Radosław Waśko
Radosław Waśko
> Radek, haven't you already reported this problem once? > > * [Warn about invalid indentation levels #8858](https://github.com/enso-org/enso/issues/8858) I have written in my comment that these 2 issues are related....
> The logging of the problematic test works, as can be seen in its [output](https://github.com/enso-org/enso/actions/runs/8802686851/job/24191517691?pr=9763#step:7:4054). So far, I have restarted the `Standard Library Tests (GraalVM CE) (linux, x86_64)` job three...
Hmm, what causes the `org.enso.interpreter.runtime.data.Type.allTypes(Type.java:142)` call to be repeated _so many times_ on the stack? It looks like some infinite recursion loop, no? Do I understand this log correctly, or...
> > Hmm, what causes the org.enso.interpreter.runtime.data.Type.allTypes(Type.java:142) call to be repeated so many times on the stack? It looks like some infinite recursion loop, no? Do I understand this log...
Moreover, the `Enso_Project.enso_project` call fails if the first time we are calling it outside of Enso: ``` Assertion_Error.Error 'Should not reach here: callRootNode = org.graalvm.polyglot.Value.execute. Probably not called from Enso?'...
Moreover, adding `make_a = A.Ctor2` to `Main.enso` makes the program run: ``` Ctor2 Ctor2 ``` because it also shadows the imported `make_a`. This shadowing also does not issue any error...
> According to @4e6 and @JaroslavTulach, type shadowing is perfectly fine. Imagine you would like to define your `Boolean` type. In that case, you would not be able to import...
> * This would require changes in the Cloud to allow the `/logs` endpoint to accept multiple messages in a single request. As reported by @PabloBuchu the Cloud endpoint for...
I've implemented the batching part of this task with #10918. Moving back to New so that we can schedule the second part - handling pressure by blocking further async log...
Possible solutions: 1. reorder test summary so that failed groups are at the end i. cons: - with such reordering, one cannot display progress of tests being run but instead...