Skip to content

Conversation

@ArtificialOwl
Copy link
Member

@ArtificialOwl ArtificialOwl commented Jan 9, 2025

This fix an eventual regression from #40885 when discovering remote ocm provider data.

Also, there is no reason for an app to directly interact with the discovery() as the method itself should manage last version of the protocol.

Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
@ArtificialOwl ArtificialOwl added the 3. to review Waiting for reviews label Jan 10, 2025
@nickvergessen
Copy link
Member

This fix an eventual regression from #40885 when discovering remote ocm provider data.

I remember we talked about it, but I don't recall. What exactly was the problem?

@susnux susnux added this to the Nextcloud 32 milestone Mar 2, 2025
@ArtificialOwl
Copy link
Member Author

If we dont reset the data and execute the discovery on 2 differents instances, some data from the first request might be kept on second request

This was referenced Aug 22, 2025
@skjnldsv skjnldsv modified the milestones: Nextcloud 32, Nextcloud 33 Sep 28, 2025
@susnux susnux deleted the fix/noid/discover-unique-ocmprovider branch November 1, 2025 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants