Geir Ove Grønmo
- Total activity 292
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 124
Comments
Recent activity by Geir Ove Grønmo-
Official comment Yes, that would definitely be useful. We also have plans for extending the metrics API with information like this.
-
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...
-
Official comment That makes sense and it is a reasonable thing to do. We'll see what we can do.
-
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...
-
Official comment Agreed. We'll also add support for string arguments to the `ni-ns` function as it is similar.
-
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...
-
Changelog: https://docs.sesam.io/changelog.html#changelog-2022-10-11
-
Official comment We have had discussions about how to improve the pipe progress status in the UI. This is a fairly major effort, but it is clearly something that would be very useful. We intend to make improvements...
-
Official comment Indeed. It it unnecessary to retry requests that returned 4xx as these are client side problems. We'll look into how we can handle this.
-
Official comment Yes, we already have this on our planning board. We'll add a warn to pipes where hops are used, but dependency tracking won't be guaranteed or done. Another example is if the pipe source is not a ...