Bug report: Application crashed with InvalidRequestError
Opened this issue · 1 comments
Automated report
This issue was created with the app's automated bug reporting feature.
Attached to this issue is the full traceback as well as an environment
fingerprint that contains information about the operating system as well as all
installed libraries.
Additional comments (optional):
I opened an old calculation, went to PDOS, and selected orbitals, the different orbitals type labels do not appear (e.g. remains C instead of C2px and if I click on a PDOS channel it crashes)
Attachments
Traceback
/opt/conda/lib/python3.9/site-packages/aiida/storage/psql_dos/orm/utils.py in __getattr__(self, item)
80
81 if self.is_saved() and self._is_mutable_model_field(item) and not self._in_transaction():
---> 82 self._ensure_model_uptodate(fields=(item,))
83
84 return getattr(self._model, item)
/opt/conda/lib/python3.9/site-packages/aiida/storage/psql_dos/orm/utils.py in _ensure_model_uptodate(self, fields)
159 :param fields: optionally refresh only these fields, if `None` all fields are refreshed.
160 """
--> 161 self.session.expire(self._model, attribute_names=fields)
162
163 def _in_transaction(self):
/opt/conda/lib/python3.9/site-packages/sqlalchemy/orm/session.py in expire(self, instance, attribute_names)
3260 except exc.NO_STATE as err:
3261 raise exc.UnmappedInstanceError(instance) from err
-> 3262 self._expire_state(state, attribute_names)
3263
3264 def _expire_state(
/opt/conda/lib/python3.9/site-packages/sqlalchemy/orm/session.py in _expire_state(self, state, attribute_names)
3267 attribute_names: Optional[Iterable[str]],
3268 ) -> None:
-> 3269 self._validate_persistent(state)
3270 if attribute_names:
3271 state._expire_attributes(state.dict, attribute_names)
/opt/conda/lib/python3.9/site-packages/sqlalchemy/orm/session.py in _validate_persistent(self, state)
4136 def _validate_persistent(self, state: InstanceState[Any]) -> None:
4137 if not self.identity_map.contains_state(state):
-> 4138 raise sa_exc.InvalidRequestError(
4139 "Instance '%s' is not persistent within this Session"
4140 % state_str(state)
InvalidRequestError: Instance '<DbNode at 0xffff758f9ca0>' is not persistent within this Session
Environment fingerprint
eNptWNty4zYS_RWX8hqyRFKXsd8mfkuNd2fXk6S2tlIqkIQoWCAAE6BlOjX_nkZ3Q0JSedQBCPT19IH- WL3JyStrVg_VjyunRTjaaVw9_LESU3dSQXZhnuTq4f-r3aZVYfXjavU77FvCyZrD9dNVU96XVQOrN- iH6u756evdkzV3n-fhrqrv1p8eNvuHdXX3y7fHu3pdb1bf4SjRncUgPV6pVC-KzsYLV3W5K2s4kUDn5dxbgKtyW66v8OssTJhH6d 0kvY_rG_jstn4Rxig53a_xwPqfVoqLnc5HbS8e9zS3PVq0EdqAbzl2kDr6ty6rssnhkx3lP-5_Zbhal2tR5SsX1Q8y-EMrvEy3C3 LaFk6dBYC78lNJH0FiXjHWDQFajq3qMCa8xRgbRJB9ERYXQwpG7skW41V9CqPG3fcUWLMoi-ft6GvnejV53LEpN4SMtpd4zic6Jx bFmyycCCeEN3TUNFhTF93xqKIbVYriDS5aZXplBk_rnAn0uinrmgzwIdizNJQIuBKxxXSHQRo5iWAnNK7Cb0NAW-O3eNhPopUav4 Q4x8S0UFmd0BrtpAsj5OwUfHmcTRes1b7Q01x0ojtJPHuHjrfdtLiA1cQfSjEHdZy1t7Pb4EJVodGtlvAxIFCWDChzlmTpNv4Gl0 5o14bMmmzQyi1Zdh7j9Y_WhMmStRVlGM1CK9mUDYLJc9iE0e_kBLZh5KGpIFPNOqF8DcWX0wN2b-n3SUxehsJAYQmtPtDoGE5alK MyR8snUEl3aupmqquKCqLTqjsDAAVY7tPvwjtlDB4XuwTz1VltJzEKrpotQqYXlEI-PgIFM0JxEqaHWA5csrwh2HlCm1KRYarsMA l3inADdlGclk4nE8j_XrbzwN_uMBe9BLLhutqy4708zl7276PmDBEIBAORJ2pLJdcrfz7Y9gVI0gdirVTavfFEkrid0tzbzocJPD q4GHi2bRdXZn1RHXUUN4OE7pYmcKNtmPXkKJQ- vEG2ejY7sRrshUBYZQLlJ4ZAvnfSRZuHCcqWratxQXZQzxxb8vsI7ffirfEx84K8JAY-Ki21xTQ3EcPdWoUDM3XDQTpCdm7Vut0Q ONMAgXvWaCgQXsFEBZZxMeE9mMM39UFhoCYeJimNloENjdBpHoU5TkpCeWAy6VzVG4HGRM_VGNtcq7YYZRAQK2LStPW6ClMD6qlD rtxel90CDWyQTXbRYQYtxHIUzId1QjnJ-7LZ5FABnAUh1v5vu8EfRmpCeAbgEXsy_goW8j2Am7LP8qSC74UZJKTUZ_l_kb1KjRm3 _azMC4wSTBle9WKBmVpmdwQg2Vtu7i3_viZ_k_x-mcFoOR2gsaHEyFHanhaoCK6EyHgBBf7GNFjd_2UlYG1DuXLus2tOc4smr3OQ 5jAkFifCDSzcMsQe8VlAb6uHqwF1JLy_Ld6iXiWGOqvLjZb3DHirkxcbBLWYzlkngWCCLoMh2WV2Q5xHMbaCuYbYVtthnmY- Pn76JM6WT4pljV9k-5_got5eSF3tGZjdszjKjKZHEZyOA6VlFVb_BSyUAQqVHOhINaPyYTaSR2wstxHadknDY0_DY4SkFqD-ptTP UFRU3qMbiZIS_45-iIzNkURk1kH1qgvUP4gZETz0HJ5EB5m208J7FDBpIkSMyyzNRoCsgRRQ6RE3mjaKVBGwaYmPjPRAK1EsqKQS dwiHKO_eSWbQzkG_KXnhdMWKAi6SrbVnNBfquM6wwp_UmNWpmUfOak1SwYIwOKXw0w0ZT0TSi3bQTCPCrYnGHOi3EAToB9Z0BI5S i4wtAXh1mTB1MBRF6vuGAdsBRUOyfKaPYcSIUWGF1XEAMoYaOao5_Fa-O9mRzqFx7gY_czdF5xwMcy096ATJKdkiqkEuE_NSLr8q zlmNxypHgjcG0p2HSIOHyLTQSgcjRsnVg12XnhwsPUEjUcBi_S6Y4JoGidMceriFtIbDDXAOLk8gv8NJzr7Iaqjib2HRhSIW81kF Tn2DKz5ah_dQ7zi_dNYNNcbtvrzPoKhhBbLWdQV09mRhfORa28G8KyTM6IyW3NICTxDAIVse1fG_v6HLG3IZbvGC7CZ5AshVKcA5 FUHzpLEXNsQTboFxELCN6uQDQ4frU6qmsZgWgJxDSGq8JHL8eiPTOgpQMvLn377xHnRtga6DwXaTmve462l5_s8XHiUNIv8Sjzqv xuXfTprn5y-5YndL9I6aIiYEI7oA4sM1fzTMvi7PoD-ovPfsNQ5ZmOySE1iDNXW2Ag1s3riTsi_ilCuAiweO6nXRvnRidFmrx2Et qOBS9MIHeV6xl__7_PQFWWPNV3_gCy2mGI99lUUi0DSnJ_k6A1fxY5N6OGHZO4SYZJojH5SLYDFa7akKMrzsiHxipe2uS0VcKpLA XscB-Cne7jvF9MVPDC_l2SVCv8e28nKkkdewW88gQepvk_AnfmviSTLMLjm325bUaP4EJD_Pqk-Bj-559U5XkqLwRsFDxGYjJD6q vJJv6Q1cl876gOe5gdxLFQh19llHkbJw9prISD4AvxYs89Y8QP0y3nyNdgDZznFeZw8aqBHRKRx_98y4wKPw8BG9ZXlOoDJL532d 6bBgU1IoSvG3ykoqxuYjPT_wDDvxsSSrw2s_0h8WFDuoNhU0iZJtsm9x8b2AMtCzXI4Tig74YI-xFyMyx- rOpSy8cmF0CqBnhRq3YT6a3fEQ7IG3JwUIzHJ7DLLmaQiHLDRp7CHf_ipAQy-Zer-I0J16O6CFFIJLBzKL_yio8YaLbKUBucTck1 IFsIcGh5fBlbsrrqjLSUqKc0OdT8rt4OSkbBQZ1wlaZcvetNeY8V8caCO8MEJei_DKy947ZMwiJp23yIdyjsXVevX9-5-lsm9s
By submitting this issue I confirm that I am aware that this information can
potentially be used to determine what kind of calculation was performed at the
time of error.
Hi @cpignedoli , thanks for reporting this issue. I can reproduce it.
The issue is because, after PR #844 , the result panel is run inside the process monitor, which is run in another thread.
I need to think about how to solve it. The worst case, is that we don't support this #822 .