[WIP] Migrate to TypeScript - Version 2.0

This PR includes TS Migration, New Awesome Feature, and Bug fix.
I hope to become easy to maintain and update this project, by migrating.
Linking Issue is following:
Enchantment, Feature -
#33 #34 #36 #37 #38 #45
Bug fix:
#35 #41

Feature #47


Clean up after myself

forgot to update the file headers for v1.0.6 in my last batch
+less greedy check on the signature font size

Would you mind throwing in the code for #2232 ? :angel:

Ohhh... and darn, I forgot to update the headers too!... well, I guess I have to clean them up, so I can put in that code myself. ;D

Glad I'm not the only one who forgets these things :innocent:


fix(media-library-cloudinary): fix options, add tests

Rewire seems to have broken some unrelated tests, investigating.

Deploy preview for cms-demo ready!
Built with commit 4a06468ccc46ee16e9e8f2c2d96947b4e24674db
https://deploy-preview-1938--cms-demo.netlify.com

Deploy preview for cms-demo ready!
Built with commit c0f3168d61da65ac204a237aebd4dc66c3305d00
https://deploy-preview-1938--cms-demo.netlify.com


If a file's already open in the window, don't edit it again.

Description of Changes
Closes #1102
The issue can be recreated without NERDTree using these commands that simulate what NERDTree does:
$ echo "hello" > world.txt
$ vim

:set noconfirm
:e world.txt
:copy 0
:vsplit
:e world.txt

The solution is to skip the second :e world.txt command if the file is already open in the new window. This fixes a regression introduced in #1098.

New Version Info
Author's Instructions

[x] Derive a new MAJOR.MINOR.PATCH version number. Increment the:

MAJOR version when you make incompatible API changes
MINOR version when you add functionality in a backwards-compatible manner
PATCH version when you make backwards-compatible bug fixes

[x] Update CHANGELOG.md, following the established pattern.

Collaborator's Instructions

[x] Review CHANGELOG.md, suggesting a different version number if necessary.
[x] After merge, tag the merge commit, e.g. git tag -a 3.1.4 -m "v3.1.4" && git push origin --tags

Hello, I can't open the file after upgrading nerdtree to 6.7.6
Error detected while processing function nerdtree#ui_glue#invokeKeyMap[1]..80[18]..79[3]..30_customOpenFile[1]..109[1]..125[3]..181[6]..182[17]..16:
line    2:
E119: Not enough arguments for function: bufname
E15: Invalid expression: bufname() !=# l:bufname

Upgrading to vim 8.2 fixed the problem for me personally, but I guess this plugin wants to maintain some kind of backwards compatibility for older vim versions.

Yes, the bufname() implementation changed in 8.2, such that the argument is optional. I fixed this in #1105

This is awesome; I just encountered this error from installing NERDTree last night and it's already fixed. Thanks!

Thanks, I upgraded vim to 8.2 and the problem was solved

Today I have a new problem.
When use NERDTree to open a file in a directory, it opens a directory instead.
The cause of this problem is that I moved the directory of the file.

@scrawld, can you open a new issue for this and provide more detail about how to recreate it?
Thanks!


[Feature][Connector-V2] Support multi-table sink feature for hive

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
sub task of #5652
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@Carl-Zhou-CN

@FlechazoW

Hi, @FlechazoW , Is there any progress on this task?


TST: ndimage: GPU test failures

@ev-br I just gave the ndimage tests a whirl on GPU. Looks like you covered CuPy and JAX well, but there are a lot of failures with PyTorch. We need to figure out how to skip on GPU while still testing CuPy. The crude way to do this is to just add skips for torch specifically , which may be the best option for now.
https://gist.github.com/lucascolley/62e223fa893204ffc51da057457a641b

But this is expected, right? GPU tensors cannot be used with numpy-only compiled CPU code. torch.cpu is fine, torch gpu is not and will never be. Ditto for jax on GPU. And it's all ndimage.

yup, but that doesn't mean we want hundreds of errors when running the test suite - that is what the skip machinery is for. I think I've figured out a decent API for it, will work on a PR.


Revert "[Envoy Mobile]Implement QUICHE_LOG with ABSL_LOG (#30160)"

This reverts commit 5b4e1a6d57777836f858b377534a7ffdaa42a41a.

Target //library/kotlin/io/envoyproxy/envoymobile:envoy

https://github.com/envoyproxy/envoy/actions/runs/6512770457/job/17691086927#step:5:53

cc @RyanTheOptimist main is permafailing currently

/retest


Class diagram

Unified Modeling Language (UML) diagrams generated using Pyreverse, a tool in the Pylint tool suite.

Running this script and following the instructions in it I generated several uml in the folder uml/.
In this folder you can find the main .svg images, and in particular I think that classes_npl.svg and packages_npl.svg are the most relevant for our purpose.
Anyway, running the make_uml.sh script locally (after having installed both pylint and plantuml) you can generate all the files (there can be multiple diagrams for each module), and also the .puml files that I deleted here. You can use them to display interactively the uml, as explained here.

Could you please review this PR? @FarzanehParizi

@gcroci2 @LilySnow
Better to check the main changes of the final implementation to the first draft of the class diagram before merging. There are many updates and changes compared to the first draft of the class diagram, as the first draft was designed based on the initial requirements.
With an overall check you can see changes for the Query Interface and the classes designed to implement it:
e.g.

The Query class is not implemented as an Interface. The interface helps to reduce the code (no implementation is needed in Interface) while providing only the layout for the classes which implement it.
The PPIInterface class has been changed to two different classes as  PPIInterfaceAtomicQuery and PPIInterfaceResidueQuery. Although both have mainly the same code copied. They could have been designed with much less code.
The same for SingleResidueVariantResidueQuery and SingleResidueAtomicQuery

Bellow you can see the first draft for this class:

@gcroci2 @LilySnow Better to check the main changes of the final implementation to the first draft of the class diagram before merging. There are many updates and changes compared to the first draft of the class diagram, as the first draft was designed based on the initial requirements.

The code represented in the class diagrams has been already merged (months ago). But if we think it needs to be changed to be improved, we can of course open new issues.

With an overall check you can see changes for the Query Interface and the classes designed to implement it: e.g.

The Query class is not implemented as an Interface. The interface helps to reduce the code (no implementation is needed in Interface) while providing only the layout for the classes which implement it.

Could you be more detailed? Meaning, what should we change in the Query class? For me it's not clear. Maybe it is for @cbaakman ?

The PPIInterface class has been changed to two different classes as  PPIInterfaceAtomicQuery and PPIInterfaceResidueQuery. Although both have mainly the same code copied. They could have been designed with much less code.
The same for SingleResidueVariantResidueQuery and SingleResidueAtomicQuery

I agree that PPIInterfaceAtomicQuery and PPIInterfaceResidueQuery (and same for SingleResidueVariantResidueQuery and SingleResidueAtomicQuery) contain basically the same code. But I bet there was a reason for implementing them in this way, right @cbaakman ?

@gcroci2 I think that the query class cannot be considered an interface anymore, because it has inheritable private methods. I made those so that it's children don't have to implement them. PPIInterfaceAtomicQuery and PPIInterfaceResidueQuery do almost the same, but one builds an atomic graph and the other one builds a residue graph.

So the questions now are:

Does the actual Query class, which is not an interface, have limitations? If yes, which ones and why? @FarzanehParizi
Regarding PPIInterfaceAtomicQuery and PPIInterfaceResidueQuery: the only real different method between these two classes is build_graph, which builds either an atomic graph or a residue graph. This is also the only actual method implemented in the two classes (if you don't consider the dunder methods and get_query_id). Note also that the dunder methods and the get_query_id method do not have much code. I think it makes sense to have two different classes, especially if we think about possible future implementations of atomic-level and residue-level graphs: maybe there will be the need of implementing completely different stuff in the two classes and having the two of them would be handy. But of course, I'm open to discussing it. @LilySnow @FarzanehParizi

For now, we'll keep the code as it is. In the future, we can take some time to explore the possibility of changing some of the internals, comparing the code to its starting design.


GO:0044876, Rhea reaction linked to this term has been deleted

RHEA:42680, linked to this GO term has been deleted since new research published in pmid:36071162 has demonstrated that selenoneine is synthesised by these reactions:
RHEA:77159 H2O + selenophosphate + UDP-N-acetyl-α-D-glucosamine = H+ + N-acetyl-1-seleno-β-D-glucosamine + phosphate + UDP
RHEA:77163 H+ + hercynine + N-acetyl-1-seleno-β-D-glucosamine + O2 = H2O + hercynyl-SeGlcNAc selenoxide
RHEA:77167 AH2 + hercyncyl-SeGlcNAc selenoxide = 2-acetamidoglucal + A + H2O + selenoneine
RHEA:77167 is spontaneous
The change will become public in release 2024_01 scheduled for January 17 2024.

Hi @kaxelsen
I dont find these in the rhea-test site yet; go you have references for these?

Unfortunately, the new reactions have not yet been reviewed by @amorgat

RHEA:77159, RHEA:77163 and RHEA:77167 are now approved. Pascale, these reactions will be available tomorrow in rhea-test. Warning PMID:36071162 may only be displayed later (bibliography is updated once a week).


~Free Cash App Money Hacks You Need to Try Right Now [ TRCXg]

｡･ﾟﾟ･Free Cash App Money Hacks You Need to Try Right Now [ TRCXg]
Get Rich Quick: How to Score Free Cash App Money in 5 Easy Steps!
Are you tired of living paycheck to paycheck? Do you dream of financial freedom and never having to worry about money again? Well, look no further because we have the ultimate solution for you - free cash app money!
🔴📺📱👉 Click here free cash
🔴📺📱👉 Click here free cash
In this groundbreaking article, we will reveal the secrets to unlocking unlimited cash app money without spending a dime. Yes, you read that right - FREE money just waiting for you to claim it.
Step 1: Download the Cash App
The first step to getting free cash app money is to download the Cash App on your smartphone. This user-friendly app allows you to send and receive money with just a few taps of your finger, making it the perfect tool for scoring some extra cash.
Step 2: Sign Up for an Account
Once you have downloaded the Cash App, it's time to sign up for an account. Simply enter your email address and create a password to get started. Don't worry, it's completely secure and your information will be kept safe.
Step 3: Link Your Bank Account
To start receiving free cash app money, you'll need to link your bank account to the app. This will allow you to transfer money back and forth between your bank and the Cash App with ease.
Step 4: Refer Your Friends
Now here's where the magic happens - refer your friends to join the Cash App and earn free money for each person who signs up using your unique referral code. The more friends you refer, the more cash you'll earn!
Step 5: Cash In Your Rewards
Once you've accumulated enough free cash app money, it's time to cash in your rewards. Simply transfer the money to your bank account and watch as your wallet grows fatter with each referral.
So what are you waiting for? Say goodbye to financial stress and hello to a life of abundance with free cash app money.


[FEATURE REQUEST]

I am using foundry 0.8.9 with the sandbox module and the clocks dont work. They are unresponsive, and cant make them to "thick" nor am i able to change the number of segments of the clock. I would really like to use this module.

Edit: sanndbox world, i mean

Apologies for the delay. Github never sends me notifications regarding issues here.
As for this. Can you note which version of Lancer Clocks is being used? There may be an easy fix depending on the version given. That being said, further notable support for Foundry 0.8.9 is unlikely due to how much the API has changed.


[DELIVER] Support new App Store Connect APIs ✨

Feature Request
Motivation Behind Feature
Just in the last few weeks, Apple broke some undocumented APIs that fastlane was using to interact with App Store Connect.  Fastlane should prefer to use documented public APIs where possible to avoid these kinds of situations in the future.
What's new in App Store Connect

We're excited to be adding two powerful new sets of API.  We'll be introducing a suite of app metadata API that will let you manage your presence on the App Store as well as a new power and performance API. They'll let you download the same aggregate data that drives the new power and performance analysis tools in Xcode.  In fact, just between these two new categories of API functionality, we're adding over 200 new endpoints.  For app metadata, you'll be able to do things like create new App Store versions, set pricing and availability, edit app and version metadata, associate builds to your App Store versions, and submit those versions for review.

Another session later this week will go more in-depth Expanding automation with the App Store Connect API
Feature Description
This can be more fleshed out later in the week when the other session becomes available to give more concrete info on what APIs will be available
Alternatives or Workarounds
Continue to use undocumented APIs that might break in the future

Please see https://github.com/fastlane/fastlane/pull/16640 and https://github.com/fastlane/fastlane/issues/16639 😊
Its already mostly done and in available for testing in 2.150.0.rc2


Write a Kotlin program to convert hours to minutes

Description
Write a Kotlin program to convert hours to minutes
1 hour = 60 minutes
Input  : 5
Output : 300

How to contribute

Save the solution in program/ConvertHoursToMinutes.kt file
Add ConvertHoursToMinutes.kt file in convert-hours-to-minutes folder

!assign


Add validator with line number and default setter

Error on backporting to branch 0.9, see Docker Hub actions for more information.


[Error: 907135000: arguments invalid] after upgrading to react-native 0.73.9

Description
I have recently upgraded my project to 0.73.9 and I found that I had to also upgrade hmscore/react-native-hms-push from 6.5.0-300 as it was causing the build to fail. I tried to go with the latest version 6.12.0-302 but although the build is successful the hms-push service doesn't seem to work at all. After debugging the issue i found that the getToken method always seem to exit with this error
Error registering to HMS [Error: 907135000: arguments invalid]

According to my investigation this seemed to be an issue with my configuration, I have removed everything hms related from my project and followed the documentation to make sure I have the absolute latest configurations but I still ended up with the same issue.
I looked into the GitHub issues here and followed a couple more suggestions but none of them seemed to work (#335, #217, #185)
settings.gradle
rootProject.name = <REDACTED>

if (System.getenv("IS_HUAWEI")=="TRUE") {
  include ':react-native-hms-push'
  project(':react-native-hms-push').projectDir = new File(rootProject.projectDir, '../node_modules/@hmscore/react-native-hms-push/android')
}
apply from: file("../node_modules/@react-native-community/cli-platform-android/native_modules.gradle");
applyNativeModulesSettingsGradle(settings)
include ':app'
includeBuild('../node_modules/@react-native/gradle-plugin')

app/android/build.gradle
if (System.getenv("IS_HUAWEI")=="TRUE") {
  apply plugin: "com.huawei.agconnect"
}

buildscript {
    ext {
        buildToolsVersion = "34.0.0"
        minSdkVersion = 26
        compileSdkVersion = 34
        targetSdkVersion = 34
        kotlinVersion = "1.8.0"
        ndkVersion = "25.1.8937393"
        androidXBrowser = "1.3.0"
    }
    repositories {
        google()
        mavenCentral()
        if (System.getenv("IS_HUAWEI")=="TRUE") {
          maven { url 'https://developer.huawei.com/repo/' }
        }
    }
    dependencies {
        classpath("com.android.tools.build:gradle")
        classpath("com.facebook.react:react-native-gradle-plugin")
        classpath('org.jetbrains.kotlin:kotlin-gradle-plugin')
        if (System.getenv("IS_HUAWEI")=="TRUE") {
          println("Using Huawei push")
          classpath 'com.huawei.agconnect:agcp:<IP_ADDRESS>0'   //Huawei
        } else {
          println("Using Firebase push")
          classpath 'com.google.gms:google-services:4.4.2'  //firebase
        }
    }
}
apply plugin: "com.facebook.react.rootproject"
allprojects {
    repositories {
        google()
        mavenCentral()
        if (System.getenv("IS_HUAWEI")=="TRUE") {
          maven { url 'https://developer.huawei.com/repo/' }
        }
    }
}

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

apply from: project(':react-native-config').projectDir.getPath() + "/dotenv.gradle"
react {}
def enableProguardInReleaseBuilds = true
def jscFlavor = 'org.webkit:android-jsc:+'

project.ext.react = [
  enableHermes: true,  // clean and rebuild if changing
]

project.ext.sentryCli = [
  logLevel   : "debug",
  flavorAware: true
]

apply from<EMAIL_ADDRESS>
android {
  ndkVersion rootProject.ext.ndkVersion
  buildToolsVersion rootProject.ext.buildToolsVersion
  compileSdk rootProject.ext.compileSdkVersion

  compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
  }
  namespace <REDACTED>
  defaultConfig {
    applicationId <REDACTED>
    minSdkVersion rootProject.ext.minSdkVersion
    targetSdkVersion rootProject.ext.targetSdkVersion
    multiDexEnabled true
    ...
  }

  signingConfigs {
    release {
      if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
        storeFile file(MYAPP_RELEASE_STORE_FILE)
        storePassword System.getenv("KEYSTORE_PASSWORD")
        keyAlias MYAPP_RELEASE_KEY_ALIAS
        keyPassword System.getenv("KEYSTORE_PASSWORD")
      }
      v2SigningEnabled true
      enableV3Signing = true
    }
    debug {
      storeFile file('debug.keystore')
      storePassword 'android'
      keyAlias 'androiddebugkey'
      keyPassword 'android'
      v1SigningEnabled true
      v2SigningEnabled true
      enableV3Signing = true
//      proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
    }
  }
  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.
      debuggable false
      shrinkResources enableProguardInReleaseBuilds
      zipAlignEnabled enableProguardInReleaseBuilds
      minifyEnabled enableProguardInReleaseBuilds
      proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
      signingConfig signingConfigs.release
    }
  }
  packagingOptions {
     pickFirst 'lib/x86/libc++_shared.so'
     pickFirst 'lib/x86_64/libjsc.so'
     pickFirst 'lib/arm64-v8a/libjsc.so'
     pickFirst 'lib/arm64-v8a/libc++_shared.so'
     pickFirst 'lib/x86_64/libc++_shared.so'
     pickFirst 'lib/armeabi-v7a/libc++_shared.so'
  }
  flavorDimensions "type"
  productFlavors {
    uat {
      dimension "type"
    }
    production {
      dimension "type"
      applicationId <REDACTED>prod
    }
  }
}

dependencies {
  // The version of react-native is set by the React Native Gradle Plugin
  implementation("com.facebook.react:react-android")
  implementation("com.facebook.react:flipper-integration")

  if (hermesEnabled.toBoolean()) {
    implementation("com.facebook.react:hermes-android")
  } else {
    implementation jscFlavor
  }
  if (System.getenv("IS_HUAWEI")=="TRUE") {
    implementation "com.huawei.hms:push:<IP_ADDRESS>0"
  }

  implementation 'com.onfido.sdk.capture:onfido-capture-sdk:16.1.0'
  implementation 'com.onfido.sdk.capture:onfido-capture-sdk-core:16.1.0'
  implementation 'androidx.work:work-runtime:2.8.0'
  implementation 'androidx.work:work-runtime-ktx:2.8.0'
  implementation 'com.datatheorem.android.trustkit:trustkit:1.1.3'
  implementation 'androidx.preference:preference-ktx:1.1.1'
  implementation 'androidx.swiperefreshlayout:swiperefreshlayout:1.1.0'
  implementation(platform("com.squareup.okhttp3:okhttp-bom:4.9.3"))
  // define any required OkHttp artifacts without version
  implementation("com.squareup.okhttp3:okhttp")
  implementation("com.squareup.okhttp3:logging-interceptor")
  implementation("com.appmattus.certificatetransparency:certificatetransparency:2.4.1")
  implementation("com.appmattus.certificatetransparency:certificatetransparency-android:2.4.1")
}

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

// For Firebase
if (System.getenv("IS_HUAWEI") != "TRUE") {
  apply plugin: 'com.google.gms.google-services'
}

Environment

Platform: React-Native
Kit: Push
Kit Version 6.12.0-302
OS Version Android 12
Android Studio version (if applicable) [e.g. 4.1]
Platform version (if applicable)
Node Version v18.19.1
Your Location/Region (if applicable)

Facing same problem with react-native 0.76.1. Also tried everything proposed in issues you mentioned with no success.
Have you been able to solve this?

Facing same problem with react-native 0.76.1. Also tried everything proposed in issues you mentioned with no success.
Have you been able to solve this?

Recently I also get the error 907135000 with cordova-plugin-hms-push. I believe it happens since I updated to the latest cordova-android (using Android SDK 34). I do not have any problem with previous versions of my app using Android SDK 33. Using the latest @hmscore/cordova-plugin-hms-push does not help. I have not found any solution so far.


Update virtual-machines-faq-for-disks.md

Got this question from a customer - i think its super important to state it here.

@MaxMelcher : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@MaxMelcher sorry about the delay. We appreciate you taking the time to help improve our docs. Would you mind modifying your change? We would prefer updating the first bullet rather than making a second, completely separate bullet for this. I'll suggest some text in comment format.

@MaxMelcher : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@MaxMelcher Thanks for making that change, it all looks good now so:
#sign-off


[Snyk] Security upgrade python from 3.6 to 3.10.14

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

base/python/python3.6/Dockerfile

We recommend upgrading to python:3.10.14, as this image has only 199 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

829
Out-of-bounds Write SNYK-DEBIAN11-LIBWEBP-5893094
Mature

829
Out-of-bounds Write SNYK-DEBIAN11-LIBWEBP-5893094
Mature

829
Out-of-bounds Write SNYK-DEBIAN11-LIBWEBP-5893094
Mature

829
Out-of-bounds Write SNYK-DEBIAN11-LIBWEBP-5893094
Mature

844
Resource Exhaustion SNYK-DEBIAN11-NGHTTP2-5953384
Mature

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Resource Exhaustion

Checkmarx One – Scan Summary & Details – b5d6d32c-ce66-4bd6-af9e-0315e8903469
No New Or Fixed Issues Found


Rename output.from and output.to

Output.from expression indicates the result of the task (and can be consumed by subsequent task)
Output.to expression indicates what should be the value of the context once the task is completed.
I think the names are confusing (it actually takes me a lot of time to understand why do we have two expressions in output), so I think we must change them.
output.from might be renamed to output.result (the expression indicates the result of the task)
output.to might be renamed to output.setContext (clearly states the purpose is to the set the value of the context), If we found that setContext break the single word paradigm that we are implicitly following in the DSL, then lets just use output.context.
Also we need to explicilly indicate in the documentation that it is assumed that the expression language should support merging context.
Related to that, if this assumption turns to be wrong, another possibility is to use
output:
    context:
        set:

Right now, context will only support set: but we leave the door open to add append:, delete: or merge: in future if needed

@JBBianchi @matthias-pichler-warrify WDYT?

Renaming output.from to output.result
Renaming output.to to output.context
Creating two expression properties to describe the performed operation

Personally:

Fine by me, though I personally like the actual wording. As demonstrated by #837 and by @fjtirado admitedly late understanding by lack of info, it does however requires much more documentation.
Same than 1.
As expressed in #837, I personally prefer it the way it is now, meaning that the user has the ability to write the expression he wants (i.e. replace or update the context). I do think however that the proposal makes sense, so I'll rally to the consensus on that one.

Globally, more documentation won't hurt, for sure :)
If I can add my grain of salt, we might gain clarity by "splitting" output.from and output.to into distinct keywords. So my take would be the following:

Rename output.from to output, it shows the intention of the user to alter/transform the default output (but I have no strong opinion)
Rename output.to to export, it shows the intention of the user to export something from the task to a broader context (but  again, I have no strong opinion)
Relying on the expression rather than making the spec more complex seems a better solution to me, so I'd rather keep this as they are.

Rename output.from to output, it shows the intention of the user to alter/transform the default output (but I have no strong opinion)
Rename output.to to export, it shows the intention of the user to export something from the task to a broader context (but again, I have no strong opinion)

You suggestion is awesome! Much clearer and ubiquitous!
This would however get rid of the critical output.schema property, as discussed in #837 😭 We could however move it elsewhere. Ideas?

Good catch, I didn't think about that ... We could keep the to then maybe ? (or as)
input:
  from: ...
  schema: ...
output:
  to/as: ...
  schema: ...
export:
  to/as: ...
  schema: ...

The problem with to is that it might user though they can set the destination, which is not really true, soo I vote for as rather than.
I was going to suggest the same split than @JBBianchi ;)
Also, using export: as a separate keyword allow us to add in future set: or merge: if we change our mind.

Good catch, I didn't think about that ... We could keep the to then maybe ? (or as)

Works for me!
On a side note, there is not way to specify the context schema, but I get its was a copy/paste leftover.
Should therefore be:
input:
  from: ...
  schema: ...
output:
  to/as: ...
  schema: ...
export: 'myexpression'

Or, if we believe we might need additional properties at some point, like @fjtirado said:
input:
  from: ...
  schema: ...
output:
  as: ...
  schema: ...
export: .data += .mydata

On a side note, there is not way to specify the context schema, but I get its was a copy/paste leftover.
It was intentional, why can't we support a schema for the context as well ? I think it's a point that's been raised, even in the previous version of the spec, that we don't know at some point in the workflow, what to expect in the context. With the schema, it give the opportunity to the user to defined what expected of the context to be at a given point in time.

@JBBianchi because you cannot forecast the state of the context (ex: if a switch state was executed before) at a point in time. AFAIK, that never was brought up, also because you can both update the context (adding a new prop, removing one, etc) and replace it. For the replace it could work but has little to no value. For the update, that would be impossible or at least impractical, for little to no value.

@cdavernas I can schema for context being used by users that want to restrict the context content (I do agree with you that the most frequent use case is "free" context ;)). As far as is optional I do not see any issue.

@JBBianchi because you cannot forecast the state of the context (ex: if a switch state was executed before) at a point in time.
AFAIK, that never was brought up, also because you can both update the context (adding a new prop, removing one, etc) and replace it. For the replace it could work but has little to no value. For the update, that would be impossible or at least impractical (diff patch or replace), for little to no value.
IMO there's no way you, or any user, would like to document a whole schema just for updating a prop in a data bag (unordered, untyped).

I don't really agree with your arguments. As the user defines the context, it's predictable. The user knows what kind of operations he does (merge, replace, patch...) to the context. The only thing I agree with is that it might become cumbersome, it requires copy/pasting the schema maybe, or it might be a complex schema, and most users won't use them. But most users won't use input/output schemas either, at least not inside the workflow. But I think it's still a valuable piece of information to know the structure of the data at any given point.
That being said, we can postpone this discussion for now. I believe we've reached a consensus on replacing output.to with export.as. (Personally, I would also prefer using output.as, but I don't have a strong preference. It could remain from, become to, or as - it's a minor detail.)

@JBBianchi I prefer output.as too

The only point I agree with is that writing the schemas can become cumbersome. It involves copying and pasting them, they might be complex, and most users won't bother. However, most users also won't utilize input/output schemas, at least not within the workflow. Nevertheless, I believe it is valuable to understand the structure of the data at any given point.

It might be very valuable though to validate a subset of properties in the context. JSON Schema objects have additionalProperties: true by default so the schema
type: object
properties:
  foo:
    type: number

allows all the following values:
{
  "foo": 1
}

{
  "foo": 1,
  "bar": true
}

so it is trivial to write a context schema that for example only validates the exported properties 👍  It is not required to copy paste the schema to every task.
On another note the workflow schema also does not specify additionalProperties or unevaluatedProperties at the moment so arbitrary garbage properties can be set everywhere and it would still validate (I was thinking about opening a PR to fix this)

+1 @matthias-pichler-warrify to fix the validation, hence I think we can also improve our CI to have invalid DSLs


update admin panel

Overview
this PR purpose is to merge the new written admin panel to the current e-wallet repository.
Changes

change admin panel
redefine how to run admin panel on starting server

Implementation Details
change the whole logic of admin panel, now all data will be lazy loaded and cached after so increase the experience for users
Usage
runs admin panel normally
Impact
this PR does not includes a lot of test cases and can break anytime, for merging purpose.

Oh btw. Looks really neat. Awesome job!

I ran it in local and it looks great, just a few comments that should be fixed in an other PR:

@unnawut fixed


Install failed: no matches for kind "CertificateSigningRequest" in version "certificates.k8s.io/v1beta1"

Component
webhook-init and webhook
Description
The status of pod kuda-webhook-init is CrashLoopBackOff:
$ kubectl get pod -n kuda-system
NAME                                       READY   STATUS              RESTARTS      AGE
kuda-controller-manager-6fbcfc9867-v9nx6   2/2     Running             0             2m40s
kuda-webhook-74bb8c6d7b-7lcfx              0/1     ContainerCreating   0             2m39s
kuda-webhook-init-qwbzx                    0/1     CrashLoopBackOff    4 (58s ago)   2m39s

Error message in logs for this pod as follows:
......
error: unable to recognize "STDIN": no matches for kind "CertificateSigningRequest" in version "certificates.k8s.io/v1beta1"

Version
kubernetes version:  v1.23.4

The webhook-init should use admissionregistration.k8s.io/v1 instead v1beta1 which has been removed:
$ kubectl api-versions | grep admissionregistration.k8s.io
admissionregistration.k8s.io/v1


Will the image size of the training resource affect the training result?

I noticed that my largest image size is 4096x2621. When the model training is completed, the model file is several hundred MB, but the default pre-trained model cunet model file is only about 20MB, because I don’t understand these contents, I just guess the larger the size will help Image enlargement retains clearer content, but also produces a larger segmentation training time.

Torch's model has some temporary buffers. Most of them are removed by clearState() when saving the model, but some remains. These do not affect the scaling/denoising result.
The default pretrained models are rebuild by tools/cudnn2cunn.lua. At that time, all unnecessary buffers are removed, so the size is small.


Fixing codecoverage

Context:
A few open PRs are failing because of indirect changes in the coverage of three files, all of which are unrelated to the given PRs.
Here, I either add tests (where I know how to test) or # pragma: no cover to the problematic lines

I think codecov is wrong....
Tried running tests locally with prints inserted where codecov claims to be not covered, it is actually hitting those lines.

I think codecov is wrong....
Tried running tests locally with prints inserted where codecov claims to be not covered, it is actually hitting those lines.

Mmmh interesting..
So what would you suggest we do? We could force this in with #pragma no cover?


[FLINK-2259][ml] Add Train-Testing Splitters

This PR adds an object in ml/pipeline called splitter with the following methods:
randomSplit: Splits a DataSet into two data sets using DataSet.sample
multiRandomSplit: Splits a DataSet into multiple datasets according to an array of proportions
kFoldSplit: Splits DataSet into k TrainTest objects which have a testing data set of size 1/k of the original dataset and the remainder of the dataset in the training
trainTestSplit: A wrapper for randomSplit that return a TrainTest object
trainTestHoldoutSplit: A wrapper for multiRandomSplit that returns a TrainTestHoldout object
the TrainTest and TrainTestHoldout objects are case classes.  randomSplit and multiRandomSplit return arrays of DataSets.

[x] General

[ ] Documentation

Documentation is in code, will write markdown after review/feedback/finalization

[x] Tests & Build

One build failed on error: scala.reflect.internal.MissingRequirementError: object scala.runtime in compiler mirror not found.
Another on some weird YARN stuff, which I didn't touch. Flakey builds?

Yes the failing tests are most likely caused by the build infrastructure.

Any thoughts on this approach or go ahead and write docs/prepare to merge?

Thanks for your contribution @rawkintrevo. Good work. I had some minor inline comments. I'm mainly concerned about the efficiency of multiRandomSplit because it can construct some really long pipelines.
I think we should also add online documentation for the Splitter. Otherwise people will just miss it. You can take a look at docs/libs/ml/ and create a web page for the splitter. We could then create a site with tools from where we link to the Splitter, for example.

Hey @tillrohrmann, thanks for the review.  I've addressed your commments in the code. I am in the middle of documentation had to commit. Should finish up docs this afternoon.

This should be gtg

bump?  failing on flaky test, can someone restart/verify/etc?

The PR looks really good @rawkintrevo. I had some minor comments. Once they are fixed, we should be good to merge this PR :-)

As you've said, the failing test case is unrelated and therefore not a problem.

Thanks for the review @tillrohrmann
I need to find a markdown editor with spell check...

Great work @rawkintrevo and thank you very much for your contribution :-) I'm going to merge your PR now. Sorry for the long waiting time.

No problem @tillrohrmann ! I know there's been a lot going on.  thank you!


Typeerror at the completion of BayesianSignatureOptimizer

code
teleprompter_baysian = BayesianSignatureOptimizer(prompt_model="Route the respective question to the required service", task_model="route integer option", metric=metric, n=3)

kwargs = dict(num_threads=NUM_THREADS, display_progress=True, display_table=0)

compiled_router_prompt = teleprompter_baysian.compile(Router_module(),  devset=total_data[:DEV_NUM], optuna_trials_num=100, max_bootstrapped_demos=3, max_labeled_demos=5, eval_kwargs=kwargs)

Error
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Cell In[34], [line 3](vscode-notebook-cell:?execution_count=34&line=3)
      [1](vscode-notebook-cell:?execution_count=34&line=1) teleprompter_baysian = BayesianSignatureOptimizer(prompt_model="Route the respective question to the required service", task_model="route integer option", metric=metric, n=3)
      [2](vscode-notebook-cell:?execution_count=34&line=2) kwargs = dict(num_threads=NUM_THREADS, display_progress=True, display_table=0)
----> [3](vscode-notebook-cell:?execution_count=34&line=3) compiled_router_prompt = teleprompter_baysian.compile(Router_module(),  devset=total_data[:DEV_NUM], optuna_trials_num=100, max_bootstrapped_demos=3, max_labeled_demos=5, eval_kwargs=kwargs)

File [/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:301](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:301), in BayesianSignatureOptimizer.compile(self, student, devset, optuna_trials_num, max_bootstrapped_demos, max_labeled_demos, eval_kwargs, seed, view_data, view_examples)
    [298](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:298)             demo_candidates[id(module_p)].append(candidate_p.demos)
    [300](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:300) # Generate N candidate prompts
--> [301](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:301) instruction_candidates, _ = self._generate_first_N_candidates(module, self.n, view_data, view_examples, demo_candidates, devset)
    [303](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:303) # Initialize variables to store the best program and its score
    [304](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:304) best_score = float('-inf')

File [/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:176](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:176), in BayesianSignatureOptimizer._generate_first_N_candidates(self, module, N, view_data, view_examples, demo_candidates, devset)
    [174](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:174)     self.observations = None
    [175](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:175)     with dspy.settings.context(lm=self.prompt_model):
--> [176](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:176)         self.observations = self._observe_data(devset).replace("Observations:","").replace("Summary:","")
    [178](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:178) if view_examples:
    [179](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:179)     example_sets = {}

File [/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:131](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:131), in BayesianSignatureOptimizer._observe_data(self, trainset)
    [129](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:129) def _observe_data(self, trainset):
    [130](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:130)     upper_lim = min(len(trainset), self.view_data_batch_size)
--> [131](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:131)     observation = dspy.Predict(DatasetDescriptor, n=1, temperature=1.0)(examples=(trainset[0:upper_lim].__repr__()))
    [132](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:132)     observations = observation["observations"]
    [134](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/teleprompt/signature_opt_bayesian.py:134)     skips = 0

File [/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:49](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:49), in Predict.__call__(self, **kwargs)
     [48](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:48) def __call__(self, **kwargs):
---> [49](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:49)     return self.forward(**kwargs)

File [/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:90](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:90), in Predict.forward(self, **kwargs)
     [87](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:87) template = signature_to_template(signature)
     [89](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:89) if self.lm is None:
---> [90](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:90)     x, C = dsp.generate(template, **config)(x, stage=self.stage)
     [91](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:91) else:
     [92](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:92)     # Note: query_only=True means the instructions and examples are not included.
     [93](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:93)     # I'm not really sure why we'd want to do that, but it's there.
     [94](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dspy/predict/predict.py:94)     with dsp.settings.context(lm=self.lm, query_only=True):

File [/opt/homebrew/lib/python3.11/site-packages/dsp/primitives/predict.py:77](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dsp/primitives/predict.py:77), in _generate.<locals>.do_generate(example, stage, max_depth, original_example)
     [75](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dsp/primitives/predict.py:75) # Generate and extract the fields.
     [76](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dsp/primitives/predict.py:76) prompt = template(example)
---> [77](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dsp/primitives/predict.py:77) completions: list[dict[str, Any]] = generator(prompt, **kwargs)
     [78](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dsp/primitives/predict.py:78) completions: list[Example] = [template.extract(example, p) for p in completions]
     [80](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/lib/python3.11/site-packages/dsp/primitives/predict.py:80) # Find the completions that are most complete.

TypeError: 'str' object is not callable

You are not using BayesianSignatureOptimizer correct.
prompt_model should not be a string.
See the cheatsheet for more info: https://dspy-docs.vercel.app/docs/cheatsheet


A welcome message would be nice

When you GET on the root or the basePath, it would be nice to display:

Welcome to tusd version x.y.z. For documentation and bug reports, please check https://github.com/tus/tusd

Instead of

Just more friendly and to let admins know they did something right, vs wrong.

Here you go :)

I like it, except that you should not mix "we" and "I".
So let's change "However, there is something I want to tell you personally: " to "However, there is something you need to be aware of: "

Great stuff! We could perhaps run the copy also via @ajvanloon


Fat Boy names.json has extraneous instruments

Hi,
The names.json file for Fat Boy lists synth_strings_1 & 2, but these sounds aren't present as .js or .mp3 samples. Is the names.json wrong or are the sound files missing (or am I missing something?)
Thanks
Rob

You're right! I dug a bit deeper into why this happened. For info here https://github.com/gleitz/MIDI.js/commit/3f4fefe311899c3712156675ec04467db8137876 but essentially MIDI.js does not match the MIDI association spec, but my soundfont-generator does, so this caused compatibility issues.
I will be re-uploading all soundfonts with corrected filenames, fondernames, and names.json files.


Pull request review process

There are 4 open PRs from a year ago, and it would be nice if we could delegate someone to do the reviews

At the time when those PRs where opened there were unfortunately no active caretakers assigned to this project – meaning that there are still no active developers. (I only ended up by a kind of accident in this role later that year and only noticed those PRs today thanks to you. :slightly_smiling_face:)
See the recent comments on #1 for the current status of this: There is nothing usable here and there is no particular reason to retain anything from this repo aside from maybe a few scraps of documentation.


LUCENE-10255: cleaned up module system support and other sub-issues

See also draft PR #470 for history and more details.

Right. I'm not sure there's much to be added here without adding tons of stuff. The issue itself (LUCENE-10255) can remain open for other patches but this one is already huge and is fairly self-contained.
Please take a look and let me know what you think.

showServiceProviders in modules-debbuging.gradle is not available by default, how can one use it?

Include it in the main file or module.gradle. I think it'll be useful in very rare circumstances? If you believe otherwise, we can include it in.

I also did some checks with Eclipse. Project opens and you can edit source code. Of course module-tests (e.g. distribution) won't run.

Luke launch scripts still have --add-modules jdk.unsupported  option. I think this can be removed.
https://github.com/dweiss/lucene/blob/db9dff225ce389eaec8341346a0e32e3cc8aa06d/lucene/distribution/src/binary-release/bin/luke.sh#L20
https://github.com/dweiss/lucene/blob/db9dff225ce389eaec8341346a0e32e3cc8aa06d/lucene/distribution/src/binary-release/bin/luke.cmd#L20

Luke launch scripts still have --add-modules jdk.unsupported  option. I think this can be removed. (I confirmed that MMapDirectory is enabled without this option.) https://github.com/dweiss/lucene/blob/db9dff225ce389eaec8341346a0e32e3cc8aa06d/lucene/distribution/src/binary-release/bin/luke.sh#L20 https://github.com/dweiss/lucene/blob/db9dff225ce389eaec8341346a0e32e3cc8aa06d/lucene/distribution/src/binary-release/bin/luke.cmd#L20

Yes it is obsolete. I tested the command line as printed b gradle and this worked. We need to pass no modules at all because it knows dependencies. (Although I never understood the transitive stuff).

When building a release it fails for some reason (not sure why) on luke's:
Execution failed for task ':lucene:luke:renderJavadoc'.
C:\Users\Uwe Schindler\Projects\lucene\lucene\lucene\luke\src\java\org\apache\lucene\luke\util\LogRecordFormatter.java:28: error - LogRecordFormatter (class): javadocs are missing

I thought we had javadocs disabled?

When building a release it fails for some reason (not sure why) on luke's:
Execution failed for task ':lucene:luke:renderJavadoc'.
C:\Users\Uwe Schindler\Projects\lucene\lucene\lucene\luke\src\java\org\apache\lucene\luke\util\LogRecordFormatter.java:28: error - LogRecordFormatter (class): javadocs are missing

I thought we had javadocs disabled?

No, these are the javadocs jar file, hwich is NOT disabled. So this is an unrelated bug but we should fix it.

I built a release and started ./bin/luke.cmd. I then opened an too old index and it printed a stack trace to log with MMapDirectory, so unsupported module was correctly added by dependencies.
16:09:01 [WARNING] org.apache.lucene.luke.models.util.IndexUtils: Error opening directory
org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="C:\Users\Uwe Schindler\Desktop\index.8.8.0-nocfs\segments_3"))): This index was initially created

I think for the luke, we should make "check" depend on "renderJavadocs" (only for that case, because we don't generate site javadocs), otherwise the javadocs are never checked. @dweiss - you did that change. Should I do a PR on main or simply commit it here?

You're right. If something is not part of site, check should render its javadocs. Perhaps you can file a separate PR for this, referencing original issue number?

I'll take one final look and will commit it in during the weekend. Thanks a lot for collaboration.

You're right. If something is not part of site, check should render its javadocs. Perhaps you can file a separate PR for this, referencing original issue number?

will do.

or leave javadocs to me and fix that apache jenkins worker server, if you know how. :) Is there an ssh to those machines or should infra be involved?

or leave javadocs to me and fix that apache jenkins worker server, if you know how. :) Is there an ssh to those machines or should infra be involved?

That's infra's task. Tey install JDKs with Puppet. I will ask on Slack.

or leave javadocs to me and fix that apache jenkins worker server, if you know how. :) Is there an ssh to those machines or should infra be involved?

That's infra's task. Tey install JDKs with Puppet. I will ask on Slack.

They reverted already the JDK update: https://github.com/apache/infrastructure-p6/pull/914

I'll commit the javadoc fix here - you're right, it belongs here better as the javadoc rendering is slightly different.

I did some sanity checks on this branch. Looks everything is fine.
https://gist.github.com/mocobeta/387585d846714aab86205ab92bc0beba


How to distinguish different audio tracks?

Hello! How to distinguish different audio tracks between publications? The LiveKit server returns the same publication/track sid every time.

It's not clear what you are asking.. please provide additional information including steps to demonstrate your use case.

@davidzhao  This is what I've done to implement my goal. Not sure, if it's useful for everyone. But the idea is to have different remote track id for every publication

I see, I understand you are trying to disable the same track SID being returned during multiple attempts of publish & unpublish sequences.
This is a reasonable workaround. Thanks for sharing!
Closing this issue for now.


perl: add cc in addition to makeBinaryWrapper

Description of changes
see NixOS#311794
The "correct" solution to this problem (makeBinaryWrapper fails to be able to compile the binary wrapper when building a freebsd cross env) is that makeBinaryWrapper should propagate or embed a reference to the compiler. However, this causes build failures on musl, so this will have to do for now.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[x] x86_64-freebsd (native and cross)

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Can you add some sort of "TODO: remove..." in the code? In https://github.com/NixOS/nixpkgs/pull/311794 I left a comment saying I think I know how to fix hardening issue on the "proper" fix.

done


--verbose adds extra context information

dotnet version, if installed/available
code version (vscode), if installed/available

we can even see the installed extensions --list-extensions and ideally their versions too

the foundation image labels in the images being used, if available see https://github.com/QuantConnect/Lean/commit/529841ea776a7c3c3d04ca740be4e34b660ae087 . Lean CLI already reads label from images, see https://github.com/QuantConnect/lean-cli/pull/441, reuse. Research image & lean engine image

See related https://github.com/QuantConnect/Lean/issues/8015
See https://github.com/QuantConnect/lean-cli/blob/master/lean/click.py#L51

@Marinovsky

Reopening so we add user name running the command, docker version, see related https://github.com/QuantConnect/lean-cli/issues/515


AzureCliCredentials throws an exception on invalid data when parsing the token in Windows

Azure.Identity:
1.5.0:
Windows 10:
3.9.2:
Microsoft Azure Cli version 2.0.80

Describe the bug
When trying to obtain a token using AzureCliCredential I get an error saying the token returned from Az is invalid.
Issue seems to lie in some extra characters of unknown origin.
Example of token produced by the library call to account get-access-token
8th line has an ESC char followed by some unknown characters
{
  "accessToken": "eyJ********",
  "expiresOn": "2021-05-12 14:58:55.021835",
  "subscription": "7a7b5559-58af-401a-b543-61b7321a97ea",
  "tenant": "72f988bf-86f1-41af-91ab-2d7cd011db47",
  "tokenType": "Bearer"
}
****

To Reproduce
Hard to say why this fails. Code is basically
self._kusto_uri = "https://kusto.kusto.windows.net"
self._az_auth_context = AzureCliCredential()
msi_token = self._az_auth_context.get_token(self._kusto_uri)

Expected behavior
Well, this ought to produce a valid token :)
Screenshots

Additional context
None

This looks like #11362. The gist of that is, the Azure CLI adds those extra characters to color output. When you use AzureCliCredential in some terminals, in particular PyCharm's, they appear in the subprocess's stdout, making it invalid JSON. Azure CLI added an environment variable applications can set to disable output coloring in its version 2.3.0 or thereabouts, which AzureCliCredential sets to prevent this problem. I see you're using Azure CLI 2.0.80--can you update to a newer version and try again?

That seems to be the issue.
An upgrade resolved the problem.
Thanks!

P.S.
Reading the code, I don't see any cache level in AzCliCredential.
Since you execute a program to get the token, it would significantly slow down scripts that use it repeatedly.
You may want to cache the token for up tp 10 minutes or so before its expires.

Glad that worked, I'll close this issue then. You're correct that AzureCliCredential caches nothing, every get_token() invokes the CLI, ensuring the credential always reflects the login state of the CLI. That does make get_token() expensive but in typical usage, i.e. through an Azure SDK client, it isn't a problem because our clients do what you suggest.


DataView crashes if one of the displayed axes is not an array

If you select an axis that is not an array (i.e. only one element, perhaps from averaging), DataView crashes.  See error log below:
Traceback (most recent call last):
File "/Users/dereks/Documents/GitHub/dataview/dataview/dataview.py", line 434, in updateAxesFieldsAction
self.makePlot()
File "/Users/dereks/Documents/GitHub/dataview/dataview/dataview.py", line 516, in makePlot
self.plot2D()
File "/Users/dereks/Documents/GitHub/dataview/dataview/dataview.py", line 682, in plot2D
cs = self.canvas_ax.contourf(hax, vax, data, levels, cmap=colormap)
File "/anaconda3/lib/python3.7/site-packages/matplotlib/init.py", line 1810, in inner
return func(ax, *args, **kwargs)
File "/anaconda3/lib/python3.7/site-packages/matplotlib/axes/_axes.py", line 6239, in contourf
contours = mcontour.QuadContourSet(self, *args, **kwargs)
File "/anaconda3/lib/python3.7/site-packages/matplotlib/contour.py", line 887, in init
kwargs = self._process_args(*args, **kwargs)
File "/anaconda3/lib/python3.7/site-packages/matplotlib/contour.py", line 1493, in _process_args
x, y, z = self._contour_args(args, kwargs)
File "/anaconda3/lib/python3.7/site-packages/matplotlib/contour.py", line 1551, in _contour_args
x, y, z = self._check_xyz(args[:3], kwargs)
File "/anaconda3/lib/python3.7/site-packages/matplotlib/contour.py", line 1585, in _check_xyz
raise TypeError("Input z must be a 2D array.")
TypeError: Input z must be a 2D array.
Abort trap: 6

Just realized this belongs in the other repository.  Copying over and closing this one.


Replace socket FFI with libc versions

Getting this up there to get some CI run on it. Replacing the msghdr, cmsghdr, and other FFI function declarations will be a little more involved so I wanted to run this through first.

There's more work to do here, but I don't know when I'll be able to get to it, so let's start with this and get it merged.

bors r+


[Bug] - do not work on webstorm 2024.2.1

Describe the bug
After Update of Webstorm to 2024.2.1 the plugin do not work
Platform

IDE Details:1. Click on New
2. The plugin section do not appare

No Update from User closing the issue. Please reopen if this is still an issue.


CI job spec files are not picking up revremark

Describe the bug
The jakarta-cdi-spec-4.1.html and jakarta-cdi-spec-4.1.pdf attached to the CDI Release-JDK17 job build artifacts are showing the correct date, but have the revremark from the pom.xml:
4.1, March 07, 2024: Draft(M1)
The job shows that the revremark was override on the command line with -Drevremark=Final.
Expected behavior
The document revremark should be using the override value passed in on the command line from the build job parameters. When I use the same command line on a local build of the 4.1.0 tagged branch I see the spec files with the revremark from the command line.
Additional context
Add any other context about the problem here.

It seems the release:prepare phase modifies only the versions of the pom files and then creates a separate script to run the release on these. The simplest solution for now is to simply run the build of the spec subproject again after the release build with the license and revremark properties specified. I tried a 5.0.0.Alpha1 build on main with the spec marked as final and that worked. That build has been dropped.


[KK][NodesConstraints] HF3.29(NodesConstraints1.3.2) and KK_HSPlugins_2024.07.08(NodesConstraints 1.3.3) If you “set as child” the root of a person such as “chaF_001” to something, the person becomes unselectable and CharaStudio is forced to terminate.

If you “set as child” the root of a person such as “chaF_001” to something, the person becomes unselectable and CharaStudio is forced to terminate.
It is possible to load the scene and click on the ▶ and ▼ areas without selecting the character, and CharaStudio may not be forced to close just because it becomes unselectable.
If you need to confirm reproducibility, do you need us to upload a video of the procedure?
The version tested is
HF3.29(NodesConstraints1.3.2) and KK_HSPlugins_2024.07.08(NodesConstraints 1.3.3).
I noticed the instability of NodesConstraints in the update from 3.21 to 3.28, I don't think it was there in 3.21.
Sorry for the poor English, I am using a translation engine.

Are you absolutely sure that it is caused by NodesConstraints v1.3.3 update? Is the issue fixed by only reverting NodesConstraints to v1.3.2 without changing anything else?

Release affected https://github.com/IllusionMods/HSPlugins/releases/tag/r2.13

This occurs in both 1.3.2 and 1.3.3.
The version that does not occur is probably in HF3.21.

We need to know exactly which version of NC introduced the issue.

Sorry, the version of NodesConstraints had nothing to do with it.
It seems that KK_ShalltyUtils and NodesConstraints are conflicting in a scene with complex parent-child relationships.
We confirmed this by removing the plug-ins for the scene causing the problem one by one.
After removing KK_ShalltyUtils, the scene with the parent-child relationship could be reorganized.
... I guess I need to switch to a fix request for .KK_ShalltyUtils, but I don't know how to reproduce the complicated scene situation.
Do I need to upload the scene file and have it checked?
Excuse the POOR English by deepl.

You can try asking on discord but at the moment KK_ShalltyUtils is abandoned.

ShalltyUtils was very, very convenient for the timeline tool to support numerical input. It's a shame that support is abadon.
And sorry for doubting NodesConstraints. Thanks.
If anyone is having trouble with a similar case (CharaStudio crashes when selecting a parent-child object), it is recommended to try temporarily disabling ShalltyUtils.

oh,wait.
https://discord.com/channels/447114928785063977/1091473728740786236/1260153416026689536
ShalltyUtils v1.0 (now) -> v1.1 (2024.07.09)
The above update fixed the crash!
I see that Discord has the latest version, thanks!


Android Crashes: Known Device/Quantization Incompatibilities

This issue serves as a repository for tracking Android devices and specific quantizations that lead to crashes.
Please share detailed reports including device model and CPU specs, Android versions, the specific GGUF and its quantization, and stack traces if available.

Phone Model
Chipset
CPU Configuration
App Version
Model(s)

Tecno Spark 20 Pro+
MediaTek Helio G99
8-core (2x Cortex-A76 at 2.2 GHz & 6x Cortex-A55 at 2.0 GHz)
1.4.6

OnePlus 12
Qualcomm SM8650-AB Snapdragon 8 Gen 3 (4 nm)
8-core (1x3.3 GHz Cortex-X4 & 3x3.2 GHz Cortex-A720 & 2x3.0 GHz Cortex-A720 & 2x2.3 GHz Cortex-A520)
1.4.6

Motorola Edge 30 Neo
Qualcomm SM6375 Snapdragon 695 5G (6 nm)
Octa-core (2x2.2 GHz Kryo 660 Gold & 6x1.7 GHz Kryo 660 Silver)
1.5.2
madlad400

Xiaomi Redmi Note 8 Pro
Mediatek MT6785V/CC Helio G90T (12 nm)
Octa-core (2x2.05 GHz Cortex-A76 & 6x2.0 GHz Cortex-A55)
1.4.6
Whatever model

Samsung Galaxy Note10 Lite
Exynos 9810 (10 nm)
Octa-core (4x2.7 GHz Mongoose M3 & 4x1.7 GHz Cortex-A55)
1.4.6

Infinix NOTE 30
Mediatek Helio G99 (6 nm)
Octa-core (2x2.2 GHz Cortex-A76 & 6x2.0 GHz Cortex-A55)
1.4.6

If you don't know the CPU and chipset of the phone, you can use GSMArena to get the information.

I used this T5 model, trying different modes and templates: https://huggingface.co/Felladrin/gguf-q5_k_m-madlad400-3b-mt
Either I had only crashes when run without any template and <2en> prompt header for Spanish text, or unreadable <><>>>< sequences when the default template was used. I think, the llama.cpp kernel should be updated

Using Nubia z60 Ultra 16/512GB, Mag Mell IQ3_M crashes upon trying to load.
https://huggingface.co/mradermacher/MN-12B-Mag-Mell-R1-GGUF/blob/main/MN-12B-Mag-Mell-R1.IQ3_M.gguf


why not found ernie bot from baidu in llms package? Thanks

Issue you'd like to raise.
No response
Suggestion:
No response

thanks for you


Switch CRC computation from SW to HW

Description
Unfortunately, the HW CRC unit of the STM32 is a bit weird and the HW CRC32 differs from the SW version. This means that we have to notify the other endpoints about the change, and they need to implement a version that agrees with our HW version. Only then can we finally switch.

Since the HW CRC unit of the STM32 is so weird, we probably won't switch at all. Benchmarks will show how slow or fast the SW CRC is and if it is fast enough for checking a whole FM image.


Rival 110 Unable to find the requested device

MacOS
I have rivalcfg installed from pip rivalcfg-3.6.0
I see the follwing error:
W: The following mouse was found but rivalcfg was not able to open it:

mouse: SteelSeries Rival 110 (1038:1729)
error: Unable to find the requested device: 1038:1729:00

The suggested unplug re-plug did not work.

This can be caused by

An other program already connected with the mouse (like the officiel Steelseries Enine 3)
A permission issue (the current user cannot open the device).

I never tested this application on Mac OS and I have no Mac to make test, so I will not be very helpful... :(

I close this issue, but feel free to answer if you have more information


Spark fun Pro Micro

Sparkfun's ProMicro comes in 2 variations. A 3.3v and a 5v. Which should I be using?

Hi!
The pre-built firmware supports 5v/16MHz pro micros. If you order the 3.3v/8MHz you just need to change the rules.mk file to update the CPU frequency and rebuild the firmware.
So, they're all supported but I suggest you to use the 5V version. :)


Bump ep8 number

👷 Deploy Preview for resonant-mousse-b60fda processing.

Name
Link

🔨 Latest commit
4e059d92692ed469803eadb78850a11cb5421871

🔍 Latest deploy log
https://app.netlify.com/sites/resonant-mousse-b60fda/deploys/660edae481b23d0008c17c45


8261 - Avoid including Cesium3DTileSet in Picking.js

Fixes #8261

Thank you so much for the pull request @Samulus! I noticed this is your first pull request and I wanted to say welcome to the Cesium community!
The Pull Request Guidelines is a handy reference for making sure your PR gets accepted quickly, so make sure to skim that.

:x: Missing CONTRIBUTORS.md entry.

Please add yourself to the contributors file!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Can we do something similar to avoid sucking in Cesium3DTileFeature too?

@hpinkos Cesium3DTileFeature doesn't have too many imports and will unlikely have more. It might be ok to skip it.
import Color from '../Core/Color.js';
import defined from '../Core/defined.js';
import defineProperties from '../Core/defineProperties.js';

Also - add an entry to CHANGES.md.

@lilleyse fixed

Can confirm this fix reduces the build size. For future reference these were the steps @mramato suggested to verify this:

Switch to master
Edit CesiumViewer.js to create a minimal demo:

    window.CESIUM_BASE_URL = '../../Source/';

    import {
        CesiumWidget
    } from '../../Source/Cesium.js';

    function main() {
        var widget = new CesiumWidget('cesiumContainer');
    }

    main();

Run npm run makeZipFile
Run npm run buildApps
Check size of CesiumViewer.js
Do the steps above on this branch

With fix: CesiumViewer.js is 1.3 MB
Without fix: CesiumViewer.js is 1.8 MB

@Samulus there's one style comment that you missed: https://github.com/AnalyticalGraphicsInc/cesium/pull/8532/files#r365949948
After that's fixed I'll go ahead and merge.

@lilleyse rebased and annotation added

Little bit of offline miscommunication on my part, I should have been the one to merge the PR. That said, the changes do look good and I was about to merge :+1:


Take Volume Snapshot Action

Implement take snapshot custom action form:

Example on how to add a custom action form, you can see: https://github.com/apache/cloudstack-primate/pull/69/files

@utchoang cc @svenvogel tagged for next tasks to consider. Thanks.

Ping @utchoang - you may pick this one. cc @svenvogel

Ping @utchoang I'm reviewing your other PRs, maybe you can pick this one next.


Slider update

What does this PR do? Why are doing this? References?
range_slider module is updated upon review. Getter and setter of values changed to be compatible with Qt style. Demo part is separated from module and given as an example to use the slider.
Type of change
[Please delete options that are not relevant.]

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Only manually tested on OSX Mojave with python 3.7.0 and PyQt5 5.10.1.

[X] manual test - examples/slider.py

Final Checklist:

[X] My PR is the possible minimum work for the desired functionality
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works

Hello @AhmetCanSolak! Thanks for submitting the PR.

In the file examples/slider.py, following                are the PEP8 issues :

Line 9:9: E261 at least two spaces before inline comment
Line 10:80: E501 line too long (81 > 79 characters)

In the file gui/util/range_slider.py, following                are the PEP8 issues :

Line 50:80: E501 line too long (92 > 79 characters)
Line 86:80: E501 line too long (83 > 79 characters)
Line 93:80: E501 line too long (102 > 79 characters)
Line 105:80: E501 line too long (96 > 79 characters)
Line 107:80: E501 line too long (98 > 79 characters)
Line 157:80: E501 line too long (98 > 79 characters)
Line 158:80: E501 line too long (98 > 79 characters)
Line 163:80: E501 line too long (104 > 79 characters)
Line 164:80: E501 line too long (95 > 79 characters)
Line 166:80: E501 line too long (104 > 79 characters)
Line 167:80: E501 line too long (95 > 79 characters)
Line 180:80: E501 line too long (150 > 79 characters)
Line 181:80: E501 line too long (142 > 79 characters)
Line 182:80: E501 line too long (93 > 79 characters)
Line 210:80: E501 line too long (98 > 79 characters)
Line 215:80: E501 line too long (93 > 79 characters)
Line 233:80: E501 line too long (150 > 79 characters)
Line 234:80: E501 line too long (142 > 79 characters)
Line 235:80: E501 line too long (93 > 79 characters)
Line 263:80: E501 line too long (102 > 79 characters)
Line 268:80: E501 line too long (102 > 79 characters)
Line 269:80: E501 line too long (85 > 79 characters)

@AhmetCanSolak I don't really agree with the choice of using a dev branch. I realise the old "git flow" post advocates for one, but most (all?) packages in the scientific Python ecosystem seem to get by just fine with just a working master. Do you think it is necessary here? My intuition is that it will simply drive more merge conflicts.

@jni We decided on this approach because we expect there to be rapid, iterative development on the dev branch with potentially breaking changes from commit to commit. We want to separate this from the master branch with "early" releases.
This allows the master branch to be relatively stable from change to change, and grants users the ability to effectively subscribe to the upcoming release without necessarily breaking their installation.
While conflicts may be a problem, we expect dev branch contributors to be pretty experienced with both git and Python and easily able to resolve and/or adapt to them. All changes to master should be squash-merged regardless to keep the package easily git-installable, which will cover up a lot of the messiness that merge commits bring.

@kne42 if by "breaking" changes you mean that the API changes, I think this is totally fine on master, and doesn't require a new branch. This is simply the stage of development and no one should expect a master API to be stable.
If, on the other hand, you mean that stuff on the dev branch may not even be functional... Well, I don't see much use in that either, since that sort of work should happen on feature branches anyway.
Having said all this: whatever works for you guys now, since you are much more active in development than me. I hope that this will change very soon though, at which point I might be quite a bit more opinionated about the branching model. =P

I agree with Kira, we had a few examples of people wanting to try Napari only to be temporarily discouraged by a broken master. I would suggest we keep master for releases and develop on master.
I like the idea of topic branches, which can be a good alternative to a dev branch...

@jni thank you for your comment.
I think the traditional git flow is perfect from many perspectives and we have some cases as @royerloic explained for motivation to keep branches separated. I know majority(almost all) of the python packages does not follow such good practices, especially the ones in scientific community :) it is worth to question, I believe.
We are also planning to use master as a release branch which I believe will be so helpful for the git-based plugins of Napari.

@AhmetCanSolak sure, happy for it to be questioned, but I'll point out that the SciPy "master-only" model came after Fernando Perez and others questioned whether git-flow was necessary, or just overhead. Many of these projects started out using git-flow then got to the point that dev could nicely act as master anyway. Specifically, if we have good test coverage and process, master should never be broken. dev to me seems to encourage breaking things.
I also don't like the sound of squashing everything in between releases. A clean history is absolutely critical for finding regressions and when things broke.


no-unpublished-require throws a TypeError when "." or "./" is required

The rule n/no-unpublished-require sometimes throws a TypeError when require(".") or require("./") occurs in the code.
This only happens under certain circumstances:

The node environment is set
The file that contains the require is included in the files field in package.json.
There is no file named index.js, or if package.json defines a different file in the main field, that file does not exist.

The smallest repro I've come up with:
package.json
{
  "files": [
    "*.js"
  ],
  "devDependencies": {
    "eslint": "latest",
    "eslint-plugin-n": "latest"
  }
}

.eslintrc
{
    "env": {
        "node": true
    },
    "plugins": [
        "n"
    ],
    "rules": {
        "n/no-unpublished-require": "error"
    }
}

foo.js
require('.');

Running npm installand then npx eslint . in the project folder prints an error message like this:
Oops! Something went wrong! :(

ESLint: 8.22.0

TypeError: path must not be empty
Occurred while linting /home/user/my-project/foo.js:1
Rule: "n/no-unpublished-require"

DEMO LINK

I could try to fix this if desired.

sounds it should report an eslint errror in this case - it will throw an 'module not found' error if you run your code.

Yes, my code doesn't work of course. But the rule should report the linting problem instead of throwing an error.

I think the root of the problem is this check where npmignore.match is being called with an argument that is possibly an empty string, resulting in the empty string being passed to ignore that produces the TypeError.
https://github.com/weiran-zsd/eslint-plugin-node/blob/d7b975a07e1b876ca2c75597d054a81564b25685/lib/util/check-publish.js#L52-L54
That's because toRelative returns an empty string when called with an argument that is the same as the package directory. And require('.') resolves to the package directory when called by a file in that location.
This could be probably fixed by making sure that npmignore.match is never called with an empty string. I will try to come up with a test case, and I'll create a PR if my fix works.


Problem with D&D in W7P 64b (VMware)

Hello, I'm quite sure thats not a Component issue, because it works fine for me under w10 (non VMware).
But with this configuration (see title) I'm not able to perform drag&drop. I'm using your demo 'SimpleTarget' (but its general behavior) and when I drag file (from explorer) then I can't drop them to the form just because its disabled ... Icon disabled as well (you know, the crossed circle). I spend half day but I can't find the solution.
Note: The SimpleTargetDemo is not using elevated privileges.
thanks in advice, Ondrej

do you have it checked with current sources?

ok, reopen this issue, if it still exists.


Cognitoidentityprovider can't recognize new parameters during update

What happened?
When creating a resource in the cognitoidentityprovider group it is not possible to add parameters after the resource has been created. They are not recognized as a change in the spec.

How can we reproduce it?
Create a UserPool with minimal values. Add a new value (e.g. AccountRecoverySetting). It won't update the resource.
Create:
apiVersion: cognitoidentityprovider.aws.crossplane.io/v1alpha1
kind: UserPool
metadata:
  name: example
spec:
  forProvider:
    region: us-east-1
    poolName: examplePool
  providerConfigRef:
    name: example

Update with:
apiVersion: cognitoidentityprovider.aws.crossplane.io/v1alpha1
kind: UserPool
metadata:
  name: example
spec:
  forProvider:
    region: us-east-1
    poolName: examplePool
    accountRecoverySetting:
      recoveryMechanisms:
        - name: verified_email
          priority: 1
  providerConfigRef:
    name: example

What environment did it happen in?
All versions

works as of https://github.com/crossplane-contrib/provider-aws/pull/1533

Closing, since this seems to be fixed in #1533.


Auto Login Fix

Fixed Auto Login and Modified Docker files to support Auto Login on startup.
Modified README.md

hey @koushikmln are you going to update this pr. could you also rebase before editing

I'll try and close it next week. Its been pending for too long.


Edited and modified license

Examine the license for your project and consider whether this is the choice you want to make, or whether you want to change the license. Discuss and reason the license choice by opening issues in both Python and R repositories. As it is likely to be a very similar discussion for both projects, one of these issues can just link to the other issue where it is thoroughly discussed

We are currently using the MIT License in both our R and Python package. In my opinion, I think the MIT License works best. For future use, our functions could be modified for other applications.
Someday in the future, we might come back to this code to use for later packages or codes and so keeping it simple and being open and permissive such as MIT License sounds good to me!


fix: virus column (list) is unhashable

fix a bug introduced by https://github.com/AllenNeuralDynamics/foraging-behavior-browser/pull/89 where virus column is unhashable when determining the columns for "groupby" in the x-y view.

The x-y view should be usable within 20 mins once this PR is merged @bwtan-allen

@bwtan-allen @rachelstephlee  this quick bug fix is ready to review


Problems building : Error in conformMethod .. cannot be in sig

Running into the following when issuing either

devtools::install_github('rstudio/sparklyr')
or
install.packages("sparklyr")

** inst
** tests
** preparing package for lazy loading
Error in conformMethod(signature, mnames, fnames, f, fdef, definition) :
  in method for ‘sqlParseVariables’ with signature ‘conn="spark_connection"’: formal arguments (conn = "spark_connection", sql = "spark_connection", ... = "spark_connection") omitted in the method definition cannot be in the signature
Error : unable to load R code in package ‘sparklyr’
ERROR: lazy loading failed for package ‘sparklyr’
* removing ‘/home/mtz/R/x86_64-redhat-linux-gnu-library/3.3/sparklyr’
Error: Command failed (1)

This is on RHEL 7.3 running R version 3.3.2
I did notice this:  https://github.com/rstudio/sparklyr/issues/513  and installed DBI in CRAN as a result.  No change.
Thanks!

Seems to be the same basic problem as I posted this morning (clarified the title just now as it might not have been evident):
https://github.com/rstudio/sparklyr/issues/538

@Nova-Boy @HugoHehn Tahnk you, patch to sparklyr as 0.5.3 was submitted and accepted to CRAN this morning, it might take up to a day to replicate in CRAN, but for most users, reinstalling should work as expected now. There was a breaking change in DBI 0.6 that required a patch in sparklyr, all should be good now.

Thanks! Confirming that it looks good.  I'm able to install 0.5.3 w/o issue.

Thanks for confirming!


Make app looks good on mobile

Clear and concise description of the problem

We are currently able to visit the site even on mobile, but it doesn't look good.
Suggested solution

Make app looks good with left sidebar and generated code in the middle.
Alternative
N/A

Additional context

Is this GitHub bug? Not closing automatically?

Interesting...
but on the right we see:

Successfully merging a pull request may close this issue.
MAY close... :)) so
it's might be a bug)


[DOC-463] test main branch

Description
(Please describe the changes in this PR for reviewers, motivation, rationale - mandatory)
This PR wil never be merged
Purpose of this branch is to be the base for any new branch created to test the real docs toolchain workflow

Upstream PR
The following PR deals with the following generated content for the following versions:

3.10: arangodb/enterprise-preview:3.10-nightly
3.11: arangodb/enterprise-preview:3.11-nightly
3.12:
devel:

/generate

/generate

/generate

/generate

/generate

/generate-commit

/generate-commit


Changes in commits should support tree structure

Testing #3488
When I expand a commit I would have expected to see a tree structure, given my setting githubPullRequests.fileListLayout is tree:

Alternatively I would have expected to see the path as description segment next to the label, independent of that setting.

Hm, it looks like I was maybe using the non-pre-release version...

No, I see no tree structure using v0.41.2022042509

The new build with the change wasn't out yet. After you update to v0.41.20220426* do you see the tree structure?


Pagespeed did not respect preserve URL

System:
Linux prestabebe 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 GNU/Linux
Bitnami Prestashop Stack + Varnish
PHP 5.5.30 (cli) (built: Jan  1 2016 01:42:53)
Copyright (c) 1997-2015 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2015 Zend Technologies
with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2015, by Zend Technologies
Server version: Apache/2.4.18 (Unix)
Server built:   Jan  1 2016 01:32:00
Pagespeed config : http://pastebin.com/XvnCsxVt
Although I define the pagespeed to respect the URL, it still append the pagespeed.ic.Hash.
Am I missing something?
GTMetrix : https://gtmetrix.com/reports/bebehouz.my/iQ7kwt5w
404 URL : http://bebehouz.my/20-home_default/xprinted-chiffon-dress.jpg.pagespeed.ic.y54eacAaaG.jpg
Working URL : http://bebehouz.my/20-home_default/xprinted-chiffon-dress.jpg

I noticed this response-header in the HTML response for the index with the unexpected .pagespeed. urls:
X-Cache: HIT
Could you purge any cdn- and http- caches and see if that fixes the problem? I think html pages are being cached which where served with an older pagespeed configuration (which at that point did not preserve urls).

I think you're right. I purge both Varnish and Cloudflare. It only works for awhile and then same thing happen. Latest right. How this happen and how I can prevent it? Initially I thought the ResourceOptimization cause this and I already turned it off.

@m0d0  I can no longer reproduce the problem by testing myself or via gtmetrix. Can you?

I actually have 2 instance testing CF, Varnish, Pagespeed with Apache. Now, I have changed it to another instance, Digital Ocean. Previously, Google Cloud.  I have compared it side by side and there is significant differences. I've spent more than 100 hours to get things right - tend to add here and there thus lead to this differences.
Varnish : http://pastebin.com/07Q7m4rJ
Pagespeed : http://pastebin.com/8DYKjf80
Previously404Pagespeed :  http://pastebin.com/XvnCsxVt
Previously404Varnish : http://pastebin.com/Cb7wwzzV
Any comments?

@m0d0 I'm not sure what you are asking, could you clarify?


SelectField highlight overflows in 0.15.0-alpha.2 if width set

Problem Description

Create a Select Field explicitly specifying a width: <SelectField style={{width: 400}}> with some MenuItem children
Open the drop down menu, and hover over any of the MenuItem
The highlight of the MenuItem overshoots the bounds of the drop down menu to the right

Versions

Regression in 0.15.0-alpha.2
Works in 0.14.4


chore(typings): Enabled noImplictAny

With this change compliation time and performance is improved

@kwonoj  This was the quick way, there might a few places where the formatting, or in some cases the variable names used in method signatures that have changed.  If I need to reverse those let me know and I'll make a pass at it shortly.

Appreciate for effort :) few copy-paste from original PR

would you able to align commit message as same as others, starts with no-capital
npm script package.json should be updated as well as tsconfig.json

I'll try to come up with possible cases of suppressImplicitAnyIndexErrors in our codebase meanwhile..

done! :smile:

would you able to align commit message as same as others, starts with no-capital
npm script package.json should be updated as well as tsconfig.json

Build is erroring for suppressImplicitAnyIndexErrors in a few places (that I wasn't seeing, which is strange but not super important here).
Do we want to suppress those messages, or define the types so they don't happen?

Build is erroring for suppressImplicitAnyIndexErrors in a few places

: Yes, those are errors I could see while I work on this, reason of suggestion for enabling suppressImplicitAnyIndexErrors. I don't see lot of values to enforce type for those indexers in our codebases, i.e if (observerOrNext[rxSubscriber]) {, ish[SymbolShim.observable], etcs.. (but would like to hear your opinion also if you think it'd benefit to have type for those)

I don't see much value in typing them, there aren't a lot of cases where Rx is using objects as a dictionary or similar (not when there is map, etc).
I will update to suppress those messages then.

I'm seeing some of function signatures are changed not related to implicit any, specifically projection function definition accepts to return Promise. Most of current operator implementation as far as I recall it does not checks projected result is promise or observable. I think this is kind of out-of scope changes requires discussion (will we support those behavior or not?) would like to suggest to not to change those signatures in this PR and create issue if it's necessary.

They are technically supported today, because all of the methods call through to subscribeToResult which handles everything under the sun.

Correct in sense of availability, but still I'd like to suggest it to take out as separate discussion if we want to support those as interface. As same as original PR, thinking about size of this changes limiting scope would be better, or discussion would be expanded.

I think changes are now good to be checked in. Is there additional suggestion @luisgabriel ?

:balloon: :tada: :balloon:

Also cc @blesh to see if there's any suggestions around. @blesh , I think changes are good now and waiting @luisgabriel 's response if there's additional suggestion from him. If there isn't, I'll check this in around tomorrow. Meanwhile if you have any suggestions, would be appreciate to have it. :)

I'll also rebase if #1065 goes in first, as it will probably have a small
conflict.
On Wed, Dec 16, 2015 at 3:02 PM, OJ Kwon<EMAIL_ADDRESS>wrote:

Also cc @blesh https://github.com/blesh to see if there's any
suggestions around. @blesh https://github.com/blesh , I think changes
are good now and waiting @luisgabriel https://github.com/luisgabriel 's
response if there's additional suggestion from him. If there isn't, I'll
check this in around tomorrow. Meanwhile if you have any suggestions, would
be appreciate to have it. :)
—
Reply to this email directly or view it on GitHub
https://github.com/ReactiveX/RxJS/pull/1077#issuecomment-165226494.

@kwonoj I'll give another look. But I think it's good to go. ;)
Very good work, @david-driscoll! My suggestion to future contributions is to do the work incrementally with more self-contained commits/PRs. It can speed up a lot the review process. ;)

Cool, thanks @luisgabriel

work incrementally with more self-contained commits/PRs

: I agree to this in general, but I also think this was bit exceptional case since enabling compiler flag will require change all file at once. :)

@david-driscoll , would you able to rebase this PR? #1065 landed first..

I can later this evening
On Wed, Dec 16, 2015 at 6:24 PM OJ Kwon<EMAIL_ADDRESS>wrote:

@david-driscoll https://github.com/david-driscoll , would you able to
rebase this PR? #1065 https://github.com/ReactiveX/RxJS/pull/1065
landed first..
—
Reply to this email directly or view it on GitHub
https://github.com/ReactiveX/RxJS/pull/1077#issuecomment-165282607.

--
Thanks,
David

such a huge work!

@kwonoj rebased.

@kwonoj @david-driscoll Just finished to review it. Comments are inline. Most of them are style-related.

LGTM.
Thanks, @david-driscoll!

Cool, I'll check this in around late today to this weekend, allow some time buffer to see any other suggestions around considering given size of PR.

@kwonoj I think it'd be better if we could merge this PR before the change @trxcllnt and @blesh are discussing on #1099 to avoid more rebasing conflicts.
What do you guys think?

I haven't had a chance to check it, but it's possible it's not needed
anymore.
On Wed, Dec 23, 2015 at 2:07 PM Luís Gabriel Lima<EMAIL_ADDRESS>wrote:

@kwonoj https://github.com/kwonoj I think it'd be better if we could
merge this PR before the change @trxcllnt https://github.com/trxcllnt
and @blesh https://github.com/blesh are discussing on #1099
https://github.com/ReactiveX/RxJS/pull/1099 to avoid more rebasing
conflicts.
What do you guys think?
—
Reply to this email directly or view it on GitHub
https://github.com/ReactiveX/RxJS/pull/1077#issuecomment-166972431.

--
Thanks,
David

Just a note: This PR should probably wait for @trxcllnt's changes (code reviewed in branch and PR incoming shortly) to the Subscription scheme to land. They're big changes, so it may mean a painful refactor of this PR... however, they're important changes to internals, so they take precedence.

Agreed with @blesh here. It wasn't intended to make this PR's check in delayed though, now it's overlaps with major refactoring to subscriptions - in this case, I'd like to let those changes land first prior to this. (Also https://github.com/ReactiveX/RxJS/pull/1097 as well @luisgabriel , current assumption's those PR's nearly orthogonal to subscription changes, but want to be sure).

Ok, no problem. I was assuming that it would be less painful to adapt @trxcllnt's changes since merging this one after could also require adding explicit typing on the new code besides solving the conflicts.

@david-driscoll the effort that went into this PR is clearly enormous, so thanks for that. Apologies if rebasing from #1106 is a major headache. I'll do the legwork to reconcile with this PR if necessary.

#1106 's now landed, @david-driscoll would you able to rebase this? I'll take this as priority to check in once it's rebased, given size of changes delaying it more would create more change conflicts between PRs. (Just note : @luisgabriel , I'll take #1097 as second order after this one. Let me know if you have any suggestions).

@kwonoj Ok, no problem from my side. I'll try to rebase this patch tomorrow to see if I can help @david-driscoll to update this PR.

@david-driscoll I've rebased your patch on the current master. You can find it in this branch: https://github.com/luisgabriel/RxJS/tree/pr-1077
It was less painful than I thought. ;)

The sooner we get the rebased version in the PR (or PR'ed elsewhere) the sooner we can review the changes again after the rebase and merge this.

Marking "Blocked" as it's awaiting rebase.

Will get working on this is in the next day or two, I've been enjoying some
much needed time off :)
On Mon, Jan 4, 2016 at 3:14 PM Ben Lesh<EMAIL_ADDRESS>wrote:

Marking "Blocked" as it's awaiting rebase.
—
Reply to this email directly or view it on GitHub
https://github.com/ReactiveX/RxJS/pull/1077#issuecomment-168791363.

--
Thanks,
David

@david-driscoll I recommend you use https://github.com/luisgabriel/RxJS/tree/pr-1077 as a base for updating this PR. A lot of the conflicts are already solved in this branch.

:+1: also @blesh, who's the masochist now? https://github.com/ReactiveX/RxJS/pull/517#issuecomment-147892560

@robwormald haha. Yeah, that was before I knew it would reduce the amount of time I'd have to wait for builds. :package:

@luisgabriel sorry for the delay, life happens.  Now fully rebased and building correctly.

@david-driscoll No problem at all. Thank you for the effort! ;)

LGTM :+1:

Cool, I'm checking in this.. (finally!)

Merged with db7f0b1. Appreciate @david-driscoll  for this huge effort, and also @luisgabriel takes effort to review this changes too.


Fix typo where -> were

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Typo fix, no change to functionality

Nice, thanks!


Page is vague about how to get the 'key' value

Following the instructions for setting up the authorization file under Create the authorization file send you to another page, this one https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-authenticate-service-principal-powershell.
This page could use some clarification to make it more obvious how to retrieve the value we should put in the auth file on the line
key=<authentication-key>

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

ID: 5d29559e-6487-e3b8-0cf4-82a8e04dafa0
Version Independent ID: 2dfc827f-ed3a-dea9-e5b8-7668f8e8188e
Content: Deploy a VM using C# and a Resource Manager template - Azure Windows Virtual Machines
Content Source: articles/virtual-machines/windows/csharp-template.md
Service: virtual-machines-windows
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

IMHO the docs here are much easier to follow for the same sort of operation.
https://docs.microsoft.com/en-us/dotnet/azure/authentication
Maybe the link from the page could be changed to point here?

@1RedOne Thanks for the feedback! The article that contained the link is being removed until it can be reworked.
@Karishma-Tiwari-MSFT Can you redirect this feedback to the owner of https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-authenticate-service-principal-powershell so they can look at https://docs.microsoft.com/en-us/dotnet/azure/authentication and maybe simplify the instructions in their article?

#reassign @Karishma-Tiwari-MSFT

I have shared the feedback with the team internally.
Thanks for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.

Adding @rwike77, the owner of the below doc for their awareness.
https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-authenticate-service-principal-powershell