Unable to make HPA created by KEDA to work

Discussed in https://github.com/kedacore/keda/discussions/6154

Originally posted by rishabhgargg September 12, 2024
I am using KEDA 2.15.1 in EKS (v1.24.17)
I have installed KEDA from helm chart from kedacore-charts version 2.15.1
I already had prometheus stack installed, so I deleted the 'apiserver.yaml' from the templates/metrics-server directory (Please let me know if there is a better approach than this to make the two of these work together in same kubernetes cluster)
I also disabled certificate generation by setting certificates.autoGenerated: false in values.yaml.
Now, the services are up and running perfectly fine without any errors (shown below).

I am deploying a ScaledObject that uses promtheus scaler to scale my StatefulSet. The YAML for that is:
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: set1
  namespace: set1
  labels:
    deploymentName: set1-cloud
  annotations:
    scaledobject.keda.sh/transfer-hpa-ownership: "true"  # Transfer HPA ownership to KEDA
spec:
  maxReplicaCount: 64
  pollingInterval: 600
  advanced:
    horizontalPodAutoscalerConfig:
      name: set1  # Name of the HPA resource
  scaleTargetRef:
    kind: StatefulSet
    name: set1-cloud
  triggers:
    - type: prometheus  # Use Prometheus trigger
      metadata:
        serverAddress: http://prometheus-kube-prometheus-prometheus.prometheus.svc.cluster.local:9090  # URL for Prometheus service in cluster
        metricName: pod_replicas  # Use the pod_replicas metric
        threshold: "1"  # Set threshold to 1 (we will rely on the query to dictate the scale)
        query: pod_replicas # Directly query the pod_replicas metric value

Here, I was trying to achieve that, whatever the value metric returns, that many pods must be running for that statefulset.
But, after deploying this, the HPA created on doing kubectl describe hpa gives this:
PS C:\Users\rishabh.garg> kubectl describe hpa set1 -n set1
Warning: autoscaling/v2beta2 HorizontalPodAutoscaler is deprecated in v1.23+, unavailable in v1.26+; use autoscaling/v2 HorizontalPodAutoscaler
Name:                                      set1
Namespace:                                 set1
Labels:                                    app.kubernetes.io/managed-by=keda-operator
                                           app.kubernetes.io/name=set1
                                           app.kubernetes.io/part-of=set1
                                           app.kubernetes.io/version=2.15.1
                                           deploymentName=set1-cloud
                                           scaledobject.keda.sh/name=set1
Annotations:                               <none>
CreationTimestamp:                         Wed, 11 Sep 2024 22:27:35 +0530
Reference:                                 StatefulSet/set1-cloud
Metrics:                                   ( current / target )
  "s0-prometheus" (target average value):  34m / 1
Min replicas:                              1
Max replicas:                              64
StatefulSet pods:                          16 current / 16 desired
Conditions:
  Type            Status  Reason                   Message
  ----            ------  ------                   -------
  AbleToScale     True    SucceededGetScale        the HPA controller was able to get the target's current scale
  ScalingActive   False   FailedGetExternalMetric  the HPA was unable to compute the replica count: unable to get external metric set1/s0-prometheus/&LabelSelector{MatchLab
els:map[string]string{scaledobject.keda.sh/name: set1,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: the server could
 not find the metric s0-prometheus for
  ScalingLimited  True    TooFewReplicas           the desired replica count is less than the minimum replica count
Events:
  Type     Reason                        Age                    From                       Message
  ----     ------                        ----                   ----                       -------
  Warning  FailedComputeMetricsReplicas  42m (x12 over 44m)     horizontal-pod-autoscaler  invalid metrics (1 invalid out of 1), first error is: failed to get s0-prometheus
external metric: unable to get external metric set1/s0-prometheus/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: set1,},MatchExpressions:[]LabelSe
lectorRequirement{},}: unable to fetch metrics from external metrics API: the server could not find the metric s0-prometheus for
  Warning  FailedGetExternalMetric       4m35s (x161 over 44m)  horizontal-pod-autoscaler  unable to get external metric set1/s0-prometheus/&LabelSelector{MatchLabels:map[s
tring]string{scaledobject.keda.sh/name: set1,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: the server could not find
 the metric s0-prometheus for
PS C:\Users\rishabh.garg>

I am not able to understand that why it is trying to query s0-prometheus metric instead of pod_replicas metric, which actually returns a value (successfully tested in prometheus UI)?
Right after applying ScaledObject YAML, when I try to see via kubectl edit ScaledObject I get this, in which somehow in externalMetricNames it mentions s0-prometheus
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: >
      {"apiVersion":"keda.sh/v1alpha1","kind":"ScaledObject","metadata":{"annotations":{"scaledobject.keda.sh/transfer-hpa-ownership":"true"},"labels":{"deploymentName":"set1-cloud"},"name":"set1","namespace":"set1"},"spec":{"advanced":{"horizontalPodAutoscalerConfig":{"name":"set1"}},"maxReplicaCount":64,"pollingInterval":600,"scaleTargetRef":{"kind":"StatefulSet","name":"set1-cloud"},"triggers":[{"metadata":{"metricName":"pod_replicas","query":"pod_replicas","serverAddress":"http://prometheus-kube-prometheus-prometheus.prometheus.svc.cluster.local:9090","threshold":"1"},"type":"prometheus"}]}}
    scaledobject.keda.sh/transfer-hpa-ownership: 'true'
  creationTimestamp: '2024-09-11T20:51:33Z'
  finalizers:
    - finalizer.keda.sh
  generation: 2
  labels:
    deploymentName: set1-cloud
    scaledobject.keda.sh/name: set1
  managedFields:
    - apiVersion: keda.sh/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:finalizers:
            .: {}
            v:"finalizer.keda.sh": {}
          f:labels:
            f:scaledobject.keda.sh/name: {}
        f:spec:
          f:advanced:
            f:scalingModifiers: {}
      manager: keda
      operation: Update
      time: '2024-09-11T20:51:33Z'
    - apiVersion: keda.sh/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        f:status:
          .: {}
          f:conditions: {}
          f:externalMetricNames: {}
          f:hpaName: {}
          f:lastActiveTime: {}
          f:originalReplicaCount: {}
          f:scaleTargetGVKR:
            .: {}
            f:group: {}
            f:kind: {}
            f:resource: {}
            f:version: {}
          f:scaleTargetKind: {}
      manager: keda
      operation: Update
      subresource: status
      time: '2024-09-11T20:51:33Z'
    - apiVersion: keda.sh/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:annotations:
            .: {}
            f:kubectl.kubernetes.io/last-applied-configuration: {}
            f:scaledobject.keda.sh/transfer-hpa-ownership: {}
          f:labels:
            .: {}
            f:deploymentName: {}
        f:spec:
          .: {}
          f:advanced:
            .: {}
            f:horizontalPodAutoscalerConfig:
              .: {}
              f:name: {}
          f:maxReplicaCount: {}
          f:pollingInterval: {}
          f:scaleTargetRef:
            .: {}
            f:kind: {}
            f:name: {}
          f:triggers: {}
      manager: kubectl-client-side-apply
      operation: Update
      time: '2024-09-11T20:51:33Z'
  name: set1
  namespace: set1
  resourceVersion: '410711161'
  uid: 4ddb0c99-666d-4d58-80a5-fc3018c82554
  selfLink: /apis/keda.sh/v1alpha1/namespaces/set1/scaledobjects/set1
status:
  conditions:
    - message: ScaledObject is defined correctly and is ready for scaling
      reason: ScaledObjectReady
      status: 'True'
      type: Ready
    - status: Unknown
      type: Active
    - status: Unknown
      type: Fallback
    - status: Unknown
      type: Paused
  externalMetricNames:
    - s0-prometheus
  hpaName: set1
  lastActiveTime: '2024-09-11T20:51:33Z'
  originalReplicaCount: 16
  scaleTargetGVKR:
    group: apps
    kind: StatefulSet
    resource: statefulsets
    version: v1
  scaleTargetKind: apps/v1.StatefulSet
spec:
  advanced:
    horizontalPodAutoscalerConfig:
      name: set1
    scalingModifiers: {}
  maxReplicaCount: 64
  pollingInterval: 600
  scaleTargetRef:
    kind: StatefulSet
    name: set1-cloud
  triggers:
    - metadata:
        metricName: pod_replicas
        query: pod_replicas
        serverAddress: >-
          http://prometheus-kube-prometheus-prometheus.prometheus.svc.cluster.local:9090
        threshold: '1'
      type: prometheus
```</div>

Please don't open issue and a discussion for the same problem 🙏


Automatic data model update

This update to the data model documentation was automatically created from tonight's O2 dev branch.

@pbuehler Now it looks fine! :)


feature: discover migrations

TL;DR
This PR allows developers to specify whether their package should auto-discover all migrations in their package without having to specify individual file names.
Context – What problem does this solve?
For smaller packages with maybe a handful of migrations, calling hasMigration multiple times (or just hasMigrations once) is trivial and non-invasive.
However for larger packages, or for people using this tool in larger projects (e.g. registering composer modules in a large-scale production application), having to specify the name of every migration that is within a package or module becomes arduous and prone to mistakes
For example, newer developers will not necessarily always remember that each migration must be manually registered in a service provider (especially since Laravel's functionality is to auto-discover migrations).
Solution
This PR allows developers to choose whether or not their package "auto-discovers" its own migrations, by expanding the Package API with a new discoversMigrations method.
Developers and teams can now simply build a new package with as many migrations as they like without needing to remember to manually register the migration:
$package
    ->name('your-package-name')
    ->discoversMigrations();

When this is called, we will assume this is the default and that any calls to hasMigration or hasMigrations can safely be ignored. (If not, then in some scenarios, this would cause duplicate migrations and errors after publishing migrations and running artisan migrate).
$package
    ->name('your-package-name')
    ->hasMigration('create_my_package_tables') // Ignored
    ->hasMigrations(['my_package_tables', 'some_other_migration'])  // Ignored
    ->discoversMigrations();

I've also updated the hasMigrations to call discoversMigrations when no migration names are provided

Maybe add a (default) parameter of database/migrations so that you could technically discover it from elsewhere.

Thanks!


[SPARK-39805][SS] Deprecate Trigger.Once and Promote Trigger.AvailableNow

What changes were proposed in this pull request?
This PR proposes to deprecate Trigger.Once and suggest Trigger.AvailableNow as a replacement.
This PR also tries to replace Trigger.Once to Trigger.AvailableNow in the test code as well, except the cases Trigger.Once is used intentionally.
Why are the changes needed?
Trigger.Once() exposes various issues, including:

weak guarantee of the contract

This is the javadoc content of Trigger.Once:

A trigger that processes all available data in a single batch then terminates the query.

Spark does not respect the contract when there is "uncommitted" batch in the previous run. It really works as the name represents, "just run a single batch", hence if there is "uncommitted" batch, Spark will execute the "uncommitted" batch and terminate without processing new data.

scalable issue on batch

This is the main rationalization we introduced Trigger.AvailableNow.

huge output latency for stateful operator due to the lack of no-data batch

Since Trigger.Once executes the single batch and terminates, the processing for watermark advancement is deferred to the next execution of the query, which tends to be multiple hours or even day(s).
Does this PR introduce any user-facing change?
Yes, end users will start to see the deprecation message when they use Trigger.Once. The deprecation message guides the end users to migrate to Trigger.Available, with the rationalization on migration.
How was this patch tested?
Existing UTs

Github Action only fails with Run TPC-DS queries with SF=1
We can retrigger once the PR gets reviewed and getting approval.

cc. @zsxwing @viirya @xuanyuanking @bozhang2820

ParquetIOSuite.SPARK-7837 Do not close output writer twice when commitTask() fails
Hit this again. Will retrigger.

It only failed in TPC-DS (again) which does not run any streaming query AFAIK. I'm ignoring it.

Thanks! Merging to master.


"Unused" warning shown for type parameters

When declaring type parameters that are not used in the class body, Ceylon compiler shows an "unused declaration" warning. Type parameters that are not used in class body are called phantom types, and they have several benefits. My current workaround now is simply using suppressWarnings("unusedDeclaration"), but I don't think unused invariant type parameters should have a warning at all.

FTR, I've wondered about this several times. I agree I should probably fix this.

@ilmoeuro I've made the requested change.


Allow karmabot to store notes for users, both in private and public

I added a new private and public command note with three subcommands:

note add <message> stores a new note in the database with id, user_id as fk, timestamp and note message
note list lists all notes from the db for the current user in the format  note from : , with linebreak between each note
note del <id> deletes note with  from database.

Added some tests and tried to be as failsave as possible.

Awesome, thanks @pmayd looking forward using this feature soon.


CloudEvents content doesn't reflect correct emitter namespace and subject type

Report
we emit an event like this:
{
    "specversion" : "1.0",
    "type" : "com.cloudeventsource.keda",
    "source" : "/{cluster-name}/{namespace}/keda",
    "subject" : "/{cluster-name}/{namespace}/workload/{scaledobject-name}",
    "id" : "<guid>",
    "time" : "2018-04-05T17:31:00Z",
    "datacontenttype" : "application/json",
    "data" : {
      "reason":"<event-reason>",
      "message":"<event-message>"
   }
}

The source is /{cluster-name}/{namespace}/keda but the emitter is /{cluster-name}/{keda-namespace}/keda because it's KEDA who emits the event and not the resource itself, who is the subject indeed.
In the same way, the subject should be /{cluster-name}/{namespace}/scaledobject/{scaledobject-name} instead of /{cluster-name}/{namespace}/workload/{scaledobject-name} because now we are emitting events only for ScaledObjects, but we plan to extend to other resources, and workload doesn't make sense at that point.
{
    "specversion" : "1.0",
    "type" : "com.cloudeventsource.keda",
    "source" : "/{cluster-name}/{keda-namespace}/keda",
    "subject" : "/{cluster-name}/{namespace}/{object-type}/{object-name}",
    "id" : "<guid>",
    "time" : "2018-04-05T17:31:00Z",
    "datacontenttype" : "application/json",
    "data" : {
      "reason":"<event-reason>",
      "message":"<event-message>"
   }
}

@SpiritZhou WDYT?

I agree. I think it's clearer.


Windows-msvc is slower than Linux or macOS (no asm)

I'm using libz-sys in a multithreaded PNG encoder and found that my Windows builds run slower than Linux or macOS builds; much of the difference seems to be down to how zlib is built.
For my test compressing a very large screenshot on a single thread:

static version: 671ms
vcpkg-built zlib1.dll: 646ms
manually-built zlib1.dll with asm: 596ms
Linux version on WSL: 555ms

(Something like 2/3 of the total runtime is in deflate.)
Using the vcpkg version (with VCPKGRS_DYNAMIC=1) seems to give a small boost of a few percent, but a bigger win comes from manually rebuilding zlib1.dll with assembly optimizations and dropping that in over the vcpkg version. This gets my whole run going almost as fast as the Linux version.
Would it be worth special-casing the msvc builds to pull in the x86/x64 assembly bits? I'm not sure how hard that is with the cc crate build framework (they're extra .asm files that need to be run through the assembler into .obj files, not inline assembler in .c files). Or should there be an easier way to drop in a customized zlib build if you need it?
(And thanks for the crate -- it gave me exactly the low-level interface into zlib I needed to create a stream stitched together from work done on multiple threads!)

Oh dear, thanks for the report! The cc crate does indeed have support for simply feeding it assembly files (and it takes care of compliation on platforms and making sure the objects make their way to the linker)
I didn't know though that zlib had asm files to build! What files were you thinking we should build?

Cool! The .asm files for each platform are hiding under "contrib" which made them a bit invisible to me at first ;) but there's a note in the win32 Makefile listing how to enable them there.
Need to set defines on the C compiles:

-DASMV
-DASMINF

Files for x64:

contrib\masmx64\inffasx64.asm
contrib\masmx64\gvmat64.asm
contrib\masmx64\inffas8664.c

Files for x86:

contrib\masmx86\inffas32.asm
contrib\masmx86\match686.asm

The inffas* bits should speed up inflate decompression, while the *mat* bits speed up deflate's longestMatch function during compression.

Ah ok, cool! Are we sure it's a good idea to use those? There's a relatively scary comment indicating that they're not necessarily recommended for use

@brion We'd also be happy to accept PR's in vcpkg to enable the ASM!

Ah ok, cool! Are we sure it's a good idea to use those? There's a relatively scary comment indicating that they're not necessarily recommended for use

Hmm, after more careful poking the Debian/Ubuntu package doesn't appear to be using the gcc asm either, unless it's triggering via some means I don't understand (Deb packages confuse me!) but it's sure faster... Not 100% sure what's the best course of action here.

Perhaps an off-by-default feature could be included? That way users could determine if the asm works for them?

Sounds good -- then can opt in easily. :)

@brion want to test out https://github.com/alexcrichton/libz-sys/tree/asm and see if it works for you?

@alexcrichton works great, I see a definite improvement of several percent in total PNG encoding throughput when enabling the 'asm' feature on Windows, both x86_64 and x86. :)

Ok thanks! I've pushed that to master now


Abort vs. Time limit

After commanding Solve, is there a way to command solver to abort solving?
Or is this only with pre-determined time limit, or via the operating system.

Which solver are you using?

VRP version 6.X

/// Callback-based search limit. Search stops when limiter returns true; if
/// this happens at a leaf the corresponding solution will be rejected.
SearchLimit* MakeCustomLimit(std::function<bool()> limiter);


Remove .cargo/config, specify libsodium-sys path in Cargo.toml

This makes using sodiumoxide from git easier.
Fixes #155.

Does this work even if you add sodimoxide as a dependency from crates.io?

Of course. See cargo doc here.
There are many projects out there specifying deps this way, e.g., openssl, gtk, (and my noise implementation 😴).


Add Converter extension

Description
An elegant tool for converting various kinds of data.
Screencast
Number

String

IP

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed in the media folder

Hi @Sunnyyoung 👋
Thanks for your contribution 💯
Did you see that an extension with almost every feature in this already exists, it's called Toolbox – could it be an idea to migrate your features inside that extension instead?

Ah yes, I saw that, and I am going to close this pull request, because I have no time work on it recently. 🫤


Android build fails because of jcenter

Description
Hi,
I have a react native project I was able to build until some days ago, now the build fails because it is not able to resolve anymore the dependency on jcenter, for example I get this kind of errors
https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-stdlib/1.2.71/kotlin-stdlib-1.2.71.jar
I tried to modify the build.gradle and replace the jcenter() with mavenCentral(), but I got the same error
Version
0.64.0
Output of npx react-native info
System:
OS: Windows 10 10.0.19044
CPU: (6) x64 Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
Memory: 6.14 GB / 15.96 GB
Binaries:
Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - ~\git\YouCoach\node_modules.bin\yarn.CMD
npm: 8.5.0 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK:
API Levels: 28, 29, 30, 31
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.2
System Images: android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom
Android NDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-201.87<IP_ADDRESS>53283
Visual Studio: Not Found
Languages:
Java: 11.0.9 - C:\Program Files\Common Files\Oracle\Java\javapath\javac.EXE
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
./gradlew bundleRelease
Snack, code example, screenshot, or link to a repository
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
ext {
googlePlayServicesVersion = "+" // default: "+"
firebaseMessagingVersion = "21.1.0" // default: "21.1.0"
buildToolsVersion = "30.0.2"
minSdkVersion = 21
compileSdkVersion = 31
targetSdkVersion = 31
ndkVersion = "20.1.5948944"
}
repositories {
google()
mavenCentral()
}
dependencies {
classpath("com.android.tools.build:gradle:4.1.0")
classpath('com.google.gms:google-services:4.3.3')
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
mavenLocal()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url("$rootDir/../node_modules/react-native/android")
}
maven {
// Android JSC is installed from npm
url("$rootDir/../node_modules/jsc-android/dist")
}
    google()
    mavenCentral()
    maven { url 'https://www.jitpack.io' }
}

}

I'm also getting the same error (version 0.66.4). anyone know what should we do?

https://github.com/facebook/react-native/issues/35136

is there any update on this i have tried all the possible steps but could not resolved.

I tried to modify the build.gradle and replace the jcenter() with mavenCentral(), but I got the same error. But another laptop it's working.

I tried to modify the build.gradle and replace the jcenter() with mavenCentral(), but I got the same error. But another laptop it's working.

The other laptop is probably working because you haven't executed gradle clean from there.

I remove jcenter in build.gradle ,it resolved!
project root => android => build.gradle
allprojects {
    repositories {
        all { ArtifactRepository repo ->
            if(repo instanceof MavenArtifactRepository){
                def url = repo.url.toString()
                if (url.startsWith('https://jcenter.bintray.com/')) {
                    remove repo
                }
            }
        }
    }
}

has been restored

Closing as this was a local outage


Feature: Publish Colored Task Manager to Open VSX

Dear extension author,
Please publish this extension to the Open VSX marketplace.
Context
Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in Open VSX and publish this extension on Open VSX.
My specific use case
Due to some limitations I could only use VS Code in the Browser through Gitpod, unfortunatelly, VS Code Browser is prohibited from accessing the Microsoft VS Code Extensions marketplace as mentioned here.
What is Open VSX? Why does it exist?
Open VSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia-based IDEs, and so on.
You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ.
How can you publish to Open VSX?
The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the ovsx publish command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.

Published!
https://open-vsx.org/extension/JakobiLee/file-organizer


Improve "local configuration" topic in deployment section

Description of the bug or enhancement
Example of a person confused with local configuration:
https://www.cuba-platform.com/discuss/t/deployment-with-configuration-out-of-war/10059
Deployment section:
http://cubadev:8181/manual/deployment.html
It does not clearly describe the concept of local configuration which can be applied to the system at deployment time, and does not specify place for local.app.properties.

the same: https://www.cuba-platform.com/discuss/t/change-dbms-type-via-local-app-properties/10237

also answer questions asked in these topics:
https://www.cuba-platform.ru/discuss/t/peremennye-okruzheniya/3907/4 (environment-specific properties)
https://www.cuba-platform.ru/discuss/t/razvyortyvanie-dvuh-kopij-prilozheniya-na-odnom-servere/3911/3 (two webapp copies in one tomcat)
https://www.cuba-platform.ru/discuss/t/ukazyvat-nastrojki-podklyucheniya-k-hranilishham-dannyh-vo-vremya-zapuska-prilozheniya/3914/2 (change database settings on prod server)


Font is missing some glyphs

The Font in Assets/Font is missing some glyphs like e.g. '%'

not relevant anymore


arch: arm: initialize variable

there are several code paths where this variable could end up being
returned uninitialized.
Signed-off-by: Jacob Siverskog<EMAIL_ADDRESS>

Thanks @jsiverskog
Could you please indicate a code path that ends up returning ptr_esf uninitialized? I did a quick pass and did not find any (but might have missed something)

after taking another look - yes, you are right. although i believe the change makes sense anyway, for clarity, but with another commit message?

Thanks @jsiverskog
Could you please indicate a code path that ends up returning ptr_esf uninitialized? I did a quick pass and did not find any (but might have missed something)

after taking another look - yes, you are right. although i believe the change makes sense anyway, for clarity, but with another commit message?

Actually, I think it would be better to leave it as is. Rationale: if we modify the function in the future, and accidentally create a path, where ptr_esf could be returned un-initialized, then a static analyzer could catch this and give a warning. If we force initialization to NULL, we lose this "protection". Any thoughts?

Thanks @jsiverskog
Could you please indicate a code path that ends up returning ptr_esf uninitialized? I did a quick pass and did not find any (but might have missed something)

after taking another look - yes, you are right. although i believe the change makes sense anyway, for clarity, but with another commit message?

Actually, I think it would be better to leave it as is. Rationale: if we modify the function in the future, and accidentally create a path, where ptr_esf could be returned un-initialized, then a static analyzer could catch this and give a warning. If we force initialization to NULL, we lose this "protection". Any thoughts?

ok! closing.


Update alpine to 2.60.3.

Updated the alpine branch to be able to update the official jenkins images.

alpine branch is no longer used, Dockerfile-alpine is

OK. Then we need to  find a way to be able to update the official alpine image. See https://github.com/docker-library/official-images/pull/3421
If I put the dockerfile in another folder, would you accept the change?

The jenkins image has been deprecated in favor of jenkins/jenkins
I thought @ndeloof had talked to docker

Didn't knew about. Just updated my instance with jenkins/jenkins :).

Maybe we should just remove this obsolete branch now


Adding backup restore blog post

Hey @kovrus here's a draft of the blog post, I kept it pretty simple to lead people towards the docs, more of an announcement with a little detail.
We should probably wait until the feature makes stable branch?

@ChrisChinchilla it is in testing now, we can already post it.

@kovrus And you're happy with the content?


[Bug]: js_image_layer doesn't work with --nobuild_runfile_links

What happened?
The binary's runfiles aren't be included in the app layer tar when build --nobuild_runfile_links is set in .bazelrc.
Version
Development (host) and target OS/architectures: osx, arm64
Output of bazel --version: 6.0.0
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file: v1.20.0
How to reproduce
cd e2e/js_image_docker
bazel test //... --nobuild_runfile_links

fyi @thesayyn

This intersects with what we do with Workflows so we should figure out what the principled fix is here.
cc @mattem @alexeagle

I see that the e2e/js_image_oci also fails with that flag.


ETC not showing on Mainnet but shows up on epool.io

Hi all,
I apologise if this is a dumb question, but my ETC i transferred from exchange to Emerald Wallet a few days ago is not showing on mainnet. Blocks are sync'd currently at 5498838 so is fully sync'd. They do however show up on epool.io  I know i haven't lost the coins, but just wondering how i can get to show up on mainnet? Thanks for your help.

Hi all, this issue is still ongoing, no ETC in mainnet, but epool and gastracker show balance but not the actual transaction.

FYI,
Still an issue.

I also had this issue. I'm in the process of trying to resync 0.9.0 RC3 to see if that fixes it. Sorry I can't help. I hope someone who can finally actually responds to you so that we can figure out how to fix this.

@KryptoKangaroo, @NotTheFloor  any progress with that ?


Error setting up in iOS (lib/dist/index.js doesn't exist)

The library works perfectly on Android, but in iOS when add the line:
pod 'react-native-notifications', :podspec => '../node_modules/react-native-notifications/react-native-notifications.podspec'
on the Podfile, install it and run the app, it crash because is unable to find the file lib/dist/index.js
See the full error:
Metro Bundler has encountered an error: While trying to resolve module react-native-notificationsfrom filewhatever, the package /project/ios/Pods/react-native-notifications/package.jsonwas successfully found. However, this package itself specifies amain module field that could not be resolved (/project/ios/Pods/react-native-notifications/lib/dist/index.js. Indeed, none of these files exist
The version is installing is: Installing react-native-notifications (3.1.4)

@AlexD10S try this: pod 'react-native-notifications', :path => '../node_modules/react-native-notifications', it worked for me.

Thanks, doing this is not crashing.
However, the handling methods of notifications: registerNotificationReceivedForeground, registerNotificationReceivedBackground... of the  library are not working when receive a notification

the same
this not working for me:
https://github.com/wix/react-native-notifications/issues/557#issuecomment-610425746

I'm getting the same issue on react-native 0.62.2 and react-native-notifications: 3.1.4. Any ideas on how this could be fixed?

@ciprian-iacob i have the same issue, when i try to install as a Pod file. And i try to install via Pod, because local notification are not working, but there was another problem: rn-firebase problem
so if you using a react-native-firebase for remote notifications and react-native-notification for local, try to install it without Podfile and install<EMAIL_ADDRESS>

Metro Bundler has encountered an error: While trying to resolve module react-native-notificationsfrom filewhatever, the package /project/ios/Pods/react-native-notifications/package.json was successfully found. However, this package itself specifies amain module field that could not be resolved (/project/ios/Pods/react-native-notifications/lib/dist/index.js. Indeed, none of these files exist

The reason this happens is because the .podspec file includes package.json file, so it gets copied into ios/Pods/react-native-notification. React-native Metro bundler finds that package.json file and uses it instead of the proper file (which is still under node_modules).
The solution for this specific problem is to delte the file ios/Pods/react-native-notifications/package.json.
This will raise another issue: the js code is looking for a dependency called ReactNativeNotifications, but the .podspec registers the package as react-native-notifications. The easier way is to change the podspec file to match the native module. I'm not sure about the implications of doing that when autolinking though.
If possible, the library could ship two podspecs: the current one for auto-linking; and an alternative for manual link with the native name ReactNativeNotifications.podspec

Workaround while the library is not fixed:
Use patch-package to change the podspec file in node_module so it doesn't include package.json in the pod and also register the proper name.
After installing patch-package and adding it as postinstall, save this as patch file in patches/react-native-notifications+3.1.4.patch:
diff --git a/node_modules/react-native-notifications/react-native-notifications.podspec b/node_modules/react-native-notifications/react-native-notifications.podspec
index c8e4e78..6db6a69 100644
--- a/node_modules/react-native-notifications/react-native-notifications.podspec
+++ b/node_modules/react-native-notifications/react-native-notifications.podspec
@@ -3,7 +3,7 @@ require 'json'
 package = JSON.parse(File.read(File.join(__dir__, 'package.json')))

 Pod::Spec.new do |s|
-  s.name           = 'react-native-notifications'
+  s.name           = 'ReactNativeNotifications'
   s.version        = package['version']
   s.summary        = package['description']
   s.description    = package['description']
@@ -15,7 +15,7 @@ Pod::Spec.new do |s|
   s.requires_arc   = true
   s.platform       = :ios, '8.0'

-  s.preserve_paths = 'LICENSE', 'README.md', 'package.json', 'notification.ios.js', 'notification.android.js', 'index.android.js', 'index.ios.js'
+  s.preserve_paths = 'LICENSE', 'README.md', 'notification.ios.js', 'notification.android.js', 'index.android.js', 'index.ios.js'
   s.source_files   = 'lib/ios/*.{h,m}'

   s.dependency 'React'

Change ios/Podfile entry to:
  pod 'ReactNativeNotifications', :podspec => '../node_modules/react-native-notifications/react-native-notifications.podspec'

Run yarn install and cd ios && pod install

Any updates on this?

+1 I'm also getting this error.

+1 Any updates on this?

+1 Any updates on this?

@AlexD10S try this: pod 'react-native-notifications', :path => '../node_modules/react-native-notifications', it worked for me.

thanks, It works

pod 'react-native-notifications', :path => '../node_modules/react-native-notifications' it doesn't work, any updates?

Metro Bundler has encountered an error: While trying to resolve module react-native-notificationsfrom filewhatever, the package /project/ios/Pods/react-native-notifications/package.json was successfully found. However, this package itself specifies amain module field that could not be resolved (/project/ios/Pods/react-native-notifications/lib/dist/index.js. Indeed, none of these files exist

The reason this happens is because the .podspec file includes package.json file, so it gets copied into ios/Pods/react-native-notification. React-native Metro bundler finds that package.json file and uses it instead of the proper file (which is still under node_modules).
The solution for this specific problem is to delte the file ios/Pods/react-native-notifications/package.json.
This will raise another issue: the js code is looking for a dependency called ReactNativeNotifications, but the .podspec registers the package as react-native-notifications. The easier way is to change the podspec file to match the native module. I'm not sure about the implications of doing that when autolinking though.
If possible, the library could ship two podspecs: the current one for auto-linking; and an alternative for manual link with the native name ReactNativeNotifications.podspec
Workaround while the library is not fixed:
Use patch-package to change the podspec file in node_module so it doesn't include package.json in the pod and also register the proper name.
After installing patch-package and adding it as postinstall, save this as patch file in patches/react-native-notifications+3.1.4.patch:
diff --git a/node_modules/react-native-notifications/react-native-notifications.podspec b/node_modules/react-native-notifications/react-native-notifications.podspec
index c8e4e78..6db6a69 100644
--- a/node_modules/react-native-notifications/react-native-notifications.podspec
+++ b/node_modules/react-native-notifications/react-native-notifications.podspec
@@ -3,7 +3,7 @@ require 'json'
 package = JSON.parse(File.read(File.join(__dir__, 'package.json')))

 Pod::Spec.new do |s|
-  s.name           = 'react-native-notifications'
+  s.name           = 'ReactNativeNotifications'
   s.version        = package['version']
   s.summary        = package['description']
   s.description    = package['description']
@@ -15,7 +15,7 @@ Pod::Spec.new do |s|
   s.requires_arc   = true
   s.platform       = :ios, '8.0'

-  s.preserve_paths = 'LICENSE', 'README.md', 'package.json', 'notification.ios.js', 'notification.android.js', 'index.android.js', 'index.ios.js'
+  s.preserve_paths = 'LICENSE', 'README.md', 'notification.ios.js', 'notification.android.js', 'index.android.js', 'index.ios.js'
   s.source_files   = 'lib/ios/*.{h,m}'

   s.dependency 'React'

Change ios/Podfile entry to:
  pod 'ReactNativeNotifications', :podspec => '../node_modules/react-native-notifications/react-native-notifications.podspec'

Run yarn install and cd ios && pod install

Thanks!!! this worked a treat!

pod 'react-native-notifications', :path => '../node_modules/react-native-notifications'

worked for me too, thanks

I have this issue when trying to use a fork of the repo - the repo doesn't contain lib/dist 😞  (which is included when retrieving the package from npm). Since there's no dist, it doesn't contain e.g. typescript definitions and the error message is totally valid (and the proposed solution doesn't work for this case). Not sure how to generate this, but noting it down in case someone else uses a fork and runs into the same problem.

@madandrija If you use a fork, you can build a dist folder using npm run build
Or you can run npm pack in the react-native-notifications folder. It will generates a tgz file which you can upload as a binary to release in your github repo.
More here https://glebbahmutov.com/blog/npm-install-with-just-github/ (just skip the part with adding files to package.json – it's not needed for this lib)


inbucket.org doesn't load

inbucket.org (vs www.inbucket.org) used to be very slow, and now it fails to load at all.

Think this is now fixed, needed to update my A records for github.


Why does this example not mention validate-azure-ad-token

This example makes no reference to the validate-azure-ad-token policy.
This leads to confusion as to what validate-azure-ad-token is for and why it's not recommended as an approach to validate a token from azure ad.
Please would you provide some context.

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

ID: 823eb96f-e5f1-0832-b175-0b31009be92f
Version Independent ID: 330085ae-dcf6-e930-86a8-0e4a60ab1314
Content: Protect API in API Management using OAuth 2.0 and Azure Active Directory - Azure API Management
Content Source: articles/api-management/api-management-howto-protect-backend-with-aad.md
Service: api-management
GitHub Login: @dlepow
Microsoft Alias: danlep

@Dev1thing Thanks for reaching out to us and reporting this issue. The above PR has been filed to enhance the documentation.


Option proto is being set to '0'

Seems to be a bug with option proto value being generated as '0' instead of 'all'.   The controls only worked for me when I manually changed the value from '0' to 'all' in the firewall configuration.
option proto '0'  -- not working
option proto 'all' -- works

OpenWrt reference says, that 0 and 'all' are synonyms. After all, the program does work for everybody else.
What version of OpenWrt do you use?


Add job resource for job kind

Short description: Need ability to access Job resources
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

/verified


Default value for variable substitution

Let's say I have a message "{name} works for company..." on a user creation form. When the user hasn't entered any name yet, the result will be "undefined works for company". Now I could give the default value myself, but the information should be in the translation, not in the application logic.
For example "{name, default, {User}} works for company...",
or just "{name | User} works for company..."
Maybe I'm missing something?

I have just implemented the ICU MessageFormat spec in JS, so I'm not really in charge of adding new features.
There's no shorthand for what you want, but you probably either want separate messages and a smarter template:
{{#if userHasFilledOutField}}
  {{mf key="message.worksfor"}}
{{else}}
  {{mf key="message.worksforteaser"}}
{{/if}}

or to use SelectFormat if for some reason you think the branching would be locale dependent (requires you to send extra state data into the message):
{formIsFilled, select,
  true {{name} works for company}
  other {They work for company}
}

Hope that helps!

Thanks for the tips! I understand not wanting to add features that aren't part of the spec.
Making the template smarter is a bit tricky, because I want to use it in a placeholder attribute and it would make the template quite messy.
I was also thinking about using the select feature just before you replied, I might give it a shot. But if it seems hard I'll just drop it for a static string.

Because the key values are cast to strings by JavaScript during the lookup, a value that is left undefined in the input data matches the string 'undefined'. This "feature" means that the following form is probably what you're looking for:
{name, select, undefined{They work} other{{name} works}} for company

Unfortunately the security strategy of angular-translate sanitizes undefined values to empty strings, but using name || 'undefined' as the value works nicely. Kiitos!
I guess it's a feature that other{{name}} doesn't work as a case alone and I have duplicate "works".


LTO build fixes

[Zephyr] Fix sys_heap malloc build with LTO
[nrfconnect] Do not link libCHIPShell.a with --whole-archive

@LuDuda The commit to enable LTO was added just for testing. I removed it, so the PR can be merged now.


Update for 6.0.0.GA?

Hi Centogram,
Do you have an updated dist for 6.0.0.GA+? I've tried to do this myself but I keep getting stuck with the hook/intercom.js and the R$color bug that is listed in a previous issue for this module
It seems fairly easy to upgrade with this guide: https://medium.com/all-titanium/rebuilding-android-modules-for-titanium-6-x-b20086c5cb47
Much appreciated!
Markive

You're better off just using Hyperloop going forward. I've abandoned any more updates to this module as it was just too cumbersome
On Jun 17, 2017, 10:41 AM -0400, markive<EMAIL_ADDRESS>wrote:

Hi Centogram,
Do you have an updated dist for 6.0.0.GA+? I've tried to do this myself but I keep getting stuck with the hook/intercom.js and the R$color bug that is listed in a previous issue for this module
It seems fairly easy to upgrade with this guide: https://medium.com/all-titanium/rebuilding-android-modules-for-titanium-6-x-b20086c5cb47
Much appreciated!
Markive
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (https://github.com/centogram/TiIntercomAndroid/issues/7), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAM3iQY_fW8sWt-k2F-oObDwaL3sig3Yks5sE-WGgaJpZM4N9PgV).


[Accessible Pressables] Migrate components using TouchableWithoutFeedback to use PressableWithoutFeedback

HOLD on https://github.com/Expensify/App/issues/16988
Description
This is a tracking issue. Components are grouped together based on their priority. This is priority group #1.
List of components to migrate for this issue:

[ ] GrowlNotification
[ ] BasePreRenderer
[ ] PDFView
[ ] IOUPreview
[ ] BaseTextInput
[ ] BankAccountStep

Triggered auto assignment to @conorpendergrast (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero process steps for feature requests for more details.

cc @RobertKozik

Letting this stay closed because it's actually done already 🎉

Well check that out


Is this project still active?

I ask because I can see that the most recent code merged into master is almost two years old.  I can see that there's a "develop" branch but that hasn't been touched for over a year now and there's no indication that it will be merged into master.
What is the state of develop?  Is there anything in it that makes it unsuitable for merging?
From my point of view I came across this plugin yesterday only to find that the example project worked but when I added similar code to my project it didn't.  It turned out that the plugin doesn't support the version of Cordova I'm using (6.3.1) on iOS.  Although looking at the Cordova it looks like it will have been broken since Cordova 4.  (See the notes on initWithWebView at https://github.com/apache/cordova-ios/blob/master/guides/API changes in 4.0.md)
I have a fix of sorts but I was hoping that this project could be brought back to life to bring it back to full compatibility with the latest versions of Cordova, iOS, Android, etc.

Hello,
This project is no longer actively developed as we didn't have a chance to use it recently but contributions are always more than welcome.
Bringing this project back to full compatibility with the latest versions of Cordova/iOS/Android would indeed be the main priority. If you have any interest in this project and would be willing to make the necessary changes as a PR, we would gladly review and merge it!
As the current state of develop, there is nothing specific that makes it unsuitable for merging afaik.
If this project was to be brought back to life, it would be nice to drop the develop branch system altogether to switch to a master+releases system and publish it on NPM.

Sorry, I meant to reply to this and say that although I'm happy to assist with getting the project up to date, I have no experience of Objective C nor Cordova plugins architecture.  Debugging this issue was the first time I had spent any time looking at Objective C code.
I do have a fix which is good enough for my basic experiments with the plugin but I haven't started using it in anger yet and I have already noted that it breaks the existing example code which uses an older version of Cordova.
My naive fix is here
https://github.com/XuluWarrior/phonegap-plugin-wizViewManager/commit/d1e1b5a1e82f71eda33811ad7ee6401dd0cb6052

Hello! Thanks for taking the time to reply. Your fix seems to be what is expected from the notes you linked to, so there should not be any issue merging it.
I tried to create a PR to discuss it but there are other commits in your master branch. See for yourself here:
https://github.com/Wizcorp/phonegap-plugin-wizViewManager/compare/develop...XuluWarrior:master?expand=1
If you could cherry-pick your commit based on Wizcorp's develop branch and PR it, I could look into fixing the example.
As a heads-up, my only comment concerning your fix would be asking why you used self.webViewEngine.engineWebView instead of self.webView?

Sorry, I got pulled on to other things and neglected to get back to this.
There was no reasoning behind using self.webViewEngine.engineWebView.  I was merely using code inspection to find a suitable property.  (As I said I have no Objective C or Cordova plugin experience.)  I made another check-in replacing it with self.webView.
I cherry-picked a branch but should have read your message more closely as I based it on master rather than develop.  I will recreate the pull request.
Also due to moment of madness I called my branch Issue#84 when it actually refers to Issue #86

Thanks again for your contribution! I merged your PR. I think this issue can be closed, feel free to open it again if you think it has not been resolved yet.

I'm glad I could help :)
I'm not working with this plugin at the moment, but when I get back to it I'll be sure to report any issues I find ;)


Update aruba timeout to use config block

This updates to be similar to:
https://github.com/rspec/rspec-mocks/blob/4be625e322ed1da7607ecab0e838efd9453ac0c6/features/support/env.rb#L4-L10
The current usage @aruba_timeout_seconds appears to be deprecated:
https://github.com/cucumber/aruba/blob/1c6bc8731891692f5064fcfd1ff8a885c23298a6/CHANGELOG.md#080pre

Thanks!


Histogram should handle PVs with many values better

We don't currently limit how many possible values are shown in the histogram. This PR will make Visallo handle PVs like all other datatypes.

[ ] joeferner
[ ] mwizeman joeybrk372 jharwig sfeng88

Testing Instructions:
Select more than 5 entities on the graph, each of which should have a possible value property set to a different value. The histogram should not show more than five bars for that property.
Points of Regression:
CHANGELOG
Added:
Changed:
Documentation:
Deprecated:
Removed:
Fixed: Fixed handling of possible values in the histogram when there are many possible value types
Security:

@kunklejr can you remove the changelog section of this PR? It will be covered by the 4.0 PR.


feat: add broken-backlinks audit type (SITES-18417)

This PR adds the broken-backlinks as supported audit type for SITES-18417.
Relates to https://github.com/adobe/spacecat-audit-worker/pull/77, https://github.com/adobe/spacecat-audit-post-processor/pull/37, https://github.com/adobe/spacecat-audit-scheduler/pull/27, https://github.com/adobe/spacecat-api-service/pull/97
Please ensure your pull request adheres to the following guidelines:

[ ] make sure to link the related issues in this description
[ ] when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

Related Issues
Thanks for contributing!

:tada: This PR is included in version @adobe/spacecat-shared-data-access-v1.8.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


AdalContext is not exported

I took your advice from the nativescript-oauth and came here, and now I'm having the following issue:
For some reason, the adal.ios.ts and adal.android.ts are missing from the package , so the ts compiler says that there is no AdalContext in the package
Also, I tried to copy the files from the repo and then I get the following error
node_modules/@navara/nativescript-adal/adal-library.ios.d.ts(4,41): error TS2503: Cannot find namespace 'interop'.
tns --version 3.3.0

Hi @laur3d, thanks for trying this plugin!
There seems to be something wrong with the publish to npm - I'll try to fix this soon

There is a 1.0.2 version released now - and this one seems to be working fine for me!

You my friend are awesome, thanks for the quick fix 👍
I just tried it and works like charm on both iOS and Droid

I am getting the same issue with 1.0.6. Works fine with 1.0.2

@BeMor81 same, have been trying to figure out the proper implementation of this in a shared project this whole day, 3 a.m. and still at it! Let me know if you find a solution.

@YvesCandel so this might also be isolated but the typings in the iOS package are throwing out errors preventing the compilation even of the web version although it has nothing to do with it and isn't imported/loaded anywhere.
The errors are following the following pattern and there's probably like 20-30 of them, didn't count: node_modules/@aminebizid/nativescript-adal/platforms/ios/typings/adal-library.ios.d.ts(291,72): error TS2503: Cannot find namespace 'interop'.
Is this something happening because of something missing from the dependencies or just a wrong tsconfig? Any ideas on how to overcome it?


Add jquery as a dependency

This package depends on jquery but doesn't list it as a dependency in the package.json.  This will break in webpack/browserify.  Will send a PR if you agree.

+1

+1

+1

If it helps anyone, I was able to resolve this in webpack by adding jQuery as an external in my config
 externals: {     "jquery": "jQuery",     "$" : "jQuery" }

I just bumped up against this with browserify. Hope you agree. Thanks in advance.


lib: Add struct Register

The Register struct will be used when registering a workload (like in register_workload() in reference-kbs). It contains no TEE-specific data; only the ID, measurement, TEE-config info, and passphrase to unlock the disk.
Signed-off-by: Tyler Fanelli<EMAIL_ADDRESS>

Will re-submit with other SNP additions.


Problem with quantity input on BASK

Noticed a couple issues with the BASK page, namely that when a customer manually wants to change a quantity by typing in their desired amount, the form submits. I think it would be best if it was only submitted on a "return / enter / go" keypress or tap. Because as it stands, if you hit backspace to remove the existing quantity the form submits and the product is removed entirely from the cart – haha potentially huge issues and I can just hear it now. Anyone know of an easy fix for this?
Expected Behavior
When using the backspace or delete key, the form should not submit.
Current Behavior
When using the backspace or delete key, the form submits before you can change the quantity.
As reported on the Miva Forum

It appears there was some incorrect checking being performed in the Quantify extension. Replace the existing JavaScript with this code to correct the issue. This fix will be included in the next maintenance release.
/**
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |q|u|a|n|t|i|f|y|
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 *
 * This extension allows for the use of buttons to increase/decrease item
 * quantities on the product and basket pages. When used on the basket page,
 * the decrease button becomes a remove button if the quantity is 1.
 */

(function () {
	'use strict';

	var adjusters = document.querySelectorAll('[data-hook="quantify"]');

	for (var id = 0; id < adjusters.length; id++) {
		adjusters[id].addEventListener('click', function (event) {
			if (event.target.matches('button')) {
				var button = event.target;
				var inputs = [].filter.call(this.children, function (sibling) {
					return sibling !== button && sibling.matches('input');
				});
				var input = inputs[0];
				var value = parseInt(input.value);
				var action = button.getAttribute('data-action');
				var changed = document.createEvent('HTMLEvents');

				changed.initEvent('change', true, false);
				event.stopPropagation();
				event.preventDefault();

				if (action === 'decrement') {
					/**
					 * THIS CAN BE USED TO SET A MINIMUM QUANTITY
					 * value = value > 5 ? value - 1 : 5;
					 */
					value = value > 1 ? value - 1 : 1;

					input.value = value;
					input.dispatchEvent(changed);
					allowRemoveUpdate();
				}
				else if (action === 'increment') {
					/**
					 * THIS CAN BE USED TO SET A MAXIMUM QUANTITY
					 * value = value < 100 ? value + 1 : 100;
					 */
					value = value + 1;

					input.value = value;
					input.dispatchEvent(changed);
					allowRemoveUpdate();
				}
				else {
					input.value = 0;
					input.dispatchEvent(changed);
				}
			}
		});
	}

	function allowRemoveUpdate() {
		var quantities = document.querySelectorAll('[data-hook="group-quantity"]');

		if (quantities) {
			for (var id = 0; id < quantities.length; id++) {
				var quantityLine = quantities[id];
				var removeToggle = quantityLine.previousElementSibling;

				if (removeToggle.dataset.hook !== 'remove') {
					if (quantityLine.value > '1') {
						removeToggle.classList.remove('u-icon-remove');
						removeToggle.classList.add('u-icon-subtract');
						removeToggle.setAttribute('data-action', 'decrement');
					}
					else {
						removeToggle.classList.remove('u-icon-subtract');
						removeToggle.classList.add('u-icon-remove');
						removeToggle.setAttribute('data-action', 'remove');
					}
				}

				quantityLine.addEventListener('change', function (event) {
					groupSubmit(event, this);
				});

				quantityLine.addEventListener('input', function (event) {
					groupSubmit(event, this);
				});
			}
		}
	}

	allowRemoveUpdate();

	function groupSubmit(event, quantity) {
		if (event.key !== 8 && event.key !== 37 && event.key !== 38 && event.key !== 39 && event.key !== 40 && event.key !== 46 && quantity.value !== '') {
			document.querySelector('[data-hook="' + event.target.getAttribute('data-group') + '"]').submit();
		}
	}
})();

How are these bug fixes being applied? Should we not be downloading the readyTheme from the Miva App store? Should we checkout the shadows Git repository locally and update it manually? What's the best practice here?

Until a maintenance release is pushed to the AppStore, the best course is to manually perform the updates as listed here. Each maintenance release is related to a specific milestone, so this will be part of the 1.0.2 release.


MyriaL support for SplitExpression and SequenceExpression

These are currently the only built-in flatmap expressions in MyriaX, so can be supported in RACO without syntax support for MyriaL flatmap UDFs. Tested in MyriaWeb with the following queries:
R = load("https://s3-us-west-2.amazonaws.com/uwdb/sampleData/tab.txt",
csv(schema(index:int, intlist:string), delimiter="\t"));
store(R, flatmap_input, [index, intlist]);
S = scan("public:adhoc:flatmap_input");
T = [from S emit S.index, S.intlist, split(S.intlist, ",")];
store(T, flatmap_output, [$0, $1, $2]);
T = [from S emit S.index, S.intlist, sequence(S.index)];
store(T, sequence_output, [$0, $1, $2]);

Coverage decreased (-0.05%) to 91.829% when pulling 61340fcf11b61f2c6c34932234e0001ab064eccd on flatmap into 0231c0936bde9f68386a80fc9b9e96309b8d2091 on master.

LGTM

Coverage decreased (-0.05%) to 91.829% when pulling 61340fcf11b61f2c6c34932234e0001ab064eccd on flatmap into 0231c0936bde9f68386a80fc9b9e96309b8d2091 on master.

Coverage decreased (-0.1%) to 91.756% when pulling 335c8ca8865e7eada14a216f0f13aad95a45648d on flatmap into 0231c0936bde9f68386a80fc9b9e96309b8d2091 on master.


[Bug] Incorrect pronunciation of sounds in "Слоги Королёвой/Гласные О-И-У"

Precondition:
Log in as default2 user<EMAIL_ADDRESS>/ password)
Steps to reproduce:

Go to https://brainup.site/groups/1/series/18/subgroup/143/
Click on exercises 3 (https://brainup.site/groups/1/series/18/subgroup/143/exercise/2014/task/2002, https://brainup.site/groups/1/series/18/subgroup/143/exercise/2015/task/2003, https://brainup.site/groups/1/series/18/subgroup/143/exercise/2016/task/2004,
https://brainup.site/groups/1/series/18/subgroup/143/exercise/2018/task/2006, https://brainup.site/groups/1/series/18/subgroup/143/exercise/2022/task/2010, https://brainup.site/groups/1/series/18/subgroup/143/exercise/2028/task/2016
Press the red play button.

Actual result:
Syllable "бо" is pronounced as"бв" and "бу" is pronounced like "боу" (exercise 3).
Syllable "до" is pronounced like "да" (exercise 4)
Syllable "гу" is pronounced like "гоу" (exercise 5)
Syllable "ни" is pronounced like "нь"/"не" (exercise 7)
Syllable "ко" is pronounced like "ку" (exercise 11)
Syllable "пу" is pronounced like "поу" and "по" is pronounced like "пв" (exercise 13)
Syllable "со" is pronounced like "ca" (exercise 17)
Expected result:
Syllable "бо" is pronounced as"бо" and syllable "бу" is pronounced like "бу" (exercise 3).


Upgrade to SK RC4

Update the latest Semantic Kernel RC

will wait till 1.0.0 to reduce churn - thanks!


single-select: Does not truncate longer text in option

Detailed description of how to reproduce the problem
If you have a longer text as option of the select, it does not get truncated (with ellipsis) but completely shown with line-break.
Upload a screenshot

Describe the development framework
No response
Expected behavior
Long text should be truncated with ellipsis when text is longer than dropdown width
Additional information
No response

Your [issue](https://github.com/orgs/Infineon/projects/4?pane=issue&itemId=89660180&issue=Infineon%7Cinfineon-design-system-stencil%7C1621) has been approved! You can follow the latest status on our public backlog board. Thank you for your contribution!
@ralfongit
I edited the title because the issue only occurs in single-select.


Program does not download full art

The program does not download the full version of the art, but its reduced version

on which platform? and which art? a link would be helpful i could try it out myself

Sorry, I completely forgot to write that the program did not download full art from deviantart.
Platform - windows 10. Artist - https://www.deviantart.com/dream-and-nightmare

Thank you for submitting the issue, you were right, the app indeed downloaded the scaled down versions of the images. I assumed that the list deviantart api gives me contains the urls to the original sized images, which is the case for the most images but some images seem to be an exception (e.g. ultra wide images/banner).
I've fixed it in my latest commit


Try::Tiny has some performance issues

So I'm using this amongst other things to load my indexes up in bulk.  This process takes some 5-6 hours so I've been profiling to see where I can improve it (It's already been improved quite a bit, it was between 8 and 18 hours).
One of the things I noticed is that you're using Try::Tiny everywhere (but especially within your json encoder role).
According to https://metacpan.org/pod/Try::Tiny::Tiny and http://blogs.perl.org/users/diab_jerius/2017/04/how-fast-can-you-try.html Try::Tiny is actually pretty slow.
In Search::Elasticsearch::Role::Serializer::JSON I changed the encode routine to
#===================================
sub encode {
#===================================
    my ( $self, $var ) = @_;
    unless ( ref $var ) {
        return is_utf8($var)
            ? encode_utf8($var)
            : $var;
    }
    my $return;
    eval {
        $return = $self->JSON->encode($var);
    };
    if ($@) {
        throw( "Serializer",$@, { var => $var } );
    }

    return $return;
}

On a limited run which took 4:22 before I changed, it now takes 3:43.  This is borne out by my profiling which shows it taking 30 seconds https://imgur.com/a/7A8jUg5
Results from my changed version are shown here https://imgur.com/a/cljcPQR
I was really quite surprised that Try::Tiny had that much overhead but it may be worth considering switching back to using raw eval or Syntax::Keyword::Try which came out favourably as well.

If you like I can send a pull request in with the relevant changes.  Minimized to the json encode/decode stuff if wanted.

Sorry I haven't gotten back to you on this.  Interesting find, and worth changing.  I had a quick grep through the module and I'm using none of the more interesting features of Try::Tiny, so it could be replaced by pretty much any of the alternative modules.  One thing I'm not sure about is if those modules play nicely with AnyEvent.
I'd be happy to review a PR, even just targeting the JSON encoding bit (but would be good to completely switch modules instead)

Syntax::Keyword::Try is also less quirky than Try::Tiny

Syntax::Keyword::Try is also less quirky than Try::Tiny

I did consider that but it has a hard requirement of perl 5.14 and it's still somewhat slower than eval, so I figured if we were speeding things up it made sense to just go with the basics.  It's also much less likely to conflict with AnyEvent

Thanks for this PR and sorry for the slow responses.  I'm trying to find time to release a 7.0 compatible version at the moment, and will look at merging this at the same time.

eval() is probably the way to go in terms of speed and compatibility.

@spansh, how much slower was Syntax::Keyword::Try than eval?

The link in the original post has speed comparisons

@spansh thanks for the link, I'll have a look to your PR soon.


Flex grid problem for form element fieldset and legend

The flex grid system is not working on google chrome and firefox for form element fieldset and legend.
We are using Bootstrap 4 Alpha-6. We have tested on chrome version  56.0.2924.87 and firefox version 52.0.1 .
Sample link is : https://jsfiddle.net/krishnanandsaha/9Lfqj3nn/15/
What is wrong with my code?

Why do you need fieldset. change it to a div like the other group rows.

Why do you need fieldset.

because it's the structurally correct element to use when you also want to provide an overarching <legend>. so yes, @krishnanandsaha's markup is correct, and it's likely a shortcoming of the BS CSS

Problem with this element, also  and  is it has bug in flexbox on all mayor browers.

This is flexbug 9—some elements cannot be flex containers. The only solution is to put another element directly within the <fieldset> it appears. Closing as a can't fix.


Scaleledmatrix

Automatically scale led matrix buttons based on the size of the matrix. Allow allows it to be parameteriszed. Fix for https://github.com/microsoft/pxt-microbit/issues/2891

Thank you for putting this in, that's great. Did you consider that 0.6 is the smallest it should be?

Trying to avoid tiny buttons that become an accessiliby issue. How many LEDs did you need?

Maybe not too many!
Is this in the beta release only or will it and the custom size facility appear in the default?

Beta only for now.

From: Michael Killpatrick<EMAIL_ADDRESS>Sent: Friday, April 24, 2020 4:50:02 PM
To: microsoft/pxt<EMAIL_ADDRESS>Cc: Peli de Halleux<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [microsoft/pxt] Scaleledmatrix (#6910)
Maybe not too many!
Is this in the beta release only or will it and the custom size facility appear in the default?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpxt%2Fpull%2F6910%23issuecomment-619283593&data=02|01|jhalleux%40microsoft.com|17a53f117fac45c4b1ce08d7e8aa34aa|72f988bf86f141af91ab2d7cd011db47|1|0|637233690036781735&sdata=50MbHXOCX5Gnryh5VbzgkoVAfkHUR3fGmhu6FxLFEW8%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA73QKLC4TKG3X7WO5VQHPTROIQSVANCNFSM4MQMHBYA&data=02|01|jhalleux%40microsoft.com|17a53f117fac45c4b1ce08d7e8aa34aa|72f988bf86f141af91ab2d7cd011db47|1|0|637233690036791688&sdata=YTntPm0amQRk%2FGCPP7YYMr2pNiuYb7ufkJvtOmsb8jE%3D&reserved=0.


Wrong unit for sun irradiance

The unit reported to home assistant for sun irradiance (W/m²) does not match the unit from the simple_dwd_forecast (kJ/m²/h). Either the unit should be updated or the reported values need to be divided by 3.6 to convert between kJ/h and W. I noticed this because the values I'm currently seeing are consistently above the solar constant of 1361 W/m², which is impossible. Dividing by 3.6 yields much more sensible values that also closely match my simple local weather station with a light sensor.
Either solution will probably mess up long-term statistics in Home Assistant (incompatible units or sudden jump in magnitude)

Hi, thanks for reaching out. We had this already in #35 and now I'm a bit confused. I will have a look into this later. Or maybe you can clarify this?

Thanks for pointing out the previous issue on this. However, I think it was correct originally and the change made following issue 35 was not correct. Let me clarify:
You cannot get a solar irradiance value above 1361 W/m² because this is the total power output of the sun at the earth's distance per m². This number is called the solar constant. Hence, this value is the physical upper limit on any measured value.
Due to atmospheric effects the actually measured value on earth is even lower, which is correctly cited by user @lbrandh in the previous issue (~1120 W/m²). However, even he states that he is getting values between 0-2000. While this is, as he writes, in the same ballpark as the Wikipedia value of 1120 W/m², it is nevertheless above the stated physically possible value, hence the unit cannot be W/m².
Going on, he mistakenly states that his measured value is about a factor of 10 too small for the kJ/m² figure taken from Wikipedia (21.6 MJ/m² = 21600 kJ/m²). This number however represents energy per area for a whole day, i.e. 21.6 MJ/m²/day. If we convert this value back to kJ/m² per hour (the original unit of the Rad1 value in your dataset), we arrive at 900 kJ/m²/hour which is again in the same ballpark as his number. As this 900 kJ/m²/hour is averaged over the whole day, the peak value at noon will of course be higher. We can simply calculate this maximum possible value if we multiply the solar constant by 1 hour (i.e. accumulating the solar energy deposited in 1 hour in 1 m²), arriving at 4899.2 kJ/m². I have never observed a value of more than ~2500 since last September, which is twice as high as the physical upper limit
The numerical conversion factor between kJ/m²(/hour) and W/m² is simply 3.6. Below find a graph of the DWD values your integration provides divided by 3.6 (orange) and my local sensor (blue). My sensor goes down in the afternon due to some tree shading.

To conclude, the number provided by DWD is accumulated energy over 1 hour in kJ/m², which according to Wikipedia is called "solar irradiation, solar exposure, solar insolation, or insolation". The very similar named solar irradiance is momentary solar power per m², i.e. W/m². You can convert between the two by dividing the kJ/m² number by 3.6 to arrive at W/m². The W/m² solar irradiance will be the average value over one hour.
Whether the value provided by DWD for 12:00 is the accumulated energy between 11 and 12 or 12 and 13 I cannot say ;).

Thank you very much for your detailed answer. I don't use the values myself, so I never compared them to real values.
I released a new version which fixes this.
Best regards


Copied MX Panel from flex-sdk

Copied MX Panel from flex-sdk to Start mx.containers.Panel Emulation

I did Panel


Adding Relevant Content to the Course Supervised vs Unsupervised Learning, making it a Structured Course.

I want to make the whole Structured and Organized Course Structure for Supervised vs Unsupervised Learning which will make it a complete course Structured for 3 weeks. I'll be covering each and everything important in Supervised vs Unsupervised Learning course along with making it visible and Interactive on the web site. I will also try to include a Assessment test at the end of this course.
Please assign me this issue under gssoc-ext label.

hello @vivekvardhan2810  can you assign this to me as I really want to work on this project

Okay @SoumyaU25 Assigning this issue to you.
Make sure to complete this in next 3 days.

"I would like to work on this issue as I have a strong background in CSS and HTML. Please assign me to this task under GSSOC'24 Extended."

You Can Complete this issue @SoumyaU25, i have closed that previous issue.

Okay thanks @vivekvardhan2810

I am closing this issue, as the courses page were updated including contents, But don't get disappointed, i would encourage you to create new issue regarding website improvements, then you can create new issue.


Expose Dark mode from Excalidraw

Hello, thanks for making this tool I think it's great idea!
I always enable dark mode when using excalidraw, I think it would be great for users to be able to enable/disable darkmode when looking at the slides too.
I've started to look how to do it unfortunately it's a little more involved than a one line change but I will share what I found:
In excalidraw the dark mode toggle button changes the appearance on the AppState:
setAppState({ appearance });
https://github.com/excalidraw/excalidraw/blob/538f2be097686a42a0c158bff68d7ab39d402171/src/components/BackgroundPickerAndDarkModeToggle.tsx#L21
You can see the appearance key on the AppState here:
appearance: "light" | "dark";
https://github.com/excalidraw/excalidraw/blob/master/src/types.ts#L85
The App component reacts to the appearance value change and adds the css class "Appearance_dark" on to the .excalidraw html markup:
document.querySelector(".excalidraw").classList.toggle("Appearance_dark", this.state.appearance === "dark");
https://github.com/excalidraw/excalidraw/blob/bf143ed0b8ba06e67e512978d14d6859833ed83d/src/components/App.tsx#L879
This means that a quick hack could be to add the css class "Appearance_dark" on the Excalidraw component by running this code (the better way would be to call setAppState({ appearance }) on the Excalidraw component but they don't currently expose a way to do so):
document.querySelector(".excalidraw").classList.toggle("Appearance_dark", this.state.appearance === "dark");
Unfortunately I've tried running it in the Chrome console, on excalidraw.com it works and enables dark mode, however on excalidraw-slides.netlify.app it doesn't so I think the Excalidraw component that is imported from npm might not include the css styles for the dark mode.

I made some progress and created a PR to the Excalidraw repo to include the Dark mode css styles in their exported package:
https://github.com/excalidraw/excalidraw/pull/2392

Bumped into a bigger issue, the npm package of excalidraw 0.6.1 is actually exporting the source from a special repository called https://github.com/excalidraw/excalidraw-embed which hasn't been updated in 3 months and is missing support for Dark mode.
I think the best way to import the latest version of Excalidraw would be to import it as a github subfolder like in https://github.com/dai-shi/excalidraw-animate/tree/master/src

We'll be releasing a new npm package under @excalidraw/excalidraw soon, directly from the src/packages/excalidraw.


prog: enable_syscalls does not properly handle resources within unions

When a syscall description is the only producer of a resource and at the same time also consumes it, syzkaller cannot resolve this dependency and disables such syscalls with the disabling X: no syscalls can create resource Y, enable some syscalls that can create it [X] error.
Here is a discussion where the issue was reported. Here is an example of such a system call description.

Gave the issue another thought and updated it. The problem is not in the circular dependencies per se -- if we have a genuine circular dependency, we cannot build programs that would satisfy it.
I.e.
A {
 field1 B (in)
 field2 B (out)
}
some_syscall(arg ptr[inout, A])

is indeed an invalid construction. While such descriptions
A [
 field1 B (in)
 field2 B (out)
]
some_syscall(arg ptr[inout, A])

can be used to generate valid programs and should be normally handled.

We could fix it as follows. Let the separation into "input" and "output" resources remain the same.
https://github.com/google/syzkaller/blob/b599f2fcc734e2183016a340d4f6fc2891d8e41f/prog/target.go#L154-L155
However, it makes sense to limit the output of getInputResources only to those resources, which are truly necessary to execute a system call. Right now it returns all the resources which could be taken by that syscall as input (directly or indirectly via compound arguments - structs/unions/etc).

Potentially it will work as-is if we permit such limited cycles. When we generate a resource we have this ugly loop that tries to generate arguments that actually produce the required resource:
https://github.com/google/syzkaller/blob/be2c130d4c0c511da96ce278486cf0564aeadcea/prog/rand.go#L379-L415
So it will loop until it creates a union option where this resource is 'out'.
But I am not sure if it's worth it. Depends on the amount of code to properly detect such limited cycles. The alternative is to provide multiple syscall specializations (one has the resource is output, another - as input).

Okay, so as of now (2023), it looks like resources are actually never ever taken from unions (*):
https://github.com/google/syzkaller/blob/5b429f39ae82dfd954322d3f42c830cf560f51d2/prog/resources.go#L55-L57
In this case, the originally described problem (a struct either producing or consuming resources depending on the union) is no longer relevant. But we are still too strict in terms of required input resources: every resource mention by any union field must be present for a call to be enabled.
(@ramosian-glider FYI)
(*) At the same time, syzkaller does not complain about definitions where there are out resources inside unions:
nested_union [
 some fd
]

some_struct {
 field nested_union (out)
}

read$test(fd fd, val ptr[out, some_struct], len len[val])

But we are still too strict in terms of required input resources: every resource mention by any union field must be present for a call to be enabled.

Gave it another thought and it looks like the fix is not that straightforward.
For every union, we must pick exactly one alternative (we cannot pick 0), so the set of necessary resources depends on the choices made. There won't be a single minimum necessary set of resources for a call. We have to ensure that all enabled calls can produce resources to fulfill the requirements of at least one of its alternative union selections.
Array types (if they are permitted to be of 0 length) can further reduce resource requirements.


Add detailed logging for debugging

Current logging only hows little details like :
[2022-11-30T16:30:01.888Z] Starting cron job
[2022-11-30T16:30:02.523Z] Started cron job with day Thursday
-> Extend it so that detailed debugging of issues is possible


Fix/allow default value

I don't even remember why, but while working on avro compatibility check, we found out strange behaviour by the parser if it encounter null value while parsing String. While trying to fix that, a lot of stuff popped out.
We used that opportunity to fix handling of "null" and implement "default" field value (avro spec).
We also added a parameter "missingDefaultIsNull", that put "null" as "default" if no default is given
More info on why this is needed on https://issues.apache.org/jira/browse/AVRO-1803
(no "null" default means that if key isn't found in the record, the record is invalid)
This parameter is "true" by default for simplicity and avoid breaking compatibility
It SHOULD not break anything, UT still works, but it might, has before, in the fromMap method of AvroConverter, the only line was
record.put(field.name(), convert(field.schema(), data.get(field.name())));

this didn't check if the key existed in the record, Map().get() returns null if the key doesn't exist

This still needs works : a lot of TODO and FIXME were put in nearly every avro type test
I'd like some help on those because I have deadlines coming around :sweat:

Also, missingDefaultIsNull is a lame variable name, some ideas for a better one ?

will be a massive breaking change, will clause so far


Baidu.com issue

With PR https://github.com/Athlon1600/php-proxy/pull/47 now baidu.com works fine, but there is a strange issue when clicking on search results.
For example, if I search for "php-proxy" and I click on the first link found, the content of the HTML page that contains two redirects (one via location.replace() and one via meta refresh) is not filtered via ProxifyPlugin. It looks like if it is ignored or if it is too early that OnCompleted() event can't catch it. See this image:

Related to #43

meta refresh issue is now fixed: https://github.com/Athlon1600/php-proxy/commit/f182fd063b3c432c1b02e4d7dc9869a63a9c12fb
As far as Javascript problems, I would just disable javascript entirely for baidu.com from your config.php file like this:
$config['js_remove'] = array('baidu.com');


Android App - Search for notifications

I would like to be able to search through my notifications for the specified search term(s).
I am envisioning two searching methods:

Searching within a topic - display only notifications whose message / title / tags match the search term
Searching all topics - similar to the first one, but may be done from the "Subscribed topics" view, and would show all matching notifications from all topics

I don't hat the idea; the UI would be a little tricky I think, but searching the small SQLite db should be easy enough.

I would also chime in for search ability in web version. Recently I needed to search for one specific alert and I was surprised there is not such option.

Recently I needed to search for one specific alert and I was surprised there is not such option.

The WA is to load as many messages as possible by pressing and holding the PgDown button on the selected topic and then use the browser's built-in search functionality.
However, still can't search in the Android app, and, thus, it's still impossible completely switch from an app like Telegram to the incredible Ntfy app :disappointed:


KAFKA-6813: Remove deprecated APIs in KIP-182, Part I

I'm breaking KAFKA-6813 into a couple of "smaller" PRs and this is the first one. It focused on:

Remove deprecated APIs in KStream, KTable, KGroupedStream, KGroupedTable, SessionWindowedKStream, TimeWindowedKStream.

Also found a couple of overlooked bugs while working on them:

2.a) In KTable.filter / mapValues without the additional parameter indicating the materialized stores, originally we will not materialize the store. After KIP-182 we mistakenly diverge the semantics: for KTable.mapValues it is still the case, for KTable.filter we will always materialize.
2.b) In XXStream/Table.reduce/count, we used to try to reuse the serdes since their types are pre-known (for reduce it is the same types for both key / value, for count it is the same types for key, and Long for value). This was somehow lost in the past refactoring.
2.c) We are enforcing to cast a Serde<V> to Serde<VR> for XXStream / Table.aggregate, for which the returned value type is NOT known, such the enforced casting should not be applied and we should require users to provide us the value serde if they believe the default ones are not applicable.
2.d) Whenever we are creating a new MaterializedInternal we are effectively incrementing the suffix index for the store / processor-node names. However in some places this MaterializedInternal is only used for validation, so the resulted processor-node / store suffix is not monotonic.
Committer Checklist (excluded from commit message)

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

@mjsax @bbejeck @vvcephei this PR is ready for reviews now.

Failure unrelated, exceded rate limit.
Retest this please

@mjsax I understand this is a large PR... I've tried hard to make it into multiple smaller ones (I'll probably have two other PRs at about similar sizes) while the hope is that for this PR, most of the removals are straight forward except the fixes mentioned in 2).
Regarding your question about inheritance: I did this for the following reasons:
a) Before KIP-182 we are actually doing sth. already about the inheritance, but only for count and reduce; when we add KIP-182 we mistakenly dropped some of those.
b) For aggregations, i.e. from grouped stream / grouped table / time windowed grouped stream, the only following operation is aggregation; while for other operators like stream().to() we need to decide whether to inherit based on the actual operator, which is more tricky. I do have plans to enhance the inheritance of serdes once we have removed the deprecation though (that was part of the plan for post-KIP182 anyways) but I want separate that general enhancement from this smaller scoped feature.
c) Scala API is actually relying on the fix above to make strong typing strict. So I want to make sure this part does make it to 2.0 release along with the Scala API.


Flex volume API and Improved lifecycle (flexvolume)

Description
Existing flex volume plugin enables administrators/vendors to create out-of-tree volume plugins, i.e., plugins which do not reside in Kubernetes project. But, it has the following gaps.
It lacks support for the latest enhancements to in-tree plugins like dynamic provisioning and centralized attach-detach controller
It does not define a stable driver api for administrators/vendors to work.
The current flex volume plugin deployment model is not suitable for environments like GCE & CoreOS, where access to the root file system is restricted. And in other environments the overall user experience is poor, as it requires manual installation of the plugin on every node and restart of kubelets & controller manager.
Progress Tracker

[ ] Before Alpha

[ ] Write and maintain draft quality doc

[ ] During development keep a doc up-to-date about the desired experience of the feature and how someone can try the feature in its current state. Think of it as the README of your new feature and a skeleton for the docs to be written before the Kubernetes release. Paste link to Google Doc: DOC-LINK

[ ] Design Approval

[ ] Design Proposal.  This goes under docs/proposals.  Doing a proposal as a PR allows line-by-line commenting from community, and creates the basis for later design documentation.  Paste link to merged design proposal here: PROPOSAL-NUMBER
[ ] Decide which repo this feature's code will be checked into. Not everything needs to land in the core kubernetes repo. REPO-NAME
[ ] Initial API review (if API).  Maybe same PR as design doc. PR-NUMBER

Any code that changes an API (/pkg/apis/...)
cc @kubernetes/api

[ ] Identify shepherd (your SIG lead and/or<EMAIL_ADDRESS>will be able to help you). My Shepherd is<EMAIL_ADDRESS>(and/or GH Handle)

A shepherd is an individual who will help acquaint you with the process of getting your feature into the repo, identify reviewers and provide feedback on the feature. They are not (necessarily) the code reviewer of the feature, or tech lead for the area.
The shepherd is not responsible for showing up to Kubernetes-PM meetings and/or communicating if the feature is on-track to make the release goals. That is still your responsibility.

[ ] Identify secondary/backup contact point. My Secondary Contact Point is<EMAIL_ADDRESS>(and/or GH Handle)

[ ] Write (code + tests + docs) then get them merged.  ALL-PR-NUMBERS

[ ] Code needs to be disabled by default.   Verified by code OWNERS
[ ] Minimal testing
[ ] Minimal docs

cc @kubernetes/docs on docs PR
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
New apis: Glossary Section Item in the docs repo: kubernetes/kubernetes.github.io

[ ] Update release notes

[ ] Before Beta

[ ] Testing is sufficient for beta
[ ] User docs with tutorials

Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
cc @kubernetes/docs on docs PR
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

[ ] Thorough API review

cc @kubernetes/api

[ ] Before Stable

[ ] docs/proposals/foo.md moved to docs/design/foo.md

cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

[ ] Soak, load testing
[ ] detailed user docs and examples

cc @kubernetes/docs
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers.
FEATURE_STATUS: IN_DEVELOPMENT
More advice:
Design

Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Coding

Use as many PRs as you need.  Write tests in the same or different PRs, as is convenient for you.
As each PR is merged, add a comment to this issue referencing the PRs.  Code goes in the http://github.com/kubernetes/kubernetes repository,
and sometimes http://github.com/kubernetes/contrib, or other repos.
When you are done with the code, apply the "code-complete" label.
When the feature has user docs, please add a comment mentioning @kubernetes/feature-reviewers and they will
check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
testing.  They won't do detailed code review: that already happened when your PRs were reviewed.
When that is done, you can check this box and the reviewer will apply the "code-complete" label.

Docs

[ ] Write user docs and get them merged in.
User docs go into http://github.com/kubernetes/kubernetes.github.io.
When the feature has user docs, please add a comment mentioning @kubernetes/docs.
When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.

@gr4701 @thockin @philips Create new Feature request for Flex volume proposals:
https://github.com/kubernetes/kubernetes/issues/32543
https://github.com/kubernetes/kubernetes/issues/32550

@chakri-nelluri can you provide the actual status of the feature? Which SIG is responsible for it?

@kubernetes/sig-storage is responsible for this feature.
It is not part of 1.5

@saad-ali thank you!

@saad-ali which release does this feature target and which stage (alpha/beta/stable)?

@idvoretskyi alpha in 1.6

@chakri-nelluri @mdelio please, provide us with the release notes and documentation PR (or links) at https://docs.google.com/spreadsheets/d/1nspIeRVNjAQHRslHQD1-6gPv99OcYZLMezrBe3Pfhhg/edit#gid=0

Pingity ping. Is there a Docs PR for this?  Is one needed?

@jaredbhatti is this enough for docs: https://github.com/kubernetes/kubernetes/pull/43326  or do we need a PR against kubernetes/kubernetes.github.io also?

This looks like a pretty sizable feature that folks around going to want to
know about. The current documentation is pretty slim, but if the readme is
enough for current users, I'm fine with it.
This is what exists now:
https://kubernetes.io/docs/user-guide/volumes/#flexvolume
On Fri, Mar 17, 2017 at 3:04 PM, bradley childs<EMAIL_ADDRESS>wrote:

@jaredbhatti https://github.com/jaredbhatti is this enough for docs:
kubernetes/kubernetes#43326
https://github.com/kubernetes/kubernetes/pull/43326 or do we need a PR
against kubernetes/kubernetes.github.io also?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/features/issues/93#issuecomment-287482828,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF3Lgt4nUsb7TXu-oXINjaaiMIfvhLBfks5rmwN4gaJpZM4J8Hyy
.

@jaredbhatti more documentation is at:
https://github.com/kubernetes/kubernetes/tree/master/examples/volumes/flexvolume
The open PR https://github.com/kubernetes/kubernetes/pull/43326 updates
this documentation to reflect 1.6 changes.
Let me know if there is any other place holder to include this
documentation. I will update it.
Thanks
~Chakri
On Fri, Mar 17, 2017 at 3:32 PM, Jared<EMAIL_ADDRESS>wrote:

This looks like a pretty sizable feature that folks around going to want to
know about. The current documentation is pretty slim, but if the readme is
enough for current users, I'm fine with it.
This is what exists now:
https://kubernetes.io/docs/user-guide/volumes/#flexvolume
On Fri, Mar 17, 2017 at 3:04 PM, bradley childs<EMAIL_ADDRESS>wrote:

@jaredbhatti https://github.com/jaredbhatti is this enough for docs:
kubernetes/kubernetes#43326
https://github.com/kubernetes/kubernetes/pull/43326 or do we need a PR
against kubernetes/kubernetes.github.io also?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/kubernetes/features/issues/93#issuecomment-287482828
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AF3Lgt4nUsb7TXu-
oXINjaaiMIfvhLBfks5rmwN4gaJpZM4J8Hyy>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/features/issues/93#issuecomment-287487639,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJdfb7H6oqRES-yRSoLpvccAffToIcccks5rmwoYgaJpZM4J8Hyy
.

@chakri-nelluri, please confirm with @saad-ali and @devin-donnelly that no updates are needed to the user facing documentation at k8s.io.
cc: @ethernetdan, @kubernetes/release-team

/close

@chakri-nelluri Where is this feature or its successor now tracked?

@luxas
After I check this feature. It seems that these two feature are both abandoned.

Hi @luxas this will be superseded by CSI. https://github.com/container-storage-interface/spec

@chakri-nelluri So https://github.com/kubernetes/features/issues/178 is the successor, right?

@luxas. Yes #178 is the successor. Thanks


[v6] Following migration guide results in Module not found: Error: Can't resolve 'history' in ....

Node version: v12.18.2
npm version: 6.14.5
I've followed the migration steps outlined here: https://github.com/ReactTraining/react-router/blob/dev/docs/advanced-guides/migrating-5-to-6.md#upgrade-to-react-router-v6
Installation seems to go fine, but when I try to actually run my app locally (using webpack-dev-server) I get:
ERROR in ./node_modules/react-router/index.js
Module not found: Error: Can't resolve 'history' in '/.........../node_modules/react-router'
 @ ./node_modules/react-router/index.js 1:0-58 3:110-129 8:79-85 16:61-70 21:62-71
 @ ./node_modules/react-router-dom/index.js
 @ ./client/index.js

ERROR in ./node_modules/react-router-dom/index.js
Module not found: Error: Can't resolve 'history' in '/.........../node_modules/react-router-dom'
 @ ./node_modules/react-router-dom/index.js 1:92-163 4:85-105 5:85-102 6:427-437 6:443-453
 @ ./client/index.js

I don't think it's related to webpack-dev-server as running webpack --mode production also results in the same error. The relevant packages I have listed in my package.json:
    "react": "^16.13.0",
    "react-router": "^6.0.0-beta.0",
    "react-router-dom": "^6.0.0-beta.0",

Really like the new v6 API so any help here would be greatly appreciated.
Thanks!

You need to also install the history library. I added a note about this to the docs.

Great, thank you.


Fuzzy history matching

Hi,
I love hh, it has changed they way I work with my shell!
That being said, I would love to have fuzzy history matching. More often than not I am searching the history for calls like this:
$ program --param1 path --param2
I would love to search like this:
search: prog --param2
and get the correct result.
Thx and keep up the great work.

Did you try keyword style search? If not, add to your environment configuration variable keywords setting:
export HH_CONFIG=hicolor,keywords

First try it in current shell, they you may want to add it e.g. to .bashrc. IMO this settings changes search in the way you described - I use hh with this configuration myself. For more details please refer to man hh.
Thank you for kind words - I really appreciate it! :+1:

Wow, yeah that's exactly what I was looking for. I checked the man page but for some reason didn't find it. Maybe I was too focused on the term "fuzzy". :) Thx a lot!

:smile:

Would it be possible to have truly fuzzy search? Eg, using the examplle above, typing propar2 would still match that command.


add the ability to addTextField

Can we add a textfield just like the default alert controller?

By default no, but you can try to add a UITextField inside the stack view (alertActionStackView).
Let me know.
-Paolo

@hadiyazdi did you try it? Did it work?


Amend 920300 to exclude CONNECT requests

After some research*, it seems that HTTP CONNECT requests typically do not include an Accept request header.
A user with a web application making use of the CONNECT method would find that (at PL 3) rule 920300 causes false positives. This is because rule 920300 expects all requests to feature an Accept header (with the exception of OPTIONS requests and requests with a User-Agent of either "AppleWebKit" or "Android").
This PR:

adds the CONNECT method as an additional exemption, next to the OPTIONS method which is already exempt;
adds three new tests:

one covering the newly exempt CONNECT method;
one covering the exempt OPTIONS method;
and one covering an exempt User-Agent containing the string "AppleWebKit".

*Sources

RFC 7231 provides examples of CONNECT requests, none of which feature an Accept header.

Mozilla's documentation of HTTP methods includes an example of a valid CONNECT request which does not feature an Accept header.

Constructing a valid HTTP CONNECT request using cURL does not include an Accept request header:

$ curl -v -o/dev/null -p -x localhost:80 http://test.com
...
> CONNECT test.com:80 HTTP/1.1
> Host: test.com:80
> User-Agent: curl/7.79.1
> Proxy-Connection: Keep-Alive
...

I believe this PR is ready to go.


Margin not supported in .html()

With sample provided for auto page split in repo, I tried using .html() method, I am unable to use margin. I tried this code (adding keys margin / margins) -
var pdf = new jsPDF("p", "pt", "letter");
pdf.html(document.getElementById("html"),{ margin : [50, 50, 50, 50], callback: function(pdf) {
                var iframe = document.createElement("iframe");
                iframe.setAttribute('style','position:absolute;right:0; top:0; bottom:0; height:100%; width:500px');
                document.body.appendChild(iframe);
                iframe.src = pdf.output('datauristring');
            }
});

Any alternative ?

Any alternative ?
No.

Dont know what you mean with "auto page split" in connection with html()-method.

Dont know what you mean with "auto page split" in connection with html()-method.

I was referring to one of the sample in the repository auto_break.html

Duplicate of #1176