Open rlefevre opened 4 years ago
Another example with elm diff
:
$ elm diff elm-community/typed-svg 5.2.0 6.0.0
-- PROBLEM LOADING DOCS --------------------------------------------------------
I need the docs for 5.2.0 to compute this diff, so I fetched:
https://package.elm-lang.org/packages/elm-community/typed-svg/5.2.0/docs.json
I got the data back, but it was not what I was expecting. The response body
contains 133164 bytes. Here is the beginning:
[{"name":"TypedSvg","comment":"\n\n\n# HTML Embedding\n\n@docs svg\n\n\n#...
Does this error keep showing up? Maybe there is something weird with your
internet connection. We have gotten reports that schools, businesses, airports,
etc. sometimes intercept requests and add things to the body or change its
contents entirely. Could that be the problem?
elm diff elm-community/typed-svg 5.2.0 6.0.0
The parser error is:
(Index 1 (Field "values" (Index 164 (Field "type" (Failure (Region (Position 1 65494) (Position 1 4)) BadType)))))
Again at a string going above the 65535 offset, which confirms with a very high probability the 16 bits optimization issue.
Workaround, try doing elm diff
or elm bump
or elm publish
with version 0.19.0.
Show stopper - if your package depends on "elm-version": "0.19.1 <= v < 0.20.0"
. Probably a good idea not to make packages require 0.19.1 anyway.
thanks @rupertlssmith!
@juanedi just had this probelm with elm-ui (elm 0.19.1 choked on this file).
used $ npx elm@0.19.0-no-deps bump
to get this work
Quick Summary:
When running
elm bump
onjustgook/alt-linear-algebra
withelm 0.19.1
, we get the following error:When running the same command with
elm 0.19.0
, it works as expected.SSCCE
Additional Details
As it works with
elm 0.19.0
, it seems to be a regression.The compiler fails to parse the
alt-linear-algebra
package documentation.When adding a
putStrLn
in the compiler, we get the following error:By getting the same index with
jq
, we get:The full type is
Matrix4Record
:The fact that this type goes above the 65535 offset (error is at 65376) might also be significant if this is another 16bits integer optimization issue.