-
Notifications
You must be signed in to change notification settings - Fork 14
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
Sign of pulse parameters is not deserialized properly #826
Labels
bug
Something isn't working
Milestone
Comments
I agreed and added to the milestone. And indeed, by avoiding parsing the strings manually, these errors should become almost impossible. |
stavros11
added a commit
that referenced
this issue
Mar 4, 2024
stavros11
added a commit
that referenced
this issue
Mar 21, 2024
hay-k
pushed a commit
that referenced
this issue
Mar 29, 2024
hay-k
pushed a commit
that referenced
this issue
Mar 29, 2024
10 tasks
stavros11
added a commit
that referenced
this issue
Apr 15, 2024
alecandido
pushed a commit
that referenced
this issue
Apr 15, 2024
hay-k
pushed a commit
that referenced
this issue
Apr 16, 2024
alecandido
pushed a commit
that referenced
this issue
Jun 25, 2024
stavros11
added a commit
that referenced
this issue
Jul 13, 2024
alecandido
pushed a commit
that referenced
this issue
Aug 5, 2024
alecandido
pushed a commit
that referenced
this issue
Aug 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
gives
so
-0.02
is converted to0.02
. I am not sure if this has any practical consequence in this case.I found this while working on #789 for 0.2, but then I realized that it also exists for 0.1. I am guessing it will be solved by #818 where the ugly
eval
will be dropped, so I would even postpone for 0.2. @alecandido if you agree, we can put this directly to the 0.2 milestone.The text was updated successfully, but these errors were encountered: