-
Notifications
You must be signed in to change notification settings - Fork 141
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
Failed to read schema document https://www.eolang.org/xsd/XMIR-0.48.2.xsd
#3636
Comments
@yegor256 Could you take a look, please? This issue blocks any progress in |
Where it happened: at com.jcabi.xml.StrictXML.<init> (StrictXML.java:122)
at com.jcabi.xml.StrictXML.<init> (StrictXML.java:93)
at com.jcabi.xml.StrictXML.<init> (StrictXML.java:84)
at com.jcabi.xml.StrictXML.<init> (StrictXML.java:74)
at org.eolang.jeo.representation.VerifiedEo.asXml (VerifiedEo.java:71) |
@volodya-lombrozo the URL is valid. The problem most probably is related to some instability of network connection. The best we can do is to introduce a retrying mechanism to |
@yegor256 I believe we shouldn't rely on an internet connection here. It creates an enormous number of bugs and flaky tests. It's better to keep everything local. In other words, now we can't develop without the internet. Btw, it is often the case. As you can see, I faced with this problem immediately. |
@yegor256 btw, it might be interesting https://stackoverflow.com/questions/28267536/how-to-refer-to-a-classpath-xsd-in-xsischemalocation |
@volodya-lombrozo actually, not a bad idea. We can introduce new class |
@yegor256 I got the same error for EO
|
@volodya-lombrozo looks like you are still using |
https://www.eolang.org/xsd/XMIR-0.46.0.xsd
https://www.eolang.org/xsd/XMIR-0.48.2.xsd
@yegor256 The |
@rultor release, tag is |
@volodya-lombrozo try 0.49.0 please |
@yegor256 I'm getting this with
Full log is right here
If it's important, I can open a separate issue for this problem, however the origin is the same. |
@volodya-lombrozo better close this one and open a new one, since the scope is changed: we have a new module, but it doesn't work as expected. |
Continuation is here: #3677 |
Recently one of the pipelines in
jeo-maven-plugin
failed with the following error:build.log
Moreover, it failed only on
ubuntu
system. Onmacos
everything is fine.The text was updated successfully, but these errors were encountered: