profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/pkositsyn/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Pavel Kositsyn pkositsyn Yandex Moscow Monitoring and observability. Go, C++, Python. MIPT DIHT and YSDA grad.

push eventpkositsyn/resty

Kishan B

commit sha 7a0e1ea9b189eefb4e7ac22da8e2af1d9c1bd623

Fix broken members link in readme (#435) The link https://github.com/orgs/go-resty/teams/core/members is broken (404 error) Changing it to https://github.com/orgs/go-resty/people

view details

cnmade

commit sha df4a64cac6954e8b2bccea389aa1c3bcef530371

Version update 2.6.0 on readme for go.mod (#453)

view details

Kishan B

commit sha 3f7a6e520679e490a622ba56694ab4fc89745b5a

Add 1.16.x and remove 1.14.x from the travis build (#434)

view details

Muhammad Ilham

commit sha ecf7cdae04c4e7f7c98d3c78d17b1be7ca13d5b7

feat(#432): Implement Easier Adding of Multiple Value HTTP Header (#452)

view details

Tanya Bouman

commit sha d717652a514c232b698690a577a9cafda870b985

Update Bazel build to work with 4.0.0 (#428) * Update Bazel build to work with 4.0.0 This includes several updates to the BUILD and WORKSPACE files, so that they now work with Bazel 4.0.0, Gazelle 0.23 and rules_go 0.27. By default, [Gazelle now uses](https://github.com/bazelbuild/bazel-gazelle/pull/863) the last component of the Bazel package, rather than `go_default_library` as the `go_library name`. This causes problems when the naming conventions do not match. https://github.com/bazelbuild/bazel-gazelle/issues/890#issuecomment-685145667 Adding support for the new naming convention should not break anything that depends on using the old naming convention, because the Gazelle option `import_alias` makes aliases to the libraries and this allows the old naming convention to still work.

view details

Pavel Borzenkov

commit sha c1fa35881e814e06d0b49c1ea899fe65738282e0

Don't use sync.Pool for json.NewEncoder target buffers (#421) * Don't release buf to sync.Pool to early The slice returned by `noescapeJSONMarshal` continues to be accessed even after `pool.Put` was called on the buffer. This might lead to incorrect data being sent in request body if the buffer is acquired and re-written by a concurrently running goroutine. So make sure we release the buffer once the request completes. * Release request body buf back to sync.Pool only after body is closed net/http.RoundTripper may access request body in a separate goroutine, so we need to wait release the buf back to sync.Pool only after the body is closed. From the docs: // RoundTrip must always close the body, including on errors, // but depending on the implementation may do so in a separate // goroutine even after RoundTrip returns. This means that // callers wanting to reuse the body for subsequent requests // must arrange to wait for the Close call before doing so.

view details

Pavel

commit sha 78861d16d6661b0bc387ea83f23d0cc8c7076b3f

Merge branch 'master' of https://github.com/go-resty/resty into do_not_wait_last_retry

view details

Pavel

commit sha 55cd25d3cb77167ddeddb5d8d05426f38eabd20d

Fix tests Signed-off-by: Pavel <kositsyn.pa@phystech.edu>

view details

push time in 12 days

pull request commentgo-resty/resty

Don't wait after last retry

@jeevatkm Done. Thanks!

pkositsyn

comment created time in 12 days

push eventpkositsyn/resty

Pavel

commit sha 458f0daa02be24704e3b1278a40d64306345ca74

Change to trigger pipeline Signed-off-by: Pavel <kositsyn.pa@phystech.edu>

view details

push time in 12 days

PR opened go-resty/resty

Don't wait after last retry

Add check not to wait after last retry. Did it after retry hooks to keep compatibility.

Link to issue: #443

Signed-off-by: Pavel kositsyn.pa@phystech.edu

+48 -6

0 comment

2 changed files

pr created time in a month

create barnchpkositsyn/resty

branch : do_not_wait_last_retry

created branch time in a month

fork pkositsyn/resty

Simple HTTP and REST client library for Go

fork in a month

issue openedgo-resty/resty

Do not wait retry time if exceeded max attempts

In this block https://github.com/go-resty/resty/blob/70336cb87f39407ce7f8d41ffcd2b40b9729f401/retry.go#L104-L145 when attempt == opts.maxAttempts and onRetryCondition returned true we wait extra time for retry. But after waiting just return err as long as we don't enter cycle anymore.

Example: https://play.golang.org/p/v3l6LmcWRvA. Should wait 2 seconds for 1 retry instead of 4.

created time in a month

PR opened vitkovskii/insane-json

Fix floats representation as int

https://play.golang.org/p/l55RaWCbfUP

If json is {"value": 1e+1}, then AsInt() should be 10 instead of 0

+3 -2

0 comment

2 changed files

pr created time in 3 months

push eventpkositsyn/insane-json

Pavel

commit sha 91f150d0566f105f5dac31d6cedfb67c7e70bbba

Add test

view details

push time in 3 months

create barnchpkositsyn/insane-json

branch : fix_floats

created branch time in 3 months

fork pkositsyn/insane-json

Lighting fast and simple JSON decode/encode library for GO

fork in 3 months