Ran
|
Jobs
1
|
Files
816
|
Run time
57s
|
Badge
Embed ▾
README BADGES
|
push
github
Fix qpy.dump()'s use_symengine when passed a truthy object (#11730) (#11731) This commit fixes an issue in the qpy dump() function's use_symengine kwarg. When a user provided a truthy value that wasn't the literal `Truth` boolean object the generated qpy payload would be corrupted. That's because the check that assigns the encoding key in the file header was unecessarily checking for the literal ``True`` object instead of a object that evaluated to true. This was causing the header to say it was using a sympy encoding, but then all the checks that were encoding the data were evaluating true and setting symengine data. This would cause a failure on reading the qpy payload when the parameter expressions were parsed as it would try to load the binary symengine encoding with the sympy parser. (cherry picked from commit 21be91c06) Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
58822 of 65937 relevant lines covered (89.21%)
188584.73 hits per line
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 7813908573.1 | 816 |
89.21 |
GitHub Action Run |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|