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

Error in globalCallingHandlers when calling executeDqChecks #466

Closed
frasansa opened this issue Jul 2, 2023 · 3 comments
Closed

Error in globalCallingHandlers when calling executeDqChecks #466

frasansa opened this issue Jul 2, 2023 · 3 comments

Comments

@frasansa
Copy link

frasansa commented Jul 2, 2023

I encountered an error while using the executeDqChecks function from the DataQualityDashboard package. When I called the function, the following error (with traceback) occurred:

Error in globalCallingHandlers(condition = conditionHandler) : 
should not be called with handlers on the stack
5.
globalCallingHandlers(condition = conditionHandler)
4.
registerDefaultHandlers()
3.
getLoggerSettings()
2.
ParallelLogger::registerLogger(logger = logger)
1.
DataQualityDashboard::executeDqChecks(connectionDetails, cdmDatabaseSchema = "main", 
resultsDatabaseSchema = "quality_checks", cdmSourceName = "Synthea synthetic health database", 
outputFolder = "qc_results", cdmVersion = "5.3", sqlOnly = TRUE, 
sqlOnlyIncrementalInsert = TRUE)

I am using:
R version 4.3.1 (2023-06-16 ucrt)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build 19045)
DatabaseConnector_6.2.3

@katy-sadowski
Copy link
Collaborator

Hmm. This seems like it might be a ParallelLogger issue - could you please share what version of ParallelLogger you have installed? (Also - assume you're on latest version of DQD?)

@frasansa
Copy link
Author

frasansa commented Jul 3, 2023

Thank you, @katy-sadowski, for your message. I have installed ParallelLogger_3.2.0 and DataQualityDashboard_2.3.0. After further investigation, I found that the error only occurs when calling the function inside a quarto chunk, possibly due to a conflict with the error options configuration of Quarto in my R Studio environment. Fortunately, the error does not occur when running the .R script directly.

@katy-sadowski
Copy link
Collaborator

Interesting, OK, thanks for the update! I'll close this issue for now but please let me know if you experience further issues.

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

2 participants