Paramount plus subtitle

How to download subtitles in italian language from third season of series Evil? , paramount plus USA.

Please show the verbose log where a command to do this according to the manual is failing.

this should probably be closed. at least the video I tested, is only DRM:
> paramount -b iOXKwejhCZmDoNeAeqtLv7eztBs1hA3B
GET https://www.paramountplus.com/apps-api/v2.0/androidphone/video/cid/iOXKwejhCZmDoNeAeqtLv7eztBs1hA3B.json?at=ABAAAAAAAAAAAAAAAAAAAAAA9jDfkJRdbo%2BRDNoMFGetppwEHT95XGHp0Yb%2BIu1zY%2B4%3D
GET http://link.theplatform.com/s/dJ5BDC/media/guid/2198311517/iOXKwejhCZmDoNeAeqtLv7eztBs1hA3B?assetTypes=Downloadable&formats=MPEG4
panic: 412 Precondition Failed

> paramount -b iOXKwejhCZmDoNeAeqtLv7eztBs1hA3B -d
GET http://link.theplatform.com/s/dJ5BDC/media/guid/2198311517/iOXKwejhCZmDoNeAeqtLv7eztBs1hA3B?assetTypes=DASH_CENC&formats=MPEG-DASH
GET https://www.paramountplus.com/apps-api/v2.0/androidphone/video/cid/iOXKwejhCZmDoNeAeqtLv7eztBs1hA3B.json?at=ABAAAAAAAAAAAAAAAAAAAAAA9jDfkJRdbo%2BRDNoMFGetppwEHT95XGHp0Yb%2BIu1zY%2B4%3D
GET https://www.paramountplus.com/apps-api/v3.0/androidphone/irdeto-control/anonymous-session-token.json?at=ABAAAAAAAAAAAAAAAAAAAAAA9jDfkJRdbo%2BRDNoMFGetppwEHT95XGHp0Yb%2BIu1zY%2B4%3D
POST https://cbsi.live.ott.irdeto.com/widevine/getlicense?CrmId=cbsi&AccountId=cbsi&SubContentType=Default&contentId=iOXKwejhCZmDoNeAeqtLv7eztBs1hA3B
1.33%   12.59 megabyte   10.59 megabyte/s

so I dont know what good getting the subtitles will be.


Build failure on 32-bit platforms

From this i386 log:
error[E0308]: mismatched types
   --> acme_common/src/crypto/openssl_certificate.rs:111:39
    |
111 |         let now = Asn1Time::from_unix(timestamp)?;
    |                                       ^^^^^^^^^ expected `i32`, found `i64`
    |
help: you can convert an `i64` to `i32` and panic if the converted value wouldn't fit
    |
111 |         let now = Asn1Time::from_unix(timestamp.try_into().unwrap())?;
    |                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Maybe the timestamp should not hardcode i64..

Thank you for reporting it!


Mod does not work

I used /disguise and Nothing! Like command does not exist
How can I fix this?
Cheers,
Mata

Uhmmm ... do you have cheats? Silly question, but are you sure that mod is loaded?


Write tombstone events with "quick append" processing on failures

I don't have a concept for this quite yet except for some vague idea about using autonomous sub transactions
Scenario:

Using quick append events, and in a batch
Some event inserts go in, but later ones fail, blowing up the whole transaction. Quick append isn't able to capture the sequence numbers that were used
The sequence has already been checked out and this causes a gap in the high water mark
The high water detection has to pause and skip, just slowing down teh projection

Soltution:
Magically find a way to write tombstones for quick append some how so the high water detection doesn't have to skip

i'm back to thinking this isn't really feasible


Profiling graph

This PR provides mvp of merging algorithm for the profile graph.
I will procede with refactors, some code comments, more features in following PRs

Merging, as probably nobody will be reviewing the logic


[Doc] add README info on development

The current README does not walk users through getting started with the development process. What tools are required, building the app, packaging, etc.

Closing, addressed by #3


:+1: Setup issue & pull request template

Summary
As the title suggests.
Expected

When create new issue in GitHub, preset template text for issuing
When create new pull request in GitHub, preset template text for opening pull request

issue template is exists.
https://github.com/takoba/create-typescript-app/tree/main/.github/ISSUE_TEMPLATE


Feature: Implement Streaming Half-Space-Trees

Streaming Half-Space-Trees (HS-Trees), a fast one-class anomaly detector for evolving data streams.
Theory and the pseudocode algorithm can be reviewed in:
S. C. Tan, K. M. Ting, and T. F. Liu, “Fast anomaly detection for streaming data,” in IJCAI Proceedings-International Joint Conference on Artificial Intelligence, 2011, vol. 22, no. 1, pp. 1511–1516.:

Changes proposed in this pull request:

An implementation of streaming Half Space Trees.
[TODO] Test is missing on this commit. I have a dummy branch where I created some tests, but it is reading from a big csv file which was mentioned in the paper. If you have any suggestion
on how to integrate any tests on this PR I would be happy. Link for the dummy brach for testing: https://github.com/mertozer94/scikit-multiflow/tree/Silly-tests-Half-Space-Trees

Checklist

[ ] Code complies with PEP-8 and is consistent with the framework.
[ ] Code is properly documented.
[ ] Tests are included for new functionality or updated accordingly.
[ ] Travis CI build passes with no errors.
[ ] Test Coverage is maintained (threshold is -0.2%).
[ ] Files changed (update, add, delete) are in the PR's scope (no extra files are included).

I have started looking into the code. My first question is about the 3 classes (HalfSpaceTrees, HalfSpaceTree and HalfSpaceTreeNode) declared instead of the 2 in the MOA implementation (HSTrees and HSTreeNode). Why is this?
It seems to me that this adds complexity when reading the code and differentiates both implementations. However, if this is closer to the author's work I am ok with it.
I will leave some comments in the code. I won't cover all the classes at this point but will focus on HalfSpaceTree and HalfSpaceTreeNode

Thanks for the changes @mertozer94 !
I have marked as "resolved" the corresponding comments. Let me know if you need help with the validation testing.
On the other hand, the errors in the Codecov Report will be addressed with functional tests once we are sure the implementation is correct.

Thanks for the changes @mertozer94 !
I have marked as "resolved" the corresponding comments. Let me know if you need help with the validation testing.
On the other hand, the errors in the Codecov Report will be addressed with functional tests once we are sure the implementation is correct.

My tests are complying with the results of the paper, what kind of functional tests I should focus on?

The idea behind our tests is to protect the code against unintentional changes from future development, whereas implementation correctness is tested as part of the PR process.
Considering this, we usually favor the usage of generators given that they are requirement-wise efficient. However, if there is a case where a generator is not the best option then we can consider using a data set. The most important elements are reproducibility and coverage.
If you have installed pytest then you can evaluate coverage offline as follows:
pytest --cov=src/skmultiflow tests/anomaly_detection/test_half_space_trees.py --showlocals -v

Regarding this comment related to the depth of a HalfSpaceTreeNode:

Actually, this was the root of the performance difference that I have reported, now, depending on the parameters, auc score is around 0.998.

Does this means that the default value should be set as in MOA (depth=1) or can it be set by the user?

@mertozer94 It might be usefult to take a look into /tests/trees/test_hoeffding_tree.py for some ideas

Thank you for the clarification.

Regarding this comment related to the depth of a HalfSpaceTreeNode:

Actually, this was the root of the performance difference that I have reported, now, depending on the parameters, auc score is around 0.998.

Does this means that the default value should be set as in MOA (depth=1) or can it be set by the user?

I would say that we can set the default value as 1 and not leave it to the user.

I would say that we can set the default value as 1 and not leave it to the user.

Sounds good to me.

Hello @jacobmontiel I needed a generator which was capable of generating values between 0 to 1. I found SEAGenerator the most suitable one. It creates values between 0 to 10 and I am simply scaling those into 0 to 1. I have included a really simple test case which you can find in tests/anomaly_detection/test_half_space_trees

Thanks @mertozer94
It seems that codecov is broken for the PR. This is likely related to the lack of support for "force-pushed" commits. Could you run locally the coverage report?

Thanks @mertozer94
It seems that codecov is broken for the PR. This is likely related to the lack of support for "force-pushed" commits. Could you run locally the coverage report?

Of course, here is the result when I run it locally:
/home/mert/.local/lib/python3.6/site-packages/skmultiflow/anomaly_detection/half_space_tree.py                             55     55     0%
/home/mert/.local/lib/python3.6/site-packages/skmultiflow/anomaly_detection/half_space_tree_node.py                        11     11     0%
/home/mert/.local/lib/python3.6/site-packages/skmultiflow/anomaly_detection/half_space_trees.py                           176      3    98%

And in total:
TOTAL                                                                                12255   2410    80%
P.S: I had to remove test_show_versions.py because I had the following error:
../../.local/lib/python3.6/site-packages/skmultiflow/utils/_show_versions.py:61: ImportError
ImportError: cannot import name '_get_blas_info'

Thanks @mertozer94
If I am correct these two files are not part of your PR:

 /home/mert/.local/lib/python3.6/site-packages/skmultiflow/anomaly_detection/half_space_tree.py                             55     55     0%
 /home/mert/.local/lib/python3.6/site-packages/skmultiflow/anomaly_detection/half_space_tree_node.py                        11     11     0%

The PR is almost ready. I was revisiting the open actions from the review. Please check my comments. Also, I added some comments in your test.

Thanks @mertozer94
If I am correct these two files are not part of your PR:

 /home/mert/.local/lib/python3.6/site-packages/skmultiflow/anomaly_detection/half_space_tree.py                             55     55     0%
 /home/mert/.local/lib/python3.6/site-packages/skmultiflow/anomaly_detection/half_space_tree_node.py                        11     11     0%

The PR is almost ready. I was revisiting the open actions from the review. Please check my comments. Also, I added some comments in your test.

Yes they are not part of the the PR.

Here are my last "minor" comments. The PR is almost ready, thanks for your understanding.
Note: Please avoid force pushing the commits in your branch since this could corrupt the PR. [Source]

No worries, since it was my first PR in a open source library I was expecting to have a lot of comments. Now I know more about the structure so I am more prepared for the next PR :)
I was squashing latest fix in order to make PR ready to merge all the time.

@jacobmontiel I have pushed the requested changes.

Awesome work @mertozer94 and thanks for your patience during the PR review.
All changes have been implemented. The PR is ready to merge.

thanks for your patience during the PR review.

@jacobmontiel It's a pleasure :) I feel more comfortable with the environment right now and I would like to continue to implement anomaly detection algorithms, if it is possible of course.

@mertozer94, of course. We are open to contributions and collaborations. If you already have an anomaly detection method in mind please create a new issue and we can discuss it. We will look into this on our side as well.


Update CI and repository settings

Set minimum Go version to 1.19, the current earliest supported version upstream. This has the effect of trimming the go.sum file because of a change in how modules are downloaded.
Increase the timeout on golangci-lint. I've been seeing it fail in my experimentation.
The fixture-building seems to be nondeterministic. I'm setting gitattributes to show more files as text in the interest of providing better diffs when the fixture test fails.

thanks! It seems like changing the testdata introduced errors in CI.

Yup. I tried to fix it, but the derivation code is complex enough that I'm going to instead avoid upgrading Nix for the fixture tests.

Alright, I'm fairly confident this should pass now. (I've run the fixture generation with Nix 2.14 locally.)

Oh, I did not see this PR before doing https://github.com/nix-community/go-nix/pull/109 and https://github.com/nix-community/go-nix/pull/110. Can check which of your CI-related fixes should still be ported from here?

Done. PTAL

Done.

Thanks!


grep: warning stray \ before /

Not sure if this is relevant, seems like its not
https://lists.gnu.org/archive/html/grep-devel/2022-06/msg00006.html

I will close this for now. It's just a warning and doesn't seem to make any difference.


run-trust4 is very slow, what should I do to speed, my data is bulk BCR-seq

[Tue Nov  5 13:52:15 2024] Read in and count kmers for 112200000 reads.
[Tue Nov  5 15:05:27 2024] Found 109640387 reads.
[Tue Nov  5 15:07:42 2024] Finish sorting the reads.
[Tue Nov  5 15:15:52 2024] Finish rough annotations.
[Tue Nov  5 15:17:52 2024] Processed 100000 reads (96984 are used for assembly).
[Tue Nov  5 15:18:08 2024] Processed 200000 reads (116845 are used for assembly).
[Tue Nov  5 15:18:09 2024] Processed 300000 reads (164767 are used for assembly).
[Tue Nov  5 15:18:09 2024] Processed 400000 reads (242688 are used for assembly).
...
[Sun Nov 10 01:47:45 2024] Processed 6800000 reads (5988662 are used for assembly).
[Sun Nov 10 07:57:21 2024] Processed 6900000 reads (6088107 are used for assembly).
[Sun Nov 10 12:22:23 2024] Processed 7000000 reads (6173861 are used for assembly).
[Sun Nov 10 20:38:25 2024] Processed 7100000 reads (6273293 are used for assembly).
[Mon Nov 11 03:37:36 2024] Processed 7200000 reads (6367994 are used for assembly).
[Mon Nov 11 08:49:15 2024] Processed 7300000 reads (6456989 are used for assembly).
[Mon Nov 11 15:24:26 2024] Processed 7400000 reads (6556401 are used for assembly).
[Mon Nov 11 20:34:51 2024] Processed 7500000 reads (6639358 are used for assembly).
[Tue Nov 12 04:52:51 2024] Processed 7600000 reads (6739051 are used for assembly).

./run-trust4
-1 $DATA_PATH/BY24.clean.R1.fastq.gz
-2 $DATA_PATH/BY24.clean.R2.fastq.gz
-f $TRUST4_PATH/hg38_bcrtcr.fa
--ref $TRUST4_PATH/human_IMGT+C.fa
-t 20
--od $RESULTS_PATH/BY24_output/
this is my script,

Which version of TRUST4 is this? You can add the option "--repseq", which should improve the running time. Just want to confirm, is this UMI-based BCR-seq?

yes，this is UMI-based BCR-seq.

./run-trust4 --version
[Tue Nov 12 12:02:29 2024] TRUST4 v1.1.5-r565 begins.
Yes，this is UMI-based BCR-seq.

If it UMI based and you know the read format, like where the UMI sequence located in the read. You can use the options "--barcodeLevel molecule --barcode xxx --readFormat XXX", where TRUST4 can regard the UMI as barcode to speed up the data processing. Since your file is super large and you are using the github version v1.1.5, you can use options like "--skipReadRealign" and "--contigMinCov 3" to further speed up the process. The "--contigMinCov" will filter UMI with less the specified number of reads, so "--contigMinCov" will only generate the results for UMIs with at least 3 reads.

./run-trust4
-1 $DATA_PATH/BY24.clean.R1.fastq.gz
-2 $DATA_PATH/BY24.clean.R2.fastq.gz
-f $TRUST4_PATH/hg38_bcrtcr.fa
--ref $TRUST4_PATH/human_IMGT+C.fa
-t 80
-k 8
--skipReadRealign
--skipMateExtension
--repseq
--contigMinCov 3
--barcodeLevel molecule
--barcode 8 \   # UMI is in the first 8 bases
--readFormat PE
--od $RESULTS_PATH/output
error，bash run_trust4_job_2.sh
[Tue Nov 12 14:11:52 2024] TRUST4 v1.1.5-r565 begins.
Could not find file 8 ，I do know how to change it

运行TRUST4命令
./run-trust4
-1 $DATA_PATH/BY24.clean.R1.fastq.gz
-2 $DATA_PATH/BY24.clean.R2.fastq.gz
-f $TRUST4_PATH/hg38_bcrtcr.fa
--ref $TRUST4_PATH/human_IMGT+C.fa
--od $RESULTS_PATH
-t 36
--skipReadRealign
--skipMateExtension
--repseq
--contigMinCov 3
--clean 1
--barcode $DATA_PATH/BY24.clean.R1.fastq.gz
--readFormat "bc:0:15,r1:16:-1,r2:0:-1" ,                                                                                Hi mourisl, this is my script, but program is still very slow, just like this:                                                                                Sun Nov 17 16:11:04 2024] Found 109640387 reads.
[Sun Nov 17 16:14:12 2024] Finish sorting the reads.
[Sun Nov 17 17:34:03 2024] Finish rough annotations.
...
[Mon Nov 18 01:20:03 2024] Processed 3700000 reads (3125295 are used for assembly).
[Mon Nov 18 02:19:36 2024] Processed 3800000 reads (3215601 are used for assembly).
[Mon Nov 18 03:33:27 2024] Processed 3900000 reads (3306588 are used for assembly).
[Mon Nov 18 05:02:21 2024] Processed 4000000 reads (3400819 are used for assembly).
[Mon Nov 18 06:27:30 2024] Processed 4100000 reads (3491291 are used for assembly).
[Mon Nov 18 08:14:26 2024] Processed 4200000 reads (3582141 are used for assembly).
[Mon Nov 18 10:02:51 2024] Processed 4300000 reads (3673120 are used for assembly).
[Mon Nov 18 12:53:53 2024] Processed 4400000 reads (3766495 are used for assembly).

Yes, this is too slow. What is the running command of "trust4" main program in the running log?

I used nohup bash run_trust4_job.sh  , this is script :
./run-trust4
-1 $DATA_PATH/BY24.clean.R1.fastq.gz
-2 $DATA_PATH/BY24.clean.R2.fastq.gz
-f $TRUST4_PATH/hg38_bcrtcr.fa
--ref $TRUST4_PATH/human_IMGT+C.fa
--od $RESULTS_PATH
-t 36
--skipReadRealign
--skipMateExtension
--repseq
--contigMinCov 3
--clean 1
--barcode $DATA_PATH/BY24.clean.R1.fastq.gz
--readFormat "bc:0:15,r1:16:-1,r2:0:-1"

[Sun Nov 17 16:11:04 2024] Found 109640387 reads.
[Sun Nov 17 16:14:12 2024] Finish sorting the reads.
[Sun Nov 17 17:34:03 2024] Finish rough annotations.
[Sun Nov 17 17:34:19 2024] Processed 100000 reads (96984 are used for assembly).
[Sun Nov 17 17:34:19 2024] Processed 200000 reads (116845 are used for assembly).
[Sun Nov 17 17:34:19 2024] Processed 300000 reads (164767 are used for assembly).
[Sun Nov 17 17:34:20 2024] Processed 400000 reads (242688 are used for assembly).
[Sun Nov 17 17:34:20 2024] Processed 500000 reads (329413 are used for assembly).
[Sun Nov 17 17:34:22 2024] Processed 600000 reads (422298 are used for assembly).
nohup: ignoring input
[Sun Nov 17 11:20:13 2024] TRUST4 v1.1.5-r565 begins.
[Sun Nov 17 11:20:13 2024] SYSTEM CALL: /mnt/disk5/jianrong_disk5/vdj/chen_VDJ/software/TRUST4-master/fastq-extractor -t 1 -f /home/jianrong/jianrong_disk5/vdj/chen_VDJ/software/TRUST4-master/hg38_bcrtcr.fa -o /home/jianrong/jianrong_disk5/vdj/chen_VDJ/result/TRUST_BY24_toassemble  -1 /home/jianrong/jianrong_disk5/vdj/chen_VDJ/BY24_BulkVDJ/CleanData/BY24.clean.R1.fastq.gz -2 /home/jianrong/jianrong_disk5/vdj/chen_VDJ/BY24_BulkVDJ/CleanData/BY24.clean.R2.fastq.gz
[Sun Nov 17 11:20:13 2024] Start to extract candidate reads from read files.
[Sun Nov 17 12:38:24 2024] Finish extracting reads.
[Sun Nov 17 12:38:24 2024] SYSTEM CALL: /mnt/disk5/jianrong_disk5/vdj/chen_VDJ/software/TRUST4-master/trust4  -f /home/jianrong/jianrong_disk5/vdj/chen_VDJ/software/TRUST4-master/hg38_bcrtcr.fa -o /home/jianrong/jianrong_disk5/vdj/chen_VDJ/result/TRUST_BY24 -1 /home/jianrong/jianrong_disk5/vdj/chen_VDJ/result/TRUST_BY24_toassemble_1.fq -2 /home/jianrong/jianrong_disk5/vdj/chen_VDJ/result/TRUST_BY24_toassemble_2.fq
[Sun Nov 17 12:38:26 2024] Read in and count kmers for 100000 reads.
[Sun Nov 17 12:38:29 2024] Read in and count kmers for 200000 reads.
[Sun Nov 17 12:38:31 2024] Read in and count kmers for 300000 reads.
[Sun Nov 17 12:38:35 2024] Read in and count kmers for 400000 reads.
[Sun Nov 17 12:38:38 2024] Read in and count kmers for 500000 reads.
[Sun Nov 17 12:38:42 2024] Read in and count kmers for 600000 reads.
[Sun Nov 17 12:38:46 2024] Read in and count kmers for 700000 reads.
[Sun Nov 17 12:38:50 2024] Read in and count kmers for 800000 reads.
[Sun Nov 17 12:38:56 2024] Read in and count kmers for 900000 reads.
[Sun Nov 17 12:39:01 2024] Read in and count kmers for 1000000 reads.
[Sun Nov 17 12:39:04 2024] Read in and count kmers for 1100000 reads.
[Sun Nov 17 12:39:07 2024] Read in and count kmers for 1200000 reads.
[Sun Nov 17 12:39:10 2024] Read in and count kmers for 1300000 reads.
[Sun Nov 17 12:39:15 2024] Read in and count kmers for 1400000 reads.
[Sun Nov 17 12:39:18 2024] Read in and count kmers for 1500000 reads.
[Sun Nov 17 12:39:21 2024] Read in and count kmers for 1600000 reads.
[Sun Nov 17 12:39:24 2024] Read in and count kmers for 1700000 reads.
[Sun Nov 17 12:39:26 2024] Read in and count kmers for 1800000 reads.
[Sun Nov 17 12:39:30 2024] Read in and count kmers for 1900000 reads.
[Sun Nov 17 12:39:36 2024] Read in and count kmers for 2000000 reads.
[Sun Nov 17 12:39:39 2024] Read in and count kmers for 2100000 reads.
[Sun Nov 17 12:39:43 2024] Read in and count kmers for 2200000 reads.
[Sun Nov 17 12:39:47 2024] Read in and count kmers for 2300000 reads.
[Sun Nov 17 12:39:54 2024] Read in and count kmers for 2400000 reads.
[Sun Nov 17 12:39:58 2024] Read in and count kmers for 2500000 reads.
[Sun Nov 17 12:40:03 2024] Read in and count kmers for 2600000 reads.
[Sun Nov 17 12:40:07 2024] Read in and count kmers for 2700000 reads.
run_trust4_job.log

[Sun Nov 17 16:11:04 2024] Found 109640387 reads.
[Sun Nov 17 16:14:12 2024] Finish sorting the reads.
[Sun Nov 17 17:34:03 2024] Finish rough annotations.
[Sun Nov 17 17:34:19 2024] Processed 100000 reads (96984 are used for assembly).
[Sun Nov 17 17:34:19 2024] Processed 200000 reads (116845 are used for assembly).
[Sun Nov 17 17:34:19 2024] Processed 300000 reads (164767 are used for assembly).
[Sun Nov 17 17:34:20 2024] Processed 400000 reads (242688 are used for assembly).
[Sun Nov 17 17:34:20 2024] Processed 500000 reads (329413 are used for assembly).
[Sun Nov 17 17:34:22 2024] Processed 600000 reads (422298 are used for assembly).
[Sun Nov 17 17:34:24 2024] Processed 700000 reads (518004 are used for assembly).
[Sun Nov 17 17:34:27 2024] Processed 800000 reads (601344 are used for assembly).
[Sun Nov 17 17:34:35 2024] Processed 900000 reads (688215 are used for assembly).
[Sun Nov 17 17:34:49 2024] Processed 1000000 reads (773828 are used for assembly).
[Sun Nov 17 17:35:14 2024] Processed 1100000 reads (865280 are used for assembly).
[Sun Nov 17 17:35:46 2024] Processed 1200000 reads (953925 are used for assembly).
[Sun Nov 17 17:36:36 2024] Processed 1300000 reads (1042795 are used for assembly).
[Sun Nov 17 17:37:50 2024] Processed 1400000 reads (1129429 are used for assembly).
[Sun Nov 17 17:39:20 2024] Processed 1500000 reads (1214814 are used for assembly).
[Sun Nov 17 17:41:46 2024] Processed 1600000 reads (1300869 are used for assembly).
[Sun Nov 17 17:44:53 2024] Processed 1700000 reads (1385015 are used for assembly).
[Sun Nov 17 17:48:38 2024] Processed 1800000 reads (1469792 are used for assembly).
[Sun Nov 17 17:53:29 2024] Processed 1900000 reads (1554178 are used for assembly).
[Sun Nov 17 17:58:46 2024] Processed 2000000 reads (1637712 are used for assembly).
[Sun Nov 17 18:05:29 2024] Processed 2100000 reads (1722121 are used for assembly).
[Sun Nov 17 18:13:57 2024] Processed 2200000 reads (1806344 are used for assembly).
[Sun Nov 17 18:24:41 2024] Processed 2300000 reads (1891016 are used for assembly).
[Sun Nov 17 18:37:12 2024] Processed 2400000 reads (1975661 are used for assembly).
[Sun Nov 17 18:52:37 2024] Processed 2500000 reads (2063588 are used for assembly).
[Sun Nov 17 19:10:10 2024] Processed 2600000 reads (2149792 are used for assembly).
[Sun Nov 17 19:30:03 2024] Processed 2700000 reads (2236971 are used for assembly).
[Sun Nov 17 19:49:22 2024] Processed 2800000 reads (2324378 are used for assembly).
[Sun Nov 17 20:07:44 2024] Processed 2900000 reads (2410479 are used for assembly).
[Sun Nov 17 20:28:30 2024] Processed 3000000 reads (2497734 are used for assembly).
[Sun Nov 17 20:56:04 2024] Processed 3100000 reads (2587591 are used for assembly).
[Sun Nov 17 21:23:51 2024] Processed 3200000 reads (2676031 are used for assembly).
[Sun Nov 17 21:58:42 2024] Processed 3300000 reads (2764604 are used for assembly).
[Sun Nov 17 22:35:59 2024] Processed 3400000 reads (2853675 are used for assembly).
[Sun Nov 17 23:22:29 2024] Processed 3500000 reads (2943887 are used for assembly).
[Mon Nov 18 00:21:08 2024] Processed 3600000 reads (3035447 are used for assembly).
[Mon Nov 18 01:20:03 2024] Processed 3700000 reads (3125295 are used for assembly).
[Mon Nov 18 02:19:36 2024] Processed 3800000 reads (3215601 are used for assembly).
[Mon Nov 18 03:33:27 2024] Processed 3900000 reads (3306588 are used for assembly).
[Mon Nov 18 05:02:21 2024] Processed 4000000 reads (3400819 are used for assembly).
[Mon Nov 18 06:27:30 2024] Processed 4100000 reads (3491291 are used for assembly).
[Mon Nov 18 08:14:26 2024] Processed 4200000 reads (3582141 are used for assembly).
[Mon Nov 18 10:02:51 2024] Processed 4300000 reads (3673120 are used for assembly).
[Mon Nov 18 12:53:53 2024] Processed 4400000 reads (3766495 are used for assembly).

As you can see, there are many options did not pass to the "trust4" main program, such as --barcode and the thread number (-t). I guess there might be some typo in the bash script, or you still ran it with the old parameter setting.

If there are syntax errors in the script, it will not run properly. Because I  wrote syntax errors in my script before, the program could not run.

I try new script, check there no problem:
cat run_job_3.log
nohup: ignoring input
[Mon Nov 18 15:14:02 2024] TRUST4 v1.1.5-r565 begins.
[Mon Nov 18 15:14:02 2024] SYSTEM CALL: /home/data/TRUST4-master/fastq-extractor -t 120 -f /home/data/TRUST4-master/hg38_bcrtcr.fa -o /home/data/BY24_BulkVDJ/results_2/TRUST_BY24_toassemble  --readFormat bc:0:15,r1:16:-1,r2:0:-1 -1 /home/data/BY24_BulkVDJ/CleanData/BY24.clean.R1.fastq.gz -2 /home/data/BY24_BulkVDJ/CleanData/BY24.clean.R2.fastq.gz --barcode /home/data/BY24_BulkVDJ/CleanData/BY24.clean.R1.fastq.gz
[Mon Nov 18 15:14:02 2024] Start to extract candidate reads from read files. But , it is still slow.

I found that no matter how many threads I set up, it ultimately runs in a single thread.

I think that the program may not be using multithreading correctly. In the logs, both fastq-extractor and trust4 indeed received the -t 120 parameter, but whether they correctly parsed and applied it internally needs to be checked in their documentation or source code.

What is the command of "trust4" command in the running log now?


Uncaught TypeError: Cannot read property 'fn' of undefined for autocomplete.js

i get this error when i try to load the autocomplete.js the error is on row 126,
$.fn.yourlabsRegistry = function(key, value) {......

jquery is not loaded before autocomplete.js loads

i have found the problem, i have to load the autocomplete_light/static.html inside admin_tools, and this is a real chalange

Please make sure that you have read the install docs, particularly from here: http://django-autocomplete-light.readthedocs.org/en/master/install.html#ensure-you-understand-django-contrib-staticfiles

All the static files are ok, because if i do the modifications without admin_tools is working just fine, even if the jquery lib is loaded twice for no reason.
I thing the best option is to use class Media but when is called, to load the base.html.
When class Media is used the file position is loaded ok, after all the js files that django admin loads default,
The problem is that django-autocomplete-light is not tested with admin_tools and in docs is nothing about this.

On Wed, Dec 2, 2015 at 10:14 PM, Zaharia Constantin <
<EMAIL_ADDRESS>wrote:

All the static files are ok, because if i do the modifications without
admin_tools is working just fine, even if the jquery lib is loaded twice
for no reason.
Obviously, it's not loaded right.

I thing the best option is to use class Media but when is called, to load
the base.html.
When class Media is used the file position is loaded ok, after all the js
files that django admin loads default,

Oh, we used to do that, of course ;) If we don't anymore, it's for a
reason, that's all in the message of the git commit that does it, probably
even in the changelog :)

The problem is that django-autocomplete-light is not tested with
admin_tools and in docs is nothing about this.

Yeah, the problem is that nobody has yet contributed an example project
with regression tests. Because if someone had, we'd be able to garantee
that it works and that there is no regression for ever, and ever, and ever !
If you want to maintain admin-plus support in DAL you're welcome to join
the team for that ;)
Anything else ?
--
http://yourlabs.org http://blog.yourlabs.org
Customer is king - Le client est roi - El cliente es rey.

For the moment no, i will try to find a solution for admin_tools and how the files are loaded

Well if you need any further help, we've got some pointers here:
http://django-autocomplete-light.readthedocs.org/en/master/faq.html#how-to-ask-for-help


NIFI-12105: ExecuteStateless processor accepts additional NAR directories

Summary
NIFI-12105
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[x] Documentation formatting appears as expected in rendered files

Thanks @exceptionfactory - I'll go ahead and merge
Thanks for the addition @pgyori !

Thank you @pvillard31 and @exceptionfactory !


Other player skins missing when use itag and.

so first when i put itag in with the newest version it puts TagAPI in aswell is that meant to be happening. Next thing is when its Itag is in all other player skins on the server go to a steve skin your player skin stays but no one else can see your own skin. Im using spigot 1.8.7 #40 and the most recent version of itag and protocol. So i dont know.

yes tagapi is meant to be installed but i still have the skins not showing up

Use iTag without TagAPI.

I have the same issue but I don't have TagAPI installed?

#13 will fix this


Try microk8s enable kubeflow instead.

ubuntu :
microk8s enable kubeflow
This command can't be run as root.
Try microk8s enable kubeflow instead.

@knkski Can you give me some advice on this problem,thanks

@knkski Can you give me some advice on this problem,thanks

@qingfengmingyue could you try to add yous self to the microk8s group [1] and try microk8s enable kubeflow again?
[1] https://microk8s.io/docs

@qingfengmingyue could you try to add yous self to the microk8s group [1] and try microk8s enable kubeflow again?
[1] https://microk8s.io/docs


Update the generation of /etc/rc.conf.d/telegraf

When writing this file, empty the telegraf_flags field in order to allow the UI settings for quiet/debug logging to be effective
Fixes: opnsense/plugins#3137

Doesn't work as expected, closing.


v1.8 backports 2020-08-04-2

#12409 -- Cilium operator HA mode (@fristonio)

Once this PR is merged, you can update the PR labels via:
$ for pr in 12409; do contrib/backporting/set-labels.py $pr done 1.8; done

test-backport-1.8

test-backport-1.8

test-me-please

test-backport-1.8

test-me-please

test-backport-1.8

test-backport-1.8

test-backport-1.8


Code block without language tag broken memos

Describe the bug
I created a memo with a code block, then every time I open my memos, it shows an error Unexpected Application Error! invalid language tag: "null", I got no chance to fix it.
Steps to reproduce

Create a memo with content like this (Please replace "\```" with "```"):

# Title
\```
The code block
\```

Save the memo

Memos will show error message Unexpected Application Error! invalid language tag: "null"
The version of Memos you're using
0.19.1
Screenshots or additional context
Is there any workaround that I can fix the memo manually? thanks!

reminds me on this one which i still experience - it help when i remove the memo via the mobile app
#2898
....but then timeline and resources do work even after i deleted the memo via the app

Fixed with https://github.com/usememos/memos/commit/a76b86f18a2ca8092bd3e1c705b99b5392e500d1


Returning  causes the URL to change but not the content

Describe the bug
When returning <Navigate> from a component, it will update the URL but return the content of the original URL. However, when the <Navigate> is returned conditionally, it works fine.
E.g. I have a condition in my login route component. If logged in, return <Navigate> to an authenticated route. If not logged in, return the login form. If I was not logged in, and I use the returned form to log in, which updates the state and causes the <Navigate> to now be returned, it works. But if I was already logged in when I navigated to the login route, it partially navigates and breaks.
I've set up both scenarios in the linked codesandbox. It's not affected by changing strict mode.
Your Example Website or App
https://codesandbox.io/s/cool-ace-fz4t2s
Steps to Reproduce the Bug or Issue

Open file routes/loginRoute.ts . Observe that a Navigate will be returned every time.
Navigate to /login in the browser. Observe that the URL changes to /home but the home route's component is not shown.
Open file routes/loginRoute2.ts . Observe that the Navigate is conditional on a state change.
Navigate to /login2 in the browser. The login "form" is rendered. Click the "Log In" button. Observe that the state changes and the condition to return the Navigate is met. The URL updates to /home and the content updates to /home.

Expected behavior
As a user, I expect that returning <Navigate> from a component will always cause a successful navigation.
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Firefox
react-router versions: 205-214+

Additional context
No response

+1, also experiencing this

Same here.
I use the useNavigate() hook in my component as a workaround since it does not seem to be affected.

Yes, now after updating from beta 214 to beta 240, the problem with <Navigate />seems to be fixed, but now my useNavigate() approach does not work anymore (causing an infinite render loop when called on load).
Also some other parts of our site where I use manually triggered useNavigate(), the navigation does not work anymore - but on some other parts it still does. I need to do some more investigation here and might open another issue about this.

I just pushed an update that fixes this.

Awesome!
@tannerlinsley Thanks for your great work.


 Delete the others, including these Instructions.
{{cask_file}} represents the cask file you’re submitting/editing (if applicable).
If there’s a checkbox you can’t complete for any reason, that’s OK. Just explain in detail why you weren’t able to do so.

Changes to a cask
Editing an existing cask

[ ] Commit message includes cask’s name (and new version, if applicable).
[ ] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} left no offenses.

Adding a new cask

[x] Checked there aren’t open pull requests for the same cask.
[x] Checked there aren’t closed issues where that cask was already refused.
[x] When naming the cask, followed the reference.
[x] Commit message includes cask’s name.
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.

Can this be reopened now since the mononoki repo is using GH releases?

Yes, feel free to submit an updated PR!


Need more updates on components

Hi,

Nowadays all accordions are designing with icons like plus,arrows or some other icons and the click option is enable for whole title box, but i can see from long days its still needs to click on the title to open the accordion body.

Nav menu needs to implements with mega menu  as default component. like normal nav menu option.

And https://getbootstrap.com/docs/4.4/components/navs/#working-with-flex-utilities  section while clicking on the tab menu the content body it should open immediate below of the tab title, but it shows after the tab titles.this needs to implement

Nowdays all designs are designing with some default behaviors, so please take care of those things while adding and updating the components
Some of the above points are will helpful for developers to use bootstrap.

Accordions are customizable, you can change how they’re toggled.
Navigation doesn’t need mega menus as any kind of default. This is something you can create and others can create as needed for your projects.
The example there isn’t functional by design—there is JS for toggling tabs though, just look at the nav components page.


SERVICE_URL in envoy.py assumes 'default' namespace

SERVICE_URL constant in envoy.py, assumes that ambassador running in default namespace. dns service entry 'kubernetes' will resolved only if ambassador is running in default namespace. If ambassador is deployed in another namespace then it fails.
Solution: Instead of 'kubernetes', we should use 'kubernetes.default' as service dns

I think that that'll help only for Ambassador running in non-default, routing to services in default -- is that your intention?
Supporting multiple namespaces is indeed on the list. I think I need to understand your use case to make sure we can do the right thing, though.

Yeah, I just ran into this. We want to run ambassador in both staging and production namespaces (different ELBs and DNS), but it cannot find the kubernetes service (running 0.11.1).

It seems to be that if you replace kubernetes with the environment variables $KUBERNETES_SERVICE_HOST and $KUBERNETES_PORT_443_TCP_PORT, you get a fully portable solution, wouldn't you?

Fixed in Ambassador 0.12.0.


feat: Add support for log-hooks

Implemented using a custom struct HookEntry, to avoid exposing implementation-detail of logrus in our hooks. Might make the transition to another log-library easier.
Closes #29

Maybe instead of having hooks in separate places, we move to a contrib model and have all hooks that will be commonly used across multiple of our projects to this project?
Reference, (something like this).

That's basically what's starting to develop in our own datadog-library (grpc server/client interceptor, echo, net/http client, db/SQL, gorm, and now: go-logger hook)
But the Hook for adding trace-data needs to have trace-specific data, so it belongs in go-datadog-lib.
This PR does not implement a specific Hook, it simply opens up the possibility to add hooks.
We also probably won't have that many hooks, as the use-cases are few.
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg

From: Arun Poudel @.>
Sent: Wednesday, December 27, 2023 11:03:29 PM
To: coopnorge/go-logger @.>
Cc: Nesbø, Bendik August @.>; Author @.>
Subject: Re: [coopnorge/go-logger] feat: Add support for log-hooks (PR #74)
Maybe instead of having hooks in separate places, we move to a contrib model and have all hooks that will be commonly used across multiple of our projects to this project?
Referencehttps://github.com/DataDog/dd-trace-go/tree/main/contrib/database/sql, (something like this).
—
Reply to this email directly, view it on GitHubhttps://github.com/coopnorge/go-logger/pull/74#issuecomment-1870654659, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AALI4AYXFVDQ4HSMQCJXOA3YLSLLDAVCNFSM6AAAAABBEN4VSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGY2TINRVHE.
You are receiving this because you authored the thread.Message ID: @.***>


refine Teams URL check

(Excuse me for my poor English.)
Teams URL value's check does not work properly.
It does not work in the following cases.

create project after custom_field Teams URL is created.
set Teams URL's value "https://hoge", and set Teams URL's value "". (empty string)

If project is created after custom_field Teams URL is created, custom_value's record for the project Teams URL is created. (value is empty).
So proj.custom_value_for(cf) is not nil.
listener.rb L152
currently:
url = (proj.custom_value_for(cf).value rescue nil) ||
      url_for_project(proj.parent) ||
      Setting.plugin_redmine_msteams['msteams_url'].presence

should be:
cv = proj.custom_value_for(cf)
url = (cv.value.blank? ? nil : cv.value rescue nil) ||
      url_for_project(proj.parent) ||
      Setting.plugin_redmine_msteams['msteams_url'].presence

The tests I did are:

setting:

Administration > Plugins > Redmine Microsoft Teams => Teams channel-X
Project01                                          => not set (never set)
Project02                                          => Teams channel-B
  -> Project03(parent: Project02)                  => Teams channel-C
Project04                                          => Teams channel-D
  -> Project05(parent: Project04)                  => not set (never set)
Project06                                          => Teams channel-F
  -> Project07(parent: Project06)                  => not set (set once and set to empty string)
Project08                                          => not set (set once and set to empty string)
Project09                                          => set "-"

Only Project01 is created before custom_field Teams URL is created.
Other projects are created after custom_field Teams URL is created.

test:
Add issue each projects, and post to expected channel.

Project01 => Teams channel-X
Project02 => Teams channel-B
Project03 => Teams channel-C
Project04 => Teams channel-D
Project05 => Teams channel-D
Project06 => Teams channel-F
Project07 => Teams channel-F
Project08 => Teams channel-X
Project09 => not post

Thanks a lot, Sebastian


Remove the trailing document separator (---) from examples generated

Description of your changes
This PR removes the document separator at the end of examples generated in upjet-based providers.
Fixes: https://github.com/upbound/upjet/issues/196
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested
Manually tested in turkenf/upjet and turkenf/provider-azuread.

Hey!
would appreciate the fix landing soon in a release.


Fixed github pages deployment

GitHub Pages couldnt find bootstrap, so lets grab the source files ourselves.

Coverage remained the same at 72.835% when pulling c1a9ea0f79a87da94d70712bf436198f28a482e7 on would-you-like-to-know-more into feba6190629f57b68b5b26b9f5e4bbc0cee311a0 on master.


Built a ReplyToDiscussions demo using Azure functions

In the read me would it help to add the steps to setup api management with the GitHub graphql and set the authorization policy?

Wrote readme.md!

I created a new PR https://github.com/Azure/APIManagement-Authorizations/pull/8 because I am not using this account anymore. Closing-


HTML

HTML
User Story
I want to create a web page for boot camp students to keep track of notes taken in prework and easily access the information.
Acceptance Criteria
GIVEN a Prework Study Guide website, then WHEN I visit the site I THEN see 4 boxes (categories)  titled HTML, CSS, Git, and JavaScript with associated notes listed.

done adding HTML


Unclear how i18n (lang.Translate) determines the target language

When I use {{ i18n "key" }} in a template, there appears to be no way to change/set the target language. E. g. if $page is a translated page (from $.AllTranslations), neither
{{ with $page }}
   {{ i18n "key" }}
{{ end }}

nor
{{ i18n "key" $page }}

has any effect on the target language, while {{ $page.Content }} clearly shows that I have indeed looked up a translated page.
The documentation should state how (or rather when) the language is determined and what the optional parameter [CONTEXT] actually means and if it is at all possible to change the target language within a template.

The scenario is a Multilingual Site where I want language specific pages that are still incomplete to show the content of the default language (or any other language).
For this I'm using a custom frontmatter value in the incomplete page which triggers the fallback when set, i. e. the template looks up the already completed/translated (default) $page and calls {{ $page.Content }} instead of {{ .Content }}.

Closing as duplicate of #7844.
Well, I see you tried to create a PR to enable cross-site-language translations some time ago ...

Please open an issue in the documentation repository regarding suggested changes to the documentation.
https://github.com/gohugoio/hugoDocs/issues/2619


Extension authors should be able to put settings in a specific order

Affects https://github.com/microsoft/vscode/issues/70589

@rzhao271 I've been playing around with this in GitLens -- This is awesome!
From using this new field, it makes me REALLY which the order of the settings in the JSON were honored -- similar to how command placements are. That way I could largely avoid needing to set an order on individual settings and instead rely on the order within each category. And then the order could just be used as an override.
Also ran into a minor issue, it looks like not having an order on settings does indeed order them at the end (which is great), but order on the categories doesn't (seems like they are ranked highest). Not a big deal as it is much easier to add an order to every category, but it would be nice to be consistent.
/cc @roblourens

I'll treat that inconsistency as another bug under https://github.com/microsoft/vscode/issues/137257


Unreadable file.

Hi,
Each time I download a score in the MSCZ format the Musescore software says that the file is not readable. Each time i must download files in pdf and then convert them to MSCZ, is there any kind of fix?
I'm using the latest version of the software and of the script. Any solution?

can u try again and take a pic?

Problem sloved, it was a download problem


Add idealhack as a reviewer

I'd happily provide my review for Chinese docs.
sponsor:
/cc @zacharysarah

oops, wrong repo


Touch press/release events on BangleJs2

Currently I see no option to capture touch press and release events on the BangleJs2. The usual methods e.g. Bangle.on('touch'...) do only fire on release, so only short and long presses are evaluated.
E.on('touch', function(x, y, b) { ... }); which can do that according to the documentation is unsupported on the BangleJs.

Can't you just use the 'drag' event? When the 'b' value changes that's a difference in whether the screen is touched or not

That looks good, thanks and sorry for the noise.


Added support for .NET Standard 1.0+

This pull request adds support for .NET Standard 1.0-1.5. What this means is that the higher .net standard framework version you target you get more features as follows:

1.0: Bare minimum to run.
1.1: Added support for Concurrent Collections, Numerics (BigInteger), and System.Data.SqlClient types
1.2:
1.3: Reflection polyfills dropped, Xml Support added
1.4:
1.5: System.AppDomain support added

I've verified that the unit tests do all pass :), there may be some tests that could be enabled to run on .net standard due to it has more api surface than portable.
Notes:
Starting with .NET Standard 1.1, a reference on System.Data.SqlClient is required. However, I did add a compiler directive called NO_SQL_CLIENT that removes that functionality. This allows people source embedding to disable that functionality.

Looks good

Any ideas on if this will be merged?

I don't want to support every netstandard but post RTM I will add a higher level one, maybe 1.3.

You don't have to, but at least having these directives allow source importers to support any level also allows you use use more features per each stepping stone

We could probably find a way to do this better but shouldn't need it for most code, it's the code that depends on reflection or some new api that you'd need it and how often do you do that stuff? For example all of your new renaming code didn't need anything and you already have all these compiler directives in there for DOTNET and PORTABLE already. This was a lot of work and I think a lot of people would benefit from this patch. Especially when you get 1.0 support and nuget picks the highest net standard when referencing so you get more and more features automatically.

Well if we already have pre-processor flags all over the place, what's a few more going to hurt?

Thanks @DaveVdE for volunteering to keep an up to date fork of Newtonsoft.Json with all the pre-processor flags. Anyone who wants the source code with additional binding flags can get it from your repo.

This is a bit ridiculous :\ especially when .net standard support isn't really there (it's using portable, which .net standard 1.0 supports a lot more than portable subset). Also in the near future you can drop all other compiler directives in favor of .net standard which this pr adds support for in a minimalist way. In the end, if this is accepted or not, you'll be adding these same compiler directives to your code base, it's just a matter of time.

@JamesNK I never claimed I wanted to fork. Why this reaction? 😦

@JamesNK if you want I can simplify this and remove some of the netstandard directives if you don't want to support them all.

@JamesNK looks like my compiler directives match the microsoft recommended ones which are understood by the compiler: https://docs.microsoft.com/en-us/dotnet/articles/core/tutorials/libraries

@JamesNK would you be willing to accept a minimal PR for just adding .NET Standard 1.3 support where reflection comes in? We would try to keep the changes as small as possible.

Where reflection comes in? What do you mean by that?
I was planning to add 1.3 and add support for Reflection.Emit but some platforms don't support it and there is no way to figure that out at runtime. I'm going to need to figure that out before adding a higher level netstandard.

We are source importing and used your portable compiler directive along with the "NETStandard.Library": "1.6.0" meta package. And it works great, however when you get to 1.3, the "NETStandard.Library": "1.6.0" brings in reflection and then were unable to compile with the PORTABLE compiler directive because of the reflection polyfills.
I haven't heard anything about Reflection.Emit issues and I've tested on osx, windows and linux. Do you have a link to the issues you are seeing? Could always wrap the calls and fallback to the polyfill?

Reflection.Emit doesn't work in AOT scenarios: Xamarin, Unity, UWP, etc. With netstandard there is just one library so it needs to handle it.


Add growable write buffer

Clarification and motivation
Unfortunately, at the moment, otter memory consumption in small cache sizes is quite large compared to other caches. This is caused by the buffers that otter uses, and creates them too large without knowing in advance the characteristics of the workloads. Therefore, it is proposed to implement a growable write buffer that will be able to grow from minimum capacity to maximum capacity.

I tried to write a growable queue and here are the conclusions:

A queue with mutexes can be written so that its speed practically coincides with the speed of the channels, but I never managed to overtake them, and it is unlikely to work. After all, channels use a lower-level api.
I also tried to write a bounded version of the queue from this page. It was able to overtake the channels, but unfortunately allocates memory, and if you add sync.Pool to it, then its speed becomes equal to the speed of the channels. :(

Also, according to observations, even with a load profile of reads=25%,writes=75%, the queue speed does not particularly affect the speed of the entire cache, but with only writes it becomes a bottleneck.
And some benchmarks.
goos: darwin
goarch: arm64
pkg: github.com/maypok86/otter/internal/queue
BenchmarkChanProdConsWork100-10                  3815607               324.0 ns/op             0 B/op          0 allocs/op
BenchmarkBlockingProdConsWork100-10              3406512               354.1 ns/op             0 B/op          0 allocs/op
BenchmarkMPSCProdConsWork100-10                  5416998               220.2 ns/op            16 B/op          0 allocs/op
BenchmarkMPSCPoolProdConsWork100-10              3699946               319.6 ns/op             0 B/op          0 allocs/op
PASS
ok      github.com/maypok86/otter/internal/queue        6.260s

So I'll probably really just take a queue with mutexes as a good enough solution. Maybe later I will get bored and I will try to implement the lock-free version, but it will definitely be much later.


jdt-language-server: 1.31.0 -> 1.36.0

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)

[!NOTE]
To be able to run the wrapper, a jdk (e.g. nixpkgs.jdk) needs to be on the PATH.

24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 316861 run on x86_64-linux 1

1 package built:

jdt-language-server


Disabling wildcard imports on Intellij IDE

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.39%. Comparing base (b37c566) to head (172c5fc).
Report is 57 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1160      +/-   ##
============================================
+ Coverage     92.35%   92.39%   +0.04%
- Complexity     2821     2836      +15
============================================
  Files           292      293       +1
  Lines          5609     5614       +5
  Branches        599      598       -1
============================================
+ Hits           5180     5187       +7
+ Misses          275      273       -2
  Partials        154      154

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Cheers, I didn't know that was possible! Much appreciated!


Mouse wheel scrolling for older software and apps that doesn't support wheel scrolling

Description of the new feature / enhancement
It would be nice to add mouse wheel support for scrolling in some older software and apps that doesn't support wheel scrolling.
A utility that translate mouse wheel messages into scroll bar messages. This allows wheel scrolling in old applications that don't support mouse wheels.
PowerToys have some great mouse utilities, and I think this could be a nice complement. It could even have extra features, like scrolling any window under the mouse pointer, or reverse mouse wheel direction (like OS X).
Scenario when this would be used?
It would be useful with apps that have scrollbars but does not support scrolling with the mouse wheel.
Supporting information
There is a software called "KatMouse", by Eduard Hiti, that does a similar job. But it hasn't been updated since 2014.
https://ehiti.de/katmouse/
There's also a program called "WizMouse", by Antibody Software, that does the same thing. Last updated in 2013.
https://antibody-software.com/wizmouse

Can you give examples of apps that don’t support scrolling?  /needinfo


'Retrying setup: None' Error

Running into the persistent error when adding a new moonraker device of "Retrying setup: None". I am unable to view any of the devices or sensors after setup.
Running HACS Moonraker version 0.3.1
Here's what I found in the log:
2023-03-05 21:13:27.370 ERROR (MainThread) [custom_components.moonraker] Unexpected error fetching moonraker data: 'thumbnails'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 239, in _async_refresh
    self.data = await self._async_update_data()
  File "/config/custom_components/moonraker/__init__.py", line 102, in _async_update_data
    thumbnail = await self._async_get_thumbnail(
  File "/config/custom_components/moonraker/__init__.py", line 113, in _async_get_thumbnail
    "thumbnails": gcode["thumbnails"][len(gcode["thumbnails"]) - 1][
KeyError: 'thumbnails'
2023-03-05 21:13:27.372 WARNING (MainThread) [homeassistant.config_entries] Config entry 'mainsailos' for moonraker integration not ready yet: None; Retrying in background
2023-03-05 21:13:33.151 ERROR (MainThread) [custom_components.moonraker] Unexpected error fetching moonraker data: 'thumbnails'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 239, in _async_refresh
    self.data = await self._async_update_data()
  File "/config/custom_components/moonraker/__init__.py", line 102, in _async_update_data
    thumbnail = await self._async_get_thumbnail(
  File "/config/custom_components/moonraker/__init__.py", line 113, in _async_get_thumbnail
    "thumbnails": gcode["thumbnails"][len(gcode["thumbnails"]) - 1][
KeyError: 'thumbnails'

can you try to completely remove the device and add it back.
https://github.com/marcolivierarsenault/moonraker-home-assistant/wiki#full-reload-of-the-integration

Did it worked in a previous version

I followed the instructions.
Uninstalled; rebooted
Installed; rebooted
Added IP of printer and still seeing the same error.
Anything else I can try?
It was working in version 0.2.0

Can you send me the output if you open your browser with
<IP_ADDRESS>/server/files/metadata
(change IP for IP of your moonraker)

{"error": {"code": 400, "message": "No data for argument: filename", "traceback": "Traceback (most recent call last):\n\n  File \"/home/pi/moonraker/moonraker/app.py\", line 693, in _process_http_request\n    result = await self._do_request(args, conn)\n\n  File \"/home/pi/moonraker/moonraker/app.py\", line 672, in _do_local_request\n    user=self.current_user))\n\n  File \"/home/pi/moonraker/moonraker/components/file_manager/file_manager.py\", line 377, in _handle_metadata_request\n    requested_file: str = web_request.get_str('filename')\n\n  File \"/home/pi/moonraker/moonraker/common.py\", line 327, in get_str\n    return self._get_converted_arg(key, default, str)\n\n  File \"/home/pi/moonraker/moonraker/common.py\", line 295, in _get_converted_arg\n    raise ServerError(f\"No data for argument: {key}\")\n\nmoonraker.utils.ServerError: No data for argument: filename\n\n\nThe above exception was the direct cause of the following exception:\n\n\nTraceback (most recent call last):\n\n  File \"/home/pi/moonraker-env/lib/python3.7/site-packages/tornado/web.py\", line 1713, in _execute\n    result = await result\n\n  File \"/home/pi/moonraker/moonraker/app.py\", line 656, in get\n    await self._process_http_request()\n\n  File \"/home/pi/moonraker/moonraker/app.py\", line 696, in _process_http_request\n    e.status_code, reason=str(e)) from e\n\ntornado.web.HTTPError: HTTP 400: No data for argument: filename\n"}}

@marcolivierarsenault Thank fixed the issue for me.
Log: home-assistant_moonraker_2023-03-06T03-34-12.034Z.log

Great Solved in 0.3.2


Compilation still slow with via-ir

Was chatting with Georgios about this and ran some benchmarks / tests on https://github.com/uniswap/universal-router. Posting here to hopefully help debug this
Repo:

solc 0.8.17
via-ir = true
optimizer runs = 1,000,000
forge-std version: 1.1.0 33d4895fb629aabf12e0f60740367bd03e702bd1

Cold build with hardhat: 16s
Cold build with forge: 45s
Removing only test/: 23s
Removing only script/: 30s
Removing test/ and script/: 7s
Removing forge-std and test/ and script: 6.5s
With the hunch that console.log or console2.log was causing this, i removed those from forge-std and all callsites: 40s
So, something in forge-std is causing the slow compilation and it's not console. I can maybe go one-by-one and test further later but wanted to post here in case other folks have time to TAL. 45s obviously not terrible but 3x worse than hardhat and bit of a drag on development

Just want to confirm my understanding and make sure we're on the same page:

When building with hardhat, the 16s build time is just the contracts/ dir, so the equivalent comparison of foundry vs. hardhat build times is the 7s build time when removing test/ and script/
Then, compiling scripts takes 16s (23 total minus 7s base)
And compiling tests takes 23s (30s total minus 7s base).
This makes sense, since you cited 45s as the full build time, and 7 + 16 + 23 = 46s is very close

There was speculation in #207 that the slow via-ir build times might be related to something in foundry/svm-rs, as opposed to generic solc slowness, which is why I want to confirm that hardhat's 16s time is not including the foundry scripts/tests.
@marktoda Do you mind trying a few other benchmarks and sharing the results? (I tested these changes in forge-std directly using the CompilationTest contract and include the results I saw below)

Try compiling with optimizerSteps = '' and see if that impacts build times, see here for how to set this correctly. This disables all via-ir optimizer steps and should reduce build time significantly. If this speeds up build times, you can have separate test and release foundry profiles (i.e. with and without optimizer steps)

When I make this change in forge-std and compile with via-ir, compilation goes from 60s to 5s (@leonardoalt pretty sure I configured this improperly last time and told you it did not affect compilation time, sorry)
(Side bar: @mattsse maybe this should be renamed to optimizer_steps instead of optimizerSteps for consistency with other config names? Same for other related solc flags)

Comment out the _constructor method in StdCheats.sol, which was the problem section originally last time. If this reduces build time, perhaps we change to the solution from #209 which lazily ran that method on the first usage and just take the small UX hit

When I make this change in forge-std, compilation goes from 60s to 4s

Try the combination of the first two

When I make this change in forge-std, compilation goes from 60s to 3s

If you see similar results, there's two options to consider.

Make no changes, and just better document that the via-ir optimizers are enabled by default and suggest different test/release profiles
Implement #209 or something similar for lazy initialization at the small UX expense so users don't need to setup the two profiles

I'd be curious to hear your thoughts on each.
I think the solc team is working on improving via-ir build times too, so hopefully this becomes less of an issue in future versions, but it makes sense the optimizer will always be slower than no optimizer

there's two options to consider

I say the latter option, if that ends up being the case. Don’t want to require additional setup from users - want the library to be as easy to use as possible.
Good analysis, @marktoda, @mds1.

@marktoda WDYT re Matt's response above?

Thanks for the analysis here! running these now:

optimizerSteps = '': 8s
commenting out _constructor: 18s

I think having a test profile with no optimizer steps is a good option, hadn't considered that before. A bit of a hassle / chance of forgetting to set to release mode and accidentally releasing unoptimized code though
IMO the lazy initialization is worth it for a 2x speedup, though I'm not sure I fully understand the UX issue

Oh, other problem with the test/release profiles is that we heavily weigh gas snapshots in PR reviews. These snapshots would now be much less reflective of real gas if not using optimizer when generating them

IMO the lazy initialization is worth it for a 2x speedup, though I'm not sure I fully understand the UX issue

Not a big one, it's just instead of calling x you call x().

Ok great. So let’s move to lazy initialization and document the optimizer suggestion in the book as well. I'm traveling this week, @ZeroEkkusu do you think you can take the lead on making these changes?

chance of forgetting to set to release mode and accidentally releasing unoptimized code though

Agreed, the way I like to handle this is keep the default profile to have the release settings, and use that in CI, then a lite profile for local dev and testing. I think this makes it less likely to forget to set release mode, since you would need to explicitly enable the wrong profile during deployment.
Regarding snapshots, @gakonst maybe we bump the priority of https://github.com/foundry-rs/foundry/issues/2056 and discuss options/UX there, and make them easier to integrate into CI?

Haven't thought about snapshots at all, let's move conversation there. @ZeroEkkusu if you can take point in the forge-std optimizations that would be great. And we can follow-up with the release mode discussion in a separate issue, if @mds1 can take point there with a braindump.

@gakonst re lite vs. release mode, just created https://github.com/foundry-rs/book/issues/709

Im on forge-std 1.5 and compile times on a rather simple code base are still over 35 seconds.
optimizer = true
via_ir = true
optimizer_runs = 1000000
optimizerSteps = ''
[⠔] Compiling 63 files with 0.8.17
[⠘] Solc 0.8.17 finished in 29.33s

@zeroknots Can you open a new issue with steps to reproduce? And can you benchmark the time to only compile the source files, compared to both source + test, to make sure the slowness is caused by forge-std?

@zeroknots Can you open a new issue with steps to reproduce?

Done :) Hope this is helpful to triage.
https://github.com/foundry-rs/forge-std/issues/321


Adding react-native-vector-icons

rnvi works without being in a monorepo, but when it is in one it throws this:
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|
|       return (
>         <Text selectable={false} {...props}>
|           {glyph}
|           {children}

How did I test it? I tried importing a screen from the /packages/app with an icon in it and the error was shown. When I put the screen directly into the /packages/next/pages/index.tsx file it works perfectly
Here is my next.config.js file
/** @type {import('next').NextConfig} */
const path = require("path");

const withPlugins = require('next-compose-plugins')
// Necessary to handle statically imported images
const withImages = require('next-images');
// Necessary to handle statically imported fonts
const withFonts = require('next-fonts');

const withTM = require('next-transpile-modules')([
	// 'react-native-paper',
	'react-native-vector-icons',
  'react-native-svg'
],{resolveSymlinks:true});

module.exports = withPlugins(
  [
    withTM, withFonts, withImages,
  ],
  {
      devIndicators: {
        autoPrerender: false
      },
      enableSvg: true,
      // Allows us to access other directories in the monorepo
      experimental: {
        externalDir: true,
        // concurrentFeatures: true,
      },
      // This feature conflicts with next-images
      images: {
        disableStaticImages: true,
      },
      webpack: (config, options) => {
        config.resolve.alias = {
          ...(config.resolve.alias || {}),
          // Transform all direct `react-native` imports to `react-native-web`
          'react-native$': 'react-native-web',
          'recyclerlistview$': 'recyclerlistview/web',
        }
        config.resolve.extensions = [
          '.web.js',
          '.web.ts',
          '.web.tsx',
          ...config.resolve.extensions,
        ]

        if (options.isServer) {
          config.externals = ['react', 'react-native-web', ...config.externals];
        }
        config.resolve.alias['react'] = path.resolve(__dirname, '.', 'node_modules', 'react');
        config.resolve.alias['react-native-web'] = path.resolve(__dirname, '.', 'node_modules', 'react-native-web');

        config.module.rules.push(
          {
            test: /\.(jpe?g|png|gif|svg)$/i,
            use: [ 'url-loader?limit=10000', 'img-loader' ]
          },
          {
            test: /\.ttf(\?v=\d+\.\d+\.\d+)?$/,
            exclude: /node_modules/,
            use: [
              {
                loader: 'url-loader',
              }
            ],
            include: path.resolve(__dirname, '../app/node_modules/react-native-vector-icons')
            }
        )

        return config;
      }

  }
)

Hey @toto1384 , Have you figured it out?

It's a low priority for my client right now so kind of gave up on it for the time being
You might want to have a look at https://capacitorjs.com/. I AM NOT SAYING IT IS BETTER, OR GOOD AT ALL, just that I've heard about it on the interwebs :))


Gained tab on website not sorting users alphabetically

Our clan gives points to users depending how much exp they got each week.
Whilst checking it, I've noticed you can sort the list by column headers (rank,start,end,gained) except name.
I was wondering if this was intended that you can't sort names alphabetically or if it's a bug.

It would make tracking users gained exp and giving points for them a lot quicker if we could sort names alphabetically, if this were to be resolved.
Thank you for your consideration

this was fixed, and also this is the discord bot's repository, so the issue doesn't apply here.


Users without organizer privileges can get to place creation page

Use an account that lacks orgnanizer privileges.

On the results page, you'll see this on the upper right-hand side:

That link takes you to the place creation page, but if you try to save your new place you'll hit and error that says you don't have orgnanizer privileges.

Since users without organizer privileges can't actually make a new place, we should remove that link for non-organizer users.
TODO

[ ] Remove "Not finding what you want? Add a New Place" text and link from /places/search if they do not have the organizer privilege
[ ] PlacesController#new should redirect the user back if they don't have the organizer privilege (I think we just need to add :new to requires_privilege :organizer, only: [:new, :create, :edit, :update, :destroy])

Hello @kueda , Please assign me this issue . Thanks.

@pleary @kueda As we have discussed in the slack, I think 2nd todo task is not needed, as it is already redirecting it to current page if user manually types URL and go to place creation page. There is no way user is goes to place creation page.  Just the thing is we need to correctly display the error message if user manually tries to open place creation link. Just a suggestion,  I think we should create a different issue for this task.


Cant compile

I am getting this error.
i am using "scons -j 6" to compile
modules\qrcodetexture\qr_code_texture.cpp(2): fatal error C1083: Cannot open include file: 'qrcodegen.hpp': No such file or directory scons: *** [modules\qrcodetexture\qr_code_texture.windows.tools.64.obj] Error 2 scons: building terminated because of errors. [Time elapsed: 00:01:02.785]

Fixed it. I had to add these two files:
https://raw.githubusercontent.com/nayuki/QR-Code-generator/master/cpp/qrcodegen.cpp
https://raw.githubusercontent.com/nayuki/QR-Code-generator/master/cpp/qrcodegen.hpp

This was because the qr_code_generator library was a git submodule. For it to work you would need to run:
git submodule init && git submodule update.
I've made an update so this is no longer needed - it should just work with a trivial download or git clone from now on.


Bump mlir aie

combines #379 and #375

I will look at this when manage to build mlir-aie (build issues)  and @erwei-xilinx will take a look in parallel. One set of failures is because I did not update the lit tests for the LLVM changes to ReduceOp.

I will look at this when manage to build mlir-aie (build issues) and @erwei-xilinx will take a look in parallel. One set of failures is because I did not update the lit tests for the LLVM changes to ReduceOp.

Thanks. I think I've done most of the low hanging fixes. I haven't looked at the AIRDependency failures. I also see some weirdness around aiex.ipu.dma_memcpy_nd, maybe related to https://github.com/Xilinx/mlir-aie/pull/901, not sure. Locally I also get failures related to missing hsa, so maybe #380 wasn't enough.

replaced by #383


Playing a clip does not start if one already playing

Reopening in AudioKit/AudioKit since this is an issue with AudioPlayer and not Cookbook
Original ticket: AudioKit/Cookbook#97

Hi @roboldham,
Can you test your example with AudioKit main branch and let me know if the new changes work. Thanks.

It does indeed! Yay... across all apps using AudioPlayer , .status() also reporting correctly in all cases
Thanks very much!


Merge UAT to Master 22 Mei 2018

Coverage increased (+0.6%) to 78.419% when pulling 4432d734974deadcbc511a32e88d4ba7a48af13e on uat into deb8cac3cbe3890576520ef2d147b53dbf8c03a0 on master.


LF or CRLF or don't care?

When running npm run build in Windows, the scripts convert all line breaks to LF where the bulk of files has the Linux style CRLF.
I'm severely lacking NPM skills to figure how to fix this, or if @bhousel you'd like this to be fixed anyway?
K

Thanks for raising this  - I added a .gitattributes file that should set all the text files to LF when git touches them.
This answer contains some more info:  https://stackoverflow.com/a/42135910/7620
If your local copy of the repository has a mix of line endings, I think these steps should fix things to LF and it should stay that way going forward:
git pull origin       # Get the .gitattributes file
git rm --cached -r .  # Remove every file from git's index.
git reset --hard      # Rewrite git's index to pick up all the new line endings.

Works like a charm, thanks :-)


Unnecessary spacing in CLI output

After spending 30 minutes trying to figure out why csharpier was formatting a different number of files in our CI pipeline than locally, I finally noticed that my browser window was the exact width that resulted in chopping the Total time and Total files output numbers in half:

It may be worth considering removing the spacing to prevent this kind of misreading of the output.

I've been considering simplifying the output for check and getting rid of the stats, I'm not sure that they add value. Prettier only provides a simple "everything is good" or "here are the files that aren't formatted" output. Maybe adding an option to show more details about the number of files, etc. If I do keep around the details I'll clean up the spacing to avoid this problem.

Related #875

I'm going to rework the logging and add a logging level with #875. As part of that the format is going to change which will remove this problem.


Feat: Implement claim_fees and claim_ui_fees in the FeeUtils library.

Description
Implement the claim_fees function in the FeeUtils library.
File: src/fee/fee_utils.cairo.
Function signature:
    /// Claim fees for the specified market.
    /// # Arguments
    /// * `data_store` - The `DataStore` contract dispatcher.
    /// * `event_emitter` - The `EventEmitter` contract dispatcher.
    /// * `market` - The market to increment claimable fees for.
    /// * `token` - The fee token.
    /// * `receiver` - The receiver of the claimed fees.
    fn claim_fees(
        data_store: IDataStoreSafeDispatcher,
        event_emitter: IEventEmitterSafeDispatcher,
        market: ContractAddress,
        token: ContractAddress,
        receiver: ContractAddress,
    )

Implement the claim_ui_fees function in the FeeUtils library.
File: src/fee/fee_utils.cairo.
Function signature:
    /// Claim ui fees for the specified market.
    /// # Arguments
    /// * `data_store` - The `DataStore` contract dispatcher.
    /// * `event_emitter` - The `EventEmitter` contract dispatcher.
    /// * `ui_fee_receiver` - The ui fees receiver.
    /// * `market` - The market to increment claimable fees for.
    /// * `token` - The fee token.
    /// * `receiver` - The receiver of the claimed fees.
    fn claim_ui_fees(
        data_store: IDataStoreSafeDispatcher,
        event_emitter: IEventEmitterSafeDispatcher,
        ui_fee_receiver: ContractAddress,
        market: ContractAddress,
        token: ContractAddress,
        receiver: ContractAddress,
    ) -> u128

Acceptance criteria

Function is implemented and well commented.
Associated unit tests (nominal and failure) are implemented and passing.

Resources

claimFees function in GMX repo
claimUiFees function in GMX repo

Hi, @sparqet, can i work on this?

Hi, @sparqet, can i work on this?

Hi sorry I've already done it 😅

Alright. Any open issue you can assign me to work on?


considering making "include" part of recipe DSL

A lot of people get trolled by the fact that Chef recipes look like regular Ruby, so they think they can just do things like:
include Opscode::OpenSSL::Password

to mixin modules. But of course that doesn't work, 'cause include isn't part of the DSL. Thus users have to dive into ugly Ruby metaprogramming, with syntax like:
::Chef::Recipe.send(:include, Opscode::OpenSSL::Password)

to effectively monkeypatch the Recipe class to mixin the module.
It gets even gnarlier if they want ruby_block to mixin modules; now they need to know the provider class:
Chef::Provider::RubyBlock.send(:include, Some::Thingy)

Is there a way we could make the user experience better? Say, by making include part of the DSL? Other ideas?

not_if blocks are evaluated in the context of the Chef::Resource::Whatever object so its reasonable that people would want that as well.  There should probably be an easy way to mixin to Chef::Recipe, Chef::Resource and Chef::Provider all in one go, although that's a rather large footgun.
Something like:
use Opscode::OpenSSL::Password, in_resource: :ruby_block
Could be used to wire up to the resource and provider that :ruby_block evaluates to, but with service providers that'd be problematic to determine.  Could also take a class name and something like :all_resources to engage the full footgun mode....

i love it :-). may be use
use Foo::Bar

for inclusion in all resources & recipes. and
use Foo::Bar, in: :ruby_block, :execute

if user want to mixin their module only in one resource, they can do it directly, without use DSL
ruby_block 'mixin_demo' do
  exten Foo::Bar
  block do
  end
end

we can a generic middle ware API for these mixins using the top level Chef.* DSL methods.

I'd probably want use Foo::Bar to only hit the recipe DSL.  For the footgun I think you should have to type a bit more.  Its pretty dangerous because if you collide with any internal method names or collide with any properites of any Resources or LWRPs then you may get very odd behavior, and you may see that odd behavior very distant from where you launched the footgun at.

per discussion in #4674 we probably want to be more targeted with this.  so by default use Foo::Bar should ideally only infect the instance of the object of the current DSL context.
so:
use Opscode::OpenSSL::Password
node['whatever'] = random_password

would not inject random_password into other recipes.  global inclusion across the board should be handled in library files and not by the end user writing recipe code (i.e. the openssl cookbook should inject its methods into the global DSL if it wants to do that and not pass the buck to the end user).
similarly for ruby_block would probably want it to get written like:
ruby_block "whatever" do
  block do
    use Opscode::OpenSSL::Password
    puts random_password # wut security?
  end
end

ruby_block "boom" do
  block do
    random_password   # will raise
  end
end

means typing more and being more explicit, but avoids polluting resources in other cookbooks that are totally orthogonal.  and again it should be up to the cookbook that is offering the module, or something core like chef-sugar or chef-client itself to mix those methods in globally.

After https://github.com/chef/chef/pull/8243 the following all works:
Chef::DSL::Universal.send(:include, MyMethods)
Chef::DSL::Core.send(:include, MyMethods)
Chef::DSL::Recipe.send(:include, MyMethods)

One of those is probably the correct thing for injecting methods into DSLs.  The DSL file have large comment banners explaining their usage.
Chef::Resource::RubyBlock.send(:include, MyMethods)

Remains the correct way to inject methods only into one resource.
Due to lack of interest in creating DSL helper methods, I'm closing this.


Protection from large Coverage API requests

For large datasets, such as satellite products covering long periods of time, it is easy to submit a synchronous coverage request that cannot be fulfilled within typical timeout limits. Even if a large request CAN be fulfilled, the user may be impacted by getting much more data volume than expected. There is likely no one solution to solve this for the diversity of users and servers. An assemblage of solutions might include the following capabilities:

page through the coverage response by spatial or temporal chunk or tile

obtain estimated size of a response before actually requesting the data (like a HEAD request)

allow servers to advertise maximum request limit

have a specific error response that indicates the request is too big to satisfy

support asynchronous response

allow servers to advertise maximum request limit

How would servers be able to evaluate whether a request was too big?

For coverages that are regular grids, the response volume can often be computed from the bounding box size and the time period requested. For servers in the cloud, a response may also be too big for cost reasons, so the next step would be to estimate egress and processing charges. For multi-point coverages, this may be more difficult.

@chris-little So far this discussion has not touched on async.  However, I have captured the async issue under API-Common issue 231.

SWG 2021-05-26: Agreed that service-metadata is the best place to describe API-wide limits in terms of a maximum number of cells and/or uncompressed megabytes of data that the server will accept to return. Furthermore we need a permission that the server can reject a client request (some standardized 400 code?) if the client is asking for too much data.

413 Payload Too Large ~ https://datatracker.ietf.org/doc/html/rfc7231#section-6.5.11

@nmtoken As we discussed in the call, I believe 413 as defined might applies to the payload provided by the client, as opposed to the payload being returned to the response, though that should be clarified.

@jerstlouis Sorry, wasn't on the call and missed the discussion.
Now you say it, I agree, it could mean that too or either may apply.  My next pick would be 400 Bad Request ~ https://datatracker.ietf.org/doc/html/rfc7231#section-6.5.1

he 400 (Bad Request) status code indicates that the server cannot or
will not process the request due to something that is perceived to be
a client error (e.g., malformed request syntax, invalid request
message framing, or deceptive request routing).

As a related aside to this, I would like to suggest that we consider that for servers that support the scaling conformance classes, that a default /coverage request could provide downsampled data if scaleFactor=1 is not explicitly provided. This makes it easy for client to get an overview of the whole coverage regardless of its dimensions or resolution, and prevents the default request from returning an error.
e.g.
https://maps.ecere.com/ogcapi/collections/SRTM_ViewFinderPanorama/coverage?scaleFactor=1 returns an error, but
https://maps.ecere.com/ogcapi/collections/SRTM_ViewFinderPanorama/coverage does not.

not a good idea to change the behavior of Core in a way that is not intuitive and not consistent. And makes it more complicated to understand. Why not focus energy on a good set of examples, which would be extremely beneficial...

@pebau while I agree on the examples, that is a separate topic.
The reason I make this suggestion here is that the link to /coverage is is provided from the collection resource, and for many coverages it is a broken link that is asking for too much data if not modified with additional parameters specified.
Principle #23 of the OGC API Web Guidelines mentions:

Good practice for defining default behavior is avoiding exception, error or empty pages as the response.

So I really like the idea of being able to return the downsampled coverage by default if the full resolution is too much for the server to process or the client expecting to receive, while saying scaleFactor=1 would mean the client knows what it is doing and insists on retrieving the full resolution data.
I also believe it is part of the solution to the problem raised in this issue by @clynnes .
Also to address the original suggestions, all of these are good capabilities as well:

page through the coverage response by spatial or temporal chunk or tile

The specification now has conformance classes for subset and coverage tiles.

obtain estimated size of a response before actually requesting the data (like a HEAD request)

We should probably add this as a new requirement?

allow servers to advertise maximum request limit

We were just discussing adding this to service metadata at the API level.

have a specific error response that indicates the request is too big to satisfy

We were just discussing 400 is likely the proper error response for this.

support asynchronous response

Discussed in #66 -- multiple OGC API specifications are going to use of Prefer header to indicate that an async response is desired, and this could be defined in Common.

@jerstlouis you commonly "like the idea" - let me note, for the records, that others do not necessarily like it (in this case: at least me). In my world, more technically based arguments tend to be used.
In the case on hand, concerns get mixed: consistent service logic and resource-dependent limitations such as quota.

@pebau I included the reason why I like the idea: to avoid a default behavior returning an error or returning more data than the client (or webcrawler) intended to request. I understand your opinion and concerns about the service consistency, I think it's a question of balancing perceived consistent service logic vs. the implications of having a default behavior which is normally not what is intended by users/clients.

@jerstlouis I do not share the idea that users would intend what is sketched (let aside that a complete specification is still missing), also with webcrawlers. If this is a use case, how is that solved by other tools and services, in the geo and other domains?  Any investigation available?

Admittedly we haven't actually had any real clients yet for our OGC API - Coverages implementation, but I can tell you that of all the people within our company that I got to test drive what's been implemented so far, they've all complained that our /coverage endpoint is broken because they get a "400 Bad Request" response.  So in this respect it seems to me that having endpoints that actually work without having to append parameters to them would be a good thing.
If a client wants to explicitly request the full-scale coverage, it always can do so by adding scaleFactor=1.  It doesn't even have to check to see if the server actually supports the scaling conformance class, since servers that don't support this conformance class would presumably just ignore this parameter (or throw an error if its value is something other than 1).
I don't feel strongly about this one way or another, and am happy to let the industry decide, but I just figured I'd share my own personal experience and opinion in this matter.

SWG 2021-11-25: We agreed to include permissions and requirements along these lines:
Permission: A server advertising conformance for the scaling conformance class MAY return a downsampled version of the coverage, if the client does not explicitly request scale-factor=1
Requirement: Even if the scaling conformance class is not supported, the server SHALL understand requests specifying scale-factor=1 as indicating that the client wishes to retrieve the data at full resolution.

just for the records, I am strongly against this.

2022-01-12: Suggestion from @tomkralidis to have a boolean property in the metadata indicating that the default /coverage request will return downsampled data.

@tomkralidis
Question regarding your suggestion

to have a boolean property in the metadata indicating that the default /coverage request will return downsampled data

There is a permission now in place.

In the case where a response to a request without a scale-factor, scale-axes or scale-size parameters would be larger than an advertised server limit, an implementation MAY automatically downsample the coverage to a suitable resolution instead of returning a 4xx client error.

and a Note:

A client retrieving a coverage from an implementation advertising support for this "Scaling" requirements class should explicitly use scale-factor=1 if it wants to ensure retrieving the coverage in its native resolution and prefers receiving an error instead of a downsampled version of the data.

I am wondering now how to implement this suggestion, and having seconds thoughts about whether it is really necessary / useful. The only place we could include this metadata (e.g., "defaultCoverageMayBeDownsampled" : true) would be in /collections/{collectionId}.
My feeling, as per the note, is that any client requesting /coverage needs to explicitly use ?scale-factor=1 as query parameter if it absolutely does not want downsampled data. Then these clients should not care what this property says, and should just assume this to be the case for all implementations.
Adding more things to the collection description complicates things.
Adding this could also have an opposite effect to the intent of preventing downsampled data used inadvertently.
It could create a situation where clients think they can rely on looking at defaultCoverageMayBeDownsampled and if it is not there or false, they do not need to use ?scale-factor=1 to ensure downsampled data, but a server implementation could then fail this requirement. It actually makes things more complicated to implement for both client and server to look for this property and branch one way or the other, and introduces more potential points of failure.
In OGC API - Maps we already have this expectation that /map is not necessarily the most detailed resolution.
In Features there is a paging mechanism, so an expectation that /items will not necessarily return all items.
Thoughts about whether it is necessary or not to include something like "defaultCoverageMayBeDownsampled" : true, or we may be better off without it?

@jerstlouis so to summarize:

the server provides the data in whatever resolution it decides, by default/implicitly, and that clients can explicitly specify scale-factor=1 if they so choose
no additional collection level metadata is then required

That works for me, we should have some informative text on this behaviour (probably a similar in OAMaps while we're at it).


feat: add option for get gate with default value

* similar to GO sdk issue
Background
In continue of OpenFeature PR, it is a common practice to evaluate a boolean/gate with a default value:
client.getBooleanValue("non-existing", true)

Problem
BooleanEvaluation with default value true cannot fallback to true.
On scenarios such as get gate of non-existing gate, statsig returns false without indication of whether it was successful get gate or some error reason. Therefore, the evaluation will be evaluated to false in this case.
Suggested solution
add:
Statsig.checkGateAsync(user, key, boolean fallback);

@xinlili-statsig

We've added a new API(which will return the evaluation details regarding a gate) for this.  Please take a look. https://github.com/statsig-io/java-server-sdk/releases/tag/v1.14.0

We've added a new API(which will return the evaluation details regarding a gate) for this. Please take a look. https://github.com/statsig-io/java-server-sdk/releases/tag/v1.14.0

Thanks. The request of fallback was not added exactly as requested, so managed to overcome it via specific reasons check.


"Almașu" , "Băbiu" , "Cutiș" , "Jebucu" , "Mesteacănu" , "Petrinzel" , "Sfăraș" , "Stana" , "Țăudu" are listed in the drop-down menu

Description:
When user writes "Almașu" , "Băbiu" , "Cutiș" , "Jebucu" , "Mesteacănu" , "Petrinzel" , "Sfăraș" , "Stana" , "Țăudu" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Almașu"

Expected results
The location appears in the drop-down menu as "Sat Almașu, SĂLAJ (Almașu)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Băbiu"

Expected results
The location appears in the drop-down menu as "Sat Băbiu, SĂLAJ (Almașu)".

Step 3
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 6
Write in the search bar "Jebucu"

Expected results
The location appears in the drop-down menu as "Sat Jebucu, SĂLAJ (Almașu)".

Step 7
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 8
Write in the search bar "Mesteacănu"

Expected results
The location appears in the drop-down menu as "Sat Mesteacănu, SĂLAJ (Almașu)".

Step 9
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 10
Write in the search bar "Petrinzel"

Expected results
The location appears in the drop-down menu as "Sat Petrinzel, SĂLAJ (Almașu)".

Step 11
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 12
Write in the search bar "Sfăraș"

Expected results
The location appears in the drop-down menu as "Sat Sfăraș, SĂLAJ (Almașu)".

Step 13
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 14
Write in the search bar "Stana"

Expected results
The location appears in the drop-down menu as "Sat Stana, SĂLAJ (Almașu)".

Step 15
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 16
Write in the search bar "Țăudu"

Expected results
The location appears in the drop-down menu as "Sat Țăudu, SĂLAJ (Almașu)".


[R] Source package install not using precompiled libarrow binaries

Describe the bug, including details regarding any error messages, version, and platform.
While testing the latest (18.1.0) arrow CRAN submission, I noticed the prebuilt libarrow binaries aren't being used. I'm not sure if this has been an issue for more than just this release yet.
How I can reproduce this:
git checkout maint-18.1.0-r
cd r
make build
ARROW_R_DEV=TRUE R CMD INSTALL arrow_18.1.0.tar.gz
* installing to library ‘/home/bryce/R/aarch64-unknown-linux-gnu-library/4.4’
* installing *source* package ‘arrow’ ...
** using staged installation
*** pkg-config found.
trying URL 'https://apache.jfrog.io/artifactory/arrow/r/'
downloaded 1284 bytes

*** Building on linux aarch64
*** Found local C++ source: 'tools/cpp'
*** Building libarrow from source
    For build options and troubleshooting, see the install guide:
    https://arrow.apache.org/docs/r/articles/install.html
*** Building with MAKEFLAGS=-j2

I think it would be good while fixing the issue to improve the print logging if we can.
cc @assignUser
Component(s)
R

on linux aarch64

We don't have Linux arm64 pre-built binaries, so non could be downloaded. Also if you are on Debian it would also built from source.

I think you've told me either one or both of those things in the past, sorry about that. In the R release guide, we have an instruction,

[ ] Check install.packages("arrow_X.X.X.tar.gz") on Ubuntu and ensure that the hosted binaries are used

Is that just a very out of date instruction?

That assumes amd64, we should add that. Ubuntu is allow listed for binaries, Debian is not (because cran runs Debian).


RenderComplete event does not fire

Describe the bug
The rendercomplete event does not fire for the map object in a Vue serverless application.
To Reproduce

Add layers, move, zoom, update params of sources.
Console log the event firing

Expected behavior
I expect the map to fire a rendercomplete event once I update the time parameter on the ImageWMS sources and they all render.

It will be impossible to track down this problem without seeing your code. If you can go to the official examples (https://openlayers.org/en/latest/examples), choose one that is suitable to be extended to show your issue, and click the "Edit" button, you can create an application that exposes the problem.


Add Asynchronous Initialization and Properly Connect to Wallet RPC When Using MoneroNetwork Enum

Add Asynchronous API to DaemonClient and WalletClient Creation. WalletClient's asynchronous initialization does work, opening the wallet so we don't need two separate calls (one to contructor, one to OpenWalletAsync). See use in ReadMe.MD
Properly connect to default MoneroWallet hostname and port. Previously when the wallet client was initialized with MoneroNetwork (e.g. MoneroNetwork.Mainnet), it used the Daemon's default address.

@rbrunner7

The matching comparison was just way more succinct than the alternative. Couldn't resist. Thanks for reviewing.