Package: golang-github-gin-gonic-gin / 1.6.3-4

Metadata

Package Version Patches format
golang-github-gin-gonic-gin 1.6.3-4 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
0001 adjust test parameters.patch | (download)

gin_integration_test.go | 10 8 + 2 - 0 !
1 file changed, 8 insertions(+), 2 deletions(-)

 adjust test parameters

For now, make it possible to set an alternative location (to /tmp) for
the test (UNIX) socket.

Signed-off-by: Cyril Brulebois <cyril@debamax.com>

0002 binding avoid 2038 problem on 32 bit architectures.patch | (download)

binding/form_mapping.go | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 [patch] binding: avoid 2038 problem on 32-bit architectures (#2450)

Function setTimeField calls strconv.ParseInt with bit size 0 when
parsing Unix time, which means it is equivalent to specifying 32 on
32-bit architectures. This causes the function to suffer from the year
2038 problem. To fix it and keep the behavior the same on both 32-bit
and 64-bit architectures, explicitly specify bit size 64.

Co-authored-by: thinkerou <thinkerou@gmail.com>

0003 avoid failures on flaky test.patch | (download)

path_test.go | 5 4 + 1 - 0 !
1 file changed, 4 insertions(+), 1 deletion(-)

 avoid failures on flaky test

The TestPathCleanMallocs test fails sometimes (and could also be an
incentive for using -short), but Shengjing Zhu agrees we shouldn't
abort when that happens.

Replace the assert with a warning message if the results don't match
expectations, so that we still have access to this information if we
need it.

Suggested-by: Shengjing Zhu <zhsj@debian.org>
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
0004 fix test failure with go 1.17.patch | (download)

context_1.16_test.go | 31 31 + 0 - 0 !
context_1.17_test.go | 33 33 + 0 - 0 !
context_test.go | 13 0 + 13 - 0 !
3 files changed, 64 insertions(+), 13 deletions(-)

 fix ftbfs with go 1.17
 Go 1.17 has multiple changes to mime/multipart and net/http that were causing
 one of the build-time tests to panic rather than exit cleanly as expected.
 See https://golang.org/doc/go1.17 for more information