You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally it would either create a new instance of the object, or return a reference to the existing object instead of the panic error.
The (likely) preferred approach should be to create the variable once and pass it around, but ideally i should be able to create a second reference to the object and use it the same as the first, or this would be documented if its not the anticipated behaviour.
I can't run this in a jupyter notebook as well without calling the BW client at the top scope either, otherwise subsequent calls raises the error.
Operating System
Windows
Operating System Version
10
Build Version
0.1.0
Issue Tracking Info
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Maybe I didn't compile correctly the fix or the fix doesn't help.
This is what I tried: #676 (comment)
I did cargo build in crates/bws as in the newest state of the main branch and then cargo install --path ., but what next? The lookup plugin still fails with a panic error as before.
Steps To Reproduce
when attempting to create the api twice in the same process, getting an error.
raises
Expected Result
Not raise an error, or return a reference to the existing object
Actual Result
Panic error raised.
Screenshots or Videos
No response
Additional Context
Ideally it would either create a new instance of the object, or return a reference to the existing object instead of the panic error.
The (likely) preferred approach should be to create the variable once and pass it around, but ideally i should be able to create a second reference to the object and use it the same as the first, or this would be documented if its not the anticipated behaviour.
I can't run this in a jupyter notebook as well without calling the BW client at the top scope either, otherwise subsequent calls raises the error.
Operating System
Windows
Operating System Version
10
Build Version
0.1.0
Issue Tracking Info
The text was updated successfully, but these errors were encountered: