Improved offset when dropping element in animations

Tried to fix the offsets when adding elements in the editor.
When an element is added to an animation, its position is converted from pixels to % of the animation size.
When displaying an element, the position is converted back from % to pixels.
The values were not corresponding but now it is fixed.
I don't know why but I also needed to remove from the y coordinates the top bar size... (hope it does not only work on my phone)
The position is still not perfect (the element moves a few pixels from the dropping point) but it is quite close.
I also fixed the color of the text in the disc (it was white on a white background).

Awesome!
I'm on holidays this week. I'll review the code and  check it out on my
phone on Sunday
Le mar 11 août 2020 12:18, ZacharieALES<EMAIL_ADDRESS>a écrit :

Tried to fix the offsets when adding elements in the editor.
When an element is added to an animation, its position is converted from
pixels to % of the animation size.
When displaying an element, the position is converted back from % to
pixels.
The values were not corresponding but now it is fixed.
I don't know why but I also needed to remove from the y coordinates the
top bar size... (hope it does not only work on my phone)
The position is still not perfect (the element moves a few pixels from the
dropping point) but it is quite close.
I also fixed the color of the text in the disc (it was white on a white
background).
You can view, comment on, or merge this pull request online at:
https://github.com/UltimateApp/UltimateApp/pull/192
Commit Summary

Improved offset when dropping element in animations

File Changes

M src/Components/animation/Animation.js
https://github.com/UltimateApp/UltimateApp/pull/192/files#diff-d957adce46514b3fdc394d85a26a1013
(23)
M src/Components/animation/AnimationEditor.js
https://github.com/UltimateApp/UltimateApp/pull/192/files#diff-1e7a0fa236feb297457614429e1dd72c
(59)
M src/Components/animation/DisplayedCuts.js
https://github.com/UltimateApp/UltimateApp/pull/192/files#diff-b9157309f3cd09a5407ad6642abb1034
(30)
M src/Components/animation/DisplayedElement.js
https://github.com/UltimateApp/UltimateApp/pull/192/files#diff-9d977c0158396ab5261e1b9f869648d7
(33)
M src/Components/animation/DraggableDisplayedElement.js
https://github.com/UltimateApp/UltimateApp/pull/192/files#diff-a43173854113be04afc129f7f7059d6c
(1)
M src/Components/animation/MovingCircle.js
https://github.com/UltimateApp/UltimateApp/pull/192/files#diff-60b787991e22da7057a73345cda8f71f
(1)
M src/Components/animation/debug.js
https://github.com/UltimateApp/UltimateApp/pull/192/files#diff-9cd91f2b5191de4eb3c34211c340c8b1
(2)

Patch Links:

https://github.com/UltimateApp/UltimateApp/pull/192.patch
https://github.com/UltimateApp/UltimateApp/pull/192.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/UltimateApp/UltimateApp/pull/192, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5CL24IHBGND5PBURBFHJ3SAELGDANCNFSM4P24BLWQ
.

@ZacharieALES I get this exception when I run the app on this branch, on an Android Emulator
Invariant Violation: inputRange must be monotonically non-decreasing 0,1,NaN,2,3,NaN,4,NaN,5
- node_modules/react-native/Libraries/LogBox/LogBox.js:148:8 in registerError
- node_modules/react-native/Libraries/LogBox/LogBox.js:59:8 in errorImpl
- node_modules/react-native/Libraries/LogBox/LogBox.js:33:4 in console.error
- node_modules/expo/build/environment/react-native-logs.fx.js:27:4 in error
- node_modules/react-native/Libraries/Core/ExceptionsManager.js:104:6 in reportException
- node_modules/react-native/Libraries/Core/ExceptionsManager.js:171:19 in handleException
- node_modules/react-native/Libraries/Core/ReactFiberErrorDialog.js:43:2 in showErrorDialog
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:15257:32 in logCapturedError
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:15361:20 in logError
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:16612:14 in update.payload
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:6899:23 in getStateFromUpdate
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:7032:39 in processUpdateQueue
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:8107:20 in updateClassInstance
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:12394:38 in updateClassComponent
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:19181:22 in beginWork$1
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:18085:22 in performUnitOfWork
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:18013:38 in workLoopSync
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:17977:18 in renderRootSync
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:17674:33 in performSyncWorkOnRoot
* [native code]:null in performSyncWorkOnRoot
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:5321:31 in runWithPriority$argument_1
- node_modules/scheduler/cjs/scheduler.development.js:653:23 in unstable_runWithPriority
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:5316:21 in flushSyncCallbackQueueImpl
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:5304:28 in flushSyncCallbackQueue
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:17718:28 in batchedUpdates$1
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2492:29 in batchedUpdates
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2638:16 in _receiveRootNodeIDEvent
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2713:25 in receiveEvent
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:416:4 in __callFunction
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:109:6 in __guard$argument_0
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:364:10 in __guard
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:108:4 in callFunctionReturnFlushedQueue
* [native code]:null in callFunctionReturnFlushedQueue

Happens on the Give'n'Go drill accessed from the Drill List
Here is my emulator spec:

This seems to come from invalid values in the animation

I have had this bug when playing around (same configuration as above)
The counter cut circle moves away


Failed to build gem native extension / libiconv is missing

Before being able to install fastlane, I had to manually install nokogiri using the following command:
sudo gem install nokogiri -- --use-system-libraries --with-xml2-include=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/usr/include/libxml2
--use-system-libraries allows the install to use the OS X version of libiconv.
--with-xml2= tells it where to find libxml2
Other solutions I found online involved installing homebrew, which I didn't want to do.

Building nokogiri manually is a pain and sometimes quite tricky to do, that's why I recommend using homebrew. Is there a reason you don't want to use it?

I'll close this issue for now, let me know if you need any help.


Configuration Manager rebranding

User Story 1643831: Content Update: ConfigMgr rebrand
System Center Configuration Manager is now part of Microsoft Endpoint Manager with Intune, Desktop Analytics, Autopilot, and the Device Management Admin Center (DMAC).
Its full brand name is now Microsoft Endpoint Configuration Manager.
This PR addresses the rebranding of all instances of "System Center Configuration Manager" in this repo.
4 instances of "System Center Configuration Manager 2012" were left because they referred to that specific version.

#sign-off


Implement a Log-In Button

Implement a log-in button for the Spotify users.

I think I heard that the default profile picture will be the log-in button. If this was implemented already, close this issue.


> Task :expo-keep-awake:processReleaseJavaRes
> Task :expo-keep-awake:mergeReleaseJavaResource
> Task :expo-keep-awake:syncReleaseLibJars
> Task :expo-keep-awake:bundleReleaseLocalLintAar
> Task :expo-secure-store:extractReleaseAnnotations
> Task :expo-secure-store:mergeReleaseGeneratedProguardFiles
> Task :expo-secure-store:mergeReleaseConsumerProguardFiles
> Task :expo-secure-store:prepareLintJarForPublish
> Task :expo-secure-store:prepareReleaseArtProfile
> Task :expo-secure-store:processReleaseJavaRes
> Task :expo-secure-store:mergeReleaseJavaResource
> Task :expo-secure-store:syncReleaseLibJars
> Task :expo-secure-store:writeReleaseAarMetadata
> Task :expo-secure-store:bundleReleaseLocalLintAar
> Task :expo-web-browser:mergeReleaseJniLibFolders
> Task :expo-web-browser:mergeReleaseNativeLibs NO-SOURCE
> Task :expo-web-browser:stripReleaseDebugSymbols NO-SOURCE
> Task :expo-web-browser:copyReleaseJniLibsProjectAndLocalJars
> Task :expo-web-browser:extractDeepLinksForAarRelease
> Task :expo-web-browser:extractReleaseAnnotations
> Task :expo-web-browser:mergeReleaseGeneratedProguardFiles
> Task :expo-web-browser:mergeReleaseConsumerProguardFiles
> Task :expo-web-browser:mergeReleaseShaders
> Task :expo-web-browser:compileReleaseShaders NO-SOURCE
> Task :expo-web-browser:generateReleaseAssets UP-TO-DATE
> Task :expo-web-browser:packageReleaseAssets
> Task :expo-web-browser:prepareLintJarForPublish
> Task :expo-web-browser:prepareReleaseArtProfile
> Task :expo-web-browser:processReleaseJavaRes
> Task :expo-web-browser:mergeReleaseJavaResource
> Task :expo-web-browser:syncReleaseLibJars
> Task :expo-web-browser:writeReleaseAarMetadata
> Task :expo-web-browser:bundleReleaseLocalLintAar
> Task :expo-modules-core:configureCMakeRelWithDebInfo[arm64-v8a]
> Task :expo-av:buildCMakeRelWithDebInfo[arm64-v8a]
> Task :expo-dev-launcher:compileReleaseKotlin
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/DevLauncherRecentlyOpenedAppsRegistry.kt:32:47 Unchecked cast: MutableMap<Any?, Any?> to MutableMap<String, Any>
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/DevLauncherRecentlyOpenedAppsRegistry.kt:50:27 'getRawJson(): JSONObject' is deprecated. Prefer to use specific field getters
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:37:23 'constructor TaskDescription(String!, Bitmap!, Int)' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:63:61 'FLAG_TRANSLUCENT_STATUS: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:90:33 Variable 'appliedStatusBarStyle' initializer is redundant
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:92:45 'getter for systemUiVisibility: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:95:68 'SYSTEM_UI_FLAG_LIGHT_STATUS_BAR: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:99:67 'SYSTEM_UI_FLAG_LIGHT_STATUS_BAR: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:103:67 'SYSTEM_UI_FLAG_LIGHT_STATUS_BAR: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:107:15 'setter for systemUiVisibility: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:115:59 'FLAG_FULLSCREEN: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:116:61 'FLAG_FORCE_NOT_FULLSCREEN: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:118:59 'FLAG_FORCE_NOT_FULLSCREEN: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:119:61 'FLAG_FULLSCREEN: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:131:23 'replaceSystemWindowInsets(Int, Int, Int, Int): WindowInsets' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:132:25 'getter for systemWindowInsetLeft: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:134:25 'getter for systemWindowInsetRight: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:135:25 'getter for systemWindowInsetBottom: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:160:63 'FLAG_TRANSLUCENT_NAVIGATION: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:171:63 'FLAG_TRANSLUCENT_NAVIGATION: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:175:33 'getter for systemUiVisibility: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:176:33 'SYSTEM_UI_FLAG_LIGHT_NAVIGATION_BAR: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:177:21 'setter for systemUiVisibility: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:190:29 'getter for systemUiVisibility: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:191:62 'SYSTEM_UI_FLAG_HIDE_NAVIGATION: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:191:101 'SYSTEM_UI_FLAG_FULLSCREEN: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:192:63 'SYSTEM_UI_FLAG_HIDE_NAVIGATION: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:192:102 'SYSTEM_UI_FLAG_FULLSCREEN: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:192:136 'SYSTEM_UI_FLAG_IMMERSIVE: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:193:70 'SYSTEM_UI_FLAG_HIDE_NAVIGATION: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:193:109 'SYSTEM_UI_FLAG_FULLSCREEN: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:193:143 'SYSTEM_UI_FLAG_IMMERSIVE_STICKY: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/main/java/expo/modules/devlauncher/launcher/configurators/DevLauncherExpoActivityConfigurator.kt:196:17 'setter for systemUiVisibility: Int' is deprecated. Deprecated in Java
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/release/java/expo/modules/devlauncher/DevLauncherController.kt:103:20 Parameter 'context' is never used
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/release/java/expo/modules/devlauncher/DevLauncherController.kt:103:38 Parameter 'reactNativeHost' is never used
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/release/java/expo/modules/devlauncher/DevLauncherController.kt:109:64 Parameter 'cazz' is never used
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/release/java/expo/modules/devlauncher/DevLauncherController.kt:114:35 Parameter 'reactActivity' is never used
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/release/java/expo/modules/devlauncher/DevLauncherController.kt:119:27 Parameter 'reactActivity' is never used
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/release/java/expo/modules/devlauncher/DevLauncherController.kt:119:57 Parameter 'intent' is never used
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/release/java/expo/modules/devlauncher/DevLauncherPackageDelegate.kt:15:27 Parameter 'reactContext' is never used
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/release/java/expo/modules/devlauncher/DevLauncherPackageDelegate.kt:16:43 Parameter 'context' is never used
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/release/java/expo/modules/devlauncher/DevLauncherPackageDelegate.kt:17:45 Parameter 'activityContext' is never used
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/release/java/expo/modules/devlauncher/DevLauncherPackageDelegate.kt:18:35 Parameter 'activityContext' is never used
w: file:///home/expo/workingdir/build/node_modules/expo-dev-launcher/android/src/release/java/expo/modules/devlauncher/DevLauncherPackageDelegate.kt:19:37 Parameter 'context' is never used
> Task :expo-av:configureCMakeRelWithDebInfo[armeabi-v7a]
> Task :expo-dev-launcher:compileReleaseJavaWithJavac
> Task :expo-dev-launcher:bundleLibCompileToJarRelease
> Task :expo:compileReleaseKotlin
w: file:///home/expo/workingdir/build/node_modules/expo/android/src/main/java/expo/modules/ReactActivityDelegateWrapper.kt:139:50 No cast needed
> Task :expo-av:buildCMakeRelWithDebInfo[armeabi-v7a]
> Task :expo:extractReleaseAnnotations
> Task :expo:compileReleaseJavaWithJavac
> Task :expo:mergeReleaseGeneratedProguardFiles
> Task :expo:mergeReleaseConsumerProguardFiles
> Task :expo:processReleaseJavaRes
> Task :expo:mergeReleaseJavaResource
> Task :expo:syncReleaseLibJars
> Task :expo:bundleReleaseLocalLintAar
> Task :expo-dev-launcher:extractReleaseAnnotations
> Task :expo-dev-launcher:mergeReleaseGeneratedProguardFiles
> Task :expo-dev-launcher:mergeReleaseConsumerProguardFiles
> Task :expo-dev-launcher:processReleaseJavaRes
> Task :expo-dev-launcher:mergeReleaseJavaResource
> Task :expo-dev-launcher:syncReleaseLibJars
> Task :expo-dev-launcher:bundleReleaseLocalLintAar
> Task :expo-dev-menu-interface:mergeReleaseJniLibFolders
> Task :expo-dev-menu-interface:mergeReleaseNativeLibs NO-SOURCE
> Task :expo-dev-menu-interface:stripReleaseDebugSymbols NO-SOURCE
> Task :expo-dev-menu-interface:copyReleaseJniLibsProjectAndLocalJars
> Task :expo-dev-menu-interface:extractDeepLinksForAarRelease
> Task :expo-dev-menu-interface:extractReleaseAnnotations
> Task :expo-dev-menu-interface:mergeReleaseGeneratedProguardFiles
> Task :expo-dev-menu-interface:mergeReleaseConsumerProguardFiles
> Task :expo-dev-menu-interface:mergeReleaseShaders
> Task :expo-dev-menu-interface:compileReleaseShaders NO-SOURCE
> Task :expo-dev-menu-interface:generateReleaseAssets UP-TO-DATE
> Task :expo-dev-menu-interface:packageReleaseAssets
> Task :expo-dev-menu-interface:prepareLintJarForPublish
> Task :expo-dev-menu-interface:prepareReleaseArtProfile
> Task :expo-dev-menu-interface:processReleaseJavaRes
> Task :expo-dev-menu-interface:mergeReleaseJavaResource
> Task :expo-dev-menu-interface:syncReleaseLibJars
> Task :expo-dev-menu-interface:writeReleaseAarMetadata
> Task :expo-dev-menu-interface:bundleReleaseLocalLintAar
> Task :expo-dev-client:mergeReleaseJniLibFolders
> Task :expo-dev-client:mergeReleaseNativeLibs NO-SOURCE
> Task :expo-dev-client:stripReleaseDebugSymbols NO-SOURCE
> Task :expo-dev-client:copyReleaseJniLibsProjectAndLocalJars
> Task :expo-dev-client:extractDeepLinksForAarRelease
> Task :expo-dev-client:extractReleaseAnnotations
> Task :expo-dev-client:mergeReleaseGeneratedProguardFiles
> Task :expo-dev-client:mergeReleaseConsumerProguardFiles
> Task :expo-dev-client:mergeReleaseShaders
> Task :expo-dev-client:compileReleaseShaders NO-SOURCE
> Task :expo-dev-client:generateReleaseAssets UP-TO-DATE
> Task :expo-dev-client:packageReleaseAssets
> Task :expo-dev-client:prepareLintJarForPublish
> Task :expo-dev-client:prepareReleaseArtProfile
> Task :expo-dev-client:processReleaseJavaRes NO-SOURCE
> Task :expo-dev-client:mergeReleaseJavaResource
> Task :expo-dev-client:syncReleaseLibJars
> Task :expo-dev-client:writeReleaseAarMetadata
> Task :expo-dev-client:bundleReleaseLocalLintAar
> Task :expo-manifests:mergeReleaseJniLibFolders
> Task :expo-manifests:mergeReleaseNativeLibs NO-SOURCE
> Task :expo-manifests:stripReleaseDebugSymbols NO-SOURCE
> Task :expo-manifests:copyReleaseJniLibsProjectAndLocalJars
> Task :expo-manifests:extractDeepLinksForAarRelease
> Task :expo-manifests:extractReleaseAnnotations
> Task :expo-manifests:mergeReleaseGeneratedProguardFiles
> Task :expo-manifests:mergeReleaseConsumerProguardFiles
> Task :expo-manifests:mergeReleaseShaders
> Task :expo-manifests:compileReleaseShaders NO-SOURCE
> Task :expo-manifests:generateReleaseAssets UP-TO-DATE
> Task :expo-manifests:packageReleaseAssets
> Task :expo-manifests:prepareLintJarForPublish
> Task :expo-manifests:prepareReleaseArtProfile
> Task :expo-manifests:processReleaseJavaRes
> Task :expo-manifests:mergeReleaseJavaResource
> Task :expo-manifests:syncReleaseLibJars
> Task :expo-manifests:writeReleaseAarMetadata
> Task :expo-manifests:bundleReleaseLocalLintAar
> Task :expo-json-utils:mergeReleaseJniLibFolders
> Task :expo-json-utils:mergeReleaseNativeLibs NO-SOURCE
> Task :expo-json-utils:stripReleaseDebugSymbols NO-SOURCE
> Task :expo-json-utils:copyReleaseJniLibsProjectAndLocalJars
> Task :expo-json-utils:extractDeepLinksForAarRelease
> Task :expo-json-utils:extractReleaseAnnotations
> Task :expo-json-utils:mergeReleaseGeneratedProguardFiles
> Task :expo-json-utils:mergeReleaseConsumerProguardFiles
> Task :expo-json-utils:mergeReleaseShaders
> Task :expo-json-utils:compileReleaseShaders NO-SOURCE
> Task :expo-json-utils:generateReleaseAssets UP-TO-DATE
> Task :expo-json-utils:packageReleaseAssets
> Task :expo-json-utils:prepareLintJarForPublish
> Task :expo-json-utils:prepareReleaseArtProfile
> Task :expo-json-utils:processReleaseJavaRes
> Task :expo-json-utils:mergeReleaseJavaResource
> Task :expo-json-utils:syncReleaseLibJars
> Task :expo-json-utils:writeReleaseAarMetadata
> Task :expo-json-utils:bundleReleaseLocalLintAar
> Task :expo-updates-interface:mergeReleaseJniLibFolders
> Task :expo-updates-interface:mergeReleaseNativeLibs NO-SOURCE
> Task :expo-updates-interface:stripReleaseDebugSymbols NO-SOURCE
> Task :expo-updates-interface:copyReleaseJniLibsProjectAndLocalJars
> Task :expo-updates-interface:extractDeepLinksForAarRelease
> Task :expo-updates-interface:extractReleaseAnnotations
> Task :expo-updates-interface:mergeReleaseGeneratedProguardFiles
> Task :expo-updates-interface:mergeReleaseConsumerProguardFiles
> Task :expo-updates-interface:mergeReleaseShaders
> Task :expo-updates-interface:compileReleaseShaders NO-SOURCE
> Task :expo-updates-interface:generateReleaseAssets UP-TO-DATE
> Task :expo-updates-interface:packageReleaseAssets
> Task :expo-updates-interface:prepareLintJarForPublish
> Task :expo-updates-interface:prepareReleaseArtProfile
> Task :expo-updates-interface:processReleaseJavaRes NO-SOURCE
> Task :expo-updates-interface:mergeReleaseJavaResource
> Task :expo-updates-interface:syncReleaseLibJars
> Task :expo-updates-interface:writeReleaseAarMetadata
> Task :expo-updates-interface:bundleReleaseLocalLintAar
> Task :expo-av:configureCMakeRelWithDebInfo[x86]
> Task :app:buildKotlinToolingMetadata
> Task :app:generateCodegenSchemaFromJavaScript SKIPPED
> Task :app:generateCodegenArtifactsFromSchema SKIPPED
> Task :app:generatePackageList
> Task :app:preBuild
> Task :app:preReleaseBuild
> Task :app:generateReleaseBuildConfig
> Task :react-native-reanimated:buildCMakeRelWithDebInfo[armeabi-v7a]
> Task :expo-av:buildCMakeRelWithDebInfo[x86]
> Task :expo-modules-core:buildCMakeRelWithDebInfo[arm64-v8a]
> Task :expo-av:configureCMakeRelWithDebInfo[x86_64]
> Task :expo-av:buildCMakeRelWithDebInfo[x86_64]
> Task :expo-av:mergeReleaseJniLibFolders
> Task :expo-av:mergeReleaseNativeLibs
> Task :expo-av:stripReleaseDebugSymbols
> Task :expo-av:copyReleaseJniLibsProjectAndLocalJars
> Task :expo-av:extractDeepLinksForAarRelease
> Task :expo-av:extractReleaseAnnotations
> Task :expo-av:mergeReleaseGeneratedProguardFiles
> Task :expo-av:mergeReleaseConsumerProguardFiles
> Task :expo-av:mergeReleaseShaders
> Task :expo-av:compileReleaseShaders NO-SOURCE
> Task :expo-av:generateReleaseAssets UP-TO-DATE
> Task :expo-av:packageReleaseAssets
> Task :expo-av:prepareLintJarForPublish
> Task :expo-av:prepareReleaseArtProfile
> Task :expo-av:processReleaseJavaRes
> Task :expo-av:mergeReleaseJavaResource
> Task :expo-av:syncReleaseLibJars
> Task :expo-av:writeReleaseAarMetadata
> Task :expo-av:bundleReleaseLocalLintAar
> Task :expo:extractDeepLinksRelease
> Task :expo-application:extractDeepLinksRelease
> Task :expo-av:extractDeepLinksRelease
> Task :expo-blur:extractDeepLinksRelease
> Task :expo-constants:extractDeepLinksRelease
> Task :expo-crypto:extractDeepLinksRelease
> Task :expo-dev-client:extractDeepLinksRelease
> Task :expo-dev-launcher:extractDeepLinksRelease
> Task :expo-dev-menu:extractDeepLinksRelease
> Task :expo-dev-menu-interface:extractDeepLinksRelease
> Task :expo-file-system:extractDeepLinksRelease
> Task :expo-font:extractDeepLinksRelease
> Task :expo-json-utils:extractDeepLinksRelease
> Task :expo-keep-awake:extractDeepLinksRelease
> Task :expo-manifests:extractDeepLinksRelease
> Task :expo-secure-store:extractDeepLinksRelease
> Task :expo-updates-interface:extractDeepLinksRelease
> Task :expo-web-browser:extractDeepLinksRelease
> Task :react-native-app-auth:extractDeepLinksRelease
> Task :react-native-async-storage_async-storage:extractDeepLinksRelease
> Task :react-native-community_slider:extractDeepLinksRelease
> Task :react-native-gesture-handler:extractDeepLinksRelease
> Task :react-native-picker_picker:extractDeepLinksRelease
> Task :react-native-safe-area-context:extractDeepLinksRelease
> Task :react-native-screens:extractDeepLinksRelease
> Task :react-native-track-player:extractDeepLinksRelease
> Task :react-native-webview:extractDeepLinksRelease
> Task :expo:compileReleaseLibraryResources
> Task :expo-application:compileReleaseLibraryResources
> Task :expo-av:compileReleaseLibraryResources
> Task :expo-blur:compileReleaseLibraryResources
> Task :expo-constants:compileReleaseLibraryResources
> Task :expo-crypto:compileReleaseLibraryResources
> Task :expo-dev-client:compileReleaseLibraryResources
> Task :expo-dev-launcher:compileReleaseLibraryResources
> Task :expo-dev-menu:compileReleaseLibraryResources
> Task :expo-dev-menu-interface:compileReleaseLibraryResources
> Task :expo-file-system:compileReleaseLibraryResources
> Task :expo-font:compileReleaseLibraryResources
> Task :expo-json-utils:compileReleaseLibraryResources
> Task :expo-keep-awake:compileReleaseLibraryResources
> Task :expo-manifests:compileReleaseLibraryResources
> Task :expo-secure-store:compileReleaseLibraryResources
> Task :expo-updates-interface:compileReleaseLibraryResources
> Task :expo-web-browser:compileReleaseLibraryResources
> Task :react-native-app-auth:compileReleaseLibraryResources
> Task :react-native-async-storage_async-storage:compileReleaseLibraryResources
> Task :react-native-community_slider:compileReleaseLibraryResources
> Task :react-native-gesture-handler:compileReleaseLibraryResources
> Task :react-native-picker_picker:compileReleaseLibraryResources
> Task :react-native-safe-area-context:compileReleaseLibraryResources
> Task :react-native-screens:compileReleaseLibraryResources
> Task :react-native-track-player:compileReleaseLibraryResources
> Task :react-native-webview:compileReleaseLibraryResources
> Task :expo:bundleLibCompileToJarRelease
> Task :react-native-app-auth:bundleLibCompileToJarRelease
> Task :react-native-async-storage_async-storage:bundleLibCompileToJarRelease
> Task :react-native-community_slider:bundleLibCompileToJarRelease
> Task :react-native-gesture-handler:bundleLibCompileToJarRelease
> Task :react-native-picker_picker:bundleLibCompileToJarRelease
> Task :react-native-safe-area-context:bundleLibCompileToJarRelease
> Task :react-native-screens:bundleLibCompileToJarRelease
> Task :react-native-track-player:bundleLibCompileToJarRelease
> Task :react-native-webview:bundleLibCompileToJarRelease
> Task :expo:bundleLibRuntimeToJarRelease
> Task :expo:createFullJarRelease
> Task :expo:writeReleaseLintModelMetadata
> Task :expo-application:bundleLibRuntimeToJarRelease
> Task :expo-application:createFullJarRelease
> Task :expo-application:writeReleaseLintModelMetadata
> Task :expo-av:bundleLibRuntimeToJarRelease
> Task :expo-av:createFullJarRelease
> Task :expo-av:writeReleaseLintModelMetadata
> Task :expo-blur:bundleLibRuntimeToJarRelease
> Task :expo-blur:createFullJarRelease
> Task :expo-blur:writeReleaseLintModelMetadata
> Task :expo-constants:bundleLibRuntimeToJarRelease
> Task :expo-constants:createFullJarRelease
> Task :expo-constants:writeReleaseLintModelMetadata
> Task :expo-crypto:bundleLibRuntimeToJarRelease
> Task :expo-crypto:createFullJarRelease
> Task :expo-crypto:writeReleaseLintModelMetadata
> Task :expo-dev-client:bundleLibRuntimeToJarRelease
> Task :expo-dev-client:createFullJarRelease
> Task :expo-dev-client:writeReleaseLintModelMetadata
> Task :expo-dev-launcher:bundleLibRuntimeToJarRelease
> Task :expo-dev-launcher:createFullJarRelease
> Task :expo-dev-launcher:writeReleaseLintModelMetadata
> Task :expo-dev-menu:bundleLibRuntimeToJarRelease
> Task :expo-dev-menu:createFullJarRelease
> Task :expo-dev-menu:writeReleaseLintModelMetadata
> Task :expo-dev-menu-interface:bundleLibRuntimeToJarRelease
> Task :expo-dev-menu-interface:createFullJarRelease
> Task :expo-dev-menu-interface:writeReleaseLintModelMetadata
> Task :expo-file-system:bundleLibRuntimeToJarRelease
> Task :expo-file-system:createFullJarRelease
> Task :expo-file-system:writeReleaseLintModelMetadata
> Task :expo-font:bundleLibRuntimeToJarRelease
> Task :expo-font:createFullJarRelease
> Task :expo-font:writeReleaseLintModelMetadata
> Task :expo-json-utils:bundleLibRuntimeToJarRelease
> Task :expo-json-utils:createFullJarRelease
> Task :expo-json-utils:writeReleaseLintModelMetadata
> Task :expo-keep-awake:bundleLibRuntimeToJarRelease
> Task :expo-keep-awake:createFullJarRelease
> Task :expo-keep-awake:writeReleaseLintModelMetadata
> Task :expo-manifests:bundleLibRuntimeToJarRelease
> Task :expo-manifests:createFullJarRelease
> Task :expo-manifests:writeReleaseLintModelMetadata
> Task :expo-secure-store:bundleLibRuntimeToJarRelease
> Task :expo-secure-store:createFullJarRelease
> Task :expo-secure-store:writeReleaseLintModelMetadata
> Task :expo-updates-interface:bundleLibRuntimeToJarRelease
> Task :expo-updates-interface:createFullJarRelease
> Task :expo-updates-interface:writeReleaseLintModelMetadata
> Task :expo-web-browser:bundleLibRuntimeToJarRelease
> Task :expo-web-browser:createFullJarRelease
> Task :expo-web-browser:writeReleaseLintModelMetadata
> Task :react-native-app-auth:bundleLibRuntimeToJarRelease
> Task :react-native-app-auth:createFullJarRelease
> Task :react-native-app-auth:writeReleaseLintModelMetadata
> Task :react-native-async-storage_async-storage:bundleLibRuntimeToJarRelease
> Task :react-native-async-storage_async-storage:createFullJarRelease
> Task :react-native-async-storage_async-storage:writeReleaseLintModelMetadata
> Task :react-native-community_slider:bundleLibRuntimeToJarRelease
> Task :react-native-community_slider:createFullJarRelease
> Task :react-native-community_slider:writeReleaseLintModelMetadata
> Task :react-native-gesture-handler:bundleLibRuntimeToJarRelease
> Task :react-native-gesture-handler:createFullJarRelease
> Task :react-native-gesture-handler:writeReleaseLintModelMetadata
> Task :react-native-picker_picker:bundleLibRuntimeToJarRelease
> Task :react-native-picker_picker:createFullJarRelease
> Task :react-native-picker_picker:writeReleaseLintModelMetadata
> Task :react-native-safe-area-context:bundleLibRuntimeToJarRelease
> Task :react-native-safe-area-context:createFullJarRelease
> Task :react-native-safe-area-context:writeReleaseLintModelMetadata
> Task :react-native-screens:bundleLibRuntimeToJarRelease
> Task :react-native-screens:createFullJarRelease
> Task :react-native-screens:writeReleaseLintModelMetadata
> Task :react-native-track-player:bundleLibRuntimeToJarRelease
> Task :react-native-track-player:createFullJarRelease
> Task :react-native-track-player:writeReleaseLintModelMetadata
> Task :react-native-webview:bundleLibRuntimeToJarRelease
> Task :react-native-webview:createFullJarRelease
> Task :react-native-webview:writeReleaseLintModelMetadata
> Task :expo:copyReleaseJniLibsProjectOnly
> Task :expo-application:copyReleaseJniLibsProjectOnly
> Task :expo-av:copyReleaseJniLibsProjectOnly
> Task :expo-blur:copyReleaseJniLibsProjectOnly
> Task :expo-constants:copyReleaseJniLibsProjectOnly
> Task :expo-crypto:copyReleaseJniLibsProjectOnly
> Task :expo-dev-client:copyReleaseJniLibsProjectOnly
> Task :expo-dev-launcher:copyReleaseJniLibsProjectOnly
> Task :expo-dev-menu:copyReleaseJniLibsProjectOnly
> Task :expo-dev-menu-interface:copyReleaseJniLibsProjectOnly
> Task :expo-file-system:copyReleaseJniLibsProjectOnly
> Task :expo-font:copyReleaseJniLibsProjectOnly
> Task :expo-json-utils:copyReleaseJniLibsProjectOnly
> Task :expo-keep-awake:copyReleaseJniLibsProjectOnly
> Task :expo-manifests:copyReleaseJniLibsProjectOnly
> Task :expo-secure-store:copyReleaseJniLibsProjectOnly
> Task :expo-updates-interface:copyReleaseJniLibsProjectOnly
> Task :expo-web-browser:copyReleaseJniLibsProjectOnly
> Task :react-native-app-auth:copyReleaseJniLibsProjectOnly
> Task :react-native-async-storage_async-storage:copyReleaseJniLibsProjectOnly
> Task :react-native-community_slider:copyReleaseJniLibsProjectOnly
> Task :react-native-gesture-handler:copyReleaseJniLibsProjectOnly
> Task :react-native-picker_picker:copyReleaseJniLibsProjectOnly
> Task :react-native-safe-area-context:copyReleaseJniLibsProjectOnly
> Task :react-native-screens:copyReleaseJniLibsProjectOnly
> Task :react-native-track-player:copyReleaseJniLibsProjectOnly
> Task :react-native-webview:copyReleaseJniLibsProjectOnly
> Task :expo-modules-core:configureCMakeRelWithDebInfo[armeabi-v7a]
> Task :react-native-reanimated:configureCMakeRelWithDebInfo[x86]
> Task :app:createBundleReleaseJsAndAssets
> Task :expo-modules-core:buildCMakeRelWithDebInfo[armeabi-v7a]
> Task :react-native-reanimated:buildCMakeRelWithDebInfo[x86]
> Task :expo-modules-core:configureCMakeRelWithDebInfo[x86]
> Task :react-native-reanimated:configureCMakeRelWithDebInfo[x86_64]
> Task :expo-modules-core:buildCMakeRelWithDebInfo[x86]
> Task :expo-modules-core:configureCMakeRelWithDebInfo[x86_64]
> Task :react-native-reanimated:buildCMakeRelWithDebInfo[x86_64]
> Task :react-native-reanimated:mergeReleaseJniLibFolders
> Task :react-native-reanimated:extractDeepLinksForAarRelease
> Task :react-native-reanimated:extractReleaseAnnotations
> Task :react-native-reanimated:mergeReleaseGeneratedProguardFiles
> Task :react-native-reanimated:mergeReleaseConsumerProguardFiles
> Task :react-native-reanimated:mergeReleaseShaders
> Task :react-native-reanimated:compileReleaseShaders NO-SOURCE
> Task :react-native-reanimated:generateReleaseAssets UP-TO-DATE
> Task :react-native-reanimated:packageReleaseAssets
> Task :react-native-reanimated:mergeReleaseNativeLibs
> Task :react-native-reanimated:externalNativeBuildRelease
> Task :react-native-reanimated:generateJsonModelRelease
> Task :react-native-reanimated:prefabReleaseConfigurePackage
> Task :react-native-reanimated:stripReleaseDebugSymbols
> Task :react-native-reanimated:prefabReleasePackage
> Task :react-native-reanimated:prepareLintJarForPublish
> Task :react-native-reanimated:prepareReleaseArtProfile
> Task :react-native-reanimated:processReleaseJavaRes NO-SOURCE
> Task :react-native-reanimated:copyReleaseJniLibsProjectAndLocalJars
> Task :react-native-reanimated:writeReleaseAarMetadata
> Task :react-native-reanimated:mergeReleaseJavaResource
> Task :react-native-reanimated:extractDeepLinksRelease
> Task :react-native-reanimated:syncReleaseLibJars
> Task :react-native-reanimated:bundleReleaseLocalLintAar
> Task :react-native-reanimated:compileReleaseLibraryResources
> Task :react-native-reanimated:bundleLibRuntimeToJarRelease
> Task :react-native-reanimated:writeReleaseLintModelMetadata
> Task :react-native-reanimated:createFullJarRelease
> Task :react-native-reanimated:copyReleaseJniLibsProjectOnly
> Task :expo-modules-core:buildCMakeRelWithDebInfo[x86_64]
> Task :expo-modules-core:mergeReleaseJniLibFolders
> Task :expo-modules-core:extractDeepLinksForAarRelease
> Task :expo-modules-core:extractReleaseAnnotations
> Task :expo-modules-core:mergeReleaseGeneratedProguardFiles
> Task :expo-modules-core:mergeReleaseConsumerProguardFiles
> Task :expo-modules-core:mergeReleaseShaders
> Task :expo-modules-core:compileReleaseShaders NO-SOURCE
> Task :expo-modules-core:generateReleaseAssets UP-TO-DATE
> Task :expo-modules-core:packageReleaseAssets
> Task :expo-modules-core:prepareLintJarForPublish
> Task :expo-modules-core:prepareReleaseArtProfile
> Task :expo-modules-core:processReleaseJavaRes
> Task :expo-modules-core:writeReleaseAarMetadata
> Task :expo-modules-core:mergeReleaseJavaResource
> Task :expo-modules-core:extractDeepLinksRelease
> Task :expo-modules-core:mergeReleaseNativeLibs
> Task :expo-modules-core:syncReleaseLibJars
> Task :expo-modules-core:compileReleaseLibraryResources
> Task :expo-modules-core:writeReleaseLintModelMetadata
> Task :expo-modules-core:stripReleaseDebugSymbols
> Task :expo-modules-core:copyReleaseJniLibsProjectAndLocalJars
> Task :expo-modules-core:bundleLibRuntimeToJarRelease
> Task :expo-modules-core:bundleReleaseLocalLintAar
> Task :expo-modules-core:copyReleaseJniLibsProjectOnly
> Task :expo-modules-core:createFullJarRelease
> Task :app:createBundleReleaseJsAndAssets
Writing bundle output to: /home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle
Writing sourcemap output to: /home/expo/workingdir/build/android/app/build/intermediates/sourcemaps/react/release/index.android.bundle.packager.map
Done writing bundle output
Done writing sourcemap output
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:3428:16: warning: the variable "SharedArrayBuffer" was not declared in function "from"
    if (typeof SharedArrayBuffer !== 'undefined' && (isInstance(value, Shared...
               ^~~~~~~~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:8200:18: warning: the variable "DebuggerInternal" was not declared in function "__shouldPauseOnThrow"
          typeof DebuggerInternal !== 'undefined' &&
^~~~~~~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:18963:7: warning: the variable "setTimeout" was not declared in function "logCapturedError"
      setTimeout(function () {
      ^~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:16923:108: warning: the variable "nativeFabricUIManager" was not declared in function "onChange"
...lInstanceHandle ? (from && nativeFabricUIManager.setIsJSResponder(from.sta...
                              ^~~~~~~~~~~~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:17544:21: warning: the variable "clearTimeout" was not declared in anonymous function " 345#"
cancelTimeout = clearTimeout;
                    ^~~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:21294:30: warning: the variable "__REACT_DEVTOOLS_GLOBAL_HOOK__" was not declared in anonymous function " 345#"
  if ("undefined" !== typeof __REACT_DEVTOOLS_GLOBAL_HOOK__) {
                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:22818:5: warning: the variable "setImmediate" was not declared in function "handleResolved"
    setImmediate(function () {
    ^~~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:26821:5: warning: the variable "fetch" was not declared in anonymous function " 558#"
    fetch,
    ^~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:26822:5: warning: the variable "Headers" was not declared in anonymous function " 558#"
    Headers,
    ^~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:26823:5: warning: the variable "Request" was not declared in anonymous function " 558#"
    Request,
    ^~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:26824:5: warning: the variable "Response" was not declared in anonymous function " 558#"
    Response
    ^~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:26981:24: warning: the variable "FileReader" was not declared in function "readBlobAsArrayBuffer"
      var reader = new FileReader();
                       ^~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:27032:36: warning: the variable "Blob" was not declared in anonymous function " 569#"
        } else if (support.blob && Blob.prototype.isPrototypeOf(body)) {
                                   ^~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:27034:40: warning: the variable "FormData" was not declared in anonymous function " 569#"
        } else if (support.formData && FormData.prototype.isPrototypeOf(body)) {
                                       ^~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:27036:44: warning: the variable "URLSearchParams" was not declared in anonymous function " 569#"
...e if (support.searchParams && URLSearchParams.prototype.isPrototypeOf(body...
                                 ^~~~~~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:27155:26: warning: the variable "AbortController" was not declared in anonymous function " 575#"
          var ctrl = new AbortController();
                         ^~~~~~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:27289:23: warning: the variable "XMLHttpRequest" was not declared in anonymous function " 579#"
        var xhr = new XMLHttpRequest();
                      ^~~~~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:26834:71: warning: the variable "self" was not declared in anonymous function " 561#"
...undefined' && globalThis || typeof self !== 'undefined' && self ||
                                      ^~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:31511:27: warning: the variable "performance" was not declared in anonymous function " 753#"
  if ("object" === typeof performance && "function" === typeof performance.no...
                          ^~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:31534:26: warning: the variable "navigator" was not declared in anonymous function " 753#"
  "undefined" !== typeof navigator && undefined !== navigator.scheduling && u...
                         ^~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:31644:37: warning: the variable "MessageChannel" was not declared in anonymous function " 753#"
  };else if ("undefined" !== typeof MessageChannel) {
                                    ^~~~~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:31659:34: warning: the variable "nativeRuntimeScheduler" was not declared in anonymous function " 753#"
... = "undefined" !== typeof nativeRuntimeScheduler ? nativeRuntimeScheduler....
                             ^~~~~~~~~~~~~~~~~~~~~~
/home/expo/workingdir/build/android/app/build/generated/assets/createBundleReleaseJsAndAssets/index.android.bundle:43613:34: warning: the variable "requestAnimationFrame" was not declared in function "start 9#"
...    this._animationFrame = requestAnimationFrame(this.onUpdate.bind(this));
                              ^~~~~~~~~~~~~~~~~~~~~
> Task :app:checkReleaseAarMetadata
> Task :app:generateReleaseResValues
> Task :app:mapReleaseSourceSetPaths
> Task :app:generateReleaseResources
> Task :app:packageReleaseResources
> Task :app:parseReleaseLocalResources
> Task :app:createReleaseCompatibleScreenManifests
> Task :app:extractDeepLinksRelease
> Task :app:mergeReleaseResources
> Task :app:processReleaseMainManifest FAILED
See https://developer.android.com/r/studio-ui/build/manifest-merger for more information about the manifest merger.
/home/expo/workingdir/build/android/app/src/main/AndroidManifest.xml Error:
	Attribute data@scheme at AndroidManifest.xml requires a placeholder substitution but no value for <appAuthRedirectScheme> is provided.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:processReleaseMainManifest'.
> Manifest merger failed : Attribute data@scheme at AndroidManifest.xml requires a placeholder substitution but no value for <appAuthRedirectScheme> is provided.
* Try:
> Run with
--stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
BUILD FAILED in 7m 44s
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.3/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
955 actionable tasks: 955 executed
Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.

@JayOfemi hiii,
check this: https://discordapp.com/channels/695411232856997968/1234906042526203954
hope this helps,
happy coding!

@Naveen-g09 & @dpuckett Thanks for suggesting this workaround. It does look promising.
@dpuckett I followed your instructions, but I get the below error when running npx patch-project --clean. I have tried a few things such as running the command as Admin, and ensuring that I have full control of the android folder. Did you run into a similar issue by any chance?
Error: EPERM: operation not permitted, rename '...\myapp\android' -> '...\myapp\.patch-project-tmp\android\origin'

Don't close, this needs fixing!

needs to be fixed

@expo-bot stop making this stale please.

^ atleast it listened to you
Came here to say the same problemo

^ atleast it listened to you
Came here to say the same problemo. @dpuckett your solution only seems to work for one build, then it fails in the EAS build process, do you know how to solve that?

I think it's a bug with patch-project. The get a similar problem, but if I refresh the patches it fixes the issue.

Hey guys, i found what is the error,  npm uninstall react-native-app-auth, i had to uninstall auth library that makes a problem. It overwrites something or idk, there are some similar libaries with auth thing so check if you have them uninstall them. Also add scheme thing inside app.json
"scheme": "com.loy365.ppmobileapp",
"intentFilters": [
{
"autoVerify": true,
"action": "VIEW",
"data": [
{
"scheme": "com.loy365.ppmobileapp",
"host": "com.loy365.ppmobileapp"
}
],
"category": ["BROWSABLE", "DEFAULT"]
}
]
},
that is for android

I'm getting the sense that this is originating from blank or incorrect auth provider url/domain origins not being handled correctly in the build process.
The build step may not now how to handle redirect URIs or callback domains for auth providers. I can't say more since I don't understand the Android build process well enough and have limited Java knowledge.
I ran into this issue only after installing Auth0
npm install react-native-auth0
I do think this should be re-opened, as @jayharr-is and @dpuckett have stated, as it seems to be an ongoing issue.

I am also facing this issue and believe this issue should be reopened.

I am also having this issue even though i already added

manifestPlaceholders = [    appAuthRedirectScheme: 'io.identityserver.demo' ]
in android/app/build.gradle

having the exact same issue. manifestPlaceholders solution didn't work :(

Please see this issue where the problem has been discovered it is react-native-app-auth causing the issue.
Uninstalled this package and used expo-auth-session on it's own and problem is solved.
https://github.com/expo/eas-cli/issues/2743


Implement Wiki

Things to add:

Usage and examples of API
Documentation of job struct
Disclaimers/Issues

Maybe move some stuff from the README to there...

Basics are here, create own tickets for the rest.


export uuidv4 function from main module

Type of PR (feature, enhancement, bug fix, etc.)
Enhancement proposal
Description
Export the uuidv4 function from the main module.
Why should this be added
I'm not 100% sure this should be added! But my logic was that if we expose this function as a convenience feature, it might save someone who needs to generate a uuid for any reason on the client from writing their own or importing a dependency.
It could be an over-reach. What do y'all think?
Checklist

[x] My code follows the style guidelines of this project
[x] Checks (StandardRB & Prettier-Standard) are passing
[x] This is not a documentation update

@marcoroth is correct: this is off-topic. I can write it up as a tip in the docs, maybe.

Yeah.. You are probably better off if you add uuid to your package.json.
import { v4 as uuid } from 'uuid';

const myUuid = uuid()


Better diagnostics/exception handling

Hi, The current api does not have any diagnostics in terms of failure to connect. For example if the db name is wrong etc. I have prototyped at least a connect method that can create a DB if it doesn't exist and plan to add several other exception handlers. But I am not sure if you have plans to address this and/or how you will do so.
I didnt want to get too far in a fork without at least asking if you have said plans/and or if you would accept PRs. For the connect method at least I had to touch Transport/HTTP as well as InfluxDB.
If you would let me know if you have interest in this please let me know.
Much appreciated.
-mp

Hi, all PR with fixes, new features and improvements are highly welcome!
I work on this project in sprints every month, I plan to progress on it next during Christmas break.


Base64 encoding is not JWS compliant.

The base64 encoding used for encode the jws result is not compliant with the standard.
The current implementation uses the standard base64. But jws has specified a concrete base64 variant: urlsafe base64 without padding.
You can see it in the Base64 encoding section: http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-40#page-6 and example implementation of it, using C#: http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-40#page-52

Quoting the RFC they describe how to implement this in C# this should be easy to implement in Groovy as well:
     static string base64urlencode(byte [] arg)
     {
       string s = Convert.ToBase64String(arg); // Regular base64 encoder
       s = s.Split('=')[0]; // Remove any trailing '='s
       s = s.Replace('+', '-'); // 62nd char of encoding
       s = s.Replace('/', '_'); // 63rd char of encoding
       return s;
     }

     static byte [] base64urldecode(string arg)
     {
       string s = arg;
       s = s.Replace('-', '+'); // 62nd char of encoding
       s = s.Replace('_', '/'); // 63rd char of encoding
       switch (s.Length % 4) // Pad with trailing '='s
       {
         case 0: break; // No pad chars in this case
         case 2: s += "=="; break; // Two pad chars
         case 3: s += "="; break; // One pad char
         default: throw new System.Exception(
           "Illegal base64url string!");
       }
       return Convert.FromBase64String(s); // Standard base64 decoder
     }

See https://github.com/alvarosanchez/grails-spring-security-rest/blob/cd49837f51db9e1c9d0a759563a5497ce6329c5b/src/main/groovy/grails/plugin/springsecurity/rest/token/generation/jwt/SignedJwtTokenGenerator.groovy

@mgdelacroix what's is the status of this issue?
I have some concerns about this, because I'm using the plugin and telling my customers that we provider JWT auth for the REST API, but the generated token is not compliant against https://jwt.io/
Thanks!

@ppazos it will be implemented next week
Best!

@mgdelacroix TY!


feat: add filetype in yeet-cache window

I added filetype in yeet-cache window so it can be targeted by autocommands, ftplugin files etc.
Thanks for this great plugin!

Good stuff, thanks!


Optimized calls for SVG images

Questions
Answers

Description?
Optimized calls for SVG images

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes PrestaShop/PrestaShop#15869

How to test?
If you have multiples blocks on the same pageBEFORE* Each block call the imageAFTER* Duplicated image are called once per page

Thanks & Welcome @sLorenzini


Document links to a non-existing .json file in its note

The document specifies:

A complete sample JSON file is available in the OfficeDev/Excel-Custom-Functions GitHub repository.

However it links to a non-existing .json file:
https://github.com/OfficeDev/Excel-Custom-Functions/blob/master/src/functions/functions.json

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

ID: cc9afc49-47bc-c0b4-249f-5c66a9421747
Version Independent ID: ae89f268-e83d-1a08-babe-3f1c3dc11796
Content: Metadata for custom functions in Excel - Office Add-ins
Content Source: docs/excel/custom-functions-json.md
Product: excel
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@PeterBrodersen thanks for reporting this issue; we'll look into it and update doc as needed.
@mscharlock can you please look into this issue when you have a chance? Looks like the functions.json file is no longer included in the sample project (OfficeDev/Excel-Custom-Functions), presumably since it's being autogenerated from the JSDoc comments. Thanks!

@kbrandl oh right! Yes, sure thing. :) Thanks for pointing this out, @PeterBrodersen. We have switched up the yo office template a couple times, so this is an out of date link. I'll go ahead and update it.

@PeterBrodersen a fix is in the docs and should go out tomorrow when we do our latest pull in of all our updates. Thank you for reporting this and hope you are enjoying developing with custom functions! I'm going to close this issue but let me know if you would like me to reopen this issue by commenting on it. Thank you again!


MatSelectModule: add header and footer inside select component

Fixed CSS, should be good to go now

@googlebot I signed it!

target: minor

How do I add "target: minor" label?
Also could you review? @crisbeto


XLink race improvements

Updated XLink library with race bug fixes.
TODO - code polish and merge

Hi @themarpe : I'm wondering if Luxonis still continue working on this PR, or it has been substituted with other ones? Thanks!

@developer-mayuan
Its WIP, but not actively developed upon - there are updates on https://github.com/luxonis/xlink, but currently those aren't yet "stable" to be integrated.


pre trained weight

do you have any plan to publish pre-trained weight?

Hi @iammehdii ,
Yes pre-trained weights are already available on the model repo.
I'll put up a clearer mention of this in the readme.
Cheers


ctrl+z return to top of page

Just a Small possible issue / iritation. When i Undo an entry using ctrl + Z my view is moved to the top of the screen or just up. Would be best if the screen stayed on the current view so long as the change was on the current view.

Hi @Di2g10, I'm having trouble being able to replicate this issue. Can you provide exact steps along with details of what browser you're using?

I'm going to close this for now, If you still find the issue and can produce steps to replicate we'll re-open this issue.


Empty line on left of website on small mobile devices

Empty space created on the left side of the whole website page when on small mobile devices minor than 300px width

Image in projects section had min-width for 320px and was sticking out

Change for max-width instead and width in % to make it responsive


Issue or Discussion?

Hi Charles. I'm working through the Getting Started Document and posting comments and questions in the discussions section.

Discussions. Issues are for Bugs and Feature Requests.


Trivial compile fails with VS2017

Tried this with sol3.02 (revision dafb184), using VS2017 15.9.13:
#include "sol.hpp"
int main() {}

It fails to compile with this error:
sol.hpp(11964): error C3779: 'sol::stack::stack_detail::unchecked_unqualified_get': a function that returns 'decltype(auto)' cannot be used before it is defined
Shouldn't this just compile?

Turn off /permissive until Visual Studio 16.3 becomes the official compiler.
See #821 for details.

Seems to be a duplicate of #778, sorry for the noise!


The link https://cloud.vul337.team/, which hosted experiments.tar.gz and models.tar.gz, is no longer accessible.

The link https://cloud.vul337.team/, which hosted experiments.tar.gz and models.tar.gz, is no longer accessible.

Thanks for your feedback. The readme has been updated


Add marked source for ObjC classes [phab:D1708]

Created by salguarnieri at 2017-06-13 18:38:06:
Add basic marked source support for objc containers. A container is an interface, category, or protocol. For now, we are just outputting the name of the class.

zarko commented inline (context lost during migration) at 2017-06-14 03:49:58:
Is there a reason you have this BOX here instead of making the IDENTIFIER the root? (If you found that rendered incorrectly, there could be a bug.)

salguarnieri wrote at 2017-06-14 17:34:04:

Add c++ class test

salguarnieri commented inline (context lost during migration) at 2017-06-14 17:35:32:
I was matching what was done for C++ classes

salguarnieri wrote at 2017-06-14 22:23:23:

Remove empty box for non-qualified classes

salguarnieri commented inline (context lost during migration) at 2017-06-14 22:23:44:
I updated the tests and code so that boxes aren't used if there is no context.

zarko accepted this revision at 2017-06-14 23:09:23

salguarnieri closed via commit 8466c38fb74393ee1fd5764b5e12bbb20252ff5b at 2017-06-14 23:12:37


Error Page Modification

Related Issue

#27
Closes: #[issue number]
Description of Changes

Checklist:

[ ] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] I have included comments in areas that may be difficult to understand.
[ ] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots

Original
Updated

Please provide any necessary screenshots to illustrate the changes made.

@apoorvaron finally completed learnt something new about special type of routing

@apoorvaron any other thing where i work ?

@PatilHarshh

if i write url "http://localhost:8888/tiny/" or "http://localhost:8888/tiny" it should not redirect me to 404.php page
Create your own 404 page :: Simple + Attractive + Creative + responsive + button to Home Page Because current 404 is not responsive etc..

@PatilHarshh

yes working

@PatilHarshh it is not working, lemme share recording

@PatilHarshh it is not working, lemme share recording

I am working brother

@PatilHarshh
https://github.com/apoorvaron/Shorty/assets/83576954/f29bfe43-d691-4402-923f-9eceadd42518

Still no working @apoorvaron , I spend moring in this

@PatilHarshh Just put a condition here that if($new_url is empty)then nothing happens, that's it.

see @apoorvaron

@PatilHarshh Just put a condition here that else if( $new_url is empty)then nothing happens,else redirect to 404. that's it.

add else if and else condition after the current if condition, Don't put inside current if because newURL is not found in the DB then no lines inside if block executes.

still nit working can you send code?

@PatilHarshh i can't give you code, you have to do it yourself.

are you sure there is no need to change in .htaccess and it is working
@apoorvaron

cess and it i
There is no use of .htaccess for 404 redirection

@PatilHarshh update?

@apoorvaron  tried my best but unfortunately, idea is not trickling

@Ayushpanditmoto can you please him in this issue

@apoorvaron ???

@Ayushpanditmoto
@PatilHarshh is trying to add 404 page with solution like ( if a shortname is present in db then redirect to that particular original url if not present then 404.php but he is not able to write code for "http://shrty.rf.gd/" if this url is hit then his code is also redirecting to 404.php page )

@apoorvaron  i fixed this issue can i make a pull request lol

@PatilHarshh just add else {
redirect to 404.php file
}

there is some issues even home page redirect to 404page

@PatilHarshh
This is your hint
you need to fix even the home page redirect to 404.php

 @PatilHarshh This is your hint you need to fix even the home page redirect to 404.php

brother this is done already the issue is what you mentioned now !!!

@PatilHarshh just add else { redirect to 404.php file
}

already done

 @PatilHarshh This is your hint you need to fix even the home page redirect to 404.php

@Ayushpanditmoto brother this is done already the issue is what you mentioned now ( Home Redirection )!!!

@Ayushpanditmoto

@PatilHarshh Hey , I have done the code part because you were stuck so much , now just create a best 404 page UI and replace by current 404 and after that tell me for review. Just do it within 2 days otherwise i will assign this to someone else
Thanks!

ok

@PatilHarshh Are you done with your work ?

yes will raise pr tomorrow or want to see design before raising pr ? @apoorvaron

@PatilHarshh Yes, Send screenshots

Desktop View
Mobile
Tab view

@PatilHarshh Yes, Send screenshots

Desktop View
Mobile
Tab view

@PatilHarshh

@PatilHarshh Yes, Send screenshots

Desktop View
Mobile
Tab view

@PatilHarshh Send !

@PatilHarshh Why did you close this PR?


Support openbuddy mistral 7b

support openbuddy mistral 7b
support transformers>=4.34
add requires in MODEL_MAPPING
rename dataset and model
add sh

support mistral-7b, mistral-7b-chat


Support EqualScalar and NotEqualScalar Primitives with Dask

The EqualScalar primitive currently has Dask related code, but the NotEqualScalar primitive does not. Both are currently marked as unsupported by Dask. Review these primitives to determine if they can be supported using code similar to that in EqualScalar.

Closed by #967


err 101

Hi!
I'm using the default code with Arduino Uno and a DHT11 but keep getting error code 101. I couldn't figure out a way to fix it.

I had similar issues (https://github.com/t-w/SimpleDHT/issues/2, https://github.com/t-w/SimpleDHT/issues/3). If you haven't resolved this, you can try a version with my patch:
https://github.com/t-w/SimpleDHT/tree/mega2560_r3
or slightly different timing in one place on comm. init.:
https://github.com/t-w/SimpleDHT/tree/esp8266
(the second might work for more cases, since the error threshold is lower / the code is more tolerant).
If this works for you (and I will have such signals from others) I can open a merge request, to improve the mainline. For the moment the patched version is only very briefly tested.

Please test 1.0.9


DSP-23996: Ignore unknown fields while deserializing LocalInfo (vsearch)

The goal of this patch is to make LocalInfo class deserialization compatible with the local files that are created by DSE 6.8.
Equivalent patch for ds-trunk (https://github.com/datastax/cassandra/pull/1008)

@JeremiahDJordan / @eolivelli would you mind taking a look at the equivalent PR but for ds-trunk as well https://github.com/datastax/cassandra/pull/1008?


Patroni - postgresql incompatible version

Hi,
we are using patroni with helm,Default postgresql version 10.
before value.yaml
repository: registry.opensource.zalan.do/acid/spilo-10
So, we try to change value.yaml to   repository: registry.opensource.zalan.do/acid/spilo-11
it is giving below error.How we can  change postgresql version.
ERROR
FATAL:  database files are incompatible with server
DETAIL:  The data directory was initialized by PostgreSQL version 10, which is not compatible with this version 11.1 (Ubuntu 11.1-3.pgdg18.04+1)

Resolved.


The remote server returned an error: (400) Bad Request.

Business Event is showing below error
The remote server returned an error: (400) Bad Request.
what could be the reason ?

Thanks for contacting us. Unfortunately, we're unable to handle Support requests for the product here. To contact Support, consider one of the options described here: Support contact options. In particular, you might want to go to the Dynamics 365 for Finance and Operations community page to get help with your questions from the Dynamics community.


Images disappear from meeting notes

Hello,
Client version information: Microsoft Teams Version <IP_ADDRESS>266 on macOS.
When embedding images into meeting notes, leaving the meeting notes, reopening them and then clicking anywhere in the document the image disappears. I am including a screen recording of these steps.

Regards,
David

For issues related to teams product, please reach out to the Product support channels for Microsoft Teams

We are closing this issue for now, Please feel free to reopen it, if required.


Step 3: Upgrade NSX-T (Optional), not required while upgrading PKS

Upgrade of NSX-T tile is not required as PKS never uses NSX-T tile. All the NSX-T configurations are embedded into PKS tile and configured there. https://docs-pcf-staging.cfapps.io/runtimes/pks/1-1/upgrade-pks.html

See https://www.pivotaltracker.com/story/show/158676406. Will be following up with Narayan.

I commented on the story.

Thanks @lparis!


Revert some of the lock version update to work around lerna bootstrap problem

Revert the lock file back to before change change in commit aa5e9fe and only do a scope fix for the build problem for the graphql package lock.

/azp run Build - client packages


Fixed: MXNET R Reference manual broken link

What were proposed in this Pull Request ?

Broken link fixed for R Package Reference manual.

@mli Relevant 2 issues are open due to above broken link issue, once this will get merge. will ask issuer to close issue.

we should remove the R reference manual link. it is not maintained anymore. we are consisdering to generate html pages instead of a pdf file

@mli For time being let's user go ahead with the pdf, even though generate html for 99 pages pdf will take time. I think for now you can merge it and will keep issue open named generate html for reference manual. would that sounds good.

Merged since this is at least better than broken link.


Adaptive lambdas

Realization of adaptive lambdas and dynamic loss function for boundary conditions.

What we have done so far -  we fully revamped adaprive lambdas routine such that it is computed using dispersion part directly with Sobol indices, not neural tangent kernel eigenvalues analogue. It is done since NTK does not work for anything exept single PDE - in NTK case we would have left ODE and systems out.
Secondly, we rework the loss - it is now computed in two faces - one with lambdas for gradient descent and one with normalized for stopping crtiterion. Even though it is a bit of pulls back everything - namely, training process is not quite connected with stop criterion - it would be benefit for parameter unification.
Additionally, we split Dirichlet and initial (we made a step further and split Dirichlet, operator, periodic) boundary conditions in terms of lambda like big guys. Adaptive lambdas are also split.
I hope we making last second fixes and pull new shiny feautes asap.


Consul Graceful Leave

Is there any way I can perform a graceful leave and shutdown for consul agent using this library that performs the following action?
$ curl \
    --request PUT \
    http://<IP_ADDRESS>:8500/v1/agent/leave

Also, when I tried to use force_leave in version 1.1.0, the server responded with 405 because that version still uses get method instead of put (here). Is there any upcoming release that will include this fix?

Hello !
This change has been merged but not yet released on Pypi https://github.com/cablehead/python-consul/pull/224

Any updates on when this will be pushed? I did a pip install today and am still getting this 405 GET not allowed on force_leave.


Turning right on the Vita analogue

For some reason turning right on the Vita analogue doesn't seem to work unless I move stick slightly up or down keeping right. Even though ship is turning somehow, turning is half of what ship can turn to the left side.

Also seeing this, double checked the stick with a tester, but it behaved fine there.


Bump snowflake-connector-python to 3.0.4

What does this PR do?
Bump snowflake-connector-python to 3.0.4

Motivation
We are bumping requests library from 2.28.1 to 2.31.0, however this requires using charset_normalizer>=3.x, which is not supported on snowflake-connector-python==3.0.1. This is fixed in snowflake-connector-python==3.0.4.

Additional Notes
Complement PR on integrations-core: https://github.com/DataDog/integrations-core/pull/14675

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

Verified with Agent Platform team that the failing Code Scanning - Action / CodeQL-Build is a flaky test.


Updating in background?

How would you propose updating the activities in the background?
could you run a background task in react native that calls updateActivity periodically?
Or would you have to setup the push notification flow

If you want to support background tasks at some point I think you can use that library https://github.com/Rapsssito/react-native-background-actions

I can confirm that this is working great.

@anthlasserre I will give this a try, I thought you cannot update anything in background from javascript as it is being "killed" when using React Native.
One solution that I know will work for a fact is to use Apple APN service to send live notification update.
https://developer.apple.com/documentation/activitykit/updating-live-activities-with-activitykit-push-notifications

Yeah indeed, the best solution ever to update Live Activity widgets is to populate the values through push notifications payload. For instance 3rd parties like Braze & OneSignal already support these features.

As this issue is outside the scope of React Native, should we close it, @mrados7 ?

@anthlasserre I agree, you can close this one.

@zackify ?


Chore: ICS V6

Related PRs:

https://github.com/neutron-org/neutron/pull/740
https://github.com/neutron-org/neutron-std/pull/1
https://github.com/neutron-org/neutron-integration-tests/pull/359
https://github.com/neutron-org/neutronjsplus/pull/67
https://github.com/neutron-org/neutronjs/pull/9
https://github.com/neutron-org/neutron-dev-contracts/pull/69

https://github.com/neutron-org/neutron-tests/actions/runs/11258230632


Inheriting configuration from a dependency gem

I am working on different repos, shared with different people. We have a default overcommit configuration on a gem. Everytime a change is made to this config, we have to pass it manually to each repo.
It would be really great to be able to inherit configuration from a remote custom configuration so that a same config can be shared across different repos, exactly as it can be done with RuboCop. In my case, it would be especially interesting to inherit configuration from a dependency gem.
Did you ever think about such a feature ? Does it make sense to you ? Thanks

Hey @rouaneta, thanks for the suggestion.
Open to such a feature, though one would first need to solve the challenge of adding support for inheriting configurations in the first place, which Overcommit does not support today.
Would welcome a well-tested pull request.

Something like travis import directive would be nice:
https://docs.travis-ci.com/user/build-config-imports/


Await database path retrieval

Without awaiting the path retrieval, the database can't be opened. This issue has been introduced by #326.

That's what I was wondering as well. I didn't see any warnings when looking through the code. Dart's linter might not pick up un-awaited Futures in conditional statements.


Add support for custom base image in Truss

Is your feature request related to a problem? Please describe.
I am trying to deploy a NeMO Megatron based model using truss. The installation has a lot of dependencies that I cannot achieve using simply the provided system_packages and python_requirements features that truss provides. I have spent two days trying to resolve these issues but keep going down the rabbit hole of installing more things that happen to not work.
However, NVIDIA provides a base image that does work for all these kinds of models and includes all kinds of run-time optimizations that I would like to benefit from.
Describe the solution you'd like
I would like a custom_base_image config in the config.yaml for truss. If this custom image is provided, truss tries to use it for preparing the truss server, instead of the base gpu image.
It's okay for this custom_base_image to not succeed in all cases. For example, if I use a base image that doesn't have a compatible python version, truss server might fail. I think that's okay given that this is a very advanced feature.

There are a few potential approaches:

Use custom_base_image in place of the base_image_name_and_tag in base.Dockerfile.jinja and then add a few steps to make sure that server deps are installed (pip install requirements.txt should take care of it since the server python requirements are merged with the user right now).
We can use custom_base_image in a multistep docker build and copy certain paths from it to our docker image
We could do the inverse of 2. Start with custom_base_image and copy certain parts of base_image_name_and_tag that we know are needed for the server.

I am against 2 since it requires the user to be more verbose and know the details of the docker image that they are trying to use (which they won't know).
I think 1 is a quick short term solution that we can get out quickly and 3 could be a followup that is more robust (1 what would work if the base image has the python support that we're hoping for).
@pankajroark what do you think?


Write rfc

Have you tried to write a rfc with this spec and submit it? Seems like a more clean and simple alternative to WebDAV, and could have a good traction in some sectors like Node.js or NodeOS... :-)

Well, i have zero experience with the rfc's procedures. But yes it would be absolutely great to have an rfc. (Albeit i think the directory listing part needs a bit of refactoring)

It's not so complicated to write it, you can take anyone as example. Maybe the submit process is more complicated, but one step at a time :-) The readme is really clear and complete, it can be used as basis :-D
By the way, the directory listing (just a list of names) I think is simple :-) I've decided to use the same format on Davius.


acme-sh: 3.0.2 -> 3.0.4

Description of changes
https://github.com/acmesh-official/acme.sh/releases/tag/3.0.4

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 175145 run on x86_64-linux 1

1 package built:

acme-sh


Definition of DataspaceRegistrationService

A DataspaceRegistrationService was not described so far, see also the comment in #72 .
Lets continue the discussion here.
    I have thought about the necessity of a distinct registration service, too. My work-around was to mentally merge it with the IdentityProvider in the sense that a participant can be either `in` (it has an IDS identity) or `out` (the IdentityProvider refuses to create an identity proof)...

Originally posted by @sebbader in https://github.com/International-Data-Spaces-Association/IDS-G/pull/72#discussion_r993501712

Regarding membership list: It should be discussed, how members are exposed. IMHO an automatic exposure of membership, thus participants, might not be the best idea.


Use env.php for storing credentials instead of config

Bucket configuration is env-sensetive and should not be hardcoded in global config (like database connection settings). See https://devdocs.magento.com/guides/v2.3/config-guide/config/config-php.html for more details.

Hi @Koc
@atishgoswami has made a change as part of #67 to fix the sensitive data leak that you described.
Can you install the latest version of this extension and see if that fixes your problem? Feel free to open this ticket again if not.
Regards,
Thai

Hello.
I prefer to have the settings for this extension in the env.php file and locked from the admin panel.
So I did this from a test from-scratch install:
bin/magento config:set -l -n thai_s3/general/access_key MinioAccess
bin/magento config:set -l -n thai_s3/general/secret_key MinioSecret
bin/magento config:set -l -n thai_s3/general/bucket magento
bin/magento config:set -l -n thai_s3/general/region us-east-1
bin/magento config:set -l -n thai_s3/custom_endpoint/endpoint http://minio:9000/
bin/magento config:set -l -n thai_s3/custom_endpoint/region us-east-1
bin/magento config:set -l -n thai_s3/custom_endpoint/enabled 1
bin/magento s3:storage:export

But in the s3:storage:export step it says:

"The AWS credentials you provided did not work. Please review your details and try again. You can do so using our config script."

I am understanding it wrongly and doing something wrong or is there something wrong with the extension?
Thanks a lot!!!

Hey @ibaldonl
You don't have to set the custom_endpoint properties unless you're using an another S3-compatible storage service, e.g. Digital Ocean. If you're not using them, you should clear out those values.
Regards,
Thai

Thanks for your answer @thaiphan !!!
Yes, I use and need the custom_endpoint to point it to Minio https://www.minio.io/ which I use in a Docker Compose environment for development and tests.
Is that the reason why it doesn't work?
Again: thanks!!!

Does the bucket that you're connecting to exist yet? If it does then the export might fail.

It does exist and if I configure the extension in this other way it works:
bin/magento s3:config:set --access-key-id MinioAccess --secret-key MinioSecret \
    --bucket magento --region us-east-1
bin/magento s3:custom-endpoint:enable --endpoint http://minio:9000/ --region us-east-1
bin/magento s3:storage:export
bin/magento s3:storage:enable

But we need to have the settings in the env.php file which is not in version control, so we can have different settings for different environments (we have many).
Thanks!!!

@thaiphan I am doing something wrong or should I open another issue or do you reopen this one?
Thanks!!!


Syntax highlighting for object properties

From @evenfrost on November 25, 2017 21:12
Would be great if we had syntax highlighting for object properties. Right now it looks like this:

And this is how babel-sublime handles this:

Quoted properties here are just as an example of what it looks like to be a proper syntax highlighting for such case.
Copied from original issue: Microsoft/TypeScript-Sublime-Plugin#632

We do have scoped this correctly, as in both headers and 'headers' have same scopes with exception that 'headers' has extra string scope. Themes should be able to handle that correctly.
Scope for headers:
Scope:                         source.ts
                               meta.var.expr.ts
                               meta.objectliteral.ts
                               meta.object.member.ts
                               meta.object-literal.key.ts

Scope for 'headers':
Scope:                         source.ts
                               meta.var.expr.ts
                               meta.objectliteral.ts
                               meta.object.member.ts
                               meta.object-literal.key.ts
                               string.quoted.single.ts

@sheetalkamat I see that the scopes are pretty similar but it may be better to highlight quoted and unquoted properties the same way, what do you think?
Example with default Monokai color scheme:
TypeScript.tmLanguage

JavaScript (Babel).tmLanguage

And that can be achieved in the theme but thats upto the theme maker. But I think most of the editors have default theme that distinguish between the string literals (wherever they are) with any other constructs.


WIP pcln-icons package

Adds a separate icon components package
Intend to help reduce app bundle sizes for perf
Icons can be imported individually
A backwards-compatible Icon component is also included for migration
Uses rollup for the bundled Icon component
Uses official material-design-icons package for non-custom icons
[x] This PR depends on the monorepo setup in #353
[ ] Verify that all icon names are properly aliased for current icon names
[ ] Remove icons from core package
[ ] Add docs for Icon

Fixes #179 #288
Related #375

Closing in favor of #385


[React] Reduce hooks number

In order to implement a Popover, for now to complete require at least three or more hooks. Hope to change hooks such as useClick/useDismiss/useHover/useRole etc. into simpler util functions to easier use.
for the more, may they can change into like this:
import { click, dismiss, hover, mergeRefs, role } from '@floating-ui/react/utils';

function Popover(props) {
  const data = useFloating(props.config);
  const context = data.context;
  const interactions = useInteractions(context, [click, hover, dismiss, role]);

  // this is dummy
  return
{props.children}

}

may relavent: https://github.com/floating-ui/floating-ui/issues/2100

Yeah, #2100 is about reducing configuration necessary. However in the proposal given, it's not clear how you can configure each of the hooks' behavior. How do you pass options?
In its current state, the JavaScript of the library works a lot like CSS, where things are progressively added as you need them. This allows you to compose pieces of functionality common to different floating elements in a way that can create unique or different interactions without duplicating anything. (This also applies to the positioning part of the library.)
The hooks work a bit like Tailwind's CSS utilities. For example, to style a popover, you might have this

In a way these utilities are like the interaction hooks:
const click = useClick(context);
const dismiss = useDismiss(context);
const role = useRole(context);

const interactions = useInteractions([click, dismiss, role]);

Fundamentally, it's about composition and giving you full flexibility. This has the tradeoff/cost of more code to setup, but I feel like copy/pasting the reusable examples and working from them gives you the best baseline to jump off.
I'm open to ideas about how to make this better/easier without sacrificing the goals of the library. What do you think? /cc: @mihkeleidast

To me the proposal is not too much simpler - you still have to import all of the util functions and pass them to interactions hook. Does it matter if they are prefixed with use or (not) called when passing them to useInteractions?
One thing I do like about this proposal is moving the context passing to useInteractions, not to every interaction separately. Maybe this would also open up a way for an options param on that hook, which could hold that common enabled prop I wanted a while back (see #2125)?
It does look a bit simpler to me.
useInteractions([useClick(context), useDismiss(context), useRole(context)]);
useInteractions(context, [useClick(), useDismiss(), useRole()], opts);

react-table handles this nicely

To me the proposal is not too much simpler - you still have to import all of the util functions and pass them to interactions hook. Does it matter if they are prefixed with use or (not) called when passing them to useInteractions?
One thing I do like about this proposal is moving the context passing to useInteractions, not to every interaction separately. Maybe this would also open up a way for an options param on that hook, which could hold that common enabled prop I wanted a while back (see #2125)?
It does look a bit simpler to me.
useInteractions([useClick(context), useDismiss(context), useRole(context)]);
useInteractions(context, [useClick(), useDismiss(), useRole()], opts);

This is indeed not simple to write, but it can be integrated into other functions that are conditionally judged.
Hooks restrict their use to certain circumstances.
For example, to implement a Popover that allows dynamic modification of the trigger type, the use of hooks must be divided into ClickPopover and HoverPopover to make the hooks work correctly (I think we know that they will look similar except for a few hooks), but if not hook, it can be much simpler

For api usebility and fixbility, i think unified's plugins systeam is a good sample

All of the interaction hooks have a enabled option, which you can toggle based on some external condition like the trigger type:
const click = useClick(context, {
  enabled: trigger === 'click',
});
const hover = useClick(context, {
  enabled: trigger === "hover",
});
const interactions = useInteractions([click, hover]);

What's the benefit of conditionally passing utils to useInteractions instead of conditionally enabling them?
If you want to reuse some of that logic in multiple places, you can wrap it in your own hook:
const useMyInteractions = ({
  context,
  trigger = 'click',
}: {
  context: FloatingContext<ReferenceType>;
  trigger?: 'click' | 'hover';
}) => {
  const click = useClick(context, {
    enabled: trigger === 'click',
  });
  const hover = useClick(context, {
    enabled: trigger === "hover",
  });

  return useInteractions([click, hover]);
};

It may be worth waiting for the new "use" hook that should be introduced soon into React. It should allow for a more ergonomic API

I can't help but think that if you want simpler hooks, you could just create a library that composes several of the hooks of this library in they way that you want. I really like the composability of floating-ui.

Going to close this due to some problems with the proposals, but any suggestions can still go in #2100.


Player Strums Modchart

What is your question?
Is there a way to set the player strums to up scroll?
im trying to make a mod chart and the things im doing are not working to set it to up scroll.

This should work.
function onCreatePost()
   for i = 0,3 do
      setPropertyFromGroup('playerStrums', i, 'upScroll', true);
      setPropertyFromGroup('playerStrums', i, 'y', 50);-- the value might not be exact, but you can just change it.
   end
end


Adding custom stats to database

@ochawkeye will probably be the best guy to help me out with this question
I use nfldb for fantasy analysis.  I have my own processes where I compute scores for players, but it can be cumbersome when I have to iterate through every play to calculate 'tiered' statistics, such as distance of each kicking_fgm stat.  I'd like to be able to use the .as_aggregate() function, as it is so much faster than calculating it play-by-play, especially when calculating multi-season stats.  I figure the best thing to do is to create a new {kicking_fgm_50 : 1} stat and add it to the stats dictionary in the nfldb database.
I see two paths forward to address this:
1.)  I can modify nflgame to compute these stats as it parses the raw json and populates nfldb
2.)  I can write an independent script (update-tiered-stats.py) that will iterate through every play in the database and insert each tiered stat to its original play statistics set in the database
I like one because it is clean and straightforward, but I don't know how much I like the idea of editing the base code of the nflgame package.  Not my usual M.O.
I like two because it is a modular add-on script that can be shared online.  However it seems inefficient and a bit of a lazy hack.
So, what are your thoughts on the best way to go about doing this? or maybe you have another idea as to the most efficient way to keep track of FF scoring using the nflx packages?

Someone will have a better answer, but in the meantime you can check out what @JessePresnell did with his forked code, as it looks like he added some fantasy scoring.
https://github.com/JessePresnell/nfldb/commits/master

Thanks.  This is a bit removed from what I'm trying to do, but interesting nonetheless!
My project is a combination of nfldb and an ESPN FF API.  I have one database of player/game information (nfldb), and another database of specific league information for different leagues.  Since scoring is specific to a leagues settings, the scoring procedures must be dynamic.
I'll add a bit more information
I would ultimately like to have my code operate as such:
league_scoring = {'passing_tds': 4, 'rushing_yds': 0.1,..., kicking_fgm_50: 4}

q.game(season_year = 2017, week = 1).player(player_id = 'xyz')
for  pp q.as_aggregate():
    for stat in pp.fields:
        score[stat] = league_scoring[stat] * getattr(pp, stat)

Where the statistic kicking_fgm_50 was already calculated and inserted into the nfldb database, rather than having to compute kicking_fgm_50 every time I want to compute a score
I'm just looking to discuss the best way to get tiered statistics such as kicking_fgm_50, passing_tds_50, punting_inside_20, etc into the database before querying so that when I compute the score it becomes a simple "stat_score = stat_points * stat_value" operation.

You can create a trigger function that does the calculations when new rows are inserted into the applicable table. This will slow down the inserts, though.
You could also create a postgresql function that does the calculations for you based on various parameters. Then query the function instead of the underlying table.
As an aside, why is it a problem to recalculate in python code? I would be surprised if performance was a huge issue for a small number of players and statistics. If you find that you are doing the same calculations over and over, you can cache the function results.

Hey @CMorton737 --
I've updated my query a bit, but I ran into a similar use case where I had multiple scoring systems. The best thing to do is take the structure of the fantasy.sql script and create views that will automatically update named for the scoring system you use. In my case individual_dk represents individual level fantasy stats for Draft Kings. You could do the same for ESPN, Fan Duel, NFL, or whatever scoring system you may use. Creating views seems more optimal than writing additional parsing functionality as the data that's already been parsed is sufficient to build your scoring tables out with. Using views ensures the data stays dynamic.
As for referencing those tables inside of nflgame, I'd have to toy with the code, but I'm sure it's possible.

@sansbacon I like the idea of using a trigger function.  Assuming by 'slowing down inserts' you mean during a live game or when populating nfldb, it which case it I don't see that as much of an issue.  I'll definitely look into it.
I see it as an issue because my ultimate goal is to use my FF analysis package as a backend for a small fantasy football stats website where a user can enter their league ID and get info relevant to their league/waiver wire.  Since NFL player statistics are global, I figure it would be best to calculate the tiered stats one time and insert them to the database, rather than calculate them every time a user requests a score (which could end up being quite frequent)


Prints

A calculated value prints without \n in the end, so it makes reading output of the program harder.

This issue is fixed in master and the Calc2 release. I will consider back-porting it.
You can fix this yourself locally by changing the C printf on line 84 of comp/comp.go to include "\n" to look like this:
fmt.Fprintf(c.fp, "printf("%%d\n", %d);\n", c.compNode(f.Root))

Yep, fixed it on my machine as soon as found it.
Glad to hear you fixed it!