Replies: 5 comments 10 replies
-
|
As @JacquesCarette mentioned in our meeting yesterday (#4087), we're reaching a point where we need to address the elephant in the room: the fundamentally different view on how chunks are formed. As per the wiki, in the past, chunks were formed in a Matryoshka style, where data was "attached" to smaller nuggets gradually by continuously wrapping around a chunk, with each one sharing the same With #2873, we are completely diverging from this. Each thing registered in the |
Beta Was this translation helpful? Give feedback.
-
|
Strictly speaking, for the conflicting |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
The majority of the " The vast majority of the remaining issues are now on a similar wavelength to our "t_0": [
"symbols",
"concepts"
],
"theory:accj": [
"instanceModels",
"concepts"
], |
Beta Was this translation helpful? Give feedback.
-
|
This was completed with #4465 being our latest PR needed to fixing up the conflicting |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Context: #2873
A "conflicting
UID" is aUIDthat appears in more than one of Drasil's chunk database tables. To see which ones currently exist at any time, you can runmake debugand peek into thebuild/X/.drasil/problematic_seeds.jsonfiles.At time of writing, the categories are as follows:
IdeaDicts) and Symbols (QuantityDicts) -- e.g., indblpendConceptChunks) -- e.g., ingamephysics,glassbrgamephysicsgamephysicsglassbrUnitDefns) -- e.g., inhghcsglpendsspWe don't want any conflicting
UIDs because when the upgradedChunkDBprototype is merged, chunks will be overwritten by one another. We need to change theUIDs of things, reorganizing the chunks if necessary.Beta Was this translation helpful? Give feedback.
All reactions