Jani Korhonen

> I'm guessing that it doesn't like trying so many times maybe I changed the `refreshInterval` to `1h` and now my `PushSecret` object has been staying at `synced` as far...

> @bthuilot ? :D I think their [comment](https://github.com/external-secrets/external-secrets/issues/3130#issuecomment-1975211927) about the race condition in that other thread _might_ be the reason for this issue. So fixing that might fix both of...

This issue was related to https://github.com/external-secrets/external-secrets/issues/3130 and got fixed at the same time as that one. There is more discussion in that issue too.

Or instead of it showing list view of the month it should show list view of upcoming events. Or events from today onward. That way it would be more usable...

Hmm... Apparently after running the shin engine I would need to re-enable `xkb:fi:classic:fin` with `ibus engine xkb:fi:classic:fin` to get them working again. I'm kinda unfamiliar with ibus though so it...

Actually now that I found out about this whole ibus thing I think I enjoy `xkb:fi:nodeadkeys:fin` more and it doesn't seem to break after running ` shin` :grin: So personally...

Actually seems to be: ```sh $ ibus engine xkb:us::eng ``` Running shin unsets the previous engine, and setting it back to what it was actually doesn't set something back up...

Would shin even have this information out of box since you start it by enabling engine `shin`? Then if `shin` would check the active engine, it would get `shin` as...

One addition to this issue btw. One thing that does break each time I activate shin even if I set `ibus engine xkb:fi:nodeadkeys:fin` initially is my CTRL + SHIFT +...

That is exactly how I'm running `shin` right now. And while I don't have any immediate problem with that I'm also not confident it's the way things should work by...