moby + Azure CNI

Getting inconsistent HPA results from moby + Azure CNI clusters.
$ kubectl describe hpa php-apache-kubernetes-westus2-8241-79058
Name:                                                  php-apache-kubernetes-westus2-8241-79058
Namespace:                                             default
Labels:                                                <none>
Annotations:                                           <none>
CreationTimestamp:                                     Tue, 16 Oct 2018 17:36:42 +0000
Reference:                                             Deployment/php-apache-kubernetes-westus2-8241-79058
Metrics:                                               ( current / target )
  resource cpu on pods  (as a percentage of request):  0% (0) / 5%
Min replicas:                                          1
Max replicas:                                          10
Conditions:
  Type            Status  Reason            Message
  ----            ------  ------            -------
  AbleToScale     True    ReadyForNewScale  the last scale time was sufficiently old as to warrant a new scale
  ScalingActive   True    ValidMetricFound  the HPA was able to successfully calculate a replica count from cpu resource utilization (percentage of request)
  ScalingLimited  True    TooFewReplicas    the desired replica count is increasing faster than the maximum scale rate
Events:
  Type     Reason                        Age              From                       Message
  ----     ------                        ----             ----                       -------
  Warning  FailedGetResourceMetric       7m (x2 over 8m)  horizontal-pod-autoscaler  unable to get metrics for resource cpu: no metrics returned from resource metrics API
  Warning  FailedComputeMetricsReplicas  7m (x2 over 8m)  horizontal-pod-autoscaler  failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

@cpuguy83 @ksaur @khenidak  FYI, we can troubleshoot this here

@jackfrancis  Let me know if you want us to take a look at something from Azure CNI side.

This is an odd error, because metrics are working, I can see them in /apis/metrics.k8s.io/v1beta1/nodes and /apis/metrics.k8s.io/v1beta1/pods.... although it is saying that cpu usage is 0.
    {
      "metadata": {
        "name": "php-apache-kubernetes-westus2-8241-79058-664bf4b6c4-xc8x4",
        "namespace": "default",
        "selfLink": "/apis/metrics.k8s.io/v1beta1/namespaces/default/pods/php-apache-kubernetes-westus2-8241-79058-664bf4b6c4-xc8x4",
        "creationTimestamp": "2018-10-16T18:30:47Z"
      },
      "timestamp": "2018-10-16T18:30:00Z",
      "window": "1m0s",
      "containers": [
        {
          "name": "php-apache-kubernetes-westus2-8241-79058",
          "usage": {
            "cpu": "0",
            "memory": "9292Ki"
          }
        }
      ]
    },

But these metrics (cpu and mem) are collected from the same endpoint on the kubelet... if it wasn't able to collect one then it wouldn't be able to collect the other...
Meanwhile, the kubelet is reporting > 0 cpu usage:

 {
    "podRef": {
      "name": "php-apache-kubernetes-westus2-8241-79058-664bf4b6c4-xc8x4",
      "namespace": "default",
      "uid": "f8a17d74-d169-11e8-bdaf-000d3afd17c7"
    },
    "startTime": "2018-10-16T17:36:11Z",
    "containers": [
      {
        "name": "php-apache-kubernetes-westus2-8241-79058",
        "startTime": "2018-10-16T17:36:14Z",
        "cpu": {
          "time": "2018-10-16T18:38:44Z",
          "usageNanoCores": 23545,
          "usageCoreNanoSeconds": 163200183
        },
        "memory": {
          "time": "2018-10-16T18:38:44Z",
          "usageBytes": 9519104,
          "workingSetBytes": 9515008,
          "rssBytes": 5947392,
          "pageFaults": 3427,
          "majorPageFaults": 0
        },
        "rootfs": {
          "time": "2018-10-16T18:38:44Z",
          "availableBytes":<PHONE_NUMBER>4,
          "capacityBytes":<PHONE_NUMBER>2,
          "usedBytes": 45056,
          "inodesFree": 3698854,
          "inodes": 3840000,
          "inodesUsed": 9
        },
        "logs": {
          "time": "2018-10-16T18:38:44Z",
          "availableBytes":<PHONE_NUMBER>4,
          "capacityBytes":<PHONE_NUMBER>2,
          "usedBytes": 28672,
          "inodesFree": 3698854,
          "inodes": 3840000,
          "inodesUsed": 141146
        },
        "userDefinedMetrics": null
      }
    ],
    "cpu": {
      "time": "2018-10-16T18:38:41Z",
      "usageNanoCores": 23795,
      "usageCoreNanoSeconds": 176395954
    },
    "memory": {
      "time": "2018-10-16T18:38:41Z",
      "usageBytes": 10035200,
      "workingSetBytes": 10031104,
      "rssBytes": 5996544,
      "pageFaults": 0,
      "majorPageFaults": 0
    },
    "network": {
      "time": "2018-10-16T18:38:34Z",
      "name": "eth0",
      "rxBytes": 236778,
      "rxErrors": 0,
      "txBytes": 53738,
      "txErrors": 0,
      "interfaces": [
        {
          "name": "eth0",
          "rxBytes": 236778,
          "rxErrors": 0,
          "txBytes": 53738,
          "txErrors": 0
        }
      ]
    },
    "volume": [
      {
        "time": "2018-10-16T17:36:12Z",
        "availableBytes":<PHONE_NUMBER>,
        "capacityBytes":<PHONE_NUMBER>,
        "usedBytes": 12288,
        "inodesFree": 892135,
        "inodes": 892144,
        "inodesUsed": 9,
        "name": "default-token-qzsfz"
      }
    ],
    "ephemeral-storage": {
      "time": "2018-10-16T18:38:44Z",
      "availableBytes":<PHONE_NUMBER>4,
      "capacityBytes":<PHONE_NUMBER>2,
      "usedBytes": 73728,
      "inodesFree": 3698854,
      "inodes": 3840000,
      "inodesUsed": 9
    }
  }

Also now these events are gone for some reason.


Usage of System.Data.SqlClient requires Xamarin License

I would like to use the CSV parsing to allow bulk data import into a Xamarin app. Sadly I only have the Indie Version of Xamarin, which forbids the usage of System.Data.SqlClient. Would it be possibe to somehow remove that functionally in a mobile build? There is a more or less undocumented __MOBILE__ preprocessor directive that could be used to omit that reference.

Hi @MarcusRiemer can you check this build:
http://www.filedropper.com/filehelpersnodatalink
It has no Datalink feature, so no SqlClient Usage.
I don't do mobile programming with Xamarin, but if you help me I have no problem to make the lib mobile compatible, and optimize it
Thanks

@MarcusRiemer Any news about the version I uploaded ?
Thanks

Since release 3.3 we ship a net standard 2.0 binary.
That should solve your problem.
Matthias


java.lang.NoSuchFieldError: de.kherud.llama.InferenceParameters.antiPrompt [Ljava/lang/String;

Just like the issues #26 #30 #27 I had this issue on a Linux machine (amd64).
From the failed pipeline on github I added the artifacts that were build with success and changed the path paramter.
But this will result in the following error:
java.lang.NoSuchFieldError: de.kherud.llama.InferenceParameters.antiPrompt [Ljava/lang/String;
    at jdk.internal.loader.NativeLibraries.load (Native Method)
    at jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open (NativeLibraries.java:331)
    at jdk.internal.loader.NativeLibraries.loadLibrary (NativeLibraries.java:197)
    at jdk.internal.loader.NativeLibraries.loadLibrary (NativeLibraries.java:139)
    at java.lang.ClassLoader.loadLibrary (ClassLoader.java:2418)
    at java.lang.Runtime.load0 (Runtime.java:852)
    at java.lang.System.load (System.java:2021)
    at de.kherud.llama.LlamaLoader.loadNativeLibrary (LlamaLoader.java:162)
    at de.kherud.llama.LlamaLoader.loadNativeLibrary (LlamaLoader.java:106)
    at de.kherud.llama.LlamaLoader.initialize (LlamaLoader.java:66)
    at de.kherud.llama.LlamaModel.<clinit> (LlamaModel.java:29)
    at nl.enimatek.llama.chat.Main.main (Main.java:16)
    at org.codehaus.mojo.exec.ExecJavaMojo.lambda$execute$0 (ExecJavaMojo.java:283)
    at java.lang.Thread.run (Thread.java:1583)

I also 'rebuild' the whole project including the llama-ccp on my M2 macbook where the current Maven-jar -does- work, but rebuilding it gives the same result as the above.
So I think, even after getting the pipeline to publish the updated llama libraries (that is now causing all the above mentioned open issues), the JNI will break anyways, maybe because of an update in the llama-ccp? - I'm not proficient in c++/jni enough atm, and the reason for me to use this library ;)

This probably has to do with a difference in "antiprompt" in the jni definition and "antiPrompt" with capital P in the Java class definition. I had the same issue when using the library as a maven dependency. Using the code from the repo in my project works for me, together with building the shared library.

I just released version 3.0 and this should be fixed. Note, that the naming changed to `InferenceParameters#setStopStrings(String[]).


Re-Evaluate Higher Explainability Models

Details
Several models initially excluded should now be re-evaluated due to the higher degree of explainability and interpretability inherent in their architectures, compared to currently higher performing alternatives.


V8 consolidated: Consolidated sdk changes for web-client to move to v8

Will open another PR after merging the code.


Cleanup tests

Closes #1696

How about doing tests/integration/cairo1 instead of tests/integration/cairo1_tests, it's obvious there are going to be tests there, right?

Eventually I want to name it just cairo1, but the directory like this already exists so resolving possible conflicts between this PR and master is not going to be nice. I'll rename it before the merge.

Also, why commands dir is outside of the main Cairo 1 directory (next to it to be precise)? I'd put it inside of it.

There are commands which aren't directly related to cairo1 and I don't think it makes much sense to split it between cairo0 and 1 commands directories, since some are shared between versions.

Can we prioritize merging this one above anything elese? It will be very prone to merge conflicts


Add build tag to enable OSTRACE() logging

This pull request adds the sqlite_os_trace build tag which sets the following compilation flags:

SQLITE_FORCE_OS_TRACE=1
SQLITE_DEBUG_OS_TRACE=1

This produces verbose debugging output of every operating system call made by SQLite. These two flags are the same as the flags set in Makefile.msc in the SQLite repository:
https://github.com/sqlite/sqlite/blob/cf2ad7ae3652a3fc47d3625a9bf44e5239b4d35f/Makefile.msc#L837-L840

Codecov Report

Merging #1067 (eed275a) into master (3ccccfb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1067   +/-   ##
=======================================
  Coverage   46.29%   46.29%
=======================================
  Files          11       11
  Lines        1499     1499
=======================================
  Hits          694      694
  Misses        666      666
  Partials      139      139

Continue to review full report at Codecov.

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

Thank you

Thanks, @mattn!


Alert LonghornNodeDown example in documentation doesn't work.

@Turb0Fly commented on Sat Sep 25 2021
The prometheus alert LonghornNodeDown as seen on https://longhorn.io/docs/1.2.0/monitoring/alert-rules-example/ does not work.
longhorn_node_total - (count(longhorn_node_status{condition="ready"}==1) OR on() vector(0))
The metric longhorn_node_total does not exist. When querying the metrics , longhorn_node_count_total is there.  However, replacing the metric with the correct one in the expression does not work either.  When forcing a node down, the alert is never fired but querying the metric gets the correct value.
Using Longhorn 1.1.0
Rancher 2.5.8
Rancher Monitoring 14.5.100
We need an expression that will fire only when a node is not ready and not just on count, e.g. getting an alert when value is 0.
FWIW, I came up with something that works :
(avg(longhorn_node_count_total) or on() vector(0)) - (count(longhorn_node_status{condition="ready"} == 1) or on() vector(0)) > 0

@github-actions[bot] commented on Tue Nov 16 2021
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions[bot] commented on Mon Nov 22 2021
This issue was closed because it has been stalled for 5 days with no activity.

@jenting commented on Thu Mar 10 2022
Issue moved to longhorn/longhorn #3729 via ZenHub

It's a duplicate issue, close it.


Insufficient specification

Issue in help/using/integration/receiving-audience-data/real-time-outbound-transfers/real-time-outbound-transfers.md
There is no information about how the request should look like. Only the response is specified.

Thanks for pointing this out. We're investigating and will update the documentation.

We've updated the documentation to better reflect the specification.
Thanks again for reporting this.
Vlad Falon
Technical Writer
Adobe Audience Manager


cmsis_device_f1/Include/stm32f103xb.h line L4223-L4232 lose "TIM_CCER_CC4NP" define

Caution
The Issues are strictly limited for the reporting of problem encountered with the software provided in this project.
For any other problem related to the STM32 product, the performance, the hardware characteristics and boards, the tools the environment in general, please post a topic in the ST Community/STM32 MCUs forum.
Describe the set-up

The board (either ST RPN reference or your custom board)
IDE or at least the compiler and its version

Describe the bug
A clear and concise description of what the bug is.
How To Reproduce

Indicate the global behavior of your application project

The modules that you suspect to be the cause of the problem (Driver, BSP, MW ...)

The use case that generates the problem

How we can reproduce the problem

Additional context
If you have a first analysis or patch correction, thank you to share your proposal.
Screenshots
If applicable, add screenshots to help explain your problem.

Hi @kex2017,
TIM_CCER_CC4NP is not defined for STM32F103xx devices and it is not defined for any of the stm32F1XX devices. Actually, this bit definition was deleted from the STM32F1 cmsis device files since release v4.2.0.
You may also refer to the TIMx_CCER register mapping described in the  "capture/compare enable register (TIMx_CCER)" sections of the  STM32F103xx reference manual.
Please allow me then to close this thread. Thank you for your comprehension and thank you again for your contribution.
With regards,


reduce final size

Hi @epoberezkin
I really like ajv. Version 5 is great because I have no problem with webpack as well.
Currently I am trying to reduce bundle size of my projects and ajv took almost 196kb / 35kb minified gziped version.
Did you think about spliting your package? or do it more modular with ES6?
Currently I am using just very simple funcionality from ajv like required properties and min max values.
Thank you for your time

@seeden I'm not sure how Ajv can be split... Theoretically keywords can be plugins and optional, but I'm not sure I like this idea. In any case it is not related to using ES6.
For your application a better idea could be to precompile your schemas into modules using ajv-cli (that uses ajv-pack inside). It may result in a smaller bundle size (depending on the number and the size of schemas) as only a small portion of Ajv will be included in the compiled code.

@epoberezkin I am generating schemas on demand because they are dynamic

You can also try using some build tools that remove unused code - e.g. if there are some Ajv methods/functions you don't use it can be removed. It requires bundling Ajv together with your app, but it's easier than managing manually what should and shouldn't be included.

e.g. http://2ality.com/2015/12/webpack-tree-shaking.html

I am using webpack 2 (modules false) with uglify as well. But as I told the final size is 196kb / 35kb minified gziped version.

196kb not minified? in which case you already remove 25%
I can suggest forking and removing unused keywords from these two files:
https://github.com/epoberezkin/ajv/blob/master/lib/compile/_rules.js
https://github.com/epoberezkin/ajv/blob/master/lib/compile/rules.js
That should reduce the bundle substantially.
You can also contribute a script that automates generating bundle including only certain keywords (e.g. by updating and then restoring these files after the bundle is created).

This is now possible in v7 using AjvCore (import AjvCore from "ajv/dist/code") that does not import any keywords, so only the needed keywords can be added.
The size reduction is not as substantial as may be expected - Ajv without any keywords is approximately 35% smaller than Ajv with all draft-2019-09 keywords, and 30% smaller than with draft-7 keywords - the big part is the core logic that is required for all keywords.
A bigger potential to reduce the size could be to ship with compiled schemas (PR #1332 - in progress), but it depends on the number of schemas - a compiled validation code is bigger than the schema itself - so you have to do this estimation for your application.


Allow \Stringable in ID return type on ProcessedMessage

What about string|int|\Stringable|null? It needs to be scalar to access the details route

Yes, \Stringable would work just fine.

@kbond added \Stringable to the return type.

Thanks @balazscsaba2006!


Update generated resources using api schema

Summary by CodeRabbit

New Features

Improved type safety and clarity by updating parameter types from generic dictionaries to specifically typed dictionaries and lists in various classes.

Documentation

Streamlined and clarified docstrings for constructors, enhancing readability and reducing verbosity across multiple classes.

Refactor

Adjustments to type annotations and parameter structures to better align with common usage patterns and improve maintainability.

Report bugs in Issues
The following are automatically added:

Add reviewers from OWNER file (in the root of the repository) under reviewers section.
Set PR size label.
New issue is created for the PR. (Closed when PR is merged/closed)
Run pre-commit if .pre-commit-config.yaml exists in the repo.

Available user actions:

To mark PR as WIP comment /wip to the PR, To remove it from the PR comment /wip cancel to the PR.
To block merging of PR comment /hold, To un-block merging of PR comment /hold cancel.
To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
verified label removed on each new commit push.
To cherry pick a merged PR comment /cherry-pick <target branch to cherry-pick to> in the PR.

Multiple target branches can be cherry-picked, separated by spaces. (/cherry-pick branch1 branch2)
Cherry-pick will be started when PR is merged

To build and push container image command /build-and-push-container in the PR (tag will be the PR number).

You can add extra args to the Podman build command

Example: /build-and-push-container --build-arg OPENSHIFT_PYTHON_WRAPPER_COMMIT=<commit_hash>

To add a label by comment use /<label name>, to remove, use /<label name> cancel
To assign reviewers based on OWNERS file use /assign-reviewers
To check if PR can be merged use /check-can-merge

Supported /retest check runs

/retest tox: Retest tox
/retest python-module-install: Retest python-module-install

Supported labels

hold
verified
wip
lgtm

/verified

/lgtm


Modernize bash script

This improves a few things about the install script:

Set strict mode and check that there are no unset variables and fix instances of where that is currently the case
Use bash builtin conditional characters
Restructure the export file logic and only make it output to shell if EXPORT_FILE is unset

Fixes #113.

I think the CI failure isn't caused by this.

Thanks for the contribution! The CI failure is due to: https://github.com/esp-rs/esp-idf-sys/issues/99

Thanks for the contribution! The CI failure is due to: esp-rs/esp-idf-sys#99

Is this blocking this PR?

Thank you @svenstaro for a great improvement of the code. Initial tests seem to be ok. Let's include changes in the new installer for <IP_ADDRESS>, which will also contain several fixes to the compiler.

set -u seems to make the installer crash on macos with:
install-rust-toolchain.sh: line 141: POSITIONAL[@]: unbound variable

Using POSITIONAL="" in definition of POSTIONAL seems to solve it but I am not sure if there are any implications of this change.


Fix table heading

@Rayne after merging this I remembered the markdown file is generated.  So would also need to update :
https://github.com/keith-turner/ecoji/blob/d8dc1978ae6accdf84e28d47d6774c9fed634a52/markdown_test.go#L72
If you are interested in making that change feel free to make another PR.  If not I can update it.


Add Muse configuration file

This PR adds a configuration file for the Muse platform to run on Eureka. I was able to fix a few issues Muse found and my changes were recently accepted. I thought that the Eureka project would benefit from Muse analysis.
In addition to this configuration, a maintainer should install this app (free forever for open source): https://github.com/marketplace/muse-dev
This will enable Muse to scan incoming pull requests and report potentially introduced bugs into the diff. Please feel free to reach out if there is anything else I can help with 😄

Talked offline, we won't be enabling Muse at this very point, but looking forward to experimenting with it more in the future.


[Snyk] Security upgrade @angular-devkit/build-angular from 0.1102.19 to 13.0.0

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

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

frontend/package.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

768/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5
Uncontrolled resource consumption SNYK-JS-BRACES-6838727
Yes
Proof of Concept

661/1000  Why? Recently disclosed, Has a fix available, CVSS 7.5
Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

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

Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Uncontrolled resource consumption

Checkmarx One – Scan Summary & Details – 71bb34b7-0ad5-4fce-81c6-4e510dcd3dde
Policy Management Violations

Policy Name
Rule(s)
Break Build

No highs or mediums
No Highs or Mediums, level 3 strict
false

New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2022-23539
Npm-jsonwebtoken-0.1.0
Vulnerable Package

CVE-2022-23539
Npm-jsonwebtoken-0.4.0
Vulnerable Package

CVE-2022-23540
Npm-jsonwebtoken-0.1.0
Vulnerable Package

CVE-2022-23540
Npm-jsonwebtoken-0.4.0
Vulnerable Package

CVE-2022-25881
Npm-http-cache-semantics-3.8.1
Vulnerable Package

CVE-2022-25883
Npm-semver-7.3.5
Vulnerable Package

CVE-2022-25883
Npm-semver-7.3.4
Vulnerable Package

CVE-2022-25887
Npm-sanitize-html-1.4.2
Vulnerable Package

CVE-2022-3517
Npm-minimatch-3.0.4
Vulnerable Package

CVE-2023-26136
Npm-tough-cookie-2.5.0
Vulnerable Package

CVE-2023-29017
Npm-vm2-3.9.11
Vulnerable Package

CVE-2023-29199
Npm-vm2-3.9.11
Vulnerable Package

CVE-2023-30547
Npm-vm2-3.9.11
Vulnerable Package

CVE-2023-32314
Npm-vm2-3.9.11
Vulnerable Package

CVE-2023-32695
Npm-socket.io-parser-4.0.5
Vulnerable Package

CVE-2023-37466
Npm-vm2-3.9.11
Vulnerable Package

CVE-2023-37903
Npm-vm2-3.9.11
Vulnerable Package

CVE-2023-42282
Npm-ip-1.1.9
Vulnerable Package

CVE-2023-46233
Npm-crypto-js-3.3.0
Vulnerable Package

CVE-2024-29180
Npm-webpack-dev-middleware-5.3.0
Vulnerable Package

CVE-2024-4068
Npm-braces-2.3.2
Vulnerable Package

Cxc7705965-e0f0
<EMAIL_ADDRESS>Vulnerable Package

CVE-2022-23541
Npm-jsonwebtoken-0.1.0
Vulnerable Package

CVE-2022-23541
Npm-jsonwebtoken-0.4.0
Vulnerable Package

CVE-2022-36313
Npm-file-type-11.1.0
Vulnerable Package

CVE-2022-36313
Npm-file-type-6.2.0
Vulnerable Package

CVE-2022-36313
Npm-file-type-4.4.0
Vulnerable Package

CVE-2022-36313
Npm-file-type-3.9.0
Vulnerable Package

CVE-2022-36313
Npm-file-type-5.2.0
Vulnerable Package

CVE-2022-41940
Npm-engine.io-4.1.2
Vulnerable Package

CVE-2023-0842
Npm-xml2js-0.4.23
Vulnerable Package

CVE-2023-28155
Npm-request-2.88.2
Vulnerable Package

CVE-2023-32313
Npm-vm2-3.9.11
Vulnerable Package

CVE-2023-44270
Npm-postcss-7.0.39
Vulnerable Package

CVE-2023-44270
Npm-postcss-8.4.5
Vulnerable Package

CVE-2024-21501
Npm-sanitize-html-1.4.2
Vulnerable Package

CVE-2024-28863
Npm-tar-4.4.19
Vulnerable Package

CVE-2024-4067
Npm-micromatch-3.1.10
Vulnerable Package

CVE-2024-4067
Npm-micromatch-4.0.7
Vulnerable Package

Unpinned Actions Full Length Commit SHA
/lint-fixer.yml: [24](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/lint-fixer.yml# L24)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/codeql-analysis.yml: [18](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/codeql-analysis.yml# L18)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: [205](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/ci.yml# L205)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: [50](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/release.yml# L50)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/zap_scan.yml: [17](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/zap_scan.yml# L17)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: [145](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/ci.yml# L145)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: [123](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/ci.yml# L123)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: [62](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/release.yml# L62)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: [66](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/release.yml# L66)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/rebase.yml: [17](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/rebase.yml# L17)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: [203](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/ci.yml# L203)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: [221](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/ci.yml# L221)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: [266](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/ci.yml# L266)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: [64](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/release.yml# L64)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/update-challenges-www.yml: [24](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/update-challenges-www.yml# L24)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/codeql-analysis.yml: [20](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/codeql-analysis.yml# L20)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/update-news-www.yml: [20](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/update-news-www.yml# L20)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: [97](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/release.yml# L97)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: [249](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/ci.yml# L249)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/codeql-analysis.yml: [22](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/codeql-analysis.yml# L22)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: [83](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/ci.yml# L83)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: [72](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/release.yml# L72)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: [77](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/ci.yml# L77)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: [207](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/ci.yml# L207)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: [78](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//.github/workflows/release.yml# L78)
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Angular_Usage_of_Unsafe_DOM_Sanitizer
/frontend/src/app/score-board/score-board.component.ts: [175](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//frontend/src/app/score-board/score-board.component.ts# L175)
Attack Vector

Fixed Issues

Severity
Issue
Source File / Package

CVE-2020-28469
Npm-glob-parent-3.1.0

CVE-2021-23440
Npm-set-value-2.0.1

CVE-2021-23449
Npm-vm2-3.9.3

CVE-2021-23555
Npm-vm2-3.9.3

CVE-2021-35065
Npm-glob-parent-3.1.0

CVE-2021-35065
Npm-glob-parent-5.1.2

CVE-2021-44906
Npm-minimist-0.2.1

CVE-2022-21213
Npm-mout-1.2.3

CVE-2022-24771
Npm-node-forge-0.10.0

CVE-2022-24772
Npm-node-forge-0.10.0

Cx347a3da7-ba99
Npm-node-forge-0.10.0

Passwords And Secrets - Generic Password
/users.yml: [115](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L115)

Passwords And Secrets - Generic Password
/users.yml: [107](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L107)

Passwords And Secrets - Generic Password
/users.yml: [166](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L166)

Passwords And Secrets - Generic Password
/users.yml: [242](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L242)

Passwords And Secrets - Generic Password
/users.yml: [31](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L31)

Passwords And Secrets - Generic Password
/users.yml: [236](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L236)

Passwords And Secrets - Generic Password
/users.yml: [88](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L88)

Passwords And Secrets - Generic Password
/users.yml: [3](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L3)

Passwords And Secrets - Generic Password
/users.yml: [203](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L203)

Passwords And Secrets - Generic Password
/users.yml: [149](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L149)

Passwords And Secrets - Generic Password
/users.yml: [248](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L248)

Passwords And Secrets - Generic Password
/users.yml: [63](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L63)

Passwords And Secrets - Generic Password
/users.yml: [176](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L176)

Passwords And Secrets - Generic Password
/users.yml: [212](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L212)

Passwords And Secrets - Generic Password
/users.yml: [140](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L140)

Passwords And Secrets - Generic Password
/users.yml: [123](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L123)

Passwords And Secrets - Generic Password
/users.yml: [158](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L158)

Passwords And Secrets - Generic Secret
/users.yml: [150](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//data/static/users.yml# L150)

Passwords And Secrets - Google OAuth
/default.yml: [57](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//config/default.yml# L57)

CVE-2022-0122
Npm-node-forge-0.10.0

CVE-2022-24773
Npm-node-forge-0.10.0

Cx24228ad1-81fd
Npm-sanitize-html-1.4.2

Cx65603961-769c
Npm-debug-3.1.0

Cx65603961-769c
Npm-debug-2.6.9

Cxb41ee3b9-e4b0
Npm-adm-zip-0.4.16

Host Namespace is Shared
/docker-compose.test.yml: [3](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//docker-compose.test.yml# L3)

Host Namespace is Shared
/docker-compose.test.yml: [7](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//docker-compose.test.yml# L7)

Networks Not Set
/docker-compose.test.yml: [3](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//docker-compose.test.yml# L3)

Networks Not Set
/docker-compose.test.yml: [7](https://github.com/tyleragypt/juice-shop/blob/snyk-fix-65574c84117160dc904a36aed2e37551//docker-compose.test.yml# L7)


Run non-Python commands / Ansible raw module support

Following on from #419, the following work item remains:

Command line building. To handle Ansible's raw action, we need to be able to turn connection configs into command lines, and run those commands, including typing any passwords and suchlike as we do already.

Lots of pieces are in place for it now. Roughly what's left:

[ ] The per-connection BootstrapProtocol subclasses need to change, so they know somehow that they don't just run until MITO000 appears on the stream. They need to know how to feed stdin of the program with arbitrary data, and record its output in an 8-bit clean manner
[ ] Figure out if Connection wants to handle running custom commands, or it wants split up even more to handle just the 'start this stream and wait for it to disconnect' part.
[ ] Modify the existing HistoryMixin to handle collecting up a big chunk of potentially binary data, and maybe teach it about size limits or similar. Maybe re-work it so that it doesn't subclass DelimitedProtocol, but wraps the raw on_receive() instead.
[ ] Figure out the public API for it. Don't both with Router.ssh() etc. since they're going away anyway, make it something like mitogen.ssh.run(...), returning some kind of Receiver-like object that can be waited on etc.
[ ] Figure out how to make it work recursively using something like via=. This is needed for Ansible so raw: against a machine proxied via mitogen_via= is completely transparent.
[ ] Must preserve the ability for connection methods to continue typing passwords and understanding tool output as they do already.
[ ] Modify Ansible extension to use it. Connection.exec_command() seems to be where it wants to go, but this needs some heuristic or hard rule about when exec_command() should assume Python is installed on the remote and start a real connection, or when a raw command line should be run from the parent instead. It must always be consistent
[ ] Figure out how to enable Ansible 2.8's Python interpreter detection

User issue: #597

NB I rarely need raw command support, but when I do I just use env ANSIBLE_STRATEGY=free ansible-playbook ... and skip mitogen for this particular play.

FWIW, I just spent half an hour trying to figure out why ansible was complaining about not being able to find python when I was using the raw module. Mitogen turned out to be the issue. I've set "strategy: linear" in that playbook now. Thankfully it's a short one so mitogen didn't have much of an impact anyway.


[Bug] Improve CLI errors when namespace is incorrect

What are you really trying to do?

Any action in the CLI that involves specifying a namespace.
Describe the bug

When an incorrect namespace is provided, the CLI returns a pretty unhelpful error message similar to: Error: unable to run workflow: context deadline exceeded. Unfamiliar users to Temporal will not look to see if they're providing the correct namespace, and instead escalate to a central team to debug.
Minimal Reproduction

Run a command that requires taking -n namespace flag, but provide it a namespace that does not exist.
Environment/Versions

I think this is global behavior.
Additional context

Hi @robzienert, can you tell me which specific commands you've observed this with? I've tried with a couple different commands (e.g. temporal operator namespace describe and temporal workflow describe) and they all return namespace not found or similar errors. Thanks!

I'm also unable to reproduce this with workflow start and workflow execute:
❯ temporal workflow execute -n asdf --task-queue q --type foo
time=2024-06-18T16:41:09.619 level=ERROR msg="failed starting workflow: Namespace asdf is not found."

❯ temporal workflow start -n asdf --task-queue q --type foo
time=2024-06-18T16:41:14.306 level=ERROR msg="failed starting workflow: Namespace asdf is not found."

So to make any progress I'm going to need an example showing which command is at issue. Thanks!

Closing since I haven't heard back.
@robzienert If you're still seeing this in the latest version of the CLI (v0.13.1), please feel free to reopen, and let us know:

Exactly which command you were running that caused this
Which server you're running against (the dev-server? an on-prem setup? Temporal Cloud?) and which version of the server (if you know)


Duplicate Id error

× Duplicate ID: 7238e60d-2e38-4742-ac61-159746755e20
But there are no duplicate ids.
Quiz failed to validate: file.toml                                                                         │
│2024-09-05 11:31:39 [ERROR] (mdbook::utils): Error: The "quiz" preprocessor exited unsuccessfully with exit status: 1 status

Oh are you embedding the same quiz in two different places or pages? That's a but then, we shouldn't mark those as duplicates.

Oh are you embedding the same quiz in two different places or pages?

Yes.

This will be fixed in the next release!


_layouts are excluded from git, yet are checked in

The .ignore plugin in IntelliJ warns that there are some files under version control that are covered by .gitignore patterns.
These include

_layouts/homepage.html
_layouts/default.html

Sure enough, .gitignore includes the following entries:
# ignore github pages file and site.
_site/**
_layouts/**
Gemfile

Either
a) these files are valid - in which case .gitignore needs updating to not exclude them
OR
b) These files are not valid - in which case they should be deleted from source control
@jmertic - do you happen to know? I am not family with the website setup

I think that at least _layouts may need to be removed from .gitignore, as the website uses this to show the different layouts you see on http://egeria.odpi.org (ie. main page is different from sub-pages due to different layouts).
That said, I suspect these are needed in a specific branch that GitHub itself uses for displaying the website -- which may not be master...  Not sure that we could .gitignore from just master and leave them in the other branch, though (?)

I've removed from .gitignore as these files appear to be valid for GitHub pages. PR open

@planetf1 just a heads-up, you are aware that you can describe the PR with a comment like fixes #1234 or resolves #1234 (where 1234 is the issue number), and when the PR is merged it will automatically close the issue as well?
That saves you needing to manually close things + doing so before the PR is merged 😉


custom_folders folder structure

Here comes the new flag custom_folders which enables you to easily restructure your output folders (idea from #204).
For example, I I made it this way that my final Scene goes to into the download folder as only one file. Everything else goes into a sub-directory called  "temp_movie_files". Structures can be defined in "default.cfg", and it looks like this:
[custom_folders]
media_dir = /home/jh/Downloads/temp_movie_files
video_dir = /home/jh/Downloads/temp_movie_files
tex_dir   = /home/jh/Downloads/temp_movie_files
text_dir  = /home/jh/Downloads/temp_movie_files
output_file = /home/jh/Downloads/XXX

What should not be merged is the file:
"hello.py" , that is only for testing.
Also line 432
for k, v in file_writer_config.items():
    print (k, '-->', v)

is only for testing purpose.

I am now one week on vacation without internet.
Before merging this, we/I should also have a look on how what I currently named XXX can be changed to the actual scene name

Hi @kolibril13, please let us know when you are back from vacation and able/willing to keep working on this. I'm closing this for now.

I just saw that the config.py changed a lot.
So what I would do now, is eighter this:

Update my local master branch
Rename my local custom_folders branch to custom_folders_old
make a new local branch custom_folders from the master branch
Carefully implement the changes.
Push the new local branch to the custom_folders
or this:
Close this pull request
make a new local branch custom_folders from the updated master branch
make a new pull request.

What is the cleaner way in this scenario?

Probably this:

git checkout custom_folders
Backup your current branch locally: git branch custom_folders_bkup (or with whatever name you want)
git fetch origin to get the latest versions of all other branches
git merge master to update custom_folders with the changes on master.

You may have merge conflicts that you'll have to resolve after this. Try using git mergetool or a conflict resolver in your IDE. You can then commit and push to your custom_folders branch, and your changes will appear in this PR.

Hi @kilacoda, thanks for your instruction.
Especially with the merging process and conflict resolving in my IDE (pycharm), I often feel very confused, so I decided to make a new branch from the master and then picked up the parts I need by hand.

@kolibril13 thanks for the update. Since you are starting a new branch/PR, I'm deleting this one.

Ok! :+1:


[DebugInfo] Enable debug_scope_distinct.swift test

It was previously disabled in https://github.com/swiftlang/swift/pull/73373

Tagging @asl


validate directories

validating single files is possible with --f, it should alternatively be possible to recursively traverse through directories using --d
this apparently requires a new root node for the output report to remain xml compliant.
As an extra feature there could be nonverbose tabular output (e.g. only filename and validity) and a hit list, i.e. a summary at the end repeating which errors was present how often in the validated files, by error count descending.

no closed in mustangproject with actions validateExpectValid/validateExpectInvalid


Problems with setup:  attempt to index field 'grammar_guard' (a nil value)

It says [grammar-guard] The ltex language server has not been installed. Run :GrammarInstall to install it., this is not true, I have ltex-ls installed and in the path. I don't want to run the installer as I don't know what it does to my system, I would like to use my own installation.
In my init.vim I have this extension installed via vim-plug:
Plug 'brymer-meneses/grammar-guard.nvim'

lua require("lsp")

lsp.lua
  local nvim_lsp = require 'lspconfig'

  require('grammar-guard').init()

  nvim_lsp.grammar_guard.setup {
    settings = {
      ltex = {
        enabled = { 'latex', 'tex', 'bib', 'markdown' },
        language = 'en',
        diagnosticSeverity = 'information',
        setenceCacheSize = 2000,
        additionalRules = {
          enablePickyRules = true,
          motherTongue = 'en',
        },
        trace = { server = 'verbose' },
        dictionary = {},
        disabledRules = {},
        hiddenFalsePositives = {},
      },
    },
  }

But I get E5108: Error executing lua xxx/lsp.lua:17: attempt to index field 'grammar_guard' (a nil value)
PS I hope this pull request https://github.com/neovim/nvim-lspconfig/pull/863 gets sorted soon, I am trying this extension until then.
I tried with Neovim 0.5.1 and the master, Thanks!

Now ltex-lsp is in nvim-lspconfig I assume grammar-guard is going to need a major update, so this issue is probably irrelevant,  I will close it.


Margin changes since 7.9.2

The margin on the content (not header/footer) changes since the last version (7.9.2) on the generation html to pdf with Chromium.
Do you have more informations? A new parameter? Different resolution? Different default values?
See the screens:
7.9.1

7.9.2

The height of header & footer seems to be different too.

Hello @ytilotti,
Thanks for the heads up!  No idea about what’s going on there... I did not change anything related to margins. I suspect a new behavior (or bug?) in Chromium. The cdproto dependency has been updated also, but it is auto-generated so I don’t suspect a breaking change here.

I check the issues on Chromium, there are feedbacks margin on 117.
But don't know if the same issue.
For the moment, I've made some modifications on margins for using 7.9.2.
I'll be careful on the next update. There are corrections to margins in version 119 (beta)

Yep, sorry about that. It's kinda hard to keep everything updated while also guaranteeing semver "fidelity".

It's not in your responsability, no problem.
But I'm having trouble understanding the modification of header and footer margins because we can't configure it outside css.
No change generation html to pdf on your side?

Nothing, just dependencies updates.

No, I mean "No change generation html to pdf on your side" on your tests?

I'm closing this for now. Alas, there is nothing I can really do there 😅

Hi @gulien. No Chromium update since?

New version is 119.0.6045.159, so with some luck they did fix this issue.

Any news about this Issue?
Is there a common workaround?
I also reported this issue to chromium: 41487881
They don't seem to be able to reproduce.

I did not change anything code wise, maybe there were some changes in the ChromeDevTools protocol? I'm using the chromedp/chromedp library.


Investigate why goreleaser gh action is failing on arm64 build

• docker images
    • building docker image                          image=ghcr.io/adobe/k8s-shredder:v0.1.8-arm64v8
    • building docker image                          image=ghcr.io/adobe/k8s-shredder:v0.1.8-amd64
    • took: 5s
  ⨯ release failed after 9m1s                error=docker build failed: failed to build ghcr.io/adobe/k8s-shredder:v0.1.8-arm64v8: exit status 1: #1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 671B done
#1 DONE 0.0s

#2 [internal] load .dockerignore
#2 transferring context: 2B done
#2 DONE 0.0s

#3 [internal] load metadata for docker.io/library/alpine:latest
#3 DONE 0.8s

#4 [show_me_your_security 1/2] FROM docker.io/library/alpine@sha256:124c7d2707904eea7431fffe9[152](https://github.com/adobe/k8s-shredder/actions/runs/4620283707/jobs/8170164708#step:6:153)2a01e5a861a624ee31d03372cc1d138a3126
#4 resolve docker.io/library/alpine@sha256:124c7d2707904eea7431fffe91522a01e5a861a624ee31d03372cc1d138a3126 0.0s done
#4 sha256:124c7d2707904eea7431fffe91522a01e5a861a624ee31d03372cc1d138a3126 1.64kB / 1.64kB done
#4 sha256:b5a5b7ce4eabc8414bf367761a28f4e8b16952ce5de537c15ed917b71b245f11 528B / 528B done
#4 sha256:51e60588ff2cd9f45792b23de89bfface0a7fbd711d17c5f5ce900a4f6b16260 1.49kB / 1.49kB done
#4 sha256:c41833b44d910632b415cd89a9cdaa4d62c9725dc56c99a7ddadafd6719960f9 3.26MB / 3.26MB 0.2s done
#4 extracting sha256:c41833b44d910632b415cd89a9cdaa4d62c9725dc56c99a7ddadafd6719960f9
#4 extracting sha256:c41833b44d910632b415cd89a9cdaa4d62c9725dc56c99a7ddadafd6719960f9 0.4s done
#4 DONE 0.6s

#5 [internal] load build context
#5 transferring context: 38.15MB 0.9s done
#5 DONE 1.2s

#6 [show_me_your_security 2/2] RUN apk add --no-cache ca-certificates
#6 0.631 exec /bin/sh: exec format error
#6 ERROR: executor failed running [/bin/sh -c apk add --no-cache ca-certificates]: exit code: 1
------
 > [show_me_your_security 2/2] RUN apk add --no-cache ca-certificates:
#6 0.631 exec /bin/sh: exec format error
------
ERROR: failed to solve: executor failed running [/bin/sh -c apk add --no-cache ca-certificates]: exit code: 1

Learn more at https://goreleaser.com/errors/docker-build

If still valid, see more details in https://github.com/adobe/k8s-shredder/actions/runs/4620283707/jobs/8170164708

Done in https://github.com/adobe/k8s-shredder/commit/4a3ea27a150c2d964117e212aaac24298e4abf85


Add progress bars to transactions with expiries

Closes #321

adds progress bar
adds the icon from the designs
removes transaction link (ref)

Hijacked this branch to add an additional fix for our approvals check (f458981)

We now wait for supportedTokens to resolve before checking active token balances. This fixes a bug on the first page load on a new browser (because localStorage persists them otherwise) whereby all tokens will request allowance
To be extra sure, we also check to see if we have actually received an allowance figure in the allowance check. Previously we were checking something equivalent to: if (!allowances[token]) requiresApproval = true - instead we now set requiresApproval false in this case to prevent the user approving something they've already approved. We additionally set the error flag to tell the user to refresh the page. This should no longer happen though thanks to the change above and the changes last night in combination.


Introduce backend.result_type

[MOVED FROM KERAS CORE PR]
https://github.com/keras-team/keras-core/pull/938
Hi @fchollet
I want to verify whether this PR is on the right track.
I am attempting to implement a Keras Core version of result_dtype in keras/backend/common/dtypes.py.
Currently, the result matchs jnp.result_dtype when the input is python scalar types
(as demonstrated in keras_core/backend/common/dtypes_test.py)
If it is good, I will add more unit tests for result_dtype. Afterward, I can utilize it to refactor some of ops.numpy.* and add the previously mentioned tests.
WIP:

[x] Add backend.dtypes functionality
[x] Add unit tests
[x] Refactor ops.numpy (partially)

Codecov Report
Patch coverage: 57.20% and project coverage change: -21.24% :warning:

Comparison is base (1530666) 77.25% compared to head (c206043) 56.01%.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #18482       +/-   ##
===========================================
- Coverage   77.25%   56.01%   -21.24%
===========================================
  Files         331      332        +1
  Lines       31952    32131      +179
  Branches     6240     6290       +50
===========================================
- Hits        24685    17999     -6686
- Misses       5689    12697     +7008
+ Partials     1578     1435      -143

Flag
Coverage Δ

keras
56.01% <57.20%> (-21.15%)
:arrow_down:

keras-jax
?

keras-numpy
56.01% <57.20%> (-0.02%)
:arrow_down:

keras-tensorflow
?

keras-torch
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

keras/backend/torch/numpy.py
0.00% <0.00%> (-94.85%)
:arrow_down:

keras/backend/jax/numpy.py
38.44% <40.00%> (-59.56%)
:arrow_down:

keras/backend/tensorflow/numpy.py
37.21% <53.33%> (-56.96%)
:arrow_down:

keras/backend/common/dtypes.py
61.76% <61.76%> (ø)

keras/ops/numpy.py
93.81% <62.85%> (-0.61%)
:arrow_down:

keras/backend/numpy/numpy.py
97.32% <92.85%> (-0.25%)
:arrow_down:

keras/backend/__init__.py
65.00% <100.00%> (-29.88%)
:arrow_down:

keras/backend/common/__init__.py
100.00% <100.00%> (ø)

... and 175 files with indirect coverage changes

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

The logic here is quite complex overall, and it may be difficult to extend and maintain in the future. I assume it is adapted from JAX? Could it be significantly simplified?

Yes, it is adapted from JAX. In the latest commit, I believe I have simplified it significantly.

I think we can just need a function that can resolve result_dtype(a_dtype, b_dtype).

I think most of the complexity arises from dealing the weak type (python's int and float). We can simplify the logic by removing them, but we might lose some value in result_dtype.
For example, there are some ops allow python scalar type for their arguments. It would be inconvenient if we couldn't handle weak type in result_dtype.

Hi @fchollet
I think backend.result_type should now be ready. I have applied it to the following ops:

ops.ones
ops.zeros
ops.empty
ops.identity
ops.tri
ops.eye
and also added the corresponding tests.

It is worth noting:
There is an inevitable gap between tensorflow and other backends, where tf.Variable with int32 cannot be placed on the GPU, and as a workaround we need to use int64.
https://www.tensorflow.org/xla/known_issues#tfvariable_on_a_different_device
So I have skipped the canonicalization when the resulting dtype is int64 with tensorflow in backend.result_type.

While there are still some dtype inconsistencies in other ops, we can address them in a separate PR.

The failed tests should be unrelated to this PR.
I have demonstrated the usage of backend.result_type in ops.add. Now, the type inference is consistent across different backends.
This can be verified by the following unit test:
    @parameterized.product(dtype1=ALL_DTYPES, dtype2=ALL_DTYPES)
    def test_add(self, dtype1, dtype2):
        import jax.numpy as jnp

        x1 = knp.ones((1,), dtype=dtype1)
        x2 = knp.ones((1,), dtype=dtype2)
        x1_jax = jnp.ones((1,), dtype=dtype1)
        x2_jax = jnp.ones((1,), dtype=dtype2)
        self.assertEqual(
            standardize_dtype(knp.add(x1, x2).dtype),
            standardize_dtype(jnp.add(x1_jax, x2_jax).dtype),
        )
        self.assertEqual(
            standardize_dtype(knp.Add().symbolic_call(x1, x2).dtype),
            standardize_dtype(jnp.add(x1_jax, x2_jax).dtype),
        )

Generally, we should adhere to JAX's type inference rules with enable_x64=True. Is that correct?

Yes, that is a good plan. My experience with JAX dtype promotion policy is that it is more user friendly than TF's (with the exception of 64 bit dtypes being disabled by default).

Yes, that is a good plan. My experience with JAX dtype promotion policy is that it is more user friendly than TF's (with the exception of 64 bit dtypes being disabled by default).

Currently, backend.result_type and some of ops.numpy.* behavior matches JAX when using JAX_DEFAULT_DTYPE_BITS=32 and JAX_ENABLE_X64=true

Thank you for the thorough review.
Please let me know if any changes are necessary.


Add nightly job to attempt rebase on Bitcoin core master

Instead, I am making a new repo for this


We Stopped Hearing from Agents

Who do we need to talk to about re-opening an ICM that we had about a year ago with this same issue? or is some one that can help resolve this issue? Thanks

Hi @jquintero88 could you please elaborate more about your issue and fill in necessary info?

We are seeing self hosted agents get a we stopped hearing from agents error after 12+ hours. We have pipelines that run for up to 2+ days. Looking through diag logs seems like it is a problem with auth token expiring. we had this same issue last year and we thought it was mitigated only to start happening again. Don't know what exactly you need as far as necessary info. if you post any direct questions I can try to answer.

I spoke with @vijayma,
@Rajesh Ramamurthy can you please help with token lifecycle and expiry.

We are having the similar issue with our pipelines, only on weekends (saturday & sunday). These pipelines will complete their builds within a hour, we are having autoscaling enabled for the agent pool as well.
This issue is hapenning from July 31 2021.

@jquintero88 for us, this issue is happenning mostly on weekends, is it the same for your team as well?

@c002910  yes mostly on weekends, but we do see some during the week.

@jquintero88, I am closing this issue since it is most likely that this is a network issue and is not related to the agent itself. I will provide you with more info if it appears.

As per our analysis and testing with the MS support team, it seems to have worked fine when auto scaling was disabled.
This issue seems to got fixed with the Aug 19 release of Azure DevOps.
Ref: https://docs.microsoft.com/en-us/azure/devops/release-notes/2021/sprint-191-update
Below is the note related to the issue:
"Until now, these variables worked well with Windows scale set agents but not with Linux scale set agents because of an issue with the Azure Pipelines auto-scaling script. This issue has been addressed now. "


Fix typos in README

this repo is hear → this repo is here
At it's core → At its core

Great catch thanks!


refactor 3/n

Hello @williamFalcon! Thanks for opening this PR.

In the file pytorch_lightning/accelerator_backends/dp_backend.py:

Line 31:120: E501 line too long (133 > 119 characters)
Line 102:29: W503 line break before binary operator

Do see the Hitchhiker's guide to code style


Package request: Muse Hub

Project description
Muse Hub allows for the installation of MuseSounds, a high-quality selection of sounds for MuseScore. MuseScore already exists within the Nixpkgs repo, so having access to MuseSounds would be incredibly useful to MuseScore users using Nix.
Metadata

homepage URL: https://www.musehub.com/
source URL: N/A (closed-source)
license: proprietary
platforms: Linux

Notes
Muse Hub also acts as an installer for MuseScore, Audacity, and other apps, which may conflict with Nix's model. I am unsure of how feasible this all is, but I would like to be able to take advantage of MuseSounds on NixOS if at all possible.
EDIT
Muse Hub on Linux only provides MuseSounds, so please disregard the previous note. However, MuseSounds is installed in /srv, not within the home folder.

I second this, but I don't know how to write a nixos package at all. I'll add, though, that if installing in /srv is a problem, that directory can be  changed (potentially by default, but not having it installed I can't check which file would have to be edited

Looking at AUR for Arch they seem to use this URL for the src of the build:
https://pub-c7a32e5b5d834ec9aeef400105452a42.r2.dev/Muse_Hub.deb
When I went to the musehub site and tried to download the linux version of MuseHub I got the same URL:
https://pub-c7a32e5b5d834ec9aeef400105452a42.r2.dev/Muse_Hub.deb
The main problem with this URL is that the file doesn't change it's name with a version update (so checksum/hashing is going to be an issue.) (aka, can't pin down a version)
I will try and contact MuseHub and ask if they can have each version available as well for easier packaging in linux.
... to be continued...

oh, just found a comment detailing a manual build on Fedora...
https://musescore.org/en/node/336003#comment-1148388
Worth a read if you need to know how MuseHub works under the hood.

found their beta release URL:
https://pub-c7a32e5b5d834ec9aeef400105452a42.r2.dev/Muse_Hub_Beta.deb

It appears that MuseHub is no longer releasing for Linux.
See the website here: https://www.musehub.com/
However, they have changed the name to Muse Sounds Manager BETA, so they are making it clear that this app for Linux is only for Muse Sounds and not MuseHub.

any updates perhaps?

any updates perhaps?

Since source code is not provided AFAIK, the deb/rpm would have to be unpacked and repacked, and even then it may not work. In other words, I don't know how possible it is. I guess this issue is just to see if anyone else knows.

A solution I found to use an archived version of the app from arhive.org, this is kind of a hack but works for now.
I wrote a flake which packages Muse Sounds Manager based on the rpm package. You can find it here. Testing is greatly appreciated. If this turns out to work, I may also merge this into nixpkgs:
https://github.com/thilobillerbeck/muse-sounds-manager-nix

A solution I found to use an archived version of the app from arhive.org, this is kind of a hack but works for now.
I wrote a flake which packages Muse Sounds Manager based on the rpm package. You can find it here. Testing is greatly appreciated. If this turns out to work, I may also PR this into nixpkgs:
https://github.com/thilobillerbeck/muse-sounds-manager-nix

How do I install this on my system? I'm new to NixOS and don't entirely understand what a flake is or how to use it

A solution I found to use an archived version of the app from arhive.org, this is kind of a hack but works for now.
I wrote a flake which packages Muse Sounds Manager based on the rpm package. You can find it here. Testing is greatly appreciated. If this turns out to work, I may also PR this into nixpkgs:
https://github.com/thilobillerbeck/muse-sounds-manager-nix

How do I install this on my system? I'm new to NixOS and don't entirely understand what a flake is or how to use it

@ShawkMusic  here guide for you

@vandenoever
@doronbehar
Hi, just notifying the maintainers of the Nix Musescore package that someone has made a flake that packages Muse Sounds Manager for NixOS.
https://github.com/thilobillerbeck/muse-sounds-manager-nix
I might be able to package it myself but not right now. Maybe you two could be able to do it as you already maintain the main application that Muse Sounds Manager is for?
Thanks

@colin-heffernan @Soliprem @Hachem-H @thilobillerbeck @ShawkMusic @BasilYes
please help this pull request https://github.com/NixOS/nixpkgs/pull/341856
by either :+1:  or by testing/reviewing the code.
let's get this finished!

As mentioned in this https://github.com/NixOS/nixpkgs/pull/341856#issuecomment-2351576544 comment, due to the issues described in https://github.com/NixOS/nixpkgs/issues/318210 I am a bit hesitant in merging such a package, as it seem to have the potential to break Musescore . I will test again though when the PR is slightly more mature.

If MuseScore becomes unreliable after using muse-sounds-manager (which is not the case for me), the solution is to delete ~/.local/share/MuseSampler/. If you want to restore it back, just launch muse-sounds-manager again, it will immediately recreate it (and print |INFO|Muse.Common.Interop.ServiceCore|Installing MuseSampler to the console).


Update website to consume metadata for localized hints [1]

The current version of the website reads hint metadata directly from meta.ts for each hint, but this breaks with the changes in webhintio/hint#2634.
To handle localized hints, the website should now read the metadata name and description from _locales/en/messages.json for each hint.

Fixed by #748.


Is it possible to use ResNext?

I replaceed with ResNext, but the test acc only achieve to 87.5.

87.5

Seems like Resnet and Resnext achieved similar performance. Interesting. I will close the issue.


[Performance] [Tracking] Individual chat messages are slow to render

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Tap on a chat

Expected Result:

When chat loads the entire visible area is filled with messages instantly

Actual Result:

When items first render only a subset of them render and each "batch" of items is slightly delayed and one message renders after the other in a staggered fashion

Workaround:
Wait for the messages to appear awkwardly.
Platform:
All platforms, but the effects are felt differently depending on the platform.
Here's an example of what this looks like on various platforms...
Web:

iOS:

Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on Upwork

Triggered auto assignment to @lschurr (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

@marcaaron should this be assigned to you?

Triggered auto assignment to @Luke9389 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Adding Eng before posting to External..

Ok, I see no reason not to make this external. Let's see what proposals our contributors come up with.

Triggered auto assignment to @SofiedeVreese (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

@lschurr auto assign to eng is perfect thanks!

Removing @marcaaron 's assignment.
Posted to Upwork: https://www.upwork.com/jobs/~011974a9e078cd37d9
Adding Exported label now.

Triggered auto assignment to @deetergp (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

PROPOSAL
We can add initialNumToRender props in FlatList at this position
tested with initialNumToRender={30} and it's look good
https://github.com/Expensify/Expensify.cash/blob/1a1d66a322c733bbc79f8a5f05f1527240c769d7/src/components/InvertedFlatList/BaseInvertedFlatList.js#L142-L158
Thanks

As I'm out of office tomorrow, I'm going to unassign myself and re-add the External label.

Triggered auto assignment to @kevinksullivan (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Hey @kevinksullivan I'm OOO tomorrow hence applying the External label again.
The job is posted on Upwork!

That sounds pretty straight-forward, @aliabbasmalik8, let's do it.

Sorry @deetergp I'm going to disagree here... more details incoming

The problem is that individual chat message items are slow to render. They'd be slow to render if we have 1 or 1000. So changing the initialNumToRender won't influence the total time it takes to load a chat message. It will only make it so that the FlatList will render with some minimum number of items.
That said, raising the initialNumToRender seems like a good idea to prevent the issue where blank space is observed. The default is 10 and seems like that is clearly what we are experiencing on iOS. I'll create a new issue so we can address that and make sure @aliabbasmalik8 is assigned.

Might be related to

#4101

If you take a large picture of those commits, you'll notice a meta-pattern involving list cells, with 3 phases spanning over 2.3s:
Phase 1
(c33 → c52)

withOnyx(Component) in renderCell. Consecutive 2-commits patterns caused by state changes (preferredLocale then loading)
Phase 2
(c52 → c71)

withOnyx(ReportActionItem), descendent of component in phase one.  Consecutive 2-commits patterns caused by state changes (draftMessage then loading)
Phase 3
(c76 → c145)
.
Two repeated components updates:

2 instances of withOnyx(Component), descendant of component in phase 2.  Consecutive 2-commits patterns caused by state changes (preferredLocale then loading)
1 instance of withOnyx(Component) (the big spike of 30ms), which renders ReportActionContextMenu

Discussion
It's hard to identify a clear pattern after phase 3, but it seems that it's when RenderHtml starts being rendered in each cell. The most important finding is that bursts of commits identified in #4101 happen recursively, for each component in the tree created by renderCell wrapped in a withOnyx, n + 1 extraneous commits are added.
So if we have, let's say, 3 components wrapped in withOnyx in the cell tree, each subscribing to two keys, that's 3 * (2 + 1) = 9 extraneous commits per cell. Implementing the proposals suggested in #4101 should make a noticeable difference.

A simple observation (perhaps not surprising) but if we set the initialNumToRender for the FlatList to be very low + remove the loading spinner then the chat navigation happens very fast which seems to suggest that the time it takes to render items + the number rendered initially will also have a big impact (naturally we are rendering less of them - so if they are expensive to render then rendering a large number up front blocks us from navigating).

Avg. Switch Time initialNumToRender={20}
initialNumToRender={1}
Difference

1332.25
282.5833333
1049.666667

Of course, in these examples, the chats are not "fully loaded" when initially rendered onscreen, but it "feels" faster vs. the interaction completely hanging for 1.5 seconds. If anything I think this just provides extra evidence that the individual items themselves are heavy and slow to render.
I'm starting to think that we're not looking for a silver bullet that will suddenly make everything faster, but lots of small changes to make report action items render faster + managing carefully how many of them we decide to render when the chat first loads.
I'm not too sure how to suggest we proceed, but will think about it. Might be interesting to set up a single test case and some profiling tools so that we can try to improve an "example" report action.

To clarify, if you do this, will it only show one chat -- or will it start
showing one row, and then immediately backfill the rest?
On Mon, Jul 19, 2021 at 5:50 PM Marc Glasser @.***>
wrote:

A simple observation (perhaps not surprising) but if we set the
initialNumToRender for the FlatList to be very low + remove the loading
spinner then the chat navigation happens very fast which seems to suggest
that the time it takes to render items + the number rendered initially will
also have a big impact (naturally we are rendering less of them - so if
they are expensive to render then rendering a large number up front blocks
us from navigating).
Avg. Switch Time initialNumToRender={20} initialNumToRender={1} Difference
1332.25<PHONE_NUMBER> 1049.666667
Of course, in these examples, the chats are not "fully loaded" when
initially rendered onscreen, but it "feels" faster vs. the interaction
completely hanging for 1.5 seconds. If anything I think this just provides
extra evidence that the individual items themselves are heavy and slow to
render.
I'm starting to think that we're not looking for a silver bullet that will
suddenly make everything faster, but lots of small changes to make report
action items render faster + managing carefully how many of them we decide
to render when the chat first loads.
I'm not too sure how to suggest we proceed, but will think about it. Might
be interesting to set up a single test case and some profiling tools so
that we can try to improve an "example" report action.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Expensify/Expensify.cash/issues/4022#issuecomment-882960666,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEMNUTI6UFYG6NKFSQ7G4DTYTB5RANCNFSM5AKI2SMQ
.

Correct, it shows one row immediately. Then backfills the rest. Here's a video of what it looks like compared to what it looks like with the loading spinner + front-loading the report with 20 comments instead of 1
Loading Spinner + initialNumToRender = 20
https://user-images.githubusercontent.com/32969087/126252296-e68a0b60-b6a7-4a73-a891-42856153be67.mp4
No loading spinner + initialNumToRender = 1
https://user-images.githubusercontent.com/32969087/126252279-c94b0bf7-0172-4091-a146-f468ec3872b2.mp4

Well that seems a huge improvement, right?
On Mon, Jul 19, 2021 at 7:23 PM Marc Glasser @.***>
wrote:

Correct, it shows one row immediately. Then backfills the rest. Here's a
video of what it looks like compared to what it looks like with the loading
spinner + front-loading the report with 20 comments instead of 1
Loading Spinner + initialNumToRender = 20
https://user-images.githubusercontent.com/32969087/126252296-e68a0b60-b6a7-4a73-a891-42856153be67.mp4
No loading spinner + initialNumToRender = 1
https://user-images.githubusercontent.com/32969087/126252279-c94b0bf7-0172-4091-a146-f468ec3872b2.mp4
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Expensify/App/issues/4022#issuecomment-883001733, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEMNUXDF3MPTTWF5GC5XIDTYTM2NANCNFSM5AKI2SMQ
.

I think so, but the effect is slightly more noticeable with a larger chat...
https://user-images.githubusercontent.com/32969087/126258234-486f10f5-e59b-4529-a2df-2086dc070c51.mp4
Mostly, I think there's likely a sweet spot where we:

make messages more performant to load (whether through refactors or Onyx improvements)
approximate an ideal number of messages to initially render based on the screen height (h/t to @rdjuric for that idea)

I'd love to experience it with just one chat loading
On Mon, Jul 19, 2021, 8:46 PM Marc Glasser @.***> wrote:

I think so, but the effect is slightly more noticeable with a larger
chat...
https://user-images.githubusercontent.com/32969087/126258234-486f10f5-e59b-4529-a2df-2086dc070c51.mp4
Mostly, I think there's likely a sweet spot where we:

make messages more performant to load (whether through refactors or
Onyx improvements)
approximate an ideal number of messages to initially render based
on the screen height (h/t to @rdjuric https://github.com/rdjuric for
that idea)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Expensify/App/issues/4022#issuecomment-883028435, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEMNUXJ6LUIGUZU3HDEV6DTYTWRLANCNFSM5AKI2SMQ
.

https://user-images.githubusercontent.com/32969087/126264077-dfed5cd4-a4a1-459b-8c7c-c507a8f85fc7.mp4

Oh sorry, I meant let's deploy this!

@deetergp, @kevinksullivan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@marcaaron Just so I understand, you are suggesting that we:

Get rid of the loading spinner
Render the initial number of chats based on the vertical viewport height
Then finally backfill n number of chats after that initial number loads?

Is that correct?

@marcaaron it appears you're working on this but you're not assigned.  Any reason @kevinksullivan shouldn't double this on Upwork? It's only $250 now and it's been 9 days

@mallenexpensify I'm going to make this more of a tracking issue and myself if you want to cancel the Upwork gig. This has become more of a discussion at this point and will need to be addressed by several smaller issues.

@deetergp yes, that's the idea @rdjuric had. I think maybe we can create a new issue for it.

Job is closed/removed in Upwork (also checked and Help Wanted label is on this issue)

@deetergp yes, that's the idea @rdjuric had. I think maybe we can create a new issue for it.

@marcaaron I opened a issue for this https://github.com/Expensify/App/issues/4258

@rdjuric nice! Thanks for that.

@marcaaron Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

We're making some pretty interesting progress with this issue and it's starting to become clear that any list item components using withOnyx are going to take a long time to render since they'll always be blocked and "waiting for data" from Onyx. By leveraging the Context API we can avoid creating a new connection and get that time back. Exploring it in this PR.

So, I think chat switching is starting to approach something resembling an acceptable amount of time. Check out these latest videos which are release builds off main + the changes in the last PR I linked above...
iOS
https://user-images.githubusercontent.com/32969087/127958695-935956fc-9268-4866-bef2-28fffd42577f.mov
Android
https://user-images.githubusercontent.com/32969087/127958741-0177a936-c80f-484c-99ee-37a580adc876.mp4
Android looks slightly slower than iOS still (and is a little janky or something at one part) but whatever we are doing is working. 🍻

Whoa!  How do I get a taste of this?
On Mon, Aug 2, 2021, 9:43 PM Marc Glasser @.***> wrote:

So, I think chat switching is starting to approach something resembling
an acceptable amount of time. Check out these latest videos which are
release builds off main + the changes in the last PR I linked above...
iOS
https://user-images.githubusercontent.com/32969087/127958695-935956fc-9268-4866-bef2-28fffd42577f.mov
Android
https://user-images.githubusercontent.com/32969087/127958741-0177a936-c80f-484c-99ee-37a580adc876.mp4
Android looks slightly slower than iOS still (and is a little janky or
something at one part) but whatever we are doing is working. 🍻
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Expensify/App/issues/4022#issuecomment-891519687, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEMNURYBFONN6TNXSNFLM3T25XX3ANCNFSM5AKI2SMQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

@marcaaron Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@marcaaron 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

@marcaaron Huh... This is 4 days overdue. Who can take care of this?

@marcaaron Still overdue 6 days?! Let's take care of this!

Going to close this for now as the last of the changes are on staging. I'm not sure what else we can do to improve the individual loading of chat messages and they seem to load pretty fast for now.


Fix logic error in positioning of negative button

;) RIGHT is END (in LTR)

Oh right, aweosme thanks


Update README.md

Added instructions for google colab

Since we don't link notebooks on the Readme I think installation.mdx would be better suited for the information. What do you think?


Database changelog lock table support

Thoughts on implementing something similar to that feature in liquibase?
https://docs.liquibase.com/concepts/basic/databasechangeloglock-table.html

Database Change Lock
Another way Liquibase supports this pattern is to include a locking mechanism. This lock ensures that if multiple servers start simultaneously, they won’t run into problems as they both try to apply the same database changes.
The locking system uses a DATABASECHANGELOGLOCK table as the synchronization point, with the service setting the LOCKED column to 1 when it takes the lock and setting it to 0 when it finishes.
As long as the process that has set the LOCKED column to 1 isn’t killed before it has a chance to set back to 0, this works fine. When it’s not working fine, all of the other Liquibase processes (including a newly restarted process on the same machine) will just continue to wait for a 0 value which will never come. The only way to recover from this scenario is by running the Liquibase unlock command or updating the DATABASECHANGELOGLOCK table manually.

This is unlikely to be part of umzug as things stand, because locking varies a lot between database systems. Last I checked there wasn't a clear way to do this via sequelize. It's possible to achieve this on the user side, though. Here's how @slonik/migrator does this by overriding the runCommand method, and uses pg_advisory_lock: https://github.com/mmkal/slonik-tools/blob/e88bfaab73cd2f8033d0d23551330ad23fd30191/packages/migrator/src/index.ts#L140-L170

Sounds good.


documentation for Inotify::watches is broken in 0.10.1

The public crate docs here have dead links to Watches::add and Watches::remove, that return a 404. I also notice that the return type Watches is not linked.

Thanks for reporting, @eric-seppanen! Not sure why this broke, but it hopefully shouldn't be too hard to fix.

Thank you, that makes sense. I've just confirmed that it works on master.
I've added releasing a new version to my list, and should hopefully get to it soon. Closing this issue, as it's already fixed in the repository.


kmsan: enable panic_on_kmsan=1

Signed-off-by: Alexander Potapenko<EMAIL_ADDRESS>
Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

PTAL.
Please note that I didn't actually rebuild any other configs, hope that's fine.


Unnecessary console.logs in formatElevation function

I've started using this plugin and it is perfect for my needs, however I've noticed excessive logging in the console, coming from what seems to be the formatEleveation function which has a console.log(this.options); call, which produces the excessive logging.

Hi @Stromwerk, thanks for pointing this out. That console.log should definitely not belong there.

What version of the library are you using?

I'm using version 0.5.1

Fixed in 0.5.2


[BUG] SkBitmap.Decode always fail some images, but using SKImage.FromEncodedData works

Description
I am trying to load images in UWP with StorageFile, but some images always fail with a weird error message.
Code
using (var stream = await storageFile.OpenStreamForReadAsync())
{
    SKBitmap bitmap = SKBitmap.Decode(stream);
    // the rest
}

Expected Behavior
the image should be loaded
Actual Behavior
some pictures fail at the line of calling SKBitmap.Decode, with this error message:
Value cannot be null.
Parameter name: buffer

Basic Information

Version with issue:  2.80.3-preview.24
Last known good version:  N/A
IDE:  VS.NET
Platform Target Frameworks: 10.0.19041.0 - 10.0.17763.0

Android:
iOS:
Linux:
macOS:
Tizen:
tvOS:
UWP:  6.2.10
watchOS:
Windows Classic:

Target Devices:   x64

** Details **
The manifest permission is all opened. For those images that fail, I can call GetThumbnailAsync properly.
Moreover, the stream is not null, I added the following code:
                        if (stream.CanRead && stream.CanSeek)
                        {
                            stream.Seek(0, SeekOrigin.Begin);
                        }

these lines pass, and the Decode still failed.
However, if I do this instead:
SKImage img = SKImage.FromEncodedData(stream);
SKBitmap bitmap = SKBitmap.FromImage(img);

Now those images can be loaded.
but why?
Screenshots
I uploaded one failed image in SO:
https://stackoverflow.com/questions/66096184/why-does-skiasharp-fail-to-load-some-image-in-uwp-when-calling-skbitmap-decode
Reproduction Link

Are you able to attach the file here in a zip? These websites like to process them.

yes, sorry, I was distracted after I quickly post the bug.
There are 2 photos in the folder Photos, the 4.jpg cannot be loaded but the other one works fine.
If you change the code to: using SKImage to read stream and then load into SKBitmap, then it works.
SkiaLoadTest.zip

I am experiencing the exact same behaviour with some images exported from Photoshop.
Do we have information why this is happening?

SKBitmap bitMap = SKBitmap.FromImage(SKImage.FromEncodedData(new MemoryStream(mediaFileBytearray)));
Does not work using SKImage too
skia version 2.80.3

Duplicate of #1551

Might have same cause as https://github.com/mono/SkiaSharp/issues/1621

Can it do anything with "some images" are thoses with specific metadata, causing this to happen?..
I have the following error happening with stable 2.80.3 on iOS 14.x (on iOS 12.x it's not happening):
var bitmap = SKBitmap.Decode(stream);
crash boom bang:
{System.ArgumentNullException: Value cannot be null.
Parameter name: buffer
  at SkiaSharp.SKManagedStream.OnReadManagedStream (System.IntPtr buffer, System.IntPtr size) [0x0000d] in <870e9db956e7461cb750c2b6d9037f6f>:0
  at SkiaSharp.SKManagedStream.OnRead (System.IntPtr buffer, System.IntPtr size) [0x00006] in <870e9db956e7461cb750c2b6d9037f6f>:0
  at SkiaSharp.SKAbstractManagedStream.ReadInternal (System.IntPtr s, System.Void* context, System.Void* buffer, System.IntPtr size) [0x00015] in <870e9db956e7461cb750c2b6d9037f6f>:0
  at (wrapper native-to-managed) SkiaSharp.SKAbstractManagedStream.ReadInternal(intptr,void*,void*,intptr)
  at (wrapper managed-to-native) SkiaSharp.SkiaApi.sk_codec_new_from_stream(intptr,SkiaSharp.SKCodecResult*)
  at SkiaSharp.SKCodec.Create (SkiaSharp.SKStream stream, SkiaSharp.SKCodecResult& result) [0x0003b] in <870e9db956e7461cb750c2b6d9037f6f>:0
  at SkiaSharp.SKCodec.Create (System.IO.Stream stream, SkiaSharp.SKCodecResult& result) [0x00006] in <870e9db956e7461cb750c2b6d9037f6f>:0
  at SkiaSharp.SKCodec.Create (System.IO.Stream stream) [0x00000] in <870e9db956e7461cb750c2b6d9037f6f>:0
  at SkiaSharp.SKBitmap.Decode (System.IO.Stream stream) [0x0000e] in <870e9db956e7461cb750c2b6d9037f6f>:0

Downgrading to 2.80.2 solved it..

I am getting the same errors for images with a high DPI (300). Images with lower ones (< 96) are working fine. Any ideas why this is the case?

Hi folks. Sorry it took forever to fix this - especially since it was so simple and totally my fault. I will try get a package out ASAP after this merges: https://github.com/mono/SkiaSharp/pull/2265


[bug]:  doc fix or a fix to include zod in the install command

Describe the bug
Please make sure to mention the manual install of the zod install, otherwise many devs are getting confused with that.
Affected component/components
Form
How to reproduce
If I don't manually install zod using npm then it shows the module is not found.
Codesandbox/StackBlitz link
No response
Logs
No response
System Info
Microsoft Edge browser running on windows 10

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

Easy I can do this but is it needed? No idea. It's written there to follow Zod documentation. As a sensible developer, I think one should not have any problem with this.

Ok, it said, it was a dependency but a dev told me that it is automatically installed as a dependency when you install the shadcn-ui using npm, but actually it was needed to be manually done. So, I thought why not exclusively mention that manually you need to install this dependency, because that might be very helpful for new developers.

From: Tanishq Sharma @.>
Sent: 20 April 2024 03:43
To: shadcn-ui/ui @.>
Cc: Gourab Mahapatra @.>; Author @.>
Subject: Re: [shadcn-ui/ui] [bug]: doc fix or a fix to include zod in the install command (Issue #3521)
Easy I can do this but is it needed? No idea. It's written there to follow Zod documentation. As a sensible developer, I think one should not have any problem with this.
—
Reply to this email directly, view it on GitHubhttps://github.com/shadcn-ui/ui/issues/3521#issuecomment-2067344507, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATU3J6OFADAPVIIIESTGKETY6GJIVAVCNFSM6AAAAABGMSTWD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXGM2DINJQG4.
You are receiving this because you authored the thread.Message ID: @.***>


Adding Azure DevOps data connector and onboarding scripts

Azure DevOps Auditing Repackaging changes
Required items, please complete
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

TestEvidenceDoc

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

@v-mchatla : Please review the PR and provide your feedback. Thanks

@v-mchatla, please update the file extension for "Set-AzureDevOpsAuditing.ps1.txt" as it should be just "Set-AzureDevOpsAuditing.ps1", same with "readme.md.txt", it should just be "readme.md", thanks.

Hi @v-sabiraj ,
I will update the author details.
Thanks

Hi @v-sabiraj,
I will address the remaining comments today.
Thanks

@v-mchatla, please check, thanks.

Hi @v-sabiraj,
Waiting on confirmation from Prateek.
Thanks

@v-mchatla, please update branch from master to fix the arm-ttk validations.

Looking into this

@v-mchatla, please update the branch from master.

Hi @v-sabiraj,
I will fix the validation errors today.
Thanks

@v-mchatla, waiting on merge confirmation.

Hi @v-sabiraj,
I have requested @rushriva for some help in configuring the connector. Once we got approval will go ahead with the merge.
Thanks

Hello @v-mchatla please clear the checks

Hi @rushriva,
Can you please provide update on how to proceed further.
Thanks

Hi @rushriva,
Can you please provide update on how to proceed further.
Thanks

Hi,
I will go through the data connector instruction steps once and try to configure the connector.
Thanks

Hi @v-rucdu,
Can you please try deploying the connector once and let me know the update.
Thanks

Hi @v-rucdu,
Can you please try deploying the connector once and let me know the update.
Thanks

Hi @v-rucdu,
Can you please try deploying the connector once and let me know the update.
Thanks

@v-mchatla, any update on this?

Waiting for update on this, thanks.

Hi @v-rucdu,
Can you please try deploying the connector once and let me know the update.
Thanks

Hi,
Yesterday Ruchita had deployed the solution but we need do deploy the connector and see the functionality.
Thanks

Waiting for update on this, thanks.

Hi,
Requested help from Ruchita for Dataconnector testing.
Thanks

Hi,
Requested help from Ruchita for Dataconnector testing.
Thanks

Hello @v-rucdu please reply on the following

Hi,
Requested help from Ruchita for Dataconnector testing.
Thanks

Waiting for update on this, thanks.

Hi,
Requested help from Ruchita for Dataconnector testing.
Thanks

Hi,
Requested help from Ruchita for Dataconnector testing.
Thanks

closing for now


Fix AA issues for Footer

*Issue:*https://github.com/bcgov/entity/issues/19455
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://bcregistry-btr-dev--pr-118-hhv8ymec.web.app

/gcbrun

Temporary Url for review: https://bcregistry-btr-dev--pr-118-hhv8ymec.web.app


Massive NPM package

Just wanna let you know that I tried to use scroll-js via NPM yesterday, but was shocked to wait for 240 secs till about 3 hundred dependencies get installed. Maybe Bower package is not so heavy, but Bower is no being abandoned.
Are all those babel dependencies necessary? All I really need is one JS file. I believe the library works great, at least as I read the description, but the collateral damage of having about 300 deps installed is no for me.

Just to clarify, this package only has only four dependencies at the time of this writing. These dependencies are necessary to allow the use of ES6 syntax and features while also being backwards compatible (mainly for IE browsers).
You should note that when using the npm package, it is assuming that you are building your own dist file. And even though other nested deps are installed, they are not shipped with your production code, so it shouldn't make a difference of how many packages get installed.
If you are only interested in the smallest JS file possible without having to install npm deps, I suggest you download the dist files directly (as indicated in the Installation instructions on the README).
I am closing this as this is not an issue. However, please feel free to still comment here and I will make time to address any further concerns.

Thanks for your reply! It seems that we differ in NPM philosophy.
I never considered to build dist files of third party packages in Node ecosystem. I always thought that building third-party packages is meant only for development of the package. And I thought that thats the reason for devDependencies.

@dominikfiala I understand your concerns. The reason the package was built this way to give developers a way to use their own build processes to ensure the final output would be as small as possible. However, for the reasons you've stated and out of convenience, I do think it is best at this point to point the npm package at the dist file and remove the unnecessary dependencies to customize the build.
I have done this and added it to version 1.8 (latest version) of this package. Thanks for your contribution.