Enhancement: Provide docker multiarch images

Currently, images on the Docker Hub are only published for the linux/amd64 architecture.
Due to the increasing popularity of ARM for both local development and cloud instances, it would be beneficial to have support for linux/arm64 as well.
While it is relatively easy to accomplish this using buildx, I believe the images are automatically published on Docker Hub through some integration that occurs outside of GitHub actions.

I don't think there is a real demand for that.
It is not done even in much larger and more popular packages like PyTorch
https://hub.docker.com/r/pytorch/pytorch/tags?page=2&page_size=&ordering=&name=

@mrT23 they are providing arm64 images on ghcr.io, as you can see here:

Action: https://github.com/pytorch/pytorch/blob/a34320a6f225061a3b5fe130a5a8fe35ed7a40f9/.github/workflows/docker-release.yml#L91
Image: https://github.com/orgs/pytorch/packages/container/pytorch/248296974?tag=2.4.0-runtime
Merged MR: https://github.com/pytorch/pytorch/pull/83437

I don't know why they chose to support ghcr.io but anyway, they are providing them.

I don't think it's needed. we already have many platforms and dockers. I won't double it by two without a real strong demand.

I don't know what you mean by "platforms and dockers." the docker image published is just linux/amd64 building it even for linux/arm64 I guess it's more or less a flag to add to the docker build process.

Just tested again to natively build on arm64 from an apple silicon machine:
> docker build -t test/pr-agent -f docker/Dockerfile .
[+] Building 82.2s (11/11) FINISHED                                                                                docker:desktop-linux
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 1.25kB                                                                                0.0s
 => [internal] load metadata for docker.io/library/python:3.12.3                                                                                1.8s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 147B                                                                                0.0s
 => [base 1/5] FROM docker.io/library/python:3.12.3@sha256:3966b81808d864099f802080d897cef36c01550472ab3955fdd716d1c665acd6                               25.9s
 => => resolve docker.io/library/python:3.12.3@sha256:3966b81808d864099f802080d897cef36c01550472ab3955fdd716d1c665acd6                                     0.0s
 => => sha256:db4833383c5df58967f7f7012b21834b5477b4a20e092b93dc89d4bc5726a3b9 2.77MB / 2.77MB                                                             0.5s
 => => sha256:94c9c1a110e2aec14c4da4be6e41c22baa463c9db548884e75ac02e97c1bbf41 243B / 243B                                                                 0.5s
 => => sha256:9256ecbd254ade127592159086931931bdcdb7ba0580d5533d02852d00fc34d7 22.21MB / 22.21MB                                                           4.1s
 => => sha256:228270bb5dc5207f6bbf31f0728807c55124238c0b5e44dc35eafcc56e166acb 6.47MB / 6.47MB                                                             2.1s
 => => sha256:30ed4c12791345d3f20f66024e1f22275ce507868c508509b83dcf231b1c9adc 63.99MB / 63.99MB                                                          14.6s
 => => sha256:feb30c5ba2d151512d29ff4b92109a740559509ef6f3072a86c5006a1379397b 202.59MB / 202.59MB                                                        22.7s
 => => sha256:15856ca26414127b85cee6d10acbc4cee6eba9070f3f5a04b9cc72ce95abfa7f 23.59MB / 23.59MB                                                           6.0s
 => => sha256:91e301773f03e9e0fabc5c177fe6bfe8daf14e992ab816f151692b814ddc462c 49.61MB / 49.61MB                                                           9.8s
 => => extracting sha256:91e301773f03e9e0fabc5c177fe6bfe8daf14e992ab816f151692b814ddc462c                                                                  0.6s
 => => extracting sha256:15856ca26414127b85cee6d10acbc4cee6eba9070f3f5a04b9cc72ce95abfa7f                                                                  0.2s
 => => extracting sha256:30ed4c12791345d3f20f66024e1f22275ce507868c508509b83dcf231b1c9adc                                                                  0.7s
 => => extracting sha256:feb30c5ba2d151512d29ff4b92109a740559509ef6f3072a86c5006a1379397b                                                                  2.3s
 => => extracting sha256:228270bb5dc5207f6bbf31f0728807c55124238c0b5e44dc35eafcc56e166acb                                                                  0.1s
 => => extracting sha256:9256ecbd254ade127592159086931931bdcdb7ba0580d5533d02852d00fc34d7                                                                  0.2s
 => => extracting sha256:94c9c1a110e2aec14c4da4be6e41c22baa463c9db548884e75ac02e97c1bbf41                                                                  0.0s
 => => extracting sha256:db4833383c5df58967f7f7012b21834b5477b4a20e092b93dc89d4bc5726a3b9                                                                  0.1s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 665.84kB                                                                                0.0s
 => [base 2/5] WORKDIR /app                                                                                0.2s
 => [base 3/5] ADD pyproject.toml .                                                                                0.0s
 => [base 4/5] ADD requirements.txt .                                                                                0.0s
 => [base 5/5] RUN pip install . && rm pyproject.toml requirements.txt                                                                                42.0s
 => [cli 1/1] ADD pr_agent pr_agent                                                                                0.1s
 => exporting to image                                                                                12.1s
 => => exporting layers                                                                                10.0s
 => => exporting manifest sha256:4796240a6bb66bbe159977c46cc3079ab9b4f508a04fc586d2e709584a6890c3                                                          0.0s
 => => exporting config sha256:a2c64bd6d60a580e1a44e32fb2234640385f8df59471ecaa800269cb1d2dfb72                                                            0.0s
 => => exporting attestation manifest sha256:6c5567cf9835f10fb68e03db1b1de02edd42c6ae4998d42c63001f503cfa4354                                              0.0s
 => => exporting manifest list sha256:f90964ee842ab9b75d84dfe1f76e13c06b0c4f38303c11d807c337d86149f54b                                                     0.0s
 => => naming to docker.io/test/pr-agent:latest                                                                                0.0s
 => => unpacking to docker.io/test/pr-agent:latest                                                                                2.0s

> docker run --rm -it --entrypoint "bash" test/pr-agent -c "arch"
aarch64

> docker run --rm -it test/pr-agent
usage:     Usage: cli.py --pr-url=<URL on supported git hosting service> <command> [<args>].
    For example:
    - cli.py --pr_url=... review
    - cli.py --pr_url=... describe
    - cli.py --pr_url=... improve
    - cli.py --pr_url=... ask "write me a poem about this PR"
    - cli.py --pr_url=... reflect
    - cli.py --issue_url=... similar_issue
 [cut]


Amazon SQS Endpoints do not support amazonsqs protocol identifier.  https is required

It would be helpful is the AmazonSqsScheme was a variable instead of hardcoded.  Amazon SQS endpoints only support the https protocol identifier.
namespace MassTransit.AmazonSqsTransport
{
using System;
using System.Diagnostics;
using Util;
[DebuggerDisplay("{" + nameof(DebuggerDisplay) + "}")]
public readonly struct AmazonSqsHostAddress
{
    public const string AmazonSqsScheme = "amazonsqs";

    public readonly string Scheme;
    public readonly string Host;
    public readonly string Scope;

    public AmazonSqsHostAddress(Uri address)
    {
        Scheme = default;
        Host = default;
        Scope = default;

        var scheme = address.Scheme.ToLowerInvariant();
        switch (scheme)
        {
            case AmazonSqsScheme:
                Scheme = address.Scheme;
                Host = address.Host;

                ParseLeft(address, out Scheme, out Host, out Scope);
                break;

The URL used by MassTransit have nothing to do with what's used by Amazon. It's how MassTransit identifies the transport.

Is there a directive or configuration item that forces SSL with SQS.   The current protocol identifier amazonsqs:// is not supported when using Amazon SQS Endpoints.  Does the h.UseSsl switch work with Rabbit MQ and SQS? Any help to force https:// would be helpful
Thank you very much for responding.

SQS requires SSL, there isn't an alternative.

Our SQS implementation is working if the queues are accessed via public connectivity. When we switch to a SQS endpoint, the connectivity fails. The Endpoints work via the AWS CLI on our server.  I am not trying to be a pain, we may need to wireshark the communication to see the actual packets.  Thanks for responding.
Below is the conversation I had with Amazon support:
On the chat, it was informed that EC2 instance is able to access SQS queue via internet however, when internet gateway is removed instance is not able to access the queue via SQS VPC endpoint. I reviewed SQS VPC endpoint, EC2 instance network  configurations and informed that Security group as well as subnet ACLs allow the traffic in either ways (EC2 instance --> SQS VPC endpoint and SQS VPC endpoint --> EC2 instance).  Further, I see that private DNS is also enabled for SQS VPC endpoint. When inquired why the ping requests to SQS VPC endpoint from EC2 instance timed out, I mentioned that SQS servers may or may not respond to ping requests.
As mentioned on the chat, please specify the endpoint "https://sqs..amazonaws.com/"  you are connecting to during client creation, since Private DNS doesn't support legacy endpoints such as queue.amazonaws.com or .queue.amazonaws.com. Please review the following documentations [1], [2], [3] on how to connect to SQS queue from Amazon Virtual Private Cloud, specify endpoints in .net SDK
Additionally, as mentioned on the chat if possible kindly configure AWS CLI on the EC2 instance with an IAM identity that has permissions to SQS queue and send message to SQS queue as below, in order to isolate the issue.
    aws sqs send-message --region <region> --endpoint-url https://sqs.<region>.amazonaws.com/ --queue-url <URLoftheSQSQueue> --message-body "Hello from Amazon SQS."

MassTransit uses the Amazon SQS .NET client library, which doesn't even let you configure the URL. You only pass the region:
new AmazonSQSConfig {RegionEndpoint = regionEndpoint ?? RegionEndpoint.USEast1};

That library only uses the modern SDK URL's so there isn't anything MassTransit is doing incorrectly.

I did find the issue causing this problem. I did not realize Masstransit uses SQQ and SNS services. If you are using an Amazon endpoint to keep traffic local to a VPC,  you must create an endpoint for SQS and SNS services.  My issue was a missing SNS endpoint.

Thanks for reporting back your findings!

I'm looking for info on how to use MassTransit with SNS / SQS under a private VPC. I didn't quite understand your issue @grateitservices
Can I ask how did you achieve that?
I had a look at https://docs.aws.amazon.com/sns/latest/dg/sns-vpc-tutorial.html which states that an AWS PrivateLink must exist between the private VPC (e.g: I publish messages from apps running in ECS Fargate cluster) and the SNS.
The problem is that I rely on MassTransit to create SNS topics, SQS queues and subscriptions. In other words, I don't have anything in my AWS cloud formation scripts that creates topics/queues/subscriptions.
Is there any way with MassTransti to have continue relying on it for topology creation but doing so in the private VPC so that the traffic is more secure?
I don't seem to find info on this.

@diegosasw To keep local SQS/SNS traffic local to a VPC, you need to setup Endpoints ((SQS Endpoint Instance and SNS Endpoint Instance)for both SQS and SNS.  The Masstransit configuration still only requires the region. MassTransit builds the URL from that information. Private Link is not required.
https://docs.aws.amazon.com/general/latest/gr/sqs-service.html
https://docs.aws.amazon.com/general/latest/gr/sns.html


Segmentation fault superagi-gui

I just pulled the project like an hour ago and been trying to solve the issues that have been showing up.
First this user I had this user error
 /usr/local/lib/python3.9/site-packages/celery/platforms.py:840: SecurityWarning: You're running the worker with superuser privileges: this is
superagi-celery-1           | absolutely not recommended!
superagi-celery-1           |
superagi-celery-1           | Please specify a different user using the --uid option.

which was fixed by adding this lines to DockerfileCelery
RUN groupadd -g 999 nonrootgroup
RUN useradd -u 501 -g 999 -M nonrootuser
USER nonrootuser

This is the complete log after executing docker-compose up --build
2023-06-06 02:20:01 superagi-super__redis-1     | 1:C 06 Jun 2023 06:20:01.360 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2023-06-06 02:20:01 superagi-super__redis-1     | 1:C 06 Jun 2023 06:20:01.360 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
2023-06-06 02:20:01 superagi-super__redis-1     | 1:C 06 Jun 2023 06:20:01.360 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
2023-06-06 02:20:01 superagi-super__redis-1     | 1:M 06 Jun 2023 06:20:01.365 * monotonic clock: POSIX clock_gettime
2023-06-06 02:20:01 superagi-super__redis-1     | 1:M 06 Jun 2023 06:20:01.367 * Running mode=standalone, port=6379.
2023-06-06 02:20:01 superagi-super__redis-1     | 1:M 06 Jun 2023 06:20:01.369 # Server initialized
2023-06-06 02:20:01 superagi-super__redis-1     | 1:M 06 Jun 2023 06:20:01.371 * Ready to accept connections
2023-06-06 02:20:01 superagi-super__postgres-1  |
2023-06-06 02:20:01 superagi-super__postgres-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-06-06 02:20:01 superagi-super__postgres-1  |
2023-06-06 02:20:01 superagi-super__postgres-1  | 2023-06-06 06:20:01.636 UTC [1] LOG:  starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-06-06 02:20:01 superagi-super__postgres-1  | 2023-06-06 06:20:01.637 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-06-06 02:20:01 superagi-super__postgres-1  | 2023-06-06 06:20:01.637 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-06-06 02:20:01 superagi-super__postgres-1  | 2023-06-06 06:20:01.649 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-06-06 02:20:01 superagi-super__postgres-1  | 2023-06-06 06:20:01.673 UTC [29] LOG:  database system was shut down at 2023-06-06 06:19:41 UTC
2023-06-06 02:20:01 superagi-super__postgres-1  | 2023-06-06 06:20:01.693 UTC [1] LOG:  database system is ready to accept connections
2023-06-06 02:20:03 superagi-celery-1           | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main
2023-06-06 02:20:06 superagi-celery-1           |
2023-06-06 02:20:06 superagi-celery-1           |  -------------- celery@e67c16ab4adb v5.2.7 (dawn-chorus)
2023-06-06 02:20:06 superagi-celery-1           | --- ***** -----
2023-06-06 02:20:06 superagi-celery-1           | -- ******* ---- Linux-5.15.49-linuxkit-x86_64-with-glibc2.31 2023-06-06 06:20:06
2023-06-06 02:20:06 superagi-celery-1           | - *** --- * ---
2023-06-06 02:20:06 superagi-celery-1           | - ** ---------- [config]
2023-06-06 02:20:06 superagi-celery-1           | - ** ---------- .> app:         superagi:0x7f7e27eafee0
2023-06-06 02:20:06 superagi-celery-1           | - ** ---------- .> transport:   redis://super__redis:6379/0
2023-06-06 02:20:06 superagi-celery-1           | - ** ---------- .> results:     redis://super__redis:6379/0
2023-06-06 02:20:06 superagi-celery-1           | - *** --- * --- .> concurrency: 10 (prefork)
2023-06-06 02:20:06 superagi-celery-1           | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
2023-06-06 02:20:06 superagi-celery-1           | --- ***** -----
2023-06-06 02:20:06 superagi-celery-1           |  -------------- [queues]
2023-06-06 02:20:06 superagi-celery-1           |                 .> celery           exchange=celery(direct) key=celery
2023-06-06 02:20:06 superagi-celery-1           |
2023-06-06 02:20:06 superagi-celery-1           |
2023-06-06 02:20:06 superagi-celery-1           | [tasks]
2023-06-06 02:20:06 superagi-celery-1           |   . execute_agent
2023-06-06 02:20:06 superagi-celery-1           |
2023-06-06 02:20:07 superagi-celery-1           | [2023-06-06 06:20:07,522: INFO/MainProcess] Connected to redis://super__redis:6379/0
2023-06-06 02:20:07 superagi-celery-1           | [2023-06-06 06:20:07,533: INFO/MainProcess] mingle: searching for neighbors
2023-06-06 02:20:08 superagi-celery-1           | [2023-06-06 06:20:08,551: INFO/MainProcess] mingle: all alone
2023-06-06 02:20:08 superagi-celery-1           | [2023-06-06 06:20:08,570: INFO/MainProcess] celery@e67c16ab4adb ready.
2023-06-06 02:20:02 superagi-gui-1              |
2023-06-06 02:20:02 superagi-gui-1              | ><EMAIL_ADDRESS>dev
2023-06-06 02:20:02 superagi-gui-1              | > next dev
2023-06-06 02:20:02 superagi-gui-1              |
2023-06-06 02:20:03 superagi-gui-1              | - ready started server on <IP_ADDRESS>:3000, url: http://localhost:3000
2023-06-06 02:20:03 superagi-gui-1              | - warn Invalid next.config.js options detected:
2023-06-06 02:20:03 superagi-gui-1              | - warn     The root value has an unexpected property, webpackDevMiddleware, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, configOrigin, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, modularizeImports, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, skipMiddlewareUrlNormalize, skipTrailingSlashRedirect, staticPageGenerationTimeout, swcMinify, target, trailingSlash, transpilePackages, typescript, useFileSystemPublicRoutes, webpack).
2023-06-06 02:20:03 superagi-gui-1              | - warn See more info here: https://nextjs.org/docs/messages/invalid-next-config
2023-06-06 02:20:04 superagi-gui-1              | Attention: Next.js now collects completely anonymous telemetry regarding usage.
2023-06-06 02:20:04 superagi-gui-1              | This information is used to shape Next.js' roadmap and prioritize features.
2023-06-06 02:20:04 superagi-gui-1              | You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
2023-06-06 02:20:04 superagi-gui-1              | https://nextjs.org/telemetry
2023-06-06 02:20:04 superagi-gui-1              |
2023-06-06 02:20:02 superagi-backend-1          | wait-for-it.sh: waiting 60 seconds for super__postgres:5432
2023-06-06 02:20:02 superagi-backend-1          | wait-for-it.sh: super__postgres:5432 is available after 0 seconds
2023-06-06 02:20:03 superagi-backend-1          | INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
2023-06-06 02:20:03 superagi-backend-1          | INFO  [alembic.runtime.migration] Will assume transactional DDL.
2023-06-06 02:20:03 superagi-backend-1          | INFO:     Will watch for changes in these directories: ['/app']
2023-06-06 02:20:03 superagi-backend-1          | INFO:     Uvicorn running on http://<IP_ADDRESS>:8001 (Press CTRL+C to quit)
2023-06-06 02:20:03 superagi-backend-1          | INFO:     Started reloader process [1] using WatchFiles
2023-06-06 02:20:05 superagi-backend-1          | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main
2023-06-06 02:20:07 superagi-backend-1          | INFO:     Started server process [20]
2023-06-06 02:20:07 superagi-backend-1          | INFO:     Waiting for application startup.
2023-06-06 02:20:07 superagi-backend-1          | INFO:     Application startup complete.

Only thing I can see that looks wierd is that - warn Invalid next.config.js options detected: .
Anyways, the only container that wasn't running was the superagi-gui-1 and by clicking the play button to execute it, this log comes up
2023-06-06 02:26:27 superagi-gui-1              |
2023-06-06 02:26:27 superagi-gui-1              | ><EMAIL_ADDRESS>dev
2023-06-06 02:26:27 superagi-gui-1              | > next dev
2023-06-06 02:26:27 superagi-gui-1              |
2023-06-06 02:26:27 superagi-gui-1              | - ready started server on <IP_ADDRESS>:3000, url: http://localhost:3000
2023-06-06 02:26:28 superagi-gui-1              | Segmentation fault
1969-12-31 21:00:00 superagi-gui-1 exited with code 139

Any ideas why this is happening?
My machine is a macOS Ventura 13.4

I basically commented out the webpackDevMiddleware options
I added that config because the in windows next.js was unable to detect code changes when developing.
try removing it and check

Hi Fluder, thanks for answering.
I commented out the lines you showed in the next.config.js file and the gui container is answering with the same segmentation fault log as shown above.

I am using the Pinecone free plan and thanks to this issue I managed to setup the workaround for it.
Now the gui container is not showing segmentation fault but it is still exiting with code 1.
I tried downloading the release version0.0.2 and running docker-compose up --build is showing segmentation fault for the gui container.

I left all 4 containers running and after a while I tried to restart the gui container and segmentation fault is back 😢
2023-06-06 12:01:06 superagi-gui-1              |
2023-06-06 12:01:06 superagi-gui-1              | ><EMAIL_ADDRESS>dev
2023-06-06 12:01:06 superagi-gui-1              | > next dev
2023-06-06 12:01:06 superagi-gui-1              |
2023-06-06 12:01:07 superagi-gui-1              | - ready started server on <IP_ADDRESS>:3000, url: http://localhost:3000
2023-06-06 12:01:07 superagi-gui-1              | Segmentation fault
1969-12-31 21:00:00 superagi-gui-1 exited with code 139

can u try with the latest main

@gpilleux can you try downloading/cloning the latest code in main branch instead of the release

All the executions have been with the latest main (except this one time with the release verison 0.0.2).
I have pulled the latest main branch and still getting Segmentation Fault
2023-06-06 15:26:56 superagi-backend-1          | wait-for-it.sh: waiting 60 seconds for super__postgres:5432
2023-06-06 15:26:56 superagi-backend-1          | wait-for-it.sh: super__postgres:5432 is available after 0 seconds
2023-06-06 15:27:01 superagi-backend-1          | INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
2023-06-06 15:27:01 superagi-backend-1          | INFO  [alembic.runtime.migration] Will assume transactional DDL.
2023-06-06 15:27:03 superagi-backend-1          | INFO:     Will watch for changes in these directories: ['/app']
2023-06-06 15:27:03 superagi-backend-1          | INFO:     Uvicorn running on http://<IP_ADDRESS>:8001 (Press CTRL+C to quit)
2023-06-06 15:27:03 superagi-backend-1          | INFO:     Started reloader process [1] using WatchFiles
2023-06-06 15:27:10 superagi-backend-1          | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main
2023-06-06 15:27:19 superagi-backend-1          | INFO:     Started server process [20]
2023-06-06 15:27:19 superagi-backend-1          | INFO:     Waiting for application startup.
2023-06-06 15:27:19 superagi-backend-1          | INFO:     Application startup complete.
2023-06-06 15:26:57 superagi-gui-1              |
2023-06-06 15:26:57 superagi-gui-1              | ><EMAIL_ADDRESS>dev
2023-06-06 15:26:57 superagi-gui-1              | > next dev
2023-06-06 15:26:57 superagi-gui-1              |
**2023-06-06 15:26:58 superagi-gui-1              | Segmentation fault**
2023-06-06 15:27:04 superagi-celery-1           | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main
2023-06-06 15:27:13 superagi-celery-1           |
2023-06-06 15:27:13 superagi-celery-1           |  -------------- celery@d0163640b931 v5.2.7 (dawn-chorus)
2023-06-06 15:27:13 superagi-celery-1           | --- ***** -----
2023-06-06 15:27:13 superagi-celery-1           | -- ******* ---- Linux-5.15.49-linuxkit-x86_64-with-glibc2.31 2023-06-06 19:27:13
2023-06-06 15:27:13 superagi-celery-1           | - *** --- * ---
2023-06-06 15:27:13 superagi-celery-1           | - ** ---------- [config]
2023-06-06 15:27:13 superagi-celery-1           | - ** ---------- .> app:         superagi:0x7f22e26a5040
2023-06-06 15:27:13 superagi-celery-1           | - ** ---------- .> transport:   redis://super__redis:6379/0
2023-06-06 15:27:13 superagi-celery-1           | - ** ---------- .> results:     redis://super__redis:6379/0
2023-06-06 15:27:13 superagi-celery-1           | - *** --- * --- .> concurrency: 10 (prefork)
2023-06-06 15:27:13 superagi-celery-1           | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
2023-06-06 15:27:13 superagi-celery-1           | --- ***** -----
2023-06-06 15:27:13 superagi-celery-1           |  -------------- [queues]
2023-06-06 15:27:13 superagi-celery-1           |                 .> celery           exchange=celery(direct) key=celery
2023-06-06 15:27:13 superagi-celery-1           |
2023-06-06 15:27:13 superagi-celery-1           |
2023-06-06 15:27:13 superagi-celery-1           | [tasks]
2023-06-06 15:27:13 superagi-celery-1           |   . execute_agent
2023-06-06 15:27:13 superagi-celery-1           |
2023-06-06 15:27:16 superagi-celery-1           | [2023-06-06 19:27:16,831: INFO/MainProcess] Connected to redis://super__redis:6379/0
2023-06-06 15:27:16 superagi-celery-1           | [2023-06-06 19:27:16,900: INFO/MainProcess] mingle: searching for neighbors
2023-06-06 15:27:17 superagi-celery-1           | [2023-06-06 19:27:17,993: INFO/MainProcess] mingle: all alone
2023-06-06 15:27:18 superagi-celery-1           | [2023-06-06 19:27:18,090: INFO/MainProcess] celery@d0163640b931 ready.
2023-06-06 15:26:54 superagi-super__redis-1     | 1:C 06 Jun 2023 19:26:54.393 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2023-06-06 15:26:54 superagi-super__redis-1     | 1:C 06 Jun 2023 19:26:54.394 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
2023-06-06 15:26:54 superagi-super__redis-1     | 1:C 06 Jun 2023 19:26:54.394 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
2023-06-06 15:26:54 superagi-super__redis-1     | 1:M 06 Jun 2023 19:26:54.396 * monotonic clock: POSIX clock_gettime
2023-06-06 15:26:54 superagi-super__redis-1     | 1:M 06 Jun 2023 19:26:54.412 * Running mode=standalone, port=6379.
2023-06-06 15:26:54 superagi-super__redis-1     | 1:M 06 Jun 2023 19:26:54.412 # Server initialized
2023-06-06 15:26:54 superagi-super__redis-1     | 1:M 06 Jun 2023 19:26:54.419 * Ready to accept connections
2023-06-06 15:26:54 superagi-super__postgres-1  |
2023-06-06 15:26:54 superagi-super__postgres-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-06-06 15:26:54 superagi-super__postgres-1  |
2023-06-06 15:26:54 superagi-super__postgres-1  | 2023-06-06 19:26:54.598 UTC [1] LOG:  starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-06-06 15:26:54 superagi-super__postgres-1  | 2023-06-06 19:26:54.600 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-06-06 15:26:54 superagi-super__postgres-1  | 2023-06-06 19:26:54.600 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-06-06 15:26:54 superagi-super__postgres-1  | 2023-06-06 19:26:54.612 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-06-06 15:26:54 superagi-super__postgres-1  | 2023-06-06 19:26:54.640 UTC [29] LOG:  database system was interrupted; last known up at 2023-06-06 19:26:14 UTC
2023-06-06 15:26:55 superagi-super__postgres-1  | 2023-06-06 19:26:55.354 UTC [29] LOG:  database system was not properly shut down; automatic recovery in progress
2023-06-06 15:26:55 superagi-super__postgres-1  | 2023-06-06 19:26:55.361 UTC [29] LOG:  invalid record length at 0/19BCCD0: wanted 24, got 0
2023-06-06 15:26:55 superagi-super__postgres-1  | 2023-06-06 19:26:55.361 UTC [29] LOG:  redo is not required
2023-06-06 15:26:55 superagi-super__postgres-1  | 2023-06-06 19:26:55.377 UTC [27] LOG:  checkpoint starting: end-of-recovery immediate wait
2023-06-06 15:26:55 superagi-super__postgres-1  | 2023-06-06 19:26:55.401 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.007 s, sync=0.003 s, total=0.029 s; sync files=2, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=0 kB
2023-06-06 15:26:55 superagi-super__postgres-1  | 2023-06-06 19:26:55.416 UTC [1] LOG:  database system is ready to accept connections

This is the complete log of `docker-compose up --build with the highlighted superagi-gui error.

can you give your computer spec
try this out
once the error occurs
install node if you dont have it
then do

npm install
npm run dev

if you already have a node modules folder delete it first

try replacing your next.config.js with the following:
`/** @type {import('next').NextConfig} */
const nextConfig = {
assetPrefix: process.env.NODE_ENV === "production" ? "/" : "./",
webpack: config => {
config.watchOptions = {
poll: 1000,
aggregateTimeout: 300,
};
return config;
},
};
module.exports = nextConfig;
`

So I ran a bash shell on the container and you can see that npm is installed and up to date. Segmentation fault visible after second npm run dev command. Couldn't fetch localhost:3000 on either execution. How can I look for more specific logs?

Aren't you seeing this same error? Why would my OS have anything to do on this container being executed? I have a Macbook Pro 2020 running on Ventura 13.4.

I tried in mac didn't get the error
can you increase the amount of resource the docker desktop is provided
you can change it in docker desktop setting under resources

I have those exact same settings on the Docker Desktop.
Since I don't know how else to debug this, I deleted the project and cloned the repo from scratch. Only change made was renaming config_template.yaml to config.yaml and didn't touch any of the code.
Running docker-compose up --build gives me the exact same log as previously. Really strange. Am I missing some configuration which might provoke this segmentation fault?

Now I cloned the repo on an ubuntu machine and the gui is running fine!
I'm really confused as to why this isn't working on my macOS... but oh well, will be using it on the Ubuntu where is doesn't have any problems.
Thanks so much for the support, keep it up!

I'm having the exact same issue (Intel macOS). I wonder if it is an issue with docker on macOS on intel?

I solved it: Docker Settings->Uncheck Virtualization Framework and used system default container terminal and legacy file system. Not sure which one fixed it. But was excited to share the update.

This actually solves it.
So much thanks @kcverde !!

I also can confirm that disabling "Use Virtualization framework" in Settings does the magic.  Thanks @kcverde for sharing your observation, it really did save my and many others' day!
I didn't change "Container terminal" option, which is "Integrated" in my Settings and it works. Neither did I change "Legacy file system" option, and the GUI works.
Can we enforce this container setting somehow? It would be nice to have that setting in right condition for everyone who clones the repo and builds the container. Quite many seem to run into this exact problem. As a workaround and quick fix, we could update it in the README.
But, do we have a config level solution for this so that it would work just like magic?

Is this issue still persisting in the newer version releases?

I solved it: Docker Settings->Uncheck Virtualization Framework and used system default container terminal and legacy file system. Not sure which one fixed it. But was excited to share the update.

Thank you a lot, finally, it solved on intel macOS


xml_reflection: First step to enable deprecation of public access

First step in #34
Also cleans up the README. Can split that off into separate PR if so desired.

@clalancette Might you have time at some point to take a gander at this?

@eacousineau Thanks for the pull request! Unfortunately I think the earliest we'll be able to review this is after the Crystal release in December. How soon would you like to see this PR in?

 And no rush on my part, December sounds good. Would be nice to start hiding the internals so they can either be simplified or stripped away at some point in lieu of something simpler.


Fix uri issue with subdomain addresses like

https://yourserver/git/YourOrga/Repo.git
:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
fix issue #762
:boom: Does this PR introduce a breaking change?
no

Travis-CI is insane 9d27f8


worked on your latest feature update issue. changed a simple sidebar into a  smooth side bar with few animations, and responsive as well

https://github.com/user-attachments/assets/b684cc02-15a6-4333-86eb-13e1b945435a
you can have a look at the changes over here 👆🏻

@archita-2810 Kindly mention the issue that you have fixed/resolved.
For example:- fixes #xyz issue

worked on
issue - Improve Responsiveness of Sidebar Menu #4

Hello @archita-2810, As you know, the assignee can submit a pull request (PR) and you haven't been assigned to it.


unfollow requests to follow

Hello guys how are you_ Is here any script to unfollow my requests to follow?
Thank you

you mean cancel the pending follow requests ??

you mean cancel the pending follow requests ??

Yes, that is it!

the unfollow function on the API cancel the follow request if the user did not accept  if keep list of users you followed or try to follow you cam iterate throw them and cancel the follow request of users you did not follow

the unfollow function on the API cancel the follow request if the user did not accept if keep list of users you followed or try to follow you cam iterate throw them and cancel the follow request of users you did not follow

Thank you for replying bro.
If i use unfollow non followers on multi_script_CLI didnt take the list from pending follow requests.

this not implemented to any of the examples provided you have to code the way suit and you the list of users you target later to check of the one non followed and cancel the pending request

There is no examples to unfollow from file and to take the list could be something hard if you have a lot of contacts that didnt acept you... i followed this steps to take the list:
Go to Instagram.com
Click on your profile then the settings icon
Click ‘Privacy and security’
Under ‘Account data’, Click on ‘View account data’
Under ‘Connections’, click on ‘View all current follow requests’
But have to click on "MORE" more than 100 times...
Thats why i asked for some example that do that, i dont have
knowledge to code that.

Any help? Thank you!

Anyone could help me with this action please?


[FLINK-15488] Obtain the JVM and TM param correctly

What is the purpose of the change
When using logback it is not possible to start the taskmanager using taskamanger.sh scripts. To fix this issue, we need to make a contract that the calculation result is always outputted in the last line and in specific format. Then, we can fetch and verify it even when the log is redirected to console.
Brief change log

Introduce a prefix to the calculation result of BashJavaUtils class
Fetch the calculation result and ignore side output.
Fail the script when error occurs during calculation.

Verifying this change

Using logback, you could follow this guide

Start a TaskExecutor by ${FLINK_DIR}/bin/taskmanager.sh

Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? no

cc @tillrohrmann  @azagrebin @xintongsong @wangyang0918

Thanks for the review @xintongsong . PR updated.

LGTM. Merging


Peechy

Hello,
Name : Peechy
Licence : Do whathever you want
List of files : Top, Bottom and Button
Here is Peechy, a cross design between Pebble and Watchy.
STL Files : ( Can't upload STL directly )  Peechy-STL.zip
I'm not an expert in 3D or technical design, the files are not as clean as the reference design, I tried to submit a design that would fullfil my wishes about the watch.
What I love about Watchy, is the blunt design, I really likes the fact that you can see the components directly on your wrist, making the form being the function.
I appreciate a bit of comfort too, so I tried to mix the Watchy reference case, with the entire screen board visible and buttons a bit more integrated than the reference design.
Here is some pictures !

Don't forget the metal 👍

Have a great day !

@optogram beautiful renders!

@Optogram added to main repo and submitted your design for our contest!

Closing

@Optogram  congratulations on winning third place for the design contest! Please reach out to us via<EMAIL_ADDRESS>or DM us on Twitter with your contact info so you can collect your prize!


[STORM-3000] added missing @Override annotations

https://issues.apache.org/jira/browse/STORM-3000
Adding missing @Override annotations helps detecting inheritance issues when generics are used more intensively.

I don't think we should modify the thrift generated files, any way we could tell thrift to generate these annotation? If not, can we leave those files as is given they should never be modified manually anyways so @override will not provide any value in those cases.

-1
Agree with Parth. Modifying the generated files is out of the question. The Thrift compiler should be patched to add those annotations if it doesn't have an option for that already.

@krichter722 thanks for the pull request, if you could remove the changes you made to the generated thrift code the rest seems fine.

@krichter722 Any news on this?

@krichter722 this pull request has been inactive for months, so I will be closing it soon.  Please reopen the pull request if you would like to address the comments.  If you do, please create a Jira for this work and resolve conflicts with the master branch.

@d2r I rebased the branch, removed changes in classes generated by the Thrift compiler and included all subprojects. Since checkstyle is now in place I reviewed all maxAllowedViolations in POMs in order to avoid future missing @Overrides.
I can reduce the maxAllowedViolations values is a separate PR, but I think it makes sense to include them here.
Please reopen this PR (I can't do it) can trigger Travis.

@krichter722 Sorry, I guess no one noticed your comment. Github won't let us reopen closed PRs if the base branch has been force pushed. If you still want these changes in, please open a new PR.

Apologies @krichter722, my GitHub notifications were getting black-holed while my employer changed its name. I had missed them for a while and evidently I did not see your comment. Yes I think we are not able to re-open this PR due to a GitHub limitation. This PR is superseded by #3020

@d2r You can merge #3020 if you want :)

@d2r You can merge #3020 if you want :)

OK I took a look at it, thanks for the reminder.


Hidden verbs

Hidden verbs: https://www.plainlanguage.gov/guidelines/words/avoid-hidden-verbs/

Referenced in https://www.plainlanguage.gov/guidelines/words/avoid-hidden-verbs/. We could try to detect words like “carry out”, “undertake”, “make”,  and others mentioned there. We could also do a regular expression to look for words ending in -ing, -tion, -ment, or -sion that are between the words “the” and “of.”


Auto uid

Previously, when setting up a tinkerforge solution in Bonsai we need to open the tinkerforge viewer to figure out what UIDs correspond to connected modules and then enter those UIDs manually on each tinkerforge node in Bonsai. This is time consuming and prone to error. Here, we implement a "Device" drop down that searches across tinkerforge IP connections to automatically populate UIDs and their corresponding device names.

Change requests implemented by commits 4afe2a2 / 83d8996


Strip / when joining the registry url components.

This fixes an issue when pushing docker images built in the .github/workflows/sv_pipeline_docker.yml workflow.

Thank you, @TedBrookings


[KOGITO-998] Setup all run-smoke params into Makefile

https://issues.redhat.com/browse/KOGITO-998
Many thanks for submiting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[x] You've tested the new feature/bug fix in an actual OpenShift cluster

will add also some bats tests

added some bats tests. Please let me know @ricardozanini @sutaakar

Looks good to me.

@radtriste are we ready?

@ricardozanini we are :)


Change time updates to current time for duplicate sync out records

@edmofro fine to delete related branch yea?

Yeah think so!


Python 3.11 support, and matrix cleanup

What does this pull request do?
Adds support for testing with Python 3.11, and cleans up the test matrix a bit:

some excludes are no longer needed, as the instrumented package fixed the incompatibility
some package versions are not compatible with any Python version we test, so instead of excluding them via matrix, we can remove them from the matrix altogether.

This depends on #1678

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-10-25T12:46:45.563+0000

Duration: 32 min 6 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
5076

Skipped
3634

Total
8710

:green_heart: Flaky test report
Tests succeeded.
:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test linters : Run the Python linters only.

/test full : Run the full matrix of tests.

/test benchmark : Run the APM Agent Python benchmarks tests.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

:globe_with_meridians: Coverage report

Name
Metrics % (covered/total)
Diff

Packages
100.0% (68/68)
:green_heart:

Files
100.0% (229/229)
:green_heart:

Classes
100.0% (229/229)
:green_heart:

Lines
92.182% (18383/19942)
:grey_exclamation:

Conditionals
75.257% (2850/3787)
:grey_exclamation:

/test full

/test full

/test full


Is caffe2 conflicting TensorFlow？

hello,
To avoid conflicting packages, I can create a new environment in conda, and install all the requirements in there。But can i  install caffe2 in the environment like my-ENV_python2???
build on:

ubuntu14.0.4
cuda 8.0 cudnn 7.0
anaconda3 python3.5
env anaconda: python2.7.13

Thanks!

Have you created the environment?


CODE RUB: GET Started Using Standard-Team Principles

This issue is a starting point for getting current code base refactored for Teams
@pratikkaje

Add copyright headers to all files (See programs.cs file in PR: #2 commit one)
by placing your cursor at the beginning of the first foremost line of the file hit ctrl+.
select add header. (this only works if there is a existing header)

Acceptance tests require there own models within the project, do not use project shared models.
If a model changes in the core model the acceptance test can help discover these changes. You can copy the class to a appropriate folder within the acceptance project.

Use Team Standard principles https://github.com/hassanhabib/The-Standard-Team
by doing this it allows others to assist and code review

Mark PR's as DRAFT so they do not accidentally get merged.

More to follow.

@pratikkaje Note the first PR that closed this was setup settings and not this Issue related.


[ryu]Fix linux problem with ccache

What does your PR fix? Fixes issue #
Error on Linux machines with ccache - "ccache: error: Failed to create temporary file for..."
Which triplets are supported/not supported?
As in initial PR
Does your PR follow the maintainer guide?
Yes

Hi @kreuzerkrieg
Thanks for this PR.
Could you please also bump the version as 2.0-1 in CONTROL file?
It seems that this port doesn't support arm, uwp, x86. If so, please update vcpkg_fail_port_instll(ON_ARCH "x86" "arm" ON_TARGET "uwp").
Also add Supports: !(uwp|arm|x86) field to CONTROL file.

Hi @kreuzerkrieg
Thanks for this PR.
Could you please also bump the version as 2.0-1 in CONTROL file?
It seems that this port doesn't support arm, uwp, x86. If so, please update vcpkg_fail_port_instll(ON_ARCH "x86" "arm" ON_TARGET "uwp").
Also add Supports: !(uwp|arm|x86) field to CONTROL file.

Done

bump

oops! didnt push the change

/azp run


Fixing misleading details about tab selection api

Currently, documentation on tabs says:

You can programmatically trigger a tab change with our select_tab method. You have to input the id of the tab you want to switch to.

Specifically:

input the id of the tab

This is very false. As you can see by the source here, selection of tabs has nothing to do with their id, and is instead entirely based on the contents of the href attribute of the element.
I've updated the documentation here to be correct.

See here

There are id's and they will also be the same as the href's, they are essentially the same thing

@Dogfalo In the example code in the tutorials/in your screenshot, it is true that the id's and the the hrefs are the same. Since they are the same, attempting to select based on the id will appear to work.
However, if the example html where changed so the ids are different from the hrefs and you attempt to select a tab now based on the id, the js will not work and the selection will not change.
So if the html where changed to the following:

Test 1

Test 2

Disabled Tab

Test 4

Test 1

Test 2

Test 3

Test 4

Given the above html, attempting to change the selected tab like so:
$('ul.tabs').tabs('select_tab', 'testone');

This javascript will do nothing and no new tab will be selected.

I'm not quite sure your point is completely valid, as the example that you give breaks the tabs implementation altogether: http://codepen.io/anon/pen/pJxaKa
For it to work it needs to be the same code as the documentation: http://codepen.io/anon/pen/NqOyzg
In which case the id and href are essentially the same thing as indicated by @Dogfalo

@carlosperate @Dogfalo  The context that I brought this issue up in was a project that made use of the tabs but without taking advantage of the built in ability to hide and show elements based on the currently selected tabs.
Revisiting this, I see that the way the mentioned project was using these tabs was not how they where intended to be used by the Materialize developers. I see now why the documentation for Materialize is the way it is. Thank you both for your comments!


Accept UIAppearance

Added capacity to customize layout using UIAppearance
Now you have one alternative to customize TSMessageView, you can use UIAppearance.
These are the properties
[TSMessageView appearance] setTitleFont:[UIFont boldSystemFontOfSize:6]];
[[TSMessageView appearance] setTitleTextColor:[UIColor redColor]];
[[TSMessageView appearance] setContentFont:[UIFont boldSystemFontOfSize:10]];
[[TSMessageView appearance]setContentTextColor:[UIColor greenColor]];
[[TSMessageView appearance]setErrorIcon:[UIImage imageNamed:@"NotificationButtonBackground"]];
[[TSMessageView appearance]setSuccessIcon:[UIImage imageNamed:@"NotificationButtonBackground"]];
[[TSMessageView appearance]setMessageIcon:[UIImage imageNamed:@"NotificationButtonBackground"]];
[[TSMessageView appearance]setWarningIcon:[UIImage imageNamed:@"NotificationButtonBackground"]];

@KrauseFx whats your thoughts about this PR? i think it a really good approach to using custom design...

+1 @KrauseFx

Any updates on this?

Looks great, thanks for the pull request :+1:
Could you just fix the merge conflicts:

We can’t automatically merge this pull request.

Thanks!

Thanks!

@KrauseFx Merged with 'master'.

Thanks @diogomaximo for working on this! :+1:

And sorry it took so long :disappointed:


docs: v3.1 Release Notes

Description
Release notes for v3.1

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

In Release notes we should only keep the latest release + patches. It's not a changelog. That's why I removed the "unreleased section"


Have a nice day! @jesen8 ! :)


fix(builder): corretly detect mode of hashed plugins

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

moduleContainer.addPlugin generates a hash suffixed name if no explicit fileName is provided to prevent name collisions inside .nuxt. This PR ensures mode of file names like mode-test.plugin.client.530b6c6a.js is also correctly detected.
fixes #5694
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #5695 into dev will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##             dev   #5695   +/-   ##
=====================================
  Coverage   95.6%   95.6%
=====================================
  Files         82      82
  Lines       2664    2664
  Branches     683     683
=====================================
  Hits        2547    2547
  Misses        98      98
  Partials      19      19

Impacted Files
Coverage Δ

packages/builder/src/builder.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@clarkdo As the pattern is like .(client|server|all). I think it is safe to just allow extending suffix. Resolving mode in addPlugin introduces duplicate code. Any concerns for not allowing more than 2 suffixes?

Maybe an inappropriate example, foo.client.server.js

In normal usage, it’s fine, so feel free to merge.

The interesting fact is that with current replace strategy both previous and current result in something wrong :D


Encode and Decode  JWT specific base64url encoding with 'WithPadding(…

using official base64 package's method  "WithPadding" to padding stripped.

replace "base64.URLEncoding.WithPadding(base64.NoPadding)" with "base64.RawURLEncoding"

Thank you for helping me and my team mate solve an issue with this package, please merge this :)


Component video-control error

Describe the bug
Component video-control throws a Cannot read properties of null (reading 'setAttribute') at n.init (video-control.js:68:21)
To Reproduce
Here is an example plane with video-control:
{
  "object_id": "video-ctlr",
  "persist": true,
  "type": "object",
  "action": "update",
  "data": {
    "object_type": "plane",
    "height": 1,
    "width": 1,
    "position": {
      "x": 1,
      "y": 1,
      "z": 1
    },
    "rotation": {
      "w": 1,
      "x": 0,
      "y": 0,
      "z": 0
    },
    "material": {
      "color": "#7f7f7f"
    },
    "video-control": {
      "frame_object": "/store/users/wiselab/images/conix-face-white.jpg",
      "video_object": "square_vid6",
      "video_path": "/store/users/wiselab/videos/kungfu.mp4"
    },
    "click-listener": {
      "enabled": true,
      "bubble": true
    }
  }
}

Using arena-core v1.19.1
Expected behavior
Video control should allow to add a video and start/stop it.
Device/OS (please complete the following information):
I tried in Desktop Chrome; it should happen across browsers.

I think this was fixed in the refactor? Can you try again on https://arenaxr.org/lobby?


Stream.js example doesn't work?

If I try the example after cloning the source from Github, it works.  If I try it from an npm install telehash then I get the following error:
bash-3.2$ node stream.js
[Error: invalid public key data]
[Error: invalid public key data]

/Users/david/Documents/Toptal/clients/Eris-Industries/worker-hello-world/node_modules/telehash/examples/stream.js:9
meshA.mesh(meshB);
      ^
TypeError: Cannot call method 'mesh' of undefined
    at Object.<anonymous> (/Users/david/Documents/Toptal/clients/Eris-Industries/worker-hello-world/node_modules/telehash/examples/stream.js:9:7)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:935:3

I just reinstalled and now it's working; it must have been a fluke.


Image classification/annotation multiple image columns

Fixes the case for multiple image columns present in the intended annotation dataset

Fixes #1527


update workflow and requirements on python 3.8-3.12

python community support python3.8>=. Well, I update workflow and toml file

Thanks @ArtemIsmagilov . Both Python 3.6 and 3.7 have made it past end-of-life so these changes are all welcome.

@unode, thanks to all the developers for this project, it blew my mind that the library can be generated by a bash script. This is clearly a big step forward for the industry. And thanks for the comment)

The power of standards :)
It's a little inflexible but it was an interesting meta project to write.
Thanks for the feedback and for the contribution!


Allow multiple instrumentators for multiple servers

What is the problem?
If I run integration tests with my fastapi server instrumented with metrics I have the following error:
ValueError: Duplicated timeseries in CollectorRegistry: {'http_requests', 'http_requests_created', 'http_requests_total'}

How to reproduce?
from fastapi import FastAPI
from prometheus_fastapi_instrumentator import Instrumentator

def test_expose_twice():
    app = FastAPI()
    Instrumentator().instrument(app).expose(app, endpoint="/metrics_1")
    Instrumentator().instrument(app).expose(app, endpoint="/metrics_2")

Issue
The issue is that the Instrumentator always use prometheus_client.REGISTRY for its metrics. When we run our tests we construct multiple instances of our servers so the instrumentator tries to register the same metrics for all of them.
Possible solution
Accept registry as a constructor parameter to PrometheusFastApiInstrumentator class so users can specify their own registries.

中文版本
可以使用如下的方式：
from loggers import logger
from fastapi import FastAPI, Form
import uvicorn
from prometheus_fastapi_instrumentator import Instrumentator

app = FastAPI()

@app.get('/')
def root():
    return {"message": "Hello World"}

@app.on_event("startup")
async def startup_event():
    Instrumentator().instrument(app).expose(app)

if __name__ == '__main__':
    uvicorn.run("api:app", host="<IP_ADDRESS>", port=5002,)

把该文件命名为 api.py

然后使用 python api.py 运行该文件，将获得如下的输出：
─➤  python api.py
INFO:     Started server process [14004]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:5002 (Press CTRL+C to quit)

具体可以参考:Instrumentator appears to be broken with the latest FastAPI

English Version
You can use the following.
from loggers import logger
from fastapi import FastAPI, Form
import uvicorn
from prometheus_fastapi_instrumentator import Instrumentator

app = FastAPI()

@app.get('/')
def root():
    return {"message": "Hello World"}

@app.on_event("startup")
async def startup_event():
    Instrumentator().instrument(app).expose(app)

if __name__ == '__main__':
    uvicorn.run("api:app", host="<IP_ADDRESS>", port=5002,)

name the file api.py

Then run the file with python api.py and you will get the following output.
─➤  python api.py
INFO:     Started server process [14004]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:5002 (Press CTRL+C to quit)

For details, see:Instrumentator appears to be broken with the latest FastAPI

is there a solution to this?

I have a somewhat related issue, so adding to this thread - let me know if opening a separate issue would be better. the issue:
I have a fastapi app that i annotate and expose with the instrumentator, and it works as expected in that it adds a /metrics GET endpoint with all metrics. When i serve this app using more than 1 (lets say uvicorn) servers, i naturally get more than one /metrics endpoint. which of the various works i connect to when visiting {url}/metrics seems to be randomly decided by the load balancing logic of the parent worker process.
this however is an issue, as prometheus presumably would only ever connect to one randomly selected worker process' /metrics endpoint and scrape what is essentialy the nth part of the metrics it should get.
is there a way to avoid this (breaking imo) issue and consolidate the metrics resulting from exposing the app to the instrumentator into one metrics endpoint? I have seen other libraries' approach to this (e.g. kserve - they dont use this library and rely on the more low level prometheus-client library directly), but would be interested in your opinion

@SebastianScherer88, please check out the following section in the documentation of prometheus-client:
https://github.com/prometheus/client_python#multiprocess-mode-eg-gunicorn
The gist is that you have to set the environment variable PROMETHEUS_MULTIPROC_DIR before starting the respective Python program.

It seems like the issue fixed in #208
https://github.com/trallnag/prometheus-fastapi-instrumentator/blob/master/CHANGELOG.md#5100--2023-02-26

Thanks for pointing this out @navolotsky


Added the default ignore config for service disable error

Integration test logs

Logs
Add passing integration test logs here

Example query results

Results
Add example SQL query results here (please include the input queries as well)

@cbruno10  You are correct that The main use case would be ignoring specific code/message combinations, e.g., if multiple error codes had similar messages.  Not knowing what these error messages look like, or how common that case is, Its hard to make a recommendation.  If it is uncommon / unlikely, I would probably opt for the simpler, backward-compatible solution.

FWIW, I've squashed and rebased the commits from this PR here: https://github.com/pdecat/steampipe-plugin-gcp/tree/issue-286, and can confirm it works great :)
I've integrated the changes in our custom build of the plugin here: https://github.com/pdecat/steampipe-plugin-gcp/tree/dev

This PR is also working great to ignore issues when new regions are added, like is currently happening with northamerica-south1 (Queretaro):
2024-11-12 10:38:10.814 UTC [ERROR] steampipe-plugin-gcp.plugin: [ERROR]<PHONE_NUMBER>653: gcp_cloud_run_service.listCloudRunServices:
  api_error=
  | googleapi: Error 400: region: Unsupported region northamerica-south1
  | Details:
  | [
  |   {
  |     "@type": "type.googleapis.com/google.rpc.BadRequest",
  |     "fieldViolations": [
  |       {
  |         "description": "Unsupported region northamerica-south1",
  |         "field": "region"
  |       }
  |     ]
  |   }
  | ]
  | , badRequest

The following configuration allows to ignore them (along with service disabled errors):
connection "gcp" {
  plugin = plugin.gcp

  ignore_error_messages = [
    "^.*API has not been used.*$",
    "^.*Unsupported region.*$",
  ]
}


getAnnotations method throws an error when called from selectAnnotation event handler

While trying to get all the current annotations in the selectAnnotation event handler, the following error is thrown:
OpenSeadragonAnnotator.jsx:241 Uncaught (in promise) TypeError: Cannot read property 'clone' of undefined
    at OpenSeadragonAnnotator.jsx:241
    at Array.map (<anonymous>)
    at p.getAnnotations (OpenSeadragonAnnotator.jsx:241)
    at e.getAnnotations (index.js:131)
    at (index):101
    at n.emit (index.js:36)
    at Object.onAnnotationSelected (index.js:73)
    at p.<anonymous> (OpenSeadragonAnnotator.jsx:83)
    at index.js:271
    at Array.some (<anonymous>)

Hi, that's actually a duplicate to this issue in Annotorious (standard version):
https://github.com/recogito/annotorious/issues/120
.getAnnotations() throws this error when an annotation is currently selected.
The good news is: it's already fixed. But only in the latest state of the main branch. The bug still exists in the latest release, but will be gone with the next.

@rsimon. Thanks. I am closing this issue since its resolved in https://github.com/recogito/annotorious/issues/120.


[CMT-740-1082] Create de.md YN #54

Description

Please include a summary of the change and which issue is fixed.
Please also include relevant motivation and context.

This pull request ...
Fixed issue

Please indicate the fixed issues with this exact format Fixes #232 where 232 is the number of the issue. This will trigger an auto-close if the issue when this PR is merged.
Supported keywords:
Fixes #1,#2,#3
close #1, #2, #3
fix #1 #2 #3
resolve #1,#2 #3
Resolves: #1,#2,#3
closed : #1, #2, #3

Fixes #(issue)
Type of change

Please delete options that are not relevant and check the box.

[ ] Add a new article/page
[ ] Fix a Typo
[ ] Add a new translation
[ ] Other

Resources

Any screenshots, links or relevant resources to explain better the changes.

duplicate version already closed. This one can stay


Column "EBS Optimized: Max Bandwidth" displays incorrect MB/s

Look at Amazon's page: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html .
The figures in the column on ec2instances.info appear to be coming from the "Throughput (Mbps)" column from Amazon's page (above).
Note that Amazon's "Throughput" figures are in mega BITS, not mega BYTES.
Let's take a look at an example, c1.xlarge:
ec2instances.info says "EBS Optimized: Max Bandwidth = 1000.0 MB/s"
docs.aws.amazon.com says "Max. bandwidth (MiB/s) = 125"
I'm unsure whether issue https://github.com/powdahound/ec2instances.info/issues/135 (closed) is related.

Thanks for the heads up! Change on AWS' site got missed while making changes for the new X1 instance yesterday.


Better retry logic and error handling

When we call get_asset, we check if the error is a 404. If it is, that usually means that the operation hasn't completed yet, so we infinitely retry.
If the error is anything but a 404, we panic. We should probably have logic to stop in place and write the incomplete entries so that the user doesn't have to start over?

Fixed in aa4a1441ee0920f0410dc089848c7d8a1207b885


Swagger to WebAPI Link broken

the link https://github.com/NSwag/NSwag/wiki/SwaggerToCSharpControllerGenerator yields https://github.com/NSwag/NSwag/wiki

Yes, this feature/class is currently documented (experimental)

Great news, we are awaiting to see the documentation on this experimental feature.

Because this is an experimental feature, and the usage is very low, writing the documentation is not very high on my list... Do you have specific questions? You can use the NSwagStudio app to try various settings or run the "help" command in the command line for a list of available options...

thank you

awesome tooling dude!


UnixPB: Install JQ for mac repro tests.

Ensure JQ is installed on Mac Hosts for Reproducible build tests.
See: #3593
Checklist

[X] commit message has one of the standard prefixes
[X] VPC not applicable for this PR ( No Mac testing option. )

fyi @sophia-guo

Solaris check fail is unrelated to these changes, but is due to the github runner installing a newer version of Ansible, that has no Supported version of python installed on Solaris 10.


Lightweight Checkpointing

An epic. See Issue #447 for more context.

[x] Issue #447
[x] Issue #448

Done, see https://github.com/IntersectMBO/cardano-node/issues/5730 for the remaining upstream integration work.


Add support for SET_AWAY_MODE and TURN_ON/OFF on Daikin Climate

Description:
Adds support for SET_AWAY_MODE and TURN_ON/OFF on Daikin Climate
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#9370
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly (example).
[ ] New dependencies have been added to requirements in the manifest (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

This looks good -- but please the docs need to be updated and I couldn't find a PR in https://github.com/home-assistant/home-assistant.io.

@andrewsayre thanks! There are some issues with the next branch for Daikin in https://github.com/home-assistant/home-assistant.io, with many changes old changes that doesn't show up in current (which are correct).
I'm not sure how to proceed with the documentation changes to the next branch, but I did the changes that would merge nicely to the current branch: https://github.com/home-assistant/home-assistant.io/compare/current...fredrike:patch-8

@andrewsayre The documentation is updated now.


[JBEAP-15571] Test calls method with an Enum parameter from the JSF page.

Test calls deployed application with a JSF page. No error should occur when the class called from the JSF has a superclass and the called method has an Enum as a parameter.
JIRA issue: https://issues.jboss.org/browse/JBEAP-15571

Hi @dcihak -- Commit messages and PR titles must reference upstream JIRAs, not JBEAP.

Hi @bstansberry , I was unable to find any appropriate upstream JIRA issue, is it the JBEE-172? Thanks.

Hi @bstansberry , I was unable to find any appropriate upstream JIRA issue, is it the JBEE-172? Thanks.

Hi @bstansberry , I was unable to find any appropriate upstream JIRA issue, is it the JBEE-172? Thanks.

Hi @bstansberry , I was unable to find any appropriate upstream JIRA issue, is it the JBEE-172? Thanks.

Hi @bstansberry , I was unable to find any appropriate upstream JIRA issue, is it the JBEE-172? Thanks.

Hi @bstansberry , I was unable to find any appropriate upstream JIRA issue, is it the JBEE-172? Thanks.

Hi @bstansberry , I was unable to find any appropriate upstream JIRA issue, is it the JBEE-172? Thanks.

Hi @bstansberry , I was unable to find any appropriate upstream JIRA issue, is it the JBEE-172? Thanks.

@dcihak Best is to use a JIRA for the project to which you are committing, i.e. WFLY. If there isn't one, create it.

@bstansberry  I updated the pull-request and created upstream JIRA issue for it.

Retest this please.


tests: Made pointer parameters explicitely const where non-const pointer parameters are not needed

modified parameter types to receive a const pointer when a non-const pointer is not needed
This corresponds to following misra coding guideline:

A cast shall not remove any const or volatile qualification from the type pointed to by a pointer

This PR is part of the enhancement issue https://github.com/zephyrproject-rtos/zephyr/issues/48002 which port the coding guideline fixes done by BUGSENG on the https://github.com/zephyrproject-rtos/zephyr/tree/v2.7-auditable-branch back to main
The commit in this PR is a subset of the original auditable-branch commit:
https://github.com/zephyrproject-rtos/zephyr/commit/f953e929d842c7654957c0e41dd10d44c4c9f5b8

@andyross , @npitre
You are right, i was planning on adding const thing seperately across the different modules of the project.
Like here for example: https://github.com/zephyrproject-rtos/zephyr/pull/72675
I admit it was never ideal.
As it turns out, it might be possible to remove the arch_buffer_validate method entirely, as it does not seem to be in use anymore.
For this pr, I just removed the change for the validate method.


Multiple @javascript tests break zombie.js

I've been writing tests in Behat for my Drupal site, and I've based my setup after the example/ folder here, so I'm running tests with Goutte and Zombie.js. However, as soon as I had a second Feature tagged @javascript, it throws this error:
      Server process has been terminated: (8) [
      events.js:72
              throw er; // Unhandled 'error' event
                    ^
      Error: listen EADDRINUSE
          at errnoException (net.js:904:11)
          at Server._listen2 (net.js:1042:14)
          at listen (net.js:1064:10)
          at net.js:1146:9
          at Object._onImmediate (node_modules/zombie/lib/zombie/dns_mask.js:69:16)
          at processImmediate [as _immediateCallback] (timers.js:345:15)
      ] (RuntimeException)

I assume this means that either zombie.js is trying to bind the same port for its browser, or to listen to my site twice and getting blocked. I haven't yet gotten into zombie's internals to figure it out, but I wanted to raise the issue about it. I'd really rather not have to give up grunt-parallel-behat, but since these tests are running on Jenkins, that's not (yet) a deal breaker.

Issue cross-posted at minkphp/MinkZombieDriver#126.

The Mink people said that specifying a different port for each process in grunt-parallel-behat ought to work, which I have requested at linusnorton/grunt-parallel-behat#12.

We are currently looking to switch to Phantom.js


Make a view where gangs can see who they need to call given the current state

As per now, if a user has applied to several roles, but have not got any offers, the gang that this person has as it's lowest priority is supposed to call them at let them know. Make a view where each gang can view who they need to call given the current situation.

#200 #201 #202


reproducible builds

Thanks @nvollmar. I need to get back to this at some stage but something about this change is causing unit test failures and that will need to be investigated.

The tests that fail rely on finding cassandra-bundle.jar, one of the jars produced during the build. Something about enabling sbt-reproducible-builds upsets this lookup.

hmm, I wonder if updating https://github.com/raboof/sbt-reproducible-builds/blob/main/build.sbt#L39 would help.


fix: selection in other pages

we were passing wrong row coordinates to isSelected. it was the same for isLocked so this one fixes that as well

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


React 18 update. Updated packages versions. Fixed bugs after update.

Can this PR be merged?

Bump


A comment for avoid a nasty crash while running the simplest demo

This has been fixed in sciview 0.4.1 and was due to an abuse of Swing's EDT. I'll therefore close this PR.


DBZ-6216 New images only on Quay.io

https://issues.redhat.com/browse/DBZ-6216

@Naros Could you please take a look at this one? The content LGTM. If fine for you could you please merge it and sync it with a at least Twitter message?
@vjuranek Could you please send an announcement to the mailing list and create a new topic in the users stream when this is published?

@jpechane @Naros please review again if everything is accurate. Thanks!

LGTM, let's merge it after the release.


"error!options are missing alert" on home page shouldn't be shown

Bug report
Title
"error!options are missing alert" on home page shouldn't be shown
Issue Description
"error!options are missing alert" on home page shouldn't be shown
Preconditions
1. framework Version- master

Steps to reproduce
1. step1- create a booking, configurable product
2. step2- click on add to cart button from the home page, (showing error alert before redirect to the product page, it creating confusion for the visitors)

Expected result

As expected, the error alert shouldn't show on home page, it should be reflected after customer redirected to the product page

also, the alert is warning message, so kindly show a warning in "YELLOW" color instead of "RED"

Actual result

fixed

When will it be released?

I've tested the new https://github.com/bagisto/bagisto/releases/tag/v1.2.0-BETA1 release, where it's stated that bug 3231 is fixed and released.
#3231 "error!options are missing alert" on home page shouldn't be shown
Unfortunatelly the bug still exists, except now it's Warning! not an Error!

@stoney024
Agree with you. Thanks for notifying us


Update former-ramona.njk

Removing contain from bold summary of work.

@aaronhans Now that I know where things live, I thought I'd make this change for you to save you time. 🙂

Thanks @m-sullivan7!
I saw this update in slack and deployed the fix along with the Spanish version.


Add thermal material properties

In an internal DLR project, we want to compute radar and infrared signatures from aircraft. To do so, we need to add some basic thermal properties of materials, which are:

Thermal conductivity
Specific heat
Diffuse emissivity

These should be added to
/cpacs/vehicles/materials/material/

As the diffuse emissivity depends on the spectral wave length it should be stored as an array including wave length and the emmisivity factor.
The specific heat typically depends on the temperature. Therefore, it also needs to be an array including temperature and value.

What unit if measurement should we use for the wavelength? Internally, micrometers are normally used but that might conflict with the SI unit system that is used in CPACS elsewhere.
@DLR-LY what do you think?

I agree that we should consistantly use SI units throughout CPACS. Any exceptions would lead to uncertanties in the interpretation. I'd suggest we keep it clean by sticking to SI units for all values.

Merged into main development branch. Will be available at the next release 2.3.1 at the end of this month.

Perfect, thanks! :smile:


HOST file editor

Description of the new feature / enhancement
At times, you need to alter the HOST file but it is a very manual process.
It can become very cumbersome and would be very powerful and useful to have a quick editor for the file
This idea came from @snickler
Scenario when this would be used?
testing load balancers for instance
Supporting information
No response

Very cool!
I definitely would like to create a POC with basic functionality.
C# and WinUI3 are fine?

Very cool! I definitely would like to create a POC with basic functionality. C# and WinUI3 are fine?

That sounds perfect to me.

I have started working on the POC. I am focusing more on the service that read/write the hosts file than the UI 😄
@crutkas at the moment lines that aren't parsed as valid entry (including headers/comments) are removed when we write the file. Will be tricky to preserve them especially if sorting will be implemented. What do you think?
@niels9001 what do you suggest for the user inteface? What do you think about using a DataGrid here instead of a ListView?

Maybe we lead with PT generated comment and our UX had a direct editor for the top part we can’t parse?

I like the idea for the header on top of the file but still be a problem if users mix valid hosts entries and commented lines.

@niels9001 what do you suggest for the user inteface? What do you think about using a DataGrid here instead of a ListView?

Nice! I think a DataGrid could work, but only if we expect to do resizable columns and/or inline/direct editing (without the popup). (I personally like your current implementation btw :))!

Since I am not a big fan of DataGrid and I like to pipup let's try keep the ListView.
Thank you @niels9001 😃

I think a DataGrid could work [..]

Shameless plug: https://github.com/jerone/HostProfiles#readme

It would be nice to have hosts editor functionality similar to Hostsman, which allows us to subscribe to local or remote sources, such as Malware Domain List.


Your application already supports English language.
I will be glad if you add English version of README.md.
If you don't want to replace the current README.md, you can make the English version a link in the header, like other projects do.
For example:
https://github.com/hiddify/hiddify-next

We are delighted to hear that you've enjoyed using this application and appreciate your eagerness to share it with a global audience. Your feedback means a lot to us, and we thank you for your support and enthusiasm.
Now, the README has been successfully updated to English, making this project more accessible to a wider community. This change will help spread the word about the app and potentially attract new contributors and users from around the world.

Thank you!
I will try to spread the application among people


After pd.set_option('display.max_rows', None), df.describe().T only displays 60 rows

System information

OS: macOS 12.4
Modin version: 0.15.2
Python version: 3.9.12 (Anaconda)
Code we can use to reproduce:
In Jupyter nbotebook:

import os
os.environ["MODIN_ENGINE"] = "ray"
import modin.pandas as pd
import numpy as np
import ray
ray.init()
pd.set_option('display.max_rows', None)
df = pd.DataFrame(np.zeros((2,100)))
df.describe().T

Describe the problem

After running
pd.set_option('display.max_rows', None), df.describe().T only displays 60 rows

to display all rows of output, df.describe().T shows the first 30 rows and last 30 rows only, with no indication that you're not seeing all of the output.
Source code / logs

@rhstanton thank you for reporting this issue! I can reproduce it at Modin version 910bf2dd893f52072c2c25413bf0866825f8309d:
import modin.pandas as pd
pd.set_option('display.max_rows', None)
print(pd.DataFrame(list(range(20))))

the above script gives me just 12 rows in my terminal in ipython, while pandas gives me all 20 rows.
To whomever works on the fix:
I tried passing num_rows = len(self.index) to modin.pandas.BasePandasDataset._build_repr_df in case display.max_rows is None (and likewise for columns), but that's not passing the modified unit test test__options_display with max_rows = max_cols = None. However, setting max_rows to math.inf with special treatment so we don't try to divide infinity worked. The latter solution doesn't seem as clear, though.

This seems like low hanging fruit that we should fix in an effort to improve user experience.


Fix View creation in do_posts_and_waits

Noticed while trying to use DTK with Trilinos 14/Kokkos 3.7, also see https://github.com/ORNL-CEES/DataTransferKit/pull/603.
Our intent here was to initialize dest_buffer as empty first for general layouts. The default layout, e.g., for LayoutLeft, represents is 0-dimensional, though, see https://github.com/kokkos/kokkos/blob/25e2302a61cd07c8a5f8c369bbbcd2f43fde542f/core/src/Kokkos_Layout.hpp#L91-L100, and we started checking for the passed layout to have correct rank in Kokkos 3.7.0.
Since we are resizing the View in the next line anyway, it's easy to fix the issue here and just initialize it with the correct layout in the first place.

we started checking for the passed layout to have correct rank in Kokkos 3.7.0.

Why haven't we seen this in testing?

Why haven't we seen this in testing?

It might be that we are not exercising the if (permutation_necessary) branch.

So the check of the layout is runtime, an not compile time?

So the check of the layout is runtime, an not compile time?

Yes, it can't be compile-time.

It turns out that we don't actually need this since we changed the type of constructor in between the ArborX version I used for DTK and master. I'm not quite sure if it's a good idea that we don't check the input arguments for the constructor taking view_alloc arguments, also see https://github.com/kokkos/kokkos/pull/4618/files#r899449617 since that should also work now in the case described there.
We actually hit the permutation_necessary branch in our unit tests. Anyway, this pull request is still an improvement and would also make sure that we don't run into problems in case Kokkos would actually check the rank in that constructor.

Having a trouble reproducing the test failure.

Having a trouble reproducing the test failure.

I can reproduce the test failure but I still don't fully understand what's going on. Since this is only affecting SYCL+CUDA I would just disable the annotation test here and investigate independently.

There really wasn't a good reason to not allow Kokkos to create whatever allocations it needs.

Warnings reported are from building SYCL base image


Web interface softer on the eyes

Color tweaks to to make the web interface softer on the eyes by using a dark theme, +reducing the go_back refresh to 10 seconds.

I actually prefer the white background 😅

Let's make it configurable, then.

Anything subjective like colors should indeed be configurable, with a sensible default.
Maybe in first instance adding the colors to user_config_override-template.h

Like this (for current values)?
#define HTTP_META_GO_BACK_TIME "15"
#define HTTP_BODY_BACKGROUND "#FFFFFF"
#define HTTP_BUTTON_BACKGROUND "#0af"
#define HTTP_BUTTON_TEXT "#eee"
#define HTTP_BUTTON_REDBACK "#f33"
#define HTTP_BODY_TEXT "#000000"

The values are embedded in consts so to make it configurable a bit more rewrite is needed.

It is now possible to change the interface colors via user_config_override.h and build with the desired color scheme.
for example, the dark template @nagyrobi suggested.
// Dark theme
#define D_HTTP_COLOR_TEXT               "#eaeaea"    // Global text color - Very light gray
#define D_HTTP_COLOR_BACKGROUND         "#252525"    // Global background color - Very dark gray (mostly black)
#define D_HTTP_COLOR_INPUT_TEXT         "#000"       // Input text color - Black
#define D_HTTP_COLOR_INPUT              "#ddd"       // Input background color - Very light gray
#define D_HTTP_COLOR_INPUT_WARNING      "#ff5661"    // Warning text color - Brick Red
#define D_HTTP_COLOR_BUTTON_TEXT        "#faffff"    // Button text color - Very pale (mostly white) cyan
#define D_HTTP_COLOR_BUTTON             "#1fa3ec"    // Button color - Vivid blue
#define D_HTTP_COLOR_BUTTON_RESET       "#d43535"    // Restart/Reset/Delete button color - Strong red


chore: package upgrades, standardisation on linters, small code fixes

chore: package upgrades, standardisation on linters, small code fixes

I appreciate the hard work and commitment for reviewing all of my code!
This is a bit overwhelming to review, and there's too much noise to focus on specific refactoring goals. Would it be possible to open a unique PR per package scope? e.g. documentation changes, eden, eden-react-query, eden-svelte-query, react-example, etc.
It's just that there is a lot of feedback and clarification I would like to address, and I'm worried it will take an exceedingly long time to accumulate it in this big PR.


Add cache status output

Description:
Please, add cache status output cache-hit (see https://github.com/actions/cache).

I think this is coming, we're just waiting for merge: https://github.com/actions/setup-java/pull/275

Hello @sergey-s-betke
Thank you very much for your request!
We are considering your feature request and will review the PR very soon and inform you about it.
Thank you for your patience.

Hello everyone. The cache-hit output was added. For now I'm going to close the feature request. If you have any concerns feel free to ping us.


MediaObject does not appear but plays sound

I've just noticed that all agents using MediaObject does not appear the object (with picture and progress bar) but plays sound. Both platforms: iOS and Android.
Action's Simulator shows the object correctly.

On Android, do you see a media player notification appear?

notification was ok.
Seems that problem is fixed already.


Fixed distribution and tox tests

Codecov Report

:exclamation: No coverage uploaded for pull request head (dev@31e57dc).

Continue to review full report at Codecov.

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


As a maintainer, I want to enhance the schematic to handle files from multiple paths within the project.

**Given** the schematic is configured to process files,
**When** multiple file paths are specified as input,
**Then** the schematic should correctly process and generate files from each specified path.
**And** the schematic's documentation should be updated to reflect this new feature.
**And** tests should be added or updated to ensure the functionality is working correctly.


Code Structure

Hey @garrettrayj I saw your post on the mapnik dev mailing list, I don't have to give a big review but thought I would open a few tickets on your repo here on issues that I might see.
The first issue I see is that you have all your source in the main directory, its not required but its a lot easier if you put it all in a directory. Is this something required by phpize?
Confused by this as it shouldn't be any issue:
Do NOT compile Boost with C++11. On Mac at least, you'll have a bad time with missing symbols.

I'm not a fan of the directory structure either, but it's PHP extension convention and fighting it is more trouble than it's worth.
That note may be out of style. It's a issue I ran into early that very well could of been caused by a mistake elsewhere. I'll tinker with compiling Boost and update the README in the next release if it turns out to be a phantom.
Thanks again for the feedback!

@flippmoke I was a bit late to figuring out the fight was all in my head, but I got there eventually. The sigh I let out after revisiting this project's code could be heard around the world. 😆 Now all the extension classes are organized in the /src folder.
Also, the Boost issue was either a local problem, or something fixed by time. Using stock Mapnik and Boost Homebrew formulas works fine for compiling on Mac now.


chore(deps): upgrade dependencies

Description

References

Review Checklist

[ ] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[ ] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

Close in favour of https://github.com/openfga/frontend-utils/pull/194


Can't diff with another branch including uncommitted changes

Currently there is no way for the user to perform a diff between a branch -including uncommitted changes- and another branch.
In git, the command git diff <branch name> will diff the current HEAD including uncommitted changes with the given branch.
(git diff HEAD <branch name> will show the diff between the HEAD, without the uncommitted changes, and the given branch).
Decide which syntax will provide the desired result: related to #1305.

Also relevant: #996.

First, keeping HEAD out of this discussion for now. It shouldn't be introduced as part of the Diff change, the more appropriate place would be the resulting tasks of #1305
Suggestion:

When you diff using the branch reference, include the uncommitted objects.
When you specify anything else (Tag, Commit, anything with '~' or '^' ) which isn't directly the branch, use just the committed data.

Comparing to other operations:

List is aligned with the above semantics.
Merge/Revert blocks on a dirty branch for now.

I can live with that solution. The main downside I can see here, is that you will see uncommitted changes from both branches. This maybe strange if you're comparing with a branch that is not "owned" by yourself. For example, when comparing my branch with master, I will see uncommitted master changes that I don't need to know about (not in a security sense, just usability).
That's why I think #1305 should be addressed sooner than later.

But do you think #1305 is a prerequisite?
I agree with the downside, but you can still overcome it by referencing the commit that master points to. We can come up with an example where you DO want to compare the uncommitted in master.
My point is that guessing what the user wants is hard and error-prune. Having an aligned API (Branch -> with uncommitted, anything else without) allows flexibility and reduces friction of unexpected results. The exception to this is Merge and its supporting utils, where we decided to avoid dealing with uncommitted for now.

AFAICS the only disagreement here is about how to express "uncommitted" data.  We should think of "uncommitted" data as a cross between git index (staging) and stash (an actual commit).  So the half-plumbing command to access those is git diff-index.  And I think git diff takes a specific argument --no-index to avoid staging.  Thing is, git staging index is not per-branch.
So what should we do?
AFAICT we glue a git staging area to a branch.  This could have been porcelain, not plumbing.  So we could pretend that we have 2 tree types: committed and index, where an index is backed by a committed.  (This is a lot like our implementation, of course!).
Can we expose that?  Sure.  It's almost like selecting a ref.  So we could say that refs/heads/<BRANCH> is the committed, just like it is in git, and e.g. refs/indexes/<BRANCH> is the (current) staging.  Our problems stem from the fact that we want <BRANCH> to be shorthand for indexed rather than heads.  We can change just that, and state that <BRANCH> is always indexed/<BRANCH>.  If that's not what you want, explicitly state the ref heads/<BRANCH>, which is just the committed branch.  This also generalizes to when we decide to split indexed and heads, and allow a staging area that does not share the branch name.  We might never do this, but also we could.

We provide an address - listing or diff. The address represents also a state.
The command line for each option can set defaults if we like to address committed or not committed.
But the main issue is that the same address is using from the user's application - I think that we will need to align our URI schema first.
It will reflect which data we present or perform the operation on.

Changes proposal:

Diff operation will work on uncommitted changes when branch name is specified.  This will effect the current lakectl diff and the UI compare screen.
Merge button should be disabled in case one of the branches is selected - should work only for committed data.
Branch name with 'master@' will reference the last commit on the branch.

Agreed.
Do you mean merging is still blocked if one of the branches is dirty? I'm guessing this is a problem for branches which receive their inputs from some stream.
What's the git way of doing that? master~^~0 perhaps?

@itaiad200:

Yes, today we check only destination branch and assume you like to merge the committed data (this is what we show currently on compare).
If we like to address the part where we can merge into a working branch (with or without conflicts) we will probably need to address it in other issue.
The part that worries me is the UX. We are trying to align the use of the branch address for diff as for other commands. Example lakectl fs ls <branch> will list staging of the branch.  But when you diff and merge - if the stage area and the last commit got a different meaning we need to be consist on what we show.
Showing the latest uncommitted changes when we diff between two branches and have a button called 'Merge' that will merge changes between the committed data of the two branches is a problem, same issues will occur from the command line.

git stage area is not part of branch - the name of the branch is the same as referencing the head of the branch. in our older version of lakeFS we had ':HEAD' where you cloud use 'main:HEAD" to reference the latest commit on 'main' branch. but I'll take any syntax that works for us.

Alternative in order to focus on this use-case only - we can add an option for diff where we show the uncommitted changes from source by demand. it can be the default for the UI and options for the command line.
It means at we do not support any special reference syntax to the committed data. We keep using the branch name as a name and a flag / operation determine how to address the data.

After first discussion on the above, we agreed to first address the branch URI #2135.
When it will be enable to address branch committed and uncommitted workspace explicitly, we can agree on what the default branch refrence will perform and support it.

@nopcoder still relevant?

@nopcoder still relevant?

very


Incompatibility with Node v7.3.0

I seem to be unable to run Karma and jsdom with Node v7.3.0.
The following error occurs:
21 12 2016 14:34:03.540:INFO [karma]: Karma v1.3.0 server started at http://localhost:9876/
21 12 2016 14:34:03.543:INFO [launcher]: Launching browser jsdom with unlimited concurrency
21 12 2016 14:34:03.550:INFO [launcher]: Starting browser jsdom
21 12 2016 14:34:04.336:INFO [Node.js (linux; U; rv:v7.3.0) AppleWebKit/537.36 (KHTML, like Gecko)]: Connected on socket /#tduonCE02UcVqoG8AAAA with id 35304974
21 12 2016 14:34:14.343:WARN [Node.js (linux; U; rv:v7.3.0) AppleWebKit/537.36 (KHTML, like Gecko)]: Disconnected (1 times), because no message in 10000 ms.
Node.js (linux; U; rv:v7.3.0) AppleWebKit/537.36 (KHTML, like Gecko) ERROR
  Disconnected, because no message in 10000 ms.

Original issue in Karma repo: https://github.com/karma-runner/karma/issues/2511#issuecomment-268663143

You might have more luck by contributing to this https://github.com/badeball/karma-jsdom-launcher/issues/6

Since this involves libraries besides jsdom and there has been no attempt to reproduce it using just jsdom, this is out of scope for this repository. Closing.