Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Realtime reporter produces no output #985
Comments
|
This is not a framework bug. It's caused by the SQL Developer extension. The consumer thread must be started before the producer thread to avoid this behavior. |
|
I'm re-opening this issue based on the discussion in JetBrain's DBE-9671 and in Slack. In the meantime I consider this a utPLSQL framework bug based on the following code in ut_output_buffer_base
If the producer and the consumer session run the The workaround until now is to start either the consumer or the producer with a short delay (e.g. 100ms). As long as the query on the However, we can do better and make it work without enforcing the consumers to apply a delay when starting producers and consumers. One way to solve it is to lock the table
Since all transactions on this table are very short, |
Describe the bug
Running the realtime reporter from the SQL Developer extension produces sometimes no output due to a
ORA-00001: unique constraint (UT3_LATEST_RELEASE.UT_OUTPUT_BUFFER_INFO_TMP_PK) violatedProvide version info
Information about client software
utPLSQL for SQL Developer 1.0.0 (or current development version)
To Reproduce
initializing...message forIn the SQL Developer logs I find the following:
as a consequence of this failure the consumer thread does not find result rows.
Expected behavior
Repeat test runs without technical issues.