fix: UDP comms for AWS

Use separate announce TCP / UDP announce hostnames
Use public IP on AWS nodes to enable DiscV5 Peer Discovery

Docs Preview
Hey there! 👋 You can check your preview at https://665dc4396690d56123cfb81a--aztec-docs-dev.netlify.app

Benchmark results
No metrics with a significant change found.

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

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,780 (+1%)
1,572 (+1%)
702
775 (+5%)
786 (+1%)

proof_construction_time_sha256_30_ms
12,046 (+2%)
3,202 (+2%)
1,416 (+1%)
1,446 (+1%)
1,479 (+1%)

proof_construction_time_sha256_100_ms
45,572 (+2%)
12,254 (+2%)
5,674 (+1%)
5,610
5,495 (+1%)

proof_construction_time_poseidon_hash_ms
79.0 (+1%)
34.0
35.0 (+3%)
57.0 (-2%)
87.0

proof_construction_time_poseidon_hash_30_ms
1,540 (+1%)
424 (+1%)
202
225 (+1%)
265 (-2%)

proof_construction_time_poseidon_hash_100_ms
5,801 (+1%)
1,581 (+1%)
723
798 (+5%)
792 (+1%)

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

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412
1,412

l1_rollup_calldata_gas
9,440
9,464
9,464

l1_rollup_execution_gas
607,976
608,000
608,000

l2_block_processing_time_in_ms
1,270 (-1%)
4,704 (-3%)
9,315 (-3%)

l2_block_building_time_in_ms
43,260 (-3%)
171,349 (-3%)
343,258 (-2%)

l2_block_rollup_simulation_time_in_ms
43,071 (-3%)
170,637 (-2%)
341,620 (-2%)

l2_block_public_tx_process_time_in_ms
39,916 (-3%)
167,414 (-2%)
338,287 (-2%)

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

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
9,457 (-1%)
14,524 (-1%)

node_database_size_in_bytes
14,508,112
21,344,336

pxe_database_size_in_bytes
18,071
29,868

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

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.3 (-1%)
17.2
N/A
N/A
N/A
N/A
N/A
N/A
N/A

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

batch_insert_into_append_only_tree_16_depth_hash_ms
0.600 (-1%)
0.518
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.2 (-1%)
75.6 (-3%)
242 (-2%)
473 (-1%)
906 (-3%)
1,806 (-2%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.491 (-1%)
0.466 (-2%)
0.440 (-1%)
0.442 (-1%)
0.429 (-3%)
0.432 (-2%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
57.7 (-1%)
111 (-1%)
348 (-2%)
698 (-1%)
1,356 (-3%)
2,694 (-2%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
106
208
692
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.499 (-1%)
0.497 (-1%)
0.473 (-2%)
0.479 (-1%)
0.469 (-3%)
0.467 (-2%)
N/A

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

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
107

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

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
84,053
665,267

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


Removed broad exception clause to catch exceptions which may be relevant...

NB: I only briefly acquainted myself with the algorithm.  I'm not entirely sure this doesn't sabotage the nature of the algorithm (since it requires precise timing), but it's a lot easier to debug exceptions than to figure out why a lock isn't being acquired due to a broad catch clause.
For example, a ResponseError indicating the wrong number of arguments is
raised when the Redis server version is too old to handle the nx or px
arguments. This exception information is useful, and the case of acquiring
or not acquiring the lock can be handled by expecting either True or None
from the call to set.

Might be better to just do some logging rather than remove the except. It is greedy for sure. I should also write a more extensive test suite and really understand what errors could be thrown.

I think I'm +1 for catching the exception, logging a message, and then returning false.
Even though it's generally better to catch exceptions, as you increase the number of servers in the cluster, the chance that the Redlock client gets an exception increases by just less than probability_of_exception * n_servers.  (I believe the actual math for this is 1 - scipy.stats.binom.pmf(0, n_servers, probability_of_crash).
Because it seemed like a fun thing to do (and totally overkill! :smile:), I plotted the probabilities of an exception occurring.

labels = 1. / (2**np.arange(2, 10))
z = np.array([1 - scipy.stats.binom.pmf(0, range(7), p) for p in labels])
plot(range(1, 8), z.T)
``

I think it best to catch the exception


Deprecation warning when using the phar file with PHP 5.5

The example build:
https://travis-ci.org/GoogleCloudPlatform/getting-started-php/builds/96800932#L1072
PHP Deprecated:  curl_setopt_array(): The usage of the @filename API for file uploading is deprecated. Please use the CURLFile class instead in phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Curl/CurlHandle.php on line 202
PHP Stack trace:
PHP   1. {main}() /home/travis/bin/coveralls:0
PHP   2. require() /home/travis/bin/coveralls:12
PHP   3. Symfony\Component\Console\Application->run() phar:///home/travis/bin/coveralls/bin/coveralls:21
PHP   4. Symfony\Component\Console\Application->doRun() phar:///home/travis/bin/coveralls/vendor/symfony/console/Symfony/Component/Console/Application.php:106
PHP   5. Symfony\Component\Console\Command\Command->run() phar:///home/travis/bin/coveralls/vendor/symfony/console/Symfony/Component/Console/Application.php:193
PHP   6. Satooshi\Bundle\CoverallsV1Bundle\Command\CoverallsV1JobsCommand->execute() phar:///home/travis/bin/coveralls/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:239
PHP   7. Satooshi\Bundle\CoverallsV1Bundle\Command\CoverallsV1JobsCommand->executeApi() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Command/CoverallsV1JobsCommand.php:114
PHP   8. Satooshi\Bundle\CoverallsV1Bundle\Repository\JobsRepository->persist() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Command/CoverallsV1JobsCommand.php:161
PHP   9. Satooshi\Bundle\CoverallsV1Bundle\Repository\JobsRepository->send() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Repository/JobsRepository.php:68
PHP  10. Satooshi\Bundle\CoverallsV1Bundle\Api\Jobs->send() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Repository/JobsRepository.php:154
PHP  11. Satooshi\Bundle\CoverallsV1Bundle\Api\Jobs->upload() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Api/Jobs.php:137
PHP  12. Guzzle\Http\Message\Request->send() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Api/Jobs.php:157
PHP  13. Guzzle\Http\Client->send() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Message/Request.php:285
PHP  14. Guzzle\Http\Curl\CurlMulti->send() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Client.php:467
PHP  15. Guzzle\Http\Curl\CurlMulti->beforeSend() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Curl/CurlMulti.php:279
PHP  16. Guzzle\Http\Curl\CurlMulti->createCurlHandle() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Curl/CurlMulti.php:343
PHP  17. Guzzle\Http\Curl\CurlHandle::factory() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Curl/CurlMulti.php:359
PHP  18. curl_setopt_array() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Curl/CurlHandle.php:202
Deprecated: curl_setopt_array(): The usage of the @filename API for file uploading is deprecated. Please use the CURLFile class instead in phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Curl/CurlHandle.php on line 202
Call Stack:
    0.0005     323040   1. {main}() /home/travis/bin/coveralls:0
    0.0031     529728   2. require('phar:///home/travis/bin/coveralls/bin/coveralls') /home/travis/bin/coveralls:12
    0.0086    1472752   3. Symfony\Component\Console\Application->run() phar:///home/travis/bin/coveralls/bin/coveralls:21
    0.0111    1823392   4. Symfony\Component\Console\Application->doRun() phar:///home/travis/bin/coveralls/vendor/symfony/console/Symfony/Component/Console/Application.php:106
    0.0113    1824920   5. Symfony\Component\Console\Command\Command->run() phar:///home/travis/bin/coveralls/vendor/symfony/console/Symfony/Component/Console/Application.php:193
    0.0115    1828288   6. Satooshi\Bundle\CoverallsV1Bundle\Command\CoverallsV1JobsCommand->execute() phar:///home/travis/bin/coveralls/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:239
    0.0188    2945248   7. Satooshi\Bundle\CoverallsV1Bundle\Command\CoverallsV1JobsCommand->executeApi() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Command/CoverallsV1JobsCommand.php:114
    0.0207    3273224   8. Satooshi\Bundle\CoverallsV1Bundle\Repository\JobsRepository->persist() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Command/CoverallsV1JobsCommand.php:161
    0.0367    3644304   9. Satooshi\Bundle\CoverallsV1Bundle\Repository\JobsRepository->send() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Repository/JobsRepository.php:68
    0.0368    3644432  10. Satooshi\Bundle\CoverallsV1Bundle\Api\Jobs->send() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Repository/JobsRepository.php:154
    0.0368    3644728  11. Satooshi\Bundle\CoverallsV1Bundle\Api\Jobs->upload() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Api/Jobs.php:137
    0.0446    4619808  12. Guzzle\Http\Message\Request->send() phar:///home/travis/bin/coveralls/src/Satooshi/Bundle/CoverallsV1Bundle/Api/Jobs.php:157
    0.0446    4619952  13. Guzzle\Http\Client->send() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Message/Request.php:285
    0.0464    4971520  14. Guzzle\Http\Curl\CurlMulti->send() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Client.php:467
    0.0464    4971840  15. Guzzle\Http\Curl\CurlMulti->beforeSend() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Curl/CurlMulti.php:279
    0.0464    4972224  16. Guzzle\Http\Curl\CurlMulti->createCurlHandle() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Curl/CurlMulti.php:343
    0.0464    4973304  17. Guzzle\Http\Curl\CurlHandle::factory() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Curl/CurlMulti.php:359
    0.0468    5001120  18. curl_setopt_array() phar:///home/travis/bin/coveralls/vendor/guzzle/guzzle/src/Guzzle/Http/Curl/CurlHandle.php:202

The result was successfully uploaded though.

It only happens with PHP 5.5. Maybe we can just ignore this.

This should not be ignored and should be treated as bug.

@keradus Ok, can you take this?

Not this year for sure.
As I told you on the beginning, for now I could not support by sending PRs.

Assigning to you since you think it's a bug, but not in rush :)

Please do not assign anythink to me. I am using assigning for sth other.

If you use PHPUnit and your CI report will be flooded by deprecation notices then you would say it is great?
It is ridiculous to ignore the bug only for reason it happen only in some circumstances like PHP version

Not ignoring. We're resource-limited, I just want to de-prioritize it. Please feel free to take it if your situation changes ;P

Low priority doesn't mean we should ignore it and imitate that the problem doesn't exists, and that is what you have done by closing it!

+1 for guzzle/guzzle to guzzlehttp/guzzle

So what is status of this ?

move to guzzlehttp/guzzle ?

Closing as Guzzle is updated and thread is suuuuper old


Bump Rails dependency version

Hi!
I've just increased the Rails dependency version to 4.2.1 as we needed it to run on this version and it all seems to be pretty happy on that version too.
Thanks for the great Gem!

Thanks! Merged as c39c50570e9bc36a1707d12b15f9549df6f7f410 & b235804c9015d880e8f83512bb5375f36b63555f, with minor changes. In the future, please avoid changing the pg_audit_log gem version in individual commits, as that should be done only upon releasing a version. A new version will be released either later today or tomorrow.


Add ability to reject signals by type

Is your feature request related to a problem? Please describe.
Sometimes a workflow needs the ability to reject signals that it is not listening to. For example a workflow that was canceled doesn't want to accept signals while it is performing cleanup.
Describe the solution you'd like
Add commands to enable/disable signal types. The signal type which is not enabled will be rejected synchronously.
BTW the same can apply to updates.
Describe alternatives you've considered
An update can be rejected, but it requires workers to run. This feature will generate rejection even if workers are down.

Thank you for your feature request. While Temporal doesn't currently support enabling/disabling signal types, it's a great idea for improving workflow control.
As a workaround, you could consider using a flag in the workflow state to track whether it's in a "cleanup" state, and only process signals when that flag is false. You can set this flag in a signal handler that notifies the workflow it's being canceled. This would give you a basic way to control signal reception.
Let me know if you have any other questions.

Thank you for the feature request. While Temporal doesn't currently have this feature, you can work around it by using the existing update mechanism. For example, you could set up a timer in the workflow that will periodically check if it is canceled. If the workflow is canceled, the timer can reject updates until the cleanup is finished.
We appreciate your feedback and will consider adding the ability to enable/disable signals and updates for future releases.

Thank you for your feature request! It's great to hear that you're thinking about ways to make Temporal workflows more efficient and flexible.
Currently, there's no built-in functionality to enable/disable specific signal types within a workflow. However, you can achieve similar behavior by utilizing the workflow's internal state and conditional logic.
Here's a potential workaround:

Maintain a state variable: Within your workflow, you can introduce a flag or a set of flags to track which signals are currently "enabled" or "disabled."
Conditional handling: In your signal handlers, check the state of these flags. If a signal is "disabled," you can either ignore it or handle it in a specific way that suits your cleanup scenario.

This approach provides the ability to control signal reception based on the workflow's state. While not a direct implementation of enabling/disabling signals, it allows you to achieve a similar outcome through workflow logic.
Let me know if you have any further questions or need help with specific code examples.


[BUG] Error 2502 when adding WindowsNodeFeature

Describe the bug
Error 2502 when modifying K8s installation to add WindowsNodeFeature.
To Reproduce
Execute setup instructions for K8s as written until the step where you re-run the MSI.
msiexec.exe /i AksEdge-K8s-0.7.22335.1024.msi ADDLOCAL=CoreFeature,WindowsNodeFeature
Screenshots

Additional context
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.22621.0 Microsoft Windows NT 10.0.22621.0

Disregard. I ran out of disk space.


2 New articles, minor changes to create ticket.

2 new articles created, reports and alerts.

Closing request, will re-open with additional changes.


Slug cannot save with Unicode

I have use slug for saving article with Unicode character. But it cannot save my title. It replace by -1, or -2 number. Please help.

Sorry for the delay.  This would be related to the underlying Cocur\Slugify class not knowing how to translate the unicode character, I suspect.  Can you paste the particular string you are having trouble slugging (or a base64-encoded version, if Gitlab doesn't like you pasting it)?


Loading: showing with property value is false

Hi!
I have sat the property loading to false but loading over lay still showing.

The reason of this issue is because i turned off the pagination and not set pageSize value that fit all the rows data from a server. Now after enabling pagination or set pageSize to proper value the issue gone.

are you including the stylesheet?

No, adding it solve my issue.

Yeah. Initially @tannerlinsley talked about moving the styles to scss and inline them into the component not sure where he stands on that work.
Sent from my iPhone
On Dec 19, 2016, at 2:23 PM, mhd999 <notifications<EMAIL_ADDRESS>wrote:
No, adding it solve my issue.

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/tannerlinsley/react-table/issues/20#issuecomment-268082507, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AC2mGNQb-bdkKwuYxva6Y_XqieDBvsWbks5rJvXngaJpZM4LObgg.

Still contemplating how to handle the styles.  Closing this particular issue for now.


fix syntax error for edge id with comma

close https://github.com/vesoft-inc/nebula-exchange/issues/92

please post the related bug issue @dbacyj @xiajingchun

Codecov Report

Merging #91 (bdccf64) into master (44a09a7) will increase coverage by 2.78%.
The diff coverage is 22.72%.

:exclamation: Current head bdccf64 differs from pull request most recent head 6649c70. Consider uploading reports for the commit 6649c70 to get more accurate results

@@             Coverage Diff              @@
##             master      #91      +/-   ##
============================================
+ Coverage     54.38%   57.17%   +2.78%
- Complexity       76       81       +5
============================================
  Files            17       17
  Lines          1368     1366       -2
  Branches        259      259
============================================
+ Hits            744      781      +37
+ Misses          493      446      -47
- Partials        131      139       +8

Impacted Files
Coverage Δ

...soft/exchange/common/writer/ServerBaseWriter.scala
26.04% <22.72%> (+26.04%)
:arrow_up:

...ain/scala/com/vesoft/exchange/common/Package.scala
41.66% <0.00%> (+33.33%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

please post the related bug issue @dbacyj @xiajingchun
done 😜


Snippets for bulk get/delete function

Corresponding doc change to enable it: http://cl/282953279

@rsgowman thanks for these!  Certainly we never mind contributions but in the future you can always just ping a DPE to get us to write the snippets.


Terminology MaStR

@stap-m
i am not sure about the terminology i should use for the parameters from MaStR. For now i just translated them like AuflagenAbschaltungSchattenwurf = RequirementsSwitchOffShadowing.

You can find some hints for terminology here.
I am not that familiar with terms of MaStR. Does BNetzA provide definitions/explanations?
Where does this term AuflagenAbschaltungSchattenwurf occur? Is it a table/column name?
And why should it be part of the ontology?
I'd also like to discuss a subontology for mastr-terms e.g. oeo_mastr, like oeo_geo.

Yes they do, in the so-called Schnittstellenkonzept
It's a column name of the Wind Entity. There are some defined attributes/parameters for the different Technologies.
In my master thesis i am working on a method to connect the ontology with Datasets and put them as Import Data in oemof.
That could be an idea but in MaStR are also parameter like EnergyCarrier which is a class in the oeo.

Auflage, Schattenwurf and Abschaltung seem to fit to concepts in the ontology, e.g. they could be a parameter from a modelling point of view.

I am closing this issue now.


Data retention features

We need the ability for application data to automatically align with a bespoke data retention policy. For example, a policy may say something like:

All personally-identifying information (PII) or intellectual property (IP) will be removed from applications that are out of remit and dismissed.
All PII and IP will be removed within 3yrs for any applications that are not approved.
All PII and IP will be removed from all applications after 6yrs, regardless of the outcome.
All non-PII/IP (categories/meta tags, amounts, etc) for all applications will be stored indefinitely for long-term analysis.

To have the app automatically comply, we'd need the ability to flag specific fields that contain PII/IP and then to define the policy conditions. @frjo and @Parbhat, how can we do this rightly and quickly?
cc @saoun @fourthletter

Simplify the rules as much as possible. E.g. delete all PII and IP info as soon as the application is dismissed even if it's allow for x month/years. Scheduling things years ahed is meaningless in my opinion.
We could add PII/IP options to every field but they already have help links etc. Better to create custom PII/IP fields with hard coded help text.

Agree with points by Fredrik. There are two possible scenarios

The PII/IP fields can be uniquely identified: The form fields type required to tag for PII/IP are uniform across all funds. For example, duration and requested amount etc. These fields are present in every fund. So, we can simply fetch these fields in our code for the update. This is the simplest scenario and does not require any change in the admin area. But the number of these fields is very small and our required PII/IP fields may not be covered in it.

The PII/IP fields are created from generic form field blocks: For example, Richtext Field and Text field (multi-line). These fields vary across application forms for funds. We can not fetch these fields using code only as can not be uniquely identified. We need a way to give Staff user an option to mark a form field for PII/IP while creating application forms. From implementation point of view, it seems better to create an abstract PII/IP block. Then create new form field block like Rich text field (PII/IP) from it.
Currently, we have three groups (Required, Custom and Fields) for form fields under Apply > Application forms. We can create a fourth group for PII/IP fields. This will help admin user to distinguish between normal and PII/IP fields.
More information about the possible fields needed for PII/IP will help to choose from the above possible scenarios. But looks like our requirement will probably fall in the second scenario.

Heroku saves database backups for up to one month. This needs to be taken in to account when stating how long we keep data.


[DO NOT MERGE] Remove v1p1beta1 samples

Blocked by #52

[ ] Get OK from TW to remove

TODOs

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

@beccca bump :) Is this still a thing?


Usage in NAV2018CU2

Hello
I want to make use of the functions ConvertValueToBase64 and ConvertValueFromBase64 in this new COD10 Type helper, in order to get rid of dotnet-usage.
How do I do this?
Can I download the COD10.txt from the CAL-open-library, import it into NAV CSIDE and compile the object?
If I then do 'download symbols', can I make a variable of codeunit 10 and call those functions?
Kind Regards,
SirBETE

You can use code from this library in your on-prem installation in the same way as you would do any other base application changes. To use them in AL/new compiler you then need to follow instructions from:  https://docs.microsoft.com/en-us/dynamics-nav/developer/devenv-running-cside-and-al-side-by-side
For further help, please reach out through regular support channels since this GitHub repo and AL repo are focused on supporting the latest pre-release version of the product.

I hope that answered your questions. In case you're having problems or further questions, please reopen this issue :-) Happy side-by-side coding!


I want to get Xs. Is there any code for Gs?

Weights are specified by a set of n segmentation masks S that can be specified manually or generated automatically by a segmentation network Gs using a latent code Xs.  I want to get Xs. Is there any code for Gs?
.

It's a bit more advanced usage, but you can change max_segments to something like 8 or 10 and then change the segment drawing by clicking middle mouse button. If you want to save the latent codes, you can do so via the menu. The automatic segmentation described in the full ECCV paper is not implemented in this UI version, as it's primarily aimed at interactive scenarios.


How about the performance this method(fps) in which computer?

Traceback (most recent call last):
File "C:\Users\chang\Desktop\Crosswalk-Recognition-master\Crosswalk-Recognition-master\crosswalkRec.py", line 309, in
img = cv2.imshow('Processed',processedFrame)
NameError: name 'processedFrame' is not defined
I am getting this error , What should i do?


Switch from flake8 to Ruff

Consider switching to Ruff :smile:

Thanks for the proposal! Looking through the failures, it seems that it caught some real issues in the code, though some of the recommendations seem a bit nitpicky (why are list comprehensions better than map, for example?)

the recommendations seem a bit nitpicky

You're absolutely right.  Even the maintainers don't like all the rules.  They add them by user request.  Definitely, block the codes you don't like.
(I blocked the unnecessary map rule.)

@NeilGirdhar – after a couple weeks, my verdict is: ruff is blazing fast and works great. Thanks so much for suggesting this!

@jakevdp My pleasure, glad it worked out!
(Of course the real credit goes to the Ruff team :) @charliermarsh)

Thanks for tagging @NeilGirdhar! So glad Ruff is working well for you and the team @jakevdp, I'm a big fan of your work :)

Hi @NeilGirdhar, Flax is also using the unused import Ruff rule (F401) currently and may look to add more rules (currently looking at the JAX ruff rules for inspiration). I have a couple questions:

why use the F811 and F821 for just the single files, instead of applying them to all files?
why not apply F401 to all files and add an exclusion (i.e. exclude=[...]) for jax/_src, which would make it less verbose than adding a separate line for each file you want to apply F401 to?

why use the F811 and F821 for just the single files, instead of applying them to all files?

They should ideally not be applied to any files.  I only preserved because this change was intended to convert the flake8 configuration into a Ruff one.  If I had more time, I would eliminate these problems.
In particular, F401 would ideally be eliminated by adding an __all__ to each of these files.  This would solve https://github.com/google/jax/issues/7570.  It would also keep PyRight happy.  If you add RUF022 to the rules and use ruff . --fix, ruff will automatically sort __all__ for you too.

Incidentally, if you're interested in linting, there's quite a bit of low hanging fruit that I noticed.  If you enable every error and run Ruff, you should be able to find other rules that could be usefully enabled, e.g.,

RUF*
PTH*
UP*
RET505
E231
PYI026
D301

It'll be up to the Jax team of course what they value changing and how much churn they want to tolerate, so I didn't want to open that door :smile:.


Update to latest CoffeeNet parent version 0.33.1

New CoffeeNet parent version 0.33.1 was released! Please check https://github.com/coffeenet/coffeenet-starter/blob/master/CHANGELOG.md for more information

Pull Request Test Coverage Report for Build 299

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

Totals

Change from base Build 296:
0.0%

Covered Lines:
220

Relevant Lines:
237

💛  - Coveralls


Compilation Error

I'm getting compilation error
 CC radio/mavlink.c
 radio/mavlink.c:131: error 158: overflow in implicit constant conversion
 include/rules.mk:100: recipe for target 'obj/rfd900a/radio~rfd900a/mavlink.rel' failed
 make[1]: *** [obj/rfd900a/radio~rfd900a/mavlink.rel] Error 1
 make[1]: Leaving directory '/home/voyvoda/Desktop/SiK_Multipoint-master/Firmware'
 Makefile:96: recipe for target 'build~radio~rfd900a' failed
 make: *** [build~radio~rfd900a] Error 2

Are you able to give any more information on your build environment like the version number?
Is the base SiK compiling for you?

Hello, I am usign ubuntu 18.04 and I can properly compile the base Sik firmware.

AES encryption is done at the hardware layer, so the first thing you need to have is a board with the AES encryption.
It has been a long time since I looked at the code that uses AES encryption.
I believe it's not fully operational as it presently stands. The problem was the speed of the encryption and decryption caused delays in receiving / transmitting causing the two modems to loose sync and they hop through the frequencies.
Have a go if you like, but don't expect it to work perfectly out of the box. Prepare to read the code and make improvements.
The setting of the encryption key is done in the parameters.c file, have a dig through this and see if you can see where this is set.
Due to AES not fully working to the level I would like, it had become a undocumented feature waiting for someone to improve the code.
If your willing to put in the time and effort to improving the code you could be the first to get this to work.
Otherwise I would recommend purchasing the ARM version that has a lot more power to beable to do the encryption on the fly.


refactor: feature flag backup configurations

Checklist

[ ] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[ ] PR title is ready for inclusion in changelog

This is to featureflag wrap experimental backup configurations. If you think this is useful, ensure you speak to the Lagoon team before you enable this to find out if it will work for your specific environments, as there is potential for issues with backups if incorrectly configured.

Closing issues
closes #3250

This is experimental because it relies on newer versions of k8up to work properly, which is not fully supported in Lagoon yet. Support is being added while we work on supporting newer versions of k8up, which is why this is feature flagged.


chore: upgrade charts

updated chart jxgh/jx-charter from 0.0.27 to 0.0.28
updated chart jxgh/jx-preview from 0.0.191 to 0.0.192

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign rawlingsj
You can assign the PR to them by writing /assign @rawlingsj in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[BUG] tele ls --runtimes does not show K8s runtimes

Describe the bug
tele ls --runtimes shows the same information as tele ls.
To Reproduce

Expected behavior
tele ls --runtimes
Name            Version                 Created
----            -------                 -------
kubernetes      5.5.16-1                Fri Sep  6 20:39 UTC
kubernetes      5.5.8                   Wed May  8 19:15 UTC
kubernetes      6.0.1                   Mon Jul 22 15:58 UTC
kubernetes      6.0.5                   Wed Sep  4 20:04 UTC

Logs

Environment (please complete the following information):

OS [e.g. Redhat 7.4]:
Gravity [e.g. 5.5.4]: 5.5+
Platform [e.g. Vmware, AWS]:

Additional context

flag is deprecated in 5.5+


Refactor OPUS code

I noticed a small issue with the current OPUS code (both the dummy version and the "real" one) after my last PR had been reviewed, but I thought it would be best to make a new PR for it as it involves a few small changes all over.
Currently, when the response to a command is received from OPUS, we send a "opus.command.response" message. The problem is that information about which command has been executed is not included, which makes it annoying to work with. I decided to use separate messages for each command of the form f"opus.response.{command}, which allows the users of the interface to subscribe to responses from specific commands if desired (or they can subscribe to opus.response to get all of them). In addition, I've turned "status" into a regular command like the others. In a sense it is special, as we have to request a separate URL from OPUS and it behaves slightly differently, but this isn't a distinction the frontend needs to care about.
I also added a test for the OPUS HTML parser and fixed some unrelated stepper motor tests which were giving spurious failures.

I've split up the tests and I think it's cleaner now. Thanks! I also added coverage for a couple of lines I missed.
The lines that codecov was warning about weren't really added by me; I modified a bunch of lines which already weren't covered and didn't add new tests for them. The problem is that this code is GUI-based and currently most of the GUI stuff isn't tested. I've got another branch queued up which adds some tests using pytest-qt so I think it would make sense to wait until then before adding more GUI tests, if you agree?


[storage-file-share] Fix empty continuation token with list methods

Packages impacted by this PR
@azure/storage-file-share
Describe the problem that is addressed by this PR
When the empty string was passed as a continuationToken to the byPage method of any list operation, the constructed url would have an empty marker parameter &marker=&.
This was causing issues with SharedKey authentication since we now share the same credential signing logic as storage-blob and the implementation of getURLQueries in storage-blob ignores query parameters without a value:
https://github.com/Azure/azure-sdk-for-js/blob/b4e1a63cd2499016f91852c7208f0c4c569651d4/sdk/storage/storage-blob/src/utils/utils.common.ts#L371
However, the previous copy of this method in storage-file-share did not:
https://github.com/Azure/azure-sdk-for-js/blob/b4e1a63cd2499016f91852c7208f0c4c569651d4/sdk/storage/storage-file-share/src/utils/utils.common.ts#L306
Notice the missing && lastIndexOfEqual < value.length - 1 in the second implementation.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
While it is possible to change the way storage-blob does this signing to match storage-file-share, given that storage-blob is a far more popular package, there is considerable risk to changing behavior there.
Since existing storage-file-share customers (such as Storage Explorer) may be already passing the empty string today, there is a strong desire to maintain that contract.
Rather than diverge the signing logic around SharedKeyCredential again, I believe the least invasive fix is to have the list methods in storage-file-share ignore the empty string as demonstrated in this PR.

API change check
API changes are not detected in this pull request.

Yes I believe we already doing that for most markers.  I traced the change back to PR #4418 and looks that it is an intentional change https://github.com/Azure/azure-sdk-for-js/pull/4418/commits/e73327fb1e06785538d94b549f786fee6993766b.


ET for list and searching packages

The ET charter is two-fold: find bugs in the listing and searching of packages, and document any differences in behavior between the old gallery and the new gallery.

Filters :
• In the new gallery, "Highest rated" and "Relevance" are gone
• #211 : Hide "sort by" when there is no packages.
• #209 : Packages list "A-Z" currently sorts by Package.Id
Search
• Partial keyword search returns more results in the new gallery. e.g.  "Conform" doesn't return MVVMT4, NTS in old gallery ("Conform" is in description of those packages)
• Search with author names doesn't return results (new and old galleries)
Tags
• #246 - Package List : filter by tag doesn't filter for tags.
Author
• The new gallery shows the owner (instead of author)
• Individual links in new gallery while the old gallery search for all terms.
• Clicking author in the new gallery brings profile page
• #218 - Clicking link (e.g. author) with ampersand gives "Error: Oh no, we broke something"
Pager
• The new gallery shows 20 item while old gallery was 10 by default and changeable.
• Navigation (next/previous) still works when filtering results or not.
• #173 - Reset page when changing package sort order
Profile
• #237 - Packages doesn't appear in "Unlisted Packages" when another version of it is listed.
• #204 - Download count is wrong
Packages list doesn't show unlisted packages
• When you're the owner
• When searching/sorting
• Shows "listed" versions when latest is unlisted
○ Note: this is different than the old gallery where unpublished is by package id, not by version
Misc :
• #211 - Hide "sort by" when there is no packages.
• #215 - Remove whitespace around searchable fields (it returns all results)
Similarly, sometimes tags includes a comma or a semi-colon.
• Reviews are shown only in the old gallery
• In the new gallery the Icon link goes to specific package version, while the package name goes to default page


Add skipWhile, skipUntil, limitWhile, limitUntil to StreamUtils

See pull request  : https://github.com/aol/cyclops/pull/35


BTC2ETH.sol is reverting on exchange function

Function: https://github.com/James-Sangalli/learn-solidity-with-examples/blob/master/Finance/bitcoin-to-ethereum-swap/BTC2ETH.sol#L79

Now uses btcrelay processFunction callback


Add DPG: Book Dash

Automatic addition of a new digital public good submitted through the online form available at https://digitalpublicgoods.net/submission

Hey, @nathanbaleeta @prajectory I had a call with the product owner of this solution recently and they will submit it again through the new web app with updated information. So I think we can close this PR.


fails to render

Describe the bug
ColorPicker throws error on initial render.  Dependency versions were carefully compared to manual dependencies list.
To Reproduce
Render the component <ColorPicker defaultValue="red" onChange={() => {}} />.
Expected behavior
The component renders like in the story book
Console log
Uncaught Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.
    at resolveDispatcher (:9080/[project directory]/node_modules/react/cjs/react.development.js:1465)
    at Object.startsWith [as useRef] (:9080/[project directory]/node_modules/react/cjs/react.development.js:1504)
    at je (:9080/[project directory]/node_modules/src/components/ColorPicker.jsx:36)
    at renderWithHooks (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:14804)
    at mountIndeterminateComponent (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:17483)
    at beginWork (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:18597)
    at HTMLUnknownElement.callCallback (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:189)
    at Object.invokeGuardedCallbackDev (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:238)
    at invokeGuardedCallback (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:293)
    at beginWork$1 (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:23204)

Desktop (please complete the following information):

OS: Ubuntu 20.04
Browser [ chrome ]
Version [Version 86.0.4240.111]

Additional context
Project uses electron, mobx-state-tree, typescript

I really wanted this to work so I made sure nothing else in my project was causing this by making it the only thing react rendered and still the error persisted.

My related dependencies
"material-ui-color": "^0.4.6",
"material-ui-popup-state": "^1.7.0",
"prop-types": "^15.7.2",
"react": "^16.13.1",
"react-dom": "^16.13.1",
"styled-components": "^5.2.1",
 "@material-ui/core": "^4.11.0",

Thanks I check.

Use : <ColorPicker value="red" onChange={() => {}} />
I didn't reproduce this bug...
My sandbox to test:
https://codesandbox.io/s/material-ui-color-picker-qvcg3?file=/src/App.tsx

Use : <ColorPicker value="red" onChange={() => {}} />
I didn't reproduce this bug...
My sandbox to test:
https://codesandbox.io/s/material-ui-color-picker-qvcg3?file=/src/App.tsx

Sorry I missed this, I will take another look
On Mon., Jan. 11, 2021, 11:16 a.m. Mik<EMAIL_ADDRESS>wrote:

Closed #93 https://github.com/mikbry/material-ui-color/issues/93.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mikbry/material-ui-color/issues/93#event-4191614749,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFJOC7L5TARU44Y6RNRSSDSZMP6XANCNFSM4TV66MNA
.

Sorry I missed this, I will take another look
On Mon., Jan. 11, 2021, 11:16 a.m. Mik<EMAIL_ADDRESS>wrote:

Closed #93 https://github.com/mikbry/material-ui-color/issues/93.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mikbry/material-ui-color/issues/93#event-4191614749,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFJOC7L5TARU44Y6RNRSSDSZMP6XANCNFSM4TV66MNA
.


Code for parralel attention

Implementation of #2.
I overwrote the existing classes to highlight the differences with the base architecture but it would obviously require a refactoring to make it prettier and let the option to choose between parallel and sequential attention (I was waiting for the big refactoring to make it compatible).
Notably ; maybe it's not that clean to forward the intermediate_ff as the result of the attention_block and merging it with the SwiGLU block might be better.
Also, after discussions with @ohallstrom (and @iacolippo on discord back then), we do not think it makes sense to implement it with post-norm, hence why I changed the code to pre-norm without adding flags.

we should still leave the option of sequential attention no?

Yes, as I said I was mostly waiting for the refactoring to see how to properly let the user choose: use flags in the classes or create different ones.
Sorry it was not clear, I am editing the original comment.

@NohTow I have a flexible BERT implementation almost ready to go in the flexbert branch. Should PR it later today after I do some more MLM cleanup and get classification working.
For fused parallel attention, you'd need to create a new FlexBertUnpadFusedParallelPreNormLayer, FlexBertUnpadFusedParallelAttention, and FlexBertFusedParallelGLU layers.
Let me know here or on discord if you have any questions.

Thanks, I looked at it!
I'll recreate a branch and add those once we merge the flexbert branch into main.


A few IUCN matching issues

Not super-important, but just to note warnings for 3 taxa when running the IUCNquery.py script on the current tree:
total ott matches ~ 145198 (145201 in table)
remaining unmatched ~ 15446 (not including ~3238 below the species level) entries
Could not find a unique iucn status code for taxon with ott = 4725104. Matches against multiple IUCN names: ['Rondeletia galeottii', 'Arachnothryx galeottii'].
Could not find a unique iucn status code for taxon with ott = 48240. Matches against multiple IUCN names: ['Pseudohydromys musseri', 'Neacomys musseri'].
Could not find a unique iucn status code for taxon with ott = 254488. Matches against multiple IUCN names: ['Xerocrassa cobosi', 'Gasullia cobosi'].
Setting all IUCN summaries for all nodes to 0
...

Quick analysis of OTT 4725104:

OTT lookup: Renistipula galeottii with synonyms Arachnothryx galeottii and Rondeletia galeottii
IUCN has separate entries for Arachnothryx galeottii (CR) and Rondeletia galeottii (VU)

So basically IUCN doesn't treat them as synonyms.


Fixed solution.

What did you fix?

Ah, Thanks!!! I see what I did now

Excellent Contribution. Thank you. I really should go to bed. Coding late at night can have negative consequences. :(


MAX, MIN more than two given numbers

Hello
as per max/min(a,b) i can only get max/min number of given two number.
so my suggestion to find max,min of more than 2 given number.
example max/min(5,9,2,3,2,1) so output is 9 for max and 1 for min

Hi @TonyStark! I'm not actively maintaining this project, but this sould be relatively easy to implement. First, there's currently no support for functions with arbitrary arity, so some special value for  arbitrary arity needs to be added and checked for in the evaluateFunc function. Then, the Min and Max functions in need to be updated to take an arbitrary amount of arguments.


feat(UDP-transport): added a udp transport out of the box

Created a UDP transport to support logging to Splunk and other 3rd party log storages.
Added tests and updated readme.

:tada: This PR is included in version 1.6.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[inky] Add Inky Impression 7.3" support

Inky Impression 7.3" is a larger e-ink display that unlike smaller variants is based on AC073TC1A rather than UC8159.
This PR is effectively a port of pimoroni/inky#158 since the difference is primarily in the reset and update commads.
(draft until I have a chance to properly test)

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 102 lines in your changes missing coverage. Please review.

Project coverage is 45.5%. Comparing base (2cf8fa1) to head (2a24918).

Files with missing lines
Patch %
Lines

inky/impression.go
0.0%
99 Missing :warning:

inky/types.go
0.0%
3 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##            main     #75     +/-   ##
=======================================
- Coverage   46.4%   45.5%   -0.9%
=======================================
  Files         82      82
  Lines      10031    8013   -2018
=======================================
- Hits        4658    3645   -1013
+ Misses      5211    4204   -1007
- Partials     162     164      +2

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

I just saw the PR as it is a draft. Can you fix the linter errors? You'll need to rebase.


chore: test CLA assistant on main DO NOT MERGE

I have read and agree to the CLA

I have read and agree to the CLA


Compile failing when partial is an instance of Handlebars.SafeString

When partial's indent option is used, runtime compilation of string partial is failing for partials produced by Handlebars.SafeString because of split method call.
let lines = result.split('\n');

https://github.com/wycats/handlebars.js/blob/master/lib/handlebars/runtime.js#L52
See jsfiddle demo for details.
I have fixed it in a straight way by explicitly calling result.toString().

Can you add a test to ensure that this does not regress and I'll be glad to
add. spec/regressions.js might be a good place to add this, otherwise
spec/partials.js
On Tue, Jul 7, 2015 at 8:05 PM Andrey Kravtsov<EMAIL_ADDRESS>wrote:

When partial's indent option is used, runtime compilation of string
partial is failing for partials produced by Handlebars.SafeString because
of split method call.
let lines = result.split('\n');
https://github.com/wycats/handlebars.js/blob/2c1d509c6cafea145ece5ff9bc8b5c2ca98f9749/lib/handlebars/runtime.js#L52
See jsfiddle demo http://jsfiddle.net/j1j60b0u/ for details.
I have fixed it in a straight way by implicitly calling result.toString().
You can view, comment on, or merge this pull request online at:
https://github.com/wycats/handlebars.js/pull/1054
Commit Summary

Ensure that partial invoke result is a string before splitting it
for indenting

File Changes

M lib/handlebars/runtime.js
https://github.com/wycats/handlebars.js/pull/1054/files#diff-0 (2)

Patch Links:

https://github.com/wycats/handlebars.js/pull/1054.patch
https://github.com/wycats/handlebars.js/pull/1054.diff

—
Reply to this email directly or view it on GitHub
https://github.com/wycats/handlebars.js/pull/1054.

I'm little bit unsure about exact solution to this problem. Should partial always return a string only?
If so it'll be better to call result.toString() inside invokePartial and not in the any conditions later, e.g. one in invokePartialWrapper.
Could you tell me about partial's main concept? Is it just a part of the template (and in that case it should always return string), or partial in Handlebars is something more than just a piece of template (and maybe it should return objects like SafeString in some cases)?

You raise an interesting point. I was surprised that you were able to cause a safe string return from a partial in the first place. Modifying your example a little bit, http://jsfiddle.net/j1j60b0u/1/, shows that a template with a simple wrapper can return a SafeString as well, which could lead to issues down the road. I think we need to make sure that the return from any template, partial or not, is always a string and have proper tests to ensure that :)

@rd5, I went the route of consistent string return from the API and implemented your test case there. Thanks for the report!

Thank you!


Styled js code blocks in README where missing

just added back ticks with js language identifier were it was missing

@amerikan thanks for the PR! IIRC we have to keep these like this so that it imports well on developers.google.com
@ebidel - do I get it right?

@aslushnikov didn't know, feel free to close is such the case.

Yep, IIRC. Can't do GH style markdown for codeblocks for the import to work :(


At/update user show page

Added Bootstrap list-group component to users/show.erb

@HanuMaIV @aceburgess @Doralyp


[new-resource-request]: adding 1+MG framework

New Resource Request
recommended resource to  add 1+MG framework
Resource Title
1-Plus Million Genomes Framework
Resource URL
https://framework.onemilliongenomes.eu/
Resource Description
The 1+MG Framework is a series of components based on the output of the 1+MG projects that provide guidance on ELSI, data quality, data standards, and technical infrastructure standards and APIs.  According to the 1+MG Framework Editorial Guidelines, the content is approved and maintained by working group leads or their deputies. Requests for changes or additions to the core content are open to all members of the consortium. National Implementations can be contributed by all member states.
Resource Category and Subcategory
Data Management and Stewardship - Guidelines and best practices
Resource Tags
sequencing guidelines, data models, ontologies, technical infrastructure, data governance

PR #41


[Bug] 0.11.10 forces api key replacement due to whitespaces

Describe the bug
After upgrading provider from 0.11.8 to 0.11.10 it want to replace api key due to whitespace changes. Api key role_descriptors are not changed
To Reproduce

Create api key with 0.11.8
Upgrade provider to 0.11.10
Run plan

  # elasticstack_elasticsearch_security_api_key.telegraf must be replaced
-/+ resource "elasticstack_elasticsearch_security_api_key" "telegraf" {
      ~ api_key              = (sensitive value)
      ~ encoded              = (sensitive value)
      ~ expiration_timestamp = 0 -> (known after apply)
      ~ id                   = "25opFie5T1qs3JS9dz9YFA/daCobZIBlhlmOGXYaM3k" -> (known after apply)
      ~ key_id               = "daCobZIBlhlmOGXYaM3k" -> (known after apply)
      ~ metadata             = jsonencode({}) -> (known after apply)
        name                 = "telegraf"
      ~ role_descriptors     = jsonencode( # whitespace changes
            {
                telegraf = {
                    cluster = [
                        "monitor",
                        "cluster:admin/snapshot/status",
                        "cluster:admin/repository/get",
                        "manage_slm",
                    ]
                    indices = [
                        {
                            allow_restricted_indices = true
                            names                    = [
                                "*",
                            ]
                            privileges               = [
                                "monitor",
                                "view_index_metadata",
                            ]
                        },
                    ]
                }
            }
        )
        # (1 unchanged attribute hidden)
    }

Plan: 1 to add, 0 to change, 1 to destroy.

Expected behavior
Whitespaces shouldn't force api key replacement
Debug output
N/A
Screenshots
N/A
Versions (please complete the following information):

OS: macos 15
terraform 1.8.0
provider registry.terraform.io/elastic/elasticstack v0.11.10
elasticsearch 8.14.3 on elastic.co

Additional context
N/A

Ah, this bug sucks. Sorry folks.
For clarity, changes to role_descriptors aren't causing resource replacement here. This resource was migrated from the old Terraform SDK to the newer Plugin Framework in 0.11.10. The SDK stored unset attributes as in state as their default values, specifically expiration:"". The Plugin Framework correctly models this as expiration:null, however this was causing TF to force replacement of the API Key resource, since "" != null
https://github.com/elastic/terraform-provider-elasticstack/pull/875 fixes this behaviour, only requiring replacement if the expiration values actually change (e.g 1d -> 1h).


fix: Raise an api error on graphql errors

The tap (and the sdk) were not reporting any graphql errors (because annoyingly, graphql chooses to ignore good HTTP practice by returning a status 200 even on fatal errors).
This PR adds a minimal level of reporting by checking for errors in the response.
@edgarrmondragon The sdk does not seem to check for graphql errors at all, it simply defers to the REST streams validate_response which is not adapted to it. Is it worth adding something in the sdk in that respect?

@edgarrmondragon The sdk does not seem to check for graphql errors at all, it simply defers to the REST streams validate_response which is not adapted to it. Is it worth adding something in the sdk in that respect?

@laurentS Probably, yes. I wasn't aware of any standard or spec around errors in graphql, but if there is one, it makes sense to use it in the default validate_response implementation for GraphQL streams. I logged https://github.com/meltano/sdk/issues/1421.

@laurentS - Thanks very much for creating this!


Update cmdline

Add both command :

show
update [-vc]

It remains to implement the tests.

Fixes with #43


macOS version

ever think of extending support to macOS for SSH and SFTP? I haven't tried the iOS app, but there aren't really any macOS SSH apps that have both SFTP (GUI) and SSH.

I will port the app to macOS after WWDC19. Apple is releasing something to code iOS apps and with the same code, build them for the Mac. It’s already in macOS 10.14, but privately. https://www.imore.com/marzipan

haha, that's funny. i thought that might be the case. i will keep an eye out. thanks


Work Package wp-gm.csv

I would like to work on this, please!

Manually assigned you (@ramyasaimullapudi). Please use the exact phrase in the documentation in the future. :)

Results of Phase 1
wp-gm-results.csv

I completed this work package.

Results of Phase 1
wp-gm-results.csv

I would like to work on this package.

Results of Phase 2
wp-gm-results.csv

Results for Phase 2:
wp-gm-results.csv


[Chart] add logic for updating/verifying helm repo, support helm install online by url.

Signed-off-by: zhu733756<EMAIL_ADDRESS>
What type of PR is this?
/kind enhancement
What this PR does / why we need it:
Add logic for updating/verifying helm repo, support helm repo install online by url.

make update-helm-repo to refresh the helm repo
make verify-helm-repo to check the checksum of the helm repo

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

Other Note

/cc

/assign @SataQiu

/assign @gnunu

should binary charts/yurtcluster-operator.tgz be a part of commit?

Yeah, we can install through helm install  https://github.com/openyurtio/yurtcluster-operator/.../yurtcluseter-operator.tgz, by a link here.

are files moves necessary?

The script packages the subfolder, it is easy to get the whole checksum.  In addition,  the tgz file mixed the YAML  files, I think a bit not make sense.

should binary charts/yurtcluster-operator.tgz be a part of commit?

Yeah, we can install through helm install https://github.com/openyurtio/yurtcluster-operator/.../yurtcluseter-operator.tgz, by a link here.

Ideally, I think we would only release the tgz package in every release instead of committing it into codebase.
So user can consume it by a link.

should binary charts/yurtcluster-operator.tgz be a part of commit?

Yeah, we can install through helm install https://github.com/openyurtio/yurtcluster-operator/.../yurtcluseter-operator.tgz, by a link here.

Ideally, I think we would only release the tgz package in every release instead of committing it into codebase. So user can consume it by a link.

should binary charts/yurtcluster-operator.tgz be a part of commit?

Yeah, we can install through helm install https://github.com/openyurtio/yurtcluster-operator/.../yurtcluseter-operator.tgz, by a link here.

Ideally, I think we would only release the tgz package in every release instead of committing it into codebase. So user can consume it by a link.

All right.

/close
Please download the helm chart from https://github.com/openyurtio/yurtcluster-operator/releases/download/v0.6.1/yurtcluster-operator-v0.6.1.tgz


Relative import in module

Environment

Operating System: Linux
Node Version:     v18.17.1
Nuxt Version:     3.10.3
CLI Version:      3.10.1
Nitro Version:    2.9.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://github.com/eri-hellowords/exchange
Describe the bug
I created module, add addServerHandler - it works
    addServerHandler({
      route: '/api/exchange',
      handler: resolve('./runtime/server/api/exchange')
    })

then i create file with helper functions, but cant import it
import checkauth from '../utils/checkauth.mjs'

It resolves path relative to PROJECT_HOME/../../ -> /mnt/home/eri/Projects/2024/src/runtime/server/utils/checkauth.mjs
but file in /mnt/home/eri/Projects/2024/b2b/1c_exchange/src/runtime/server/utils/checkauth.mjs
Additional context
No response
Logs
[17:08:37]  ERROR  [worker reload] [worker init] Cannot find module '/mnt/home/eri/Projects/2024/src/runtime/server/utils/checkauth.mjs' imported from /mnt/home/eri/Projects/2024/b2b/1c_exchange/playground/.nuxt/dev/index.mjs

  at __node_internal_captureLargerStackTrace (node:internal/errors:496:5)
  at new NodeError (node:internal/errors:405:5)
  at finalizeResolution (node:internal/modules/esm/resolve:324:11)
  at moduleResolve (node:internal/modules/esm/resolve:943:10)
  at defaultResolve (node:internal/modules/esm/resolve:1129:11)
  at nextResolve (node:internal/modules/esm/loader:163:28)
  at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
  at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
  at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
  at link (node:internal/modules/esm/module_job:76:36)

Would you see if you can reproduce this in pure Nitro (reproduction sandbox), and if so, raise there? 🙏

@danielroe cant reproduce in sandbox. cant run npx nuxi init -t module my-module
[17:12:51]  ERROR  Error: Failed to download https://codeload.github.com/nuxt/starter/tar.gz/refs/heads/module: TypeError: fetch failed

Same on Windows

Operating System: Windows_NT
Node Version:     v20.11.1
Nuxt Version:     3.10.3
CLI Version:      3.10.1
Nitro Version:    2.9.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

same problem on macos

Same problem on MacOS for nitro.  Trying to import Prisma client which has an index.js file in it breaks the build and give the wrong import path.

I have it after updating to 3.14.0
ERROR  [worker reload] [worker init] D:/Projecten/organizer/.nuxt/dev/index.mjs failed
------------------------------
- Operating System: Windows_NT
- Node Version:     v22.11.0
- Nuxt Version:     3.14.0
- CLI Version:      3.15.0
- Nitro Version:    2.10.2
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      default
- Runtime Modules:  normalizedModule(), normalizedModule<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -
------------------------------

Is this the same issue as https://github.com/nuxt/nuxt/issues/18909?
Does this solution work?

Idk, for me it happened when using the resolver from @nuxt/kit inside a nuxt module.
Something like
import { defineNuxtModule, createResolver } from "@nuxt/kit"
const { resolve } = createResolver(import.meta.url)

Replaced with
import { resolve } from "path"
Complete example
modules/sheetjs/index.ts
import { resolve } from "path"
import { defineNuxtModule, createResolver } from "@nuxt/kit"
export default defineNuxtModule({
  meta: {
    name: "@nuxtjs/sheetjs",
    configKey: "sheetjs",
    compatibility: { nuxt: ">=3.0.0" },
  },
  setup(options, nuxt) {
    // const { resolve } = createResolver(import.meta.url)
    // https://nuxt.com/docs/api/advanced/hooks
    nuxt.hook("content:context", (contentContext) => {
      contentContext.transformers.push(resolve("modules/sheetjs/sheetjs.ts"))
    })
  },
})

The annoying part for me was that the error was not giving any good hints, so I basicly had to rebuild the whole application to find the source

Is there any way to make the error more readable?


cannot download playlists

ERROR: Unable to extract title; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
no change after updating

Post the full output of youtube-dl when run with --verbose option.


fix bad link for installation

it looks like the old link no longer works for installation instructions

For code in this repo the changes are promoted automatically, I am seeing that the link is fixed now. Thanks!


health endpoint with serviceId as path parameter

In the current stability test on Kubernetes and Consul clusters, we are using TCP health check from Consul server to registered service IP address and port number. It has a flaw as described below.

A service registers itself to the consul and asks consul to ping the IP and port.
When the service is crashed without a chance to deregister itself.
Kubernetes started another service on the same IP and reused the port number as it is dynamically allocated.
Consul pings the service and it is still alive but it is not the registered service anymore.

We can ask each service to pre-allocate a range of port numbers but it would be very hard to manage or enforce even in the same Kubernetes namespace or Openshift project.
It looks like we cannot use TCP health check in our case although it is the most efficient one.
The TTL based health check is also not ideal as we put a lot of load to the consul servers to update the pass and fail status by calling consul APIs.
The only thing that is left is the HTTP health check and we need to make some changes to uniquely identify the service. I am thinking to update the /health to /health/{serviceId} in the new handler.yml so that Consul won't get status code 200 if the target service is not the same service as registered. What do you think? Thanks

Sounds to me that /health/{serviceId} is the best option.

@stevehu just to be clear on this, we're saying that the health check will implement a check to ensure that the path variable passed in matches its service id right?
Or did you mean that {serviceId} will be a hard coded path in each service for their service id?

It would be a hard-coded path in the handler.yml; however, this will be generated from light-codegen so it should be transparent to the developers.
Here is an example of the handler.yml
https://github.com/networknt/light-example-4j/blob/develop/discovery/api_d/http-health/src/main/resources/config/handler.yml

So now every time they bump up the service id version in their applications they have to make sure they change both..

In most of the cases, this serviceId won't be changed at all. If it is changed, then this is an extra place that needs to update. If the API is following the evolution guidelines, then there is no need to change the serviceId. Changing serviceId will impact all clients and I think it is an even bigger issue.
https://doc.networknt.com/design/evolution/

@stevehu i thought that every time there's a new version of an api the service id will change.. since the version is within the service id. Is that not the case?
What was the downside of including that check within the health handler?

We can put the serviceId into the header and check that in the health check handler; however, if someone wants to use a customized handler to cascade checking database, then he/she must do the same check for the serviceId. This can be easily forgotten and cause problem consul health check.


forced reflow getCarouselWidth

Bug Report
Current Behavior
A component is producing forced reflow and slowing down the render of 50 carousels instances (search results)
I removed lazy load, classes and extra scoped styling to pin point what produce this reflow with no success
Stack is Rails / Webpacker and Vue 2.5 and I could not reproduce the bug with a sample Vue app
Someone has a clue about where should I look ? A conflicting UI package ? A directive ?  SASS Styling ?
Input Code and steps to reproduce
    <carousel
              :per-page="perPage"
              :navigation-enabled="navigationEnabled"
              :pagination-enabled="paginationEnabled"
              :loop="loop"
              :navigation-next-label="navigationNextLabel"
              :navigation-prev-label="navigationPrevLabel"
              :mouse-drag="mouseDrag"
              :navigateTo="miniCarousel"
              @pageChange="onPageChange($event)">
      <slide v-for="(image, index) in images" :key="index">

      </slide>
    </carousel>

Expected behavior/code
No reflows
Additional context/Screenshots

pointing to
 getCarouselWidth: function getCarouselWidth() {
          var t = this.$refs["VueCarousel-inner"];
          return this.carouselWidth = t && t.clientWidth || 0, this.carouselWidth;
        },

/bump.. someone has a clue ?

anyone ?


ros_emacs_utils: 0.4.15-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository ros_emacs_utils to 0.4.15-1:

upstream repository: https://github.com/code-iai/ros_emacs_utils.git
release repository: https://github.com/code-iai-release/ros_emacs_utils-release.git
distro file: noetic/distribution.yaml
bloom version: 0.9.7
previous version for package: 0.4.14-3

The version from yesterday's PR still had the old CMake version in CMakeLists, which made the build unstable. This version fixes that. Sorry for the inconvenience.


Handling Floating Windows

For some reason, Emacs always starts floating.
Could it be related to this line in my sway config, and if yes, what's the alternative?
assign [class="Emacs"] workspace 1
Either way, even using SUPER+SPACE to toggle focus between tiling and floating windows does not work there for some reason.
And while we are at it, sometimes Right-click menus and Extension popups quickly popup before being covered by firefox itself (the latter more commonly, the former is not happening right now, seems to be primarily when a page is loading slowly), making them quite useless. This issue persist when moving Firefox to floating with Super+Shift+Space.

For me the keybind to make things float is super+shift+space, not just super+space.

But the keybind to toggle focus between tiling and floating is C-S-SPC, which is what I was referring to - the other keybind works.
One example for the latter issue is the MasterPassword extension in Firefox: I click on it, the window pops up and immediately vanishes again, presumably covered by Firefox itself. Maybe the focus handling for pop-up windows does not work properly here?

Ah, well. Now I get it. I can't really tell why that happens in this particular case, as it works for regular Firefox UI elements. BUT I had the same issue for example with java applications, like IntelliJ in the past.

And how did you solve it?
The rightclick issue also comes back from time to time...

Not using IntelliJ anymore :dancing_men:

I still can't use MasterPassword in the browser, which is quite annoying.
Leaving Intellij is bold, did you stop with Java/Kotlin or find an alternative?
I am still struggling with them as I just can't find an adequate replacement, even though I despise the keybindings not conforming to what I have in my Doom Emacs.
To get back to the original issue, I have this in my config:
assign [class="Emacs"] workspace 1
assign [app_id="firefox"] workspace 2

Let's say I already have a terminal open in workspace 2 and open Firefox.
Unlike what I thought, it does not actually start floating. What happens is that it weirdly coexists in a way that it is not accessible until I close the terminal.

Here you can see the same thing for Emacs - it opens in workspace 1, but I can't access it via CMD-TAB nor CMD-1

I can't test it right now, but this may be related to the renaming of workspaces, sworkstyle performs. Could you try if this changes anything for you?
assign [class="Emacs"] workspace number 1

I think this just works.

Interesting, I had this exact thing in my config the whole time, but now it actually works ^^

I can't find anything about 'number' being deprecated in the manpage. Am I blind?

not deprecated, but irrelevant ;)


extra CAN MODE VER in land_detail.jnl

Reported by Andrew Wittenberg on 26 Jul 2005 23:44 UTC
As of the 5.81 version of the scripts, there's still a CAN MODE VER in
land_detail.jnl, which prevents the user's environment from being preserved.
See my comment #9 on bug 1014.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1300

Comment by<EMAIL_ADDRESS>on 1 Aug 2005 19:02 UTC
Fixed in version version 1.6 of land_detail.jnl.

Comment by<EMAIL_ADDRESS>on 28 Aug 2006 17:07 UTC
This extra "can mode ver" is still present as line 117 of go/land_detail.jnl, at
least as provided in the latest v6.00 tar file at:
ftp://www.ferret.noaa.gov/pub/linux_32/fer_environment.tar.Z
with the following result:
    NOAA/PMEL TMAP
    FERRET v6
    Linux(g77) 2.4.21-32 - 08/23/06
    28-Aug-06 12:58

yes? show mode verify
MODE            STATE        ARGUMENT
VERIFY           SET         DEFAULT
yes? go basemap
yes? go land_detail
yes? show mode verify
MODE            STATE        ARGUMENT
VERIFY        CANCELLED      DEFAULT

Comment by<EMAIL_ADDRESS>on 14 Sep 2006 16:57 UTC
This crept back in due my misunderstanding how to create the Ferret release  --
the correct version of land_detail.jnl is checked in to CVS, and is included in
all of the fer_environment.tar.Z files for the operating systems in the Ferret
v6.0 release. It's also installed for PMEL in the jnls script directories on
porter, stout, ferret, corona


update porosity.py

The function density_porosity was returning only 0. I´ve fixed it to return the porosity.

I've tested the function returning "phi" and it works here, I don't know what went wrong in the tests.

tests where made and everything works
I'm doing the merge here.


[0.9.4] export 'useInsertionEffect' (imported as 'useInsertionEffect') was not found in 'react

The recently released version 0.9.4 has caused an issue with React 17

I think #12 will fix this, take a look before I merge?

 I tried to reproduce it, but couldn't.
Thank you

Hi @shkreios This is a reproduction in CRA
https://github.com/nghieptiki/cra-react-17-use-event-0.9.4-bug
Demo Codesanbox

@nghieptiki Thank you, I tried out the fix from #12 it seems to fix the problem, the strange part is if I compare webpack bundled the development output of useEvent. The lines which include useInsertionEffect  i.e.
const useBrowserEffect =
    typeof window !== "undefined"
      ? react__WEBPACK_IMPORTED_MODULE_0__.useInsertionEffect ??
        react__WEBPACK_IMPORTED_MODULE_0__.useLayoutEffect
      : () => {};

The only lines that differ are strangely the ones where others react hooks are accessed, i.e.
// 0.9.4
const latestRef = (0, react__WEBPACK_IMPORTED_MODULE_0__.useRef)(
  useEvent_shouldNotBeInvokedBeforeMount
);
// with fix
const latestRef = react__WEBPACK_IMPORTED_MODULE_0__.useRef(
  useEvent_shouldNotBeInvokedBeforeMount
);

I expect this has something to do with the way how webpack bundles are accesses packages.
Nonetheless the fix from #12 should resolve the problem.


[FIX #185] Implemented Toast Feature

Implemented toast feature, now if user follows or does any action, he gets notified by a toast, as shown in video below.
Issue no.: #185
https://github.com/SUGAM-ARORA/UniCollab/assets/132436131/4dd2e69e-526f-488a-99ce-85f154a2935b

@yashmandi Branch updation is required . Just do that and it is good to go.


prometheus: 2.49.0 -> 2.49.1

Diff: https://github.com/prometheus/prometheus/compare/v2.49.0...v2.49.1
Changelog: https://github.com/prometheus/prometheus/blob/v2.49.1/CHANGELOG.md
Description of changes
Only one hour after the Prometheus release 2.49.0, hotfix 2.49.1 came out to fix a regression that broke scraping for some targets.
@mfrw was very quick to fetch the upgrade (thanks!) within that 1 hour window, but must have overlooked the hotfix for a full month.
This PR upgrades nixpkgs Prometheus to the latest hotfix version.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

@hacklschorsch - I actually knew about it but for some reason the tests kept failing on me and I did not turn-around to debug.
I guess, I should have created an Issue for others to look at.
My bad :(

@mfrw No worries.  Strange though that the tests failed - this is a hotfix release, with only one small change (which had no tests).
Now, how does something like this find its way into nixpkgs?  Do I have to do anything, or just chill out and wait for the maintainers to find time to look at it?

@mfrw No worries. Strange though that the tests failed - this is a hotfix release, with only one small change (which had no tests).

@hacklschorsch I am pretty sure, it was my personal dev-box that might have had issues & not the release itself.

Now, how does something like this find its way into nixpkgs? Do I have to do anything, or just chill out and wait for the maintainers to find time to look at it?

IMO, our (non-committers) work is done. We might have watch out for review items if any (unlikely in this case); other than that, it would be now the maintainers and committers that actually merge this in.
Thank you for the hotfix PR :)

Result of nixpkgs-review pr 288817 run on x86_64-linux 1

3 packages built:

prometheus
prometheus.cli
prometheus.doc

Thanks!

Can I expedite this fix's way into stable?
IIUC I can't issue a request for automated backporting, right?  I'd have to add the backport 23.11 label IIANM?
Can someone add the label to get this fix ported to current stable 23.11?

nudge nudge ?  I'd like to upgrade to current nixos-23.11 (for the recent GitLab security patches), but I'm blocked by this missing Prometheus Hotfix in nixos-23.11.
Would be amazing if s.o. could add the backport label for this.  Pretty please? @fpletz @WilliButz @Frostman


Result form: Add explanatory messaging

Story
When I'm confused about some of the more abstract or technical required fields on the Results form, I can quickly access contextual help instead of combing through TolaWiki.

Acceptance criteria
Note: These tooltips should follow the same design pattern we're using for tool tip on Program page graphs.
Tool tip text

[x] 1. Result date: "This date determines where the result appears in indicator performance tracking tables. If data collection occurred within the target period, we recommend entering the last day you collected data. If data collection occurred after the target period ended, we recommend entering the last day of the target period in which you want the result to appear."

(Please note the use of italics for emphasis.)

[x] 2. Measure against target:

[x] 2.1. If the indicator's target frequency is annual, semi-annual, tri-annual, quarterly, or monthly, then the tool tip says, "The target is automatically determined by the result date."
[x] 2.2.  If the target frequency is midline/endline or event, then the tool tip says, "You can measure this result against the Midline or Endline target."
[x] 2.3.  If the target frequency is Life of Program (LoP) only, then the tool tip says, "All results for this indicator will be measured against the Life of Program (LoP) target."

[x] 3. Record name: "Give your record a short name that is easy to remember."

[x] 4. Link to file or folder: "Provide a link to a file or folder in Google Drive or another shared network drive. Please be aware that TolaActivity does not store a copy of your record, so you should not link to something on your personal computer, as no one else will be able to access it."

(Please note the use of italics for emphasis.)
Mockups
Please note that the most recent text updates in this ticket are not reflected in these mockups.

Housekeeping

[ ] Unit test/s written wherever applicable
[x] i18n tags included wherever applicable
[ ] Functionality is accessible to people using screen readers

Deployment Verification

[x] Confirmed “Ready for Deploy” status
[x] Verified text matches Acceptance Criteria:

Result date: "This date determines where the result appears in indicator performance tracking tables. If data collection occurred within the target period, we recommend entering the last day you collected data. If data collection occurred after the target period ended, we recommend entering the last day of the target period in which you want the result to appear."
(Please note the use of italics for emphasis.)

Measure against target:

2.1. If the indicator's target frequency is annual, semi-annual, tri-annual, quarterly, or monthly, then the tool tip says, "The target is automatically determined by the result date."
2.2. If the target frequency is midline/endline or event, then the tool tip says, "You can measure this result against the Midline or Endline target."
2.3. If the target frequency is Life of Program (LoP) only, then the tool tip says, "All results for this indicator will be measured against the Life of Program (LoP) target."
3. Record name: "Give your record a short name that is easy to remember."

Link to file or folder: "Provide a link to a file or folder in Google Drive or another shared network drive. Please be aware that TolaActivity does not store a copy of your record, so you should not link to something on your personal computer, as no one else will be able to access it."


⚠ AGEG website (redirect) has degraded performance

In 38a183c, AGEG website (redirect) (https://ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 2156 ms

Resolved: AGEG website (redirect) performance has improved in a055aa5.


Crash app in case import NFT by ERC20, PSP22 contract

Describe the bug
Crash app in case import NFT by ERC20, PSP22 contract
To reproduce the behavior
Steps:

Open SubWallet extension
Go to the import NFT screen
Input data below:

Networks: Aleph Zero Testnet
Contract address: 5DGHdeY4SXsZ2w8RZrgXXJwHXXe2Qg8LCnUoDTr3tnBnu2BC
Input valid data for remain fields

Click on Import button

Actual: Crash app when back to NFT tab

Expect: Discuss more

Version test: v1.0.12
Do not reproduce this issue.


Array extractors can collide with assignments

They are already valid JS:
// variable declaration + assignment
let Foo
(x) = y

// assignment + assignment
Foo
(x.z) = y

Here are some solutions for this issue:

forbid the line terminator between QualifiedName[?Yield, ?Await] and ExtractorArrayBindingPattern[?Yield, ?Await]
use other sigils for the array pattern, i.e. ||, ~[], etc.
innovate the syntax, i.e. let [x] with Foo = y, etc.

Sorry for the noise. I actually turned on error recovery mode and overlook the errors.


Removed react-next package as its no longer required.

Removed react-next package as its no longer required.

#481


hyprland-per-window-layout: init at 2.3

Description of changes

Add the hyprland-per-window-layout - per window layout for Hyprland.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Thank you and welcome as a maintainer :)

Thank you, @onny and @misuzu!


bug: offchain tables are not hydrated

Offchain tables are not hydrated in the client. The component browser does seem to receive the Store logs though.

Closing as this was fixed in https://github.com/latticexyz/mud/pull/1843


Fixing the link to onPageLoad sample

Noticed it was 404.


Update typescript definitions

Update type definitions of STATE and PITCH types to be more accurate.
Also run prettier on the index.d.ts file.

thanks for this @andrekovac -- the main branch (v2) has been rewritten in Typescript. I'll close this for now.


Express instrumentation does not properly handle router usage

I don't think the current express instrumentation handles usage of a express.Router().   Perhaps change use-express.mjs for now to not use a Router and we add a separate issue about handling Router in instr-express?
Originally posted by @trentm in https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1966#discussion_r1505871458
I expected it to show up as router - /post/:id but instead was just router - /

@JamieDanielson This is related to https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1947
At the moment,http.route attributes of router and middleware spans are set to the "mount path" (in the cases I could see).
// Tests PR example (root mount path)
const routerA = express.Router();
routerA.get('/post/:id', (req, res) => {
  res.send(`Post id: ${req.params.id}`);
});
app.use(routerA);

// Adapted example (non-root mount path)
const routerB = express.Router();
routerB.get('/:id', (req, res) => {
  res.send(`Post id: ${req.params.id}`);
});
app.use('/post', routerB);

Tests PR example (root mount path)
Adapted example (non-root mount path)

router span
http.route: "/"name: "router - /"
http.route: "/post"name: "router - /post"

request span
http.route: "/post/:id"name: "GET /post/:id"
http.route: "/post/:id"name: "GET /post/:id"

Spans for the example from tests PR (using a minimal express app)
{
  traceId: 'a1c7faafb2135a3d970d31093ee63437',
  parentId: 'fb4451520d0fa2b5',
  traceState: undefined,
  name: 'middleware - query',
  id: '788673a2a133abce',
  kind: 0,
  timestamp:<PHONE_NUMBER>205000,
  duration: 375.252,
  attributes: {
    'http.route': '/',
    'express.name': 'query',
    'express.type': 'middleware'
  },
  status: { code: 0 },
  events: [],
  links: []
}
{
  traceId: 'a1c7faafb2135a3d970d31093ee63437',
  parentId: 'fb4451520d0fa2b5',
  traceState: undefined,
  name: 'middleware - expressInit',
  id: '7ece8b4ea1cf76fc',
  kind: 0,
  timestamp:<PHONE_NUMBER>205000,
  duration: 372.568,
  attributes: {
    'http.route': '/',
    'express.name': 'expressInit',
    'express.type': 'middleware'
  },
  status: { code: 0 },
  events: [],
  links: []
}
{
  traceId: 'a1c7faafb2135a3d970d31093ee63437',
  parentId: 'fb4451520d0fa2b5',
  traceState: undefined,
  name: 'router - /',
  id: 'de567c024714ac71',
  kind: 0,
  timestamp:<PHONE_NUMBER>206000,
  duration: 111.275,
  attributes: {
    'http.route': '/',
    'express.name': '/',
    'express.type': 'router'
  },
  status: { code: 0 },
  events: [],
  links: []
}
{
  traceId: 'a1c7faafb2135a3d970d31093ee63437',
  parentId: 'fb4451520d0fa2b5',
  traceState: undefined,
  name: 'request handler - /post/:id',
  id: 'ee140eee706875b2',
  kind: 0,
  timestamp:<PHONE_NUMBER>208000,
  duration: 32.743,
  attributes: {
    'http.route': '/post/:id',
    'express.name': '/post/:id',
    'express.type': 'request_handler'
  },
  status: { code: 0 },
  events: [],
  links: []
}
{
  traceId: 'a1c7faafb2135a3d970d31093ee63437',
  parentId: undefined,
  traceState: undefined,
  name: 'GET /post/:id',
  id: 'fb4451520d0fa2b5',
  kind: 1,
  timestamp:<PHONE_NUMBER>201000,
  duration: 12980.123,
  attributes: {
    'http.url': 'http://localhost:3000/post/5',
    'http.host': 'localhost:3000',
    'net.host.name': 'localhost',
    'http.method': 'GET',
    'http.scheme': 'http',
    'http.target': '/post/5',
    'http.user_agent': 'insomnia/8.6.1',
    'http.flavor': '1.1',
    'net.transport': 'ip_tcp',
    'net.host.ip': '::ffff:<IP_ADDRESS>',
    'net.host.port': 3000,
    'net.peer.ip': '::ffff:<IP_ADDRESS>',
    'net.peer.port': 58665,
    'http.status_code': 200,
    'http.status_text': 'OK',
    'http.route': '/post/:id'
  },
  status: { code: 0 },
  events: [],
  links: []
}

I expected it to show up as router - /post/:id but instead was just router - /

At first I naively expected something like "/*" for http.route (implying a name like router - /*), since the router is matching every route.
Now I'm thinking that doesn't make sense either, because http.route, as defined in the semantic conventions, only applies to a request and probably shouldn't describe how some framework internal routing is matching (even if it plays a role in the request route matching).
So I think your expectation fits better than mine. However, now I'm wondering if http.route should be included at all for router and middleware spans. They don't represent a request and don't have any other http span attributes. At least for people without Open Telemetry experience (like me) http.route could always be a bit confusing on these spans, because a router or middleware also has a route (path template) leading to it.
An alternative could be to use an attribute like express.route (or express.mount_path (router span) and similar), hopefully making it clearer what to expect.
Thinking about it this way, I even like the current naming of router spans being "router - <Mount Path (Template)>". In the examples, "router - /" and "router - /post" are actually helpful. But maybe this is confusing for the people with more Open Telemetry experience (expecting http.route to be part of names, as it is for request spans).
I'm happy to provide a PR, which would address both issues (once I know which keys and values make sense).

Thanks for looking into this. I've been facing similar issues fully populating http.route in Express applications with more complicated nested routers. I came across aspecto-io Express Instrumentation. I replaced @opentelemetry/instrumentation-express js-contrib package with Aspecto's opentelemetry-instrumentation-express locally and it seemed to set http.route with a more complete path template I was hoping for. Sadly it's marked as deprecated as of last week, but seems like a decent workaround or might be interesting to compare approaches.

However, now I'm wondering if http.route should be included at all for router and middleware spans.

@JohannesHuster Thank you for detailing your thoughts here! I can see how there are a few ways we could go about this. One thing I am checking out is how other languages may handle these types of middleware and router spans because as you mention, they're not the actual request spans so perhaps they shouldn't have any http attributes like this. There may still be good reasoning to use something like express.route, as you also point out and as it seems may be included in the aspecto instrumentation linked by @neilfordyce .  We already have things like express.type and express.name in the instrumentation. I'll look further into this!

@JamieDanielson, I have been debugging this usage as it's also breaking the SDK in Sentry v8. I can try to wrap up a PR if you don't have an active work in progress.


[Task] Prevent SonarCloud checks on GitHub to fail if coverage for new code is < 80%

What product(s) is this feature for?
Sage Monorepo
Description
I recently pushed new code for the first time and the new code has a coverage of less than 80%, which triggers a failed SonarCloud check. See https://github.com/Sage-Bionetworks/sage-monorepo/runs/16520909517
Anything else?
No response
Code of Conduct

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

Solution

I create a Quality Gate named Sage way based on the default Sonar way profile.
I updated the profile to so that coverage less than 0% results in a failed check (never)
I configure the new profile as the default for the existing and new projects


add instance segmentation per_sample_transform

What does this PR do?
Fixes https://github.com/PyTorchLightning/lightning-flash/issues/930
Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes?
[x] Did you write any new necessary tests? [not needed for typos/docs]
[x] Did you verify new and existing tests pass locally with your changes?
[x] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[x] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?

[x] Make sure you had fun coding 🙃

@ethanwharris Hi, may I ask for help? )
I created all necessary tests for my new code changes. But It's strange that Codecov reports: will decrease coverage by 19.69%.
Could you approve a workflow for test running?

@MrShevan - I guess we can merge this :) I'm going to merge this for now, once all tests are done. Thank you for your contribution.

@ethanwharris @krshrimali Thanks for your review ! It was a pleasure for me to work on this PR :)


Update faq-managed-response.md

Submitted via Learn Editor.

Removed the following.
**For devices (Available now)

Release file from quarantine

For users (coming soon)

Suspend user**

Confirming merge


Change "Gradle/Grails" to "Gradle" on artifact page

What are you trying to do?

Browsing to an artifact page and finding the instructions for how to use it with Gradle.
E.g. when opening https://search.maven.org/beta/artifact/org.junit.jupiter/junit-jupiter-api/5.2.0-M1/jar there's an entry for "Gradle/Grails" that shows the Grails logo and the URL of the Grails Gradle plugin. Gradle is used for a lot more things than Grails so this listing is confusing. A user might ask himself whether it will only work for Grails etc.

What feature or behavior is this required for?

Instead, it should just show "Gradle", the Gradle logo, and use gradle.org as the URL.

How could we solve this issue? (Not knowing is okay!)

see above :)

Anything else?

In addition, it would be great if the URLs for all entries would be clickable.
Please let me know whether you think this makes sense. If so, I'd be happy to submit a PR.

@marcphilipp thanks for filing this! This appeared pretty simple, so took a quick look at.
I updated the naming and icon and made to text actual links, let me know if this is what you were having in mind :

Thank you @SirMaster! I noticed that there is a Gradle Kotlin DSL entry below. Would it make sense to clarify "Gradle" as "Gradle Groovy DSL"?

@eriwen @marcphilipp feel free to pop over a PR if you want, we'd love to get some contributions!

@DarthHater do note I already have a PR  for this :-) that's what the screen shot is from. So might save them some time/effort.


Services forgot between sessions

Hi,
I just installed franz 5.0 on Ubuntu 14.04 from deb file (see #3 ). At the first run everything was fine, I was able to import services from my previous franz 4.4, to add new services and create an account.
But after closing franz and opening it again, services are not saved and it prompts again to add services. Furthermore, if I click on any service it doesn't actually let me set it, but rather it stays there doing nothing.

I have experienced some issues with the import of on premise services. Can you please send me an email to<EMAIL_ADDRESS>to let me know what email address you have used during signup?

sure!

Ok after debugging we found out it was because I was loading a custom recipe that I was using with Franz 4. Thanks for the help @adlk !


Add about Ternary operator in day-6

Select the Day of Content
Day 6
What information is missing?
ternary operator is an advanced topic in conditional statements

hey @subhadipbhowmik please assign me this task

hey @subhadipbhowmik please assign me the task

hey @subhadipbhowmik please look into this and merge if everything is ok.


Weird Mask

Hi there, I have a question about the mask after padding. Just like in DETR, if an image is calculated by padding and backbone, it can get an h*w feature map, where the sensitivity field of each feature point in the original image must be large, which contains part of the pixel value and part of the padding value. If we want to calculate the self attention of this feature map, the padding in the original image has been mixed with the pixel value in the same feature point, but the mask value corresponding to the feature point is either 0 or 1. Is this inappropriate?

@YangHan-Morningstar https://github.com/open-mmlab/mmdetection/blob/main/mmdet/models/detectors/detr.py#L92

Yeah, I have seen this. But I think this code results in that a feature point is ignored even if there are some useful features in it, because the sensitivity field containing original pixel and padding value, the feature calculated from these original pixel are just ignored. I think this is weird.


DM-159 Implement UI changes per design feedback

Move "Complete Profile" button on signUpStepTwo page to the right on desktop
Fix opacity of sign in/up of nav buttons.

Going to merge this PR because it's minimal, cosmetic stuff


Feature/grid upgrade test

This introduces a new breakpoint for extra large (xl) and shifts the previous breakpoint values to the next breakpoint (previous xs value now becomes the sm value etc). The previous iteration of the design system had no extra large media query breakpoint resulting in mobile and tablet width sharing the same dimensions and being unable to design for a mobile 1st experience.
The previous PR #848 merged into develop addressed most of the challenges with the new breakpoint but a zero pixel width on the xs breakpoint resulted in this breakpoint not being created correctly yet a positive pixel width of 1 and above did, but resulted in a 1 pixel space. The variable $AU-media-xs was removed and instead the narrowest breakpoint was changed from min-width to a max-width of $AU-media-sm minus 1.
in _globals.scss:
@if( $breakpoint == "xs" ) {
	@media (max-width: $AU-media-sm - 1) {
		@content;
	}
}

The following line in _module.scss requires additional checking, as the calculation 0 - $AU-grid-12-gutter-width results in a negative value.
@include AU-media( xs ) {
	width: ( 0 - $AU-grid-12-gutter-width );
}

PR details reverted to previous fix by @sukhrajghuman. This PR no long relevant.


Meet the designer meeting

Preparation for "Meet the designer" monthly meeting (april 2021) with:

intro to the team
what has been happening since January
collaboration with designers in Equinor
data grid component
color tokens

Could you check the draft in figma @BirteThornquist