cannot remap copy to ctrl-c

Description of the problem or steps to reproduce
i wanted to use ctrl+c (no shift, just: ctrl+c) instead of the default ctrl+C (you need shift with the default keybind). so i created ~/.config/micro//bindings.json and i've put inside:
{
"ctrl-c":"Copy",
"ctrl-p":"Paste"
}

and it is not being picked up by micro.
i tried to change the case with: "Ctrl" instead of "ctrl", i also tried "Ctrlc" and "ctrlc" and more, but nothing woked.
Specifications
Commit hash: 1856891
OS: ubuntu 19.04
Terminal: st
i also tried with the nightly:
$ ./micro --version
Version: 1.4.2-dev.77
Commit hash: 3a8898d
Compiled on July 27, 2019
it didn't work either.
i use that hotkey in my terminal all day long, it works fine, i copy with ctrl+c, and i send break with ctrl+shift+c. i wanted to do the same in micro.

The default binding is ctrl-c (no shift). Make sure you install xclip or xsel for micro to be able to interact with the clipboard. Without these tools installed, micro will only use an internal clipboard for copy and paste. When you use ctrl-shift-c, you are likely accessing the clipboard through your terminal application rather than through micro.

xclip is installed.
please watch this:  https://ufile.io/b2iutmgx
this is a small video (less than 5mb) that shows what i was talking about in my first post.


Image File not found error in web directory when running flutter create

Steps to Reproduce

... install version 2.5.3 for macOS and add to PATH
... run flutter create my_app
... profit

Logs

Logs

❯ flutter create test_app
Creating project test_app...
  test_app/test/widget_test.dart (created)
  test_app/pubspec.yaml (created)
  test_app/README.md (created)
  test_app/lib/main.dart (created)
  test_app/ios/Runner.xcworkspace/contents.xcworkspacedata (created)
  test_app/ios/Runner.xcworkspace/xcshareddata/IDEWorkspaceChecks.plist
  (created)
  test_app/ios/Runner.xcworkspace/xcshareddata/WorkspaceSettings.xcsettings
  (created)
  test_app/ios/Runner/Info.plist (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  (created)
  test_app/ios/Runner/Assets.xcassets/LaunchImage.imageset/README.md (created)
  test_app/ios/Runner/Assets.xcassets/LaunchImage.imageset/Contents.json
  (created)
  test_app/ios/Runner/Assets.xcassets/LaunchImage.imageset/LaunchImage.png
  (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  ng (created)
<EMAIL_ADDRESS>  ng (created)
<EMAIL_ADDRESS>  (created)
  test_app/ios/Runner/Assets.xcassets/AppIcon.appiconset/Contents.json (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  (created)
<EMAIL_ADDRESS>  (created)
  test_app/ios/Runner/Base.lproj/LaunchScreen.storyboard (created)
  test_app/ios/Runner/Base.lproj/Main.storyboard (created)
  test_app/ios/Runner.xcodeproj/project.xcworkspace/contents.xcworkspacedata
  (created)
  test_app/ios/Runner.xcodeproj/project.xcworkspace/xcshareddata/IDEWorkspaceChe
  cks.plist (created)
  test_app/ios/Runner.xcodeproj/project.xcworkspace/xcshareddata/WorkspaceSettin
  gs.xcsettings (created)
  test_app/ios/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme (created)
  test_app/ios/Flutter/Debug.xcconfig (created)
  test_app/ios/Flutter/Release.xcconfig (created)
  test_app/ios/Flutter/AppFrameworkInfo.plist (created)
  test_app/ios/.gitignore (created)
  test_app/test_app.iml (created)
  test_app/.gitignore (created)
  test_app/web/favicon.png (created)
  test_app/web/index.html (created)
  test_app/web/manifest.json (created)
  test_app/web/icons/Icon-maskable-512.png (created)
Image File not found
/Users/cbonifacio/development/test_app/web/icons/Icon-maskable-512.png

Hi @chrisbonifacio, thanks for filing the issue.
I attempted to reproduce, but the project setup was just fine for me.
Please share the output of flutter create <foo> -v and flutter doctor -v.
The output of flutter create <foo> -v is likely to be huge so you can just put it into a text field and attach it here.
Thank you
side note:  represents your project name.

flutter create -v
[ +126 ms] executing: sysctl hw.optional.arm64
[  +20 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[   +6 ms] executing: [/Users/cbonifacio/development/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +8 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 18116933e77adc82f80866c928266a5b4f1ed645
[        ] executing: [/Users/cbonifacio/development/flutter/] git tag --points-at 18116933e77adc82f80866c928266a5b4f1ed645
[  +17 ms] Exit code 0 from: git tag --points-at 18116933e77adc82f80866c928266a5b4f1ed645
[        ] 2.5.3
[  +10 ms] executing: [/Users/cbonifacio/development/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +10 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/Users/cbonifacio/development/flutter/] git ls-remote --get-url origin
[   +9 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[ +123 ms] executing: [/Users/cbonifacio/development/flutter/] git rev-parse --abbrev-ref HEAD
[  +14 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +5 ms] stable
[  +12 ms] executing: sw_vers -productName
[  +43 ms] Exit code 0 from: sw_vers -productName
[        ] macOS
[        ] executing: sw_vers -productVersion
[  +31 ms] Exit code 0 from: sw_vers -productVersion
[   +2 ms] 12.0.1
[        ] executing: sw_vers -buildVersion
[  +22 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 21A559
[  +70 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[  +10 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'WindowsUwpEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +47 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'WindowsUwpEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'PubDependencies' is not required, skipping update.
[  +47 ms] Creating project test_flutter_app...
[  +53 ms] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/flutter_window.cpp, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/utils.h, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/run_loop.h, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/utils.cpp, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/runner.exe.manifest, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/CMakeLists.txt, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/win32_window.h, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/Runner.rc.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/win32_window.cpp, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/resources/app_icon.ico.img.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/main.cpp.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/resource.h, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/run_loop.cpp, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/runner/flutter_window.h, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/flutter/CMakeLists.txt, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/.gitignore, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/windows.tmpl/CMakeLists.txt.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner.xcworkspace/contents.xcworkspacedata, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner.xcworkspace/xcshareddata/IDEWorkspaceChecks.plist, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner.xcworkspace/xcshareddata/WorkspaceSettings.xcsettings, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner/Info.plist.tmpl, missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner/Assets.xcassets/LaunchImage.imageset/README.md, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner/Assets.xcassets/LaunchImage.imageset/Contents.json, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner/Assets.xcassets/LaunchImage.imageset/LaunchImage.png, missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner/Assets.xcassets/AppIcon.appiconset/Contents.json, missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping<EMAIL_ADDRESS>missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner/Base.lproj/LaunchScreen.storyboard, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner/Base.lproj/Main.storyboard, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner.xcodeproj/project.xcworkspace/contents.xcworkspacedata, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner.xcodeproj/project.xcworkspace/xcshareddata/IDEWorkspaceChecks.plist, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner.xcodeproj/project.xcworkspace/xcshareddata/WorkspaceSettings.xcsettings, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Flutter/Debug.xcconfig, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Flutter/Release.xcconfig, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/Flutter/AppFrameworkInfo.plist, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios.tmpl/.gitignore, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/projectName.iml.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/.gitignore.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/web/favicon.png.copy.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/web/index.html.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/web/manifest.json.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/web/icons/Icon-192.png.copy.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/web/icons/Icon-512.png.copy.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/.metadata.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner.xcworkspace/contents.xcworkspacedata, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner.xcworkspace/xcshareddata/IDEWorkspaceChecks.plist, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_16.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_1024.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_256.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_64.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_512.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_128.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Assets.xcassets/AppIcon.appiconset/Contents.json, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_32.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/DebugProfile.entitlements, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Base.lproj/MainMenu.xib, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/MainFlutterWindow.swift, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Configs/Debug.xcconfig, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Configs/Release.xcconfig, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Configs/Warnings.xcconfig, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Configs/AppInfo.xcconfig.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/AppDelegate.swift, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Info.plist, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner/Release.entitlements, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner.xcodeproj/project.xcworkspace/xcshareddata/IDEWorkspaceChecks.plist, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner.xcodeproj/project.pbxproj.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Flutter/Flutter-Debug.xcconfig, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/Flutter/Flutter-Release.xcconfig, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/macos.tmpl/.gitignore, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios-objc.tmpl/Runner/AppDelegate.h, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios-objc.tmpl/Runner/main.m, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios-objc.tmpl/Runner/AppDelegate.m, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios-objc.tmpl/Runner.xcodeproj/project.pbxproj.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios-objc.tmpl/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/profile/AndroidManifest.xml.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/mipmap-mdpi/ic_launcher.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/mipmap-hdpi/ic_launcher.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/drawable/launch_background.xml, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/mipmap-xxxhdpi/ic_launcher.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/mipmap-xxhdpi/ic_launcher.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/values-night/styles.xml, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/values/styles.xml, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/drawable-v21/launch_background.xml, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/main/res/mipmap-xhdpi/ic_launcher.png, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/main/AndroidManifest.xml.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/app/src/debug/AndroidManifest.xml.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/gradle/wrapper/gradle-wrapper.properties, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/gradle.properties.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/.gitignore, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android.tmpl/settings.gradle, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android-kotlin.tmpl/app/build.gradle.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android-kotlin.tmpl/app/src/main/kotlin/androidIdentifier/MainActivity.kt.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android-kotlin.tmpl/build.gradle, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android-kotlin.tmpl/projectName_android.iml.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios-swift.tmpl/Runner/Runner-Bridging-Header.h, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios-swift.tmpl/Runner/AppDelegate.swift, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios-swift.tmpl/Runner.xcodeproj/project.pbxproj.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/ios-swift.tmpl/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android-java.tmpl/app/build.gradle.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android-java.tmpl/app/src/main/java/androidIdentifier/MainActivity.java.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android-java.tmpl/build.gradle, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/android-java.tmpl/projectName_android.iml.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/.idea/runConfigurations/main_dart.xml.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/.idea/libraries/Dart_SDK.xml.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/.idea/libraries/KotlinJavaRuntime.xml.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/.idea/modules.xml.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/.idea/workspace.xml.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/linux.tmpl/main.cc, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/linux.tmpl/my_application.h, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/linux.tmpl/my_application.cc.tmpl, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/linux.tmpl/flutter/CMakeLists.txt, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/linux.tmpl/.gitignore, missing from the template manifest.
[        ] Skipping /Users/cbonifacio/development/flutter/packages/flutter_tools/templates/app/linux.tmpl/CMakeLists.txt.tmpl, missing from the template manifest.
[  +11 ms]   test_flutter_app/test/widget_test.dart (created)
[  +13 ms]   test_flutter_app/pubspec.yaml (created)
[   +1 ms]   test_flutter_app/README.md (created)
[        ]   test_flutter_app/lib/main.dart (created)
[   +3 ms]   test_flutter_app/ios/Runner.xcworkspace/contents.xcworkspacedata (created)
[   +2 ms]   test_flutter_app/ios/Runner.xcworkspace/xcshareddata/IDEWorkspaceChecks.plist (created)
[   +1 ms]   test_flutter_app/ios/Runner.xcworkspace/xcshareddata/WorkspaceSettings.xcsettings (created)
[   +1 ms]   test_flutter_app/ios/Runner/Info.plist (created)
[        ]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]   test_flutter_app/ios/Runner/Assets.xcassets/LaunchImage.imageset/README.md (created)
[   +1 ms]   test_flutter_app/ios/Runner/Assets.xcassets/LaunchImage.imageset/Contents.json (created)
[   +2 ms]   test_flutter_app/ios/Runner/Assets.xcassets/LaunchImage.imageset/LaunchImage.png (created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]   test_flutter_app/ios/Runner/Assets.xcassets/AppIcon.appiconset/Contents.json (created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]<EMAIL_ADDRESS>(created)
[   +1 ms]   test_flutter_app/ios/Runner/Base.lproj/LaunchScreen.storyboard (created)
[   +1 ms]   test_flutter_app/ios/Runner/Base.lproj/Main.storyboard (created)
[   +1 ms]   test_flutter_app/ios/Runner.xcodeproj/project.xcworkspace/contents.xcworkspacedata (created)
[   +2 ms]   test_flutter_app/ios/Runner.xcodeproj/project.xcworkspace/xcshareddata/IDEWorkspaceChecks.plist (created)
[   +2 ms]   test_flutter_app/ios/Runner.xcodeproj/project.xcworkspace/xcshareddata/WorkspaceSettings.xcsettings (created)
[   +3 ms]   test_flutter_app/ios/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme (created)
[   +3 ms]   test_flutter_app/ios/Flutter/Debug.xcconfig (created)
[   +3 ms]   test_flutter_app/ios/Flutter/Release.xcconfig (created)
[   +1 ms]   test_flutter_app/ios/Flutter/AppFrameworkInfo.plist (created)
[   +1 ms]   test_flutter_app/ios/.gitignore (created)
[   +1 ms]   test_flutter_app/test_flutter_app.iml (created)
[   +1 ms]   test_flutter_app/.gitignore (created)
[   +1 ms]   test_flutter_app/web/favicon.png (created)
[   +2 ms]   test_flutter_app/web/index.html (created)
[   +4 ms]   test_flutter_app/web/manifest.json (created)
[   +3 ms]   test_flutter_app/web/icons/Icon-maskable-512.png (created)
[  +36 ms] "flutter create" took 323ms.
[  +10 ms] Image File not found /Users/cbonifacio/Work/test_flutter_app/web/icons/Icon-maskable-512.png
[   +5 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      Template.render. (package:flutter_tools/src/template.dart:320:11)
           #2      _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:400:8)
           #3      Template.render (package:flutter_tools/src/template.dart:253:24)
           #4      CreateBase.renderMerged (package:flutter_tools/src/commands/create_base.dart:429:21)

           #5      CreateBase.generateApp (package:flutter_tools/src/commands/create_base.dart:440:23)

           #6      CreateCommand.runCommand (package:flutter_tools/src/commands/create.dart:269:31)

           #7      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:1125:27)

           #8      AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

           #9      CommandRunner.runCommand (package:args/command_runner.dart:209:13)

           #10     FlutterCommandRunner.runCommand. (package:flutter_tools/src/runner/flutter_command_runner.dart:288:9)

           #11     AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

           #12     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:236:5)

           #13     run.. (package:flutter_tools/runner.dart:62:9)

           #14     AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

           #15     main (package:flutter_tools/executable.dart:92:3)

[ +174 ms] ensureAnalyticsSent: 168ms
[   +1 ms] Running shutdown hooks
[        ] Shutdown hooks complete
[        ] exiting with code 1

flutter doctor -v
[✓] Flutter (Channel stable, 2.5.3, on macOS 12.0.1 21A559 darwin-x64, locale en-US)
    • Flutter version 2.5.3 at /Users/cbonifacio/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (4 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/cbonifacio/Library/Android/sdk
• Platform android-30, build-tools 30.0.3
• ANDROID_HOME = /Users/cbonifacio/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 13.1, Build version 13A1030d
• CocoaPods version 1.11.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
[✓] VS Code (version 1.62.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension can be installed from:
🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)
• Chrome (web) • chrome • web-javascript • Google Chrome 95.0.4638.69
• No issues found!

Hi @chrisbonifacio, I need you to do one thing for me.
Can you check on the master channel if you still experience this issue?
flutter channel master
flutter upgrade --force
flutter doctor -v
Thank you

@danagbemava-nc Sorry, I should've posted an update here. I uninstalled flutter and re-installed it via homebrew which seems to have fixed my issues. Thank you though!


[Feature Request] Editable "give" command for cheat mode.

Hello !
I have confirmed that this is not possible in the current version via the discord support channel.
If you enable cheat-mode in EMI, you can use it to grab items from it, be it a piece, or a stack, however if you are playing on a server which is not using the default minecraft commands, you will only see an error appear in chat when trying to use this feature.
This could be solved easily by letting the user edit the command used in the config. I dont know what the current command is formatted, but I would suggest following the example of JourneyMap. A box where the default command would be I imagine something like "/give {name} {item} {quantity}" and that can be edited freely by the user.
Hope more people will find this useful.

I can understand why someone might find utility in this but... it seems pretty low cost to support vanilla commands on a server, and I'm not sure why it wouldn't even be an option. A more serious concern is the ability to secretly put any command into modpack. Say you made an EMI addon pack for a vanilla compatible server and changed the command to, say, run /op myusername, so if any of the admins ever used the pack, they'd get opped. This may seem like a wild concern but allowing arbitrary commands is something I'd definitely not want to add lightly with that concern in mind.

Repackaging the .jar would be an unauthorized redistribution and would not be hosted on CurseForge
Downloading modpacks hosted on third-party website is always a risk
The developer for JourneyMap implementing it is their own decision, doesn't mean that other developers need to do the same if they don't like the risks that come with it

I'm going to close this issue as I just don't think I want to put hidden arbitrary command scripting at a button press.


chore: make error_status and resource_name tests discoverable

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 67.64%. Comparing base (84e5f3c) to head (0cc562f).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #100      +/-   ##
==========================================
+ Coverage   67.47%   67.64%   +0.16%
==========================================
  Files          36       36
  Lines        3533     3533
  Branches      615      615
==========================================
+ Hits         2384     2390       +6
+ Misses        824      818       -6
  Partials      325      325

see 1 file with indirect coverage changes


Permissions to tables

Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if any
[x] I have reproduced the issue with at least the latest released version of superset
[x] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.20.5
Expected results
I want a restricting access to a table, not only on datasource. for example, when i add a mysql database, I want Role A can see parts of tables in the database,and Role B can see the different parts of tables.Does superset support this? I only found permission on datasource or slice.
Actual results
Steps to reproduce

Aren't table datasources?

Thanks a lot, according to your answer, I resolve the problem. Just in Datasource-->Tables, add table can create a view, awesome!


Utilized to call an external API for OAuth token?

Describe the solution you'd like
I simply would like to call an external API endpoint for an OAuth token and then have a secret created
What is the added value?
Not having to store the token in a vault, simply grab it from the source.
Give us examples of the outcome
Something similar to the webook provider, but just calling an API endpoint instead
Observations (Constraints, Context, etc):
Maybe we can use the webhook provider for this? Or would this need to be a new feature developed?

Hi @nmajin ! If you have the necessary information to get the OAuth token, I believe webhook provider would already work =)

After installing the Operator, I've configured a SecretStore and ExternalSecret and applied them both. I am not seeing any activity, including anything in the external-secrets-operator-controller-manager pod. I was expecting to at least see a call out to the remote endpoint at least using.
apiVersion: external-secrets.io/v1alpha1
kind: SecretStore
metadata:
  name: example-webhook-secretstore
spec:
  provider:
    webhook:
      url: "https://api/oauth"
      method: POST
      timeout: 1m
      result:
        jsonPath: "$.token"
      headers:
        Content-Type: application/json
        Accept: application/json
      body: '{"username": "<user>", "password": "<pass>"}'

apiVersion: external-secrets.io/v1alpha1
kind: ExternalSecret
metadata:
  name: example-webhook-externalsecret
spec:
  refreshInterval: "1m"
  secretStoreRef:
    name: example-webhook-secretstore
    kind: SecretStore
  target:
    name: example-sync
  data:
  - secretKey: foobar
    remoteRef:
      key: secret

I am also wondering if this will even work for my case here where I have to hit the API sending the creds in the body, not the Authorization header:
"Limitations
Webhook does not support authorization, other than what can be sent by generating http headers"
https://external-secrets.io/v0.4.4/provider-webhook/#limitations

So the good news is that this appears to be working! However, there was a missing component "OperatorConfig", which was that clear for the OLM install, but I guess it is referenced here: https://operatorhub.io/operator/external-secrets-operator.
The syntax for the body, which is not documented well:
body: "{\"username\": \"test\", \"password\": \"test\"}"
And it appears we can authenticate via passing in creds in the body, so the limitation is not clear.


Myriad core not loading

When attempting to open myriad-qt, during process of loading block index, a runtime error appears.
file validation.cpp line 2452
!setblockindexcandidates.empty()
loading fails, repeated 3 times. win 10 64bit

Have you tried with
myriad-qt.exe -reindex

Also, perhaps you might try removing all but your wallet.dat and redownloading.

It looks like the reinstall will work fine, thank you. I had nothing in the wallet yet, so no worries there.


[Bug]: Unable to link to the local model according to the document link

Bug Description
Unable to link to the local model according to the document link
`from llama_index.llms.ollama import Ollama
from llama_index.core.llms import ChatMessage
llm = Ollama(model="wangshenzhi/llama3.1_8b_chinese_chat", request_timeout=300.0)
resp = llm.complete("Who is Paul Graham?")
print(resp)
messages = [
ChatMessage(
role="system", content="You are a pirate with a colorful personality"
),
ChatMessage(role="user", content="What is your name"),
]
resp = llm.chat(messages)
print(resp)`
curl is OK

Version
Latest version
Steps to Reproduce
refer to https://docs.llamaindex.ai/en/stable/examples/llm/ollama/
Relevant Logs/Tracbacks
No response

Thank you, I have resolved the issue and your response was very timely and excellent.Have a good day！


SubList  field is invalid or not supported.

OS: Windows 10
Node.js version: e.g. 12.16.1 LTS
suitecloud-cli version: 1.0.4
Describe the bug
The CLI validation doesn't handle the  field of sublists during project validation.
To Reproduce

use 'suitecloud account:setup` to login into any account.

then use suitecloud object:import -i to import into the SDF projcect any custom entry form which has an entry in the sublists tab. For example, in my account, I have a vendor entry form like this

Open the .xml file in your editor and search for the subList keyword. Verify that at least ONE of your subList items has the 'neverEmpty' property. For example, with the vendor form shown above

  <subItems>
    <subList>
      <id>ENTITYMESSAGES</id>
      <label>Messages</label>
      <visible>T</visible>
      <neverEmpty>false</neverEmpty>
    </subList>
  </subItems>

in the SAME account, execute suitecloud project:validate

Actual Behavior
The CLI raises this error
An error occurred during custom object validation. (custform_XXXXXX)
Details: The neverEmpty field is invalid or not supported.

Expected Behavior
Objects imported from a working NetSuite instance, should either

NOT import xml with unsupported or invalid values. Or,
all values imported from a working account should be valid or supported.

Thanks for reporting this detailed case @grugknuckle , we will investigate and reproduce and I´ll get back to you.

This behavior occurs in the Eclipse plugin as well. Would love to see this issue resolved!

@grugknuckle @stephen-suiterep just wanted to give you an update in the reported issue.
This has already bin fixed and we are testing the solution. Hopefully we will role out the fix with upcoming major release.

@alii-gator - Thanks for fixing it. I came back to this issue because I happened to read this article in the help.
/app/help/helpcenter.nl?fid=section_N2858591.html
Where it states:
"The Never Empty box is not available for all sublists. Only sublists that are listed in the SuiteScript Records Browser are supported."
Which got me thinking that maybe it could be that the object XML generator is outputing the <neverEmpty> tag for unsupported sublists. Or that the code which parses the XML during import isn't taking this exception into account.

@grugknuckle
I am closing this issue since.
 should be fixed, let us know if it's otherwise.
do check out the lates node cli version 1.1.0

Thank you @alii-gator . I'll npm install the latest version and retest.


Support arbitrary custom mountpoints

Add unit test to test specific mountpoint paths against the mountpoint policy. Replace distro-specific unit tests which were testing basically the same thing, but in which distro. This makes little sense, since all distros use the same mountpoint policy.
Explicitly disallow mountpoints which can't / shouldn't be on a separate partition.
Relax the mountpoint policy to allow arbitrary custom mountpoints and adjust the unit test accordingly.

Related to https://issues.redhat.com/browse/COMPOSER-2030

Nice work and I really like the merged testing. Is there more work to be done here (draft)?

Not that I know of. I was just not sure if I didn't forget to fix some tests. :innocent:  But in general, this should be sufficient for this repo.


Remove conda default channel

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.092%

Totals

Change from base Build<PHONE_NUMBER>3:
0.0%

Covered Lines:
620

Relevant Lines:
652

💛  - Coveralls


reproducing a NeurIPS2018 paper using pytorch_geometric

The newly published NeruIPS 2018 paper (https://www.biostat.wisc.edu/~yli/preprints/yin_nips2018_camera_ready.pdf) has been applied on three visual recognition tasks: sementic segmentation, object dection and instance segmentation.
Could you consider implementing it and making it as part of your awesome API ?

I think this should be straightforward to implement in PyTorch Geometric, although I do not know if I find the time to implement it. Feel free to help out in designing a first draft :)


179 simulator  refactor architecture

Included in https://github.com/yeagerai/genlayer-simulator/pull/229


fix: /etc/kubernetes/super-admin.conf file perms for cis benchmark

What this PR does / why we need it:
FIxes
[FAIL] 1.1.13 Ensure that the default administrative credential file permissions are set to 600 (Automated)
[FAIL] 1.1.14 Ensure that the default administrative credential file ownership is set to root:root (Automated)
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Steps to reproduce

Does this PR introduce a user-facing change?

Fixes master CIS benchmark checks 1.1.13 and 1.1.14 for /etc/kubernetes/super-admin.conf file permissions.

Does this PR require documentation?

This is still failing and is blocked by a bug in kube-bench
https://github.com/aquasecurity/kube-bench/issues/1666
https://github.com/aquasecurity/kube-bench/issues/1667
with fix
https://github.com/aquasecurity/kube-bench/pull/1668


SEO Icon + 6th tile in scan results

Design an SEO icon for the SEO category in the scan results page (and readjust layout of category tiles)

@molant do we still need an SEO icon? I see your comment about an "other" or "misc" icon here.

We will eventually have that category. If you have cycles might as well do it now.

Two options to choose from.

Removing part of this issue's title to focus on the SEO icon bit since we don't technically have tiles or an issue with space anymore.


The destination VPN Client server does not allow administrating connections from remote computers.

Hi all,
I use Debian Jessie and I compile the latest git version of SoftEtherVPN.
Firstly, I start the vpnclient service:
$ sudo vpnclient start
The SoftEther VPN Client service has been started.
Then I want to use the vpncmd command to do the connection settings, but failed as follows:
$ sudo vpncmd
vpncmd command - SoftEther VPN Command Line Management Utility
SoftEther VPN Command Line Management Utility (vpncmd command)
Version 4.19 Build 9599   (English)
Compiled 2015/10/19 20:09:05 by yagi at pc30
Copyright (c) SoftEther VPN Project. All Rights Reserved.
By using vpncmd program, the following can be achieved.

Management of VPN Server or VPN Bridge
Management of VPN Client
Use of VPN Tools (certificate creation and Network Traffic Speed Test Tool)

Select 1, 2 or 3: 2
Specify the host name or IP address of the computer that the destination VPN Client is operating on.
If nothing is input and Enter is pressed, connection will be made to localhost (this computer).
Hostname of IP Address of Destination:
The destination VPN Client server does not allow administrating connections from remote computers. Launch the command line management utility or VPN Client Manager on the computer that VPN Client is running on and connect to localhost.
$
Previously I can use the above command to connect the vpnclient running on my local computer.
But, as you can see, the latest git version doesn't let me do this job, why does this happen?
Regards

Hello, I have the same issue in Ubuntu 16.04.5 LTS
vpnclient version is:

Version 4.28 Build 9669   (English)
Compiled 2018/09/11 12:23:27 by yagi at pc33

I had to manually set bool AllowRemoteConfig true in vpn_client.config file to make it work on localhost

Change the line to: bool AllowRemoteConfig true
./vpnclient stop
./vpnclient start


ERROR while setting up code signing

Ask your Question

I am trying to include code signing in my Re.Pack project using these two as references - https://github.com/callstack/repack/pull/348 & https://github.com/callstack/super-app-showcase/pull/43/
I am getting the following errors - please help fix this

Hi @pttchsswk,
Please provide a reproduction repository with your setup, I'm not able to do so with just the screenshot you've provided.
Btw, docs for CodeSigningPlugin should be available later this week (for the v4 version), perhaps you will be able to solve it yourself with them.

@pttchsswk I've closed this issue since we've added docs for code-signing available here:
https://re-pack.dev/4.x/docs/plugins/code-signing
If you still can't get it to work please open a new issue with a reproduction repository included so we can dig deeper into the problem you are/were having


fix #85 - string serializer returning None

Thanks for the PR, everything looks good to me, I'll merge when the CI checks are over :)

Cool, no worries. Turned out to be a bit trivial for a PR, but anyway. :)

By the way, I added django-nose to the test dependencies because the runtests.py script complained about it - not sure if I missed something and there was a reason django-nose wasn't included in requirements-test.txt before.

Okay, everything looks fine on my side, merge incoming!

1.3.1 was pushed to PyPi and includes this ;)


Solar mode power regulation

Describe the bug
When using solar mode with solar_max_import parameter greater than 0, the EVSE tries to reach solar_max_import value instead of 0.
For example, if you set "current_min": 6, "solar_start_current": 2 and "solar_max_import": 5
When mains meter drops below -2A charging starts, then it regulates charging power to keep mains meter around +5A.
Expected behavior
Charging current should stay at current_min (6A in my exemple) as long as mains meter don't drop under 0A.

Well your expectations are wrong: solar_max_import is exactly that.
I recommend setting solar_max_import to 0A, the solar timer to 60 minutes, and startcurrent at your preferres value, and you will see the behaviour you want!

Sorry, but the documentation says :

solar_max_import
The maximum current (sum of all phases) of the MainsMeter that can be imported before the solar timer is fired off,
  after expiration the car will stop charging.

So, it's a maximum not a target value and it's supposed to only trigger stop timer, not to regulate at that value.
Maybe it needs an additional parameter like solar_import

@TFleury I also prefer your version of this option, and i added a compile flag to  the Smartevse V2 version some years ago
https://github.com/SmartEVSE/SmartEVSE-2/commit/b784585f1a3091bb39330b42a2c2f88c417d3b3e

Yes, there should be two options.

The balance point (positive for steady import, negative for steady export)
The solar import (to allow start charging before reaching the 6 A surplus)

I also added a compile flag to change the solar import to a per phase value on the V2 version
https://github.com/SmartEVSE/SmartEVSE-2/commit/a58c5cc8a43e6416b9944f0efc9aade767d5cdab
because when configuring an import of e.g. 15 A, a 3 phase car waits until some solar power is available, while a 1 phase car starts charging at full speed...

Interesting; but you seem to prefer ImportCurrent = 0 (looking at #ifdef SPECIAL), so then #ifdef ALWAYS is not making any difference anymore ?!

@bobosch thank you for your feedback.
I think the two parameters approach is more interesting than compile flag which involves maintaining a different build.
Are you interested in a PR for that ?

but you seem to prefer ImportCurrent = 0 (looking at #ifdef SPECIAL), so then #ifdef ALWAYS is not making any difference anymore ?!
This was existing code, I don't touched it ...

Maybe It's enough to change the behavior of the START option
{"START",   "Surplus energy start Current (per charging phase)", 0, 16, START_CURRENT}
When set to e.g. 1 A it should also allow to draw 5 A from grid (and initiate STOP timer when drawing more)
as mentioned before it must be per charging phase for same behavior...
I have only V2 to test - I will implement it there first. When it works I will need some help to check it on V3

Good idea, it's simple and don't requires new setting.
I will be able to implement and test it on V3.

New commits on V2
c8f65863ddb3d4aa9a8f2f00ed88df26d871c035 Allow ImportCurrent to be negative (for steady export)
544a635e7296521e88df59f2ad4e5081dfeb302f Allow StartCurrent to be negative
ba6415511a215285029a056febed5d8d93db95e0 Make StartCurrent per phase (for same behaviour on different cars)
bc95b8d1f2d2619e3501afd7e71c55575666c4cc Stop solar charging only when over 6 A (per phase) more than StartCurrent is used

I tried to merge these commits into V3:
tmp.zip

I think the negative value handling is a bit tricky and it will introduce breaking changes with settings storage and web API.
I just proposed a PR (#70) to avoid start/stop cycles.


What will happen if both client and server starts a rpc-request at the same time ?

I am reading the vim rpc implementation:
https://github.com/vim-denops/denops.vim/blob/68f607d93a9758d15c0d63d3268aa420ddd29edd/autoload/denops/_internal/rpc/vim.vim#L27-L33
The function ch_evalexpr will send a request to the server and wait for a response. However, the TCP socket is a bi-directional channel. If the server sends a request or a notification at the same time, ch_evalexpr will not receive the correct response but instead a new request/notification from the server.
And the code using denops#_internal#rpc#vim#request will get an unexpected return value.
This is likely to happen when the server and client are sending notifications/requests to each other frequently or when the server is busy.
Another potential issue may occur due to nested RPC calls from both sides:
1) client is requesting a server function
2) in that server function, it will request another client-side function.
3) the client is still waiting for the response from the server-side, but it will only receive a new rpc-request.

Sorry for late reply.
Well, unfortunately we don't have clear answer for your question because we just use Vim's RPC implementation and we don't have deep knowledge about that.
However, denops works well for several years in many environments and we haven't heard about message mixed issues except on Neovim (that's solved already) so we think Vim properly handle such case.
Is this question comes from actual issues or just from code investigation?


Online AudioContext improvements (continue playing after drop, terminate event loop)

Fixes #464 #421

Looks good to me!
Just one question, what is the use case you envision for #464 ?

Or do you think it is better to keep the previous behaviour?

I dont know actually, no strong opinion... I don't really understand why someone would do that but I don't think this hurts neither :)


Error React !

Uncaught ReferenceError: React is not defined.

@vlade2008 did this solve your issue?

@vlade2008 You may just need to do
import * as React from 'react'

or
const React = require('react')

based on your build system's configuration wherever you use this module

Closing issue as it is not a problem with react-audio-recorder.


remove 'the' in 'This is the where you want'

remove 'the' in 'This is the where you want'
Summary
Describe your changes here.
Fixes #Issue_Number (if available)

Looks good. Thanks!!


Cannot install on Laravel 7

Hello,
I was trying to install on 7 but recieved the following errors:
Problem 1
- Conclusion: remove laravel/framework v7.28.4
- Conclusion: don't install laravel/framework v7.28.4
- swatty007/laravel-inline-editor v0.2.1 requires illuminate/database ^5.2 -> satisfiable by laravel/framework[5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.x-dev, 5.8.x-dev], illuminate/database[5.2.x-dev, 5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9].
- swatty007/laravel-inline-editor v0.2.1 requires illuminate/database ^5.2 -> satisfiable by laravel/framework[5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.x-dev, 5.8.x-dev], illuminate/database[5.2.x-dev, 5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9].
- Can only install one of: laravel/framework[5.4.x-dev, v7.28.4].
- Can only install one of: laravel/framework[5.5.x-dev, v7.28.4].
- Can only install one of: laravel/framework[5.6.x-dev, v7.28.4].
- Can only install one of: laravel/framework[5.7.x-dev, v7.28.4].
- Can only install one of: laravel/framework[5.8.x-dev, v7.28.4].
- don't install illuminate/database 5.7.17|don't install laravel/framework v7.28.4
- don't install illuminate/database 5.7.18|don't install laravel/framework v7.28.4
- don't install illuminate/database 5.7.19|don't install laravel/framework v7.28.4
- don't install illuminate/database 5.7.x-dev|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.0|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.1|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.10|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.11|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.15|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.2|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.20|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.21|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.22|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.23|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.26|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.27|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.28|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.3|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.4|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.5|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.6|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.7|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.8|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.7.9|don't install laravel/framework v7.28.4
- don't install illuminate/database 5.8.x-dev|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.0|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.11|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.12|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.14|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.15|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.17|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.18|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.19|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.2|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.20|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.22|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.24|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.27|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.28|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.29|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.3|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.30|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.31|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.32|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.33|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.34|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.35|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.36|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.4|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.8|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.8.9|don't install laravel/framework v7.28.4
- don't install illuminate/database 5.4.x-dev|don't install laravel/framework v7.28.4
- don't install illuminate/database 5.5.x-dev|don't install laravel/framework v7.28.4
- don't install illuminate/database 5.6.x-dev|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.4.0|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.4.13|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.4.17|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.4.19|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.4.27|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.4.36|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.4.9|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.0|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.16|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.17|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.2|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.28|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.33|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.34|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.35|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.36|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.37|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.39|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.40|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.41|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.43|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.5.44|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.0|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.1|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.10|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.11|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.12|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.13|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.14|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.15|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.16|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.17|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.19|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.2|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.20|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.21|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.22|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.23|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.24|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.25|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.26|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.27|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.28|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.29|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.3|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.30|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.31|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.32|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.33|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.34|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.35|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.36|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.37|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.38|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.39|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.4|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.5|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.6|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.7|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.8|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.6.9|don't install laravel/framework v7.28.4
- don't install illuminate/database 5.2.x-dev|don't install laravel/framework v7.28.4
- don't install illuminate/database 5.3.x-dev|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.0|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.19|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.21|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.24|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.25|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.26|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.27|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.28|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.31|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.32|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.37|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.43|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.45|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.6|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.2.7|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.3.0|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.3.16|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.3.23|don't install laravel/framework v7.28.4
- don't install illuminate/database v5.3.4|don't install laravel/framework v7.28.4
- Installation request for laravel/framework (locked at v7.28.4, required as ^7.0) -> satisfiable by laravel/framework[v7.28.4].
- Installation request for swatty007/laravel-inline-editor ^0.2.1 -> satisfiable by swatty007/laravel-inline-editor[v0.2.1].
Installation failed, reverting ./composer.json to its original content.
Could you please advise on the best way to get this installed?
Many Thanks

I managed to get it installed (I still had a few issues).
I created a fork of the repository and amended the composer.json for my version of Laravel
    "require": {         "illuminate/support": "7.*",         "illuminate/database": "7.*"     },
Then in my local projects composer file I added:
    "repositories": [         {             "type": "vcs",             "url": "https://github.com/rickg123/laravel-inline-editor"         }     ],
Then ran:
composer require swatty007/laravel-inline-editor "dev-master as 0.2.1" --ignore-platform-reqs
I will add the following issues I had soon.

Fixed with v0.3.0


Persist the source_id

Should we also update https://github.com/sul-dlss-labs/taco/pull/157/files#diff-b59c3123b50baba682c9babe1d65b958R54?

I would think so re updating both.


Add docs about using Shiv for packaging (similar to PEX)

What changes were proposed in this pull request?
The Shiv packaging tool works similarly to PEX and can be used to distribute Python with its dependencies in an executable. These changes mention Shiv and demonstrate it's use similar to the PEX project.
Why are the changes needed?
Shiv is a widely used packaging tool similar to PEX. These changes mention Shiv as an alternative tool.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
No code changes.

Can one of the admins verify this patch?

Let's create another section instead of reusing PEX, and make sure testing on Yarn cluster/client, K8S cluster client and standalone modes (all options here are manually tested by me).
I don't have a strong opinion on this (and I have less context on Shiv). I am fine with adding this if this library is expected to be actively maintained. Asking to user mailing list and collecting more feedback from the community might be another option before we go ahead.
cc @mridulm and @xkrogen who might have a better context on this. cc @fhoering for PEX.

ok to test

for the PR itself,

mind enabling Github Actions in your forked repository? see also https://github.com/apache/spark/pull/34083/checks?check_run_id=3693066509
please file a JIRA and format the Pr title (see also https://spark.apache.org/contributing.html)

Test build #143578 has started for PR 34083 at commit c93ec6f.

Test build #143578 has finished for PR 34083 at commit c93ec6f.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143578/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48087/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48087/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/48087/

Agree with @HyukjinKwon - it would be good to start a discussion in spark mailing lists as well.

Can one of the admins verify this patch?

+CC @zhouyejoe

Hi, @HyukjinKwon. Thanks for reviewing it. We have tested in YARN cluster mode. Will check with client mode, and also K8s cluster/client mode, standalone mode.
I am wondering what kind of testing that needs to be conducted. Does a simple job with some dependencies work? Or do we need some other kinds complex set up?

Looks like this got dropped from our review radar @HyukjinKwon.
Do you think this is valid ? If yes, we can reopen and review ...

@mridulm I think we can reopen this until we have done enough testing around using Shiv here. Thoughts?

Sounds good, we can revisit the PR once we have validated things.

Sounds good, we can revisit the PR once we have validated things.

Shall we add a JIRA ticket for this?


Use Design System date format in Support app

What
Replace date picker in the following forms:

[ ] “Request a new campaign”
[ ] “Remove user”
[ ] “Content change request”
[ ] “Content advice and help”
[ ] Feedback Explorer "Total quantity by day" (https://support.publishing.service.gov.uk/anonymous_feedback/explore)

in Support app to use Design System date format: https://design-system.service.gov.uk/patterns/dates/ (separate fields for day, month, year). Add relevant validations.
NB: we are not converting the forms to Design System

[ ] Remove "jquery-ui-rails" dependency https://github.com/alphagov/support/blob/main/Gemfile#L18 and any related JS.

[ ] Reply to the Zendesk ticket.

Why
Date picker arrows in Support app stopped working after the migration to Dart Sass. It’s caused by a known issue in the way Dart Sass handles the icon as Unicode - https://github.com/sass/sass/issues/1395 we were not able to find a workaround. Date picker are not very accessible. When users are filling the dates in the form they normally know them already (and don’t need to pick it by looking at a calendar).
Users see a  symbol instead of an arrow. There’s alt text (Next, Prev). It’s also possible to enter date manually.
This will allow us to drop dependency on jquery-ui-rails.

Reopening because we still need to remove date picker from 2 fields in Feedback Explorer: https://support.staging.publishing.service.gov.uk/anonymous_feedback/explore
before we can remove "jquery-ui-rails" dependency.
I've added that to the task list


[fix] [broker] fix flaky test auto subscribe patter consumer from broker watcher

Motivation
see: https://github.com/apache/pulsar/actions/runs/6257755998/job/16993960633?pr=21216
  Error:  org.apache.pulsar.client.impl.PatternTopicsConsumerImplTest.testAutoSubscribePatterConsumerFromBrokerWatcher  Time elapsed: 10.152 s  <<< FAILURE!
  org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a org.apache.pulsar.client.impl.PatternTopicsConsumerImplTest expected [4] but found [0] within 10 seconds.
  	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
  	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
  	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
  	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
  	at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:769)
  	at org.apache.pulsar.client.impl.PatternTopicsConsumerImplTest.testAutoSubscribePatterConsumerFromBrokerWatcher(PatternTopicsConsumerImplTest.java:617)
  	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
  	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
  	at org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:139)
  	at org.testng.internal.invokers.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:47)
  	at org.testng.internal.invokers.InvokeMethodRunnable.call(InvokeMethodRunnable.java:76)
  	at org.testng.internal.invokers.InvokeMethodRunnable.call(InvokeMethodRunnable.java:11)
  	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
  	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
  	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
  	at java.base/java.lang.Thread.run(Thread.java:833)
  Caused by: java.lang.AssertionError: expected [4] but found [0]
  	at org.testng.Assert.fail(Assert.java:110)
  	at org.testng.Assert.failNotEquals(Assert.java:1577)
  	at org.testng.Assert.assertEqualsImpl(Assert.java:149)
  	at org.testng.Assert.assertEquals(Assert.java:131)
  	at org.testng.Assert.assertEquals(Assert.java:1418)
  	at org.testng.Assert.assertEquals(Assert.java:1382)
  	at org.testng.Assert.assertEquals(Assert.java:1428)
  	at org.apache.pulsar.client.impl.PatternTopicsConsumerImplTest.lambda$testAutoSubscribePatterConsumerFromBrokerWatcher$16(PatternTopicsConsumerImplTest.java:618)
  	at org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53)
  	at org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:248)
  	at org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:235)
  	... 4 more

Root cause: If the new topic is created before the consumer's topic list watcher is connected, the watcher cannot accept the notifications of new topic creation.
Modifications

Make new topics creation start after the consumer's topic list watcher is connected
Since the config subscriptionPatternMaxLength's default value is 50, the pattern name in the test might be too long. So set subscriptionPatternMaxLength to a larger value.

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: x

Codecov Report

Merging #21222 (4d7378c) into master (66271e3) will increase coverage by 0.46%.
Report is 1 commits behind head on master.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #21222      +/-   ##
============================================
+ Coverage     72.73%   73.20%   +0.46%
- Complexity    32465    32479      +14
============================================
  Files          1875     1887      +12
  Lines        139929   140118     +189
  Branches      15413    15426      +13
============================================
+ Hits         101781   102570     +789
+ Misses        30067    29457     -610
- Partials       8081     8091      +10

Flag
Coverage Δ

inttests
24.18% <ø> (+0.01%)
:arrow_up:

systests
24.74% <ø> (?)

unittests
72.51% <ø> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 154 files with indirect coverage changes


I want to add no.of forks , issues, stars in readme file .

I want to add no. of forks, issues, stars in the readme file.
Example:

I want to work on this Please assign me this issue.

Go ahead
Deadline 29 April,2021


Fix parser shift reduce conflict

Building outputs these warnings:
Warning: 3 states have shift/reduce conflicts.
Warning: 14 shift/reduce conflicts were arbitrarily resolved.

The --dump and --explain flags with the menhir CLI generates files with detailed explanations which will help with this.


added DNSTypeNAPTR and DNSType65

I observed many Unknown DNSTypes using gopacket.NewDecodingLayerParser(). As I drilled down I found those Unknown's belong to RR's which are detected by ISC BIND as NAPTR and TYPE65.

@googlebot I signed it!


fix: move to stricter linting configuration

:tada: This PR is included in version 12.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add config option to fix bad UX with Next.js static pre-rendering.

Context
Next.js static pre-renders any page not doing SSR. During pre-rendering on the server, route parameters are empty (because there's no request). For example, a dynamic page like /products/[productId].tsx will be rendered with query.productId === undefined.
Problem 1
useQuery will call the query function during pre-rendering, on the server, which will usually cause noisy but harmless error logs (but they are alarming if you don't know exactly what's happening here).
Workaround: If typeof window === 'undefined', pass a never resolving promise instead of the real query function.
Problem 2
Because the page was statically rendered with empty route params, Next.js will make the first render on the client also have empty route params (otherwise React complains). And it's very common to use a route parameter with useQuery.
So now we have a problem because on the first render useQuery will call your query function which has invalid parameters (route parameter is undefined instead of string, for example). And so this causes noisy but harmless error logs (but they are alarming if you don't know exactly what's happening here).
Workaround: If the router is not ready, pass a never resolving promise instead of the real query function AND use a bogus query key.
You can see in the blitz code how we are currently using both workarounds.
Proposed Solution
At first glance, the enabled config flag seems like the answer. However, that doesn't work because in concurrent mode, useQuery does not throw when enabled = false.
So we need a new config flag similar to enabled that let's us disable the query function being called but while still throwing the loading promise.
Alternate solution: Change the current behavior so that useQuery always throws even if enabled = false.
Additional context
Earlier discussion about this problem: https://github.com/tannerlinsley/react-query/issues/744

So are you currently passing a never resolving promise for `typeof window === 'undefined'?

Are you currently fixing this by passing a never resolving promise when `typeof window === 'undefined'?

@tannerlinsley I'm doing that, but that only solves Problem 1, not Problem 2.

When a query is disabled initially, it does have an isIdle state. Are you able to utilize that somehow to just render nothing until the parameters eventually resolve?

No, because we want to render the suspense fallback, not something else.

@flybayer Did you have any ideas on how to fix this in RQ?

@tannerlinsley yes, in my original post.

So we need a new config flag similar to enabled that let's us disable the query function being called but while still throwing the loading promise.
Alternate solution: Change the current behavior so that useQuery always throws even if enabled = false.

Throw Loading Promise
Execute Query

enabled === false
❌
❌

queryEnabled === false
✅
❌

My personal preference would be not add a new flag but instead change current behavior to always throw promise if enabled = false and suspense = true.

Yeah, I think I'm on your side with this one. Can you think of any downsides to this? Any expectations where people would expect enabled = false to not throw in suspense? This basically means that enabled doesn't really work in suspense at all...

My personal preference would be not add a new flag but instead change current behavior to always throw promise if enabled = false and suspense = true.

I would also not prefer a new flag, as there are quite many already :)

This basically means that enabled doesn't really work in suspense at all...

If I understood this correctly, it would still "work", it would just always render the Suspense fallback if you set enabled=false. Not sure what people are currently rendering when a query is disabled, but if you want a differentiation between disabled and loading, you wouldn't get it. Personally, our dependent queries render a loading spinner anyways if they are disabled because they wait for some data, so 🤷 .
Middle ground would be to enhance the enabled boolean to true | false | 'someString' - I think that would still be better than an extra flag :)

Let’s just have it suspend all the time then. Suspense is experimental so I’m not too concerned about it

Sweet. And yeah if you don't want it to suspend, simply set suspense: false

Wanna PR that Brandon?

Yeah, but too busy! 😅

What if you have two queries in a suspense component and one of them is conditional? If the conditional query would throw a never resolving promise, then the component would never render? Think the custom useQuery hook is a pretty good solution :)

This is still an interesting edge case, but one that I haven't seen anywhere in the wild other than blitz, and it looks like @flybayer was able to work around it on his end. With that in mind, I think we can just leave it up to @flybayer to propose a fix if and when he finds the time.

This is still an interesting edge case, but one that I haven't seen anywhere in the wild other than blitz, and it looks like @flybayer was able to work around it on his end. With that in mind, I think we can just leave it up to @flybayer to propose a fix if and when he finds the time.

@flybayer
I am facing the same issue. Do you have a code snippet of your workaround at hand?


LRS Demo Cloudformation Templates

VPC
Postgres DB
Credentials Init for PG DB using Custom Resource Lambda
App Server, with service def, version param, etc
LB
SSL/Cert and Domain Updates

Consider putting an output on the LRS template with the uri of the admin interface!

Consider putting an output on the LRS template with the uri of the admin interface!

So I did consider it. The reason i didn't is its literally directly an input of the stack and it felt weird to spit back a param. I can do it though i guess it could be handy.

Keyname should be optional, for nice no-access instances

this is done.

Consider putting an output on the LRS template with the uri of the admin interface!

done!


Remove trailing spaces and add final newlines

And introduce Editorconfig.
I hope your IDE supports it (maybe through a plugin)

Thank you.

Glad to contribute.


Update LCR link to LCR specific guidance

The Liverpool City Region has additional guidance on top of the base very high guidance. The base guidance does not link to the LCR page, but the LCR page does link to the base page, so I think it makes sense to link to the specific page first.

I'm not sure if these links are actually used; as LCR is the only very high region at present, you could also change the link in https://github.com/alphagov/collections/blob/929ca08d377956ea7d64d997c426c13c34d3a493/config/locales/en/lookup.yml#L43 as an alternative, if that's the link being shown at present.

Yes, it looks like you'd need to use @restriction.guidance.link in the tier three template (at the least) rather than the lookup.yml string used at present for the change in this PR to do anything. Happy to adjust to either change lookup.yml or change template to use the link from the data, once someone confirms which would be the better approach (or if you've not already done it).

👋  Thanks @dracos, I've flagged this with the team.

Have rebased on current master, and adjusted the lookup.yml link instead, as the other links have been removed. This would work until more areas went into VH tier, and so would presumably provide more accurate guidance right now than the current result.
Another solution if this is not wanted would be to have a note on the baseline VH guidance linking to the Liverpool guidance, that would perhaps be easier to implement?

Any news? A postcode lookup in Liverpool still does not return any Liverpool specific guidance, it still links to https://www.gov.uk/guidance/local-covid-alert-level-very-high without mentioning https://www.gov.uk/guidance/local-covid-alert-level-very-high-liverpool-city-region even though https://www.gov.uk/guidance/local-covid-alert-levels-what-you-need-to-know#local-covid-alert-level-very-high literally says "You should therefore check whether additional restrictions apply in your area" linking to the postcode lookup.

Hi @dracos! Thanks for your suggestion.
Currently the guidance for each level (medium, high, very high) links to a single page that then links to the extra restrictions for an area.
As more areas move into very high restrictions, we’re looking into to the best way to show the extra restrictions specific to an area whilst keeping the user journey as simple as possible. At the moment we’re looking at how better to do this in the content for each level, rather than in the postcode checker itself.
As part of this work we've looked at the guidance for the “extra” restrictions, which shows it is not as useful as the very high guidance, so for now we don't think it's the best journey to link to that through the checker. But we will continue to monitor feedback.

Thanks for the reply. Think this is out of date now anyway.


Resolve: store repost's original channel too

Issue

Closes #1535 bunch of channels (from featured?) resolved on page load
It was due to the use of reposts in the Category. As we did not store the repost's original channel claim, ChannelThumbnail couldn't find the author and requested a separate resolve.

Change
Store the repost's original channel claim as well.

Ah duh, that totally escaped me. Thank you!


tests, integ: Test MTU change with two VLAN/s

Define two VLAN/s over a shared base interface and edit their MTU.
The transaction fails and therfore marked as xfail.
Ref: https://bugzilla.redhat.com/1751079

Coverage remained the same at ?% when pulling 5f47419d617769684feb2443cea2368ad3871c6a on EdDev:test-mtu-with-two-vlans into 0ef2e0f151661bc2bf981099a33c540a571111c6 on nmstate:master.

Thanks @cathay4t , done.


Update patchYamlJsonPackage.js to handle paths with spaces in applyPatch

Problem
When language-servers is checked out under a directory that contains spaces in the full path, npm install will fail to complete due to patchYamlJsonPackage.js.
Solution
This commit fixes this issue by ensuring file paths are quoted to support spaces in them.
Testing
Ensured npm install succeeds in a directory with spaces in the full path (i.e. under a user's Application Support folder for Sublime Text on OS X).
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This is a continuation of https://github.com/aws/language-servers/pull/258.

I've once again created the PR: https://github.com/aws/language-servers/pull/270

I've once again created the PR: #270

Why? That loses the PR comments. Please just force-push to your existing branch instead of creating new PRs.


PHP Fatal error:  Class 'Pool' not found in /srv/twitchbot/console-cli-thread.php on line 73

Hey there, I've set everything up as described and I'm getting the following error:

PHP Fatal error:  Class 'Pool' not found in /srv/twitchbot/console-cli-thread.php on line 73
Fatal error: Class 'Pool' not found in /srv/twitchbot/console-cli-thread.php on line 73

I can't find the class 'Pool' anywhere, am I missing some not mentioned requirements?

Hi,
sorry it is a very basic alpha release on github. I had not have time to upload the "final" version, which I have currently running.
The readme is also quite old, currently there are missing requirements:

https://github.com/krakjoe/pthreads


Multiple message callbacks for listen (close #525)

Now we can call several times listen to use more than one callbacks
Also close #525

Is very good idea ! :D

Hi @Vinetos, thanks for contributing! As I said in #525, I'm not convinced this is necessary -- this functionality can be very easily accomplished in user code.
Is there a use case that I'm missing that is impossible/hard to accomplish without this change?

See also my example in https://github.com/Schmavery/facebook-chat-api/issues/525#issuecomment-329016053

Closing as explained in #525, feel free to comment if you have any issues.


Language Detection

PR for the issue #29.

Adds LanguageLogitsFilter that suppresses non-language logits
Implements detectLanguage in TextDecoder that does a single forward pass from <startoftranscript> to get the language token
Adds tests for LanguageLogitsFilter

Added a couple CI fixes here FYI @Abhinay1997 should be in a working state now

Thanks for the feedback ! Yes, let me add tests for Spanish and Japanese. Will need to look into the filtering time !

@ZachNagengast, for comparing the detection with and without logits filter, I'll add a applyFilter param to detectLanguage then ? To toggle it on and off.

The filter adds only 2.9802322387695312e-06 seconds. Negligible imo


GH Actions Experiment

Core - Full Integration Build 9522 outcome was UNKNOWN using a merge of 93e813fe25224053287a9d95bdb63b8befee6011
Summary: Canceled (Tests passed: 5130, ignored: 79; exit code 143 (Step: Build & test full (Maven)) (new)) Build time: 01:29:41

Core - Full Integration Build 9517 outcome was UNKNOWN using a merge of 1c1cb6812cb59637f9f1607dbcd2dd405b47328d
Summary: Canceled (Exit code 143 (Step: Build & test full (Maven)) (new)) Build time: 00:06:48

Core - Full Integration Build 9524 outcome was UNKNOWN using a merge of 1c1cb6812cb59637f9f1607dbcd2dd405b47328d
Summary: Canceled (Tests passed: 458, ignored: 7; exit code 143 (Step: Build & test full (Maven)) (new)) Build time: 00:06:52

Core - Full Integration Build 9525 outcome was UNKNOWN using a merge of 557bd53022a702817dbde879b04630eec990f237
Summary: Canceled (Exit code 143 (Step: Build & test core (Maven)) (new)) Build time: 00:00:45

Core - Full Integration Build 9518 outcome was UNKNOWN using a merge of 557bd53022a702817dbde879b04630eec990f237
Summary: Canceled (Exit code 143 (Step: Build & test core (Maven)) (new)) Build time: 00:00:45

Core - Full Integration Build 9519 outcome was UNKNOWN using a merge of 58a7c36c1ab9543d8c06c263f1ce1d4e0dace34f
Summary: Canceled (Error while applying patch; cannot find commit 58a7c36c1ab9543d8c06c263f1ce1d4e0dace34f in the https://github.com/wildfly/wildfly-core.git repository, possible reason: refs/pull/4155/head branch was updated and the commit selected for the b... Build time: 00:00:06

Core - Full Integration Build 9526 outcome was UNKNOWN using a merge of 58a7c36c1ab9543d8c06c263f1ce1d4e0dace34f
Summary: Canceled (Error while applying patch; cannot find commit 58a7c36c1ab9543d8c06c263f1ce1d4e0dace34f in the https://github.com/wildfly/wildfly-core.git repository, possible reason: refs/pull/4155/head branch was updated and the commit selected for the b... Build time: 00:00:13