core-estimator works on my development server, but not on my web page

I recently had to reinstall Windows on my computer.  I freshly installed all major browsers.  You may recall that I use core-estimator on my web page at http://danielsadventure.info/html5fractal/.
This page seems to work fine with IE and Chrome (altho IE tends to misestimate the number of cores), but for some reason, Firefox hangs when trying to estimate the number of cores.
The strange thing is that this happens only in Firefox and only when I run the page on my public web server.  When I run it in the Visual Studio development server, it works fine.  Furthermore, Firefox shows no error indicating that anything went wrong, and the browser itself does not hang; only the Javascript seems to stop.

Seeing as the behavior is different off your dev server, it may be partly caching-related. Please clear your entire cache in Firefox and report back.
As for the general JS hang, I will look into Core Estimator on the current version of Firefox later today.

As this happened with a fresh installation of Windows 8 and Firefox, I don't see how caching could be a problem.  I did go ahead and clear my cache several times, but the behavior is frustratingly persistent.
The issue only happens with Firefox and only when the page runs on the public web server, as opposed to the development server.  When you access the page for the first time, it immediately invokes core-estimator, so it should be easy for you to reproduce the problem: just point your browser here: http://danielsadventure.info/html5fractal/.
If you don't see the same issue and you're using the latest version of Firefox, that would suggest that there is a problem with my setup, but as of now, I have no idea what is causing the problem.

Yeah, the estimator is definitely freezing for me on Firefox as well (the page itself is still responsive though). I'll help look into this later today.

Thanks, Eli.  I can understand Chrome working, but not Firefox due to Chrome using the NaCl system, but one would think that if it works in IE, it should work in Firefox because both are doing some heavy number crunching to estimate performance the same way.

Yeah, it may actually be a bug in Firefox. Hopefully it's not and is something I can fix in Core Estimator.

I spent a few minutes tonight checking it out but it isn't very obvious. I'll look more tomorrow.

Eli, I spent some more time poking at this.
I reduced the complex web page down to the bare bones required to reproduce the problem and published this to http://danielsadventure.info/test.
There are only four lines of code in addition to your .js files.  Maybe this will make it easier for you to help me fix it.

Checking out your reduced testcase now. I'll see what I can find.

I'm really sorry, but I can't seem to reproduce your problem anymore in Firefox on the reduced testcase or even on http://danielsadventure.info/html5fractal/, as I'm getting the alert with the # of cores result now. I ran it a bunch of times to see if the issue would come up but it won't.
I updated Firefox yesterday. Are you encountering this issue on Firefox 38.0.1?

Hmmmm.... I wonder what is causing this.  I forgot to tell you earlier that it seems to reproduce about 9 times out of 10 on http://danielsadventure.info/test, but I have no idea why... perhaps some sort of race condition or something.  For what it's worth, if I open up the "Task Manager" and reproduce the problem, I see the CPU usage spike for a second or so and then drop back down close to 0 as the page hangs.
I recently upgraded to a 4-core 4 GHz i7 machine, so maybe the hardware has something to do with it.  Your test page (http://wg.oftn.org/projects/core-estimator/demo/) seems to work fine every time.
Maybe you can point me to directions for using your version of the core estimator with feedback that shows the numbers lighting up as it guesses at the number of cores?  Perhaps that would shed some light on the situation.

Oh, and yes, my Firefox version is 38.0.1

I'm sorry that I'm no help finding this possible race condition so far. I may cross-post this to a programming group IRC channel I frequent or to StackOverflow if a it doesn't look like we can find the solution soon.

Okey, dokey... I just tried to reproduce this again with Firefox 38.0.5.  It works fine now, so it seems that there is some issue with that particular version of Firefox I was using before: 38.0.1


comparing positive and negative angles in degrees_east

from cf_xarray.units import units

220 * units.degrees_east == (-140 * units.degrees_east)

is False. Can this be True instead?

This would be a good thing to ask upstream in Pint! I'm not aware of any modular arithmetic support, but I definitely see something like this being useful.


Feature/description

Feature: media description added

add description to a media
remove description
view description

LGTM, great work on adding the features.


different color for project and tasks

Hello how can i have a color for a main task (a project) and different color for all dependent tasks ???
regards
António

First


Feature: pluggable workflow

This PR makes it possible to use nf-cmgg/germline as a pluggable workflow in a meta pipeline.

Oh forgot to fix the tests :grin:


fix(Interceptor): wrap the "once" event listener, ditch "untilIdle" Promise

Follow-up to #427

Changes

These are internal changes and have no effect on the public API.

This change drops the internal implementation of AsyncEventEmitter used to await all request listeners from being done. Instead, it introduces a RequestConrtoller that just holds a response Promise to whichever surface calling .respondWith().
The request listener await logic is achieved by:

Adding a once request listener that always responds to the intercepted request with `undefined. using the request controller. This leverages the native listeners execution order to provide a fall-safe listener in case the consumer hasn't handled the request in any way.
Adding a new emitAsync utility to account for async request listeners. emitAsync executes all the listeners for the given events awaiting them (i.e. in order).

Released: v0.25.2 🎉
This has been released in v0.25.2!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i @mswjs/interceptors@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


param order

I think you should change the parameter order. I mean:
colorful.Println(colorful.RedColor, colorful.BlueBackground, "RedColorBlueBackground")

to
colorful.Println("Text", colorful.RedColor, colorful.BlueBackground)

And the color parameters could be optional (variadic):
colorful.Println("Text") // equivalent of fmt.Println
colorful.Println("Text", colorful.RedColor) // only color changed
colorful.Println("Text", colorful.RedColor, colorful.BlueBackground) // color and bg changed

Hi,@milad jan as you know Go doesn't support method overloading and also it doesn't support multiple variadic parameters in a function. I know that we have some alternative ways for handling that like(...interface{}) but I think that those ways are not suitable for our use case and I changed the structure for fixing that.
now, we can use this package like the below:

with color and background

	colorful.WithColor(colorful.RedColor).
		WithBackgroundColor(colorful.BlueBackgroundColor).
		Println("RedColorBlueBackground")

or
	colorful.WithBackgroundColor(colorful.BlueBackgroundColor).
		WithColor(colorful.RedColor).
		Println("RedColorBlueBackground")

only with color:

	colorful.WithColor(colorful.GreenColor).
		Println("GreenColor")

only with background color:

	colorful.WithBackgroundColor(colorful.YellowBackgroundColor).
		Println("YellowBackground")

If you have any other ideas, please tell me.
Thanks a lot.

Regrettably, Go does not provide support for the feature I mentioned. However, I truly appreciate your understanding of my idea, and I must say your solution appears to be excellent. Well done!


fix Use pending_remote_rowsets to avoid deleting rowset files being uploaded

Proposed changes
Issue Number: close #xxx
Problem summary
Previous remote_files_lock is not work in such situation:
Thread A upload new rowset.
Thread B list rowsets, then calculate unused remote files by list result and rowsets in tablet.
Thread A add new rowset to tablet.

Use pending_remote_rowsets to avoid deleting rowset files being uploaded.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[x] Is this PR support rollback (If NO, please explain WHY)

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...

run p0

run arm

run p0

run buildall

run p0

run p0

run p0


chore: get granular benchmarks for avm simulation and kernel proving across the various public phases

Get milliseconds for avm simulation of functions.

Benchmark results
Metrics with a significant change:

proof_construction_time_sha256_30_ms (16): 1,808 (+29%)
app_circuit_witness_generation_time_in_ms (SchnorrAccount:constructor): 1,431 (-22%)
protocol_circuit_witness_generation_time_in_ms (private-kernel-inner): 988 (-18%)
protocol_circuit_proving_time_in_ms (root-parity): 39,435 (+16%)
protocol_circuit_proving_time_in_ms (public-kernel-app-logic): 48,949 (+23%)
protocol_circuit_proving_time_in_ms (public-kernel-teardown): 46,830 (+19%)
protocol_circuit_proving_time_in_ms (public-kernel-tail): 184,877 (+18%)
protocol_circuit_proving_time_in_ms (root-rollup): 23,741 (+20%)

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,693
1,536
702 (-1%)
753
780 (+2%)

proof_construction_time_sha256_30_ms
11,722
3,158 (+1%)
:warning: 1,808 (+29%)
1,634 (+15%)
1,536 (+5%)

proof_construction_time_sha256_100_ms
44,796
12,072
5,655
5,596 (+1%)
5,514 (+1%)

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
58.0
88.0

proof_construction_time_poseidon_hash_30_ms
1,510
415
200 (+1%)
224
270 (+2%)

proof_construction_time_poseidon_hash_100_ms
5,718
1,568
725 (-1%)
762
787 (-1%)

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

Metric
4 txs
8 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412

l1_rollup_calldata_gas
9,464
9,448

l1_rollup_execution_gas
608,000
607,984

l2_block_processing_time_in_ms
697 (+1%)
1,284

l2_block_building_time_in_ms
22,452
45,575

l2_block_rollup_simulation_time_in_ms
22,326
45,227

l2_block_public_tx_process_time_in_ms
19,177
41,831

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
5,897
8,499

node_database_size_in_bytes
9,494,608
12,763,216

pxe_database_size_in_bytes
7,774
15,127

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
proving_time_in_ms
input_size_in_bytes
output_size_in_bytes
proof_size_in_bytes
num_public_inputs
size_in_gates

private-kernel-init
135 (-1%)
486 (-4%)
12,917 (+5%)
20,634
64,614
89,536
2,731
524,288

private-kernel-inner
406 (-1%)
:warning: 988 (-18%)
50,438 (+11%)
92,326
64,614
89,536
2,731
2,097,152

private-kernel-tail
373 (+1%)
1,821 (-8%)
46,361 (+8%)
96,545
68,261
11,648
297
2,097,152

base-parity
6.49 (-5%)
1,687 (-5%)
2,632 (-2%)
128
64.0
2,208
2.00
131,072

root-parity
49.6 (-5%)
62.2 (+19%)
:warning: 39,435 (+16%)
27,100
64.0
2,720
18.0
2,097,152

base-rollup
5,967 (-1%)
2,439 (+3%)
82,826 (+11%)
119,738
756
3,648
47.0
4,194,304

root-rollup
113 (+1%)
80.0 (+29%)
:warning: 23,741 (+20%)
25,309
620
3,456
41.0
1,048,576

public-kernel-app-logic
569
3,530 (-2%)
:warning: 48,949 (+23%)
108,073
86,550
116,768
3,582
2,097,152

public-kernel-tail
1,133 (-1%)
23,011 (+3%)
:warning: 184,877 (+18%)
403,238
7,646
11,648
297
8,388,608

private-kernel-reset-small
588
1,970 (-7%)
46,945 (+8%)
120,737
64,614
89,536
2,731
2,097,152

public-kernel-setup
661 (-2%)
2,765 (+3%)
43,268 (+15%)
108,073
86,550
116,768
3,582
2,097,152

public-kernel-teardown
566
3,548 (-1%)
:warning: 46,830 (+19%)
108,073
86,550
116,768
3,582
2,097,152

merge-rollup
30.5 (-5%)
N/A
N/A
16,542
756
N/A
N/A
N/A

private-kernel-tail-to-public
N/A
6,959 (-4%)
53,117 (+8%)
N/A
N/A
116,768
3,582
2,097,152

Stats on running time collected for app circuits

Function
input_size_in_bytes
output_size_in_bytes
witness_generation_time_in_ms
proof_size_in_bytes
proving_time_in_ms
size_in_gates
num_public_inputs

ContractClassRegisterer:register
1,344
9,944
465 (-1%)
N/A
N/A
N/A
N/A

ContractInstanceDeployer:deploy
1,408
9,944
41.1 (-2%)
N/A
N/A
N/A
N/A

MultiCallEntrypoint:entrypoint
1,920
9,944
1,763 (-13%)
N/A
N/A
N/A
N/A

SchnorrAccount:constructor
1,312
9,944
:warning: 1,431 (-22%)
N/A
N/A
N/A
N/A

SchnorrAccount:entrypoint
2,304
9,944
2,830
16,768
55,895 (+12%)
2,097,152
457

Token:privately_mint_private_note
1,280
9,944
1,574 (-10%)
N/A
N/A
N/A
N/A

FPC:fee_entrypoint_public
1,344
9,944
1,046 (-7%)
16,768
10,743 (+5%)
524,288
457

Token:transfer
1,376
9,944
5,469 (+1%)
16,768
53,465 (+11%)
2,097,152
457

Benchmarking:create_note
1,344
9,944
1,395
N/A
N/A
N/A
N/A

SchnorrAccount:spend_private_authwit
1,280
9,944
76.9
N/A
N/A
N/A
N/A

Token:unshield
1,376
9,944
3,883 (-1%)
N/A
N/A
N/A
N/A

FPC:fee_entrypoint_private
1,376
9,944
4,766 (-1%)
N/A
N/A
N/A
N/A

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
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.4 (-1%)
16.8 (-3%)
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.7
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.602 (-1%)
0.516 (-4%)
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.9 (-3%)
75.9
133
246
475 (+1%)
N/A

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

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.495 (-4%)
0.468
0.456
0.446
0.443
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
58.3 (-4%)
112
184
350
631
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
107
208
355
686
1,263
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.502 (-3%)
0.503
0.487
0.479
0.471
N/A

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

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
101

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.549 (-2%)

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
79,470
665,267

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

Benchmark results
Metrics with a significant change:

app_circuit_witness_generation_time_in_ms (SchnorrAccount:constructor): 1,427 (-22%)
protocol_circuit_witness_generation_time_in_ms (private-kernel-inner): 954 (-21%)
protocol_circuit_proving_time_in_ms (root-parity): 40,696 (+20%)
protocol_circuit_proving_time_in_ms (public-kernel-setup): 44,017 (+17%)
protocol_circuit_proving_time_in_ms (public-kernel-teardown): 46,222 (+17%)
protocol_circuit_proving_time_in_ms (public-kernel-tail): 181,681 (+16%)
protocol_circuit_proving_time_in_ms (root-rollup): 23,994 (+21%)

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,692
1,543
707
744 (-1%)
771

proof_construction_time_sha256_30_ms
11,685 (-1%)
3,120 (-1%)
1,405
1,440 (+1%)
1,466

proof_construction_time_sha256_100_ms
44,594
12,017
5,647
5,555
5,503

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
58.0
88.0

proof_construction_time_poseidon_hash_30_ms
1,510
415
200 (+1%)
222 (-1%)
268 (+1%)

proof_construction_time_poseidon_hash_100_ms
5,728
1,569
730
785 (+3%)
798

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

Metric
4 txs
8 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412

l1_rollup_calldata_gas
9,476
9,450

l1_rollup_execution_gas
608,012
607,986

l2_block_processing_time_in_ms
702 (+1%)
1,282

l2_block_building_time_in_ms
22,468
45,728

l2_block_rollup_simulation_time_in_ms
22,343
45,380

l2_block_public_tx_process_time_in_ms
19,175
41,994

setup_kernel_simulation_avg_ms
0.00
0.00

setup_avm_simulation_avg_ms
0.00
0.00

app_logic_kernel_simulation_avg_ms
642
650

app_logic_avm_simulation_avg_ms
1,955
2,440

teardown_kernel_simulation_avg_ms
0.00
0.00

teardown_avm_simulation_avg_ms
0.00
0.00

tail_kernel_simulation_avg_ms
0.00
0.00

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
5,875
8,468

node_database_size_in_bytes
9,502,800
12,771,408

pxe_database_size_in_bytes
7,774
15,127

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

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

batch_insert_into_append_only_tree_16_depth_ms
10.4
16.9 (-3%)
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.7
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.605
0.519 (-3%)
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.7 (-3%)
76.7 (+1%)
135 (+2%)
246
480 (+2%)
N/A

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

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.497 (-3%)
0.472 (+1%)
0.462 (+1%)
0.447
0.448 (+2%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
58.4 (-3%)
114 (+2%)
185 (+1%)
349
637 (+1%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
107
208
355
686
1,263
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.503 (-3%)
0.509 (+1%)
0.491 (+1%)
0.478
0.476 (+1%)
N/A

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

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
101

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.549 (-2%)

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
79,470
665,267

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

Benchmark results
No metrics with a significant change found.

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,721
1,547
698
752 (+1%)
776 (+1%)

proof_construction_time_sha256_30_ms
11,439
3,058
1,373
1,414
1,458

proof_construction_time_sha256_100_ms
43,878
11,804 (+1%)
5,411
5,369
5,381

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
57.0 (-2%)
86.0 (-2%)

proof_construction_time_poseidon_hash_30_ms
1,519 (-1%)
419
201 (-1%)
231 (+2%)
264 (-1%)

proof_construction_time_poseidon_hash_100_ms
5,741
1,577
727
773 (-3%)
792

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
1,412
1,412
1,412

l1_rollup_calldata_gas
9,476
9,452
9,464

l1_rollup_execution_gas
610,297
610,273
610,285

l2_block_processing_time_in_ms
699 (+2%)
1,286 (+3%)
2,450 (+2%)

l2_block_building_time_in_ms
22,543 (+3%)
46,095 (+3%)
88,299 (+5%)

l2_block_rollup_simulation_time_in_ms
22,437 (+3%)
45,721 (+3%)
87,912 (+5%)

l2_block_public_tx_process_time_in_ms
19,258 (+4%)
42,299 (+3%)
84,603 (+5%)

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
5,926 (+3%)
8,531 (+4%)

node_database_size_in_bytes
9,465,936
12,771,408

pxe_database_size_in_bytes
9,242
15,127

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

Function
time_ms ms

GasToken:set_portal
58.5

Token:constructor
98.7

FPC:constructor
62.2

GasToken:mint_public
54.0

Token:mint_public
542

Token:assert_minter_and_mint
57.7

SchnorrAccount:approve_public_authwit
33.0

FPC:prepare_fee
80.9

Token:transfer_public
59.9

FPC:pay_refund
113

Benchmarking:increment_balance
2,431

Token:_increase_public_balance
56.3

FPC:pay_refund_with_shielded_rebate
54.5

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
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.5 (+2%)
17.0 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.608 (+1%)
0.521 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.9 (+1%)
75.8 (+1%)
133
246 (+3%)
473 (+2%)
N/A

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

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.499 (+1%)
0.468 (+1%)
0.455
0.446 (+3%)
0.442 (+2%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.7 (+2%)
112 (+2%)
185 (+2%)
355 (+3%)
695 (+1%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
108
208
355
691
1,363
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.508 (+2%)
0.503 (+2%)
0.491 (+2%)
0.481 (+3%)
0.477 (+2%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
60.1 (+2%)

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
103

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.552 (+2%)

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
79,470
665,267

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

Benchmark results
Metrics with a significant change:

app_circuit_proving_time_in_ms (FPC:fee_entrypoint_public): 11,543 (+16%)
protocol_circuit_proving_time_in_ms (private-kernel-tail): 46,076 (+17%)
protocol_circuit_proving_time_in_ms (base-rollup): 87,583 (+25%)
protocol_circuit_proving_time_in_ms (root-parity): 40,139 (+19%)
protocol_circuit_proving_time_in_ms (public-kernel-teardown): 45,565 (+18%)
protocol_circuit_proving_time_in_ms (public-kernel-tail): 183,793 (+19%)
protocol_circuit_proving_time_in_ms (root-rollup): 23,115 (+18%)

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,724
1,544
701 (+1%)
754 (+2%)
769

proof_construction_time_sha256_30_ms
11,464
3,066
1,380 (+1%)
1,417
1,458

proof_construction_time_sha256_100_ms
43,912
11,800 (+1%)
5,494 (+2%)
5,496 (+2%)
5,400 (+1%)

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
58.0
88.0

proof_construction_time_poseidon_hash_30_ms
1,521
420
202
225
268

proof_construction_time_poseidon_hash_100_ms
5,745
1,575
729
792
791

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
1,412
1,412
1,412

l1_rollup_calldata_gas
9,464
9,454
9,440

l1_rollup_execution_gas
610,285
610,275
610,261

l2_block_processing_time_in_ms
694 (+1%)
1,305 (+5%)
2,476 (+3%)

l2_block_building_time_in_ms
22,507 (+3%)
45,629 (+2%)
88,328 (+5%)

l2_block_rollup_simulation_time_in_ms
22,400 (+3%)
45,259 (+2%)
87,932 (+5%)

l2_block_public_tx_process_time_in_ms
19,229 (+3%)
41,854 (+2%)
84,608 (+5%)

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

Metric
get-nullifier-index blocks
3 blocks
5 blocks

public_db_access_time_ms
0.181
N/A
N/A

node_history_sync_time_in_ms
N/A
6,027 (+5%)
8,662 (+6%)

node_database_size_in_bytes
N/A
9,502,800
12,791,888

pxe_database_size_in_bytes
N/A
9,242
15,127

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

Function
time_ms

GasToken:set_portal
57.9

Token:constructor
100

FPC:constructor
61.7

GasToken:mint_public
58.1

Token:mint_public
62.1

Token:assert_minter_and_mint
212

SchnorrAccount:approve_public_authwit
32.0

FPC:prepare_fee
84.5

Token:transfer_public
44.7

FPC:pay_refund
63.6

Benchmarking:increment_balance
2,416

Token:_increase_public_balance
58.5

FPC:pay_refund_with_shielded_rebate
55.1

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.181

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
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.4 (+1%)
17.0 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.605 (+1%)
0.521 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.7 (+1%)
76.2 (+1%)
133
248 (+4%)
473 (+2%)
N/A

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

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.497 (+1%)
0.470 (+2%)
0.455
0.449 (+3%)
0.442 (+2%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.5 (+2%)
113 (+3%)
184 (+1%)
358 (+4%)
697 (+2%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
108
208
355
691
1,363
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.506 (+2%)
0.505 (+2%)
0.487 (+1%)
0.484 (+4%)
0.479 (+2%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
60.2 (+2%)

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
103

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.553 (+2%)

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
79,470
665,267

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


Add description option to thyme

Fixes #13.
A description is particularly useful for me when I'm learning or investigating tech or doing anything particularly abstract, to capture one concrete thing to drive my scatterbrained work.

Thanks for the pull request! It looks great and is a useful feature, but I think I'd like to keep thyme small and concise as just a timer. Features beyond that scope can be added as plugins!


"views" on the Video Analytics Overview is not show the view count

https://ucsdlibrary.zendesk.com/agent/tickets/447

@gamontoya - The problem has been fixed and deployed to staging.  Could you review it?  Thanks
Here are the screen shots.
//Before the fix

//After the fix

@VivianChu Hi Vivian. I got the correct output on DMR stage. Do you need a release ticket?

@gamontoya - Thanks for reviewing.  Yes, I need a release ticket.


Completions/SignatureHelp help-text seems to be broken for bal code snippets

Description:
Completions/SignatureHelp help-text seems to be broken for bal code snippets. Please refer below;

Affected Product Version:
2.0.0-SLA3

Duplicate #29547. Hence closing


Building from GitHub zip of latest master fails

https://github.com/stnava/ANTs/blob/master/CMake/ProjectSourceVersion.cmake#L38
This line in the make flow assumes that ProjectSourceVersionVars.cmake exists if a git repo is not found. However, using GitHub's "Download ZIP" button provides user with a repo-less snapshot of master which does not include this file.

I have the same problem in #235

do you have a proposed solution?
brian
On Mon, Nov 2, 2015 at 3:37 AM, Igor Gnatenko<EMAIL_ADDRESS>wrote:

I have the same problem in #235
https://github.com/stnava/ANTs/issues/235
—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTs/issues/213#issuecomment-152952145.

Add configure() a bit earlier. I will send patch in this evening

Fixed in #236. Please close.


Revise assert_raise to handle any kind of Exception

Ruby's default rescue only handles StandardError subclasses. This is a problem when testing for exceptions that don't inherit from StandardError. The standard timeout library is one such offender: Timeout::Error inherits from Interrupt.
This is causing a test in redis-rb to fail, which is what led me here (see packagethief/redis-rb@b5dd8413203e07f9165f1d51ecec6fffa1ee17dc).
I'm not sure about packagethief@958519aaccfc4d27a574712204508571b42a732f. Prior to this change, these tests were failing due to differences in backtrace formatting (./test/fixtures/failure.rb vs. test/fixtures/failure.rb). If they weren't failing for anyone else, just ignore; it's possible that it's version specific (I tested using 1.8.7 p253).

hi can anyone rebase this patch to current version?


experimental DNSLINK support doesn't work

I have a DNS TXT entry for ggr.com:
~ ❯❯❯ dig ggr.com TXT                                                       Mon 2017-10-09 10:47:56 -0700

; <<>> DiG 9.4.2-P2 <<>> ggr.com TXT
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6017
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ggr.com.                       IN      TXT

;; ANSWER SECTION:
ggr.com.                60      IN      TXT     "ALIAS for home.ggr.com"
ggr.com.                3600    IN      TXT     "dnslink=/ipns/QmVTofH3UuafnKihbGa6whtsLaH7YyqMWiR9Pzha9xQYuK"

;; Query time: 90 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Mon Oct  9 10:47:59 2017
;; MSG SIZE  rcvd: 133

~ ❯❯❯                                                                       Mon 2017-10-09 10:47:59 -0700

Yet, when I visit https://ggr.com using Firefox 56.0 on OpenBSD 6.1-stable-amd64 with ipfs-companion 0.4.11-dev I am NOT redirected to the IPFS version of the site as I had hoped/expected I would be.
I have HSTS enabled on ggr.com. I have more than one TXT DNS entry. I wonder if one of those is causing problems. In any case, even though its an experimental feature, I figured a 100% repro example problem case might be useful.

For a little background, browser extension uses /api/v0/dns/  for dnslink lookups.
Basic troubleshooting is to check if both public and your local gateway return the same result:

https://ipfs.io/api/v0/dns/ggr.com
http://<IP_ADDRESS>:8080/api/v0/dns/ggr.com

Right now both return this error for your FQDN:
{"Message":"Could not resolve name (recursion limit exceeded).","Code":0}

It looks like a bug caused by use of IPNS path in your dnslink (most of sites use static IPFS path).
cc @Kubuxu

Based on the example:
https://github.com/ipfs/examples/tree/master/examples/websites
it seems an IPNS path in my dnslink was at least intended to work at some point. It works on the command line:
~/Downloads ❯❯❯ ipfs --debug name resolve -r ggr.com                        Mon 2017-10-09 12:09:19 -0700
14:09:29.683  INFO   cmd/ipfs: IPFS_PATH /home/scott/.ipfs main.go:301
14:09:29.687 DEBUG   cmd/ipfs: calling pre-command hooks... main.go:295
14:09:29.687 DEBUG   cmd/ipfs: executing command via API main.go:332
/ipfs/QmWqNxbUnGZzmLeyA8jMi1VeyuHpBcYDYH9WcYZY31zijk

but only if I pass in the -r, without it I get the same error as with the api call through the browser:
~/Downloads ❯❯❯ ipfs --debug name resolve ggr.com                           Mon 2017-10-09 14:10:30 -0700
14:11:28.500  INFO   cmd/ipfs: IPFS_PATH /home/scott/.ipfs main.go:301
14:11:28.500 DEBUG   cmd/ipfs: calling pre-command hooks... main.go:295
14:11:28.500 DEBUG   cmd/ipfs: executing command via API main.go:332
Error: Could not resolve name (recursion limit exceeded).

So...should I file a bug on go-ipfs do you think?

I wonder if the api doesn't recurse by default, reminds me of: https://github.com/ipfs/go-ipfs/issues/4167

Fix from https://github.com/ipfs/go-ipfs/issues/4293#issuecomment-416310364 will be introduced when  #558  is merged.


Decrease max size of docker logs, and rotation

What this PR does / why we need it:
This change decreases maximum size of a log file down to 50 Mb and limits their number to 5 so that overall disk space occupied by logs could not exceed 250 Mb per container.
Which issue this PR fixes: fixes #1394
Special notes for your reviewer:
none
Release note:
Decrease maximum size of Docker log file to 50 Mb and maximum number of files to 5

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Version 4 deinstall, reinstall to get it to work.

Describe the bug
app did not control Hue Light even that everything was looking ok
To Reproduce
Expected behavior
continuation after update
Screenshots
...
Further details

21H1
PresenceLight App Type Desktop
PresenceLight Build Store
PresenceLight Version <IP_ADDRESS>
Did you clear settings.json? (C:\Users\username\AppData\Local\Packages\37828IsaacLevin.197278F15330A.SomeValue\LocalState\settings.json
by deinstalling
ASP.NET Core version ?

To be clear, v4 does not work for your Hue lights at all?

It works after reinstalling and without using Working hours

4.0.26 has a fix for this

sounds good


Cannot stop logger printing to console in flash environments

Expected behavior
I would like to be able to turn off the logger output to console when running a flash environment. I tried logger.disable, logger.propagate on the root logger as well as all loggers used by universe and gym, as well as changing verbosity as shown in the diagnostic-agent example.
Actual behavior
Nothing makes a difference, loggers are still at level INFO and still print out everything to console.
Versions

88-Ubuntu SMP Wed Mar 8 16:34:45 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Python 3.6.0 :: Anaconda custom (64-bit)
Name: universe
Version: 0.21.4.dev0
---
Name: gym
Version: 0.7.4
---
Name: tensorflow
Version: 1.0.0
---
Name: numpy
Version: 1.12.0
---
Name: go-vncdriver
Version: 0.4.19
---
Name: Pillow
Version: 4.0.0

The most voluminous logs are from the Docker container. It's useful to see when something in the container is breaking, but once you have it working it the logging makes it impossible to use the REPL.
I checked in a proposed fix on a branch. Check out the https://github.com/openai/universe/tree/tlb-less-logging branch and run export OPENAI_REMOTE_VERBOSE=0 before running python.

This works great, thanks a lot!


Slight cleanup and documentation update in NumUtils.

mostly renaming parse_lenient() to parse_int_lenient() for readability.

I guess we need parse_hex(), parse_binary() (and anyone still using octal ? then parse_octal())
(These will simpler as they are always unsigned)


Renamed "device" to "accelerator" when the term is used to referred to TF (as opposed to "host")

The term "device" continues to refer to a TF device, such as TPU.

@swift-ci please test tensorflow

Done: https://github.com/tensorflow/swift-models/pull/13


feat(near-api-js): wallet sign-in page redirection is now optional

Motivation
Sometimes, we want the sign-in process not to redirect the whole page, but to be open in a popup window.
As mentioned in https://github.com/near/near-api-js/issues/1010
Description
She added to different methods (requestSignInLink, requestSignInLink, and completeSignInWithAccessKeyLink) to the WalletConnection, to get the needed URLs to the NEAR wallet in order to manually process them like in a popup or _blank redirection.
Checklist

[x] Read the contributing guidelines
[x] Commit messages follow the conventional commits spec
[x] Performed a self-review of the PR
[x] Added automated tests (The methods added are already tested as they are executed by the ones with a written test)
[x] Manually tested the change

@DevSlashRichie We are bringing near-api-js back to be actively maintained. This change makes total sense to me, but it needs to be rebased now (probably faster to just manually re-implement it as a lot of files have actually moved to other places). Do you have the capacity to rebase?

the idea of having methods for generating a Wallet URL without redirecting looks also reasonable to me and was implemented in https://github.com/near/near-api-js/pull/1260
I'd suggest closing this one so we don't leave it out of date

Resolved by #1260.


vacuum skips deleting currently running builds if skipRunningBuilds is true

vacuum skips deleting currently running builds if skipRunningBuilds is true (false by default).
Previously, vacuum deletes all builds regardless of their phase even if running or pending.

Just to add some context, this is regarding #604
In this commit, I added a helm config param for vacuum to skip deleting builds in pending/running phase.
To enable this feature, you would just add "skipRunningBuilds: true" under vacuum in values.yaml. Otherwise, vacuum would behave as it used to (i.e., deleting all builds) by default.
I updated vacuum_test.go as well to cover this use case when the param is set. All vacuum tests are passing.
It'd be appreciated if anyone could review this.


RFC 6555 Support (Dual Stack / Happy Eyeballs)

This PR adds a happy eyeballs algorithm and thereby provides dual stack support.
Contrary to how it sounds in the RFC, it is actually quite hard to get right.
Tested:

[x] What happens if interrupted during connect?

Try with both working setup
Result: Made a lot of connection attempts and encountered nothing out of the ordinary.

[x] IPv4 working, IPv6 working

Should establish IPv6 immediately

[x] IPv4 missing, IPv6 working

Should establish IPv6 immediately

[x] IPv4 working, IPv6 missing

Should establish IPv4 immediately

[x] IPv4 missing, IPv6 missing

Should error

[x] IPv4 broken, IPv6 working

Should establish IPv6 immediately

[x] IPv4 working, IPv6 broken

Should establish IPv4 after a brief delay

[x] IPv4 broken, IPv6 broken

Should error

[x] Above with DNS that includes multiple records
[x] Above without TLS
[x] Above with TLS
[x] Above with proxy and without TLS
[x] Above with proxy and TLS
[x] Above with Android (was not able to remove interfaces but could simulate broken interfaces)

To do:

[x] Run tests
[x] Resolve TODOs
[x] Add docstrings
[x] Create upstream PR

Notify maintainer that this is a breaking change to the API (major)

(broken means that the interface exists but packets are being discarded or rejected)

Okay, this is working well now. But I'll run the same tests on Android just to be sure.

Was merged upstream. :tada:


API docs + some fine tuning for Plugin API

What was wrong?
Plugins didn't have proper API docs yet. There were also some easy to fix glitches that this PR addresses. Notice that this is just a first step towards a full detailed plugin guide which is coming in a separate PR (#1429 )
How was it fixed?

created API docs
created TrinityBootInfo type to reduce complexity of several method signatures
Use pass instead of raise for abstract methods
Fix that ugly thing were we return None as a context

Cute Animal Picture

@pipermerriam I decided to spin out the guide into a separate PR (#1429) as writing the guide will still take a bit more time and I think we can get this in independently from the guide.


No translations showing up in progess, no inline annotations

Describe the bug

The progress window shows below:

I also saw, when I manually specified the locales folder as the automatic one crashes because there's a permission error in my project folder (Docker image mounted volume locally with root), the below message popup:

So simply said - the extension is not working for me, my translation files are as follows:

folder structure:

Extension Version

i18n Ally - latest version - just installed today
Framework/i18n package you are using

I'm using it on a Laravel-Mix project, but building it as a SPA using vue-i18n.
To Reproduce
Steps to reproduce the behavior:
Don't really have steps to reproduce it - just added the extension, selected the locales manually and error.
Device Infomation

OS: Windows 10 => WSL 2 Ubuntu 18
Version: Ubuntu 18.x
VSCode Version:  1.42.1 (using remote devserver because of WSL 2)

Extension Log
Go to View -> Output -> i18n Ally, and paste the content below. You should mask any sensitive information
🈶 Activated, v1.12.9

――――――

💼 Workspace root changed to "{PROJECT_ROOT}"
📦 Packages file "package.json" founded **SHOULDN'T THIS BE 'FOUND'?**
🕳 Packages file "pubspec.yaml" not exists
📦 Packages file "composer.json" founded **SHOULDN'T THIS BE 'FOUND'?**
🕳 Packages file "Gemfile" not exists
🌞 Enabled
🐱🏍 "Laravel" framework(s) detected, extension enabled.
🧬 Parsers "json", "yaml", "js", "json5", "ini", "po", "php" enabled.

🚀 Initializing loader "{PROJECT_ROOT}"

📂 Loading locales under {PROJECT_ROOT}/locales
	📑 Loading (en) en.json
	📑 Loading (nl) nl.json

👀 Watching change on {PROJECT_ROOT}/locales

✅ Loading finished

――――――

🐛 ERROR: TypeError: Cannot read property 'split' of undefined
TypeError: Cannot read property 'split' of undefined
    at getKeyname (.././src/utils/utils.ts:44:26)
    at new BaseNode (.././src/core/Nodes.ts:19:97)
    at new LocaleTree (.././src/core/Nodes.ts:75:9)
    at LocaleLoader.updateLocalesTree (.././src/core/loaders/LocaleLoader.ts:333:30)
    at LocaleLoader.update (.././src/core/loaders/LocaleLoader.ts:349:18)
    at LocaleLoader.init (.././src/core/loaders/LocaleLoader.ts:42:14)
    at Function.initLoader (.././src/core/Global.ts:86:9)
    at Function.update (.././src/core/Global.ts:154:13)
    at Function.updateRootPath (.././src/core/Global.ts:109:13)
    at Function.init (.././src/core/Global.ts:36:9)
    at activate (.././src/extension.ts:25:5)
🐱🚀 Update detected <change> {PROJECT_ROOT}/locales/en.json [en.json]
🐱🚀 Perfroming a full reload

📂 Loading locales under {PROJECT_ROOT}/locales
	📑 Loading (en) en.json
	📑 Loading (nl) nl.json

✅ Loading finished

――――――

🐛 ERROR: TypeError: Cannot read property 'split' of undefined
TypeError: Cannot read property 'split' of undefined
    at getKeyname (.././src/utils/utils.ts:44:26)
    at new BaseNode (.././src/core/Nodes.ts:19:97)
    at new LocaleTree (.././src/core/Nodes.ts:75:9)
    at LocaleLoader.updateLocalesTree (.././src/core/loaders/LocaleLoader.ts:333:30)
    at LocaleLoader.update (.././src/core/loaders/LocaleLoader.ts:349:18)
    at LocaleLoader.updateFile (.././src/core/loaders/LocaleLoader.ts:301:22)

Screenshots

Hi @ThaDaVos , the Laravel i18n uses a dir struture like this:
  locales
  ├── en
  |   ├── common.json
  |   ├── buttons.json
  |   ├── ...
  |   └── <filenames>.json
  ├── de-DE
  |   ├── common.json
  |   ├── buttons.json
  |   └── ...
  └── <contry-code>
      ├── common.json
      ├── buttons.json
      └── ...

If you use Vue to handle all the i18n parts only, you can disable the Laravel support by
"i18n-ally.enabledFrameworks": "vue"

Then the problem should be solved.

SHOULDN'T THIS BE 'FOUND'

Thanks for spotting the typo. WIll fix.

Thank you for the "i18n-ally.enabledFrameworks": "vue" that solved the issue -> maybe when multiple frameworks are located, ask the user which one they want to use and set this config option for the current workspace automatically?

Thank you for the suggestion, I would consider that. The original idea is that making different frameworks works together. It's just happened to be that Larevel required some specific logic to load.


None of Duo Strength's features are appearing despite being enabled

I'm using Chrome on Windows 10.

Thanks for reporting, I'm taking a look now.

@VictoryStar527 I have just published v2.0.29 which should hopefully fix this issue caused by the new Duolingo layout.
This is available now for firefox, but is still awaiting approval for chrome/opera/edge. This should only take a couple of hours.
You can check which version you have by opening the Duo Strength extension options popup, where it should be displayed in the top right.
Any more issues, let me know.
Toran


MCC to register with media proxy

The MCC should register itself with the media proxy, to avoid inter-subsystem dependencies when (if) the media proxy is moved out of the bt subsystem.

Closed as no longer relevant, as we removing the Media Proxy


:sparkles: Support calling provider plugins.

What this PR does / why we need it:
We need a way to call csmctl plugins which handle the provider specific parts (like creating node-images).
Which issue(s) this PR fixes
Fixes #4
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:

[ ] squash commits
[ ] include documentation
[ ] add unit tests

@guettli can you rebase this today? Then we can merge it. I think it is tested already and we need to continue working on this with other PRs that require this one here

Sad, that we did not merge this PR earlier. There were a lot of conflicts with the main branch now. I created a new PR: https://github.com/SovereignCloudStack/csctl/pull/97


Shout about workarounds ;-)

What does this PR change?
Cosmetical: currently, we have Workaround, workaround, work around, and HACK.
Use WORKAROUND in all caps:

make it more noticeable
align with test suite
make grepping easier

Also standardize bsc# and github# shortcuts. Sometimes it was not indicated which github repository it was all about.

Please just wait for the checks

Please just wait for the checks


Yarn boys

Converted npm commands to yarn commands
Removed package-lock.json files and added yarn.lock file
Fixed Generate.ts not working when dependencies are hoisted to the root directory
Added fp script to root package to simplify executing commands in the fp project like so:

yarn fp <command-from-fp's-package.json> (e.g. yarn fp generate)

Ready to merge after the comment is addressed.


[Thought] Using Volumes for java actions

currently Java action jars are stored in couch DB and the streamed to the JarLoader while invocation. @gorkem  is working to  refactor that approach to save load and invocation time.
One of the thought is define a m2 kind of lay out and Java Action pick the jar from it instead of streaming. It could be modelled around GlusterFS and PV.

Volumes? As in mounted file system from the host?

yes @rabbah something like that, we an use PV as well but @gorkem  felt its take a bit of time loading PV, so thinking of some way like GlusterFS kind of things.
My thoughts around proposing this idea were:

help big SI adopt OW with option that they connect their existing maven repos to the volumes
wsk create (java action) does not need to store the jar binary in couchdb instead it can point to maven GAV
when invoking action the maven GAV could be used to add that jar alone to CP and invoke it.

I need to access config file from host when calling action(Java action) by openwhisk .
But am unable to read from host(showing file not found exception).
So for that i need to add volume when docker java8action image/container bootup.
How i will add that volume info..
Please suggest..


Add mmorhun to build-service grafana dashboard owners

Build team has automation that updates reference to grafana dashboard. In order to merge updates, we need this permissions.

LGTM

/approved
/lgtm

/lgtm
/approve


feat: simplify gep-replication configuration

Create dynamic georeplications blocks in alphabetical order based on the location property.
Validate that input variable georeplications does not contain objects with duplicate location.
Add precondition to throw error when trying to configure geo-replication when SKU is not Premium.

Fixes #48

Tests pass 🎉


Application window on desktop opens with no frame.

When we run desktop application it launches without frame  which creates difficulty in navigation. Can we include frame in window? It can be fixed by modifying the browser window property of electron.
BEFORE MODIFYING BROWSER WINDOW PROPERTY

AFTER MODIFYING BROWSER WINDOW PROPERTY

It's on purpose so the children could stay concentrate on the application.
A --window option already exist to run it in a Window. See https://github.com/llaske/sugarizer/tree/dev#sugarizer-application


[Feature request] Add copy mode

Add a copy mode, like in wezterm, which allows to navigate the scrollback buffer with keyboard

I would rather have Vim mode like in Alacrity https://github.com/alacritty/alacritty/blob/master/docs/features.md.
because with Wezterm copy mode it is impossible to achieve real Vim normal mode behavior.


[ENHANCEMENT]: Changing the color of Contact Form

I think the color of Contact Form is not going with the website theme, if you allow me I can change it's color.
Here's a screenshot,

Hello @khushi-joshi-05 and @sunny0625
Please assign me this issue under GSSOC'24
Thank You

Hello @sunny0625 and @khushi-joshi-05
Please assign me this issue under GSSOC'24.


fix: Add heuristic element-to-violation matching to prevent incorrect repairs

Fix #245
Replaces #248
Depends on #250 to be merged first
This PR introduces a heuristic for matching Spoon elements to rule violations. This further increases the amount of control we have over repairs, as it decides on all elements to repair for any given rule violation before actually starting to enact repairs. Currently, the heuristic scans the Spoon model once for each rule (as we parse once for each rule), and for each element that the associated processor says that it can repair, does the following:

Finds all rule violations that intersect that element.
Finds all rule violations on the same line as that element.

When the scan is done, the matcher iterates over the rule violations and for each violation picks the first available matching Spoon element, with intersections being prioritized over same-line elements (the same-line elements are essentially a fallback mechanism for when Spoon and Sonar positions don't line up properly). Each Spoon element can only be matched to 1 violation, so the matching is 1:1.
The matching is guaranteed to be the same given the same input, as rule violations are sorted before the scan according to their position and rule type.
When Sorald then goes on to repair violations, it simply checks the best fits mapping for each element to see if there's a matching rule violation, and if there is it repairs that element.

This is really great, thanks @slarse!


WIP: [AMQ-9359] Jetty-12 conversion

TODO:

[ ] Fix web-demo compile issue with InputStreamContentProvider
[ ] Fix/Refactor JspConfigurer to use Handler.Sequence
[ ] Refactor all jetty.xml's to migrate from HandlerCollection -> Handler.Sequence

I'm already working on this for 6.2./6.3.x.

I think EE10 makes more sense. However, if we jump straight to EE10, I think  we’d need to rev to 7.x.
This change would allow us to get to Jetty 12 in 6.x minor release

I think EE10 makes more sense. However, if we jump straight to EE10, I think we’d need to rev to 7.x.
Staying with EE9 would allow us to get to Jetty 12 in 6.x minor release

Looking at it in more detail and reading https://jetty.org/docs/jetty/12/operations-guide/deploy/index.html , I don't think it's compatible after all for EE9 and EE10 when embedded.
EE10 removes some stuff from the API and i took a look at the Jetty 12 download and they actually package all 3 versions of both the API and modules separately (EE8, EE9, EE10) and each war file is isolated for deployment so you can run independently. This of course does not work for something embedded.
So we can probably stick with EE9 until 7.x. I guess if someone wants to use EE10 and with an embedded version of AMQ they could probably still do so as long as they were not using anything that relied on the EE9 stuff (any of the AMQ websockets or servlets, etc) and they would have to exclude the EE9 transitive dependencies from AMQ

So we can probably stick with EE9 until 7.x. I guess if someone wants to use EE10 and with an embedded version of AMQ they could probably still do so as long as they were not using anything that relied on the EE9 stuff (any of the AMQ websockets or servlets, etc) and they would have to exclude the EE9 transitive dependencies from AMQ

If users embed, they should be able to do EE10 runtime by excluding activemq-http and activemq-web-* modules. I believe the other EE specs in use are forward compatible b/w EE9 and EE10.


Option {json:true} not working

I am using needle for my inter-service http calls and I always use the option {json:true} but the out come seems to be not working.
{
    "name" : "biil",
    "age" : 20
}
{
    "name" : "biil",
    "age" : "20"
}

I send something like the first and get something like the second.

So the problem is that "age" should be an integer but you're getting a string?

That I am getting a string. But it was actually a placement bug (bodyparser, the one that we were using) was not parsing the "form" header and the data we were sending was for some reason under "form" and not "body". I know don't think that is is a problem with needle. The reason I did was that our http requests where going being sent by needle and on one side it was an integer and as soon as I could on the otherside it was a string

Ok I'm closing this issue then. If you find anything else feel free to open another issue.


Implementations 2/3 of LocallyConnected1D layer don't work with saved_model.save()

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
N/A
TensorFlow installed from (source or binary):
binary
TensorFlow version (use command below):
2.3.0
Python version:
3.6
Bazel version (if compiling from source):
N/A
GCC/Compiler version (if compiling from source):
N/A
CUDA/cuDNN version:
N/A
GPU model and memory:
N/A

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
ValueError: Tried to convert 'shape' to a tensor and failed. Error: None values not supported.
Describe the expected behavior
Successfully saving the model (as with implementation=1)
Standalone code to reproduce the issue
import tensorflow as tf
input = tf.keras.Input(
            shape=(10,1),
)
output = tf.keras.layers.LocallyConnected1D(
            1,
            5,
            5,
            implementation=3,  # implementation=1 does not cause error
)(input)
model = tf.keras.Model(
            inputs=input,
            outputs=output,
)
tf.saved_model.save(model, "tmp")

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

@sgdre217
I ran the code shared on tf nightly and tf 2.3, i do not see any error on nightly please find the gist here.

While I don't have access to your gist, I have independently confirmed that the error does not occur on tf nightly. Thanks!

@sgdre217
Access has been granted to the gist, please move the issue to closed status as it is resolved.

I am reopening this issue as the bug has persisted through TF version 2.5.0. Additionally, it seems like the bug is now present in tf-nightly. Here is a collab (note that it seems like the one @Saduf2019 linked has since been edited): https://colab.research.google.com/drive/1YUrOJautQiBZASDNZ97jIHlxCIsd9NHV#scrollTo=NhL5OdF3tx4z

I am able to replicate this issue please find the gist here. Thanks!

We have already two tickets and a PR https://github.com/tensorflow/tensorflow/pull/49230

@Saduf2019 , you can close the issue because we have exact same 2 tickets as @bhack mentioned. You can subscribe to these 2 tickets although so that you can get updates.
Attaching the 2 tickets: #48584 and #47689 .


GTN meeting (15th of November)

The next meeting of the GTN will take place during the next CoFest (#1082), on Thursday, the 15th of November
To accommodate different time zones and schedules, we will have 2 calls (with similar discussions) at 7am (UTC + 1) and 4pm (UTC + 1) via Hangout.
If there are any topics you wish to discuss, please comment here 😄

@Slugger70 raised this issue in #1103, talking about the tool screenshots: "Maybe we need a system where we can automatically produce them from a workflow? Naming them sensibly and so including them still? Probably a conversation for our next meeting/hackathon?"

@Slugger70 raised this issue in #1103, talking about the tool screenshots: "Maybe we need a system where we can automatically produce them from a workflow?

Just a note that with the UI refresh in Galaxy 19.01, we will have to redo all the screenshots on tutorials that have them.

@jmchilton attempted this already for the rule builder: https://github.com/galaxyproject/training-material/blob/master/topics/galaxy-data-manipulation/tutorials/upload-rules/gen_images.sh

The meeting is next week.
Proposed Agenda

Training material

What happen during the last months?

Bunch of new tutorials and some hidden
planemo for training
Embedded feedback forms

Ongoing

Biohackathon
Training Handbook
Workflow testing

Future direction

More visibility of the training material
Localization
Tags and curriculum

Community

What happen during the last months?

GOBLET
Instructor meeting
Tutorial of the Month
TIaaS
Advertisement card

Ongoing

Instructor community

Future direction

Next CoFest and meeting: 21st of February, 2019

GTN meeting
attendees
Morning Session

Bérénice @bebatut BB
Saskia @shiltemann SH
Helena @erasche HR
Simon @slugger70 SG
Anna @annasyme AS
Björn @bgruening BG
Peter @pvanheus PvH

Afternoon Session

Bérénice @bebatut BB
Helena @erasche HR
Saskia @shiltemann SH
Nicola @nsoranzo
John @jmchilton
Fotis  @fpsom FP
Gildas @lecorguille
Delphine @Delphine-L
Peter @pvanheus
Subina @subinamehta SM
Dan @blankenberg
Pratik
Frederik @frederikcoppens

Training material
Introduction

SG/AS present their training that they've been doing, "hybrid training session", anna sits in a room and talks to a camera, everyone else spreads across the country. did RNA seq, genome assembly, spades, variant calling, metagenomics with GTN tutorial with soil metagenomics. It all went well! At one stage, 80 jobs running, 16 in queue. Across Aus + Malaysia.
AS: if on larger scale could work as a "webinar", realtime? Roughly 100 people for each one.
SG: to begin with they asked people to be local facilitators for things. trained them all how it works /  how it'll be run. flew them all to melbourne, even malaysian coordinator. Explained how it'll all work, train the trainer kind of thing. Everyone signed up for event brite thing, listed all of the local places they could do training,local facilitator handles computer/wifi issues and any issues. Simon watched the monitoring. There was a google doc where anyone could ask questions. No one need to sign up. AS: google doc can come back to questions and write something nice after the fact. People could ask loads of questions and everyone could respond inline, separate threads where people could respond and discuss.

In the past months

We've begun to write a training handbook to help people start to give training s and use the materials, we wrote checklists and recommendations. What simon did would fit really well there and we'd love to have their trainer story/philosphies. How they give their training. So many differences in the way of giving trainings, soit's great that we document this and help each other/insturctors think critically about how they give trainings and what is a good fit for them/their material/their style. @slugger70 @AnnaSyme

SM: We use jetstream for this, is it possible to use usegalaxy.eu for this in a similar way with their own accounts? Our jetstream instance occasionally crashes with >100 participants
BB: We have TIaaS
HR: EU is happy to support this, if you have extra space on jetstream you can just attach compute resources there to usegalaxy.eu and help process training jobs.
SM: Can we write a tour for a workflow?
HR/JC/BB: Bjoern will support this, we can find someone to help. HR: @polkhe can maybe test this?
Pratik: We need to get all workflows onto EU and working.

@pvanheus shared https://twitter.com/H3ABioNet/status/1060484271863988224 so EU has a goal for their next training
SG: Enis/Nuwan finishing work on Pulsar stuff, we can leverage this + possibly also prevention of re-running old jobs, especially for a training of this scale.
Will SG/AS migrate their training materials? SG/AS: will take some time. SH: We can organise a cofest around this? Can get some help to migrate materials?
How can we aggregate the feedback and maybe address some of it? Maybe some statistics over it, summarize this in a nice way for people. Do y'all think this is useful?

SG; we've discussed adding the form in melbourne, getting people to do it after isn't great. Comms people still love paper so it's an issue.

We now have automatic translation.

There are some words which should never be translated such as "reads" and "mapping".
We're testing that now but it's available, you should try it if you speak another language.
SG: DaveC's comments from GOBLET, next one will be in Indonesia with Malaysians/Japanese groups, automatic translation would be incredibly helpful for them.
PvH: would be interesting for his context to do Arabic.
BB: A couple of japanese colleagues here at BioHackathon checked some, the translations were a bit rough. So we need to ensure that there is really good english and simplified sentences. Just take some tutorials and go through and see if we can improve the english at all. If there are terms, we should start a dictionary that should never be translated.
HR: We have google analytics data since a month thanks to @martenson, maybe this could let us prioritize.
BB: Japanese group will maintain some manually, they have a couple they want a HQ translation, so we can let them be manually curated if up to date. If they become three months out of date we will go back to automatic translations for those tutorials.

Ongoing

In Biohackathon

BB: Writing a proposal with Carpentries people to combine our trainings and do the EU wide training.

Workflow testing

BB: Testing abunch on EU, to guaruntee that things are rnuning.
HR: 13/16 are passing, AU can just use our jenkins if they like
HR: hopefully have some planemo improvements soon that will make this more reliable

Fairness assessment of training materials:

BB: Group in BH that's analysing "how can you assess fairness of materials". Some things are outside our control, (HR: or are possibly misassesed)

We've implemented a Search via TeSS (for a part of the fairness assessment)

PvH: How does TeSS parse it? HR: json-ld schema.

Future Directions

More visibility of the training material

BB: Webhook to display training materials

Tags and Curriculum

BB: What are best next steps. In the metadata could have next steps.
SG: Filter by tag, maybe could see trainings across categories, maybe from start to finish of analysis.
BB: If you want to import things, then we can import + hide them. If tools aren't on TS, we hide by default.

More instructor visibility

Training events will be shown on both hub + training materials (+EU)
GTN is more at level of institution, we want to show a more personal directory and give more visibility to the awesome instructors that make up our community
We’re doing a TOTM now which will be highlighted on EU + Org

More instructor support (blog post framework, events feed on home page)

BB: Office hours program where experienced trainers help new people who show up/ask questions.
FP: In the carpentries it’s a good time to exchange ideas over best practices, things we encounter.
FP: In carpentries, we ask every single break “what did you like in the past hours / what didn’t you like”, asking for feedback. Helps identify weaknesses in either myself or in the material, maybe didn’t teach something well, or the material is lacking in that point. If the training ends on a high note, additionally biases the feedback.
SG: Train the trainers at GCC?
BB: Give more visibility like having instructor directory, but GTN is more for institutions but not individuals. With Dave we'll work on having a real list of instructors and thanking them and highlighting them.
BB: Also will embed an event list (@erasche/@tnabtaf)
PvH: can help with onboarding / growing the GTN community
SG: Repeat what SH/HR did in Melbourne, here's how to write materials/develop tools/etc, helped people get over the energy of activatiomn boundary.
BB: Idea of discussion meeting somewhat, to help new people answer some questions.
PvH: Carpentries has a mentoring programme.
BB: This takes quite some time committment, ours hopefully is less work for the trainers. BB meets with her mentees every two weeks regarding mentoring. For us, maybe we don't have enough time on our side and cannot ask GTN members for this. Maybe in the future if our community continues to grow

Misc

Gildas: Any recommendation to split the wf / multiple tours for different parts of workflow?
BB: one tour : one workflow
DL: I have been ask in conferences if there were any places were people could find or share workflows for specific subject, maybe we could link a repo of workflows linked to a specific subject, without having the whole tutorial for each of them ?

BG: our idea was to use this repo and similar once for this: https://github.com/galaxyproject/iwc

Community
Last Months

GOBLET

BB: Not much feedback on GOBLET yet, hopefully we'll hear at next meeting. Maybe @tnabtaf can write a nice report from GOBLET.

TIaaS

BB: it's working well
SG: We want to build a community of trainers, it could be good to leverage this, it would be nice to be informed of trainings run on our server.

Advertisment Card:

BB: We made a nice card! No stickers yet.

Next CoFest:

Thursday, 21st of Febuary

Closing Notes

We will move this slot to at least 1 hour later (could move 2)
DB: Everything is great

@erasche Thank you very much for taking the notes/minutes yesterday

Thanks @erasche for the notes and for everyone for their participation!


ENH: accept tf.data.Dataset inputs

Partially addresses #160 by enabling direct tf.data.Dataset inputs.
This mainly enables the use case where a user has an existing Dataset and Model and would like to use GridSearch or something on it, but most of the rest of the SciKeras and Sklearn features will be unavailable including:

Encoding/decoding of labels to allow strings, obj, etc.
Ability to dynamically adapt Model inputs/outputs to data

And this requires using BaseWrapper directly, or alternatively subclassing KerasClassifier or KerasRegressor to disable the transformers.

Codecov Report

Merging #166 (4423dd9) into master (08f8239) will decrease coverage by 0.44%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #166      +/-   ##
==========================================
- Coverage   99.55%   99.11%   -0.45%
==========================================
  Files           6        5       -1
  Lines         678      678
==========================================
- Hits          675      672       -3
- Misses          3        6       +3

Impacted Files
Coverage Δ

scikeras/wrappers.py
99.45% <100.00%> (+0.01%)
:arrow_up:

scikeras/_saving_utils.py
96.20% <0.00%> (-3.80%)
:arrow_down:

scikeras/__init__.py

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 08f8239...dacbdd0. Read the comment docs.

Codecov Report

Merging #166 (4423dd9) into master (08f8239) will decrease coverage by 0.44%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #166      +/-   ##
==========================================
- Coverage   99.55%   99.11%   -0.45%
==========================================
  Files           6        5       -1
  Lines         678      678
==========================================
- Hits          675      672       -3
- Misses          3        6       +3

Impacted Files
Coverage Δ

scikeras/wrappers.py
99.45% <100.00%> (+0.01%)
:arrow_up:

scikeras/_saving_utils.py
96.20% <0.00%> (-3.80%)
:arrow_down:

scikeras/__init__.py

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 08f8239...dacbdd0. Read the comment docs.


OKV-<IP_ADDRESS>: There was an error while executing VBoxManage, a CLI used by Vagrant

Command
    vagrant up

Virtualization has to be enabled for the machine
Ref : https://github.com/hashicorp/vagrant/issues/10056

Virtualization was enabled , which didn't resolved this  issue....
issue persist


chore: deprecate -h, only -f needed for list-devices

- What I did

deprecated -h, --host (also hide both of these)
made it so -t, and -h are not needed to --list-devices
with -t only list-devices for that daemon, without -t, list for all devices.

- How I did it
- How to verify it

Tested -h and --host for breaking changes, still negotiates with rv correctly.
List devices works with -t, only listing devices for -t
List devices work without -t, listing devices as devicename@deviceatsign

This approach maintains compatibility with the notes from #968

- Description for the changelog
chore: deprecate -h, only -f needed for list-devices

Additional changes

minus_r_flag e2e_all test:

base command still uses -h otherwise we have to do a bunch of refactoring of the tests to change the base command based on client version
Test 1 : --host regression test
Test 2 : -r overrides -h value (made -h value a non-activated atSign, so it will fail if the -h value is used)

Updated noports core to 6.0.7 and updated changelog
Updated sshnoports to 5.2.0 (since I need a cut-off version for when this test is allowed to run)


Python Env

Hello,
I test to dockerize your server in docker, but i have a problem to pip install cmake.
Can you provide me your version of python and pip ?
Thanks

Hi!
I see that I am using a quite older version of pip. Here is the version number.
Python 3.6.0
pip 9.0.1


Make it possible to configure containerSecurityContext for init-containers

Is your feature request related to a problem? Please describe.
I need to be able to define securityContainerContext on the init container to be able to start the grafana-operator on my current cluster due to psp rules that we have globally defined.
Describe the solution you'd like
Use the same containerSecurityContext on the init container that you get from grafana.spec.deployment.containerSecurityContext
kind: Grafana
metadata:
  name: grafana
spec:
  deployment:
    containerSecurityContext:
      allowPrivilegeEscalation: false

to the init container.
Describe alternatives you've considered
Instead of using the same containerSecurityContext we could define a seperate one for the init container. Instead of using additional special config for initContainers directly under grafana.spec, like we do for grafana.spec.InitResources I would suggest creating a grafana.sepc.initContainers and store all initContainer specific config under it.
kind: Grafana
metadata:
  name: grafana
spec:
  initContainer:
    InitResources:
      requests:
        memory: "64Mi"
        cpu: "250m"
    initContainerSecurityContext:
      allowPrivilegeEscalation: false
  deployment:
    containerSecurityContext:
      allowPrivilegeEscalation: false

We could still keep grafana.spec.InitResources to be backwards compatible and defining it would prioritize it over  grafana.spec.initContainer.InitResources. But when releasing 4.0 I would suggest removing grafana.spec.InitResources to only have one place to define initResources.
Additional context
When trying to start the grafana-operator on my current cluster I get the following error:
psp-allow-privilege-escalation-container] Privilege escalation container is not allowed: grafana-plugins-init

Existing solutions
N/A

Automation should have closed this, resolved through #373 :+1:


Sensor not working on AsyncSceneCollider

Hi, seems like Sensor has no effect on AsyncSceneCollider.
Objects collide with it and cannot pass through it.
    commands.spawn((
      scene.clone(),
      RigidBody::Static,
      Sensor,
      AsyncSceneCollider::new(Some(ComputedCollider::TriMesh))
        .with_layers_for_name("Sensor", CollisionLayers::new([Layer::One], [Layer::Two])),
    ));

I've also tried using it as parent/child collider -
With Async as parent - both colliders created, but Async still won't let objects through:
    RigidBody::Static,
    AsyncSceneCollider::new(Some(ComputedCollider::TriMesh))
      .with_layers_for_name("Sensor", CollisionLayers::new([Layer::One], [Layer::Two])),
    Sensor,
    ))
    .with_children(|children| {
    children.spawn((
        Sensor,
        Collider::ball(1.0),
        Transform::from_xyz(0., 0., 0.),
        ));
    });

With Async as child - Async not created, only parent is created:
    RigidBody::Static,
    Collider::ball(1.0),
    Sensor,
    ))
    .with_children(|children| {
    children.spawn((
        AsyncSceneCollider::new(Some(ComputedCollider::TriMesh))
          .with_layers_for_name("Sensor", CollisionLayers::new([Layer::One], [Layer::Two]))
        ));
    });

Also tried including AsyncSceneCollider in a Compound collider:
    Collider::compound(vec![
        (
        Position::from(Vec3::new(0., 0., 0.)),
        Rotation::default(),
        AsyncSceneCollider::new(Some(ComputedCollider::TriMesh)).with_layers_for_name("innerCol", CollisionLayers::new([Layer::Pan], [Layer::Sheep]))
        )
    ]),

That throws an error:
| |_____^ the trait `From<bevy_xpbd_3d::components::AsyncSceneCollider>` is not implemented for `bevy_xpbd_3d::components::Collider`

294 |     pub fn compound(
    |            -------- required by a bound in this associated function
...
298 |             impl Into<Collider>,
    |                  ^^^^^^^^^^^^^^ required by this bound in `Collider::compound`

Thank you for a great crate!!!

I'll just add that the scene is already loaded before the AsyncSceneCollider is created, in an earlier game state, so it doesn't really have to wait for it.
(The only reason I'm using the async method is because creating the collider from GltfMesh was complicated. It worked, managed to get the Mesh and generate, but could not scale it for some reason..)

@dror-g FYI https://github.com/Jondolf/bevy_xpbd/pull/375 should fix the scaling issues at least

Amazing! These bevy-native helper functions really make bevy_xpbd a great choice for bevy physics, and I think spending time on them is well worth it.
Please feel free to close the issue, I don't know when I'll get a chance to confirm this myself..
Thank you!


reactive props destructure with default values doesn't work

Environment

Operating System: Linux
Node Version:     v18.20.3
Nuxt Version:     3.13.1
CLI Version:      3.13.1
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      compatibilityDate, devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-t1vjvm?file=components%2Fcomp.vue,app.vue
Describe the bug
Defining props with default value using the new vue 3.5 props destructure is compiled differently in nuxt.
In the vue playground (vue3.5.1, SSR):

/* Analyzed bindings: {
  "foo": "props"
} */
import { defineComponent as _defineComponent } from 'vue'

const __sfc__ = /*@__PURE__*/_defineComponent({
  __name: 'Comp',
  props: {
    foo: { type: Boolean, required: false, default: true }
  },
  setup(__props, { expose: __expose }) {
  __expose();

const __returned__ = {  }
Object.defineProperty(__returned__, '__isScriptSetup', { enumerable: false, value: true })
return __returned__
}

});
import { ssrInterpolate as _ssrInterpolate } from "vue/server-renderer"
function ssrRender(_ctx, _push, _parent, _attrs, $props, $setup, $data, $options) {
  _push(`${_ssrInterpolate($props.foo)}`)
}
__sfc__.ssrRender = ssrRender
__sfc__.__file = "src/Comp.vue"
export default __sfc__

In Nuxt:

import { createHotContext as __vite__createHotContext } from "/_nuxt/@vite/client";import.meta.hot = __vite__createHotContext("/components/comp.vue");import { defineComponent as _defineComponent } from "/_nuxt/node_modules/vue/dist/vue.runtime.esm-bundler.js?v=8fea97c8";
const _sfc_main = /* @__PURE__ */ _defineComponent({
  __name: "comp",
  props: {
    foo: { type: Boolean, required: false }
  },
  setup(__props, { expose: __expose }) {
    __expose();
    const { foo = true } = __props;
    const __returned__ = { foo };
    Object.defineProperty(__returned__, "__isScriptSetup", { enumerable: false, value: true });
    return __returned__;
  }
});
import { toDisplayString as _toDisplayString } from "/_nuxt/node_modules/vue/dist/vue.runtime.esm-bundler.js?v=8fea97c8";
function _sfc_render(_ctx, _cache, $props, $setup, $data, $options) {
  return _toDisplayString($setup.foo);
}
_sfc_main.__hmrId = "ea5b442f";
typeof __VUE_HMR_RUNTIME__ !== "undefined" && __VUE_HMR_RUNTIME__.createRecord(_sfc_main.__hmrId, _sfc_main);
import.meta.hot.accept((mod) => {
  if (!mod) return;
  const { default: updated, _rerender_only } = mod;
  if (_rerender_only) {
    __VUE_HMR_RUNTIME__.rerender(updated.__hmrId, updated.render);
  } else {
    __VUE_HMR_RUNTIME__.reload(updated.__hmrId, updated);
  }
});
import _export_sfc from "/_nuxt/@id/__x00__plugin-vue:export-helper";
export default /* @__PURE__ */ _export_sfc(_sfc_main, [["render", _sfc_render], ["__file", "/home/projects/github-t1vjvm/components/comp.vue"]]);

Additional context
No response
Logs
No response

For now you can enable with:
export default defineNuxtConfig({
  vue: {
    propsDestructure: true
  },
})

wish, I checked this earlier.  spent hours trying to figure out what I was missing
Thank you

Sorry about that!

There's nothing to be sorry about. You guys are doing an amazing job, taking into account the complexity you are trying to hide from users and features to uncover.
I am constantly assessing and switching between various UI frameworks for my clients, and the Vue/Nuxt ecosystem is a whole different level.
That feature was just released in Vue, and same day, you made it available in nuxt. There must be some teething issues at that rate.
Thank you @danielroe and whole team once again

For now you can enable with:
export default defineNuxtConfig({
  vue: {
    propsDestructure: true
  },
})

Thankyou sooooo much. I was struggling since past two days because many of my website functionality was depended on this.

I stil have the error: pluginContext.vueCompilerOptions.plugins is not iterable

You might be missing the feature keys. I had to have the following to get it to work.
export default defineNuxtConfig({
  vue: {
    features: {
      propsDestructure: true,
    }
  }
})

For now you can enable with:
export default defineNuxtConfig({
  vue: {
    propsDestructure: true
  },
})

@danielroe Thankyou sooooo much. I was struggling since past two days because many of my website functionality was depended on this.

I have this enabled and also still get the pluginContext.vueCompilerOptions.plugins is not iterable error with<EMAIL_ADDRESS>
Operating System: Darwin
Node Version:     v20.17.0
Nuxt Version:     3.13.1
CLI Version:      3.13.2
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>

@adamdehaven would you raise that as a separate issue? 🙏

@danielroe https://github.com/nuxt/nuxt/issues/29144
Admittedly this is likely the most vague issue I've ever created 🫣 I wasn't sure what context to provide lol


Wrong image size when 'Zoom view' mode is activated

Describe the bug
When repeatedly using the 'Zoom view' button to focus the image, the image size might change, which might lead the user to readjust the zoom in the lens, only to discover then the image is too big/small at scan time (when, it appears, the image is set back at the correct size again). As a temporary workaround you might enable/disable the 'Zom vide' mode until the image comes back to the right size.
To Reproduce
Steps to reproduce the behavior:

Load a film in the scanner
Click on 'Zoom view' several times, until the image while it is activated is displayed at an unexpected size.

Expected behavior
Image is displayed at the required zoom level when 'Zoom view' is activates
Screenshots
NA at this moment
Desktop (please complete the following information):

OS: Raspberry Pi OS (Bullseye)
Version: 1.10.58

Additional context

This issue should be fixed with 1.10.63. To be closed if no new reports arrive in the coming weeks.


HTTPS/2.0 + TLS

Here's a tutorial for Digital Ocean https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04


[BUG] Bot walking speed slowing down when telegram enabled

Expected Behavior

Actual Behavior

Bot is slowing down when telegram is enabled.
Your FULL config.json (remove your username, password, gmapkey and any other private info)

Output when issue occurred

Steps to Reproduce

Start the bot with telegram enabled.
Other Information
OS: centos

Branch: dev

Git Commit:

Python Version:

Any other relevant files/configs (eg: path files)

https://github.com/PokemonGoF/PokemonGo-Bot/issues/4902

Title of the issue is incomplete but cannot change it.

Yes, you can. Look at the right of the title.

same here, when i set "enable_social": true,
bot slow down and failed to connect to broker.pikabot.org:1883
this is log after checking with proxifier

Please post your config.

i'll fix

Don't know if the bot is multi threaded but I suppose this could be the fix?

can someone give me a link to the telegram feature?
thank you!

Thank you @askovpen
What kind of link are you looking for @avexus ?


Changes from debugging session

This PR includes all the changes from the yesterday's debugging session.

Looks good :+1:


openrouter.ai support

It has variety of models (150+) starting from $0.015 so it's really affordable.
Also any plan to open your discord server ? Cuz I'm in love with you perfect it's soo soo good ❤

+1 👍
Also in need of Openrouter.ai support.
Thanks.

Implementing generic OpenAI API-style support would be ideal, particularly when we have the capability to modify the base URL. This approach would provide flexibility and compatibility with various AI inference providers.

using  lite llm  would be the ideal solution


(3.3.4) FormBuilderDateTimePicker ignoring initialDate

Hi Danvick,
Noticed a possible breaking change.
Passing initialDate: DateTime.tryParse("20000101"), for example, in the constructor has no effect. The date picker still open at current date.
And if one passes a lastDate that is before today, then one gets an
!initialDate.isAfter(lastDate) assertion error from within date_picker.dart
The problem seems to be here in form_builder_date_time_picker.dart
Future<DateTime> _showDatePicker(
     ....
      return showDatePicker(
          context: context,
          ....
          initialDate: currentValue ?? DateTime.now(),
          firstDate: widget.firstDate ?? DateTime(1900),
          lastDate: widget.lastDate ?? DateTime(2100));
  }

I think initialDate: (currentValue ?? widget.initialDate) ?? DateTime.now() is what's required. But you can confirm.
Thanks
Abhinav.

Thank you for bringing this to our attention.

Hi,
The initialValue also not working in FormBuilderDateTimePicker. The value set in initialValue i.e {'date':DateTime.utc(2010,1,1)} were successfully assigned to the attribute (it is not null) but not printed in the field, it just blank.

Looks like the culprit is that the value of the text editing controller is not being set on intiState.
Adding the following got me back up and running:
In initState(), right after
_textFieldController = widget.controller ?? TextEditingController();
_widget.initialValue == null ? "" :_
**widget.format == null ? DateFormat("EEEE, MMMM d, yyyy 'at' h:mma").format(
    widget.initialValue) :
widget.format.format(widget.initialValue));**

I'm sure there is a more elegant way to do this - also, I have a check box in my app to show or hide the date, that logic seems to be not working at the moment.

This bug has come sometime after 3.0.1. Hence I am hoping it gets fixed here itself.

Hi @abhinavc,
Kindly confirm that this issue is fixed as of v3.4.0.
Feel free to reopen the issue if not.

Hi Danvick,
Tried 3.4.1 and it seems the issue still remains.
firstDate is honored. lastDate is also honored, though specifying one can lead to an assertion
error because initialDate still seems to be set to today's date.


Update julia ci versions and compat

Codecov Report

Merging #9 (01cd877) into main (7fb09ec) will increase coverage by 0.75%.
The diff coverage is n/a.

:exclamation: Current head 01cd877 differs from pull request most recent head 22099fd. Consider uploading reports for the commit 22099fd to get more accurate results

@@            Coverage Diff             @@
##             main       #9      +/-   ##
==========================================
+ Coverage   37.85%   38.60%   +0.75%
==========================================
  Files           4        4
  Lines         177      158      -19
==========================================
- Hits           67       61       -6
+ Misses        110       97      -13

Impacted Files
Coverage Δ

src/utils.jl
64.86% <0.00%> (-2.64%)
:arrow_down:

src/benchmarks.jl
0.00% <0.00%> (ø)

src/allocations.jl
48.00% <0.00%> (+1.57%)
:arrow_up:

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 7fb09ec...22099fd. Read the comment docs.


[BEAM-13127] [Playground] Implement TCP listener

TCP listener which binds with our gRPC server. This listener is wanted for easy testing of server endpoints. The choice type of listener (HTTP or TCP) depends on the value of the environment variable ("protocolTypeKey").

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

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

LGTM


Django debug toolbar 1.4 does not support django 1.7

Can please drop backwards compatibility for django 1.7 on django debug toolbar 1.4, because the test did not really covered that django version because on travis logs it was installing django 1.8 instead

So these tests should be fail instead of succeeding.

Unfortunately there's no way we can change the 1.4 release retroactively. This problem has been solved in subsequent releases.
If I missed something, please clarify what changes you would like to make.

The current, maintained version of django-debug-toolbar is 1.6, the probability that anything will happen on 1.4.x is really small (except if someone does the work of actually fixing issues and convincing me that the fixes are worth it).
Or as Aymeric said maybe I misunderstood something. Feel free to reopen the issue in this case.
Thanks!

There are no maintenance releases for the Debug Toolbar. Releases are made in linear order, always from master.


Add passing a Writer to the CLI logger.

Test branch.

@opudrovs I happened to fix this in #3027
would you mind reviewing it instead?
We are fixing it with the same logic.

@chanwit approved. Have not tested it yet but it looks like it should work. 🙂

Closed as a test PR.


RuntimeError: Error building extension 'fused_adam'[BUG]

File "/home/nbicc/data/anaconda3/envs/visualglm/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 2112, in _run_ninja_build
raise RuntimeError(message) from e
RuntimeError: Error building extension 'fused_adam'

怎么解决呢

Hi @chenchen333-dev - can you please share your deepspeed version, torch version and cuda version, as well as the command you are running and the full error message?  Thanks.

hi, the repo build different deepspeed wheels.

Hi @AlongWY - thanks, but some users will need to either build wheels locally or use from a known PyPI index.
@chenchen333-dev if you have a chance, please let us know more about your environment.

Hi, @loadams , I got the same issue as @chenchen333-dev .
When I run finetune_qlora_single_gpu.sh command, I got this error:
RuntimeError: Error building extension 'fused_adam'

This is my environment info:
[2024-03-26 12:28:08,970] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
 [WARNING]  Please specify the CUTLASS repo directory as environment variable $CUTLASS_PATH
 [WARNING]  using untested triton version (2.1.0), only 1.0.0 is known to be compatible
--------------------------------------------------
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
async_io ............... [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
cpu_lion ............... [NO] ....... [OKAY]
 [WARNING]  Please specify the CUTLASS repo directory as environment variable $CUTLASS_PATH
evoformer_attn ......... [NO] ....... [NO]
fused_lamb ............. [NO] ....... [OKAY]
fused_lion ............. [NO] ....... [OKAY]
inference_core_ops ..... [NO] ....... [OKAY]
cutlass_ops ............ [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
ragged_device_ops ...... [NO] ....... [OKAY]
ragged_ops ............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
 [WARNING]  using untested triton version (2.1.0), only 1.0.0 is known to be compatible
sparse_attn ............ [NO] ....... [NO]
spatial_inference ...... [NO] ....... [OKAY]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ............... ['/home/ubuntu/miniconda3/envs/glm/lib/python3.10/site-packages/torch']
torch version .................... 1.13.1+cu117
deepspeed install path ........... ['/home/ubuntu/miniconda3/envs/glm/lib/python3.10/site-packages/deepspeed']
deepspeed info ................... 0.14.1+0529eac, 0529eac, master
torch cuda version ............... 11.7
torch hip version ................ None
nvcc version ..................... 11.5
deepspeed wheel compiled w. ...... torch 1.13, cuda 11.7
shared memory (/dev/shm) size .... 47.15 GB

Any help? Thanks !

And I also notice that there are many ops that are compatible with my env but they are not installed. So how can I install these ops ?

the page say you can use to install the ops:
DS_BUILD_OPS=1 pip install deepspeed --global-option="build_ext" --global-option="-j8"

the page say you can use to install the ops:
DS_BUILD_OPS=1 DS_BUILD_EVOFORMER_ATTN=0 DS_BUILD_SPARSE_ATTN=0 pip install deepspeed --global-option="build_ext" --global-option="-j8"

I uninstall deepspped, and then use the given command DS_BUILD_OPS=1 DS_BUILD_EVOFORMER_ATTN=0 DS_BUILD_SPARSE_ATTN=0 pip install deepspeed --global-option="build_ext" --global-option="-j8" to install deepspeed. Sadly, it doesn't work for me, there is nothing changed about the results of ds_report.

Hi @zzyzeyuan - you do not need to pre-compile the ops, if they are used/needed in your model, DeepSpeed will JIT compile them, more info here.  Typically you only need to do this if you are building an instance of the wheel that you need to distribute across a number of nodes.

Closing this issue since we are off the original topic.  @chenchen333-dev - if you are still hitting this issue, please open a new issue and link this one.