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

"gsec display" only shows some first users when there are many users (>50) in security database [CORE1680] #2105

Closed
firebird-automations opened this issue Jan 9, 2008 · 14 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

When security database is big enough, gsec display output is terminated too early, often with some garbage in last line.

Commits: 7a19a66 7137e23 4531c4d 0e99b07 e488a74

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

The bug was showing itself when >2 buffers of data were received from server.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 2.1 RC1 [ 10201 ]

Fix Version: 2.0.4 [ 10211 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 13805 ] => Firebird [ 14117 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @pmakowski

I test this under windows, for 2.1 it is ok

for 2.0.4 snapshot (2008-02-28 02:18:01 Firebird-2.0.4.13100-0_win32.zip)
if I make a display, all is displayed ok, but gsec quit
(21 users with fname,lname, mname)

@firebird-automations
Copy link
Collaborator Author

Commented by: @pmakowski

with 21 users with fname,lname,maname, under Win32 with the snapshot build (2008-02-28 02:18:01 Firebird-2.0.4.13100-0_win32.zip), gsec display is not garbaged, but gsec quit without any warning.

(the 2.1 version is ok)

@firebird-automations
Copy link
Collaborator Author

Modified by: @pmakowski

status: Resolved [ 5 ] => Reopened [ 4 ]

resolution: Fixed [ 1 ] =>

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

I've fixed an issue in 2.0.4 and HEAD. Do not htink it's worth having one more cycle in 2.1.0, therefore added to be ported to 2.1.1.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Reopened [ 4 ] => Reopened [ 4 ]

Target: 2.1.1 [ 10223 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

Fix Version: 2.5 Alpha 1 [ 10224 ]

Fix Version: 2.1 RC1 [ 10201 ] =>

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Last byte of data, returned by service, was tragically lost.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Reopened [ 4 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1.1 [ 10223 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Fix Version: 2.1.0 [ 10041 ]

Fix Version: 2.1.1 [ 10223 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment