Gergely Kalmár

Perhaps I could write it up, but it might take some more time then. As you're building on ``distutils`` I guess I would need to [dig a bit](https://github.com/pypa/setuptools/blob/master/setuptools/__init__.py#L153) to make...

It's not a very friendly interface to type hint though with all the ``**attrs`` catch-alls (https://github.com/python/cpython/blob/master/Lib/distutils/core.py#L57).

That would have been my idea too. I'm pretty busy at the moment though and so I'm not sure I'd get to it anytime soon!

It might be useful to add that in the meantime stubs were developed in typeshed: https://github.com/python/typeshed/pull/5762 It seems to be ready to be released, once it is released I think...

This indeed does work well, thank you! Could we consider to make this the default option? I've found it to be quite useful to see which plugin a given failure...

That all makes perfect sense, however, why make this change then before https://peps.python.org/pep-0740/ is accepted and implemented? If I understand you correctly there seems to be no way currently to...

I seem to have the same issue, or, well, at least some issue that looks similar. I also have three monitors, they are all aligned on the top in this...

Not sure if related, but I'm also seeing the following error appear three times in the logs when switching: Jul 6 11:22:32 flux gnome-shell[38619]: JS ERROR: TypeError: this._settings is null#012_sync@resource:///org/gnome/shell/ui/dateMenu.js:525:28#012_updateCount@resource:///org/gnome/shell/ui/dateMenu.js:521:14#012countUpdated@resource:///org/gnome/shell/ui/messageTray.js:788:15#012_onNotificationDestroy@resource:///org/gnome/shell/ui/messageTray.js:831:14#012destroy@resource:///org/gnome/shell/ui/messageTray.js:515:14#012destroyNonResidentNotifications@resource:///org/gnome/shell/ui/messageTray.js:901:39#012_onFocusAppChanged@resource:///org/gnome/shell/ui/notificationDaemon.js:349:24#012changeFocus@/.../.local/share/gnome-shell/extensions/focus-changer@heartmire/extension.js:34:27#012_bindShortcut/

@yarinb Did you manage to find a workaround? We're seeing the exact same behavior in AWS MSK.

I think that this is configurable via the MSK Connect worker configuration: ``` key.converter=org.apache.kafka.connect.storage.StringConverter value.converter=org.apache.kafka.connect.storage.StringConverter config.providers=secretManager config.providers.secretManager.class=com.github.jcustenborder.kafka.config.aws.SecretsManagerConfigProvider config.providers.secretManager.param.aws.region=us-east-1 config.providers.secretManager.param.secret.ttl.ms=86400000 ``` Note the added `config.providers.secretManager.param.secret.ttl.ms` value (changed to 1 day in...