mambauser cannot write to bind mounts on Linux

If a script wants to write to the current working directory on the host system, an obvious way is to use a bind mount to map a directory on the host to a directory inside the container.
Unfortunately, this does not work with Docker on Linux systems; the non-root  mambauser cannot write to directories from bind mounts, no matter if we set the UID/GID to that of the user on the host or not:
# Minimal example (works on Docker Desktop on OSX)
$ docker run --rm -it -v "$(pwd):/tmp" \
   mambaorg/micromamba:1.5.6 /bin/bash
$ id
uid=57439(mambauser) gid=57439(mambauser) groups=57439(mambauser)
$ touch test.txt
touch: cannot touch 'test.txt': Permission denied
$ touch /tmp/test.txt
touch: cannot touch '/tmp/test.txt': Permission denied

# With using the host user's UID and GID
$ docker run --rm -it --user $UID:$GID -v "$(pwd):/home/mambauser"  \
    mambaorg/micromamba:1.5.6 /bin/bash
$ cd /home/mambauser/
$ echo test > test.md
bash: test.md: Permission denied
$ ls -la
total 8
drwxr-xr-x 2 root root 4096 Jan 11 03:15 .
drwxrwxrwx 3 root root 4096 Dec 30 15:30 ..
$ pwd
/home/mambauser

Writing to Docker bind volumes on Linux systems as non-root users is a well-known and complicated topic, but I wonder if there is an elegant way of adding the mambauser to the group that has write access to a bind mount point.
Or is there any other way of writing to a directory on the host from the mambauser?
Note: The issue does not appear on Docker Desktop for OSX, as the built-in VM maps between the host system and the Docker environment.
References:

https://jtreminio.com/blog/running-docker-containers-as-current-host-user/#ok-so-what-actually-works
https://stackoverflow.com/questions/39397548/how-to-give-non-root-user-in-docker-container-access-to-a-volume-mounted-on-the
https://stackoverflow.com/questions/56019914/docker-user-cannot-write-to-mounted-folder
https://github.com/moby/moby/issues/2259
https://www.joyfulbikeshedding.com/blog/2021-03-15-docker-and-the-host-filesystem-owner-matching-problem.html

Addendum: Tested with Micromamba:1.5.6, Docker version 24.0.7, build afdd53b on Debian 11.8
Docker version 24.0.7, build afdd53b

I also tried building the Docker image locally with the host user UID, GID and username included in the build process as mycromamba, to no avail:
# Build micromamba-docker:1.5.6 locally
docker build . -t mycromamba --build-arg="MAMBA_USER=$USER" \
  --build-arg="MAMBA_USER_ID=$(id -u)" \
  --build-arg="MAMBA_USER_GID=$(id -g)"

$ docker run --rm -it --user $UID:$GID -v "$(pwd):/home/foobar/data" mycromamba /bin/bash
$ cd /home/foobar/data/
$ ls -la
total 8
drwxr-xr-x 2 root  root  4096 Jan 11 03:15 .
drwxrwxrwx 3 foobar foobar 4096 Jan 11 03:38 ..
# Writing to bind mount /home/foobar/data fails:
$ touch test.txt
touch: cannot touch 'test.txt': Permission denied
# Writing to user directory /home/foobar *inside the container* works (but is not bound to host)
$ cd ..
$ touch test.txt
$ ls
data  test.txt

Works for me:
$ docker run -it --rm -v $(pwd):/home/mambauser  -u $(id -u):$(id -g) mambaorg/micromamba:1.5.6 /bin/bash -c 'touch /home/mambauser/foobar'
$ docker version
Client: Docker Engine - Community
 Version:           24.0.6
 API version:       1.43
 Go version:        go1.20.7
 Git commit:        ed223bc
 Built:             Mon Sep  4 12:32:16 2023
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          24.0.6
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.7
  Git commit:       1a79695
  Built:            Mon Sep  4 12:32:16 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.24
  GitCommit:        61f9fd88f79f081d64d6fa3bb1a0dc71ec870523
 runc:
  Version:          1.1.9
  GitCommit:        v1.1.9-0-gccaecfc
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

On the host, do you have write permission to the working directory where you are executing the docker run ... command?
this:
drwxr-xr-x 2 root  root  4096 Jan 11 03:15 .

seems to indicate that you do not have write permissions in that directory on the host.

Just upgraded docker to the same version you tried, and I still cannot reproduce it when in a host directory where I have write access.
$ docker version
Client: Docker Engine - Community
 Version:           24.0.7
 API version:       1.43
 Go version:        go1.20.10
 Git commit:        afdd53b
 Built:             Thu Oct 26 09:08:17 2023
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          24.0.7
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.10
  Git commit:       311b9ff
  Built:            Thu Oct 26 09:08:17 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.26
  GitCommit:        3dd1e886e55dd695541fdcd67420c2888645a495
 runc:
  Version:          1.1.10
  GitCommit:        v1.1.10-0-g18a0cb0
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Works fine for me too:
$ docker run --rm -it -v "$(pwd):/tmp" --user $UID:$GID mambaorg/micromamba:1.5.6 /bin/bash
(base) I have no name!@9b2eefcffcd4:/tmp$ touch test && ls
test

Thanks for looking into this!
Please note that I am using a rootless Docker installation on the host machine, as is best practice; this may have an effect-
For my py4docker project, I was able to solve the issue as follows:

Creating a dedicated, non-root and non-sudo user on the host machine. The user in my experiments was member of the sudo group.
My new user has a UID and GID of 1000, the new one has 1002. I think I read somewhere that only UIDs from 1001 onwards work for bind volume mounting.
Made sure that when running the Docker daemon in rootless mode, you set the proper CLI context:
docker context use rootless

Without a lot of effort, I cannot tell exactly if the UID of 1000 or the sudo group membership of the user on the host cause this behavior, but the cause is most likely one of the two. The CLI context is a requirement to access the Docker daemon, but does not fix the issue (I can still reproduce it by using the UID 1000 user with sudo rights).
Again, thanks for your time and support!
PS: The problem seems to have a long history, hence I add a link to resources and findings on the topic of Docker bind mounts here for future visitors to this issue.

Works fine for me too:
$ docker run --rm -it -v "$(pwd):/tmp" --user $UID:$GID mambaorg/micromamba:1.5.6 /bin/bash
(base) I have no name!@9b2eefcffcd4:/tmp$ touch test && ls
test

In this test, it is IMO not completely clear if your write operation takes place inside the mount point or elsewhere. mambauser can write to many places inside the container, as long as the OS is not set to read-only. In my project, I take quite some effort to minimize persistent, harmful actions by the application code or its dependencies.

One small addendum:

Bash does not seem to set the $GID enviroment variable, which leads to a GID of 0 and root group membership.
So it is better to use --user $(id -u):$(id -g) than --user $UID:$GID:

With --user $(id -u):$(id -g):
docker run --rm -it -v "$(pwd):/tmp" --user $(id -u):$(id -g) mambaorg/micromamba:1.5.6 /bin/bash
(base) I have no name!@8b30d9644121:/tmp$ id
uid=1000 gid=1000 groups=1000

With --user $UID:$GID:
docker run --rm -it -v "$(pwd):/tmp" --user $UID:$GID mambaorg/micromamba:1.5.6 /bin/bash
(base) I have no name!@1433c5a8d78d:/tmp$ id
uid=1000 gid=0(root) groups=0(root)

I also find that the --user approach does allow me to access mounts in our rootless podman setup. However, --userns=keep-id:uid=1000,gid=1000 is a working alternative.
(Note that micromamba 1.5.0 and later use UID/GID 57439 instead of 1000, so you need to modify that to --userns=keep-id:uid=57439,gid=57439)

For others running into similar problems, this tool might be useful:
https://www.joyfulbikeshedding.com/blog/2023-04-20-cure-docker-volume-permission-pains-with-matchhostfsowner.html

Still working on the issue... and I think there is an underlying problem that surfaces when you are using micromamba-docker

with the plain Docker daemon (not Docker Desktop),
on a Linux machine
in rootless mode.

As far as I understand, the non-root mambauser conflicts with the way Docker in rootless mode deals with bind mounts and namespace mapping in general.
Docker in rootless mode utilizes rootlesskit, which maps user namespaces between the host system and the system inside the container.
See how rootlesskit changes the username, UID, and GID of resources owned by a local user:
# Create a test folder and file
# Default permissions set by umask
$ mkdir foo
$ cd foo
$ mkdir bar
$ touch mytext.txt
# Show permissions from the host user's perspective
$ ls -la
total 12
drwxr-xr-x  3 myusername myusername 4096 Apr 30 19:23 .
drwxr-xr-x 15 myusername myusername 4096 Apr 30 19:23 ..
drwxr-xr-x  2 myusername myusername 4096 Apr 30 19:23 bar
-rw-r--r--  1 myusername myusername    0 Apr 30 19:23 mytext.txt
$ id
uid=1000(myusername) gid=1000(myusername) groups=1000(myusername),996(docker)
# Now turning on RootlessKit, as used by Docker
# RootlessKit creates user_namespaces and executes newuidmap/newgidmap along with subuid and subgid
# https://github.com/rootless-containers/rootlesskit
$ rootlesskit bash
root@110:~/foo# ls -la
total 12
drwxr-xr-x  3 root root 4096 Apr 30 19:23 .
drwxr-xr-x 15 root root 4096 Apr 30 19:23 ..
drwxr-xr-x  2 root root 4096 Apr 30 19:23 bar
-rw-r--r--  1 root root    0 Apr 30 19:23 mytext.txt
root@110:~/foo# id
uid=0(root) gid=0(root) groups=0(root),65534(nogroup)
root@110:~/foo# exit

You can see that rootlesskit changes the owning user and user group from myusername to root and maps the UID from 1000 to 0.
This means that the non-root mambauser cannot access such files and folders, even if the UID/GID of the local user is passed to the container when Docker is run in the rootless mode (for which there are good reasons).
The exact mapping is determined by /etc/subuid and /etc/subgid.
I am reopening the issue, because

I have been unable to fix this despite considerable effort and
the WWW is full of unsatisfying solutions for the underlying problem.

It may be possible to fix this by

configuring /etc/subuid and /etc/subgid, or modifying
the _entrypoint.sh shell script or
the Dockerfile.

Any ideas will be very much appreciated!
PS: The test from earlier on fails now, too, since I changed my system to a rootless Docker configuration:
$ docker run --rm -it -v "$(pwd):/tmp" --user $(id -u):$(id -g) mambaorg/micromamba:1.5.8 /bin/bash
(base) I have no name!@a84cfa7e0ace:/tmp$ touch test
touch: cannot touch 'test': Permission denied
(base) I have no name!@a84cfa7e0ace:/tmp$ id
uid=1000 gid=1000 groups=1000
(base) I have no name!@a84cfa7e0ace:/tmp$ ls -la
total 12
drwxr-xr-x  3 root root 4096 Apr 30 19:23 .
drwxr-xr-x 17 root root 4096 Apr 30 19:54 ..
drwxr-xr-x  2 root root 4096 Apr 30 19:23 bar
-rw-r--r--  1 root root    0 Apr 30 19:23 mytext.txt

As shown above with rootlesskit alone, despite the indicated GID and UID being identical, the user namespace mechanism changes the owner to root from inside the container:
# Permissions from the host user's perspective
$ ls -la
total 12
drwxr-xr-x  3 myusername myusername 4096 Apr 30 19:23 .
drwxr-xr-x 15 myusername myusername 4096 Apr 30 19:23 ..
drwxr-xr-x  2 myusername myusername 4096 Apr 30 19:23 bar
-rw-r--r--  1 myusername myusername    0 Apr 30 19:23 mytext.txt
$ id
uid=1000(myusername) gid=1000(myusername) groups=1000(myusername),996(docker)

Wow, thanks @mfhepp for your persistence in getting to the bottom of this issue! This looks like it was quite some effort.
I have not yet used rootless mode myself (although I probably should), so this is a bit beyond my current comfort level. Thus I don't have a preference among your suggested approaches for a fix. Perhaps @wholtz has some thoughts?

Have been doing additional experiments today - here is my current summary:
Essentially, there are at least four solutions:
Option 1: Make mambauser root with --user root
I think the most pragmatic way to deal with this is to use --user root if, and only if

Docker is running in rootless mode
the host user is not root
the host user has no sudo rights.

Then mambauser will internally be root, but thanks to rootlesskit etc., this will be mapped to the host user running the container (eg. uid 1001).
This should work and is IMO quite safe. The user is not root on the host.
A similar approach has been added to syzkaller.
Downsides:

mambauser has root access inside the container and could hence to quite some stuff (e.g. accessing other users, creating new ones. One potential risk is that it could create additional users inside the container that are crafted to be mapped onto existing ones on the host (Example: There is a user with uid=3000 with sudo rights on the host, we create a new user with uid=1500 inside the container - if /etc/subuid/ allows mapping to uid 3000..., then we can do what that user can do on the host. I did not test this, but think it is possible.).
We need to make sure that the three conditions from above are safely met. If we run the same container on a system with a regular "root" Docker daemon and/or the host user has root privileges, it can do much damage.

Credits:

https://sthbrx.github.io/blog/2023/04/05/detecting-rootless-docker/ - thanks, @sthrbx!

In my py4docker project, I will likely add this to run_script.sh as a quick and portable fix with checks for the aforementioned conditions.
As for micromamba-docker, it is probably best to add a section to the documentation. Again, the WWW is full of desperate ;-) people facing similar problems with volume mounts, non-root users, and rootless Docker ;-). My fear is most of them will simply give up and run everything as root :-(.
See also my answer in https://stackoverflow.com/a/78412890/516699.
Option 2: Mimic --userns=keep-id on Docker by tweaking /etc/subuid and using a dedicated non-root user on the host (likely the best approach, not yet tested)
I think I do now understand what happens when rootlesskit uses /etc/subuid (and ...gid for the group accordingly):

root@container -> user@host: UID 0 inside the container is mapped to the uid of the user running the container on the host (Example: your UID is
UIDs 1 ...@container are mapped based on the settings in /etc/subuid for the host user.

Example: /etc/subuid contains
user: 10000,65536

This says that for the user user on the host, all UID > 0 can / will be mapped to the UID range from 10000 to 10000+65536, like so
UID on container --> UID on host
1 -> 10000
2 -> 10001
...

You can debug the mapping rules from container to host like so :
$ rootlesskit bash
# cat /proc/self/uid_map
         0       1000          1
         1     100000      65536
# cat /proc/self/gid_map
         0       1000          1
         1     100000      65536

Possible Solution:

Create a non-root user mambauser_host on the host for running rootless Docker and the micromamba-docker image with a UID of 57439 (the internal UID of mambauser). It could be any other sufficiently large UID, but this way it's more transparent.

sudo groupadd -g 57439 mambauser_host
sudo useradd mambauser_host -u 57439 -g 57439 -m -s /bin/bash
sudo paddwd mambauser_host

Install and start rootless Docker for this user.
Craft /etc/subuid and  /etc/subgid so that the UID and GUID of mambauser inside the container will map to those on the host.

This requires a bit of thinking ;-): We want the UID on the host to be 57439. The UID inside the container should be > 1000, e.g. 1002. In order to map 1002 in the container to 57439 on the host for the user mambauser_host, we need to add
`mambauser_host: 56.437, 1002``
to  /etc/subuid and  /etc/subgid.
If we then run the container with
docker run --rm -it -v "$(pwd):/tmp" --user 1002:1002 mambaorg/micromamba:1.5.8 /bin/bash

the UIDs starting from 1 will be mapped to the UID range starting at 56437, like to
UID 1 -> 56437
UID 2 -> 56438
...
UID 1002 -> 57439

Et voilà!
I have not yet tested this, but wanted to save the intermediate status. **This should basically do what --userns=keep-id:uid=57439,gid=57439 would do on Podman.
Details and Credits: https://rootlesscontaine.rs/how-it-works/userns/
Option 3: Use Podman with --userns=keep-id:uid=57439,gid=57439
# Note that we do not use the --user option, so mambauser remains 57439:57439!
podman run --rm -it -v "$(pwd):/tmp" --userns=keep-id:uid=57439,gid=57439 mambaorg/micromamba:1.5.8 /bin/bash

This is untested as I have no Podman installation at hand, but likely the cleanest approach.
Option 4: Disable user namespace with Docker in rootless mode
In theory, it might be possible to use --userns=host with Docker and disable the user namespace mechanism, like so:
docker run --rm -it -v "$(pwd):/tmp" --userns=host mambaorg/micromamba:1.5.8 /bin/bash

But it does not work, at least on my test server, and there are a bunch of Docker issues related to this, e.g. this one.
It might also introduce new security issues.
Hope you find this useful :-)! The problem has for long been a huge blocker in my workflow and I would have loved to avoid digging so deeply into this ;-). And of course, the underlying challenges are not specific to micromamba-docker; it's just that in here the non-root user makes the default recipes for mounting host volumes for write-access with a rootless Docker installation fail.

Addendum:

Instead of editing subuid and subgid with an editor, you can better usermod like so (from here):

sudo usermod --add-subuids <start>-<end> <username>

The proposed solution requires changes on the host system (new non-root user and setting subuid and subgid. This makes it a bit less portable - but then again, it is conceptually clean and IMO the most secure option despite using Podman.

Update:

My preferred Option 2 (via subuid) does not seem to work, because at least in Debian, there is a conflict when mapping the container user to the UID of the host user.
It may be worthwhile to look into how Podman is implementing --userns=keep-id in its source-code.

Solution and Conclusion
1. The best solution is to install Podman, which is super-simple, and to use the --userns=keep-id option. As the additional uid/gid parameters described in the current version are not available in e.g. Podman 3.0.1, you best use this command:
podman run --rm -it -v "$(pwd):/tmp" --userns=keep-id --user $(id -u):$(id -g) docker.io/mambaorg/micromamba:1.5.8 /bin/bash

In there, touch testfile.txt works like a charm, and the external username and id is also visible from inside.
2. The second-best solution is to use --user root when starting the container if and only if Docker is running in rootless mode and if the host user has no sudo rights.**. This can be a quick fix with acceptable risks in most cases.
docker run --rm -it -v "$(pwd):/tmp" --user root mambaorg/micromamba:1.5.8 /bin/bash

touch testfile.txt works, too, and the container root user is mapped to the local user on the host system.
The other options do not work; tweaking the subuid and subgid mapping does not work without brittle and intransparent modifications on the host system.
Hope this is useful for many of you! Frankly, it was a nightmare to get to this solution and insight and I learned many things that are intellectually interesting but were not on my bucket-list to master ;-).
Most important to say: micromamba-docker is not all all to blame that it was such a painful journey; it is Docker's insufficient documentation and the lack of --userns=host  and/or --userns=keep-id support; deeply hidden in Docker issues and other sources. The hundreds of related posts and discussions indicates that many, many others are wasting their life-time with this Docker problem. So please spread the word.
TODO: Add summary and pointer to this to the documentation.

@mfhepp thanks for the detailed investigation and clear recommendations. I am certainly in support of increasing our documentation in this area. Do you have any interest in putting together a documentation PR?

@mfhepp thanks for the detailed investigation and clear recommendations. I am certainly in support of increasing our documentation in this area. Do you have any interest in putting together a documentation PR?

Much appreciated! Will try to send a PR when I will have done my homework on py4docker!


[chore]: #4231 Update MAINTAINERS (dev branch)

Let's replace iroha2-dev MAINTAINERS file with a fresh version.

Yes, most definitely.


Undetected  licence

Hi, nlf does not detect licence for https://github.com/crypto-utils/keygrip
Reproduce
npm init -y
npm i --save keygrip
nlf

Sorry this was my mistake, was looking on wrong version. Closing issue


API not able to login using LDAP authentication

Hello, I am trying to use the next configuration for api.properties

dbname=dashboarddb
dbusername=dashboarduser
dbpassword=dbpassword
dbhost=<IP_ADDRESS>
dbport=27017
dbreplicaset=false
dbhostport=[localhost:27017,<IP_ADDRESS>:27017]
server.contextPath=/api
server.port=8085
logging.level.com.capitalone.dashboard=DEBUG
auth.authenticationProviders=LDAP,STANDARD
auth.ldapServerUrl=ldap://ip:port/dc=corp,dc=corp2,dc=com,dc=co
auth.ldapUserDnPattern=cn={0},uid={0},ou=user
auth.expirationTime=6000000
auth.adDomain=corp.corp2.com.co
auth.adRootDn=dc=corp,dc=corp2,dc=com,dc=co
auth.adUrl=ldap://ip:port

But still is not enough that get up successful authentication through ldap.
The console has the output, where the userDn is not set, i don't have idea where set him

2019-04-19 00:19:11,010 INFO  org.mongodb.driver.connection - Opened connection [connectionId{localValue:2, serverValue:572}] to <IP_ADDRESS>:27017
2019-04-19 00:19:11,225 INFO  o.s.s.l.DefaultSpringSecurityContextSource -  URL 'ldap://<IP_ADDRESS>:3268/dc=corp,dc=epm,dc=com,dc=co', root DN is 'dc=corp,dc=epm,dc=com,dc=co'
2019-04-19 00:19:11,229 INFO  o.s.l.c.s.AbstractContextSource - Property 'userDn' not set - anonymous context will be used for read-write operations
2019-04-19 00:19:11,271 INFO  o.s.s.l.u.DefaultLdapAuthoritiesPopulator - groupSearchBase is empty. Searches will be performed from the context source base
2019-04-19 00:19:11,395 INFO  o.s.b.c.e.FilterRegistrationBean - Mapping filter: 'characterEncodingFilter' to: [/]
2019-04-19 00:19:11,399 INFO  o.s.b.c.e.DelegatingFilterProxyRegistrationBean - Mapping filter: 'springSecurityFilterChain' to: [/]
2019-04-19 00:19:11,401 INFO  o.s.b.c.e.FilterRegistrationBean - Mapping filter: 'ssoAuthenticationFilter' to: [/]
2019-04-19 00:19:11,402 INFO  o.s.b.c.e.FilterRegistrationBean - Mapping filter: 'jwtAuthenticationFilter' to: [/]
2019-04-19 00:19:11,403 INFO  o.s.b.c.e.FilterRegistrationBean - Mapping filter: 'standardLoginRequestFilter' to: [/]
2019-04-19 00:19:11,404 INFO  o.s.b.c.e.FilterRegistrationBean - Mapping filter: 'githubWebhookRequestFilter' to: [/]
2019-04-19 00:19:11,406 INFO  o.s.b.c.e.FilterRegistrationBean - Mapping filter: 'ldapLoginRequestFilter' to: [/]
2019-04-19 00:19:11,407 INFO  o.s.b.c.e.FilterRegistrationBean - Mapping filter: 'apiTokenRequestFilter' to: [/]
2019-04-19 00:19:11,409 INFO  o.s.b.c.e.ServletRegistrationBean - Mapping servlet: 'dispatcherServlet' to [/]
2019-04-19 00:19:11,445 DEBUG c.c.d.a.t.JwtAuthenticationFilter - Initializing filter 'jwtAuthenticationFilter'
2019-04-19 00:19:11,449 DEBUG c.c.d.a.t.JwtAuthenticationFilter - Filter 'jwtAuthenticationFilter' configured successfully
2019-04-19 00:19:11,451 DEBUG c.c.d.a.a.ApiTokenRequestFilter - Initializing filter 'apiTokenRequestFilter'
2019-04-19 00:19:11,452 DEBUG c.c.d.a.a.ApiTokenRequestFilter - Filter 'apiTokenRequestFilter' configured successfully
2019-04-19 00:19:11,454 DEBUG c.c.d.a.ldap.LdapLoginRequestFilter - Initializing filter 'ldapLoginRequestFilter'
2019-04-19 00:19:11,455 DEBUG c.c.d.a.ldap.LdapLoginRequestFilter - Filter 'ldapLoginRequestFilter' configured successfully
2019-04-19 00:19:11,458 DEBUG c.c.d.a.w.g.GithubWebHookRequestFilter - Initializing filter 'githubWebhookRequestFilter'
2019-04-19 00:19:11,459 DEBUG c.c.d.a.w.g.GithubWebHookRequestFilter - Filter 'githubWebhookRequestFilter' configured successfully
2019-04-19 00:19:11,753 INFO  o.s.s.web.DefaultSecurityFilterChain - Creating filter chain: org.springframework.security.web.util.matcher.AnyRequestMatcher@1, [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@56cd2efe, org.springframework.security.web.context.SecurityContextPersistenceFilter@344ae67b, org.springframework.security.web.header.HeaderWriterFilter@5892ef6c, org.springframework.security.web.authentication.logout.LogoutFilter@4052896d, com.capitalone.dashboard.auth.standard.StandardLoginRequestFilter@421a9bc8, com.capitalone.dashboard.auth.sso.SsoAuthenticationFilter@6dbd2786, com.capitalone.dashboard.auth.ldap.LdapLoginRequestFilter@496e0b98, com.capitalone.dashboard.auth.apitoken.ApiTokenRequestFilter@15f5a158, com.capitalone.dashboard.auth.token.JwtAuthenticationFilter@3e3e97b5, com.capitalone.dashboard.auth.webhook.github.GithubWebHookRequestFilter@4d6b94a4, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@2e6d2caa, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@52fb5cdc, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@2f45fbb8, org.springframework.security.web.session.SessionManagementFilter@4e810743, org.springframework.security.web.access.ExceptionTranslationFilter@5e729b99, org.springframework.security.web.access.intercept.FilterSecurityInterceptor@1b70c00c]
2019-04-19 00:19:11,770 DEBUG c.c.d.a.s.StandardLoginRequestFilter - Initializing filter 'standardLoginRequestFilter'
2019-04-19 00:19:11,771 DEBUG c.c.d.a.s.StandardLoginRequestFilter - Filter 'standardLoginRequestFilter' configured successfully
2019-04-19 00:19:11,774 DEBUG c.c.d.a.sso.SsoAuthenticationFilter - Initializing filter 'ssoAuthenticationFilter'
2019-04-19 00:19:11,775 DEBUG c.c.d.a.sso.SsoAuthenticationFilter - Filter 'ssoAuthenticationFilter' configured successfully
2019-04-19 00:19:13,220 INFO  o.s.b.a.s.AuthenticationManagerConfiguration -

And login failed

2019-04-19 00:24:09,776 DEBUG c.c.d.a.ldap.LdapLoginRequestFilter - Request is to process authentication
2019-04-19 00:24:10,106 DEBUG c.c.d.a.ldap.LdapLoginRequestFilter - Authentication request failed: org.springframework.security.authentication.BadCredentialsException: Bad credentials
2019-04-19 00:24:10,107 DEBUG c.c.d.a.ldap.LdapLoginRequestFilter - Updated SecurityContextHolder to contain null Authentication
2019-04-19 00:24:10,113 DEBUG c.c.d.a.ldap.LdapLoginRequestFilter - Delegating to authentication failure handler org.springframework.security.web.authentication.SimpleUrlAuthenticationFailureHandler@4b5f26d3

I appreciate your help
Regards

I am facing the same issue. Any help please...?

When I connect to LDAP i am only supplying:
auth.adUrl=ldaps://company.com:port
auth.adDomain=login.url.com
auth.adRootDn=dc=XXX,dc=XXX,dc=company,dc=com

I changed the  configuration like you say @Sbrenthughes
This is the configuration on api.properties

auth.expirationTime=6000000
auth.secret=trB2EOD++DjyWGcVqHii8tZSx20900qe
logging.level.com.capitalone.dashboard=DEBUG
auth.authenticationProviders=LDAP,STANDARD
auth.adDomain=company.com
auth.adRootDn=cn={employee's full name},ou=city,dc=company,dc=com
auth.adUrl=ldap://company.com:port

The order of my rootDn is cn,ou,dc,dc.
The 'cn' of my company is the employee's full name, but when i try to login with correct credentials, i get the next error, where the match bind with ou,dc,dc is true

I not found that the reason for error DSID-03100241. Then, we come back to same issue ... How configure the cn for user?
Where i can set things like this (objectClass=user)(sAMAccountName={login}) ???

I am getting the same error:
ERROR o.s.s.l.a.a.ActiveDirectoryLdapAuthenticationProvi                                                                                der - Failed to locate directory entry for authenticated user: username
javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DS                                                                                ID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of:
'OU=XXX,OU=XXX,DC=XXX,DC=XXX,DC=XXX'

I changed the configuration like you say @Sbrenthughes
This is the configuration on api.properties
auth.expirationTime=6000000
auth.secret=trB2EOD++DjyWGcVqHii8tZSx20900qe
logging.level.com.capitalone.dashboard=DEBUG
auth.authenticationProviders=LDAP,STANDARD
auth.adDomain=company.com
auth.adRootDn=cn={employee's full name},ou=city,dc=company,dc=com
auth.adUrl=ldap://company.com:port
The order of my rootDn is cn,ou,dc,dc.
The 'cn' of my company is the employee's full name, but when i try to login with correct credentials, i get the next error, where the match bind with ou,dc,dc is true

I not found that the reason for error DSID-03100241. Then, we come back to same issue ... How configure the cn for user?
Where i can set things like this (objectClass=user)(sAMAccountName={login}) ???

Oh and I forget. After of this error, appers this

I am still facing this issue.
05:08:22,304 ERROR o.s.s.l.a.a.ActiveDirectoryLdapAuthenticationProvider - Failed to locate directory entry for authenticated user: username
javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of:
'DC=xxx,DC=xxx,DC=xxx'
Any suggestions please?

I changed the configuration like you say @Sbrenthughes
This is the configuration on api.properties
auth.expirationTime=6000000
auth.secret=trB2EOD++DjyWGcVqHii8tZSx20900qe
logging.level.com.capitalone.dashboard=DEBUG
auth.authenticationProviders=LDAP,STANDARD
auth.adDomain=company.com
auth.adRootDn=cn={employee's full name},ou=city,dc=company,dc=com
auth.adUrl=ldap://company.com:port
The order of my rootDn is cn,ou,dc,dc.
The 'cn' of my company is the employee's full name, but when i try to login with correct credentials, i get the next error, where the match bind with ou,dc,dc is true

I not found that the reason for error DSID-03100241. Then, we come back to same issue ... How configure the cn for user?
Where i can set things like this (objectClass=user)(sAMAccountName={login}) ???

Oh and I forget. After of this error, appers this

Have you tried ou=user instead of ou=city?

We have moved out the API from the project to its own repo. See https://github.com/Hygieia/api/issues/10 for an update on how to resolve LDAP issue.


Fix docstring for na_values in parsers

I discovered entirely by accident that the na_values in pd.read_* can be a string. According to the docstring, it can only be a sequence or a dict. This PR fixes that.

thanks!

@jaidevd There are some other places in the docs were this is described (eg in io.rst). Would you like to adapt this as well?

@jorisvandenbossche Sure. Give me a couple of hours.

@jorisvandenbossche https://github.com/pydata/pandas/pull/10488


Avoid fair lock blocking when this lock is reused

If lots of thread registered in redission fair lock queue and timeout map, and all these threads got shutdown accidently. The another app which trys to reuse this fair lock will get blocked for a long time.
Add logic to clear those not used queue info.

reopen with another pull request.


DELTASPIKE-1278: Added an additonal check

This PR adds an additional check to ensure that a given file url does exist. This allows the EnvironmentPropertyConfigSourceProvider to respect a positive optional flag. It is still to question how to handle other non file:\\ urls. I also thought about making optional handling part of PropertyFileUtils#loadPropertiesbut wasn't sure if this brings problems to other places.

Sorry for the delay, PR looks good, merged.


fix vm complete state

Description
Benchmark-runner: CNV CI: Fix VM complete state for Stressng, Uperf, Hammerdb
Fixes
Stressng - adding {{ trunc_uuid }} to roles/stressng/templates/stressng_workload_vm.yml.j2
Uperf - adding {{ trunc_uuid }} to roles/uperf/templates/configmap_script.yml.j2
hammedb - adding back VM section to roles/hammerdb/tasks/main.yaml and add {{ trunc_uuid }} to the following:
roles/hammerdb/templates/db_mariadb_workload_vm.sh.j2
roles/hammerdb/templates/db_mssql_workload_vm.sh.j2
roles/hammerdb/templates/db_postgres_workload_vm.sh.j2
Those fixes already tested and verified by benchmark-runner framework
Please merge it ASAP to make benchmark-runner CNV CI pass.

Can one of the admins verify this patch?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1cc1216). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #663   +/-   ##
=========================================
  Coverage          ?   53.48%
=========================================
  Files             ?        8
  Lines             ?      316
  Branches          ?        0
=========================================
  Hits              ?      169
  Misses            ?      147
  Partials          ?        0

Flag
Coverage Δ

gha
53.48% <0.00%> (?)

python-3.9
53.48% <0.00%> (?)

unit
53.48% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1cc1216...87f74ab. Read the comment docs.


Issue of printer emulation.

Hi,
I tried Build#317. It can print text data correctly, but still generated pgm image(s)
even I do have the libpng16.dll in the same folder as VARCem.exe.
Then I tried to print graphics data -> run "TYPE README.DOC > PRN:" under ETEN 24x24 font
environment, but failed and VARCem hangs.
By the way, on a real printer, when the ribbon is faded, we can print the same thing twice or more times
without line feed to deepen the color. Such actions can make certain lines or words more visible (more stressed). Can such an effect be simulated?

Forgot to mention this :
I can't get the result pgm image if the printed data is less than one page.
In most cases this is not the normal condition of the real printer.
Can this be set by parameters?

Hi,

The current print engine works per-page.  So, if less than one page
is printed, it wont be flushed (rendered) until you exit the application.

Graphics does not yet work, its being worked on.

PNG works fine here.  Please send me a logfile to compare with.

The hanging may have been fixed, still working on it.  Basically, a
command is sent that needs data, but not enough data is then sent,
and it will stay in that loop...
--fred

On Wed, 11/7/18, coolhaken<EMAIL_ADDRESS>wrote:
Subject: Re: [VARCem/VARCem] Issue of printer emulation. (#61)
To: "VARCem/VARCem"<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Date: Wednesday, November 7, 2018, 7:55 AM
Forgot to mention this
:
I can't get the result pgm image if the printed data is
less than one page.
In most cases this is not the normal condition of the real
printer.
Can this be set by parameters?
—
You are
receiving this because you are subscribed to this thread.
Reply to this email directly, view
it on GitHub, or mute
the thread.

Please send me a logfile to compare with.
I tried all three version of VSARCem (standard/debug/dev).
But there seems to be no option to generate a log file.

You have to start it from the commandline for that:
C:\ > VARCem.exe -L logfile.txt
optionally followed by the name of the configuration file- by default that is 'config.varc'.
Cheers,
Fred

On Thu, 11/8/18, coolhaken<EMAIL_ADDRESS>wrote:
Subject: Re: [VARCem/VARCem] Issue of printer emulation. (#61)
To: "VARCem/VARCem"<EMAIL_ADDRESS>Cc: "Fred N. van Kempen"<EMAIL_ADDRESS>"Comment"<EMAIL_ADDRESS>Date: Thursday, November 8, 2018, 6:51 AM
Please send me a logfile to compare with.
I tried all three version of VSARCem
(standard/debug/dev).
But there seems to be no option to generate a log file.
—
You are receiving this because you
commented.
Reply to this
email directly, view
it on GitHub, or mute
the thread.

VARCem's logfile doesn't "append" information correctly. (Build #317)
Everything written and overwritten and I finally got a logfile.txt which only contains this :
NVR: saving to 'D:/VARCem/nvr/ami_386dx_opti495.nvr'


progress method not executed on main thread during upload

When uploading a file and using the progress callback the callback method is not called on the main thread. Therefore a progressview is not updated during the upload.
    println("progressView created: \(NSThread.currentThread())")
    Alamofire.upload(
        Method.POST,
        URLString: "...",
        multipartFormData: { multipartFormData in
        },
        encodingCompletion: { encodingResult in
            println("encodingCompletion: \(NSThread.currentThread())")
            switch encodingResult {
            case .Success(let upload, _, _):
                upload.progress { bytesWritten, totalBytesWritten, totalBytesExpectedToWrite in
                                println("Total written \(totalBytesWritten) - progress \(progress) \(NSThread.currentThread())")
                    }

                }.responseJSON { request, response, json, error in
                    println(json)
                }
            case .Failure(let encodingError):
                println(encodingError)
            }
        }
    )

The above code results in the following log output:
progressView created: <NSThread: 0x7f9bf3546160>{number = 1, name = main}
encodingCompletion: <NSThread: 0x7f9bf3546160>{number = 1, name = main}
Total written 32768 - progress 0.193659 <NSThread: 0x7f9bf5eaf060>{number = 5, name = (null)}
Total written 65536 - progress 0.387317 <NSThread: 0x7f9bf370f680>{number = 6, name = (null)}
Total written 98304 - progress 0.580976 <NSThread: 0x7f9bf5eaf060>{number = 5, name = (null)}
Total written 131028 - progress 0.774374 <NSThread: 0x7f9bf370f680>{number = 6, name = (null)}
Total written 131072 - progress 0.774634 <NSThread: 0x7f9bf5e9fe80>{number = 4, name = (null)}
Total written 134232 - progress 0.79331 <NSThread: 0x7f9bf370f680>{number = 6, name = (null)}
Total written 138516 - progress 0.818628 <NSThread: 0x7f9bf5e9fe80>{number = 4, name = (null)}
Total written 141372 - progress 0.835507 <NSThread: 0x7f9bf5eaf060>{number = 5, name = (null)}
Total written 144228 - progress 0.852386 <NSThread: 0x7f9bf5e9fe80>{number = 4, name = (null)}
Total written 148512 - progress 0.877705 <NSThread: 0x7f9bf3416de0>{number = 7, name = (null)}
Total written 151368 - progress 0.894583 <NSThread: 0x7f9bf370f680>{number = 6, name = (null)}
Total written 155652 - progress 0.919902 <NSThread: 0x7f9bf370f680>{number = 6, name = (null)}
Total written 158508 - progress 0.936781 <NSThread: 0x7f9bf3416de0>{number = 7, name = (null)}
Total written 161364 - progress 0.95366 <NSThread: 0x7f9bf5e9fe80>{number = 4, name = (null)}
Total written 163840 - progress 0.968293 <NSThread: 0x7f9bf370f680>{number = 6, name = (null)}
Total written 168504 - progress 0.995857 <NSThread: 0x7f9bf3416de0>{number = 7, name = (null)}
Total written 169205 - progress 1.0 <NSThread: 0x7f9bf5e9fe80>{number = 4, name = (null)}
A workaround for this is to force the update of the progressview on the main thread like this:
 NSOperationQueue.mainQueue().addOperationWithBlock({ () -> Void in
       progressView.setProgress(progress, animated: true)
 })

So after much thought I think we should leave this as is. The main reason is that in some cases, we aren't going to want to call the progress closures on the main thread.
For example, if you have some library that you are working on that handles asset downloads, you probably want Alamofire to call your library off the main thread so you can then handle some processing and then eventually bubble it up to the main thread. If we automatically dispatch the progress closures to the main thread, you'll have to then dispatch again to get off the main thread causing unnecessary dispatching.
The downside of not changing the behavior is that you must dispatch to the main thread if your progress closure needs to update some user interface values. While this is unfortunate, at least you still have full control over the behavior.
Thanks for opening the issue so we could investigate!

Thanks for your reply. May I suggest to update the documentation and maybe add the workaround/solution to update the UI? It took me some time to figure out why the progress view was not updating and how to solve this. We could save this time other developers ;)

+1 for putting this in the documentation!

Absolutely @grundid...I've added a task to our Trello project to get the docs updated before the 2.0 release. I'll update this issue once I've done so. Thanks again.


.cdk-overlay-container prevents scrolling of dialog with long content

Bug, feature request, or proposal:
Not sure if it's a bug or just a misunderstanding of the use case
What is the expected behavior?
Content of dialog is scroll able or enable window scroll for long content.
What is the current behavior?
.cdk-overlay-container has pointer-events none that block scroll event and the .cdk-overlay-container remain in  after dialog closed.
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Based on Basic dialog example
https://plnkr.co/edit/O9r1GdiNkq9MhTQSCQiy?p=preview
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Most of the modern browsers
Is there anything else we should know?

@sashanana Try wrapping the content of the dialog in <md-dialog-content></md-dialog-content> tags :)

It sounds like you're looking for md-dialog-content
https://material.angular.io/components/component/dialog


[fontconfig] Disable install data files

Do not install data on *inx to avoid installation issue.
Fixes #14864.

@BillyONeal  No, only zh_CN is set in the source code of fontconfig.

Sounds great, thanks!


Lowercase account names. Fixes #1108

Does this affect .Account comparisons? E.g. the one in UseLocalAvatar https://github.com/42wim/matterbridge/blob/eaf92fca4ddf6bf78d2092618a4dc93b78af7140/bridge/discord/discord.go#L403-L406

No, it's still case-sensitive there. It only is an issue with the viper AllKeys() method which only returns lowercase keys. (only used there in the code)


Add libvirt log filters to make logs less verbose and more concrete

What this PR does / why we need it:
This PR serves two purposes:

Adds a possibility to override Kubevirt's default libvirt log filters though VMI annotations. This may be helpful for both debugging, developing and production. To override defaults filters one needs to add an annotation where the key is "log-filters" and the value is a string representing libvirt filters.

Example:
kind: VirtualMachineInstance
metadata:
  name: my-vmi
  annotations:
    log-filters: "3:remote 4:event 3:util.json 3:util.object 3:util.dbus 3:util.netlink 3:node_device 3:rpc 3:access 1:*"

Massively reduces log length where libvirt debug logs are turned on (environment variable LIBVIRT_DEBUG_LOGS is defined and equals to 1) alongside virt-launcher log verbosity (defined in KubevirtCR's developerConfiguration).

Below you can see a table for the filters I've added alongside their impact. This was measure in the following way; I've created a VMI with a custom filter log-filters: "1:XYZ 4:*" where XYZ is a certain filter. I've created the VMI, waited for 10 seconds, collected virt-launcher log, then removed the VMI. Then I've filtered out all line that do not have "subcomponent":"libvirt" in the log so I only count libvirt log entries. Here are the results:

Filter category
number of log lines
log link

qemu.qemu_monitor
2805
log

util.threadjob
119
log

qemu.qemu_monitor_json
899
log

conf.domain_addr
288
log

cpu.cpu
1911
log

Here's the before/after results for default filters and after adding all of the above:

Description
number of log lines
log link

With currently defined filters
5925
log

With all filters defined above
818
log

As you can see from provided logs, most of the categories above include noise for the vast majority of the use cases. If these categories do matter - it is possible to re-add them to VMIs with the annotation explained above.
IMPORTANT NOTE: All filters are added with level 3, meaning that debug and info logs will be filtered while warning and errors logs will be recorded. Take a look here for more info.
Release note:

Adds a possibility to override default libvirt log filters though VMI annotations

/hold
Seems that [test_id:3197] fails. This is part of the test:
// There are plenty of strings we can use to identify the debug logs.
// Here we use something we deeply care about when in debug mode.
Eventually(logs,
  2*time.Second,
  500*time.Millisecond).
  Should(And(ContainSubstring("QEMU_MONITOR_SEND_MSG"), ContainSubstring(`"subcomponent":"libvirt"`)))

If I remove the QEMU_MONITOR_SEND_MSG part, meaning: Should(ContainSubstring("subcomponent":"libvirt")), this test passes.
My question - do we really care that much about QEMU_MONITOR_SEND_MSG (it is part of qemu.qemu_monitor category, see all category related events in this log)? This category is very verbose - it added almost 3,000 log entries in the 10 seconds long experiment I made. Would like to hear thoughts about that.
p.s. [test_id:7529] passes locally.

/retest

/test pull-kubevirt-e2e-k8s-1.20-sig-compute-nonroot

@andreabolognani Thanks for your awesome review! All is addressed now, please share your thoughts.

/test pull-kubevirt-unit-test
They pass locally...

/test pull-kubevirt-unit-test

Look great! Thanks @iholder-redhat !
@andreabolognani Thank you very much for your review!
/approve

@iholder-redhat you have a hold on the PR. Is it intentional?

@iholder-redhat you have a hold on the PR. Is it intentional?

Thanks for the reminder, it's no longer relevant. Thanks!
/hold cancel
/retest

@andreabolognani Thanks very much for your fruitful review!
Do you mind LGTMing if no more changes required? Thanks!

Sure thing, I'm just never sure how much "power" I actually have in the context of KubeVirt ;)
/lgtm

I had some unit tests with the same description.. that's why they "failed".
@andreabolognani can you re-LGTM? :) sorry for the trouble!

/test pull-kubevirt-e2e-k8s-1.22-sig-storage

No worries :)
/lgtm

/test pull-kubevirt-e2e-kind-1.19-vgpu


Implement proper client side routing for all BOS  tags

There are a lot of <a> tags used throughout BOS that cause really inefficient page reloads or redirects due to them not being native Next/Link components (which use client side routing). We should first investigate implementing customElements.Link in our VM initialization: https://github.com/NearSocial/VM/releases/tag/2.1.0
We'll then need to do a find and replace for all <a> tags in our components repo to use this Link component instead.

Needed to implement a VM change to support this ticket: https://github.com/NearSocial/VM/pull/149
This will be a blocker until merged and published with a new VM version @charleslavon.


Themes updates

Diner domain can use light or dark
Merchant domain can use light, classic or dark

This has been corrected in TK3. Closing issue


Expose wrestic metrics

As a k8up user
I want I don't want to install prometheus pushgw
So that managing k8up installations is easier
Context
Currently wrestic is sending the metrics to a prometheus push gateway containing a bit more detailed information about the actual job run. Also the operator has a prometheus metrics endpoint that could potentially host the metrics.
While the push gateway is intended to be used in such a fashion it' not really great to use. Also it's another cog in an already complex machine. Getting rid of it makes the whole management easier.
So there should be a way for the operator to collect those metrics and expose them directly.
Out of Scope

redefining what the metrics should be

Further links
Acceptance criteria
Given an k8up installation
When a job finishes
Then the metrics will be available in the operator's own metric endpoint
Implementation Ideas

termination-log?
wrestic updates the status of it's job object and the operator updates the metrics accordingly

Given the plan to integrate wrestic into K8up, we should also keep resp. move wrestic's metrics to K8up as well. So closing this issue, please reopen if still somehow relevant.


fix: CS8667 Nullability of reference types in type of

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 11.0.999-cibuild0023640-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0023649-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


Showing black background.

I am using this library and when i set image using picasso image shows black background and when i resume app and open again it goes.

Are you using LAYER_TYPE_SOFTWARE?

Yes but not working this.
On Fri, 17 Aug 2018, 7:17 pm Henning Dodenhof<EMAIL_ADDRESS>wrote:

Are you using LAYER_TYPE_SOFTWARE?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hdodenhof/CircleImageView/issues/282#issuecomment-413871191,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKq7H8D8ZrZC5tkX3fVCNlYqJgnRN7vcks5uRslUgaJpZM4VzWgv
.

Well, you shouldn't use that.

How can i resolve that issue?
On Fri, 17 Aug 2018, 10:00 pm Henning Dodenhof<EMAIL_ADDRESS>wrote:

Well, you shouldn't use that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hdodenhof/CircleImageView/issues/282#issuecomment-413919799,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKq7H2ruHIjJOI6NCumcYMGaoxpYPqCsks5uRu-WgaJpZM4VzWgv
.

As I said: if you are using LAYER_TYPE_SOFTWARE you need to disable that. If you aren't using LAYER_TYPE_SOFTWARE, please provide more details about your environment, i.e. the device this happens on an the Android version.

I ma facing this issue in all devices like Samsung S6,Samsung A5 etc...

I have loaded image using Picasso.

From Xml File:
<de.hdodenhof.circleimageview.CircleImageView
android:id="@+id/image_profile"
android:layout_width="120dp"
android:layout_height="120dp"
android:layout_alignParentTop="true"
android:layout_centerHorizontal="true"
android:src="@drawable/large_profile_placeholder"
app:civ_border_color="#ffffff"
app:civ_border_width="1dp" />
//Using Picasso
Picasso.with(mContext).
load(MY_URL)
.placeholder(R.drawable.large_profile_placeholder)
.into(image_profile);

This is happening for me on Android Things using the Raspberry Pi 3. Same setup as maheshsuthar93 software wise

Ok so for me, it loads fine the first time inside of my fragment. Then when I switch to a different Fragment and then back to the original one, that is when the black box appears. And it only appears for facebook profile pictures (jpeg images)

Does this only happen for images loaded using Picasso?

Does disabling the memory cache in Picasso change the outcome in any way?

How do we disable cache? There are several examples on their github, but which one do we try?

Ok I tried adding .networkPolicy(NetworkPolicy.NO_CACHE).memoryPolicy(MemoryPolicy.NO_CACHE) and that did fix it!

Ok I spoke too soon. It works better than it did before, but it still gets a black border every now and then

I have implemented all but not works and in samsung device some time it
shows placeholder and image both at a time with unexpected results.
On Sat, 8 Sep 2018, 12:59 am Nick Wallace<EMAIL_ADDRESS>wrote:

Ok I spoke too soon. It works better than it did before, but it still gets
a black border every now and then
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hdodenhof/CircleImageView/issues/282#issuecomment-419542308,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKq7H-5kIcyc3YJY97gc8VbMFuIm3o3qks5uYskYgaJpZM4VzWgv
.

I should also say this is happening in Android Things as well. This is what I am using this library on

I am also facing placeholder issue like above in some devices its showing also placeholder with cut edges.

I'm sorry for the delay, work keeps me quite busy days. Unfortunately I can't reproduce any of the issues with the devices I have at hand. It's very likely that the root cause is an issue with the image decoder on some devices, i.e. nothing that can be fixed in this library. I might be able to add a workaround but I would first need to be able to reproduce the issue.
Can you provide a minimal running sample app that shows these issues together with information on the device you're having this issues on, its Android version, etc.?

Not much I can do without the requested details.


Default language not applied after open an python ipynb file

Describe the bug
With polyglot notebook installed in VS Code. Open an ipynb file with python code cells in it.
Select kernel ".NET Interactive"
Even the default language configuration is F#, all the cells are initialized with C# language.
Please complete the following:
Which version of .NET Interactive are you using? (In a notebook, run the #!about magic command. ):
.NET Interactive

© 2020 Microsoft Corporation

Version: 1.0.512901+07977b2f577c0c9a2bc47fc2ca1df2f59a14c825

Library version: 1.0.0-beta.24129.1+07977b2f577c0c9a2bc47fc2ca1df2f59a14c825

Build date: 2024-03-10T05:03:32.3855964Z

OS

[ ] Windows Server 2019

Frontend

[ ] Visual Studio Code

Even the default language configuration is F#

Could you provide more details? Are you describing a default for the specific notebook file? How was the notebook created?

Hi, ^^
https://github.com/d2l-ai/d2l-zh-pytorch-colab/blob/main/chapter_preliminaries/probability.ipynb
I don't know how it was created...

I am experiencing an issue like this also. If I add a new file in vscode and name it file.dib it will default to C#.
The vscode Polyglot-notebook: Default Notebook Language setting is set to fsharp.
Looking at the file.dib in a text editor, I see this
#!meta

{"kernelInfo":{"defaultKernelName":"csharp","items":[{"aliases":[],"name":"csharp"}]}}

#!fsharp

//test

so the extension seems to not be picking up the default setting.
I tried on linux and windows and both do this.
linux -> LMDE6 (Linux Mint Debian Edition 6)
windows -> 10
Version: 1.87.1
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:21:07.287Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.1.0-18-amd64

.NET Interactive

© 2020 Microsoft Corporation

Version: 1.0.516401+c4e9b8ca9ec9d23dc04cf02cc5bfce25a157384b

Library version: 1.0.0-beta.24164.1+c4e9b8ca9ec9d23dc04cf02cc5bfce25a157384b

Build date: 2024-03-14T21:26:06.0000000Z

But this works fine.
https://github.com/dotnet/TorchSharpExamples/blob/main/tutorials/FSharp/synthetic_data.ipynb
Once we open the ipynb file and all cells are in F#.

The default language setting only affects new notebooks. Existing notebooks will have a default language set in their metadata, which takes precedence over this setting.

I don't know how it was created...

Based on the metadata from the notebook you linked, I would assume Jupyter. It doesn't contain .NET Interactive metadata but it seems like the correct behavior would be to identify the cells as being Python.

But when I change the kernel from CPython to .net interactive, it changes all cells into c#, even not Python....

Yes, that's a bug.


form: fix coverity issues.

Signed-off-by: Gustavo Lima Chaves<EMAIL_ADDRESS>

Done.


[Sticky] Check bottom of browser instead of only top

It would be handy if we could tell Sticky to check the bottom of the page if specific location is reached.
example:
<div class="sticky" data-sticky data-top-anchor="foo:top" data-top-screen-location="bottom" data-btm-anchor="foo:bottom" data-margin-top="0">
data-top-screen-location default should be top of course.

Hi @RvWensen,
I don't understand the feature you request. Could you follow the GitHub template we provide (https://github.com/zurb/foundation-sites/issues/new) and add more informations about how data-top-screen-location="bottom" shoud behave and what you understand by "check the bottom" ?
Thank you.

@ncoden
With sticky you can check if for example data-btm-anchor="foo:bottom" reached the the top of the screen.
So when, you scroll over the id foo, the sticky is activated.
But there is no why to let sticky check the bottom of the screen so when you scroll over id with the bottom of the page you can not activate or deactivate sticky.
I hope this explains what i mean? :-)


modified to point to my branch version of main

Skeptical that this is the issue as the build seems to be fine. Issue seems to be that payu doesnt like the module corresponding to my branch

IDK why this happened. I made same changes that are in update_cable3. I incremented the<EMAIL_ADDRESS>line which maybe I shouldn't have but error looks substantially worse than that

Hi Jhan
It looks like this repository is not fully set up yet. I would try copying .github/workflows and config folders from https://github.com/ACCESS-NRI/ACCESS-ESM1.6/pull/11 (or just merge that branch into this one)


ValueError: an illegal memory access was encountered terminate called after throwing an instance of 'std::runtime_error'   what():  ./include/cudarray/common.hpp:95: an illegal memory access was encountered 中止 (コアダンプ)

Hi Andersbll,
GTX1080 with CUDA8.0.27 and cudnn 5.1 here.
Installed cudarray with cuda back-end. Then try running this project but failed because illegal memory access.
LOG:

Traceback (most recent call last):
File "neural_artistic_style.py", line 138, in
run()
File "neural_artistic_style.py", line 130, in run
cost = np.mean(net.update())
File "/home/caoxiaolun/Workspace/CNN/neural_artistic_style/neural_artistic_style-master/style_network.py", line 150, in update
weight = float(self.style_weights[l]) / norm
File "/usr/local/lib/python2.7/dist-packages/cudarray-0.1.dev0-py2.7-linux-x86_64.egg/cudarray/cudarray.py", line 124, in rdiv
return elementwise.divide(other, self)
File "/usr/local/lib/python2.7/dist-packages/cudarray-0.1.dev0-py2.7-linux-x86_64.egg/cudarray/elementwise.py", line 167, in divide
return binary(elementwise.div_op, x1, x2, out)
File "/usr/local/lib/python2.7/dist-packages/cudarray-0.1.dev0-py2.7-linux-x86_64.egg/cudarray/elementwise.py", line 87, in binary
out = cudarray.empty(array.shape, dtype=out_dtype)
File "/usr/local/lib/python2.7/dist-packages/cudarray-0.1.dev0-py2.7-linux-x86_64.egg/cudarray/cudarray.py", line 246, in empty
return ndarray(shape, dtype=dtype)
File "/usr/local/lib/python2.7/dist-packages/cudarray-0.1.dev0-py2.7-linux-x86_64.egg/cudarray/cudarray.py", line 36, in init
self._data = ArrayData(self.size, dtype, np_data)
File "cudarray/wrap/array_data.pyx", line 16, in cudarray.wrap.array_data.ArrayData.init (./cudarray/wrap/array_data.cpp:1473)
File "cudarray/wrap/cudart.pyx", line 12, in cudarray.wrap.cudart.cudaCheck (./cudarray/wrap/cudart.cpp:824)
ValueError: an illegal memory access was encountered
terminate called after throwing an instance of 'std::runtime_error'
what():  ./include/cudarray/common.hpp:95: an illegal memory access was encountered
中止 (コアダンプ)

Besides, if I switch user to root and run, CUDA back-end will be unavailable: "CUDArray: CUDA back-end not available, using NumPy." But normal user will not show up this.
Thanks for your help.
oscarriddle
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 367.44                 Driver Version: 367.44                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1080    Off  | 0000:01:00.0      On |                  N/A |
|  0%   40C    P8    10W / 210W |    345MiB /  8112MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0       935    G   /usr/lib/xorg/Xorg                             231MiB |
|    0      1558    G   compiz                                         109MiB |
|    0      1894    G   /usr/lib/firefox/firefox                         2MiB |
+-----------------------------------------------------------------------------+

Hi,
In previous issue: here
It seems that this issue is somehow because of out of memory. I checked nvidia-smi and find at peak, python will consume more than 2GB memory.
I just tried to reproduce the image by command:
python neural_artistic_style.py --subject images/tuebingen.jpg --style images/starry_night.jpg
Not sure why there will be an out of memory issue.
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 367.44                 Driver Version: 367.44                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1080    Off  | 0000:01:00.0      On |                  N/A |
| 72%   55C    P2   191W / 210W |   2800MiB /  8112MiB |     96%      Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0       935    G   /usr/lib/xorg/Xorg                             279MiB |
|    0      1558    G   compiz                                         119MiB |
|    0      1894    G   /usr/lib/firefox/firefox                         2MiB |
|    0     15425    C   python                                        2395MiB |
+-----------------------------------------------------------------------------+

Continue. I tried to step by step check whether I lost something so now cudarray cannot work.

By running CUDA 8.0RC samples, the CUDA 8.0RC  is working. check
cuDNN is installed correctly. check
After including export path and env variable CUDNN_ENABLED=1 into /etc/profile. Now cudarray is installed and can be imported. check
I tried cudarray examples/test.py then got below log:

$python test.py
True
.
.
.
True
True
True
False
True
True
True
False
(3.0232945639326929, 3.0016344)
(10.010378811733982, 9.9944296)
(0.49997663711219476, 0.50012529)
(0.28865082930213165, 0.28864652)
(10.019171134185873, 10.004223)
(11.540598502938147, 11.549608)
Traceback (most recent call last):
File "test.py", line 494, in
run()
File "test.py", line 488, in run
test_reduce()
File "test.py", line 347, in test_reduce
print(np.allclose(c_np, np.array(c_ca)))
File "/usr/local/lib/python2.7/dist-packages/cudarray-0.1.dev0-py2.7-linux-x86_64.egg/cudarray/cudarray.py", line 42, in array
self._data.to_numpy(np_array)
File "cudarray/wrap/array_data.pyx", line 24, in cudarray.wrap.array_data.ArrayData.to_numpy (./cudarray/wrap/array_data.cpp:1593)
File "cudarray/wrap/cudart.pyx", line 12, in cudarray.wrap.cudart.cudaCheck (./cudarray/wrap/cudart.cpp:824)
ValueError: an illegal memory access was encountered
terminate called after throwing an instance of 'std::runtime_error'
what():  ./include/cudarray/common.hpp:95: an illegal memory access was encountered
中止 (コアダンプ)

This also showd that the cudarray is not working. Not sure whether because it cannot utilize the cuDNN and CUDA, so any memory allocation(even very tiny) will exceed the limitation. Still not sure how to solve it.

just wanted to note that I'm having the same issue on a GTX1080, which is funny because it worked a month or so ago with a different GTX1080. Other deep learning frameworks are working fine right now, will post again once I find out more, probably will go with a system reinstall first

have the same issue on a GTX850M,  which makes me disappointed

the same problem, is anyone know how to solve it?

@andersbll
@oscarriddle
I also met this problem.here is the log:
Traceback (most recent call last):
File "neural_artistic_style.py", line 138, in
run()
File "neural_artistic_style.py", line 130, in run
cost = np.mean(net.update())
File "/home/sojoyoo/neutral_style_adv_2/style_network.py", line 150, in update
weight = float(self.style_weights[l]) / norm
File "/home/sojoyoo/anaconda2/lib/python2.7/site-packages/cudarray-0.1.dev0-py2.7-linux-x86_64.egg/cudarray/cudarray.py", line 124, in rdiv
return elementwise.divide(other, self)
File "/home/sojoyoo/anaconda2/lib/python2.7/site-packages/cudarray-0.1.dev0-py2.7-linux-x86_64.egg/cudarray/elementwise.py", line 167, in divide
return binary(elementwise.div_op, x1, x2, out)
File "/home/sojoyoo/anaconda2/lib/python2.7/site-packages/cudarray-0.1.dev0-py2.7-linux-x86_64.egg/cudarray/elementwise.py", line 87, in binary
out = cudarray.empty(array.shape, dtype=out_dtype)
File "/home/sojoyoo/anaconda2/lib/python2.7/site-packages/cudarray-0.1.dev0-py2.7-linux-x86_64.egg/cudarray/cudarray.py", line 246, in empty
return ndarray(shape, dtype=dtype)
File "/home/sojoyoo/anaconda2/lib/python2.7/site-packages/cudarray-0.1.dev0-py2.7-linux-x86_64.egg/cudarray/cudarray.py", line 36, in init
self._data = ArrayData(self.size, dtype, np_data)
File "cudarray/wrap/array_data.pyx", line 16, in cudarray.wrap.array_data.ArrayData.init (./cudarray/wrap/array_data.cpp:1465)
File "cudarray/wrap/cudart.pyx", line 12, in cudarray.wrap.cudart.cudaCheck (./cudarray/wrap/cudart.cpp:816)
ValueError: an illegal memory access was encountered
terminate called after throwing an instance of 'std::runtime_error'
what():  ./include/cudarray/common.hpp:95: an illegal memory access was encountered
已放弃 (核心已转储)
env is ： Ubuntu 16.04 cuda 8.0,cudnn 5.0, gforce gtx 1070(8G memory)


NVidia cuda support

Could you please consider supporting NVidia cuda drivers implementation in Rancher OS?
NVidia is already providing docker support here https://github.com/NVIDIA/nvidia-docker

+1

+1

Working on the support of Nvidia cuda drivers implementation in Rancher OS.But now there is a problem that hardware devices cannot be identified in the os kernel，which leads to the fact that driver cannot be installed.
The following are the contrast between RancherOS and Ubuntu16.04
RancherOS:
00:1e.0 Class 0302: 10de:102d
Ubuntu16.04:
00:1e.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)

Drivers identify the hardware by their PCI IDs; 10de:102dis the ID of that card.  There is not a database of ID->human friendly name mappings loaded in RancherOS, but this shouldn't affect anything with the driver detecting it.

@vincent99 Yes, drivers identify hardware by PCI IDs.The error of  installation caused by other reasons. Thank you very much.

Tested with rancheros v1.4.0-rc1.
I verified this issue with reference to https://github.com/rancher/os-services/tree/master/n, but I encountered some errors in the execution of /var/lib/rancher/nvidia/build.sh that made me No way to continue.
The below is error output
  ERROR: An error occurred while performing the step: "Building kernel modules". See /var/log/nvidia-installer.log for details.

  ERROR: An error occurred while performing the step: "Checking to see whether the nvidia kernel module was successfully built". See
         /var/log/nvidia-installer.log for details.

  ERROR: The nvidia kernel module was not created.

  ERROR: Installation has failed.  Please see the file '/var/log/nvidia-installer.log' for details.  You may find suggestions on fixing installation
         problems in the README available on the Linux driver download page at www.nvidia.com.

The nvidia-docker cannot work with our new kernel, we have asked for help to that community.
Keep this open before we find the solution and remove this feature in v1.4.0 milestone.

Does this work now?

We have fixed the kernel issue, I think we can add this nvidia-docker support on next release.

Awesome. Do you know when the next release might be for RancherOS?
On Aug 15 2018, at 8:56 pm, niusmallnan<EMAIL_ADDRESS>wrote:

We have fixed the kernel issue, I think we can add this nvidia-docker support on next release.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (https://github.com/rancher/os/issues/1637#issuecomment-413387302), or mute the thread (https://github.com/notifications/unsubscribe-auth/ABu0acPTYAmES5dv9H0-UlFyoB_owcRyks5uRMNXgaJpZM4MFled).

Hi there! Any update on this?

I want to integrate nvidia-docker2, currently mainly related to these projects.

https://github.com/NVIDIA/nvidia-docker
https://github.com/NVIDIA/libnvidia-container
https://github.com/NVIDIA/nvidia-container-runtime

They almost only provide deb and rpm packages, and it seems difficult to install from binary. So at this stage I don't plan to support it in the default console. I will give priority to supporting it in the ubuntu console.
Usually we just need to add the apt source and install the corresponding deb, but there will be a problem in ROS. The nvidia-docker2 relies on docker deb files, ROS does not use the deb to manage docker.
# https://github.com/NVIDIA/nvidia-docker/blob/master/debian/control

Package: nvidia-docker2

Architecture: all
Breaks: nvidia-docker (<< 2.0.0)
Replaces: nvidia-docker (<< 2.0.0)
Depends: ${misc:Depends}, nvidia-container-runtime (= @RUNTIME_VERSION@), @DOCKER_VERSION@

So I can customize nvidia-docker2, just remove this dependency.
Boot a vm(Ubuntu 18.04), and build the package after this patch
diff --git a/debian/control b/debian/control
index d06d85f..86d2023 100644
--- a/debian/control
+++ b/debian/control
@@ -12,7 +12,7 @@ Package: nvidia-docker2
 Architecture: all
 Breaks: nvidia-docker (<< 2.0.0)
 Replaces: nvidia-docker (<< 2.0.0)
-Depends: ${misc:Depends}, nvidia-container-runtime (= @RUNTIME_VERSION@), @DOCKER_VERSION@
+Depends: ${misc:Depends}, nvidia-container-runtime (= @RUNTIME_VERSION@)
 Description: nvidia-docker CLI wrapper
  Replaces nvidia-docker with a new implementation based on
  nvidia-container-runtime

Just run make 18.06.1-ubuntu18.04, you can replace 18.06.1 if you want to support other docker version.
Boot a ROS(v1.5.0) instance, and add nvidia-docker repo, but we need to use the ubuntu console
ros console switch ubuntu

apt update && apt install gnupg

curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | \
  sudo apt-key add -
curl -s -L https://nvidia.github.io/nvidia-docker/ubuntu18.04/nvidia-docker.list | \
  sudo tee /etc/apt/sources.list.d/nvidia-docker.list
apt update

Install pakages
apt install  nvidia-container-runtime=2.0.0+docker18.06.1-1

# install your custom nvidia-docker
dpkg -i nvidia-docker2_2.0.3+docker18.06.1-1_all.deb

Tesla K80 installed - (is there a special way of installing NVIDIA driver on RancherOS 1.5.0?)
docker run --runtime=nvidia --rm nvidia/cuda nvidia-smi
reports an error:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused "process_linux.go:385: running prestart hook 1 caused \"error running hook: exit status 1, stdout: , stderr: exec command: [/usr/bin/nvidia-container-cli --load-kmods configure<EMAIL_ADDRESS>--device=all --compute --utility --require=cuda>=10.0 brand=tesla,driver>=384,driver<385 --pid=8281 /var/lib/docker/overlay2/9b72f828525e4a83bd6084006f7caf8af91ad99b8249cc50e89de7053f24462e/merged]\\nnvidia-container-cli: initialization error: cuda error: no cuda-capable device is detected\\n\""": unknown.

I got a similar error
lspci | grep NVIDIA
01:00.0 3D controller: NVIDIA Corporation GK106M [GeForce GTX 765M] (rev a1)

docker run --runtime=nvidia --rm nvidia/cuda:9.0-base nvidia-smi
docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"process_linux.go:407: running prestart hook 1 caused \\\"error running hook: exit status 1, stdout: , stderr: exec command: [/usr/bin/nvidia-container-cli --load-kmods configure<EMAIL_ADDRESS>--device=all --compute --utility --require=cuda>=9.0 --pid=8168 /var/lib/docker/overlay2/514c92b8bb41862f9810364512638163ada28875a193b4f4200e7d6563ee15ac/merged]\\\\nnvidia-container-cli: initialization error: driver error: failed to process request\\\\n\\\"\"": unknown.

although the error is different at the end initialization error: driver error: failed to process request

@niusmallnan So it's  fixed now?

I went through the steps outlined by @niusmallnan above and kept running into the following error:
nvidia-container-cli: ldcache error: process /sbin/ldconfig.real failed with error code: 1

After a little digging, I found that it's failing when trying to pivot_root here:
https://github.com/NVIDIA/libnvidia-container/blob/deccb2801502675bd283c6936861814dbca99ecd/src/nvc_ldcache.c#L117
I'm not sure why it's failing there or how to fix it, but thought I'd share my findings in case it helps someone else narrow down the issue.

@davidhyman did you get this to work on rancher OS using the patched package?

Is this issue still being worked on and if so, any update on the status?

+1 interested in the status of this issue

+1 interested in the status of this issue

+1 interested in the status of this issue

+1 interested in the status of this issue

Looking through the rancher docs I found this page that talks about scheduling pods to nodes with gpus for what it's worth.

+1 interested in the status of this issue

+1 interested in the status of this issue


Adding helper for starting thread in teams

Pull Request Test Coverage Report for Build 110751

6 of 12 (50.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 83.339%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/botbuilder/src/teamsInfo.ts
6
12
50.0%

Totals

Change from base Build 110694:
0.08%

Covered Lines:
9276

Relevant Lines:
10717

💛  - Coveralls

Pull Request Test Coverage Report for Build 110750

6 of 12 (50.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 83.236%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/botbuilder/src/teamsInfo.ts
6
12
50.0%

Totals

Change from base Build 110694:
-0.02%

Covered Lines:
9267

Relevant Lines:
10717

💛  - Coveralls

fixes #1631


Yocto build error

Trying to build an image with bitbake core-image-base (using docker because I don't have Ubuntu) but get following errors:
$ bitbake core-image-base
Loading cache: 100% |###############################################################################################################################################################################| Time: 0:00:00
Loaded 1647 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "2.0.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-22.04"
TARGET_SYS           = "arm-poky-linux-musleabi"
MACHINE              = "stm32f769-disco"
DISTRO               = "poky"
DISTRO_VERSION       = "4.0.9"
TUNE_FEATURES        = "armv7em cortexm7"
TARGET_FPU           = "soft"
meta
meta-poky
meta-yocto-bsp
meta-stm32f7x        = "<unknown>:<unknown>"

...
| ../libffi-3.4.4/src/arm/sysv.S: Assembler messages:
| ../libffi-3.4.4/src/arm/sysv.S:104: Error: selected processor does not support ARM opcodes
| make[2]: Leaving directory '/home/miha/stm/yocto/build/tmp/work/cortexm7-poky-linux-musleabi/libffi/3.4.4-r0/build'
| make[2]: *** [Makefile:1288: src/arm/sysv.lo] Error 1
| make[1]: *** [Makefile:1384: all-recursive] Error 1

...
| make[1]: *** [Makefile:22530: test/asn1_dsa_internal_test] Error 1
| collect2: error: ld returned 1 exit status
| make[1]: *** [Makefile:22500: test/algorithmid_test] Error 1
| collect2: error: ld returned 1 exit status
| make[1]: Leaving directory '/home/miha/stm/yocto/build/tmp/work/cortexm7-poky-linux-musleabi/openssl/3.0.8-r0/build'
| make[1]: *** [Makefile:5263: libcrypto.so.3] Error 1
| make: *** [Makefile:3245: build_sw] Error 2
| ERROR: oe_runmake failed

This is a known issue:
https://lists.yoctoproject.org/g/yocto/topic/98824124#60005
Right now only the BSP and basic initramfs are building.
This requires external uclibc toolchains to work properly with cortex m7

Managed to build the fitimage with kas-container, flashed, and when booting I get (maybe because of missing initramfs):
[    1.156675] This architecture does not have kernel memory protection.
[    1.163142] Run /init as init process
[    1.166850]   with arguments:
[    1.169830]     /init
[    1.172103]   with environment:
[    1.175284]     HOME=/
[    1.177657]     TERM=linux
[    1.217501]
[    1.217501] Unhandled exception: IPSR = 00000006 LR = fffffffd
[    1.224873] CPU: 0 PID: 1 Comm: init Not tainted 6.3.0 #1
[    1.230266] Hardware name: STM32 (Device Tree Support)
[    1.235416] PC is at 0xc0658a3c
[    1.238525] LR is at 0xc0658a19
[    1.241737] pc : [<c0658a3c>]    lr : [<c0658a19>]    psr: 61000000
[    1.248017] sp : c053fd20  ip : 00000019  fp : 00000000
[    1.253273] r10: c0479d80  r9 : 00000002  r8 : 84837bf8
[    1.258431] r7 : c053fe40  r6 : c053fee0  r5 : c053fefc  r4 : c069d588
[    1.265024] r3 : 00000000  r2 : c053ff7c  r1 : c053fd58  r0 : c053ff84
[    1.271615] xPSR: 61000000

@adrianalin check the first answer it's explained there !


Update helpers.js

Correction to an assumed typo, which causes twitching movement (stop and go) in random patrol.

def a typo, thanks for catching it


Sm/mpd-push

What does this PR do?
[draft until https://github.com/forcedotcom/source-tracking/pull/53 merges]
new option in sfdx-project.json for pushPackageDirectoriesSequentially
use new STL logic for byPkgDir
iterate array of  componentSets for push
NUT for asserting how many deploys happened from the org
What issues does this PR fix or reference?
@W-10146239@
QA notes:
top-level boolean prop pushPackageDirectoriesSequentially on sfdx-project.json
use this updated push command to QA the STL changes
I used https://github.com/salesforcecli/sample-project-multiple-packages as a test repo
check what happens with duplicate files in json output from subsequent deployments--do you get duplicates?  Is that different from toolbelt or the same?
testing ideas that I didn't try
examining hook output (should fire once for each directory)
check source tracking files (source:status) on an mpd deployment
check pushPackageDirectoriesSequentially when there's only one pkgDirectory
test the human (non-json) output with a MPD project...the messages and fileResponses should all merge into one table across all the deploys
have a failure on any one pkgDir...it should stop any other deployments from happening.

combining these changes into https://github.com/salesforcecli/plugin-source/pull/325


[BUG]: Activate the Sync Template flows steps doesn't work

Describe the bug
when try to follow Activate the Sync Template flows steps from documentation. it givens and error listed in screenshot
Component (please tell us which flow or app you are experiencing issues with):

Solution Core

To Reproduce
Steps to reproduce the behavior:

Follow steps in "Active the sync template" section - Here is link to doc https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components

Expected behavior
it shows allow to follow that step
Screenshots
attached
Additional context
None

Hello,
are you using the latest version of the CoE Starter Kit? Please make sure you download  the latest version of the kit as this issue was addressed and fixed there.
Thanks for using the CoE Starter Kit,
Manuela

Yes , Version 1.53 of the Core Components.

Seeing the same error on different flows. Screenshot attached.

That is correct, I get similar error on another flow. I am using 1.53 version

Rather than doing a save-as, can you please edit the flow and reconnect the connectors there? Go to the settings and see what the pagination setting is for the gets. Here is one you can use to find:

The threshold is set to 5000

Can you please enable the flow using this methodology (enable all these connectors instead of save as) and see if the flow runs?

for me, it is not the case, it shows this and I see settings disable. I am global admin

Sachdesai, you need to add a new connection first.

I did but still it gives same message, anyone available to troubleshoot this live?

Our support model does not afford us to do calls with our GitHub users unfortunately.
When you say it gives the same message, what do you mean. Can you share a screenshot?
I'm hoping you guys can change the value down (try 2,000 for example) and see where you are allowed to use/save as the flow.

Hello @Sachdesai,
can you please find this action in the Flow called "Find connector record", it's under the "apply to each connector" loop and go the ... > Settings > and change the Pagination there to 5000. It will currently be set to 10000. Looks like we missed one action when we reduced the pagination for all.

I tried to do that today, here is message it gives

It looks like one of your connections is not authorised.
Look for a Flow step with an exclamation mark on it.
From: Sachdesai<EMAIL_ADDRESS>Sent: 27 July 2020 17:06
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: Activate the Sync Template flows steps doesn't work - pagination issue (#382)
I tried to do that today, here is message it gives
[image]https://user-images.githubusercontent.com/31678434/88564688-826dcc80-d001-11ea-9c1c-87f939a106b6.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/382#issuecomment-664488297, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUBB7VSSOEQTTUJOQPTR5WQXDANCNFSM4PCRX7JA.

Yeah, somehow I don't see that, there were few triangle but after adding connection, it goes away

Hi
They must be there somewhere or else you would not get the message.
I suggest you expand all of the workflow steps.  You should then find where the unauthorised connections are.
I would certainly expand the switch statement (The one which is grey)
Regards
Nigel
From: Sachdesai<EMAIL_ADDRESS>Sent: 27 July 2020 18:04
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: Activate the Sync Template flows steps doesn't work - pagination issue (#382)
Yeah, somehow I don't see that, there were few triangle but after adding connection, it goes away
[image]https://user-images.githubusercontent.com/31678434/88570110-84d42480-d009-11ea-91ae-6c2fce89eace.png
[image]https://user-images.githubusercontent.com/31678434/88570132-8d2c5f80-d009-11ea-8ea0-1d761284de38.png
[image]https://user-images.githubusercontent.com/31678434/88570149-95849a80-d009-11ea-829b-978472944e6d.png
[image]https://user-images.githubusercontent.com/31678434/88570165-9ae1e500-d009-11ea-9936-9e47bc944938.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/382#issuecomment-664519676, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUCQOGCBNNBJKOS4AMTR5WXQLANCNFSM4PCRX7JA.

It was issue with Flow license. Once flow license is assigned to admin, it solved all this issue.

Thank you for following up with us on the resolution, and for using CoE!


Automate generating verified results

If it is possible to somehow automatically generate the verified results that would save me a lot of time and allows me to update the site far quicker and more often.
I've looked at BrowserStack and they offer Selenium integration. That means it is possible to create a script that opens html5test.com on all of their different browsers and submit those results back to our server using a secret key. The processing on the site would be fairly trivial.
This still requires adding some missing results manually, because not all browsers are on BrowserStack, but it would allow the site to launch with meaningful data right away and we don't have to wait for weeks to collect data from visitors.

I've send a request for an account to @BrowserStack.

Got a positive response back from BrowserStack, so it looks like this will be doable.
I want to make this an automated tool that:
a) fetches all available browsers from BrowserStack
b) fetches a list of browsers that do not have any confirmed results from HTML5test
c) determines based on a) and b) what tests can be run and run them
Running a tests works like this:
a) get an id from the HTML5test API
b) use php-webdriver to load html5test.com with the id as parameter
c) poll the HTML5test API to see if we received a report with the id
d) show an error or send an e-mail when the test fails
e) continue with the next one
The idea is that this will be a command line tool, that could even be run automatically using cron.

The initial version of this tools is now ready and used it generate 800+ results:
https://github.com/WebPlatformTest/Automation
Still needed:

nominate automated reports as a confirmed score.
auto update the browser data

Remaining issues are now handled by:
https://github.com/WebPlatformTest/Data


Windowing operators

Adding code snippets to the windowing documentation

Hi @davidselassie @awmatheson and @whoahbot
Added a few sample code snippets to the windowing operator API documentation
Before I add more, I want to gauge if I am moving in a good direction or if there are other areas I can explore or you'd like showed in the code snippets.

Hi everyone,
Dan and I had a chance to chat and go over the examples - I got a good to continue.
Will add more code snippets for the remaining windowing operators


Testing this feature

Game-changing? Hum... Let's see...

How fast can this delivery?

 You need to try! Hahaha

How fast can this delivery?

 You need to try! Hahaha @dizys

Pretty fast I would say. But there seems to be some caching problem when going from the issue page back to the list.

This IS game changing!


npm install -d failure

npm info it worked if it ends with ok
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm ERR! Couldn't read dependencies.
npm ERR! Error: ENOENT, No such file or directory '/root/package.json'
npm ERR! Report this entire log at:
npm ERR!     http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR<EMAIL_ADDRESS>npm ERR!
npm ERR! System Linux <IP_ADDRESS>-rscloud
npm ERR! command "node" "/usr/local/bin/npm" "install" "-d"
npm ERR! cwd /root
npm ERR! node -v v0.5.9-pre
npm ERR! npm -v 1.0.94
npm ERR! path /root/package.json
npm ERR! code ENOENT
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /root/npm-debug.log
npm not ok

Please read npm help install.  I'm not sure what you expected that to do.


PROD SUPPORT : FSO not able to see documents in Firefox. It became working when we login to Google Chrome

Describe the bug
FSO not able to see documents in Firefox. It became working when we login to Google Chrome

Hi @Susmitabe, @rajeshcherukumalli, @Ramu-kandimalla
Working Fine in UAT
Refer Screenshots

Hi @Susmitabe  Please verify and confirm

resolved


Use prompt_toolkit instead of readline

https://github.com/jonathanslenders/python-prompt-toolkit

Thank you very much for this link! Really, I've been searching for this for so long :D

Everything goes wrong after clear command. I will use colors for prompt from prompt_toolkit itself instead

Now everything works fine


Add support of keyword arguments.

Thank @keizo042 and @ksss for sending me Ruby Under a Microscope via amazon.co.jp. The book helped a lot to start implementing this.
This PR isn't squashed since its modification is too big and may need more changes.

The parser is mostly ported from CRuby's parse.y. Thanks to CRuby developers.

Though AST generating is completely different since data structure of mruby AST is different from CRuby.

Most test from ruby/spec is passing.
Before Optimize keyword arguments., I've implemented handling keyword arguments only with Hash.

After adding OP_SENDK, it uses Array to handle passed keyword arguments instead. Though the old way is still used to handle arguments with OP_SEND or OP_SENDB opcode.
struct mrb_callinfo size is increased for optimization.
I've re-reduced size of mrb_callinfo by reducing size of acc field since it's always 9-bit integer(GETARG_A). Thanks to @miura1729 for some advice.
And kwds is removed since it's value is from kdict.

Some codedump.c improvements is added to know what is on the stack.

Name block, rest arguments, keyword rest arguments with &, *, ** when there is no specific variable name.
Print local variable names with VM code dumps.

This PR breaks VM compatibilities mostly in 4 opcodes(3 new and 1 changed).

OP_KARG and OP_KDICT's behavior is changed from the previous documentation to make keyword arguments handling easier. See updated documents for detail.
OP_SENDK is added to call method with optimized keyword arguments passing.

Instead of building hash, it creates array of keyword symbol and value pairs terminated with nil object.
In OP_KARG keyword is linear searched instead of mrb_hash_get.

OP_ENTER's arguments specifier's layout has changed. And now maybe it's got a big VM instruction.

In old layout there was no difference between required keyword and keyword with default argument.
Post required arguments is decreased to 4 bit(max: 31 -> 15).
Required keyword arguments and optional keyword arguments is 3 bit (max: 7) each.
After changing it I've noticed that adding another opcode like OP_ENTERK may make VM compatible.

Differences between CRuby:

Hash#fetch(implemented in mruby-hash-ext), Hash#delete, Hash#key? isn't used to handle keyword arguments. So Hash methods overwriting example in Ruby Under a Microscope can't be reproduced in this implementation.

mrb_get_args can only handle keyword arguments with last hash argument.

Should we add another C API equivalent to OP_KARG and OP_KDICT?.

Great works!
I fount some incompatibility with CRuby.
$ ruby -e 'p ->(a:){}.arity'
1

$ mruby -e 'p ->(a:){}.arity'
0

$ ruby -e 'p ->(a:1){}.arity'
-1

$ mruby -e 'p ->(a:1){}.arity'
0

$ ruby -e 'p ->(**){}.arity'
-1

$ mruby -e 'p ->(**){}.arity'
0

$ ruby -e 'p ->(a, b:){}.call(1, b: 2)'
nil

$ mruby -e 'p ->(a, b:){}.call(1, b: 2)'
trace:
	[0] -e:1
-e:1: unhandled keyword arguments found: {:b=>2} (ArgumentError)

@ksss @miura1729
Fixed some bugs and add some improvements mrb_callinfo.

@take-cheeze I found another bugs may about GC.
$ ruby -e 'p ->(a:, **k) { [a, k] }.call(a: 1, b: 2, c: 3)'
[1, {:b=>2, :c=>3}]

$ mruby -e 'p ->(a:, **k) { [a, k] }.call(a: 1, b: 2, c: 3)'
[1, {:b=>2}]

And interpretation for argument.
$ ruby -e 'p ->(a = nil, **k) { [a, k] }.call({a: 1}, {})'
[{:a=>1}, {}]

$ mruby -e 'p ->(a = nil, **k) { [a, k] }.call({a: 1}, {})'
trace:
	[0] -e:1
-e:1: 'call': wrong number of arguments (2 for 0) (ArgumentError)

mruby: e7bab50a
build_config.rb
MRuby::Build.new do |conf|
  toolchain :gcc
  enable_debug
  conf.gembox 'default'
  conf.cc.defines << %w(MRB_GC_STRESS)
end

@ksss Should be fixed with updates.

@take-cheeze Great!
I found more diffs. (using fedae3f)
$ cat t.rb
p ["-> (a:, b:) { }.arity", -> (a:, b:) { }.arity]
p ["-> (a, b, c:, d: 1) { }.arity", -> (a, b, c:, d: 1) { }.arity]
p ["-> (a, b=1, *c, d:, e:, f: 2, **k, &l) { }.arity", -> (a, b=1, *c, d:, e:, f: 2, **k, &l) { }.arity]

$ ruby t.rb
["-> (a:, b:) { }.arity", 1]
["-> (a, b, c:, d: 1) { }.arity", 3]
["-> (a, b=1, *c, d:, e:, f: 2, **k, &l) { }.arity", -3]

$ mruby t.rb
["-> (a:, b:) { }.arity", 2]
["-> (a, b, c:, d: 1) { }.arity", -4]
["-> (a, b=1, *c, d:, e:, f: 2, **k, &l) { }.arity", -4]

@ksss I should read description of Proc#arity more closely.
Should be fixed with update.

@take-cheeze Thank you for responding.
I could't find bugs about kw_args anymore!

@ksss That's nice!
Thank you for many reviews!

Rebased and fixed a GC issue in C function.

@matz @take-cheeze What's the status about keyword arguments? It was announced that they will arrive with 1.4.0 and 1.4.1 is out already but without them.

@katzer I don't know the detailed progress but this can't be applied without an incompatible changes to VM instructions so I'm waiting for the new VM instruction sets to come.

We are going to make big changes in the next release and name it mruby 2.0!
The keyword arguments will be among those changes.  It is working on my machine.

Whats the big picture for mruby 2.0?

The current plan is:

bytecode, instead of word instruction
new mrb binary format
keyword arguments

That sounds all great, however what about better threading support?

@katzer Unfortunately there's no plan for the better threading support. Some platforms mruby supports do not provide threading functionality (e.g. small devices without OS). That means mruby cannot support threading by the core, which is needed for the better treading support, in my opinion.

Since the keyword argument is merged in the mruby2-draft branch, I close this issue.


Fix issue #20264 Lrt.lt site redesign

Fixes the issue ytdl-org/youtube-dl#20264
As part of the fix the following changes were made to video attributes:

duration - removed
view_count - removed
like_count - removed
release_date - added

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense -
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix - updated existing extractor after the site redesign
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
LRT.lt had an existing extractor. The site has been redesigned (approximately in Feb 2019) which broke the extractor. The website lrt.lt now has a JSON API to get the details about the media file and the reference to the m3u8 file.
The existing extractor has been updated.

I can confirm that this works as it should. Please merge :)


how to pod target to >= (9.0.0)

<!--
I am using Xcode 9.0 & cocoapod. My project pod file mentioned : pod 'Moya'
but when I start with pod install it always install pod with Using Moya (8.0.3)
when I am trying to pod 'Moya', '~ 9.0.0' it gives me error like - `Moya (~> 9.0.0)` required by `Podfile` How to get latest pod 9.0 from pod install commands?

I am using Xcode 9.0, swift 4.0. and cocoapod. My pod file mentioned pod 'Moya' but when I start with pod install it always downloaded 'Using Moya (8.0.3)', how can I update to latest moya 9.0?

Hey @mwapptest,
Can you do pod update and then try pod install again?

1.pod repo update;
2.pod install,
work well for me

it works now, thanks @Lixyss  & @SD10


Support Vendoring Deno Deps

We might want to vendor deno dependencies for production environments, and we can ensure that the scripts don't reach out in production for deps by adding support for --no-remote to the run command.
For more information.
<EMAIL_ADDRESS>

We also need to support --import-map to force using vendor resources.


Increase size of Reason

On the account request page, increase the size of the 'Reason' field. It is currently '50'. Perhaps make this a text area that is 3 lines by 50-80 chars?
Imported from trac ticket #98,  created by ahelsing on 01-12-2015 at 15:59, last modified: 01-12-2015 at 15:59

Field may be called 'purpose'.  Add text encouraging people to provide enough input so that we can make an intelligent decision.

Complete. 3 lines by 50 columns. Alignment is a bit off, maybe a CSS wizard can fix that.