Skip to content
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

isc_info_svc_get_users returns error message in the result cluster [CORE3220] #3594

Closed
firebird-issue-importer opened this issue Nov 8, 2010 · 9 comments

Comments

@firebird-issue-importer
Copy link

@firebird-issue-importer firebird-issue-importer commented Nov 8, 2010

Submitted by: @AlexPeshkoff

Attachments:
test_get_users.zip

Bug was reported in devel by Cosmin Apreutesei.

When trying to request a just-created user I
get the error directly in the cluster, starting directly with the
error message. Is this a bug? If not, how can I parse this cluster?

This btw only happens with firebird 2.1.3 (2.5 doesn't do this), and
only immediately after I add the user TEST_USER with the following
parameters:

			isc\_spb\_sec\_username    = 'TEST\_USER',
			isc\_spb\_sec\_password    = '1234',
			isc\_spb\_sec\_firstname   = 'Test',
			isc\_spb\_sec\_middlename  = 'W',
			isc\_spb\_sec\_lastname    = 'User',
			isc\_spb\_dbname          = user\_db\_file,

This is the byte array I get (starting with code 68 which is
isc_info_svc_get_users, and ending in 1 which is eof -- the cluster
size is also right: 127 bytes).

68 D
127 �
0
114 r
101 e
99 c
111 o
114 r
100 d
32
110 n
111 o
116 t
32
102 f
111 o
117 u
110 n
100 d
32
102 f
111 o
114 r
32
117 u
115 s
101 e
114 r
58 :
32
84 T
69 E
83 S
84 T
95 _
85 U
83 S
69 E
82 R
10

7
6
0
83 S
89 Y
83 S
68 D
66 B
65 A
10

3
0
83 S
113 q
108 l
11
6
0
83 S
101 e
114 r
118 v
101 e
114 r
12
13

0
65 A
100 d
109 m
105 i
110 n
105 i
115 s
116 t
114 r
97 a
116 t
111 o
114 r
5
0
0
0
0
6
0
0
0
0
7
9
0
84 T
69 E
83 S
84 T
95 _
85 U
83 S
69 E
82 R
10

4
0
84 T
101 e
115 s
116 t
11
1
0
87 W
12
4
0
85 U
115 s
101 e
114 r
5
0
0
0
0
6
0
0
0
0
1

Commits: 54d2827 3c22228 eb5414a 1183e9c

====== Test Details ======

No errors using fdb, checked FB major versions (avaliable for me) since 2.1.3
Discussed with Alex, letter 21.02.2018 14:32

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 8, 2010

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 8, 2010

Commented by: @AlexPeshkoff

Bug takes place due to error message left in internal engine's buffer used to communicate with service thead.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 8, 2010

Commented by: @AlexPeshkoff

This test case helps to reproduce a bug

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 8, 2010

Modified by: @AlexPeshkoff

Attachment: test_get_users.zip [ 11812 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 8, 2010

Commented by: @AlexPeshkoff

Though bug did not show itself in fresh versions, cleaning up service output buffer is anyway correct idea.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 8, 2010

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1.4 [ 10361 ]

Fix Version: 2.5.1 [ 10333 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

Fix Version: 2.0.7 [ 10390 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 4, 2011

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 18, 2016

Modified by: @pavel-zotov

QA Status: No test

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 22, 2018

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested

Test Details: No errors using fdb, checked FB major versions (avaliable for me) since 2.1.3
Discussed with Alex, letter 21.02.2018 14:32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants