Update JTL.Wawi to v<IP_ADDRESS>

Changelog: https://www.jtl-software.de/jtl-wawi-download/changelog#version-1-5-46-0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Would you mind creating a de-DE locale?

That's a good idea. I'll be adding it in the next few minutes.

Would you mind creating a de-DE locale?

Pull Request created for de-DE locale
#18352

Would you mind creating a de-DE locale?

Pull Request created for de-DE locale
#18352

Great!


Implement and test cluster autoscaling in Airflow architecture

As mentioned by @ireneisdoomed in this discussion, certain steps require lots of resources, so it's vital to enable autoscaling to make sure they can run in reasonable time.
This should also make per-job configuration not necessary anymore, simplifying running any workloads.

Important to note that the LD index generation is likely to be part of the preprocessing part.


Refactored and simplified fanout with improvements from incoming chunk iterator PRs.

Changes:

Secondary logic is hidden, instead of weird failed series set logic we had.
Fanout is well commented
Fanout closing record all errors
MergeQuerier improved API (clearer)
deferredGenericMergeSeriesSet is not needed as we return no samples anyway for failed series sets (next = false).

Signed-off-by: Bartlomiej Plotka<EMAIL_ADDRESS>

Unfortunately, we need to merge this if we want CI ):
There is one todo but it's super late so let's do it tomorrow. PTAL @kakkoyun


[Feature Request] Update azure-storage-js to v10

A new version of azure/storage-js (v10.3.0) has been published with major changes. The project actually uses the 2.10.2 version, which differences with the new one are that it has only one package which includes the implementation of blob, queue and file storage, but the v10.3.0 has a different package for each one.
Also, the project only uses the blob-storage implementation, so it would be more performant to only use the respective package (Azure/storage-blob).
Note
The Azure/storage-blob is the only package of the new version which is not in preview stage

Duplicate of #328. Closing.


WSS error on production  on SSL domain

Hi i have problem with WSS connect  for  3days .
I read all questions and test all
the production server is centos and in local all thing is ok
the production  domain is over SSL
but i dont have .key and .crt file
so i know set
LARAVEL_WEBSOCKETS_SSL_CA=
LARAVEL_WEBSOCKETS_SSL_LOCAL_CERT=
LARAVEL_WEBSOCKETS_SSL_LOCAL_PK=
LARAVEL_WEBSOCKETS_SSL_PASSPHRASE=

in the env but how and hot to get this files
websockets.php
<?php

use BeyondCode\LaravelWebSockets\Dashboard\Http\Middleware\Authorize;

return [

    /*
     * Set a custom dashboard configuration
     */
    'dashboard' => [
        'port' => env('LARAVEL_WEBSOCKETS_PORT', 8443),
    ],

    /*
     * This package comes with multi tenancy out of the box. Here you can
     * configure the different apps that can use the webSockets server.
     *
     * Optionally you specify capacity so you can limit the maximum
     * concurrent connections for a specific app.
     *
     * Optionally you can disable client events so clients cannot send
     * messages to each other via the webSockets.
     */
    'apps' => [
        [
            'id' => env('PUSHER_APP_ID'),
            'host' => env('PUSHER_HOST'),
            'name' => env('APP_NAME'),
            'key' => env('PUSHER_APP_KEY'),
            'secret' => env('PUSHER_APP_SECRET'),
            // 'path' => env('LARAVEL_WEBSOCKETS_PATH', 'laravel-websockets'),
            'capacity' => null,
            'encrypted' => true,
            'enable_client_messages' => false,
            'enable_statistics' => true,

        ],
    ],

    /*
     * This class is responsible for finding the apps. The default provider
     * will use the apps defined in this config file.
     *
     * You can create a custom provider by implementing the
     * `AppProvider` interface.
     */
    'app_provider' => BeyondCode\LaravelWebSockets\Apps\ConfigAppProvider::class,

    /*
     * This array contains the hosts of which you want to allow incoming requests.
     * Leave this empty if you want to accept requests from all hosts.
     */
    'allowed_origins' => [
        //
    ],

    /*
     * The maximum request size in kilobytes that is allowed for an incoming WebSocket request.
     */
    'max_request_size_in_kb' => 1024,

    /*
     * This path will be used to register the necessary routes for the package.
     */
    'path' => env('LARAVEL_WEBSOCKETS_PATH', 'laravel-websockets'),

    /*
     * Dashboard Routes Middleware
     *
     * These middleware will be assigned to every dashboard route, giving you
     * the chance to add your own middleware to this list or change any of
     * the existing middleware. Or, you can simply stick with this list.
     */
    'middleware' => [
        'web',
        Authorize::class,
    ],

    'statistics' => [
        /*
         * This model will be used to store the statistics of the WebSocketsServer.
         * The only requirement is that the model should extend
         * `WebSocketsStatisticsEntry` provided by this package.
         */
        'model' => \BeyondCode\LaravelWebSockets\Statistics\Models\WebSocketsStatisticsEntry::class,

        /**
         * The Statistics Logger will, by default, handle the incoming statistics, store them
         * and then release them into the database on each interval defined below.
         */
        'logger' => BeyondCode\LaravelWebSockets\Statistics\Logger\HttpStatisticsLogger::class,

        /*
         * Here you can specify the interval in seconds at which statistics should be logged.
         */
        'interval_in_seconds' => 60,

        /*
         * When the clean-command is executed, all recorded statistics older than
         * the number of days specified here will be deleted.
         */
        'delete_statistics_older_than_days' => 60,

        /*
         * Use an DNS resolver to make the requests to the statistics logger
         * default is to resolve everything to <IP_ADDRESS>.
         */
        'perform_dns_lookup' => false,
    ],

    /*
     * Define the optional SSL context for your WebSocket connections.
     * You can see all available options at: http://php.net/manual/en/context.ssl.php
     */
    'ssl' => [
        /*
         * Path to local certificate file on filesystem. It must be a PEM encoded file which
         * contains your certificate and private key. It can optionally contain the
         * certificate chain of issuers. The private key also may be contained
         * in a separate file specified by local_pk.
         */
        'local_cert' => env('LARAVEL_WEBSOCKETS_SSL_LOCAL_CERT', null),

        /*
         * Path to local private key file on filesystem in case of separate files for
         * certificate (local_cert) and private key.
         */
        'local_pk' => env('LARAVEL_WEBSOCKETS_SSL_LOCAL_PK', null),

        /*
         * Passphrase for your local_cert file.
         */
        'passphrase' => env('LARAVEL_WEBSOCKETS_SSL_PASSPHRASE', null),

        'verify_peer' => env('APP_ENV') === 'production',

        'allow_self_signed' => env('APP_ENV') !== 'production',
    ],

    /*
     * Channel Manager
     * This class handles how channel persistence is handled.
     * By default, persistence is stored in an array by the running webserver.
     * The only requirement is that the class should implement
     * `ChannelManager` interface provided by this package.
     */
    'channel_manager' => \BeyondCode\LaravelWebSockets\WebSockets\Channels\ChannelManagers\ArrayChannelManager::class,
];

broadcastin.php

<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Default Broadcaster
    |--------------------------------------------------------------------------
    |
    | This option controls the default broadcaster that will be used by the
    | framework when an event needs to be broadcast. You may set this to
    | any of the connections defined in the "connections" array below.
    |
    | Supported: "pusher", "redis", "log", "null"
    |
    */

    'default' => env('BROADCAST_DRIVER', 'null'),

    /*
    |--------------------------------------------------------------------------
    | Broadcast Connections
    |--------------------------------------------------------------------------
    |
    | Here you may define all of the broadcast connections that will be used
    | to broadcast events to other systems or over websockets. Samples of
    | each available type of connection are provided inside this array.
    |
    */

    'connections' => [

        'pusher' => [
            'driver' => 'pusher',
            'key' => env('PUSHER_APP_KEY'),
            'secret' => env('PUSHER_APP_SECRET'),
            'app_id' => env('PUSHER_APP_ID'),
            'options' => [
                    'cluster' => env('PUSHER_APP_CLUSTER'),
                    'encrypted' => true,
                    'host' => env('PUSHER_HOST'),
                    'port' =>  env('PUSHER_PORT'),
                    'scheme' => env('PUSHER_SCHEME', 'http'),
                    'useTLS' => true,
                    'curl_options' => [
                        CURLOPT_SSL_VERIFYHOST => 0,
                        CURLOPT_SSL_VERIFYPEER => 0,
                    ]
                ],

        'redis' => [
            'driver' => 'redis',
            'connection' => 'default',
        ],

        'log' => [
            'driver' => 'log',
        ],

        'null' => [
            'driver' => 'null',
        ],

    ],

];

app.js
window.Echo = new Echo({
        broadcaster: 'pusher',
        encrypted: true,
        key: process.env.MIX_PUSHER_APP_KEY,
        wsHost: process.env.MIX_PUSHER_HOST,
        wsPort: process.env.MIX_PUSHER_PORT,
        forceTLS: (process.env.MIX_APP_ENV === 'production' ? true : false ),
        disableStats: true,
        enabledTransports: ['ws', 'wss']
    });

every server with ssl has those files, you just have to add them to .env
LARAVEL_WEBSOCKETS_SSL_CA=
LARAVEL_WEBSOCKETS_SSL_LOCAL_CERT=
LARAVEL_WEBSOCKETS_SSL_LOCAL_PK=
LARAVEL_WEBSOCKETS_SSL_PASSPHRASE=

how and hot to get this files

nobody else have access to your server for tell you where are them,
in any case you would have to publish the root password and your server 😄

@PaolaRuby
i found this files and set into .env but  not work
LARAVEL_WEBSOCKETS_SSL_LOCAL_CERT="/usr/local/directadmin/data/users/admin/domains/DOMAIN.COM.cert"
LARAVEL_WEBSOCKETS_SSL_LOCAL_PK="/usr/local/directadmin/data/users/admin/domains/DOMAIN.COM.key"

i nano this file and exist in the  ex: DOMAIN.COM
after change i run :
php artisan cache:clear
php artisan clear-compiled
supervisorctl restart all
but not worked ...

DOMAIN.COM.cert sounds generic, maybe they are not the certs for https

@PaolaRuby
Has anyone ever managed to connect to SSL?
Every time I look at the problems, everyone has this problem and many are left without an answer ...

@PaolaRuby
The LARAVEL_WEBSOCKETS_SSL_CA=  is not exist in websockes.php config i search this param in my project never used , why you say that set LARAVEL_WEBSOCKETS_SSL_CA=
In .env  when never used any where

Here is LARAVEL_WEBSOCKETS_SSL_CA
https://github.com/beyondcode/laravel-websockets/blob/fd2070fc3d28696247acceacc4f40667828f3016/config/websockets.php#L244
Here it sends LARAVEL_WEBSOCKETS_SSL_CA as websockets.ssl.capath
https://github.com/beyondcode/laravel-websockets/blob/efb3aa82b9be93fcdabc1c7e089ab6d2d0aa63d5/src/ServerFactory.php#L118-L120
it is not a bug if you don't know how plugin works or how to use it

Duplicate of #920
Solution without certs config https://github.com/beyondcode/laravel-websockets/issues/920#issuecomment-1010956181 (Workaround rewriting url using https)


Fix SharedLibraryUtil#getLibraryPath returning NUL

The length includes the null-terminator, but memUTF8 assumes there isn't one.

Thank you @octylFractal!


[Discussion] remove the ttl and proxy variables

The ttl and proxy variables can be omitted from the cf api call which will result in them staying the same as they were. As these are not updated dynamically i would suggest omitting them from the script and leaving them to the cloudflare dashboard.

Including the TTL and proxy variables should be fine as Cloudflare defaults to a TTL of 300 seconds for "automatic" and Proxy Status of "true". However, it's possible that the records may get updated by a user or changed by a service that was not intended and the script enforces that with the included variables. This action may be desirable and advantageous to those using the script. Thoughts?

As i see it we have two possible scenarios:

The script auto-updates ttl + proxy
Now if a user wanted to change it, he would have to do it via the script.
If you change something on the Cloudflare dashboard, expecting it to stay this way, you will be dissapointed.

The script doesn't update ttl + proxy
If a user wanted to change these values, he could do so via the cloudflare dashboard (or an api call).
There is no disappointment, because changing these values via the script is impossible.

In my opinion, scenario 2 is much preferable over scenario 1, as there is less that can go wrong.
Of course this is a minor issue, how often do you even update these things. But nonetheless it is something i noticed and I think it would be an improvement to the ux.

I won't lie, the first time I used the script, I didn't understand why my DNS record kept switching to DNS only from Proxied, so even for me I noticed some confusion. Though, another possible option might be to just keep the two variables blank by default, thereby still allowing the choice of the user. That would be a win-win scenario?

Thanks for bringing this up. I've not thought about the possibility of a lock-up by the script if it was predefined. I think what @Wizman87 mentioned is good, leaving it empty with documentation.
Letting users make their own decisions when it comes to configuring the script to their needs.


Problem with Paperspace. No module named "torch."

Tried to add ''import torch'' in mainpapersapceA1111.py file, but this file changes but whenever you run the first cell.

Restart the machine and try again


preserving keys (+ types by key) while mapping over objects (R.mapObjIndexed, R.map)

AFAICT, TS currently doesn't support this. I'd like to leave this as a place-holder for when they would start supporting this though. I think currently this is my main gripe about using Ramda with TS.
Edit: linked issue

Update: so it looks like it should be possible; thanks to the helpful community at the TypeScript repo for helping point that out.
I'm currently still trying to figure out the details though. Anders was already helpful enough to provide a relevant example in his PR:
function mapObject<K extends string | number, T, U>(obj: Record<K, T>, f: (x: T) => U): Record<K, U>;

My current confusion is w.r.t. how I might be able to reapply constructs like the type T5 = { [P in keyof Item]: Item[P] }; so as to be able to have the result types per key be calculated based on the original type in the object for that value along with the function in/out types. Open to ideas.

Made a PR for this here now.

I think in keyof syntax is new in TS 2.1 so it would be required to run it?
For me that is totally OK as I want to add ReadOnlyArray that is only supported in TS 2.0 :-).

Yeah, I'm under the impression it's pretty new. That said, I imagine there shouldn't be too many downsides to upgrading...

This can be supported once 2.2.0 is released as stable. 2.1 is currently in RC, and keyof is currently in the nightlies.

@blakeembrey: Yeah, basic support (preserving keys) is possible with keyof, though as it stands the full intention here (types separate by key, rather than assuming they're all homogeneous) so far isn't it seems -- note TypeScript's mhegazy couldn't quite figure this out yet either, and eventually recommended following this existing thread.
That said, it definitely seems time to jack up this TS version. :)

Sounds great. I just found the thread because I was using pick and the latest nightly, and this issue covered the new keyof feature. I'm sure there's some other places where it'll be useful too. Looking forward to 2.2 stable myself, updating the RethinkDB definition will be lots of fun too 😄

This is mostly blocked by https://github.com/Microsoft/TypeScript/issues/6606, will retry after.


Corrected import / inherited model class

The section for SerializerModel incorrectly showed code importing and using SignalsModel.

Just realized this should be corrected in README.pt.rst as well.


a11y-light fails WCAG AA contrast with gray background

Some of the text color choices fail the 4.5:1 contrast ratio required to meet WCAG AA when the background color is changed from white to gray.
You can see this failure in a code block on the PyData Sphinx Theme website (make sure you are looking at the light theme version, not dark theme).

In that example, the shade of blue used for class and function names, #007faa, against the background gray, #f3f4f5, produces a contrast of 4.1:1, which fails the contrast requirement for regular size text.

cc @trallard

Noting that I plan to work on this mid/late November

👋🏽 Apologies for the drive-by comment.

You can see this failure in a code block on the PyData Sphinx Theme website (make sure you are looking at the light theme version, not dark theme).

This seems to be due to pydata-sphinx-theme overriding the theme's background configuration by setting background-color: var(--pst-color-surface); on <pre> tags. You can see that the .highlight parent of the <pre> tag sets the background color according to the pygments styling.
That CSS variable is related to a user-configurable setting on pydata-sphinx-themes' end (https://pydata-sphinx-theme.readthedocs.io/en/latest/user_guide/styling.html#color-variables).

Hey @pradyunsg, lovely to see you around and thanks for sharing your insights!

This seems to be due to pydata-sphinx-theme overriding the theme's background configuration by setting background-color: var(--pst-color-surface); on  tags.

We are aware of this, and while that could be easily fixed by changing this overwrite in PST, we also realised the themes could improve their contrasts.
Other people/themes are likely customising the background colour, so the upcoming changes in #33  should help cover a broader range of background colours and providing good defaults for some of these customisation cases (note the "some" because we will never be able to support al flavours of customisations)


Error when running examples/execution_profile.rs - EACH_QUORUM ConsistencyLevel is only supported for writes

When running the execution_profile example via SCYLLA_URI="<IP_ADDRESS>:9042" cargo run --example execution_profile the scylla-rust-driver reports Error message: EACH_QUORUM ConsistencyLevel is only supported for writes
examples % SCYLLA_URI="<IP_ADDRESS>:9042" cargo run --example execution_profile
    Finished dev [unoptimized + debuginfo] target(s) in 0.23s
     Running `/Users/practical/OneSignal/scylla-rust-driver/target/debug/examples/execution_profile`
Connecting to <IP_ADDRESS>:9042 ...
Error: Database returned an error: The query is syntactically correct but invalid, Error message: EACH_QUORUM ConsistencyLevel is only supported for writes

It's unclear to me if this error is actually intentional, to demonstrate a query that fails with one profile, but succeeds in another? In which case some clarifying comments might help.
If that's not the case, I wonder if small fix changing consistency from Consistency::EachQuorum to Consistency::Quorum or Consistency::LocalQuorum in the execution_profile example would be useful.

Thanks for the report.
I can confirm that it fails, both on the latest versions of Scylla and on the old Scylla 4.6.
The example was added in https://github.com/scylladb/scylla-rust-driver/pull/592.
I guess it didn't work back then as well, it must've slipped by the review.
I don't think it's intentional, examples should work.

If that's not the case, I wonder if small fix changing consistency from Consistency::EachQuorum to Consistency::Quorum or Consistency::LocalQuorum in the execution_profile example would be useful.

That's a good idea. LocalQuorum would be a good replacement because Quorum is the default value, and the example demonstrates how to override the deafults.

Opened a PR with the fix: https://github.com/scylladb/scylla-rust-driver/pull/840

Awesome!


How to store these emoji's to SQLite database and retrieve them?

Problem storing these emoji's to SQLite database and retrieving them as these emoji's support utf8mb4 encoding which is not supported by SQLite, i suppose. Currently if i try to store and retrieve from database it gives a ?? for each emoji.
How to store and retrieve these to android SQLite database.

I have the same problem.
Does Anyone got any solution ?
I need to save message from EmojiconEditText to database and after get data and show in a EmojiconTextView.
Is it possible ?

Yes indeed i have found one. The data type for the emoji to be stored on
server, needs to be kept as NVARCHAR or equivalent. For me, that solved the
problem of storing and retrieving emoji to and from db.
On 4 Sep 2015 21:39, "Eduardo Gorio"<EMAIL_ADDRESS>wrote:

I have the same problem.
Does Anyone got any solution ?
I need to save message from EmojiconEditText to database and after get
data and show in a EmojiconTextView.
Is it possible ?
—
Reply to this email directly or view it on GitHub
https://github.com/rockerhieu/emojicon/issues/12#issuecomment-137778798.

Have you used SQLite ?

How to get text from EmojiconEditText ?
EmojiconEditText etMessage;
etMessage.getText().toString()

@themitshah could you contact me<EMAIL_ADDRESS>? Thank you

you may store the emoticons from edit text as
StringEscapeUtils.escapeJava(edittext.getText().toString());  to get it in unicode format.
and decode it back to emoticon u can use
textview.setText(StringEscapeUtils.unescapeJava(<unicode_emoticon>));

i through "rails new scaffold p name :string description:text" and i use the sqlite,when the description has emoji,   the sqlite can not store it ,how to deal it?thanks

I don't know if this is applicable to SQLite, but I just get the String from the EditText (EmojiconEditText.getText().toString()), and then de/encode the string as described here

You can save the emoticons into Sqlite db by saving the emoticon's emoji i.e use StringEscapeUtils.escapeJava(EmojiconEditText.getText().toString());
to get the uniocode of the emoji and save it to Sqlite.
To retrieve back the emoticon from that unicode use
StringEscapeUtils.unescapeJava(<unicode_emoticon>);
and set the value received from above to a textview which displays the required emoticon ..

Yes indeed i have found one. The data type for the emoji to be stored on server, needs to be kept as NVARCHAR or equivalent. For me, that solved the problem of storing and retrieving emoji to and from db. On 4 Sep 2015 21:39, "Eduardo Gorio"<EMAIL_ADDRESS>wrote:

I have the same problem.
Does Anyone got any solution ?
I need to save message from EmojiconEditText to database and after get
data and show in a EmojiconTextView.
Is it possible ?
—
Reply to this email directly or view it on GitHub
#12 (comment).

can you post your 'create table sql'


Fix deprecation annotation

Deprecation annotation was done in javadoc but not on the fields themselves, which led to warnings. This commit corrects annotations and removes warnings.
Checklist before you submit for review

[ ] Make sure there is a PR in the CNDB project updating the Converged Cassandra version
[x] Use NoSpamLogger for log lines that may appear frequently in the logs
[ ] Verify test results on Butler
[ ] Test coverage for new/modified code is > 80%
[ ] Proper code formatting
[x] Proper title for each commit staring with the project-issue number, like CNDB-1234
[x] Each commit has a meaningful description
[x] Each commit is not very long and contains related changes
[x] Renames, moves and reformatting are in distinct commits

One new failure was identified, but it doesn't look to be related to the changes and seems to fail previously.


Add testing for the main page

Description
We should add a test that validates that everything is in place in the main page
Screenshots

Additional information
No response

I will take this one


Delegate ECS/ECR access to platform team

Adds an aws_iam_role and associated policy and role policy to delegate ECS and ECR access to the platform team account root, from where it can be further distributed to devs.
This is in order that platform team members have visibility of experience team infrastructure and to provide for emergency infra changes.
It's also mixed in with a terraform fmt because I do not git correctly.

I guess we don't need ECR if you're not storing anything there, up to you if you mind it being there or not.

if you mind it being there or not.

Not fussed, it might just confuse someone later trying to figure out why it's there.

This work allows: https://github.com/wellcometrust/platform-api/pull/637


Allow lazy initialization of trees

When integrating AccessKit with Druid, we'll need to be able to lazily initialize the accessibility tree when the first WM_GETOBJECT message on Windows, or equivalent request on other platforms, is received. I think this requirement will be common enough that it's worth supporting directly in AccessKit. So that's what this branch does.
I've implemented this in a backward-compatible way, so it doesn't break the tests and example, but I suppose I really should update them to lazily initialize and update the tree.

I believe this is ready for review.
My main concern with this change was that it might be necessary to proactively raise UIA focus change events, particularly when the window gained focus, even if we hadn't yet received a WM_GETOBJECT message. But, by studying the relevant code in the open-source WPF repository, testing the modified example with a variety of Windows screen readers, and updating the test infrastructure, I've now convinced myself that it's OK to skip raising focus change events until we've received our first WM_GETOBJECT and lazily initialized the tree.

Very smart! Now the example app is becoming quite complex and I would certainly not understand everything if I had not followed from the start.
It's OK for me, you have some conflicts to fix though.


Document the format of the http access_log

URL for relevant page?
https://docs.influxdata.com/influxdb/v1.7/administration/logs/
What products and version are you using?
InfluxDB 1.6+
Where did you look before opening the issue?
Above link.
Request to document the http access log format that we spew.  Example log line:
<IP_ADDRESS>,<IP_ADDRESS> - - [21/Jul/2019:03:01:27 +0000] "GET /query?db=metrics&q=SELECT+MEAN%28value%29+as+average_cpu%2C+MAX%28value%29+as+peak_cpu+FROM+%22foo.load%22+WHERE+time+%3E%3D+now%28%29+-+1m+AND+org_id+%21%3D+%27%27+AND+group_id+%21%3D+%27%27+GROUP+BY+org_id%2Cgroup_id HTTP/1.0" 200 11450 "-" "Baz Service" d4ca9a10-ab63-11e9-8942-000000000000 9357049
I think the format is:
	return fmt.Sprintf(`%s - %s [%s] "%s %s %s" %s %s "%s" "%s" %s %d`,
		host,
		detect(username, "-"),
		start.Format("02/Jan/2006:15:04:05 -0700"),
		r.Method,
		uri,
		r.Proto,
		detect(strconv.Itoa(l.Status()), "-"),
		strconv.Itoa(l.Size()),
		detect(referer, "-"),
		detect(userAgent, "-"),
		r.Header.Get("Request-Id"),
		// response time, report in microseconds because this is consistent
		// with apache's %D parameter in mod_log_config
		int64(time.Since(start)/time.Microsecond))

From: influxdb/services/httpd/response_logger.go

Let's add this to the platform documentation section.

@timhallinflux I'm wondering if it makes more sense for this to go in the influxdb logs documentation (https://docs.influxdata.com/influxdb/v1.7/administration/logs/) instead?

yeah...I think you are right.


Metadata API request failed: request to https://../services/Soap/m/##.0 failed, reason: getaddrinfo EAI_AGAIN

I've seen this bug since switching to the sf CLI, including the most recent build. It happens randomly and isn't reproducible. Seen while running sf project deploy start and sf project deploy validate commands.
I understand EAI_AGAIN is a DNS issue, but I've seen previous CLI bugs such as the "Org Cannot Be Found" error be temporarily resolved by disabling the DNS check with the environment variable. SF_DISABLE_DNS_CHECK=true
I am running the CLI in a GitLab CI/CD environment with Kubernetes (K8s) runners and the latest Ubuntu container.
My question is where specifically in the code base is this error raised? Does this occur when the CLI determines the latest API version available in the Org? Will disabling the DNS check resolve this issue and is there any downsides to disabling the DNS? If I keep the maximum API version stored in the sfdx-project.json file in my VCS, I don't see the need for the additional API version check done by the DNS.
Please let me know what I can do to hopefully remove this Metadata API failure.
Steps To Reproduce
Cannot re-produce this type of bug.
Seen while running these commands:
sf project deploy start for deploy (non-apex)
sf project deploy validate for validations ahead of quick-deploys (apex)
sf project deploy quick  for quick-deploys (apex)
Expected result
CLI final status matches the Salesforce Deployment Status.
Actual result
Pipelines using the CLI occasionally fail with this error as the deployment continues in the Salesforce Org.
System Information
Bash / Ubuntu Docker Image (latest) / GitLab CI/CD with Kubernetes runners
We build our Custom Docker Image using this Dockerfile:
We have also seen this while using alpine:latest before we switched to Ubuntu.
FROM ubuntu:latest

# Set Salesforce CLI Environment Variables
ENV SF_AUTOUPDATE_DISABLE=true \
    # ^-- By default, the CLI periodically checks for and installs updates.
    #     Disable (false) this auto-update check to improve performance of CLI commands.
    SF_USE_GENERIC_UNIX_KEYCHAIN=true \
    # ^-- Set to true if you want to use the generic UNIX keychain instead of the Linux libsecret library or macOS keychain.
    #     Specify this variable when using the CLI with ssh or "headless" in a CI environment.
    SF_DOMAIN_RETRY=300 \
    # ^-- Specifies the time, in seconds, that the CLI waits for the Lightning Experience custom domain to resolve and become available in a newly-created scratch org.
    #     If you get errors about My Domain not configured when you try to use a newly-created scratch org, increase this wait time.
    SF_PROJECT_AUTOUPDATE_DISABLE_FOR_PACKAGE_CREATE=true \
    # ^-- For force:package:create, disables automatic updates to the sfdx-project.json file.
    SF_PROJECT_AUTOUPDATE_DISABLE_FOR_PACKAGE_VERSION_CREATE=true \
    # ^-- For force:package:version:create, disables automatic updates to the sfdx-project.json file.
    SF_DISABLE_DNS_CHECK=true
    # ^-- Disable the DNS check done when looking for the latest API version in the org.

# Install python3, nodejs, npm, Salesforce CLI, and output versions
RUN apt-get update && apt-get install -y curl python3 && \
    curl -fsSL https://deb.nodesource.com/setup_lts.x | bash - && \
    apt-get install -y nodejs && \
    npm install --global<EMAIL_ADDRESS>&& \
    sf version --verbose --json

{
  "cliVersion"<EMAIL_ADDRESS>  "architecture": "linux-x64",
  "nodeVersion": "node-v18.17.1",
  "osVersion": "Linux 5.15.108",
  "shell": "bash",
  "rootPath": "/usr/lib/node_modules/@salesforce/cli",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 2.3.8 (core)",
    "@oclif/plugin-commands 2.2.25 (core)",
    "@oclif/plugin-help 5.2.19 (core)",
    "@oclif/plugin-not-found 2.4.1 (core)",
    "@oclif/plugin-plugins 3.7.1 (core)",
    "@oclif/plugin-search 0.0.22 (core)",
    "@oclif/plugin-update 3.2.3 (core)",
    "@oclif/plugin-version 1.3.10 (core)",
    "@oclif/plugin-warn-if-update-available 2.1.0 (core)",
    "@oclif/plugin-which 2.2.32 (core)",
    "@salesforce/cli 2.10.2 (core)",
    "apex 2.3.15 (core)",
    "auth 2.8.17 (core)",
    "data 2.5.9 (core)",
    "deploy-retrieve 1.18.0 (core)",
    "info 2.6.43 (core)",
    "limits 2.3.34 (core)",
    "login 1.2.31 (core)",
    "marketplace 0.2.2 (core)",
    "org 2.10.8 (core)",
    "schema 2.3.26 (core)",
    "settings 1.4.29 (core)",
    "sobject 0.2.7 (core)",
    "source 2.10.34 (core)",
    "telemetry 2.3.3 (core)",
    "templates 55.5.12 (core)",
    "trust 2.6.13 (core)",
    "user 2.3.32 (core)"
  ]
}

Additional information

Hello Team,
While pushing to sandbox for review through CLI we are getting below mentioned error .
Support pointed us towards here saying this is a CLI issue and not associated with deployment error.
Metadata API request failed: request to https://xyz--review.sandbox.my.salesforce.com/services/Soap/m/60.0 failed, reason: getaddrinfo EAI_AGAI
cc: @mcarvin8

I still see this failure all the time in our CI pipelines and locally. I closed this because I went back and forth with the team who maintains our Kubernetes runners for my work's CI infrastructure and Salesforce support.
These Metadata API request failures are pretty frequent in any environment (CI and local) and I'm starting to see metadata api requests failures without any error statement like EAI_AGAIN.
Feel free to raise this issue but I threw in the towel after the back and forth.


Added Features card medium filled

Solved Issue #114

Good job @AmitDeka
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


Blob.text and Blob.arraybuffer are 10x+ slower on 20.x

The blob/blob.js benchmark is taking hours: https://ci.nodejs.org/view/Node.js benchmark/job/benchmark-node-micro-benchmarks/1402/console
This probably didn't take so long in the past, there is this PR that changed the Blob's behavior a lot: https://github.com/nodejs/node/pull/45258/
From what I saw, the problem is in the JS->C++ transitions, for each piece of data it crosses JS->C++.
Furthermore, the text function expects arraybuffer and then calls decode, when we could just decode the data as soon as we get it from the C++ instead of keeping everything in memory and then discarding it.
I can do some optimizations on the JS side but I think this could be largely improved if we do the heavy operations on C++, I have no idea how to handle the asynchronous code on C++, so I accept some hints or if anyone wants to try work on this.

Some benchmark data:
NodeJS 16.20.1

name
ops/sec
samples

text (128)
17,269
57

text (1024)
10,257
57

arrayBuffer (128)
24,974
53

arrayBuffer (1024)
10,955
57

slice (0, 64)
48,310
67

slice (0, 512)
23,750
66

NodeJS 18.17.0

name
ops/sec
samples

text (128)
36,176
74

text (1024)
13,691
69

arrayBuffer (128)
36,788
74

arrayBuffer (1024)
14,305
75

slice (0, 64)
49,139
71

slice (0, 512)
26,774
76

NodeJS 20.5.0

name
ops/sec
samples

text (128)
3,194
74

text (1024)
380
76

arrayBuffer (128)
3,478
80

arrayBuffer (1024)
407
75

slice (0, 64)
45,076
66

slice (0, 512)
16,484
64

@jasnell @flakey5

@H4ad run a git bisect to find where the regression is?

@benjamingr I will!
Also, this regression was so hard to run this piece of code:

const buff = Buffer.allocUnsafe(1024 ** 2);
const source = new File(buff, 'dummy.txt', options);

const now = performance.now();
source.text().then(() => console.log(`diff: ${performance.now() - now}`));

It took 3s on node 20.x and 80ms on 18.x.

Which public api affected by this?

If I understand your question, File is from Buffer which inherits Blob, so any code that inherits and uses Blob will be slowdown when calling the text or arraybuffer.
From what I read, undici uses File and Blob to handle multipart/form-data and files.

This will be a tricky one as the new mechanism underlying the C++ implementation of Blob is also going to be used for the QUIC implementation that I'm currently working on. It also serves as the underlying bit for file-backed Blob. There is lots of room for performance improvement here but I would appreciate this not being changed right at this moment as it could lead to conflicts with the ongoing QUIC implementation work. What would probably be the most valuable right now would be just identifying where the key bottlenecks -- identifying those so that we can circle back around to making those pieces faster.

In the QUIC implementation, you are changing the Blob?

Making an initial attempt here https://github.com/nodejs/node/pull/49873 just stuck on how to make the pulling part async similar to how we are doing queueMicrotask in js in cpp

so I kinda did git bisect and I suspect it was either created by:

https://github.com/nodejs/node/pull/47320

or created by those:

36f36b99b0dc2cf747aa99a316b2678234acfdcb
9b6270afe23ee165d33cca7890ec63e8ad8f8bc7

Hmm the main problem seems like we pass callback -> callback again passes back value after reading -> repeat 2 JS -> C++ and back calls everytime data being read

just stuck on how to make the pulling part async similar to how we are doing queueMicrotask in js in cpp, Is there maybe some sort of way to queue jobs in c++ part

Pretty sure you were looking for v8::Isolate::EnqueueMicrotask

ahah yes! would do the job i guess but bigger problem rn is how to queue them described in https://github.com/nodejs/node/pull/49873#issuecomment-1736024886

@jasnell how is going the QUIC Implementation? Do you think we can go back and look for ways to optimize or do you think we should wait until we have more updates on the QUIC implementation?

Made some progress on this in https://github.com/nodejs/node/pull/49873 but stuck on some C++ pointer stuff if anyone could help or take a look would be great


fix(blockifier): get alias from last state diff

This change is

#2767
#2946  👈 (View in Graphite)
main-v0.13.4

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

Merge activity

Dec 26, 7:50 AM EST: Graphite disabled "merge when ready" on this PR due to: a merge conflict with the target branch; resolve the conflict and try again..


symlink creation on windows corrected

corrects the error symlink(): permission denied on windows

Thanks @nicola-inchingolo-aslbat


docs[minor]: Add missing {context} variable in example

The example included under the deprecated RetrievalQAChain method is missing the required {context} variable.
The createStuffDocumentsChain "expects a dictionary as input with a list of Documents being passed under the "context" key." as per the specs.
If one tries to replicate the example without including the {context} variable in the prompt template, the following error is produced:

prompt must include a "context" variable

Which is based on DOCUMENTS_KEY = "context";
I believe the example must include the required variable to avoid any confusion and streamline the process of migrating to the alternative syntax.

Thanks!


Update Air Gap Docs to include mirroring rancher server chart repo

Continuation of #808
https://github.com/rancher/docs/pull/808#issuecomment-422883929

We also need to document mirroring the rancher server chart repository, e.g. either by

Creating a local helm repository to host the rancher server chart from https://github.com/rancher/server-chart,
or
Probably better: How to pull the packaged archive of rancher server chart and then use helm to deploy from that local package.

Removing dependency on tiller and remote charts. Charts can be fetched and rendered on a system with internet access and copied to a system that has access to the cluster. #854

I think this has been added to the docs already:

HA air gap docs about preparing a private registry: https://rancher.com/docs/rancher/v2.x/en/installation/air-gap-high-availability/prepare-private-registry/
Single node air gap docs about preparing a private registry: https://rancher.com/docs/rancher/v2.x/en/installation/air-gap-single-node/prepare-private-registry/

@MBishop17, can this issue be closed?


editor.bind not available

I'm trying to attach event handlers to the EditorApp within a an angular directive.
                // Initialise the editor
                scope.editor = new ContentTools.EditorApp.get();
                scope.editor.init('[ip-editor]', 'ip-editor');
                // Bind a function on editor save
                scope.editor.bind('save', function(regions, autoSave) {

                    scope.$apply(function(){
                        scope.regions = regions;
                    });

                    // "regions" contains all the html for each editable regions
                    // Now, "regions" can be saved and used as needed.

                });

This code comes from an example contenttools-angularjs project
It states however that the editor instance doesn't have a bind function.

The bind method in the ContentTools UI has been replaced with addEventHandler method now (see release 1.2.0 for details).
The implementation of save is pretty similar still, the above code would now become:
// Initialise the editor
scope.editor = new ContentTools.EditorApp.get();
scope.editor.init('[ip-editor]', 'ip-editor');

// Bind a function on editor save
editor.addEventListener('saved', function (ev) {
    scope.$apply(function(){
        scope.regions = regions;
    });

    // ...
});

Thanks... works like a charm.


BC42328 could be a little better explained

I have some AddHandlers and RemoveHandlers that all seem quite similar, so I have no clue why one is throwing this warning, and others aren't. This article is not particularly helpful, and when I did the Alt+Enter to show the potential fix (It basically just moved the RemoveHandler line in question to a new method), it showed the same warning on the "fixed" version!
It's also strange that it says the AddressOf expression "has no effect", when it has the effect of allowing a successful compile... not having one there is a syntax error.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 592d581c-131c-5835-4fe5-b9d44a0c5786
Version Independent ID: 88ccadb3-7e46-599f-66f5-5d335eb51961
Content: The 'AddressOf' expression has no effect in this context because the method argument to 'AddressOf' requires a relaxed conversion to the delegate type of the event
Content Source: docs/visual-basic/misc/bc42328.md
Product: dotnet-visualbasic
GitHub Login: @KathleenDollard
Microsoft Alias: kdollard

@ocdtrekkie Can you paste a small snippet of the code to show me an example where this is failing?

I have to be honest: I don't remember if I got the message to go away or not, but this is the file I was working on the day that I filed this issue: https://github.com/ocdtrekkie/HAController/blob/master/modSync.vb
I just have no idea what BC42328 was trying to tell me. AddHandler and RemoveHandler require the AddressOf, so I don't know what it means by "has no effect".

@KathleenDollard can you take a look at this one?

I suggest we simply close this. This seems to be a response to a scenario the user can get into. We cannot reproduce it so we have no idea whether it is helping people and no way to make it better.

I mean, I know something extremely nonsensical was happening here. Something can't simultaneously have no effect and be required at the same time.
I can try to see if I can reproduce it again, but basically it was just that by the time someone responded here, I forgot where I left the issue.
Sent from my Windows 10 device
From: Kathleen Dollard
Sent: Tuesday, April 30, 2019 2:55 PM
To: dotnet/docs
Cc: Jacob Weisz; Mention
Subject: Re: [dotnet/docs] BC42328 could be a little better explained (#10157)
I suggest we simply close this. This seems to be a response to a scenario the user can get into. We cannot reproduce it so we have no idea whether it is helping people and no way to make it better.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Apologies on that. If you run into that again, let us know!

This fixed this warning for me: https://github.com/ocdtrekkie/HAController/commit/9d89361e297fe85783598eab2f783a2174efc61b
Apparently RemoveHandler really wants that (sender, e) on it. But I also then wasn't able to use the same Sub when I kicked it off with a Threading.Thread.
I still think the warning message makes no sense in any way shape or form, and should be revised, because neither the message nor the proposed fix was helpful.

This fixed this warning for me: https://github.com/ocdtrekkie/HAController/commit/9d89361e297fe85783598eab2f783a2174efc61b
Apparently RemoveHandler really wants that (sender, e) on it. But I also then wasn't able to use the same Sub when I kicked it off with a Threading.Thread.
I still think the warning message makes no sense in any way shape or form, and should be revised, because neither the message nor the proposed fix was helpful.

Also, note that @DualBrain is who got my years-old warning gone. \o/

Also, note that @DualBrain is who got my years-old warning gone. \o/

@dotnet/docs Stale-botting issues after 9 days where Microsoft averages over a month to respond isn't ideal. :/
I resolved my code issue, but I still don't understand what this compiler error was trying to say, and the suggested fix in IntelliSense actually broke the code further.

@dotnet/docs Stale-botting issues after 9 days where Microsoft averages over a month to respond isn't ideal. :/
I resolved my code issue, but I still don't understand what this compiler error was trying to say, and the suggested fix in IntelliSense actually broke the code further.

I had this warning turn up and found this thread after some Googling. Mine was a handler to a Toggleswitch.Toggled handler and I had (sender as Toggleswitch, e as RoutedEventArgs). Changing the sub declaration to (sender as Object, e as RoutedEventArgs) fixed it.
What it actually means I cannot begin to understand.


OAuth app loses assignements when updating

Hi, I have an OAuth app followed by a group assignment:
app = okta.app.OAuth("app"
    label="app",
    type="web",
    grant_types=["authorization_code"],
    hide_web=False,
    response_types=["code"],
    opts=pulumi.ResourceOptions(provider=provider))

okta.app.GroupAssignment(mygroup,
    app_id=app.id,
    group_id=<group id>,
    opts=pulumi.ResourceOptions(parent=app, provider=provider))

If I do any change to the OAuth app, like for example changing hide_web from False to True, only that resource will change, but in Okta the group is no longer assigned to the application.

When you perform the update, does it show an update being applied to the group assignment?

No, it only shows an update to the hideWeb field:
 ~   ├─ okta:app:OAuth       àpp      update     [diff: ~hideWeb]

Just as a note, I've just tried using version 2.4.0 of the Plugin, which was released yesterday, and the problem still persists.
As a workaround I've been using the group and user input property of app.OAuth, which the documentation says it's not recommended, but works.

I've now followed the warning on the documentation and added an ignore_changes on the app.OAuth resource, but still made no difference:
app = okta.app.OAuth("app"
    label="app",
    type="web",
    grant_types=["authorization_code"],
    hide_web=False,
    response_types=["code"],
    opts=pulumi.ResourceOptions(ignore_changes=["groups", "users"], provider=provider))

I want to point out that this only made sense after I read this latest patch upstream, which actually explains why that would be needed: https://github.com/oktadeveloper/terraform-provider-okta/pull/172/files
For reference:

!> NOTE When using this resource in conjunction with other application resources (e.g. okta_app_oauth) it is advisable to add the following lifecycle argument to the associated app_* resources to prevent the groups being unassigned on subsequent runs:

So I think this is definitely related to my problem, but the solution doesn't work for me.

If there's no diff, then I wouldn't expect any changes to be made in the provider, so I'm not sure why the group would no longer be assigned. If you run a pulumi refresh is it able to read the state of the group assignment?

I've now followed the warning on the documentation and added an ignore_changes on the app.OAuth resource, but still made no difference:
app = okta.app.OAuth("app"
    label="app",
    type="web",
    grant_types=["authorization_code"],
    hide_web=False,
    response_types=["code"],
    opts=pulumi.ResourceOptions(ignore_changes=["groups", "users"], provider=provider))

I want to point out that this only made sense after I read this latest patch upstream, which actually explains why that would be needed: https://github.com/oktadeveloper/terraform-provider-okta/pull/172/files
For reference:

!> NOTE When using this resource in conjunction with other application resources (e.g. okta_app_oauth) it is advisable to add the following lifecycle argument to the associated app_* resources to prevent the groups being unassigned on subsequent runs:

So I think this is definitely related to my problem, but the solution doesn't work for me.

I'm having the exact same problem. Have you found a workaround?
I tried adding the DeleteBeforeReplace option and this doesn't seem to work either. I verified in the console that the application is not deleted and that it still creates the Okta Application with the same ID. I dont think the custom resource options is being applied to Okta resources.
}, new CustomResourceOptions {                             DeleteBeforeReplace = true, IgnoreChanges = new List<string> { "groups" }                        });

I'm sorry, I don't use Okta any more, so I can't help with this issue.

Just to share, I do not have this error when updating my oauth app. But I'm not defining the flag hideWeb, I can change any property in my app that it will update without removing the group assign.
export const myApp = new okta.app.OAuth('okta-facade-health-test', {
    label: 'My label',
    type: 'native',
    status: config.status,
    grantTypes: ['authorization_code', 'password'],
    responseTypes: ['code'],
    tokenEndpointAuthMethod: 'client_secret_basic',
    clientId: config.clientId,
    clientBasicSecret: config.clientSecret,
    redirectUris: [
        `https://${okta.config.orgName}.${okta.config.baseUrl}/callback`
    ],
    postLogoutRedirectUris: [
    ],
});

But I tried to add hideWeb=True just to test and it indeed remove the group assignment once I ran the code. I can see the changes in the update, not sure why it's removing the group. Weird I don't see the hideweb changes.

After I tried to remove the hideWeb=True and the group was not assigned back, it just changed this property I was adding.

Unfortunately, it looks like this issue hasn't seen any updates in a while. If you're still encountering this problem, could you leave a quick comment to let us know so we can prioritize it?


tags: parse "line:" and use it for search

Fixes https://github.com/vim/vim/issues/1057.

so could you fix those TODOS and possibly add a test?

Please add a test.

Should it go into src/testdir/test_tagjump.vim?
Any feedback on my comments/questions in the PR?

Any feedback on my comments/questions in the PR?

I did not see any, besides your comments to fix some points...

Any update?


Fix Paxos V2 prepare response serialization

Patch by Ariel Weisberg; Reviewed by David Capwell for CASANDRA-19023

Found a bug in size calculation as well. Removed serializedRejection and put the serialization of maybeConsensusMigratedAt at the end so it doesn't need to be repeated for accept/reject.


Multiple Check-Ins for the same Event (QR-Code) are possible

Avoid duplicates

[X] Bug is not mentioned in the FAQ
[ ] Bug is specific for Android only (cannot identify, have only Android)
[X] Bug is not already reported in another issue

Describe the bug
I can check-in multiple times to the same event, represented by its QR code.
This is obviously not sensible and could be avoided.
See attached screenshot.

Steps to reproduce the issue
Create QR code on one device.
Check in multiple times using another device.
Expected behaviour
I think, re-scanning the same QR code while a check-in for the same QR code is still active should update the existing check-in and prolong its check-in time by the "default check-in time" of the event.
Example: Default check-in time is 2 hours.
I checked in 1 hour ago. I now check in again.
Result: I still have only one active checkin, and it will automatically check out two hours from now.
Less good would be an error message "You are already checked in here".

Confirm same bug under iOS.

@jkrwdf I suggest that you open a separate feature request for this in the https://github.com/corona-warn-app/cwa-wishlist repository.

There also some person which visit multiple rooms on an event at the same time. For example waiters or visitor on conferences. We don't want to restrict here to much.

How about if scanning same QR code again, the automatic check out time is added to the remaining time of that event/location?

@vaubaehn I think this suggestion is not as realistic as the approach to set the checkout time of the event in that case to the current time plus 1 times the automatic checkout time. In my initial example, I would have 6 hours otherwise.

@jkrwdf

@vaubaehn I think this suggestion is not as realistic as the approach to set the checkout time of the event in that case to the current time plus 1 times the automatic checkout time. In my initial example, I would have 6 hours otherwise.

True, but I can imagine different use cases, where I would find it comfortable for myself.
What about, if CWA asked you what to do, if you scanned the same QR code again while still being checked in?
Possible options:
-> cancel (dismiss scan/don't check in again)
-> add (automatic checkout) time to remainng time
-> modify check in time/remaining time manually (while still being checked in)
If someone found this useful, I'm not sure if this is a bug fix or an enhancement request...


Get Electric Cinema data

There are 2 electric cinema venues
Data for both is embedded into the HTML page -- https://www.electriccinema.co.uk/
/* <![CDATA[ */
var electric = { ... };
/* ]]> */

Added ✅


⚠ Bofrost.be has degraded performance

In 4c0b3b6, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2536 ms

Resolved: Bofrost.be performance has improved in 8f36209.


Add OpenSearch Exporter to the Contrib Manifest

Description
The OpenSearch exporter was recently merged to the contrib repo
It is not yet present in the otel contrib distrbution
Additional info

https://github.com/open-telemetry/opentelemetry-collector-releases/blob/main/distributions/otelcol-contrib/manifest.yaml

  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/opensearchexporter v0.83.0

cc code owners @Aneurysm9 @MitchellGale @MaxKsyunz @YANG-DB

cc code owners @Aneurysm9 @MitchellGale @MaxKsyunz @YANG-DB

The exporter needs to be add to otelcontribcol. I'll submit a PR for that.
Is there anything else necessary before it can be marked as Alpha?

The CI will fail if you try to move to alpha and miss anything.


python312Packages.gaphas: 4.0.0 -> 4.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.gaphas is: GTK+ based diagramming widget
meta.homepage for python312Packages.gaphas is: https://github.com/gaphor/gaphas
meta.changelog for python312Packages.gaphas is: https://github.com/gaphor/gaphas/releases/tag/4.1.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.1.1 with grep in /nix/store/nk157r0dv2n02507pwpz7yvpzn9s75ph-python3.12-gaphas-4.1.1
found 4.1.1 in filename of file in /nix/store/nk157r0dv2n02507pwpz7yvpzn9s75ph-python3.12-gaphas-4.1.1

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

gaphor
python311Packages.gaphas
python312Packages.gaphas

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nk157r0dv2n02507pwpz7yvpzn9s75ph-python3.12-gaphas-4.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.gaphas https://github.com/r-ryantm/nixpkgs/archive/b067dc0a68b581d12a388d9ba7cf1f4ae84ea4f6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b067dc0a68b581d12a388d9ba7cf1f4ae84ea4f6#python312Packages.gaphas

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nk157r0dv2n02507pwpz7yvpzn9s75ph-python3.12-gaphas-4.1.1
ls -la /nix/store/nk157r0dv2n02507pwpz7yvpzn9s75ph-python3.12-gaphas-4.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages failed to build:

gaphor
gaphor.dist

4 packages built:

python311Packages.gaphas
python311Packages.gaphas.dist
python312Packages.gaphas
python312Packages.gaphas.dist

Maintainer pings

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

gaphor should be fixed in https://github.com/NixOS/nixpkgs/pull/335627


Mamba2 constantly gives error regarding  causal_conv1d: strides (x.stride(0) && x.stride(2)) to be multiples of 8

HI,
I am trying to play with Mamba2. I tried several options when it comes to input dim. However, I constantly getting error as below.
from mamba_ssm import Mamba2
batch, length, dim = 100, 64, 64
x = torch.randn(batch, length, dim).to("cuda")
model = Mamba2(
# This module uses roughly 3 * expand * d_model^2 parameters
d_model=dim, # Model dimension d_model
d_state=128,  # SSM state expansion factor, typically 64 or 128
d_conv=4,    # Local convolution width
expand=2,    # Block expansion factor
headdim=dim,
).to("cuda")
y = model(x)
File C:\ProgramData\anaconda3\Lib\site-packages\mamba_ssm\ops\triton\ssd_combined.py:930 in mamba_split_conv1d_scan_combined
return MambaSplitConv1dScanCombinedFn.apply(zxbcdt, conv1d_weight, conv1d_bias, dt_bias, A, D, chunk_size, initial_states, seq_idx, dt_limit, return_final_states, activation, rmsnorm_weight, rmsnorm_eps, outproj_weight, outproj_bias, headdim, ngroups, norm_before_gate)
File C:\ProgramData\anaconda3\Lib\site-packages\torch\autograd\function.py:575 in apply
return super().apply(*args, **kwargs)  # type: ignore[misc]
File C:\ProgramData\anaconda3\Lib\site-packages\torch\amp\autocast_mode.py:465 in decorate_fwd
return fwd(*args, **kwargs)
File C:\ProgramData\anaconda3\Lib\site-packages\mamba_ssm\ops\triton\ssd_combined.py:779 in forward
causal_conv1d_cuda.causal_conv1d_fwd(rearrange(xBC, "b s d -> b d s"),
RuntimeError: causal_conv1d with channel last layout requires strides (x.stride(0) && x.stride(2)) to be multiples of 8
Exception raised from causal_conv1d_fwd at C:\Users\roman\AppData\Local\Temp\pip-req-build-ph0joy5p\csrc\causal_conv1d.cpp:162 (most recent call first):
00007FFDDA6E83C900007FFDDA6E8320 c10.dll!c10::Error::Error [ @ ]
00007FFDDA6E6BEA00007FFDDA6E6B90 c10.dll!c10::detail::torchCheckFail [ @ ]

same as you

try this issue


Question: How to debug a "Unable to retrieve templates" error

Question:
I'm getting a "Unable to retrieve templates" error on portainer while trying to access the templates section after configuring it to use a custom template.
I already tried to see if it was a network problem by creating a new container on the same network as the portainer one and I was able to successfully wget the template file link.
I also saw no log entries about this issue on the container logs.
How can I check the real reason why portainer was unable to retrieve the templates?
Here's a screenshot of the referenced error:

Hi @deviantony!
I was using a HTTPS URL, changed it to HTTP and the error is still happening.
What do you mean exactly by "inspect the failed request response"?

Hey @vboufleur
Do you know how to use browser developer tools? For example, in Chrome you can hit F12, reload the page, go to the network tab, select the request that is failing (in your case something like /templates) click on it and inspect the reponse in the response tab.

@deviantony I got only 200 ok responses

Ok I've solved it. For future reference, my portainer app template file had no opening and closing brackets.
Can't be:
{
    "type": "stack",
    .
    .
    .
}

Has to be:
[
  {
    "type": "stack",
    .
    .
    .
  }
]

Have the same problem. Lets see if I can describe all my configuration.
I have created the portainer docker with the command:
sudo docker create --name=pidocker \
--restart=always \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /media/Multimedia/home/helio/docker_data/portainer/data/:/data \
-v /media/Multimedia/home/helio/docker_data/portainer/shared/:/shared \
-e PGID=0 -e PUID=0 \
-e TZ=Europe/London \
-p 8001:8000 \
-p 9000:9000 \
portainer/portainer-ce

The app templates is the default in the installation:

When I go to app templates I get the error:

Looking the chrome debug:

Looging the portainer logs:
2020/12/05 17:19:18 http error: Unable to retrieve templates via the network (err=Get https://raw.githubusercontent.com/portainer/templates/master/templates-2.0.json: Bad Request) (code=500)

Trying to reach the url from the docker host:
$ sudo docker ps | grep portai
104df52cb3fe        portainer/portainer-ce   "/portainer"             2 hours ago         Up 2 hours          <IP_ADDRESS>:9000->9000/tcp, <IP_ADDRESS>:8001->8000/tcp   pidocker
$
$ wget https://raw.githubusercontent.com/portainer/templates/master/templates-2.0.json
--2020-12-05 17:21:53--  https://raw.githubusercontent.com/portainer/templates/master/templates-2.0.json
A resolver raw.githubusercontent.com (raw.githubusercontent.com)...<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
A conectar raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... conectado.
Pedido HTTP enviado, a aguardar resposta...200 OK
Tamanho: 25759 (25K) [text/plain]
Saving to: ‘templates-2.0.json’

templates-2.0.json            100%[=================================================>]  25,16K  --.-KB/s    in 0,005s

2020-12-05 17:21:53 (4,67 MB/s) - ‘templates-2.0.json’ saved [25759/25759]

My nginx configuration to reach portainer from browser:
    location / {

        proxy_http_version 1.1;
        proxy_set_header Host $host;
        proxy_set_header Connection "";
        proxy_pass http://localhost:9000; # Portainer

        #access_log off;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }

    location /api/websocket/ {
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_http_version 1.1;
        proxy_pass http://localhost:9000/api/websocket/;
    }

Can someone point me what do I need to do to get App Templates running?

Have exactly the same problem on my synology nas

Have exactly the same problem on my synology nas

@Justinio99
Verify that the Synology firewall settings under Security\Firewall in DSM are not blocking the port used by Portainer to fetch the templates.  You will get that error if that is the case.

@Justinio99
Verify that the Synology firewall settings under Security\Firewall in DSM are not blocking the port used by Portainer to fetch the templates. You will get that error if that is the case.

THis worked for me. For anyone who is interested:

whitelist(Allow) this IP range with subnet <IP_ADDRESS> in Security/Firewall

Can someone point me what do I need to do to get App Templates running?

@heliomcp  Have you solved this? I'm unable to get the default template too! Happens the same with docker host able to download it...
Here i try another template from Github yet the problem persists. I'm on Portainer CE 2.11.0

In case anyone else is still facing this issue - you need to update your firewall settings and in my case it was the firewall settings in my synology NAS (security>firewall>firewall profile>edit rules).

Which ports.... I opened heaps of ports yet still says another port is closed....

For the error message @sirdeniel was having, I just updated my container to 2.13.1 and the error is gone. Seems to be a 2.11 issue.

iner to 2.13.1 and the error is gone. Seems to be a 2.11

I was facing the same problem even on Portainer 2.14.2.
So I copy pasted the templates-2.0.json and added [ ] brackets around the {} as @vboufleur explained.

Hello all,
I am running docker on my Synology NAS, and have a very similar issue. I have no firewall set up on my NAS, can someone assist me with debugging this?


hmedians not found

In the notebook dcal/DCAL_Land_Change.ipynb in step 20 I get the following error:
---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
<ipython-input-20-9740b870cefe> in <module>()
----> 1 from utils.data_cube_utilities.dc_mosaic import ls8_unpack_qa, ls7_unpack_qa
      2
      3 unpack_function = {"LANDSAT_7": ls7_unpack_qa,
      4                    "LANDSAT_8": ls8_unpack_qa}
      5

~/examples/dcal/utils/data_cube_utilities/dc_mosaic.py in <module>()
     28 import collections
     29 from collections import OrderedDict
---> 30 import hdmedians as hd
     31
     32 import datacube

ModuleNotFoundError: No module named 'hdmedians'

Hey @chriscmorgan this is an issue again. Can you please check out if it's still being installed?


RC.4 Nightly Issue: Slides options ignored

Ionic version:
2.0.0-rc.4-201701062325
I'm submitting a ...
bug
Current behavior:
In my app I built a wizard based on the Slides component. It's the core process of my app.
To handle the different the wizard and guide the user across the different steps, I use the Slides' option "onlyExternal = true" to disable the default behavior of allowing the user to swipe across the different slides. Furthermore, I also set the pager to false because I don't want to show a pager.
Today I tried the last nightly and it turns out that setting "onlyExternal = true"  (just for trying) hasn't got any effects anymore. Even with that option, I was able to swipe between slides aka to swipe across my wizard without feeling informations.
For "fun" I tried to activate the pager = true, this had no effect too.
Expected behavior:
The Slides' option "onlyExternal = true" when activated, should works as before aka don't allow user to swipes the slides.
Same for pager, when activated, a pager should be displayed.
Steps to reproduce:
Create a slides with "onlyExternal = true and at least to slides. Try to swipe, shouldn't not be possible.
Related code:
<ion-slides #newAdSlider [options]="newAdSlideOptions" (ionSlideDidChange)="onSlideChanged()">
 </ion-slides>

constructor() {
     this.newAdSlideOptions = {
        initialSlide: 0,
        loop: false,
        pager: true,
        onlyExternal: true
    };
}

Ionic info:
Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-rc.4-201701062325
Ionic CLI Version: 2.1.18
Ionic App Lib Version: 2.1.9
Ionic App Scripts Version: 0.0.48
ios-deploy version: 1.9.0
ios-sim version: 5.0.13
OS: macOS Sierra
Node Version: v7.2.1
Xcode version: Xcode 8.2.1 Build version 8C1002
P.S.: Hi @jgw96 I saw that you seems to work on the sliders according different issues, thought maybe this information may interest you

The documentation about the attribute pager boolean doesn't seems to be correct neither in slides.d.ts
/**
 * @input {boolean}  String with type of pagination. Can be
 * `bullets`, `fraction`, `progress`. Default does not have
 * pagination set.
 */
pager: boolean;
private _pager;

Last update ;)
I found a way to activate the pager by setting it to true in the html code like following, but this means that by default it isn't active as documented..
<ion-slides  pager="true"> <!-- ==> Gonna work, page gonna be active only if explicitly written down -->

Furthermore to that, seems that this version introduce a new default color (blue) for the active pager instead of black as it was...
.swiper-pagination-bullet-active {
background: #007aff;
}

Hey @peterpeterparker , thanks for opening an issue with us! So looks like you have ran into one of the dangers of running nightly, currently un-documented changes (: . So all the options for ion-slides should now be passed as attributes to ion-slides. This is going to be in the changelog for our next release. I will look into the issue you are seeing with the pager not being active by default and the pager bullet being blue. Thanks for all the detailed info on this!

Hey @peterpeterparker could you point me to where you see that we document that the pager option is true by default? Im looking here and see that we document pager as being false by default.

@jgw96 thx a lot for your feedback. look like I was dreaming you are absolutely right, pager is set per default to false, sorry for the false information and loosing your time.
yep I ran into some dangers of running the nightly, but it was for good purpose, wanted/had to tests other issues related to the nightly (which are now solved).

No problem at all, very glad to hear the nightly has fixed your issues. Ill be closing this issue for now but feel free to open new issues if you run into something else!


241 hardhat deploy

The Problem

closes #241
closes #203
The Solution

A few remaining TODOs:

Critical: make sure that deploying contracts to an arbitrary network is easy (eg via ops/deploy-contracts.sh). There are no tests for this & it's probably broken..
Performance improvement: Can (should?) we package hardhat.config.ts into a collection of js files? I wasn't able to get that working so I putt all of the contract dev deps into the ethprovider image & use the hardhat.config.ts file directly. This drastically increases the build time, size, and startup time of the ethprovider image. This image is only used for testing so poor performance wouldn't affect anything in prod at least. Hardhat seems to have poor support for ts->js so this might be something to do later..
Luxury: Should we move the hardhat deploy scripts folder back into src.ts? Feels like it belongs there but it wasn't able to find contracts until I moved it out.. this is a nice-to-have that doesn't actually affect anything.

final TODOs before this is ready to merge:

we need to migrate the deployment data from address-book.json to hardhat's file structure in modules/contracts/deployments
run a test migration to rinkeby to make sure deployment data gets updated properly


[DO NOT MERGE] KAFKA-6145: Ensure each client has at least one task when previous assignment is used

This PR verifies that each client in the previous assignment has at
least one task before re-using the previous assignment. Otherwise
a new client that joins the group might never get a task assigned.
For example, if the topology only consists of stateless tasks,
the group consists of only one client, and a new client joins the
group, the previous assignment would be considered valid because
the state constraint and the balance factor are satisfied, all
tasks are assigned and no warmup tasks exist. The new client would
not get any tasks assigned.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

The balanced assignment is deterministic, so if the previous assignment was valid we should end up with the same thing.

Exactly this happened here https://github.com/vvcephei/kafka/pull/3/files#r416758157

But the prevStandbyTasks are actually just every non-active task found on disk, so if we do decide that the assignment is valid, we may end up assigning more than num.standby.replica tasks to any client with extra state left on disk.

We could also verify num.standby.replica, but then I am not sure how useful it is to check for the previous assignment anymore.

My vote would be to just remove the usePreviousAssignment check, and always go through the assignment. Now that we start with the balanced assignment and only move things if the state constraint is violated, we should be guaranteed to get the same assignment back if the previous assignment actually was valid. And we won't have to worry about standby accounting or lurking bugs in previousAssignmentIsValid

I'm +1 to just remove the usePreviousAssignment check. Standing back and considering the larger context in which we have these probing rebalances with a deterministic target assignment, this check starts to look like a "micro" optimization. The fact that Sophie pointed out about standby tasks means that it's not "just" re-constructing the prior assignment, it's actually a separate assignment algorithm of its own (if we fix it). Which makes it that much more of a liability.
This system will be easier to reason about if we know that we'll just execute the same HATA logic on every rebalance.

I agree with both of you and opened the following PR https://github.com/apache/kafka/pull/8590.


fix Compression to_string and into string impls

I proposed this change so that the to_string function for the Compression enum formats it correctly according to the protocol spec. It should be either all caps or lowercase. The default impl will format it as the enum name e.g. "Snappy", when it should be "snappy" or "SNAPPY".

In Rust typically string representations of enums reflect the names itself. I think it would be better to explicitly add to_protocol_string()/from_protocol_string() or similar.


Add PyTorch embedded example.

My plan after this is merged is to 1) link to it from the iree-torch repo, 2) get the binary size as small as possible, 3) embed the vmfb directly, and 4) get it automatically tested via CI in this repo.

Friendly ping.


Error when using ping to send a message

I'm trying this:
irb(main):013:0> notifier = Slack::Notifier.new "https://hooks.slack.com/services/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2K", channel: "#qe", username: "notifier"
Then:
irb(main):014:0> notifier.ping "Hi", channel: "#qe"
I get this error message:
URI::InvalidURIError: bad URI(is not URI?): https://https://hooks.slack.com/services/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.slack.com/services/hooks/incoming-webhook?token={:channel=>"#qe", :username=>"notifier"}

Nevermind, looks like the version I was using of slack-notifier was very old 0.5 .... I forgot to run bundle update and for some reason that is the version that got installed


Clings/skids

AFAIK, the friction for these balls are responsible for throws and clings/skids are caused when a high-friction spot (where it is a chalk mark) is happened to be at contact point.
However, a paper about Bounce Maps makes me curious because the idea of spatially-varying physical properties are nothing new, can something like this be applied for the friction instead of elasticity and these maps are dynamically changing (every time a cue strikes the ball, it imparts high-friction spot where there is a chalk mark)?

This is cool, thanks for sharing.
I think it's definitely possible, and I'll definitely keep it in mind for the future. Although at the current moment, not even uniform ball friction is implemented. You wouldn't be interested in becoming a contributor, would you?


Has any plan to support react components library?

Sorry no

@antfu
Sorry...I misunderstood the usage scene of this plugin.
I only want to find a vite plugin to autoload antd style by component just now.
Now i find it. https://github.com/anncwb/vite-plugin-style-import

@vitejs/plugin-react use babel.config.js


Hysterese writable

Would be very good if the values luxtronik2.0.Einstellungen.Temperaturen.Hysterese-WW / luxtronik2.0.Einstellungen.Temperaturen.Hysterese-HR  were also editable.
Both are created as write. However, the changes are not transferred.

Basically this value should only be modified by your 'Heizungstechniker' (based on Luxtronic manual - you need an additional password). Anyhow I am still on 0.2.0 and there it was editable, it was modified but now my adapter is not working anymore..

Thanks for your appraisal.
But in my opinion, many things that the adapter does actually require the installer.
To use the adapter, the user should of course know what he is doing.
To use the adapter, the user should of course know what he is doing.

just did some checks - in 0.42 it is no longer writable, but if you using the right password (for Installateur) you can write this value.


Add option to turn off purgePeriodically

Is your feature request related to a problem? Please describe.
In some scenarios, I need to bind thread in the coroutine, so if the coroutine is destroyed by the timeout mechanism, the benefits of bindthread are lost.
Describe the solution you'd like
Add an option to turn off purgePeriodically.
Describe alternatives you've considered
Consider setting the timeout very large, but that's a bit tricky.
Additional context
The os.LockOSThread() mechanism is mostly useful when Go has to interface with some foreign library (a C library for instance). It guarantees that several successive calls to this library will be done in the same thread.
https://stackoverflow.com/questions/25361831/benefits-of-runtime-lockosthread-in-golang

You surely can call runtime.LockOSThread() in your task function which is submitted to ants.Pool, but after that task is done, how do you manage to ensure that your new task can be processed by that exact previous goroutine in pool?

You surely can call runtime.LockOSThread() in your task function which is submitted to ants.Pool, but after that task is done, how do you manage to ensure that your new task can be processed by that exact previous goroutine in pool?

Actually, all the os threads would be bound in ants.Pool, we don't care if the new task is processed by the specified goroutine, as long as the task is processed by one of the goroutines in the pool, and these goroutines should never be unbound.

You surely can call runtime.LockOSThread() in your task function which is submitted to ants.Pool, but after that task is done, how do you manage to ensure that your new task can be processed by that exact previous goroutine in pool?

@panjf2000
In particular, every call to cgo, even within a single goroutine, might happen on a different OS thread.
In our usage scenario, cgo will call openmp, thus creating an openmp thread pool attached to this thread, and the openmp thread pool will not disappear with the destruction of the coroutine. If these coroutines are not bound, it will cause a lot of system threads at the end.


Feature/csi 5609 basic flow call home

this is phase 1 of call-home without the option for the user to disable call-home

Apparently, the grpc module is built with concurrent.futures, so the preferred async execution mode should be by using the concurrent.futures.Executor.
controller_server = grpc.server(futures.ThreadPoolExecutor(max_workers=max_workers))

It's possible that you will need to pass the executor separately to the controller servicers as you need an executor instance to submit a callable


scripts/*syscalls.py: sort os.walk() for a more deterministic build

Found by "disordered --shuffle-dirents=yes".
Sorting os.walk() in scripts/subfolder_list.py removes the randomness in
the following files:
build/zephyr/misc/generated/syscalls_subdirs.txt
build/zephyr/CMakeFiles/syscall_list_h_target.dir/ or build.ninja
Sorting os.walk() in scripts/parse_syscalls.py removes the randomness
in:
build/zephyr/misc/generated/syscalls.json
build/zephyr/include/generated/syscall_dispatch.c
build/zephyr/include/generated/syscall_list.h
Note my (limited so far) testing did not observe any randomness in any
object file that this would address; the main purpose here is to remove
a very large amount of noise in diffoscope.
Signed-off-by: Marc Herbert<EMAIL_ADDRESS>

Codecov Report

Merging #13446 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13446   +/-   ##
=======================================
  Coverage    52.5%    52.5%
=======================================
  Files         318      318
  Lines       46526    46526
  Branches    10754    10754
=======================================
  Hits        24429    24429
  Misses      17198    17198
  Partials     4899     4899

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f0a20c6...68623c2. Read the comment docs.

Seems like a good change.

Very nice.

BTW it's possible right now to entirely nullify the output of diffoscope --exclude-directory-metadata hello_world/build.1/ hello_world/build.2/ where build.1 and build.2 are two consecutive hello_world/build/ with just this hack:
--- a/cmake/app/boilerplate.cmake
+++ b/cmake/app/boilerplate.cmake
@@ -28,6 +28,9 @@ cmake_minimum_required(VERSION 3.13.1)
 # CMP0002: "Logical target names must be globally unique"
 cmake_policy(SET CMP0002 NEW)

+SET(CMAKE_C_ARCHIVE_CREATE "<CMAKE_AR> Dqc <TARGET> <LINK_FLAGS> <OBJECTS>")
+SET(CMAKE_C_ARCHIVE_FINISH "<CMAKE_RANLIB> -D <TARGET>")
+
 if(NOT (${CMAKE_VERSION} VERSION_LESS "3.13.0"))
   # Use the old CMake behaviour until 3.13.x is required and the build
   # scripts have been ported to the new behaviour.

It's unrelated to disordered --shuffle-dirents=yes and needed either way.

Another determinism fix if you liked this one: PR #13608 git describe --abbrev=12


Appstudio update test-component-pac-sykr

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-sykr-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
12 seconds
clone-repository

✅ Succeeded
30 seconds
build-container

✅ Succeeded
19 seconds
deprecated-base-image-check

✅ Succeeded
17 seconds
inspect-image

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
32 seconds
clamav-scan

✅ Succeeded
15 seconds
sbom-json-check

✅ Succeeded
13 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary


Revert "Remove hex from spending details in the multi sig wallet"

We may need to rethink this, the CCTS looks for withdrawal transactions often, and this includes unconfirmed transactions within the wallet. I overlooked that in my review, so this causes exceptions stating that the withdrawal transactions can't be found. Unless unconfirmed wallet transactions can be skipped in the ValidateCrossChainTransfers check, which I don't believe is advisable, we will have to revert this for now. @quantumagi do you have any thoughts on this?
Also, note that there are two places in the wallet manager that save the hex into the wallet, of which only the latter one was being suppressed:
AddTransactionToWallet
BuildSpendingDetails

hey @zeptin @fassadlr @quantumagi
Some thoughts:

We shouldn't call into the blockstore from the FWM. The FWM is always locked when used, but the blockstore could have reorged in a different thread. That error is going to be hit commonly when these components are out of sync.
The underlying problem is "the federation wallets get too big", right? Removing the hex from SpendingDetails may not be the right answer, only delaying the issue. Instead, how about removing spent transactions from the wallet more than MaxReorg old? This could fix the problem long-term and will have performance benefits too.

(Note for a more user-friendly experience for viewing the wallet we may want to make the rule more like once there are more than 100 transactions in the wallet remove any past the maxreorg)
I support this PR and keeping the SpendingDetails in the wallet

Happy with this PR. It's probably more important to add indexing than to reduce the size of the wallet file, although some reductions should be possible as @codingupastorm is pointing out.

Also if we can still bring in the changes around RecordLatestMatureDepositResult and other helpful things I think that would be good.

The underlying problem is "the federation wallets get too big", right? Removing the hex from SpendingDetails may not be the right answer, only delaying the issue. Instead, how about removing spent transactions from the wallet more than MaxReorg old? This could fix the problem long-term and will have performance benefits too.

I'm in favor of this @codingupastorm!
Also, yeah let's keep the result class for recording the mature deposits.
My thoughts are lets merge this, reverting the change and reintroduce the result class?

I see now that we merge conflicts. I would actually suggest that we then perhaps "revert" the changes in a PR and not a commit revert.


fix(notification): remove default notification sound on Windows

reverts https://github.com/tauri-apps/plugins-workspace/commit/7d71ad4e587bcf47ea34645f5b226945e487b765

No need for a change file since we didn't release yet @amrbashir and actually need to delete .changes/notification-sound.md.

We did release it https://github.com/tauri-apps/plugins-workspace/releases/tag/notification-v2.0.0-alpha.1


argocd support

Hi
This plugin can work with argocd ?
the krm function use docker for build manifests with embedded bin, but can't use docker in argocd
any suggestion ?
Thanks

Hi @chris93111 the plugin is also available as an Exec KRM function and can be downloaded from the release page https://github.com/DevOpsHiveHQ/kustomize-plugin-merger/releases
You will find the Exec KRM function section in all examples, but it's commented. E.g.
https://github.com/DevOpsHiveHQ/kustomize-plugin-merger/tree/62e552e/examples/manifest-lists-without-schema#manifest
All that you need to do is download the binary to the ArgoCD system and it will work:
apiVersion: generators.kustomize.aabouzaid.com/v1alpha1
kind: Merger
metadata:
  name: merge
  annotations:
    # Exec KRM functions.
    config.kubernetes.io/function: |
      exec:
        path: kustomize-plugin-merger
spec:
[...]

And the rest under spec is the same.

Hi @chris93111 the plugin is also available as an Exec KRM function and can be downloaded from the release page https://github.com/DevOpsHiveHQ/kustomize-plugin-merger/releases
You will find the Exec KRM function section in all examples, but it's commented. E.g.
https://github.com/DevOpsHiveHQ/kustomize-plugin-merger/tree/d61661b/examples/manifest-lists-without-schema#manifest
All that you need to do is download the binary to the ArgoCD system and it will work:
apiVersion: generators.kustomize.devopshive.net/v1alpha1
kind: Merger
metadata:
  name: merge
  annotations:
    # Exec KRM functions.
    config.kubernetes.io/function: |
      exec:
        path: kustomize-plugin-merger
spec:
[...]

And the rest under spec is the same.

Given the thumb-up, I'm closing this issue because of the solution provided.


EnableReferences might be causing incorrect deserialization

I have created a ConfigurationContainer configured like this:
serializer = new ConfigurationContainer()
    .UseAutoFormatting()
    .UseOptimizedNamespaces()
    .EnableParameterizedContent()
    .Type<Color>().Register().Converter().Using(ColorConverter.Default)
    .EnableReferences()
    .Create();

I have decided to "enable references" because my model potentially has circular references, but doing so makes deserialization act weird (results in empty object)
To see the problem, please, reproduce the issue with the step below:

Clone this repo: https://github.com/SuperJMN/Velcro-Designer.git
Run the application name Designer. It's a Universal Windows Application
Create an Ellipse using the toolbar like in the animation:

You will see that the load operation doesn't load anything but a blank document (no Items).

However, if you comment out the .EnableReferences() line:
ProjectStore.cs

...and repeat the previous steps, you will notice the that document with the ellipse load perfectly.
Tips

ProjectStore.cs is exactly where the serialization/deserialization takes place. This is the class that will be called whenever you load/save a document.
I've created a property Id for types inherited from the Body class. It may interfere with references 🤔

Cool!  Thank you for the information and for providing the code, @SuperJMN.  I am looking into this now. 👍

Alright @SuperJMN check it out:
https://github.com/ExtendedXmlSerializer/home/pull/342#issuecomment-564454665
Try that out to see if that works better for you.  The issue we ran into here was that the references extension was attempting to apply references to attribute values, which is not supposed to happen.  Shocking that we haven't seen that until now. 😁
Anyways, that should be fixed... let me know if you run into any further issues.

It's working now. Big thanks! I'll test extensively the Circular References feature these days. I'll provide feedback in case it's not working as expected :)


IVT RC300/310 Bosch/Buderus

Hi,
with Home Assistant 2023.4.6
integration over HACS:
module:
IVT
od RC300
Firmware: 04.08.02
Missing pretty much all of the sensors. Only working thing is thermostat and hot water setup. All internal sensors report as missing.
Is there something, I can do to pinpoint the issue?

enable those you need, sensors are disabled by default


[BugFix][TOPI] Fix the integer overflow problem of the scatter_nd op.

Problem Statement
scatter_nd crashes on cuda backend, when input data shape is slightly larger than usual.
Code to reproduce

import tvm
import numpy as np
import tvm.relay as relay

dev = tvm.cuda()
target = tvm.target.Target("cuda")

# input data:
data_np = np.zeros((32, 128, 128, 256)).astype(np.float32)
indices_np = np.random.uniform(1,5,(32, 600, 3)).astype(np.int64)
updates_np = np.random.rand(32, 600, 256).astype(np.float32)

# Construct relay input nodes:
data = relay.var("data", shape=data_np.shape, dtype=str(data_np.dtype))
indices = relay.var("indices", shape=indices_np.shape, dtype=str(indices_np.dtype))
updates = relay.var("updates", shape=updates_np.shape, dtype=str(updates_np.dtype))

# Compute indices:
indices_dim = len(indices_np.shape)
axes = list(range(indices_dim))
indices_t = relay.transpose(indices, axes[-1:] + axes[:-1])

# Construct relay scatter_nd op:
out = relay.op.scatter_nd(data, indices_t, updates, "update")
func = relay.Function([data, indices, updates], out)

# Execute scatter_nd:
intrp = relay.create_executor("debug", device=dev, target=target)
op_res = intrp.evaluate(func)(data_np, indices_np, updates_np)

Error Message

Root Cause

We can see the problem more clearly from the cuda code generated. The TIR implementation of scatter_nd would cause a int32 overflow when "i" is large, thus the if statement is always evaluate to true, and conducts a invalid memory access.

@tqchen @masahi @icemelon9 Could you help review this fix, or bridge someone who is willing to?

I've implemented an alternative fix in #8419

I've implemented an alternative fix in #8419

@tkonolige Thank you for review this PR.
Just curious, is there any specific reason why you created another PR? I understand the alternative fix you proposed maybe better than the existing one, in someway probably. But why bother create a new separate PR? We can discuss and improve the code here, I think that's exactly what code review is about, right?
Anyway, please let me know if there is anything I can help.

@zhuwenxi I definitely shouldn't have opened a new PR. I just got a little hasty and did the fix myself. Feel free to copy the code from that PR into this one. I'll end up closing the other one.

@tkonolige That's OK, it happens.

You hit a flaky test, I found a fix here: #8431

@mbrookhart I've fixed the UT failure.

Thanks @zhuwenxi @tkonolige


Request for the sample policy used

I tried this but I am getting 1101 error on request. I suspect the problem is because I use improper policy.
Please provide the dynamoBD policy used.
Thank you.

I suspect the error was that the worker threw an exception. Did you try to inspect the worker using wrangler tail?

+1


feat: add support for chunked uploading

tested manually with GIF images, but no automated tests in this
I hereby declare that this contribution is licensed under Apache License Version 2
@redouane59 feel free to rework however you need. Should fix #183 and #281 but is hacky and not my best code

Hello,
Thanks ! Can you just correct the bug that sonar shows ?

@redouane59 feel free to rework however you need

Just driving by my friend. But getting a release that can let me tweet gifs would be much appreciated, do whatever you want with the PR

To clarify, I don’t have the headspace to determine what the idiomatic way of handling the interrupted exception is in your library. Probably quicker if you just push the way you want it on top. This PR should allow edits from maintainers, and I am happy for you to align the code with your style


Adjust node assignment logic for default operations

a) always create a copy of a default node
b) adjust the copy logic of node.py to have a full set of attributes

Still has some issues.


Document PersistentSession

The documentation only shows saving the Session variable but the code exposes a PersistentSession which seems a lot nicer to use than throwing everything I want to persist into Session.
Could the readme be updated to reflect this? Right now it's seriously under"selling" the usefulness of this package.
Renaming PersistentSession to PersistentReactiveDict might go a bit far, but would make it clearer what this package does.

Actually I do think the package should be PersistentReactiveDict. :smile:


Also check USELESS_ELVIS in UnreachableCode

Fixes https://github.com/detekt/detekt/issues/6623

I understand why this is added to the existing unreachable code rule but I believe this should be implemented as a separate rule since it's a wrapper of an existing compiler warning. I don't think wrapped compiler warnings should be consolidated in the same rule.
And very technically speaking the Elvis operator itself is not unreachable - it will always be hit.

I understand why this is added to the existing unreachable code rule but I believe this should be implemented as a separate rule since it's a wrapper of an existing compiler warning. I don't think wrapped compiler warnings should be consolidated in the same rule.

I'm not sure about this. It's true, it's easy to think "two different rules" looking at the implementation. But, as a user, both are unreachable code so I think that it is ok to merge them. A new rule will help to make this more configurable but I think that we don't need such configuration.


RuntimeError: CUDA out of memory. Tried to allocate 768.00 MiB (GPU 2; 47.46 GiB total capacity; 45.22 GiB already allocated; 605.25 MiB free; 45.68 GiB reserved in total by PyTorch)

Hi,
I got the CUDA out of memory issue. I am running run_sup_example.sh on 4 GPUs (RTX 8000, each GPU has 48601MiB (48GB) memory) and I am using the RoBERTa-large and the hyperparameter I am using batch size = 512, learning rate = 1e-5. If 4 Nvidia 3090 GPUs can run the supervised SimCSE (large) why it cannot be running in RTX 8000 and each GPU has 48GB memory?

Hi,
I see that you have more than 4 GPUs available. Please make sure that when you run the script, you properly set up the GPUs by using CUDA_VISIBLE_DEVICES. Also, make sure that the selected GPUs are not occupied by other programs.

Thanks. One more question when I try to replicate the result from Sup. RoBERTa. I met the CUDA out of memory issue when I use batch size = 512. But it works when the batch size = 128. Does different batch size will produce much different results?

Different batch sizes might make a significant difference if using the same learning rate and other hyperparameters.