Ag/proving queue perf

Please read contributing guidelines and remove this line.

Benchmark results
Metrics with a significant change:

protocol_circuit_simulation_time_in_ms (private-kernel-reset-tiny): 458 (+50%)
protocol_circuit_simulation_time_in_ms (base-rollup): 2,766 (-20%)
protocol_circuit_simulation_time_in_ms (public-kernel-tail): 557 (-36%)
protocol_circuit_simulation_time_in_ms (private-kernel-reset-small): 468 (+52%)
avm_simulation_time_ms (Token:transfer_public): 20.3 (-38%)
avm_simulation_time_ms (Benchmarking:increment_balance): 940 (-22%)
protocol_circuit_witness_generation_time_in_ms (private-kernel-reset-tiny): 887 (+22%)
l2_block_building_time_in_ms (4): 9,050 (-21%)
l2_block_building_time_in_ms (8): 17,518 (-21%)
l2_block_building_time_in_ms (16): 35,549 (-20%)
l2_block_rollup_simulation_time_in_ms (4): 9,049 (-21%)
l2_block_rollup_simulation_time_in_ms (8): 17,518 (-21%)
l2_block_rollup_simulation_time_in_ms (16): 35,549 (-20%)
l2_block_public_tx_process_time_in_ms (4): 7,658 (-21%)
l2_block_public_tx_process_time_in_ms (8): 15,995 (-22%)
l2_block_public_tx_process_time_in_ms (16): 33,998 (-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,749
1,556 (-1%)
709
778 (+4%)
779 (+1%)

proof_construction_time_sha256_30_ms
11,439
3,073
1,370 (-1%)
1,411 (-2%)
1,481 (+2%)

proof_construction_time_sha256_100_ms
44,102
11,785
5,407 (-1%)
5,441
5,647 (-2%)

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
58.0 (+2%)
87.0

proof_construction_time_poseidon_hash_30_ms
1,525
420
202
226
266 (-1%)

proof_construction_time_poseidon_hash_100_ms
5,639
1,512
674
734 (-1%)
744

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

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
4,356
7,876
14,884

l1_rollup_calldata_gas
50,280
92,970
178,168

l1_rollup_execution_gas
1,396,531
2,130,117
3,915,371

l2_block_processing_time_in_ms
248 (-2%)
445
824

l2_block_building_time_in_ms
:warning: 9,050 (-21%)
:warning: 17,518 (-21%)
:warning: 35,549 (-20%)

l2_block_rollup_simulation_time_in_ms
:warning: 9,049 (-21%)
:warning: 17,518 (-21%)
:warning: 35,549 (-20%)

l2_block_public_tx_process_time_in_ms
:warning: 7,658 (-21%)
:warning: 15,995 (-22%)
:warning: 33,998 (-20%)

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
2,940
3,807 (-2%)

node_database_size_in_bytes
12,623,952
16,715,856

pxe_database_size_in_bytes
16,254
26,813

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

Circuit
simulation_time_in_ms
witness_generation_time_in_ms
input_size_in_bytes
output_size_in_bytes
proving_time_in_ms

private-kernel-init
89.4 (+1%)
411 (+4%)
21,755
44,860
N/A

private-kernel-inner
168 (+1%)
702
72,566
45,007
N/A

private-kernel-reset-tiny
:warning: 458 (+50%)
:warning: 887 (+22%)
65,675
44,846
N/A

private-kernel-tail
196 (+20%)
157 (+16%)
50,686
52,257
N/A

base-parity
5.71 (+2%)
N/A
160
96.0
N/A

root-parity
35.6 (+1%)
N/A
73,948
96.0
N/A

base-rollup
:warning: 2,766 (-20%)
N/A
189,136
664
N/A

block-root-rollup
41.6
N/A
58,205
2,448
N/A

public-kernel-setup
83.7
N/A
105,085
71,222
N/A

public-kernel-app-logic
95.8 (+1%)
N/A
104,911
71,222
N/A

public-kernel-tail
:warning: 557 (-36%)
N/A
410,534 (+5%)
16,414
N/A

private-kernel-reset-small
:warning: 468 (+52%)
N/A
66,341
45,629
N/A

private-kernel-tail-to-public
1,362 (-1%)
646 (+5%)
460,796 (+1%)
1,825
N/A

public-kernel-teardown
82.7
N/A
105,349
71,222
N/A

merge-rollup
20.6 (-2%)
N/A
38,174
664
N/A

undefined
N/A
N/A
N/A
N/A
78,104 (-1%)

Stats on running time collected for app circuits

Function
input_size_in_bytes
output_size_in_bytes
witness_generation_time_in_ms

ContractClassRegisterer:register
1,344
11,731
343

ContractInstanceDeployer:deploy
1,408
11,731
18.3

MultiCallEntrypoint:entrypoint
1,920
11,731
406

FeeJuice:deploy
1,376
11,731
394 (+2%)

SchnorrAccount:constructor
1,312
11,731
74.6 (-1%)

SchnorrAccount:entrypoint
2,304
11,731
401 (+1%)

Token:privately_mint_private_note
1,280
11,731
108 (+4%)

FPC:fee_entrypoint_public
1,344
11,731
27.7 (-6%)

Token:transfer
1,312
11,731
229 (-3%)

Benchmarking:create_note
1,344
11,731
89.8 (+2%)

SchnorrAccount:verify_private_authwit
1,280
11,731
27.6

Token:unshield
1,376
11,731
536 (+2%)

FPC:fee_entrypoint_private
1,376
11,731
714 (+1%)

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

Function
time_ms
bytecode_size_in_bytes

FeeJuice:_increase_public_balance
54.7
7,739

FeeJuice:set_portal
9.81 (-19%)
2,354

Token:constructor
79.0 (-3%)
26,051

FPC:constructor
52.4 (-1%)
18,001

FeeJuice:mint_public
40.2 (+1%)
5,877

Token:mint_public
70.3 (+1%)
10,917

Token:assert_minter_and_mint
42.2 (+2%)
7,512

AuthRegistry:set_authorized
41.0 (+7%)
4,391

FPC:prepare_fee
224 (-3%)
7,043

Token:transfer_public
:warning: 20.3 (-38%)
39,426

FPC:pay_refund
51.1 (-4%)
10,234

Benchmarking:increment_balance
:warning: 940 (-22%)
6,563

Token:_increase_public_balance
46.9 (+15%)
8,433

FPC:pay_refund_with_shielded_rebate
67.5 (+7%)
10,783

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.163 (+3%)

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

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

batch_insert_into_append_only_tree_16_depth_ms
2.19
3.88 (+1%)
N/A
N/A
N/A
N/A
N/A

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

batch_insert_into_append_only_tree_16_depth_hash_ms
0.114
0.110 (+1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
11.8 (+4%)
18.1 (+4%)
31.5 (+3%)
60.0 (+2%)
113

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

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.113 (+3%)
0.105 (+4%)
0.102 (+3%)
0.103 (+2%)
0.102 (+1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
14.6 (+1%)
26.0 (+1%)
44.6 (+3%)
83.7 (+2%)
162 (+1%)

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

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.111 (+1%)
0.105 (+2%)
0.108 (+3%)
0.103 (+2%)
0.102 (+1%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
16.6
N/A
N/A
N/A
N/A

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

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.107 (+1%)
N/A
N/A
N/A
N/A

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

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
64,779
668,997

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


fix: remove redundant installations from Dockerfile

Related Issues

fixes #36

Checklist

[ ] Commits squashed
[ ] Issues referenced (in commit and pull request)


buildah bud --idfile functionality is missing

Description
buildah bud --idfile is missing and needs to be provided.  This is functionality that Docker has.
#599 is the parent issue for this issue.
Output of buildah version:
Buildah v0.16

Ugh, just noted this should be --iidfile, my bad cut/paste from last night.  Sorry @rhatdan


Duration scalar - fix for defining custom scalar name

Fixing Duration scalar so that you can define a custom scalar name.
Current behavior impacts Duration scalar and also OffsetDateTime scalar
#30

@setchy oh, thank you for this fix!


Add missing "s" to {metric_,}relabel_config

Also fix references to anchors, which were already broken.

@brian-brazil ok, right ! Doh :-)
I'll send another PR to fix the anchors. Thanks !


Compatibility with Aframe 1.3.0

When using AFrame 1.3.0, the following error occurs:

aframe-websurfaces.umd.js:1 Uncaught TypeError: Class constructor Mesh cannot be invoked without 'new'
    at new n (aframe-websurfaces.umd.js:1:4354)
    at HTMLElement.<anonymous> (aframe-websurfaces.umd.js:1:7158)
    at HTMLElement.<anonymous> (aframe-v1.3.0.min.js:45177:2943)
    at i.tick (aframe-websurfaces.umd.js:1:7873)
    at HTMLElement.value (aframe-v1.3.0.min.js:45187:12868)
    at HTMLElement.value (aframe-v1.3.0.min.js:45187:13402)
    at aframe-v1.3.0.min.js:45324:132
    at onAnimationFrame (aframe-v1.3.0.min.js:20088:34)
    at onAnimationFrame (aframe-v1.3.0.min.js:9547:4)

Easy fix found.  Replace all instances of THREE with AFRAME.THREE.
This corrected the issue for me

I'm also having this issue. Any fix?

I reverted to aframe 1.2.0
This was my only way of resolving this issue.  I plan on looking to patch a fork of this lib in the future for aframe 1.3.0.   The underlying threejs is many versions behind for this project and needs to be patched to be compatible with the same threejs version aframe 1.3.0 is using.

Okay thanks for your reply!

Getting the same issue for v1.3 of AFrame, are there plans to update this?

Did anyone find a work around for this incompatibility issue?


fix(vue-app): don't normalise route path if it's valid

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)

Description
After https://github.com/nuxt/nuxt.js/pull/9431 we were using the normalised path (which might, for example, lack a trailing slash if trailingSlash: true weren't set). This PR reverts that behaviour whilst keeping the fix, at the expense of a double implicit call to router.resolve.
Closes #9442
Checklist:

[x] All new and existing tests are passing.

Codecov Report

Merging #9460 (e602bea) into dev (35c6ac4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #9460   +/-   ##
=======================================
  Coverage   65.15%   65.15%
=======================================
  Files          94       94
  Lines        4107     4107
  Branches     1125     1125
=======================================
  Hits         2676     2676
  Misses       1153     1153
  Partials      278      278

Flag
Coverage Δ

unittests
65.15% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

Any news on when this will be merged?

Please release fix

Hi, this is going to be released?

It will release in 2.16 but there is no eta for this release.
Meanwhile you can nuxe-edge instead of nuxt. nuxt-edge does include this fix

@farnabaz

I believe, It will release in 2.16 but there is no eta for this release.
Meanwhile you can nuxe-edge instead of nuxt. nuxt-edge does include this fix
Thanks for the tips 😬

Please release 🙏

Released in v2.15.8

My node version is 18.12.1 and yarn version is 1.22.19. I tried to install node packages and run project but I got some types of errors like that.
When I change node version, I can see another issue.

This is node version 14.15.0 issue.

This is node version 14.15.0 issue.

it says there is no issue. but project is not running


feat: bump ethereum-package version

Description

The latest version of Kurtosis v0.89.0 introduced a breaking change to the way files are stored when using the store statement. This disrupted the operation of the ethereum package. A patch has been released to mitigate the problem.
The PR also fixes the docker-image-builder cron job triggers.
References (if applicable)

Fixes #96

Closing in favor of #97


Add Website and Other Links to README

As recommended by @astoycos I've added some additional content to the README.
Questions:
Some other READMEs have nice graphics - is there one that would make sense here?
As a new contributor I find the website being only for the AdminNetworkPolicy to be a bit confusing - is it worth either specifying that it is the current team focus - or adding a more generic landing page to the website?
Should we link to any NW Policies v1 site/documentation incase someone ends up here by mistake?

/assign
Thanks so much for this @cailynse!! Will take a look ASAP

Also small nit @cailynse But can you sign your commits with -s? It just made it easier to figure out who owned the original commits in the future!

Thanks @cailynse This looks sooo much better!

/lgtm
/approve


Server sending requests to clients

Hello! I stumbled across this project, hopefully you don't mind some random premature question.
I am not very familiar with futures/tokio yet. I wonder how you would handle a scenario such as this:

An async server SERVER serving multiple concurrent clients.

A client CLIENT connects to SERVER.

SERVER sends multiple concurrent requests & notifications to CLIENT.

CLIENT processes the requests and returns replies after a while, not necessarily in order.

Usually a client sends requests to a server, here it's inverted.
I assume SERVER would want to spawn a task per client, build up a future of the entire interaction with the client in that task, and wait on it?
In other languages, I would create a future per request, which I'll store in a pending requests map (mapped by the request ID) in the task. When a reply comes in, I match it to the request in the pending requests map and resolve the future. This way the mechanics of the RPC protocol are hidden, and for the caller, an RPC call is just Request -> Future<Response>.
Thanks!

Hello
Maybe I haven't thought about the higher-level details yet, but I can't say I see a problem with this being reversed. After you either connect or accept a connection, it's up to you what you do with that connection. If you put the server structure/handling on the end that connected and client on the end that listened, than everything should work.
Furthermore, I intend to get to a place where one endpoint may be both the client and server at the same time, so this scenario would definitely be supported.
But as you said, this is a bit premature, because even the low-level parts aren't finished yet. So, I must admit I don't know yet how I'll reach that goal.

Thanks! And good luck with the project.


Support const parameters

Reported by jsoumagne on 1 Jan 1970 00:22 UTC
Because hg_proc_xxx functions are used for both encoding and decoding, const parameters cannot be passed without an explicit cast.  There should be a way of avoiding that, maybe by having hg_const_string_t etc ?

Comment by jsoumagne on 1 Jan 1970 00:22 UTC
commit f77b5046745e5bf57ede17eb154444e8d4db8a8c adds proc_extra and mercury_proc_string which takes care of const and non const strings passed to mercury. Since it is in proc_extra, include of mercury_proc_string.h needs to be explicitly added.


'Item already owned' yet continues to try to claim it again

For the past few days, the bot has been trying to claim Watch Dogs 2 over and over, even though it recognizes 'item already owned'. I'm not sure why.... Please find trace logging here: https://pastebin.com/03tLkZa4
Thank you!

I created an EU test account and confirmed this wasn't a regional issue. Can you visit the store page logged in as the problem account and let me know what the availability looks like for the game variants?
Here's mine for example:

Here you go:

It appears as if none of the Watch_Dogs 2 editions are available for my account, but I don't understand why that would be the case. I already own Watch_Dogs 2 and have it installed:

Thanks!!


OverflowError: Python int too large to convert to C long

I ran the 2sectors example and received the following error:
File "abcEconomics\trade.pyx", line 485, in abcEconomics.trade.Trade.sell
File "abcEconomics\trade.pyx", line 121, in abcEconomics.trade.Offer.cinit
OverflowError: Python int too large to convert to C long

Same error here I experience:
File "abcEconomics\trade.pyx", line 485, in abcEconomics.trade.Trade.sell
File "abcEconomics\trade.pyx", line 121, in abcEconomics.trade.Offer.cinit
OverflowError: Python int too large to convert to C long
Any way to fix it?

Didn't see this issue until just now.
The abcEconomics on current master (not yet renamed to main to avoid the bad connotation) no longer uses cython, because the speedup gain is not significant, so we remove it for simplicity's sake. I will try to update the version uses in this repo when I have the time.
Currently, to make it work on cython's C, we probably need to use long long (int64).

I ran the start.py of 2sectors on latest master (https://github.com/AB-CE/abce/commit/983d427899a081160a3e3f0592ed0b1c1e3b69ab) and it worked fine. However, some of the examples are using outdated API that it will take a while to update this repo's requirements.txt.


Add option --webdewey and guess output format from filename

I also extended the README in branch https://github.com/gbv/mc2skos/tree/readme but not mentioning option --webdewey yet.

Codecov Report

Merging #33 into master will decrease coverage by 0.76%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master      #33      +/-   ##
==========================================
- Coverage   79.09%   78.32%   -0.77%
==========================================
  Files           5        5
  Lines         684      692       +8
==========================================
+ Hits          541      542       +1
- Misses        143      150       +7

Impacted Files
Coverage Δ

mc2skos/mc2skos.py
53.23% <33.33%> (-1.69%)
:arrow_down:

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 e8e8340...523cf91. Read the comment docs.

Thanks! I can also document the --webdewey option.

Btw. the --notes flags is mostly included because I'm not allowed to publish that for WebDewey. But for a general tool it probably makes more sense to include notes by default and have a --exclude-notes flag for the WebDewey case.

Thanks! I'd prefer --no-notes instead of --exclude_notes but nevermind.


@graphql-codegen/near-operation-file-preset does not import root Types when a fragment spread a fragment but does not query any fields itself.

Describe the bug
Where a parent fragment only spreads child fragment(s), and that child includes an enum, but the parent does not reference fields itself, it only spreads fragments. The near-operation-file preset does not import the root Types namespace causing a TypeScript error when the file references the enum with Types.enum.
To Reproduce
Create a repo with 3 folders, one that contains a root query file, another that contains a fragment that fetches something from the API and a third that spreads the afore mentioned fragment (but does not fetch anything itself). Then spread the second fragment in the query and generate.
Working reproduction: https://codesandbox.io/s/divine-voice-zjt60q?file=/src/fragment/fragment.graphql

My GraphQL schema:

type Query {
    test: Test
}

type Test {
    UUID: ID
    sampleEnum: SampleEnum
}

enum SampleEnum {
    Foo
    Bar
}

My GraphQL operations:

query test {
    test {
        ...FragmentSpreadFragment
    }
}

fragment FragmentSpreadFragment on Test {
  # Uncomment this to make the generated file import Types
  # UUID
  ...Fragment
}

fragment Fragment on Test {
    sampleEnum
}

My codegen.yml config file:

schema: schema.graphql
documents: 'src/**/*.graphql'
generates:
  src/types.ts:
    plugins:
      - typescript
  src/:
    preset: near-operation-file
    presetConfig:
      extension: .generated.tsx
      baseTypesPath: types.ts
    plugins:
      - typescript-operations
      - typescript-urql

Expected behaviour
The generated file should include the Types import as it is referenced in the file.
Environment:

OS: macOS 11.6.1
@graphql-codegen/...: All dependencies are latest and match what is used in the reproduction
NodeJS: 14.8.1

Additional context
This requirement came about because I have a React component that is rendered in two places, those two places do not need anything from the API themselves so they just spread their child's fragment.

Hi @alextuppen, and thank you for the report!
Sorry but I'm not adding a lot here but just labeling it according to our new Contribution Guide and issue flow.
Thanks to your reproduction, it seems you already got into stage 1 thanks to your reproduction! Thank you for that!
Now to advance to stage 2 we'll need a failing test; it would be great if someone could help progress the issues through the stages.
Thank you, and sorry that this comment is not a complete solution (yet).

Fixed in<EMAIL_ADDRESS>thanks to @resessh's path! 📦


Add EconomyAPI Support

As the names tell, just add the all time best economy ( EconomyAPI )

we deliberately abandoned the Api economy, because there was a problem with lib eco (support Economy Api + Bedrock Economy)  So for now this plugin is available only for the Bedrock Economy plugin.


Resolves: Exception when an interrupt controller is in a hierarchy

(#1433).
Index 'PL.interrupt_controllers' by the 'hierarchy_name' rather than the 'name' of the controller.
This can be done in several other ways, such as by changing interrupt_pins to use the name instead of the hierarchy_name. I chose one way pretty much arbitrarily.
It would nice if this issue is resolved, either by this PR or by some other way.

Our lab has hit this too and this patch resolves things for us

Looks great, thanks for the contribution.


App Engine

How can I host uptime kuma on Google App Engine free-tier?

I personally do not suggest it, as I remember that there is a lot of hidden costs of Google Cloud Platform such as the bandwidth costs across two different countries.
Oracle Cloud free-tier is my suggestion.

Yeah...I totally agree with you. I've signed up at Oracle months ago but didn't use it much. Unfortunately, due to account inactivity, they disabled my account. Now they don't even respond to my emails.


fix: rust does not have a 2022 edition

Small fix.
Rust does not have a 2022 edition. It's current editions are 2015, 2018 and 2021.
See: https://doc.rust-lang.org/edition-guide/

Thanks!


Generate syntax with random result

Hello,
I recently wondered why little changes (like a simple color change) to my settings very often result in Log-Highlight not working as expected.
Workflow: change user settings -> generate syntax -> close ST3 -> open ST3 -> apply Log-Highlighting
Now I made several consecutive "generate syntax" while leaving the settings file identical.
Big surprise: tmTheme is generated completely different (see attachment, all files generated from also attached settings file!?). In the working version, there is proper line formatting, while it is missing in the non-working tmTheme. Instead there are several commented lines there which do not appear in the working version.
settings.zip
I am working on Win10, ST3.2.2, Build3211, Log-Highlight 2.0.9
Update:
It seems that the tmTheme is updated when ST3/LogHighlight first matches a file with the respective extension pattern of this log-highlight profile when the file is opened. After this, the tmTheme changed to the working version.
Instead, when the file to highlight is already open and "Select syntax ...hnf" or just "highlight" is issued, the tmTheme does not get updated/corrected.
The initial (not working) version is easily identifiable by the second line:
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
In the corrected version this line is changed to
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

@SteffenWa , Hi,
A .tmTheme file can be changed when applying its background color as current color-scheme. Although two files look different, they shall have the same elements except commented. I don't know why one is working, and the other is not working. However, I've updated the package (v2.0.10) to generate .tmTheme similarly.
And, in your settings, I recommend that you should delete 'example' because it has the same extension with 'hnflog'.
'hnflog' : { "extension" : [ ".log", ... ],
'example' : { "extension" : [ "*.log", ".vcs.log", ".cpp.log", ... ],


Feat/aut754 Refactor of Feature line and heatmap plots

Improved Heatmap:

Added color scale
Display values on the grid
Only one feature is displayed at a time (accessible through combo box)
Details are displayed on tooltip when cell is hovered
Handled different case of error: invalid values, "not enough data"

Plot lines

the grid match the injection number column
no more tick on the horizontal axis
some padding around the plot
tooltip when you hover the plot.

Request modifications applied.


Show rubocop -V output even if the configuration is invalid

Currently if the configuration has anything invalid in it (obsolete cops, invalid cops, etc.), rubocop -V will output error messages from config validation but not the actual version information.
$ rubocop -V
Error: The `Style/MethodMissing` cop has been split into `Style/MethodMissingSuper` and `Style/MissingRespondToMissing`.
(obsolete configuration found in .rubocop.yml, please update it)

This change allows the config to be loaded without being validated, which allows rubocop -V to output properly. Only the version command is affected.
$ rubocop -V
1.6.1 (using Parser <IP_ADDRESS>, rubocop-ast 1.3.0, running on ruby 2.6.6 x86_64-darwin18)
  - rubocop-performance 1.9.1
  - rubocop-rspec 2.0.1

$ rubocop
Error: The `Style/MethodMissing` cop has been split into `Style/MethodMissingSuper` and `Style/MissingRespondToMissing`.
(obsolete configuration found in .rubocop.yml, please update it)

Related to #9228 (will slightly conflict but I'll fix it up once once is merged).

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

For example, see #9196 (rubocop -V was not working for the error report).

You'll have to rebase on top of master.

@dvandersluis Don't forget to rebase this PR.

Yeah I have this on my list, I have to fix the tests that were failing too I think.

@bbatsov finally got this green!

@bbatsov finally got this green!

@bbatsov finally got this green!

@bbatsov finally got this green!

Thanks!

Thanks!

This seems to have broken.
❯ bundle exec rubocop -V
Error: `Performance` cops have been extracted to the `rubocop-performance` gem.
(obsolete configuration found in /Users/pboling/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/standard-performance-1.1.0/config/base.yml, please update it)


Fix form disposed while opening sometimes throwing an exception

TyneFormBase occasionally throws an exception if it's disposed while opening.

Issue reported on v3.2.2, before the changes in v3.3.0 which modify the CancellationTokenSource usage (and inadvertently fix this issue)


Assess options to sleep system when not in use

consider light sensor

https://tasmota.github.io/docs/Commands/


CVPR 2024 Mose Challenge

I don't know if you are interested but the 1st solution in the CVPR 2024 challenge it seems a small CUTIE adaptation
https://arxiv.org/abs/2406.04600
And also the 3d place it was a CUTIE adaptation
https://arxiv.org/abs/2406.03668

Interesting. Thank you for letting me know!
Congrats to them 😄

They are not very detailed but probably some trick it could still be still useful to be adopted here.

I am happy to see and sure there will be future developments on better mask tracking. I would gladly take pull requests but unfortunately my current research focus is elsewhere. Thank you for your support and suggestion.

P.s. also the 2nd solution so 3/3 :wink:


KIT Environment needs pirvate subnets to support fargate pods

While I was testing KIT Environment with Fargate, I couldn't create fargate profiles as our KIT environment only creates public subnets even though some subnets are named private, as they have IGW associated in their route tables. Fix is required to be able to launch fargate pods.
An error occurred (InvalidParameterException) when calling the CreateFargateProfile operation: Subnet subnet-0ab49c01946ecc462 provided in Fargate Profile is not a private subnet

Merged


Update installation instructions to include windows install

Please update how to install for goodwork for windows, which includes a links to Docker and removing the "sudo" from install.sh where "sudo docker-compose -f docker-compose.dev.yml" and "sudo docker-compose" just for windows.

Do you already try to use it (https://www.microsoft.com/en-us/p/ubuntu/9nblggh4msv6)?


Daily delegations and unbonding data

We would like to show the daily delegation and unbonding amount. This can be done by querying all the delegations and unbonding information from all validators. It will be interesting when comparing the delegations with token price.

Would you like to have a per-account base delegation/undelegation tracking, or more something a global tracking?

After yesterday's call, we've decided to track on a per-account base.
That being said, the following API endpoints can be used to query the data:

/staking/validators/{validatorAddr}/delegations
/staking/validators/{validatorAddr}/unbonding_delegations

This should allow us to save both for validators as well for delegators.


Allow specifying specialArgs from nixos-rebuild?

Issue description
specialArgs seems to be a feature of the NixOS module system where values can be specified and made available to all modules in the evaluated configuration.
These arguments appear to be useful in certain situations or approaches to structuring NixOS configurations where regular NixOS module options don't work as well (e.g. would cause infinite recursion), such as imports = [ "base/${hostname}/partitions.nix" ] or lanIP = lanIPs.${hostname}.
It is possible to specify specialArgs in Flake-based NixOS configurations, by specifying them in the expression invoking nixpkgs.lib.nixosSystem. However, there is no way to specify them when using nixos-rebuild with a non-Flake-based configuration.
I think a --special-arg NAME VALUE switch for nixos-rebuild would be a nice addition for these circumstances, and to make it possible to parametrize NixOS configurations in general.
Reference:

https://stackoverflow.com/questions/47650857/nixos-module-imports-with-arguments

Alternatives considered

As mentioned, NixOS module options work well in most circumstances, though requiring constructs such as mkIf in some of them. However, it's not possible to specify them on the command line.
Perhaps improving NixOS module options is possible, e.g. by using fixpoint evaluation to avoid the infinite recursion problem?
It's possible to return modules from functions. However, this 1. seems to be a legacy format which causes problems such as with error locations, and 2. requires passing the arguments from the top-level downwards for each import, unlike module options and specialArgs which are available globally.
An unversioned file containing any local data that would otherwise be passed as parameters, however, this prohibits building multiple configurations in one go.
builtins.getEnv would be roughly equivalent to an unversioned file, with additional caveats.

However, there is no way to specify them when using nixos-rebuild with a non-Flake-based configuration.

You can generally use _module.args, unless you need to import them. Though, even _module.args can often be mis-/over-used when people are just afraid of learning how to use options properly.

Perhaps improving NixOS module options is possible, e.g. by using fixpoint evaluation to avoid the infinite recursion problem?

What do you believe lib.evalModules does in the first place?

I think a --special-arg NAME VALUE switch for nixos-rebuild would be a nice addition for these circumstances, and to make it possible to parametrize NixOS configurations in general.

This would be a bad idea for reproducibility.

It's possible to return modules from functions. However, this 1. seems to be a legacy format which causes problems such as with error locations,

You can set _file to work around this.

and 2. requires passing the arguments from the top-level downwards for each import, unlike module options and specialArgs which are available globally.

... and _module.args.

An unversioned file containing any local data that would otherwise be passed as parameters, however, this prohibits building multiple configurations in one go.
builtins.getEnv would be roughly equivalent to an unversioned file, with additional caveats.

These would be even worse ideas, as they throw reproducibility out the window.

You can generally use _module.args, unless you need to import them. Though, even _module.args can often be mis-/over-used when people are just afraid of learning how to use options properly.

I have experimented with them, but, as far as I can tell, they are equivalent with module options, and suffer from the same problem.

What do you believe lib.evalModules does in the first place?

I have not looked closely at its implementation, however, I have seen discussions about a potential change in that direction. Sorry if I've misconstrued.

This would be a bad idea for reproducibility.

Would you mind elaborating? I would assume that the argument becomes part of the hash, so two different values would result in different hashes, which wouldn't harm reproducibility.

I'm using reproducibility here to mean the same config should result in the same build output. You can't get the same output if you're passing getting config from the environment or CLI flags. Channels are bad enough in this respect, as everyone will have different channels; let's not make the situation actively worse.

I feel like that's a decision that lies squarely with the user. The user can set up a personal nixos-rebuild workflow which is, in fact, "deterministic"; and, as you've pointed out, they have plenty of capabilities to make their configuration non-"deterministic" right now.
I'm putting "deterministic" in quotes here because you seem to be using a certain specific definition of determinism (i.e. what is part of the inputs and what is not) that seems useful to you, but not everyone. We could use the same logic to say the ability to specify flake inputs, or the ability of flakes to have multiple outputs, make them non-deterministic.
@eclairevoyant I would also appreciate if you could, instead of only criticizing the proposal, try to understand the problem that it is trying to solve and offer alternative solutions.

Also you still haven't explained what your use case is yet.

I feel like I have, but to clarify:

Specifically, to inject information that is available globally to all modules in the configuration, such as the name of the machine being configured
More generally, a way to parametrize NixOS configurations that doesn't have the problems of the listed alternatives.

Please see the linked StackOverflow thread for additional discussion; I can find more similar discussions about others encountering the same challenges, if you wish.

We could use the same logic to say the ability to specify flake inputs, or the ability of flakes to have multiple outputs, make them non-deterministic.

No, because flakes have a lockfile including narHashes of all inputs.

@eclairevoyant I would also appreciate if you could, instead of only criticizing the proposal,

I'm criticising the choice to make NixOS actively worse to use for everyone to suit your individual usecase.

1. Specifically, to inject information that is available globally to all modules in the configuration, such as the name of the machine being configured

Which was answered above.

2. More generally, a way to parametrize NixOS configurations that doesn't have the problems of the listed alternatives.

Which I already addressed, point-by-point.

No, because flakes have a lockfile including narHashes of all inputs. The entire config is self-contained, which is not the case with your new CLI flags.

And what about --override-input?

I'm criticising the choice to make NixOS actively worse to use for everyone to suit your individual usecase.

You are being unreasonably hostile.

I don't see how a new option, which you don't need to use, will make NixOS worse for anyone, let alone everyone.
It is not just my use case.

Which was answered above.

If you're referring to the suggestion to use _module.args, then I've already pointed out that it has the same problems as one of the other alternatives I've already listed.

If you're referring to the suggestion to use _module.args

I'm referring to all of the suggestions, including import-ing a function that returns a module, which does not have any such issues.

OK, I tried a few different approaches:

#323720
Specifying variables via a file in the Nix search path
Parametrized modules (i.e. returning a module from a function)

The last two seem to work OK, but not without their own disadvantages. For the last one, there is the small inconvenience of having to ensure that all modules have the _file property, but it does seem like the least clunky approach without any nixpkgs patches.
To distill what I think is missing - I don't think we necessarily need a mechanism to pass arguments from the command line, but really perhaps just a way to pass the output of eval-config.nix to nixos-rebuild, which is currently not possible. That would still allow specifying variables declaratively in a way that makes them accessible to all modules without compromising on being able to use constructs like if. Another way could be some way to declare "constants" in modules, which cannot be overridden by other modules, but on the other hand can be used in if and attribute set lookups.
Not that I still think we need them, but I still don't understand the exact grounds of the objection against the proposal to add nixos-rebuild arguments. They don't seem any less "reproducible" than using -I / NIX_PATH to specify different nixpkgs or nixos-config or any other search path entries, or --override-input, or builtins.getEnv, or any other way to affect the evaluation. In the end, it will still result in a specific derivation whose instantiation will be as reproducible as always for the same inputs; the proposed arguments just being one more thing on this long list of inputs.

Perhaps improving NixOS module options is possible, e.g. by using fixpoint evaluation to avoid the infinite recursion problem?

What do you believe lib.evalModules does in the first place?

One way it could be different that could help in this area is if it were more optimistic when dealing with infinite recursion situations. From what I understand, right now, infinite recursion occurs because a setting's value is attempted to be resolved before all modules are evaluated, and that in turn occurs when attempting to evaluate a module. A potential improvement would be to assume that any attempt to evaluate a module which requires the value of a setting would not affect said setting, i.e. other.config does not occur inside the if branches of some.config = if other.config then ... else .... This can be verified mechanically by applying the configuration values in the if and re-evaluating; if the if statement is paradoxical, it should then lead to a "true" infinite recursion.


Remove unwanted Twitter icons, etc., from software pages

All the software pages have Twitter, Facebook, email, etc. links that are nonsense.

Could you provide a snapshot from the website? I couldn't find them

Oh yeah, I see this now, that is nonsense. It also occurs in publications too, which is more nonsense. What are your thoughts on just removing that footer all together? That would be easiest and I can't imagine any of our work warranting separate facebook, twitter, etc. pages. The other option would be searching if there is a linked facebook, twitter, etc., then add it to the footer; otherwise, remove it. This would be likely be significantly hard but I haven't looked into it much.

It seems to depend on browser, I don't see them in chrome


Xampp localhost After signup error loading.

Hello, I'm trying to install on xampp localhost. I followed eveything correctly But when I try to sign up on the sign up page it just says loading page ans sitd there. Can someone pleadse help me to fix this problem?
Joseph

Hello, It has been some time and i'm still stuck on the sign in loading page. It still keeps on saying locading. Can you please help me?


feat(api): at_edge = 'split' will behave like at_edge = 'stop' in ignored buffers when no mux window to move to

Fixes #83

@mehalter pretty simply change FYI. Will tag a minor release shortly after merging this.

Looks clean! Thanks again


Need a separate scan profile for 1.24

The insecure-port flag on the apiserver was removed in v1.24. Ref: https://github.com/kubernetes/kubernetes/pull/106859
We currently check for this in most of the scan profiles as it is explicitly stated as one of the checks in CIS 1.2.19, however, this should not be valid in k8s v1.24+ as the flag itself has been removed there.
CIS 1.2.19 ref:

Closing this as the profiles are based on the CIS Benchmark profiles themselves and should probably conform to those.


[Keyvault] az keyvault security-domain upload: Fix sd warpping keys with passwords

Related command

az keyvault security-domain upload
Description

#25270 introduced a bug which missed passwords argument while making restore blob. This PR aims to fix
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Keyvault


Proposal: Pre-emptive NavigationView visual refresh

Proposal: Pre-emptive NavigationView visual refresh

Summary

I know there is probably work and code ready to add to the repo for this control, but it would be good for the community to submit ideas and feedback before work is done with this control's refresh.

As the visual refresh works its way across all of WinUI - here is a place for the community to share thoughts on the NavigationView - which is essentially the default app pattern for WinUI apps.
Scope

Capability
Priority

This refresh should fit nicely with Edge and FluentUI - whilst adopting the new colours and styling
Must

With reveal going away, defaults should take this into accound
Should

An Inset Shadow should be added when in Left and LeftCompact modes (as well as RtL flow)
Should

Minimal mode could remain alongside a Flyout mode which displays a menu flyout with NavigationViewItems
Could

Important Notes

Allowing the NavigationView to use MenuFlyouts would enable a scenario like this one created by @zeealeid

Which I think is a very good use of space for smaller windows, and other utility style applications.

Other things to point out:

Selected Nav View Items would have a backplate which has a 4px margin top, left, and bottom - but flush with the right, below the inset shadow;
The Search Box would have it's search icon aligned to the left, to better match the NavigationViewItems with icons on their left;
When in Minimal or Flyout modes, the navigation pane would swap it's Inset Shadow for a DropShadow - as with other flyouts;
Icons would use the Fluent UI System Icons, for Settings, Back and the Hamburger buttons - it would be an open question as to how or if the Filled icon states are adopted by the control.

Open Questions

As mentioned above, Fluent UI System Icons have a Regular and Filled state, which are typically used to indicate an Active or Selected state - the NavigationView (and TabView) have a selected concept, and so an easy way to use these Filled states would be useful I think.

This design looks fantastic!
One question is that NavigationView has 2 different PaneDisplayMode, one is at left like the design the other is at the top.
How about NavigationView with PaneDisplayMode set at top? Should it also have a new design, or be part of Pivot or TabsView?

This design looks fantastic!
One question is that NavigationView has 2 different PaneDisplayMode, one is at left like the design the other is at the top.
How about NavigationView with PaneDisplayMode set at top? Should it also have a new design, or be part of Pivot or TabsView?

This design looks fantastic!
One question is that NavigationView has 2 different PaneDisplayMode, one is at left like the design the other is at the top.
How about NavigationView with PaneDisplayMode set at top? Should it also have a new design? Or be part of Pivot or TabsView?

I need to have a think about the top design mode - it has other considerations but is not radically different to the side aligned version

This design looks fantastic!
One question is that NavigationView has 2 different PaneDisplayMode, one is at left like the design the other is at the top.
How about NavigationView with PaneDisplayMode set at top? Should it also have a new design? Or be part of Pivot or TabsView?

I need to have a think about the top design mode - it has other considerations but is not radically different to the side aligned version

Guess I was right to put Pre-emptive in the title lol
#4009  Navigation View Visual Update

Guess I was right to put Pre-emptive in the title lol
#4009  Navigation View Visual Update

Interestingly, this design is highly consistent with Microsoft's new style.

Interestingly, this design is highly consistent with Microsoft's new style.

Interestingly, this design is highly consistent with Microsoft's new style xd.

When you see the direction the wind is blowing, its not too difficult to put yourself into the mindset of what is to come.
But I went a little further with some details like the Selected Item States and the Inset Shadow.
The Overlay/Flyout mode is also a new feature I am proposing, rather than just a visual update.

Interestingly, this design is highly consistent with Microsoft's new style xd.

When you see the direction the wind is blowing, its not too difficult to put yourself into the mindset of what is to come.
But I went a little further with some details like the Selected Item States and the Inset Shadow.
The Overlay/Flyout mode is also a new feature I am proposing, rather than just a visual update.

But I went a little further with some details like the Selected Item States and the Inset Shadow.
The Overlay/Flyout mode is also a new feature I am proposing, rather than just a visual update.

There's still a lot of room to enhance NavigationView in terms of functionality
For example, in WinUI 3, Hierarchical NavigationView is currently ignored.
In have multiple items in the navigation menu, if there is the Overlay/Flyout navigation menu mode and compact mode 2 kind of variable type, I'll prefer to go to choose the Overlay/Flyout mode.
Under the compact mode while it is possible to save the screen space, but in some cases difficult to jump to other items, in the Overlay/Flyout mode, I can put it in screen space position and focus on the work of other free.

But I went a little further with some details like the Selected Item States and the Inset Shadow.
The Overlay/Flyout mode is also a new feature I am proposing, rather than just a visual update.

There's still a lot of room to enhance NavigationView in terms of functionality
For example, in WinUI 3, Hierarchical NavigationView is currently ignored.
In have multiple items in the navigation menu, if there is the Overlay/Flyout navigation menu mode and compact mode 2 kind of variable type, I'll prefer to go to choose the Overlay/Flyout mode.
Under the compact mode while it is possible to save the screen space, but in some cases difficult to jump to other items, in the Overlay/Flyout mode, I can put it in screen space position and focus on the work of other free.

When WinUI 3 is out, all the updates and controls from WinUI 2's modern branches will be merged back in

When WinUI 3 is out, all the updates and controls from WinUI 2's modern branches will be merged back in

Thank you, @mdtauk. NavigationView has been updated to match our internal designers' work with #4009. Closing this proposal.


Modular Architecture for the Deep Space Habitat Instrumentation System

Data set for Modular Architecture for the Deep Space Habitat Instrumentation System
✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

Good one @kavyaLokuge
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow these steps.

Star this repository. ⭐
Follow Clueless on GitHub
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to the profile section from the top right-hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard!
And don’t forget to share your achievement with your friends.

Good one @kavyaLokuge
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow these steps.

Star this repository. ⭐
Follow Clueless on GitHub
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to the profile section from the top right-hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard!
And don’t forget to share your achievement with your friends.

Profile URL: https://www.clueless.tech/profile/82757644
@nikhil25803


Add class to DOM before element gets rendered

The class of a dynamic style seems to be added after the element has been rendered. This leads to not working css animations at the first time.

Seems to be caused by asynchronously adding those classNames to the DOM after the whole React tree was rendered.
I was already thinking of some way to directly use insertRule within the resolver. But not sure if that totally fixes the problem is unknown.


[BUG]  PDF Export isn't working

Describe the bug

Logged into my account, changed my resume and then when I'm click to export to pdf, the app keeps updating and the download/archive never appears to download.
Already checked into Firefox, Safari, Edge and Chrome as well as into a Linux and Mac os box.
Product Flavor

[x] Managed (https://rxresu.me)
[ ] Self Hosted

To Reproduce

Go to 'your resume'
Click on 'export to pdf'
Wait ...
Never actually sees the PDF

Expected behavior

I expected to see my resume in pdf format.
Screenshots

Desktop (please complete the following information):

OS:  Linux Ubuntu 22.04, Mac os 10.15 and Windows 10.
Browser  Chrome, Safari, Firefox
Version  Always the latest

Additional context

Cannot second this, pdf export works perfectly fine for me.

I was thinking about doing it in figma or mural as well, but this solution here works for me now

Good, I moved to Figma and got way more control over the layout and design, also the bug-free experience for me is a huge plus. Cannot recommend enough.


New rule to detect case in switch too long

Other code analysis tools have rules like this usually switch length >10 lines.

is # of lines a good metric though? Wouldn't maybe number of case blocks be better? Or # of lines inside a case block?

Both going on what sonar cube does [1][2]  it detects

no of case statement blocks (3 minimum / 30 maximum default)
switch statement should be short (5 line / block default)

1.https://sonar.spring.io/coding_rules#q=case statement
1.https://sonar.spring.io/coding_rules#q=switch


fix[DB Checker]: fixed MissingIndexChecker checks and enabled it

Fixes #4385
Describe the changes you have made in this PR -

Enabled MissingIndexChecker under DatabaseConsistencyCheckers
Fixed all checks by adding proper indexes to the tables

Screenshots of the changes (If any) -

cc @tachyons
Hi Firstly i got this error when i enabled MissingIndexChecker

so i marked the "index_grades_on_project_id" as unique using migration but then a redundant uniqueness check got failed

so i had to remove the uniqueness of "index_grades_on_project_id_and_assignment_id"  but doing so failed a codeclimate check:

I am not sure what to do any ideas?

Hi @tanmoysrt will it be a good idea to remove the validates :project_id, uniqueness: { scope: :assignment_id } line, this will resolve the codeclimate issue.
but I am not sure if it will be fine to do so, but based on logs i provided earlier it seems we don't need the above line, i.e:-


Ping method was removed from podman

No pypodman command seem to work anymore:
CRITICAL | 'SimpleClientInterfaceHandler' object has no attribute 'Ping'
Probably because that method was removed:
https://github.com/containers/libpod/commit/608019b65b2fb3dc1c88efcbed1cd88b70794fd7

@jwhonce


Reduce impact of disable feature in example config

Good catch. This is definitely the better default option.


OCM-152 | feat: 'rosa verify network' command

https://docs.google.com/document/d/1pLN83t5kh7Pv0iBtJFFQnIQvdpagG4WZIyel9YRFE3s/edit#
Note: The go mod vendor commit will be removed. Dependent on:
https://github.com/openshift-online/ocm-api-model/pull/757
https://gitlab.cee.redhat.com/service/uhc-clusters-service/-/merge_requests/5884

@willkutler Removing --status-only would imply removing the --watch too which means it would always be "interactive". I haven't used rosa enough to know users' patterns. Would it be sufficient to just always block and wait when the command is run?

@thomasmckay Hmm, thinking it about it more, it's probably better to not require users to be blocked and wait for a minute-plus long command to run. I think it should be good as-is

/retest

/test commits


GPIO - Verify the Driver file with its application examples

[ ] verify using fpga

Complete the documentation for gpio driver.

Remove the gpio_testcase directory in the samples.

is the documentation complete?


Exclude nonmonophyletic individuals from further analysis

If you have two dogs in a branch with five cats, the cats are the predominant species of that branch; thus, when we identify a dog as being nonmonophyletic, we should exclude that dog from future comparisons.

I believe that this is what the global_nm array is supposed to do.

Example test file is trio171sequence

Is this complete? Did the biologists verify it? @mollysrour

The first pass on this was pushed in #103, but the test file you mention, trio171sequence, does not work due to some ent problems.  @hawkrives said he'd take a look at it tomorrow, but provided that the input is formatted like what we have in emydura.gb or any of the other emydura examples, we should have this mostly if not completely done, and it should work.

(To be more concise: the mbnb pipeline, which will get deployed soonish, does have that pruning magic built out.)

I think we have this solved, but I'd like to keep it open until we can verify on the trio171 dataset.

We're done with this right @hawkrives ? Can we close?

This is now fully solved, I believe.


Pathfinder jump clearance

Fix the clearance checks in the current position and the neighbors when calculating which neighbors are reachable.
Also added the pathfinder debug particles from the devtest game. Those will need to be disabled or put behind a command before release.
Fixes #40

This needs more work.


Document process how to build TraceEvent Nuget

I was trying to check paths in the built TraceEvent library and I did not found a script for this.
I manage to find approximation like this. But that's probably not ideal and I do not know location where this can be documented.
cd src\TraceEvent
nuget.exe pack -Properties OutDir=bin\debug\ -Version 1.0.0 Microsoft.Diagnostics.Tracing.TraceEvent.nuspec

Separate note, does this project have to be built using msbuild? Maybe dotnet build works just fine with minor modifications, that way it would be possible to have dotnet pack and maybe signing related issue would be non-issue?

The nuget is built after the build of TraceEvent itself. TraceEvent.csproj sets GeneratePackageOnBuild to `true.
The .nuspec's placeholder properties, (Configuration, version and OutDir) are set in a custom target called SetNuspecProperties, also in TraceEvent.csproj:
So you just have to dotnet build TraceEvent.csproj and the .nupkg will be created under the bin directory.


Remove view wrapper

Removing the 'contents' view wrapper as optimal fix (could also wrap the entire view, but this is not needed).

Too messy, will redo this later if need be.


Grid rows not updated after setRowData() or getRows()

@ceolter
Niall -
I have a use case that requires toggling between two grids.  The case is essentially to show a list of selected recipients for sending a notification to, and to alternately show a list of all possible people that could be selected as recipients (for adding to the recipient list).
I've tried a number of approaches for this, and have run into different problems.  Currently, my solution is to have to complete Grid instances, each with their own GridOptions instance, and I am using Aurelia DOM bindings to show/hide the grids depending on the view mode that I'm in.  One grid (selectedRecipients) uses an InMemoryRowModel, and the other (allRecipients) using a VirtualPagingModel.
This works for the initial display, and for toggling of the grids.  However, I'm running into a confusing situation of not seeing the grid row data updated in the visible grid when I make changes to the underlying row data.  Here are the issues I'm seeing.

I am trying to preselect (select: true) rows for the grids, using code like this:

                // pre-select nodes as needed.
                if(Array.isArray(selection)) {
                  gridOptions.api.forEachNode( function (node) {
                      if (selection.find(function(item:any, index:number, array:any[]) {
                        return item.memberId === node.data.memberId
                      })) {
                          node.setSelected(true);
                          gridOptions.api.refreshRows([node]);
                      }
                  });
                }

By debugging this code, I can see that the row node is selected, but I never see the visible row marked as selected via the selection checkbox.  I have tried with and without adding the call to gridOptions.api.refreshRows([node]);.

When I detect a change to the tracked selection data, I then call the following code on the grid instance that uses the InMemoryRowModel:

      gridOptions.api.setRowData(selection);
      gridOptions.api.selectAll();

After this, I can verify that the number of rows in the row model has changed, but again I am not seeing the visible rows in the grid change - the data is not modified in the visible grid.
I've tried every combination of refreshView(), purgeVirtualRowCache(), refreshVirtualRowCache(), etc., but with no effect.  Is there something else that I've missed, or any suggestion you can provide about where to look or what to change?
Regards,
Don

can you single this down to a simple test, and possibly provide a plunker?
node.setSelected(true);
gridOptions.api.refreshRows([node]);

the refreshRows is not needed.
i don't know whats wrong, but the setSelected(true) should just work, so i'm thinking maybe the grids are getting mixed up somehow. if there was a plunker i could debug through it.
ps closing as it's not an ag-grid issue, want github for tracking items needing fixing in ag-grid

Hi All,
i need some help for below issue..
i have scenarios where my grid should change data as per the response object.
i tried using this.gridOptions.api.setRowData(this.rowDataGrid); but i got a error as "Cannot read property 'setRowData' of undefined"
So i tried using
this.gridOptions.api.setRowData(this.rowDataGrid);
this.gridOptions = {
onGridReady: function() {
this.gridOptions.api.setRowData(this.rowDataGrid);
}
}
with this i got error as "Cannot read property 'api' of undefined"
Please help i am very new to angular 2

@don-bluelinegrid if u have got this done,,, pls share how u made UI to accept changes?

same issue
core.js:1448 ERROR Error: Uncaught (in promise): TypeError: Cannot read property 'setRowData' of undefined
TypeError: Cannot read property 'setRowData' of undefined
at TaskPropertyListComponent.createRowData (task-property-list.component.ts:48)
at new TaskPropertyListComponent (task-property-list.component.ts:31)
at createClass (core.js:12441)
at createDirectiveInstance (core.js:12284)
at createViewNodes (core.js:13742)
at createRootView (core.js:13631)
at callWithDebugContext (core.js:15056)
at Object.debugCreateRootView [as createRootView] (core.js:14339)
at ComponentFactory_.create (core.js:11236)
at ComponentFactoryBoundToModule.create (core.js:4023)
at TaskPropertyListComponent.createRowData (task-property-list.component.ts:48)
at new TaskPropertyListComponent (task-property-list.component.ts:31)
at createClass (core.js:12441)
at createDirectiveInstance (core.js:12284)
at createViewNodes (core.js:13742)
at createRootView (core.js:13631)
at callWithDebugContext (core.js:15056)
at Object.debugCreateRootView [as createRootView] (core.js:14339)
at ComponentFactory_.create (core.js:11236)
at ComponentFactoryBoundToModule.create (core.js:4023)
at resolvePromise (zone.js:809)
at resolvePromise (zone.js:775)
at eval (zone.js:858)
at ZoneDelegate.invokeTask (zone.js:421)
at Object.onInvokeTask (core.js:4740)
at ZoneDelegate.invokeTask (zone.js:420)
at Zone.runTask (zone.js:188)
at drainMicroTaskQueue (zone.js:595)
at ZoneTask.invokeTask [as invoke] (zone.js:500)
at invokeTask (zone.js:1517)
can anyone please give the correct solution


Update docs: homebrew/livecheck

The docs are outdated, since live check has been moved to the Homebrew organization.

Thank you for your first contribution, @davidchall!


Sequences still don't work

Same as: https://github.com/nandorojo/moti/issues/140
Is this still a bug in react-native-reanimated?
I don't think this solved it: https://github.com/software-mansion/react-native-reanimated/pull/2851
Could you give the v2.5.0 a try?
    "react-native-reanimated": "2.5.0",
    "moti": "0.17.1",
    "react-native": "0.67.3",

can you make a reproduction using the starter template? if you want to use the newer reanimated version, simply use expo run:ios to create a custom dev client.
npx create-react-native-app -t with-moti

@nandorojo
FYI: I'm still getting having the same issue, even with the latest version of reanimated (2.8.0)
Since reanimated 2.3.0 I can't use sequences anymore https://github.com/nandorojo/moti/issues/131
I'm not using expo by the way
Let me know if I can help with the reproduction of the issue

hm, do they work with reanimated?

It seems to be working fine with the expo v44 and the latest version of moti.
We are using react-native v0.66.3 and a bare workflow with some expo dependencies
I will try to create a small repro project


MismatchSenderID on android

When trying to send a message (either individual or bulk) I get an error back:
Bulk: GCMError: {u'failure': 1, u'canonical_ids': 0, u'success': 0, u'multicast_id':<PHONE_NUMBER>371826898, u'results': [{u'error': u'MismatchSenderId'}]}

Individual: GCMError: Error=MismatchSenderId

I have followed the instructions to setup everything and in my settings.py I have:
PUSH_NOTIFICATIONS_SETTINGS = {
        "GCM_API_KEY": "my-api-key",
        "APNS_CERTIFICATE": "path/to/my/cert.pem",
}

From the Google developper docs I get the impression that also the sender ID has to be send and not only the API key.
Is this a bug or am I simply doing something very wrong?

Did you take a look at this?
https://stackoverflow.com/questions/11313342/why-do-i-get-mismatchsenderid-from-gcm-server-side

I found the problem: I shouldn't do programming before having my morning coffee...
In the client app I wrote the API key instead of the ClientID during the registration of the device and that caused the error. Changed that and everything works like a charm now.


Add Heathens by Twenty One Pilots

Song Name
Heathens
Artist Name
Twenty One Pilots
Source
Youtube
Youtube Link
Rx43cpumP01V8LyI
Direct File Link
No response
Song ID
749713
Start Offset [ms]
20 seconds
Extra
Created from Auto Nong.
Created for level: 107380822
Put the start ofset to 20 seconds please

reject
invalid YouTube link


Streaming beta samples

Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for discussion)

[X] Tests and linter pass
[X] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Please review.

@JustinBeckwith Fixed the review comments. Please let me know if there is anything else.


Crash on startup on Raspberry Pi4b 64bit Ubuntu 22.04 + v3dv

Godot version
Godot Engine v4.0.alpha.custom_build.41fdddb1f
System information
Raspberry Pi4b 64bit Ubuntu 22.04 + v3dv
Issue description
I just built and was trying to start Godot with the vulkan loader pointing to the official Raspberry Vulkan driver v3dv by Igalia.
I get a black window and this message in the term,
Hopefully this can be of use.
bin/godot.linuxbsd.tools.64
Godot Engine v4.0.alpha.custom_build.41fdddb1f - https://godotengine.org
Vulkan API 1.2.0 - Using Vulkan Device #0: Unknown - V3D 4.2

ERROR: vmaCreatePool failed with error -8.
   at: _find_or_create_small_allocs_pool (drivers/vulkan/rendering_device_vulkan.cpp:8807)
ERROR: Can't create buffer of size: 1024, error -8.
   at: _buffer_allocate (drivers/vulkan/rendering_device_vulkan.cpp:1347)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.0.alpha.custom_build (41fdddb1f8132dcba8256a145de44da5df3155b2)
Dumping the backtrace. Please include this when reporting the bug on: https://github.com/godotengine/godot/issues
[1] linux-vdso.so.1(__kernel_rt_sigreturn+0) [0xffff9919f7dc] (??:0)
[2] /usr/lib/libvulkan_broadcom.so(+0x13f2c4) [0xffff96d9f2c4] (??:0)
[3] /usr/lib/libvulkan_broadcom.so(+0x13f550) [0xffff96d9f550] (??:0)
[4] /usr/lib/libvulkan_broadcom.so(+0x13f644) [0xffff96d9f644] (??:0)
[5] /usr/lib/libvulkan_broadcom.so(+0x603f4) [0xffff96cc03f4] (??:0)
[6] /usr/lib/libvulkan_broadcom.so(+0x60f5c) [0xffff96cc0f5c] (??:0)
[7] /usr/lib/libvulkan_broadcom.so(+0xa252c) [0xffff96d0252c] (??:0)
[8] RenderingDeviceVulkan::texture_get_data(RID, unsigned int) (??:0)
[9] RendererRD::TextureStorage::texture_2d_get(RID) const (??:0)
[10] RenderingServerDefault::texture_2d_get(RID) const (??:0)
[11] ImageTexture::get_image() const (??:0)
[12] bin/godot.linuxbsd.tools.64(+0x34cf990) [0xaaaadcfff990] (??:0)
[13] create_editor_theme(Ref<Theme>) (??:0)
[14] create_custom_theme(Ref<Theme>) (??:0)
[15] ProjectManager::ProjectManager() (??:0)
[16] Main::start() (??:0)
[17] bin/godot.linuxbsd.tools.64(main+0x13c) [0xaaaadbd88950] (??:0)
[18] /lib/aarch64-linux-gnu/libc.so.6(+0x273fc) [0xffff98b973fc] (??:0)
[19] /lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98) [0xffff98b974cc] (??:0)
[20] bin/godot.linuxbsd.tools.64(_start+0x30) [0xaaaadbd88730] (??:0)
-- END OF BACKTRACE --
================================================================

Cheers
Steps to reproduce
Build as usual but with Mesa/Igalia Vulkan driver build from hot.
Run in shell on Ubuntu desktop.
Minimal reproduction project
No response

Is there a way to make the build use only Vulkan 1.1 ?


3.7.5 => 3.8.3 introduces breaking change(and shouldn't)

TypeScript Version:  3.8.3

Search Terms:

Option 'noEmit' cannot be specified with option 'incremental'.
typescript incremental noEmit
tsc noEmit incremental

Code
{
  "incremental": true
}

tsc --noEmit

Expected behavior:
The typescript project should compile successfully (it does under 3.7.5) since 3.7.5 to 3.8.3 is not a semver breaking change the two should be backwards compatible, but aren't. https://semver.org/spec/v2.0.0.html#summary
Actual behavior:
tsconfig.json:15:5 - error TS5053: Option 'noEmit' cannot be specified with option 'incremental'.

15     "incremental": true,
       ~~~~~~~~~~~~~

Found 1 error.

Playground Link:
n/a (typescript playground doesn't have the option to configure the tsc command or set the incremental option in tsconfig.json
Related Issues:
n/a

since 3.7.5 to 3.8.3 is not a semver breaking change

TypeScript does not follow SemVer: https://github.com/microsoft/TypeScript/issues/14116#issuecomment-280410804

...oh.
...Well that's "fun".

There are good reasons to not follow SemVer. :-) You can read about them in #14116.
Also you can check out #36917, which mentions why noEmit and incremental is not allowed/supported together.

Yeah, thanks. I'm reading the thread just now...the only problem is that I'm pinned to 3.5.2 and getting 3.8.x.
If typescript doesn't follow semver...is there an explanation somewhere of what the version numbers actually mean? Do they mean anything at all?


Experiment/user defined abstractions dfu

Similar to configs, just taking any references to mcuboot/stm32 flash/our custom code out of the bm_dfu_client.cpp file and using the functions in bm_dfu_generic.h in a bm_dfu_generic.c file in the "app" code base where we will now make all of those mcuboot/stm32 flash/custom calls.
Next steps
This PR does not convert the bm_dfu_core/host/client.cpp files to using the bm_os/freertos functions and I think that can be in a separate PR so those changes don't congest this PR. I believe converting to use the bm_os functions and creating a common crc16_ccitt would be the last steps needed to move these files over to bm_core.
Blocked by https://github.com/bristlemouth/bm_core/pull/9, so I can point back to the main branch sha.
Testing
Issuing the update from Spotter and begining to download to bridge:

Bridge finishing download from spotter and start sending chunks to the mote:

Mote info before the udpate:

Mote receiving the update:

Mote doing the update, successfully restting and confirming the new image:

Mote info after the udpate:

Bridge receiving client update success:

Spotter receiving update success:

I just realized that there may also be a config reference since we may need to check the dfu_confirm config... I will look for that and add that in to this PR. Ahhh it is in bm_dfu_core.cpp. I'll try move those over to bm_dfu_generic.h and add the implementations to bm_dfu_generic.c! I also just realized that there is all of the code surrounding NVM paritions.... so that needs to be handled as well!

Okay so i have made the sys config changes which means I should test

a normal update flow again
an update from v0.10.0 to latest

TODO - do these two tests ^^^
But I also need to try and remove the NVM partition references, so maybe I will try that first then do the tests so that I don't have to repeat more tests!

Okay one more thing I realized should be moved over is the generic state machine. I think this should be moved in bm_common and then once I get that linked back in here I will test it!

Okay so all of the nvm, config stuff has been removed and is no longer included in any of the bcmp/bcmp_config/bcmp_dfu/bm_l2 .h/.c/.cpp files!
[ ] - Now i need to repeat the config testing that I did in PR:https://github.com/bristlemouth/bm_protocol/pull/179
[ ] - test a normal update flow from the current changes to another current change image
[ ] - test an update from v0.10.0 to current
Then in a separate PR I will remove all of the freeRTOS stuff using the bm_os abstraction then we should be good to move these files over to bm_core!

System partition tests
Set and commit:

Get and status after commit:

delete and commit:

status after delete

User partition tests
set and com

get and status

delete and commit

status after delete

##Normal update:
Spotter getting info and starting update:

### end of the update and getting info:

We can see the SHA went from 3e8b497f to 81a5e11c successfully! (these are the current last two commits here with not actual code changes)

The hello world mote updating a soft mote down the chain
soft mote info before update (v0.11.2-RC4):

Loading the image into the hello world motes DFU partition:

Successfully finished loading into the dfu partition:

Starting the update from the hello world mote and validating the loaded image:

Hello world mote finishing validating the loaded image and then begin sending it to the soft mote:

Soft mote beginning to receive the update:

Soft mote finishing receiving the update and resetting:

Hello world mote finishing sending the update, and getting a successful update response:

Soft Mote info after update (v0.11.2-RC3):

Updating from v0.9.0
This test started with both the hello world mote and bridge on v0.9.0. I then set the dfu_confirm config to 0 to tell the mote that it does not need an ACK from the bridge to confirm its update. I then issued the update from Spotter and waited for the expected "failure" on Spotter. After updating the bridge back to develop, we can see the mote update succeeded.
Setting the sys config dfu_confirm on the mote to 0 (from the Bridge's CLI):

Starting the update from spotter:

Spotter end of update with expected error:

Mote info after update:

after updating bridge back to latest, a bm info 0 from the spotter:

sys cfg status from the mote after updating showing successful settting of dfu_confirm to 1!


Improve error handling in BytesQueue.Push function in queue.go

The Push function in BytesQueue currently uses a generic error message when the queue is full. It is suggested to use errFullQueue for a more descriptive error message.
Current Code:
var (
	errEmptyQueue       = &queueError{"Empty queue"}
	errInvalidIndex     = &queueError{"Index must be greater than zero. Invalid index."}
	errIndexOutOfBounds = &queueError{"Index out of range"}
)

Push function
if !q.canInsertAfterTail(neededSize) {
		if q.canInsertBeforeHead(neededSize) {
			q.tail = leftMarginIndex
		} else if q.capacity+neededSize >= q.maxCapacity && q.maxCapacity > 0 {
			return -1, &queueError{"Full queue. Maximum size limit reached."}
		} else {
			q.allocateAdditionalMemory(neededSize)
		}
	}

Updated code
var (
	errEmptyQueue       = &queueError{"Queue is empty."}
	errInvalidIndex     = &queueError{"Index must be greater than zero. Invalid index."}
	errIndexOutOfBounds = &queueError{"Index out of range."}
	errFullQueue        = &queueError{"Queue is full. Maximum size limit reached."}
)

if !q.canInsertAfterTail(neededSize) {
		if q.canInsertBeforeHead(neededSize)) {
			q.tail = leftMarginIndex
		} else if q.capacity+neededSize >= q.maxCapacity && q.maxCapacity > 0 {
			return -1, errFullQueue
		} else {
			q.allocateAdditionalMemory(neededSize)
		}
	}

This will improve the code quality

@akanchha25 Indeed it's a good improvement. Do you think errors should be unexpeorted? If we export them then they could be used to check for given error like with io.EOF

@janisz That's a great point. Exporting the errors would indeed allow for more robust error handling, similar to checking for specific errors like io.EOF. This could be beneficial for users of the BytesQueue package to handle different error scenarios more explicitly.
I can update the code to export these error variables, making it easier for others to handle specific error conditions. I'll proceed with the changes if that sounds good to you.

Hi @akanchha25  @janisz . Guys i think bundling and seperating all error logs in a different go file like bytes_queue_error_logs.go would make it easy for us to keep all error logs in a single place and then export them directly in different functions or files for queue package. Would love to know your thoughts on this and would like to work on adding this functionality if you could assign me this task.


期望的时间

想知道 MAUI 的文章什么时候完成，期待已久。期望给一个准确的时间，
Translated:
I've been wondering when maui's article will be completed, and I've been waiting for a long time. Expect to give an accurate time,

文档详细信息
⚠ 请勿编辑此部分。 docs.microsoft.com ➟ GitHub 问题链接必须具有此部分。

ID: 7607155a-9a56-d752-c5ac-c3aeb6b128bc
Version Independent ID: 9a62d421-d009-30b3-843e-a92bfc21c061
Content: .NET MAUI安装 - .NET MAUI
Content Source: docs/get-started/installation.md
Product: dotnet-mobile
Technology: dotnet-maui
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hello. I translated your comment so that I could read it.
The translation indicated that you're speaking about this article, but I'm unsure if that is correct. This article has been completed. If you're wondering about the .NET MAUI product, that was released yesterday. The first official release of .NET MAUI was yesterday, with more updates coming soon. It still requires the preview versions of Visual Studio.
If you have more feedback related to this, you should share it on the .NET MAUI github repository.
I'm going to close this question as answered. If you don't think it is, please reopen it.
Have a good day.


Guardian "meta" for arbitrary key / value data per guardian

Currently the guardian setup has a field for adding a name for each guardian, but that's all guardians can do to indicate who they are. That's useful in the setup UI for having a human readable name, but the user experiences people will want to build on top of fedimint for identifying and verifying guardians is going to require much more. It would be useful if there were an arbitrary JSON blob similar to the federation meta that allowed each guardian to provide a set of key / value pairs for extra information to identify them.
Some examples of what kinds of keys could be added:

avatar_url for showing an image associated with the guardian
nostr for connecting to a nostr identity, which clients could potentially validate using something like NIP-39
twitter for linking to a twitter handle / tweet that you've made to prove you're a guardian of the federation
domain for providing a domain that you own, which clients could potentially validate by looking for a .well-known entry with a matching federation ID (See NIP-05 or Lightning Addresses)

We will also ultimately want to expose this metadata via the ClientConfig in the api_endpoints map.

Great idea!
There doesn't need to be consensus on these fields, ideally guardians can change them unilaterally if their handles change etc. This makes it much easier to implement too, but means the data wouldn't be part of the client config but rather a new API endpoint where each guardian returns their own identity.


Make username clickable in convo info screen

...on native.
This fixes DESKTOP-3963.

r? @keybase/react-hackers

Addressed https://github.com/keybase/client/commit/52a0415dcd82a8b28d821ef9a4da1e0d6162d20a#commitcomment-23433228; PTAL!


chore(v3): remove URLSync

This PR removes the URLSync.
This PR depends on #3148 to be fixed.

The doc is now updated

Linting is failign in this PR :)

Linting is failign in this PR :)

Linting never sleeps :)


Crash with GT 1.5.4

Crashes when loading into a world, using GT-- 1.1.5b
Log says:
[00:43:36] [Render thread/ERROR] [GregTechCEu/]: gt recipe gtceu:extrude_magnetic_samarium_to_plate output items is empty
[00:43:37] [Render thread/ERROR] [GregTechCEu/]: shaped recipe gtceu:plate_double_magnetic_samarium output is empty

Fixed as of GT-- 1.1.6.


Container Image Scanning Jobs do not get timeout when scanning pod fails

As far as I can tell [1] changed this. Jobs that are in the queue in state ready are ignored for timeout, but because we are using the queue to schedule the polling of the image-inspector pod state, if there is a failure in the pod then we will keep polling forever. It used to only skip this test for MiqServer agent class but now it will catch for all Jobs.
Is there a way we could use the Job timeout mechanism anyway?
We could always "reimplement" a timeout inside "kubernetes/container_manager/scanning/job.rb" but I feel like this is not a good solution right now.
[1]https://github.com/ManageIQ/manageiq/pull/14356

cc @kbrock @yrudman @cben @moolitayer @simon3z

@miq-bot add_label bug, providers/containers, smart state


Suggestion: implementation of the model reloading

I play with FreeCammer v1.2.4 and when I enter the free camera mode, my model becomes invisible:

To fix it I need to restart the save, which is problematic if I'm the host. So I just want to ask, could you add some button that will reload my model?

Does enabling the free camera cause the model to go invisible? Not when you emote, correct? I could probably add this in the next patch. I don't want to add a default keybind for this, though, so I might only allow setting the keybind with InputUtils installed if that works for you.

Oh no, is there any way to avoid InputUtils? It breaks some of my mods...

And yeah, it doesn't matter where to enter the free camera mode

I've tested the new update and realized that reloading the model doesn't help, so I think I should give an appropriate list of steps to recreate the problem:

Create new profile
Get TooManyEmotes v1.8.6 and FreeCammer v1.2.4
Start new game
Enter the free camera mode
Emote

Okay thanks! Let me see if I can find anything out!

Hey, I rewatched my replays and noticed that previous versions of my mods didn't have this problem yet. I've tested it and found out that the problem occurs if FreeCammer has version 1.2.4. So if it can help with investigations, FreeCammer v1.2.3 doesn't cause the problem.

I have good news, the FreeCammer developer fixed the issue on his side, so there is no problem anymore.


Support formatting python code cells in Quarto document (.qmd extensions)

Description
For context about the Quarto project (https://quarto.org/)

Quarto® is an open-source scientific and technical publishing system built on Pandoc

Quarto document will be Markdown text file leveraging the Pandoc Markdown syntax, but with the addition for Computation code cells.  It supports different computation engine, including Python https://quarto.org/docs/computations/python.html
The could also be other block syntax containing Python code to format.
Some details below

About Quarto content with Python code
Here is an example of .qmd using Python computation to produce a HTML document
---
title: "matplotlib demo"
format:
  html:
    code-fold: true
jupyter: python3
---

For a demonstration of a line plot on a polar axis, see @fig-polar.

```{python}
#| label: fig-polar
#| fig-cap: "A line plot on a polar axis"

import numpy as np
import matplotlib.pyplot as plt

r = np.arange(0, 2, 0.01)
theta = 2 * np.pi * r
fig, ax = plt.subplots(
  subplot_kw = {'projection': 'polar'}
)
ax.plot(theta, r)
ax.set_rticks([0.5, 1, 1.5, 2])
ax.grid(True)
plt.show()
```

The special code block syntax using ```{python} represents computation cells with special comments using YAML syntax for configuration and then usual Python code. These are cells that will be evaluated in order for there output to be including in a classic .md file, and then converted to an output format (here .html), by Pandoc.
A Quarto document can have also usual Markdown code blocks using the ```python  syntax (https://quarto.org/docs/authoring/markdown-basics.html#source-code) . Those code blocks won't be evaluated, just shown in the output as highlighted python code. For those blocks, I believe blacken-docs already works.
Last type of code block containing python code is "unexecuted block" (https://quarto.org/docs/computations/execution-options.html#unexecuted-blocks) useful to demo Quarto syntax in an output
```{{python}}
import numpy as np
```

Would that be something to consider for blacken-docs project ?

We believe that https://github.com/psf/black/issues/294 can be dealt with directly on Quarto side. We'll follow work in https://github.com/quarto-dev/quarto/issues/111 and thus close this issue as it will be easier to call the format than learn / know how to navigate a qmd file from an another tool.


Add a flag which runs migrations with CREATE TABLE UNLOGGED instead of CREATE TABLE

Problem
integration/functional tests involving the DB are slow. One way to speed them up significantly is to use UNLOGGED tables. I don't have any benchmarks on me, but with a huge test suite it can save like 20-40% time and CPU resources.
Suggested solution
I am not sure how everyone else does it, but I setup DBs for testing using prisma migrate reset command.
So for me, the ideal solution would be a CLI flag for that command like --unlogged-tables.
This would do a very simple thing-when any sql files is loaded, before it is executed, we would just replace all CREATE TABLE|create table with CREATE TABLE UNLOGGED
Alternatives
alternatively I could write a script that replaces it in the migration files, calls  prisma migrate reset  and then reverts all migration files back, but the CLI flag would be much more elegant.
Additional context
I write JS/TS for food and shelter. No time for caution.

👋 Hi @capaj!
I've been working on my NPM Package Prisma Util, which is all about implementing features that are requested by developers in the community. This issue has attracted my attention and I want to ask if you'd be interested in it being implemented in Prisma Util.
Could you explain this feature a bit more so I can understand exactly what capabilities you want?

I think it would be benedficial to be able to specify UNLOGGED in the schema definition too. I use unlogged tables for cache (instead of redis to reduce TCO). Or is there another way to specify that in the model without modifying generated migrations?

Is anyone working on this? I use unlogged tables for cache too, but Prisma looks like not support CREATE TABLE UNLOGGED yet.

You can always modify the generated migration.sql and the contained SQL statements before executing them. This issue is just about having a flag that allows to configure that, so the generated SQL is like that by default.

@janpio
Yes, I know that I can modify the generated migration.sql to add UNLOGGED.
after I modify migration.sql and run prisma migrate next time, always has a modified after it was applied warning message. So I have to update the checksum of

@janpio
Yes, I know that I can add UNLOGGED manually to migration.sql, but it generates a warning message when I run prisma migrate after any modifications. To resolve it, I must update the checksum of the _prisma_migrations table. It would be easier if prisma.schema had a flag to handle this.

That should not be the case if you use migrate dev --create-only to create the migration file, adapt it, and only then apply it (which will mark it as applied in _prisma_migrations with a checksum) with another migrate dev or migrate deploy run.


Child applications are not loading because of 404 error

Hello,
I've started experimenting with this example project to see how I can add my own child applications or modify existing ones, and ran into the following error (Note: it also applies to all my currently active child applications):

Uncaught Error: 'menu' died in status SKIP_BECAUSE_BROKEN: "Try to load /menu/index.html, status : undefined => undefined"

On the top of the trace, the following error appeared:

Failed to load resource: the server responded with a status of 404 (Not Found) - :8080/menu/index.html

First of all, I was trying to modify existing apps included in this git project, then decided to rollback to the original version. Neither original version nor my custom solution is able to load any of the child applications.
I don't know if this issue is related to webpack's bundling process, or something like that, but I hope we can get through this easily.
Webpack versions:

webpack: ^3.11.0
webpack-dev-server: ^2.9.7

Do you run
npm install -g @angular/cli
npm install
npm run ng:build
npm start
?

I think you forgot the npm run ng:build to build all your child app

Yes, that was the issue, thanks for your help.

Is it ok now?

Yes, thanks 🙂


Use #[non_exhaustive] instead of manual __Nonexhaustive variants

It used to not be available in our MSRV, but that got bumped recently.

#[non_exhaustive] was introduced in 1.40, our MSRV is 1.36. We shouldn't do this yet, right?

1.40 is a year old by now, I would just bump MSRV to 1.40.

I added a PR for this one. I'm not sure how MSRV is handled, though.

I added a PR for this one. I'm not sure how MSRV is handled, though.


Basic ambient lighting

Foreword
Ambient lights should be supported as partially instantiated lights. That means although we can give them a position, and orientation and a scale, those properties will be ignored and only color information will be used.
Impacts
Core.Light
Of course, our core LightType is about to change to introduce this. We’ll add the constructor Ambient. On Ambient lights, shadowing can’t be enabled.
Shaders
Our current shaders (lighting and shadowing) implements both lighting and shadowing aspects for omnidirectional lights. That is wrong. We need to find a way to change the shader regarding the light type. Better, we need to render all types of a given type all at the same time.

Impacts
Core.Light
Of course, our core LightType is about to change to introduce this. We’ll add the constructor Ambient. On Ambient lights, shadowing can’t be enabled.
Shaders
Our current shaders (lighting and shadowing) implements both lighting and shadowing aspects for omnidirectional lights. That is wrong. We need to find a way to change the shader regarding the light type. Better, we need to render all types of a given type all at the same time.


⚠ Bofrost.be has degraded performance

In cf69f9b, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2226 ms

Resolved: Bofrost.be performance has improved in 7db809c after 6 minutes.


Auto generating AUTHORS based on git log

Description
This commit is for testing the generation of AUTHORS.txt which happens on push to master.
The same code is already in https://github.com/pion/.goassets/pull/64 . Once this commit is merged we need to pull the master and verify the AUTHORS.txt has valid content. Once it's verified we can merge the .goassets PR and update all the pion project.

Closing for https://github.com/pion/webrtc/pull/1862
I am just having it squash and some other minor things.


simplify onbording

add a make builder target for easier initial setup
make Dockerfiles not rely on proto being precompiled

I would argue this is recommended for everyone

So should we then remove the other way altogether? Easier to maintain, what is gone can not bitrot.


Docs on how to get data out of S3

Once one has the URL, what does one do with it? A bit more details would be nice, for the API docs, and maybe in a tech note.

where should I add that - since you're working on docs and old docs will be out of date, just put it here for you to add in your docs site?

Yes that makes sense

will do

some notes towards good docs for /history/:date route @maelle
/history/:date route
The /history/:date route allows GET requests only. The route is intended for fetching compressed new-line delimited JSON for an individual date, where all CRAN checks data across all packages is combined.
:date should be of the form YYYY-MM-DD
A request to /history/:date leads to a redirect (http status 302) and a returned JSON body with a message telling the user to follow the link in the Location response header in case they aren't familiar with redirects. The link to follow is a temporary Amazon S3 link to the JSON file for the given date.
One can automatically get the link to the JSON file by following the redirect. You can do this in curl with the -L flag, or in R by using the followlocation curl option like followlocation=1.
An important note is the data in the JSON file is NOT valid JSON as an entire entity. Each line of the file IS valid JSON; called newline delimited JSON (NDJSON; see http://ndjson.org/). You don't have to worry about these details if you use cchecks::cch_history(), which takes care of downloading the file and reading in the compressed NDJSON. On the command, you can do e.g, download the file, save to a .json.gz gzip-compressed file extension, then in the next line decompress the file with gzip, then pipe to jq, and use head to get the first 10 lines
curl -vL https://cranchecks.info/history/2020-04-01 > 2020-04-01.json.gz
gzip -dc 2020-04-01.json.gz | jq . | head -n 10

see https://cran-checks-docs.netlify.app/#history
I think the issue can be closed :-)

thanks!


Make shortcuts in storybook optionable or move to addon

Issue details
On one of the components that we have in our storybook, we have several shortcuts that we want add functionality to. One of them overlaps with storybook default one ⌘ ⇧ C, and disable us to handle this shortcut properly on the component.
My proposal is to add the possibility to enable or disable shortcuts in storybook through addon-options, keeping them as enabled by default.

Hello @Kiwka @igor-dv 👋
I'd love to take this up!
Does this spec seem fine to you folks?
setOptions({
    ...
    enableShortcuts: false, // true by default
})

Sure @PunitGr go for it

Thanks @PunitGr for looking into this 🙇♀

Released as 4.0.0-alpha.0


[Feature Request] Programmatically Highlight or Scroll to Search Results

Context

[X] This issue is not a bug report. (please use a different template for reporting a bug)
[X] This issue is not a duplicate of an existing issue. (please use the search to find existing issues)

Description
In our project we use Monaco Editor (via ngx-monaco-editor port for Angular) for config editing. There's a need to implement search and present results functionality.
There are two options that satisfy user.
First: search and highlight
Multiple highlighting would be great, but if not, highlighting the first match also works.
E.g. after monaco.editor.searchAndHighlight('world');

editor should look like

Second: search and scroll to
Here I think we could only scroll to the first match.
E.g. after monaco.editor.searchAndScrollTo('comment');

editor should look like

So far I could only find examples of syntax highlighting, but not this. So, I considered this functionality missing.
Basically, it's programmatical Ctrl+F, but with possibility to highlight multiple search results in the same time (by modifying HTML from text to text I guess).

Search and highlight functionality appeared to be supported already, and here's how to use it.
The issue is closed.


feat-006:raw output mode

I converted any responses of commands to Hash object but  sometimes raw output can be helpful.
So output mode should be made.

to put this keyword for every method is not good idea.


Improve pre-installation instructions

Move the pre-installation instructions to before the installation instructions. Expand on requirements for Debian/Ubuntu.

@jtcohen6 — is anyone on your team well-placed to review this? It's all latin to me!

Hey @brylie, since each of these pre-installation requirements applies to a much smaller subset of users, I'd rather keep them further down on the page, and keep the more generally applicable information about brew, pypi, and building from source up top. That said, I think it would make a lot of sense to include a sentence near the top of the page to the effect of:
If you use CentOS, Debian/Ubuntu, or Windows, some [pre-installation setup](#pre-installation-requirements) is required.

I understand that not all operating systems have the same amount of set-up.
However, the document flows more naturally when the prerequisites are described first followed by the installation. Providing a table of contents makes it easier for the reader to skip to the relevant sections, if the prerequisites are not relevant.

Since there's a table of contents in the right hand pane, I don't think we would want one at the top of the page as well. I agree with Jeremy here — even though the flow isn't linear, I'd prefer if this information is not at the top of the page. I think a hyperlink in the first paragraph is the right move

I spent some amount of time (15-30 minutes) troubleshooting the dbt installation on a fresh version of Ubuntu 20.04, whereas a clearly organized installation document could have cut that time and confusion down significantly.
Every person who installs dbt will have some prerequisites that don't come pre-installed on the OS:

MacOS: Homebrew and Python 3
Windows: Git and Python 3
Debian/Ubuntu: utilities related to detecting OS version and pip

It is conventional to put prerequisites before installation in technical documentation.
The left-side table of contents along with a friendly, intro message like "Hey friend, there are some prerequisites you need on your OS before installing dbt. If you think you've got the prerequisites covered, feel free to skip to the relevant installation section." would both assist readers who want to get straight to installation.
I have closed this pull-request as we seem to have artistic differences, but urge the dbt documentation team to reconsider the structure of this document.

In addition to Git and Python 3, both Windows and Linux will fail to install dbt if pkg-config is not installed.
Please test these installation instructions by observing someone who is not familiar with dbt follow the instructions on a fresh operating system. I believe there are some tacit steps and prerequisites that are missing from the documentation and have been inadvertently suppressed by core developers who are more familiar with dbt than new users.


koordlet: add flag to support disable querying kubelet configuration

Signed-off-by: Joseph<EMAIL_ADDRESS>Ⅰ. Describe what this PR does
fix #815 , add flag to support disable querying kubelet configuration.
This is a short-term workaround. I will remove this flag after thinking of a better solution.

V. Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in make test

/area koordlet

/milestone v1.1


Update CONTRIBUTORS.md

@P-Pavan , thanks Pavan for your contribution!
Don't forget to follow me on GitHub and stay tuned for updates to this organization.
Thanks, and have a good day ahead!