About office on woa

Hii! This its not a report of a bug but still I need some info or help about this topic. I have some doubts about how its the actual state of woa. The msoffice implementation of office its still on emulation?If the answer is yes, it use a 32 bit arm msoffice or 64bit arm build instead? I ask these thing because i want to use microsoft office app under wine natively. I need, if it possible, a few advices of how to extract the binary to run it on linux, if its compiled to arm 32 bits... i search a lot time ago inside a windows rt image and i could find microsoft offfice rt version... and if there its a 32 bit arm office it would be great than we could launch it natively out of the box on linux distro. Iva compiled wine several times on my pi 3, just for test the notaz recompiled binaries of diablo II, starcraft, etc. But the only program i could execute from other source its rufus... and it didnt work properly because its really windows api demanding. The same happend on x86 system, so for me was a succes. If you wanna help i would be extremly greatful with you. Thanks anyway.

For questions, please ask them at https://t.me/raspberrypiwoa


Reload app by changing gps permissions

Plugin version: 0.5.3
Platform: Android
OS version: 7.0 and 9.0.2
Device manufacturer and model:
P8 lite and Oneplus 6
React Native version: 0.53.0
Plugin configuration options:

BackgroundGeolocation.configure({       desiredAccuracy: 10,       stationaryRadius: 50,       distanceFilter: 50,       debug: false,       startOnBoot: false,       stopOnTerminate: false,       locationProvider: BackgroundGeolocation.ACTIVITY_PROVIDER,       interval: 10000,       fastestInterval: 5000,       activitiesInterval: 10000,       stopOnStillActivity: true,       startForeground: true,       notificationIconColor: "#e33",       notificationText: "Background tracking",       saveBatteryOnBackground: false,       activityType: "Fitness",       syncThreshold: 1     });
Whether I have the app open with the geolocation process active or not, if I go into the settings of the app and remove the permission to use the gps, returning to the app, it is reloaded as if it closed because of the change of permission.

I have this problem, when user give permission


Integration tests are slightly unstable

Seem to hit more problems on Drone when running on the fommil.com machine versus my machine. Appveyor has no issues, but I'm paying for more memory and cores, I believe.
Not sure how to fix this one, but want to come to some conclusion before 1.1.0 is finished.

Fixed by #302.


Spelling

I've tried to exclude third party code/modules. If I missed a module, please let me know or feel free to exclude it.

The API change is now its own PR.


Repeated audio route change causes left and right headphones to get out of sync

If you repeatedly take your headphones in and out really fast, the sound that is playing either becomes out of sync in the left and right headphones (usually), or the sound becomes extremely choppy (sometimes).
I noticed that you do a lot of stuff when the audio route changes so I commented that part out and it ended up fixing both symptoms of the issue for me. I'm going to investigate further.
What fixes it:

Commenting out [sm checkSessionProperties]

What doesn't fix it:

Dispatching [sm checkSessionProperties] to another queue (WEIRD!)
Commenting out all of the NSLogs
Commenting out the CheckErrors
Commenting out [self checkAudioSource] in checkSessionProperties

SO I think the problem is all of the calls to AudioSessionGetProperty when the audioRoute changes. What I think you should ACTUALLY do is have custom getters for numInputChannels, numOutputChannels, etc. And when the audio route changes, set all of them to -1. When the getter is called, and if they are set to -1, THEN it calls AudioSessionGetProperty.
edit: Nevermind, I tried implementing the above and it didn't fix the problem. I'm stumped.

Has anyone solved the issue??

nope.


feat: remote_write_receiver option

Issue
the juju cos setup cannot receive data from the grafana-agent if the grafana-agent is not running inside juju.
Solution
Add a charm option to enable the remote remote_write_receiver feature even when no relation is established.
Context
IoT devices cannot run juju due to resources constraint, so they must run grafana-agent snap standalone.
This way the COS stack can be used on servers and snaps can be used on devices to export data.
Notes
This is a draft PR as a suggestion as I am exploring the usage of COS for robots.
The PR is based on my recent learning of Juju/Charm and COS.

This seems like a good idea. What do you think @simskij?

@Guillaumebeuzeboc would you mind squashing your commits into a signed commit to allow for merging? Thanks.

@Guillaumebeuzeboc would you mind squashing your commits into a signed commit to allow for merging? Thanks.

Done, let me know if it's all good.
Thanks!


Rebuild for pytorch113

Migrator is stuck because pytorch 1.13 is only built for CUDA 11.2

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/openmmtorchplugin, this is green, PTAL :)


License requirements for conditional access

[Enter feedback here]
I heard that Azure AD P1 is also required for the users specified in "Exclude" of "Users and groups".
Please consider describing this.

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

ID: 3d525ecd-381b-162f-84b7-2912b83462f6
Version Independent ID: db11cbb8-d83a-2a03-0160-beed5afb42c9
Content: What is Conditional Access in Azure Active Directory?
Content Source: articles/active-directory/conditional-access/overview.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@KJ2256 Thanks for reaching out. We will investigate and update the thread accordingly.

Covered in the doc under License requirements. Azure AD is licensed per-user. #please-close


Update README

Close https://github.com/winebarrel/faraday_middleware-aws-sigv4/issues/14

Coverage remained the same at 100.0% when pulling 8aa7336599ca1ae0ae344728915923552b0b7079 on update_readme into 7b8750fa3f420ccc68b5e1b0b82fa2f273fa252c on master.


ui: allow filtering account by state

This allows users and admin to filter account by state
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

cc @kishankavala @vishesh92

@blueorangutan ui

@rohityadavcloud a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/7365 (QA-JID-64)

@vishesh92 since you're on this in another PR, could you merge this PR in yours. Thanks.


Fix index handling in ecma_op_advance_string_index

Fixes #3389
JerryScript-DCO-1.0-Signed-off-by: Adam Szilagyi<EMAIL_ADDRESS>

With this fix, the test case in #3389 returns with ref count limit error, which is the proper behaviour, but i dont't know how to write a valid test for this, because this error thrown internally.


Make Tuple class and methods public to enable extending Masker

To allow others to overwrite the main, doWork, and add alternatives to maskDialogContent, make Tuple a public class with public methods. This enabled creating of a JSONL parsing facility.

Also changed maskedNam to maskeName


[ASCII-1186] Cleanup IPC code in the subcommands, less usage of pkgconfig.Datadog

What does this PR do?
Adds a struct IPCEndpoint that simplifies internal api calls in the subcommands, and uses it for two commands: agent status and agent secrets.

Motivation
Removes code duplication across the subcommands. Also lets us remove uses of the global pkgconfig.Datadog config object.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
Build an agent and run it. Then run the agent status command, which would continue to work correctly. Also run the agent secrets command and make sure it doesn't produce an error.

/merge


KAFKA-13891: reset generation when syncgroup failed with REBALANCE_IN_PROGRESS

This PR is a missing part of https://github.com/apache/kafka/pull/11451
Previous change want to solve https://issues.apache.org/jira/browse/KAFKA-13419, but in the final code didn't add code to reset generation id when SyncGroup received REBALANCE_IN_PROGRESS error.
Committer Checklist (excluded from commit message)

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

Thanks for the patch. Could we file a Jira for it please?

created a jira for it: https://issues.apache.org/jira/browse/KAFKA-13891

@showuon can you please help to review this?

@aiquestion , thanks for the PR. Could we add a test for it?

@showuon sorry for the delay. What should i do to get this PR merged? ( it's my first time submit a PR )

Failed tests are unrelated
    Build / JDK 11 and Scala 2.13 / kafka.server.MultipleListenersWithDefaultJaasContextTest.testProduceConsume()
    Build / JDK 11 and Scala 2.13 / kafka.server.UpdateFeaturesTest.testShouldFailRequestDuringDeletionOfNonExistingFeature()

Hey @dajac @showuon just came across this from a user who's running into this on 3.0, given it was part of a series of fixes leading up to/included in 3.0, I think it can/should be backported to 3.1 & 3.0 -- any concerns there?
Just lmk if there's any reason to be careful, or changes needed to backport the fix faithfully

Agree to backported to 3.2 - 3.0. Thanks.

Thanks @showuon ! Unfortunately I'm now seeing that the situation may be more complicated than I'd initially thought :/ Just came across this followup to the patch here: https://issues.apache.org/jira/browse/KAFKA-14016
Original reporter/PR author actually suggests reverting the changes here, and offers an alternative fix. I feel like I'm still catching up on the whole history here but while I wrap my head around could you give this new ticket a look? Wondering what your take on this is
Don't want to bias you with this but FWIW, when I was first pointed to this PR I was definitely skeptical of the changes, though I did ultimately convince myself it made sense. Now I'm letting my doubts creep back in lol


Premature upshift during airtime

Describe the bug
Catching any sort of airtime, even a tiny bump, will redline the speedometer and upshift the car. This is problematic when a premature upshift to fifth happens as it won't downshift again until ~160 km/h, this leaves the car almost unable to accelerate beyond whatever speed it prematurely upshifted at.
(almost, accelerates by ~2km/s).
Example / Reproduction

Drive in fourth gear at 170 km/h.
Encounter a small bump or catch some airtime.
The car prematurely upshifts to fifth gear at 170 km/h instead of ~225 km/h
The car struggles to accelerate significantly after the premature upshift.
The car finally downshifts back to fourth gear at approximately 160 km/h.

Expected behavior
When catching airtime, the gears should remain locked and the speedometer should still redline. The car should not gain any speed when it touches the ground after catching airtime, as this would resemble curb boosting in GTA 5, where driving on and off curbs allow for speed gains due to increased RPM.
Version

Demo 1.5.3

It's possible to fix this, but will require a custom implementation to check when the car is off the ground or not, and will take some time to thoroughly test


Fixed github #95: Allow using Pygments styles directly in .pdbrc.py

Great feature - works fine for me.
Please merge the PR.

I did some testing with the available styles. The results are a bit mixed: All themes with dark background work fine (native, friendly, monokai). Some styles have wrong colors (vim, bw) or show strange artifacts (tango).
It's a bit tedious to nail down the cause of this problem - in Kubuntu 16.04 it could be Linux, the terminal konsole or the pygments library.
@vaughnkoch: It would be nice if you could check styles other than monokai and see if the lighter themes work on your machine.

@vaughnkoch
Please address the comments above, and then rebase this on master, please.
I have not tested this myself yet, but thanks for the investigation/testing already, @GHPS !

Ping?

@blueyed - thanks for the time you spend on implementing this PR.
Styling is really a great idea - people loved it when this feature was
implemented in iPython [1].
But I am not sure what the current status of this PR is. Is the
feature ready to use?
1: https://github.com/ipython/ipython/issues/9541

@GHPS
I think you can achieve everything already via the dynamic config..  I've just pinged to see what the state / opinion(s) on this are.

See https://github.com/antocuni/pdb/pull/222.

@blueyed Thanks for implementing this great feature!


Ionic Deploy fails to extract snapshot on Android

When running my app on Android, I'm getting an error when trying to load in a new snapshot from Ionic Deploy.
As shown by logcat in Android Studio:
...
12-01 17:08:26.240 510-547/APP_ID I/IONIC.DEPLOY.DOWNLOAD: Progress: 99%
12-01 17:08:26.243 510-547/APP_ID I/IONIC.DEPLOY.DOWNLOAD: Progress: 100%
12-01 17:08:26.250 510-510/APP_ID I/chromium: [INFO:CONSOLE(6)] "Ionic Deploy: download complete", source: file:///android_asset/www/lib/ionic.cloud.min.js (6)
12-01 17:08:26.272 510-510/APP_ID I/chromium: [INFO:CONSOLE(26794)] "TypeError: Cannot read property 'emitter' of undefined
                                                                                at e.extract (file:///android_asset/www/lib/ionic.cloud.min.js:6:24131)
                                                                                at processQueue (file:///android_asset/www/lib/ionic/js/ionic.bundle.js:29127:28)
                                                                                at file:///android_asset/www/lib/ionic/js/ionic.bundle.js:29143:27
                                                                                at Scope.$eval (file:///android_asset/www/lib/ionic/js/ionic.bundle.js:30395:28)
                                                                                at Scope.$digest (file:///android_asset/www/lib/ionic/js/ionic.bundle.js:30211:31)
                                                                                at file:///android_asset/www/lib/ionic/js/ionic.bundle.js:30434:26
                                                                                at completeOutstandingRequest (file:///android_asset/www/lib/ionic/js/ionic.bundle.js:19194:10)
                                                                                at file:///android_asset/www/lib/ionic/js/ionic.bundle.js:19470:7", source: file:///android_asset/www/lib/ionic/js/ionic.bundle.js (26794)

This error seems to be originating from this line in the Ionic Cloud client:
https://github.com/driftyco/ionic-cloud/blob/master/src/deploy/deploy.ts#L155
Here's how I'm invoking the deploy process:
angular.module('app.controllers', ['ionic.cloud'])
.controller('AppCtrl', function( ... $rootScope, ... $ionicDeploy) {

    $rootScope.$on('appAuthenticated', function (event, settingsData) {

        // check for new deploy snapshots
        $ionicDeploy.check().then(function(snapshotAvailable) {
            if (snapshotAvailable) {
                return $ionicDeploy.download()
                    .then($ionicDeploy.extract);
            }
        });

    });

})

On iOS, the Ionic Deploy works flawlessly. This issue occurs in my testing on Android 4.4, 5.0, and 6.0.
I'm using:

Ionic v1.3.1 (and thus Angular 1.5.3)
Ionic Cloud client v0.14.0
ionic-plugin-deploy v0.6.5 (Cordova plugin)

Any help will be greatly appreciated!

@johnellmore The fact that it's working on iOS but not Android makes me think that this is actually an outdated dependency being used when you run the build for Android. Are you able to provide a test project we can build and run?

Unfortunately, I can't provide the project, as it's a private project for a client. I can possibly provide certain files, though; are there specific files that you'd like to see? My employer is okay granting outside access to the codebase, but would require some legal paperwork first. So I'd love to avoid that complexity if possible :)
Or if that's too tedious, do you have any suggestions for where I can start troubleshooting?
I appreciate your help!

@johnellmore One thing you could do is to print out the version of the cloud client from within your app code. If it's running an out of date version that would show an older version instead of your latest version you may or may not have installed. Here is a reference to the code but I'm blanking on the usage off the top of my head. @dwieeb can you provide a usage example?

.controller('AppCtrl', function( ... $rootScope, ... $ionicCloud) {
    console.log($ionicCloud.version);
})


Errors in log using vxlan backend under CPU load

I have the following messages in the journal if cpu usage is > 60%
Mar 02 21:36:58 ip-10-0-2-240.eu-central-1.compute.internal sdnotify-proxy[2093]: E0302  21:36:58.118918 00001 device.go:218] Failed to receive from netlink: no buffer space available
Mar 02 21:36:59 ip-10-0-2-240.eu-central-1.compute.internal sdnotify-proxy[2093]: E0302  21:36:59.215630 00001 device.go:218] Failed to receive from netlink: no buffer space available
Mar 02 21:37:00 ip-10-0-2-240.eu-central-1.compute.internal sdnotify-proxy[2093]: E0302 21:37:00.316524 00001 device.go:218] Failed to receive from netlink: no buffer space available
Mar 02 21:37:01 ip-10-0-2-240.eu-central-1.compute.internal sdnotify-proxy[2093]: E0302 21:37:01.465853 00001 device.go:218] Failed to receive from netlink: no buffer space available

It goes from here
https://github.com/coreos/flannel/blob/7cb8d6b9a80632828e9569033d411361afee1816/backend/vxlan/device.go#L218
Do I need to tweak some parameters?
I have already played with
sudo sysctl -w net.ipv4.tcp_rmem="10240 87380 12582912"
sudo sysctl -w net.ipv4.tcp_wmem="10240 87380 12582912"

sudo sysctl -w net.ipv4.tcp_rmem="102400<PHONE_NUMBER>29120"
sudo sysctl -w net.ipv4.tcp_wmem="102400<PHONE_NUMBER>29120"

sudo sysctl -w net.core.wmem_max="125829120"
sudo sysctl -w net.core.rmem_max="125829120"

sudo sysctl -w net.ipv4.tcp_window_scaling="1"
sudo sysctl -w net.ipv4.tcp_timestamps="1"

sudo sysctl -w net.ipv4.tcp_sack="1"
sudo sysctl -w net.core.netdev_max_backlog="5000"

sudo sysctl -w net.ipv4.udp_mem="102400<PHONE_NUMBER>29120"
sudo sysctl -w net.ipv4.udp_mem="102400<PHONE_NUMBER>29120"

sudo sysctl -w net.ipv4.udp_rmem_min="10240"
sudo sysctl -w net.ipv4.udp_wmem_min="10240"

sudo sysctl -w net.core.rmem_default=524280
sudo sysctl -w net.core.rmem_max=524280

I'm interested to hear if anyone else has hit this or if anyone has a repro for it.

We've also run into this, box is generally around <5% idle cpu, so could also be cpu related.

Hi, we are also encountering the same issue.
Since we don't have the problem on all the boxes, we are analysing  the issue in order to understand if there is a match for specific pods hosted by specific boxes.
Flanneld v0.7.0
Etcd2 2.3.7
Kubernetes v1.5.2
Average cpu load of the nodes is 25%

Same problem.
Apr 06 06:47:10 node204 flanneld[2584]: E0406 06:47:10.852782    2584 device.go:222] Failed to receive from netlink: no buffer space available
Apr 06 06:51:44 node204 flanneld[2584]: E0406 06:51:44.384812    2584 device.go:222] Failed to receive from netlink: no buffer space available
Apr 06 06:56:01 node204 flanneld[2584]: E0406 06:56:01.500101    2584 device.go:222] Failed to receive from netlink: no buffer space available
Apr 06 07:04:31 node204 flanneld[2584]: E0406 07:04:31.445611    2584 device.go:222] Failed to receive from netlink: no buffer space available

Ubuntu 16.04 on baremetal x86_64
Flanneld v0.6.2 and Flanneld v0.7.0
Is not related to the pods, nodes without pods produce errors as nodes with pods do not produce error.
Node without pod and with errors:
%Cpu(s):  0.3 us,  0.8 sy,  0.0 ni, 98.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
Node without pod and without errors:
%Cpu(s): 19.1 us,  2.0 sy,  0.0 ni, 77.2 id,  0.0 wa,  0.0 hi,  1.7 si,  0.0 st
It seems to be some (too small) default setup during the netlink call that permits the communication between the kernel and the userspace process

Seeing the same thing #779 . Our cluster is about 250 to 300 nodes.

core@ip-10-72-148-29 ~ $ ifconfig flannel.1
flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 8951
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::6c89:a7ff:febd:578f  prefixlen 64  scopeid 0x20<link>
        ether 6e:89:a7:bd:57:8f  txqueuelen 0  (Ethernet)
        RX packets 56700389  bytes<PHONE_NUMBER>0 (69.1 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 105960931  bytes<PHONE_NUMBER>4 (74.2 GiB)
        TX errors 0  dropped 22871 overruns 0  carrier 0  collisions 0

Dropping packets is seen on minions in a ~ 270-node cluster.

Only as info.
These parameters remove the log entry increasing the netlink buffer.
net.core.rmem_default = 524280
net.ipv4.udp_rmem_min = 10240


bug(ui): Create a group is rendered offscreen

Issue:
When you open create a group it is rended offscreen to the right
OS:
All
Screenshot:

cc @Flemmli97 @lgmarchi if you guys wanna take a look 😄

thanks! 🎉


Support built_collection 2.0.0

built_collection is at 2.0.0 and not compatible with built_redux which only supports ^1.0.0

thanks for the heads up, I'll open up that range tonight

https://github.com/davidmarne/built_redux/issues/43


BC compliance check fixed, tests fixed

what

BridgeCrew compliance checks fix
readme updated
code clean up
workflows updated

why

To be able to position our modules as standards compliant
Providing explicit note about policy attached directly to user
removed unnecessary providers dependencies
to stay in sync with all repos

references

https://docs.bridgecrew.io/docs/iam_16-iam-policy-privileges-1

/test all

/test all

/test all

/test all


team communication

hello  @gotk3/gotk3-core
we need a (simple, friendly, ..) communication channel.
have you a idea?

Github issues work for me.

the team has no other ideas. then we communicate over github issues :-)


Compatibility check to js-controller 4.0

Dear Adapter developer,
with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.
If something is not correct this is logged as 'warning' or 'info' log.
Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!
Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.
For questions please refer to ioBroker/ioBroker.js-controller#1749
Please close the issue after you checked it.
Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Wäre klasse wenn da ein fix kommen könnte.
`

govee.0
2023-07-05 13:52:13.200
error
Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at Govee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5388:49) at Govee.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5349:21) at /opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:2043:16 at new Promise () at Govee.setStateAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:2042:16) at /opt/iobroker/node_modules/iobroker.govee/main.js:834:16 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

govee.0
2023-07-05 13:52:13.200
error
unhandled promise rejection: undefined is not a valid state value

govee.0
2023-07-05 13:52:13.200
error
undefined is not a valid state value

govee.0
2023-07-05 13:52:13.199
error
Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

govee.0
2023-07-05 13:52:13.198
error
undefined is not a valid state value

`


flush out repo README

the main README.md needs to outline the project goals, status and build instructions for the firmware and documentation

I think this has been done, review if you would like


Prints report of longest running tests.

Changes proposed in this PR

Prints report of longest running tests.
See build output for the report.
Each individual test also includes duration on finish.

Why are we making these changes?

Helps us identify which tests are taking a long time.

Example output for future reference:
...
lein test waiter.zk-test
Longest running tests:
waiter.scheduler-test/test-retry-on-transient-server-exceptions 7591ms
waiter.utils-test/test-compression-decompression-clojure-data-maps 4846ms
waiter.kv-test/test-new-kv-store 3041ms
waiter.process-request-test/test-stream-http-response 3014ms
waiter.curator-test/test-read-write-path 1829ms
waiter.auth.authenticator-test/test-decode-auth-cookie 1700ms
waiter.kv-test/test-encrypted-kv-store 1578ms
waiter.curator-test/test-synchronize 1516ms
waiter.state-test/test-evenly-distribute-slots-using-consistent-hash-distribution 1421ms
waiter.curator-test/test-synchronize-fail-to-acquire 1147ms
Ran 440 tests containing 8478 assertions.
0 failures, 0 errors.

This would be helpful in Cook too.


Increment version for kubernetesconfiguration releases

Increment package version after release of com.azure.resourcemanager azure-resourcemanager-kubernetesconfiguration

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


Update Playlist methods types

The code in this changeset improves the typings for the Voice.Playlist methods to remove the option to pass volume as a param. This param was already ignored since it's not a supported feature.

/cc @danieleds if he needs to update the docs when we merge


UCP: Migrate scalar function Insert from TiDB

Description
Port the scalar function Insert from TiDB to coprocessor.
Score

50

Mentor(s)

@mapleFU

Recommended Skills

Rust programming

Learning Materials
Already implemented expressions ported from TiDB

https://github.com/tikv/tikv/tree/master/components/tidb_query/src/rpn_expr)
https://github.com/tikv/tikv/tree/master/components/tidb_query/src/expr)

/pick-up-challenge


[finalize-classes] Feature request: skip classes with an @final annotation

I have a few classes that should not be inherited, but are sometimes mocked in tests. For these, I use a @final annotation, supported by PHPStan, so that no one can inherit them. It would be nice if this script would take that into account.

could you provide a failing test-case or maybe even a test and a fix?

Closing as this command should be strictly native-PHP based. Ref https://github.com/rectorphp/swiss-knife/pull/20#issuecomment-2100759996
Thanks for understanding


Integrate direct support for RTC clock

We should directly integrate support (in terms of kernel modules and setup script) for the PiFace RTC clock as supported by the the hm-rtc (https://github.com/jens-maus/hm-rtc) CCU Addon package.

After a quick check the corresponding kernel modules are now automatically loaded. Thus, done.


Inconsistent insertion order for addMethodDeclaration fixed

What's changed?
In the previous code, the addMethodDeclaration method had a comparator that compared instances of Statement using UUIDs when they weren't instances of J.MethodDeclaration. This fallback to UUID comparison could lead to inconsistent placement of MethodDeclaration instances.
Here are the key changes made in the modified code:
Refined addMethodDeclaration Method:
Previously, the comparator used a fallback to UUID comparison for non-MethodDeclaration statements. This was changed to explicitly compare J.MethodDeclaration instances using the provided idealOrdering comparator.
This ensures that new MethodDeclaration instances are consistently placed according to the ordering defined by idealOrdering, improving predictability.
No Other Structural Changes:
The structure and organization of the classes and methods remain the same as in the previous code.
The rest of the code continues to provide coordinate builders (JavaCoordinates) for various Java syntax elements (Statement, Expression, Annotation, etc.).
These changes focus on enhancing the reliability and consistency of placing MethodDeclaration instances within Java code constructs, addressing the issue you encountered with intermittent test failures due to placement inconsistencies.
What's your motivation?

Anything in particular you'd like reviewers to focus on?

Anyone you would like to review specifically?

Have you considered any alternatives or workarounds?

Any additional context
Closes issue #4203
Checklist

[ ] I've added unit tests to cover both positive and negative cases
[ ] I've read and applied the recipe conventions and best practices
[ ] I've used the IntelliJ IDEA auto-formatter on affected files

@timtebeek please checkout this PR
Thanks

Hi @Riyazul555 ; it looks like you've converted the ternary operator into an if statement, without changing the logic. I think it might be best to add a unit test to guarantee that we make the correct change, as I don't expect any improvement yet.

Ya I was just testing in another way
Ok I will add it
Thanks

Let's close this PR until such a test is added, just to make it clear this is not yet fixed. We can reopen the PR when a tests is added to the branch.


Transformer loss incorrectly calculated for DC-connected battery

Describe the bug
For PV-battery configurations with DC-connected batteries, with transformer losses specified, SAM calculates very large loss values.

A workaround is to assign the transformer loss input to the AC wiring loss category and set transformer loss inputs to zero.
https://sam.nrel.gov/forum/forum-general/3700
To Reproduce
Steps to reproduce the behavior:

Create a default PV-Battery / Single Owner case.
On the Losses page set both the transformer load and no load loss values to 0.2%.
On the Battery Cell and System page, choose the DC Connected option.
Run.

Expected behavior
Annual transformer loss percentage in results should be of similar magnitude as input percentages.
Operating System and Version
SAM 2021.12.02, tested in Windows

Closed with ssc 728


Revised English translations for transparency titulus

Revised English translations  for the transparency titulus controlled vocabulary in order to respond to comments in issue #184

@giorgialodi come generi il CSV a partire dal TTL?


Binary Search Algorithm

Adds tests for binary search exercise
Update README
Add Search interface

Thanks. Will take a look and add the correct one when I'm at my machine.


Training vram memory usage?

Thanks author for sharing this awasome answer, I have read all the issue about training and know that you use 32G 8v100-gpus, batch=8 to train, which means the 32GB vram is enough. Howere when i run tutorial_train_faceid.py with batch 8, it use almost double of 32 GB. So i wander is there something i miss?
I use
torch==2.0.0+cu118
diffusers==0.22.1
accelerate==0.23.0

I also have a similar issue. In multi-GPU training, there's a problem with the loss gradient updates. I have modified the parameters that the optimizer needs to update. However, the VRAM usage is indeed very high. I suspect that it might be necessary to enable enable_xformers_memory_efficient_attention, and perhaps add a dedicated XFormersAttnProcessor for the IP Adapter.

I used deepspeed to train. also you can use xformers or torch2.0 attention processor

According to https://huggingface.co/docs/diffusers/optimization/torch2.0, memory-efficient attention is enabled by default in torch 2.0. Did you also turn on the offload_param and offload_optimizer to allow batch=8 in V100? Thanks.

I don't use offload_param and offload_optimizer


Exception when using IPs in traceroute headercontraints

I'm getting an exception when using IPs in traceroute headercontraints...
>>> bf.q.traceroute(startLocation='nxos-core1', headers=HeaderConstraints(srcIps='<IP_ADDRESS>', dstIps='<IP_ADDRESS>'),maxTraces=1).answer().frame()
Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "/home/rick/development/tech-sessions/2022-11-netcov/.venv/lib/python3.8/site-packages/pybatfish/question/question.py", line 192, in answer
    return _bf_answer_obj(
  File "/home/rick/development/tech-sessions/2022-11-netcov/.venv/lib/python3.8/site-packages/pybatfish/client/internal.py", line 66, in _bf_answer_obj
    return session.get_answer(question_name, snapshot, reference_snapshot)
  File "/home/rick/development/tech-sessions/2022-11-netcov/.venv/lib/python3.8/site-packages/netcov/hook.py", line 42, in get_answer
    self.cov.collect_trace(answer)
  File "/home/rick/development/tech-sessions/2022-11-netcov/.venv/lib/python3.8/site-packages/netcov/coverage.py", line 92, in collect_trace
    self.trace.update(convert_traceroute_traces([answer.frame()]))
  File "/home/rick/development/tech-sessions/2022-11-netcov/.venv/lib/python3.8/site-packages/netcov/algorithm/converttrace.py", line 30, in convert_traceroute_traces
    action_stats[path[-1][-1]] += 1
  File "<attrs generated hash pybatfish.datamodel.flow.Step>", line 2, in __hash__
    return hash((
  File "<attrs generated hash pybatfish.datamodel.flow.RoutingStepDetail>", line 2, in __hash__
    return hash((
TypeError: unhashable type: 'list'

@rickdonato - This looks like some invalid assumption in how NetCov is parsing TR data. It'll help if you can provide a repro - the snapshot used and any relevant setup before you ran the TR query above.

@ratulm This is the snapshot that Im using... https://github.com/networktocode/interop2020-batfish/tree/master/snapshots/3tier-multivendor


Wizard: support RHEL Installer image type

The image-installer image type is now available in cockpit-composer. Users can select it in the Create Image Wizard. It has no required configuration. Testing is added to verify the fields display as expected.

I'd merge but it looks like I'm not authorized to hit the button.


Change HCL for adding resources to watches

Currently the API for adding a repository (or any type of resource) is like so:
resource "artifactory_xray_watch" "test" {
  name        = "watch-npm-local-repo"
  description = "apply a severity-based policy to the npm local repo"

  resources {
    type       = "repository"
    name       = "npm-local"
    bin_mgr_id = "default"
    repo_type  = "local"
  }
}

I strongly believe that the resources key should be singular (i.e. resource) since it is intended to be specified once per resource you intend to add to the xray watch. This would make this more consistent with the core terraform modules. Given that resource is
resource "artifactory_xray_watch" "test" {
  name        = "watch-npm-local-repo"
  description = "apply a severity-based policy to the npm local repo"

  resource {
    type       = "repository"
    name       = "npm-local"
    bin_mgr_id = "default"
    repo_type  = "local"
  }

  resource {
    type       = "repository"
    name       = "npm-remote"
    bin_mgr_id = "default"
    repo_type  = "remote"
  }
}

Released in v0.0.1


New Feature - #1671 - Added Profile Page for Vets

#1671

The effort is appreciated, but I'm not sure we need this (and the usual policy on new features is to decline). Also the UUID change is kind of unnecessary as well as being invasive.

No worries, I didn't know about the policy :) but thanks for letting me know!
You're right that the UUID change is not necessary; probably overkill.
If you like I can close this PR and work a bit on the existing code base with smaller changes :) .

Contributions always gratefully accepted.


Refactor parsing doc

for parser and stream_parser

Can you elaborate?

I don't see anything particularly wrong with it.


Force rebuild / redeploy

Hey,
I am trying to use tilt in my current environment:
Windows 10 host machine using WSL to run Ubuntu 18.04.
Everything works great so far, only feature that is buggy is the file watch, and auto build+deploy. This seems to be known issue with WSL not fully implementing inotify. There is also more related information in VS Code Repo.
I don't think this is something tilt can (or should) solve, but in order to still use tilt features in an environment that does not support it would be nice to have a force rebuild & deploy in the HUD, just like  can be used to manually to a rebuild (for changed) components, it would be nice to have a force rebuild shortcut as well!
Any thoughts / ideas appreciated!
Cheers,
Datosh

@nicks is this issue resolved with the --auto-deploy flag of tilt up?

@jazzdan no, that doesn't work for this use-case because it still relies on filechange events to do things

@datosh, I don't know if you're still interested in this, but for what it's worth, we've spec'd out a possible solution. TBD when we're going to start implementing, but just wanted to let you know that it's still on our radar.

@maiamcc, thanks for the update :)
I have read the proposed solution, and I think this is heading in the right direction.
In the spec you talk quite a bit about changes to the UI, do you also consider CLI changes? This might be helpful for things like editor / IDE integration. Is this in focus of Tilt?
I think it would be nice to use the build/deploy capabilities of, e.g., VS Code, or even write a simple Tilt plugin to make it a first class citizen in VS Code? No necessarily right now, but keeping the options open.

@datosh yeah, I think that's a possibility, but pretty far in the future for us. Still, it's definitely crossed our minds (it's on our roadmap for later) -- glad to hear that other people are interested in this, it's useful data!

An example issue I had where a way to force a rebuild would be useful:

I make a change and am building / pushing an image. My ECR token times out, causing the push to fail and Tilt to show the error.
Without another code change, I cannot "retry" the build after I login to ECR.

Hey folks, I've just shipped [Force Update]I(https://blog.tilt.dev/2019/11/14/force-update.html) -- take a look and let us know if this meets your needs, and feel free to drop us a line/open another issue if there's big functionality missing, or ways you think we can improve it :)


Creates translations file next to _output

Is this a request for help?: NO

Is this an ISSUE or FEATURE REQUEST? (choose one): ISSUE

What version of acs-engine?: e86076153ce40dfdbd13ff05f0ddc6aca6280727

When running generate the _output directory is created as expected, but so is a translations directory containing some translation files.

This has been fixed in PR #1426! (merged a couple weeks ago), sorry for the inconvenience!


Avatars (and probably other media) do not display with account on a self-signed server

https://matrix.to/#/!tDRGDwZwQnlkowsjsm:matrix.org/$1479806434848416Rbrux:matrix.org

I can confirm that all media does not load. Also the app keeps on reloading every couple of seconds so you have the spinning animation constantly displayed everywhere.

I am experiencing the same problem, though the server's certs are CAcert-issued (not self-signed).
It does not matter whether I give Riot permission to trust the certificate, or install the CAcert certificate profile into iOS.
Probably the issue lies deep inside some Apple black box which fails (or refuses) to work with officially sanctioned certificate authorities.
cc. @mjollnir

This issue is still present on v0.4.3.  Specifically, client connects to a server with self-signed cert.  No media is displayed.  It was the same with v0.3.13 (on app store previously; updated today).

@edam: I tested it again, and I did not reproduce it on a self-signed server.

Hi @giomfo, thanks for taking a look!  Problem is definitely there, and was with v0.3.13 too.  There is no media shown, and server has self-signed cert (although this is possibly not relevant).
Can I help diagnose the problem?  I'm a developer myself, but the phone is a friend's and I am not familiar with iOS myself.  Would it help if I created an account for you on the server for you to test the client against?  Would if help to know what version of iOS the device is running?

@giomfo: platform is iOS v10.3.2 on iPhone 6s.

Pinging. 🙂
Would you like me to set up an account on the server that this issue occurs on to help diagnose the issue in the client?

@edam: Yes please (you may send this account credentials in a PM to @Giom:matrix.org)

May be solved by https://github.com/matrix-org/matrix-ios-sdk/pull/332

@giom: PMed!

@manuroe: #332 would seem to describe the problem accurately.  The self-signed cert was accepted by the user, and all but media downloads work.

I reproduced the issue with the provided account.
(matrix-org/matrix-ios-sdk#332 does not fix it)
Investigation is in progress

@edam: Fixed on matrix-ios-sdk develop. Thanks again for your help.
The MXMediaLoader adds now all the allowed certificates to the chain of trust at the time of preparing the SSL negotiation.


Need to get cert-based authentication working

One tester attempted cert-based authentication and but is stuck towards the end of phase 2 (no meaningful error messages from charon.log) . Do we have a working config we can share which uses cert auth?

Here's an example config that has been shown to work.
The rightid settings in addition to the leftcert are the key differences as compared to when cert auth is not used.
    config setup
      charondebug=2

    conn %default
      leftauth=pubkey
      rightauth=pubkey
      ike=aes256-sha256-modp2048s256,aes128-sha1-modp1024!
      ikelifetime=28800s
      aggressive=no
      esp=aes128-sha256-modp2048s256,aes128-sha1-modp1024!
      lifetime=3600s
      type=tunnel
      dpddelay=10s
      dpdtimeout=30s
      keyexchange=ikev1
      rekey=yes
      reauth=no
      dpdaction=restart
      closeaction=restart
      left=%defaultroute
      leftsubnet=<IP_ADDRESS>/0,::/0
      rightsubnet=<IP_ADDRESS>/0,::/0
      leftupdown=/etc/strongswan/ipsec-vti.sh
      installpolicy=yes
      compress=no
      mobike=no

    conn AWS-VPC-TUNNEL-1
      left=%any
      right=nn.nn.nn.nn
      rightid="CN=vpn-0...db.endpoint-1"
      auto=start
      mark=100
      leftcert=vpn.acme.cloud.pem

    conn AWS-VPC-TUNNEL-2
      left=%any
      right=nn.nn.nn.nn
      rightid="CN=vpn-0...db.endpoint-0"
      auto=start
      mark=200
      leftcert=vpn.acme.cloud.pem

Support for certificate-based authentication has been added to the template.


Wrong package id after plugin install

Hello.
After intalling the plugin in config.xml appear line this your plugin. But the record is wrong because the id is mx.ferreya.callnumber and must be call-number. Please fix it.

Could you please fix this issue? It is very annoying. I would really appreciate it. :)

The plugin.xml file seems to be correct already. Do you plan to deploy a new release with this fix ?

I'm still having this issue, running the command ionic cordova plugin add call-number adds mx.ferreyra.callnumber to my package.json.

anybody have a fix for this.....going crazy here!

@theHellyar  You can solve the problem by changing the version from

to

Because NPM is still in the old version
see : https://www.npmjs.com/package/call-number


Refresh / create another Receive Address doesn't work

Issue description
When clicking the

icon in "Receive Funds", it spins for a few seconds but the "My Address" and the QR-Code do not change.
Wallet version
Which version of wallet are you using?
1.1.0
System specification
Xubuntu 20.04
Is it a repeatable issue?
Y
Steps To reproduce the issue
Explain how the maintainer can reproduce the issue.

Create a wallet
Click on "Receive"
Click on

Expected behaviour
A new receiving address is generated and displayed
Actual behaviour
Nothing happens
Errors
Nothing in the log

Did you already use the address that is displayed? Since the addresses are reusable with Chrysalis you don´t have to generate a new address with every time you would like to send.

No, but having multiple receiving addresses per profile/seed is a valid use case - as you may want to hand out different addresses for different "payment channels" you're expecting.
I guess that's why the "refresh" button is there in the UI in the first place, it's just that it doesn't work.

No, but having multiple receiving addresses per profile/seed is a valid use case - as you may want to hand out different addresses for different "payment channels" you're expecting.
I guess that's why the "refresh" button is there in the UI in the first place, it's just that it doesn't work.

maybe in this case it would be even clearer if you created separate accounts within the profile.


Update "ScpBufrToRaijin" to handle ASCAT L2 soil wetness Bufr files

keyword_APS3_Bufr_remote_copy_sam_MARS_ASCAT_soil_wetness resolution_duplicate   |    by<EMAIL_ADDRESS>
Up until now our global suites used the ASCAT L2 soil wetness data that are archived on sam: sam:/global/ha-sam/mrlr/gen/idharss/ascat. This archive has problems,

"ascatq.20101107_1.bufr" to "ascatq.20161010_1.bufr"
. missing data between 20160108 and 20160116
. smaller file sizes for 20160107 and 20160117

201701/, 201702/, etc.
. only MetOp-1 (=MetOp-B)
. missing data between 20161011 and 20170102
. Bufr files for 20170106 and 20170107 seem small

The new suites which are used for all-sky work and which Fiona is porting currently (they are based on the PS39 and PS40 global standard suites) require ASCAT Bufr files which are not in the sam archive. We will have to use ASCAT data which are available from marsop.
Note 1. In marsop only MetOp-2 (=MetOp-B) is available
Note 2. In marsdev only MetOp-1 is available; also the data from marsdev show strange lines which are perpendicular to swathes
This ticket describes changes made to the "ScpBufrToRaijin" scripts to allow retrievals of ASCAT data from marsop and their transfer to Raijin.

Issue migrated from trac:353 at 2024-01-31 18:33:12 +1100

<EMAIL_ADDRESS>changed status from new to closed

<EMAIL_ADDRESS>set resolution to duplicate

<EMAIL_ADDRESS>commented

The script, "ScpBufrToRaijin" is not a good starting point for what I want to do. I will write a new script (which is described in #355) and close this ticket.

<EMAIL_ADDRESS>commented

From "trunk",
https://access-svn.nci.org.au/trac/nwp/browser/da/utilities/odb/scripts/ScpBufrToRaijin (![604])
I created my development branch,
https://access-svn.nci.org.au/trac/nwp/browser/branches/dev/jtl548/da/utilities/odb/scripts/r604_ScpBufrToRaijin


enterprise model options link in model selector

Link to enterprise model and model provider options in the model selector to show the additional options available in Cody Enterprise.
Depends on https://github.com/sourcegraph/docs/pull/396.

Test plan
CI

@valerybugakov:

Works nicely with sourcegraph/docs#396.
One minor issue I've noticed is that the dropdown menu doesn't close immediately when opening a link using the keyboard. When I return to the VS Code window from my browser, the dropdown menu closes, causing a slight UI flicker.

I see that as well. Will file for a followup fix. Thanks!

Filed at https://linear.app/sourcegraph/issue/CODY-2189/links-in-model-selector-dropdown-do-not-close-dropdown-until-later


[Onboarding] expert view

show status of images in onboarding expert view
be careful, it's not 50% of the width :(

waiting for #311 docker images reporting before calling it "done"


Logs include exception="None\n" when there is no exception

All python SDK logs emit an exception field even when there is no exception. Weirdly, the field is "None\n" with a trailing newline that does not appear in any other field. This field should be omitted when there is no exception, so that searches for "exception" will not return so many spurious results
Example from stackdriver logging in a python job using dataflow runner:
jsonPayload: {
    exception: "None
"
    job: "2019-03-28_18_01_16-4563580283031363654"
    logger: "root:cloud_logging.py:EmitLogMessages"
    message: "baz"
    stage: "s01"
    step: "EmitLogs"
    thread: "132:139730156779264"
    worker: "df2-cloud-logging-python--03281801-ilme-harness-7sw5"
}
Imported from Jira BEAM-6941. Original Jira may contain additional context.
Reported by: edre.

no longer observed. And this is handled in Dataflow but not Beam sdk
.close-issue


Documentation on 's isValidConnection callback is incorrect

Describe the Bug
Documentation on <ReactFlow>'s isValidConnection callback is incorrect.
Hello,
I just wanted to report that the documentation for the isValidConnection callback at https://reactflow.dev/api-reference/react-flow#is-valid-connection states that the callback's type is:
(edge: Edge) => boolean
However, it appears to actually be:
(connection: Connection) => boolean
At least, that's what my IDE (WebStorm) is telling me:

And if I log the parameter of the callback, it looks like a Connection object to me:
const isValidConnection = useCallback((edge : Edge) => {
    console.log(edge);
    return true
}, [])

In fact, a different documentation page (https://reactflow.dev/examples/interaction/validation) correctly uses a Connection object instead of an Edge object.
I am using ReactFlow version 11.10.1
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Create a callback with the signature (edge : Edge) => boolean.
Define a React component that uses a <ReactFlow> instance and set the ReactFlow's isValidConnection callback to the callback you defined in step 1.
Run ESLint or paste your code in WebStorm and observe the type error.

Expected behavior
I believe the code behavior is correct.
The documentation should state that the isValidConnection callback has this signature:
(connection: Connection) => boolean
Screenshots or Videos
No response
Platform

OS: Linux (Ubuntu 22.04.1)
Browser: Chromium

Additional context
Just thought I'd mention that this is my first time using ReactFlow and I'm loving it so far. Keep up the great work!

Thanks for pointing this out, should be fixed on next deployment.


config/v1: add status subresource for infrstrastructure

There are various platform specific status fields for infrastructure. And all of these not not user modifyable.
These fields are setup at the install-time and never changed.
   aws:
     description: AWS contains settings specific to the Amazon Web Services
       infrastructure provider.
     type: object
     properties:
       region:
         description: region holds the default AWS region for new AWS
           resources created by the cluster.
         type: string
   azure:
     description: Azure contains settings specific to the Azure infrastructure
       provider.
     type: object
     properties:
       networkResourceGroupName:
         description: networkResourceGroupName is the Resource Group
           for network resources like the Virtual Network and Subnets
           used by the cluster. If empty, the value is same as ResourceGroupName.
         type: string
       resourceGroupName:
         description: resourceGroupName is the Resource Group for new
           Azure resources created for the cluster.
         type: string
   baremetal:
     description: BareMetal contains settings specific to the BareMetal
       platform.
     type: object
     properties:
       apiServerInternalIP:
         description: apiServerInternalIP is an IP address to contact
           the Kubernetes API server that can be used by components inside
           the cluster, like kubelets using the infrastructure rather
           than Kubernetes networking. It is the IP that the Infrastructure.status.apiServerInternalURI
           points to. It is the IP for a self-hosted load balancer in
           front of the API servers.
         type: string
       ingressIP:
         description: ingressIP is an external IP which routes to the
           default ingress controller. The IP is a suitable target of
           a wildcard DNS record used to resolve default route host names.
         type: string
       nodeDNSIP:
         description: nodeDNSIP is the IP address for the internal DNS
           used by the nodes. Unlike the one managed by the DNS operator,
           `NodeDNSIP` provides name resolution for the nodes themselves.
           There is no DNS-as-a-service for BareMetal deployments. In
           order to minimize necessary changes to the datacenter DNS,
           a DNS service is hosted as a static pod to serve those hostnames
           to the nodes in the cluster.
         type: string
   gcp:
     description: GCP contains settings specific to the Google Cloud
       Platform infrastructure provider.
     type: object
     properties:
       projectID:
         description: resourceGroupName is the Project ID for new GCP
           resources created for the cluster.
         type: string
       region:
         description: region holds the region for new GCP resources created
           for the cluster.
         type: string
   ibmcloud:
     description: IBMCloud contains settings specific to the IBMCloud
       infrastructure provider.
     type: object
     properties:
       location:
         description: Location is where the cluster has been deployed
         type: string
       providerType:
         description: ProviderType indicates the type of cluster that
           was created
         type: string
       resourceGroupName:
         description: ResourceGroupName is the Resource Group for new
           IBMCloud resources created for the cluster.
         type: string
   openstack:
     description: OpenStack contains settings specific to the OpenStack
       infrastructure provider.
     type: object
     properties:
       apiServerInternalIP:
         description: <>
         type: string
       cloudName:
         description: cloudName is the name of the desired OpenStack
           cloud in the client configuration file (`clouds.yaml`).
         type: string
       ingressIP:
         description: <>
         type: string
       nodeDNSIP:
         description: <>
         type: string
   ovirt:
     description: Ovirt contains settings specific to the oVirt infrastructure
       provider.
     type: object
     properties:
       apiServerInternalIP:
         description: <>
         type: string
       ingressIP:
         description: <>
         type: string
       nodeDNSIP:
         description: <>
         type: string
   vsphere:
     description: VSphere contains settings specific to the VSphere infrastructure
       provider.
     type: object
     properties:
       apiServerInternalIP:
         description: <>
         type: string
       ingressIP:
         description: <>
         type: string
       nodeDNSIP:
         description: <>
         type: string

To make sure there are no modifiers of the object, I skimmed through the audit logs of various CI runs to find if there was any client sending update or updating status of the infrastructure.
$ wget https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.4/2173/artifacts/e2e-aws/must-gather.tar
$ wget https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-openstack-4.4/1363/artifacts/e2e-openstack/must-gather.tar
$ wget https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-4.4/1467/artifacts/e2e-gcp/must-gather.tar
$ wget https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-azure-4.4/1476/artifacts/e2e-azure/must-gather.tar

$ cat 0/quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-f663341a354710612436078149ddf989d302e193faabd3896b16544a1a78e6b6/audit_logs/kube-apiserver/*.log > audit.log
$ cat 1/quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-f663341a354710612436078149ddf989d302e193faabd3896b16544a1a78e6b6/audit_logs/kube-apiserver/*.log > audit.1.log
$ cat 2/quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-f663341a354710612436078149ddf989d302e193faabd3896b16544a1a78e6b6/audit_logs/kube-apiserver/*.log > audit.2.log
$ cat 3/quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-f663341a354710612436078149ddf989d302e193faabd3896b16544a1a78e6b6/audit_logs/kube-apiserver/*.log > audit.3.log

$ rg '"requestURI":"/apis/config.openshift.io/v1/infrastructures/cluster"' audit.1.log audit.2.log audit.3.log audit.log  | wc -l
363
$ rg '"requestURI":"/apis/config.openshift.io/v1/infrastructures/cluster","verb":"get"' audit.1.log audit.2.log audit.3.log audit.log  | wc -l
363
$ rg '"requestURI":"/apis/config.openshift.io/v1/infrastructures/cluster","verb":"update"' audit.1.log audit.2.log audit.3.log audit.log  | wc -l
0

And that shows that there are no update calls for infrastructure status..
Not having a subresource status for infrastructure makes controllers fragile as they have to send Update that can mutate the spec, so UpdateStatus is very useful.
/cc @deads2k

While this is technically tightening validation, this is fundamental to proper operation of cluster config and was always intended to have status.  We have sufficient CI testing that we would catch if this breaks an upgrade.  In terms of customer impact, a customer would be able to switch to using UpdateStatus like every other resource, so we are not removing, but correctly securing, access to fields.
/approve

Shouldn't there be a // +kubebuilder:subresource:status tag added in types_infrastructure.go?

/lgtm
/hold
I'd like to see a proof PR in openshift/cluster-config-operator demonstrating that we still work before we merge this.  Once it's green, you may release the hold

found proof in https://github.com/openshift/cluster-config-operator/pull/124
/hold cancel

https://github.com/openshift/cluster-config-operator/pull/124/commits/0590039677e10592d8b9ae10c041204aad205f1a

I added the commit to one of testing PRs yesterday, and the CI was green. Does that cover the proof @deads2k
e2e-aws: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-config-operator/124/pull-ci-openshift-cluster-config-operator-master-e2e-aws/572
e2e-aws-upgrade: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-config-operator/124/pull-ci-openshift-cluster-config-operator-master-e2e-aws-upgrade/283

/retest


HARP-3891: Display generic (open-sourced by Here) road-shields.

Simple solution for generic road-shields display (same for every world
region). Solves problem with different road names (name length).
Signed-off-by: Krystian Kostecki<EMAIL_ADDRESS>

@heremaps-bot ok to test

For now I have used mapbox icons, generated with their tool (requires license check):
https://labs.mapbox.com/map-icon-editor/editor/
Later on we may change it to custom icons created by graphics.

@heremaps-bot ok to test


Change the "Delete Test Case" dialog message

Change it to "This test case is being used by the following test suites.  Do you want to remove it?".

Hi @quockhanh ,
Please help me review this PR https://github.com/rockmelonqa/ide/pull/122

Done:


Grails PR Build Failing with Spaces

I'm using this plugin with a grails wrapper and the variables that GitHub is passing in as environment variables that have spaces (description of pull request, author name, etc.) are causing the errors for the grails wrapper.  Is there a way to configure this plugin so that we do not pass in all of the environment variables?

At the moment there is not.  I am not sure what the proper way to handle this would be.  It would be possible to escape the parameters before queueing up the job.

Is there a way to escape all of the variables that get passed in? Or are
you saying I should escape each space individually then creating thr PR and
commenting on it?
On Fri, Jun 12, 2015, 16:54 David Tanner<EMAIL_ADDRESS>wrote:

At the moment there is not. I am not sure what the proper way to handle
this would be. It would be possible to escape the parameters before
queueing up the job.
—
Reply to this email directly or view it on GitHub
https://github.com/jenkinsci/ghprb-plugin/issues/99#issuecomment-111628270
.

Closing this issue due to inactivity. If it still persists please reopen. I am just going through the old issues here to cleanup a bit.


Update github.com/minio/minio-go

This corrects a severe performance regression when the current minio
server is used as a backend, see
https://github.com/minio/minio/issues/4275

Codecov Report

Merging #946 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #946      +/-   ##
=========================================
- Coverage   55.72%   55.7%   -0.02%
=========================================
  Files         101     101
  Lines        7918    7918
=========================================
- Hits         4412    4411       -1
- Misses       2864    2865       +1
  Partials      642     642

Impacted Files
Coverage Δ

src/restic/archiver/archiver.go
64.74% <0%> (-0.23%)
:arrow_down:

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 db6541b...c09e005. Read the comment docs.


peer to peer

there's a problem with the line spacing in the css file , line spacing is important to avoid the linters errors .

My suggestion is that you should try to use prettier extension on vscode to solve spacing and code structure

done


Touch example .ino

Can we get an example multifunction sketch showing us how to use screen/touch/sd card etc simultaneously. I'm struggling to get the features I need working together with the limited resources.

Hello @jaylfc
have you checked out the Touch example in the Unified repository? It shows how to use screen and touch. For the SD card maybe check out this example.
Thanks
Felix

I have thanks ,they helped a little!


chore: make start:backstage to ignore cli package

@mareklibra noticed yarn start:backstage also starts @janus-idp/cli package. This is not the desired behavior.

LGTM


Adding a rough draft for the guardrail book

The intent of book.md is to be:

Provide motivation for why potential users should care about guardrail/OpenAPI
Longer form than README.md, covering each section with more depth
Permit README.md to be made shorter, into an actual quickstart, taking over for the sprawling brain-dump in QUICKSTART.md
Compiled by https://github.com/tpolecat/tut, permitting real compiler errors and generated code to be included inline in chapters.

@chrisphelps I'm merging this in its current state, though I'm interested in your thoughts on the most recent iteration if you've got a minute. Thanks for taking a look!


Bugfix for Error Record Category

The input validation was not sufficient, causing the function to resolve to a bad error category, when ...

An inner error record was provided
That error record would not contain a proper CategoryInfo
A new validation condition is applied, ensuring that only when a valid categoryinfo property is on the record it will be used to override the default

Thanks fred!


When creating a Measurement object with the python package _ecal_hdf5_py is not found

I'm trying to setup eCal's python library in a docker container which runs Ubuntu 18.04. (Previously we used eCal 5.3.6, so basically we'd like to upgrade for the latest version.)
I'm installing eCal the following way:
add-apt-repository ppa:ecal/ecal-latest
apt install -y python3.7 python3-pip
apt-get install -y ecal
apt install -y python3-ecal5

I was following the documentation found here: https://eclipse-ecal.github.io/ecal/getting_started/hello_world_python.html
(I know there the recommended python version is simply python3, but for other reasons we need 3.7.)
When I check with pip list, I see that eCal5 is indeed installed:
ecal5                    5.10.1

However when I try to create a Measurement object I get the following error:
#python
Python 3.7.13 (default, Apr 24 2022, 01:04:09)
[GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from ecal.measurement.measurement import Measurement
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/ecal/measurement/measurement.py", line 26, in <module>
    import ecal.measurement.hdf5 as ecal_hdf5
  File "/usr/lib/python3/dist-packages/ecal/measurement/hdf5.py", line 32, in <module>
    import ecal._ecal_hdf5_py as _ecalhdf5
ModuleNotFoundError: No module named 'ecal._ecal_hdf5_py'

With the previous version (5.3.6) we didn't have this error (although we built that from source).
When I list the package's library for the latest install, I see this:
# ll /usr/lib/python3/dist-packages/ecal
total 432
drwxr-xr-x 7 root root   4096 Aug 26 14:04 ./
drwxr-xr-x 1 root root   4096 Aug 26 14:04 ../
-rw-r--r-- 1 root root      0 May 24 09:41 __init__.py
drwxr-xr-x 2 root root   4096 Aug 26 14:04 __pycache__/
-rw-r--r-- 1 root root  74536 May 24 09:41 _ecal_core_py.cpython-36m-x86_64-linux-gnu.so
-rw-r--r-- 1 root root 333440 May 24 09:41 _ecal_hdf5_py.cpython-36m-x86_64-linux-gnu.so
drwxr-xr-x 3 root root   4096 Aug 26 14:04 core/
drwxr-xr-x 3 root root   4096 Aug 26 14:04 measurement/
drwxr-xr-x 7 root root   4096 Aug 26 14:04 pb/
drwxr-xr-x 3 root root   4096 Aug 26 14:04 proto/

So the files seems to be there.
Thus I ran:
chmod 755 /usr/lib/python3/dist-packages/ecal/_ecal_hdf5_py.cpython-36m-x86_64-linux-gnu.so
chmod 755 /usr/lib/python3/dist-packages/ecal/_ecal_core_py.cpython-36m-x86_64-linux-gnu.so
cp /usr/lib/python3/dist-packages/ecal/_ecal_core_py.cpython-36m-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/ecal/_ecal_core_py.so
cp /usr/lib/python3/dist-packages/ecal/_ecal_hdf5_py.cpython-36m-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/ecal/_ecal_hdf5_py.so

And after removing the cpython-36m-x86_64-linux-gnu part of the filename plus set the .so files to be executables our code finally works once again.
I'm not sure however whether I've missed a step in the setup or this is an actual issue.
May I get a comment on this?

Hi Kvrepo,
Ubuntu 18.04's default python version is python 3.6, not 3.7. Therefore, via apt-get you can only install the 3.6 binding of eCAL. You will have the same issue with every other python package as well, via apt-get.
What you can do is simply install the .whl from the eCAL Downloads page:
https://eclipse-ecal.github.io/ecal/_download_archive/download_archive_ecal_5_10_2.html
There you can find bindings for other python versions as well (including 3.7 on Bionic). That should fix your issue without having to copy and rename any shared object file 😉
Best Regards
Florian

I didn't mention this, but we've installed python 3.7 on Ubuntu 18.04 by adding the necessary repos (ppa:deadsnakes/ppa).
However reading your comment made me realize that this decision came with some unforeseen consequences.
If I switch from bionic to focal and make the transition to python 3.8 from 3.7 I can install eCal just fine with apt install -y python3-ecal5 and everything works as intended.
Thank you very much for the fast and helpful response!

Switching to Focal is a good idea anyways, as Bionic will go out of support in April 2023 👍


added ionosphere dataset

Description

Issue Ticket Number
Fixes #(issue_number)

Checklist:

[ ] I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
[ ] I have cross-checked that the dataset I'm uploading is not present in the project
[ ] I have cross-checked that the dataset is present in the correct folder

Good one @Mahakal0123
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow these steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to the 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.


Debian packaging, CMake and README.md fixes

See invididual commits for details. I am preparing to upload stlink to Debian, and these are some changes required to pass the new package review process.
Fixes https://github.com/texane/stlink/issues/682

@xor-gate ping

Thanks!

Thank you for your effort!

stlink package is pending here, no idea when it will be the archive: https://ftp-master.debian.org/new/stlink_1.5.0+ds-1.html

stlink-tools and stlink-gui are now available in Debian unstable, testing and stretch-backports, and Ubuntu 18.10

great, thanks @bluca

I made a PR to change the README.md https://github.com/texane/stlink/pull/821


Build and release an Android app

Hi I have followed flutter.dev instruction on how deploy an app but I end up with is error below
FAILURE: Build failed with an exception.

What went wrong:
Gradle could not start your build.

Cannot create service of type TaskExecuter using method ProjectExecutionServices.createTaskExecuter() as there is a problem with parameter #17 of type ReservedFileSystemLocationRegistry.
Cannot create service of type ReservedFileSystemLocationRegistry using method ProjectExecutionServices.createReservedFileLocationRegistry() as there is a problem with parameter #1 of type List.
Could not create service of type ExecutionHistoryStore using ExecutionGradleServices.createExecutionHistoryStore().
Cannot lock execution history cache (/Users/aoomle/Documents/Prototypes/Freelancer/pokdoc_doctor/android/.gradle/6.7/executionHistory) as it has already been locked by this process.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2s
Running Gradle task 'assembleRelease'...                            3.3s
Gradle task assembleRelease failed with exit code 1
aoomle@Abdulmaliks-MBP pokdoc_doctor %

@codewithmalik
The error you are getting seems to be coming from Gradle itself:
Could not create service of type ExecutionHistoryStore using ExecutionGradleServices.createExecutionHistoryStore().
> Cannot lock execution history cache (/Users/aoomle/Documents/Prototypes/Freelancer/pokdoc_doctor/android/.gradle/6.7/executionHistory) as it has already been locked by this process.

This may be causing by running gradle in a folder where you lack permissions. Ensure that your project and gradle home have rwx on linux/macOS and/or do not require admin permissions on windows.
Closing from here. If you disagree, write in comments and I'll reopen.

Thanks @darshankawar, Please how do i fix it

The only thing that fixed it for me was a restart of IntelliJ IDEA.
Otherwise....
In the same directory as the file from the error, is there any  .lock file?
(in this case close to .gradle/6.7/executionHistory/executionHistory.bin, from your project folder).
ls .gradle/6.7/executionHistory
-rw-r--r--  1 yoyo  unicorn    14M Feb 14 00:33 executionHistory.bin
-rw-r--r--  1 yoyo  unicorn    39B Feb 14 00:36 executionHistory**.lock**

Deleting the .lock file might free-up the permission.
rm .gradle/6.7/executionHistory/executionHistory.lock
However, it didn't solve the problem for me.


Prototyping tests was added

Current coverage is 73.53% (diff: 100%)

Merging #5 into master will not change coverage

@@             master         #5   diff @@
==========================================
  Files            59         59
  Lines          2093       2093
  Methods         403        403
  Messages          0          0
  Branches        150        150
==========================================
  Hits           1539       1539
  Misses          554        554
  Partials          0          0

Powered by Codecov. Last update a05a6d9...3ec99a4


Translations update from Weblate

Translations update from Weblate for mattermost-languages-shipped/mattermost-mobile.
Current translation status:

Hello @weblate,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

i'm going to merge it to avoid any issues in the weblate side


fixed bug causing particles to freeze

one line change to reset the particles life time when a new particle is emitted. closes #56886

Superseded by https://github.com/godotengine/godot/pull/57302.


Warning Original test failed

Hello :D. I have a gtest that normally run for 3-4 minutes but if I use mull on it, it gives me a warning: original test failed , status: Timedout
    [warning] Original test failed
    test: main
    status: Timedout
    stdout: 'Running main() from /usr/src/googletest/googletest/src/gtest_main.cc
    [==========] Running 10 tests from 1 test suite.
     Finished in 3009ms

As you can see in Log the test runs for 3 secs.
I also tried to increase timer to 90000ms using --timeout=90000 and it runs for a bit longer, 8 secs circa
    [ RUN      ] Sunlight.Radiance_range
    [2021-06-04 21:30:55.478251] [0x00007f3869edf740] [debug]   hourly log mark
    [-----more Logs-----]
    [2021-06-04 21:31:03.877599] [0x00007f3869edf740] [debug]   hourly log mark
    [2021-06-04 21:31:03.887255] [0x00007f3869edf740] [debug]   hourly log mark
    [2021-06-04 21:31:03.896910] [0x00007f3869edf740] [debug]   hourly log mark
    [2021-06-04 21:31:03.906'
    stderr: ''

           [################################] 1/1. Finished in 90019ms

It doesn't seems affect the number of mutations detected, but is a warning that bothers me a bit. There is a way to solve it?
Thank you very much.
P.S. I also incresed the timeout up to 10 minutes, but I had not appreciable results.

P.S. I also incresed the timeout up to 10 minutes, but I had not appreciable results.

It should've fixed the problem if the original code finished after 3-4 minutes. Can you share the log with the 10 minutes timeout (omitting the test output logs)?

That's all the log mull prints far now, i had to run it again, It is running significantly slowest.
    [info] Extracting bitcode from executable (threads: 1)
           [################################] 1/1. Finished in 52ms
    [info] Loading bitcode files (threads: 1)
           [################################] 7/7. Finished in 191ms
    [info] Sanity check run (threads: 1)
    [warning] Original test failed
    test: main
    status: Timedout
    stdout: 'Running main() from /usr/src/googletest/googletest/src/gtest_main.cc
    [==========] Running 10 tests from 1 test suite.
    [----------] Global test environment set-up.
    [ RUN      ] Sunlight.Radiance_range
    [2021-06-04 22:32:02.985946] [0x00007f4a6193c740] [debug]   hourly log mark
    [---Logs---]
    [2021-06-04 22:32:11.366417] [0x00007f4a6193c740] [debug]   hourly log mark
    [2021-06-04 22:32:11.376'
    stderr: ''
           [################################] 1/1. Finished in 600177ms
    [info] Gathering functions under test (threads: 1)
           [################################] 1/1. Finished in 0ms
    [info] Applying function filter: no debug info (threads: 1)
           [################################] 1219/1219. Finished in 1ms
    [info] Applying function filter: file path (threads: 1)
           [################################] 1023/1023. Finished in 1ms
    [info] Instruction selection (threads: 1)
           [################################] 50/50. Finished in 6ms
    [info] Searching mutants across functions (threads: 1)
           [################################] 50/50. Finished in 2ms
    [info] Applying filter: no debug info (threads: 1)
           [################################] 55/55. Finished in 0ms
    [info] Applying filter: file path (threads: 1)
           [################################] 55/55. Finished in 0ms
    [info] Applying filter: junk (threads: 1)
           [################################] 55/55. Finished in 2941ms
    [info] Deduplicate mutants (threads: 1)
           [################################] 1/1. Finished in 1ms
    [info] Prepare mutations (threads: 1)
           [################################] 1/1. Finished in 0ms
    [info] Cloning functions for mutation (threads: 1)
           [################################] 7/7. Finished in 106ms
    [info] Removing original functions (threads: 1)
           [################################] 7/7. Finished in 17ms
    [info] Redirect mutated functions (threads: 1)
           [################################] 7/7. Finished in 0ms
    [info] Applying mutations (threads: 1)
           [################################] 30/30. Finished in 0ms
    [info] Compiling original code (threads: 1)
           [################################] 7/7. Finished in 1203ms
    [info] Link mutated program (threads: 1)
    [info] Compiled executable: /tmp/mull-35eeca.exe
           [################################] 1/1. Finished in 1283ms
    [info] Warm up run (threads: 1)
    [################################] 1/1. Finished in 600083ms
    [info] Baseline run (threads: 1)
    [-----Still Running-----]

I take it back, the warning affects definitively the mutations, while mull detect a certain ammount of mutations it seems it's not able to mutate theme and consider theme killed.
This is the script inside the make i use to start mull
#!/bin/sh

mull-cxx --linker=clang++-10 --linker-flags="-lpthread -lboost_log /usr/local/lib/libgtest_main.a /usr/local/lib/libgtest.a" \
--include-path=$2  \
-compilation-flags="\
-isystem /usr/lib/llvm-10/lib/clang/10.0.0/include \
-isystem @PATH_DIRECTORY_INCLUDE@ \
-isystem @PATH_DIRECTORY_SYSTEM@
-isystem @PATH_DIRECTORY_TEST@/Utilities " $1

$2 = the file I want to mutate
$1 = the executable
Anyway the problem occurs only when i call a function several time, something like 24100365*3600 times, could be bacause a some sort of mull buffer filled, or a sort of block to AST that avoids to many branches?

Yeah, if the original test finishes in 3-4 minutes, but Mull timeouts after 10 minutes, then it's certainly a bug on our side.

@AndreiBogdanPislaru here my 50 cents:

Which kind of code are you running? Is this a pure computation, i.e. algorithm, or you also have things like reading to files, accessing network, signals or timers?

Anyway the problem occurs only when i call a function several times, something like 24 * 100 * 365 * 3600 times, could be because a some sort of mull buffer filled, or a sort of block to AST that avoids the creation of too many branches?

2a) Can you confirm that if you run your function only once, then everything works?
2b) Could you print "Running function round N" and let us know after how many rounds your function timeouts / fails?
The strategy for solving this would be to find a delta between the part that works and the part that no longer works. After that, it could be easier to identify the contributing cause.

Hello @stanislaw :D.

The code just simulate passing time, every hour a log is printed (an hour correspond at 360.000 function calls).
2a. I use the same function also to test the code after one our passing and one day passing and mull does not complain.
2b. I introduce a counter to see how many times the inner function (which simulate one second passing) is called and mull stops the test after simulated 117 day, more precisely after 1.010.880.021 calls to the inner function, that with --timeout=120000, i tested also with --timeout=60000, but there is no difference.

probably the #915 will also fix this issue. The way timeout was passed to report seemed to not cause the expected behavior.

@AndreiBogdanPislaru Would you mind having a look if this is also fixed?

Oh yes, I was waiting for the last release, the problem now is fixed, thank you!!


Enabling Read-Through Caching via environment variable for Docker

It would be great to be able to have Read-through caching enabled even with the Docker version.
Maybe by adding and using two environment variables like:
Mirror__Enabled=true
Mirror__PackageSource="https://api.nuget.org/v3/index.json"

Or simply the second one (as its presence or absence would determine the mirro enabling/disabling

That should already work - I'm doing it that way and it is properly behaving as a read-through cache.  .NET's configuration framework can also read from environment variables with double-underscores separating object names.

Yup, what @Shamus03 said is correct. Did that work for you @edouardberthe?


add overview text for the extensions as a whole

add overview text for the extensions as a whole – describing why they are there and any rules for implementation (e.g., that user manipulation needs to be implemented as a whole and cannot be implemented in parts)

Added to spec


Sending a platform message on iOS can happen before the engine is ready with no error

Ideally, there would be a way to wait for the engine to finish setting up.  E.g., the following code is racy (and consistently is a no-op for me on a simulator):
 FlutterEngine* engine = [[FlutterEngine alloc] initWithName:@"PlatformViewTest" project:nil];
    [engine runWithEntrypoint:nil];

    [engine.binaryMessenger sendOnChannel:@"set_scenario" message:[@"text_platform_view" dataUsingEncoding:NSUTF8StringEncoding]];

Adding a sleep makes things "work".
Ideally, this message would get delivered once the engine was ready.
/cc @jmagman @xster @chinmaygarde @gaaclarke

@dnfield Sounds like you figured this out and there is already a channel message for this?

The race is because both Dart and native sides needs to have setup the channels before they can communicate over the same. You can setup a mechanism where one side pings the other and sets up a response handler (sendOnChannel:message:binaryReply: in your case). Message that are dropped on the floor because the other side is not setup yet will not get a response. Retry till you get a response.

I did figure this out.  I wonder if there's a way that we could throw an error if you try to send a message to a channel that isn't registered?

Makes sense but that would be a significant breaking change.

Perhaps it could be another overload that you opt into, e..g on iOS it'd be something like sendOnChannel:@"set_scenario" message:foo failIfNotRegistered:YES, and default it to NO on the existing overloads.

I think this class of problems (confusing setInitialRoute, deep linking etc) will keep re-occurring until we solve the channel timing issue https://docs.google.com/document/d/1AKPWL50wzQFTSaEz2AbGZm5Fkm01uvunZH8AEoLJMRI (sorry, not public yet)

If we used a ring buffer to hold messages when getting communicated from objc to dart this could work.  This would mean messages sent too early won't get dropped, just postponed (unless you overflow the buffer before the reader gets initialized).
Pseudocode:
-- Objc Thread --
sendMessage(data) {
ring_buffer_.push(data);
condition_.signal();
}
-- Dart Thread --
run() {
while (true) {
while (!ring_buffer_.empty()) {
handle(ring_buffer_.pop());
}
condition_.wait();
}
}

It's probably enough to just hold the last message. It would also be nice to do this in some platform agnostic way if possible, so we don't have separate implementations for Android/iOS/Fuchsia/macOs/Windows/Linux/Web ... although web might need to be separate.

FWIW, this code is what I used to make things work reliably:
engine.binaryMessenger
        setMessageHandlerOnChannel:@"scenario_status"
              binaryMessageHandler:^(NSData* _Nullable message, FlutterBinaryReply _Nonnull reply) {
                [engine.binaryMessenger
                    sendOnChannel:@"set_scenario"
                          message:[@"text_platform_view" dataUsingEncoding:NSUTF8StringEncoding]];
              }];

And on the dart side:
  final ByteData data = ByteData(1);
  data.setUint8(0, 1);
  window.sendPlatformMessage('scenario_status', data, null);

at the end of main (after I set up my handler for the channel).

https://github.com/flutter/engine/blob/25ffa223b9576e8db64a6d24b164f5fb6c4e2d5c/shell/common/engine.cc#L272
I suspect this is where the messages are getting dropped.  This method silently drops messages if IsRootIsolateRunning() returns false.

It's that, but it's also in lib/ui/runtime_controller.cc and lib/ui/window.cc:264.  We can drop messages if there's no window, and we can drop messages if the dart state has disappeared after that, and we can drop messages if they get to hooks.dart:152 and the message handler just hasn't finished setting up yet on the Dart side.

This is reproducible 100% of the time with the following patch and running testing/scenario_app/run_ios_tests.sh
--- a/testing/scenario_app/ios/Scenarios/Scenarios/AppDelegate.m
+++ b/testing/scenario_app/ios/Scenarios/Scenarios/AppDelegate.m
@@ -21,17 +21,19 @@
   // under test will create platform views.
   if ([[[NSProcessInfo processInfo] arguments] containsObject:@"--platform-view"]) {
     FlutterEngine* engine = [[FlutterEngine alloc] initWithName:@"PlatformViewTest" project:nil];
+    NSLog(@"foobar run start");
     [engine runWithEntrypoint:nil];
-
+    NSLog(@"foobar run stop");
     FlutterViewController* flutterViewController =
         [[NoStatusBarFlutterViewController alloc] initWithEngine:engine nibName:nil bundle:nil];
-    [engine.binaryMessenger
-        setMessageHandlerOnChannel:@"scenario_status"
-              binaryMessageHandler:^(NSData* _Nullable message, FlutterBinaryReply _Nonnull reply) {
+//    [engine.binaryMessenger
+//        setMessageHandlerOnChannel:@"scenario_status"
+//              binaryMessageHandler:^(NSData* _Nullable message, FlutterBinaryReply _Nonnull reply) {
+                NSLog(@"foobar send message");
                 [engine.binaryMessenger
                     sendOnChannel:@"set_scenario"
                           message:[@"text_platform_view" dataUsingEncoding:NSUTF8StringEncoding]];
-              }];
+//              }];
     TextPlatformViewFactory* textPlatformViewFactory =
         [[TextPlatformViewFactory alloc] initWithMessenger:flutterViewController.binaryMessenger];
     NSObject<FlutterPluginRegistrar>* registrar =

The fix Dan did to make this test pass doesn't work how we thought it did.  It makes the test pass because the initializer for the _scenarios[1] variable constructs a PlatformViewScenario which in its constructor it asynchronously sets himself up to be rendered.[2]
The question still remains, "Why isn't the set_scenario message getting delivered?"
[1]https://github.com/flutter/engine/blob/8f4a0a7c9aa041bd0fc60a7d994bd956be2f3c5c/testing/scenario_app/lib/main.dart#L18
[2]https://github.com/flutter/engine/blob/8f4a0a7c9aa041bd0fc60a7d994bd956be2f3c5c/testing/scenario_app/lib/src/platform_view.dart#L86


Alarms and automation

Hello.
Fusion Solar add-on is working in HA, thank you for your work however I have issue with my physical inverter due to too high voltage in grid that cause shutdown.
In Fusion Solar portal for today I see this alarms:

In HA first of all I see two statuses

One is empty and second is:

What is strange do not see change about 13:01 in HA and missing shutdown status like form yesterday:

I try build automation notification but not working, my current notification automation config is:
`
alias: Powiadomienie inwerter XXXXXX Shutdown
description: ""
trigger:

platform: state
entity_id:

sensor.inverter_1_inverter_status
to: "changed to Shutdown: unexpected shutdown"
condition: []
action:

service: notify.notify
data:
data:
actions:
- action: URI
title: Open Url
uri: /energy
message: Inwerter XXXXX wywalony
title: Inwerter XXXXX Shutdown
mode: single
`

I try build automation base on below status string of inverter  but I general not working:
"changed to Shutdown: unexpected shutdown"
"Shutdown: unexpected shutdown"
"unexpected shutdown"
Due to I jump to dev in HA tool and found this:

and seems status in numerical valu, what should I use in my automation?
Summary

It is possible download to HA Alarms?
Why I do not see shutdown status of inverter for today? In Fusion Solar portal for yesterday and today status is the same - grid over-voltage but yesterday got shutdown status but today no?
Do not see change status about 13:01 today (now is almost 14:00 when I write this and still no change status)
It is possible that some statuses do not download to HA? How to check what status are visible in API for today? I'd like compare with HA statuses? Can ask for short instruction?
How I can build notification about over-voltage / shutdown in HA? Should use string or numerical value?

BR, Krzysiek

All data that is exposed through the following calls is available in HA, and is updated regularly

/thirdData/getDevRealKpi
/thirdData/getKpiStationYear

Note that this pulled from the API, and not pushed from the API to HA. So there can be delays, or missing information if the status changes between these intervals. For instance if the update is x:10, x:20, x:30, ... and the status changes at x:11 and changes back to another status at x:19, that won't be visible in HA.
You can find the status codes and their translation at: custom_components/fusion_solar/translations/en.json
All the information that is used to develop this integration comes from master/docs/imaster-neteco-v600r022c00-northbound-interface-reference-v6.pdf.
I think you will need to use the numerical values as the translations happen through the HA system, see Translating the state of entities for more information

@kzajac83 was the information I gave clear? I will close this issue, but feel free to reopen the issue if needed.


First cell appears behind the textInputBar instead of above it

The first UITableViewCell in the UITableView is behind the textInputBar when the UIViewController appears instead of having a top content inset greater than 0. It will only fix itself when I tap on the textView (bringing up the keyboard) and then tap off of it (dismissing the keyboard).
This is after upgrading from v1.7.2 to v1.8. I bisected around and looks like https://github.com/slackhq/SlackTextViewController/commit/3ce0f7bf57c62989e00ae156fff925736cb9c16d breaks it.

Found out what's going on. I was adding a UIRefreshControl to the UITableView to the top as usual (which will put it at the bottom since inverted == true).
However, I called refreshControl.beginRefreshing() in viewDidLoad so it'll show as refreshing when the user comes into the screen. I'm guessing UIRefreshControl does some contentInset changes that messes with the contentInset changes that you guys do.
Moving refreshControl.beginRefreshing() to viewDidAppear fixes the issue.
Feel free to close if this is too specific of a bug.


Rethinking core backup process - adopting to Docker

Ideally, it will be great if users can use this tool in a container environment.

Start Docker container
Issue commands to our tool and it should do the trick.

The concern is historically our tool designed to work on the same host where MySQL was installed. So basically it checks if MySQL server is up and running, and if the specified backup and other directories exist or not, etc.
We need to discuss how design and flow should be changed to create the best experience.

Already started to implement as first step with #419
Closing this as DONE


Bandwidth achieved for INT8 is much smaller than FP16

I run CodeLlama 7B: when I use FP16, bandwidth achieved is 700 GB/s; however, when I use INT8, it is 197 GB/s. I run the model on one AMD MI210 GPU. Why is bandwidth achieved lower using INT8?
@kit1980 @msaroufim @yifuwang @huntzhan
Thanks, Yao Fehlis (AMD)

The above numbers are acquired using PyTorch 2.1 ROCm 5.6. When I used PyTorch 2.2 ROCm 5.7, the results are much better. However, INT8 is still lower than FP16. I have seen your results on the website for that trend as well. Do you know why?

the quantization overhead is to blame, at least for the numbers in the README. You're doing the same amount of computation in the matmul but also have to decompress the loaded int8 weight. While you gain a lot of e2e perf from ~2x faster load speed, you lose a bit from the overhead but in terms of Memory Bandwidth you don't gain anything from the loading half as much data twice as fast. Its unclear why it'd be so bad for AMD GPU's, the int8 weight only kernel is a bit finicky though so it might be handled differently on AMD.
I'd recommend also not using Fp16, the quantized model is set to operate in bf16 and that might not be playing well with fp16.
Finally, the option torch._inductor.config.use_mixed_mm = True changes the kernel to a triton one which may perform differently on your hardware.

Yeah, generally speaking, when you go from int8 to int4, the "theoretical" speedup should be 2x. But in practice, due to Amdahl's law type reasons, you end up getting bottlenecked by other factors and so the actual speedup is less than 2x. And that results in a lower "memory bandwidth"


added IE 8 support

I think IE 8 support is pretty standard throughout the industry since companies don't pay for upgrades if they can get away with it.
Here's a demo if you have IE 8 and want to try:
http://codepen.io/lacoolj/full/RPPqay/
See issue #10 for extra info.

Hi Deryck,
why you closed the pull request?

Because with the exception of load time, supporting IE 8 provides no improvement on current capabilities of the browser.  That and when scrolling DOM can't keep up with the JS so the rows disappear until stopping (though this may be partly because of my testing in a virtual machine).  If you can test on a Windows or Mac PC and you don't have this issue I'll re-fork and pull again (and add the other small changes I forgot to put last time - revisit the codepen for specifics).

Exception of demo page load time? This occurs because the insert 50000 rows in the table. DOM can't keep up fast scrolling elements, that's true, but rows appears once stop scrolling, that's fine for so ancient browser. btw it seems fine when scroll by mouse wheel.
I decided to include ie8 support as it will cost only extra 0.07kb, so pull again please


Querying required instance extensions always fails

When i try to use vulkanalia's get_required_instance_extensions i always get an empty list.
The memory view during debug looks like:

If i copy the function and change .collect::<HashSet<_>>() to .collect::<Vec<_>>() it works.
I am using cargo/rustc version 1.49.0 stable on win32 (MSVC).
Does that help?

also the comparison between the c_char arrays seem to not work.

I compiled and ran the triangle example with Rust 1.49.0-i686-pc-windows-msvc and 1.49.0-x86_64-pc-windows-msvc and in both cases get_required_instance_extensions returned the correct list of extensions.
I loosely based the window module off of ash's ash-window crate, and it seems they have changed their implementation to simply return the extensions for the raw window handle. I think I will change my window module to do the same which will hopefully also fix this issue.

I just checked out the current version from git, no changes.
This is my result:
vulkanalia\examples>cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.20s
     Running `C:\Users\ChristopherKoenig\PrivateProjects\vulkanalia\target\debug\triangle.exe`
thread 'main' panicked at 'could not load vkCreateWin32SurfaceKHR', vulkanalia\src\vk\commands.rs:6830:25
stack backtrace:
   0: std::panicking::begin_panic<str*>
             at C:\Users\ChristopherKoenig\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:521
   1: vulkanalia::vk::commands::{{impl}}::load::fallback
             at C:\Users\ChristopherKoenig\PrivateProjects\vulkanalia\vulkanalia\src\vk\commands.rs:6830
   2: vulkanalia::vk::extensions::KhrWin32SurfaceExtension::create_win32_surface_khr<vulkanalia::Instance>
             at C:\Users\ChristopherKoenig\PrivateProjects\vulkanalia\vulkanalia\src\vk\extensions.rs:6267
   3: vulkanalia::window::create_surface
             at C:\Users\ChristopherKoenig\PrivateProjects\vulkanalia\vulkanalia\src\window.rs:56
   4: examples::App::new<triangle::TriangleExample>
             at .\src\lib.rs:78
   5: triangle::main
             at .\src\bin\triangle.rs:23
   6: core::ops::function::FnOnce::call_once<fn() -> core::result::Result<tuple<>, anyhow::Error>,tuple<>>
             at C:\Users\ChristopherKoenig\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:227
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
error: process didn't exit successfully: `C:\Users\ChristopherKoenig\PrivateProjects\vulkanalia\target\debug\triangle.exe` (exit code: 101)

Well that's because I hadn't made the change yet!
However, the proposed change is now in the misc-updates branch if you want to try it out.
I also need to make some other changes which will be in the next release, namely that I think I need to mark pretty much all the functions as unsafe due to how easy it is to run into undefined behavior/crashes/etc. in Vulkan even with the tiniest of mistakes.

Well that's because I hadn't made the change yet!

Just wanted to make sure that I have the issues with the provided example as well :) (a verification so to say)

I also need to make some other changes which will be in the next release, namely that I think I need to mark pretty much all the functions as unsafe due to how easy it is to run into undefined behavior/crashes/etc. in Vulkan even with the tiniest of mistakes.

I was happy i didnt have to do much unsafe (unlike ash) but i can see and understand your point.

Sorry, I read it as you thought I meant that I had pushed a fix.
Fortunately, now I have (maybe).
The updated window module is in v0.6.0 which has just now been released, hopefully it fixes the window extension problem.
Unfortunately so is The Great Unsafening™.
I agree having everything marked as unsafe is annoying but I shot myself in the foot many times while porting/writing the tutorial chapters (which included several segfaults and mysterious crashes). I can't in good conscience let these functions stay bereft of unsafe, our benevolent crab overlord Ferris would surely disapprove.

just a heads up, latest version (0.6) works as expected.


Require PHP 5.6 or newer.

Coverage remained the same at 100.0% when pulling 38ca6da75b3a4ebd4a1135245acb690e0bf3747f on php-56 into 58ae2802cb3a26b13479bcaaaadbcfdd7388d9a8 on master.

Coverage remained the same at 100.0% when pulling 796271a49a119e03af653c92ac2c58b31521fdf5 on php-56 into 58ae2802cb3a26b13479bcaaaadbcfdd7388d9a8 on master.


url to add

https://arxiv.org/abs/2404.10699

Thanks! All the links are added now. You can access the dataset too!