You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
User in Swarm noticed that the time range for a channel is not correct sometime (see usgs/swarm#218). I have not been able to reproduce. It appears the min/max times come from Winston's Channel.timespan, which is through Winston client's channel handler. So far it's not clear where this can go wrong without being able to reproduce.
The text was updated successfully, but these errors were encountered:
I've looked at the swarm issue, but I'm still not clear on the problem. It looks like maybe a channel is Swarm is greyed out when it should not be and the dates shown in the tooltip are incorrect. Is that what's going on? Can you point me to a wave server where I can duplicate the problem?
@jpesicek anything special about the environment you're running swarm in?
Your description of the problem is correct, but I cannot find an example currently. It happens once in a while, but I do not know the circumstances that cause it. Perhaps large data gaps somewhere are causing bad dates?
nothing special about my environment that I know of.
On Jul 24, 2019, at 4:08 PM, Tom Parker ***@***.***> wrote:
I've looked at the swarm issue, but I'm still not clear on the problem. It looks like maybe a channel is Swarm is greyed out when it should not be and the dates shown in the tooltip are incorrect. Is that what's going on? Can you point me to a wave server where I can duplicate the problem?
@jpesicek <https://github.com/jpesicek> anything special about the environment you're running swarm in?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#70?email_source=notifications&email_token=AE7SDZ2KBV33R2NKBOMXPZTQBDOHJA5CNFSM4HCDL62KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2X3LWA#issuecomment-514831832>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE7SDZ53JASB7AGWV54XIULQBDOHJANCNFSM4HCDL62A>.
I'll leave this open, but I don't know where to start trying to replicate the problem. I'll ask AVO folk to be on the lookout for it. If you notice this again, point me in the right direction to see it in action.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
User in Swarm noticed that the time range for a channel is not correct sometime (see usgs/swarm#218). I have not been able to reproduce. It appears the min/max times come from Winston's Channel.timespan, which is through Winston client's channel handler. So far it's not clear where this can go wrong without being able to reproduce.
The text was updated successfully, but these errors were encountered: