Failed to create the APK. libreactskia.so', missing and no known rule to make

Description
I can't produce the android binary
Version
v0.1.158-alpha
Steps to reproduce
yarn bootstrap && cd example
--
➜  example git:(35248873) yarn e2e:build:android
yarn run v1.22.19
warning ../../../../package.json: No license field
$ owl build -p android
[OWL - CLI] Building the app on android platform.
> Task :react-native-gradle-plugin:compileKotlin UP-TO-DATE
> Task :react-native-gradle-plugin:compileJava NO-SOURCE
> Task :react-native-gradle-plugin:pluginDescriptors UP-TO-DATE
> Task :react-native-gradle-plugin:processResources UP-TO-DATE
> Task :react-native-gradle-plugin:classes UP-TO-DATE
> Task :react-native-gradle-plugin:inspectClassesForKotlinIC UP-TO-DATE
> Task :react-native-gradle-plugin:jar UP-TO-DATE

> Configure project :react-native-reanimated
AAR for react-native-reanimated has been found
/home/grigio/Code/testing/react-native-skia/example/node_modules/react-native-reanimated/android/react-native-reanimated-70-hermes.aar

> Configure project :shopify_react-native-skia
react-native-skia: node_modules/ found at: /home/grigio/Code/testing/react-native-skia/example/node_modules/@shopify/react-native-skia/node_modules
react-native-skia: React Native version: 70
react-native-skia: Is Source build: false
react-native-skia: Prebuilt dir: /home/grigio/Code/testing/react-native-skia/example/node_modules/@shopify/react-native-skia/android/build/react-native-0*/jni
react-native-skia: Build type: debug

> Task :app:bundleReleaseJsAndAssets
warning: the transform cache was reset.
                Welcome to Metro v0.72.3
              Fast - Scalable - Integrated

info Writing bundle output to:, /home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle
info Writing sourcemap output to:, /home/grigio/Code/testing/react-native-skia/example/android/app/build/intermediates/sourcemaps/react/release/index.android.bundle.packager.map
info Done writing bundle output
info Done writing sourcemap output
info Copying 16 asset files
info Done copying assets
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:847:27: warning: the variable "Promise" was not declared in anonymous function " 26#"
    return new (P || (P = Promise))(function (resolve, reject) {
                          ^~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:1060:7: warning: the variable "clearTimeout" was not declared in anonymous function " 34#"
      clearTimeout(automateTimeout);
      ^~~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:1061:25: warning: the variable "setTimeout" was not declared in anonymous function " 34#"
      automateTimeout = setTimeout(function () {
                        ^~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:1185:13: warning: the variable "clearInterval" was not declared in anonymous function " 43#"
            clearInterval(checkInterval);
            ^~~~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:1188:31: warning: the variable "setInterval" was not declared in anonymous function " 42#"
          var checkInterval = setInterval(function () {
                              ^~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:2876:23: warning: the variable "DebuggerInternal" was not declared in function "__shouldPauseOnThrow"
        return typeof DebuggerInternal !== 'undefined' && DebuggerInternal.shouldPauseOnThrow === true;
                      ^~~~~~~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:9681:30: warning: the variable "__REACT_DEVTOOLS_GLOBAL_HOOK__" was not declared in anonymous function " 150#"
  if ("undefined" !== typeof __REACT_DEVTOOLS_GLOBAL_HOOK__) {
                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:9699:146: warning: the variable "nativeFabricUIManager" was not declared in anonymous function " 179#"
    null != handle._nativeTag && (null != handle._internalInstanceHandle ? (handle = handle._internalInstanceHandle.stateNode, null != handle && nativeFabricUIManager.dispatchCommand(handle.node, command, args)) : _$$_REQUIRE(_dependencyMap[2]).UIManager.dispatchViewManagerCommand(handle._nativeTag, command, args));
                                                                                ^~~~~~~~~~~~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:10670:5: warning: the variable "setImmediate" was not declared in function "handleResolved"
    setImmediate(function () {
    ^~~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:14591:12: warning: the variable "fetch" was not declared in anonymous function " 373#"
    fetch: fetch,
           ^~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:14592:14: warning: the variable "Headers" was not declared in anonymous function " 373#"
    Headers: Headers,
             ^~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:14593:14: warning: the variable "Request" was not declared in anonymous function " 373#"
    Request: Request,
             ^~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:14594:15: warning: the variable "Response" was not declared in anonymous function " 373#"
    Response: Response
              ^~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:14770:24: warning: the variable "FileReader" was not declared in function "readBlobAsArrayBuffer"
      var reader = new FileReader();
                       ^~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:14815:36: warning: the variable "Blob" was not declared in anonymous function " 384#"
        } else if (support.blob && Blob.prototype.isPrototypeOf(body)) {
                                   ^~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:14817:40: warning: the variable "FormData" was not declared in anonymous function " 384#"
        } else if (support.formData && FormData.prototype.isPrototypeOf(body)) {
                                       ^~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:14819:44: warning: the variable "URLSearchParams" was not declared in anonymous function " 384#"
        } else if (support.searchParams && URLSearchParams.prototype.isPrototypeOf(body)) {
                                           ^~~~~~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:15096:23: warning: the variable "XMLHttpRequest" was not declared in anonymous function " 393#"
        var xhr = new XMLHttpRequest();
                      ^~~~~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:14603:76: warning: the variable "self" was not declared in anonymous function " 376#"
    var global = typeof globalThis !== 'undefined' && globalThis || typeof self !== 'undefined' && self || typeof global !== 'undefined' && global;
                                                                           ^~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:23228:27: warning: the variable "performance" was not declared in anonymous function " 541#"
  if ("object" === typeof performance && "function" === typeof performance.now) {
                          ^~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:23254:26: warning: the variable "navigator" was not declared in anonymous function " 541#"
  "undefined" !== typeof navigator && undefined !== navigator.scheduling && undefined !== navigator.scheduling.isInputPending && navigator.scheduling.isInputPending.bind(navigator.scheduling);
                         ^~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:23334:37: warning: the variable "MessageChannel" was not declared in anonymous function " 541#"
  };else if ("undefined" !== typeof MessageChannel) {
                                    ^~~~~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:32007:32: warning: the variable "requestAnimationFrame" was not declared in function "onUpdate"
        this._animationFrame = requestAnimationFrame(this.onUpdate.bind(this));
                               ^~~~~~~~~~~~~~~~~~~~~
/home/grigio/Code/testing/react-native-skia/example/android/app/build/generated/assets/react/release/index.android.bundle:45715:18: warning: the variable "WebSocket" was not declared in function "initWebSocket"
    var ws = new WebSocket("ws://" + ipAddress + ":" + _$$_REQUIRE(_dependencyMap[1]).WEBSOCKET_PORT);
                 ^~~~~~~~~

> Task :app:generatePackageList
> Task :app:preBuild
> Task :app:preReleaseBuild
> Task :react-native-owl:preBuild UP-TO-DATE
> Task :react-native-owl:preReleaseBuild UP-TO-DATE
> Task :react-native-owl:compileReleaseAidl NO-SOURCE
> Task :react-native-safe-area-context:preBuild UP-TO-DATE
> Task :react-native-safe-area-context:preReleaseBuild UP-TO-DATE
> Task :react-native-safe-area-context:compileReleaseAidl NO-SOURCE
> Task :react-native-screens:preBuild UP-TO-DATE
> Task :react-native-screens:preReleaseBuild UP-TO-DATE
> Task :react-native-screens:compileReleaseAidl NO-SOURCE
> Task :shopify_react-native-skia:preBuild UP-TO-DATE
> Task :shopify_react-native-skia:preReleaseBuild UP-TO-DATE
> Task :shopify_react-native-skia:compileReleaseAidl NO-SOURCE
> Task :app:compileReleaseAidl NO-SOURCE
> Task :react-native-owl:packageReleaseRenderscript NO-SOURCE
> Task :react-native-safe-area-context:packageReleaseRenderscript NO-SOURCE
> Task :react-native-screens:packageReleaseRenderscript NO-SOURCE
> Task :shopify_react-native-skia:packageReleaseRenderscript NO-SOURCE
> Task :app:compileReleaseRenderscript NO-SOURCE
> Task :app:generateReleaseBuildConfig UP-TO-DATE
> Task :app:javaPreCompileRelease UP-TO-DATE
> Task :react-native-owl:writeReleaseAarMetadata UP-TO-DATE
> Task :react-native-safe-area-context:writeReleaseAarMetadata UP-TO-DATE
> Task :react-native-screens:writeReleaseAarMetadata UP-TO-DATE
> Task :shopify_react-native-skia:writeReleaseAarMetadata UP-TO-DATE
> Task :app:checkReleaseAarMetadata UP-TO-DATE
> Task :app:generateReleaseResValues UP-TO-DATE
> Task :app:mergeReleaseShaders UP-TO-DATE
> Task :app:compileReleaseShaders NO-SOURCE
> Task :app:generateReleaseAssets UP-TO-DATE
> Task :react-native-owl:mergeReleaseShaders UP-TO-DATE
> Task :react-native-owl:compileReleaseShaders NO-SOURCE
> Task :react-native-owl:generateReleaseAssets UP-TO-DATE
> Task :react-native-owl:packageReleaseAssets UP-TO-DATE
> Task :react-native-safe-area-context:mergeReleaseShaders UP-TO-DATE
> Task :react-native-safe-area-context:compileReleaseShaders NO-SOURCE
> Task :react-native-safe-area-context:generateReleaseAssets UP-TO-DATE
> Task :react-native-safe-area-context:packageReleaseAssets UP-TO-DATE
> Task :react-native-screens:mergeReleaseShaders UP-TO-DATE
> Task :react-native-screens:compileReleaseShaders NO-SOURCE
> Task :react-native-screens:generateReleaseAssets UP-TO-DATE
> Task :react-native-screens:packageReleaseAssets UP-TO-DATE
> Task :shopify_react-native-skia:mergeReleaseShaders UP-TO-DATE
> Task :shopify_react-native-skia:compileReleaseShaders NO-SOURCE
> Task :shopify_react-native-skia:generateReleaseAssets UP-TO-DATE
> Task :shopify_react-native-skia:packageReleaseAssets UP-TO-DATE
> Task :app:mergeReleaseAssets UP-TO-DATE
> Task :app:copyReleaseBundledJs UP-TO-DATE
> Task :app:generateReleaseResources UP-TO-DATE
> Task :react-native-owl:compileReleaseRenderscript NO-SOURCE
> Task :react-native-owl:generateReleaseResValues UP-TO-DATE
> Task :react-native-owl:generateReleaseResources UP-TO-DATE
> Task :react-native-owl:packageReleaseResources UP-TO-DATE
> Task :react-native-safe-area-context:compileReleaseRenderscript NO-SOURCE
> Task :react-native-safe-area-context:generateReleaseResValues UP-TO-DATE
> Task :react-native-safe-area-context:generateReleaseResources UP-TO-DATE
> Task :react-native-safe-area-context:packageReleaseResources UP-TO-DATE
> Task :react-native-screens:compileReleaseRenderscript NO-SOURCE
> Task :react-native-screens:generateReleaseResValues UP-TO-DATE
> Task :react-native-screens:generateReleaseResources UP-TO-DATE
> Task :react-native-screens:packageReleaseResources UP-TO-DATE
> Task :shopify_react-native-skia:compileReleaseRenderscript NO-SOURCE
> Task :shopify_react-native-skia:generateReleaseResValues UP-TO-DATE
> Task :shopify_react-native-skia:generateReleaseResources UP-TO-DATE
> Task :shopify_react-native-skia:packageReleaseResources UP-TO-DATE
> Task :app:mergeReleaseResources UP-TO-DATE
> Task :app:mapReleaseSourceSetPaths UP-TO-DATE
> Task :app:createReleaseCompatibleScreenManifests UP-TO-DATE
> Task :app:extractDeepLinksRelease UP-TO-DATE
> Task :react-native-owl:extractDeepLinksRelease UP-TO-DATE
> Task :react-native-safe-area-context:extractDeepLinksRelease UP-TO-DATE
> Task :react-native-owl:processReleaseManifest UP-TO-DATE
> Task :react-native-safe-area-context:processReleaseManifest UP-TO-DATE
> Task :react-native-screens:extractDeepLinksRelease UP-TO-DATE
> Task :react-native-screens:processReleaseManifest UP-TO-DATE
> Task :shopify_react-native-skia:extractDeepLinksRelease UP-TO-DATE
> Task :shopify_react-native-skia:processReleaseManifest UP-TO-DATE
> Task :app:processReleaseMainManifest UP-TO-DATE
> Task :app:processReleaseManifest UP-TO-DATE
> Task :app:processReleaseManifestForPackage UP-TO-DATE
> Task :react-native-owl:compileReleaseLibraryResources UP-TO-DATE
> Task :react-native-owl:parseReleaseLocalResources UP-TO-DATE
> Task :react-native-owl:generateReleaseRFile UP-TO-DATE
> Task :react-native-safe-area-context:compileReleaseLibraryResources UP-TO-DATE
> Task :react-native-safe-area-context:parseReleaseLocalResources UP-TO-DATE
> Task :react-native-safe-area-context:generateReleaseRFile UP-TO-DATE
> Task :react-native-screens:compileReleaseLibraryResources UP-TO-DATE
> Task :react-native-screens:parseReleaseLocalResources UP-TO-DATE
> Task :react-native-screens:generateReleaseRFile UP-TO-DATE
> Task :shopify_react-native-skia:compileReleaseLibraryResources UP-TO-DATE
> Task :shopify_react-native-skia:parseReleaseLocalResources UP-TO-DATE
> Task :shopify_react-native-skia:generateReleaseRFile UP-TO-DATE
> Task :app:processReleaseResources UP-TO-DATE
> Task :react-native-owl:generateReleaseBuildConfig UP-TO-DATE
> Task :react-native-owl:javaPreCompileRelease UP-TO-DATE
> Task :react-native-owl:compileReleaseJavaWithJavac UP-TO-DATE
> Task :react-native-owl:bundleLibCompileToJarRelease UP-TO-DATE
> Task :react-native-safe-area-context:generateReleaseBuildConfig UP-TO-DATE
> Task :react-native-safe-area-context:compileReleaseKotlin UP-TO-DATE
> Task :react-native-safe-area-context:javaPreCompileRelease UP-TO-DATE
> Task :react-native-safe-area-context:compileReleaseJavaWithJavac UP-TO-DATE
> Task :react-native-safe-area-context:bundleLibCompileToJarRelease UP-TO-DATE
> Task :react-native-screens:generateReleaseBuildConfig UP-TO-DATE
> Task :react-native-screens:compileReleaseKotlin UP-TO-DATE
> Task :react-native-screens:javaPreCompileRelease UP-TO-DATE
> Task :react-native-screens:compileReleaseJavaWithJavac UP-TO-DATE
> Task :react-native-screens:bundleLibCompileToJarRelease UP-TO-DATE
> Task :shopify_react-native-skia:generateReleaseBuildConfig UP-TO-DATE
> Task :shopify_react-native-skia:javaPreCompileRelease UP-TO-DATE
> Task :shopify_react-native-skia:compileReleaseJavaWithJavac UP-TO-DATE
> Task :shopify_react-native-skia:bundleLibCompileToJarRelease UP-TO-DATE
> Task :app:compileReleaseJavaWithJavac UP-TO-DATE
> Task :app:extractProguardFiles UP-TO-DATE
> Task :react-native-owl:processReleaseJavaRes NO-SOURCE
> Task :react-native-owl:bundleLibResRelease NO-SOURCE
> Task :react-native-owl:bundleLibRuntimeToJarRelease UP-TO-DATE
> Task :react-native-owl:createFullJarRelease UP-TO-DATE
> Task :react-native-owl:writeReleaseLintModelMetadata UP-TO-DATE
> Task :react-native-safe-area-context:processReleaseJavaRes NO-SOURCE
> Task :react-native-safe-area-context:bundleLibResRelease UP-TO-DATE
> Task :react-native-safe-area-context:bundleLibRuntimeToJarRelease UP-TO-DATE
> Task :react-native-safe-area-context:createFullJarRelease UP-TO-DATE
> Task :react-native-safe-area-context:writeReleaseLintModelMetadata UP-TO-DATE
> Task :react-native-screens:processReleaseJavaRes NO-SOURCE
> Task :react-native-screens:bundleLibResRelease UP-TO-DATE
> Task :react-native-screens:bundleLibRuntimeToJarRelease UP-TO-DATE
> Task :react-native-screens:createFullJarRelease UP-TO-DATE
> Task :react-native-screens:writeReleaseLintModelMetadata UP-TO-DATE
> Task :shopify_react-native-skia:processReleaseJavaRes NO-SOURCE
> Task :shopify_react-native-skia:bundleLibResRelease NO-SOURCE
> Task :shopify_react-native-skia:bundleLibRuntimeToJarRelease UP-TO-DATE
> Task :shopify_react-native-skia:createFullJarRelease UP-TO-DATE
> Task :shopify_react-native-skia:extractAARHeaders
> Task :shopify_react-native-skia:extractJNIFiles
> Task :shopify_react-native-skia:configureCMakeRelWithDebInfo[arm64-v8a]

> Task :shopify_react-native-skia:buildCMakeRelWithDebInfo[arm64-v8a] FAILED
C/C++: ninja: error: '../../../../../libs/android/arm64-v8a/libsvg.a', needed by '../../../../build/intermediates/cxx/RelWithDebInfo/1j2u5p3w/obj/arm64-v8a/libreactskia.so', missing and no known rule to make it

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':shopify_react-native-skia:buildCMakeRelWithDebInfo[arm64-v8a]'.
> Build command failed.
  Error while executing process /home/grigio/Android/Sdk/cmake/3.18.1/bin/ninja with arguments {-C<EMAIL_ADDRESS>reactskia}
  ninja: Entering directory<EMAIL_ADDRESS>
  ninja: error: '../../../../../libs/android/arm64-v8a/libsvg.a', needed by '../../../../build/intermediates/cxx/RelWithDebInfo/1j2u5p3w/obj/arm64-v8a/libreactskia.so', missing and no known rule to make it

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

2: Task failed with an exception.
-----------
* What went wrong:
java.lang.StackOverflowError (no error message)

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

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

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 57s
99 actionable tasks: 6 executed, 93 up-to-date
Error: Command failed with exit code 1: ./gradlew assembleRelease --console plain -PisOwlBuild=true
    at makeError (/home/grigio/Code/testing/react-native-skia/example/node_modules/react-native-owl/node_modules/execa/lib/error.js:60:11)
    at handlePromise (/home/grigio/Code/testing/react-native-skia/example/node_modules/react-native-owl/node_modules/execa/index.js:118:26)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  shortMessage: 'Command failed with exit code 1: ./gradlew assembleRelease --console plain -PisOwlBuild=true',
  command: './gradlew assembleRelease --console plain -PisOwlBuild=true',
  escapedCommand: '"./gradlew" assembleRelease --console plain "-PisOwlBuild=true"',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: undefined,
  stderr: undefined,
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}

Specify --help for available options
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Snack, code example, screenshot, or link to a repository
.

Ok, but I'd like to test and build the example app APK on Linux, how can I do it?
I changed the example app to make it a normal app but I still have the same errors
from
    "@shopify/react-native-skia": "link:../package/",

to
    "@shopify/react-native-skia": "v0.1.158 alpha",

Hi, @grigio - I would suggest you try the following steps to get started:

Create a new React Native App (forget about the example app for now) (build and verify that your environment is correct)
Install @shopify/react-native-skia (build and verify that your environment is correct)
Copy code from the example and have fun with Skia :)

If you have problems in step 2 you are welcome to ask for help here - if you have problems in step 1 you should visit the react-native repo / stack overflow to get help and advise.

Hello, i am having same issue all of sudden, I am not running example folder.
`


How to disable spyder main window from coming on top when clicked on spyder editor window

Description of your problem
I am using two monitors. One for spyder main window and one for spyder editor window. I would like to use the monitor with spyder main window for other applications as well, such as Notepad++ or google chrome to see other codes, and at the same time write my code in the spyder editor on the second screen. But, whenever I click on the spyder editor, it brings the spyder main window on top as well. Is there any way to disable this?
What steps will reproduce the problem?

Open spyder, undock editor and place it in second monitor
Open any other application (such as Notepad++) on first monitor, so the spyder main window is behind the current application
click on spider editor. You will see that the spyder main window will come on top hiding the other application(Notepad++)

What is the expected output? What do you see instead?
Please provide any additional information below
Versions and main components

Spyder Version:3.1.4
Python Version:3.5.2
Qt Version:
PyQt Version:
Operating system: Windows 7 (64bit)

Dependencies
Please go to the menu entry Help > Optional Dependencies (or
Help > Dependencies), press the button Copy to clipboard
and paste the contents below:
jedi >=0.9.0     :  0.10.2 (OK)
matplotlib >=1.0 :  1.5.3 (OK)
nbconvert >=4.0  :  5.1.1 (OK)
numpy >=1.7      :  1.11.3 (OK)
pandas >=0.13.1  :  0.19.2 (OK)
pep8 >=0.6       :  1.7.0 (OK)
pyflakes >=0.6.0 :  1.5.0 (OK)
pygments >=2.0   :  2.2.0 (OK)
pylint >=0.25    :  1.7.1 (OK)
qtconsole >=4.2.0:  4.3.0 (OK)
rope >=0.9.4     :  0.9.4-1 (OK)
sphinx >=0.6.6   :  1.5.5 (OK)
sympy >=0.7.3    :  None (NOK)

Is there any way to disable this?

None I'm aware of. But we'll take a look at it to see if we can improve the situation in Spyder 4.
Sorry for the inconveniences in the meantime.


Remove old build system and associated tools

Don't look at this until #3106 is merged.  Then this can be insta-merged because it will just be a delete of ant and other files associated with the old build process that are no longer needed.

I guess you need to update this PR with the tweaks from the gulp PR?  More diffs here than just the deletions.

I cleaned everything up and did a force push, this is ready.  Thanks for all of the help @shunter!


[Updated] UserTestimonial.js | Solved Issue #2444

I have updated the user testimonials.js file & added a feature solving the issue https://github.com/EddieHubCommunity/LinkFree/issues/2444. You can review it accordingly.
Fixes Issue
Closes https://github.com/EddieHubCommunity/LinkFree/issues/2444
Changes proposed
Check List (Check all the applicable boxes)
[ X ] My code follows the code style of this project.
[ X ] My change requires changes to the documentation.
[ X ] I have updated the documentation accordingly.
[ X ] All new and existing tests passed.
[ X ] This PR does not contain plagiarized content.
[ X ] The title of my pull request is a short description of the requested changes.
Note to reviewers
I have reviewed all the changes & the update feature works fine. So you can add it to the deployment without any hesitation.

@adityassharma-ss thank you for requesting a review from me. Please see my inline comments first


[BUG] !IMPORTANT! - Bot allows multiple submissions for SAME daily problem.

People can submit a solution multiple times for the problem of the day. THIS IS BAD.

This can be remedied with a boolean attribute for users in the participant data that is reset daily.


Support for Laravel facade classes

I'm running phan on a Laravel 4.2 code base and I'm getting tons of output like:
PhanUndeclaredClassMethod Call to method table from undeclared class \DB
In this case, DB is a Laravel facade. I can understand why phan is complaining about this since these "facades" are magical in the way they're implemented. Has anyone else experienced this and maybe found a workaround?

Is DB in the root namespace? This class is not. Maybe a return type is incorrect somewhere?
Unless Laravel is creating classes on the fly, a la Mockery, in which case phan would need a special way of handling that.

It's not creating the classes on the fly; it is creating class aliases on the fly: https://github.com/laravel/framework/blob/4.2/src/Illuminate/Foundation/AliasLoader.php#L64

@ebernhardson One thing you could do would be to create a .phan/stubs directory where you could drop files that contain the interfaces that aren't otherwise accessible, and then add the stubs directory to the directory_list in your .phan/config.php file.
I wrote up a wiki article on this with some more details.

Sounds like Laravel IDE helper might be handy for generating the stubs file. https://github.com/barryvdh/laravel-ide-helper

I add stub/_ide_helper.php and modified .phan/config.php accordingly. It fixed the problem. Thank you for the help gentleman.

@berndlosert this is quite old but could you share your configuration with me? this isn't working for me somehow i'm not sure what i'm doing wrong.

FWIW (@yazfield, @zelazowy) this seems to work for me:
    'exclude_analysis_directory_list' => [
        'vendor',
        '.phan/stubs',       // <<< ADD IT HERE
    ],
    'directory_list' => [
        'app',
        'bootstrap',
        'config',
        'database',
        'public',
        'routes',
        'tests',
        'vendor',
        '.phan/stubs',       // <<< AND HERE
    ],

It does require the _ide_helper.php generated by the helper to be in .phan/stubs instead of the project root (which is the default).  For now, I'm just symlinking things so I don't need to change my work flow too much.


[DOCS] useSignal is undocumented

useSignal should be documented, remember to check #1729
when fully documented, the tutorial should update to use useSignal #1810
including:

useRef
synchronous events

synchronous events tutorial is updated #2112

All tutorials have been updated. Only missing documentation.

We have useSignal() docs now!


Wed. Aug. 24th ⚡ 📻  the Show Notes

The next episode of FullStackLA live is here, with @kpearson & @machikoyasuda, brought to you by @MaxCDN / StackPath - thanks to our favorite @jdorfman :octocat:
This week, we have a special local guest, developer & OSS contributor @eirinikos of Los Angeles, a local @homebrew 🍻  💎  contributor in the Ruby language. She will be talking about her summer as a fellow for Outreachy.
The local meetup forecast ☀ ⛅

Event Pick of the Month: 8th Light: SCNA, apply for the scholarship for their conference coming up at USC in October: http://scna.softwarecraftsmanship.com/opportunity/
Chat Guest: Our virtual mentor of the night will be @gr2m. You can chat with him via Slack. Start here: http://hood.ie/chat/
Anything else to add? Add a link in the comments.

Tonight's show

7 🕖  Stand Up
8 🕗  Talk on Homebrew by @eirinikos https://github.com/fullstackla/pairing-meetup/issues/62
✨  Pairing Time ✨
9 🕘   And there's always more for the hungry folks! Poquito Mas.js @ Poquito Mas 🍴

A word from our sponsors:

@MaxCDN is now StackPath.

Upcoming

September edition of Fullstack: We will have local developer & OSS contributor @gyllen from @mapillary, speaking about @Netflix's library, Falcor. Netflix. Ever heard of it? 📺  Got any burning questions for @gyllen already about it? Get in on the discussion here: https://github.com/fullstackla/pairing-meetup/issues/73

Over and out ⚡

+1 @benjaminma HTML/CSS/JavaScript

@lenkli67 Ruby/ JavaScript/ HTML/ CSS

@kennethlee da Jay Ess.

@thomasjinlo Ruby

+1 @leighphan HTML, CSS, JavaScript

Python, R, C++, (maybe Java, HTML/CSS)

@dmacstack Ruby, PHP, JavaScript, HTML, CSS

Majan ... PHP, JS ... never done ruby ... but i am down to learn...!!

+1 @xuhdev Python / HTML / CSS / C++

Swift, Objective-C

@jaimemendozadev and I can do either Ruby or JavaScript ( probably 😉 )

@jdorfman | markdown, json | https://github.com/jdorfman/awesome-json-datasets/issues/12

@IanDCarroll HTML/CSS/JS, Python, whatever

@xuhdev would like to share a tool he uses with firefox: Vimperator: http://www.vimperator.org/vimperator
Also, a rad blog about open source: https://www.topbug.net/blog/2016/08/19/why-is-open-source-beneficial-for-economic-growth-in-the-long-run/

Michael @server-monitor bash, Ruby, Perl, JavaScript, Python, HTML, CSS, would like to learn more Elixir and Go.

@IanDCarroll idea: maybe one day we can convert these show notes into "Awesome lists"

"Awesome lists?" I do not understand awesome. Can you explain it?
Also: another contribution: @xuhdev wrote about pairing on the map project: https://www.topbug.net/blog/2016/08/27/optimization-for-mobile-a-pair-programming-story-at-fullstackla/

@IanDCarroll https://github.com/sindresorhus/awesome


Switch to IMDb Py instead of TMDB

I think everyone would prefer movie data being fetched from IMDB, instead of TMDB. And IMDb Py can do just that. I already implemented IMDB rating in #268. If that req is accepted, I can move further for a transition to IMDb Py. IMDbPy can fetch everything that IMDB has to offer.
Sent from my Xiaomi MI 5 using FastHub

Sounds good. It would be better to get everything from a single source than from two.

@ahmedsadman Are you still working on this?

@aviral1701 I am willing to, but the main developer hasn't given any consent. It's tagged as Suggestion
Sent from my Xiaomi MI 5 using FastHub

I say go for it. @swapagarwal gave you a thumbs up in the first post, which I think is a green light to go ahead and code it.

Sounds great. But I need some good amount of time for academics purpose. I think I can start at the end of this month

@ahmedsadman Sure, go ahead! Let us know if you're working on this; or would like someone else to pick it up. 😄

Sorry for the late reply. I was busy with academics. I think it would be better if someone else picks up the work


add chinese mirrors

for chinese users who can't access github correctly, I made a mirror page on https://gitee.com/dawn_magnet/zimfw and https://gitee.com/dawn_magnet/zimfw-install and I changed its source from github to a chinese substitute called gitee. I wish to add an helpful link to the main page so chinese users can access the cn download script and chinese version of readme.

Hi @DawnMagnet. Thank you for taking the time to translate our README to Chinese!
I'd like to avoid having documentation that makes users run a shell script that's outside our organization repos though.
I'm wondering, do any of the following URLs work in China?

https://github.com/zimfw/zimfw/releases/latest/download/zimfw.zsh.gz
https://api.github.com/repos/zimfw/zimfw/tarball/master

Hi @DawnMagnet. Thank you for taking the time to translate our README to Chinese!您好。感谢您抽出时间将我们的自述文件翻译成中文！
I'd like to avoid having documentation that makes users run a shell script that's outside our organization repos though.我想避免留档，让用户运行我们组织存储之外的外壳脚本。
I'm wondering, do any of the following URLs work in China?我想知道，以下URL在中国有效吗？

https://github.com/zimfw/zimfw/releases/latest/download/zimfw.zsh.gz
https://api.github.com/repos/zimfw/zimfw/tarball/master

i'm sorry, the *.github.com are all abandoned in china. I also considered that this behavior is not very thoughtful, but for some limited network situations, we really can't access github.


IndexError: list index out of range

Hi,
when I tried to run vcftobedpe analysis, got a constant error like this:
Traceback (most recent call last):
File "/Users/burcudursun/miniconda2/bin/svtools", line 6, in
sys.exit(svtools.cli.main())
File "/Users/burcudursun/miniconda2/lib/python2.7/site-packages/svtools-0.3.1-py2.7.egg/svtools/cli.py", line 78, in main
File "/Users/burcudursun/miniconda2/lib/python2.7/site-packages/svtools-0.3.1-py2.7.egg/svtools/vcftobedpe.py", line 120, in run_from_args
File "/Users/burcudursun/miniconda2/lib/python2.7/site-packages/svtools-0.3.1-py2.7.egg/svtools/vcftobedpe.py", line 67, in vcfToBedpe
File "/Users/burcudursun/miniconda2/lib/python2.7/site-packages/svtools-0.3.1-py2.7.egg/svtools/vcf/variant.py", line 35, in init
IndexError: list index out of range
Could you please help me to solve this?

My best guess based on that error message is that your input VCF doesn't include sample information (i.e. a format field and samples). Is that correct?


BSD Port: Current Issues (Feedback welcomed)

Description
Just a general list of bugs I'm working on ironing out. None of these will break the core platform support but now that UIKit's been implemented, everything can be built and tested. I hope to get this fully functional by next main release. There's not many official game dev tools that support the BSDs.
Prerequisites
Current master has the code changes. Anyone that has 64-bit FreeBSD 14.0 or 14.1 (or other 64-bit BSDs) can test this out.
Steps to Reproduce

Install all of the qt5 requirements (installing the meta package should cover this)
Install libinotify, amath, llvm15+, gcc13+, cmake (all required)
Optional installs:

assimp (may need to rely on a system version for this one instead of the one under thirdparty; will give details below)
ccache (to speed up compile times; if you use this, add -DCMAKE_COMPILER_LAUNCHER=ccache to the end of Step 7 below)

Clone the latest master: git clone --recursive https://github.com/thunder-engine/thunder.git
Make an external build directory: mkdir -pv thunder-build
cd thunder-build
Clang is the default compiler and what the repos will use for building if this were packaged by the OS maintainers and community, but I'm finding that GCC is picking up some linkage errors that Clang is ignoring. Run: CC=gcc CXX=g++ cmake ../thunder to set everything up for building.
I'm not sure about the other BSDs but FreeBSD uses gmake for building native software. Run: gmake to start building. You can speed up the build by running gmake -j <number of cores your CPU has> instead, but for debugging and testing, that can make it hard to see what's happening.

Expected behavior:
Everything should compile without issues and WorldEditor should start up without crashing or major errors. None of the dependencies are directly problematic for the BSDs and (at least on FreeBSD) most of them have official ports available.
Actual behavior:

[x] 1. Engine editor code ignores QTCore and QTWidgets headers (see terminal snippet below). Both are found under /usr/local/include/qt5 on my system and are the only part of engine that's having problems at the moment.

[ 54%] Building CXX object engine/CMakeFiles/engine.dir/src/editor/assetconverter.cpp.o
In file included from /home/brad/git/thunder/engine/src/editor/assetconverter.cpp:1:
/home/brad/git/thunder/engine/includes/editor/assetconverter.h:4:10: fatal error: 'QObject' file not found
#include <QObject>

[ 57%] Building CXX object engine/CMakeFiles/engine.dir/src/editor/asseteditor.cpp.o
In file included from In file included from /home/brad/git/thunder/engine/src/editor/assetconverter.cpp:1:
/home/brad/git/thunder/engine/includes/editor/assetconverter.h:In file included from /home/brad/git/thunder/engine/src/editor/assetmanager.cpp:1:
/home/brad/git/thunder/engine/includes/editor/assetmanager.h:4:10: 4:/home/brad/git/thunder/engine/src/editor/asseteditor.cpp10::fatal error: 1 'QObject' file not foundfatal error:
'QObject' file not found
#include <QObject>
/home/brad/git/thunder/engine/includes/editor/asseteditor.h:4         ^~~~~~~~~:
10: fatal error: 'QWidget' file not found
#include <QWidget>

[x] 2. Assimp::StackAllocator:g_maxBytesPerBlock throws an undefined reference error when linking WorldEditor at the end through libengine-editor.so and sometimes libgraph-editor.so. One suggestion from the assimp issue tracker for similar issues was to upgrade to the latest version. I plan to test it out since the version used in the engine is just one below but also expect breakage when doing such.

[X] 3. WorldEditor crashes due to AddressOutOfBounds segfault after a full successful build with GCC13.

[ ] 4. Clang fully builds and runs both the WorldEditor and Builder applications but WorldEditor crashes after creating a New Project with this error:

 The required settings was not specified: Company Name, Project Version, First Map Please specify them in the Project Settings.
 [PluginManager] Can't load plugin: /home/brad/git/thunder-build/worldeditor/uikit-editor.so
 [ FileIO ] Can't open file index
fish: Job 1, './worldeditor/WorldEditor' terminated by signal SIGSEGV (Address boundary error)

Reproducibility:
Both are consistent with GCC13. Not always reproducible with Clang15.
Versions

Right now, doing a reinstall of all of Qt5 and then rebuilding. It's possible that while I was at work, there was a version update that broke the build since that issue didn't occur before work during my tests.

Update: I have figured out the Assimp issue. Despite this being the error that shows
[ 96%] Linking CXX executable WorldEditor
/usr/local/bin/ld: ../engine/libengine-editor.so: undefined reference to `Assimp::StackAllocator::g_maxBytesPerBlock'
collect2: error: ld returned 1 exit status

it's actually an issue with the FBX Importer. By disabling it only for FreeBSD, the error completely goes away. Other importers use StackAllocator without problems. It's just that one particular one that has a linking issue. It doesn't seem to be fixed in 5.4.1 (the new release), so I may open an issue report upstream.
I have everything fully building now with GCC13. About to test with Clang.

To solve the Address error, I'm currently working my way back a bit on dependencies to see which ones I can remove the -fPIC compiler flag from and still get a full build. That's where I'm guessing the address issues lie.

Hello,
Regarding Issue 4. I have received reports regarding crash on creation of new project. But was unable to reproduce it on my end. Usually it creates a project in any way and restart application solves the problem. But in your case I can see the UIKit was not properly loaded. This is bad. could you please show me the export table for this lib?

Hello, Regarding Issue 4. I have received reports regarding crash on creation of new project. But was unable to reproduce it on my end. Usually it creates a project in any way and restart application solves the problem. But in your case I can see the UIKit was not properly loaded. This is bad. could you please show me the export table for this lib?

It's not building that plugin library at all. Linking the libuikit-editor.so file in the directory doesn't solve the issue either (which is probably related to $ORIGIN linkage differences with the platform). I need to dive into some of my older code for that but I did figure out awhile back how to get around it. That's going to be a new issue.
Give me a sec on the export table. It may not be relevant due to the plugin not building at all, but I can grab one for WorldEditor and libuikit-editor.so while I get more awake.

Update: I have figured out the Assimp issue. Despite this being the error that shows
[ 96%] Linking CXX executable WorldEditor
/usr/local/bin/ld: ../engine/libengine-editor.so: undefined reference to `Assimp::StackAllocator::g_maxBytesPerBlock'
collect2: error: ld returned 1 exit status

it's actually an issue with the FBX Importer. By disabling it only for FreeBSD, the error completely goes away. Other importers use StackAllocator without problems. It's just that one particular one that has a linking issue. It doesn't seem to be fixed in 5.4.1 (the new release), so I may open an bug report upstream.
I have everything fully building now with GCC13. About to test with Clang.

Building as a shared library with the -editor.so suffix does solve the compiler errors but doesn't solve the linkage issue. It's probably not a viable solution.

Full stack trace from GDB at crash:
Thread 1 received signal SIGSEGV, Segmentation fault.
Address not mapped to object.
0x0000000824420e4b in PluginManager::createRenderer() const ()
   from /home/brad/git/thunder-build/engine/libengine-editor.so

With this PR, all of the port specific bugs here have been merged into master. Number 4 and 5 are most likely engine specific and not from the port work since neither of them were directly altered by code I've submitted. The PluginManager::createRenderer() crash could possibly be related to this issue. Finding out more before continuing to look into it.


Support for transactional remote write

Proposal
Use case. Why is this important?
Atomic writes for Prometheus scraped data to remote storage.
Here is the design doc, that contains the plan and discussions around the topic.
Status: Review phase

Perhaps link the doc under https://prometheus.io/docs/introduction/design-doc/ ?

That will be a good place. How do we add to that list?

Just update https://github.com/prometheus/docs/blob/master/content/docs/introduction/design-doc.md and open a PR for that repo.

Reviewed at bug-scrub:
There's not much detail here, and the point is captured under #6333, so closing this issue.


Create CLI options

Options for

adding labels for all repos in an organization.
adding labels for specific repos in an organization.

This is taken care of on PR #12

There's one issue we need to clarify, our initial goal was to apply labels to a repository at once, but I guess that functionality has broken now. @fdiogo

You mean several labels at once?

For several repositories, just one label

Maybe I'm not getting it, but that is possible now. You can select an organization, any number of repositories and any number of issues and apply a label.

Can we select all repos at once ?

Yes, when you select an organization it loads all the repos and presents them as a checklist. You can select all with "a" or one by one by hitting space. Then the same happens with the issues. The issues that are shown are all the issues combined of all the repositories selected previously.

Great ! Then it fits our expectation.


Update version to 2.0.2

The version number in boot.html can be bumped to version 2.0.2.
Reference Issue
Fixes #4751

Done!

Closing per https://github.com/Polymer/polymer/issues/4751#issuecomment-326156028


#3948 highlight stages in timelines with color

Closes #3948
Timeline in service screen:

Timeline in sequence screen:

Signed-off-by: Klaus Strießnig<EMAIL_ADDRESS>

The color of the selected stage now depends on the result of this stage.
Success:

Error:

Approval:


update smoke tests

investigate smoke test failures.
implement changes to address smoke test failures

@chrisjrd - could you describe the failures you're referring to? CC @niarenaw @LalaP

Smoke test executed without errors.


Minor update to README

Correct mistake concerning "e.detail.destination.container"
Emphasise that connectWith is deprecated in section about acceptFrom

Coverage remained the same at 78.088% when pulling<PHONE_NUMBER>cb12aba31c7d69dcdf4e0c3c3e530b on Dory-dev:patch-1 into 8114d243ae00fdc8e4fea83361762fe5623e718a on lukasoppermann:master.

I would also like to point out that the readme still includes multiple references to the deprecated function connectWith. I am unsure if those references can simply be changed to reference acceptFrom.
Maybe you could have a look and update where it is appropriate. Or I'd be glad to update those references if you can confirm that the methods are interchangeable.

It would be great if you could update the rest as well. I am currently not sure if this does apply to acceptFrom as well. Would you have a moment to test it?


Increase timeout for REKT tests to 90m

The execution might take longer if the client is run farther away from the cluster (i.e. not in the same cloud).
/cherry-pick release-v1.14
/cherry-pick main
Slack discussion

/cherry-pick release-v1.14

/cherry-pick main

/lgtm


feat(crux-ui): creating the password icon in crux-ui

fixes #873

Comment from #877 applies to here as well.
Thank you.


feat(css/parser): @container at-rules

Description:
Parse @container
BREAKING CHANGE:
Yes
Related issue (if exists):
Partial https://github.com/swc-project/swc/issues/5410

Still under construction :smile: The spec is big so I am WIP

@kdy1 Ready for review, currently missing and will be implemented in next PRs:

style(...) syntax
SizeFeature validation
todos in code


Regen S3 data

Some sources have changed their cache keys, so we'll need to regen their full S3 data.
The scrapers from CDS that had cache key changes were:
US/TN : default => data
US/VA : we talked about this one before, with their county names becoming cache keys, eg Some County => somecounty
US/VT : default => data
Can gen all three with:
node tools/generate-v1-cache.js --location US/TN,US/VA,US/VT --dest zz-mig3

Done!


Add a --no-ignore-dir to allow negating defaults

For this case https://github.com/petdance/ack2/issues/642 a --no-ignore-dir would have solved the problem.

Expanded into #89.


[NumberField] onChange does not work as expected

🐛 Bug Report
onChange event of useNumberField from @react-aria/numberfield or NumberField from @react-spectrum/numberfield does not work as expected.
🤔 Expected Behavior
Expecting that every time user input or type, it should trigger onChange event when it pass to the component prop. For controlled form, it should trigger the state changes whenever user input which can be seen in console.log
😯 Current Behavior
Currently, it only trigger like onBlur event. User have to click outside of the input in order to see the changes, in this case to see the updated state. doing console.log and see it only trigger whenever click anywhere outside of the input.
🔦 Context
I'm trying to use useNumberField from @react-aria/numberfield with React Hook Form by using Controller by RHF but turns out that NumberField doesn't properly doing onChange event as expected while TextField works fine.
💻 Code Sample
https://codesandbox.io/s/react-spectrum-numberfield-issue-jdp5p
🌍 Your Environment

Software
Version(s)

react-spectrum
3.4 and 3.0-alpha for NumberField

Browser
Chrome

Operating System
MacOS

I was looking something like react-number-format but since react-aria provide accessibility out of the box, gotta go for that.

Ah, very cool project, I think there's room for improvement to this component. And it looks like they might have figured out how to deal with selection position while formatting in real time, that was one of our biggest issues as Devon noted. We should look into how they handle that and make sure it works with things like pinyin.


Incompatibility with version of CategoricalArrays

There seems to be some conflict with the version of CategoricalArrays listed in the Manifest.toml. I can load DataFrames in the Julia REPL, but when I try to run the Julia notebook First steps with data frames.ipynb I get a conflict with CategoricalArrays after using DataFrames.
┌ Info: Precompiling DataFrames [a93c6f00-e57d-5684-b7b6-d8193f3e46c0]
└ @ Base loading.jl:1260
ERROR: LoadError: ArgumentError: Package CategoricalArrays does not have Compat in its dependencies:
- If you have CategoricalArrays checked out for development and have
  added Compat as a dependency but haven't updated your primary
  environment's manifest file, try `Pkg.resolve()`.
- Otherwise you may need to report an issue with CategoricalArrays
Stacktrace:
 [1] require(::Module, ::Symbol) at ./loading.jl:905
 [2] include(::Module, ::String) at ./Base.jl:377
 [3] top-level scope at none:2
 [4] eval at ./boot.jl:331 [inlined]
 [5] eval(::Expr) at ./client.jl:449
 [6] top-level scope at ./none:3
in expression starting at /Users/user888/.julia/packages/CategoricalArrays/dmrjI/src/CategoricalArrays.jl:11
ERROR: LoadError: Failed to precompile CategoricalArrays [324d7699-5711-5eae-9e2f-1d82baa6b597] to /Users/user888/.julia/compiled/v1.4/CategoricalArrays/RHXoP_Ek050.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1272
 [3] _require(::Base.PkgId) at ./loading.jl:1029
 [4] require(::Base.PkgId) at ./loading.jl:927
 [5] require(::Module, ::Symbol) at ./loading.jl:922
 [6] include(::Module, ::String) at ./Base.jl:377
 [7] top-level scope at none:2
 [8] eval at ./boot.jl:331 [inlined]
 [9] eval(::Expr) at ./client.jl:449
 [10] top-level scope at ./none:3
in expression starting at /Users/user888/.julia/packages/DataFrames/S3ZFo/src/DataFrames.jl:5
Failed to precompile DataFrames [a93c6f00-e57d-5684-b7b6-d8193f3e46c0] to /Users/mj847/.julia/compiled/v1.4/DataFrames/AR9oZ_Ek050.ji.

Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1272
 [3] _require(::Base.PkgId) at ./loading.jl:1029
 [4] require(::Base.PkgId) at ./loading.jl:927
 [5] require(::Module, ::Symbol) at ./loading.jl:922
 [6] top-level scope at In[1]:1

Tested with following package versions
Status `~/.julia/environments/v1.4/Project.toml`
  [c52e3926] Atom v0.12.10
  [324d7699] CategoricalArrays v0.7.7
  [35d6a980] ColorSchemes v3.9.0
  [5ae59095] Colors v0.12.0
  [f65535da] Convex v0.13.3
  [a93c6f00] DataFrames v0.20.2
  [31c24e10] Distributions v0.22.6
  [2fe49d83] Expectations v1.4.0
  [f6369f11] ForwardDiff v0.10.10
  [38e38edf] GLM v1.3.9
  [60bf3e95] GLPK v0.13.0
  [ea4f424c] Gen v0.3.2 #master (https://github.com/probcomp/Gen)
  [7073ff75] IJulia v1.21.2
  [c601a237] Interact v0.10.3
  [b6b21f68] Ipopt v0.6.1
  [c8e1da08] IterTools v1.3.0
  [42fd0dbc] IterativeSolvers v0.8.4
  [4076af6c] JuMP v0.21.2
  [e5e0dc1b] Juno v0.8.1
  [ba0b0d4f] Krylov v0.5.1
  [5c8ed15e] LinearOperators v1.1.0
  [2fda8390] LsqFit v0.10.0
  [6f286f6a] MultivariateStats v0.7.0
  [429524aa] Optim v0.21.0
  [1dea7af3] OrdinaryDiffEq v5.36.0
  [3b7a836e] PGFPlots v3.2.1
  [91a5bcdd] Plots v1.2.3
  [f27b6e38] Polynomials v1.0.4 #master (https://github.com/JuliaMath/Polynomials.jl.git)
  [140ffc9f] ProximalAlgorithms v0.3.1
  [a725b495] ProximalOperators v0.10.3
  [6f49c342] RCall v0.13.6
  [c946c3f1] SCS v0.6.6
  [682df890] Stan v6.0.4
  [c1514b29] StanSample v2.1.3
  [2913bbd2] StatsBase v0.32.2
  [c751599d] ToeplitzMatrices v0.6.1
  [0f1e0344] WebIO v0.8.13 #master (https://github.com/JuliaGizmos/WebIO.jl)

Hm,  I just tried running this and was unable to replicate the issue. Perhaps the issue is that you are not running the notebook with the correct Manifest and Project files?
My Pkg.status() does not give me as many entries as this and it should be using the Manifest and Project files from this repo not the main ones in your julia folder which it seems to be pointing to.

I would make sure you cd() into the correct folder. CC @bkamins We should point people to download the entire repo here right?

Yes - you should download the whole repository and run it from the folder where you have downloaded the files.
This is exactly the purpose of running https://github.com/JuliaAcademy/DataFrames/blob/master/1. Environment setup.ipynb part to make sure that you have the proper environment set up. You should get the output exactly as shown there.
Now regarding your output note that you have:

DataFrames.jl version 0.20.2
you do not have CSV.jl installed
you have not activated the project environment, but rather you are using the default environment

If you check the Manifest.toml in the repository of the tutorial you will see that in particular:

DataFrames.jl is required to be in 0.21 version
CSV.jl needs to be installed in 0.6.2 version

Note that if you are in the correct directory Jupyter Notebook will automatically use Project.toml and Manifest.toml files I have shared. I also have recently written up a small post explaining how to make Julia REPL to do the same here: https://bkamins.github.io/julialang/2020/05/10/julia-project-environments.html.

I had changed to the directory with the data-frame tutorials, but I can no longer reproduce the problem. Everything seems to run fine now. Thank you!


[vm] non-const LinkedHashMap in JIT snapshots

We currently don't support having non-const LinkedHashMaps in JIT snapshots.
When invoking a function with non-const Maps before creating the snapshot and invoking the same function after loading the JIT snapshot we crash.
Reproduction: https://dart-review.googlesource.com/c/sdk/+/204503/1
Removing either the invocation of the non-const Map before creating the snapshot or when running from the snapshot makes the test succeed.
(Possibly related: Changing the clusters for kLinkedHashMapCid in clustered_snapshot.cc to UNREACHABLE still builds the SDK just fine, and doesn't trigger on the reproduction test case.)

JIT snapshots don't support/expect arbitrary non-constant data in them, that's why they are taken with fields_may_be_reset flag. I think the cluster code for serializing kLinkedHashMapCid is dead code and is untested.


Bump nginx-ingress-controller-seed to v1.6.4 for 1.23+ seeds

How to categorize this PR?

/area control-plane open-source
/kind enhancement
What this PR does / why we need it:
Bump nginx-ingress-controller-seed to v1.6.4 for 1.23+ seeds and v1.4.0 for 1.22.x seeds
See compatibility matrix: https://github.com/kubernetes/ingress-nginx#supported-versions-table
https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.4.0
https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.5.1
https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.6.4
Adapted RBAC related to https://github.com/kubernetes/ingress-nginx/pull/8890
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

`nginx-ingress-controller-seed` image is updated to `v1.6.4` for 1.23+ seeds and `v1.4.0` for 1.22.x seeds.

/test pull-gardener-e2e-kind


Bump bevy_asset_loader version to 0.12.1

This isn't needed, since the manifest file doesn't freeze the minor version


Cannot find package "google.golang.org/api/photoslibrary/v1"

I am not able to install since of the missing package from above.
Trying to do:
go get -u  -> fails with package google.golang.org/api/photoslibrary/v1: cannot find package "google.golang.org/api/photoslibrary/v1" in any of:
make build

Hi,Please review installation instructions... it's not possible to use go get when you ate using a "vendor" library and go mod. PacoEl 29 jun. 2019 6:29, gregadunbit<EMAIL_ADDRESS>escribió:I am not able to install since of the missing package from above.
Trying to do:
go get -u  -> fails with package google.golang.org/api/photoslibrary/v1: cannot find package "google.golang.org/api/photoslibrary/v1" in any of:
make build
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.


v1 alerts are not working on 2.6.3 -> alerts are not firing when there is activity

Rancher Server Setup

Rancher version: v2.6.3-rc4
Installation option (Docker install/Helm Chart): docker

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: 1.20.13, 1.22.3
Cluster Type (Local/Downstream): both were tested (local 1.22, downstream 1.20 and 1.22)

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): node driver, digital ocean

Describe the bug

alerts are not firing when there is clear activity for that alert

To Reproduce

enable legacy flag
add a notifier (legacy -> notifiers). I used slack
add a simple alert (legacy -> alerts) i.e. normal pod activity should send an alert
deploy a workload or deploy some charts

Result
alerts are not firing and the notifiers are not being triggered
Additional context
found when testing https://github.com/rancher/rancher/issues/34059#issuecomment-986420709
edit: after installing monitoring v0.3.1, this is working on the 1.20 downstream cluster since alerting is dependent on the operator that monitoring installs.

The bug is reproduced in rancher 2.6.3-rc4 single install setup.
Alerting v1 is broken in Rancher v2.6.3-rc4 (local cluster runs k3s 1.22 ), in downstream clusters running either RKE1 1.20 or 1.22
Normally, there should be two apps installed in the system project when cluster alerting is enabled: cluster-alerting and monitoring-operator.

In the downstream 1.20 cluster, the cluster-alerting app is installed with some resources missing, the monitoring-operator app is not installed.  We see the following error in rancher logs
2021/12/07 19:43:00 [ERROR] error syncing 'c-vqvng/car-zhkcj': handler cluster-alert-rule-deployer: failed to get Alertmanager Deployment information, statefulsets.apps "alertmanager-cluster-alerting" not found, handler cluster-alert-rule-controller: Failed to get service for alertmanager, services "cattle-prometheus/alertmanager-operated" not found, requeuing

In the downstream 1.22 cluster,  none of those two apps are installed, and we see the following error in rancher logs
[tiller] 2021/12/07 23:03:31 warning: Release cluster-alerting crd-install rancher-monitoring/templates/crds.yaml failed: unable to recognize "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
[tiller] 2021/12/07 23:03:31 failed install perform step: unable to recognize "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
Finished installing CRD: unable to recognize "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"2021/12/07 23:03:31 [DEBUG] Stopping Tiller

and the following in the app in  Rancher UI

The error makes sense because apiextensions.k8s.io/v1beta1 does not exist in 1.22 cluster.

Going to test this with 1.21 before bumping to 2.6.4.

Root cause
The prometheus-operator-handler is used for both monitoring and alerting, but in rancher v2.6 it will be started only if monitoring is enabled.
As the result, enabling alerting alone does not trigger prometheus-operator-handler to run, so alerting is broken.
What was fixed, or what changes have occurred
enable the prometheus-operator-handler when either monitoring or alerting is enabled.
Areas or cases that should be tested
alerting v1
What areas could experience regressions?

both the cluster-alerting and monitoring-operator app should be installed properly
alerts can be sent out to receives such as lack

Are the repro steps accurate/minimal?
yes, the steps in the original issue is accurate.

Setup For Reproduction

Rancher version: v2.6.3-rc4
Installation option (Docker install/Helm Chart): docker

Cluster Information

Cluster type: RKE1
K8s Version: 120.13

Steps For Reproduction

enable legacy flag

add a notifier (legacy -> notifiers). I used slack

add a simple alert (legacy -> alerts) i.e. normal pod activity should send an alert

deploy a workload or deploy some charts

Result
There were no slack notifications sent when I installed and app or a workload.
Setup For Validation

Rancher version: v2.6.3-head(fd930f7)
Cluster type: RKE1
K8s Version: : v1.21.7

Steps for validation

enable legacy flag

add a notifier (legacy -> notifiers). I used slack

add a simple alert (legacy -> alerts) i.e. normal pod activity should send an alert

deploy a workload or deploy some charts

Result
The alerts are being sent once the appropriate parameters are met that got set within the notifier.