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
{{ message }}
Repository navigation
ORAS publishing errors not being fully displayed #1115
When publishing to an OCI/ORAS repo, a 401 bad credentials error is being truncated and lost. It manifests as ERROR! Unable to push <PYTHON EXCEPTION> 246 <class 'ValueError'>: Issue retrieving session url: {'errors': which is unhelpful as the actual error is missing.
When the actual error message is saved to a debug global, the missing information is present. So somehow somewhere it is being truncated. ^mtempdc(7463.984942,"errMsg")="ValueError(""Issue retrieving session url: {'errors': [{'status': 401, 'message': 'Bad Credentials'}]}"")"
To Reproduce
Unfortunately I've been unable to reproduce this so far.
Expected behavior
Python errors should be properly displayed to the user. 401, 403, and 404 errors should also maybe get special handling. (This would likely be a good workaround trying to reproduce the full error.)
System information (please complete the following information):
IPM version: 0.10.6
IRIS version: Unknown
OS: Linux
Docker or local: Docker
Dev notes
Look at the %IPM.Repo.Oras.PublishService class, especially the Push() and PushOras() methods.
Note that this truncated error messaging also occurs when an incompatible Python version is installed (because that will only throw warnings and not fail IPM install itself), and certain commands are run. In general we should properly propagate Python errors to the user.
To properly propagate python errors, we may want to consider moving all of our Language = python references to external .py files and use %SYS.Python since that is the recommended approach to using embedded python
Rough idea:
IPM .py files should be <FileCopy>'d to /mgr/ipm/<version>/python and then IPM code calls into %SYS.Python.Import with the constructed full path
Activity
isc-dchui commentedon Apr 10, 2026
Note that this truncated error messaging also occurs when an incompatible Python version is installed (because that will only throw warnings and not fail IPM install itself), and certain commands are run. In general we should properly propagate Python errors to the user.
isc-kiyer commentedon Apr 10, 2026
To properly propagate python errors, we may want to consider moving all of our Language = python references to external .py files and use %SYS.Python since that is the recommended approach to using embedded python
isc-dchui commentedon Apr 20, 2026
Rough idea:
IPM .py files should be
<FileCopy>'d to/mgr/ipm/<version>/pythonand then IPM code calls into%SYS.Python.Importwith the constructed full pathisc-dchui commentedon May 19, 2026
Users keep bumping into very unhelpful python exceptions so priority of this should be bumped.