-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added timeout functionality for pathway summary. Related to #2362. #977
Added timeout functionality for pathway summary. Related to #2362. #977
Conversation
@@ -173,7 +173,7 @@ define([ | |||
return p + '=' + query[p]; | |||
}).join('&'); | |||
|
|||
return when(request.post(_self.apiServer + '/pathway/', { | |||
return when(request.post(_self.apiServer + 'pathway/', { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JacobPorter Can you put these slashes back in for consistency? It doesn't look like there's a trailing slash in the configs on the servers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The apiServer string ended with a slash, so that is why it was removed. I can put it back in if you like since it won't hurt anything, but then there will be two slashes.
This depends on how it was defined in the config file. I suspect your local dev env doesn’t have the trailing slash defined as part of that api server url, but in the dev/production environments they do. So one of these things needs to happen: a) how it is defined in configs needs to be consistent between dev/production or b) there needs to be some code that normalizes what is provided in the config (to not have the slash), or c) there needs to be a joiner used to construct these paths that takes the slash into account (this will have to be modified all over the place).
… On Jun 25, 2020, at 12:30 PM, Jacob Porter ***@***.***> wrote:
@JacobPorter commented on this pull request.
In public/js/p3/store/PathwaySummaryMemoryStore.js <#977 (comment)>:
> @@ -173,7 +173,7 @@ define([
return p + '=' + query[p];
}).join('&');
- return when(request.post(_self.apiServer + '/pathway/', {
+ return when(request.post(_self.apiServer + 'pathway/', {
The apiServer string ended with a slash, so that is why it was removed. I can put it back in if you like since it won't hurt anything, but then there will be two slashes.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#977 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABOQ3X4H3O533NOKVCV5ALRYN3UFANCNFSM4NVEZDYA>.
|
@dmachi I likely sent @JacobPorter my local config that did have a trailing slash. I'm now looking at the default config https://github.com/PATRIC3/p3_web/blob/master/config.js and the
[Note the other "dataAPI", "serviceAPI", "workspaceAPI" urls too] I don't think the extra slash actually hurts anything? Or, there's also the |
@JacobPorter thanks, and sorry for the confusion. I'm partly operating on "if it ain't broken, don't fix it" for a couple weeks, and maybe we'll have maintenance time to address some of these issues. |
When a pathway summary query timeouts, the circular wait widget is removed, and then an alert and message is produced that says, "The query took too long or could not be loaded."