Challenge save succeeds but fails [closed]

Question

After editing a challenge checker script and saving, the save process times out and we get a "Save failed" message. However the save did actually occur. Could the save message please be fixed - it confused me for a bit before I learned to ignore it.

Comments

I believe this would be more appropriate for the challenge checkers forum, rather than here.

Answer 1

I only managed to reproduce this once, after that, it's running smooth. But I have a theory.

The save is failing, because it fails to commit to GitLab.com, which seems to be a timeout issue in their end. I am not too happy about the GitLab integration. I like the idea, but there are a few things that really didn't turn out as intended.

I would like to wait for a few days to see what happens in their end. Otherwise I might have to remove the integration between the sites.

Comments

Fails every time for me. Note that I do not have GitlLab account.

---

Having a GitLab account or not isn't relevant. Project-GC is keeping the repository updated regardless.

I know one other thing that potentially could be slow. I will make a patch to add that into a background queue instead of running it directly in the ajax call. I'll get back with another comment later today.

---

A new release is now out there. Does it work better with that patch?

---

Sorry Magma, still faulty :-(

---

That's weird. First I would like to double check. We are speaking about saving source code for a challenge checker script right?

Here are some (temporary) debug log from when I am saving one of my scripts:
A 1524138632
B 1524138632
C 1524138632
D 1524138632
E 1524138632
F 1524138632
G 1524138635
H 1524138635
I 1524138635
J 1524138635
K 1524138635
L 1524138635

The number is a unix timestamp, so between F and G it takes ~3 seconds, that's the push to GitLab.com.

If you visit https://project-gc.com/Admin/dev-access (temporary enabled) and use the link there to get into my development environment. Can you reproduce it there? When using the development environment you will get a pink tint on the background, and you will see that the subdomain dev-01 is used.

When using the development environment it might be easier for me to see errors in the logs, since there aren't a hundred simultaneous users. Also, it will save the timings (those I posted above) into a file.

---

Fails in the dev environment too. If you want to see the timestamp I edit the script 528 just 2 minutes ago. And yes, we are talking about editing the checker script itself. By the way I live in New Zealand, the timestamp on this post is 4:34 In the morning.

---

Does this happen with other files than script id 528 as well? I can easily reproduce it with this file though.

When committing the new version to GitLab.com via their API I am getting a HTTP 500. Project-GC then retries. HTTP 500 each time. BUT, it also gets commited each time...

I will spend some more time looking into this, but it might end up with me removing the GitLab implementation.

---

I have created a support ticket. Last time it took them almost a month to resolve my issue, so I will probably disconnect the whole thing today.

---

All fixed! Git lab fixed it or you disconnected them?

---

I removed it. Will consider it again when they fix things.

---

Thanks for your help, Magma.

---

It's you who deserves the thank you. For creating challenge checkers, caring and reporting.

Answer 2

This bug should be solved

Comments

Sorry, fault still present.

---

That's strange because it happen to me in the weekend but on monday it was solved. I'm using using chroom Versie 65.0.3325.181 (Officiële build) (64-bits)

---

Saving the script details works correctly. Saving the script itself does not. I use a tablet, fails with both Samsung Internet and Chrome browsers. Will check on a pc when I get to work (in two hours)

---

Fails on my PC, using Chrome Version 63.0.3239.132 (Official Build) (64-bit) or Internet Explorer version 11.0.9600.18977. I doubt that it is the version of Chrome, though - more likely it broke again since you last tried it.