Malformed errors returned when key-value store is locked

Is this a request for help?: No

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

Which release version?: v1.0.11

Which component (CNI/IPAM/CNM/CNS): CNI

Which Operating System (Linux/Windows): Windows Server version 1803
Which Orchestrator and version (e.g. Kubernetes, Docker): Kubernetes v1.10.6

What happened:
When I try to scale up to several pods on the same node, there will be some store locking issues as overlapped calls are made to the Azure CNI binary.
2018/08/15 21:11:45 Going to send Telemetry report to hostnetagent http://<IP_ADDRESS>/machine/plugins?comp=netagent&type=cnireport
2018/08/15 21:11:45 "Start Flag false CniSucceeded false Name CNI Version v1.0.11 ErrorMessage Store is locked vnet []
				Context AzureCNI SubContext "
2018/08/15 21:11:45 OrchestratorDetails &{  kubectl command failed due to exit status 1}
2018/08/15 21:11:45 OSDetails &{windows    }
2018/08/15 21:11:45 SystemDetails &{0 0 0 0 0 0 }
2018/08/15 21:11:45 InterfaceDetails &{Primary <IP_ADDRESS>/12 <IP_ADDRESS> 00:0d:3a:f9:3a:fe vEthernet (Ethernet 2) 30 0 }
2018/08/15 21:11:45 BridgeDetails <nil>
2018/08/15 21:11:45 Send telemetry success 200
2018/08/15 21:11:45 Going to send Telemetry report to hostnetagent http://<IP_ADDRESS>/machine/plugins?comp=netagent&type=cnireport
2018/08/15 21:11:45 "Start Flag false CniSucceeded false Name CNI Version v1.0.11 ErrorMessage Store is locked vnet []
				Context AzureCNI SubContext "
2018/08/15 21:11:45 OrchestratorDetails &{  kubectl command failed due to exit status 1}
2018/08/15 21:11:45 OSDetails &{windows    }
2018/08/15 21:11:45 SystemDetails &{0 0 0 0 0 0 }
2018/08/15 21:11:45 InterfaceDetails &{Primary <IP_ADDRESS>/12 <IP_ADDRESS> 00:0d:3a:f9:3a:fe vEthernet (Ethernet 2) 30 0 }
2018/08/15 21:11:45 BridgeDetails <nil>
2018/08/15 21:11:45 Send telemetry success 200
2018/08/15 21:11:45 Going to send Telemetry report to hostnetagent http://<IP_ADDRESS>/machine/plugins?comp=netagent&type=cnireport
2018/08/15 21:11:45 "Start Flag false CniSucceeded false Name CNI Version v1.0.11 ErrorMessage Store is locked vnet []
				Context AzureCNI SubContext "
2018/08/15 21:11:45 OrchestratorDetails &{  kubectl command failed due to exit status 1}
2018/08/15 21:11:45 OSDetails &{windows    }
2018/08/15 21:11:45 SystemDetails &{0 0 0 0 0 0 }
2018/08/15 21:11:45 InterfaceDetails &{Primary <IP_ADDRESS>/12 <IP_ADDRESS> 00:0d:3a:f9:3a:fe vEthernet (Ethernet 2) 30 0 }
2018/08/15 21:11:45 BridgeDetails <nil>
2018/08/15 21:11:45 Send telemetry success 200
2018/08/15 21:11:45 Going to send Telemetry report to hostnetagent http://<IP_ADDRESS>/machine/plugins?comp=netagent&type=cnireport
2018/08/15 21:11:45 "Start Flag false CniSucceeded true Name CNI Version v1.0.11 ErrorMessage  vnet []
				Context AzureCNI SubContext "
2018/08/15 21:11:45 OrchestratorDetails &{  kubectl command failed due to exit status 1}
2018/08/15 21:11:45 OSDetails &{windows    }
2018/08/15 21:11:45 SystemDetails &{0 0 0 0 0 0 }
2018/08/15 21:11:45 InterfaceDetails &{Primary <IP_ADDRESS>/12 <IP_ADDRESS> 00:0d:3a:f9:3a:fe vEthernet (Ethernet 2) 30 0 }
2018/08/15 21:11:45 BridgeDetails <nil>
2018/08/15 21:11:45 Send telemetry success 200
2018/08/15 21:11:45 SetReportState succeeded
2018/08/15 21:11:45 SetReportState succeeded
2018/08/15 21:11:45 SetReportState succeeded
2018/08/15 21:11:45 SetReportState succeeded
E0815 21:11:45.950994    4188 cni.go:259] Error adding network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
E0815 21:11:45.950994    4188 cni_windows.go:49] error while adding to cni network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
W0815 21:11:45.950994    4188 docker_sandbox.go:353] failed to read pod IP from plugin/docker: NetworkPlugin cni failed on the status hook for pod "iis-1803-5ffd8b84d6-46msm_default": netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
I0815 21:11:45.957988    4188 kubelet_node_status.go:491] Using Node Hostname from cloudprovider: "15453k8s9001"
E0815 21:11:45.971011    4188 cni.go:259] Error adding network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
E0815 21:11:45.971011    4188 cni_windows.go:49] error while adding to cni network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
W0815 21:11:45.971011    4188 docker_sandbox.go:353] failed to read pod IP from plugin/docker: NetworkPlugin cni failed on the status hook for pod "iis-1803-5ffd8b84d6-vdppz_default": netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
E0815 21:11:45.991997    4188 cni.go:259] Error adding network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
E0815 21:11:45.992999    4188 cni_windows.go:49] error while adding to cni network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
W0815 21:11:45.992999    4188 docker_sandbox.go:353] failed to read pod IP from plugin/docker: NetworkPlugin cni failed on the status hook for pod "iis-1803-5ffd8b84d6-sjlmm_default": netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
E0815 21:11:46.006993    4188 cni.go:259] Error adding network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
E0815 21:11:46.006993    4188 cni_windows.go:49] error while adding to cni network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
W0815 21:11:46.006993    4188 docker_sandbox.go:353] failed to read pod IP from plugin/docker: NetworkPlugin cni failed on the status hook for pod "iis-1803-5ffd8b84d6-2rz9c_default": netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2018/08/15 21:11:46 SetReportState succeeded
2018/08/15 21:11:41 [cni] Timed out on locking store, err:Store is locked.
2018/08/15 21:11:46 Failed to initialize key-value store of network plugin, err:Store is locked.
2018/08/15 21:11:46 Report plugin error
2018/08/15 21:11:41 [cni] Timed out on locking store, err:Store is locked.
2018/08/15 21:11:46 Failed to initialize key-value store of network plugin, err:Store is locked.
2018/08/15 21:11:46 Report plugin error
2018/08/15 21:11:41 [cni] Timed out on locking store, err:Store is locked.
2018/08/15 21:11:46 Failed to initialize key-value store of network plugin, err:Store is locked.
2018/08/15 21:11:46 Report plugin error
2018/08/15 21:11:41 [cni] Timed out on locking store, err:Store is locked.
2018/08/15 21:11:46 Failed to initialize key-value store of network plugin, err:Store is locked.
2018/08/15 21:11:46 Report plugin error
2018/08/15 21:11:41 [cni] Timed out on locking store, err:Store is locked.
2018/08/15 21:11:46 Failed to initialize key-value store of network plugin, err:Store is locked.
2018/08/15 21:11:46 Report plugin error
2018/08/15 21:11:46 [cni] Timed out on locking store, err:Store is locked.
2018/08/15 21:11:46 Failed to initialize key-value store of network plugin, err:Store is locked.
2018/08/15 21:11:46 Report plugin error
2018/08/15 21:11:46 [cni] Timed out on locking store, err:Store is locked.
2018/08/15 21:11:46 Failed to initialize key-value store of network plugin, err:Store is locked.
2018/08/15 21:11:46 Report plugin error

What you expected to happen:
Instead of seeing E0815 21:11:45.950994    4188 cni.go:259] Error adding network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input after CNI failed to get the lock, I would expect a valid error.
I looked at the source: https://github.com/Azure/azure-container-networking/blob/677d4717e5a9808beb57cf51cebf81a8eb04cc5b/cni/network/plugin/main.go#L92
and it has return code 1 with nothing on stderr
What I would expect is a return code >100 (vendor specific), along with this json schema on stdout:
{
  "cniVersion": "0.3.1",
  "code": <numeric-error-code>,
  "msg": <short-error-message>,
  "details": <long-error-message> (optional)
}

How to reproduce it (as minimally and precisely as possible):
Try to scale anything up on Windows. It will eventually succeed, but there will be errors in the process as multiple pods need addEndpoint called simultaneously.

Could this be related at all to https://github.com/docker/libnetwork/issues/1950 ?

Looking at the code here, I strongly suspect this is actually another instance of https://github.com/etcd-io/bbolt/pull/122, which fixes https://github.com/docker/libnetwork/issues/1950. This repo uses libnetwork, so it would make sense that the two things are related. libnetwork in turn uses libkv.
So far:

https://github.com/etcd-io/bbolt/pull/122 has been merged and available in https://github.com/etcd-io/bbolt/releases/tag/v1.3.1-etcd.8
https://github.com/docker/libkv/pull/202 has been merged to pick up the boltdb fix, and move from the unsupported boltdb/bolt repo to the maintained etcd-io/bbolt repo instead
https://github.com/docker/libnetwork/pull/2268 is currently open to pull in the updated libkv.

Once https://github.com/docker/libnetwork/pull/2268 is merged, someone needs to fix up <insert component, CNI - where is that repo - @PatrickLang any idea?> to move to the updated libnetwork to fix this.

@dineshgovindasamy @madhanrm Are there any other CNI fixes needed here to move to updated libnetwork as @jhowardmsft indicates?


electron: Module "package.json" needs an import assertion of type "json"

start electron app...

App threw an error during load
TypeError [ERR_IMPORT_ASSERTION_TYPE_MISSING]: Module "file:///home/jilotta/awrit/awrit-electron/package.json" needs an import assertion of type "json"
    at new NodeError (node:internal/errors:405:5)
    at validateAssertions (node:internal/modules/esm/assert:95:15)
    at defaultLoad (node:internal/modules/esm/load:91:3)
    at nextLoad (node:internal/modules/esm/loader:166:28)
    at ESMLoader.load (node:internal/modules/esm/loader:608:26)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:462:22)
    at new ModuleJob (node:internal/modules/esm/module_job:64:26)
    at #createModuleJob (node:internal/modules/esm/loader:485:17)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:439:34)
    at async ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:79:21)
A JavaScript error occurred in the main process
Uncaught Exception:
TypeError [ERR_IMPORT_ASSERTION_TYPE_MISSING]: Module "file:///home/jilotta/awrit/awrit-electron/package.json" needs an import assertion of type "json"
    at new NodeError (node:internal/errors:405:5)
    at validateAssertions (node:internal/modules/esm/assert:95:15)
    at defaultLoad (node:internal/modules/esm/load:91:3)
    at nextLoad (node:internal/modules/esm/loader:166:28)
    at ESMLoader.load (node:internal/modules/esm/loader:608:26)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:462:22)
    at new ModuleJob (node:internal/modules/esm/module_job:64:26)
    at #createModuleJob (node:internal/modules/esm/loader:485:17)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:439:34)
    at async ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:79:21)

The electron branch is not functional in any form at the moment, which is why it's not the main branch.

Oh, thanks. Are the deprecated package warnings going to be fixed?
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/object-schema instead
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/config-array instead

These are from upstream packages and will not be fixed.
I'm half tempted to switch to yarn so that people don't bother me with npm's nonsense like this and "security" warnings about packages which in reality have no effect since this isn't code running on a remote server exposed to the internet.
The reason why I don't want to use yarn is because it's another dependency people will require and it's not compatible with electron when packaging.


Need std of means for benchmarks with multiple runs

actually this can just be a downstream task for users at the moment


Product shows Color Code insteand Color Name

I have installed magento2-vsbridge-indexer and after that I have found one issue that product shows color code instead of color name. Same issue has happened with size also.
Magento Configuration for magento2-vsbridge:

Vue storefront:

Note: I have used this command in magento directory: composer require divante/magento2-vsbridge-indexer:2.0-alpha
and composer require divante/magento2-vsbridge-indexer-msi:0.2.0. Because I have es7 dependency.
And also please describe what does it mean alpha in composer command.
Nothing changed in Code

Please show screens from your Elasticsearch attribute entries. Maybe you have there attributes with labels - and just did not fetched it in PWA? We have to make sure about it at first


Annoying GitHub commit

VSCode Version: 1.36.1
OS Version: Linux (Ubuntu 19.04)

Steps to Reproduce:

Make your default code editor (commit editor) of git to "code".
Turn ON autosave on vscode.

Try to commit, it will autosave that file and blank commit get passed.

In my opinion, it should ignore the "COMMIT_EDITMSG" file.
Does this issue occur when all extensions are disabled?: Yes

@yogesh-aggarwal I am using this setup all the time and see no issues, even with auto save enabled. The commit should only happen when you close the editor. Could it be some mis-configuration on your end given this is the first time I hear about it?
//cc @joaomoreno

@yogesh-aggarwal I am using this setup all the time and see no issues, even with auto save enabled. The commit should only happen when you close the editor. Could it be some mis-configuration on your end given this is the first time I hear about it?
//cc @joaomoreno

Yes you are right, on windows, I also have no problems but on Ubunutu 19.04 LTS it has appeared the first time annoying. Are you on Linux (Ubuntu).


datetime - Maximum call stack size exceeded

Ionic version:  (check one with "x")
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
Current behavior:
Since I upgraded to Ionic 3.1.1 all ion-datetime in my app do not work anymore.
I can select a date one time, but as soon as I select another date I get the following error:
RangeError: Maximum call stack size exceeded
    at callWithDebugContext (http://localhost:8100/build/main.js:13377:15)
    at Object.debugHandleEvent [as handleEvent] (http://localhost:8100/build/main.js:12954:12)
    at dispatchEvent (http://localhost:8100/build/main.js:9133:21)
    at http://localhost:8100/build/main.js:10997:38
    at SafeSubscriber.schedulerFn [as _next] (http://localhost:8100/build/main.js:4193:36)
    at SafeSubscriber.__tryOrUnsub (http://localhost:8100/build/main.js:19195:16)
    at SafeSubscriber.next (http://localhost:8100/build/main.js:19144:22)
    at Subscriber._next (http://localhost:8100/build/main.js:19086:26)
    at Subscriber.next (http://localhost:8100/build/main.js:19050:18)
    at EventEmitter.Subject.next (http://localhost:8100/build/main.js:41303:25)
    at EventEmitter.emit (http://localhost:8100/build/main.js:4167:76)
    at TimeoutDebouncer.<anonymous> (http://localhost:8100/build/main.js:39357:33)
    at TimeoutDebouncer.schedule (http://localhost:8100/build/main.js:86890:18)
    at TimeoutDebouncer.debounce (http://localhost:8100/build/main.js:86882:14)
    at DateTime.BaseInput._fireIonChange (http://localhost:8100/build/main.js:39355:29)

I build my forms using Angulars reactive forms.
When ionChange fires I use patchValue to set the value in my form.
Before upgrading to Ionic 3.1.x everything worked as expected.
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Cordova CLI: 6.4.0
Ionic Framework Version: 3.1.1
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.3.4
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v7.6.0
Xcode version: Not installed

can you provide a template + code that reproduces the issue? I think the stack loop is in your code

Hello all! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!


sublime-settings file

The sublime settings file for PPCL that ships with this package does not seem to properly load in the users' environment. This affects the word endings parameter for word stops.

I've noticed the settings files won't load from the menu either. I believe this because the package name, as installed through Package Control, is actually "PPCL Language Syntax and Editor." So, line 112  in
"Main.sublime-menu":
"file": "${packages}/PPCL/ppcl.sublime-settings"
Should probably be:
"file": "${packages}/PPCL Language Syntax and Editor/ppcl.sublime-settings"

great, i'll dig into that.  i think you're probably right.


Add php 8.3 to docker because minimum php version in composer is 8.3

The minimal version of php in composer.json file is 8.3, it makes sense to change the php version in Laravel Sail from 8.2 to 8.3

Laravel Dusk introduces so much complexity to the project... it's insane. Do we really need it?

@vsergiu93 You are the Dusk master here, do you know why it fails? I've updated it to version 8 thinking it will fix failing but it now fails with a different error Failed to connect to localhost port 9515 after 0 ms: Connection refused

Hey @SerhiiCho, "Dusk master", yeah I'd wish, more like "Dusk noob" :smiley:, I'll have a look to see why it fails.

@SerhiiCho I fixed the failing tests, I opened a PR here https://github.com/SerhiiCho/rfc-vote/pull/1, you can merge those changes in your branch or close that PR and manually apply the same changes. I also tested the fix on my end by opening a PR and triggering the dusk action on my fork which successfully passed, you can see it here https://github.com/vsergiu93/rfc-vote/pull/1


Default Surface Controller

It would be great to have a default surface controller for all grid elements or specify the controller to use in the grid setup
I currently use strongly typed views using ditto and have to create a separate surface controller for each type although they inherit from a base type.

Fixed in commit 00ed7f9. A DefaultDocTypeGridEditorSurfaceControllerResolver has been added (works the same way as the umbraco DefaultRenderMvcControllerResolver) on which you can register a default DocTypeGridEditorSurfaceController to use for all requests. It will try looking for a more specific controller first, but if one isn't found, and a default is set, it will look for an appropriately named action on the default controller, and if one can't be found, defaults to "Index".
It's important to note, If you set a DefaultDocTypeGridEditorSurfaceController, then the Html helper will ALWAYS use that controller for every call to it.

Just implementing this now into my solution and seem to have a problem with the order that my IApplicationEventHandler is loaded and the doctypegrideditor is loaded.
This happens about 50% of the time,
Current has not been initialized on Our.Umbraco.DocTypeGridEditor.Web.Mvc.DefaultDocTypeGridEditorSurfaceControllerResolver. You must initialize Current before trying to read it.

That's weird, IApplicationEventHandler should always occur first. Do you get that error on the front end when you try to view the page? or is it some place else?

The problem is that there is 2 IApplicationEventHandler one for the doc type editor and one for my application where I register the resolver.
It appears to change how each one is loaded.

Ahh, ok, I get the issue now.

My hacky fix is to add this to both ApplicationStarting.
Apart from that works a treat I have it in about 15 doctypes
if(!DefaultDocTypeGridEditorSurfaceControllerResolver.HasCurrent)
{
    DefaultDocTypeGridEditorSurfaceControllerResolver.Current = new DefaultDocTypeGridEditorSurfaceControllerResolver();
}


Added two articles on React

What does this PR do?
This PR adds 2 articles about React.
Any relevant issues this PR addresses? (optional)
No. It doesn't address any issue.
#
Any background context you want to add?

@BolajiAyodeji, please checkout other opened PRs for merging. Thanks.


Readme.md updates

Clarifies distinction between dev setup and end-user setup (pointing to Releases page)
Moved features and supported devices to the top (since relevant to both end-user and dev setup).
Added point about SSL and additional requirements for the Z.
Dev Setup

Clarifies the file to edit is dnsmasq.conf

Anyhow, I've made updates based on the comments above, and I've incorporated the changes from the master branch to reflect some of the recent feature wording changes. I think this is good to merge if anyone with write access agrees.

LGTM


Get service version, e.g. Flanneld, Calico

Microk8s uses a few services, listed on https://microk8s.io/docs/configuring-services. For example, flanneld: https://github.com/flannel-io/flannel
Please let users find out the version of services used. Which version of flanneld is used? If this is already possible, please document it or let me know.
Why is this important?
If I know the version of the service, I can use the correct version of the documentation, so I can configure it properly. It also helps debug certain behaviour. I can also report issues about specific versions - improves bug reports.

Hi @ben-xD
The binaries for all services that are included with MicroK8s (etcd, flanneld, containerd, helm, etc) can be found in /snap/microk8s/current/bin. Some ways to retrieve
1. From a live MicroK8s installation
It is possible to retrieve this version by calling the binary directly with the --version flag, e.g.
$ /snap/microk8s/current/bin/containerd --version
containerd github.com/containerd/containerd v1.6.15 5b842e528e99d4d4c1686467debf2bd4b88ecd86

$ /snap/microk8s/current/opt/cni/bin/flanneld --version
v0.15.1

2. From source code
The version of each component that MicroK8s is using is defined in build-scripts/components/<component>/version.sh. For example, for flanneld this is https://github.com/ubuntu/microk8s/blob/master/scripts/components/flanneld/version.sh#L3. Note that this is latest master. For versioned releases, see the respective branch. For example, for 1.25 https://github.com/ubuntu/microk8s/blob/1.25/build-scripts/components/flanneld/version.sh#L3
3. Convenience command
There have been some discussions in the past to extend the microk8s version command with something like an --all flag which would print the versions of all included components as well. That would be mostly a convenience wrapper around the first option.
I am not too sure if that would be useful, since the possible changes and breaking backwards compatibility of its output format would invalidate any of its benefits.
Happy to get your opinion on this if 1 or 2 are not helping, and how a possible extension to the microk8s version command could make things easier.
Thanks!


Scopes aren't working

As of 0.3.2 the scopes on index tables no longer actually filter results. I've written some failing cukes and am working on it.

Wait.. yes they are :-S

Wow. That ticket scared me for a second!

Well I tried something like scope :first_three { |posts| posts.limit(3) } and that doesn't work so I was kinda worried too... which lead me to improving the cukes and realizing the scopes do work otherwise. So long story short: in the end it was a good thing :-)
Sent from my iPhone
On 2011-10-24, at 9:00 PM, Greg<EMAIL_ADDRESS>wrote:

Wow. That ticket scared me for a second!
--
Reply to this email directly or view it on GitHub:
https://github.com/gregbell/active_admin/issues/591#issuecomment-2512711


Commit cda30eb leads to a lot of false positives

Commit https://github.com/crowdsecurity/hub/commit/cda30eb1b2e5d61f2a0dfbebe2ffd379aca491ec leads to a lot false positives. It is common for web applications to probe for authentication requirements with requests like:
OPTIONS /SOGo/dav/username/
as returncode it gives a 401 which signals that authentication is required . The client then sends the same request with authentication, which succeeds with return code 200.
The old code checked explicitedly for method POST and did not trigger in this case. The new code in this commit does not check the method and results in a false positive.
Maybe you should exclude OPTIONS methods.

method     │ PROPFIND                             │
│ method     │ OPTIONS                              │
│ method     │ REPORT                               │
│ status     │ 401                                  │
│ target_uri │ /SOGo/dav/username/                    │
│ target_uri │ /SOGo/dav/                           │

| method     │ PROPFIND                             │
│ method     │ OPTIONS                              │
│ method     │ REPORT                               │
│ status     │ 401                                  │
│ target_uri │ /SOGo/dav/username/                    │
│ target_uri │ /SOGo/dav/                           │

However, from this it seems there are other types that leads to 401 such as REPORT and PROPFIND but I guess OPTIONS should be ignored.
I am thinking of reverting back to the original and filtering down to ones we are sure wont cause an issue
EG: evt.Parsed.verb in ['GET', 'POST', 'HEAD']
OR we could do the opposite and reverse ones we know can be prone to FP's
EG: evt.Parsed.verb not in ['OPTIONS', 'PROPFIND', 'REPORT']


Add optional letters on the bottom of buttons

Introduce the new showLetters field for PinCode, wich defaults to false.
Switch the old IconButton widgets with MaterialButton for ink-splash.
Make the shape of MaterialButton rounded with a bit of padding.
Add the spacer (SizedBox) and the Text for letters as List (workaround).
This could be changed to use spread-operators in the future.
At the moment spread-operators are not in stable channel.
Swap the empty IconButton on the "bottom-left" with empty Expanded.
Add the new introduced option to the example.
Resolves #7

Looks Good To Me.

There are some issues with the .gitignore file, but maybe i will look into this in a future commit.

@awazgyawali Are you reviewing the PR or do you want to merge it?

Sorry, I forgot about it. I Will update on pub tonight.


innerText

innerText

This issue was imported from Google Moderator
Moderator votes: +11
Issue added by FrankC on 2014-06-05
To vote this issue up or down, simply include +1 or -1 in your comment.

outerHTML and innerHTML are already covered: http://caniuse.com/#feat=xml-serializer
innerText doesn't seem to be currently covered.

@Fyrd Narrow this issue to just innerText per previous comment?

Done.

Now available at http://caniuse.com/#feat=innertext


Feature request: black or at least dark light within light cookies

Can you develop the option of black or at least dark light within light cookies? ... I want to make a tool for Tattoo artists, where edges need to be really black.
Not possible right now.
cf my project: https://playcanvas.com/editor/scene/968488

Sounds like you want to project a texture onto a model.
These two demos may help in that regard
https://github.com/playcanvas/playcanvas.github.io/blob/master/graphics/painter.html
https://developer.playcanvas.com/en/tutorials/character-damage-demo

Can you develop the option of black or at least dark light within light cookies? ... I want to make a tool for Tattoo artist, where edges need to be really black.
Not possible right now.

This would be also very useful to project blob shadows.

@yaustar: in case you are referring to https://playcanvas.github.io/#graphics/painter.html, it will not help. I have a model character which recieves the texture in a bad way (what is projected on the back is also projected on the front - a bit like a mirror effect, but only that the mapping is off {ps: UV unwrap is not always a walk in the park - many of my tried Blender unwrap methods does, for example, not transfer at FBX-export to PC})

the painter example paints on each of the 6 sides as well :-/

I am more interested in the damage-example, where the UV mapping seem to perfect already (there is no mirrored effect, as all seams and islands on the black/white rendertexture to the left are mapped correctly). Here I want to project a readymade texture to the model. Kind of the reverse procedure of the present 'damage' infliction. Here is my project with a naïve approach to the problem (blue tattoo put at decal-texture): https://playcanvas.com/editor/scene/1028837

BTW @yaustar: I have found a compromise solution for the mapping problem ... you don't have to pursue this (just in case ... but thx again)

Having summed up the different mehods to project an image to a character (to a total four methods), I hereby return to this issue as each of them seem to possess their own challenge. In case the developers think that it is possible to use the two most obvious ones (texture and rendertexture), they both have inherit flaws in the shape of 'seams' and 'distorted stretches' that prevails me to make fluint dynamic movement of an image across the character without a lot stretching: https://playcanv.as/b/9tQ1i4Cq/ (forked from a Leonidas tutorial)  + https://playcanv.as/b/FiSGfBFX/ (note the stretch on the back of the upper left arm). Theese dynamic stretches are (close to) never a problem when making UV-mapping for games, as the textures are static in such cases. But here the texture is dynamic, and the inherit original mapping structure (from when being developed in Blender etc.) reveals itself ... conclusion: Although not-being a natural category of physique, 'black light' as a light cookie option, would be very useful, as it can bypass mapping issues al together.

Although not-being a natural category of physique, 'black light' as a light cookie option, would be very useful, as it can bypass mapping issues al together.

Even if this is possible, you are going to have the same problem as you are not projecting onto a flat surface.

I am already ahead of that problem, as I am using a 'rolling effect' that changes the UV-tiling of the material as a function of the camera-to-bodypart position.

Decals?

A) As an option I can go back to the https://developer.playcanvas.com/en/tutorials/character-damage-demo (that includes decals) option, but so far I have seen this example as being taylor made for special game situations (and thus very relevant for most PlayCanvas developers).
B) As a parallel I made this post in the forum: https://forum.playcanvas.com/t/shooting-an-image-on-to-a-surface/15755 yesterday. From there I pursued https://playcanvas.com/project/704805/overview/paint-3d-test (also decals)
From both A) and especially B) I seem to be stuck at this line [from B)]:
this.material.setParameter("paintColor",new pc.Vec3(1.0,1.0,1.0).data);

is there a material.setParameter method/approach for 'painting' with an image?

(please note that this issue now have made me post this parallel https://github.com/playcanvas/engine/issues/2556 - it might help my/an overall goal of a more wider option pool and/or a better rendering pipeline ... all in all; so at least of of the above mentioned four approaches [texture, rendertexture, decals and light cookie] improves :-) )

I've converting this discussion to a request to implement a decal system:
https://github.com/playcanvas/engine/issues/4053


Decomm

Hello @gwenchee! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file d3ploy/demand_driven_deployment_inst.py:

Line 186:53: W291 trailing whitespace
Line 301:80: E501 line too long (90 > 79 characters)
Line 308:80: E501 line too long (97 > 79 characters)

In the file d3ploy/solver.py:

Line 202:1: E302 expected 2 blank lines, found 1
Line 206:58: W291 trailing whitespace
Line 213:1: W293 blank line contains whitespace
Line 221:46: W291 trailing whitespace
Line 228:1: E302 expected 2 blank lines, found 1
Line 230:45: W291 trailing whitespace
Line 243:1: W293 blank line contains whitespace
Line 257:13: E722 do not use bare 'except'
Line 258:77: W291 trailing whitespace
Line 259:54: W291 trailing whitespace
Line 262:29: E127 continuation line over-indented for visual indent
Line 262:80: E501 line too long (84 > 79 characters)

In the file d3ploy/supply_driven_deployment_inst.py:

Line 179:53: W291 trailing whitespace
Line 294:80: E501 line too long (97 > 79 characters)

In the file tests/integration_tests/decommission_test.py:

Line 21:78: E225 missing whitespace around operator
Line 21:80: E501 line too long (95 > 79 characters)


Installer for ActiveAdmin

Hi Corey, I saw that on the roadmap there is an item "Administrative interface for adding and editing announcements" but what I really needed right now was to allow ActiveAdmin to manage the announcements.
What do you think of a installer to config starburst's announcements to be manageable by ActiveAdmin? Would you accept the pull request if I implement it?

A very belated yes!

A very belated belated yes!


feat: update description and user stories

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Related to: https://github.com/freeCodeCamp/freeCodeCamp/issues/39721

@moT01 was adding the blocked label intentional?

Yes, I opened the PR and then noticed that hint in the boilerplate and wanted to add it here

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Need correct root type on biological phase GO terms

In order to display biological phase GO terms correctly on the Noctua form and VPE editors, we need the correct root type.
Currently, the root type is biological process but we need to add biological phase.
@balhoff @tmushayahama

@tmushayahama I've got a PR for this (#497), changes are merged to dev branch.

@vanaukenk Is there a desire to hold this for now or merge and test for next week's release?

Tested on production and working okay, but note that we'd like to do some related ontology work here:
https://github.com/OBOFoundry/COB/issues/51
https://github.com/OBOFoundry/COB/issues/40
https://github.com/geneontology/go-ontology/issues/17914#issuecomment-548120923


Webhook configuration isn't validating correctly

Issue summary
After configuring a webhook using shopify-app-express package (as it's configured by default in Shopify Nodejs template), when firing an event, the webhook cannot be validated
-->

@shopify/shopify-app-* package and version<EMAIL_ADDRESS>Node version: v18.12.1
Operating system: Ubuntu 22.04.1 LTS running on Windows 11 WSL2

[shopify-api/INFO] Processing webhook request | {apiVersion: 2023-01, domain: supernormal-dev.myshopify.com, topic: checkouts/update, webhookId:
                                 a7762489-908c-4547-85a8-b8c098bfa5a7}
2023-01-24 22:05:16 | backend  | [shopify-app/ERROR] Failed to process webhook: Error: Could not validate request for topic checkouts/update

Expected behavior
When firing an event related with the webhook configured, I should receive the payload
Actual behavior
Getting a could not validate request error
Steps to reproduce the problem

Configure an express post call for webhooks

app.post(   shopify.config.webhooks.path,   shopify.processWebhooks({ webhookHandlers: webhookHandlerIndex }) );

Configure the handler as documented by Shopify GDPR examples

`import { DeliveryMethod } from "@shopify/shopify-api";
export const webhookHandlerIndex = () => {
return ({
    CHECKOUTS_UPDATE: {
        deliveryMethod: DeliveryMethod.Http,
        callbackUrl: "/api/webhooks",
        callback: async (topic, shop, body, webhookId) => {
            const payload = JSON.parse(body);
            console.log(payload)
        }
    },
})

}
`

Hi david did you ever figure this out. I am also having trouble configuring the webhooks

@david-supernormal someone just submitted a bug issue that could be related to why you webhooks aren't validating correctly. The ngrok url might not be updating


Remove .x version IDs from examples in README

As per our conversation today, the .x OTP version references can lead to 404 errors because Erlang Solutions doesn't publish all versions.
Please see change history in elixir-git/xgit#215.

We now pull OTP and Elixir from Hex.pm, instead of Erlang Solutions (need to update README), so I believe more versions are available.


Renaming attribute to name in v4.0.0

It's my plan to rename the attribute named attribute in form fields to name in v4.
Any thoughts or objections?
@jasonlaw? @awhitford? @VOIDCRUSHER? Anyone?

I am fine with that. :)

While I'm onboard for renaming the field, I feel that "name" could get confused with "label" terminology when more than a name, this parameter is really being used as a key for the field under the form in scope. So maybe something like "fieldKey" would be more appropriate?

I get your point @VOIDCRUSHER. I, however, think that including the term key in the name is still not the best idea since Flutter has its own Keys and may still bring confusion.
You'll notice that with this library my aim was to make Flutter forms as easy as HTML forms, hence most concepts and naming is either borrowed from HTML or Angular's Reactive Forms - mostly since a good number of Flutter users have a web background.
The idea of naming it name is will actually be borrowed from HTML inputs, where there doesn't seem to be a lot of confusion between the name attribute within the <input> element and the <label> element.

Sorry, this ended up in my spam folder, but I also prefer name. 👍
(Using key could get confusing since Flutter has fleshed Key concepts already and it has nothing to do with that.)


Create VM from Azure Image Step Fails if image name is provided. Need…

Create VM from Azure Image Step Fails if image name is provided as currently shown in docs. The full image id needs to be provided.
i.e. Following command Fails
az vm create \
    --resource-group myResourceGroup \
    --name myVM \
    --image myPackerImage \
    --admin-username azureuser \
    --generate-ssh-keys

The Error message is
Invalid image "managedPackerLinux". Use a custom image name, id, or pick one from ['CentOS', 'CoreOS', 'Debian', 'openSUSE-Leap', 'RHEL', 'SLES', 'UbuntuLTS', 'Win2016Datacenter', 'Win2012R2Datacenter', 'Win2012Datacenter', 'Win2008R2SP1']

When Full Image Id is provided as shown in command command below it succeeds (subcriptiontionid, resourcegroupname and imagename need to be changed)
az vm create \
    --resource-group myResourceGroup \
    --name myVM \
    --image "/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.Compute/images/<image-name>"  \
    --admin-username azureuser \
    --generate-ssh-keys

@maniSbindra : Thanks for your contribution! The author, @iainfoulds, has been notified to review your proposed change.

Sorry you ran into issues, @maniSbindra . I've tested this multiple times throughout the life of this doc, and just tested again the Azure Cloud Shell with the Azure CLI 2.0 version 2.0.30. The doc does work as noted without the need for the full image ID.
If you provide a different resource group for the VM you create from your image, then yes, the full image ID needs to be provided. The Azure CLI 2.0 can only determine an image name within the same resource group as your destination VM. That's a little outside the scope of this doc, but in general across Azure if you're outside the scope of a resource group then the full resource ID must be provided.
For now, as the doc shows the image and VM being created within the same resource group as the Packer image, I'm going to leave the doc as-is for simplicity.
#please-close

Thanks @iainfoulds , I had tried that as well, that is  creating the vm in the same resource group. The issue was that the sample packer template has regions as East US, so the image gets created in East US region, where as my resource group was in West US. In that case also there was an error when I tried to create VM as VM region and image region were different.
Next I created a new resource group with region east US for the VM, and that when I needed to Give image ID (image name did not work).
In My Opinion It would be good if these constraints/rules can be mentioned somewhere in the document itself, as in many real world scenarios the resource group where the images are created and used are different.


Awake Update - DAISY023_04102024

Improves the following:

Consolidates different code paths for easier maintenance.
Removes the dependency on Windows Forms and creates the system tray icon and handling through native Win32 APIs (massive thank you to @BrianPeek for helping write the window creation logic and diagnosing threading issues).

Fixes the following:

When in the UI and you select 0 as hours and 0 as minutes in TIMED awake mode, the UI becomes non-responsive whenever you try to get back to timed after it rolls back to PASSIVE.

Hey @dend l, how's this going?

@Jay-o-Way - getting some changes ready in the next few days, been side-track with my full-time job 😀 Should have something for you to review next week.

@Jay-o-Way @crutkas - y'all are super patient 😀 We're in the middle of SFI right now, so time has been limited, but aiming to have the final batch of changes in the coming week (more breathing room then).

When i select "keep awake for a time interval" the UI reverts back to option 0
Even editing the json the UI flashes option 2 and reverts to option 0

When i select "keep awake for a time interval" the UI reverts back to option 0 Even editing the json the UI flashes option 2 and reverts to option 0

Yep, known issue. Working on fixing it as part of this PR.

@crutkas @niels9001 - if y'all can grab me the icons from #11996 I can put them into this PR too, because the infra for icon changes is now in place.

@crutkas looks like the CI is failing and I need to add my updated package version to an index?

@dend looking now

Thanks for looking into this, @jaimecbernardo - testing to make sure that settings work.

@dend Nice work on this PR!
Will the tray icon eventually just be integrated into the PowerToys flyout like this suggestion? https://github.com/microsoft/PowerToys/issues/11996#issuecomment-922352064
That would make the system tray a bit cleaner. Interested to hear your thoughts.
Perhaps a future issue / PR should be made for this.

@dend Nice work on this PR!
Will the tray icon eventually just be integrated into the PowerToys flyout like this suggestion? #11996 (comment)
That would make the system tray a bit cleaner with fewer icons. Interested to hear your thoughts. Perhaps a future issue / PR should be made for this.

Likely a future issue. But keep in mind that Awake will likely  always be in the tray as an app, since it works standalone from the rest of PowerToys as well.

@jaimecbernardo this should be in shape for a review now 🚀

Thanks @jaimecbernardo!
Couple of points:

Scenario - go to passive state, switch to expiration. I can verify that the expiration works. What date/time are you selecting (how far in advance from the current time)? I've just pushed some changes meant to be a safeguard, to ensure that whenever a load from settings happens that we never have to have a date in the past.
Scenario - changing Awake states changes icons. See the tray. The icons should switch between the ones that @niels9001 created in #11996. I just tested it on my box and I can see the icons switch between each other as you change the state from both PowerToys Settings view as well as through the tray menu.

On the other scenario, I am still testing, but that should not be the case.

Hi @dend , I've figured it out. I was building an installer and testing the installed version. Icons were failing (and actually tray icon was malfunctioning) because the icons were not included in the installer. I've moved them to the actual Awake assets folder as expected by the installer and pushed that commit: https://github.com/microsoft/PowerToys/pull/32378/commits/63771d2e1f2fc0d0b4932f3285b15243d42cd9e1
Regarding the icons themselves, I see that normal.ico and scheduled.ico are not used in the code. So they're not doing anything there or are they added in expectation of future features?
Other than that, Awake seems to be working well for me now. Will do another code review.

Added a commit to remove unneeded entries from spellcheck expect that were just two words joined together for names added by the PR.

Hi @dend , I've figured it out. I was building an installer and testing the installed version. Icons were failing (and actually tray icon was malfunctioning) because the icons were not included in the installer. I've moved them to the actual Awake assets folder as expected by the installer and pushed that commit: 63771d2
Regarding the icons themselves, I see that normal.ico and scheduled.ico are not used in the code. So they're not doing anything there or are they added in expectation of future features?
Other than that, Awake seems to be working well for me now. Will do another code review.

Thanks @jaimecbernardo - really appreciate it! Yes, I plan on adding some additional functionality to Awake in the next release (scheduled Awake) that will need those icons.

Hey @dend
Love the new dynamic icon and the work to decoupling the system tray from WinForms! 😃
I gave it a try and found some regressions:

PowerToys.Awake.exe crashes when started stand-alone: seems that the tray icon initialization is missing 🤔
Keep screen on is disabled when switching using the tray icon from Off to Indefinitely
Pure aesthetic: this last separator should be visible only when the started stand-alone

Thanks @davidegiacometti - let me take a look at this later today and have a new PR with the changes.


Reading version inside code

There is a problem with getting version of package inside code. Using directly package.json works fine for node but for web it will always raise an error. This is because build version and source will have a different path to package.json.
The solution done for core works fine
https://github.com/open-telemetry/opentelemetry-js/blob/b58ad102c45dbefb0c86bc8beb8ef755a05f1a7e/packages/opentelemetry-core/scripts/version-update.js#L35
I want to implement a script that will be generating the version for each of package to have consistency across all packages.

@open-telemetry/javascript-approvers

@draffensperger ^^

I want to implement a script that will be generating the version for each of package to have consistency across all packages.

Quick question: why do you want to generate version for each package, AFAIK this is only needed for core package (which we already have)?

We don't have now one reliable way of getting the version of certain plugin. We were discussing with @dyladan last week to have something reliable that could be similar across all packages for web and node.

so basically the short answer would be one script that can be used for all packages

@mayurkale22 the reason is because you could theoretically have a different version of core than of a plugin. The version that a plugin claims to be should not depend on another package. Right now packages are version locked together, but this may not always be the case.

Makes sense, thanks for the explanation.


Add CircuitBreakerService

Sometimes, if a service is unhealthy, users might want to automatically stop receiving new incoming requests from clients
and open a circuit for the service URL. This could be useful to prevent an outage of a service from making a server unhealthy.
Because many services could share common resources such as a blocking task executor. The outage could be propagated to the server in an instant.
So if we provide a CircuitBreakerService, the CircuitBreakerService could make a server more resilient.

If a service returns a number of 5xx server errors than a threadhold,
a CircuitBreakerService opens a circuit and rejects new requests, and drops the connections.
A CircuitBreakerService MAY selectly opens a circuit for a certain remote peer such as IP address or domain name.

The IPs or domains may be abusers or trying DDOS attacks.

We could reuse a lot of code of CircuitBreaker module on the client-side.

Just a though - We may want to take advantage of this chance to see if we can make sure of resilience4j.

this chance to see if we can make use of resilience4j.

That is a nice idea.

Hi @ikhoon 👋,
If this issue is still valid. I'd like to work on this. Could you please assign it to me? Thank you.

For sure! Thanks for your attention to this.

Are we thinking about an implementation similar to ThrottlingService that also comes with a decorator?
https://armeria.dev/docs/advanced-production-checklist/
We already have circuit breakers recommended in the production checklist for clients. I think it is a great idea to add circuit breaking on server side. I really liked the idea because of the reasons you provide and based on our post-mortem.
Let's say one of our endpoints started taking too long time to process requests and everything suddenly started timing out. There can be several reasons:

An external API or DB is down.
Suddenly clients decided to send a lot more requests than usual.
Suddenly clients decided to send much much bigger requests than usual.
A buggy deployment of application causing that specific endpoint to timeout.

If things are running in event loop and let's say waiting tasks are implemented as blocking operations, ideally there should be no blocking operations but we don't want to take the whole app down just because an endpoint has buggy implementation. Circuit breaker should fail fast after that specific endpoint times out.
If there are no blocking operations in event loop, still we will spend lots of CPU cycles in high throughput, huge payload or buggy deployment scenarios. Circuit breaker should pull the rest of the endpoints into a somewhat healthy state.
If we have blockingTaskExecutor enabled, having concurrent calls is not a huge issue but the thread pool can be depleted (Not sure what is the default thread pool size) meaning other tasks to not have enough threads to operate safely. Even in this scenario, server should prevent itself by short circuiting those calls to that endpoint. This also applies to very long running operations that deplete CPU and make other endpoints slow too.
I believe we wouldn't see this behavior if we had circuit breaking service in our app too:
https://discord.com/channels/1087271586832318494/1087272728177942629/1131268159907844307
Anyway, long story short, I am interested in implementing this. I can provide a sample PR soon.
I think we should be careful about decorator orders while implementing this too. Ideally circuit breaker should be the outermost decorator so we are not having performance issues caused by other decorators, i.e. logging decorator.

We can re-use the code from exiting CircuitBreaker but it is bound to a client request context. Should we move away from the client oriented circuit breaker and use a circuit breaker that takes a request context?
It can induce some breaking changes as we move circuit breaker away from client package to common and introduce two kinds of circuit breakers such as ServerCircuitBreaker and ClientCircuitBreaker maybe using the syntax CircuitBreaker.ofClient() etc.
Please let me know if it is the right direction and we should lean towards that.

We can re-use the code from exiting CircuitBreaker but it is bound to a client request context. Should we move away from the client oriented circuit breaker and use a circuit breaker that takes a request context?

Good question. IIRC, CircuitBreaker does not depend on ClientRequestContext but some classes in circuitbreaker are bound to ClientRequestContext. We designed CircuitBreaker as a general utility so that users can use it in any situation apart from CircuitBreakerClient.

It can induce some breaking changes as we move circuit breaker away from client package to common and introduce two kinds of circuit breakers such as ServerCircuitBreaker and ClientCircuitBreaker maybe using the syntax CircuitBreaker.ofClient() etc.

We don't make breaking changes for API that is not marked as @UnstableApi. We can copy CircuitBreaker to common and make the original CircuitBreaker extends the one in common.
package com.linecorp.armeria.common.circuitbreaker;
public interface CircuitBreaker {
   ...
}

package com.linecorp.armeria.client.circuitbreaker;
@Deprecate
public interface CircuitBreaker extends com.linecorp.armeria.common.circuitbreaker.CircuitBreaker {
   @Override
   ...
}

We also need to deprecate some interfaces or classes that are also needed on the server-side.
If some of them depend on ClientRequestContext, we need to change it to RequestContext.

Good idea, I did not think about using the same name in common packege. I will get into it ASAP 🙂


Can not set from / to in calibration from SHIFT + drag

Seems the shift + define zone does not work anymore

@lpatiny
actually, it's work with me !!!!!!!!! can you test it again

@lpatiny
actually, it's work with me !!!!!!!!! can you test it again

Ok the problem was that I didn't select the right tool to draw the range.
Please when we open this dialog change automatically the tool

Ok the problem was that I didn't select the right tool to draw the range.
Please when we open this dialog change automatically the tool


The app only copies first 20 files from my android phone's DCIM folder

Description
I lost a lot of media because your app only copied first 20 files from my android phone's DCIM folder. I pressed Ctrl+a to select all of the files in the source folder and then pressed Ctrl+v in the destination folder. I thought that all of the files have been copied but it only copied first 20 files. I deleted the files in the source folder to free up the space. What would you say and do over this? 😐
Steps To Reproduce

Go to a folder with more than 100 photos and videos files. Call this folder the source folder.
Press Ctrl+a to select all of the files in the source folder.
Go to another empty folder. Call this the destination folder.
Press Ctrl+v in the destination folder
Count the number of files copied to the destination folder.

Expected behavior
All files should have been copied from source to the destination folder
Files Version
2
Windows Version
Windows 11
Relevant Assets/Logs
None

Plase update the file version and windows version using Files settings > about > copy on the top item


sap.ui.layout.Splitter: Buggy resizing using splitters inside splitters.

OpenUI5 version: 1.63.1
Browser/version (+device/version): Any
Steps to reproduce the problem:
Create below openui5 app:
var localAppID = "SPLITTERTEST";
sap.ui.getCore().attachInit(function(data) {
var oApp = new sap.m.App("oApp",{});
var oPage = new sap.m.Page("oPage",{});
var oSplitter = new sap.ui.layout.Splitter("oSplitter",{});
var oPanel4 = new sap.m.Panel("oPanel4",{});
var oTable3 = new sap.m.Table("oTable3",{});
var oPanel = new sap.m.Panel("oPanel",{});
var oTable = new sap.m.Table("oTable",{});
var oPanel1 = new sap.m.Panel("oPanel1",{});
var oSplitter1 = new sap.ui.layout.Splitter("oSplitter1",{});
var oPanel2 = new sap.m.Panel("oPanel2",{});
var oTable1 = new sap.m.Table("oTable1",{});
var oPanel3 = new sap.m.Panel("oPanel3",{});
var oTable2 = new sap.m.Table("oTable2",{});
setTimeout(function(){oApp.placeAt("body");},200);
oApp.addPage(oPage);
oPage.addContent(oSplitter);
oSplitter.addContentArea(oPanel4);
oPanel4.addContent(oTable3);
oSplitter.addContentArea(oPanel);
oPanel.addContent(oTable);
oSplitter.addContentArea(oPanel1);
oPanel1.addContent(oSplitter1);
oSplitter1.addContentArea(oPanel2);
oPanel2.addContent(oTable1);
oSplitter1.addContentArea(oPanel3);
oPanel3.addContent(oTable2);
});
What is the expected result?
All panes should resize properly.
What happens instead?

When the app loads resize pane 2 and 3.
Resize pane 1 and 2 inside pane 3, any resizing will do.
Now resize pane 2 and 3 again. Now pane 1 and 2 inside pane 3 is not resized at all, overflow just get hidden.

What is done to the state of pane 1 and 2 inside 3 to make resizing break when they are resized?
Is there any way to fix this? If not I will have to throw out openui5 and replace it with something else.

Hi,
The problem you facing is caused by the behaviour of the splitter: In initial state all the panes widths are calculated to be percentage and the responsiveness works out of the box, once you resize one of panes manually it's width become px and they stay fixed until you did another manual resize here is an example:
You have 2 panes and you want to split them by 50% ones they are created you will have:
splitPane 1 ->50% | splitPane 2 -> 50%
if you resize the window, without resizing them manually, everything is working as expected (since everything is in percentage ), but if you start resizing by dragging the splitter line you will get the following for the width:
splitPane 1 ->247px | splitPane 2 -> 192px
Once the width is calculated in pixels it remains that way and stops being responsive in a context of the browser window.
This is a problem of the sap.ui.layout.Splitter control.
The solution to your problem is using the:  sap.ui.layout.ResponsiveSplitter which can manage this behaviour correctly.
Regards,
Stefan

Since there is no response from the author for more than 4 weeks I'm closing the ticket.


Canary can't route the traffic to new version with ingess-nginx

Hi,experts, I want to consult a question。When I use flagger and ingress-nginx to do AB Test, I found that it can't to route traffic to new version.
I try to deploy podinfo on my computer according to the document （https://docs.flagger.app/tutorials/nginx-progressive-delivery） and then do the AB Test。
Below is my deployment result：

My svc:
➜  ~ k get svc -n test
NAME              TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
podinfo           ClusterIP   <IP_ADDRESS>   <none>        80/TCP    14m
podinfo-canary    ClusterIP   <IP_ADDRESS>     <none>        80/TCP    2m43s
podinfo-primary   ClusterIP   <IP_ADDRESS>   <none>        80/TCP    2m43s
➜  ~ k get svc -n test podinfo -o yaml
apiVersion: v1
kind: Service
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: '...omit'
  creationTimestamp: "2020-08-19T09:27:23Z"
  name: podinfo
  namespace: test
  resourceVersion: "612845"
  selfLink: /api/v1/namespaces/test/services/podinfo
  uid: e7be0099-7cd6-4716-bd92-7686583daaf4
spec:
  clusterIP: <IP_ADDRESS>
  ports:
  - name: http
    port: 80
    protocol: TCP
    targetPort: 9898
  selector:
    app: podinfo-primary
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

My ingress (podinfo):
➜  ~ k get ingress -n test podinfo -o yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: 'omit...'
    kubernetes.io/ingress.class: nginx
  creationTimestamp: "2020-08-19T09:28:03Z"
  generation: 1
  labels:
    app: podinfo
  name: podinfo
  namespace: test
  resourceVersion: "610967"
  selfLink: /apis/extensions/v1beta1/namespaces/test/ingresses/podinfo
  uid: c5ba7ec4-c2b2-41eb-8fe9-e465b0be8a06
spec:
  rules:
  - host: app.example.com
    http:
      paths:
      - backend:
          serviceName: podinfo
          servicePort: 80
status:
  loadBalancer:
    ingress:
    - ip: <IP_ADDRESS>

My ingress (podinfo-canary):
➜  ~ k get ingress -n test
NAME             HOSTS             ADDRESS      PORTS   AGE
podinfo          app.example.com   <IP_ADDRESS>   80      5h35m
podinfo-canary   app.example.com   <IP_ADDRESS>   80      5h23m
➜  ~ k get ingress -n test podinfo-canary -o yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/canary: "false"
  creationTimestamp: "2020-08-19T09:39:44Z"
  generation: 1
  labels:
    app: podinfo
  name: podinfo-canary
  namespace: test
  ownerReferences:
  - apiVersion: flagger.app/v1beta1
    blockOwnerDeletion: true
    controller: true
    kind: Canary
    name: podinfo
    uid: ee28a1c0-dbb6-41e2-9549-3d291085606b
  resourceVersion: "637204"
  selfLink: /apis/extensions/v1beta1/namespaces/test/ingresses/podinfo-canary
  uid: e01be494-6b5b-4287-9d6b-f9e3b0abdd9b
spec:
  rules:
  - host: app.example.com
    http:
      paths:
      - backend:
          serviceName: podinfo-canary
          servicePort: 80
status:
  loadBalancer:
    ingress:
    - ip: <IP_ADDRESS>
➜  ~

My canary:
➜  ~ k get canary -n test
NAME      STATUS        WEIGHT   LASTTRANSITIONTIME
podinfo   Initialized   0        2020-08-19T09:39:44Z
➜  ~ k get canary -n test -o yaml
apiVersion: v1
items:
- apiVersion: flagger.app/v1beta1
  kind: Canary
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: '...omit'
    creationTimestamp: "2020-08-19T09:38:40Z"
    generation: 1
    name: podinfo
    namespace: test
    resourceVersion: "612856"
    selfLink: /apis/flagger.app/v1beta1/namespaces/test/canaries/podinfo
    uid: ee28a1c0-dbb6-41e2-9549-3d291085606b
  spec:
    analysis:
      interval: 1m
      iterations: 10
      match:
      - headers:
          x-canary:
            exact: insider
      - headers:
          cookie:
            exact: canary
      threshold: 10
    ingressRef:
      apiVersion: networking.k8s.io/v1beta1
      kind: Ingress
      name: podinfo
    progressDeadlineSeconds: 60
    provider: nginx
    service:
      port: 80
      targetPort: 9898
    targetRef:
      apiVersion: apps/v1
      kind: Deployment
      name: podinfo
  status:
    canaryWeight: 0
    conditions:
    - lastTransitionTime: "2020-08-19T09:39:44Z"
      lastUpdateTime: "2020-08-19T09:39:44Z"
      message: Deployment initialization completed.
      reason: Initialized
      status: "True"
      type: Promoted
    failedChecks: 0
    iterations: 0
    lastAppliedSpec: 689f645b78
    lastTransitionTime: "2020-08-19T09:39:44Z"
    phase: Initialized
    trackedConfigs: {}
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

then, I use port-forward to access my service:

So far everything is OK.
Then I try to update the image:

Canary and Pods has changed:
Pods:

Canary:
➜  flagger k get pods -n test
NAME                               READY   STATUS    RESTARTS   AGE
podinfo-67dd999bb8-zxntg           1/1     Running   0          117s
podinfo-primary-68d7b4548c-zkszq   1/1     Running   0          9m56s
➜  flagger k describe canary -n test
Name:         podinfo
Namespace:    test
Labels:       <none>
Annotations:  'omit...'
API Version:  flagger.app/v1beta1
Kind:         Canary
Metadata:
  Creation Timestamp:  2020-08-19T09:38:40Z
  Generation:          1
  Resource Version:    614408
  Self Link:           /apis/flagger.app/v1beta1/namespaces/test/canaries/podinfo
  UID:                 ee28a1c0-dbb6-41e2-9549-3d291085606b
Spec:
  Analysis:
    Interval:    1m
    Iterations:  10
    Match:
      Headers:
        X - Canary:
          Exact:  insider
      Headers:
        Cookie:
          Exact:  canary
    Threshold:    10
  Ingress Ref:
    API Version:              networking.k8s.io/v1beta1
    Kind:                     Ingress
    Name:                     podinfo
  Progress Deadline Seconds:  60
  Provider:                   nginx
  Service:
    Port:         80
    Target Port:  9898
  Target Ref:
    API Version:  apps/v1
    Kind:         Deployment
    Name:         podinfo
Status:
  Canary Weight:  0
  Conditions:
    Last Transition Time:  2020-08-19T09:46:43Z
    Last Update Time:      2020-08-19T09:46:43Z
    Message:               New revision detected, progressing canary analysis.
    Reason:                Progressing
    Status:                Unknown
    Type:                  Promoted
  Failed Checks:           0
  Iterations:              1
  Last Applied Spec:       5b45f87898
  Last Transition Time:    2020-08-19T09:48:44Z
  Phase:                   Progressing
  Tracked Configs:
Events:
  Type     Reason  Age                  From     Message
  ----     ------  ----                 ----     -------
  Warning  Synced  10m                  flagger  podinfo-primary.test not ready: waiting for rollout to finish: observed deployment generation less then desired generation
  Normal   Synced  9m10s (x2 over 10m)  flagger  all the metrics providers are available!
  Normal   Synced  9m10s                flagger  Initialization done! podinfo.test
  Normal   Synced  2m11s                flagger  New revision detected! Scaling up podinfo.test
  Warning  Synced  71s                  flagger  canary deployment podinfo.test not ready: waiting for rollout to finish: 0 of 1 updated replicas are available
  Normal   Synced  11s                  flagger  Starting canary analysis for podinfo.test
  Normal   Synced  10s                  flagger  Advance podinfo.test canary iteration 1/10

So far, I think if i access the service at this time, the Canary can route the traffic to new version.
But I got unexpected results,no matter whether I use this Headers or not, I can only get the old version:

Then when all the Canary iterations are completed, I can get new version:

➜  ~ k describe canary/podinfo -n test
Name:         podinfo
Namespace:    test
Labels:       <none>
Annotations:  kubectl.kubernetes.io/last-applied-configuration:
                {"apiVersion":"flagger.app/v1beta1","kind":"Canary","metadata":{"annotations":{},"name":"podinfo","namespace":"test"},"spec":{"analysis":{...
API Version:  flagger.app/v1beta1
Kind:         Canary
Metadata:
  Creation Timestamp:  2020-08-19T09:38:40Z
  Generation:          1
  Resource Version:    616493
  Self Link:           /apis/flagger.app/v1beta1/namespaces/test/canaries/podinfo
  UID:                 ee28a1c0-dbb6-41e2-9549-3d291085606b
Spec:
  Analysis:
    Interval:    1m
    Iterations:  10
    Match:
      Headers:
        X - Canary:
          Exact:  insider
      Headers:
        Cookie:
          Exact:  canary
    Threshold:    10
  Ingress Ref:
    API Version:              networking.k8s.io/v1beta1
    Kind:                     Ingress
    Name:                     podinfo
  Progress Deadline Seconds:  60
  Provider:                   nginx
  Service:
    Port:         80
    Target Port:  9898
  Target Ref:
    API Version:  apps/v1
    Kind:         Deployment
    Name:         podinfo
Status:
  Canary Weight:  0
  Conditions:
    Last Transition Time:  2020-08-19T10:00:42Z
    Last Update Time:      2020-08-19T10:00:42Z
    Message:               Canary analysis completed successfully, promotion finished.
    Reason:                Succeeded
    Status:                True
    Type:                  Promoted
  Failed Checks:           0
  Iterations:              0
  Last Applied Spec:       5b45f87898
  Last Promoted Spec:      5b45f87898
  Last Transition Time:    2020-08-19T10:00:42Z
  Phase:                   Succeeded
  Tracked Configs:
Events:
  Type     Reason  Age                  From     Message
  ----     ------  ----                 ----     -------
  Warning  Synced  172m                 flagger  podinfo-primary.test not ready: waiting for rollout to finish: observed deployment generation less then desired generation
  Normal   Synced  171m (x2 over 172m)  flagger  all the metrics providers are available!
  Normal   Synced  171m                 flagger  Initialization done! podinfo.test
  Normal   Synced  164m                 flagger  New revision detected! Scaling up podinfo.test
  Warning  Synced  163m                 flagger  canary deployment podinfo.test not ready: waiting for rollout to finish: 0 of 1 updated replicas are available
  Normal   Synced  162m                 flagger  Starting canary analysis for podinfo.test
  Normal   Synced  162m                 flagger  Advance podinfo.test canary iteration 1/10
  Normal   Synced  161m                 flagger  Advance podinfo.test canary iteration 2/10
  Normal   Synced  160m                 flagger  Advance podinfo.test canary iteration 3/10
  Normal   Synced  159m                 flagger  Advance podinfo.test canary iteration 4/10
  Normal   Synced  158m                 flagger  Advance podinfo.test canary iteration 5/10
  Normal   Synced  150m (x8 over 157m)  flagger  (combined from similar events): Promotion completed! Scaling down podinfo.test
➜  ~ curl http://app.example.com:5566
{
  "hostname": "podinfo-primary-75bdf4b8-csfkk",
  "version": "3.1.4",
  "revision": "7b6f11780ab1ce8c7399da32ec6966215b8e43aa",
  "color": "#34577c",
  "logo": "https://raw.githubusercontent.com/stefanprodan/podinfo/gh-pages/cuddle_clap.gif",
  "message": "greetings from podinfo v3.1.4",
  "goos": "linux",
  "goarch": "amd64",
  "runtime": "go1.13.1",
  "num_goroutine": "8",
  "num_cpu": "2"
➜  ~

I basically followed the steps in the document, but I don’t understand what went wrong, so I’d like to ask the seniors.
Thank you very much~

➜  ~ k get pods -n test
NAME                               READY   STATUS    RESTARTS   AGE
podinfo-67dd999bb8-4mb7x           1/1     Running   0          6m12s
podinfo-primary-58fc977dfd-t4bk4   1/1     Running   0          66m

➜  ~ k get pods -n test podinfo-67dd999bb8-4mb7x -o yaml  | grep image
    image: stefanprodan/podinfo:3.1.4
    imagePullPolicy: IfNotPresent
    image: docker.io/stefanprodan/podinfo:3.1.4
    imageID: docker.io/stefanprodan/podinfo@sha256:870600586a527a89d8cfad68f09e4680906f9a11c3c4da0dcfa949f485e729a5

➜  ~ k get pods -n test podinfo-primary-58fc977dfd-t4bk4 -o yaml  | grep image
    image: stefanprodan/podinfo:3.1.0
    imagePullPolicy: IfNotPresent
    image: docker.io/stefanprodan/podinfo:3.1.0
    imageID: sha256:bbd8c7acec1bbc1076ff158d71e7b0af43395eab7d1ff3b7581146474069f001

➜  ~ k describe canary/podinfo -n test
Name:         podinfo
Namespace:    test
Labels:       <none>
Annotations:  kubectl.kubernetes.io/last-applied-configuration:
                {"apiVersion":"flagger.app/v1beta1","kind":"Canary","metadata":{"annotations":{},"name":"podinfo","namespace":"test"},"spec":{"analysis":{...
API Version:  flagger.app/v1beta1
Kind:         Canary
Metadata:
  Creation Timestamp:  2020-08-19T09:38:40Z
  Generation:          1
  Resource Version:    648149
  Self Link:           /apis/flagger.app/v1beta1/namespaces/test/canaries/podinfo
  UID:                 ee28a1c0-dbb6-41e2-9549-3d291085606b
Spec:
  Analysis:
    Interval:    1m
    Iterations:  10
    Match:
      Headers:
        X - Canary:
          Exact:  insider
      Headers:
        Cookie:
          Exact:  canary
    Threshold:    10
  Ingress Ref:
    API Version:              networking.k8s.io/v1beta1
    Kind:                     Ingress
    Name:                     podinfo
  Progress Deadline Seconds:  60
  Provider:                   nginx
  Service:
    Port:         80
    Target Port:  9898
  Target Ref:
    API Version:  apps/v1
    Kind:         Deployment
    Name:         podinfo
Status:
  Canary Weight:  0
  Conditions:
    Last Transition Time:  2020-08-19T15:12:17Z
    Last Update Time:      2020-08-19T15:12:17Z
    Message:               New revision detected, progressing canary analysis.
    Reason:                Progressing
    Status:                Unknown
    Type:                  Promoted
  Failed Checks:           0
  Iterations:              6
  Last Applied Spec:       5b45f87898
  Last Promoted Spec:      689f645b78
  Last Transition Time:    2020-08-19T15:18:17Z
  Phase:                   Progressing
  Tracked Configs:
Events:
  Type    Reason  Age                  From     Message
  ----    ------  ----                 ----     -------
  Normal  Synced  6m49s (x2 over 77m)  flagger  New revision detected! Scaling up podinfo.test
  Normal  Synced  5m48s (x2 over 76m)  flagger  Advance podinfo.test canary iteration 1/10
  Normal  Synced  4m49s (x2 over 75m)  flagger  Advance podinfo.test canary iteration 2/10
  Normal  Synced  3m49s (x2 over 74m)  flagger  Advance podinfo.test canary iteration 3/10
  Normal  Synced  2m49s (x2 over 73m)  flagger  Advance podinfo.test canary iteration 4/10
  Normal  Synced  109s (x2 over 72m)   flagger  Advance podinfo.test canary iteration 5/10
  Normal  Synced  49s (x2 over 71m)    flagger  Advance podinfo.test canary iteration 6/10

➜  ~ k get ingress -n test
NAME             HOSTS             ADDRESS      PORTS   AGE
podinfo          app.example.com   <IP_ADDRESS>   80      5h51m
podinfo-canary   app.example.com   <IP_ADDRESS>   80      5h39m

➜  ~ k get ingress -n test podinfo-canary -o yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/canary: "true"
    nginx.ingress.kubernetes.io/canary-by-cookie: canary
    nginx.ingress.kubernetes.io/canary-by-header: x-canary
    nginx.ingress.kubernetes.io/canary-by-header-value: insider
  creationTimestamp: "2020-08-19T09:39:44Z"
  generation: 1
  labels:
    app: podinfo
  name: podinfo-canary
  namespace: test
  ownerReferences:
  - apiVersion: flagger.app/v1beta1
    blockOwnerDeletion: true
    controller: true
    kind: Canary
    name: podinfo
    uid: ee28a1c0-dbb6-41e2-9549-3d291085606b
  resourceVersion: "647291"
  selfLink: /apis/extensions/v1beta1/namespaces/test/ingresses/podinfo-canary
  uid: e01be494-6b5b-4287-9d6b-f9e3b0abdd9b
spec:
  rules:
  - host: app.example.com
    http:
      paths:
      - backend:
          serviceName: podinfo-canary
          servicePort: 80
status:
  loadBalancer:
    ingress:
    - ip: <IP_ADDRESS>

➜  ~ curl -H "X-Canary: insider" http://app.example.com:5566
{
  "hostname": "podinfo-primary-58fc977dfd-t4bk4",
  "version": "3.1.0",
  "revision": "7b6f11780ab1ce8c7399da32ec6966215b8e43aa",
  "color": "#34577c",
  "logo": "https://raw.githubusercontent.com/stefanprodan/podinfo/gh-pages/cuddle_clap.gif",
  "message": "greetings from podinfo v3.1.0",
  "goos": "linux",
  "goarch": "amd64",
  "runtime": "go1.13.1",
  "num_goroutine": "8",
  "num_cpu": "2"
}%
 ➜  ~

I closed this issus. I found the cause of the problem.:joy::joy::joy:
I should not use this
k port-foreard service/podinfo 5566:80

this will cause traffic not to pass through the ingress-controll'Service when " curl http://xxxxxx ".
the correct approach should be:
➜  ~ k get svc -n ingress-nginx
NAME                                 TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                        AGE
ingress-nginx                        NodePort    <IP_ADDRESS>     <none>        80:32724/TCP                   7d14h
ingress-nginx-controller             NodePort    <IP_ADDRESS>   <none>        8000:30769/TCP,443:31653/TCP   8d
ingress-nginx-controller-admission   ClusterIP   <IP_ADDRESS>     <none>        443/TCP                        8d

➜  ~ k port-forward service/ingress-nginx-controller  5566:8000 -n ingress-nginx

Forwarding from <IP_ADDRESS>:5566 -> 80
Forwarding from [::1]:5566 -> 80

hhhhhhh I'm dull~
Flagger is awesome~:thumbsup::thumbsup::thumbsup:


[Bulk] Validation Alt-Text Fixes AM 5-16

This PR fixes missing/duplicate descriptions/alt-text across 4 articles.

Global effort to fix build validation errors
@Rick-Anderson
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!


sfLIU Completed Frontend

I have completed the frontend this includes:

Styling all pages and components.
Connecting the frontend to the backend.
Creating functionality for receiving and displaying the JSON data of the analyzed transcript sent from the backend.
Adding documentation to all functions and functional components.
Making full use of React.js's component capabilities. This means making anything that can be its own component a component and ensuring that each file has as little code as possible.
Making full use of TypeScript. This means giving proper types to everything instead of using type any.
Implementing React Router.
Testing.
Eliminating unecessary files.

Currently, you will notice that in the analysis section the numbers are not truncated so they just run on forever (eg. 66.66666666...). This will NOT be a frontend fix. This is expected to be fixed in Aurora's PR.
#78

Forgot to change package.json back to "WATCH..." so build failed. Corrected in most recent commit.

Hey Kai can you resolve the issue with the navbar? It seems like Node isn't compiling because of it

Hey Kai can you resolve the issue with the navbar? It seems like Node isn't compiling because of it

That wasn't the issue, I forgot to change the react run script back to work with docker. It should be fine now. There is an issue with the server now though.

Awesome yeah looks great

Hey Kai can you resolve the issue with the navbar? It seems like Node isn't compiling because of it

That wasn't the issue, I forgot to change the react run script back to work with docker. It should be fine now. There is an issue with the server now though.

Server issue was fixed. Had the proxy in package.json set to the wrong link.

Yeah the github action doesn't rely on Docker, it just runs npm run build so you can test if it builds on your local device first and then run build. For the docker issue yeah that is the solution nice

Great work, glad the issues are resolved now


[Android] Add null checks for getting a connection in AndroidChipStack

Problem

ChipDeviceController.java exposes close(), which terminates the BLE connection. AndroidChipStack doesn't account for the case where close() was called, and always assumes it can find the BLE connection.

Change overview

Add null checks for AndroidChipStack.getConnection()
Log if we can't find the connection.

Testing

Called ChipDeviceController.close() early in the flow and verified that onSend, onUnubscribe, etc. output logs but do not crash.

@bzbarsky-apple @chrisdecenzo @Damian-Nordic @hawk248 @jepenven-silabs?


Elastic.Transport.UnexpectedTransportException with Indices.GetAsync

Elastic.Clients.Elasticsearch version: 8.12.0
Elasticsearch version: 8.12.2
.NET runtime version: 8.0
Operating system version:
Description of the problem including expected versus actual behavior:
Try to use await client.Indices.GetAsync(....) and it throws
Elastic.Transport.UnexpectedTransportException : The JSON value could not be converted to System.Collections.Generic.ICollection`1[System.String]. Path: $.relations.entry | LineNumber: 0 | BytePositionInLine:
I have an index with a relation:
"mappings": {
"properties": {
.......
"parentChild": {
"type": "join",
"relations": {
"entry": "term"
}
},
.........
Expected behavior
Previously this does not throw any exception and based on the official web site, it is a valid relation still

Hi @feherbbj,
just to clarify. Are you really using Elastic.Clients.Elasticsearch 8.12.0?

Yes, i started the migration in this march from 7.x and since there are parallel issue and our caode base is large. I still on 8.12.0. If the issue is fixed in later versions, i might consider upgrading.

Thanks for the response. Yes, this looks like it is the same bug as in #7871 which meanwhile was fixed.

Thanks for the info


Failing Validation: Inheritance

There seems to be a problem with the validation of inherited values.
By adding the following two lines of code
var schema = JsonSchema4.FromType<Container>();
var errors = schema.Validate(json);

at the end of the test method When_JsonInheritanceConverter_is_used_then_inheritance_is_correctly_serialized_and_deserialized() validation will return 1 error.
{NotOneOf: #/Animal
{
  NoAdditionalPropertiesAllowed: #/Animal.Bar
  NoAdditionalPropertiesAllowed: #/Animal.SubElements
}
{
  NullExpected: #/Animal
}
}

Am I doing something wrong or is this a known issue?

Yes, this is a problem.. but because I mainly use NJsonSchema for code generation (http://nswag.org) it was not an issue...

The problem is that for validation we need oneOf inheritance (ie define the child classes): https://github.com/NJsonSchema/NJsonSchema/issues/13
... and for swagger generation we need allOf inheritance (ie define parent classes)

But oneOf inheritance is not supported by swagger (oneOf is not defined)

As there is yet no real property inheritance / overwrite support in the json schema standard I handle validation with a custom json schema structure.
For instance: I have two classes Person and Player. The Player class inherits all the properties from the Person class. Validaton should pass for instances of both classes. AddtionalProperties should be restricted.
My working json schema looks as follows:
{ 	"additionalProperties": true, 	"definitions": { 		"Person": { 			"additionalProperties": false, 			"properties": { 				"PersonProperty": { 					"type": "string" 				}, 				"Type": { 					"type": "string", 					"enum": ["Person"] 				} 			} 		}, 		"Player": { 			"additionalProperties": false, 			"properties": { 				"PersonProperty": { 					"type": "string" 				}, 				"PlayerProperty": { 					"type": "string" 				}, 				"Type": { 					"type": "string", 					"enum": ["Player"] 				} 			} 		} 	}, 	"oneOf": [{ 		"$ref": "#/definitions/Person" 	}, 	{ 		"$ref": "#/definitions/Player" 	}] }
As you can see, I have to duplicate the Person properties within the Player schema and use a enum restricted Type string property as suggested here.
Leaving out the allOf reference in the Player schema to the Person schema will somehow break the inheritance configuration, but using allOf does then only pass validation if I set addtionalProperties to true on the Person and Player schemas. Something I want to avoid.
I also tried out other allOf, oneOf configurations and relocations of the Type property without any success. Property inheritance and overwrites are not yet supported.
There might be a better approach here and I would be happy for any inputs. However, I am sure that the output provided by NJsonSchema does not yet create the json schema structure for the validations I need.

Did you also try the FlattenInheritanceHierarchy option?

For validation we need: https://github.com/NJsonSchema/NJsonSchema/issues/13


Interthr calib develop

Can one of the admins verify this patch?

Can one of the admins verify this patch?

It seems @MagdaSkurzok is not in J-PET collaboration team in github, so jenkins is not running tests.
@wkrzemien can you add @MagdaSkurzok to group so jenkins will trust this PR and run tests?

please retest this

test this please

test this please


Podman-desktop stays in "initalizing" after starting on Gnome 45 and NixOS

Bug description
When starting podman-desktop it stays on "initializing"

Operating system
Linux 6.7.7 #1-NixOS SMP PREEMPT_DYNAMIC Fri Mar  1 12:42:00 UTC 2024 x86_64 GNU/Linux
Installation Method
Other
Version
1.7.0
Steps to reproduce
run podman-desktop on a console and observe the UI
Relevant log output
APPIMAGE env is not defined, current application is not an AppImage
checkForUpdatesAndNotify called, downloadPromise is null
[68126:0310/103935.145981:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.StatusNotifierWatcher.RegisterStatusNotifierItem: object_path= /StatusNotifierWatcher: org.gnome.gjs.JSError.ValueError: appIndicator is undefined
(node:68126) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'endsWith')
    at /nix/store/pcmwm7y9lal28cw6m5lsgw7kcqrxjvs3-podman-desktop-0.12.0/share/lib/podman-desktop/resources/app.asar/packages/main/dist/index-2fc77038.cjs:37699:43
    at Array.forEach (<anonymous>)
    at ExtensionLoader.loadRuntime (/nix/store/pcmwm7y9lal28cw6m5lsgw7kcqrxjvs3-podman-desktop-0.12.0/share/lib/podman-desktop/resources/app.asar/packages/main/dist/index-2fc77038.cjs:37696:32)
    at ExtensionLoader.loadExtension (/nix/store/pcmwm7y9lal28cw6m5lsgw7kcqrxjvs3-podman-desktop-0.12.0/share/lib/podman-desktop/resources/app.asar/packages/main/dist/index-2fc77038.cjs:37507:26)
    at async Promise.all (index 0)
    at async ExtensionLoader.start (/nix/store/pcmwm7y9lal28cw6m5lsgw7kcqrxjvs3-podman-desktop-0.12.0/share/lib/podman-desktop/resources/app.asar/packages/main/dist/index-2fc77038.cjs:37442:5)
    at async PluginSystem.initExtensions (/nix/store/pcmwm7y9lal28cw6m5lsgw7kcqrxjvs3-podman-desktop-0.12.0/share/lib/podman-desktop/resources/app.asar/packages/main/dist/index-2fc77038.cjs:77929:5)
    at async /nix/store/pcmwm7y9lal28cw6m5lsgw7kcqrxjvs3-podman-desktop-0.12.0/share/lib/podman-desktop/resources/app.asar/packages/main/dist/index-2fc77038.cjs:78172:29
(Use `electron --trace-warnings ...` to show where the warning was created)
(node:68126) UnhandledPromiseRejectionWarning: 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unh
andled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
PluginSystem: received dom-ready event from the UI
Warning: vkCreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
    at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:101)
    at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:493)
    at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:379)
    at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:301)
    at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:556)

Additional context
No response

@papanito are you able to use https://github.com/containers/podman-desktop/releases/download/v1.7.1/podman-desktop-1.7.1.tar.gz ?
unpack the .tgz and run the podman-desktop binary from there ?

@benoitf sorry to not follow up. I did not follow up on this - actually was waiting that the package in nixrepo will be updated.

@papanito are you able to use https://github.com/containers/podman-desktop/releases/download/v1.7.1/podman-desktop-1.7.1.tar.gz ?
unpack the .tgz and run the podman-desktop binary from there ?

it's not possible (i mean out of the box) in nixos:
[18:49:37] [~/Apps/podman-desktop-1.13.2] ❱❱❱ ./podman-desktop
Could not start dynamically linked executable: ./podman-desktop
NixOS cannot run dynamically linked executables intended for generic
linux environments out of the box. For more information, see:
https://nix.dev/permalink/stub-ld
[18:49:39] [cost 0.012s] ./podman-desktop

@papanito How about trying with current nixpkgs version?
It had been updated to 1.13.2 since nixos-24.11.
https://github.com/NixOS/nixpkgs/pull/343648

Yep that work now as expected.


Is ora stable for production ?

Hi, authors !
Is the ora v4.1.5 stable for production ?

As stable, as I can manage: no breaking changes in major version (v4), all API changes (extensions) gets a new minor version (v4.1: ora.L) and all changes gets new patch version.
Production readiness:  we have no known bugs, but that's all.
I'm using it in production, but for a limited scope: no LOBs, no NVARCHAR2, no db restarts - see the recently closed issues.
If someone reports an issue, I'll try my best to reproduce it and fix it.

so recommend upgrade from ora.v3 to ora.v4 (go 1.8)?

Absolutely!
Jia Lu<EMAIL_ADDRESS>ezt írta (időpont: 2017. márc. 6., H
3:26):

so recommend upgrade from ora.v3 to ora.v4 (go 1.8)?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/rana/ora/issues/169#issuecomment-284287603, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAPoSoZA69_6mqPNxox_o2P-7vugH4YPks5ri27CgaJpZM4MTHph
.

@tgulacsi Is Oracle client 12.2 is mandatory ? I have 12.1 (there's no 12.2 for OSX) installed.
It compiles fine but this is the result:
[asaf@Asafs-MacBook-Pro 1]$ cat foo.go
package main

import (
	_ "gopkg.in/rana/ora.v4"
)

func main() {

}[asaf@Asafs-MacBook-Pro 1]$ go run foo.go
signal: killed

Any clue?
Thanks.

It is used in production.
I don't have a mac. strace, gdb?
Asaf Shakarzy<EMAIL_ADDRESS>ezt írta (időpont: 2017. márc.
28., K 11:50):
@tgulacsi https://github.com/tgulacsi Is Oracle client 12.2 is mandatory
? I have 12.1 (there's no 12.2 for OSX) installed.
It compiles fine but this is the result:
[asaf@Asafs-MacBook-Pro 1]$ cat foo.go
package main
import (
_ "gopkg.in/rana/ora.v4"
)
func main() {
}[asaf@Asafs-MacBook-Pro 1]$ go run foo.go
signal: killed
Any clue?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rana/ora/issues/169#issuecomment-289719870, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAPoSp0x7IeQSueXh4DsGsks6TNFdX-aks5rqNfsgaJpZM4MTHph
.

It has something to do with: https://github.com/golang/go/issues/11887
Adding -ldflags=-s works for now.
Thanks.

See https://github.com/golang/go/issues/19734


Drop Down box for Navbar on Homepage

If we could add a drop-down on the Home Page for the nav bar items including 'Connect to Shardeum', 'Claim Testnet SHM' etc., It would look more representable.

Can you share some more details on the suggestion? Do you mean to add a  drop-down nav bar with the same links?

Yes exactly, add a drop down with the same links, to make it look more organised. Like the drop-down does appear when we smaller the size of the chrome but it disappears when opened in full screen, and all the links are visible on the same line making it a bit confusing for the user.

I am not sure if I am getting your idea. Can you share a reference image/website which has similar functionality?


aio runtime activation logs --tail shows last log before running the command

Describe the bug
Same as in https://github.com/adobe/aio-cli-plugin-app/issues/385
The command should only show logs for new invocations that occur AFTER the command is run

@Himavanth could you qualify?

I think logs --tail is a little different from app run. Another probable way of looking at this is show last "few" logs and keep polling/waiting for more logs. This is how UNIX's tail -f works. It's debatable but i'm ok to go either way. Do you think there is a confusion in the current functionality?


support go-tuf v1?

There is a client wrapper for go-tuf (v2) already
One of the most widely used tuf clients is the one in cosign: it uses go-tuf v1
The goal is for cosign to use go-tuf v2 in future

The question is: would supporting both go-tuf versions in the conformance suite be useful in making that transition safer and easier?
If yes, then we should consider making a client wrapper for go-tuf v1

@haydentherapper @cpanato @bobcallaway Do you have thoughts on this?

Due to the proliferation of Cosign throughout Sigstore infra, we also have it used in sigstore/scaffolding, to set up private TUF repositories. Also note https://github.com/sigstore/cosign/issues/3548 is the issue for adopting the new Sigstore TUF client / go-tuf v2 in Cosign.
The plan is to fully adopt go-tuf v2 through the new Sigstore TUF client in the coming months. If the conformance test suite found that go-tuf v1 is not compliant, I wouldn't expect the maintainers to fix those non-compliance issues, since I'd assume they'd just point us to go-tuf v2. I'm OK excluding go-tuf v1 from the suite, from Sigstore's perspective.

Let's go with that, closing


As a user I want to use Trello as datasource for the report

Trello API is bad. It's skinny. Doesn't offer much features. Will have to create a new account to hide my current boards in case my Trello access token gets leaked!


Error pulling from docker hub

Overview
I have read many of the people with a problem similar to mine but I could not find anyone who had/have the same.
Usually when people get the errors I get when runing docker run hello-world, they say it is the proxy or you have changed network. I don't think I have a proxy, and I have a desktop so I don't like change network often even after restart my mac I still have the problem.
Errors
I think it is strange that I get different errors but I do, here they are:
docker: Error response from daemon: Get https://registry-1.docker.io/v2/library/hello-world/manifests/latest: Get https://auth.docker.io/token?account=jakobeng&scope=repository%3Alibrary%2Fhello-world%3Apull&service=registry.docker.io: dial tcp: lookup auth.docker.io on <IP_ADDRESS>:53: no such host.
docker: error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/c5/c54a2cc56cbb2f04003c1cd4507e118af7c0d340fe7e2720f70976c4b75237dc/data?Expires=1468116651&Signature=DcMG9BizyfFAXvFKBpFfoq2IV3EmRtrg5QuiZXicJzGdTSmECT-U4Hj8MqrZ5vs6VDLDJ2gtJxS6djWBEs3bsAok2L8YFcPO8y7cDgfwdcj3vLXMkxSDyBH3~YuZRcbAyHQjfUzxpoztLusYX99p4WYy2KZsT0pO7yI1Zv~Rl8U_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: dial tcp: lookup dseasb33srnrn.cloudfront.net on <IP_ADDRESS>:53: no such host.
docker: error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/c5/c54a2cc56cbb2f04003c1cd4507e118af7c0d340fe7e2720f70976c4b75237dc/data?Expires=1467738345&Signature=Eb~8-GGFBUxS6wE~GNZEOxCrCK5wBaBTkIH18TODSpgUHlpvoVx~W4UrRFAReoQ-LSVIzOZPJiXn4RTKMzKCqhLgAPGgAhU7xOuaBgnrwyccAD9pKMjm0pi879hIbHBWY~-kVNdd7XEaQiQ5ClX4ukKkY~RoXthaQs~-~kTy54k_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: dial tcp: lookup dseasb33srnrn.cloudfront.net on <IP_ADDRESS>:53: DNS message ID mismatch
docker: Tag latest not found in repository docker.io/library/hello-world.
Sometimes it works though, but more than half the time it don't.
Proxy and Dns
When I do to preference > network > Then I login > advanced > proxy and look through every proxy at the left, there is no information about any proxy. I have also talk with a friend and he sad the problem could be something with the DNS server but not what precisely. In preference > network the DNS ip is <IP_ADDRESS> but grayed out.
Versions
I use docker 1.12.0-rc3 but had the same problem with version 1.11. I use macOS (as it is called now), version 10.11.5
I glad to give more information about the problem if there is something I have forgot.
Thanks in advance

@JakobEng Since this happens also outside of Kitematic, it's more than likely something with docker itself - It seems related to:
https://github.com/docker/docker/issues/18842

It seems that docker/docker#18842 has something to do with ping, push, and more. I does not really look to be the same I think. My problem is with pulling images from docker hub.

The reason I mentioned it, was due to the similarity of DNS issue/errors.
Do you know if this is still happening?

What, it works now! Do you know what why changes? I so happy I finally can get to work with Docker. Thanks

we've made a lot of changes to the beta (now also available as stable) to handle Proxy more easily. happy to hear it also fixed your issue.


Add definition of FaaS

Added the definition of FaaS. This PR fixes #201

Also can you please also add the following to the wordlist.txt:
FaaS
transcodes


Add LLM App

Add LLM App to Readme file

@filipecalegario Could you help to merge this PR, please? Thanks!


Optional chaining for extensions -- ?::

It would be great if optional chaining was baked into the proposal:
document.querySelector("#myElement")?::let(it => {
  // it's safe to do things with the element here
  setupInteractivity(it);
});

Equivalent to:
let temp = document.querySelector("#myElement");
if (temp != null) {
    setupInteractivity(temp);
}

Yes, the proposal will be updated to include it. Especially I plan to change the syntax from :: to dot-based syntax, so it's very natural to still use ?. symbol, eg. document.querySelector("#myElement")?.do:let(it => { ... }).

Note, one consequence of including optional chaining is we must simplify the hooks semantic. In the initial proposal, we have invoke hook which can skip the method resolving step (this help some use cases like eventual send proposal), but ?. semantic is based on that. Consider eventual send proposal itself also changed in past years and seems can't fully covered by extension proposal, I'd like to drop invoke hook and keep extension methods using similar semantic with normal methods and private methods.

fwiw, obj?.do: seems like it'd conflict with condition ? obj?.do : …, parsing-wise.

Yeah, the separator also need to be reinvestigated.
Options:

obj.ext@method() obj?.ext@method()
obj.ext#method() obj?.ext#method()
obj.ext~method() obj?.ext~method()
obj.ext!method() obj?.ext!method()
obj.ext'method() obj?.ext'method()
obj.ext::method() obj?.ext::method()


python311Packages.botocore: 1.31.57 -> 1.32.7

Description of changes
Update the awscli stack:

python311Packages.botocore: 1.31.57 -> 1.32.7
python311Packages.boto3: 1.28.57 -> 1.29.7
python311Packages.s3transfer: 0.7.0 -> 0.8.0
awscli: 1.30.2 -> 1.30.7
python311Packages.moto: 4.2.6 -> 4.2.10
python311Packages.cfn-lint: 0.79.11 -> 0.83.3
python311Packages.aws-sam-translator: 1.78.0 -> 1.81.0
python311Packages.aiobotocore: 2.6.0 -> 2.7.0

Also fixes the broken build of aws-encryption-sdk-cli.
botocore =>1.32 supports urllib3 v2
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Rebased against staging (too many rebuilds)

Most of these commits may be included in major updates. https://github.com/NixOS/nixpkgs/pull/271586

Feel free to rebase onto python-updates to add what is missing right now.