Chore/vite plugin ssr to vike

🙂 Thought you might be out of my time zone 💤, so did some updating and manual testing on a branch ...  no worries ... please close of the PR
Bumped some versions

Please revert all unrelated changes.
PRs should generally be focused upon a single topic and switching to vike shouldn't require bumping other dep versions or rewriting the Yarn lock file (should never really do that).

Thanks!


Prevent Valid_Message without Verify_Message

When building the IP sniffer test, I forgot to run Verify_Message before checking Structural_Valid_Message. While this was not a correctness issue (the context of cause was invalid), it took me some time to realize that. I wonder if we should add a predicate to those convenience operations that work on a whole message that states/requires that a verification has been attempted on a context. This way we could spot such oversights during proof.

We should make sure that such a predicate also works with Verify, not only with Verify_Message. I think the simplest solution would be to let the Initialize procedure add a predicate Unchanged to the context, which is automatically removed by any procedure with an in-out context parameter (i.e. Verify, Verify_Message, Take_Buffer, Switch and Update). All validation functions would then need a not Unchanged as precondition.

Suggested name for the predicate: No_Verification_Attempted

The envisioned solution is not applicable, as the value of the predicate is unknown after a procedure with an in-out parameter. After some discussion we think there is no simple solution, which has no drawbacks.
A good solution is able to statically analyze, if the code could lead to a valid message before Valid_Message is called. The following properties should be fulfilled, before Valid_Message can be used:

a complete verification (Verify_Message) or a incremental verification (Verify ) was performed
at least a subset of all fields, which form a potential valid message, have been verified
Verify have been called in the correct order
if Verify is used in a nested way (see code example below), the correct condition checks have been done

Initialize (C, Buffer);

Verify (C, Field_A);
if Valid (C, Field_A) then
   Verify (C, Field_B);
   if Valid (C, Field_B) then
      ...
   end if;
end if;

For a good usability it should be possible to call Valid_Message (C) after this nested if-statements (if a correct incremental verification was done before). But I guess the verification tools would be only able to show the correct usage if Valid_Message is used inside of the nested if-statements.

After further discussion we came to the following idea as solution:

Ensure that Verify is always called in correct order by predicate and appropriate pre- and postconditions
Add precondition to Valid_Message that Verify of at least one potential final field is called (the postcondition of Verify_Message is extended accordingly)

This covers the first three aspects mentioned in the comment above. As field conditions are checked internally by Verify, it is not necessary to enforce the user to do same again. Calling Valid_Message after nested if-statements will be not possible in the way shown above (a workaround would be to bind the proof-state to a boolean value in a branch where the necessary verifications have been done - that value has to be checked before using Valid_Message).
The implementation comprises the following tasks:

Add predicate Verification_Attempted (Context, Field)
Add precondition to Verify (Context, Field), which enforces the validity of Verification_Attempted (Context, Field) for all definite predecessors of a Field
Add a corresponding postcondition to Verify
Add postcondition to Verify_Message and correspondig precondition to Valid_Message, which enforces the validity of Verification_Attempted for at least one potential final field
Add postcondition, which preserves validity of Verification_Attempted, to all other procedures, which modify Context
(Simplify Valid_Message to only check validity of potential final field and corresponding outgoing condition)


chore: update stylua-action version

1.0.0 is broken and is causing the pipeline to fail.
This PR fixes back the pipeline.

thank you!


feat: native world state

This PR adds a new CPP module for managing the merkle trees that make up the world state. A new implementetion of MerkleTreeDb is provided to interact with the native code.
msgpack is used to pass messages across the js<->cpp boundary. Tests have been added to assert that the two world state implementations work in the same way (more tests would be better).
This PR builds on top of #7037.
PS: I'm not as experienced with C++

A question for @ludamad maybe. Should this all be in barretenberg/cpp/src/{world_state, etc} instead of barretenberg/cpp/src/barretenberg/{world_state, etc}. Seems like we'd want to have some separation between what't the core proving system and things around it (even if it means doing some work on the cmake side).
PS: on that note, it might also make sense to move the AVM one level up from here.

Benchmark results
Metrics with a significant change:

avm_simulation_time_ms (Token:transfer_public): 41.9 (+105%)

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,784
1,570
714
757 (-1%)
779 (+1%)

proof_construction_time_sha256_30_ms
11,600 (+1%)
3,134 (+2%)
1,401 (+2%)
1,471 (+5%)
1,479 (+1%)

proof_construction_time_sha256_100_ms
44,528 (+1%)
12,004 (+2%)
5,667 (+4%)
5,735 (+4%)
5,941 (+5%)

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
58.0 (-3%)
88.0 (-1%)

proof_construction_time_poseidon_hash_30_ms
1,528
423
203 (-1%)
230 (+5%)
269

proof_construction_time_poseidon_hash_100_ms
5,651
1,530 (+1%)
681 (-2%)
734 (+1%)
749 (+1%)

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

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
4,356
7,876
14,884

l1_rollup_calldata_gas
50,172
92,998
178,180

l1_rollup_execution_gas
842,832
1,576,554
3,361,792

l2_block_processing_time_in_ms
258 (-2%)
469 (+3%)
836

l2_block_building_time_in_ms
11,358
22,167
44,735 (+1%)

l2_block_rollup_simulation_time_in_ms
11,358
22,166
44,735 (+1%)

l2_block_public_tx_process_time_in_ms
9,639 (-1%)
20,357
42,884 (+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,040 (-1%)
4,089 (+4%)

node_database_size_in_bytes
12,664,912 (+1%)
16,736,336

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
97.4 (+7%)
403 (+2%)
21,735
44,860
N/A

private-kernel-inner
175 (+2%)
687 (-2%)
72,544
45,007
N/A

private-kernel-reset-tiny
309
704 (-2%)
65,593
44,846
N/A

private-kernel-tail
166
131 (-6%)
50,644
52,257
N/A

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

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

base-rollup
3,442
N/A
189,136
664
N/A

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

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

public-kernel-app-logic
96.9
N/A
104,911
71,222
N/A

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

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

private-kernel-tail-to-public
1,367 (-1%)
591 (-4%)
455,400
1,825
N/A

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

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

undefined
N/A
N/A
N/A
N/A
88,711 (+12%)

Stats on running time collected for app circuits

Function
input_size_in_bytes
output_size_in_bytes
witness_generation_time_in_ms

ContractClassRegisterer:register
1,344
11,731
344

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

MultiCallEntrypoint:entrypoint
1,920
11,731
405

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

SchnorrAccount:constructor
1,312
11,731
73.9

SchnorrAccount:entrypoint
2,304
11,731
394

Token:privately_mint_private_note
1,280
11,731
97.6 (-4%)

FPC:fee_entrypoint_public
1,344
11,731
26.4 (-12%)

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

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

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
747 (+5%)

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

Function
time_ms
bytecode_size_in_bytes

FeeJuice:_increase_public_balance
57.9 (-11%)
7,101

FeeJuice:set_portal
11.9 (+19%)
2,128

Token:constructor
87.6 (+8%)
25,285

FPC:constructor
67.3 (+23%)
17,853

FeeJuice:mint_public
38.9 (-2%)
5,415

Token:mint_public
43.3 (-4%)
10,101

Token:assert_minter_and_mint
66.1
6,844

AuthRegistry:set_authorized
46.1 (+12%)
3,969

FPC:prepare_fee
245 (+6%)
6,747

Token:transfer_public
:warning: 41.9 (+105%)
38,126

FPC:pay_refund
57.3 (+15%)
9,398

Benchmarking:increment_balance
1,196
6,179

Token:_increase_public_balance
39.9
7,705

FPC:pay_refund_with_shielded_rebate
63.4 (-2%)
9,881

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.169 (+6%)

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.20
3.91 (-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.114 (-1%)
0.110 (-2%)
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 (-1%)
17.7 (-2%)
30.8 (-5%)
62.1 (+5%)
114 (-2%)

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.108 (-2%)
0.103 (-2%)
0.0998 (-4%)
0.107 (+5%)
0.102 (-1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
14.4 (-1%)
25.9 (-1%)
43.9 (-3%)
84.5 (+2%)
164 (-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.109 (-1%)
0.103 (-1%)
0.106 (-3%)
0.104 (+2%)
0.105

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
16.7
N/A
N/A
N/A
N/A

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

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.107
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 |  |
| - |  |

Re organization, so far e.g. the AVM stuff is all over and we've been okay with it, but I'd sympathize with wanting it in its own module. No strong opinions at this time

Re organization, so far e.g. the AVM stuff is all over and we've been okay with it, but I'd sympathize with wanting it in its own module. No strong opinions at this time

But this is not avm, right? :)
I think recently I made some changes and now all AVM files should at least always be under barretenberg/cpp/vm (also the generated ones and the relations). Of course, there's also the unavoidable things in main.cpp. Maybe it can already be made a module? (not sure how cmake works)

I was just saying I agree with separation but no strong opinions, as I hadn't had with AVM

Cmake changes look otherwise good


Add watertight dicing option to objects

I think the formatting for the watertight is correct.  The online docs just say "dice" "watertight" but that crashes the exporter with an access violation.  So I put in the "int" part and rendering works fine, but I don't have a good example file to see if it's actually doing anything different.


ControlNet problem

ControlNet always keeps crash no matter which model I use on colab.
Loading preprocessor: canny, model: control_sd15_canny [fef5e48e]
^C

It's a memory leak that's been happening, presumably due to a regression with tcmalloc, or something that relies on a previously existing functionality, it's all a bit of a mystery at this moment. Add the below code as a cell in the notebook, run it (Only once), then the leak should stop happening entirely.
!wget http://launchpadlibrarian.net/367274644/libgoogle-perftools-dev_2.5-2.2ubuntu3_amd64.deb
!wget https://launchpad.net/ubuntu/+source/google-perftools/2.5-2.2ubuntu3/+build/14795286/+files/google-perftools_2.5-2.2ubuntu3_all.deb
!wget https://launchpad.net/ubuntu/+source/google-perftools/2.5-2.2ubuntu3/+build/14795286/+files/libtcmalloc-minimal4_2.5-2.2ubuntu3_amd64.deb
!wget https://launchpad.net/ubuntu/+source/google-perftools/2.5-2.2ubuntu3/+build/14795286/+files/libgoogle-perftools4_2.5-2.2ubuntu3_amd64.deb
!apt install -qq libunwind8-dev
!dpkg -i *.deb
%env LD_PRELOAD=libtcmalloc.so
!rm *.deb

It's a memory leak that's been happening, presumably due to a regression with tcmalloc, or something that relies on a previously existing functionality, it's all a bit of a mystery at this moment, but it currently causes issues with nearly every AI related notebook for Colab. Add the below code as a cell in the notebook, run it (Only once), then the leak should stop happening entirely for the remainder of the Colab session.
!wget http://launchpadlibrarian.net/367274644/libgoogle-perftools-dev_2.5-2.2ubuntu3_amd64.deb
!wget https://launchpad.net/ubuntu/+source/google-perftools/2.5-2.2ubuntu3/+build/14795286/+files/google-perftools_2.5-2.2ubuntu3_all.deb
!wget https://launchpad.net/ubuntu/+source/google-perftools/2.5-2.2ubuntu3/+build/14795286/+files/libtcmalloc-minimal4_2.5-2.2ubuntu3_amd64.deb
!wget https://launchpad.net/ubuntu/+source/google-perftools/2.5-2.2ubuntu3/+build/14795286/+files/libgoogle-perftools4_2.5-2.2ubuntu3_amd64.deb
!apt install -qq libunwind8-dev
!dpkg -i *.deb
%env LD_PRELOAD=libtcmalloc.so
!rm *.deb

It worked, thank you.

It's a memory leak that's been happening, presumably due to a regression with tcmalloc, or something that relies on a previously existing functionality, it's all a bit of a mystery at this moment, but it currently causes issues with nearly every AI related notebook for Colab. Add the below code as a cell in the notebook, run it (Only once), then the leak should stop happening entirely for the remainder of the Colab session.
!wget http://launchpadlibrarian.net/367274644/libgoogle-perftools-dev_2.5-2.2ubuntu3_amd64.deb
!wget https://launchpad.net/ubuntu/+source/google-perftools/2.5-2.2ubuntu3/+build/14795286/+files/google-perftools_2.5-2.2ubuntu3_all.deb
!wget https://launchpad.net/ubuntu/+source/google-perftools/2.5-2.2ubuntu3/+build/14795286/+files/libtcmalloc-minimal4_2.5-2.2ubuntu3_amd64.deb
!wget https://launchpad.net/ubuntu/+source/google-perftools/2.5-2.2ubuntu3/+build/14795286/+files/libgoogle-perftools4_2.5-2.2ubuntu3_amd64.deb
!apt install -qq libunwind8-dev
!dpkg -i *.deb
%env LD_PRELOAD=libtcmalloc.so
!rm *.deb

It worked, thank you.

Issue should be fine to close now, since @TheLastBen integrated my proposed fix.🥳

@Daviljoe193 Hey, whenever you have time, find us a way to suppress this useless tensorflow msg https://awesomescreenshot.s3.amazonaws.com/image/4038606/37154912-2443b5d1912f7b01da354f36711bb15a.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJSCJQ2NM3XLFPVKA%2F20230218%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230218T190354Z&X-Amz-Expires=28800&X-Amz-SignedHeaders=host&X-Amz-Signature=cf3d8d550a65395a09ee3698733a218dbb5eaf44516a8177bede6c70532491d3

@Daviljoe193 Hey, whenever you have time, find us a way to suppress this useless tensorflow msg

Placing this python anywhere in the notebook before the webui launch will do exactly that! 😁
import os
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '3'
import tensorflow as tf

Great! thanks.


support >1 custom fields per system in datamap export

Closes https://github.com/ethyca/fidesplus/issues/679.
Code Changes

for systems with privacy declarations and with custom field data, our iteration to add the custom field data looked like this:

for each custom field, iterate over each product (row of output data); and then within each product (row), add the custom field value to the row, and add the row to the list of output rows (the cartesian_product_of_declaration itself gets appended to the output_list):

if system_custom_field_data:
  for _, v in system_custom_field_data.items():
    for product in cartesian_product_of_declaration_builder:
      product.append(v)
      cartesian_product_of_declaration.append(tuple(product))

this had the effect of adding a new row of output data for each custom field - which is not what we want!
instead, what we do now is: for each product (row), iterate over each custom field; within each custom field, add it to the row; then, add the updated row to the ultimate list of output rows:

for product in cartesian_product_of_declaration_builder:
  if system_custom_field_data:
    for _, v in system_custom_field_data.items():
      product.append(v)
  cartesian_product_of_declaration.append(tuple(product))

separately: added in a bunch of "brute force" end-to-end automated tests around datamap export

Steps to Confirm

it's a bit tricky to manually test this on just fides since we rely on both the datamap UI and the custom field UI that's available only in fidesplus - (even more of a reason to add the automated tests!)

it's worth noting, the automated tests that were added were failing before this fix was in place - specifically the test_datamap_privacy_declarations_two_custom_fields test case

the steps in https://github.com/ethyca/fides/pull/2775 can be used as a reference and adjusted accordingly

Pre-Merge Checklist

[x] All CI Pipelines Succeeded
Documentation:

[ ] documentation complete, PR opened in fidesdocs
[ ] documentation issue created in fidesdocs

[x] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[x] Update CHANGELOG.md

Description Of Changes
The code change for this particular fix is small - just switching around a nested iteration that had the wrong nesting order.
More substantially, I decided to add a fair amount of "end-to-end" test coverage around the export_datamap endpoint and its handling of custom metadata. Previously the automated tests were not doing much besides confirming we got the appropriate response code - in fact, the response bodies in the tests weren't actually populated with any data, they just had the "column header" row. Within the 2.8.x releases/hotfixes, we've experiencing a bit of 'whack-a-mole' with the datamap generation code - as we've fixed one problem, other problems have arisen. Even if the "new" problems haven't been directly caused by the fixes to the "old" problems, trying to manually cover all test cases with each new fix has proven difficult and time consuming. Additionally, without test cases covering the export code and custom metadata, it was difficult to get a debugger onto some of the problem states, meaning we'd need to rely on static analysis of some rather complex data manipulation code. In short - automated tests are a pretty critical first step for trying to make this more robust!
The test coverage that was added is a brute force approach to all (or most) of the different combinations of features/scenarios that can arise with the datamap export and custom metadata as we have it now. This probably isn't a good final state for this test coverage, but I decided to go the brute force approach for now, because:

having any automated_ test coverage of the custom metadata export, even if it's a bit unwieldy, is a lot better than not having any! the end-to-end "integration" tests here allow us to feel confident that we've got the functionality we need in place
we need a fix for the >1 custom fields problem quickly, as it's impacting customers
we should likely refactor some of the datamap export code anyway since the use now for the export has drifted from its original use as a CLI command; at that point, we can improve the test coverage

i'll create a tech debt follow-up ticket for this item so we don't lose track of it

-- UPDATE --
I'm noticing that we did already have some test coverage around custom field and datamap export in https://github.com/ethyca/fides/blob/main/tests/ctl/core/test_export.py - but it seems minimal. going forward, we could look at updating that to provide more comprehensive unit test coverage that's a bit more maintainable, rather than relying only on the brute force, end-to-end integration tests i've got in this PR. that being said, i still think the integration tests here are helpful in ensuring our end-to-end functionality is working well across a variety of use cases.

Thanks @adamsachs, great work!


SmartThings devices' ias_zone appear as moisture sensor device_class

The ST Motion Sensor and Multipurpose Sensor both have an ias_zone that is incorrectly showing up as a moisture sensor device_class. This is possibly related to #170
You can override this in the Home Assistant UI, but that is a pain for many devices.

This was fixed by #226 in the last release of the lib and will be in the next release of HA.


Moon phase

Thank you for this. I like to know the moon phase, such as Last Quarter. Is it possible to include this as well as how many days old the moon is?

To clarify, do you mean a text output instead of an emoji ("Last Quarter" instead of "🌗")?
Also, isn't the moon's day the same as the age of the moon? If so, this is output by default and can be accessed using the "%M" placeholder in the output format. Sorry, I am not particularly familiar with lunar terminology.

The emoji is great. But a text output would be good particularly in
distinguishing between the last and first quarter, for instance, or waning
gibbous versus waning crescent.
On Sun, 15 Jan 2023 at 23:34, Mubariz Ahmed @.***>
wrote:

To clarify, do you mean a text output instead of an emoji ("Last Quarter"
instead of "🌗")?
Also, isn't the moon's day the same as the age of the moon? If so, this is
output by default and can be accessed using the "%M" placeholder in the
output format. Sorry, I am not particularly familiar with lunar terminology.
—
Reply to this email directly, view it on GitHub
https://github.com/mubarizahmed/obsidian-weather-moon/issues/1#issuecomment-1383139819,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTR6N2ZGWT76SOE5SDVULDWSPVE5ANCNFSM6AAAAAAT3WLWN4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks but %n doesn't seem to generate anything for me.
On Wed, 18 Jan 2023 at 02:08, Mubariz Ahmed @.***>
wrote:

Closed #1 https://github.com/mubarizahmed/obsidian-weather-moon/issues/1
as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/mubarizahmed/obsidian-weather-moon/issues/1#event-8246664022,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTR6NZ7PA4ZNB6CY3HQ3ATWS2YVFANCNFSM6AAAAAAT3WLWN4
.
You are receiving this because you authored the thread.Message ID:
@.***
com>


VPP resize generates jumpy frames (for 2:3 pulldown coded video)

I have a stream which contains mixed PicStructs (combinations of Progressive, TFF, BFF, Field_Repeat). When decoding and resizing through VPP the frames jumps up and down in vertical direction. It also looks like Top and Bottom field gets mixed up.
Reproducable with:
sample_multi_transcode -i::mpeg2 video_es.mpeg2 -o::raw out.raw -w 720 -h 480
Input stream:
https://a2b-my.sharepoint.com/:u:/g/personal/herman_molinder_wisi_se/Ec0zRVAAyzhLqFj5EcQAZT0B2QcwpbyjVMKM66rXA3t3zA?e=ZaEndf
Without resizing output looks fine.
Tested on Media SDK 20.1.0 on both Apollo Lake and Kaby Lake.

We have already worked on that. Will update it soon.

@FurongZhang ,
I'm really glad to hear that! When do you estimate this fix will be released?

@HermanMolinder
Hi, I checked this issue. You can add deinterlace force VPP to deinterlace input stream.
sample_multi_transcode -i::mpeg2 video_es.mpeg2 -o::raw out.raw -w 720 -h 480 -deinterlace::BOB
It may help you fix this problem. Thx.

@VickyZengg ,
Thank you, but we need to output it as interlaced. It's also a performance concern. So deinterlacing isn't a good solution for our application.

You mean, for the interlaced frame, you need to output the interlaced and scaled frames. Right? If yes, for the interlaced frames, we can do some interlaced scaling.

@FurongZhang
Yes, that's right. The output is fed to a PAL/NTSC modulator, which expects an interlaced video that is 720x576/720x480.

And for this particular  stream we check the Field_Repeat flag to decide if some fields are to be repeated to the modulator.

Hi @FurongZhang ,
This issue is still present in Media SDK release 20.3.0.
You mentioned that you had worked on this issue? Can you please elaborate?
BR
Herman

Yes, we almost rooted cause this issue. Next Monday, we can give you an update about this issue.

Thank you. I'm happy to hear that!

Hi @HermanMolinder
We rooted cause this issue. In interlaced scale, we take different ways to deal with top field and bottom field. So it looks like jumpy in mixed PicStructs. Top and Bottom field didn't get mixed up. The purpose of this different ways is to make the interlaced scale quality better. Do you have any quality concerns else?

Hi @VickyZengg ,
I see, that explains a lot! Do you have a solution for this?
I don't have any other quality concerns for now.

Hi @HermanMolinder
This behavior is expected, it improves interlaced scale quality. If you don't have other quality concerns, it's no need to change it.
If you have, please feel free to let us know.
Thanks,
Vicky

@VickyZengg ,
I think we misunderstood each other.
The input stream (with mixed PicStruct) is a valid MPEG stream and the resulting output has inferior quality which is not expected. I want to claim that this is a bug that needs to be fixed.
BR
Herman

Hi @HermanMolinder
Interlaced content can't be played directly. In interlaced content, we think this jumpy is expected.
Is it still jumpy after deinterlaced?
Thanks,
Vicky

Hi @VickyZengg ,
Our application decodes, processes and modulates a PAL/NTSC signal. PAL/NTSC is interlaced and can be viewed on a CRT TV without any deinterlacing involved.
This video stream is decoded correctly, without jumpy picture and without deinterlacing, in other professional decoder chipsets. So this is something we really need help solving in Intel Media SDK.
Please tell me if you want me to explain more. We can have a video conference meeting if that makes it easier.
BR
Herman

Hi @HermanMolinder
I update one patch : https://github.com/VickyZengg/media-driver
Can you use this driver to see if it fix the problem?
Waiting for your reply. Thank you.
Thanks,
Vicky

Hi @VickyZengg ,
I tested your patch and still get jumpy picture.
BR
Herman

Hi @HermanMolinder  The jumpy is the same as before?

@VickyZengg
It looked the same, but I need to double check to be sure if it was exactly the same behavior. Need to check that in our office, which I will be back to next week.

Hi @HermanMolinder , it can't be the same. We did test, they are not bitmatch. If you have any problems in compiling driver, please contact me. Thank you.

Hi @VickyZengg ,
Sorry for the delay. Haven't been able to test this until now, due to ongoing pandemic..
You're right, with your patch applied the picture looks different. It doesn't look good though. The picture is still jumpy, and for "normal" interlaced content the quality has been reduced. There're combing artefacts. So this actually made it worse.
BR
Herman


Add ways of differentiating between public and controlled metadata

Add tags to differentiate between public and controlled metadata.
These tags should allow automated differentiation of which metadata fields are public vs controlled.

Achieved via subsets.


What about middlewares?

I noticed api metrics are not available if response is created and returned from a nest middleware.
Is there anything I can do on the middleware itself to get api metrics of it?

Nevermind. I found It has something to do with the nestjs's middleware order =/


forward as attachment is broken (.eml)

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.802
Where did you get the app from?
Google Play
Android version
14
Device model
Pixel 7 Pro
Steps to reproduce

Go to inbox
Open a mail
Select 3-dot menu
Select Forward as attachment
Send mail to someone

Expected behavior
Mail gets forwarded as an attached .eml file
Actual behavior
the .eml file is empty.
in the "sent" folder it has content while it's empty for the receiver.
This was only tested within the K9 mail client. (Sender and receiver)
I tested multiple mail accounts
This is reproducible and I have tested different mails
Logs
No response

Have you checked if the .eml file is actually empty? It shows as "0 B" in K-9 Mail, but otherwise should contain all data.

Have you checked if the .eml file is actually empty? It shows as "0 B" in K-9 Mail, but otherwise should contain all data.

Hello. I've checked it. The file is not really empty. When we open it, it shows the content and it's not empty. However, the email display screen only shows the size as 0. While it's not really zero, it does contain content.
Now, considering this, I think we should fix the issue of the size being shown as zero. Am I right? Do you have any thoughts on this?

ups, I checked and then forgot to answer. I wanted to check and compare/hash the files on desktop first. I will do that now.

Have you checked if the .eml file is actually empty? It shows as "0 B" in K-9 Mail, but otherwise should contain all data.

Hello. I've checked it. The file is not really empty. When we open it, it shows the content and it's not empty. However, the email display screen only shows the size as 0. While it's not really zero, it does contain content. Now, considering this, I think we should fix the issue of the size being shown as zero. Am I right? Do you have any thoughts on this?

I debugged. Actually, on the receiving side of the email, the field size(attachment.size) of the .eml attachments is zero. Do you have an idea to fix this problem? that we can find and display the real size of those attachments? @cketti

Have you checked if the .eml file is actually empty? It shows as "0 B" in K-9 Mail, but otherwise should contain all data.

Hello. I've checked it. The file is not really empty. When we open it, it shows the content and it's not empty. However, the email display screen only shows the size as 0. While it's not really zero, it does contain content. Now, considering this, I think we should fix the issue of the size being shown as zero. Am I right? Do you have any thoughts on this?

I continued debugging and examined the code in more detail. I realized that even on the sender's side, if the database is cleared once after sending the message and we try to reopen that message, it also shows a size of zero (on the sender's side)!!


Add option for TrailingCommaOnCallSite to ignore  this rule when argument is multiline

Expected Behavior
Make trailing comma on call side optional for multiline arguments
Current Behavior
The callDelegate.enqueue method has one argument, but this argument is multiline, so a comma at the end (2nd to last line)
is questionable.

            }
        },
    )

Additional information

Current version of ktlint: 0.48.0

This request is similar to #1820. See comment https://github.com/pinterest/ktlint/issues/1820#issuecomment-1428566271 why this will not be implemented.


Update jsdom to v11.1.0 and chai to v4.1.1.

Note that we are still using the old API.
Also, jsdom requires node.js >= 6 now.
/CC @mikelambert @RyanZim

Coverage remained the same at 97.328% when pulling c1015a4000a55fe89272753392c79d12d2f919f2 on update-jsdom into c4333d2bf20914a536e804d12695095e56564411 on master.

Coverage remained the same at 97.328% when pulling 1e5bc8600807e8363a610fc853be91663c434e61 on update-jsdom into c4333d2bf20914a536e804d12695095e56564411 on master.

Does this fix canvas issues?

Didn't try that yet; I'll try later and let you know. Also it seems tests fail at resemble on Appveyor for some reason while they work fine locally on Windows.

OK, I tested canvas and is still not implemented.

OK, windows is passing now. I guess I'm just wondering what this is supposed to be fixing. Or is it just a general dep upgrade?

It's a general update hoping we can look into moving the new API. jsdom.env isn't available as far as I can tell.

LGTM if we're OK with dropping Node 4 (I am)

It might be worth looking into updating to the new API in this PR before merging.

If we're going to drop Node 4, then does that mean we need a major semver change? But I'd hate to do a semver bump just for a functionally-identical dependencies upgrade... :/
When you say jsdom.env isn't available, are you referring to the new API vs the old API (which has it)?

Yeah the new API does not have it.
IMO we should switch to the new API sooner than later.
Anyway I can't really comment on node 4 since I personally use the latest
LTS version.
On Aug 5, 2017 22:01, "Mike Lambert"<EMAIL_ADDRESS>wrote:

If we're going to drop Node 4, then does that mean we need a major semver
change? But I'd hate to do a semver bump just for a functionally-identical
dependencies upgrade... :/
When you say jsdom.env isn't available, are you referring to the new API
vs the old API (which has it)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/giakki/uncss/pull/324#issuecomment-320463954, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVVtePTzR-5Aqr04fyf04aqehhsivpqks5sVLwUgaJpZM4Ouako
.

I don't use node 4 either. My point was that dropping support for node 4 without a major semver release, means downstream dependencies may suddenly break. (ie their travis builds...or a fresh reinstall of their project into their runtime environment, etc). They can fix it by hardcoding a direct version...but we are breaking the semantic guarantees of semver if we don't bump, right? (Don't need to be a node 4 user to be able to comment on this :P )

I meant that I don't really care about the version change :) I know about
semver but we didn't really follow it with 0.15 either...
On Aug 5, 2017 22:16, "Mike Lambert"<EMAIL_ADDRESS>wrote:

I don't use node 4 either. My point was that dropping support for node 4
without a major semver release, means downstream dependencies may suddenly
break. (ie their travis builds...or a fresh reinstall of their project into
their runtime environment, etc). They can fix it by hardcoding a direct
version...but we are breaking the semantic guarantees of semver if we don't
bump, right? (Don't need to be a node 4 user to be able to comment on this
:P )
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/giakki/uncss/pull/324#issuecomment-320464879, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVVtVAkJmI4GLPh2PKr-wQHQrVJ_oWaks5sVL-WgaJpZM4Ouako
.

Ahh fair, good point. I think 0.15 breakage was actually a result of my first big change to this project (to move to postcss), before I was a "maintainer" and had "responsibility" for this package. ;) And to be fair, I was new to the node/npm world and had no clue what LTS or node versions really meant...

So, anyone willing to have a take on updating the API calls? I had a quick look yesterday but didn't succeed.

Coverage remained the same at 97.328% when pulling e23db9ed4a7b58445f3cec00a55c1bce780f9351 on update-jsdom into e0c4243a89b4a0cbf0fd6a9097092df84cb141d6 on master.

@RyanZim @mikelambert: I updated all deps here; tests are passing so I think we are good to go.

Not a Node 4 user either, but this definitely needs to be released as semver-major. If we're going to do this, we should remove Bluebird and upgrade our code to the ES6 supported by Node 6+ as well. Thoughts everyone?

Well, sure but that is for another PR :)

So I'm against submitting a version-identical change that means we need to do a semver upgrade, for no net benefit. And I hate having submitted-changes on the master branch that are not yet released to NPM, as makes it difficult to do other patch fixes if they come in.
However, I am okay with this change, if it means we are also going to do the Promise cleanup and perhaps the JSDom API upgrade, and get our whole system in a much better state.
So perhaps the best way to resolve that is to commit this into a branch, where these further-on features can be done, and then pulled in all-at-once?

@mikelambert I agree. I changed the base branch to develop, and merged it. Whoever/whenever we get a chance, we can open PRs against that branch for further development for the next major release.

Working on ES6 syntax upgrades

Are you sure that ES6 syntax upgrades are okay? I've occasionally run into problems with trying to use modules that use ES6 (due to assumptions that only the top-level code needs transpilation), and I thought it was still best practice not to publish modules to NPM that use ES6 (unless you're in the react-native world, for example)

I'm not upgrading to all ES6 syntax, only the parts supported by Node v4+. I've done this with all of my packages that don't support Node 4 with zero issues. We just should make a clear note in the README that we only support Node 4+, and tell users to downgrade to 0.15.0 if they need Node 4 support.


New extension ID created on new build

There's a new extension ID that gets created on new builds that prevents from me validating oauth

Can you elaborate on what the issue is?

We will close this issue as there has been no additional feedback for a long time.


Fix file spec when HOME ends with /

For example:
  1) File expand_path converts a pathname to an absolute pathname, using ~ (home) as base
	     Failure/Error: File.expand_path("~/").should eq(home)

	       expected: "/jenkins-slave/"
	            got: "/jenkins-slave"

	     # spec/std/file_spec.cr:417

It seems a couple of specs still fail

I guess travis's HOME is /. The speced method behaves correctly but the strip solution fails to give the correct expected answer.

Maybe return "/" for home if it ends up being empty?

(or return "/" if home is "/")

Looks like it's going to pass this time.


add order to how tags are shown

tags are shown in ui in an order that one can not change
if one can change it how do you do so dynamically -- ie. place it in the middle, at the top or at the bottom?
how does this work when yaml files update your data on load?

A few thoughts cross my mind:

It's probably acceptable to set this order "globally", rather than on the specific feature you are tagging.
In general, it might be useful to send some metadata to b6 for usage by the UI. This already happens with the "centroid" and "docked" directives on the root collection

In detail, as discussed, it could look like:

Setting a kind of "label-order" directive to something standard like: alphabetical, or similar.
Hard-coding a list of labels in the given order; with any label not appearing in that list just being ordered subsequently alphabetically
???

The thing to work out would be how to provide this information.
Options:

Add a new function, called set-label-ordering which would do this, and take effect in subsequent actions
Provide it as a metadata config file to the b6 executable
Provide it as a command-line arg to b6
Add it as a new directive alongside "centroid" and "docked" (bit strange, as these typically refer to features)
???

I'd be tempted to go for the new function, or the metadata config file. Maybe the new function is a bit more idiomatic to how b6 works at present.


Adding documentation for BigInt.to_s methods

In src/big_int/big_int.cr :

add documentation for to_s

Thank's for the comment. It should be a BigInt now !

@Nesqwik Thank you! Could you squash into a single commit?

It's done now, sorry for taking so long.

Thanks!


deposit

i was wondering why depositing coin is not detected. i deposited rvn and the bot did not pick it up. it is still showing the old number.

Look, @salimj6
When you ask some questions, I really need more contexts or at least some screenshots.
I won't be able to help you without any further information because I don't have any access to your bot.

Close the issue as I didn't get more information.


Reload firewalld always when config change is detected

Fixes an issue where new nodes cannot connect to weave mesh.

@jnummelin PTAL


chore: Empty commit for the benefit of publish_process.js

Didn't find anything against.

Technically correct. The best kind of correct!


Constance CLI does not work properly without django admin

Describe the problem
It seems disabling django admin's app breaks the constance CLI. As I noticed constance/management/commands/constance.py imports ConstanceForm and get_values from admin configuration. The problem is admin.py tries to register the constance's config class and since the admin app is not present in INSTALLED_APPS django throws a LookupError.
I think splitting ConstanceForm and get_values to a separate module (like forms.py) and importing them directly from that module can easily fix the problem.
Steps  to reproduce

Remove django.contrib.admin from INSTALLED_APPS (And its URL pattern)
Run python manage.py constance --help

System configuration

Django version: 4.0.7
Python version: 3.10.7
Django-Constance version: 2.9.1

I am running into the same thing, this is the error we are getting:
Traceback (most recent call last):
  File "/venv/lib/python3.10/site-packages/django/apps/registry.py", line 156, in get_app_config
    return self.app_configs[app_label]
KeyError: 'admin'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/dashboard/manage.py", line 22, in <module>
    main()
  File "/usr/src/dashboard/manage.py", line 18, in main
    execute_from_command_line(sys.argv)
  File "/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
    utility.execute()
  File "/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 413, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 257, in fetch_command
    klass = load_command_class(app_name, subcommand)
  File "/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 39, in load_command_class
    module = import_module('%s.management.commands.%s' % (app_name, name))
  File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/venv/lib/python3.10/site-packages/constance/management/commands/constance.py", line 10, in <module>
    from ...admin import ConstanceForm, get_values
  File "/venv/lib/python3.10/site-packages/constance/admin.py", line 366, in <module>
    admin.site.register([Config], ConstanceAdmin)
  File "/venv/lib/python3.10/site-packages/django/utils/functional.py", line 246, in inner
    self._setup()
  File "/venv/lib/python3.10/site-packages/django/contrib/admin/sites.py", line 561, in _setup
    AdminSiteClass = import_string(apps.get_app_config('admin').default_site)
  File "/venv/lib/python3.10/site-packages/django/apps/registry.py", line 163, in get_app_config
    raise LookupError(message)
LookupError: No installed app with label 'admin'.

@syre @Alirezaja1384 please confirm if this issue was resolved by installing the packed from the main branch

@camilonova I just tested it. It works completely fine. Thank you.


init React package and setup App.tsx

Codecov Report
Attention: Patch coverage is 0% with 18 lines in your changes missing coverage. Please review.

Project coverage is 24.59%. Comparing base (903d1cb) to head (fd6313a).

Files with missing lines
Patch %
Lines

src/App.tsx
0.00%
10 Missing and 1 partial :warning:

src/pages/Home.tsx
0.00%
6 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #2      +/-   ##
==========================================
- Coverage   25.00%   24.59%   -0.41%
==========================================
  Files           5        6       +1
  Lines          60       61       +1
  Branches        6        7       +1
==========================================
  Hits           15       15
  Misses         41       41
- Partials        4        5       +1

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


time.String produces garbage out for time.Parse (garbage in)

time.String() produces non-standard output that time.Parse cannot handle.  This goes against less is more since either a person needs to write a custom parser or change the output format which both increases the code base.
If marked as not a bug nor not fixing, documentation for time package should be updated to inform that that time.String output is incompatible with time.Parse.
What version of Go are you using (go version)?
go1.7.1 linux/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="$HOME/.local/share/go"
GORACE=""
GOROOT="/usr/lib/go"
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build766838131=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
What did you do?
https://play.golang.org/p/wmfQP5wX0S
func main() {
    t := time.Now().UTC()
    s := t.String()

    t, err := time.Parse(s,s)
    if err != nil {
        fmt.Println(s, "parsed with error", err)
    } else {
        fmt.Println(s, "equals", t.String())
    }
}

The first value to time.Parse is the layout. time.String's docs indicate what the layout is. So this works.
If anything here it would be nice to export that format as a constant instead of embedding the string directly in time.String().

You already filed this bug in #17253. What @freeformz is correct. You're just not using the time package correctly.
I recommend https://golang.org/wiki/Questions for questions about learning Go.

Sorry, didn't know layout had to be certain date and time, looked only to be just the format.


[TPU] Implement prefix caching for TPUs

Nice work!

In theory, this should enable chunked prefill too right?

Btw, which command did you use run examples/offline_inference_tpu.py. I used $ python vllm/examples/offline_inference_tpu.py but it fails. Do you need to use a model other than "google/gemma-2b"?

@vanbasten23

Btw, which command did you use run examples/offline_inference_tpu.py. I used $ python vllm/examples/offline_inference_tpu.py but it fails. Do you need to use a model other than "google/gemma-2b"?

This is weird. Which version & TPU are you using?


Add definition for $show_organizations

Purpose
Commit 97606bf added support for show_organizations in the people widget. The original author forgot to add the definition of this variable at top of the widget, leading to hugo not being able to build the site because the variable was not initialized.
This commit adds a definition for show_organizations at the top of the widget to fix the build error.
Documentation
As described in commit 97606bf, you can set the value of show_organizations in the people widget's design section. See an example config at this page and add show_organizations: true at the end of it.

Thanks for submitted a fix!


[bug] image not found if an image sha256 updated

Ⅰ. Issue Description
some application use image sha256 to visit the image, so when the image updated, it will occur image not found error.
Ⅱ. Describe what happened
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

pouch version (use pouch version):
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

Any update? Please sync with the community about the status. @HusterWan


Server error while obtaining access token from XSUAA (502 BAD_GATEWAY)

Hi,
Below is the code I used to get the client credential. Most of the time, the code works, but in one case, it gives me the error. "c.s.c.s.x.c.XsuaaOAuth2TokenService      : Server error while obtaining access token from XSUAA (502 BAD_GATEWAY): 502 Bad Gateway: Registered endpoint failed to handle the request."
Do you have any idea for this ? Attached is the log. Uploading log.txt…
Thank you for your help,
Best regards
XsuaaTokenFlows tokenFlows = new XsuaaTokenFlows(
tokenService,
new XsuaaDefaultEndpoints(xsUaaUri),
new ClientCredentials(clientId, clientSecret));
OAuth2TokenResponse clientCredentialsToken = tokenFlows.clientCredentialsTokenFlow().execute();

Hi @yduong
as the client libs logs the issues, that are received from the xsuaa service, i would suggest you to create either a BCP ticket or a JIRA NGPBUG on component "xsuaa".
Thanks and best regards,
Nena


this commit adds the first version of description about traits into U…

This adds the first version of description about traits into user manual.

@vahdat-ab Great start on traits for the user manual. It is very timely since I will be lecturing about traits on Thursday and would love to be able to point to relevant pages and code examples in the user manual.
However, could you please make the following adjustments before merging it:

Please put traits after 'Methods' in the user manual, not before: Reason: Logically, people will want to learn first about methods, because they are used in traits. That requires a minor adjustment to order.group

In all your examples, could you please elaborate slightly on the comment. For example, rather than just saying 'Example 1', say 'Example 1: using template parameters in traits' (or whatever is relevant). Reason: This will ensure that when they are loaded in Umpleonline, or otherwise observed out of context, that people know what is special about the code.

The titles (and generated URLs) of many of your pages will end up being too generic. For example
in build/reference/0607traits_state_machines.txt, you have on the first line as page title
Basic Definitions
That will end up generating a URL BasicDefinitions.html
The problem with that is that if someone wants to cross reference it, or looks at the URL, it will seem as though the page is talking about Umple basic definitions in general.

Can you please change this to
Traits
which will continue to generate Trait.html
(another possibility would be to use 'Basic Definition of Traits'. The problem is your pull request will delete the generated Traits.html page, and I have already pointed people to this URL, and there is a link to in at least one place in the manual, so Google will have indexed it).
Other cases:
Clients -> Clients of Traits
Attributes -> Attributes in Traits
Template Parameters -> Trait Template Parameters
Associations -> Associations in Traits
State Machines -> State Machines in Traits
(Required Interfaces and others I have not mentioned are OK as they are specific enough)

The page State Machine Operators is too long. Can you split it into 3 parts:
at points indicated below (I have copied text from your existing titles). The first part of the page would have the material up to:
Removing/keeping a state machine

start a new page here called Selecting Operators
and up to just before the existing heading
Extending a state by adding a state machine to it
starts new page here called Extending a State
Obviously the correct examples would be put on the relevant pages.

You have specified the same syntax elements on every one of the pages. Can you vary this by putting the relevant syntax elements on the relevant pages?

If possible, could you add a few hyperlinks in some of the pages so people can jump around more easily (this is lower priority and could be done later; hyperlinks would point to the generated name, which is composed from the title, with spaces removed ... see existing examples)

The internal details (writing) is quite good. I may do some light textual editing later, but if you do the above 5 (or 6) changes you can then merge the PR without further input from me.

@TimLethbridge Thanks for the review.
Item 1 is done.
Item 2 is done.
Item 3 is done. I changed the title to Traits to keep links valid. I also provided unique titles for all pages.
item 4 is done.
item 6 is done.
Item 5: I could not get the point. Could you please explain more?

By item 5 I meant this:
For @@syntax in each of your pages, you have specified
[[traitDefinition]] [[traitContent]]
That will expand both of on every page. I think you need these two on the first page, but the other pages should not repeat them. It is redundant, from the readers perspective. However on the Trait Template parameters page, it might be reasonable to specify
[[traitParameters]] [[traitFullParameters]] [[traitParametersInterface]] [[gTemplateParameter]] [[AllInclusionExclusionAlias]]
... and so on. In other words, the relevant grammar items for the topics on that page.

One more point I just noticed.
Please keep umpleonline/ump/manualexamples/Traits1.ump
and please add back this at the end of the first traits manual page
This is a good example of practical use. And it has been mentioned already in teaching materal.


Add timeout configuration

Closes #133
Fortunately, Apache HttpClient offers 3 types of timeout configuration:

http.socket.timeout
http.connection.timeout
http.conn-manager.timeout: This is for multithreaded requests situation, which seems not applicable for sbt-sonatype, IIUC.

This PR exposes (1) socket timeout and (2) connection timeout.
Values are given to http client only if explicitly configured.
So I think this is NOT going to be a breacking change.
Sorry, not tested at all, since I could not figure how to test this feature.

Thanks for the PR. A concern is we usually don't know the right timeout configuration. For example, connection timeout is usually should be less than 1 min, so that we can quickly resend the request if the server is not responding. So rather than configuring, http client's parameter, we should use a longer total retry attempt duration.
The current sbt-sonatype implementation is already 6-year old, and I'd like to revise the entire code to use the state-of-the-art techniques (e.g., use airframe-http-client, airframe-control Retry, etc.) based on JSON, instead of using XML. In doing so, adding such extra config can incur a migration cost if we can drop these configurations.
If you really need this feature right now, instead of adding such a configuration, we should use longer default timeout values or retry intervals.

OK to close this PR.
Retry is fine for me, if users can increase the number of retries and/or wait between retries, for expected very long operation on Sonatype end.

Closing because new HTTP client will add more granular control of timeout


Fixes the license value in package.json

As documented on the NPM documentation (https://docs.npmjs.com/files/package.json#license). The license field has to comply with the SPDX specification for communicating the licenses and copyrights associated with a software package. This commit changes the license to a valid SPDX value (MIT)

Hi,
I see you've been going through the entire JS community making this kind of fix. Why so? Isn't that a minute detail? Have you been mandated to do so?
Just curious,
--Martin

i built npmcompare.com and one of the values i look at is the license.
it helps me personally that everyone will be syncronized.
plus it's a small contribution to the community that gave me so much.. but it's something..


Promethus operator fails to start Promethus pods after upgrading from pelorus-operator.v0.0.8 to pelorus-operator.v0.0.9

OpenShift version
4.13
Problem description
After upgrading from pelorus-operator.v0.0.8 to pelorus-operator.v0.0.9, Promethus operator pod shows below error and fails to start Promethus pods:
level=info ts=2024-07-01T15:26:40.289390758Z caller=operator.go:1163 component=prometheusoperator msg="sync prometheus" key=pelorus-operator/prometheus-pelorus
level=error ts=2024-07-01T15:26:40.322958155Z caller=klog.go:116 component=k8s_client_runtime func=ErrorDepth msg="Sync \"pelorus-operator/prometheus-pelorus\" failed: creating config failed: generating config failed: unmarshalling additional scrape configs failed: yaml: line 7: did not find expected '-' indicator"

Steps to reproduce

install Pelorus operator pelorus-operator.v0.0.9
create a new instance of Pelorus with following yaml:

kind: Pelorus
apiVersion: charts.pelorus.dora-metrics.io/v1alpha1
metadata:
  name: pelorus-devspaces
spec:
  federate_openshift_monitoring:
    enabled: true
    metrics_filter:
      # pull devspaces metrics we're interested in
      - "{namespace=~'.*-devspaces',pod=~'workspace.+'}"
  exporters:
    instances: []
  prometheus_storage: true
  prometheus_storage_pvc_capacity: 3Gi
  prometheus_storage_pvc_storageclass: gp2
  prometheus_retention_size: 2GB

Current behavior
Promethus operator pod shows below error and fails to start Promethus pods:
level=info ts=2024-07-01T15:26:40.289390758Z caller=operator.go:1163 component=prometheusoperator msg="sync prometheus" key=pelorus-operator/prometheus-pelorus
level=error ts=2024-07-01T15:26:40.322958155Z caller=klog.go:116 component=k8s_client_runtime func=ErrorDepth msg="Sync \"pelorus-operator/prometheus-pelorus\" failed: creating config failed: generating config failed: unmarshalling additional scrape configs failed: yaml: line 7: did not find expected '-' indicator"

Expected behavior
Promethus server starts up without errors
Code of Conduct

[X] I agree to follow Pelorus's Code of Conduct

@achdmbp I've been able to reproduce your issue. gonna dig into it more now.

@achdmbp could you try changing your config to (all I did was change the single and double quotes on the metrics_filter):
kind: Pelorus
apiVersion: charts.pelorus.dora-metrics.io/v1alpha1
metadata:
  name: pelorus-devspaces
spec:
  federate_openshift_monitoring:
    enabled: true
    metrics_filter:
      # pull devspaces metrics we're interested in
      - '{namespace=~".*-devspaces",pod=~"workspace.+"}'
  exporters:
    instances: []
  prometheus_storage: true
  prometheus_storage_pvc_capacity: 3Gi
  prometheus_storage_pvc_storageclass: gp2
  prometheus_retention_size: 2GB


The development config directory is read when running hugo

Problem exists in v0.112.0, v0.112.1, v0.112.2.
config/
├── _default/
│   └── config.toml
└── development/
    └── module.toml  <-- BUG: this is read when running `hugo`

Minimal example:
git clone --single-branch -b hugo-forum-topic-44506 https://github.com/jmooring/hugo-testing hugo-forum-topic-44506
cd hugo-forum-topic-44506
hugo

Error: failed to load modules: module "foo" not found

Then run:
hugo -e production

No problems.
Reference: https://discourse.gohugo.io/t/44506/3

This could expose sensitive/internal content.
config/development/module.toml
[[mounts]]
source = 'content'
target = 'content'

[[mounts]]
source = 'hidden'
target = 'content'

I can replicate this on v0.112.2 as well but my development config is called testing:
❯ tree config/
config/
├── testing
│   └── config.yaml <-- this file is being loaded
└── development
    └── config.yaml

3 directories, 2 files

In config/testing/config.yaml I set the baseurl to be something different and its being updated:
❯ hugo config | egrep '(envi|baseurl)'
baseurl = 'https://testground.example.com'
environment = 'production'

vs
❯ hugo config -e production | egrep '(envi|baseurl)'
baseurl = 'https://example.com'
environment = 'production'

I'm running OSX locally but discovered the bug in Netlify's build env.


Enable alerts definitions using web sessions

Aggregated (active/expired/rejected) web sessions

https://issues.jboss.org/browse/HAWKULAR-1255

@miq-bot add-label  providers/middleware

@lucasponce  Can you please take a look?

@josejulio It looks good to me.
I have one doubt if web sessions metrics should have two conditions or just a simple threshold is enough.
I personally like to have a single condition (choosing the operator), to define a condition when expired matches the operator instead to chain two.
i.e.
An alert when web sessions > 40 or web session < 10 is confusing to me, as you would expect two different alerts on this case (I think).
But, I guess this should be confirmed by @abonas or John Doyle.
If there is not a clear requeriment, I would go for a single condition, it's easier and the same semantic can be implemented with two alerts (and I think as a user it will be more meaningful).

Also, alerting offers more possibilities like range or rates conditions,
http://www.hawkular.org/docs/rest/rest-alerts-v1.html#Condition
But for a first introduction in MiQ of this feature I think a threshold can be enough.

@lucasponce updated the PR with your suggestions.
Also it nows depends on:
https://github.com/ManageIQ/manageiq-ui-classic/pull/2309 and https://github.com/ManageIQ/manageiq-providers-hawkular/pull/68

@aljesusg please review

LGFM @josejulio

Thanks, @chessbyte, can you review? thanks!

@abonas will review after your 👍

@miq-bot add_label alerts


Discussion: Given Akka Cluster Bootstrap, do we need ConstructR any longer

Have you seen Akka Cluster Bootstrap (part of Akka Management): https://github.com/akka/akka-management?
This allows for bootstrapping clusters without central coordination. Pretty cool IMHO. I have tried it with docker-compose: https://github.com/hseeberger/trial-cluster-bootstrap. Works fine.
Now I wonder whether we need ConstructR any longer. What do you think?

I will have to disagree on ConstructR being rendered obsolete in the presence of Akka Cluster Bootstrap. I firmly believe it remains relevant for quite a few users for the time being, and perhaps even in the long run. The reason for this is quite straightforward: most software running today has been created way before Akka Cluster Bootstrap (and Akka itself for that matter); hence, as far as service discovery is concerned, existing systems probably already have adopted some specific approaches which do not stack up with (yet) another one. That is especially the case if a software stack contains components that kind of "impose" the way to go (e.g. Kafka and Zookeeper), and once a choice has been made, there are some very legitimate reasons to stick to it:

The accumulated experience on a technical and operational level of an existing technology may outweigh the advantages of a new one
The operational cost of introducing extra components into an already large stack may be prohibiting.
The advantages of the new technology may be context specific (in this case more Kubernetes friendly/oriented), and thus may not necessarily apply in most cases (how many legacy systems can one realistically expect to be migrated into Kubernetes within the next couple of years?)

Given the above, I would say that one of the main advantages of ConstructR is the freedom it provides of choosing the coordination service backend, and I find that to be a "selling point" that should keep it in the game.

I would say that one of the main advantages of ConstructR is the freedom it provides of choosing the coordination service backend

Which the bootstrap also allows (will allow), since the "discovery" part is just a trait where you can plug-in whatever discovery mechanism you like. If you have some external system handling these things, and want to remain using it, this will be possible.
This simply was not implemented yet, as the current impl was put together in 4 days and we wanted to present it quickly to the world ;-)
I don't think it currently renders ConstructR obsolete, but it eventually could if we added discovery using all the mechanisms that @hseeberger and contributors here have implemented. We're open to that and could happily collaborate on that I think :-) So rather than "obsolete", I'd call it a state "things can start to converge", since the commercial conductr has gone away, we're free to make nice useful things in this space.

For us, it would be essential to maintain support for Consul as coordinator. We would be more than willing to collaborate to make it possible in the context of akka-management taking advantage of the experience gained in the development of constructr-consul.

Cool, thanks for chiming in! I'll be cleaning up things this week there and lay out a plan how to contribute alternative discovery impls then. Thanks in advance! I'll ping here once more info can be shared.

Great! Looking forward to converge ;-)

@juanjovazquez BTW, with the current approach/implementation there is no central coordination in Akka Cluster Bootstrap.

@hseeberger Thanks for bringing that up. I imagine that we'll be able to find the way to adapt the k8 version to Consul. I hope at least... ;-)

k8 was only used as an example. I have another example running in Docker. The only thing that is needed/used in the current version of Akka Cluster Bootstrap is DNS. It serves the purpose of etcd, Consul, etc. in ConstructR, but without the coordination aspects (no locks, just registration of node addresses).
So if you do not want to use DNS, you could easily implement a Consul "backend" – easily because your current backend already should do more than necessary for Akka Cluster Bootstrap.

Yup, it's as Heiko explained. Putting the existing impls to use for Bootstrap should be rather simple.
Really looking forward to this. I'll work on it more tomorrow

Got it. It sounds great!. Please, ask for help if you need it.

Also happy to contribute a zookeeper backend implementation to Akka Cluster Bootstrap. Could do that in the week before Christmas.

@ktoso the suggestion to incorporate multiple strategies into the bootstrap extension does seem very promising indeed. However, after reviewing the source code of akka bootstrap, I can see one major limitation, which is that single node clusters are not supported. In fact, there is a comment related to this issue in ClusterBootstrapSettings.scala:
val requiredContactPointsNr: Int = discoveryConfig.getInt("required-contact-point-nr")
    require(requiredContactPointsNr >= 2,
      "Number of contact points must be greater than 1. " +
      "For 'single node clusters' simply avoid using the seed bootstraping process, and issue a self-join manually.")

I am not sure whether this limitation (i.e. avoiding using a single contact point to retrieve seed nodes) is some hard rule in the context of the chosen algorithm, but - especially if it is - it's a limitation that it is very difficult for consumers to adapt to. The whole point of a discovery service is to eliminate the need of knowing a cluster's structure prior to run-time. As an example, we have a very common case where a single "special" node may have to form a cluster on its own, and start operating as a cluster node in a seamless matter (i.e. unaware of the fact that it is alone in the cluster) while other nodes may jump in much later (or not at all). The node must start working immediately despite of the absence of the rest, and it is not acceptable if it cannot bootstrap until a second node tries to join as well. However, for the same cluster, it may be the case that this "special" node may not be required, thus the rest of the nodes will form the cluster on their own. The discovery service allows us to uniformly address these scenarios.
To your knowledge, is the single node cluster issue something that can be worked around by the bootstrap module, or having more that one contact points is it a hard requirement?

I bet this is not a general limitation, but just the current state of affairs.

That's a lot of text and serious wording for a small default requirement change @nick-nachos ;-)
It allows 1 node now in 0.7, while it's a terrible idea, it's allowed yeah.
All, please see https://github.com/akka/akka-management as 0.7 and the modularisation has been merged. Please do contribute modules to akka-discovery if you'd like to do so! The interface currently is very naive, and may change, but let's get this started like this. See the akka-discovery-dns for a simple example.

@hseeberger have you deleted docker compose example on a purpose ?
may you restore that repo or fix link in a first post ?

Sorry, it's gone.

Warning: DNS SRV is not yet supported by akka-management Service Discovery.

Hi everyone, small reminder that we're looking for contributions for akka-discovery https://github.com/akka/akka-management/tree/master/discovery/src implementations for other tools :)
By now we implemented:

AWS APIs
DNS (indeed SRV is missing, but we hope to solve that soon)
Kubernetes APIs and
Marathon APIs

Would be cool to port the integrations that constructr had with other tools to Akka Management. I have not heard any immediate need or requests for it, but would be great nevertheless -- if someone would be interested in a cool side project :)

Thanks for the reminder. I still want to port the zookeeper implementation to Akka Discovery. Currently, I am very busy but I’ll try to sneak it in.

Would be super lovely :)

We're very interested in porting the Consul implementation to Akka Discovery too. I'll try to find some spare time for it. Thanks for the heads up!


Add plugin: Bridge admin panel

Summary
I made a admin panel for hexo called Bridge.
Would like to add the plugin to the official hexo website.
Check List
Please read and check followings before submitting a PR.

[x] I want to publish my plugin on Hexo official website.

[x] I have read the plugin publishing doc.
[x] name is unique.
[x] link URL is correct.

ping @SukkaW @YoshinoriN @stevenjoezhang, is everything ok with this pr?
Do I need to make more changes before it gets approved & merged?

Can you remove this blank line?

@jiangtj done, I removed the empty line and resolved all of the conflicts.


sap.ui.layout.HorizontalLayout allowWrapping not working in sap.ui.layout.Splitter

OpenUI5 version:
1.52.9
Browser/version (+device/version):
Chrome 66.0.3359
Any other tested browsers/devices(OK/FAIL):
Internet Explorer 11 FAIL
URL (minimal example if possible):
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:

Create UI5 App
Add sap.ui.layout.Splitter
Add sap.ui.layout.HorizontalLayout with enough children to fill the width of the screen more than once and allowWrapping="true"
(or: add a sap.ui.comp.smartfilterbar.SmartFilterbar with several Filter)

What is the expected result?
The controls inside the HorizontalLayout are wrapped properly if the length of those controls exceeds the width of the HorizontalLayout. (Screenshot 1)
What happens instead?
The controls are not wrapped and the width of the HorizontalLayout div is equal to the combined width of the children inside the HorizontalLayout.
Any other information? (attach screenshot if possible)
Expected Result

Unexptected Result

XML View for testing purpose:
MainView.txt

The question is forwarded to my colleagues with #1870253920
Updates will be posted here as well


Set-up GitHub Actions

I would like to test GitHub Actions as Travis CI is very slow and flaky last time

This looks cool! Looks like we still have some failing tests?

The tests were failing on Windows - we didn't run them on the Travis :) I will comment Windows for now as an error occurs on the multi-process mode and we want to drop support for this anyway.

@piotr-oles - did you want to swap the badges in the readme as well? The Travis badge is still there and there isn't a badge in place for the GitHub actions build.

Good catch - I will change badges :)

:tada: This PR is included in version 4.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix of ShellCheck. Doc update. Int testing updates. Added ShellCheck job.

fixed ShellCheck concerns
added ShellCheck job as part of CI flow
updated Actions workflow to fix wrong names of steps
updated Readme file to add default values for few inputs
in workflow explicitly set permissions as they are needed for some Actions

⚠ With current configuration all concerns from ShellCheck will fail build on errors.
In the PR's code https://github.com/hadolint/hadolint-action/pull/74/files#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fR35
Link to the readme of GitHub action https://github.com/reviewdog/action-shellcheck#fail_on_error

thanks!


WIP: bldy: have bldy build more things

doesn't work yet, but it will
Signed-off-by: Ronald G. Minnich<EMAIL_ADDRESS>

So this does it. The result is mostly a mirror in build_out of the tree we need to boot.
But it has to be moved.
Note that acpi is not building, as is acpi/irq.

API IS NOW building ... sorry


⚠ Avatar API Endpoint has degraded performance

In 357110d, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 4817 ms

Resolved: Avatar API Endpoint performance has improved in 97daf29 after 6 minutes.


Remove nimbus build system

It seems like nimble >= 0.14.2 is working just fine for now, we can remove the nimbus build system dependencies and flow for now, to avoid duplication.

Finished in https://github.com/codex-storage/nim-codex-dht/pull/73


Fixed error sending more than 256 fragments  [7404]

The async thread was not awaken to send the next unsent fragments after sending the first 256. This PR fixes this.
Refactored as a port of #973

Build status:

Linux
Mac
Windows


[Feature] : Add Help page

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
@Counselllor
we can add help page
when user click on help link from footer they will redirect to /help route

and it will look like

please assign it to me, i would like to work on this issue.

@thestarsahil I would like to work on this issue.
Will you please assign it to me


First version of cf app ssh plugin

There's a few jsdoc lint errors, otherwise js LGTM (i've switched PR to merge to deploy-app to make reviewing easier, will flip back to master when deploy-app makes it in)


metal/util/pred_to_prob Squeezing 1d tensor with 1 element to 0d tensor

If Y_h is a 1d tensor with 1 element, and we squeeze that tensor, it becomes a 0d tensor, and fails the check in the subsequent line (56) at assert Y_h.dim() == 1

I'm not sure how to make a pull request because I can't seem to push a new branch to the repo (probably permissions) but I think the fix would be to check that Y_h.dim() > 1 before squeezing, because the two possible outcomes are a 0d tensor (bad) and the same 1d tensor (no effect), so we shouldnt squeeze when Y_h.dim() is 1.


feat: embeddings and image generations endpoints

Ok, I tried to test this PR.
The embeddings are working.
I was not able to test image generation.


Received image not sampled at bottom edge for bottom LEDs

Bug report, debug log and your config file (FULL LOGS ARE MANDATORY)

I created a small website to test the accuracy of my LED layout. Just a black screen with a moving white 5px x 5px rectangle to see if it lines up with the LEDs.
It looks like to set the color of my bottom LEDs the image isn't sampled at the bottom edge but slightly inwards. The bottom LEDs don't "trigger" with the white dot at the edge of the image.
I use an LG TV and Piccap sending a 336x192 image (4x LED width and height)
Logs: https://pastebin.com/4fg4uzcv (don't seem very informative, even though I set Log level to Debug...)
Config: https://pastebin.com/QN4rczx3
Steps to reproduce
No special steps needed, just happens
What is expected?
Since my HW config has the LEDs placed at the very edge, I would expect the image to be sampled at the edges.
Works for all other edges.
Maybe an Off-By-One error in a loop somewhere? Or is this expected?
System

https://pastebin.com/1MnV6Rfx
Let me know if you need anything else!

Hi
I restored your config. Couldn't use your resolution but it doesn't matter here. Well, in fact it may matter because for 192 height we've got area that has height only 2 pixels which is invitation for various border problems like rounding/truncation, but you chose to configure it that way.
My camera offers 640x480 and that was used.
Let's take your first LED from your configuration. As you can see it's located at the bottom.

So we multiply these values by dimension then expected area for 640x480 is:
horizontal(x): [512.512, 519.936>
vertical(y): [475.2, 480>
And what we've got in HyperHDR?

It's OK. If you experience such problems then I suggest it's cause by video source that is providing stream for HyperHDR (bad capturing or extreme cropping/scaling or it's just your reception)

Hey, thanks for the info but I'm not quite sure what you're suggesting. Sorry if I'm being dumb, but where do the "2 px height" come from?
Does this mean that at the edge the size of the samples is just 2x4px? I'm having a bit of a hard time picturing it :p
I think the bottom line is that I should increase the capture resolution?

Yes: it 4x 2pixels
For that bottom single LED
width: 0.8124-0.8008 = 0.0116
height: 1 - 0.99 = 0.01
multiple it by 336x192 for that single LED
which gives 4 (3,8976) x 2 (1,92)
You can increase the source resolution or maybe you can try to increase LED height from that 0.01 in the LED strip configuration in HyperHDR. But mostly the effect really depends on the video input source: if its scaler detects a portion of the box that is approaching the our target LED area (it might just skip some lines instead of averaging the pixels).


feat: more matrix lemmas about 37 : Matrix n n R etc

This extends the lemmas about zero and one in this file to lemmas about ofNat, natCast, and intCast.

bors merge


Reject queries and all of their works

Queries are complex and I haven't used them in my recent work, so this PR considers just what it looks like to throw them away. In particular, this is a chance to play with what optimisations are possible without them.
Resolves #17

I mean, a first win is that the codebase is 600 lines lighter.

Woo hah! Now almost 900 lines down!


[Bug]: px is treated as spaces.

Checklist

[X] I have read the appropriate section in the contributing guidelines
[X] I believe this issue is a problem with polybar itself and not a misconfiguration on my part
[X] I have searched for other open and closed issues that may have already reported this problem
[X] I have checked the known issues page for this problem.
[X] I have followed the debugging guide to narrow down the problem to a minimal config.

Steps to reproduce

polybar -c minimal.ini minimal
observe

Minimal config
[colors]
bg1 = #282c34
bg2 = #2f333d
fg = #979fad

[bar/minimal]
font-0 = JetBrains Mono:size=14;4

; 30 pixels - correct
height = 30px

background = ${colors.bg1}
foreground = ${colors.fg}

; 5 spaces, not pixels - incorrect
module-margin = 5px

modules-left = foo bar baz

[module/foo]
type = custom/text
content = "first label; in the correct place"
content-background = ${colors.bg2}

; 5 spaces, not pixels - incorrect
content-padding = 5px

[module/bar]
type = custom/text
content = "second label; too much offset"
content-background = ${colors.bg2}

; 5 spaces, not pixels - incorrect
content-padding = 5px

[module/baz]
type = custom/text
content = "third label; same issue"
content-background = ${colors.bg2}

; 5 spaces, not pixels - incorrect
content-padding = 5px

Polybar log
notice: Parsing config file: .config/polybar/minimal.ini
notice: Loaded font "JetBrains Mono:size=14" (name=JetBrains Mono, offset=4, file=/usr/share/fonts/jetbrains-mono/JetBrainsMono-Regular.ttf)
notice: Termination signal received, shutting down...

Expected behavior
I expected modules to have 5px of padding and 10px in-between one another.
Actual behavior
modules were 10 spaces away from each other and had 5 spaces of padding.
Window Manager and Version
dwm 6.3
Linux Distribution
Gentoo 5.15.14
Polybar version
polybar 3.5.7

Features: +alsa -curl -i3 -mpd -network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) +composite +xkb +xrm +xcursor

Build type: Gentoo
Compiler: /usr/bin/x86_64-pc-linux-gnu-g++
Compiler flags: -march=native -O2 -pipe -Wall -Wextra -Wpedantic
Linker flags: -Wl,-O1 -Wl,--as-needed

Additional Context / Screenshots
No response

That's a version 3.6 feature, you are still using an older version


Yara cuckoo module not hitting on any report attributes

Sample rule
import "cuckoo"
import "math"
import "pe"

rule testing
{
	condition:
		cuckoo.sync.mutex(/Global\\3a886eb8-fe40-4d0a-b78b-9e0bcb683fb7/)
}

Running from command line using the following command:
yara -x cuckoo=cuckoo/reports/report.json myrulesFile.yar badSample.exe
This same issue applies for all cuckoo module attributes, ie: filesystem.files_accesses(), registry keys, etc. Have tried everything but no hits on any of the Cuckoo report attributes.
Is it a formatting issue with the json I am passing in (json is from the reports/report.json which is given in the analysis.zip file downloaded from GUI)? I have also tried using a variety of regexp formats when writing to rule.

What version is the Cuckoo report? Yara doesn't currently support 1.3 or
2.x +
On Mon, Jun 24, 2019, 6:07 PM Bufu1003<EMAIL_ADDRESS>wrote:

Sample rule
import "cuckoo"
import "math"
import "pe"
rule testing
{
condition:
cuckoo.sync.mutex(/Global\3a886eb8-fe40-4d0a-b78b-9e0bcb683fb7/)
}
Running from command line using the following command:
yara -x cuckoo=cuckoo/reports/report.json myrulesFile.yar badSample.exe
This same issue applies for all cuckoo module attributes, ie:
filesystem.files_accesses(), registry keys, etc. Have tried everything but
no hits on any of the Cuckoo report attributes.
Is it a formatting issue with the json I am passing in (json is from the
reports/report.json which is given in the analysis.zip file downloaded from
GUI)? I have also tried using a variety of regexp formats when writing to
rule.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/VirusTotal/yara/issues/1082?email_source=notifications&email_token=ABGVQIQVKZ5H2YLHFZUBWT3P4FAQ3A5CNFSM4H3CWWTKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G3M2ZRQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGVQIS42PNT52XIKX72JGTP4FAQ3ANCNFSM4H3CWWTA
.

What version is the Cuckoo report? Yara doesn't currently support 1.3 or 2.x +
…
On Mon, Jun 24, 2019, 6:07 PM Bufu1003 @.***> wrote: Sample rule import "cuckoo" import "math" import "pe" rule testing { condition: cuckoo.sync.mutex(/Global\3a886eb8-fe40-4d0a-b78b-9e0bcb683fb7/) } Running from command line using the following command: yara -x cuckoo=cuckoo/reports/report.json myrulesFile.yar badSample.exe This same issue applies for all cuckoo module attributes, ie: filesystem.files_accesses(), registry keys, etc. Have tried everything but no hits on any of the Cuckoo report attributes. Is it a formatting issue with the json I am passing in (json is from the reports/report.json which is given in the analysis.zip file downloaded from GUI)? I have also tried using a variety of regexp formats when writing to rule. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1082?email_source=notifications&email_token=ABGVQIQVKZ5H2YLHFZUBWT3P4FAQ3A5CNFSM4H3CWWTKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G3M2ZRQ>, or mute the thread https://github.com/notifications/unsubscribe-auth/ABGVQIS42PNT52XIKX72JGTP4FAQ3ANCNFSM4H3CWWTA .

Cuckoo version 2.0.6. Any idea if there is a way to circumvent this issue? Possibly by modifying source code in Yara Cuckoo module, specifically where it pulls it's file info, regkey info, mutex info from?
Also any idea if the Yara rules using Cuckoo module will work in VTI? Guessing it depends on version of Cuckoo VT is using

I have a PR open if you want to grab that which supports 2.0.6 I just
haven't added backwards compatible code so it's not merged yet.
On Mon, Jun 24, 2019, 9:39 PM Bufu1003<EMAIL_ADDRESS>wrote:

What version is the Cuckoo report? Yara doesn't currently support 1.3 or
2.x +
… <#m_6230808447622098027_>
On Mon, Jun 24, 2019, 6:07 PM Bufu1003 @.***> wrote: Sample rule import
"cuckoo" import "math" import "pe" rule testing { condition:
cuckoo.sync.mutex(/Global\3a886eb8-fe40-4d0a-b78b-9e0bcb683fb7/) } Running
from command line using the following command: yara -x
cuckoo=cuckoo/reports/report.json myrulesFile.yar badSample.exe This same
issue applies for all cuckoo module attributes, ie:
filesystem.files_accesses(), registry keys, etc. Have tried everything but
no hits on any of the Cuckoo report attributes. Is it a formatting issue
with the json I am passing in (json is from the reports/report.json which
is given in the analysis.zip file downloaded from GUI)? I have also tried
using a variety of regexp formats when writing to rule. — You are receiving
this because you are subscribed to this thread. Reply to this email
directly, view it on GitHub <#1082
https://github.com/VirusTotal/yara/issues/1082?email_source=notifications&email_token=ABGVQIQVKZ5H2YLHFZUBWT3P4FAQ3A5CNFSM4H3CWWTKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G3M2ZRQ>,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGVQIS42PNT52XIKX72JGTP4FAQ3ANCNFSM4H3CWWTA
.
Cuckoo version 2.0.6. Any idea if there is a way to circumvent this issue?
Possibly by modifying source code in Yara Cuckoo module, specifically where
it pulls it's file info, regkey info, mutex info from?
Also any idea if the Yara rules using Cuckoo module will work in VTI?
Guessing it depends on version of Cuckoo VT is using
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/VirusTotal/yara/issues/1082?email_source=notifications&email_token=ABGVQIRJNUM6HSEUWIDYUQ3P4FZOJA5CNFSM4H3CWWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYOWIIQ#issuecomment-505242658,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGVQIU4NAJD5MJCZDMY4CTP4FZOJANCNFSM4H3CWWTA
.

Much appreciated, definitely what’s needed. Also I see what’s on the PR thread re backwards compatibility requirements, not sure how far along you are in meeting them but I’d be up to help out if need be. Definitely extremely useful for VTI hunting

I really haven't done much with it yet to be honest I wouldn't say no to
help. I'm basically working on the open source version of vti with Yara
rule management and cuckoo reports with the web UI.
On Mon, Jun 24, 2019, 10:42 PM Bufu1003<EMAIL_ADDRESS>wrote:

Much appreciated, definitely what’s needed. Also I see what’s on the PR
thread re backwards compatibility requirements, not sure how far along you
are in meeting them but I’d be up to help out if need be. Definitely
extremely useful for VTI hunting
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/VirusTotal/yara/issues/1082?email_source=notifications&email_token=ABGVQIR7SWJ4ZGFCLZYKCQTP4GAZDA5CNFSM4H3CWWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYOZU7Q#issuecomment-505256574,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGVQISNIDX7I4DEFTXQX6DP4GAZDANCNFSM4H3CWWTA
.

I really haven't done much with it yet to be honest I wouldn't say no to help. I'm basically working on the open source version of vti with Yara rule management and cuckoo reports with the web UI.
…
On Mon, Jun 24, 2019, 10:42 PM Bufu1003 @.***> wrote: Much appreciated, definitely what’s needed. Also I see what’s on the PR thread re backwards compatibility requirements, not sure how far along you are in meeting them but I’d be up to help out if need be. Definitely extremely useful for VTI hunting — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1082?email_source=notifications&email_token=ABGVQIR7SWJ4ZGFCLZYKCQTP4GAZDA5CNFSM4H3CWWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYOZU7Q#issuecomment-505256574>, or mute the thread https://github.com/notifications/unsubscribe-auth/ABGVQISNIDX7I4DEFTXQX6DP4GAZDANCNFSM4H3CWWTA .

Using the same ES dashboards from the video presentation on threat actor tracking in VTI? Definitely thinking of setting one of those up for our VTI. Re Cuckoo, I'll see if I can work with the fork so that it has backwards compatibility. Issue is, until they merge it, either the rules won't hit on 2.x + behavioral reports, or they won't hit on anything else.

i had the same problem as you fixed it.


kube-aws: error messages are not very actionable

#hackday
Error messages when things fail are not very actionable:
$ kube-aws up
Initialized TLS infrastructure
Wrote kubeconfig to /home/eric/p/#hackday/clusters/kubernetes/kubeconfig
Waiting for cluster creation...
Failed creating cluster: The following resource(s) failed to create: [InstanceController, LaunchConfigurationWorker].
$ kube-aws up
Failed initializing TLS infrastructure: open /home/eric/p/#hackday/clusters/kubernetes/ca-key.pem: permission denied
$ rm -rf clusters
$ kube-aws up
Initialized TLS infrastructure
Wrote kubeconfig to /home/eric/p/#hackday/clusters/kubernetes/kubeconfig
Waiting for cluster creation...
Failed creating cluster: AlreadyExistsException: Stack [kubernetes] already exists
	status code: 400, request id: ed276ada-a041-11e5-aa76-cdc607b29f17

In #199 suggestion was to redirect to aws web console because it has more information about failures. In this case "stack already exists" is probably all we would get, but there are definitely other errors where there is additional information we could likely grab from the api (e.g. "failed because over VPC limit").

kube-aws tool has been updated pretty significantly (debug output as well). Please re-open if this is still an area for improvement.


No mechanism for feeding back information during slow builds

Initial build times for an image can be somewhat slow while Nixery retrieves the required derivations from the Nix cache under-the-hood.
Due to how the Docker Registry API works, there is no way to provide feedback to the user during this period - hence the UX (in interactive mode) is currently that "nothing is happening" for a while after the Unable to find image-message is printed.
Ideally we would figure out some way to feed back information to users in the meantime.

I believe there is nothing that can be done with this issue other than work towards speeding up builds. Closing.


[WIP] Move PullOutPythonUDFInJoinCondition rule into 'Extract Python UDFs'

What changes were proposed in this pull request?
This PR targets to move PullOutPythonUDFInJoinCondition to 'Extract Python UDFs' together with other Python UDF related rules.
I will file a JIRA later. I would like to run the tests first.
How was this patch tested?
Existing tests should cover.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13735/
Test PASSed.

Test build #108648 has started for PR 25358 at commit b3c6b1e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13737/
Test PASSed.

Test build #108651 has started for PR 25358 at commit 29c6dc0.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13738/
Test PASSed.

Test build #108652 has started for PR 25358 at commit 7408b3a.

Test build #108648 has finished for PR 25358 at commit b3c6b1e.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108648/
Test FAILed.

Test build #108651 has finished for PR 25358 at commit 29c6dc0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108651/
Test PASSed.

Test build #108652 has finished for PR 25358 at commit 7408b3a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108652/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13751/
Test PASSed.

Test build #108666 has started for PR 25358 at commit 4bc07bb.

Test build #108673 has started for PR 25358 at commit e6d22c8.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13759/
Test PASSed.

Test build #108666 has finished for PR 25358 at commit 4bc07bb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108666/
Test PASSed.

Test build #108673 has finished for PR 25358 at commit e6d22c8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108673/
Test PASSed.

Merged build finished. Test PASSed.

LGTM
Merged to master.


Fix white on white text

Fixes #225 and #227
This also fixes the design view of authorize client (http://localhost:5000/design/authorize when running locally)
Ready for review @heroku/api

:+1:

Thanks!


how to change navbar with clear color

how to change navbar with clear color
and set navigationItem tintcolor to white

To confirm, you want the background of the NavigationBar to be clear and the buttons to be white? If so, then you would need to set the background of the NavigationBar to clear, and that can be done through an extension for global settings and locally for isolated view controllers. For example:
class AppNavigationController: NavigationController {
    open override func prepare() {
        super.prepare()

        guard let v = navigationBar as? NavigationBar else {
            return
        }

        v.backgroundColor = .clear
        v.depthPreset = .none
    }
}

If you want to do it for a specific view controller, then you will need to use the helper navigationController? property in that view controller and set the background like so:
(navigationController?.navigationBar as NavigationBar)?.backgroundColor = .clear

To set the color of the buttons, you would need to do that for each button at the current moment. You can do that when you create the button, like so:
let button = IconButton(image: Icon.add, tintColor: .white)

navigationItem.leftViews = [button]

If you need further help, please use the Material Gitter channel. Thank you!


Allow setting field descriptions via a translation file

In order to simplify updating field descriptions I added a few lines of code to the DescriptionHandler class. Default behavior is not changed, so if a DataRow has $details->description set, that description will be displayed. However, if a translation voyager.help.{$dataType->name}.{$row->field} exists, that will be used.
So suppose we have a DataType posts which has one DataRow title. The DescriptionHandler as it is now will just check whether DataRow->options->description exists. If it doesn't exist, the description isn't visible. The updated version does an additional check (only if options->description isn't set) - it looks for the translation voyager.help.posts.title and uses that instead, if it exists.

This would also need some description (get it?) in the Readme.

This will be available in Voyager 2 ootb.


Add support for fetching multiple audiobooks

Add support for fetching multiple audiobooks

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

Project coverage is 100.00%. Comparing base (3fcee45) to head (5895bcd).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #357   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          601       652   +51
  Branches        28        28
=========================================
+ Hits           601       652   +51

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