Is network alias supported in Azure Container Apps/Environment

Please provide us with the following information:

This issue is a: (mark with an x)

[ ] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
This is rather a question..
How do we implement network aliases within Azure Container Environment. While docker compose supports network aliases, if we feed the docker compose, does Azure Container Apps use the network alias?
For example, I have multiple azure container environments each of them having its own mongo db instances that needs to be referenced by name "mongo" by other container apps. i can not have the service name as mongo in every environment as Azure Container Environment is requiring the service names to be globally unique.
How to achieve local dns resolution within azure container environment so that the name "mongo" resolves to the local instance within the container environment?
Steps to reproduce

..
..

Expected behavior [What you expected to happen.]
Actual behavior [What actually happened.]
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Ex. Did this issue occur in the CLI or the Portal?

@kamalsivalingam Hi, Yes, if you have multiple Azure Container Environments, each with its own MongoDB instances, it's possible for other container apps to reference them by the name 'mongo'.
-- In Azure Container Service (ACS), there is a feature called appname that functions similarly to Docker Composes network alias.

Thanks @v-vish. If i have multiple container app environments, the name of the container app should be unique across all the environments. So do i have to suffix with something like environment name? Once i suffix and make the name unique, can i access the db container app from other container app using the name?

You're application name does not have to be unique across all environments. You can use the same name over and over as long as it's not within the same environment. Are you wanting to connect from one environment to another one which hosts your DB?

@simonjj Looks like the container app name should be unique across container environments not just within.
I get below error when i try to use the same name in a different environment...
(ContainerAppEnvironmentMismatch) Container App 'gw-pr-303' already exists in a different environment. To create it in the environment '/subscriptions/xxx-xxx-xxx/resourceGroups/xx-xx-xx/providers/Microsoft.App/managedEnvironments/pr-304' delete it from the environment 'pr-303' first.


Usenet widget

Environment
Docker
Version
0.11.2
Describe the problem
I've configured my usenet integration using port 80

But the usenet widget is throwing an error for both history and queue Cannot connect to NZBGet. Missing port in app config.
Ping is working for the application so that ruled out network connectivity issue

My thoughts right now is that app.port is returning empty string since its port 80?
Additional info
Looking at the docs here https://nodejs.org/api/url.html#urlport it seems like we need to add some support for default protocols in the widget logic
Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues
[X] You've tried to debug yourself

I haven't looked into it before. Is your internal URL an IP ?

Or we can remove this check for people that use default protocols. https://github.com/ajnart/homarr/blob/99df5d77601c0eacba02dcf4423d472e4a887849/src/pages/api/modules/usenet/nzbget/nzbget-client.ts#L9-L11

so in my example http://nzbget.internal is all I need to access nzbget in my local network. It gets terminated on a reverse proxy (traefik) which knows the default port for my apps.

Internal IP should be internal as it states, you are meant to use the containers IP directly , not any hostnames

so my internal url can change anytime since this is a kubernetes clusters. If the app goes down a new one spins up which will be new ip. So homar can't support internal url only internal static ips?

also it doesn't matter if I use a hostname or ip. If the nzbget container was running on my computer on port 80. The check will still fail even on http://<IP_ADDRESS>:80 since its a default port for http protocol.


feat: add test client example in docs for streaming responses

As a user, I want lanarky to provide a test client example in the docs for testing streaming responses.
Acceptance Criteria

[ ] add test client example in docs

test clients added as part of v0.8 release.
You can find the documentation here: https://lanarky.ajndkr.com/getting-started/#client


Bump dependencies

The compose multiplatform version needed to be bumped to be compatible with projects using kotlin 2.0.0 and related compose versions. Bump other dependencies at the same time.
Bump kotlin and compose according to:  https://www.jetbrains.com/help/kotlin-multiplatform-dev/compose-compiler.html#migrating-a-compose-multiplatform-project
Fixes the issue where a project which has already been updated using this library gets the error: https://github.com/JetBrains/compose-multiplatform/issues/4277

Thanks!


Xamarin binding

Please create an Xamarin binding for this SDK

I'll look into that

Have you already looked here? There are already bindings for Xamarin. Would that fit for you?
https://www.nuget.org/profiles/ProjectOxfordSDK


kind: upgrade to 0.12.0

Issue #, if available:
Description of changes:
This updates kind to 0.12.0 from 0.11.1.  Added the updating section to the rebuild and updated the various constants which are replaced during the build to override image tags.  Bumped golang to 1.17.  Removes iptables alternatives call since this image is now based off the iptables minimal image which has this same code.
Also clean go version handling and update helper script to match builder base, similar to https://github.com/aws/eks-distro/pull/848
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

/unhold


Added batch update for statuses

Overview
This PR adds a batch endpoint for updating statuses of credentials. It is the last PR that fixes #347
Description
Added the v1/credentials/status/batch endpoint. See the swagger spec file for documentation on the request/response schemas.
How Has This Been Tested?
Unit and integration tests.

Codecov Report

Merging #658 (d486ace) into main (1955573) will decrease coverage by 0.17%.
The diff coverage is 4.34%.

@@            Coverage Diff             @@
##             main     #658      +/-   ##
==========================================
- Coverage   25.72%   25.55%   -0.17%
==========================================
  Files          56       56
  Lines        6254     6299      +45
==========================================
+ Hits         1609     1610       +1
- Misses       4369     4413      +44
  Partials      276      276

Files Changed
Coverage Δ

config/config.go
30.40% <ø> (ø)

integration/common.go
2.15% <0.00%> (-0.06%)
:arrow_down:

pkg/server/router/credential.go
11.93% <0.00%> (-1.38%)
:arrow_down:

pkg/server/server.go
71.37% <100.00%> (+0.11%)
:arrow_up:


What is the difference between @junobuild/core and @junobuild/core-peer

Hello
I have a question:
what is the difference between
https://www.npmjs.com/package/@junobuild/core
and
https://www.npmjs.com/package/@junobuild/core-peer

Hi @CodingFu,
Feature-wise, both @junobuild/core and @junobuild/core-peer are identical. In fact, the code of the first is copied into the second at build time.
Originally and in the future, I want to support only @junobuild/core, which pre-packages everything needed by the client.
Unfortunately, because the Agent-js libraries require some NodeJS polyfills, I started noticing issues with certain bundlers and frameworks, for example, SvelteKit. For some reason, even though everything is pre-polyfilled in the core, the library started to face issues with unresolved NodeJS APIs such as Buffer and other components. Despite trying hard to find a solution, I ultimately figured out that there was no way to embed Agent-js for those types of projects. The only solution was to ship the library with everything @dfinity/agent|client|etc. set as peer dependencies. That's why the core-peer library was added to the stack.
Note that it is not directly documented which library should be used with what type of bundler and framework, but all the guides in the documentation and templates of the create CLI are using the appropriate library type.
Let me know if you have more questions on that matter.

I gonna close this question but, if anthing is unclear or requires to be documented in the documentation please let me know @CodingFu. Happy to reopen the issue if useful.


Resting dropped connection

Hi,
I am constantly seeing Resetting dropped connection for every URL,
Could you please let me know Why i am getting and how do i avoid such error message?
Here is python snippet
def __init__(self, base_url, username, password):
        self.session = requests.Session()
        self.session.auth = (username, password)
        adapter = requests.adapters.HTTPAdapter(pool_connections=1, pool_maxsize=100, pool_block=True, max_retries=0)
        self.session.mount('http://', adapter)
        self.base_url = base_url
        start_url = base_url + 'index.html'
        _req = self.session.get(start_url)
        self.cookie = _req.cookies
        print self.cookie

    def get_entry(self, url):
        print self.cookie
        _req = self.session.get(url, cookies=self.cookie)
        print _req.headers
        return _req

    def post_entry(self, url, body):
        header = {"Content-type":"application/json"}
        print self.cookie
        _req = self.session.post(url=url, data=body, cookies=self.cookie, headers=header)
        print _req.headers
        print _req.text
        return _req

Thanks
Malli

I further debugged and I came to the socket information has,
However the cookie information is common across all the connection
The socket information must be False every time?
<RequestsCookieJar[<Cookie session=4D51754C for <IP_ADDRESS>/>]>

connection <requests.packages.urllib3.connection.HTTPConnection object at 0x032FD5F0>
{'_HTTPConnection__state': 'Idle', '_buffer': [], '_create_connection': <function create_connection at 0x02ABF130>, '_tunnel_headers': {}, '_tunnel_host': None, 'sock': None, 'port': 80, 'strict': True, 'host': '<IP_ADDRESS>', '_tunnel_port': None, 'timeout': None, 'socket_options': [(6, 1, 1)], 'source_address': None, '_HTTPConnection__response': None, '_method': 'GET'}

send: 'GET test/one/data HTTP/1.1\r\nHost: <IP_ADDRESS>\r\nAccept-Encoding: gzip, deflate\r\nAccept: */*\r\nUser-Agent: python-requests/2.8.1\r\nConnection: keep-alive\r\nCookie: session=4D51754C\r\nAuthorization: Basic QURNSU46UEFTU1dPUkQ=\r\n\r\n' reply: 'HTTP/1.0 200 OK\r\n' header: Server: xxx TinyServer header: MIME-version: 1.0 header: Cache-Control: no-store, no-cache; header: Pragma: no-cache; header: Set-Cookie: session=4D51754C; path=/; header: Content-Type: application/json header: Expires: -1 header: Content-Length: 2 {'Content-Length': '2', 'Set-Cookie': 'session=4D51754C; path=/;', 'Expires': '-1', 'Server': 'ADTRAN TinyServer', 'Pragma': 'no-cache;', 'Cache-Control': 'no-store, no-cache;', 'Content-Type': 'application/json', 'MIME-version': '1.0'}

Thanks
Malli

Thanks for this @vkosuri!
This is expected behaviour. Requests attempts to "connection pool", which means that it attempts to reuse sockets as frequently as possible. Sometimes, requests will come to try to re-use a socket and find that the underlying TCP connection got closed while it's away. When that happens, it'll reset the connection. We mention this in the logs because it's potentially important to debug very subtle issues.
The important things to know are:

this is a log message, not a warning or error message
it's logged at INFO level, which is fairly low

If you want to make the message go away, simply set the log level higher than INFO or disable logging for the requests.packages.urllib3 logger.

@Lukasa How to disable Retrying warning messages?
[ WARN ] Retrying (Retry(total=9, connect=None, read=None, redirect=None)) after connection broken by 'NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7fe2c71ad150>: Failed to establish a new connection: [Errno 111] Connection refused',)'

I am getting thousands of Warning messages in my testcase, due to this effect the log file size was increasing drastically. Is there any possibility to remove/disable warning message when NewConnectionError ?

@vkosuri That warning is raised by urllib3. If you want to disable that message, either handle retries yourself (stop passing the parameter into urllib3), or raise the log level for urllib3, or disable logging from urllib3 entirely. The logger you want to disable is the one at requests.packages.urllib3.connectionpool.

Thank you @Lukasa I am using Robotframework-Requests. I have added fallowing lines code to Requests.py
Still it is not working? Am i missed anything? Could you please suggest me?
# Disable warnings
logging.basicConfig() # you need to initialize logging, otherwise you will not see anything from requests
logging.getLogger().setLevel(logging.DEBUG)
requests_log = logging.getLogger("requests")
requests_log.setLevel(logging.DEBUG)
requests_log.propagate = True

That has enabled logging, not disabled it. You need to set the level higher than that (e.g. to logging.ERROR).

Thanks @Lukasa It's working
logging.basicConfig() # you need to initialize logging, otherwise you will not see anything from requests
logging.getLogger().setLevel(logging.ERROR)
requests_log = logging.getLogger("requests")
requests_log.setLevel(logging.ERROR)
requests_log.propagate = True


oneup image build fails on minikube v1.15.0

Running tilt up on the oneup tutorial project fails with:

ERROR:
╎
╎ ERROR IN: [internal] extracting build context
╎   → container_linux.go:345: starting container process caused "process_linux.go:424: container init caused "rootfs_linux.go:109: jailing process inside rootfs caused \"pivot_root invalid argument\"""
  ERROR: ImageBuild: executor failed running [copy --unpack /src/context /out/]: exit code: >1

The output of tilt doctor is:
[user@machine oneup]$ tilt  doctor
Tilt: v0.9.4, built 2019-07-15
System: linux-amd64
---
Docker
- Host: tcp://<IP_ADDRESS>:2376
- Version: 1.39
- Builder: 2
---
Kubernetes
- Env: minikube
- Context: minikube
- Cluster Name: minikube
- Namespace: default
- Container Runtime: docker
- Version: v1.15.0
---
Thanks for seeing the Tilt Doctor!
Please send this info along when filing bug reports. 💗

Running DOCKER_BUILDKIT=1 docker build -t x . works fine
[iliec@is-devtag oneup]$ DOCKER_BUILDKIT=1 docker build -t x .
Sending build context to Docker daemon 5.632 kB
Step 1/5 : FROM golang:1.11-alpine
1.11-alpine: Pulling from library/golang
050382585609: Pull complete
0bb4ee3360d7: Pull complete
893f09c2afb0: Pull complete
c2e22f8e95ff: Pull complete
e908c6b3f8b4: Pull complete
Digest: sha256:e14164f34ebf0197a6d07a22ad3518374f5beb2a72ec61eb28f794562d8b9183
Status: Downloaded newer image for golang:1.11-alpine
 ---> d9aba3165478
Step 2/5 : WORKDIR /go/src/github.com/windmilleng/integration/oneup
 ---> Running in 354a067b577f
Removing intermediate container 354a067b577f
 ---> 87f70dcf9787
Step 3/5 : ADD . .
 ---> 0157b582e0db
Step 4/5 : RUN go install github.com/windmilleng/integration/oneup
 ---> Running in a9fa0b2470d4
Removing intermediate container a9fa0b2470d4
 ---> 77bcdeb9d4e9
Step 5/5 : ENTRYPOINT /go/bin/oneup
 ---> Running in a786a0c34ffe
Removing intermediate container a786a0c34ffe
 ---> bb51112d5df4
Successfully built bb51112d5df4
Successfully tagged x:latest

The system i'm using is:
[user@machine oneup]$ cat /etc/redhat-release
Fedora release 30 (Thirty)

Thanks for the report! Do you have something in your env setting DOCKER_BUILDKIT=1?
For now, you can workaround this by setting DOCKER_BUILDKIT=0 when running tilt.
I'm also going to update Tilt so that it will never use buildkit on minikube.
Background info: The problem is that the minikube docker server doesn't support buildkit (https://github.com/kubernetes/minikube/issues/4143). A good way to verify this is something like:
DOCKER_BUILDKIT=1 tilt docker -- build -t x .

which will talk to the same docker server that Tilt does (rather than your default docker server).

Run some more tests and got it to work:
machine:oneup <user>$ env | grep DOCKER
DOCKER_HOST=tcp://<IP_ADDRESS>:2376
DOCKER_TLS_VERIFY=1
DOCKER_CERT_PATH=/Users/<user>/.minikube/certs

If i run with this set to 1 it fails. Setting it to 0 works.
machine:oneup <user>$ DOCKER_BUILDKIT=1 tilt docker -- build -t x .
Running Docker command as:
DOCKER_BUILDKIT=1 DOCKER_HOST=tcp://<IP_ADDRESS>:2376 DOCKER_CERT_PATH=/Users/<user>/.minikube/certs DOCKER_TLS_VERIFY=1 docker build -t x .
---
[+] Building 31.3s (7/8)
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 220B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/golang:1.11-alpine                                                                                3.5s
 => CACHED [internal] helper image for file operations                                                                                0.0s
 => [1/3] FROM docker.io/library/golang:1.11-alpine@sha256:e14164f34ebf0197a6d07a22ad3518374f5beb2a72ec61eb28f794562d8b9183                                                 27.0s
 => => resolve docker.io/library/golang:1.11-alpine@sha256:e14164f34ebf0197a6d07a22ad3518374f5beb2a72ec61eb28f794562d8b9183                                                  0.0s
 => => sha256:893f09c2afb0995b31b535c5ef1e3e6baf15d6e3ba20cca23ab228dc23959bba 156B / 156B                                                                                1.4s
 => => sha256:e14164f34ebf0197a6d07a22ad3518374f5beb2a72ec61eb28f794562d8b9183 1.65kB / 1.65kB                                                                               0.0s
 => => sha256:2edee773ecab4eebb906947fe54e6cf0a6129d0ccffdc8c2f7db7a011d6d47dc 1.36kB / 1.36kB                                                                               0.0s
 => => sha256:d9aba316547821e8316be967be44340469b40bd9b75cbfa32fa1e90187856188 3.81kB / 3.81kB                                                                               0.0s
 => => sha256:0503825856099e6adb39c8297af09547f69684b7016b7f3680ed801aa310baaa 2.79MB / 2.79MB                                                                               1.4s
 => => sha256:0bb4ee3360d7674b72befc5a29a65d17c2aad071dba363cedc48e21337e2f9fc 301.72kB / 301.72kB                                                                           1.6s
 => => extracting sha256:0503825856099e6adb39c8297af09547f69684b7016b7f3680ed801aa310baaa                                                                                0.8s
 => => sha256:c2e22f8e95fffa1ed4442d5409e8a22d90a3af80eefa1c34e3db6399a779501f 110.30MB / 110.30MB                                                                           9.0s
 => => sha256:e908c6b3f8b4a22a83fa4a674339b5bdb314a068d530ebe03a47704258c9f2e0 125B / 125B                                                                                1.9s
 => => extracting sha256:0bb4ee3360d7674b72befc5a29a65d17c2aad071dba363cedc48e21337e2f9fc                                                                                0.5s
 => => extracting sha256:893f09c2afb0995b31b535c5ef1e3e6baf15d6e3ba20cca23ab228dc23959bba                                                                                0.0s
 => => extracting sha256:c2e22f8e95fffa1ed4442d5409e8a22d90a3af80eefa1c34e3db6399a779501f                                                                                16.9s
 => => extracting sha256:e908c6b3f8b4a22a83fa4a674339b5bdb314a068d530ebe03a47704258c9f2e0                                                                                0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 1.71kB                                                                                0.0s
 => ERROR [2/3] ADD . .                                                                                0.6s
------
 > [2/3] ADD . .:
#7 0.336 container_linux.go:345: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:109: jailing process inside rootfs caused \\\"pivot_root invalid argument\\\"\""
------
executor failed running [copy --unpack /src-0 go/src/github.com/windmilleng/integration/oneup/]: exit code: 1
Error: exit status 1

If i run with this set to 0 it works:
machine:oneup <user>$ DOCKER_BUILDKIT=0 tilt docker -- build -t x .
Running Docker command as:
DOCKER_BUILDKIT=0 DOCKER_HOST=tcp://<IP_ADDRESS>:2376 DOCKER_CERT_PATH=/Users/<user>/.minikube/certs DOCKER_TLS_VERIFY=1 docker build -t x .
---
Sending build context to Docker daemon  5.632kB
Step 1/5 : FROM golang:1.11-alpine
1.11-alpine: Pulling from library/golang
050382585609: Already exists
0bb4ee3360d7: Already exists
893f09c2afb0: Already exists
c2e22f8e95ff: Already exists
e908c6b3f8b4: Already exists
Digest: sha256:e14164f34ebf0197a6d07a22ad3518374f5beb2a72ec61eb28f794562d8b9183
Status: Downloaded newer image for golang:1.11-alpine
 ---> d9aba3165478
Step 2/5 : WORKDIR /go/src/github.com/windmilleng/integration/oneup
 ---> Running in 4a42b36c776e
Removing intermediate container 4a42b36c776e
 ---> 0bc1a1f9fa19
Step 3/5 : ADD . .
 ---> f6223d806d91
Step 4/5 : RUN go install github.com/windmilleng/integration/oneup
 ---> Running in c589d614ed17
Removing intermediate container c589d614ed17
 ---> 61aa85cbeea3
Step 5/5 : ENTRYPOINT /go/bin/oneup
 ---> Running in 8065ec465340
Removing intermediate container 8065ec465340
 ---> 183fec10c7fa
Successfully built 183fec10c7fa
Successfully tagged x:latest

Running tilt up with this set to 0 also does the trick
machine:oneup <user>$ DOCKER_BUILDKIT=0 tilt up

Run some more tests and got it to work:
machine:oneup <user>$ env | grep DOCKER
DOCKER_HOST=tcp://<IP_ADDRESS>:2376
DOCKER_TLS_VERIFY=1
DOCKER_CERT_PATH=/Users/<user>/.minikube/certs

If i run with this set to 1 it fails. Setting it to 0 works.
machine:oneup <user>$ DOCKER_BUILDKIT=1 tilt docker -- build -t x .
Running Docker command as:
DOCKER_BUILDKIT=1 DOCKER_HOST=tcp://<IP_ADDRESS>:2376 DOCKER_CERT_PATH=/Users/<user>/.minikube/certs DOCKER_TLS_VERIFY=1 docker build -t x .
---
[+] Building 31.3s (7/8)
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 220B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/golang:1.11-alpine                                                                                3.5s
 => CACHED [internal] helper image for file operations                                                                                0.0s
 => [1/3] FROM docker.io/library/golang:1.11-alpine@sha256:e14164f34ebf0197a6d07a22ad3518374f5beb2a72ec61eb28f794562d8b9183                                                 27.0s
 => => resolve docker.io/library/golang:1.11-alpine@sha256:e14164f34ebf0197a6d07a22ad3518374f5beb2a72ec61eb28f794562d8b9183                                                  0.0s
 => => sha256:893f09c2afb0995b31b535c5ef1e3e6baf15d6e3ba20cca23ab228dc23959bba 156B / 156B                                                                                1.4s
 => => sha256:e14164f34ebf0197a6d07a22ad3518374f5beb2a72ec61eb28f794562d8b9183 1.65kB / 1.65kB                                                                               0.0s
 => => sha256:2edee773ecab4eebb906947fe54e6cf0a6129d0ccffdc8c2f7db7a011d6d47dc 1.36kB / 1.36kB                                                                               0.0s
 => => sha256:d9aba316547821e8316be967be44340469b40bd9b75cbfa32fa1e90187856188 3.81kB / 3.81kB                                                                               0.0s
 => => sha256:0503825856099e6adb39c8297af09547f69684b7016b7f3680ed801aa310baaa 2.79MB / 2.79MB                                                                               1.4s
 => => sha256:0bb4ee3360d7674b72befc5a29a65d17c2aad071dba363cedc48e21337e2f9fc 301.72kB / 301.72kB                                                                           1.6s
 => => extracting sha256:0503825856099e6adb39c8297af09547f69684b7016b7f3680ed801aa310baaa                                                                                0.8s
 => => sha256:c2e22f8e95fffa1ed4442d5409e8a22d90a3af80eefa1c34e3db6399a779501f 110.30MB / 110.30MB                                                                           9.0s
 => => sha256:e908c6b3f8b4a22a83fa4a674339b5bdb314a068d530ebe03a47704258c9f2e0 125B / 125B                                                                                1.9s
 => => extracting sha256:0bb4ee3360d7674b72befc5a29a65d17c2aad071dba363cedc48e21337e2f9fc                                                                                0.5s
 => => extracting sha256:893f09c2afb0995b31b535c5ef1e3e6baf15d6e3ba20cca23ab228dc23959bba                                                                                0.0s
 => => extracting sha256:c2e22f8e95fffa1ed4442d5409e8a22d90a3af80eefa1c34e3db6399a779501f                                                                                16.9s
 => => extracting sha256:e908c6b3f8b4a22a83fa4a674339b5bdb314a068d530ebe03a47704258c9f2e0                                                                                0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 1.71kB                                                                                0.0s
 => ERROR [2/3] ADD . .                                                                                0.6s
------
 > [2/3] ADD . .:
#7 0.336 container_linux.go:345: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:109: jailing process inside rootfs caused \\\"pivot_root invalid argument\\\"\""
------
executor failed running [copy --unpack /src-0 go/src/github.com/windmilleng/integration/oneup/]: exit code: 1
Error: exit status 1

If i run with this set to 0 it works:
machine:oneup <user>$ DOCKER_BUILDKIT=0 tilt docker -- build -t x .
Running Docker command as:
DOCKER_BUILDKIT=0 DOCKER_HOST=tcp://<IP_ADDRESS>:2376 DOCKER_CERT_PATH=/Users/<user>/.minikube/certs DOCKER_TLS_VERIFY=1 docker build -t x .
---
Sending build context to Docker daemon  5.632kB
Step 1/5 : FROM golang:1.11-alpine
1.11-alpine: Pulling from library/golang
050382585609: Already exists
0bb4ee3360d7: Already exists
893f09c2afb0: Already exists
c2e22f8e95ff: Already exists
e908c6b3f8b4: Already exists
Digest: sha256:e14164f34ebf0197a6d07a22ad3518374f5beb2a72ec61eb28f794562d8b9183
Status: Downloaded newer image for golang:1.11-alpine
 ---> d9aba3165478
Step 2/5 : WORKDIR /go/src/github.com/windmilleng/integration/oneup
 ---> Running in 4a42b36c776e
Removing intermediate container 4a42b36c776e
 ---> 0bc1a1f9fa19
Step 3/5 : ADD . .
 ---> f6223d806d91
Step 4/5 : RUN go install github.com/windmilleng/integration/oneup
 ---> Running in c589d614ed17
Removing intermediate container c589d614ed17
 ---> 61aa85cbeea3
Step 5/5 : ENTRYPOINT /go/bin/oneup
 ---> Running in 8065ec465340
Removing intermediate container 8065ec465340
 ---> 183fec10c7fa
Successfully built 183fec10c7fa
Successfully tagged x:latest

Running tilt up with this set to 0 also does the trick
machine:oneup <user>$ DOCKER_BUILDKIT=0 tilt up

aha! The env | grep DOCKER output was helpful, thank you.
Ya I can reproduce if I use minikube docker-env to configure the docker-env before Tilt starts. I think Tilt is getting confused, and thinks the DOCKER_HOST env variable trying to send it to some remote docker server outside minikube. This is a bug.


Apply growth rates to initial_value datasets

Description
This PR removes the ability to perform per-dataset aggregations
prior to combining datasets. That methodology did not work with growth
rate datasets. Secondly, while there are some efficiencies to be gained
with aggregating dimensions in that early stage, such as combining
electricity end uses, we expect that we will usually store cached
versions of project-mapped datasets. User queries will use those cached
datasets, and so this is not a significant loss in functionality.
The PR also fixes two issues in the current codebase that caused #180 and #181:

Fraction values were not being applied to datasets after dimension mapping. This resulted in duplicate combinations of dimension rows. This PR applies the fraction with groupBy/agg.
If a query filtered a dimension with specific records but a dataset includes dimension mappings that specify records in the to_id column that should be filtered out, those invalid records would show up in the final table. This PR fixes that by filtering the dimension mapping records.

This PR includes #182. That PR should be reviewed and merged first.
This is currently draft because of open questions regarding the data_source dimension.

Is the "filename too long" issue the same as https://stackoverflow.com/questions/22575662/filename-too-long-in-git-for-windows?

Is the "filename too long" issue the same as https://stackoverflow.com/questions/22575662/filename-too-long-in-git-for-windows?

Probably, and now I can't replicate the issue (to even confirm that the git config command fixes it), so let's assume that's not an issue.

@elainethale @lixiliu The model_year issue above happens because we removed the mappings in dsgrid_project/datasets/modeled/resstock/dimension_mappings/model_year_to_model_year.csv in this PR: https://github.com/dsgrid/dsgrid-project-StandardScenarios/pull/71/.
Either we restore those changes or figure out a different way to filter datasets. We don't need that mapping for any case other than this, I think. We removed it because we didn't think it was necessary. Any other thoughts?

@elainethale @lixiliu The model_year issue above happens because we removed the mappings in dsgrid_project/datasets/modeled/resstock/dimension_mappings/model_year_to_model_year.csv in this PR: dsgrid/dsgrid-project-StandardScenarios#71.
Either we restore those changes or figure out a different way to filter datasets. We don't need that mapping for any case other than this, I think. We removed it because we didn't think it was necessary. Any other thoughts?

Is filtering happening before or after applying the growth rate formula? It seems like filtering should work if it happens after the growth rate formula is applied?

@elainethale @lixiliu The model_year issue above happens because we removed the mappings in dsgrid_project/datasets/modeled/resstock/dimension_mappings/model_year_to_model_year.csv in this PR: dsgrid/dsgrid-project-StandardScenarios#71.
Either we restore those changes or figure out a different way to filter datasets. We don't need that mapping for any case other than this, I think. We removed it because we didn't think it was necessary. Any other thoughts?

Is filtering happening before or after applying the growth rate formula? It seems like filtering should work if it happens after the growth rate formula is applied?

We fully process the standalone dataset and growth rate set, including filter application, before applying the growth rate. I think that is what we want. If the user cares about a single county, as in this case, it's better to pre-filter the dataset because it saves a lot of work.
If we restore the mapping then the dataset itself will get exploded in a pointless way (40+ years of redundant data). This needs some more thought.

I was hoping that this query:
{
  "name": "Taos County Projections",
  "version": "0.1.0",
  "project": {
    "project_id": "dsgrid_conus_2022",
    "dataset": {
      "dataset_id": "taos_county_select_years",
      "source_datasets": [
        {
          "dataset_id": "tempo_conus_2022",
          "dataset_type": "standalone"
        },
        {
          "dataset_id": "comstock_projected_conus_2022",
          "initial_value_dataset_id": "comstock_conus_2022_reference",
          "growth_rate_dataset_id": "aeo2021_reference_commercial_energy_use_growth_factors",
          "construction_method": "formula123",
          "base_year": null,
          "dataset_type": "exponential_growth"
        },
        {
          "dataset_id": "resstock_projected_conus_2022",
          "initial_value_dataset_id": "resstock_conus_2022_reference",
          "growth_rate_dataset_id": "aeo2021_reference_residential_energy_use_growth_factors",
          "construction_method": "formula123",
          "base_year": null,
          "dataset_type": "exponential_growth"
        }
      ],
      "expression": "tempo_conus_2022 | comstock_projected_conus_2022 | resstock_projected_conus_2022",
      "params": {
        "dimension_filters": [
          {
            "dimension_type": "geography",
            "dimension_query_name": "county",
            "column": "id",
            "operator": "isin",
            "value": [
              "35055"
            ],
            "negate": false,
            "filter_type": "DimensionFilterColumnOperatorModel"
          }
        ],
        "table_format": "pivoted"
      }
    },
    "excluded_dataset_ids": [],
    "include_dsgrid_dataset_components": false,
    "version": null,
    "spark_conf_per_dataset": []
  },
  "result": {
    "supplemental_columns": [],
    "replace_ids_with_names": false,
    "aggregations": [
      {
        "aggregation_function": "sum",
        "dimensions": {
          "data_source": [],
          "geography": [
            {
              "dimension_query_name": "county",
              "function": null,
              "alias": null
            }
          ],
          "metric": [
            {
              "dimension_query_name": "electricity",
              "function": null,
              "alias": null
            }
          ],
          "model_year": [
            {
              "dimension_query_name": "model_year",
              "function": null,
              "alias": null
            }
          ],
          "scenario": [
            {
              "dimension_query_name": "scenario",
              "function": null,
              "alias": null
            }
          ],
          "sector": [
            {
              "dimension_query_name": "sector",
              "function": null,
              "alias": null
            }
          ],
          "subsector": [
            {
              "dimension_query_name": "all_subsectors",
              "function": null,
              "alias": null
            }
          ],
          "time": [
            {
              "dimension_query_name": "time_est",
              "function": null,
              "alias": null
            }
          ],
          "weather_year": [
            {
              "dimension_query_name": "weather_2012",
              "function": null,
              "alias": null
            }
          ]
        }
      }
    ],
    "reports": [],
    "output_format": "parquet",
    "sort_columns": [],
    "dimension_filters": [
      {
        "dimension_type": "model_year",
        "dimension_query_name": "model_year",
        "column": "id",
        "operator": "isin",
        "value": [
          "2020",
          "2025",
          "2030",
          "2035",
          "2040",
          "2045",
          "2050"
        ],
        "negate": false,
        "filter_type": "DimensionFilterColumnOperatorModel"
      }
    ],
    "time_zone": null
  }
}

would be a workaround to my filtering issue, but I got this error:
23/01/11 13:43:28 INFO DAGScheduler: Job 9 finished: collect at /home/ehale/dsgrid/dsgrid/utils/spark.py:272, took 0.094841 s
Traceback (most recent call last):
  File "/home/ehale/c-leap/dsgrid_taos_county_query.py", line 160, in <module>
    main(args.output_dir)
  File "/home/ehale/c-leap/dsgrid_taos_county_query.py", line 150, in main
    ProjectQuerySubmitter(project, output_dir).submit(
  File "/home/ehale/dsgrid/dsgrid/utils/timing.py", line 130, in timed_
    return _timed_func(collector, func, *args, **kwargs)
  File "/home/ehale/dsgrid/dsgrid/utils/timing.py", line 139, in _timed_func
    return func(*args, **kwargs)
  File "/home/ehale/dsgrid/dsgrid/query/query_submitter.py", line 255, in submit
    return self._run_query(
  File "/home/ehale/dsgrid/dsgrid/query/query_submitter.py", line 155, in _run_query
    df = self._apply_filters(df, context)
  File "/home/ehale/dsgrid/dsgrid/query/query_submitter.py", line 176, in _apply_filters
    raise Exception("Filtering result data is not supported yet")
Exception: Filtering result data is not supported yet


Feature: File input for models in TextrudeInteractive

Copying the file contents into the models tab is a bit clunky, would be cooler, if a file could be chosen directly.
This could look, for example, look like this:

Yes agreed! (see my slightly longer answer at https://github.com/NeilMacMullen/Textrude/discussions/7#discussioncomment-308693) but this actually the way one of the very early prototypes worked.  I found the UI got a little confusing since the input windows could now be...

text with no backing file
text loaded from a backing file but edited in the input window (no link back to the originating file except maybe for explicit save?)
text loaded from a 'live' linked file (text changes if user edits the original file).  What happens if the user edits the file in both places? Probably easiest to just disable editing in the edit window in this case.

Yes agreed! (see my slightly longer answer at https://github.com/NeilMacMullen/Textrude/discussions/7#discussioncomment-308693) but this actually the way one of the very early prototypes worked.  I found the UI got a little confusing since the input windows could now be...

text with no backing file
text loaded from a backing file but edited in the input window (no link back to the originating file except maybe for explicit save?)
text loaded from a 'live' linked file (text changes if user edits the original file).  What happens if the user edits the file in both places? Probably easiest to just disable editing in the edit window in this case.

Hm, good point. Maybe models could have two "modes":

Backed by a file and read-only
Free input

This would probably need some descriptive icons to distinguish the two easily.
Or the models are always backed by files and can be edited in TextrudeInter. and when external changes are detected, a reload or discard can be done (like Notepad++):

But I think the "2-mode" idea would be a bit more consistent for the user...

Hm, good point. Maybe models could have two "modes":

Backed by a file and read-only
Free input

This would probably need some descriptive icons to distinguish the two easily.
Or the models are always backed by files and can be edited in TextrudeInter. and when external changes are detected, a reload or discard can be done (like Notepad++):

But I think the "2-mode" idea would be a bit more consistent for the user...

Out of interest, is your main use-case

you have some existing files and just want to get them into the UI so you can start playing with a template?
you anticpate your model/template files to be under active development outside the tool and periodically want to reload them
you want to use an external editor to edit the models/template "live"

I'm sure you have already worked out that the "Project/save/load/export as invocation provides a (clunky) persistence mechanism while developing new templates?
Blocked by https://github.com/NeilMacMullen/Textrude/issues/10#issue-793532970

Out of interest, is your main use-case

you have some existing files and just want to get them into the UI so you can start playing with a template?
you anticpate your model/template files to be under active development outside the tool and periodically want to reload them
you want to use an external editor to edit the models/template "live"

I'm sure you have already worked out that the "Project/save/load/export as invocation provides a (clunky) persistence mechanism while developing new templates?
Blocked by https://github.com/NeilMacMullen/Textrude/issues/10#issue-793532970

My current use case is:

develop a template that uses a CSV file to generate some C# classes, which should be incorporated into a VS project
save the finished template in the solution and generate C# files in the Pre-Build step

The models will probably be static at 2., only at 1 they are dynamic, as I have to evaluate which pieces of info. needed to be passed on to the C# classes, so it works with the existing system.
I am also considering replacing some T4 templates, which generate C# files from YAML files, but this comes maybe later

My current use case is:

develop a template that uses a CSV file to generate some C# classes, which should be incorporated into a VS project
save the finished template in the solution and generate C# files in the Pre-Build step

The models will probably be static at 2., only at 1 they are dynamic, as I have to evaluate which pieces of info. needed to be passed on to the C# classes, so it works with the existing system.
I am also considering replacing some T4 templates, which generate C# files from YAML files, but this comes maybe later

Thanks.  I think the best workaround for now would to set up a project to hold the models and template during #1 then use the "export as invocation" step when you're ready to move onto #2.  I think the changes discussed here are a good idea but may take a while (I'm currently trying to flesh out some C# code templates in 'libs')

Thanks.  I think the best workaround for now would to set up a project to hold the models and template during #1 then use the "export as invocation" step when you're ready to move onto #2.  I think the changes discussed here are a good idea but may take a while (I'm currently trying to flesh out some C# code templates in 'libs')

Yeah, that works for me.
No sweat, the things I want to do, work, so no hurry :)

Yeah, that works for me.
No sweat, the things I want to do, work, so no hurry :)

Partially done - head of main includes a "Load" button on each model tab.  Similarly there is a "save" button on each output tab.  Not quite as good a live link but may be useful.

Partially done - head of main includes a "Load" button on each model tab.  Similarly there is a "save" button on each output tab.  Not quite as good a live link but may be useful.

Cool :) (and helps for existing data)
Thinking about, this would be (probably) enough, as this could get out of hand fast (as discussed).
If they are no other objections, I would close this issue.

Cool :) (and helps for existing data)
Thinking about, this would be (probably) enough, as this could get out of hand fast (as discussed).
If they are no other objections, I would close this issue.

If they are no other objections, I would close this issue.

Super - btw, just started looking at your monaco branch.  Are you still playing with it or are you happy for me to rip the code and integrate it?

If they are no other objections, I would close this issue.

Super - btw, just started looking at your monaco branch.  Are you still playing with it or are you happy for me to rip the code and integrate it?

For monaco: see #7, there could be some problems integrating it right now

For monaco: see #7, there could be some problems integrating it right now


README.md guess

a game in which the player must correctly guess the answer —often used metaphorically In such cases, making a diagnosis can be a real guessing game. As they wait for her final decision, reporters continue to speculate.

a game in which the player must correctly guess the answer —often used metaphorically In such cases, making a diagnosis can be a real guessing game. As they wait for her final decision, reporters continue to speculate.


mac-36 is dead.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
mac-36 is dead.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

mac-36 is up and running fine. Mac-36 is out of sync with Salt master. Run command "salt-call state.apply" to re-sync with Salt master again.
flutter-devicelab-mac-36:~ swarming$ uptime
15:56  up  6:49, 4 users, load averages: 0.96 0.91 0.94


User Experience Forecast Linear Weighted Analysis Issue

The numbers do not agree with the graphs.

I believe this has to do with the tile height and plotting of the data points. I did a few tests in my demo environment and created the graphs 30x7 and the single value tiles 8x7. The graphs scale much better with those settings. Can you edit your dashboard and try these settings? The only downside, depending on your screen zoom, you might need to scroll down to see the later weeks. My screen zoom is set to 67% and it shows most of the rows...

Let me know if resizing the tiles helps.

I'm afraid you're missing my point. My Satisfied User Counts should be greater than my Tolerated User Counts.

I see the issue now. I'll push a fix in a few minutes. Thanks for catching this...

Fixed. Relaunch the Configurator and try deploying again. Let me know if the counts are accurate...

That did the trick. Thanks.


change this to be "angular"

https://github.com/mse2321/muzak/blob/master/js/app.js#L63
Instead of using jQuery to get the value, give it ng-model or something.

Ok, this was an older app converted to angular. Looks like I need to convert more of it.

Done. I set up an ng-model


ComfyUI process is unexpectedly invoking launch_util

https://github.com/AUTOMATIC1111/stable-diffusion-webui/pull/11856
It appears to me that the subprocess the extension launched has invoked modules/launch_util.py and in turn activated a start timer. This looks unexpected. Is there any way to mitigate this?

This is caused by the new process importing webui modules to reuse code. As webui modules are imported in a new subprocess, modules that are already imported have to be redefined, since processes do not share memory contrary to threads.
We will fix it on our side, you can close the issue in auto's repo.

Thank you!


Faster histeq

Ref https://github.com/timholy/Images.jl/pull/523#issuecomment-235236460, CC @mronian.

Since I had this already I thought it would be best to just submit it. But a little bit of poking around suggests that histmatch may have the same performance problem, so a good exercise for you :smile: will be to check that it's indeed a problem and fix it.

Coverage increased (+0.02%) to 77.338% when pulling b3ea840ee5dd4be819269a8ea890da601ad63c5f on teh/faster_histeq into 4f0fc15609533c29d574f892a64ff88ecec5cb28 on master.

@timholy I tried the same with histmatch and adjust_gamma but there seems to be no increase in speed. ProfileVIew.view(C=true) does not have the internal C function calls or typemap at the top of the stack like in histeq. Still, should we avoid map just to be safe?

Turns out not only map but any type of [do this for i in I] type of statement causes speed issues. I changed -
table = [T((i / typemax(raw_type)) ^ gamma_inv) for i in zero(raw_type):typemax(raw_type)]

to -
table = zeros(Float64, typemax(raw_type) + 1)
    for i in zero(raw_type):typemax(raw_type)
        table[i + 1] = T((i / typemax(raw_type)) ^ gamma_inv)
    end

in adjust_gamma and the speed up is incredible.

Great, glad to hear it! (Or in a sense, sorry to hear it---would be nice if the original worked just as well. But worthwhile improvements for users.)


Worksheet.tables does not correctly work!

Seems to return javascript object with tablename as key. Not sure how to access


Expose Top or Take

Looking to select example: 4 items from my specification. I've resorted to using Query.Paginate(0, 4).
@ardalis suggested raising an Issue here to see if it might be a trivial item to implement.

Hey @ovation22 ,
If I understood correctly, you want to expose Take in the specification? You want to use Query.Take(4), instead of Query.Paginate(0, 4) ?
What would be the benefit actually? Not writing the 0?
Implementation wise, not hard to add. But, we have to ensure that Paginate() and Take() won't be used within the same specification, since it will overwrite the values. And that might add to the confusion.

It's a good point about the two being exclusive of one another. @ovation22 and I were discussing this Friday and my first thought was that it would be more intuitive to offer a .Take directly rather than having to "page" to do it. Conceptually to me at least, I don't think about paging as a way to get "Top X Rows/Records". Under the covers I know paging uses Skip/Take but it still seems like a bit of a hack to have to go through the Paging abstraction just to take advantage of this fact.
It shouldn't be too hard for us to support Take or Paginate, and throw if both are used, right?

Not a problem to implement. I was just thinking how to provide a consistent API. Not a huge fan of overlapping functionalities :)
If we think twice, Paginate is just a dummy wrapper and made sense in the legacy API, but now that we have LINQ alike structure, we may be more verbose and expose Top and Skip directly. For now we can support both ways, and decorate the Paginate as obsolete. In the future we'll remove it completely. Makes sense?
But, I have a feeling we misunderstood @ovation22. He might want to get top records regardless of the specification (for any spec). If this is a case, this can be done in your repository implementation.
We provide RepositoryBase generic repository ready to use. It's an abstract one, so anyway you will have to derive from it. You could do something like this in your repo.
public interface IRepository<T> : IRepositoryBase<T> where T : class
{
    Task<List<T>> GetTopAsync(ISpecification<T> specification, int take);
    Task<List<TResult>> GetTopAsync<TResult>(ISpecification<T, TResult> specification, int take);
}

public class Repository<T> : RepositoryBase<T>, IRepository<T> where T : class
{
    protected readonly TestDbContext dbContext;

    public Repository(TestDbContext dbContext) : base(dbContext)
    {
        this.dbContext = dbContext;
    }

    public async Task<List<T>> GetTopAsync(ISpecification<T> specification, int take)
    {
        return await ApplySpecification(specification).Take(take).ToListAsync();
    }

    public async Task<List<TResult>> GetTopAsync<TResult>(ISpecification<T, TResult> specification, int take)
    {
        return await ApplySpecification(specification).Take(take).ToListAsync();
    }
}

PS. I just noticed ApplySpecification is a private method. We'll make that protected, no harm of exposing it.

I was specifically referencing using Top/Take in a Specification, but I appreciate the option with the IRepository.
Giving it more thought over the weekend I was thinking along those lines same lines as you mention @fiseni if it would make sense to expose Take and Skip and deprecating Paginate. Makes sense to me.

One of the key benefits of the Specification pattern IMO is that it helps prevent the need for repository implementations to have tons of different methods. If we can avoid adding more methods to repository by allowing fewer methods to do the same thing using a specification, I think we should do that. I also don't want to require devs to have to use our base repository just because they want to use specifications (as that will hurt adoption).
So, I think your original idea works:

Not a problem to implement. I was just thinking how to provide a consistent API. Not a huge fan of overlapping functionalities :)
If we think twice, Paginate is just a dummy wrapper and made sense in the legacy API, but now that we have LINQ alike structure, we may be more verbose and expose Top and Skip directly. For now we can support both ways, and decorate the Paginate as obsolete. In the future we'll remove it completely. Makes sense?

I'm still not sure I want to drop Paginate, since I like the naming of it (it's a higher level abstraction that covers up the low level skip/take details) but I agree it's not great design to have 2 ways to do the same thing.

Giving it more thought over the weekend I was thinking along those lines same lines as you mention @fiseni if it would make sense to expose Take and Skip and deprecating Paginate. Makes sense to me.

Sounds like we all agree. Add Take/Skip to specification and mark Paginate obsolete.

I do share your opinion regarding the repositories. I didn't mean to provide the functionality through the repo, or enforce it in any way. It's just an example how users can implement such thing in their code base, in their repo (cos that's the only way you can get such general Top functionality).
I'm free for the next 30 mins, I'll do the changes now.

This is implemented. If no one has additional comments, we may close the issue.

Ok so all I need to do if it looks good is publish a new point release, yes?

Yes, I think so.
I don't think we have some breaking changes, but you might want to go through the history and cross check. There is a comment on the last commit too.
Other than that, tests should be refactored. It's in my backlog too, if I find time in the next period, I'll try to go through that.


SQLActionException[UnsupportedFeatureException: Cannot use table functions inside aggregates]

Use case:
When i query select count( distinct unnest("col"['id'])) FROM table where id = 8499;
got error SQLActionException[UnsupportedFeatureException: Cannot use table functions inside aggregates]
Feature description:

You've to rewrite the query slightly:
SELECT
    count(x)
FROM ( SELECT DISTINCT
        UNNEST(xs) AS x
    FROM
        t1
    WHERE
        id = 8499) tv;


Cleanup vendored

Been having issues with consul 1.9.6 being corrupted, updating should make that a non-issue.
Removed vendored vault-bin as the changes have been upstreamed
Bump nixpkgs

removed vault-bin commit because upstream needs to be fixed: https://github.com/NixOS/nixpkgs/pull/131883

closing, as these have been updated past 1.9.6


configure travis to publish artifacts to github

see https://docs.travis-ci.com/user/deployment/releases/

duplicate #9


bug in autosuggest text in multiline

git bisect points to 1a55699 as the culprit for this.  A minor display issue that I ran across in xonsh
I'm on xonsh master for both of these.
With prompt_toolkit 0.57 this is the autosuggest display:

After 1a55699 the autosuggest text is mirrored at the end of the first line:

Hi @gforsyth, Thank you for pointing out this bug. I'll fix it asap.
Jonathan

Hi @gforsyth, it should be fixed in https://github.com/jonathanslenders/python-prompt-toolkit/commit/c8ef2b9b3e19b10741a525e770f6562279234336
Could you try again. Thanks!

Hey @jonathanslenders, that did it!  Thanks!


Upgrading the UI of projects and the project box[cart] section

Hello @cleveranu ,
I think Project section needs to be update because the Search doesn't have any search button & the font is too big for the Title section.
Also the cart text is not well maintained.
Screenshot which I was talking about :

@cleveranu Please assign this issue to me. I am an experienced designer would definitely make the necessary changes and make it look more promising.

@cleveranu Please review this.


Building as docker image

Let me preface this by saying I understand that this isn't the intended usage of this tool but I don't understand why it doesn't work.
I created a Dockerfile below:
FROM ghcr.io/cargo-lambda/cargo-lambda:0.21.1 as rust-lambda-local

WORKDIR /usr/src/app
COPY . .

CMD ["cargo", "lambda", "watch", "-a", "<IP_ADDRESS>", "-p", "8080"]

I can't bind the internal port 8080 to any host machine port. Localhost 8080 is unresponsive:

Yet I can run other cargo lambda commands inside the running container:

Why do I want this? 2 reasons, I'd like to interact with the "API" endpoints through an nginx proxy to orchestrate other services and having them addressable by name instead of localhost:<port>. The second is to be able to containerize the running database.

docker run rust-lambda-local -p <IP_ADDRESS>:8080:8080/tcp

Yes, this is on Windows inside of WSL. I tried running curl inside of WSL and from Windows and neither responded.

I tried outside of docker compose:

Use this CMD:
CMD ["cargo", "lambda", "watch", "-a", "<IP_ADDRESS>", "-p", "8080"]

The address is local to the container, so if you use <IP_ADDRESS>, any external connection will be rejected.

Awesome! Thank you so much, this worked. Closing


Orchestration logic changes

The Orchestration service must be changed based on the following:

Use the new "Dataset" node.
Remove the "Data Ingestion" and "Data Loading" features from its graph logic.

The testing of the needed features is successful so this issue is getting closed.


Update README.md

Proposed change
Corrected spelling error on line #57 of README.md from [Notificaions] to [Notifications].
Type of change
Spelling error.

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests
[X] Documentation update
[ ] Adds a new shipper
[ ] Update existing shipper

Additional information
Corrected spelling error on line #57 of README.md from [Notificaions] to [Notifications].
(Please forgive my pedantic attention to detail -- I appreciate the hard work!)

Please target the dev branch, and thank you for your attention to detail.


Added a restart method for convenience

The restart function will allow lazy people like me to simple call stopwatch.restart() instead of manually calling the stop, restart start methods one by one, or recreating the object itself.

Coverage increased (+0.01%) to 94.54% when pulling d6f3109985eec112acb1584d3561c04ca9a76b9b on esend7881:master into ee19f8247c4bc0335ad3efe212dc0bdce97e2034 on apache:master.

Coverage increased (+0.01%) to 94.54% when pulling d6f3109985eec112acb1584d3561c04ca9a76b9b on esend7881:master into ee19f8247c4bc0335ad3efe212dc0bdce97e2034 on apache:master.

Hi @esend7881
thanks for the pull request.
I'm not sure it is a good idea to add at method that is nearly identical to StopWatch#createStarted.

@PascalSchumacher good point. I would say the main advantage is my method would not have the JVM re-create an object. So if you are restarting the timer over and over, it may be less costly. In the end, same outcome.


Can't load Who Reacted plug-in

When I try to install and enable the Who Reacted plug-in I get these errors

TypeError: this._dispatcher.createToken is not a function
at new E (https://discord.com/assets/35705.68d74baeb9f25c82c1d6.js:1:7474617)
at new DefaultSettingsStore (betterdiscord://plugins/WhoReacted.plugin.js:128:9)
at eval (betterdiscord://plugins/WhoReacted.plugin.js:165:23)
at eval (betterdiscord://plugins/WhoReacted.plugin.js:730:12)
at N.requireAddon (betterdiscord/renderer.js:5:28792)
at N.loadAddon (betterdiscord/renderer.js:5:6412)
at N.loadAddon (betterdiscord/renderer.js:5:26460)
at betterdiscord/renderer.js:5:4392

Same

I'm able to enable it now. User icons are still not showing

same

fixed plugin: https://gist.github.com/0xeac7/b44f7519c8edb4ba16942fcbdfae35ad

It's still doesn't

still broken, fix from @0xeac7 does not work unfortunately


[outdated] Offline radio stations

A few radio stations are offline, I suggest to remove them; reference

I will fix this in few hours.

Good :+1:

Shouldn't this be closed/

It'll be closed once it's up and running on our own servers.

It's now up and running on our servers, closed


.

https://github.com/DeBankDeFi/Issues

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀


[KYUUBI #4876] Fix flaky test BackendServiceMetricSuite

Why are the changes needed?

Close #4876
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Thanks for digging and fixing this flaky test. And it's more easily fail on JDK 17, which proves the JDK 17 is faster :)

@lightning-L please use script dev/merge_kyuubi_pr.py to merge PR, which reserves more information in git commit message, and simplifies the backporting process.

@lightning-L I suppose this PR should be cherry-picked to branch-1.7, and don't forget to update the milestone after PR is merged.

manually merged to branch-1.7: https://github.com/apache/kyuubi/pull/4926

sorry, will use the script next time...


Add an options parameter to all the methods that allow creation of an HTML document fragment

We are facing an issue where we cannot provide a DocumentFragment with the XML::ParseOptions::HUGE option because it doesn't take the options int like the regular Document class does. This adds an optional parameter for passing that down.
Let me know if there need to be extra tests to ensure this is working :-)

There are failing tests here related to the jruby implementation that will need to be addressed.
I would like test coverage for this, yes, to ensure we're exercising this code path. Not sure which parse option to test with; maybe NOENT or NOERROR would be good candidates?

Thanks for the prompt response @flavorjones! I ran the tests locally, but I guess it only runs the plain Ruby implementation. Was just writing the Ruby test now. I'll look at the Java tests too :)

So after looking at this a bit, it turns out that there's a difference in the behaviour of the Java and C implementations. When instantiating a XmlDocumentFragment, the C implementation yields the provided block with an argument of itself (see https://github.com/JackMc/nokogiri/blob/058f5700fbff4b264b4727da484bfc419db1eb32/ext/nokogiri/xml_document_fragment.c#L28), whereas the Java implementation does not. This is causing trouble when using MRI and
This is not documented or tested and is used internally in one place as far as we can tell (https://github.com/sparklemotion/nokogiri/commit/d18f1ac91f7d725ce58683b0dd845b33cb160ae8#diff-8b98857b6a2cb5117b8b1de836357ecdR59). I'd argue that it would be best to rewrite this one usage so the block parameter can be freed up for this purpose (bringing it in line with XmlDocument's functionality) and so we can bring the Java and C implementations to functional equivalence.
@flavorjones what do you think?

Actually, it looks like that previous use is only for Node, so it doesn't seem to be used anywhere.

Bump :) I've rebased upon master now so this should be easier to review

Bump :)

Sorry for the terrible response time on this. I'd like to get this into v1.9.0, and so I'm going to rebase these commits and submit a separate PR to make sure they pass CI. I'll continue any conversation that needs to happen here, but will link to the other branch for visibility.

Ok - so this changeset doesn't actually work in the JRuby implementation, and so it's not going to make it into v1.9.0.
It's also becoming apparent, as I added test coverage, that the JRuby implementation has some other pre-existing warts that I need to fix. Here's how I'd like to approach:

[net new behavior] have all XML::Document and HTML::Document underlying parse methods (e.g., #read_io, #read_memory) save the ParseOptions as a Document attribute, to make testing a bit easier
[partially implemented by this PR] have all XML::DocumentFragment and HTML::DocumentFragment parse methods take options and an options-configuration block
[fixes] ensure the JRuby impl matches the CRuby behaviors

I'm going to open a new issue, linking to this one, to track all the additional work. I'll make sure your commit appears in master so you get contributor credit.
Changing target milestone to v1.10.0

See #2399 for an updated version of this branch.

Will ship in v1.13.0 ... thanks for your patience!


Rcpt-Merge

Merged code with Rcpp stuff

Hi Anqi,
I've merged my rcpp stuff and we should use this as the base from now on.


Update monitor-security-operations.md

The last URL ("Check for identity, network, data risks") was wrong. It went to the same page you're on. It's supposed to go to the bottom page in this content set.

@EdPrice-MSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; verified. Thanks.


repository mdillonvv/postgis not found: does not exist or no pull access

I get this error message:
"repository appropriate/docker-postgis not found: does not exist or no pull access"
However I can pull other images just fine. Did the access rights to this repository change?

Problem was with different repository. This one works fine.


Does not work with Vuetify 2+

vue.js:634 [Vue warn]: Error in render: "TypeError: Cannot read property 'bar' of undefined"
found in

Found the solution in the link.
https://github.com/eolant/vuetify-toast-snackbar/issues/42

Found the solution in the link.
https://github.com/eolant/vuetify-toast-snackbar/issues/42


feat!: forward port to firebase-ios-sdk v7+ / firebase-android-sdk v26+

Description
This is a series of commits that build towards (and then mostly implement) a forward port to firebase-ios-sdk v7+ and firebase-android-sdk v26+
Each commit may be viewed in isolation, and in fact that is recommended.
Related Issues
Unsure if there are other issues to relate but:
#4013 - updating to SDK26 for firestore
#3969 - auth useEmulator discussion - it is gated on this but is trivial once the forward port is done
Checklist
This is my first Dart code, first Flutter code, and first FlutterFire PR
I did the same port for react-native-firebase though, so I'm new here but have been in the area a lot. Be gentle ;-)
I am not sure what should be done in the CHANGELOG or with regard to version numbers here.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
iOS minimum deployment target is moved to 10+
RemoteConfig debugMode no longer exists. minimumFetchTime / fetchTimeout replace it

[x] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[ ] No, this is not a breaking change.

@googlebot I signed it!

@Salakar  / @Ehesp this is ready for review, I believe iOS and Android are both working now, should clear the way for auth emulator as a quick followon
I understand there may be concurrent work with regards remote-config port, happy to coordinate on that though I was very very light with regards to my forward-port treatment of it here and kept the commits pretty granular so it should be easy to deal de-conflict / integrate

GitHub actions aren't wrapped in retry so the android gradle ones flake without recovering as they attempt to pull remote dependencies. Something like this would fix it though it will need to be flutter-ified https://github.com/invertase/react-native-firebase/pull/4084/commits/f1b9af98f26f6b1e7302035785fa2c3108497922
One of the storage tests flaked for ios, it's passed before during this PR development and passes locally so should be unrelated to the commit:

[firebase_storage_example]:   updateMetadata
[firebase_storage_example]:      ✔ updates metadata
[firebase_storage_example]:      ✘ errors if metadata update removes existing data
[firebase_storage_example]:        [E]: Expected: {'action': 'updateMetadata test'}
[firebase_storage_example]:               Actual: {'activity': 'test', 'action': 'updateMetadata test'}

If you retry both (I don't have permission) it should go green after one or two attempts, they work locally each time


Fail if date or git not installed

Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

Replaces https://github.com/projectatomic/buildah/pull/616

Should prevent https://github.com/projectatomic/buildah/issues/612 in the future.

Looks like the tests are breaking, on my vm I'm seeing:
make
go build -ldflags '-X main.gitCommit= aca2a1e -X main.buildInfo=1524575762' -o buildah -tags "   selinux seccomp" ./cmd/buildah
# github.com/projectatomic/buildah/cmd/buildah
usage: link [options] main.o
  -B note
    	add an ELF NT_GNU_BUILD_ID note when using ELF
{lots of info removed}
  -w	disable DWARF generation
make: *** [Makefile:20: buildah] Error 2

LGTM assuming happy tests.  My tests look happier to me.
# mv /bin/date /bin/nodate
# make
make: date: Command not found
Makefile:10: *** "date failed".  Stop.
# mv /bin/nodate /bin/date
# mv /usr/bin/git /usr/bin/nogit
# make
make: git: Command not found
Makefile:9: *** "git failed".  Stop.

# mv /usr/bin/nogit /usr/bin/git
# make
{happy make output removed}

@rh-atomic-bot r=TomSweeneyRedHat


UI improved

@vibgyor786  Have a look
I made changes such as in the nav bar now it is looking neater, the color scheme of the nav was changed and uniform color scheme was applied to the whole application and a uniform border scheme was also applied along with the uniform font.
Also, I made some small changes such as hover effects and container width so that it looks much better now.
I also made the required changes in the tic tac toe game that was available.
Resolves #7

Kindly add new features that reflects the essence of Games and Go, note that the initial design including fonts and buttons were added to reflect an old school 90s games theme for the end user. You may read Contributing.md and Readme.md before you make contributions. No doubt, you have done good work adding uniform components to the homepage however you must keep in mind the purpose and essence of a project before making contributions. So I highly recommend you to go with the initial design of the app and add more elements to it like footer and about section etc. you can also add animation to the games card or think of something out of the box to do with the project.

Kindly add new features that reflects the essence of Games and Go, note that the initial design including fonts and buttons were added to reflect an old school 90s games theme for the end user. You may read Contributing.md and Readme.md before you make contributions. No doubt, you have done good work adding uniform components to the homepage however you must keep in mind the purpose and essence of a project before making contributions. So I highly recommend you to go with the initial design of the app and add more elements to it like footer and about section etc. you can also add animation to the games card or think of something out of the box to do with the project.

@Shreyaar12 Got it!
Will try to give it an old school 90s design and would be adding footer and about section

@amitmishra11 The border doesn't match with the theme..
please add an image that doesn't have a watermark in it
Change the home button back to the original one
Center the Game on div in mobile view


remove robots.txt file

@n1tranquilla, do we want search engines indexing this site?

Recommend to squash on merge.


Include link to wiki in the second slo action

https://progress.opensuse.org/issues/119176#note-23

feels like you overlooked my question in https://github.com/openSUSE/backlogger/pull/52#pullrequestreview-2059759466 . can you answer that please?

So should the message now include the explanation and wiki link? Can you show an update on a example ticket or something?

I havent run it but the changes should just make the comment exactly as we agree This ticket was set to **{priority}** priority but was not updated [within the SLO period]({url}). The ticket will be set to the next lower priority **{priority}**


[ci:component:github.com/gardener/aws-lb-readvertiser:0.3.0->0.4.0]

Release Notes:
:warning: The AWS LB readvertiser has been completely refactored and does now no longer change the deployment manifest of the kube-apiserver. Instead, it changes the `default/kubernetes` endpoint and keeps it up-to-date. This requires users to deploy their kube-apiserver with `--endpoint-reconciler-type=none`. Moreover, the AWS LB readvertiser needs a kubeconfig having privileges to talk to the kube-apiserver. Please consider the latest example manifest for instructions how to deploy the AWS LB readvertiser.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


FEAT(forest): hyperparameter support for RF clf inference

Description
Add hyperparameters to Random Forest classification inference, corresponding oneDAL changes in https://github.com/oneapi-src/oneDAL/pull/2638

Add hyperparameters to forest.py & forest.cpp where supported by oneDAL
Add tests that set a range of possible values and run inference

Checklist to comply with before moving PR from draft:
PR completeness and readability

[x] I have reviewed my changes thoroughly before submitting this pull request.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have updated the documentation to reflect the changes or created a separate PR with update and provided its number in the description, if necessary.
[x] Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
[x] I have added a respective label(s) to PR if I have a permission for that.
[x] I have resolved any merge conflicts that might occur with the base branch.

Testing

[x] I have run it locally and tested the changes extensively.
[x] All CI jobs are green or I have provided justification why they aren't.
[x] I have extended testing suite if new functionality was introduced in this PR.

Performance
does not apply

/intelci: run

/intelci: run

CI with branch from oneDAL#2638
http://intel-ci.intel.com/eee09489-921d-f165-8b50-a4bf010d0e2e

/intelci: run

Updated run with changes from 2638 http://intel-ci.intel.com/eee0cbf3-f8dd-f171-9c4f-a4bf010d0e2e

Benchmarks: http://intel-ci.intel.com/eee0cf89-b051-f1ed-a729-a4bf010d0e2e

/intelci: run

Updated job with oneDAL + scikit-learn-intelex changes http://intel-ci.intel.com/eee23804-7d24-f117-86db-a4bf010d0e2e

Are hyperparameters just another name for performance tuning parameters?

@Vika-F are we able to finalize this one?

@Vika-F @ethanglaser @icfaust @avolkov-intel
Who is expected to be next assigned to this job done?

@ahuber21 please use PR template in your description for Check PR Checklist / Close all checkboxes before moving from draft (pull_request)
Please mark it ready for review, moving to draft now

/intelci: run

Intel CI successful except for an environment error and a timeout in unrelated test cases: http://intel-ci.intel.com/ef8c9e4c-c4c4-f1f1-8c83-a4bf010d0e2d

@Vika-F would be great if you could take another look. Two questions in particular

Does the code reflect the (updated) hyperparameters from https://github.com/oneapi-src/oneDAL/pull/2692
Do you agree with how I handle classification and regression separately (since the hyperparameters are only available in classification)

/intelci: run

Typing tools in Python and common IDEs have become very mature and are an immense help when debugging code. I strongly favor adding as much type information as possible. It is sometimes difficult in this project when objects and classes are coming from cython, but limited typing information is still better than none.
It is simply common and best practice nowadays and we have to start somewhere. Typing is never enforced in Python, so even if we receive input outside of the types, nothing bad happens (except maybe for undefined behavior, because our understanding of the code is wrong).
I would argue against static typing checks for now because I would expect it to be highly non-trivial for this particular repo. Moreover, we should probably first create all necessary type stubs so that we can actually use type hints consistently. If you look into my changes, I annotated the hyperparameters_backend dictionary as Dict[Tuple[str, str], Any], simply because the type of the *_hyperparameters() getters from backend isn't readily available.
For now all contributors should feel encouraged but not forced to use type hints. If you want to bring this discussion to a dedicated issue go for it :)

Thank you @Alexsandruss. It is updated

/intelci: run


Support for vue 3.0

Can vuex-class support vue 3,0?

With vue-class-component now supporting Vue 3 in an rc-1 release, it would be pretty great to have vuex-class supporting it as well.

I tried to use vuex-class in vue3.0, there seems to be no problem;

I've created a package to support vue3, I've used in vite project with vue-ts.
Install it
npm i s-vuex-class
This project fork from this package, just make it support vue3.

 Should I be using @watch, or something else?
Expected behavior:
When files are added for upload, I would expect for HELLO {{ canUpload }} to re-render and show "HELLO true," but it isn't. It stays on showing HELLO false
I apologize for my lack of knowledge, I'm new to vue + vuex + vuex-class decorators.
canUpload is a getter in my vuex store:
  get canUpload(): boolean {
    console.log('IN THE GETTER1')
    console.log('THE ANSWER IS! ', this._uploading !== null)
    return this._uploading !== null
  }

<template>
  HELLO {{ canUpload }} !!

    <q-file
      :model-value="files"
      @update:model-value="updateFiles"
      label="Pick files"
      outlined
      multiple
      :clearable="!isUploading"
      style="max-width: 400px"
    >
      <template v-slot:file="{ index, file }">
        <q-chip
          class="full-width q-my-xs"
          :removable="isUploading && uploadProgress[index].percent < 1"
          square
          @remove="cancelFileByIndex(index)"
        >
          <q-linear-progress
            class="absolute-full full-height"
            :value="uploadProgress[index].percent"
            :color="uploadProgress[index].color"
            track-color="grey-2"
          ></q-linear-progress>

          <q-avatar>
            <q-icon :name="uploadProgress[index].icon"></q-icon>
          </q-avatar>

            {{ file.name }}

          <q-tooltip>
            {{ file.name }}
          </q-tooltip>
        </q-chip>
      </template>

      <template
        v-slot:after
        v-if="canUpload"
      >
        <q-btn
          color="primary"
          dense
          icon="cloud_upload"
          round
          @click="upload"
          :disable="!canUpload"
          :loading="isUploading"
        ></q-btn>
      </template>
    </q-file>

</template>

@ktsn Any plans to update this library for Vue 3?

Agreed, but I'm not too familiar with the inner workings of this plugin and I see that Vue 3 doesn't have the global instance anymore, are there any technical difficulties?

Stumbled upon an example for Vue 3 here - https://davidjamesherzog.github.io/2020/12/30/vue-typescript-decorators/

Work dependency:
"vue-class-component": "^8.0.0-rc.1",
"vue-property-decorator": "^10.0.0-rc.3",
"vuex-class": "^0.3.2"

@sienrik15 could you confirm you're using vuex-class and not s-vuex-class? Looking at your dependencies, not sure how this would work: vue-class-component would work with Vue 3.x but vuex-class wouldn't.

I've created a package to support vue3, I've used in vite project with vue-ts. Install it npm i s-vuex-class This project fork from this package, just make it support vue3.

MasterShu, the npm package s-vuex-class points to https://github.com/MasterShu/vuex-class repository, which doesn't have the source code for the same version. Any chance you could publish it?
Also it seems to only work with vue-class-component but not vue-facing-decorator.

Any updates on this? Looks like Vue 2 -> 3 migration for projects using class components + decorators + vuex-class is almost solved, the last missing peace seems to be vuex-class.

vuex-class 可以支持 vue 3.0 吗？

Designed for vue 3, do the same work like vuex-class.
https://www.npmjs.com/package/vuex-facing-decorator

Can vuex-class support vue 3,0?

Designed for vue 3, do the same work like vuex-class.
https://www.npmjs.com/package/vuex-facing-decorator

Any updates on this? Looks like Vue 2 -> 3 migration for projects using class components + decorators + vuex-class is almost solved, the last missing peace seems to be vuex-class.

Designed for vue 3, do the same work like vuex-class.
https://www.npmjs.com/package/vuex-facing-decorator

Work dependency: "vue-class-component": "^8.0.0-rc.1", "vue-property-decorator": "^10.0.0-rc.3", "vuex-class": "^0.3.2"

Designed for vue 3, do the same work like vuex-class.
https://www.npmjs.com/package/vuex-facing-decorator

Work dependency: "vue-class-component": "^8.0.0-rc.1", "vue-property-decorator": "^10.0.0-rc.3", "vuex-class": "^0.3.2"

Designed for vue 3, do the same work like vuex-class. https://www.npmjs.com/package/vuex-facing-decorator

Thanks a lot! It works like a charm.


Rgba2gray fixes

These are two improvements to the "rgba2gray" example.
Loading an image larger than 1024x1024 causes a panic. The problem lies in this line:
Block::xy((w - 1) / GRID_SIZE + 1, (h - 1) / GRID_SIZE + 1))?;

The CUDA documentation states "On current GPUs, a thread block may contain up to 1024 threads". With large images, this code would try to create more than that. I fixed this by using a variable grid size and a constant block size, instead of the other way around.
The other improvement is supporting the loading of images without an alpha channel.

Thanks, @Seeker14491.


Divider: Expect to provide a default padding value for slot content

About styles 🛠
I wish the following two usage can give consistent effects,
However, the second one appears not provide a padding value for hello.
  <var-divider description='hello' />
  <var-divider>hello</var-divider>

more details:
playground

Default slots for more freedom of customization, So we should not add default padding to users using the slots


build pahole from source

To avoid a bug with Ubuntu's pahole, and to allow us to use newer flags.

FYI I'm not able to test this Action myself, but it should work. If you have a way to test this change before merge, then please do.

I have reverted this one as it did not work. Will get something else similar to this to have latest pahole always built.


Tray bar icon

Hi,
when a new message arrives, the icon in tray bar changes in a gear and it remain in this state also when the message is been read.
I use v1.5.2 and debian testing with lxqt

This is a problem with electron
bug submitted: https://github.com/electron/electron/issues/15124


add prepack to copy admin-web to cli/dist

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

This PR will add prepack script to cli and when we publish cli admin-web will be included.

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Looks good!
The CI failure seems related to your changes, though 🤔 . Unsure if that's because ./scripts/../../admin-web/dist is the wrong path, or if admin-web/dist doesn't exist yet 🤔

Looks good!
The CI failure seems related to your changes, though 🤔 . Unsure if that's because ./scripts/../../admin-web/dist is the wrong path, or if admin-web/dist doesn't exist yet 🤔

yarn build will generate dist folder. I thought before prepack we would have yarn build called! will look into!


How could I export texture_UV maps from the saved .obj files from existing Image-to-3D methods?

I have tried to run a couple of Image-to-3D methods, including Wonder3D, TripoSR, SV3D, etc.
The output of these methods is all single .obj file without .mtl and textured_UV maps.
I am writing to seek for advice about how to export these files together with the .obj file.
I see that there are mesh extracting codes in the main repo of threestudio, but I guess it can't be applied to independent official repos of other projects.
Looking for comments and suggestions. Thank you!

well you sure that with the current code base of st-ai, you are able to generate .obj files from SV3D? btw even for .obj textures can be incorporated, it's just a matter of implementation.


Fixed broken link in README.md

What Changed
Updated the link for graph quilt gateway.
Why
Existing link was dead
Todo:

[X] Add tests
[X] Add docs

Thank you for your contribution. Could you also bless us with a ⭐


Custom operator support for conversion from MXNet to PyTorch

Platform: ubuntu 16.04:
Python version: 3.6
Source framework with version:  mxnet-cu92mkl 1.2.0
Destination framework with version: pytorch-0.4 with GPU
Running scripts:
SYM=mxnet/Deformable-ConvNets/rfcn/resnet_v1_101_rfcn_dcn.json
PARAMS=mxnet/Deformable-ConvNets/params/rfcn_dcn_coco-0000.params

mmconvert -sf mxnet -in $SYM -iw $PARAMS --dstNodeName MMdnn_Output -df pytorch -om res101_rfcn_dcn_coco.pth --inputShape 3 224 224

Error:
Traceback (most recent call last):
  File "/home/ml/farleylai/anaconda3/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/ml/farleylai/anaconda3/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/ml/farleylai/anaconda3/lib/python3.6/site-packages/mmdnn/conversion/_script/convertToIR.py", line 189, in <module>
    _main()
  File "/home/ml/farleylai/anaconda3/lib/python3.6/site-packages/mmdnn/conversion/_script/convertToIR.py", line 184, in _main
    ret = _convert(args)
  File "/home/ml/farleylai/anaconda3/lib/python3.6/site-packages/mmdnn/conversion/_script/convertToIR.py", line 68, in _convert
    parser = MXNetParser(model)
  File "/home/ml/farleylai/anaconda3/lib/python3.6/site-packages/mmdnn/conversion/mxnet/mxnet_parser.py", line 239, in __init__
    self.model, self.weight_data = MXNetParser._load_model(input_arg[1], input_arg[2])
  File "/home/ml/farleylai/anaconda3/lib/python3.6/site-packages/mmdnn/conversion/mxnet/mxnet_parser.py", line 172, in _load_model
    sym, arg_params, aux_params = mx.model.load_checkpoint(weights, int(epoch))
  File "/home/ml/farleylai/anaconda3/lib/python3.6/site-packages/mxnet/model.py", line 419, in load_checkpoint
    symbol = sym.load('%s-symbol.json' % prefix)
  File "/home/ml/farleylai/anaconda3/lib/python3.6/site-packages/mxnet/symbol/symbol.py", line 2535, in load
    check_call(_LIB.MXSymbolCreateFromFile(c_str(fname), ctypes.byref(handle)))
  File "/home/ml/farleylai/anaconda3/lib/python3.6/site-packages/mxnet/base.py", line 149, in check_call
    raise MXNetError(py_str(_LIB.MXGetLastError()))
mxnet.base.MXNetError: [00:13:37] src/operator/custom/custom.cc:104: Check failed: CustomOperator::Get()->Find(params.op_type) != nullptr Cannot find custom operator proposal

The pre-trained model is downloaded from the Deformable-ConvNets which contains a custom operator 'proposal.'
The custom operator is a python module in the source tree.
Is there any way to instruct MMdnn to import the custom operator?
Or the custom operator for conversion from MXNet is not suppored yet?

Hi @farleylai ,Could you provide your model file(.json and .params) for us to test?

Sure, the network symbol is generated by calling tojson() as attached FYI.
The network source is located at resnet_v1_101_rfcn_dcn.py.
resnet_v1_101_rfcn_dcn.json.zip
The params is quite large (~254MB) but I believe you can download from the official site (stored on OneDrive with file named rfcn_dcn_coco-0000.params).
The CustomOp proposal source is available in Python or by calling C++ contrib APIs.
Let me know if you need something else.

Hi @farleylai . In current MMdnn, custom operator is not supported yet. Thanks.

Hi @farleylai . In current MMdnn, custom operator is not supported yet. Thanks.

Hi，@farleylai
https://github.com/Microsoft/MMdnn/wiki/Contribution-Guideline，The above link provide the method to add customized op, but you say “custom operator is not supported yet”，I‘m confused, can you confirm that, thinks.

Hi @farleylai . In current MMdnn, custom operator is not supported yet. Thanks.

Hi，@kitstar
https://github.com/Microsoft/MMdnn/wiki/Contribution-Guideline，The above link provide the method to add customized op, but you say “custom operator is not supported yet”，I‘m confused, can you confirm that, thinks.


Chat smart contract

This is a PoC implementation of a simple Chat smart contract, optimizing on lines of code. Every Chat post is an NFT and some of the functionality is delegated to the app-layer (i.e., one can reference another object, but what this reference means (reply, retweet, like, attachment etc) is encoded, by convention, inside metadata. The plan is to eventually augment the PoC to support most if not all of the features of a Twitter, Chat, Blog, and other social network engine on top of Sui via a single smart contract.

@sblackshear gave me no option, pushing hard on having separate functions for post and post with reference. Back to you.


clicking on Navigator causes Viewport to zoom

If my image is zoomed to the point where it fills the viewport, clicking on the Navigator works as expected.
However, if I have zoomed out so that the images is less than the viewport, clicking on the Navigator causes the viewport to zoom from its current size to almost filling the Viewport at the end of the animation.
For example, my current zoom is 0.24665939374432364
When I click on the Navigator I first get an "animate-start" event followed by an "animation" event
On each "animation" event I call getZoom(true) and getZoom(false)
On the first "animation" event, the current zoom is 0.24665939374432364 and the target zoom is 0.24665939374432364
(all good so far)
Then I get a "zoom" event with "immediately" undefined and a value of 0.730681067165689
A series of "animation" events follow, the current and target zooms are as follows:
0.356769535723414        0.730681067165689
0.43277752052818863      0.730681067165689
0.49557292724960134      0.730681067165689
0.5758611692829617       0.730681067165689
0.6174957282360439       0.730681067165689
0.6670779609377104       0.730681067165689
0.6994278251095688       0.730681067165689
0.7194902451789433       0.730681067165689
0.730681067165689        0.730681067165689

Of course, I don't expect any zooming to occur.

How are you telling the viewer that it's okay to zoom out that much?  If you haven't loosened the constraints on zooming and you programmatically zoom outside of those constraints, then when you interact with the navigator, it will force you back inside the constraints.
I tested by including minZoomImageRatio: 0 in my viewer options, and I'm not getting any unwanted zooming.

Yes, I was zooming programmatically so I went beyond the limits. I have added limit checking and all is well now

Great, good to know!


Code formatting

Upload _clang-format or atleast rules to configure formatting tools

I am using the following, but for some reason it doesn't work on pipes:
# Align pipes
BreakBeforeBinaryOperators: All
AlignConsecutiveAssignments: true
AlignOperands: true