Skip to content

running: detect missing tarantool through wrapped errors#1304

Open
bigbes wants to merge 1 commit into
v3from
bigbes/gh-no-tarantool-not-found-msg
Open

running: detect missing tarantool through wrapped errors#1304
bigbes wants to merge 1 commit into
v3from
bigbes/gh-no-tarantool-not-found-msg

Conversation

@bigbes

@bigbes bigbes commented Jun 1, 2026

Copy link
Copy Markdown
Collaborator

The integrity dummyRepository.Read now wraps the os.Open error with fmt.Errorf("open %q: %w", ...). baseInstance.Run checked the result with the legacy os.IsNotExist, which does not unwrap, so a missing tarantool binary leaked a raw 'open "": no such file or directory' message instead of the friendly 'tarantool executable is not found'.

Use errors.Is(err, os.ErrNotExist) so the wrapped not-exist error is recognized again. Fixes test_run_without_tarantool on v3.

@bigbes bigbes requested review from Mockird31 and sssciel June 1, 2026 09:20
@bigbes bigbes added the full-ci Enables full ci tests label Jun 1, 2026
The integrity dummyRepository.Read now wraps the os.Open error with
fmt.Errorf("open %q: %w", ...). baseInstance.Run checked the result with
the legacy os.IsNotExist, which does not unwrap, so a missing tarantool
binary leaked a raw 'open "": no such file or directory' message instead
of the friendly 'tarantool executable is not found'.

Use errors.Is(err, os.ErrNotExist) so the wrapped not-exist error is
recognized again. Fixes test_run_without_tarantool on v3. so .
@bigbes bigbes force-pushed the bigbes/gh-no-tarantool-not-found-msg branch from ea425b7 to 854ebc9 Compare June 1, 2026 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full-ci Enables full ci tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants