Repository navigation
Conversation
A child listed in a container's `content:` that could not be resolved on load (its directory was deleted, its config was missing or broken) made the container "partially loaded", and YamlFormatSynchronizer.saveItem then skipped every save of its config for the rest of the session. Every child added later never reached `content:` and vanished after the next restart. For Hyperskill this lost each topic opened after a single topic folder had gone missing: the folders stayed on disk, but the topics disappeared from the course, and reopening one from the browser created "<topic> (1)". Now the container remembers the unresolved entries together with the resolved entry each one followed (ItemContainer.unresolvedContent), and the YAML mixins write `content:` from ItemContainer.contentNames, which puts them back in place. The container is saved as usual, so the on-disk list keeps the unresolved names and still gains new children. Adding a child with the same name takes the entry over. The loader now logs which child it could not resolve.
maven.pkg.jetbrains.space no longer resolves: JetBrains Space package hosting is shut down. Gradle asks repositories in declaration order, and this one came before the IntelliJ Platform and Marketplace repositories, so every artifact that was not cached yet failed on it instead of falling through to the next repository. The new Rust plugin build for 263 (263.7307.313) broke `:intellij-plugin:hs-Rust:compileKotlin` this way, and any build against a new IDE version would too. The only artifact taken from it, kotlin-css-jvm 2026.8.4, is on Maven Central. (cherry picked from commit 53c5a41)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A student reported that Hyperskill topics kept disappearing from the course tree after an IDE restart, while their files stayed on disk. Reopening one of these topics from the browser created a second folder,
<topic> (1).Cause
One topic folder listed in
Topics/section-info.yamlwas gone from disk. In this case it was a stray topic that the student had deleted. From then on, every load marked theTopicssection as partially loaded. For a partially loaded container,YamlFormatSynchronizer.saveItemskipped every save of its config for the whole session. This guard was added so that a truncatedcontent:list would not be written back.The guard also skipped the save that adds a newly opened topic. Each new topic got its folder and configs on disk but never reached
content:, so the next load ignored it. The log showed this as a repeated line:Fix
content:entry it could not resolve, together with the resolved entry it followed (ItemContainer.unresolvedContent).content:fromItemContainer.contentNames. That is the names ofitems, with the unresolved entries put back in their original positions.StudyItem.isPartiallyLoadedare removed. A partially loaded container is saved like any other: it keeps its unresolved entries and can still gain new children.StudyItemConverterbecame unused and is removed.Unsupported tasks in Hyperskill topic lessons are still skipped on purpose and dropped from
content:on save, as before.Already affected projects
This PR stops new topics from being lost. It does not bring back topics that were already lost: their folders are not listed in
content:, and nothing scans for them. Students who are already affected still need to fixTopics/section-info.yamlby hand while the IDE is closed. Itscontent:list should contain exactly theTopicssubfolders that have alesson-info.yaml.Not fixed here
The stray topic in this report came from
HyperskillOpenInIdeRequestHandler.getTopicWithRecommendedSteps. When it cannot find the theory step (Can't get theory step title for <id> step), it names the topic lesson after the problem. That creates a duplicate topic, and the student deleted it.Build fix taken from #73
mainstill declares the deadmaven.pkg.jetbrains.spacerepository. Because of it, the CI jobs for 261 and 262 failed to resolvecom.jetbrains.intellij.idea:ideabefore compiling anything. This branch carries a cherry-pick of the same one-line removal from #73 (Remove the dead JetBrains Space Maven repository). Once #73 is merged, it drops out of this PR's diff.Testing
UnresolvedContentYamlTestchecks four cases:coursecreator.yaml.*,learning.yaml.*,learning.format.*, HyperskillprojectOpen.*,HyperskillCourseUpdateTestandHyperskillLoadingTest. 144 tests ran and 143 passed.AddNewItemYamlTest > test new task file added. It runs first in the JVM for this subset and fails the same way on the base commit without this change. It passes when its class runs alone.main.:intellij-plugin:testandverifyPlugin.