Toggling Non-Canvas toggle switch off does not remove the color

Describe the bug
Toggling a non-canvas toggle switch from on to off does not fully toggle the switch, the color remains
To reproduce

Launch UITearSheet Example (non-canvas)
Toggle non-canvas switches on, then off
See switch not change color, acting like its on if the user isn't looking carefully

Expected behavior
When toggled off, the switch will not be empty with no color
Video
https://user-images.githubusercontent.com/110259320/182422454-afece86a-8474-4f3a-8cc3-464764983afe.mp4
Your setup

Device HoloLens2
Unity Version [2020.3.37f1]
Commit Version acdecca31b97720a6fcda057cc35b3815ad56a02

Target platform

HoloLens 2
Quest

ISSUE MIGRATION
Issue migrated from: https://github.com/microsoft/MixedRealityToolkit-Unity/issues/10815

Original comment by:
 Zee2

This is fixed by #10751!

Original comment by:
 Zee2

Fixed.


Add v2 class maps

More tasks were added in add v2 class maps as demostrated here: https://github.com/wasserth/TotalSegmentator/blob/390a5b7f55035b8bcc5f682c3a088f720a9a2ef5/totalsegmentator/map_to_binary.py#L108-L319
Should I try to make necessary changes on a pull-request?

v2 class maps are not ready yet (confirmed by Jakob).
I've already started to add terminology for the new segments but when it turned out that they are not available yet then I stopped. I've already added the new segmentation tasks, though.
It would be nice if you could keep an eye on the TotalSegmentator repository and when the additional segments are actually available then finish adding the new segments to the repository.

It would be nice if you could keep an eye on the TotalSegmentator repository and when the additional segments are actually available then finish adding the new segments to the repository.

I'll do

Ok, just saw the new PR #32, never mind & thanks for the great job! :-)

Transition to v2 is almost completed - see https://github.com/lassoan/SlicerTotalSegmentator/pull/38


Make RowVector::resize recursive

Modify RowVector::resize to add recursive resize for child vectors. This makes
it easier to build RowVectors for intermediate results in aggregate functions
and other places. Add a test to ensure intermediate results of an "avg" aggregate
function are correct. The bug in that function motivated this change.

I'm abandoning this change because there are multiple places in the code that call RowVector::resize without checking that child vectors are mutable. With this change these code paths throw an error: Can only resize flat vectors.
Here are some examples:

SelectiveStructColumnReader::getValues calls resize on result which may contain dictionary encoded children. It then re-assigns child vectors to new vectors.
Operator::fillOutput calls output_->resize() as long as output_.unique() is true which doesn't guarantee that children are flat.

CC: @oerling @pedroerp @laithsakka


Current npm version (v3.10.8) does not handle optional dependencies when using shrinkwrap

Issue Description

Create a new build definition
Add a single NPM step
Configure NPM step as Custom with command as "install -g polymer-cli"
Save and run the definition on a VSTS Hosted Agent

Expected result
Command should execute without any issue.
Actual result
Command fails due to an optional package related to macOS platform being installed despite it is not necessary.
Error logs
2018-02-09T15:14:08.5769237Z ==============================================================================
2018-02-09T15:14:08.5769398Z Task         : npm
2018-02-09T15:14:08.5769561Z Description  : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Package Management.
2018-02-09T15:14:08.5769738Z Version      : 1.0.10
2018-02-09T15:14:08.5769850Z Author       : Microsoft Corporation
2018-02-09T15:14:08.5769977Z Help         : [More Information](https://go.microsoft.com/fwlink/?LinkID=613746)
2018-02-09T15:14:08.5770246Z ==============================================================================
2018-02-09T15:14:09.4902747Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" --version"
2018-02-09T15:14:13.6905874Z 3.10.8
2018-02-09T15:14:16.9887815Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" config list"
2018-02-09T15:14:18.4614831Z ; cli configs
2018-02-09T15:14:18.4615481Z user-agent = "npm/3.10.8 node/v6.9.1 win32 x64"
2018-02-09T15:14:18.4615824Z
2018-02-09T15:14:18.4615998Z ; environment configs
2018-02-09T15:14:18.4616254Z cache = "C:\\NPM\\Cache"
2018-02-09T15:14:18.4616446Z prefix = "C:\\NPM\\Modules"
2018-02-09T15:14:18.4616740Z userconfig = "D:\\a\\1\\npm\\33823.npmrc"
2018-02-09T15:14:18.4616880Z
2018-02-09T15:14:18.4617419Z ; globalconfig C:\NPM\Modules\etc\npmrc
2018-02-09T15:14:18.4617642Z registry = "http://registry.npmjs.org/"
2018-02-09T15:14:18.4617782Z
2018-02-09T15:14:18.4617957Z ; builtin config undefined
2018-02-09T15:14:18.4618109Z
2018-02-09T15:14:18.4618297Z ; node bin location = C:\Program Files\nodejs\node.exe
2018-02-09T15:14:18.4618482Z ; cwd = D:\a\1\s
2018-02-09T15:14:18.4618661Z ; HOME = C:\Users\buildguest
2018-02-09T15:14:18.4618869Z ; "npm config ls -l" to show all defaults.
2018-02-09T15:14:18.4619008Z
2018-02-09T15:14:18.4621692Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" install -g polymer-cli"
2018-02-09T15:15:20.3975302Z npm ERR! Windows_NT 6.3.9600
2018-02-09T15:15:20.3975860Z C:\NPM\Modules
2018-02-09T15:15:20.3979392Z npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "polymer-cli"
2018-02-09T15:15:20.3979695Z `-- (empty)
2018-02-09T15:15:20.3981781Z npm ERR! node v6.9.1
2018-02-09T15:15:20.3981882Z
2018-02-09T15:15:20.4128290Z npm ERR! npm  v3.10.8
2018-02-09T15:15:20.4130039Z npm ERR! code EBADPLATFORM
2018-02-09T15:15:20.4130416Z
2018-02-09T15:15:20.4130791Z npm ERR! notsup Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
2018-02-09T15:15:20.4131404Z npm ERR! notsup Valid OS:    darwin
2018-02-09T15:15:20.4131825Z npm ERR! notsup Valid Arch:  any
2018-02-09T15:15:20.4132147Z npm ERR! notsup Actual OS:   win32
2018-02-09T15:15:20.4132521Z npm ERR! notsup Actual Arch: x64
2018-02-09T15:15:20.4132828Z
2018-02-09T15:15:20.4133307Z npm ERR! Please include the following file with any support request:
2018-02-09T15:15:20.4133681Z npm ERR!     D:\a\1\s\npm-debug.log
2018-02-09T15:15:20.4134059Z npm ERR! code 1

...
2018-02-09T15:15:20.7725926Z 113214 verbose stack Error: Unsupported platform for<EMAIL_ADDRESS>wanted {"name":"fsevents","version":"1.1.3","description":"Native Access to Mac OS-X FSEvents","main":"fsevents.js","dependencies":{"nan":"^2.3.0","node-pre-gyp":"^0.6.39"},"os":["darwin"],"engines":{"node":">=0.8.0"},"scripts":{"install":"node install","prepublish":"if [ $(npm -v | head -c 1) -lt 3 ]; then exit 1; fi && npm dedupe","test":"tap ./test","node-pre-gyp":"node-pre-gyp"},"binary":{"module_name":"fse","module_path":"./lib/binding/{configuration}/{node_abi}-{platform}-{arch}/","remote_path":"./v{version}/","package_name":"{module_name}-v{version}-{node_abi}-{platform}-{arch}.tar.gz","host":"https://fsevents-binaries.s3-us-west-2.amazonaws.com"},"repository":{"type":"git","url":"git+https://github.com/strongloop/fsevents.git"},"keywords":["fsevents","mac"],"author":{"name":"Philipp Dunkel","email":"pip@pipobscure.com"},"license":"MIT","bugs":{"url":"https://github.com/strongloop/fsevents/issues"},"homepage":"https://github.com/strongloop/fsevents","devDependencies":{"tap":"~0.4.8"},"readme":"# fsevents [![NPM](https://nodei.co/npm/fsevents.png)](https://nodei.co/npm/fsevents/)\n\nNative access to OS X FSEvents in [Node.js](http://nodejs.org/)\n\nThe FSEvents API in OS X allows applications to register for notifications of\nchanges to a given directory tree. It is a very fast and lightweight alternative\nto kqueue.\n\nThis is a low-level library. For a cross-compatible file watching module that\nuses fsevents, check out [Chokidar](https://www.npmjs.com/package/chokidar).\n\n* [Module Site & GitHub](https://github.com/strongloop/fsevents)\n* [NPM Page](https://npmjs.org/package/fsevents)\n\n## Installation\n\n\t$ npm install fsevents\n\n## Usage\n\n```js\nvar fsevents = require('fsevents');\nvar watcher = fsevents(__dirname);\nwatcher.on('fsevent', function(path, flags, id) { }); // RAW Event as emitted by OS-X\nwatcher.on('change', function(path, info) { }); // Common Event for all changes\nwatcher.start() // To start observation\nwatcher.stop()  // To end observation\n```\n\n### Events\n\n * *fsevent* - RAW Event as emitted by OS-X\n * *change* - Common Event for all changes\n * *created* - A File-System-Item has been created\n * *deleted* - A File-System-Item has been deleted\n * *modified* - A File-System-Item has been modified\n * *moved-out* - A File-System-Item has been moved away from this location\n * *moved-in* - A File-System-Item has been moved into this location\n\nAll events except *fsevent* take an *info* object as the second parameter of the callback. The structure of this object is:\n\n```js\n{\n  \"event\": \"<event-type>\",\n  \"id\": <eventi-id>,\n  \"path\": \"<path-that-this-is-about>\",\n  \"type\": \"<file|directory|symlink>\",\n  \"changes\": {\n    \"inode\": true, // Has the iNode Meta-Information changed\n    \"finder\": false, // Has the Finder Meta-Data changed\n    \"access\": false, // Have the access permissions changed\n    \"xattrs\": false // Have the xAttributes changed\n  },\n  \"flags\": <raw-flags>\n}\n```\n\n## MIT License\n\nCopyright (C) 2010-2014 Philipp Dunkel\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n","readmeFilename":"Readme.md","bundleDependencies":["node-pre-gyp"],"_id":"fsevents@1.1.3","_shasum":"11f82318f5fe7bb2cd22965a108e9306208216d8","_resolved":"https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz","_from":"fsevents@https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz","_inCache":true,"_requested":{"raw":"fsevents@https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz","scope":null,"escapedName":"fsevents","name":"fsevents","rawSpec":"https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz","spec":"https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz","type":"remote"},"_spec":"fsevents@https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz","_where":"C:\\NPM\\Modules\\node_modules\\polymer-cli","_args":[[{"raw":"fsevents@https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz","scope":null,"escapedName":"fsevents","name":"fsevents","rawSpec":"https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz","spec":"https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz","type":"remote"},"C:\\NPM\\Modules\\node_modules\\polymer-cli"]],"_shrinkwrap":null,"optionalDependencies":{}} (current: {"os":"win32","cpu":"x64"})
2018-02-09T15:15:20.7737947Z 113214 verbose stack     at checkPlatform (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-install-checks\index.js:45:14)
2018-02-09T15:15:20.7738253Z 113214 verbose stack     at thenWarnEngineIssues (C:\Program Files\nodejs\node_modules\npm\lib\install\validate-args.js:41:5)
2018-02-09T15:15:20.7738430Z 113214 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\iferr\index.js:13:50
2018-02-09T15:15:20.7738593Z 113214 verbose stack     at checkEngine (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-install-checks\index.js:24:10)
2018-02-09T15:15:20.7738763Z 113214 verbose stack     at module.exports.isInstallable (C:\Program Files\nodejs\node_modules\npm\lib\install\validate-args.js:38:3)
2018-02-09T15:15:20.7738939Z 113214 verbose stack     at actions.(anonymous function) (C:\Program Files\nodejs\node_modules\npm\lib\install\actions.js:52:14)
2018-02-09T15:15:20.7739094Z 113214 verbose stack     at execAction (C:\Program Files\nodejs\node_modules\npm\lib\install\actions.js:114:7)
2018-02-09T15:15:20.7739248Z 113214 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\slide\lib\async-map.js:52:35
2018-02-09T15:15:20.7739406Z 113214 verbose stack     at Array.forEach (native)
2018-02-09T15:15:20.7739542Z 113214 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\slide\lib\async-map.js:52:11
2018-02-09T15:15:20.7739670Z 113215 verbose pkgid<EMAIL_ADDRESS>2018-02-09T15:15:20.7739786Z 113216 verbose cwd D:\a\1\s
2018-02-09T15:15:20.7739892Z 113217 error Windows_NT 6.3.9600
2018-02-09T15:15:20.7740044Z 113218 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "polymer-cli"
2018-02-09T15:15:20.7740196Z 113219 error node v6.9.1
2018-02-09T15:15:20.7740298Z 113220 error npm  v3.10.8
2018-02-09T15:15:20.7740401Z 113221 error code EBADPLATFORM
2018-02-09T15:15:20.7740554Z 113222 error notsup Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
2018-02-09T15:15:20.7740690Z 113223 error notsup Valid OS:    darwin
2018-02-09T15:15:20.7740863Z 113223 error notsup Valid Arch:  any
2018-02-09T15:15:20.7740973Z 113223 error notsup Actual OS:   win32
2018-02-09T15:15:20.7741094Z 113223 error notsup Actual Arch: x64
2018-02-09T15:15:20.7741199Z 113224 verbose exit [ 1, true ]
2018-02-09T15:15:20.7741266Z
2018-02-09T15:15:20.7795203Z ##[error]Error: Npm failed with return code: 1

Remarks
The dependency generating the error (fsevents) comes from the following dependency graph
C:\Users\me>npm-remote-ls polymer-cli
└─<EMAIL_ADDRESS>   ├─ ...
   ├─<EMAIL_ADDRESS>   │  ├─ ...
   │  ├─<EMAIL_ADDRESS>   │  │  ├─ ...

The dependecy from chokidar to fsevents is well defined as optional here.
When running the same command locally on a Windows 10 box (npm/3.10.10 node/v7.3.0 win32 x64), package installation is executed property (fsevents is reported as an optional package and is skipped):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\polymer-cli\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

After narrowing down the issue, I noticed polymer-cli is using a npm shrinkwrap to manage dependencies.
There is also a known issue about npm which does not handle well optional dependencies with shrinkwrap in v3.10.8.
Issue seems to be fixed by npm v3.10.10. Is it possible to include that update on the VSTS hosted agent?

Looks like only solution is to wait on https://github.com/Microsoft/vsts-image-generation/issues/13 to complete its deployment

You can use the node installer task in the box.  Pick the node 6.x (npm 3.x latest) or node 8.x (npm 5.x latest) to pull JIT.
No need to wait.

I would also recommend moving to npm 5.x (node 8.x) and use package lock files.  shrinkwrap is being deprecated

I update my build definition default queue to use a Hosted Agent VS2017 as this one is sourced with npm 5.x (node 8.x).
Shrinkwrap is used by a dependency we need to build our project and can't get ride of it.

Great. I'm going to close this since you're unblocked. As Bryan mentioned, you can also use the Node Tool Installer task to control the exact versions of Node and npm used in a particular build, regardless of what's on the agent.


/api/1.x/cachegroups/{{ID}}/deliveryservices endpoint should have a more informative error message

trying to assign a cachegroup with no cache servers to a deliveryservice via the /api/1.x/cachegroups/{{ID}}/deliveryservices endpoint returns a 500 response with the body:
{
  "alerts": [
    {
      "text": "Internal Server Error",
      "level": "error"
    }
  ]
}

In the debug logs it explains that this is because there aren't any cache servers in the group, so it can't deliver content. However, "Internal Server Error" doesn't really tell you what went wrong.

Update: it appears to be doing string interpolation with an empty string to create the message; if you specify a CDN that actually doesn't exist in the request, you get back the message "cdn {{CDN ID}} does not exist", which means there's a null/undefined value being coalesced to an empty string at some point.

{
  "alerts": [
    {
      "text": "no edge or origin servers found on cachegroup 473",
      "level": "error"
    }
  ]
}

@ocket8888 Is this the response you were hoping for?

That's much better - though it'd be best to tell me the Cache Group's name, not it's numeric identifier.


Fastlane Does Not Recognize Gemfile Dependencies

Question Checklist

[X] Updated fastlane to the latest version
[X] I read the Contribution Guidelines
[X] I read docs.fastlane.tools
[X] I searched for existing GitHub issues

Question Subject
Fastlane does not respect the Gemfile in a project repository
Question Description
I am attempting to install cocoapods-art on our build box which is used to connect cocoa pods to Artifactory for package management. The problem is there is a need for both Ruby gems and cocoapods to be resolved using our internal Artifactory instance.
I opened an issue with them and they recommended using bundle install and the output I get is:
Using CFPropertyList 3.0.0
...
Using cocoapods-art 1.0.2
...
Using fastlane 2.119.0
Bundle complete! 2 Gemfile dependencies, 66 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
43534752mac:ios teamcity$ bundle info cocoapods-art
  * cocoapods-art (1.0.2)
	Summary: Artifactory support for CocoaPods
	Homepage: https://github.com/JFrogDev/cocoapods-art
	Path: /usr/local/lib/ruby/gems/2.4.0/gems/cocoapods-art-1.0.2

So far so good. The plugin is showing as installed. I then proceed to run bundle exec fastlane beta for our beta build lane and it should respect the Gemfile according to the Fastlane docs on this but I get:
[15:17:22]: ----------------------------------------
[15:17:22]: --- Step: Verifying fastlane version ---
[15:17:22]: ----------------------------------------
[15:17:22]: Your fastlane version 2.122.0 matches the minimum requirement of 2.64.0  ✅
[15:17:22]: ------------------------------
[15:17:22]: --- Step: default_platform ---
[15:17:22]: ------------------------------
[15:17:22]: Driving the lane 'ios beta' 🚀
[15:17:22]: -----------------------
[15:17:22]: --- Step: cocoapods ---
[15:17:22]: -----------------------
[15:17:22]: $ pod install
[15:17:23]: ▸ [!] Your Podfile requires that the plugin `cocoapods-art` be installed. Please install it and try installation again.
[15:17:23]: Exit status of command 'pod install' was 1 instead of 0.
[!] Your Podfile requires that the plugin `cocoapods-art` be installed. Please install it and try installation again.

[15:17:23]: $ pod install --repo-update
[15:17:24]: ▸ [!] Your Podfile requires that the plugin `cocoapods-art` be installed. Please install it and try installation again.
[15:17:24]: Exit status of command 'pod install --repo-update' was 1 instead of 0.
[!] Your Podfile requires that the plugin `cocoapods-art` be installed. Please install it and try installation again.

+------------------+----------+
|        Lane Context         |
+------------------+----------+
| DEFAULT_PLATFORM | ios      |
| PLATFORM_NAME    | ios      |
| LANE_NAME        | ios beta |
+------------------+----------+
[15:17:24]: [!] Your Podfile requires that the plugin `cocoapods-art` be installed. Please install it and try installation again.

+------+---------------------+-------------+
|             fastlane summary             |
+------+---------------------+-------------+
| Step | Action              | Time (in s) |
+------+---------------------+-------------+
| 1    | Verifying fastlane  | 0           |
|      | version             |             |
| 2    | default_platform    | 0           |
| 💥   | cocoapods           | 2           |
+------+---------------------+-------------+

[15:17:24]: fastlane finished with errors

Looking for related GitHub issues on fastlane/fastlane...

Found no similar issues. To create a new issue, please visit:
https://github.com/fastlane/fastlane/issues/new
Run `fastlane env` to append the fastlane environment to your issue
/Users/teamcity/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.122.0/fastlane_core/lib/fastlane_core/ui/interface.rb:153:in `shell_error!': [!] [!] Your Podfile requires that the plugin `cocoapods-art` be installed. Please install it and try installation again. (FastlaneCore::Interface::FastlaneShellError)

	from /Users/teamcity/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.122.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing'

So my questions are:

How do you get Fastlane's version of Ruby to use a custom Gem repo (Artifactory in this case)?
How do you install gems into Fastlane's custom version of Ruby?

pod install should actually be bundle exec pod install in this case for to work. cocoapods has an use_bundle_exec for this: https://docs.fastlane.tools/actions/cocoapods/#parameters

In my beta lane I added:
cocoapods(
      use_bundle_exec: true,
      try_repo_update_on_error: true
    )

and the build commands are:
bundle install
bundle exec pod install
bundle exec fastlane beta

But it still gives this error even though I see cocoapods-art in the installation list output of the bundle install command:

Your Podfile requires that the plugin cocoapods-art be installed. Please install it and try installation again.

But it still gives this error even though I see cocoapods-art in the installation list output of the bundle install command:

Your Podfile requires that the plugin cocoapods-art be installed. Please install it and try installation again.

Is the command that is executed by the cocoapods action done in the same folder as the others?

I ended up having to shim ruby and install fastlane into the shimmed version. It was kind of hacky. I wish there was an easier way to do this.

Suggestions how this could be solved on the fastlane level?


fix(handleDelegateEvent): stop propagation beyond DOM boundary

Fixed  and released ;)

What does this mean? This could potentially be a problem for others plugins. Default the DOM boundary seems to be document which hopefully will not be a problem. Why do you need to call event.stopPropagation()?

@jdanyow @EisenbergEffect any comments regarding the event.stopPropagation call? Why was it needed. It would be better if this kind of calls could be avoided but unfortunately it sometimes is needed just wondering if this could be solved differently.

The idea behind the delegated event is that the actual event handler is registered somewhere higher in the tree, such that the event bubbles up to that higher element and it is handled there. The problem is that our earlier version broke component encapsulation by always registering the handlers on the document, allowing internal events to bubble out of components. But it also didn't work with the shadow dom, which prevented events from bubbling out of the shadow root. The new implementation uses component boundaries as the location to register the actual handlers, which allows both fixes the shadow dom bug and allows our native components to function more like standard web components. Thecall to stopPropagation in this case was added to solve an IE bug. Though it does make sense that propagation should stop.
@stoffeastrom Is there a bug that this is causing for you?

Not at the moment. I was just worried since event.stopPropagation could cause troubles. For instance my gesture framework only adds event listeners on document and doing a event.stopPropagation() on any of the native DOM events (example mousedown, mousemove, mouseup) could break the event flow completely.
If it's only for internal events it makes sense. If not, then I'm still worried. As I wrote doing a event.stopPropagation() should only be used as a last resort in my opinion.

@EisenbergEffect this is affecting me horrible right now. I just tested and it breaks everything :(
<div class="page-host" mousedown.delegate="test();">
    <router-view></router-view>
  </div>

Added this and now my sortable plugin stopped working

Us there some reason you can' t use trigger?
On Aug 1, 2015 1:27 PM, "Christoffer Åström"<EMAIL_ADDRESS>wrote:

@EisenbergEffect https://github.com/EisenbergEffect this is affecting
me horrible right now. I just tested and it breaks everything :(

Added this and now my sortable plugin stopped working
—
Reply to this email directly or view it on GitHub
https://github.com/aurelia/binding/pull/142#issuecomment-126938818.

That was an example... I can't control what any user does...

Anyone using the plugin could break it by adding that

I wonder if what we should do is re-target the events. I think that's what shadow dom does. Idea would be that we stop propagation of the original event. But, then we fire a new event of the same type, but retargeted so that it looks like it came from the component's element rather than the element inside the component. @jdanyow Do you think this would allow IE to function correctly?

I'm not sure I understand what the root cause was for changing this. But reading through your previous answer makes me a bit more concerned. What you are now saying is that the event listeners are now added on the closest component level? This means if you have a custom element in a repeat and register an event on an element in that, a DOM event listener would be added for each item in the repeat. This could lead to severe performance problems.

Regarding the component encapsulation. I don't agree. This is handled by the framework and thus doesn't break the encapsulation per see from the user point of view.

Regarding the shadow DOM. What was the reason for the events not bubbling out of the shadow root?

What was the issue in IE?

@EisenbergEffect I just tested and it adds an event listener for each item in the repeat. Is this really intended?
Looked through the shadow DOM draft and indeed there are some event that are scoped

5.1 Events that are not leaked into ancestor trees

For the following events, scoped flag is initialized to true by default if the events are dispatched by the user agent:

abort
error
select
change
load
reset
resize
scroll
selectstart

Don't know if that was the issue though.
Also, I don't think we should consider all components as web components. If there is need for some special treatment for the shadow DOM it should be handled with feature detection and not affect other components.

We will get this fixed this week. I will work on it myself, top priority. I've got some ideas about it, but I first need to do some spec reading and run a few experiements in chrome. I'll report back.

This is also a breaking change for me. click.delegates in anchors don't work after this change. I think I will go back to 0.8.3, because I used .delegate() for everything since it was recommended to do so in the docs

I have a fix I believe. I hope to get it out on Monday. I will add some
notes here soon.
On Aug 2, 2015 8:59 AM, "Jeroen Vinke"<EMAIL_ADDRESS>wrote:

This is also a breaking change for me. click.delegates in anchors don't
work after this change. I think I will go back to 0.8.3, because I used
.delegate() for everything since it was recommended to do so in the docs
—
Reply to this email directly or view it on GitHub
https://github.com/aurelia/binding/pull/142#issuecomment-127022938.

The solution I have is pretty simple and involves the following:

Change the event manager so that it uses some new event properties to find the original event target even in the presence of shadowDOM. The code basically looks like this:

function findOriginalEventTarget(event){
  return event.originalTarget || (event.path && event.path[0])
    || (event.deepPath && event.deepPath[0]) || event.target || event.srcElement;
}

This code accounts for differences in browsers and differences in shadow dom spec versions. With this code, as long as it's not a closed shadow dom, we can retrieve the original event target and thus make event delgation work across shadow dom boundaries.

With the above fix in place, the adhoc domBoundary property has been removed from elements when it was previously added by the view factory.
All delegated events can be handled again by the document, thus there is no need to use the dom boundary at all in this process. As a result, the stopping of event propagation has also been removed.
The dom boundary is only created when there is a real shadow dom or a request for one, but not for components where authors did not specify this. The system does not use this itself, but just makes it available so component authors working in shadow dom can get access to the shadow root.

Merging changes to master shortly. This involves changes in binding and templating. I hope to release this today or tomorrow. Thank you all for your patience and I apologize for the issues.

This sounds great @EisenbergEffect! I think it was really good to catch this now and not later. :+1:

Release is looking good for tomorrow. Hopefully everyone on this thread will kick the tires on that and let us know if it's all working well for your scenarios.


feat: commute non-inner join for DPHyp

Proposed changes
Issue Number: close #xxx
Problem summary
commute non-inner join for DPHyp
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


[!] The plist file at path ***/Pods/FirebaseAnalytics/Frameworks/FirebaseAnalytics.xcframework/Info.plist doesn't exist.

Step 0: Are you in the right place?

For issues or feature requests related to the code in this repository
file a Github issue.

If this is a feature request please use the Feature Request template.

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general (non-iOS) Firebase discussion, use the firebase-talk
google group.
For backend issues, console issues, and other non-SDK help that does not fall under one
of the above categories, reach out to
Firebase Support.
Once you've read this section and determined that your issue is appropriate for
this repository, please delete this section.

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.5.1_
Firebase SDK version: 7.10.0_
Installation method: CocoaPods | Carthage | Zip file | Swift Package Manager (select one)
Firebase Component: _____ (Auth, Core, Database, Firestore, Messaging, Storage, etc)

[REQUIRED] Step 2: Describe the problem
I'm using M1 Macbook Pro. when I enter 'pod install', show error like this:
[!] The plist file at path ***/Pods/FirebaseAnalytics/Frameworks/FirebaseAnalytics.xcframework/Info.plist doesn't exist.
Steps to reproduce:
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.
Relevant Code:
// TODO(you): code here to reproduce the problem

Please update to a more recent version:
pod deintegrate and pod update


3.0.0-fix-reactpy

Description
Fix accidental version revert on reactpy, and update changelog to indicate new version release
Checklist:
Please update this checklist as you complete each item:

[x] Tests have been included for all bug fixes or added functionality.
[x] The changelog has been updated with any significant changes, if necessary.
[x] GitHub Issues which may be closed by this PR have been linked.

I think we might also want to remove the accidental v3.0.0a4 that was released on github.


fix(client): store challenge panes sizes

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 main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #39088

Base on Re-Flex Storage demo example
Aims to add functionality on desktop view

Steps to test

Open challenge view
Resize a pane
Either refresh window or go to next challenge

Ouput
Window should retain resize made by user

Thanks for the PR. Mind taking a look at the tests, please?

@raisedadead, a code update has been submitted and test are passing.
Any comments or suggestions are welcome.

:sparkles: :sparkles: AWESOME! LGTM. :sparkles: :sparkles:
Thanks, @victor-duarte, for this pull request and for contributing to the code-base for the first time.
We will be looking forward to more contributions in future.
Cheers and happy contributing!


Success class when adding from basket inside the exam editor

When adding questions from the basket inside an exam, there is little indication that a question has been added successfully following a click. This could be a success class for the add icon (in the same way as the basket item turns green when clicked in the search view), or some other indication of which questions in the basket are already included in the exam.

This is a good idea.
To do this:

in editor/static/js/exam/edit.js, add a computed observable usedInExam to the Question class, which returns true when a question with the same id is present in the exam's question list. (I'm not sure whether there's an explicit list of all the exam's questions at the moment - they're separated into question groups)
in editor/templates/exam/edit.html, add a css binding to the .glyphicon-plus tag, to add the class text-success when usedInExam is true. (docs about the css binding)

Hi @christianp,
I would like to work on this issue. Is there any one working on this?

@narendravardi thanks for offering. Nobody's working on this at the moment.

@christianp Thanks for letting me know. I am making a local installation of Numbas in order to make changes and test locally. Will keep you updated on the status.

Is this still in progress or is it open?

@jastee07 I don't think anyone is currently taking this on.


[VS Incentives]: Investigate whether creating gauge ref keys is necessary for group gauges

Background
Investigate whether ref keys need to be created for group gauges. It seems this was added without fully exploring/understanding whether it is necessary so it should be double checked.
Suggested Design

Confirm necessity of ref link creation at end of CreateGroupGauge

Acceptance Criteria

Issue is settled and captured in comments & tests

For speed of delivery, I propose the following:

Groups do not have a lifecycle. If Group's underlying group Gauge has finished, the Group becomes unusable
We gate Group creation by a high fee and governance

As a result, Group creation can either be achieved via high price r waiting for 5 days in voting

Similar to CL pools, we create a sub-dao that can bypass governance and the fee for ease of management of internal incentive

more context: all external incentives use non-perpetual gauges. If we want external incentivizers to support, we should allow non-perpetual.
If we go with non-perpetual and no pruning, should leave opportunity to prune in the future

Conclusions from this issues have been discussed. The outcomes are transferred into TDD and follow-up issues.
Next step: https://github.com/osmosis-labs/osmosis/issues/6434
Closing this


Add load function for measures and value sets

Yes, but only because I rebased. Let me handle that really quick.

Alright, the mac .so is updated. But the linux one will still be out of date (this is how it has been). We should probably investigate if we can cross-compile a .so file like we can a normal go project. There might be some obstacles with the .so file though.

I am, we can change this later in a different PR. It's not like I'm taking away functionality, this is just how it has been.


Drop support for 2022.1: override getActionUpdateThread in our actions

As for now, the default seems to be com.intellij.openapi.actionSystem.ActionUpdateThread#OLD_EDT:

This is deprecated, the plugins should migrate to select either BGT or EDT.
To be checked when ActionUpdateThread was added/how it affects our IDEA compatibility.

Okay, so let's leave as is for the moment, to be done as a part of #859. Marking as intellij-support

Hmm.... actually, break compatibility... in what specific sense? as in, what's gonna be the error from gradle runPluginVerifier?
I'd bet that you still can define the getActionUpdateThread (in 2022.1, it just won't be an overridden method). Or are ActionUpdateThread constants missing in 2022.1 as well? (that would be more of a problem)

Constants are missing :(

☹


SKGLView does not dispose or release memory [Xamarin Forms UWP]

Description
When using SKGlView in UWP on a page in a grid and then navigating away from that page, the SKGLView never disposes. If you create a new page with a new SKGLView they just keep building up in memory. There is no dispose method on SKGLView to release the underlying UWP native drawing objects.
Code

Expected Behavior
After the page is gone from the navigation stack and the SKGLView is disconnected from the PaintSurface event, it should release and dispose with the page.
Actual Behavior
SKGLView remains in memory and each time a new one is created, none of them dispose themselves according to VS2017 memory profiler.
Basic Information

Version with issue: 1.60.3
Last known good version:
IDE:  VS2017
Platform Target Frameworks: UWP

Android:
iOS:
Linux:
macOS:
Tizen:
tvOS:
UWP:
watchOS:
Windows Classic:

Target Devices:

Screenshots

Reproduction Link

VS bug #735693

We are also seeing this. CC @sir-deenicus

This also applies to 1.68.0.
This makes SkiaSharp an extremely large memory leak.
@mattleibow do you have any ideas?
This may block our release so if we can help please tell us where to get started.
It's a little surprising that SKGLView is not IDisposable, since a lot of other SkiaSharp objects are.

Thanks for reporting this, I am having a look at this. I'll let you know what I find, and if there are any workarounds/solutions.

There is some work exploring this in the CSharpMath repo: https://github.com/verybadcat/CSharpMath/issues/23

Thanks for that issue. I'll see if I can get back to you today.

I am having a look at this, and the sample attached to the CSharpMath issue has cycles - the renderer keeps a reference to the native view which has a reference to the renderer, and the cycle is complete.
But, this is v1.60.0, which had that issue. I am trying to see what happens with v1.60.3 and also with v1.68.0.

Although, something is happening here...
I know this is the SKCanvasView... Will try the SKGLView in a sec.
The first block is the start/baseline. Then I add a SKCanvasView, and it goes up high. I cleared the view and did a snapshot - for some reason it still had 40 items. Then, 3 seconds later, it magically cleared up again:

Yay! 🎉🎉🎉 Found the issue - I had to dig deep! Not really, just a lot of testing.
What was happening was the view was initializing ANGLE, and then releasing all the references and things - except for the final context. This left all sorts of references on the native side still hooked up inside the ANGLE library. As a result, even though the managed GC was all free, ANGLE was never told that it should let go of the views.

The new graph! I took the same sample, and upgraded to my "preview" NuGets and this is what we see:

How can I get the fix within vs2017? Is there a new preview version to
install from nuget?
On Wed, Dec 26, 2018 at 3:19 AM Matthew Leibowitz<EMAIL_ADDRESS>wrote:

Closed #705 https://github.com/mono/SkiaSharp/issues/705.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mono/SkiaSharp/issues/705#event-2044313490, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Amjxo4LwGTz2GyNTvSXZ_Wxe9C4jYcDZks5u8zEbgaJpZM4YzFz3
.

I am working on merging a few branches and then I hope to get a preview release out. Can't say for sure, but might be next week sometime.

@comfr3ak @charlesroddie @Happypig375 I have pushed out a preview release to our Early Access Program feed - let me know if this works for you: https://www.myget.org/F/skiasharp-eap/api/v3/index.json

There is a new crash with 1.68.1-preview71.
Reproduction:

Start debugging skia-leak-min (the sample in CSharpMath)
Click "GL View Mathview"
Wait for UI to respond
Click "GL View Mathview" again
Wait for debugger to break
Debugger breaks at

#if DEBUG && !DISABLE_XAML_GENERATED_BREAK_ON_UNHANDLED_EXCEPTION
UnhandledException += (sender, e) =>
{
    if (global::System.Diagnostics.Debugger.IsAttached) global::System.Diagnostics.Debugger.Break();
};
#endif

Exception message:

System.Exception: Failed to create EGL surface
   at SkiaSharp.Views.GlesInterop.GlesContext.CreateSurface(SwapChainPanel panel, Nullable`1 renderSurfaceSize, Nullable`1 resolutionScale)
   at SkiaSharp.Views.UWP.AngleSwapChainPanel.EnsureRenderSurface()
   at SkiaSharp.Views.UWP.AngleSwapChainPanel.OnSizeChanged(Object sender, SizeChangedEventArgs e)

Darn, let me have a look.

This was fixed in #1024


wsl install end correctly but wsl is not executable

Windows Build Number
Microsoft Windows [Versione 10.0.19043.1110]
WSL Version

[X] WSL 2
[X] WSL 1

Kernel Version
don't install
Distro Version
debian latest
Other Software
No response
Repro Steps
https://www.windowscentral.com/install-windows-subsystem-linux-windows-10
Expected Behavior
debian wsl working
Actual Behavior
Installing, this may take a few minutes...
Please create a default UNIX user account. The username does not need to match your Windows username.
For more information visit: https://aka.ms/wslusers
Enter new UNIX username:
Diagnostic Logs
No response

Have you input the username and password? You have to setup a default unix account during the installation. look like you didn't finish the installation.

This is the expected behaviour from the new distro! It starts and you enter your Linux username and password and then you should be good to go. :)


face_encodings method freezes program on raspberry pi

face_recognition version: Latest
Python version: 3.4.2
Operating System: Raspbian Jessie

Description
Thanks for making this - it is awesome.
The face_encodings method seems to freeze the python shell.  No error - the shell just stops printing or doing anything:
obama_image = face_recognition.load_image_file("obama_small.jpg")
print("image loaded")
obama_face_encoding = face_recognition.face_encodings(obama_image)[0]
print("image encoded")

The above code just returns:
image loaded

Any idea how to fix this?
What I Did
Paste the command(s) you ran and the output.
I just run the program with python3 facerec_on_raspberry_pi.py
If there was a crash, please include the traceback here.

Sounds like the same or similar issue as in #109, so just linking these issues.

Yea, I saw #109 but unlike that one I can't even ctrl-c out.  It just freezes.

Strange. I didn't have this issue when I lasted tested it on an RPi, so I'm not sure what is going on. How did you go about installing dlib? Did you install dlib via pip, compile it locally, or something else?

I did it exactly as described on the face_recognition raspberry pi install page install page:
mkdir -p dlib
git clone -b 'v19.4' --single-branch https://github.com/davisking/dlib.git dlib/
cd ./dlib
sudo python3 setup.py install

Thanks. Since I haven't seen this issue myself, it's hard to know what is going on.
When it happens, is the CPU pegged at 100% or idle? Does this issue still happen if you try processing a very small image (like 100x100 pixels or something) instead of a larger image?
If you are familiar with how to use strace, can you capture a trace from when this happens?

I'm using the obama_small image that comes included.  I'll try looking at trace

@ageitgey i tested obama_small image on my raspberry pi 3B , CPU is pegged at 100% ..... moreover python stuck with 80% CPU when i force stop the process 'obama_face_encoding renamed as abhi_face_encodings' had to kill it manually!!!. Here is the trace capture during process ........
output.zip

it is happening with all images whatever size of image is used.....dlib v19.7.0 with neon support is installed and working properly as i use that in other projects  ,any help is greatly appreciated 👍

i met the same problem. Do you find the solution?


crash during call-home establishment

Hi,
We are seeing crash during call-home establishment. Below is the back trace:
#0 0x00007f7df428af20 in SSL_get_rbio () from /usr/lib64/libssl.so.10
#1 0x00007f7df428af61 in SSL_get_rfd () from /usr/lib64/libssl.so.10
#2 0x00007f7df79a4da4 in nc_session_is_connected () from /usr/local/lib64/libnetconf2.so.2
#3 0x00007f7df79abe35 in nc_session_free () from /usr/local/lib64/libnetconf2.so.2
#4 0x00007f7df79c13e2 in nc_connect_libssl () from /usr/local/lib64/libnetconf2.so.2
#5 0x00007f7df79c1587 in nc_accept_callhome_tls_sock () from /usr/local/lib64/libnetconf2.so.2
#6 0x00007f7df79af2ea in nc_accept_callhome () from /usr/local/lib64/libnetconf2.so.2

Logs on netconf client:
Session 4 [ERR]: Inactive read timeout elapsed.
Session 4 [ERR]: Failed to receive a reply to <get-schema>.
libyang[0]: Loading "ietf-origin" module failed.
Session 4 [ERR]: Invalid session to send RPCs.
Session 4 [ERR]: Failed to send the <get-schema> RPC.
Session 4 [ERR]: Invalid session, discarding.
Session 4 [ERR]: Invalid session to read from.

I am using NP2SRV_VERSION 2.0.25 and sysrepo version 2.0.38. Could you please let me know if this issue is fixed or needs to be fixed?

I have not encountered it before so I cannot really tell you more. But what I have noticed immediately is the libssl.so.10 library, what OpenSSL version are you using, perhaps the new 3.0?

This issue happened only once till now. We will try to reproduce it.
Below I sending the sequence of steps and some logs which may give you some clue.
Sequence of steps before crash:

edit-config RPC sent
Timeout for receiving a reply expired
Session Deleted
New call-home request came

Logs from netconf in sequence:
Waiting for notification thread exit failed (timed out)
Timeout for receiving reply to a get-schema expired.
Inactive read timeout elapsed
Failed to receive a reply to get-schema.
libyang[0]: Loading "ietf-origin" module failed."
Invalid session to send RPCs.
Failed to send the get-schema RPC.
Invalid session, discarding.
Invalid session to read from.
After this last log it crashed.

After looking more at the issue, it seems a fairly simple one and I have attempt to fix it in the latest libnetconf2 (devel).


Come up with testing process

We need to think how to test our Ansible playbooks.
There were suggestions to go with Vagrant, but feel free to come with other ways.

Vagrant is actually nice option, it can be automated. However, guys in TLV are working on lago testing setup. I believe Gal is working on it.
What I would like to see, is automated deployment (vagrant, lago) and automated check, with checklist of what is OK and what NOT.
It will be ideal to have Gal join us and work with us on this together, since this way we do not replicate each others steps.
In first step we can do thinks together here, and organize everything in folders. Once the time comes, the project can split to deploy - test - develop.
@fabiand can you please invite Gal to this repository too? Thank You.

Relevant PR #24


Wait when Build command fails

What type of PR is this:
/kind code-refactoring
What does this PR do / why we need it:
this PR refactors the pkg/dev package to make more code generic between podman and kubernetes platforms. It changes the behaviour when the Build command fails.
Which issue(s) this PR fixes:
Fixes #6671
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:

Nothing happened after pressing p (I tried multiple times at different intervals to check). It works as expected on Podman however.
Is it just me?

It works for me on K8s cluster.
Details

$ odo dev --debug --no-watch
  __
 /  \__     Developing using the "my-nodejs-app" Devfile
 \__/  \    Namespace: default
 /  \__/    odo version: v3.9.0
 \__/

 ⚠  You are using "default" namespace, odo may not work as expected in the default namespace.
 ⚠  You may set a new namespace by running `odo create namespace <name>`, or set an existing one by running `odo set namespace <name>`

↪ Running on the cluster in Dev mode
 •  Waiting for Kubernetes resources  ...
 ⚠  Pod is Pending
 ✓  Pod is Running
 ✓  Syncing files into the container [138ms]
 ✓  Building your application in container (command: install) [1s]
 •  Executing the application (command: debug)  ...
 ✓  Waiting for the application to be ready [1s]
 -  Forwarding from <IP_ADDRESS>:20001 -> 3000

 -  Forwarding from <IP_ADDRESS>:20002 -> 5858

↪ Dev mode
 Keyboard Commands:
[Ctrl+c] - Exit and delete resources from the cluster
     [p] - Manually apply local changes to the application on the cluster
pPushing files...

 •  Waiting for Kubernetes resources  ...
 ✓  Syncing files into the container [65ms]
 ✓  Building your application in container (command: install) [789ms]
 ✗  Finished executing the application (command: debug) [35s]
 •  Executing the application (command: debug)  ...
 ✓  Waiting for the application to be ready [1s]

↪ Dev mode
 Keyboard Commands:
[Ctrl+c] - Exit and delete resources from the cluster
     [p] - Manually apply local changes to the application on the cluster

/override OpenShift-Integration-tests/OpenShift-Integration-tests
[FAILED] [169.775 seconds]
odo remove binding command tests when the component with binding is bootstrapped (bindingName=my-nodejs-app-cluster-sample-ocp) when odo dev is running when binding is removed [It] should have led odo dev to delete ServiceBinding from the cluster
/go/odo_1/tests/integration/cmd_remove_binding_test.go:71

[...]

[odo] I0502 07:47:27.510696    6779 exec.go:49] ExecuteCommand returned an an err: error while streaming command: error sending request: Post "[https://c100-e.eu-de.containers.cloud.ibm.com:31049/api/v1/namespaces/cmd-remove-binding-test71ook/pods/mynode-app-6f4678f6db-bx42v/exec?command=%2Fbin%2Fsh&command=-c&command=cat+%2Fopt%2Fodo%2F.odo_cmd_run.pid+%7C%7C+true&container=runtime&stderr=true&stdout=true":](https://c100-e.eu-de.containers.cloud.ibm.com:31049/api/v1/namespaces/cmd-remove-binding-test71ook/pods/mynode-app-6f4678f6db-bx42v/exec?command=%2Fbin%2Fsh&command=-c&command=cat+%2Fopt%2Fodo%2F.odo_cmd_run.pid+%7C%7C+true&container=runtime&stderr=true&stdout=true%22:) dial tcp: lookup c100-e.eu-de.containers.cloud.ibm.com: operation was canceled. for command '[/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true]'


Hard-coded default branch

Fails when e.g. 'main' is the default branch

With go-git there currently is no way to get the default branch: https://github.com/go-git/go-git/issues/510

What's actually wanted is not the 'default branch' but the currently checked out HEAD I think. Maybe with something like: https://github.com/emersion/matcha/compare/master...bbusse:matcha:use-current-head


Speedup Pauli network synthesis code

This PR includes several low-hanging performance improvements for pauli network synthesis.
Reasoning about PauliDag's front layer
Instead of recalculating the front layer in the DAG every time, we use a vector in_degree to store the number of unprocessed predecessors for every node in the DAG. In addition, the nodes with no unprocessed predecessors are kept in a vector front_nodes. Note that we no longer remove nodes from a DAG, instead we consider them as processed and decrease the in_degree of their successors by 1.
Unfortunately, the output of the new method is not identical to the one before, probably because the order of Pauli operators in the Pauli set passed to single_synthesis_step may be different (even after sorting by support size). Empirically, this makes the results a bit better in some cases and a bit worse in some others.
Speeding up PauliSet.commute
For some testcases a considerable time is spent is PauliSet.commute, due to its calling get_as_vec_bool and allocating/deallocating vectors. It is significantly faster to just use get_entry method. In addition, we do not need to return or reason about Pauli phases.
Benchmarking
Here are two illustrative benchmarks from benchpress:

test 35: old method: 19.4 seconds, new method: 0.3 seconds
test 66: old method: 129.1 seconds, new method 13.7 seconds
(with run arguments: metric = &Metric::COUNT, preserve_order = true, nshuffles = 0, skip_sort = false, fix_clifford = false)

Other comments
The PauliDag's function single_step_synthesis now gets the synthesized circuit as an argument, and adds new gates to it directly. I think this makes the code a bit cleaner.
One additional small fix is for the function check_circuit to correctly account for all-identity Paulis. Note that this checking function is still not quite correct, since it only checks that each Pauli is eventually transformed to a single-qubit rotation, but ignores the commutativity between Paulis.
In the future we could extend the synthesis functions to return a full circuit, consisting both of Clifford gates and Pauli operations. This would make Rustiq integration in Qiskit significantly simpler. I actually have the code for this already.
This PR is not based on #2 or #3 (so some of the changed code could introduce new clippy warnings).

Here are some preliminary benchmarking results on my laptop for the 100 benchpress Hamiltonians
rustiq_changes.xlsx


Add sound effects

...only if we find a way to complete #5, though. We'll use the same method to implement the SFX as the gradients/noise.

Hi,
I have a collection of LCARS sounds, including the voice.

Coming in 2.0.


Feature request: Set individual outputs per input flag

Currently, the outputs.tags gives a list of all the tags that were pushed. It would be useful if when, for example,  a tag-sha is true, there was an outputs.tag-sha to accompany it. This would enable later steps to use a particular tag.
The motivation for this is a building an image of an application and picking a particular tag to use for generating a PR to bump the image tag in a Helm chart values.yaml

@andy-v-h LGTM, I will focus on #30 to refactor this action and I keep this feature.

I think this solves what you are trying to do. I think the tag list follows the meta tags list order so if you put your ref tag first...
${{ fromJson(steps.dockermeta.outputs.json).tags[0]


Frontend Enhancement

Current table is showing the information but not in a uniform pattern which could be improved and will make the website look more professional.

photo we can see in the end column pm is not in the line which doesn't look good.
I would like to implement the enhancement. Please assign it to me.

Assigned

Do you want hacktoberfest label for this issues?

yes. Please you add hacktoberfest label for both of the issues

Done

Let me know if you are / will be working on this.

Sorry for delayed response, I'm working on it and soon will raise the PR as well.

No problem 👍


[Enhancement] Added two fixes description in Changelog

Se agregan dos fixes en el changelog.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@6dde0f4). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #739   +/-   ##
==========================================
  Coverage           ?   25.36%
==========================================
  Files              ?      232
  Lines              ?    17906
  Branches           ?     1530
==========================================
  Hits               ?     4542
  Misses             ?    12860
  Partials           ?      504

Continue to review full report at Codecov.

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


[Java] Implement a function to retrieve reference buffers in StringView

Describe the enhancement requested
At the moment in the StringView implementation, public ArrowBuf[] getBuffers(boolean clear) function only returns the offset, validity and value buffers. But for recreating views entirely and support related features it would be better to introduce additional function or improve the existing function to return the view buffers.
Component(s)
Java

Issue resolved by pull request 41796
https://github.com/apache/arrow/pull/41796


Add "linked from" strip below header of linked pane

To help users navigate, add a one-line strip to each linked pane indicating that the pane is linked, and some clue of what it's linked from.
At the left can be an icon representing the linked state, and to the right a short textual description of what it's linked from.
The icon can be a button to unlink the pane (implementing part of #43 in a different way).
Having some way to unlink panes will be a significant improvement.

The linked-from strip has been added, but right now only shows useful text in inspector panes linked from evaluation sub-panes.


Allow multiple withRule(s)

We added withRule in https://github.com/arcjet/arcjet-js/issues/193 to allow adding a new rule after the client is created, however it only allows a single new rule to be added.
This would be useful in our own example where we change the rate limit for logged in users. We might also want to set a different bot detection rule at the same time e.g. disallow all automated clients for logged out, but allow API clients for logged in.

withRule is allowed to be chained aj.withRule(tokenBucket()).withRule(detectBot())
I experimented with allowing multiple rules when I designed this and it makes the type inference very difficult or impossible so I think we just recommend multiple calls to withRule.

Updated the docs in https://github.com/arcjet/arcjet/pull/2345 to make this clear.


ipsec failed to start after docker restart

Rancher versions:
rancher/server or rancher/rancher: 1.6.18
rancher/agent or rancher/rancher-agent: 1.2.10
Infrastructure Stack versions:
healthcheck: 0.3.6
ipsec: 0.13.13
network-services: metadata-0.10.2, dns-0.17.3, manager-0.7.20
scheduler: 0.8.3
kubernetes (if applicable): no
Docker version: (docker version,docker info preferred)
docker version
Client:
 Version:         1.13.1
 API version:     1.26
 Package version: docker-1.13.1-63.git94f4240.el7.centos.x86_64
 Go version:      go1.9.4
 Git commit:      94f4240/1.13.1
 Built:           Fri May 18 15:44:33 2018
 OS/Arch:         linux/amd64

Server:
 Version:         1.13.1
 API version:     1.26 (minimum version 1.12)
 Package version: docker-1.13.1-63.git94f4240.el7.centos.x86_64
 Go version:      go1.9.4
 Git commit:      94f4240/1.13.1
 Built:           Fri May 18 15:44:33 2018
 OS/Arch:         linux/amd64
 Experimental:    false

docker info
Containers: 20
 Running: 20
 Paused: 0
 Stopped: 0
Images: 20
Server Version: 1.13.1
Storage Driver: overlay2
 Backing Filesystem: xfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: docker-runc runc
Default Runtime: docker-runc
Init Binary: /usr/libexec/docker/docker-init-current
containerd version:  (expected: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1)
runc version: e9c345b3f906d5dc5e8100b05ce37073a811c74a (expected: 9df8b306d01f59d3a8029be411de015b7304dd8f)
init version: 5b117de7f824f3d3825737cf09581645abbe35d4 (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
 seccomp
  WARNING: You're not using the default seccomp profile
  Profile: /etc/docker/seccomp.json
Kernel Version: 3.10.0-862.3.3.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 4
Total Memory: 15.51 GiB
Name: XXXXXXXXX
ID: VE74:KLYV:ZZIN:GYPX:X3X3:AUFG:IKET:QR6C:TKYP:P4OY:XPUU:K3MK
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://registry.XXXX.com/v1/
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false
Registries: registry.XXXXX.com (secure), docker.io (secure)

Operating system and kernel: (cat /etc/os-release, uname -r preferred)
cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

 uname -r
3.10.0-862.3.3.el7.x86_64

Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
VMWare
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA rancher, external DB
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Restart docker on a host : systemctl restart docker
Results:
The container ipsec need a long time (more than 5 minutes) before to be available.
Only logs available are :
8/6/2018 5:24:51 PMRefer to router sidekick for logs
8/6/2018 5:24:51 PMmkfifo: cannot create fifo 'f': File exists

Another side effect in my case, I have a consul cluster deployed and it is not able to start while ipsec is not ready.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Paragon clothing bug

What happened?
Paragon sparrow pants are invisible and Paragon sparrow top makes the players and NPC's body invisible.

Modlist version
1.0.6

I did not use console commands to spawn clothes, they were on a robber

not a bug, pieces were obtained via cheating


Animation panel: effect dropdown navigate with arrow left/right

Currently the animation effect dropdown allows navigation by arrow up and down which is in line with standard dropdown functionality, however because this dropdown sometimes can appear to have 2 options in one "line" (as it is a grid) we should allow navigation by left/right arrow as well.
More info here: https://github.com/google/web-stories-wp/pull/5615#issuecomment-742033724
Acceptance Criteria:

Using the left and right arrows in the animation effect dropdown allows navigation of effects like up and down arrows.

Verified in QA

This works well, closing it @samitron7 @aaecheverria @ivayloklissarov


Still active? Or alternative?

Looks like the last commit was 10 months ago. Is this project still active/maintained and recommended to be used for cleaning up unused CSS in webpack projects? Or is there an alternative that is suggested?

This one seems to be active PurgeCss

There are no contributors here. Looks better use https://github.com/FullHuman/purgecss-webpack-plugin, we can archive with repository to avoid misleading.


Depth Frequency Analysis (Object Detection)

Time estimate: 15-20 hours
Description of task:
Create a ROS node that maps depth points versus number of pixels (frequency) that a specific depth has in the current view frame - a histogram. This can be used to see if a specific depth has a 'peak' in frequency, which would indicate an object. Find a way to get the indices of the pixels in the areas of interest of the histogram to be able to see the 'peak' in an image format.

The idea is implemented in https://github.com/vortexntnu/Vortex-CV/tree/main/rcfa_detection for the red channel.


DNN 09.07.02 NL-NL LP release work

Updating the basics for a new release

Closing per @EPTamminga request as this is done in 9.7.2


Add service management

What would you like to see added?
It would be nice to extend the service management with the ability to stop/restart services, same as in fluidd for example.
Perhaps a specific message with buttons, or a button for each service.

I would like to be able to restart the host from the bot

Maybe we should add reboot command alike shutdown?


LookupViewId and QuickViewFormId Importance

Hello,
It could be a good idea to add that the optimal values LookupViewId and QuickViewFormId are necessary in order to search for the entity. Without them, you will get stuck forever (In custom Tile in Customer Journey).
https://community.dynamics.com/365/marketing/f/dynamics-365-for-marketing-forum/398182/custom-entity-in-custom-channel-tile/1077128#1077128

Thank you for the heads up! We will get that updated on the page.

Awesome, thanks!


OverviewMap

OverviewMap implementation for:

C++/Quick
QML/Quick
C++/Widgets

@JamesMBallard Apologies, I've made some implementation changes to allow for zooming the insetView to update the geoView (previously this was disabled and only panning was allowed.) This has changed the state-tracking implementation to make use of TaskWatchers instead.


Zero downtime deployments for stack updates

Is your feature request related to a problem? Please describe.
I'm always frustrated when I need to make stack updates and I have to incur downtime to the agent pool when doing so. When I deploy updates, all agents in that group are terminated and replaced. This leads to jobs failing with Exited with status -1 (agent lost). I then have to manually restart all those jobs or rely on users to do so.
Describe the solution you'd like
I would like agents to drain their workload before being terminated and replaced during a stack update.
Describe alternatives you've considered

Performing the stack update during non-peak hours.
Manually creating an adjacent stack, migrating to the stack, and then turning off the original stack

Additional context
Perhaps using AWS lifecycle hooks to put instances in a Terminating:Wait state to allow draining would be helpful.
Alternatively, I could detaching all instances from the ASG before stack update, but I then have the problem of determining when those agents are drained and can be terminated. Maybe if the buildkite-agent service could detect the detached state and then drain the workload that would be helpful

I guess this could be controlled by CloudFormation and how it applies changes to the ASG: https://github.com/buildkite/elastic-ci-stack-for-aws/blob/b2fed351f642566439dffda4c8fd4bf1ecc3b9ee/templates/aws-stack.yml#L1268
It was set like this 6 years ago which most probably there was a reason for doing it that way, but I'm not sure if it's still relevant.

I guess this could be controlled by CloudFormation and how it applies changes to the ASG:
https://github.com/buildkite/elastic-ci-stack-for-aws/blob/b2fed351f642566439dffda4c8fd4bf1ecc3b9ee/templates/aws-stack.yml#L1268
It was configured like this 6 years ago, which most probably there was a reason for doing it that way, but I'm not sure if it's still relevant. I haven't found any confirmation in this, or the agent's repo.

OK, the reason is explained here: https://github.com/buildkite/elastic-ci-stack-for-aws/issues/764#issuecomment-723736461


The file or directory to be published does not exist error

Bug Report
I don't think this is a bug, but maybe rather something odd happening in my setup. I've started noticing this regularly in my error logs:
The file or directory to be published does not exist: /home/vendor/putyourlightson/craft-sprig-core/src/resources/lib/htmx/2.0.1

I've tried running composer update in case it's out of date dependencies, but it persists. I have sprig-core 3.5.1 in my composer.lock.
ComponentsService.php also lists the correct version: public const HTMX_VERSION = '2.0.2';
I've cleared caches and so I'm confused where to look next. Any thoughts?
Plugin Version
3.5.0
Craft CMS Version
5.4.4
PHP Version
No response

If the htmx version constant says 2.0.2 but the file that cannot be found is 2.0.1 then it really must be a caching issue. I don't see any other explanation.

Thanks Ben, I'll keep digging.


running predict in python file for streamlit

I'm trying to run predict.py in a streamlit app, but it doesn't save the new image
the image is saved like this:
uploaded_file = st.file_uploader(label, type=['jpg'])
image = np.array(Image.open(uploaded_file))
cv2.imwrite(f"/content/lama/data_for_prediction/curr_image.jpg", image)
the masked saved like this:
bimask= boolean mask
plt.imsave(f"/content/lama/data_for_prediction/curr_image_mask.png", bimask, cmap='gray')
and tried to run predict, with a lot of variations of this:
os.system('python /content/lama/bin/predict.py model.path=/content/lama/big-lama indir=/content/lama/data_for_prediction outdir=/content/output dataset.img_suffix=.jpg > /dev/null')
I don't get an error from os.system, curr_image and curr_image_mask exist where they should how they should, but nothing is saved into  '/content/output'.

Hi! The issue is probably caused by the environment. Just a couple of days ago I tested the code in colab and it worked (and nothing changed since then).
If you run python /content/lama/bin/predict.py model.path=/content/lama/big-lama indir=/content/lama/data_for_prediction outdir=/content/output dataset.img_suffix=.jpg without os.system, does it work as intended in your environment? If you remove > /dev/null, what does it output?
You'd probably better refer to an existing third-party streamlit app or colab. Also, if you're using LaMa from a python app, calling it via os.system might be suboptimal.


Android 12 support

Same issue as reported here:
https://github.com/CrossGeeks/PushNotificationPlugin/issues/175
Is it possible to add Exported = false to the Service tag of  PNMessagingService?

Also having issues with this.

That PR is still not accepted and there is no new version. Is there a work around?

I found a work around. Just take the AndroidManifest.xml service deceleration you find the obj/Debug folder when you make a build and copy it manually into you AndroidManifest.xml in the project with the android:exported flag. Mine looks like this

Then when you build again you will see that the AndroidManifest.xml in the obj/Debug has the correct deceleration.

I found a work around. Just take the AndroidManifest.xml service deceleration you find the obj/Debug folder when you make a build and copy it manually into you AndroidManifest.xml in the project with the android:exported flag. Mine looks like this
Then when you build again you will see that the AndroidManifest.xml in the obj/Debug has the correct deceleration.

Thank you for your suggestion. Maybe I'm doing something wrong because the modified .XML file is always regenerated


TP2000-696 Content amendments packaging automation UI

TP2000-696 Content amendments packaging automation UI
Why
Small content amendments could be made to improve users' understanding of actions taken throughout the packaging automation journey.
What
Amends the following content:

'Add to queue' warning text
'Pausing and unpausing' dropdown detail text
'How to process an envelope' dropdown detail text
Accept or reject envelope warning text
Envelope rejection confirmation text

Codecov Report
Base: 91.86% // Head: 91.85% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (90167b4) compared to base (1e8cbfb).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #804      +/-   ##
==========================================
- Coverage   91.86%   91.85%   -0.01%
==========================================
  Files         394      394
  Lines       25723    25738      +15
  Branches     1941     1941
==========================================
+ Hits        23630    23642      +12
- Misses       1714     1716       +2
- Partials      379      380       +1

Impacted Files
Coverage Δ

publishing/forms.py
82.92% <ø> (ø)

publishing/views.py
61.81% <0.00%> (ø)

importer/taric.py
78.43% <0.00%> (-1.31%)
:arrow_down:

workbaskets/tests/test_views.py
98.58% <0.00%> (-0.29%)
:arrow_down:

measures/models.py
98.05% <0.00%> (-0.02%)
:arrow_down:

quotas/models.py
100.00% <0.00%> (ø)

quotas/tests/test_models.py
100.00% <0.00%> (ø)

common/models/utils.py
98.18% <0.00%> (+0.30%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


managed reconciler: status update has its own context

Description of your changes
The status update call should have its own context in order to be able to report error in the case where the main context's deadline is exceeded.

Fixes #98
Checklist

I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[x] Updated any relevant documentation, examples, or release notes.
[x] Updated the RBAC permissions in clusterrole.yaml to include any new types.

This is a tricky one. Currently we have one context, which I think of as the context for the entire reconcile loop. This means its deadline is for both cloud provider and Kubernetes API calls. The downside of this pattern is that a timeout at the cloud provider will prevent us from making the Kubernetes API calls necessary to let a user know we've timed out elsewhere in the system. To be honest I'm not sure we should go to the trouble of keeping a second context for this specific case, but if we do I agree with @hasheddan that it should have its own timeout.

Another option here (that is probably overkill) would be to create a separate goroutine that handles context timeouts - i.e. waits for the ctx.Done() channel to close, and does the needful if ctx.Err() is DeadlineExceeded - https://golang.org/pkg/context/#Context

Another option here (that is probably overkill) would be to create a separate goroutine that handles context timeouts.

I think this will make the code harder to read to some extent.
I agree with the need for timeout but it starts to count when the context is created, so we have to create the context right when we start the operation. How about something like this:
// The status update calls should have their own context in order to be able to
// report error in the case where the main context's deadline is exceeded.
var updateCtx = func() context.Context {
	ctx, _ := context.WithTimeout(context.Background(), managedReconcileTimeout)
	return ctx
}

// Reconcile a managed resource with an external resource.
func (r *ManagedReconciler) Reconcile(req reconcile.Request) (reconcile.Result, error) { // nolint:gocyclo
....
return reconcile.Result{RequeueAfter: r.shortWait}, errors.Wrap(r.client.Status().Update(updateCtx(), managed), errUpdateManagedStatus)

I think this will make the code harder to read to some extent.

@muvaf I appreciate the attention to this, but I also think that crossplane-runtime is a place where we can handle things elegantly even if it is less readable for someone new to the language. The vast majority of people will be consumers of crossplane-runtime who don't necessarily have to understand a detail like this that happens behind the scenes.
All of that being said, if we do not want to introduce new explicit goroutines, your solution seems straightforward to me :)

What if instead of using a completely separate context we used a child context with a slightly smaller timeout for our cloud provider calls?
I think we should have one context per "request" that our system handles, and in this context I think that means one context per reconcile loop. Currently we set one timeout for that entire loop, meaning we have a certain amount of time (a minute iirc?) to get the resource under reconciliation from the API server, then make 1-2 calls to the cloud provider, then make 1-2 calls to the Kubernetes API server to reflect any changes we made. My feeling is that this PR is probably most useful in the case where we timeout because the cloud provider did not respond quickly enough; if we're timing out because the API server is responding too slowly it's likely that our attempt to update our status (by calling the API server) will also time out.
So if we were to create a context with a timeout of ~60 seconds for the entire reconcile, but use a child context with a timeout of ~45 seconds for the cloud provider API calls, we'd hopefully have 10-15 seconds left of our parent context to update the status if/when we timeout due to the cloud provider being unresponsive.

So if we were to create a context with a timeout of ~60 seconds for the entire reconcile, but use a child context with a timeout of ~45 seconds for the cloud provider API calls, we'd hopefully have 10-15 seconds left of our parent context to update the status if/when we timeout due to the cloud provider being unresponsive.

@negz Yeah, that's pretty much what we want. I'll look into how I can do that and update this PR. Thanks for the suggestion!

I have tested this by putting time.Sleep(45*time.Second) in an Observe call of a managed resource and confirmed that context deadline exceeded returned from that call appeared as condition.

@negz I think this should be ready to merge.


Name Change

Checklist

[x ] I'm asking a question
[x ] I've looked through the README and FAQ for similar questions
[ x] I've searched the bugtracker for similar questions including closed ones

Question

youtube-dlc can download video/audio from more sites other than YouTube. This would be very good time to rename the project to indicate so.

@blackjack4494  any reply ?

Yes I feel you.
The reason why I kept the name youtube-dl and added a 'c' to it is that you can easily merge it back (folder will be auto identified as renamed). If youtube-dl ever want to merge something from this fork whatsoever.
But you are totally right. Some neutral name would be better.

I think that they could have banned you because they think that your fork might be better and might split up userbase and their userbase might decrease.
Because of your ban,i don't think that they are interested in your fork/interested in getting merges from this project.
I personally think that this project could be named to somewhat more intuitive. This could also increase the popularity of this project.

I am closing this issue as you have answered my question ( I assume "NO" as answer)

I created a label called Future so it's easier to sort for those.
But feel free to let this open and discuss about it. I just stated my opinion but is only for you to understand why I did it.
This should be community based/centered so in no means do I want to dictate anything and am glad about hearing other people's opinions and solutions to this :)

Ok, if you were to consider renaming, please consider my proposals:

mget -> media-get (pun on wget)

vidget -> video-get

mfetch -> media fetch

mdl -> media dl


#1179 @Nullable -> @Nonnull for getText(), innerText(), innerHtml(), …

…getSelectedText()

getSelectedOption() is non-nullable: if there is no selected option, it will throw an exception
any methods using WebElement.getAttribute() are nullable
unfortunately, all screenshots-related methods are nullable: taking a screenshot may fail at any moment

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Checklist

[ ] Checkstyle and unit tests are passed locally with my changes by running gradlew check chrome_headless firefox_headless command
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

@asolntsev
https://github.com/selenide/selenide/blob/fix-nullable-annotations/src/main/java/com/codeborne/selenide/impl/ScreenShotLaboratory.java#L67
marked as @Nullable but https://github.com/selenide/selenide/blob/fix-nullable-annotations/statics/src/main/java/com/codeborne/selenide/Screenshots.java#L25 isn't. Seems nullabl annotaions should be added to Screenshots.java too

@BorisOsipov done


Add Practice Exercise: micro-blog

Problem specification:
https://github.com/exercism/problem-specifications/tree/main/exercises/micro-blog
TODO:

generate the exercise with ./bin/fetch-configlet && ./bin/configlet create --practice-exercise micro-blog
check if any of the existing tracks (examples below) implement the exercise and you can reuse the implementation:

Go: https://github.com/exercism/go/tree/main/exercises/practice
Rust: https://github.com/exercism/rust/tree/main/exercises/practice
Python: https://github.com/exercism/python/tree/main/exercises/practice

use exercise's canonical-data.json to see which test cases to implement:
https://github.com/exercism/problem-specifications/blob/main/exercises/micro-blog/canonical-data.json

https://github.com/exercism/cairo/pull/254#issuecomment-2334748046


Homography Matrix for optical flow

Im trying to use the output of the net (H -> homography matrix) to create an optical flow map
the pred_full is correct and the interpolate returns the correct frame, however when is use the formula the create the map from the matrix i get worng flow values
code use to calc the map:

new cord is the cord for frame 2
H is homo matrix

 newCord = np.matmul(**H**,oldCord)
 newCord[0,:] = newCord[0,:]/newCord[2,:]
 newCord[1,:] = newCord[1,:]/newCord[2,:]
 newX = np.reshape(newCord[0,:],(rows,cols))
 newY = np.reshape(newCord[1,:],(rows,cols))
 dX = newCord[0,:] - X.flatten()
 dY = newCord[1,:] - Y.flatten()```

What am i doing wrong???

May I have a look on  your optical-flow and warped img?


Lubwisi site displays vernacular incorrectly

I uploaded Lubwisi to its site, https://www.webonary.org/lubwisi/browse/browse-lubwisi-english/. It looks like this:

Then I uploaded the same project to my test site, https://www.webonary.org/test-stutzman2/browse/browse-vernacular/ and it looks right,

The reversal looks correct.

The FLEx project can be accessed here: https://drive.google.com/file/d/1Vcyr__dQViCwllJmSYvusiYtc-g5BhqM/view?usp=share_link.

I discovered that there is a checkbox for Display subentries as main entries. If I unchecked it then the vernacular browse view displayed fine.

After I unchecked it the option went away.
What is the purpose of that checkbox?

I am removing it for cloud sites. I assume it was added for a reason and I don't want to break any old sites that need it.


Using Assets which requires attribution

Can I use part of this asset in my clock?
https://www.vecteezy.com/vector-art/85439-free-forest-landscape-with-flock-of-birds-vector
Thanks.

Also, can I use flare (rive) assets made by others?
https://rive.app/explore

Check FACs for more informations...You must create all assets.

You do not need to create them, but they must have an appropriate license. See flutter.dev/clock:
"Your Submission’s code must be licensed under an appropriate open source license (for code, BSD aka University of California license, MIT license or Apache 2.0 license are recommended; for assets, CC BY 4.0 license or Apache 2.0 license are recommended; for fonts, OFL license is recommended)."


Lag after losing focus

In many cases I find a long lag after I return to the Cmder window after it lost focus to do something else. Commands does not work and I have to wait about 10seconds before it starts to respond again.
Is this a known issue? Any workarounds?

There was a similar issue some time ago, but I was under the impression it had been fixed. Either way, the solution that worked for me can be found here.

Ok thanks, I don't think I'm running the latest version.
Have set it and will check if it still happens.
On Wednesday, 4 February 2015, Ryan Morrin<EMAIL_ADDRESS>wrote:

There was a similar issue some time ago, but I was under the impression it
had been fixed. Either way, the solution that worked for me can be found
here. https://github.com/bliker/cmder/issues/40#issuecomment-29648808
—
Reply to this email directly or view it on GitHub
https://github.com/bliker/cmder/issues/385#issuecomment-72820505.

This has been fixed in the latest version but if you want to fix it yourself, untick this option:
https://github.com/bliker/cmder/issues/109#issuecomment-31736141


bug(ion-input): clearInput attribute not working

Short description of the problem:
When testing in the browser and on a device, I am not able to press the close button on the ion-input that has the clearInput attribute. This means I cannot easily clear the text box.
It appears as though the button is disabled?
Note that the input event does not seem to be firing when this button is enabled.
  <ion-card>
    <ion-item>
      <ion-label floating>Movie Name</ion-label>
      <ion-input  type="text" (input)='search($event)' clearInput></ion-input>
    </ion-item>
  </ion-card>

Which Ionic Version? 2.x
Plunker that shows an example of your issue
http://plnkr.co/edit/V3INKguqz8E4BopcJ21w?p=preview
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.1.1
Gulp version:  CLI version 3.9.1
Gulp local:   Local version 3.9.1
Ionic Framework Version: 2.0.0-beta.7
Ionic CLI Version: 2.0.0-beta.24
Ionic App Lib Version: 2.0.0-beta.14
OS:
Node Version: v5.10.1

Thanks for the issue! So is the button working when you click it when you are not focused in the input? I have an open issue for fixing that issue if so: https://github.com/driftyco/ionic/issues/6514
Just trying to see if this is the same issue. :smile:

Hi @brandyscarney
See: http://plnkr.co/edit/xz6INvvLKyTJS4TWgOhr?p=preview
The clearInput button becomes active when the focus moves off of the input field.

Thanks for the plunker! This is the same issue as #6514 so I am going to close this one. :smile:


Option to open a folder as a new VS Code window

When right-clicking a folder in your project, there should be an option to open the folder in a new VS Code window, it would be nice :)

https://marketplace.visualstudio.com/items?itemName=chrisdias.vscode-opennewinstance


echo $SHELL is wrong

echo $SHELL returns /bin/zsh  but that is obviously false; it has none of the features of ZSH.
echo $BASH_VERSION returns 3.2.57(1)-release which matches macOs's /bin/bash version.

thanks for identifying these issues. any thoughts?
Some notes of the Kui architecture:

Kui proxies commands to an underlying shell. it currently does so via an underlying bash (on mac and linux) or powershell (on windows).

At the same time, it gathers your environment variables and aliases from whatever SHELL you have configured as your default (zsh, in your case).

The reason kui fixes the proxied requests to bash (rather than your default SHELL) is something we can fix, but is mostly just a statement in time.

Why doesn't kui hold open a connection to an underlying (and durable) shell process? this is a possibility, but doing so would require some rethinking of the Kui REPL. Kui's read-eval-print-loop decides whether the command will be serviced by a Kui plugin, or by an underlying shell process. since Kui is in charge of the REPL, it therefore needs to know when a command execution completes (so it can Loop!). we weren't sure if this was possible to manage via a persistent shell process (where the job control is, to the best of our knowledge, a mostly opaque affair managed by the shell).

Is the bash version included in KUI or is it hard coded to /bin/bash?  It might be better to include the shell in KUI itself on UNIXy platforms.
The problem/danger with using the user's shell configuration in their prompt may be complex and hard to render. e.g. my zsh problem requires Nerd Fonts.
If you can point at the REPL code, maybe I can think of something.  I've done lots of shell stuff, including (for example) executing commands over a standing ssh connection.  There are tricks you can use to detect what's going on.

* At the same time, it gathers your environment variables and aliases from whatever SHELL you have configured as your default (zsh, in your case).

It doesn't seem to do a good job of this. I use fish, and every command I run in Kui has this before the output:
bash: alias: doh-client: not found
bash: alias: docker run --rm -it monachus/doh-tools client: not found
bash: alias: hey: not found
bash: alias: docker run --rm -it rcmorano/docker-hey: not found
bash: alias: k: not found
bash: alias: kubectl: not found
bash: alias: ka: not found
bash: alias: kubectl apply: not found
bash: alias: kak: not found
<snip>

My best guess is that this is because, while the fish aliases file follows a bash-like format, the output of the alias command does not:
➤ alias
alias doh-client 'docker run --rm -it monachus/doh-tools client'
alias hey 'docker run --rm -it rcmorano/docker-hey'
alias k kubectl
alias ka 'kubectl apply'

Would this be easy to fix with some regex magic before passing it off to Bash, or with error handling to dump aliases that don't follow the correct format? Since everything is bounced to a new Bash shell, there doesn't seem to be any way to avoid this or filter it out, and it makes Kui unusable for me.
UPDATE: I was able to get around it by converting all my aliases to functions by recreating them with alias -s and then deleting aliases.fish:
cat aliases.fish | sed -E 's/^alias //' | grep -vE '^$' | grep -Ev '#' | while read x; set name (echo $x | awk -F= '{ print $1 }'); echo $name; set val (echo $x | awk -F= '{ print $2 }'); if ! test -f ~/.config/fish/functions/$name.fish; alias -s $name=$val; end; end

/remove-lifecycle stale


[Bug]: Unable to view token counts from Bedrock LLM instance and phoenix Observability

Bug Description
I am unable to see token counts for LLM models instantiated using Bedrock class. I am using phoenix as Observability tool.
Version
0.10.20
Steps to Reproduce
You can use the starter 5 lines code to reproduce this.
import phoenix as px
from llama_index.core import set_global_handler
from llama_index.llms.bedrock import Bedrock
from llama_index.core import Settings
session = px.launch_app()
set_global_handler("arize_phoenix")
profile_name = "Your aws profile name"
llm= Bedrock(
model="amazon.titan-text-express-v1", profile_name=profile_name
)
Settings.llm = llm
llm.complete("What is the capital of france?")
Relevant Logs/Tracbacks
No response

@dosu I am aware that the token counting handler is sufficient for estimating the token counts. But this issue is related to arize_phoenix observability integration is not working with Bedrock models of llama-index. Hope you got the context now.

I am getting following error:
ImportError: cannot import name 'CallbackManager' from 'llama_index.core'
(llama-index : Version: 0.11.1)