Closed AlphaTechnolog closed 1 month ago
About the tests failing, looks like blueprint compiler changed the repository? if you run git clone https://gitlab.gnome.org/jwestman/blueprint-compiler nowadays, it will just fail with this
fatal: unable to access 'https://gitlab.gnome.org/jwestman/blueprint-compiler/': The requested URL returned error: 503
which is the error in the failing tests, also if you go to that repo, it will just say the repository does not exists? looks like they removed it.
ah no looks like whole gnome.org is down lmao
Yeah, I believe that GNOME services have had some problem recently, last week the forums were offline too.
I'm running the pipelines again hoping that the response is different this time.
This pull request addresses #83 where all the problem itself is being detailed, but in resume it's just that when cartero gets a non success status on a request (e.g: 400, 500), it will change the label to red/yellow depending, which is ok, but after that if you get again a 200 status, it won't just update its color to green again, which was being caused because the warning or error classes were overriding the success one since nothing was cleaning them up resulting in a label with every class, and the one with the most level of priority was the one that was overriding every other one.
What this PR does is cleaning all the classes if found before adding the new class to the label, which seems to do the trick, but im open to any change or any suggestion to improve the code :grin:
Another thing this pull request does is to fix the devShell which wasn't being able to manually let me build cartero for dev purposes, which was being caused by glib not being pulled and others, this pr addresses that one too.