When argonaut server is configured but not answering, the wait is too long
Maybe we should have some timeout setting? The actual wait for the argonaut server is definitely too long, and happens too often, each time we edit a system there is the same wait, there should be some kind of cache for argonaut server state.
The same apply for argonaut client that are configured but not answering.
(from redmine: issue id 1406, created on 2012-10-22, closed on 2012-12-05)
- Changesets:
- Revision c8b66198 by Benoit MORTIER on 2012-10-23T08:49:13.000Z:
Fixes: #1406 When argonaut server is configured but not answering, the wait is too long
- Revision e4e9d806 by Benoit MORTIER on 2012-10-23T08:55:48.000Z:
Fixes: #1406 When argonaut server is configured but not answering, the wait is too long
- Revision 374a0b8d by Benoit MORTIER on 2012-10-23T09:44:22.000Z:
Fixes: #1406 When argonaut server is configured but not answering, the wait is too long
- Revision b074b119 by Benoit MORTIER on 2012-10-24T13:55:10.000Z:
Fixes: #1406 When argonaut server is configured but not answering, the wait is too long
- Revision ca852445 by Benoit MORTIER on 2012-10-29T16:05:57.000Z:
Fixes: #1406 When argonaut server is configured but not answering, the wait is too long
- Revision e473c816 by Benoit MORTIER on 2012-10-30T10:13:31.000Z:
Fixes: #1406 When argonaut server is configured but not answering, the wait is too long
- Revision d157902a by Benoit MORTIER on 2012-11-28T13:39:20.000Z:
Fixes: #1406 When argonaut server is configured but not answering, the wait is too long
- Custom Fields:
- Bug in version: 1.0.4
- Uploads:
- 0002-Fixes-1406-When-argonaut-server-is-configured-but-no.patch
- 0003-Fixes-1406-When-argonaut-server-is-configured-but-no.patch
- 0004-Fixes-1406-When-argonaut-server-is-configured-but-no.patch
- 0005-Fixes-1406-When-argonaut-server-is-configured-but-no.patch
- 0006-Fixes-1406-When-argonaut-server-is-configured-but-no.patch
- 0007-Fixes-1406-When-argonaut-server-is-configured-but-no.patch