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
Optional first arg for Vector.record can be an ARTIFICIAL_CELL #2858
base: master
Are you sure you want to change the base?
Conversation
✔️ 0041a06 -> Azure artifacts URL |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2858 +/- ##
==========================================
+ Coverage 67.18% 67.19% +0.01%
==========================================
Files 563 563
Lines 104284 104279 -5
==========================================
+ Hits 70064 70074 +10
+ Misses 34220 34205 -15 ☔ View full report in Codecov by Sentry. |
This comment has been minimized.
This comment has been minimized.
The CI was previously green here. I have re-launched CI on this branch just to see if the issue with recent latest failures is code related or runners environment. cc: @alkino |
Quality Gate passedIssues Measures |
✔️ e10de94 -> Azure artifacts URL |
The existing logic of the
if
statement that generated the error message"Optional first arg is not a POINT_PROCESS"
was incorrect.[ ] add test
[ ] update documentation
The Vector.record also presently requires the existence of a Section. This seems unnecessary if the POINT_PROCESS or ARTIFICIAL_CELL arg is present. Section could disagree with POINT_PROCESS about which thread they are in.
It is not easy for the user to determine the thread of an ARTIFICIAL_CELL. Perhaps there should be a method for ARTIFICIAL_CELL and POINT_PROCESS which returns the thread id. Also, recording thread time and associating with a range variable is not obvious to the user. Finally, Vector.record(callable) could be useful.