-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Collections cannot be managed in family organization #2750
Comments
L'errore specifico riportato indica che l'espressione LINQ non può essere tradotta. Ciò potrebbe essere dovuto a un problema di compatibilità tra la versione di Docker che hai aggiornato e il codice sorgente dell'applicazione Webvault. |
Hi there, Thank you for your report! I was able to reproduce this issue, and have flagged this to the Bitwarden engineering team. Thanks once again! |
Any idea on time frame when this will be fixed? Paying for a family sub that is unusable due to this error. |
Latest push to /dev works perfectly. |
Beta tag seems to still have this issue even though it says it is on server 2023.2.2 as of latest push. I'm not really sure how that happens. I assumed dev = beta when they are pushed at the same time (and at the least that the server would include changes made prior to the version bump). |
That's a great question. I don't know what changes were pushed to beta. It was odd to see both pushed at the same time last night and I immediately changed my tag to beta and rebuilt the container. I too noticed that this fix was not implemented in the beta at that time. There's not a lot of view into their pipeline to understand what is pushing when. |
Glad to have confirmation. @justindbaur can you provide any insight into why this might be the case? Usually the server releases are versioned such that any commit before the tag is included. How could it be then that the beta release says version 2023.2.2 but does not have this fix in it, which is in a commit prior to the version bump? |
@holow29 Our code is not versioned that anything before a tag is included. We create an I won't say a definitive never but unified issues will very rarely be hotfixed while it is in beta. Once it is out of beta it will be just like the standard product. The |
Steps To Reproduce
Expected Result
A view showing the filter view with the collections etc. on the left and the collections/entries in the middle pane.
Actual Result
A loading indicator on the left running "forever" (waited 15 minutes) and all entries of the entire vault loading in the middle with a gray empty square where normally the collections it is in are shown. (According to the online view in the webvault).
Also the "api.log" shows the following error:
Screenshots or Videos
Additional Context
Seems to be related to some issue with EF-translation of the query. Looking at the code it seems that the "groups" and "user" query could have the same issue. (Lines 188 & 193
src/Infrastructure.EntityFramework/Repositories/CollectionRepository.cs
)Doing some research one possible solution from Stackoverflow was to add an "orderBy" in the query: https://stackoverflow.com/questions/70423147/translation-of-select-which-contains-grouping-parameter-without-composition-is
You can also not edit any existing user, add a new one or add a new collection, as it only shows the loading indicator in the popup and also narrows down to the same error in the logs.
Githash Version
3cedc0c-dirty
Environment Details
Database Image
mariadb: 10.6
Issue-Link
#2480
Issue Tracking Info
The text was updated successfully, but these errors were encountered: