-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
No valid parser for XML #2343
Comments
Since the error occurs sporadic, it is probably because of your VPN, which may be failing to download the XML atom correctly. Ìf you check feedjira documentation, it states:
Which means, it checks if the returned (assumed) XML file can be parsed by one of its parsers. This error message is kind of misleading, since it is not that it hasn't a parser, but that the file given to be parsed is not a valid parseable XML file. |
But thinking about it now, it would be useful to add a check if the file was fetched successfully in the external posts plugin. Would you mind sending a PR for this? |
I am more than happy to create the PR. |
Adjusting issue #2343 by adding null check.
…edivat#2347) Adjusting issue alshedivat#2343 by adding null check.
…edivat#2347) Adjusting issue alshedivat#2343 by adding null check.
…edivat#2347) Adjusting issue alshedivat#2343 by adding null check.
…edivat#2347) Adjusting issue alshedivat#2343 by adding null check.
…edivat#2347) Adjusting issue alshedivat#2343 by adding null check.
…edivat#2347) Adjusting issue alshedivat#2343 by adding null check.
Have you checked that your issue isn't already filed?
Bug description
Feed parser could be loading empty xml file even the format is matching.
How to reproduce the bug
Please notice the error does not occur every time and it is hard to predict when will happen.
Error messages and logs
What operating system are you using?
Mac
Where are you seeing the problem on?
Running locally with Docker
More info
I suspect this issue is from rendering order but not sure as I have not looked into it.
Update: VPN could also cause the problem.
The text was updated successfully, but these errors were encountered: