#Error with Gleam 0.30 and order operators?
1 messages · Page 1 of 1 (latest)
The precedence of the operators <> and |> changed. You could put {} around the string you want to print or do
io.println_error(“Unexpected Error Code: “ <> int.to_string(unhandled_exit_code))
Sorry typing on a phone 🤣
^^^ If the error is coming from glee unit then I think gleeunit will need to do an update too.
It might have already, you could check what the most recent version is 🙂
Looks like it is in glacier
@celest badger I'm not sure if this is a bug but I tried to add gleam = ">= 0.30" and it's triggering:
error: Invalid version format
I was unable to parse the version >= 0.30.
The error from the parser was:
expected more input
if I put gleam = "~ > 0.30" then it's working
but I guess it's not the same effect
">= 0.30" isn't a valid requirement, would be ">= 0.30.0"
It's the same rules as Hex requirements
I just copied from the announcement ;-P
you're welcome!
@coarse cairn I just created a PR https://github.com/inoas/glacier/pull/12 ... but I cannot find glacier_gleeunit and it's requiring be modified as well, please, could you point me out where is it?
yes I need to fix glacier and it (need to rely) relies on a fork of gleeunit sadly - do that could be it too
the gmeeunit glscier is a branch in my gleeunit repo which is a fork of ipils
i with my changes were somehow in upstream - they badically allow to run gleeunit as a function and specific a list of test module pathes and do not ssnd unix exit/halt as a flag
@fair cove I think after fixing I want to try showtime as a runner 🙂
@barren jay please try again with the updated version
Nice ✨ I think that should be possible. You would need to run it with shellout (because it was tricky to expose a function). Specific modules are supported as CLI arguments and adding a flag for exit-code should be easy.
Currently it is not compatible with gleam 0.30 (this is in progress but need to figure out how to deal with some deps first).
at this point, keeping in mind that gleeunit is abandoned, glacier should get the code that is needed from that and avoid an unnecessary dependency, just for simplicity
I keep it as a fork to make it easy to update and rebase with upstream
sorry, maybe abandoned is a strong word, I just wanted to point that it was put aside, freeze and it's not planned to evolve it in a near future, and even it's recommended using glacier instead
the problem with that is you need to take care of two repositories and because it's not clear where glacier_gleeunit dwells, it's difficult getting people involved
as a small and fast fix, I recommed adding a Github link to the Hex package pointing out the URL to the gleeunit repo and branch in use for the package
who said any of that ;)? i am happy that you are using it - I'am planning on also offering showtime as a runner
will do
oh wow 😉
@barren jay did you check out showtime? I am still trying to wrap my head around what I do wrong here https://discord.com/channels/768594524158427167/1129335105974968370 ... then will take a look at using showtime as a runner instead of gleeunit for glacier
sorry, I was lost in translation, I have no idea what's "showtime as a runner" 😄 ... I guess you're referring to a new dependency to use instead of gleeunit for glacier, right?
yes
so glacier does not run the tests, it figures out which test modules it should run and passes them to the runner and starts the file watcher per target etc
I feel louis isn't a fan of the approach but I like it a lot, it is a bit like mix test interactive, it does not replace mix test
it sounds good 🙂