When trying to upload .arw and .ct2 files, I am getting the 'Image type not supported' error message in the file status area. Like this
So here are my questions:
Is it possible to add support for .arw and .ct2 file types?
Is it possible to know what other file types are not currently supported?
Thanks
This particular error message was generated by FilePondPluginImageValidateSize, as it obviously does not support these file types.
Setting allowImageValidateSize to 'false' solved this for me.
Still would be nice to know exactly what image types are not supported by this plugin, if possible :) Haven't found this info in the docs.
Thanks
Related
I was looking for a configuration parser for go and https://github.com/spf13/viper seems to come highly recommended.
I am very surprised to find that configuration files are not validated by default.
Viper parses files and extracts requested values from them but I cannot find a way to detect bad configuration.
For instance I if create a (Java style) .properties file containing just "???" and nothing else. This is accepted without any error.
I can understand the philosophy that you should ignore irrelevant configuration items but I desire more rigor. I would also like to reject anything that does not match the X=Y format in a properties file.
To me this is a fatal flaw that suggests I should use a different package (or roll my own as usual).
Have I missed something? Does viper in fact support detecting and rejecting bad configuration keys?
I think the answer is no. viper does not validate java .properties files.
I posted a bug report (or feature request depending on your point of view) as https://github.com/spf13/viper/issues/790
You can try https://github.com/num30/config library which is based on Viper. It has built-in validation.
Following error shown in the problem section for unknown property
There is no easy way to fix the warning in STS4
Even after adding the quickfix, the error is not seems to be going
Description Resource Path Location Type
'IntuitAccountingAPIHost' is an unknown property. application.properties /hk-qbo-connector/src/main/resources line 8 org.eclipse.lsp4e.diagnostic
'OAuth2AppClientId' is an unknown property. application.properties /hk-qbo-connector/src/main/resources line 2 org.eclipse.lsp4e.diagnostic
'OAuth2AppClientSecret' is an unknown property. application.properties /hk-qbo-connector/src/main/resources line 3 org.eclipse.lsp4e.diagnostic
'OAuth2AppRedirectUri' is an unknown property. application.properties /hk-qbo-connector/src/main/resources line 5 org.eclipse.lsp4e.diagnostic
You should probably consider raising your problem as a bug-report or feature request on our issue tracker. It doesn't read like a 'question' to me, and so it probably doesn't belong on SO as such.
Nevertheless let me try and answer as best as I can.
Even after adding the quickfix, the error is not seems to be going
It will, once you save the additional-spring-configuration-metadata.json file where the quickfix creates new metadata for you.
I agree it is a little unintuitve that the change is not saved automatically, but I'm afraid we (STS vscode extension) don't have control over this. The changes are being applied by the Vscode language server client, and it's the client's decision to apply the changes only to 'dirty' editor buffers rather than apply them directly to the files on disk.
As to your general statement that 'In STS 4.0 ignoring unknown property support is missing'... I think you are referring to the fact that in STS3 it used to be possible to ignore problems of a given type altogether and this is no longer possible in STS4. This is true. If you like to get this kind of user-configurability back again, please consider raising a feature request on our issue tracker. SO, really isn't the place to ask for this sort of thing.
In STS 4.11, you will find this option in Window -> Preferences -> Language Servers -> Spring Language Servers -> Spring Boot Language Servers -> Yaml Editor or Properties Editor.
I need to set up a collection of Washing Machine manuals in a way that I can then set up queries against the paragraphs that are included in the manuals. My understanding is that Element Classification should help achieve that goal
https://console.bluemix.net/docs/services/discovery/element-classification.html#element-classification
Using the tooling, I set up a collection and uploaded the following file, selecting "Default Contract Configuration" : https://www.samsung.com/us/pdf/wf338_manual.pdf
Why is this document upload failing?
To get more error details, I tried using the API with Postman but am unable to run the Add Document query as described here https://www.ibm.com/watson/developercloud/discovery/api/v1/curl.html?curl#add-document
The document is in PDF format and in text form, and is less than 50MB.
Does anyone know what is happening or has a suggestion on how to resolve?
Thanks
I have a user trying to cast an m3u8 video and he keeps getting that error.
The type provided ('video/mp2t; codecs="avc1.100.42,mp4a.40.2"') is unsupported.
Is that codec supposed to be supported?
Thank.
As stated in some threads and related SO post, some builds of Chromecast were rejected so it is recommended to use supported media type like "avc1.66.30" instead. As stated in this forum, a workaround would be trying to update the playlist or use host.processManifest.
Hope this helps.
Can anyone please help on how to open this png file: https://dl.dropboxusercontent.com/u/23248082/TEST.PNG
Also it would be great if you can tell me how it is enrcrypted or why its not opening.
It opens fine only with Meditech client. It seems Meditech is encrypting in someway.
I tried with different viewers and also tried converting it into differen format but so far no luck.
Iam also a newbie in this area. Any help would be highly appreciated.
Thanks..
Looking at it with tweakpng it seems the format is deliberately corrupted for proprietary use. There's a wrong CRC for the palette (correcting it does no good) and an invalid chunk count.
If your Meditech is the EHR (Electronic Health Record) system then you will only be able to accurately view the image by accessing it from the system. All data is encrypted for the purpose of restricting access to patient records.