-
-
Notifications
You must be signed in to change notification settings - Fork 5
Add test attempting to reproduce "Affixes" field error with affix morph types #2109
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
base: develop
Are you sure you want to change the base?
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
Added tests to pinpoint which morph types and entry configurations cause issues with complex form components. Tests cover: - All morph types with components - Affix morph types as components - Affix morph types with both components and complex forms These tests help identify the specific conditions that trigger the "Affixes" field error. Co-authored-by: myieye <[email protected]>
Added more targeted tests to identify the "Affixes" field error: - Tests for adding components to existing affix entries - Tests for using affix entries as components - Tests verify back-references are created correctly All targeted tests pass individually, indicating the error is specific to random data combinations in CanSyncRandomEntries test. Co-authored-by: myieye <[email protected]>
|
@copilot I think there's likely a combination of morph type and component/complex-form relationship (the Morph Type of both the component and complex-form are likely relevant) that consistently triggers this exception. I'm not looking for lots of tests I just want 1 simple test that triggers the exception. Try again. |
…ld error Simplified to one test that attempts to reproduce the error with an affix MorphType (Prefix) entry having both components and complex forms. Test currently passes, indicating the error requires additional conditions not yet identified in the random test scenario. Co-authored-by: myieye <[email protected]>
Replaced all tests with a single focused test ( However, the test passes consistently, indicating the error requires additional conditions beyond what I could identify. The original error showed The intermittent nature of the failure in the random test suggests it may depend on:
Would you be able to provide more details from a failing test run (e.g., the actual entry data that triggers it, or a seed value for the random generator)? Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
The
CanSyncRandomEntriestest fails intermittently withLcmInvalidFieldException: Fieldname 'Affixes' does not existwhen entries with certain morph types have complex form components.Root Cause
LibLCM bug:
LexEntry.get_VisibleComplexFormBackRefs()attempts to access an "Affixes" field that doesn't exist for entries usingIMoAffixAllomorphinternal structures (affix morph types: Prefix, Suffix, Infix, Circumfix, Simulfix, Suprafix, *Interfix variants).Note: The original error showed
MorphType = Enclitic, but Enclitic is actually treated as a stem type in the codebase, not an affix type. This suggests the error conditions are more complex than initially understood.Changes
Added a single targeted test method to isolate triggering conditions:
CanCreateAffixEntryWithComplexFormComponents: Tests affix MorphType (Prefix) entry with both components and complex formsTest currently passes, indicating the error requires additional conditions not yet identified, likely:
Next Steps
This is a LibLCM library bug requiring either:
The test provides a foundation for reproduction once the specific triggering conditions are identified.
Original prompt
This section details on the original issue you should resolve
<issue_title>CanSyncRandomEntries failure: Fieldname 'Affixes' does not exist</issue_title>
<issue_description>Note that this occurred when testing the FwData API and using the FwData API for round-tripping.
I assume it has something to do with Morph Types.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.