How to start detection only when need to detect?

I use TX2 to control the robot to complete SLAM and navigation. During the navigation process, I need to detect several frames of images in a short period of time (about 2 seconds) at a specified location.
In order to save the computing resources of TX2, I want to suspend detect during other non-detect time. But I found that when I start the darknet_ros node, the node keeps detecting the images collected by the camera.
What should I do to detect the image captured by the camera only when needed?

Hi, I am not an expert. But you can try to remap that topic to something else when you don't want darknet_ros to detect object and when you want it to detect again remap the topic to the required one.
If it work or not, please comment down.

hello, I am also using TX2 to run Darknet_ros, in the makefile, I edited  GPU=1 OPENCV=1 CUDNN=1, combined with Yolov3.Weights ,FPS is only about 0.7, When I use Yolov2-tiny weights, FPS increases to about 3.8FPS.
I'm so confused, because I see on the Internet that yolov2-Tiny can reach 20+ FPS. Is my TX2 configuration wrong? When I run "sudo jetson_release", output the following:

NVIDIA Jetson TX2

Jetpack 3.0 [L4T 27.1.0]
NV Power Mode: MAXN - Type: 0
jetson_stats.service: active

Libraries:

CUDA: 8.0.64
cuDNN: 5.1.10
TensorRT: NOT_INSTALLED
Visionworks: <IP_ADDRESS>n
OpenCV: 3.3.0 compiled CUDA: YES
VPI: NOT_INSTALLED
Vulkan:
Is there a problem here? Could it be the version that caused the problem?

Can you tell me how your CUDNN is configured and whether this path exists in your files
My /usr folder does not have this path"/usr/local/cudnn/". Is this correct? In the /usr/local/cuda/include ,I can find cudnn.h, in the /usr/local/cuda/lib64/ ,I can find some file like "libcudnn.so"
This problem has been bothering me for many days, and I hope to get your guidance, Thank you! @willzoe

After using SDK Manager to configure TX2, I haven't configured cuDNN again.
The FPS is very slow may be because the input video resolution is too high. You can try to adjust the resolution of the input image to 640480 or 1280720.


pip auto versioning strategy makes invalid assumptions

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
pip
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
As first noted in https://github.com/dependabot/dependabot-core/issues/6625#issuecomment-1424194477, I think the reasoning on which versioning strategy to use for Python packages when not configured explicitly is not sound. I promised then I'd give it some thought and report back.
Current behavior
The current implementation tries to differentiate between a Python application and a Python library. For an application, it uses the increase strategy, while for a library it uses widen. I think I get the reasoning behind this decision, and if I understand correctly it's a general dependabot approach, regardless of the package manager. So I have no issues with this approach per se. I do however think that the deciding factors in the current implementation for what makes an application versus a library are flawed, and err on the side of conflicts.
The deciding factors as I understand them are the following: if the package has a pyproject.toml and it has ever been published to PyPi, it's a library. Otherwise it's an application (see https://github.com/dependabot/dependabot-core/commit/4dc71870ea8a05699d229a5fc05a143f372bf63c). I believe this leads to both false positives and false negatives. I'm especially concerned about many libraries being labeled applications. The consequences of this are currently limited due to a bug that happens to mitigate the difference (#6519, #6631) but if I understand the bump process correctly, it will change the bumping behavior on a lot of projects when this bug is fixed.
Where it falls short
I'm not a Python or dependency management expert by far, but I have gathered quite some experience with it and I think I understand the ecosystem pretty well. So while I don't have many references I believe most of what I say below applies to the Python ecosystem in general. My objections with this approach are the following:

The presence of a pyproject.toml file has nothing to do with a package being a library or an application. It is just one of the potential metadata files for Python projects, and with PEP518 I expect it will gain a lot of traction, both for applications and for libraries. Always labeling projects without this file an application is therefore incorrect.
PyPi is just a Python package index. Private libraries might not be published there, and public applications probably are published there. Furthermore, anyone can upload a package to PyPi if the name is not yet in use, so even private applications may have a namesake on PyPi, published by someone else. A package being on PyPi therefore has nothing to do with it being a library or an application.
While I see the use case for the increase strategy for applications, I don't think it's as important as the opposite: libraries will be used by many projects, together with many other libraries. Each of these libraries may have some constraints on their dependencies to ensure proper functionality. These constraints should generally be as loose as possible to keep the risk of dependency conflicts low. A lower bound on a dependency constraint should generally be due to an incompatibility with lower versions. The current approach, as indicated above, has both false positives and false negatives. Therefore, it will apply the widen strategy to some applications and the increase strategy to some (many) libraries. The first could be considered unfortunate (and even that is subjective), the second should in my opinion be considered a real issue. Therefore, in case of doubt, widen is the sane fallback, not increase.

Proposed solution
To summarize, I think the main concern is that ideally, all libraries should be bumped with the widen strategy. The secondary constraint is that we make a best effort to identify applications and apply the increase strategy to them. This to be in line with the documentation and what seems to be dependabot's general approach.
Alas, as far as I know, there is no reliable way to differentiate Python libraries and applications. The best I can think of would be to use the presence of one or more entry points (excluding plugins) as the deciding factor. It is still far from perfect: some packages may be both a library and an application, in which case widen would be appropriate, but it would have an entry point defined. It is however far more accurate than the current approach. The alternative would be to not even try, and just default to widen always. I actually believe that would be both the sanest approach (even though it breaks slightly with the general documentation of auto) as well as the least breaking: increase has been bugged to behave like widen, so with backwards compatibility in mind it could make sense to stick to the same behavior as a default (but use the proper name).
Conclusion
In summary, I can't think of a reliable way to tell the difference between an application and a library. Considering the importance of flexible constraints for libraries, and the lack of a strong motivation for strong constraints for applications, I would propose to just always default to widen. If this is not acceptable, the most accurate (though still flawed) metric I can think of would be the presence of entry points.
I'd be interested to hear your thoughts on this.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

Hi, glad to hear you're going to follow this up with the team, I'll be interested to hear what you conclude.
I agree with your summary. I still think #6630 would be a nice-to-have to be able to specify the strategy explicitly. It could provide a bit more stability if the semantics of auto would ever change. But I agree it becomes way less urgent if auto comes to mean widen.

Sure, I'll keep you posted.
Just to have all the options clear. What do "entry points" look like exactly on Python applications? Do you mean particular files for detecting applications using specific frameworks (say, for example, a root manage.py file for Django projects?)?

I was referring to entry points as defined in the setuptools documentation. They declare cli commands or GUI scripts (for which binaries are created at installation iirc).
But I must confess that I didn't take other types of applications into account at all (e.g. Django). I have no experience with them so I forgot to account for them. I just had a very quick look at Django specifically, and it doesn't seem to use entry points. If I understand correctly the application is always started by invoking python manage.py. So I think using entry points as a metric like I proposed is probably quite naive, and while I still think it would be better than the current scenario, it would identify a (presumably large) class of applications (e.g. Django) as libraries.

I was referring to entry points as defined in the setuptools documentation. They declare cli commands or GUI scripts (for which binaries are created at installation iirc).

Oh alright! I'll read a bit more about that but from a quick scan, I agree it's not ideal since some libraries would be detected as applications. At least in the Ruby world, many libraries also provide some kind of CLI.

I assumed that to be quite rare, but I have no statistics on it so I could be wrong about that. And it's definitely not unheard of. This is the main reason I'd personally be in favor of just using widen for auto. The entry points suggestion was more of a best-effort in case you really wanted to keep some sort of application vs library discovery.

Entry points are a generic plugin / extensibility mecanism: https://packaging.python.org/en/latest/specifications/entry-points/
They are used by applications and libraries.


download file splitted into seperate file slower than 1 large file

Description
when downloading a huge file (>1M) as a CSV and checking "split output file" fetching data is much slower than without this option checked.
DBeaver Version
Community, 23.3.3
Operating System
Windows
Database and driver
Postgres
Steps to reproduce
No response
Additional context
No response

cannot reproduce against PostgreSQL (26 Mb filesize)

@JeroenNienhuis Hi, if you are writing multiple files, this can sometimes be slower if you have an HDD. It writes slower for multiple files than for one large file.


WebSocket improvements: Haproxy support for hixie76

In order to get Hixie76 through a HAProxy loadbalancer the server must send response headers before the request nonce is received. In other words: before haproxy will send extra data from the client it expects the server to respond to the header. Current cowboy implementation does not support that. Example (nc localhost 8080 and paste):
GET /echo/000/afc7f9ea-5b6f-4c94-bc2e-4fe7f5a74241/websocket HTTP/1.1
Host: localhost:8080
Accept-Encoding: identity
Origin: http://localhost:8080
Connection: Upgrade
Upgrade: WebSocket
Sec-WebSocket-Key2: 12998 5 Y3 1  .P00
Sec-WebSocket-Key1: 4 @1  46546xW%0l 1 5

Result: cowboy waits.
Expected result: response headers.
How to trigger expected result: type eight more bytes and press enter.

Thanks for the report! Can you make one bug report per issue though? It'll be easier to discuss them.

Thanks.
Yes hixie-76 is a huge problem for proxies. Not sure how much I should send back at that point though? How are the other websocket implementations doing here?

I'm not talking about proxies. I'm talking about haproxy loadbalancer. Other implementations are mostly ignoring the problem and do not work behind loadbalancers.
Relevant discussion: https://github.com/miksago/node-websocket-server/issues/29

Fix for HAProxy? No change is needed to HAProxy. The WebSocket server that sits behind HAProxy needs only send the 101 response before receiving the binary nonce from the client. HAProxy will go ahead and forward the binary nonce upstream once the 101 response has validated that the server wishes to receive it, and then your WebSocket server can generate and transmit the rest of the handshake response.

So, don't wait for nonce, send 101 back just after request headers were received and then block and wait for nonce.

Haproxy is a proxy by all meaning of the term. :)
But yeah if sending the Status-line is all that's needed it should be an easy change. I'll do that one this week.

I would say status line and the headers, but that needs investigating.

Can't send all the headers though, we can't calculate the key.

In hixie76 there is no key in headers. The nonce is returned after the headers src:

GET /demo HTTP/1.1
Upgrade: WebSocket
Connection: Upgrade
Host: example.com
Origin: http://example.com
Sec-WebSocket-Key1: 4 @1  46546xW%0l 1 5
Sec-WebSocket-Key2: 12998 5 Y3 1  .P00

^n:ds[4U

HTTP/1.1 101 WebSocket Protocol Handshake
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Origin: http://example.com
Sec-WebSocket-Location: ws://example.com/demo
Sec-WebSocket-Protocol: sample

8jKS'y:G*Co,Wxa-

Oh right. Then it's not a problem. It'll even be a little cleaner to do it like this.

Should be done in 70d28ff64d107eb04903779573a4c6b4df18fdfa. Tell me if that works for you.

Works fine. Thanks.  One comment: on timeout, when headers were given but not nonce yet,  an error appears:
=ERROR REPORT==== 20-Oct-2011::13:45:23 ===
Error in process <0.1339.0> with exit value: {{badmatch,{error,timeout}},[{cowboy_http_websocket,websocket_handshake,3}]}

I'm not sure what should happen in such case. Is this error desired?

It's not undesired. A proper error should probably be sent instead, but there's other points where the handshake can fail by crashing so I suppose we can take a look at that later, unless there's an implementation having an issue.
I'm doing things on an implementation basis for websocket code at the moment, until the drafts get completed.

If something else goes bad open a new ticket, thanks.


Temporary Commit

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Current dependencies on/for this PR:

master

PR #4   👈

This stack of pull requests is managed by Graphite.


Create a multi-architecture jar

Have you thought about creating a multi-architecture jar and at init time look at the current architecture and load that native library?
zstd-jni and lz4-java do this. This turns it into one big jar instead of several jars. This in turn simplifies releases of applications that use jbrotli.
For the furture, for unsupported platforms, we could use the java decoder implementation that has surfaced in the brotli repo. Would be a nice fallback.

+1 for it.
And also can we have brotli packaged as a static lib? Just like netty-tcnative-boringssl-static (http://netty.io/wiki/forked-tomcat-native.html), so we do not have to worry about platform library versions.


Fix for displaying char* and char** values

changing to var-list-children to use --all-values. lldb treats any object
with children as not simple, and therefore will not show values when
passing --simple-values as the parameter.

@edumunoz @jacdavis @gregg-miskelly


Use offical blessed package to control the version(700)

This PR follows the instruction to manage the version of Cromwell-tools. This will be not only necessary for Lira's /version endpoint but also important to maintain the versions of all of our dependencies.
So in other applications, we can now get the version by:
import cromwell_tools

cromwell_tools.__version__

And we don't need to update the setup.py manually anymore, it will automatically grab the right git tag.
Please ensure the following when opening a PR:

[ ] Added or updated tests
[ ] Updated documentation
[ ] Applied style guidelines
[x] Considered generalizability beyond our own use case

Rebased and addressed the comments, will merge it.


Add noise monitoring app

Prior art:

https://publicmap.github.io/noiselogger/

Next actions:

Decide if this should be integrated within the 3d map or should be a separate page

cc @marlonrodrigues

would be useful add it as a layer to the base map. can envision 10+ layers and user may want to overlay several to get more insights

posted to /sound as a standalone map not integrated into the core map


Upgrade docker to rocm 4.1 and drop hcc

Are the source code changes related to dropping hcc?

No, they are related to new warnings in clang tidy.


TBI - Add onClick method to UIActionCallout

Description (include screenshots)
Under the current implement of UIActionCallout the commandAction is used to open extensions in VSCode or open the link in the broswer.
In addition to this, it would be valuable to have a callback in order to track when the click is event is fire in all cases. The proposal is to add an onClick method.
Value
onClick method contains a callback (can be used to track telemetry events for example)
Architecture Elaboration
No
Notes
Tasks

[ ] Add onClick method to UIActionCallout

@cianmSAP The proposed fix is a little confusing (having a flag to prevent multiple click events), can we investigate using stopPropogation as that is its intended use. Also it would be useful to pass the action detail in the click callback if available for consumers.


[FLINK-12293][docs, datastream]Fix some comment typos in flink-streaming-java.

What is the purpose of the change
This PR is related to FLINK-12293. Fix some comment typos.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

@dawidwys Thanks for your comments, I have resolved them, please have a look.

Thank you for opening this PR to Flink. I would like to close this pull request, without merging it, as it does not substantially improve Flink.
Some of the fixed typos are indeed valid, while others are questionable. Still, these typos do not hurt any user experience (as the APIs are not user facing), nor do they make it harder to understand the APIs itself.
I'm sure we would converge to a state (after a few rounds of reviews) where this change is acceptable, but then we would have spend a lot of valuable committer/contributor time on a change not raising the bar for Flink.

@rmetzger Thanks for replying, I have closed this PR.


Unable to use manyfold-solo

Describe the bug
I've never used Manyfold before, so decided to start with the "solo" image. It looks like everything starts, but when I go to the browser it redirects to "users/sign_in", then I get the message:
We're sorry, but something went wrong.
If you are the application owner check the logs for more information.

Pasting the logs down below.
To Reproduce
Steps to reproduce the behavior:

Start docker-compose
Go to web browser

Expected behavior
App should work.
Screenshots
Described above.
Desktop (please complete the following information):
Not applicable.
Smartphone (please complete the following information):
Not applicable.
Additional context
Raspberry Pi 4
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 12 (bookworm)
Release:	12
Codename:	bookworm

docker-compose logs
manyfold_1       | s6-rc: info: service s6rc-oneshot-runner: starting
manyfold_1       | s6-rc: info: service s6rc-oneshot-runner successfully started
manyfold_1       | s6-rc: info: service fix-attrs: starting
manyfold_1       | s6-rc: info: service fix-attrs successfully started
manyfold_1       | s6-rc: info: service legacy-cont-init: starting
manyfold_1       | s6-rc: info: service legacy-cont-init successfully started
manyfold_1       | s6-rc: info: service redis: starting
manyfold_1       | s6-rc: info: service redis successfully started
manyfold_1       | s6-rc: info: service manyfold: starting
manyfold_1       | s6-rc: info: service manyfold successfully started
manyfold_1       | s6-rc: info: service legacy-services: starting
manyfold_1       | 54:C 12 Jul 2024 22:48:40.217 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
manyfold_1       | 54:C 12 Jul 2024 22:48:40.217 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=54, just started
manyfold_1       | 54:C 12 Jul 2024 22:48:40.217 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
manyfold_1       | 54:M 12 Jul 2024 22:48:40.219 * monotonic clock: POSIX clock_gettime
manyfold_1       | 54:M 12 Jul 2024 22:48:40.222 * Running mode=standalone, port=6379.
manyfold_1       | 54:M 12 Jul 2024 22:48:40.222 # Server initialized
manyfold_1       | 54:M 12 Jul 2024 22:48:40.222 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
manyfold_1       | 54:M 12 Jul 2024 22:48:40.226 * Ready to accept connections
manyfold_1       | Preparing database...
manyfold_1       | s6-rc: info: service legacy-services successfully started
manyfold_1       | Illegal option -p
manyfold_1       | sh: lspci: not found
manyfold_1       | Illegal option -p
manyfold_1       | sh: lspci: not found
manyfold_1       | Cleaning up old cache files...
manyfold_1       | Illegal option -p
manyfold_1       | sh: lspci: not found
manyfold_1       | Illegal option -p
manyfold_1       | sh: lspci: not found
manyfold_1       | Setting temporary directory permissions...
manyfold_1       | Launching application...
manyfold_1       | 22:48:56 rails.1              | started with pid 117
manyfold_1       | 22:48:56 default_worker.1     | started with pid 118
manyfold_1       | 22:48:56 performance_worker.1 | started with pid 119
manyfold_1       | 22:49:08 performance_worker.1 | Illegal option -p
manyfold_1       | 22:49:08 default_worker.1     | Illegal option -p
manyfold_1       | 22:49:08 default_worker.1     | sh: lspci: not found
manyfold_1       | 22:49:08 performance_worker.1 | sh: lspci: not found
manyfold_1       | 22:49:08 performance_worker.1 | Illegal option -p
manyfold_1       | 22:49:08 default_worker.1     | Illegal option -p
manyfold_1       | 22:49:08 performance_worker.1 | sh: lspci: not found
manyfold_1       | 22:49:08 default_worker.1     | sh: lspci: not found
manyfold_1       | 22:49:08 rails.1              | Illegal option -p
manyfold_1       | 22:49:08 rails.1              | sh: lspci: not found
manyfold_1       | 22:49:08 rails.1              | Illegal option -p
manyfold_1       | 22:49:08 rails.1              | sh: lspci: not found
manyfold_1       | 22:49:12 rails.1              | => Booting Puma
manyfold_1       | 22:49:12 rails.1              | => Rails <IP_ADDRESS> application starting in production
manyfold_1       | 22:49:12 rails.1              | => Run `bin/rails server --help` for more startup options
manyfold_1       | 22:49:19 performance_worker.1 | 2024-07-12T22:49:19.738Z pid=119 tid=h5b WARN: Scoped order is ignored, it's forced to be batch order.
manyfold_1       | 22:49:19 default_worker.1     | 2024-07-12T22:49:19.844Z pid=118 tid=h5a WARN: Scoped order is ignored, it's forced to be batch order.
manyfold_1       | 22:49:20 performance_worker.1 | 2024-07-12T22:49:20.264Z pid=119 tid=h5b INFO: Booted Rails <IP_ADDRESS> application in production environment
manyfold_1       | 22:49:20 performance_worker.1 | 2024-07-12T22:49:20.264Z pid=119 tid=h5b INFO: Running in ruby 3.3.1 (2024-04-23 revision c56cd86388) [aarch64-linux-musl]
manyfold_1       | 22:49:20 performance_worker.1 | 2024-07-12T22:49:20.264Z pid=119 tid=h5b INFO: See LICENSE and the LGPL-3.0 for licensing details.
manyfold_1       | 22:49:20 performance_worker.1 | 2024-07-12T22:49:20.264Z pid=119 tid=h5b INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
manyfold_1       | 22:49:20 performance_worker.1 | 2024-07-12T22:49:20.272Z pid=119 tid=h5b INFO: Sidekiq 7.3.0 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>"redis://localhost:6379"}
manyfold_1       | 22:49:20 performance_worker.1 | 2024-07-12T22:49:20.299Z pid=119 tid=h5b INFO: Sidekiq 7.3.0 connecting to Redis with options {:size=>1, :pool_name=>"default", :url=>"redis://localhost:6379"}
manyfold_1       | 22:49:20 default_worker.1     | 2024-07-12T22:49:20.422Z pid=118 tid=h5a INFO: Booted Rails <IP_ADDRESS> application in production environment
manyfold_1       | 22:49:20 default_worker.1     | 2024-07-12T22:49:20.422Z pid=118 tid=h5a INFO: Running in ruby 3.3.1 (2024-04-23 revision c56cd86388) [aarch64-linux-musl]
manyfold_1       | 22:49:20 default_worker.1     | 2024-07-12T22:49:20.422Z pid=118 tid=h5a INFO: See LICENSE and the LGPL-3.0 for licensing details.
manyfold_1       | 22:49:20 default_worker.1     | 2024-07-12T22:49:20.422Z pid=118 tid=h5a INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
manyfold_1       | 22:49:20 default_worker.1     | 2024-07-12T22:49:20.423Z pid=118 tid=h5a INFO: Sidekiq 7.3.0 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>"redis://localhost:6379"}
manyfold_1       | 22:49:20 default_worker.1     | 2024-07-12T22:49:20.450Z pid=118 tid=h5a INFO: Sidekiq 7.3.0 connecting to Redis with options {:size=>4, :pool_name=>"default", :url=>"redis://localhost:6379"}
manyfold_1       | 22:49:20 rails.1              | [117] Puma starting in cluster mode...
manyfold_1       | 22:49:20 rails.1              | [117] * Puma version: 6.4.2 (ruby 3.3.1-p55) ("The Eagle of Durango")
manyfold_1       | 22:49:20 rails.1              | [117] *  Min threads: 4
manyfold_1       | 22:49:20 rails.1              | [117] *  Max threads: 16
manyfold_1       | 22:49:20 rails.1              | [117] *  Environment: production
manyfold_1       | 22:49:20 rails.1              | [117] *   Master PID: 117
manyfold_1       | 22:49:20 rails.1              | [117] *      Workers: 4
manyfold_1       | 22:49:20 rails.1              | [117] *     Restarts: (✔) hot (✖) phased
manyfold_1       | 22:49:20 rails.1              | [117] * Preloading application
manyfold_1       | 22:49:20 rails.1              | [117] * Listening on http://<IP_ADDRESS>:3214
manyfold_1       | 22:49:20 rails.1              | [117] Use Ctrl-C to stop
manyfold_1       | 22:49:20 rails.1              | [117] - Worker 0 (PID: 179) booted in 0.06s, phase: 0
manyfold_1       | 22:49:20 rails.1              | [117] - Worker 1 (PID: 187) booted in 0.05s, phase: 0
manyfold_1       | 22:49:20 rails.1              | [117] - Worker 2 (PID: 193) booted in 0.03s, phase: 0
manyfold_1       | 22:49:20 rails.1              | [117] - Worker 3 (PID: 207) booted in 0.02s, phase: 0
manyfold_1       | 22:49:20 performance_worker.1 | 2024-07-12T22:49:20.833Z pid=119 tid=h5b INFO: Loading Schedule
manyfold_1       | 22:49:20 performance_worker.1 | 2024-07-12T22:49:20.834Z pid=119 tid=h5b INFO: Schedule empty! Set Sidekiq.schedule
manyfold_1       | 22:49:20 performance_worker.1 | 2024-07-12T22:49:20.835Z pid=119 tid=h5b INFO: Schedules Loaded
manyfold_1       | 22:49:20 default_worker.1     | 2024-07-12T22:49:20.944Z pid=118 tid=h5a INFO: Loading Schedule
manyfold_1       | 22:49:20 default_worker.1     | 2024-07-12T22:49:20.947Z pid=118 tid=h5a INFO: Schedule empty! Set Sidekiq.schedule
manyfold_1       | 22:49:20 default_worker.1     | 2024-07-12T22:49:20.948Z pid=118 tid=h5a INFO: Schedules Loaded

Then when I try to open in the browser:
manyfold_1       | 22:49:28 rails.1              | 2024-07-12T22:49:28.170Z pid=187 tid=113r INFO: Sidekiq 7.3.0 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>"redis://localhost:6379"}

Thanks, that's certainly not right! I'll see if I can reproduce the problem here. Have you just used the docker-compose example, or have you added any other configuration?

I just tried the solo container as well and get the same error. Everything is setup according to the docker-compose example.
/package/admin/s6-overlay/libexec/preinit: info: read-only root /package/admin/s6-overlay/libexec/preinit: info: writable /run. Checking for executability. /package/admin/s6-overlay/libexec/preinit: warning: unable to find /run in /proc/mounts, check that your container manager pre-mounts /proc, and that /run is a tmpfs. The container is likely to crash soon, if /run is (incorrectly) mounted noexec. s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service redis: starting s6-rc: info: service redis successfully started s6-rc: info: service manyfold: starting s6-rc: info: service manyfold successfully started s6-rc: info: service legacy-services: starting Preparing database... s6-rc: info: service legacy-services successfully started 54:C 13 Jul 2024 19:47:32.404 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 54:C 13 Jul 2024 19:47:32.404 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=54, just started 54:C 13 Jul 2024 19:47:32.404 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf 54:M 13 Jul 2024 19:47:32.404 * monotonic clock: POSIX clock_gettime 54:M 13 Jul 2024 19:47:32.405 * Running mode=standalone, port=6379. 54:M 13 Jul 2024 19:47:32.405 # Server initialized 54:M 13 Jul 2024 19:47:32.405 * Ready to accept connections Illegal option -p sh: lspci: not found Illegal option -p sh: lspci: not found Cleaning up old cache files... Illegal option -p sh: lspci: not found Illegal option -p sh: lspci: not found Setting temporary directory permissions... Launching application... 19:47:38 rails.1              | started with pid 115 19:47:38 default_worker.1     | started with pid 116 19:47:38 performance_worker.1 | started with pid 117 19:47:42 rails.1              | Illegal option -p 19:47:42 default_worker.1     | Illegal option -p 19:47:42 performance_worker.1 | Illegal option -p 19:47:42 rails.1              | sh: lspci: not found 19:47:42 default_worker.1     | sh: lspci: not found 19:47:42 performance_worker.1 | sh: lspci: not found 19:47:42 rails.1              | Illegal option -p 19:47:42 default_worker.1     | Illegal option -p 19:47:42 performance_worker.1 | Illegal option -p 19:47:42 rails.1              | sh: lspci: not found 19:47:42 default_worker.1     | sh: lspci: not found 19:47:42 performance_worker.1 | sh: lspci: not found 19:47:43 rails.1              | => Booting Puma 19:47:43 rails.1              | => Rails <IP_ADDRESS> application starting in production 19:47:43 rails.1              | => Run bin/rails server --help for more startup options 19:47:45 default_worker.1     | 2024-07-13T19:47:45.392Z pid=116 tid=h5c WARN: Scoped order is ignored, it's forced to be batch order. 19:47:45 performance_worker.1 | 2024-07-13T19:47:45.419Z pid=117 tid=h5d WARN: Scoped order is ignored, it's forced to be batch order. 19:47:45 default_worker.1     | 2024-07-13T19:47:45.445Z pid=116 tid=h5c INFO: Booted Rails <IP_ADDRESS> application in production environment 19:47:45 default_worker.1     | 2024-07-13T19:47:45.445Z pid=116 tid=h5c INFO: Running in ruby 3.3.1 (2024-04-23 revision c56cd86388) [x86_64-linux-musl] 19:47:45 default_worker.1     | 2024-07-13T19:47:45.445Z pid=116 tid=h5c INFO: See LICENSE and the LGPL-3.0 for licensing details. 19:47:45 default_worker.1     | 2024-07-13T19:47:45.445Z pid=116 tid=h5c INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org 19:47:45 default_worker.1     | 2024-07-13T19:47:45.445Z pid=116 tid=h5c INFO: Sidekiq 7.3.0 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>"redis://localhost:6379"} 19:47:45 default_worker.1     | 2024-07-13T19:47:45.447Z pid=116 tid=h5c INFO: Sidekiq 7.3.0 connecting to Redis with options {:size=>4, :pool_name=>"default", :url=>"redis://localhost:6379"} 19:47:45 performance_worker.1 | 2024-07-13T19:47:45.512Z pid=117 tid=h5d INFO: Booted Rails <IP_ADDRESS> application in production environment 19:47:45 performance_worker.1 | 2024-07-13T19:47:45.512Z pid=117 tid=h5d INFO: Running in ruby 3.3.1 (2024-04-23 revision c56cd86388) [x86_64-linux-musl] 19:47:45 performance_worker.1 | 2024-07-13T19:47:45.512Z pid=117 tid=h5d INFO: See LICENSE and the LGPL-3.0 for licensing details. 19:47:45 performance_worker.1 | 2024-07-13T19:47:45.512Z pid=117 tid=h5d INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org 19:47:45 performance_worker.1 | 2024-07-13T19:47:45.512Z pid=117 tid=h5d INFO: Sidekiq 7.3.0 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>"redis://localhost:6379"} 19:47:45 performance_worker.1 | 2024-07-13T19:47:45.520Z pid=117 tid=h5d INFO: Sidekiq 7.3.0 connecting to Redis with options {:size=>1, :pool_name=>"default", :url=>"redis://localhost:6379"} 19:47:45 rails.1              | [115] Puma starting in cluster mode... 19:47:45 rails.1              | [115] * Puma version: 6.4.2 (ruby 3.3.1-p55) ("The Eagle of Durango") 19:47:45 rails.1              | [115] *  Min threads: 4 19:47:45 rails.1              | [115] *  Max threads: 16 19:47:45 rails.1              | [115] *  Environment: production 19:47:45 rails.1              | [115] *   Master PID: 115 19:47:45 rails.1              | [115] *      Workers: 4 19:47:45 rails.1              | [115] *     Restarts: (✔) hot (✖) phased 19:47:45 rails.1              | [115] * Preloading application 19:47:45 rails.1              | [115] * Listening on http://<IP_ADDRESS>:3214 19:47:45 rails.1              | [115] Use Ctrl-C to stop 19:47:45 rails.1              | [115] - Worker 0 (PID: 177) booted in 0.02s, phase: 0 19:47:45 rails.1              | [115] - Worker 1 (PID: 185) booted in 0.01s, phase: 0 19:47:45 rails.1              | [115] - Worker 2 (PID: 203) booted in 0.01s, phase: 0 19:47:45 rails.1              | [115] - Worker 3 (PID: 216) booted in 0.0s, phase: 0 19:47:45 default_worker.1     | 2024-07-13T19:47:45.639Z pid=116 tid=h5c INFO: Loading Schedule 19:47:45 default_worker.1     | 2024-07-13T19:47:45.640Z pid=116 tid=h5c INFO: Schedule empty! Set Sidekiq.schedule 19:47:45 default_worker.1     | 2024-07-13T19:47:45.640Z pid=116 tid=h5c INFO: Schedules Loaded 19:47:45 performance_worker.1 | 2024-07-13T19:47:45.746Z pid=117 tid=h5d INFO: Loading Schedule 19:47:45 performance_worker.1 | 2024-07-13T19:47:45.747Z pid=117 tid=h5d INFO: Schedule empty! Set Sidekiq.schedule 19:47:45 performance_worker.1 | 2024-07-13T19:47:45.747Z pid=117 tid=h5d INFO: Schedules Loaded

Thanks, that's certainly not right! I'll see if I can reproduce the problem here. Have you just used the docker-compose example, or have you added any other configuration?

I just copy/paste the docker-compose file from the documentation.

Thanks - those logs look sensible, but obviously something's going wrong. Can you try to docker exec -it manyfold cat /usr/src/app/log/production.log and see if there's any errors in there? They should be appearing in the docker log, but they might not be...

W, [2024-07-13T23:25:39.984775 #72]  WARN -- : You are running SQLite in production, this is generally not recommended. You can disable this warning by setting "config.active_record.sqlite3_production_warning=false".
W, [2024-07-13T23:25:40.577458 #72]  WARN -- : Scoped order is ignored, it's forced to be batch order.
W, [2024-07-13T23:26:05.967850 #120]  WARN -- : You are running SQLite in production, this is generally not recommended. You can disable this warning by setting "config.active_record.sqlite3_production_warning=false".
W, [2024-07-13T23:26:05.967911 #119]  WARN -- : You are running SQLite in production, this is generally not recommended. You can disable this warning by setting "config.active_record.sqlite3_production_warning=false".
W, [2024-07-13T23:26:05.968957 #118]  WARN -- : You are running SQLite in production, this is generally not recommended. You can disable this warning by setting "config.active_record.sqlite3_production_warning=false".
W, [2024-07-13T23:26:12.039351 #120]  WARN -- : Scoped order is ignored, it's forced to be batch order.
W, [2024-07-13T23:26:12.059299 #119]  WARN -- : Scoped order is ignored, it's forced to be batch order.
W, [2024-07-13T23:26:12.189040 #118]  WARN -- : Scoped order is ignored, it's forced to be batch order.
I, [2024-07-13T23:26:21.790690 #207]  INFO -- : [71a7c2df-fc85-4227-b4a1-86dd8f1d88d1] {"method":"GET","path":"/users/sign_in","format":"html","controller":"Users::SessionsController","action":"new","status":500,"allocations":21959,"duration":629.42,"view":0.0,"db":11.15,"@timestamp":"2024-07-13T23:26:21.789Z","@version":"1","message":"[500] GET /users/sign_in (Users::SessionsController#new)"}
F, [2024-07-13T23:26:21.792129 #207] FATAL -- : [71a7c2df-fc85-4227-b4a1-86dd8f1d88d1]
[71a7c2df-fc85-4227-b4a1-86dd8f1d88d1] ActiveRecord::StatementInvalid (SQLite3::ReadOnlyException: attempt to write a readonly database):
[71a7c2df-fc85-4227-b4a1-86dd8f1d88d1]

I think i had the same problem and the problem was that the manyfold files in the config folder, i.e. the files:
manyfold.sqlite3
manyfold.sqlite3-shm
manyfold.sqlite3-wal
had "root" as owner, so i changed it to the correct user and after that the manyfold webpage would load correctly.

Manually changing the permissions is a way to fix it, but ideally it should
be fixed in the composer file, passing the right arguments. I just haven't
had time to sit down and look at it yet. 😞
Mauricio Teixeira
(sent from mobile, sorry for my brevity)
On Sun, Jul 14, 2024, 2:24 PM Lugnt @.***> wrote:

I think i had the same problem and the problem was that the manyfold files
in the config folder, i.e. the files:
manyfold.sqlite3
manyfold.sqlite3-shm
manyfold.sqlite3-wal
had "root" as owner, so i changed it to the correct user and after that
the manyfold webpage would load correctly.
—
Reply to this email directly, view it on GitHub
https://github.com/manyfold3d/manyfold/issues/2388#issuecomment-2227443284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAODBEE3GNXPOZXVOZCUR3TZMK67LAVCNFSM6AAAAABKZV46JOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXGQ2DGMRYGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I think I understand the problem. As soon as the container starts, I sh into it and see this:
root          58  0.0  0.0   1708   896 ?        Ss   20:27   0:00 sh ./run manyfold
root          67  0.0  0.0   1708  1024 ?        S    20:27   0:00 /bin/ash bin/docker-entrypoint.sh foreman start
root          69 97.9  1.4<PHONE_NUMBER>56 ?       Rl   20:27   0:12 /usr/local/bin/ruby bin/rails db:prepare:with_data

That's when the sqlite database gets created. After that it starts the application with PUID 1000, but then the database is owned by root.
If I am right about this, the solution would be to either initialize the database honoring the PUID (I don't know how) or running chown here.
My 2c.

some additional context, as the issue with the owner of the DB can also seemingly create problems in other areas: I installed manyfold-solo on unraid using the supplied xml; using PUID and PGID of a non-root user. Installation went fine, but on stat-up same error as OP happened. I then restarted the docker using PUID and PGID "0" (thinking "yea, on first startup ofc I would need an admin / root user to set everything up"), then on initial admin user creation in manyfold, I used my original non-root user. Reset PUID and PGID to the non-root user again (and also gave that user change permissions on the libraries and sqlite folder). Manyfold then started up fine, and I could import models; but when trying to add tags to files, same error appeared (I assume, that would also happened with everything else that would have needed permissions for the SQLite DB). After changing the owner of the DB in unraid, that seems to have been solved.
Suggestion: include some simple checks in the startup sequence making sure the user under which manyfold is running has all necessary rights to all needed files and folders.

Ah, great catch, yes, the databases is getting created as root and not chowned. Thank you. I'll get a fix out immediately.

I've just released v0.72.1 which fixes this problem - if you update, it should all work. Sorry about that!

Just wanted to confirm it works now.
The instructions about how the libraries are supposed to be created are a bit confusing, but I managed.
Thanks!


npx does not run binary from a GitHub repository

Describe the bug
npx github:chalk/chalk-cli green "Hello world" should pull and run chalk-cli from GitHub repo.
I'm not sure if this falls under this section of the FAQ, but it seems like this should work similar to running a binary from a github repo locally.
Locally, these all run the chalk-cli binary from GitHub:
npx chalk/chalk-cli green "Hello world"
npx github:chalk/chalk-cli green "Hello world"
npx https://github.com/chalk/chalk-cli green "Hello world"

Link to the blitz that caused the error
https://stackblitz.com/edit/http-server-f8vdap
To Reproduce
Steps to reproduce the behavior:

Go to https://stackblitz.com/edit/http-server-f8vdap
In the terminal, run npx chalk-cli green "Hello world"
See "Hello world" display in green
In the terminal, run npx github:chalk/chalk-cli green "Hello world"
See error

Expected behavior
npx should run binary from GitHub repo
Screenshots

Desktop (please complete the following information):

OS: MacOS High Sierra 10.13.6
Browser: Chrome
Version 90.0.4430.93 (Official Build) (x86_64)

Great project by the way 😄

Ah good find! Our npm client currently doesn't support pulling from git or any sources outside of the npm registry. Will take this back to the team and get this on the roadmap, thanks for letting us know (and for the kind words 🤗 )!

This now works correctly in Codeflow. We're probably not releasing the git binary for the classic editor, so closing this as solved.


Update http4s-circe, http4s-dsl, ... to 1.0.0-M32

Updates

org.http4s:http4s-circe
org.http4s:http4s-dsl
org.http4s:http4s-ember-client
org.http4s:http4s-ember-server

from 1.0.0-M23 to 1.0.0-M32.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Superseded by #155.


Question - is this project still being worked on by some developer advocate?

Haven't seen any commits in a long time, and I wonder if there are still plans to extend UAMP.

Yes 😃 https://github.com/android/uamp/commits/master


Fix for chained responses with newlines

This fixes the JSON decoder to handle chained responses which have newlines between the objects, such as for api.ping(...).

looks good!  Thanks.


update, restart and notification

It would be nice if when the server is rebooted or updated, messages about this would be written to the server itself. That a restart is expected or that it will be now. If possible
and also, it would be great to do server backups for example every 60 minutes and so on, as we ourselves indicate. Not only at the time of the start or update, but at intervals to save player data, a map, and so on. And accordingly limit the number of backups, for example, no more than 3 days, 7 days, and so on, so that you can specify.

I will see what i can do about notification.
Backups are already an option in windowgsm, not up to the plugin honestly, i will see if i can modify something to backup only the Saved folder.

I am also here for this to be a feature. and/or when an update happens it does a world save before running the update. to minimize roll back or loss of progress

Would love to see a scheduler for restarting with broadcasts in game etc, will owe you a beer :P


Prop to support Upload from Camera

Can we pass input props to open camera to take picture?

Mobile OS's already provide that feature automatically

Can we set default camera like capture="environment" ?


Update index.js

Solve #1

Hi !
Could you add some tests cases and squash your commits ?
Thank you very much for contributing !

It's done 👎
You're (not) the best 🥇

It's done 👎
You're (not) the best 🥇


Add rule - space around operator

This PR adds the space-around-operator rule. It has tests for both SCSS and Sass. There are numerous changes which will need to be implemented when we implement version 3 of gonzales-pe. These have been clearly noted for now.
Fixes #31
DCO 1.1 Signed-off-by: Ben Griffith<EMAIL_ADDRESS>

:+1: ready to go :shipit:


SAK-41485 Use server supplied new rubric title

https://jira.sakaiproject.org/browse/SAK-41485

Good work here!


Upgrade: Connection dashboard server with Server-Site Events

I checked the Network section from the web page and I saw some constant connections:

/api/players/online
/api/ping
/api/stats/

I propose the use of the Server-Site Events in order to send messages of "success" connections and other needed info.
I leave here the MDN documentation: https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events

I've never worked with SSE before, so I may need some time to get familiar with it. But if it helps reduce traffic, I think it's worth it. Also, thanks for all the feedback you have for this project, I really appreciate it! :)


Convert webflow example to use esnext modules

Description
This makes progress toward #15917 by converting @fluid-example/webflow to use esnext modules.
This is the most involved update of any of the packages that depend on @fluid-internal/test-version-utils, since ESNext modules don't support the require.extensions api (they don't support require), which was the technique used to make webpack-style CSS imports not blow up when run in a node environment. Instead, it's recommended to use the node esm loader API. Although this API is experimental, it hasn't receive any changes between v16.12 and the node latest (v20.x). I've written a very simple loader which is equivalent to ignore-styles to make tests work. We could consider devDepending on a package in the create-esm-loader family instead, if we want.

esm-loader-css has very few projects depending on it, but I looked through their code and it looks good. An alternative would be to define our own bare-bones loader:
const extensionsRegex = /\.css$/;

/**
 * This uses the node loader API (see https://nodejs.org/docs/latest-v16.x/api/esm.html#loaders)
 * to enable webpack-style imports of .css modules.
 *
 * This is the recommended successor to `require.extensions`, which was used by https://www.npmjs.com/package/ignore-styles
 * to accomplish the same thing.
 */
export async function load(url, context, nextLoad) {
	if (extensionsRegex.test(url)) {
		return {
			format: "json",
			shortCircuit: true,
			source: "{}",
		};
	}

	// Defer to the next hook in the chain.
	return nextLoad(url, context);
}

but this seems like it'd have more maintenance burden and doesn't handle edge cases as well (e.g. the fact that the loader api changed in 16.12).

I was going to leave a comment about using --experimental-loader, but it seems like you did your due-diligence there. I don't know how much we gain from using esm-loader-css. If the API changes and the package is unmaintained, don't we end up in the same situation as using our own implementation?

Perhaps, but the package already does better than writing our own loader in 2 cases:

It works on node before 16.12 (we technically don't support this by our "engines" config, but I think most things in our repo work for any node 16, and I don't see a real reason to explicitly break that)
It's less code for us to maintain, and the approach scales better if we have other web examples we convert to esnext with .css imports and mocha tests--we'd otherwise need to move our own custom loader to some place we can reference it. Using esm-loader-css is just a matter of adding a devDep and some NODE_OPTIONS flags.


Remove numbering

Had a number with no content on a list, removed it.

Codecov Report

Merging #86 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #86   +/-   ##
=========================================
  Coverage     72.29%   72.29%
  Complexity      454      454
=========================================
  Files            79       79
  Lines          1462     1462
  Branches        151      151
=========================================
  Hits           1057     1057
  Misses          359      359
  Partials         46       46

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 ce52eff...1e4b561. Read the comment docs.


eval doc does not pass test

🐛 Describe the bug
https://github.com/pytorch/torchchat/pull/1383 enables run-docs evaluation to extract a test script from eval documentation,
to run evaluation script.  In turn, this extracts the command
python3 torchchat.py eval stories15M --tasks wikitext --limit 10

from the eval doc as a test to ensure that the doc is in fact correct.  This appears to be a correct use of eval to me, yet it fails when running as follows:
https://hud.pytorch.org/pr/pytorch/torchchat/1383#33154706429
2024-11-18T18:13:35.1710781Z + python3 torchchat.py eval stories15M --tasks wikitext --limit 10
2024-11-18T18:13:35.1711201Z NumExpr defaulting to 16 threads.
2024-11-18T18:13:35.1711531Z PyTorch version 2.6.0.dev20241002+cu121 available.
2024-11-18T18:13:35.1711768Z
2024-11-18T18:13:35.1711939Z Downloading builder script:   0% 0.00/5.67k [00:00<?, ?B/s]
2024-11-18T18:13:35.1712401Z Downloading builder script: 100% 5.67k/5.67k [00:00<00:00, 37.1MB/s]
2024-11-18T18:13:35.1712808Z Traceback (most recent call last):
2024-11-18T18:13:35.1713182Z   File "/pytorch/torchchat/torchchat.py", line 100, in <module>
2024-11-18T18:13:35.1713552Z     eval_main(args)
2024-11-18T18:13:35.1713905Z   File "/pytorch/torchchat/torchchat/usages/eval.py", line 238, in main
2024-11-18T18:13:35.1714340Z     builder_args = BuilderArgs.from_args(args)
2024-11-18T18:13:35.1714667Z                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-11-18T18:13:35.1715101Z   File "/pytorch/torchchat/torchchat/cli/builder.py", line 169, in from_args
2024-11-18T18:13:35.1715520Z     return cls(
2024-11-18T18:13:35.1715827Z     run_cmd_or_die(f"docker exec -t {container_name} /exec")
2024-11-18T18:13:35.1716580Z   File "/home/ec2-user/actions-runner/_work/torchchat/torchchat/test-infra/.github/scripts/run_with_env_secrets.py", line 39, in run_cmd_or_die
2024-11-18T18:13:35.1717388Z     raise RuntimeError(f"Command {cmd} failed with exit code {exit_code}")
2024-11-18T18:13:35.1718153Z RuntimeError: Command docker exec -t c2e4cff2805edb5848301b09ed712578d726414222642162007e0e16e7c48ba1 /exec failed with exit code 1
2024-11-18T18:13:35.1718786Z            ^^^^
2024-11-18T18:13:35.1719026Z   File "<string>", line 24, in __init__
2024-11-18T18:13:35.1719475Z   File "/pytorch/torchchat/torchchat/cli/builder.py", line 76, in __post_init__
2024-11-18T18:13:35.1719926Z     raise RuntimeError(
2024-11-18T18:13:35.1720431Z RuntimeError: need to specified a valid checkpoint path, checkpoint dir, gguf path, DSO path, or PTE path

Versions
github runner, environment as configured by pytorch test infra

@vmpuri Can you take a look?
Maybe the doc is outdated

Resolved by landing #1383


Un-ignore main KSymResolver test

The /proc/kallsyms virtual file is commonly available. However, depending on kernel configuration all symbols may be reported as 0 for regular users.
 Hence, enable the main KSymResolver test again.

Simple change; merging.


Set forceFetch to false by default, do all-or-nothing diffing

per this comment: https://github.com/apollostack/apollo-client/issues/82#issuecomment-207647987

Essentially, we should see which root queries we can resolve from the store, and for each one we either resolve the whole query from the client or send the whole thing to the server.
This already covers a good set of use cases for caching, and doesn't require us to implement any kind of feature detection for the server.


Tdigest post aggregator

can we merge quantiles_from_tdigestsketch and quantile_from_tdigestsketch  to 1 file? @jbguerraz WDYT?

can we merge quantiles_from_tdigestsketch and quantile_from_tdigestsketch  to 1 file? @jbguerraz WDYT?

I prefer to keep them separate...
because quantiles_from_tdigestsketch and quantile_from_tdigestsketch are two different post aggregators. The filename aligns with the query type in the druid document.
"type": "quantilesFromTDigestSketch",
and
"type"  : "quantileFromTDigestSketch",


Any plans to add redux support?

Hello @ammoto!
Yes, that's makes sense. I'll add this to roadmap.
Thanks for suggestion!

Any news related to this?

+1 here — Really looking forward to this!

Waiting for this feature

I tried to add redux but then get:
undefined is not an object (evaluating 'getPrototypeOf(sourceComponent)')

hoistNonReactStatics
    hoist-non-react-statics.cjs.js:40:52
withRkTheme
    rkThemeProvider.js:40:22
routeMapping
    routesBuilder.js:16:22
<unknown>
    routesBuilder.js:21:38
<unknown>
    routesBuilder.js:20:21
loadModuleImplementation
    require.js:214:12
<unknown>
    App.js:12
loadModuleImplementation
    require.js:214:12
<unknown>
    crna-entry.js:7:11
loadModuleImplementation
    require.js:214:12
guardedLoadModule
    require.js:141:45
global code
    <unknown file>:0

@numediaweb did you find a solution to get around this?

Any news related to this?
@numediaweb what your solution ?
thanks !

Hello all.
We decided to not add redux support because we don't want to push our users to use some specific state management solution.
This demo app is mostly about UI and you can add any state management approach you want.


Incorrect number of days

"When you select Usage metrics or the icon usage metrics icon. next to a dashboard or report, Power BI generates a pre-built report with usage metrics for that content for the last 90 days. "
The last 90 days is to the best of my knowledge incorrect.  Only the last 30 days are available via the Power Bi service, the Power API activity only returns that last 30 days. All reports which I have access to via a number of different clients only returns 30 days of history.
That said the Office 365 audit logs do return that the last 90 days. It should be noted that this history is not available via the end use of the Power BI Metrics User reports do not have access to those logs. Via the Power BI service. Nor to the best of my knowledge is that data surfaced by the dataset which support the Power BI Metrics User reports.
If I am incorrect, then can you let me know how to get the last 90 days of data in the power bi service, and via the the Power Restful API activity as this would be of significant benefit.
Robert

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

ID: 719feeea-d688-78bf-fef5-8b58c2fb047f
Version Independent ID: 78793fa4-e2e2-7113-3652-b1165ee92145
Content: Monitor report usage metrics - Power BI
Content Source: powerbi-docs/collaborate-share/service-usage-metrics.md
Service: powerbi
Sub-service: pbi-collaborate-share
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks for your comment, @rwlpf. This issue has been assigned to the doc author for review.

thanks for your comment @rwlpf! I'm checking with the product group. I note that it says 90 days on the usage metrics report itself.

Hi @rwlpf , I'm moving this issue to our work item backlog for better consideration and tracking, and closing it here in the meantime.


FOUNDRYUI-138 CI/CD enhancements -> v1-release

Add slack notifications, alpha and beta pre-release branches, and upload build artifacts to github
on merges, no longer upload coverage since it should be stored, add commitizen configuration in the root package.json

:tada: This PR is included in version 1.0.0-v1-release.4 :tada:
The release is available on:

npm package (@v1-release dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ci: Don't allow failure in ontology linting step

This was previously an allowed failure because it was failing on what we had checked in, now that it's no longer failing we can enforce it's checks going forward.

Ah, looks like this step became out-of-date while it was in this "allowed failure" state:
ERROR: /home/runner/work/RACK/RACK/assist/bin/check:13: user:main directory_files/2: file `'models/TurnstileSystem/src'' does not exist
Error: Process completed with exit code 2.

Will fix.

.................................. Summary ...................................
No issues found

:tada:


docs(installataion): add info about development on github codespaces

Motivation

https://github.com/facebook/docusaurus/issues/6865#issuecomment-1062930085

Have you read the Contributing Guidelines on pull requests?
Yes.
Related PRs

https://github.com/facebook/docusaurus/issues/6865

@facebook-github-bot recheck now.

@vedantmgoyal2009 The CLA bot updates the PR status automatically. It doesn't get triggered by anything.

I do not have any problem in moving it to CLI docs but am just putting my thoughts here.
I think there are a considerable number of developers on GitHub that uses and even provide support for development on Codespaces and .devcontainer files for more easy development. For instance, I can remember of Oh-my-posh (https://github.com/JanDeDobbeleer/oh-my-posh/blob/main/CONTRIBUTING.md#codespaces--devcontainer-development-environment)

Yes, but that's CONTRIBUTING, which is developer-facing, not user-facing.
We have a lot of casual users who don't use these toolchains—they have a text editor, Node and NPM, and that's it. We don't want to clutter the installation guide (and any introductory content) with these niche use-cases. So yes, moving to CLI docs is the most sensible.

I guess a section under "Advanced Guides" would make more sense?

No, because "advanced" is relative to users' understanding of our infrastructure, not relative to their toolchain's advancedness :)

Thank you🎉🎉


Release RC_Triangulum-2021-07-19

Staging
Release notes: https://github.com/DataBiosphere/duos-ui/releases/tag/staging_RC_Triangulum-2021-07-19
Deployment: https://duos.dsp-duos-staging.broadinstitute.org/
Production
Release notes: https://github.com/DataBiosphere/duos-ui/releases/tag/production_RC_Triangulum-2021-07-19
Deployment: https://duos.broadinstitute.org/
Important Changes

DUOS-1315: Significant reduction of tech debt
DUOS-1322: Improved efficiency of fetching institutions
DUOS-1338: Bug fix
DUOS-1339: Identify SOs better in DAR UI
DUOS-1340: Bug fix

Released 👍🏽


Add a data converter for SVT

Thank you for your contribution to the MindOCR repo.
Before submitting this PR, please make sure:

[x] You have read the Contributing Guidelines on pull requests
[x] Your code builds clean without any errors or warnings
[x] You are using approved terminology
[ ] You have added unit tests

Motivation
(Write your motivation for proposed changes here.)
Test Plan
(How should this PR be tested? Do you require special setup to run the test or repro the fixed bug?)
Related Issues and PRs
(Is this PR part of a group of changes? Link the other relevant PRs and Issues here. Use https://help.github.com/en/articles/closing-issues-using-keywords for help on GitHub syntax)

please solve the conflict.

please solve the conflict.

Done.


Suggestions about transcription enhancement

Is your feature request related to a problem? Please describe
Not a problem.
Describe the solution you'd like

Support more output format, such as vtt, srt, lrc etc.
Add adequate punctuation to the sentence.
Incorporate insanely-fast-whisper-api to speed up the transcription process.

Describe alternatives you've considered
Additional context

Thanks for your suggestion. Do you have an interest to contribute these enhancements?


Run  cargo fmt and enforce style using Travis CI

Is this actually checking everything?  This is a really small number of changes.  Also, this needs to be rebased.

Yeah, it seems it didn't check all of the files last time. This should be all now.

I fixed the broken build

This is fixed in #1449.


For consideration - Jog in Place Locomotion

I ported over as best as I can Neosparks' jog-in-place locomotion module to the OpenXR-Tools style.  Code can be found here: https://github.com/teddybear082/Godot_XR_JogInPlace_Locomotion

I think that it would also be good to have an option to use this for sprinting (i.e. walk with the joystick and jog in place to move faster). Just a thought.


Specify required fields for Mention and Emoji objects in TextMessageV2

Overview
Specification of required parameters for MentionSubstitutionObject and EmojiSubstitutionObject, and removal of unnecessary whitespace.
Changes

MentionSubstitutionObject

Made mentionee a required parameter.

EmojiSubstitutionObject

Made productId and emojiId required parameters.

Reference:

LINE Developers - Text message (v2)

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

@nanato12 Thank you for your contribution!
Could you please agree to our Contributor License Agreement?


Add x86_64-unknown-linux-musl binary release

I can confirm that it compiles for Linux musl target.
Closes #391

Looks good! I'll do a beta release to make sure it works, hopefully some time today.


Publish separate TS declarations; fixes #4

This should fix #4.
@willclarktech could you review the changes? I can publish to npm first if that's needed to confirm.

Published on npm as version 0.5.1


Add method to return character from char event.

Firstly, thank you for this library. I've really enjoyed hacking my way through it.
This is a minor proposal that helped me clean up some ugly code. Here's an example:
use cursive::event::{Event, EventResult, EventTrigger};
use cursive::views::TextView;

fn main() {
    let mut siv = cursive::default();
    siv.add_layer(TextView::new("enter uppercased character:"));

    siv.set_on_pre_event_inner(uppercased(), move |event| {
        // use the method here
        let c = event.char().expect("only chars are triggered");
        Some(EventResult::with_cb(move |siv| {
            siv.add_layer(TextView::new(format!("do something useful with: {}", c)))
        }))
    });

    siv.set_on_pre_event(Event::Char('q'), |siv| siv.quit());
    siv.run();
}

fn uppercased() -> EventTrigger {
    EventTrigger::from_fn(|e| matches!(e, Event::Char('A'..='Z')))
}

This Event::chars() method allows us to access the inputted character without creating a mapping, which is a bit tedious when you want to capture a range of values (as we do in the example).

Thanks for the PR!
I think in this case a match self might be shorter and simpler than a if let.
Also, should it maybe also return the char for AltChar and CtrlChar events?


Revert "Added pip install jax/jaxlib to bazel build"

Reverts google/iree#1047
We found a way to avoid this dependency. See https://groups.google.com/forum/#!topic/iree-discuss/QN7calgcvr0

Workflow files can't be managed by copybara because of GitHub "security", so this just gets merged directly :-)


Rust Rewrite

I may do this if I get bored or need another side-project.
Problem:
I have grown somewhat frustrated with golang over the years for a variety of reasons.

Generics support is not very good, making optionals annoying
Annoying default struct initialisation: The only way to enforce a struct initialisation invariant is to put the type into a different package than all the code using it. On top of this, it then gets really hard to init a struct in different ways. Rust's Default trait is way nicer.
Golang's absolutely insane and haphazard use of Equal, which doesn't overload the == operator. This is straight up dangerous. Now that we're using Decimal (Date also has this issue, but less problematically), we have to call Equal everywhere, but there's nothing preventing us from using ==. This is not an issue in rust, because you can implement Eq.

This issue can track the necessary bits and pieces that will need to be figured out before charging in.
Answered (probably):

Command line parsing: https://github.com/clap-rs/clap
WASM: https://rustwasm.github.io/docs/book/
Decimals: https://docs.rs/rust_decimal/latest/rust_decimal/
CSVs: https://docs.rs/csv/latest/csv/
Table rendering: https://github.com/zhiburt/tabled or https://github.com/RyanBluth/term-table-rs
Yaml: https://github.com/chyh1990/yaml-rust
https://github.com/serde-rs/json

Unanswered:

???

This is pretty much done as of 56b9c1f I think. Just needs to be vetted a little more and merged


[stable/metrics-server] Error: UPGRADE FAILED: failed to replace object: Service "metrics-server" is invalid: spec.clusterIP: Invalid value: "": field is immutable

Describe the bug
second time i run the following:
helm --namespace kube-system upgrade --install --force --wait   --repo https://kubernetes-charts.storage.googleapis.com --version 2.10.0 --values /tmp/inceptr/metrics-server.yaml metrics-server metrics-server

i get:
Error: UPGRADE FAILED: failed to replace object: Service "metrics-server" is invalid: spec.clusterIP: Invalid value: "": field is immutable

i am using values.yaml containing:
image:
  repository: gcr.io/google_containers/metrics-server-amd64

Version of Helm and Kubernetes:
> helm version                                                                                10:44:51
version.BuildInfo{Version:"v3.1.1", GitCommit:"afe70585407b420d0097d07b21c47dc511525ac8", GitTreeState:"clean", GoVersion:"go1.13.8"}

> kubectl version                                                                                10:46:15
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-13T18:08:14Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.9-eks-c0eccc", GitCommit:"c0eccca51d7500bb03b2f163dd8d534ffeb2f7a2", GitTreeState:"clean", BuildDate:"2019-12-22T23:14:11Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
metrics-server
(also similar with hpa-operator)
What happened:
Error: UPGRADE FAILED: failed to replace object: Service "metrics-server" is invalid: spec.clusterIP: Invalid value: "": field is immutable

What you expected to happen:
upgrade to succeed :)
How to reproduce it (as minimally and precisely as possible):
install chart as described above, then attempt to reinstall
Anything else we need to know:

Same here, it i still happening
helm 3.1.0
kubernetes v1.15.9-gke.26


Live client occasionally fails with IndexError

Currently, I will restart the algorithm if it catches an exception - but sometimes restarting it without cleaning the algorithm will cause the following error to appear:
Traceback (most recent call last):
  File "binance_catalyst_live_limit.py", line 229, in run
    simulate_orders=False
  File "/usr/local/lib/python2.7/dist-packages/catalyst/utils/run_algo.py", line 551, in run_algorithm
    stats_output=stats_output
  File "/usr/local/lib/python2.7/dist-packages/catalyst/utils/run_algo.py", line 238, in _run
    data_frequency='minute'
  File "/usr/local/lib/python2.7/dist-packages/catalyst/utils/factory.py", line 70, in create_simulation_parameters
    trading_calendar=trading_calendar,
  File "/usr/local/lib/python2.7/dist-packages/catalyst/finance/trading.py", line 178, in __init__
    self._end_session, direction="previous"
  File "/usr/local/lib/python2.7/dist-packages/catalyst/utils/calendars/trading_calendar.py", line 742, in minute_to_session_label
    Given a minute, get the label of its containing session.
  File "/usr/local/lib/python2.7/dist-packages/catalyst/utils/calendars/trading_calendar.py", line 771, in minute_to_session_label
    current_or_next_session = self.schedule.index[idx]
  File "/usr/local/lib/python2.7/dist-packages/pandas/tseries/base.py", line 251, in __getitem__
    val = getitem(key)
IndexError: index 1436 is out of bounds for axis 0 with size 1436
index 1436 is out of bounds for axis 0 with size 1436

@Ericxgao this is a tough one. I have live algos running for several days so I don't believe that it is a systematic issue. But I know that you are using a lot of market so there must be some edge case which I did not encounter. Any additional contextual info that you could offer would be useful. Otherwise, we're working on adding a large number of markets to our tests.

@fredfortier
Pretty significant is that I'm multithreading it. I actually completely stopped using any of Enigma's data fetching tools in favor of CCXT or directly accessing Binance's API - there might be race conditions I'm not seeing under the hood if you are using a single CCXT exchange object.
For the time being I've completely just given up on logging performance and have made my own version of enigma disabling balance synchronization.
At this point, I think my use case might be a little ahead of what enigma is capable of - state saving doesn't seem to work either so I've written my own methods of doing so.

Actually, it's worth noting that I was able to get this issue while running it on just one coin, on a single thread as well. I've written my own recovery code to clean the algo when it happens, which seems like the only way for it to be fixed.

Okay, it makes sense. Multithreading is something which we haven't tested yet. I can see how it could interfere with the state. Feel free to describe your use case for the multiple threads if you want, we can try to get to there relatively soon.

Running separate processes takes up around 160 MB of RAM per process - I tried multithreading it to try to reduce that overhead since I'm cheaping out on my server - that's all. Just want to run more coins with lower RAM usage.

Okay, I see. So you are basically running the same strategy with a large
number of coin in parallel? Or, are you trying to fetch the price data and
compute TA for multiple markets in parallel, then consolidating the threads
and placing your orders where you found signals? We can try to facilitate
the latter soon as we can since it is not inherently difficult. The
challenge with the former would be to consolidate the performance stats.
On Tue, Feb 6, 2018 at 11:58 PM Ericxgao<EMAIL_ADDRESS>wrote:

Running separate processes takes up around 160 MB of RAM per process - I
tried multithreading it to try to reduce that overhead since I'm cheaping
out on my server - that's all. Just want to run more coins with lower RAM
usage.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/enigmampc/catalyst/issues/208#issuecomment-363657555,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZ-QhvaiAP2RI-rG3SHAE_Yo2U30a4Cks5tSS1ugaJpZM4R4Y2H
.

Same strategy with a large number of coins - but the latter case would have the same results if I understand correctly.

Yes, I'll try creating a sample strategy with the second method and see how it goes. We'll get back to you when we have something fully tested.

@Ericxgao to one of your points above, we recently included the functionality to save whatever you need to preserve from the state (a dict that can hold anything) under context.state between runs. Documentation needs to catch up with it as per #224.


Accept binary representation of atom on Ecto.Enum.cast/3

We currently rely on the database representation for casting. This means
that, if :foo translates to 1 in the database, we only accept 1  and
:foo as input when casting. This PR changes it so "foo" is also
accepted.
Closes #3691

Just a disclaimer: if you think that parameterized type params growing big is an issue, we may calculate everything from the mappings param. But it implies a small performance overhead, I think

Also, behaviour:
If you have: [zero: "one", one: "two"]
casting "one" will return :zero
Otherwise it would be a compatibility break

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


The example page logs current state instead of next state

Open the example page https://theaqua.github.io/redux-logger/
Do any operation, and view the log.

Expected: the next state logged to console equals to the state after the operation
Current: the next state logged to console equals to the state before the operation, instead

I see. It's interesting.

I can't replicate this problem running the latest version of example locally. So, I suppose it's a bug that occurred in earlier versions.
We haven't updated the hosted example for quite some time.

We should update it and close this issue afterwards.

Has there been any progress on this so far?

I am on version 3.0.6 of redux-logger and version 3.7.2 of redux and it still appears to exist.  I am also using redux-promise-middleware (v4.4.1) and redux-thunk (v2.2.0).  When i examine the state through the React plugin for Chrome the state is correct there.  the changed element is a nested array inside the Object.  Let me know if i can provide any additional information that may help.

Closing the issue as the example page is no longer available.


PyQt5 ImportError

🐛 Bug
I'm sorry this issue does not follow the bug template, as it doesn't fit it very well.
I'm working in an app that integrates napari. Yesterday everything worked fine, but today I'm getting the following error when trying to run it:
--> napari.run()

ImportError: /home/pepv/anaconda3/envs/hyperion/lib/python3.10/site-packages/../.././libQt5Core.so.5: version `Qt_5.15' not found (required by /home/pepv/anaconda3/envs/hyperion/lib/python3.10/site-packages/PyQt5/QtCore.abi3.so)]()

What is turning me crazy is the following: when running the code in an existing jupyter notebook in particular, the code runs just fine and napari is launched. Running it into any other new or existing jupyter notebook returns the same error, even if executing the %gui qt5 magic command. I have already checked that kernels are the same.
I'm using a conda environment with the folloring Qt related packages:
pyqt                      5.12.3          py310hff52083_8    conda-forge
pyqt5                     5.15.6                   pypi_0    pypi
pyqt5-qt5                 5.15.2                   pypi_0    pypi
pyqt5-sip                 12.9.1                   pypi_0    pypi
pyqtchart                 5.12            py310hfcd6d55_8    conda-forge
pyqtgraph                 0.12.3                   pypi_0    pypi
pyqtwebengine             5.12.1          py310hfcd6d55_8    conda-forge
qt                        5.12.9               ha98a1a1_5    conda-forge
qtconsole-base            5.2.2              pyhd8ed1ab_1    conda-forge
qtpy                      2.0.1              pyhd8ed1ab_0    conda-forge

I know this is a very broad and n00b-like issue, but it doesn't make any sense for me that the error appeared overnight nor being able to run napari only in a specific notebook.
Edit
I created a new environment and reinstalled all dependencies. Napari seems to run as it used to. I still don't understand the source of the issue.

Hi @Jose-Verdu-Diaz, glad you were able to get it fixed.

I created a new environment and reinstalled all dependencies. Napari seems to run as it used to. I still don't understand the source of the issue.

The issue was very likely the fact that you ended up with PyQt5 installed from both conda (which unfortunately names it pyqt) and PyPI (which names in pyqt5).
pyqt                      5.12.3          py310hff52083_8    conda-forge
pyqt5                     5.15.6                   pypi_0    pypi

This dual installation can happen if you had pyqt already installed in the environment from some other dependency, and then you run pip install napari[all].  Because pip doesn't recognize pyqt as fulfilling the pyqt5 requirement, it installs over it, and causes the binary incompatibility that you saw.  The fix is to create a new environment as you found.  But just a heads up that you might run into it again if you frequently mix conda and pip with packages that pull down pyqt


Update app.md

Fix Property name.

@akira345
Thank you for your pull request, and I'm so sorry to be late to reply to you.

If it complies with the kintone REST API specification, it will be "properties", but in kintone-js-sdk,
the property name "fields" is used to make it easy to understand where the value of the field is specified.
It was confusing, sorry.
Also, the new API client(kintone-rest-api-client) is currently under development, and the current kintone-js-sdk will be deprecated in the near future.
For the new API client, we use the design you mentioned above.
Please use this for future projects.

Thank you.

Thank you for your reply.
I understand the situation. (It confuses me.)
Thank you for introducing our new API client. Is there a way to make a formal announcement?

@akira345
We will announce formally in cybozu developer network if it will be ready in a few months.
You can already use it, but please wait for a little longer to use it with everything including the documents.


bot tests: Extend tests for TicTacToeModel.

The tictactoe bot requires clean up and coverage improvements due to low
maintenance. Coverage for tictactoe.py was very low due to several functions
entirely missed in line coverage. Adding tests to cover functions
get_locations_of_char and is_valid_move improved coverage of the
TicTacToeModel and increased line coverage from 41.66%
to 50%. Testing was done locally by running ./tools/test-main until we
received response 'ok', as well as using coverage to give us the final
coverage percentage.
#417

thanks - will make the changes!

hey! made the changes you requested.

@jchinnam: Looks great, merged! Thanks for working on this! :)

thank you!!


memory issue

Hey, when u mix screen and camera the chrome browser goes insane on using memory so it just dies. Same happens on ur demos as well.

Memory problems also occur in Multiple Cameras (Customized) demo.
It is OK to change mixer.frameInterval = 1; to mixer.frameInterval = 10;

But even when I did that it still had memory issues. It just grows more slowly. After about 5 minutes it was using 5GB of memory and still rising. Eventually, my computer starts crashing.


Silently new WPP Version 1.5.2401.21 released?

Is a new version for WPP silently released?
Today I get surprised by a new message. When starting WPP it shows a a message "Please Upgrade .NET Framework on this machine"
WPP version info shows 1.5.2401.21 installed which is newer than the one here in the repository. Auto Update Feature was enabled.

I wonder the same. Binaries updating out of the blue without any kind of a digital signature are quite the red flag, especially when seemingly "official" project sites contain no release notes or other traces of that new version. Very odd!

Hi @sonduko and @SwissJay, sorry for the scare. Yes, there is a new build of WPP. I didn’t have the time to upload the new binary here.

Please update the README with the new version, even if not yet available in releases page.
Having a binary on my server with a "non-official" version number is quite worrying.
Or, at least, reopen and pin this issue, so people (like me) can find it easily and know everything is ok.
(I was going to downgrade to latest available till I had a look into "closed" issues...)


Standalone Grid Doesn't Import Flex

I noticed that the bootstrap-grid.scss doesn't @import "utilities/flex"; considering that the documentation makes references to those classes should these be included in that file?

Fixed by 6b9265fc2dbe242bc6e4120333710b8a29b0b5ca.


perf(stream): dispatch message concurrently

https://github.com/risingwavelabs/risingwave/blob/6fe26b46b399e5831a6927fdf859a84b02432da4/src/stream/src/executor/dispatch.rs#L69-L135

If there's a lot of downstream jobs and then a lot of actors, this might be a significant improvement. On the other side, the inputs are executed concurrently and permits (#6170) are returned concurrently as well.
However, it's still worth noting that there's still an "alignment" where we have to wait for all dispatchers finishing the dispatching. The asynchronization is achieved by exchange buffers.


Not Working in chrome

Hi Team,
The code is not working in chrome from morning
even in demo page also iam not getting lat long
it is saying geoloaction is not enabled even after enabling
Attached screen short for reference

Same here, I also tried with Safari, and its not working, maybe its not working with mac at all?

Hi, that is strange, it works on my machine (MacBook Pro 2018, Chrome 72.0.3626.119, latest Safari). Did you allow the position usage using the popup (see screenshot)?

same here... even if i allow  position usage using the popup... but some times it works fine

I have the same problem on an e-commerce just released in beta: 60% of users seems to have it working and 40% not: even if they enable the geolocation, I receive isGeolocationEnabled: false.
I'll try logging with the onSuccess callback. Unfortunately it is not easy to reproduce.

@matteofrana I'm sad that it behaves so weirdly all of the sudden :-/ any additional information could help us figure out what is wrong. Thank you for helping!

Reporting not working, even after allowing location popup dialog, both chrome and safari.

Apparently, this is a Chrome bug: https://bugs.chromium.org/p/chromium/issues/detail?id=753242

Oh indeed thanks, now we can track this issue there.

Closing as it was a bug in Chrome


Initialize lru-cache with new

Fix class constructor LRUCache cannot be invoked without 'new'

this fix is merged but NPM registry is not updated


[HxMultiSelect] InputGroupStartTemplate and InputGroupEndTemplate inner button clicks don't function

When you use either a InputGroupStartTemplate or InputGroupEndTemplate element within the HxMultiSelect and it contains functionality such as an HxButton (or similar I'd imagine) they don't get clicked, instead the main multi-select dropdown is toggled.
Instead, the dropdown click event should only be triggered if the main input is clicked, not either template.

Have you tried setting OnClickStopPropagation="true" for those buttons? (Or @onclick:stopPropagation for HTML elements.) Your click event is propagating to the enclosing div that contains the data-bs-toggle attribute for the selection dropdown.
If that's the case, could you please provide us with a simplified code example that we can use to reproduce the issue?


Login Message Broker requests to Northstar

Any creates/updates to a user start lazy loading into either message broker or Northstar

Send info to the platform

email
uid
first name
address
timestamps

fixed with #4600


Account balance adjustments

Adjust outputs accordingly based on comparison testing against Rosetta Ocaml implementation.

Addressed in https://github.com/MinaFoundation/MinaMesh/pull/78.


[py2py3] Migrate WMCore/Configuration

Impact of the new feature
This involves migrating WMCore/Configuration. It does not depend on any other wmcore module, so it can be tackled straight away.
This change can directly impact
'WMCore_WMStats',
'WMQuality_WebTools',
'WMCore_Locale',
'WMCore_JobSplitting',
'WMCore_WMInit',
'WMCore_Agent',
'WMCore_WebTools',
'WMCore_DataStructs',
'WMCore_FwkJobReport',
'WMCore_ReqMgr',
'WMCore_MicroService',
'WMQuality_Emulators',
'WMCore_WMSpec',
'WMComponent_AnalyticsDataCollector',
'WMCore_REST'

since these modules import WMCore/Configuration.
Is your feature request related to a problem? Please describe.
Make WMCore/Configuration compatible with both python2 and python3.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
Run futurize on WMCore/Configuration, then apply manual changes if needed

This has been postponed to after we have a python3 environment. I added the tag to reflect a choice made in a private discussion with Alan short after we opened this issue.

This has been postponed to after we have a python3 environment. I added the tag to reflect a choice made in a private discussion with Alan short after we opened this issue.


Nested Collections / Sub-folders

As far as I can tell, this hasn't been asked before. We're using Excalidraw+ at work and it would be great if we could have nested collections. This is especially important when multiple teams are using Excalidraw and each team is managing multiple projects.

Nvm, I see that it was reported in #5284.


Add Badge component

Add Badge component, and make it auto-available for components like Icon and IconButton.
Consider as well components used in complex ones like AppBar / Modal / Table which can benefit from it.
See for reference: https://material-ui.com/components/badges/

Badge component added in<EMAIL_ADDRESS>


Storage name starting and ending with "-" is invalid name.

This fixes the trailing dash - in storage name issue. Associated with https://github.com/Azure/aks-periscope/pull/20

Its kind of undocumented, but some pseudo mention here: https://docs.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata#container-names

cc: @feiskyer and @JunSun17

LGTM.


add Route ServicePublishingStrategy for Konnectivity

Add a Route ServicePublishingStrategy for Konnectivity and switches to use it by default.
The APIServer is the only service remaining that requires an LB.
@derekwaynecarr @csrwng

/test e2e-aws-pooled

e2e test timed out during cleanup but the tests passed

/lgtm
/hold
Feel free to remove hold when ready, thanks!

try one more time
/test e2e-aws-pooled

/hold cancel


SRX-2PM2DM - Add a Checkout dialog

there was some edits to ActionsCart and the file was moved to a new directory.

I like it!