apk update/add in the docker container under proxy giving permission denied

Running docker in a host (centos Red Hat Enterprise Linux Server release 7.2 (Maipo)) which is under proxy, able to pull alpine:3.4 by following steps in stackoverflow.
Now starting the container form alpine:3.4, setting proxy, and running apk --update add curl giving me permission denied
[root@xxx ~]# docker run -it alpine:3.4 sh
/ # export http_proxy=http://proxyuser:proxypassword@proxyip:proxyport
/ # export https_proxy=http://proxyuser:proxypassword@proxyip:proxyport
/ # apk --update add curl
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.4/main: Permission denied
WARNING: Ignoring APKINDEX.167438ca.tar.gz: No such file or directory
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/community/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.4/community: Permission denied
WARNING: Ignoring APKINDEX.a2e6dac0.tar.gz: No such file or directory
ERROR: unsatisfiable constraints:
  curl (missing):
    required by: world[curl]
/ #

Got something similar with the python:2.7-alpine image :
FROM python:2.7-alpine
RUN pip install virtualenv
RUN apk add --update git && rm -rf /var/cache/apk/*

Give me :
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/community/x86_64/APKINDEX.tar.gz
(1/6) Installing ca-certificates (20160104-r4)
(2/6) Installing libssh2 (1.7.0-r0)
(3/6) Installing libcurl (7.49.1-r0)
(4/6) Installing expat (2.1.1-r1)
(5/6) Installing pcre (8.38-r1)
(6/6) Installing git (2.8.3-r0)
ERROR: git-2.8.3-r0: Permission denied
Executing busybox-1.24.2-r9.trigger
Executing ca-certificates-20160104-r4.trigger
1 errors; 15 MiB in 23 packages

Got something similar with the nginx:alpine image :
FROM nginx:alpine

MAINTAINER Mahmoud Zalt<EMAIL_ADDRESS>
ENV http_proxy 'http://user:pass@<IP_ADDRESS>:9090'
ENV https_proxy 'http://user:pass@<IP_ADDRESS>:9090'

ADD nginx.conf /etc/nginx/
ADD laravel.conf /etc/nginx/conf.d/laravel.conf

ARG PHP_UPSTREAM=php-fpm

RUN apk update \
    && apk upgrade \
    && apk add --no-cache bash \
    && adduser -D -H -u 1000 -s /bin/bash www-data \
    && rm /etc/nginx/conf.d/default.conf \
    && echo "upstream php-upstream { server ${PHP_UPSTREAM}:9000; }" > /etc/nginx/conf.d/upstream.conf

CMD ["nginx"]

EXPOSE 80 443

Error Result :
Step 8 : RUN apk update     && apk upgrade     && apk add --no-cache bash     && adduser -D -H -u 1000 -s /bin/bash www-data     && rm /etc/nginx/conf.d/default.conf     && echo "upstream php-upstream { server ${PHP_UPSTREAM}:9000; }" > /etc/nginx/conf.d/upstream.conf
 ---> Running in 204aabee34a1
fetch http://dl-cdn.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.3/main: Permission denied
WARNING: Ignoring APKINDEX.5a59b88b.tar.gz: No such file or directory
fetch http://dl-cdn.alpinelinux.org/alpine/v3.3/community/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.3/community: Permission denied
WARNING: Ignoring APKINDEX.7c1f02d6.tar.gz: No such file or directory
2 errors; 31 distinct packages available
ERROR: Service 'nginx' failed to build: The command '/bin/sh -c apk update     && apk upgrade     && apk add --no-cache bash     && adduser -D -H -u 1000 -s /bin/bash www-data     && rm /etc/nginx/conf.d/default.conf     && echo "upstream php-upstream { server ${PHP_UPSTREAM}:9000; }" > /etc/nginx/conf.d/upstream.conf' returned a non-zero code: 2

I tried this and saw that, it is just that apk tool that is failing. When I tried wget on alpine:3.4 container under proxy, wget succeeds. But apk tool continue giving permission denied error. Does the apk tool under alpine honor http_proxy/https_proxy environment variables ?

I am seeing the same thing, permission denied. Is there any solution or workaround for this?

can you try running strace apk update and see what it tries to connect to? apk should honor http_proxy and HTTP_PROXY. Not sure if it honors the https variants.

@ncopa strace isn't installed in alpine image and so we cannot run it. Is strace for alpine downloadable from any URL ?. I could use wget if we have URL.

@kiranpradeep apk add --no-cache strace

@ncopa :) I downloaded(wget) strace from here(1) and installed it as  apk add strace-4.13-r0.apk. Then ran strace apk add --no-cache vim to get the attached error log

It seems that apk uses libfetch, which accepts HTTP_PROXY_AUTH environment variable. I could workaround this issue as following:
export http_proxy=http://proxyhost:proxyport
export HTTP_PROXY_AUTH=basic:*:proxyuser:proxypass

Please note that upper case letters must be used for HTTP_PROXY_AUTH .

Come back to that issue. The work around doens't work when no authentication is requried at proxy side. I m running over docker 1.12.1 (I see docker info | grep Security => seccomp). Running strace fails with also Operation not permitted.
My guess is something goes wrong with security options, but how to deal with ?
I still get the sequences :
docker run -it alpine:3.3 sh
apk update
fetch http://dl-cdn.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
^C
wget http://dl-cdn.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
Connecting to dl-cdn.alpinelinux.org (<IP_ADDRESS>:80)
^C
/ # export http_proxy=http://proxyhost:proxyport
/ # export https_proxy=http://proxyhost:proxyport
/ # wget http://dl-cdn.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
Connecting to proxy (proxy)
APKINDEX.tar.gz      100%
/ # apk update
fetch http://dl-cdn.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.3/main: Permission denied
/  strace apk update
strace: ptrace(PTRACE_TRACEME, ...): Operation not permitted

docker run -v /home/jenkins/addons:/custo --security-opt seccomp:unconfined --cap-add SYS_PTRACE -e http_proxy=http://proxyhost:proxyport -e https_proxy=http://proxyhost:proxyport -it alpine:3.3 sh
apk add /custo/strace-4.13-r0.apk
strace apk update
=> get a 407 .
The mistake comes with the proxy i was using.
Just to close the thread adding the tip for running strace over 1.12 docker.

Closing as it sounds like the workaround here is to set HTTP_PROXY_AUTH=basic:*:proxyuser:proxypass as well as your normal proxy information.

I have same problem with almost plain vanilla alpine on
docker run -it --name test expert/docker-java-minimal:server-jre /bin/ash

I have no proxy. What should I do ?

@unoexperto you've probably solved your issue by now but this may be useful to someone else.
I had a similar issue also on EC2, running Docker 17.06.0-ce.
To troubleshoot, I tried wget in my Dockerfile
wget http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
but got 403s as well, then instead of trying
I then switched to HTTPS and tried
wget https://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz and that worked after I turned the SSL certificate check off.
However https://dl-3.alpinelinux.org had a valid certificate so I set that as my repository in my Dockerfile.
RUN echo 'https://dl-3.alpinelinux.org/alpine/v3.4/main' > /etc/apk/repositories
However, even though I was attempting to only apk install --no-cache --update nodejs I got the following warning and error
WARNING: The repository tag for world dependency 'php5-redis@testing' does not exist
ERROR: Not committing changes due to missing repository tags. Use --force to override.

So I added testing and community repositories like so
RUN echo 'https://dl-3.alpinelinux.org/alpine/v3.4/main' > /etc/apk/repositories  && \
    echo '@testing https://dl-3.alpinelinux.org/alpine/edge/testing' >> /etc/apk/repositories && \
    echo '@community https://dl-3.alpinelinux.org/alpine/v3.4/community'

Everything worked happily after that.

Hi all - I'm sure all involved have moved on, but in case someone else finds this - this might also help (in addition to what @omoloro mentioned above)
I encountered this issue on our Google Cloud Compute instance running ubuntu 17.04. None of the fixes here helped, so I decided to see if the same thing happens on Centos 7 - and it worked on first try!
We don't use any proxy server ourselves, but I imagine that running in a VM inside a cloud would mean that there's some kind of proxy along the path in their infrastructure. In any case, I'm assuming there's something in Ubuntu's configuration (not necessarily related to Docker) that [indirectly] causes this.

Finally I solved this corporate proxy chore. I'm on windows 10.

Set windows environment (this is optional, otherwise you need to type it out in docker build)
HTTP_PROXY_AUTH=basic:*:user:password(without html encoding for special char)
HTTP_PROXY=http://user:password(with html encoding for special char)@proxy:port
HTTPS_PROXY=http://user:password(with html encoding for special char)@proxy:port
You can check if these are set by typing $HTTP_PROXY, etc in shell.

Inside docker file:
ARG proxy ARG auth ENV http_proxy=$proxy https_proxy=$proxy ENV HTTP_PROXY_AUTH=$auth

Add this to "docker build" command:
--build-arg proxy=$HTTP_PROXY --build-arg auth=$HTTP_PROXY_AUTH

Someone was able to use this image with https proxy?

All in all problems should have been fix with specifying --build-args http_proxy="$http_proxy" --build-args https_proxy="$https_proxy" for $ docker build, with http_proxy and https_proxy defined in /etc/environment on the host system.
Except I ran into the situation where http_proxy and https_proxy contained special characters in the username and password fields. Something like:
http://userlocation\username:password@proxy.xyz:80 (notably the "\")
and needed to be defined as:
http://userlocation%5Cusername:password@proxy.xyz:80 (notably the "%5C")
This worked on the host system (ubuntu), but apk did not support this, and vice-versa.
Problem was fixed by defining http_proxy_unescaped and https_proxy_unescaped and passing these to $ docker build instead of http_proxy and https_proxy

After several attempts with several combinations, I found the magic solution :
HTTP_PROXY_AUTH=basic:*:proxy_user:proxy_password
HTTP_PROXY=http://proxy_host:proxy_port
HTPPS_PROXY=http://proxy_host:proxy_port
My password contains the @ character, I left it as it is.

I've tried it and got the same solution.
ng1
# export http_proxy=http://proxy@user:proxy_passwd@proxy.host:8080
# apk update
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.8/main: DNS lookup error
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.8/community: DNS lookup error

apk can't resolve the proxy host name without percent-encoding.
ng2
# export http_proxy=http://proxy%40user:proxy_passwd@proxy.host:8080
# apk update
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.8/main: Permission denied
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/x86_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.8/community: Permission denied

Probably libfetch does not support percent-encoding.
see: libfetch/http.c
ok
# export http_proxy=http://proxy.host:8080
# export HTTP_PROXY_AUTH=basic:*:proxy@user:proxy_passwd
# apk update

docker build
# cat Dockerfile
FROM alpine
ARG HTTP_PROXY_AUTH
RUN apk update
# docker build --build-arg http_proxy=... --build-arg HTTP_PROXY_AUTH=... -t mycontainer .

@crts-xxx I managed to make it work doing as @AndolsiZied said :

HTTP_PROXY_AUTH has to be basic:*:proxy_user:proxy_password not basic:*:proxy@proxy_user:proxy_password # remove 'proxy@'
HTTP_PROXY must be defined, not http_proxy but the pattern is as you say

Crazy I spent so much time on it... Thanks @crts-xxx .
I would just add the quotes on the password.
export HTTP_PROXY_AUTH='basic:*:proxy@user:proxy_passwd'

@etlfg proxy@user is the username. ;)
He just highlight that we must not percent encode the characters.

It appears that apk only honours the HTTP_PROXY variable and not http_proxy. So your environment variable has to be all caps. Same for HTTPS_PROXY. Do not use small case proxy environment variable here.

I am using only an EC2 ..I dont have any proxy .. still I am facing same issue.

Same issue without using a proxy!
Alpine is such a pain...

Same issue without using a proxy!

Then you have a different issue, since this was about the use of proxy.

Same issue without using a proxy!

Then you have a different issue, since this was about the use of proxy.

The issue is precisely the same, but the environmental circumstances are different. I'm getting the same error, but the solution is not feasible for my case. What to do? Open a new issue ticket which will be closed because everyone assumes it must be the proxy to which a solution was given here in this thread? Please instruct...

Then you have a different issue, since this was about the use of proxy.

The issue is precisely the same, but the environmental circumstances are different. I'm getting the same error, but the solution is not feasible for my case. What to do? Open a new issue ticket which will be closed because everyone assumes it must be the proxy to which a solution was given here in this thread? Please instruct...

Please create a new ticket, but without using the word proxy in the title. Then describe how to reproduce it.

Setting environment variables and then running sudo is a bad idea. Commands under sudo have their own environment variables.
> export http_proxy=xxx
> sudo apk add something

will not work. Solution:
> sudo bash
# export ...
# apk add something

sudo -E keeps your environment variables.

same problem for golang image with

RUN apk update && apk add alpine-sdk git && rm -rf /var/cache/apk/*

add in Dockerfile
ENV http_proxy=your_proxy
ENV https_proxy=your_proxy
worked

Closing as it sounds like the workaround here is to set HTTP_PROXY_AUTH=basic:*:proxyuser:proxypass as well as your normal proxy information.

Unfortunately this workaround can't be used if the proxy server does not accept any authentication credentials. In my environment, behind a coorporate firewall, I can't get it to work as I cannot use HTTP_PROXY_AUTH 🤷

Closing as it sounds like the workaround here is to set HTTP_PROXY_AUTH=basic:*:proxyuser:proxypass as well as your normal proxy information.

Unfortunately this workaround can't be used if the proxy server does not accept any authentication credentials. In my environment, behind a coorporate firewall, I can't get it to work as I cannot use HTTP_PROXY_AUTH 🤷

Still seeing this.  For me it was also DNS related.  I did not have the option of rebuilding the container however.
I was however able to correctly ping <IP_ADDRESS> but not access dl-cdn.alpinelinux.org.  In my case it was sufficient to add a new entry to the top of /etc/resolv.conf:
nameserver <IP_ADDRESS>

RUN apk add ca-certificates --no-cache

After several attempts with several combinations, I found the magic solution : HTTP_PROXY_AUTH=basic:*:proxy_user:proxy_password HTTP_PROXY=http://proxy_host:proxy_port HTTPS_PROXY=http://proxy_host:proxy_port My password contains the @ character, I left it as it is.

I've spent sooooo much time changing my image from a slim and gorgeous alpine to a bloated ubuntu based...
Glad to see it now. Thanks!!!!

Unfortunately this workaround can't be used if the proxy server does not accept any authentication credentials. In my environment, behind a coorporate firewall, I can't get it to work as I cannot use HTTP_PROXY_AUTH

@utrotzek you must use  export HTTP_PROXY_AUTH= without any value.

docker build --build-arg http_proxy="http://proxy:port" https_proxy="http://proxy:port" --tag my-image:x.y .
!!! "http://proxy:port" !!!!
It's running !


[stable/percona-xtradb-cluster] re-creation of a cluster with existing persistent volumes fails

Is this a request for help?: No

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST

Version of Helm and Kubernetes:
Kubernetes v1.9.2
Helm v2.8.2
Which chart:
stable/percona-xtradb-cluster
What happened:
Install the chart, using persistent storage.
Write some data to the database.
Delete the StatefulSet.
Recreate the StatefulSet.
The first pod enters a CrashLoop due to safe-to-bootstrap protection
Manually edit the grastate.dat file within the volume mounted by the first node, and set safe_to_bootstrap to 1.
The StatefulSet properly gets created.
What you expected to happen:
Given that Kubernetes StatefulSets provide guarantees around the ordering of deletion of pods, I would expect that on a re-create, the SS should be able to properly start and bootstrap from the first pod.
How to reproduce it (as minimally and precisely as possible):
See above.
Anything else we need to know:

cc @stephenlawrence

I'm using this job to edit grastate.dat. PXC cluster should be stopped first. Use proper claim name inside.
apiVersion: batch/v1
kind: Job
metadata:
  name: safe-to-bootstrap
spec:
  template:
    spec:
      volumes:
      - name: mysql-data
        persistentVolumeClaim:
          claimName: mysql-data-pxc-0
      containers:
      - name: safe-to-bootstrap
        image: busybox
        imagePullPolicy: IfNotPresent
        command:
          - sed
          - -i
          - "s|safe_to_bootstrap.*:.*|safe_to_bootstrap:1|1"
          - /var/lib/mysql/grastate.dat
        volumeMounts:
        - mountPath: /var/lib/mysql
          name: mysql-data
      restartPolicy: OnFailure

I think this is still a issue. What if the first node's grastate.dat contains seqno: -1 and is thus not the best node to bootstrap from because it doesn't contain the last version of the database. What if it is the third node in the statefulset that contains the last version of the data.

I got same problem. It can't pass our failover test.


YeonJoon Cheong's Personal Information

Thanks @yjcheong!
I only have two minor comments:

Could you change the PR title to something more descriptive?
 Could you crop the image so that it shows up bigger?

Hi Wu-Jung,
The title of the PR was changed, and the image was cropped.

LTGM, I'll merge now!


fix: add .no-skeleton ability to images

This PR adds the ability for images to NOT show a skeleton by adding the .no-skeleton class.

:tada: This PR is included in version 0.9.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.9.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Values do not save properly if there are multiple HTML (Ace) fields on the page

Noticed an issue where values were not saving on a dashboard page with multiple Ace editors (markdown & no editor). Steps to reproduce:

Create a template or section that contains multiple html type fields with either markdown or false as the editor
Attempt to add values to fields and save
Add a value to the last field first
save
attempt to edit the other fields

This will result in other fields either blanking out or inheriting the value added to the last field. Proposed fix in PR #28

Fixed in #28.


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In 3707d88, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 6849 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in f516be8 after 7 minutes.


Issue #167 Proposed Fix

The issue #167 root cause appears to be related to pruneOldestThreadFiles() and the for delSize <= firstSize loop. If the removed file doesn't complete the required pruning, the loop continues. However, in the case that files is less than the updated index value delCnt, the panic will occur.

Looks good, but I'm currently unable to merge due to conflicts.  Could you do a merge with master and update the PR accordingly?


UTable: How to display the cell value if its column header contains a dot (".")?

Description
Hi, first of all thanks for the great library!
I have a (maybe stupid) question:
<template>
    <UTable :rows="data2"></UTable>
</template>
<script setup>
const data2 = [{ 'na.me': 'John' }];
</script>

The cell value (John) is not seen in the output.
Is there any way to make sure the cell value can be seen?
Thanks in advance.
Full playground:
https://stackblitz.com/edit/nuxt-ui-vhvpqr?file=app.vue

Use columns to make it work, like
<template>
    <UTable :rows="data2" :columns="col"></UTable>
</template>
<script setup>
const data2 = [{ 'na.me': 'John' }];
const col = [{ key: 'na.me', label: 'Name' }];
</script>

Use columns to make it work, like
<template>
    <UTable :rows="data2" :columns="col"></UTable>
</template>
<script setup>
const data2 = [{ 'na.me': 'John' }];
const col = [{ key: 'na.me', label: 'Name' }];
</script>

Thanks @MuhammadKhizar7 . Unfortunately it is the same result ("John" isn't displayed in the table cell):
https://stackblitz.com/edit/nuxt-ui-vhvpqr?file=app.vue


RI-575 Fix the ansible-sshd checkout version

In pike/newton the version is attached to a tag, which is missing
the 'v' in front, this will be reverted once we get the fix
upstream.
(cherry picked from commit 4e86c8a966bfd1e32cb2e8acf92f808ae2a7de8c)
Issue: RI-575

Thank you for submitting a pull request to this project!
Once all check jobs have passed and the pull request has received a
sufficient number of reviews, the repository's gate jobs can be triggered by
adding a comment of :shipit: to this pull request.
When the gate jobs have completed successfully, this pull request will get
merged automatically.


multiple attribute in gtf file

In a gtf file, attributes may repeat. For example, tag attribute repeats in the example below:
GTF row:
1	havana	exon	65419	65433	.	+	.	gene_id "ENSG00000186092"; gene_version "5"; transcript_id "ENST00000641515"; transcript_version "1"; exon_number "1"; gene_name "OR4F5"; gene_source "ensembl_havana"; gene_biotype "protein_coding"; transcript_name "OR4F5-202"; transcript_source "havana"; transcript_biotype "protein_coding"; tag "CCDS"; ccds_id "CCDS30547"; exon_id "ENSE00003812156"; exon_version "1"; tag "basic";
Current read_gtf functions overwrite repeated attributes. This PR fixes this issue with returning list for repeating attributes.

Thanks for making me aware of this issue and the PR - I will have at look at it tomorrow. I will also need to check what happens if you write multiple tags :)

I think I should add a flag duplicate_tag with the options "last" or "all" since all (your version) is going to be a tad slower.
When writing these to GTF, I am contemplating using the GFF3 standard of separating multiple identical tags with a comma so that your example becomes:
1 havana exon 65419 65433 . + . gene_id "ENSG00000186092"; gene_version "5"; transcript_id "ENST00000641515"; transcript_version "1"; exon_number "1"; gene_name "OR4F5"; gene_source "ensembl_havana"; gene_biotype "protein_coding"; transcript_name "OR4F5-202"; transcript_source "havana"; transcript_biotype "protein_coding"; **tag "CCDS,basic";** ccds_id" "CCDS30547"; exon_id "ENSE00003812156"; exon_version "1"

Thoughts?

Also, what about deduplicating these by creating columns tag, tag2 (and tag3 and so on) in the pyranges?. When multiple tags are stored in a list they are stored in a list it is not possible to use vectorized operations easily.

I think gff3 stardart (providing single string with commo separater) is better option compare to providing list or naming tags as (tag1, tag2 ...).

Great work!


CookBook package resolution does not work in Xcode 13

macOS Version(s) Used to Build
macOS 11 Big Sur
Xcode Version(s)
Xcode 13.0
Description
I hope this ticket is not out of place, in such a case sorry, either way it can be closed promptly.
The project does not compile with xcode 13. It fail to build the package dependency graph.
I have been trying to fix it, since i think the main reason is that the only stable release of AudioKit for xcode 13 is 5.2.2, but the current CookBook requires 5.5.0 or such.
I figure it's faster to install xcode on another machine than fix this issue, but for the future, I would suggest git-tagging the commits or even better having releases, for each update of AudioKit, or this information will be lost as soon as a new potentially unstable commit is pushed to master.
Thank you for your work and time
Crash Logs, Screenshots or Other Attachments (if applicable)
No response

I'm on Xcode 14 so I can't test this. Did you try File > Packages > Reset Package Caches?

It worked on my Xcode 14.1, but I had issues with package resolution too. The reason was that the package URL was described with HTTPS and even though theoretically, providing an access token should work, I went into an infinite loop of credential dialogs...
So, I changed the URLs to SSH, and voila!! success by giving a passphrase once.
Here is my CookbookCommon/Package.swift.
// swift-tools-version:5.5

import PackageDescription

let package = Package(
    name: "CookbookCommon",
    platforms: [.macOS(.v12), .iOS(.v15), .tvOS(.v15)],
    products: [.library(name: "CookbookCommon", targets: ["CookbookCommon"])],
    dependencies: [
        .package(url: "git@github.com:AudioKit/AudioKit", from: "5.5.4"),
        .package(url: "git@github.com:AudioKit/AudioKitUI", from: "0.3.4"),
        .package(url: "git@github.com:AudioKit/AudioKitEX", from: "5.5.0"),
        .package(url: "git@github.com:AudioKit/Controls", from: "1.0.0"),
        .package(url: "git@github.com:AudioKit/DunneAudioKit", from: "5.5.0"),
        .package(url: "git@github.com:AudioKit/Keyboard", from: "1.3.0"),
        .package(url: "git@github.com:AudioKit/SoundpipeAudioKit", from: "5.5.0"),
        .package(url: "git@github.com:AudioKit/SporthAudioKit.git", from: "5.5.0"),
        .package(url: "git@github.com:AudioKit/Tonic.git", from: "1.0.0"),
    ],
    targets: [
        .target(
            name: "CookbookCommon",
            dependencies: ["AudioKit", "AudioKitUI", "AudioKitEX", "Keyboard", "SoundpipeAudioKit", "SporthAudioKit", "DunneAudioKit", "Tonic", "Controls"],
            resources: [
                .copy("MIDI Files"),
                .copy("Samples"),
                .copy("Impulse Responses"),
            ]
        ),
        .testTarget(name: "CookbookCommonTests", dependencies: ["CookbookCommon"]),
    ]
)

Yes, sadly no effect

I'm going to close this. Feel free to open it again if needed.


Plugin: Try migrating typst-ws

To survey the performance bottleneck of our renderer

done by https://github.com/Myriad-Dreamin/typst.ts/commit/ce5079688c90078c833b1bfeb14b39f492a9b363


Formally include esbuild in dependency list

See issue #15

Thanks for your contribution!
Replace esbuild with the transformWithEsbuild method exposed by vite:  https://github.com/pd4d10/vite-plugin-svgr/commit/d208a31803d0cb5ea0f3fb9032b22dc43fc6c79e , which seems to be a better way.

Thanks for your contribution!
Replaced esbuild with the transformWithEsbuild method exposed by vite: d208a31 , which seems to be a better way.

All good! 🍻


Synthesis failed for Google.Cloud.ErrorReporting.V1Beta1

Hello! Autosynth couldn't regenerate Google.Cloud.ErrorReporting.V1Beta1. :broken_heart:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the Google.Cloud.ErrorReporting.V1Beta1 API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-19 22:43:37,381 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/Google.Cloud.ErrorReporting.V1Beta1
2021-03-19 22:43:37,877 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2021-03-19 22:43:37,882 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2021-03-19 22:43:37,885 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2021-03-19 22:43:37,889 autosynth [DEBUG] > Running: git config push.default simple
2021-03-19 22:43:37,892 autosynth [DEBUG] > Running: git branch -f autosynth-Google.Cloud.ErrorReporting.V1Beta1
2021-03-19 22:43:37,896 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.ErrorReporting.V1Beta1
Switched to branch 'autosynth-Google.Cloud.ErrorReporting.V1Beta1'
2021-03-19 22:43:38,110 autosynth [DEBUG] > Running: git rev-parse --show-toplevel
2021-03-19 22:43:38,117 autosynth [DEBUG] > Running: git log -1 --pretty=%H
2021-03-19 22:43:38,121 autosynth [DEBUG] > Running: git remote get-url origin
2021-03-19 22:43:38,155 synthtool [ERROR] > Failed executing git checkout master:

error: Your local changes to the following files would be overwritten by checkout:
	google/cloud/dialogflow/v2/answer_record.proto
	google/cloud/dialogflow/v2/conversation.proto
	google/cloud/dialogflow/v2/conversation_profile.proto
	google/cloud/dialogflow/v2/participant.proto
Please commit your changes or stash them before you switch branches.
Aborting

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 312, in _inner_main
    git_source.enumerate_versions(sources, pathlib.Path(temp_dir))
  File "/tmpfs/src/github/synthtool/autosynth/git_source.py", line 202, in enumerate_versions
    source_versions = enumerate_versions_for_source(git_source, temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/git_source.py", line 166, in enumerate_versions_for_source
    local_repo_dir = str(synthtool_git.clone(remote))
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 85, in clone
    shell.run(["git", "checkout", "master"], cwd=str(dest), check=True)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'checkout', 'master']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


cf7 push - no resource exists with the name resource_matches

Please fill out the issue checklist below and provide ALL the requested information.

[x] I tried updating to the latest version of the CF CLI to see if it fixed my problem.
[x] I attempted to run the command with CF_TRACE=1 to help debug the issue.
[x] I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
I cf7 push -f manifest.yml with a unique app + route name, but deployment fails with no resource exists with the name resource_matches error
To Reproduce
git clone https://github.com/cloudfoundry-community/cf-env
cd cf-env
cf7 push -f manifest.cf7-unique-name.yml

The output is:
This command is in EXPERIMENTAL stage and may change without notice

Using manifest file manifest.cf7-unique-name.yml
Applying manifest...
Manifest applied
Pushing app cf-env-unique-name-changeme to org starkandwayne / space cf-env-cf7-test as<EMAIL_ADDRESS>Getting app info...
Mapping routes...
no resource exists with the name resource_matches
FAILED

The resulting app created shows the route was created and mapped:
$ cf7 apps
name                          requested state   instances   memory   disk   urls
cf-env-unique-name-changeme   stopped           0/1         256M     1G     cf-env-unique-name-changeme.cfapps.io

Provide more context
$ cf7 -v
cf7 version 7.0.0-beta.18+cd7c383f7.2019-03-27
$ cf7 target
api endpoint:   https://api.run.pivotal.io
api version:    3.68.0

Hi @drnic the V7 CLI is still under rapid development and not all push functionality currently works as expected. Once we complete our work for getting the basic push functionality working, we will more widely engage our users to use the V7 beta. Also important to note that VAT develops against a release candidate of the CC API.  Was there a particular V7 CLI functionality you wanted to test or use?

I wanted to blog about cf7 set-label and similar features. I wanted to encourage ppl to start upgrading their CI systems to start recording metadata about where the source code comes from, which CI pipeline/job is doing the deployments, who to contact regarding the app.
I was trying cf7 push to see if adding metadata.labels into a manifest.yml would be passed through to the CC v3 API and automatically register the labels/annotations on deploy.

To confirm, you only want v7 bugs raised if they fail against master branch or release candidates of cf-deployment?
When I saw cfsummit keynote demos I don't think it was clear (or I missed it) about where we would go and find these features (PCF 2.5, api.run.pivotal.io, cf-deployment master, cc_ng branches, etc). Sorry about the misunderstanding.

Hey @drnic np. For V7, the release is currently under rapid development so bug fixes right now will not be as helpful until we fully publicize the beta release; we hope to soon as we update the basic push functionality and would welcome bug reports then.
Could you clarify what you mean about finding these features:
(PCF 2.5, api.run.pivotal.io, cf-deployment master, cc_ng branches, etc).

Thanks!

Hi @drnic I'm going to close this issue but please get in touch again if you have any additional questions.


Tood's onnx file request

Hello, I was not able to export the onnx file successfully using mmdet.Is there a Tood onnx file available? I would like to further visualize the network structure for learning, thank you!

@hjfdsssdg Sorry, we have not exported the onnx file.

@fcjian Okay, thank you for your reply!


Python3

I have an error with python3 /usr/bin/env: ‘python’: No such file or directory. I fixed it by changing the first string
#! /usr/bin/env: python to #! /usr/bin/env: python3

I +1 this - for a workaround, you have a few options here:

Create a venv - Then there is a python symlink to python3 by default
Symlink your system python binary to python3


Conflicting numbers on Event Hubs partitions

[Enter feedback here]
This doc says partition count ranges from 2 to 32, but this page says it ranges from 1 to 32.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 71adf8e4-a51b-d20d-39e1-fd7551bc94b9
Version Independent ID: 3d26fbc0-b6ae-e0ca-089f-e4966c19ef22
Content: Overview of features - Azure Event Hubs - Azure Event Hubs
Content Source: articles/event-hubs/event-hubs-features.md
Service: event-hubs
GitHub Login: @spelluru
Microsoft Alias: spelluru

@lilyjma - from 1-32 is correct. I will update the article. Thanks.

Fixed. #please-close


Is there a way to change the drawerLabel of a DrawerComponent dinamically?

Hello,
I want to internationalize my app and change its language within it. While all the regular views are updated perfectly at runtime, the drawer does not seem to do so. I've tried several things, like forcing an update of the Root Component of the app, but it does not seem to work either, which really bugs me.
My guess is that the routeConfig is created at the start of the app statically, and therefore cannot be changed afaik.
Here's a sample of a route of the createDrawerNavigator:
const DrawerNavigation = createDrawerNavigator({   Home: {     screen: StackHome,     navigationOptions: {       drawerLabel: I18n.t('home'), //HERE COMES THE TRANSLATED LABEL       drawerIcon: ({ tintColor }) => (         <Image style={styles.icon}           source={require('../../../assets/icons/inicio.png')}         />     )},   },
I'm using the react-native-i18n library if that means anything.
I've been 2 days already trying to solve this issue, but I can't find anything.
Thanks in advance.

I managed to get this to work by creating my own customDrawerComponent as stated here:
Instead of a const component, I put it as a class, so I could change its content at runtime (it gets its own lifecycle, you know).
After that, I just had to override the items option with an array in the component state.
<DrawerItems {...this.props} items={this.state.elements}. So now, everytime I do a this.setState({elements: newArrayWithNewLanguage}) it updates in the drawer.
I hope it helps anyone. Closing.

There is a more easy solution for this .  just do it like this ...
navigationOptions: () =>({
       drawerLabel: I18n.t("Profile"),
       drawerIcon: () => (
         <Icon
           name="user"
           style={{ fontSize: 20, color: "#2b8a3e" }}
           type="SimpleLineIcons"
         />
       )
     })


set_high / set_low reversed?

Following a suggestion  by  @TheZoq2  in https://github.com/stm32-rs/stm32f1xx-hal/issues/234#issuecomment-647268069  I have been working on some examples that are intended to separate HAL/MPU setup so that the main application part of the code is clearly distinguished from the hardware initialization. In the blink example below I am finding that set_high turns the led off on my bluepill  and on with three other boards using stm32f3xx-hal, stm32f4xx-hal, and stm32l1xx-hal. I am a newbie so could be missing something simple, but this does seem peculiar.
//! Blink  onboard LED if one is available, or PC13 otherwise.
//! compare  blink3 example and stm32f1xx_hal example blinky.rs.
//!
//! stm32f1xx below uses PC13  which is onboard green LED on Bluepill.
//! stm32f3xx below uses PE15  which is onboard green LD6 (West) LED on STM32F303 Discovery kit.
//! stm32f4xx below uses PA5   which is onboard green LD2  LED on STM32F411RET6 Nucleo-64 board,
//!                              but can be configures to PB13.
//! stm32l1xx below uses PB6   On some STM32L1.. Discovery boards there are onboard LD3 and LD4 LEDs on PB7
//!                            and PB6 but mine are defective and so tested with off board LED on PB6.
//!

#![deny(unsafe_code)]
#![no_std]
#![no_main]

#[cfg(debug_assertions)]
extern crate panic_semihosting;

#[cfg(not(debug_assertions))]
extern crate panic_halt;

use cortex_m_rt::entry;
use asm_delay::{ AsmDelay, bitrate, };

#[cfg(feature = "stm32f1xx")]  //  eg blue pill stm32f103
use stm32f1xx_hal::{prelude::*,
                     pac::Peripherals,
		     gpio::{gpioc::PC13, Output, PushPull,},
		     };

#[cfg(feature = "stm32f1xx")]
use embedded_hal::digital::v2::OutputPin;

#[cfg(feature = "stm32f3xx")]  //  eg Discovery-stm32f303
use stm32f3xx_hal::{prelude::*,
                    stm32::Peripherals,
		    gpio::{gpioe::PE15, Output, PushPull,},
		    };

#[cfg(feature = "stm32f4xx")] // eg Nucleo-64  stm32f411
use stm32f4xx_hal::{prelude::*,
                    pac::Peripherals,
    	            delay::Delay,
		    gpio::{gpioa::PA5, Output, PushPull,},
		    };

#[cfg(feature = "stm32f4xx")]
use embedded_hal::digital::v2::OutputPin;

#[cfg(feature = "stm32l1xx") ] // eg  Discovery STM32L100 and Heltec lora_node STM32L151CCU6
use stm32l1xx_hal::{prelude::*,
                    stm32::Peripherals,
		    gpio::{gpiob::PB6, Output, PushPull,},
                    };

#[cfg(feature = "stm32l1xx") ]
use embedded_hal::digital::v2::OutputPin;

#[entry]
fn main() -> ! {

    // setup() does all  hal/MCU specific setup and returns generic hal device for use in main code.

    // 1. Get device specific peripherals
    // 2. Take ownership of the raw rcc (Reset and Clock Control) device and convert to  HAL structs
    // 3. Configure gpio pin as a push-pull output.

    #[cfg(feature = "stm32f1xx")]
    fn setup() -> (PC13<Output<PushPull>>, AsmDelay) {

       let dp        = Peripherals::take().unwrap();
       let mut rcc   = dp.RCC.constrain();
       let mut gpioc = dp.GPIOC.split(&mut rcc.apb2);

       // return tuple  (led, delay)
       (gpioc.pc13.into_push_pull_output(&mut gpioc.crh),            // led on pc13
        AsmDelay::new(bitrate::U32BitrateExt::mhz(16)) )             // delay
       };

    #[cfg(feature = "stm32f3xx")]
    fn setup() -> (PE15<Output<PushPull>>, AsmDelay) {

       let dp        = Peripherals::take().unwrap();
       let mut rcc   = dp.RCC.constrain();
       let mut gpioe = dp.GPIOE.split(&mut rcc.ahb);

       // return tuple  (led, delay)
       (gpioe.pe15.into_push_pull_output(&mut gpioe.moder, &mut gpioe.otyper),  // led on pe15
        AsmDelay::new(bitrate::U32BitrateExt::mhz(16)) )                        // delay
       };

    #[cfg(feature = "stm32f4xx")]
    fn setup() -> (PA5<Output<PushPull>>, AsmDelay) {

       let dp    = Peripherals::take().unwrap();
       let gpioa = dp.GPIOA.split();

       // return tuple  (led, delay)
       (gpioa.pa5.into_push_pull_output(),                         // led on pa5
        AsmDelay::new(bitrate::U32BitrateExt::mhz(32)) )           // delay
       };

    #[cfg(feature = "stm32l1xx")]
    fn setup() -> (PB6<Output<PushPull>>, AsmDelay) {

       let dp    = Peripherals::take().unwrap();
       let gpiob = dp.GPIOB.split();

       // return tuple  (led, delay)
       (gpiob.pb6.into_push_pull_output(),                        // led on pb6
        AsmDelay::new(bitrate::U32BitrateExt::mhz(4)) )           // delay
       };

    // End of hal/MCU specific setup. Following should be generic code.

    let (mut led, mut delay)  = setup();

    let on  : u32 = 1000;
    let off : u32 = 3000;

    // Wait for the timer to trigger an update and change the state of the LED
    loop {
        let _r = led.set_high();  // set_high turns bluepill off, Discovery & Nucleo-64 on
        delay.delay_ms(on);
        let _r = led.set_low();   // set_low turns bluepill  on,  Discovery & Nucleo-64 off
        delay.delay_ms(off);
    }
}

@pdgilbert GPIO pins can source or sink current. Depending on which way around the LED is connected it will light up if you pull the pin low (sink) or high (source).

pins can source or sink current. Depending on which way around the LED is connected it will light up if you pull the pin low (sink) or high (source).

That's the case for the led on the bluepill, it's wired as active-low. The led cathode is the one connected to the pin, while the anode is connected to Vcc.

You do know that "the" bluepill doesn't exist? There're at least a dozen variants of that design... 😅

Thanks for explaining the reason, I suspected it might be something like that. Yes, I am aware there are different variants of bluebill, but I don't have a sense of how extensive the difference are.

Yes, I am aware there are different variants of bluebill, but I don't have a sense of how extensive the difference are.

Some do not even come with a STM32F103R8 MCU. 😅

(Just to complete this thread for anyone that might read it.)
The example in the original post does not achieve the objective of containing the hardware configuration in the setup() function and making the rest of the code generic, because of different boards wiring leds as sink or source. That is, .set_low() and .set_high() can have opposite effects on different boards. To remedy this I have added an LED trait with on and off methods defined in setup(), so .on() and .off() can be used in the generic code. The  complete revised example is below. This example will change when embedded_hal 1.0.0 is released, at least in the aspect of v2::OutputPin. A more recent version may be available at https://github.com/pdgilbert/eg_stm_hal.
//! Blink  onboard LED if one is available, or PC13 otherwise.
//! compare  blink3 example and stm32f1xx_hal example blinky.rs.
//!
//! stm32f1xx below uses PC13  which is onboard green LED on Bluepill.
//! stm32f3xx below uses PE15  which is onboard green LD6 (West) LED on STM32F303 Discovery kit.
//! stm32f4xx below uses PA5   which is onboard green LD2  LED on STM32F411RET6 Nucleo-64 board,
//!                              but can be configured to PB13.
//! stm32l1xx below uses PB6   On some STM32L1.. Discovery boards there are onboard LD3 and LD4 LEDs on PB7
//!                            and PB6 but mine are defective and so tested with off board LED on PB6.
//!

#![deny(unsafe_code)]
#![no_std]
#![no_main]

#[cfg(debug_assertions)]
extern crate panic_semihosting;

#[cfg(not(debug_assertions))]
extern crate panic_halt;

use cortex_m_rt::entry;
use asm_delay::{ AsmDelay, bitrate, };

#[cfg(feature = "stm32f1xx")]  //  eg blue pill stm32f103
use stm32f1xx_hal::{prelude::*,
                     pac::Peripherals,
                     gpio::{gpioc::PC13, Output, PushPull,},
                     };

#[cfg(feature = "stm32f1xx")]
use embedded_hal::digital::v2::OutputPin;

#[cfg(feature = "stm32f3xx")]  //  eg Discovery-stm32f303
use stm32f3xx_hal::{prelude::*,
                    stm32::Peripherals,
                    gpio::{gpioe::PE15, Output, PushPull,},
                    };

#[cfg(feature = "stm32f4xx")] // eg Nucleo-64  stm32f411
use stm32f4xx_hal::{prelude::*,
                    pac::Peripherals,
                    gpio::{gpioa::PA5, Output, PushPull,},
                    };

#[cfg(feature = "stm32f4xx")]
use embedded_hal::digital::v2::OutputPin;

#[cfg(feature = "stm32l1xx") ] // eg  Discovery STM32L100 and Heltec lora_node STM32L151CCU6
use stm32l1xx_hal::{prelude::*,
                    stm32::Peripherals,
                    gpio::{gpiob::PB6, Output, PushPull,},
                    };

#[cfg(feature = "stm32l1xx") ]
use embedded_hal::digital::v2::OutputPin;

pub trait LED {
   fn  on(&mut self)  -> () ;
   fn off(&mut self)  -> () ;
}

#[entry]
fn main() -> ! {

    // setup() does all  hal/MCU specific setup and returns generic hal device for use in main code.

    // 1. Get device specific peripherals
    // 2. Take ownership of the raw rcc (Reset and Clock Control) device and convert to  HAL structs
    // 3. Configure gpio pin as a push-pull output.

    // 4.
    // The version of bluepill tested is active-low, cathode connected to the pin and anode to Vcc,
    // so pin low is a sink and allows current flow. Other boards are wired for the GPIO pin to source.
    // Thus set_high turns the bluepill LED off and Discovery & Nucleo-64 boards LEDs on while
    //      set_low  turns the bluepill LED  on, Discovery & Nucleo-64 LEDs off.
    // To achieve generic code an LED trait is defined, with different boards having different use
    // of high and low for on and off in their implemantations.

    #[cfg(feature = "stm32f1xx")]
    fn setup() -> (PC13<Output<PushPull>>, AsmDelay) {

       let dp        = Peripherals::take().unwrap();
       let mut rcc   = dp.RCC.constrain();
       let mut gpioc = dp.GPIOC.split(&mut rcc.apb2);

       impl LED for PC13<Output<PushPull>> {
           fn   on(&mut self)  -> () { self.set_low().unwrap()  }
           fn  off(&mut self)  -> () { self.set_high().unwrap() }
           };

       // return tuple  (led, delay)
       (gpioc.pc13.into_push_pull_output(&mut gpioc.crh),      // led on pc13 with on/off
        AsmDelay::new(bitrate::U32BitrateExt::mhz(16)) )       // delay
       };

    #[cfg(feature = "stm32f3xx")]
    fn setup() -> (PE15<Output<PushPull>>, AsmDelay) {

       let dp        = Peripherals::take().unwrap();
       let mut rcc   = dp.RCC.constrain();
       let mut gpioe = dp.GPIOE.split(&mut rcc.ahb);

       impl LED for PE15<Output<PushPull>> {
           fn   on(&mut self)  -> () { self.set_high().unwrap()  }
           fn  off(&mut self)  -> () { self.set_low().unwrap() }
           };

       // return tuple  (led, delay)
       (gpioe.pe15.into_push_pull_output(&mut gpioe.moder, &mut gpioe.otyper),  // led on pe15 with on/off
        AsmDelay::new(bitrate::U32BitrateExt::mhz(16)) )                        // delay
       };

    #[cfg(feature = "stm32f4xx")]
    fn setup() -> (PA5<Output<PushPull>>, AsmDelay) {

       let dp    = Peripherals::take().unwrap();
       let gpioa = dp.GPIOA.split();

       impl LED for PA5<Output<PushPull>> {
           fn   on(&mut self)  -> () { self.set_high().unwrap()  }
           fn  off(&mut self)  -> () { self.set_low().unwrap() }
           };

       // return tuple  (led, delay)
       (gpioa.pa5.into_push_pull_output(),                         // led on pa5 with on/off
        AsmDelay::new(bitrate::U32BitrateExt::mhz(32)) )           // delay
       };

    #[cfg(feature = "stm32l1xx")]
    fn setup() -> (PB6<Output<PushPull>>, AsmDelay) {

       let dp    = Peripherals::take().unwrap();
       let gpiob = dp.GPIOB.split();

       impl LED for PB6<Output<PushPull>> {
           fn   on(&mut self)  -> () { self.set_high().unwrap()  }
           fn  off(&mut self)  -> () { self.set_low().unwrap() }
           };

       // return tuple  (led, delay)
       (gpiob.pb6.into_push_pull_output(),                        // led on pb6 with on/off
        AsmDelay::new(bitrate::U32BitrateExt::mhz(4)) )           // delay
       };

    // End of hal/MCU specific setup. Following should be generic code.

    let (mut led, mut delay)  = setup();

    let on  : u32 = 1000;
    let off : u32 = 3000;

    // Wait for the timer to trigger an update and change the state of the LED
    loop {
        let _r = led.on();
        delay.delay_ms(on);
        let _r = led.off();
        delay.delay_ms(off);
    }
}


manifest-db: propage the osbuild SHA on manifest-db

Add a bot to update the SHA dependency to OSBuild on manifest-db automatically.
The OSBuild SHA will be changed only if the manifest-db SHA was updated on the last commit landed on main. This way this ensure that CI ran successfully for this exact version of OSBuild against manifest-db's actual state. Therefore it is safe to assume that we can upgrade the manifest dependency without running the whole CI again.
Testing done:

On my fork, after this commit, I added first another one ammending the manifest-db dependency. It successfully opened a PR on manifest-db: https://github.com/osbuild/manifest-db/pull/49
Then I added a second commit on top of this one changing something else in the repo, the bot did not opened a PR on manifest-db. https://github.com/lavocatt/osbuild/actions/runs/3060823276/jobs/4939810608

Thus making this a success

https://github.com/osbuild/manifest-db/pull/52 has the latest formatting.


identify unique conditions to filter genes on

Fixes filter_genes that was broken by PR #70 - PR #70 made it permissible to pass a list of conditions to perform differential expression analysis.

This fix checks for a list type and if found, unlists and finds unique values.
This fix also reduces the conditions to unique values.

This PR is a bit unruly as problems kept presenting themselves. I don't have an explanation why this code passed checks in PR #70

Fixes tests for functions that wrapvariancePartition by creating test counts and metadata that are not rank deficient or co-linear.
Perhaps undesirable, but uses[[ to extract character vectors from the conditions list (checks for type list) that have more than 1 value.


Errors with tensorflow-gpu 2.0 alpha0

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10 Pro
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary
TensorFlow version: tensorflow-gpu 2.0 alpha0
Python version: 3.6
Installed using virtualenv? pip? conda?: pip
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: cudatoolkit 10.0.130, and cudnn 7.5
GPU model and memory: NVIDIA GTX 1070/6GB

Describe the problem
I have installed tensorflow-gpu 2.0alpha0, cudatoolkit 10.0.130, and cudnn 7.5 in a windows 10.
TensorFlow 2.0 works well with CPU, but encounters errors while running with GPU.
Errors messages are as bellow:
2019-04-02 23:47:38.646661: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2019-04-02 23:47:38.666653: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Could not dlopen library 'nvcuda.dll'; dlerror: nvcuda.dll not found
2019-04-02 23:47:38.666842: E tensorflow/stream_executor/cuda/cuda_driver.cc:318] failed call to cuInit: UNKNOWN ERROR (303)

I think the main issue is "Could not dlopen library 'nvcuda.dll'".
However, I have installed the latest NVIDIA driver (version 419.67), and 'nvcuda.dll' can be found in C:\Windows\System32\nvcuda.dll.
The issue is also posted in stackoverflow.
Provide the exact sequence of commands / steps that you executed before running into the problem
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@loveunk Could you check this issue which is similar to your issue but for older TF version. If those solutions doesn't work, could you uninstall and reinstall CUDA and cuDNN? Please let us know how it progresses. Thanks!

@jvishnuvardhan It does not work. The same error exists.

@loveunk  Could you uninstall and reinstall CUDA and cuDNN? Can you try some solutions that were listed in some of GitHub issues and Stackoverflow? This is more related to NVIDIA's CUDA so they might have solutions in their GitHub repo. Thanks!

@jvishnuvardhan I have tried several different penitential solutions, including reinstalling CUDA Toolkit and cuDNN. Unfortunately, none of them work.
Currently, it's hard to judge whether this issue is more related to CUDA than tensorflow.
I have write some test win32 application with C++ to load 'nvcuda.dll',  it can be found and loaded to the program successfully.

YMMV, but we had the same issue with tensorflow-gpu 2.0.0-beta0. Here's how we got around it:
conda create -n tf_beta python=3.6 cudnn cudatoolkit cudatoolkit-dev pip; conda activate tf_beta; pip install tensorflow-gpu==2.0.0-beta0
For alpha0, this seems to work on our 2080ti rig:
conda create -n tf_alpha python=3.6 cudnn cudatoolkit cudatoolkit-dev pip; conda activate tf_alpha; pip install tensorflow-gpu==2.0.0-alpha0
System information
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Xubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): source
TensorFlow version: tensorflow-gpu 2.0 alpha0 & beta0
Python version: 3.6
Installed using virtualenv? pip? conda?: conda with pip
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: cudatoolkit 10.0.130, and cudnn 7.5
GPU model and memory: 2x NVIDIA RTX 2080 TI / 11G x 2 (NVLink 22G)

@loveunk Is this resolved. If yes, please close the issue. Thanks!

Automatically closing this out since I understand it to be resolved, but please let me know if I'm mistaken.Thanks!


Some template improvements.

Another pr!
I've splitted the content in a content and a javascript template. This way, people are free to include the javascript template at the footer of the page. Using a jQuery independent document ready function prevents the javascript from giving an error (Uncaught ReferenceError: $ is not defined) in case jQuery is loaded at a later point. In the current situation, jQuery must be loaded before redering the template which is not the best thing from a performance perspective.
Also I moved the page title to the wrapper template. Imho this is part of styling and people might already have the title rendered in the layout template.

That's fine 👍  Thanks a lot


Incorrect export to the CustomVision service

Describe the bug
Regions exported to the Custom Vision Service do not match those previously marked up using VoTT.
To Reproduce
Steps to reproduce the behavior:

Mark up any data using VoTT
Click "Export Tags"
Select "Custom Vision Service"
Paste a training key

Expected behavior
Regions expected to be identical.
Screenshots

Platform
[x] Electron
[ ] Browser
OS
[x] Windows
[ ] Mac
[ ] Linux

+1, Also seeing cases where the images aren't being exported to Custom Vision at all, specifically with the following configuration:

Source Connection: Bing, with "person wearing yellow" as search term
Target Connection: Blob storage
Export: Custom vision
Platform: Electron
OS: Windows

I tagged ~20 photos, and only 1-3 of them get exported at all, and the ones that do get exported are still showing up as 'untagged'

+1 @arode
I've faced this issue as well when exporting images from a local folder. Not all the images were exported.

+1
seeing same behaviour from local folder - not all tagged images are exported

+1
Would make life a lot easier!

+1
I tried to export my images from VoTT to Custom Vision and none of them appeared in my Custom Vision tool. I did Create New Project for Custom Vision, and project was created, just no images were uploaded to Custom Vision.
Source Connection: Blob storage
Target Connection: Blob storage
Export: Custom vision
Platform: Electron
OS: Windows


Release 1.1.0 - Add terraform 1.1.0 support

New 1.1.x release available
Based on addition of 1.0.0 support

nice 👍


The program crashes for an unknown reason. Suspect: esp_timer_impl_lac.c  (IDFGH-14284)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
ESP-IDF v5.3.1-dirty
Espressif SoC revision.
ESP32 chip revision: v1.0
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
CMD
Development Kit.
Custom Board
Power Supply used.
External 5V
What is the expected behavior?
Particle system run as usual...
What is the actual behavior?
after half second crash
Steps to reproduce.
run program.
click 3 times.
particle system run.
some particles emitted.
Crash.
Debug Logs.
load:0x40080404,len:4060                                                                                entry 0x400806b8                                                                                I (30) boot: ESP-IDF v5.3.1-dirty 2nd stage bootloader                                                                                I (30) boot: compile time Dec 22 2024 08:28:07                                                                                I (30) boot: Multicore bootloader                                                                                I (35) boot: chip revision: v1.0                                                                                I (39) boot.esp32: SPI Speed      : 40MHz                                                                                I (44) boot.esp32: SPI Mode       : DIO                                                                                I (48) boot.esp32: SPI Flash Size : 4MB                                                                                I (53) boot: Enabling RNG early entropy source...                                                                                I (58) boot: Partition Table:                                                                                I (62) boot: ## Label            Usage          Type ST Offset   Length                                                                                I (69) boot:  0 nvs              WiFi data        01 02 0000a000 00006000                                                                                I (76) boot:  1 phy_init         RF data          01 01 00010000 00001000                                                                                I (84) boot:  2 factory          factory app      00 00 00020000 00200000                                                                                I (91) boot:  3 storage          Unknown data     01 82 00220000 00100000                                                                                I (99) boot: End of partition table                                                                                I (103) esp_image: segment 0: paddr=00020020 vaddr=3f400020 size=3715ch (225628) map                                                                                I (168) esp_image: segment 1: paddr=00057184 vaddr=3ffb0000 size=03f90h ( 16272) load                                                                                I (173) esp_image: segment 2: paddr=0005b11c vaddr=40080000 size=04efch ( 20220) load                                                                                I (180) esp_image: segment 3: paddr=00060020 vaddr=400d0020 size=c676ch (812908) map                                                                                I (385) esp_image: segment 4: paddr=00126794 vaddr=40084efc size=11c20h ( 72736) load                                                                                I (418) boot: Loaded app from partition at offset 0x20000                                                                                I (418) boot: Disabling RNG early entropy source...                                                                                I (430) cpu_start: Multicore app                                                                                I (438) cpu_start: Pro cpu start user code                                                                                I (438) cpu_start: cpu freq: 240000000 Hz                                                                                I (438) app_init: Application information:                                                                                I (441) app_init: Project name:     PromoDisplayPrj                                                                                I (447) app_init: App version:      1                                                                                I (451) app_init: Compile time:     Dec 22 2024 08:27:58                                                                                I (457) app_init: ELF file SHA256:  a55b8d066251da6c...                                                                                I (463) app_init: ESP-IDF:          v5.3.1-dirty                                                                                I (468) efuse_init: Min chip rev:     v1.0                                                                                I (473) efuse_init: Max chip rev:     v3.99                                                                                I (478) efuse_init: Chip rev:         v1.0                                                                                I (483) heap_init: Initializing. RAM available for dynamic allocation:                                                                                I (490) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM                                                                                I (496) heap_init: At 3FFBB9D0 len 00024630 (145 KiB): DRAM                                                                                I (502) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM                                                                                I (509) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM                                                                                I (515) heap_init: At 40096B1C len 000094E4 (37 KiB): IRAM                                                                                I (523) spi_flash: detected chip: generic                                                                                I (526) spi_flash: flash io: dio                                                                                I (533) gpio: GPIO[0]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0                                                                                I (539) : EventPool Constructor. numOfLayer = 1                                                                                I (544) StateManager: Reset all settings done.                                                                                I (550) main_task: Started on CPU0                                                                                I (560) main_task: Calling app_main()                                                                                I (560) app_main() : : PromoDisplay by -=Diyarov.Denis=- 2024. @mexito                                                                                I (580) >>> nvs_init(): : NVS partition inited ok.                                                                                I (630) spiffs_init_f(): : Mount: ok.                                                                                Partition size: total: 956561, used: 542662. (percentage: 56.730515)                                                                                This is esp32 chip with 2 CPU core(s), WiFi/BT/BLE, silicon revision v1.0, I (640) displayTask: ====================================================================================                                                       I (640) MEM INFO: : smallest amount of stack mem for DisplayTask = 11744                                                                                I (650) displayTask: ========================[ D E B U G........B U I L D ]==============================                                                                                I (650) MEM INFO: : free: 207844, minFree: 207844                                                                                I (660) displayTask: ====================================================================================                                                                                I (680) leddisplay: (64 * 1)x32 (8bits)                                                                                I (680) leddisplay: frame buffers: size=32768 (available total=207640, largest=110592)                                                                                I (700) leddisplay: init done                                                                                I (700) HUB75Display::: leddisplay driver init OK. 8-)                                                                                I (1410) MainScene: clicks = -1                                                                                I (1670) MEM INFO: : smallest amount of stack mem for DisplayTask = 11688                                                                                I (1670) MEM INFO: : free: 121124, minFree: 121092                                                                                I (2670) MEM INFO: : smallest amount of stack mem for DisplayTask = 11688                                                                                I (2670) MEM INFO: : free: 121124, minFree: 121092                                                                                I (2910) MainScene: clicks = 3                                                                                I (3670) MEM INFO: : smallest amount of stack mem for DisplayTask = 11688                                                                                I (3670) MEM INFO: : free: 118924, minFree: 118924                                                                                I (4670) MEM INFO: : smallest amount of stack mem for DisplayTask = 11688                                                                                I (4670) MEM INFO: : free: 118484, minFree: 118308                                                                                Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.                                                                                Core  1 register dump:                                                                                PC      : 0x400da48b  PS      : 0x00060830  A0      : 0x800dc769  A1      : 0x3ffcc2a0                                                                                0x400da48b: ParticleEmitter::emit(long) at C:/MyDevEnv/Projs/PromoDisplay/CodeESP32/components/particles/src/ParticleEmitter.hpp:856                                                                                A2      : 0xfffda810  A3      : 0x00000013  A4      : 0x3ffb5fa0  A5      : 0x00000000                                                                                A6      : 0x3ffb60b0  A7      : 0x3ffdb910  A8      : 0xfa000000  A9      : 0x00000000                                                                                A10     : 0x2b400000  A11     : 0x00000000  A12     : 0x11c40000  A13     : 0x3ffda81c                                                                                A14     : 0x3ffda828  A15     : 0x3ffdb970  SAR     : 0x0000000a  EXCCAUSE: 0x0000001c                                                                                EXCVADDR: 0xfffda894  LBEG    : 0x40082dc1  LEND    : 0x40082dc9  LCOUNT  : 0x00000027                                                                                0x40082dc1: esp_timer_impl_get_counter_reg at C:/Espressif_v5/frameworks/esp-idf-v5.3.1/components/esp_timer/src/esp_timer_impl_lac.c:119                                                                                0x40082dc9: esp_timer_impl_get_counter_reg at C:/Espressif_v5/frameworks/esp-idf-v5.3.1/components/esp_timer/src/esp_timer_impl_lac.c:129                                                                                Backtrace: 0x400da488:0x3ffcc2a0 0x400dc766:0x3ffcc330                                                                                0x400da488: ParticleEmitter::emit(long) at C:/MyDevEnv/Projs/PromoDisplay/CodeESP32/components/particles/src/ParticleEmitter.hpp:853                                                                                0x400dc766: ParticleSystem::run(long) at C:/MyDevEnv/Projs/PromoDisplay/CodeESP32/components/particles/src/ParticleSystem.hpp:144                                                                                (inlined by) displayTask(void*) at C:/MyDevEnv/Projs/PromoDisplay/CodeESP32/main/display/displayTask.cpp:2925

More Information.
There is plenty of memory, and the same code runs perfectly on a PC. During execution, no specific calls are made except for rendering on HUB75.

Crash seems to be coming from 0x400da488: ParticleEmitter::emit(long) at C:/MyDevEnv/Projs/PromoDisplay/CodeESP32/components/particles/src/ParticleEmitter.hpp:853 accessing an invalid address 0xfffda894.
Does not seem related to esp_timer_impl_lac from what I can see

Crash seems to be coming from 0x400da488: ParticleEmitter::emit(long) at C:/MyDevEnv/Projs/PromoDisplay/CodeESP32/components/particles/src/ParticleEmitter.hpp:853 accessing an invalid address 0xfffda894.
Does not seem related to esp_timer_impl_lac from what I can see

I think I found the problem. It's stack and heap overlap.

Marking this as closed then as it seems to be not an issue with esp-idf.


Revert "fix: [BD-46] skeleton.css for both dev and prod (#2531)"

This reverts commit 7e96a0a6bba91f3a00a85d3fd40a7c3afb26b4d1.
Description
Reverts #2531 as it still seems to be causing issues for consuming MFEs (e.g., frontend-template-application). That is, an MFE was unable to start/build with the changes in this prior commit even though testing the same MFE through module.config.js worked without issue.
Deploy Preview
n/a
Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[ ] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

:tada: This PR is included in version 21.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Doc] Add doc for some math functions

Signed-off-by: Tao Li<EMAIL_ADDRESS>What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[x] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Add doc for some math functions: cos,acos,cosh,sin,asin,sinh,tan,atan,tanh.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

should add the new added to docs/TOC.md too.

Thanks @imay for your review. I updated TOC.md.


Mean pooling function.

Hi sockeye dev, if we want to add a mean pooling function for the pytorch backend sockeye, where should the function be included? Or is there already a similar function in sockeye?
def mean_pooling(enc_feats, src_masks=None):
    """
    :param enc_feats: Tensor x Batch x Channel
    :param src_masks: Batch x Tensor
    """
    if src_masks is None:
        enc_feats = enc_feats.mean(0)
    else:
        src_masks = (~src_masks).transpose(0, 1).type_as(enc_feats)
        enc_feats = (
            (enc_feats / src_masks.sum(0)[None, :, None]) * src_masks[:, :, None]
        ).sum(0)
    return enc_feats

It does not exist in Sockeye yet. The location of that function depends on where in the model you want to use it. Where do you want to apply mean pooling?

Closing for now.  Feel free to reopen if you have other questions.


build symmetric adjacency matrix

Hi,
Just curious about this line in utils/load_data
adj = adj + adj.T.multiply(adj.T > adj) - adj.multiply(adj.T > adj)
Seems like it fails due to the comparison which makes it boolean. Is it even needed ? As I see it , the adjacency matrix is already symmetric with a shape of (2708, 2708).

Yes, I think the adjacency matrix is "symmetric" in shape, but it is not necessarily a symmetric matrix (i.e., A^T = A). Maybe try a different python/numpy version or add an explicit conversion to float if you get an error. Feel free to submit a pull request with a fix.


About solenoid

Hello,
It's a really interesting keyboard, it's a really nice piece of work, I'm especially interested in his solenoids, "da da da", sounds great, but the best I can find on my local shopping site The parameters of the solenoid valve are DC3V 0.5A; DC5V (0.83A, 0.41A), I want to know which one should I choose, I am looking forward to your answer, thank you

I would go with the 3v one just to be safe. The 5v one might work depending on how much power your other components are drawing. Hard to predict without actually trying it out.

Thank you very much for your answer,
I will give it a try and I will come back and let you know when I get the results

Hi, did you try successfully? Solenoid with 5V working?

I was not able to get a 5V solenoid working.  Only a 4.5V worked for me, so I would not go higher than that.

Sorry, I'm not allowed to receive courier due to the novel coronavirus epidemic in my area, so I haven't tried it yet, but I think 3v should work

I've received confirmation that a 3v solenoid works.


CLI: Add support for changing configuration during update

Is your feature request related to a problem? Please describe.
If the value definitions of a package are different between versions, it is sometimes not possible to update safely. Particularly, if a new required value is added, it is not possible to update at all.
Describe the solution you'd like
When running glasskube update to update a package with configuration values, the user should be asked if they want to change the configuration. If they answer yes, the configuration wizard should be started.

Hey @Harshitk-cp! I would be happy to assign you this issue once your other PRs are approved and merged. Due to a recent influx of external contributions, PR reviews can take a little longer than usual, so please have some patience until we get to yours :pray:

hey! got a PR merged yesterday might i pick this up now?

@kosmoz can you give bit more detail on this? also how does the configuration wizard updates the value definitions of the package, is it implemented somewhere?

I imagine it something like this (pseudo code):
For each package to be updated:
  Fetch the manifest for the new version
  If it has at least one value definition:
    Ask the user if they want to update the configuration
    If they agree run the config wizard (see below)

For an example, take a look at cmd/glasskube/cmd/configure.go:
https://github.com/glasskube/glasskube/blob/9b6f854396a229d76adb0512aa259b8a2bb8a8a2/cmd/glasskube/cmd/configure.go#L60-L68


[Feature Request] Better support for w4a8 quantization

Based on this doc, we have to use deepcompressor to build prepare fake-quantized checkpoint. However, it's a lot more trouble to set up that repo and it seems to me that tool is not being maintained well, especially for new llama models like 3.1/3.2. At least I was not able to do it successfully for llama 3.1 8b.
It would be great if we can add more native support for w4a8 quantization in the trtllm.

@Barry-Delaney  would u plz add comments here?

Hi,
Our officially supported toolkit for quantization is ModelOpt. We have discussed before and found that it is not trivial to land the techniques used by DeepCompressor (such as asymmetric quantization, double quantization, rotation, smoothing etc) into ModelOpt. At least in the near future we need to rely on DeepCompressor.
If you find problems on quantizing new models, could you try to do some implementation as DeepCompressor has an abstraction layer for models like this? You could also raise an issue in the DeepCompressor library and paste the errors in detail. The authors of DeepCompressor would be glad to answer.
Thank you!

Thanks! I have filed https://github.com/mit-han-lab/deepcompressor/issues/38.
BTW if we can fix these issues: https://github.com/NVIDIA/TensorRT-LLM/issues/2602, https://github.com/NVIDIA/TensorRT-LLM/issues/2603, https://github.com/NVIDIA/TensorRT-LLM/issues/2604, we can at least use w8a8. But today we can't even use w8a8.


changes for nightly debian/ubuntu builds to latest tag

changes for nightly debian/ubuntu builds to latest tag

Fixes: #9
Signed-off-by<EMAIL_ADDRESS>


Deploy IDE with Tact v1.5.0 support when it lands on NPM

And utilize the updated TextMate grammar once https://github.com/tact-lang/tact-sublime/issues/22 gets resolved


AzCopy CompletedWithSkipped

Which version of the AzCopy was used?
10.14.1
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)
Linux
What command did you run?
azcopy copy "/mnt/confprod-1/attachments/ver003/nonspaced/[161-249]*" "https://j1d08c6a8spstg.file.core.windows.net/jiraprod/AzCopyConfluenceMarch13\nonspaced?xxx" --check-length=false --recursive=true --log-level=ERROR --overwrite=ifSourceNewer
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
What problem was encountered? Many files were skipped. The output is shown below
Job 3a88057a-9e31-c246-7caa-cb5548fbe23a summary
Elapsed Time (Minutes): 976.0547
Number of File Transfers: 1804570
Number of Folder Property Transfers: 1863389
Total Number of Transfers: 3667959
Number of Transfers Completed: 2740959
Number of Transfers Failed: 0
Number of Transfers Skipped: 927000
TotalBytesTransferred:<PHONE_NUMBER>33
Final Job Status: CompletedWithSkipped
How can we reproduce the problem in the simplest way?
You can try to reproduce the problem if you have many child folders at the source.
Have you found a mitigation/solution?
No

Hi @grsa0704 Could you please share your AzCopy logs?

output10.txt
output8.txt
I am attaching 3 output files and logs files as well.
output9.txt

@grsa0704 Could you reshare the logs? I can only see the output files here.

ad5bad70-50c1-8848-65b6-6708b455af8c.zip
4c2f6412-98ae-5b49-600b-a4d5c0e33bb9.zip
3a88057a-9e31-c246-7caa-cb5548fbe23a.zip

@grsa0704 Do some of these files already exist in the destination?

No, the destination is a new empty folder. But shouldn't it just overwrite the files if they already exist?

My understanding is that AzCopy will mark and "older" files as Skipped.

Yes, we have a lot of files to be copied, so I had to split the files and run AzCopy multiple times. All the commands ran at the same time. I will try again without ifSourceNewer

Are there any other parameters that I can add to complete the execution faster? Currently, this command runs for more than 15 hours.

Can we run multiple AzCopy executions on a single VM at the same time?

As long as the paths arent overlapping, it should be fine.

All the commands have a different source location but the destination is the same. Below are the sample commands
azcopy copy "/mnt/confprod-1/attachments/ver003/[0-25]*" "https://j1d08c6a8spstg.file.core.windows.net/confprod/AzCopyConfluenceMarch15?xxx" --check-length=false --recursive=true --log-level=ERROR
azcopy copy "/mnt/confprod-1/attachments/ver003/[26-50]*" "https://j1d08c6a8spstg.file.core.windows.net/confprod/AzCopyConfluenceMarch15?xxx" --check-length=false --recursive=true --log-level=ERROR
We have to copy more than 100M files from source to destination, so we are dividing the files and running 13 AzCopy commands at the same time.

@grsa0704 are you still encountering the CompletedWithSkipped issue when you run the command without overlapping paths and start from an empty container?

@gapra-msft We have to copy more than 100M files from source to destination. I will confirm you in the next week.

@gapra-msft We are still seeing some errors. Please find the attached logs.
3b25b9f2-7428-1648-4e82-93d9b68a5c9f.log
89064235-40c3-7e45-5983-c9215b299c12.log
b2343372-6370-e943-4756-b5f64ebd6022.log
cad9b217-6aa6-af42-6883-5a68e5db5cec.zip

@gapra-msft @adreed-msft
Would you please let us know how to fix the error?

@grsa0704 We are unable to see any evidence of skipped files in the current log. Could you please set the log level to WARN (or even DEBUG) so we can see more information in the logs?

Closing due to inactivity. Please reopen if you are still experiencing this issue.


Add UI pages for result history

Closes https://github.com/mlcommons/mobile_app_open/issues/320

Screenshots

comment by @Mostelk: add mechanism to delete history

I have added arrow icons into the table of benchmarks.


Png image is being converted to jpg when selected from gallery in case of iOS

If you are creating an issue for a BUG please fill out this information. If you are asking a question or requesting a feature you can delete the sections below.
Failure to fill out this information will result in this issue being closed. If you post a full stack trace in a bug it will be closed, please post it to http://gist.github.com and then post the link here.
Bug Information
Version Number of Plugin: 2.6.2
Device Tested On: Any iOS Device
Simulator Tested On: Any iOS Simulator
Version of VS: Testing it on Mac Mini
Version of Xamarin: <IP_ADDRESS>
Versions of other things you are using: -
Steps to reproduce the Behavior
Just select a png photo from gallery using following code snippet
Expected Behavior
Image should be png and file path should end with .png
Actual Behavior
Image is jpg and filepath is ending with .jpg
Code snippet
if (CrossMedia.Current.IsPickPhotoSupported)
                        {
                            string filePath = null;

                            using (MediaFile file = await CrossMedia.Current.PickPhotoAsync())
                            {
                                InsightsFacade.Track("ImageReceivedFromGallery");

                                if (file != null)
                                {
                                    filePath = file.Path;

                                    if (filePath != null)
                                        await this.OnPhotoReceived(filePath);
                                }
                            }
                        }

Screenshotst

I think iOS store images in gallery as .jpg by default, try to take a photo with the camera an you will see is a .jpg

Everything is stored as jpg by design

@jamesmontemagno
I suggest you re-open this. The gallery can store PNG files and you can get them back as PNG files.
I just had a case where a customer added a PNG file to the gallery and when getting it back it lost transparency because it was returned as a jpg. However I was able to have them workaround this issue by creating their own dependency service, checking the path of the image returned from the iOS UIImagePickerController and if it is PNG, then you can create a stream as a PNG. So it is possible to store and retrieve PNG images in the iOS photo gallery. The line where you are forcing the image to be a JG is here:
https://github.com/jamesmontemagno/MediaPlugin/blob/master/src/Media.Plugin/iOS/MediaPickerDelegate.cs#L477
Our guide for a Forms pick photo dependency service does the same thing:
https://docs.microsoft.com/en-us/xamarin/xamarin-forms/app-fundamentals/dependency-service/photo-picker#ios-implementation
See this code:
void OnImagePickerFinishedPickingMedia(object sender, UIImagePickerMediaPickedEventArgs args)
    {
        UIImage image = args.EditedImage ?? args.OriginalImage;

        if (image != null)
        {
            // Convert UIImage to .NET Stream object
            NSData data = image.AsJPEG(1);
            Stream stream = data.AsStream();
            ...
    }

The above forces the image to be returned to the caller as a JPG, but if you do this:
void OnImagePickerFinishedPickingMedia(object sender, UIImagePickerMediaPickedEventArgs args)
    {
        UIImage image = args.EditedImage ?? args.OriginalImage;

        if (image != null)
        {
            // Convert UIImage to .NET Stream object
            NSData data;
            if (args.ReferenceUrl.PathExtension == "PNG" || args.ReferenceUrl.PathExtension == "png")
                data = image.AsPNG();
            else
                data = image.AsJPEG(1);
            Stream stream = data.AsStream();
            ...
    }

Then you get a PNG back. There would seem to be no reason why you can't do similar in this library.
I will work on a pull request.

@Nerololo
Yes, if you take a picture, it will store as a JPEG, but there are other ways to get images into the Photos app, like saving a PNG image from a website for one.
I just did a pull request that should fix this issue. It checks the file extension of the selected image, and if a PNG saves it and passes it back as a PNG instead of a JPG.


Add type to outputs and transactions in DB and API

:clipboard: Add associated issues, tickets, docs URL here.
Overview
Describe what your Pull Request is about in a few sentences.
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Change 1
Change 2
...

Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.

Coverage remained the same at ?% when pulling 542b5248e85b1e62e23008407eae37019d3922dd on mederic-p/53-store-tx-type into fabb45fb909ec68b85908a7eb19a79329eaf56b9 on master.


TDX: Add support for kernel IPI offloading (needs kernel version bump)

The user<-> kernel transitions during IPI handling incur a significant amount of overhead on both the send and receive sides. These changes support handling IPIs entirely in-kernel, eliminating these transitions.
(Needs kernel PR to be merged and kernel version bumped)

Marking as non-draft & ready for review since the only additional change will be a kernel package bump. GitHub copy of the kernel PR: https://github.com/microsoft/OHCL-Linux-Kernel/pull/26

While we're making kernel changes in this area, can we also make whatever changes are needed for the same code to support Guest VSM (i.e. separate tracking of interrupts for VTL 0 and VTL 1)? We're going to need it at some point. We need it for SNP too.

This is going to conflict with #470.

LGTM but we'll need to update the kernel first.

While we're making kernel changes in this area, can we also make whatever changes are needed for the same code to support Guest VSM (i.e. separate tracking of interrupts for VTL 0 and VTL 1)? We're going to need it at some point. We need it for SNP too.

The new version only turns on kernel offloading if the next vtl is vtl0. Is that sufficient for now?

Honestly I don't think I'm familiar enough with offloading to say for sure. But my understanding is it's solely a perf improvement, and not needed functionality, correct? And if we combine that with believing that VTL 1 will be running a very small percentage of the time compared to VTL 0, and will not be receiving many interrupts, then maybe this perf change isn't necessary for it?

While we're making kernel changes in this area, can we also make whatever changes are needed for the same code to support Guest VSM (i.e. separate tracking of interrupts for VTL 0 and VTL 1)? We're going to need it at some point. We need it for SNP too.

The new version only turns on kernel offloading if the next vtl is vtl0. Is that sufficient for now?

Honestly I don't think I'm familiar enough with offloading to say for sure. But my understanding is it's solely a perf improvement, and not needed functionality, correct? And if we combine that with believing that VTL 1 will be running a very small percentage of the time compared to VTL 0, and will not be receiving many interrupts, then maybe this perf change isn't necessary for it?

Definitely yes on "solely a perf improvement, and not needed functionality", and my understanding is yes for the second


[Bug] Hide Recommendation does not work at all

内容の詳細
I still can see Recommended Songs, Trending videos from boom, and Openchats with disgusing skibidi stuff.
再現する手順
No need to explain here, enable hide recommendation and there is issue.
モジュールのバージョン
1.4
LINEアプリのバージョン
14.1.3

LIME v1.4 only supports LINE v14.0.2.
I released LIME v1.5, which is compatible with LINE v14.1.3. Give it a try.
https://github.com/Chipppppppppp/LIME/releases/tag/v1.5


Genome browser: show feature + 3000bp flanks

feature level page -> genome browser -> it shows only feature, no flanking region.
It should show features + 3000bp regions on either side to show the context.
-Maulik

Fixed at least from the feature view Genome Browser tab. If there are other ways to get there they will have to be modified as well.


Example of csp pandas extension type functionality

Create a new (crude) example of the pandas extension type functionality to illustrate basic usage.

Closed by https://github.com/Point72/csp/pull/110


menue item is not defined

MenuItem' isn't a function. (Documentation)  Try correcting the name to match an existing function, or define a method or function named 'MenuItem'.
The name 'MenuItem' is defined in the libraries 'package:flutter/src/widgets/platform_menu_bar.dart' and 'package:flutter_admin_scaffold/src/menu_item.dart (via package:flutter_admin_scaffold/admin_scaffold.dart)'. (Documentation)  Try using 'as prefix' for one of the import directives, or hiding the name from all but one of the imports.

how to solve

@shahid123-hue
see: https://stackoverflow.com/questions/19723063/what-is-the-difference-between-show-and-as-in-an-import-statement
example:
import `package:flutter_admin_scaffold/admin_scaffold.dart` hide MenuItem;

or
import `package:flutter_admin_scaffold/admin_scaffold.dart` as admin_scaffold;

try it!


added provisions for password field

Added frontend support for the password field type. Specifically for the MQTT password., but will work with any other field deemed sensitive by changing the data type to 'p' instead of 's'.

A little improvement, no longer clear text UI, but password. It's still interceptable, but better than it was. Thanks to @DutchessNicole :)


Reef admins

Add reef-to-admin table (custom intermediate table for manyToMany relationship between admin and reef)
Change reef \ admin relationship from manyToOne (users can have many reefs but a reef has only one admin) to manyToMany (reefs now can have more than one admin)
Refactor reef endpoints to follow the manyToMany relationship between user and reef
Add IsReefAdminGuard to restrict access to reef_managers to only their reefs
Refactor surveys endpoints:

Change survey's global prefix to reefs/:reef_id/surveys so that we always track the reef_id, which is needed for IsReefAdminGuard
Change GET /surveys/reefs/:id to /reefs/:reef_id/surveys
Make necessary changes in the DTOs and survey service

Some front-end refactor is needed due to the prefix change
Related issue: https://github.com/aqualinkorg/aqualink-app/issues/111

@avalmas-programize can you list the necessary frontend changes? Or even have a stab at them? They shouldn't be too complicated at the moment.

Front-end changes:
All surveys/ endpoints URLs should changes:

POST /surveys/                                => POST /reefs/:reef_id/surveys/
POST /surveys/:survey_id/media/    => POST /reefs/:reef_id/surveys/:survey_id/media/
POST /surveys/upload/                     => POST /reefs/:reef_id/surveys/upload/
GET /surveys/reefs/:reef_id              => GET /reefs/:reef_id/surveys/
GET /surveys/:survey_id/                  => GET /reefs/:reef_id/surveys/:survey_id/
GET /surveys/:survey_id/media/       => GET /reefs/:reef_id/surveys/:survey_id/media/
PUT /surveys/:survey_id/                  => PUT /reefs/:reef_id/surveys/:survey_id/
PUT /surveys/media/:media_id/        => PUT /reefs/:reef_id/surveys/:survey_id/
DELETE /surveys/:survey_id/           => PUT /reefs/:reef_id/surveys/:survey_id/
DELETE /surveys/media/:media_id/ => PUT /reefs/:reef_id/surveys/:survey_id/

I have added the Public decorator. Implementation:

Override method AuthGuard('custom').canActivate so that it will not apply the strategy if isPublic equals to true
Override Levels and ReefAdmin guards to return true if isPublic equals to true
Add OverrideLevelAccess decorator which overrides the level defined in the Auth decorator on the Controller in order to have different level of access per Controller
Refactor Auth decorator in order for the above change to work without re-applying extra decorators

When I tried it, I did not get promoted to "reef_manager" in the DB for some reason.
But I am actually wondering if this is still useful, if a user has a reef - user row, we can probably assume that they are an admin this way. And just keep default / super_admin
Thoughts @avalmas-programize @bencpeters

No I think keeping all three roles is much useful and easier to maintain.
Also there was a bug regarding the promotion of the user to reef_manager.
Saves after the update operation for the user promotion were reverting the level of the user to their prior one.
Added a new commit that resolves this.


Rename to Host.swift to match the class name

A subset of #739.

@swift-ci please test and merge

The failure looks unrelated.

@swift-ci please test


Ubuntu 18.04 freeze after each reboot

Hello all,
I´m running Ubuntu 18.04. Since last week I´ve been struggling with rapid freezing - it appears after approximatelly 5 minutes. The only way is to reboot the system. I haven´t performed any update.
The details of Ubuntu. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic
When typing "uname -r" the result is: 4.4.0-18362-Microsof. linux-generic-hwe-18.04 is already the newest version (<IP_ADDRESS>.99). xserver-xorg-hwe-18.04 is already the newest version (1:7.7+19ubuntu8~18.04.3).
I´ve tried many corrections I googled but still without any success. I´m new to Ubuntu. Please, could you help me? Where is the problem?
Thanks a lot Regards Adam

You are talking about Ubuntu in WSL. Is WSL freezing? Is it related to VSCode or not?
If its a WSL issue and not VSCode related, you need to file the issue against https://github.com/microsoft/WSL

the problem is related to to WSL thus I file the issue in https://github.com/microsoft/WSL. Closing the case. Thanks.


[Exceptions] Request-Level Filtering

Summary
Adds basic filtering to /exceptions via a POST. This does not restrict which exceptions are stored (that will come in a later PR), just which ones are shown for a given request.
There are a few areas in this PR where I expect some discussion (and potentially changes) - I'll try to call a few of them out explicitly down below.
Also, this PR looks a lot bigger than it is (a lot of it is docs/tests) - most of the real changes are confined to a handful of files.

Release Notes Entry

Summarizing what was discussed earlier regarding fuzzy-matching - the current iteration of this change no longer includes simple names or fuzzy matching (everything must be fully written out). To improve our standardization, omitting this for now gives us more flexibility to add it (potentially using wildcards) in the future, without locking us into anything for this PR or establishing a one-off mechanism.