Native crash during acceptance tests.

During acceptance tests i got a native crash that failed the build.
I don't know if this is flakey or not. I might be a bug.
The failing build can be found here:
https://app.circleci.com/pipelines/github/hyperledger/besu/5672/workflows/1120c35a-7563-4e49-aed1-1b799a7b8f18/jobs/27286
Detailed error log can be found here:
https://circle-production-customer-artifacts.s3.amazonaws.com/picard/forks/5d70c4385140754677d585cb/208739519/5f8010b2338e470df053691a-1-build/artifacts/acceptance-tests/tests/build/jvmErrorLogs/java_err_pid716.log?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20201009T083540Z&X-Amz-SignedHeaders=host&X-Amz-Expires=60&X-Amz-Credential=AKIAJR3Q6CR467H7Z55A%2F20201009%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=de42181ac8405c0720c34e074bc7fba0a8dd7f47929ed0d9d643659067754fd5
> Task :acceptance-tests:tests:acceptanceTest
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0x00007fb34961ca6f, pid=716, tid=871
#
# JRE version: OpenJDK Runtime Environment 18.9 (11.0.8+10) (build 11.0.8+10)
# Java VM: OpenJDK 64-Bit Server VM 18.9 (11.0.8+10, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  [ld-linux-x86-64.so.2+0x1ea6f]
#
# Core dump will be written. Default location: /home/circleci/project/acceptance-tests/tests/core.716.%E
#
# An error report file with more information is saved as:
# /home/circleci/project/acceptance-tests/tests/build/jvmErrorLogs/java_err_pid716.log
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

Got the failure again @timbeiko
https://app.circleci.com/pipelines/github/hyperledger/besu/5776/workflows/b84ecbae-378e-4bb2-bb04-dfbcb6ecf024/jobs/27832
https://circle-production-customer-artifacts.s3.amazonaws.com/picard/forks/5d70c4385140754677d585cb/208739519/5f8da91f98b7110f5f82d9ee-1-build/artifacts/acceptance-tests/tests/build/jvmErrorLogs/java_err_pid744.log?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20201019T151046Z&X-Amz-SignedHeaders=host&X-Amz-Expires=60&X-Amz-Credential=AKIAJR3Q6CR467H7Z55A%2F20201019%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=218a41227d3a5f8c3db5df9901ba8198157a2b60ab6589f1470a0ffe6d07cb98

again - https://app.circleci.com/pipelines/github/hyperledger/besu/6005/workflows/599863c8-0bf7-4217-a7f5-c3ff7e9181ca/jobs/29001

Hey @abdelhamidbakhta @shemnon, has this crash stopped happening for now? if so I'll close this until we see it again


 This stackoverflow question gives a good use case: polling.
We can also use this to do scope specific digests, which really helps performance and snappiness on mobile devices.
It also gives us a little more control over the API, and also makes it similar to $timeout.

Small FYI, if you just push again to your branch the pull request will updated. No need to create a new one.

It's similar to how the $timeout and $interval services, but no other reason. I could change it to use the config object if that's preferable.

This change isn't enough to prevent the digest from happening because resolving a $q deferred schedules a digest via $evalAsync. $qq should be used instead of $q when invokeApply is true.
As a side note, I wonder why the explicit call to $apply is needed in $http at all?

This looks great and will be a great option to improve performance for those of us still doing http polling.
@Utsav2 any chance you can modify the pull request to use $$q in lieu of of $q to get things moving again?

Can we try to push this in one of the near-future minor releases?

As @thorn0 mentioned, this is not enough to prevent the $digest. We need to also somehow swap $q for $$q depending on the invokeApply argument (hacky demo showcasing swapping $q for $$q).

As @thorn0 mentioned, this is not enough to prevent the $digest. We need to also somehow swap $q for $$q depending on the invokeApply argument (hacky demo showcasing swapping $q for $$q).

Correct me if I'm wrong here, but isn't it enough to just swap $q for $$q in the service - regardless of the parameter value? As mentioned, $http is already going to conditionally invoke $apply with this change. No reason that $q needs to do anything.

@colinmorelli Actually, the $apply() call modified by this PR isn't needed at all because it does nothing. It's just a leftover, and there is a PR to remove it: #13128. After it gets merged, the invokeApply option can be implemented by simple switching between $q and $$q like it's done in $timeout.

I know this is a larger conversation...but that feels backwards to me. If anything is going to be doing $rootScope.$apply, my opinion is that it should be at the highest level possible. In other words, I'd sooner opt for having $http always use $$q, and schedule digests where necessary than have a low level promise service have a side effect of causing the $rootScope to be digested.
All that said, I'd still like to be able to get this in. Having $http constantly pushing $rootScope changes is painful.

Why do you think $http itself needs to schedule digests? A digest is needed when there is a probability that something was changed in the model. $http doesn't change any scopes. The callbacks of the promises do.

I think what you said is exactly my point: $http doesn't change any scopes. And $q certainly does not. The callbacks that are provided to them do. In an ideal world, I actually don't think $http should schedule digests either. I'd rather personally have control over which scopes are digested in a callback (think something like thenInScope($scope) as an addition to the promise API).
But, that said, I definitely don't think that creating and resolving a promise with $q should, by default, cause a dirty check to be run across the entire application. $q is a low level building block in angular. It has a plethora of use cases. Because of that, we now have $$q and $q because sometimes you don't want $rootScope.$apply to be run.
I understand why it was done. I think the simplicity of being able to just call .then() and have it "just work" makes sense, especially for early adopters. But as applications grow, the side effect of digesting the entire application every time an $http response comes back becomes less desirable.

Changing the behavior of $q would be too much of a breaking change. So using $$q (or native Promise) and adding the invokeApply option everywhere is the only thing that can be done about it. Apart from$timeout and $http, what else needs it?

+1
I noticed that because $http is used to fetch templates (be they triggered by $http.get, ng-include or component templateUrls) there is a $rootScope.$digest() on every one.  So if I have 20 templates loading during application bootstrap, there are 20 $rootScope.$digest()s.
I know this is a little off topic, but if the invokeApply option was added here (and I would love it for polling, and other reasons) surely we can avoid the digest on every template fetch?

Any updates on this?

We feel that this is somewhat of a corner case that is not required for the vast majority of situations.
So we do not intend to implement this feature. Thanks for the work on this @Utsav2.

Oh nuts!   Well, it's a corner case, except for...  probably most non-trivial apps.  But I understand the need to rationalise... the resource allocation on Angular 1.x must be asymptoting rapidly to 0. :P


Development

Highlights

Created a new Rails app called 'hello-rails-react'.
Initialized the project with Git.
Installed needed node dependencies.
Created a babel.config.js in the root folder of the project.
Updated webpack.config.js to include the babel loader.
Made sure that the project has a Postgres database set up.
Created a table for storing messages and created 5 different greetings.
Created an API endpoint that selects a random greeting from the table.
Created a static view that will be the root of the app.
Created the App component with react-router and rendered it in the static view.
Created the Greeting component that will display a greeting. Set it up as a route in the App component.
Created a store, an action, and a reducer that will connect to the API endpoint to get the random greeting.
Displayed the random greeting in the Greeting component.

@descholar-ceo ,
Fixed the issue.
Thanks a lot.

@KDlamini ,
Thanks a lot


Add GrpcExecutors metrcis

What changes are proposed in this pull request?
Added some GrpcExecutors ThreadPool metrics
Why are the changes needed?
Add a way to monitor worker load info. Include worker read/write/cache thread pool.
Does this PR introduce any user facing changes?
no

The time complexity of metrics operation is O(1), so it is a cheap operation

alluxio-bot, merge this please


got response of COMx:null"

Describe the bug
I put UF2 on the device, it reboots.  I open a command prompt as admin and type **.exe ls and all I get is COM13:null as response.  not sure what to do from here, thx.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
I expected to see a device.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

OK, I feel stupid, I changed the name to "max" and now it parses as COM13:max.   It is telling me 'success'.  I think I have a blown up light string (It is 8 LED inside some ARGB fans).
Ideally you could have an example screenshot of what people would expect to see.  I couldn't tell if 'null' meant nothing found on COM13.  I now realize null means 'default name/no name set'
The Pico is only showing 1.8v max on my multimeter from the Data pin, no idea if that is OK.

I just tried running it, and I found an issue I somehow hadn't encountered before. While I'm fixing it, can you try to make your LED strip green?
I don't see any measurable voltage on my data pin, but it should be fine.
I will update the README along with my fix.

I just fixed an issue where the first digit of a hex value could not be a letter. Does that fix your problem?


pthread_rwlock_t implementation is missing try-lock functions (IDFGH-7685)

ESP-IDF has recently added support for pthread_rwlock_t (https://github.com/espressif/esp-idf/commit/32e34447018539522c8ffae612408ef34d395783), but strangely the try-lock functions pthread_wrlock_tryrdlock and pthread_wrlock_trywrlock are missing... I'm wondering why they have been omitted?

@Spacechild1

I'm wondering why they have been omitted?

They simply haven't been implemented. The original feature request came from the Rust-community who needed only the simple functionality. I'll take a look at the code within the next few days.

Thanks!

to see if the implementation would be easy.

They are pretty easy to implement: instead of waiting on the condition variable, you would just unlock the resource mutex and return EBUSY. I can also make a PR if necessary.

Has there been any progress on this? I think this functionality would be pretty neat to have. Speaking from a Rust perspective, it's actually required to make full use of the tracing ecosystem.

I also encountered this problem. It would be nice to have this for the Rust ecosystem.

The try-lock functions have been merged into master. Feel free to take a look.

Looks like https://github.com/espressif/esp-idf/commit/e7312cccea37c12bea6b9a0e6ba5c9f39762391a is still not in any release. What's the policy here? What future release would this be contained in?

Hi @svenstaro, it has been merged to master. This means it will go into the next release (v5.2), as well as all the following releases.


not working with bootstrap table while filtering

I´m Using this:
https://github.com/wenzhixin/bootstrap-table
almost working ok, but when I search for one record, the x-editable is not working while filtering in bootstrap table. Any ideas?

Same around here... Hope someone will advise

Just trying to help: After a lot of fiddling around, I gut x-editable up an running with the very powerfull datatables.net Library.   Bootstrap-Table also looks nice.   If x-editable is not working anymore after filtering, I'd guess, that most probably somehow a non initialized editable DOM element remains. I found that it is very important to call the inital .editable( { ... } ) call on the  correct DOM element.

Use this:  https://api.jquery.com/on


Remove conflicting View components to set a default z-index for Box

Nice! Good job hunting this frustrating issue down and fixing it


Use keydown/keyup in typeblocking for non-printable keys

Starting in Firefox 65 (and presumably in Chrome somewhat soon), non-printable characters (e.g., arrow keys, ESC) won't be reported via the keypress event. This breaks typeblocking. We should switch to using keydown or keyup to handle these. Relevant Firefox issue.
Some experiments to run:

How did key press interact with the system keyboard timings? Is keydown or keyup more suited to similar behavior?
Test the following key behaviors and make sure they work correctly under the new implementation:
a. up/down after opening the list of typeblocking options
b. escape key to close the typeblocking window
c. enter key to select an option

On second thought, most of the typeblocking functionality is provided by the Google Closure Library's autocomplete widget. It might just be a matter of upgrading to the latest version of the closure compiler (which will also need some testing).


🐛 [BUG] - Memory Leakage with VSCode extension

Description
When I use the extension, my memory will slowly goes to 16G and VSCode then crashes. I believe there may be memory leakage.
Reproduction steps
When developing foundry project, the memory slowly goes from 5G to 16G and then VSCode crashes. I have to restart VSCode before the memory is full.

Reproduction URL
No response
Screenshots
No response
Logs
No response
OS
Linux

Can confirm on Mac os x. Python process leaks like crazy, I have seen 32G. Will be grateful for a fix.


download filtered list of studies from curation app

This is a feature request for a way to download a list of high level study meta-data from the curation app.
The use case is a curator filtering the studies in the curation system using the functions on the 'curation home' page (https://www.ebi.ac.uk/gwas/curation/studies?page=1), and being able to download (e.g. csv format) all the results returned.  The download should include all the fields visible in the curation home page (e.g. author, title, curator, status, notes etc.) AND GCST (which is not currently visible).
My primary use case is searching the notes (using the 'search notes' search box) for a specific term. I then want to examine the returned studies more closely.
Ideally there would be a download button, similar to the one on the main UI.  But a script-based method would also be workable.

@aoifemcm , can you please test the filter study list export in snoopy, its ready for testing : http://snoopy.ebi.ac.uk:9680/gwas/curation/studies?page=1&notesquery=PGS

@ljwh2 and @aoifemcm , I will also like to know if there will be a use case requiring you to export all the studies i.e without applying any filter, thats going to be a huge list of over 10,000 records, and such large request will take some length of time to deliver, I just pegged the maximum downloadable rows to 1000 rows at the moment.
You can let me know if there might be need to download all 11,000+ studies, I will open up the limit, but I will need to implement multithreading enhancement on the query to make it faster

@sprintell I think it is fine to release with 1000 row limit. The functionality works fine for me, @aoifemcm please confirm?


Add COMMIT_TYPES.BUMP to parts dict.

Previously was undefined, causing the CI to show up as failed.
This fix corrects this bug, making the CI pass
again correctly.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #416   +/-   ##
=======================================
  Coverage   60.64%   60.64%
=======================================
  Files          66       66
  Lines        3232     3232
=======================================
  Hits         1960     1960
  Misses       1272     1272

Continue to review full report at Codecov.

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


refactor: use lighter modules

These changes significantly reduce the size of this package by lightening the dependencies.

clsx is a much lighter alternative to classnames and works with the same API.
I avoided install the entire lodash package because we only use debounce method.

thanks @aykutkardas
merged 🙌


Extract “Tangled circles”

Then, the circular contigs were left alone, and each tangled “circle” was re-assembled by Hifiasm-meta with default parameters, using the fragmental contigs that constructed the “circle” as input reads, and resulted seven extra circular contigs.

HiI am using hifiasm-meta for metagenome assembly and have divided the assembled results into three types. However, I am encountering some issues, as mentioned above, because I am unfamiliar with the software and don’t know how to extract and reassemble the “tangled circles.” I would greatly appreciate any help you can provide.
Best wishes

Hi,I have been resolved the problem

Sorry for the late rely. Glad it's resolved. Please feel free to drop a new issue if you have any questions :)

Hi, I'm sorry to bother you again. I encountered the following error while running hifiasm, and I'm not sure what it means. It's also worth noting that the memory usage can reach up to 600GB during the run.
Writing reads to disk...
wrote cmd of length 387: hamt version=0.3-r073, ha base version=0.13-r308, CMD= /home/jiaoh/00.Software/hifiasm-meta/hifiasm_meta -o /home/jiaoh/10.meta-genome/04.Enviroment/01.PRJNA879921/02.Assembly/plant_gas -t 50 /home/jiaoh/10.meta-genome/04.Enviroment/01.PRJNA879921/01.host_remove/plant_gas.clean.fq.gz
Bin file was created on Mon Sep  9 09:59:05 2024
Hifiasm_meta 0.3-r073 (hifiasm code base 0.13-r308).
Reads has been written.
[hamt::write_All_reads] Writing per-read coverage info...
[hamt::write_All_reads] Finished writing.
Writing ma_hit_ts to disk...
ma_hit_ts has been written.
Writing ma_hit_ts to disk...
ma_hit_ts has been written.
bin files have been written.
[M::hamt_clean_graph] (peak RSS so far: 620.3 GB)
[M::hamt_clean_graph] no debug gfa
[M::hamt_clean_graph] (peak RSS so far: 620.3 GB)
MGA.sh: line 27: 30568 Killed                  ~/00.Software/hifiasm-meta/hifiasm_meta -o ${path}/02.Assembly/${i} -t ${threads} ${fq_clean}

Looks like oom kill, unless job hit some time limit. Could you try resuming the run by ~/00.Software/hifiasm-meta/hifiasm_meta -o ${path}/02.Assembly/${i} -t ${threads} ${fq_clean} in the same directory, with all variables the same as before? The stage after all-v-all read ovec should use less memory and hopefully could finish.
If you have other samples to run, or runs killed before the log could say "bin files have been written", please try the meta_dev branch (commit f98f1ad, r74) instead, which tries to fix the high peak RSS issue and otherwise identical to r73. I will merge r74 into master and update bioconda this week.

Hi, has the latest r74 version been released? Does this version address the high peak RSS issue and help reduce memory usage? Thank you!

It is now merged into master and is in the current release. I also opened PR at bioconda, which is waiting for review and hopeful will be merged soon. Thanks for your patience.

Hi, I saw that you released an update, and I immediately installed it using conda. However, unfortunately, I encountered the following error. Could you please help me understand what might be the cause
[M::main] Start: Mon Sep 23 14:42:49 2024

[M::hamt_assemble] Skipped read selection.
/opt/gridview/slurm/spool_slurmd/job9804618/slurm_script: line 53: 112549 Segmentation fault      hifiasm_meta -o ${output}/02.Assembly/${i} -t ${threads} ${fq_clean}

Hello, I am still encountering the above error when rerunning locally on the HPC. The data is from all Colorectum data in PRJNA748109.
hifiasm_meta -o 02.Assembly/PRJNA748109_Colorectum  -t 50 ../05.PRJNA748109_Colorectum/01.host_remove/PRJNA748109_Colorectum.clean.fq.gz

Hello, I am still encountering the above error when rerunning locally on the HPC. The data is from all Colorectum data in PRJNA748109.
hifiasm_meta -o 02.Assembly/PRJNA748109_Colorectum  -t 50 ../05.PRJNA748109_Colorectum/01.host_remove/PRJNA748109_Colorectum.clean.fq.gz
[M::main] Start: Tue Sep 24 11:20:12 2024

[M::hamt_assemble] Skipped read selection.
Segmentation fault

Hello. I'm sorry to bother you again. What should I do when encountering the following log information? However, I still obtained the assembled results.
********** checkpoint: post-assembly **********

[M::hamt_clean_graph] (peak RSS so far: 126.1 GB)
[M::hamt_ug_opportunistic_elementary_circuits] collected 0 circuits, used 0.02s
[M::hamt_ug_opportunistic_elementary_circuits] wrote all rescued circles, used 0.00s
[T::hamt_ug_opportunistic_elementary_circuits_helper_deduplicate_minhash] got the sequences, used 0.0s
[T::hamt_minhash_mashdist] sketched - 0.0s.
[T::hamt_minhash_mashdist] compared - 0.0s.
[T::hamt_ug_opportunistic_elementary_circuits_helper_deduplicate_minhash] collected mash distances for 0 seqs, used 0.0s
[M::hamt_ug_opportunistic_elementary_circuits_helper_deduplicate_minhash] had 0 paths, 0 remained (0 dropped by length diff, 0 by length abs),used 0.0s after sketching.
[M::hamt_ug_opportunistic_elementary_circuits] deduplicated rescued circles, used 0.01s
[M::hamt_ug_opportunistic_elementary_circuits] wrote deduplicated rescued circles, used 0.00s
[M::hamt_simple_binning] Will try to bin on 101 contigs (skipped 0 because blacklist).
Using random seed: 42
Perplexity too large for the number of data points!

Perplexity too large for the number of data points!

Sorry about the vague error. This run actually finished, both the assembly and the circle finding results should have been produced. The error was on the built-in MAG binning, which failed to find any bins: either because the sample was simple & there is nothing to bin with, or the assembly was fragmented & there is nothing to bin with. I should've include catching of this signal in the latest patch, but forgot to...
Is this the PRJNA748109 that segfaulted, or a different sample?

Thank you for clarifying my confusion. The segmentation fault occurred during the run of Colorectum in PRJNA748109.

So did PRJNA748109 somehow managed to have a run without the segfault, and got to the "checkpoint: post-assembly" part as the log posted above? Or this sample always triggered the segfault, while other samples of yours were assembled?
Thanks for letting me know though, I will remember to test on PRJNA748109 when I have access to servers. Sorry for no actual fix at the moment.

Hello, I'm not sure what the reason is, but when I switch to another server, it runs successfully. However, on some servers, including clusters, it encounters a segmentation fault (SG). They were all installed via conda.

I see, thanks so much for the report. I will remember this when testing.

Perplexity too large for the number of data points!

Sorry about the vague error. This run actually finished, both the assembly and the circle finding results should have been produced. The error was on the built-in MAG binning, which failed to find any bins: either because the sample was simple & there is nothing to bin with, or the assembly was fragmented & there is nothing to bin with. I should've include catching of this signal in the latest patch, but forgot to...
Is this the PRJNA748109 that segfaulted, or a different sample?

Hi @xfengnefx,
Is there any opportunity to fix the Perplexity too large for the number of data points! error reporting? It's wreaking havoc on the cluster for me right now. We're running a lot of samples with lower data volumes and the post-assembly binning is breaking the workflow for many of the samples. Alternatively, is there an option to turn off the binning steps?


Add new OMs of the month

This is gonna take many commits :(
srry this is my first big pr

This is gonna take many commits :(
srry this is my first big pr

I was hoping you would do this. I need someone to take over from me one day! :)

I was hoping you would do this. I need someone to take over from me one day! :)

Also fix all the Travis errors

Also fix all the Travis errors

:)

:)

Did you test it, this latest version of the code

Did you test it, this latest version of the code

Srry got dcd, yes the code works

Srry got dcd, yes the code works


HBASE-27684: add client metrics related to user region lock. (#5081)

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 23s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m  5s
branch-2.4 passed

+1 :green_heart:
compile
1m  2s
branch-2.4 passed

+1 :green_heart:
shadedjars
3m 54s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 50s
the patch passed

+1 :green_heart:
compile
1m  1s
the patch passed

+1 :green_heart:
javac
1m  1s
the patch passed

+1 :green_heart:
shadedjars
3m 53s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m 26s
hbase-client in the patch passed.

+1 :green_heart:
unit
162m 43s
hbase-server in the patch passed.

187m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5133/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5133

JIRA Issue
HBASE-27684

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b0124c46d616 5.4.0-144-generic #161-Ubuntu SMP Fri Feb 3 14:49:04 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 4ebf6c8d55

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5133/1/testReport/

Max. process+thread count
2850 (vs. ulimit of 30000)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5133/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  2s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 27s
branch-2.4 passed

+1 :green_heart:
compile
0m 54s
branch-2.4 passed

+1 :green_heart:
shadedjars
3m 33s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 39s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 22s
the patch passed

+1 :green_heart:
compile
0m 53s
the patch passed

+1 :green_heart:
javac
0m 53s
the patch passed

+1 :green_heart:
shadedjars
3m 32s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 59s
hbase-client in the patch passed.

+1 :green_heart:
unit
172m 36s
hbase-server in the patch passed.

195m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5133/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5133

JIRA Issue
HBASE-27684

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 8ac8147ce332 5.4.0-144-generic #161-Ubuntu SMP Fri Feb 3 14:49:04 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 4ebf6c8d55

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5133/1/testReport/

Max. process+thread count
2379 (vs. ulimit of 30000)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5133/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Add support for testcontainers

Please add support for org.testcontainers:testcontainers:1.17.6.
Depends on #128.

Working on that one.


[Crosswalk-16][misc] Update upgrade method in feature files

Impacted tests(approved): new 0, update 3, delete 0
Unit test platform: Crosswalk Project for Android 16.45.421.19
Unit test result summary: pass 3, fail 0, block 0
BUG=https://crosswalk-project.org/jira/browse/XWALK-6037
BUG=https://crosswalk-project.org/jira/browse/XWALK-6052

LGTM


Trackback most recantcall ( using termux to run linux)

I used android and use termux to run linux kalinethunter so i got this
root@localhost:~/kickthemout# python3 kickthemout.py Traceback (most recent call last):   File "kickthemout.py", line 753, in <module>      defaultInterface = getDefaultInterface()   File "kickthemout.py", line 154, in getDefaultInterface     network, netmask, _, interface, address = max(iface_routes, key=lambda item:item[1]) ValueError: max() arg is an empty sequence i already reinstall kickthemout but still got nothing

Hi there @Scholes13. Unfortunately, KickThemOut does not support Android devices. Thanks!


fix(UserProfileImage): fix tooltip version of user profile image

Contributes to #1743
Fixes the hover/focus state of the tooltip version of the UserProfileImage component.
What did you change?
packages/cloud-cognitive/src/__tests__/__snapshots__/styles.test.js.snap
packages/cloud-cognitive/src/components/UserProfileImage/UserProfileImage.js
packages/cloud-cognitive/src/components/UserProfileImage/_user-profile-image.scss

How did you test and verify your work?
Storybook

Yes, you're right @elycheea, the --container is kind of unnecessary. I'll update and remove it to just be .${blockClass}__tooltip


context-based comps, hooks and missing provider in 2.0

Hi,
Currently, it's possible to use formik in v2 which does not require a parent FormikProvider
But this will make all components using FormikContex to fail. It's actually a bit nasty because there's no warning on mount, but as the context methods are not injected into the consumer components, we get this kind of errors:

I think we should
1) Make it fail fast
const form = useFormik()
return <FieldArray>...</FieldArray>

This should crash/error on mount instead of on attempt to modify form
2) Document that this is possible:
const form = useFormik()
return <FormikProvider value={form}><FieldArray>...</FieldArray></FormikProvider>

It's a workaround I'll use temporarily (as I'm for strong typesafety/manual typesafe wiring, I try to avoid using context-based components)
3) Allow all context-based components to be able to receive the form as props
const form = useFormik()
return <FieldArray form={form}>...</FieldArray>

All context based components and hooks should crash with a warning. In a perfect world there is a formik.getFieldArrayHelpers that can be used without context just like formik.getFieldProps

Closing due to long inactivity


Update readme.md to reflect changes in watch.js

There is outdated information under Debuggers/For gulp, this is how i disabled PHPCS:
If you don't want to use phpcs with gulp, you can disable it by changing the line watch(config.php.watch, series('phpcs')).on('change', bs.reload); to watch(config.php.watch).on('change', bs.reload); in /gulp/tasks/watch.js.

Yeah, it can get outdated sometimes as we're fast with updates. While you're at it, please send a PR? Closing this as an issue for now.


Server returned HTTP response code: 403

androidStudio create new a project ,This situation always occurs.
Server returned HTTP response code: 403 for URL: https://services.gradle.org/distributions/gradle-4.10.1-all.zip

This is public on Internet. We didn't receive any other report for this issue, so I strongly recommend you checking yourself's network, e.g. firewall, proxy, etc.
P.S. I can download this file without issues.

I tested it, the browser can download it directly, but androidStudio downloads the prompt number 403, so I think it is impossible to be a firewall problem, so it is probably the problem of androidStudio itself, but I still reinstall androidStudio is still invalid, so this with you We have no direct relationship, right? If so, should I consult the official androidStudio?

You may need to check the proxy settings for AS itself.

It has not been set up before, it can be used, but now suddenly prompted an error, can not be downloaded.


Add sleep time after tests are run

Is there a motivation for this?
If so, it should be explained somewhere with a comment around he sleep.


T8.3.1 adapt 'post-mortem' tool

we do not need post-mortem tool for analysis anymore.
it turned out to more practical to do the analysis directly on the data from logs and explorer.


macOS Keychain - Use accessiblity option for all operations and throw PlatformException for SecErrors

Changes from PR #602 but for macOS.

Could possibly fix or at least fail with a native error message #581, #350 and #302.

Tested and working, thanks again !


Update libgit2 to c655def11

https://github.com/libgit2/libgit2/compare/baa87dfc5...c655def11

Closing in favour of #44


unlucky md5 checksum value is parsed to inf

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
I have a File model with an md5 checksum. One of my files got a value of<PHONE_NUMBER>5203397e00089319024245, which could be interpreted as an integer. I want to coerce it into a string, but somewhere it gets converted to inf. I believe this is related to #6045 and #5606.
What should I do to get around this?
Thank you for your help :bow:
Example Code
from pydantic import BaseModel, ConfigDict

class File(BaseModel):
    model_config = ConfigDict(coerce_numbers_to_str=True)
    md5: str

File.model_validate_json('{"md5": 208622926}')
# >>> File.model_validate_json('{"md5": 208622926}')
# File(md5='208622926')

File.model_validate_json('{"md5":<PHONE_NUMBER>5203397e00089319024245}')
# >>> File.model_validate_json('{"md5":<PHONE_NUMBER>5203397e00089319024245}')
# File(md5='inf')
#
# I would expect: File(md5='20862292665203397e00089319024245')

Python, Pydantic & OS Version
pydantic version: 2.7.1
        pydantic-core version: 2.18.2
          pydantic-core build: profile=release pgo=true
                 install path: /usr/local/lib/python3.10/site-packages/pydantic
               python version: 3.10.14 (main, May 14 2024, 08:46:25) [GCC 12.2.0]
                     platform: Linux-6.4.16-linuxkit-x86_64-with-glibc2.36
             related packages: mypy-0.991 email-validator-2.0.0.post2 typing_extensions-4.6.3 fastapi-0.101.1
                       commit: unknown

Hey,
I think it fails because<PHONE_NUMBER>5203397e00089319024245 is a very huge floating point number. You could try:
File.model_validate_json('{"md5": "20862292665203397e00089319024245"}')

That would work - but unfortunately I do not have control over the json sent to the application.

This works at least in this specific case:
File.model_validate(json.loads('{"md5":<PHONE_NUMBER>5203397e00089319024245}', parse_float=str))

Thanks @mikeleppane :bow:

Marking as resolved for now, thanks @mikeleppane!
I think this is an infrequent enough issue that we can close.


Question about mobile platform deploy

As mentioned in other issues:

https://github.com/Meituan-AutoML/MobileVLM/issues/8
https://github.com/Meituan-AutoML/MobileVLM/issues/4

Deploying on mobile platform such as Snapdragon 888 is based on llama.cpp, the questions  I want to ask is:

Did you use QNN to deploy the model?
Did you rewrite the gpu kernel based on opencl or use clblast?

Hi, we are closing this issue due to the inactivity. Hope your question has been resolved. If you have any further concerns, please feel free to re-open it or open a new issue. Thanks!


Monitor explicitly chosen output devices for liveness

This mirrors what is done for input devices, and enables the output tests. This fixes cubeb's behavior with Firefox when unplugging a device that is being played to with setSinkId and that does not affect the default device (we used to always install the default-output listener and therefore changes to the default device would trigger a reinit, which would result in an error if the device no longer exists).

I see this is a new take on #170, well let me know what you think.


Poor pigs LC solution

There are buckets buckets of liquid, where exactly one of the buckets is poisonous. To figure out which one is poisonous, you feed some number of (poor) pigs the liquid to see whether they will die or not. Unfortunately, you only have minutesToTest minutes to determine which bucket is poisonous.
You can feed the pigs according to these steps:
Choose some live pigs to feed.
For each pig, choose which buckets to feed it. The pig will consume all the chosen buckets simultaneously and will take no time. Each pig can feed from any number of buckets, and each bucket can be fed from by any number of pigs.
Wait for minutesToDie minutes. You may not feed any other pigs during this time.
After minutesToDie minutes have passed, any pigs that have been fed the poisonous bucket will die, and all others will survive.
Repeat this process until you run out of time.
Given buckets, minutesToDie, and minutesToTest, return the minimum number of pigs needed to figure out which bucket is poisonous within the allotted time.
Example 1:
Input: buckets = 4, minutesToDie = 15, minutesToTest = 15
Output: 2
Explanation: We can determine the poisonous bucket as follows:
At time 0, feed the first pig buckets 1 and 2, and feed the second pig buckets 2 and 3.
At time 15, there are 4 possible outcomes:

If only the first pig dies, then bucket 1 must be poisonous.
If only the second pig dies, then bucket 3 must be poisonous.
If both pigs die, then bucket 2 must be poisonous.
If neither pig dies, then bucket 4 must be poisonous.

At time 15, there are 2 possible outcomes:

If either pig dies, then the poisonous bucket is the one it was fed.

At time 30, one of the two pigs must die, and the poisonous bucket is the one it was fed.

Constraints:
1 <= buckets <= 1000
1 <= minutesToDie <= minutesToTest <= 100
Accepted
121.7K
Submissions
204.5K
Acceptance Rate
59.5%
Topics
Companies
Hint 1
Hint 2
Hint 3
Discussion (114)
Choose a type
Copyright © 2024 LeetCode All rights reserved
1.8K
114

I'd like to work on it please@Kushal997-das

Hi there!
I am the Mentor of this project.
Although this repo is not part of Hacktoberfest 2024, we have some great alternatives for you. Welcome to SkillShow, a repository focused on skill enhancement!
Guidelines:

Please adhere to the existing guidelines.
No additional rules, thanks!
Check it out here: SkillShow.

Note: Start by creating an issue. Once it’s assigned to you, feel free to open a pull request (PR). Directly opening a PR will lead to an invalid label.
Looking forward to your contributions!


fix(avatar): avoid passing disableAnimation prop to a DOM element

Closes #3109
📝 Description

Add a brief description

⛳ Current behavior (updates)

Please describe the current behavior that you are modifying

🚀 New behavior

Please describe the behavior or changes this PR adds

💣 Is this a breaking change (Yes/No):

📝 Additional Information

Summary by CodeRabbit

Bug Fixes

Resolved an issue in the avatar component to prevent passing the disableAnimation prop to a DOM element, ensuring better compatibility and performance.

Improvements

Enhanced the avatar component with improved logic for filtering DOM properties based on the type of image component, leading to more robust and flexible behavior.

I am on 2.4.2 and the error persists. Anyone else?

@AmazingTurtle Sorry about that. I can confirm that there is an extra disableAnimation introduced during resolving the merge conflict. I've made another PR here.

Thank you! Yes I'm experiencing it on 2.4.2 as well. Hope the new PR gets merged soon =)

@AmazingTurtle @paperdiamond The PR has been merged. You guys can use the canary version 0.0.0-canary-20240616172522 as a temp fix at the moment.

Thank you @wingkwong that did resolve the issue =)


[stable/grafana] add pod labels as configuration option

Signed-off-by: Miles Pool<EMAIL_ADDRESS>
Is this a new chart
No
What this PR does / why we need it:
Adds configurable labels to Grafana pods, to enable custom pod selection.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test
/lgtm


NR_CLOSED error intermediately on AUTH recently since last month or so on our Lambda NodeJS 12.x

Issue

We are using redis node module for Redis client to communicate with Redis server. We are facing NR_CLOSED error intermediately on AUTH recently since last month or so on our Lambda. We are using node redis library and redis-labs as our redis server, details of which are mentioned below.

2021-05-25T08:47:00.034Z	ed14111b-3ce2-4354-b46e-3101c27b6efa	ERROR	Uncaught Exception
{
    "errorType": "AbortError",
    "errorMessage": "Stream connection ended and command aborted. It might have been processed.",
    "code": "NR_CLOSED",
    "command": "AUTH",
    "args": [
        "*******"
    ],
    "origin": {
        "errorType": "Error",
        "errorMessage": "Redis Error",
        "stack": [
            "Error: Redis Error",
            "    at Object.retry_strategy (/var/task/services/CacheService.js:15:20)",
            "    at RedisClient.connection_gone (/var/task/node_modules/redis/index.js:618:41)",
            "    at RedisClient.on_error (/var/task/node_modules/redis/index.js:410:10)",
            "    at Socket.<anonymous> (/var/task/node_modules/redis/index.js:279:14)",
            "    at Socket.emit (events.js:314:20)",
            "    at Socket.EventEmitter.emit (domain.js:483:12)",
            "    at emitErrorNT (internal/streams/destroy.js:92:8)",
            "    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)",
            "    at processTicksAndRejections (internal/process/task_queues.js:84:21)"
        ]
    },
    "stack": [
        "AbortError: Stream connection ended and command aborted. It might have been processed.",
        "    at RedisClient.flush_and_error (/var/task/node_modules/redis/index.js:362:23)",
        "    at RedisClient.connection_gone (/var/task/node_modules/redis/index.js:624:18)",
        "    at RedisClient.on_error (/var/task/node_modules/redis/index.js:410:10)",
        "    at Socket.<anonymous> (/var/task/node_modules/redis/index.js:279:14)",
        "    at Socket.emit (events.js:314:20)",
        "    at Socket.EventEmitter.emit (domain.js:483:12)",
        "    at emitErrorNT (internal/streams/destroy.js:92:8)",
        "    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)",
        "    at processTicksAndRejections (internal/process/task_queues.js:84:21)"
    ]
}

Before 2 months we never got this redis error. This is how we have been using it in our code in Lambda.
CacheService.js
var redis = require("redis");
var await = require('asyncawait/await');
var async = require('asyncawait/async');
const { promisify } = require('util');

module.exports = function (config) {
	this.client = redis.createClient({
	host: config['redis']['host'],
	port: config['redis']['port'],
	password:config['redis']['password'],
    retry_strategy: function (options) {

        if (options.error) {
            console.log("RedisError: ", options.error);
            return new Error('Redis Error');  //line 15 for error stack reference
        	}
        return 100;
    	}
        });

        this.getCachedData = async function getCachedData(key) {
		const getAsync = promisify(this.client.get).bind(this.client);
		var data =  await getAsync(key);
		return data
	}

	this.closeConnection = function closeConnection() {
		// close the redis connection
		this.client.quit();
	}
}

This is how this service is consumed
module.exports = {
    resetConfig: async function (paramConfigData, falconConfigData) {
        if (paramConfigData !== "" && paramConfigData.fetched_at < Date.now()) {
            paramConfigData = ""
        }

        if (paramConfigData === "") {

>         try {
>                 var configCacheHandler = new CacheService(falconConfigData)
>                 var cachedConfig = await(configCacheHandler.getCachedData(this.client+":config"));
                 paramConfigData = JSON.parse(cachedConfig);
                 paramConfigData.fetched_at = Date.now() + 10000;
                configCacheHandler.closeConnection();

            } catch (e) {
                console.log("Cached config RedisError:", e)
            }
        }
        return paramConfigData;
    }

}

Environment

Node.js Version: 12.x

Redis Library Version: 2.8.0

Redis Version: 6.0.6

Platform: Node JS(Lambda)

do you have a listener on the error event?
client.on('error', (err) => console.error(err));

in case there is an error event, and there is no listener, node.js will kill the process.
in case there is a listener attached, the listener will get executed, and the the retry strategy will kick in.

@leibale I'm kind of new to this. We are not using this. Can you point out how I can use it in my code shared above?

@ayushnenawati in CacheService.js#modules.exports
this.client = redis.createClient({
  // ...
});

this.client.on('error', err => console.error('Redis Client Error', err));


Implementation of Client Statistics feature

Implemented Client Statistics feature.

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test PASSed.

Windows test PASSed.

Linux test FAILed.

Windows test PASSed.

Windows test PASSed.

Linux test FAILed.

Windows test PASSed.

Linux test FAILed.

Linux test PASSed.

Windows test PASSed.

Windows test PASSed.

Linux test FAILed.

Windows test PASSed.

Linux test PASSed.


Command to share a surprise (random) rant!

It only picks from the pool of rants that have at least a score of 15.

Thanks for this @DFoxinator, i merged this in via 748a4e3 as it needed a test.


Improve AsinhNumericalEncoder

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

Project coverage is 100.00%. Comparing base (c6dc388) to head (0acfd3d).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #350   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          100       100
  Lines         3155      3155
  Branches       277       277
=========================================
  Hits          3155      3155

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


Add custom divider message

If user enters custom divider, maybe oglog should show something like: "Your divider will be {divider}".

Decided to just change message.


demo可以跑, 控制台打印一堆约束错误

@giveMeHug, please tell me your device os version and demo version?

xcode 8.2.1     demo version 1.6 beat

在模拟器上跑会打印约束问题  but 在真机上没有上述报错

在模拟器上跑会打印约束问题 but 在真机上没有上述情况

@giveMeHug simulator version？

@giveMeHug good catch, issue confirmed. thanks your report.

I have the same problem on iOS10.2, But it's ok on iOS8.1. Both iOS10.2 and iOS8.1 are simulator version.
I solve the problem by adding widthFenceConstraint.priority = UILayoutPriorityDefaultHigh; in methodfd_systemFittingHeightForConfiguratedCell: fix the problem.

@giveMeHug would you mind to use pod 'Alamofire', :git => "https://github.com/forkingdog/UITableView-FDTemplateLayoutCell.git", :branch => "master" to test if it works. we will release ASAP.


Improve study pane configuration

The Chore
It would be useful to be able to pass callback to the chart which will be called when the internal panes change size. Additionally it would be good to be able to set the initial size
ACs

[x] I can set the height of the study panes
[x] Studies should NOT grow proportionally when the chart canvas gets larger. ALL extra size when the chart grows should go to the main chart.
[ ] Studies should only shrink when the chart area gets smaller IF necessary to fit the chart and all the studies

Something like: if the chart would get smaller than the biggest study (because of resizing or the adding of studies), reduce ALL of the studies proportionally as the canvas gets smaller, BUT don't persist the studies temporarily smaller sizes (do persist if they are then manually sized though)

[x] The chart should greedily take the extra space.

Tasks

[x] Expose pane onChange callback
[x] Allow setting initial pane size in px/%
[ ] Adjust pane resizing logic
[x] Dev
[ ] Test

Additional details / background info

@mattrussell36 if I have multiple studies open and resize a study below another to be taller, it shrinks the study above. And vice versa, if i shrink a study below, the stufy above grows.
I would have though that the study above would remain the same size in both scenarios?


Add some metadata to integrators and export coefficients

Current behavior
There's no way to currently obtain the number of gradient calls for a given integrator.
Also, it is sometimes useful to have the integrator coefficients, and these aren't exported from integrators.py.
Desired behavior
Functions like:
def calls_per_integrator_step(c):
    if c==velocity_verlet_coefficients: return 1
    if c==mclachlan_coefficients: return 2
    if c==yoshida_coefficients: return 3

    else: raise Exception

def name_integrator(c):
    if c==velocity_verlet_coefficients: return "velocity_verlet"
    if c==mclachlan_coefficients: return "mclachlan"
    if c==yoshida_coefficients: return "yoshida"

    else: raise Exception

Also, to export the coefficients.

Per #681, we need some other ways to expose this information.
How about assigning the property to the return integrator object? We can type integrators as Protocal.

Yes, I think that would be good. The info we want attached is:

Order of the integrator
Number of grad calls
Name
Type (isokinetic or mclachlan)
The integrator itself (this could be a function of "isokinetic" or "euclidean", if you think that's a reasonable design decision

I think the decision ultimately tie to how these information is used in the library beyond benchmarking. Let's circle back when you have some examples.


[BUG]block finder was changed

http://www.idcray.com/pool/shares.jpg
http://www.idcray.com/pool/block.jpg
like this
we found two blocks
the share_id is 14778 and 14755 in Block table
but in the Shares table ID is 14781 and 14791
they are different
so the block finder was changed
how to fix it?

The shares from the shares table are not real block shares (upstream_result = N). If you are certain these are the block shares just assign them to those blocks.
At the same time go and check if your block chain had a hard fork. Those are the most common reason for issues in MPOS.
And last but not least your coin stratum may not insert the solved block hash into the finding share. MPOS will fall back to various other search mechanisms which are not as reliable as the block hash checksum in the share field.
And if all fails, mark those blocks as accounted for and MPOS will skip them. If they keep showing up you have a hard fork in your chain and you need to clean up the chain before deleting all blocks after the fork occurred.

I am now unavailable for two weeks (vacations and no internet - used a hotspot). Maybe someone else can help further if required.

why mpos cant record the real shares_id for new blocks?
need update mysql,or not?

Stratum, not MPOS. This is an issue with your coin daemon and stratum. Only once shares are inserted by you stratum server MPOS comes into play.
That's not fixable in MPOS. It has a lot of fallbacks in case stratum doesn't work as expected and the least favorable method to assigning a share is using any share that has about the same timestamp as the block. Bad way but the only left if all else failed.


Fix import error when module.file doesn't exist

Also, an update to RedisCache, to support passwords.

@mitsuhiko, any update on this?


Loading data is not working at all

At least for me OSM data is never, ever loaded.
If it is working in general - I can try debugging the app.

Aha, interesting. What version are you on?
If it's not 1.0.1-fdroid or 1.0.1-gplay, can you update using the APK in the latest release and try again? (1.0.1 has exception reporting, maybe that will catch something)

Now it claim that I should zoom in even on extreme zoom in.
I can try debugging once I get back to a computer

Okay, I'm first going to implement #7 (better status indicator) and #2 (faster loading). Hopefully that will make it easier to hunt down the problem.
The "Zoom in to show data" message showing when already zoomed in is already fixed, I'll let you know when I publish that version.

Thanks, then I will wait with more thorough debugging.

Alright, the status indicator has improved a lot and loading is now 44 times faster.
Do try again if you have the time, v1.1.0-gplay should be live on Google Play.
F-Droid is a little delayed, so if you use that you can instead install the apk from the releases page.

It shows me cloud with arrow (downloading?) but nothing happens for loooooooooooooooooooong time.
But something is finally being loaded!
Thanks for fixing.

Hmm yeah it's indeed downloading from the OSM api.
Out of curiosity: was the area densely mapped (like a city)?
If not that is a little weird.

Out of curiosity: was the area densely mapped (like a city)?

Yes, very densely mapped (Kraków - https://www.openstreetmap.org/#map=19/50.07717/19.88741 ). Maybe it should default to downloading smaller area?

Hmm indeed very slow.
But difficult to fix.


changed metric name to be descriptive of the pipeline type

Changing the metric name "element-counter" and "error-counter" to be more descriptive of the pipeline type.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

r: @pabloem
r: @manavgarg

looks like Spotless is broken here. Can you run ./gradlew :sdks:java:io:google-cloud-platform:spotlessApply and push again?

@pabloem Fixed it and checks should have passed!


Application unable to accept GPT API key

Perhaps this is related to issue #76 , but I am unable to get the application to recognise my paid API key.  I've attempted with both docker and conda.  I'm on Ubuntu 22.04.3 with python 3.9.18
Using Docker
sudo docker run -it -e OPENAI_API_KEY=Key_went_here -v "$(pwd)":/app zeroxeli/readme-ai:latest readmeai -o readme-ai.md -r Repo_went_here
Using Conda
First
export OPENAI_API_KEY=YOUR_API_KEY
Then
conda create -n readmeai python=3.9
and I enter the conda enviornment with
source activate readmeai
and install requirements.txt with
pip install -r requirements.txt
Finally running the application with
readmeai --output readme-ai.md --repository Repo_goes_here
Both implementations give me
"ERROR    HTTPStatus Exception:
Client error '404 Not Found' for url 'https://api.openai.com/v1/chat/completions'
For more information check: https://httpstatuses.com/404
with the link saying
"{
"error": {
"message": "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}"
I even tried to modify the https://github.com/eli64s/readme-ai/blob/4cc83dc49e0f5bf3b304d504394a9adf7c028acb/readmeai/core/model.py#L176C1-L176C75 to directly include my API key as a string, but this did not fix the issue.

Hi @johmicrot, thanks for reporting the issue. Have you tried installing the PyPI package readmeai directly? Can you run the steps below and report back when you get a moment?
pip install readmeai --upgrade

readmeai -r <repository-url>

Thank you,
Eli

@johmicrot one other thing to check, if you manually cloned the repo and are using conda, you need to use the command below to run the program:
python3 -m readmeai.cli.commands -r <repository-url>

Using the readmeai command can only be used if you installed the readmeai PyPI package.
See the project's README - running readme-ai section for more details on how to run the tool.
Thank you,
Eli

Sorry I meant to mention that i did also try it with pip using the commands you specified (outside of conda), and the python3 -m readmeai.cli.commands -r <repository-url> command (inside conda) also does not work and gives the same error.
I should have specified that it does generate the report, but it seems to be equivalent to the offline report.

@johmicrot in your docker command are you setting the api key as OPENAI_API_KEY=$OPENAI_API_KEY
For example, you can try running the following on one of my example repo.
docker pull zeroxeli/readme-ai:latest

export OPENAI_API_KEY="your-api-secret-key"

docker run -it -e OPENAI_API_KEY=$OPENAI_API_KEY -v "$(pwd)":/app zeroxeli/readme-ai:latest readmeai -o readme-ai.md -r https://github.com/eli64s/readmeai-ui

Also have you tried creating a new api key on OpenAI's site?

I executed all of the commands you provided, and actually i get a new error!
After pulling the latest image, exporting the key, and running the following docker command
sudo docker run -it -e OPENAI_API_KEY=$OPENAI_API_KEY -v "$(pwd)":/app zeroxeli/readme-ai:latest readmeai -o readme-ai.md -r https://github.com/eli64s/readmeai-ui
I get this response
exec /home/tempuser/.local/bin/readmeai: exec format error
So it appears something with the latest push broke it in my system.
Some possible causes that I'm aware of : Mismatched Architecture, Corrupted Image, Incorrect Shebang in Script (e.g. If /home/tempuser/.local/bin/readmeai is a script, it might have an incorrect shebang line), or possibly  Binary Built for Different OS.

The application uses gpt-4-1106-preview, which is not available for free accounts. To resolve this, either upgrade to a paid account or use the -m flag to change the model to gpt-3.5-turbo-1106. However, be aware of #61 if your repository is large, as it might cause errors. Switching to a pay-per-use account is recommended.
sudo docker run -it -e OPENAI_API_KEY=$OPENAI_API_KEY rmai readmeai -o readme-ai.md -r https://github.com/eli64s/readmeai-ui -m gpt-3.5-turbo-1106

@Ashu0Singh No, i actually have a paid account.
Interestingly when i specify
sudo docker run -it -e OPENAI_API_KEY=$OPENAI_API_KEY rmai readmeai -o readme-ai.md -r https://github.com/eli64s/readmeai-ui -m gpt-3.5-turbo-1106
I get the "429 Too Many Requests"
Then when i specify
sudo docker run -it -e OPENAI_API_KEY=$OPENAI_API_KEY rmai readmeai -o readme-ai.md -r https://github.com/eli64s/readmeai-ui -m gpt-4-1106-preview  (or even just -m gpt-4, the default)
then i get the 404 Not Found,
I just realized the error "You didn't provide an API key" I see when clicking on the "https://api.openai.com/v1/chat/completions" is actually not related to the run I just made, it is the HTTP error for clicking on the link.  But the two errors above still stand.

While I do have a paid account, i was sill somehow under the "free tier".  I pay 20 a month for gpt4, but somehow I just had to put $5 on to my account  to get the gpt-3.5-turbo-1106 model to work.  The latest update has the requirements.txt version pinned, perhaps that also fixed a previous error I had.  Closing the issue.
@Ashu0Singh thanks for the heads up about the usage, even with the gpt-3.5-turbo-1106 model I've quickly used up $ 0.39


Move to Core.Compiler?

To me it feel that @stable would make more sense in Base. The implementation seems fairly straightforward:

@stable annotates a function body via the meta mechanism (essentially trivial)
In inference, we add a check for a :stable meta annotation, and if found then once a function is done being inferred, we impose a rule: if the input types are concrete and the inferred output types are not, throw an error (during compilation)

However, it might be even better as a new AbstractInterpreter type. I've never played with that part of inference, so it might take some digging/asking to figure out what that implementation would look like.

I am 100% for this!
On LinkedIn @ChrisRackauckas mentioned he was going to talk to the compiler team about potentially doing this, though I am not sure what the status is.
Would also be nice to have the same features in Base with respect to configuration in Preferences.jl, like this: https://github.com/MilesCranmer/DispatchDoctor.jl?tab=readme-ov-file#usage-in-packages. I have found it useful to turn on instability checks for multiple packages during testing, while still having the "default" be disabled (in case downstream users are doing unstable things on purpose)

I had mentioned it to @topolarity and @gbaraldi, though I know they are a bit busy trying to get everything juliac ready for JuliaCon (https://pretalx.com/juliacon2024/talk/FUTLND/) as a "big reveal" of small binaries. But I do hope that we can find some of their time to do this properly. Again as I mentioned elsewhere, I think the interface here is solid, but I don't think the implementation is quite correct. It needs to run after Julia's compiler passes as there's the heuristics used here are not always true. For example, https://github.com/MilesCranmer/DispatchDoctor.jl/pull/31 union splitting at a high level is okay, but users can actually change the heuristic on a per-module basis, and there's other inference heuristics and effects analysis that could make unions split or not split. There's other issues as well, for example you might have a piece of code that doesn't infer, but due to DCE that code is just eliminated by the compiler so it turns into being a non-issue.
So at the end of the day, the only way to really know if you got "bad" behavior is to ask Julia if you have bad behavior after its compiler optimizations. Pre-optimizations will have false positives, and heuristics to remove those would introduce false negatives.
I had suggested at the LLVM level https://github.com/MilesCranmer/DispatchDoctor.jl/issues/30 because it could then just make use of the same infrastructure as https://github.com/JuliaLang/AllocCheck.jl. Using the LLVM level, you just need to flag functions that have jl_apply_generic (or correct me if I'm wrong, there might be another function or two, but it's at least a small finite list), and that would give you every spot where dynamic dispatch occurred in the final compiled code. That's actually just a subset of AllocCheck, since any dynamic dispatch will introduce allocations, and so it already effectively finds all of those spots.
So my first suggestion is to just "extend" alloc check to have a second macro that's just for dynamic dispatch checking (which IIUC is just subsetting the whitelist that already exists), and then using the ideas of DispatchDoctor.jl in order to have a better API. And I think we should use the DispatchDoctor.jl API ideas on the allocation-free checks as well, being able to annotate a function and have it only run in tests and such is a very nice idea. That implementation shouldn't take all that long and would get us a correct and usable form that handles both dynamic dispatch and allocation testing with a really nice high level API. So I'd "rush" to get that together as a generally usable tool.
From there, then I think we should consider what the next steps would be. Allocation testing cannot be moved to the Julia level IIUC because that will only be correct after LLVM optimizations, while dynamic dispatch is a Julia level thing that could be done in the AbstractInterpreter post inference and Julia level optimizations like DCE? That's a question mark from me as I'll let the compiler dev's answer that 😅. But I think the relative improvement of doing that next step of getting an AbstractInterpreter implementation vs the LLVM level one is low, as the LLVM level would already solve the correctness, though the AbstractInterpreter level would retain more high level information so it could have better error messages. So I personally wouldn't put that part of it at the highest priority.

there's other inference heuristics and effects analysis that could make unions split or not split

Indeed, this seems slightly tricky to do without going into the internals. Although perhaps a downstream type instability might be able to catch union splitting from the outermost Base.promote_op.

DCE

How different is Base.promote_op from what you have in mind? Base.promote_op looks to be an alias of Core.Compiler.return_type and is also used for things like figuring out the eltype in a list comprehension. So, is the main idea here to try to flag dynamic dispatch internal to a function?

and that would give you every spot where dynamic dispatch occurred in the final compiled code

Just to note that this would be slightly different behaviour from the existing @stable, which only checks for type stable return values, rather than any instances of dynamic dispatch in the body. The idea is that if you have some logging callback that does dynamic dispatch, it would not get flagged (whether that be positive or negative). In any case, I think that erroring on internal dispatch should be an optional flag as in certain contexts it is acceptable and it is just the return values that kill performance.
Right now, this is done with @unstable, which lets you declare certain functions as allowed. So, for example:
@stable begin

f(x) = x
g(x) = x
@unstable logging_callback(x) = ...
function h(x)
    logging_callback(x)
    f(x) + h(x)
end

end

h(1)

In this example, f, g, and h are all checked for unstable return values.
logging_callback would normally be checked as well (simply because it gets passed values from h), although here we have declared it @unstable which toggles back off the check.

I am just ducking in here quickly since any mention of moving things to Core or Base is the bat signal for me :) I think this is a cool package for users who want it, especially at the application level, but there are conceptual problems with @stable. Functions cannot really be divided into two kinds, must-be-stable and can-be-unstable, such that it would make sense to mark each function with its "kind". For example getindex(::Vector, ::Int) is only stable for vectors with concrete element types. Also these days many functions achieve type stability through constant propagation.

Just to note that this would be slightly different behaviour from the existing @stable, which only checks for type stable return values, rather than any instances of dynamic dispatch in the body.

I agree with checking return types being more useful; disallowing dynamic dispatch turns out to be very restrictive and often unrelated to performance, e.g. for logging and error paths.

I agree with checking return types being more useful; disallowing dynamic dispatch turns out to be very restrictive and often unrelated to performance, e.g. for logging and error paths.

Depends on the use case, one of our big use cases for these kinds of tools is codegen for static libraries where we want to remove the runtime, or at least hope juliac would remove the runtime. That has stricter requirements than just using things from Julia, and I think @gbaraldi mentioned the other day that he ran into this in that it's hard to ensure that library code satisfies the requirements for such an application.

I can definitely see use-cases for both of these modes. What I think would be nice is just have another option for this, like perhaps "extent". Along the lines of the existing options, you could have:

default_extent::String="return_only":

Change the default extent from "return_only" to "full" to also detect dynamic dispatch within the function body, analysing all compiled LLVM code after optimisations
To locally or globally override the mode for a package that uses DispatchDoctor, you can use the "instability_check_extent" key in your LocalPreferences.toml (typically configured with Preferences.jl).

Then you could configure this as another parameter with Preferences.jl, and even set it at a package level.
@stable default_extent="full" begin
    f(x) = x
    g(x) = x^2
end

You wouldn't be able to toggle it back off with @unstable, but I suppose that's exactly what you would want for static compilation.
@ChrisRackauckas if AllocCheck.jl adds this, perhaps DispatchDoctor.jl could alias it as a dependency, and call it whenever the user passes extent="full"? And DispatchDoctor.jl could still perform the return-only analysis as it does currently if extent="return_only".
P.S.,

For example getindex(::Vector, ::Int) is only stable for vectors with concrete element types. Also these days many functions achieve type stability through constant propagation.

Just for anybody scrolling through this thread, I want to emphasise that @stable applies to a method rather than a function. So the way to solve cases such as the one @JeffBezanson mentioned is to use:
@stable getindex(::MyVector, ::Int) = ...
@unstable getindex(::MyVector{MyUnstableType}, ::Int) = ...

The same advice applies for constant propagation. If DispatchDoctor starts complaining about an instability in some function you know will be inlined, just stick an @unstable on it, and you are good! The @stable on the outermost function will catch if that function is not being inlined any inference problems.
It might get tedious if you have many cases of this but I think it's still useful to declare explicitly what you expect to be unstable and inlined.


Requests to GCM should implement a timeout

(in https://golang.org/pkg/net/http/#Client allows a Timeout to be specified.
If no timeout is specified, then there is no timeout, and connections may be left open forever.
TLS dialing seems like it already has default timeouts.
func (self *gcmPushService) multicast should be changed

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain plentyproductions.com has exceeded the max emails per hour (202/200 (101%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from github-smtp2-ext1.iad.github.net ([<IP_ADDRESS>]:34925 helo=github-smtp2a-ext-cp1-prd.iad.github.net)
by server21.abstractdns.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256)
(Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1bJ0DA-0008MG-KX
for<EMAIL_ADDRESS>Fri, 01 Jul 2016 15:18:32 +0000
Date: Thu, 30 Jun 2016 12:10:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1467313806;
bh=6c/zeHz3AtZvkGbH8YSlWkDLG1KsjhhuaiR4IKX4kiI=;
h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post:
List-Unsubscribe:From;
b=kDbr3Ov3mEJUdZ9J0o7F8bqTLm58r+HhiISSVDXPUCWHpptbPQZ8MePnsElbNZjFV
ASX0h8PK3/4EnBtmCAxq5Ts9QECFf4gbi8k9Au0fcfjeFdhYGpeh3LyAPtitZx+sNr
PAhGfNZmxHRfH8Rs4ktoedZqP5UD9pG5jQhn30a8=
From: Tyson Andre<EMAIL_ADDRESS>Reply-To: uniqush/uniqush-push<EMAIL_ADDRESS>To: uniqush/uniqush-push<EMAIL_ADDRESS>Cc:
Message-ID<EMAIL_ADDRESS>Subject: [uniqush/uniqush-push] Requests to GCM should implement a timeout
(#124)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_57756e8e6a60b_7ce03ff7f81db2a031273c";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: TysonAndre
X-GitHub-Recipient: gtrevg
List-ID: uniqush/uniqush-push <uniqush-push.uniqush.github.com>
List-Archive: https://github.com/uniqush/uniqush-push
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/ABA47bxjnzyzm9nupxcc8zk0XQFiQXrXks5qRBSOgaJpZM4JCfxA
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>----==_mimepart_57756e8e6a60b_7ce03ff7f81db2a031273c
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
(in https://golang.org/pkg/net/http/#Client allows a Timeout to be specified.
If no timeout is specified, then there is no timeout, and connections may be left open forever.
TLS dialing seems like it already has default timeouts.
func (self *gcmPushService) multicast should be changed

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/uniqush/uniqush-push/issues/124
----==_mimepart_57756e8e6a60b_7ce03ff7f81db2a031273c
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
(in https://golang.org/pkg/net/http/#Client allows a Timeout to be specified.
If no timeout is specified, then there is no timeout, and connections may be left open forever.
TLS dialing seems like it already has default timeouts.
func (self *gcmPushService) multicast should be changed
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_57756e8e6a60b_7ce03ff7f81db2a031273c--


Update Blockly imports to make dist package smaller

Change-Id: I485ebe5518ef688d60059dbcee8826621713750e

After applying this change the dist/index.js file should be about an order of magnitude smaller.


It did not show up

Hey, the plugin seems to be working okay for me on Godot 4.3. Could you tell me what version you're on?


Support Workspace Trust

Hello :wave: I'm from the VS Code team.
Recently, we have been exploring a security feature we refer to as Workspace Trust. This feature is intended to centralize and unify a security conscious decision required by a variety of VS Code features. With workspace trust, the user will be able to declare whether or not they trust the folder that is opened in VS Code before these features are executed.
Why you should care
We want to make sure that those users have a delightful experience with workspace trust and that includes extension authors deciding how much of their extension is supported in an untrusted workspace. Custom editors are special in that if they cannot at least render in an untrusted state then they will be replaced by a lightweight message telling the user to enable trust. This means that users of your extension will not be able to see their editors and there may even be cases of data loss.

Workspace Trust experience
You can enable the feature with the following setting security.workspace.trust.enabled. Once enabled, you will see the following dialog when opening folders in VS Code.

This dialog is important for allowing the user to make a decision early and understand the impact of their decision. Once you understand the feature, you may want to customize when to display the dialog using the setting security.workspace.trust.startupPrompt.
You can follow the development of Workspace Trust and provide feedback in issue #106488.
Workspace trust API
First off, all of what I am about to say can be found in issue #120251. That issue will include discussion of the feature and any updates to the feature.
The Workspace Trust extension API is now in stable. This allowed us to release the first cut of our guide for onboarding your extension to Workspace Trust. The API is small, so here is a quick look.
You can declare your extension to provide complete, partial or no support in untrusted workspaces using the untrustedWorkspaces capability in package.json.
The following example declares that the extension is supported completely in untrusted workspaces. In this case, the extension is enabled in untrusted workspaces.
"capabilities": {
  "untrustedWorkspaces": {
    "supported": true
  }
}

The next example declares that the extension is not supported in untrusted workspaces. In this case, the extension is disabled in untrusted workspaces.
"capabilities": {
  "untrustedWorkspaces": {
    "supported": false
  }
}

The third option is to declared limited support. There are three tools provided to you when you select the limited option.
First, if you have a setting that can be configured in the workspace but requires the workspace to be trusted in order to apply the workspace value, then you can include the setting using restrictedConfigurations array property in untrustedWorkspaces object. Doing so, VS Code will ignore the workspace value of these restricted settings when your extension reads these settings values using the VS Code Workspace Configuration API.
The following example declares the settings that are restricted in untrusted workspaces.
"capabilities": {
  "untrustedWorkspaces": {
    "supported": "limited",
    "restrictedConfigurations": [
      "markdown.styles"
    ]
  }
}

Next, you can also check and listen if the current workspace is trusted or not programmatically using the following API:
export namespace workspace {
  /**
   * When true, the user has explicitly trusted the contents of the workspace.
   */
  export const isTrusted: boolean;
  /**
   * Event that fires when the current workspace has been trusted.
   */
  export const onDidGrantWorkspaceTrust: Event<void>;
}

Lastly, you can hide commands or views declaratively with the isWorkspaceTrusted context key in your when clauses.
A far more detailed guide on how to onboard which will be updated as we receive feedback can be found in issue #120251.
Rollout plan
We are planning on enabling this by default in the near future (most likely next release). To prepare for that day, we want to work with you to allow your editor to work seamlessly alongside the trusted workspace experience
Our Asks
The main features that should work for custom editors in an untrusted folder is rendering, viewing, and saving (if applicable). After reviewing your codebase, I believe that your extension doesn't rely on user's file contents beyond simple reading and therefore is safe to operate in untrusted workspaces. I recommend adopting the supported: true.
Please let me know if you have any question or would like to meet up via voice chat as I would be happy to assist you in getting your extension ready for workspace trust!

Yes, would be nice if we could have a voice chat. Please send me some details.
(I'm in UTC+2h)

I have sent a Microsoft Teams calendar invite to the email on your github account

OK, see you at 19.5.

Yes no worries, feel better

Is supported now.
"capabilities": {
  "untrustedWorkspaces": {
    "supported": true
  }
}


An example for ffi input/output aliasing

an example here to show how input/output are aliased.

Good suggestion! I've just opened a PR (https://github.com/jax-ml/jax/pull/25042) that adds such an example. I didn't add it to the tutorial, because we are using the examples/ffi directory in the JAX repo to demonstrate more advanced features for now. Please take a look at https://github.com/jax-ml/jax/pull/25042 (or, more precisely, this diff) to see if you have any more specific questions that aren't answered there.


Connection States

So I could probably start digging through code, but I figured I'd ask:
If my ConnectionStateListener gets sent a LOST state change, is that the equivalent of Zookeeper's SESSION_EXPIRED?
In other words, will I not get a LOST until I actually reconnect to the cluster (which is how SESSION_EXPIRED works) or will I get a LOST right away after the retry policy is exhausted (but perhaps before I reconnect to the cluster)?
I'm hoping it's the latter.  I ask because I'm trying to figure out at which point my locks have become garbage:  at SUSPENDED or at LOST.
(Ignoring ZK session timeouts vs retry policy lengths for the moment.)
Thanks, and apologies if this is documented somewhere,
John

If you get LOST, the retry policy has been exhausted. i.e. Curator has given up. It's not necessarily equivalent to SESSION_EXPIRED but that could be one of the causes. There are a variety of reasons you could get LOST.
SUSPENDED means there is a temporary loss to the server. i.e. the server you're connected to goes down or drops the connection. ZooKeeper/Curator will attempt to reconnect to another server in the ensemble and, if successful, you'll get RECONNECTED. If it fails, you'll get LOST.


[#3007] Set a SmartLifecycle phase lower than the ones written in the spring WebServer lifecycle ones.

This means that we "start" Axon before starting the web server and "stop" axon after stopping the web server.
#3007

I went with the simplest possible solution here, hard-coding a value with a descriptive comment.
I could rewrite it to dynamically inject the web server lifecyle if it's present on the classpath, and make the required "spring web" dependencies optional dependencies to the spring maven module.
However - it felt like that was quite a lot of plumbing for something that I would suspect will be rather stable (the phase value of the web server lifecycles).

Great point @smcvb. I updated it to have a public constant for its phase. Let me know what you think!


Add vim-help feature

New feature: vim-help is here!
Type ':h help' to get help of the help command of vim.

Looks good to me
ESLint says so too

Yay


Microsoft Defender for Business

[Thank you for the article! Please help to include whether Microsoft Defender for Business is eligible for this function or not. Our customers and partners are keen to know.]

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

ID: fb9a6dfb-2853-20fc-bd6c-2f636945b328
Version Independent ID: 60586381-2d76-32bc-8e44-342ee36ada1c
Content: Onboard Windows devices in Azure Virtual Desktop
Content Source: microsoft-365/security/defender-endpoint/onboard-windows-multi-session-device.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@hasuzuki0005 Thank you for your feedback. Currently, Microsoft Defender for Business is not eligible for this function. If you would like to know more about the roadmap, Please leave your feedback on our main feedback portal (https://feedbackportal.microsoft.com/) so that one of our dev/product engineers will be able to provide more details on whether this will be eligible in the future or not.
Hope this helps!
Thanks
Sri

@hasuzuki0005 Thank you very much for your kind feedback. Considering your valuable feedback, please log this issue as advised. Here we are limited to documentation fixes and improvements only. Concerning team will evaluate and take the appropriate action, as per their schedule. We proceed here to close it. Thanks again for taking out some time and sharing your feedback.

Sure, thank you for your response and guidance.
Thanks,
Hajime
From: Yogesh Kumar @.>
Sent: Wednesday, October 19, 2022 5:37 PM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Hajime Suzuki @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Microsoft Defender for Business (Issue #9950)
@hasuzuki0005https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhasuzuki0005&data=05|01|hasuzuki%40microsoft.com|4e4f6c7a240e48c3dde908dab1ad2841|72f988bf86f141af91ab2d7cd011db47|1|0|638017654549313020|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=IgHtTUc1t9RmiHFKKgd7lDikwhf19%2FP6PaUE4h6jkjE%3D&reserved=0 Thank you very much for your kind feedback. Considering your valuable feedback, please log this issue as advised. Here we are limited to documentation fixes and improvements only. Concerning team will evaluate and take the appropriate action, as per their schedule. We proceed here to close it. Thanks again for taking out some time and sharing your feedback.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fissues%2F9950%23issuecomment-1283637843&data=05|01|hasuzuki%40microsoft.com|4e4f6c7a240e48c3dde908dab1ad2841|72f988bf86f141af91ab2d7cd011db47|1|0|638017654549469259|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=9YumfkTpfu8f%2FMFlJdkWH8r3BMp%2FDfPkFJsWXsIWkHY%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXOB7TNK7PRXNF6X6QUHXFTWD6XMRANCNFSM6AAAAAAREHJYIE&data=05|01|hasuzuki%40microsoft.com|4e4f6c7a240e48c3dde908dab1ad2841|72f988bf86f141af91ab2d7cd011db47|1|0|638017654549469259|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Ee%2FC7deYdl1ijgrjDDQDGwAxLGuvJKoJmsXKbfJ2TX8%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Refactor of populateThemeDropdown()

Using async/await and try/catch.
Also added "option" for simplicity.

@omicreativedev hello! i`m sorry, accidentaly close this PR.
create new with discussed changes - https://github.com/omicreativedev/hacktoberfest2023/pull/58/


Added system diagram to ECDSA Readme

Added system diagram presenting how system components interact with each other.
The system diagram was generated by @michalinacienciala in #2967.
I copied the image to ecdsa so that we do not need to wait for #2927 to be merged to have this diagram incorporated into our documentation.

Please hold on with merging, some updates to the diagram are needed.


New empty tooltips

tooltips--allow-html
We have little tooltips for the CR/QA checkoff icons like No signoffs yet! and No QA required!.
Now the tooltips are showing up even when there's no content for them.
I am guessing a dependency from the latest dependabot pulls changed this.

Oops, I didn't realize this before, but the tooltips are supposed to also show the names of the reviewers!

@k0rvusk0r4x pointed this out to me


Folder First then Files

Is there any way to make sure that the folders are first in the output and files second?

@besteman Check out a similar package that I wrote that has this feature - https://github.com/yangshun/tree-node-cli


134 alias support

Pull Request Test Coverage Report for Build 452

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-2.2%) to 90.847%

Files with Coverage Reduction
New Missed Lines
%

build/src/validators/address.validator.js
5
53.33%

Totals

Change from base Build 448:
-2.2%

Covered Lines:
368

Relevant Lines:
410

💛  - Coveralls

@NemTechCN Thanks!


EconomicDispatch with OPFData

This PR updates the EconomicDispatch implementation:

Add reserve bounds + MRR to OPFData
Separate types for ED/EDR
No soft power balance or soft reserve requirement option
Remove export_ptdf

Todo:

[x] add a has_values check before grabbing pg in solve!
[x] extract ptdf_pf, not pf
[x] set constraint coefficients to zero for reserve requirement, power balance
[ ] if vector-formulations switches to load-wise pd before this is merged, update solve! to account

LGTM


How to add cookie in Selenium test

I need to add cookie value before loading an URL for some validation, how I can do in open test , we started using open test in our organization and we blocked at this step.
Didn't find any steps to add, when I use document.cookie function in script its failing.

OpenTest already has the keywords to add and delete a cookie, but they are not yet documented (we'll document them soon, along with other recent additions). In the meantime, here's the basic syntax to add/delete cookies:
- description: Add a cookie named MyCookie
  action: org.getopentest.selenium.AddCookie
  args:
    name: MyCookie
    value: my cookie value

- description: Delete cookie named MyCookie
  action: org.getopentest.selenium.DeleteCookie
  args:
    name: MyCookie

The document.cookie syntax that you mentioned can only be run by the web browser and not by the OpenTest actor. To do that, you need to use the ExecuteScript keyword. You don't need this for working with cookies (since we already have the two dedicated keywords that I just mentioned), but, for the future, this is how you can run scripts in the browser:
- description: Run a browser script
  action: org.getopentest.selenium.ExecuteScript
  args:
    script: |
      document.cookie = "MyCookie=my cookie value";

The AddCookie and DeleteCookie keywords are now properly documented.
Closes #44


Handle key not found with END

When a key is not found, the server should only return END.

Fixed, see PR #55

Wrongly closed.
@zhangwei1984 @wenhuizhang are fixing the issue.

It is updated, and could return "END" now, thanks, pls close the issue

Fixed in 312de3a


Attention-based Spatial Alignment

Excuse me,I want to ask:
What is the two input features of Attention-based Spatial Alignment Net? Do the input two features come from the two types of  augment respectively?(Standard aug and simclr augment)
But in the program,I find that the two input features are same.(Copy feature_a as fearure_b)
Thanks!

Hi @yubin2020
The implementation is done to be as general as possible, so the module can take any two tensors A and B, and aligns each example in A with each example in B.
For example, as you said, A can be origianal batch and B the augmented batch, but you can also pass [A & B] and [A & B] for both to contrast a larger number of examples (while removing self contrasting in the loss), and this works a bit better.
So in our case, we use all example and simply pass the same tensor of features (current batch).
Hope this helps.

Thank you very much for your kind attention personal response！
As you said，when we use A (origianal batch ) and B (augmented batch) as the two inputs, we can get two different similarity matrices through the Attention-based Spatial Alignment Net.But when we pass [A & B] and [A & B] ,we can end up with two identical similarity matrices to calculate loss (because of the two same inputs).So if we use [A & B] and [A & B] as input, we only need to calculate the similarity once (equivalent to removing the branch of calculating the second similarity).
Please,do I understand this correctly?
------------------ 原始邮件 ------------------
发件人:                                                                                "yassouali/SCL"                                                                                @.>;
发送时间: 2021年11月20日(星期六) 凌晨1:35
@.>;
<EMAIL_ADDRESS>主题: Re: [yassouali/SCL] Attention-based Spatial Alignment (Issue #2)
Hi @yubin2020
The implementation is done to be as general as possible, so the module can take any two tensors A and B, and aligns each example in A with each example in B.
For example, as you said, A can be origianal batch and B the augmented batch, but you can also pass [A & B] and [A & B] for both to contrast a larger number of examples (while removing self contrasting in the loss), and this works a bit better.
So in our case, we use all example and simply pass the same tensor of features (current batch).
Hope this helps.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yes @yubin2020
That is correct, if you want to make the computation more efficient, you can only compute it once in our case

Thanks for your help!
------------------ 原始邮件 ------------------
发件人:                                                                                "yassouali/SCL"                                                                                @.>;
发送时间: 2021年11月21日(星期天) 凌晨3:25
@.>;
<EMAIL_ADDRESS>主题: Re: [yassouali/SCL] Attention-based Spatial Alignment (Issue #2)
Yes @yubin2020
That is correct, if you want to make the computation more efficient, you can only compute it once in our case
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Excuse me, I also want to ask the program(the simclr loss). If I use A(origianal batch) and B(augmented batch) as input, where else do I still need to change ? (Known:feature_a is A, feature_b is B, the [mask = mask.repeat(2, 2)] is not needed )
Thanks!
------------------ 原始邮件 ------------------
发件人:                                                                                "yassouali/SCL"                                                                                @.>;
发送时间: 2021年11月20日(星期六) 凌晨1:35
@.>;
<EMAIL_ADDRESS>主题: Re: [yassouali/SCL] Attention-based Spatial Alignment (Issue #2)
Hi @yubin2020
The implementation is done to be as general as possible, so the module can take any two tensors A and B, and aligns each example in A with each example in B.
For example, as you said, A can be origianal batch and B the augmented batch, but you can also pass [A & B] and [A & B] for both to contrast a larger number of examples (while removing self contrasting in the loss), and this works a bit better.
So in our case, we use all example and simply pass the same tensor of features (current batch).
Hope this helps.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

in your case, no need to remove self contrastive (the diagonals of the similarity matrix), since all the two features are different
exact line: https://github.com/yassouali/SCL/blob/0a45738435d27781e26ccf621a23177617c2b084/losses.py#L80

I can understand what you mean.In this case,the '2N' of the loss will change  to 'N'.
But I don't  understand how to modify the code. Can you explain it a little？
Thanks!
------------------ 原始邮件 ------------------
发件人:                                                                                "yassouali/SCL"                                                                                @.>;
发送时间: 2021年11月25日(星期四) 凌晨0:49
@.>;
<EMAIL_ADDRESS>主题: Re: [yassouali/SCL] Attention-based Spatial Alignment (Issue #2)
in your case, no need to remove self contrastive (the diagonals of the similarity matrix), since all the two features are different
exact line: https://github.com/yassouali/SCL/blob/0a45738435d27781e26ccf621a23177617c2b084/losses.py#L80
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I just updated the loss, now it should be working by simply passing original features as features_a and augmented features as features_b

Thanks for your help!I mainly study few-shot action recognition,I want to learn from your work！
Hope to have more opportunities to communicate with you in the future！
Good luck！
------------------ 原始邮件 ------------------
发件人:                                                                                "yassouali/SCL"                                                                                @.>;
发送时间: 2021年11月25日(星期四) 凌晨1:50
@.>;
<EMAIL_ADDRESS>主题: Re: [yassouali/SCL] Attention-based Spatial Alignment (Issue #2)
I just updated the loss, now it should be working by simply passing original features as features_a and augmented features as features_b
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Update k8s user guide to use deployments

Which issue does this PR close?
Closes #473.
What changes are included in this PR?

Rename port to bind-port since the configure_me create was trying to parse an env var that was being autopopulated by Kubernetes
Change the user guide for k8s

cc @andygrove

Codecov Report

Merging #474 (56aeaea) into master (1601112) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master     #474   +/-   ##
=======================================
  Coverage   75.84%   75.84%
=======================================
  Files         153      153
  Lines       25872    25872
=======================================
  Hits        19622    19622
  Misses       6250     6250

Impacted Files
Coverage Δ

ballista/rust/executor/src/main.rs
0.00% <0.00%> (ø)

ballista/rust/scheduler/src/main.rs
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Testbed: allow external modification of physics world

To continue the discussion from https://discourse.nphysics.org/t/testbed-and-specs-rs-how-to-influence-physics-world/242.
My use case it to use specs.rs with nphysics testbed, allowing modification from a specs::System.
I might make pull requests to explore these options:

lower the ownership requirement of nphysics::world::World within testBed (a reference or refcell should be sufficient)
separate clearly graphics rendering and physics update, so each is optional and can have their own implementation.

Fixed by #133