Skip to content
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

[query] yaml input file throwing error #399

Closed
akikinho opened this issue Jul 1, 2024 · 9 comments
Closed

[query] yaml input file throwing error #399

akikinho opened this issue Jul 1, 2024 · 9 comments

Comments

@akikinho
Copy link

akikinho commented Jul 1, 2024

Hello Wireviz Team,
I am facing an issue with the Wireviz software recently after the update. Sometimes the yaml input file runs and sometimes it doesn't. Next when I switch to another new file and start again it works and then it fails again. I am wondering if there is some random bug in the software which breaks the code? I get the following error again and again until I switch to a new file and start again from the beginning. Could you please guide regarding this issue and how to best go about resolving it?

File "", line 730, in realpath
OSError: _getfinalpathname: path too long for Windows

Package Version


click 8.1.7
colorama 0.4.6
graphviz 0.20.3
numpy 1.26.4
pandas 2.2.2
pillow 10.3.0
pip 24.0
python-dateutil 2.9.0.post0
pytz 2024.1
PyYAML 6.0.1
setuptools 70.1.0
six 1.16.0
tzdata 2024.1
wireviz 0.4.1.dev0

Microsoft Windows [Version 10.0.19045.4529]

Thank you and Best Regards,

@kvid
Copy link
Collaborator

kvid commented Jul 1, 2024

It seems you already are using the branch of PR #365 that should include a fix for a similar error. This issue might be a duplicate of #391 that will be fixed by PR #392 that probably soon will be ready for merging into #365.

In the meantime you could try the current branch of #392 to see if it already contains the fix you need. If not, I suggest you add a comment to #392 with a reference to this issue and ask the author if the issues might be related.

Please provide your Python version and a YAML input that triggers the error.

@akikinho
Copy link
Author

akikinho commented Jul 4, 2024

Thank you @kvid,
The Python version is Python 3.12.3 and the YAML file is too big.

@kvid
Copy link
Collaborator

kvid commented Jul 5, 2024

@akikinho - Did you confirm that #392 fixed your issue?

The relevant fixes are now merged into the release/v0.4.1-rc branch of PR #365 that is not yet released, but also describes how you can install the latest collection of fixes before the release.

@akikinho
Copy link
Author

akikinho commented Jul 7, 2024

Hello @kvid, I am wondering how to call the #392 ? Is it using this command gh pr checkout 392?

@kvid
Copy link
Collaborator

kvid commented Jul 7, 2024

@akikinho wrote:

Hello @kvid, I am wondering how to call the #392 ? Is it using this command gh pr checkout 392?

That command might still work, so please try that. However, as #392 now is already merged into PR #365, you might also try that PR. See my previous comment above.

@akikinho
Copy link
Author

akikinho commented Jul 8, 2024

Hello @kvid, I downloaded the #392 wireviz.py file into the local system and ran the yaml input file and it showed the same error.

@kvid
Copy link
Collaborator

kvid commented Jul 8, 2024

@akikinho wrote:

Hello @kvid, I downloaded the #392 wireviz.py file into the local system and ran the yaml input file and it showed the same error.

Thank's for reporting this. Please provide a full copy of text output in your terminal (AKA command shell) window of your latest test, starting with the command you execute, all output from WireViz, including stack trace and exception output.

Then I want you to provide (in a new comment) a similar full copy of text output in your terminal window of you testing #365, starting with the installation commands described in that PR description (pip uninstall wireviz + pip install git+https...), including executing wireviz on your YAML input, all output from WireViz, including stack trace and exception output.

When you paste in such a large text dump into your comment, I recommend you select all lines of the text dump and press the <> Code button to format the text dump as raw text. Optionally, you might also type cmd immediately following the 3 leading backticks that appear (but nothing else on the same line) to obtain command shell syntax coloring.

@kvid
Copy link
Collaborator

kvid commented Jul 14, 2024

@akikinho - Now it's too late to try those PRs I requested you to try. The fixes was released as v0.4.1 yesterday.

If this issue is still a problem with the latest release, you must provide a full copy of all text output in your terminal window while you run the latest release (as I described with the PR testing above). Otherwise, please close this issue as completed.

@kvid
Copy link
Collaborator

kvid commented Jul 16, 2024

@akikinho - I'm glad that this issue has been resolved with the v0.4.1 release (confirmed by you closing the issue as completed). 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants