Skip to content

Fix slicer owner issue #1173

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

Merged
merged 2 commits into from
May 22, 2025
Merged

Conversation

smallhive
Copy link
Contributor

@smallhive smallhive commented May 20, 2025

Closes #1172.

@smallhive smallhive requested a review from roman-khimov as a code owner May 20, 2025 06:14
@smallhive smallhive force-pushed the 1172-internal-slicer-test-still-failing branch from 86b09fb to d67a63f Compare May 20, 2025 07:37
….0-rc.13.0.20250516065036-cd732ce85922

Closes #1172.

Signed-off-by: Evgenii Baidakov <evgenii@nspcc.io>
@smallhive smallhive force-pushed the 1172-internal-slicer-test-still-failing branch from d67a63f to 56f2309 Compare May 22, 2025 06:19
@smallhive
Copy link
Contributor Author

Well, updating to the latest actual master of the SDK fixed everything. My previous patch wasn't based on the latest version. I consider it was git pull fail, which I missed

Sometimes it is usefull to have gate and anonymous user pub key or user id.

Signed-off-by: Evgenii Baidakov <evgenii@nspcc.io>
@smallhive smallhive force-pushed the 1172-internal-slicer-test-still-failing branch from 56f2309 to 7c55089 Compare May 22, 2025 09:38
@roman-khimov roman-khimov merged commit b1cc7af into master May 22, 2025
12 of 15 checks passed
@roman-khimov roman-khimov deleted the 1172-internal-slicer-test-still-failing branch May 22, 2025 11:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Internal slicer test still failing
2 participants