Geir Ove Grønmo
- Total activity 268
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 114
Activity overview
Latest activity by Geir Ove Grønmo-
Geir Ove Grønmo commented,
This has now been implemented. See https://docs.sesam.io/hub/changelog.html#changelog-2023-05-02
-
Geir Ove Grønmo commented,
Official comment That's a very good idea. We'll implement that.
-
Geir Ove Grønmo commented,
Official comment Yes, we've been aware of this limitation for a while. We are currently working on implementing support for getting only the latest versions of entities out of a subset. A dataset source with a subs...
-
Geir Ove Grønmo commented,
Official comment Yes, that would definitely be useful. We also have plans for extending the metrics API with information like this.
-
Geir Ove Grønmo commented,
Official comment The "Pipe is not ready: " part of the message is just to indicate that the pipe wasn't able to run. I guess using "The pipe cannot run now:" might be better?It is possible to see the pipe queue siz...
-
Geir Ove Grønmo commented,
Official comment That makes sense and it is a reasonable thing to do. We'll see what we can do.
-
Geir Ove Grønmo commented,
Official comment Interruption of threads is cooperative in most programming languages. That means that the thread will actually have to check if it has been interrrupted, and if it has then stop. Unfortunately a lo...
-
Geir Ove Grønmo commented,
Official comment Agreed. We'll also add support for string arguments to the `ni-ns` function as it is similar.
-
Geir Ove Grønmo commented,
Official comment Rescans use the same logging logic as all full syncs. They only log pump runs if there were actually any changes. You can opt-out of the default behaviour by setting `log_events_noop_runs` and `log...
-
Geir Ove Grønmo commented,
Changelog: https://docs.sesam.io/changelog.html#changelog-2022-10-11