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

ValueError: not enough values to unpack (expected 3, got 1) #2

Open
DmEye opened this issue Feb 8, 2023 · 0 comments
Open

ValueError: not enough values to unpack (expected 3, got 1) #2

DmEye opened this issue Feb 8, 2023 · 0 comments

Comments

@DmEye
Copy link

DmEye commented Feb 8, 2023

I have a fbtrace_text file and I want to parse it by trace.py. But the error "ValueError" occurs when I parse my file. I changed some code in trace.py to see what problem is. So, the function "_parse_transaction_info" tries to parse the line "-------------------------------------------------------------------------------". I looked for the reason of it and found the next content of my trace file:

Statement 482:
-------------------------------------------------------------------------------
SELECT MON$DATABASE_NAME FROM MON$DATABASE

2023-02-06T12:01:58.9220 (12598:0x7f6f1d531bc0) PREPARE_STATEMENT
	employee (ATT_76, SYSDBA:NONE, NONE, TCPv4:127.0.0.1/54122)
	/opt/firebird/bin/isql:12834
-------------------------------------------------------------------------------

In this part of trace file there is not any information about transaction number, options and so on but trace.py tries to parse anyway.

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

No branches or pull requests

1 participant