Flo Edelmann
Flo Edelmann
Workaround: Setting `stringSerialization = YamlBuilder.StringSerialization.SINGLE_QUOTATION`: ```yaml [ 'foo', 'bar, baz' ] ```
It probably has to be fixed in the [`getQuotationAvailability` function](https://github.com/Him188/yamlkt/blob/5fa3c522370debf52bf87969cbe21f2b0b686b19/yamlkt/src/commonMain/kotlin/net.mamoe.yamlkt/internal/Escape.kt#L650).
Thanks for the submission @aboutofpluto! However, as @kengruven said, it will be quite a lot of work to bring this fixture to a mergeable state, so I'll close this as...
> I submitted the file via Github because there was an error with the Fixture Editor. Do you remember which error message was reported? It is not included in the...
> Request failed with status code 413 HTTP Status Code 413 means "Content Too Large": https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/413 So something is not quite right yet... @luc122c Dou you know what could be...
Yes, GitHub has a character limit (65536 according to your screenshot), and the error message that includes the uploaded file as an base64-encoded string is larger than that. But the...
Nope, no CDN or (external) reverse proxy. Maybe the Nginx reverse proxy and Express interpret the file size differently?
Seems like the default applies then: https://github.com/OpenLightingProject/open-fixture-library/blob/master/server/nginx-site-available
I'd appreciate a PR, then I can apply it on production.
see https://github.com/OpenLightingProject/open-fixture-library/pull/3860#issuecomment-2033165404