api: more informative request canceling

[nurzhan-saktaganov]

Log the probable reason for unexpected requestId.
Add requestId info to context done error message.

What has been done? Why? What problem is being solved?

I didn't forget about (remove if it is not applicable):

• Tests (see documentation for a testing package)
• Changelog (see documentation for changelog format)

Related issues:

[oleg-jukovec]

Thank you for the patch! I would like to use a more general request ID, request id or just request instead of requestId that refers to the internal implementation.

[oleg-jukovec]

Thank you for the patch! Please, squash commits into one.

[oleg-jukovec]

Please, fix the linter error:
https://github.com/tarantool/go-tarantool/actions/runs/10949588796/job/30417271248?pr=407

It should be enough:

$ go install golang.org/x/tools/cmd/goimports@latest
$ goimports -w .

[nurzhan-saktaganov]

I have fixed linter error and squashed commits into single commit.

[oleg-jukovec]

I have fixed linter error and squashed commits into single commit.

Thank you. Let's wait a bit for a second reviewer and I'll merge.

[KaymeKaydex]

I'm a little confused by the use of regular expressions to calculate the error type. regexp is slow compared to errors.Is. Why can't we use the errors.Is construct in this case?

[oleg-jukovec]

We could extend the ClientError & errors.As to catch it:

go-tarantool/errors.go

Lines 25 to 30 in 0ccdee2

	// ClientError is connection error produced by this client,
	// i.e. connection failures or timeouts.
	type ClientError struct {
	Code uint32
	Msg string
	}

go-tarantool/errors.go

Lines 55 to 64 in 0ccdee2

	// Tarantool client error codes.
	const (
	ErrConnectionNotReady = 0x4000 + iota
	ErrConnectionClosed = 0x4000 + iota
	ErrProtocolError = 0x4000 + iota
	ErrTimeouted = 0x4000 + iota
	ErrRateLimited = 0x4000 + iota
	ErrConnectionShutdown = 0x4000 + iota
	ErrIoError = 0x4000 + iota
	)

[nurzhan-saktaganov]

Since it's tests, there is no performance issue is questioned. So using regexp is ok here.
Returning here a ClientError or something else changes API.
I'm not intended to change the existing API, I'm intended just to make more informative the existing one (to avoid misleading and questions by users of library in the future).

[DerekBum]

Thanks for the patch!