libre.sh issueshttps://lab.libreho.st/groups/libre.sh/-/issues2023-12-29T14:44:47Zhttps://lab.libreho.st/libre.sh/nextcloud-apps/liiibre/-/issues/3Add the forum to the menu2023-12-29T14:44:47ZHugo RenardAdd the forum to the menuLike on nuage.liiib.re.Like on nuage.liiib.re.https://lab.libreho.st/libre.sh/nextcloud-apps/liiibre/-/issues/2FR: add option to delete user in NC2023-09-08T13:29:04ZTimothee GosselinFR: add option to delete user in NCAs we don't have scim yet, an admin should be able to delete a user. This hidden at the momentAs we don't have scim yet, an admin should be able to delete a user. This hidden at the momentTimothee GosselinTimothee Gosselinhttps://lab.libreho.st/libre.sh/nextcloud-apps/liiibre/-/issues/1FR: Make sites configurable in admin settings2023-11-07T16:11:45ZTimothee GosselinFR: Make sites configurable in admin settingshttps://lab.libreho.st/libre.sh/nextcloud-version-retention/-/issues/1Check for duplicate ETag & make it less agresssive2023-05-26T15:14:32ZHugo RenardCheck for duplicate ETag & make it less agresssivehttps://lab.libreho.st/libre.sh/scim/scimserviceprovider/-/issues/12Spurious group membership change notifications2024-02-06T10:48:50ZArieSpurious group membership change notificationsTo add (or in theory, remove) users to a group, one needs to set the new complete list of members in a `PUT` call, as there is no `PATCH` support. The way this is implemented results in a notification being sent to every group member, sa...To add (or in theory, remove) users to a group, one needs to set the new complete list of members in a `PUT` call, as there is no `PATCH` support. The way this is implemented results in a notification being sent to every group member, saying that they have been removed from the group, and then that they have been added to the group, even though nothing really changed for them. I can see how this happens, with the code first removing everyone from the group and then re-adding from the new list, but it's not very nice.https://lab.libreho.st/libre.sh/scim/scimserviceprovider/-/issues/11Removing group members doesn't work2023-05-11T09:11:21ZArieRemoving group members doesn't workWhen changing the set of group members via a `PUT` call, I get back a `200` code, but even though new additions are indeed added to the group, removals are not reflected. I tested this with the built-in `admin` group, not sure if other g...When changing the set of group members via a `PUT` call, I get back a `200` code, but even though new additions are indeed added to the group, removals are not reflected. I tested this with the built-in `admin` group, not sure if other groups have the same problem.
There are no errors in the Nextcloud log.
This is a very important issue for us (Stackspin).https://lab.libreho.st/libre.sh/scim/rocketchat-scim/-/issues/18Scim doesn't seem to work on Version 5.4.62023-04-18T07:28:55Zd3hScim doesn't seem to work on Version 5.4.6Only tested on 5.4.6 - not sure if it's a configuration Problem - but at least i can't see the Url that's needed to configure it with kc after I deleted the app.Only tested on 5.4.6 - not sure if it's a configuration Problem - but at least i can't see the Url that's needed to configure it with kc after I deleted the app.https://lab.libreho.st/libre.sh/scim/scimserviceprovider/-/issues/10Composer missing coenjacobs/mozart configuration2023-03-04T13:55:43ZrawtazComposer missing coenjacobs/mozart configurationI may be mistaken, but from what I can tell, there are only occurences (and configuration for) `coenjacobs/mozart` in `composer.lock` - nothing in `composer.json`.
Since `composer.json` is the place where one should add and configure `c...I may be mistaken, but from what I can tell, there are only occurences (and configuration for) `coenjacobs/mozart` in `composer.lock` - nothing in `composer.json`.
Since `composer.json` is the place where one should add and configure `coenjacobs/mozart`, I presume that some of the code used during development has not been committed to the repository? Here are the official configuration instructions and they clearly mention `composer.json` (which makes sense): https://github.com/coenjacobs/mozart#configuration
Can you guys check this and also at the same time make sure to check if there are any other parts that haven't been committed (just seeing as it has happened before in !2 that some things weren't committed properly, so it'd good to make sure once and for all)?https://lab.libreho.st/libre.sh/scim/scimserviceprovider/-/issues/9Move auth_type and jwt.secret out of config file2023-03-03T10:46:01ZrawtazMove auth_type and jwt.secret out of config fileCurrently there is a `lib/Config/config.php` file in which one configures the settings `auth_type` and optionally also `jwt` with a subsetting of `secret`.
Having this in a version controlled config file like this is messy to deal with,...Currently there is a `lib/Config/config.php` file in which one configures the settings `auth_type` and optionally also `jwt` with a subsetting of `secret`.
Having this in a version controlled config file like this is messy to deal with, in particular during development. I propose that we move these (and other settings) into [a simple form](https://docs.nextcloud.com/server/24/developer_manual/digging_deeper/settings.html#settings-form) in [the `additional` section](https://docs.nextcloud.com/server/24/developer_manual/digging_deeper/settings.html#section) (no need for our own custom Section, as it is just two small form fields) of the Settings view in Nextcloud, and then also store these settings in the [app's configuration](https://nextcloud-server.netlify.app/classes/ocp-iconfig#method_setAppValue).https://lab.libreho.st/libre.sh/scim/keycloak-scim/-/issues/23syncing attributes failed2023-02-22T07:51:48ZSzkudlareksyncing attributes failedI am new to SCIM but we're using KC for many services (we're using 20.0.5).
So we were trying to use the plugin for configuration as the provisioning (we want to sync users from KC to KnowBe4) for:
https://support.knowbe4.com/hc/en-us/ar...I am new to SCIM but we're using KC for many services (we're using 20.0.5).
So we were trying to use the plugin for configuration as the provisioning (we want to sync users from KC to KnowBe4) for:
https://support.knowbe4.com/hc/en-us/articles/360052380374
The sync works, but it looks like attributes are missing or mixed. I tried to switch between content type, but no effect.
The app says that no e-mail addresses are wrong (although they are visible in the KC).
From the app's log i can read, that the user name in json is probably transferred as the email, the name is empty.
Is there anything else to be set up in the KC or the plugin (mappers?) to get it working? What could be the reason for the issues?https://lab.libreho.st/libre.sh/docker/discourse/-/issues/14Prepackage some themes2023-01-26T13:37:47ZTimothee GosselinPrepackage some themesPrepackage some themes in Dockerfile - see https://meta.discourse.org/t/install-a-theme-programatically/191843Prepackage some themes in Dockerfile - see https://meta.discourse.org/t/install-a-theme-programatically/191843Timothee GosselinTimothee Gosselinhttps://lab.libreho.st/libre.sh/nextcloud-apps/multioffice/-/issues/2Missing compatible version2023-08-13T10:49:04ZPikeMissing compatible versionHi,
I saw Nextcloud 24.0.8 was released but I'm getting warnings that multioffice is not compatible, most likely the same with 25.x.x also.
I also saw the app is no longer on the Nextcloud App store, can I ask what happened?
Thanks
...Hi,
I saw Nextcloud 24.0.8 was released but I'm getting warnings that multioffice is not compatible, most likely the same with 25.x.x also.
I also saw the app is no longer on the Nextcloud App store, can I ask what happened?
Thanks
Brendanhttps://lab.libreho.st/libre.sh/scim/scimserviceprovider/-/issues/6Clarify user account requirement for JWT token2023-03-04T20:41:42ZrawtazClarify user account requirement for JWT tokenDuring my testing of PR !2 I've discovered that the username that is mentioned in the JWT token's payload must also exist as a user in Nextcloud. However, it must not be part of the admin group, it can be a regular unprivileged user. Giv...During my testing of PR !2 I've discovered that the username that is mentioned in the JWT token's payload must also exist as a user in Nextcloud. However, it must not be part of the admin group, it can be a regular unprivileged user. Given the latter, why do we even need an actual user account in the first place? Couldn't we just use a token that is "userless", and once verified allows access to editing users and groups using SCIM?https://lab.libreho.st/libre.sh/scim/scimserviceprovider/-/issues/5Clarify version requirements and GUI effect2023-03-31T21:35:29ZrawtazClarify version requirements and GUI effectThe following relates to the current work being done in PR #2.
- The appinfo in that code currently dictates that the only accepted Nextcloud version for this app is version 22. Is that (draft) app compatible with NC 24 and NC 25? Has i...The following relates to the current work being done in PR #2.
- The appinfo in that code currently dictates that the only accepted Nextcloud version for this app is version 22. Is that (draft) app compatible with NC 24 and NC 25? Has it been tested and perhaps even developed with these versions?
- Also, is there supposed to be any Settings or similar other parts of the web GUI with this app, or is it only the enabling/disabling of the app in the Applications view that shows up in relation to installing it?https://lab.libreho.st/libre.sh/compose/discourse/-/issues/23What if...?2022-09-14T06:10:23ZJean-Luc GARNIERWhat if...?Hi Pierre,
What if:
- I want to deploy this stack on my private server (Debian 11 + Docker)? May I just run the same installation script?
- I want to use non-standard ports such as 3080/3443 to avoid conflicts? May I just modify the YML...Hi Pierre,
What if:
- I want to deploy this stack on my private server (Debian 11 + Docker)? May I just run the same installation script?
- I want to use non-standard ports such as 3080/3443 to avoid conflicts? May I just modify the YML file (i.e. ports: 3080:80)?
It seems my issues could be related to the above questions...
Thanks in advance for your advice!https://lab.libreho.st/libre.sh/docker/nextcloud/-/issues/1Use defaultApps instead of disabled and enabled apps2022-09-06T15:23:07ZTimothee GosselinUse defaultApps instead of disabled and enabled appsOur install script should only use default apps instead of two variables.
It should be able from the list of default apps to disable and enables the right appsOur install script should only use default apps instead of two variables.
It should be able from the list of default apps to disable and enables the right appshttps://lab.libreho.st/libre.sh/compose/discourse/-/issues/22install script fails on rake launch2022-09-06T08:06:54ZJean-Luc GARNIERinstall script fails on rake launchHi all,
I want to give a try with Discourse and strictly followed the install process. Unfortunately, the ./scripts/install runs fine until it hits the `docker-compose run app bash -c 'sleep 60 && bundle exec rake db:migrate assets:preco...Hi all,
I want to give a try with Discourse and strictly followed the install process. Unfortunately, the ./scripts/install runs fine until it hits the `docker-compose run app bash -c 'sleep 60 && bundle exec rake db:migrate assets:precompile'` command, which returns:
```
Creating network "discourse_back" with driver "bridge"
Creating discourse_postgres_1 ... done
Creating discourse_redis_1 ... done
Couldn't connect to Redis
rake aborted!
Redis::CannotConnectError: Error connecting to Redis on localhost:6379 (Errno::EADDRNOTAVAIL)
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:398:in `rescue in establish_connection'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:379:in `establish_connection'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:117:in `block in connect'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:344:in `with_reconnect'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:116:in `connect'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:417:in `ensure_connected'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:269:in `block in process'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:356:in `logging'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:268:in `process'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:162:in `call'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/mini_profiler/profiling_methods.rb:85:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis.rb:967:in `block in get'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis.rb:72:in `block in synchronize'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis.rb:72:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis.rb:966:in `get'
/var/www/discourse/app/models/global_setting.rb:42:in `safe_secret_key_base'
/var/www/discourse/config/initializers/100-secret_token.rb:6:in `<main>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.12.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:39:in `load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.12.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:39:in `load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/engine.rb:667:in `block in load_config_initializer'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/notifications.rb:208:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/engine.rb:666:in `load_config_initializer'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/engine.rb:620:in `block (2 levels) in <class:Engine>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/engine.rb:619:in `each'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/engine.rb:619:in `block in <class:Engine>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:32:in `instance_exec'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:32:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:61:in `block in run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:50:in `tsort_each_child'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:60:in `run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/application.rb:372:in `initialize!'
/var/www/discourse/config/environment.rb:7:in `<main>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.12.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.12.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/zeitwerk-2.6.0/lib/zeitwerk/kernel.rb:35:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/application.rb:348:in `require_environment!'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/application.rb:511:in `block in run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli/exec.rb:58:in `load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli/exec.rb:58:in `kernel_load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli/exec.rb:23:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli.rb:479:in `exec'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli.rb:31:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli.rb:25:in `start'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/exe/bundle:48:in `block in <top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/exe/bundle:36:in `<top (required)>'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'
Caused by:
Errno::EADDRNOTAVAIL: Cannot assign requested address - connect(2) for [::1]:6379
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/connection/ruby.rb:155:in `connect_addrinfo'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/connection/ruby.rb:193:in `block in connect'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/connection/ruby.rb:191:in `each'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/connection/ruby.rb:191:in `each_with_index'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/connection/ruby.rb:191:in `connect'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/connection/ruby.rb:305:in `connect'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:385:in `establish_connection'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:117:in `block in connect'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:344:in `with_reconnect'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:116:in `connect'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:417:in `ensure_connected'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:269:in `block in process'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:356:in `logging'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:268:in `process'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis/client.rb:162:in `call'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/mini_profiler/profiling_methods.rb:85:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis.rb:967:in `block in get'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis.rb:72:in `block in synchronize'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis.rb:72:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.5.1/lib/redis.rb:966:in `get'
/var/www/discourse/app/models/global_setting.rb:42:in `safe_secret_key_base'
/var/www/discourse/config/initializers/100-secret_token.rb:6:in `<main>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.12.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:39:in `load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.12.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:39:in `load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/engine.rb:667:in `block in load_config_initializer'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/notifications.rb:208:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/engine.rb:666:in `load_config_initializer'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/engine.rb:620:in `block (2 levels) in <class:Engine>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/engine.rb:619:in `each'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/engine.rb:619:in `block in <class:Engine>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:32:in `instance_exec'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:32:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:61:in `block in run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:50:in `tsort_each_child'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/initializable.rb:60:in `run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/application.rb:372:in `initialize!'
/var/www/discourse/config/environment.rb:7:in `<main>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.12.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.12.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/zeitwerk-2.6.0/lib/zeitwerk/kernel.rb:35:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/application.rb:348:in `require_environment!'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3/lib/rails/application.rb:511:in `block in run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli/exec.rb:58:in `load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli/exec.rb:58:in `kernel_load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli/exec.rb:23:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli.rb:479:in `exec'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli.rb:31:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/cli.rb:25:in `start'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/exe/bundle:48:in `block in <top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.16/exe/bundle:36:in `<top (required)>'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'
Tasks: TOP => db:migrate => db:load_config => environment
(See full trace by running task with --trace)
```
I just can't find any clue and am obviously unable to run the docker-compose command... I don't understand why the script is expecting Redis to run as Redis would be deployed by the docker-compose command! 🤔
Thanks in advance for any help!https://lab.libreho.st/libre.sh/scim/scim/-/issues/7Feat: allow path overwritte in setup urls2022-08-19T13:44:46ZHugo RenardFeat: allow path overwritte in setup urlshttps://lab.libreho.st/libre.sh/scim/rocketchat-scim/-/issues/17Can't link users to existing users in Rocketchat2022-10-25T09:34:28Zd3hCan't link users to existing users in Rocketchat## Server Versions
Keycloak Version 16.1.1-legacy
RCVersion 4.8.3
## Bug descriptions
So I deployed the scim-adapter on an existing keycloak + rc and for existing users the role mapping doesn't seem to work.
Keycloak shows me the f...## Server Versions
Keycloak Version 16.1.1-legacy
RCVersion 4.8.3
## Bug descriptions
So I deployed the scim-adapter on an existing keycloak + rc and for existing users the role mapping doesn't seem to work.
Keycloak shows me the following error message - the api call to rc scim is never made.
```
2022-08-11T12:05:27.297644765Z 12:05:27,297 INFO [sh.libre.scim.event.ScimEventListenerProvider] (default task-78) DELETE users 3f9bed91-6ce4-40f5-a41d-3b58ce13a6f5 roles
2022-08-11T12:05:27.297725249Z 12:05:27,297 INFO [sh.libre.scim.core.ScimDispatcher] (default task-78) 22db2fe9-c2d7-4731-a88d-8d4e8cc13258 scim scim org.keycloak.storage.UserStorageProvider
2022-08-11T12:05:27.306681350Z 12:05:27,306 WARN [sh.libre.scim.core.ScimClient] (default task-78) failed to replace resource 3f9bed91-6ce4-40f5-a41d-3b58ce13a6f5, scim mapping not found
```
For new users it works, but it looks like the users that existed before in Keycloak can't be linked to the user in rc with scim.
Users are coming from an external identity provider.https://lab.libreho.st/libre.sh/docker/rocketchat/-/issues/1Dependency Dashboard2023-06-21T07:31:20ZrenovateDependency DashboardThis issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Open
These updates have all been created already. Click a checkbo...This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
- [ ] <!-- rebase-branch=renovate/rocketchat-rocket.chat-5.x -->[chore(deps): update dependency rocketchat/rocket.chat to v5.4.10](!10)
- [ ] <!-- rebase-branch=renovate/rocketchat-rocket.chat-6.x -->[chore(deps): update dependency rocketchat/rocket.chat to v6](!11)
## Detected dependencies
<details><summary>regex</summary>
<blockquote>
<details><summary>.gitlab-ci.yml</summary>
- `RocketChat/Rocket.Chat 5.4.8`
</details>
</blockquote>
</details>