-
Notifications
You must be signed in to change notification settings - Fork 1.4k
MRG, MAINT: Tweak CIs #7943
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
MRG, MAINT: Tweak CIs #7943
Conversation
Fixed VTK9 rendering on macOS by disabling depth peeling and anti-aliasing. The remaining bug on my macOS system is that the widget controls do not work because there is a 2x mismatch between their render position and the click position needed to control them. We'll have to see if this is fixable at the PyVista end, or if this is an underlying VTK bug (my money is on the latter). |
This suggests that there's something off with the conversion between retina pixels and displayed points |
|
||
|
||
############################################################################### | ||
# Work around autosummary making bad :class: links |
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.
this sucks. It was working with an older version? if so can we rather pin the version rather than crippling our code?
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.
How does this cripple our code? It just replaces a few docstrings. Subclassing like isinstance(x, dict)
are still fine. Overhead should be minimal.
The problem is that numpydoc improved the signature extraction, and we hit a bug now with autosummary trying to add effectively:
:class:`v, remove specified key and return the corresponding value.`
to correspond to the D.pop() -> v, remove specified key and return the corresponding value.
docstring.
This seemed like the cleanest solution, but I'm open to other ideas.
it's because numpydoc does not parse docstring of std lib?
… |
See above -- I think it's because numpydoc passes the stdlib definition unchanged, then autodoc sees the |
would it make sense to wait for autodoc/autosummary to fix the bug?
… |
Maybe, but in the meantime all CircleCI builds will fail. I guess we could roll back numpydoc in the meantime, but no idea how long the autodoc fix will take. |
Personally I don't see why the |
ok fair enough
let's proceed and see in a few weeks/months if we can undo this after a fix
upstream
… |
I agree with @agramfort that it is kind of ugly, but I think it's okay for now :) |
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.
- Switch to
conda
for VTK (Following the installation instructions for macOS yields an error message #7939)
Wait, you're not doing that, unless my brain isn't functioning right bc I haven't had breakfast yet :) You're still using pip
to install vtk
, and only dropped the version constraint for macOS. This will not fix #7939.
I believe this also begs the question if / whether we should switch to $ conda search vtk |grep pkgs/main
vtk 8.1.0 py27h04d9db9_201 pkgs/main
vtk 8.1.0 py27h87a2a2b_201 pkgs/main
vtk 8.1.0 py35h04d9db9_201 pkgs/main
vtk 8.1.0 py35h87a2a2b_201 pkgs/main
vtk 8.1.0 py36h04d9db9_201 pkgs/main
vtk 8.1.0 py36h87a2a2b_201 pkgs/main
vtk 8.1.1 py27ha9eb873_204 pkgs/main
vtk 8.1.1 py27hce9f6a2_204 pkgs/main
vtk 8.1.1 py36ha9eb873_204 pkgs/main
vtk 8.1.1 py36hce9f6a2_204 pkgs/main
vtk 8.2.0 py27h9bafd54_200 pkgs/main
vtk 8.2.0 py36h9bafd54_200 pkgs/main
vtk 8.2.0 py37h9bafd54_200 pkgs/main
$ |
@hoechenberger I think it follows the news on pyvista/pyvistaqt#16 (comment) and pyvista/pyvistaqt#15 (comment) Fetching |
Ok so we only need to pin VTK to >=9.0.1? |
For MacOS at least, yes |
This reverts commit 237e3e1.
The failures of the notebook job are note related, see #7944 |
The
|
try:
python -m pytest
see https://docs.pytest.org/en/stable/usage.html
|
The command failing is often an indicator that the install still failed (but didn't error out for some reason) |
I pushed again, it seems there was indeed an error in the installation. |
Still not happy:
There is a tab in the file XD |
how do we proceed? we have 2 PRs that are red but collectively could be green? |
I branched out in #7944. If it makes things easier, I can integrate it in here? |
ok for me
… |
thx a lot @larsoner and @GuillaumeFavelier ! |
* upstream/master: (30 commits) MRG: Add remove_labels to _Brain (mne-tools#7964) Add get_picked_points (mne-tools#7963) ENH: Add OpenGL info to mne sys_info (mne-tools#7976) [MRG] Fix reject_tmin and reject_tmax for reject_by_annotation in mne.Epochs (mne-tools#7967) mrg: Add scalar mult and div operators for AverageTFR (mne-tools#7957) MRG, MAINT: Cleaner workaround for Sphinx linking issue (mne-tools#7970) MRG, ENH: Speed up epochs.copy (mne-tools#7968) MRG, BUG: Allow ref mags to have a comp grade (mne-tools#7965) do not forget to pass adjacency (mne-tools#7961) [MRG] fix Issue with stc.project after restricting to a label (mne-tools#7950) Only process nirx event file if present (mne-tools#7951) MRG+1: BUG: info['bads'] order shouldn't matter in write_evokeds() (mne-tools#7954) Fix some small glitches introduced via mne-tools#7845 (mne-tools#7952) Add time player (mne-tools#7940) MAINT: Clean up VTK9 offset array [circle front] (mne-tools#7953) MAINT: Skip a few more on macOS (mne-tools#7948) fix links [skip travis] (mne-tools#7949) MRG, MAINT: Tweak CIs (mne-tools#7943) MRG, BUG: Fix vector scaling (mne-tools#7934) MRG, VIZ, BUG: handle CSD channel type when topo plotting (mne-tools#7935) ...
master
) so that we can transition to or at least allow the "new" (as of 2016) way of writing code, as discussed hereconf.py
make flake
on the entire codebase not just select foldersconda
for VTK (Following the installation instructions for macOS yields an error message #7939)numpydoc
seen hereCloses #7939
NumpyDoc will still cause a failure, I think it needs to be fixed at the NumpyDoc end...