Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
Content-Length: 280254 | pFad | http://github.com/python-gitlab/python-gitlab/discussions/3200
73
Fetched URL: http://github.com/python-gitlab/python-gitlab/discussions/3200
Alternative Proxies:
Uh oh!
There was an error while loading. Please reload this page.
-
According to https://python-gitlab.readthedocs.io/en/stable/gl_objects/pipelines_and_jobs.html#id6, the result of
.trace(streamed=False)is/are "entirely stored in memory in this example".I believe similar behavior can be achieved via
iterator=True, though without callbacks.The function
python-gitlab/gitlab/utils.py
Lines 69 to 89 in 5a4acab
even though it uses
response.iter_content, which could supportdecode_unicode=True(def iter_content(self, chunk_size=1, decode_unicode=False):), but there is currently no way to pass that downward.The result is a binary stream, which is unworkable as-is for line-based operations - as I "expect"/process the Job Log as a line stream (e.g. match this, ignore that ...). This also mirrors "average Joe's processing" of a job log: Go through it line-by-line, search etc
Not a blocker - just wondering if there is a more elegant, in-library workaround (or solution I have missed).
... or "food for thought" if development is due to happen.
Beta Was this translation helpful? Give feedback.
All reactions