text:
Remove MaxRSS and MaxVSize from StdBase spec definition

Fixes #8236
Possible replaces #8481
From the discussion with P&R team:
https://github.com/CMSCompOps/WmAgentScripts/issues/248
we might simply remove those 2 parameters from the top level requests (keeping them only at task level). So users won't (be allowed) set these two parameters.
MaxRSS is already automatically set to the Memory value (need to check resized jobs)
MaxVSize is just set to a huge number (1TB), and eventually we might just remove it.

test this please

@ticoann I'm starting the tests only now, however, feel free to leave your first review.
About the VSize, it's likely going to die: https://github.com/dmwm/WMCore/issues/8221
but for now, we just keep it set to a very high number.

Patch looks good to me. We can clean up a little further (removing setMaxRSS, etc) but we can think about it later.

I pushed a few more line changes in the 2nd commit.
It passes all my tests:

Memory during creation of every spec, including ACDC
Memory during assignment of every spec, including ACDC

However, it would be great to have the cleanup also in this PR. Maybe we just skip it for the next month to be on the safe side...
TODO: I still have to make sure that the current production ReqMgr is correctly setting MaxRSS, at least for request creation phase.

I did again all my tests and I couldn't spot any issues, which looks suspicious...
We can discuss it later today whether we add it or not this week.

source: gharchive/pull-request

authors: amaltaro ticoann

repo: dmwm/WMCore

license_type: permissive

license_source: github-api


text:
Owner, where are you?

Hey @dmytrodanylyk - do you need help with this repo? There are bunch of good pull requests waiting and I would prefer some of them are merged to fix bugs and have unified base version.
Let me know if you need help with administration.

Hi, unfortunately I am don't have time to further support this repo. If you want you can clone it and do some fixes / improvements.
If you do so, let me know, I could put link to your version in README.md file.

@dmytrodanylyk It's funny that it also took me so much to respond ;)
I've done some changes to streamline usage of button (theme + gradle). I've submitted pull request:
https://github.com/dmytrodanylyk/android-process-button/pull/58
Instead of linking my repo I would prefer that you add me as contributor to yours... that way I can take care of some pull requests + see if there is anything other contributors want to fix.

source: gharchive/issue

authors: dmytrodanylyk lepipele

repo: dmytrodanylyk/android-process-button

license: mit

license_source: bigquery


text:
start_windows fails to launch

Hi, the install goes as it should but as soon as I use the start file it opens CMD for a second before closing again and not starting anything.

It's most likely this error:
2024-09-19 17:51:51.582 | ERROR    | glados.llama:is_running:173 - Couldn't establish connection after max_connection_attempts=10
Traceback (most recent call last):
  File "T:\AI\GlaDOS\glados.py", line 594, in <module>
    start()
  File "T:\AI\GlaDOS\glados.py", line 573, in start
    llama_server.start()
  File "T:\AI\GlaDOS\glados\llama.py", line 125, in start
    raise ServerStartupError("Failed to startup! Check the error log messages")
glados.llama.ServerStartupError: Failed to startup! Check the error log messages

Try adding PAUSE at the end of start_windows.bat and run again.
so like this:
@echo off
REM Start GLaDOS
call .\venv\Scripts\activate
python glados.py
PAUSE

Traceback (most recent call last):
File "C:\Users\gamem\Desktop\GlaDOS-main\glados.py", line 21, in
from glados import asr, tts, vad
File "C:\Users\gamem\Desktop\GlaDOS-main\glados\asr.py", line 6, in
from . import whisper_cpp_wrapper
File "C:\Users\gamem\Desktop\GlaDOS-main\glados\whisper_cpp_wrapper.py", line 861, in
_libs["whisper"] = load_library("whisper")
^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\gamem\Desktop\GlaDOS-main\glados\whisper_cpp_wrapper.py", line 547, in call
raise ImportError("Could not load %s." % libname)
ImportError: Could not load whisper.
This is the error I get

Did you install using install_windows.bat? (I'm no expert in this, but I'll try to help.)

Yes, I used the install_windows.bat.

Can you confirm that submodules\whisper.cpp folder exists? In glados folder?

Yes. both exist in the folder

Could you remove them and rerun the installer?

I mean this:
echo Downloading Llama...
curl -L "https://github.com/ggerganov/llama.cpp/releases/download/b3266/cudart-llama-bin-win-cu12.2.0-x64.zip" --output "cudart-llama-bin-win-cu12.2.0-x64.zip"
curl -L "https://github.com/ggerganov/llama.cpp/releases/download/b3266/llama-b3266-bin-win-cuda-cu12.2.0-x64.zip" --output "llama-bin-win-cuda-cu12.2.0-x64.zip"
echo Unzipping Llama...
tar -xf cudart-llama-bin-win-cu12.2.0-x64.zip -C submodules\llama.cpp
tar -xf llama-bin-win-cuda-cu12.2.0-x64.zip -C submodules\llama.cpp

echo Downloading Whisper...
curl -L "https://github.com/ggerganov/whisper.cpp/releases/download/v1.6.0/whisper-cublas-12.2.0-bin-x64.zip" --output "whisper-cublas-12.2.0-bin-x64.zip"
echo Unzipping Whisper...
tar -xf whisper-cublas-12.2.0-bin-x64.zip -C submodules\whisper.cpp

Still gives the same error.

IS python 3.12 installed and does it show up like this in cmd?
C:\Users\xxx>python -V
Python 3.12.6   (should be 3.12.x)
and if it doesn't show like this try this command:
C:\Users\xxx>python3.12
Python 3.12.6 (tags/v3.12.6:a4a2d2b, Sep  6 2024, 20:11:23) [MSC v.1940 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

if it works it should be alright. No need to worry about "C:\Users\xxx>python -V"
attempt 2:
run this as a bat file
@echo off

:: Downloading Whisper
echo Downloading Whisper...
curl -L "https://github.com/ggerganov/whisper.cpp/releases/download/v1.6.0/whisper-cublas-12.2.0-bin-x64.zip" --output "whisper-cublas-12.2.0-bin-x64.zip"

:: Creating submodules directory for Whisper
echo Creating submodules directory for Whisper...
mkdir submodules\whisper.cpp

:: Unzipping Whisper using PowerShell with overwrite
echo Unzipping Whisper using PowerShell...
powershell -Command "Expand-Archive -Path 'whisper-cublas-12.2.0-bin-x64.zip' -DestinationPath 'submodules\whisper.cpp' -Force"

:: Cleaning up Whisper zip file
echo Cleaning up...
del whisper-cublas-12.2.0-bin-x64.zip

:: Downloading Llama
echo Downloading Llama...
curl -L "https://github.com/ggerganov/llama.cpp/releases/download/b3266/cudart-llama-bin-win-cu12.2.0-x64.zip" --output "cudart-llama-bin-win-cu12.2.0-x64.zip"
curl -L "https://github.com/ggerganov/llama.cpp/releases/download/b3266/llama-b3266-bin-win-cuda-cu12.2.0-x64.zip" --output "llama-b3266-bin-win-cuda-cu12.2.0-x64.zip"

:: Creating submodules directory for Llama
echo Creating submodules directory for Llama...
mkdir submodules\llama.cpp

:: Unzipping Llama using PowerShell with overwrite
echo Unzipping Llama using PowerShell...
powershell -Command "Expand-Archive -Path 'cudart-llama-bin-win-cu12.2.0-x64.zip' -DestinationPath 'submodules\llama.cpp' -Force"
powershell -Command "Expand-Archive -Path 'llama-b3266-bin-win-cuda-cu12.2.0-x64.zip' -DestinationPath 'submodules\llama.cpp' -Force"

:: Cleaning up Llama zip files
echo Cleaning up...
del cudart-llama-bin-win-cu12.2.0-x64.zip
del llama-b3266-bin-win-cuda-cu12.2.0-x64.zip

echo Done!

if that doesn't work then... I don't know. Maybe the path in the following is wrong?
GlaDOS\glados\whisper_cpp_wrapper.py on line 858
"add_library_search_dirs(['./submodules/whisper.cpp/'])  # add the path to the whisper.cpp submodule

# Begin libraries
_libs["whisper"] = load_library("whisper")"

You could change it to r"C:/Users/gamem/Desktop/GlaDOS-main/submodules/whisper.cpp/" like this.

That's all I can think of... Sorry if it doesn't help.

Traceback (most recent call last):
File "C:\Users\gamem\Desktop\GlaDOS-main\glados.py", line 21, in
from glados import asr, tts, vad
File "C:\Users\gamem\Desktop\GlaDOS-main\glados\asr.py", line 6, in
from . import whisper_cpp_wrapper
File "C:\Users\gamem\Desktop\GlaDOS-main\glados\whisper_cpp_wrapper.py", line 861, in
_libs["whisper"] = load_library("whisper")
^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\gamem\Desktop\GlaDOS-main\glados\whisper_cpp_wrapper.py", line 547, in call
raise ImportError("Could not load %s." % libname)
ImportError: Could not load whisper.
I did the last thing by changing the code and this is the new error I get.

It's the same, no idea. Sorry.

same issue here in win10

This is a huge pain, due to using whisper DLLs and wrappers.
I'm currently refactoring GLaDOS to use Nemo Parakeet,.which has better performance, speed and runs on GPU with less pain.

repo: dnhkng/GlaDOS

license: MIT


text:
Can't run crouton on chromebook, help!

I used to experiment crouton on my Acer Chromebook 14 but since one of the reinstall (in order to reinstall I turn on and off again developer mode) it stop allowing me to enter any crouton system. It starts loading but exits upon loading and gives the following lines:

crosh>

shell
chronos@localhost / $ sudo startunity
Entering /mnt/stateful_partition/crouton/chroots/precise...
Failed to start message bus: Failed to open "/etc/selinux/targeted/contexts/dbus_contexts": No such file or directory
WARNING: starting chroot system dbus daemon failed with code 1
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.42-75-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.18.0-13530-g8bc6aca #1 SMP PREEMPT Wed Feb 22 23:33:57 PST 2017 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3584000 verity payload=PARTUUID=23added6-2217-6740-9fe8-96a57fe44224/PARTNROFF=1 hashtree=PARTUUID=23added6-2217-6740-9fe8-96a57fe44224/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=c695e6f86484b1e052c12dbef107232c4d63f494 salt=79322ef1057cee6e8ec4b60ceb54436be3e26830bd344901475a85823696c559" noinitrd vt.global_cursor_default=0 kern_guid=23added6-2217-6740-9fe8-96a57fe44224 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
Build Date: 12 February 2015  03:37:52PM
xorg-server 2:1.15.1-0ubuntu2~precise5 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Tue Mar 21 19:41:44 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
setversion 1.4 failed: Permission denied
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[intel_init_bufmgr:1069] Error initializing buffer manager.
setversion 1.4 failed: Permission denied
crouton: version 1-20170228132702~master:21cb695b
release: precise
architecture: amd64
xmethod: xorg
targets: unity
host: version 9000.91.0 (Official Build) stable-channel edgar
kernel: Linux localhost 3.18.0-13530-g8bc6aca #1 SMP PREEMPT Wed Feb 22 23:33:57 PST 2017 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Running exit commands...
/usr/bin/xinit: connection to X server lost
waiting for X server to shut down Hangup
(EE) Server terminated successfully (0). Closing log file.
Unmounting /mnt/stateful_partition/crouton/chroots/precise...

Have you tried updating your chroot?
Check out the Update a chroot directions here

as @JoseJX, update your chroot, I have no problems with everything up-to-date Acer 14.

Updating did work. I do feel stupid. Thank you very much :D

authors: Alkata JoseJX liltinkerer

repo: dnschneid/crouton


text:
⚠ Site ANTS has degraded performance

In c4561b1, Site ANTS (https://ants.gouv.fr) experienced degraded performance:

HTTP code: 200
Response time: 15915 ms

Resolved: Site ANTS performance has improved in 827012b.

repo: dnum-mi/stats-sites-api


text:
Remove extra vertical bars in (unnumbered) program listings

The vertical bars | at the beginning of lines in program listings look like leftovers after adding proper CSS to the listings. The bars do not seem to be needed in the generated output, given the ability of CSS to declare content for ::before and ::after pseudo-elements. And in unnumbered listings, the generated bars overlap with the program text, making it ugly. Here is an MWE:
<?xml version="1.0" encoding="UTF-8"?>
<article version="5.1" xmlns="http://docbook.org/ns/docbook">
	<title>Unnumbered programlisting test</title>
	<programlisting linenumbering="unnumbered">class Foo {}</programlisting>
</article>

I suggest removing vertical bars from the generated output for program listings altogether. If some additional separator is still needed for numbered listings, the unconnected vertical bars are better replaced with a single border (which can be customized with CSS if needed).

Are you  using the included CSS files? The CSS provides a proper border and uses display: none; to suppress the text bars. The text bars are there for non-CSS renderings like text browsers.
If you set the $verbatim-number-separator parameter to the empty string, they'll go away.

Indeed, I was using an earlier version, 1.9.0 to be precise. In 1.10.1 there are no vertical bars anymore, thank you.
However, now every line is offset from the beginning by sufficiently large whitespace (reserved for line numbers, I guess). Shouldn't elements span.ln disappear altogether when line numbering is not requested?

I think that's a bug in 1.10.1 that I've fixed. I'm in the middle of a fairly substantial refactor to support enerating EPUB3 files so it's a bit tangled at the moment (both on disk and in between my ears!).
I'm happy if you open another bug for that issue so that we can track it.

authors: kwaxer ndw

repo: docbook/xslTNG


text:
add timestamps to upstart logs and remove color

This request is very similar to what was done with docker with the "--raw-logs" flag in this ticket https://github.com/docker/docker/pull/18621.
When you look at the logs (/var/log/upstart/docker.log) in less you see
ESC[34mINFOESC[0m[305786] containerd: <msg>
ESC[33mWARNESC[0m[305788] containerd: <msg>

The color adds nothing but confusion, and not having timestamps makes debugging difficult.
Version info:
$ docker --version
Docker version 1.12.6, build 78d1802
$ docker-containerd --version
containerd version 0.2.4 commit: 2a5e70cbf65457815ee76b7e5dd2a01292d9eca8
$ docker info
Containers: 9
 Running: 9
 Paused: 0
 Stopped: 0
Images: 10
Server Version: 1.12.6
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 125
 Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host bridge null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options:
Kernel Version: 3.13.0-55-generic
Operating System: Ubuntu precise (12.04.4 LTS)
OSType: linux
Architecture: x86_64
CPUs: 3
Total Memory: 8.782 GiB
Name: <name>
ID: <ID>
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 127.0.0.0/8

Timestamps are already included, I'll add a --raw-log flag

@mlaventure This should be fixed with the logrus fix, no?

@stevvooe would have to check, but I think so

@stevvooe It does, I'll vendor the new version in, thanks

This was resolved with the logrus update.

authors: crosbymichael jdfless mlaventure stevvooe

repo: docker/containerd


text:
Split datakit-github into datakit-github and datakit-bridge-github

datakit-github provides abstraction API for GitHub and doesn't need a lot of
depencencies. This can be used by the CI and by the local bridge without
requiring to depend on ocaml-github at all.
Signed-off-by: Thomas Gazagnaire thomas@gazagnaire.org

All green!

repo: docker/datakit


text:
Fix typo in set-up-dev-env.md

Describe the proposed changes
Change text BIN_DIR to BIND_DIR.

Project version
any

Related issue
none

Related issue or PR in another project
none

Please take a look

To mount the local Docker repository source into the Docker container, the developer needs to set an environment variable called BIND_DIR, not BIN_DIR.

Great catch, thanks @rothrock :)

Glad to help. Thanks for providing this really useful guide.

authors: johndmulhausen rothrock


text:
Update upgrade.md

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Can you give a bit more context into what you're trying to achieve?
Are you adding this note because previous versions of UCP allowed the TLS connection to be downgraded to TLS 1.1, and you want to make sure users know that they can configure UCP to never downgrade the UCP connection?
If that's the case why did you chose to add that information as a note that's part of the upgrade process? Is it because when you upgrade from a previous version, UCP won't use the new default (force TLS connections to a 1.2)?

Ping @lenestopage for a reply, otherwise we'll close this contribution due to inactivity.

I'm closing this one due to inactivity 😢

authors: joaofnfernandes lenestopage


text:
Docker Desktop : Add GDPR related policy regarding how we handle cleaning diagnostics in FAQs.

Please wait for validation by a few Docker Desktop colleagues before merging this.

Who should be added as a reviewer?

@joaofnfernandes can you add @rn & @stephen-turner (I can't add reviewers), thx.
And if you know who might be relevant on the legal side...

LGTM too, apart from the nit Rolf noted.

my bad, obviously the push didn't go through... better now.

authors: gtardif joaofnfernandes stephen-turner


text:
Add a note to env_file option

Proposed changes

Unreleased project version (optional)

Related issues (optional)

I added a follow-on commit to add some clarification. Thanks for your contribution.

authors: dankeder mstanleyjones


text:
API retrieve exact cli command

Hi guys!
I'm having an issue where I'm trying to diff running containers against my configuration. Is there a way to determine Config variables passed via CLI vs. inherited from Dockerfile ... ? My current issue is that there are some ENVs specified in a Dockerfile (over which I have no control or insight) that are not in my configuration, but still show up in the API. And there are no way to determine which ENV came from where. Or is there? :stuck_out_tongue_closed_eyes: I've been using the inspect api.
It would be nice if I could accurately reproduce the cli command used to spawn the container.

You may be able to get what you want by doing a docker inspect on the container to get the base image used.  That inspect should also get you the list of env vars (list 1) that docker put into the container.  From that image name if you do a docker inspect on it you should then able to get the list of env vars from that image (list 2).  Then, I think, the list of env vars specified on the command line should be: list1 - list 2.
Gonna close this if that's ok.  Also, I think I might be more appropriate to use the irc channel or google forum for questions. Github issues are more for bugs, feature request, PRs, etc...

Thanks :+1:

authors: asbjornenge duglin

repo: docker/docker


text:
RHEL 6: Not possible to containerize ANY systemd based image (any docker version)

---- TRIAGE -----
Problem: Systemd is not supported on RHEL6 kernels (and this won't be fixed). As such containers which include systemd will not work.
Resolution: Update docs to reflect issues attempting to run systemd based images on kernels < 3.8
---- END TRIAGE ----
Hi,
this is more a documentation / information related problem:
"Develop, Ship and Run Any Application, Anywhere" NOT true for:

Anywhere = [Redhat | CentOS] 6) AND
Application dependent on systemd

This should be at least mentioned in the install description for RH6.
In our case we realized this only when we wanted to deploy ready, working containerized Apps to production at a customer. Their operations and security departments disallows major Kernel or OS upgrades so we have a real problem - which bit us unexpectedly, due to the claim that the docker enabled series 2 RH kernel is fine.
Description of problem:
Any systemd enabled container can't start on RH 6, with systemd as Pid 1

With --privileged or without
With -e 'container:docker' or without

The root cause is the missing /sys/fs/cgroup interface of the kernel - which can't be created there (sysfs) - allthough all cgroups are actually supported, mounted to /cgroup
I'm clear that docker supports the one container per process approach but for various reasons (many legacy) we require a full init system - and systemd is the default in Linux these days.
docker version:
Tried 1.3.0 and also Docker version 1.6.2, build 7c8fca2
docker info:
[root@ip-172-30-0-24 ~]# docker info
Containers: 19
Images: 11
Storage Driver: devicemapper
Pool Name: docker-202:80-3145731-pool
Pool Blocksize: 65.54 kB
Backing Filesystem: extfs
Data file:
Metadata file:
Data Space Used: 2.375 GB
Data Space Total: 107.4 GB
Data Space Available: 105 GB
Metadata Space Used: 2.879 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.145 GB
Udev Sync Supported: false
Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Kernel Version: 2.6.32-504.el6.x86_64
Operating System:  (containerized)
CPUs: 1
Total Memory: 994.7 MiB
Name: ip-172-30-0-24.eu-west-1.compute.internal
ID: IZBN:IMN5:OGHI:L2LQ:IVB7:RBPC:7KPS:KKSW:ZKZF:SHMD:EPNF:ABXB
uname -a:
Linux ip-172-30-0-24.eu-west-1.compute.internal 2.6.32-504.el6.x86_64 #1 SMP Tue Sep 16 01:56:35 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux
Environment details (AWS, VirtualBox, physical, etc.):
[root@ip-172-30-0-24 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.6 (Santiago)
Reproduced on AWS (ami-9cfd53eb)
On customer site its in vmware server.
How reproducible:
100%
Steps to Reproduce:
We tried various ways. Here the most naive ones:
a) # docker run -ti --privileged -e "container=docker" debian:jessie  /sbin/init
-> Failed to mount tmpfs at /sys/fs/cgroup: No such file or directory
b) # docker run -ti --privileged -e "container=docker" -v '/cgroup:/sys/fs/cgroup' debian:jessie  /sbin/init
-> FATA[0000] Error response from daemon: Cannot start container 3c37ba2028310fcfbe7fa3e8f8f084ecb28670d7b1566e4865d3c9ff0eeca590: [8] System error: mkdir /var/lib/docker/devicemapper/mnt/3c37ba2028310fcfbe7fa3e8f8f084ecb28670d7b1566e4865d3c9ff0eeca590/rootfs/sys/fs/cgroup: no such file or directory
c) # ./docker-1.3.0 run -t -i --privileged --lxc-conf="lxc.mount.auto = proc:rw sys:rw cgroup-full:mixed" -e 'container=docker' debian:jessie  /sbin/init
-> Failed to mount tmpfs at /sys/fs/cgroup: No such file or directory
d) # ./docker-1.3.0 run -it --privileged cloudbees/archbase
-> Failed to mount tmpfs at /sys/fs/cgroup: No such file or directory
e) # ./docker-1.3.0 run -it cloudbees/archbase
-> Failed to mount tmpfs at /run: Operation not permitted
Expected Results:
systemd as pid1 inside (as working with ubuntu as base OS or also when we upgrade the kernel according to http://nareshv.blogspot.com/2014/02/installing-docker-08-version-on-centos.html  (which is not allowed in production))
Additional info:

https://github.com/jpetazzo/dind/issues/17
http://developerblog.redhat.com/2014/05/05/running-systemd-within-docker-container/ (which is only working on RH7)
https://registry.hub.docker.com/u/offlinehacker/nixos/ (does also not work)

In general I want to say that the problem is not a bug in docker as such. Since it is also not possible to get systemd up on RH6 using lxc.
But it should be made very clear to users of dockers that their containers can't work on default RH 6 - if systemd is used as init system inside.
PS: If there is any workaround whatsoever (dind?) I would be very happy if I'm proven wrong with the main claim of this issue.

Here a definite confirmation from Lennart:
https://bugs.freedesktop.org/show_bug.cgi?id=90517
=> You might really want to provide this information in your install notes for Red Hat, Cent Os 6 type OSes. Since it will save users a lot of time finding out the hard way :-/

Thanks! I updated the issue to reflect what needs to be done

#dibs

Docs now state only v7 is supported.  Suggest closing this issue.

@mikebrow thanks, yes, I think this can be closed now that we no longer have RHEL/CentOS 6 in the list of supported versions

@mikebrow thanks also from here. Sorry was pretty much for quite some time.

authors: AXGKl cpuguy83 mikebrow thaJeztah


text:
docker [1.7.0] ps output breaks certain compatibility

In some dokku plugins (ex: https://github.com/Kloadut/dokku-pg-plugin/blob/35edfebd9bc4eafcdf9f3ecfc32cef3404853b9b/commands#L42) the image tag was used to identify a particulr running container.
Why drop this from the output and is there a way to gain it back (with arguments perhaps?)
related: https://github.com/progrium/dokku/issues/1263

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

This was most likely unintentional.

oh I recall this

I see. This just seems like a weird thing to change. Please correct me if I'm wrong but the net result is if you exec docker run myimage:tag, docker ps will show the tag but if you run docker run myimage, you get no tag? Why change the output when you're still actually running the latest tag in the latter case?

Any suggestions on what to do here?

Tentatively closing as the issue seems to be resolved by #12918: please let me know if it needs reopening! Thanks.

authors: GordonTheTurtle cpuguy83 icecrime michaelshobbs runcom


text:
Categories Docker images for industry trends

I have an idea. There are millions of Docker images in Docker hub. Say, I come from storage background and want to know what Docker images are available for storage industry. Same case could be if I am working for hardware industry I would be interested to know what system management tools are available. The only option I have is browsing through the tools one after another and that might consume time once Docker repo gets large and large. Why not classify it in terms of industry trends(say, server, cloud, networking, storage, system management, big data, hadoop etc.) so that user can quickly know what containers are present for respective point of interest.
I am not sure if this is the right place but yes, do redirect this thread accordingly.
Thank You.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Sounds like a good idea. Here are my 2 cents: Instead of categorizing based on industry, why not do it based on App ecosystem. I mean, that's the basic stuff we are trying to do, right? Making apps deployment easier. So,  as you said we can categorize them accordingly like cloud apps images, storage apps images, infrastructure apps etc. Let me know what you think about that.

Hi Peeyush,
Thanks.You have put it in the right way. I agree with your views.
Ajeet
On 4 Aug 2015 10:17, "Peeyush gupta" notifications@github.com wrote:

Sounds like a good idea. Here are my 2 cents: Instead of categorizing
based on industry, why not do it based on App ecosystem. I mean, that's the
basic stuff we are trying to do, right? Making apps deployment easier. So,
as you said we can categorize them accordingly like cloud apps images,
storage apps images, infrastructure apps etc. Let me know what you think
about that.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/15280#issuecomment-127477476.

Thanks for creating this proposal @ajeetraina, however, issues and feature requests regarding Docker Hub are not handled in this repository (it's managed by a different team). Usually, you'll have to report those via https://support.docker.com, however, because Docker Hub has just gotten a makeover, you could try opening a feature request in this repo; https://github.com/docker/hub-beta-feedback
I'm going to close this issue here, because there's nothing the maintainer here can do about this, but feel free to comment here after closing

authors: GordonTheTurtle Pensu ajeetraina thaJeztah


text:
Cannot remove container stopped while in "Restarting"

Output of docker version:
Client:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:34:23 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:34:23 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 269
 Running: 13
 Paused: 0
 Stopped: 256
Images: 2994
Server Version: 1.11.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 3553
 Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: overlay bridge null host
Kernel Version: 3.13.0-85-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.36 GiB
Name: xxxxxxxx
ID: xxx.xxx.xxx.xxx
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
Cluster store: consul://xxx.xxx.xxx.xxx:8500
Cluster advertise: xxx.xxx.xxx.xxx:2376

Additional environment details (AWS, VirtualBox, physical, etc.):
Physical box
Steps to reproduce the issue:
Create a container with restart policy 'unless-stopped':
docker run -d --name restartbug --restart unless-stopped busybox /bin/true
checking the status I get:
748270c68181  busybox  "/bin/true"  25 seconds ago   Restarting (0) 10 seconds ago   restartbug
After stopping it with docker stop restartbug:
`748270c68181  busybox  "/bin/true" 57 seconds ago    Exited (0) 19 seconds ago   restartbug`

Describe the results you received:
Trying now to remove the container:
$ docker rm restartbug
Error response from daemon: Driver aufs failed to remove root filesystem
748270c68181ca10d178efc89ad56bc6f54bf4129d652104f5d37faea0ad4a50: rename
/var/lib/docker/aufs/diff/d20b5c2ac56e67f44a4b7771efc31d14d892bd2459a041561593f0af14d4ed5b
/var/lib/docker/aufs/diff/d20b5c2ac56e67f44a4b7771efc31d14d892bd2459a041561593f0af14d4ed5b-removing:
device or resource busy

and the status of the containers is then:
 `748270c68181  busybox  "/bin/true"   About a minute ago    Dead                 restartbug`

Describe the results you expected:
Being able to remove the container.
Additional information you deem important (e.g. issue happens only occasionally):
We have tried changing the restart-policy to no and it was working.
We also tried with on-failure:

docker run -d --name restartbug2 --restart on-failure busybox /bin/false
docker run -d --name restartbug3 --restart on-failure:1024 busybox /bin/false
docker run -d --name restartbug4 --restart on-failure:1 busybox /bin/false

In the first 2 cases we issued the stop while in Restarting and we faced the same issue on the rm.
In the third case we waited for the container being in Exit(1) before removing the container, and in this
case it was successful.

As additional information, and workaround if one realise the issue before doing the rm, executing:
docker update --restart no restartbug5
while in Restart allow then to stop (if required) and then remove the container without the problem.

Confirmed hit that in master
Error response from daemon: Driver aufs failed to remove root filesystem 338b4ce0795f23da480056a8a6f010b41d48ef19c6111c35c59a803a062b5ca5: rename /var/lib/docker/aufs/diff/873b83c3d539130763caa5e92a6c360cd37ff755f015568a929048e4b1f1e5ca /var/lib/docker/aufs/diff/873b83c3d539130763caa5e92a6c360cd37ff755f015568a929048e4b1f1e5ca-removing: device or resource busy

but after docker rm -f <container id>, the container gone

@HackToday, right, with rm -f you still get the error but the container is then removed. Thanks.

@Teudimundo do you have any running containerd mounting  /var/run? If so, it could be the same as #21969

nope, no container is mounting /var/run.

@Teudimundo /var/lib/dockerthen?
I still can't find a way to reproduce this issue otherwise, I did come upon the issue that @tonistiigi #22237 PR is fixing but that's it.
I'll mark this as P3 until we have a dev that can reliably reproduce it for debugging.

It easy to reproduce with Python 3.5 container :
docker run -d --name=test_name --restart=always python:3.5 python -c 'import badmodule'
docker stop test_name
docker rm test_name #fails with  error ' Driver aufs failed to remove root filesystem.... device or resource busy'
docker rm -f test_name #the same message, but container actually was removed

@AleksandrIakhnev would you be able to test docker 1.11.1-rc1? I think this issue should be resolved, but if you are able to test it, that would be great! (note, it's a release candidate, so shouldn't be used in production) https://github.com/docker/docker/releases/tag/v1.11.1-rc1

@thaJeztah Thanks for the anwer, I will try.

@thaJeztah On  1.11.1-rc1  container can be removed without force flag and warnings, issue is fixed.

@AleksandrIakhnev thanks so much! Good to hear it's resolved indeed; 1.11.1 GA should be released soon

authors: AleksandrIakhnev HackToday Teudimundo mlaventure thaJeztah


text:
docker containers' stats through UNIX socket not showing

Output of docker version:
Client:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4a6e2b1
 Built:
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4a6e2b1
 Built:
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 5
 Running: 5
 Paused: 0
 Stopped: 0
Images: 2
Server Version: 1.11.2
Storage Driver: overlay
 Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.7.0-coreos
Operating System: CoreOS 1122.1.0 (MoreOS)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.801 GiB
Name: localhost
ID: Z6DG:PZYS:QGVO:XSD4:QE6I:MGPX:KZJ2:2T5S:A2R3:Z5I3:Y6BL:JNE2
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/

Additional environment details (AWS, VirtualBox, physical, etc.):
The docker host is a VMware VM.
Steps to reproduce the issue:

Start a container and mount /var/run/docker.sock
Query for: echo -ne "GET /containers/$CONTAINERID/stats HTTP/1.1\r\n\r\n" | ncat -U /var/run/docker.sock (with root privileges)

Describe the results you received:
For any container that I query (including the one where I run the above mentioned cmd from), I get the following HTTP response
HTTP/1.1 200 OK
Server: Docker/1.11.2 (linux)
Date: Wed, 24 Aug 2016 15:40:54 GMT
Content-Type: text/plain; charset=utf-8
Transfer-Encoding: chunked
0
Describe the results you expected:
With docker version 1.6.x, seems like the API call over UNIX socket returns the JSON output of CPU/MEM usage. But not with vers > 1.6
Additional information you deem important (e.g. issue happens only occasionally):

It's because of the chunked transfer encoding.
Netcat is getting a response immediately.
Try using curl instead.


text:
get the service details that  the starting task belongs to -  from within the task

I couldn't find any documentation about all dns records that can be queried from inside a container so posting my case hoping for a simple solution
trying to improve the percona cluster image
every starting task needs to know the ip addresses of all existing task in a healthy state and its own ip address for the sync linking
--wsrep_cluster_address="gcomm://$joinNodes" --wsrep_node_address="$myIp"
my idea is that each starting task queries the dns get this information (form within the task itself)
dig $(hostname)
to get some info about the service name this task belongs to ($serviceName) and the ip address of the network the tasks is attached to ($myIp)
then using the service name I can $joinNodes=dig tasks.$serviceName to get all other running tasks
one way I managed solve the issue is bind mounting the docker.sock and
getting all info from there using curl and parsing the json using jq,
but using dns would be a lot cleaner so hoping for some bright ideas :)
percona/percona-docker@105a4b4#diff-2ccb91d8e101f4269c720edffee04bdd

I found this PR #26331 which is exactly what I need so closing this

I think you should be able to work around this for now, by passing the service name to the container as an environment variable, so that it can be used for the dig tasks.<servicename> lookup
@mavenugo do you think we need a "special" way to look up tasks for the same service that the task is part of? dig tasks.<some-special-name>

@krasi-georgiev let me reopen this issue for a bit; while an introspection API can certainly be used for this, it may also be a "heavy weight" solution for service discovery

authors: krasi-georgiev thaJeztah


text:
statsCollector: fix data race in run()

statsCollector.publishers must be protected to prevent modifications during the iteration in run().
Being locked for a long time is bad, so pairs of containers &publishers (pointers) are copied to release the lock fast. However, it gives an extra pressure to GC.

does this fix a specific issue? just so we can be sure we close it after

@jfrazelle Sorry, I forgot about an issue. Here it is #12717

Seems, I mad a stupid mistake. I'm gonna fix it :D

Hmm, I launched make all and test-integration-cli passed:
DockerSuite.TestDiffFilenameShownInOutput                   0.93
DockerSuite.TestEventsContainerEvents                       1.14
DockerSuite.TestEventsContainerEventsSinceUnixEpoch         1.03
DockerSuite.TestEventsContainerFailStartDie                 1.23
DockerSuite.TestEventsFilterContainer                       2.24
DockerSuite.TestEventsFilterImageName                       1.69
DockerSuite.TestEventsFilters                               2.00

But I did on Mac. Could you help me (or give a hint how) to reproduce this windows error, please?

im rebuilding, could have been a fluke

I think it is possible to rewrite it with channels for more graceful synchronization. But for now this is cool fix.

@noxiouz Can you squash commits before merge pls?

@LK4D4 Done. Thanks for review. I'm gonna think how to rewrite this part. By the way, there is a similar part in Swarm.

Oh, I don't understand.

Happens sometimes :)

LGTM

LGTM

authors: LK4D4 jfrazelle noxiouz


text:
Scaling out a single group viamanager group commit updates every group

We have a group definition with a managers and a workers group. We want to scale out the workers group and issued the following after updating the Allocation|Size from 1->2:
Group workers with plugin group plan: Adding 1 instances to increase the group size to 2
Group managers with plugin group plan: Performing a rolling update on 3 instances

In this case we did not want to perform a rolling update on any of the managers; we only wanted to scale out the workers.
Is there a different command we should use to only update a specific group? Or can this flow be updated to detect that nothing changed in the managers group and not do a rolling update?
It seems like we need a way to differentiate between performing a rolling update and a scale out (where only the allocations changed).
Thanks!

Can you add the groups.json that you used?

Note that if I run a second commit right after the first I see:
Group workers with plugin group plan: Noop
Group managers with plugin group plan: Performing a rolling update on 3 instances

The problem is that quorum groups DO NOT check for instance definition changes (only checks LogicalID):
https://github.com/docker/infrakit/blob/master/pkg/plugin/group/quorum.go#L37-L39
Scaler groups DO check this:
https://github.com/docker/infrakit/blob/master/pkg/plugin/group/scaler.go#L60-L67
The fix is to add a similar check to the quorum group PlanUpdate function.

authors: chungers kaufers

repo: docker/infrakit


text:
the 'before' tag to images

Before redeploying the stack, the vote and result services in the file docker-stack.yml are tagged with the before and in the docker stack services shows the latest tag. And, initially, the tags are before so renaming those tags.
Thank you.

ok，I see. thank you!

repo: docker/labs


text:
Add id/gid option to mount when using vmhgfs

Follow up of #1394
Signed-off-by: Fabio Rapposelli fabio@vmware.com

LGTM

LGTM

authors: dgageot frapposelli jeanlaurent

repo: docker/machine


text:
Generalize server keys

Unfortunately the database is still called "timestamp_keys" and I'm not sure how to fix that cleanly. Everything else has been generalized though so that one piece of ugly legacy hangover is highly contained to the database migration files, and the Key.TableName method.

@endophage I think MySQL supports atomic renaming of tables:  https://dev.mysql.com/doc/refman/5.7/en/rename-table.html
So we can add a migration for that, if you like.

A couple more test cases involving the same gun with a different role would be awesome (maybe even inserting the same key for multiple roles?)

@cyli I figured I'd add those tests as part of the actual snapshot management stuff so they're coming, just in a different PR.
As far as renaming the table, it's definitely possible, it's just impossible to synchronize with a code push, and even more scary, if something goes wrong and we say, have to restore the DB from a backup, we've suddenly caused a significant outage.

@endophage Oh I meant specifically tests for the storage driver that tests the unique key comprising the gun and role.  (e.g. that same role but different gun and vice versa can be successfully added to the DB, but the same gun and same role, even if the keys are different, cannot be added to the DB).
Also, similar DB changes should probably be added to either notarymysql initial.sql or migrate.sql, else notarymysql will be in a broken state after this PR - I know that we were going to fix our mysql stuff anyway, I just wasn't sure whether it's ok to leave it broken in the meantime?

@cyli last 2 commits update migrate.sql and add tests respectively.

Other than the above nitpick, LGTM!

@cyli good call on that test update. I think gorm may not set up multicolumn unique indexes properly... (possibly just in sqlite). It wasn't erroring when I tried to insert a duplicate gun+role but a different key/algorithm. Small code update along with test fix in the last commit.

authors: cyli endophage

repo: docker/notary


text:
Fix access controller resource type

The token server returns tokens with the type as "repository" not "repo".
Example token body
{
  "access": [
    {
      "type": "repository",
      "name": "dmcgowan/busysleep2",
      "actions": [
        "pull",
        "push"
      ]
    }
  ],
  "aud": "notary.docker.io",
  "exp": 1436827486,
  "iat": 1436827186,
  "iss": "auth.docker.io",
  "jti": "7n6E3t3-EdKg1D_Cgbg0",
  "nbf": 1436827186,
  "sub": "dmcgowan"
}

LGTM (looks like I misread a line in distribution when I was adding the integration)

authors: dmcgowan endophage


text:
Do not install go vet on the Dockerfile

Not sure what changed, but looks like go vet just comes with the image now and also osxcross breaks unless pinned to a commit.  Copied the OSX cross stuff from docker/docker Dockerfile.
Also bumped the min OSX version to 10.9.

I'll leave it to you to work out if godep is required, otherwise LGTM.

LGTM

authors: cyli endophage riyazdf


text:
use --cpu-shares instead of -c in integration test

Running integration test locally ran into such case:
# Warning: '-c' is deprecated, it will be replaced by '--cpu-shares' soon. See usage.

This pr did:

use --cpu-shares instead of -c in integration test

While --cpu-shares is always usable in each version of docker daemon.
In docker version of docker 1.11.0, no -c in docker run usage:
root@10-11-1-156:~# docker run --help
Usage:	docker run [OPTIONS] IMAGE [COMMAND] [ARG...]
Run a command in a new container
  -a, --attach=[]                 Attach to STDIN, STDOUT or STDERR
  --add-host=[]                   Add a custom host-to-IP mapping (host:ip)
  --blkio-weight                  Block IO (relative weight), between 10 and 1000
  --blkio-weight-device=[]        Block IO weight (relative device weight)
  --cpu-shares                    CPU shares (relative weight)

Signed-off-by: Sun Hongliang allen.sun@daocloud.io

Good idea. LGTM.

LGTM

authors: MHBauer allencloud nishanttotla

repo: docker/swarm


text:
Use gometalinter; switch from x/net/context -> context

This PR contains a few related changes. The following is a copy-paste from commit messages. Hope it makes sense.
I. Makefile: use gometalinter
Instead of running many small source code checkers and linters one by
one, let's use gometalinter that runs them all in parallel.
While at it, remove the individual make targets (fmt, vet, lint,
ineffassign, and misspell) and replace with a single check target.
One thing it provides is faster source validation.
BEFORE:
real    0m24.025s
user    1m2.646s
sys     0m3.860s

(note these timings are without building binaries, which
for some reason was a dependency of the vet target)
AFTER:
real    0m6.330s
user    0m20.255s
sys     0m1.019s

In addition to this, it is now way easier to add/remove the checks,
as well as to filter out some errors from linters that we consider
false positives.
II. Switch from x/net/context -> context

Since Go 1.7, context is a standard package. Since Go 1.9, everything
that is provided by "x/net/context" is a couple of type aliases to
types in "context".

While at it, fix the order of imports (done by goimports and some shell
trickery, see below).

Also, when the standard context package is used, the errors of
not calling cancel() are detected/reported by go vet:

the cancel function returned by context.WithTimeout should be called,
not discarded, to avoid a context leak (vet)

This essentially asks to call cancel() as otherwise a stray timer
is leaked. Fix a few such issues, mostly in _test.go files.

Since in func (*session).start (see agent/session.go) we deliberately
do not want to cancel the context, govet gives us a couple of errors:

agent/session.go:140: the cancelSession function is not used
on all paths (possible context leak)
agent/session.go:163: this return statement may be reached
without using the cancelSession var defined on line 140

To silence these, use // nolint: vet mark in a couple of places
(this is a feature of gometalinter).
Oh, the conversion (items 1 and 2 above) was performed by this
shell script:
FILES=$*
test -z "$FILES" && FILES=$(git ls-files \*.go | grep -v ^vendor/ | grep -v .pb.go$)

for f in $FILES; do
        sed -i 's|"golang.org/x/net/context"|"context"|' $f
        goimports -w $f
        for i in 1 2; do
                awk '/^$/ {e=1; next;}
                        /\t"context"$/ {e=0;}
                        {if (e) {print ""; e=0}; print;}' < $f > $f.new && mv $f.new $f
                goimports -w $f
        done
        echo -n .
done
echo

Multiple goimports calls and some awk trickery is needed to iron out
incorrect formatting (excessive empty lines) from the import statements.
III. Add some more linters and fix warnings reported by those
Those are:

deadcode
goimports
unconvert
gosimple

For the warnings reported and fixed, please see individual commit messages.

Please note patches 3 to 5 are optional -- please let me know if you want them to either be removed or separated out to another PR.

@dperny PTAL

Similar PRs:

https://github.com/docker/libnetwork/pull/2140
https://github.com/containerd/containerd/pull/2305
https://github.com/moby/moby/pull/36904
https://github.com/docker/cli/pull/1038
https://github.com/containerd/continuity/pull/133

Rebased; merge conflicts (due to PR #2748) resolved.
@thaJeztah @yongtang PTAL

I realize this looks messy like there are two independent features in one PR. Let me explain.
The first patch (introducing gometalinter) is needed to use gometalinter's functionality of silencing some selected warnings (ones we are sure are bogus).
The second patch (switch to standard context package) reveals some warnings about leaked contexts that the code fails to cancel(). Some of them are fixed in the patch, some are silenced as we are quite sure we do not want to cancel those contexts.
The rest of the series is more linters for gometalinter.
Now, if this is too much to digest at once, I can split this into two, three, or more PRs:

Use gometalinter.
Switch to standard context pkg.
Add more linters.

PRs 2 and 3 would depend on 1.
Please let me know how to proceed.

CI failure:

protoc --decode google.protobuf.FileDescriptorSet /usr/local/include/google/protobuf/descriptor.proto
/usr/local/include/google/protobuf/descriptor.proto: File does not reside within any path specified using --proto_path (or -I).  You must specify a --proto_path which encompasses this file.  Note that the proto_path must be an exact prefix of the .proto file names -- protoc is too dumb to figure out when two paths (e.g. absolute and relative) are equivalent (it's harder than you think).

Mea culpa. It's because of https://github.com/stevvooe/protobuild/pull/20; let me try to fix it

Fix is submitted (https://github.com/stevvooe/protobuild/pull/21) but not yet merged.

alright, ship it.

authors: dperny kolyshkin

repo: docker/swarmkit


text:
Feature/update macos quickstart

Description
Update Dockstore CLI install instructions, with an emphasis on updating the Mac OS instructions. Notably, we now correctly tell Mac users to use Java 17 instead of 11.
What's been tested

The Ubuntu instructions, because I only reformatted them, not changing any actual content
The "option B" instructions for Mac on an Intel-hardware Mac
Any new zsh alternatives to bash stuff

What has not been tested

The "option A" instructions for Mac, although I did fix the name of the file paths
The "option B" instructions for Mac on an Apple Silicon Mac -- this post from Ben implies option B might not work on Apple Silicon, but maybe the cask has been updated since then?

Specific feedback request
I listed some use cases for the Dockstore CLI after step 5, but I don't know if I "sold" it very well. Any thoughts?
Issues

https://github.com/dockstore/dockstore-ui2/pull/1814 -- old PR that got borked after a rebase 😬
https://github.com/dockstore/dockstore/issues/4486

Security
N/A
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that your code compiles by running npm run build
[ ] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket. (Need feedback on this one!)
[x] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[x] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[x] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[x] Do not use cookies, although this may change in the future
[x] Run npm audit and ensure you are not introducing new vulnerabilities
[x] Do due diligence on new 3rd party libraries, checking for CVEs
[x] Don't allow user-uploaded images to be served from the Dockstore domain
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.
[x] Check whether this PR disables tests. If it legitimately needs to disable a test, create a new ticket to re-enable it in a specific milestone.

As mentioned in the previous PR, since this is an external fork, these commits might need to be cherrypicked to an internal branch to get the tests to pass.
I've made sure this compiles, but I'm not sure how/if I can authenticate locally so I can see the onboarding page, so this is a bit of a blind change. 🙈 Would appreciate someone screenshotting the resulting markdown so I can ensure our flavor of markdown renders the ##### I've introduced distinctly from ####.

Build issues are probably due to this being a fork (and then branch) rather than a branch inside the ui2 repo.
Overall though, probably need someone on Mac to review

More notes about Apple Silicon compatibility:

As I see it, the problem isn’t with miniwdl (or cromwell) but with running a WDL that uses x86 containers on an ARM mac. Where miniwdl or cromwell comes into play is in how the WDL runtime loads the docker container that your WDL needs to run. Given that ARM macs can run x86 executables via software emulation, there should be a way to make docker (and then miniwdl/cromwell) run x86 containers on ARM macs. Or if you had docker containers that support ARM natively, that would also work.
-- Phil Shapiro, OpenWDL Slack, r/e https://github.com/chanzuckerberg/miniwdl/issues/652

Other notes from that discussion:

Try using Docker parameter --platform=linux/amd64
Try setting an env variable: export DOCKER_DEFAULT_PLATFORM=linux/amd64
The actual Cromwell JAR works on Apple Silicon, and miniwdl likely does to (troublesome Docker images notwithstanding)

Checking in on this as part of https://ucsc-cgl.atlassian.net/browse/SEAB-6003
@coverbeck or @svonworl can someone mac-based take over this and get it over the line?

Although I'm using a different machine now, I'm still using Intel hardware, so I can't test the Apple Silicon stuff. Recommend whichever reviewer has Apple Silicon hardware checks that a workflow running an x86 Docker image actually goes through.
See also:

From 2020: https://www.macrumors.com/2020/06/23/rosetta-wont-support-x86-virtualization-windows/
From 2022: https://www.ginkgobioworks.com/2022/07/19/using-docker-on-apple-silicon/
From 2023: https://yalamati.medium.com/docker-without-docker-desktop-mac-m1-eb7016082492

I haven't seen issues running x86 Docker images from people running Linux on other ARM architecture; I think this is mostly a Mac issue.
Also worth keeping in mind that although the heavy hitters of Docker Hub tend to build multi-arch images, most bioinformatics Dockers images seem to be solely available in x86.

Closing in favor of #1964, which is based off of this, but whose branch is in this repo which allows somebody other than Ash to respond to PR comments.

authors: aofarrel coverbeck denis-yuen


text:
and, or doesn't work in DQL

I migrate a mysql db to sqlAnywhere(sqla) to test my app developed with Doctrine2.
Acces to sqla works,
DQL like
$query = $em->createQuery('SELECT e FROM countries e WHERE e.conlng = :lng );
$query->setParameters(array(
'lng' => 'DE'
));
$result = $query->getResult();
also runs funny.
$query = $em->createQuery('SELECT e FROM countries e WHERE e.connum = :num );
$query->setParameters(array(
'num' => '4'
));
$result = $query->getResult();
also no problems!
BUT!
$query = $em->createQuery('SELECT e FROM countries e WHERE e.conlng = :lng AND e.connum = :num');
$query->setParameters(array(
'lng' => 'DE',
'num' => '4',
));
$result = $query->getResult();
doesn't work!!
$result = empty!
with operator OR it's the same problem!
Any idea!

Interactive sql works!

But if i change my test-pgm to this ..

look at the sql statement!
SELECT e FROM countries e WHERE e.conlng = :lng  or e.connum = :num
and the result in the sceenshot.
It woorks with an OR operator??!
I'm very irritated !

SELECT e FROM countries e WHERE e.conlng = :lng or e.connum = :num

Is this the same SQL statement that the ORM runs?
Use a DebugStack logger to see if the SQL statement is the same.
The one difference I noticed is that sometimes your parameters are string, sometimes int: try looking for differences there as well as in the executed SQL string.

I'm very irritated !

This is not a support hotline: if you need to get irritated over volunteers helping you out, you can instead hire somebody to help you out, and be (contractually) allowed to be irritated instead.

@winnilein can you expand on params and types there?

Both are bound as string there - can you try passing in an integer and running the SQL statement manually with either string or int, and see if there is a difference?

native sql..

and the result of my script..

my script..
<?php
include "Bootstrap.php";
require_once 'Entities/countries.php';
error_reporting(E_ALL);

$stack = new \Doctrine\DBAL\Logging\DebugStack();
$stack->enabled;
$em->getConfiguration()->setSQLLogger($stack);

$query = $em->createQuery('SELECT e FROM countries e WHERE e.conlng = :lng AND e.connum = :num');

$LNG = 'DE';
$NUM = 4;

  $query->setParameters(array(
    'lng' => $LNG,
    'num' => $NUM,
            ));

$result = $query->getResult();

            if (!$result) {

                echo 'Noting found!';

            } else {

                foreach ($result as $row) {
                    $TXT=$row->getContxt();
                    echo $TXT;
                }

            }

      echo '<pre>';
\Doctrine\Common\Util\Debug::dump($stack, 5);

For your entertainmant..
$query = $em->createQuery('SELECT e FROM countries e WHERE e.conlng = :lng AND e.connum = :num');
$NUM = 4;
result ->

and now !
$query = $em->createQuery('SELECT e FROM countries e WHERE e.conlng = :lng or e.connum = :num');

$NUM = '4';

result..

f****** web apps
i think i continue programming midrange applications

Closing: nobody's spare time is worth following up on this attitude.
If you don't have the willpower to contribute to this conversation in a constructive way, then please consider hiring somebody doing it for you instead.

authors: Ocramius winnilein


text:
Add sidebar.rst and cleanup docs homepage.

This depends on https://github.com/doctrine/doctrine-website/pull/88

LGTM, waiting for website change to be merged

authors: jwage malarzm

repo: doctrine/mongodb-odm


text:
Required Rule don't get updated properly

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
After setting the required prop of i.a. a TextfieldElement from true to false, the required rule will still be active.
This is due to the rules of RHF register.
Currently the rules object will change from
// required
{
  required: "This field is required"
}

to
// not required
{}

instead it has to be changed to
// not required
{
  required: false
}

Expected behavior 🤔
After setting the required prop to false it should deactivate the required rule properly.
Steps to reproduce 🕹
https://codesandbox.io/s/young-river-fqo0hs?file=/src/App.tsx
Steps:

Uncheck the required checkbox
click submit

@TobiasKrahn your codesandbox does not show any react-hook-form-mui related components. You see this error on every component or on any specific one?

@TobiasKrahn thanks for your demo. Looking at the code https://github.com/dohomi/react-hook-form-mui/blob/master/packages/rhf-mui/src/TextFieldElement.tsx#L52 seems the default is an empty object which actually works for almost all use cases (I use the lib in many prod environment and never stumbled accrossit).
You can provide also a validation object instead of setting required, I tried it like this but it seems to not work either:
https://codesandbox.io/s/silly-cartwright-g9ygq9?file=/src/App.tsx
Strange to be honest, maybe I have to unset the empty {} but not sure right now.

Thats what I did here: https://codesandbox.io/s/silly-cartwright-g9ygq9?file=/src/App.tsx:1286-1322
still doesnt seem to be right

Yes you are right, this would be a valid workaround, but I would suggest to change the addition of the required rule at https://github.com/dohomi/react-hook-form-mui/blob/master/packages/rhf-mui/src/TextFieldElement.tsx#L35
from
if (required && !validation.required) {
  validation.required = 'This field is required'
}

to something like this
validation.required ??= !!required && 'This field is required'

to prevent other users to fall into this trap.

@TobiasKrahn the required prop shortcut is really only useful if users are happy with only english translation and want to be fast and simple. It mainly just appends the "*" asterix symbol behind the label and has a simple english translation.
The recommended API is the use of validationprop as its just an alias for rules. As soon you use i18n you have to use it to translate your error messages.
Feel free to open a PR I can revisit it soon, currently I am bombed with other things at work.

authors: TobiasKrahn dohomi

repo: dohomi/react-hook-form-mui


text:
3DMark06 crash

Please describe your issue as accurately as possible. If you run into a problem with a binary release, make sure to test with latest master as well.
So I've installed dxvk using winetricks and tried to lunch some games and benchmarks. However, the game tried to load for a while then crashed. Launching with command line show a continuous non-stop spamming of OpenVR error
Software information
Name of the game, settings used etc.
Literally every DirectX game or benchmark
System information

GPU: intel UHD Graphics 620
Driver: i915
Wine version: wine-6.22 (Staging)
DXVK version: v1.9.2-53-g804eca9c

Log files
All the log files that generated (d3d9, dxgi) only contain a continuous spamming of:
info:  Game: 3DMark06.exe
info:  DXVK: v1.9.2-53-g804eca9c
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
info:    OpenXR
info:  OpenVR: could not open registry key, status 2
info:  OpenVR: Failed to locate module

This is not a bug and is 100% expected when not running in a VR environment. What is your issue exactly?

I have the same issue.
Opensuse 15.2
5.3.18-lp152.106-preempt
dxvk 1.9.2
wine 7.0rc1
Logs:
info:  Game: Hades.exe
info:  DXVK: v1.9.2
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
info:    OpenXR
info:  OpenVR: could not open registry key, status 2
info:  OpenVR: Failed to locate module
0100:err:virtual:virtual_setup_exception stack overflow 1936 bytes in thread 0100 addr 0x7fab6d2ec5ca stack 0x20870 (0x20000-0x21000-0x120000)
Hades, Frostpunk, etc... Almost every dx10 or dx11 games have starting loop with the same errors.

info:  Game: Machinarium.exe
info:  DXVK: v1.9.2
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
info:    OpenXR
info:  OpenVR: could not open registry key, status 2
info:  OpenVR: Failed to locate module
info:  Required Vulkan extension VK_KHR_surface not supported
terminate called after throwing an instance of 'dxvk::DxvkError'

abnormal program termination

(app closes)

Same but app is uncloseable normally, I need to kill the processes. It repeat this message endlessly

@rayrapetyan This has nothing to do with the issue. Your problem is that your graphics driver isnt installed correctly. Make sure you also have the 32bit version installed.

When starting steam with dxvk it spams this message so much that it actually slows steam down and makes my computer fan go wilder than it should. It also seems to be preventing steam's chromium from initializing due to timeouts. Is there a way to disable this from being logged? Specially since, as you say, there is no problem at all.

I have the same infinite loop with Vortex under Wine 7.0rc:
info:  Game: Vortex.exe
info:  DXVK: v1.9.2
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
info:    OpenXR
info:  OpenVR: could not open registry key, status 2
info:  OpenVR: Failed to locate module
info:  Game: Vortex.exe
info:  DXVK: v1.9.2
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
info:    OpenXR
info:  OpenVR: could not open registry key, status 2
info:  OpenVR: Failed to locate module
…

Vortex is the only app I experience this particular issue with.
I'm sure it has nothing to do with OpenVR though.

I met the issue: 1) i used the release dxvk-1.9.4, it can work well; 2) i following the build instruction, and use the build library, success build. But when i use the library which i build by myself, the app crash reported "OpenVR could not open registry key, status 2". what should i do to check this problem?
Environment:
Ubuntu 20.04
Meson: 0.61.2
mingw64: 8.0.0

I am also having this issue as well, though after installing 4 things from winetricks, rather than it simply happening suddenly.

Solved by following https://github.com/doitsujin/dxvk/issues/1986 and removing dxgi via winecfg. Sorry for the annoyance.

Solved by following #1986 and removing dxgi via winecfg. Sorry for the annoyance.

hi can you please explain exactly what did you do to solve it? Thanks in advance!

in winecfg, go to the libraries tab, search for a dxgi library, and then try to delete it. it might not work for everyone and im not sure why exactly this happens, but it looks like that might be it.

For what it's worth, i just had this issue with Minecraft Dungeons.  I went into the winecfg, set dxgi to wine's version, and the launcher works again without crashing.  I think they're shipping a dxgi.dll that conflicts with dxvk's.

@BruhDudeWew Friendly ping. Are you still experiencing issues like this related to dxvk?

This issue is a mess filled with completely unrelated reports about a bunch of different games.
If you do still experience any problems, please open a new issue.

authors: Alexander-Senko Blisto91 BruceNguyen812 BruhDudeWew Ereski K0bin Kilvador MonAaraj bphd doitsujin garpu guangli0510 rayrapetyan

repo: doitsujin/dxvk

license: Zlib


text:
Persona 4 Golden crashes on launch with "Application has crashed" on NVIDIA 515.43.04 drivers

Upon running Persona 4 Golden with NVIDIA 515.43.04 drivers, the game crashes immediately at launch:

This happens no matter what version of Proton is used (including known previously working ones) and it doesn't happen on NVIDIA 510.68 drivers. I've tested this by running the game with GE-Proton7-18 several times on 510.68 which worked without issues, and after updating to 515.43 without having changed the prefix or Proton version I started getting this issue.
Upon reverting back to 510.68, again on the same Proton version, the game launches perfectly. I've tested this with Experimental, GE, and older versions of Proton to no avail - all of which work on 510.68 and before.
I'm able to launch other games (such as Neptunia x SENRAN KAGURA: Ninja Wars) fine without any issues on 515.48, so this seems to only affect certain titles, one of which someone who is facing the same issue mentioned here.
Checking the log I got from launching the game with PROTON_LOG=1, some lines of interest are:
info:  Game: P4G.exe
info:  DXVK: v1.10.1-async
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
info:    OpenXR
info:  Required Vulkan extension VK_KHR_surface not supported
err:   DxvkInstance: Failed to create instance

Outside of the game working before 515.43, it also contradicts the output of vulkaninfo --summary:
==========
VULKANINFO
==========

Vulkan Instance Version: 1.3.211

Instance Extensions: count = 19
-------------------------------
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6

Instance Layers: count = 8
--------------------------
VK_LAYER_MANGOAPP_overlay         Mangoapp Layer               1.2.135  version 1
VK_LAYER_MANGOHUD_overlay         Vulkan Hud Overlay           1.2.135  version 1
VK_LAYER_NV_optimus               NVIDIA Optimus layer         1.3.205  version 1
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.2.136  version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.2.136  version 1
VK_LAYER_VALVE_steam_overlay_32   Steam Overlay Layer          1.2.136  version 1
VK_LAYER_VALVE_steam_overlay_64   Steam Overlay Layer          1.2.136  version 1
VK_LAYER_VKBASALT_post_processing a post processing layer      1.2.136  version 1

Devices:
========
GPU0:
        apiVersion         = 4206797 (1.3.205)
        driverVersion      = 2160771328 (0x80cac100)
        vendorID           = 0x10de
        deviceID           = 0x1e07
        deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName         = NVIDIA GeForce RTX 2080 Ti
        driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
        driverName         = NVIDIA
        driverInfo         = 515.43.04
        conformanceVersion = 1.3.1.0
        deviceUUID         = d6f55b39-5de1-0033-6b7e-3df9d73b7ea8
        driverUUID         = c50a21fe-1add-508b-b23c-d7b64c4bda7e

Software information
Game: Persona 4 Golden
System information

GPU: NVIDIA RTX 2080 Ti
Driver: 515.43.04
Wine version: GE-Proton7-18
DXVK version: 1.10.1

Apitrace file(s)

https://files.catbox.moe/viw1i2.xz

Log files

steam.log: steam-1113000.log
dxgi.log: P4G_dxgi.log

Nevermind, fixed the issue. Turns out NVIDIA split their driver packages for 32-bit into separate packages with the release of R515 for my distro without any notice.


text:
🛑 Feed is down

In 65d9e95, Feed (https://bsky-feed.dolciss.net/.well-known/did.json) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Feed is back up in 4e1033a after 4 minutes.

repo: dolciss/upptime


text:
for..of is not IE11 compatible

https://kangax.github.io/compat-table/es6/#ie11
While I appreciate the desire to write modern JavaScript, IE11 is going to have to be "modern" through something like 2020 thanks to the Microsoft support cycle. Transpilers work pretty hard to prevent altering node modules, so the following statement is a lot more complex for most of us than it reads.

Chai as Promised requires Node v4+ or a browser with equivalent support for modern JavaScript syntax. If your browser doesn't support modern JavaScript syntax, you'll need to transpile it down using a tool like Babel.

Would you be will to produce a browser bundle with support for current browsers?

No; please feel free to use whatever tools are appropriate for your project and environment, but that's specific to you, and won't be a part of this library.

authors: domenic ianwremmel

repo: domenic/chai-as-promised


text:
Need support for charts in Sky

From @abarth on June 14, 2015 17:40
Possibly something like https://github.com/google/charted
Presumably we don't want this in the main framework.  Charting support might be a good place to start with another Dart pub package that depends on the |sky| package.
Copied from original issue: domokit/mojo#242

From @eseidelGoogle on June 22, 2015 23:47
I briefly looked at this.  charted currently imports dart:html in many places and will take some surgery to remove that dependency. @psunkari

We now have a basic charting library in playfair.

authors: Hixie abarth


text:
USER ACCOUNTING

Can you connect this panel to Mikrotik usermanager?

Hi @mpxsam , I took a look but I don't have any knowledge on this product, I'm not sure how to do that.
Cheers,
Donald

Closing due to out of scope issue :)

authors: donaldzou mpxsam

repo: donaldzou/WGDashboard


text:
Switch to using the 'raw' binding in guides

The guides, especially the PMO guide, had some use of the
prop:from="'String value'" binding. This PR switches it to use
prop:raw="String value" instead. Closes #1087

Coverage remained the same at 96.067% when pulling 99c1472b36ca1c48cccbe73e4d11e0d5f148b4b7 on raw into 895ac366b34f38adc328b700cea5884058316d49 on master.

authors: coveralls matthewp

repo: donejs/donejs


text:
Modifying ClassNLLCriterion.cu

Replacing ClassNLLCriterion.cu in ~/torch/extra/cunn/lib/THCUNN/ throws up errors :
/u/<user>/torch/extra/cunn/lib/THCUNN/ClassNLLCriterion.cu(126): error: identifier "THCRealTensor_checkGPU" is undefined

/u/<user>/torch/extra/cunn/lib/THCUNN/ClassNLLCriterion.cu(130): error: identifier "THCRealTensor_checkGPU" is undefined

/u/<user>/torch/extra/cunn/lib/THCUNN/ClassNLLCriterion.cu(198): error: identifier "THCRealTensor_checkGPU" is undefined

/u/<user>/torch/extra/cunn/lib/THCUNN/ClassNLLCriterion.cu(203): error: identifier "THCRealTensor_checkGPU" is undefined

4 errors detected in the compilation of "/tmp/tmpxft_0000621d_00000000-7_ClassNLLCriterion.cpp1.ii".
CMake Error at THCUNN_generated_ClassNLLCriterion.cu.o.cmake:267 (message):
  Error generating file
  /u/<user>/torch/extra/cunn/build/lib/THCUNN/CMakeFiles/THCUNN.dir//./THCUNN_generated_ClassNLLCriterion.cu.o

I think the problem is caused by the torch7 version, because torch7’s backend development is quite active. The torch7 version I used is c0e51b98acbb54e6655343a57152b6e711ffdc2b.

There seems to be some more errors in THCNN , is there a specific version of that required ?
Error Message :
In file included from /u/<user>/torch/extra/cunn/lib/THCUNN/BatchNormalization.cu:1:0:
/u/<user>/torch/extra/cunn/lib/THCUNN/THCUNN.h:11:35: fatal error: THCGenerateFloatTypes.h: No such file or directory
 #include "THCGenerateFloatTypes.h"
                                   ^
compilation terminated.
CMake Error at THCUNN_generated_BatchNormalization.cu.o.cmake:206 (message):
  Error generating
  /u/<user>/torch/extra/cunn/build/lib/THCUNN/CMakeFiles/THCUNN.dir//./THCUNN_generated_BatchNormalization.cu.o
make[2]: *** [lib/THCUNN/CMakeFiles/THCUNN.dir/./THCUNN_generated_BatchNormalization.cu.o] Error 1
make[1]: *** [lib/THCUNN/CMakeFiles/THCUNN.dir/all] Error 2
make: *** [all] Error 2

The error seems to be caused by the problem of torch's install script. I am not sure what the specific reason is.

Line 44 of install.sh git submodule update --init --recursive probably needs to be uncommented since our goal is to build the specific version c0e51b98acbb54e6655343a57152b6e711ffdc2b.

Running with the git update commented out yields the following error, during the building of rocks/cunn-scm-1.rockspec. (BTW, we are building with CUDA v 8.0 for CUDA architecture 3.5.)
/u/vj0/torch/extra/cunn/lib/THCUNN/ClassNLLCriterion.cu(126): error: identifier "THCRealTensor_checkGPU" is undefined

/u/vj0/torch/extra/cunn/lib/THCUNN/ClassNLLCriterion.cu(130): error: identifier "THCRealTensor_checkGPU" is undefined

/u/vj0/torch/extra/cunn/lib/THCUNN/ClassNLLCriterion.cu(198): error: identifier "THCRealTensor_checkGPU" is undefined

/u/vj0/torch/extra/cunn/lib/THCUNN/ClassNLLCriterion.cu(203): error: identifier "THCRealTensor_checkGPU" is undefined

4 errors detected in the compilation of "/tmp/tmpxft_000006f4_00000000-7_ClassNLLCriterion.cpp1.ii".
CMake Error at THCUNN_generated_ClassNLLCriterion.cu.o.cmake:264 (message):
  Error generating file
  /u/vj0/torch/extra/cunn/build/lib/THCUNN/CMakeFiles/THCUNN.dir//./THCUNN_generated_ClassNLLCriterion.cu.o

The environment we used:
OS: Scientific Linux 7.1
GCC: 4.9.1 20140922 (Red Hat 4.9.1-10)
GPU: 980 or titan x
CUDA: 7.5

I compress my torch folder and upload it to Google Drive.
Link: https://drive.google.com/file/d/0B8yp1gOBCztycW42eDNNaExWSlU/view?usp=sharing
Hope this would help.

Thanks, with this torch folder I was able to make it work -- blew away cmake cache files, and ran install.sh. I am able to run lang2logic now... awesome!

Great!

hi @saraswat ,  I met the same problem as you. my question is how to remove the cmake cache files. I am a rookie for linux os. thanks!

@saraswat  I solved it. just run clean.sh. Thanks!

authors: Demolei avinash2692 donglixp saraswat


text:
AndroidRuntime: FATAL EXCEPTION with android.test.canceled

Version of react-native-iap
1.0.6
Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
no crash, instead fail gracefully
Actual behavior
crash in android native module
Tested environment (Emulator? Real Device?)
Device: Motoralo Moto G4
Steps to reproduce the behavior
Testing my app with test iap id android.test.canceled I get the following crash after android tells me the purchase was successful.
E/AndroidRuntime: FATAL EXCEPTION: main
                  Process: com.example.myapp.debug, PID: 15033
                  java.lang.NullPointerException: Attempt to invoke interface method 'java.lang.Object java.util.List.get(int)' on a null object reference
                      at com.dooboolab.RNIap.RNIapModule$7.onPurchasesUpdated(RNIapModule.java:379)
                      at com.android.billingclient.api.BillingClientImpl$1.onReceive(BillingClientImpl.java:136)
                      at com.android.billingclient.api.LocalBroadcastManager.executePendingBroadcasts(LocalBroadcastManager.java:303)
                      at com.android.billingclient.api.LocalBroadcastManager.access$000(LocalBroadcastManager.java:44)
                      at com.android.billingclient.api.LocalBroadcastManager$1.handleMessage(LocalBroadcastManager.java:114)
                      at android.os.Handler.dispatchMessage(Handler.java:102)
                      at android.os.Looper.loop(Looper.java:154)
                      at android.app.ActivityThread.main(ActivityThread.java:6123)
                      at java.lang.reflect.Method.invoke(Native Method)
                      at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867)
                      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:757)

Eventhough there might be actually sth. going wrong I would expect com.dooboolab.RNIap.RNIapModule to fail gracefully instead of crashing.
Thx

@martnst I haven't tried this one. I'll come back to you if I try this.

Even I am facing the same issue with android.test.canceled.

@martnst @yasheshkt Sorry for late come back guys. I was really busy these days. Could you please try 1.0.8? I've just tested this out and found out there purchases could be null when buyProduct. Please reopen when it is still crashing in 1.0.8. Thank you for the report!

@dooboolab thanks for the quick fix. It working fine for me now.

authors: dooboolab martnst yasheshkt

repo: dooboolab/react-native-iap


text:
Resubscribe not triggered on iOS

I am trying to implement a subscription on my app but, it worked great the first time, I called requestSubscription then purchaseUpdatedListener has been triggered.
But days after that, the sandbox subscription has expired and when I am calling requestSubscription then purchaseUpdatedListener is instantly triggered without asking me for the Apple Pay. The purchase variable from purchaseUpdatedListener is my old purchase which has been made days ago
When I verify the receipt from apple server using the /verifyReceipt endpoint the last expire date is 2023-01-22 18:58:28 Etc/GMT and when I am posting we are the 2023-01-25 so the subscription is expired
When I go in my phone parameters in the app store sandbox profile, I can activate again the subscription, but I would like to do it with requestSubscription, this is not really user-friendly to go into parameters, ...
Should display the purchase dialog when trying to subscribe back
Environment:

react-native-iap: 12.5.1
react-native: 0.71.1
Platforms (iOS, Android, emulator, simulator, device): iOS device

To Reproduce

create an iOS subscription
subscribe to this subscription
Wait for the subscription (this is fast in dev) or unsubscribe from the config
subscribe back

Found the solution, I had to call clearTransactionIOS before purchase

Experiencing the same behavior.
Seems finishTransaction doesn't do the job so transaction is not finished.
We do clearTransactionIOS though but only when smth went wrong, which I assume correct usage of that method

Is this happening only on dev? if finish transaction is not working, please post what the method is returning or if an error is being thrown

It seems finishTransaction not working in iOS.
iOS : 16 react-native-iap : 12.7.2 react-native: 0.68.2
        <Button
          title={`Consume all purchases`}
          onPress={async () => {
            // await deepLinkToSubscriptionsIos();
            if (availablePurchases?.length > 0) {
              availablePurchases.forEach(async (purchase: Purchase) => {
                if (purchase.productId) {
                  try {
                    const result = await finishTransaction({
                      purchase,
                      isConsumable: true,
                    });
                    console.log(`purchase result`, result);
                  } catch (e) {
                    console.error(`purchase error!`, e);
                  }
                }
              });
            }
          }}
        />

By this, result are true, but availablePurchases are not cleared.

Same here. result is true but when re-initializing IAP on next app start it will purchase the subscription again. Only on iOS. Android is totally fine and working.

Are you on StoreKit 1 or 2? Am seeing the same issue and could only solve it by moving to StoreKit 2.

Are you on StoreKit 1 or 2? Am seeing the same issue and could only solve it by moving to StoreKit 2.

SK1, probably need to upgrade yeah

https://github.com/dooboolab-community/react-native-iap/issues/2455 Can anyone please suggest on this issue Please ?

authors: Prathameshlabde Relax594 ajouve andresesfm professorkolik sedot42


text:
add missing proration mode

ProrationModesAndroid enum was missing IMMEDIATE_AND_CHARGE_FULL_PRICE mode

Thank you @mmajk55

@andresesfm Can You create release 8.6.8 with this change?

Unfortunately not @mmajk55. Since 9.0.0 was merged into master, any reason no to move to 9?


text:
Add TravisCI configuration

Title says it all 👍

Done via  2388917


text:
[Clang Compile] Fix clang compile failed in function_case

1 通过gcc和clang编译
2 通过sql正确性测试 SELECT SUM(CASE WHEN LO_SUPPLYCOST + 10000 > 100000 then 1 else 0 END) FROM lineorder_flat;

把数组声明换成then_idx_data, 然后声明一个叫then_idx的restrict指针吧... 或者把下面用到的地方都得改成then_idx_ptr也行 不能只改memset

把数组声明换成then_idx_data, 然后声明一个叫then_idx的restrict指针吧... 或者把下面用到的地方都得改成then_idx_ptr也行 不能只改memset

已更新

LGTM

LGTM

authors: BiteTheDDDDt wangbo yiguolei

repo: doris-vectorized/doris-vectorized


text:
Replace filebrowser

Sounded like a chore, actually worked out pretty nicely out of the box.

Because migrations still contain filebrowser, we'll have to squash them to remove the dependency on it (from requirements.txt). We should await doing this until we know we're safe to do so; by testing thoroughly. Nothing should have been using filebrowser for the past couple of months though, but you never know.


text:
gql-gen init - Error: Cannot find module 'graphql/language/parser'

Describe the bug
Everytime I run gql-gen I get an error
module.js:549
    throw err;
    ^
Error: Cannot find module 'graphql/language/parser'

This is happening in existing and new projects.  I am using Angular CLI to generate my projects.
To Reproduce
Steps to reproduce the behavior:
Install required packages:
npm install graphql
npm install -D graphql-code-generator
Expected behavior
I expect it to run through the gql init.  It just errors out.
Schema/Documents
If possible and relevant, please provide your GraphQL schema and GraphQL documents.
Not possible.  I cannot run init.
Environment:

OS: Windows 10
Codegen:
Node: 8.11.1

Additional context
Add any other context about the problem here.
Here is my package.json
{
  "name": "gql-test-project",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^6.0.0",
    "@angular/common": "^6.0.0",
    "@angular/compiler": "^6.0.0",
    "@angular/core": "^6.0.0",
    "@angular/forms": "^6.0.0",
    "@angular/http": "^6.0.0",
    "@angular/platform-browser": "^6.0.0",
    "@angular/platform-browser-dynamic": "^6.0.0",
    "@angular/router": "^6.0.0",
    "core-js": "^2.5.4",
    "graphql": "^14.1.1",
    "rxjs": "6.0.0",
    "zone.js": "^0.8.26"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.6.1",
    "@angular/cli": "~6.0.1",
    "@angular/compiler-cli": "^6.0.0",
    "@angular/language-service": "^6.0.0",
    "@types/jasmine": "~2.8.6",
    "@types/jasminewd2": "~2.0.3",
    "@types/node": "~8.9.4",
    "codelyzer": "~4.2.1",
    "graphql-code-generator": "^0.17.0",
    "jasmine-core": "~2.99.1",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~1.7.1",
    "karma-chrome-launcher": "~2.2.0",
    "karma-coverage-istanbul-reporter": "~1.4.2",
    "karma-jasmine": "~1.1.1",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.3.0",
    "ts-node": "~5.0.1",
    "tslint": "~5.9.1",
    "typescript": "~2.7.2"
  }
}

@aoakeson can you try to install @types/graphql as well?
Also, can you share you codegen.yml file? I guess it's an invalid import in one of the plugins.

Hi @dotansimha I installed they @types/graphql, but still getting the same error.  Like i mentioned, I was trying to run the gql-gen init command, but its erroring out.  I also created the codegen.yml file as suggested, and no luck.  Here is that file
schema: http://localhost:12465/graphql
generates:
  src/types.ts:
    - typescript-common
    - typescript-apollo-angular

You need to have documents to generate Angular services for operations inside documents. I think you don’t have a valid path defined as ‘documents’ in your configuration file.

Fixed in the recent refactor, we'll release it soon.

Fix available in 1.0.0 👍

authors: aoakeson ardatan dotansimha

repo: dotansimha/graphql-code-generator


text:
[typescript-resolvers] Create a type for directive args

I wanted to enforce a better type check when implementing Apollo custom directives, but since the directive arguments are exported inside the directive resolver type I need to create a workaround to retrieve the arguments types.
Since I have several custom directives it would be nice if the type was exported from the generated file.
Now when exporting a Directive we have:
export type MyDirectiveDirectiveResolver<
  Result,
  Parent,
  ContextType = any,
  Args = { arg1: Maybe<Scalars['String']> }
> = DirectiveResolverFn<Result, Parent, ContextType, Args>;

I would like to change it to:
export type MyDirectiveDirectiveArgs = {
  arg1: Maybe<Scalars['String']>
}
export type MyDirectiveDirectiveResolver<
  Result,
  Parent,
  ContextType = any,
  Args = MyDirectiveDirectiveArgs
> = DirectiveResolverFn<Result, Parent, ContextType, Args>;

This way I can import the Args type and set in my SchemaDirectiveVisitor for better type checking.
The workaround that I'm using is this:
/** Gets the third argument type from the function:
export type DirectiveResolverFn<
  TResult = {},
  TParent = {},
  TContext = {},
  TArgs = {}
> = (
  next: NextResolverFn<TResult>,
  parent: TParent,
  args: TArgs,
  context: TContext,
  info: GraphQLResolveInfo,
) => TResult | Promise<TResult>;
*/
type MyDirectiveArgs = Parameters<
  MyDirectiveDirectiveResolver<unknown, unknown, unknown>
>[2];

export class MyDirective extends SchemaDirectiveVisitor {
  args: MyDirectiveArgs;

You can try the following canary version with this feature until it gets released;
1.12.2-alpha-3cb57f00.14

Fixed in 1.12.2! Thanks @ardatan

Thanks! @ardatan @dotansimha

authors: ardatan dotansimha victor-accarini


text:
Not compatible with graphql-config@3 when multiple projects are defined in the .graphqlrc.yml

Describe the bug
here is the content of my .graphqlrc.yml:
projects:
  first:
    schema: ./first.graphql
    documents: ./src/first-gql.js
    extensions:
      codegen:
        generates:
        ./first.graphql:
          plugins:
            - schema-ast
      endpoints:
        default:
          url: https://first
  second:
    schema: ./second.graphql
    documents: ./src/second-gql.js
    extensions:
      codegen:
        generates:
        ./second.graphql:
          plugins:
            - schema-ast
      endpoints:
        default:
          url: https://second

But when running npx codegen generate it throws the error:
Project 'default' not found

And if naming the first project default, then it throws the error:
✖ Parse configuration
    → Invalid Codegen Configuration!
    Generate outputs
  Invalid Codegen Configuration!

        Please make sure that your codegen config file contains the "generates" field, with a specification for the plugins you need.

        It should looks like that:

        schema:
          - my-schema.graphql
        generates:
          my-file.ts:
            - plugin1
            - plugin2
            - plugin3

And if moving the generate key up, then it throws:
Unable to find Codegen config file!

Expected behavior

I expect graphql-code-generator to fully support graphql-config options.
I'm currently solving this by creating one project.codegen.yml config file per project. But it's kind of de-deduplicating graphql config in two different places (which kind of defeat why graphql-config was created in the first place no? :)
Environment:

OS: Ubuntu 20.04
NodeJS: 16.4

Thanks for your help!

i agree.... Trying to fix this issue..
Graphql  works on fb base...

I think we look for the default project by default, can you please try to add --project first to your CLI command? Seems like we do support it (https://github.com/dotansimha/graphql-code-generator/blob/6a95377706eec019d04807f735d4cedc888c42d0/packages/graphql-codegen-cli/src/config.ts#L213)

Ok, there's a catch 22 here:
For this config:
projects:
  first:
    schema: ./first.graphql
    documents: ./src/first-gql.js
    extensions:
      codegen:
        generates:
        ./first.graphql:
          plugins:
            - schema-ast
      endpoints:
        default:
          url: https://first
  second:
    schema: ./second.graphql
    documents: ./src/second-gql.js
    extensions:
      codegen:
        generates:
        ./second.graphql:
          plugins:
            - schema-ast
      endpoints:
        default:
          url: https://second

If I run npx graphql-codegen generate --project first it throws:
✔ Parse configuration
  ❯ Generate outputs
    ❯ Generate ./first.graphql
      ✖ Load GraphQL schemas
        →           - ./first.graphql
        Load GraphQL documents
        Generate

 Found 1 error

  ✖ ./first.graphql
    Error:
          Unable to find any GraphQL type definitions for the following pointers:

              - ./first.graphql

Now if I put the graphql endpoint url as the value of the schema field like this:
projects:
  first:
    schema: https://first
    documents: ./src/first-gql.js
    extensions:
      codegen:
        generates:
        ./first.graphql:
          plugins:
            - schema-ast
      endpoints:
        default:
          url: https://first
  second:
    schema: https://second
    documents: ./src/second-gql.js
    extensions:
      codegen:
        generates:
        ./second.graphql:
          plugins:
            - schema-ast
      endpoints:
        default:
          url: https://second

Then npx graphql-codegen generate --project first works!
BUT, npx eslint ./src/first-gql.js throws an error now:
/home/me/code/github.com/project/repo/node_modules/node-fetch/lib/index.js:1222
                        throw new TypeError('Expected signal to be an instanceof AbortSignal');
                        ^

TypeError: Expected signal to be an instanceof AbortSignal

I guess that graphql-code-generator should generate from the extenstion -> endpoint -> url value instead?
My use case is pretty simple: I want to regularly locally download latest version of the remote .graphql schema, in order to benefit from eslint warnings.
Preferably using one unified config file: .graphqlrc.yml :)
Thanks !

You can't use dependencies within codegen config outputs, since each one is standalone.
You can use separate config files for generating outputs that depends on each other.

It happened to me too. I would prefer if codegen can run on all projects when running generate or watch

@moshest did you check the discussion here and saw if that helped you?
https://github.com/B2o5T/graphql-eslint/issues/526

Can't see how it relevant @Urigo...
I ended up using the default project as a workaround:
projects:
  # codegen is not supporting multiple projects yet:
  # https://github.com/dotansimha/graphql-code-generator/issues/6282
  default:
    schema: services/a-service/lib/schema.graphql
    extensions:
      codegen:
        generates:
          services/b-service/queries/graphql.codegen.tsx:
            schema: services/a-service/lib/schema2.graphql
            documents: 'services/b-service/**/*.graphql'
            plugins:
              - typescript
              - typescript-operations
              - typescript-resolvers
              - typescript-react-apollo
              - fragment-matcher
              - typescript-apollo-client-helpers

          services/c-service/src/queries/graphql.codegen.tsx:
            documents: 'services/c-service/src/**/*.graphql'
            plugins:
              - typescript
              - typescript-operations
              - typed-document-node

  b-service:
    schema: 'services/a-service/lib/schema2.graphql'
    documents: 'services/b-service/**/*.graphql'
    extensions:
      codegen:
        generates:
          services/b-service/queries/graphql.codegen.tsx:
            plugins:
              - typescript
              - typescript-operations
              - typescript-resolvers
              - typescript-react-apollo
              - fragment-matcher
              - typescript-apollo-client-helpers

  c-service:
    schema: 'services/c-service/lib/schema.graphql'
    documents: 'services/c-service/src/**/*.graphql'
    extensions:
      codegen:
        generates:
          services/c-service/src/queries/graphql.codegen.tsx:
            plugins:
              - typescript
              - typescript-operations
              - typed-document-node

It allows me to run graphql-codegen on the default project by default and if needed I can run it on specific project like this: graphql-codegen --project b-service
The only downside is that we have duplicate configuration on the default project. I really wish codegen will able to support this flow and merge all configuration to one if no project provided.

https://github.com/dotansimha/graphql-code-generator/releases/tag/%40graphql-codegen%2Fcli%402.7.0

authors: FeliciaAKelley Urigo dotansimha moshest saihaj waterdrop01