id
int64 393k
2.82B
| repo
stringclasses 68
values | title
stringlengths 1
936
| body
stringlengths 0
256k
โ | labels
stringlengths 2
508
| priority
stringclasses 3
values | severity
stringclasses 3
values |
|---|---|---|---|---|---|---|
443,908,498 | go | runtime: occasional hangs in TestCgoCallbackGC | Looks like the test hung for some reason.
https://build.golang.org/log/e9e9a00d8fbae5c7ffb803d871b86982849c08ea
<details>
```
--- FAIL: TestCgoCallbackGC (60.03s)
crash_test.go:95: testprogcgo CgoCallbackGC exit status: exit status 2
crash_cgo_test.go:70: expected "OK\n", but got:
SIGQUIT: quit
PC=0x1005d49c m=0 sigcode=0
goroutine 0 [idle]:
runtime.futex(0x101f8a08, 0x80, 0x0, 0x0, 0x0, 0x0, 0x10033d90, 0x10035fc8, 0x10033de8, 0x100000081, ...)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/sys_linux_ppc64x.s:472 +0x1c
runtime.futexsleep(0x101f8a08, 0x0, 0xffffffffffffffff)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/os_linux.go:44 +0x3c
runtime.notesleep(0x101f8a08)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/lock_futex.go:151 +0xb8
runtime.stopm()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/proc.go:1928 +0xb8
runtime.startlockedm(0xc0000c1800)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/proc.go:2098 +0x78
runtime.schedule()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/proc.go:2561 +0x60
runtime.exitsyscall0(0xc0000c2480)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/proc.go:3135 +0x140
runtime.mcall(0xc0000c2480)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/asm_ppc64x.s:202 +0x58
goroutine 1 [chan receive]:
main.CgoCallbackGC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:90 +0x134
main.main()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/main.go:34 +0x198
goroutine 17 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 19 [syscall]:
os/signal.signal_recv(0x0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/sigqueue.go:139 +0xf8
os/signal.loop()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/os/signal/signal_unix.go:23 +0x24
created by os/signal.init.0
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/os/signal/signal_unix.go:29 +0x3c
goroutine 163 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 162 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 161 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 159 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 158 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 157 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 156 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 155 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 154 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 164 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 185 [runnable]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 153 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 150 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 146 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 145 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 144 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 143 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 142 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 141 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 138 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 136 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 133 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 132 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 130 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 128 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 123 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 184 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 182 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 181 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 180 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 179 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 178 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 177 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 176 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 175 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 174 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 173 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 172 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 170 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 169 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 168 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 167 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 165 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 152 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 186 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 187 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 188 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 189 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 190 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 191 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 192 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 193 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 194 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 195 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 196 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 197 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 198 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 199 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 200 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 201 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 202 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 203 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 204 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 205 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 206 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 207 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 208 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 209 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 210 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 211 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 212 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 213 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 214 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 215 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 216 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 217 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 218 [syscall]:
main._Cfunc_foo()
_cgo_gotypes.go:211 +0x40
main.CgoCallbackGC.func2(0xc0000700c0)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:85 +0x24
created by main.CgoCallbackGC
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:84 +0x104
goroutine 226 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 231 [runnable, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 232 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 241 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 242 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 245 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 246 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 247 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 248 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 249 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 250 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 254 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 257 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 258 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 259 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 260 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 261 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 262 [running, locked to thread]:
goroutine running on other thread; stack unavailable
goroutine 263 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 264 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 265 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 266 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 267 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 268 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 269 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 270 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 272 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 273 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 274 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 275 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 276 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 279 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 280 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 281 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 282 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 283 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 284 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 285 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 286 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 287 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 288 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 289 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 291 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 292 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 293 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 295 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:44 +0x58
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 296 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 297 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 298 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 299 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 300 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 301 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 302 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 303 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 304 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 305 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 306 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 307 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 308 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 309 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 310 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 311 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 312 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 313 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 314 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 315 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 316 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 317 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 318 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 319 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 320 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 321 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 322 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 323 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
goroutine 324 [semacquire, locked to thread]:
runtime.GC()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1064 +0x68
main.go_callback()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/testdata/testprogcgo/callback.go:42 +0x24
main._cgoexpwrap_4097c8f6dac3_go_callback()
_cgo_gotypes.go:403 +0x24
r0 0xdd r1 0x7fffcfae7b08
r2 0x80 r3 0x101f8a08
r4 0x80 r5 0x0
r6 0x0 r7 0x0
r8 0x0 r9 0x0
r10 0x0 r11 0x0
r12 0x0 r13 0x7fff7ff8a810
r14 0x1000c254 r15 0xc0000be678
r16 0x101112ed r17 0xc000023340
r18 0x7fffcfae7950 r19 0x0
r20 0xc00009a018 r21 0x101f88c0
r22 0xc00026ef38 r23 0x0
r24 0x30 r25 0x8
r26 0x0 r27 0x0
r28 0x7fff7ff80000 r29 0x7fff7ff7f6f8
r30 0x101f80e0 r31 0x1000c0e8
pc 0x1005d49c ctr 0x0
link 0x1002b38c xer 0x0
ccr 0x54400882 trap 0xc00
FAIL
FAIL runtime 85.907s
```
</details><br>
CC @aclements @mknyszek | Testing,NeedsInvestigation | medium | Critical |
443,911,446 | go | x/build: increase timeouts or reduce parallelism on darwin-arm-mg912baios builder? | There is a strange effect visible in [this log](https://build.golang.org/log/a5b12928389cb0bdf4e3f3923dd893bddc52e942) on the `darwin-arm-mg912baios` builder.
The tests are running along fine for a while, and when they get to the (presumably CPU-intensive) `hash/*` tests they suddenly dropm from ~150s per test to ~19m per test.
The first couple of `image` tests are similarly slow, but then the builder seems to recover:
```
ok go/parser 89.266s
ok go/printer 93.493s
ok go/scanner 90.741s
ok go/token 91.229s
ok go/types 93.029s
ok hash 95.535s
lldb: running program
PASS
*** Test killed: ran too long (19m0s).
FAIL hash/adler32 1145.074s
ok hash/crc32 1140.671s
ok hash/crc64 1139.541s
ok hash/fnv 1137.713s
ok html 1136.359s
ok html/template 1135.509s
ok image 1133.465s
ok image/color 1135.193s
ok image/draw 91.719s
ok image/gif 95.854s
ok image/jpeg 102.705s
ok image/png 102.427s
```
I wonder if that implies some sort of resource contention (perhaps a thermal limit?) between the tests โ should we reduce the parallelism of that builder to decrease the likelihood of spurious timeouts?
CC @eliasnaur @steeve @bradfitz @dmitshur | Testing,Builders,NeedsInvestigation | low | Major |
443,915,237 | go | runtime: "sweep increased allocation count" on darwin-arm64-corellium builder | From https://build.golang.org/log/f06119002ee0fe160d0b78b3e67ce274e468a96d:
(Note that the failure occurred during bootstrapping, in the `toolchain3` phase.)
This might be blocked on #21729.
<details>
```
darwin-arm64-corellium at ed7a92bab459806c958459264f8c88495ea6c4ba
:: Running /bin/bash with args ["bash" "/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/make.bash"] and env ["SHELL=/bin/sh" "TMUX=/private/var/tmp/tmux-501/default,13591,0" "GOROOT_BOOTSTRAP=/tmp/workdir-host-darwin-arm64-corellium-ios/go1.4" "PWD=/var/mobile" "RSYNC_RSH=ssh" "LOGNAME=mobile" "HOME=/var/mobile" "LANG=en_US.UTF-8" "LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:" "GO_BUILDER_ENV=host-darwin-arm64-corellium-ios" "CLICOLOR=" "SSH_CONNECTION=10.11.3.2 64144 10.11.0.1 22" "TERM=screen" "USER=mobile" "TMUX_PANE=%0" "SHLVL=2" "SSH_CLIENT=10.11.3.2 64144 22" "PATH=/var/mobile/bin:/var/mobile/bin:/var/mobile/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games" "CC=/var/mobile/bin/clangsign" "MAIL=/var/mail/mobile" "SSH_TTY=/dev/ttys001" "_=/var/mobile/go/bin/buildlet" "WORKDIR=/tmp/workdir-host-darwin-arm64-corellium-ios" "GO_BUILDER_NAME=darwin-arm64-corellium" "GOROOT_BOOTSTRAP=/var/mobile/go-darwin-arm64-bootstrap" "GOBIN=" "TMPDIR=/tmp/workdir-host-darwin-arm64-corellium-ios/tmp" "GOCACHE=/tmp/workdir-host-darwin-arm64-corellium-ios/gocache" "GOROOT_BOOTSTRAP=/var/mobile/go-darwin-arm64-bootstrap"] in dir /tmp/workdir-host-darwin-arm64-corellium-ios/go/src
Building Go cmd/dist using /var/mobile/go-darwin-arm64-bootstrap.
Building Go toolchain1 using /var/mobile/go-darwin-arm64-bootstrap.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
warning: unable to find runtime/cgo.a
Building Go toolchain2 using go_bootstrap and Go toolchain1.
Building Go toolchain3 using go_bootstrap and Go toolchain2.
# os
runtime: nelems=3 nalloc=2 previous allocCount=1 nfreed=65535
fatal error: sweep increased allocation count
runtime stack:
runtime.throw(0x1009ed10d, 0x20)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/panic.go:714 +0x4c
runtime.(*mspan).sweep(0x103a5a380, 0x103a5a300, 0x16ff0ab00)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/mgcsweep.go:329 +0x864
runtime.(*mcentral).uncacheSpan(0x101149560, 0x103a5a380)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/mcentral.go:197 +0x114
runtime.(*mcache).releaseAll(0x1017006d0)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/mcache.go:155 +0x68
runtime.(*mcache).prepareForSweep(0x1017006d0)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/mcache.go:182 +0x44
runtime.acquirep(0x130030500)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/proc.go:4114 +0x30
runtime.stopm()
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/proc.go:1930 +0xc0
runtime.gcstopm()
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/proc.go:2125 +0xbc
runtime.schedule()
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/proc.go:2481 +0x430
runtime.goschedImpl(0x130000180)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/proc.go:2625 +0xe0
runtime.gopreempt_m(0x130000180)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/proc.go:2653 +0x30
runtime.newstack()
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/stack.go:1033 +0x1f4
runtime.morestack()
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/runtime/asm_arm64.s:310 +0x70
goroutine 1 [runnable]:
cmd/compile/internal/ssa.(*poset).lookup(0x1303ab400, 0x1309754f0, 0x100000079)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/ssa/poset.go:263 +0xe0
cmd/compile/internal/ssa.(*poset).setOrder(0x1303ab400, 0x1309754f0, 0x130972540, 0x13106cc00, 0xffffffffffffff00)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/ssa/poset.go:865 +0x40
cmd/compile/internal/ssa.(*poset).SetOrderOrEqual(...)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/ssa/poset.go:999
cmd/compile/internal/ssa.(*factsTable).update(0x131097580, 0x1309a8e60, 0x1309754f0, 0x130972540, 0x1, 0x3)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/ssa/prove.go:233 +0x1b14
cmd/compile/internal/ssa.addRestrictions(0x1309a8e60, 0x131097580, 0x1, 0x1309754f0, 0x130972540, 0x3)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/ssa/prove.go:983 +0x6c
cmd/compile/internal/ssa.addBranchRestrictions(0x131097580, 0x1309a8e60, 0x1)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/ssa/prove.go:956 +0x188
cmd/compile/internal/ssa.prove(0x131084580)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/ssa/prove.go:822 +0xbd8
cmd/compile/internal/ssa.Compile(0x131084580)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/ssa/compile.go:92 +0x808
cmd/compile/internal/gc.buildssa(0x1306b9760, 0x0, 0x0)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/gc/ssa.go:288 +0xb10
cmd/compile/internal/gc.compileSSA(0x1306b9760, 0x0)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/gc/pgen.go:297 +0x28
cmd/compile/internal/gc.compile(0x1306b9760)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/gc/pgen.go:276 +0x34c
cmd/compile/internal/gc.funccompile(0x1306b9760)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/gc/pgen.go:221 +0xbc
cmd/compile/internal/gc.Main(0x1009fdbe8)
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/internal/gc/main.go:676 +0x31a4
main.main()
/private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/src/cmd/compile/main.go:51 +0xa8
go tool dist: FAILED: /private/var/tmp/workdir-host-darwin-arm64-corellium-ios/go/pkg/tool/darwin_arm64/go_bootstrap install -gcflags=all= -ldflags=all= -a -i cmd/asm cmd/cgo cmd/compile cmd/link: exit status 2
```
</details><br> | NeedsInvestigation,compiler/runtime | low | Critical |
443,946,429 | go | x/build: linux-amd64-race TryBot straggling | In the TryBot run for https://golang.org/cl/176580 at Patchset 4, most of the TryBots ran relatively quickly (less than 10m), but the `linux-amd64-race` builder took much longer (over 20m).
I'm not sure exactly why it was so slow, but it leads me to believe that there may be something wrong with the sharding for that builder.
(CC @bradfitz @dmitshur @andybons) | Performance,Testing,Builders,NeedsInvestigation | low | Major |
443,969,449 | pytorch | RoiAlignTest.CheckCPUGPUEqual is still flaky | https://circle.pytorch.org/pattern-details.html?pattern_id=86
Previously #8084
CC @yinghai @xkszltl
```
May 14 00:21:35 [ RUN ] RoiAlignTest.CheckCPUGPUEqual
May 14 00:21:37 WARNING: Logging before InitGoogleLogging() is written to STDERR
May 14 00:21:37 W0514 00:21:37.976260 425 init.h:115] Caffe2 GlobalInit should be run before any other API calls.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:221: Failure
May 14 00:21:39 Expected equality of these values:
May 14 00:21:39 y_cpu_vec[max_diff_idx]
May 14 00:21:39 Which is: 101.09059
May 14 00:21:39 y_gpu_vec[max_diff_idx]
May 14 00:21:39 Which is: 0
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 721.8125, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 721.8125,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 2275.1875, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 2275.1875,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 2096.53125, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 2096.53125,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 4172.3125, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 4172.3125,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 6203.2705078125, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 6203.2705078125,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 591.08331298828125, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 591.08331298828125,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1683.916748046875, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 1683.916748046875,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 2437.04150390625, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 2437.04150390625,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1097.0833740234375, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 1097.0833740234375,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 2124.6875, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 2124.6875,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 6226, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 6226,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 3807.91650390625, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 3807.91650390625,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 8495.6669921875, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 8495.6669921875,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 139, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 139,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1715.8333740234375, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 1715.8333740234375,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1678.8748779296875, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 1678.8748779296875,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 12598.4580078125, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 12598.4580078125,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 100.43750762939453, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 100.43750762939453,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 15708.25, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 15708.25,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 71.333335876464844, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 71.333335876464844,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 510.2083740234375, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 510.2083740234375,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1136.6875, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 1136.6875,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 30, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 30,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1689.541748046875, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 1689.541748046875,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 233.9375, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 233.9375,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 16.703125, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 16.703125,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 22944.833984375, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 22944.833984375,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 209.625, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 209.625,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1629, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 1629,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1963.3125, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 1963.3125,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 11.375000953674316, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 11.375000953674316,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 10961.9990234375, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 10961.9990234375,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 5428.7919921875, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 5428.7919921875,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1781.9375, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 1781.9375,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 276.0625, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 276.0625,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 70.416664123535156, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 70.416664123535156,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 375.0625, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 375.0625,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 517.33331298828125, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 517.33331298828125,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 3557.33349609375, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 3557.33349609375,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 320.75, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 320.75,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:39 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:39 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 7591.5, which exceeds 1e-1, where
May 14 00:21:39 y_cpu_vec[max_diff_idx] evaluates to 7591.5,
May 14 00:21:39 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:39 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1364.604248046875, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1364.604248046875,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 6256.75, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 6256.75,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 9761.25, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 9761.25,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1609.75, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1609.75,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1734.979248046875, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1734.979248046875,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1634.91650390625, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1634.91650390625,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1115.1875, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1115.1875,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 82.500007629394531, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 82.500007629394531,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 23338.75, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 23338.75,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 142.125, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 142.125,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 624.0833740234375, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 624.0833740234375,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 2212.5625, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 2212.5625,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 3544.0625, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 3544.0625,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 5507.75, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 5507.75,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1064.5, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1064.5,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1466.3123779296875, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1466.3123779296875,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1587.90625, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1587.90625,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 146.72915649414062, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 146.72915649414062,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 21.375, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 21.375,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 27.125, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 27.125,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1973.229248046875, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1973.229248046875,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 147.25, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 147.25,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 7530.1875, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 7530.1875,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 563.22918701171875, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 563.22918701171875,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 916.75, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 916.75,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 5647.5, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 5647.5,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 405.8333740234375, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 405.8333740234375,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 287.87496948242188, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 287.87496948242188,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 471.4583740234375, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 471.4583740234375,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 14.625, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 14.625,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 297.9375, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 297.9375,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 23657.85546875, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 23657.85546875,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1374.5625, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1374.5625,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 3182, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 3182,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1133.645751953125, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1133.645751953125,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 5989.6669921875, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 5989.6669921875,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1842.895751953125, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1842.895751953125,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 102.02084350585938, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 102.02084350585938,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 4801.5625, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 4801.5625,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 7784.5, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 7784.5,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1116.3125, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1116.3125,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 1967.833251953125, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 1967.833251953125,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 2699.416748046875, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 2699.416748046875,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 12939.45703125, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 12939.45703125,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 /var/lib/jenkins/workspace/caffe2/operators/roi_align_op_gpu_test.cc:262: Failure
May 14 00:21:40 The difference between y_cpu_vec[max_diff_idx] and y_gpu_vec[max_diff_idx] is 292.50003051757812, which exceeds 1e-1, where
May 14 00:21:40 y_cpu_vec[max_diff_idx] evaluates to 292.50003051757812,
May 14 00:21:40 y_gpu_vec[max_diff_idx] evaluates to 0, and
May 14 00:21:40 1e-1 evaluates to 0.10000000000000001.
May 14 00:21:40 [ FAILED ] RoiAlignTest.CheckCPUGPUEqual (5376 ms)
May 14 00:21:40 [----------] 1 test from RoiAlignTest (5376 ms total)
May 14 00:21:40
May 14 00:21:40 [----------] Global test environment tear-down
May 14 00:21:40 [==========] 1 test from 1 test case ran. (5376 ms total)
May 14 00:21:40 [ PASSED ] 0 tests.
May 14 00:21:40 [ FAILED ] 1 test, listed below:
May 14 00:21:40 [ FAILED ] RoiAlignTest.CheckCPUGPUEqual
```
https://circleci.com/gh/pytorch/pytorch/1680769?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
RNG should be deterministic here, I don't know why it is flaking. | caffe2,triaged,module: flaky-tests,better-engineering | low | Critical |
444,013,997 | terminal | Get Performance Tests Working | I've added a performance mode to some of the `conhost.feature.tests.dll` tests and managed to ensure that they do work with the WinPerf infrastructure.
Now I need to finish up and get this running in an automated fashion. I'm pretty sure that WinPerf and the Windows Performance backend services are going to remain private, but that won't necessarily stop us from having an internal build that can orchestrate these and submit bugs that we can then pull back out to GitHub. | Product-Conhost,Area-Performance,Issue-Bug,Area-Build | low | Critical |
444,016,344 | go | spec: document nil checks for value methods | <!-- Please answer these questions before submitting your issue. Thanks! -->
### What version of Go are you using (`go version`)?
<pre>
go version go1.12 linux/amd64
</pre>
### What did you do?
```
package main
import (
"fmt"
)
type S struct {}
func (S) M(n int) {
fmt.Println(n)
}
type T struct {
*S
}
type I interface {
M(n int)
}
func foo() {
var v = &T{}
var i I = v
f := i.M // ok
v.S = &S{}
f(111) // 111
}
func bar() {
var v = &T{}
f := v.M // panic
v.S = &S{}
f(111)
}
func main() {
foo()
bar()
}
```
### What did you expect to see?
Same behavior
### What did you see instead?
Different behaviors.
| Documentation,NeedsInvestigation | low | Major |
444,022,692 | material-ui | Feature Request: Warnings for missing ARIA properties | When rendering certain components such as Menus, Images, etc... it would be awesome if those components that *should* have aria attributes, if they aren't specified would issue `console.warn` statements for non-production builds at render. This should also include input elements that don't have an `id` property, as they don't tether the label to the input component in a way that can be detected in terms of accessibility.
I think that doing this would encourage developers to tackle the low hanging fruit in terms of accessibility. It doesn't have to affect functionality, but the debug warning statements would at least be a significant guidance ahead of tools like Lighthouse, Wave and axe.
Should probably spell out each component that offers menu, menu-like functionality, modals, popovers, images, inputs, etc and note when the feature is added. I'm also not sure which projects externally would need to be coordinated, iirc the svg icons are from an external package. Svg icons themselves could implement a default alternate text attribute with a console.info statement in debug mentioning to use an explicit {''} if no alt text is desired.
Just created a request for effectively the [same feature](https://github.com/facebook/react/issues/15649) for baseline rendering. This should also be implemented for wrapper components with a more explicit context here as well. | accessibility,discussion | low | Critical |
444,052,116 | go | cmd/go: restore ability to see what updates will happen | In 1.12, `go list -u -m all` displays the direct and indirect dependencies of the current module that have available updates, and `go get -u` attempts to update those dependencies.
In #26902, there was a very nice change that narrowed the set of updates that happen for things like `go get -u -m all` (and other variations like `go get -u all`), which now no longer follow the full module-level dependency graph.
However, now it is not easy to see what those updates will be:
* `go list -u -m all` still shows information from the module-level dependency graph.
* updates via `go get -u -m all` or similar pay attention to the package-level import graph to determine what updates actually happen, which is often a subset of what is shown by `go list -u -m all`.
It would be nice if something could be done to make the "what updates are available" and "please do those updates" workflow more consistent and easy to remember.
### Comments from CL 174099 discussion
Moving over some [comments](https://go-review.googlesource.com/c/go/+/174099/11#message-410fe4be2ba9f50420276c3af96edd6526221578) from https://golang.org/cl/174099:
It would be nice if there was some 'go list' invocation that could show the list of available upgrades under the new 'go get' behavior. One could try to do something today on tip by chaining together different commands, such as something like:
```
$ go list -u -m $(go list -deps -test -f '{{with .Module}}{{.Path}}{{end}}')
```
That might be close, but I am not sure if that is correct, and clearly that is not convenient.
Putting the above comments together-- it would be nice if there was a recommended way to do something like:
```
1. go list <some args>
2. go get <same args>
3. go list <same args>
```
and have step 3. report no more upgrades are available. It would be nice if the same exact arguments could be used in each of those steps (although having them be the same arguments might not end up being possible or desirable based on other constraints).
For example, perhaps 'go list -u -m' could be defined in 1.13 to show the upgrades available under the new 'go get -u -m' behavior. That would mean you could do:
```
1. go list -u -m // upgrades listed
2. go get -u -m // upgrades happen
3. go list -u -m // no upgrades listed
```
Alternatively, perhaps the meaning of 'all' for 'go list' could be made to conform to the newly narrower meaning meaning of 'all' for 'go get', and then you could do:
```
1. go list -u -m all // upgrades listed
2. go get -u -m all // upgrades happen
3. go list -u -m all // no upgrades listed
```
Or perhaps there could be some other change to smooth things out here.
Jay [responded](https://go-review.googlesource.com/c/go/+/174099/11#message-dbf9d780d69824e2c447a32a5d18fcfd297ebcb0) in CL 174099:
> I don't think there's a concise command for "check what modules go get -u all" would upgrade. 'go list -m -u all' will list modules that are part of the module graph, but this is a superset of what 'go get -u all' does now. We should probably add a flag to 'go get' that prints what it would do without actually doing it (or maybe we should expand the interpretation of -n). Whatever we do should be consistent with #27005 (same but for 'go mod tidy'). Feel free to open an issue or comment on that one.
### Additional Background
The exact behavior for `go get` might be tweaked further, but in [CL 176902](https://go-review.googlesource.com/c/go/+/176902), the `go get` help currently includes these related excerpts describing the new behavior:
```
The -u flag instructs get to update modules providing dependencies
of packages named on the command line to use newer minor or patch
releases when available.
[...]
The special pattern 'all' has the same meaning whether or not the -m flag is used:
'all' matches packages in the main module and their dependencies,
including test dependencies.
When the -m and -u flags are used together, 'go get' will update
modules providing packages imported by packages in the modules named on
the command line. For example, 'go get -m -u A' will update A and
any module providing packages needed to build packages in A,
not including tests. 'go get -m -u' will update modules providing packages
needed to build packages in the main module. 'go get -u all' also updates
modules providing packages needed to build packages in the main module,
and it also updates modules providing test dependencies.
```
Potentially related: #32037, #32038
CC @bcmills, @jayconrod | NeedsInvestigation,modules | low | Minor |
444,077,058 | pytorch | Statically make `__setstate__` set all attributes/parameters | #20242 added support for `__getstate__` and `__setstate__` on a module which is an alternative to automatically saving all parameters/attributes. This means the user must be initializing all parameters/attributes themselves. Like in TorchScript classes' `__init__()`, we should be statically verifying that this is actually happening.
cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @anjali411 @mruberry | high priority,module: serialization,triaged | low | Minor |
444,111,318 | electron | Allow multiple webRequest handlers | <!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
### Problem Description
<!-- Is your feature request related to a problem? Please add a clear and concise description of what the problem is. -->
There's no way to register multiple `webRequest` events such as `onBeforeRequest`
### Proposed Solution
<!-- Describe the solution you'd like in a clear and concise manner -->
It would be great if Electron could provide normal `EventEmitter` object. For example:
```javascript
session.webRequest.on('before-request', ...)
```
| enhancement :sparkles: | low | Major |
444,132,400 | PowerToys | Trim " in explorer address bar | If I paste a path like โC:\Windowsโ including the โ to the explorer address bar and press enter it opens a browser window instead of navigating to C:\Windows. It would be nice to trim the โ on navigating.
This would also be a benefit to any save or open file dialog.
Another nice feature would be to ignore \\\ within a path to allow pasting paths where \ was escaped. | Idea-New PowerToy | low | Major |
444,144,763 | flutter | Add dependency management support for Windows plugins | We'll need flutter_tool support for adding the native portions of plugins to the build, including fetching dependencies, plugin registrant generation, etc.
This will likely use NuGet for package management, but that needs evaluation. | tool,platform-windows,a: desktop,P2,team-windows,triaged-windows | low | Critical |
444,145,038 | flutter | Decide on a dependency management plan for Linux plugins | We'll need flutter_tool support for adding the native portions of plugins to the build, including fetching dependencies, plugin registrant generation, etc.
How dependency management/fetching will be done for Linux is an open question. | tool,platform-linux,a: desktop,P2,team-linux,triaged-linux | low | Major |
444,150,563 | terminal | Resize reflow tests | I have some note to myself in the internal tracker that resize-with-reflow should probably have a test suite on it. Sure, it's a conhost feature, but it will likely affect the presentation of things through the ConPTY.
We'll probably want to adjust some of the behaviors around resize-with-reflow as we tighten up integration with the PTY and with the Terminal app, and before we make big changes... we should probably have enough tests to convince ourselves that the behavior we currently have is maintained to some degree (or at least changed intentionally, not accidentally).
This was MSFT: 19600272 | Product-Conhost,Area-Interaction,Issue-Task | low | Minor |
444,154,178 | terminal | Create comprehensive word-by-word selection tests | This is ported from MSFT: 19672875.
I don't remember why this exists. I filed this on myself and this is the only information I had.
Maybe I left a to-do item behind somewhere in the code referencing this ID?
It has to have to do with conhost, not with Terminal. | Product-Conhost,Area-Interaction,Issue-Task | low | Minor |
444,158,548 | vscode | Be able disable task detection from tasks.json or override tasks execution | Currently VSCode uses `tasks.json` to detect the tasks. If there is a `FileSystemProvider` registered, it will use it to read `tasks.json`. The problem with that is the tasks may not make sense if they come from something else other than `file:/.../.vscode/tasks.json`. E.g. if the file system provider is of a remote kind (like fetching files from sftp or Live Share), tasks from `tasks.json` most likely won't work locally.
To deal with this scenario, VSCode may provide different options:
1. An ability to override task execution for any tasks from `tasks.json`. This work may be merged into #33523. VSCode should pass along the URI of the original `tasks.json` to the extension code that overrides the task execution.
1. An ability to disable tasks detection from `tasks.json` based on the file scheme. This will be a new API. Alternatively, you can make VSCode respect `tasks.json` only from `file:` scheme and let the extensions opt in other schemes if they so chose.
| feature-request,tasks | low | Major |
444,167,146 | terminal | ReadPendingInput plays unsafe byte/char games with pending data | Ported from MSFT: 18047766.
I fixed an immediate crash bug in MSFT: 17987369 that affected this area, but realized at the time that it's really bad that the `ReadPendingInput` function in the console host is playing games with a void pointer and mix-and-match of byte versus character counting.
This represents investigating what we can do to stop mix/matching the char and byte counts in `ReadPendingInput`.
@adiviness might be working on something like this with his changes to input to support emoji... | Issue-Feature,Product-Conhost,Area-Input,Area-Server | low | Critical |
444,183,224 | go | x/mobile/cmd/gomobile: Mygomobileios.framework/Mygomobileios(go.o)' does not contain bitcode. | <!-- Please answer these questions before submitting your issue. Thanks! -->
### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.12.5 darwin/amd64
gomobile version +32b2708 Thu May 9 16:48:39 2019 +0000 (android,ios); androidSDK=
</pre>
### Does this issue reproduce with the latest release?
Yes
### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
</pre></details>
### What did you do?
gomobile bind -target=ios -tags="ios" -v -ldflags=-w mygomobileios
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
### What did you expect to see?
Success when imported in Xcode and compiled
### What did you see instead?
<pre>
ld: '/mygo/src/mygomobileios/gomobileios_test/Mygomobileios.framework/Mygomobileios(go.o)'
does not contain bitcode.
You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE),
obtain an updated library from the vendor, or disable bitcode for this target.
for architecture arm64
</pre> | NeedsInvestigation,mobile | low | Critical |
444,184,255 | go | cmd/compile: optimize sparse line numbering | In [CL 154617](https://go-review.googlesource.com/c/go/+/154617), @dr2chase wrote:
> I've attempted to speed this up by not using maps, and have not succeeded. I'd rather get correct code in now, speed it up later if I can.
That CL adds about 1.5% to compile time.
This is a reminder issue to optimize.
| ToolSpeed,NeedsInvestigation,compiler/runtime | low | Minor |
444,198,119 | godot | One way platforms don't have consistent collision on edge | **Godot version:**
3.1
**OS/device:**
Windows 8, Toshiba Satellite
**Issue description:**
This is a rehash of closed issue #14724.
One-way `StaticBody2Ds` with rectangular `CollisionShape2Ds` do not consistently detect collision with a `KinematicBody2D` player when the player is on the edge of the platform.
Here is a video demonstrating the issue:
Even at low velocity, sometimes the player falls through the platform.
The player's movement is done by `move_and_slide()`, but the issue is also present when using `move_and_slide_with_snap()`.
**Steps to reproduce:**
1. Create a basic platformer with a rectangular player and a rectangular one-way platform.
2. Position the player atop the one-way platform on an edge.
3. Jump repeatedly until the player falls through.
4. Adjust nearness to edge if you can't reproduce immediately.
**Minimal reproduction project:**
[test_project.zip](https://github.com/godotengine/godot/files/3180551/test_project.zip)
| bug,confirmed,topic:physics | low | Minor |
444,222,720 | puppeteer | [feature request] page.screenshot should not freeze when the page is not focused | <!--
STEP 1: Are you in the right place?
- For general technical questions or "how to" guidance, please search StackOverflow for questions tagged "puppeteer" or create a new post.
https://stackoverflow.com/questions/tagged/puppeteer
- For issues or feature requests related to the DevTools Protocol (https://chromedevtools.github.io/devtools-protocol/), file an issue there:
https://github.com/ChromeDevTools/devtools-protocol/issues/new.
- Problem in Headless Chrome? File an issue against Chromium's issue tracker:
https://bugs.chromium.org/p/chromium/issues/entry?components=Internals%3EHeadless&blocking=705916
For issues, feature requests, or setup troubles with Puppeteer, file an issue right here!
-->
### Steps to reproduce
**Tell us about your environment:**
* Puppeteer version: v1.15/v1.16
* Platform / OS version: osx
* URLs (if applicable): *
* Node.js version: v10.15.0
**What steps will reproduce the problem?**
_Please include code that reproduces the issue._
1. disable headless mode
2. const page1 = browser.newPage(); await page1.goto();
3. const page2 = browser.newPage() ;await page2.goto();
4. await page1.screenshot();
**What is the expected result?**
you know
**What happens instead?**
pages are loaded while stuck right at screenshot. i've tried to comment screenshot and it works fluently. so basically it is all about screenshot.
# my explorations
actually, it is because when the screenshot method runs, the target page is not active nor at front. it could be avoided by turning on headless mode or using locks to assure page.bringToFront called before page.screenshot.
hopefully this could be added to documentation or page.screenshot automatically synchronously calls page.bringToFront.
| feature,confirmed | low | Critical |
444,223,362 | rust | Support Windows path manipulation on other platforms | It'd be nice if the facilities under `std::os` which don't use platform-specific APIs would be available on all platforms. For example, the ability to take a bytestream and construct a Windows path out of it in order to detect whether it is a valid Windows path would be great.
The use case is implementing a check for Git repositories which validates that a path is valid on Windows. The `OsStrExt` to get access to the underlying data as if it were a Windows path would be useful for this (since the check should be able to do its work on any platform).
I suspect that there are other APIs that would be useful for manipulating data as another platform might see it. | T-libs-api,C-feature-request,A-io | low | Major |
444,235,314 | PowerToys | ADD multiple VLAN Support without intel / realtek support | Add possibility to configure VLAN Adapters not only VLAN tagging the "one" interface. | Idea-New PowerToy | low | Minor |
444,350,608 | angular | Prioritize _ngcontent styles over _nghost | <!--๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
Oh hi there! ๐
To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
๐
-->
# ๐ feature request
### Relevant Package
<!-- Can you pin-point one or more @angular/* packages the are relevant for this feature request? -->
<!-- โ๏ธedit: --> This feature request is for @angular/core, I guess
### Description
Angular adds component styles in order it meets the components. It leads to inconsistency of applied styles. Consider two components:
1) Button with hostbinded class `._large` to set size
2) A Card component with Button inside it that has class `.override_size` applied to nested Button that sets a different size
If there was a Button component in the view by the time we load Card, Button styles are already in HEAD and therefore `.override_size` class, having the same specificity, overrides `._large` class, because it comes later.
On the other hand, if Button first appears inside Card, its styles are added to the HEAD later and therefore `._large` class takes over.
Have a look at this Stackblitz demo:
https://stackblitz.com/edit/angular-styles-specificity-bug
_**Note**: please do not think about exact examples I gave, these are just the simplest cases I could think of._
### Describe the solution you'd like
Increase specificity of `_ngcontent` styles as they are typically more important. You would have some styles built in within a component and when you use it later inside some other component โ you add classes to it to specify what styles you need in exactly this usage. Easiest way to do so would be to add `[_ngcontent-X]` attribute selector to styles twice (i.e. `.override_size[_ngcontent-c2][_ngcontent-c2] {`).
### Describe alternatives you've considered
Right now we have to manually increase specificity by either adding tag name before class (i.e. `button-component.override_size`) or with any other way like adding two classes instead of one:
```
.override_size {
&& {
our styles
}
```
so it compiles to `.override_size.override_size` which is not ideal but is the cleanest solution I could think of. Problem is, we have to keep that in mind **all the time we add classes to components** and not just HTML tags. | type: bug/fix,freq1: low,area: core,state: confirmed,core: CSS encapsulation,P3 | low | Critical |
444,383,270 | vue | get error detail when use async component factory | ### What problem does this feature solve?
https://vuejs.org/v2/guide/components-dynamic-async.html#Handling-Loading-State
```
const component = new Promise(function (resolve, reject) {
reject('error detail');
});
```
```
const AsyncComponent = () => ({
// The component to load (should be a Promise)
component: component,
// A component to use while the async component is loading
loading: LoadingComponent,
// A component to use if the load fails
error: ErrorComponent,
// Delay before showing the loading component. Default: 200ms.
delay: 200,
// The error component will be displayed if a timeout is
// provided and exceeded. Default: Infinity.
timeout: 3000
})
```
i want get error detail in `AsyncComponent.error` component, make page friendly
### What does the proposed API look like?
maybe inject error as props to `AsyncComponent.error` ?
<!-- generated by vue-issues. DO NOT REMOVE --> | feature request | low | Critical |
444,422,501 | vue | Triggering a listener of a functional component breaks reactivity in Safari 12.1, if iframe is on the page | ### Version
2.6.10
### Reproduction link
[https://jsfiddle.net/ebgj6fra/2/](https://jsfiddle.net/ebgj6fra/2/)
### Steps to reproduce
- Access the fiddle
- click the "change" button
### What is expected?
*Hello world!* should change to *tada!*
### What is actually happening?
In latest Safari (12.1) on Mac OS, nothing happens, but it works as expected in other browsers.
---
Removing the `iframe` from the page makes the issue go away, as seen here: https://jsfiddle.net/ebgj6fra/3/
Seems like maybe there's a difference in how/when the latest Safari runs the `flushCallbacks`.
Conditionally rendering the iframe (`v-if="myExpression !== null`), triggering the listener inside a `setTimeout` or calling `$forceUpdate` circumvents the issue.
<!-- generated by vue-issues. DO NOT REMOVE --> | bug,browser quirks,has workaround | low | Minor |
444,476,718 | go | encoding/json: interface{} not being stringified when JSON ",string" tag is used | ### What version of Go are you using (`go version`)?
1.12.5 playground
### Does this issue reproduce with the latest release?
yes
### What operating system and processor architecture are you using (`go env`)?
NACL
### What did you do?
https://play.golang.org/p/Q4JdghzkBI-
### What did you expect to see?
interface{} fields that point to integers should be converted to strings when the string tag is used.
The documentation says:
`It applies only to fields of string, floating point, integer, or boolean types`
but it also says:
```
Interface values encode as the value contained in the interface. A nil interface value encodes as the null JSON value.
```
### What did you see instead?
They were not converted to strings. | help wanted,NeedsInvestigation | low | Minor |
444,480,183 | pytorch | c++ torch::nn::Sequential increments count on name errors | ## ๐ Bug
Sequential size() returns incremented count when _push_back_ fails on name errors:
```
torch::nn::Sequential s; size_t n=0;
std::cout << "initial size: " << s->size() << "\n";
ASSERT_THROWS_WITH(
s->push_back("name.with.dot", torch::nn::Linear(3, 4)),
"Submodule name must not contain a dot (got 'name.with.dot')");
ASSERT_THROWS_WITH(
s->push_back("", torch::nn::Linear(3, 4)),
"Submodule name must not be empty");
std::cout << "size after name errors: " << s->size() << "\n";
for(auto&c:s->named_children()) n++;
std::cout << "size of named children: " << n << "\n";
```
prints:
```
initial size: 0
size after name errors: 2
size of named children: 0
``` | module: cpp,triaged | low | Critical |
444,503,466 | TypeScript | JSDoc property on typedef can only extend `Object` type | <!-- ๐จ STOP ๐จ ๐ฆ๐ง๐ข๐ฃ ๐จ ๐บ๐ป๐ถ๐ท ๐จ
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!
Please help us by doing the following steps before logging an issue:
* Search: https://github.com/Microsoft/TypeScript/search?type=Issues
* Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ
Please fill in the *entire* template below.
-->
<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:** 3.4.0-dev.201xxxxx
<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** typedef jsdoc widen extend property
**Code**
```mjs
/**
* @typedef {Array} A
* @property {string} a
*/
/**
* @type {A}
*/
var a;
a.a; // Property 'a' does not exist on type 'any[]'.
/**
* @typedef {any[]} B
* @property {string} b
*/
/**
* @type {B}
*/
var b;
b.b; // Property 'b' does not exist on type 'any[]'.
/**
* @typedef {{}} C
* @property {string} c
*/
/**
* @type {C}
*/
var c;
c.c; // Property 'c' does not exist on type '{}'.
/**
* @typedef {Object} O
* @property {string} o
*/
/**
* @type {O}
*/
var o;
o.o; // string
```
**Expected behavior:**
Other types to behave similarly? I thought non-alias typedefs would act like
```ts
type __X = {}; // from @typedef type expression
interface X extends __X {
x: string // from @property
}
```
Either way of making it not work for object or allowing it to work for other types seems reasonable.
**Actual behavior:** `Object` is treated as a special type that doesn't behave like other types. See comments in example for errors when using other types.
**Playground Link:** it is JSDoc, can't.
**Related Issues:** n/a | Bug | low | Critical |
444,533,329 | godot | Sub-Viewport dosn't capture proberly when using get_texture().get_data() | **Godot version:**
3.1.1-stable
**OS/device including version:**
Windows 10, GTX 1080, Driver version: 419.67
**Issue description:**
Make a screenshot with get_viewport().get_texture().get_data(), but only get a complete black picture. Using the same and create a ImageTexture from it and assign it to a sprite turns out black or transparent, while using directly get_viewport().get_texture() on a sprite works.
**Steps to reproduce:**
- Create a 3D scene with a camera in it and an mesh.
- Create a canvas layer and a sprite inside of it.
- Create a viewport node and set the size. Add a camera as child.
- may positionate both cameras different, helpful to differ from wich camera the output was captured
- Write an script an the second camera (in the viewport) with does the following:
```
get_node("../../CanvasLayer/Sprite").texture = get_viewport().get_texture()
```
- Run the project: seems good.
- Change the script to:
```
yield(get_tree(), "idle_frame");
yield(get_tree(), "idle_frame");
var tex = ImageTexture.new()
tex.create_from_image(get_viewport().get_texture().get_data())
get_node("../../CanvasLayer/Sprite").texture = tex
```
- Run the project: the sprite displays nothing (and in some situations black)
- 3rd check: change the script again, so its saves the output to a file:
```
yield(get_tree(), "idle_frame");
yield(get_tree(), "idle_frame");
get_viewport().get_texture().get_data().save_png("./output.png");
```
- Run project again: output.png contains a complete black picture.
**Minimal reproduction project:**
Notes: all tests are in the script "Camera.gd", as seperated functions. just uncomment the call in _ready what you want to test.
[BlackViewport.zip](https://github.com/godotengine/godot/files/3183468/BlackViewport.zip)
| topic:core,documentation | low | Minor |
444,537,566 | vscode | Add more flexible Decorations or editor overlays for extensions | Flutter in IntelliJ/Android Studio has this new feature that draws guide lines between parent/child widgets in the code editor:
The feedback has been great and many have asked for the same in VS Code (for ex. see https://twitter.com/brwngrldev/status/1128300139980959745).
I've tried to implement this in VS Code using decorations, but it's been a struggle because the decorations API wasn't really designed for this. Some of the quirks I found while trying to implement this:
- Blank lines will only render the first decoration
- Decorations that span multiple lines are appear individually to each line (eg. a bottom border would appear on every line in the range, not just the bottom)
- Unable to render a vertical line starting at the top of an editors line other than border (which has little control over positioning)
- Images that fill the whole line height will cause some lines (usually the first in a block with the decoration) to grow by a few pixels (so you have some lines in the editor taller than others)
- No way to render a horizontal line that will extend automatically with its range (borders seem like they'd work, but positioning them within lines is difficult).
I also noticed there are other extensions that try to do similar things in the editor that have similar quirks (things like Indent Rainbow).
I'm not very confident in shipping what I've built so far because it's very quirky, but it would be a shame for VS Code users to miss out on this feature. It would be great if we had a more flexible way of drawing in the editor (without affecting the layout/positioning of code). I don't know exactly what the API/feature to support this better might look like, but for example if we could draw to a canvas and had an API to get the coordinates/size of a given character/`Position` I think we could make this much more reliable.
I did look up how VS Code draws its indent guides hoping for some inspiration, but it seems like it uses features/APIs unavailable to extensions (like its own custom CSS).
Here's what I have now. There are gaps between lines because I'm using ascii characters to draw (if you reduce your line height, you can eliminate these, at the expense of your lines being crushed) and because of how we have to draw it, there's also a noticeable delay when code is moved around (https://github.com/microsoft/vscode/issues/54147 would also help with that).
| feature-request,editor-rendering | high | Major |
444,633,839 | go | x/playground: error line highlighting broken with multi-file programs | With the new support for multiple files (#32040), the error highlighting is broken (sometimes):
https://play.golang.org/p/S5z9R-mbAzj
/cc @ysmolsky @dmitshur | help wanted,NeedsFix | low | Critical |
444,652,529 | go | testing: Benchmark prints nothing on failure | Benchmark functions can call Log, Error and Fatal, but if the benchmark is run with the Benchmark function, all messages are discarded.
https://play.golang.org/p/fd5Ed-il70V
Perhaps the messages should be printed to standard error? | NeedsInvestigation | low | Critical |
444,653,276 | terminal | Feature request: Enable customization for tabs on bottom/right/left | There should be an option for 'tabs on bottom' for the user to set in profiles.json.
| Issue-Feature,Area-UserInterface,Area-Extensibility,Product-Terminal | medium | Critical |
444,653,653 | pytorch | torch.norm produces incorrect results | ## ๐ Bug
torch.norm gives incorrect results on CPU in the latest nightly build as well as in 1.1.0 stable.
## To Reproduce
```
>>> import torch
>>> a=torch.rand(2000,2000,64)
>>> b=torch.norm(a)
>>> c=torch.norm(a.cuda())
>>> b,c
(tensor(5792.6187), tensor(9237.8311, device='cuda:0'))
```
<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->
## Expected behavior
Both b and c should have the same values.
## Environment
PyTorch version: 1.1.0.dev20190514
Is debug build: No
CUDA used to build PyTorch: 9.0.176
OS: Red Hat Enterprise Linux Server release 7.4 (Maipo)
GCC version: (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
CMake version: version 2.8.12.2
Python version: 3.6
Is CUDA available: Yes
CUDA runtime version: Could not collect
GPU models and configuration:
GPU 0: Tesla K40m
GPU 1: Tesla K40m
Nvidia driver version: 387.26
cuDNN version: Could not collect
Versions of relevant libraries:
[pip3] msgpack-numpy==0.4.1
[pip3] numpy==1.14.3
[pip3] torch==0.4.0
[pip3] torchtext==0.2.3
[pip3] torchvision==0.2.1
[conda] blas 1.0 mkl
[conda] mkl 2018.0.2 1
[conda] mkl_fft 1.0.1 py36h3010b51_0
[conda] mkl_random 1.0.1 py36h629b387_0
[conda] pytorch-nightly 1.1.0.dev20190514 py3.6_cuda9.0.176_cudnn7.5.1_0 pytorch
[conda] torchtext 0.2.3 <pip>
## Additional context
<!-- Add any other context about the problem here. -->
| triaged,module: numerical-reproducibility,module: norms and normalization | low | Critical |
444,663,808 | go | cmd/objdump: incorrect filename for function | ```
$ go tool objdump -s cmplx.Inf ../pkg/darwin_amd64/math/cmplx.a
TEXT math/cmplx.Inf(SB) gofile..$GOROOT/src/math/bits.go
bits.go:27 0x2e24 90 NOPL
isinf.go:19 0x2e25 f20f100500000000 MOVSD_XMM 0(IP), X0 [4:8]R_PCREL:$f64.7ff0000000000000
isinf.go:20 0x2e2d f20f11442408 MOVSD_XMM X0, 0x8(SP)
isinf.go:20 0x2e33 f20f11442410 MOVSD_XMM X0, 0x10(SP)
isinf.go:20 0x2e39 c3 RET
```
Note that `cmplx.Inf` is listed as being in `$GOROOT/src/math/bits.go`. It looks like cmd/objdump may assume that the first instruction in the function is located within the function. With inlmarks in a prologue-less function, at least, this assumption is false.
Also, why is that inlining mark there in the first place?
cc @randall77 because this is an unintended consequence of inlmarks
cc @dr2chase for all things position
| help wanted,NeedsFix,compiler/runtime | low | Major |
444,669,888 | go | cmd/compile: inlining mark elimination is fragile | [broken out from #32068]
If you remove the following rule from generic.rules
`(Geq(64|32|16|8) (Const(64|32|16|8) [c]) (Const(64|32|16|8) [d])) -> (ConstBool [b2i(c >= d)])`
and recompile math/cmplx.Inf, you get similar generated code. The constant folding that did not occur during generic opt occurs in lowered opt. (The generated code isn't identical, but I'm working on that independently.)
However, if the constant folding occurs during lowered opt, there is no inlining nop at the beginning of the function.
Either we need one, or we don't; it shouldn't be sensitive to whether a particular generic constant folding optimization occurs.
cc @randall77 for inlining marks
| NeedsInvestigation,compiler/runtime | low | Critical |
444,680,472 | pytorch | Performance issue when accessing an extremely large (10GB) longtensor | ## ๐ Bug
I'm encountering a very strange performance issue when accessing an extremely large tensor. I first encountered it when loading a whole dataset into gpu memory on a Tesla v100, which may be required for reproducibility because smaller tensors don't demonstrate the effect.
If the tensor is above a certain size, then once you index past a specific value, access to the tensor (or at least the performance of the dnn) begins to take longer and longer. The linked repo includes an example notebook that demonstrates the performance dropoff.
There doesn't seem to be an issue with tensors in cpu memory.
Here are the things I've tested so far to help isolate:
- Different tensor shapes (2x wider tensors results in degredation at ~6M samples)
- Changed the tensor size to be within the limit (no slowdown occurs)
- CPU Memory (No issues)
- Different GPUs, although all on the same DGX-1 (hopefully validating hardware is functioning)
- Artifically starting the dataloader at the point where it slows down. (Slowdown is immediate and performance is much worse (25K samples/s)
- Breaking up the tensor into multiple blocks to see if being contiguous matters (multiple tensors don't have the same effect. Only one larger tensor demonstrates this issue)
- Started with multiple blocks and concated together on the GPU. (issue shows up again)
- Tested just the indexing of the single large random tensor to see if it was impacted (no slowdown)
This is possibly due to a int (or long) variable in the memory addressing of the tensor; If I calculate the point in the tensor where the slowdown occurs (45x4bytesx~12M = 2.16B) that's suspiciously close to the int limit of 2147483647.
What's strange is that the slowdown only occurs if there is significant access beyond that range. I tested a tensor that was 4 bytes larger (and one that was 100K larger) and neither of those displayed significant problems. It's only when it's much larger that it seems to cause the issue.
As mentioned above, for a larger tensor if I start accessing in that region the slowdown is immediate and much more pronounced.
It's worth noting I encountered a similar and more nefarious issue when shuffling by index a tensor loaded from dl_pack of this size where the region of the data beyond the int limit was all 0s.
I understand tensors of this size are unusual (at least for now) but it would be great to figure out the limitations so that others don't run into this and so that we can plan for future GPUs with much more RAM and in GPU memory datasets.
## To Reproduce
Steps to reproduce the behavior:
Run the notebook available in the repo: https://github.com/EvenOldridge/HugeTensor
The notebook uses ignite version 0.1.2 and contains a batch dataloader that I'm prototyping and hope to integrate into pytorch once its kinks are worked out.
## Expected behavior
Performance of the nn should be consistent when indexing the same tensor. As soon as the data is split into 3 tensors the performance is fine as expected. Performance on the CPU for a single large tensor is also fine. No performance dropoff should occur when accessing a single large tensor in GPU memory.
## Environment
- PyTorch Version (e.g., 1.0): 1.01
- OS (e.g., Linux): Linux
- How you installed PyTorch (`conda`, `pip`, source): pip
- Python version: 3.6
- CUDA/cuDNN version: 10.0
- GPU models and configuration: TeslaV100 32 Gig (on a DGX-1)
- Any other relevant information:
## Additional context
| module: cudnn,module: cuda,triaged | low | Critical |
444,681,329 | TypeScript | Automatic `skipDefaultLibCheck` (and potentially `skipLibCheck`) | This issue is adapted from a work item discussed at #25658.
# Automatic `skipDefaultLibCheck`
`lib.d.ts` is a pretty big file, and it's only going to grow. Realistically, most people don't ever declare symbols that conflict with the global scope, so we made the `skipDefaultLibCheck` (and also the `skipLibCheck` flag) for faster compilations.
[We can suggest this flag to users](https://twitter.com/drosenwasser/status/1007721634193477632), but the truth is that it's not discoverable. It's also often misused, so I want to stop recommending it to people. ๐
It'd be interesting to see if we can get the same results of `skipDefaultLibCheck` based on the code users have written. Any program that doesn't contribute a global augmentation, or a declaration in the global scope, doesn't really need to have `lib.d.ts` checked over again.
@mhegazy and I have discussed this, and it sounds like we have the necessary information after the type-checker undergoes symbol-merging. If no symbols ever get merged outside of lib files, we can make the assumption that `lib` files never need to get checked. But this requires knowing that all lib files have already had symbols merged up front before any other files the compiler is given.
## Open Questions
* Is the idea to only type-check symbols which have been merged? Or is it to fall back to the worst-case behavior of checking everything when *any* symbol has been merged across files?
* If it's the only checking merged entities, does `declare class B extend A {}` need to be re-checked if `A` has ever been subsequently merged? How would we keep track of that information?
* If it's falling back to the worst-case behavior, does this feature actually help anyone outside of the "Hello world" case?
## Cons
* It feels like there are certain interactions we may be overlooking - we will have to be careful about our assumptions in the compiler with this behavior in place.
* Users who edit `lib.d.ts` wouldn't see erroneous changes in a compiler (so we'd likely need a `forceDefaultLibCheck`).
## Pros
* Running with `skipDefaultLibCheck` removes anywhere between 400-700ms on my machine from a "Hello world" file, so we could expect the same here under this behavior.
* Only our team ever needs to run `forceDefaultLibCheck`, reducing the cost for all other TypeScript users.
| Suggestion,In Discussion,Domain: lib.d.ts,Domain: Performance | low | Major |
444,712,978 | rust | Naming associated type leads to incorrect lifetime errors | [playground link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=2d6a330fff6b07b13560649dadaf1cae)
This impl compiles:
```rust
unsafe impl<D> TrustedContainer for D
where
D::Target: TrustedContainer,
D: ops::Deref,
{
type Item = <D::Target as TrustedContainer>::Item;
unsafe fn get_unchecked<'a>(&self, i: usize) -> &Self::Item {
<D::Target>::get_unchecked(self, i)
}
}
```
while this this theoretically identical one doesn't:
```rust
unsafe impl<T: ?Sized, D> TrustedContainer for D
where
T: TrustedContainer,
D: ops::Deref<Target = T>,
{
type Item = T::Item;
unsafe fn get_unchecked(&self, i: usize) -> &Self::Item {
T::get_unchecked(self, i)
}
}
```
Type context:
```rust
pub unsafe trait TrustedContainer {
type Item: ?Sized + TrustedItem<Self>;
unsafe fn get_unchecked(&self, i: usize) -> &Self::Item;
}
pub unsafe trait TrustedItem<A: TrustedContainer<Item=Self> + ?Sized> {
type Unit;
}
unsafe impl<T: ?Sized, Array: ?Sized, D> TrustedItem<D> for T
where
T: TrustedItem<Array>,
Array: TrustedContainer<Item = T>,
D: ops::Deref<Target = Array> + TrustedContainer<Item = T>,
{
type Unit = T::Unit;
}
``` | A-lifetimes,A-associated-items,T-compiler,C-bug | low | Critical |
444,740,684 | go | x/crypto/ssh: "ssh: handshake failed: EOF" with 3des-cbc | ### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.12.5 linux/amd64
</pre>
### Does this issue reproduce with the latest release?
Yes.
### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN="/home/jae/.local/bin"
GOCACHE="/home/jae/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/jae/projects/go/golib:/home/jae/projects/go/gotools:/home/jae/projects/go/mylib"
GOPROXY=""
GORACE=""
GOROOT="/home/jae/projects/go/goroot"
GOTMPDIR=""
GOTOOLDIR="/home/jae/projects/go/goroot/pkg/tool/linux_amd64"
GCCGO="/usr/bin/gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/jae/notes/developement/programming/go/examples/misc-tests/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build225295978=/tmp/go-build -gno-record-gcc-switches"
</pre></details>
### What did you do?
I help maintain the github.com/pkg/sftp library and am helping a user with an ssh issue. They have an SFTP server that only supports some older ciphers, like 3des-cbc and they can't connect successfully. I've tried to simplify and reproduce their issue with some success. I've configured my local openssh server to only accept that cipher, with `Ciphers 3des-cbc` in the sshd_config and was able to connect to it with the openssh client with `ssh -c 3des-cbc localhost`. If I don't specify `-c 3des-cbc` on the command line it won't connect with a negotiation error. So everything seems good on that side.
I then try to connect with a simple program using x/crypto/ssh set to use that same cipher and get the error `ssh: handshake failed: EOF` and the openssh server spits out the following in the log.
```
May 15 20:41:26 XXX sshd[12686]: Bad packet length 1474871687. [preauth]
May 15 20:41:26 XXX sshd[12686]: ssh_dispatch_run_fatal: Connection from 127.0.0.1 port 53234: Connection corrupted [preauth]
```
My simple program to reproduce is..
```
package main
import (
"fmt"
"net"
"os"
"golang.org/x/crypto/ssh"
"golang.org/x/crypto/ssh/agent"
)
func main() {
sshagent, err := net.Dial("unix", os.Getenv("SSH_AUTH_SOCK"))
if err != nil {
panic(err)
}
signer := ssh.PublicKeysCallback(agent.NewClient(sshagent).Signers)
sshConfig := &ssh.ClientConfig{
User: os.ExpandEnv("$USER"),
Auth: []ssh.AuthMethod{signer},
HostKeyCallback: ssh.InsecureIgnoreHostKey(),
}
sshConfig.SetDefaults()
sshConfig.Ciphers = []string{"3des-cbc"}
_, err = ssh.Dial("tcp", "localhost:22", sshConfig)
fmt.Printf("%v\n", err)
}
```
### What did you expect to see?
No error and have it connect.
### What did you see instead?
ssh: handshake failed: EOF
Thanks.
| NeedsInvestigation | low | Critical |
444,747,054 | youtube-dl | [Site support request] Vudu.com - Free movies and TV shows | <!--
######################################################################
WARNING!
IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################
-->
## Checklist
<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.05.11. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->
- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.05.11**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones
## Example URLs
<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->
- Single video: https://www.vudu.com/content/movies/details/Storks/784456
- Single video: https://www.vudu.com/content/movies/play/311378/ADVERT_CONTENT
- Playlist: https://www.vudu.com/content/movies/details/I-Dream-of-Jeannie-Season-3/311376
## Description
<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->
Vudu is a USA-only (geo-restricted) streaming platform that provides ad-supported movies and tv shows along with paid content, the site is geo restricted (even the login is geo restricted) but creating an account is free. Closed Captions/subtitles are provided as well.
From what I can gather the content is streamed using MPEG-DASH but I'm not sure if it is DRM protected. It probably is but I thought I'd ask anyway. | site-support-request | low | Critical |
444,750,176 | create-react-app | React npm start con't run and open the localhost:3000 | > [email protected] start C:\Users\mohammad ahmad\Desktop\React Projects\app
> react-scripts start
Starting the development server...
events.js:174
throw er; // Unhandled 'error' event
^
Error: spawn cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\mohammad ahmad\AppData\Roaming\npm-cache\_logs\2019-05-15T20_48_25_193Z-debug.log | issue: needs investigation | medium | Critical |
444,758,634 | svelte | afterUpdate docs should mention recursion protection | In src/internal/scheduler.js, `flush()` protects against recursion caused by `afterUpdate` with its `seen_callbacks` variable.
This may lead to surprising behaviour, if the user depends on multiple but finite invocations of their `afterUpdate` callback, so it should be documented. | stale-bot,temp-stale,documentation | low | Minor |
444,759,280 | TypeScript | const TemplateStringsArray for TaggedTemplateExpression | <!-- ๐จ STOP ๐จ ๐ฆ๐ง๐ข๐ฃ ๐จ ๐บ๐ป๐ถ๐ท ๐จ
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section.
-->
## Search Terms
TemplateStringsArray, TaggedTemplateExpression
## Suggestion
<!-- A summary of what you'd like to see added or changed -->
There shouldn't be a type `TemplateStringsArray`, it should be a `const string tuple type`, so we can write code:
```ts
interface SQL<TSA, VS> {
texts: TSA;
values: VS;
}
function sql<TSA extends readonly string[], VS extends any[]>(texts:TSA, ...values: VS): SQL<TSA, VS> {
return { texts, values };
}
// then
let s: SQL<['select * from person where a=', ' and b=', ''], [number, Date]> = sql`select * from person where a=${1} and b=${new Date()}`;
```
## Use Cases
<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->
Just like in the above code, we can test the sql at compile time or use a TypeScript Language Service Plugin *(in fact, I'm writing it[ts-sql-plugin](https://github.com/xialvjun/ts-sql-plugin) and then come across this problem)*.
## Examples
<!-- Show how this would be used and what the behavior would be -->
## Checklist
My suggestion meets these guidelines:
* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
There is another issue is alike. https://github.com/microsoft/TypeScript/issues/16552#issuecomment-492919476
Besides, `TemplateStringsArray` is `ReadonlyArray<string>`, it should be const anyway. | Suggestion,Awaiting More Feedback | high | Critical |
444,785,178 | pytorch | NVRTC_ERROR unknown when using self-built libtorch | Hi, I am doing inference with my own GPU model. When i use the released nightly version of libtorch from official website, there is no issue. Then I build libtorch from the same version of pytorch source and use the self-built version of libtorch to do inference, it shows the following error:
pytorch/torch/csrc/jit/fuser/cuda/fused_kernel.cpp:196: NVRTC_ERROR unknown:
operation failed in interpreter:
:
operation failed in interpreter:
Aborted (core dumped)
For some reasons I have to build libtorch from source, but seems the flags i use to build libtorch are not the same as the official ones used to build nightly version. Anyone know how the nightly version of libtorch is built and what are the flags used to build? Thanks a lot!.
The following is my local environment:
Linux16.04;
CUDA 9;
libtorch nightly verison: May 13, 2019
| module: build,triaged | low | Critical |
444,808,214 | vue-element-admin | ๅผๅฏFixed Header๏ผๆๅผel-dialogๅ็Navbarๆ ทๅผ้ฎ้ข | ## Bug report๏ผ้ฎ้ขๆ่ฟฐ๏ผ
#### Steps to reproduce๏ผ้ฎ้ขๅค็ฐๆญฅ้ชค๏ผ
1. ๅผๅฏFixed Header
2. ๆๅผel-dialog
#### Screenshot or Gif๏ผๆชๅพๆๅจๆๅพ๏ผ
#### Link to minimal reproduction๏ผๆๅฐๅฏๅจ็บฟ่ฟๅdemo๏ผ
https://panjiachen.github.io/vue-element-admin/#/table/complex-table | enhancement :star: | low | Critical |
444,808,904 | go | crypto/tls: make it clear that implementation is compliant with RFC 5246 | In #31933, @swanandt pointed out that the following note at the top of the [crypto/tls package](https://golang.org/pkg/crypto/tls/):
> Package tls **partially implements** TLS 1.2, as specified in RFC 5246
may be misinterpreted as a warning about non-compliance with the RFC 5246. This is not the case, as @FiloSottile explained:
> As far as I know, we implement everything that is REQUIRED by RFC 5246, so we are in full compliance with it.
It may be useful to slightly change the wording of the doc to make it completely clear the only *optional* features (like DHE, topic of the discussion at #31933) are currently not implemented, and so the package is fully compliant with RFC 5246.
| Documentation,NeedsFix | low | Minor |
444,827,475 | PowerToys | 'Show desktop' button, option to minimize per monitor | When clicking the 'Show desktop' button, all windows are minimized across all monitors. It would be nice to have the option to only show the desktop on that specific monitor and keep windows on other monitors untouched. | Idea-New PowerToy | low | Major |
444,855,101 | flutter | BackdropFilter performance issue | Hi, I'm using a BackdropFilter widget as a cell background in a list.
But this widget totally cripples the application, the performances are very bad and the UI lags very much.
This is my custom widget:
```dart
class FrostedBox extends StatelessWidget {
final Widget child;
final double sigmaY;
final double sigmaX;
final Color _color = AppColors.whiteText.withOpacity(0.1);
FrostedBox({@required this.child, this.sigmaX = 8, this.sigmaY = 8});
@override
Widget build(BuildContext context) {
return Stack(
children: <Widget>[
ClipRect(
child: BackdropFilter(
filter: ImageFilter.blur(sigmaX: this.sigmaX, sigmaY: this.sigmaY),
child: new Container(
decoration: new BoxDecoration(
color: _color
)
),
)
),
this.child
],
);
}
}
```
It seems that the BackdropFilter constantly repaints itself. I've tried to use a stack to reduce the amount of things it rebuilds, but still, the lag is very high.
I think that the problem is that every time I scroll the list, the blur effect on the single cell it's rebuilded costing a lot of performances
Any tip? Am'I using the wrong widget? | framework,engine,c: performance,customer: crowd,a: images,has reproducible steps,P2,team-engine,triaged-engine,found in release: 3.19,found in release: 3.20 | low | Major |
444,907,408 | TypeScript | [3.5.0-dev.20190516] Incorrect type error for mixin | When using the [mixin pattern](https://www.bryntum.com/blog/the-mixin-pattern-in-typescript-all-you-need-to-know/), there are 2 main notations to define the type of the mixin entity.
The mixin pattern:
```ts
export type AnyFunction<A = any> = (...input : any[]) => A
export type AnyConstructor<A = object> = new (...input : any[]) => A
export type Mixin<T extends AnyFunction> = InstanceType<ReturnType<T>>
export const Box = <T extends AnyConstructor<object>>(base : T) =>
class Box extends base {
value : any
}
```
1st notation:
```ts
export type Box = Mixin<typeof Box> {}
```
2nd notation:
```ts
export interface Box extends Mixin<typeof Box> {}
```
The 1st notation can not be used for recursive definitions (#29872). Because of that we primarily use 2nd notation. It works fine in most cases, however I found a case, when it produces invalid type error. The full snippet to reproduce the problem below.
Note:
- The typechecker correctly figures out that there's no `zxc` property on `this`, inside the `observe` method of `Quark` mixin.
- In that method, it does not complain about the `this.value` usage
- It does complain, when `value` is used on function argument
- If you'll switch the `Quark` mixin to the 1st notation, the error will disappear
Expected behavior:
- No type errors for the definition of `test` function below
```ts
export type AnyFunction<A = any> = (...input : any[]) => A
export type AnyConstructor<A = object> = new (...input : any[]) => A
export type Mixin<T extends AnyFunction> = InstanceType<ReturnType<T>>
export const Box = <T extends AnyConstructor<object>>(base : T) =>
class Box extends base {
value : any
}
export interface Box extends Mixin<typeof Box> {}
export const Observable = <T extends AnyConstructor<object>>(base : T) =>
class Observable extends base {
observe () : Quark {
return
}
}
export interface Observable extends Mixin<typeof Observable> {}
export const Quark = <T extends AnyConstructor<Box & Observable>>(base : T) =>
class Quark extends base {
observe () : Quark {
// No error here!
this.value
// error: Error:(28, 14) TS2339: Property 'zxc' does not exist on type 'Quark'.
this.zxc
return
}
}
export interface Quark extends Mixin<typeof Quark> {}
const test = (a : Quark) => a.value // <-- Error:(35, 28) TS2339: Property 'value' does not exist on type 'Quark'.
```
| Bug,Fix Available | low | Critical |
444,945,431 | rust | Should Thumb bugs get increased visibility, e.g. Tier 1 status? | Spawned off of discussion here: https://github.com/rust-lang/rust/pull/58605#issuecomment-484929150
Do we need to explicitly revise stuff in our tagging/tests/release processes to try to decrease risk of Thumb bugs?
Namely these two points:
> we may want to expand the number of items tested in the thumb-* tests contained in https://github.com/rust-lang/rust/tree/master/src/test/run-make
and:
> There was a discussion at the 2018 all hands about making the thumb targets tier 1, however this was not done as @alexchrichton mentioned that the concept of tiers was going away, or was being retooled.
>
> If not, I'd like to reintroduce the discussion of making the thumb targets an official tier one target, as it already has some of the ground work laid to claim this | O-Arm,I-needs-decision,T-lang,T-compiler,T-infra,WG-embedded | low | Critical |
444,988,426 | go | x/tools/cmd/goimports: does not find import with package in vendor/, GOFLAGS="-mod=vendor" and empty $GOPATH/pkg directory | ### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.12.4
</pre>
goimports from from https://github.com/golang/tools, commit `d1a3278ee74994e9aa609e9e711c616bba677d5d`
### Does this issue reproduce with the latest release?
Yes, reproducible with go 1.12.5
### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/fho/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/fho/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/tmp/testproject/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build188015067=/tmp/go-build -gno-record-gcc-switches"
```
### What did you do?
1. Create a new golang project using go.mod.
The project has a a `main.go` file that imports the external dependency `github.com/lib/pq`.
The external modules are downloaded into `vendor/` via `go mod vendor`.
```
mkdir -p /tmp/testproject
cd /tmp/testproject
go mod init "testproject"
echo 'package main
import (
"fmt"
"github.com/lib/pq"
)
func main() {
var test pq.StringArray
fmt.Println(test)
}' > main.go
go mod vendor
```
2. Remove the `"github.com/lib/pq"` import from main.go:
```
sed -i '/"github.com\/lib\/pq"/D' main.go
```
3. Remove `$GOPATH/pkg`, run goimports with `GOFLAGS=-mod=vendor`:
```
sudo rm -rf $(go env GOPATH)/pkg
GOFLAGS="-mod=vendor" goimports -d main.go
```
### What did you expect to see?
goimports detects the missing `github.com/lib/pq` import and shows it in the diff.
### What did you see instead?
goimports **does not** find the missing `github.com/lib/pg` import and prints no diff. | NeedsInvestigation,modules,Tools | low | Critical |
444,998,756 | create-react-app | Publish react-dev-utils/openBrowser as separate package? | ### Is this a bug report?
No.
---
First of all, thanks for this awesome project! Your work on low-configuration tooling for the React community is a huge help for those of all skill levels.
I would like to suggest the possibility of publishing `react-dev-utils/openBrowser` (and maybe other things) separately as low-dependency helper packages to avoid the issue caused by the locked dependencies of `react-dev-utils`.
Let me outline the use case with an example:
`mdx-deck` uses `react-dev-utils/openBrowser` to reliably open the deck in the browser and focus the tab:
https://github.com/jxnblk/mdx-deck/search?q=react-dev-utils&type=Code
This is a great use of the library, but it has the downside of creating a sub-dependency on the locked dependencies of `react-dev-utils`, which there are many of:
https://github.com/facebook/create-react-app/blob/57ef103440c24e41b0d7dc82b7ad7fc1dc817eca/packages/react-dev-utils/package.json#L53-L77
This, combined with the use of the common `^` minor version specifier for `react-dev-utils` and the relatively fast cadence of releases in `react-dev-utils` means that any incompatibilities between any versions of any of the locked dependencies can cause situations if used with other, older packages.
For example, using a Yarn workspace with package using a pre-2.0 version of mdx-deck along with another package using version `3.0.1` of `react-scripts`.
In my particular case, it resulted in a cryptic ["BrowserslistError: Unknown browser kaios"](https://stackoverflow.com/a/55872461/1268612), caused by the locked dependency on an older version of `browserslist` in `react-dev-utils`.
I cannot downgrade `browserslist` via Yarn Resolutions reliably, because `[email protected]` depends on `react-dev-utils@^9.0.1`. And I cannot upgrade `react-dev-utils` because of the minor `^` selector in the old and current versions of `mdx-deck` (`react-dev-utils@^7.0.3` and `react-dev-utils@^8.0.0` respectively).
So I'm left with using a resolution that may break things more subtly if there's a different bug between `[email protected]` (sub-dep from `[email protected]` + `[email protected]`) and `[email protected]` (sub-dep from `[email protected]` + `[email protected]`).
---
### Solution
If the module was published as a separate package, it could retain its locked dependency list but with far lower possibility for incompatibilities.
I wouldn't suggest this for every module in `react-dev-utils`, but it seems as if the `openBrowser` module is useful enough to warrant separate publishing.
In any case, thanks for listening!
### Alternative Solution
Strongly recommend that package authors do not depend on the modules from `react-dev-utils` or provide some different alternative for them.
Also, if you know of a third option that I haven't thought of, I'm all ears! | issue: proposal | low | Critical |
445,029,084 | opencv | VideoWriter class does not support stream copy | ##### System information (version)
- OpenCV => 3.1 with bindings in Python 3.6
- Operating System / Platform =>Ubuntu 18.04 LTS
- Compiler => Visual Studio 2015
-->
##### Detailed description
The VideoWriter object does not have working stream copy functionality. Using a command line call to ffmpeg, for instance, one can read a video stream as input (akin to the VideoCapture object) and directly copy this stream into an output file without any decoding or re-encoding, which saves a lot of computation time. In OpenCV, if no codec is specified for the VideoWriter object, no file is output. Documentation suggests that entering a value of 0 into the fourcc codec code and a framerate of 0 when constructing the VideoWriter object should accomplish this but does not.
https://docs.opencv.org/3.4/dd/d9e/classcv_1_1VideoWriter.html
"If FFMPEG is enabled, using codec=0; fps=0; you can create an uncompressed (raw) video file."
The following code produces no output file.
```.py
fourcc = 0
fps = 0
size = 1080,720
out = VideoWriter("outfile.avi",outvid, fourcc, float(fps), size)
```
-->
| priority: low,category: videoio | low | Major |
445,061,759 | pytorch | @ignore annotation for user defined type | ## ๐ Feature
In user defined type, it would be nice to have a @ignore annotation similar to https://github.com/pytorch/pytorch/pull/16055
This allows the user to write python only methods that are only used in training / debugging (like `def #visualize`)
cc @suo | oncall: jit,triaged,jit-backlog | low | Critical |
445,085,085 | youtube-dl | site support: mediagoblin, libreplanet | ## Checklist
- [X ] I'm reporting a new site support request
- [X ] I've verified that I'm running youtube-dl version **2019.05.11**
- [X ] I've checked that all provided URLs are alive and playable in a browser
- [X ] I've checked that none of provided URLs violate any copyrights
- [ X] I've searched the bugtracker for similar site support requests including closed ones
## Example URLs
- Playlist: https://media.libreplanet.org/u/libreplanet/tag/libreplanet-2019-video/
Single videos from this site work fine.
## Description
```
joshua@cocoa:/tmp$ youtube-dl -v https://media.libreplanet.org/u/libreplanet/tag/libreplanet-2019-video/
[debug] System config: []
[debug] User config: ['-x', '--no-mtime', '--audio-format', 'opus', '--audio-quality', '96k', '--ignore-errors', '--download-archive', '/home/joshua/.config/youtube-dl/downloaded.txt']
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://media.libreplanet.org/u/libreplanet/tag/libreplanet-2019-video/']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2019.05.11
[debug] Python version 3.7.3 (CPython) - Linux-5.0.0-13-generic-x86_64-with-Ubuntu-19.04-disco
[debug] exe versions: ffmpeg 4.1.3, ffprobe 4.1.3, phantomjs 2.1.1, rtmpdump 2.4
[debug] Proxy map: {}
[generic] libreplanet-2019-video: Requesting header
WARNING: Falling back on generic information extractor.
[generic] libreplanet-2019-video: Downloading webpage
[generic] libreplanet-2019-video: Extracting information
ERROR: Unsupported URL: https://media.libreplanet.org/u/libreplanet/tag/libreplanet-2019-video/
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/youtube_dl/YoutubeDL.py", line 796, in extract_info
ie_result = ie.extract(url)
File "/usr/local/lib/python3.7/dist-packages/youtube_dl/extractor/common.py", line 529, in extract
ie_result = self._real_extract(url)
File "/usr/local/lib/python3.7/dist-packages/youtube_dl/extractor/generic.py", line 3329, in _real_extract
raise UnsupportedError(url)
youtube_dl.utils.UnsupportedError: Unsupported URL: https://media.libreplanet.org/u/libreplanet/tag/libreplanet-2019-video/
``` | site-support-request | low | Critical |
445,090,438 | youtube-dl | Site support request: kvf.fo | <!--
######################################################################
WARNING!
IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################
-->
## Checklist
<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.05.11. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->
- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.05.11**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones
## Example URLs
<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->
- Single video: https://kvf.fo/live/1
- Single video: http://kvf.fo/vit/sjonvarp/2019/03/20/snipp-snapp-0
## Description
<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->
More info about website itself here -> https://en.wikipedia.org/wiki/Kringvarp_Fรธroya
Content is streaming by MPEG-DASH. Generic extractor included in youtube-dl don't work and videos are downloadable when I get direct link to m3u8 file. | site-support-request | low | Critical |
445,097,400 | kubernetes | Simultaneous calls to add a finalizer and delete can race | Store#Delete begins by looking up the existing object:
https://github.com/kubernetes/kubernetes/blob/8ae998ceb69ae83afe730795aea3bd44913ad868/staging/src/k8s.io/apiserver/pkg/registry/generic/registry/store.go#L865-L875
If that object has no pending finalizers, and that type does not do graceful deletion, and the incoming deletion options do not specify preconditions (uid or resourceVersion) or GC-related finalizers (like orphan or foreground deletion), then the object is deleted unconditionally:
https://github.com/kubernetes/kubernetes/blob/8ae998ceb69ae83afe730795aea3bd44913ad868/staging/src/k8s.io/apiserver/pkg/registry/generic/registry/store.go#L929-L932
In between the initial get and the unconditional delete, an update adding finalizers could have been made and succeeded.
/kind bug
/sig api-machinery
/priority important-soon
/cc @caesarxuchao | kind/bug,priority/important-soon,sig/api-machinery,lifecycle/frozen | medium | Critical |
445,112,219 | vscode | New revealProblems property in task presentation options is missing from the API | A new `revealProblems` property is available in the `presentation` of tasks in `tasks.json` in current Insider's builds / the upcoming 1.34. However, this property [is absent from the `TaskPresentationOptions` API in `vscode.d.ts`](https://github.com/microsoft/vscode/blob/07ec42fb0070bd629c1a7fa8f17a8183d7ac4958/src/vs/vscode.d.ts#L4851-L4885), even though historically, new options were always added there. It also doesn't seem to be respected when you ignore the type declaration and set the property via the tasks API anyway.
Is this intentional, or simply an oversight? | feature-request,api,tasks | low | Minor |
445,181,578 | flutter | Widgets show hover effect when clicked on a desktop embedder that has no hover support | When running on a desktop embedder that has no hover support, a widget will incorrectly show hover effect when a mouse clicks inside it, which is dismissed when the mouse clicks out of it.
In the example below, the hover effects are the light-grey color and the tooltip.
If hover is enabled onto the same embedder, the hover effect behaves as expected.
Environment:
- gLinux
- Framework: 900875fd3ff2ec63cce2556a11ab5f86b02d47d6
- Embedder: https://github.com/google/flutter-desktop-embedding/pull/355
Related discussion: https://github.com/flutter/flutter/issues/32835 | engine,a: desktop,P2,team-design,triaged-design | low | Major |
445,185,381 | terminal | Encapsulate the background image settings into a JSON object | # Summary of the new feature/enhancement
As we're adding more settings to the JSON file, do we want to keep what's in each object flat or should we start introducing nested objects? I think having them be nested looks nicer and is easier to read (especially as the settings file gets really big). On the other hand, this might mean that we're forcing settings to look a certain way.
Consider this:
- Today:
```
{
guid: ...,
useAcrylic: ...,
colorScheme: ...,
backgroundImage: ...,
backgroundImageOpacity: ...,
backgroundImageStretchMode: ...,
backgroundImageSetting4: ...,
backgroundImageSetting5: ...
}
```
- Proposal:
```
{
guid: ...,
useAcrylic: ...,
colorScheme: ...,
backgroundImage:
{
url: ...,
opacity: ...,
stretchMode: ...,
setting4: ...,
setting5: ...
}
}
```
I think the proposal looks a lot nicer. I'm picking on backgroundImage from #853 but it definitely can apply to some other things like `fontProperties` (size, family, etc...) and `devEnvironment` (environmentVariables, startingDirectory, etc...).
Also, I think it's easier to see the benefit when there's a nasty looking settings file as follows:
```
{
profileName: ...,
backgroundImage: ...,
guid: ...,
backgroundImageOpacity: ...,
useAcrylic: ...,
backgroundImageStretchMode: ...,
colorScheme: ...
}
```
| Area-Settings,Product-Terminal,Issue-Task | low | Major |
445,187,645 | pytorch | groupby function | ## ๐ Feature
<!-- A clear and concise description of the feature proposal -->
## Motivation
Say for example you have a batch of data but want to take a different action (e.g. run a different model) based on the label index, or based on the length of the input, etc. You want to subdivide the batch according to that value, and in some cases you need to reconstruct the outputs back into the shape of the original tensor. What is needed is a function that groups the rows of the tensor based on the value of the groupby field.
I've ended up needing to implement this multiple times across projects.
## Pitch
```
groups, values, inverse_map = T.groupby(F[, dim=0])
```
Basically T is an `Nx...` tensor and `F` is a size `N` tensor (assuming dim=0). This function returns a list `groups` of length equal to the number of unique values in F. Each group contains all the rows of `T` for that unique element. `values` is just a tensor containing the unique values corresponding to each group, and `inverse_map` is a list of tensors telling you where all the rows came from.
## Alternatives
This can be implemented in about 10 lines in pytorch with something like:
```
sorted_vals, order = F.sort(0)
delta = F[1:] - F[:-1]
cutpoints = delta.nonzero()[0].tolist()
res, inverse_map = [], [], torch.zeros(len(cutpoints))
for start, end, i in zip([0] + cutpoints, cutpoints + [len(F)], range(len(cutpoints) + 1)):
res.append(T[order[start:end]])
inverse_map.append(order[start:end])
values[i] = F[start]
return res, values, inverse_map
```
This could be done faster and in a more standard way as part of Pytorch.
## Additional context
cc @colesbury @lerks | feature,triaged | low | Major |
445,188,177 | rust | Tracking issue for `HashSet` entry APIs | Feature gate: `#![feature(hash_set_entry)]`
This is a tracking issue for `Entry` and entry-like methods on `HashSet`.
### Public API
```rust
impl<T, S> HashSet<T, S>
where
T: Eq + Hash,
S: BuildHasher,
{
pub fn get_or_insert(&mut self, value: T) -> &T {...}
pub fn get_or_insert_with<Q: ?Sized, F>(&mut self, value: &Q, f: F) -> &T
where
T: Borrow<Q>,
Q: Hash + Eq,
F: FnOnce(&Q) -> T,
{...}
pub fn entry(&mut self, value: T) -> Entry<'_, T, S> {...}
}
pub enum Entry<'a, T, S> {
Occupied(OccupiedEntry<'a, T, S>),
Vacant(VacantEntry<'a, T, S>),
}
pub struct OccupiedEntry<'a, T, S> {...}
pub struct VacantEntry<'a, T, S> {...}
impl<T: fmt::Debug, S> fmt::Debug for Entry<'_, T, S> {...}
impl<T: fmt::Debug, S> fmt::Debug for OccupiedEntry<'_, T, S> {...}
impl<T: fmt::Debug, S> fmt::Debug for VacantEntry<'_, T, S> {...}
impl<'a, T, S> Entry<'a, T, S> {
pub fn insert(self) -> OccupiedEntry<'a, T, S>
where
T: Hash,
S: BuildHasher,
{...}
pub fn or_insert(self)
where
T: Hash,
S: BuildHasher,
{...}
pub fn get(&self) -> &T {...}
}
impl<T, S> OccupiedEntry<'_, T, S> {
pub fn get(&self) -> &T {...}
pub fn remove(self) -> T {...}
}
impl<'a, T, S> VacantEntry<'a, T, S> {
pub fn get(&self) -> &T {...}
pub fn into_value(self) -> T {...}
pub fn insert(self)
where
T: Hash,
S: BuildHasher,
{...}
}
```
The `get_or_insert[_with]` methods provide a simplification of the `Entry` API for `HashSet`, with
names chosen to match the similar methods on `Option`. The full `Entry` API mimics that
of `HashMap`, though without methods for the map value (which is just `()` in a set).
### Steps / History
- [x] Initial methods: #60894
- [x] Fuller `Entry` API: #120077
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR
### Unresolved Questions
- None yet.
See also #133549 for `BTreeSet`.
[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html | A-collections,T-libs-api,B-unstable,C-tracking-issue,Libs-Tracked | high | Critical |
445,215,776 | go | x/tools/godoc: remove replaceLinePrefixCommentsWithBlankLine in favor of better fix | Now that #7702 is resolved, it should be possible to remove the [`replaceLinePrefixCommentsWithBlankLine`](https://github.com/golang/tools/blob/1a8f2608bd819ae0c5aeb07edd6bae2fa2cebd71/godoc/parser.go#L55-L57) workaround with a better fix.
This issue is about tracking the progress on that (since all previous issues related to this were closed).
I've looked into this a bit and it's not clear to me if the fix belongs in `golang.org/x/tools/godoc` itself, or if perhaps it can be implemented in a lower level component: one of `go/doc`, `go/parser`, `go/scanner`, `go/ast`, etc. (The workaround would need to stay until it's possible to fully rely on the lower level fix in stdlib.)
I'm also not sure if it's expected behavior for `//line` comments to show up in `ast.CommentGroup` or not.
@griesemer Do you have suggestions on how to best deal with this issue, now that [`token.PositionFor`](https://godoc.org/go/token#File.PositionFor) API exists?
### History
Issue #5247, reported in 2013, was about `godoc` then not handling the following input properly:
```Go
package p
//line file:2
// G doc.
func G()
```
It was showing "line file:2 G doc." as the documentation of function `G`, rather than just "G doc." as it should've been. (If you were to change the line number in the comment to `//line file:10`, it wouldn't show up anymore.)
At that time, there was no API to obtain the raw source positions from a `token.Pos`, which was the main blocker and a long-standing TODO.
As a result, the godoc issue (#5247) was fixed via a workaround in https://github.com/golang/tools/commit/55ea53125770b1ee7bd5cdbd3794ccf2875831e with the comment:
```Go
// Temporary ad-hoc fix for issue 5247.
// TODO(gri) Remove this in favor of a better fix, eventually (see issue 7702).
replaceLinePrefixCommentsWithBlankLine(src)
```
Issue #7702 was filed about adding an API to access the original source lines. It has since been resolved via https://github.com/golang/go/commit/e66ff2b9080669373704914191abf2ee5f65eb75. | NeedsInvestigation,Tools | low | Minor |
445,294,692 | go | plugin: call dlclose if loading a plugin fails | <!-- Please answer these questions before submitting your issue. Thanks! -->
### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.12.5 linux/amd64
</pre>
### Does this issue reproduce with the latest release?
Yes
### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/wangzhizhao/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/wangzhizhao/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build948496286=/tmp/go-build -gno-record-gcc-switches"
</pre></details>
### What did you do?
First I load an .so built with go1.12๏ผwhile error occur๏ผI load another .so built with go1.12.5๏ผstill got error๏ผplugin was built with a different version of package errorsใ
If I only load the .so which built with go1.12.5, It works correctly.
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
### What did you expect to see?
If load an .so built with different verison of go๏ผwhile error occur๏ผI load another .so built with the correct version of go๏ผno error should occur๏ผIt should work correctlyใ
### What did you see instead?
| NeedsInvestigation,compiler/runtime | low | Critical |
445,352,672 | rust | Android fails to link in libc-test | I was trying to fix and upgrade the Android build jobs in libc, and I've managed to get the x86_64 and i686 ones running, but the arm and aarch64 ones fail to link and I have no idea why (https://github.com/rust-lang/libc/pull/1344). These are the two errors that I get:
```
= note: /android/ndk-arm/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: cannot open crtbegin_dynamic.o: No such file or directory
/android/ndk-arm/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: cannot open crtend_android.o: No such file or directory
/android/ndk-arm/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: cannot find -llog
external/jemalloc/src/jemalloc.c:1422: error: undefined reference to 'pthread_atfork'
external/jemalloc/src/jemalloc.c:1422: error: undefined reference to 'pthread_atfork'
external/jemalloc/src/jemalloc.c:1422: error: undefined reference to 'pthread_atfork'
external/jemalloc/src/jemalloc.c:1422: error: undefined reference to 'pthread_atfork'
external/jemalloc/src/jemalloc.c:1358: error: undefined reference to 'atexit'
clang80: error: linker command failed with exit code 1 (use -v to see invocation)
```
and
```
cannot find crtbegin_dynamic.o: No such file or directory
clang80: error: linker command failed with exit code 1 (use -v to see invocation)
```
I initially suspected that this might have something to do with the different API or NDK versions used by rust-lang/rust vs the ones in the PR which are newer, but the part of the test script that fails is the one that has `--no-default-features` in it, which means that `use_std` is disabled, so only `libcore` should be linked, so this shouldn't be an issue.
The Android build jobs have been failing for a couple of months already, and we have been adding linux APIs that might have been breaking Android because they are not properly scoped, so getting these up and running again is kind of important for Android support. | A-linkage,O-android,T-compiler,C-bug | low | Critical |
445,406,603 | pytorch | Main page broadcasting (?) example image bug | ## ๐ Bug
There is an image on the main page of this repo:
Looks like the numbers on the result tensor are wrong (and pretty unreadable btw).
| module: docs,triaged | low | Critical |
445,420,468 | terminal | Missing operator delete/delete[] for some allocated objects | Hi.
Looks like there are few places in the Terminal code where I can suspect a memory leaks due to missing `operator delete` or `operator delete[]`.
These allocation sites can be grouped into following:
- raw `operator new` without `operator delete` like this https://github.com/Microsoft/Terminal/blob/master/src/cascadia/TerminalConnection/ConptyConnection.cpp#L191
- allocation by `operator new` some global object or class member (https://github.com/Microsoft/Terminal/blob/master/src/cascadia/TerminalControl/TermControl.cpp#L281)
- allocation by `operator new` some memory in a function and return it by raw pointer, which can leak then.
Here is my gist with quite a simple grep for`operator new` calls - https://gist.github.com/dreamer-dead/c43248466fc4d445378b4dfba80d8d25
Is this an intentional behaviour or a bug that should be fixed? | Product-Conhost,Help Wanted,Issue-Bug,Area-CodeHealth | low | Critical |
445,537,822 | go | runtime: optimization to reduce P churn | # Background
The following is a fairly frequent pattern that appears in our code and others:
goroutine1:
```
ch1 <- data (1)
result = <-ch2 (2)
```
goroutine2:
```
data = <- ch1 (3)
// do work...
ch2 <- result (4)
```
The scheduler exhibits two different behaviors, depending on whether goroutine2 is busy and there are available Ps.
- If goroutine2 is busy or there are no idle Ps, then the behavior is fine. The item will be enqueued in the channel, goroutine2 is marked as runnable if needed, and eventually goroutine1 will yield.
- If goroutine2 is not busy and there are idle Ps, then the behavior is sub-optimal. The operation in (1) will mark goroutine2 as runnable, and wake up some idle P via a relatively expensive system call [1]. Ultimately the wake will likely result in an IPI to wake an idle core, if there are any. The next P will be scheduled and a race to (2) and (3) ensures.
In the second case, if the P wakes and successfully steals the now runnable goroutine2, i.e. (3) happens first, then it will start executing on the new P. Unfortunately, the whole dance will happen again with the result. If the P wakes but does not successfully steal the now runnable goroutine2, i.e. (4) happens first and goroutine2 is run locally, then a large number of cycles are wasted. Either way, this dance happens again with the result. In both cases, we spend a large number of cycles and interprocessor co-ordination costs for what should be a goroutine context switch.
These are further problems caused by this, as it will introduce unnecessary work stealing and bouncing of goroutines between system threads and cores. (Leading to locality inefficiencies.)
# Ideal schedule
With an oracle, the ideal schedule after (1) would be:
- If goroutine2 is running or there are no idle Ps, enqueue only (current behavior).
- If goroutine1 will not block or has other goroutines in its runqueue, wake idle Ps (current behavior).
- If goroutine1 will block immediately, and there are no other goroutines in P's local runqueue, **do not wake up any other Ps**. The goroutine2 will be executed by the current P immediately after goroutine1 blocks.
In essence, we want to yield the goroutine1's time to goroutine2 in this case, or at least avoid all the wasted signaling overhead. To put it another way: if goroutine1's P will block, then it fills the role of the "idle P" far more efficiently.
# Proposal
It may be possible to specifically optimize for this case in the compiler, just as certain loop patterns are optimized.
In the case where a blocking channel send is immediately followed by a blocking channel receive, I propose an optimization that tries to avoid these scheduler round trips.
Here's a rough sketch of the idea:
- runqput returns a bool that indicates whether the newly placed G is the only item on the queue. (Alternatively we could just check the runq length below.)
- goready takes an additional parameter "deferwake" which skips the wake operation if true. By default this will be false everywhere, which implements current behavior.
- chansend accepts a similar "deferwake" parameter. This is plumbed through to send, and will be AND'ed with the result of runqput. The deferwake parameter will be passed as true if the compiler detects a blocking receive immediately following the blocking send statement (or possibly in the same block, see below).
- chanrecv also accepts a "deferwake" parameter, which will be set to true only when proceeded by a call to chansend with deferwake also set to true. If this is true AND the current goroutine will not yield as a result of the recv AND the current runqueue length > 0 AND there are idle Ps, at this point we can call wakeup.
# Rejected alternatives
I thought about this problem a few years ago when it caused issues. In the past, I considered the possibility of a different channel operator. Something like:
ch1 <~ data
This operator would write to the channel and immediately yield to the other goroutine, if it was not already running (otherwise would fall back to the existing channel behavior). Using this operator in the above situation would make it much more efficient in general.
However, this is a language change, and confusing to users. When do you use which operator? It would be good to have the effect of this optimization out of the box.
# Extensions
- This optimization may apply to other kinds of wakes. I consider only channels today.
- The optimization could be extended to cases where a blocking channel receive appears following the blocking send in the same block, not necessary the subsequent statement.
[1] https://github.com/golang/go/blob/master/src/runtime/proc.go#L665 | Performance,NeedsInvestigation | medium | Major |
445,541,525 | flutter | Attach output should give clear instructions when application is already started | Internal: b/132252088
The attach output (if not run with debug-uri or url) currently says:
```
Waiting for a connection from Flutter on Pixel 3 XL...
```
which does not prompt for a user action.
We should likely enrich this to say:
```
If your app is already running, please restart it (or pass --debug-uri <observatory_url>)
Waiting for your app to run on Pixel 3 XL...
``` | c: new feature,platform-android,tool,a: quality,P3,team-android,triaged-android | low | Critical |
445,543,379 | vscode | Have `createQuickPick` no longer sort by label | <!-- Please search existing issues to avoid creating duplicates. -->
<!-- Describe the feature you'd like. -->
Similar to https://github.com/microsoft/vscode/issues/63050, I wish to avoid the final sort on the quick pick list. I am using the quickpick as a search field, and the `items` field I set is already sorted by my relevance metric, so I do not want to have VS Code sort the list again . Specifically, I want an option to skip this block: https://github.com/microsoft/vscode/blob/a69d0f8b218498e22b7c3a0f76926cc6322e6106/src/vs/workbench/browser/parts/quickinput/quickInputList.ts#L518-L523)
| feature-request,api,quick-pick,api-proposal | medium | Critical |
445,547,347 | flutter | MergeSemantics should not forcibly merge nodes marked as "explicitChildNodes" | When the MergeSemantics widget attempts to merge its descendants' Semantics nodes, it throws the following assertion:
```
flutter: 'package:flutter/src/semantics/semantics.dart': Failed assertion: line 2446 pos 16: 'node.parent ==
flutter: null || !node.parent.isPartOfNodeMerging || node.isMergedIntoParent': is not true.
```
I think that
1. the assert message could be clearer in notifying the developer on what is actually causing this problem
2. we should making sure the MergeSemantics documentation properly suggests this could happen
Issue first described in https://github.com/flutter/flutter/issues/31437
EDIT: Now, the goals are as follows:
1. The MergeSemantics algorithm should be updated to keep semantics nodes marked with explicitChildNodes as its own children. This allows for applications that are properly annotated/described semantically to remain as such without forcing developers to make any changes.
2. Remove the semantics examples in Switch/Checkbox/RadioListTile docs, since they will be rendered unnecessary once MergeSemantics no longer attempts to forcibly merge its children. | framework,a: accessibility,d: api docs,a: quality,c: proposal,a: error message,P3,team-framework,triaged-framework | low | Critical |
445,570,267 | go | encoding/json: accept float starting with "." (".85") while unmarshaling json with ,string tag | ### What version of Go are you using (`go version`)?
<pre>
โฏ go version
go version go1.12.5 darwin/amd64
</pre>
### Does this issue reproduce with the latest release?
yes
### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/ashwin/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/ashwin/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.12.5/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.12.5/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/nl/_f7rxwqs2y730r18nk0shs240000gn/T/go-build739953451=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>
### What did you do?
Tried unmarshaling json that contained float string starting with "."
The playground link below contains 3 examples
1. json unmarshal with ".85" -- fails
2. json unmarshal with "0.85" -- succeeds
3. strconv.ParseFloat ".85" -- succeeds
https://play.golang.org/p/q4OFvV6Asxt
### What did you expect to see?
I expect ".85" to be successfully converted to a float using unmarshal
".85" -> 0.85
### What did you see instead?
this error: `json: invalid use of ,string struct tag, trying to unmarshal ".85" into float64`
| NeedsDecision | low | Critical |
445,574,088 | go | x/net/ipv4: wrong endianness in IP header on darwin-amd64 | <!-- Please answer these questions before submitting your issue. Thanks! -->
### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.11.5 darwin/amd64
</pre>
### Does this issue reproduce with the latest release?
Yes
### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/rhuang/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/rhuang/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.11.5/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.11.5/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/xy/qpsgj2816g97b0ctzkq0ps_r0000gs/T/go-build097375093=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>
### What did you do?
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
marshall IPv4 IP header with x/net/ipv4/header, but I got little-endian instead of big-endian.
### What did you expect to see?
Got big-endian IP header len.
### What did you see instead?
little-endian
Looking at By looking at the code https://github.com/golang/net/blob/master/ipv4/header.go#L71., for darwin, 32bit/64bit os should have a different conversion.
Darwin amd64 is little-endian, it should convert. | help wanted,OS-Darwin,NeedsInvestigation | low | Critical |
445,580,472 | pytorch | nn.Embedding backwards slow under high row contention | ## ๐ Bug
nn.Embedding backward is very slow when there is high contention for a small number of rows in the embedding matrix. This can be ameliorated with different approaches to backward in this case.
## To Reproduce
Steps to reproduce the behavior:
```
import torch
import torch.nn as nn
from torch.nn import Parameter
class ParameterEmb(nn.Module):
def __init__(self, n, dim):
super().__init__()
self.emb = Parameter(torch.zeros(n, dim))
def forward(self, input):
return self.emb.index_select(0, input)
class OneHotEmb(nn.Module):
def __init__(self, n, dim):
super().__init__()
self.n = n
self.emb = nn.Linear(n, dim, bias=False)
def forward(self, input):
onehot = torch.zeros(input.size(0), self.n, device=input.device)
onehot.scatter_(1, input.unsqueeze(1), 1)
return self.emb(onehot)
def forward_backward(M, x):
return M(x).sum().backward()
N, D = 100, 100
E = nn.Embedding(N, D)
PE = ParameterEmb(N, D)
OHE = OneHotEmb(N, D)
```
Lets first time everything with a uniform distribution over input rows:
```
x = (torch.arange(10000, dtype=torch.long) % N)
%timeit forward_backward(E, x)
%timeit forward_backward(PE, x)
%timeit forward_backward(OHE, x)
E.cuda()
PE.cuda()
OHE.cuda()
x = x.cuda()
%timeit forward_backward(E, x)
%timeit forward_backward(PE, x)
%timeit forward_backward(OHE, x)
```
Everything is fine here
```
CPU Emb 2.87 ms ยฑ 53.8 ยตs per loop (mean ยฑ std. dev. of 7 runs, 100 loops each)
CPU Param 12.8 ms ยฑ 496 ยตs per loop (mean ยฑ std. dev. of 7 runs, 10 loops each)
CPU OneHOt 2.9 ms ยฑ 288 ยตs per loop (mean ยฑ std. dev. of 7 runs, 100 loops each)
GPU Emb 343 ยตs ยฑ 660 ns per loop (mean ยฑ std. dev. of 7 runs, 1000 loops each)
GPU Param 150 ยตs ยฑ 238 ns per loop (mean ยฑ std. dev. of 7 runs, 10000 loops each)
GPU OneHOt 231 ยตs ยฑ 983 ns per loop (mean ยฑ std. dev. of 7 runs, 1000 loops each)
```
But if I have high contention on a single row, Embedding becomes 20x slower while other approaches do not.
```
x = torch.zeros(10000, dtype=torch.long)
CPU Emb 31.5 ms ยฑ 248 ยตs per loop (mean ยฑ std. dev. of 7 runs, 10 loops each)
CPU Param 12.8 ms ยฑ 66.9 ยตs per loop (mean ยฑ std. dev. of 7 runs, 10 loops each)
CPU OneHOt 2.52 ms ยฑ 95.6 ยตs per loop (mean ยฑ std. dev. of 7 runs, 100 loops each)
GPU Emb 6.34 ms ยฑ 348 ns per loop (mean ยฑ std. dev. of 7 runs, 100 loops each)
GPU Param 513 ยตs ยฑ 198 ns per loop (mean ยฑ std. dev. of 7 runs, 1000 loops each)
GPU OneHOt 205 ยตs ยฑ 500 ns per loop (mean ยฑ std. dev. of 7 runs, 1000 loops each)
```
## Environment
```
PyTorch version: 1.0.1.post2
Is debug build: No
CUDA used to build PyTorch: 9.0.176
OS: Ubuntu 18.04.1 LTS
GCC version: (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
CMake version: version 3.12.1
Python version: 3.7
Is CUDA available: Yes
CUDA runtime version: Could not collect
GPU models and configuration:
GPU 0: Quadro GP100
...
Nvidia driver version: 410.79
cuDNN version: Could not collect
Versions of relevant libraries:
[pip3] numpy==1.15.2
[pip3] torch==1.0.1.post2
[pip3] torchbiggraph==1.dev0
[pip3] torchvision==0.2.1
[conda] blas 1.0 mkl
[conda] mkl 2019.0 118
[conda] mkl_fft 1.0.6 py37h7dd41cf_0
[conda] mkl_random 1.0.1 py37h4414c95_1
[conda] torch 1.0.1.post2 pypi_0 pypi
[conda] torchvision 0.2.1 py37_1 pytorch
``` | module: performance,module: nn,module: cuda,triaged | low | Critical |
445,614,433 | rust | rustdoc: private module appears when overriding glob re-export | Consider this code in a crate's lib.rs:
```rust
mod m1 {
pub mod m2 {
pub struct Foo;
}
}
pub use m1::*;
use crate::m1::m2;
```
The generated documentation will show the `m2` module at the crate root, though nothing will show up inside the `m2` module page. The `m2` module is private to outside crates, so I don't think it should be showing up at all.
## Meta
`rustc --version --verbose`:
rustc 1.36.0-nightly (7d5aa4332 2019-05-16)
binary: rustc
commit-hash: 7d5aa43325ad7629766b1183011f5bf5b2a1ea26
commit-date: 2019-05-16
host: x86_64-pc-windows-msvc
release: 1.36.0-nightly
LLVM version: 8.0 | T-rustdoc,A-visibility,C-bug | low | Minor |
445,639,281 | youtube-dl | Pleas look at radioklassik.at | <!--
######################################################################
WARNING!
IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################
-->
## Checklist
<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.05.11. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->
- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.05.11**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones
## Example URLs
<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->
- Single audio: https://radioklassik.at/programm/sendungsdetails/?sdk=rubato&sdd=17.05.2019
## Description
Even doe't work with supported High sierra
<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->
youtube-dl -v 'https://radioklassik.at/programm/sendungsdetails/?sdk=rubato&sdd=17.05.2019'
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://radioklassik.at/programm/sendungsdetails/?sdk=rubato&sdd=17.05.2019']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2019.05.11
[debug] Python version 3.7.3 (CPython) - Darwin-15.6.0-x86_64-i386-64bit
[debug] exe versions: avconv 12.3, avprobe 12.3, ffmpeg 4.1.1, ffprobe 4.1.1, rtmpdump 2.4
[debug] Proxy map: {}
[generic] ?sdk=rubato&sdd=17.05: Requesting header
WARNING: Falling back on generic information extractor.
[generic] ?sdk=rubato&sdd=17.05: Downloading webpage
[generic] ?sdk=rubato&sdd=17.05: Extracting information
ERROR: Unsupported URL: https://radioklassik.at/programm/sendungsdetails/?sdk=rubato&sdd=17.05.2019
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 796, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 529, in extract
ie_result = self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 3329, in _real_extract
raise UnsupportedError(url)
youtube_dl.utils.UnsupportedError: Unsupported URL: https://radioklassik.at/programm/sendungsdetails/?sdk=rubato&sdd=17.05.2019
| site-support-request | low | Critical |
445,658,291 | flutter | Add memory leak test | Make sure we don't get regressions on the embedding or in the engine. We manually tested and fixed issues for 1.12 to make sure the show screen, dismiss screen cycle doesn't cost any memory on a pre-warmed engine. Make sure it's locked it.
Examples:
- https://github.com/flutter/flutter/issues/61558
- https://github.com/flutter/engine/pull/9288
- https://github.com/flutter/engine/pull/18657
- https://github.com/flutter/engine/pull/17646
- https://github.com/flutter/flutter/issues/45499
- https://github.com/flutter/flutter/issues/56482
- https://github.com/flutter/flutter/issues/65941 | a: tests,team,engine,c: performance,a: existing-apps,perf: memory,P3,team-engine,triaged-engine | low | Major |
445,672,355 | terminal | Code Cleanup - Member variables not initialized in GdiEngine's constructor | Minor Code cleanup
In src/renderer/gdi/state.cpp
GdiEngine's constructor is not initializing all of it's member variables.
_isTrueTypeFont
_fontCodepage
_tmFontMetrics
_coordFontLast
_psInvalidData
In Debug only
_debugWindow
_debugContext
As far as I can tell, none of the above variables are used before being initialized (in the normal code path). Most of these get set in UpdateFont and _CreateDebugWindow. It might make sense to make a pass and initialize these in the header with default values. Some members are correctly being set to a default value in the constructor, but it might be better for maintainability to remove those and initialize them in the header also.
| Product-Conhost,Issue-Bug,Area-Build | low | Critical |
445,674,705 | terminal | Callback function passed to EnumFontFamiliesExW uses wrong signature | Example callback function used with `EnumFontFamiliesExW`:
```cpp
int CALLBACK FontEnumForV2Console(ENUMLOGFONT *pelf, NEWTEXTMETRIC *pntm, int nFontType, LPARAM lParam);
```
But `FONTENUMPROC` as expected by `EnumFontFamiliesExW` is defined as follows (SDK 10.0.18362.0):
```cpp
typedef int (CALLBACK* OLDFONTENUMPROCW)(CONST LOGFONTW *, CONST TEXTMETRICW *, DWORD, LPARAM);
```
In practice, the differing argument types are representation-compatible anyway, so it works fine, but it does require a cast on the function pointer. It was suggested in #871 to get this sorted out.
Affected files:
```none
>git grep FONTENUMPROC
src/propsheet/misc.cpp: EnumFontFamiliesEx(hDC, &LogFont, (FONTENUMPROC)((ShouldAllowAllMonoTTFonts()) ? FontEnumForV2Console : FontEnum), (LPARAM)&fed, 0);
src/renderer/gdi/tool/main.cpp: EnumFontFamiliesExW( hDC, &lf, (FONTENUMPROC)EnumFontFamiliesExProc, 0, 0 );
src/tools/fontlist/main.cpp: EnumFontFamiliesExW(hdc.get(), &LogFont, (FONTENUMPROC)FontEnumForV2Console, (LPARAM)hdc.get(), 0);
```
BTW, `src/renderer/gdi/tool/main.cpp` is not included in any project in the solution, preventing it to be scanned by an IDE. Is that intentional? | Product-Conhost,Help Wanted,Issue-Bug,Area-CodeHealth | low | Minor |
445,678,834 | flutter | Vertical `Dismissible` does not dismiss `SingleChildScrollView` (nor` ListView`) | Internal: b/132630514
The following code snippet demonstrates that Dismissible cannot be used for implementing the common pattern of swipe downwards to dismiss screen (where the screen contains a scrollable). This pattern appears for example in the image viewer in Google Search App, in the directions screen of Google Maps and more.
Expected behaviour: On dragging downwards, the list starts moving (not scrolling) downwards.
Observed behaviour: On dragging downwards, the list overscrolls (and cannot be dismissed)
Dismissible(
direction: DismissDirection.down,
key: Key("dismissible"),
child: SingleChildScrollView(
child: Container(
color: Colors.green,
child: Column(
children: [
Text("Example", style: TextStyle(fontSize: 50)),
Text("Example", style: TextStyle(fontSize: 50)),
Text("Example", style: TextStyle(fontSize: 50)),
Text("Example", style: TextStyle(fontSize: 50)),
Text("Example", style: TextStyle(fontSize: 50)),
Text("Example", style: TextStyle(fontSize: 50)),
Text("Example", style: TextStyle(fontSize: 50)),
Text("Example", style: TextStyle(fontSize: 50)),
Text("Example", style: TextStyle(fontSize: 50)),
Text("Example", style: TextStyle(fontSize: 50)),
Text("Example", style: TextStyle(fontSize: 50)),
Text("Example", style: TextStyle(fontSize: 50)),
],
),
),
),
),
--- This information is sufficient for reproducing the bug. Below we provide some further details. --
Variation 1: Changing the direction to horizontal, allows for the view to be dismissed horizontally.
Variation 2: Removing some items from the SingleChildScrollView allows for the view to be dismissed vertically.
Variation 3: Changing SingleChildScrollView with ListView does not solve the issue.
Further investigation: It seems that a GestureDetector over SingleChildScrollView, even when using HitTestBehavior.opaque, will never get any vertical gesture event. For our prototype, we solved this issue using a stack with the scrollable and a gesture detector that decides whether to dismiss or to forward gestures to the scrollable. However, the code becomes much complicated. | framework,f: scrolling,customer: google,has reproducible steps,P2,found in release: 1.21,found in release: 2.2,workaround available,team-framework,triaged-framework | low | Critical |
445,687,763 | go | cmd/go: ambiguous error message on ambiguous import | ### What version of Go are you using (`go version`)?
1.12
### Does this issue reproduce with the latest release?
yes
### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/user/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/user/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build116507160=/tmp/go-build -gno-record-gcc-switches"
```
### What did you do?
I deal with a problem of ambiguous module import when I try to import `github.com/spf13/[email protected]` and `github.com/gin-gonic/[email protected]`
https://play.golang.org/p/NwzVwWsOjbO
### What did you expect to see?
@thepudds (thx to him for his support) has advised me to open a issue to have clearer diagnostic message or a simpler solution.
the proposed solution, that works for me, is:
` go get github.com/ugorji/go/codec@none`
https://groups.google.com/forum/#!topic/golang-nuts/0mJh8SkaomA
| NeedsInvestigation,modules | low | Critical |
445,722,817 | pytorch | [distribution] Support for various domain for AffineTransform | ## ๐ Feature
Currently, AffineTransform's domain and codomain are `real`. So transformed distribution with affine transform will return `real` support by default. It would be great if we allow several more domains such as `greater_than` or `interval`. cc @neerajprad who is also interested in this feature.
Related issue: currently, `transform_to(constraints.interval(a, b))`'s codomain is real; while it should be `constraints.interval(a, b)`.
## Motivation
This will be helpful so that users don't have to redefine `support` for such transformed distributions.
## Alternatives
A simple solution is to allow a `domain` arg in AffineTransform initialization. Then we can define `codomain` as a dependent property. This way, we can fix the above issue at `constraint_registry` by using
```
def _transform_to_greater_than(constraint):
return transforms.ComposeTransform([transforms.ExpTransform(),
transforms.AffineTransform(constraint.lower_bound, 1,
domain=constraint.positive)])
```
or
```
def _transform_to_interval(constraint):
...
return transforms.ComposeTransform([transforms.SigmoidTransform(),
transforms.AffineTransform(loc, scale,
domain=constraint.unit_interval)])
```
cc @fritzo @neerajprad @alicanb @vishwakftw who are maintainers of distributions library
| module: distributions,triaged | low | Major |
445,723,137 | godot | Script gets shadow-removed when _init(arg) + tool | <!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->
**Godot version:**
3.1.1 official
<!-- Specify commit hash if non-official. -->
**OS/device including version:**
windows 10
<!-- Specify GPU model and drivers if graphics-related. -->
**Issue description:**
Script disappears from scene, when the script is a tool-script and there is a non-standard _init() method in the script. When i delete one or the other ("tool" or "_init(arg)" ) the script reappears.
When being used with the standard "_init()" it works as intended and the script doesnt disappear from the scene.
When i run the scene with the script not showing up in the scene-tree, the script wont exist (not attached to the node it actually should be)
I was fighting with this bug for about an hour, working with signals, wondering if i did my signals wrong, but actually it was this culprit, that my scripts just didnt exist while i ran the scene.
My expectation would be, if this is a mistake from my side, to get an error-message to show or it being fixed, if its a bug.
<!-- What happened, and what was expected. -->
**Steps to reproduce:**
**Minimal reproduction project:**
You can try it out, by opening the scene "Control.tscn" and opening the script "script_with_error.gd" by removing or adding the "tool" or the "_init(arg)".
[reproduction_project.zip](https://github.com/godotengine/godot/files/5066152/script.%2B.tool.shadow-remove.zip)
<!-- Recommended as it greatly speeds up debugging. Drag and drop a zip archive to upload it. -->
Edit: Replaced the MRP with a project created in 3.2.3.rc3
| bug,topic:gdscript,confirmed | low | Critical |
445,738,472 | create-react-app | react-error-overlay fails to parse typescript errors | ### Is this a bug report?
yes
### Which terms did you search for in User Guide?
react-error-overlay
### Environment
<details>
<summary>Environment</summary>
System:
OS: macOS 10.14.5
CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Binaries:
Node: 12.2.0 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Browsers:
Chrome: 74.0.3729.157
Firefox: 66.0.5
Safari: 12.1.1
npmPackages:
react: ^16.8.6 => 16.8.6
react-dom: ^16.8.6 => 16.8.6
react-scripts: 3.0.1 => 3.0.1
npmGlobalPackages:
create-react-app: 3.0.0
</details>
### Steps to Reproduce
In a create-react-app typescript project:
1. Start the development server
2. Make a typescript error in any file (```let a: string = 0``` for example).
3. The error overlay displays the error, however clicking on the exception does not navigate to the file in the text editor as with other webpack errors.
### Expected Behavior
Clicking on the error overlay navigates to the file in a text editor.
### Actual Behavior
The error overlay isn't clickable.
### Details
React-error-overlay tries parsing the exception by looking for a filepath in the error message. This is handled in [parseCompileError.js](https://github.com/facebook/create-react-app/blob/4704382558fe6f0d7564c72ce65d45e441a3ff61/packages/react-error-overlay/src/utils/parseCompileError.js), where the filepath regex matches only relative paths:
```js
const filePathRegex = /^\.(\/[^/\n ]+)+\.[^/\n ]+$/;
```
whereas typescript errors use absolute paths. As discussed in https://github.com/facebook/create-react-app/pull/6502#discussion_r259686344 making the paths relative has some drawbacks so it would be best to keep them absolute.
Also TS error locations are specified like `(line,colon)` so we would need to add that format to the lineNumberRegexes array.
I can submit a PR for this if that's okay. | issue: bug | low | Critical |
445,743,840 | TypeScript | const module = {}; export = module | <!-- ๐จ STOP ๐จ ๐ฆ๐ง๐ข๐ฃ ๐จ ๐บ๐ป๐ถ๐ท ๐จ
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!
Please help us by doing the following steps before logging an issue:
* Search: https://github.com/Microsoft/TypeScript/search?type=Issues
* Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ
Please fill in the *entire* template below.
-->
<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:** 3.4.0-dev.201xxxxx
<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
**Code**
```ts
const module = {
}
export = module
```
**Expected behavior:**
```js
const module_1 = {};
module.exports = module_1;
```
**Actual behavior:**
```js
const module = {};
module.exports = module;
```
**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->
**Related Issues:** <!-- Did you find other bugs that looked similar? -->
| Bug | low | Critical |
445,765,122 | PowerToys | Power Plan Switching (automatic too) | I use Full Throttle Override to force my CPU to a certain power plan automatically when a certain application is run (music production DAW in my case). It's the only app of its kind out there, and isn't under further development. I think this would be a perfect case for a Power Toy. Thanks! | Idea-New PowerToy,Product-Power management | low | Major |
445,770,573 | go | cmd/go: building a test binary with "go test -c" probably shouldn't run vet | While working on some slow full emulation qemu VMs, I noticed `go test -c` was much slower than expected. Looking at top, I saw `vet` eating CPU.
It seems surprising that we default to running vet on a flag that's described as:
> Compile the test binary to pkg.test but do not run it
Any vet output would look like a test failed and thus ran, even if it's not technically a test.
I vote we turn it off for `-c`. @bcmills, @jayconrod, @ianlancetaylor, @rsc?
In any case, it's not critical. Now I know to always use `-vet=off` with `-c`:
```
gopher@buildlet:~/go/src/io$ time ../../bin/go test -c
real 0m28.740s
user 0m14.184s
sys 0m9.208s
gopher@buildlet:~/go/src/io$ time ../../bin/go test -c -vet=off
real 0m19.385s
user 0m9.772s
sys 0m6.488s
gopher@buildlet:~/go/src/io$ time ../../bin/go test -c
real 0m28.651s
user 0m16.804s
sys 0m10.260s
gopher@buildlet:~/go/src/io$ time ../../bin/go test -c -vet=off
real 0m18.051s
user 0m10.504s
sys 0m6.692s
```
Marking for Go 1.14, unless this is a recent regression. I didn't check. | NeedsDecision | low | Critical |
445,774,902 | pytorch | In-source build causes repeating filename annotations (Windows doesn't support out-of-source build) | We are seeing filenames in `aten/src/ATen/native/cpu/` like the following cases:
```
Activation.cpp
Activation.cpp..cpp
Activation.cpp..cpp..cpp
Activation.cpp.AVX.cpp
Activation.cpp.AVX.cpp..cpp
Activation.cpp.AVX.cpp..cpp..cpp
Activation.cpp.AVX.cpp.AVX.cpp
UnaryOpsKernel.cpp.DEFAULT.cpp.DEFAULT.cpp.AVX2.cpp.AVX2.cpp
UnaryOpsKernel.cpp.DEFAULT.cpp.DEFAULT.cpp.DEFAULT.cpp.AVX2.cpp
UnaryOpsKernel.cpp.DEFAULT.cpp.AVX.cpp.DEFAULT.cpp.AVX2.cpp
```
They will slow down the build, and sometimes even make it hang if we don't clean the build cache and do the in-source build.
Edit: This can also cause multiple symbol definition problem
cc @ezyang @gchanan @zou3519 @peterjc123 | module: build,module: windows,triaged | medium | Major |
445,796,882 | flutter | Document what lifecycle events users need to manually hook up when using FlutterEngine without a FlutterFragment | FlutterFragment communicates lifecycle events to its FlutterEngine. These lifecycle events impact Flutter's internal lifecycle state, e.g., whether or not rendering is paused.
Document these details in the JavaDocs for FlutterEngine and FlutterFragment.
Include this info in a guide that explains all details of utilizing a FlutterView directly. | platform-android,engine,d: api docs,a: existing-apps,dependency: android,P2,team-android,triaged-android | low | Minor |
445,799,457 | flutter | Support espresso/EarlGrey integration tests on engine PRs | espresso has a doc at go/espresso-flutter-api | a: tests,c: new feature,team,engine,P3,team-engine,triaged-engine | low | Major |
445,805,757 | TypeScript | Module resolution - four issues (specific and simple to general) | I know there have been plenty of questions around module resolution, I read some of them (SO and here). I still have these issues: The most general one last, the most specific one first.
# 1 Fix documentation
From page https://www.typescriptlang.org/docs/handbook/module-resolution.html
> **_Classic_**
>
> This used to be TypeScriptโs default resolution strategy. Nowadays, this strategy is mainly present for backward compatibility.
But "Classic" still **is** the default, no?
This sounds like it should not be the default.
# 2 Don't ascend above project directory
*(At least not by default, or provide an option to prevent it.)*
Why is TS allowed, by default, to ascend up out of the project directory?
I have a folder `Projects/` with various projects, some included by others, but via packages and not directly from those directories but they have the same name locally. What happens is that when I run `tsc` in one of those projects it ends up including definitions from another project instead of from `node_modules/`, which makes no sense to me. I mean I get it if that was an optional behavior, but by default going into folders that don't belong to the project?
How can I prevent tsc from looking for anything outside the current project's directory?
# 3 Include node_modules in module resolution
What I mean is that it should always be used, or at least make it configurable but not as it is now where it depends on module resolution "node". The use of `node_modules` is not node.js specific at this time.
I'm also confused because TS _does_ find things `<PROJECT_ROOT>/node_modules`, it only finds `@types` imports. I bundle .d.ts files in my own library, which since it's internal and private has no way to get its .d.ts published via DefintelyTyped. When I import from "myLib/lib/someFile", for which a .js and a .d.ts and a .d.ts.map file exists, it only finds it in "node" module resolution mode.
It may as well include that folder in its search even in "Classic" mode, that IMHO makes more sense than the search outside the project directory.
# 4 Module resolution depends on build target
*First I checked if this still applies, and it does.*
In reference to:
- https://github.com/Microsoft/TypeScript/issues/8189#issuecomment-212082894
- https://github.com/Microsoft/TypeScript/issues/18865#issuecomment-333412703 ("_An issue here is that the module resolution strategy we use is determined by your compiler options..._ ")
1. I don't see that mentioned in the docs (page linked above)
2. I don't understand the purpose
At least for me, the build and development are orthogonal. I build for browser, react-native, node.js and experimentally even for two embedded platforms (Moddable, low.js) and I don't see why my code structure used for development should depend on the build target! After transpiling (here using Babel, but that would be the same if we used TS for that) module resolution on the various platforms is vastly different. From webpack-packages to a "flat" module namespace (Moddable, many platforms use their own very different module handling. Whether Webpack or Moddable find a module has nothing whatsoever to do with TypeScript used while writing the code and how it type-checks and finds modules.
IMHO development time module resolution should not depend on the build target.
My own build target is "esnext" (I also have `"noEmit": true` because I only use TS at development time, if there is any transpilation it is done by Babel, usually that's just removing the type annotations and maybe a — flexible — module system target), but even node supports ES2015 modules these days, so I don't think there is the direct connection between "commonjs" and "node_modules" any more, if ever there was.
Especially since the support of the Babel option the distinction that already and always existed between development with type checks (when the type checker needs to be able to find a) included modules, but b) also just type info like .d.ts files which have no runtime equivalent and there location surely should not depend on what the build target is), transpiling and packaging, and running the code, probably deserves another look to remove unnecessary cross-concern bindings like module resolution (used for type checking) depending on transpilation (which does not even need to know about where to find modules since it is in between type checking and runtime).
On a more general note, I think TS has too tight a coupling because those concerns, which despite all efforts I can see even here in the "Issues" in reaction to feature requests where anything that would make TS different from JS is routinely rejected, leads to a lot of confusion esp. among new(er) developers (to the ecosystem, not necessarily by age) that TS is a different language. Especially since Babel workflows are officially supported too now the more clear separation of development time (type checking) and transpilation might be beneficial. It's not even a code change, maybe a few tsconfig layout changes at most.
As an aside, there is even more of a disconnect between development and runtime. I, for example, use TSypeScript only for type checking. It's a setup I could also run with Flow, same for anyone that uses Babel for transpilation (many people don't seem to know, all the Babel-TS plugin does is remove the types, because then TypeScript code is just "ESnext" *(if one doesn't use namespaces, enums, import=/export=)*.
That means I use tsc only from the IDE as language service and for type checks. It (tsc) only needs to understand the layout of the code *during development*. It does not need to concern itself with either transpilation or where modules might be found during runtime — especially the latter, in the days of Webpack & Co., is something `tsc` does not need to know. So finding files and types (.d.ts) during development should be separate from finding code modules during runtime, and TS should focus on the former (the latter is the domain of various build systems anyway, which have their very own ideas).
That means that, for example, I can use TS-only features like namespaces for my *types* (inside a .d.ts file) even if I would not or can't use it in my code. In my particular case it helps with type checks (declaration merging between a private lib an apps using it, just my particular private case and example).
So in my — I would claim not unusual — setup, **1)** type checking (by tsc), **2)** transpiling (by Babel), **3)** packaging (Webpack, Moddable compiler, React Native, and others) and then **4)** the actual runtime all are disconnected. This is in line with the architecture of TS I think, the merging of concerns is, I think, a product of user-facing components. I don't think tying those components together, for example by binding module resolution (used during development for type checks) on a build target (used only when actually building, and even that does not necessarily need to be done with tsc since there is the Babel option) is not good.
| Suggestion,Needs Proposal | low | Minor |
445,808,515 | godot | Open compressed files that were not made by godot | **Godot version:** 33897d9b5844aa0147d55841845427ed599d069f
<!-- Specify commit hash if non-official. -->
**OS/device including version:** Linux 4.14.113-1-MANJARO
<!-- Specify GPU model and drivers if graphics-related. -->
**Issue description:**
<!-- What happened, and what was expected. -->
I was trying to load a gzipped json file from an external web server, and found out that I can't seem to find a way to do so in godot without making a gdnative plugin. File has the method open_compressed() which supports gzip, but the format it expects for gzip has [this bizarre gcpf magic header](https://github.com/godotengine/godot/blob/master/core/bind/core_bind.cpp#L1621) that encapsulates the format.
I kind of expected that it would at the very least open up compressed files that weren't made using the godot editor, assuming encryption wasn't used, considering at the end of the day it's just a bunch of strings or whatever other bytes in there. I'm not sure why the magic header exists in the compression format, but ideally if it could fall back to not requiring the magic header at all and just open up the file without it instead that would be cool.
If I ever need to edit a gzipped file that godot has made i can't just do a quick change from any other archive tools, i'll have to open up godot, open it up, edit it, and then re-export it in order for godot to continue being able to read it which is kind of annoying.
**Steps to reproduce:**
1. download a gzip'd file from anywhere or make one yourself using the command line
2. try and load it into godot using open_compressed or any other manner
**Minimal reproduction project:**
<!-- Recommended as it greatly speeds up debugging. Drag and drop a zip archive to upload it. -->
[test_compression.zip](https://github.com/godotengine/godot/files/3195000/test_compression.zip)
* there's a test.json.gz file at the root of the project file that was made using gzip on the command line, which has the same contents as the text edit that is in the project.
* If you click the "save gz" button it will save out a file to `user://test.json.gz`, and load it with "load gz". you can use this to compare the output that godot is expecting compared to the output from command-line gzip
* You can try to load the command-line gzip file by clicking the button on the bottom of the text edit, and if it fails it will spit out the error below. It will generally always be error 15 until something changes.
* There's also a checkbox to verify if the input is valid json or not.
| enhancement,topic:core,confirmed | medium | Critical |
445,808,658 | go | x/text/language: matcher incorrect handling of zh | ### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.12.5 darwin/amd64
</pre>
### Does this issue reproduce with the latest release?
Yes
### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/frederic/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/frederic/.go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.12.5/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.12.5/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/frederic/Creative/src/wayke/backend/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/h9/05jw9tbx44941w86t3ml3bmw0000gn/T/go-build309324644=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>
### What did you do?
Building on [CLDR LocalMatcher tests](https://github.com/golang/text/blob/342b2e1fbaa52c93f31447ad2c6abc048c63e475/language/testdata/CLDRLocaleMatcherTest.txt#L213), I tested the case where both `zh-CN` and `zh-HK` are supported and `zh-TW` is desired. I switched `CN` and `HK` relative positions in supported.
https://play.golang.org/p/4bG57qBzNQr
### What did you expect to see?
I expected `zh-HK` to be returned in both cases.
### What did you see instead?
`zh-HK` is returned when HK is before CN in supported, `en` is returned when CN precedes HK. | NeedsInvestigation | low | Critical |
445,812,437 | flutter | flutter attach should show DevTools in the resident runner and in IDEs | tool,a: existing-apps,P3,team-tool,triaged-tool | low | Minor |
|
445,827,687 | godot | Mono log profiler not working on Windows [upstream issue] | ___
***Bugsquad note:** This issue has been confirmed several times already. No need to confirm it further.*
___
**Godot version:**
3.1.1 Mono 64bit
**OS/device including version:**
Windows 10 64bit
**Issue description:**
The mono profiler that was added with https://github.com/godotengine/godot/pull/26513
isnt working, there is no output.mlpd in the project, %appdata%/Godot or near the Godot.exe
**Steps to reproduce:**
Run a program with the mono/profiler setting enabled. | bug,platform:windows,confirmed,topic:dotnet | low | Critical |
445,831,793 | godot | C# ImageTexture.CreateFromImage never released from VRAM? | **Godot version:**
v3.1.1.stable.mono.official
**OS/device including version:**
macOS 10.14.4/MacBookPro 2016
**Issue description:**
I have a subclass of `Spatial` which is instantiated periodically, and the constructor runs something like the following:
```c#
var groundImage = new Image();
groundImage.Create(2048, 2048, false, Image.Format.Rgb8);
// ...
var groundTexture = new ImageTexture();
groundTexture.CreateFromImage(groundImage);
```
It then attaches the texture to a material which is then used by a mesh which is added to its tree.
My understanding from the docs is that `Resource` subclasses such as `ImageTexture` are automatically freed, but even though I remove nodes from the scene, the texture memory monotonically increases.
<img width="485" alt="TextureMemMonitor" src="https://user-images.githubusercontent.com/334192/57984237-e1ac7600-7a27-11e9-8327-d98ab3669e1b.png">
The only workaround I've found is to manually track texture RID's and call `VisualServer.FreeRID()` when I no longer need them. Which perhaps is expected, but I didn't get that impression from the docs.
**Minimal reproduction project:**
This project creates a new `Chunk` spatial node every half second. The `Chunk()` constructor creates a `MeshInstance` child with its own texture. Whenever a new `Chunk` is created, the previous chunk is `QueueFree`'d.
[LeakReproduction.zip](https://github.com/godotengine/godot/files/3195234/LeakReproduction.zip)
```c#
using Godot;
class Chunk : Spatial
{
public Chunk()
{
var groundImage = new Image();
groundImage.Create(2048, 2048, false, Image.Format.Rgb8);
var groundTexture = new ImageTexture();
groundTexture.CreateFromImage(groundImage);
var material = new SpatialMaterial();
material.SetTexture(SpatialMaterial.TextureParam.Albedo, groundTexture);
var groundMesh = new PlaneMesh();
groundMesh.SetMaterial(material);
var ground = new MeshInstance();
ground.SetMesh(groundMesh);
}
}
public class MainScene : Spatial
{
void MakeATexture()
{
var newChunk = new Chunk();
AddChild(newChunk);
if (GetChildCount() > 2)
{
// Schedules the previous node to be removed from the scene.
// Shouldn't this result in freeing the node's texture?
GetChild(1).QueueFree();
}
}
public override void _Ready()
{
var timer = new Timer();
AddChild(timer);
timer.WaitTime = 0.5f;
timer.ProcessMode = Timer.TimerProcessMode.Physics;
timer.Connect("timeout", this, "MakeATexture");
timer.Start();
}
}
``` | bug,confirmed,topic:dotnet | low | Major |
445,859,452 | godot | Built-in scripts are exported in plain text | **Godot version:**
3.1.1
**Issue description:**
Embedded scripts in Scenes are getting exported in plain text, even if compile scripts is selected in export options. | bug,topic:gdscript,confirmed,topic:export | low | Minor |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.