Skip to content

ADBM-3113: Fix for socket init at repo-push#107

Merged
dkovalev1 merged 3 commits into2.54-cifrom
ADBM-3113
May 5, 2026
Merged

ADBM-3113: Fix for socket init at repo-push#107
dkovalev1 merged 3 commits into2.54-cifrom
ADBM-3113

Conversation

@dkovalev1
Copy link
Copy Markdown

@dkovalev1 dkovalev1 commented Apr 29, 2026

Command repo-push uses remote manifest, but to load it with S3 local socket
must be initialized first.

Socket is initialized in the call of sckInit() which is called when option --keep-alive is valid.
It can become valid if --keep-alive is available for the repo-push.
sck-keep-alive is a part of command buffer-size where all similar options are
listed.

This commit adds repo-push to the buffer-size.

The file src/config/parse.auto.c.inc is autogenerated and shall be updated as well.

ADBM-3113

@dkovalev1 dkovalev1 changed the title [DRAFT] ADBM-3113: Fix for socket init at repo-push ADBM-3113: Fix for socket init at repo-push Apr 30, 2026
RekGRpth
RekGRpth previously approved these changes Apr 30, 2026
@hilltracer

This comment was marked as resolved.

@dkovalev1
Copy link
Copy Markdown
Author

@dkovalev1 Please test it with S3 storage and publish the result to make sure that the problem is really resolved.

full integration tests were run with ADBM, details in the ADBM-3113

@dkovalev1 dkovalev1 merged commit 8a1452b into 2.54-ci May 5, 2026
15 checks passed
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.

3 participants