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
Unknown tag (0) in isc_svc_query() results [CORE6396] #6634
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffreporter: Alexander Peshkov [ alexpeshkoff ] => Pavel Zotov [ tabloid ] |
Commented by: @aafemt Right patch for this ticket:
|
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 RC 1 [ 10930 ] Fix Version: 3.0.7 [ 10940 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Cannot be tested |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] Test Details: First time it was found in LI-V2.5.8.27072 and 2.5.9.27117. Number of attachments did not matter but trace .conf must contain almost all options with include status = true. Bug can not be reproduced in normal time: at least 25 minutes required for this, without 100% warranty that this error occurs. |
Submitted by: @pavel-zotov
Is duplicated by CORE5882
When running trace from fbsvcmgr sometimes (rather rarely) it fails with error message:
Unknown tag (0) in isc_svc_query() results
Commits: 2a75646 a4e79bb 422f382
====== Test Details ======
First time it was found in LI-V2.5.8.27072 and 2.5.9.27117. Number of attachments did not matter but trace .conf must contain almost all options with include status = true.
Discussed with Vlad and Alex since 13.12.2017; resumed 19.09.2018; 20.11.2018; 23.11.2018 (catched additional debug info, got explanations from Alex); 11.02.2019.
Bug can not be reproduced in normal time: at least 25 minutes required for this, without 100% warranty that this error occurs.
The text was updated successfully, but these errors were encountered: