Flavors & App Bundle missing index.android.bundle with proguard enabled

Issue
We use the flavors into our apps to use different version. We have dev, test and prod. When we have upgraded to 0.63 (same with 0.64), to classpath("com.android.tools.build:gradle:3.5.3") and distributionUrl=https://services.gradle.org/distributions/gradle-6.2-all.zip and  proguard enabled,  we cannot use the appbundle.
when we run ./gradlew bundleDevRelease -> we cannot find into the app-dev-release.aab the index.android.bundle. This cause a crash when open the app.
If we run this command : ./gradlew bundleRelease -> it build all variants
app-dev-release.aab -> missing
app-test-release.aab -> index.android.bundle present
app-prod-release.aab -> index.android.bundle present
Description
Please provide a clear and concise description of what the bug is. Include screenshots if needed.
Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html
React Native version:
System:
OS: macOS 10.15.7
CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
Memory: 944.16 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.15.4 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.14.10 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
Android SDK:
API Levels: 23, 27, 28, 29
Build Tools: 26.0.2, 27.0.3, 28.0.3, 29.0.2, 29.0.3
System Images: android-19 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom_64, android-27 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.87<IP_ADDRESS>53283
Xcode: 12.0/12A7209 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_201 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.0 => 0.64.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
1.Create a new project: npx react-native init AppName --template react-native-template-typescript
2. Add to gradle.build :
productFlavors {
prod {
}
dev {
applicationId 'com.appname.dev'
resValue "string", "build_config_package", "com.appname"
}
test {
applicationId 'com.appname.test'
resValue "string", "build_config_package", "com.appname"
}
}
3. Enable Proguard
4. run into android folder : ./gradlew clean && ./gradlew bundleDevRelease
Expected Results
Obtain an .aab file into android/build/outputs/bundle/devRelease. when i open the .aab i expect to find the folder base and into the base the folder assets that contain the index.android.bundle.

@lorenzoangelini This issue has now been resolved in 0.64.
https://github.com/facebook/react-native/pull/30177

@gedeagas i reproduce this issue when proguard is active

@lorenzoangelini Interesting, do you mind providing a git repo of the problem?
@renopp This is probably related to your case ( multiflavors, prod aab dosen't have index.android.bundle, etc ). Let's try to fix this if there is a problem here.

@gedeagas with a new project i reproduce this issue when i using flavors.

Can reproduce on RN 0.64.0 🤔
I'd share the git repo, but this app is private for a client.
I don't use productFlavors, only buildTypes.
Debug and prod APKs work fine.
// build.gradle
buildTypes {
    release {
        signingConfig signingConfigs.release
        minifyEnabled enableProguardInReleaseBuilds
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        minifyEnabled true
        shrinkResources true
    }
    releaseUnsigned {
        initWith release
        signingConfig null
        // needed to prevent react native dependency code failing
        // to build
        matchingFallbacks =  ['release']
    }
}

// ------------------------------------------------

// proguard-rules.pro
-keep public class com.horcrux.svg.** {*;}

react-native info ouput

info Fetching system and libraries information...
System:
    OS: Windows 10 10.0.19042
    CPU: (6) x64 Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
    Memory: 3.70 GB / 15.94 GB
  Binaries:
    Node: 15.1.0 - ~\AppData\Local\Temp\yarn--1616780838243-0.2835069363144411\node.CMD
    Yarn: 1.22.5 - ~\AppData\Local\Temp\yarn--1616780838243-0.2835069363144411\yarn.CMD
    npm: 7.6.3 - c:\users\david\appdata\roaming\npm\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK:
      API Levels: 23, 24, 25, 26, 28, 29, 30
      Build Tools: 28.0.3, 29.0.2, 30.0.2, 30.0.3
      System Images: android-26 | Android Wear Intel x86 Atom, android-28 | China version of Wear OS Intel x86 Atom, android-28 | Wear OS Intel x86 Atom, android-30 | Google APIs Intel x86 Atom
      Android NDK: Not Found
    Windows SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Visual Studio: 15.9.28307.1321 (Visual Studio Community 2017)
  Languages:
    Java: 11.0.7 - c:\program files\adoptopenjdk\jdk-<IP_ADDRESS>-hotspot\bin\javac.EXE
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: ^0.64.0 => 0.64.0
    react-native-windows: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

@davwheat so it's working on RN 63? hmm.. that is strange.
I will be looking at this on Monday. Thanks for the report.

It was working before I upgraded on 20th March -- I suppose it could have come in from another change I've made, but I doubt any JS changes would cause it, and I haven't tinkered with my build process at all (except the upgrade process).
If you want me to test anything or give you more info, let me know :)

@davwheat  me too, i don't have any problem with 0.62, the app bundle was build correctly.

@davwheat do you also have proguard turned on like @lorenzoangelini ?

@gedeagas Yes, I use proguard, including a custom rule which I posted above.

Any updates on this? We're also having issues on bundling android releases with proguard enabled

@lorenzoangelini @davwheat @danaelisanicolas
I just created a PR to fix the issue, kindly check

Apologies for the tangent, but the I was scanning the react-native issues list for a different reason and saw this - I patterned a change to the react-native-elements font-copy task after the changes done here in the react-native repo to handle gradle 4.1+, and it's the same code area - if anyone using react-native-elements notices that for app bundles that use flavors and variants you aren't seeing your fonts copied, it may be that the same sort of change needs to be carried into the react-native-elements font-copy gradle task, c.f. https://github.com/oblador/react-native-vector-icons/pull/1307

Hi, Actually mine got fixed when I change from:
buildTypes {     debug {         signingConfig signingConfigs.debug     }     release {         // Caution! In production, you need to generate your own keystore file.         // see https://reactnative.dev/docs/signed-apk-android.         minifyEnabled true         shrinkResources true         signingConfig signingConfigs.release         proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"     } }
to just:
buildTypes {     debug {         signingConfig signingConfigs.debug     }     release {         // Caution! In production, you need to generate your own keystore file.         // see https://reactnative.dev/docs/signed-apk-android.         minifyEnabled enableProguardInReleaseBuilds         signingConfig signingConfigs.release         proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"     } }
and for context my proguard file looks like this:
-keep class com.facebook.hermes.unicode.** { *; } -keep class com.facebook.jni.** { *; } -keep public class com.horcrux.svg.** {*;}
Please correct me if i'm wrong, but from what I understand, minifyEnabled WITHOUT the proguard reference doesn't keep the files (during minifying and shrinking) that hermes, jni, and svg needs which then gets null reference pointer exception when bundled and ran.

I think the bigger issue is that we shouldn't suddenly have builds break for no apparent reason, especially when it's not super easy to test aabs, and when it's not listed in the changelog.
The PR is a simple one line fix (I haven't tested it personally, but I trust that it works) so merging that should be a priority over other workarounds, otherwise people will put off upgrading RN as it breaks their app.

Hi, Actually mine got fixed when I change from:
buildTypes {
    debug {
        signingConfig signingConfigs.debug
    }
    release {
        // Caution! In production, you need to generate your own keystore file.
        // see https://reactnative.dev/docs/signed-apk-android.
        minifyEnabled true
        shrinkResources true
        signingConfig signingConfigs.release
        proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
    }
}

to just:
buildTypes {
    debug {
        signingConfig signingConfigs.debug
    }
    release {
        // Caution! In production, you need to generate your own keystore file.
        // see https://reactnative.dev/docs/signed-apk-android.
        minifyEnabled enableProguardInReleaseBuilds
        signingConfig signingConfigs.release
        proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
    }
}

and for context my proguard file looks like this:
-keep class com.facebook.hermes.unicode.** { *; }
-keep class com.facebook.jni.** { *; }
-keep public class com.horcrux.svg.** {*;}

Please correct me if i'm wrong, but from what I understand, minifyEnabled WITHOUT the proguard reference doesn't keep the files (during minifying and shrinking) that hermes, jni, and svg needs which then gets null reference pointer exception when bundled and ran.

my problem was app would crash when open (AAB), but no issue for debug app & APK.
fixed with remove shrinkResources in build.gradle.
thanks @danaelisanicolas
my error log:
12-10 15:04:34.984 27112 27112 E AndroidRuntime: FATAL EXCEPTION: main
12-10 15:04:34.984 27112 27112 E AndroidRuntime: Process: com.brambang.apps, PID: 27112
12-10 15:04:34.984 27112 27112 E AndroidRuntime: java.lang.AssertionError: APK bundle must contain the expected embedded asset index.android.bundle
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.l.e.a(Unknown Source:147)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.l.e.g(Unknown Source:50)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.l.e.e(Unknown Source:10)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.l.g.x(Unknown Source:64)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.l.g.B(Unknown Source:96)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.f.D(Unknown Source:75)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.f.s(Unknown Source:5)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.UpdatesPackage$a.b(Unknown Source:12)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at f.a.e.createReactInstanceManager(Unknown Source:33)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at com.facebook.react.s.a(Unknown Source:9)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at com.brambang.apps.MainApplication.onCreate(Unknown Source:11)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1193)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6991)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.app.ActivityThread.access$1500(ActivityThread.java:257)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1982)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:106)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:236)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:8056)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:656)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:967)

I was also missing index.android.bundle after updating RN 0.64.x => 0.66.x and what worked for me was calling
./gradlew assembleMyFlavorRelease

instead of
./gradlew assembleRelease

I was using the latter previously, which builds all flavors at once. Apparently if you assemble each flavor one at a time, it works.

Ciao,
I'm writing for all the people who, like me, have experienced this problem.
Affected Versions

React Native: 0.67.x
Gradle 7.2.x - 7.3.x

The common error

Unable to load script. Make sure you're either running a Metro server (run 'react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release.

In short, index.android.bundle is missing.
Common problem when trying to use productFlavors.
The problem
I found that the problem is in a native react gradle task, to be precise in the copy task called currentAssetsCopyTask located in react.gradlefile.
As I understand, this "task" is responsible for copying the assets and in particular index.android.bundle and pasting them into the temporary directories used to generate the APK.
The solution
I created a repo that with a js script solves the problem before building the android app
https://github.com/9christian9/FIX-Android-productFlavors-RN0.67-gradle7.2-7.3
I hope this will help.
With ♥ by Christian


docs: Docs (sample notebook) for Vertex Check Grounding Wrapper + Update Google Provider mdx docs

Adding 2 documentation updates:

Vertex Check Grounding API  Wrapper - The check grounding API determines how grounded a given piece of text is in a given set of reference texts. The API can generate supporting citations from the reference text to indicate where the given text is supported by the reference texts.
Update the Google Provider mdx docs with the Rerank and Check Grounding API

+1, I did not think that tools was the right place, but I saw some existing integrations (which are not tools) like Upstage (which also does grounding check) and Wolfram Alpha under tools, so I placed it there as well.
Do let me know what would be a more appropriate place and I'll send out a change for that! 🙏
Thanks
cc: @RajeshThallam @lkuligin

Hi @hwchase17 @efriis, just wanted to follow up on this to see if there is any resolution on where to place the docs ? Thank you!

Could you

add a small example to the docstring in langchain-ai/langchain-google, so that it renders in the api docs: https://api.python.langchain.com/en/latest/vertex_check_grounding/langchain_google_community.vertex_check_grounding.VertexAICheckGroundingWrapper.html#langchain_google_community.vertex_check_grounding.VertexAICheckGroundingWrapper
reopen this pr with just the provider changes, linking to the api doc with the example code

Thanks!


Sync SnowflakeHook return type and add SnowflakeSensorAsync

Sync SnowflakeHook return type to conform to upstream OSS SnowflakeHook from provider 4.0.2 (https://github.com/apache/airflow/pull/28006)
Add SnowflakeSensorAsync (need to add test)

Fixes https://github.com/astronomer/astronomer-providers/issues/729

@park-peter  LGTM. Can you rebase the branch and fix the CircleCI failures

@park-peter @phanikumv I would just to create an issue to add the example DAG in integration tests


Laravel api resource exception is being generated

Laravel Version: 5.5.25
PHP Version: 7.0.22

Description
I'm generating resources for my api with apiResource and exceptions I define are being ignored.
Selected content of routes/api.php
Route::apiResource('posts', 'PostController', ['except' => ['show']]);
Selected output of  php artisan route:list
GET|HEAD | api/posts/{post} | posts.show | App\Http\Controllers\PostController@show | api
Not sure if this is a lacking feature or a bug.
To reproduce.
Create a project
Generate a controller:
php artisan m:controller PostController
Create an api route for the controller in routes/api.php by adding the following code:
Route::apiResource('posts', 'PostController', ['except' => ['show']]);
For this app we don't want the specific show method hence we added an extra param called except which as stated here should instruct laravel to ignore the specific one's we instruct it to ignore.

What exceptions do you define and how are you defining them?
Please include a detailed steps of replication, I don't seem to understand your issue.

@themsaid by exceptions I mean adding the  ['except' => ['show']] part while generating the resource.
The expected behavior is that the route posts.show shouldn't be generated but it is as shown by output of route:list command. I've updated the reproducing instructions.

Yeah it seems like you can't use except with apiResources since only is already used under the hood and it overrides the except, switch to using Route::resource instead.

Thanks, I'll close this for now. Would be something nice to have in a later version though.


bump for v1.0.0a2

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe (might be a conda-smithy bug) :cry:

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@jhamman we can get the checksum directly from PyPI from URL:
https://pypi.org/project/netcdftime/#files
If you do have to calculate it yourself, like for GitHub tarballs, you can use these instructions.

@ocefpaf - thanks for keeping an eye on this. I'm still learning the process and the checksum seems to be difficult for me to get right.

and the checksum seems to be difficult for me to get right.

Not only for you we all messed that up at some point. But in the near future we will add a functionality to get the checksum automatically from PyPI, avoiding such headaches.


Commands are not saved

I followed the instructions on the README, installed PS Core, the package with the package manager, I can add new aliases (with Import-WslCommand) of my WSL, and it works. But when I close the PowerShell window, and open a new one, the aliases are gone.

Are you adding the Import-WslCommand call to your PowerShell profile?

My bad, I definitely read the explanations too quickly 😅
Thank you for the fast answer, it fixed it indeed!
Love your project


Flash attention and attention mask modification. Does the model support flash attention?

Dear authors,
first of all congrats for your idea and paper!!
I have a question about the code. I see here https://github.com/Yxxxb/VoCo-LLaMA/blob/79859d0ad7df2f322ae7b06c58d246b062f39ffd/llava/model/language_model/llava_llama_1stg.py#L263 that in flash attention you do not modify the attention mask. Is it expected?
thanks

Hi,
Thank you for your interest.
Since we need to use a 4d attention mask, but the open source flash attention only supports a 2d casual attention mask, we chose the standard sdpa and modified the attention mask based on that.


Design Resources section

[x] I have followed (at least) the PR section of the contributing guide.

@iRyanBell You can already find them a https://material-ui.com/discover-more/related-projects/#design-resources.


Assign-user does not work with application user

Hi,
When I want to execute assign-user, I get following error: Error: Insufficient privileges to complete the operation.
The authentication is done with a service principal.
#Get the client secret from the machine
$appId = "xxx"
$secret = "xxx"
$tenantId = "xxx"
$environmentId = "xxx"
$maker =<EMAIL_ADDRESS>#Create connection to the Power Platform tenant
pac auth create --applicationId $appId --clientSecret $secret --tenant $tenantId --environment $environmentId
pac admin assign-user --environment $environmentId --user $maker --role 'Environment Maker'
Is this a bug?

@snizar007 any update on this?


Drowsiness detection using EEG signals using DL

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Drowsiness Detection Using EEG Signals
:red_circle: Aim : To develop a deep learning model to detect drowsiness from EEG signals using various algorithms and compare their performance to identify the best-fitted algorithm based on accuracy scores.
:red_circle: Dataset : https://figshare.com/articles/dataset/EEG_driver_drowsiness_dataset/14273687
:red_circle: Approach :

Exploratory Data Analysis (EDA):

Analyze and preprocess the EEG dataset.
Visualize EEG signals and class distributions.

Model Development:

Implement the provided deep learning model using TensorFlow and Keras.
Develop and implement three additional models:

Convolutional Neural Network (CNN).

Model Training and Evaluation:

Train each model on the EEG dataset.
Evaluate models using accuracy, precision, recall, and F1-score.
Compare performances to identify the best model.

Visualization and Conclusion:

Visualize training and validation metrics.
Provide insights and conclusions based on model comparisons.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name : Kamakshi Ojha
GitHub Profile Link : https://github.com/KamakshiOjha
Email ID<EMAIL_ADDRESS>What is your participant role? (Mention the Open Source program) GSSOC

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

What are the CNN architectures you are planning to use here?
Apart from CNN what are the models you are planning to implement for this EEG dataset?
@KamakshiOjha

Input Layer:

Input Shape: (30, 128, 1)

Convolutional Layers:

Branch 1:

Conv2D with 16 filters, kernel size (1, 3), ReLU activation
Conv2D with 32 filters, kernel size (1, 3), ReLU activation
Conv2D with 64 filters, kernel size (1, 3), ReLU activation
cbam_block applied to the output

Branch 2:

Conv2D with 16 filters, kernel size (1, 5), ReLU activation
Conv2D with 32 filters, kernel size (1, 5), ReLU activation
Conv2D with 64 filters, kernel size (1, 5), ReLU activation
cbam_block applied to the output

Branch 3:

Conv2D with 16 filters, kernel size (1, 7), ReLU activation
Conv2D with 32 filters, kernel size (1, 7), ReLU activation
Conv2D with 64 filters, kernel size (1, 7), ReLU activation
cbam_block applied to the output

Combined Branch:

The outputs from the branches are combined using an Add layer.
Further Convolutional Layers:

Conv2D with 64 filters, kernel size (1, 3), ReLU activation
Conv2D with 128 filters, kernel size (1, 3), ReLU activation
Conv2D with 128 filters, kernel size (1, 3), ReLU activation

Global Pooling and Fully Connected Layers:

GlobalAveragePooling2D applied to the last convolutional layer.
Fully connected (Dense) layers:

Dense with 512 units, ELU activation
Dense with 256 units, ELU activation
Dense with 128 units, ELU activation
Dense with 32 units, ELU activation
Output Dense with 2 units, Softmax activation (for classification)

Since my dataset consists of EEG signals, I've experimented with various CNN architectures to find the best results. Additionally, I've incorporated an attention mechanism into my model to enhance its performance.

Input Layer:

Input Shape: (30, 128, 1)

Convolutional Layers:

Branch 1:

Conv2D with 16 filters, kernel size (1, 3), ReLU activation
Conv2D with 32 filters, kernel size (1, 3), ReLU activation
Conv2D with 64 filters, kernel size (1, 3), ReLU activation
cbam_block applied to the output

Branch 2:

Conv2D with 16 filters, kernel size (1, 5), ReLU activation
Conv2D with 32 filters, kernel size (1, 5), ReLU activation
Conv2D with 64 filters, kernel size (1, 5), ReLU activation
cbam_block applied to the output

Branch 3:

Conv2D with 16 filters, kernel size (1, 7), ReLU activation
Conv2D with 32 filters, kernel size (1, 7), ReLU activation
Conv2D with 64 filters, kernel size (1, 7), ReLU activation
cbam_block applied to the output

Combined Branch:

The outputs from the branches are combined using an Add layer.

Further Convolutional Layers:

Conv2D with 64 filters, kernel size (1, 3), ReLU activation
Conv2D with 128 filters, kernel size (1, 3), ReLU activation
Conv2D with 128 filters, kernel size (1, 3), ReLU activation

Global Pooling and Fully Connected Layers:

GlobalAveragePooling2D applied to the last convolutional layer.

Fully connected (Dense) layers:

Dense with 512 units, ELU activation
Dense with 256 units, ELU activation
Dense with 128 units, ELU activation
Dense with 32 units, ELU activation
Output Dense with 2 units, Softmax activation (for classification)

Cool. Go ahead with this approach.
Assigned @KamakshiOjha


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/1028 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit ae2fa69:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_main_2022-02-10-02-33-12 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Pyserial asyncio as submodule

alternativ to #437
workaround until pyserial/pyserial-asyncio#9 is resolved
fix for #429

Coverage remained the same at 93.174% when pulling 195a47b774fcca8907b8f99e0f8e2d3b86bd0ae0 on pyserial-asyncio_as_submodule into 80af31d2abe0e72b7ce35ff9556ee9d4e494cfee on dev.

Coverage increased (+0.01%) to 93.186% when pulling 195a47b774fcca8907b8f99e0f8e2d3b86bd0ae0 on pyserial-asyncio_as_submodule into 80af31d2abe0e72b7ce35ff9556ee9d4e494cfee on dev.


Hotfix: compute API version used in ARM templates

Which issue this PR addresses:
No Jira ticket; small thing I encountered doing some other work.
What this PR does / why we need it:
While I was working on deploying our shared dev infra in the Red Hat tenant I encountered an error indicating that the API version specified for the compute RP didn't seem to exist. I traced it back to this commit: https://github.com/Azure/ARO-RP/pull/3600/commits/de3f34242f1c31b8d9762fd364a16df3b63b5e73. You can see the exact error message if you check out my commit messages on this PR.
My PR switches our ARM templates to use the latest stable compute API version.
If the current API version, 2021-12-01, is truly no longer available, I expect that this issue will block any upcoming RP deployments in any environments.
Test plan for issue:
Validated that I no longer encounter issues locally. E2E will validate it in CI as well.
Is there any documentation that needs to be updated for this PR?
N/A
How do you know this will function as expected in production?
E2E in CI + E2E in canary during the next RP release.

/azp run ci, e2e

/azp run ci, e2e

/azp run e2e

/azp run e2e

/azp run e2e

/azp run e2e


Is there a way to calculate the months the user has been on github?

Since some people haven't been on github for a year yet (like me), in their account age thing, it will say "0". So can you implement something that will say like __ years and __ months? Thanks!

I don't have the bandwidth to do so right now, PRs are welcome though.

Ok.


Updating Rails patch version to <IP_ADDRESS>

Fixes CVE-2018-16476
https://groups.google.com/forum/#!msg/rubyonrails-security/FL4dSdzr2zw/zjKVhF4qBAAJ
Rails Changelog https://weblog.rubyonrails.org/2018/3/29/Rails-5-0-7-and-5-1-6-have-been-released/

Gaprindashvili backport details:
$ git log -1
commit 28a581bfb463e4bc3039e76ec043ade8b77ae033
Author: Jason Frey<EMAIL_ADDRESS>Date:   Wed Nov 28 13:47:12 2018 -0500

    Merge pull request #18238 from juliancheal/update_rails_patch

    Updating Rails patch version to <IP_ADDRESS>

    (cherry picked from commit c4757b96fcd5a94a0cd279c361a413966fce9d82)


Inconsistency importing "GLOBAL" library using "WITH NAME" with and without args

I'm seeing an inconsistency when importing libraries:

When importing a library with "ROBOT_LIBRARY_SCOPE" set to "GLOBAL" and using different "WITH NAME" values, I'm seeing only one instance when executing tests in Robot Framework.
When importing a different "GLOBAL" library but specifying arguments using different "WITH NAME" values, I'm seeing two instances when executing tests.

For replicating I have three files:
Files: robot_libimport.tar.gz
LibImport.py:
import logging

class LibImport(object):
    ROBOT_LIBRARY_SCOPE='GLOBAL'

    def __init__(self):
        self._name = None

    def set_name(self, value):
        self._name = value

    def log_name(self):
        logger = logging.getLogger(__name__)
        logger.info("name=%s", self._name)

LibImport2.py:
import logging

class LibImport2(object):
    ROBOT_LIBRARY_SCOPE='GLOBAL'

    def __init__(self, name):
        self._name = name

    def set_name(self, name):
        self._name = name

    def log_name(self):
        logger = logging.getLogger(__name__)
        logger.info("name=%s", self._name)

test.robot:
*** Settings ***
LIBRARY    ./LibImport.py    WITH NAME    libimport_1
LIBRARY    ./LibImport.py    WITH NAME    libimport_2
LIBRARY    ./LibImport2.py    value_1    WITH NAME    libimport2_1
LIBRARY    ./LibImport2.py    value_2    WITH NAME    libimport2_2

*** Test Cases ***
Incremenent And Log Count For LibImport.py
    libimport_1.Set Name    libimport_1
    libimport_2.Set Name    libimport_2

    libimport_1.Log Name
    libimport_2.Log Name

Incremenent And Log Count For LibImport2.py
    libimport2_1.Set Name    libimport_1
    libimport2_2.Set Name    libimport_2

    libimport2_1.Log Name
    libimport2_2.Log Name

To replicate I'm just running this:
robot -L trace test.robot
What I'm seeing is that the log keyword for LibImport.py will show "libimport_2" for both instances, while the ones for LibImport2.py will show "libimport_1", and "libimport_2" for the respective instances.
I took a quick look, and this seems happening when setting the import cache but I haven't had time to really test that theory.
For this case, I was actually hoping the library using LibImport2.py was the expected behavior. I was planning that as a workaround for the current framework I have. My main concern is using that workaround and watching everything break if I upgrade 😄.

I don't remember the details without looking at the code, but I'm fairly certain this behavior is by design. When you have a library that has a global scope, Robot avoids creating new instances, but when you take it into use with different arguments, that's just not possible.

This is to some extend related to #2106. The design can be reconsidered but definitely not in RF 3.1.

Nothing will be done for this in the near future and we already have related #2106. I think this can be closed.


[Proposal] Criteria for Preview Feature & Experimental/Alpha API stable designation

/area docs
This proposal intends to formalize under which circumstances Preview features and Experimental / Alpha APIs may graduate to stable (or default) features.
Proposed Criteria

SDK support in Go, Python, Java, JavaScript, .NET [if new API or API change]
Partner with other SDK maintainers to create implementation plan [if new API or API change]
Must support HTTP and gRPC [if new API or API change]
One community sponsor other than the organization authoring the feature adopts the feature and offers endorsement

Create a GitHub issue seeking community feedback and ask for official community sponsor who endorses the feature for stable designation.

No open P1 bugs against feature
End to End (E2E) tests must exercise the new feature

Criteria for removing preview / alpha feature or API

After a preview feature / alpha feature has not graduated to stable for 4 releases a GitHub issue proposal can be raised to remove a preview feature / Alpha API
The proposal should be available for public comment for a period of 2 months
The Steering community reviews the public comments and makes a formal decision on feature removal

Additional thoughts:
When an experimental API / Alpha API is made stable for a period of 1 release alias the API to be available under the preview name and the new stable name.
When a preview feature graduates to stable it is enabled by default. Offer a way to optionally disable the feature for a limited period of time.

@berndverst overall this looks good! A piece of feedback and suggestion before the STC meeting today is to remove the following:

SDK support in Go, Python, Java, JavaScript, .NET [if new API or API change]

We should not tie runtime feature maturity to SDKs. Making sure that an API has both HTTP and gRPC is enough.
Removing features
Out of the 3 bullet points, only the first is a criteria item that talks about the why and not the how, and I suggest we remove or update it to something else.
It's much more likely that a feature will be used by possibly many users but not documented or tracked anywhere, (because tracking Dapr usage in general is near impossible, and tracking usage of specific features is straight out impossible :) ). In that case, suggesting to remove a feature based on it not advancing in time (which can happen due to a myriad of reasons unrelated to the actual maturity) carries a risk of deprecation chaos and breaking users production systems.

The question I have on the criteria is defining what constitutes a feature. Clearly new APIs are, but then there is a blurry line on adding new capabilities to existing features. Actor reentrancy is an example. This makes all new features always start in preview.

@msfussell this issue refers to Preview Features as they are defined in code today and Alpha APIs. Whether something should be added as a Preview Feature or Alpha API isn't intended to be the focus of this issue.

@artursouza this is a reminder to modify the proposal based on the STC discussion. Thanks in advance!

This is the updated proposal based on the feedback from the STC.
Updated Criteria for stable feature or new API

~SDK support in Go, Python, Java, JavaScript, .NET [if new API or API change]~
Partner with ~other~ SDK maintainers to create implementation plan [if new API or API change]
Must support HTTP and gRPC [if new API or API change]
~One community sponsor other than the organization authoring the feature adopts the feature and offers endorsement~

~Create a GitHub issue seeking community feedback and ask for official community sponsor who endorses the feature for stable designation.~

No open P1 bugs against feature
End to End (E2E) tests must exercise the new feature
Performance test to exercise feature
If a preview feature or alpha API is not stable after 4 releases, the work must be prioritized by maintainers

~Criteria for removing preview / alpha feature or API~

~After a preview feature / alpha feature has not graduated to stable for 4 releases a GitHub issue proposal can be raised to remove a preview feature / Alpha API~
~The proposal should be available for public comment for a period of 2 months~
~The Steering community reviews the public comments and makes a formal decision on feature removal~


Recursion Exercises: Add new factorial exercise

Because

We want to bring the recursion exercises done in the recursion lesson in house.
Link the curriculum issue for this: https://github.com/TheOdinProject/curriculum/issues/27265#issuecomment-2011689860
This PR

Adds new exercise for calculating a factorial with recursion.

Issue

Closes #XXXXX
Additional Information

Leaving this as a draft for the time being. The main question I'd have is: are we okay with this organization / structure, or do we want to approach this differently?
Currently all the exercises in this repo are for "basic ruby." It might make sense to create an entirely new repo for these new exercises, which is the same way we do the custom enumerables project.
If we do leave them in this repo, is the way I have them organized here okay? Definitely interested in other maintainer input on the approach here.
Pull Request Requirements

[x] I have thoroughly read and understand The Odin Project Contributing Guide
[x] The title of this PR follows the location of change: brief description of change format, e.g. Data types exercise: Update spec files
[x] The Because section summarizes the reason for this PR
[x] The This PR section has a bullet point list describing the changes in this PR
[ ] If this PR includes changes that needs to be updated on the solutions branch, I have created another PR (and linked it to this PR).

After discussing with the maintainer team, we agreed to go ahead with this organization, so I've opened this up for review.


Add gcs and bypass cache args to datastore cli

I also gave the role Service Usage Consumer to the<EMAIL_ADDRESS>group so we can all use the GCS cache.

I gave<EMAIL_ADDRESS>the Service Usage Consumer role.


KAFKA-16684: fix flaky DedicatedMirrorIntegrationTest

Context
from DistributedHerder, the comment

Similar to handling HTTP requests, config changes which are observed asynchronously by polling the config log are
batched for handling in the work thread.

Thus, when there is a rebalance, the herder would throw an error RebalanceNeededException (in DistributedHerder, L2309). I think this should be an retryable exception since it's possible and we should wait for a while and try again.
Jira: https://issues.apache.org/jira/browse/KAFKA-16684
Test
run ./gradlew clean connect:test --tests DedicatedMirrorIntegrationTest and passed
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@C0urante thanks for the review!
Just updated it.

CI has passed on at least one node and the changes are trivial; merging...


chore: split package size workflow to make it work for PRs from forks

This enables the package-size to work also from forks. Currently
it does not work because the workflow gets only a readonly token
if started from a fork, hence the workflow cannot post the comment.
https://github.com/netlify/cli/runs/7194403058?check_suite_focus=true#step:6:27
By splitting the workflow, we run the calculation in a secure environment with
only the readonly token and then run the second workflow after the first
one is finished. The second workflow then has write access and can
post the comment
taken from https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
This upload of a workflow artifact will not count against the storage limit of the netlify github-account, because this is a public repository. https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions#about-billing-for-github-actions
There is no way to test this in a PR: 🤞

Note: This event will only trigger a workflow run if the workflow file is on the default branch.

https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_run

Nice idea!

Sorry I now also added a retention of the artifacts for 7 days.


Minimap

The minimap is now available using the hotkey forward slash /.
The border has been updated a bit since v1 to soften its edges.

Its operation is nearly the same as the old one- except that on pan, the viewfield doesn't update.

Its operation is nearly the same as the old one- except that on pan, the viewfield doesn't update.

I'd like to reopen this because I think having the viewfield rectangle stay fixed while the imagery moves under it is a pretty important feature - this allows the user to actually use the minimap to focus on some part of the map.

[ ] fix viewfield rectange

minimap v1

minimap v2 beta

Also noticing some minor visual issues:

[ ] Locator overlay texture disappears sometimes?  It might be the code that removes locator overlay when map is loaded (this is a thing that should happen on the main map only)
[ ] Actually we should probably scale down all the textures used?  This was an issue with the old map too.  Basically - we are displaying the overlay images that are designed for a normal sized map.  This image shows kind of what I mean:

I'd like to reopen this because I think having the viewfield rectangle stay fixed while the imagery moves under it is a pretty important feature - this allows the user to actually use the minimap to focus on some part of the map.

I fixed this viewfield issue sometime around  3cbb638e3

Actually we should probably scale down all the textures used?  This was an issue with the old map too.  Basically - we are displaying the overlay images that are designed for a normal sized map.

Fixed this in 061854d9d by just.. always rounding up to the next integer zoom instead of rounding to nearest.  This results in always fetching slightly sharper images than we need, rather than sometimes displaying blurry images. We'll see how this performs.


Multiple code improvements - squid:S1118, squid:S106

This pull request is focused on resolving occurrences of Sonar rules
squid:S1118 - Utility classes should not have public constructors.
squid:S106 - Standard outputs should not be used directly to log
anything.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S1118
https://dev.eclipse.org/sonar/rules/show/squid:S106
Please let me know if you have any questions.
George Kankava

Changes Unknown when pulling 05bcfb32fd175675746bbe9836891d99b37d0e77 on DevFactory:release/multiple-code-improvements-fix-1 into ** on universal-automata:master**.

Changes Unknown when pulling 23bcd8ef6cf8cc4a63ab948bfbda4f5d776d49fb on DevFactory:release/multiple-code-improvements-fix-1 into ** on universal-automata:master**.

Changes Unknown when pulling fc7d8ae3299ebac0e55124ab39a7038466487019 on DevFactory:release/multiple-code-improvements-fix-1 into ** on universal-automata:master**.


Public IP fallback for awless ssh --private

I normally use private IP addresses to connect by ssh to EC2 instances, but, in some cases, the instances are only reachable using their public IP, so, to avoid trying at the first time with the private address, and, if it fails, with the public one, an useful feature will be add another flag to delegate this work to awless.

@edubxb I guess the use case presented could be generalized as fallbacking on the other IP (public or private) when one does not work. And indeed we do not support that yet.
I have a few remarks though:

we would have to inspect the error to know it is an IP failure. Inspection would be a bit fiddly as there can be many errors originating a connection failure.
in most cases when connecting through a private IP you have to do it knowingly (using --private flag) meaning the machine is setup to not be accessed publicly, so there would little chance of such machines having an public IP
awless ssh provides many fallbacks when resolving/finding the SSH key and user. It also provides clear output messages with guesses on what should be done next.
not your case but generalizing: falling back on a private IP address (if we detect the public one does not work) make the assumption that the user has setup a dedicated tunneling (VPN, etc ...) to connect directly to private IPs

I might not have understood your DevOps scenario well enough, so do not hesitate to clarify your setup.

Yes @simcap, the use case could be from private to public, or vice versa, but in my case, is the first, let me explain my current scenario...
I work with several AWS accounts, some of then are for production and others for development or staging purposes. VPC of some accounts are reachable from our local networks through [Direct Connect] (https://aws.amazon.com/es/ Directconnect /). Due I'm a little lazy, when I need to connect to an EC2 instance, I do not want to remember if the instance belongs to an VPC reachable by our private network or not. This is the reason I suggested this feature.
In some cases, the instances do not have a public IP, so awless could inspect the instance properties to find it, and if doesn't have one (not sure if awless already do this currently), use the private address instead, regardless the flag used or the default behavior.
Another situation could be an instance with public IP, but not reachable using it by SSH, because the admin tasks are done with the private one.
Please, let me know if you need more information about it.

Ok, thanks.
In order to implement that (fall back on public) we will have to better type and identify our errors returned by the code from awless ssh. The idea is to know for sure what was the failure about: wrong username, key issue, host issue. This is not the case right now.
Once we have that we will be able to implement cleanly such scenarios. Do not know when though.
P.S: in the meantime, there might be a way to have the behavior by combining some bash functions + awless, though I have not had the time to look into it yet

Yes, some script magic can help, something like:
function aws-ssh {
  awless ssh --private "$@" || awless ssh "$@"
}

This bash script seems to be sufficient for this problem.


[FEATURE] Improve collection card

🎇 Description
We could put some effects on hover and create some ctas on cards in collections, what do you think?
🖼 Screenshots

Sure, please go ahead! 🤩

could you please accept my pr


Can't send notification when run release

Works normally when running debug on android and ios

**

**

same here, but look like can't send register request from app to my servers


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit 5322df4:
:clock10: Pending: waiting for processors (23 builds ahead of you)
:warning: Docs Build is busy, currently there are 23 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 5322df4:
:clock10: Full build: the average full build time is 7 min(s) 18 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 5322df4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


ghost icon only buttons in the Header Panels, coloring?

What's the best way to color a small ghost icon-only button in a Header Utilities panel? Right now the icons show by default in the dark text color, meaning that they are hidden in the panel.

I would recommend :global() modifier for this use case that targets SVG elements with a "data-carbon-icon" data selector. This way, a custom fill color will not affect non-Carbon SVG elements.
<script>
  import Add16 from 'carbon-icons-svelte/lib/Add16';
</script>

<style>
  :global(svg[data-carbon-icon]) {
    fill: blue;
  }
</style>

<Add16 />

Svelte REPL

Note: You may need increase the specificity if you just want to target icons in the Header Utilities panel:
<style>
:global(.${header-panel-common-ancestor} svg[data-carbon-icon]) {
    fill: blue;
}
</style>

This is one of the reasons why carbon-icons-svelte ships with a [data-carbon-icon] utility selector.

Thanks for this! I was able to get this working.


Dates are not advancing

Love your plugin, very easy to configure with short code.
Unfortunately the date does not advance automatically my two sites are stuck on the date from when I  reinstalled the plugin.
assumptiongranger.org - is one of the sites.
I am running cron job through c-panel and disabled WP cron in wp-config.php - Is it possible that is the problem?
Thanks,
Shannon

Same here...

wpc open weather is a good alternative, I just changed...

FYI -- This is probably a WordPress transients issue.  I had the same problem where the date was stuck in October, and deleting the transients fixed the problem. Not sure what causes transients to get stuck, but I've seen it on a few sites now.

This is fixed in #47 - the issue was likely using Personal Weather Station data, which is not reliable.


Update audio-conferencing-on-network.md

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/5753
Added note.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@CarolynRowe PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Row index column can't work as expected if no data column been selected

Bug description
below spark sql query would return wrong results of row index columns
case 1: only select _metadata.row_index without data column
select _metadata.row_index from t;

result is :
Array([2266956753800648], [2266965343735242], [2266973933669836], [2266982523604430], [2882706183611875585], [-5182228451473484542], [2018341187252983046], [1514921414753372181], [114547136799965192], [2306126442695491587], [2449958210728099843], [2594073398837510147], ...

The issue due to current row index generator logic depends on columnReader and needs at least one data column been selected.
Checking here
https://github.com/facebookincubator/velox/blob/abaf323d907334fbfe35353893d081eacc46561b/velox/dwio/common/Reader.cpp#L207C1-L212C4
if no data column been selected, the rowOffsets.size would always 0 , and causes wrong result
System information
ubuntu 22.04
Relevant logs
No response

@Yuhta FYI

@Yuhta  the above fix PR only cover case only row index column been selected but not case if row index and const data column been project
could you help review PR https://github.com/facebookincubator/velox/pull/10012 which address the case project with only const data column


[HAMMER] Users without groups should use admin retirement

Backport of https://github.com/ManageIQ/manageiq/pull/19309 which adds group check to system context for retirement
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1754043
@miq-bot assign @simaishi

@lfu please review

@lfu @tinaafitz is this good to go?

@tinaafitz @lfu Satoe's waiting for this, please put it out of its misery

hey @lfu it's failing because you made me change it to responds to.
https://travis-ci.org/ManageIQ/manageiq/builds/588520854#L1045

can I please put it back to how it was?

hey @simaishi do you need a second approver on this?


Installation error: cannot open file 'gdi32.lib'

I'm trying to install better sqlite, but for some reason i keep on having the same issue.
LINK : fatal error LNK1104: cannot open file 'gdi32.lib' [C:\Users\Admin\Desktop\Projects\Discord Bot\node_modules\better-sqlite3\build\better_sq lite3.vcxproj]   test_extension.c   win_delay_load_hook.cc LINK : fatal error LNK1104: cannot open file 'gdi32.lib' [C:\Users\Admin\Desktop\Projects\Discord Bot\node_modules\better-sqlite3\build\test_exte nsion.vcxproj] gyp ERR! build error  gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\14.0\bin\MSBuild.exefailed with exit code: 1 gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:194:23) gyp ERR! stack     at ChildProcess.emit (events.js:310:20) gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12) gyp ERR! System Windows_NT 10.0.18363 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--release" gyp ERR! cwd C:\Users\Admin\Desktop\Projects\Discord Bot\node_modules\better-sqlite3 gyp ERR! node -v v12.16.2 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok  npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR<EMAIL_ADDRESS>build-release:node-gyp rebuild --release`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build-release script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR!      C:\Users\Admin\AppData\Roaming\npm-cache_logs\2020-08-13T12_42_32_731Z-debug.log
npm WARN<EMAIL_ADDRESS>requires a peer of erlpack@hammerandchisel/erlpack#master but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>No repository field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: prebuild-install || npm run build-release
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.`
Thats the error message i get and have been stuck with for quite some time now.

There seems to be a lot of issue installing on windows lately, the developer could fix these by providing prebuilt binaries for windows, like he does for linux

The same problem occurs in mac (catalina), too.

The same problem with me, but i do npm rebuild or rm -rf node_modules && npm install that's work!

Has anyone tried the solution presented by @hansputera ?

my friends 😅

Has anyone tried the solution presented by @hansputera ?

I tried it on macOS, none of works.
❯ npm install better-sqlite3

(node:30718) ExperimentalWarning: The fs.promises API is experimental
npm ERR! code 1
npm ERR! path .../node_modules/better-sqlite3
npm ERR! command failed
npm ERR! command sh -c prebuild-install || npm run build-release
npm ERR! ><EMAIL_ADDRESS>build-release
npm ERR! > node-gyp rebuild --release
npm ERR! (node:30748) ExperimentalWarning: The fs.promises API is experimental
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using<EMAIL_ADDRESS>npm ERR! gyp info using<EMAIL_ADDRESS>| darwin | x64
npm ERR! gyp info spawn /usr/bin/python2
npm ERR! gyp info spawn args [ '.../node_modules/node-gyp/gyp/gyp_main.py',

❯ node --version
v10.15.1

MacOS:

Install XCode
Once XCode is installed, go to Preferences, Downloads, and install the Command Line Tools.

Windows:

npm i -g --add-python-to-path --vs2015 --production windows-build-tools
npm i -g node-gyp@latest

Linux:

sudo apt-get install build-essential

Source: https://enmap.evie.dev/install#pre-requisites

Has anyone tried the solution presented by @hansputera ?

I have not. I dont have a mac and I plain refuse to install anything Visual Studio on my machines (if some software bundles it then sure I guess, but I don't like it)

Has anyone tried the solution presented by @hansputera ?

I just tried it (the vs2015 part), and can confirm it works, though I'd like to point out that if your using nvm with custom paths, you may have to move some files yourself

I just try to downgrade the node version to v12, and it works.

I tried with node version v15 and v14 won't work.

Closing due to inactivity


Commit Message in the "Source Control" message input box should retain after closing the VSCode

Commit Message in the "Source Control" message input box should retain after closing the VSCode.
By this way, we can add changelog when developing in process

Duplicate of #41232


How to format table head cell individually (cells with labels)?

Hey everyone,
Using mui-datatables 2.0.0-beta.59 and I'm wondering: is there a way to format the table head cells individually (the label cells)?
Use case: I want to left-align the content of certain columns and right-align others. I can do that because I can display JSX in the table cells. But then the column title is out of alignment with the content.
I can only specify column labels as text. If I use JSX as a label, the app crashes if I click on the table head cell (might have to do something with the sorting arrow being added at that time).
Any solution? Thanks!

Check out the customize-columns example here: https://github.com/gregnb/mui-datatables/blob/master/examples/customize-columns/index.js.
You can use customHeadRender to specify how each column header renders, like
customHeadRender: (columnMeta, updateDirection) => (
   updateDirection(2)} style={{ cursor: 'pointer' }}>
    {columnMeta.name}

)

Thanks @gabrielliwerant
That does change how the cell is rendered. But some functionality is lost (arrow showing sort direction doesn't appear).

Correct, if you choose to customize it, you will have to provide your own icons and transition behavior, but if you look under the hood at how it's implemented in the library, it may give you some ideas.

Turns out it was really easy to do:
customHeadRender: (o, updateDirection) => {
    return  updateDirection(o.index)} style={{fontWeight: 400, cursor: "pointer"}}>
        {o.label}
        <TableSortLabel active={o.sortDirection !== null} direction={o.sortDirection || ""}/>
    	;
}

@dandrei Thanks. I really need this.


Add the internal _feature_version to compile()

close #456

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.44%. Comparing base (c31bd9b) to head (1f58e29).
Report is 1 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##            master     #458      +/-   ##
===========================================
- Coverage   100.00%   98.44%   -1.56%
===========================================
  Files           21       21
  Lines         2308     2308
===========================================
- Hits          2308     2272      -36
- Misses           0       36      +36

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fixed order of names AB#13657

closed because this will be released as a hotfix on latest release branch


Forecast for 2024-03-03

@MayaSal sorry for the inconvenience. I updated .github/workflows/validate-submission.yaml and .github/workflows/after-validate-submission.yaml to resolve the issue how to use a token.  Could you merge them in your MayaSal:add-UGA_flucast-INFLAenza?

Do I need to resubmit the file once updating things on my end?

@MayaSal No need to resubmit, but could you include the file and recommit on the branch you made? (please update this PR)


Ensure Point2 is generated properly by SDK

When choosing RoME.Point2 as the VariableType in SDK, the cloud cannot support it for some reason.
The following error occurs: BoundsError([6.94616648028127e-310, 2.121995791e-314], [1, 2, 3]
To reproduce:

Change type from RoME.Pose2 to RoME.Point2 in testVariable.jl
Start local cloud via npm start in cloud-system root
Change apiUrl to http://localhost:4343
Run julia --project=. ./test/integration/runtests.jl

Resolve in https://github.com/NavAbility/NavAbilitySDK.jl/pull/73


Multi speaker training？

Does Multi speaker training will be supported in future?

We will consider training multi-speaker when we have the time and computional resources. Thank you for your interest!


Dependency versioning

Now that nipype 0.13.1 is out, it might be time to revisit our dependency pinning pattern. We've been simply pinning commits, which obviously is fine for development, but we saw in #540 that this strategy can cause issues for users running natively because pip doesn't install the versions pinned in requirements.txt.
Since we can release niworkflows as often as we like, I think we should plan to make a release prior to any fmriprep/mriqc release, so that we can depend on that in the app releases.
Nipype is more complicated. We're already starting to depend on post-0.13.1 PRs, so we can't simply pin to 0.13.1 and compensate for any changes in niworkflows and fmriprep until another nipype release. (My understanding is Satra doesn't intend to push another release until 1.0.) We could try to persuade Satra to have a short (e.g. 2-week or 1-month) release cycle just to get the ENH/FIX PRs into something we can depend on with pip.
Or perhaps we could push to move nipype to versioneer-like strings which allow us to say "more recent than this version". We'd still need to be able to persuade pip to automatically install something if the current version doesn't satisfy...
Any thoughts?

+1 . For mriqc 0.9.5 I waited for the release of niworkflows and didn't want to include anything beyond nipype 0.13.1.
For next 0.9.6 (due by the end of this week) I was planning not to stay with the latest release of niworkflows and start a submodule with nipype-specific stuff until those items get included in an official release of nipype.
This is a short-term solution that might work for small iterations like mriqc-0.9.6 but doubtfully sustainable in the long term.
On the other hand, it seems that trying to release nipype more often did not work in the past. So a versioneer-like scheme might be a good compromise solution.
Overall you are right, this is currently an outstanding problem. And I can't think of solutions other than those you enumerated.

Let's revisit our goals:

Keep as much as we can in nipype master so others can benefit.
Make installation possible for the few that cannot use Docker/singularity.

I wonder if we shouldn't just ship a pinned version of nipype master with niworkflows (import niworkflows.nipype as nipype). This might be easy to achieve using git submodules. WDYT?

That sounds reasonable to me on first read. Can we foresee any downsides?


Importing characters issues

importing character from maintstream did not like the current setup lol

You can also sometimes see a similar problem, when first logging into the server, players sometimes have a standard human character.

Maybe wizden issue!

huh, upstream moment?

huh, upstream moment?

idk


Export TokenIssuer so that it may be used by non-native auth providers

I am working on a custom auth provider which needs to be able to issue tokens. TokenIssuer in plugin-auth-backend was not yet exported, though.

Sorry, had to force push a few times to clean up some things, as it's my first contrib :)


Hectic hover updating after reload on "..." menu

Here I hover over the "..." of the extensions viewlet.

Will be fixed when adopting the new hover service API setupDelayedHoverAtMouse with lifecycleOptions.groupId


Empty File in Data Lake Bucket

Thank you for publishing this work. I created the stack and loaded files to the S3 bucket as you had instructed but I see one and only one empty file (0 bytes) named "hit-data_$folder$" in the data lake bucket. Crawler does not find any tables and therefore I cannot query the data.
Can you please check the Python file load-data.py?

I had selected more than the October 2016 columns. I selected October 2016 columns from the Adobe Analytics portal and it resolved the issue.

So it's all working now?  You're probably the first person other than me to really try this solution.  Hopefully I didn't make any mistakes in it...

@chriskl  It's solid work. I was so happy when I found your repo. I just corrected a few typos that I will send over to you in a pull request.
Another question, what did you do about the lookup tables and resolving things like country codes? For example, country code 300 is U.S. commercial but in the output parquet files it is just 300. Do you suggest replacing the lookup codes with actual values in the final table?

Hi John,
I never got around to processing the lookup data.  That would be an
exercise for the reader :)
There's an example of processing it here:
https://aws.amazon.com/blogs/big-data/closing-the-customer-journey-loop-with-amazon-redshift-at-equinox-fitness-clubs/
In that case it uses the metadata to get column names...but you can't get
types.
We could process the lookup files and substitute in new columns into the
parquet files perhaps, or just set up a new table each hour with the lookup
data.  Unfortunately the lookup data is a zipped set, which makes it even
harder to process. And I'm no gun Spark or Python coder :(
Here's a bounty I put on StackExchange:
https://stackoverflow.com/questions/55272228/how-to-prevent-processing-files-twice-with-spark-dataframes
Other references:

https://github.com/awslabs/athena-adobe-datafeed-splitter

http://datafeedtoolbox.com/how-to-setup-a-data-lake-and-start-making-sql-queries-with-adobe-analytics-aws-s3-and-athena/
Good luck :) . Please submit cool stuff back :) . I might be doing one of
these for Braze soon too.
Chris
On Sun, 9 Jun 2019 at 02:44, John Shojaei<EMAIL_ADDRESS>wrote:

@chriskl https://github.com/chriskl It's solid work. I was so happy
when I found your repo. I just corrected a few typos that I will send over
to you in a pull request.
Another question, what did you do about the lookup tables and resolving
things like country codes? For example, country code 300 is U.S. commercial
but in the output parquet files it is just 300. Do you suggest replacing
the lookup codes with actual values in the final table?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HealthEngineAU/adobe-analytics-data-lake/issues/1?email_source=notifications&email_token=AAMIH67KAF3IB4GCQ4LSK23PZP4ZXA5CNFSM4HV3DMOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXH3AOA#issuecomment-500150328,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMIH67C4WESKQAUCJ4MAQTPZP4ZXANCNFSM4HV3DMOA
.


We need to choose a name!

Although we want to make something super modular, we need an overarching name for this project that doesn't clash with, like, everything (https://www.thedatalab.com, https://cloud.google.com/datalab/docs/, https://datalab.apache.org, http://www.thedatalab.org, https://pypi.org/project/datalab/).
I quite liked "alembic" at one point, though it turns out that almost all alchemical equipment names are taken by SQLAlchemy and related spin-offs...
Rubbish suggestions:

something Grey related: greyta/greyter/> for short ("Grey"-ting your data into smaller blocks ;))
something big/map related to tie into BIG-MAP (tempting fate)
something better/more general

gyr

dlab -- only clashes with some US military thing and the name of a chinese company, someone is squatting on it with an empty v<IP_ADDRESS> package on PyPI that we could probably takeover

I think we can finally say that this ship has sailed... datalab has endured, but we can still have lots of fun trying to name specific plugins and offshoots.


add Delete and Purge (delete before) id links to UI

This resolves #3  for me

@ambled Thank you!! Merged and released!!


Add optional attributes to SDK samplers

Is your feature request related to a problem? Please describe.
According to the spec, the sampling result consist of decision, attributes and trace state. However, the current samplers in the SDK are all accepting only decision data such as ratio, but are not able to return attributes
Describe the solution you'd like
I suggest adding optional parameter attributes to the constructor of each sampler. these attributes will be returned in the SamplingResult when called.
Creating the sampler will look like this:
const sampler = new AlwaysOnSampler({attributeName: 'attribute value'});

Describe alternatives you've considered
Adding an AttributeSampler that accepts another sampler and then invokes it and merges the configured attributes into the sampling result.
It might look like this:
const sampler = new AttributeSampler(new AlwaysOnSampler(), {attributeName: 'attribute value'});

Pros: it will be useable for any sampler, not just those of the SDK
Cons: setup is more complicated and a little less efficient
Additional context
Posting it here in the hope that someone might find it interesting to pick up. It's a non-breaking change feature that I think is straightforward to implement.

New attributes returned by a sampler are already supported by the SDK: https://github.com/open-telemetry/opentelemetry-js/blob/main/packages/opentelemetry-sdk-trace-base/src/Tracer.ts#L125.
IMHO, AlwaysOnSampler is defined by the spec https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#alwayson and adding any features need a normative change on the spec. Significant public interfaces provided by the SDK like mentioned "AttributeSampler" need to be introduced with the spec too. I'd suggest raising an issue at the spec repo https://github.com/open-telemetry/opentelemetry-specification.

New attributes returned by a sampler are already supported by the SDK

Yes, I use them with my custom samplers. SDK covers the setting of the attributes returned from the sampler, but there is currently no support for it in any of the existing SDK samplers. If the user wants to add attributes, he has to implement his own sampler.

IMHO, AlwaysOnSampler is defined by the spec https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#alwayson and adding any features need a normative change on the spec.

The spec talks about the returned decision, but it says nothing about attributes. Since it's an optional extended configuration, I think it does not violate the spec to return attributes as well if user need to, but I'll open an issue in the spec repo as well to discuss it.

opened an issue for that in spec:
https://github.com/open-telemetry/opentelemetry-specification/issues/2198

Note: Added waiting-for-spec label and removed up-for-grabs so that we don't confuse newcomers that this is ready to work on.

You would like the sampler to apply a constant value to the attribute? If so, a span processor like ConstantAttributeProcessor might be more appropriate? Unless there is something sampler-specific about the attributes you're looking at. I think the feature in the spec is to allow sampling-relevant attributes to be added (like b3's sample debug flag or similar)

You would like the sampler to apply a constant value to the attribute? If so, a span processor like ConstantAttributeProcessor might be more appropriate? Unless there is something sampler-specific about the attributes you're looking at. I think the feature in the spec is to allow sampling-relevant attributes to be added (like b3's sample debug flag or similar)

I would like to enhance the spans with data about sampling decisions.
For example:
    this.sampler = new TraceIdRatioBasedSampler(samplingConfig.ratio, {
      "sampling.initialized": true,
      "sampling.config.id": samplingConfig.id,
      "sampling.ratio": samplingConfig.ratio,
    });

In the example above, I want to enrich only the root span for the trace (the one used for sampling) with information that can later help with debugging sampling issues. These can include config rule id in use and if config was available during span creation (fetching the config is async process and spans can be created before we have the config).

@blumamir do you no longer want/need this?


Search configuration for unicode folding and partial matching

Changes for #363 #316

Adds unicode folding to general text solr field and adds a new ngram filter token field type and dynamic field.
Uses copy fields on person name and sort name to generate text and ngram versions
Configures name search to use the new fields, but boosts primary name fields higher
Updates alpha page label logic to compare case-insensitively to avoid discrepancies between the solr sorting and the display (note: we may want to revise the logic to ignore whitespace + punctuation at some point)
Add directions to deploy notes about solr config change and indexing
Unrelated to these features, while I was updating the alpha page labels I modified the solr query to get all page labels in a single query instead of getting them individually as we'd been doing previously. This should result in a performance improvement on the members list page.

Note: when I was working on this I had to unload and reload my solr core multiple times. I don't think that should be necessary, and hope it's something to do with the tweaks I had to make as I refined the configuration. We might need to clear people from the index first (manage.py -c person -i none) before indexing.

All of the changes needed from this PR have now been handled in separate branches or updates to develop (with actual passing builds).


Inline delimiter parser can not be registered more than once, delimiter character: ~

Trying to implement a separate extension for subscript like H~2~0, but I can't use tilde in conjunction with the existing ext-gfm-strikethrough extension, as they clash on parser registration.  A workaround seems to be create a new extension that bundles both, something like ext-subscript-and-gfm-strikethrough that works similar to the EmphasisDelimiterProcessor. This is somewhat ugly, but perhaps reasonable since this should be a fairly rare occasion.
Thoughts?

I'm not sure if it's a good idea to implement this as a delimiter processor. Have you looked at doing it in a post-processing step on Text nodes instead?
I'd also be very interested in how pandoc implemented this.

The current restriction on delimiter characters is rather aggressive. It should be possible to register the same delimiter multiple times if the minimum number of delimiter characters differs. I have implemented this in my patched ParserBuilder here https://github.com/szeiger/ornate/blob/b76669837bf8e4efca558fb8be535227c644dc2c/core/src/main/scala/com/novocode/ornate/commonmark/CustomParserBuilder.scala#L54-L127 for the same reason (using strikethrough together with my own subscript extension). Preliminary tests indicate that it works as intended.

@szeiger Interesting. Can you come up with a way to integrate that into InlineParserImpl? A pull request would be much appreciated :).


Latest Docker sample requires archive file

The latest changes now requires the archive file to have been built - This broke the desired behavior of skipping the archive if the user did not build it. Fix to desired behavior

Converted to Jira WDT-296


Feedback for “Cache – SWR”

Would you mind updating the docs when possible? https://swr.vercel.app/docs/advanced/cache (great library btw...)

@sergiofdez4 What do you need in the docs?

On how to clear cache. clear method does not exist (v.1.3.0). We're looping through the cache object and deleting each key. We're not sure if it is the best approach though. Any feedback is appreciated.

Thank you! As the docs say, modifying the cache data directly is not a recommended way because it might cause unexpected behaviors.
In v2 (RC), there is a new feature to mutate multiple data, and it can be used as a way to clear cache data. We've added it in the v2 docs.
https://beta-swr.vercel.app/docs/advanced/cache#modify-the-cache-data


Additional checks on Marlin/Darlin proof and vk + utility function to compute proof size given free parameters

Closed and moved to https://github.com/HorizenOfficial/zendoo-cctp-lib/pull/19


miss spelled wdiget in battery_level.py line 49

In the the file battery_level.py,
in function update_battery_level
in line 49
following correction can be done: wdiget to widget.
wrong:
self.widget.tooltip["text"] = self.wdiget._["Access denied"]
correct:
self.widget.tooltip["text"] = self.widget._["Access denied"]
Thanks for the code, trying to learn bleak with tkinter.
My first activity here.

Thanks, I fixed it.


Comment # type: ignore stopped to work

Environment data

Pylance v2021.12.1
Language Server version: Pylance language server 2021.12.1 (pyright fcab8004)
OS and version: Windows 10 1809
Python version (& distribution if applicable, e.g. Anaconda): Python 3.8.9 from python.org

Expected behaviour

Open empty folder as project in VS Code
Create file notebook1.ipynb with the following content:

a = 5
print(5)

Create file notebook2.ipynb with the following content:

# cell [1]
%run "notebook1.ipynb"

# cell [2]
print(a)

Pylance will show that "a" is not defined. This is uncorrected, because we "imported" this variable via %run command.

Create new cell at the start of  notebook2.ipynb and type in it:

# type: ignore

Previously, this comment worked nice and helped me a lot. But now this don't work. I had to disable Pylance, because now it just gets in the way of my work.
Actual behaviour
me: # type: ignore
pylance: <ignoring my comment>
me: <disabling pylance>
vscode:

me:

Logs

click
[Info  - 21:04:46] Pylance language server 2021.12.1 (pyright fcab8004) starting
[Info  - 21:04:46] Server root directory: c:\Users\Sindzicat\.vscode\extensions\ms-python.vscode-pylance-2021.12.1\dist
[Info  - 21:04:46] No configuration file found.
[Info  - 21:04:46] No pyproject.toml file found.
[Info  - 21:04:46] Setting pythonPath for service "e": "d:\Temp\e\pyenv3.8.9-win64\python.exe"
[Warn  - 21:04:46] stubPath d:\Temp\e\typings is not a valid directory.
[Info  - 21:04:46] Assuming Python version 3.8
[Info  - 21:04:46] Assuming Python platform Windows
Search paths for d:\Temp\e
  c:\Users\Sindzicat\.vscode\extensions\ms-python.vscode-pylance-2021.12.1\dist\typeshed-fallback\stdlib
  d:\Temp\e
  d:\Temp\e\typings
  c:\Users\Sindzicat\.vscode\extensions\ms-python.vscode-pylance-2021.12.1\dist\typeshed-fallback\stubs\...
  c:\Users\Sindzicat\.vscode\extensions\ms-python.vscode-pylance-2021.12.1\dist\bundled\stubs
  [censured by user]
  c:\Users\Sindzicat\AppData\Roaming\Python\Python38\site-packages
  c:\Users\Sindzicat\AppData\Roaming\Python\Python38\site-packages\win32
  c:\Users\Sindzicat\AppData\Roaming\Python\Python38\site-packages\win32\lib
  c:\Users\Sindzicat\AppData\Roaming\Python\Python38\site-packages\pythonwin
  [censured by user]
[Info  - 21:04:46] Searching for source files
[Info  - 21:04:58] Found 20529 source files
[Info  - 21:04:58] Background analysis(1) root directory: c:\Users\Sindzicat\.vscode\extensions\ms-python.vscode-pylance-2021.12.1\dist
[Info  - 21:04:58] Background analysis(1) started
Background analysis message: setConfigOptions
Background analysis message: setImportResolver
Background analysis message: ensurePartialStubPackages
Background analysis message: setTrackedFiles
Background analysis message: markAllFilesDirty
Background analysis message: setFileOpened
Background analysis message: analyze
[BG(1)] analyzing: d:\Temp\e\notebook2.ipynb ...
[BG(1)]   parsing: d:\Temp\e\notebook2.ipynb (48ms)
[BG(1)]   parsing: c:\Users\Sindzicat\.vscode\extensions\ms-python.vscode-pylance-2021.12.1\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 6ms] (388ms)
[BG(1)]   binding: c:\Users\Sindzicat\.vscode\extensions\ms-python.vscode-pylance-2021.12.1\dist\typeshed-fallback\stdlib\builtins.pyi (133ms)
[BG(1)]   binding: d:\Temp\e\notebook2.ipynb (0ms)
[BG(1)]   checking: d:\Temp\e\notebook2.ipynb (3ms)
[BG(1)] analyzing: d:\Temp\e\notebook2.ipynb (576ms)
Background analysis message: resumeAnalysis

Code Snippet / Additional information

XXX

Maybe fixed in Pylance v2021.12.2-pre.1. At least # type: ignore works for me now...

Found a workaround. At the top of ipynb file type the following code in the first cell:
# pyright: reportUndefinedVariable=false

This helped me at least.

Thanks for the report. Will investigate this

looks like there is a hidden code at the top of cells that cause # type features to not work. probably will be fixed by Erik's new LSP notebook support.

@sindzicat, # type: ignore works for me in notebooks after opting into the notebooks experiment that we shipped in Pylance 2022.5.3.
Note that each cell is considered a separate document now, and therefore putting a # type: ignore at the top of a cell will only ignore errors in that one particular cell.
Give it a try:

Install the latest builds of the Python, Pylance, and Jupyter extensions.
Set "python.pylanceLspNotebooksEnabled": true
Reload VS Code.

We're closing this issue since it is fixed when python.pylanceLspNotebooksEnabled is set to true and as of Python extension version 2022.14.0 that is now the default.
If you are setting python.pylanceLspNotebooksEnabled to false, we would like to understand why. Please file an issue.


Hooks

Hey guys! How can i launch some .bat right before the server start? i didn't find some information about it

In the server manager config add a hook object to the hooks array like so:
...
"hooks": [
  {
    "type": "beforeStart",
    "program": "path/to/your/script.bat"
  }
],
....


Update simpleclient to 0.16.0

Updates io.prometheus:simpleclient from 0.8.1 to 0.16.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.prometheus", artifactId = "simpleclient" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "io.prometheus", artifactId = "simpleclient" }
}]

labels: library-update, early-semver-major, semver-spec-minor, commit-count:1

Coverage: 33.898% (-0.0%) from 33.898% when pulling db6be6dd81f2b4ac28bfbe0564013ad1041fcd29 on scala-steward:update/simpleclient-0.16.0 into d082b04ae38161e522ab7991a62ceff130832f4e on evolution-gaming:master.


Sent JWT token does not give back user in controller.

Hi,
I receive anonymous user when I try finding the user in controller via:
$user = $this->get('security.token_storage')->getToken()->getUser();
config.yml
lexik_jwt_authentication:
    private_key_path: '%kernel.root_dir%/../var/jwt/private.pem'
    public_key_path: '%kernel.root_dir%/../var/jwt/public.pem'
    pass_phrase: 'example'

security.yml
security:
    encoders:
        FOS\UserBundle\Model\UserInterface: bcrypt

    role_hierarchy:
        ROLE_ADMIN:       ROLE_USER
        ROLE_SUPER_ADMIN: ROLE_ADMIN

    providers:
        fos_userbundle:
            id: fos_user.user_provider.username_email

    firewalls:
        dev:
            pattern:  ^/(_(profiler|wdt)|css|images|js)/
            security: false

        login:
            pattern:  ^/
            stateless: true
            anonymous: true
            form_login:
                login_path: fos_user_security_login
                provider: fos_userbundle
                check_path: /login_check
                require_previous_session: false
                username_parameter: _username
                password_parameter: _password
                success_handler: lexik_jwt_authentication.handler.authentication_success
                failure_handler: lexik_jwt_authentication.handler.authentication_failure
            oauth:
                provider: fos_userbundle
                resource_owners:
                    facebook: facebook_login
                    google: google_login
                    linkedin: linkedin_login
                failure_path: app_login
                login_path: app_login
                oauth_user_provider:
                    service: app.provider.oauth
            logout:
                path:   fos_user_security_logout
                target: /

        register:
            pattern:  ^/register
            stateless: true
            anonymous: true

        api:
            pattern:  ^/api
            stateless: true
            anonymous: false
            provider: fos_userbundle
            guard:
                authenticators:
                    - app.jwt_token_authenticator
            lexik_jwt:
                authorization_header: # check token in Authorization Header
                    enabled: true
                    prefix:  Bearer

        refresh:
            pattern:  ^/api/token/refresh
            stateless: true
            anonymous: true

    access_control:
        - { path: ^/login$, role: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/login_check$, role: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/register, role: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/resetting, role: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/api/doc, role: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/api/token/refresh, roles: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/api/v1, role: IS_AUTHENTICATED_FULLY }
        - { path: ^/admin/, role: ROLE_ADMIN }

I have a question that when I send the jwt token in the Authorization header, I dont receive a preauthentication token in JWTTokenAuthenticator.php on line 100.
var_dump:
object(Lexik\Bundle\JWTAuthenticationBundle\Security\Authentication\Token\PreAuthenticationJWTUserToken)#569 (8) {
  ["rawToken":"Lexik\Bundle\JWTAuthenticationBundle\Security\Authentication\Token\PreAuthenticationJWTUserToken":private]=>
  string(835) "eyJhbGciOiJSUzI1NiJ9.eyJyb2xlcyI6WyJST0xFX1VTRVIiXSwidXNlcm5hbWUiOiJwcmFzaGFudC5iYWxhbkBob3RtYWlsLmNvbSIsImlhdCI6MTQ5ODYzNTc0NiwiZXhwIjoxNDk4NjM5MzQ2fQ.i4cjTLaurmNK_wgzjzRsRTHg4HdJR2q9A9bb_CVMETSBavMBQYRmG8DsWT15osqCDli1enaFMquVayTehyYX4aGez0TZtP_hB4U-S3Gxq7lslfzlFr6hDT_3lM3wRXKHiLTMvfwt-pnwfdUZdNB7TdU48NSGTRD8KWmeCjG9ifofPwBwxkKHElt4uA8_M78ksTMTsW4haKIZd_qSF6L0ubnhDWD8f7zZSw4E9rw_JYgbX0LsWedHkAB_9rjWHBAPfu-mw-BFrp8GA-2VyWr8ZbRDf3YTvIpRuqsAeYrXp52aFKxTUI9--tBkfVF1thP45a9y-0pIZ810tfFXZPRlKDK7dx8Jr9B16eT6c0Ea1fw4MC55qBvVFB2fO0bY-ylT3NiodQvYEGeO5VDybdahd1RBBvumRQmYCO4ZPaPe9tH2K46V82gP0t6dOZFipvJkaLWWRRZIiGgRRhvDWRfmne5pnnGiqjxMfPS1vC8cDGfmTIXxCuPJ1CgMhuytLIlr3seFaTG0qXzvr3VI8JF9tJ939T_d6mGDQpiQTjfu5uM2LZUKcWJB0pxTmM170gcG3WnmZ1L0gkqjeCZActtIg9TryYoonErF1atUi-w5rXtjw9q3uKXFLOAbZKZhZG0HqxnshcAkEy663Fo36q5CtpcM3gKkJ9bz26SKzhk8e84"
  ["payload":"Lexik\Bundle\JWTAuthenticationBundle\Security\Authentication\Token\PreAuthenticationJWTUserToken":private]=>
  NULL
  ["credentials":"Symfony\Component\Security\Guard\Token\PreAuthenticationGuardToken":private]=>
  NULL
  ["guardProviderKey":"Symfony\Component\Security\Guard\Token\PreAuthenticationGuardToken":private]=>
  NULL
  ["user":"Symfony\Component\Security\Core\Authentication\Token\AbstractToken":private]=>
  NULL
  ["roles":"Symfony\Component\Security\Core\Authentication\Token\AbstractToken":private]=>
  array(0) {
  }
  ["authenticated":"Symfony\Component\Security\Core\Authentication\Token\AbstractToken":private]=>
  bool(false)
  ["attributes":"Symfony\Component\Security\Core\Authentication\Token\AbstractToken":private]=>
  array(0) {
  }
}

I have a Security established exactly like the one in your Sandbox environment:
https://github.com/chalasr/lexik-jwt-authentication-sandbox/blob/master/src/AppBundle/Security/Guard/JWTAuthenticator.php
Do I need to make a change to my User entity?

Use the following two lines in my controller to fetch the user, if someone else has the same issue.
$preAuthToken = $this->jwtAuthenticator->getCredentials($request);
$response['user'] = $this->jwtManager->decode($preAuthToken);

I have created some  REST API  and tested it's working fine with jwt token on postman.
I need to call REST API through ajax so, how i can receive jwt  tokent to send with REST API.

I had the same problem (I mean, I don't know how to get the user from the current request inside a Service/Controller, when a JWT token is sent inside a Header/Get Parameter). After researching, I found this convenient solution:

Inject Symfony\Component\Security\Core\Authentication\Token\Storage\TokenStorageInterface (for example in an attribute tokenStorageInterface)
Inject Lexik\Bundle\JWTAuthenticationBundle\Services\JWTTokenManagerInterface (for example, in an attribute jwtManager)
Call decode in jwtManager, and getToken in tokenStorageInterface.

Constructor of the service/controller (steps 1,2)
public function __construct(TokenStorageInterface $tokenStorageInterface, JWTTokenManagerInterface $jwtManager)
    {
        $this->jwtManager = $jwtManager;
        $this->tokenStorageInterface = $tokenStorageInterface;
    }

How to get user info from JWT Token? (step 3)
$decodedJwtToken = $this->jwtManager->decode($this->tokenStorageInterface->getToken())

I hope this helps anybody that haven't found an exact solution to this question.

Hi, does anyone know, how to do that in tests with cli (without request)?

Found the answer here.
https://github.com/lexik/LexikJWTAuthenticationBundle/issues/292#issuecomment-269898218
Works for me!

@pbalan It gives me random user for the same token that I receive from frontend header's request. I could not reproduce this issue on local or dev. It is only happening on production. I think that it is because of a huge user (70K users) base on production. I tried this solution but not worked. I also tried to decode jwt that I receive in $_SERVER.  Which class do I need to inject to use the line $this->jwtAuthenticator->getCredentials($request); inside the controller?


feat(decorators): allow concrete type on JSONField

Note: needs tests.

Looks very nice! I assume with  @JSONField({ filter: true, nullable: true, gqlFieldType: EventObject }) the filtering based on the JSON fields will be added out-of-the box?

@dzhelezov that's right - I haven't changed anything of the JSON filtering behavior, just the data types in the generated schema

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


run name different from planet name?

this moight be the case!

oh this is already an option for run_simulation lol but apparently not for the input file

doooone!


[question] - Does now @model always create AmplifyDataStore tables?

Which Category is your question related to?
API
Amplify CLI Version
4.25.0
What AWS Services are you utilizing?
Amplify
AppSync
DynamoDB
Lambda
Provide additional details e.g. code snippets
Does declaring a GraphQL type using @model directive now create AmplifyDataStore DynamoDB tables? I know they are used for "Delta Sync" feature of DataStore, but I'm not currently using DataStore and I don't remember seeing those tables before.

You're right, I've just seen these tables appearing tonight ouf of nowhere while  I am ont using Datastore either!

Hi @ernestostifano and @eripoll, this is definitely a bug on the Amplify CLI side the workaround would be to edit the file  amplify/backend/api/is4965/transform.conf.json
{
    "Version": 5,
    "ElasticsearchWarning": true,
    "ResolverConfig": {}
}

to
{
    "Version": 5,
    "ElasticsearchWarning": true
}

and invoke command amplify push

@ernestostifano This issue is fixed in the latest version of the CLI


cargo-temp: 0.2.19 -> 0.2.20

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/yozhgoor/cargo-temp/releases.
meta.description for cargo-temp is: A CLI tool that allow you to create a temporary new Rust project using cargo with already installed dependencies
meta.homepage for cargo-temp is: https://github.com/yozhgoor/cargo-temp
meta.changelog for cargo-temp is: https://github.com/yozhgoor/cargo-temp/releases/tag/v0.2.20
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.2.20 with grep in /nix/store/np7m873ksd9k8jsq91yy9fsrgnzrhdcn-cargo-temp-0.2.20
found 0.2.20 in filename of file in /nix/store/np7m873ksd9k8jsq91yy9fsrgnzrhdcn-cargo-temp-0.2.20

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cargo-temp

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/np7m873ksd9k8jsq91yy9fsrgnzrhdcn-cargo-temp-0.2.20 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cargo-temp https://github.com/r-ryantm/nixpkgs/archive/be86ca7e0e5320b7a42711b88c1b32cafce7fef1.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/be86ca7e0e5320b7a42711b88c1b32cafce7fef1#cargo-temp

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/np7m873ksd9k8jsq91yy9fsrgnzrhdcn-cargo-temp-0.2.20
ls -la /nix/store/np7m873ksd9k8jsq91yy9fsrgnzrhdcn-cargo-temp-0.2.20/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

cargo-temp

Maintainer pings
cc @figsoda @matthiasbeyer for testing.

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

1 package built:

cargo-temp

Backport pushed to https://github.com/NixOS/nixpkgs/pull/298312


Rustdoc: Scrape example

Objective
Provide more usage examples in API docs so that people can see methods being used in context.
Solution
Enable experimental rustdoc feature "scrape examples". See https://doc.rust-lang.org/nightly/rustdoc/scraped-examples.html for official docs.
Example screenshots of examples :)

Limitations

Only methods seem to show examples so far
It may be confusing to have curated examples from doc comments followed by snippets from examples/

If this is approved, consider including it in 0.11.1!

re ci: check-bans fail seems unrelated

I also agree that its worth including in 0.11.1

I'm on board in principle with enabling this! Haven't reviewed the diff yet though.

I've played with this in bevy-ui-navigation. In my experience it's tricky to get the config right so that docs.rs properly scraps examples.

@mockersf Would this work with https://dev-docs.bevyengine.org/bevy/index.html?

Just so you know, new examples will need these flags in Cargo.toml. Maybe a good idea to check this in CI.

I think this doesn't work. It was part of 0.11.1 so docs on docs.rs should be built with it but I can't find any scraped example

I think this doesn't work. It was part of 0.11.1 so docs on docs.rs should be built with it but I can't find any scraped example

looks the same to me

@mockersf FYI if we can make the CI for dev-docs run on nightly, it will pick up https://github.com/rust-lang/cargo/issues/13074 and include examples :)


Add Category as a class of

I'm working on a new site and for easier theming, it's really handy to have the category in the body class.
In order to achieve this, in templates/base.html I changed the line that reads <body> to:
<body{% if category %} class='{{category}}' {% endif %}>

I don't know if this is something that others would feel is useful/handy, so I'm not sure if I should submitting a Pull Request.

Hi!
First of all, thanks for your interest in this theme! It's with heavy heart that I have decided that I can no longer maintain this theme due to lack of time and changing interests. To makes sure the theme lives on however and not goes to waste, I've donated it to the Pelican community. It can now be found in the official pelican-themes repository. I'd suggest you re-submit your issue  there.
Sorry for the inconvenience!


Add Cueme underwear support

See buttplugio/stpihkal#22

buttplug-js will soon be part of buttplug-wasm in https://github.com/buttplugio/buttplug-rs-ffi, closing this bug as it relates to implementation that will be taken care of in buttplug-rs.


Explicitly specify the void type keyword for all void functions/methods.

Current coverage is 73.01% (diff: 97.05%)

Merging #1042 into master will decrease coverage by 0.28%

@@             master      #1042   diff @@
==========================================
  Files           126        125     -1
  Lines         18209      17972   -237
  Methods        2547       2523    -24
  Messages          0          0
  Branches       2220       2189    -31
==========================================
- Hits          13347      13122   -225
+ Misses         4172       4167     -5
+ Partials        690        683     -7

Powered by Codecov. Last update c53c0e4...c7d0275