-
Notifications
You must be signed in to change notification settings - Fork 109
feat(loader): update loading logic & enhance failure case #704
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
Changes from all commits
1463d64
528f12e
3503b08
9683b47
d3fa860
cd92e05
80d1544
d37cb4e
ca92b2a
8a487f5
0b965c6
a432785
171a988
f062624
866a4a0
ceaed28
e39f503
eda716e
71644b6
78fa442
ee496dd
0379118
572cc94
a54eb64
537445c
6f663c7
18e83cf
dddfa40
ed816e3
1831893
588adad
f60d5a1
3706a3b
c328a01
146bdf4
1af9a32
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -1197,7 +1197,9 @@ public void testMultiFilesHaveHeader() { | |||||||||
| "-s", configPath("multi_files_have_header/schema.groovy"), | ||||||||||
| "-g", GRAPH, | ||||||||||
| "-h", SERVER, | ||||||||||
| "--test-mode", "true" | ||||||||||
| "--test-mode", "true", | ||||||||||
| // FIXME: Set parser-threads to 1 because values > 1 currently trigger a NullPointerException (NPE). | ||||||||||
|
||||||||||
| // FIXME: Set parser-threads to 1 because values > 1 currently trigger a NullPointerException (NPE). | |
| // FIXME [HUGEGRAPH-XXXX]: Using parser-threads > 1 currently triggers a NullPointerException (NPE) | |
| // when loading multiple CSV files with headers in parallel. Limit to 1 thread here as a temporary | |
| // workaround to keep this functional test stable until the underlying concurrency bug is fixed. |
Copilot
AI
Jan 21, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The FIXME comment indicates that setting parser-threads to values > 1 triggers a NullPointerException (NPE). This suggests that either: (1) the new default value of parser-threads (max(2, CPUS/2)) may cause NPEs in these test scenarios, or (2) there's an existing bug that's being worked around. If this is a new bug introduced by changing the default value, it should be fixed before merging. If it's an existing known issue, the FIXME should reference an issue tracker number and explain why it's acceptable to work around it in tests.
| // FIXME: Set parser-threads to 1 because values > 1 currently trigger a NullPointerException (NPE). | |
| // Set parser-threads to 1 to avoid a known NullPointerException (NPE) when using multiple parser threads in this scenario. |
Uh oh!
There was an error while loading. Please reload this page.