tests/net/mgmt/testcase.yaml#test :failed due to un-handled exception

Testcase :--tests/net/mgmt/testcase.yaml#test @ esp32:xtensa COMPLETION failed
This testcase is failed due to unhandled exception.
The failure report are pasted below :--
Detailed description
configure passed
Build procedure :--
build passed: 'mkdir -p /outdir-ari3-asid-esp32; outdir-ari3-asid-esp32/.config'
build passed: 'make -j -C zephyr/tests/net/mgmt/
EXTRA_CFLAGS="-Werror -Wno-error=deprecated-declarations"
KCPPFLAGS=-DTC_RUNID=:asid
BOARD=esp32 ARCH=xtensa
O=/outdir-ari3-asid-esp32 initconfig'
build output: Using zephyr/boards/xtensa/esp32/esp32_defconfig as base
build output: Merging /zephyr/tests/include/test.config
build output: Merging prj.conf
build output: outdir-ari3-asid-esp32/boot_config.conf
build output: # configuration written to .config
build passed: 'make -j -C zephyr/tests/net/mgmt
EXTRA_CFLAGS="-Werror -Wno-error=deprecated-declarations"
KCPPFLAGS=-DTC_RUNID=:asid
BOARD=esp32 ARCH=xtensa
O=outdir-ari3-asid-esp32'
build passed
make flash
Reset
eval failed: found expected (for failure) (USAGE FAULT|[Ff]atal fault in ) in console esp32 :default at 1.35s
console output: Running test suite test_mgmt_fn
console output: ===================================================================
console output: starting test - test_mgmt
console output: Starting Network Management API test
console output: - Request Net MGMT
console output: - Sending event 1 times, without a receiver, without info
console output:         Throwing event 0x97ab1234 1 times
console output: - Sending event 2 times, without a receiver, without info
console output:         Throwing event 0x97ab1234 2 times
console output: - Sending event 1 times, with a receiver, without info
console output:         Throwing event 0x97ab1234 1 times
console output:                 Received event 0x97ab1234
console output:         Received 0x97ab1234 1 times
console output: - Sending event 2 times, with a receiver, without info
console output:         Throwing event 0x97ab1234 2 times
console output:                 Received event 0x97ab1234
console output:                 Received event 0x97ab1234
console output:         Received 0x97ab1234 2 times
console output: - Sending event 1 times, without a receiver, with info
console output:         Throwing event 0x97ab1234 1 times
console output:         Throwing event 0x97ab1234 1 times
console output:                 Received event 0x97ab1234
console output:         Received 0x97ab1234 1 times
console output: - Sending event 2 times, with a receiver, without info
console output:         Throwing event 0x97ab1234 2 times
console output:                 Received event 0x97ab1234
console output:                 Received event 0x97ab1234
console output:         Received 0x97ab1234 2 times
console output: - Sending event 1 times, without a receiver, with info
console output:         Throwing event 0x97ab1234 1 times
console output: - Sending event 2 times, without a receiver, with info
console output:         Throwing event 0x97ab1234 2 times
console output: - Sending event 1 times, with a receiver, with info
console output:         Throwing event 0x97ab1234 1 times
console output:                 Received event 0x97ab1234
console output:         Received 0x97ab1234 1 times
console output: - Sending event 2 times, with a receiver, with info
console output:         Throwing event 0x97ab1234 2 times
console output:                 Received event 0x97ab1234
console output:                 Received event 0x97ab1234
console output:         Received 0x97ab1234 2 times
console output: - Triggering core event: 0xf0600001
console output:                 Received event 0xf0600001
console output: - Triggering core event: 0xf0600002
console output:                 Received event 0xf0600002
console output: - Synchronous event listener
console output:         Throwing event 0x97ab1234 2 times
console output: *** Unhandled exception ****
console output: Exception cause 28 (load prohibited):
console output:   EPC1     : 0x40086386 EXCSAVE1 : 0x8008827d EXCVADDR : 0x00000010
console output: Program state (PS):
console output:   INTLEVEL : 03 EXCM    : 0 UM  : 1 RING : 0 WOE : 1
console output:   OWB      : 04 CALLINC : 2
console output: Current thread ID = 0x3ffb2214
console output: Faulting instruction address = 0xdeaddead
console output: Fatal fault in ISR! Spinning...
evaluation failed

can't reproduce, also esp32 is currently not a platform where networking is supported.


Update to allow for using dtype_numpy key alongside old dtype_str

Description
Allow for using dtype_numpy keyword as specified in ophyd async
Motivation and Context
Decision was made to use dtype_numpy for the machine data type of resources in ophyd_async this change allows for using it alongside the older dtype_str

We have a number of ohpyd devices on the floor that are using 'dtype_str'.  To ease converting them, I think we should apply some normalization in describe and convert 'dtype_str' -> 'numpy_dtype' silently for now and then loudly in the future.
This means we will stop putting funny data in the databases but do not have to do a flag-day on getting all the devices on the floor fixed and we do not have any "can not roll back" changes made for a while.

In the case of "announcing it loudly", what is the best mechanism for this? Raising a warning of some kind? Should that be done somewhere here in the bluesky codebase, or in ophyd?

I think a release where we silently fix it and then warnings.warn for a while ("loud") so it would show up in the terminal.
I don't think we ever want to reject dtype_str so long term I can see a case of fixing-and-warning forever or warning for a bit and then just letting it pass (once we are sure dtype_str has fallen out of memory ;) ).


Add XTest_tabpage_cmdheight to gitignore

Running make test generates src/testdir/XTest_tabpage_cmdheight.
Add this to .gitignore and ignore it.
$ cat src/testdir/XTest_tabpage_cmdheight
set laststatus=2
set cmdheight=2
tabnew
set cmdheight=3
tabnext
redraw!
echo "hello\nthere"
tabnext
redraw

i think this should be deleted in the testfile at the end.

@chrisbra Thanks!
I found a place where I tried to delete another file from the file created in the test.
I will submit another modified pull request.


[Bug]: collection.query and peek error in version 0.5.17

What happened?
Calling collection.query or collection.peek in client/server mode breaks when server is running 0.5.17, whereas they work in 0.5.16. Minimal example:
import chromadb

client = chromadb.HttpClient(host='localhost', ssl=False, port=8000)

collection = client.create_collection(name="test")

collection.add(
    documents=[
        "This is a document about pineapple",
        "This is a document about oranges"
    ],
    ids=["id1", "id2"]
)

print(collection.get('id1')) # <----- This works

print(collection.query(query_texts=['hawaii'])) #  <----- But this fails

Versions
0.5.17 (run locally with Docker)
Relevant log output
Traceback (most recent call last):
  File "/Users/henry/Library/Caches/pypoetry/virtualenvs/llm-kCwWOmYK-py3.12/lib/python3.12/site-packages/chromadb/api/base_http_client.py", line 99, in _raise_chroma_error
    resp.raise_for_status()
  File "/Users/henry/Library/Caches/pypoetry/virtualenvs/llm-kCwWOmYK-py3.12/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status
    raise HTTPStatusError(message, request=request, response=self)
httpx.HTTPStatusError: Client error '400 Bad Request' for url 'http://localhost:8000/api/v2/tenants/default_tenant/databases/default_database/collections/c6b33238-fda9-4d71-a834-bc22eab5efb8/query'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/henry/repos/llm/example.py", line 17, in <module>
    print(collection.query(query_texts=['hawaii'])) #  <----- But this fails
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/henry/Library/Caches/pypoetry/virtualenvs/llm-kCwWOmYK-py3.12/lib/python3.12/site-packages/chromadb/api/models/Collection.py", line 224, in query
    query_results = self._client._query(
                    ^^^^^^^^^^^^^^^^^^^^
  File "/Users/henry/Library/Caches/pypoetry/virtualenvs/llm-kCwWOmYK-py3.12/lib/python3.12/site-packages/chromadb/telemetry/opentelemetry/__init__.py", line 146, in wrapper
    return f(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^
  File "/Users/henry/Library/Caches/pypoetry/virtualenvs/llm-kCwWOmYK-py3.12/lib/python3.12/site-packages/chromadb/api/fastapi.py", line 528, in _query
    resp_json = self._make_request(
                ^^^^^^^^^^^^^^^^^^^
  File "/Users/henry/Library/Caches/pypoetry/virtualenvs/llm-kCwWOmYK-py3.12/lib/python3.12/site-packages/chromadb/api/fastapi.py", line 90, in _make_request
    BaseHTTPClient._raise_chroma_error(response)
  File "/Users/henry/Library/Caches/pypoetry/virtualenvs/llm-kCwWOmYK-py3.12/lib/python3.12/site-packages/chromadb/api/base_http_client.py", line 103, in _raise_chroma_error
    raise Exception(f"{resp.text} (trace ID: {trace_id})")
Exception: {"error":"InvalidArgumentError","message":"Expected where to have exactly one operator, got {}"} (trace ID: 0)

@itaismith Ah, updating the client solves the problem. Thanks! But, if client and server need to be on the same version, how would one upgrade in production without downtime?

Great! There are many ways to achieve this! I recommend taking this to our Discord where you can share more information about your setup and we can give you the right direction.

I found same issue by using 0.5.18 and .17. When doing query, 400 error returned with no result.


this.formatNumber is not a function

Hello, copied an example from readme and it did't work.

Hi，now，it‘s OK。
<EMAIL_ADDRESS>

Hello,
nope, for me it is also not working at version 1.1.1


Consider adding "why promoted" context information for warnings/errors caused by type promotion

Inspired by this comment: https://github.com/dart-lang/language/issues/1523#issuecomment-799930453
Consider the following code:
f(Object? x) {
  g(x as int); // (1)
  if (x == null) { // (2)
    print('x was null');
  }
}
g(int? x) {}

Note that the user migrated this code incorrectly from a pre-null-safety version: at (1), they should have used x as int? to preserve the behavior that null is allowed.
Currently the analyzer generates the following warning at the line marked (2):
   info • test.dart:3:9 • The operand can't be null, so the condition is always false. Try removing the condition, an enclosing condition, or the whole
          conditional statement. • unnecessary_null_comparison

Based on this warning, it's not easy to figure out that the mistake was in the as expression at (1).  A possible way to help this would be to add context information to the warning explaining the reason the operand can't be null: because it was promoted at line (1).
It should be possible to do this in a similar way to how we are adding "why not promoted" context information (https://github.com/dart-lang/sdk/issues/44897).

Note that there's the lint cast_nullable_to_non_nullable to catch (1)


Support build args in docker file resources

It's commonplace to provide --build-arg when building container images with docker build. In fact, certain scenarios require it, such as Node.js apps that expect certain env vars to be available when they build. Aspire will need to expose an API that allows developers to express that their container images are built with specific environment variables, provided as --build-arg.
This is related to https://github.com/Azure/azure-dev/issues/3432
See https://docs.docker.com/reference/cli/docker/image/build/#build-arg

I assume this means new overloads of the PublishAsDockerFile method, something like the following perhaps?
public static IResourceBuilder<NodeAppResource> PublishAsDockerFile(
    this IResourceBuilder<NodeAppResource>,
    IEnumerable<DockerBuildArg> buildArgs);

public class DockerBuildArg
{
    public DockerBuildArg(string name);
    public DockerBuildArg(string name, string value);

    public required string Name { get; set; }
    // Value is optional, if omitted it means it will be flowed from the environment
    public string string? Value { get; set; }
}

Consumption would be something like:
builder.AddNodeApp("apiapp", "../apiapp/app.js")
    .PublishAsDockerFile([new("HTTP_PROXY"), new("FTP_PROXY", "http://<IP_ADDRESS>:4567)")]);

Maybe more than string/string we need to store reference to other resources?

Maybe more than string/string we need to store reference to other resources?

Can you elaborate on the scenarios? I admit I'm not super clear on them here, other than Docker supports build args so we should.

To my knowledge, all we'd need is env vars. I'm curious too, what scenario would we need anything more than string/string pairs?


fix formatter & linting

@paoloricciuti I've already merged this but just wanted to make sure you're aware/happy with this change. I updated the format command to also run any fixable linting issues

@paoloricciuti I've already merged this but just wanted to make sure you're aware/happy with this change. I updated the format command to also run any fixable linting issues and error on any errors that aren't automatically fixable

Yeah perfectly fine


feat:new-design

Do we still depend on the main.old.css and index-old.html files for the new design? If not, you can delete them, because the old versions will still be available in the git history if we need them for any reason.

Do we still depend on the main.old.css and index-old.html files for the new design? If not, you can delete them, because the old versions will still be available in the git history if we need them for any reason.
not really :D I left them in case we would need quick change to the prev design, thought it would be more quicker, but you are right. Deleted


Check for existence of secret token from SoundCloud

SoundCloud have changed something to do with secret_tokens (which we previously relied on).
This probably means SoundCloud embeds won't be working anywhere.
This fix does a null check on the secret_token so pages won't 404, but we'll still need to get SoundCloud embeds working again.

Are we planning on that as a next step?

Yeah, I'll make sure there's a ticket in for it.


add flag to opt out of batch review process

part of #659
This is mainly for API users, that might need to have their batch changes continue to hard fail rather than fall into the manual review process if the manual review process is enabled system-wide and the batch changes have soft failures.
Changes in this pull request:

add an attribute on the batch change request called disableManualReview, default value is false
if the system config valuemanualReviewEnabled is set to true and a user sets the disableManualReview to true in their batch change it will proceed  down one of two paths, as if manualReviewEnabled were false:

if there are no errors the batch change will be processed
if there are any errors (soft or hard) the batch change will fail, it will not enter the manual review process

if the system config valuemanualReviewEnabled is set to false the disableManualReview value of a batch change is ignored.

did we need this? i thought we had decided that manualReviewEnabled was enough and all flows go to pending if that is on

changed this flag from disableManualReview: Boolean = false to allowManualReview: Boolean = true


attempting to fix redirect build error

There is a build error due to redirects, so attempting to resolve that here. I suspect it is the anchor at the end of the url that may be causing this, but not sure.
cc @toriancrane

@sean1588 I think we can close this now, so I'll go ahead and do that. Thanks for hopping in to help with it though!


Permission denied on bin/es-docker if ran with user remapping

docker info output:
Containers: 85                                                                                Running: 0                                                                                Paused: 0                                                                                Stopped: 85                                                                                Images: 336                                                                                Server Version: 17.04.0-ce                                                                                Storage Driver: aufs                                                                                Root Dir: /var/lib/docker/1000.1000/aufs                                                                                Backing Filesystem: extfs                                                                                Dirs: 372                                                                                Dirperm1 Supported: true                                                                                Logging Driver: json-file                                                                                Cgroup Driver: cgroupfs                                                                                Plugins:                                                                                Volume: local                                                                                Network: bridge host macvlan null overlay                                                                              Swarm: inactive                                                                                Runtimes: runc                                                                                Default Runtime: runc                                                                                Init Binary:                                                                                containerd version: 422e31ce907fd9c3833a38d7b8fdd023e5a76e73                                                            runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228                                                                  init version: 949e6fa                                                                                Security Options:                                                                                apparmor                                                                                seccomp                                                                                Profile: default                                                                                userns                                                                                Kernel Version: 4.8.0-46-generic                                                                                Operating System: Ubuntu 16.04.2 LTS                                                                                OSType: linux                                                                                Architecture: x86_64                                                                                CPUs: 4                                                                                Total Memory: 31.33GiB                                                                                Name: workBuntu                                                                                ID: 5N25:YF6I:3CKB:YMIE:G4QQ:QYDD:PTVZ:TXP4:7YMH:IKR2:Q4XX:K4FO                                                         Docker Root Dir: /var/lib/docker/1000.1000                                                                              Debug Mode (client): false                                                                                Debug Mode (server): false                                                                                Registry: https://index.docker.io/v1/                                                                                Experimental: false                                                                                Insecure Registries:                                                                                <IP_ADDRESS>/8                                                                                Live Restore Enabled: false                                                                                WARNING: No swap limit support

docker-compose version:
docker-compose version 1.12.0, build b31ff33

Host OS and version:
Ubuntu 16,04

Bug description
I am running elasticsearch with user remapping for docker as such:
https://blog.yadutaf.fr/2016/04/14/docker-for-your-users-introducing-user-namespace/
Running the image with docker-compose gives me the following error:
/bin/bash: bin/es-docker: Permission denied
elasticsearch exited with code 126

@jens1245 Could you please provide your exact docker-compose file (or docker run command?)?

Certainly!:
version: '2'
services:
elasticsearch:
image: docker.elastic.co/elasticsearch/elasticsearch:5.3.0
container_name: elasticsearch
environment:
- cluster.name=docker-cluster
- bootstrap.memory_lock=true
- "ES_JAVA_OPTS=-Xms512m -Xmx512m"
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536
hard: 65536
mem_limit: 1g
cap_add:
- IPC_LOCK
volumes:
- esdata:/usr/share/elasticsearch/data
ports:
- 9200:9200
networks:
- esnet
volumes:
esdata:
driver: local
networks:
esnet:
driver: bridge

@jens1245 I reformatted your docker-compose.yml below for readability, but other than that this will work fine.
You are using a named volume called esdata.
If you haven't used that volume before this should work out of the box.
If you have used the same esdata: storage volume before, say with a different image and hence having dirs with different ownerships, perhaps ES won't be able to write there.
If you do not mind losing the data currently store in esdata:, can you try wiping it away with:

docker-compose down -v

(-v will delete the volume)
and then start it again with:

docker-compose up

version: '2'
services:
  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:5.3.0
    container_name: elasticsearch
    environment:
      - cluster.name=docker-cluster
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    ulimits:
      memlock:
        soft: -1
        hard: -1
      nofile:
        soft: 65536
        hard: 65536
    mem_limit: 1g
    cap_add:
      - IPC_LOCK
    volumes:
      - esdata:/usr/share/elasticsearch/data
    ports:
      - 9200:9200
    networks:
      - esnet

volumes:
  esdata:
    driver: local

networks:
  esnet:
    driver: bridge

I used:
docker-compose down -v
and rebuilt the image, but I still get the same error.
Did you set the user mapping?
{
        "userns-remap": "yadutaf"
}

in /etc/docker/daemon.json?

@jens1245 No I didn't set the userns-remap option. Would you care describing what are you trying to achieve with this option, for your use case? The docker ES image, defaults to a specific non-privileged user (elasticsearch uid:1000, gid: 1000) inside the container, with no sudo access. The ES wrapper script /bin/es-docker starts using this user, so this limits the attack surface, if it's security that has you looking at the userns-remap option.

I set the user mapping for another container. This way it is easy to share data with the host and at the same time limits the attack surface. Thus, in this case, it is not so much for Elasticsearch but for for overall security / usability. Unfortunately, I do not know of a way to use user remapping only for some containers.

Another temporary workaround is to write your own Dockerfile, based on the history from elasticsearch
FROM alpine

RUN apk --no-cache  add bash curl openjdk8 openssl
RUN adduser -D -u 555 -h /usr/share/elasticsearch elasticsearch

ARG ELASTIC_VERSION
ARG ES_DOWNLOAD_URL
ARG ES_JAVA_OPTS

ENV ELASTIC_VERSION=5.3.0
ENV ES_DOWNLOAD_URL=https://artifacts.elastic.co/downloads/elasticsearch
ENV PATH /usr/share/elasticsearch/bin:$PATH
ENV JAVA_HOME /usr/lib/jvm/java-1.8-openjdk

WORKDIR /usr/share/elasticsearch

# Download/extract defined ES version. busybox tar can't strip leading dir.
RUN wget ${ES_DOWNLOAD_URL}/elasticsearch-${ELASTIC_VERSION}.tar.gz && \
    EXPECTED_SHA=$(wget -O - ${ES_DOWNLOAD_URL}/elasticsearch-${ELASTIC_VERSION}.tar.gz.sha1) && \
    test $EXPECTED_SHA == $(sha1sum elasticsearch-${ELASTIC_VERSION}.tar.gz | awk '{print $1}') && \
    tar zxf elasticsearch-${ELASTIC_VERSION}.tar.gz && \
    chown -R elasticsearch:elasticsearch elasticsearch-${ELASTIC_VERSION} && \
    mv elasticsearch-${ELASTIC_VERSION}/* . && \
    rmdir elasticsearch-${ELASTIC_VERSION} && \
    rm elasticsearch-${ELASTIC_VERSION}.tar.gz

RUN set -ex && for esdirs in config data logs; do \
        mkdir -p "$esdirs"; \
        chown -R elasticsearch:elasticsearch "$esdirs"; \
    done

# Install Plugin
RUN /usr/share/elasticsearch/bin/elasticsearch-plugin list
RUN /usr/share/elasticsearch/bin/elasticsearch-plugin install --batch repository-s3

# Remove x-pack 'https://github.com/elastic/elasticsearch-docker/issues/35#issuecomment-285912424
# RUN /usr/share/elasticsearch/bin/elasticsearch-plugin remove  x-pack
RUN rm -rf plugins/x-pack

USER elasticsearch

COPY elasticsearch.yml config/
COPY log4j2.properties config/
COPY bin/es-docker bin/es-docker

USER root
RUN chown elasticsearch:elasticsearch config/elasticsearch.yml config/log4j2.properties bin/es-docker && \
    chmod 0750 bin/es-docker

USER elasticsearch
CMD ["/bin/bash", "bin/es-docker"]

Thank you so much!
I've slightly changed the Docker file you provided for my purpose (with X-pack) and it all works now:
FROM alpine

RUN apk --no-cache  add bash curl openjdk8 openssl
RUN adduser -D -u 555 -h /usr/share/elasticsearch elasticsearch

ARG ELASTIC_VERSION
ARG ES_DOWNLOAD_URL
ARG ES_JAVA_OPTS

ENV PATH /usr/share/elasticsearch/bin:$PATH
ENV JAVA_HOME /usr/lib/jvm/java-1.8-openjdk

WORKDIR /usr/share/elasticsearch

# Download/extract defined ES version. busybox tar can't strip leading dir.
RUN wget ${ES_DOWNLOAD_URL}/elasticsearch-${ELASTIC_VERSION}.tar.gz && \
    EXPECTED_SHA=$(wget -O - ${ES_DOWNLOAD_URL}/elasticsearch-${ELASTIC_VERSION}.tar.gz.sha1) && \
    test $EXPECTED_SHA == $(sha1sum elasticsearch-${ELASTIC_VERSION}.tar.gz | awk '{print $1}') && \
    tar zxf elasticsearch-${ELASTIC_VERSION}.tar.gz && \
    chown -R elasticsearch:elasticsearch elasticsearch-${ELASTIC_VERSION} && \
    mv elasticsearch-${ELASTIC_VERSION}/* . && \
    rmdir elasticsearch-${ELASTIC_VERSION} && \
    rm elasticsearch-${ELASTIC_VERSION}.tar.gz

RUN set -ex && for esdirs in config data logs; do \
        mkdir -p "$esdirs"; \
        chown -R elasticsearch:elasticsearch "$esdirs"; \
    done

USER elasticsearch

# Install xpack
RUN /usr/share/elasticsearch/bin/elasticsearch-plugin install --batch x-pack

COPY elasticsearch.yml config/
COPY log4j2.properties config/
COPY bin/es-docker bin/es-docker

USER root
RUN chown elasticsearch:elasticsearch config/elasticsearch.yml config/log4j2.properties bin/es-docker && \
    chmod 0750 bin/es-docker

USER elasticsearch
CMD ["/bin/bash", "bin/es-docker"]

Another temporary workaround is to write your own Dockerfile, based on the history from elasticsearch

@jegade You do not need to use the docker history command to see how the image has been built, you can always refer to the Dockerfile used in the repo.
Additionally, while creating your customized image, you may also use the existing image as a base and add your own customizations to reduce repetition. One example is provided in the documentation here.

@dliappis sorry, the refered Dockerfile does not contains the whole history. This is based on FROM docker.elastic.co/elasticsearch/elasticsearch-alpine-base:latest - where the USER is applied.
Changing the uid for the existing image does not work for me.

This is based on FROM docker.elastic.co/elasticsearch/elasticsearch-alpine-base:latest - where the USER is applied.

That is correct. This image is also in a public repo and you can find the Dockerfile here.
One strategy for changing the uid/gid in a dynamic way, when you build the image, is to use build args.
Here is an example:
FROM docker.elastic.co/elasticsearch/elasticsearch:5.3.0
ARG CUSTOM_UID
ARG CUSTOM_GID
USER root
RUN sed -r -i "s/^elasticsearch:x:\d+:\d+:(.*)\$/elasticsearch:x:$CUSTOM_UID:$CUSTOM_GID:\1/" /etc/passwd && \
    sed -r -i "s/^elasticsearch:x:\d+:(.*)\$/elasticsearch:x:$CUSTOM_GID:\1/" /etc/group && \
    chown -R $CUSTOM_UID:$CUSTOM_GID /usr/share/elasticsearch
USER elasticsearch

For example, in a fresh VM where I have a user with uid=1001, gid=1001, I built a customized image with:
$ id
uid=1001(elastic) gid=1001(elastic) groups=1001(elastic),1002(docker) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
$ docker build --build-arg CUSTOM_UID=$(id -u) --build-arg CUSTOM_GID=$(id -g) -t myes .

This results in a working container:
[elastic@fedora25vbox ~]$ docker run --rm myes
[2017-04-20T14:28:11,704][INFO ][o.e.n.Node               ] [] initializing ...
[2017-04-20T14:28:12,835][INFO ][o.e.e.NodeEnvironment    ] [pRZ41B3] using [1] data paths, mounts [[/ (/dev/mapper/docker-253:0-8792783-ab2ae70e9d0911287fa77759bf0d62dcd73e613a03303d38f9e09327bc52ef9c)]], net usable_space [9.7gb], net total_space [9.9gb], spins? [unknown], types [xfs]

@dliappis if i try the same with 5.4.1 version i still face Permission denied on bin/es-docker
but in 5.3.0 this works. Any changes to be done in the Dockerfile ?
FROM docker.elastic.co/elasticsearch/elasticsearch:5.4.1
ARG CUSTOM_UID
ARG CUSTOM_GID
USER root
RUN sed -r -i "s/^elasticsearch:x:\d+:\d+:(.*)\$/elasticsearch:x:$CUSTOM_UID:$CUSTOM_GID:\1/" /etc/passwd && \
    sed -r -i "s/^elasticsearch:x:\d+:(.*)\$/elasticsearch:x:$CUSTOM_GID:\1/" /etc/group && \
    chown -R $CUSTOM_UID:$CUSTOM_GID /usr/share/elasticsearch
USER elasticsearch

@anshitabharti Sure; start with 5.4.0, the images are based on centos:7, so the /etc/{passwd,group} format is a bit different, but on the plus side it's easier to change the uid/gid like so:
FROM docker.elastic.co/elasticsearch/elasticsearch:5.4.1
ARG CUSTOM_UID
ARG CUSTOM_GID
USER root
RUN groupmod -g 1001 elasticsearch && \
    usermod -u 1001 elasticsearch && \
    chown -R $CUSTOM_UID:$CUSTOM_GID /usr/share/elasticsearch
USER elasticsearch

@dliappis This worked. Thank you!

The above did not work for me. The file system fails to return the right file ownership for directories under /usr/share/elasticsearch and thus ElasticSearch fails to start. I had to use the following workaround to get chown'd files to be visible correctly to elasticsearch user:
FROM docker.elastic.co/elasticsearch/elasticsearch:5.4.1
ARG CUSTOM_UID
ARG CUSTOM_GID
USER root
RUN cp -r /usr/share/elasticsearch /tmp/silly_aufs_fix && \
    rm -rf /usr/share/elasticsearch && \
    cp -r /tmp/silly_aufs_fix /usr/share/elasticsearch && \
    groupmod -g $CUSTOM_UID elasticsearch && \
    usermod -u $CUSTOM_GID elasticsearch && \
    chown -R elasticsearch:elasticsearch /usr/share/elasticsearch
USER elasticsearch

I guess this workaround forces AUFS to make another copy of the files and chown them so that changes are visible in my extended Docker image.
Another workaround I found is to run ls /usr/share/elasticsearch command as root on live container before running elasticsearch as elasticsearch user.

@perttuta Thanks for sharing, what seems to be, an aufs specific problem! I believe your are hitting this aufs issue[1].
I was also able to reproduce it on a ubuntu:16.04 virtualbox vm using aufs.
My modinfo shows:
root@ubuntu1604vbox:~# modinfo aufs
filename:       /lib/modules/4.4.0-81-generic/kernel/fs/aufs/aufs.ko
alias:          fs-aufs
version:        4.x-rcN-20160111
description:    aufs -- Advanced multi layered unification filesystem
author:         Junjiro R. Okajima<EMAIL_ADDRESS>license:        GPL
srcversion:     BD1C47D04FE5C2D88F63AAB
depends:
intree:         Y
vermagic:       4.4.0-81-generic SMP mod_unload modversions
parm:           brs:use <sysfs>/fs/aufs/si_*/brN (int)
parm:           allow_userns:allow unprivileged to mount under userns (bool)

And I assume the patch hasn't made it to the aufs version shipped with the latest Ubuntu 16.04 (aufs >=4.(x>=1)-20160905)
If it is possible in your environment, you may want to consider the following recommendation from Docker:

If your Linux kernel is version 4.0 or higher, and you use Docker CE, consider using the newer overlay2, which has potential performance advantages over the aufs storage driver.

Using the devicemapper, overlay or overlay2 storage driver, I couldn't reproduce the problem on Ubuntu 16.04.
As this issue has slightly become a sink for all issues generally related to permissions, I'll take the opportunity to layout some of the general options.

The best practice for data dir persistence for ES in Docker is using a named docker data volume as mentioned in the production mode example. This can be achieved, on the cli, as easily as docker run -v esdata:/usr/share/elasticsearch/data docker.elastic.co/elasticsearch/elasticsearch:5.4.2 and will be automatically re-created or reused if it already exists.

When mounting a host dir as a data volume, it needs to be readable/writable by 1000:1000

A number of volume plugins are available to utilize enterprise block storage backends.

Notes
[1] See also modifying files or directories on aufs:

Renaming directories: Calling rename(2) for a directory is not fully supported on AUFS. It returns EXDEV (“cross-device link not permitted”), even when both of the source and the destination path are on a same AUFS layer, unless the directory has no children. Your application needs to be designed to handle EXDEV and fall back to a “copy and unlink” strategy.

Related to: https://github.com/moby/moby/issues/1295#issuecomment-269058662

my remote test server is  root@ubuntu1604  .  and i use docker.elastic.co/elasticsearch/elasticsearch:5.5.1 this image
USER root
RUN chown -R elasticsearch:elasticsearch /usr/share/elasticsearch
USER elasticsearch

the code above can not change any ownership at all in the container.
it is make me crazy because the same code in my mac can work perflect.
and i change the docker storage drive to overlay2. the  problem is still
last time ,  i found the below post
https://stackoverflow.com/questions/29245216/write-in-shared-volumes-docker/29251160#29251160
they told me ,the linux is something different.
so i just in the docker host cmd  run chown 1000:1000 the data dir and then i can docker-compose up the elastic service.
but i think maybe there is more perflect solve solution.  i use an other image https://hub.docker.com/_/mongo/   . just set an volumes in the docker-compose.yml and all nothing is ok .Heavy did not encounter the problem of Permission

Hi.
I reproduced the same issue even with overly2 storage driver.
Server Version: 17.06.2-ce
Storage Driver: overlay2
Kernel Version: 4.10.0-33-generic
Operating System: Ubuntu 16.04.3 LTS

If I run the docker daemon without the user remapping option, the folder /usr/share/elasticsearch within the container belongs to elasticsearch user, as expected:
$ docker run docker.elastic.co/elasticsearch/elasticsearch:5.4.1 ls -ln /usr/share |grep elastic
drwx------  1 1000 1000 4096 Jun 14 08:00 elasticsearch

but if I run it with the user remapping option, while mapping to 1000 uid (my host user's uid), the same folder now belongs to root:
$ docker run docker.elastic.co/elasticsearch/elasticsearch:5.4.1 ls -ln /usr/share |grep elastic
drwx------  1 0 0 4096 Jun 14 08:00 elasticsearch

Now, if I run the daemon while remapping user to another uid (for example 1981).
I really do not know how user remapping is implemented by docker, but what I understand is that there is a bug when a user into the container has exactly the same uid as the user remapping uid.
So, as a workaround, I changed my uid/gid in my host and now it works like a charm ;)

@ballinette
I am not sure, I later compared with the mongo docker different, I think it is likely to need to add the data directory to. Dockerignore file. You can try it. I was also replaced by overlay2 did not work

This issue is quite old. Maintenance of the docker files for elasticsearch has moved to the elasticsearch repo. Any future issues can also be opened in the forums, where there is an active community ready to assist. As we will be archiving this repository, I am going to close this issue.


SPAs don't extract embedded images and other non-code (<> JS/CSS) artifacts

... and special care is needed for making sure that the images, etc referenced via relative paths in CSS are treated correctly.

Bitbucket: https://bitbucket.org/intellifactory/websharper/issue/296
Originally reported by: Adam Granicz
Originally created at: 2014-10-17T16:13:15.741

Not sure if there is much we can do about CSS url-ed resources, but we must fix the extracting of these resources finally.

In https://github.com/intellifactory/websharper/commit/9b1041 all web resources are extracted under output path, next to the .js and .css files (default is \Content).


Issue with Show current day in daily list

I know at a certain time of day the current day drops off from the daily list but at the moment it's past 7:00pm but not quite 8:00pm Friday and with "Show current day in daily list" set to off, it's dropping Saturday from the daily list and it's only showing Sunday and beyond (mine is set to show only 4 days cause I didn't want it to scroll, so it shows 3 in one screenshot).
With "Show current day in daily list" set to on, it goes back to showing Saturday since it's after 7:00pm so "Friday" has dropped off.
I would expect  that both settings for "Show current day in daily list" would show Saturday since the current day is still Friday.
Might it also be possible to always show the current day all the way until 11:59pm? I realize that this messed up the hourly chart though when someone tapped on that day to open it since there's no longer any hourly data to show at 11:59pm so just fixing what I mentioned above might be enough (that Saturday would be listed with both Show current day on/off in my example of the current day being Friday).

Thanks again :)

@0-5-0 that is definitively a bug. Need to reproduce it, but i will fix it!
BTW you have my deepest thanks for your support of my work!

Really not a problem, OSS weather is a great app (much better than the government one here) and you're an awesome dev, super responsive, open to suggestions. I'm happy to donate to projects I use and like, I bumped up my donation to Open-Meteo too to be fair :).
My timezone is on UTC -5 [EST] Eastern Standard Time [Toronto, Canada]

@0-5-0 sadly i cant reproduce it. I tried to put my phone in your time/timezone but even around 7/8pm i can always see the current/next day.
is it always happening for you? is it dependent on the weather location? Maybe you can see a "pattern" on when it is happening?

It's pretty consistent for me, every night basically, I'll keep an eye on it to see if there's a pattern. In my example it was between 7PM and 8PM but it might be more reliable checking for the current day to drop off closer to 9PM or 10PM.
31 Dec 2024, 09:45 by @.***:

@0-5-0 https://github.com/0-5-0>  sadly i cant reproduce it. I tried to put my phone in your time/timezone but even around 7/8pm i can always see the current/next day.
is it always happening for you? is it dependent on the weather location? Maybe you can see a "pattern" on when it is happening?
—
Reply to this email directly, > view it on GitHub https://github.com/Akylas/oss-weather/issues/289#issuecomment-2566506690> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/A2ZUHBGDHKD7GOP7P5GGFI32IKUZ5AVCNFSM6AAAAABUJJFIP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGUYDMNRZGA> .
You are receiving this because you were mentioned.> Message ID: > <Akylas/oss-weather/issues/289/2566506690> @> github> .> com>

@0-5-0 OK I was almost certain it is related to timezone. Like UTC time would already be on the next day while your local time still on the current day, which could produce that issue. But i could not reproduce it

Yea, I tried changing the time and timezone to various times to force it early but couldnt reproduce it either. I'll keep an eye out for any patterns.
Dec 31, 2024, 13:40 by @.***:

@0-5-0 https://github.com/0-5-0>  OK I was almost certain it is related to timezone. Like UTC time would already be on the next day while your local time still on the current day, which could produce that issue. But i could not reproduce it
—
Reply to this email directly, > view it on GitHub https://github.com/Akylas/oss-weather/issues/289#issuecomment-2566653380> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/A2ZUHBHC2WGY74GNC25VDMD2ILQLRAVCNFSM6AAAAABUJJFIP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGY2TGMZYGA> .
You are receiving this because you were mentioned.> Message ID: > <Akylas/oss-weather/issues/289/2566653380> @> github> .> com>

I noticed forcing the time and timezone on my phone forward making it 1 day later than it actually was the current forecast top right shows Wednesday but the daily list view at the bottom still showed the previous Tuesday. Not sure if that's just cause there's a forced delay on the refresh where it wasnt pulling live data but instead fetched cached data. It could explain why it's difficult to reproduce.
I'll keep trying to break it ;)
Dec 31, 2024, 14:19 by @.***:

Yea, I tried changing the time and timezone to various times to force it early but couldnt reproduce it either. I'll keep an eye out for any patterns.
Dec 31, 2024, 13:40 by @.***:

@0-5-0 https://github.com/0-5-0>>  OK I was almost certain it is related to timezone. Like UTC time would already be on the next day while your local time still on the current day, which could produce that issue. But i could not reproduce it
—
Reply to this email directly, >> view it on GitHub https://github.com/Akylas/oss-weather/issues/289#issuecomment-2566653380>> , or >> unsubscribe https://github.com/notifications/unsubscribe-auth/A2ZUHBHC2WGY74GNC25VDMD2ILQLRAVCNFSM6AAAAABUJJFIP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGY2TGMZYGA>> .
You are receiving this because you were mentioned.>> Message ID: >> <Akylas/oss-weather/issues/289/2566653380>> @>> github>> .>> com>


I've got error TypeError: cannot unpack non-iterable NoneType object

I want to used sleep function collaborate with my accelerometry data which contain Timestamp and 3Axes which are xyz0,xyz1, and xyz2 in .csv file. So I write my code like this and I've got some error. Someone help me please, Thank you.

Oh, Thank you. Now, I can fix it.

Excuse me, I have another question. If I want to get the Time end like Timestamp end of Sleep opportunity. Do you have any suggestion for me?

yes you can add duration to start timestamp to get the end, and convert it if necessary to human readable

yes you can add duration to start timestamp to get the end, and convert it if necessary to human readable

Thank you very much for beautiful code and beautiful suggestion for me.


Move remaining tests in e2e/service.go to unique namespaces.

This prevents multiple runs of the same test from trampling on each other,
both serially and in parallel. Ultimately we'll move this to a suite-wide test
initlalization and teardown routine as per #6553, but until that's done, lets
prevent these particular tests from failing unnecessarily with this small change.
e2e tests are still busy running.  I'll update this thread to confirm that they've
succeeded.

LGTM. Just want to confirm that all e2e tests still pass.

As discussed offline, I found a bug, fixed it, and all e2e tests for Services pass now.  Ready for merge, I believe.
Ran 5 of 40 Specs in 162.920 seconds
SUCCESS! -- 5 Passed | 0 Failed | 0 Pending | 35 Skipped I0415 15:32:05.887675   53532 driver.go:117] All tests pass

LGTM


feat(WMGv2): Create V2 version of \query endpoint

Here are the execution steps in order:

Version the query API - Make a copy of v1.py and test_v1.py and name them as v2.py and test_v2.py

The reason for this is to mitigate against the case of making API code changes that are backward incompatible with the current frontend code running in production. For example, if the API changes require changes to the structure of the data sent to the frontend that the current production version of frontend is not prepared to handle, then it is safer to simply version the API

tissue_ontology_term_ids (here) should be updated to allow no items (min_items=0)
Modify v2.py to query the expression_summary and expression_summary_default cubes without specifying tissues.
Modify wmg-api.yml to include v2/query and check that v2/query executes code in v2.py
Modify the data structures returned gene expression calculator functions and rollup functions (gene expression and cell counts) appropriately to serve the requirements of the frontend.
Refactor unit test files test_v2.py and test_query.py to include changes made in v2.py

At the end of these 6 steps, the V2 Query API should be functional but may not be optimized for performance in production. It may not be performance optimized the backend cube changes may have not been made. Furthermore, other optimizations besides cube changes may be needed and is as yet undetermined.

@seve - It might be helpful to put in this ticket what the request payload and response format are V1 and V2 of the query api as it might be helpful during implementation. I will put what I know in comments below but if you could put down the expected V2 response format that would be good.

V1 Request Payload
{
  "filter": {
    "dataset_ids": [],
    "development_stage_ontology_term_ids": [],
    "disease_ontology_term_ids": [],
    "gene_ontology_term_ids": [
      "ENSG00000000003"
    ],
    "organism_ontology_term_id": "NCBITaxon:9606",
    "self_reported_ethnicity_ontology_term_ids": [],
    "sex_ontology_term_ids": [],
    "tissue_ontology_term_ids": [
      "UBERON:0000178"
    ]
  },
  "is_rollup": true
}

V1 Response Payload
{
    "expression_summary": {
        "gene_1": {
            "tissue_1": {
                "cell_1": {
                    "aggregated": {
                        "me": 1.3531017013676259,
                        "n": 1629,
                        "pc": 0.009338079760614971,
                        "tpc": 0.008942196849096997
                    }
                },
                "cell_2": {
                    "aggregated": {
                        "me": 1.3531017013676259,
                        "n": 1629,
                        "pc": 0.009338079760614971,
                        "tpc": 0.008942196849096997
                    }
                },
            },
            "tissue_2": {
                "cell_1": {
                    "aggregated": {
                        "me": 1.3531017013676259,
                        "n": 1629,
                        "pc": 0.009338079760614971,
                        "tpc": 0.008942196849096997
                    }
                },
                "cell_2": {
                    "aggregated": {
                        "me": 1.3531017013676259,
                        "n": 1629,
                        "pc": 0.009338079760614971,
                        "tpc": 0.008942196849096997
                    }
                },
            },
        },
        "gene_2": {
            "tissue_1": {
                "cell_1": {
                    "aggregated": {
                        "me": 1.3531017013676259,
                        "n": 1629,
                        "pc": 0.009338079760614971,
                        "tpc": 0.008942196849096997
                    }
                },
                "cell_2": {
                    "aggregated": {
                        "me": 1.3531017013676259,
                        "n": 1629,
                        "pc": 0.009338079760614971,
                        "tpc": 0.008942196849096997
                    }
                },
            },
            "tissue_2": {
                "cell_1": {
                    "aggregated": {
                        "me": 1.3531017013676259,
                        "n": 1629,
                        "pc": 0.009338079760614971,
                        "tpc": 0.008942196849096997
                    }
                },
                "cell_2": {
                    "aggregated": {
                        "me": 1.3531017013676259,
                        "n": 1629,
                        "pc": 0.009338079760614971,
                        "tpc": 0.008942196849096997
                    }
                },
            },
        },
     }
}

V2 Request Body
NOTE: tissue_ontology_term_ids does not exist in the V2 request body
{
  "filter": {
    "dataset_ids": [],
    "development_stage_ontology_term_ids": [],
    "disease_ontology_term_ids": [],
    "gene_ontology_term_ids": [
      "ENSG00000000003"
    ],
    "organism_ontology_term_id": "NCBITaxon:9606",
    "self_reported_ethnicity_ontology_term_ids": [],
    "sex_ontology_term_ids": [],
  },
  "is_rollup": true
}


Use a generic room update chat command

Coverage increased (+0.02%) to 84.916% when pulling 6a21ed14300d8e7b8668a669ae70c409e2f45b0c on feature/room_update into 2fd87c7be0180aeca0e3d125fad8e5dda50057fa on master.


Limited brightness

The midday sun intensity can easily exceed 100000, and indoor fluorescent light intensity can exceed 100, but the resulting HDRi maximum intensity never seems to exceed 35

I understand this is due to the maximum exposure value being limited to -5, is there a way (e.g. training myself) to get a larger dynamic range?

As you menntion that this problem is coming from the model being limited by EV-5.
To train the model by yourself to support lower than EV-5, we provide a training code at DiffusionLight-LoRA-Trainer. You can try to set --max_negative_exposure in the<EMAIL_ADDRESS>as high as you want. but I'm not sure if the result will be okay or not.


kubernetes/: Add network troubleshooting doc

Add guide to k8s network troubleshooting with toolbox on
CoreOS. Ref #802.

/cc @omkensey @philips @robszumski

LGTM! I would like to add more stuff like iptables debugging, NAT, etc. But this is a good start!


Check if runtime is Python2

Add ability to check python runtime

I think this can still work if I just skip the pip install -e on python3.  I'll update this before merging.

will update.

@andriisoldatenko Thanks!  To get the mypy stuff working, we can do something like this for now:
  - if [[ $TRAVIS_PYTHON_VERSION != 3.* ]]; then pip install -e .
  - if [[ $TRAVIS_PYTHON_VERSION != 3.* ]]; then travis_retry pip install -r requirements-dev.txt
  - if [[ $TRAVIS_PYTHON_VERSION == 3.* ]]; then pip install mypy-lang==0.4.5; fi

Probably worth moving out to a separate shell script if this gets any more complicated, unless there's a better way to do this.

@jamesls  @dstufft thanks guys for suggestions.

Thanks!


Modified java_src/gen.sh for external file list generation command

Changed gen.sh command for file generation in regards to previous change of genjava.js where an external file list can be used to generate classes and such.

@jlhughes


[FLINK-14267][connectors/filesystem]Introduce BaseRow Encoder in csv for filesystem table sink.

What is the purpose of the change
This pull request introduce BaseRow Csv Encoder in csv format for filesystem table sink..
Brief change log

Introduce BaseRow Csv Encoder.
Reuse current CsvRowSerializationSchema to deal csv serialzation.

Verifying this change
Add unit tests in CsvBaseRowDeSerializationTest.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): ( no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (JavaDocs)
This PR is just part of new feature filesystemTableSink and will add docs when the umbrella tasks finished.

@azagrebin thanks for update the PR link ^_^

@leonardBang no worries, I also created this kind of PR couple of times :)

merged in https://github.com/apache/flink/pull/11755


Check if the repo is private only when the pipeline is started

In order to reduce the number of GitHub API calls made during a pipeline run, check whether the GitHub repository is private (or enabled for private runs) only once: when the pipeline is created.
See packit/research#171 for more details.

Still relevant, but not urgent.


Alternative to Glyphicons icon font

On these pages :

https://getbootstrap.com/docs/4.3/extend/icons/#preferred
https://getbootstrap.com/docs/4.3/migration/#components

I would like to propose a new alternative : Friconix - https://friconix.com (very similar to Font Awesome, including CDN and fully free).
There is the Bootstrap logo : https://friconix.com/icon/fi-xnsuxl-bootstrap/
Hope this will help.

Thanks, we'll consider it!

Great alternative. It deserves to be known !


wepack dev server continuously compiling

Environment

Reproduction
Setup a monorepo with pnpm
use webpack as the builder
consume a local package from the pnpm workspace
nuxt dev start
make any change in nuxt app
(I will try to create a minimal repo with the above steps for easier reproduction)
Describe the bug
We set up a Nuxt 3 app using mono repo and using webpack as the builder. The app is consuming from local packages using pnpm workspace. The problem is once we start the dev server and make any changes and hit save, The dev server continuously compiles and is not stopping until we manually close it.
Additional context
No response
Logs
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/runtime.2abad7a80ca8ef09d0ff.hot-update.js                                                                                11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/_nuxt_app-component_mjs-_nuxt_app_config_mjs-_nuxt_css_mjs-_nuxt_i18n_utils_mjs-_nuxt_layouts-9deb6b.2abad7a80ca8ef09d0ff.hot-update.js
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/_nuxt_app-component_mjs-_nuxt_app_config_mjs-_nuxt_css_mjs-_nuxt_i18n_utils_mjs-_nuxt_layouts-9deb6b.css?1676700679286                 11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/pages_portal_personal-information_vue-packages_component-library_src_components_alert_Alert_v-8ef32e.css?1676700679286                 11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/packages_component-library_src_components_button_Button_vue-packages_component-library_src_co-57adae.css?1676700679287                 11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/runtime.2abad7a80ca8ef09d0ff.hot-update.js.map                                                                                11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/pages_portal_customer-service_vue.css?1676700679287                                                                                11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/_nuxt_app-component_mjs-_nuxt_app_config_mjs-_nuxt_css_mjs-_nuxt_i18n_utils_mjs-_nuxt_layouts-9deb6b.2abad7a80ca8ef09d0ff.hot-update.js.map
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/layouts_portal_vue.css?1676700679288                                                                                11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/pages_portal_forbidden_vue-packages_component-library_src_components_alert_Alert_vue.css?1676700679288                                 11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/node_modules_pnpm_nuxt_ui-templates_1_1_1_node_modules_nuxt_ui-templates_dist_templates_error-4b3f5b.css?1676700679288                 11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/pages_portal_users-and-locations_vue-packages_component-library_src_components_alert_Alert_vue.css?1676700679289                       11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/node_modules_pnpm_nuxt_ui-templates_1_1_1_node_modules_nuxt_ui-templates_dist_templates_error-1fea37.css?1676700679289                 11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/pages_portal_invoices_vue-node_modules_pnpm_headlessui_vue_1_7_9_vue_3_2_47_node_modules_head-c92136.css?1676700679289                 11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/components/icon.css?1676700679289                                                                                11:41:19
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/pages_portal_orders_vue-packages_component-library_src_components_slide-over_SlideOver_vue.css?1676700680293                           11:41:20
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/pages_portal_contact-preference_vue-node_modules_pnpm_nuxt-icon_0_1_8_vue_3_2_47_node_modules-f0885d.css?1676700680294                 11:41:20
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/composables_useDateFilter_ts-composables_useSearch_ts-packages_component-library_src_componen-4845ae.css?1676700680294                 11:41:20
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/_nuxt_app-component_mjs-_nuxt_app_config_mjs-_nuxt_css_mjs-_nuxt_i18n_utils_mjs-_nuxt_layouts-9deb6b.css?1676700680301                 11:41:20
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/layouts_portal_vue.css?1676700680301                                                                                11:41:20
<i> [webpack-dev-middleware] wait until bundle finished: /_nuxt/pages_portal_users-and-locations_vue-packages_component-library_src_components_alert_Alert_vue.css?1676700680301                       11:41:20

This is  continuously repeated until it stopped
Also attaching the logs from console

[HMR] Reload all css
client.js:251 [HMR] bundle 'client' rebuilt in 1435ms
process-update.js:51 [HMR] Checking for updates on the server...
process-update.js:125 [HMR] Updated modules:
process-update.js:127 [HMR]  - ../../packages/tailwind-preset/tailwind.css
process-update.js:132 [HMR] App is up to date.
client.js:242 [HMR] bundle rebuilding
hotModuleReplacement.js:230 [HMR] Reload all css
client.js:251 [HMR] bundle 'client' rebuilt in 1776ms
process-update.js:51 [HMR] Checking for updates on the server...
process-update.js:125 [HMR] Updated modules:
process-update.js:127 [HMR]  - ../../packages/tailwind-preset/tailwind.css
process-update.js:132 [HMR] App is up to date.
client.js:242 [HMR] bundle rebuilding
hotModuleReplacement.js:230 [HMR] Reload all css
client.js:251 [HMR] bundle 'client' rebuilt in 1340ms
process-update.js:51 [HMR] Checking for updates on the server...
client.js:242 [HMR] bundle rebuilding
process-update.js:125 [HMR] Updated modules:
process-update.js:127 [HMR]  - ../../packages/tailwind-preset/tailwind.css
process-update.js:132 [HMR] App is up to date.
hotModuleReplacement.js:230 [HMR] Reload all css
client.js:251 [HMR] bundle 'client' rebuilt in 1480ms
process-update.js:51 [HMR] Checking for updates on the server...
client.js:242 [HMR] bundle rebuilding
process-update.js:125 [HMR] Updated modules:
process-update.js:127 [HMR]  - ../../packages/tailwind-preset/tailwind.css
process-update.js:132 [HMR] App is up to date.
hotModuleReplacement.js:230 [HMR] Reload all css
client.js:251 [HMR] bundle 'client' rebuilt in 1378ms
process-update.js:51 [HMR] Checking for updates on the server...
client.js:242 [HMR] bundle rebuilding
process-update.js:125 [HMR] Updated modules:
process-update.js:127 [HMR]  - ../../packages/tailwind-preset/tailwind.css
process-update.js:132 [HMR] App is up to date.
hotModuleReplacement.js:230 [HMR] Reload all css
client.js:251 [HMR] bundle 'client' rebuilt in 1249ms
process-update.js:51 [HMR] Checking for updates on the server...
client.js:242 [HMR] bundle rebuilding
process-update.js:125 [HMR] Updated modules:
process-update.js:127 [HMR]  - ../../packages/tailwind-preset/tailwind.css
process-update.js:132 [HMR] App is up to date.
hotModuleReplacement.js:230 [HMR] Reload all css

Would you provide a reproduction? 🙏

Hi, Sorry for not including the reproduction, it was a large mono repo and I have removed every package except the package causing the issue. Here is the link to repo - https://github.com/mohamed-vj-mc/nuxt3-tailwind-issue

I am not sure if this is a nuxt3 issue or an issue with @nuxtjs/tailwindcss module.

I can't reproduce with the latest Nuxt/tailwind versions: https://stackblitz.com/edit/github-jrjjei.
Let me know if it's still occurring for you (with an updated reproduction) and I'll happily reopen.


Using django_nose.NoseTestSuiteRunner, Dynamic Context is listed as nose.case.Test.runTest

Dynamic Context is listed as  nose.case.Test.runTest rather than the expected tests.models
Describe the bug
Using django with django_nose as a Test Runner, setting settings.py
TEST_RUNNER = "django_nose.NoseTestSuiteRunner"

the .coveragerc contains:
[run]
dynamic_context = test_function

When I compile the coverage with the command line:
coverage html --show-contexts

The coverage ctx dropdown says only:
nose.case.Test.runTest

To Reproduce
How can we reproduce the problem?  Please be specific.

What version of Python are you using? 3.6
What version of coverage.py are you using? 5.0.3
What versions of what packages do you have installed?

django_nose: 1.4.6
nose: 1.3.7

What commands did you run?

It's django:  ./manage.py test {test_filename}

Hi @graemeworthy, sorry this has taken a long time.  Do you happen to have a complete runnable example I could use?  That is, "clone this, run this command"?


EQE Not Working A12 12.4

A12 Is not Supported
Only iPhone 8 or Plus
Only iPhone X
12.4 A12 and iPad Pro Not Supported
ONLY WORKS A11 Devices Running Unc0ver

Only iPhone 7 iPhone 8 or  + or any iPads Running A11 CPU

It will work other Than A12 it wont Work

Thank you! I waiting for eqe 🤩

EQE For A12 Is Now Avalible
Notice Please Use Filza to install DONT USE CYDIA to Inatall this New Program Download EQE Beta 2 A12 Enjoy
HOW TO INSTALL EQE ON iOS 12
Don't use the Cydia version.
unc0ver, Electra and Chimera are supported.

Install Filza and Debian Packager and coreutils and RocketBootstrap (RocketBootstrap from https://rpetri.ch/repo)
Copy/paste this link into Safari:  https://github.com/rweichler/EQE/releases/download/a12-beta2/eqe.deb
Open In/Copy to Filza (DON'T USE SILEO)
Tap on the file, tap Install, then Respring
Open MTerminal (or NewTerm) and type uicache and press enter (if you're on Chimera or Electra, do uicache —all instead)
If you had an old install of EQE, reboot/rejailbreak. Otherwise the app will crash on launch.

The app should appear on your homescreen.
READ <#562891468600115229> BEFORE ASKING FOR HELP

@miguelr4720 Your instructions are out of date. I would appreciate it if you simply linked to the Discord, which has up to date instructions.


Auto generate pytest unit test stubs for hamilton functions

 Issue by skrawcz
Wednesday Jul 20, 2022 at 21:19 GMT
Originally opened as https://github.com/stitchfix/hamilton/issues/160

Is your feature request related to a problem? Please describe.
We should be able to bootstrap a unit test suite given a hamilton function module.
Most DS probably write functions first, and then think about tests. We should make bootstrapping unit tests easy.
Describe the solution you'd like

User writes Hamilton functions.
User uses a command line utility to generate pytest unit test stubs for a module.
feature_logic.py --> test_feature_logic.py
Within that module, then we should be able to determine which functions have tests and which do not, creating the test for them appropriately
def my_feature() --> def test_my_feature().
To start we  probably don't want too many options -- perhaps a --dry-run argument that would list what would be created.

Describe alternatives you've considered
Not doing this.
Additional context
This would help the software engineering best practices story.
We could similarly use this approach to bulk add check_output decorators.

Closing as we've duplicated and begun work here: https://github.com/DAGWorks-Inc/hamilton/issues/74


clojurescript variants that have nodejs pre-installed?

Should we consider adding clojurescript images that pre-install node, npm, etc.?

Yes! I am currently using a custom Dockerfile for ClojureScript development that builds on the Clojure image to pre-install nodejs.
As a first step, I suggest making clojure:default also have nodejs pre-installed, providing a kitchen-sink image for clojure(script) development.

@njordhov Hmm... interesting idea. I was thinking of just creating official clojurescript images with all the other tags we generate but with latest LTS node / npm stuff pre-installed and the latest clojurescript pre-downloaded. And then clojurescript:latest would have lein, boot, and tools-deps stuff pre-installed like we recently started doing with clojure:latest. What do you think of that?
Thoughts @Quantisan?

@cap10morgan a separate image sounds good to keep it clean. Otherwise, I haven't used clojurescript for ages so I don't know what toolsets are needed anymore.

@cap10morgan A separate clojurescript image is fine, particularly when going beyond a kitchen-sink image. Thanks for all your work in making this happen.

Please no; AFIK there is no cljs builder that uses node in process.
You just need the node_modules folder.
Just do like this:
FROM node:alpine AS node
COPY package.json package-lock.json ./
RUN npm install

FROM openjdk-16-tools-deps-alpine
COPY --from=node node_modules node_modules
RUN clojure -A:shadow-cljs release app

@souenzzo That's an argument for why you don't need it (not why it would be undesirable nor why others shouldn't need it). If we created it and you still didn't need it, you could just not use it. The other images aren't going away.

@souenzzo I still have a use-case for this, using leiningen/fighweel-main which uses webpack for post-processing/bundling.

This is still something I'd like to do. I think it will involve changing some fundamental assumptions in our build system, so the work involved there is the big hurdle.

Tangental tip for those using the clojure docker image with CircleCI and wanting to add nodejs support: you can add nodejs easily enough with their node orb. Here's how I did this for cljdoc's build.


Fix user registration

AC1 - fix spinner position to center
AC2 - fix information window about successful registration ( change to popup information )
AC3 - delete success new page

Need to define functionality for system and user flow


fix: MD005/list-indent

Inconsistent indentation for list items at the same level

@AndreaBarr Please review and merge this housekeeping PR that introduces various whitespace indentation fixes. Thanks.

Looks like the merge of your previous PR to this file brought about the need for a branch update for this PR.

@AndreaBarr Following up for updates.

Another PR branch rebase be useful before someone gets around to merging this content.

@nschonni  please resolve the conflicts so that I can merge this PR

@AndreaBarr I've rebased again


[TST] add tests for _add_volumes and _remove_volumes

Changes proposed in this pull request
Addresses the promise to add tests for the functions _add_volumes and _remove_volumes

Documentation that should be reviewed
N/A

for the codacy check, is there another pattern I should use besides assert condition?

No, that's fine.


Cannot open bags with /script OpenAllBags()

Addon Version
v0.1.24
World of Warcraft Version
Retail
Describe the bug
Unclear when it was working but I updated my betterbag recently and now I cannot open my bags w/ my macro of /script OpenAllBags() -- nothing happens.
Steps to reproduce

Load Better Bags
Create a macro with /script OpenAllBags() or just type it in the text box
Bags do not open :(

Use /script ToggleAllBags()

Thank you!


While selecting/hovering over PayPal options, the PayPal icon has a weird white box fill background.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Expected Result:
Just reduced opacity to bolden the symbol alone, as we do in other menu options.
Like we do in other menu options

Actual Result:
White background behind the icon.

Workaround:
No, UI Bug.
Platform:
Where is this issue occurring? All Platforms

Web
iOS
Android
Desktop App
Mobile Web

Version Number:
Reproducible in staging?:
Reproducible in production?:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @Santhosh-Sellavel
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1632924820242900
Upwork job link - https://www.upwork.com/jobs/~01bce7c6eb5aa7eafc
View all open jobs on GitHub

Triggered auto assignment to @michaelhaxhiu (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Here is the correct file needed: paypal.svg.zip

Proposal
The issue is caused by the existing Paypal icon.
So updating the existing icon, with the icon provided here will solve the issue: https://github.com/Expensify/App/issues/5581#issuecomment-930255443

@shawnborton Can I submit PR or wait for triage to complete.

Let's wait for triage to complete so we follow the standard process here - hopefully it won't take long, this is an easy one and your proposal is good.

I am seeing multiple issues related to the Paypal payment option and relatively there are very minor changes. I suggest combining them into one saving precious resources and efforts.

Hm not a bad idea. I think we could combine these but I'm not sure if it's really necessary. Imo we should get faster results if it's separated (and their a contributor on each one).
Upwork job - https://www.upwork.com/jobs/~01bce7c6eb5aa7eafc

Triggered auto assignment to @AndrewGable (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

I made a mistake, need to assign Engineering right now (not Exported yet)

Triggered auto assignment to @robertjchen (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Looks good and has all the proper details to proceed 👍

Solution:
Update the PayPal logo without white background.
If the solution is still not provided, I can open PR that solves the issue.
I have used the PayPal logo provided here

@maskeynihal
I see you should be new here. Please read the Contributors Guidelines

I already proposed the solution here
Waiting for confirmation from team to start PR.
cc: @michaelhaxhiu @shawnborton
Can I start PR?

@maskeynihal
There are more Open Jobs. You can submit proposals there.
Wait for an engineer to review your proposal, only when your proposal is accepted you should start a PR.

@Santhosh-Sellavel, Thanks. I got it. I was trying the solution only on my forked repo.
I have read the Contributors Guidelines. That's the reason I have not submitted the PR.
I was just asking if I could raise a PR if @Santhosh-Sellavel is not working on this issue.
Please continue to work on it once the proposal is accepted. :hugs:

@maskeynihal  Sorry, PR is on the forked repo, Oops I missed that 😂. We are good here then!


glfw3: 3.3.8 -> 3.3.9

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/glfw/GLFW/releases.
meta.description for glfw3 is: Multi-platform library for creating OpenGL contexts and managing input, including keyboard, mouse, joystick and time
meta.homepage for glfw3 is: https://www.glfw.org/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.3.9 with grep in /nix/store/071x3w38vf3q1kxkpidh62cxfk6k0z5h-glfw-3.3.9
found 3.3.9 in filename of file in /nix/store/071x3w38vf3q1kxkpidh62cxfk6k0z5h-glfw-3.3.9

Rebuild report (if merged into master) (click to expand)

73 total rebuild path(s)

73 package rebuild(s)

First fifty rebuilds by attrpath
MIDIVisualizer
arrayfire
bambu-studio
blackshades
blender
blender-hip
bottles
bottles-unwrapped
chickenPackages_5.chickenEggs.glfw3
chickenPackages_5.chickenEggs.hypergiant
cpu-x
cudaPackages.cuda-samples
cudaPackagesGoogle.cuda-samples
cudaPackages_10.cuda-samples
cudaPackages_11.cuda-samples
cudaPackages_12.cuda-samples
djv
embree
embree2
esshader
forge
glfw
glfw-wayland
glfw3
glslviewer
goxel
gr-framework
heroic
hmcl
icesl
idrisPackages.glfw
imhex
io
jazz2
librealsense-gui
libsForQt5.mapbox-gl-native
libsForQt5.mapbox-gl-qml
libsForQt5.maplibre-gl-native
linux-wallpaperengine
mangohud
mlx42
mmlgui
mujoco
openmvs
pixelnuke
plasma5Packages.mapbox-gl-native
plasma5Packages.mapbox-gl-qml
plasma5Packages.maplibre-gl-native
prismlauncher
prismlauncher-qt5

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/071x3w38vf3q1kxkpidh62cxfk6k0z5h-glfw-3.3.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A glfw3 https://github.com/r-ryantm/nixpkgs/archive/9fa270750951d8de650357b01505c9a19be12c5e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9fa270750951d8de650357b01505c9a19be12c5e#glfw3

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/071x3w38vf3q1kxkpidh62cxfk6k0z5h-glfw-3.3.9
ls -la /nix/store/071x3w38vf3q1kxkpidh62cxfk6k0z5h-glfw-3.3.9/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @MarcWeber @Twey for testing.

@ofborg eval


Fix CICD workflows - pre-build-checks, gh-event-notification, nightly-build

Description

pre-build-checks - fix missing pip-audit=report.md, cleanup displayed messages
gh-event-notification -
nightly-build - remove smoke test, rename to sit-build

Motivation and Context
bug fix
Type of Change

fix: A bug fix

How to Test
Run workflow manually in ci-workflow-dev branch.
Checklist
Please check all the boxes that apply to this pull request using "x":

[x]  I have tested the changes locally and verified that they work as expected.
[x]  I have added or updated the necessary documentation (README, API docs, etc.).
[ ]  I have added appropriate unit tests or functional tests for the changes made.
[ ]  I have followed the project's coding conventions and style guidelines.
[ ]  I have rebased my branch onto the latest commit of the main branch.
[ ]  I have squashed or reorganized my commits into logical units.
[ ]  I have added any necessary dependencies or packages to the project's build configuration.
[x]  I have performed a self-review of my own code.
[x]  I have read, understood and agree to the Developer Certificate of Origin below, which this project utilises.

Screenshots (if applicable)
[If the changes involve visual modifications, include screenshots or GIFs that demonstrate the changes.]
Additional Notes
[Add any additional information or context that might be relevant to reviewers.]

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
   have the right to submit it under the open source license
   indicated in the file; or

(b) The contribution is based upon previous work that, to the best
   of my knowledge, is covered under an appropriate open source
   license and I have the right under that license to submit that
   work with modifications, whether created in whole or in part
   by me, under the same open source license (unless I am
   permitted to submit under a different license), as indicated
   in the file; or

(c) The contribution was provided directly to me by some other
   person who certified (a), (b) or (c) and I have not modified
   it.

(d) I understand and agree that this project and the contribution
   are public and that a record of the contribution (including all
   personal information I submit with it, including my sign-off) is
   maintained indefinitely and may be redistributed consistent with
   this project or the open source license(s) involved.

Hi @imda-kwokwk, I added some comments for the license-file-gen.yaml file.

Changed to "Notices FIle Generation"


Bad contrast between selection box color and list bullet

Regardless the colors, this is something inherited from three.js editor where they used the colors to show entity types, each color represent a light, camera, or whatever.
We already have this functionality with the component's icons, so I don't know if it's a bit redundant to have colored bullets or just keep then using the same base color. Right now I've one color for a-entity elements and another one for non-a-entity, and maybe if we hover the icon it will show the html element name. Do you think it could be useful that way?
Regarding the colors, I'll ask Dennis to give some higher contrast color range.

Agree its redundant.   I was confused as to what those dots were even.

To be honest, I think those icons and bullets are confusing anyways.  I don't see much value in having them since one entity can have any number of components.  so it's not that really helpful.

Unity scene hierarchy doesn't have any icons.

The bullets we could just remove and change them for arrows like treeview. But I believe the icons will give you a quick look of the kind of entity you're dealing with, for example if you're looking for the camera or light you'll get it quite fast. This is the approach 3d software like cinema4d or 3dsmax follow.

Sure, for camera yes, I agree that would be useful.

Fixed on https://github.com/aframevr/aframe-editor/pull/105


Using oobUrl in didcomm:// deeplink for linking with shortened url

When using the didcomm:// scheme to link to a didcomm enabled application, you lose the ability to use shortened urls, as you don't know where to resolve the invitation from.
We've encountered with larger OOB invitations that they exceed the character limit iOS allows and thus it's not possible to use a didcomm deeplink for this purpose.
For this reason we've started using a custom oobUrl property on the didcomm:// deeplink that contains a shortened url.
a working link looks like this:
didcomm://?oobUrl=https%3A%2F%2Fparadym.id%2Finvitation%2Fefaf249a-39e5-42ab-9083-0aab96e7c3f1

I think it could be useful to standardize this custom parameter for passing a shortened oob url to a didcomm deeplink for the case described above.
Thoughts?
cc @tommylans

I think this is a good idea, but given that unified DIDComm deeplinking is being marked as STALLED in https://github.com/hyperledger/aries-rfcs/pull/827 it gives me the impression that it was not broadly implemented within Aries community.
Do you know if this is being used in different mobile apps? If that's the case I think the status should be reconsidered.

Don’t put too much stalk into the STALLED marking of that RFC — I may be out of the loop on that one.
I think @TimoGlastra ’s idea seems kinda clever.  I think it still suffers from the “iOS doesn’t do deep links nicely”, but its better than not having no redirect and impossibly large invitations. I do notice that Timo explicitly mentions iOS though, so that is interesting.

I think it still suffers from the “iOS doesn’t do deep links nicely”

Agreed that's not something that this will solve. But is is nice to add a didcomm deeplinkg to allow opening in other wallets (we by default use universal links to open in specific wallet directly, but this enables "Open in other wallet", although on iOS you can't select which wallet sadly)

I think RFC 0268 may do too much, and is a bit outdated, so I think it can benefit from either being updated or being replaced with a very simple "DIDComm Deeplinking" RFC that covers a) didcomm://, and b) oobUrl query params (or oob_uri would be more in line with Aries standards)

Plus 1 on the idea of a simple "DIDComm Deeplinking" RFC

I'm also in favor of introducing a simple DIDComm Deeplinking RFC--would this RFC cover iOS Unviersal Links? I lean towards no--as Universal Links are inherently limited to the app owner's domain (websites that can redirect using a Universal Link requires providing authorized domains with .well-known/apple-app-site-association). I've demonstrated a method (https://github.com/JamesKEbert/aries-invitation-service & sample deployment) for having a community managed service to allow users to choose the app they'd like to use for an iOS device, which is open-source friendly, but this is a fairly significant effort to get launched and running (which I think is beyond the scope of what we need today).
Also @TimoGlastra, have you run into the same length constraints when using an Android intent?
intent://invite?oob=${props.base64Invite}#Intent;action=android.intent.action.VIEW;scheme=didcomm;end

I think RFC 0268 may do too much, and is a bit outdated, so I think it can benefit from either being updated or being replaced with a very simple "DIDComm Deeplinking" RFC that covers a) didcomm://, and b) oobUrl query params (or oob_uri would be more in line with Aries standards)

I've recently discovered that BCGov have implemented something very similar to this: an _url query parameter that contains a Base64URL representation of the actual short URL where the invitation object can be retrieved.
Although it is easy for a wallet to support both, I think it would be nice to standardize this, so we don't end up making multiple approaches that do pretty much the same thing.


Re-design run for signal handlers

This PR re-designs the signal handlers to improve inference.

bors r+


Errors after compiling of prolect

Hi.
I tried project BlynkSprinklerRelay, but after compiling of prolect i got messages about errors:
D:\KLG\Arduino\Arduino_Projects\BlynkSprinklerRelay-master\BlynkSprinklerRelay\BlynkSprinklerRelay.ino: In function 'void loop()':
BlynkSprinklerRelay:189: error: 'class BlynkWifi' has no member named 'virtualRead' Blynk.virtualRead(0);
exit status 1
'class BlynkWifi' has no member named 'virtualRead'.
What it may be?
Another question: can I use of  the Your dashboard for this project  on  my  smartphone? If yes then how?
Thank You.

he sir i have some problems in wifi control relay.
the errors are mentioned in this document.
I USED TWO METHODS BUT NO ONE IS CORRECT.
PROGRAM FOR.docx

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @


Move option of per capita to chart

The options of each chart , i.e. per capita in this case, is kept in an object chartOptions. The key of chartOptions is mprop of the chart because each chart represents a unique mprop. The value is a dictionary of options.
An example of chartOptions:  {count: {pc: true}}. It means:  per capita for the chart with mprop = count is true.
More options such as log scale will be added in the future.
We encode value of chartOptions in the url. The initial value of chartOption would be decoded from the url and updated by the callback function passed to the "onClick" prop of the per Capita buttons.

Some high level suggestions:
Binding the chart options to mprop maybe a too strong assumption. If we decided to have other ways to group the stats vars then the logic would change a lot. A more robust way is to enclose the "grouping" information in the chart options:
chartOption = [
{
statsVars: [sv1, sv2, sv3]
pc: true
log: false
},
{
statsVars = [sv4]
pc: false,
log: true
}
...
]
The grouping information is from groupStatsVars function and would naturally adjust when the logic in that function change.
In each Chart component, it will check if all the stats var matches (which should), unless the logic of grouping function changes and new app got old url. Need some thought on err handling here.

I think we still need a key for each chart that does not change when we add/remove statsVars. It should be the same key as grouping, which is mprop now, it can be mprop+something else in the future.
The problem of the suggested way is that, we would have to change ChartOptions when we add/remove statsVars. It would make the logic more complex. The current logic is to use the default options for each chart, and set chartOptions when the option buttons are clicked.


Added Implementation for TableParser

The pull request introduces a new TableParser module, which would help to parse the TableElement objects and retrieve the parsed table data accordingly. To utilize it, follow these steps:

Obtain the desired TableElement object.
Instantiate TableParser by passing the TableElement object to the constructor.
Invoke the parse method to process the table.
Retrieve the parsed data as either a:

DataFrame using the table_as_df method
JSON using the table_as_json method

Example:

@nnilayy,
Firstly, a big thank you for your dedication and hard work on the table parsing feature – it's a crucial part of our project at Alphanome AI!
I've taken the liberty of refining a few minor points highlighted by the Ruff linter and other checks. For your reference, you can run these checks on your own using ruff check --fix sec_parser/ && mypy && pytest tests/unit/. Alternatively, if you have Task installed, simply execute task pre-commit-checks to run all the checks as outlined in our Taskfile.yml.
Unit Tests and Quality Assurance
Ensuring the quality of our parser is pivotal. We're focusing on introducing robust Unit Tests to achieve this. You can understand more about our testing philosophy here.
Here's what I've added to guide our testing efforts:

A sample table from Apple's latest 10-Q report as a test case:

https://github.com/alphanome-ai/sec-parser/blob/46b5ff8f2a6ea5a7b7ffe4068af86bad97951754/tests/unit/semantic_elements/table_element/_data_for_table_parser.py#L1-L5

The expected parsing output for this table:

https://github.com/alphanome-ai/sec-parser/blob/46b5ff8f2a6ea5a7b7ffe4068af86bad97951754/tests/unit/semantic_elements/table_element/test_table_parser.py#L11-L30

A visual comparison of the input and expected output:

Could you review these test cases and adjust them if they don't align with your expectations for the output? Also, it would be great if you could add more diverse or edge-case examples to our test suite (you could do it just by adding more items to the tests := [ list). This would immensely help in covering a wider range of scenarios and ensuring robustness in our parser.
Thank you for your continuous contributions and support. Your efforts are greatly valued in our community!

Hey Elijas,
Thank you so much for refining the code on my behalf and for your feedback regarding the use of Ruff Linter and other IDE tools. My apologies for a sloppy commit history. I'm gonna work on keeping up with the common practice and the latest IDE tools to make the workflow smoother and more professional.
As for the tests, I'll work on adding more edge case tests for the parser. As for the output, I do have something different in mind, as I think the parser could be refined even more to reduce data redundancy. As in this example, if we see the output data frame, for columns 2 & 3, the rows except $ signs are the same, so they could be merged, Ultimately leaving a 2-column data frame, the implementation for which is already in the parser. So yeah regarding the output and further refining the parser, I would love to discuss that with you in Discord.
Again thank you so much for the feedback and for merging this pr.

refining the code on my behalf

I forgot to add link to the refinement PR, in case you'd want to have a reference -- https://github.com/alphanome-ai/sec-parser/pull/47

sloppy commit history.

No worries at all, Github provides with a very convenient "Squash and merge" functionality, which overwrites all PR commit history with 1 commit with a custom message. So for contributor convenience, we're just doing 1 PR = 1 commit 👍

I'm gonna work on keeping up

Once again, no worries at all -- not having latest linters and stuff like that should never be a reason to re-consider creating a PR or delay submitting a contribution 🙌
Thanks again for the PR!


SmoothQuant doesn't work with cpu offloading

Describe the bug
When using a SmoothQuantModifier and cpu offloading there is a conflict of tensors not being on the right device.
Expected behavior
cpu offloading should work w/ SmoothQuant 😄
Environment
I don't think environment is relevant.
To Reproduce
from transformers import AutoTokenizer
from datasets import load_dataset
from llmcompressor.transformers import SparseAutoModelForCausalLM, oneshot
from llmcompressor.modifiers.quantization import GPTQModifier
from llmcompressor.transformers.compression.helpers import custom_offload_device_map

model_id = "meta-llama/Meta-Llama-3.1-405B-Instruct"

num_samples = 512
max_seq_len = 4096
num_gpus = 8
max_memory_per_gpu = "20GB"

tokenizer = AutoTokenizer.from_pretrained(model_id)

def preprocess_fn(example):
  return {"text": tokenizer.apply_chat_template(example["messages"], add_generation_prompt=False, tokenize=False)}

ds = load_dataset("neuralmagic/LLM_compression_calibration", split="train")
ds = ds.shuffle().select(range(num_samples))
ds = ds.map(preprocess_fn)

recipe = [
  SmoothQuantModifier(smoothing_strength=0.8),
  GPTQModifier(
    sequential=True,
    targets="Linear",
    scheme="W8A8",
    ignore=["lm_head"],
    dampening_frac=0.01,
    observer="mse"
  )
]

device_map = custom_offload_device_map(
  model_id,
  max_memory_per_gpu=max_memory_per_gpu,
  num_gpus=num_gpus,
  torch_dtype="auto",
)

model = SparseAutoModelForCausalLM.from_pretrained(
  model_id,
  device_map="auto",
)

oneshot(
  model=model,
  dataset=ds,
  recipe=recipe,
  max_seq_length=max_seq_len,
  num_calibration_samples=num_samples,
)

model.save_pretrained("Meta-Llama-3.1-405B-Instruct-quantized.w8a8")

Errors
2024-08-18T11:40:15.797525+0000 | _apply_smoothing | INFO - Smoothing activation scales...
Traceback (most recent call last):
  File "/root/.clearml/venvs-builds/3.10/code/queue_llmcompressor_oneshot.py", line 253, in <module>
    oneshot(
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/transformers/finetune/text_generation.py", line 76, in oneshot
    main(model_args, data_args, training_args)
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/transformers/finetune/text_generation.py", line 364, in main
    stage_runner.one_shot()
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/transformers/finetune/runner.py", line 171, in one_shot
    self.trainer.one_shot(calibration_data=calib_data, stage=stage)
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/transformers/finetune/session_mixin.py", line 401, in one_shot
    apply(
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/core/session_functions.py", line 184, in apply
    return active_session().apply(
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/core/session.py", line 210, in apply
    self.initialize(**kwargs)
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/core/session.py", line 156, in initialize
    mod_data = self._lifecycle.initialize(
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/core/lifecycle.py", line 126, in initialize
    data = mod.initialize(state=self.state, **extras)
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/modifiers/stage.py", line 124, in initialize
    modifier.initialize(state, **kwargs)
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/modifiers/modifier.py", line 118, in initialize
    initialized = self.on_initialize(state=state, **kwargs)
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/modifiers/smoothquant/base.py", line 135, in on_initialize
    self._apply_smoothing(state.model)
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/modifiers/smoothquant/base.py", line 282, in _apply_smoothing
    scales = self._calculate_smoothing_scales(balance_layers, activation_scales)
  File "/root/.clearml/venvs-builds/3.10/lib/python3.10/site-packages/llmcompressor/modifiers/smoothquant/base.py", line 332, in _calculate_smoothing_scales
    scales = activation_scales.pow(self.smoothing_strength) / weight_scales.pow(
  File "/usr/local/lib/python3.10/dist-packages/torch/_prims_common/wrappers.py", line 266, in _fn
    result = fn(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/_refs/__init__.py", line 1171, in div
    return true_divide(a, b)
  File "/usr/local/lib/python3.10/dist-packages/torch/_prims_common/wrappers.py", line 266, in _fn
    result = fn(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/_prims_common/wrappers.py", line 138, in _fn
    result = fn(**bound.arguments)
  File "/usr/local/lib/python3.10/dist-packages/torch/_refs/__init__.py", line 1044, in _ref
    output = prim(a, b)
  File "/usr/local/lib/python3.10/dist-packages/torch/_refs/__init__.py", line 1738, in true_divide
    return prims.div(a, b)
  File "/usr/local/lib/python3.10/dist-packages/torch/_ops.py", line 667, in __call__
    return self_._op(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/_library/abstract_impl.py", line 95, in meta_kernel
    return abstract_impl_holder.kernel(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/_library/utils.py", line 20, in __call__
    return self.func(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/library.py", line 788, in inner
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/_library/custom_ops.py", line 471, in fake_impl
    return self._abstract_fn(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/_prims/__init__.py", line 383, in _prim_elementwise_meta
    utils.check_same_device(*args_, allow_cpu_scalar_tensors=True)
  File "/usr/local/lib/python3.10/dist-packages/torch/_prims_common/__init__.py", line 742, in check_same_device
    raise RuntimeError(msg)

Additional context
I met this issue when quantizing Meta-Llama-3.1-405B-Instruct but I'm sure there's no need to use such a large model to reproduce it.

model = SparseAutoModelForCausalLM.from_pretrained(
model_id,
device_map="auto",
)

It seems that you did not pass the correct device_map here.
device_map = custom_offload_device_map(
  model_id,
  max_memory_per_gpu=max_memory_per_gpu,
  num_gpus=num_gpus,
  torch_dtype="auto",
)
model = SparseAutoModelForCausalLM.from_pretrained(
  model_id,
  device_map=device_map,
)

Closing this out due to lack of activity. Please reopen if you are still hitting the issue!


Extended gateway test for VLAN

Currently not run due to vmxnet3 with VLAN not working in qemu (being worked on).

Will fail until #1945 is merged.