Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Indent each line of error messages #161

Merged
merged 5 commits into from
Sep 25, 2023

Conversation

anka-213
Copy link
Member

Previously only the first line of an error message was indented.

Changing this makes the error messages easier to parse, both for humans and machines. In addition to looking better it would also help making it easier for gf-lsp to show the errors at the correct location

Before:

PizzaEng.gf:47:1:
   conflicting information in module PizzaEng
    lin Friends = "friends" ;
and
    lin Friends = "other" ;

After

PizzaEng.gf:47:1:
   conflicting information in module PizzaEng
       lin Friends = "friends" ;
   and
       lin Friends = "other" ;

By indenting each line instead of just the first, we simplify
the work of the gf-lsp parser, so we can see which errors are the same
There are no longer any gihub actions runners available for these

Note that this means we can't build for ubuntu-18 anymore, but that
should hopefully no longer be relevant, since it's over 5 years old now.
cibuildwheel requires python >= 3.8
@anka-213 anka-213 changed the title Indent each line of an error message Indent each line of error messages Sep 25, 2023
@anka-213
Copy link
Member Author

anka-213 commented Sep 25, 2023

I added commits to disable the platforms that github no longer has runners available for, to fix the stuck CI actions.

I also made the build CI actions faster by making them not build gf an extra time just for the tests. This has cut the CI time for the stack builds roughly in half, from 18 minutes to 9 minutes (or 2 hours cpu time vs 1 hour cpu time).

@inariksit inariksit merged commit 7d9015e into GrammaticalFramework:master Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants