[android] Plugin [id: 'com.facebook.react.settings'] was not found in any of the following sources

Description
build fail on android after upgrading from 0.74.5 to 0.75.1 caused by "/android/settings.gradle' line: 2"
pluginManagement { includeBuild("../../../node_modules/@react-native/gradle-plugin") }
plugins { id("com.facebook.react.settings") }
extensions.configure(com.facebook.react.ReactSettingsExtension){ ex -> ex.autolinkLibrariesFromCommand() }
rootProject.name = 'driver'
include ':app'
includeBuild('../../../node_modules/@react-native/gradle-plugin')

i'm using monorepo, i rechecked node_modules path and it is correct
Steps to reproduce

upgrade to<EMAIL_ADDRESS>react-native run-android

React Native Version
0.75.1
Affected Platforms
Runtime - Android
Output of npx react-native info
...

Stacktrace or Logs
FAILURE: Build failed with an exception.

* Where:
Settings file '/Users/hamoboker/Projects/shoory/shoory-mobile/apps/driver/android/settings.gradle' line: 2

* What went wrong:
Plugin [id: 'com.facebook.react.settings'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Included Builds (No included builds contain this plugin)
- Plugin Repositories (plugin dependency must include a version number for this source)

Reproducer
...
Screenshots and Videos
No response

same issue

check your @react-native/gradle-plugin resolution in yarn.lock/package-lock.json; if you have any lingering other than 0.75.1 (eg i have 0.74.1 left in there) you have to remove node_modules and regenerate your lock file

@lovegaoshi is right. Can you confirm you have @react-native/gradle-plugin version 0.75.1 installed?

@lovegaoshi i already did that, but didn't solve the issue.

@lovegaoshi is right. Can you confirm you have @react-native/gradle-plugin version 0.75.1 installed?

I'll recheck and give you feedback

@lovegaoshi  A working solution. Thank you!

Thank you @lovegaoshi & @cortinico issue has been solved

@cortinico The problem occurred again after reinstalling node_modules.
I created a new project using npx @react-native-community/cli init and faced the same issue. I tried removing ~/.gradle/caches and building again but that didn't solve the problem
Logs from the newly created app
~/Projects/SomeApp git:[main]
yarn android
info A dev server is already running for this project on port 8081.
info Installing the app...

info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor

FAILURE: Build failed with an exception.

* Where:
Settings file '/Users/hamoboker/Projects/SomeApp/android/settings.gradle' line: 2

* What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']
> Could not read workspace metadata from /Users/hamoboker/.gradle/caches/8.8/kotlin-dsl/accessors/b22002a57a45d84a557a6d199ea7ef01/metadata.bin

* 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 596ms
error Failed to install the app. Command failed with exit code 1: ./gradlew app:installDebug -PreactNativeDevServerPort=8081 FAILURE: Build failed with an exception. * Where:
Settings file '/Users/hamoboker/Projects/SomeApp/android/settings.gradle' line: 2 * What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']
> Could not read workspace metadata from /Users/hamoboker/.gradle/caches/8.8/kotlin-dsl/accessors/b22002a57a45d84a557a6d199ea7ef01/metadata.bin * 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 596ms.
info Run CLI with --verbose flag for more details.

Seems related to: https://github.com/gradle/gradle/issues/28974
I don't have a solution at the moment and I also cannot reproduce:
https://github.com/user-attachments/assets/62058329-2649-4e1a-9c6b-e109a4fd70f7
I would have suggested to attempt removing the .gralde/caches folder which you already did.
I'd like to see if other users are also having this problem or not

/settings.gradle/
rootProject.name = 'your_project_name'
apply from: file("../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesSettingsGradle(settings)
include ':app'
includeBuild('../node_modules/@react-native/gradle-plugin')

/Android/app/build.gradle   apply plugin: "com.android.application"
apply plugin: "org.jetbrains.kotlin.android"
apply plugin: "com.facebook.react"
/**

This is the configuration block to customize your React Native Android app.

By default you don't need to apply any configuration, just uncomment the lines you need.
/
react {
/ Folders */
//   The root of your project, i.e. where "package.json" lives. Default is '..'
// root = file("../")
//   The folder where the react-native NPM package is. Default is ../node_modules/react-native
// reactNativeDir = file("../node_modules/react-native")
//   The folder where the react-native Codegen package is. Default is ../node_modules/@react-native/codegen
// codegenDir = file("../node_modules/@react-native/codegen")
//   The cli.js file which is the React Native CLI entrypoint. Default is ../node_modules/react-native/cli.js
// cliFile = file("../node_modules/react-native/cli.js")
/* Variants */
//   The list of variants to that are debuggable. For those we're going to
//   skip the bundling of the JS bundle and the assets. By default is just 'debug'.
//   If you add flavors like lite, prod, etc. you'll have to list your debuggableVariants.
// debuggableVariants = ["liteDebug", "prodDebug"]
/* Bundling */
//   A list containing the node command and its flags. Default is just 'node'.
// nodeExecutableAndArgs = ["node"]
//
//   The command to run when bundling. By default is 'bundle'
// bundleCommand = "ram-bundle"
//
//   The path to the CLI configuration file. Default is empty.
// bundleConfig = file(../rn-cli.config.js)
//
//   The name of the generated asset file containing your JS bundle
// bundleAssetName = "MyApplication.android.bundle"
//
//   The entry file for bundle generation. Default is 'index.android.js' or 'index.js'
// entryFile = file("../js/MyApplication.android.js")
//
//   A list of extra flags to pass to the 'bundle' commands.
//   See https://github.com/react-native-community/cli/blob/main/docs/commands.md#bundle
// extraPackagerArgs = []
/* Hermes Commands */
//   The hermes compiler command to run. By default it is 'hermesc'
// hermesCommand = "$rootDir/my-custom-hermesc/bin/hermesc"
//
//   The list of flags to pass to the Hermes compiler. By default is "-O", "-output-source-map"
// hermesFlags = ["-O", "-output-source-map"]
}

/**

Set this to true to Run Proguard on Release builds to minify the Java bytecode.
*/
def enableProguardInReleaseBuilds = false

/**

The preferred build flavor of JavaScriptCore (JSC)

For example, to use the international variant, you can use:
def jscFlavor = 'org.webkit:android-jsc-intl:+'

The international variant includes ICU i18n library and necessary data
allowing to use e.g. Date.toLocaleString and String.localeCompare that
give correct results when using with locales other than en-US. Note that
this variant is about 6MiB larger per architecture than default.
*/
def jscFlavor = 'org.webkit:android-jsc:+'

android {
ndkVersion rootProject.ext.ndkVersion
buildToolsVersion rootProject.ext.buildToolsVersion
compileSdk rootProject.ext.compileSdkVersion
namespace "com.project2"
defaultConfig {
    applicationId "com.project2"
    minSdkVersion rootProject.ext.minSdkVersion
    targetSdkVersion rootProject.ext.targetSdkVersion
    versionCode 1
    versionName "1.0"
}

signingConfigs {
release {
storeFile file("your-release-key.keystore")
storePassword "1111111"  // Key store key enter
keyAlias "your-key-alias"
keyPassword "1111111"  // Key store key enter
}
}
buildTypes {
release {
signingConfig signingConfigs.release
minifyEnabled enableProguardInReleaseBuilds
proguardFiles getDefaultProguardFile("proguard-android-optimize.txt"), "proguard-rules.pro"
}
}
}
dependencies {
// The version of react-native is set by the React Native Gradle Plugin
implementation("com.facebook.react:react-android")
if (hermesEnabled.toBoolean()) {
    implementation("com.facebook.react:hermes-android")
} else {
    implementation jscFlavor
}

}
apply from: file("../../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesAppBuildGradle(project)

Seems related to: gradle/gradle#28974
I don't have a solution at the moment and I also cannot reproduce:
Screen.Recording.2024-08-16.at.11.04.14.mov
I would have suggested to attempt removing the .gralde/caches folder which you already did. I'd like to see if other users are also having this problem or not

I tried everything listed above but nothing is working.

@sarwanand24
I'm not sure if this will help, but you can also try this
pluginManagement { includeBuild(“../../../node_modules/@react-native/gradle-plugin”) }
plugins { id(“com.facebook.react.settings”) }
extensions.configure(com.facebook.react.ReactSettingsExtension){ ex -> ex.autolinkLibrariesFromCommand() }

Change it like below
pluginManagement {
  includeBuild(new File([“node”, “--print”, “require.resolve(‘@react-native/gradle-plugin/package.json’)”].execute(null, rootDir).text.trim()).getParentFile().toString())
}
plugins { id(“com.facebook.react.settings”) }
extensions.configure(com.facebook.react.ReactSettingsExtension){ ex -> ex.autolinkLibrariesFromCommand() }

Test environment
macos 14.4.1 (M1 Pro)
Using pnpm workspace (monorepo)
bare react-native 0.75.1
node 20.16.0
This got me past the above error, but I got an error on the expo-images side, so I downgraded to bare React Native temporarily.  If you don't use the above packages, it should work :(

@jieey1140 I deleted the gradle many times and rebuild the project then it worked for me.

@lovegaoshi is right. Can you confirm you have @react-native/gradle-plugin version 0.75.1 installed?

This worked for me too!

I have same issue, no metter what i do, i'm getting same error. Removed /node_modules, .gradle. Tried everything, but the error in Andorid remains.

did yall regenerate yarn.lock though
On Sun, Aug 18, 2024, 9:04 AM Djordje Devic @.***>
wrote:

I have same issue, no metter what i do, i'm getting same error. Removed
/node_modules, .gradle. Tried everything, but the error in Andorid remains.
—
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/46046#issuecomment-2295311265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZMOVVUQ7SRSAXQQHAYPQBDZSDAXVAVCNFSM6AAAAABMSK64ACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGMYTCMRWGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes i did, everything from scratch installed with yarn

yarn add<EMAIL_ADDRESS>--exact

Currently my issue is related to gradle cache
Could not read workspace metadata from /Users/hamoboker/.gradle/caches/[GRADLE_VERSION]
getting this error on GRADLE_VERSION = 8.8 and 8.6

@HamoBoker thanks for the update, I'm closing then:

@cortinico i solved my issue by removing rm -rf ~/.gradle/caches and restarting the device
removing ~/.gradle/caches without restarting didn't solve the problem so i guess restart is required after removing folder.

Generally doing:
cd android && ./gradlew --stop && rm -rf ~/.gradle/caches

should be sufficient rather than having to reboot.
Please open separate issues if you're having similar problmes.

Does anyone have this error ?

@HamoBoker thanks for the update, I'm closing then:

@cortinico i solved my issue by removing rm -rf ~/.gradle/caches and restarting the device
removing ~/.gradle/caches without restarting didn't solve the problem so i guess restart is required after removing folder.

Generally doing:
cd android && ./gradlew --stop && rm -rf ~/.gradle/caches

should be sufficient rather than having to reboot.
Please open separate issues if you're having similar problmes.

@cortinico @HamoBoker Thank you so much, your solution works for me.
cd android && ./gradlew --stop && rm -rf ~/.gradle/caches

FAILURE: Build failed with an exception.

Where:
Settings file 'D:\delet\reactnative\android\settings.gradle' line: 2

What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']

still showing same error
"node_modules/@react-native/gradle-plugin": {
"version": "0.75.1",
"resolved"<EMAIL_ADDRESS>"integrity": "sha512-a2gVjX3MB9TF9QZSKje79n1GDAnseTU94VIcFH/4DS3KjbK3yrNXsu1maxGZxDUAKmTUH7Rz4An/Rb5nkZG7dw==",
"dev": true,
"engines": {
"node": ">=18"
}
},

FAILURE: Build failed with an exception.

Where:
Settings file 'D:\delet\reactnative\android\settings.gradle' line: 2

What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']

still showing same error
"node_modules/@react-native/gradle-plugin": {
"version": "0.75.1",
"resolved"<EMAIL_ADDRESS>"integrity": "sha512-a2gVjX3MB9TF9QZSKje79n1GDAnseTU94VIcFH/4DS3KjbK3yrNXsu1maxGZxDUAKmTUH7Rz4An/Rb5nkZG7dw==",
"dev": true,
"engines": {
"node": ">=18"
}
},

Hi @V-SATHISH2109, Last couple days ago, I was facing the same errors.
Below things work for me

Recheck the installed JAVA SDK version,   react-native 0.75 requires a min JAVA sdk version 17.
JAVA -- version

Clean the gradle cache via below command inside the Android.

cd android && ./gradlew --stop && rm -rf ~/.gradle/caches

I have one small doubt i want to use this command in project Android
folders
On Sat, Aug 24, 2024, 9:37 AM Rahul Lodhi @.***> wrote:

FAILURE: Build failed with an exception.

Where:
Settings file 'D:\delet\reactnative\android\settings.gradle' line: 2
What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']
still showing same error
@./gradle-plugin": {
"version": "0.75.1",
"resolved": "
@./gradle-plugin/-/gradle-plugin-0.75.1.tgz
",
"integrity":
"sha512-a2gVjX3MB9TF9QZSKje79n1GDAnseTU94VIcFH/4DS3KjbK3yrNXsu1maxGZxDUAKmTUH7Rz4An/Rb5nkZG7dw==",
"dev": true,
"engines": {
"node": ">=18"
}
},
Hi @V-SATHISH2109 https://github.com/V-SATHISH2109, Last couple days
ago, I was facing the same errors.
Below things work for me

Recheck the installed JAVA SDK version, react-native 0.75 requires a
min JAVA sdk version 17.
JAVA -- version
2.
Clean the gradle cache via below command inside the Android.
cd android && ./gradlew --stop && rm -rf ~/.gradle/caches
—
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/46046#issuecomment-2308043658,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A24F6GDP3CXDHAQKWOYNN73ZTABJ5AVCNFSM6AAAAABMSK64ACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGA2DGNRVHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I have one small doubt i want to use this command in project Android
folders
On Sat, Aug 24, 2024, 9:37 AM Rahul Lodhi @.***> wrote:

FAILURE: Build failed with an exception.

Where:
Settings file 'D:\delet\reactnative\android\settings.gradle' line: 2
What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']
still showing same error
@./gradle-plugin": {
"version": "0.75.1",
"resolved": "
@./gradle-plugin/-/gradle-plugin-0.75.1.tgz
",
"integrity":
"sha512-a2gVjX3MB9TF9QZSKje79n1GDAnseTU94VIcFH/4DS3KjbK3yrNXsu1maxGZxDUAKmTUH7Rz4An/Rb5nkZG7dw==",
"dev": true,
"engines": {
"node": ">=18"
}
},
Hi @V-SATHISH2109 https://github.com/V-SATHISH2109, Last couple days
ago, I was facing the same errors.
Below things work for me

Recheck the installed JAVA SDK version, react-native 0.75 requires a
min JAVA sdk version 17.
JAVA -- version
2.
Clean the gradle cache via below command inside the Android.
cd android && ./gradlew --stop && rm -rf ~/.gradle/caches
—
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/46046#issuecomment-2308043658,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A24F6GDP3CXDHAQKWOYNN73ZTABJ5AVCNFSM6AAAAABMSK64ACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGA2DGNRVHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

No,  you can run from projects's root folder, because this command already includes the change directory command for changing the folder.

FAILURE: Build failed with an exception.

Where:
Settings file 'D:\delet\reactnative\android\settings.gradle' line: 2

What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']

still showing same error
"node_modules/@react-native/gradle-plugin": {
"version": "0.75.1",
"resolved"<EMAIL_ADDRESS>"integrity": "sha512-a2gVjX3MB9TF9QZSKje79n1GDAnseTU94VIcFH/4DS3KjbK3yrNXsu1maxGZxDUAKmTUH7Rz4An/Rb5nkZG7dw==",
"dev": true,
"engines": {
"node": ">=18"
}
},

Hi @V-SATHISH2109, Last couple days ago, I was facing the same errors.
Below things work for me

Recheck the installed JAVA SDK version,   react-native 0.75 requires a min JAVA sdk version 17.
JAVA -- version

Clean the gradle caches via below command.
cd android && ./gradlew --stop && rm -rf ~/.gradle/caches

@react-native/gradle-plugin

Adding it as a devDependency solved it for me

yarn add<EMAIL_ADDRESS>--exact

yarn add<EMAIL_ADDRESS>--exact

This gives the following error

What went wrong:
Included build /Users/raahimkhan/Desktop/Image-Picker-Prototype/node_modules/react-native/node_modules/@react-native/gradle-plugin has build path :gradle-plugin which is the same as included build /Users/raahimkhan/Desktop/Image-Picker-Prototype/node_modules/@react-native/gradle-plugi

I was facing this problem when i upgraded an old project to the latest RN version 0.75.2
and i managed to solve it in android studio, open file > Project Structure > Project and i have set gradle version to 8.2.0

Just started the project with the latest version of React Native
at first build only got this error

What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']

i tried removing gradle caches etc
Nope!

same issue

Claro! Aqui está a tradução do seu passo a passo:

Simple solution:

Restart your PC
Navigate to your project
Delete the .gradle folder
Run cd android
Run gradlew clean
Run yarn android

Thank me later!!

The real solution!!
After deeply investigated this issue, this is my verdict to fix the issue for RN version 0.74.5.
Perform the next steps from the root of your project.

./gradlew --stop && rm -rf ~/.gradle/caches
Empty your yarn.lock file. (Deleting the file will make yarn unhappy)
Delete node_modules.
Run: yarn install
Run: cd android
Run: gradlew clean
Run: yarn android

Happy coding

Does anyone know what's going on here have any idea what to do about it? react-native 0.71.3
Sync Project with Gradle Files  Resulting error

Claro! Aqui está a tradução do seu passo a passo:
Simple solution:

Restart your PC
Navigate to your project
Delete the .gradle folder
Run cd android
Run gradlew clean
Run yarn android

Thank me later!!

I had the same issue unitl I followed these step. Thank you so much issue resolved.

If you are using windows, it has a limit on file path length, which may cause issues.
You can enable long path support:
Press Win + R, type gpedit.msc and OK
Now:
Computer Configuration > Administrative Templates > System > Filesystem > Enable Win32 long paths
Last:
Double-click Enable Win32 long paths and set it to Enabled.

for \android\settings.gradle' line: 2 * What went wrong: Error resolving plugin [id: 'com.facebook.react.settings'] error
just run
npm install<EMAIL_ADDRESS>--exact
or if yarn
yarn add<EMAIL_ADDRESS>--exact

I just ran into this issue when using expo@next and upgrading to new arch then downgrading.
My solution was was  ./gradlew --stop && rm -rf ./gradle/caches && ./gradlew clean
Worth noting I also cleared node_module and deleted and prebuilt the android project to no prevail.

Getting same error

FAILURE: Build failed with an exception.

Where:
Settings file 'C:\Users\hp\Desktop\react-native-world\01\AwesomeProject\android\settings.gradle' line: 2

What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']

java.io.UncheckedIOException: Could not move temporary workspace (C:\Users\hp\Desktop\react-native-world\01\AwesomeProject\android.gradle\8.10.2\dependencies-accessors\569c8b261a8a714d7731d5f568e0e5c05babae10-2a394f4b-039c-4c6d-9410-de2b202a8c22) to immutable location (C:\Users\hp\Desktop\react-native-world\01\AwesomeProject\android.gradle\8.10.2\dependencies-accessors\569c8b261a8a714d7731d5f568e0e5c05babae10)

"dependencies": {
"@react-native/gradle-plugin": "^0.75.1",
"react": "18.3.1",
"react-native": "0.76.1"
},

"dependencies": {
"expo": "~51.0.39",
 "react": "18.2.0",
 "react-native": "0.74.5",
} I need help

I tried deleting package-lock.json and reinstalling the dependencies and it worked out fine for me.
Platform -> windows
react-native-> 0.76
gradle-> 8.10

https://stackoverflow.com/a/79235480/11043676
this resolve the issues without the downgrading any versions. i noticed this issue occurs due to misconfiguration of gradle files

Hey everyone, I found a simple solution to this issue: just delete the .gradle folder inside the android directory and run the following command: npx react-native run-android. This worked for me.

Hey everyone, I found a simple solution to this issue: just delete the .gradle folder inside the android directory and run the following command: npx react-native run-android. This worked for me.

So do we need to delete the .gradle directory each time when we install a new plugging? and reassemble it? is there any alternative solutions for resolve it properly @Cyber-Nut

I had the same issue. And I solved it! Just uninstall the Java extensions in VSCode, reload VSCode, and that's it! You might need to do a clean install, but this worked for me. I didn't have any issues doing a clean install without the Java extensions.

@cortinico @HamoBoker Thanks, your solution works for me. Thank you so much, you saved my day!

For me, running the following command worked:
@react-native/gradle-plugin -D

screen-capture (1).webm
same issue


Create a Ping Command

Create a Ping command for the bot to return the about of latency in milliseconds. Display it in an Embed

I want to work on this
Assign it to me

Alright @satyamrs00
The bot will be invited into the MLSC server soon, and you can test your developments there


Fed Commons template - Output to template not working

Writing the Fed Commons template is no longer working. It should be acknowledged that even getting the template to work will not result in the same processes as in the JSON-LD export.
Anticipated limitations of template:
(1) These processes would not have consistent flow names within the same life cycle stage, because process linking by specifying the default provider is not supported by the template.
(2) Scoring data quality using the EPA data quality schema for openLCA is not possible
(3) Elementary flows will not link to Fed Commons Elementary Flows because the template does not create or link to existing flow UUIDs

I added the old code for this to a new branch

@TJTapajyoti @jump2conclusionsmatt. @gschivley @hottleta  No one in the Fed Commons group is using or supporting the Excel LCI template anymore, so I propose not supporting writing to that template and deleting the branch where that code is at (its always available in the git history)

No longer supporting use of this template, closing issue


Enable Selective Opacity

[x] convert all 2D colormaps to RGBA format
[x] disable RGBA format for 3D colormaps until plotly can support

@Luthaf I've made it through the first pass on the branch feat/rgba. Currently, there are no opacity-affected colormaps, so I included a commented line in src/maps/colorscales.ts to uncomment to demonstrate the new functionality. Thoughts on the structure? If it looks good I'll move ahead with opacity modes.

Why do you say that this wouldn't work in 3D? seems it's enough to set
trace opacity to 0.99999 and then it honors the alpha channel
https://github.com/plotly/plotly.js/issues/3492
On Thu, 27 Aug 2020 at 17:11, rosecers<EMAIL_ADDRESS>wrote:

@Luthaf https://github.com/Luthaf I've made it through the first pass
on the branch feat/rgba. Currently, there are no opacity-affected
colormaps, so I included a commented line in src/maps/colorscales.ts to
uncomment to demonstrate the new functionality. Thoughts on the structure?
If it looks good I'll move ahead with opacity modes.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cosmo-epfl/chemiscope/issues/79#issuecomment-682010968,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIREZYIHVZOFVM2GVM4RFTSCZZRBANCNFSM4QLZ77VQ
.

I remember that there where some other issues with transparency in 3D with plotly (related to depth buffer & points appearing on top of others), but we can check if the fix would work for us!


New bug report

Hey there, I just encountered the following error with Alva:
It says Material Design is not compatible.
Stack Trace
Error
    at getBundle (/Applications/Alva Canary.app/Contents/Resources/app.asar/index.js:206141:23)
    at Object.analyze (/Applications/Alva Canary.app/Contents/Resources/app.asar/index.js:206154:25)
    at /Applications/Alva Canary.app/Contents/Resources/app.asar/index.js:82376:32

#783

Thanks for your report. We will let you know as soon as we fixed install bug as reported here #783


Allow users to install a project's dependencies, without the project itself

Not sure if we want this -- it's like Poetry's --no-root. Let's wait and see if we can find motivating use-cases for it. Poetry also has this concept of "operating modes" which toggle this automatically.

(Not decided, filed to revisit later.)

Lots of prior chatter over in https://github.com/python-poetry/poetry/issues/800

Maybe see also https://github.com/pypa/pip/issues/11440 for potential use cases.

(Interestingly, we actually kind of already support what's described in that issue because we allow pip install -r pyproject.toml. But that's separate from this issue.)

(Interestingly, we actually kind of already support what's described in that issue because we allow pip install -r pyproject.toml. But that's separate from this issue.)

That doesn't support the [extras] syntax (e.g. pip install -r pyproject.toml[doc])?
Personally, I'd love to see support for the syntax suggested here:
pip install --only-deps  .[doc]  # project.dependencies and project.optional-dependencies.doc

This works great pip install -r pyproject.toml :) It would be still great to add a flag and also add it to the pyproject.toml
[tool.uv]
package-mode = false

So it would also work with uv add <package>. Many things that I work on are not packages, but it would still be great to use uv to manage dependencies.
PS: uv is such an amazing tool - thanks for building it ❤

I have a use case for that: my blog, which is cirtually Markdown content only, and that is built by Pelican, a pure Python static website generator.
In that case the package-mode = false from Poetry was handy.
In the mean time, I hacked the process and added a dummy package at the root of my repository:
$ ls -lah ./blog
Permissions Size User Date Modified    Name
drwxr-xr-x     - kde  2024-07-13 14:12  .
drwxr-xr-x@    - kde  2024-07-13 14:17  ..
.rw-r--r--     0 kde  2024-07-13 14:11  __init__.py

And added the following directive in pyproject.toml:
[tool.setuptools.packages.find]
include = ["blog"]

My use case: ansible project with bundled ansible and other related packages.
For ansible project, the majority of code are written in yaml, by providing pyproject.toml we can build a self-contained ansible environment in project's .venv folder, with guaranteed ansible modules versions.
Besides, non-python-package programs like sshpass can be distributed into .venv/bin, so by source .venv/bin/activate ansible will be able to use functionally like remote host with password.

We use --no-root to better caching of container image layers.
The first layer just installs the project dependencies; the second adds the projects itself.
So if dependencies don't change, the layer can be reused.
We hope to write something like:

WORKDIR /src
ADD pyproject.toml uv.lock /app
RUN uv sync --no-dev --no-root
ADD src /app
RUN uv sync --no-dev

In the above scenario of a layered Dockerfile to leverage caching of infrequently changing dependencies, it is important that there is a way to install from uv.lock without involving pyproject.toml. That is because when pyproject.toml gets involved, it may in turn require the presence of the whole project (because of an in-tree build backend, dynamic dependencies, etc).
At first sight, uv.lock contains everything that is needed to do this, except for an indication about the top level package(s).
IMHO this is a critical feature for adoption of uv.lock, as without it the space and time efficiency of dockerfile builds will be severely impacted, compared to the traditional approach of installing requirements.txt in a layer, then the app in another.

I agree that something like this is necessary.

I'll chime in that --no-root is not enough. You probably also want a --no-directory or --no-local, maybe just generalize to a source selector or something.
Motivation: https://python-poetry.org/docs/faq#poetry-busts-my-docker-cache-because-it-requires-me-to-copy-my-source-files-in-before-installing-3rd-party-dependencies
In particular the idea is that if you have a monorepo you can still copy in your top-level lockfile and not have to copy in anything (not even the pyproject.toml) from your sub-projects/packages.

Yeah 100% agree that you should be able to sync from just the lockfile. The lockfile itself is actually designed to support that (it doesn’t rely on pyproject.toml), but we need to expose the right options to users…

I can see a few approaches here (all fairly easy to implement, mostly about getting the API right)...

--no-project (or --no-workspace) along with a separate --no-local flag (to ignore path dependencies that aren't part of the workspace)
--only-remote (the inverse)
Something like --seed or another semantic term that indicates why this is useful

In case you’re looking for opinions, I like “seed”. The others are rather generic and I’d have to guess what they exactly mean.

(Gonna see if we can come up with an API and ship this ~today.)

Opinions very welcome.

I think --no-project is pretty clear but don't care too much as well as it's documented.

Would --no-self and --only-self be more intuitive?

--seed {package-name}[extra,...], because you need to tell it what top level package you need to install?

I think extras would be covered by the normal --extra and --all-extras options.
I worry about --no-project and --no-workspace because those have a different meaning elsewhere; which is, don't discover a project or workspace entirely. We still should perform normal project or workspace discovery, e.g., to find the uv.lock file if you're in a subdirectory for some reason.
I think we might want to use --without- and --only- prefixes, to match the our --with options.
The difficulty is in choosing how to describe what we're selecting. There are a few things we want to be able exclude:

The current project
A workspace member
A path dependency

Unfortunately --without-editables doesn't work because a path dependency can be either editable or not editable. We also want to be able to toggle whether or not the current project and workspace members are installed as editable in the future.
All of these are "local" dependencies, as in they're on the local file system, so --without-local might make sense. Does this include the current project though?
It feels like we need a separate flag for excluding just the current project, like --without-self or --without-root. Presumably we'd pair this with an opposite flag like --only-self or --only-root.
I think --without-project isn't an option because it overlaps too much with --no-project.
Do we need the ability to exclude all local dependencies except the current project? Or can it be done in two steps:
uv sync --without-local
uv sync --inexact --only-self

What's the use-case for that?

I think the only use-case for the Docker caching situation is "exclude all locals".
I think excluding the current project (but not other workspace members) is independently useful, like for "virtual projects." We could choose not to solve that here, but we should probably have a design that won't cause us problems in the future if we pursue it.

As a note on my own post, I think I prefer --without-locals over --without-local?

What about --no-locals or --no-local to match options like --no-project?

Ok, I didn't get this shipped today, but I did implement it: https://github.com/astral-sh/uv/pull/6398

The gist is that you can copy in uv.lock, then run uv sync --frozen --no-locals.

Well, I specifically opted for --without- instead of --no- since we use --with- for including dependencies it probably makes sense to do the same for excluding them?

I would be remiss if I didn't mention that this feature would be massively more useful (and less surprising, I guess) in the Docker context if uv sync --python /some/venv/bin/python worked as expected. 😇
But mega kudos for the quick implementation as always; this is amazing! 🚀

We'll definitely be tackling alternative sync targets ASAP as well.

I think the docker case is real but at the end of the day it creates a situation in the virtualenv that I would argue should not exist.  So at least in my mind there is a significant difference between "install third party deps", make a layer, then follow by installing the rest vs "never ever install the root package because it's inconvenient".
Particularly for the docker situation I quite honestly wonder if not a fundamentally better solution is to allow the installation process to be explicitly being built for that use case by supporting skipping/interrupting and continuing.  I understand that this is not how any other tool works but particularly for more complicated setups I can see this being quite useful.
I'm imagining that this might be quite interesting.  This would work if the lockfile is up to date prior to the sync.
# first layer, third party deps only
RUN uv sync --partial --skip-package="root-package" --skip-package="second-package"
COPY src/root-package ./src/root-package
# second layer, bring one package in
RUN uv sync --partial --skip-package="second-package"
COPY src/second-package ./src/second-package
# sync what we have not seen yet
RUN uv sync

At sentry for instance we do install packages from two different repositories (open source git checkout followed by internal billing code checkout).
I think being more explicit about what this is used for would be a good thing and also forces that the docker case is intentionally supported on the uv side and not just a happy little accident.

My use case here is very similar to the ones listed here, but with a twist. We do not copy the workspace into the build context, rather, we mount a wheel that was already built in a previous CI stage.
This reduces duplication, both in terms of stages (build-backend only invoked once), as well as storage (if I COPY src and then proceed to uv sync that, I'd have an src tree left over in my resulting image, taking space and causing confusion).
Most importantly, by using a wheel and not a raw workspace, this also lets me have consistent builds between different targets (docker, pypi, rpm/deb/nix, etc etc)
Being able to uv sync without the root package will help to an extent, but I am not sure if it is a globally-optimal solution. I'd end up with:
RUN uv sync --frozen --no-locals
RUN uv pip install /mnt/my-actual-application.whl       # This part is lockfile agnostic; no guarantee that things won't drift!

For context, right now we do:
RUN uv pip install /mnt/my-actual-application.whl -c /mnt/constraints.txt

Which works exactly as intended -- but it's not a proper lockfile (and being able to slice it into layers is a very nice thing to be able to do)

Yes, the lock file needs to be copied first, but only prior to the first partial sync and if it's not there, uv sync --partial would fail.
My point is mostly, without going too much into the implementation, that a partial sync would be an explicit, multi-stage approach precisely to safely make a multi-layer caching solution work.

I for one could live with explicitly naming the package I want to sync later (i.e. uv sync --skip-package="my-app") but I'm not 100% sure we're on the same page.

My reasoning with explicit skipping here is not so much that this is how it should be (eg: this is how you name what has not been synced) but that it's a very intentional process and you don't accidentally start interacting with a partial venv and then end up surprised about random failures later down the line.

I think it would be pretty reasonable to use --skip-package rather than --no-locals. It would enable strictly more use-cases. The downside is that you need to include the package name (of course) and that, if you have a large workspace, it's a little tedious to enumerate them all. But it might be a better, more flexible solution than --no-locals.

Does the lock file include dev dependencies? In that case it would be very tedious if we don't want these in the docker image.
How about --dependencies-of package ?

Ah, right I now see the lock file knows the distinction between regular and dev dependencies :+1:

Might be worth considering https://github.com/astral-sh/uv/issues/4422 too when designing a --skip-package interface.

Today we discussed doing something like:

--no-install-root (skip root package)
--no-install-workspace (skip any workspace dependencies, including the root)
--no-install-paths (skip any path dependencies)
--no-install package [package] (skip a specific package)

We may even want to have a dedicated separate command for this with different defaults (per the above).

This will be available when we release (soon, I'm sure). Let me know if you encounter any problems!

This is available now in 0.3.3

Is --no-install-paths still planned?

@justenstall we're waiting to see how necessary it is since we have --no-install-package and the amount of options could get excessive. We can track in https://github.com/astral-sh/uv/issues/6695

Can --no-install-project be set in config?

PDM has concept of describing if project is application or library https://pdm-project.org/en/latest/usage/project/#library-or-application


[Code app]: Update "Chat completion" according to selected example

Description
To make examples work properly for Code app need to input correct parameters.
Suggestion:
update required parameters according to selected example:

Chat completion and DIAL_URL environmental variable for "Simple RAG" example
Chat completion for "Hello world" example

Use case/motivation
No response
Related issues
No response
Confidential information

[X] I confirm that do not share any confidential information

verified on staging
related issue #2750


iOS Event Parameters inverted on Flurry - BUG FIX

There is a critical bug in the iOS Wrapper, which causes Event Parameters to be swapped at the parameter key and the parameter value.
Following line in function keyValueToDict in UnityFlurry.mm is wrong:
[dict setObject:[keysArray objectAtIndex: i] forKey:[valuesArray objectAtIndex: i]];
CHANGE TO:
[dict setObject:[valuesArray objectAtIndex: i] forKey:[keysArray objectAtIndex: i]];
Sadly Objective-C is being one of those languages where a Map is set in the form of value/key instead the other ways around!
Hope it helps. Cheers.

Thanks, fixed.


docs: rename "Implementing..." section to "User Guides"

This PR renames the section previously called "Implementing Keptn Applications" to be just "User Guides".  We discussed this in the 13 September 2023 Community Meeting and agreed that "User Guides" is a more accurate and more friendly name.
We decided to not subdivide this section by "Metrics", "Observability", and Release Lifecycle Management but to reorder some of the pages to be in a more logical order, so the first sections, in order, are:

Integrate Keptn with your applications
Keptn Metrics
Dora Metrics
OpenTelemetry observability

The remaining sections are all related to Release Lifecycle Management.

Fixes #2087

@StackScribe why did you not rename the folder as well? doesn't this look weird in URLs?


ilmbase: Proprietary licence in halfExport.h

There is something clearly wrong with the license associated with this file:

https://github.com/openexr/openexr/blob/develop/IlmBase/Half/halfExport.h

//
//  Copyright (c) 2008 Lucasfilm Entertainment Company Ltd.
//  All rights reserved.   Used under authorization.
//  This material contains the confidential and proprietary
//  information of Lucasfilm Entertainment Company and
//  may not be copied in whole or in part without the express
//  written permission of Lucasfilm Entertainment Company.
//  This copyright notice does not imply publication.
//

Could you please fix this license ASAP, this is a serious issue for distribution like Debian. Thanks.

Sorry, that's just an oversight.  We'll get it replaced with the appropriate license consistent with the rest of the package ASAP.
For Debian, is it sufficient for the fix to be at the head of the develop branch, or does it need to be in a numbered release?

License corrected in development branch now.

Great ! I see the patch here:

https://github.com/openexr/openexr/commit/20d043d017d4b752356bb76946ffdffaa9c15c72

That's enough for us within Debian, no need for a new version release. Thanks for the quick update.

@cary-ilm Thanks for preparing v2.2.1 release. We are going to use this new release in Debian. However would you please apply git commit 20d043d to your release branch. That would be wonderful, otherwise @mfvescovi will need to integrate -again- a local patch in Debian.

Could some kind repo collaborator re-open the issue to keep track of it progress ? Debian BTS can watch automatically the status of github bug tracker.


Coupons Used Not Shown in Order Details Page

Setup:

in Backoffice, enable and publish promotion rule "coupon_code_fixed_discount".
1.a. Make sure coupon SUMMER69's validity and redemptions are greater than 0, and not already used.

Steps to Reproduce:

Navigate to Spartacus storefront.
Add items to cart.
In cart page, add coupon "SUMMER69".
Proceed to checkout.
After order is placed, navigate to order details page.

Expected Results:
5. Coupon "SUMMER69" is listed as having been used.
Actual Results:
5. No coupon is listed. Only the discount is available (which is inferred to come from the coupon).

Old-Accelerator:

Spartacus:

Dupe of #5154


node modules following github packages naming weren't included

Github Packages naming conventions are mapped wrongly by Electron-Forge Ignore function.
Github Packages requires "@organization/package" name for libraries and Electron-Forge gives you just "node_modules/@organization".
If you want to open an issue on their GitHub feel free to do so.

Also I would appreciate if you can merge & npm publish asap. Thanks.

It looks like this change would package everything under @org/ which could be including far too much.
Can you give me an example module that is currently failing to get packaged?

It looks like this change would package everything under @org/ which could be including far too much.
Can you give me an example module that is currently failing to get packaged?

I tried with my own module which is private. But you can try yourself with any package which has "@org/package".
I know that with my fix every "@org" package will be included. But the ignore function returns the package name wrong.
Since I only have a single "@org" package I fixed that way, but the real issue is in Electron Forge API I guess?

Since I only have a single "@org" package I fixed that way, but the real issue is in Electron Forge API I guess?

The plan is to merge this functionality into forge so whatever the source of the issue I need to work out what's causing it so I can fix it.

Since I only have a single "@org" package I fixed that way, but the real issue is in Electron Forge API I guess?

The plan is to merge this functionality into forge so whatever the source of the issue I need to work out what's causing it so I can fix it.

Honestly it's the first time I've been working with Electron Forge and my package has a Native Node Addon (.node) which loads a dylib (or DLL depending on the OS). The only way I got it working was with this plugin and a small fix (the PR).
If you have any better solution let me know.

The problem is really that electron-forge does not call the plugin with the correct package name. In case of a scoped package (@org) it's only providing /node_modules/@org, which is wrong. It should be providing /node_modules/@org/package-name.
The plugin tries to process the dependencies of the externals so including a whole scope would not be ideal. Some dependencies could fail to be included.

Exactly what I needed. Thank you. This library and the changes proposed works great


CASMTRIAGE-5002 & CASMPET-6357: upload rebuild templates and install iuf-cli

Description
When upgrading to CSM 1.4, the rebuild workflow templates need to be uploaded as a prerequisite.

Checklist

[ ] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[ ] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport main

/backport main

/backport main

/backport main


Merkle Tree Generation fails [243rd trit must be zero]

Describe the bug
When trying to generate a new Merkle Tree for a private tangle, a panic error gets thrown and the tool exists.
calculating 1048576 addresses...
panic: each 243rd trit must be zero: invalid trit

goroutine 83 [running]:
github.com/iotaledger/iota.go/merkle.calculateAllAddresses.func1(0xc00003c990, 0xc00009e1e0, 0xc00003a009, 0x51, 0x2, 0xc000680000, 0x100000, 0x100000)
        /github/home/go/pkg/mod/github.com/iotaledger/iota.go@v1.0.0-beta.15.0.20201113171647-14f7a0d87712/merkle/merkle_tree.go:110 +0x14d
created by github.com/iotaledger/iota.go/merkle.calculateAllAddresses
        /github/home/go/pkg/mod/github.com/iotaledger/iota.go@v1.0.0-beta.15.0.20201113171647-14f7a0d87712/merkle/merkle_tree.go:104 +0x1ab

To Reproduce
Steps to reproduce the behavior:

Start with a fresh installation of hornet.
Follow the instructions for a private tangle.
Try to generate a merkle tree.

Expected behavior
The tool should generate a merkle tree.
Environment information:

OS: Ubuntu 20.04 LTS
RAM: 2 GB
Cores: 8
Type: VPS
HORNET version 0.5.6

Additional context
Apparently this error was already fixed in HORNET itself, but was missed in the merkle tree tool

Replace the last Tryte of your Coordinator Seed with a "9".
We won't fix this, since its not a bug. It could fail earlier, but Merkle trees for COO will be removed with chrysalis anyway.


add generic header slot

Type

What types of changes does your code introduce?

Allows a slot header to be defined for all columns.

Put an x in the boxes that apply_

[ ] Fix
[ x] Feature

Checklist

Put an x in the boxes that apply._

[ ] Title as described
[ ] Add unit test by vitest if necessary

LGTM


Very bright objects does not approach/become white with filmic tonemapper

Godot version
v4.0.beta1.official [20d667284]
System information
N/A
Issue description
This is basically https://github.com/godotengine/godot-proposals/issues/3214 but for the Filmic tonemapper. It seems that both ACES and Filmic are supposed to have this behavior according to Blender, but only ACES got the "fitted" treatment despite Filmic being the "preferred" tonemapper in 4.0 according to the tonemapper used if you enabled tonemap in the preview world env.
This issue also applies to 3.x.
For details about Filmic, see Color Grading and Filmic Tonemapper(Unreal Doc)
Blender reference:

Comparison of ACES and Filmic in 4.0
ACES:

Filmic:

Same comparison in 3.x
ACES Fitted:

Filmic:

Steps to reproduce

Set up a scene with a world env, set tonemapper to Filmic
Place down some objects and a high energy directional light.

Minimal reproduction project
No response

This isn't a bug, it is a feature proposal. Feature proposals should be made in the https://github.com/godotengine/godot-proposals repository


research: explore using pyodide and supernote-tool

One idea to avoid porting all of @jya-dev 's work on https://github.com/jya-dev/supernote-tool is to use pyodide to pull the python libraries into WASM. It seems most of the dependencies work out of the box: https://github.com/philips/obsidian-plugin-supernote/compare/main...pyodide

Hrm, two hurdles looking into this more:

some issue with pyodide assuming it is running on node if it detects electron https://github.com/pyodide/pyodide/discussions/2248
pyodide seems to not have a solution for bundling everything together so I would need to figure out how to make supernote-tool a separate library and package all pyodide and the wheels together into a static assets in the plugin build.

Some breadcrumbs from gemini and research:
 **While esbuild doesn't directly support Pyodide, here's a workaround approach to package your project:**

**1. Structure Your Project:**

- Organize your project files as follows:

project_root/
├── package.json
├── pyodide-lock.json
├── pyodide/
│   ├── pyodide.asm.js
│   ├── pyodide.asm.wasm
│   ├── pyodide.js
│   ├── pyodide.mjs
│   └── python_stdlib.zip
├── src/   (JavaScript source files)
│   └── ...
└── build/ (Destination for bundled files)

**2. Install esbuild:**

- Use npm or yarn to install esbuild:

```bash
npm install --save-dev esbuild

3. Create a Build Script:

Create a JavaScript file (e.g., build.js) to configure the bundling process:

import { build } from 'esbuild';

build({
  entryPoints: ['src/index.js'],  // Adjust based on your entry file
  bundle: true,
  outfile: 'build/bundle.js',
  format: 'esm',
  define: {
    // Define any necessary Pyodide-related globals
    PYODIDE: 'pyodide',  // Example if you're using Pyodide globally
  },
  external: [
    'pyodide/pyodide.asm.js',
    'pyodide/pyodide.asm.wasm',
    'pyodide/pyodide.js',
    'pyodide/pyodide.mjs',
    'pyodide/python_stdlib.zip',
  ],
});

4. Run the Build:

Execute the build script:

node build.js

5. Serve Bundled Files:

Distribute the build folder, ensuring the Pyodide files are accessible from the same relative path:

bundle.js
pyodide/
  └── ... (Pyodide files)

Key Considerations:

Manual Adjustments: You may need to manually handle Pyodide-specific initialization and loading in your JavaScript code.
Future Updates: Stay informed about potential esbuild integration with Pyodide, as this workaround might evolve with future updates.
Pre-built Wheels: If possible, consider using pre-built Pyodide wheels for a smoother integration experience.

Esbuild currently doesn't have direct support for integrating Python wheels, including Pyodide wheels. Wheels are designed for installation within a Python environment, not directly in a JavaScript bundler like esbuild.

Here are some alternative approaches to consider:

1. **Serve Wheels Separately:**

- Maintain your Pyodide wheels alongside your bundled JavaScript code.
- Use a server-side solution or a CDN to serve these wheels to your application.
- In your JavaScript code, you'll need to handle loading the wheels using techniques like dynamic imports or fetching them from the server.

2. **Explore Alternative Bundlers:**

- Some bundlers like Webpack offer more flexibility in handling non-JavaScript assets through loaders and plugins. You might find tools like the `file-loader` or a custom loader suitable for Pyodide wheels in Webpack.

3. **Future Developments:**

- The Pyodide project is exploring ways to potentially leverage esbuild for its build process. While not yet available, future advancements might offer better integration options for Pyodide with esbuild.

**Remember:**

-  Serving wheels separately adds an extra layer of complexity to your deployment process.
- Webpack introduces a steeper learning curve compared to esbuild, but it might be more suitable for handling wheels at this time.

It's best to choose the approach that aligns best with your project's needs and your comfort level with different tools.

This is probably not worthwhile now. Closing


'SchoolContext' does not contain a definition for 'Student'

I get this error when I try to run the app:
`html.cs(26,38): error CS1061: 'SchoolContext' does not contain a definition for 'Student' and no accessible extension method 'Student' accepting a first argument of type 'SchoolContext' could be found (are you missing a using directive or an assembly reference?)`

The build failed. Fix the build errors and run again.

The error is in
Create.cshtml.cs, Delete.cshtml.cs, Edit.cshtml.cs and Index.cshtml.cs where 'Student' is. For example, Student in this line is underlined --> _context.Student.Add(Student);
I feel like I've copied-pasted everything so I'm not sure what the issue is.
This is the tutorial II'm following--> https://docs.microsoft.com/en-us/aspnet/core/data/ef-rp/intro?view=aspnetcore-3.1&tabs=visual-studio-code
ASP.NET Core 3.1
On Mac, using VSCode.
Thanks,
Lydia

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

ID: 7a54c97f-ddd4-b041-5e5f-a2df009ace50
Version Independent ID: fa488196-1f98-08ea-adcc-17d9dac86727
Content: Razor Pages with Entity Framework Core in ASP.NET Core - Tutorial 1 of 8
Content Source: aspnetcore/data/ef-rp/intro.md
Product: aspnet-core
Technology: aspnetcore-data
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

You're missing the step where your rename student I think. The tutorial does work.

I believe The tutorial does work! The entity classes in SchoolContext.cs should be in singular form.

I believe The tutorial does not work! The entity classes in SchoolContext.cs should be in singular form.


Fix filter to generate class_{organ}_log

Hard for me to meaningfully review.  Can you write a quick ticket that describes the issue and link to PR?  I'll try to be quick as I guess this is urgent - to prevent errors from entering sprint review cycle.


datastore: rewrite dataframe integration in terms of DataTable's

Drop most of the awful code that does the ad-hoc integration between the arrow store and polars, and instead rely on DataTable's serialization & dataframe primitives.
Requires #1692

The dataframe integration is gone.


Rebuild and modify context accordingly

The attributes of ctx are classified into the following two classes

ctx.xxx: general attributes
ctx.var.xxx: actually refer to ctx["var"][${ctx.cur_mode}_${ctx.cur_data_split}]["xxx"]

Add lifecycle manager

Build two classes CtxStatsVar and CtxReferVar to wrap the variables with specific lifecycle and clear function.

CtxStatsVar: statistic variables (float), e.g. loss_batch_total

lifecycle: chosen from  batch, epoch, routine and None

CtxReferVar: reference variable, e.g. y_prob, data_batch

lifecycle: chosen from  batch, epoch, routine and None
efunc: the customized function to run when the lifecycle ends

e.g. for ctx.model, maybe we want to move it to cpu when the lifecycle ends.
When efunc is None, the variable is deleted at the end of the lifecycle

Add an attribute lifecycles in Context to record the lifecycles of the attributes
Add a decorator @lifecycle(lifecycle=xxx) to manage  the variables.

This pr is under modification


add blackarch install step

I packaged it, tested it and I installed it myself that way.Yes it works 😉


Remove HttpOnhy flag for cookies

Refs: https://github.com/metarhia/StarterKit/issues/11

Landed in https://github.com/metarhia/impress/commit/d547652b635e7d66e161c0dec4ac43f5ba60c72c


Crash on Time Scaling 0

Setting Time Scaling to 0, gives Error: java.lang.ArithmeticException: / by zero when loading a world. "Ticking world" being the error title.

Fixed with https://github.com/Globox1997/RpgDifficulty/commit/1543a1182c9346547701607f3c5bd13a5052d163
Thanks for reporting :)


What can be done with this emulator!!

Hello guys, I invite you to my website, it is a sample of what can be done with this wonderful emulator that Ben Firshman and his team have created. I have made some reforms and added support for Gamepad.
Visit my website!
https://www.familygame.online

Site is down


Tests are failing on Travis CI

https://travis-ci.org/github/JuliaClimate/CDSAPI.jl

Hello @juliohm, I will try looking through the stack trace and figure out what is causing this issue.

Okay, so in build for  Julia: 1.4 I saw this error:
SystemError: opening file "/home/travis/.cdsapirc": No such file or directory

This is because we are looking for API keys from .cdsapirc file in the retrieve() method.
We can fix this by setting up API keys on Travis environment (something like storing keys in .cdsapirc and then encrypting them, as we do in GitHub secrets).
I am not sure about what's the right way of doing this, but I am on it.
I will try to post a solution for Julia: 1.4 first and then I will target the lower versions.

Hello @juliohm, one solution I found is encrypting .cdsapirc file using Travis command line tool and then uploading the generated encrypted file .cdsapi.enc to GitHub (see: Secret Files). After that, adding commands to .travis.yml to decrypt the file in the specified location before running the test jobs.

Nice @LakshyaKhatri , I am not the most experienced with GitHub and keys, but I appreciate if you can document in the issue the process you took so that future contributors can reproduce in case the secret file gets outdated.
Thank you for the great work, it is really nice to see the package evolving.

Should I document the process in this issue itself?

That would be nice. Thanks for doing it.
On Mon, Jul 20, 2020, 07:37 Lakshya Khatri<EMAIL_ADDRESS>wrote:

Should I document the process in this issue itself?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JuliaClimate/CDSAPI.jl/issues/30#issuecomment-660948265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZQW3LNIOBRNSEILIMF6T3R4QM45ANCNFSM4OYSAQGA
.

(Julia: 1.4) Error:
SystemError: opening file "/home/travis/.cdsapirc": No such file or directory
Problem:
The file .cdsapirc contains the API keys that we use to fetch data from the CDS website. Since the file contains sensitive information it is kept outside from the git tracking directory. A standard is to keep the run command (rc) files in the HOME directory. Now, since the file is not getting tracked by git, it is also not getting uploaded to Travis CI. Hence, when the retrieve() function is called it looks for the .cdsapirc file in the HOME directory and complains when the file is not found.
Solution:
There can be many possible solutions. One which I found is:

Encrypting the .cdsapirc file using Travis CI Command-Line Client.
Adding the encrypted .cdsapi.enc file to GitHub.
Adding instructions to .travis.yml to tell Travis CI that it has to decrypt the file before running the build.

Implementation

Create a file .cdsapirc in the HOME directory with the following contents:

url: https://cds.climate.copernicus.eu/api/v2
key: <cds-apikey-for-travis>

Install Travis CI Command-Line Client.
Log in to travis using:

travis login

Encrypt .cdsapirc file:

travis encrypt-file -r path/to/CDSAPI/Repo $HOME/.cdsapirc --add

This will encrypt the .cdsapirc file and add decryption command to your .travis.yml automatically, which will look something like this:
before_install:
 - openssl aes-256-cbc -K $encrypted_0a6446eb3ae3_key -iv $encrypted_0a6446eb3ae3_iv -in .cdsapirc.enc -out ~\/.cdsapirc -d

But Travis will complain that there is no directory matching ~/.

Update the decrypted file path in .travis.yml. In other words, change this:

before_install:
 - openssl aes-256-cbc -K $encrypted_0a6446eb3ae3_key -iv $encrypted_0a6446eb3ae3_iv -in .cdsapirc.enc -out ~\/.cdsapirc -d

To this:
before_install:
 - openssl aes-256-cbc -K $encrypted_0a6446eb3ae3_key -iv $encrypted_0a6446eb3ae3_iv -in .cdsapirc.enc -out $HOME\/.cdsapirc -d

Note: Encrypting the file again will generate new public keys for Travis.

This will allow retrieve() to use API keys from a .cdsapirc file and will resolve the issue.

PS: I am going through the error log to check what is the issue in other versions and will soon post solutions to fix them too.

Such an amazing work @LakshyaKhatri , thank you for improving the package, very professional report. Is the issue solved now in Travis CI Julia v1.4?

Yes :smile: :

Could you please submit a PR @LakshyaKhatri to implement the changes in the .travis.yml? I wonder how the tests are passing on Travis without the commands you shared above in the .travis.yml file?

Hello @juliohm, I tried to figure out the build issues for Julia 1.0, 1.1 and 1.2. It is the same dependency issue in all of them:
ERROR: Unsatisfiable requirements detected for package eccodes_jll [b04048ba]:
 eccodes_jll [b04048ba] log:
 ├─possible versions are: [2.17.0, 2.18.0] or uninstalled
 ├─restricted by compatibility requirements with GRIB [b16dfd50] to versions: [2.17.0, 2.18.0]
 │ └─GRIB [b16dfd50] log:
 │   ├─possible versions are: 0.2.0 or uninstalled
 │   └─restricted to versions * by an explicit requirement, leaving only versions 0.2.0
 └─restricted by compatibility requirements with libpng_jll [b53b4c65] to versions: uninstalled — no versions left
   └─libpng_jll [b53b4c65] log:
     ├─possible versions are: 1.6.37 or uninstalled
     └─restricted by julia compatibility requirements to versions: uninstalled

I searched a lot and my best hunch is that it is causing because GRIB is using version 2.18.0 (which is released 13 days ago) for eccodes_jll but the minimum available version for eccodes_jll is 2.17.0 (see GRIB.jl/Manifest.toml).
I might need some help in this one.

Thank you @LakshyaKhatri for the update. I think we can support Julia v1.4 and later versions. For simplicity, let's drop support for lower versions in our .travis.yml and add julia = 1.4 to our Project.toml. Could you please work on that? :)

Thanks for the help @juliohm, are we considering adding Julia 1.3 too (since the errors are fixed in #34) ?

Nice, if the tests are passing for Julia 1.3 without eccodes_jll issues, let's add it as well :+1:

Okay, I will check and make changes accordingly. :)


Run fly in production

As talked about with @lukeed

I wonder why we need 🤔

We actually don't. Still having the conversation. It's nothing to do with Fly itself. @timneutkens wants to compile the Babel scripts & inject a NODE_ENV value while doing so.

I think you need this. And then I would introduce an uglify() step (within release task), which would drop the dead code blocks.
Eg; 'development' === 'production', 'production' === 'production'

Actually it has no relation to dead code removal. Webpack handles that. The only reason I want to do this is to keep the environment consistent with the way we're building (for production). If we don't pass it through babel will default to development.

+1 that this is very strange

@lukeed if it's not needed at all we could close it though.

If I'm understanding you correctly, then the current behavior makes perfect sense. It's doing all that it is configured to do.
Right now, the only bundle that gets injected with a production environment is the prefetcher script, because it's the only entry that webpack is aware of.
While setting the environment here might work, I don't think it's a very consistent way of doing it, iirc. This is why bundlers like rollup & webpack rely on replace-text plugins, --environment flags, cross-env, or a combo of the three.
And personally, I would still worry about dead codeblocks. Once you inject an environment value, react has so many block statements that can be cleaned up or removed, which removes the need for a simple parts and a simple execution. Without it, you still technically don't have a production-ready react bundle.
Sorry to go on about it, but I know Dan Abramov has spoken a lot about this.

Closing this after discussing with @lukeed. He's going to check the dead code removal.


lxd recover wrong uids/gids on recovered storage volume

Required information

Distribution: centos
Distribution version: 8-Streams
The output of "lxc info" or if that fails:

config:
cluster.https_address: lxd11:8443
core.https_address: lxd11:8443
api_extensions:

storage_zfs_remove_snapshots
container_host_shutdown_timeout
container_stop_priority
container_syscall_filtering
auth_pki
container_last_used_at
etag
patch
usb_devices
https_allowed_credentials
image_compression_algorithm
directory_manipulation
container_cpu_time
storage_zfs_use_refquota
storage_lvm_mount_options
network
profile_usedby
container_push
container_exec_recording
certificate_update
container_exec_signal_handling
gpu_devices
container_image_properties
migration_progress
id_map
network_firewall_filtering
network_routes
storage
file_delete
file_append
network_dhcp_expiry
storage_lvm_vg_rename
storage_lvm_thinpool_rename
network_vlan
image_create_aliases
container_stateless_copy
container_only_migration
storage_zfs_clone_copy
unix_device_rename
storage_lvm_use_thinpool
storage_rsync_bwlimit
network_vxlan_interface
storage_btrfs_mount_options
entity_description
image_force_refresh
storage_lvm_lv_resizing
id_map_base
file_symlinks
container_push_target
network_vlan_physical
storage_images_delete
container_edit_metadata
container_snapshot_stateful_migration
storage_driver_ceph
storage_ceph_user_name
resource_limits
storage_volatile_initial_source
storage_ceph_force_osd_reuse
storage_block_filesystem_btrfs
resources
kernel_limits
storage_api_volume_rename
macaroon_authentication
network_sriov
console
restrict_devlxd
migration_pre_copy
infiniband
maas_network
devlxd_events
proxy
network_dhcp_gateway
file_get_symlink
network_leases
unix_device_hotplug
storage_api_local_volume_handling
operation_description
clustering
event_lifecycle
storage_api_remote_volume_handling
nvidia_runtime
container_mount_propagation
container_backup
devlxd_images
container_local_cross_pool_handling
proxy_unix
proxy_udp
clustering_join
proxy_tcp_udp_multi_port_handling
network_state
proxy_unix_dac_properties
container_protection_delete
unix_priv_drop
pprof_http
proxy_haproxy_protocol
network_hwaddr
proxy_nat
network_nat_order
container_full
candid_authentication
backup_compression
candid_config
nvidia_runtime_config
storage_api_volume_snapshots
storage_unmapped
projects
candid_config_key
network_vxlan_ttl
container_incremental_copy
usb_optional_vendorid
snapshot_scheduling
snapshot_schedule_aliases
container_copy_project
clustering_server_address
clustering_image_replication
container_protection_shift
snapshot_expiry
container_backup_override_pool
snapshot_expiry_creation
network_leases_location
resources_cpu_socket
resources_gpu
resources_numa
kernel_features
id_map_current
event_location
storage_api_remote_volume_snapshots
network_nat_address
container_nic_routes
rbac
cluster_internal_copy
seccomp_notify
lxc_features
container_nic_ipvlan
network_vlan_sriov
storage_cephfs
container_nic_ipfilter
resources_v2
container_exec_user_group_cwd
container_syscall_intercept
container_disk_shift
storage_shifted
resources_infiniband
daemon_storage
instances
image_types
resources_disk_sata
clustering_roles
images_expiry
resources_network_firmware
backup_compression_algorithm
ceph_data_pool_name
container_syscall_intercept_mount
compression_squashfs
container_raw_mount
container_nic_routed
container_syscall_intercept_mount_fuse
container_disk_ceph
virtual-machines
image_profiles
clustering_architecture
resources_disk_id
storage_lvm_stripes
vm_boot_priority
unix_hotplug_devices
api_filtering
instance_nic_network
clustering_sizing
firewall_driver
projects_limits
container_syscall_intercept_hugetlbfs
limits_hugepages
container_nic_routed_gateway
projects_restrictions
custom_volume_snapshot_expiry
volume_snapshot_scheduling
trust_ca_certificates
snapshot_disk_usage
clustering_edit_roles
container_nic_routed_host_address
container_nic_ipvlan_gateway
resources_usb_pci
resources_cpu_threads_numa
resources_cpu_core_die
api_os
container_nic_routed_host_table
container_nic_ipvlan_host_table
container_nic_ipvlan_mode
resources_system
images_push_relay
network_dns_search
container_nic_routed_limits
instance_nic_bridged_vlan
network_state_bond_bridge
usedby_consistency
custom_block_volumes
clustering_failure_domains
resources_gpu_mdev
console_vga_type
projects_limits_disk
network_type_macvlan
network_type_sriov
container_syscall_intercept_bpf_devices
network_type_ovn
projects_networks
projects_networks_restricted_uplinks
custom_volume_backup
backup_override_name
storage_rsync_compression
network_type_physical
network_ovn_external_subnets
network_ovn_nat
network_ovn_external_routes_remove
tpm_device_type
storage_zfs_clone_copy_rebase
gpu_mdev
resources_pci_iommu
resources_network_usb
resources_disk_address
network_physical_ovn_ingress_mode
network_ovn_dhcp
network_physical_routes_anycast
projects_limits_instances
network_state_vlan
instance_nic_bridged_port_isolation
instance_bulk_state_change
network_gvrp
instance_pool_move
gpu_sriov
pci_device_type
storage_volume_state
network_acl
migration_stateful
disk_state_quota
storage_ceph_features
projects_compression
projects_images_remote_cache_expiry
certificate_project
network_ovn_acl
projects_images_auto_update
projects_restricted_cluster_target
images_default_architecture
network_ovn_acl_defaults
gpu_mig
project_usage
network_bridge_acl
warnings
projects_restricted_backups_and_snapshots
clustering_join_token
clustering_description
server_trusted_proxy
clustering_update_cert
storage_api_project
server_instance_driver_operational
server_supported_storage_drivers
event_lifecycle_requestor_address
resources_gpu_usb
clustering_evacuation
network_ovn_nat_address
network_bgp
network_forward
custom_volume_refresh
network_counters_errors_dropped
metrics
image_source_project
clustering_config
network_peer
linux_sysctl
network_dns
ovn_nic_acceleration
certificate_self_renewal
instance_project_move
storage_volume_project_move
cloud_init
network_dns_nat
database_leader
instance_all_projects
clustering_groups
ceph_rbd_du
instance_get_full
qemu_metrics
gpu_mig_uuid
event_project
clustering_evacuation_live
instance_allow_inconsistent_copy
network_state_ovn
storage_volume_api_filtering
image_restrictions
storage_zfs_export
network_dns_records
storage_zfs_reserve_space
network_acl_log
storage_zfs_blocksize
metrics_cpu_seconds
instance_snapshot_never
certificate_token
instance_nic_routed_neighbor_probe
event_hub
agent_nic_config
projects_restricted_intercept
metrics_authentication
images_target_project
cluster_migration_inconsistent_copy
cluster_ovn_chassis
container_syscall_intercept_sched_setscheduler
storage_lvm_thinpool_metadata_size
storage_volume_state_total
instance_file_head
instances_nic_host_name
image_copy_profile
container_syscall_intercept_sysinfo
clustering_evacuation_mode
resources_pci_vpd
qemu_raw_conf
storage_cephfs_fscache
network_load_balancer
vsock_api
instance_ready_state
network_bgp_holdtime
storage_volumes_all_projects
metrics_memory_oom_total
storage_buckets
storage_buckets_create_credentials
metrics_cpu_effective_total
projects_networks_restricted_access
storage_buckets_local
loki
acme
internal_metrics
cluster_join_token_expiry
remote_token_expiry
init_preseed
storage_volumes_created_at
cpu_hotplug
projects_networks_zones
network_txqueuelen
cluster_member_state
instances_placement_scriptlet
storage_pool_source_wipe
zfs_block_mode
instance_generation_id
disk_io_cache
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
tls
environment:
addresses:

lxd11:8443
architectures:
x86_64
i686
certificate: |
-----BEGIN CERTIFICATE-----
MIICKzCCAbGgAwIBAgIRAIFlFS6V2+9Ec9fL26PWUvMwCgYIKoZIzj0EAwMwQTEc
MBoGA1UEChMTbGludXhjb250YWluZXJzLm9yZzEhMB8GA1UEAwwYcm9vdEBseGQx
LjJlLXN5c3RlbXMuY29tMB4XDTIxMDIxOTExMTI0NloXDTMxMDIxNzExMTI0Nlow
QTEcMBoGA1UEChMTbGludXhjb250YWluZXJzLm9yZzEhMB8GA1UEAwwYcm9vdEBs
eGQxLjJlLXN5c3RlbXMuY29tMHYwEAYHKoZIzj0CAQYFK4EEACIDYgAE46bR2t/T
7lR7umFjfrOcwRllxeZoXh5oTnM+PxJSLPn7wU0Ir/wpcR6con0G1OLFhx5LbNdv
gaBRCWbipMWt74HkZnPKFd9ng5nm605bJTqjDKRtLEXy4XixkCPgCb7Ho20wazAO
BgNVHQ8BAf8EBAMCBaAwEwYDVR0lBAwwCgYIKwYBBQUHAwEwDAYDVR0TAQH/BAIw
ADA2BgNVHREELzAtghNseGQxLjJlLXN5c3RlbXMuY29thwR/AAABhxAAAAAAAAAA
AAAAAAAAAAABMAoGCCqGSM49BAMDA2gAMGUCMG3YDI2Xzso+CrW05R23UJbQOXf5
U4u4e4/eA/EqkkrLs83dYOamgjEux09e5oMiNQIxAMgGVbuLf3s8AIWsNBkJ+7pb
SmadVM2ToQ09k6OlbPmu2O2yb4T0ayZnyIB+BhKb2A==
-----END CERTIFICATE-----
certificate_fingerprint: f16c37f4733db3cfbcb6068f040b0aff0a6957a1278714cdadc6376e171268c7
driver: lxc | qemu
driver_version: 5.0.2 | 7.1.0
firewall: xtables
kernel: Linux
kernel_architecture: x86_64
kernel_features:
idmapped_mounts: "false"
netnsid_getifaddrs: "true"
seccomp_listener: "false"
seccomp_listener_continue: "false"
shiftfs: "false"
uevent_injection: "true"
unpriv_fscaps: "true"
kernel_version: 4.18.0-490.el8.x86_64
lxc_features:
cgroup2: "true"
core_scheduling: "true"
devpts_fd: "true"
idmapped_mounts_v2: "true"
mount_injection_file: "true"
network_gateway_device_route: "true"
network_ipvlan: "true"
network_l2proxy: "true"
network_phys_macvlan_mtu: "true"
network_veth_router: "true"
pidfd: "true"
seccomp_allow_deny_syntax: "true"
seccomp_notify: "true"
seccomp_proxy_send_notify_fd: "true"
os_name: CentOS Stream
os_version: "8"
project: default
server: lxd
server_clustered: true
server_event_mode: full-mesh
server_name: lxd11
server_pid: 2706
server_version: "5.12"
storage: zfs
storage_version: 2.1.11-2
storage_supported_drivers:
name: btrfs
version: 5.16.2
remote: false
name: ceph
version: 17.2.0
remote: true
name: cephfs
version: 17.2.0
remote: true
name: cephobject
version: 17.2.0
remote: true
name: dir
version: "1"
remote: false
name: lvm
version: 2.03.11(2) (2021-01-08) / 1.02.175 (2021-01-08) / 4.46.0
remote: false
name: zfs
version: 2.1.11-2
remote: false

Issue description
attempted to lxd recover one container and attached storage volume, it went OK, but the uids/gids on the storage volume were wrong:
[root@vaulttest ~]# ls -al /testvol/
total 10
drwx--x--x  2 1000000 1000000  3 May 22 17:47 .
drwxr-xr-x 19 root    root    24 May 22 16:33 ..
-rw-r--r--  1 1000000 1000000 10 May 22 16:34 aa
Steps to reproduce
lxc launch images:ubuntu vaulttest
lxc storage volume create default testvol
lxc storage volume attach default testvol vaulttest /testvol
copy the containers away
zfs send mypool/containers/vaulttest | zfs receive mypool/temp/vaulttest
zfs send mypool/custom/default_testvol | zfs receive mypool/temp/default_testvol
lxc rm -f vaulttest
lxc storage volume delete default testvol
zfs rename mypool/temp/vaulttest mypool/containers/vaulttest
zfs rename mypool/temp/default_testvol mypool/custom/default_testvol
lxd recover
lxc exec vaulttest -- bash
[root@vaulttest ~]# ls -al /testvol/
you will see the output above, i.e. files have an uid of 100000 instead of 0

Please show "lxc config show (instance) --expanded" before and after restore.

Reproduced the issue.

It'd be good to have something for sure, but I'm not sure what can be done given that unlike instances, we don't really have a place for a backup.yaml type file on custom volumes...
What may push me towards "won't fix" is that VFS idmap is starting to be pretty ubiquitous, so the need for id remapping of instances and volumes is going to go down very rapidly over the next 6 months or so.

Idmapped mounts for the win!


User search screen should order prefix matches first

At present, user search results are shown with all matches in alphabetical order. This doesn't match what the user is trying to do, which is usually to put in the start of someone's name. It looks especially "broken" when the user first start typing, as it's unclear why these particular names are being shown, or why the name list didn't seem to change (or change much) when the first letter was typed.
We should change the ordering to show prefix matches with any part of the name above other results, the way we currently do in the right sidebar of the web app. It should be fine to just use <space> as the separator, or match whatever implementation we have in the web app.

@aly!, I tried a lot with this issue. Could you please explain a little bit more. I still not able to figure out where to start. Thanks 🙂

Hi @thisisnitish , please post any specific questions you have, as it's hard to help with such a general request. See here for some tips on asking good questions.

Thanks @alya!, since we both have worked on some issues, so I thought you will understand.

See here for some tips on asking good questions.

Sure I'll check it once and I will get back to you. Thanks 😊

@alya! Till now, I've observed is, searching of user doesn't starts from the first character it starts from the second character. But in our web app, searching starts from the beginning itself. Correct me if I'm wrong. Thanks 🙂

@thisisnitish Yes, there is a separate issue for changing that behavior on mobile: #4872.

Edited title to make explicit that this is about the user-search screen (the one you get from the "New PM" button), and not the typeahead for @-mentions. (The same thing should apply there, but it's a separate implementation.)


Datalogger infrastructure

TODO:

[ ] Finish state machine heartbeat
[ ] CAN msgs from heartbeat sent to datalogger IDs
[ ] Wiring harness integration

Also need a CAN database file of our CAN msgs - potentially for the datalogger? or maybe for the whole system idk


TypeError: unhashable type: 'c4d.BaseObject' raised when importing .omni file

This error occurs when attempting to import a .omni file using the importer or dragging it into the scene.
Tested in Cinema 4D versions R26.107 and R2023.1.3 with identical results.

INFO:OmniscientImporter:Selected .omni file: C:\Users\Mark\Downloads\IMG_181218028_10May\IMG_181218028.omni
INFO:OmniscientImporter:Parsed .omni data.
ERROR:OmniscientImporter:An error occurred while processing the .omni file:
Traceback (most recent call last):
File "C:\Program Files\Maxon Cinema 4D R26\plugins\OmniscientImporter\lib\OmniscientImporter.py", line 202, in import_omni_file
process_import(doc, obj_path, "Scan_Omni")
File "C:\Program Files\Maxon Cinema 4D R26\plugins\OmniscientImporter\lib\OmniscientImporter.py", line 50, in process_import
objects_before_import = set(doc.GetObjects())
TypeError: unhashable type: 'c4d.BaseObject'

However, the importer is able to successfully create a material with the background footage, create a C4D background object, and apply the material to it.
Files exported in the Omniscient app version 1.15.1 on the iPad pro 3rd gen (16.4.1) with the C4D option selected only.

Ah that change would make sense.
The fix for both my C4D versions worked incredibly well.
Thank you for your time!

Thanks @EnderElement for confirming that it fixes the issue! Enjoy the app :)


Remove the letter 's' from "InitialTransformParametersFileName"

By default, started using "InitialTransformParameterFileName" (without 's'), instead of "InitialTransformParametersFileName" (with 's'), as parameter name.
This commit still supports reading and retrieving the old parameter name, but only for backward compatibility (producing a warning).
Aims to improve consistency. The elastix manual uses the term "parameter file" (and not "parameters file"), and itk::ElastixRegistrationMethod has GetInitialTransformParameterFileName and SetInitialTransformParameterFileName member functions (without 's' in their name).
Addresses issue https://github.com/SuperElastix/elastix/issues/900, "InitialTransformParametersFileName or InitialTransformParameterFileName? (with or without letter 's')"

Discussed at the sprint today, we agreed to have it merged. But carefully!


Load instrumentation key from appsettings or code

Do you have any plans to add support for loading the instrumentation key from appsettings, or from the app startup code? Looking at ways to avoid having to create copies of index.html for different deployment environments and interested if you had considered this and / or had any ideas about how best to tackle it?

Out of curiosity do you mind sharing some details on how you replaced the key in your pipeline?
I have an Azure App Service for my application where I configure settings etc. however I haven't managed to find a way to replace to instrumentation key in the JavaScript in head in index.html.
Maybe you are using a complete different setup, however any input are greatly appreciated.

For the scenario where the application insights key is known at deploy time, we ended up breaking out the script block into a script file then in our repo we include a local dev script file (applicationinsights.js) and a copy for each environment (e.g. applicationinsights.DEV.js). Then in the Deploy to App Service task we set a post deploy script that deletes the local dev applicationinsights.js file and copies over the appropriate one for the environment we are deploying to (e.g. applicationinsights.QA.js -> applicationinsights.js).
You could use the same idea for index.html but in our scenario everything else in there was identical and we didn't want to have to keep all the copies in sync as changes were inevitably made to index.html.

This feature has been added in 1.1.0. https://github.com/IvanJosipovic/BlazorApplicationInsights#set-instrumentation-key


CacheV2 should support multiple key files

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Feature
Enter Task Name: CacheV2
Environment

Server - Azure Pipelines
Agent - Hosted

Issue Description
CacheV2 currently does not support multiple key files. This was recently added to GitHub Actions via multiple arguments to the hashFiles function. See https://github.com/actions/cache/issues/143.

IIRC comma separating works. Do you see otherwise?

@johnterickson Doh! I somehow missed this is documented too. Will give it a go, thanks!

Indeed, this works as expected. 😸


R.id.back not resolved in AppIntroBase.java

java.lang.NoSuchFieldError: com.github.paolorotolo.appintro.R$id.back
at com.github.paolorotolo.appintro.AppIntroBase.onCreate(AppIntroBase.java:86)

AppIntro Version 4.10
My devices: Nexus 5X 7.1.1 and Galaxy Tab E 4.4.4
The project compile, only crashes in runtime
And the error happend before my own code, happens at super.onCreate class method

EDIT1:
My gradle

Hmm...strange. Let me mess around a bit and I'll get back to you. Thanks for the detailed issue.

I think is something with the layouts that doesn't have the ids declaration on XML, or you might removed and let the code there, because the 4 layouts that came in gradle download dind't had those declarations in layout. I  think that must be a easy solution, if I download the zip from release, they work, but directly from gradle must be something missing

@paolorotolo This issue is not there anymore. Can be closed for inactivity


Hubot 3.0.1 robot.messageRoom with Slack - TypeError: Cannot read property 'send' of undefined

I'm using "hubot": "^3.0.1" and "hubot-slack": "^4.3.4"
calling this method:
module.exports = robot => {
  robot.messageRoom({ room: "general" }, "hello");
}

I get : TypeError: Cannot read property 'send' of undefined
It seems that @client in  @client.send(envelope, message) in hubot-slack bot.coffee is undefined.
how is it possible that @client is undefined? shall I bind it somehow?
thanks

I found that is fixed in the latest master: https://github.com/cirpo/hubot/blob/8b0b8a9ba80e6d65df2e644b106c43d4b309d01f/src/robot.js#L608
thanks, I'll wait for a release then


feat(tools, daffio): generate interface docs with dgeni; generate doc…

…s for all public fields
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?
Only fields that have decorators (like @Input and @Output) are added to the documentation for a class doc.
What is the new behavior?
All public-facing fields of classes/interfaces have docs generated for them.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information
The type fields are rarely correct, and I think a lot can be done in the components themselves to make the documentation look better. But I think it's definitely an improvement.

@lderrickable I don't know what type is in several of the contexts rendered.

I think this is a general improvement on the current state of the docs. It makes certain things worse, but as a whole adds a net positive. Will merge, but we should revisit the "type" splitting that's going on in the docs, as it appears to cause other kinds of issues.

@damienwebdev yea, I mentioned that in the description. I don't think the types ever actually worked better than they do in this PR. It's just that we could only see the types for Inputs and Outputs, which are all non-generic types (i.e. without < or >). I think dgeni gets confused by more complex types like Observable<boolean>. It only takes the first part, Observable.

@damienwebdev @lderrickable see #1095 for more info. Its being caused by overeager HTML sanitation.


Backup JupyterHub databases

Background
We currently use the default sqlite database backend for JupyterHub, held in a small PVC disk attached to each hub. Most important information here is list of allowed users - for most of our hubs, this is the only place they are in.
We currently don't back this up! We should.
Options
There are two options from my perspective.

Move to a postgresql server. 1 db per cluster, with 1 db per hub.
Use something like litestream to backup sqlite to object storage.

I very much prefer (2) - it's a lot simpler, and fits our use case (backup) very well.

To do (2), we'll need to give each hub pod some way to write to a GCP bucket. Not sure what's the easiest way to do that is

we'll need to give each hub pod some way to write to a GCP bucket.

And I guess it is the same for an S3 bucket on the AWS-based deployments, right?

And I guess it is the same for an S3 bucket on the AWS-based deployments, right?

Yep!

The primary problem here is to avoid 'leaking' one hub credentials to another. Each hub should be able to backup its own database (in a write-only fashion) and nothing else. So the service account provisioned for each hub should have write access only to its object, and nothing else. And we should just put everything in a centralized GCS for simplicity.
So, we need to:

Create a GCS bucket for storing these databases
As part of the deployer, create a Service Account with access to a prefix in this bucket for each hub
Write a sidecar that backs up the database (and any additional files) to this prefix on the bucket

We could've used https://kubernetes.io/docs/concepts/storage/volume-snapshots/ but it isn't available in most clouds yet (since it requires migrating to a CSI driver for storage), and I'm worried that kubernetes errors might make it not work. I would rather have the backup mechanism be on a pathway that isn't dependent on kubernetes

I would rather have the backup mechanism be on a pathway that isn't dependent on kubernetes

I agree with that!

Setting this one as a low priority for now, since I don't think that this is actively problematic right now (but would be eventually, so we should keep track of it and prioritize higher in the future once some of our bigger infrastructure issues are improved)


Remove c++14 support in proxy-wasm.

Signed-off-by: John Plevyak<EMAIL_ADDRESS>

This depends on https://github.com/proxy-wasm/proxy-wasm-cpp-host/pull/46
Once that goes in I will update it.


Feature/blui storybook

Changes proposed in this Pull Request:

Go BLUI for the storybook API docs

This needs to go to master.

same here for alpha


Settings stored in the database override those set in the settings.cfg?

Changes to settings.cfg seem not to have any effect after the settings have been save to the database. I've tested this with SITE_NAME, SITE_LOGO and SITE_ICON, but a quick look at server.py does not reveal any special treatment for those keys. Is my assessment correct?
My expectation would have been that settings in the configuration file (settings.cfg) are always respected as the "source of truth". That enables changing the configuration without poking at database contents or doing changes manually via Otterwiki web admin page. At minimum I think the documentation (here) should be changed to reflect how Otterwiki loads the configuration.

Hey @mattock, what you've observed and read in the code is correct and works as intended ... but I agree, this can be counterintuitive and should be documented. Thank you for bringing this up!
How An Otter Wiki can be configured grew over time. At first there was only the settings.cfg and with the docker image came the environment variables and later the admin interface, that stores the settings in the database.
The implementation of the behaviour you expected is tricky: The settings.cfg is loaded first, the environment variables second .. because the SQLALCHEMY_DATABASE_URI has to be configured to load the database. After loading the settings from the database, the setings from the settings.cfg and the environment variables could be re-applied, but this feels hacky. And that these variables are immutable must be visible in the admin interface.
I will give it some thought. I can imagine circumstances where this makes sense.

Updated the documentation https://otterwiki.com/-/commit/5819b3


:bug: fix echarts as dependency and remove potential unnecessary maps

world, china for province only map

Codecov Report

Merging #111 into master will increase coverage by 0.41%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #111      +/-   ##
==========================================
+ Coverage   96.92%   97.33%   +0.41%
==========================================
  Files          56       56
  Lines        1917     1916       -1
==========================================
+ Hits         1858     1865       +7
+ Misses         59       51       -8

Impacted Files
Coverage Δ

pyecharts/custom/page.py
97.43% <ø> (+12.82%)
:arrow_up:

test/test_page.py
100% <ø> (+3.61%)
:arrow_up:

pyecharts/charts/map.py
100% <100%> (ø)
:arrow_up:

pyecharts/base.py
80.41% <100%> (ø)
:arrow_up:

pyecharts/constants.py
100% <100%> (ø)
:arrow_up:

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 5738fce...aa4b8c4. Read the comment docs.


explore card hover effect added

fixes issue #776
Result
Screencast from 2023-10-02 22-23-27.webm
Added hover effect based on the theme of the website and better user experience

What type of PR is this? (check all applicable)

[ ] ♻ Refactor
[X] ✨ New Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 👷 Example Application
[ ] 🧑💻 Code Snippet
[ ] 🎨 Design
[ ] 📖 Content
[ ] 🧪 Tests
[ ] 🔖 Release
[ ] 🚩 Other

Description

This PR [adds/removes/fixes/replaces] this [feature/bug/etc].
Related Tickets & Documents

Resolves #
Mobile & Desktop Screenshots/Recordings

Added code snippets?

[ ] 👍 yes
[X] 🙅 no, because they aren't needed

Added tests?

[ ] 👍 yes
[X] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

No tests? Add a note

Added to documentation?

[ ] 📜 readme
[ ] 📜 contributing.md
[ ] 📓 general documentation
[X] 🙅 no documentation needed

@angiejones merging

@captain-Akshay Really nice change thank you! 🥳


Add #jobs-bulletin listener.

As suggested in the #uqcs-meta channel, set up a listener for posts to #jobs-bulletin that posts a follow up message there directing all questions/related discussion to #jobs-discussion.
Message should be a generic notice that the channel is for job postings only so as to not be out of place should the poster decide upon seeing it to remove their message.
Additionally, a message should be sent to poster explaining the purpose of the bulletin (and outlining any rules/suggestions for posts there - i.e. fair work compliance, and a warning about what to expect on posting an 'unpaid role').

I think the first two paragraphs should be the focus of a bot feature and the final paragraph probably implemented instead as a "READ ME BEFORE POSTING" on the channel (i.e. in description or some shit)


Set displayName and __ui__ for @yamada-ui/snacks

Closes #2904

@hirotomoyamada
fixed.
please review


AsyncLock fixes

Case, which lead to the issue:
There is a separate view with the RestClient used internally. When the view should be closed (using back navigation), it disposes the RestClient regradless of running requests. Even if running tasks are cancelled, the ObjectDisposedException could be thrown, if disposing occurred before the request is completed.

:+1:

I'll create new NuGet packages in the next couple of days


SearchV3: Show in profile view on desktop

@keybase/react-hackers
Here's a rebase of #7310 against master, that PR was based off @MarcoPolo's WIP branch.  No other changes from the approved version.

The commits f903feeb938b...20c2c267f44d introduce visual changes on linux. :mag_right: 1 new

Added: Colors-white_20_rgba_255_255_255_0_20


Sampling for bin construction

@guolinke If I understand correctly, bin_construct_sample_cnt is used to set the number of observations used to create the bins.  Could you confirm whether this is a random sample or a sample of the top n observations?  Thanks.

it is random sample.

@guolinke Could you explain what is happening in this example?  I have  a single predictor, x1, with two possible values: 1 or 2.  When the dataset is sorted by x1, I get the error:
[LightGBM] [Fatal] Cannot construct Dataset since there are not useful features.
Error in lgb.call("LGBM_DatasetCreateFromMat_R", ret = handle, private$raw_data,  :
api error: Cannot construct Dataset since there are not useful features.
When I randomize the order of observations, it gives the expected results.
Code:
library(lightgbm)

# Create a sample dataset
set.seed(1)
df <- data.frame(x1 = as.numeric(c(rep(1,400000), rep(2, 100000))))
df$y <- df$x1 + runif(nrow(df))

lgb.unloader()
lgb.model1 <- lgb.train(
  data = lgb.Dataset(data = as.matrix(df[, c("x1")]), label = df$y)
  ,obj = "regression_l2"
  ,nrounds = 1
)

# Randomize order of observations, then refit
lgb.unloader()
df <- df[sample(1:nrow(df)), ]
lgb.model2 <- lgb.train(
  data = lgb.Dataset(data = as.matrix(df[, c("x1")]), label = df$y)
  ,obj = "regression_l2"
  ,nrounds = 1
)
table(predict(lgb.model2, as.matrix(df[, c("x1")])))

The issue seems to be related to bin_construct_sample_cnt.  In the above example, I tested values of bin_construct_sample_cnt between 1,000 and 600,000 in increments of 1,000.  It seemed to only produce the error when bin_construct_sample_cnt was between approximately 126,000 and 133,000 or between 167,000 and 200,000.  Other values would run fine.

refer to https://github.com/Microsoft/LightGBM/blob/master/include/LightGBM/utils/random.h#L65
sample K from N.

@rgranvil it seems the final sampling has some problems

@guolinke Yes, it seems that in the Sample function, some values of N and K would make it very unlikely to sample from the bottom of the data.
Would this sampling approach work as an alternative?
https://stackoverflow.com/a/9345144

@guolinke or is there a reason this method couldn't be used for all K < N?
else if (K > N / 2) {
for (int i = 0; i < N; ++i) {
double prob = (K - ret.size()) / static_cast(N - i);
if (NextFloat() < prob) {
ret.push_back(i);
}
}

@rgranvil
This algorithm is O(N), while another is O(K).
I think we can change it to the hashset solution for the stable result.

@guolinke If it was R coding, I could probably help out, but I don't know nearly enough C++ to be of any help implementing it


Fix variable name in AwsS3EnvironmentRepository.java for readability

Issue #2222
I have renamed the variable to make it more readable
The object is yaml, not json.

@deeaitche Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@pivotal-cla This is an Obvious Fix”

@deeaitche This Pull Request contains an obvious fix. Signing the Contributor License Agreement is not necessary.


[Snyk] Security upgrade @sveltejs/kit from 1.25.0 to 1.26.0

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

⚠ Warning
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

481/1000  Why? Recently disclosed, Has a fix available, CVSS 3.9
Information Exposure SNYK-JS-UNDICI-5962466
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
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.

fixed on #148


Greenkeeper/@types/node 11.13.9

Fixes #144

Coverage remained the same at 100.0% when pulling 8d8a635f82a0a17527773f1007d79ba3c12d6629 on<EMAIL_ADDRESS>into 16bff4fb8cb1c82bb99517212df29832075b0fde on master.

Fixes #144