[00:52:34] I’ve finally managed to create a test for Z6804 (but cannot connect it, of course ) Z21616. I noticed that the duration after publishing was 9394 ms compared with 5727 ms before publishing. Similarly, Z21612 completes before publishing in 5715 ms but times out after publishing (>10000 ms). [02:43:58] That's so strange, for me it passes in under a second? [09:08:33] Do you mean that you see results in under a second? If you look at the metadata in “Details”, do you not see 9394 ms? (re @MolecularPilot: That's so strange, for me it passes in under a second?) [09:59:11] Oh I see that now, sorry it was too early in the morning for me to realise it was probably cached hahaha! I'm not quite sure what the issue is though [09:59:26] Good luck resolving it! :) [10:09:29] That’s okay. I think there are different API calls depending on the context but if this sort of difference in performance is typical, it may be worth investigating. I’m thinking about some workarounds for Z21612 but I’m not actively working on it. (re @MolecularPilot: Oh I see that now, sorry it was too early in the morning for me to realise it was probably cached hahaha! [10:09:29] I [10:09:29] 'm not quite sure wha...) [18:31:33] Hello all, the Volunteer's Corner is happening right now! Please join us at https://meet.google.com/xuy-njxh-rkw [18:31:59] (also, sorry for not reporting it here, it's a busy period and I'm starting to lose pieces here and there) [19:55:14] https://www.wikifunctions.org/w/index.php?title=Special:Log/block&page=User%3ASHB2000 [19:55:19] what a childish behaviour [20:38:21] indeed it was (re @Sannita: after I asked you not to use inflammatory tones, one week of silence should teach you when enough is enough) [20:54:09] Just to note that Feeglgeef is currently silenced and cannot defend themselves [20:55:05] Sigh, I only noticed now (re @nerim4n: ) [21:04:23] Feeglgeef it would be nice if you don't circumvent the block by DM'ing people with inappropriate messages [22:49:45] Unfortunately, the way JS treats `eval` won't let us do this (since we need `eval` to run the submitted code). (@lucaswerkmeister though I wonder if the evaluator should perhaps block `eval()` instead) [22:50:36] We do sort-of block `exec` inside of the Python `exec` blocks, but it's pretty easy to work around. `eval` and `exec` are here to stay :-/