Stavros Ntentos

Seems the issue here is "obvious": From the server, a bunch of ```py 2024-02-01 00:46:01,928 doing a full keyboard reset, keys now pressed={50: ['Shift_L', 'ISO_Next_Group'], 64: ['Alt_L', 'ISO_Next_Group']} 2024-02-01 00:46:01,931...

> So I prefer we close this issue as "not planned" Then please do so :pray: Don't close it as "completed"

> Is there a reason why you chose a different location ('/usr/share/keychain') for the key than in the article? > > It seems to me like '/usr/share/keyrings' has become the...

It would be nice for mypy to explicitly note that somewhere here: `"""Note that, for ``FORCE_COLOR`` to work, there needs to be a suitable ``TERM`` in the enviroment!"""` https://github.com/python/mypy/blob/ff81a1c7abc91d9984fc73b9f2b9eab198001c8e/mypy/util.py#L511-L516 `TERM=ansi`...

_Pls don't forget the `py.typed` marker_ 🙏 Also, partial stuff (like merging this MR) is better than no stuf Also related to https://github.com/benoitc/gunicorn/issues/2833?

That is ... very respected ❤️

Oh ... Haven't tried the `streamed=` 😅 Then, _at least_ ` | bytes` is also needed?

Actually ... even worse? 😅 😅 ``` In [4]: a = job.trace(streamed=True) b'\x1b[0KRunning with gitlab-runner ...ERROR: Job failed: command terminated with exit code 1\n\x1b[0;m\n' In [5]: repr(a) Out[5]: 'None' ```...

Apologies for the "necrobump" and the @nejch -bump :sweat_smile: I am having the same issue in `gitlab --version 4.4.0`. ``` $ gitlab --debug project-merge-request-discussion list --project-id ./. --mr-iid 14254 DEBUG:urllib3.connectionpool:Starting...

Yeap :confused: That's it Can you please make `gitlab.Gitlab` a bit more strict it what it accepts? And/or check early if "it's valid" or not? ... do you want a...