Add configuration options for AWS S3 server access logging

Description
Fixes #3003.

In our environment the S3 bucket where should be stored S3 access logs is pre-created by "central" team and we don't have permissions to do any changes. In such case we don't have to:

Create it - the current code creates the logging bucket only if it doesn't exist. No change is needed.
Configure logging bucket e.g. ACL, public access, encryption, tls enforcement - adding option to skip the configuration for access log bucket.
PartitionDateSource - Adding one more option to allow users to configure PartitionDateSource.

Additionally 1) adding error logging into the function configureAccessLogBucket. Without it I wasn't able to detect why the logging isn't configured on the source bucket. The error is returned but ignored. 2) Adding code to detect if the logging policy / configuration was change. The previous code just check if some policy is enabled.
TODOs
Read the Gruntwork contribution guidelines.

[x] Update the docs.
[ ] Run the relevant tests successfully, including pre-commit checks.
[x] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
[ ] Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added / Removed / Updated [X].
Migration Guide

N/A.

Hey @findmyname666 , are you willing to rebase to get this PR up to speed?
Also, are you able to run the tests locally to confirm that they work as expected?

Hey @findmyname666 , are you willing to rebase to get this PR up to speed?
Also, are you able to run the tests locally to confirm that they work as expected?

Hi @yhakbar , I will try to do it this week. Thx.

Hey @findmyname666 , are you willing to rebase to get this PR up to speed?
Also, are you able to run the tests locally to confirm that they work as expected?

--- PASS: TestParseTerraformStateLocal (0.00s)
=== CONT  TestDiffersFrom/same_backend_type_value
=== CONT  TestDiffersFrom/different_gcs_prefix_values
=== CONT  TestDiffersFrom/different_s3_key_values
--- PASS: TestGetAwsSessionConfigWithAssumeRole (0.00s)
    --- PASS: TestGetAwsSessionConfigWithAssumeRole/all-values (0.00s)
=== PAUSE TestGetTerraformInitArgs/empty-no-values
DEBU[0000] Backend s3 has not changed.
=== CONT  TestDiffersFrom/identical_S3_configs
=== CONT  TestDiffersFrom/gcs_null_values_ignored
=== RUN   TestGetTerraformInitArgs/valid-s3-configuration-keys
DEBU[0000] Backend s3 has not changed.
=== RUN   TestConfigValuesEqual/equal-multiple-keys
=== PAUSE TestGetTerraformInitArgs/valid-s3-configuration-keys
=== PAUSE TestConfigValuesEqual/equal-multiple-keys
DEBU[0000] Backend gcs has not changed.
=== RUN   TestGetTerraformInitArgs/terragrunt-keys-filtered
=== RUN   TestConfigValuesEqual/equal-encrypt-bool-handling
=== PAUSE TestGetTerraformInitArgs/terragrunt-keys-filtered
DEBU[0000] Changed from map[bucket:foo location:europe-west3 prefix:bar project:foo-123456] to map[bucket:foo location:europe-west3 prefix:different project:foo-123456]
=== PAUSE TestConfigValuesEqual/equal-encrypt-bool-handling
=== CONT  TestDiffersFrom/different_boolean_values_and_boolean_conversion
DEBU[0000] Changed from map[bucket:foo key:bar region:us-east-1] to map[bucket:foo key:different region:us-east-1]
=== RUN   TestConfigValuesEqual/equal-general-bool-handling
=== PAUSE TestConfigValuesEqual/equal-general-bool-handling
=== CONT  TestDiffersFrom/different_gcs_boolean_values_and_boolean_conversion
DEBU[0000] Changed from map[something:true] to map[something:%!s(bool=false)]
=== RUN   TestConfigValuesEqual/equal-ignore-s3-tags
DEBU[0000] Changed from map[something:true] to map[something:%!s(bool=false)]
=== PAUSE TestConfigValuesEqual/equal-ignore-s3-tags
=== CONT  TestDiffersFrom/different_s3_region_values
=== RUN   TestConfigValuesEqual/equal-ignore-dynamodb-tags
=== PAUSE TestConfigValuesEqual/equal-ignore-dynamodb-tags
=== RUN   TestConfigValuesEqual/equal-ignore-accesslogging-options
=== PAUSE TestConfigValuesEqual/equal-ignore-accesslogging-options
DEBU[0000] Changed from map[bucket:foo key:bar region:us-east-1] to map[bucket:foo key:bar region:different]
=== RUN   TestConfigValuesEqual/unequal-wrong-backend
=== CONT  TestForcePathStyleClientSession/path-style-non-existent
=== CONT  TestForcePathStyleClientSession/path-style-true
=== CONT  TestDiffersFrom/different_backend_type_values
=== PAUSE TestConfigValuesEqual/unequal-wrong-backend
INFO[0000] Backend type has changed from s3 to atlas
=== RUN   TestGetTerraformInitArgs/empty-no-values-all-terragrunt-keys-filtered
=== RUN   TestConfigValuesEqual/unequal-values
=== CONT  TestForcePathStyleClientSession/path-style-false
=== PAUSE TestGetTerraformInitArgs/empty-no-values-all-terragrunt-keys-filtered
=== PAUSE TestConfigValuesEqual/unequal-values
=== RUN   TestGetTerraformInitArgs/lock-table-replaced-with-dynamodb-table
=== PAUSE TestGetTerraformInitArgs/lock-table-replaced-with-dynamodb-table
=== RUN   TestGetTerraformInitArgs/dynamodb-table-not-replaced-with-lock-table
=== PAUSE TestGetTerraformInitArgs/dynamodb-table-not-replaced-with-lock-table
=== RUN   TestGetTerraformInitArgs/assume-role
=== PAUSE TestGetTerraformInitArgs/assume-role
=== RUN   TestConfigValuesEqual/unequal-non-empty-config-nil
=== PAUSE TestConfigValuesEqual/unequal-non-empty-config-nil
=== CONT  TestGCSConfigValuesEqual/equal-both-empty
=== CONT  TestDiffersFrom/null_values_ignored
=== CONT  TestGCSConfigValuesEqual/unequal-wrong-backend
DEBU[0000] Backend s3 has not changed.
DEBU[0000] Backend type has changed from gcs to wrong
=== CONT  TestGCSConfigValuesEqual/equal-ignore-gcs-labels
=== RUN   TestConfigValuesEqual/unequal-general-bool-handling
=== CONT  TestGCSConfigValuesEqual/equal-general-bool-handling
=== CONT  TestGCSConfigValuesEqual/equal-encrypt-bool-handling
=== PAUSE TestConfigValuesEqual/unequal-general-bool-handling
=== CONT  TestGCSConfigValuesEqual/equal-multiple-keys
=== CONT  TestGCSConfigValuesEqual/equal-one-key
=== RUN   TestConfigValuesEqual/equal-null-ignored
=== PAUSE TestConfigValuesEqual/equal-null-ignored
=== CONT  TestGCSConfigValuesEqual/unequal-non-empty-config-nil
=== CONT  TestGCSConfigValuesEqual/unequal-general-bool-handling
=== CONT  TestGCSConfigValuesEqual/equal-empty-and-nil
=== CONT  TestGCSConfigValuesEqual/terragrunt-only-configs-remain-intact
=== CONT  TestGCSConfigValuesEqual/equal-null-ignored
=== CONT  TestGetTerraformInitArgs/empty-no-values
--- PASS: TestGetAwsSessionConfig (0.00s)
    --- PASS: TestGetAwsSessionConfig/all-values (0.00s)
    --- PASS: TestGetAwsSessionConfig/no-values (0.00s)
    --- PASS: TestGetAwsSessionConfig/extra-values (0.00s)
DEBU[0000] Backend config changed from map[something:%!s(bool=false)] to map[something:%!s(bool=true)]
=== CONT  TestGCSConfigValuesEqual/unequal-values
=== CONT  TestGetTerraformInitArgs/empty-no-values-all-terragrunt-keys-filtered
=== CONT  TestGetTerraformInitArgs/terragrunt-keys-filtered
=== CONT  TestGetTerraformInitArgs/valid-s3-configuration-keys
=== CONT  TestGetTerraformInitArgs/lock-table-replaced-with-dynamodb-table
=== CONT  TestGetTerraformInitArgs/dynamodb-table-not-replaced-with-lock-table
--- PASS: TestCreateS3LoggingInput (0.00s)
    --- PASS: TestCreateS3LoggingInput/equal-default-prefix-no-partition-date-source (0.00s)
    --- PASS: TestCreateS3LoggingInput/equal-no-prefix-no-partition-date-source (0.00s)
    --- PASS: TestCreateS3LoggingInput/equal-custom-prefix-no-partition-date-source (0.00s)
    --- PASS: TestCreateS3LoggingInput/equal-custom-prefix-custom-partition-date-source (0.00s)
DEBU[0000] Backend config changed from map[foo:different] to map[foo:bar]
=== CONT  TestDiffersFrom/different_gcs_location_values
=== CONT  TestGCSConfigValuesEqual/equal-empty-and-nil-backend-config
=== CONT  TestConfigValuesEqual/equal-null-ignored
=== CONT  TestConfigValuesEqual/equal-ignore-accesslogging-options
=== CONT  TestConfigValuesEqual/equal-ignore-dynamodb-tags
=== CONT  TestConfigValuesEqual/equal-both-empty
=== CONT  TestConfigValuesEqual/equal-general-bool-handling
=== CONT  TestGetTerraformInitArgs/assume-role
=== CONT  TestConfigValuesEqual/equal-multiple-keys
=== CONT  TestConfigValuesEqual/equal-one-key
=== CONT  TestConfigValuesEqual/equal-empty-and-nil-backend-config
=== CONT  TestConfigValuesEqual/equal-empty-and-nil
=== CONT  TestConfigValuesEqual/unequal-values
DEBU[0000] Changed from map[bucket:foo location:europe-west3 prefix:bar project:foo-123456] to map[bucket:foo location:different prefix:bar project:foo-123456]
=== CONT  TestConfigValuesEqual/unequal-general-bool-handling
=== CONT  TestConfigValuesEqual/unequal-wrong-backend
=== CONT  TestConfigValuesEqual/unequal-non-empty-config-nil
=== CONT  TestConfigValuesEqual/equal-encrypt-bool-handling
=== CONT  TestConfigValuesEqual/equal-ignore-s3-tags
--- PASS: TestForcePathStyleClientSession (0.00s)
    --- PASS: TestForcePathStyleClientSession/path-style-false (0.00s)
    --- PASS: TestForcePathStyleClientSession/path-style-true (0.00s)
    --- PASS: TestForcePathStyleClientSession/path-style-non-existent (0.00s)
--- PASS: TestParseTerraformStateInvalid (0.00s)
--- PASS: TestValidateS3Config (0.00s)
    --- PASS: TestValidateS3Config/no-region (0.00s)
    --- PASS: TestValidateS3Config/no-bucket (0.00s)
    --- PASS: TestValidateS3Config/no-key (0.00s)
--- PASS: TestGCSConfigValuesEqual (0.00s)
    --- PASS: TestGCSConfigValuesEqual/equal-both-empty (0.00s)
    --- PASS: TestGCSConfigValuesEqual/unequal-wrong-backend (0.00s)
    --- PASS: TestGCSConfigValuesEqual/equal-ignore-gcs-labels (0.00s)
    --- PASS: TestGCSConfigValuesEqual/equal-general-bool-handling (0.00s)
    --- PASS: TestGCSConfigValuesEqual/equal-encrypt-bool-handling (0.00s)
    --- PASS: TestGCSConfigValuesEqual/equal-one-key (0.00s)
    --- PASS: TestGCSConfigValuesEqual/equal-multiple-keys (0.00s)
    --- PASS: TestGCSConfigValuesEqual/unequal-non-empty-config-nil (0.00s)
    --- PASS: TestGCSConfigValuesEqual/equal-empty-and-nil (0.00s)
    --- PASS: TestGCSConfigValuesEqual/terragrunt-only-configs-remain-intact (0.00s)
    --- PASS: TestGCSConfigValuesEqual/equal-null-ignored (0.00s)
    --- PASS: TestGCSConfigValuesEqual/unequal-general-bool-handling (0.00s)
    --- PASS: TestGCSConfigValuesEqual/equal-empty-and-nil-backend-config (0.00s)
    --- PASS: TestGCSConfigValuesEqual/unequal-values (0.00s)
DEBU[0000] Backend type has changed from s3 to wrong
DEBU[0000] Backend config changed from map[foo:different] to map[foo:bar]
--- PASS: TestDiffersFrom (0.00s)
    --- PASS: TestDiffersFrom/both_empty (0.00s)
    --- PASS: TestDiffersFrom/different_s3_bucket_values (0.00s)
    --- PASS: TestDiffersFrom/different_gcs_bucket_values (0.00s)
    --- PASS: TestDiffersFrom/identical_GCS_configs (0.00s)
    --- PASS: TestDiffersFrom/same_backend_type_value (0.00s)
    --- PASS: TestDiffersFrom/identical_S3_configs (0.00s)
    --- PASS: TestDiffersFrom/gcs_null_values_ignored (0.00s)
    --- PASS: TestDiffersFrom/different_gcs_prefix_values (0.00s)
    --- PASS: TestDiffersFrom/different_s3_key_values (0.00s)
    --- PASS: TestDiffersFrom/different_boolean_values_and_boolean_conversion (0.00s)
    --- PASS: TestDiffersFrom/different_gcs_boolean_values_and_boolean_conversion (0.00s)
    --- PASS: TestDiffersFrom/different_s3_region_values (0.00s)
    --- PASS: TestDiffersFrom/different_backend_type_values (0.00s)
    --- PASS: TestDiffersFrom/null_values_ignored (0.00s)
    --- PASS: TestDiffersFrom/different_gcs_location_values (0.00s)
DEBU[0000] Backend config changed from map[something:%!s(bool=false)] to map[something:%!s(bool=true)]
--- PASS: TestConfigValuesEqual (0.00s)
    --- PASS: TestConfigValuesEqual/equal-null-ignored (0.00s)
    --- PASS: TestConfigValuesEqual/equal-both-empty (0.00s)
    --- PASS: TestConfigValuesEqual/equal-ignore-dynamodb-tags (0.00s)
    --- PASS: TestConfigValuesEqual/equal-ignore-accesslogging-options (0.00s)
    --- PASS: TestConfigValuesEqual/equal-general-bool-handling (0.00s)
    --- PASS: TestConfigValuesEqual/equal-multiple-keys (0.00s)
    --- PASS: TestConfigValuesEqual/equal-one-key (0.00s)
    --- PASS: TestConfigValuesEqual/equal-empty-and-nil-backend-config (0.00s)
    --- PASS: TestConfigValuesEqual/equal-empty-and-nil (0.00s)
    --- PASS: TestConfigValuesEqual/unequal-non-empty-config-nil (0.00s)
    --- PASS: TestConfigValuesEqual/equal-encrypt-bool-handling (0.00s)
    --- PASS: TestConfigValuesEqual/equal-ignore-s3-tags (0.00s)
    --- PASS: TestConfigValuesEqual/unequal-wrong-backend (0.00s)
    --- PASS: TestConfigValuesEqual/unequal-values (0.00s)
    --- PASS: TestConfigValuesEqual/unequal-general-bool-handling (0.00s)
--- PASS: TestGetTerraformInitArgs (0.00s)
    --- PASS: TestGetTerraformInitArgs/empty-no-values (0.00s)
    --- PASS: TestGetTerraformInitArgs/empty-no-values-all-terragrunt-keys-filtered (0.00s)
    --- PASS: TestGetTerraformInitArgs/terragrunt-keys-filtered (0.00s)
    --- PASS: TestGetTerraformInitArgs/valid-s3-configuration-keys (0.00s)
    --- PASS: TestGetTerraformInitArgs/dynamodb-table-not-replaced-with-lock-table (0.00s)
    --- PASS: TestGetTerraformInitArgs/assume-role (0.00s)
    --- PASS: TestGetTerraformInitArgs/lock-table-replaced-with-dynamodb-table (0.00s)
PASS
ok      github.com/gruntwork-io/terragrunt/remote       0.016s


Fan Toggle not displaying state

Checklist:

[X] I updated to the latest version available
[X] I cleared the cache of my browser

Release with the issue:
v1.10.3
Last working release (if known):
Browser and Operating System:
OS: Linux Mint and Android
Browsers: Linux: Firefox & Chrome
Android: HA App, Chrome, Firefox

Description of problem:
I have configured a card with a fan entity that does not support speed adjustment -- it is 'on' or 'off'. As such, I have enabled the toggle_on_click option in the slider. With this configuration, the tap_action (toggle) functions as expected (turning the fan on or off) but the state reported by the card remains 'Off'. Similarly, the icon for the fan does not spin.
My assumption is that for fan entities, the card is looking for a percentage as the state. When toggle_on_click is enabled for fan entities, the state check should look for 'on' and 'off' instead.

Javascript errors shown in the web inspector (if applicable):

Additional information:
Love this card!

OK yeah I have a fan that does support speed adjustment and that is broken so it only can turn on or off the fan. :)
Suspect something in HASS.io has changed wrt fans and how they are interacted with from a js perspective, too odd we're having similar issues this close together.


feat(web): filters to use POST requests to limit bot crawling

https://pins-ds.atlassian.net/browse/APPLICS-1081
POC of filters using POST request rather than GET to limit  bot crawling

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[ ] I have performed a self-review of my own code
[ ] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[ ] I have referenced the ticket number above
[ ] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 2.33.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Creation of double shopping carts after approval payment Mollie

Expected behavior
This module makes after a payment has taken place a double shopping cart with the same items
Actual behavior
n.b.
Steps to reproduce the behavior
See after a payment has been excepted by Mollie the shopping carts and you wil see a duplication of the one what has just be handle a agreed on paymant
Environment

PrestaShop version: <IP_ADDRESS>
Mollie module version: 4.0.7
PHP version: 7.2.33

Hello and thank you for your query.
@Goedkoopsteverf are you experiencing the same issues on 4.0.8?
Best Regards.

We cann't test this because the error 500 is in this version so we have to switch back to the previous version.

Hey @Goedkoopsteverf thank you for your information,
We are still having some struggles trying to reproduce the case.
Could you please give us the actual video screen reproduction steps?
Best Regards.


glitchy sidebar on settings

Bug description
The text is moving, and the scrollbar only appear on hover, which is a bit frustrating
https://github.com/user-attachments/assets/f86b4ec7-b8e5-4549-bab0-0234abe79c13
Operating system
Windows 11
Installation Method
Installer from website/GitHub releases
Version
next (development version)
Steps to reproduce

Go to settings
Open preferences
Hover and don't hover to see appear the navbar

Relevant log output

Additional context
No response

We could style it and do something nice all accross the app
See https://www.geeksforgeeks.org/how-to-change-style-of-scrollbar-using-tailwind-css/
The current problem come from the following lines
https://github.com/podman-desktop/podman-desktop/blob/5aef2f0b2da27efddd7d7fa2a0b6007780756ae9/packages/renderer/src/PreferencesNavigation.svelte#L83
I am not sure why we did that, IMO the scrollbar should be always visible 🤔

We have a duplicate of this component here so same problem for kubernetes
https://github.com/podman-desktop/podman-desktop/blob/5fc6524e407275b15fe2f1abb29c912c2a0e2737/packages/renderer/src/SubmenuNavigation.svelte#L31

Learn more about sidebar https://next.shadcn-svelte.com/docs/components/sidebar


not a issue but a idea - speed hack

hello!
is there a possibility to add a speed hack in the bot?
it seems to me really cool if it possible to add this addition too
i am waiting for a reply
regards
Dave

this is a bot, not a speed hack

it was just a suggestion, i only wanted to know: "is it possible", but never mind...

It's not possible as the game is running on a server which we don't have access to.


prefer remotePatterns over domains for images

From https://nextjs.org/docs/api-reference/next/image#remote-patterns

We recommend using remotePatterns instead so you can restrict protocol and pathname.

Thanks to @leerob for pointing this out. 🔒

Rebased to get the new CI workflow running on this PR: https://github.com/replicate/getting-started-nextjs/pull/8 🍏


Update documentation

I'm finding Codo rather unmanageable. It's awkward to use and flat doesn't work on one of my computers. Vaguely defeats the purpose of auto-documentation generation.
I'd like to replace the documentation with something else.

Resolved! Moved to Read the Docs. I've left the underlying stuff undocumented, since it's well-commented.


Add support for property changes (and change sets)

@ppalaga I've implemented the first support for change sets: https://github.com/heiko-braun/api-gen/blob/changesets/api/src/test/java/org/wildfly/swarm/config/IntegrationTestCase.java#L193

In short, this code:
        DataSource dataSource = new DataSource("TestDS");
        dataSource.jndiName("java:/foo/bar/DS");
        dataSource.userName("john.doe");
        dataSource.password("password");

        Map<String, Object> changeset = new HashMap<>();
        dataSource.addPropertyChangeListener(evt -> {
            changeset.put(evt.getPropertyName(), evt.getNewValue());
        });

        dataSource.userName("john.doe2");
        dataSource.password("password2");

        EntityAdapter<DataSource> entityAdapter = new EntityAdapter<>(DataSource.class);
        ModelNode operation = entityAdapter.fromChangeset(changeset);
        // invoke on operation on server

produces a composite operation like:
{
    "operation" => "composite",
    "address" => [],
    "steps" => [
        {
            "address" => [
                ("subsystem" => "datasources"),
                ("data-source" => "*")
            ],
            "operation" => "write-attribute",
            "name" => "password",
            "value" => {"password" => "password2"}
        },
        {
            "address" => [
                ("subsystem" => "datasources"),
                ("data-source" => "*")
            ],
            "operation" => "write-attribute",
            "name" => "userName",
            "value" => {"user-name" => "john.doe2"}
        }
    ]
}

Great, thanks!

This complements the API to read/write full resources on the EntitAdapter:

https://github.com/heiko-braun/api-gen/blob/changesets/runtime/src/main/java/org/wildfly/config/invocation/EntityAdapter.java#L92

https://github.com/heiko-braun/api-gen/blob/changesets/runtime/src/main/java/org/wildfly/config/invocation/EntityAdapter.java#L269

@ppalaga let me know if this fits your purpose

@lance This is a change request from hawkular. They intend to use the lib standalone to configure wildfly instances. Any objections if we merge this?

@ppalaga did you have the time to look at it?

@heiko-braun sorry, not yet, we are releasing a hk milestone today.

@heiko-braun I am ok with merging this. As an aside, it does feel odd that what is now the "canonical" repo for wildfly-config-api is a fork of yours, even though that's exactly how it happened.

@lance to avoid "fork of", @heiko-braun should "Transfer ownership" of his repo to wildfly-swarm.

@lance yes, it's some weird github internal. I don't it to remain like this either, but then I have new clue how to fix. But we can try what @ppalaga suggested.

Blocked by the decision how to move forward with #7 and #8


should add_f64 return an option?

In my opinion, as_f64 shouldn't return an Option<f64> as all patterns return back Some.
It looks like it's only returning an Option<f64> because of the arb. precision features; which drops the error via ok().

I do not know to what extent option is necessary or not, but I would like to point out that wrapping something into an option can sometimes reduce performance.

This is intentional because JSON numbers can hold quantities that are bigger than fit into f64. See https://github.com/serde-rs/json/commit/b1ca6c718674e5d1f9f66f9cbe12b930f547fc0b.

@deeprobin: if the performance difference between f64 and Option<f64> is a bottleneck for your codebase then it should not be using serde_json::Value.


Build issue

rustup 1.27.1 (2024-05-07), cargo 1.83.0 (5ffbef321 2024-10-29).
Got the following error when trying to build master with cargo build:
error[E0308]: mismatched types
   --> src/test_summary.rs:122:68
    |
122 |             if self.slowest_test.is_none_or(|(time, _)| new_time > time) {
    |                                                                    ^^^^ expected `&Duration`, found `Duration`
    |
help: consider dereferencing the borrow
    |
122 |             if self.slowest_test.is_none_or(|(time, _)| *new_time > time) {
    |                                                         +

error[E0308]: mismatched types
   --> src/test_summary.rs:128:76
    |
128 |             if self.most_memory_used.is_none_or(|(memory, _)| new_memory > memory) {
    |                                                                            ^^^^^^ expected `&u64`, found `u64`
    |
help: consider dereferencing the borrow
    |
128 |             if self.most_memory_used.is_none_or(|(memory, _)| *new_memory > memory) {
    |                                                               +

The change suggested above doesn't work, though then another suggestion (provided below) is made, which does work.
I have absolutely no idea whether this is correct or horrible, as I don't know rust at all:
diff --git a/src/test_summary.rs b/src/test_summary.rs
index c0c402c..3125ad8 100644
--- a/src/test_summary.rs
+++ b/src/test_summary.rs
@@ -118,15 +118,15 @@ impl TestSummary {
     }

     fn add_metrics(&mut self, metrics: &ExecutionMetrics, test_name: &str) {
-        if let Some(new_time) = &metrics.time {
-            if self.slowest_test.is_none_or(|(time, _)| new_time > time) {
-                self.slowest_test = Some((*new_time, test_name.to_string()));
+        if let Some(new_time) = metrics.time {
+            if self.slowest_test.as_mut().is_none_or(|(time, _)| new_time > *time) {
+                self.slowest_test = Some((new_time, test_name.to_string()));
             }
         }

-        if let Some(new_memory) = &metrics.memory_kibibytes {
-            if self.most_memory_used.is_none_or(|(memory, _)| new_memory > memory) {
-                self.most_memory_used = Some((*new_memory, test_name.to_string()));
+        if let Some(new_memory) = metrics.memory_kibibytes {
+            if self.most_memory_used.as_mut().is_none_or(|(memory, _)| new_memory > *memory) {
+                self.most_memory_used = Some((new_memory, test_name.to_string()));
             }
         }
     }

This error seems to be caused by Rust 1.82 adding a utility method with the same name as a method we add to Option, but with slightly different functionality. I'll make sure to fix this on master by the end of the week, and in the meantime it looks like your fix would work.
Additionally, I have to warn you that currently master is not totally stable, as it's the version following a total rewrite and it hasn't been properly tested or finished yet. No releases of this version have been made as of yet (even if I'm planning to do so, I just have little time for it at this moment). If you want a more stable experience, I recommend the 1.2.2 branch

Fixed in the newest commit.


test(pagination): make tests pass on Chrome

Don't ask me why but without this change pagination tests are failing in Chrome (perfectly fine in FFox, thus not visible on TravisCI)

I'll try later when I get home, it is really weird.

Works for me, although sounds like a potential ng2 bug here.

It works for me perfect Pawel, even in chrome (locally). Are you telling me that running "gulp" locally fails for you?

I've just updated Chrome on my Ubuntu box and tests are passing now :-/ Must have been particular Chrome version messing up things. Closing for now.


1.82: can not run code . in wsl1

VS Code Version:  1.82
OS Version:  win11
wsl Version: wsl1

Steps to Reproduce:
VSCODE cannot be opened using code path
It can be opened normally with version 1.81.1

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.82.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I also have this problem which I managed to fix by:

Uninstall VS Code 1.82.0 in Windows
Remove VS Code Server in WSL by running rm -r ~/.vscode-server within WSL shell
Reinstall VS Code 1.81.1 in Windows
Open VS Code in Windows and disable the auto update feature in File > Preferences > Settings
Running code path in WSL works again

Thanks @ACken2! Had the same issue (WSL1, VS Code 1.82.0, Windows 10) and your solution resolved it for now.

I'm able to reproduce and found the problem.
The bug has been there for a while, but only surfaces now in WSL1, likely to the Node update (from 16 to 18)

I can confirm that the workaround by @ACken2 worked. For those what want to find the working VS Code version 1.81.1 see this URL: https://code.visualstudio.com/docs/supporting/faq#_previous-release-versions.

Having this exact same problem. WSL1, VSCode 1.82.0 and Windows 11.

Fix is the latest Insiders and will be in a 1.82.2 coming at the end of the week.

@aeschli should this be closed?

To verify:

install the latest stable/insiders on Windows, don't start it yet
open a terminal on a WSL1 distro. To see what version distros have, use wsl --list --verbose. To install a new WSL1 distro run
wsl --set-default-version 1; wsl --install Ubuntu; wsl --set-default-version 2;
run code .. If it opens with a remote window: success.


Focus should not place on input field after closing the modal

The issues forum is NOT for support requests. It is for bugs and feature requests only.
Please read https://github.com/angular-ui/bootstrap/blob/master/CONTRIBUTING.md and search
existing issues (both open and closed) prior to opening any new issue and ensure you follow the instructions therein.
Bug description:
In internet explorer 10, the focus is automatically placed on input field after I close the modal. This should not be happen when I close the modal.
Link to minimally-working plunker that reproduces the issue:
Version of Angular, UIBS, and Bootstrap
angularjs 1.4
angular-ui-bootstrap, Version: 0.12.1 - 2015-02-20
bootstrap 2.2.2
Angular:
UIBS:
Bootstrap:

Any reproduction?

Closing due to lack of actionable information.


Native Session support

As beaker is no longer maintained there might be a need for native session support with files.
This can be made in one class which should not take a lot of space in the module.
I can supply a not so working one (had problems with concurrency when using gevent for example)...
This is only feature which should be in bottle as currently it requires a dance with the wolves to set up correctly and beaker is still buggy as hell.

I don't think bringing it into bottle is the right answer, but the example using beaker's session should definitely be removed or replaced.  We got hit hard with it's race conditions last year, and wound up rolling our own replacement: https://github.com/keredson/drsession

Yes, beaker is not perfect. But I do not known any alternative that really solves this issue other than not using sessions and store stuff in a real database instead. Even 'drsession' shows the same race condition problem if you modify the same key in a session from two concurrent requests. For example, you would not be able implement a request counter (for rate limiting) with drsession in any reliable way. You'd have to access redis directly for that (using the redis HINCRBY command) or risk loosing updates occasionally.
I think it would not hurt to warn users about these limitations, and make absolutely clear that sessions are no substitute for a real database. If it's not acceptable to loose updates, don't put it in a session.
But for simple use cases, beaker and co are still useful. A typical workflow (store user info in session on login, remove session on logout) works just fine. I think its an error to use sessions for more than that.

Didn't see this reply before I responded to other issue, sorry.  Actually pretty sure we implemented hincrby for +=.  I don't agree that it's an error to use sessions for more than the session id.  But fair enough.

@defnull you were right, we weren't using HINCRBY.  Fixed. https://github.com/keredson/drsession/issues/3


255 Chars maximum for TTS voices

Is there 255 Characters maximum increasing from 180 Characters maximum for all TTS Voices?

I don't believe there is an easy way to do this.  Even if I could, some TTS providers have their own character limits.  You could always have your character say whatever needs to be said in multiple scenes.


Rename disabled channel

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#4273  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @karlenDimla and the rest of your teammates on  Graphite


IT container semi-automatic scripts

Scripts that automatize the analysis in the IT Container.

I realized the pre-commit workflow was not actually running fine and fixed it. You should merge the master here to have that running. In principle it should fail for this branch, I tried running pre-commit and many files are not formatted well. You can set-up pre-commit following https://magic-cta-pipe.readthedocs.io/en/latest/developer-guide/getting-started.html#installing-magic-cta-pipe-in-development-mode . In that way you know that the lint and pyflakes workflows will be ok. Also running make doc will tell you if the documentation generation is fine (I plan to add documentation validation to pre-commit too).

It seems to me that there are some scripts very similar to each other in the IT_container_data_MC_bash_scripts and IT_container_data_nsb_bash_scripts, with a lot of duplicated code which could be somehow unified. Moreover I read in one of the README:
This is a temporary branch (to store these scripts): A new branch and a PR will be created from the master after the '4 LSTs' PR merge.

so, are the scripts in IT_container_data_nsb_bash_scripts to be reviewed at all? @Elisa-Visentin @ranieremenezes

Yes, sorry, I forgot to remove those lines (here we copied only some of the scripts that are in the temporary branch).
As for the duplicated code, actually they are two versions of the automatic pipeline, one of them running both data and MCs and the second one processing only real data. The kind of analysis (and in the future even the cluster) will 'select' the needed folder

I realized the pre-commit workflow was not actually running fine and fixed it. You should merge the master here to have that running. In principle it should fail for this branch, I tried running pre-commit and many files are not formatted well. You can set-up pre-commit following https://magic-cta-pipe.readthedocs.io/en/latest/developer-guide/getting-started.html#installing-magic-cta-pipe-in-development-mode . In that way you know that the lint and pyflakes workflows will be ok. Also running make doc will tell you if the documentation generation is fine (I plan to add documentation validation to pre-commit too).

I will do this tomorrow, because I have to check a bit the merge result (when I merged the master into this branch today, I got some duplicated lines/functions, some lines/files removed in the master re-appeared here and some changes were not merged adequately). A lot of files, so a lot of merge conflicts and a lot of wrong automatic merges  :(

@Elisa-Visentin @ranieremenezes I saw you merged the latest changes of the master in this branch. As you can see, I added some validation of the documentation, because otherwise it would not be rendered correctly in the html version. I do not know which editor you are using. If you are using Visual Studio Code, I use this extension (https://marketplace.visualstudio.com/items?itemName=njpwerner.autodocstring) to generate automatically snippets of the documentation following the required style. If you use SublimeText, there was one as well I was using in the past. If you use PyCharm I think there is an extension available for sure. Let me know if you need support in fixing the docs.

I'm just fixing them! Thank you!

We tried to merge the two folders (and script versions) into a single one (the cluster and the analysis type passed in the config file). As for using the MCP config.yaml instead of writing all the lines, we tried to implement it in the setting_up_config_and_dir script: let us know if this is ok and we will implement it in all the scripts. As for the DOC, we will fix them after we fix the scripts format


Validate Rocky Linux 8.5

https://docs.rockylinux.org/release_notes/8_5/
Following https://github.com/rancher/rancher/issues/35460

Hi @superseb,
I wonder why this was closed.
I have just tried to install Rancher on Rocky Linux 8.5 - and it does not work at all.
It seems like Rocky Linux is using a systemd package that causes k3s to just exit with and never come up.
So and the version that works was from Rocky Linux 8.4 - so if Rancher works on RHEL 8.5 - its not the same as Rocky Linux 8.5.
So is it possible that you guys can work on getting it working on Rocky Linux 8.5?
Or do we have to downgrade to Rocky Linux 8.4 if thats even possible?
I will be happy to help diagnose if required.
Thanks


Added TypeScript type definition file

Nothing special. Just wanted to have TS support.

Coverage remained the same at 100.0% when pulling 413591a2078e1d1786e0e4c097be569c88959132 on mcoakley:master into 83f880cd670ff485deba2dcef76e4bfddb40131e on devlato:master.

@mcoakley Hi!
Thanks for contributing!
TypeScript definitions are definitely a must-have. But I won't accept this PR. I would prefer to use declare module ... syntax for the definitions instead to prevent potential conflicts.
That's why I've just added the definition file by myself (but I've listed you in the Author section).
The new version containing definitions will go live very soon, so feel free to update.

@devlato Understood and truly, no need to list me, the thought is appreciated. Thanks for the module!

@mcoakley The new version (1.2.4) is live. Feel free to update!


Update erroneous cloud security_domain

security_domain: cloud appeared in a number of detections, but this is not a valid value for the security_domain enumeration in Enterprise Security.
This has been fixed in the following contentctl PR:  https://github.com/splunk/contentctl/pull/314
Once that PR has been merged, this PR should be evaluated and merged as well.

no presence of security_domain: cloud , the contentctl PR looks good too!


Missing input rom error on DSi SD (FIXED)

I have confirmed the rom does exist its just not finding it.
the path to the rom is (root/Apps/unxDS/unx/boot.rom)

FIXED unx folder has to be in roos of SD card

This layout should be fixed in https://github.com/asiekierka/uxnds/commit/7fb9120b6af38d679d63f8d82d9509817afd2ea4


Possible to customize existing models?

Laravel Version: 5.4.15
Voyager Version: 0.11
PHP Version: 5.6
Database Driver & Version: 10.0.28-MariaDB-0+deb8u1

Description:
I would like to add an attribute to an out of the box bread post item and use it on a relationship. so a Post can have 1 access_level and an access_level can have many Posts.  This would require a accessLevelId method on Post. Can I achieve this without editing the Post model in vendor? Voyager::model pulls hard-coded model (use TCG\Voyager\Models\Post) in BreadController, so unsure how to move forward.

since Post is pulled from the container,  I added my method to App\Post, extended TCG\Voyager\Models\Post & asked the container to return App\Post when asked for an instance of TCG\Voyager\Models\Post in my AppServiceProvider. Hopefully this is best practice.


Fix Cisco SE loading of data from API

Fixes #3362
Proposed Changes

Add the json library
Parse the data from the stream
Fixes where the data is actually stored in the API

@scottymcraig Please add the updated zip package in this PR. Thank you.


ng2-img-cropper not working with reactive form or model

ng2-image-cropper is not working properly when I load image first time.when I upload same image second time than it will be loaded.

i find the solutions for this issue. it's working well for me.
 myReader.onloadend = function (loadEvent:any) {
            image.src = loadEvent.target.result;
            let timeoutId = setTimeout(() => {
                that.cropper.setImage(image);
              }, 100);
        };
        myReader.readAsDataURL(file);

thanks.


feat(homepage): Activity graph in banner

Adds an activity graph to the homepage banner.
The mobile view will need more work if we expect the page to be viewed on small screens. It might be worth asking Ant to look at this when he's back from the holidays.

Feel free to tweak the view to the style you want or let me know if you want anything different.

Will you be able to remove the grey box around the Get started button and the EDGESEC title?

Will you be able to remove the grey box around the Get started button and the EDGESEC title?

@mereacre I've done this, I'm not sure the title is as readble.

Or maybe we change the transparency level of the graph

Or maybe we change the transparency level of the graph

I think making the test a bit stronger or adding a border works better:

I like.

The border and weight makes all the difference.


Fix a typo and update the test for then new concepts

One of the tests was still targeted for a branch where completion signatures were split between elements and the whole sequence.

/ok to test


'has' method return wrong result

i have below code: https://runkit.com/ndinhbang/5fab75f6f8205200133e3273
const collect = require("collect.js")
let arr = ['aaa'];
let fliped = collect(arr).flip();
let hasItem = fliped.has('aaa');

the expected result is true, but it actually return false

Hi, @ndinhbang.
This PR #265  will resolve problem with method 'has'.
In your example, if checking property first element in array, after flip return the object: {  'aaa': 0 }.
After has, checking return a value of key. In your case value 0, thats equates to false.
All keys with negative values like: 0, null, undefined, '', false - will return false.
I hope that helped.

Closed in 9a94695

@Kassaila thank you so much!
I think we can use Object.prototype.hasOwnProperty.call(_this.items, key)  instead of  Object.keys(_this.items).includes(key)
for better performance, right ?

@ndinhbang Yes we can. If it gives the best performance, on a lot of operations with the method has.

✅ hasOwnProperty https://github.com/ecrmnn/collect.js/commit/02dff133957eb398f31aca899138a76603316491

@ecrmnn @Kassaila thank you


Support PHP 8, drop PHP 5 & 7.0 - 7.1

As discussed in #615. Related #616.

This seems to be already done in https://github.com/nrk/predis/blob/main/.travis.yml (main)
and can be closed then.

@dereuromark: I'll keep this open until the tests pass again.
Are you up for fixing the test failures on main that came with the PHPUnit upgrade from 4 to 8?

@dereuromark: I'll keep this open until the tests pass again.
Are you up for fixing the test failures on main that came with the PHPUnit upgrade from 4 to 8?

I can help with this if needed as well :).

I didnt see the test fails
@AhmedRaafat14 much appreciated.

@AhmedRaafat14: Go for it 👍🏻

@emmanix2002 @AhmedRaafat14 You can split it up, too, so we have many small PRs and not one massive one 🙂
There seem to be quite a few sectors:

Depreciation notices
Redis 6 changes
Broken mocks

I was just thinking about the same thing.
@emmanix2002 you can tell what you already started fixing and I can take another point, what do you think :)!
Otherwise, I will just start looking into the docs 😉

@AhmedRaafat14 fixed issues for some of the files inside of tests/PHPUnit for now, specifically:

tests/PHPUnit/ArrayHasSameValuesConstraint
tests/PHPUnit/PredisTestCase
tests/PHPUnit/RedisCommandConstraint

Currently on:

tests/PRedis/ClientExceptionTest

There are quite a number of issues but the ones in the PHPUnit directory are the lowest hanging fruits

@AhmedRaafat14 quick question, I don't know if we want to set namespace declarations inside the test files. IMO, we should only use namespace declarations for the actual source file.
I ask because the files inside tests/Predis have namespace declarations on them.
What do you think?

I ask because the files inside tests/Predis have namespace declarations on them.

If am doing that I will use namesspaces for sure I love having everything inside a specified namespace and not just laying around (I think laravel doesn't have namespace for tests not sure about that but remember something like that!) but tobh it confuses me sometimes 😂.
So I would suggest yes please use namespaces.

@AhmedRaafat14 😂 Cool, we'll maintain the namespaces.

We just dropped Travis for 2.0 and added GitHub actions 👍🏻

I guess this can be closed now?
We've done everything described here: v1.1 targets PHP 5.3 ~ 8.0 and main targets PHP 7.2 ~ 8.0, test suites for these branches were fixed accordingly and they are green for both.


Question: How to change applicationID in Google Cast dynamically?

I initialize Google Cast SDK in my application: didFinishLaunching like that:
let criteria = GCKDiscoveryCriteria(applicationID: kGCKDefaultMediaReceiverApplicationID)
let options = GCKCastOptions(discoveryCriteria: criteria)
GCKCastContext.setSharedInstanceWith(options)

I stream video content to Default Media Receiver and it works.
But I need to be able to change kGCKDefaultMediaReceiverApplicationID to a custom receiver application id to send different content to a custom receiver application I registered via Google Cast SDK Developer Console. I can't relaunch the app to specify a different application id.
Is there a way to do it dynamically at some point in the app after GCKCastContext.setSharedInstanceWith(options) has already been called?
The call of this method works only once and I cannot update GCKDiscoveryCriteria: GCKCastContext.setSharedInstanceWith(options)
I use google-cast-sdk-no-bluetooth, version: 4.5.3
I also asked the same question on stackoverflow:
https://stackoverflow.com/questions/65331067/how-to-change-applicationid-in-google-cast-dynamically-in-ios-sdk
In Android SDK there is a method which can change the receiver app id on the fly: https://developers.google.com/android/reference/com/google/android/gms/cast/framework/CastContext#public-void-setreceiverapplicationid-string-applicationid
Unfortunately, I don't see anything like that in the iOS SDK :(
The only thing I found is this (inside GCKSessionManager):
/**
 * Sets the default session options for the given device category.The session options are passed to
 * the GCKDeviceProvider::createSessionForDevice:sessionID:sessionOptions: method when the user
 * selects a device from the Cast dialog.  For Cast sessions, the session options can specify which
 * receiver application to launch.
 *
 * @param sessionOptions The session options. May be nil to remove any previously set
 * options.
 * @param category The device category.
 *
 * @since 4.0
 */
- (void)setDefaultSessionOptions:(nullable GCKSessionOptions *)sessionOptions
               forDeviceCategory:(NSString *)category;

But there is no documentation on which sessionOptions and category to pass (category is probably kGCKCastDeviceCategory). It's not understandable which params exist and how to construct them.

Found a solution myself: https://stackoverflow.com/a/65410319/5147552
Would be great to have an official way to do it too.
I will appreciate it, if you decide to include it into the SDK and update your docs.
Thanks in advance!


Building Autocorrect Feature Using NLP with Python

Article checklist
Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #4941

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

reference #4991

@srishilesh any updates??

@srishilesh any updates??

@dentex22
Please wait for your previous test reviewer @okeloviolet to review this.
Thanks.

@hectorkambow
Are we still allowing test peer-reviewers to review articles?
If not, I can take up and review this PR. It has been pending for a while.
Thanks.

@srishilesh feel free to review the article though I started reviewing the article here #4991

@dentex22
I'll start my review ASAP.

@dentex22
I'll start my review ASAP.

ok

@srishilesh done with changes

@dentex22
Great article.
I've made some changes to the formatting and flow. Make sure to go through the commits.
Also, thanks for adding the front matter and PRC line.
Moving for the final review.
Thanks.

ook @srishilesh

Welcome to Section EngEd and congrats on your first article @dentex22
Thank you for the review @srishilesh
Please go over the changes I've made.

Please reach out to me via Slack DM @dentex22


bootstrap.min.css not updated when it’s generated from a config.json

Hello developers,
I’m having problems with the generated minified bootstrap.min.css. I have my personal config.json for my web site, when I’ve updated from (http://getbootstrap.com/customize/) and save it again, the bootstrap.css file is updated ok, but the bootstrap.min.css does not. I have try in various occasions but the result it’s the same. On the other hand if I start a new json configuration the bootstrap.min.css file saved its well. What’s the problem? Could anyone help me?
Thanks in advantage……

What is incorrect with the resulting bootstrap.min.css? What version is the config.json from?

Hello and thank for the quick answer,
I’m using Bootstrap v3.3.2, and I load in the bootstrap site my json configuration file created 2 days ego. The problem  is that the new zip generated after make some modifications in http://getbootstrap.com/customize/  have:

The bootstrap.css updated ok with my new changes.
The bootstrap.min.css not updated, with my old .json configuration.

You are loading the config using the file picker at the top of the customizer, correct?
Please post your config.json file.
Please give examples of some of the changes that you are making that aren't being reflected in the minified CSS.

I had this problem about 2 weeks ago, but I have made some test during the morning and right now its working fine and the bootstrap.min.css file its updated correctly........thanks for the help

I had this problem about 2 weeks ago, but I have made some test during the morning and right now its working fine and the bootstrap.min.css file its updated correctly........

thanks for the help


Warning: getDefaultProps is only used on classic React.createClass definitions

During the build phase there are a lot of errors. They do not seem to be real errors since the build still finishes and I can serve the files.

Error: Warning: getDefaultProps is only used on classic React.createClass definitions. Use a static property named   defaultProps instead.

I've tried to figure out where they come from with grep -rnwl './node_modules' -e 'getDefaultProps' but I didn't find it yet.
Environment

react-static -v:  error: unknown option `-v'
node -v: v9.11.1
yarn --version or npm -v: 1.6.0
Operating system: MacOS 10.13.4

Steps to Reproduce the problem

run create using less-antdesign template
run yarn build

React static does not use the deprecated createClass utility. Not sure
where this is coming from, but it's not React Static. I would suggest
commenting out or removing dependencies until the error no longer displays
to find the culprit.
On Sun, May 13, 2018 at 6:17 AM Thijs Koerselman<EMAIL_ADDRESS>wrote:

During the build phase there are a lot of errors. They do not seem to be
real errors since the build still finishes and I can serve the files.
Error: Warning: getDefaultProps is only used on classic React.createClass
definitions. Use a static property named defaultProps instead.
I've tried to figure out where they come from with grep -rnwl
'./node_modules' -e 'getDefaultProps' but I didn't find it yet.
Environment

react-static -v: error: unknown option `-v'
node -v: v9.11.1
yarn --version or npm -v: 1.6.0
Operating system: MacOS 10.13.4

Steps to Reproduce the problem

run create using less-antdesign template
run yarn build

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/607, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCZF2JKfMKxhffdsFJTtz69XBv8Ulks5tyCRQgaJpZM4T8xtO
.

@tannerlinsley Aren't the examples supposed to build without errors / warnings? It doesn't give a very nice impression to newcomers.
If boilerplates do not have official support maybe consider making them external (like Gatsby uses a Github url for its CLI), so it's clear they are not the responsibility of react-static.

Absolutely. They are the responsibly of react static. If you are
experiencing this bug on a clean install then we need to know what template
you are using or be able to look at your repo/codr for reproduction. To our
knowledge and tests, we have never seen this problem, so the better you can
help us reproduce it, the faster we can solve the issue.
On Mon, May 14, 2018 at 1:48 AM Thijs Koerselman<EMAIL_ADDRESS>wrote:

@tannerlinsley https://github.com/tannerlinsley Aren't the examples
supposed to build without errors / warnings? It doesn't give a very nice
impression to newcomers.
If boilerplates do not have official support maybe consider making them
external (like Gatsby uses a Github url for its CLI), so it's clear they
are not the responsibility of react-static.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/607#issuecomment-388727034,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCYSMhWfHk3fnvCOiJip4vzJ7NP0jks5tyTbBgaJpZM4T8xtO
.

This is on a clean install. The steps to reproduce are as I reported them above.
And react-static -v gives an error, but --version tells me 5.9.1


How to set user_provider to Doctrine user provider?

Hello,
as per api-platform's recommedations, I am using Doctrine user provider in my API.
So, my User entity looks like this:
// src/Api/Entity/User.php
namespace App\Api\Entity;
class User implements UserInterface, \Serializable {...}

Now I have no idea how to configure user_provider. I tried to set it like this:
# config/packages/gesindet_jwt_refresh_token.yaml
gesdinet_jwt_refresh_token:
    user_provider: app.api.entity.user

But I'm getting this error:
Type error: Argument 1 passed to ...\RefreshTokenProvider::setCustomUserProvider() must implement interface ...\UserProviderInterface, null given
Do you have any idea how do I set user_provider path properly, please?

Just found the solution I put this
gesdinet_jwt_refresh_token:
    user_provider: security.user.provider.concrete.user_provider

And my security.yaml is the following
security:
#...
    providers:
        user_provider:
            entity:
                class: App\Entity\User
#...

Hi @sandoche!
In what version of Symfony are you working? With Symfony 4 that service does not exists :(

Forget it @sandoche, you are right and I'm a monkey patcher... 😅
My provider is not called user_provider, so its very improbable that Symfony will found that service.
Already fixed, thanks!

@sandoche sorry I forgot to reply earlier. I can also confirm that your solution just works fine, thank you!

@loffler I think this info has to be noted in the documentation. I broke my head in the internals to find out under which name the Security component registers custom user providers. Do you want a PR for documentation?


Release deposit when DAO is detroyed

The deposit created as part of #10 will be released when the DAO is destroyed.
The protocol then has to transfer the entire amount to the then-active owner of the DAO.

This is included in the reservation PR...


Mast Sail Components

Shrubs under mast are now sail components. This update lets you nest your UI shrubs inside of other UI shrubs using the <kid> element. For instance, if you have a diary shrub which contains text shrub children, you can write a shrub to view the text that can at once be used as the main UI representing the text shrub at its pith, and as a nested component within the diary shrub. It will exist as the same shrub in the back-end, and on the client if you have the text shrub and the diary shrub open in separate windows at the same time, the same diff is sent and applied to each.
Events which take place on nested sail components will be routed to the corresponding shrub, so you can write them in a self contained and modular way.
Only the shrubs that update are the ones that need to recompute their sail, so you can split your UI up to make it more efficient e.g. if you need to stream quick updates. To make things even more efficient, you can make a sail component static simply by not taking a rely poke and only rendering on init. You could use this for assets or large amounts of text, or you could have a static layout component as the root of your UI which has smaller dynamic ones nested in. Static components can be nested in dynamic ones and vice versa.

Instead of a ;kid; element which takes two attributes for the renderer imp and the pith, the element tag is now the name of the renderer imp prefixed by "imp", and it takes a text node which encodes the pith of the dependency it renders, e.g. ;imp_diary-ui: pith.


Update function el_click

I ran into a problem here while using the player in a nested element: offsetLeft doesn't always calculate the distance from the edge of the page, sometimes it just calculates the distance to the edge of its parent element (or from the parent element to the edge? I'm not certain). Anyway I believe that the getBoundingClient method I used here is compatible with more contexts — at the very least it fixed the problem I was having.

Hey @zachy9, thanks for the fix! 👍

you're welcome, thanks for the cool code


Move to a maintained fork of gomock

golang/mock was archived and no longer receives updates. It names go.uber.org/mock as a maintained fork, so switch to that library and generator.
/cc @mresvanis @ybettan @yevgeny-shnaidman

/lgtm


Remove @babel/core from babel-preset-react-app dependencies

It's not a dependency of babel-preset-react-app - it's not used anywhere inside it. Potentially it could be set as a peer dependency - just for information purposes, but not sure if you want that. It definitely ain't a hard dependency though.

I believe the PR is still sound so bumping for the stale bot.

I don't think we can make this change. It causes a whole bunch of peer dependency warnings: https://dev.azure.com/facebook/create-react-app/_build/results?buildId=1242&view=logs&jobId=8999f565-280a-527f-721e-375d49cc4cd5&j=8999f565-280a-527f-721e-375d49cc4cd5&t=7980f6bf-f3f8-5575-47e3-a23aae330cb3

If you want to keep @babel/core as hard dependency then you might want to move it to react-scripts or something and make @babel/core a peer of babel-preset-react-app.
Right now it being a hard dependency of babel-preset-react-app doesn't make sense - it's never required by the babel-preset-react-app. The @babel/core is always provided externally by the caller to your preset so any version used as a hard dependency of your preset is just hiding a potential issue as that version won't ever actually be used (unless hoisted, but that makes it only working by accident).

We do have it in react-scripts already. I agree we should change it to a peer dep though. It would make sense to follow official babel preset packages convention: https://github.com/babel/babel/blob/master/packages/babel-preset-react/package.json


Use removed_from_source field to filter dead links from Elasticsearch

We routinely crawl the web and consume APIs to find CC licensed works. As a search engine, we have to deal with link rot; images are often deleted or moved from their original location. During crawling, if we detect that an image has been deleted, we will mark it with the removed_from_source field in our database.
ingestion-server, our tool for building an Elasticsearch index, will need to be updated to discard images where removed_from_source=True.

@aldenstpage I want to work on this issue. Can you guide me how to proceed with this?

@alirizwi: I am actually working on this right now.


Database adapter in connections.js conflicts with local.js when they are defined using different properties

I want to have a separate db settings for my local development machine and one for production. The way sails accomplishes this by defining local settings in config/local.js and overwriting or combing them with the production ones.
So I can define my postgres adapter settings in 2 ways. One way is to use a connection url property, the second way is to user properties for host, user, password etc.
If I define my adapter using the same property in both local.js and connections.js (e.g. by setting the url property in both) it works fine. However if I set it up as below sails try to combine them and I end up with a database connection error.
Maybe this should be an issue in the sails-postgresql repo instead?
//code in  config/connections.js
 module.exports = {
    postgresql: {
       adapter: 'sails-postgresql',
       url: "postgres://user:password@localhost/db"
     }
 }

 //code in config/local.js
 module.exports = {
   connections: {
     postgresql: {
      adapter: 'sails-postgresql',
      host: 'host',
      user: 'user',
      password: 'password',
      database: 'database'
    }
}

I know there is a github issue somewhere that has a reference to this as well? but I can't find it.
But it Might be related to the following
http://stackoverflow.com/questions/28069677/handling-database-environment-configuration-in-sails-js/28080407#28080407
http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.connections.html?q=multiple-connections-for-an-adapter

I don't think this is a bug but a feature by design.  Last I checked, config files are merged which means settings in local.js are for override, not full replacement.  You basically end up with:
 module.exports = {
   connections: {
     postgresql: {
      adapter: 'sails-postgresql',
      host: 'host',
      user: 'user',
      password: 'password',
      database: 'database',
      url: "postgres://user:password@localhost/db"
    }
}

Which naturally will create a conflict unless you actually set
url : null

in local.js

@crh3675 that makes since

I have config/local.js with connection details for my local machine mongo db, but it always tries to connect with one specified in config/connection.js file (which is remote). Can anyone please provide more documentation on local.js file.
// connections.js
module.exports.connections = {
  'mongodb-dev': {
    adapter: 'sails-mongo',
    host: 'test-server.com',
    port: 27017,
    database: 'test-dev'
  },
}

// local.js
module.exports = {
  connections: {
    'mongodb-dev': {
      adapter: 'sails-mongo',
      host: 'localhost',
      port: 27017,
      database: 'test-local'
    },
  }
}

When I sails lift, it tries to connect with database at test-server.com. Any idea what could be happening?


lighthouse: fix validator service not setting arguments properly

This fixes lighthouse validator not respecting metrics and additional arguments NixOS configuration options.
Supersedes #206325.
Description of changes

Things done

Built on platform(s)

[ ] 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

[ ] 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/)
23.05 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@vcunat This is the new PR you've asked me to create.

Thank you for this !


Ensure that ObservableCollection(s) remain sorted when adding, removing and updating reminders

Currently when completing items they're simply added to the end of the list.

New implementation status: The list is updated when the tab page is navigated to - Not optimal.


Hi. How to make it work with dropbox links?

Steps to reproduce
Tell us about your environment:

Puppeteer version: last
Platform / OS version: ubuntu 16.04
URLs (if applicable):
Node.js version: 9

What steps will reproduce the problem?
Please include code that reproduces the issue.

What is the expected result?
counted number of words
What happens instead?
nothing

Are you able to provide some example code? Not really able to see what the issue is :)

Actually i found the solution. Thanks. Because of using iframe on dropbox it was difficult to get correct html.


Pre submit build status in github is not refreshed though the build has finished

Linux fuchsia_precache status was stuck for more than 2 hours for https://github.com/flutter/flutter/pull/83718 and commit: https://github.com/flutter/flutter/pull/83718/commits/bb267529516eb278e6489bbf38a5e9e0df3a933d.
However the build has finished: https://ci.chromium.org/ui/p/flutter/builders/try/Linux fuchsia_precache/16509/overview
From gcloud, there is no luci status refresh log about the above build.
To summarize, the build was scheduled/run in buildbucket, but status was not reflected in github UI.
/cc @yjbanov

obsolete


Issue running app on release/profile mode in flutter web

The following error appears when I run the web application in release / profile mode:
NoSuchMethodError: method not found: 'pendingResult' on null
js_primitives.dart:47     at _GetItImplementation.call$1$3$instanceName$param1$param2 (http://localhost:51996/main.dart.js:146471:30)
js_primitives.dart:47     at _GetItImplementation.call$3$instanceName$param1$param2 (http://localhost:51996/main.dart.js:146487:19)
js_primitives.dart:47     at StackedLocator.call$1$0 (http://localhost:51996/main.dart.js:153365:27)
js_primitives.dart:47     at StartupView_build_closure1.call$0 (http://localhost:51996/main.dart.js:81285:17)
js_primitives.dart:47     at ViewModelBuilder.viewModelBuilder$0 (http://localhost:51996/main.dart.js:153545:36)
js_primitives.dart:47     at _ViewModelBuilderState._createViewModel$0 (http://localhost:51996/main.dart.js:153559:36)
js_primitives.dart:47     at _ViewModelBuilderState.initState$0 (http://localhost:51996/main.dart.js:153553:15)
js_primitives.dart:47     at StatefulElement._firstBuild$0 (http://localhost:51996/main.dart.js:129606:51)
js_primitives.dart:47     at StatefulElement.mount$2 (http://localhost:51996/main.dart.js:129482:12)
js_primitives.dart:47     at StatelessElement.inflateWidget$2 (http://localhost:51996/main.dart.js:129249:16)

If I change this code in app.locator.dart:
import 'package:stacked/stacked.dart';
import 'package:stacked_services/stacked_services.dart';

import '';
import '../services/api_service.dart';
import '../services/authentication_service.dart';
import '../services/shared_preferences_service.dart';

final locator = StackedLocator.instance;

Future setupLocator() async {
  locator.registerLazySingleton(() => NavigationService());
  locator.registerLazySingleton(() => AuthenticationService());
  locator.registerLazySingleton(() => ApiService());
  final sharedPreferencesService = await SharedPreferencesService.getInstance();
  locator.registerSingleton(sharedPreferencesService);
}

For this one:
import 'package:get_it/get_it.dart';
import 'package:stacked_services/stacked_services.dart';

import '../services/api_service.dart';
import '../services/authentication_service.dart';
import '../services/shared_preferences_service.dart';

final locator = GetIt.instance;

Future setupLocator() async {
  locator.registerLazySingleton(() => NavigationService());
  locator.registerLazySingleton(() => AuthenticationService());
  locator.registerLazySingleton(() => ApiService());
  final sharedPreferencesService = await SharedPreferencesService.getInstance();
  locator.registerSingleton(sharedPreferencesService);
}

Everything works fine.
Apparently the problem is in StackedLocator.instance.

I was trying to figure out whats going on for 1h now. Thanks @katusiky !

That's a weird bug because in debug mode everything works?!

thanks @katusiky!
Unfortunately same error occurs when using stacked_themes, cost me the whole weekend to find that out.
Here is actually final locator = GetIt.asNewInstance(); used, so I'm not sure if it's 100% related to StackedLocator.instance.
I got here the code to reproduce it, just played around a bit with the combination of provider, get_it, stacked and stacked_themes:
https://github.com/BenPoell/get_it_provider

and I have this
@StackedApp(   routes: [     MaterialRoute(page: StartUpView, initial: true),     MaterialRoute(page: DashboardView),     MaterialRoute(page: SignUpFormView),     MaterialRoute(page: BusinessHomeView),     MaterialRoute(page: LoginView),   ],   dependencies: [     LazySingleton(classType: NavigationService),     LazySingleton(classType: LoginViewModel)   ], ) class AppSetup {   /** Serves no purpose besides having an annotation attached to it */ }


Fix postgres schema dumping in 1.x when using case_sensitive => false and operator_class together

Fixes a bug whereby a migration line like:
add_index :users, :name, :case_sensitive => false, :operator_class => 'text_pattern_ops', :name => :usernamelower

migrates properly, but results in a schema.rb line like:
t.index ["name"], :name => "usernamelower", :case_sensitive => false, :operator_class => {nil => "text_pattern_ops"}

which will not load properly.
This will now output the following schema line:
t.index ["name"], :name => "usernamelower", :case_sensitive => false, :operator_class => {'name' => "text_pattern_ops"}

Coverage remained the same at 98.79% when pulling 2c2f28fada1f86968082d8907eb2d67cc7858580 on mikeauclair:operator_classes_dumper into 59ea144db8a6fd83f279163827d9886dc63da086 on SchemaPlus:1.x.

Coverage remained the same at 98.79% when pulling 2c2f28fada1f86968082d8907eb2d67cc7858580 on mikeauclair:operator_classes_dumper into 59ea144db8a6fd83f279163827d9886dc63da086 on SchemaPlus:1.x.

Coverage remained the same at 98.79% when pulling 2c2f28fada1f86968082d8907eb2d67cc7858580 on mikeauclair:operator_classes_dumper into 59ea144db8a6fd83f279163827d9886dc63da086 on SchemaPlus:1.x.

@mikeauclair Great -- thanks!

@mikeauclair FYI I've release version 1.8.7 with this fix in it.


Verifying Network IDs of the callers of received RPCs

There has to be a way for checking who the caller is to act accordingly.
It would be great if it could be done by using a different keyword in place of "remote" for when you want your function to only be executable if the caller has ID equal to 1.

More like, if you have a move function on the master, you want it to be callable from only one client, not all clients (as it currently is). I would go with one of the following syntaxes, though I'm not sure which is "better":
# GH syntax highlight fails me
master(client_id) func idea_one(param1, param2):
  if can_be_affected_by(client_id): # Checked by your own code
    # do stuff
master func idea_two(param1, param2):
  if can_be_affected_by(get_tree().get_rpc_caller_id()): # Checked by your own code
    # do stuff

I'm not sure of the case where this is needed.

You could just send the unique id of the caller through the rpc function, since your function will be specifically looking for it anyways

master func something(id, param1, param2):
    if(id == 1):
        #do something
func call_something(p1,p2):
    rpc("something",get_tree().get_network_unique_id(),p1,p2)

you could also only ever do that call from the server

if(get_tree().is_network_server()):
   rpc("something")

I personally think it's wiser to make less calls rather than filter the calls after they've been made.

I guess this is not needed to often, but as these are always called from
the main thread, worst case we can add some function lke
get_tree().get_rpc_caller_id()
On Tue, Dec 27, 2016 at 6:34 PM, Leonard Meagher<EMAIL_ADDRESS>wrote:

I'm not sure of the case where this is needed.

You could just send the unique id of the caller through the rpc
function, since your function will be specifically looking for it anyways

master func something(id, param1, param2):
if(id == 1):
#do somethingfunc call_something(p1,p2):
rpc("something",get_tree().get_network_unique_id(),p1,p2)

you could also only ever do that call from the server

if(get_tree().is_network_server()):
rpc("something")
I personally think it's wiser to make less calls rather than filter the
calls after they've been made.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/7362#issuecomment-269385891,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z2_xfG4RVKv6-H9-guDJEuKibkMjZks5rMYRugaJpZM4LVJCm
.

@reduz Well, currently, if you have one server with 2 clients connected, a "bad" client can fully impersonate the other to the underlying server-side GDScript code, that's why it is needed.
Example:
Server scene has:
Node2D (master)
 - player1 - Rigidbody2D (master) [player.gd] # Or slave, but doesn't make much of a difference
 - player2 - Rigidbody2D (master) [player.gd]

Client1's scene has:
Node2D (slave)
 - player1 - Rigidbody2D (slave) [player-local-control.gd]
 - player2 - Rigidbody2D (slave) [player-remote.gd]

Client2's scene has:
Node2D (slave)
 - player1 - Rigidbody2D (slave) [player-remote.gd]
 - player2 - Rigidbody2D (slave) [player-local-control.gd]

Now, while the server can have to connections to each client and fully differenciate between them, it won't prevent any of them to switch the scripts around, and start controlling the other player.
So, if Client2 does get_node("player1").set_script(preload("player-local-control.gd")), then he would be able to control both players at once.

@bojidar-bg This can be closed, as discussed here: #7853 (and merged change above)


Add ability to see and change workload live updates process

See https://xd.adobe.com/view/fd07bd86-2295-4d19-6ec8-d67e1a6654bd-8b36/


registerBeforeSendCallback is not honored all the time

Description
I have setup registerBeforeSendCallback to not send anything (return false) under some conditions. However, this is not being honored at all for some errors such as unhandled android native errors, or ARNs. I keep getting logs sent
bugsnagConf.registerBeforeSendCallback(function(report, error) {
  console.warn("bugsnag report: ", report, error)
  if (conf.env === 'dev'){
    console.warn("Bugsnag error not sent: ", report, error)
    return false;
  }
})

The above code is not called at all for ARNs. It is still called for test code such as bugsnag.notify(new Error("TEST ERROR HELLO"));
Do I need to do something else to prevent messages from being sent?
Environment
Library versions:
"bugsnag-react-native": "2.18.0",
"react": "16.8.6",
"react-native": "^0.59.5",
Android 8.1 (Moto G5) / Android 9 (Google Pixel 2) / IOS Simulator (12.x)

Unhandled errors are also sent while debugging, pretty annoying.

Any way at all to completely prevent bugsnag from sending native unhandled errors to the server? It is becoming very tiresome to see errors there from local development.

Hi @cristianoccazinsp
There are issues with how some config options are passed between bugsnag-react-native and the underlying bugsnag-android library used for native crashes. We're currently working on some significant improvements to bugsnag-react-native in which we're hoping to address many of these issues.
For the time being to prevent unhandled android native errors from being sent, you can also include the logic a callback in the bugsnag-android layer as described here:
https://docs.bugsnag.com/platforms/android/ndk/customizing-error-reports/#customizing-native-crash-reports
See also:
https://docs.bugsnag.com/platforms/react-native/react-native/enhanced-native-integration/#further-configuration
If you have any issues getting this to work I'd suggest contacting Bugsnag support where we can discuss specifics.
Thanks
Matt

Thinking about it, if all you're trying to do is disable sending errors in development, you don't need to implement a beforeSend callback at all.
You can just ensure that your release stages are configured correctly and use the notifyReleaseStages config option to list which environments you want to enable error notifications for:
https://docs.bugsnag.com/platforms/react-native/react-native/configuration-options/#notifyreleasestages

That might be a better option I guess, although errors will still be sent
right?
Modifying both the IOS and Android layers might be troublesome since I will
need to ensure they are properly configured back for release versions. I
was really hoping for the onSendCallback to solve this kind of setup.
Is there any other hard setting that can be used from the JS side to
disable all logging? I believe some JS setting are already being sent to
the native layer, so it would be good to have any other native setting
exposed to the JS layer.
El vie., 24 de mayo de 2019 07:55, Matt Young<EMAIL_ADDRESS>escribió:

Thinking about it, if all you're trying to do is disable sending errors in
development, you don't need to implement a beforeSend callback at all.
You can just ensure that your release stages are configured correctly and
use the notifyReleaseStages config option to list which environments you
want to enable error notifications for:
https://docs.bugsnag.com/platforms/react-native/react-native/configuration-options/#notifyreleasestages
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bugsnag/bugsnag-react-native/issues/354?email_source=notifications&email_token=ALU263BY3GR4JUUTE5GJVVDPW7CRPA5CNFSM4HL3VV52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWE5SIY#issuecomment-495573283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALU263DHLSRLUCJUIIYGYH3PW7CRPANCNFSM4HL3VV5Q
.

If you use notifyReleaseStages errors would only be sent for the release stages you list, e.g. you could configure this to send production but not development.
To disable all logging just set autoNotify = false:
https://docs.bugsnag.com/platforms/react-native/react-native/configuration-options/#autonotify

Got it. I guess I can just use autoNotify = false if running locally. I
will come back if I see that errors are still being sent from the native
code even with this setting on. Thanks!
On Fri, May 24, 2019 at 11:16 AM Matt Young<EMAIL_ADDRESS>wrote:

If you use notifyReleaseStages errors would only be sent for the release
stages you list, e.g. you could configure this to send production but not
development.
To disable all logging just set autoNotify = false:
https://docs.bugsnag.com/platforms/react-native/react-native/configuration-options/#autonotify
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bugsnag/bugsnag-react-native/issues/354?email_source=notifications&email_token=ALU263FDXSSQIOTLCTPWCATPW72E3A5CNFSM4HL3VV52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWFQBRA#issuecomment-495648964,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALU263CW5DTXDCKFYYIKYEDPW72E3ANCNFSM4HL3VV5Q
.


Automatically create chips for email

Is your feature request related to a problem? Please describe.
While adding members or mentors to the group, we have to input emails separated by coma(,) to make it more visual, we can show chips for each email.
Describe the solution you'd like
For context you can see this package flutter_chip_input.
Are you working on this? (Yes/No)

Hi @aman-singh7 I would like to contribute on this issue, can you please assign this issue to me.

@aman-singh7

@anuragrao04, you can start working if someone doesn't show any update on the assigned issue in a week. He will be unassigned.

Thanks! can you please assign me this issue on the 19th of this month? I will have my exam week from the 14th to the 18th of November. I would still try to work on the issue during this period though. If anybody wants to work on the issue during this period, they can be assigned and I will not be blocking the issue. I will ping back here on the 19th as a reminder :)

I am working on this issue.

@aman-singh7 can you please checkout the latest pr?


[libcopp]Update to version 1.4.1

Describe the pull request

What does your PR fix?
Fixes #18424

Which triplets are supported/not supported? Have you updated the CI baseline?

all

Does your PR follow the maintainer guide?

yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

yes
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Awesome, thanks so much for the update PR and for making a great library!


Remove Metro from the boycott list

Hello,
I just saw while looking at the site that Metro is also listed. They support Ukraine with food and fonds. So please do better research in the future before blacklisting such huge companies.
You can also look here:

https://www.metro.de/service/ukraine
https://www.metroag.de/westandwithukraine

Best greetings from germany.

@vshymanskyy is the man to decide.

Thanks for pinging, I missed this issue!

Done

Sorry, it took so long...


Update change in Gym website

I add a footer where are link of social media and small details of website
I fixed issue #69
Fully responsive footer
Here some images -

@Sanju-github002 can you make some chages

Background image should not repeat
change the heading "Aj ka gym" to some cool heading you like

@Sanju-github002 can you make some chages

Background image should not repeat
change the heading "Aj ka gym" to some cool heading you like

okay I do this changes and make new PR

@Sanju-github002 u always don't need to make a new PR for changes , u can update within this from next time

@Sanju-github002 u always don't need to make a new PR for changes , u can update within this from next time

Yaaa maam sorry but I don't know this 😅 next time I will take care of this.


Fix crash when creating a new shader

From the main menu, Shader Graph -> New Shader crashes with a null pointer exception.
This commit ensures that ShaderProject$ProjectData.projectMetadata is instantiated before trying to write to it, allowing a new shader to be created via the menu.

Thanks!


Is there a preferred way to suggest missing hosts?

I noticed one of the tracking companies started using a different domain than they did before. It is not on your list right now.
Is there a preferred way to suggest that host for inclusion, or should I just make a pull request? If so - are there any requirements (e.g. specific branch, comments, etc.)?
Checked the wiki and the existing issues.

Hi Alex @mehov, we're mostly an aggregator of existing lists so, ideally, the submission should be made with one of these providers.
However it's also OK to fork this repo, add the domain(s) to my ad-hoc list which is in the StevenBlack data folder.  From there, I'll entertain a pull request.


Move seed garbage collection to seed-care, ignore stale Pods when checking for updated Deployments

How to categorize this PR?

/area ops-productivity
/kind enhancement
What this PR does / why we need it:
This PR addresses the concerns mentioned in #10476:

Stale Pods (e.g., those still existing in Evicted or other stale statuses) are ignored when checking whether a Deployment rollout succeeded (i.e., whether all Pods belonging to older ReplicaSets have been terminated).
For legacy reasons, the seed garbage collection was part of shoot-care controller. Hence, it was only active in shoot namespaces in the seed cluster. Now, we have moved this part to the seed-care controller. It will be active in all namespaces in the seed except for kube-system. If the seed is a managed seed (i.e., a shoot cluster), then the still existing garbage collection in the shoot-care controller will take care of it. If it is an unmanaged seed, it is out of the responsibility of gardenlet.

When checking whether a `Deployment` rollout is complete, stale `Pod`s are now ignored and no longer counted.

/assign


arm GCC does not support armv8-m with 0.9.5

Hi,
When I porting zephyr to arm-v8m chip, it seems the Zephyr SDK(0.9.5) does not support this architecture at present.
arm-zephyr-eabi-gcc: error: unrecognized argument in option ‘-march=armv8-m.main’
arm-zephyr-eabi-gcc: note: valid arguments to ‘-march=’ are: armv2 armv2a armv3 armv3m armv4 armv4t armv5 armv5e armv5t armv5te armv6 armv6-m armv6j armv6k armv6kz armv6s-m armv6t2 armv6z armv6zk armv7 armv7-a armv7-m armv7-r armv7e-m armv7ve armv8-a armv8-a+crc armv8.1-a armv8.1-a+crc iwmmxt iwmmxt2 native
make[3]: *** [zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj] Error 1

We can use 3rd party tool chain as a workaround, which is works for me.
https://docs.zephyrproject.org/latest/getting_started/toolchain_3rd_party_x_compilers.html#gnu-arm-embedded


Use of undeclared type 'SwiftAvatar'

I have integrated it through Pod and imported the module, but for an known reason that error is what I get
Use of undeclared type 'SwiftAvatar'

Sorry for the late answer but I'm pretty sure that you figure out that you missed the y in SwiftyAvatar


Opening Multiple USB Grizzlies

I have had trouble with this.
Here's what I found:
http://nbviewer.ipython.org/urls/gist.githubusercontent.com/andrewjchen/b2bcf77290420a144c85/raw/c6996b1738cf8fbb7299e93c5a679e2a494de932/Multiple USB Grizzlies.ipynb

At some point, the fact that PiER implemented motor number as (0x0F - address) should be documented. I have no idea why it was done that way.


Issue #1569: implement runtime check for the LLVM locale bug

Can we consolidate the description of the bug and workaround into the docs?  I'd rather not have someone wade through the discussion in the issue tracker to find out what to do.

Ok, I've added a FAQ entry and redirected the URL in the error there.


Airdrop without burn

We can also do an airdrop without burning sats. Such an airdrop must have a maximum amount of runes claimed per transaction such that the it cannot exceed the supply, even if all transactions from the etching to the block height in which the airdrop concludes were mints.

Closing in favor of #54. Covers mins w and w/o burn.


sgminer Error： Initialising kernel skunkhash.cl with nfactor 10, n 1024

gminer 5.3.3 - Started: [2017-08-22 13:18:00] - [0 days 00:00:40]
(5s):4.599M (avg):4.146Mh/s | A:0 R:0 HW:11 WU:0.000/m
ST: 1 SS: 0 NB: 1 LW: 49 GF: 0 RF: 0
Connected to sigt.pool.mn (stratum) diff 0.004 as user aipame.w2
Block: 6df3100e... Diff:14.5K Started: [13:18:00] Best share: 0
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 81.0C 9999RPM | 441.5K/497.6Kh/s | R: 0.0% HW:2 WU:0.000/m I:20
GPU 1: 78.0C 3083RPM | 3.407M/3.759Mh/s | R: 0.0% HW:10 WU:0.000/m I:20
[13:17:54] Started sgminer 5.3.3
[13:17:54] * using Jansson 2.10
[13:17:55] Probing for an alive pool
[13:17:56] sigt.pool.mn difficulty changed to 0.004
[13:17:58] Startup GPU initialization... Using settings from pool sigt.pool.mn.
[13:17:58] Startup Pool No = 0
[13:17:59] Initialising kernel skunkhash.cl with nfactor 10, n 1024
[13:17:59] Initialising kernel skunkhash.cl with nfactor 10, n 1024

You failed to mention what GPU is this.

My GPU is AMD R9280X

а как его указать ?