Update communication model

Remove unneeded fields from de/serialising
Append the trailing slash to the advertised URL
Only decode the main payload, since the recipient list will always be empty

Codecov Report

Merging #482 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #482      +/-   ##
============================================
+ Coverage     99.65%   99.67%   +0.02%
- Complexity     1169     1248      +79
============================================
  Files           189      192       +3
  Lines          3766     4011     +245
  Branches        194      229      +35
============================================
+ Hits           3753     3998     +245
  Partials         13       13

Impacted Files
Coverage Δ
Complexity Δ

...n/java/com/quorum/tessera/enclave/EnclaveImpl.java
100% <100%> (ø)
16 <0> (ø)
:arrow_down:

...va/com/quorum/tessera/enclave/EnclaveMediator.java
100% <100%> (ø)
21 <1> (ø)
:arrow_down:

.../java/com/quorum/tessera/node/PartyInfoParser.java
100% <100%> (ø)
8 <1> (ø)
:arrow_down:

.../com/quorum/tessera/node/PartyInfoServiceImpl.java
97.77% <100%> (ø)
12 <0> (ø)
:arrow_down:

...va/com/quorum/tessera/api/TransactionResource.java
100% <100%> (ø)
11 <0> (ø)
:arrow_down:

...va/com/quorum/tessera/config/cli/OverrideUtil.java
100% <0%> (ø)
87% <0%> (+28%)
:arrow_up:

...va/com/quorum/tessera/config/KeyConfiguration.java
100% <0%> (ø)
9% <0%> (+4%)
:arrow_up:

...ssera/config/adapters/KeyConfigurationAdapter.java
100% <0%> (ø)
18% <0%> (+11%)
:arrow_up:

...a/com/quorum/tessera/config/JaxbConfigFactory.java
100% <0%> (ø)
15% <0%> (+3%)
:arrow_up:

.../quorum/tessera/config/builder/KeyDataBuilder.java
100% <0%> (ø)
13% <0%> (+1%)
:arrow_up:

... and 5 more

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 771491a...38b5177. Read the comment docs.


Try to fix a race condition in the single-root-UI test

Try to fix a race condition in the single-root-UI test

Ugh.  Now there's a problem with the configure-and-build test too. 😢


Toughen ruff linting

Changes
flake8-commas (COM)

https://docs.astral.sh/ruff/rules/#flake8-commas-com
https://pypi.org/project/flake8-commas/

flake8-builtins (A)

https://docs.astral.sh/ruff/rules/#flake8-builtins-a
https://pypi.org/project/flake8-builtins/

flake8-errmsg (EM)

https://pypi.org/project/flake8-errmsg/
https://pypi.org/project/flake8-errmsg/

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

Comparison is base (0061417) 58.93% compared to head (d556e28) 58.93%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #31   +/-   ##
=======================================
  Coverage   58.93%   58.93%
=======================================
  Files          10       10
  Lines         660      660
=======================================
  Hits          389      389
  Misses        271      271

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


Feature Request: Dark Mode

I'd like to see a 'dark mode' feature on TIL. You flip a toggle, and your colors change to dark mode. The browser remembers your choice. Here's an idea of what it might look like.

We can also use a media query to detect if the user turned on darkmode in their OS
@media (prefers-color-scheme: dark) {

}

https://css-tricks.com/dark-modes-with-css/

Closing; there are several tools that can handle this without any code changes. I'm currently using Dark Reader:
https://addons.mozilla.org/en-US/firefox/addon/darkreader/


fix: Deploy L1 rollup contract using salt if provided

Fixes a bad merge that disabled the usage of deployment salt for rollup contract.

Currently reverting with:
  aztec:cli [ERROR] Error in command execution +5ms
  aztec:cli [ERROR] TransactionExecutionError: Execution reverted with reason: custom error 118cdaa7:000000000000000000000000976ea74026e726554db657fa54763abd0c3a0aa9.

Request Arguments:
  from:  0x976EA74026E726554dB657fA54763abd0C3a0aa9
  to:    0xccf3812ff8bca31d4f848557550dfbbd0784a901
  data:  0x6133f985000000000000000000000000931a2813aa3d91a4656bf5ea024e5a9e3687935f00000000000000000000000029ed3be73e158345082b508e3b26abb85264957a16a83e3395bc921a2441db55dce24f0e0932636901a2e676fa68b9b2b9a644c1

Benchmark results
Metrics with a significant change:

avm_simulation_time_ms (Token:mint_public): 69.7 (+57%)
avm_simulation_time_ms (Token:assert_minter_and_mint): 39.2 (-42%)
avm_simulation_time_ms (Token:transfer_public): 20.1 (-34%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,761
1,556 (+1%)
711 (+1%)
768 (+1%)
767

proof_construction_time_sha256_30_ms
11,856 (-1%)
3,195
1,412 (-15%)
1,439 (-9%)
1,474 (-4%)

proof_construction_time_sha256_100_ms
45,469 (+1%)
12,306 (+1%)
6,717 (+1%)
5,983
5,402 (-4%)

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
59.0 (+2%)
88.0 (+1%)

proof_construction_time_poseidon_hash_30_ms
1,530
421
203 (+1%)
232 (+2%)
270 (+2%)

proof_construction_time_poseidon_hash_100_ms
5,650 (+1%)
1,513
672
725 (-2%)
750

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
4,324
7,844
14,852

l1_rollup_calldata_gas
49,732
92,384
177,644

l1_rollup_execution_gas
1,383,226
2,130,846
3,958,145

l2_block_processing_time_in_ms
250 (-3%)
447 (-2%)
814 (-4%)

l2_block_building_time_in_ms
8,932 (-1%)
17,490
34,825 (-1%)

l2_block_rollup_simulation_time_in_ms
8,931 (-1%)
17,490
34,825 (-1%)

l2_block_public_tx_process_time_in_ms
7,520 (-1%)
15,984
33,264 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
3,007 (+3%)
3,862 (-3%)

node_database_size_in_bytes
12,611,664
16,728,144

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Circuit
simulation_time_in_ms
witness_generation_time_in_ms
input_size_in_bytes
output_size_in_bytes
proving_time_in_ms

private-kernel-init
84.0
399 (-1%)
21,502
44,858
N/A

private-kernel-inner
157 (-1%)
713
72,180
45,005
N/A

private-kernel-reset-tiny
470 (-1%)
874
65,502
44,844
N/A

private-kernel-tail
199
161 (-1%)
50,606
52,256
N/A

base-parity
5.58
N/A
160
96.0
N/A

root-parity
33.5
N/A
69,084
96.0
N/A

base-rollup
2,745 (-1%)
N/A
187,817
664
N/A

root-rollup
38.7 (-1%)
N/A
54,525
716
N/A

public-kernel-setup
83.2 (-2%)
N/A
103,760
71,222
N/A

public-kernel-app-logic
95.5
N/A
103,599
71,222
N/A

public-kernel-tail
553
N/A
409,190
16,414
N/A

private-kernel-reset-small
461 (-1%)
N/A
66,085
45,629
N/A

private-kernel-tail-to-public
984 (-1%)
650
473,529
1,697
N/A

public-kernel-teardown
82.6
N/A
104,005
71,222
N/A

merge-rollup
19.1
N/A
35,742
664
N/A

undefined
N/A
N/A
N/A
N/A
64,336 (-2%)

Stats on running time collected for app circuits

Function
input_size_in_bytes
output_size_in_bytes
witness_generation_time_in_ms

ContractClassRegisterer:register
1,344
11,731
344 (+1%)

ContractInstanceDeployer:deploy
1,408
11,731
18.3 (-1%)

MultiCallEntrypoint:entrypoint
1,920
11,731
423

FeeJuice:deploy
1,376
11,731
391

SchnorrAccount:constructor
1,312
11,731
106

SchnorrAccount:entrypoint
2,304
11,731
432

Token:privately_mint_private_note
1,280
11,731
140 (-3%)

FPC:fee_entrypoint_public
1,344
11,731
31.1 (+2%)

Token:transfer
1,312
11,731
270 (-2%)

Benchmarking:create_note
1,344
11,731
103

SchnorrAccount:verify_private_authwit
1,280
11,731
27.3

Token:unshield
1,376
11,731
557

FPC:fee_entrypoint_private
1,376
11,731
758

AVM Simulation
Time to simulate various public functions in the AVM.

Function
time_ms
bytecode_size_in_bytes

FeeJuice:_increase_public_balance
52.3 (-5%)
7,739

FeeJuice:set_portal
9.57 (-14%)
2,354

Token:constructor
78.6 (-2%)
26,525

FPC:constructor
52.1 (+1%)
18,383

FeeJuice:mint_public
39.1 (+3%)
5,877

Token:mint_public
:warning: 69.7 (+57%)
10,917

Token:assert_minter_and_mint
:warning: 39.2 (-42%)
7,512

AuthRegistry:set_authorized
36.7 (-20%)
4,391

FPC:prepare_fee
233 (-10%)
7,712

Token:transfer_public
:warning: 20.1 (-34%)
39,946

FPC:pay_refund
53.0 (-10%)
10,811

Benchmarking:increment_balance
940 (+1%)
6,929

Token:_increase_public_balance
38.2 (-16%)
8,433

FPC:pay_refund_with_shielded_rebate
63.7 (-4%)
11,360

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.156 (-2%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
2.18 (-2%)
3.95
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.114 (-2%)
0.111
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
11.6 (-1%)
17.8 (-1%)
31.4 (+1%)
59.9 (-2%)
114

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.111 (-1%)
0.103 (-1%)
0.102 (+1%)
0.103 (-1%)
0.102

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
14.5 (+1%)
25.9 (-1%)
44.4 (+1%)
83.5 (-1%)
163 (+1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.110 (+1%)
0.104
0.107 (+1%)
0.103 (-1%)
0.102

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
16.5 (-1%)
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
132
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.106 (-1%)
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
64,779
668,997

Transaction size based on fee payment method
| Metric |  |
| - |  |


@orta => Temp disable placeholder images at right size in effort to debug crash.

This is ugly, but will get reverted as soon as the 2.0.1 bugfix release
has been released. It should at least give us some insight into whether
or not this code is in any way related to, as of yet, unreproducible
issue https://github.com/artsy/eigen/issues/526.

This own't be the only place that the aspect ratio is getting set I bet

The aspect ratio gets set from setAspectRatioConstraintWithImage: which is only called from this classes’ setImage:.
~/C/A/eigen [temporarily-disable-correctly-sized-placeholder] » ack -i AspectRatioConstraintWithImage Artsy
Artsy/Classes/View Controllers/ARArtworkPreviewImageView.m
108:        [self setAspectRatioConstraintWithImage:image];
113:- (void)setAspectRatioConstraintWithImage:(UIImage *)image

Bump.

:+1:


Fix conversation with global middleware

At first glance this may seem unnecessary given the last pr, but explained with an example it is simpler:
I would like for example to have a global middleware that takes from the database the user by telegram_id and puts it in the context, and if it is not there in the database, it asks him a question that he has to answer (so opening a mini conversation with nextStep(...)) and then saves it to database.
This is not possible anymore, since now all global middleware is always applied to all conversation handlers, and basically you enter the loop where the bot asks you always the same question, because the middleware is called before the conversation handler. You can avoid this by not using global middleware, but that means having to apply it to every listener by hand (with ->middleware(...)), which makes the code redundant and defeats the benefit of global middleware.
In this pr is what I came up with to make middlewares optional for certain conversation flows.
It also add some _ in the cache keys because now are kinda hard to read when debugging

Ok, very edge case 😅 but can happen. I made ttl configurable

Ok, very edge case 😅 but can happen. I made ttl configurable


Update pip using pip after installing.

The stock pip seems to get corrupted during a fresh vagrant up at some
point in the chef run unless pip is updated first.

This is very similar to what @dbishop ran into - https://github.com/swiftstack/vagrant-swift-all-in-one/pull/16/files#diff-a6bc8a65517fa0a7aadef2dfe94102f6R19
the server-per-port change hasn't merged upstream yet - so i'm keen to get in a fix for this ahead of that.
Did you not have to also uninstall the python-pip system package?

It works without uninstalling the system package, but that is probably confusing. I think I like removing the system package completely and using easy_install to get pip like @dbishop did.

Yeah that patch is great, but depends on an upstream change that's got caught up in some low-level ring muk so we have to untangle that ball of mud.  I'm testing this change now - if it works I'll merge and when we get the other from @dbishop we'll just be all that much better off!

yeah, this works for me - only thing with new pip is you have to sudo pip install pyopenssl --upgrade and update /etc/sudoers with:
Defaults always_set_home

... to get all the new pip versions warnings to shut up

so... i sort of take it back - pip 7.0 messes up the pyeclib install pretty gnarly.
The fix is to enabled the trusty-backports repo and install libjerasure-dev and all it's dependencies
... so I'll probably just have to do all that then

Oh wow, dependency hell. Thanks for digging into it.
On Jun 17, 2015 4:02 PM, "clayg"<EMAIL_ADDRESS>wrote:

so... i sort of take it back - pip 7.0 messes up the pyeclib install
pretty gnarly.
The fix is to enabled the trusty-backports repo and install
libjerasure-dev and all it's dependencies
... so I'll probably just have to do all that then
—
Reply to this email directly or view it on GitHub
https://github.com/swiftstack/vagrant-swift-all-in-one/pull/18#issuecomment-112948977
.


bump oceananigans compat

Purpose
<!--- One sentence to describe the purpose of this PR, refer to any linked issues:

bump oceananigans compat

@glwagner

yeah looks like the example fails for reasons beyond my understanding.
Feel free to take over the PR, I've hit allow edits by maintainers.

Was the example OK before the PR?

The failure clearly has nothing to do with this PR so it was probably broken already

Thanks @wsmoses


Add support for command JSON.ARRINDEX

Add support for the JSON.ARRINDEX command in DiceDB similar to the JSON.ARRINDEX command in Redis. Please refer to the following commit in Redis to understand the implementation specifics - source.
Write unit and integration tests for the command referring to the tests written in the Redis codebase 7.2.5. For integration tests, you can refer to the tests folder. Note: they have used TCL for the test suite, and we need to port that to our way of writing integration tests using the relevant helper methods. Please refer to our tests directory.
For the command, benchmark the code and measure the time taken and memory allocs using benchmem and try to keep them to the bare minimum.

please assign it to me. thanks.

@jujiale I believe you already have a few issues assigned (https://github.com/DiceDB/dice/issues/484, https://github.com/DiceDB/dice/issues/487, https://github.com/DiceDB/dice/issues/489, https://github.com/DiceDB/dice/issues/490, https://github.com/DiceDB/dice/issues/503). Once you wrap those up, you’re welcome to pick this one. Want to make sure everyone gets a chance to contribute :) Thanks so much for your eagerness and enthusiasm.

@lucifercr07 would like to work on this issue

@Rits1272 assigned, thanks for picking this up.

@jujiale I believe you already have a few issues assigned (#484, #487, #489, #490, #503). Once you wrap those up, you’re welcome to pick this one. Want to make sure everyone gets a chance to contribute :) Thanks so much for your eagerness and enthusiasm.

ok, let's build dice stronger together

Hi @lucifercr07
Is this still being worked upon ? Otherwise I'll be happy to pick this up.
Thanks

Hey, still working upon this issue. Will drop a PR by today itself

Hello @Rits1272,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

I have opened PR for this already. There are some reviews/comments on the PR. I will resolve it in a day or two

Hello @Rits1272,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

This issue is available since there has been no activity on the associated PR (#765) for a while. Anyone interested in picking this up can refer to the existing PR and its review comments.

Hi @JyotinderSingh - would like to take this on next! Please assign to me whenever possible

Hi @JyotinderSingh - would like to take this on next! Please assign to me whenever possible

Assigned

Update 10/24 - had some work commitments, sorry for the delay. I have started working on the implementation a couple of days back, referred the prior PR and suggestions in there. Will try to link a draft / ready PR by EOW.
Sorry for the delay.
cc @JyotinderSingh

Hi @sashpawar11 , How are you? I am excited to know about your progress so far.

Hi @apoorvyadav1111 @JyotinderSingh - I'm not able to work on this at the moment due to work priorities. Sorry for the inconvenience and delay caused - please assign out to someone else.
Thankyou

Hey @apoorvyadav1111  please assign to me, will work on it!


Winnower Indexing

Starting on August 16th my server began encountering this error:
[Errno 1] _ssl.c:510: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
I cannot reproduce this error locally, and the version of requests on my local machine is identical to the version on the server (2.9.1).
I'll send out some emails, but the error isn't a big deal as I've been wondering if I should still be indexing The Winnower since they have now partnered with Authorea and almost everything that gets indexed are just Reddit AMAs.

Couldn't figure out why the issue arose on the 16th, but adding all of this to my virtualenv seemed to solve the problem: pip install urllib3[secure] pyopenssl ndg-httpsclient pyasn1


Include Reference and Exception Peaks

Hi there,
thx for this nice library. By default the thermo RawFileReader hides exception and reference peaks from FTMS capable instruments. According to the RawFileReader documentation these can be activated via:
// Enable the include reference and exception data
rawFile.IncludeReferenceAndExceptionData = true;

A github search did not reveal this line in the current code base of ThermoRawFileParser so I assume the written files do not contain the reference and exception peaks.
Is it possible to add a flag which controls the inclusion of reference and exception peaks to ThermoRawFileParser? In our case one of the reference peaks coincides with a m/z of interest.

Hi @ozgurdemir ,
yes, you are right - reference and exception peaks are not included.
It can be done, though.

@caetera thx. the question is should they be included by default. so just setting the
rawFile.IncludeReferenceAndExceptionData = true;
of should the user have the posibility to set it via a command line flag. The 2nd solution makes usage a bit more complicated and the implementation, too.

So since I need this if it's ok I'd open up a pull request setting the flag to true and add a comment in the readme that by default reference and exception peaks are included.

I think, it is better to keep the default behavior as it is now. Your case is rather an exception, IMO, thus, I would prefer the second solution.
If you can implement it and make a pull request I will be happy to review/merge it, otherwise, I can implement it later.

I agree that it is the better solution. However, I'm not familiar with the code base. So setting up the dev env and making the changes which are probably rather small will take me some time. What would be your timeline @caetera to implement this?

837995a implements the change;
new console key -x|--includeExceptionData adds exception and reference data.
Please let me know if it works for you.
You can use semi-official docker container if necessary https://hub.docker.com/r/caetera/thermorawfileparser/

@caetera wow that was quick. thx a lot for the implementation. really appreciated. I quickly tried the docker container and it seems to work.

I'm gonna close this issue as it has been fixed.

Great. I will include this update in the next release.

@caetera any clue when the next release will be?

@ozgurdemir It might take some time, let's say a week or two. There might be some minor changes in other parts of the tool.


Add Support for Maintenance Mode

What do you think about adding a maintenance mode/switch into Gardener in which we don't allow any creation/deletion of shoots?
Why?
To prevent inconstancy when we do a controlled restore of a cluster we currently might run into a situation where our backup (even the incremental one) might miss objects which have been created/deleted. In addition any infrastructure related jobs (creation or reconcile) should also be put on hold to prevent inconsistency.

Not exactly sure about the use-case, but wouldn't a kubectl -n garden scale deploy/gardener-controller-manager --replicas=0 suffice to achieve the same?

Well that will work for us, however is combined with a downtime experience for the user. I was thinking about something were we also tell the user in the dashboard via a notification or something - and scaling down the controller in the background.

OK, but how do you envision this? Is that really something that needs to be build into Gardener? Can you elaborate on how that could be implemented?

Ok, I guess we can close this one for now since there is no high prio need for that.


Not working with UTF-8

I tried to convert a JSON string to Base64 with this package, depend on the README, but it's simply return an [object ArrayBuffer] and I can't get the value from the object as a string.
Here is the code which I have written.
var text = data.profile; // It is a JSON string.
var bytes = utf8.encode(text);
var encoded = base64.encode(bytes);
_this.changeURL(_this.domain+"user/fb_login_callback?userNode="+encoded);

This doesn’t look like a bug in this library.
If you want help, please show your full code example.


Revert "Update README.md"

Reverts siaimes/pai#3

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 33.686%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1438

Relevant Lines:
3458

💛  - Coveralls


Sanitize doesn't adequately protect HTML

This has the makings of a great sanitization library but right now it appears to have some vulnerabilities, based on a quick read-through of the clear and well-written code.
https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.md
To quote the first cheatsheet: Even if you use an HTML entity encoding method everywhere, you are still most likely vulnerable to XSS. You MUST use the escape syntax for the part of the HTML document you're putting untrusted data into.
It might be useful to develop a test suite based on this:
https://www.owasp.org/index.php/XSS_Filter_Evasion_Cheat_Sheet
For example, escaping only <> isn't enough. OWASP used to have a list (as follows), but now even this isn't sufficient.
&  -> &
< -> <
> -> >
" -> "
' -> '
/ -> /
\n ->  <br>

Also have a look at how https://github.com/microcosm-cc/bluemonday does it.
This is another OWASP cheat sheet that might be valuable:
https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Input_Validation_Cheat_Sheet.md

Thanks. I will have a look at the links. If you do want to propose specific changes it's fine to discuss them here.


AttributeError: 'AsyncHTMLSession' object has no attribute 'run'

Python 3.6.0, windows 7x64
pip install requests-html
...
...
Succesfully installed ..., requests-html-0.9.0

missing __version__ parameter in file

>>> from requests_html import AsyncHTMLSession
>>> asession = AsyncHTMLSession()

>>> async def get_pythonorg():
...    r = await asession.get('https://python.org/')

>>> async def get_reddit():
...    r = await asession.get('https://reddit.com/')

>>> async def get_google():
...    r = await asession.get('https://google.com/')

>>> result = asession.run(get_pythonorg, get_reddit, get_google)

AttributeError: 'AsyncHTMLSession' object has no attribute 'run'

See issue #230. The wrong version of the library is on PyPI (but it has the same version number). The fix while we wait for the correct version to make it to PyPI is to download requests_html.py from this repository and replace the one installed on your machine with it. To find the location of the file on your machine :
>>> import requests_html
>>> requests_html.__file__
"Path\to\file.py"

AsyncHTMLSession.run is now available on v0.10.0. Sorry, it was in the README but there was not a release yet.


CR padded GSM7BitPackedCharset version

I want to use this library in the jSMPP library. The GSM7BitPackedCharset does not use CR padding. Are there plans to add a charset which implements this ? Or should I make a PR ?

Hi, @pmoerenhout
PRs are welcome! I think it will be faster to reach result.


Decide on data source interface for components

Properties:

Data source
Data scheme
Item renderer

SelectionList should be our model. At least at the moment. See https://github.com/wix/stylable-components/blob/master/specs/selectionlist.md

@danielstro If the previous comment solves the problem, you can close the issue, I guess.


Endpoint for Annual Debt Service Coverage Ratio (ADSCR)

What bug or feature you wants to report.
Annual Debt Service Coverage Ratio (ADSCR) is a financial metric used to assess the ability of a company or individual to meet their debt obligations. It measures the cash flow available to cover annual debt payments, including both principal and interest
ADSCR = Net Operating Income / Annual Debt Service

Ok will be merging this once approved! :)


Categorizing - Distance does not show route and button loads infinitely on confirmation page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.22-7
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:
Precondition:

User is logged in with Expensifail account

Go to staging.new.expensify.com
Go to self DM
Go to + > Track expense > Distance
Submit a track distance expense
Click Categorize it from the actionable whisper
Select a workspace and category
On confirmation page, click Distance
Note that the map does not display the route with infinite loading button
Dismiss the confirmation page
Click on the expense preview
Note that Distance and Rate fields show pending

Expected Result:
In Step 8, the map will show the correct route and the button will not load infinitely
In Step 11, Distance and Rate fields will show the correct data
Actual Result:
In Step 8, the map does not show the correct route (no green route line) and the button loads infinitely
In Step 11, Distance and Rate fields show "Pending"
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/b635b7d0-52c2-4dcd-a509-d757f8d27b57
View all open jobs on GitHub

@johncschuster  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Proposal
Please re-state the problem that we are trying to solve in this issue.
Distance map doesn't show the green route when categorizing a track expense and when opening the distance edit page, the button loads infinitely.
What is the root cause of that problem?
When the track expense is completed, the routes object whcih contains the green line route is cleared.
https://github.com/Expensify/App/blob/685bb4c7bbaa2ef332896de5cace193edb9c6a51/src/libs/actions/IOU.ts#L1509-L1515
So, when we try to categorize it and it opens the confirmation page, we don't see the green route line. The route will be re-fetched if we open the distance page.
https://github.com/Expensify/App/blob/685bb4c7bbaa2ef332896de5cace193edb9c6a51/src/pages/iou/request/step/IOURequestStepDistance.tsx#L162-L167
But in our case, it loads infinitely. It's because, when we call the GetRoute request, it saves the route to transactions_xxx, meanwhile, we use transactionsDraft_xxx when categorizing the expense.
https://github.com/Expensify/App/blob/685bb4c7bbaa2ef332896de5cace193edb9c6a51/src/pages/iou/request/step/withFullTransactionOrNotFound.tsx#L76-L78
So, shouldFetchRoute stays true because the route is still empty,
https://github.com/Expensify/App/blob/685bb4c7bbaa2ef332896de5cace193edb9c6a51/src/pages/iou/request/step/IOURequestStepDistance.tsx#L98
https://github.com/Expensify/App/blob/685bb4c7bbaa2ef332896de5cace193edb9c6a51/src/pages/iou/request/step/IOURequestStepDistance.tsx#L103
and the loading shows indefinitely.
https://github.com/Expensify/App/blob/685bb4c7bbaa2ef332896de5cace193edb9c6a51/src/pages/iou/request/step/IOURequestStepDistance.tsx#L513
Also, there is another issue with STRICT MODE. The code below that saves and restores backup is triggered twice because of the strict mode. The problem is, the restore logic is called late.
create backup
create backup
restore backup to draft

https://github.com/Expensify/App/blob/685bb4c7bbaa2ef332896de5cace193edb9c6a51/src/pages/iou/request/step/IOURequestStepDistance.tsx#L187-L205
It's because the restore needs to connect to the onyx first which delays the logic,
https://github.com/Expensify/App/blob/685bb4c7bbaa2ef332896de5cace193edb9c6a51/src/libs/actions/TransactionEdit.ts#L29-L39
and the restore logic will remove the restore the backup to the draft and remove the backup. Once we close the page, the restore logic is called again, but this time, the backup is already empty, so we restore an empty data (null) to the transaction draft which clears it.
What changes do you think we should make in order to solve the problem?

To fix the infinite loading, we need to call GetRouteForDraft when categorizing.
TransactionAction.getRoute(transaction.transactionID, validatedWaypoints, action === CONST.IOU.ACTION.CREATE || IOUUtils.isMovingTransactionFromTrackExpense(action));

The last param tells whether to use draft or not. There are many places where we need to update from action === CONST.IOU.ACTION.CREATE to action === CONST.IOU.ACTION.CREATE || IOUUtils.isMovingTransactionFromTrackExpense(action)) like in waypoint page so we can update the waypoint while categorizing too.
https://github.com/Expensify/App/blob/685bb4c7bbaa2ef332896de5cace193edb9c6a51/src/pages/iou/request/step/IOURequestStepWaypoint.tsx#L158
To fix the missing route issue, we need to fetch the route in confirm page too following the similar logic we have in distance page. To keep it clean, we can make it a hook.
https://github.com/Expensify/App/blob/685bb4c7bbaa2ef332896de5cace193edb9c6a51/src/pages/iou/request/step/IOURequestStepDistance.tsx#L162-L167
useFetchRoute.ts
export default function (transaction, waypoints, action) {
    const {isOffline} = useNetwork();
    const hasRouteError = !!transaction?.errorFields?.route;
    const hasRoute = TransactionUtils.hasRoute(transaction);
    const isRouteAbsentWithoutErrors = !hasRoute && !hasRouteError;
    const isLoadingRoute = transaction?.comment?.isLoading ?? false;
    const validatedWaypoints = TransactionUtils.getValidWaypoints(waypoints);
    const previousValidatedWaypoints = usePrevious(validatedWaypoints);
    const haveValidatedWaypointsChanged = !isEqual(previousValidatedWaypoints, validatedWaypoints);
    const shouldFetchRoute = (isRouteAbsentWithoutErrors || haveValidatedWaypointsChanged) && !isLoadingRoute && Object.keys(validatedWaypoints).length > 1;

    useEffect(() => {
        if (isOffline || !shouldFetchRoute) {
            return;
        }
        TransactionAction.getRoute(transaction.transactionID, validatedWaypoints, action === CONST.IOU.ACTION.CREATE || IOUUtils.isMovingTransactionFromTrackExpense(action));
    }, [shouldFetchRoute, transaction.transactionID, validatedWaypoints, isOffline, action]);

    return {shouldFetchRoute, validatedWaypoints};
}

Then, use it in distance and confirm page. For example, in confirm page,
useFetchRoute(transaction, transaction.comment.waypoints, action);

To solve the strict mode issue, we can cancel the restore if there is a create backup request.
let connectionID;

function createBackupTransaction(transaction: OnyxEntry<Transaction>) {
    ...;
    Onyx.disconnect(connectionID);
    // Use set so that it will always fully overwrite any backup transaction that could have existed before
    Onyx.set(`${ONYXKEYS.COLLECTION.TRANSACTION_BACKUP}${transaction.transactionID}`, newTransaction);
}

function restoreOriginalTransactionFromBackup(transactionID: string, isDraft: boolean) {
    connectionID = Onyx.connect({...});
}

This will behaves as if we are updating the backup.
create backup
create backup
(the 2nd backup replaces the 1st one, but there will be no restore)

https://github.com/Expensify/App/blob/685bb4c7bbaa2ef332896de5cace193edb9c6a51/src/pages/iou/request/step/IOURequestStepDistance.tsx#L202
Notice that we need to update the action === CONST.IOU.ACTION.CREATE condition too as explained above.

Pinging my pal, @neil-marcellini for a little insight into the best project for this. I feel like it could be #wave-collect, but I'm not certain. Can you point me in the right direction?

Thanks for the proposals, everyone! @bernhardoj 's proposal looks good to me as it has correct RCA and fixes both issues in the OP.
🎀 👀 🎀  C+ review!

PR is ready
cc: @hungvu193

This issue is now ready for payment @johncschuster

Payment Summary:
Contributor: @bernhardoj owed $250 via NewDot
Contributor+: @hungvu193 owed $250 via NewDot
@bernhardoj / @hungvu193 do you feel this requires regression test steps? If so, can you please provide them? Thank you!

Regression test:

Open self DM.
Create a new distance track expense.
Select Categorize it.
Select any workspace.
In confirm page, verify the map shows the green route line.
Press the Distance field.
Verify the map shows the green route line.
Verify the button doesn't infinitely show loading indicator.
Close the categorize page.
Open the track expense report.
Verify the distance and rate don't show Pending.

Do we 👍 or 👎  ?

$250 approved for @hungvu193

All BZ Steps are complete. We're just waiting on paying out @bernhardoj. Closing!

Requested in ND.

$250 approved for @bernhardoj


pdfstudio: 2023.0.3 -> 2024.0.0

Description of changes
Update to version 2024.0.0
https://kbpdfstudio.qoppa.com/whats-new-in-pdf-studio-2024/
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

I see that Check 1 has failed, and looking into it I think this is the relevant bit from the README.md in pkgs/by-name:
Recommendation for new packages with multiple versions
These checks of the pkgs/by-name structure can cause problems in combination:

New top-level packages using callPackage must be defined via pkgs/by-name.
Packages in pkgs/by-name cannot refer to files outside their own directory.

This means that outside pkgs/by-name, multiple already-present top-level packages can refer to some common file.
If you open a PR to another instance of such a package, CI will fail check 1,
but if you try to move the package to pkgs/by-name, it will fail check 2.
This is often the case for packages with multiple versions, such as
{
  foo_1 = callPackage ../tools/foo/1.nix { };
  foo_2 = callPackage ../tools/foo/2.nix { };
}

The best way to resolve this is to not use callPackage directly, such that check 1 doesn't trigger.
This can be done by using inherit on a local package set:
{
  inherit
    ({
      foo_1 = callPackage ../tools/foo/1.nix { };
      foo_2 = callPackage ../tools/foo/2.nix { };
    })
    foo_1
    foo_2
    ;
}

I don't know nix well enough to know what to do. Using the pattern above, I think I need to create something like this, below,  and remove the original pdfstudio2021 = callPackage ../applications/misc/pdfstudio { year = "2021"; }; etc. from all-packages.nix, but I don't know where I need to create this and whether this is a part of a larger file.
{
  inherit
    ({
      pdfstudio2021 = callPackage ../applications/misc/pdfstudio { year = "2021"; };
      pdfstudio2022 = callPackage ../applications/misc/pdfstudio { year = "2022"; };
      pdfstudio2023 = callPackage ../applications/misc/pdfstudio { year = "2023"; };
      pdfstudio2024 = callPackage ../applications/misc/pdfstudio { year = "2024"; };
      pdfstudioviewer = callPackage ../applications/misc/pdfstudio { program = "pdfstudioviewer"; };
    })
    pdfstudio2021
    pdfstudio2022
    pdfstudio2023
    pdfstudio2024
    pdfstudioviewer
    ;
}

I'm going to kill this. I've now figured out how to add it to pkgs/by-name as a new package and will ask about this approach separately on discourse.

 I've now figured out how to add it to pkgs/by-name as a new package and will ask about this approach separately on discourse.

 I've now figured out how to add it to pkgs/by-name as a new package and will ask about this approach separately on discourse.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/advice-requested-on-whether-this-is-the-correct-way-to-use-pkgs-by-name/44933/1


Feature/30 add support for write keys

Manually tested all new methods.
Manually tested one/both API keys on construction.
This should close #30

Update the docs before merging to master.
Ensure that other code that uses the PurpleAIrAPI doesn't break.


offer salix to LSP users

We offer html5 interaction via the Content library on the REPL and in IDEServices, but no real support for serving actual content. Salix is a way to do that, with proven features. In this way this would substitute for the old Figure library (SWT version) of the Eclipse plugin.

This would be a vs code specific thing right? Not a LSP broad implementation?

It will be generic for all uses of the LSP servers because I've abstracted the client API in IDEservices interface that all editors must provide.


fix auditing so we can start adding audits

clear audit directory and make sure audit.py won't break things before merging in schema destroyer.

ok this is now working with submit last night


Index settings lifecycle name should be optional, not ILM policy name

JavaScript codegen started failing for me after this PR merged the other day, specifically breaking on the "policy name in ILM should be optional" change. The docs say policy_id is a required parameter, since it is part of the URL path.
I'm fairly certain the optional name that the original issue was referring to was for IndexSettingsLifecycle rather than PutLifecycleRequest.

this is the correct fix, sorry for the oversight

No problem! It took me a while to figure out that there were two separate possible places to look for this. :smile:


Clarify docs on additionalTextEdits

3.16 added support for deferring additionalTextEdits in completions (https://github.com/microsoft/language-server-protocol/issues/1003), but I don't see this mentioned anywhere in the draft 3.16 specification. Can the docs on what is allowed to be lazy be updated?

The client capability is in the spec here: https://github.com/microsoft/language-server-protocol/blob/gh-pages/_specifications/specification-3-16.md#L3244
Added a clarifying sentence to https://github.com/microsoft/language-server-protocol/blob/gh-pages/_specifications/specification-3-16.md#L3166
Thanks for pointing this out.


Updated badges on readme

Increased README readability

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.


Folder with three levels deep

Hi,
When I structure my project
my-app/
  README.md
  index.html
  favicon.ico
  node_modules/
  package.json
  src/
    components/
      header.js
    images/
      logo.svg
    App.css
    App.js
    index.css
    index.js

and I try to import logo.svg from: /src/components/header.js
as follows:
import logo from '../images/logo.svg';
It does recognize the path correctly.
But when I structure my project
my-app/
  README.md
  index.html
  favicon.ico
  node_modules/
  package.json
  src/
    components/
      header/
        index.js
    images/
      logo.svg
    App.css
    App.js
    index.css
    index.js

and I try to import logo.svg from: /src/components/header/index.js
as follows:
import logo from '.../images/logo.svg';
It doesn't recognize the path
Any help please?

If your code is import logo from '.../images/logo.svg', then the three dots at the beginning break the import. Try import logo from '../../images/logo.svg'.

Yep.


Graceful node termination (cordon/drain)

(Creating issues to track v0.3 roadmap items in #435, will update this description with more details in the coming days)

Just an FYI, this is becoming built-in: https://kubernetes.io/blog/2021/04/21/graceful-node-shutdown-beta/

Hey Matt. Thanks for bringing this up! We'll definitely be utilizing this in the future to reduce the work that Karpenter has to do for graceful node shutdown. As the Kubernetes site says that it is a 1.21 beta feature right now and we haven't verified 1.21 for Karpenter yet, we can't use this.
In the meantime, we'll be using the process referenced in the termination design doc. In the future we should re-evaluate and deduplicate the work we do here.

#534


✨ Mobile | Claim rewards in-person

What triggered this change? (PBI link, Email Subject, conversation + reason, etc)

#858

What was changed?

Allows for user's to redeem rewards in-person, which generates a QR code which they must then show to SSW staff. SSW staff can then scan the code to confirm the redemption and provide the user with the reward.

Figure: Users now have the option to redeem in-person

Figure: Redeeming in-person will display a QR code which must be then scanned by SSW staff. The user can also cancel the redemption if they've changed their mind. (Note: points aren't deducted until the redemption is confirmed)

Figure: If the user has closed the window of a pending redemption, they can tap the QR button to bring it up again

Figure: When SSW staff scans the code it will then be confirmed and they can hand over the reward. Points get deducted at this point.

Did you do pair or mob programming?

No

Also closes #314


Bump ITensors compat to fix directsum issue

This bumps the compat of ITensors to v0.3.48, which includes a fix to directsum made in https://github.com/ITensor/ITensors.jl/pull/1221. This fixes an issue that was being discussed in #77 where some functionality that made use of directum for converting between MPO formats (InfiniteBlockMPO and InfiniteMPO) was broken.

@LHerviou looks like tests are passing now.


performance compared to crun/runc/youki

Has any data related to this?

The oci-spec-rs crate is used to read/create the specs defined by OCI. As such it is not comparable to crun or youki which are used to create containers. Youki is using this crate to read the configuration for a container.


cant turn off control panel

please put the panel in the right screen.
chect work well but the panel right centrel screen so can play

I don't understand... could you send a screenshot link?

https://cdn.discordapp.com/attachments/450121951432802319/475592780362678272/New_Bitmap_Image.bmp
https://cdn.discordapp.com/attachments/450121951432802319/475607417980190720/New_Bitmap_Image_2.bmp
here bro, esc and B buttons cant make panel turn off

Try redownloading it now.

It work very well. Thank you


"Vertical" is incorrect

The control works horizontally -- it should be documented as a horizontal control.

Correct! Thanks!


流式音频生成报错[Errno -9996] Invalid output device (no default output device)

测试流式音频时，右上角弹出错误信息为：
[Errno -9996] Invalid output device (no default output device)

我查找了一下资料，是pyaudio引发的异常
原因是我在linux的docker容器中运行，找不到音频设备
我目前的解决方法是将宿主机的音频设备映射到docker容器，添加参数--device /dev/snd
不知能不能，在服务器端不需要音频设备的情况下，实现流式音频输出？

对不起，这是一个bug，在修，你用api调用的话是正常的流式返回，但是gradio我还在研究

大佬好，我用api流式调用时，也报错，报错信息如下：
| ERROR:    Exception in ASGI application   | Traceback (most recent call last):   |   File "/usr/local/lib/python3.9/site-packages/starlette/responses.py", line 265, in __call__   |     await wrap(partial(self.listen_for_disconnect, receive))   |   File "/usr/local/lib/python3.9/site-packages/starlette/responses.py", line 261, in wrap   |     await func()   |   File "/usr/local/lib/python3.9/site-packages/starlette/responses.py", line 238, in listen_for_disconnect   |     message = await receive()   |   File "/usr/local/lib/python3.9/site-packages/uvicorn/protocols/http/h11_impl.py", line 535, in receive   |     await self.message_event.wait()   |   File "/usr/local/lib/python3.9/asyncio/locks.py", line 226, in wait   |     await fut   | asyncio.exceptions.CancelledError: Cancelled by cancel scope 7f25929052b0   |    | During handling of the above exception, another exception occurred:   |    |   + Exception Group Traceback (most recent call last):   |   |   File "/usr/local/lib/python3.9/site-packages/uvicorn/protocols/http/h11_impl.py", line 407, in run_asgi   |   |     result = await app(  # type: ignore[func-returns-value]   |   |   File "/usr/local/lib/python3.9/site-packages/uvicorn/middleware/proxy_headers.py", line 69, in __call__   |   |     return await self.app(scope, receive, send)   |   |   File "/usr/local/lib/python3.9/site-packages/fastapi/applications.py", line 1054, in __call__   |   |     await super().__call__(scope, receive, send)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/applications.py", line 123, in __call__   |   |     await self.middleware_stack(scope, receive, send)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/middleware/errors.py", line 186, in __call__   |   |     raise exc   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/middleware/errors.py", line 164, in __call__   |   |     await self.app(scope, receive, _send)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/middleware/cors.py", line 85, in __call__   |   |     await self.app(scope, receive, send)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/middleware/exceptions.py", line 65, in __call__   |   |     await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app   |   |     raise exc   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app   |   |     await app(scope, receive, sender)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 756, in __call__   |   |     await self.middleware_stack(scope, receive, send)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 776, in app   |   |     await route.handle(scope, receive, send)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 297, in handle   |   |     await self.app(scope, receive, send)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 77, in app   |   |     await wrap_app_handling_exceptions(app, request)(scope, receive, send)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app   |   |     raise exc   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app   |   |     await app(scope, receive, sender)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 75, in app   |   |     await response(scope, receive, send)   |   |   File "/usr/local/lib/python3.9/site-packages/starlette/responses.py", line 265, in __call__   |   |     await wrap(partial(self.listen_for_disconnect, receive))   |   |   File "/usr/local/lib/python3.9/site-packages/anyio/_backends/_asyncio.py", line 678, in __aexit__   |   |     raise BaseExceptionGroup(   |   | exceptiongroup.ExceptionGroup: unhandled errors in a TaskGroup (1 sub-exception)   |   +-+---------------- 1 ----------------   |     | Traceback (most recent call last):   |     |   File "/usr/local/lib/python3.9/site-packages/starlette/responses.py", line 261, in wrap   |     |     await func()   |     |   File "/usr/local/lib/python3.9/site-packages/starlette/responses.py", line 252, in stream_response   |     |     chunk = chunk.encode(self.charset)   |     | AttributeError: 'tuple' object has no attribute 'encode'   |     +------------------------------------

这个问题解决了么？

修好了

请见 GSVI： https://github.com/X-T-E-R/GPT-SoVITS-Inference/commit/b99abc6d3c45e9e00b78032e38edafb2279a1bd5

请见 GSVI： X-T-E-R/GPT-SoVITS-Inference@b99abc6

刚提交的Inference/config.json的Json格式多了一个逗号，需要修正一下。

请见 GSVI： X-T-E-R/GPT-SoVITS-Inference@b99abc6

刚提交的Inference/config.json的Json格式多了一个逗号，需要修正一下。

对的，我删内容的时候忘了，谢谢提醒


Incorrect jar name

In demo/income_prediction/job_runner.sh, the version number for the income prediction jar file is old.  As a result, there is a ClassNotFoundException when trying to find the JobRunner class.
Existing:
build/libs/income_prediction-0.1.3-all.jar \
Should be:
build/libs/income_prediction-0.1.6-all.jar \
Please apply this change and commit to the git repo.
Thanks!

The issue has been fixed. Thanks!


Adds migration for seller and item database tables

Closing pull request due to failed refs after rebasing from main. Will open fresh pull request.


fix issues in tls policy docs markdown

@philbrookes triggered a manual docs build to deploy (see https://github.com/Kuadrant/docs.kuadrant.io#deploying)


v0.7.0 release plan

[x] OpenFunction Gateway
[ ] Disable Nginx ingress controller for default installation (Helm)
[x] Replace Kourier with Contour (Helm)
[x] Prepare Contour gateway installation (Helm)
[ ] Update and test dependent components: Dapr, KEDA, Knative etc. https://github.com/OpenFunction/OpenFunction/issues/260
[ ] Docs update for OpenFunction Gateway
[ ] Update function samples, especially the gateway-related part (Replacing domain ingress method with gateway method)
[ ] Release new version for functions-framework including Go, Nodejs, Java
[ ] Release new version for go/nodejs/java builders and push builder images if necessary

https://github.com/OpenFunction/functions-framework-go/pull/57 functions-framework-go has upgrade Dapr to 1.8.1 , thanks @tpiperatgod


Fail with admin authorization

I add an admin user in admin database and use the following uri to add a new connection in adminMongo:
mongodb://admin:thepass@<IP_ADDRESS>:27017/?authSource=admin

But then the server throws errors:
_http_outgoing.js:346
    throw new Error('Can\'t set headers after they are sent.');
    ^

Error: Can't set headers after they are sent.
    at ServerResponse.OutgoingMessage.setHeader (_http_outgoing.js:346:11)
    at ServerResponse.header (/home/perqin/Apps/adminMongo/node_modules/express/lib/response.js:719:10)
    at ServerResponse.send (/home/perqin/Apps/adminMongo/node_modules/express/lib/response.js:164:12)
    at done (/home/perqin/Apps/adminMongo/node_modules/express/lib/response.js:956:10)
    at Immediate._onImmediate (/home/perqin/Apps/adminMongo/node_modules/express-handlebars/lib/utils.js:26:13)
    at tryOnImmediate (timers.js:543:15)
    at processImmediate [as _immediateCallback] (timers.js:523:5)

npm ERR! Linux 4.4.0-47-generic
npm ERR! argv "/home/perqin/Apps/bin/node" "/home/perqin/Apps/bin/npm" "start"
npm ERR! node v6.0.0
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `node app.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node app.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the admin-mongo package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node app.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs admin-mongo
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls admin-mongo
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/perqin/Apps/adminMongo/npm-debug.log

That connection string looks fine. What page/URL are you navigating to when you get the Can't set headers after they are sent. error?

@mrvautin Just the index localhost:1234. Use mongodb://admin:thepass@<IP_ADDRESS>:27017/somedb?authSource=admin also works. It seems that I must specific a database when using admin account.


Android - we cant download more than 29 VCs in the INJI app

Describe the bug
We cant download more than 29 VCs in the INJI app
To Reproduce
prerequisite : dowload 29 VCs in the app

Authenticate and enter the app
click on ADD ID and download a 30th VC

Expected behavior
Should able to download suucessfully or proper limit message should be said
Observed
we are able to download and audit for that is loagged, but once the app is closed and reopened, the VCs which are downloaded after 29 th VC all gone back to loading state
Video
Uploading screen-20230125-164217.mp4…
Smartphone:

Device: PIXEL 6
OS: Android 13
MOSIP Version: <IP_ADDRESS>
MOSIP server: qa-1201-b2.net
APP link; https://github.com/mosip/inji/actions/runs/3986424542

Need to understand if this is a configured number.

This bug has been moved to Jira.
Link to Jira bug: https://mosip.atlassian.net/browse/MOSIP-26841

No more a valid bug as the limitation on hte number of VCs are based on the phone storage limit and not on the count of the VC downloaded, hence closing the bug on github.


Formula prediction module fails to calculate correct adduct mass from m/z

Basic information

My operating system and version:Windows11 Version 22H2 (OS build
22621.1702)
My MZmine version: Mzmine_Windouws_portable_3.4.27

What happened
I opened the Aligned feature list, selected the Predict molecular formula to start Formula prediction module.
It seems that there is an issue with adduct mass calculation ([M+H]+, [M-H]+, [M-H]-...), When I try to calculate adduct mass from m/z, I get wrong results.
For example, detected ion is 442.22875 and when [M-H]- ionization type is selected I get 443.23603, which seems to be the calculated mass for [M+H]+ adduct.

Sorry for the confusion, I am just a beginner. MZmine works as expected.
Just a suggestion, can you please change the description in the module of "Calculated mass* --> "Calculated neutral mass" or "Calculated mass of the neutral molecule" or similar.
Thank you very much!


feat(icon): Megaphone Icon

Overview

Added megaphone-icon.svg to gamut-icons

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[X] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-icons@5.9.4-alpha.fd52e7.0@codecademy/gamut-kit@0.5.67-alpha.fd52e7.0@codecademy/gamut-labs@19.24.11-alpha.fd52e7.0@codecademy/gamut@37.1.3-alpha.fd52e7.0@codecademy/monaco@0.3.15-alpha.fd52e7.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://613a3d3782ba8638ef8fa2c9--gamut-preview.netlify.appDeploy Logs

Sorry to rerequest a review — the icon was too thick and I was trying to edit the stroke width without doing the weird Figma exports. But the only way I could do it was to apply a stroke-width="0.624" property to get it to be the same width as our other icons. Would this cause any problems?

📬Published Alpha Packages:@codecademy/gamut-icons@5.9.4-alpha.173562.0@codecademy/gamut-kit@0.5.67-alpha.173562.0@codecademy/gamut-labs@19.24.11-alpha.173562.0@codecademy/gamut@37.1.3-alpha.173562.0@codecademy/monaco@0.3.15-alpha.173562.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://613a446b7a3d702fe85d95c1--gamut-preview.netlify.appDeploy Logs

o rerequest a review — the icon was too thick and I was trying to edit the stroke width without doing the weird Figma exports. But the only way I could do it was to apply a stroke-width="0.625" property to get it to be the same width as our other icons. Would this cause any problems?

I don't think so as it's going to get converted to a single path anyway.  We can keep an eye on it though.

Sounds good, the stroke widths are calculated correctly when I import them into Figma, but I know the actual markup with the transform x stroke-width could be messy. Happy to go back and touch this up again if we're experiencing issues.

📬Published Alpha Packages:@codecademy/gamut-icons@5.9.4-alpha.e7f602.0@codecademy/gamut-kit@0.5.68-alpha.e7f602.0@codecademy/gamut-labs@19.25.0-alpha.e7f602.0@codecademy/gamut-tests@2.5.0-alpha.e7f602.0@codecademy/gamut@37.2.0-alpha.e7f602.0@codecademy/konamimojisplosion@0.2.55-alpha.e7f602.0@codecademy/monaco@0.3.15-alpha.e7f602.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://613a6467eb106308af312310--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-icons@5.9.4-alpha.9539f6.0@codecademy/gamut-kit@0.5.69-alpha.9539f6.0@codecademy/gamut-labs@19.25.1-alpha.9539f6.0@codecademy/gamut@37.2.1-alpha.9539f6.0@codecademy/monaco@0.3.16-alpha.9539f6.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://613a6712d136470f0fbf3ec7--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-icons@5.10.2-alpha.851a3e.0@codecademy/gamut-kit@0.5.75-alpha.851a3e.0@codecademy/gamut-labs@19.26.4-alpha.851a3e.0@codecademy/gamut@37.3.3-alpha.851a3e.0@codecademy/monaco@0.4.3-alpha.851a3e.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://613fe56d4386a700b8c5a0c0--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-icons@5.10.2-alpha.e4cef5.0@codecademy/gamut-kit@0.5.80-alpha.e4cef5.0@codecademy/gamut-labs@20.0.1-alpha.e4cef5.0@codecademy/gamut@37.5.1-alpha.e4cef5.0@codecademy/monaco@0.4.6-alpha.e4cef5.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61426a035bc1131576f9debd--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-icons@5.10.2-alpha.71276b.0@codecademy/gamut-kit@0.5.83-alpha.71276b.0@codecademy/gamut-labs@20.0.4-alpha.71276b.0@codecademy/gamut@37.5.3-alpha.71276b.0@codecademy/monaco@0.4.8-alpha.71276b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61449a1009d01a2c0ed2c7b6--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-icons@5.10.2-alpha.05de7d.0@codecademy/gamut-kit@0.5.84-alpha.05de7d.0@codecademy/gamut-labs@20.1.1-alpha.05de7d.0@codecademy/gamut@37.5.3-alpha.05de7d.0@codecademy/monaco@0.4.8-alpha.05de7d.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6144e4cb0f59facd44699855--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-icons@5.10.2-alpha.c45047.0@codecademy/gamut-kit@0.5.85-alpha.c45047.0@codecademy/gamut-labs@20.1.2-alpha.c45047.0@codecademy/gamut@37.6.1-alpha.c45047.0@codecademy/monaco@0.4.9-alpha.c45047.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6148eba18b79431a41a861ab--gamut-preview.netlify.appDeploy Logs


Design the architecture for new Ocean.js

https://github.com/apollographql/apollo-client/tree/main/examples/bundling

forgot close comment: closed cause I see there's lots of work going on for new ocean.js so assuming there is an architecture design behind it.


Improvement apply AVX512 for memcmp and memcpy

Proposed changes
Inspired by Clickhouse #33706 Clickhouse #35983
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Now, doris do not support avx512 rethink we really should support it not the avx2 ?


Add Volts script

Adds a super basic script that simply generates user-configurable offset voltages.  It's wholly non-interactive and exists only to be a reliable, fixed voltage source for other modules.
Configuration must be done via the configuration JSON file.

Unfortunately, it looks like it was deleted, but Rory had a similar but configurable "Preset" script with user input for the static stored voltages. https://github.com/Allen-Synthesis/EuroPi/pull/173
I like this script as a starting point; I can see a lot of simple useful features added to this like the above mentioned user input voltages and saved banks for switching between sets of static voltage.


image processing

Could you please elaborate a little on input image size and size of mask for respective datasets? like celeb input image is 266x266 and the mask is written 256x256, which seems to be wrong.
Specifically, could you share the input image size places 2, and the size of the mask?
In training:
https://github.com/USTC-JialunPeng/Diverse-Structure-Inpainting/blob/main/README.md#:~:text=Modify data/data_loader.py according to the dataset. For CelebA-HQ%2C we resize each image to 266x266 and randomly crop a 256x256. For Places2 and ImageNet%2C we randomly crop a 256x256
In testing
https://github.com/USTC-JialunPeng/Diverse-Structure-Inpainting/blob/main/README.md#:~:text=Collect the testing set. For CelebA-HQ%2C we resize each image to 256x256. For Places2 and ImageNet%2C we crop a center 256x256.
I have tested the pre-trained model and found the results to be very off, attaching two sample-generated images.

Thanks for your questions.
All image sizes and mask sizes are 256x256. For the training of CelebA-HQ, we resize face images of 1024x1024 to 266x266 and then randomly crop 256x256 patches following Pluralistic Image Completion. It is a simple data augmentation but introduces a small domain gap between training and testing.
We have mentioned in REAMDE.md that the center_mask models are trained with images of 256x256 resolution with center 128x128 holes. The random_mask models are trained with images of 256x256 resolution with random regular and irregular holes. The random regular and irregular holes are generated by using net/nn.py.
As for your examples, we recommend using our random_mask model trained on Places2. If you are using our center_mask model trained on Places2, the inpainting results may be bad when the center hole is smaller than 128x128.
Best wishes,
Jialun

Thanks, Jialun.
it is working now. Great work!


Bruker method export

@kaipot Can you handle updating the Skyline-side to make use of the progress delegate?

@kaipot Can you handle updating the Skyline-side to make use of the progress delegate?

Yes, the test is working for me now, I'll make the changes in Skyline.

@kaipot Can you handle updating the Skyline-side to make use of the progress delegate?

Yes, the test is working for me now, I'll make the changes in Skyline.

I've added this to Skyline. By the way Matt, the test changes the prmsqlite file. Maybe it should copy it (or not write)?

That should get fixed. We don't want a test that causes a tree diff.

Should be ready to merge now. Kaipo I'm assuming you tested that the progress/cancel function is working ok in Skyline. :)

Should be ready to merge now. Kaipo I'm assuming you tested that the progress/cancel function is working ok in Skyline. :)

Yep, I think this is good to go. I will send out a link to the artifacts once the build is done.


.jar file

I'm looking for .jar file, for some reason i cannot get it from gradle

You cannot make a .jar file because this library contains layout files. You can fork this repo and build it locally where it'll show up in the build/outputs/aar/ directory.

Error:(26, 13) Failed to resolve: com.roughike:bottom-bar:1.3.3
Show in File
Show in Project Structure dialog

what's wrong

I have the same problem with the 1.3.9 version, other versions, and even if I try with 1.3.+
Error:(81, 13) Failed to resolve: com.roughike:bottom-bar:1.3.+
Show in File
Show in Project Structure dialog

I tried to use SDK 23 and Gradle 1.3.1 but no more idea... :(
Any idea?

tengo el mismo problema, ¿Cúal fue la solucion los que aplicaron?


compat issue with Debugger

might have to bump compat for Debugger
i'm getting this in julia-1.8
ERROR: Unsatisfiable requirements detected for package JuliaInterpreter [aa1ae85d]:
 JuliaInterpreter [aa1ae85d] log:
 ├─possible versions are: 0.1.1-0.9.15 or uninstalled
 ├─restricted by compatibility requirements with Debugger [31a5f54b] to versions: 0.7.0-0.8.21
 │ └─Debugger [31a5f54b] log:
 │   ├─possible versions are: 0.1.0-0.7.6 or uninstalled
 │   └─restricted to versions 0.6 by VimBindings [51b3953f], leaving only versions 0.6.0-0.6.8
 │     └─VimBindings [51b3953f] log:
 │       ├─possible versions are: 0.1.0 or uninstalled
 │       └─VimBindings [51b3953f] is fixed to version 0.1.0
 └─restricted by julia compatibility requirements to versions: 0.9.11-0.9.15 or uninstalled — no versions left

(not sure if JuliaInterpretter got installed as a dep from one of the packages i installed though)

@ArbitRandomUser I've removed the dependency on Debugger, you should be able to install without this issue.
I'm closing the issue for now, please re-open if there's still an issue!

@caleb-allen - I think Debugger is still in Project.toml (I'm seeing this issue also).
(Great package btw! You should add it to the package registry)

@MilesCranmer you're right, my mistake!
Removed in 248645a92a03eccdbaf9249a75262ae935a72a90

(Great package btw! You should add it to the package registry)

Thank you! I intend on adding it to the package registry after a few higher priority issues are resolved (e.g. #18)


Break codegen-server's dependency on codegen-client

Motivation and Context
This PR and fixes #1864.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@david-perez - Thanks for the thorough feedback! I think I incorporated everything, or left a reply explaining why not. Let me know if I missed something or if you disagree on a point.


Failing to start Osmosis with Docker. Panic: no base denom was set

System information
Osmosis version: osmolabs/osmosis:11.0
OS & Version: Linux with Docker
Expected behaviour
Osmosis node is running
Actual behaviour
The container is failing to start with error panic: no base denom was set
Steps to reproduce the behaviour
mkdir -p config data wasm
wget -O config/genesis.json https://github.com/osmosis-labs/networks/raw/main/osmosis-1/genesis.json
chown -R 65532:65532 config data wasm
docker run -p 26657:26657 -p 26656:26656 -p 26658:26658 -p 9090:9090 -p 1317:1317 -v ./config:/osmosis/.osmosisd/config -v ./data:/osmosis/.osmosisd/data -v ./wasm:/osmosis/.osmosisd/wasm osmolabs/osmosis:11.0 start

Backtrace
osmosis-mainnet  | 9:21AM INF starting ABCI with Tendermint
osmosis-mainnet  | 9:21AM INF Starting multiAppConn service impl=multiAppConn module=proxy
osmosis-mainnet  | 9:21AM INF Starting localClient service connection=query impl=localClient module=abci-client
osmosis-mainnet  | 9:21AM INF Starting localClient service connection=snapshot impl=localClient module=abci-client
osmosis-mainnet  | 9:21AM INF Starting localClient service connection=mempool impl=localClient module=abci-client
osmosis-mainnet  | 9:21AM INF Starting localClient service connection=consensus impl=localClient module=abci-client
osmosis-mainnet  | 9:21AM INF Starting EventBus service impl=EventBus module=events
osmosis-mainnet  | 9:21AM INF Starting PubSub service impl=PubSub module=pubsub
osmosis-mainnet  | 9:21AM INF Starting IndexerService service impl=IndexerService module=txindex
osmosis-mainnet  | 9:21AM INF ABCI Handshake App Info hash= height=0 module=consensus protocol-version=0 software-version=11.0.1
osmosis-mainnet  | 9:21AM INF ABCI Replay Blocks appHeight=0 module=consensus stateHeight=0 storeHeight=0
osmosis-mainnet  | 9:21AM INF initializing blockchain state from genesis.json
osmosis-mainnet  | 9:21AM INF running initialization for module module=capability
osmosis-mainnet  | 9:21AM INF running initialization for module module=auth
osmosis-mainnet  | 9:21AM INF running initialization for module module=bank
osmosis-mainnet  | 9:21AM INF running initialization for module module=distribution
osmosis-mainnet  | 9:21AM INF running initialization for module module=staking
osmosis-mainnet  | 9:21AM INF running initialization for module module=slashing
osmosis-mainnet  | 9:21AM INF running initialization for module module=gov
osmosis-mainnet  | 9:21AM INF running initialization for module module=mint
osmosis-mainnet  | 9:21AM INF minted coins from module account amount=225000000000000uosmo from=developer_vesting_unvested module=x/bank
osmosis-mainnet  | 9:21AM INF running initialization for module module=crisis
osmosis-mainnet  | 9:21AM INF running initialization for module module=ibc
osmosis-mainnet  | 9:21AM INF running initialization for module module=genutil
osmosis-mainnet  | panic: no base denom was set
osmosis-mainnet  |
osmosis-mainnet  | goroutine 1 [running]:
osmosis-mainnet  | github.com/cosmos/cosmos-sdk/x/genutil.DeliverGenTxs({{0x2ad5c78, 0xc000058030}, {0x2ae46a0, 0xc0000516c0}, {{0x0, 0x0}, {0xc00028c010, 0x9}, 0x0, {0x0, ...}, ...}, ...}, ...)
osmosis-mainnet  |      github.com/cosmos/cosmos-sdk@v0.46.0/x/genutil/gentx.go:113 +0x269
osmosis-mainnet  | github.com/cosmos/cosmos-sdk/x/genutil.InitGenesis(...)
osmosis-mainnet  |      github.com/cosmos/cosmos-sdk@v0.46.0/x/genutil/genesis.go:18
osmosis-mainnet  | github.com/cosmos/cosmos-sdk/x/genutil.AppModule.InitGenesis({{}, {_, _}, {_, _}, _, {_, _}}, {{0x2ad5c78, 0xc000058030}, ...}, ...)
osmosis-mainnet  |      github.com/cosmos/cosmos-sdk@v0.46.0/x/genutil/module.go:99 +0x13f
osmosis-mainnet  | github.com/cosmos/cosmos-sdk/types/module.(*Manager).InitGenesis(_, {{0x2ad5c78, 0xc000058030}, {0x2ae46a0, 0xc0000516c0}, {{0x0, 0x0}, {0xc00028c010, 0x9}, 0x0, ...}, ...}, ...)
osmosis-mainnet  |      github.com/cosmos/cosmos-sdk@v0.46.0/types/module/module.go:322 +0x429
osmosis-mainnet  | github.com/osmosis-labs/osmosis/v11/app.(*OsmosisApp).InitChainer(_, {{0x2ad5c78, 0xc000058030}, {0x2ae46a0, 0xc0000516c0}, {{0x0, 0x0}, {0xc00028c010, 0x9}, 0x0, ...}, ...}, ...)
osmosis-mainnet  |      github.com/osmosis-labs/osmosis/v11/app/app.go:338 +0x1b5
osmosis-mainnet  | github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).InitChain(0xc00023e780, {{0x0, 0xed85ec810, 0x0}, {0xc00028c010, 0x9}, 0xc0015244c0, {0x3c8d980, 0x0, 0x0}, ...})
osmosis-mainnet  |      github.com/cosmos/cosmos-sdk@v0.46.0/baseapp/abci.go:68 +0x535
osmosis-mainnet  | github.com/tendermint/tendermint/abci/client.(*localClient).InitChainSync(0xc0000afb60, {{0x0, 0xed85ec810, 0x0}, {0xc00028c010, 0x9}, 0xc0015244c0, {0x3c8d980, 0x0, 0x0}, ...})
osmosis-mainnet  |      github.com/tendermint/tendermint@v0.34.19/abci/client/local_client.go:272 +0x118
osmosis-mainnet  | github.com/tendermint/tendermint/proxy.(*appConnConsensus).InitChainSync(0x3?, {{0x0, 0xed85ec810, 0x0}, {0xc00028c010, 0x9}, 0xc0015244c0, {0x3c8d980, 0x0, 0x0}, ...})
osmosis-mainnet  |      github.com/tendermint/tendermint@v0.34.19/proxy/app_conn.go:77 +0x55
osmosis-mainnet  | github.com/tendermint/tendermint/consensus.(*Handshaker).ReplayBlocks(_, {{{0xb, 0x0}, {0x2487e33, 0x7}}, {0xc00028c010, 0x9}, 0x1, 0x0, {{0x0, ...}, ...}, ...}, ...)
osmosis-mainnet  |      github.com/tendermint/tendermint@v0.34.19/consensus/replay.go:319 +0xd78
osmosis-mainnet  | github.com/tendermint/tendermint/consensus.(*Handshaker).Handshake(0xc00fbebb40, {0x2ae4df8, 0xc000302000})
osmosis-mainnet  |      github.com/tendermint/tendermint@v0.34.19/consensus/replay.go:268 +0x3c8
osmosis-mainnet  | github.com/tendermint/tendermint/node.doHandshake({_, _}, {{{0xb, 0x0}, {0x2487e33, 0x7}}, {0xc00028c010, 0x9}, 0x1, 0x0, ...}, ...)
osmosis-mainnet  |      github.com/tendermint/tendermint@v0.34.19/node/node.go:325 +0x1b8
osmosis-mainnet  | github.com/tendermint/tendermint/node.NewNode(0xc0013e4280, {0x2ad2ab0, 0xc000239720}, 0xc0000915c0, {0x2ab98e0, 0xc00029bc08}, 0x1?, 0x0?, 0xc000091720, {0x2ad6f80, ...}, ...)
osmosis-mainnet  |      github.com/tendermint/tendermint@v0.34.19/node/node.go:733 +0x577
osmosis-mainnet  | github.com/cosmos/cosmos-sdk/server.startInProcess(_, {{0x0, 0x0, 0x0}, {0x2aebb68, 0xc0013ad350}, {0x0, 0x0}, {0x2adac60, 0xc00123d5c0}, ...}, ...)
osmosis-mainnet  |      github.com/cosmos/cosmos-sdk@v0.46.0/server/start.go:262 +0x79b
osmosis-mainnet  | github.com/cosmos/cosmos-sdk/server.StartCmd.func2(0xc00128db80?, {0xc001376e40?, 0x0?, 0x6?})
osmosis-mainnet  |      github.com/cosmos/cosmos-sdk@v0.46.0/server/start.go:129 +0x193
osmosis-mainnet  | github.com/spf13/cobra.(*Command).execute(0xc00128db80, {0xc001376d80, 0x6, 0x6})
osmosis-mainnet  |      github.com/spf13/cobra@v1.4.0/command.go:856 +0x67c
osmosis-mainnet  | github.com/spf13/cobra.(*Command).ExecuteC(0xc001242c80)
osmosis-mainnet  |      github.com/spf13/cobra@v1.4.0/command.go:974 +0x3b4
osmosis-mainnet  | github.com/spf13/cobra.(*Command).Execute(...)
osmosis-mainnet  |      github.com/spf13/cobra@v1.4.0/command.go:902
osmosis-mainnet  | github.com/spf13/cobra.(*Command).ExecuteContext(...)
osmosis-mainnet  |      github.com/spf13/cobra@v1.4.0/command.go:895
osmosis-mainnet  | github.com/cosmos/cosmos-sdk/server/cmd.Execute(0x0?, {0xc001238498, 0x12})
osmosis-mainnet  |      github.com/cosmos/cosmos-sdk@v0.46.0/server/cmd/execute.go:36 +0x1eb
osmosis-mainnet  | main.main()
osmosis-mainnet  |      github.com/osmosis-labs/osmosis/v11/cmd/osmosisd/main.go:16 +0x31
osmosis-mainnet exited with code 2

I think you have a typo on your data volume mount:
 ./data:/osmosis/.somosisd/data

Yep, accidentally made one, but it is only in this issue description

Is there a chance that you are trying to run the v1 genesis on v11 without having the state updated to v11?
When I run cat genesis.json | jq '.app_state|keys' I don't see the txfees module. This is the module that is returning panic: no base denom was set.
I believe that this module was introduced post-genesis. So my guess is that the v11 osmosis initializes the v1 genesis and ends up not having the txfees state.
Depending on what you are trying to do, you can:

sync from genesis by using v1 (version that does not have the txfees module) and swapping binaries at the right heights
use v11 but sync your node's state accordingly

We have an installer that can configure either option: https://get.osmosis.zone/
However, that would not use Docker. If using Docker is the goal, I  you can try getting a quicksync snapshot to mount on the data folder. Similar to how config and other folders were mounted. This is where quicksync snapshots can be found: https://quicksync.io/networks/osmosis.html
Please let me know if that helps

Hmm, ok, I'll try. Downloading the archive snapshot on another node right now

@dzmitrykliapkou what is it you are trying to accomplish? You likely wont need an archive snapshot (and if you do, idk if docker would be the way to go)

Hi @dzmitrykliapkou . Is there still anything that we can help with? If not, I will close this issue

@dzmitrykliapkou what is it you are trying to accomplish? You likely wont need an archive snapshot (and if you do, idk if docker would be the way to go)

We definitely need archive ones, that is for an application. We are running Cosmos archive nodes using docker, so I hope there will be no issues with Osmosis

Hi @dzmitrykliapkou . Is there still anything that we can help with? If not, I will close this issue

Think the issue can be closed


remove to be deprecated critical pod annotation

see https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/#marking-pod-as-critical
mentioned in #12602

@morvencao  could you help with this?

closing this as PR is already merged


Allow NpmAuthenticate to hanle scoped registries (#6954)

Allow NpmAuthenticate to hanle scoped registries

If multiple scoped registries are against the same account the authenticate step does not get credentials for all scopes because it is only checking host not path.

changing patch version to 2

Update package.json

Update task.json

Adding version to lock files

@keithrob Can this be merged?

I'm going to close since this is targeting m133. We can reopen if appropriate


Support for named parameters

This PR closes #385 by giving support for named parameters in the EnsembleSampler.
Specifically this PR:

allows a user to pass in a list of names (types as str but really can be anything) for the parameters to the constructor for EnsembleSampler. Checks are made to ensure that the number of unique names are ndim
In the EnsembleSampler.compute_log_prob method, these names are used to reshape the parameters passed in to the method (having previously been generated by the Move) so that instead of an ndarray of shape (nwalkers, ndim) it becomes a list of length nwalkers of dictionaries of length ndim, with each key-value pair being the names and parameters
A helper function was written to perform the ndarray -> List[Dict[str, np.number]] conversion, so that it could be tested separately from the compute_log_prob method (higher testable surface area)
test of this functionality were placed in the newly created src/emcee/tests/unit/test_ensemble.py file. I tested the helper method, compute_log_prob, and run_mcmc
very small bits of cleanup in ensemble.py to be more PEP8 compliant/more pythonic

As discussed in #385, this PR makes no assumptions about the kinds of likelihood functions or underlying models being utilized. It does not take gradients of the likelihood, nor does it break the API (frontend or backend) in any way. I believe the unit test in in the TestNamedParametes tests make it clear why this is useful. Positional bugs will be a thing of the past!
Support for named parameters could go a bit further. For example:

I didn't allow vectorize=True when naming the parameters. I guess the right thing to allow for would be if vectorize=True then we produce one dictionary where the keys are the parameter names and the values are 1D arrays of each parameter.
I did not implement support for parameter names in the PTSampler. IMO doing this would be "double work" and from a software perspective it would make more sense (IMO) to make an abstract Sampler class that handled the names, and that both the EnsembleSampler and PTSampler would subclass. But, this is obviously a non-trivial refactor (that I would be happy to contribute to).

Thanks @dfm for the discussion on #385. I look forward to your review.

Thanks @tmcclintock: This looks like a good start!
I'll take a closer look ASAP, but I think I'm overall very happy with this approach. I think the one thing I would like to have would be to allow each parameter to have an arbitrary shape. This will complicate the logic a bit, but I think it would make this more impactful.

Also: scipy needs to be an optional dependency even for the tests.

@dfm thanks for the quick response.
RE each parameter have an arbitrary shape - Going by this docstring I was under the impression that each parameter was a scalar. Are you saying you want to change the signature to EnsembleSampler.sample such that initial_state could be (List[Union[np.number, np.ndarray]]) (i.e. params[0] was a scalar but params[1] could be an array)?  If not, can you please clarify the pattern you are requesting?
RE scipy in all tests - can you elaborate? Do you mean just import scipy at the top? That should not be necessary unless there is some magic in the github actions you set up.

RE each parameter have an arbitrary shape - Going by this docstring I was under the impression that each parameter was a scalar. Are you saying you want to change the signature to EnsembleSampler.sample such that initial_state could be (List[Union[np.number, np.ndarray]]) (i.e. params[0] was a scalar but params[1] could be an array)? If not, can you please clarify the pattern you are requesting?

I'm not suggesting changing the syntax, I'm just saying that if you're adding names to elements of the vector space, there's no reason why there needs to be one name per dimension. My parameters are often multivariate, and it would be annoying to manually add param_0, param_1, ... as names manually, vs. calling it param and providing a shape. Right now, you're requiring that a name maps to a scalar and that seems artificial if we're adding this logic anyways!
If this isn't clear, I'll try to put together a little demo this week.

I see, so for instance in a GMM you would essentially like to do:
params["weights"]
# (2,)  # component weights
params["means"].shape
# (2,)
params["cov"].shape
# (3,)  # independent elements of the cov matrix

Correct?
For an MVP this is simple -- if we restrict keywords to be either single values or consecutive numbers in the parameter array then this is easy. If instead we wanted to allow a keyword to map to an arbitrary set of indices in the params array, this is tricky (like if params["a"] mapped to the first, fifth, and tenth parameters in the params array, this may be a tricky pattern to support in general).
Are you OK with allowing only consecutive parameters?

Yes this sounds about right and I would be totally happy with requiring contiguous values!

@dfm I have updated the PR. Now the following pattern is supported:
def ln_prob(params):
    mean1, mean2 = params["means"]
    var1, var2 = params["vars"]
    constant = params["constant"]
    ...

sampler = EnsembleSampler(..., parameter_names = {"means": [0, 1], "vars": [2, 3], "constant": 4})

That is, paramter_names can be any of:

a list of names ["a", "b", "c"]
a dictionary where the values can be integer positions of parameters or list of integers {"a": [1, 3, 5], "b": 0, "c": [2, 4]}

So, I was able to support non-contiguous parameter indexes.
Let me know if this all looks good. If you'd like docs work done I can either do that here or in another PR.

@dfm can you push the button on the workflow? I'd like to tackle any problems that might occur ahead of your review.

@tmcclintock: Weird - I thought I already had. Maybe I have to do it each time?

Don't worry about the coverage failure.

@tmcclintock: Sorry about the delay on this! I think this looks awesome so I've merged and we can address issues as they come up in other threads. If you'd be up for adding a tutorial about this, that would be awesome. Want to start another PR whenever you have a chance?
Thanks again for this!

Sorry to revive this, but did the tutorial mentioned ever get put together?  If so, could you point me to it?  I can probably figure it out on my own, but I figured I would check.  I'm super excited about this feature.  Thanks!

@cluhmann I have not written the tutorial. My bad :/. You can see an example of how to set up a function with named parameters in the unit test found in src/emcee/tests/unit/test_ensemble.py.


When sampling a model trained with class_cond=True, do we need to give it the imagenet grountruth labels?

As in the title, I am wandering if I need to pass the class label when sampling a trained super resolution network.
Isn't it wrong to use the data groundtruth labels during sampling? How could I have them in a real case without a classifier?
Additional question: does class conditioning improve the super resolution model performance?
Many thanks,
Stefano

if you read the manual there is the answer
"If you wish to train a class-conditional model, name the files like "mylabel1_XXX.jpg", "mylabel2_YYY.jpg", etc., so that the data loader knows that "mylabel1" and "mylabel2" are the labels. Subdirectories will automatically be enumerated as well, so the images can be organized into a recursive structure (although the directory names will be ignored, and the underscore prefixes are used as names)."
You have to rename your training set accordingly.
Also you may change the NUM_CLASSES variable in the script_util.py

You mean renaming the images to mylabel1_XXX.jpg or just creating seperate text files?

Yes exactly rename your files mylabelX_xxx.jpg. Please consider that the data loader is recursive. That means you can put each label in a different subfolder, when you like to have it sorted.

Thanks @choROPeNt for your answer! Actually my question was for the sampling stage, At the beginning I thought that we needed to provide the labels solely during training, and that during sampling that part would have been replaced by the classifier.
I was wrong: you need to condition (use the groundtruth labels) even during sampling. This is because the conditioning and guidance are two completely separate things.
However I am still thinking which kind of improvement can these labels provide during sampling, and I am also wondering what could be the purporse of a Super resolution network requiring the groundtruth labels.
I think an easy answer to this is the fact that the super resolution network is here used only for upsampling the  generated images.
I hope my message is somehow clear.

yes thats true, even on the sampling stage you have to submit label classes accordingly to your dataset.
in image_sample.py the following lines of code do that
if args.class_cond:
    classes = th.randint(
                low=0, high=NUM_CLASSES, size=(args.batch_size,), device=dist_util.dev()
            )
    model_kwargs["y"] = classes

you can modify this to
classes = th.IntTensor([cls] * args.batch_size).to(dist_util.dev())

when you like to have a specific class sampled.
Yet I dont know the exact difference of guidance and conditioning. But maybe guided diffusion  are good answers.

you can try something like this.
Create a translation dict with all classes and assign them to an integer value
my_dict = {"cat": 0, "dog": 1}

your data loader should return a list of strings like that
my_list = ["cat", "dog","cat","cat"]

now convert the list of strings to a list of integers by given dict:
matched_values = [my_dict[item] for item in my_list if item in my_dict]

for this example your example you can write:

classes  = {"cat": 0, "dog": 1}
cls = ["cat", "dog","cat,"cat","dog"]

classes = th.IntTensor([classes[item] for item in cls if item in classes] * args.batch_size).to(dist_util.dev())

print("Matched values:", matched_values)


[VScode] Switch to file-watcher architecture to prevent stale-file issues

VSCode only listens to opened files or files in the baml_src directory. Our current approach of lazily refreshing the list of files in baml_src isn't very robust.
We should just watch for file changes preemptively via a file-watcher mechanism, so we always have the latest state.
Things to keep in mind:

If we retrieve a doc from the cache, it should also have the unsaved changes as returned by VSCode onDocumentChanged(..) callbacks. Our playground works off the in-memory content even if you havent saved a file.

Added synchronization between the server in #368


Add links to example Datasette instances to appropiate places in docs

Links to working examples would really help, especially on these pages:

http://datasette.readthedocs.io/en/latest/json_api.html
http://datasette.readthedocs.io/en/latest/sql_queries.html
http://datasette.readthedocs.io/en/latest/facets.html
http://datasette.readthedocs.io/en/latest/full_text_search.html

Funny you should mention that... I'm planning on doing that as part of the official Datasette website at some point soon. A Datasette instance that lists other Datasette instances feels pleasingly appropriate.

https://datasette-registry.now.sh Is now live, powered by https://github.com/simonw/datasette-registry - still needs plenty of work but it's an interesting start.

https://latest.datasette.io/ now always hosts the latest version of the code. I've started linking to it from our documentation.


Enhancement/update token history as hive history 85zrxbfjh

Good job! Just two small things:

please link the Layer 2 transactions to the Layer 2 block explorer, not hiveblocks : https://he.dtools.dev
please use window.open instead of window.create, we don't want to have a new window created everytime we click on the logo, but rather a new tab

Done fixes as requested. Asking a new review.


ReqMgr2: ACDC creation via webpage - naming needs to be fixed

If you don't change the request name during ACDC creation, it offers the same original request name without the timestamp part, such that ACDCing
pdmvserv_EXO-RunIISummer15GS-05060_00274_v2__160308_110629_7026
creates:
amaltaro_pdmvserv_EXO-RunIISummer15GS-05060_00274_v2__160315_102225_1898
so, just prepending the user name and appending the timestamp.
My suggestion is to keep the same behaviour as in reqmgr, so replacing the user name by "ACDC" and removing the timestamp part, such that it creates:
amaltaro_ACDC_EXO-RunIISummer15GS-05060_00274_v2__160315_102225_1898

@amaltaro, Alan, you can assignall reqmgr2 problems to me. :smile:

How did you create ACDC, using Web interface or some script?

Don't worry, you can have them all :-D
Yes, I created it via web page (wmstats).

Hi Alan, this is due to its requestor's name is different from the prepended string. There is no difference between the reqmgr and reqmgr2.
requestor<EMAIL_ADDRESS>string appended: pdmvserv
Anyway, I will update the patch handle this case.


[YUNIKORN-2211] Replace Allocation uuid with allocationID

What is this PR for?
docs changes to replace uuid with allocationID
What type of PR is it?

[ ] - Documentation

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2211
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

@wilfred-s can you take a look?


Refactor epoch function

Description
Fixes all dynamic tests.
Related Issue(s)
n/a
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please describe):

Breaking Change
none
Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have run cargo fmt and cargo clippy to ensure my code is formatted and linted correctly
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Screenshots (if applicable)
n/a
Additional Notes
none

This PR now contains only refactoring of epoch function based off the dynamic branch with fixed tests.

Will create another PR to development branch instead.


Adding babel support to Monster Stat Box

By substituting the hardcoded strings in dndmonster.sty with string macros, it's possible to add captions to them so that babel or polyglossia can automatically translate the field names in the moster box.
I've implemented this mostly for myself, as such, the only language I could add was Italian. Furthermore, there still isn't an official localization for 5e source material, so I went with 3.5/Pathfinder terminology where applicable.

I have not used babel for much other than loading hyphenation rules. this will take me some time to look over, but it looks like it adds a nice localization hook for users. Thanks!

Do the translation strings require babel to be loaded before the dnd package?

As far as I know, yes; it needs to be loaded before so that other packages can pick up the language settings.

Sure, I'll get on to it later today once I'm on my PC.

And what I mean by 2 is, "How do I switch to using your language strings?"

I hope this is what you meant; I've added some comments in example.tex explaining how to use the language switches.
For babel, the new string macro definitions are added to \captions for the given language, and caption rules are loaded when loading language definitions with \usepackage[{babel}.
I've also added a base template to copy/paste to define language macros, instructions on how to use it, and a reference to it in dndstrings.sty.

Well, I guess GitHub comment box doesn't like angle brackets... That's meant to be \captionlang where lang is the name of a language supported by babel, for example \captionsitslian, and \usepackage[lang]{babel}.
Sorry for the formatting mess.


center is shifted in terms of tile

In the latest master, I have added a marker in the center. If you use selector in develop tools, you can figure out this marker is never in the tile that it is supposed to be in all zoom level. More or less shifted.
This is probably related to #13 and #15.
In zoom level 8, this is the most obvious.

I have forked your repo, and change leaflet to its latest version(actually 'master' branch).
And later I figured out the solution to #3 #13 #15 #18 #19.
Unfortunately, there has one problem related to map bounds.

And you may have a look at below urls:
http://wsw0108.github.io/leaflet-baidu/examples/baidu.html
http://wsw0108.github.io/leaflet-baidu/examples/bounds-issue.html

Great! so we can continue this project maybe.
Zhifei Fang 方之斐
Member of Paradise Lab. University of Ottawa
[image: View Zhifei Fang's LinkedIn profile]View Zhifei Fang's profile
http://ca.linkedin.com/in/zhifeifang
http://thefaceteam.org/
2015-06-19 11:23 GMT-04:00 wsw0108<EMAIL_ADDRESS>
And you may have a look at below urls:
http://wsw0108.github.io/leaflet-baidu/examples/baidu.html
http://wsw0108.github.io/leaflet-baidu/examples/bounds-issue.html
—
Reply to this email directly or view it on GitHub
https://github.com/sureleo/leaflet-baidu/issues/19#issuecomment-113547242
.

I did test against leaflet stable, the bounds issue does not occurred.
Seems it's done with leaflet stable.
You can visit http://wsw0108.github.io/leaflet-baidu/ to check.


Doubled up mega-linter runs

It appears we run mega-linter twice on PRs. Maybe need to figure out how to disable the push job unless it is on main or maybe just disable the pull-request job completely? That sounds less-than-ideal if I want outside contributions.


Remove Twenty20

The site shutted down on July 31st, 2022 - https://help.elements.envato.com/hc/en-us/articles/360034211392-About-Twenty20

Thanks for your contribution!


Titlebar not appear

The titlebar not appeared
my html
<!DOCTYPE html>

        <meta charset="utf-8">
        <title>*hidden</title>

        <link rel="stylesheet" href="..\css\index.css">

*hidden

My lipsum

Your problem is not reproduceable with the information you provided so far.
Where and how are you initializing the titlebar?

You can use the sample folder of this project, to see how the use of the title bar is.

Closed because no response was obtained.


Fix instructions for dc/os ssh tunnel

Fix notation for SSH tunnel clarifying remote/host and local ports.

@jpoon,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@jpoon : Thanks for your contribution to the Azure documentation! The author, @dlepow, has been notified to review your proposed change.

@jpoon Jason, thanks for the clarification. Looks good!
#sign-off