profile
viewpoint

python/python-docs-zh-cn 278

zh_CN translation of the Python documentation

The-Orizon/YubiKeyUserGroup 23

This is a question and answer from yubikey user group

zhsj/dockerfile 16

Personal dockerfiles

zhsj/displaylink 1

Debian package for DisplayLink Linux driver

zhsj/algo 0

Class Project: Intro to Algorithm

zhsj/anbox-docs 0

Documentation for Anbox

zhsj/anbox-modules 0

Anbox kernel modules

zhsj/aptly 0

aptly - Debian repository management tool

startedgrafana/tempo

started time in 4 hours

delete branch zhsj/singularity

delete branch : drop-image-tools

delete time in 3 days

delete branch zhsj/singularity

delete branch : drop-docker

delete time in 3 days

delete branch zhsj/dh-make-golang

delete branch : fix-typo

delete time in 3 days

push eventDebian/dh-make-golang

Shengjing Zhu

commit sha 34a37c9029ecd75f7f92401bf3521caeeed076bb

Change section to golang See https://lists.debian.org/debian-devel-announce/2020/10/msg00005.html

view details

push time in 3 days

delete branch zhsj/dh-make-golang

delete branch : change-section

delete time in 3 days

create barnchzhsj/dh-make-golang

branch : change-section

created branch time in 3 days

push eventzhsj/singularity

Shengjing Zhu

commit sha b07cef75ac18ea9b6d5b99db284b11a3364f2897

Drop the depends on github.com/docker/docker The exit code of os/exec.Command is easy to get, no need to import docker's system package.

view details

push time in 3 days

push eventzhsj/singularity

David Trudgian

commit sha 5332c40a2490b2cad34213fc225c0b712524076a

Allow /etc/localtime & /etc/hosts bind to fail - Fixes: 5465 In `singularity.conf` and hard-coded under `--contain` we bind `/etc/hosts` and `/etc/localtime` to ensure sensible timezone and hostname resolution in the container. In certain circumstances the container may be such that the bind mount onto `/etc/hosts` or `/etc/localtime` fails. This is a fatal error, but it would be nicer just to warn, as the container is likely still usable.

view details

David Trudgian

commit sha 850a48162fc7163b09570830bdd5008983ddad21

Regression test for #5465 Check we can run a container where /etc/hosts & /etc/localtime cannot be bind-mount over.

view details

Shengjing Zhu

commit sha b2736bb87440be0540b6d78b7215b328873843d2

Bump umoci to 0.4.6 This version builds on MacOS

view details

Shengjing Zhu

commit sha 2d42b1f644224945b75e53472106b5bf5b701efc

Drop the depends on github.com/opencontainers/image-tools github.com/opencontainers/image-tools is only used in unpacking rootfs on MacOS, now the function is replaced by umoci, which is same on Linux.

view details

cclerget

commit sha 5ff26b4ed6dec3bc7e6497ce36f7de0efb2d2c09

Merge pull request #5648 from dctrud/issue5465 Allow /etc/localtime & /etc/hosts bind to fail

view details

David Trudgian

commit sha d4feeff03ccd099ea49e8eac4dd76a3ef8ab2bb2

Merge pull request #5655 from zhsj/drop-image-tools Drop the depends on github.com/opencontainers/image-tools

view details

Shengjing Zhu

commit sha 60cb83196b2abf70f1f90ab446b3dfeaaba6b293

Drop the depends on github.com/docker/docker The exit code of os/exec.Command is easy to get, no need to import docker's system package.

view details

push time in 3 days

PR opened hpcng/singularity

Drop the depends on github.com/opencontainers/image-tools

Description of the Pull Request (PR):

First the umoci is upgrade to 0.4.6, a taged version which supports MacOS. Then the internal/pkg/build/sources/oci_unpack_darwin.go is removed.

However it can't be tested, since the MacOS build seems broken for a long time...

This fixes or addresses the following GitHub issues:

  • Fixes #

Before submitting a PR, make sure you have done the following:

Attn: @singularity-maintainers

+4 -48

0 comment

4 changed files

pr created time in 5 days

create barnchzhsj/singularity

branch : drop-image-tools

created branch time in 5 days

PR opened hpcng/singularity

Drop the depends on github.com/docker/docker

Description of the Pull Request (PR):

The exit code of os/exec.Command is easy to get, no need to import docker's system package.

This fixes or addresses the following GitHub issues:

  • Fixes #

Before submitting a PR, make sure you have done the following:

Attn: @singularity-maintainers

+2 -3

0 comment

3 changed files

pr created time in 5 days

push eventzhsj/singularity

Shengjing Zhu

commit sha ba415371ee0d03542adbdf08a9980fcb3fddfaa7

Drop the depends on github.com/docker/docker The exit code of os/exec.Command is easy to get, no need to import docker's system package.

view details

push time in 5 days

create barnchzhsj/singularity

branch : drop-docker

created branch time in 5 days

fork zhsj/singularity

Singularity: Application containers for Linux

https://www.sylabs.io/singularity/

fork in 5 days

pull request commenthashicorp/consul

sdk: read procfs instead of using sysctl command

TestConnectCALeaf_changingRootsBetweenBlockingCalls and TestConnectCALeaf_CSRRateLimiting failed, seems unrelated.

zhsj

comment created time in 5 days

pull request commenthashicorp/consul

sdk: read procfs instead of using sysctl command

I didn't change the ephemeral_darwin.go since I don't have a mac. But it could be updated as well. Try strace -e file sysctl -n to see what file sysctl will read.

zhsj

comment created time in 5 days

PR opened hashicorp/consul

sdk: read procfs instead of using sysctl command

This drops the dependency of sysctl command

+4 -5

0 comment

1 changed file

pr created time in 5 days

create barnchzhsj/consul

branch : sysctl

created branch time in 5 days

fork zhsj/consul

Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.

https://www.consul.io

fork in 5 days

startedmikecao/umami

started time in 6 days

pull request commentcontainerd/containerd

Zero out buildid to make builds reproducible

@zhsj I think, neither Debian nor Archlinux try builds in 1-core VMs. Only I do for openSUSE. As far as I know, they only vary -j $n to $n-1

the typical go variation for me looks like this then: https://rb.zq1.de/compare.factory-20201001/katacontainers-compare.out

in https://github.com/kubernetes/kubernetes/issues/70131#issuecomment-585603403 you said it was built with go1.13. However iirc the reproducible build for Go is improved in go1.14.

And have you opened issue for Go upstream? If -jN will affect the result, it really should be fixed in Go upstream.

utkarsh2102

comment created time in 6 days

pull request commentcontainerd/containerd

Zero out buildid to make builds reproducible

As well as archlinux https://github.com/archlinux/svntogit-community/blob/packages/containerd/trunk/PKGBUILD just use -trimpath and is reproducible-build https://tests.reproducible-builds.org/archlinux/community/containerd/containerd-1.4.1-1-x86_64.pkg.tar.zst.html

utkarsh2102

comment created time in 7 days

pull request commentcontainerd/containerd

Zero out buildid to make builds reproducible

As https://github.com/golang/go/issues/33772 is fixed in Go1.14. I'm curious why it is still problem for buildid?

And as show in https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/containerd.html it's reproducible on amd64 and i386. Though we don't use upstream Makefile, but we don't set buildid to null, just -trimpath.

utkarsh2102

comment created time in 7 days

issue openedgo-delve/delve

Test failed on arm64: TestCgoStacktrace and TestCgoEval

  1. What version of Delve are you using (dlv version)?
$ git log --oneline -1
9a3c9eba (HEAD -> master, origin/master, origin/HEAD) proc/*: add launch option to disable ASLR (#2202)
  1. What version of Go are you using? (go version)?
$ go version
go version go1.15.2 linux/arm64
  1. What operating system and processor architecture are you using?
$ cat /etc/os-release 
PRETTY_NAME="Debian GNU/Linux bullseye/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
$ lscpu
Architecture:        aarch64
Byte Order:          Little Endian
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
NUMA node(s):        1
Vendor ID:           APM
Model:               1
Model name:          X-Gene
Stepping:            0x0
BogoMIPS:            100.00
NUMA node0 CPU(s):   0-3
Flags:               fp asimd evtstrm cpuid
  1. What did you do?

I'm going to package delve for Debian. But the tests fail on arm64. https://buildd.debian.org/status/fetch.php?pkg=delve&arch=arm64&ver=1.5.0-4&stamp=1603213253&raw=0

It's also reproducible with master.

  1. What did you expect to see?

The tests succeed.

  1. What did you see instead?
(sid_arm64-dchroot)zhsj@amdahl:~/t/delve$ go test -mod=vendor -v ./service/test/ -run TestCgoEval                                                                          
=== RUN   TestCgoEval
    support.go:248: enabling recording for github.com/go-delve/delve/service/test_test.TestCgoEval                                                                         
    variables_test.go:68: Expected "\"a string\"" got "(unreadable could not read string at 0x8020080280200802 due to input/output error)" (for variable s)                
--- FAIL: TestCgoEval (1.71s)
FAIL
FAIL    github.com/go-delve/delve/service/test  1.738s
FAIL
(sid_arm64-dchroot)zhsj@amdahl:~/t/delve$ go test -mod=vendor -v ./pkg/proc -run TestCgoStacktrace                                                                          
=== RUN   TestCgoStacktrace
    proc_test.go:3347: iteration step 0
    proc_test.go:3211:  0x48ddf0 -0x90 -0xb8 main.main at main.go:13
    proc_test.go:3211:  0x430d7c -0x30 -0x13898 runtime.main at proc.go:204
    proc_test.go:3211:  0x45c574 -0x30 -0x4000044000 runtime.goexit at asm_arm64.s:1136
    proc_test.go:3347: iteration step 1
    proc_test.go:3211:  0x48e178 0xffffcd2f5660 0xffffcd2f5650 C.helloworld_pt2 at hello.c:15
    proc_test.go:3211:  0x48e1a8 0xffffcd2f5680 0xffffcd2f5670 C.helloworld at hello.c:19
    proc_test.go:3211:  0x48e130 0xffffcd2f56a0 0xffffcd2f5690 C._cgo_03f30c882f33_Cfunc_helloworld at cgo-gcc-prolog:50
    proc_test.go:3211:  0x45c33c -0x4000043f48 -0x4000044000 runtime.asmcgocall at asm_arm64.s:922
    proc_test.go:3211:  0x0 0x0 0x0 ? at .:0
    proc_test.go:3266: couldn't find frame 2 [C.helloworld_pt2 C.helloworld main.main]
    proc_test.go:3267: expected: [C.helloworld_pt2 C.helloworld main.main]
    proc_test.go:3392: see previous loglines
--- FAIL: TestCgoStacktrace (2.01s)
=== RUN   TestCgoStacktrace2
    proc_test.go:75: skipped on arm64: broken
--- SKIP: TestCgoStacktrace2 (0.00s)
FAIL
FAIL    github.com/go-delve/delve/pkg/proc      2.050s
FAIL

created time in 7 days

issue commentustclug/mirrorrequest

【镜像请求】 k8s.gcr.io 容器镜像源

https://github.com/ustclug/mirrorrequest/issues/91 https://github.com/ustclug/discussions/issues/309 https://github.com/ustclug/mirrorrequest/issues/276

lework

comment created time in 7 days

issue closedsquare/go-jose

TestJWSWithCertificateChain failed with go1.15

=== RUN   TestJWSWithCertificateChain
    jws_test.go:615: failed to verify certificate chain for test case 0: x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0
--- FAIL: TestJWSWithCertificateChain (0.00s)

closed time in 10 days

zhsj

startedcpuguy83/go-docker

started time in 10 days

push eventzhsj/test

zhsj

commit sha d02c1b295e1c3c0fe8c4d7f7b0fb59b9076f56a7

Create SECURITY.md

view details

push time in 14 days

push eventzhsj/test

zhsj

commit sha f31268b1054c6d80ed21f045ac311eed83bfcb1c

Update README.rst

view details

zhsj

commit sha 03297e665df11ff1cf6e424c895e1f7dd2466f4f

Merge pull request from GHSA-6q4h-32hc-v3w5 Update README.rst

view details

push time in 14 days

startedlf-edge/eve

started time in 14 days

startedkaiakz/rsync-os

started time in 16 days

issue commentcontainerd/containerd

Possibility to define runtime dependencies

Could you just use ctr run --rm -t private.registry/crictl-image:latest --some-options some-args ?

danielfoehrKn

comment created time in 18 days

delete branch zhsj/elvish

delete branch : typo

delete time in 18 days

startedroboll/helmfile

started time in 20 days

startedscreego/server

started time in 20 days

delete branch zhsj/pprof

delete branch : patch-1

delete time in 20 days

push eventzhsj/bplayer

Shengjing Zhu

commit sha 028830bea9619323ec14f3d4641d114ec33a19e7

refactor

view details

push time in 21 days

PR closed google/pprof

Reviewers
Only run TestDisasm on amd64 cla: yes

It seems objdump is not able to dump other architecture object.

+2 -2

8 comments

1 changed file

zhsj

pr closed time in 21 days

pull request commentgoogle/pprof

Only run TestDisasm on amd64

llvm-objdump works.

zhsj

comment created time in 21 days

pull request commentgoogle/pprof

Only run TestDisasm on amd64

on x86 system, it seems objdump can't dump arm64 as well.

$ cat a.c 
void main(){}
$ aarch64-linux-gnu-gcc a.c 
$ file a.out 
a.out: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=d65928b56beaf07019c6d04159c7e0ed28a7917f, for GNU/Linux 3.7.0, not stripped
$ /usr/bin/objdump --disassemble-all --demangle --no-show-raw-insn --line-numbers --start-address=0x0 --stop-address=0xffffffffffffffff a.out 

a.out:     file format elf64-little

/usr/bin/objdump: can't disassemble for architecture UNKNOWN!

$

$ objdump --version
GNU objdump (GNU Binutils for Debian) 2.35.1
Copyright (C) 2020 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) any later version.
This program has absolutely no warranty.

$ uname -a
Linux zhsj-debian 5.8.0-1-amd64 #1 SMP Debian 5.8.7-1 (2020-09-05) x86_64 GNU/Linux
zhsj

comment created time in 21 days

pull request commentgoogle/pprof

Only run TestDisasm on amd64

I'm on arm.

$ uname -a
Linux abel 4.19.0-11-armmp-lpae #1 SMP Debian 4.19.146-1 (2020-09-17) armv7l GNU/Linux

$ objdump --version
GNU objdump (GNU Binutils for Debian) 2.35.1
Copyright (C) 2020 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) any later version.
This program has absolutely no warranty.

$ cat /etc/os-release 
PRETTY_NAME="Debian GNU/Linux bullseye/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
zhsj

comment created time in 21 days

PullRequestEvent

pull request commentgoogle/pprof

Only run TestDisasm on amd64

Not really fixed...

Still failing

=== RUN   TestDisasm
    binutils_test.go:205: Disasm: unexpected error [/usr/bin/objdump --disassemble-all --demangle --no-show-raw-insn --line-numbers --start-address=0x0 --stop-address=0xffffffffffffffff testdata/exe_linux_64]: exit status 1
--- FAIL: TestDisasm (0.04s)
=== RUN   TestDisasmIntelSyntax
    binutils_test.go:228: This test only works on x86_64 Linux or macOS as it tests Intel asm syntax
--- SKIP: TestDisasmIntelSyntax (0.00s)
/usr/bin/objdump: testdata/exe_linux_64: file format not recognized
zhsj

comment created time in 21 days

create barnchzhsj/pprof

branch : patch-1

created branch time in 21 days

delete branch zhsj/pprof

delete branch : patch-1

delete time in 22 days

PR closed google/pprof

Only run TestDisasm on amd64 cla: yes

It seems objdump is not able to dump other architecture object.

+2 -2

1 comment

1 changed file

zhsj

pr closed time in 22 days

pull request commentgoogle/pprof

Only run TestDisasm on amd64

hmm, I'm not using master, it has been fixed.

zhsj

comment created time in 22 days

push eventzhsj/pprof

Shengjing Zhu

commit sha 924778fab6709b7b623f50fd73520cc52882dbed

Only run TestDisasm on amd64 It seems objdump is not able to dump other architecture object.

view details

push time in 22 days

PR opened google/pprof

Only run TestDisasm on amd64

It seems objdump is not able to dump other architecture object.

+2 -2

0 comment

1 changed file

pr created time in 22 days

push eventzhsj/pprof

Shengjing Zhu

commit sha 354b0a0ace6866bb1f6ada3e2c78cee42602f049

Only run TestDisasm on amd64 It seems objdump is not able to dump other architecture object.

view details

push time in 22 days

push eventzhsj/pprof

zhsj

commit sha d8378b1ddf88c895b197b043d50347c0790fe47c

Only run TestDisasm on amd64 It seems objdump is not able to dump other architecture object.

view details

push time in 22 days

fork zhsj/pprof

pprof is a tool for visualization and analysis of profiling data

fork in 22 days

delete branch zhsj/packer

delete branch : drop-osext

delete time in 23 days

PR opened hashicorp/packer

Replace kardianos/osext with stdlib

os.Executable is available since go1.8 https://github.com/kardianos/osext/blob/master/osext_go18.go

kardianos/osext is still in go.mod, because the old version of panicwrap needs this.

+4 -5

0 comment

2 changed files

pr created time in 23 days

create barnchzhsj/packer

branch : drop-osext

created branch time in 23 days

push eventzhsj/elvish

Shengjing Zhu

commit sha e7cc81f092bc46c9b30a78c2b5349df55ecb2e23

Fix typos found by codespell

view details

push time in 24 days

PR opened elves/elvish

Fix typos found by codespell
+84 -84

0 comment

35 changed files

pr created time in 24 days

push eventzhsj/elvish

Shengjing Zhu

commit sha d42617e946d4e19274ac76ad0650d999d0a50975

Fix typos found by codespell

view details

push time in 24 days

create barnchzhsj/elvish

branch : typo

created branch time in 24 days

issue openedcirconus-labs/circonus-gometrics

Test failed on Go 1.15

--- FAIL: TestNew (0.00s)
    circonus-gometrics_test.go:65: invalid config (none)
    circonus-gometrics_test.go:74: no API token, no submission URL
    circonus-gometrics_test.go:84: no API token, submission URL only
    circonus-gometrics_test.go:109: no Log, Debug = true
    circonus-gometrics_test.go:121: flush interval [good]
    circonus-gometrics_test.go:132: flush interval [bad]
    circonus-gometrics_test.go:143: Expected parsing flush interval: time: invalid duration thirty seconds got 'parsing flush interval: time: invalid duration "thirty seconds"'
FAIL

created time in 24 days

issue commentgolang/go

cmd/compile: ICE: panic during late deadcode while compiling (*ServeMux).shouldRedirectRLocked

I find a machine which I can access, which has same CPU(Marvell Armada 370/XP CPU @ 1.6GHz on a Marvell MV78460 SoC Development Board (ARM v7)) https://db.debian.org/machines.cgi?host=abel But I can't reproduce the ICE.

zhsj

comment created time in 25 days

issue openedsquare/go-jose

TestJWSWithCertificateChain failed with go1.15

=== RUN   TestJWSWithCertificateChain
    jws_test.go:615: failed to verify certificate chain for test case 0: x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0
--- FAIL: TestJWSWithCertificateChain (0.00s)

created time in 25 days

issue commentjson-iterator/go

Go 1.15

One test is failing with go1.15

    --- FAIL: Test_symmetric/map[test.stringKeyType]string (0.00s)
taowen

comment created time in 25 days

issue commentgolang/go

runtime: ICE: panic during late deadcode while compiling (*ServeMux).shouldRedirectRLocked

How repeatable is this error? Can you get it to happen on two different machines? It would be nice to eliminate the machine itself.

I don't have access to these builders. When I trigger a rebuild, it goes to another machine, which is an arm64 hardware.

The log is https://buildd.debian.org/status/logs.php?pkg=packer&ver=1.6.4%2Bdfsg-2&arch=armhf The failed machine is https://db.debian.org/machines.cgi?host=henze

I will try to see if I can get access to similar hardware.

zhsj

comment created time in 25 days

issue openedgolang/go

ICE: panic during late deadcode while compiling (*ServeMux).shouldRedirectRLocked

<!-- Please answer these questions before submitting your issue. Thanks! For questions please use one of our forums: https://github.com/golang/go/wiki/Questions -->

What version of Go are you using (go version)?

<pre> $ go version 1.15.2 </pre>

Does this issue reproduce with the latest release?

What operating system and processor architecture are you using (go env)?

<details><summary><code>go env</code> Output</summary><br><pre> $ go env

</pre></details>

What did you do?

When building packer on Debian armhf machines, we face an ICE. https://buildd.debian.org/status/fetch.php?pkg=packer&arch=armhf&ver=1.6.4%2Bdfsg-2&stamp=1601746051&raw=0

# net/http
/usr/lib/go-1.15/src/net/http/server.go:2318:14: internal compiler error: '(*ServeMux).shouldRedirectRLocked': panic during late deadcode while compiling (*ServeMux).shouldRedirectRLocked:

runtime error: makeslice: cap out of range

goroutine 39 [running]:
cmd/compile/internal/ssa.Compile.func1(0x342d71c, 0x558e300)
	/usr/lib/go-1.15/src/cmd/compile/internal/ssa/compile.go:48 +0x7c
panic(0x760ce8, 0x89eae0)
	/usr/lib/go-1.15/src/runtime/panic.go:969 +0x118
cmd/compile/internal/ssa.ReachableBlocks(0x558e300, 0xa6b000b8, 0x1, 0x3)
	/usr/lib/go-1.15/src/cmd/compile/internal/ssa/deadcode.go:23 +0x38
cmd/compile/internal/ssa.deadcode(0x558e300)
	/usr/lib/go-1.15/src/cmd/compile/internal/ssa/deadcode.go:181 +0x40
cmd/compile/internal/ssa.Compile(0x558e300)
	/usr/lib/go-1.15/src/cmd/compile/internal/ssa/compile.go:93 +0x98c
cmd/compile/internal/gc.buildssa(0x1f395f0, 0x3, 0x0)
	/usr/lib/go-1.15/src/cmd/compile/internal/gc/ssa.go:460 +0xbf4
cmd/compile/internal/gc.compileSSA(0x1f395f0, 0x3)
	/usr/lib/go-1.15/src/cmd/compile/internal/gc/pgen.go:317 +0x3c
cmd/compile/internal/gc.compileFunctions.func2(0x30171c0, 0x1ae2e50, 0x3)
	/usr/lib/go-1.15/src/cmd/compile/internal/gc/pgen.go:382 +0x38
created by cmd/compile/internal/gc.compileFunctions
	/usr/lib/go-1.15/src/cmd/compile/internal/gc/pgen.go:380 +0x100

It uses external link, other settings are standard.

GOFLAGS := -ldflags=-linkmode=external

We choose to use external link, because previously(when we still use go1.14) we meet link error, but it's another issue.

# armel/armhf fail to link:
# os/user(.text): direct call too far: .plt 87db4e

It's hard for me to reproduce locally and to write down a detailed issue, since it happens on an armhf machine, . But since it's an ICE, so I report here anyway, maybe you will know something from the trace.

What did you expect to see?

What did you see instead?

created time in a month

issue commentustclug/mirrorhelp

Please add golang settings help page support

We only provide golang compiler installer or prebuild compiler. I'm not sure what kind of instructions we should provide...

Please be noted that we don't provide Go libraries proxy. You may need https://github.com/ustclug/mirrorrequest/issues/225 and many alternatives are listed in that issue.

snowman

comment created time in a month

startedearthly/earthly

started time in a month

startedmingrammer/diagrams

started time in a month

push eventzhsj/go-transition

Shengjing Zhu

commit sha 68861bf1e715671c99ffc22cb8aef8bbd867d6de

add golang-pseudo package

view details

push time in a month

push eventzhsj/go-transition

Shengjing Zhu

commit sha db40e8fe48aa41bb7f7c02282e8275e0f3181844

add golang-pseudo package

view details

push time in a month

fork zhsj/seldon-core

An MLOps framework to package, deploy, monitor and manage thousands of production machine learning models

https://www.seldon.io/tech/products/core/

fork in a month

issue commentmoby/sys

drop freebsd support?

https://cirrus-ci.org/guide/FreeBSD/ it supports freebsd, and free for public repos.

kolyshkin

comment created time in a month

push eventzhsj/bplayer

Shengjing Zhu

commit sha ac13d1439b769e28cf02f804e2edf11f2a23620a

add acfun

view details

push time in a month

push eventzhsj/bplayer

Shengjing Zhu

commit sha 58ad3dc4a5571b74599f001e6f54f3856260caa3

bump you-get

view details

Shengjing Zhu

commit sha 99ade46facf68e65a9961880883918f4a5e37ba6

fix video quality sort

view details

push time in a month

startedgnif/LookingGlass

started time in a month

PR merged Debian/dh-make-golang

Add travis jobs on ppc64le

This PR adds power support on travis

+1 -0

0 comment

1 changed file

dineshks1

pr closed time in a month

push eventDebian/dh-make-golang

dineshks1

commit sha b184ad3ae3fcfe750233b89db0ea4eacfa0759d2

Add travis jobs on ppc64le

view details

push time in a month

PullRequestReviewEvent

startedfelixge/httpsnoop

started time in a month

startedJoxit/docker-registry-ui

started time in a month

startedsahlberg/libnfs

started time in a month

issue commentgolang/go

gccgo: no Go files in /usr/src/golang.org/x/net/http/httpguts

Probably it's same as #41368

I just found someone is trying to build containerd with gollvm, then I double checked the gccgo build result. We build go packages with gccgo on ppc64 in Debian. https://buildd.debian.org/status/logs.php?pkg=containerd&arch=ppc64

zhsj

comment created time in a month

issue openedgolang/go

gccgo: no Go files in /usr/src/golang.org/x/net/http/httpguts

What version of Go are you using (go version)?

go version go1.14.6 gccgo (Debian 10.2.0-7) 10.2.0 linux/amd64

and

go version go1.15rc2 gccgo (Debian 20200809-1) 11.0.0 20200809 (experimental) [master revision fb9e3f79464:8ad857c7881:94d4f4387de8264ee289cf71f692d59ca6ac36f8] linux/amd64

Does this issue reproduce with the latest release?

What operating system and processor architecture are you using (go env)?

<details><summary><code>go env</code> Output</summary><br><pre> $ go env

</pre></details>

What did you do?

$ ls $GOPATH/src/golang.org/x/net/http/httpguts
guts.go  httplex.go  httplex_test.go

$ export GO111MODULE=off

$ cat test.go
package main

import (
        _ "golang.org/x/net/http/httpguts"
)

func main() {}

$ go run test.go

What did you expect to see?

go run test.go without error

What did you see instead?

go build golang.org/x/net/http/httpguts: no Go files in /usr/src/golang.org/x/net/http/httpguts

It happens with GOPATH, and GO111MODULE=off, and without vendor dir.

created time in a month

issue commentgolang/go

gccgo: undefined reference when linking

Hi,

Could this be backported to gcc10? It seems that Debian will use gcc10 for its next stable release.

zhsj

comment created time in a month

issue commentcontainerd/continuity

Errophone auto-generated constants, for Go standard library (gollvm)

https://github.com/golang/go/issues/41404 it says it's fixed in libgo.

advancedwebdeveloper

comment created time in a month

push eventzhsj/packages-test

Shengjing Zhu

commit sha 7a99f9f53dac45caa6747121bd6c15538e7e5690

Fix install kubernetes

view details

push time in a month

pull request commentcontainerd/cri

[1.3 - DO NOT MERGE] User namespace support

It is same as https://github.com/rootless-containers/usernetes?

And maybe https://github.com/kubernetes/enhancements/pull/1371 should replace Kubernetes Node-Level User Namespaces Design Proposal

mauriciovasquezbernal

comment created time in a month

startedburrowers/garble

started time in a month

startedmvdan/sh

started time in a month

startedfoxcpp/maddy

started time in a month

startedindigo-dc/udocker

started time in 2 months

issue commentkubernetes-sigs/kustomize

PersistentVolume claimRef is not templated by kustomize

==> kustomization.yaml <==
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

namespace: demo

resources:
  - persistentvolume.yaml
  - persistentvolumeclaim.yaml

configurations:
  - kustomizeconfig.yaml

==> kustomizeconfig.yaml <==
namespace:
- kind: PersistentVolume
  path: spec/claimRef/namespace
  create: true

==> persistentvolumeclaim.yaml <==
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: demo-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 20Gi
  storageClassName: manual

==> persistentvolume.yaml <==
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: demo-pv
spec:
  accessModes:
    - ReadWriteOnce
  capacity:
    storage: 20Gi
  claimRef:
    name: demo-pvc
    namespace: default
  storageClassName: manual

kubectl kustomize result is:

apiVersion: v1
kind: PersistentVolume
metadata:
  name: demo-pv
spec:
  accessModes:
  - ReadWriteOnce
  capacity:
    storage: 20Gi
  claimRef:
    name: demo-pvc
    namespace: default
  storageClassName: manual
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: demo-pvc
  namespace: demo
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 20Gi
  storageClassName: manual

But the expected result is:

...
  claimRef:
    name: demo-pvc
    namespace: demo
...

I think the pv resource is skiped in https://github.com/kubernetes-sigs/kustomize/blob/v2.0.3/pkg/transformers/namespace.go#L39

However the master version of kustomize seems ok.

PacoDu

comment created time in 2 months

startedstapelberg/airscan

started time in 2 months

startedgoogle/addlicense

started time in 2 months

startedgwuhaolin/livego

started time in 2 months

issue openedtuna/issues

镜像常见docker image

https://github.com/ustclug/mirrorrequest/issues/276

理论上可以把每个 docker image 当成独立的软件、系统,按需镜像,而不是反代整个 docker hub 或者整个 gcr。目前 skopeo 等工具的出现,也让这个方法变得可行。

created time in 2 months

starteddeviceplane/deviceplane

started time in 2 months

issue commentmoby/moby

Test failed: TestTarUntarWithXattr

See libcap2 changes in 2.42

https://manpages.debian.org/unstable/libcap-dev/cap_to_text.3.en.html shows

$ ./a.out "cap_chown=p cap_chown+e" caps_to_text() returned "cap_chown=ep"

https://manpages.debian.org/buster/libcap-dev/cap_to_text.3.en.html shows

$ ./a.out "cap_chown=p cap_chown+e" caps_to_text() returned "= cap_chown+ep"

zhsj

comment created time in 2 months

issue openedmoby/moby

Test failed: TestTarUntarWithXattr

<!-- If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

For more information about reporting issues, see https://github.com/moby/moby/blob/master/CONTRIBUTING.md#reporting-other-issues


GENERAL SUPPORT INFORMATION

The GitHub issue tracker is for bug reports and feature requests. General support for docker can be found at the following locations:

  • Docker Support Forums - https://forums.docker.com
  • Slack - community.docker.com #general channel
  • Post a question on StackOverflow, using the Docker tag

General support for moby can be found at the following locations:

  • Moby Project Forums - https://forums.mobyproject.org
  • Slack - community.docker.com #moby-project channel
  • Post a question on StackOverflow, using the Moby tag

BUG REPORT INFORMATION

Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST -->

Description

<!-- Briefly describe the problem you are having in a few paragraphs. -->

TestTarUntarWithXattr failed

Steps to reproduce the issue:

  1. sudo ./archive.test -test.v -test.run TestTarUntarWithXattr

Describe the results you received:

=== RUN   TestTarUntarWithXattr
    archive_unix_test.go:268: assertion failed: string "/tmp/docker-test-untar-origin160961326/2 cap_block_suspend=ep\n" does not contain "= cap_block_suspend+ep": untar should have kept the 'security.capability' xattr
    archive_unix_test.go:268: assertion failed: string "/tmp/docker-test-untar-origin160961326/2 cap_block_suspend=ep\n" does not contain "= cap_block_suspend+ep": untar should have kept the 'security.capability' xattr
--- FAIL: TestTarUntarWithXattr (0.01s)
FAIL

Describe the results you expected:

no failure

Additional information you deem important (e.g. issue happens only occasionally):

Kernel: Linux debian 5.7.0-2-amd64 #1 SMP Debian 5.7.10-1 (2020-07-26) x86_64 GNU/Linux libcap2: 2.43

Output of docker version:

(paste your output here)

Output of docker info:

(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):

created time in 2 months

more