-
-
Notifications
You must be signed in to change notification settings - Fork 899
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
docs: Added fix for building on Windows and resolved other build errors #2395
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like temp_file
is only really needed on lines 176-183, and can be deleted afterwards. Which means you can add a finally
block for try:
on line 174, and have the file deleted within that block -- then the file name can remain a local variable within _scan_source_file()
, and doesn't need to become an instance member.
That is what I tried initially, hence why I called it out in the PR description (3). When you do the finally and delete of the file, you get an error in the JSON decoder. I presume because when you call delete, it then deletes the JSON from memory which is then being set in the parent function. I presume that when finally gets called it overwrites the return and thus you have the issue. It likely works for Unix but not on windows - not certain. A fairly comprehensive explanation is here: https://stackoverflow.com/questions/19805654/python-try-finally-block-returns. |
Here's the docs for
So, I think the best approach would be to:
|
Ok, so these commands are not executing in the way I would think they should: # In try:
temp_file.close # no error occurs
temp_file.close() # no error occurs
# In finally:
temp_file.delete # does not delete the file
temp_file.delete() # throws TypeError: 'bool' object is not callable I have tried all combinations and yeah, no go. My Python is not the strongest here. Full Code: def _scan_source_file(self):
with tempfile.NamedTemporaryFile(mode='rt', suffix='.json', delete=False) as temp_file:
try:
#self.temp_file_path = temp_file.name
temp_file.close
subprocess.run(
['dartdoc_json', self.source_file, '--output', temp_file.name],
stdout=subprocess.PIPE,
stderr=subprocess.STDOUT,
check=True,
shell=True,
)
json_string = temp_file.read()
return self._extract_symbol(json_string)
except subprocess.CalledProcessError as e:
cmd = ' '.join(e.cmd)
raise RuntimeError(
f'Command `{cmd}` returned with exit status'
f' {e.returncode}\n{e.output.decode("utf-8")}'
)
finally:
temp_file.delete |
Right, so:
|
Make sense. Updated and ran:
Eliminating the close gets you:
These are the errors that I was getting earlier today when I was solving it and which led to just putting the name in the class. |
Ah, I guess reading the file now needs an explicit open: with open(temp_file.name, 'r') as t:
json_string = t.read() |
So let me just make sure I have this straight, create a temp file, then immediately close it, pipe data to it, reopen it to read it to put the contents into a var to be returned, and on exit delete the temp file. As crazy as that seems, it worked. Edit: Just went back and confirmed it was deleting the files from the temp directory. |
Yes, that's correct:
|
Crazy and I had tried numerous variances, but didn't think to close and read back to memory. Anyway, all the code has been updated and I appreciate the help! I don't know if you saw my comments on your already merged PR for melos doc-setup, but it's a similar windows issue thing. The command is there and working, just needs some tweaks to pass the formatter. |
Just added another fix for Sphinx docs discuss the defaults for autobuild: https://pypi.org/project/sphinx-autobuild/ Additionally, I have added the flags that currently exist under the |
…rs (flame-engine#2395) <!-- The title of your PR on the line above should start with a [Conventional Commit] prefix (`fix:`, `feat:`, `docs:`, `test:`, `chore:`, `refactor:`, `perf:`, `build:`, `ci:`, `style:`, `revert:`). This title will later become an entry in the [CHANGELOG], so please make sure that it summarizes the PR adequately. --> # Description <!-- Provide a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change. If this is a breaking change, specify explicitly which APIs were changed. --> @eukleshnin identified issues with building the documents locally on a Windows workstation. Namely, the following was occurring: ``` reading sources... [ 2%] flame/layout/align_component Exception occurred: FileNotFoundError: [WinError 2] ``` This was determined to be a combination of several things. 1. In `dart_domain.py`, the `subprocess.run` calling dartdoc_json did not have the shell parameter set to true. This solves the error about the file not being found. This then generates errors that subsequent references to the `temp_file` did not exist. 2. This was due to the default setting with Python `tempfile` where when it determines the temp file has been closed, it deletes it; however, it was still needed, so by setting the `delete=False` parameter, the file would still remain. 3. Unfortunately, because it still remains, it needs to be deleted once it is no longer needed. Trying to use `finally:` with the `try` block failed to produce the results desired, so the temp file name was registered with the class so it can be deleted in the original calling function if it exists. This proved successful. 4. Although not critical, the same temp file uses a suffix of `json` so it was creating files `xxxxjson`. By adding the "." in the suffix, it creates valid file names now. This doesn't actually fix anything, it just seemed wrong, so I fixed it to be valid files if ever needed down the road. Now that the docs built, there were several warnings that could be resolved: 1. `Overlays.md` was not referenced in the TOC tree. 2. Since overlays were removed in flame-engine#2384, the Platformer tutorial had a link to the old path and it needed to be updated. Finally and open for discussion, during this process of debugging, I upgraded all packages to the most current to see what impacts there were. The following is the old and new potential `requirements.txt`: ``` ----Old linkify-it-py==2.0.0 myst-parser==0.18.1 Pygments==2.12.0 Sphinx==5.0.2 sphinxcontrib-mermaid==0.8.1 sphinx-autobuild==2021.3.14 jinja2==3.1.2 ----- New linkify-it-py==2.0.0 myst-parser==1.0.0 Pygments==2.14.0 Sphinx==6.1.3 sphinxcontrib-mermaid==0.8.1 sphinx-autobuild==2021.3.14 Jinja2==3.1.2 ``` The only byproduct of this upgrade was a deprecated package warning for `attrs_image` in `conf.py` which was updated to `attrs_inline`. I made that change initially for this PR, but backed it out as I didn't know if there was a desire to update the `requirements.txt` and felt some discussion may be warranted. Regardless, with everything upgraded or left as is, the other fixes resolve the issues on Windows. ## Checklist <!-- Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes with `[x]`. If some checkbox is not applicable, mark it as `[-]`. --> - [X] I have followed the [Contributor Guide] when preparing my PR. - [ ] I have updated/added tests for ALL new/updated/fixed functionality. - [X] I have updated/added relevant documentation in `docs` and added dartdoc comments with `///`. - [ ] I have updated/added relevant examples in `examples` or `docs`. ## Breaking Change? <!-- Would your PR require Flame users to update their apps following your change? If yes, then the title of the PR should include "!" (for example, `feat!:`, `fix!:`). See [Conventional Commit] for details. Also, for a breaking PR uncomment and fill in the "Migration instructions" section below. ### Migration instructions If the PR is breaking, uncomment this header and add instructions for how to migrate from the currently released version to the new proposed way. --> - [ ] Yes, this PR is a breaking change. - [X] No, this PR is not a breaking change. ## Related Issues <!-- Indicate which issues this PR resolves, if any. For example: Closes flame-engine#1234 !--> <!-- Links --> [Contributor Guide]: https://github.com/flame-engine/flame/blob/main/CONTRIBUTING.md [Conventional Commit]: https://conventionalcommits.org [CHANGELOG]: https://github.com/flame-engine/flame/blob/main/CHANGELOG.md --------- Co-authored-by: Lukas Klingsbo <me@lukas.fyi>
As mentioned in #2395, there are several lingering issues that can be solved by bumping the Python package requirements up. All packages need / can run on Python 3.8+, so the docs do not need to be updated regarding that. This PR specifically fixes the following warnings: flame\doc\bridge_packages\bridge_packages.md:4: WARNING: 'myst' reference target not found: ..\bridge_packages\flame_audio\flame_audio.md ....There were a lot of those.... `attrs_image` is deprecated. Use `attrs_inline` instead. Additionally, this PR adds a new command melos doc-kill which executes the kill-server.py script. This script relies on psutil which has been added to the requirements.txt, but allows a cross platform ability to isolate and kill process threads that are locking the port 8000. This commonly happens when you exit melos doc-serve and the internal web server doesn't die as well. This may not be an issue for Unix platforms, but for Windows users its extremely annoying. The only alternative for Windows users is to manually do: netstat -ano | findstr :8000 // Then run: taskkill /PID XXXXX /F As I mentioned in the other PR, I split this out so it can be debated mainly for the bump in requirements; however, I feel the benefits are very worth it. I marked this as breaking just because it changes the base package requirements and adds a package which may not qualify as breaking, depending on how you look at it. Edit: Forgot that this PR also fixes a typo in the melos doc-serve description and corrects the misspelling of everytime to every time.
Description
@eukleshnin identified issues with building the documents locally on a Windows workstation. Namely, the following was occurring:
This was determined to be a combination of several things.
dart_domain.py
, thesubprocess.run
calling dartdoc_json did not have the shell parameter set to true. This solves the error about the file not being found. This then generates errors that subsequent references to thetemp_file
did not exist.tempfile
where when it determines the temp file has been closed, it deletes it; however, it was still needed, so by setting thedelete=False
parameter, the file would still remain.finally:
with thetry
block failed to produce the results desired, so the temp file name was registered with the class so it can be deleted in the original calling function if it exists. This proved successful.json
so it was creating filesxxxxjson
. By adding the "." in the suffix, it creates valid file names now. This doesn't actually fix anything, it just seemed wrong, so I fixed it to be valid files if ever needed down the road.Now that the docs built, there were several warnings that could be resolved:
Overlays.md
was not referenced in the TOC tree.Finally and open for discussion, during this process of debugging, I upgraded all packages to the most current to see what impacts there were. The following is the old and new potential
requirements.txt
:The only byproduct of this upgrade was a deprecated package warning for
attrs_image
inconf.py
which was updated toattrs_inline
. I made that change initially for this PR, but backed it out as I didn't know if there was a desire to update therequirements.txt
and felt some discussion may be warranted.Regardless, with everything upgraded or left as is, the other fixes resolve the issues on Windows.
Checklist
docs
and added dartdoc comments with///
.examples
ordocs
.Breaking Change?
Related Issues