update-ca-certificates fails

When run under Docker, update-ca-certificates (from the package ca-certificates) fails with the line . All the information I can find seems to suggest it's a locale issue but the system profile seems to have the correct information. Any ideas?
The failure:
bash-4.3# update-ca-certificates
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping

That isn't necessarily a failure. It is just saying "the ca-certificates.crt file has multiple certificates so we are not considering it to be symlinked". What is the actual problem here? Do you have an example I can try to reproduce?

sure, CiscoCloud/nginx-consul (currently on the Docker registry as asteris/nginx-consul.) If you mount a directory with CA certs in the place mentioned in the README and run update-ca-certificates that happens. Am I misunderstanding the package instructions?

Do you have an example CA PEM or a command I can use to generate one? I'll see if I can reproduce.
To clarify: the CA is not getting added to the ca-certificates.crt file regardless of the error message?

correct. I don't have one, but you can get one by running the security-setup script in CiscoCloud/microservices-infrastructure.

Indeed, looks like an upstream bug. The line at https://github.com/alpinelinux/aports/blob/master/main/ca-certificates/update-ca-certificates#L50 should be for key,fn in pairs(certlist) do. I'll poke upstream and try to get a patch out.

Great, thank you!

Patch submitted: http://patchwork.alpinelinux.org/patch/104/.

Merged in https://github.com/alpinelinux/aports/commit/3faf2e032027ffa255f9a49f2f17c8e0239173ff. New package pushed to edge. Give it a try and let me know if we can close this.

This fix should also be in Alpine 3.2 as well. We just pushed a new 3.2 tag. Reopen if still an issue.

Issue still reproduce with the last docker image.
apk update && apk install curl ca-certificates \
&& curl https://www.gandi.net/static/CAs/GandiStandardSSLCA2.pem -o /usr/local/share/ca-certificates/GandiStandardSSLCA2.crt \
&& update-ca-certificates
/#  WARNING: ca-cert-GandiStandardSSLCA2.pem does not contain exactly one certificate or CRL: skipping

This looks to be an issue in alpine:3.3:
/ # apk add ca-certificates
OK: 28 MiB in 31 packages
/ # update-ca-certificates
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping

What specifically is the issue?

On second inspection, I don't think ca-certificates is the root of my issue, but it may be worth patching anyhow (that's obviously at your discretion).

The warning is just a warning. It doesn't affect anything.

FROM alpine:3.5

RUN apk add --no-cache ca-certificates && \
    update-ca-certificates

WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
The message says that something is skipped. It makes an impression that user get incomplete set of root certificates. Could you, please, rephrase, remove or fix this message, so people are not getting confused about the message?

This should be brought up on http://bugs.alpinelinux.org/projects/alpine/issues. It comes from the utility in the ca-certificates package at https://git.alpinelinux.org/cgit/aports/tree/main/ca-certificates/c_rehash.c#n210. I agree, the warning could be better or ignored altogether if the file is ca-certificates.crt.

+1

@adolphlwq, your "+1" comment doesn't really give us any new information.
If you're experiencing the same issue, have none of the above comments helped? As @andyshinn noted two full moons ago, this issue doesn't really belong here.

@andyshinn mentioned that this is just a warning and shouldn't affect anything. However, update-ca-certificates is exiting with code '1', and I took some time to find out why my command list was failing...

What about this guys:
FROM alpine:3.7

RUN apk update \
    && apk upgrade \
    && apk add --no-cache \
        ca-certificates \
    && update-ca-certificates 2>/dev/null || true

I think it's great for a workaround, but the command shouldn't exit 1 on a warning. Or we should be able to ignore warnings. I have implemented this workaround in my Dockerfile, but I don't think I can really assume  that everything is fine certificate wise anymore.

This still doesn't work (produces the warning, doesn't add stuff to /etc/ssl/certs/ca-certificates.crt) with alpine 3.9:
COPY ca-cert-XXX.pem /etc/ssl/certs/
update-ca-certificates

my workaround:
COPY ca-cert-XXX.pem /etc/ssl/certs/
RUN cat ca-cert-XXX.pem >> /etc/ssl/certs/ca-certificates.crt

@andyshinn so shouldn't the issue be reopened?

Just ran into this today, not able to add a CA.

This is still a problem

How I can verify that my cert has been actually imported into the ca-certs?

@da3mon-01 it should get appended to /etc/ssl/certs/ca-certificates.crt

I think there are two separate issues here, stemming from the same root cause. It looks like update-ca-certificates skips any PEM file in /usr/local/share/ca-certificates if it contains more than one certificate.
If you only get a warning about ca-certificates.crt it's harmless, but if you just added a new PEM file and you want to import it (e.g. the RDS certificate chain), you will get a warning for that file, and the certificates will not be imported. Confusing.
The workaround I found is to split the new PEM file into individual files first, one per certificate:
cd "/usr/local/share/ca-certificates" && curl "https://s3.amazonaws.com/rds-downloads/rds-combined-ca-bundle.pem" | csplit -f "rds-" - '/-----BEGIN CERTIFICATE-----/' '{*}'`

Months later, still a problem.  Issue should not be closed.

WARNING: nothing is wrong
The message above should be either reworded so it makes sense or removed. It's useless and people, like me, are wasting their time trying to figure out what it means.

Apparently, I am also experiencing the very same issue. I dont know how to approach to solve it.
root@animeVPS:~# wget https://rclone.org/install.sh
Connecting to rclone.org (<IP_ADDRESS>:443)
wget: SSL/TLS certificate is not being validated!

root@animeVPS:~# update-ca-certificates
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping

root@animeVPS:~# apk update
fetch http://dl-cdn.alpinelinux.org/alpine/v3.5/main/x86/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.5/community/x86/APKINDEX.tar.gz
v3.5.3-45-g195c4dea45 [http://dl-cdn.alpinelinux.org/alpine/v3.5/main]
v3.5.3-44-g08ec10f083 [http://dl-cdn.alpinelinux.org/alpine/v3.5/community]
OK: 7924 distinct packages available

root@animeVPS:~# apk add ca-certificates
OK: 468 MiB in 138 packages

root@animeVPS:~# update-ca-certificates
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping

# ---- Not a server side Issue? ----

root@animeVPS:~# wget --no-check-certificate https://rclone.org/install.sh
Connecting to rclone.org (<IP_ADDRESS>:443)
wget: error getting response: Connection reset by peer

#--- this might be unrelated but still worth taking a look? ---

root@animeVPS:~# apk add curl-dev
ERROR: unsatisfiable constraints:
  libressl-dev-2.4.4-r0:
    conflicts: openssl-dev-1.0.2q-r0[pc:libcrypto=2.4.4] openssl-dev-1.0.2q-r0[pc:libssl=2.4.4] openssl-dev-1.0.2q-r0[pc:openssl=2.4.4]
    satisfies: libssh2-dev-1.7.0-r2[libressl-dev] libssh2-dev-1.7.0-r2[pc:libcrypto] libssh2-dev-1.7.0-r2[pc:libssl] curl-dev-7.61.1-r1[libressl-dev]
  openssl-dev-1.0.2q-r0:
    conflicts: libressl-dev-2.4.4-r0[pc:libcrypto=1.0.2q] libressl-dev-2.4.4-r0[pc:libssl=1.0.2q] libressl-dev-2.4.4-r0[pc:openssl=1.0.2q]
    satisfies: world[openssl-dev] libssh2-dev-1.7.0-r2[pc:libcrypto] libssh2-dev-1.7.0-r2[pc:libssl]

Problem still exists

/ # mv DigiCertSHA2SecureServerCA.crt.pem /usr/local/share/ca-certificates/DigiCertSHA2SecureServerCA.crt / # update-ca-certificates WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
I'm running this in the image itself and get that warning, and I don't know if my certificates are updated or not.

Just don't use Alpine & Docker. Nobody cares if you shave 100 MB off an image. 2 hours of your work is a terabyte disk.

Message is misleading, but it's only a warning. It doesn't mean it failed to run update-ca-certificates as according to exit code, it did succeed if it continues to next step.
In case you have access to python inside your docker image and really want to make sure the certificate was correctly added, here's an example with a verification.
ARG CERT_SOURCE=https://s3.amazonaws.com/rds-downloads/rds-combined-ca-bundle.pem
ARG CERT_DESTINATION=/usr/local/share/ca-certificates/rds-combined-ca-bundle.pem

ADD $CERT_SOURCE $CERT_DESTINATION
RUN update-ca-certificates
RUN python -c "x=open('$CERT_DESTINATION').read(); y=open('/etc/ssl/certs/ca-certificates.crt').read(); exit(0) if x in y else exit(-1)"

Python trick comes from https://unix.stackexchange.com/a/114882/63222 and was adapted to fail if file doesn't contain other file.
But at this point, it's probably easier to append the bundle directly to /etc/ssl/certs/ca-certificates.crt like this:
ARG CERT_SOURCE=https://s3.amazonaws.com/rds-downloads/rds-combined-ca-bundle.pem
ARG CERT_DESTINATION=/usr/local/share/ca-certificates/rds-combined-ca-bundle.pem

ADD $CERT_SOURCE $CERT_DESTINATION
RUN cat $CERT_DESTINATION >> /etc/ssl/certs/ca-certificates.crt

I have looked into this a bit closer.
The reason for this warning is the c_rehash program that runs at the very end of update-ca-certificates. Its purpose is to (re)generate the hash symlinks in /etc/ssl/certs. This is only possible if a file contains a single certificate (or revocation list).
When c_rehash encountersca-certificates.crt which contains the concatenation of all certificates, it rightly complains that this file cannot be hashed. But as noted above, this is indeed just a warning and the update of the certificates did work.
Source: https://git.alpinelinux.org/ca-certificates/
I suggest to close this issue.

It may be a warning, but why the message skipping. This is misleading as others have commented.

but why does the message include skipping

Because the file mentioned contains more than one certificate and thus can't be hashed. This is output from c_rehash.

The issue still persists. I get the warning both for a cert and the store file:
Reproduce:

Try to install cert
 /etc/ssl/certs # update-ca-certificates
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
WARNING: ca-cert-<DOMAIN>.<TLD>.pem does not contain exactly one certificate or CRL: skipping

Checking, if the cert was added to the store: The solution by @GabLeRoux is good, but probably an overkill. There's no need for python in your container: Alpine Linux ships with comm (a reverse diff):
comm -12 /etc/ssl/certs/ca-cert-<DOMAIN>.<TLD>.pem  /etc/ssl/certs/ca-certificates.crt

The result, that you should see if the cert was added to the ca-certificates.crt-store is:
-----BEGIN CERTIFICATE-----

…or nothing. If you see a complete cert, then it tells you that the cert wasn't successfully added.
In my case, the cert was added, still the WARNING about the single cert is there.

Try to fetch from a local URl:
/etc/ssl/certs # wget -qO- http://<IP_ADDRESS>/nginx_status
ssl_client: <DOMAIN>.<TLD>: certificate verification failed: unable to get local issuer certificate
wget: error getting response: Connection reset by peer

Ignore the cert for a wget call. Does not work for other connections where you do not have access to request args:
/etc/ssl/certs # wget --no-check-certificate -qO- http://<IP_ADDRESS>/nginx_status
Active connections: 1
server accepts handled requests
10 10 8
Reading: 0 Writing: 1 Waiting: 0

The issue still persists. I get the warning both for a cert and the store file:
Reproduce:

Try to install cert
 /etc/ssl/certs # update-ca-certificates
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
WARNING: ca-cert-<DOMAIN>.<TLD>.pem does not contain exactly one certificate or CRL: skipping

Checking, if the cert was added to the store: The solution by @GabLeRoux is good, but probably an overkill. There's no need for python in your container: Alpine Linux ships with comm (a reverse diff):
comm -12 /etc/ssl/certs/ca-cert-<DOMAIN>.<TLD>.pem  /etc/ssl/certs/ca-certificates.crt

The result, that you should see if the cert was added to the ca-certificates.crt-store is:
-----BEGIN CERTIFICATE-----

…or nothing. If you see a complete cert, then it tells you that the cert wasn't successfully added.
In my case, the cert was added, still the WARNING about the single cert is there.

Try to fetch from a local URl:
/etc/ssl/certs # wget -qO- http://<IP_ADDRESS>/nginx_status
ssl_client: <DOMAIN>.<TLD>: certificate verification failed: unable to get local issuer certificate
wget: error getting response: Connection reset by peer

Ignore the cert for a wget call. Does not work for other connections where you do not have access to request args:
/etc/ssl/certs # wget --no-check-certificate -qO- http://<IP_ADDRESS>/nginx_status
Active connections: 1
server accepts handled requests
10 10 8
Reading: 0 Writing: 1 Waiting: 0

@franz-josef-kaiser that is another issue, your cert ca-cert-<DOMAIN>.<TLD>.pem is skipped from rehashing because it didn't contain exactly one cert or CRL (like the message says).
ca-certificates.crt isn't really used. Instead a certificate is looked up by its hash - a symlink like fe8a2cd8.0. These symlinks are created by the program c_rehash which is invoked as part of update-ca-certificates. And that's where the warnings come from.
The warning about the bundle is really just a warning though. It's because update-ca-certificates is writing the bundle before invoking c_rehash /etc/ssl/certs/. I've submitted a PR#1 to Alpine to address this. Just tested and seems to be working fine.
~ # update-ca-certificates
~ #

@franz-josef-kaiser that is another issue, your cert ca-cert-<DOMAIN>.<TLD>.pem is skipped from rehashing because it didn't contain exactly one cert or CRL (like the message says).
ca-certificates.crt isn't really used. Instead a certificate is looked up by its hash - a symlink like fe8a2cd8.0. These symlinks are created by the program c_rehash which is invoked as part of update-ca-certificates. And that's where the warnings come from.
The warning about the bundle is really just a warning though. It's because update-ca-certificates is writing the bundle before invoking c_rehash /etc/ssl/certs/. I've submitted a PR#1 to Alpine to address this. Just tested and seems to be working fine.
~ # update-ca-certificates
~ #

@rustyx Thanks for clarifying that (and submitting the PR to Alpine@GitLab)

Instead a certificate is looked up by its hash - a symlink like fe8a2cd8.0.

@rustyx Thanks for clarifying that (and submitting the PR to Alpine@GitLab)

Instead a certificate is looked up by its hash - a symlink like fe8a2cd8.0.

Still a problem, wow.

A problem.
FROM python:3.8-alpine
bash-5.1# update-ca-certificates WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping

The following warning is not an error. It's just how the command works: It checks all certs, including the main file, which contains more than one file. The error message just could be improved:
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping

It's much better if it outputs the result as normal linux, then we know the cert has been added, so it's just a warning. At first glance at this warning and no other outputs, I thought it did not add the cert.
update-ca-certificates
Updating certificates in /etc/ssl/certs...
1 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

updates of cacerts keystore disabled.
done.

haha. oh my. still an issue all these years later.

@vitruvvius What have you contributed to fixing the issue?

First-time poster! Please excuse any informal etiquette.
I spent 2-hours troubleshoot a similar issue in Ubuntu, but was able to come up with a solution (my thought is maybe my findings could be helpful for others). First I started from scratch:

removed all entries and files related to my .crt file (find / -type f -name "[certname].*")
ran sudo update-ca-certificates --fresh
follow up on any loose ends (had to remove one line from  /etc/ca-certificates.conf)

Important:

Follow all the usual steps, up until running update-ca-certificates
Before running the updater, set the CA certificate file permissions to 644 (sudo chmod 644 ./file.crt). Originally, in my case, my certificate had 755 permissions
Run sudo update-ca-certificates

After running the update, the certificate was available.

Hi!
This is not Alpine, but I figure out my certificates files was using UTF-8 BOM y saved without BOM and certificates was included without warnings.
FROM node:14
COPY CPTTRootCertificateAuthority.crt /usr/local/share/ca-certificates/
COPY CPTTIntermediateCertificate.crt /usr/local/share/ca-certificates/
RUN update-ca-certificates

Maybe this comment is not useful, but works for me.

For what it's worth, the exit code for this warning now appears to be 0, fortunately:
bash-5.1# update-ca-certificates --fresh
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
bash-5.1# echo $?
0

I see this "warning" does not contain exactly one certificate or CRL
and then immediately try to use my supposedly newly trusted certificate to make a TLS connection using curl and it fails
curl: (60) SSL certificate problem: self signed certificate in certificate chain
So in my case it does seem the addition to the trust store was indeed skipped as well.
I guess results may vary depending on versions or some other lurking variable.

It seems the container recognizes my CA (docker:dind - which is alpine basically), and running update-ca-certificates shows nothing within the container, but the error everyone is talking about is constantly showing up on my gitlab CI jobs.
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping

@Acerinth I'm not sure honestly, though I managed to evade that warning somehow. I still mount the CA in the gitlab-runner config.toml as shown above, but I also build my own dind image.
FROM docker:dind

COPY CA.pem /usr/local/share/ca-certificates/ca.crt # <- IMPORTANT to be *.crt
RUN update-ca-certificates --fresh

Does anyone have a script that splits a single .pem file with multiple certificates in it into individual files?
That way I can actually import and trust them without the warning/skip?
I am encountering this "warning" again and would like all the certificates in my file to actually be imported and trusted.

Also, I am sorry. I think this is the wrong repo to report this issue.
So if you can point me to where to report the problem to the correct source repo, that would be appreciated as well.
I think skipping certs in a file should be an error, not a warning. (whether they are actually skipped or not is up for debate in this thread, but in some cases the warning about skipping actually does mean they are skipped and not added to the trust store)


Compatibility issue with python 2.7 fixed

@binoyudayan I would also add in the option for httponly and domain:
set_cookie(key, value='', max_age=None, expires=None, path='/', domain=None, secure=None, httponly=False, samesite=None)
Adding in domain would take care of subdomains that are all part of the root domain. See the relevant subdomain issue #36. I just don't know how to exclude certain subdomains. But otherwise, it would solve that problem.
See here for httponly:
https://www.cookiepro.com/knowledge/httponly-cookie/
It is a security mechanism and adding it would be helpful.

I would really advise you to upgrade to Python 3 rather than expecting libraries to support a Python version that has been end-of-life for more than 2 years now

The project has been updated to be more explicit about the supported versions. Python 2.7 is not one of those, so unfortunately I'll be closing this PR as wontfix.
We appreciate the effort to contribute a patch, but Python 2.7 has been end-of-life for a while now and maintaining this project is hard enough already without having to support multiple major Python versions.


Removing leading slash from import even when in global space

For #2813

master is reserved for features, please target your PR to 2.2

done, I was mislead by the label of issue

Thank you @kubawerlos.


Use base ruby image in Dockerfile & fix watcher

It seems that the watcher will not work without the
--force-polling option.

:+1: thanks!


make pdm support compatible with pdm 2.8

resolves #39

Does this break compatibility with previous lockfile versions? I don't think that's a blocker if so, just curious.

yes i think it does.

@jvolkman i just rebased and added another fix (pytorch has started to use pytorch%2bcpu instead of pytorch+cpu)
this fix seems to still work with latest pdm.
can we get this merged somehow?

Thanks for working on it @betaboon. I'll look at merging today.


Fix compilation for 32-bit Arm platforms

The existing Neon code makes use of some intrinsics which are only available on AArch64, so adjust these implementations to also work on Armv7 platforms.
Also introduce a new REAL_TARGET_AARCH64 macro to distinguish between 32-bit and 64-bit in new and existing Arm code.
Since these implementations require that Neon is available, also add -mfpu=neon to the compile line for these files. This necessitates removing the SIMD implementation files from LTO in the same way that is already done for the x86 kernels.

Thanks for incorporating my suggestions. From your code around enabling SVE/SVE2 I assume these extensions are not available for ARMv7 ? Then I think the split between ARM and AARCH64 for VVENC_TARGET_ARCH really makes sense.
Concerning the interaction between VVENC_ENABLE_X86_SIMD and VVENC_ENABLE_ARM_SIMD, my intention was that all combinations are possible. I know it worked at some point in time, but I am not sure about the current status. I will look into it, when your changes are merged.

Thanks for incorporating my suggestions. From your code around enabling SVE/SVE2 I assume these extensions are not available for ARMv7 ?

Your interpretation is correct. Both SVE and SVE2 are only available in the 64-bit architecture (available from Armv8.2-A and Armv9.0-A respectively).

Thanks for the MR @georges-arm and for the review @K-os

Concerning the interaction between VVENC_ENABLE_X86_SIMD and VVENC_ENABLE_ARM_SIMD, my intention was that all combinations are possible. I know it worked at some point in time, but I am not sure about the current status. I will look into it, when your changes are merged.

This should be fixed by #455. Thanks for confirming the intent here.


Create Initial To-Do List Application

Developer Checklist

[x] Adhered to the guidelines outlined in the README & Contributing file.
[x] Maintained the correct directory structure (e.g., ProjectName/...yourfiles).
[x] Please ensure to include a README file for enhanced project clarity.
[ ] Starred ⭐ the repository (optional).

Summary
_Its a todo app that lists the task and make check after completion and can delete also
_
Screenshot
_
.._
Live Project Link
the app is not live feel free to do so

Here's a revised response that acknowledges the improvements you've made and reflects a refined and organized project update:

Thank you for your feedback! I’ve implemented the suggestions to enhance the To-Do List application’s usability and code quality. Here’s an overview of the updates:

PR Renaming: Updated the PR title to be more descriptive, clearly reflecting the purpose of this update.
Enhanced Error Handling: The add_task function now includes robust error handling, preventing duplicate tasks and handling input validation for empty and whitespace-only entries, as well as optional task length limits.
Keyboard Shortcuts: Added keyboard shortcuts for easier accessibility: pressing "Enter" adds a new task, and pressing "Delete" removes completed tasks.

These changes aim to create a more polished, user-friendly experience, with streamlined functionality and improved code readability. Looking forward to any additional feedback!


Android Basics: Read and update data with Room

The Room and the Main branch don't build properly for me. Working from the Starter code, it stopped working, I believe, in the 7th section of Persist Data with Room.
E/LazyAlarmStore: Removed TIME_TICK alarm
E/WifiDataStall: onDataConnectionStateChanged unexpected State: 3
E/MboOceController: onDataConnectionStateChanged unexpected State: 3

Changed the room_version in the project build.gradle and that worked.
buildscript{
ext{
...
room_version = '2.4.0-alpha03'
}
repositories {

Fixed per above comment.

Closed


Refactor + Support for Square and Hexagon cells

The PR Includes:

Support for Hexagon and Squares, the shaper.js file has all the changes necessary logic to change when the shape is different.
Splitting the functions to events.js (currently has all the mouse events), plot.js (responsible for plotting and scaling the cartogram), export.js (To export the cartogram - expected to grow over time), constants.js (all the constants in one place), cartogram.js (Algorithm to distort the map to form a cartogram).


Missing support for BigInteger datatype

There is currently no support/overloads to create BigIntegers from c++ long/ulong values.
Is this planned or do I need to implement is myself using the v8 methods directly?
E.g. Node.js >10.4.0 has built in BigInteger support.

Closing as answered.


Remove references to Mapbox iOS examples

That's a lot of examples.

@ianthetechie I would say we do care, but we care more about getting this dead links removed for now. 😉
Thanks for taking a look!


glibc-2.30 libraries link to glibc-2.27

Describe the bug
The libraries in glibc-2.30 link to the libc from glibc-2.27
To Reproduce
$ ls -l $(nix-build --no-out-link -A glibc)/lib/libpthread-2.30.so
-r-xr-xr-x 1 root root 146088 Dec 31  1969 /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/libpthread-2.30.so
$ ldd $(nix-build --no-out-link -A glibc)/lib/libpthread-2.30.so
  linux-vdso.so.1 (0x00007fff2ffb9000)
  libc.so.6 => /nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/libc.so.6 (0x00007f7c9f4a3000)
  /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/ld-linux-x86-64.so.2 => /nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib64/ld-linux-x86-64.so.2 (0x00007f7c9f67c000)

Expected behavior
$ ldd $(nix-build --no-out-link -A glibc)/lib/libpthread-2.30.so
  linux-vdso.so.1 (0x00007fff2ffb9000)
  libc.so.6 => /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/libc.so.6 (0x00007f7c9f4a3000)
  /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/ld-linux-x86-64.so.2 => /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib64/ld-linux-x86-64.so.2 (0x00007f7c9f67c000)

Additional context
This seems to be the cause of a number of other problems, in particular symbols not being found when they should be, eg, when I try to run scripts in sublime3:
bash: relocation error: /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/libpthread.so.0: symbol __write_nocancel version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
The same error is reported in #79954. I think the fix for that (#80005) should be reverted because it seems like zoom-us still needs v4l. (My camera no longer works, for example.) However, I can't revert it locally because the glibc problem prevents v4l from pre-loading with zoom-us.
Metadata

system: "x86_64-linux"
host os: Linux 4.19.107, NixOS, 19.09.2346.85d879e5133 (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.3
channels(root): "nixos-19.09.2346.85d879e5133"
channels($USER): "nixpkgs-20.09pre218717.05f0934825c"
nixpkgs: /home/$USER/.nix-defexpr/channels/nixpkgs

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/go-no-go-meeting-nixos-20-03-markhor/6495/12

Is it possible that this is related to the bootstrap-files? When I run nix-build -A stdenv.bootstrapTools, I get a lot of libraries linked to 2.27 in the store-path. Since our glibc is built with the stuff from the bootstrap-tools IIRC, a regeneration of all bootstrap-files would solve this, right?

Cannot reproduce on master (cab6b019b17881f42f618dcc9fce9341f1a6df81). Trying with the following repro.nix:
let
  pkgs = import (fetchTarball {
    url = "https://github.com/NixOS/nixpkgs/tarball/cab6b019b17881f42f618dcc9fce9341f1a6df81";
    sha256 = "0gqh7yj9vlna6vrmrra75gwkwcbj5fshdp6jrw7y2s5l1aixn388";
  }) { system = "x86_64-linux"; overlays = []; config = {}; };
in pkgs.runCommandNoCC "repro-84043" {} ''
  ${pkgs.glibc.bin}/bin/ldd ${pkgs.glibc}/lib/libpthread-2.30.so > $out
''

Then
$ cat $(nix-build repro.nix)
  linux-vdso.so.1 (0x00007ffff7fd3000)
  libc.so.6 => /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/libc.so.6 (0x00007ffff7dee000)
  /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/ld-linux-x86-64.so.2 => /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib64/ld-linux-x86-64.so.2 (0x00007ffff7fd4000)

Hmm.... I actually can't either (on NixOS 20.03). This may be related to the fact that @neilmayhew is on 19.09 (which actively uses glibc-2.27).
@neilmayhew at which git-rev of nixpkgs did you run ldd $(nix-build --no-out-link -A glibc)/lib/libpthread-2.30.so?
However, it's getting late... unless someone's faster, I can take a look at this tomorrow :)

I was at 05f0934825c (see nix-info above).
However, I've just discovered something interesting. When I run the repro.nix above, I get the same results as @Infinisil (libc.so.6 resolves to glibc-2.30). However, when I run ldd on exactly the same file, from the same store path, I get a different result (libc.so.6 resolves to glibc-2.27). I unset LD_LIBRARY_PATH and that didn't make a difference. I assume it's because:
$ readlink -f $(which ldd)
/nix/store/hblpx8x5w88igmwa4ydnsnb65s363lji-glibc-2.27-bin/bin/ldd

This is because ldd is coming from my system environment (ie nixos-19.09) rather than from my profile. However, this works:
$ nix-shell -p glibc
$$ which ldd
/nix/store/c2lx3lsqp0y5kwvwkqma8iihc7xjj1m8-glibc-2.30-bin/bin/ldd
$$ ldd /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/libpthread-2.30.so
  linux-vdso.so.1 (0x00007fffedbd8000)
  libc.so.6 => /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/libc.so.6 (0x00007f9344423000)
  /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/ld-linux-x86-64.so.2 => /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib64/ld-linux-x86-64.so.2 (0x00007f9344605000)

Even so, I'm surprised that the path to libc6 isn't enforced by libpthread-2.30.so. In particular,
patchelf --print-rpath /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/libpthread-2.30.so
(empty output)

So there is no rpath. This is confirmed by running readelf -d. Is this normal for glibc libs?

So, this seems to be depending on the environment.
I just built a NixOS 19.09 VM (which uses glibc-2.27) and I could reproduce the issue.
I checkout out nixpkgs at 318f05f7761ded5dc0f5eab1d1787006c11b00be and built glibc like this:
[root@testvm:~/nixpkgs]# nix-build -A glibc
warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring
[ lots of downloads ]
/nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30

Right now, the issue is actually reproducible:
[root@testvm:~/nixpkgs]# ldd ./result/lib/libpthread.so
	linux-vdso.so.1 (0x00007ffc7d98a000)
	libc.so.6 => /nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/libc.so.6 (0x00007f2df349e000)
	/nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/ld-linux-x86-64.so.2 => /nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib64/ld-linux-x86-64.so.2 (0x00007f2df3677000)

However, when I change the environment with nix-shell -I nixpkgs=`pwd` -p, the issue disappears:
[nix-shell:~/nixpkgs]# ldd result/lib/libpthread.so
	linux-vdso.so.1 (0x00007ffe45771000)
	libc.so.6 => /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/libc.so.6 (0x00007f1d177c2000)
	/nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/ld-linux-x86-64.so.2 => /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib64/ld-linux-x86-64.so.2 (0x00007f1d179a4000)

This raises the following questions for me:

The issue only appears if you're on 19.09 and you try to use packages from 20.03 or unstable, right? (@domenkozar may I ask if that's the case in your setup as well?).
If that's right, I guess that this appears more often due to the big version jump (I helped out shipping this update and especially 2.28 and 2.29 seemed to have relatively many changes).
Isn't this issue 'fixable" by an upgrade to 20.03? (I couldn't reproduce this on 20.03 at least). In that case we should warn about this issue in our docs (and our release-notes) as this would reappear then after every glibc bump, right?
Can someone explain to me, why exactly this nix-shell -I nixpkgs=`pwd` -p hack works? I'm not sure, I understand entirely, why.

Yeah, it happens if you mix 19.09 and 20.03. For example my GHC is coming from 19.09, while ghcide is built with 20.03

So what do you all think about there being no rpath in glibc's libraries? Surely having an rpath is an essential part of the way Nix works? All other libraries seem to have it, and I don't understand why libpthread etc. would be different. Letting something as fundamental as glibc be affected by context seems like a bad idea to me.

Not sure yet since I'm wondering if that has been implemented that way for a reason. That's also why I asked if someone can explain why the nix-shell -I hack worked.

It works because nix-shell puts the bin directory of glibc-2.30-bin into PATH and so the ldd that you run is the one from glibc-2.30.
$ git checkout 318f05f
$ which ldd
/run/current-system/sw/bin/ldd
$ readlink -f $(which ldd)
/nix/store/hblpx8x5w88igmwa4ydnsnb65s363lji-glibc-2.27-bin/bin/ldd
$ nix-shell -I nixpkgs=`pwd` -p
$$ which ldd
/nix/store/c2lx3lsqp0y5kwvwkqma8iihc7xjj1m8-glibc-2.30-bin/bin/ldd
$$ echo $PATH | tr : \\n | grep glibc
/nix/store/c2lx3lsqp0y5kwvwkqma8iihc7xjj1m8-glibc-2.30-bin/bin
/nix/store/c2lx3lsqp0y5kwvwkqma8iihc7xjj1m8-glibc-2.30-bin/bin

Also, note that this is purely due to ldd and not to any environment variable. Outside nix-shell:
$ /nix/store/c2lx3lsqp0y5kwvwkqma8iihc7xjj1m8-glibc-2.30-bin/bin/ldd $(nix-build --no-link -I nixpkgs=`pwd` -A glibc)/lib/libpthread.so
  linux-vdso.so.1 (0x00007ffc41184000)
  libc.so.6 => /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/libc.so.6 (0x00007f4c67f73000)
  /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/ld-linux-x86-64.so.2 => /nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib64/ld-linux-x86-64.so.2 (0x00007f4c68155000)

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/go-no-go-meeting-nixos-20-03-markhor/6495/16

With LD_LIBRARY_PATH unset, these seem to be relevant parts of the trace:
7173  execve("/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib64/ld-linux-x86-64.so.2", ["/nix/store/wx1vk75bpdr65g6xwxbj4"..., "/nix/store/9rabxvqbv0vgjmydiv59w"...], 0x685008 /* 95 vars */) = 0
7173  brk(NULL)                         = 0x55555659b000
7173  openat(AT_FDCWD, "/nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30/lib/libpthread.so", O_RDONLY|O_CLOEXEC) = 3
7173  read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0 l\0\0\0\0\0\0"..., 832) = 832
7173  fstat(3, {st_mode=S_IFREG|0555, st_size=146088, ...}) = 0
7173  mmap(NULL, 131520, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fec1d1e7000
7173  mmap(0x7fec1d1ed000, 61440, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7fec1d1ed000
7173  mmap(0x7fec1d1fc000, 24576, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x15000) = 0x7fec1d1fc000
7173  mmap(0x7fec1d202000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a000) = 0x7fec1d202000
7173  mmap(0x7fec1d204000, 12736, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fec1d204000
7173  close(3)                          = 0
7173  access("/etc/ld-nix.so.preload", R_OK) = -1 ENOENT (No such file or directory)
7173  openat(AT_FDCWD, "/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
7173  openat(AT_FDCWD, "/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/tls/haswell/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
7173  stat("/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/tls/haswell/x86_64", 0x7ffe291a9e40) = -1 ENOENT (No such file or directory)
7173  openat(AT_FDCWD, "/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/tls/haswell/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
7173  stat("/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/tls/haswell", 0x7ffe291a9e40) = -1 ENOENT (No such file or directory)
7173  openat(AT_FDCWD, "/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/tls/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
7173  stat("/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/tls/x86_64", 0x7ffe291a9e40) = -1 ENOENT (No such file or directory)
7173  openat(AT_FDCWD, "/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/tls/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
7173  stat("/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/tls", 0x7ffe291a9e40) = -1 ENOENT (No such file or directory)
7173  openat(AT_FDCWD, "/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/haswell/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
7173  stat("/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/haswell/x86_64", 0x7ffe291a9e40) = -1 ENOENT (No such file or directory)
7173  openat(AT_FDCWD, "/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/haswell/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
7173  stat("/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/haswell", 0x7ffe291a9e40) = -1 ENOENT (No such file or directory)
7173  openat(AT_FDCWD, "/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
7173  stat("/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/x86_64", 0x7ffe291a9e40) = -1 ENOENT (No such file or directory)
7173  openat(AT_FDCWD, "/nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
7173  read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260,\2\0\0\0\0\0"..., 832) = 832

Unfortunately argv on the exec is truncated, but it seems like that argv[1] is the location of glibc-2.30/lib/libpthread.so.
So ld-linux-x86-64.so.2 reads libpthread.so and immediately starts looking for its dependencies in glibc-2.27. I assume in the absence of an LD_LIBRARY_PATH and an ld.so.cache it has to fall back on an internally-stored search path, which cannot include glibc-2.30. I don't see how this can possibly work correctly unless libpthread.so has a rpath.
Could somebody please, please tell me why it doesn't have an rpath?

(Add -s 256 to make it only truncate strings above length 256)

I have a one-word patch that fixes this(I think).
[132976][04:27:23][inv@nerif:/local/apps/senso/nixpkgs]$ git show HEAD
commit 4c656eb5ca5d34cafdec6429e37a71b203177e32 (HEAD -> ldd)
Author: Souvik Sen<EMAIL_ADDRESS>Date:   Wed Jan 29 04:14:09 2020 -0500
    glibc.bin: fix ldd output for binaries not compiled with same glibc
    Do not use the explicit dynamic linker this ldd was compiled with.
diff --git a/pkgs/development/libraries/glibc/common.nix b/pkgs/development/libraries/glibc/common.nix
index cdc5dab1be1..f382ba5b20b 100644
--- a/pkgs/development/libraries/glibc/common.nix
+++ b/pkgs/development/libraries/glibc/common.nix
@@ -98,6 +98,9 @@ stdenv.mkDerivation ({
       ./CVE-2018-11236.patch
       # https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=f51c8367685dc888a02f7304c729ed5277904aff
       ./CVE-2018-11237.patch
+
+      # instead of using the linker ldd was compiled with, use the linker the elf specifies
+      ./ldd-use-elf-linker.patch
     ]
     ++ lib.optionals stdenv.isx86_64 [
       ./fix-x64-abi.patch
diff --git a/pkgs/development/libraries/glibc/ldd-use-elf-linker.patch b/pkgs/development/libraries/glibc/ldd-use-elf-linker.patch
new file mode 100644
index<PHONE_NUMBER>0..747ffa49021
--- /dev/null
+++ b/pkgs/development/libraries/glibc/ldd-use-elf-linker.patch
@@ -0,0 +1,12 @@
+diff -Naur glibc-2.27-orig/elf/ldd.bash.in glibc-2.27/elf/ldd.bash.in
+--- glibc-2.27-orig/elf/ldd.bash.in    2020-01-29 02:17:45.881308184 -0500
++++ glibc-2.27/elf/ldd.bash.in 2020-01-29 02:45:38.057278876 -0500
+@@ -172,7 +172,7 @@
+       }
+       ;;
+     0|2)
+-      try_trace "$RTLD" "$file" || result=1
++      try_trace "$file" || result=1
+       ;;
+     *)
+       echo 'ldd:' ${RTLD} $"exited with unknown exit code" "($ret)" >&2

Wrong output similar to @neilmayhew, before the change.
[132976][04:22:41][inv@nerif:/local/apps/senso/nixpkgs]$ $(nix-build  /nix/var/nix/profiles/per-user/hydra/nixexprs-13000-link/nixpkgs -A glibc.bin)/bin/ldd  /nix/store/ajsrs4bhqclvz2kfv6i4scpv95rcj68z-python-2.7.17/bin/python | tail -1
        /nix/store/519r8kzr2zfyac7qwchlizhafw06wvy7-glibc-2.27/lib/ld-linux-x86-64.so.2 => /nix/store/xv86xix8vr7s1dlhaqdp5j2xdbbwcwgn-glibc-2.27/lib64/ld-linux-x86-64.so.2 (0x00007f4c5f533000)

After the change:
Note: "" does not have the patch, so it has a different glibc.
[132976][04:29:43][inv@nerif:/local/apps/senso/nixpkgs]$ $(nix-build -A glibc.bin)/bin/ldd $(nix-build "<nixpkgs>" -A python)/bin/python
        linux-vdso.so.1 (0x00007ffedc98f000)
        libgcc_s.so.1 => /nix/store/519r8kzr2zfyac7qwchlizhafw06wvy7-glibc-2.27/lib/libgcc_s.so.1 (0x00007f41f5157000)
        libpython2.7.so.1.0 => /nix/store/ajsrs4bhqclvz2kfv6i4scpv95rcj68z-python-2.7.17/lib/libpython2.7.so.1.0 (0x00007f41f4f43000)
        libpthread.so.0 => /nix/store/519r8kzr2zfyac7qwchlizhafw06wvy7-glibc-2.27/lib/libpthread.so.0 (0x00007f41f4f22000)
        libdl.so.2 => /nix/store/519r8kzr2zfyac7qwchlizhafw06wvy7-glibc-2.27/lib/libdl.so.2 (0x00007f41f4f1d000)
        libutil.so.1 => /nix/store/519r8kzr2zfyac7qwchlizhafw06wvy7-glibc-2.27/lib/libutil.so.1 (0x00007f41f4f18000)
        libm.so.6 => /nix/store/519r8kzr2zfyac7qwchlizhafw06wvy7-glibc-2.27/lib/libm.so.6 (0x00007f41f4d82000)
        libc.so.6 => /nix/store/519r8kzr2zfyac7qwchlizhafw06wvy7-glibc-2.27/lib/libc.so.6 (0x00007f41f4bca000)
        /nix/store/519r8kzr2zfyac7qwchlizhafw06wvy7-glibc-2.27/lib/ld-linux-x86-64.so.2 (0x00007f41f536f000)

It also works with impure stuff.
[132976][04:29:38][inv@nerif:/local/apps/senso/nixpkgs]$ $(nix-build -A glibc.bin)/bin/ldd /usr/local/bin/python # RHEL Python
        linux-vdso.so.1 =>  (0x00007ffcf8953000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f0c12287000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f0c12655000)

I think the problem isn't just with ldd, though. This library mismatch cause a number of things to break, as I mentioned in Additional Context.
I would much rather see glibc's .so's get an rpath.

It looks to me like several fixup hooks aren't running in the build of glibc. I don't know yet what's clobbering them.

OK, I see it now. default.nix has NIX_NO_SELF_RPATH = true. I assume a self-rpath is undesirable for libc.so but surely not for the other libs?

Would it work to remove NIX_NO_SELF_RPATH = true and instead use patchelf --remove-rpath libc6.so in postFixup?

I can't see how adding the RPATH is expected to help things.  When you're loading a libpthread, you surely have some version of lbc already loaded.  I don't think you can that easily have two glibc versions loaded at once anyway (in one process).

BTW, so far the most common impurity you get (on "desktop use", unless messing with things like $LD_LIBRARY_PATH yourself) comes from OpenGL, i.e. the /run/opengl-driver* path.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/glibc-problem-with-nixos-rebuild-when-switching-to-nixos-unstable-from-nixos-19-09/6664/1

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/xorgserver-upgrade-and-startx/6834/6

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/xorgserver-upgrade-and-startx/6834/9

I'm actually getting the exact same error with Ubuntu 18.04 when using haskell-language-server:
  Unexpected usage error
  /nix/store/7p1v1b6ys9fydg5kdqvr5mpr8svhwf4p-glibc-2.31/lib/libpthread.so: symbol __write_nocancel
  version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

Except instead of pointing to a libc in the nix store, it points to the one installed by Ubuntu:
$ ldd $(nix-build nixpkgs.nix -A glibc)/lib/libpthread-2.31.so
	linux-vdso.so.1 (0x00007ffca0dec000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3ae3cee000)
	/nix/store/7p1v1b6ys9fydg5kdqvr5mpr8svhwf4p-glibc-2.31/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007f3ae40df000)

Sadly, running the haskell-language-server-wrapper from that shell doesn't fix the error.
This sadly means that it not only happens to people running 19.09, but also people running other Linux OSes.

I suspect using Ubuntu's ldd on a library won't tell the story right.  There's no "interpreter" in *.so files (in the sense of patchelf --print-interpreter), and using a different one (Ubuntu's) won't produce the same result.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/how-do-i-pin-a-specific-version-of-glibc-using-shell-nix/11755/3

This appears to be a problem with Nim-lang. nix run nimble#about completes on NixOS built frome a recent master but fails on NixOS built from release-20.09.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/fhs-nix-shell-with-older-glibc-2-27-segfaults-on-basic-system-programs/13907/1

Still very much an issue - running into this when trying to pin glibc from nixpkgs.

I am having this issue. I have a shell.nix file where I am trying to pin nixpkgs. When I don't pin nixpkgs, I don't have this issue.


lump Ocean Currents, Tidal, Riverine into new Technology parent Currents tag to incorporate PRIMRe export of Tethys Publications

See 2022-02-18 Tethys Tag ∆s for Documents in notes | mhk-env - Google Docs.

In Google Sheet tabs tags and tag_lookup of data | marineenergy.app - Google Sheets:

Technology.Current

∆ Technology.Current -> Technology.Current.OceanCurrent
∆ Technology.Riverine -> Technology.Current.Riverine
∆ Technology.Tidal -> Technology.Current.Tidal

Fixed with commits:

merge · marineenergy/apps@bdc2c56
∆ Tech tags -> Current.OceanCurrent/.Tidal/.Riverine · marineenergy/apps@595af82

Hi Jonathan and all,
I updated the Technology tags in all content hosted at MarineEnergy.app to reflect this new hierarchy of Technologies (as the updated PRIMRE export of Tethys Publications):

Current -> Current/Ocean Current
Riverine -> Current/Riverine
Tidal -> Current/Tidal

When users look for Current/Tidal the Tethys Publications will be searched by Current and notified as much:

We would prefer to not loose the granularity of differentiating between these "Current" technologies. Could they either be included as a subheading or a separate API export?
We're noticing that "Technology" in the Tethys Engineering Glossary tends to conflate Resource type and Technology type according to OpenEI under Current:

Tethys Engineering Glossary

Technology
Current: Capturing energy from tidal channels, ocean currents, or rivers.

Axial Flow Turbine: Water flows parallel to the device's axis of rotation.
Cross Flow Turbine: Water flows perpendicular to the device's axis of rotation.
Oscillating Hydrofoil: Water induces oscillating translation of hydrodynamic surface.
Kite: A device that 'flies' in the tidal stream, swooping in a figure-eight shape.
Archimedes Screw: A helical surface surrounding a ventral cylindrical shaft.
Vortex-Induced Vibration: Constant water flow applied to a rounded object will cause vibrations.
Tidal: Capturing energy from tidal fluctuations using turbines, tidal barrages, or tidal lagoons.
Ocean Current: Capturing energy from ocean currents.
Riverine: Capturing energy from river currents.

OpenEI

Property:MREDeviceTechnologyType | Open Energy Information

Axial Flow Turbine
Cross Flow Turbine
Oscillating Hydrofoil -> Oscillating Wave Surge Converter
Kite
Archimedes Screw -> Point Absorber?
Vortex-Induced Vibration -> ?

Property:MREDeviceResourceType | Open Energy Information

Tidal
Ocean Current -> Current
Riverine


Fix AABB missing constructor

Muli was throwing the following compile errors on my project

By adding a constructor that accepts the 2 vectors, it can now successfully compile 💖

Hello! Thank you for checking out my repository.
I've checked this issue, while it doesn't compile with c++20, it compiles well with the project's configuration set to c++17.
+I found that this issue can easily be resolved by removing 'AABB() = default;'

Hello! Thank you for checking out my repository. I've checked this issue, while it doesn't compile with c++20, it compiles well with the project's configuration set to c++17.
+I found that this issue can easily be resolved by removing 'AABB() = default;'

Ah, my project is currently set to c++20, that might have been the issue then

It think this constructor thing is the only issue when i update project from c++17 to c++20 so it seems appropriate to add the constructor.
Thank you for your contribution!


bug(mat-checkbox): indeterminate state is not reflected in component classlist anymore.

Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
V14
Description
V14

V15

Reproduction
Steps to reproduce:

Open docs/demo;
Open devtools;
Toggle one of these checkboxes;

See that mat-mdc-checkbox-indeterminate is not set.

Expected Behavior
Like with checked state should be reflected in classlist:

Actual Behavior
Indeterminate state reflection is missing from classlist.
Environment
Angular CLI: 15.1.6
Node: 18.14.0
Package Manager: yarn 3.3.0
OS: win32 x64
Angular: 15.1.5
... animations, cdk, common, compiler, compiler-cli, core, forms
... language-service, material, platform-browser
... platform-browser-dynamic, router
Package                            Version
@angular-devkit/architect          0.1501.6
@angular-devkit/build-angular      15.1.6
@angular-devkit/build-ng-packagr   0.1002.4
@angular-devkit/core               15.1.6
@angular-devkit/schematics         15.1.6
@angular/cli                       15.1.6
@schematics/angular                15.1.6
rxjs                               7.8.0
typescript                         4.9.5

This class isn't a public API. Previously we used it for styling, but we don't need it anymore with the MDC implementation.

@crisbeto, could you give a link to public API? Because it's not clear which classes can be used for styling and which are not. In this case mat-checkbox-checked is used, but max-checkbox-indeterminate is not which is super confusing. Most of the components are almost uncustomizable at all.

These classes are all implementation details. Since you're the one telling the checkbox if it should be indeterminate, you can also set a custom class on it.


What are sum and power used for in the predicting probability maps and where to compute loss?

Network: ENet-Label
If I'm not wrong you are feeding outputs from stage 2 and 3 of ENet encoders to the following sequentials each of input dimensions (1, 128, 36, 100) for an input image of (1, 3, 288, 800).
seq_2:add(nn.Power(2))
seq_2:add(nn.Sum(1, 3))
seq_2:add(nn.SpatialUpSamplingBilinear(8))
seq_2:add(nn.SpatialSoftMax())

seq_3:add(nn.Power(2))
seq_3:add(nn.Sum(1, 3))
seq_3:add(nn.SpatialUpSamplingBilinear(8))
seq_3:add(nn.SpatialSoftMax())

Why are feature map elements raised to power 2? How do you reduce the feature channels from 128 to n-lane maps? Also I see that seq_2 and seq_3 are concatenated later. How do you compute the loss against ground truth lane map? It is hard to understand this from the code.

The power operation is used to enlarge the difference between elements of the whole feature map. The sum operation is used to sum all values in the channel dimension so that H x W x C feature map will become H x W. Seq_2 and seq_3 are not concatenated but instead used as separate output heads so that early layers will mimic later layers. Ground truth labels are used as extra supervision of the last layer of the encoder. More details will be introduced in our paper which will be available soon. You may print the whole model to see more details.

Thanks for your reply, I used a network visualizer and it's more clear now. So the supervision for seq_2 and seq_3 heads is all classes (lanes here) combined in one channel right, as opposed to per class supervision when predicting individual probability maps and map scores?

Yes.


Distinguishing elective from emergency admissions?

Hey, for research purposes I would like to distinguish emergency from elective admissions. So far I was doing that solely by checking whether the admitsource was "Emergency room" or "PACU" / "Recovery Room", respectively. Is there a better way to do this?
Thanks for any help in advance!

admitsource is good to use. I would also look at apachepredvar which has a column electivesurgery which would help identify patients with elective surgeries.

Thank you so much!


Should this repository be archived?

rules_go now has support for gomock - https://github.com/bazelbuild/rules_go/blob/master/extras/gomock.bzl. Should anyone be using this repository anymore?

Nope, folks shouldn't be. There's a deprecation notice in the README now, and, yep, I'm going to archive this project.

Oh, I'd hoped to see docs show up before archiving this repo.


ocamlPackages.ca-certs-nss: <IP_ADDRESS> -> 3.66

https://github.com/mirage/ca-certs-nss/releases/tag/v3.66

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

:camel:


Az webapp create show error.

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp create Extension Name: appservice-kube. Version: 0.2.2.
Errors:
The command failed with an unexpected error. Here is the traceback:
_StackRuntimeHelper.__init__() got multiple values for argument 'linux'
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.39.0/libexec/lib/python3.10/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.39.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/usr/local/Cellar/azure-cli/2.39.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/local/Cellar/azure-cli/2.39.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 718, in _run_job
    return cmd_copy.exception_handler(ex)
  File "/Users/mars/.azure/cliextensions/appservice-kube/azext_appservice_kube/commands.py", line 42, in _polish_bad_errors
    raise ex
  File "/usr/local/Cellar/azure-cli/2.39.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/usr/local/Cellar/azure-cli/2.39.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/Cellar/azure-cli/2.39.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/Users/mars/.azure/cliextensions/appservice-kube/azext_appservice_kube/custom.py", line 505, in create_webapp
    helper = _StackRuntimeHelper(cmd, client, linux=(is_linux or is_kube))
TypeError: _StackRuntimeHelper.__init__() got multiple values for argument 'linux'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp create --name {} --plan {} --resource-group {}

Expected Behavior
Environment Summary
macOS-12.6-x86_64-i386-64bit, Darwin 21.6.0
Python 3.10.5
Installer: HOMEBREW

azure-cli 2.39.0 *

Extensions:
connectedk8s 1.2.11
azure-firewall 0.14.3
k8s-extension 1.2.6
aks-preview 0.5.102
azure-devops 0.25.0
appservice-kube 0.2.2
customlocation 0.1.3
interactive 0.4.5
log-analytics 0.2.2
containerapp 0.3.8
spring-cloud 3.1.5
spring 1.1.5

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

route to CXP team

@MarsWangyang Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update.

@MarsWangyang Could you please update your extension by running the below command and check if that helps ?

az extension update -n appservice-kube

Awaiting your reply.

Run it, and it's good. Thanks.


[BUG] Wrong filter operators in refine-supabase

Describe the bug
There is a wrong switch case in the refine-supabase dataProvider generateFilter function, contains and containss are reversed. At the moment contains, which should be case-insensitive, is using the like operator, which is case-sensitive. Meanwhile containss, which should be case-sensitive, is using the ilike operator, which is case-insensitive.
To Reproduce
Steps to reproduce the behavior:

Bootstrap a new refine project using supabase as dataProvider
Add a select filter on a resource field
Try to filter the select options using a lowercase value where there should be an uppercase one
The select will not find that option

Expected behavior
The select filter should be able to find the option
Desktop (please complete the following information):

OS: MacOS 12.0.1
Browser Chrome
Version 96.0.4664.55
Used dataProvider refine-supabase

Hey @icomad ,
Oh, good point. Do you want to do this for us?

Hey @icomad ,
We've released<EMAIL_ADDRESS>Could you approve this fix?


Local entries are sometimes not loaded to Suggestion Database

When I close a project and open another in the same application run, the local variables and current module methods (like collapsed) are not loaded to suggestion database.

Should be fixed by #9961

Indeed, on 5.17 I don't see the issue anymore.


Improve the examples script

Accept command line parameters in the example script
Add example epub, html, odt, and txt files for easy testing

I'm not sure if we want to check example files into version control or not. In total they're less than 50kB.

I think this can be merged (sorry for the late review)!


local docker support for url creation and deletion

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug
/kind feature

Documentation changes: Please include [skip ci] in your commit message as well
/kind documentation
[skip ci]

What does does this PR do / why we need it:
This PR implemented local docker support for url creation and deletion.
--exposed-port allows users to specify a specific exposed port on the odo url create command, otherwise a randomly assigned port will be used.
The exposed port will be saved in env.yaml file.
rerun odo url create would reassign an exposed port for the component.
If there are more than 1 ports in devfile, user would need to specify --port parameter during url creation as well.
Which issue(s) this PR fixes:
Fixes #2580
How to test changes / Special notes to the reviewer:
odo preference set experimental true
odo preference set pushtarget docker
odo create openLiberty
odo push
odo url create --port 9080 --now

run docker ps, expected an exposed port assigned to 9080
CONTAINER ID        IMAGE                                       COMMAND                  CREATED             STATUS              PORTS                                                  NAMES
c15b2f10b17c        jeevandroid/open-liberty-dev:latest         "/opt/ol/helpers/run…"    Port 9080 already has an exposed port 63947 set for it. Do you want to override the exposed port Yes
 ✓  URL lopenliberty-9080 created for component: openliberty with exposed port: 59940
 •  Push devfile component openliberty  ...
 ◐  Updating the component devruntime
Applying URL configuration
 ✓  URL <IP_ADDRESS>:59940 created

 ✓  Starting container for jeevandroid/open-liberty-dev:latest [474ms]
 ✓  Updating the component devruntime [749ms]
 ✓  Push devfile component openliberty [785ms]
 ✓  Changes successfully pushed to component

Tested it worked on Windows, Linux and MacOS:
Windows:

Linux:

MacOS:

/retest

/area devfile

/retest

/test v4.2-integration-e2e-benchmark

/assign cradge (My approval's not enough 😢 )

One big thing with both the previous docker implementation and this is that there is zero documentation.
Is there any way possible that yourself or someone on the IBM team with experience with docs can add a little document outlining the features as well as what's beeen implemented?
To be honest, we have to hunt through random PR's and issues in order to find out exactly what's been implemented and how it works.

/retest

/test v4.3-integration-e2e-benchmark

/refresh

@yangcao77 Can you rebase this PR and address merge conflicts?

@mik-dass @cdrage I've pushed new commits based on the code review. Can you help review again?

/test v4.3-integration-e2e-benchmark

/retest

@yangcao77 It looks like this PR pics up a lot of commits from @johnmcollier that were already merged as part of another PR  https://github.com/openshift/odo/pull/2806/commits

@kadel I have combined all my changes into one single commit to clean up the git history.
Now this PR only include my commits.

It seems I need to be connected to a Kube cluster for odo url create to work on Docker. I was testing out the changes with my vpn off (and my kube context set to a cluster behind the firewall), I kept getting the following error:
Johns-MacBook-Pro-3:springboot johncollier$ odo url create
 ✗  listen tcp: lookup localhost: no such host

I logged in to the vpn and it worked:
Johns-MacBook-Pro-3:springboot johncollier$ odo url create
 ✓  URL java-spring-boot-8080 created for component: java-spring-boot with exposed port: 51193

To create the URL on the cluster, please use `odo push`

@yangcao77 I think I found another issue:
I pulled your branch into master and was finding that odo push's after running odo url create wasn't restarting the container and exposing the port. So, I think you need to update the DoesContainerNeedUpdating function to see if any ports need to be exposed for that container (see https://github.com/openshift/odo/blob/e28aaf7468cf6869ac2002f398964f505d968a19/pkg/devfile/adapters/docker/component/utils.go#L145 and https://github.com/openshift/odo/blob/master/pkg/devfile/adapters/docker/utils/utils.go#L38)
The reason we didn't see this before is that my volume PR for docker fixed a bug where container's were always getting restarted with each odo push, now they only get restarted if needed.

@johnmcollier I have a fix for the issue you found. Modified DoesContainerNeedUpdating to check for devfile endpoints update, also checks for exposedPort difference between HostConfig of existing container and value in env.yaml file.
Also added a couple new integration test cases for those changes.
Please help review again.

@mik-dass @cdrage I've pushed new commits based on the code review. Can you help review again?

LGTM.
@yangcao77 Please address the comments by @johnmcollier .

/hold
We need properly handle the following situations
URL created for Docker but pushed to Kube
▶ odo preference set pushtarget docker
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated

▶ odo url create
 ✓  URL backend-8080 created for component: backend with exposed port: 49213

To create the URL on the cluster, please use `odo push`

▶ odo preference set pushtarget kube
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated

▶ odo push
 •  Push devfile component backend  ...
 ✓  Waiting for component to start [24s]

Applying URL changes
 ✗  Failed To Update Config To Component Deployed.
Error: unable to create url: unable to create ingress: error creating ingress: Ingress.extensions "backend-8080" is invalid: spec.rules[0].host: Invalid value: "backend-8080.": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a

The error message is confusing, it doesn't say anything useful. It should detect what happened, and tell user what to do.
This PR https://github.com/openshift/odo/pull/2885 is adding URL Kind to env.yaml which might be useful here.
URL created for Kube but pushed to Docker
▶ odo url create  --host apps.testocp4x.psiodo.net
 ✓  URL backend-8080.apps.testocp4x.psiodo.net created for component: backend

To create the URL on the cluster, please use `odo push`

▶ odo preference set pushtarget docker
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated

▶ odo push
 •  Push devfile component backend  ...
 ✓  Pulling image quay.io/eclipse/che-java11-maven:nightly [2s]
 ✓  Starting container for quay.io/eclipse/che-java11-maven:nightly [595ms]
 ✓  Push devfile component backend [2s]
 ✓  Changes successfully pushed to component

Url was created but it was silently ignored :-/
secure for docker
▶ odo url create -h

      --secure             Creates a secure https url

How is --secure going to work on docker?

The issues that I mentioned in the previous comment doesn't have to be a blocker for this.
I've created https://github.com/openshift/odo/issues/2977 to chapter this. We can follow up on that later.
/hold cancel
/approve

@kadel I've addressed the issue in this PR.
URL created for docker but push to kube
$ odo url create --port 8080
 ✓  URL local-java-spring-boot-8080 created for component: java-spring-boot with exposed port: 61981

To apply the URL configuration changes, please use `odo push`
$ cat .odo/env/env.yaml
ComponentSettings:
  Name: java-spring-boot
  Url:
  - Name: local-java-spring-boot-8080
    Port: 8080
    ExposedPort: 61981
$ odo preference set pushtarget kube
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated
$ odo url create local-java-spring-boot-8080 --host <IP_ADDRESS>.com --port 8080
 ✗  the url local-java-spring-boot-8080 already exists with a different push target. Please recreate one using different urlName

URL created for kube but push to docker
$ odo url create testurl1 --host <IP_ADDRESS>.com --port 9090
 ✓  URL testurl<IP_ADDRESS>.4.com created for component: java-spring-boot

To apply the URL configuration changes, please use `odo push`
e$ cat .odo/env/env.yaml
ComponentSettings:
  Name: java-spring-boot
  Url:
  - Name: local-java-spring-boot-8080
    Port: 8080
    ExposedPort: 61981
  - Name: testurl1
    Port: 9090
    host: <IP_ADDRESS>.com
$ odo preference set pushtarget docker
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated
$ odo url create testurl1 --port 9090
 ✗  the url testurl1 already exists with a different push target. Please rerun the command using a different urlName.

Also remove --secure flag if the push target is docker.

/retest


DCOS-46049: [1.12] COPS-3759 affecting dcos-ui: When no nodes are in the cluster the message should have different wording

Changed the message when there are no nodes to be more accurate.
Closes https://jira.mesosphere.com/browse/DCOS-46049
Testing

In plugins/nodes/src/js/pages/NodesAgents.js change line 306 to be if (true) {
Click on Nodes tab.
Verify that the message shown is changed.

Trade-offs
Also changed "a" to "are".
Dependencies
None.
Screenshots
Before

After

:tada: This PR is included in version 2.25.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


FailedPreconditionError with Pretty tensor tutorial 3

Hi,
When running your tutorial 3 on pretty tensor, I get FailedPreconditionError.  I am using tensorflow_gpu-0.12.0rc0-cp27-none-linux_x86_64 and prettytensor-0.6.2 with python2.7. The error occurs at the first print_test_accuracy() call.
When I searched on internet, I see that this error can occur if the session variables are not initialized.
In your tutorial they are initialized. Moreover I haven't received this error with first two tutorials.
I am wondering if this has something to do with prettytensor variables. Below is the trace back error message.
Use `tf.global_variables_initializer` instead.
Traceback (most recent call last):
  File "train.py", line 139, in <module>
    print_test_accuracy(dataset.data)
  File "train.py", line 88, in print_test_accuracy
    cls_pred[i:j] = session.run(y_pred_cls, feed_dict=feed_dict)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 766, in run
    run_metadata_ptr)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 964, in _run
    feed_dict_string, options, run_metadata)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1014, in _do_run
    target_list, options, run_metadata)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1034, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.FailedPreconditionError: Attempting to use uninitialized value layer_conv1/weights
	 [[Node: layer_conv1/weights/read = Identity[T=DT_FLOAT, _class=["loc:@layer_conv1/weights"], _device="/job:localhost/replica:0/task:0/cpu:0"](layer_conv1/weights)]]

Caused by op u'layer_conv1/weights/read', defined at:
  File "train.py", line 4, in <module>
    from debug import *
  File "/home/badami/Codes/deeplearning/src/debug.py", line 4, in <module>
    from param import *
  File "/home/badami/Codes/deeplearning/src/param.py", line 14, in <module>
    y_pred, loss = model1(x_image, y_true)
  File "/home/badami/Codes/deeplearning/src/models.py", line 11, in model1
    conv2d(kernel=5, depth=16, name='layer_conv1').\
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/prettytensor/pretty_tensor_class.py", line 1981, in method
    result = func(non_seq_layer, *args, **kwargs)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/prettytensor/pretty_tensor_image_methods.py", line 159, in __call__
    params = self.variable('weights', size, init, dt=dtype)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/prettytensor/pretty_tensor_class.py", line 1695, in variable
    collections=variable_collections)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/ops/variable_scope.py", line 1024, in get_variable
    custom_getter=custom_getter)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/ops/variable_scope.py", line 850, in get_variable
    custom_getter=custom_getter)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/ops/variable_scope.py", line 346, in get_variable
    validate_shape=validate_shape)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/ops/variable_scope.py", line 331, in _true_getter
    caching_device=caching_device, validate_shape=validate_shape)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/ops/variable_scope.py", line 677, in _get_single_variable
    expected_shape=shape)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/ops/variables.py", line 224, in __init__
    expected_shape=expected_shape)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/ops/variables.py", line 370, in _init_from_args
    self._snapshot = array_ops.identity(self._variable, name="read")
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/ops/gen_array_ops.py", line 1424, in identity
    result = _op_def_lib.apply_op("Identity", input=input, name=name)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/framework/op_def_library.py", line 759, in apply_op
    op_def=op_def)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 2240, in create_op
    original_op=self._default_original_op, op_def=op_def)
  File "/home/badami/Codes/deeplearning/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1128, in __init__
    self._traceback = _extract_stack()

FailedPreconditionError (see above for traceback): Attempting to use uninitialized value layer_conv1/weights
	 [[Node: layer_conv1/weights/read = Identity[T=DT_FLOAT, _class=["loc:@layer_conv1/weights"], _device="/job:localhost/replica:0/task:0/cpu:0"](layer_conv1/weights)]]

I encountered the exact same issue too.

You're way ahead of me :-) I haven't tried TensorFlow 0.12 yet and I just got my GPU laptop yesterday. It'll be a while before I have it setup on that PC.
However, these tutorials were developed with Python 3.5 and sometimes 2.7 gives strange error-messages. Please try using Python 3.5 and see if that fixes the issue?
Another thing you could try is to replace the following two lines:
session = tf.Session()
session.run(tf.initialize_all_variables())

with something like this:
init_op = tf.initialize_all_variables()
session = tf.Session()
session.run(init_op)

Does that fix the issue?
You can also try running TensorFlow 0.11.
I hope you can find the solution and report back so I can fix it in the Notebook.
Cheers!

Thanks for the prompt reply.
I have checked the following things right after I had posted the issue.
Python 3.4 -> same issue.
changed the lines of session as described by you with python 2.7 (the same solution I found from other thread as well) -> not working.
Run another pretty tensor tutorial on MNIST provided on pretty tensor github page with python 2.7, python 3.4 -> same error.
I have raised an issue on prettytensor github repo as well.
I am having a strong feeling that the problem is with pretty tensor/tensorflow library and not with your tutorial.
Thank you once again. Very informative tutorials and videos.
Cheers!

Hi, I've managed to solve this problem by updating my pretty tensor to the latest version as pointed out in your issue.

yes that was version mismatch between tensorflow and pretty tensor. I solved it too. works with both python 2.7 and 3.4.

Thanks for investigating the issue and sharing the solution.

how i make our own data set for im2txt model...


Fix About.html

[ ] create a division for just heading
[ ] add the test part in the lighter theme

Currently the whole page is in darker theme with particle js in the background. Only heading should be in this portion, same as other pages the content has to be added in the lighter theme.

@m0n574

Done


Error building site: EXECUTE-AS-TEMPLATE | Fedora

Unable to run Hugo server in the main branch
commit 287fa6f102652328c8fc54f8e0444879e105f150 (HEAD -> main, origin/main, origin/HEAD)
After clone and submodules updated, output says:
`~/repos/docs │ main  hugo serve                                                                                ✔ │ 8m 17s │ 08:53:18 PM
Start building sites …

Built in 1286 ms
Error: Error building site: EXECUTE-AS-TEMPLATE: failed to transform "json/offline-search-index.json" (application/json): failed to parse Resource "json/offline-search-index.json" as Template:: template: json/offline-search-index.json:5: unclosed action
 ~/repos/docs │ main
 `

SYSTEM
FEDORA 35
Hugo Static Site Generator v0.80.0/extended linux/amd64 BuildDate: unknown

Task: test with the recent Hugo version

Problem Solved:
The root cause was the Hugo Version: The fix is included in the latest Hugo version  v0.97.3
Solution: The easiest way is get the latest hugo from brew!
https://formulae.brew.sh/formula/hugo#default


kubectl requires some additional documentation

It took many tries to get kubectl set up, and even once set up it did not interact intuitively with me. Without kubectl the whole process as outlined on the page generates a stream of red message text that makes little sense.
Some additional notes on the need for azdata and azdatactl would also help; I needed to go to stack overflow to find out why the az login (the very first step) failed.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dc88b7b8-d8ae-8b11-b988-4ad4bf702863
Version Independent ID: 355e9bf2-4da3-70e1-d0a1-8a038ebdbc8e
Content: Deploy with a python script - SQL Server Big Data Clusters
Content Source: docs/big-data-cluster/quickstart-big-data-cluster-deploy.md
Product: sql
Technology: big-data-cluster
GitHub Login: @WilliamDAssafMSFT
Microsoft Alias: wiassaf

@UTrackIT Thanks for finding this issue.

@UTrackIT Thanks for this feedback. I'm glad you were able to work through your issues. A doc update is in flight for some general improvements here. Given your workarounds, do you have any specific link references or instructions that would have been helpful in this doc?  Thanks again for this feedback, your suggestions help improve our documentation. Will close this issue but open to continuing a more specific conversation.


MultiSource: a Source that merges results from other Sources

The plan is to wrap ServiceSource and IngressSource and pass it to the controller.

lgtm


RDKTV-18719 : WpeFramework crash fix

Reason for change:
HdmiCecSink shared_ptr cross reference in DisplaySettings
plugin is removed.
Test Procedure: None
Risks: Low
Change-Id: I4eff76a03b7a0ebedf5462603eb62484230060b3
Signed-off-by:Anooj Cheriyan<EMAIL_ADDRESS>

New one created: https://github.com/rdkcentral/rdkservices/pull/3075


code clean and modify log level

Signed-off-by: slievrly<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
modify log level and code clean
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1345 into develop will decrease coverage by 0.01%.
The diff coverage is 28.57%.

@@              Coverage Diff              @@
##             develop    #1345      +/-   ##
=============================================
- Coverage      48.63%   48.61%   -0.02%
+ Complexity      1645     1643       -2
=============================================
  Files            332      331       -1
  Lines          11534    11533       -1
  Branches        1428     1428
=============================================
- Hits            5609     5607       -2
- Misses          5302     5303       +1
  Partials         623      623

Impacted Files
Coverage Δ
Complexity Δ

...ore/src/main/java/io/seata/core/lock/LockMode.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...rc/main/java/io/seata/core/codec/CodecFactory.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../src/main/java/io/seata/core/protocol/Version.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...rc/main/java/io/seata/core/rpc/ChannelManager.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../java/io/seata/server/coordinator/DefaultCore.java
59.64% <100%> (ø)
24 <0> (ø)
:arrow_down:

.../java/io/seata/core/context/ContextCoreLoader.java
57.14% <100%> (ø)
1 <1> (ø)
:arrow_down:

...atasource/undo/parser/ProtostuffUndoLogParser.java
42.85% <100%> (ø)
4 <1> (ø)
:arrow_down:

...java/io/seata/rm/datasource/DataSourceManager.java
27.41% <12.5%> (ø)
7 <1> (ø)
:arrow_down:

...n/java/io/seata/rm/datasource/ConnectionProxy.java
9.3% <14.28%> (-0.23%)
4 <0> (ø)

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 4b7fe55...8dedd86. Read the comment docs.


Consistent case for Readme filenames

All but the following Readme files are named README.md (having a lowercase extension):

optional_cad_parts/README.MD
parts_list/README.MD

Solution
Rename the above two files to README.md.

Hi, can I help contribute to the project.

بله ممنون میشوم

Can we have that in english, or is there  way to translate in github?

^ lol, I won't be helpful on translating there


disableAutoPause doesn't disable auto-resume

When focus is regained while disableAutoPause is true and audio is playing, it seems like the system is still trying to "resume" the already-playing audio, causing a doubling-up of the audio (robotic echoey effect), and loss of ability to control the playback.

Do you have a repro?

Here's an example. Once the demo turns green, click to start sound playing. Click to another window, then back into the green area. Clicking on the background while the frame has focus should start and stop the sound. Not every time, but very often, the audio playback will get a phased/doubled effect, and at this point, the originally-triggered audio will be uncontrollable, and new instances will get toggled on and off.
https://codesandbox.io/s/compassionate-driscoll-lxrptn?file=/src/index.js

+1 on this.

I published v5.2.1 and v4.4.1 which contain this fix. Let me know if that works for you all.


[Menu] Add attributes to support assistive technologies

[Menu] Add presentation role to wrapper to lessen likelihood of screen readers repeatedly saying "clickable" for every nested element with event handlers attached
[Menu] Add menu role to list so element is accurately described as a menu
[MenuItem] Add menuitem role attribute to wrapping ListItem

As this change is very small I haven't created an issue, happy to create one if necessary.

[x] PR has tests / docs demo, and is linted. (Linted, no demo or tests necessary)
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

@170102 Thanks for this. IWould love to get your feedback on the next branch. @nathanmarks has made a good start adding ARIA roles compared to master, but we still have lots of for more recent contributions.

@mbrookes Thanks for maintaining an exceptional repo. I'll gladly dig into the next branch at my next opportunity to get more familiar with the direction it's taking. I have a few more potential accessibility contributions which need cleaning up before making the PR and next will help steer that

@170102 Thanks for opening that PR. I'm not an expert in i11y, that sounds good to me 👍 .


Discrepancy between 3ML and Xspec residuals of spectral fitting

Hi,
I am doing the joint spectral fitting of Fermi GBM and ASIM data using threeML and Xspec. I am getting consistent spectral parameters from both (threeML and Xspec) the tools. However, I am facing issues with the residual of the model fit. 3ML is showing a large residual for the ASIM data (although the data is good fitting), however, Xspec is showing a very low residual for the ASIM data. I am using display_spectrum_model_counts() of threeML to show the model fit and residual. Is there any other way to plot residuals in 3ML of the model fit, similar to delchi command of Xspec?  What could be the possible reasons for this discrepancy between 3ML and Xspec residuals?

I am not sure how XSPEC computes the residuals, but it my be a naive chi2. We use the proper residuals for the likelihood of the data and this may be the result of the discrepancy.

Many thanks for the prompt response @grburgess.
But I am surprised, that the joint spectral model fitting is well fitting the ASIM data but the residual plot of 3ML is very large (close to 10 sigma). What could be the possible cause of this?  Count/plugin/etc issues in the spectrum or some limitation of the 3ML itself?

Can you provide comparison plots to demonstrate the issue?

TRS_band_bin2_GBM_ASIM.pdf
Okay. Please see the attachment.

There does seem to be an issue with how the residuals are plotted. Can you provide the code used to generate the plot?

Okay, I have sent you a tar folder with code and data files to your email (jburgess@mpe.mpg.de). Many thanks.

The issue was in the scale factor of the ASIM background. How is this derived?

@rahulc157 any update?

Sorry for the delaied responce. I just sent the response from the ASIM team to your email.

The background has an exposure of:
TSTART  =            106.50000 / DOY observation start time
TSTOP   =            106.50000 / DOY observation stop time
EXPOSURE=           0.42000000 / Integration time in seconds fro the PHA data
AREASCAL=                   1. /  Area scaling factor, no field AREASCAL
BACKSCAL=                   1. /  Background scale factor, no field BACKSCAL

which does not line up with the start and stop time.
This is much shorter than the source exposure time:
TSTART  =            106.50000 / DOY observation start time
TSTOP   =            108.20000 / DOY observation stop time
EXPOSURE=           0.70000000 / Integration time in seconds fro the PHA data

and moreover the background and source times overlap. I'm not familiar with the details of the data reduction, but the significance calculation which also does the residuals is derived for a background scaling that is larger than one (this also makes since when using a profile likelihood otherwise there is not enough data to perform a stable profile).
The issue is not that the file is not being read correctly, it is that the residuals in XSPEC are not Poisson residuals, they are simply an L1 norm from the data, which is incorrect for the data you have.

Hi,
I agree that the TSTART and TSTOP keyword are not consistent with the EXPOSURE keyword. This comes from the fact that ASIM is not designed to detect GRB, and the pipeline for producing the fit files is not bullet-proof. However, as far as I know, XSPEC uses the EXPOSURE keywords only, this is why we did not bother fixing the TSTART and TSTOP keywords.
The background is, in fact, only 0.42 sec exposure, because this is all the data that we have before the trigger. We do not have all photon data as for GBM. But, of course, the background time interval does not overlap with the GRB time interval.
Sorry, but I don’t understand when you write: ‘they are simply an L1 norm from the data, which is incorrect for the data you have.’
Can you please explain me better?
What is plotted above was obtained with the XSPEC command ‘plot data delchi’, which, according to the XSPEC manual, is supposed to provide residuals between observations and the best fit model in terms of sigmas.

The formula on the y axis of the xspec plot is incorrect for poisson data.

Can we close this issue?


Fix - import json in streams.py

Fix json import in streams.py
Add unique keys to allow database targets
Bigger page_size for answers call

I am going to look at pull request this weekend.


Beacon/SSI : Sign button and message box "Wait a moment" are sometimes displayed 2 times in less than 1sec...

test  with https://talao.co/sandbox/dapp/register_gamer_pass

the flow must be smooth


Add local and git resolvers for branch option

The SDK resolves the branch the first time it needs it. It goes one by one, until it finds a string or a function that resolves in a stiring. Example:
import {local, git} from<EMAIL_ADDRESS>
branch: [process.env.XATA_BRANCH, local, git, 'main']

In this case local and git are async function that return string, undefined or null. The resolved branch name will be stored in the XATA_BRANCH env variable. If it's not defined, it'll resolve the functions sequentially. If none of them return a defined string, the branch name used will be main.

Closing as we've already implemented branch resolution in a different way


Support for Hyundai PHEVs

OOOOOOO OOOOOOOO OOOOOOOOOOO!!!!!!
if you help out the Hyundai IONIQ PHEV 2020.... I'll... I'll probably do nothing because I'm useless but man I'd be happy!


No Colors on folders

I'm not really sure if it's an issue, but I assume that downloading and putting in my css folder and activating it would make my folders have colors and stuff like previewed, but when I tried, I get only bold text folders and nothing else on both light and dark theme. I tried messing with my current plugins, turning them off to see if any changes, and nothing still... I even tried just using

Nevermind. Apparently the code is only bold... sorry for causing worry...
I just notice that the prefix below is something that I have to copy to the main thing and not something that are already linked to the functioning code or something. Now I'm gonna figure out how to make them appears in rainbow colors.
Again, sorry for submitting false issue. It's my fault on my end


Gamebreaking: If player buys additional time in pitch round, game breaks

During the pitch round, if any player chooses to buy additional time to speak, the additional time will be added to the timer and count down, but afterwards, the "next player" button will never appear on the host screen, only the timer at 0. Refreshing the host device in this state will return only the standard game UI, without any other elements.

#46 #52 #28


Improve setup.py file

This would eventually fix the "Used by" button on Github

Coverage remained the same at 66.172% when pulling 2fb637c98b7a385959d052a68c5a6db05e5c7967 on martinRenou:improve_setup_py into da1c1f0dc088fbcbca1bfebd23b39fb8e600ef39 on maartenbreddels:master.

Thanks!


Add synth script and update CI

I'm surprised that docs pass - ah well it prints "no docs 👻 "

Oh wow, all of CircleCI + Kokoro pass! 😮