basic network matrix

Please read contributing guidelines and remove this line.

Benchmark results
No metrics with a significant change found.

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

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,744
1,556 (-1%)
708 (-1%)
761 (-3%)
777

proof_construction_time_sha256_30_ms
11,418 (-1%)
3,074
1,373 (-2%)
1,424 (-2%)
1,461 (-1%)

proof_construction_time_sha256_100_ms
43,983
11,809
5,424
5,397 (-5%)
5,702

proof_construction_time_poseidon_hash_ms
79.0
34.0
34.0
59.0 (+4%)
87.0

proof_construction_time_poseidon_hash_30_ms
1,527
421
202
222
265

proof_construction_time_poseidon_hash_100_ms
5,640
1,510
671 (-1%)
716
745

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,244
92,970
178,024

l1_rollup_execution_gas
842,904
1,576,526
3,361,636

l2_block_processing_time_in_ms
257 (-1%)
451
813 (-1%)

l2_block_building_time_in_ms
11,336
22,456 (+1%)
44,793 (+1%)

l2_block_rollup_simulation_time_in_ms
11,335
22,456 (+1%)
44,793 (+1%)

l2_block_public_tx_process_time_in_ms
9,658
20,612 (+1%)
42,890 (+1%)

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

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
3,039 (+1%)
3,917

node_database_size_in_bytes
12,632,144
16,711,760

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
92.7 (-6%)
383 (-5%)
21,735
44,860
N/A

private-kernel-inner
180 (+2%)
680 (-4%)
72,544
45,007
N/A

private-kernel-reset-tiny
314 (-1%)
689 (-4%)
65,593
44,846
N/A

private-kernel-tail
167
134 (-2%)
50,644
52,257
N/A

base-parity
5.57 (-1%)
N/A
160
96.0
N/A

root-parity
35.2 (-3%)
N/A
73,948
96.0
N/A

base-rollup
3,473 (+1%)
N/A
189,136
664
N/A

block-root-rollup
41.1 (-2%)
N/A
58,205
2,448
N/A

public-kernel-setup
85.6 (-1%)
N/A
105,085
71,222
N/A

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

public-kernel-tail
861
N/A
390,582
16,414
N/A

private-kernel-reset-small
306 (-3%)
N/A
66,341
45,629
N/A

private-kernel-tail-to-public
759 (+13%)
588 (-5%)
455,400
1,825
N/A

public-kernel-teardown
83.2 (-2%)
N/A
105,349
71,222
N/A

merge-rollup
20.7 (+1%)
N/A
38,174
664
N/A

undefined
N/A
N/A
N/A
N/A
83,611 (+6%)

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
346 (+1%)

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

MultiCallEntrypoint:entrypoint
1,920
11,731
405

FeeJuice:deploy
1,376
11,731
383 (-2%)

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

SchnorrAccount:entrypoint
2,304
11,731
394 (-1%)

Token:privately_mint_private_note
1,280
11,731
99.8 (-5%)

FPC:fee_entrypoint_public
1,344
11,731
25.8 (-4%)

Token:transfer
1,312
11,731
232 (+2%)

Benchmarking:create_note
1,344
11,731
86.6

SchnorrAccount:verify_private_authwit
1,280
11,731
27.7

Token:unshield
1,376
11,731
530

FPC:fee_entrypoint_private
1,376
11,731
698 (-6%)

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

Function
time_ms
bytecode_size_in_bytes

FeeJuice:_increase_public_balance
58.3 (+3%)
7,101

FeeJuice:set_portal
10.6 (+5%)
2,128

Token:constructor
83.3 (+2%)
25,285

FPC:constructor
56.0 (+1%)
17,853

FeeJuice:mint_public
38.1 (-7%)
5,415

Token:mint_public
69.9 (-3%)
10,101

Token:assert_minter_and_mint
40.4 (+1%)
6,844

AuthRegistry:set_authorized
48.5 (-1%)
3,969

FPC:prepare_fee
239 (-4%)
6,747

Token:transfer_public
33.7 (+8%)
38,126

FPC:pay_refund
54.1 (+2%)
9,398

Benchmarking:increment_balance
1,209 (+1%)
6,179

Token:_increase_public_balance
40.0 (-2%)
7,705

FPC:pay_refund_with_shielded_rebate
62.3 (-6%)
9,881

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.168 (+5%)

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

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

batch_insert_into_append_only_tree_16_depth_ms
2.18 (-2%)
3.87 (-2%)
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.113 (-2%)
0.109 (-3%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
11.2 (-2%)
17.6
31.0 (-1%)
59.1
114 (+1%)

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.107 (-2%)
0.102
0.101
0.102
0.102 (+1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
14.3
25.9 (+1%)
44.1
82.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.108
0.104 (+1%)
0.107
0.101
0.102 (+1%)

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

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

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

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

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
64,779
668,997

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


update cargo to 0.11, closes #171

updated! with the help from folks at #hyper i was able to update the solution, it was suggested to spawn a thread with the blocking computing and then send the output to the Body
might still need some review!
cheers :)

Thanks for the update. It looks good to me. There are a couple of warnings from the compiler which look like they should be addressed though.

yeah, sorry forgot to remove the line that was triggering the code unreachable warning

Thanks!


Change tr invocation in setup script

Preface
Hi,
First and foremost: Apologies if this isn't the correct workflow for opening a pull request. The contributing page made it seem like this was an appropriate way to make relatively minor contributions, but if there are steps I should've taken first (like posting on the mailing list), I can absolutely do that and close this.
Update to the tr call in the setup script
I'm proposing a couple of changes to the tr call in the setup script: One enhancement and one small fix for users trying to run the setup script on OS X (I'm running 10.11.3, but I imagine it affects previous OS X versions as well).

Use [:alnum:] instead of enumerating the characters. Also add a small subset of punctuation characters that won't cause horrible problems, but allow a slightly larger universe of characters to create the secret from.

Set LC_CTYPE. In OS X, at least, tr will fail miserably when reading from /dev/urandom. I suppose this is probably because tr encounters non-UTF sequences in /dev/urandom and then bails out. I don't think this change will affect other OSes, but I could certainly wrap this in an $OSTYPE check if it eases anyone's mind.

Update the README
This is explained in the commit, but I think the README should say source cmd/setup.sh instead of just cmd/setup.sh

Hey Wayne:
You're absolutely right that this is the correct flow for contributions. Those are some pretty big bugfixes, so it's much appreciated.
As it turns out, another developer sent me a cmd/setup.sh (outside of Github) that fixed the bugs you mentioned and many more. It's really my fault for not getting it up here sooner.
I'll run some tests and have the fixed cmd/setup.sh integrated shortly. Apologies for any trouble, and thanks again. Let me know if there's anything else you need to get started.
Evan


Beta 21 missing Nuxt module

Looks like beta 21 has moved to a full nuxt module instead of the plugin install from beta 20 but the actual package built is missing the Nuxt module 😬.
ERROR  Error while requiring module floating-vue/nuxt:
Exploring the installed package shows no nuxt module file was included.

Added in Beta 22


vscode-lldb ignores lldb.library and lldb.libpython if their values are default

OS: NixOS
VSCode version:
Extension version: 1.5.1
Toolchain version: <!-- Name and version of the compiler you used.  Run <compiler> --version for C++ or rustup show for Rust. -->
Build target:
Python version:

So I'm using NixOS and since all the library locations are non-standard, I would like to patch the package.json to set the default value of lldb.library to point to the current liblldb directory. But it seems that the plugin ignores the value if its the default value. I think the plugin should ignore it if and only if it's not set or is an empty string.

Debug log

I think the ideal behavior would be to ignore default value only when it's undefined. For users who installed the extension from marketplace, there would be no difference, since lldb.library defaults to undefined.

But it seems that the plugin ignores the value if its the default value

It's set up that way because normally CodeLLDB uses liblldb bundled with the extension.  "lldb.library" setting allows to use external liblldb, which is desirable in some cases (e.g. when debugging Swift).
I am not familiar with NixOS, so I don't understand the context of what you are trying to do.  Are you changing the layout of vsix package?   Why?

On NixOS, all the libraries are installed under /nix/store/$hash-$packagename, including glibc and ld-linux-x86-64.so.2. The liblldb bundled with your package has a dependency on libpython3.5.so (or something similar) which is non-existent on NixOS so I would like to use the system liblldb instead.
I want to achieve this by patching package.json during the installation of this extension to add default values to lldb.library and lldb.libpython so that they point to the currently installed libraries on the system. But, as said before, this extension ignores default values.

It's set up that way because normally CodeLLDB uses liblldb bundled with the extension. "lldb.library" setting allows to use external liblldb, which is desirable in some cases (e.g. when debugging Swift).

Not ignoring the default value will not have any impact on users using unpatched package.json since currently both the default value of lldb.library and lldb.libpython are not set.

IMO this is a temporary solution, the ideal solution would be to make the dependency on bundled lldb optional just like what the rust-analyzer plugin is doing.

On NixOS ppl usually use Nix to install vscode extensions because 1. reproducibility 2. some extensions need to be patched, like this one. The building process is basically unpacking the vsix file and then copy everyhting inside that archive into a folder under /nix/store dedicated for vscode extensions. I would like to patch package.json during this process so that other installing this extension doesn't need to manually search under /nix/store for the location of liblldb and then modify the config in vscode.

IMO this is a temporary solution, the ideal solution would be to make the dependency on bundled lldb optional and defaults to use system's lldb, just like what the rust-analyzer extension is doing.

Sorry, but this isn't going to happen. I specifically went away from using system liblldb, because there's just too much variability between versions on people's machines.  I build my own lldb, which has been patched to require minimal dependencies, and can load libpython dynamically, or even work without Python at all (with reduced functionality).

The liblldb bundled with your package has a dependency on libpython3.5.so

Are you sure?  I've a test that verifies that the binaries I ship do not depend on anything but a handful of core system libraries.   libpython3.5 is definitely not on that list.
I'll check out you PR later when I have a bit more time.

❯ ldd extension/lldb/bin/lldb
        linux-vdso.so.1 (0x00007ffc27709000)
        libpthread.so.0 => /nix/store/6m2k8kx8h216jlx9dg3lp4m90bz05yck-glibc-2.30/lib/libpthread.so.0 (0x00007f50a5c61000)
        liblldb.so => /tmp/codelldb-x86_64-linux/extension/lldb/bin/../lib/liblldb.so (0x00007f50a2134000)
        libpython3.5m.so.1.0 => not found
        libgcc_s.so.1 => /nix/store/6m2k8kx8h216jlx9dg3lp4m90bz05yck-glibc-2.30/lib/libgcc_s.so.1 (0x00007f50a211a000)
        libm.so.6 => /nix/store/6m2k8kx8h216jlx9dg3lp4m90bz05yck-glibc-2.30/lib/libm.so.6 (0x00007f50a1fda000)
        libc.so.6 => /nix/store/6m2k8kx8h216jlx9dg3lp4m90bz05yck-glibc-2.30/lib/libc.so.6 (0x00007f50a1e1b000)
        /lib64/ld-linux-x86-64.so.2 => /nix/store/6m2k8kx8h216jlx9dg3lp4m90bz05yck-glibc-2.30/lib64/ld-linux-x86-64.so.2 (0x00007f50a5c84000)
        libdl.so.2 => /nix/store/6m2k8kx8h216jlx9dg3lp4m90bz05yck-glibc-2.30/lib/libdl.so.2 (0x00007f50a1e14000)

Sorry, but this isn't going to happen. I specifically went away from using system liblldb, because there's just too much variability between versions on people's machines. I build my own lldb, which has been patched to require minimal dependencies, and can load libpython dynamically, or even work without Python at all (with reduced functionality).

That's fine

You should be looking at liblldb.so, the lldb executable normally isn't used:
$ ldd lldb/lib/liblldb.so
	linux-vdso.so.1 (0x00007ffecc7ad000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fafefe13000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fafefc0f000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fafef9f0000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fafef7d8000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fafef43a000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fafef049000)
	/lib64/ld-linux-x86-64.so.2 (0x00007faff4c0d000)


Issue related to saving checked in assets.

Hello SRombauts,
Thanks to the report of a user, we came across an issue where saving an asset that is currently checked in will cause it to be checked out immediately without any confirmation. This isn't exactly a bug but causes issues with workflow so you can see this as more of a feature request. The favorable behavior would mimic the Perforce plugin where it asks if you would like to check out the asset, make it writable, or cancel the process. I put a bug report in for the issue and made it public so you can track it here
You can see a picture of what the Perforce behavior looks like on the Answerhub post that is linked to that bug report.
Thank you for your time!

Hi @Matthew-Clark, I am not totally sure on how and if I could trick Git on working with a "checkout" operation it does not know about. So in the Git plugin, every files are always said "checked-out".
But there IS a change introduced on one previous version of the Engine that broke the way the Git plugin is working: previously, you where not abled to checkin a file when the plugin returned CanCheckout()==false
=> now those unchanged files are displayed in the checkin window, which is a mess...

Ah, I'm not all that familiar with using Github's source control myself so I'm not completely aware of how it handles the checking out and such. As I mentioned to the user, if a checkout-type system isn't possible, would it be possible to add a confirmation window of sorts when saving while connected to Github source control? Even if this is an optional thing and isn't on by default, it would be helpful for the user's case.
I'm going to go ahead and change the JIRA report to a Feature Request.

Yes it's entirely possible, even easy to fake the 'checkout' workflow.
It should be optionnal, but it could becomes the default.
Do you have a time frame ? Could it make it into 4.14 or is it already too late?

I can't give any exact deadlines but it would be best if you could get it in within a couple of weeks.

This is fixed by supporting Git LFS 2 File Locks in v2.3 of the plugin #36


Add enum type to Grid component and add new filters

Add support for enum as a type for a Grid column.
Add a new filter in for enum columns, which allows to select several enum types
Add support for Guid as a type for a Grid column
Add a new filter between to numeric and date-time columns which allows to filter belonging to a closed interval
Create an example project BlazorBootstrap.Playground.GridServerTests which illustrates the work with enum and Guid types for Grid

@pacaya Thank you for the pull request. We appreciate your efforts. We're making some changes to our core logic and have moved from the master branch to the main branch. Please fork from the main branch and submit a new pull request.


Store vertex color alpha into a second color attribute

It's possible that I don't fully understand Blender, but it's my understanding that gltf lets you store vertex colors in RGBA format while Blender only accepts vertex colors in RGB format. So the importer ends up discarding the extra alpha values of the vertex colors in a gltf file. Is it possible to stash those alpha values into a second vertex color attribute during import? So the importer would create a COLOR_0 and a ALPHA_0/COLOR_0_ALPHA or something like that.

Blender switches from RGB to RGBA vertex colors somewhere between 2.79.0 and 2.79.4. Code on master / next release will cover for that.


[Bug] Broken query when using openTSDB 2.2 mode

Some queries get broken when using the 2.2 mode, for example:
min:ping.timeout{dst_host=foo*|bar*}
this gets converted to
min:ping.timeout{dst_host=iwildcard(foo*|bar*)}
which is invalid. The only solution I can think so far is to let Bosun expand the * like in 2.1, so that the query would become:
min:ping.timeout{dst_host=literal_or(foo1|foo2|bar1|bar2)}

https://github.com/bosun-monitor/bosun/issues/1495


Add help link to NavRail

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 99.651%

Totals

Change from base Build<PHONE_NUMBER>0:
0.006%

Covered Lines:
12808

Relevant Lines:
12809

💛  - Coveralls


how can i run my web application in google chrome

Hi,
Due to a lack of information, closing this issue.
Thanks


Send a notification when IMAP errors happens

Reason
Inform the user about any IMAP errors
Description
Fire a notification using the capacitor local notification api when a IMAP errors happens
Success Criteria

[ ] a working local notification fired to the user after an IMAP error happen

Additional Information
No response

see https://github.com/tiki/capture-receipt-capacitor/issues/305#issuecomment-1774948205


Add custom attributes to categories

Hello.
I added custom attributes for categories. #34

Hi,
Thanks, for PR. Can you please add tests for this.

Code style also need to be fixed https://travis-ci.org/github/Bukashk0zzz/YmlGenerator


[BUG] jacocoExclusions is very long

Describe the bug
The jacocoExclusions list is quite long, https://github.com/opensearch-project/anomaly-detection/blob/main/build.gradle#L478. Maybe we're just ignoring coverage thresholds, or they are too high? In either case those thresholds are likely not useful.
Either fix the TODOs and reduce the list, or remove/reduce the coverage thresholds.

The restful action layer is covered by integration tests, so they are excluded in the UT. The transport action layer are still missing some coverage. I am adding more unit tests for the following classes in transport layer for AD.
    'org.opensearch.ad.transport.StopDetectorRequest',
    'org.opensearch.ad.transport.StopDetectorResponse',
    'org.opensearch.ad.transport.CronRequest',
    'org.opensearch.ad.AnomalyDetectorRunner',

    'org.opensearch.ad.transport.DeleteAnomalyDetectorTransportAction*',
    'org.opensearch.ad.transport.GetAnomalyDetectorTransportAction*',
    'org.opensearch.ad.transport.SearchAnomalyResultTransportAction*',
    'org.opensearch.ad.transport.SearchAnomalyDetectorInfoTransportAction*',
    'org.opensearch.ad.transport.AnomalyDetectorJobRequest',

    'org.opensearch.ad.transport.DeleteAnomalyResultsTransportAction',
    'org.opensearch.ad.transport.handler.AnomalyResultBulkIndexHandler'

Also, these 2 task runners also needs more tests. We can address them in the next.
// https://github.com/opensearch-project/anomaly-detection/issues/241
'org.opensearch.ad.task.ADBatchTaskRunner',
'org.opensearch.ad.task.ADTaskManager',

break down this issue into several sub-issues in 492 and 493.


More information on making a more complex html structure

Could you please add more info about what I should change to make a more complex html folder structure in src?
Until now I was using the basic structure. Then I tried to split my components into folders ( moved the buttons into a 'buttons' folder, which is still inside 'components'). It didn't work by default.. I tried changing paths in the gulpfile. Still - no success. Then I looked at the generated data.json file and I saw that there was json for the folder 'buttons' but no json for the files in it.
I may have missed something simple. Help me Obi-One Kenobi, you're my only hope!

What version are you running?
Grouped materials came in 1.0

It was 0.7.0. Just updated it. Now I'm trying to figure out how does the new one work (with the hlep of the docs)... the links in the menu for my components do not compile correctly (and I just added custom html files in the components and structures folders). So I keep getting the same mistake "Cannot GET /src/materials/components.html"... still reading and trying to find where my mistake is

Apologies on the lack of documentation; been trying to improve it. Hopefully I can be some help here.
"Materials" are just partials that can be used when templating a page. They are not compiled or viewable on their own served pages. They are only used as partials. e.g. {{> material-name}}.
The pages Fabricator actually generates and serves up are in src/views or in src/views/sub-dir. By default, Fabricator puts the toolkit doc/style guide pages in root so that http://localhost:3000 opens up to your toolkit homepage. However, you don't have to keep it that way. You can organize your views however you want. They are all templated using the same context (outlined here under "Context") so you can just construct views and call them whatever you want. Checkout the fbrctr.github.io source as an example.
The default template for the side menu is also pretty basic. It just iterated over the materials object in the page context and adds a list group https://github.com/fbrctr/fabricator/blob/95f4cf42292744c4a7e1767e65616afe62b891e5/src/views/layouts/includes/f-menu.html#L12.
You could change this to be more granular. I am currently doing something like this on a project:

	Elements

		{{#each materials.elements.items}}

			{{name}}

		{{/each}}

	Components

		{{#each materials.components.items}}

			{{name}}

		{{/each}}

	Cards

		{{#each materials.cards.items}}

			{{name}}

		{{/each}}

When you run $ npm  start it compiles everything in src and dumps the artifacts in dist.
dist is the folder that is served up to http://localhost:3000. You can look in that folder to see what the build is outputting and what you can hit in a browser when the server is running.

I know most of the things you just explained to me. I'm just not very familiar with JS templating for now...
Your documentation is pretty good, tho. After rereading it and looking up a few more articles on handlebars templating, I think I can fix what I wanted to.
Thanx! (the problem was that the project I'm working on got very big and I needed the "grouped materials" feature) The toolkit you did is pretty awesome... I did look up many styleguide generators before choosing fabricator... GJ! :)

I am having a Cannot GET error as well. It was working just fine when I first built the project. But when I stopped the Localhost3000 and came back to it with npm start and a lot of things come back with "Cannot GET" like my structures. The structures folder in src and all the html files I made are still there but they won't display in the Localhost3000. Also they're not showing up in the dist folder. I've heard you have to edit the gulp file to fix this but I wouldn't know where to start in editing it. I'm still very much a beginner.


Suppress inline warning for search protocol protobuf conversion test.

@baldersheim : please review
@havardpe : FYI

[100%] Built target searchlib
In file included from /home/tegge/git/vespa/searchlib/src/vespa/searchlib/engine/search_protocol_proto.h:5,
                 from /home/tegge/git/vespa/searchlib/src/vespa/searchlib/engine/proto_converter.h:11,
                 from /home/tegge/git/vespa/searchlib/src/tests/engine/proto_converter/proto_converter_test.cpp:4:
/home/tegge/git/vespa/searchlib/src/vespa/searchlib/engine/search_protocol.pb.h: In member function ‘virtual void DocsumRequestTest_require_that_highlight_terms_are_converted_Test::TestBody()’:
/home/tegge/git/vespa/searchlib/src/vespa/searchlib/engine/search_protocol.pb.h:4630:13: error: inlining failed in call to ‘void searchlib::searchprotocol::protobuf::StringProperty::set_name(const char*)’: --param inline-unit-growth limit reached [-Werror=inline]
 4630 | inline void StringProperty::set_name(const char* value) {
      |             ^~~~~~~~~~~~~~
/home/tegge/git/vespa/searchlib/src/tests/engine/proto_converter/proto_converter_test.cpp:496:19: note: called from here
  496 |     prop->set_name("bar");
      |     ~~~~~~~~~~~~~~^~~~~~~

There are multiple such complaints, about set_name and set_value on StringProperty and TensorProperty.
Environment is Ubuntu 22.04, with gcc 11.3.0 and protoc 3.12.4.

I am not a big fan of polluting our code handling all variations of OS compiler versions.
I suggest we discuss this tomorrow.


Restrict type up input file

When using the image input button, it would be nice to restrict to using only image type files using accept

A note on accept..

The accept attribute doesn't validate the types of the selected files; it provides hints for browsers to guide users towards selecting the correct file types. It is still possible (in most cases) for users to toggle an option in the file chooser that makes it possible to override this and select any file they wish, and then choose incorrect file types.

Because of this, you should make sure that expected requirement is validated server-side

I appreciate the reminder! However since everything runs with WASM on the client there is no server side to validate things. Correct me if I'm wrong, as I'm by no means a security expert, but since everything is running client side, we don't have to be concerned with incorrect files.
This feature is just a gentle nudge for the user to only be able to upload something that will work and to make it easier since it highlights the "accepted" files. If they choose to circumvent it for whatever reason, that's on them lol.

Yeah.. just mentioning in case the goal was to disable upload of certain
files 👏
On Sat, Dec 2, 2023, 3:19 PM Technickel @.***> wrote:

I appreciate the reminder! However since everything runs with WASM on the
client there is no server side to validate things. Correct me if I'm wrong,
as I'm by no means a security expert, but since everything is running
client side, we don't have to be concerned with incorrect files.
This feature is just a gentle nudge for the user to only be able to upload
something that will work and to make it easier since it highlights the
"accepted" files. If they choose to circumvent it for whatever reason,
that's on them lol.
—
Reply to this email directly, view it on GitHub
https://github.com/Technickel-Dev/triangulation/issues/7#issuecomment-1837233144,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHGOB46ADS7MT242FP4FVYDYHN5M5AVCNFSM6AAAAAA5445GF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZXGIZTGMJUGQ
.
You are receiving this because you commented.Message ID:
@.***>

I appreciate you keeping an eye out!
Good question, given I don't have any preference, I'd be happy with image/* and if there are problems down the line with a certain image format I figure out how to support that later


Google: What determines which UI is displayed?

Avoid duplicates

[X] Question is not already answered in the FAQ
[X] Question is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[ ] Question has not already been asked in another issue
This is a sub-set of a previous question #2379.

Your Question
I have a new Google UI showing on an Android 8 device although the version number of the Exposure Notifications System has not changed from<PHONE_NUMBER>0.
How did the UI change? Why is another device showing a different UI with the same version of ENS installed?

Newest UI

Previous UI

Original UI

An Android 10 device, which was yesterday showing the Google COVID-19 UI with Corona-Warn and Open on the same line (labelled above as previous UI), is today showing the UI with Open missing on that line (labelled above as Newest UI). Instead tapping on Corona-Warn brings up a new UI level showing Open app and a greyed-out section with a slider containing the text "Automatically warn others ...".
The version number of the Exposure Notifications System hasn't changed<PHONE_NUMBER>0) and CWA is still at version 1.12.0.
I have to assume that Google is dynamically controlling the behavior of the COVID-19 Exposure Notifications System and I can't find any documentation about how this works or what parameters are available to them. The only related data exchange directly with Google I found documented under Telemetry Design.

Under such framework conditions it would be unnecessarily difficult to put an application on a 'safe and functional' basis.

@Jo-Achim
This question is also related to the unanswered discussion in https://github.com/corona-warn-app/cwa-app-android/issues/2081#issuecomment-759981811 regarding the major outage "[EN-Google] No actualization, even not after new install, stuck in "Data is being downloaded..." / DE: Aktualisiert nicht mehr und nach Neuinstalation Daten laden endet nicht" where we heard that Google fixed the issue according to the statement quoted in https://github.com/corona-warn-app/cwa-app-android/issues/2081#issuecomment-759964666. Noticeably the fix did not change the version number of the Exposure Notifications System.

Settings UX changes in the updated release notes for v1.8 of the Google API for Exposure Notifications say:
"Exposure checks" and "Delete random IDs"
The Exposure checks and the Delete random IDs button have both been moved from the main settings list to the overflow menu. There have been no functional changes to these options.
So we now have confirmation that the currently displaying Google COVID-19 Exposure Notifications UI version is the intended one.
I'm not anticipating receiving any more detailed information from Google, so I am now closing this issue.


There seems something wrong with the dirsearch

the dirsearch seems don't work correctly,when i run the dirsearch agent install in the reconness with my own command,the dirsearch seems don't work, and the terminal and logs output nothing,and there is no result at the Directories tag.But when i scan the target with the dirsearch by myself at my vps,it works good.

I working fine here


InlineCreationRows in Fiori Elements with OData V4 does not work

Hello All,
I have created a Fiori Elements application for the purpose of table maintenance. The aim is that changing the mode of creation to be made on table level (like SM30) rather than on Object Page level. However the configuration, creationMode "InlineCreationRows", does not work so far as expected. Supposingly it should be creating new empty row in the table and let the user to enter the data on the same level. But instead, it only adds an empty row to the table and keeps it read-only, not editable. I appreciate it for any comment.
UI5 Version: 1.114.0
        "targets": {
            "RepairModuleProductList": {
                "type": "Component",
                "id": "RepairModuleProductList",
                "name": "sap.fe.templates.ListReport",
                "options": {
                    "settings": {
                        "entitySet": "RepairModuleProduct",
                        "variantManagement": "Page",
                        "initialLoad": true,
                        "navigation": {
                            "RepairModuleProduct": {
                                "detail": {
                                    "route": "RepairModuleProductObjectPage"
                                }
                            }
                        },
                        "controlConfiguration": {
<EMAIL_ADDRESS>{
                                "tableSettings": {
                                    "type": "GridTable",
                                    "creationMode":{
                                        "name": "InlineCreationRows",
                                        "createAtEnd": true
                                    },
                                    "enablePaste": true,
                                    "enableFullScreen": true,
                                    "enableMassEdit": true
                                }
                            }
                        }
                    }
                }
            },
            "RepairModuleProductObjectPage": {
                "type": "Component",
                "id": "RepairModuleProductObjectPage",
                "name": "sap.fe.templates.ObjectPage",
                "options": {
                    "settings": {
                        "editableHeaderContent": false,
                        "entitySet": "RepairModuleProduct"
                    }
                }
            }
        }

Thanks in advance,
Merve

Hi @cbsmerveguel, sap.fe is part of SAPUI5 not of OPENUI5. GitHub is a place for managing issues for OPENUI5 only.
Please, open a ticket in SAP ticket system for managing incidents.


Fix build for GHC 7.10

genifunctors no longer builds on GHC 7.10.1, so I had to make some slight changes to make it work:

In template-haskell-<IP_ADDRESS>, Pred became a type synonym for Type, so I changed usages of ClassP c [VarT v] to its new equivalent, AppT (ConT c) (VarT v).
In template-haskell-<IP_ADDRESS>, all TyVarBndrs are now of the form KindedTV, which means that genifunctors rejects types of kind *, since they're now of the form KindedTV tv StarT. I added another case to unPlainTv to handle this.
GHC 7.10 is a lot more strict with TH-generated variable names, and the names for values with list or tuple types (e.g., _[]_0 or _(,)_0) will be rejected as invalid syntax. I use the newSanitizedName function to change values of list or tuple types to _List_<num> and _Tuple<degree>_<num>, respectively.

Thanks!


Add new languages to type sample page

Need to test the following languages on http://esri.github.io/calcite-web/page-layouts/type-comparison/
Hungarian
Hindi
Slovak
Bosnian

Looks like we will add Hindi, Bosnian, and Slovak. Just need to add them to site and verify.

addressed, will be part of next push

fyi this page has moved to http://esri.github.io/calcite-web/examples/i18n/


Intel graphics card offset issue

This issue only appears on Intel graphics card.
To reproduce:

Using an Intel only (e.g. Macbook Pro 13'') laptop, or use gfxCardStatus to disable the discrete AMD/nVidia Graphics card.
Remove other layers and only focus on the choropleth layer (this bug is likely to affect all layers but it is easier to bug on the choropleth layer with an underlying map for reference)
Zoom into street level and check the choropleth contours, there is positive offset in y direction.

Possible causes:

Since this only happens on Intel cards, the code logic should be correct;
We only observe the offset in the y direction, and the offset scales proportionally as we zoom in and out, so very likely this is related to the mercator projection, in which the calcualtion for latitude invovles non-linear transformations (tan/log); where the calculation for the longitute (linear) does not suffer from this. And there might be precision issues/bugs in the Intel Math library (thanks @shaojingli for the hints).
highp mediump related? maybe?

I can verify that the inaccurate tan() function from Intel's GLSL compiler is the root cause of this issue. I created a "intel_workaround" branch and replaced the tan() with my newly implemented tan_fp64(). The issue was no longer there. Please help me verify.
Of course, using an fp64 function seems to be an over-kill for this. We only need to have a more accurate tan() function in single precision.

@gnavvy Fix published in v3.0.0-beta17. Please reopen if not working.


Is it possible to combine multiple .caffemodel into one?

I want to be able to combine x.caffemodel with y.caffemodel. Is that possible and are there any existing examples of this?
Thanks.

caffemodel files are protobuf files. You should be able to open/modify them with a protobuf tool.

What tool can I use to do that with?

You can use Caffe python interface.
An example is here:
https://github.com/yahoo/caffe/blob/e107fb7a0d737868aff401ef954c1d8059e5e450/examples/net_surgery.ipynb
Pay attention to "In [8]  # Load the fully convolutional network to transplant the parameters."

@stickFigure1235 If this is addressed, please close the bug


Add config for testing against a FiaB

I plan to also add some short docs about starting a FiaB for this. What would be most appropriate, a .md file or something in the wiki or something else?

Added some newer configs and wrote a wiki page: https://github.com/DataBiosphere/saturn-ui/wiki/Develop-against-FiaB


Fix generic docs after pull #10

Resolve some issues discussed in pull #10.

Improved the wording again, see 821d30b.


Sway support

@luispabon sorry for the extremely late reply I have been pouring myself into another project for my robotics team for the past months.
Anyway, The reason I haven't merged this is as it stands now it has made one point clear to me. The way I have the extension modeled is not flexible enough to facilitate WMs such as Sway. Instead of having to add to the code an if for each environment variable I am likely going to investigate adding a way to specify the environment variable to check.
P.S. I will note that I will not be able to get to this any time in the near future as that other project still owns me :yum:. However, an update to the PR is welcome and again I apologize for being so late in replying to this.

No worries, we all have lives and stuff to get on with :+1:

Superseded by #5


[WIP]Sync addons with latest upstream, and update documentation

NOTE: This is not yet working
The Kubernetes addons in the documentation are completely out of date, for example they use ReplicationController which has long been deprecated in favour of Deployment. I've synced the addons to version 1.6 of the upstream repository and updated the documentation correspondingly. Fixes #868
The installed DNS addon is sadly not working for me, and I could really use some help in figuring out why. I suspect the issue is that the API server isn't reachable on https://<IP_ADDRESS>.
Basically, I'm seeing the following errors in the kubedns container in the kube-dns pod:
E0419 22:06:50.952662       1 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://<IP_ADDRESS>:443/api/v1/services?resourceVersion=0: dial tcp <IP_ADDRESS>:443: i/o timeout
I0419 22:07:20.444655       1 dns.go:174] DNS server not ready, retry in 500 milliseconds
F0419 22:07:20.944622       1 dns.go:168] Timeout waiting for initialization

Was seeing similar "Failed to list *v1.Service type errors" in another project, fixed with hermanjunge/kubernetes-digitalocean-terraform#31 and is possibly related to #865.

@5tefan Thanks for the input! I tried making the adjustments in your PR, but it didn't make any difference :( Looks as if <IP_ADDRESS> isn't available within the cluster.

@aaronlevy Hey, I hear you might be able to help out with this? I.e., you might understand why API Server isn't on https://<IP_ADDRESS> after being set up?

FYI: I setup a baremetal cluster today following the coreos docs, but I used this for kube-dns.
It's working great, no problems here.

@dpgeekzero Thanks for testing 🙂

would love to hear how this pans out

@dpgeekzero Did you use flannel or Calico?

Hey - Thanks for your help on these. I'm closing this PR because we've completely rewritten and moved the Kubernetes documentation. Take a look, if you like: https://coreos.com/tectonic/docs/latest/tutorials/kubernetes/getting-started.html


After releasing a package find the latest Automatic APIRevision with matching API surface and update the release information. (Release Date: ReleaseOn, Release Version: ReleasedAs)

This change is still required for C++ and Go.


Add example usage for Enhance

Hi there! We (the Enhance team) came across Drab today and thought it was super interesting. Here's a tiny PR that adds an example of how to use Drab with Enhance. Happy to make any changes that may be required!

@rossrobino Thanks! Stoked to hear you enjoyed playing around with it. Feel free to let us know if you have any questions, feedback, or requests on Discord if you like. Hope you continue to enjoy digging into it!
I've pushed the changes you requested :)


Add from_bounds and from_origin class methods

The rasterio.transform module has several methods for generating an instance of affine.Affine.  I don't think these methods are specific to rasterio, and given that they just call Affine class methods, I think it would be useful to define these here.
If you think this is a good idea I'm happy to write up a PR!

@geospatial-jeff thanks for the suggestion. I'm going to decline your offer because I want to keep this module free of GIS concepts like pixels and raster data georeferencing.


Thanks for reporting! Help welcome with this one

using document.activeElement IE11 is returning the Input and adding the :focus styles.
using document.activeElement Chrome is returning the body element, so no :focus styles are added.

the same issues effects checkbox as well.

adding the this.focus() to handleClick produces consistent behaviour between Chrome and IE. i.e. document.activeElement is returned as the clicked Input

It looks like the problem is that pageX and pageY in Edge/IE are reporting 0, but we are checking to see if they are not 0 here if (event.pageX !== 0 && event.pageY !== 0) this.blur(); to remove focus from the input. I will keep looking into why IE would be reporting 0 for the mouse event position. In the meantime, anyone know what the motivation was behind adding that check?

There is maybe another problem with the pageX/Y in IE.
We have the case that our users want to fill out the form with keyboard only. This works correctly when IE is in maximized.  Hitting the tab key for the next form field somehow doesn't work then.
I compared the values of pageX/Y from chrome and IE and they behave completely different. So maybe this check should be removed anyway.
Google material components have not implemented this blur behavior.


Update RELEASE.md

Makes sure the release process is documented. Should we also do this for Echo?
Ideally we'd automate this.

Yeah think that's a given.


Success Message doesn't show up

After successfully creating an Issue to the repository the text in fields still exists and the success message doesn't show up.
With sending the report I get the following message in the network tab:
{status: 8, message: "Undefined index: status"}
message: "Undefined index: status"
status: 8

It has the http status code 200.
The plugin is on kirby 3.36 and php 7.4.1 installed.

Thanks for reporting @amarsupial. I'll have a look on that.


Add dedicated script for Ubuntu 22.04

As can be seen here and here, Ubuntu 20.10+ use nftables instead of iptables, but the current Linux Kernel used for the WSL distro doesn't support this change. As a consequence, for Ubuntu 22.04, a specific command must be executed at the end to revert OS to legacy behavior (i.e.: use iptables-legacy instead of nftables).


Add PADLOCK_ASM to dso_defines rather than lib_defines

Since the padlock code is an engine, the assembler is for a module,
not a library link to when building a program...  there's a
distinction.
Fixes #2311

More fixes were needed, please reconfirm.

Ping @t-j-h

Ping

Merged.
master:
149c12d5e41b238ce4af6d1b6b3a767b40293bd7 Make the padlock engine build correctly
2fce15b58b2502a614529707eb45b6e5cac4eb15 Ensure configured module specific and application specific defines are used
88780b1c5f6000fe6731fec74efe697bcf493b6c Add PADLOCK_ASM to dso_defines rather than lib_defines
1.1.1:
e8926acfe25418d029656d4abb321096a2cf17c5 Make the padlock engine build correctly
5dcfd143e1409b0915875f9dcbbba253db41b138 Ensure configured module specific and application specific defines are used
9c8516b63cec92a53f3064ce3acb6d672eeea7a1 Add PADLOCK_ASM to dso_defines rather than lib_defines


Different height items cause wrong sorting animation order

Hi. I have noticed an issue. When items have different heights, the wrong item moves. In the repro, if you attempt to move 0 slowly down, you will notice that 2 moves before 1
Repro: https://codepen.io/anon/pen/EdNGOz

When dropping the sortable element, the sorting works as expected, so this is is related to the move events.

Have a look at:
SortableContainer/index.js at line 545
        const offset = {
          width: this.width > width ? width / 2 : this.width / 2,
          height: this.height > height ? height / 2 : this.height / 2,
        };

and SortableContainer/index.js at line 659
        } else if (this.axis.y) {
          if (
            index > this.index &&
            (sortingOffset.top + windowScrollDelta.top) + offset.height >= edgeOffset.top
          ) {
            translate.y = -(this.height + this.marginOffset.y);
            this.newIndex = index;
          } else if (
            index < this.index &&
            (sortingOffset.top + windowScrollDelta.top) <= edgeOffset.top + offset.height
          ) {
            translate.y = this.height + this.marginOffset.y;
            if (this.newIndex == null) {
              this.newIndex = index;
            }
          }
        }

and in that piece of code, this one:
            (sortingOffset.top + windowScrollDelta.top) + offset.height >= edgeOffset.top

If I remove offset.height the animations occur in the correct order, but only start when the top edge of the dragged element touches the element below.
Cause and solution
The offset should be calculated based on the dragged node and not the target. When the height of the dragged element (this.height) is larger than the height of the element being hovered over (height), the ternary condition kicks in and the bug is producted.
        const offset = {
          width: this.width > width ? width / 2 : this.width / 2,
          height: this.height > height ? height / 2 : this.height / 2,
        };

The solution for this error condition is to change offset to be simply:
        const offset = {
          width: this.width / 2,
          height: this.height / 2,
        };

Is there a reason why the dimensions of the target node is used here? If that is the case, would it be possible to override this with some configuration? Otherwise it can be fixed.

Another update: This produced other issues. I closed the pull request and will look further into the issue. Help is appreciated.

I'm running into this same issue, @adrianhelvik - and in fact I independently arrived at the same solution. Do you remember what the other issues you were running into with this fix? I'd like to get this solved.

Better repro: https://codesandbox.io/s/react-example-uyof2
Hmm. Well, if i remember correctly, the algorithm is incorrect due to the moment of the move being calculated from the target element and not the source element.
An element is pushed up when the bottom of the dragged element is past 50% of the target element's height.
A better solution would be to push up the element when enough space is available above to push it up, and then push it down when there is enough space below. This would require keeping track of the state of a DraggableItem (pushedUp: boolean).

I've submitted a PR to address this, #602.


Small bug with Slider control ?

Hi
I am guessing this is a V8 simulator bug with the slider ?  The light blue semi circles at the end of the slider background are not drawing properly ?  I havent tried this with V8 on my hardware, so cant say if its specific to simulator or not. See attached screenshot.

It was a bug in lvgl master a few weeks ago. Updating lvgl should solve the issue.

I have update all submodules in this repo. I hope this issue can be solved.

Thanks for the speedy update. Confirmed fixed for me

It seems to be OK to close this issue.


[App Request] InvoiceNinja 5

App Information

Name: InvoiceNinja
Short Description: Open source invoice, expense and time mgmt (and much more) platform
Official Website: https://invoiceninja.github.io/en/
GitHub Repository: https://github.com/invoiceninja
Docker Image: ghcr.io/invoiceninja/invoiceninja:5

Why do you want this app?
As a smart tech consultant working to bring smart tech to breweries and other beverage and food  businesses, I need a solid platform for tracking expenses and billing customers.  My first attempt with this was on umb rel, but it is clear your platform is much more dynamic.
Additional information?
The full stack requires nginx and mariadb.  And of course, I want to ocnfigure it behins swag for cert mgmt.
Here is a working compose file
services:
  app_proxy:
    environment:
      APP_HOST: invoice-ninja_nginx_1
      APP_PORT: 80
      PROXY_AUTH_ADD: false
      PROXY_AUTH_WHITELIST: /api/*
    container_name: invoice-ninja_app_proxy_1
  nginx:
    image: >-
      nginx:1.21-alpine@sha256:686aac2769fd6e7bab67663fd38750c135b72d993d0bb0a942ab02ef647fc9c3
    init: true
    restart: on-failure
    volumes:
      - ${APP_DATA_DIR}/config/nginx.conf:/etc/nginx/conf.d/nginx.conf:ro
      - ${APP_DATA_DIR}/data/public:/var/www/app/public:ro
    depends_on:
      - app
    container_name: invoice-ninja_nginx_1
  app:
    image: >-
      invoiceninja/invoiceninja:5.10.27@sha256:e5711a1fad103334692d5116ae0d4e62a384b08d7b52c1abb8c7ec33d526f699
    user: '1500:1500'
    restart: on-failure
    volumes:
      - ${APP_DATA_DIR}/data/public:/var/www/app/public:rw,delegated
      - ${APP_DATA_DIR}/data/storage:/var/www/app/storage:rw,delegated
    environment:
      APP_URL: https://in.gmartin.org/
      APP_KEY: ${APP_KEY:-unset}
      APP_DEBUG: false
      REQUIRE_HTTPS: true
      TRUSTED_PROXIES: '*'
      DB_HOST: invoice-ninja_db_1
      DB_DATABASE: invoiceninja
      DB_USERNAME: invoiceninja
      DB_PASSWORD: moneyprintergobrrr
      IN_USER_EMAIL: null
      IN_PASSWORD: null
    depends_on:
      - db
    container_name: invoice-ninja_app_1
  db:
    image: >-
      mariadb:10.5.12@sha256:dfcba5641bdbfd7cbf5b07eeed707e6a3672f46823695a0d3aba2e49bbd9b1dd
    user: '1000:1000'
    restart: on-failure
    volumes:
      - ${APP_DATA_DIR}/data/db:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: invoiceninja
      MYSQL_USER: invoiceninja
      MYSQL_PASSWORD: moneyprintergobrrr
      MYSQL_DATABASE: invoiceninja
    container_name: invoice-ninja_db_1

This has been added to BigBearCasaOS: https://community.bigbeartechworld.com/t/added-invoice-ninja-to-bigbearcasaos/1697?u=dragonfire1119


Specs2/Scalacheck to ZIO Test migration.

Pull request to close issue #94.

Amazing work!

Thanks a lot!
Would not have dared to start working on it, but your offer to help made me tackle this issue.  👍

Thanks a lot!
Would not have dared to start working on it, but your offer to help made me tackle this issue. 👍


[FEATURE] add ignore image list flag for supporting user to choose which one will be saved

Issue Description
Type: feature request
add flag --ignore-image-list to sealer build : sealer build --ignore-image-list ignoredlist
write ignored file:
[root@iZbp1daq0hry4n4gd6lelwZ]# cat ignoredlist
mysql:3.2
docker.io/library/nginx:alpine

when build : sealer will not save those images read from  ignorelist file.
Describe what feature you want
Additional context
Add any other context or screenshots about the feature request here.

@Stevent-fei Would you like to support this feature?

@Stevent-fei Would you like to support this feature?

ok


Error using Hyprland on Fedora38

Hyprland Version
Not installed yet
Bug or Regression?
Bug
Description
I just installed the sway spin of fedora to install hyprland (Fedora Linux 38 (Sway)) i've followed the instruction from hyprland's wiki and when i go to sddm to open hyprland it puts me again to sddm.
Additionally, when i run Hyprland in terminal it shows me this error:
-> Hyprland
Hyprland: error while loading shared libraries: libxcb-errors.so.0: cannot open shared object file: No such file or directory

How to reproduce
idk
Crash reports, logs, images, videos
No response

this is an sddm bug, hyprland is not officially supporting any login managers.

this is an sddm bug, hyprland is not officially supporting any login managers.

So how could i make it work?

Probably your system is missing xcb-errors package. so you have to build it . you can find instrction here

this is an sddm bug, hyprland is not officially supporting any login managers.

I don't think it's a bug of sddm. The same thing happens to me on my laptop: I log in from sddm and it immediately takes me back to the login screen. I've tried disabling sddm and logging in with the Hyprland command from the shell and it gives me the same error. with the desktop same thing with the latest update. I use Arch Linux on both PCs. sorry for my english, i'm using google translate

I don't think it's a bug of sddm. The same thing happens to me on my laptop: I log in from sddm and it immediately takes me back to the login screen. I've tried disabling sddm and logging in with the Hyprland command from the shell and it gives me the same error. with the desktop same thing with the latest update. I use Arch Linux on both PCs. sorry for my english, i'm using google translate

run whereis libxcb-errors.so.0 if it doesn't give you a location, you don't have the package. Install it for your system.


Template error with entities starting with number

Home Assistant release with the issue:
0.69
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Raspberry, virtual env
Component/platform:
Templating. Entity for example BMW Connected drive
Description of problem:
Its not possible to use a template with entities which start with a number.
Example: {{ states.device_tracker.118i.attributes.longitude }}
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
bmw_connected_drive:
name:
username: !secret bmw_username
password: !secret bmw_password
#country: Germany
region: !secret bmw_region
Traceback (if applicable):
Error rendering template: TemplateSyntaxError: expected token 'end of print statement', got 'i'
Additional information:
the BMW connected drive for example auto creates the entity with the name "118"
Edit: Please note {{ state_attr('device_tracker.118i', 'latitude') }} is indeed a workaround.
This is still not userfriendly. If the problem is based on jinja, autocreated entities starting with a number should be avoided and examples https://www.home-assistant.io/cookbook/google_maps_card/ should be changed or have a note

There's a note in the Templating docs.

If your template uses an entity_id that begins with a number (example: states.device_tracker.2008_gmc) you must use a bracket syntax to avoid errors caused by rendering the entity_id improperly. In the example given, the correct syntax for the device tracker would be: states.device_tracker['2008_gmc']


MediaPlayerElement freezes when playing SIMPLE mp4 urls that are more than 30 seconds Bug title

Describe the bug
MediaPlayer freezes when playing source that are mp4 URLs (NOT HTTP LIVE STREAM LINKS, or APPLE
example of a simple mp4 link: http://localhost/videos/samplefile.MP4
<MediaPlayerElement x:Name="MediaPlayerElementControl"
            Margin="5,5,5,5"
            Height="500"
            Width="500"
            Source="http://localhost/videos/samplefile.MP4"
            AreTransportControlsEnabled="True"
            HorizontalAlignment="Stretch" VerticalAlignment="Stretch"/>

I will play, then buffer, then continue to play.
Then for some reason after ~5 seconds, the sound keeps playing but the image freezes.
Pausing and playing again will cause the player to speed up and display the skipped parts of the video.
THIS IS NOT THE SAME ISSUE AS  https://github.com/microsoft/WindowsAppSDK/issues/3305 .
Steps to reproduce the bug

Create MediaPlayerElement control
Source should be a mp4 url in the Source that is longer than 30 seconds.
(NOT A HLS live stream link)

If not reproducable with 30 seconds, try a 1 min video
<MediaPlayerElement x:Name="MediaPlayerElementControl"
            Margin="5,5,5,5"
            Height="500"
            Width="500"
            Source="http://localhost/videos/samplefile.MP4"
            AreTransportControlsEnabled="True"
            HorizontalAlignment="Stretch" VerticalAlignment="Stretch"/>

Expected behavior
Should not freeze and continue to play + stream url
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.5.1: 1.5.240311000
Windows version
Windows 11 (22H2): Build 22621
Additional context
https://github.com/microsoft/microsoft-ui-xaml/issues/8708 was closed so re-created this again

THIS IS NOT THE SAME ISSUE AS https://github.com/microsoft/WindowsAppSDK/issues/3305

Closing issue as the issue on streaming an mp4 url from a connected device and the problem might be on the connected device and not on winui.


ResolutionFailedException on container.RegisterType<IEnumerable, IInterface[]>()

Description
Using .NET Framework 4.7.1.
Since 5.8.6 to 5.8.7=< (So probably the switch to .NETStandard), the registered type forwarding stopped working:
To Reproduce
        public void Main()
        {
            var container = new UnityContainer();
            container.RegisterType<IInterface, Class1>(nameof(Class1));
            container.RegisterType<IInterface, Class2>(nameof(Class2));
            container.RegisterType<IEnumerable<IInterface>, IInterface[]>();
            container.RegisterType<A>();
            var a = container.Resolve<A>();
        }

        public interface IInterface
        {
        }

        public class Class1 : IInterface
        {
        }

        public class Class2 : IInterface
        {
        }

        public class A
        {
            public A(IEnumerable<IInterface> interfaces)
            {
            }
        }

Exception
Unity.Exceptions.ResolutionFailedException
HResult=0x80131500
Message=Resolution of the dependency failed, type = 'Sandbox.MainWindow+A', name = '(none)'.
Exception occurred while: while resolving.
Exception is: InvalidOperationException - The type Int32 does not have an accessible constructor.

Thanks for your investigation.
This behavior is still remaining, which is a breaking change from 5.8.6 to 5.8.7.
It's just a type forwarding/decoupling.
I'll try the RegisterFactory<IEnumerable>() way.

Ooops, after some trials with a current version i've just removed the Registering of IEnumerableT to ArrayT.
The current UnityContainer has got a native factory for IEnumerable<>
:+1:


Increase interface surface of Veldrid components

Prereqs:

[x] https://github.com/ppy/osu-framework/pull/6187

Some components are generic enough that they don't need to be reimplemented:

VeldridShader
VeldridTexture

These components use IVeldridRenderer.
Other components are a bit more specific to VeldridRenderer and either need to be reimplemented, or not implemented at all:

VeldridVertexBuffer
VeldridFrameBuffer

These components use VeldridRenderer.

@smoogipoo I've resolved conflicts here to the best of my judgement but please double-check. Will not be reviewing for a while anyhow.


"Mismatched Quarkus version found" warning

Hi,
On "https://code.quarkus.io" I created simple project stub including only quarkus-operator-sdk extension. code-with-quarkus.zip
Maven build (mvn clean package) produce warning message:
[WARNING] [io.quarkiverse.operatorsdk.deployment.VersionAlignmentCheckingStep] Mismatched Quarkus version found: "3.15.1", expected: "3.14.2" by at least a minor version and things might not work as expected.

When "quarkus-operator-sdk" dependency is removed warning is gone.
More details:
[INFO] --- quarkus:3.15.1:build (default) @ code-with-quarkus ---
[INFO] [io.quarkiverse.operatorsdk.deployment.VersionAlignmentCheckingStep] QOSDK: 6.8.0 (commit: 79457f5) built on Mon Sep 09 21:42:27 CEST 2024
[INFO] [io.quarkiverse.operatorsdk.deployment.VersionAlignmentCheckingStep] JOSDK: 4.9.4 (commit: 3588780) built on Thu Aug 29 18:52:57 CEST 2024
[INFO] [io.quarkiverse.operatorsdk.deployment.VersionAlignmentCheckingStep] Fabric8 (effective): 6.13.3
[WARNING] [io.quarkiverse.operatorsdk.deployment.VersionAlignmentCheckingStep] Mismatched Quarkus version found: "3.15.1", expected: "3.14.2" by at least a minor version and things might not work as expected.
[INFO] [io.quarkiverse.operatorsdk.deployment.VersionAlignmentCheckingStep] Fabric8 (JOSDK-defined): 6.13.3
[INFO] [io.quarkiverse.operatorsdk.deployment.VersionAlignmentCheckingStep] Fabric8 (Quarkus): 6.13.3

Maven and java info:
C:\tmp\code-with-quarkus>c:\Programs\apache-maven-3.9.5\bin\mvn --version
Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: c:\Programs\apache-maven-3.9.5
Java version: 21.0.4, vendor: Eclipse Adoptium, runtime: c:\Users\nevenr\.jdks\temurin-21.0.4
Default locale: en_US, platform encoding: UTF-8
OS name: "windows 11", version: "10.0", arch: "amd64", family: "windows"

C:\tmp\code-with-quarkus>

Regards,
N.

Hi @nevenr, this is expected at the moment because the platform currently includes 6.8.0, which was build against Quarkus 3.14, and should have been included in the 3.15 platform, so seeing this warning is "normal" and shouldn't be a problem. Please don't hesitate to open issues if you find that this isn't the case.

Hi @metacosm ,
All is OK. Thanks for response.
Regards,
N.


Microsoft.Azure.WebJobs.Extensions.ServiceBus 5.x release date

Hi,
when are you going to release Microsoft.Azure.WebJobs.Extensions.ServiceBus 5.x?
Regards,
Alexey

Thank you for your question.  Tagging and routing to the team member best able to assist.

//cc: @pakrym, @JoshLove-msft

We are planning for Q3 2021

Q3 is nearly over. is everything still on track?

@pakrym today is the end of Q3 2021. any update on the release?

@swettstein thanks for your interest.
We are working on this and I will update this issue when we have a concrete answer.

This is now available! 🙂.


ipsec: conntrack cache problem

Linking related issue that was reported in Docker: https://github.com/docker/docker/issues/8795
Just to be clear Docker suffers from the same stale conntrack UDP issues Rancher does, but since Rancher does not use Docker native networking anymore we will fix it in Rancher.

Available in rancher/net:v0.11.0 (ipsec template version v0.0.5)  and rancher/network-manager:v0.6.0 (network-services template version v0.1.2)

Closing as per the findings from #8412 (comment).


Add site replication docs

Closes #436 .
Creates new site replication overview doc.
Adds mc admin replicate doc.
Creates new Replication Overview doc.
Updates toctrees for new left side navigation with a replication summary, then bucket and site replication sections.
Adds images for site replication.
Still to do: add recovery/healing doc when site replication is enabled.

Well, a few interactive rebases and force pushes later and I think I have master and this branch back to where they need to be.


impossible to save in netcdf because of the time dimension

What happened?
I have a dataset ds with a variable TEMP(time,level,ni,nj).
The time dimension a of type datetime64 but I get an error when I try to save a temporal selection.
What did you expect to happen?
Time dimension management should be completely transparent to the user when a datetime64 type is used.
Minimal Complete Verifiable Example
ds.time
xarray.DataArray
'time'
    time: 8760
    array(['2015-01-01T00:00:00.000000', '2015-01-01T01:00:00.000000',
           '2015-01-01T02:00:00.000000', ..., '2015-12-31T21:00:00.000000',
           '2015-12-31T22:00:00.000000', '2015-12-31T23:00:00.000000'],
          dtype='datetime64[us]')
    Coordinates:
        time
        (time)
        datetime64[us]
        2015-01-01 ... 2015-12-31T23:00:00
    Indexes: (1)
    Attributes:
    axis : T
    conventions : relative number of seconds with no decimal part
    long_name : time in seconds (UT)
    standard_name : time
    time_origin : 01-JAN-1900 00:00:00
    _FillValue : nan
     units : seconds since 1900-01-01

ds['TEMP'].isel(time=slice(0,1)).to_netcdf(f"./extract.nc")
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[81], line 1
----> 1 ds['TEMP'].isel(time=slice(0,1)).to_netcdf(f"./extract__2.nc")

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/core/dataarray.py:4081](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/core/dataarray.py#line=4080), in DataArray.to_netcdf(self, path, mode, format, group, engine, encoding, unlimited_dims, compute, invalid_netcdf)
   4077 else:
   4078     # No problems with the name - so we're fine!
   4079     dataset = self.to_dataset()
-> 4081 return to_netcdf(  # type: ignore  # mypy cannot resolve the overloads:(
   4082     dataset,
   4083     path,
   4084     mode=mode,
   4085     format=format,
   4086     group=group,
   4087     engine=engine,
   4088     encoding=encoding,
   4089     unlimited_dims=unlimited_dims,
   4090     compute=compute,
   4091     multifile=False,
   4092     invalid_netcdf=invalid_netcdf,
   4093 )

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/backends/api.py:1339](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/backends/api.py#line=1338), in to_netcdf(dataset, path_or_file, mode, format, group, engine, encoding, unlimited_dims, compute, multifile, invalid_netcdf)
   1334 # TODO: figure out how to refactor this logic (here and in save_mfdataset)
   1335 # to avoid this mess of conditionals
   1336 try:
   1337     # TODO: allow this work (setting up the file for writing array data)
   1338     # to be parallelized with dask
-> 1339     dump_to_store(
   1340         dataset, store, writer, encoding=encoding, unlimited_dims=unlimited_dims
   1341     )
   1342     if autoclose:
   1343         store.close()

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/backends/api.py:1386](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/backends/api.py#line=1385), in dump_to_store(dataset, store, writer, encoder, encoding, unlimited_dims)
   1383 if encoder:
   1384     variables, attrs = encoder(variables, attrs)
-> 1386 store.store(variables, attrs, check_encoding, writer, unlimited_dims=unlimited_dims)

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/backends/common.py:393](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/backends/common.py#line=392), in AbstractWritableDataStore.store(self, variables, attributes, check_encoding_set, writer, unlimited_dims)
    390 if writer is None:
    391     writer = ArrayWriter()
--> 393 variables, attributes = self.encode(variables, attributes)
    395 self.set_attributes(attributes)
    396 self.set_dimensions(variables, unlimited_dims=unlimited_dims)

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/backends/common.py:482](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/backends/common.py#line=481), in WritableCFDataStore.encode(self, variables, attributes)
    479 def encode(self, variables, attributes):
    480     # All NetCDF files get CF encoded by default, without this attempting
    481     # to write times, for example, would fail.
--> 482     variables, attributes = cf_encoder(variables, attributes)
    483     variables = {k: self.encode_variable(v) for k, v in variables.items()}
    484     attributes = {k: self.encode_attribute(v) for k, v in attributes.items()}

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/conventions.py:795](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/conventions.py#line=794), in cf_encoder(variables, attributes)
    792 # add encoding for time bounds variables if present.
    793 _update_bounds_encoding(variables)
--> 795 new_vars = {k: encode_cf_variable(v, name=k) for k, v in variables.items()}
    797 # Remove attrs from bounds variables (issue #2921)
    798 for var in new_vars.values():

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/conventions.py:196](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/conventions.py#line=195), in encode_cf_variable(var, needs_copy, name)
    183 ensure_not_multiindex(var, name=name)
    185 for coder in [
    186     times.CFDatetimeCoder(),
    187     times.CFTimedeltaCoder(),
   (...)
    194     variables.BooleanCoder(),
    195 ]:
--> 196     var = coder.encode(var, name=name)
    198 # TODO(kmuehlbauer): check if ensure_dtype_not_object can be moved to backends:
    199 var = ensure_dtype_not_object(var, name=name)

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/coding/times.py:979](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/coding/times.py#line=978), in CFDatetimeCoder.encode(self, variable, name)
    977 calendar = encoding.pop("calendar", None)
    978 dtype = encoding.get("dtype", None)
--> 979 (data, units, calendar) = encode_cf_datetime(data, units, calendar, dtype)
    981 safe_setitem(attrs, "units", units, name=name)
    982 safe_setitem(attrs, "calendar", calendar, name=name)

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/coding/times.py:728](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/coding/times.py#line=727), in encode_cf_datetime(dates, units, calendar, dtype)
    726     return _lazily_encode_cf_datetime(dates, units, calendar, dtype)
    727 else:
--> 728     return _eagerly_encode_cf_datetime(dates, units, calendar, dtype)

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/coding/times.py:740](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/coding/times.py#line=739), in _eagerly_encode_cf_datetime(dates, units, calendar, dtype, allow_units_modification)
    731 def _eagerly_encode_cf_datetime(
    732     dates: T_DuckArray,  # type: ignore
    733     units: str | None = None,
   (...)
    736     allow_units_modification: bool = True,
    737 ) -> tuple[T_DuckArray, str, str]:
    738     dates = asarray(dates)
--> 740     data_units = infer_datetime_units(dates)
    742     if units is None:
    743         units = data_units

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/coding/times.py:439](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/coding/times.py#line=438), in infer_datetime_units(dates)
    437 else:
    438     reference_date = dates[0] if len(dates) > 0 else "1970-01-01"
--> 439     reference_date = format_cftime_datetime(reference_date)
    440 unique_timedeltas = np.unique(np.diff(dates))
    441 units = _infer_time_units_from_diff(unique_timedeltas)

File [/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/coding/times.py:450](http://localhost:8877/home/datawork-marc/ENVS/pangeo2024/lib/python3.12/site-packages/xarray/coding/times.py#line=449), in format_cftime_datetime(date)
    445 def format_cftime_datetime(date) -> str:
    446     """Converts a cftime.datetime object to a string with the format:
    447     YYYY-MM-DD HH:MM:SS.UUUUUU
    448     """
    449     return "{:04d}-{:02d}-{:02d} {:02d}:{:02d}:{:02d}.{:06d}".format(
--> 450         date.year,
    451         date.month,
    452         date.day,
    453         date.hour,
    454         date.minute,
    455         date.second,
    456         date.microsecond,
    457     )

AttributeError: 'numpy.datetime64' object has no attribute 'year'

MVCE confirmation

[ ] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[ ] Complete example — the example is self-contained, including all data and the text of any traceback.
[ ] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[ ] New issue — a search of GitHub Issues suggests this is not a duplicate.
[ ] Recent environment — the issue occurs with the latest version of xarray and its dependencies.

Relevant log output
No response
Anything else we need to know?
 In general datetimes are always represented as numpy.datetime64[ns] when read with xarray. If that's not possible cf_time objects are used. I'm assuming since your data is in numpy.datetime64[us] for some reason the check in
https://github.com/pydata/xarray/blob/61ffc38a495b224c49f9486404ee3bdcb9049663/xarray/coding/times.py#L429-L440
fails and the code is entering the second path (cf_time handling).
Could you change your time data to numpy.datetime64[ns] and check if this fixes the export to netcdf? How did you read that data, BTW?

my dataset comes from netcdf files opened through an intake catalog.
ds = cat[cat.name].to_dask()
The individual netcdf files have a time of type datetime64[ns]

this sounds very much like #6318. @jfleroux, can you confirm that kerchunk is involved? If so, the explicit cast suggested by @kmuehlbauer should work:
ds['TEMP'].assign_coords(time=lambda ds: ds["time"].astype("datetime64[ns]")).isel(time=slice(0,1)).to_netcdf(f"./extract.nc")

Ah right, I remember that issue now.  Thanks @keewis.  @jfleroux let us know if that seems relevant / helps you work around this.

Yes it's ok with the work around :
ds['time'] = ds["time"].astype("datetime64[ns]")

Awesome, thanks for confirming that it's the kerchunk-related issue @jfleroux.


Local file IO is still broken

See: https://github.com/Fizzadar/pyinfra/commit/2ed18628391d3e4ff25d2b8ed0b061d27f08e584

If you need a beta tester : present :) As we need this issue fixed. Tx

@gdoumenc I've just pushed a (hopeful) fix for this (https://github.com/Fizzadar/pyinfra/commit/a2ede505e920d8ca43950290d8ef2602e99533c6) which happens because the jinja2 output in Python 3 is unicode data.

Should be working, will cut v0.5.3 soon!

@gdoumenc good catch, it's because we do the IO in Pythonland but that doesn't work with sudo! I'll investigate doing it using cp instead :)

This should now be fixed as of https://github.com/Fizzadar/pyinfra/commit/803e8a9fe74905bdd0d19c294066c2f8ade57f97 :)


Expand on NuGet package naming conventions & best practices

Add the regex of words for nuget package names such as [a-zA-Z_0-9] to help users understand the allowed characters.
Additionally a link to https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/names-of-namespaces to help users understand what makes a good namespace name.
Add some clarification to the following pages:
https://docs.microsoft.com/en-us/nuget/reference/nuspec#id
https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package#choose-a-unique-package-identifier-and-setting-the-version-number
We should document what the most common package ID naming convention is even though Unicode is valid.

Please note unicode letters and -, . are supported in package name id.

If additional restrictions result from this, please be sure to differentiate between what is allowed on nuget.org/myget and what is allowed on private repository. They often have different needs and what is needed on a public repo will cripple a private repos or it's packages (PS1, config transform, etc)


FIX: Ordering of fields (WIP)

NOTE: this is a WIP commit to solicit feedback only. It is far from complete.
The GraphQL spec says the order of the fields in the output should match
the order specified in the query.
Maps in Elixir do not provide a way to traverse the keys in source
order and maps are currently used to hold fields in query definitions
and during execution.
This means order of fields in the output is non-deterministic right now.
The fix for this is to use keyword lists instead of maps in query
definitions and during execution.
A further complication is that Poison (used in the plug) cannot encode
keyword lists, so we'd need to have some alternative solution for
transforming the literal query results into JSON.

I couldn't find where in the spec the order matters, but found this: http://facebook.github.io/graphql/#sec-Evaluating-a-grouped-field-set which states the opposite

I assumed from the GitHub issue that that was the case without checking the
facts. No worries the mn 😀
On Saturday, 23 January 2016, Josh Price<EMAIL_ADDRESS>wrote:

I couldn't find where in the spec the order matters, but found this:
http://facebook.github.io/graphql/#sec-Evaluating-a-grouped-field-set
which states the opposite
—
Reply to this email directly or view it on GitHub
https://github.com/joshprice/graphql-elixir/pull/51#issuecomment-174092969
.

--
James

Might be worth double-checking the spec since I have a hunch that section I
linked to doesn't actually apply to the fields.
On Sat, Jan 23, 2016 at 2:56 PM, James Sadler<EMAIL_ADDRESS>wrote:

I assumed from the GitHub issue that that was the case without checking the
facts. No worries the mn 😀
On Saturday, 23 January 2016, Josh Price<EMAIL_ADDRESS>wrote:

I couldn't find where in the spec the order matters, but found this:
http://facebook.github.io/graphql/#sec-Evaluating-a-grouped-field-set
which states the opposite
—
Reply to this email directly or view it on GitHub
<
https://github.com/joshprice/graphql-elixir/pull/51#issuecomment-174092969
.

--
James
—
Reply to this email directly or view it on GitHub
https://github.com/joshprice/graphql-elixir/pull/51#issuecomment-174126783
.

So I double checked the spec and I couldn't find anything that says order matters.
See: https://facebook.github.io/graphql/#sec-Objects

GraphQL Objects represent a list of named fields, each of which yield a value of a specific type. Object values are serialized as unordered maps, where the queried field names (or aliases) are the keys and the result of evaluating the field is the value.


Fix/static nodes

Closes #1141
Check if the same static nodes is re-used.

Within the same config (by tracking the nodepool name)
Across different configs (by tracking the IP of every node) No two static nodes can have the same IP, thus if the same IP is used in different config this means the same static node is referenced.

This will work for now, but once https://github.com/berops/claudie/issues/962 is being worked on this should be revisited.

Hi @Despire,
Will this cover also the scenario when a different Claudie instance will try to use a static node which is under control by another Claudie control plane?

Will this cover also the scenario when a different Claudie instance

Do you mean 2 claudie deployed in two management clusters ? If so they share the same mongoDB then yes, otherwise no.

@bernardhalas
Do you want to implement this ? 'Cause this might be a bigger issue, tracking all of the static nodes across different claudie instances running on different management clusters.

Will this cover also the scenario when a different Claudie instance

Do you mean 2 claudie deployed in two management clusters ? If they share the same mongoDB then yes, otherwise no.

Can we have 2 claudie instances that would share the same DB?

Do you want to implement this ? 'Cause this might be a bigger issue, tracking all of the static nodes across different claudie instances running on different management clusters.

If we had each Claudie instance with its ID, it would be pretty easy to leave a tag on the node saying to which instance it belongs. But I assume it's OK like this for now.

Can we have 2 claudie instances that would share the same DB?

Once this issue https://github.com/berops/claudie/issues/815 is implemented than it would be possible to share a common database.

If we had each Claudie instance with its ID, it would be pretty easy to leave a tag on the node saying to which instance it belongs. But I assume it's OK like this for now.

I can open an issue about this so we can discuss this further


[Compute] az vm/vmss create: Install guest attestation extension and turn on system MSI by default when Trusted Launch configuration is met

Description

Guest Attestation Extension and enable System Assigned MSI by default when Trusted Launch configuration is met https://github.com/Azure/azure-cli/issues/21395
Testing Guide

History Notes

[Compute] az vm/vmss create: Install guest attestation extension and enable system managed identity by default when Trusted Launch configuration is met
[Compute] az vm/vmss create: Add new parameter --disable-integrity-monitoring to disable the default behavior (installing guest attestation extension and turning on MSI) when creating VM/VMSS compliant with Trusted Launch

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

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

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Compute

LGTM

@sirfamelin In fact, this feature has been released in the last sprint. You can update the CLI to the latest version (2.36.0) and then try it


Widevine CDM was empty

On our main Kodi setup the children complained some add-ons no longer worked. After investigating the widevinecdm.so was empty.
There is no clear reason why it would be empty, the disk had +50GB of free disk space. So there are 3 possibilities:

Kids stopped an automatic Widevine CDM update during uncompressing?
Software issue (Kodi restarting during uncompressing, other bug)
Hardware issue

My assumption is the first one. We now we currently have no progress-indication during uncompressing and this may take op 2 minutes (which is awfully long if you are a kid, cannot read and are waiting for a video to start).
So we need to ensure that we uncompress in a different location and move the file. This would protect us against disk full conditions and people interrupting the uncompress stage, and breaking a possibly working Widevine setup.

That would be pretty much how it had been before #95.

@horstle We live, we learn :-)

My original suggestion was to tackle this together with backup/restore of Widevine CDM.
For ARM that would mean, extract under a different name widevinecdm-{chromeos}.so, and then hardlink to widevinecdm.so. For non-ARM we have an actually library version, and would be doing widevinecdm-{version}.so, and hardlink to widevinecdm.so.
Restoring becomes quite efficient, as you could simply list the available files and select the one you would like to hardlink.
For ARM that would require a translation table between ChromeOS version to Widevine version (multiple ChromeOS versions offer the same Widevine, so some optimization would be useful to avoid (a) redownloading known ChromeOS images and (b) storing multiple identical Widevine versions).

The newest version of #193 should fix this.

PR #193 was merged. Let's close this now.


PropagationCost = 1 when player stands directly on portal to higher priority room, and sound is in lower priority room

I noticed a slight gap in audio when you move from a lower priority room to a higher priority room (eg. from a room with priority 1 to a room with priority 2). Looking at the debugger in the Spatial Audio Manager, I can confirm that PropagationCost = 1 when the player is standing directly on the portal.
Steps to reproduce:
Place sound emitter in a lower priority room, and position player to stand directly on a portal to a higher priority room. I only tested this if the higher priority room is nested within a larger, lower priority room. I'm not sure if it happens if they are adjacent and not nested.
(our game is also first-person, so the listener position can be quite specific)

The only way I was able to quickly reproduce a similar end result, is in situations where the portal has been placed some distance inside the nested higher priority area (instead of on its border) and the listener is located in between the portal and the area border, plus the distance between listener and the portal is greater than the constant MinimumVectorMagnitude.
If this is the same issue you're experiencing, you can fix it either by placing the portal more accurately on the area border or by increasing the MinimumVectorMagnitude. Ideally, this could of course use a more robust solution that does not require such precision work from the user.
If the issue you're experiencing is something different, we'll have to look more closely into the repro steps.

I believe this was the issue I was experiencing, and I didn't realize that my nested room slightly overlapped the portal. Thank you!


feat: add example GH action (with zones)

Resolves #299

[x] There is an associated issue (required)
[x] The change is described in detail
[x] There are new or updated tests validating the change (if applicable)

Description
Run examples in parallel using reusable workflows.
The caller workflow spawn_examples.yml generates the list of example paths and calls the example.yml reusable workflow.
The example.yml workflow uses a marix strategy to create a job for each example file.
Also, this PR adds a setup-polkadot composite action that caches and downloads the polkadot binary.
I'd like to get some feedback on the composite action before integrating it in other workflows

covered in #300


fix(openapi): ignored schema on api generation

REPRODUCE
On startup simple example get this warnings:
2021-05-07 15:38:27,420 | WARNING | hopeit.engine 0.2.2 engine Mac-mini-de-Pablo.local 13726 | [hopeit.server.api] Schema ignored: same schema name has non-compatible implementations: event=collector.collect_spawn schema=ItemsInfo |
2021-05-07 15:38:27,425 | WARNING | hopeit.engine 0.2.2 engine Mac-mini-de-Pablo.local 13726 | [hopeit.server.api] Schema ignored: same schema name has non-compatible implementations: event=shuffle.spawn_event schema=SomethingStored |
2021-05-07 15:38:27,429 | WARNING | hopeit.engine 0.2.2 engine Mac-mini-de-Pablo.local 13726 | [hopeit.server.api] Schema ignored: same schema name has non-compatible implementations: event=shuffle.parallelize_event schema=SomethingStored |
2021-05-07 15:38:27,434 | INFO | hopeit.engine 0.2.2 engine Mac-mini-de-Pablo.local 13726 | [hopeit.server.api] Updating API spec for app=simple_example.2x0, plugin=basic_auth.2x0... |
2021-05-07 15:38:27,437 | WARNING | hopeit.engine 0.2.2 engine Mac-mini-de-Pablo.local 13726 | [hopeit.server.api] Schema ignored: same schema name has non-compatible implementations: event=collector.collect_spawn schema=ItemsInfo |
2021-05-07 15:38:27,438 | WARNING | hopeit.engine 0.2.2 engine Mac-mini-de-Pablo.local 13726 | [hopeit.server.api] Schema ignored: same schema name has non-compatible implementations: event=shuffle.spawn_event schema=SomethingStored |
2021-05-07 15:38:27,439 | WARNING | hopeit.engine 0.2.2 engine Mac-mini-de-Pablo.local 13726 | [hopeit.server.api] Schema ignored: same schema name has non-compatible implementations: event=shuffle.parallelize_event schema=SomethingStored |

@pcanto-hopeit can we assign this bug to version 0.3.0? PLMK if you can pick it up.


Please, build new version of npm package

npm  4.2.0
node v7.10.1
linux mint 18.1
In package.json i have electron-installer-debian": "*"
And i got electron-installer-debian 0.5.2 after npm install
I look forward to a scripts option (postinst etc) but in 0.5.2 version i did not found this feature.

Build v0.6.0 has been released


Path separators are hardcoded

I'm trying to use aws-sso-creds in a fairly restricted work environment. I need a POSIX shell and can't install WSL so I'm trying to use Cygwin. When I run export, I get this.

The issue is here. The code has hardcoded POSIX path separators instead of using an agnostic function (AFAIK this is the preferred method). I'll have a PR up for this later today or this week and I'll try to find all other path instances.

Thanks for the issue, I'll try spin up a windows environment to get this fixed


Replace templates and index mapping with RelationMetadata

Relates to https://github.com/crate/crate/issues/11939
Very early draft
TODO:

[ ] Alter table settings / mapping handling
[ ] Dynamic column updates. Related to ^
[ ] Alter table close/open handling
[ ] Replace use of mapping in TransportReplicationAllPermitsAcquisitionTests, IndexShardTestCase, IndexShardsTest
[ ] Replace use of mapping in MetadataTracker
[ ] MetadataIndexUpgrader
[ ] DocTableInfo.writeTo
[ ] TransportCreatePartitionsAction
[ ] FixCorruptedMetadata
[ ] Swap handling
[ ] Rename handling
[ ] Finalize new structures format; Connect tables/indices
[ ] Snapshots
[ ] BWC handling
[ ] Views migration

@mfussenegger
Sounds like a good plan 👍

indices and indicesByUUID distinction will be gone in Metadata, everything will be by UUID. (We'll lose some convenience around debugging by doing this as we'll no longer have human readable names in various places)

Couldn't we retrieve the name from the metadata maybe? Not important, can be done later if possible.

I also don't really see this getting into a state where I'd feel comfortable releasing it within the remaining 5.10 window. My current goal is to get it working (unmerged) within the 5.10 window and then work on stabilization, testing and polishing for a release with 6.0.

Yeah better to be quite safe with this. I also see no real possibilities to paralize any of these steps.

Another point for later discussion:

We could add oids for the tables and logical replication could be based on that + indexUUIDs. This would remove the restriction that a published table cannot be renamed. Currently there are test failures because I temporarily removed the publication check part. I'll need to have a closer look at logical replication to see if / how much extra effort that would add. My current plan is to do whatever is less effort and gets it working.


Derive Debug for subdivided

This adds Debug to Subdivided and should hopefully not break anything. I have a specific use of this in a derived table structure where at each vertex I store data, T that may be a float or another icosphere. If both types implement Debug it's trivial to print information from a common function.

Hmmm, this is a much more difficult PR to address. Lots of the fields in Subdivided aren't really meant to be exposed to the public eye, and are basically just book keeping structures... I'll take a closer look at this later tonight or when I get home, but I would strongly suggest just writing a specialized printing machinery for your use. This isn't the intended usage of the library

Hmmm, this is a much more difficult PR to address. Lots of the fields in Subdivided aren't really meant to be exposed to the public eye, and are basically just book keeping structures... I'll take a closer look at this later tonight or tomorrow, but I would strongly suggest just writing a specialized printing machinery for your use. This isn't the intended usage of the library

I use it mostly during development and can of course handle printing in other ways if needed, so no big issue. I think most other objects in the library implement Debug and Subdivided sticks out so to say.

I think most other objects in the library implement Debug and Subdivided sticks out so to say.

Yeah that's a leftover from development, when I wanted to print things to debug them.

I've been giving this some thought over the past two days, and unfortunately, there's not really a good way to print a Subdivded. There are three major components to a Subdivded according to the user:

The raw points as Vec3As.
The raw user data.
The indices that make up the triangles for a mesh.
However to the library, there are more nuanced details:
The edges shared by the triangles in the original source polyhedron (the shared_edges field).
The contents of the triangles in the original source polyhedron (the triangles field).
The source shape (the shape field).
Exposing these nuanced details to the user wouldn't likely provide any useful information to the user, as they're essentially implementation details about the algorithm used under the hood. Additionally, there are a few more caveats:
There is no indices field in the struct -- that's because they need to be generated from the triangle contents. Hence this means that Debug causes an allocation which isn't great.
Triangle is a recursive structure which is very implementation-detail-y, and would honestly just be gobbledygook to someone who isn't very familiar with the algorithm (and afaik, I am the only one who is as I wrote out the algorithm four years ago on a notebook and it's been mainly sitting in my head since).
The most common usage of raw_data is to just store (). Hence printing out raw_data wouldn't even be useful to most people!

For these reasons, I believe that implementing Debug on subdivided isn't a great idea, and would recommend you just newtype with application-specific behaviour. If you're actually interested in how the algorithm works (it's not particularly complicated, just annoying to picture/come up with), the feel free to ask me and/or fork the crate to make fields pub and add Debug as it is in this PR.
Hence, I will be closing this PR. I apologize for the inconvenience.

Thanks for the explanation - I agree. Btw. I found this book on the topic very helpful and genrerally fun to read: https://dividedspheres.com

I'm pretty happy with the current results of hexasphere, but I might give it a read 🙂

Yes, me too :-) I'm hoping to publish what we're working on, and will of course reference Hexasphere. You could also consider adding a citation file to the repo and/or connect it to zenodo.org.

You could also consider adding a citation file to the repo and/or connect it to zenodo.org.

Done!


AWS C360 Data Hub integrations

Issue #, if available:
N/A
Description of changes:
This PR contains four additions to the project to support integration with the AWS Customer 360 Data Hub project. These changes are as follows:

Replace in-memory DB for orders service with Dynamo DB table
Allow input of a Kinesis stream ARN for the products and orders service
Add service load balancer URLs as outputs of the top-level template
Added --private flag to the staging script to expose functionality previously only accessible by direct modification fo the script. Default behaviour remains the same.

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

This work was done by the Dae.mn Team. http://dae.mn/ml
<EMAIL_ADDRESS>

May solve issue: https://github.com/aws-samples/retail-demo-store/issues/14


Adds canonical categories

Abs page categories now uses canonical (for just the primary).
Also adds HTML tests.
https://culibrary.atlassian.net/browse/ARXIVNG-605

Pull Request Test Coverage Report for Build 124

25 of 25 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 92.538%

Totals

Change from base Build 116:
0.08%

Covered Lines:
2009

Relevant Lines:
2171

💛  - Coveralls


Ignore dotfiles

As mentioned in #145 I accidentally opened Syncthing's .stfolder with writeily which broke the synchronisation it provides for me. Dotfiles are rather common to store configuration and metadata and may be created by other tools, too.
Just ignoring any file starting with a '.' wouldn't hurt anyone and would prevent such accidents.

If you try to name a note .* it does not save it and also doesn't warns about that