Task :react-native-device-info:compileDebugJavaWithJavac FAILED

| Version  | "react-native-device-info": "^8.4.5" |
| Affected OS | Android |
| OS Version  | 12 |
Current behavior
Hi, just updated my /android/build.gradle file
buildscript {
    ext {
        buildToolsVersion = "30.0.2"
        minSdkVersion = 23
        compileSdkVersion = 31
        targetSdkVersion = 31
        ndkVersion = "21.4.7075529"
    }

and started getting
> Task :react-native-device-info:compileDebugJavaWithJavac FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.7.1/userguide/command_line_interface.html#sec:command_line_warnings
213 actionable tasks: 17 executed, 196 up-to-date
Warning: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns http://schemas.android.com/repository/android/generic/02 to old ns http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/02 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/02 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
Note<EMAIL_ADDRESS>uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note<EMAIL_ADDRESS>uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note<EMAIL_ADDRESS>uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
An exception has occurred in the compiler (1.8.0_242). Please file a bug against the Java compiler via the Java bug reporting page (http://bugreport.java.com) after checking the Bug Database (http://bugs.java.com) for duplicates. Include your program and the following diagnostic in your report. Thank you.
java.lang.AssertionError: annotationType(): unrecognized Attribute name MODULE (class com.sun.tools.javac.util.UnsharedNameTable$NameImpl)
        at com.sun.tools.javac.util.Assert.error(Assert.java:133)
        at com.sun.tools.javac.code.TypeAnnotations.annotationType(TypeAnnotations.java:231)
        at com.sun.tools.javac.code.TypeAnnotations$TypeAnnotationPositions.separateAnnotationsKinds(TypeAnnotations.java:294)

...

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-device-info:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* 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 26s

    at makeError (/Users/icecapp/Documents/projects/rn/napp/node_modules/execa/index.js:174:9)
    at /Users/icecapp/Documents/projects/rn/napp/node_modules/execa/index.js:278:16
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async runOnAllDevices (/Users/icecapp/Documents/projects/rn/napp/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:109:5)
    at async Command.handleAction (/Users/icecapp/Documents/projects/rn/napp/node_modules/@react-native-community/cli/build/index.js:192:9)

Apologies in advance if this issue is not related to react-native-device-info
Any ideas?

I'm actually getting this after installation react-native-bootsplash which asks for
buildscript {
  ext {
    buildToolsVersion = "30.0.2"
    minSdkVersion = 23 // <- AndroidX splashscreen has basic support for 21 (only the background color), so 23 is best
    compileSdkVersion = 31 // <- set at least 31
    targetSdkVersion = 31 // <- set at least 31

Started showing up after updating compileSdkVersion and targetSdkVersion to 31.
I fixed it by upgrading my selected Gradle JDK from 1.8 -> 11 (Preferences -> Build, Execution, Deployment -> Build Tools -> Gradle -> Gradle JDK)

Yep 31 api requires jdk11

Alright so I inited a fresh new project, added few libs before react-native-device-info and I'm still getting the same error as original post
package.json
  "dependencies": {
    "@sentry/react-native": "^3.2.3",
    "promise": "^8.0.3",
    "react": "17.0.2",
    "react-native": "0.66.3",
    "react-native-bootsplash": "^4.0.1",
    "react-native-contacts": "^7.0.2",
    "react-native-country-picker-modal": "^2.0.0",
    "react-native-device-info": "^8.4.8",
    "react-native-flipper": "^0.121.1"
  },

> npx react-native info
info Fetching system and libraries information...
System:
    OS: macOS 12.0.1
    CPU: (4) x64 Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz
    Memory: 27.88 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.2.0 - ~/.asdf/installs/nodejs/16.2.0/bin/node
    Yarn: 1.22.10 - ~/.asdf/shims/yarn
    npm: 7.13.0 - ~/.asdf/installs/nodejs/16.2.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.11.2 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
    Android SDK:
      API Levels: 29, 30, 31
      Build Tools: 29.0.2, 29.0.3, 30.0.2, 30.0.3, 31.0.0
      System Images: android-29 | Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 2020.3 AI-203.7717.56.2031.7784292
    Xcode: 13.1/13A1030d - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.12 - /usr/local/opt/openjdk@11/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.66.3 => 0.66.3
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

and then in Android Studio:

If you are still getting the same error, then you are using JDK1.8. The error literally contains 1.8 in the error.

An exception has occurred in the compiler (1.8.0_242). Please file a bug against the Java compiler via the Java bug reporting page (http://bugreport.java.com) after checking the Bug Database (http://bugs.java.com) for duplicates. Include your > program and the following diagnostic in your report. Thank you.

I can't be more clear on this one: It's a JDK8 issue. You must use JDK11. Something is wrong in your local environment unfortunately. I won't have time to correspond more.

Alright so I inited a fresh new project, manually updated everything to jdk11, added few libs before react-native-device-info and I'm still getting the same error as original post
package.json
  "dependencies": {
    "@sentry/react-native": "^3.2.3",
    "promise": "^8.0.3",
    "react": "17.0.2",
    "react-native": "0.66.3",
    "react-native-bootsplash": "^4.0.1",
    "react-native-contacts": "^7.0.2",
    "react-native-country-picker-modal": "^2.0.0",
    "react-native-device-info": "^8.4.8",
    "react-native-flipper": "^0.121.1"
  },

> npx react-native info
info Fetching system and libraries information...
System:
    OS: macOS 12.0.1
    CPU: (4) x64 Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz
    Memory: 27.88 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.2.0 - ~/.asdf/installs/nodejs/16.2.0/bin/node
    Yarn: 1.22.10 - ~/.asdf/shims/yarn
    npm: 7.13.0 - ~/.asdf/installs/nodejs/16.2.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.11.2 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
    Android SDK:
      API Levels: 29, 30, 31
      Build Tools: 29.0.2, 29.0.3, 30.0.2, 30.0.3, 31.0.0
      System Images: android-29 | Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 2020.3 AI-203.7717.56.2031.7784292
    Xcode: 13.1/13A1030d - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.12 - /usr/local/opt/openjdk@11/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.66.3 => 0.66.3
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

and then in Android Studio:
android/build.gradle
buildscript {
    ext {
        buildToolsVersion = "30.0.2"
        minSdkVersion = 23
        compileSdkVersion = 31
        targetSdkVersion = 31
        ndkVersion = "21.4.7075529"
    }

I am getting the same issue. And I now just remove this dependecy and the app is successfully build.
I am not sure whether it is JDK8 issue, but switching to JDK11 not solving the problem.

Switching to JDK11, if done correctly will solve the problem.
This is definitely not a module bug.
Carefully examine whether JDK11 is actually in use in the build, versus just that you think it is in use. I've already worked with a few people who thought they were using JDK11 but in fact they were not because of some obscure setting or a different way of executing gradle.
The compiler bug in play is intermittent. If this module doesn't trigger it, some other module will eventually.

Maybe there could be some indication in the docs about where to upgrade it exactly, for this lib and react-native-bootsplash (that I know @mikehardy is also involved in) which explicitly requires jdk11
I still haven't figured it out since creating this issue. Asked on SO, reactiflux, slack... no dice. Currently working with a few libs commented out pending resolution of this issue.

After that, running yarn react-native run-android or cd android && ./gradlew installDebug should work, as they use your system $PATH. How people have the Android Studio configured I've no idea, but that's on stack overflow https://stackoverflow.com/a/67414820/9910298

Alright so I inited a fresh new project, manually updated everything to jdk11, added few libs before react-native-device-info and I'm still getting the same error as original post
package.json
  "dependencies": {
    "@sentry/react-native": "^3.2.3",
    "promise": "^8.0.3",
    "react": "17.0.2",
    "react-native": "0.66.3",
    "react-native-bootsplash": "^4.0.1",
    "react-native-contacts": "^7.0.2",
    "react-native-country-picker-modal": "^2.0.0",
    "react-native-device-info": "^8.4.8",
    "react-native-flipper": "^0.121.1"
  },

> npx react-native info
info Fetching system and libraries information...
System:
    OS: macOS 12.0.1
    CPU: (4) x64 Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz
    Memory: 27.88 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.2.0 - ~/.asdf/installs/nodejs/16.2.0/bin/node
    Yarn: 1.22.10 - ~/.asdf/shims/yarn
    npm: 7.13.0 - ~/.asdf/installs/nodejs/16.2.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.11.2 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
    Android SDK:
      API Levels: 29, 30, 31
      Build Tools: 29.0.2, 29.0.3, 30.0.2, 30.0.3, 31.0.0
      System Images: android-29 | Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 2020.3 AI-203.7717.56.2031.7784292
    Xcode: 13.1/13A1030d - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.12 - /usr/local/opt/openjdk@11/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.66.3 => 0.66.3
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

and then in Android Studio:
android/build.gradle
buildscript {
    ext {
        buildToolsVersion = "30.0.2"
        minSdkVersion = 23
        compileSdkVersion = 31
        targetSdkVersion = 31
        ndkVersion = "21.4.7075529"
    }

I am getting the same issue. And I now just remove this dependecy and the app is successfully build. I am not sure whether it is JDK8 issue, but switching to JDK11 not solving the problem.

For whoever not being able to find the location
File --> Structure --> SDK Location --> JDK Location was moved to Gradle Settings --> Tada~

Updating the JDK to the one recommended in RN docs solved the issue for me.
brew tap homebrew/cask-versions
brew install --cask zulu11
https://reactnative.dev/docs/environment-setup#installing-dependencies

Updating the JDK to the one recommended in RN docs solved the issue for me.
brew tap homebrew/cask-versions brew install --cask zulu11
https://reactnative.dev/docs/environment-setup#installing-dependencies

it fixed by issue

If anyone get example same issue please update your JDK 1.8 to JDK 11 and it will work.

Switching to JDK11, if done correctly will solve the problem. This is definitely not a module bug. Carefully examine whether JDK11 is actually in use in the build, versus just that you think it is in use. I've already worked with a few people who thought they were using JDK11 but in fact they were not because of some obscure setting or a different way of executing gradle.
The compiler bug in play is intermittent. If this module doesn't trigger it, some other module will eventually.

turned out I had export JAVA_HOME=$(/usr/libexec/java_home -v 1.8.0) in my .bash_profile. After I replaced it with another version the issue went away. Thanks @mikehardy

For Anybody Still looking for solutions in 2024 try this out,
Add org.gradle.java.home=path of your jdk like this:

It specifies the Java home directory that Gradle should use when executing Java-related tasks, such as compiling Java code or running Java applications.
stackoverflow:
https://stackoverflow.com/questions/18487406/how-do-i-tell-gradle-to-use-specific-jdk-version


VSCode freezes if run as a background process on Linux (0.10.6)

I could start it easily from a terminal as a background process in Fedora 23 (using ampersand). However, after an upgrade to 0.10.6 (64bit), it freezes soon after opening. It was not the case in the previous versions.
I suspect it might be related to the git integration somehow. It freezes if a folder is under git source control. It does not freeze otherwise. When I run it with the verbose option, it stops right before prompting for my repository credentials (which it normally does if not frozen).
vscode:
Version 0.10.6
Commit a80232bbcfe8a5cdad1ebc98638673d9dcb02458
Date 2015-12-19T11:26:42.359Z
Shell 0.34.5
Renderer 45.0.2454.85
Node 4.1.1
git:
2.5.0
Normal start-up (with a git repository address being changed):
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
### VSCode main.js ###
/home/rbazhenov/Software/VSCode-linux-x64/resources/app { pathArguments: [ '/home/rbazhenov/Projects/ec+' ],
  programStart: 0,
  workers: -1,
  enablePerformance: false,
  verboseLogging: true,
  debugPluginHostPort: undefined,
  debugBrkPluginHost: undefined,
  logPluginHostCommunication: false,
  firstrun: false,
  openNewWindow: false,
  openInSameWindow: false,
  gotoLineMode: false,
  pluginHomePath: undefined,
  pluginDevelopmentPath: undefined,
  pluginTestsPath: undefined,
  disablePlugins: false }
Lifecycle#unload() 1
IPC#vscode-workbenchLoaded
Password for 'MYGITREPOADDRESS':

Failed start-up (freezes after opening):
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
### VSCode main.js ###
/home/rbazhenov/Software/VSCode-linux-x64/resources/app { pathArguments: [ '/home/rbazhenov/Projects/ec+' ],
  programStart: 0,
  workers: -1,
  enablePerformance: false,
  verboseLogging: true,
  debugPluginHostPort: undefined,
  debugBrkPluginHost: undefined,
  logPluginHostCommunication: false,
  firstrun: false,
  openNewWindow: false,
  openInSameWindow: false,
  gotoLineMode: false,
  pluginHomePath: undefined,
  pluginDevelopmentPath: undefined,
  pluginTestsPath: undefined,
  disablePlugins: false }
Lifecycle#unload() 1
IPC#vscode-workbenchLoaded

I'm fairly sure I'm having the same issue but instead of just freezing vscode it's also freezing my whole desktop environment(cinnamon)

I also encounter freezing (using latest version now, but always got freezing since December when I start using it)
Using Fedora with default Gnome desktop.
$ uname -a
Linux localhost.localdomain 4.3.5-300.fc23.x86_64 #1 SMP Mon Feb 1 03:18:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Only vscode freezes, not anything else, after a few hours of usage.
Here's the terminal outout:
$ ./code --verbose
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
### VSCode main.js ###
/home/data/apps/VSCode-linux-x64/resources/app { pathArguments: [],
  programStart: 0,
  workers: -1,
  enablePerformance: false,
  verboseLogging: true,
  debugPluginHostPort: undefined,
  debugBrkPluginHost: undefined,
  logPluginHostCommunication: false,
  firstrun: false,
  openNewWindow: false,
  openInSameWindow: false,
  gotoLineMode: false,
  pluginHomePath: undefined,
  pluginDevelopmentPath: undefined,
  pluginTestsPath: undefined,
  disablePlugins: false,
  locale: undefined }
Lifecycle#unload() 1
IPC#vscode-workbenchLoaded
IPC#vscode-openFilePicker
IPC#vscode-openFilePicker
IPC#vscode-openFilePicker

<--- Last few GCs --->

96032349 ms: Mark-sweep 1394.7 (1457.6) -> 1394.7 (1457.6) MB, 2956.1 / 21 ms [allocation failure] [GC in old space requested].
96035276 ms: Mark-sweep 1394.7 (1457.6) -> 1394.7 (1457.6) MB, 2926.9 / 22 ms [allocation failure] [GC in old space requested].
96038180 ms: Mark-sweep 1394.7 (1457.6) -> 1394.7 (1457.6) MB, 2904.4 / 31 ms [last resort gc].
96041079 ms: Mark-sweep 1394.7 (1457.6) -> 1394.7 (1457.6) MB, 2898.1 / 29 ms [last resort gc].

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0xa9cd183a859 <String[7]: file://>
    1: _completed [file:////home/data/apps/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.main.js:~23] [pc=0x187c6d132853] (this=0x1c379e06a469 <JS Object>,e=0x3a3a717041b9 <undefined>)
    2: arguments adaptor frame: 0->1
    6: bound  [native v8natives.js:1208] [pc=0x187c61da8cb0] (this=0xa9cd1846061 <JS Global Object>)

==== Details ========================================...

Failed to get crash dump id.
Report Id:
[VS Code]: detected unresponsive
Lifecycle#window-all-closed
Lifecycle#before-quit
App#dispose: deleting running instance handle

@Tyriar is this solved with the new launcher?

For me it's freezing when launching in a terminal as
./code
and leaving the terminal open.
Will the fix mentioned address freezing in the next release?
Thanks

So the freezing happens when calling with ./code, not just ./code &? What console output are you getting? Does the window and/or UI appear?
What's coming in March may fix your problems, it's a new launch script and CLI. The launch logic past the command line args parsing hasn't changed much.

So the freezing happens when calling with ./code -- yes.
It freezes after a few hours of usage, not instantly. VS Window remains frozen.
Console output is in the above comment, here's another
[marius@localhost VSCode-linux-x64]$ ./code --verbose
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
### VSCode main.js ###
/home/data/apps/VSCode-linux-x64/resources/app { pathArguments: [],
  programStart: 0,
  workers: -1,
  enablePerformance: false,
  verboseLogging: true,
  debugPluginHostPort: undefined,
  debugBrkPluginHost: undefined,
  logPluginHostCommunication: false,
  firstrun: false,
  openNewWindow: false,
  openInSameWindow: false,
  gotoLineMode: false,
  pluginHomePath: undefined,
  pluginDevelopmentPath: undefined,
  pluginTestsPath: undefined,
  disablePlugins: false,
  locale: undefined }
Lifecycle#unload() 1
IPC#vscode-workbenchLoaded
IPC#vscode-openFilePicker
IPC#vscode-openFilePicker

<--- Last few GCs --->

68220044 ms: Mark-sweep 1395.1 (1457.6) -> 1395.1 (1457.6) MB, 3072.1 / 17 ms [allocation failure] [GC in old space requested].
68223139 ms: Mark-sweep 1395.1 (1457.6) -> 1395.1 (1457.6) MB, 3095.2 / 17 ms [allocation failure] [GC in old space requested].
68226240 ms: Mark-sweep 1395.1 (1457.6) -> 1395.1 (1457.6) MB, 3100.4 / 25 ms [last resort gc].
68229369 ms: Mark-sweep 1395.1 (1457.6) -> 1395.1 (1457.6) MB, 3129.3 / 25 ms [last resort gc].

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x1460a833a859 <String[7]: file://>
    1: _completed [file:////home/data/apps/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.main.js:~23] [pc=0x10d614784c73] (this=0x1dcb3a08cef1 <JS Object>,e=0x950159041b9 <undefined>)
    2: arguments adaptor frame: 0->1
    6: bound  [native v8natives.js:1208] [pc=0x10d606d9c670] (this=0x1460a8346061 <JS Global Object>)

==== Details =======================================...

Failed to get crash dump id.

Lifecycle#window-before-close 1
Lifecycle#unload() 1
Lifecycle#window-before-close 1
Lifecycle#unload() 1
[VS Code]: detected unresponsive
Lifecycle#window-all-closed
Lifecycle#before-quit
App#dispose: deleting running instance handle

@RussBaz @mariusa I can't reproduce this, can you try reproduce on the latest insider's build using the deb or rpm packages to install?

@Tyriar  installed the insiders rpm package 2 days ago, and now it froze.
There's no log to show, since I started it using the desktop shortcut.
Note that I haven't restarted vscode since starting it 2 days ago.

@bpasero @joaomoreno have you two seen the issue before that @mariusa has been experiencing?

Is VS Code running out of memory after starting and causing it to crash?

If there's any data I could provide next time (please see previous console output), I'd be glad to, just let me know exactly what/how please.

To clarify: The freeze only happens when you open VS Code on a folder that prompts for git credentials?

That is correct in my case. (some others sound like they may be having other issues?)

I tried to reproduce on Ubuntu 15 and I am not even getting the git login dialog there, but VS Code otherwise works fine. @joaomoreno what is needed to get the dialog on Linux?

The freeze only happens when you open VS Code on a folder that prompts for git credentials?
I have .git folders in the workspace, but it never asks me for credentials, and I use git only from command line. The freeze seems random to me, and unrelated to git.

@bpasero #1796

Maybe people have configured some special git credential helper that causes this?

Closing as duplicate of #1796.


[BUG] An exception occurred while running Bloxstrap

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
Every time I try to reinstall it gives me "An exception occurred while running Bloxstrap" and it gives me and error code System.AggregateException: One or more errors occurred. (The file or directory is corrupted and unreadable. : 'C:\Users\user\AppData\Local\Bloxstrap\Versions\version-d6abc3b106a04c5c\RobloxPlayerBeta.exe')
[Inner Exception]
System.IO.IOException: The file or directory is corrupted and unreadable. : 'C:\Users\user\AppData\Local\Bloxstrap\Versions\version-d6abc3b106a04c5c\RobloxPlayerBeta.exe'
Bloxstrap_20240531T225415Z.log

This is an issue with your system. I can't do anything about this. Do an SFC scan on your disk and see if it detects anything.


[Suggestion] Ability to display armor translucent

I would like to have the ability to make the armor appear translucent not fully invisible, so one can still see what armor the other wears, while also being able to see the skin.

Gotta love minecraft transperency!
ye this feature is probably getting scrapped


Interactivity not working

As I could not find a support Discord Server or anything else, I thought I'd ask it here.
As stated, adding the using statement (using Discord.Addons.Interactive;) is not enough, I have to let the class inherit from InteractiveBase. (Otherwise it does not know AT ALL what NextMessageAsync() is/means.)
The only issue I'm facing now is that I inherit ModuleBase<SocketCommandContext> to actually trigger my commands when someone types them in a channel.
I have tried to work only with inheriting InteractiveBase but then my bot does not respond anymore to any command in that class, not even the command I am using the interactivity in.
Am I missing something here? It's 2AM here for me so that is very likely.
Kind regards.

As I could not find a support Discord Server or anything else, I thought I'd ask it here.
discord.gg/discord-api
The only issue I'm facing now is that I inherit ModuleBase to actually trigger my commands when someone types them in a channel.
So you want to execute a command before the user sends a message? It'd be a lot easier to see what you're trying to do with some code examples... Go ahead and ask again on DAPI if you haven't already. Please close the issue if you already have found a solution.


fix(slack): update slack invite

Updates old slack invite in README to current, working link.

Closing this PR because PR #73 updated the slack link.


Naming convention and import path

#import "Azure Storage Client Library/Azure_Storage_Client_Library.h"

is this actually idiomatic in Objective-C/Cocoa SDK?
I've never seen:

directory names with spaces
header files with underscores

also class names in this library starts with AZ, but the import statement does not have AZ in it.
Take a look at these examples:
#import <UIKit/UIKit.h>
...
UINavigationController* n = ...

#import "AFNetworking/AFNetworking.h>
...
AFHTTPRequestSerializer* s = ...

So I think this library should be something like:
#import "AZStorage/AZStorage.h"

because:

_Client = obvious
_Library = obvious

Sorry for the delay in response.  Excellent point.  We're not going to be able to make the change for the next release (0.1.1, minor bugfixes), but 0.2 will fix this (which we're working on features for now).  We might do something like "AZSClient/AZSClient.h", though, because the prefix we use is actually "AZS".  Would this be more idiomatic?

I think so.

However I really suggest dropping Client as well and calling it AZStorage. In the future if we develop resource provider APIs, we'd probably do something like #import <AZCompute/AZCompute.h>. I suggest looking at how others have been doing so far for this naming convention. I think it's important to get it right.
Cocoa SDK and ecosystem libraries tend to have these single .h files where all exported symbols (types, constants etc) in that framework are referenced (by importing other .h files). So developers can actually just import a single header file and use the whole package.
cc: @devigned


Adding publish iis as a project and minor cleanup

@moozzyk I think you missed a few things.

I did the change in VS Code. I have the same changes in the pipeline.

:up::date:

:ship::it:
(Thanks for fixing this for me :bow:)

no problem!


Problems in problems window not disappearing when closing a document

Use new language server
Open a python file
Confirm messages are displayed in problems window
Close the python file
Problems are still displayed in the problems window (they should vanish)

openFilesOnly is set to true, right?

Will check

Can confirm this is still a problem.

NOTE: This problem also occurs without the new language server (with "python.jediEnabled": true, the default). See the original issue for repro details (https://github.com/Microsoft/vscode-python/issues/2085)

I believe this is not happening anymore. Feel free to open a new ticket if you can still repro it though. Thanks!


Exception handling

Currently some exceptions are swallowed at the top level, we need a way to bubble them up to discord to be logged

This was tentatively handled in #71 but ill leave this open until #58 is resolved as that includes this one conceptually

the scope of this issue has been fixed but there is still work to be done, but #74 resolves this one


Redmine receive mail field

I have redmine site:
Environment:
  Redmine version                2.3.3.devel
  Ruby version                   1.9.3-p448 (2013-06-27) [x86_64-linux]
  Rails version                  3.2.13
  Environment                    production
  Database adapter               Mysql2
SCM:
  Subversion                     1.6.11
  Git                            1.7.1

I updated ruby and redmine, receiving mail not working (it worked before)
/usr/bin/rake -f /var/www/html/redmine/Rakefile --silent redmine:email:receive_pop3 RAILS_ENV="production" host=mail.my.site<EMAIL_ADDRESS>password=mypassword delete_unprocessed=1 --trace
Your FCGI gem does not contain the FCGI shared library, running pure ruby instead
*\* Invoke redmine:email:receive_pop3 (first_time)
*\* Invoke environment (first_time)
*\* Execute environment
*\* Execute redmine:email:receive_pop3
rake aborted!
"\xCE" from ASCII-8BIT to UTF-8
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mail-2.5.4/lib/mail/fields/unstructured_field.rb:149:in `encode!'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mail-2.5.4/lib/mail/fields/unstructured_field.rb:149:in`fold'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mail-2.5.4/lib/mail/fields/unstructured_field.rb:103:in `wrapped_value'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mail-2.5.4/lib/mail/fields/unstructured_field.rb:69:in`do_encode'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mail-2.5.4/lib/mail/fields/unstructured_field.rb:51:in `encoded'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mail-2.5.4/lib/mail/field.rb:167:in`method_missing'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mail-2.5.4/lib/mail/header.rb:206:in `block in encoded'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mail-2.5.4/lib/mail/header.rb:205:in`each'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mail-2.5.4/lib/mail/header.rb:205:in `encoded'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/mail-2.5.4/lib/mail/message.rb:1801:in`encoded'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionmailer-3.2.13/lib/action_mailer/base.rb:434:in `set_payload_for_mail'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionmailer-3.2.13/lib/action_mailer/base.rb:403:in`block in receive'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in`instrument'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/actionmailer-3.2.13/lib/action_mailer/base.rb:401:in`receive'
/var/www/html/redmine/app/models/mail_handler.rb:46:in `receive'
/var/www/html/redmine/lib/redmine/pop3.rb:39:in`block (2 levels) in check'
/usr/local/rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/net/pop.rb:665:in `each'
/usr/local/rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/net/pop.rb:665:in`each_mail'
/var/www/html/redmine/lib/redmine/pop3.rb:36:in `block in check'
/usr/local/rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/net/pop.rb:533:in`start'
/var/www/html/redmine/lib/redmine/pop3.rb:31:in `check'
/var/www/html/redmine/lib/tasks/email.rake:152:in`block (3 levels) in <top (required)>'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/task.rb:236:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/task.rb:236:in`block in execute'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/task.rb:231:in `each'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/task.rb:231:in`execute'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/task.rb:175:in `block in invoke_with_call_chain'
/usr/local/rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/monitor.rb:211:in`mon_synchronize'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/task.rb:168:in `invoke_with_call_chain'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/task.rb:161:in`invoke'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/application.rb:149:in `invoke_task'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/application.rb:106:in`block (2 levels) in top_level'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/application.rb:106:in `each'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/application.rb:106:in`block in top_level'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/application.rb:115:in `run_with_threads'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/application.rb:100:in`top_level'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/application.rb:78:in `block in run'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/application.rb:165:in`standard_exception_handling'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/lib/rake/application.rb:75:in `run'
/usr/local/rvm/gems/ruby-1.9.3-p448/gems/rake-10.1.0/bin/rake:33:in`<top (required)>'
/usr/bin/rake:23:in `load'
/usr/bin/rake:23:in`<main>'
Tasks: TOP => redmine:email:receive_pop3

please help

Double conversion error. Should work if you set the default external encoding or upgrade to Ruby 2.0+ where it's set to UTF-8 by default.


Support transitive subtype witnesses

The fix for #326 is blocked because adding the requested feature there exposes the lack of support for transitive subtype/conformance witnesses, which are actually required by our saturate implementation in the stdlib:
__generic<T : __BuiltinArithmeticType> T clamp(T x, T min, T max);

__generic<T : __BuiltinFloatingPointType>
__specialized_for_target(glsl)
T saturate(T x)
{
    return clamp(x, T(0), T(1));
}

At the call site to clamp, we know that T : __BuiltinFloatingPointType, but the clamp function wants a __BuiltinArithmeticType, and so we need to rely on the fact that __BuiltinFloatingPointType : __BuiltinArithmeticType via inheritance.

The work in #311 is progressing and should fix the front-end side of this. We will build TransitiveSubtypeWitness values as needed during checking, so in this case we'd build a chain that witnesses T : __BuiltinFloatingPointType and then __BuiltinFloatingPointType : __BuiltinArithmeticType.
The missing link at that point is wiring this up to the IR.
The devil is always in the detals, but the big-picture idea would be that IR witness tables should not only contain entries for methods, but also entries for required conformances. That is, given declarations like:
interface IBase { void doBase(); }
interface IDerived : IBase { void doDerived(); }
struct Concrete : IDerived { void doBase() { ... }; void doDerived() { ... } }

the IDerived interface has two requirements. First, it has the obvious method requirement doDerived. Second, it has the inheritance requirement : IBase. each of these corresponds to a declaration inside IDerived (e.g., the inheritance requirement is an InheritanceDecl).
Thus, an IR witness table for the conformance of a concrete type to IDerived should have two entries: one for the method requirement, and one for the inheritance requirement.
The concrete witness table for the Concrete : IDerived conformance should have the method entry point to the IR func for Concrete.doDerived and it should also have an entry for the : IBase requirement that takes the form of a reference to the IR witness table for Concrete : IBase.
Once that representation is in place, it becomes possible to see how to lower/specialize a TransitiveSubtypeWitness like (Concrete : IDerived) (IDerived : IBase). First, we can lower/specialize the Concrete : IDerived part to get an IR value for the appropriate witness table (this is the support we already have), and then next we can use the decl-ref embedded in the IDerived : IBase witness as a key to look up an entry in that witness table to find the Concrete : IBase witness table.
(Aside: if we allowed for type-level computation in the IR, then this would just be an application of the lookup instruction, which could get specialized according to the existing rules...).

I'm going to close this since we have some level of support here, and anything more complete is probably going to get tied up in the IR-level type system work.


perf(consensus): Make late votes outside of last block commits not get to peerMsgQueue

Closes #3154 . Make late votes outside of last blocks precommits not get into the peer msg queue. This lowers the delay for processing more important messages from the peerMsgQueue, and lowers WAL write delays. As noted in the github issue, the number of late votes is actually quite significant.
I don't think theres any test updates needed (all relevant behavior is covered under existing tests. And if you look into the consensus logic, aside from WAL write, all we'd otherwise do is:
		cs.Logger.Debug("vote ignored and not added", "vote_height", vote.Height, "cs_height", cs.Height, "peer", peerID)
                return

We could still do that if we wanted? But doesn't seem that important, since we have the mark late vote still being sent.

PR checklist

[ ] Tests written/updated
[x] Changelog entry added in .changelog (we use unclog to manage our changelog)
[x] Updated relevant documentation (docs/ or spec/) and code comments
[x] Title follows the Conventional Commits spec

Ah correction this is in v0.37.x, and does cause some very slight overhead.

But adding the solution to the consensus reactor is not really the best approach. In fact, the consensus reactor should not take the consensus state lock for every received vote, which is super inefficient in any case. While this PR hasn't introduced this behavior, if we really want to decouple reactor and state, this solution goes towards the wrong direction.

My thinking right now is that we can get the lock removed with #3211 , and then have this able to proceed concurrently (not under the single threaded state.go workload)

We need to check a corner case, though.
If a vote is from the current height but from a previous round, we might still need it. We can use it for deciding a block, if its a Precommit, and for accepting a new Proposal, if it is a Prevote for the PolRound.
See test units TestState_PrevotePOLFromPreviousRound and TestCommitFromPreviousRound, for instance.

@cason could you check this? Then, if we need these votes, we can close this PR. If not, merge this PR.

@cason could you check this? Then, if we need these votes, we can close this PR. If not, merge this PR.

We would have to make a copy of those tests that run with a reactor, instead of manually providing messages to the consensus implementation. This is not so trivial, unfortunately.
But in general I am pretty convinced that we need in some cases messages from previous rounds, these tests are just some examples.

We cannot discard votes from previous rounds because the algorithm may require those votes to progress.
The problem here is that our test units test consensus State where we deliver the messages we want it to process. Adapting these tests to rely on a reactor, i.e., messages received from peers is not simple.
If you manage to adapt the two mentioned tests to run with a consensus Reactor and they do not fail I will be surprised but accept this change.


Unsatisfiable requirements detected for package cuDNN

Hello,
when trying to add FluxPrune to my project that includes Flux, CUDA and cuDNN, there are version conficts that cannot be resolved.
I removed the packages Flux, CUDA, and cuDNN to first add FluxPrune and let it choose the Flux and CUDA version that it supports. But then I have a Unsatifiable requirements when trying to add cuDNN:
Original error message:
pkg> add FluxPrune
Updating registry at ~/.julia/registries/General.toml
Resolving package versions...
ERROR: Unsatisfiable requirements detected for package Flux [587475ba]:
Flux [587475ba] log:
├─possible versions are: 0.4.1-0.14.15 or uninstalled
├─restricted to versions * by an explicit requirement, leaving only versions: 0.4.1-0.14.15
├─restricted by compatibility requirements with FluxPrune [1384c1f3] to versions: 0.12.0-0.13.17
│ └─FluxPrune [1384c1f3] log:
│   ├─possible versions are: 0.1.0 or uninstalled
│   └─restricted to versions * by an explicit requirement, leaving only versions: 0.1.0
├─restricted by compatibility requirements with CUDA [052768ef] to versions: [0.4.1-0.10.4, 0.13.12-0.14.15] or uninstalled, leaving only versions: 0.13.12-0.13.17
│ └─CUDA [052768ef] log:
│   ├─possible versions are: 0.1.0-5.2.0 or uninstalled
│   ├─restricted to versions * by an explicit requirement, leaving only versions: 0.1.0-5.2.0
│   ├─restricted by julia compatibility requirements to versions: [2.3.0, 2.5.0-5.2.0] or uninstalled, leaving only versions: [2.3.0, 2.5.0-5.2.0]
│   ├─restricted by compatibility requirements with cuDNN [02a925ec] to versions: 4.0.0-5.2.0
│   │ └─cuDNN [02a925ec] log:
│   │   ├─possible versions are: 1.0.0-1.3.0 or uninstalled
│   │   ├─restricted to versions * by an explicit requirement, leaving only versions: 1.0.0-1.3.0
│   │   └─restricted by compatibility requirements with CUDA [052768ef] to versions: 1.0.0-1.1.1 or uninstalled, leaving only versions: 1.0.0-1.1.1
│   │     └─CUDA [052768ef] log: see above
│   └─restricted by compatibility requirements with Flux [587475ba] to versions: 2.1.0-4.4.2, leaving only versions: 4.0.0-4.4.2
│     └─Flux [587475ba] log: see above
└─restricted by compatibility requirements with Functors [d9f16b24] to versions: [0.4.1-0.10.4, 0.12.0-0.13.4] or uninstalled — no versions left
└─Functors [d9f16b24] log:
├─possible versions are: 0.1.0-0.4.10 or uninstalled
└─restricted by compatibility requirements with FluxPrune [1384c1f3] to versions: 0.2.8
└─FluxPrune [1384c1f3] log: see above

Yes this project has seen no updates while Flux and CUDA have had many. The existing Project.toml probably needs up to date compatibility bounds. Or ideally, the package should be updated to the latest Flux.

Hello, same here.


Do not send text in file

Text is a message, no need to send in file.

You mean in QuickSave mode?

QuickSave mode? Yes. Any difference ?

Text is a message, no need to send in file.

In a file-transfer app  everything is a file. To send messages you have thousands of messengers out there. Better to have a least one decent file-transfer app then one more crippled messenger.

This is actually already implemented in the upcoming 1.7.0 release.
Like in non-QuickSave mode, a payload must only contain a single text file to be treated as a message.

Duplicate of #67


CVE-2023-6892 Incorrect CPE, Vendor, Product, and Version

The CISA ADP has the wrong CPE/vendor/product for CVE-2023-6892. The vendor and product should be wpfactory and ean_for_woocommerce respectively. This is a different product from woocommerce:

https://wordpress.org/plugins/ean-for-woocommerce/#description
https://wordpress.org/plugins/woocommerce/

EAN for WooCommerce also has an existing CPE (see https://nvd.nist.gov/vuln/detail/CVE-2023-0062) so I swapped that in. Finally, the versions array said "*" or  all versions are affected despite the CNA providing a reasonable version array. I've swapped in the CNA array.

@j-baines thanks again. As with the others, I've referred this to our analysts for upstream updates. I'm merging, but data may be overwritten when the upstream changes are made.


[Question/Clarification] How does one use the output correctly?

I first tried with my own project and switched to the sample from this repo as I kept getting the following error:
Could not load file or assembly file:///....\DNNE\sample\obj\Debug\net6.0\dnne\bin\SampleNE
.dll or any of its dependencies. It is expected that the module would contain an assembly manifest.

(Above error is from the sample project)
Is there any example on in what way the files should be placed, how they should be loaded, for example with Add-Type in powershell (Above error is from Add-Type as I tried loading it through there first), as I couldn't find a clear answer in the docs and issues about this.
Just to clarify - I added the following to the sample project to get it into x86 output as that's what I need for my own project, I also used Powershell (x86) with Add-Type to try and load it.
Changed Sample.csproj:
<Project Sdk="Microsoft.NET.Sdk">

	<PropertyGroup>
		<TargetFramework>net6.0-windows</TargetFramework>
		<EnableDynamicLoading>true</EnableDynamicLoading>
		<PlatformTarget>x86</PlatformTarget>
		<RuntimeIdentifier>win-x86</RuntimeIdentifier>
		<!-- EXPERIMENTAL: The native hosting should assume it is in a self-contained scenario.
         When setting this flag to true, the only change in output will be the generated hosting
         layer will call an API that will permit self-contained runtime activation. In order for this
         option to work as desired the user must have manually configured the assembly's runtimeconfig.json
         file and deps.json file.

Is there any example on in what way the files should be placed, how they should be loaded,

Consider the project found in Sample/. This project will produce several files but only the following are needed at run-time. The below list is for a Windows build.

Sample.dll - The managed assembly that is emitted by the Roslyn compiler.
Sample.deps.json - The dependency list for the managed assembly. This is optional if the assembly only depends on the .NET TFM.
SampleNE.dll - The unmanaged binary that contains the exports that can be called by C/C++.
Sample.runtimeconfig.json - The configuration to know what runtime to load.

I also used Powershell (x86) with Add-Type to try and load it.

PowerShell is a .NET process so loading the managed assembly directly is the preferred option. DNNE is designed to facilitate the loading of a .NET library into an unmanaged (for example, C/C++) process. If the process is .NET, then using DNNE is likely unnecessary. If using DNNE is desired in a managed process the easiest way to achieve that is using DllImport or LibraryImport (.NET 7) to load the unmanaged binary.

sadly it throws this now:

Can you share the C# exports that are being generated? This is likely a case of incorrect pointer manipulation.

I created a Git project and it's on the following repo:
https://github.com/ThaDaVos/clarion-lib-printer-interop

Also, do you really need all the DLLs which are outputed during publish?

Okay, figured that out - for my project I only need the following files (ignore the printerinterop text file, that's a log file):

The thing is, it worked.... don't know what changed, but the generated .runtimeconfig.json changed contents and now it no longer works...
WORKING:
{
  "runtimeOptions": {
    "tfm": "net7.0",
    "rollForward": "LatestMinor",
    "framework": {
      "name": "Microsoft.NETCore.App",
      "version": "7.0.0"
    },
    "configProperties": {
      "System.Globalization.Invariant": true,
      "System.Globalization.PredefinedCulturesOnly": true,
      "System.Reflection.Metadata.MetadataUpdater.IsSupported": false
    }
  }
}

BROKEN:
{
  "runtimeOptions": {
    "tfm": "net7.0",
    "includedFrameworks": [
      {
        "name": "Microsoft.NETCore.App",
        "version": "7.0.0"
      }
    ],
    "configProperties": {
      "System.Globalization.Invariant": true,
      "System.Globalization.PredefinedCulturesOnly": true,
      "System.Reflection.Metadata.MetadataUpdater.IsSupported": false
    }
  }
}

Any idea what changed this?
Also, is there a way to include the Runtime inside the library.dll to ease distribution? Now one needs to install the Desktop Runtime

Any idea what changed this?

Not at all. DNNE doesn't influence anything in the runtimeconfig.json file. This is likely related to some SDK change or another project system setting.

Also, is there a way to include the Runtime inside the library.dll to ease distribution? Now one needs to install the Desktop Runtime

Not at present. If you want a single package, then I would consider NativeAOT for a library. However, that does come with other limitations.

Not at all. DNNE doesn't influence anything in the runtimeconfig.json file. This is likely related to some SDK change or another project system setting.
Gotta figure out what's doing this then - as this change causes it not to work anymore

Not at present. If you want a single package, then I would consider NativeAOT for a library. However, that does come with other limitations.

Sadly NativeOAT is only for X64 - I need X86 - so i need to use DNNE - I read something about that there is experimental single file support - is there any documentation on that?
I also checked ILMerge but it won't take the *NE.dll sadly

it is not self contained at all - don't see the size of the DLL changing

The "self contained" scenario is different from "single file". Self contained means all necessary binaries should be placed in the published output - see here. The single file scenario is about creating a single file that can be deployed, which has all needed managed and native assets within the same binary.

I read something about that there is experimental single file support - is there any documentation on that?

DNNE has experimental support for self contained not single file. I believe that was referenced in the original post. Brief notes can be found below.
https://github.com/AaronRobinsonMSFT/DNNE/blob/73a44e858d7811c646fc5205f347ae098fa494ce/src/msbuild/DNNE.props#L87-L93

I also checked ILMerge but it won't take the *NE.dll sadly

ILMerge only merges IL, not native binaries that DNNE creates to expose the desired exports.

I noticed that the output with self-contained doesn't work though - or does one need to set <SelfContained>true</SelfContained> and <DnneSelfContained_Experimental>false</DnneSelfContained_Experimental> to true and configure it by the note to get it working?
Because currently it crashes - even if the whole output is there and Runtime is installed

I noticed that the output with self-contained doesn't work though
even if the whole output is there and Runtime is installed

From the DNNE perspective the only change is the underlying API called during the initial load of the runtime. This is experimental because, as the referenced comment above notes, the developer must construct the local runtime manually. DNNE won't do that and I don't think setting SelfContained will work because that only applies to applications not libraries.
From the comment describing DnneSelfContained_Experimental.

The user must also copy the appropriate runtime binaries to create a valid self-contained install environment.

@ThaDaVos Closing this as it seems it is handled. Please let me know if there is still confusion about how to use DNNE.


Error bad file descriptor

[error] Error: bad file descriptor
at SFTPStream._transform (c:\Users\corwi.vscode-insiders\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\sftp.js:412:27)
at SFTPStream.Transform._read (internal/streams/transform.js:205:10)
at SFTPStream._read (c:\Users\corwi.vscode-insiders\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\sftp.js:183:15)
at SFTPStream.Transform._write (internal/streams/transform.js:193:12)
at writeOrBuffer (internal/streams/writable.js:358:12)
at SFTPStream.Writable.write (internal/streams/writable.js:303:10)
at Channel.ondata (internal/streams/readable.js:719:22)
at Channel.emit (events.js:315:20)
at addChunk (internal/streams/readable.js:309:12)
at readableAddChunk (internal/streams/readable.js:284:9)
at Channel.Readable.push (internal/streams/readable.js:223:10)
at SSH2Stream. (c:\Users\corwi.vscode-insiders\extensions\liximomo.sftp-1.12.9\node_modules\ssh2\lib\Channel.js:167:15)
at SSH2Stream.emit (events.js:315:20)
at parsePacket (c:\Users\corwi.vscode-insiders\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\ssh.js:3288:10)
at SSH2Stream._transform (c:\Users\corwi.vscode-insiders\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\ssh.js:694:13)
at SSH2Stream.Transform._read (internal/streams/transform.js:205:10)
at SSH2Stream._read (c:\Users\corwi.vscode-insiders\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\ssh.js:253:15)
at SSH2Stream.Transform._write (internal/streams/transform.js:193:12)
at writeOrBuffer (internal/streams/writable.js:358:12)
at SSH2Stream.Writable.write (internal/streams/writable.js:303:10)
at Socket.ondata (internal/streams/readable.js:719:22)
at Socket.emit (events.js:315:20)
at addChunk (internal/streams/readable.js:309:12)
at readableAddChunk (internal/streams/readable.js:284:9)
at Socket.Readable.push (internal/streams/readable.js:223:10)
at TCP.onStreamRead (internal/stream_base_commons.js:188:23) when local ➞ remote c:\Users\corwi\Downloads\ferox\index.js
Can you help me

Same here, this occured when I saved a file.
This was my config:
{
		"name": "workspace",
		"host": "***************",
		"port": 21,
		"type": "sftp",
		"username": "********",
		"password": "*******",
		"path": "/html/workspace",
		"autosave": true,
		"confirm": true

same issue ,-,

same here :-(

Same issue


Content Types Inheriting from Site Page in Modern Sites Inconsistent Behavior

Category

[x] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
Create a content type inheriting from Site Page.  Add this content type to the "Site Pages" library in a modern site.  Select the new content type from the + New button in the library.  Update the page and publish.
Expected behavior - after selecting the alternate content type from the +New dropdown and saving, that page should be saved as the new content type
Observed Behavior
The page is always saved as the "Site Page" content type, regardless of what content type you select from the +New button
Steps to Reproduce

Create a content type inheriting from Site Page.
Add this content type to the "Site Pages" library in a modern site.
Select the new content type from the + New button in the library.
Update the page and publish.

The page is created as the Site Page content type regardless of content type chosen from the drop down.  You can then navigate back to the Site Pages library and switch the new page to the intended content type.

Currently you can not create a site page as a different content type.  You'll want to add this as a feature request to User Voice.

I can see this is fixed in one of my tenants.  Thanks again @patmill


Added ability to pick board directory

I added the ability to choose a board directory each time change board is called.

@rijesha thanks for the submission. I guess it's not clear what you're trying to accomplish here. It breaks the original functionality of parsing Zephyr's board directory.

So there are a couple of problems I was trying to address.
I did manage to put a custom board directory in my app folder. When I did that the existing code showed me a list of my custom boards. When I went to build I got an error saying that the board doesn't exist is the default zephyr board directory. So to fix that I added the board_root_dir. This variable is passed into the west command.
This code still allows parsing the zephyr boards directory. When run the code looks for board directories in the root directory, application directory and in the zephyr directory. (assuming the zephyr directory is located in a subfolder of root) The user selects the board directory and then selects the board they want to use from that directory.

This code still allows parsing the zephyr boards directory. When run the code looks for board directories in the root directory, application directory and in the zephyr directory. (assuming the zephyr directory is located in a subfolder of root) The user selects the board directory and then selects the board they want to use from that directory.

Not when I tested it. Did you test on all 3 platforms to confirm? Does not work on Linux.

Hmm. I only tested on windows. I can try it out on linux and see whats up.
As an aside, the release on the visual studio marketplace, didn't allow me to select any boards from the zephyr directory. (Essentially I couldn't select a zephyr board, because none were populating in the list, and when I had a custom board directory in the app folder, I was able to select a board, but that board directory was not being passed into the west command. So essentially I wasn't able to build anything with the extension.)

So it seems to work on linux for me. I was running linux on a vm, so it was slow (~40s) for the full list of zephyr boards to load. (I don't think the slowness is from the code I added as the getBoardlist function is the same.)
The board directory that was in the app/project directory initially failed to parse, due to the project variable not being initialized. (It got initialized once after I ran change project or build and then started working)

So looking at the original code the directory structure had to be like the following and this is what you have that is no longer working. (Please correct me if I am wrong)
root (or app)
  - app
  - zephyr
    - boards

My directory structure is the following:
root
  - boards
  - app
    - boards
  - deps
    - zephyr
      - boards

I'll push an update to recursively look for board directories one folder down from root.

Closing this, as no updates and seems to break existing functionality.


Filter is not working for EncryptedCharField...

I have used EncryptedCharField in a model. So when i need to filter on that field it returns Blank result of queryset.
models.py
class Employee(models.Model)
    ssn = EncryptedCharField(max_length=11, null=True)

views.py
queryset = Employee.objects.filter(ssn='123')
Here i have a record with '123' data but queryset is alwasy blank.
Thanks in advance.

I don't think that's possible.
Your queryset will create a sql query like select * from app_employee where ssn = '123' but since the value of ssn is encrypted this will never match.
Since the encryption happens in Python it will be pretty hard to make SQL WHERE clauses work on that :(
A project like https://github.com/dcwatson/django-pgcrypto might be better suited for your use case. They use pgcrypto instead of keyczar and let Postgres do the crypto work including support for filtering.


Chore/action cable setup and realtime timers

Changes Unknown when pulling e67079197a706dda6968158f4c74cac77549e451 on chore/action-cable-setup into ** on develop**.

Coverage decreased (-5.8%) to 41.782% when pulling c500e6653ab898c9f80163c3f6ecee96b794c8bc on chore/action-cable-setup into 8c02476052011d6a940a760a9c79531e9d87cb65 on develop.

Coverage increased (+0.1%) to 47.695% when pulling e7aa11276e6f4f502f20a1dbea63089d7d6646d9 on chore/action-cable-setup into 8c02476052011d6a940a760a9c79531e9d87cb65 on develop.


chore: bdd-nh-1585983308 to 0.0.1

chore: Promote bdd-nh-1585983308 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


elm-fs cannot install

Hi dear,
I'm trying to install elm-fs for running a project example,
but without success..
my machine is: Ubuntu 20.10, 64-bit
thanks in advance

Thank you for letting us know.
Currently, the only function of the install command is to register the elm-fs command so that we can use it from any terminal. So an immediate workaround is to do this registration manually.
For manual registration, I would try the approach from https://askubuntu.com/questions/118312/how-can-i-create-a-custom-terminal-command-to-run-a-script/118320#118320
I will look into fixing the install command for Ubuntu 20.

I was able to reproduce the problem on Ubuntu 20. The process is documented at https://github.com/elm-fullstack/elm-fullstack/commit/c2f034b216e3a73bb8f5fcb9820bd5237055e40c

Release 2021-06-16 fixes this issue. The installation on Linux now uses the approach implemented with https://github.com/elm-fullstack/elm-fullstack/commit/0774c4fc344b0cf3f2ea5b5e9ab8aee5f8d86d46
Following are the commands for installing on Ubuntu 20.10:
docker run  -p 5000:5000 -p 4000:4000  --name=ubuntu  -t -i ubuntu:20.10  bash

apt-get update && apt-get install -y wget && apt-get install -y unzip

wget  https://github.com/elm-fullstack/elm-fullstack/releases/download/v2021-06-16/elm-fullstack-bin-0774c4fc344b0cf3f2ea5b5e9ab8aee5f8d86d46-linux-x64.zip

unzip  elm-fullstack-bin-0774c4fc344b0cf3f2ea5b5e9ab8aee5f8d86d46-linux-x64.zip

chmod a+x  elm-fs

./elm-fs  install

The docker run command above also exposes ports for further testing and administration from outside. Skip the docker to work directly on the host system.
Now the system is ready to run productive commands like this one:
elm-fs  run-server  --admin-password=test  --public-urls="http://*:5000"  --deploy-app-from=https://github.com/elm-fullstack/elm-fullstack/tree/6d96fca86dc807208e923caffb94a449d6f4b22d/implement/example-apps/docker-image-default-app

Hi, @Viir
Yeah this works fine,
I liked your project rich-chat-room
Thanks


config: replace labelsPtr, stringPtr with ptr in tests

This PR simplifies tests in the config package.

Thanks for the PR @alexandear. 😄  I'll go ahead and send it through CI.


extraClangArguments option should not disable auto include path detection

Currently, if extraClangArguments is set, the auto include path detection will be disabled. The relevant source code is list in the below.
https://github.com/cquery-project/cquery/blob/9ada8546fdb619d58dae5d3f5114348d0bcc87d1/src/project.cc#L96-L100
On the one hand, this is counterintuitive. Since this variable is called extra clang arguments and is documented with "Additional arguments to pass to clang", the users would not think setting it will overwrite the clang arguments.
On the other hand, I want to pass certain flags to the clang in addition to the auto detected include paths. These flags would be:
-Wall, -Wextra, -Werror, -Wno-long-long, -Wno-variadic-macros, -fexceptions, -DNDEBUG

Alternatively, it would be nice if cquery supports a global fallback .cquery path, which will be used if .cquery is not found in the project root. This is beneficial if users want to do some quick editing or test for some single cpp source files outside of any project. This function would be similar to what YCM current offers.
https://github.com/Valloric/YouCompleteMe/blob/e4c6750a4b3df943deca69195a671b781d16d680/doc/youcompleteme.txt#L2893-L2905

It should be configurable since some projects use special environment (android NDK for example)


Rewrite of image meta

Rewrite of imagemeta

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

298 of 2483 (12.0%)  changed or added relevant lines in 49 files are covered.
57 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-21.2%) to 30.914%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

imagehash/transforms/dct.go
0
1
0.0%

meta/canon/utils.go
0
2
0.0%

xmp/exif.go
0
2
0.0%

heif.go
0
3
0.0%

meta/meta.go
2
5
40.0%

exif2/ifds/mknote/nikon/tags.go
0
5
0.0%

jpeg/log.go
3
9
33.33%

log.go
0
6
0.0%

exif2/ifds/make.go
0
10
0.0%

exif2/ifds/mknote/canon/canon.go
0
10
0.0%

Files with Coverage Reduction
New Missed Lines
%

meta/exifTypes_gen.go
1
55.04%

imagemeta.go
3
0%

jpeg/jpeg.go
4
68.38%

imagehash/imagehash.go
49
0%

Totals

Change from base Build<PHONE_NUMBER>:
-21.2%

Covered Lines:
1712

Relevant Lines:
5538

💛  - Coveralls

[x] Stable ImageTypes API
[x] Exif parsing for jpg, heif, cr2, tiff, and dng
[x] Exif parsing for CR3
[x] Camera Make and Model lookup tables
[x] Stable Imagemeta API
[x] Canon Makernote initial support
[x] Nikon Makernote initial support
[ ] Exif parsing for AVIF (ISOBMFF format)
[ ] Exif parsing for CRW (ciff format)
[ ] Preview image extraction
[ ] Test coverage >50%

Issues addressed:

[x] Exif timezone support Offsets  #26
[x] Parse function in imagemeta #47
[x] Initial Exif parsing of PNG files #41 implemented by @abrander
[x] Add initial AVIF support, will require further testing #44

@evanoberholster I finally had a chance to clone this down and try it out. So far, it works! The Decode() function works nicely and returns timestamp and coordinate data with values as expected. I have yet to try other fields.
Is there a way to get all the extracted EXIF fields? Like a map I can iterate over?
It's OK if these fields don't have any special interpreation: just a key-value store of whatever fields were discovered. This would be easier for me to work with than a huge struct with hard-coded fields. (I think some struct fields are OK, especially if they are common or need interpretation to be useful -- but I'd still like a map of everything that was parsed anyway.)
Sorry if I have a lot of requests :upside_down_face: I think we're getting close to something that works for my use case! :tada:

Thanks for the suggestion, as this is an enhancement that will need further work. Would prefer that it were merged from a new PR request. There for I have opened issue #49
The goal is to merge develop as soon as possible as it is a rewrite.

Makes sense - thanks!

Congrats on the rewrite :smiley:


Support input type="search"

This supports type="text" but not type="search". I have this patched on my local copy - would you accept a PR for this?

Yep, please open a pull request :)


BaseSettings initialisation causes nested BaseModel.model_fields_set to be incorrect

Due to a change in 2784a7013d0bccb5c76c2db78befe0c266baac55 to dump_python any of the init kwargs, any nested structure of models is dumped to a dictionary, including default fields. This dictionary is then later used to instantiate the BaseSettings model itself, which causes all fields on child models to be set.
Take for example the following minimum example:
from pydantic import BaseModel
from pydantic_settings import BaseSettings

if __name__ == "__main__":
    class Child(BaseModel):
        foo: str = "bar"

    class Parent(BaseSettings):
        child: Child

    parent = Parent(child=Child())

    assert not parent.child.model_fields_set

Even though the foo property on Child is never explicitly set, it will show up under model_fields_set.
Would there be some way to retrieve the original behaviour? I actually rely on this to be able to merge models myself. Overriding defaults becomes difficult when model_fields_set is not correct as you can no longer keep a default value apart from a user-defined value that happens to overlap with a default value.

Thanks @MickVermeulen for reporting this. but we reverted this change on https://github.com/pydantic/pydantic-settings/commit/b3a67e92d6d4f58d35c47732fec34d7cda9d7df2 and it is available in pydantic-settings 2.2.1


This test fails, which prevents me from seeing if the resign of the app for iOS was successful

What

This test fails, which prevents me from seeing if the resign of the app for iOS was successful

Logs
00:49 +162: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/users/registration_login_test.dart: Create User & Login Login User
00:49 +162 -1: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/users/registration_login_test.dart: Create User & Login Login User [E]
Expected:
Actual:
package:test_api                                    expect
package:flutter_test/src/widget_tester.dart 455:16  expect
test/users/registration_login_test.dart 33:7        main..

Guys I fear that this is caused by the changes to auth.pl today. If that's true login is broken across all versions.
@teolemon @VaiTon @stephanegigandet
@AshAman999 what exactly happened when the login failed, I think we logged the user out didn't we?
I still seem to be logged in

Okay it's luckily not that bad right now, everything still works on prod.
Though on QueryType.TEST  both login and register are broken.
For reference here the test user credentials https://github.com/openfoodfacts/openfoodfacts-dart/blob/master/test/test_constants.dart

We just need to update this:
  /// Returns a bool if the login data of the provided user is correct
  static Future<bool> login(
    User user, {
    QueryType? queryType,
  }) async {
    final Uri loginUri = UriHelper.getPostUri(
      path: '/cgi/auth.pl',
      queryType: queryType,
    );
    final Response response = await HttpHelper().doPostRequest(
      loginUri,
      <String, String>{},
      user,
      queryType: queryType,
      addCredentialsToBody: true,
    );
    // TODO(monsieurtanuki): refactor as something more refined
    return response.statusCode == 200 && response.body == "";
  }

The last line should now be return response.statusCode == 200;
The issue is that the currently deployed apps will fail as soon as we update the code in production. I think I will add a param to get the response body, something like auth.pl?body=1 , and in a few weeks we can make getting a body the default option.

@M123-dev
Sorry to see the mention late was caught up with exams
Yeah the auth checks if you can log in, if the server just returns the wrong password we log them out else in case there is some different response we just ignore it
Is the issue fixed already?

Yes it is 👍🏼


⚠ Samsung has degraded performance

In da8c547, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2411 ms

Resolved: Samsung performance has improved in 81d9f27.


Unable to install in windows

Its using bignum which internally uses expresso, which when installed is causing errors and uninstalling  to previous state.
Please share some alternate solution for the functionality.
Error Log:
module.js:355
Module._extensions[extension](this, filename)
Error: %1 is not a valid Win32 application.

Occured at bignum.node when i installed individually.

Hi @AlexJangam, thanks for reporting this. It looks like the issue lies with bignum. I guess we could shop around for an alternative to bignum. Happy to accept a pr for one if it looks decent and passes the test suite

https://github.com/alanclarke/int-encoder/pull/2


Chat-wide and chat-and-user-wide sessions?

Hi, is there any way to create 2 sessions, 1 for the entire chat and 1 for each user within the chat?

Hey!
Yes, you can achieve that with custom session key resolver(aka getSessionKey).
const Telegraf = require('telegraf')
const RedisSession = require('telegraf-session-redis')

const bot = new Telegraf(process.env.BOT_TOKEN)

const userSession = new RedisSession({
  property: 'userSession',
  getSessionKey: (ctx) => {
    if (!ctx.from || !ctx.chat) {
      return
    }
    return `${ctx.from.id}:${ctx.chat.id}`
  }
})

const chatSession = new RedisSession({
  property: 'chatSession',
  getSessionKey: (ctx) => {
    if (!ctx.chat) {
      return
    }
    return ctx.chat.id
  }
})

bot.use(userSession.middleware())
bot.use(chatSession.middleware())

bot.on('message', (ctx) => {
  console.log('User Session', ctx.userSession)
  console.log('Chat Session', ctx.chatSession)
})

bot.startPolling()

Hi,
Thanks for the prompt reply. My next question is this:
Is that a scalable approach since each instance of RedisSession would have it's own client/connection to the Redis database?
Apologies if this is an incorrect conclusion, I am new to Redis.
Thanks again!

Don't worry, Redis can deal with hundreds of connections and scales great.

That's good to know. Thanks alot! Great library


adding security api reference #887

Description
Adding references for security APIs
Issues Resolved
https://github.com/opensearch-project/documentation-website/issues/887
Version
all.
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

We can move this to https://opensearch.org/docs/latest/security/access-control/api/
and add examples of the calls, but that section is under "Access Control", although some of the APIs listed on that page have nothing to do with access control

@AntonEliatra - Are you referring to the content under this page or in the issue?
@Naarcha-AWS


[Table] Cursor pointer for selectable rows or cells

Description
Make cursor pointer visible when "selectable" prop is defined. It is visible in List but not on Table, allowing a more intuitive clickable component.

@zediogoviana Thanks for the hint. I collected and shortened your changes for Fomantic-UI here
https://github.com/fomantic/Fomantic-UI/pull/611
See: https://jsfiddle.net/zgdjnvb5/1/


Can save data class in database with inconsistent data

Description
Certain usage of the endpoint to create a child data class can save a new data class in the data_class database table with inconsistent data (inconsistent parent_data_class_id and data_model_id fields).
Steps to reproduce

Create a non-finalised data model having id {{non_finalised_model_id}}
Create a finalised data model containing a data class having {{finalised_data_class_id}}
POST to the create child data class endpoint as follows:
POST api/dataModels/{{non_finalised_model_id}}/dataClasses/{{finalised_data_class_id}}/dataClasses
Body:

{
    "domainType": "DataClass",
    "label": "label",
    "description": "description",
    "minMultiplicity": 123,
    "maxMultiplicity": -1
}

A 201 Created response code is returned. The new data class ID isn't accessible through the API methods on the finalised data class (as expected), but it can be seen in the data_class table (with parent DC ID {{finalised_data_class_id}}, but data model ID {{non_finalised_model_id}}).

Expected behavior
It should not be possible to create a data class in the database with inconsistent parent fields via the API.
Environment

mdm-core latest develop

MI = ModelItem
M = Model
sMI  = sub ModelItem
This is probably an issue on any endpoint which adds a MI to an MI inside a M any url of this form /modelType/modelId/modelItemType/modelItemId/subModelItemType.
This is because we only check that the user can act on the M, not that the MI is inside the M.
We then add the sMI to the MI by getting it using the ID.

Issue locations with correct "find"

Child Annotation -> Would result in a root annotation
Child DataClass ->  Would result in a root annotation
DataClassComponent -> Failed validation as no DF
DataElement -> Failed validation as no DC
DataElementComponent -> Failed validation as no DCC
EnumerationValue -> Failed validation as no DT/ET
ReferenceEnumerationValue -> Failed validation as no RDT/RET
ReferenceSummaryMetadataReport -> Failed validation as no RSM
RuleRepresentation -> Failed validation as no R
SummaryMetadataReport -> Failed validation as no SM
TermRelationship -> termId in URL is unused, the term ids are taken from the body of the json

There is a security potential in getting/updating some of these objects as well. The interceptors need to check the parent objects are inside the models. This would protect the "ending up as root" and should stop the request getting to the controller.
TermRelationship needs additional validation to make sure the terms from the body are inside the terminology


EXC_BAD_ACCESS from xce_stringFromMemberType

I'm getting a "Bad access" exception from the following method:
+ (NSString*)xce_stringFromMemberType:(XcodeMemberType)nodeType {
    NSDictionary* nodeTypesToString = DictionaryWithProjectNodeTypesAsStrings();
    return [[nodeTypesToString allKeysForObject:@(nodeType)] firstObject]; // <-- Crashes here
}

It seems that the nodeTypesToString dictionary is nil. I've tried altering the code in DictionaryWithProjectNodeTypesAsStrings() to make sure it doesn't return nil (although it looks like it shouldn't anyway) but to no avail.
This is the result of calling addSubProject after an Xcode project file has been saved (the project saving code already existed before I discovered this project). The saving is done on a separate thread; I wonder if that might have something to do with it? I've tried delaying the call to addSubProject but that didn't seem to help either.
Any clues as to why this might be happening?

Fixed by adding retain to the end of each initialiser of the static dictionaries. Our project is not compatible with ARC.


[Snyk] Security upgrade nunjucks from 3.2.0 to 3.2.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json
package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Issue
Breaking Change
Exploit Maturity

Arbitrary File Overwrite SNYK-JS-TAR-174125
No
Proof of Concept

Time of Check Time of Use (TOCTOU) npm:chownr:20180731
No
No Known Exploit

Commit messages

Package name: nunjucks
    The new version differs by 7 commits.

53d1223 Release v3.2.1
93129bf Replace yargs with commander
17691da Chokidar bump
40dfdf0 Remove dead link
cefb1cf Prevent optional dependency Chokidar from loading when not watching
1485a44 Add badges in README.md
2246457 Add Mozilla Code of Conduct file

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Duplicate of https://github.com/ministryofjustice/fala/pull/210


Rainbow Crosswalks

Which area of IMT is your request about?  (ex:  Lines, Fillers, UI)
Crosswalks
Describe your idea clearly and concisely.
In many cities around the world councils painted crosswalks with rainbow colors.
Would be nice to include these in our cities as well.
Screenshots?
Many examples can be found e.g. here:
https://www.shutterstock.com/search/rainbow+crosswalk
Choose what you like / can implement.
Why would this idea be a good addition to IMT?
It's bit of fun, or pride, or gives the city a bit of color, whatever.
Anyone opposing this idea: you don't have to use it...

I suppose it would have to be that a rainbow is implemented as a full color and then scale that based on size. Coloring each individual crosswalk line might not be possible. (not a dev btw)


fix: unexpected non primitive analytics properties

Description
While digging into the Clevertap missing events issue, I noticed some logs complaining about non primitive values. I'm not sure what effect they're having in the end - the logs do say "New event processed" but there is also a "wzrk_error" and it's unclear if the event is actually processed. I thought it doesn't hurt to fix anyway. i'll give a heads up to the team that some fields that could be null can now be undefined.
2023-08-02 15:24:48.438918+0200 celo[68492:4526235] [CleverTap]: CleverTap.46W-4W9-4K6Z: New event processed: {"s":1690982683,"n":"_bg","dsync":true,"pg":1,"ep":1690982688,"wzrk_error":{"c":512,"d":"For event \"app_launched\": Property value for property sCountryCodeAlpha2 wasn't a primitive (<null>)"},"type":"profile","lsl":715,"f":false,"profile":{"Carrier":"--","totalPositionsBalanceUsd":0,"deviceLanguage":"en-NZ","phoneCountryCallingCode":"+64","Identity":"0xbd7172dc3b4c48e66f54186f81390e6a2f4781aa","topTenPositions":"","totalBalanceUsd":196.1935559708578,"countryCodeAlpha2":"NL","crealBalance":0,"appVersion":"1.64.0","walletAddress":"0xbd7172dc3b4c48e66f54186f81390e6a2f4781aa","cusdBalance":57.31787889816772,"superchargingAmountInUsd":113.72615675637601,"pincodeType":"PhoneAuth","appBuildNumber":"129","cc":"--","deviceId":"76DFFF49-6F13-4AB1-B7AA-186A378C6AB7","appBundleId":"org.celo.mobile.alfajores","positionsAppsCount":0,"localCurrencyCode":"USD","hasVerifiedNumberCPV":false,"ceurBalance":51.932072082921891,"celoBalance":33.13116614936898,"netWorthUsd":196.1935559708578,"hasCompletedBackup":true,"accountAddress":"0xbd7172dc3b4c48e66f54186f81390e6a2f4781aa","tz":"Europe\/Amsterdam","positionsTopTenApps":"","phoneCountryCodeAlpha2":"NZ","tokenCount":5,"positionsCount":0,"hasVerifiedNumber":false,"language":"en-US","hooksPreviewEnabled":false,"superchargingToken":"cEUR","otherTenTokens":"cUSD_CELO_FP:2.51958,cEUR_CELO_FP:0.31618"}}
Test plan
n/a
Related issues

Fixes RET-746

Backwards compatibility
Y

closing as i don't think this is a blocking error according to https://github.com/CleverTap/clevertap-react-native/blob/9c7794b41fa76bad9fb1d21a1e06eb71a8729839/android/src/main/java/com/clevertap/react/CleverTapModule.java#L1642C33-L1642C70


a colon ":" or slash "/" in job names (job groups) throws an error "invalid characters for local volume"

In gitlab-ci you can group jobs with colon, slash or space: https://docs.gitlab.com/ee/ci/jobs/#group-jobs-in-a-pipeline

package/docker:
package:docker:
package docker:

If you use colon or slash that will cause an error, because slash and colon are invalid character for a local volume name:
Error response from daemon: create gcl-package/docker-100159: "gcl-package/docker-100159" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path

@ck-trigfb You sure about the space? What operating system are you one?

Maybe I have to test it again, because I don’t ready the manual exactly. For groups only numbers are allowed, so that should be possible job names:

package 1/3:
package 1:3:
package 1 3:

I am on a Windows 10 system with WSL2/Ubuntu.

Ok, i did some experiments today: Maybe we have to split this probelm into different issues:

job name can consist of nearly every character. This is a valid jobname "build-my&$"§$" shit:::::" (checked with CI Lint in gitlab).

This results in different problems in gitlab-ci-local because the job name is used for directory names.
If you use images in the job, then also volumes cannot be mounted cause of the invalid characters

Job groups: As described in the gitlab-ci docs (https://docs.gitlab.com/ee/ci/jobs/#group-jobs-in-a-pipeline) you can have job groups with syntax "X Y, X/Y, or X\Y". So something like that is valid  "test1 2". "test1/2", "test1:2",

Same problems as above: invalid character for directory and volume names

Maybe an idea: hash the job names and use the hash as the name for directories and for mounting volumes.

@ck-trigfb
    get safeJobName() {
        if (this.name.match(/[^\w_-]+/)) {
            const buffer = Buffer.from(this.name, "utf8");
            return base32Encode(buffer, "Crockford", {padding: false});
        }
        return this.name;
    }

What about base32 with "Crockford" characters if jobnames fail the "sanity" check ?

Yeah, that should also do the trick ;).


Fix #693: sailsourcemodel concurrency

This PR addresses GitHub issue: #693 .
Briefly describe the changes proposed in this PR:

made all public access methods on SailSourceModel synchronized
added a compliance test that verifies large concurrent transactions do not cause errors or inconsistencies

Note that due to the nature of the problem, the added test may fail/succeed intermittently rather than consistently. I have, when running locally, been able to reproduce the error every two runs of the test, on average, and get consistent succes after applying the synchronization fixes.

Folks, I need some fresh eyes on this problem. See also discussion on issue #693 and #680. It appears that the fixes I did in this PR do not quite solve the problem. I've spent most of the day trying to debug the issue but I'm not really getting anywhere. It's definitely a concurrency issue as it happens intermittently (and, rather nastily, never when I step through with a debugger, so I'm reduced to output trace logging). From what I can tell, in some cases, one of the concurrent threads does not fully sync its pending changes to the master store. It looks as if one of the SailSourceModels created by one of the transactions somehow just gets "lost". I have verified that statements are added to it as normal, but for some reason those changes are never finalized and merged into the master store.
I'm running out of ideas here. Would really appreciate some help. @ansell , @nikolavp , @damyan-ognyanov , @aschwarte10 , if you have some time, have a look please, and tell me what I'm missing.

As an aside: to debug this problem locally (rather than having to work with a remote server) I rolled back the changes I made in this PR. With those fixes the problem does not occur when running locally, but it does still happen when running remote. So I figured the underlying cause is still there, and the synchronization I added merely influences the timing a bit. Easier to debug when running local, so...

Core of the issue seems to be that SailSourceBranch obtains references to all outstanding changes (from concurrent threads) and tries to sync/merge those changes. Part of that process is the flushing and then closing of the Model objects that hold the approved changes, but if the Model uses a NativeSailStore for disk storage, it may be impossible to flush/closes as it internally uses a ReentrantLock, which may currently be held by a different thread.
In previous versions this gave us an IllegalMonitorStateException when it tried to unlock when it had no "right to". We fixed that in #680, but now the issue seems to be that instead of trying to sync and faling, it now simply exits silently - and the changes therefore get dropped.

Investigating a change that is either brilliantly simple or simply stupid: I'm looking at removing the ReentrantLock from NativeSailStore and instead just relying on basic synchronization to ensure serialized writing access to the triplestore. Stay tuned.

In the synchronized code, what is stopping other threads from accessing/mutating the stores concurrently? Ie, not all of the methods are synchronized, but it isn't clear whether there is blocking code to make concurrent threads wait.

@ansell. Nothing. This is merely my first attempt to simplify things. You gotta wonder about the fact that with all the locking removed, suddenly all our tests (including those with concurrent modifications) succeed. But I'm looking at hardening it further with a new, simpler ReentrantLock strategy. Stay tuned.

@ansell added locking. Have another look if you can.

I've ran all unit and integration tests multiple times, without failures. Travis also succeeds, and I have also re-ran the user-submitted test code supplied by @rknowles9 in #693, several times. No errors, and expected outcomes (two contexts with the expected number of statements).

Unless I hear reactions to the contrary, I will merge this in tomorrow and publish it as part of the 2.1.4 patch release.


Long stack traces in Microsoft Edge

Long stack traces don't seem to work in the current version of Edge.
captureStackTrace returns null because the stack detection doesn't find something that it recognises.
Possibly it used to work at one point, as according to https://connect.microsoft.com/IE/feedbackdetail/view/1192551/ie-does-not-add-stack-trace-to-error-object, the Error object used to behave like IE and didn't record the stack on construction.

This is a known limitation. PR welcome.


added html-emmet support for textmate tokens

Added support for html-emmet for monaco-editor using textmate tokens.
Only one line was changed in /src/html.ts file, all the rest changes are auto-generated by rollup.

Please do NOT include dist files
Please add code samples to explain what improvements have been made exactly


docs: clarify use of Extended CONNECT for h/2

Commit Message:
Tweak the HTTP upgrades documentation to mention RFC8841 in the
documentation body (complementing the existing link to the RFC).
Minor fix to the warning text for CONNECT support.
Make explicit mention of "Extended CONNECT" in the API docs for
RouteMatch.
Closes #13044.
Additional Description: n/a
Risk Level: Low
Testing: n/a
Docs Changes: Minor clarification in API docs + Upgrade docs
Release Notes: n/a

cc: @alyssawilk

cc @mattklein123 or @htuch for the extra word in the APIs :-P


Readability/nested namespaces fix

[ ] The tests are passing

Summary
Updated namespace styling to C++17 style.
Also updated CMakeFile to properly set CXX_17 instead of passing a compiler flag, which is kind of a hack.

C++17  ❤

Very nice. I want to know what someone of the current team thinks about it as I don't think I am the right person to merge this.


gen-docs.js ~ widget argument type support

Please follow this template, if applicable.
Description
It looks for the types of args while generating docs
Usage
When adding a widget or anything else that affects the configuration,
please provide a minimal example configuration snippet showcasing how to use it and
Showcase
When adding widgets, please provide screenshots showcasing how your widget looks.
This is not strictly required, but strongly appreciated.
Additional Notes
Sorry for garbage javascript ~ im not very well versed in anything newer than es6
Checklist
Please make sure you can check all the boxes that apply to this PR.

[ ] All widgets I've added are correctly documented.
[ ] The documentation in the docs/content/main directory has been adjusted to reflect my changes.
[ ] I used cargo fmt to automatically format all code before committing

Why does this modify Cargo.lock?

Because im shit at git and have no idea how to fix

When checked out on the can branch run this: git rebase -i eb804ae3467200a7b0d162001fea02575805b2e7
Then drop the first two commits (instead of pick).

This currently crashes :/

Is your node not up to date or smth?

also this just means that propMatch[1] is not a string (i.e. undefined)

Oh hmm ~ will look into it

That ought to fix it

Also, I'd prefer if we turn f64 and i32 into float and int respectively in the docs, just replacing them in the types. f64 and i32 are kinda weird names for "user"-facing docs here.

Thanks a ton, this is much cleaner than it was before! Love deno!


Module for download templates

I have developed an interface for downloading template assets, however at the last moment I realised that it might be too unnecessary xD Since a project will only be compatible with the respective assets of its template, and it doesn't make much sense to give the user the option to choose between all the available ones, the interface looks like this:

I managed to integrate the module with Jamstack and it is called through the --jamdo option in the static.py file of each project. So, taking into account the above, I see as a better way that instead of showing the interface, the command automatically starts downloading the assets @Abdur-rahmaanJ What do you say?

Normally @Jalkhov what NLTK does is to zip all files into zip and to download and extract the zip. Like template and assets

It downsloads them to an internal folder in the package. we can also have cookie cutter versions, zip them, download and create based on them

@Abdur-rahmaanJ
Well, what I had implemented was something different, I uploaded the assets of each template to a repo https://github.com/Jalkhov/jamstack-templates, and what the downloader does is to download the files from the respective folder, to the dist/assets folder of the project, it works quite well, and so in case you want to add more templates just add them to the respective repo. I'm going to make a PR for you to see better because I don't know if I'm explaining myself well.
In any case, I was thinking that instead of creating a special command to download the assets, that they should be downloaded automatically when creating a new project.


add SRS for Mario-like game for tutorials

Description
The pull request includes the submission of the "Software Requirements Specification for Mario-Like Game Tutorial Using Splashkit" document, which outlines the purpose, features, user case, class diagram, and sequence diagrams for the game and tutorial.
Type of change

[x] Documentation (update or new)

How Has This Been Tested?
Formatted using linters with repository config.
Testing Checklist:

[ ] Tested in latest Chrome
[ ] Tested in latest Safari
[x] Tested in latest Firefox

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have requested a review from Phil on the Pull Request

 New Game - SRS


added support for batch evaluation of loss in CEM

I have added support to evaluate loss for all samples together instead of one-by-one. A possible use case is when the loss is being evaluated by a neural network. Please let me know if you want me to make any modifications.

Codecov Report

Merging #5 (85f2cc8) into master (7cb0b03) will decrease coverage by 3.38%.
The diff coverage is 50.00%.

@@             Coverage Diff             @@
##            master       #5      +/-   ##
===========================================
- Coverage   100.00%   96.61%   -3.39%
===========================================
  Files            3        3
  Lines           56       59       +3
===========================================
+ Hits            56       57       +1
- Misses           0        2       +2

Impacted Files
Coverage Δ

src/cross_entropy_method.jl
95.83% <50.00%> (-4.17%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #5 (85f2cc8) into master (7cb0b03) will decrease coverage by 3.38%.
The diff coverage is 50.00%.

@@             Coverage Diff             @@
##            master       #5      +/-   ##
===========================================
- Coverage   100.00%   96.61%   -3.39%
===========================================
  Files            3        3
  Lines           56       59       +3
===========================================
+ Hits            56       57       +1
- Misses           0        2       +2

Impacted Files
Coverage Δ

src/cross_entropy_method.jl
95.83% <50.00%> (-4.17%)
:arrow_down:

Continue to review full report at Codecov.

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


Np 45449 Batch scan data migration

Extended batch scan implementation to parse dynamoDb items to dao classes when reading scanned items. This allows us to migrate data when serialising json in the data field to DbObjects.

Weird equals and hashcode generation maybe has an explanation?

Whops, used IntelliJ default. Changed in new commit


add component svelte-toc

https://github.com/janosh/svelte-toc

I think this is fine to add if you can resolve the conflict.

Should be all set now.


use latest jossl gem and remove the classloader hack with loading som…

…e jossl class first
needs jruby-openssl-0.9.10 released

fixes https://github.com/lookout/fast-rsa-engine/issues/16 since it needs at least jruby-openssl-0.9.10 now
fixes https://github.com/lookout/fast-rsa-engine/issues/15 - there are no more warnings
fixes https://github.com/lookout/fast-rsa-engine/issues/14 - no need to get a patched jruby-openssl class loaded first. is no part of jruby-openssl
no more version check - fixes https://github.com/lookout/fast-rsa-engine/issues/18

This looks good, I'll merge it when it's green


updated react router

-Updated files to pass tests
-Changed react router for home page
Joel Gonzalez

Cannot merge due to missing sample.env file some of Joels tests were failing


suricata-verify tests for the --sync-workers cmdline option

Tests for https://github.com/OISF/suricata/pull/5842

Replaced by https://github.com/OISF/suricata-verify/pull/512