golang April 2015

golang@lists.fedoraproject.org

2 participants
132 discussions

[Bug 1085881] Review Request: golang-github-spf13-cobra - A Commander for modern go CLI interactions
by Red Hat Bugzilla 20 Apr '15

20 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1085881 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|golang-github-spf13-cobra-0 |golang-github-spf13-cobra-0 |-0.7.git79bd93d.fc20 |-0.7.git79bd93d.el6 --- Comment #32 from Fedora Update System <updates(a)fedoraproject.org> --- golang-github-spf13-cobra-0-0.7.git79bd93d.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

Broken dependencies: golang-github-google-gofuzz
by Fedora Koji Build System 18 Apr '15

18 Apr '15

golang-github-google-gofuzz has broken dependencies in the epel-6 tree: On ppc64: golang-github-google-gofuzz-devel-0-0.5.gitbbcb9da.el6.noarch requires golang >= 0:1.2.1-3 Please resolve this as soon as possible.

1 0

Broken dependencies: golang-github-google-gofuzz
by Fedora Koji Build System 18 Apr '15

18 Apr '15

1 0

[Bug 1191438] New: docker-io-1.5.0 is available
by Red Hat Bugzilla 17 Apr '15

17 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1191438 Bug ID: 1191438 Summary: docker-io-1.5.0 is available Product: Fedora Version: rawhide Component: docker-io Keywords: FutureFeature, Triaged Assignee: lsm5(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Latest upstream release: 1.5.0 Current version/release in Fedora Rawhide: 1.4.1-27.git76baa35.fc22 URL: https://github.com/docker/docker/releases Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Soon this service will be implemented by a new system: https://release-monitoring.org/ It will require to manage monitored projects via a new web interface. Please make yourself familiar with the new system to ease the transition. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1060502] Review Request: golang-github-mitchellh-cli - A library for implementing powerful command-line interfaces in Go
by Red Hat Bugzilla 16 Apr '15

16 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1060502 Jan Chaloupka <jchaloup(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1212318 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1212318 [Bug 1212318] Review Request: golang-github-hashicorp-serf- Service orchestration and management tool http://www.serfdom.io -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159935] "docker events --until" reports the events created even after the specified timestamp
by Red Hat Bugzilla 15 Apr '15

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1159935 --- Comment #7 from smahajan(a)redhat.com <smahajan(a)redhat.com> --- Issue exists on fedora 21 docker. Docker version: Client version: 1.5.0 Client API version: 1.17 but it's fixed in upstream 1.6.0 which will be released this Friday. Shishir -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159935] "docker events --until" reports the events created even after the specified timestamp
by Red Hat Bugzilla 15 Apr '15

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1159935 --- Comment #6 from Daniel Walsh <dwalsh(a)redhat.com> --- Fixed in docker-1.6? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159935] "docker events --until" reports the events created even after the specified timestamp
by Red Hat Bugzilla 15 Apr '15

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1159935 smahajan(a)redhat.com <smahajan(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED --- Comment #5 from smahajan(a)redhat.com <smahajan(a)redhat.com> --- This one is fixed in upstream. After the `--until` timestamp, `docker events` command will die. Changing it to modified. Shishir -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1046717] New: Cancel run or pull operation doesn't actually stop the ongoing task
by Red Hat Bugzilla 15 Apr '15

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1046717 Bug ID: 1046717 Summary: Cancel run or pull operation doesn't actually stop the ongoing task Product: Fedora Version: 20 Component: docker-io Severity: medium Assignee: lsm5(a)redhat.com Reporter: baptiste.millemathias(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: I've downloaded a docker image using "docker pull bradrydzewski/mongodb:2.4" and when I wanted to run it I did a "docker run bradrydzewski/mongodb" as the image name was named like that, and I saw docker pulling another image (the size was different), so I hit Ctrl+C thinking to going kill the operation. However a ps fax showed me dockerd was still downloading something, certainly image bradrydzewski/mongodb Version-Release number of selected component (if applicable): docker-io-0.7.0-14.fc20.x86_64 How reproducible: 100 % Steps to Reproduce: 1. docker pull bradrydzewski/mongodb:2.4 (let the complete operation happens) 2. docker run bradrydzewski/mongodb, and hit ctrl+c after few seconds Actual results: Dockerd still download image Expected results: docker client should ask Dockerd to cancel the download of the image -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1087704] New: repetition of signal 21 with --sig-proxy and SIGSTOP of docker
by Red Hat Bugzilla 15 Apr '15

15 Apr '15

https://bugzilla.redhat.com/show_bug.cgi?id=1087704 Bug ID: 1087704 Summary: repetition of signal 21 with --sig-proxy and SIGSTOP of docker Product: Fedora Version: 20 Component: docker-io Severity: low Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: I noticed weird reaction to SIGSTOP signal. When you start container with --sig-proxy, ignore all signals in container and from OS use kill -SIGSTOP to the `docker run` process, it's put into background. (so far correct behavior) Than when you use kill -SIGCONT, it's resumed (still in background) and it's continuing to send signal 21 to the container (100% CPU utilization). This disappears once you attach the process with fg. Version-Release number of selected component (if applicable): docker-io-0.9.1-1.fc21.x86_64 How reproducible: always Steps to Reproduce: 1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps ax |grep docker 3. kill -SIGSTOP $PID 4. kill -SIGCONT $PID Actual results: [1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' [root@t530 ~]# Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... ... (100% CPU utilization, when you use fg it stops and you can use the container again...) Expected results: [1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' [root@t530 ~]# Received 21, ignoring... Additional info: I'm not definitely sure if this is really required as it's not a common usage. But as there is no way to detach the process apart from kill -SIGSTOP people might use it and get to this problem... -- You are receiving this mail because: You are on the CC list for the bug.

1 13

← Newer
1
...
8
9
10
11
12
13
14
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang April 2015