text:
Potential lock contention: Coordinator is not able to publish routing table to new node which causes it fails to be bootstrapped

After further investigation for the issue in https://github.com/buraksezer/olric/issues/253, we find that when there is high traffic on the cluster, after we kill one pod, the new pod is not able to get the routing table from coordinator. It cannot see the log: https://github.com/buraksezer/olric/blob/master/internal/cluster/routingtable/operations.go#L92. Then it fails to call markBootstrapped later at https://github.com/buraksezer/olric/blob/master/internal/cluster/routingtable/operations.go#L116. Then DMap creation will never meet the condition IsBootstrapped at https://github.com/buraksezer/olric/blob/master/internal/cluster/routingtable/routingtable.go#L204 and thus fails with operation timeout. This happens only when we kill non-coordinator pod. If we kill coordinator pod, the new pod can come up successfully.
However, with low traffic the new node is able to get the routing table published from coordinator and then creates DMap successfully.
When there is high traffic, the coordinator is overwhelmed by the LRU deletion:
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete replica key/value on dmap.test_table: context canceled => delete.go:82"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete expired key: test:f16e1d3b-06a4-48b6-8dfe-109915d7b1cc on DMap: dmap.test_table: canceled => eviction.go:161"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete replica key/value on dmap.test_table: context canceled => delete.go:82"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete expired key: test:9305b198-5863-439e-866f-17e3b54f5afd on DMap: dmap.test_table: canceled => eviction.go:161"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete replica key/value on dmap.test_table: context canceled => delete.go:82"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete expired key: test:63dbc9d7-0633-489f-b0b2-b9e067526d3d on DMap: dmap.test_table: canceled => eviction.go:161"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete replica key/value on dmap.test_table: context canceled => delete.go:82"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete expired key: test:b5f4fb9f-4154-4d0b-a280-41e910e94725 on DMap: dmap.test_table: canceled => eviction.go:161"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete replica key/value on dmap.test_table: context canceled => delete.go:82"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete expired key: test:12a87263-b081-4ea1-acb5-4f115b3b3219 on DMap: dmap.test_table: canceled => eviction.go:161"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete replica key/value on dmap.test_table: context canceled => delete.go:82"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete expired key: test:19cee89f-8260-41da-8b1d-79656004a60d on DMap: dmap.test_table: canceled => eviction.go:161"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete replica key/value on dmap.test_table: context canceled => delete.go:82"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete expired key: test:fa128293-2b18-4bb1-a2fe-2657e7c7043e on DMap: dmap.test_table: canceled => eviction.go:161"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete replica key/value on dmap.test_table: context canceled => delete.go:82"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete expired key: test:8bd69d69-dd3f-48d2-851f-0609e2554ac2 on DMap: dmap.test_table: canceled => eviction.go:161"}
{"level":"info","ts":"2024-05-21T02:31:42.587Z","caller":"leaf.go:238","msg":"2024/05/21 02:31:42 [ERROR] Failed to delete replica key/value on dmap.test_table: context canceled => delete.go:82"}

There are also a lot of following logs:
{"level":"info","ts":"2024-05-21T02:27:19.418Z","caller":"leaf.go:238","msg":"2024/05/21 02:27:19 [ERROR] Failed to move DMap fragment: test_table on PartID: 0 to 172.19.19.174:3320: dial tcp 172.19.19.174:3320: connect: connection refused => balancer.go:91"}
{"level":"info","ts":"2024-05-21T02:27:19.418Z","caller":"leaf.go:238","msg":"2024/05/21 02:27:19 [INFO] Moving DMap fragment: test_table (kind: Backup) on PartID: 18 to 172.19.19.174:3320 => balancer.go:86"}
{"level":"info","ts":"2024-05-21T02:27:19.533Z","caller":"leaf.go:238","msg":"2024/05/21 02:27:19 [ERROR] Failed to move DMap fragment: test_table on PartID: 18 to 172.19.19.174:3320: dial tcp 172.19.19.174:3320: connect: connection refused => balancer.go:91"}
{"level":"info","ts":"2024-05-21T02:27:19.533Z","caller":"leaf.go:238","msg":"2024/05/21 02:27:19 [INFO] Moving DMap fragment: test_table (kind: Backup) on PartID: 48 to 172.19.19.174:3320 => balancer.go:86"}
{"level":"info","ts":"2024-05-21T02:27:19.624Z","caller":"leaf.go:238","msg":"2024/05/21 02:27:19 [ERROR] Failed to move DMap fragment: test_table on PartID: 48 to 172.19.19.174:3320: dial tcp 172.19.19.174:3320: connect: connection refused => balancer.go:91"}
{"level":"info","ts":"2024-05-21T02:27:19.625Z","caller":"leaf.go:238","msg":"2024/05/21 02:27:19 [INFO] Moving DMap fragment: test_table (kind: Backup) on PartID: 81 to 172.19.19.174:3320 => balancer.go:86"}
{"level":"info","ts":"2024-05-21T02:27:19.724Z","caller":"leaf:238","msg":"2024/05/21 02:27:19 [ERROR] Failed to move DMap fragment: test_table on PartID: 81 to 172.19.19.174:3320: dial tcp 172.19.19.174:3320: connect: connection refused => balancer.go:91"}
{"level":"info","ts":"2024-05-21T02:27:19.724Z","caller":"leaf:238","msg":"2024/05/21 02:27:19 [INFO] Moving DMap fragment: test_table (kind: Backup) on PartID: 94 to 172.19.19.174:3320 => balancer.go:86"}
{"level":"info","ts":"2024-05-21T02:27:19.852Z","caller":"leaf.go:238","msg":"2024/05/21 02:27:19 [ERROR] Failed to move DMap fragment: test_table on PartID: 94 to 172.19.19.174:3320: dial tcp 172.19.19.174:3320: connect: connection refused => balancer.go:91"}
{"level":"info","ts":"2024-05-21T02:27:19.852Z","caller":"leaf.go:238","msg":"2024/05/21 02:27:19 [INFO] Moving DMap fragment: test_table (kind: Backup) on PartID: 127 to 172.19.19.174:3320 => balancer.go:86"}
{"level":"info","ts":"2024-05-21T02:27:19.913Z","caller":"leaf.go:238","msg":"2024/05/21 02:27:19 [ERROR] Failed to move DMap fragment: test_table on PartID: 127 to 172.19.19.174:3320: dial tcp 172.19.19.174:3320: connect: connection refused => balancer.go:91"}

Where 172.19.19.174 is the pod got killed.
One potential root cause is that: There are a few client locks in delete.go (https://github.com/buraksezer/olric/blob/master/internal/dmap/delete.go), update.go (https://github.com/buraksezer/olric/blob/master/internal/cluster/routingtable/update.go), put.go (https://github.com/buraksezer/olric/blob/master/internal/dmap/put.go). They are fighting to lock on the Redis client. And because there's 1000s or more evictions/deletions, the routing table code can't get the lock to broadcast the routing table. This seems to be a lock contention issue.
Besides, for initial node coming up, we also sometimes see coordinator fails to publish routing table to nodes, which then cause the node fail to create DMap due to bootstrap operation timeout.
Our testing setup:
Using Olric embedded mode, 3 pods each with 4GB and 2 CPU.
config.New("lan")
ReplicaCount = 2
ReplicationMode = AsyncReplicationMode
LRU:
DMaps.MaxKeys = 1_000_000
DMaps.MaxInuse = 1_000_000_000
BootstrapTimeout = 2 * time.Minute
All others are default setting
Running 1000 QPS. Each is the sequence: Write, wait 10ms, then read.
Each key-value pair is key UUID and value random 16 bytes, so total 32 bytes.

Possibly, there is an issue with your setup: the peer discovery code doesn't work properly. It may propagate non-existing nodes or fail to remove failed nodes from the member list.
I think there is no problem with the lock usage. These parts of the code are carefully written, reviewed, and tested the time over time.
Regarding the error messages, Olric is a highly concurrent system. It has many goroutines that process some data concurrently. Some of these components are not synced. Because it is not necessary. A goroutine may try to do something; if it fails, it logs the problem and continues working as usual. The error logging may be noisy sometimes. I accept that.
As I said before, the problem might be in the peer discovery code. Is it possible to share it?

I am closing this issue due to a lack of activity.

repo: buraksezer/olric


text:
Initial set image is appearing smaller than the original size

@burhanrashid52
Actually originally the image is big in size but when we try to edit with photo editor its size appears smaller

Duplicate of #10

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Do we want to have subscriber service (like on RancherOS)?

RancherOS 1.5.1 added subscriber service like this:

There is now a built-in service for system upgrades that requires access to the internet. By default, it can detect system updates and downloads the required files. It will not automatically apply the patch. If you want to completely disable this feature, just run ros config set rancher.upgrade.policy none

It was added by https://github.com/rancher/os/pull/2667 and I assume that they used it to get understanding that how widely RancherOS have been used. It collects processor architecture, system UUID and OS version with these commands and reports them to Rancher:
uname -m
sudo cat /sys/class/dmi/id/product_uuid
sudo ros -v | awk '{print $2}'

Besides of data collection it also will pre-download OS upgrades or even do upgrades automatically if user have enabled it ros config set rancher.upgrade.policy auto
Currently subscriber service is disabled from BurmillaOS beta versions but similar data would be useful for its maintainers too.
What others think, are those infos anonymous enough that we can have enabled by default (and users will be still able to disable it if they want)?
What comes to auto download/upgrade feature. I don't want to have one big "master switch" but instead of it we should make that URL and schedule configurable so users can use it to mass deploy upgrades when they want.

I think we have to continue with that functionality since it will give us a notion of which architectures are more used to be able to focus on working on them to get better performance for example.
I think updates should be automatic to provide greater security against serious problems such as vulnerabilities.

You mean that we actually should make updates automatic by default?
Currently version have been read from http://ros.rancher.io/gateway/version which looks to be just simple text file so we can easily add similar to https://github.com/burmilla/releases/tree/v1.9.x and then just set branch policy on way that it will require at least two of us need to approve it before merge (as it will really trigger upgrades then).
If we do that then we most probably should allow users to also modify that URL so they can example fork that releases repository and that way control that when upgrade happens on their environment.
What comes to that data collection. We need figure out some good place host service which will collect that data.

You mean that we actually should make updates automatic by default?

To get the version and anonymous data collection we can make an API in PHP to provide the number of the latest version and to upload through a POST request the information collected from the user.

You mean that we actually should make updates automatic by default?

Yes, I could do the automatic updates by default so we save problems. But putting in the cloud-config.yml an option to disable automatic updates giving the user the option of when to update.
To get the version and anonymous data collection we can make an API in PHP to provide the number of the latest version and to upload through a POST request the information collected from the user.

IMO automatic updates and any telemetry should be opt-IN only.  This project should be a steward of open source and act in good faith by default.
IMO it's not worth thinking about auto updating until there's a string of successful, non-breaking stable releases.
Docker Hub should give enough in terms of download stats per image/arch to get directional information.
Github and Docker Hub are already centralized dependencies - I don't think it makes sense to add more or try to maintain a centralized service outside of those until the project has grown and it's actually needed.
I like that RancherOS can check against current version and easy updating (as well as @olljanat's plan above to maintain it in the repo with a commit policy).

IMO automatic updates and any telemetry should be opt-IN only. This project should be a steward of open source and act in good faith by default.

Agreed. That why I removed whole feature on this point.

Docker Hub should give enough in terms of download stats per image/arch to get directional information.

True so let's rely to those stats then.

Github and Docker Hub are already centralized dependencies - I don't think it makes sense to add more or try to maintain a centralized service outside of those until the project has grown and it's actually needed.

Yea and I like to use only services like these which are free for open source projects and so we don't need maintain any infrastructure.

I like that RancherOS can check against current version and easy updating (as well as @olljanat's plan above to maintain it in the repo with a commit policy).

OK. Then I propose that we reintroduce this one example under "auto-updater" name on os-services which can be enabled with ros service enable auto-updater and scheduled using system cron https://burmillaos.org/system-services/custom-system-services/#service-cron

Just my two cents here:

We do not need to track users. Lots of people are willing to share their use case I'd suspect as the project takes up speed.
Auto updates are nice to have

Closing because not planned.

authors: PrplHaz4 ToeiRei olljanat tomaswarynyca

repo: burmilla/os


text:
Support train deep learning models on Apple Silicon GPU?

Feature description
Support train deep learning models on Apple Silicon GPU? M1 and M2

Feature motivation
Faster

(Optional) Suggest a Solution

It's supported but there is a bug in tch-rs which prevents from automatically installing torch C++ libs (see the issue #180). However, we checked in a script work around. Please see my comment on how to run it: https://github.com/burn-rs/burn/issues/180#issuecomment-1454993497. This is available on main branch.
Let us know if you're having trouble setting it up. I develop and test on Mac M1 pro and I created this workaround script.
Also to note: we enabled the accelerate framework support (for MacOS and iOS) for burn-ndarray (see #183). There is a "blas-accelerate" flag in burn-ndarray tat you can use to build.

@antimora Thanks.
When I try this script, it shows:
✗ python scripts/fix-tch-build-arm64.py
Installing/Upgrading torch via pip install ...
Requirement already satisfied: torch in /opt/homebrew/lib/python3.11/site-packages (1.13.0a0+git49444c3)
Requirement already satisfied: typing_extensions in /opt/homebrew/lib/python3.11/site-packages (from torch) (4.5.0)
Requirement already satisfied: tomli in /opt/homebrew/lib/python3.11/site-packages (2.0.1)
Requirement already satisfied: tomli-w in /opt/homebrew/lib/python3.11/site-packages (1.0.0)
Updating config.toml with torch library paths ...
Traceback (most recent call last):
  File "/Volumes/Acrucial/repos/ai/burn/scripts/fix-tch-build-arm64.py", line 71, in <module>
    main()
  File "/Volumes/Acrucial/repos/ai/burn/scripts/fix-tch-build-arm64.py", line 67, in main
    update_toml_config()
  File "/Volumes/Acrucial/repos/ai/burn/scripts/fix-tch-build-arm64.py", line 26, in update_toml_config
    import tomli
ModuleNotFoundError: No module named 'tomli'

But I have tomli
python3 -m pip install tomli
Requirement already satisfied: tomli in /opt/homebrew/lib/python3.11/site-packages (2.0.1)

BTW, conda is actived. I think that is ok. Right?

BTW, conda is actived. I think that is ok. Right?

Actrully, it does.
I need this:
conda install tomli
conda install tomli-w

But looks it not be accelerated. On my Macbook pro 13 2020(M1), example mnist takes about half an hour.
@antimora How about on your Mac M1 pro for example mnist?
I use this command:
cargo run --example mnist --release --features ndarray-blas-accelerate

@overheat yes, with accelerate it takes about this long. This is because NDArray is not optimized as torch yet. @nathanielsimard made a few optimizations so you'd want to update the main.
However, currently burn-tch backend with CPU and GPU on Mac is fast. Try with "tch-gpu" or "tch-cpu" feature flags. You'll notice for some reason CPU is faster for this MNIST example, but only with the current model. It appears the model is small enough, it completes under one minute on CPU. Probably the overhead copying data to GPU is more. When I updated with a bigger model, GPU was faster. You can view activity monitor on your mac to see how much GPU is busy, like this:

BTW, conda is actived. I think that is ok. Right?

Actrully, it does. I need this:
conda install tomli
conda install tomli-w

Inspired by this article
virtual environment in which you can install custom Python modules. But the virtual environment is initially empty—even if you’ve already installed tomli on your computer!

Thanks for reporting. Probably there were some differences in the installation. I use pip and I didn't test with conda. Python packages installations is always difficult for different environments compared to rust =D

@overheat Were you able to train your models on Mac M1/M2 GPU? Can we consider this issue closed?

@nathanielsimard we should close this as duplicate #180. I don't have ability to close this ticket.

authors: antimora overheat

repo: burn-rs/burn


text:
Login via Google OAuth2

use passport.js

@burtonjc The feature with this where  login button doesn't appear when someone is already signed in, I have a question of where to begin.  Would this be best done by writing js in the passport.js file,  or with angular then including that in the index.jade?

authors: aaronpflower burtonjc

repo: burtonjc/foosnet

license: mit

license_source: bigquery


text:
lolcat speaks lotz of lotz of languages. (busyloop/#8)

require 'unicode' module seems to work. I guess it's called "module." I have no idea what I was codzing.

Pls murge, needz it foar epic output!

authors: eproxus livibetter

repo: busyloop/lolcat


text:
Not work with height in %

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

If i change height attribute value from 300 px to 20% it stop working  :cry:

Yes, that's true. I'm glad to accept a PR for this, but I won't touch it for now.

authors: bluegaurav buzinas

repo: buzinas/simple-scrollbar


text:
Investigate replacing left/top with transform:translate for positioning

Refer to this comment by James:

I think I found one potential problem: each row is placed by setting the top CSS property, which apparently makes Chrome redraw the whole viewport. I changed it to transform: translateY(...) and it seems a bit smoother.

Quick test does seem smoother but it could be confirmation bias. Need to test more and confirm that (1) performance really does improve and (2) not at an unacceptable GPU cost.
Will leave this issue open for now and see if more people have opinion or information.

Does Chrome have any way to measure GPU usage? The only potential downside is forcing each row to be handled as a GPU texture (or something like that). I'm not sure what the right pattern here is, but using transforms is probably the way to go, especially since we're only showing a constant number at one time anyway.
I've heard concerns from various browser devs about using too much GPU memory by overusing CSS properties that trigger GPU offloading, but I'm not really sure. What's the "scientific" way we can measure this?
I can see if there's anything in Firefox I can profile. I can't tell any difference in Firefox 46 with the APZ feature making things happen async.

Does Chrome have any way to measure GPU usage?

I think the white bar inside of Chrome's Timeline view is GPU but I'm very inexperienced with that type of profiling. :)

I found it: it's in the FPS overlay (???). devtools menu > more tools > rendering settings > show FPS meter. That meter shows the amount of GPU memory.
Observed results while scrolling down through the entire page:
Using top:
Without any overscan rows: 8-16 MB
With an overscan of 100: 8->25 MB
Using transform:
Without any overscan rows: 15->22MB
With an overscan of 100: 30->55MB
The question is if this is acceptable or not. I'm not really sure. But it seems like it could potentially use about twice as much memory on average (although this is all anecdotal, just watching the meter while scrolling).
I'm surprised the top works this well, honestly. I thought transforms would be clearly smoother, but maybe we should hold off on this until there's a clear reason to do it. Or wait until this lib gets used in more situations and other people complain about performance.

I'm actually not sure if we have GPU memory in our devtools yet, but I'll check Firefox if we do.

Bah. I've used that overlay before and forgotten that there was a GPU meter in there too. Nice! :)
Yeah. I'm okay to sit on this for a bit then and see if others have input. If the performance is at least improved from before (now that on-wheel is gone) then the need isn't as pressing.
I really appreciate all of the info and suggestions :)

Thanks for all the work on this project!
There's a well-known post by Paul Irish about this: http://www.paulirish.com/2012/why-moving-elements-with-translate-is-better-than-posabs-topleft/ I think if you are animating complex objects, transform is better. But I think for the use case here, top is probably better, because there are many objects and they will likely be simpler.
Eventually, it would be easy to even make this configurable so users could choose whatever they want.

I ended up making this change in version 5 because, anecdotally, it seemed like an improvement. I may revert the change (or more likely, as you say, make it configurable) if I get any reports of negative performance impact.

Actually I'll re-open this and repurpose for considering transform -> transform3d

Performance is really bad. It would be cool if we will have ability to configure it.

Performance is really bad.

Huh? Mind giving a little more context? My testing (in various browsers and devices) seems to suggest performance is quite good.

Pinging @flosstik

Sorry, but i don't have enough time for research. When i was update from version 4.0.9 to 5.1.0(and another libs), i saw jerky scrolling. When i was reinstall all dependencies and update lib to 5.2.0, i saw smooth scrolling, but when i scrolled fast, i was saw white screen and after 3 or 5 second content was loaded.
i will try use   overscanColumnsCount and overscanRowsCount, and i think it can help me.
I'm write postgresql viewer with electron. I'm have 1000 rows in one page, and can be infinity columns(in test 30).
I was switched from FixedDataTable (https://github.com/facebook/fixed-data-table). They also use transform for positioning, and they have problems (https://github.com/facebook/fixed-data-table/issues/49)
I think this information isn't helpful. When i will have time i will test it again, and will can give facts.

Research is not necessary. More context than "Performance is really bad." is absolutely necessary if I'm going to do anything about what you're reporting.
For what it's worth, I think the discussion on #124 actually may actually be related to what @flosstik is reporting.

Put another way: I don't think it's actually the transform change that's causing the problem you reported,  but rather, the key change. However I'm not currently sure of a way to resolve this and there is ongoing discussion on #124 about it.

@flosstik: You'll be happy to learn that version 5.2.3 replaces transform with left/top as you suggest. I'm going to go ahead and close this issue for now as that positioning seems to work the best in my testing when compared against translate and translate3d

authors: bvaughn flosstik jlongster

repo: bvaughn/react-virtualized


text:
🛑 VBHC Serene Town B Block is down

In e46d03e, VBHC Serene Town B Block (https://cloud.tymly.in/status/1130) was down:

HTTP code: 521
Response time: 210 ms

Resolved: VBHC Serene Town B Block is back up in b11e407.

repo: bvenkysubbu/tymlymonitor


text:
🛑 Sunshine Silicon Citi is down

In a09b0f5, Sunshine Silicon Citi (https://cloud.tymly.in/status/1021) was down:

HTTP code: 521
Response time: 20240 ms

Resolved: Sunshine Silicon Citi is back up in 4110539.


text:
🛑 Mahaveer Varna A1 is down

In 734036d, Mahaveer Varna A1 (https://cloud.tymly.in/status/1083) was down:

HTTP code: 521
Response time: 20215 ms

Resolved: Mahaveer Varna A1 is back up in 9cc4270.


text:
🛑 Sai Gardens Temple Side is down

In 69de802, Sai Gardens Temple Side (https://cloud.tymly.in/status/1074) was down:

HTTP code: 521
Response time: 217 ms

Resolved: Sai Gardens Temple Side is back up in 385c3b2.


text:
🛑 PSR Aster 1 is down

In 4252226, PSR Aster 1 (https://cloud.tymly.in/status/1059) was down:

HTTP code: 521
Response time: 20233 ms

Resolved: PSR Aster 1 is back up in 315a112.


text:
🛑 Trifecta Esplanade O Block is down

In eb949d6, Trifecta Esplanade O Block (https://cloud.tymly.in/status/1166) was down:

HTTP code: 521
Response time: 231 ms

Resolved: Trifecta Esplanade O Block is back up in 2214a07.


text:
🛑 SNR Silver Ripples is down

In fe03015, SNR Silver Ripples (https://cloud.tymly.in/status/1039) was down:

HTTP code: 521
Response time: 20252 ms

Resolved: SNR Silver Ripples is back up in 6fb58df.


text:
🛑 Dasta Concerto Entrance is down

In 447fe53, Dasta Concerto Entrance (https://cloud.tymly.in/status/1137) was down:

HTTP code: 521
Response time: 20221 ms

Resolved: Dasta Concerto Entrance is back up in dcee509.


text:
🛑 United Elysium is down

In 5b99a0f, United Elysium (https://cloud.tymly.in/status/1019) was down:

HTTP code: 521
Response time: 20224 ms

Resolved: United Elysium is back up in eba5594.


text:
🛑 Nitesh Forest Hills and Flush Meadows is down

In 86b78a4, Nitesh Forest Hills and Flush Meadows (https://cloud.tymly.in/status/1023) was down:

HTTP code: 521
Response time: 20241 ms

Resolved: Nitesh Forest Hills and Flush Meadows is back up in 96b01b3.


text:
🛑 Sunshine Silicon Citi 2 is down

In 9e1710f, Sunshine Silicon Citi 2 (https://cloud.tymly.in/status/1139) was down:

HTTP code: 521
Response time: 218 ms

Resolved: Sunshine Silicon Citi 2 is back up in b5b9ee3.


text:
🛑 SMR Vinay Cascade A Block is down

In f9baffc, SMR Vinay Cascade A Block (https://cloud.tymly.in/status/1094) was down:

HTTP code: 521
Response time: 20227 ms

Resolved: SMR Vinay Cascade A Block is back up in 8b97db2.


text:
🛑 Prakruthi Villas Sarjapura is down

In 09de195, Prakruthi Villas Sarjapura (https://cloud.tymly.in/status/1058) was down:

HTTP code: 521
Response time: 222 ms

Resolved: Prakruthi Villas Sarjapura is back up in 647cf95.


text:
🛑 Prakruthi Villas Sarjapura is down

In 888d8e1, Prakruthi Villas Sarjapura (https://cloud.tymly.in/status/1058) was down:

HTTP code: 521
Response time: 214 ms

Resolved: Prakruthi Villas Sarjapura is back up in 58697d3.


text:
🛑 Prakruthi Villas Sarjapura is down

In 62a1f29, Prakruthi Villas Sarjapura (https://cloud.tymly.in/status/1058) was down:

HTTP code: 521
Response time: 20229 ms

Resolved: Prakruthi Villas Sarjapura is back up in 2c15868.


text:
🛑 Trifecta Esplanade C Block is down

In b504462, Trifecta Esplanade C Block (https://cloud.tymly.in/status/1155) was down:

HTTP code: 521
Response time: 224 ms

Resolved: Trifecta Esplanade C Block is back up in 41a939f.


text:
🛑 United Elysium 2 is down

In 151395f, United Elysium 2 (https://cloud.tymly.in/status/1026) was down:

HTTP code: 521
Response time: 8671 ms

Resolved: United Elysium 2 is back up in 6792b0e.


text:
🛑 SMR Vinay Cascade B Block is down

In 8ffd898, SMR Vinay Cascade B Block (https://cloud.tymly.in/status/1093) was down:

HTTP code: 521
Response time: 20242 ms

Resolved: SMR Vinay Cascade B Block is back up in 82b2b95.


text:
🛑 Dasta Concerto Clubhouse Gym is down

In 2d1f79c, Dasta Concerto Clubhouse Gym (https://cloud.tymly.in/status/1189) was down:

HTTP code: 521
Response time: 20226 ms

Resolved: Dasta Concerto Clubhouse Gym is back up in f8b4b61.


text:
🛑 Hinduja Park 1 is down

In 258685a, Hinduja Park 1 (https://cloud.tymly.in/status/1067) was down:

HTTP code: 521
Response time: 1168 ms

Resolved: Hinduja Park 1 is back up in e885e17.


text:
🛑 Sterling Shalom C Block is down

In 8d868e3, Sterling Shalom C Block (https://cloud.tymly.in/status/1011) was down:

HTTP code: 521
Response time: 20215 ms

Resolved: Sterling Shalom C Block is back up in e167ec4.


text:
🛑 PSR Aster 3 E Block is down

In 7837f09, PSR Aster 3 E Block (https://cloud.tymly.in/status/1064) was down:

HTTP code: 521
Response time: 239 ms

Resolved: PSR Aster 3 E Block is back up in 987a431.


text:
Errors with validate.py

Hello,
I have completed the first two stages of LDRED -  coord_genotypes.py & LDpred.py. These have generated a number of files
coord.hdf5
ldpred_LDpred-inf.txt
....
LDpred_p1.0000e+00.txt
None_ldradius437.pickled.gz
My Phenotype.txt file is a FAM format.  Currently, I have 59529 free memory (ram) on my computer.
Now I would like to proceed to the file stage - validate.py - that will actually create the polygenic scores and give some summary statistics. For this I used the following command lines:
python validate.py --vgf=My_Data --rf=LDpred-inf.txt --pf=Phenotype.txt --rf=STANDARD --out=my_results_valid
However, this message comes up and nothing else happens:
Phenotype.txt
Parsing phenotypes

When I remove the phenotype from the command line, I get the following error:
Parsing phenotypes
Traceback (most recent call last):
  File "ldpred/validate.py", line 754, in <module>
    main()
  File "ldpred/validate.py", line 689, in main
    assert num_individs > 0, 'No phenotypes were found!'
AssertionError: No phenotypes were found!

I am not sure why I get this error as providing a phenotype is optional at this stage.
I will be grateful for any advice on how to deal with these error and successfully build polygenic scores.
Thank you very much in advance.

Thanks for using LDpred.  It seems to me that you made a small error in the flags.  You specify --rf twice, and you should also set --pf_format=FAM
I hope that helps.
Best,
Bjarni

Thank you for your response. I have corrected the mistake and also included --pf_format=FAM. However, the same message appears on the screen and nothing else happens:
Phenotype.txt
Parsing phenotypes

I will be grateful for your advice on how I can overcome this issue and build polygenic scores.
Many thanks

Is Sex defined?  In order for me to better debug this, do you have an example of the phenotype file, e.g. the first couple of lines?

Dear Bjarni,
Of course. Here are a couple lines from the phenotype file:
head Phenotype.txt
EG140001 EG140001 0 0 2 10
EG140002 EG140002 0 0 2 10
EG140003 EG140003 0 0 2 10
EG140004 EG140004 0 0 2 15
Sex is coded as'1' = male, '2' = female, '0' = unknown.  No header.
Thank you very much for your help with this.
With kind wishes.

Hi,
Thank you very much for this. I have just re-run the analysis using the modified code.
python ldpred-master/ldpred/validate.py --vgf=My_Data \
--rf=LDpred_p1.0000e+00.txt \
--pf=Phenotype.txt --pf_format=FAM \
--TS=1,0.3,0.1,0.03,0.01,0.003,0.001,0.0003,0.0001,3E-5,1E-5,1E-6,1E-7,1E-8 \
--PS=1,0.3,0.1,0.03,0.01,0.003,0.001,0.0003,0.0001 \
--out=Results/

I get the following message on the screen but no results appears on the screen on the results folder
Phenotype8.txt
Parsing phenotypes
Parsed 6926 phenotypes successfully

I will be grateful for your advice on how I can overcome this and build the scores.
Thank you very much.

I believe the issue is that you set --rf to a specific file, and not the prefix.
Try --rf=LDpred instead of --rf=LDpred_p1.0000e+00.txt
Hope this works.

Thank you. I have just tried --rf=LDpred instead of --rf=LDpred_p1.0000e+00.txt, but the same outcome occurred. A message was printed on the screen and nothing else happened.
Phenotype.txt
Parsing phenotypes
Parsed 6926 phenotypes successfully

I will be grateful for your advice on how I can overcome this and build the scores.
Thank you very much.

I apologize, I made a mistake,  --rf=  should point to whatever you used for --out in the previous step.  Writing LDpred was wrong.  I also update the code now to provide a small improvement in error messaging when this happens.

It is perfect!  It is working like magic at the moment. Thank you so much for your patience and help with this!

repo: bvilhjal/ldpred


text:
TASK: Update neos/neos requirement

drop Neos 5.x
raise Neos 7.x to 7.3 minimum
allow Neos 8.x

@kdambekalns Thanks for taking care. Mark this ready when you're done and I'll tag a 1.1.0

Form what I can tell, no futher changes are needed…

Thank you! => https://github.com/bwaidelich/Wwwision.Renderlets.Provider/releases/tag/1.2.0

source: gharchive/pull-request

authors: bwaidelich kdambekalns


text:
'No Response' in Apple Home after a certain Time

What issue do you have? Please be as thorough and explicit as possible.
After adding the Devices to Apple Home, they work for around 18h and then stopp. The only way to get them to work again is to remove the Bridge vom Home and add it back again. After the next cycle of around 18h they stopp again.
In Homebridge itself they continue to be shown and work as intended, even when Apple Home says it's not getting a response.
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Homebridge UI-X

Which version of Homebridge/HOOBS do you have?
1.6.0

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Node 18.13.0

Which version of this plugin (homebridge-ewelink) do you have? Has the issue started since upgrading from a previous version?
10.4.0

Which eWeLink devices do you have that are causing issues? Please include product models if applicable.
1 NS Panel Pro, 3 M5 Multiswitches and 1 R5 Remote

Please paste any relevant logs below.
[2/3/2023, 8:07:56 AM] [eWeLink] Fetching devices from eWeLink home/id [Zuhause] [625eafbb9590610009936e5c].
[2/3/2023, 8:08:00 AM] [eWeLink] LAN monitoring started.
[2/3/2023, 8:08:00 AM] [eWeLink] [Panel NS] initialising with options {"logging":"standard","offset":0}.
[2/3/2023, 8:08:00 AM] [eWeLink] [Panel NS] initialised and LAN mode unavailable as not discovered/supported [133:NSPanel].
[2/3/2023, 8:08:00 AM] [eWeLink] [Remote] has been added to Homebridge.
[2/3/2023, 8:08:00 AM] [eWeLink] [Remote] initialising with options {"logging":"standard"}.
[2/3/2023, 8:08:00 AM] [eWeLink] [Remote] initialised and LAN mode unavailable as not discovered/supported [174:NON-OTA-GL(174)].
[2/3/2023, 8:08:00 AM] [eWeLink] [Sleep3 M5] initialising with options {"inchChannels":"","inUsePowerThreshold":0,"logging":"standard","showAs":"default"}.
[2/3/2023, 8:08:00 AM] [eWeLink] [Sleep3 M5] initialised and LAN mode unavailable as not discovered/supported [161:M5-2C].
[2/3/2023, 8:08:00 AM] [eWeLink] [Sleep1 M5] initialising with options {"inchChannels":"","inUsePowerThreshold":0,"logging":"standard","showAs":"default"}.
[2/3/2023, 8:08:00 AM] [eWeLink] [Sleep1 M5] initialised and LAN mode unavailable as not discovered/supported [161:M5-2C].
[2/3/2023, 8:08:00 AM] [eWeLink] [Bath M5] initialising with options {"inchChannels":"","inUsePowerThreshold":0,"logging":"standard","showAs":"default"}.
[2/3/2023, 8:08:00 AM] [eWeLink] [Bath M5] initialised and LAN mode unavailable as not discovered/supported [161:M5-2C].
[2/3/2023, 8:08:02 AM] [eWeLink] ✓ Setup complete. Don't forget to ☆ this plugin on GitHub if you're finding it useful!

Hi,
Closing this just as been a little overwhelmed with issues recently.
If this is still an issue or a feature you would like implemented then please do re-open this ticket!
Thanks for your understanding!


text:
Space Heater 7135 shows light as well heater

What issue do you have? Please be as thorough and explicit as possible.
I have 8 Govee lights and as of today a new space heater (7315). HomeBridge finds it and adds it to Homekit as 3 devices: Heater, thermostat and a light. The home app shows me a temp control, heat/auto/off, a fan control and a light brightness slider.
The device obviously doesn't have a light, any way to remove it?
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Homebridge UI-X

Which version of Homebridge/HOOBS do you have?
HomeBridge v1.6.1

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Raspberry Pi, Node.js Version v20.9.0

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
homebridge-govee v9.4.2

Which Govee devices do you have that are causing issues? Please include product models if applicable.
8x H601A - for some reason the log says it can't find two but they seem to work anyway?
1x H7135 - works but with a light

Please paste any relevant logs below.
On boot
[01/12/2023, 15:48:41] [Govee] [LAN] client enabled and found 0 device(s).
[01/12/2023, 15:48:41] [Govee] [HTTP] client enabled and found 9 device(s).
[01/12/2023, 15:48:42] [Govee] [AWS] client enabled.
[01/12/2023, 15:48:42] [Govee] [BLE] client enabled.
[01/12/2023, 15:48:42] [Govee] [Space Heater] initialising with options {}.
[01/12/2023, 15:48:42] [Govee] [Space Heater] initialised with id [1E:A1:D4:AD:FC:85:97:84] [H7135].
[01/12/2023, 15:48:42] [Govee] [Studio Light 5] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"enabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[01/12/2023, 15:48:42] [Govee] [Studio Light 5] initialised with id [40:36:D4:AD:FC:9D:E1:A8] [H601A].
[01/12/2023, 15:48:42] [Govee] [Studio Light 4] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"enabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[01/12/2023, 15:48:42] [Govee] [Studio Light 4] initialised with id [61:17:D4:AD:FC:A6:4C:CE] [H601A].
[01/12/2023, 15:48:42] [Govee] [Studio Light 6] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"enabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[01/12/2023, 15:48:42] [Govee] [Studio Light 6] initialised with id [74:FE:D4:AD:FC:AB:91:7E] [H601A].
[01/12/2023, 15:48:42] [Govee] [Studio Light 7] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"enabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[01/12/2023, 15:48:42] [Govee] [Studio Light 7] initialised with id [49:D1:D4:AD:FC:AB:06:E8] [H601A].
[01/12/2023, 15:48:42] [Govee] [Studio Light 8] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"enabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[01/12/2023, 15:48:42] [Govee] [Studio Light 8] initialised with id [5C:26:D4:AD:FC:A6:4C:22] [H601A].
[01/12/2023, 15:48:42] [Govee] [Studio Light 2] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"enabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[01/12/2023, 15:48:42] [Govee] [Studio Light 2] initialised with id [30:42:D4:AD:FC:AB:96:CE] [H601A].
[01/12/2023, 15:48:42] [Govee] [Studio Light 1] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"enabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[01/12/2023, 15:48:42] [Govee] [Studio Light 1] initialised with id [14:FE:D4:AD:FC:9D:DE:90] [H601A].
[01/12/2023, 15:48:42] [Govee] [Studio Light 3] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"enabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[01/12/2023, 15:48:42] [Govee] [Studio Light 3] initialised with id [35:1F:D4:AD:FC:AC:0D:54] [H601A].
[01/12/2023, 15:48:42] [Govee] [Studio Light 7] not using AWS connection as not connected to AWS.
[01/12/2023, 15:48:42] [Govee] [Studio Light 8] not using AWS connection as not connected to AWS.
[01/12/2023, 15:49:24] [Govee] [Studio Light 7] could not be updated as Promise timed out after 10000 milliseconds at Timeout._onTimeout (file:///usr/local/lib/node_modules/homebridge-govee/node_modules/p-timeout/index.js:79:64).
[01/12/2023, 15:49:24] [Govee] Could not retrieve TTRs as timeout of 10000ms exceeded at RedirectableRequest.handleRequestTimeout (file:///usr/local/lib/node_modules/homebridge-govee/node_modules/axios/lib/adapters/http.js:643:16).
[01/12/2023, 15:49:24] [Govee] ✓ Setup complete. This plugin has been made with ♥ by bwp91, please consider a ☆ on GitHub if you are finding it useful!
[01/12/2023, 15:49:24] [Govee] [Studio Light 5] current colour [3600K / 278M].
[01/12/2023, 15:49:24] [Govee] [Studio Light 4] current colour [3600K / 278M].
[01/12/2023, 15:49:24] [Govee] [Studio Light 6] current colour [3600K / 278M].
[01/12/2023, 15:49:24] [Govee] [Space Heater] current temperature [20°C].
[01/12/2023, 15:49:24] [Govee] [Space Heater] current mode [low].
[01/12/2023, 15:49:24] [Govee] [Space Heater] current mode [auto].
[01/12/2023, 15:49:24] [Govee] [Studio Light 3] current colour [3600K / 278M].
[01/12/2023, 15:49:24] [Govee] [Studio Light 1] current colour [2700K / 370M].
[01/12/2023, 15:49:24] [Govee] [Studio Light 2] current colour [2700K / 370M].
[01/12/2023, 15:49:24] [Govee] [Studio Light 7] current colour [3600K / 278M].
[01/12/2023, 15:49:24] [Govee] [Studio Light 8] current colour [3600K / 278M].
[01/12/2023, 15:49:25] [Govee] [Studio Light 7] could not find device [d4:ad:fc:ab:06:e9].
[01/12/2023, 15:49:31] [Govee] [Studio Light 8] could not find device [d4:ad:fc:a6:4c:23].
[01/12/2023, 15:49:31] [Govee] [Studio Light 8] could not be updated as no connection method available, see https://shorturl.at/eCN04 for more info at file:///usr/local/lib/node_modules/homebridge-govee/lib/platform.js:1753:13.

When using the Heater
[01/12/2023, 15:54:44] [Govee] [Space Heater] current state [off].
[01/12/2023, 15:54:44] [Govee] [Space Heater] current mode [high].
[01/12/2023, 15:54:44] [Govee] [Space Heater] current mode [auto].
[01/12/2023, 15:55:00] [Govee] [Space Heater] current state [on].
[01/12/2023, 15:55:00] [Govee] [Space Heater] current mode [low].

When using the light
[01/12/2023, 15:55:48] [Govee] [Space Heater] current light [on].
[01/12/2023, 15:55:49] [Govee] [Space Heater] current brightness [1%].
[01/12/2023, 15:55:49] [Govee] [Space Heater] current brightness [81%].
[01/12/2023, 15:55:49] [Govee] [Space Heater] current brightness [100%].

Hi,
as per your post regarding batch closures, this one still seems unresolved as of v10.4.0 or v10.4.1-beta.1.
thanks!

Thanks for re-opening this. I see someone appears to have the same issue in #715.


text:
Wemo Devices work in Homebridge but show as "No Response" in Home App

I don't believe this is a plugin issue but here is my problem. I am running the latest homebridge and wemo plugin version on a raspberry pi. Everything looks good in homebridge. I can turn on/off my 3 devices. When I add the devices to the home app, they seem ok for a few minutes and then I get the dreaded "No Response" on all devices. I've tried resetting all the devices, the raspberry pi, and my iPhone 12. I've removed the devices from the app then re-added them and I get the same behavior. I don't know what else to do. Also, the devices work correctly in the wemo app. The 3 wemo devices are all homekit compatible but since I don't have a homekit hub (ipad, apple tv), I am using the homebridge app as my hub.

Hi @joeroks, just out of interest when you say

I am using the homebridge app as my hub.

what do you mean by this?

Ben,  I was mistaken. Homebridge is not a hub. I either need an Apple tv,  HomePod mini or iPad. I don’t need homebridge if my Wemo’s  are HomeKit compatible. Sorry for the confusion.
Joe Roks

On May 10, 2022, at 7:18 PM, Ben @.***> wrote:

Hi @joeroks, just out of interest when you say
I am using the homebridge app as my hub.
what do you mean by this?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.


text:
Define a maximum number of characters per line

Hi,
It would be nice to be able to define the number of characters per line for the command mdox fmt. Like that every paragraphs are not inline anymore and it's easier to read in IntelliJ for example.
Because then you don't need to scroll horizontally which is a pain to do it regardless how much your UI is awesome :).
If you find it interesting, I would probably take some time to implement it.

Oh yeah that's already cool to have this option ! Thank you for pointing it, I didn't pay enough attention to the documentation.
I still think it would be cool to enforce a maximum length per line. So it's the breaks-line logic for everyone :).

ah nice, thanks for the pointer ! I will look there then :).

Still, it would be amazing to have auto-wrap with given width. Help wanted!

authors: Nexucis bwplotka

repo: bwplotka/mdox


text:
Not using transaction to create url and its relation with users

Describe the bug
err = c.urlRepo.Create(url)
if err != nil {
    return entity.URL{}, err
}

err = c.userURLRelationRepo.CreateRelation(user, url)
return url, err

The code above is not safe enough. If it fails at err = c.urlRepo.Create(url), there would be a dirty record.
Expected behavior
Use transactions to create these records. I had my code in my dev branch, but since I haven't successfully set up the dev env on my computer, I can just leave it to you guys.

Hi @ZhenhangTung, thank you so much for reporting this! Would you like to take on this challenge?!

Brief description of our conversation about the current issue:

It is the common problem: there are plenty of places where transactions are crucial for providing atomicity, here are some of the links example 1, example 2.
Solution should respect SOLID and received software design principles and do not mix the business and low-level logic

As an experiment, I am going to create PR with the draft implementation of Transactional entity.

@ZhenhangTung Just saw you branch, great work! Thank you!

Thanks. I haven't set up the local development env about this project yet, so I don't have any confidence to open the PR right now. Free to use the code on my branch. It's not perfect, but I believe it is the simplest way to do the things we want, based on the current code. You can continue the development based on my code.

authors: ZhenhangTung alldroll byliuyang

repo: byliuyang/short


text:
Rename generate-raw?

This is a question based on very little experience with the tool: should it be renamed to witx-bindgen? The tool seems similar in purpose to bindgen and wasm-bindgen and renaming it to something along those lines might help users familiar with the ecosystem to more quickly pick up on what the tool is intended to do.

cc: @alexcrichton, @pchickey

repo: bytecodealliance/wasi


text:
feat(wasi-threads): improve thread id allocator to reuse identifiers

At the moment, when created, a thread receives an incremental number as an identifier.
This PR allows reusing thread ids once they are released. That is done by using a stack data structure to keep track of the used ids.
When a thread is created, it takes an available identifier from the stack. When the thread exits, it returns the id to the stack of available identifiers.

I'm doing some additional refactoring to have both pos and size as unsigned so that comparisons are safe. I just need to get pos to point to the first empty position in the stack rather than at the top element.

repo: bytecodealliance/wasm-micro-runtime


text:
wasmprinter: add snapshot tests for the outputs

This PR saves the output of every wasmprinter test into the tests/snapshot directory. Once these are in place, every time wasmprinter's output is changed, these changes will be reflected neatly in these snapshots. This can aid with the detection of issues and also as a mechanism to facilitate discussion of subjective calls on how formatting should be done (i.e. previous formatting was better, or the new formatting is better in this specific example.)
The downside is that this is 2000+ new files and 70k new lines in the repo.

This looks great to me, thanks! Would you be up for removing the snapshots component of the path though to place the .print next to all the tests? That way in diffs things should be naturally sorted where if a test was changed the *.print should show up either just before or just after to easily compare in something like the github diff UI.
Otherwise though looks good to go 👍

There are some issues with implementing this. In particular the tests/testsuite is a submodule, so adding files to that directory is going to cause problems. Others are fixable, like for example current code uses files within directories to represent all the modules defined in the wast files, but this isn’t too big a deal and could be replaced with foo.wast@{index}.print without much of an issue.

authors: alexcrichton nagisa

repo: bytecodealliance/wasm-tools


text:
Implementation strategy for the Exception Handling proposal

I've been interested in having the Exception Handling proposal supported in Wasmtime, so I looked into possible ways to implement it. There's been some prior discussion in issues #2049 and #1677, but those issues focus on details that I think are less important than a high-level strategy.
As far as I see, the core difficulty in implementing this feature is that Wasmtime currently has only one non-local control flow construct, traps, and the only way to catch traps is the scoped wasmtime_setjmp construct implemented in C. There is no particularly good way to use this construct to implement the Wasm exception handling opcodes; it is a C function that manages resources opaque to the rest of the runtime. You could translate try blocks to wasmtime_setjmp calls by splitting each Wasm function that uses exception handling into many Cranelift functions, but this is a very complex transformation that would interfere with optimizations on the fast path, and I expect that no one wants that.
So, a different non-local control flow construct is necessary for exception handling. I see two options here:

Reusing the existing OS-specific stack unwinding mechanism (SEH on Windows, DWARF elsewhere), and
Implementing a new Cranelift-specific stack unwinding mechanism.

Option (1) requires a large amount of platform-specific work. Wasmtime does already emit DWARF and SEH tables to be able to capture backtraces with Wasm frames, but a lot more work is necessary to extend that functionality to cover exception handling.
In this case, exceptions and traps would use disjoint mechanisms, which naturally aligns with the semantics specified in the proposal.
Option (2) makes it possible to use a mostly platform-independent mechanism. It doesn't make a lot of sense to implement a new zero-cost exception handling strategy (you're better off using DWARF/SEH in that case), and the other major approach is SjLj. For example, Wasmtime could maintain a linked list of registered exception handlers in VM context, and a function that has try blocks would append an entry to this list in the prologue, containing the frame pointer and the address of the basic block that dispatches an in-flight exception for a particular try body. (This is a bit similar to 32-bit SEH.) Then, on any control flow into or out of a try body, the address recorded in the entry would be updated. The throw instruction would capture the exception parameters and set SP and IP to the ones in the head of the list, while Cranelift would have to make sure that any SSA values live in the dispatch block are allocated to stack slots.
This option could actually eliminate the dependency on C setjmp/longjmp functions and unify unwinding due to exceptions and traps. However, while it requires less platform-specific work, it is more costly at runtime, and maybe not a good fit for Wasmtime in the long run.
What do you think?

You still need to implement the SEH parts for option (1). But the rationale makes sense.
Closing this in favor of #1677.

I would like to join.

Invite sent!
Something I want to highlight: it's definitely not necessary to join this or any other calls in order to weigh in on this or similar decisions. We're more than happy to discuss here, on Zulip, or if that seems appropriate for the decision, in RFCs.

To echo what others have said: thanks for filing an issue with lots of great context @whitequark.

@alexcrichton @cfallin: to be clear, we don't intend to ever unwind native frames, right?
That is, if we have a stack like wasm --call--> host --call--> wasm and the youngest Wasm frame on the stack throws an exception, we intend to return that as an error variant to the host, right? I am 99% sure the answer is "yes" but if it is ever "no" then we won't really have a way to avoid dealing with native DWARF/SEH unwinding for this stuff.
I guess this seems like the kind of thing we should answer definitively with an RFC.

we don't intend to ever unwind native frames, right?

I think that's probably a good starting point (though this along with all the other details is up for discussion!). Doing otherwise would require us to think pretty carefully about the host/wasm transition in general (including the trap logic, as @alexcrichton mentioned) and the interactions that would have with unwinding. Not to mention that it is a public API change to say that a call from native code back into a Wasm function can throw a system exception and unwind past the caller; e.g. C code might not expect this and might not clean up properly.

Yeah especially with C interop I don't think that we'll ever want wasm code to unwind host frames. Even if we do implement this via DWARF or SEH I would expect that all exceptions are caught at the wasm boundary unconditionally and raised from the entry into the host for when wasm calls the host.
This does leak into other API-looking questions, though. My initial naive thought for how we'd represent this is that we'd change all functions that return Result<T, Trap> to return Result<T, anyhow::Error> (like the rest of Wasmtime's APIs) and we'd add a new wasmtime::Exception type to map onto wasm exceptions. That way ? would naturally propagate exceptions/traps in Rust and you could still inspect the results of an invocation for just an Exception or just a Trap if you really wanted to.

I wanted to write down some further thoughts we've realized recently about libunwind and dwarf exception handling (at least on Linux). Local testing I've done shows that libunwind gets slower as more modules are loaded and is also significantly slower for the first backtrace in the process than subsequent ones:

number of modules
first backtrace
second backtrace

1024
12.34ms
447.34µs

2048
24.26ms
1.49ms

4096
48.74ms
3.19ms

8192
95.92ms
6.06ms

16384
192.15ms
12.98ms

The libunwind being used here is whatever is shipped with glibc, probably the one in libgcc_s. I haven't done much analysis of its own source or why these timings are as slow as they are, but this poses a significant obstacle for embeddings of Wasmtime that want high performance wasm with also loading lots of modules. Backtrace capturing being on the order of milliseconds is also a far cry from the overhead of calling into wasm which is on the order of nanoseconds. These performance numbers were the primary motivator for https://github.com/bytecodealliance/wasmtime/pull/3932.
It's also worth pointing out that "it's ok for traps to be slow" isn't necessarily a given with WASI's proc_exit(0) being implemented by raising a trap. That means that programs, as part of a normal execution, may raise a trap as they exit the process with a 0 return code. Additionally performance-wise libunwind also performs quite bad at high parallelism since unwinding currently takes a global lock in the Rust backtrace crate.
All this is basically to say that while libunwind/dwarf/seh/etc may be appealing from a compiler simplicity point of view it may not be as appealing from a performance point of view. I believe there's a lot of implementations of libunwind, though, and we can probably investigate some other ones to see if they have reasonable performance compared to whatever the system glibc is. That may change things but if it's still somewhat the same we may, for performance reasons, be pushed to mirror SpiderMonkey's or another JS JIT's implementation of unwinding despite the increase in complexity.

With the WasmGC support now available, I think this issue is the last blocker to get Kotlin (and Java as the GraalVM team is working on compiling JVM bytecode to WasmGC + EH)  running on Wasmtime.

FWIW, we have an open RFC discussing Wasm exceptions and working towards consensus on implementation strategy and incremental milestones: https://github.com/bytecodealliance/rfcs/pull/36

@sdeleuze, you can start experimenting (!) with Kotlin right away but without the ability to throw and catch exceptions.
To prevent using EH by Kotlin/Wasm toolchain, you need to add the following lines to your build.
tasks.withType<org.jetbrains.kotlin.gradle.dsl.KotlinJsCompile>().configureEach {
    compilerOptions.freeCompilerArgs.addAll(listOf("-Xwasm-use-traps-instead-of-exceptions"))
}

⚠ The option was added only to allow earlier experimentation with VMs with limited/lack of EH support. In this mode, throwing an exception will lead to a trap (~program termination).

authors: alexcrichton bashor cfallin fitzgen sdeleuze tschneidereit whitequark

repo: bytecodealliance/wasmtime


text:
winch: Aarch64 MacroAssembler completeness

Winch's support for Aarch64 is minimal. The objective of this issue to track the missing items in order to bring the Aarch64 MacroAssembler to parity with the x64 implementation.
If you're interested in taking on any of the elements below, please add your name beside it to signal that you're actively working on it (if you don't have permission to edit this issue, feel free to reach out via Zulip).

[ ] Stack checks ( check_stack)
[ ] address_from_sp
[ ] address_at_sp
[ ] address_at_vmctx
[ ] wasm_store
[ ] wasm_load
[ ] call
[ ] load_ptr
[ ] load_addr
[ ] pop
[ ] cmov
[ ] checked_uadd
[x] float_add (@evacchi)
[x] float_sub(@evacchi)
[x] float_mul(@evacchi)
[x] float_div(@evacchi)
[x] float_min(@evacchi)
[x] float_max(@evacchi)
[ ] float_copysign
[ ] float_neg
[ ] float_abs
[ ] float_round
[ ] float_sqrt
[ ] and
[ ] or
[ ] xor
[ ] shift
[ ] div
[ ] rem
[ ] zero
[ ] popcnt
[ ] unsigned_truncate
[ ] signed_convert
[ ] unsigned_convert
[ ] reinterpret_float_as_int
[ ] reinterpret_int_as_float
[ ] demote
[ ] promote
[ ] cmp
[ ] cmp_with_set
[ ] clz
[ ] ctz
[ ] wrap
[ ] extend
[ ] branch
[ ] jmp
[ ] unreachable
[ ] jmp_table
[ ] trap
[ ] trapz
[ ] trapif

Sorry for looking at this only now -- but I should have some of these instructions implemented soon.  I've been caught up with other things but want to resume work on this ASAP.

@lpereira to prevent accidental duplication of work and to help minimize conflicts and the need for rebases, could you edit the OP issue to add your name next to the instructions you're currently working on implementing? Thanks!

authors: fitzgen lpereira saulecabrera


text:
export func authentication

When the WASM plug-in calls back the host, is there a way to know which WASM plug-in is on the host side, so as to authenticate different WASM plug-ins, to ensure that the interface exposed by the host does not have the problem of permission leakage.

For this it's recommended to store state in the T of Store<T>. Does that work for you?

For this it's recommended to store state in the T of Store<T>. Does that work for you? 重试    错误原因

We've tried that too, and it probably won't solve the problem. Because T is shared in the store, different instances in the same store may tamper with this T to bypass our authentication rules.
I'm curious if there's a way to automatically bring up the module name interface or capability when calling back the host method.

For this it's recommended to store state in the T of Store<T>. Does that work for you?

Could you elaborate a bit on this please?
I don't see right now how that data could be relied on and have a very, very similar "problem"/question to the Op

authors: alexcrichton itachaaa nerdachse


text:
Android 版本的RangersAppLog

您好，请问在哪可以看到Android方面的RangersAppLog集成方式呢

文档：https://datarangers.com.cn/datarangers/help/doc?lid=2230&did=25685
有相关的集成demo吗

repo: bytedance/RangersAppLog


text:
check crc error

ShadowHook Version
1.0.0
Android OS Version
10
Android ABIs
arm64-v8a
Device Manufacturers and Models
Xiaomi8
Describe the Bug
我在hook 指定apk以后，尝试对内存进行crc 。
2024-04-09 11:37:10.485 Zhenxi                  com.zhenxi.hunter                    E  detect_elf_checksum item before 2 /apex/com.android.runtime/lib64/libart.so [71cf948000-71cf949000 rwxp 00347000 103:26 319                           /apex/com.android.runtime/lib64/libart.so] com.zhenxi.hunter
看到一段内存，这段内存是shadowhook留下的 ，
在内存里面是rwxp  。我在遍历这段内存指令的时候，虽然是rwxp但是发生了崩溃 。
1、hook分配的内存是否应该去掉rw ，每次写入的时候再次开启 。
2、为什么这段内存是rwxp ，但是遍历的时候发生崩溃呢？
3、为什么shadowhook 会初始化以后会hook art呢

1、hook分配的内存是否应该去掉rw ，每次写入的时候再次开启 。

shadowhook提供的public API可能存在并发调用，而内存权限是全局的状态，如果要保证可靠性，就需要对“内存权限修改 -> 修改指令 -> 内存权限恢复”的过程加锁，会影响执行效率。从实际一些的角度出发，内存权限恢复也没有必要。

2、为什么这段内存是rwxp ，但是遍历的时候发生崩溃呢？

崩溃问题你需要根据coredump或者tombstone具体分析。

3、为什么shadowhook 会初始化以后会hook art呢

shadowhook初始化后不会"自己去hook art"。

repo: bytedance/android-inline-hook


text:
Data Summary 性能优化

目标: SQLDataSummary SQLPatternDistribution ET 性能优化
现状：
当前执行SQLDataSummary ET过程中会发现整个过程中触发了很多Job，同时这些job中部分是串行触发的，无法充分利用spark集群的并发度，可以作为一个优化的点，
已经发现的包括：
tech.mlsql.plugins.mllib.ets.fe.SQLDataSummary#train
   a. tech.mlsql.plugins.mllib.ets.fe.SQLDataSummary#getQuantileNum
        for each schema 调用了 data.isEmpty() && computePercentile

   b.  tech.mlsql.plugins.mllib.ets.fe.SQLDataSummary#computePercentile
       内部逻辑里面执行了count和index.lookup
       同时这个被顺序调用了3次，改成并发
       k < c时，index.lookup 触发了3次

   c. tech.mlsql.plugins.mllib.ets.fe.SQLDataSummary#getModeNum
       ! dfWithoutNa.isEmpty 时，for each schema 调用了count

tech.mlsql.plugins.mllib.ets.fe.SQLPatternDistribution#train
for each schema 执行了 pattern_group_df.count()

注意点：
以上并不一定是全部，研发实际开发调优过程中发现新的点 也一起更新到这个issue，或关联进来。
补充一点：
@hellozepp  通过df 的 cache发现性能提升明显，所以ET侧的cache也是一个点

from @hellozepp 3. 算法剪枝
a. 下属算子可以通过一次select求出所有指标值，而不是单个计算后再union起来

b. 剪掉主键候选者；唯一值比例=100% 实际上就是 主键候选者=true ; 小于100%,主键候选者=false

c. 剪掉空白、非空计数;非空计数= 总数-（空值+空白） 所以只要有总数和空值，空值、空白、非空计数就都有了

尽可能缓存数据，减少重复计算
a. colWithFilterBlank 只有少数指标没有使用，是否可以对源表统一做一次colWithFilterBlank处理，然后cache该结果集，供其他指标使用
b. computePercentile 被调用多次，函数中sortBy 和 count 存在重复计算，可以做复用

优化的点：
1）剪掉主键候选者；唯一值比例=100% 实际上就是 主键候选者=true ; 小于100%,主键候选者=false
2）剪掉空白、非空计数;非空计数= 总数-（空值+空白）
3）computePercentile 的计算里，RDD做了 cache 操作
4）避免 df.isEmpty 取反操作, 取消 !df.isEmpty

PR：https://github.com/byzer-org/byzer-extension/pull/54/files

authors: ZhengshuaiPENG ckeys fishcus

repo: byzer-org/byzer-extension


text:
🛑 www.bellavista.sk is down

In 803c26f, www.bellavista.sk (https://www.bellavista.sk) was down:

HTTP code: 503
Response time: 644 ms

Resolved: www.bellavista.sk is back up in dfaea6c.


text:
🛑 www.zisk.eu is down

In 5afe265, www.zisk.eu (https://www.zisk.eu/sk/Home.alej) was down:

HTTP code: 403
Response time: 747 ms

Resolved: www.zisk.eu is back up in 4b35f1f.


text:
🛑 cms5.alejtech.eu is down

In 1b4fa75, cms5.alejtech.eu (http://cms5.alejtech.eu/UserSystem/login/login.alej) was down:

HTTP code: 403
Response time: 306 ms

Resolved: cms5.alejtech.eu is back up in 46ab134.


text:
Make clip-path configurable (relative/absolute)

I have some problems with converting generated SVG to PDF. One of them is that clip-path attributes of g's are absolute. Can you please provide an option for enabling/disabling relative urls?
I found commit 262672f for Issue #134 and propose to make it like this:
function getClipPath(id) {
    var relative = $$.config.relativeClipPath || window.navigator.appVersion.toLowerCase().indexOf("msie 9.") >= 0;
    return "url(" + (relativeClipPath ? "" : document.URL.split('#')[0]) + "#" + id + ")";
}

Cheers!

+1
Having the same problem when using C3 by loading the HTML document with res:// protocol (compiled in EXE).
Perhaps there is an alternative solution for 5813ff389fa08f878165d1c6375d817053b6917e, so that there must not be an absolute URL at all.

+1

+1

1

authors: alexsurg duderoot pedrostc rand0m86 thojo


text:
Turn on displaying null values in results

It's useful to see how many nulls and NAs are in a column

looks like the summary is only giving us a bool for nulls (true/false if there are any nulls in the column) - I've turned it on, but eventually we'll want to count the number of nulls

authors: jayvachon kanarinka


text:
Change Dismiss infusion / spell to a swift action

Is your feature request related to a problem?
Currently Dismiss infusion / spell is a standard action this waste a characters whole round just to remove a spell
Describe the solution you'd like
Change Dismiss infusion / spell so that it is a swift action but can't be done in the turn you cast the spell or infusion
Describe alternatives you've considered
No response
Additional context
No response

Out of scope for ToyBox.
Seems like it might not be too hard to implement as a separate mod; maybe ask on the Discord if someone could implement this?

repo: cabarius/ToyBox


text:
🛑 CBTB Coffee House Shop is down

In 7079741, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 1414 ms

Resolved: CBTB Coffee House Shop is back up in 59bfb52.

repo: cachetech/service-status


text:
🛑 CBTB Coffee House Shop is down

In 76fa597, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 1207 ms

Resolved: CBTB Coffee House Shop is back up in f038c1a after 25 minutes.


text:
🛑 CBTB Coffee House Shop is down

In b64016a, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 939 ms

Resolved: CBTB Coffee House Shop is back up in f885d03 after 13 minutes.


text:
add workaround for tmpdir errors on Darwin, fixes #255

Darwin always sets a TMPDIR. As the mkNakedShell removes the shell the TMPDIR gets null and breaks a lot of applications like VSCode with Direnv.
Before:

After:

I guess some pipelines needs to be skipped when the PR is not in cachix org :)

Could you rebase on top of main to see if that fixes CI?

seems to work

authors: domenkozar shyim

repo: cachix/devenv


text:
Interferes with pathfinding in Drag Ruler?

See https://github.com/manuelVo/foundryvtt-drag-ruler/issues/259

Fixed in v0.6.4.

repo: caewok/fvtt-light-mask


text:
Added a ModulePath folder check to be sure the directory exists ...

I have some old left-over directories who used the FooBar, BarBiz folder structure and in the current situation, this will become str_slug -> studly_case, so Foobar, Barbiz.
I added a check if the current folder-directory exists, otherwise use the FooBar folder structure ...

Thanks!

authors: kaidesu nickurt

repo: caffeinated/modules


text:
Feat: update 2.5.1, assert_ne! macro, Debug derivable trait

Update scarb -> 2.5.1
Cover assert_ne! macro in Chapter 9 - How To Write Tests. ("Testing Equality with the assert_eq! and assert_ne! Macros" and "Adding Custom Failure Messages" sections added).
Mention Debug derivable trait in Appendix C (#454)

I'm not sure if we should keep "Using assert" and "assert! and assert_eq! macros" in Chapter 10 - Unrecoverable Errors with panic ?

This change is

@julio4 can you rebase

There's something weird with the diffs 🤔

@julio4 can you rebase

Done!

repo: cairo-book/cairo-book


text:
targetExtension is checked against 0

I have a build config like the following:
var tree = new Filter(...);
tree.extensions = [ 'js', 'js.tmpl' ];
tree.targetExtension = null;

This causes the filter to output foo.null, bar.null etc instead of foo.js and bar.js.tmpl.
I can see in https://github.com/caitp/cauliflower-filter/blob/master/filter.js#L79 that targetExtension is checked against 0. Setting
tree.targetExtension = 0;

fixes my build. Is this on purpose?

Should be  void 0, probably crept in by accident. Patches welcome

hmm, but it won't work if you want to set it to null, I guess that's an API compat thing

authors: caitp mntnoe

repo: caitp/cauliflower-filter


text:
How To Use

I've been following this repository for over a month now but I'm not totally sure what it's supposed to do.
Seems to me to have something to do with intellisense for case scripts but I'm not sure.
Any plans on adding a section on how to use in the readme?

Bakery is still work in process and still undergoing major refactoring, but when we've baked things and shipped something it's on the agenda to update readme and provide documentation,
Very simplified what it does. basically it replicates the code generation Cake does for its DSL, i.e. provides functionality needed for preprocessor directives, mapping script lines to generated lines, reflects over addins, namespace imports etc.
Which will provide i.e. editors like VSCode (via OmniSharp) with the meta data it needs to provide intellisense. But it's potential could be way beyond that.

In the troubleshooting section is says to check omnistar logs: https://cakebuild.net/blog/2017/11/intellisense-vscode
I don't know what an omnistar is, I can google instructions on turning on logging but I'm not sure I've found the right thing.  Can someone point me in the right direction?

@fschwiet I can't find omnistar. Isn't it omnisharp?

@fschwiet what is being referred to is this:

Omnisharp runs inside VSCode, and if there are any problems with it, they should be written to the Output Log.

Where do you see OmniStar in that blog post?

I wrote omnistar by mistake, I meant to reference Omnisharp.  Thanks for recognziing what I meant to ask anyhow.

Instructions how to enable IntelliSense in Visual Studio Code is now available at https://cakebuild.net/docs/editors/vscode/intellisense.

authors: Meir017 SIkebe devlead fschwiet gep13 pascalberger patriksvensson

repo: cake-build/bakery


text:
build.sh downloads old version of nuget

lots of things just don't work with the nuget 2.8 that's downloaded.
I fixed many issues by actually downloading this version from build.sh
https://dist.nuget.org/win-x86-commandline/v3.4.4/NuGet.exe

I'm not sure if there's a better url to download a 'mono' version of NuGet, but the 2.8 version currently won't cut it for several scenarios
(Maybe a better issue on nuget repo)

@KyleGobel this has now been taken care of in the latest version.  Let us know if you run into any further issues.

repo: cake-build/example


text:
🛑 XMR EU Servers is down

In 9209f5d, XMR EU Servers ($XMR_EU) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XMR EU Servers is back up in 08631ff after 8 minutes.

repo: cake-tech/upptime-cakewallet


text:
🛑 XMR EU Servers is down

In d557ddb, XMR EU Servers ($XMR_EU) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XMR EU Servers is back up in f17c199 after 39 minutes.


text:
Selections GUI updates: Adding select by time or warming level approach

Description of PR
This PR is linked to PR #449 in climakitae; please see that PR for more information on the changes here.
Summary of changes and related issue
Relevant motivation and context
Dependencies required for this change?
Fixes # (issue), delete if not necessary
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

This looks great! I love the UI and I think it makes a lot of intuitive sense and will be super helpful for WL integration for notebooks. I wanted to ask about a couple things:

Would it be possible to toggle the entire "Warming Levels Approach" or "Time-Based Approach" panels to be visible or invisible depending on which approach you choose at the top? Currently, choosing WL will make time-based selections into n/a, but I'm wondering if it might be even cleaner to toggle the entire panel away (i.e. when choosing WL approach, the time-based approach disappears, and vice versa).
When toggling between the two approaches, my former approach's params get reset. For example, if I set WL's to 2.0 and 2.5, then toggle the time-based approach and come back to the WL approach, my params get reset to just the 2.0 WL. Is it possible to keep the params from resetting between toggles?

These are just questions/suggestions, but nothing breaking when I've been testing either. This looks good to me to merge if you'd like to keep it as is!

This looks great! I love the UI and I think it makes a lot of intuitive sense and will be super helpful for WL integration for notebooks. I wanted to ask about a couple things:

Would it be possible to toggle the entire "Warming Levels Approach" or "Time-Based Approach" panels to be visible or invisible depending on which approach you choose at the top? Currently, choosing WL will make time-based selections into n/a, but I'm wondering if it might be even cleaner to toggle the entire panel away (i.e. when choosing WL approach, the time-based approach disappears, and vice versa).
When toggling between the two approaches, my former approach's params get reset. For example, if I set WL's to 2.0 and 2.5, then toggle the time-based approach and come back to the WL approach, my params get reset to just the 2.0 WL. Is it possible to keep the params from resetting between toggles?

These are just questions/suggestions, but nothing breaking when I've been testing either. This looks good to me to merge if you'd like to keep it as is!

No, it's not possible to make the parameters dissappear :( I agree that would be a huge improvement but I currently don't think it's an option with panel/param. I too find it "messy" but it's the best option we have at the moment.

Hmm... that may be possible but I'm not sure how to do it. I agree that would be a nice feature. Would be nice to look into later down the line (will add it to my mental backburner list)

authors: claalmve nicolejkeeney

repo: cal-adapt/climakitaegui


text:
Add support for zod lazy schema definitions

These are used to support recursive types in schemas. Here's an example of one:
const baseNewNodeSchema = z.object({
  id: z.string(),
  properties: z.record(z.any())
})

export type Node = z.infer<typeof baseNewNodeSchema> & {
  children: Node[]
}

export const NodeSchema: z.ZodType<Node> = baseNewNodeSchema.extend({
  children: z.lazy(() => NodeSchema.array()),
})

i did a little investigation on this because I ran into a mysterious issue where my schema had a lazy type in it (even though I didn't create it with one)
this could be done by calling schema._def.getter() to get the rest of the zod schema
should probably also include some sort of recursive depth check as well
just some thoughts

authors: jaketaylorpro levi

repo: calasanmarko/trpc-swift


text:
Enable vim bindings for all REPL modes (history, shell, etc)

Currently, the custom bindings are loaded into the juliamode mode, and so do not carry over when the user navigates to another mode type (such as history).
This ruins a user flow when they navigate through their history with j and k since those keys stop working once a new mode is hit.
One potential (albeit hacky) solution would be to inject custom bindings into all available REPL modes.
Perhaps we could instead intercept key strokes before they arrive at any mode--similar to the Escape Key detection code.
I can't think of any clear reasons why we need to bind at the mode level, and that was the initial route simply because it is where the modeline can be easily altered (and where there is existing key map logic).
By moving above the mode level abstraction, one could view the REPL more as a line editor of a history ledger of commands

Also, the Escape key might be used as a "return to Julia mode" if the user is in normal mode in a different REPL mode (e.g. history). Possibly using a configurable feature flag

This has been added in ddea031b11b6ff315d2f1d05cac5e8713c17f9e0 and is available in 0.3.0


text:
Connecting DIME data to names in Cal-Access

Code finding DIME ids in Cal-Access names. It takes a while to download the files from the Stanford site.

Well, that certainly looks better.
FYI, instead of trying to run all of this, the 3 tables I added can be downloaded from here:
http://opencalaccess.org/calaccess_raw_20150509_000246_PDT/

See issue #216


text:
[docs] Have more details about FormControl, FormGroup etc.

So i've been trying to understand what are the different From* components are used for and what are the differences between them and what i should use with what.
I was forced to go to the source to actually understand what they do.
Should we have a more detailed information about those components? The documentation on the API doc is pretty minimal
Currently they are used in several examples yet i didnt fully understand their purpose.
For example, in the checkbox example all the checkboxes are placed in a FormGroup. They can be placed in a FormControl as well with a FormLabel (am i correct?), yet if i put a disabled prop on FormControl, the checkboxes are not disabled. Not sure if that's intended or not
<FormControl disabled>
  <FormLabel component="legend">Header</FormLabel>
  <FormControlLabel control={<Checkbox value="A"} label="A" />} />
</FormControl>

I have added more information to the API pages. It's better but not perfect.

I believe the example mentioned above would be useful to have on the FormControl documentation page.

@oliviertassinari at the moment I don’t feel confident in my full
understanding of the design and what the example should be. I’ll take a
deeper dive into the subject and may be could do something about it.
On Thu, 16 May 2019 at 15:31, Olivier Tassinari notifications@github.com
wrote:

@Gems https://github.com/Gems Do you want to add such an example for
the composition of the form input elements?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mui-org/material-ui/issues/8159?email_source=notifications&email_token=AACHTC7FPIRMKL2SF43K5D3PVVO2HA5CNFSM4D2RHSMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVRZ7PQ#issuecomment-493068222,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACHTCY7JADF7NPDDYMYKRTPVVO2HANCNFSM4D2RHSMA
.

authors: Gems oliviertassinari slavab89

repo: callemall/material-ui


text:
[Autocomplete] Disable browser default autocomplete popup

In AutoComplete component, TextField autoComplete attribute should be off. Otherwise it will show browser default autocomplete suggestion popup

@mbrookes @oliviertassinari any update

Alright, I'm sold https://github.com/jquery/jquery-ui/blob/master/ui/widgets/autocomplete.js#L91.
@vishalvijay Thanks :+1:.

authors: oliviertassinari vishalvijay


text:
[eslint] Refactor some component to use const instead of let

I have used the auto-fix option of eslint with this homemade fix function:
fix: function(fixer) {
  return fixer.replaceTextRange([declaration.start, declaration.start + 3], "const");
}

I hade to refactor some component too. Be careful when reviewing :grin:.

Looks good to me :+1:
This PR makes me really happy.

This is awesome :heart_eyes:
However, this PR touches a lot of files as it is. Any single PR merge is gonna conflict :grin:

Any single PR merge is gonna conflict

It's already the true ><. Alright, I'm gonna do it in two steps.
In this PR, I'm gonna only apply the manual changes that only affects 3 or 4 files. Once the first PR is merged. I will wait for the right moment to apply the auto fix.

@oliviertassinari That sounds great :+1: Thanks a lot :+1: :+1:

That's good to be reviewed again. I feel like I will have to enable the ninja mode for the second PR :boom:. There is too many PR merged every days :flushed:.

That looks good :+1:

This is great thanks a lot :+1: :+1:

authors: alitaheri newoga oliviertassinari


text:
[Tab] Style prop is not functional

Fixes #3596.

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

@maxpechenin That sounds like a good idea :+1:.

@maxpechenin Thanks!

authors: maxpechenin oliviertassinari


text:
Reset to factory state

gibt ja immer mal wieder rücksendungen in denen das richtige hex drauf ist. da wäre ne tastenkombination praktisch um an den anfang des demo/test programs ohne kopieren zu kommen.

Programm 5, wenn das frei wird?

authors: Amerlander fabianhugo


text:
The repo is outdated, I forked it

Hi,
I see this repo is very old, so I forked it and made a production-ready container that is building for each new release automatically.
https://github.com/riotkit-org/docker-django-wiki

Hi, I'm glad you found this project useful and forked it. If you want to propose changes to this project use PRs. Thanks.

authors: blackandred camandel

repo: camandel/docker-django-wiki


text:
Readiness CL: Change Status column item 7 to "Y"

          Change Status column item 7 to "Y"

Originally posted by @tanjadegroot in https://github.com/camaraproject/CallForwardingSignal/pull/75#discussion_r1692759663

Fixed in: https://github.com/camaraproject/CallForwardingSignal/pull/85

repo: camaraproject/CallForwardingSignal


text:
Rel 0.1.5-wip

What type of PR is this?

bug

What this PR does / why we need it:
Error correction to be compliant with MegaLinter
Which issue(s) this PR fixes:
https://github.com/camaraproject/CallForwardingSignal/issues/28

Sure, you can merge it.
The linting workflows will be added by separate PR.

authors: FabrizioMoggio rartych


text:
Provide feedback and align with upcoming explicit subscription related changes in commonalities

Problem description
There are currently active discussions in commonalities on solving some issues regarding explicit subscriptions. This will bring some breaking changes to the APIs which offer explicit subscriptions. The proposal has been documented here https://github.com/camaraproject/Commonalities/issues/185.
Kindly provide your feedback from the perspective of this subproject. We already have feedback from other subprojects which use explicit subscriptions (for e.g. device-status, device-location and sim-swap). It will also help this subproject to plan/prep for upcoming changes.
Possible evolution
Provide feedback to the proposal https://github.com/camaraproject/Commonalities/issues/185 as comments.
Alternative solution

Additional context

Hello ConnectivityInsight team,
New model for subscription is now defined and should be use in all our CAMARA subscription resource.
You have the guideline here and a subscription template here.
Happy to answer any question :)
Thanks for your consideration.
cc: @shilpa-padgaonkar

fixed as part of #40

repo: camaraproject/ConnectivityInsights


text:
Add multiple device in verify location

This PR is related to this issue: https://github.com/camaraproject/DeviceLocation/issues/32

We decided to close this request because we want to go on with another approach regarding multiple device in verify location.

repo: camaraproject/DeviceLocation


text:
[Question] Together AI

Required prerequisites

[X] I have read the documentation https://camel-ai.github.io/camel/camel.html.
[X] I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
[X] Consider asking first in a Discussion.

Questions
I am using togerther AI service, is there any way to use Togerther Ai for CAMEL? can you give me an example?

Hey @dangyuuki123 , we have one PR to support Together AI here: https://github.com/camel-ai/camel/pull/843
If you have time you can also help with the code review, this feature will be added to CAMEL this week

repo: camel-ai/camel


text:
The automated release is failing 🚨

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.
semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://x-access-token:[secure]@github.com/camera-2018/hdu-cs-wiki.
This can be caused by:

a misconfiguration of the repositoryUrl option
the repository being unavailable
or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.
semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://x-access-token:[secure]@github.com/camera-2018/hdu-cs-wiki.
This can be caused by:

a misconfiguration of the repositoryUrl option
the repository being unavailable
or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.
semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://x-access-token:[secure]@github.com/camera-2018/hdu-cs-wiki.
This can be caused by:

a misconfiguration of the repositoryUrl option
the repository being unavailable
or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.
semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://x-access-token:[secure]@github.com/camera-2018/hdu-cs-wiki.
This can be caused by:

a misconfiguration of the repositoryUrl option
the repository being unavailable
or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨
Your semantic-release bot :package::rocket:


text:
Google has depreciated sha1 for certs

Google Chrome will stop trusting SHA1 after Jan 2017:
http://googleonlinesecurity.blogspot.com/2014/09/gradually-sunsetting-sha-1.html
Suggest changing the default in: puppet-openssl/templates/cert.cnf.erb
to sha256

@cjeanneret care to comment on that?

Pull request for this above, this change is working for me.
I was trying to write a test to verify this behaviour, however as it is handled inside the openssl binary we can't simply trap the existing calls as best I can tell.  I'd need to re-open the file and verify the signature, and it was not clear for me how to do this.
If someone can guide me to running a command and verifying the output I'd gladly add it in.
Example verification:
openssl req -in subject.csr -noout -text|grep "Signature Algorithm"
Signature Algorithm: sha256WithRSAEncryption
In the mean time if you want to work around this issue, you can simply clone cert.cnf.erb into your module/manifest, and then pass cnf_tpl to openssl::certificate::x509

No real meaning for a unit-test on this particular point. It might have been a variable though, but enforcing good practices is better.
I'm pretty sure this kind of test cannot be done as a "standard unit-test", but with an acceptance test, where puppet is really applied, creating files and so on so that we can check them "in place". Basically, the acceptance test would call ruby native SSL lib in order to get certificate info. Maybe a bit overkill in this case ;).

Thanks for merging, and the notes about the test.

authors: cjeanneret edestecd lathiat raphink

repo: camptocamp/puppet-openssl


text:
Selected item is not highlighted in forms

Describe the Bug

In the forms after we make a selection in the execution platform the radio button selection and the highlighting are in different items.
Steps to Reproduce

Select the Camunda BPMN platform in the forms for execution.
We could see that the selection and highlight appear in the same item as selected.
Try to change the selection to Camunda cloud.
We could see that the selection is on camunda cloud and the blue highlight is still in the platform.

Expected Behavior

Selected item should be highlighted as well.
Environment

OS: [Windows 11]
Camunda Modeler Version: [4.12]

https://user-images.githubusercontent.com/85225325/145243285-25d6a4a5-a0a1-4355-9bba-26ac484a6418.mp4

Fixed via https://github.com/camunda/camunda-modeler/pull/2573.

How is this fixed via https://github.com/camunda/camunda-modeler/pull/2573?

There is only one input in the new engine profile overlay so there is no case of the wrong input being focused.

:+1: Thanks for clarifying.

authors: GeethaParthasarathy nikku philippfromme

repo: camunda/camunda-modeler


text:
Cloud deploy modal is cut off from the window.

Describe the Bug

Choose to deploy a BPMN diagram via cloud we could see that the deploy diagram modal is cut-off from the windows.
Steps to Reproduce

Create/Open a BPMN diagram in the Camunda 8 Platform
Choose to deploy in any of the cloud versions and choose Camunda Platform self-managed and oAuth for authentication.
We could see that the deploy diagram modal is cut off from the windows.

Expected Behavior

The depoly diagram modal should fit inside the window.
Environment

OS: [ Windows 10]
Camunda Modeler Version: [5.0.0 Nightly]
Execution Platform: [Camunda Cloud]

This isn't expected behavior. Ensure that an overlay dialog does not grow out of the viewport.
I quickly hacked the dialog to showcase how it should work:
https://user-images.githubusercontent.com/938244/161297002-2c378121-c40d-41ce-801e-a84256c5b7a2.mov
This should be done for all overlays including what's new:
https://user-images.githubusercontent.com/938244/161297104-86d66673-9300-4a40-89fb-54a137e7fd8a.mov

Thanks both for your feedback 👍 Moving this to backlog since it's not blocking the release.


text:
[feature] gold reminder should take into account buyback gold and scale with time

Gold reminder assistant
Pre-10 minutes: warn every 500 gold increment
10 to 30 minutes: warn every 1000 gold increment
30+ minute: warn every 1000 gold increment, taking into account buyback cost if you have buyback available
1000 gold to spend: mild reminder (ka-ching sound)
2000 gold: moderate reminder ("you have a lot of money")
3000+ gold: aggressive reminder ("you really have a lot of money")
Buyback reminder assistant
Given your buyback is off cooldown,
When you spend money such that you can no longer afford buyback
Then play a warning message

Bot is still a bit chatty when hovering around an increment mark (i.e. you reach 1000 gold, get a reminder, buy a small item, hit one creep, immediately reach 1000 gold again, get another reminder) but we'll see how annoying it is in practise.

Turns out it's annoying. Re-opening to fix chatty bot at thresholds

repo: cannawen/dota-gsi-discord-bot


text:
TemplateDoesNotExist: cannlytics_website/pages/account/sign-up.html

Template not found when user navigating to login pages:
django.template.exceptions.TemplateDoesNotExist: cannlytics_website/pages/account/sign-up.html, cannlytics_website/pages/account.html, cannlytics_website/pages/account/account.html, cannlytics_website/pages/general/account.html
at select_template (/usr/local/lib/python3.8/site-packages/django/template/loader.py:47)
at resolve_template (/usr/local/lib/python3.8/site-packages/django/template/response.py:63)
at rendered_content (/usr/local/lib/python3.8/site-packages/django/template/response.py:81)
at render (/usr/local/lib/python3.8/site-packages/django/template/response.py:105)
at _get_response (/usr/local/lib/python3.8/site-packages/django/core/handlers/base.py:143)
at _get_response (/usr/local/lib/python3.8/site-packages/django/core/handlers/base.py:145)
at inner (/usr/local/lib/python3.8/site-packages/django/core/handlers/exception.py:34)

Sign up has been moved to https://console.cannlytics.com/account/sign-up.

repo: cannlytics/cannlytics-website