Hotfix/solr setup improvements - #607
Merged
Merged
Conversation
- Updated setupSolr() to create tenant-specific configSet instead of base configSet - Modified ensureTenantCollectionExists() to use tenant-specific configSet - Added getTenantConfigSetName() method for consistent configSet naming - Removed ensureBaseCollectionExists() method as only tenant collections are needed - Updated validation to check tenant-specific configSet and collection - Updated error reporting and logging to reference tenant-specific resources - All SOLR resources now follow tenant-specific naming pattern (e.g., openregister_nc_f0e53393)
…s tracking - Added visual progress bar showing completed vs total steps - Display detailed error information with primary error, error type, and operation - Show SOLR configuration used during failed setup attempts - Added troubleshooting steps section with numbered action items - Enhanced step timeline with individual step status and timestamps - Improved visual styling with color-coded progress indicators - Failed steps now highlight in red with detailed error context - Added error metadata display (error type, operation, configuration) - Better responsive design for mobile devices - Maintains backward compatibility with existing setup response format
- Added details about tenant-specific configSets and collections - Documented enhanced error reporting with progress tracking - Listed new UI improvements in setup dialog - Fixed multi-tenant isolation improvements
remko48
pushed a commit
that referenced
this pull request
Sep 16, 2025
Hotfix/solr setup improvements Restored beta version to 0.2.7-beta.72
rubenvdlinde
added a commit
that referenced
this pull request
Dec 28, 2025
Hotfix/solr setup improvements
rubenvdlinde
added a commit
that referenced
this pull request
Aug 6, 2026
Carries ConductionNL/nextcloud-vue#608, which closes #607: the flow editor no longer lets a user press Save before the store has a flow to save. The window was real and wide. `emptyFlow()` has `name: ''`, only `open('new')` supplies the default, and `open()` ran behind `await GET /api/flows` — a list a blank flow does not need — while the sidebar was already rendered and Save already enabled. Saving in that window posted `name: ""` and the API answered 400 "A flow needs a name." A refused save rendered nothing at all, so the user saw the button flicker and no more. The same late `open('new')` also reset the flow, wiping a step already placed on the canvas. Verified against this bundle, in the window itself: clicking Save 120ms after opening a blank flow — where a 400 was previously reproducible 9 times in 10 — returns 201 with `name: "New flow"` and the route advances to the new uuid. `vue` is pinned back to ^3.5.18 by hand again. `npm install` rewrites it to ^3.5.0 to match the new package's own range, which contradicts the `overrides` entry, and CI's npm 10.8.2 refuses that with EOVERRIDE while local npm 11 accepts it silently. `npx npm@10.8.2 ci --dry-run` is clean with the range restored. Worth automating; for now it is a hand check on every bump of this package.
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
1 participant
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.
Proper config naam