generate_presigned_url for put_bucket_cors results in invalid signature

Describe the bug
Generating a presigned URL for the put_bucket_cors method results in a signature that AWS reports as "SignatureDoesNotMatch"
Expected Behavior
The signature should match and the method succeed.
Current Behavior
The request to AWS fails with the response text shown below (some text has been replaced with REDACTED).
Note the end of StringToSign which has "/test-bucket/?cors". The error text shown further below shows that botocore is using "/test-bucket?cors?cors" instead!
<?xml version="1.0" encoding="UTF-8"?>
<Error>SignatureDoesNotMatch<Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>REDACTED</AWSAccessKeyId><StringToSign>PUT
6ExFvI55ofqo42RutDlTDg==

1685543937
x-amz-security-token:REDACTED
/test-bucket/?cors</StringToSign><SignatureProvided>REDACTED</SignatureProvided><StringToSignBytes>REDACTED</StringToSignBytes><RequestId>REDACTED</RequestId><HostId>REDACTED</HostId></Error>

The full output (with some text REDACTED) for the test code is:
2023-05-31 14:38:57,176 botocore.hooks [DEBUG] Changing event name from creating-client-class.iot-data to creating-client-class.iot-data-plane
2023-05-31 14:38:57,177 botocore.hooks [DEBUG] Changing event name from before-call.apigateway to before-call.api-gateway
2023-05-31 14:38:57,177 botocore.hooks [DEBUG] Changing event name from request-created.machinelearning.Predict to request-created.machine-learning.Predict
2023-05-31 14:38:57,178 botocore.hooks [DEBUG] Changing event name from before-parameter-build.autoscaling.CreateLaunchConfiguration to before-parameter-build.auto-scaling.CreateLaunchConfiguration
2023-05-31 14:38:57,178 botocore.hooks [DEBUG] Changing event name from before-parameter-build.route53 to before-parameter-build.route-53
2023-05-31 14:38:57,179 botocore.hooks [DEBUG] Changing event name from request-created.cloudsearchdomain.Search to request-created.cloudsearch-domain.Search
2023-05-31 14:38:57,179 botocore.hooks [DEBUG] Changing event name from docs.*.autoscaling.CreateLaunchConfiguration.complete-section to docs.*.auto-scaling.CreateLaunchConfiguration.complete-section
2023-05-31 14:38:57,180 botocore.hooks [DEBUG] Changing event name from before-parameter-build.logs.CreateExportTask to before-parameter-build.cloudwatch-logs.CreateExportTask
2023-05-31 14:38:57,180 botocore.hooks [DEBUG] Changing event name from docs.*.logs.CreateExportTask.complete-section to docs.*.cloudwatch-logs.CreateExportTask.complete-section
2023-05-31 14:38:57,180 botocore.hooks [DEBUG] Changing event name from before-parameter-build.cloudsearchdomain.Search to before-parameter-build.cloudsearch-domain.Search
2023-05-31 14:38:57,180 botocore.hooks [DEBUG] Changing event name from docs.*.cloudsearchdomain.Search.complete-section to docs.*.cloudsearch-domain.Search.complete-section
2023-05-31 14:38:57,182 botocore.utils [DEBUG] IMDS ENDPOINT: http://<IP_ADDRESS>/
2023-05-31 14:38:57,183 botocore.credentials [DEBUG] Looking for credentials via: env
2023-05-31 14:38:57,183 botocore.credentials [DEBUG] Looking for credentials via: assume-role
2023-05-31 14:38:57,183 botocore.credentials [DEBUG] Looking for credentials via: assume-role-with-web-identity
2023-05-31 14:38:57,183 botocore.credentials [DEBUG] Looking for credentials via: sso
2023-05-31 14:38:57,183 botocore.credentials [DEBUG] Looking for credentials via: shared-credentials-file
2023-05-31 14:38:57,183 botocore.credentials [DEBUG] Looking for credentials via: custom-process
2023-05-31 14:38:57,766 botocore.loaders [DEBUG] Loading JSON file: /home/philipn/cors_issue/venv/lib/python3.10/site-packages/botocore/data/endpoints.json
2023-05-31 14:38:57,785 botocore.loaders [DEBUG] Loading JSON file: /home/philipn/cors_issue/venv/lib/python3.10/site-packages/botocore/data/sdk-default-configuration.json
2023-05-31 14:38:57,786 botocore.hooks [DEBUG] Event choose-service-name: calling handler <function handle_service_name_alias at 0x7fb0a77fbb50>
2023-05-31 14:38:57,790 botocore.loaders [DEBUG] Loading JSON file: /home/philipn/cors_issue/venv/lib/python3.10/site-packages/botocore/data/s3/2006-03-01/service-2.json
2023-05-31 14:38:57,801 botocore.loaders [DEBUG] Loading JSON file: /home/philipn/cors_issue/venv/lib/python3.10/site-packages/botocore/data/s3/2006-03-01/endpoint-rule-set-1.json.gz
2023-05-31 14:38:57,805 botocore.loaders [DEBUG] Loading JSON file: /home/philipn/cors_issue/venv/lib/python3.10/site-packages/botocore/data/partitions.json
2023-05-31 14:38:57,806 botocore.hooks [DEBUG] Event creating-client-class.s3: calling handler <function add_generate_presigned_post at 0x7fb0a7764160>
2023-05-31 14:38:57,806 botocore.hooks [DEBUG] Event creating-client-class.s3: calling handler <function lazy_call.<locals>._handler at 0x7fb0a747e170>
2023-05-31 14:38:57,816 botocore.hooks [DEBUG] Event creating-client-class.s3: calling handler <function add_generate_presigned_url at 0x7fb0a775beb0>
2023-05-31 14:38:57,817 botocore.endpoint [DEBUG] Setting s3 timeout as (60, 60)
2023-05-31 14:38:57,818 botocore.loaders [DEBUG] Loading JSON file: /home/philipn/cors_issue/venv/lib/python3.10/site-packages/botocore/data/_retry.json
2023-05-31 14:38:57,818 botocore.client [DEBUG] Registering retry handlers for service: s3
2023-05-31 14:38:57,818 botocore.utils [DEBUG] Registering S3 region redirector handler
2023-05-31 14:38:57,819 botocore.hooks [DEBUG] Event before-parameter-build.s3.PutBucketCors: calling handler <function validate_bucket_name at 0x7fb0a7821240>
2023-05-31 14:38:57,819 botocore.hooks [DEBUG] Event before-parameter-build.s3.PutBucketCors: calling handler <function remove_bucket_from_url_paths_from_model at 0x7fb0a7823010>
2023-05-31 14:38:57,819 botocore.hooks [DEBUG] Event before-parameter-build.s3.PutBucketCors: calling handler <bound method S3RegionRedirectorv2.annotate_request_context of <botocore.utils.S3RegionRedirectorv2 object at 0x7fb0a695a6e0>>
2023-05-31 14:38:57,819 botocore.hooks [DEBUG] Event before-parameter-build.s3.PutBucketCors: calling handler <function generate_idempotent_uuid at 0x7fb0a7821090>
2023-05-31 14:38:57,819 botocore.hooks [DEBUG] Event before-endpoint-resolution.s3: calling handler <function customize_endpoint_resolver_builtins at 0x7fb0a78231c0>
2023-05-31 14:38:57,819 botocore.hooks [DEBUG] Event before-endpoint-resolution.s3: calling handler <bound method S3RegionRedirectorv2.redirect_from_cache of <botocore.utils.S3RegionRedirectorv2 object at 0x7fb0a695a6e0>>
2023-05-31 14:38:57,819 botocore.regions [DEBUG] Calling endpoint provider with parameters: {'Bucket': 'test-bucket', 'Region': 'aws-global', 'UseFIPS': False, 'UseDualStack': False, 'ForcePathStyle': False, 'Accelerate': False, 'UseGlobalEndpoint': True, 'DisableMultiRegionAccessPoints': False, 'UseArnRegion': True}
2023-05-31 14:38:57,819 botocore.regions [DEBUG] Endpoint provider result: https://test-bucket.s3.amazonaws.com
2023-05-31 14:38:57,819 botocore.regions [DEBUG] Selecting from endpoint provider's list of auth schemes: "sigv4". User selected auth scheme is: "None"
2023-05-31 14:38:57,819 botocore.regions [DEBUG] Selected auth type "v4" as "v4" with signing context params: {'region': 'us-east-1', 'signing_name': 's3', 'disableDoubleEncoding': True}
2023-05-31 14:38:57,820 botocore.hooks [DEBUG] Event choose-signer.s3.PutBucketCors: calling handler <bound method ClientCreator._default_s3_presign_to_sigv2 of <botocore.client.ClientCreator object at 0x7fb0a749a110>>
2023-05-31 14:38:57,820 botocore.hooks [DEBUG] Event before-sign.s3.PutBucketCors: calling handler <function remove_arn_from_signing_path at 0x7fb0a7823130>
2023-05-31 14:38:57,820 botocore.auth [DEBUG] Calculating signature using hmacv1 auth.
2023-05-31 14:38:57,820 botocore.auth [DEBUG] HTTP request method: PUT
2023-05-31 14:38:57,820 botocore.auth [DEBUG] StringToSign:
PUT
6ExFvI55ofqo42RutDlTDg==

1685543937
x-amz-security-token:REDACTED
/test-bucket?cors?cors
2023-05-31 14:38:57,822 urllib3.connectionpool [DEBUG] Starting new HTTPS connection (1): test-bucket.s3.amazonaws.com:443
2023-05-31 14:38:58,239 urllib3.connectionpool [DEBUG] https://test-bucket.s3.amazonaws.com:443 "PUT /?cors&AWSAccessKeyId=REDACTED&Signature=REDACTED&x-amz-security-token=REDACTED&Expires=1685543937 HTTP/1.1" 307 None
2023-05-31 14:38:58,245 urllib3.connectionpool [DEBUG] Starting new HTTPS connection (1): test-bucket.s3-eu-west-1.amazonaws.com:443
2023-05-31 14:38:58,471 urllib3.connectionpool [DEBUG] https://test-bucket.s3-eu-west-1.amazonaws.com:443 "PUT /?cors&AWSAccessKeyId=REDACTED&Signature=REDACTED&x-amz-security-token=REDACTED&Expires=1685543937 HTTP/1.1" 403 None
2023-05-31 14:38:58,494 charset_normalizer [DEBUG] Encoding detection: utf_8 is most likely the one.
<?xml version="1.0" encoding="UTF-8"?>
<Error>SignatureDoesNotMatch<Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>REDACTED</AWSAccessKeyId><StringToSign>PUT
6ExFvI55ofqo42RutDlTDg==

1685543937
x-amz-security-token:REDACTED
/test-bucket/?cors</StringToSign><SignatureProvided>REDACTED</SignatureProvided><StringToSignBytes>REDACTED</StringToSignBytes><RequestId>REDACTED</RequestId><HostId>REDACTED</HostId></Error>

Reproduction Steps
The code copied below can be used to reproduce the error and includes a hack to "fix" it The code generates a presigned URL and then makes a request. The MODIFY_FUNC variable toggles a "fix" in the botocore.signers.generate_presigned_url() function to get it to work.
The code assumes that there exists a bucket named "test-bucket" in the "eu-west-1" region. The name and region can be changed as required.
Set MODIFY_FUNC = False to see the request failing Set it to MODIFY_FUNC = True to see the test passing.
import boto3
import requests
import hashlib
import base64
import sys

BUCKET_NAME = "test-bucket"
PROFILE_NAME = None
REGION_NAME = "eu-west-1"
ENDPOINT_URL = None
DEBUG_OUTPUT = True

MODIFY_FUNC = False

# This modifies the code from botocore.signers.generate_presigned_url() to
# change the "auth_path" in the request dict from "/{BUCKET_NAME}?cors" to "/{BUCKET_NAME}/"
def modify_generate_presigned_url(client):
    from botocore.exceptions import UnknownClientMethodError
    from botocore.utils import ArnParser

    def _should_use_global_endpoint(client):
        if client.meta.partition != 'aws':
            return False
        s3_config = client.meta.config.s3
        if s3_config:
            if s3_config.get('use_dualstack_endpoint', False):
                return False
            if (
                s3_config.get('us_east_1_regional_endpoint') == 'regional'
                and client.meta.config.region_name == 'us-east-1'
            ):
                return False
        return True

    def mod_generate_presigned_url(ClientMethod, Params=None, ExpiresIn=3600, HttpMethod=None):
        client_method = ClientMethod
        params = Params
        if params is None:
            params = {}
        expires_in = ExpiresIn
        http_method = HttpMethod
        context = {
            'is_presign_request': True,
            'use_global_endpoint': _should_use_global_endpoint(client),
        }

        request_signer = client._request_signer

        try:
            operation_name = client._PY_TO_OP_NAME[client_method]
        except KeyError:
            raise UnknownClientMethodError(method_name=client_method)

        operation_model = client.meta.service_model.operation_model(operation_name)
        params = client._emit_api_params(
            api_params=params,
            operation_model=operation_model,
            context=context,
        )
        bucket_is_arn = ArnParser.is_arn(params.get('Bucket', ''))
        endpoint_url, additional_headers = client._resolve_endpoint_ruleset(
            operation_model,
            params,
            context,
            ignore_signing_region=(not bucket_is_arn),
        )

        request_dict = client._convert_to_request_dict(
            api_params=params,
            operation_model=operation_model,
            endpoint_url=endpoint_url,
            context=context,
            headers=additional_headers,
            set_user_agent_header=False,
        )

        # MODIFICATION
        print(f"Changing auth_path in request_dict from '{request_dict['auth_path']}' to '{'/' + BUCKET_NAME + '/'}'")
        request_dict["auth_path"] = "/" + BUCKET_NAME + "/"

        # Switch out the http method if user specified it.
        if http_method is not None:
            request_dict['method'] = http_method

        # Generate the presigned url.
        return request_signer.generate_presigned_url(
            request_dict=request_dict,
            expires_in=expires_in,
            operation_name=operation_name,
        )

    client.generate_presigned_url = mod_generate_presigned_url

def test():
    if DEBUG_OUTPUT:
        boto3.set_stream_logger('')

    session = boto3.Session(profile_name=PROFILE_NAME)
    client = session.client(
        "s3",
        endpoint_url=ENDPOINT_URL,
        region_name=REGION_NAME
    )
    if MODIFY_FUNC:
        modify_generate_presigned_url(client)

    cors_xml = """\
<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
   <CORSRule>
      <AllowedMethod>GET</AllowedMethod>
      <AllowedOrigin>*</AllowedOrigin>
   </CORSRule>
</CORSConfiguration>
"""
    cors_data = cors_xml.encode('utf-8')
    cors_data_md5 = base64.b64encode(hashlib.md5(cors_data).digest()).decode('utf-8')

    cors_presigned_url = client.generate_presigned_url(
        'put_bucket_cors',
        Params={
            'Bucket': BUCKET_NAME,
            'CORSConfiguration': {
                'CORSRules': [
                    {
                        'AllowedMethods': ['GET'],
                        'AllowedOrigins': ['*']
                    }
                ]
            },
            'ContentMD5': cors_data_md5
        },
        ExpiresIn=3600
    )

    cors_headers = {
        "Content-Length": str(len(cors_data)),
        "Content-MD5": cors_data_md5
    }
    resp = requests.put(
        cors_presigned_url,
        data=cors_data,
        headers=cors_headers
    )
    if resp.status_code != 200:
        print(resp.text, file=sys.stderr)

test()

Possible Solution
See the test code. Modifying auth_path property in the request_dict in the botocore.signers.generate_presigned_url() function results a correct StringToSign and it succeeds.
Note however that this is meant as a quick hack and it is unclear what the proper fix should be.
Additional Information/Context
No response
SDK version used
botocore 1.29.143, boto3 1.26.143
Environment details (OS name and version, etc.)
Python 3.10 virtualenv

Hi @philipnbbc thanks for reaching out. Could you share more details on your use case? I'm not sure that generating a presigned url is intended to support the put_bucket_cors command. As mentioned in the boto3 documentation on presigned urls, the main purpose of presigned URLs is to grant a user temporary access to an S3 object. I tried to find similar issues related to the use case you described but was not able to.

Our use case is that we have a service that indexes content in S3 and provides information that clients can use to read and write content directly to S3 using pre-signed URLs. The pre-signed URLs allow clients to not have AWS credentials and it avoids the service having to handle the object and bucket requests (with retries etc.), becoming a bottleneck in the S3 interactions.

Thanks for following up, I brought this issue up for discussion with the team and think it requires more investigation. Marked this for further review.

It looks like this can now be closed since https://github.com/boto/botocore/pull/2971 was merged.


server.js (main file)

this will serve as the main conductor page for the site

should be good. handles the main connecting routes and models and those are created at the start


Boost-thread: doesn't build in release-only

On travis-ci, the following stanza fails if a release-only build is made.
The compiler version (8 or 9) does not make a difference.
- os: osx
  osx_image: xcode10.2
  compiler: gcc
  env:
    - VCPKG_DIR=${TRAVIS_BUILD_DIR}/vcpkg
  install:
    - brew update && brew unlink gcc && brew install gcc@9 && export CC=gcc-9 CXX=g++-9
    - brew install ninja
    - git clone --depth 1 -b soxr https://github.com/ThijsWithaar/vcpkg.git ${VCPKG_DIR}
    # If this is uncommented, the build fails, otherwise it succeeds
    #- echo "set(VCPKG_BUILD_TYPE release)" >> ${VCPKG_DIR}/triplets/x64-osx.cmake
    - ${TRAVIS_BUILD_DIR}/vcpkg/vcpkg install boost-thread

Duplicated to https://github.com/microsoft/vcpkg/issues/8613


Missing dependecy

It seems you are using edges here, but it is not listed in your dependencies. Building a file with webpack catches this and requires the user to independently install edges in order to user this.

Hi @RileyTomasek,
At this time we are not going to be splitting this compiler into its own package and maintaining it. We also do not want to add the dependency to the package just to support this compiler. I am going to close this issue for now. We will revisit the topic when and if this compiler sees greater use in the community.
Thanks,
Bobby


Implementing a prim type in a class expression should report error

🔎 Search Terms
class expression implement primitive type
🕗 Version & Regression Information

This changed between versions 5.2.2__ and 5.3.3___

⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.3.3#code/MYewdgzgLgBAgjAvDYAbAhhCMBCMCWAtgA6oCmhZYU2YAroQEZkBOMA3gL4BQ3am2AMIES5StVoNmbLkA
💻 Code
class C implements number {} // report that class cannot implement primitive type

const A = class B implements number {} // this code should report the same error, but it actually does not.

🙁 Actual behavior
Refer to the comment above
🙂 Expected behavior
Refer to the comment above
Additional information about the issue
No response

Looks like #55712


fix conditional DETR AP and Log

I'm working together with @jshilong, @Li-Qingyun, and @KeiChiTse to refactor the DETR-like algorithms in MMDetection 3.x, using a more lightweight and easy-to-read code style.
This PR is to fix the AP and Log result in conditional DETR, I update the log from 150 epoch to 50 epoch. And the AP update from 40.9 in original repo to 41.1

https://github.com/LYMDLUT/mmdetection/releases/download/untagged-b75ab9b3b045bbfb5c35/conditional-detr_r50_8xb2-50e_coco_20221121_180202.log.json
This is the 50e log of conditional DETR，please help me to update it to our server

I'm working together with @jshilong, @Li-Qingyun, and @KeiChiTse to refactor the DETR-like algorithms in MMDetection 3.x, using a more lightweight and easy-to-read code style.
This PR is to fix the AP and Log result in conditional DETR, I update the log from 150 epoch to 50 epoch. And the AP update from 40.9 in original repo to 41.1

@hhaAndroid Could you help to update this log file?

@LYMDLUT I have uploaded


How to move weekdays?

In default week start from sunday, but I need start week from monday. How to do this? Thank you.

in your configureCalendar function
let parameters = ConfigurationParameters(startDate: startDate,
                                                 endDate: endDate,
                                                 numberOfRows: numberOfRows,
                                                 calendar: testCalendar,
                                                 generateInDates: generateInDates,
                                                 generateOutDates: generateOutDates,
                                                 firstDayOfWeek: firstDayOfWeek,
                                                 hasStrictBoundaries: hasStrictBoundaries)


Unbound issue with logging and OpenVPN after rebooting OPNsense

Introduction: First I thought I've a problem with Unbound combined with OpenVPN. But after some tests with a completly fresh installed OPNsense in Hyper-V I think this is only an Unbound issue which effects OpenVPN too. Therefore I renamed this opened issue. Sorry for the confusion.
Some basic informations.
Version: 18.7.4
Installed on self-configured hardware (Intel(R) Celeron(R) CPU J1900 @ 1.99GHz (4 cores)) and as Hyper-V VM for tests with an fresh installation
Issue appears: after each reboot of OPNsense
Issue:
I raised the log level verbosity of Unbound from 1 to 2 to get every DNS query logged. I've noticed that when I restart my OPNsense, the logging stoppes or falles back to log level verbosity 1. DNS querys are not logged anymore.
I've to restart the Unbound service to get the logging working as configured in the log level verbosity settings of Unbound.
If this issue happens the DNS resolving for OpenVPN clients only is not working. LAN clients are not affected. They can resolve internal and exteranl DNS names. So I guess Unbound is not completly hanging or stopped. After restarting Unbound the DNS resolving for the OpenVPN clients works fine again.
I've also noticed that after restarting the service the FQDN DNS record of my OPNsense contains the IP address of the management interface, and the IP address of the virtual OpenVPN interface. Therefore when I try to access the WebGUI, and my client resolves the OpenVPN IP for the OPNsense FQDN, I get timeouts and of course a lot of deny entrys in the firewall logs because this interface is not configured for the WebGUI access.

Name:    jaswall.mgmt.home.arpa
Addresses:  <IP_ADDRESS>
<IP_ADDRESS>

The fresh installed OPNsense VM is configured with the basic settings like WAN and LAN interface only. No additional plugins or services are running. But it shows the same behaviour as my productive OPNsense.
I'm not sure if this are two completly different problems, or if an Unbound issue causes this behaviours.

I've installed a new instance of OPNsense in Hyper-V and configured only the needed settings like WAN and LAN interface. Everything worked fine.
Then I've configured an OpenVPN server with the wizzard and rebooted OPNsense. Same behaviour as on my productive appliance:

Unbound stops logging right after start up (last log entry says: unbound: [41353:0] info: start of service (unbound 1.7.3).). I set the loglevel to 2 to get every DNS requested logged. But nothing is shown.

OpenVPN clients are not able to resolve DNS names when using Unbound as DNS server. LAN clients and the OPNsense itself can.

The DNS record of OPNsense contains the IP of the LAN and OpenVPN interface.  Sometimes when I try to access the WebGUI, and my client reloves the OpenVPN IP for the OPNsense FQDN, I get timeouts and of course a lot of deny entrys in the firewall logs.

After restarting the Unbound service logging works fine. I've noticed on my productive appliance that sometimes the logging works fine for two minutes and sometimes for some days.

After this test I'm pretty sure that's not only a configuration problem because as I wrote above, I've configured only the needed settings to get OPNsense running. Unbound and OpenVPN are configured with the standard settings.

@JasMan78 let's start with the verbosity issue. can you verify that /var/unbound/unbound.conf verbosity changes back to 1 after reboot?
# grep verbosity: /var/unbound/unbound.conf

@fichtner The verbosity level is still 2 after a reboot. It looks like the logging of at least Unbound has completely stopped.

does this only happen with verbosity 2 or also 1 ? after reboot+in conjunction with OpenVPN I mean

Also with verbosity 1.
After a reboot the internal and external DNS queries from VPN clients are not answered by Unbound. LAN clients get an answer. When I restart the Unbound service, the DNS resolving for the VPN clients is working again.

I've installed the patch on my VM OPNsense, but same issue after rebooting it.
I'm not sure if the installation was successfull. Here's the output:
# opnsense-patch 2d5d392

Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|From 2d5d392bc2b722ab9f52aeb624d42317a78288fb Mon Sep 17 00:00:00 2001
|From: Franco Fichtner<EMAIL_ADDRESS>|Date: Wed, 17 Oct 2018 17:23:45 +0000
|Subject: [PATCH] unbound: set up a full chroot including local log socket
| #2791
|
|---
| src/etc/inc/plugins.inc.d/unbound.inc | 12 ++++++++++++
| src/etc/inc/system.inc                |  2 +-
| 2 files changed, 13 insertions(+), 1 deletion(-)
|
|diff --git a/src/etc/inc/plugins.inc.d/unbound.inc b/src/etc/inc/plugins.inc.d/unbound.inc
|index 9a3a18589..a15809375 100644
|--- a/src/etc/inc/plugins.inc.d/unbound.inc
|+++ b/src/etc/inc/plugins.inc.d/unbound.inc
--------------------------
Patching file etc/inc/plugins.inc.d/unbound.inc using Plan A...
Hunk #1 succeeded at 431 (offset 13 lines).
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/etc/inc/system.inc b/src/etc/inc/system.inc
|index eb3fa39bc..594525092 100644
|--- a/src/etc/inc/system.inc
|+++ b/src/etc/inc/system.inc
--------------------------
Patching file etc/inc/system.inc using Plan A...
Hunk #1 failed at 693.
1 out of 1 hunks failed--saving rejects to etc/inc/system.inc.rej
done

Indeed, system.inc needs patching. Sorry about the hiccup. Can you manually change it and do another reboot?
https://github.com/opnsense/core/commit/2d5d392bc2b722ab9f52aeb624d42317a78288fb#diff-460dfc2bc3262765b55473c6f9b38003R696
Use this after edit to make sure it boots ok:
# php -l /usr/local/etc/inc/system.inc

No problem, but I don't understand what I should do now or what I should "manually change".

I can send you a working patch if you tell me which version that patch needs.

Now I understand what you want me to do. Of course I can change the files manually. I will try to do it during today or tomorrow. Thank you in advanced for your help.

No worries, thanks for your help.

I've changed the files but the issue remains after reboot.

Sorry, I made a mistake. I tried to resolve a domain via the WebGUIs interface diagnostic tools this time. But as I just noticed those requests are not logged by the Unbound log. I guess they're directly forwarded to the external DNS resolver.
The Unbound logging is fine now after I've changed the files and rebooted OPNsense.

hold on, the subject says "Unbound issue with logging and OpenVPN after rebooting" and that's what was worked on. Did the previous fix it?
If yes, what is the second problem in an isolated manner and wouldn't it be better to create a separate ticket for this to avoid "endless" tickets? :)

Yes, changing the two files fixed the Unbound logging issue. 👍
OK, I understand.
Just want to inform you that the fix had no impact to the other issue(s) I have with Unbound DNS. I will open a new support tickets for this.

Thanks, then I will close and ship the logging fix in 18.7.6 and will take the other issue as soon as it's there :)


#gitleaks:allow doesnt work properly

Describe the bug
I have gitlab project, where intentionally hardcoded some tokens. I've added comment #gitleaks:allow (as you can see on screenshots) and unfortunatelly nothing changed, this token still being detected by gitleaks in my pipeline
To Reproduce
add #gitleaks:allow after any secret in your file
Expected behavior
Token is absent from report
Screenshots

Basic Info (please complete the following information):

OS:
Gitleaks Version:  v8.17.0

What type of scan? gitleaks:allow does not ignore secrets that have been previously committed

so, gitleaks:allow works only for the first commit?
How can I exclude from scan already commited secrets without using .gitleaksignore?
im asking due to the fact, that in .gitleaksignore i have to mention commit/file/type/line
as it shown here:
418edf165dbb63d6f46993ae8f8818ffd87ea582:cmd/generate/config/rules/jwt.go:jwt:17
but the difficulty in this case that code changes ang line can change many times, it means that every time developers should change lines in .gitleaksignore too, thats why idea using #gitleaks:allow seems to me very interesting. Maybe you have any advices to my case? i use gitleaks in my ci/cd pipelines as an additional stage before build.

you gotta use either a .gitleaksignore file or configure your gitleaks.toml with an allowlist to ignore the secret based on a regex.
gitleaks:allow primary use case is for committing secrets that are either for tests or known false positives

Thank you @zricethezav


Same cell for word and sentence level

In worker.py looking at lines 70-80, it seems you are using the same cell for word and sentence level, but it should be a different lstm cell

AFAIR Cell is/was a template/factory, not a layer or parameter container

I think I am getting you. BNLSTMCell is just a declaration of a class. Still when you say call BNLSTMCell.call(), it will still call same set of parameters which are already defined in the graph at word level as they fall in same namescope of defined parameters. So treated as one unique set of parameters, not two (word and sentence).
I am seeing a big performance difference by making this change. ( i am trying in a little more complex problem of multi-class multi-label )
cell_word = BNLSTMCell(40, is_training) # h-h batchnorm LSTMCell
cell = GRUCell(30)
cell_word = MultiRNNCell([cell]*5)
cell_sent = BNLSTMCell(40, is_training) # h-h batchnorm LSTMCell
cell = GRUCell(30)
cell_sent = MultiRNNCell([cell]*5)
Similarly if you expect a different cell for forward and backward then you should define two more cells.
Please correct me if I am wrong.
Other small side thing, according to my understanding, it's a general practice to not to dropout at eval time but it's happening as defined in the code here.

You might be right, my memory of TF's conventions is quite vague at this point.


New React Code Pattern Changes

@seansund  are you able to review this PR, we are about to run a workshop for HCL, and we wanted the latest React Starter Kit(Which already merged into dev branch and requesting for master)  and Inventory-UI to be part of that. Appreciate it


StateChange subclass not part of upstream pysignal project

This is part of the open package review on redhat, to get ouimeaux added to the offical Fedora repos. https://bugzilla.redhat.com/show_bug.cgi?id=1839242
Follow along with me here...
During the review, it was noticed that pysignals was bundled with ouimeaux. I have to unbundle it into it's own package. This was done and a request for a new pysignals package was created:
https://bugzilla.redhat.com/show_bug.cgi?id=1848049
That has lead to the discovery that the bundled pysignals has a custom subclass StateChange, which is not part of the upstream pysignals project.
This subclass was added in commit d2fc9359c8e22e7aabad494cfda6c26fdb54730a .
Technically, I could just patch d2fc9359c8e22e7aabad494cfda6c26fdb54730a into the new pysignals rpm package.
However, I think it would be more appropriate to move the subclass definition out of dispatcher.py to somewhere else in ouimeaux project folder. Let me know your thoughts on this. I am not convinced one way or the other at the moment.

I just thought of a hidden option number 3 - email the author of pysignals and ask for commit access to the (dead) project, with the intent of creating a new release merging py3 compat, statechange subclass, and any other needed goodies.
I'll let you know if I get a response.

@iancmcc Good news. The author of pysignals granted me commit access to the project. I will be generating a new release soon. Feedback can be left here:
https://github.com/theojulienne/PySignals/issues/4

Closing, as all changes are now part of the pysignals project


Router: Better Catch-All (/.*/) Route

The inclusion of a "*notFound" route was a real improvement for Backbone ... but it's not quite perfect.  One major issue is that it has to be the last route defined, which isn't always so simple (eg. if you have multiple routers or routes being manually registered in Required files).  This is enough of a problem in fact that someone went and made a whole plug-in just to deal with it (https://github.com/STRML/backbone.routeNotFound).  Hopefully if you look at that plug-in's source you'll agree that it shouldn't need to exist.
So rather than making the 404 (or "page not found") route something implicit that people have to struggle to get in to the right position, could you please consider adding an explicit Backbone.History.pageNotFound (or something similar) method?
In other words, inside of Backbone.History.loadUrl instead of its current return line:
return matched;

if it did:
return matched || this.pageNotFound();

that would be really great, and super easy.  It'd be a little dirty though, because what's supposed to get returned there is a matching route, not the output of a route, so maybe a slightly cleaner way of doing it would be to have a Backbone.History.registerPageNotFound method and then do:
return matched || this.getRegisteredPageNotFoundRoute();

Or I could see at least a couple other variations; the important thing is just that it would be really awesome if I could say "Backbone do this when there's no route defined" instead of "Backbone, do this if there's no route defined ... but god help me if I say that before all my routes are registered" ;-)

I am facing the same issue. I am using subroutes. I have more than 5 subrouters. what's the solution?


Prisma console(prisma.console.io) with elements overlapping each other.

Bug description

On your prisma console in plans section you have elements overlapping each other.
Check the provided image.
How to reproduce

Expected behavior
No response
Prisma information
Not related to Prisma client schema, models or queries.
Environment & setup
no ref.
Prisma Version
no ref.

Hey @RicardoGEsteves 👋
Thank you for taking the time to raise this issue. 🙏
We have tracked it internally and will resolve it.
I'll mark this GitHub Issue as closed as this repository is for managing issues of Prisma ORM and not for our commercial product Prisma Data Platform.

Hey @RicardoGEsteves 👋
Thank you for taking the time to raise this issue. 🙏
We have tracked it internally and will resolve it.
I'll mark this GitHub Issue as closed as this repository is for managing issues of Prisma ORM and not for our commercial product Prisma Data Platform.

@nurul3101 For future issues or bugs with console.prisma.io where should I report it? I mean in which repo?

@RicardoGEsteves We do not have a public repository for Prisma Data Platform (console.prisma.io). You can report issues in our Discord or send an email to<EMAIL_ADDRESS>

@RicardoGEsteves We do not have a public repository for Prisma Data Platform (console.prisma.io). You can report issues in our Discord or send an email to<EMAIL_ADDRESS>
Ok, thanks for your reply.


Create new Kill Selection for Rescaling

So far the oldest tasks are killed for scaling down. We should provide a selection for the youngest.

Closed by https://github.com/mesosphere/marathon/commit/2fe2c85a169b1bc5ff01ce01de638e6d8167142e


Dynamic advanced links list

This PR allows to retrieves the available advanced links dynamically, using a rest API.

adds a rest API handler
removes the default categories from AdvancedLinkingChoices in favor to the one get from API

@brichet is it ready for review?

@brichet is it ready for review?

Yes

Check link is binder being down, we can ignore

Thanks @martinRenou for rebasing it


UI add icons to host for declareHostAsDegraded and cancelHostAsDegraded

ISSUE TYPE

Improvement Request

COMPONENT NAME

UI

CLOUDSTACK VERSION

<IP_ADDRESS>

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

When a host is in state 'Alert' or 'Disconnected' you are able to degrade a host via api call declareHostAsDegraded. It would be nice to have this action as an icon (button) on the host page in the UI. To get a host out of degraded state it would be nice to have an icon (button) using api call cancelHostAsDegraded.
More info on those api calls: API-call to declare host as Degraded
STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

Fixed with #8327


Cooperativity parameter matters for update_reactions but not for update_species

I'm looking at the One_Step_Cooperative_Binding(Mechanism) mechanism, and I can see that in update_reactions() the default value of cooperativity is None, but in update_species the default value is 1. This creates the wrong species for the reactions if you want to change the cooperativity in the component rather than in the mechanism.

Fixed and pushed to master. Thanks for catching this


Updating the readme for the generator guide

Closes #97

Coverage increased (+0.01%) to 97.222% when pulling bf79a85210af131434699f78fa32de2c83f9fe20 on generator-readme into 0e6364ee200c4c4fb02534049904585ae1b54dfe on master.


WIP: Improve _Brain memory footprint

This PR follows https://github.com/mne-tools/mne-python/pull/7927#issuecomment-658737474 and uses various solutions to decrease memory consumption:

[x] Avoid duplication of hemi init meshes by re-using the scene vtkActor
[ ] Avoid duplication of hemi data by re-using the scene vtkActor
[ ] Store normals to avoid unnecessary computation and waste of memory

Feel free to comment on this @larsoner

Also how many data can we have on a hemi? I would like to avoid duplication for that too so I'll go ahead with the naive solution next.

Waiting for the first CI report then I'll push again.

Store normals to avoid unnecessary computation and waste of memory

These should already live in self.geo[hemi].nn, if not then load_geometry should be updated to add it using mne.surface._compute_normals

Also how many data can we have on a hemi? I would like to avoid duplication for that too so I'll go ahead with the naive solution next.

Eventually we will want to support having multiple data overlaid, possibly with different colormaps (?), but we probably need to refactor quite a bit to support it anyway

Running mayavi on this PR (should be the same as master):
MNE_3D_BACKEND=mayavi BUILD_DEV_HTML=1 mprof run sphinx-build -D plot_gallery=1 -D sphinx_gallery_conf.filename_pattern=source_space_snr -b html -d _build/doctrees  -nWT --keep-going . _build/html

I get:

Adding time_viewer=False, show_traces=False (to make it more equivalent) and MNE_3D_BACKEND=pyvista I get something very similar:

On this PR it looks like memory is reduced (hooray!), but only by a few hundred MB (better than nothing):

Removing the time_viewer=False, show_traces=False (implicitly thus setting them to True) we then get the monster:

So it must be something about these options. Let's try show_traces=False, time_viewer=True (good!):

And then show_traces=True, time_viewer=False (also good, must be because show_traces has no effect when time_viewer=False):

@GuillaumeFavelier it seems that the problem is really having both of these enabled at once, which means it's something about how we do show_traces=True I wonder if it's the matplotlib callbacks or something... In any case, how about this plan:

You sort out the actor/data reuse in this PR, and we merge it (the few hundred MB savings are worth it already, and orthogonal to the memory usage issue)
we make a new PR to make show_traces=True, time_viewer=False raise an error (currently you have to have time_viewer=True to have show_traces actually work)
deal with the show_traces+time_viewer problem in another PR
I add a _MNE_BRAIN_TIME_VIEWER_AUTO=false to CircleCI that will be respected by _check_time_viewer_compatibility in the meantime -- it will allow us to get nice traces on our plots in #7927 while we work on the show_traces+time_viewer problem

Never mind that last point, it doesn't make any sense. I'll work on looking into the show_traces mem problem...

I think I found the circular ref, it was passing the times and act_data[vert_idx] to mpl_canvas.plot, which created a nasty circular reference. Passing times.copy() and act_data[vert_idx].copy() seems to fix things. Will push to #7927

Other huge memory blowup is actually storing self.act_data[hemi] = smooth_mat.dot(act_data), i.e., full-resolution data (!). We shouldn't need to do this and can just smooth_mat[idx].dot as needed

oh boy...

While messing with this, I notice this in testing:
15.11s call     mne/viz/tests/test_3d.py::test_plot_alignment[pyvista]
8.61s call     mne/viz/tests/test_3d.py::test_plot_alignment[mayavi]

PyVista is much slower for plot_alignment. It's possible that this is because of the normal computation. We should be able to pass our own computed nn directly to renderer.mesh(..., normals=nn) to avoid this.
Basically I think every call to renderer.mesh(...) in our codebase should pass normals and (in PyVista) set smooth_shading=False. I'll add it to the todo, but we can remove if you disagree.

In the current state, we're close to the goal but I'm not too sure about the memory gain anymore, I need to run mprof. Also smooth shading was already disabled by default for renderer.mesh().
At least we don't re-create a PolyData when possible and use the given normals data.

Also smooth shading was already disabled by default for renderer.mesh().

Yes, we passed smooth_shading=False to PyVista. This fixed some VTK segfault bug, but introduced a nasty visual regression in that the surfaces were not smooth shaded anymore.
In this PR, because we provide the normals directly/manually, the surfaces should be smooth shaded now. Are they?

When the normals parameter is passed to mesh(), the infos are used to allow Phong smooth shading.

Great, Phong is back! Thanks @GuillaumeFavelier


split functionality into subcommands

The argparse package provides functionality for sub-commands, which I would like to implement, so that I could do stuff like
python -m lyscripts thermoint --args

and stuff like that. Essentially similar to how git has many subcommands.

Fixed by 62468c5e3d6a011a00238b79960b367e49780365


Using prodigal-gv results as input to pharokka

I have run Prodigal-gv on my genomes separately with default parameters and using meta.
Can the predicted ORF files (.faa) be given directly to the Pharokka instead of running it from scratch with Fasta files?

Hi @Fazel-AVB
Yes - you can use pharokka_proteins.py. Let me know if you have any trouble.
George

Hi George,
thank you for your reply.
This is the command I am using to run the pharokka_proteins.py for one of my protein files: pharokka_proteins.py -i /usr/users/f.amirvahedibonab01/Thesis/phageScopedata/phage_downloads/Rawdata/spacedust_inputs/1_ORFs.faa -o /usr/users/f.amirvahedibonab01/Thesis/phageScopedata/phage_downloads/Processed_data/annotated_genomes_pharokka -d /usr/users/f.amirvahedibonab01/Thesis/phageScopedata/software/pharokka_db/pharokka_v1.4.0_databases -t 4 -f
However, it says the Dnaapler version is wrong!

my pharokka's version is 1.6.1. Looking at the release history I couldn't find any recommendation regarding the version of the compatible dnaapler.

Hi @Fazel-AVB ,
I'd recommend upgrading pharokka to v1.7.4 (the latest version) - v1.6.1 is a year old now. Alternatively, you can downgrade dnaapler to v0.7.3 (or any version below v1) which should fix the issue too.
George

Hi George,
Thank you for the reply. Now I was wondering if you could give a hint on how to generate gbk files using protein input.
I need these files for plotting reasons and also running Phold.
I found that for gbk creation first create_gff function should be run which receives merged_df and length_df as inputs. I think merge-df is equal to the full_merged_out file resulting from `pharokka_proteins.py', right?

Hi @Fazel-AVB - you can’t really make genbank files from protein input, you will need the original contigs. If you want a genbank from pharokka, just start with the original contigs and run pharokka like normal.
george


Introduce enum, newtype, and :check-docstrings

Fixes #244.

TODO: Break Language Basics into multiple smaller labs.


failed to read data: timed out when run driving_benchmark_example.py --corl-2017

I use carla 0.8.2 when I run manual_control.py from PythonClient it worked fine, but when I want to run driving_benchmark_example.py --corl-2017 I get error :
ERROR: (localhost:2000) failed to read data: timed out
ERROR: (localhost:2000) failed to read data: [WinError 10054] An existing connection was forcibly closed by the remote host
and repeat it self till I close cmd

Ah, this bug is related to https://github.com/carla-simulator/carla/issues/697. This rpclib bug exists in the carla version before 0.9.3.

Hi @AhmdNassar
Has @Johnnyswong answer solved your question?

Ah, this bug is related to #697. This rpclib bug exists in the carla version before 0.9.3.

thank you for your replay, but in #697 he had a problem with client_example.py but it worked fine with me, I have a problem with driving_benchmark_example.py although they used the same port!


[nrf toup] net: openthread: separated variable for rx/tx operations results

The use of a single error variable for RX and TX operations has shown the OpenThread code to be asserting in some conditions.
Assert happens here: https://github.com/zephyrproject-rtos/openthread/blob/zephyr/src/core/mac/sub_mac.cpp#L494
KRKNWK-8998

Looks good, but I'd be good to open an upstream PR rightaway and mark the commits as [nrf fromlist] with a reference to the upstream PR - it's easier to track changes to revert during upmerges then.

OK, done here: https://github.com/zephyrproject-rtos/zephyr/pull/32389


MM-14714 - Updating textarea preview

Summary
MM-14714 - Updating textarea preview
Ticket Link
https://mattermost.atlassian.net/browse/MM-14714
Related Pull Requests

Has server changes (please link here)
Has redux changes (please link here)
Has mobile changes (please link here)

Before:
|
After:

Can somebody help merge + cherry pick?


AttributeError: 'NoneType' object has no attribute 'get'

I try to run /home/aaa/anaconda3/envs/openmmlab/bin/python tools/train.py /home/aaa/disk1/mmdetection/configs/_base_/models/retinanet_r50_fpn.py
but have the following error:
I also occurred this problem when I tried to train the model using a customized dataset in COCO format. But I have already change the coco.py for METAINFO = {'classes':('label1', 'label2')}
I have no idea what is this problem, and i didnt find anyone have this
Traceback (most recent call last):
  File "tools/train.py", line 133, in <module>
    main()
  File "tools/train.py", line 122, in main
    runner = Runner.from_cfg(cfg)
  File "/home/aaa/anaconda3/envs/openmmlab/lib/python3.8/site-packages/mmengine/runner/runner.py", line 444, in from_cfg
    runner = cls(
  File "/home/aaa/anaconda3/envs/openmmlab/lib/python3.8/site-packages/mmengine/runner/runner.py", line 354, in __init__
    self.setup_env(env_cfg)
  File "/home/aaa/anaconda3/envs/openmmlab/lib/python3.8/site-packages/mmengine/runner/runner.py", line 648, in setup_env
    if env_cfg.get('cudnn_benchmark'):
AttributeError: 'NoneType' object has no attribute 'get'

@Younger330 Please do not modify the code directly, you should modify the configurations.  please refer to https://github.com/open-mmlab/mmyolo/blob/main/docs/en/get_started/15_minutes_object_detection.md#config

I meet the same problem when I train the model on my own dataset, and I only change the config.

Traceback (most recent call last):
File "../mmdetection/tools/train.py", line 134, in
main()
File "../mmdetection/tools/train.py", line 123, in main
runner = Runner.from_cfg(cfg)
File "/workdir/weiyuelu/anaconda3/envs/mmlab/lib/python3.7/site-packages/mmengine/runner/runner.py", line 470, in from_cfg
cfg=cfg,
File "/workdir/weiyuelu/anaconda3/envs/mmlab/lib/python3.7/site-packages/mmengine/runner/runner.py", line 353, in init
self.setup_env(env_cfg)
File "/workdir/weiyuelu/anaconda3/envs/mmlab/lib/python3.7/site-packages/mmengine/runner/runner.py", line 647, in setup_env
if env_cfg.get('cudnn_benchmark'):
AttributeError: 'NoneType' object has no attribute 'get'

defvv

This is mainly a version issue,recommend instll mmcv by:MMCV_WITH_OPS=1 pip install -e .

I got the same issure for image segmentation, wonder if you revoled it?


added composer script for psr2 formatting

I see that there is already a pull request for phpcs config. Not sure what the best way is, but this works for me so I'll submit it for consideration

I'm into it. Anyone else?

👍


Use FOUNDATION_EXPORT over extern

New Pull Request Checklist

[X] I have read and understood the CONTRIBUTING guide

[X] I have read the Documentation

[X] I have searched for a similar pull request in the project and found none

[X] I have updated this branch with the latest master to avoid conflicts (via merge from master or rebase)

[X] I have added the required tests to prove the fix/feature I am adding

[X] I have updated the documentation (if necessary)

[X] I have run the tests and they pass

[X] I have run the lint and it passes (pod lib lint)

Pull Request Description
Use FOUNDATION_EXPORT over extern to be compatible with C++.

Looks good @skyline75489


Use events instead of polling

@keybase/react-hackers @zanderz
A better approach to showing the window on Windows startup

tested on works for me on windows vm

Wow, you made yourself an installer with Jenkins, too, I like it!
LGTM :thumbsup:

so this works fine on windows / linux?

yeah

:+1:
On Thursday, May 5, 2016, Marco Munizaga<EMAIL_ADDRESS>wrote:

yeah
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly or view it on GitHub
https://github.com/keybase/client/pull/2771#issuecomment-217292437


enable option for loading and converting bayer images

use some logic to determine if this is needed for conversion of bayer images on load:
img = np.load(filename, allow_pickle=False)
img = cv2.cvtColor(img, cv2.COLOR_BayerBG2RGB)

Since this requires cv2, I suggest that this conversion is done outside PyOPIA as a custon load function.
An example of how to create a custom class can be found here


Show More Not working

I'm trying to look at this WebSocket data in mitmweb, after I click Show More 2 times and the button no longer works. How do I fix this?

Hi, thank you! Could you please be more precise, perhaps with a screenshot? Did you get any errors in the console?

https://streamable.com/yv3f14
here's a video of it happening

Can confirm, second click on button does nothing. No error in JS console.

For some reason it is hardcoded to double the lines once and then that's it:
https://github.com/mitmproxy/mitmproxy/blob/7f7cb28d32cac2752bf00cfdb8343156855425e6/web/src/js/components/FlowView/Messages.tsx#L26-L29
PRs welcome

This Math.max should probably have been a Math.min. 🫣

This Math.max should probably have been a Math.min. 🫣

I quickly tried to change that, and apparently, it's not the only problem 😅 It's weird since, in other cases, the button seems to work fine, while with web socket messages, it doesn't 🤔

This Math.max should probably have been a Math.min. 🫣

I don't think that's it, with Math.min() it would never grow over 1024. I think the Math.max() was meant for cases where someone defined a very small content_view_lines_cutoff and clicking the button would then only give you a few lines. This makes sure you get at least 1024 when clicking the button.
Why is this line mutating state directly?
https://github.com/mitmproxy/mitmproxy/blob/7f7cb28d32cac2752bf00cfdb8343156855425e6/web/src/js/components/FlowView/Messages.tsx#L81

I've fixed it locally


[Bug] my.cnf should be mutable

Documentation

[x] I acknowledge that I have read the relevant documentation.

Describe the bug
I changed MariaDB yaml to add my.cnf configuration and got the following error
admission webhook "vmariadb.kb.io" denied the request: MariaDB.mariadb.mmontes.io "mariadb" is invalid: spec.myCnf: Invalid value: "[mariadb]\ninnodb_buffer_pool_size = 1G\ninnodb_log_file_size = 256M\ninnodb_flush_log_at_trx_commit = 2\ninnodb_write_io_threads = 8\ninnodb_io_capacity = 1000\nmax_allowed_packet = 256M\n": 'spec.myCnf' field is inmutable

Expected behaviour

Steps to reproduce the bug
Debug information

Related object events:

kubectl get events --field-selector involvedObject.name=<mariadb-resource-name>
kubectl get events --field-selector involvedObject.name=<backup-resource-name>
kubectl get events --field-selector involvedObject.name=<restore-resource-name>

mariadb-operator logs. Set the --log-level to debug if needed.

Environment details:

Kubernetes version: 1.28
Kubernetes distribution: Vanilla
mariadb-operator version: 0.24.0
Install method: helm
Install flavor: recommended

Additional context

Hey there!
100% this should be mutable at some point.
Updating the my.cnf config will need a Pod restart to pick up the new changes, so the plan is to keep it inmutable until we support custom upgrades:

https://github.com/mariadb-operator/mariadb-operator/issues/321

Hey there @rammelmueller ! I understand your concern.
At the moment, the spec.myCnf is inmutable for a reason: after updating the config, a restart of the cluster needs to happen for the changes to have effect, which means the operator will need to trigger a rolling upgrade.
The default rolling upgrade of the StatefulSet is not reliable enough, we need to implement custom upgrades, see:

https://github.com/mariadb-operator/mariadb-operator/issues/321

We will look into it shortly, and then we can make spec.myCnf mutable.

Thanks for the reply @mmontes11!
It's OK for now, I guess, however, one question remains: What is the standard procedure to updated the spec.myCnf when using some gitops tool like ArgoCD?

spec.myCnf is inmutable as I said, which means that the wehook will not allow ArgoCD to update this fiel. There is however one workaround, which implies using StatefulSet rolling upgrade, so use it at your own risk:

As you can see, the operator creates a ConfigMap to store the my.cnf which is mounted by the StatefulSet

spec:
  image: mariadb:11.2.2
  myCnf: |
    [mariadb]
    bind-address=*
    default_storage_engine=InnoDB
    binlog_format=row
    innodb_autoinc_lock_mode=2
    max_allowed_packet=256M
  myCnfConfigMapKeyRef:
    key: my.cnf
    name: mariadb-config

You may patch this ConfigMap from ArgoCD, the operator won't interact with it once it is created
Then, you should trigger a rolling upgrade. You will need to dynamically upgdate the Pod template from ArgoCD. Something equivalent to:

kubectl patch sts mariadb  -p "{\"spec\":{\"template\":{\"metadata\":{\"labels\":{\"date\":\"`date +'%s'`\"}}}}}"

This will be handled by the operator in the next few releases. The idea is that spec.myCnf becomes mutable and the ConfigMap gets updated, triggering a custom upgrade done by the operator.


[REF-697] Support per-component State

Currently State is global across the app and all components can access it... however it's not currently possible to define reusable reflex components that have their own per-component independent state.
Why would you want this? For example if I'm defining a widget, like a counter, and I want to place multiple counters in the app, then each counter needs its own state so they don't interfere with each other.
This can be achieved in 0.2.8 by using a dict in the state and keying each component into it, but it's not very clean. It would be nice if a component could define "local" state that was only part of that instance of the component.
How might this look?
def my_counter() -> rx.Component:
    class CounterState(rx.LocalState):
        count: int = 0

        def increment(self):
            self.count += 1

    return rx.vstack(
        rx.heading(CounterState.count),
        rx.button("Increment", on_click=CounterState.increment),
    )

def index():
    return rx.vstack(
        my_counter(),
        my_counter(),
        my_counter(),
    )

In this example, each counter should get its own copy of CounterState and operate independently.
Other API suggests are welcome at this point, since the feature still needs to be designed.
REF-697

Hi @masenf - just saw this State topic floating around and I was wondering if the https://github.com/reflex-dev/reflex/issues/1771 would be also something that cloud be addressed on this thread?

@include #1771 is already fixed in main, you can try out reflex==0.2.10a1 and see if it's working for you

@masenf working flowless :) thank you very much!

Is it correct, that it is currently not possible to use two different counter which share code (a reusable component with different states).
I think in plain react it would look something like this:
const Counter = () => {
  const [count, setCount] = useState(0);

  const handleIncrement = () => setCount(count + 1);
  const handleDecrement = () => setCount(count - 1);

  return (

      Current Count: {count}

        <button onClick={handleIncrement}>Increment</button>
        <button onClick={handleDecrement}>Decrement</button>

  );
};

Maybe it would be nice to write an own component like this:
class Counter(rx.UserComponent):
    count: int = rx.use_state(0)

    def handle_increment(self):
        self.count += 1

    def build(self) -> rx.Component:
        return rx.vstack(
        rx.heading(CounterState.count),
        rx.button("Increment", on_click=self.handle_increment),
    )

With my recent PRs something like this is already possible:

class Counter:
    count: int = 0

    def handle_increment(self):
        self.count += 1

   @classmethod
    def render(cls) -> rx.Component:
        return rx.vstack(
        rx.heading(cls.count),
        rx.button("Increment", on_click=cls.handle_increment),
    )

class CounterOne(Counter, rx.State):
  pass

Is this anywhere in the docs? (re-usable component with state and event handlers built-in)
If not, it should be!

@TimChild this was added recently:https://reflex.dev/docs/substates/component-state/


Ajax call on empty input

I want to suggest the following change in data/ajax.js line 91.
if (this.ajaxOptions.delay && params.term !== '') {
params.term is undefined when empty. So I would like to change this to:
if (this.ajaxOptions.delay && params.term !== undefined && params.term !== '') {
So an empty search field loads initial results fast as soon as an user opens the select2 box without addition delay. The params.term !== '' seems to have this intention as well.

Shouldn't actually check on an empty string I believe.
See:
https://github.com/select2/select2/pull/4202


Provide options for users to choose which account they want to use when publishing information to Wikidata

Use UMIL's publish Wikidata account;
Use user's own Wikidata account

For the account authentication, here is some information for reference.
What's the difference between the CSRF token and the OAuth access token when calling Wikidata API?
1. OAuth Access Token

The OAuth access token is a long-term token that grants your application permission to act on behalf of a user or account (like UMIL’s public account).
Once you have an OAuth access token, you no longer need the user’s username and password, nor do you need to manually retrieve a CSRF token.
OAuth tokens handle authentication and permissions. With an OAuth token, your API requests are inherently authorized without needing extra authentication steps.

2. CSRF Token

The CSRF token is a short-term, single-use token that’s primarily used to prevent unauthorized actions by malicious scripts or cross-site requests.
If you’re using a username and password directly (rather than OAuth), you must fetch a CSRF token each time you make an editing request to authenticate the specific action.

Key Difference

When using OAuth: The OAuth access token replaces both the username/password and the CSRF token, meaning you don’t need to retrieve a CSRF token for each request. The OAuth token itself serves as the authorization mechanism for any edits or data publishing.
When not using OAuth: If you’re relying on direct login with a username and password, the API requires a CSRF token for each action to confirm that it’s an authorized request.

Simplified Process with OAuth
With an OAuth access token:

Obtain the OAuth access token once (or refresh it as needed).
For each API request, include the OAuth access token in the Authorization header.

Here's what an API call looks like with OAuth (without needing a CSRF token):
headers = {
    "Authorization": f"Bearer {access_token}",  # OAuth access token replaces CSRF requirement
    "Content-Type": "application/json",
}

response = requests.post(
    "https://www.wikidata.org/w/api.php?action=wbsetlabel&format=json&...other_parameters...",
    headers=headers,
    json=data_to_publish,
)

Summary

With OAuth: Just use the access token; no CSRF token needed.
Without OAuth: You need a CSRF token with each request when using username and password directly.

Switching to OAuth streamlines the process, eliminates the need for a CSRF token, and is considered more secure for automated, programmatic access.


Multiple Grid intermittently overlap to each other

Hello,
When i drag the item from another column it works fine but when i need to return or drag again to another column overlap coming in. please see the attached file
   var options = {
        width: 1,
        float: false,
        cellHeight: 120,
        verticalMargin: 10,
        animate : true,
        removeTimeout : 500,
        detachGrid : false,
        disableResize: true,
        acceptWidgets: '.grid-stack-item'
    };
    $('#grid1').gridstack(options);
    $('#grid2').gridstack(options);
    $('#grid3').gridstack(options);
    $('#grid4').gridstack(options);
    $('#grid5').gridstack(options);
    $('#grid6').gridstack(options);
    $('#grid7').gridstack(options);

@jarnielcataluna Please provide a jsfiddle and we'll be happy to look into this for you.

Closing due to inactivity. Please reopen if there's still an issue.


on('registration') not fired on android

The on('registration') event is not firing on for android (working fine on iOS 4.3.0) while testing on a Sony (running<EMAIL_ADDRESS>and a Samsung (running android@5.0.1). This seems to be similar to #800, however I haven't been able to resolve it from following that thread.
I am using<EMAIL_ADDRESS>and building for<EMAIL_ADDRESS>I've installed<EMAIL_ADDRESS>alongside the cordova-plugin-google-analytics.
I've also removed the cordova-google-play-services plugin since it constantly gave me the error around multiple declarations of the com.google.android.gms package.
I've installed the required items through the Android SDK (see screenshot below):

and I'm using my config.xml file to install the plugin, and specified the SENDER_ID as part of that like so:
<plugin name="phonegap-plugin-push" spec="1.9.0">
    <param name="SENDER_ID" value="XXXXXXX" />
</plugin>

Steps to reproduce (starting from a clean project with no platform added):

add the plugins to config.xml`
cordova platform add android
cordova run android

This is what the code looks like where I make use of the plugin:
push = PushNotification.init({
        "android": { "senderID": "XXXXXXXXX", "icon": "notification_icon", "iconColor": "#0197e2" },
                "ios": { "alert": "true", "badge": "true", "sound": "true" }, "windows": {}
});

push.on('registration', function (data) {
        console.log(data.registrationId);
});

push.on('notification', function (message) {
        console.log(message);
});

push.on('error', function (e) {
        console.log(e);
});

For reference, this is the complete list of plugins I am using:
cordova-plugin-camera 2.3.0 "Camera"
cordova-plugin-compat 1.1.0 "Compat"
cordova-plugin-crosswalk-webview 2.1.0 "Crosswalk WebView Engine"
cordova-plugin-file 4.3.0 "File"
cordova-plugin-file-transfer 1.6.0 "File Transfer"
cordova-plugin-google-analytics 1.6.0 "Google Universal Analytics Plugin"
cordova-plugin-splashscreen 4.0.0 "Splashscreen"
cordova-plugin-whitelist 1.3.0 "Whitelist"
cordova-plugin-x-toast 2.5.2 "Toast"
ionic-plugin-keyboard 2.2.1 "Keyboard"
phonegap-plugin-push 1.9.0 "PushPlugin"

Note: I've tried all sorts of different permutations of the three plugins (phonegap-plugin-push, cordova-plugin-google-analytics and cordova-google-play-services) and concluded that cordova-google-play-services was a common denominator for me with either the MultiDex or More than one library with name issue, thus resulted in removing it completely.

@ntkzwane can you run adb logcat | grep PushPlugin and then start up the app? That should help debug. Also, do you see anything in the Chrome developer console?

@macdonst nothing comes up in the adb logcat logs when filtering for PushPlugin related logging.
I've verified that the PushNotification object is not undefined when the PushNotification.init({}) function is called.
There is nothing unusual being logged in the JS console either.

@ntkzwane the init method outputs some info to logs so if you are seeing nothing it makes me think init on the Java side is never being called. Try opening the project in Android Studio and setting a breakpoint.

@macdonst so I've debugged the code and it looks you are spot on, the init method for the plugin is not being called on the Java side. Do you have ideas as to what could be causing this? Is there possibly a step I am missing in my cordova config?

Native init not being called could be caused by, amongs some other ghost stuff, the following:

You simply didn't call PushNotification.init({...}) on your app's code.
You called init from js, but you somehow don't have the native code available. This can be caused by:

Bad compilation
Bad plugin installation
Cordova bug

You called init and the native code exists, but there's a bug with it.

I'm willing to bet it's a bad installation.

Do you perhaps have pointers on how to diagnose a bad installation @fredgalvao? As mentioned in my opening issue, I'm using cordova build android ensuring that the build is not using previously installed plugins i.e removing added platforms and clearing out the plugins/ directory.

@ntkzwane at this point I'd probably do:
cordova plugin rm cordova-plugin-google-analytics
cordova plugin rm cordova-google-play-services
cordova platform rm android
cordova platform add android
cordova clean android
cordova build android

Then check the platforms/android/src/com/adobe/phonegap/push directory to make sure that all of the source files were correctly delivered. Then test without the analytics plugin.

@macdonst I have verified that the issue is the cordova-plugin-crosswalk-webview plugin, and looking at this thread #1344 confirms this. I have tested this with the repository version of the crosswalk plugin and it all works fine. Thanks a ton for the help :+1:


chore: clippy

Fix clippy warnings with latest nightly.

error: `?Sized` bound is ignored because of a `Sized` requirement
   --> crates/rlp/src/decode.rs:129:9
    |
129 |     [T: ?Sized + Decodable] <alloc::boxed::Box<T>>::new(T),
    |         ^^^^^^
    |
note: `T` cannot be unsized because of the bound
   --> crates/rlp/src/decode.rs:129:18
    |
129 |     [T: ?Sized + Decodable] <alloc::boxed::Box<T>>::new(T),
    |                  ^^^^^^^^^
    = note: ...because `Decodable` has the bound `Sized`
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_maybe_sized
    = note: `-D clippy::needless-maybe-sized` implied by `-D warnings`
    = help: to override `-D warnings` add `#[allow(clippy::needless_maybe_sized)]`


Feature/299 search api

https://trello.com/c/OV00wXzM/299-search-api-endpoint-to-support-frontend-filtering
Change description
Adds the build.py script, correct paths to import CSS and adds checkboxes for frontend filtering. The frontend at /download should now look like this:

My understanding was that each of the categories - Filter by fund, Filter by area etc,. - were going to be accordions with check-boxes underneath them like the example template:

Perhaps check with @gidsg if this is the case or not?


Edited description of implementation for clarity

The following edits have been made:

In the diagram section, emphasis is put that the control unit will not be used for the entirety of the lab assignment
The implementation of add is specific to R-type only (no variants requiring direct memory access need to be implemented yet)

See details on https://jlpteaching.github.io/ECS154B/extra-credit.html for how to get credit for this fix!
Thanks!


AWS deploy problem when using IAM role

One of our users reported this in Slack. I'm going to try to reproduce today, but wanted to capture this here, as it seems like something weird is going on.
Environment

AWS w/out Cloudfront

IAM role created according to https://github.com/kubernetes/kops/blob/master/docs/aws.md

Pachyderm 1.6.3 or 1.6.4

Kubernetes:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.3", GitCommit:"f0efb3cb883751c5ffdbe6d515f3cb4fbe7b7acd", GitTreeState:"clean", BuildDate:"2017-11-09T07:27:47Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.10", GitCommit:"bebdeb749f1fa3da9e1312c4b08e439c404b3136", GitTreeState:"clean", BuildDate:"2017-11-03T16:31:49Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Behavior
When deploying to AWS with the manual deploy and using an IAM role via the --iam-role flag, pachd get's stuck in CrashLoopBackoff with the following error:
$ kubectl logs po/pachd-1269558310-lljzw
time="2017-11-16T15:41:33Z" level=info msg="validating kubernetes access returned no errors"
time="2017-11-16T15:41:33Z" level=info msg="AWS deployed with cloudfront distribution at
"
time="2017-11-16T15:41:33Z" level=info msg="Launching PPS master process"
storage is unable to discern NotExist errors, "AccessDenied: Access Denied
    status code: 403, request id: 613CB7E9A9263C79, host id: yQa3wa1XSUIu0WgQtmu0Zvb7F/doxT7YHI5R1A0b0dkbAlIhR4EGIhZZkxAWwXUgtjRAEz9FWHc=" should count as NotExist

At first glance, this seems to be related to: https://github.com/pachyderm/pachyderm/issues/1917, but note that the user is not using Cloudfront.
Reproducing
Again, I haven't been able to try this yet, but according to the steps I went through with the user:

Create IAM role based on https://github.com/kubernetes/kops/blob/master/docs/aws.md
Follow the AWS manual deploy docs using the IAM role, just as they are written.
Watch for the CrashLoopBackoff on the pachd pod
Check the logs for the pachd pod with kubectl logs

Notes
@sjezewski Maybe you have some thoughts here?

I was running into this issue yesterday when trying the manual deploy with the IAM role, but I tried again this morning using the one-shot script (static credentials) without using an IAM role and it appears there are no pachd issues that way.

Cool. Thanks for the details @scheidec! So this appears to be an apparent issue related to the way we are handling IAM roles. We will definitely try to reproduce.

Yea, so what's happening here is that pachd will use the ec2's instance IAM role by default.
(This is true no matter what you've set the --iam-role flag to, which is why our docs need updating and this is confusing: https://github.com/pachyderm/pachyderm/issues/2680)
That error message happens when that EC2 iam role does not have access to the s3 bucket specified. I saw this error when explicitly testing this out yesterday. I expect that error when the role doesn't have access. Once I added s3 access to that role, and restarted pachd, the error went away.
Hopefully that makes this a bit clearer. We have some updating to do on our docs to make this more transparent.


Hosted UI Endpoint not working

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
amplify status returns the following kind of url:
Test Your Hosted UI Endpoint: https://mydomain.auth.eu-west-1.amazoncognito.com/login?response_type=code&client_id=25flgv0rtcmidjo&redirect_uri=http://localhost:/
This url does not work at all.
Moreover it differs from the one provided buy the aws console.
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
4.11.0
To Reproduce
amplify auth update
Walkthrough all the auth configurations
Select the authentication/authorization services that you want to use: User Sign-Up, Sign-In, connected with AWS IAM controls
Allow unauthenticated logins?: no
Do you want to enable 3rd party authentication providers in your identity pool? : no
Do you want to add User Pool Groups?:no
Do you want to add an admin queries API?:no
Multifactor authentication (MFA) user login options:off
Email based user registration/forgot password: enable
default
default
Do you want to override the default password policy for this User Pool?: no
Specify the app's refresh token expiration period (in days): (default)
Do you want to specify the user attributes this app can read and write? N
Do you want to enable any of the following capabilities? (select nothing)
Do you want to use an OAuth flow? yes
-->then go ahea
Expected behavior
The Url should be the same as the one provided by aws console
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Mac/Windows/Ubuntu]
Node Version. You can use node -v to check the node version on your system

Additional context
In file:  packages/amplify-provider-awscloudformation/lib/display-helpful-urls.js
function: showHostedUIURLs
The problem comes from the following snippet, where URL parameter 'response_type' is hard coded:
if (redirectURIs.length > 0) {
const testHostedUIEndpoint = https://${HostedUIDomain}.auth.${Region}.amazoncognito.com/login?response_type=code&client_id=${AppClientIDWeb}&redirect_uri=${redirectURIs[0]}\n;
context.print.info(chalkTest Your Hosted UI Endpoint: {blue.underline ${testHostedUIEndpoint}});
}

The same issue affects the following function:
import { Auth } from 'aws-amplify';
Auth.federatedSignIn()

@gaboucand Does the url not show you a sign in page?

Hi ammarkarachi,
The result depends on the cognito user pool settings.
If you set "Allowed OAuth Flows " to "implicit grant" or "client credentials",
then the "Auth.federatedSignIn()) call would return an error.
This is due to the hard coded response type  "response_type=code".
It look like it is expected that the user pool is set to use only "Autorisation code grant".
Regards


Add a graph of dependencies to the README

Preview: https://github.com/googlefonts/fontc/tree/readme-depmap?tab=readme-ov-file#dependency-map
Fixes https://github.com/googlefonts/fontc/issues/607

It's a wee bit busy right now, so much so I had a bit of a hard time extracting information from it. I wonder if we could prune it down to the most important ones? For example, fauntlet, otexplorer, fea-lsp, font-codegen, freetype-rs, norad, and kurbo all seem like things that maybe could be removed. I think our skrifa dependency might be only for tests so maybe that could drop too.

For example, while arguably missing key data I find this version, perhaps accompanied by a note that fontc relies on read/write-fonts and kurbo more comprehensible:
%% This is a map of non-dev font-related dependencies.
%% See https://mermaid.live/edit for a lightweight editing environment for
%% mermaid diagrams.
graph TD
    %% First we define the nodes and give them short descriptions.
    %% We group them into subgraphs by repo so that the visual layout
    %% maps to the source layout, as this is intended for contributors.

    %% https://github.com/googlefonts/fontc
    subgraph fontc-repo[fontc repo]
        fontc{{fontc\nCLI font compiler}}
        fontra2fontir[fontra2fontir\nconverts .fontra files to our IR]
        glyphs2fontir[glyphs2fontir\nconverts .glyphs files to our IR]
        ufo2fontir[ufo2fontir\nconverts from a \n.designspace to our IR]
        fontir[fontir\nthe IR for fontc]
        fontbe[fontbe\nthe backend of font compilation\nIR -> binary font]
        fea-rs[fea-rs\nParses and compiles\nAdobe OpenType feature files]
        fontdrasil[fontdrasil\nCommon types and functionality\nshared between all layers of fontc]
    end

    %% Now define the edges.
    %% Made by hand on March 20, 2024, probably not completely correct.
    %% Should be easy to automate if we want to, main thing is to
    %% define the crates of interest.
    fontbe --> fontir
    fontbe --> fea-rs
    fontc --> fontbe
    fontc --> fontir
    fontc --> glyphs2fontir
    fontc --> fontra2fontir
    fontc --> ufo2fontir
    fontra2fontir --> fontir
    glyphs2fontir --> fontir
    ufo2fontir --> fontir

That might just be me, if you find the current one more helpful feel free to merge.

Yeah, simplifying it makes it much more legible.


Replace relevant instance of "pos" with "positive"

Addresses issue #420
This library has been super helpful to me! Thank you for the hard work 🎈
I grepped for instances of pos and replaced the ones which seemed relevant. I only replaced full abbreviations, leaving things like exp_pos alone. I also ran the tests locally, though I didn't check that they passed for every single toolchain.

Thanks! great cleanup.

leaving things like exp_pos alone

I'll add it to the issue so we don't forget about it.


[DOC] Add to toc tree depth to enable multiple level menu (#1081)

Description
The previous rst only allow one depth of toc, which will hide tutorial hierarchy. This pull request adds to the toc depth to enable multiple level menu. (#1081)
Checklist
Essentials

[☑] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[☑] Changes are complete (i.e. I finished coding on this PR)
[☑] All changes have test coverage
[☑] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Job PR-1108/1 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-1108/1/index.html

I can't find a difference between the new
and old

version.
Could you elaborate what you want to achieve?
I'm comparing http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-1108/1/examples/machine_translation/transformer.html and https://gluon-nlp.mxnet.io/examples/machine_translation/transformer.html
Thanks!

@StrayBird-ATSH thanks for the update. Did it render correctly in your local machine? I see some error message from the CI server. Do you have a screenshot for the working version?

Hello Haibin, thanks for your notice.
I will dig into the problem as soon as possible. I will keep an eye on future CI results after I make new attempts. I will let you informed the moment the CI pipeline can generate a working website as desired.
Thanks for your patience.

Job PR-1108/3 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-1108/3/index.html

@eric-haibin-lin @leezu
Hello Haibin and Leonard. Thanks for your waiting and patience. I think the document refactor is now ready for your review.
I have checked the website at the CI pipeline output, it seems very good and has the desired hierarchy for the left side navigation bar. But it seems there is one CPU unit test failing from the CI. I have reviewed the details but cannot figure out what happened. Maybe it is not relevant to my commit changes?
Thanks for your review!

Thanks @leezu for your instructions. The latest unit test has passed. I will try to follow your instructions to fix it if I meet similar problem in the future.
Thanks @eric-haibin-lin for your review. From my perspective, I think maybe it is better to merge this pull request first since this is a big change on the structure of the website. Also, this pull request changes no content, modifying only the styles. After merging this pull request, I will create a new one to do all the content refactoring as you have mentioned in the issue.
I think separating the style changes and the content changes may be clearer for future references and less error-prone.
Thanks!

Well done @StrayBird-ATSH !


Post-release<EMAIL_ADDRESS>dependency updates & related chores

I think the pertinent details are captured in individual commit notes. Top-level, the most notable details:

Removes the @getodk/ui-solid package, as we had planned
The updates to tree-sitter etc allowed a vast simplification of the @getodk/tree-sitter-xpath package structure, build, etc (as well as nicely paring down top-level git files)

One thing not mentioned in any of the commit notes: we are not currently running the @getodk/web-forms E2E tests in CI!  I have (and can include in this PR):

A complete fix for style.test.ts (it just needs to look for a different text snippet to proceed)
A partial fix for vue.test.ts, but it times out. I'm not sure what the best thing is for this test, but it would probably be best if we can break it up into per-fixture tests (probably requiring codegen).

Looks like I have some new lint issues to address 🙃


Android App terminated 1 minute after display timeout

When location request permissions dialog is displayed, using "only this time", the application is terminated 1 minute after display timeout.  If permission dialog is not displayed, because you previously answered "While using the app", then this does NOT happen.  So, basically every time you turn your phone on with the app in the foreground it is restarting the application!
Android 11
Pixel 3 XL and Emulator
Set Display timeout
Turn off developer "Stay Awake"
test_geolocator sample project

flutter doctor -v
[√] Flutter (Channel stable, 2.2.3, on Microsoft Windows [Version 10.0.19043.1110], locale en-US)
    • Flutter version 2.2.3 at C:\projects\flutter
    • Framework revision f4abaa0735 (6 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at C:\Users\matt\AppData\Local\Android\sdk
• Platform android-30, build-tools 30.0.3
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Android Studio
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• android-studio-dir = C:\Program Files\Android\Android Studio
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)
[√] VS Code (version 1.59.0)
• VS Code at C:\Users\matt\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.25.0
[√] Connected device (3 available)
• sdk gphone x86 64 arm64 (mobile) • emulator-5554 • android-x64    • Android 11 (API 30) (emulator)
• Chrome (web)                     • chrome        • web-javascript • Google Chrome 92.0.4515.131
• Edge (web)                       • edge          • web-javascript • Microsoft Edge 92.0.902.67
• No issues found!

I am closing this issue as there has been no activity in about two years. If you are encountering this issue on the latest version of the geolocator plugin, feel free to open a new issue, linking this issue.


Create notice when someone holds the golden fistbump for too long

In order to incentivize the sharing of the Golden Fistbump, an alert should be generated when a user has the Golden Fistbump for a long period of time(ex: a week)

We have the ability to retrieve the most recent Golden Fistbump Recognition. When a receiver holds the fistbump and receives a fistbump, I'm considering appending another whisper to the receiver of fistbumps when the following condition is met :
moment(Date.now()) - goldenRecognition.timestamp > 7 days


Upgrade build gradle

Issue description
I have issue when add compile 'io.card:android-sdk:5.5.1' is "Multiple dex files define Lio/card/payment/CardIOActivity;"
I think this issue by conflict build tool gradle, please update gradle to latest version in card.id SDK.

It's probably not because of Gradle as I'm using this library with Gradle 4.7 and Android Gradle Plugin 3.2.0-alpha15 without any problems.


Added bash/zsh autocompletion support

Added completion.go for autocompletion of commands.
(inspired from kompose)

This will resolve https://github.com/kedgeproject/kedge/issues/148

@surajssd @containscafeine @kadel @cdrage needs review on this :)

@surajnarwade LGTM.
I'm assuming this is a copy-and-paste from https://github.com/kubernetes/kompose/blob/master/cmd/completion.go and s/kompose/kedge/g ?


[Event Request] - Codeunit 5750 Whse.-Create Source Document: OnBeforeCheckIfFromSalesLine2ShptLine

We need the following event with handled pattern to be able to do additional checks:

No, this change limit use of event. You can use existing event if needed.

this event would be helpful for us too. I need a way to interfere with creation of warehouse shipments.


which config file match the Trained Model named model_epoch_025_step_100100.pth

there are two config file in the dir Det3D/examples/cbgs/configs  lyft*.py and nusc*.py
when I load the model with the file nusc ,the the model unable get right result and as fllow
The model and loaded state dict do not match exactly
unexpected key in source state_dict: model, optimizer, iteration, epoch
missing keys in source state_dict: backbone.middle_conv.8.bn1.running_var, backbone.middle_conv.3.bn2.running_mean, neck.blocks.0.17.bias, backbone.middle_conv.19.bn2.running_mean, backbone.middle_conv.1.running_mean, bbox_head.tasks.2.conv_dir.weight, backbone.middle_conv.4.conv2.bias, backbone.middle_conv.4.conv1.bias, backbone.middle_conv.11.running_mean, backbone.middle_conv.13.conv1.bias, backbone.middle_conv.4.conv2.weight, backbone.middle_conv.1.weight, neck.blocks.0.13.weight, bbox_head.tasks.2.conv_dir.bias, backbone.middle_conv.14.bn1.weight, backbone.middle_conv.5.weight, backbone.middle_conv.6.running_var, backbone.middle_conv.8.conv2.bias, neck.blocks.0.5.weight, backbone.middle_conv.14.bn2.running_mean, backbone.middle_conv.1.bias, backbone.middle_conv.9.bn1.bias, backbone.middle_conv.14.bn2.running_var, backbone.middle_conv.18.bn2.weight, backbone.middle_conv.8.bn1.bias, bbox_head.tasks.3.conv_cls.bias, backbone.middle_conv.16.running_var, backbone.middle_conv.18.bn1.weight, backbone.middle_conv.18.conv1.bias, neck.blocks.1.17.bias, backbone.middle_conv.6.weight, bbox_head.tasks.3.conv_dir.weight, backbone.middle_conv.11.weight, backbone.middle_conv.8.conv1.weight, neck.blocks.0.2.running_mean, backbone.middle_conv.9.conv1.weight, bbox_head.tasks.4.conv_cls.weight, neck.deblocks.0.1.weight, neck.blocks.1.2.running_var, neck.blocks.0.8.bias, backbone.middle_conv.13.bn1.bias, backbone.middle_conv.4.bn2.weight, neck.deblocks.0.1.running_var, backbone.middle_conv.19.bn2.weight, bbox_head.tasks.3.conv_dir.bias, backbone.middle_conv.14.bn2.weight, neck.blocks.1.14.weight, neck.blocks.1.11.weight, backbone.middle_conv.9.conv2.weight, backbone.middle_conv.18.bn2.running_mean, neck.blocks.0.5.running_mean, backbone.middle_conv.3.bn1.bias, neck.deblocks.0.1.running_mean, bbox_head.tasks.1.conv_dir.weight, bbox_head.tasks.5.conv_box.bias, bbox_head.tasks.0.conv_box.weight, backbone.middle_conv.3.bn1.running_mean, neck.blocks.1.8.weight, backbone.middle_conv.4.bn2.bias, neck.blocks.1.8.running_var, neck.blocks.1.2.bias, bbox_head.tasks.0.conv_box.bias, backbone.middle_conv.4.bn1.running_mean, backbone.middle_conv.10.weight, neck.blocks.1.17.running_var, neck.deblocks.1.1.bias, backbone.middle_conv.3.bn1.weight, backbone.middle_conv.9.bn2.weight, bbox_head.tasks.5.conv_dir.bias, backbone.middle_conv.8.bn1.weight, neck.deblocks.1.0.weight, backbone.middle_conv.4.bn2.running_mean, neck.blocks.1.5.bias, backbone.middle_conv.13.bn1.running_var, bbox_head.tasks.4.conv_box.weight, backbone.middle_conv.8.bn2.running_var, neck.blocks.1.2.weight, backbone.middle_conv.11.bias, neck.blocks.1.5.running_var, backbone.middle_conv.19.conv1.bias, backbone.middle_conv.1.running_var, bbox_head.tasks.2.conv_cls.weight, neck.blocks.0.2.weight, backbone.middle_conv.9.bn2.bias, backbone.middle_conv.9.bn1.running_mean, backbone.middle_conv.21.weight, neck.blocks.1.17.running_mean, backbone.middle_conv.8.bn1.running_mean, backbone.middle_conv.13.bn1.weight, bbox_head.tasks.2.conv_cls.bias, backbone.middle_conv.14.bn1.bias, neck.blocks.0.2.bias, neck.blocks.1.16.weight, bbox_head.tasks.5.conv_dir.weight, neck.blocks.1.10.weight, bbox_head.tasks.0.conv_cls.weight, neck.blocks.1.5.weight, bbox_head.tasks.3.conv_box.bias, backbone.middle_conv.14.conv1.weight, backbone.middle_conv.19.bn1.weight, neck.blocks.0.17.running_mean, bbox_head.tasks.4.conv_box.bias, neck.blocks.0.11.bias, neck.blocks.0.17.weight, backbone.middle_conv.3.bn2.running_var, bbox_head.tasks.3.conv_cls.weight, backbone.middle_conv.0.weight, backbone.middle_conv.18.conv1.weight, backbone.middle_conv.18.bn2.running_var, backbone.middle_conv.9.conv1.bias, neck.deblocks.1.1.weight, bbox_head.tasks.1.conv_cls.bias, bbox_head.tasks.3.conv_box.weight, backbone.middle_conv.4.bn2.running_var, neck.blocks.0.5.running_var, backbone.middle_conv.9.conv2.bias, backbone.middle_conv.4.bn1.weight, neck.blocks.0.5.bias, neck.blocks.1.1.weight, backbone.middle_conv.21.bias, backbone.middle_conv.14.conv1.bias, backbone.middle_conv.8.conv1.bias, backbone.middle_conv.6.running_mean, backbone.middle_conv.13.conv1.weight, backbone.middle_conv.9.bn2.running_var, neck.blocks.1.5.running_mean, neck.blocks.0.11.weight, bbox_head.tasks.4.conv_dir.weight, neck.blocks.1.14.running_var, neck.deblocks.0.1.bias, bbox_head.tasks.2.conv_box.bias, backbone.middle_conv.4.conv1.weight, backbone.middle_conv.19.bn2.bias, neck.blocks.0.11.running_mean, neck.blocks.0.11.running_var, backbone.middle_conv.8.bn2.bias, backbone.middle_conv.19.bn2.running_var, backbone.middle_conv.13.bn2.bias, backbone.middle_conv.8.conv2.weight, neck.blocks.1.14.running_mean, backbone.middle_conv.3.bn2.bias, backbone.middle_conv.18.bn2.bias, backbone.middle_conv.18.bn1.running_var, bbox_head.tasks.0.conv_dir.bias, neck.blocks.1.4.weight, backbone.middle_conv.14.conv2.bias, neck.blocks.0.16.weight, neck.blocks.0.8.weight, backbone.middle_conv.13.bn2.weight, neck.blocks.0.14.running_var, neck.deblocks.0.0.weight, neck.deblocks.1.1.running_var, backbone.middle_conv.13.conv2.bias, neck.blocks.1.11.bias, backbone.middle_conv.13.conv2.weight, neck.blocks.0.17.running_var, backbone.middle_conv.19.bn1.running_mean, neck.blocks.0.14.bias, backbone.middle_conv.3.conv1.bias, backbone.middle_conv.18.bn1.bias, neck.blocks.0.8.running_var, backbone.middle_conv.13.bn1.running_mean, bbox_head.tasks.4.conv_cls.bias, neck.blocks.1.17.weight, neck.blocks.1.14.bias, backbone.middle_conv.14.bn2.bias, bbox_head.tasks.2.conv_box.weight, backbone.middle_conv.18.conv2.weight, backbone.middle_conv.9.bn1.running_var, backbone.middle_conv.3.bn2.weight, bbox_head.tasks.1.conv_box.weight, bbox_head.tasks.0.conv_cls.bias, backbone.middle_conv.19.conv1.weight, backbone.middle_conv.8.bn2.weight, neck.blocks.1.8.bias, bbox_head.tasks.0.conv_dir.weight, bbox_head.tasks.1.conv_cls.weight, bbox_head.tasks.1.conv_box.bias, bbox_head.tasks.4.conv_dir.bias, bbox_head.tasks.5.conv_cls.bias, neck.blocks.1.7.weight, backbone.middle_conv.19.conv2.weight, backbone.middle_conv.3.conv2.weight, neck.blocks.1.2.running_mean, backbone.middle_conv.14.conv2.weight, backbone.middle_conv.20.weight, neck.blocks.1.11.running_var, backbone.middle_conv.16.running_mean, backbone.middle_conv.16.bias, neck.blocks.0.1.weight, backbone.middle_conv.18.conv2.bias, backbone.middle_conv.6.bias, neck.blocks.1.11.running_mean, backbone.middle_conv.21.running_var, neck.blocks.0.2.running_var, backbone.middle_conv.4.bn1.bias, backbone.middle_conv.8.bn2.running_mean, backbone.middle_conv.14.bn1.running_mean, backbone.middle_conv.11.running_var, neck.blocks.0.4.weight, neck.blocks.0.14.weight, bbox_head.tasks.5.conv_box.weight, backbone.middle_conv.21.running_mean, neck.deblocks.1.1.running_mean, backbone.middle_conv.19.bn1.running_var, neck.blocks.0.14.running_mean, backbone.middle_conv.16.weight, backbone.middle_conv.9.bn2.running_mean, backbone.middle_conv.3.conv1.weight, backbone.middle_conv.4.bn1.running_var, backbone.middle_conv.3.bn1.running_var, neck.blocks.1.8.running_mean, bbox_head.tasks.1.conv_dir.bias, backbone.middle_conv.9.bn1.weight, backbone.middle_conv.18.bn1.running_mean, backbone.middle_conv.19.bn1.bias, backbone.middle_conv.14.bn1.running_var, backbone.middle_conv.19.conv2.bias, bbox_head.tasks.5.conv_cls.weight, backbone.middle_conv.3.conv2.bias, backbone.middle_conv.13.bn2.running_mean, backbone.middle_conv.15.weight, neck.blocks.1.13.weight, backbone.middle_conv.13.bn2.running_var, neck.blocks.0.10.weight, neck.blocks.0.8.running_mean, neck.blocks.0.7.weight

nusc*.py

thanks i do this, there are some export as above . is right?:
The model and loaded state dict do not match exactly
unexpected key in source state_dict: model, optimizer, iteration, epoch
missing keys in source state_dict

@poodarchu  thanks for your work ,l  do like this,but when I load your trained model with the file nusc*.py ,the the model unable get right result and the  output as fllow:
The model and loaded state dict do not match exactly
unexpected key in source state_dict: model, optimizer, iteration, epoch
missing keys in source state_dict: backbone.middle_conv.8.bn1.running_var, backbone.middle_conv.3.bn2.running_mean, neck.blocks.0.17.bias, backbone.middle_conv.19.bn2.running_mean, backbone.middle_conv.1.running_mean, bbox_head.tasks.2.conv_dir.weight, backbone.middle_conv.4.conv2.bias, backbone.middle_conv.4.conv1.bias, backbone.middle_conv.11.running_mean, .........

you can check the loaded checkpoint and see where the mismatch is.

@poodarchu I think you need to update your code. In your uploaded log file, many layers like "DefaultArgLayer" cannot be found in the current repo. The corresponding config file also needs to be updated. Thanks a lot.

@poodarchu I think you need to update your code. In your uploaded log file, many layers like "DefaultArgLayer" cannot be found in the current repo. The corresponding config file also needs to be updated. Thanks a lot.

Indeed, Det3D is refactored for releasing purpose, and the checkpoint is from my earlier codebase.

Thank you for your reply! @poodarchu Then I hope you can release a checkpoint based on the current Det3D codebase, because the current checkpoint seems hard to use for validation.

Thank you for your reply! @poodarchu Then I hope you can release a checkpoint based on the current Det3D codebase, because the current checkpoint seems hard to use for validation.

Can you provide some feedback s?

I upload a Jupyter Notebook file here: load checkpoint error

I can provide some pre-trained models based on a forked version of det3d this week. I fix some bugs and tune the parameters a little bit and get slightly better results. I will create a pull request once I get time.

@tianweiy do you have any results already? I also tried to use the provided checkpoint but it is not possible to use it with this version of Det3D ...

It will be out with our new paper this week. Please stay tuned

@pjohh  It will be out with our arxiv paper in the next arxiv cycle (Sunday night in the US, Monday morning in Asia). Thanks for the waiting.

@tianweiy good to hear! Could you please leave a link here when your repo is online?


Support current-date initialization

It would be perfect to provide an easy way to initialize current date

Apologies for the delayed response;
To me it doesn't make much sense to provide a model binding and an initial date as separate values. When you use the component you will be binding it to a model in the component, so to set its state you would just do so there.
So for example if you are using model driven forms;
##Template
<form [formGroup]="myForm">
  <ic-datepicker formControlName="myDate"></ic-datepicker>
</form>

##Component
let myInitialDate = '2017-01-01';

this.myForm = new FormGroup({
  myDate: new FormControl(myInitialDate)
});

Or am I misunderstanding your issue?

Closing due to inactivity - ping me another comment if this is still an issue.


swift file not found

Hi ,
I created a new obj-c project and tried to add Uber SDK. I installed it via cocoa pods.
I am getting this error - 'UberRides/UberRides-Swift.h' file not found
is there any solution for this?

Glad you figured it out! :)


Add support for erasure coding

Bee v2 introdues erasure coding with swarm-redundancy-level header.
We add this in the config and use it in /bytes and /bzz endpoints

Is this done? How can a user set erasure coding for uploading, using the server and CLI combination.

its already done.
https://github.com/fairDataSociety/fairOS-dfs/issues/613#issuecomment-2109520188


Calculator SteamDB can't work

My Steam profile and more steams account can't view by SteamDB Calculator
https://steamdb.info/calculator/76561198278976653/?cc=il
this is my link ID on SteamDB
and below my Profile
http://steamcommunity.com/id/MyShadows

Steam API may have hiccups, it's working fine atm.

Well, it's will fix soon?

Your own link is working fine.

the SteamDB can't view my account on my country currency..
Israel new Shekels

It's working fine.

for me not XD thanks :)
I'll see iot soon


Raspberry pi 4 -  M105.0.5174.0 - Shared library problem

Hello i have installed this package thorium-browser-105.0.5174.0_arm64.deb
with this command:
sudo apt install ./thorium-browser-105.0.5174.0_arm64.deb
I am trying to use this headless with npm puppeteer.
pi@raspberrypi:~ $ thorium-browser

/usr/bin/thorium-browser: error while loading shared libraries: libminigbm.so: cannot open shared object file: No such file or directory

pi@raspberrypi:~ $ uname -a

Linux raspberrypi 5.15.32-v8+ #1538 SMP PREEMPT Thu Mar 31 19:40:39 BST 2022 aarch64 GNU/Linux

pi@raspberrypi:~ $ cat /etc/os-release

PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian

@rbcet So you are running without GUI?

@Alex313031
I encountered the same problem. I'm running without GUI.
How should I install it? Do you have any recommendations?

@ironyee @rbcet I think this commit will fix this, next build you guys can try it. > https://github.com/Alex313031/Thorium/commit/c0a8a68732baa4bbea4e0287ac55a85c142c7213
In the meantime, you can install libminigbm, or compile it yourself

@Alex313031
Thank you so much for the quick reply.
I'm going to wait for the next build.

@ironyee @rbcet Making new build now.

@Alex313031
Are you going to make a RPM package too?

I can try, Ive never made an rpm package of chromium or thorium before

@ironyee @rbcet New version should fix it, plus it has alot of new cool flags > https://github.com/Alex313031/Thorium-Special/releases/tag/M106.0.5215.0
Also @ironyee I answered your issue in the main repo.

@Alex313031 Thank you, Alexander. You are the best.

@Alex313031 thanks a lot, it works now