packages have newer versions incompatible with dependency constraints

Steps to Reproduce

On a Mac, create a new project in Flutter in Android Studio using current flutter from flutter stable, 3.0.5

Run “flutter pub upgrade” being cd'ed into the project folder

It complains

Resolving dependencies...
  async 2.8.2 (2.9.0 available)
  boolean_selector 2.1.0
  characters 1.2.0 (1.2.1 available)
  charcode 1.3.1
  clock 1.1.0 (1.1.1 available)
  collection 1.16.0
  cupertino_icons 1.0.5
  fake_async 1.3.0 (1.3.1 available)
  flutter 0.0.0 from sdk flutter
  flutter_lints 2.0.1
  flutter_test 0.0.0 from sdk flutter
  lints 2.0.0
  matcher 0.12.11 (0.12.12 available)
  material_color_utilities 0.1.4 (0.2.0 available)
  meta 1.7.0 (1.8.0 available)
  path 1.8.1 (1.8.2 available)
  sky_engine 0.0.99 from sdk flutter
  source_span 1.8.2 (1.9.1 available)
  stack_trace 1.10.0
  stream_channel 2.1.0
  string_scanner 1.1.0 (1.1.1 available)
  term_glyph 1.2.0 (1.2.1 available)
  test_api 0.4.9 (0.4.13 available)
  vector_math 2.1.2 (2.1.3 available)
No dependencies changed.
13 packages have newer versions incompatible with dependency constraints.

How can a fresh project already have incompatible dependency constraints?

Then run flutter pub outdated. It says

Showing outdated packages.
[*] indicates versions that are not the latest available.

If all dependencies are up to date, it seems confusing that it’s not letting me get the current versions.

Running “flutter pub cache repair” made no difference.

Some online queries report that running ”flutter packages pub run build_runner ” in the project folder helps. However, I get

Could not find package "build_runner". Did you forget to add a dependency?
pub finished with exit code 65

I have also seen being asked to run “dart pub deps -s list” This says

Could not find a file named "pubspec.yaml" in "/Users/maurice/.pub-cache/hosted/pub.dartlang.org/boolean_selector-2.1.0".

[✓] Flutter (Channel stable, 3.0.5, on macOS 12.4 21F79 darwin-x64, locale en-US)
    • Flutter version 3.0.5 at /Users/maurice/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f1875d570e (6 weeks ago), 2022-07-13 11:24:16 -0700
    • Engine revision e85ea0e79c
    • Dart version 2.17.6
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/maurice/Library/Android/sdk
    • Platform android-31, build-tools 30.0.3
    • Java binary at: /Volumes/backuphd/Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2022.1.4)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 69.0.4
    • Dart plugin version 221.6008.17

[✓] Connected device (3 available)
    • iPhone SE (3rd generation) (mobile) • 72277DA9-1568-4539-85BC-058A1F40B58D • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-15-5 (simulator)
    • macOS (desktop)                     • macos                                • darwin-x64     • macOS 12.4 21F79 darwin-x64
    • Chrome (web)                        • chrome                               • web-javascript • Google Chrome 104.0.5112.101

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Hello @mauricev. This is expected as package authors release new versions of packages. Flutter would upgrade these dependencies in newer stable versions as time goes on. But Flutter's release schedule doesn't allow it to have all the latest versions of all the packages at the current time. It's normal for this to happen, even with packages you've added to your own project. As a project becomes larger, you may not have the liberty of always using the latest package without breaking something somewhere.
Since is not a bug, I am closing this issue. If you disagree, please comment and we can reopen it. Thank you.


nixpkgs: added gimp development version

hmm...travis tells me that the sha256 hash is not correct but I can build it on my machine. Why?
output path ‘/nix/store/j12nnmk68133mmc6z9j4bh9z261i244c-git-export’ should have r:sha256 hash ‘0llff710fbbpxwb4g1yp7pq2v6wqfdriilmsk930gh7cpa6mg33f’, instead has ‘06x919454v44w6vjakih9q014xzbnjh84db5lgrqqzsr9icg10bk’

All these packages shall not be built by hydra, we have only stable released packages

ok, I didn't know

meta.hydraPlatforms = [] should prevent building.

done :)

IMHO, we shouldn't have development versions of packages in nixpkgs at all (in general), even if not built by Hydra.
Who is this development version for? How often do you plan to update it?

IMHO, we shouldn't have development versions of packages in nixpkgs at all (in general)

So where would be the right place to drop such packages?

Who is this development version for?

I'd be glad if there were a place where I can find development packages. If s.o. already wrote an expression I don't unnecessarily have to loose time to write my own one.
Can we just keep them in a separate branch?

So where would be the right place to drop such packages?

Anywhere but (upstream) nixpkgs? ;-)

I'd be glad if there were a place where I can find development packages. If s.o. already wrote an
expression I don't unnecessarily have to loose time to write my own one.

Some thoughts come to mind:

Did you try using overrideDerivation? I think it works well, very few lines needed to provide your own (exact) version of a package, given that the build system interface is mostly the same. There is usually no need to copy expressions, and you get to update exactly when you want (no need to create pull request, wait for channel updates...).

What's the ultimate goal for development packages in nixpkgs? IMHO, nixpkgs is about packaging latest (stable) releases of all open source software. This is a big job. Also tracking git HEAD of "the world", in parallel, is just crazy (IMHO). (I know you just proposed to package one package, which is not crazy, but it's the principle.)

Can we just keep them in a separate branch?

Slightly better, but I still think few people will use this and it will have a high chance of getting outdated quickly (people loose interest and don't clean up).
You could also make a fork of nixpkgs which contains only unreleased/development packages.
Or help gimp upstream to make releases that can be used in distros.

So where would be the right place to drop such packages?
Anywhere but (upstream) nixpkgs? ;-)

You insist on making specifically upstream NixPkgs less useful and not
the reasonable only stop to get Nix expressions for free software?

I'd be glad if there were a place where I can find development packages. If s.o. already wrote an
expression I don't unnecessarily have to loose time to write my own one.

Some thoughts come to mind:

Did you try using overrideDerivation? I think it works well, very few lines needed to provide your own (exact) version of a package, given that the build system interface is mostly the same. There is usually no need to copy expressions, and you get to update exactly when you want (no need to create pull request, wait for channel updates...).

What's the ultimate goal for development packages in nixpkgs? IMHO, nixpkgs is about packaging latest (stable) releases of all open source software. This is a big job. Also tracking git HEAD of "the world", in parallel, is just crazy (IMHO). (I know you just proposed to package one package, which is not crazy, but it's the principle.)

NixPkgs doesn't look like being able to be about packaging latest stable
versions of all the software. NixPkgs seems to be about packaging the
versions someone cares about...
Because no, there is a ton of packages where latest versions are usually
ignored and rarely there is a special effort to get at least some
updates.
We easily give up and keep very old versions as default ones for
relatively small reasons. Etc.
And yes, there are often good reasons to have a prerelease as an option
and there is often a prerelease as an option.

Can we just keep them in a separate branch?

Slightly better, but I still think few people will use this and it will have a high chance of getting outdated quickly (people loose interest and don't clean up).

Wouldn't be so sure.
What would be the reason to use master, and not just merge master into
it? You get more options this way.

You could also make a fork of nixpkgs which contains only unreleased/development packages.
Or help gimp upstream to make releases that can be used in distros.

For example, by lowering the barrier to casually trying out
prereleases...

Did you try using overrideDerivation? I think it works well, very few lines needed to provide your own (exact) version of a package, given that the build system interface is mostly the same.

no, that doesn't work. The stable nix expression uses precompiled files (e.g. http://download.gimp.org/pub/gimp/v2.8/gimp-2.8.14.tar.bz2) instead of source code.

What's the ultimate goal for development packages in nixpkgs?

I think there is no ultimate goal. I'd rather say everyone has its own goal ;-)

@7c6f434c: I don't "insist on making nixpkgs less useful [...]" (hey, that sounded like a really loaded question!). I just think having git HEAD snapshots in addition to latest stable releases is a bad idea in general. If we disagree then that's OK. I just wanted to share my opinion.
@flosse: Ok. I see. Maybe that can be solved by adding something extra to preConfigure?
Btw, if this is going to be merged, please use a "git describe"-like version number (base-version '-' number-of-commits-since-base-version, e.g. 1.2.3-101), so that the relation to the stable release is obvious. I don't think we want to se this when querying packages:
package-1.2.3
package-a53df89

Because there is no way of knowing what the 2nd package is, unless you have the git repo.

@flosse: I compared gimp expressions git.nix and 2.8.nix. So, you need to add a one-liner preConfigure and a couple of extra packages to buildInputs (autoconf etc.). Other than that, the expressions look the same. I don't see why that couldn't be a local expression using overrideDerivation. Then you could update your package at will! No need to wait for PR to be merged, channel to be updated etc.
Allright, enough of my opinions on this matter :-)

@7c6f434c: I don't "insist on making nixpkgs less useful [...]" (hey, that sounded like a really loaded question!). I just think having git HEAD snapshots in addition to latest stable releases is a bad idea in general. If we disagree then that's OK. I just wanted to share my opinion.

Maybe it was not because of what you wrote, but just because you were
the first one to reply, but your explanation looked like you were
describing a universal consensus, and I somewhat went overboard with the
opposite side of the everlasting arguments.
Sorry if I wrote something too loaded or too emotional.

@flosse: Ok. I see. Maybe that can be solved by adding something extra to preConfigure?
Btw, if this is going to be merged, please use a "git describe"-like version number (base-version '-' number-of-commits-since-base-version, e.g. 1.2.3-101), so that the relation to the stable release is obvious. I don't think we want to se this when querying packages:
package-1.2.3
package-a53df89

Because there is no way of knowing what the 2nd package is, unless you have the git repo.

Yes, this is a good idea, thanks.
I usually try to mark it as a VCS version, and add a date of the
snapshot, but I probably like your idea better.

@flosse: I compared gimp expressions git.nix and 2.8.nix. So, you need to add a one-liner preConfigure and a couple of extra packages to buildInputs (autoconf etc.). Other than that, the expressions look the same. I don't see why that couldn't be a local expression using overrideDerivation. Then you could update your package at will! No need to wait for PR to be merged, channel to be updated etc.
Allright, enough of my opinions on this matter :-)

The most comfortable workflow is: have a git snapshot in NixPkgs, update
it monthly, do a src-only override of the git-snapshot expression.
Maybe it's unfortunate... I am not sure that there is a universal set of
overrides that allows to build at least 70% of autotools-based
git-snapshots without further configuration.

@7c6f434c: Thanks for clearing that up :-)

Thanks for your thoughts and time. Overall I think we shouldn't merge dev versions into the master branch but keeping them separate in a dev branch. Nevertheless it seems to be too soon for this, so I'll close this PR. Hopefully the NixOS community will grow in the next few years so that there is enough power to maintain a dev branch :)


some confusions

Hello, thank you very much for your excellent open source work, but are your training parameters documented?
I don't understand cache dir means what ?
thank you!

And is torch 1.4.0 sure to support apex?
Why would I report an error and not support it?


Pilosa fails during cluster join process if another node initiates join

Cluster set of 3 nodes
replication factor 3
cluster is empty (no indexes created)
reproducible in 99% of attempts.

Let me know what else you need to investigate.
2018/10/11 13:24:34 load NodeID: /data/pilosa/.id
2018/10/11 13:24:34 add node Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a to cluster on Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a
2018/10/11 13:24:34 [DEBUG] memberlist: Stream connection from=<IP_ADDRESS>:44388
2018/10/11 13:24:34 [DEBUG] memberlist: Initiating push/pull sync with: <IP_ADDRESS>:11101
2018/10/11 13:24:34 [DEBUG] memberlist: Initiating push/pull sync with: <IP_ADDRESS>:11101
2018/10/11 13:24:34 open server
2018/10/11 13:24:34 SendSync to: http://dev-pilosa-1.dev-pilosa-headless.dev-pilosa.svc.cluster.local:10101
2018/10/11 13:24:34 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a wait for joining to complete
2018/10/11 13:24:34 monitor primary store events
2018/10/11 13:24:34 received NodeJoin event: &{0 Node: 923ada43-1d6a-4f2a-a477-19bffdaa9fbf}
2018/10/11 13:24:38 merge cluster status: &{5246c7a7-2127-4700-829d-1883f4613960 NORMAL [Node: 923ada43-1d6a-4f2a-a477-19bffdaa9fbf Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a Node: fc74f2de-7555-4581-bf25-a196bcd3f390]}
2018/10/11 13:24:38 add node Node: 923ada43-1d6a-4f2a-a477-19bffdaa9fbf to cluster on Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a
2018/10/11 13:24:38 add node Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a to cluster on Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a
2018/10/11 13:24:38 add node Node: fc74f2de-7555-4581-bf25-a196bcd3f390 to cluster on Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a
2018/10/11 13:24:38 change cluster state from STARTING to NORMAL on 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a
2018/10/11 13:24:38 mark node as joined (received coordinator update)
2018/10/11 13:24:38 stop monitor replication
2018/10/11 13:24:38 set primary translate store to 923ada43-1d6a-4f2a-a477-19bffdaa9fbf
2018/10/11 13:24:38 start monitor replication
2018/10/11 13:24:38 pilosa: replicating from offset 0
2018/10/11 13:24:38 joining has completed
2018/10/11 13:24:38 open holder path: /data/pilosa
2018/10/11 13:24:38 open holder: complete
2018/10/11 13:24:38 Sending State READY (923ada43-1d6a-4f2a-a477-19bffdaa9fbf)
2018/10/11 13:24:38 SendTo: http://dev-pilosa-0.dev-pilosa-headless.dev-pilosa.svc.cluster.local:10101
2018/10/11 13:24:38 merge cluster status: &{5246c7a7-2127-4700-829d-1883f4613960 STARTING [Node: 923ada43-1d6a-4f2a-a477-19bffdaa9fbf Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a Node: fc74f2de-7555-4581-bf25-a196bcd3f390]}
2018/10/11 13:24:38 add node Node: 923ada43-1d6a-4f2a-a477-19bffdaa9fbf to cluster on Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a
2018/10/11 13:24:38 add node Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a to cluster on Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a
2018/10/11 13:24:38 add node Node: fc74f2de-7555-4581-bf25-a196bcd3f390 to cluster on Node: 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a
2018/10/11 13:24:38 change cluster state from NORMAL to STARTING on 99d1ce3b-8d7f-41d0-980f-e6bbdda9061a
2018/10/11 13:24:38 mark node as joined (received coordinator update)
Error: running server: opening server: setting nodeState: sending node state error: err=sending: unexpected response status code: 400: receiving message: executing http request: Post http://dev-pilosa-2.dev-pilosa-headless.dev-pilosa.svc.cluster.local:10101/internal/cluster/message: dial tcp: lookup dev-pilosa-2.dev-pilosa-headless.dev-pilosa.svc.cluster.local on <IP_ADDRESS>:53: no such host
{}

running server: opening server: setting nodeState: sending node state error: err=sending: unexpected response status code: 400: receiving message: executing http request: Post http://dev-pilosa-2.dev-pilosa-headless.dev-pilosa.svc.cluster.local:10101/internal/cluster/message: dial tcp: lookup dev-pilosa-2.dev-pilosa-headless.dev-pilosa.svc.cluster.local on <IP_ADDRESS>:53: no such host
{}

Usage:
  pilosa server [flags]

Flags:
      --anti-entropy.interval duration       Interval at which to run anti-entropy routine. (default 10m0s)
  -b, --bind string                          Default URI on which pilosa should listen. (default ":10101")

If you could post the configuration for each node, and perhaps the order in which they are being started, we will attempt to reproduce.

All settings are set with ENV variables.
export PILOSA_BIND='<IP_ADDRESS>:10101'
export PILOSA_CLUSTER_REPLICAS='3'
export PILOSA_DATA_DIR='/data/pilosa'
export PILOSA_GOSSIP_PORT='11101'
export PILOSA_GOSSIP_SEEDS='dev-pilosa-0.dev-pilosa-headless.dev-pilosa.svc.cluster.local:11101,dev-pilosa-1.dev-pilosa-headless.dev-pilosa.svc.cluster.local:11101,dev-pilosa-2.dev-pilosa-headless.dev-pilosa.svc.cluster.local:11101'
export PILOSA_VERBOSE='true'

Coordinator node additionally has:
export PILOSA_CLUSTER_COORDINATOR='true'

dev-pilosa-0 has a role of coordinator. I'm starting from 0 to 2 and in reverse order.


Mark project as migrated to Xcode 9.0 / Swift 4.0.

No source changes were required.

Closing -- it's not true that no source changes were required, sorry.  You need #266 first.


Use custom validators as additional validation steps alongside type and other validators.

I will report my use case: suppose I have to validate a query object that has, among the others, the parameters fromDate and toDate, and I need to be sure that they are chronologically coherent. Why should I write two different schemas and chain validations in order to achieve that? Wouldn't it make more sense for me to specify a schema: validator and a custom: one? What if I wanted to validate an object checking its type and its conformance to some custom requirements of mine?

Sorry for not getting back on this. This is an interesting suggestion. I assume, then, that the custom validator should get called after the validator has validated the data? That would make most sense, wouldn't it?

Yes, that is the way I thought it, the custom validator would add specialization to the others.

Well, I guess I never thought of it that way, but I guess it makes pretty good sense. I only made it so that you were not tied to whatever validation features the module had. I'll take a look at it.


Doesn't work when the include is not indented

If the include line is on the very left of the line (i.e. there's nothing before it) then the program complains that there's non-whitespace in the preceding section.  (OK, kind of debatable as bugs go, I know.)

I guess that is what you get for using regex 😅 – thanks for reporting this, will fix this as soon as I get the chance. 🙃

I think this is intended behavior. Why use indent content if you're not at any indentation level?

Could be useful using this library for example : https://python-anyconfig.readthedocs.io/en/latest/usage.html#template-config-support


CI issue - Run nix-shell - error: expected JSON string

Run nix-shell
  nix-shell
  shell: /bin/bash -e {0}
error: expected JSON string
(use '--show-trace' to show detailed location information)
Error: Process completed with exit code 1.

Hmmm, I wasn't intending the github workflows to be copied via the template, I should probably remove them.

I removed the .github directory to fix this.

btw:
Where can I find that file "skip_adding_nixpkgs_channel"?


Bug - Back up of address book is a JSON file

Under the Accounts tab, click my contacts and when you click the back up address book , the file generated is a JSON file. is that ok ? i'm not sure on the expected result @AdriaCarrera

@surekabpm yes. This is expected. In json file is backup of address book.


WHERE clause sometimes fails in filtering results but adding non-existing lines

Hello!
I found that the following Kuzu may return incorrect results for the following Cypher queries with WHERE clauses.
For the first query, I do not add any WHERE clause to filter results, and it returns 4 lines of zero (n2.p13 = zero):
MATCH (n1:L1)-[]->(n2),(n1)-[]->(n2:L0:L3:L1)-[]-(n1) RETURN n2.p13

For the second query, I add a redundant WHERE clause n2.p13 = 0, but it will return 16 lines of zeros.
MATCH (n1:L1)-[]->(n2),(n1)-[]->(n2:L0:L3:L1)-[]-(n1) WHERE n2.p13 = 0 RETURN n2.p13

I have uploaded the graph data here G.zip Sorry that the graph data is a little complex.
It would be highly appreciated if you can further verify and investigate this report.
Best regards,
Qiuyang

Hi, thanks for filing the issue. Just adding the kuzu version here for us to be able to reproduce: the database that's shared is using kuzu==0.1.0. Have you also tried this with the latest version of kuzu? We're on 0.3.x now.

Hi @joyemang33, thanks for reporting. I'm able to reproduce this on 0.3.1.  We will fix this bug soon.

This has the same root cause of #3570 and should be solved in #3584


Put model to default device before initializing optimizer

Put model to default device before initializing optimizer, because otherwise this would crash for an optimizer like AdaGrad, complaining that optimizer tensors are on cpu, not model tensors are on gpu.

something wrong with poetry.lock...


Discussion: Should we set the default logging format to CRI?

The default logging format is currently set to docker. Kubernetes deprecated the docker runtime in 1.20 in favor of CRI.
Should this stay or should the default be migrated to CRI?

So... Interestingly, the container runtime is exposed in the discovery labels, which I just learned.
Further, there is an agent module which handles a lot of this magic, including fetching, and passing along the container runtime to inform the processing stage. 🤔
https://github.com/grafana/agent-modules/blob/main/modules/kubernetes/logs/targets/logs-from-worker.river#L54-L72

Ooh, I really like this approach.


Is home-assistant/homeassistant/components/nederlandse_spoorwegen/ working?

Couldn't fetch stations, API password correct?: 400 Client Error: Bad Request for url: http://webservices.ns.nl/ns-api-stations-v2
But my password is really correct! Could this plugin or API be old?

Please fill out the issue template.  Even though those details may seem unimportant, any tidbit helps.

Hey oke. Here's the error code from "full home assistent log":
2019-06-11 18:52:30 ERROR (SyncWorker_8) [homeassistant.components.nederlandse_spoorwegen.sensor] Couldn't fetch stations, API password correct?: 400 Client Error: Bad Request for url: http://webservices.ns.nl/ns-api-stations-v2
-The password is really correct. The code correct also (in de sensor section of configuration.yaml):

platform: nederlandse_spoorwegen
email: bla
password: bla
routes:

name: Utrecht-Amsterdam
from: Ut
to: Asd
name: Amsterdam-Utrecht
from: Asd
to: Ut

I think there is a problem with ns-api-stations-v2? Could that be?

Exactly the same issue, if you managed to solve it, please let me know.

I did my best to tell the makers here that there is trouble with it. But no response... :-(

The API has changed, however, the package Home Assistant uses has not been adjusted to this yet.
For more information about this, see: https://github.com/aquatix/ns-api/issues/16

Ah there is a maker! It's sometimes difficult to find out who's the owner to talk to about HomeAssitent modules wich are advertised at https://www.home-assistant.io/components/
Well hope it can be fixed. The trains would be a great addendum to HomeAssistent. :-)

This integration was contributed in the past but currently has no code owner.

We’ve all received notice some time ago NS was about to change their api.
In my setup the integration still works fine though ...

Could it be that if you got that old API in your NS account that it works. And if you have a new NS account, you won't have that old API by default, so the Spoorwegen integration cannot connect to the right API?

I wouldn't know tbh. As far as the letter from NS goes, the old Api won't be stopped until October 1st. Personally I haven't setup a new one yet, so you might be right the new one isn't compatible with the current integration ....

Hmm gonna close this topic to keep things clean. But it's unsolved.


scalability: add scheduling introduction

Signed-off-by: nolouch<EMAIL_ADDRESS>

What issue does this PR solve?

close https://github.com/tisonkun/tikv-dev-guide/issues/13

What is changed:
add the scheduling
more ref: https://github.com/tikv/pd/wiki/Scheduling-Introdction

Thanks for your contribution @nolouch ! I'm reviewing now.

ping @nolouch

Thanks for your contribution @nolouch ! Merging...


Feature: Be able to create tables and custom forms

Be able to create tables and custom forms

It's a template. You can def add forms and tables using the provided tools (supabase/sveltekit/daisy).


[common] add OnceCallback which can be invoked for at most once

This commit adds a new facility which wraps up a std::function
and makes sure that a function can be invoked for at most once.
This is useful for async operations to guarantee that the callback
for receiving the result will be only invoked once.

why not use Abseil?

There can be platforms which Abseil doesn't support.

@jwhui There is another significant enhancement PR (https://github.com/openthread/ot-br-posix/pull/1113) which is depending on this commit, PTAL :)


Differences with nplusone?

Hi! Thanks for building this tool, it sounds very useful.
Docs do not specify why this tool was created: what are the main differences with nplusone?
Thanks again!

hi @sobolevn, great question! i just added a small section with the main differences to the README: https://github.com/taobojlen/zealot?tab=readme-ov-file#comparison-to-nplusone
out of curiosity, how did you hear about zealot?

You are featured on https://django-news.com :)


feat(storyblok): add a content version parameter and the possibility of making a custom config

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

For storyblok indexing, developers can choose the version of content they want to index (generally draft in development/staging and published in production). They can also set a custom configuration for retrieving stories.
This is required because currently we can only index content in draft state, and it will only index top-level pages (not those in folders). A bit annoying when you want to build a professional website.
Checklist:

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes (if not applicable, please state why)

@Baroshem


Add coordinates, remove NSEW fields.

@danielbaker @yetti @scoen @MingtaoSun

ok :+1:

looks good. i guess we could clean up the existing properties in the dbs too

@scoen I was planning to do that as part of a banjo migration.

sounds good

@AaronCMuller , Hi Aaron, I wonder when you are going to put in the banjo side of change. There is compilation error in WorkFields when I update pom version to 1.6.4

@MingtaoSun Hopefully this week. Do you need to upgrade to 1.6.4 or later?

No, not necessarily. I can do with 1.6.3.


add synthetic test that asserts reproduction of remote reference processing

tests/synthetic/test_compare_synthetic_processing_with_archived_results.py
is comparing single station results at every commit,
but an analagous test for remote reference should also be set up.

This should be done before #108 so that tests of the m_estimator underlying TRME and TRME_RR are both validated when issue #108 is pushed.

aurora/tests/synthetic/test_compare_aurora_vs_archived_emtf.py
Now has a test called run_test2r1.  This applies remote reference processing to station "test2", remote references against station "test1", and asserts expected results are obtained.


Add Statusengine to list of integrations (Forwarding)

More information about Statusengine and Tutorial about how to setup: https://statusengine.org/tutorials/Graphite-Grafana/

Codecov Report

Merging #2452 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2452   +/-   ##
=======================================
  Coverage   80.05%   80.05%
=======================================
  Files          85       85
  Lines        8948     8948
  Branches     1914     1914
=======================================
  Hits         7163     7163
  Misses       1511     1511
  Partials      274      274

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 c4ca9cf...7087a99. Read the comment docs.


Fix #1263 : Fix fmp's build wait section according to k8-client

#1263

It seems a permutation of old code, why does it fix the error?

Yeah, It's just a result of several hit and trials. I wasn't sure whether it's the right thing that's why I
added you as a reviewer since you wrote this file. I was trying to upgrade to latest kubernetes-client
when I faced this. After looking at the code problem seem to be coming from waitUntilPodIsReady() method.
I'm afraid I don't quite have an exact answer to why this is working, but I would explain what I observed
while doing this. We are getting onClose() callback from Watcher with null cause before eventReceived callbacks(in which buildHolder is being set) here : https://github.com/fabric8io/fabric8-maven-plugin/blob/9986dc520d140aeccaf1c2927506d51cb0f27b0e/core/src/main/java/io/fabric8/maven/core/service/openshift/OpenshiftBuildService.java#L471
When I remove that waitUntilPodIsReady() method from that wait build section(which I had added in PR#1147
, the error is gone but then I get that container in pod waiting to start warning. I think here the problem
is that we're watching both Build Pod(which I added to fix #1132) and Build resource itself. Now by changing
the order we still get onClose() callback, but we wait for additional time for build pod in which eventReceived callback comes and sets buildHolder.

retest this please

@nicolaferraro : I've realized that the previous approach is not the right solution. It just avoids the error. I've refactored that code to use one watch only for build logs and Build resource. Does this change make any sense to you?

@nicolaferraro : The root cause of why we're getting onClose() callback from Watcher with null cause before eventReceived() callbacks is due to watcher getting closed here: https://github.com/fabric8io/kubernetes-client/blob/master/kubernetes-client/src/main/java/io/fabric8/kubernetes/client/dsl/base/BaseOperation.java#L711
This was added to avoid thread leak in WatchConnectionManager, You can have a look at this PR: fabric8io/kubernetes-client/pull/974

I think there's a error in the client, going to open a PR to fix it.

Closing this as actual fix is in fabric8io/kubernetes-client#1074


Enable Attribute calculation for different data types

implements:

https://github.com/code-kern-ai/refinery/issues/142

works with:

https://github.com/code-kern-ai/refinery-gateway/pull/68
https://github.com/code-kern-ai/refinery-ac-exec-env/pull/6
https://github.com/code-kern-ai/refinery-ui/pull/75
https://github.com/code-kern-ai/refinery-tokenizer/pull/11

I might be mistaken but i think there is still something to be done for data types != string since not only the docbins are prepacked in the s3 file

Something like reuploading (without recalculation) should do the trick.

[ ] resolved


neutrinonotify: async call GetUtxo from RegisterSpendNtfn

Since GetUtxo is a potentially long running call, we would see
RegisterSpendNtfn block in some cases, in particular on starting the
chain watcher, causing lnd to hang on startup.
This commit makes the call to GetUtxo in a go routine, letting
RegisterSpendNtfn return immediately when the notification events are
created.

Why is this necessary if we already pass the quit chan through a functional option?

Ah I see, it can stall while starting the chain watchers, so if we shutdown before that, then Stop won't be called and the quit chan won't be closed.


Fix CEP batching FCFS mode to group CEPs per namespace.

Fix CEP (CiliumEndpoint) batching FCFS (First Come First Served) mode to group CEPs per namespace. Initial change was introduced to always add new CEPs to the largest CES (CiliumEndpointSlice), but didn’t take into account splitting them by namespaces, which is a bug. https://github.com/cilium/cilium/pull/20969
Signed-off-by: Dorde Lapcevic<EMAIL_ADDRESS>

/test

Hi @tklauser, there are 3 failing tests that seem to be flaky.
Can you please help me move it forward?
Thanks

Hi @tklauser, there are 3 failing tests that seem to be flaky. Can you please help me move it forward? Thanks

I've re-triggered the flaky tests. The remaining failures are known flakes:

the "runtime" failure is fixed on master branch by https://github.com/cilium/cilium/pull/22043.
the "k8s-1.16-kernel-4.9" failure is https://github.com/cilium/cilium/issues/21735

All other tests passed, marking as ready to merge. Thanks for your contribution @dlapcevic.

Thank you @tklauser and @pchaigno!

Thank you for your contribution!


Wrong translation of fielded enum/not refusing to do so

#[repr(u8)]
pub enum FieldedEnum{
    A(u8),
    B(i8),
}
std::mem::size_of::<FieldedEnum>() -> 2

currently this gets translated as
public enum FieldedEnum : byte
{
  A,
  B
}

which is wrong in length
i am not sure if this is stabilized, but if the length of each field is the same i guess it may even now be considered okay to use.
https://doc.rust-lang.org/nomicon/other-reprs.html
i would suggest implementation like this:

using System;
using System.Runtime.InteropServices;

[StructLayout(LayoutKind.Sequential)]
public struct MyData
{
	public enum Variant : byte
	{
		A,
		B
	}

	[StructLayout(LayoutKind.Explicit)]
	private struct Union
	{
		[FieldOffset(0)]
		internal byte A;

		[FieldOffset(0)]
		internal sbyte B;
	}
    public Variant Type { get; private set; }
    private Union data;

    public byte A
    {
        get
        {
            if (Type != Variant.A)
                throw new InvalidOperationException($"{nameof(MyData)} is not of variant {nameof(Variant.A)}, but {this}");
            return data.A;
        }
        set
        {
            Type = Variant.A;
            data = new Union {A = value}; //must be done with with to make sure all other fields are zeroed out
        }
    }

    public sbyte B
    {
        get
        {
            if (Type != Variant.B)
                throw new InvalidOperationException($"{nameof(MyData)} is not of variant {nameof(Variant.B)}, but {this}");
            return data.B;
        }
        set
        {
            Type = Variant.B;
            data = new Union {B = value};
        }
    }

	public override string ToString()
	{
		switch (Type)
		{
			case Variant.A:
				return $"{nameof(MyData)}.{nameof(Variant.A)}: {A}";
			case Variant.B:
				return $"{nameof(MyData)}.{nameof(Variant.B)}: {B}";
			default:
				throw new InvalidOperationException("Invalid variant of {nameof(MyData)}!");
		}
	}

}

https://dotnetfiddle.net/PDCeTO

Thank you for your report.
We have considered it, but the enum of rust is very flexible, so it seems difficult to fully support it.
Unfortunately, it would be better to have them use a C & C# compatible enum.
However, as you gave us an example, incomplete enum output is a problem. So an implementation has been added that eliminates fielded enums.


add CLA checker to this repo

Adriaan had mentioned this in the context of this repo specifically, but I realized later it's actually an issue pretty much organization-wide, so I'm closing in favor of https://github.com/scala/scala-dev/issues/269


perf(mapper): avoid O(N^2) algorithm

Speed up neovim startup time by keeping the mapper_records data
structure entirely on the Lua side.
Copying it back and forth through the vimscript bridge (vim.g) would require
processing the entire table every time a new mapping is added, resulting
in an at least O(N^2) algorithm for N mappings.
This saves ~48ms of startup time (about half of my Neovim startup time).
Measurements done on a default doom-nvim install with NVIM v0.7.0 on
Fedora 36:

Command
Mean [ms]
Min [ms]
Max [ms]
Relative

HOME=compare_old nvim --headless -c "noautocmd qa!"
93.8 ± 1.7
91.2
99.8
2.06 ± 0.05

HOME=compare_new nvim --headless -c "noautocmd qa!"
45.4 ± 0.7
44.1
47.6
1.00

Measurement system:
CPU: 12-core AMD Ryzen 9 3900X (-MT MCP-) speed/min/max: 3776/2200/4672 MHz
Kernel: 5.17.11-300.fc36.x86_64 x86_64 Up: 3h 1m
Mem: 5971.2/64280.0 MiB (9.3%) Storage: 24.99 TiB (0.5% used) Procs: 499
Shell: Zsh inxi: 3.3.16

I've also benchmarked the pure Lua and vim.g.mapper_records methods in more detail: https://gist.github.com/edwintorok/01890b48caa300063be00ab2ead179f9
Here is a plot, the vim.g method becomes slower and slower the more keybindings are added (shown on a log scale here), e.g. at 200 keybindings we are already at ~76ms, whereas the pure Lua method of storing state is at ~0.2ms. With more keybindings this would become even slower (it can reach ~0.5s with enough keybindings):

(FWIW doom-nvim has ~145 keybindings by default, so having a lot of keybindings is not that far fetched)

Oh nice ! I didn't realize using the vimscript bridge would have this much of an impact, thanks for the work and explanation !


Sign in with GitHub Failure

Type: Bug
Hi, Support Team
Recently, I have been unable to signin with GitHub.
I've already reinstalled VSCode and reset VSCode local config, but  I couldn't solve the problem
I am not familiar with Proxy and did not know what to do.
I would appreciate it if you could help me solve this problem. Thank you in advance.

VS Code Version: 1.90.2
OS Version: Windows_NT x64 10.0.26120

Below is GithubAuthentication log.
2024-06-25 00:55:28.782 [info] Getting sessions for user:email...
2024-06-25 00:55:28.782 [info] Got 0 sessions for user:email...
2024-06-25 00:55:29.744 [info] Logging in for the following scopes: user:email
2024-06-25 00:55:29.748 [info] Trying without local server... (user:email)
2024-06-25 00:55:32.424 [info] Exchanging code for token...
2024-06-25 00:55:42.516 [error] request to https://github.com/login/oauth/access_token failed, reason: socket hang up

Below is Network Proxy Test log.
VS Code 1.90.2 (5437499feb04f7a586f677b155b039bc2b3669eb)
Network Proxy Test 0.0.11
win32 10.0.26120 x64

Settings:
- http.proxy:
- http.proxyAuthorization: null
- http.proxyStrictSSL: true
- http.proxySupport: override
- http.systemCertificates: true

Environment variables:

Sending GET request to https://github.com...
vscode-proxy-agent: DIRECT
Received error: socket hang up (ECONNRESET)
Retrying while ignoring certificate issues to collect information on the certificate chain.

Sending GET request to https://github.com (allowing unauthorized)...
vscode-proxy-agent: DIRECT
Received error: socket hang up (ECONNRESET)

@chrmarti could you take this one first? Does it mean anything to you?

Could this be the firewall (or transparent proxy) denying access to github.com?

@chrmarti
Thank you for your reply!
I have turned off Domain network, Private network, and Public network in reference to the following, but nothing has changed and I get the same error as above.
https://support.microsoft.com/en-us/windows/turn-microsoft-defender-firewall-on-or-off-ec0844f7-aebd-0583-67fe-601ecf5d774f
What specific action should I take?

@xyytgae Can the web browser access https://github.com? Do any other applications have network issues? ECONNRESET seems to be the remote end of the connection hanging up.

@chrmarti
I changed the Types of NAT on my LAN Router and now I have access!!
I was able to sign in to GitHub with VSCode!! VSCode was irrelevant!
Sorry for the inconvenience.
Sorry VSCode!
Thanks to @chrmarti and @TylerLeonhardt for support!

@xyytgae Out of curiosity: What was the NAT type that didn't work and which one now does work?

@chrmarti
Symmetric NAT didn't work, but Cone NAT did.

From what I read, the main difference is that Cone NAT allows other hosts than the original destination host to respond to UDP requests. 🤔


Cannot Estimate gas fees

while calling mutable functions of contract like transfer, transferFrom we are  facing this "Estimate gas fees " issue

can estimate gas issue is fixed now. from now onwards developer can set his gas strategy priority to low, medium and High #241


samples: bluetooth: mesh: Add basic documentation

Add documentation for the mesh and mesh_demo sample applications.
Fixes #6279
Signed-off-by: Johan Hedberg<EMAIL_ADDRESS>

Codecov Report

Merging #6457 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6457   +/-   ##
=======================================
  Coverage   53.16%   53.16%
=======================================
  Files         431      431
  Lines       41085    41085
  Branches     7899     7899
=======================================
  Hits        21841    21841
  Misses      16037    16037
  Partials     3207     3207

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 04a0a26...2ee6a8c. Read the comment docs.

@dbkinder I've pushed an update which should (hopefully) address all the issues you brought up.


Fix x86 target compilation

Hello,
I believe recent changes (https://github.com/pykeio/ort/pull/48) have broken x86 compilation. The current bindings are currently setting a special case for x86 targets, replacing size_t by usize when generating the bindings: https://github.com/pykeio/ort/blob/254a5ce8f059f28356393c2c72fae8df6fde5457/build.rs#L660 resulting in https://github.com/pykeio/ort/blob/254a5ce8f059f28356393c2c72fae8df6fde5457/src/bindings/linux/x86_64/bindings.rs#L376
This means that sys::OrtROCMProviderOptions expects a usize for the gpu_mem_limit field rather than a c_ulong. The current code does not compile with the following error message:
 gpu_mem_limit,
 ^^^^^^^^^^^^^^ expected usize, found u32

This PR handles the special x86 architecture case, and should hopefully maintain M1 mac compatibility from the previous PR.
This could also be fixed by casting into the expected type with:
let rocm_options = sys::OrtROCMProviderOptions {
        [...]
	gpu_mem_limit: gpu_mem_limit.try_into().unwrap(),
        [...]
};

Please let me know what your preferred solution would be, happy to amend the change request

Codecov Report

Merging #49 (6df47e3) into main (254a5ce) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 6df47e3 differs from pull request most recent head c691073. Consider uploading reports for the commit c691073 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main      #49   +/-   ##
=======================================
  Coverage   48.71%   48.71%
=======================================
  Files          19       19
  Lines        1051     1051
=======================================
  Hits          512      512
  Misses        539      539

Impacted Files
Coverage Δ

src/execution_providers.rs
5.00% <ø> (ø)


add gitbook integration

https://www.gitbook.com/
https://help.gitbook.com/github/how-can-i-import-repo.html
https://gitbookio.gitbooks.io/documentation/github/index.html

@omurbekjk If you want to work on it, go ahead :+1:


Error occurred while evaluating on validation set

When trying to evaluate based on pre-trained snapshot by calling
CUDA_VISIBLE_DEVICES=0 sh scripts/command_test_v1.sh

An error occurred: number of files for evaluation: 3769 ERROR: Couldn't read: 000560.txt of ground truth.

Hi, I guess you didn't prepare the training labels of KITTI，look at the script command_test_v1.sh carefully.
train/kitti_eval/evaluate_object_3d_offline dataset/KITTI/object/training/label_2/ train/detection_results_v1
you need to download the "Download training labels of object data set (5 MB)" from KITTI and organize the folders as dateset/README.md requests. In fact, you only need to place the label_2 on the right path to run this scripts.
I hope this can help you.


Update about.md

Wei Qi is an associate professor in the the Department of Industrial Engineering at Tsinghua University.

It looks like you are attempting to push a change to the template repository, for help with deploying your own website please start a new thread in the discussions.


Improve documentation about VideoPlayer video formats

This closes https://github.com/godotengine/godot-docs/issues/4021.

Cherry-picked for 3.2.4.


Name of allocator_example changed.

It looks like the executable is now called allocator_tutorial.

@fujitatomoya Ah, yes. I see what you are saying. I can update that as well.

@fujitatomoya Do you simply want the node names updated? Or do you want all the example code to use the updated methods in allocator_tutorial? It looks like a number of the methods have changed between the example code and the new allocator_tutorial. I'm not sure if the methods used in the example code are still valid.
For instance: the example code passes the shared pointer to MyAllocator directly to  node->create_publisher whereas allocator_tutorial creates a PublisherOptionsWithAllocator struct. It looks like passing the allocator directly to node->create_publisher is no longer valid syntax.


Add RUM to live site

add RUM (Real User Monitoring) to the live site? https://www.aem.live/developer/rum#how-to-add-rum-instrumentation-to-your-site, this way we will have more accurate information "before" and "after" we go live.

Will be resolved on the AEM side in CodeHub.
Scheduling to deploy on Sept 16.


v1.2.0 does not respect NAMESPACE variable.

Attempting to execute
NAMESPACE=mynamespace
VERSION=v1.2.0
kubectl apply -n "${NAMESPACE}" -f "https://github.com/kiegroup/kogito-cloud-operator/releases/download/${VERSION}/kogito-operator.yaml"

results in the following error
You must pass '--namespace=kogito-operator-system' to perform this operation.
the namespace from the provided object "kogito-operator-system" does not match the namespace "mynamespace".

Using NAMESPACE=kogito-operator-system results in a valid deloyment

Hi, @jarradh thank you for opening the issue :)
The YAML installer we have deploys the operator in its own namespace kogito-operator-namespace and watches all the objects in the whole cluster(cluster-wide deployment). So the NAMESPACE var is not respected, it is hard-coded in the yaml itself.  I agree we need to update our README and describe more about the behaviour of this installation.


Is there a localization API for the Next/Previous buttons?

What version of React-Table are you using?
Your bug may already be fixed in the latest release. Run yarn upgrade react-table!
6.6.0
What bug are you experiencing, or what feature are you proposing?
Localization API for all text in the elements.
I'm looking for an API to localize the text on the different elements. Is there any, or should I implement it myself by targeting the elements?

+1

It's in the doco....
  // Text
  previousText: 'Previous',
  nextText: 'Next',
  loadingText: 'Loading...',
  noDataText: 'No rows found',
  pageText: 'Page',
  ofText: 'of',
  rowsText: 'rows',

how to get to button style?


Fix fsnotify util upstream link and suggest newer version.

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The fsnotify.org domain no longer belongs to the project, we should just refer to the github repository instead.
Additionally a newer version of fsnotify package gopkg.in/fsnotify.v1 has been released (2018), we should possibly be suggesting that instead of the old (2015) v0?
Which issue(s) this PR fixes:
Fixes #240
Special notes for your reviewer:
Is this util even still required? How can we check if it is still being consumed?

/kind cleanup

/approve
/lgtm


ci: fix sonarcloud scan pr source

Sonarcloud thinks that every branch is "main" (see https://sonarcloud.io/project/branches_list?id=ionos-cloud_cluster-api-provider-proxmox)
This is an attempt to fix that
Warning: the check run here uses the workflow from main, so I cant be sure if this works. I'd be happy to receive other suggestions

There are a few things to consider here.
I guess you found this page, but another page mentions sonar.branch.name and sonar.branch.target. Then the github action setup docs don't mention any of these.
The scan action seems to have access to GITHUB_EVENT_NAME, but also GITHUB_BASE_REF, GITHUB_HEAD_REF and GITHUB_REF. That should be enough to automatically fill out the required information.
Here are action logs showing the event name:
INFO: Load project pull requests
INFO: Load project pull requests (done) | time=205ms
INFO: Load branch configuration
INFO: Github event: pull_request_target
INFO: Load branch configuration (done) | time=3ms

Then there's this issue https://github.com/SonarSource/sonarqube-scan-action/issues/29 which also mentions that sonar.pullrequest.* should be populated.
I tried looking finding where these variables are used, but couldn't find anything at first glance in https://github.com/SonarSource/sonar-scanner-cli or https://github.com/SonarSource/sonar-scanner-commons
I'm not saying your change won't work, but I think the culprit actually is sonarcloud here. So I'd propose that you open an issue (or reopen the one I linked).

I agree with you that sonar should already have all the necessary information but I dont think that this is sonar's fault. We are doing an unconventional checkout here: https://github.com/ionos-cloud/cluster-api-provider-proxmox/blob/01b3f7f6dc8c27aa0f50727401c1c14c818aa402/.github/workflows/test.yml#L22-L29
This is a workaround for branches across forks, my theory is that this confuses the sonar scan. I don't know how one would solve that properly

Old thread but it doesn't seem like much has changed since and sonarcloud still doesn't support pull_request_target:
https://community.sonarsource.com/t/github-comments-stopped-working-in-github-action-after-switch-to-pull-request-target/42556/12

Old thread but it doesn't seem like much has changed since and sonarcloud still doesn't support pull_request_target: https://community.sonarsource.com/t/github-comments-stopped-working-in-github-action-after-switch-to-pull-request-target/42556/12

Yeah, that's what I figured. I thought that opening an issue would shed some light on this

Looks good to me, tested in a test-PR: https://github.com/ionos-cloud/cluster-api-provider-proxmox/pull/91


Failed to get certificate URL

Getting the certificate's URL ...
-> Key Vault Name        : 'pkrkv****l8x9'
-> Key Vault Secret Name : 'packerKeyVaultSecret'
...failed to get certificate URL, retry(0)
...failed to get certificate URL, retry(1)
...failed to get certificate URL, retry(2)
...failed to get certificate URL, retry(3)
...failed to get certificate URL, retry(4)
Error occurred unmarshalling JSON - Error = 'json: cannot unmarshal number into Go value of type string'.
Receiving this error for Azure ARM based packer build for Windows-2012-R2 SKU. Help !

Packer Azure ARM development occurs in the official Packer repository.  Please log and review all issues from that repository.
This appears to be a duplicate of a fixed issue.  Unfortunately, a new release of Packer with the fix has not been made.  You will need to rebuild master to get the fix.  I posted a private build to another dupe of this issue if that is preferable.


👋 add quickstart.py & more install instructions in readme

added written guide for beginner programmers and the quickstart code from readme as file
Seems like many people want to use this Bot  but are struggeling with the basic usage ( #233 ,  #231, #221, #218, #160,#149)
This will help to get them started using this project.
@sudoguy thanks for the project & please merge

Hi @ezzcodeezzlife! Thank you!


Exception in Index.singleClass() when applied to module-info.class

When a client invokes method singleClass() on org.jboss.jandex.Index and provides an argument that represents module-info.class, the method fails with NoSuchElements exception. This is caused by an assumption that a map holding known classes is never empty and therefore it is safe to call .iterator().next():
https://github.com/smallrye/jandex/blob/f8b6fa83b6b0141a2173eb428b2ba9e07f76ab2b/core/src/main/java/org/jboss/jandex/Index.java#L278-L283
In my case it occurs in WildFly 33.0.1, while trying to examine bean archive candidate Wicket-CDI 10.1.0; the deployment attempt is immediately aborted. When I manually deleted module-info.class from the Wicket-CDI JAR file, the deployment worked as expected. (The mentioned version of WildFly contains Jandex version 3.2.0 within its system modules.)
I believe the correct response would be to return null.

That doesn't seem right on the first sight, even a module-info.class should result in a valid ClassInfo. I'll take a look.

Ah, now I understand. Indexer.processClassInfo() does
if (!currentClass.isModule()) {
    classes.put(currentClass.name(), currentClass);
}

so while there is a ClassInfo for the module, it isn't put into the map of classes. Should be straightforward -- if Index.singleClass() gets an Index with no classes, check the modules.


How to get HTML Export

i'm using this pack with nuxt.js. Everything work fine but just export how to make HTML ?
This example content:
qweqeqweqeqewq ##<PHONE_NUMBER>23123 > qweqweqeqeqeqweqeqeqwe - - - * [x] qwe * [x] qweqw * [ ] eqwe * [ ] qwe * [x] 12 * [x] 3123 * [x] 123 * [ ] 123 | qweqw | eqeq | wqeqw | qweqwe | | ----- | ---- | ----- | ------ | | qweqwe | qeq | weqwe

Use invoke method with getHtml.
Please refer to the example below.
https://github.com/nhn/toast-ui.vue-editor#method

Thanks. Work now.


chore: bump fulcio, trillian and ct

Use the latest versions of these dependencies to eliminate failures in snyk.

Hi @lance, unfortunately current Github actions does not work agains fork repositories and it will fail because of missing secret credentials for podman.


Feature request: Customizable width on homepage

Feature: I'd like to be able to customize the home screen to better fit my monitor setup (2k's) - being able to customize it would allow all users the ability to fine tune to their liking
Before:

After (removing the attribute, but maybe somehow could be a backend # setting?):

Would also like the ability to replace the Share Me on the top left with an image, or make it customizable, or add a custom.css

I have wide monitors as well and intentionally limited the width to keep the content centered on my screen. 😅
I think this addresses the bigger possibility to enable theming. Unfortunately as I used Mantine class names aren't that easy to override. But I will look into the possibilities and keep this ticket updated.
For now, I can take inspiration from MonicaHQ and add a APP_LAYOUT environment variable that has full-width and md/lg as options. Then all screens need to use this setting for their max width.


Remove preferGlobal

➜ npm install
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>
Could you remove "preferGlobal": true?
It's no any sense and bad practice as well.

The CLI requires to be installed globally, hence the warning.

@MichielDeMey, so why it should be installed globally?

Otherwise your system won't be able to recognize the CLI, unless you add your project's node_modules folder to your $PATH variable.
When installing it locally
➜ npm i marked
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
<EMAIL_ADDRESS>node_modules/marked
➜ marked
zsh: command not found: marked

When installing it globally
➜ npm i -g marked
<EMAIL_ADDRESS>node_modules/marked
➜ marked -o output.html
// works!

I see what you mean, but I don't see any sense to install it globally.
Why the package should be installed globally?

It doesn't have to be installed globally to use the library, but it has to be if you plan to use the CLI.
Hence it's just a warning and not an error.

but it has to be if you plan to use the CLI.

There's an line in package.json for that:
 "bin": "./bin/marked"
``

That line won't tell NPM to symlink it to the $PATH.
From the NPM package.json specification:
On install, npm will symlink that file into prefix/bin for global installs, or ./node_modules/.bin/ for local installs.

So commands like
cat content.md | marked -o output.html

won't work if you install it locally, but will work if you install it globally.

won't work if you install it locally, but will work if you install it globally.

I see what you mean, but why it should be preferred for all users?
Npm does not recommend installing packages as root:

Using sudo with npm is Very Not Recommended. Anyone can publish anything, and package installations can run arbitrary scripts."

It was explained later in more detail as:

Option 4: HOLY COW NOT RECOMMENDED!!

Why is evil?
How many users prefer this method of installation of ?
Do know who uses this package? 1165 packages!
I don't want to see the warnings :kissing:

You should definitely NOT install anything as sudo.
This tool does not force you to install it using the sudo command, so I don't see the issue.
There is a difference between
sudo npm i -g marked

and
npm i -g marked

The former is not recommended like you said since it gives npm packages sudo powers.
If you can't install global npm packages without running sudo then your npm environment is bugged and you should solve it.
Check out SO on how to solve it.
http://stackoverflow.com/questions/19352976/npm-modules-wont-install-globally-without-sudo
Apart from that, no one is forcing you to install it globally and it will work just fine when installing it locally.
The warning is just there for those who wish to use the CLI, if you don't need it you may safely disregard the warning.

if you don't need it you may safely disregard the warning.
I don't want see this warning, because there're no any reason for it.
Can you answer my question, why it should be preferred for all users?
It's really strange.

To use a cli mode, it is recommended to install packages globally. This is because you most likely do not have or want to add the node_modules folder for marked to your system $PATH variable.
If you do not want to use cli mode then don't install globally and ignore the message.
The warning is meant for people who are expecting to use cli mode since there may be issues in doing so unless the package is installed globally.

The warning is meant for people who are expecting to use cli mode since there may be issues in doing so unless the package is installed globally.

Did you see README.md?
npm install marked --save

Why not:
npm install marked -g

it's confused!
I want to find out why this method of installation is preferred for all users and not documented.
If someone wants to use the cli, let them read the doc :yum:

doesn't happen in npm v3 https://github.com/npm/npm/issues/1648

I do see this with npm 3.5.3 and I also think the warning unwarranted.
If people want to use the CLI then they should install it globally.
No point of having a warning for people who are using it just as a library.

Many engineers require no warnings or errors during installation of a project.  They can cause confusion, especially to less technical people who may think there was an install error.  Global dependencies can also make deployment more complicated.  In my opinion preferGlobal should be deprecated.
Is there anything preventing working around the issue with $PATH, like running with ./node_modules/.bin/marked?  If not, perhaps splitting the cli component into its own module a la grunt-cli would allow us to prevent the superfluous warning message in our projects…
~My 2¢

Agreed that this module should not preferGlobal. Even as a cli, it should be used locally with $(npm bin) or via an npm run-script. (these are the recommended ways to use CLIs within a project; unless the utility is intentionally not associated with a project, like a scaffold-generators for instance)


Translation of More Shield Variants into Ukrainian

Could you add the Ukrainian translation created by me?
This is to "mod-folder"/lang
uk_ua.json

This is to minecraft/lang
uk_ua.json

@pnk2u ?

Pull requests: https://github.com/pnk2u/More-Shield-Variants/pull/10, https://github.com/pnk2u/More-Shield-Variants/pull/11

Translation has been added


Some final updates to pull over from release branch

A few remaining updates that were made to the release branch that need to be ported to main

/azp run java - storage - tests

API change check for com.azure:azure-storage-blob-changefeed
API changes are not detected in this pull request for com.azure:azure-storage-blob-changefeed

API change check for com.azure:azure-storage-blob-nio
API changes are not detected in this pull request for com.azure:azure-storage-blob-nio

API change check for com.azure:azure-storage-file-datalake
API changes are not detected in this pull request for com.azure:azure-storage-file-datalake

Overriding check enforcer to get updates in despite some broken service tests

/check-enforcer override


Support Topic Alias, User Properties, ContentType and payloadFormatIndicator

#253

support SUBSCRIPTION_IDENTIFIER RESPONSE_TOPIC CORRELATION_DATA CONTENT_TYPE
to close #240


What is the benefit from from passing the repo reference to the commands?

@akonwi I see in branch 1.0.0 u start pass the repo reference to the commands but the only use i see until now is that u use to get the repo path.

Atom now allows opening multiple folders in one project. This is why atom is deprecating project.getRepo() in favor of project.getRepositories(). If a user has multiple git repos open in a project and they open the git-plus menu, while they aren't working on a file in either of those repos, then they are given the choice of which repo, they want to do these commands on. Once they make that selection, the commands in the menu use that selected repo to run the command.
Because there is the chance that someone is working with multiple repos in the same project, we can't simply rely on atom.project.getRepositories()[0] in every command. But if there is only one repo, then git.getRepo() will resolve to that. Also, if there is a file open, the package will try to return the repo that file belongs to if it is in a repo.


Doesn't support ingressClassName and latest nginx-ingress controller

Doesn't support nginx-ingress v 1.0.0 https://github.com/kubernetes/ingress-nginx/blob/main/Changelog.md

https://github.com/sorry-cypress/charts/pull/72

Resolved in #74


Support Alloc from cli & on questions format

Overview
The purpose of this pull request is to allow the user to dynamically set the balance of any given account. The motivation for doing this is that using repositories  like Quorum-Kubernetes people are assigning the balances they want to give to certain addresses in the yml files, but is unable to translate into the generated config file to to lack of support for the alloc [tag.]
Alloc Issue Quorum-Kubernetes
Further investigation shows that this is because they are using quorum-genesis-tool to create their config file:
Here
Here
Here
Here
Following this (hopefully successfull pr) I would love to make a pull-request on quorum-kubernetes repo to enable this functionality
Example usage
CLI
cd build
node index  --consensus QBFT --alloc '{"0xefE756027E36D021B0063CEDf576402C96C8095e": { "balance": "50000000000000000000000000000000000000000000" },"0xC8560eeF2391cE0Ae6A698E586DE9e15c86F2680": { "balance": "50000000000000000000000000000000000000000000" }}'
Cli (Questions format)
Include JSON format of the prefunded account {'address': { balance: '100000'}}: (default {})"
{"0xefE756027E36D021B0063CEDf576402C96C8095e": { "balance": "50000000000000000000000000000000000000000000" },"0xC8560eeF2391cE0Ae6A698E586DE9e15c86F2680": { "balance": "50000000000000000000000000000000000000000000" }}
Changes Included

Applied to all Consensus Mechanisms
Added support for --alloc flag
Added to cli questions format
Included documentation
Confirmed tests are working

Let me know what you think!

Hi @joshuafernandes and @Ezzahhh,
Let me know if you are interested in supporting this! I think it would be a useful addition!

Hi @ILoomans,
Thank you for your contribution and sorry we got to this so late. I have added a small change regarding types but otherwise looks good to me. We can look to merge this in if you there's nothing else to add

@Ezzahhh Thanks for the review, nothing left to add from my side, Thanks for maintaining this tool it's really great!


Timeout type

non_neg_integer | :infinity
thoughts?

We will definitely need it, so plus one from me.


initializing not with window load doesnt work

i have dimanic DOM elements, and want to initialize mcustomscrollbar after element appear in DOM
but running the function  get this
TypeError: undefined is not a function (evaluating '$(".customScrolled").mCustomScrollbar()')

You can use the live option parameter and call mCustomScrollbar normally without the need to wait for the dynamic elements:
$(".customScrolled").mCustomScrollbar({ live:"on" })
More info about live option:
http://manos.malihu.gr/jquery-custom-content-scroller/#plugin-data-live

thank you, saved the planet)
will try today


Code clean-up

I thought I'd do a bit of a tidy up. This is based on #14 though really depends on the outcome of that
Thanks

Using android P+ features rather than glide/ gif lib seems to improve render cpu usage:

It's around half that of glide use for webp and gif


Remove rust-skeptic dependency

This removes the dependency on skeptic, fixing #250.
I took the approach of considering #[doc = include_str!("../../README.md")], which by chance was already there, scoped to doctest only.

@ubaldop Thanks you for your PR!


install kubernetes use this guide

Hello:
I use this guide install kubernetes cluster,when start apiserver have a error like this:
unable to sync kubernetes service: Endpoints "kubernetes" is invalid: subsets[0].addresses[0].ip: Invalid value: "<IP_ADDRESS>": may not be in the loopback range (<IP_ADDRESS>/8)
what does that mean?

Do you mean you are using https://github.com/kubernetes/frakti/blob/master/docs/deploy.md ?
unable to sync kubernetes service: Endpoints means kubelet is loading an illegal kube-apiserver manifest, which is expected to be generated by kubeadm.
So could you please provide:

the content in /etc/kubernetes/manifests/kube-apiserver.yaml
the k8s version and kubeadm version

@yiqinguo Closing this issue since it is not related with frakti. The original question is at https://github.com/feiskyer/kubernetes-handbook/issues/27.


Cannot @ignore overridden getters

Steps to Reproduce

Extend a class with a getter.
Override the getter and also add @ignore

Expected result: overridden getter is "ignored".
Actual result: error during flutter packages pub run build_runner build.
Assume that Name1 is an external class we have no control over (we can't add @ignore to it.)
Code sample
abstract class Name1 {
  const Name1();

  List<Object?> get props;
}

@embedded
class Name2 extends Name1 {
  const Name2({
    this.name = 'unknown'
  });

  final String name;

  @ignore
  @override
  List<Object> get props => <Object>[name];
}

[SEVERE] isar_generator on lib/models/Name.dart:

Unsupported type. Please annotate the property with @ignore.
package:checkiday/models/Name.dart:13:21
   ╷
13 │   List<Object?> get props;
   │                     ^^^^^
   ╵

Workaround:
List the properties in the annotation and drop the @ignore annotation on the getter.
@Embedded(ignore: <String>{'props'})
class Name2 extends Name1 {
  const Name2({
    this.name = 'unknown'
  });

  final String name;

  @override
  List<Object> get props => <Object>[name];
}

Details

Platform: N/A
Flutter version: 3.3.4 stable
Isar version: 3.0.2

[x] I searched for similar issues already
[x] I filled the details section with the exact device model and version - N/A
[x] I am able to provide a reproducible example

Please use the search before opening an issue. The workaround was introduced specifically for overriding.
The docs also mention how to use it 🙂

Please use the search before opening an issue. The workaround was introduced specifically for overriding. The docs also mention how to use it 🙂

@simc  it would great if you could point me to the documentation or workaround as I could not find it. and still facing with latest version of isar.


Update ApexDocumentation and Code Contributor's Guide to match new styles

The style of http://developer.salesforcefoundation.org/ has changed. We should update the following to match it:
http://developer.salesforcefoundation.org/Cumulus/ApexDocumentation/
http://developer.salesforcefoundation.org/Cumulus/Contributor/
It'd be a good time to also add the same header from the home page to these other pages.

**lurch: attach W-007338

Tracking W-007338


Revert "Deprecate colcon_core.task.python.test.has_test_dependency()"

It turns out that this mechanism is used to communicate the Python-type dependencies from the setuptools options when processing ament_python packages, which otherwise have ROS-type dependencies. So while we're seeing python3-pytest in the test dependency list, the pure python code here looks for the pure python dependency pytest.
Since this doesn't actually save us much time and is clearly still needed, I'll take the same approach in the Python project code as was taken in ament_python so that we can all use the same Python testing task.
This reverts #536.

is there any way we can add a test to catch this situation?

We can't test for it here because colcon-ros is where then shenanigans are happening. Even then, we don't have a regular infrastructure CI job where the changes would have been tested together.


[x] #739

          - [x] #739

[x] https://github.com/octo-org/octo-repo/issues/740
[x] Add delight to the experience when all tasks are complete :tada:

Originally posted by @Nytonecombek in https://github.com/golang/go/issues/65419#issuecomment-1920580508

[x] #739
[ ] https://github.com/octo-org/octo-repo/issues/740
[ ] Add delight to the experience when all tasks are complete :tada:


statistics: resource metering

Signed-off-by: Zhenchi<EMAIL_ADDRESS>What problem does this PR solve?
Support CPU resource metering for TiKV RPC requests.
What is changed and how it works?
What's Changed:

Support CPU time recording for requests

A request is with a ResourceMeteringTag.
During the execution of the request, its ResourceMeteringTag is attached to the current thread.
There is a global CpuRecorder running in a background thread. This CpuRecorder periodicity fetches stats of threads along with their attached tags, then it records CPU time of related requests.

Introduce a reporter to periodicity send records to some agent.
Support dynamically configuring the behavior of the recorder and the reporter.

resource-metering.enabled: Enable resource metering, for now, only CPU recorder involved. (default: false)
resource-metering.agent-address: Remote agent address (default: "")
resource-metering.report-agent-interval-seconds (default: 60)
resource-metering.max-resource-groups: Control memory usage of the reporter. (default: 200)
resource-metering.precision-seconds: Control the precision of recording. (default: 1)

Related changes

Agent protocol: https://github.com/pingcap/kvproto/pull/773

Check List
Tests

Unit test
Integration test
Manual test

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Release note

Support basic resource metering

/release

/release

/release

/test

/cc @andylokandy

/test

/test

/run-all-tests

/lgtm

/merge

/lgtm

/merge

/merge

/run-all-tests


Sonos line-in and tv source fixes + Sonos discovery fix.

Description:
Fixes:

Setting properties correctly when playing line-in or tv sources.
Sonos device discovery now correctly checks if speaker is already known.

Related issue (if applicable): fixes #153 in home-assistant-polimer

https://github.com/home-assistant/home-assistant-polymer/issues/153

**Checklist:**

If the code communicates with devices, web services, or third-party tools:
  - [x] Local tests with `tox` run successfully. **Your PR cannot be merged unless tests pass**

I'll add some unit tests tomorrow, as for the size of the update func, I completely agree, I'll do some refactoring once the other PR is in (https://github.com/home-assistant/home-assistant/pull/4172)

Are there any objections to doing the unit tests along with a refactoring PR ?

Sure, probably best to do it in a new PR in any case. 🐊


Update Spin from 1.1 to 1.2

Content must go through a pre-merge checklist.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:

[x] The title, template, and date` are all set
[x] Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
[x] File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
[x] Has passed bart check
[x] Has run npm run build-index
[x] Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
[x] Headings are using Title Case
[x] Code blocks have the programming language set to properly highlight syntax and the proper copy directive
[x] Have tested with npm run test and resolved all errors
[x] Relates to an existing (potentially outdated) blog article? If so please add URL in blog to point to this content.

Closes https://github.com/fermyon/developer/pull/627

Longer term, if we feel this needs to be in the docs, it would be great to find a way of presenting it that:

Makes it easier to review.  The current system means the entire help system output appears as inserted text; there's no sense of "what has changed" just a large mass of text to be checked, most of which has already been read over in several previous versions.
Makes it easier for readers to see what has changed across versions (though this could also be accomplished via a separate changelog).

I'm not sure what a good solution looks like though!  (And it's definitely not something we need to worry about for this PR.)


Ability to save each slide in individual MD file

It would be great if we've the ability to save each slide from pptx to individual md file
Thanks

There is an argument --page that restricts the conversion into a single slide. Do this for each slides in the pptx to achieve the same effect.
This arguments is documented in README.md now.


cancel previous runs in the PR when you push new commits

While implementing #139 I sometimes pushed several commits quickly and after that I noticed that previous run worked and the most recent run was waiting in line.
I googled some solutions and I found the answer: https://stackoverflow.com/a/72408109/4544798
github docs: https://docs.github.com/en/actions/using-jobs/using-concurrency

It seems it works: https://github.com/ovn-org/ovn/actions


Rewrite/simplify gogs serve

Serve will not leak anymore the existence of repositories when the user does not have access to them. It will however give better feedback in other cases.

Hi @phsmit , would you like to resolve the conflict?

Conflict resolved

Some critical issues, but I'll change it after PR, thanks again!

Some critical issues

False alarm.


visit-install not available in source created from visit-dist.

Describe the bug
Since visit-install was moved out of visit/src/tools/dev/scripts, it is no longer available in the source distribution created from visit-dist.
I don't think we necessarily want to add all of the visit/scripts directory to our source-distribution, so the visit-install script should either be moved back to its original location, or visit-dist script should be updated to pull in files in the visit/scripts directory which are necessary for building/installing VisIt.
I ran across this trying to build and test latest 3.4RC in a container.

Cyrus asked me to pick my favorite scripts and move them somewhere they would be easier to find. We can move things back but I have continued making changes like in #19843 that make that harder to do. I think it'd be better to have visit-dist grab the scripts it really wants from the scripts folder.

src/tools/dev/scripts/source_files is the script that needs to be modified to grab the needed files.

Let's have it grab all of these:

I'm already testing it as I need this fixed for container builds.


bug: pickImages() throws Cannot load representation of type public.image

Plugin version:

0.5.9
Platform(s):

iOS
Current behavior:

Using pickImages(), once the images are selected and "Add" is clicked, the following error is thrown, and no { files } are populated.
2023-01-25 13:43:02.712489-0700 App[50423:12554644] Error copying file type public.image. Error: Error Domain=NSItemProviderErrorDomain Code=-1000 "Cannot load representation of type public.image" UserInfo={NSLocalizedDescription=Cannot load representation of type public.image, NSUnderlyingError=0x600003f9d7a0 {Error Domain=NSCocoaErrorDomain Code=4101 "Couldn’t communicate with a helper application."
Steps to reproduce:

Create new React Ionic application
Wire up pickImages() to a button
Tap button, select images, tap "Add"

Related code:

  const [files, setFiles] = useState<PickedFile[]>([])

  const pickImages = async () => {
    const result = await FilePicker.pickImages({
      multiple: true,
    })
    setFiles(result.files)
  }

Other information:

I've tested this using iOS Simulator using iOS 14.5, 15.5, and 16.2.
However, this does work on a physical device with iOS 15.5.
I can upload the sample project I'm working with if that'd be helpful.
Capacitor doctor:

💊   Capacitor Doctor  💊

Latest Dependencies:

  @capacitor/cli: 4.6.2
  @capacitor/core: 4.6.2
  @capacitor/android: 4.6.2
  @capacitor/ios: 4.6.2

Installed Dependencies:

  @capacitor/cli: 4.6.2
  @capacitor/core: 4.6.2
  @capacitor/android: 4.6.2
  @capacitor/ios: 4.6.2

[success] iOS looking great! 👌
[success] Android looking great! 👌

Thank you for the detailed issue!
So the issue does only occur in iOS simulator?

I randomly had a thought, and here's a fun series of steps to take:

Create a new iOS Simulator instance
Select some of the pre-provided images using pickImages()
Verify the error I posted originally is thrown
Download/Save a few images (via Add to Photos) to the Photo Library
Repeat Step 2 instead selecting images from Step 4
Verify result.files success
Repeat Step 2 using the pre-provided images
Verify result.files success

I'm not sure what's going on, but maybe this is a learning on how the iOS Simulator pre-populated images work? Super strange and not what I expected. Using the @capacitor/camera plugin to select an image has always worked, so I assumed the same behavior would happen.
I'll leave it up to you if you'd like to keep this open or close it, but the workaround seems to work.

Thank you! I will have a look.

I'm going to close this. Turns out, it's a known issue in the simulator with the pink flower image: https://developer.apple.com/forums/thread/699155


Support custom Docker registry when building the Docker images

Description of your changes
I would like to run a custom build of the AWS provider and for this I would like to upload the built Docker images to my own Docker registry.
The current setup has the following limitations:

the value of DOCKER_REGISTRY can not be overridden when running make targets - this is just an inconvenience as it's easy to tag the built images
the Docker image name for the controller is baked in as crossplane/provider-aws-controller:VERSION - this is again a minor inconvenience because you can override the image using the ControllerConfig CRD.

Still it's more convenient if I can do a full build, upload both images and I only have to update the spec.package on the Provider object.
For reference I was running the following commands:
PLATFORMS=linux_amd64 DOCKER_REGISTRY=quay.io/acme VERSION=v0.16.0-p1 make build publish

docker tag quay.io/acme/provider-aws-amd64:v0.16.0-p1 quay.io/acme/provider-aws:v0.16.0-p1
docker push quay.io/acme/provider-aws:v0.16.0-p1
docker tag quay.io/acme/provider-aws-controller-amd64:v0.16.0-p1 quay.io/acme/provider-aws-controller:v0.16.0-p1
docker push quay.io/acme/provider-aws-controller:v0.16.0-p1

I have:

[X] Read and followed Crossplane's [contribution process].
[X] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
I deployed my own images and verified that the provider works.
Also I've ran the make targets without setting DOCKER_REGISTRY and verified that it uses "crossplane" correctly everywere.

I'd certainly like to keep our makefiles as consistent as possible, even if it's as simple as manually replicating these changes in our various other repos.

@hasheddan @negz  I won't be able to do this for the other providers in the near future, sorry.

@hasheddan @negz  I won't be able to do this for the other providers in the near future, sorry.


[Bug]: Any file parse will stuck at 50%

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
1de31ca
Other environment information
No response
Actual behavior
Any file parsing, the information shows that it has been completed, but the status is stuck at 50%

I have checked the task table.
When I upload only one file, it will insert two tasks into the task table.
I can't get it out.
Is there any wrong or some work I should do to get it over?
Expected behavior
No response
Steps to reproduce
1.Build from source
2.Debug task_executor.py
3.Debug rag_server.py
4.cd web
5.npm run dev
6.Open http://localhost:9222
7.Create a knowledge
8.Upload any file

Additional information
No response

There must be problem with data insertion of ES.

I have re-installed ES locally, the problem was solved.
But I don't know why.
The ES was installed by Docker before , I hadn't change anything, just update ragflow from 0.5 to 0.7, and the problem  occurred.
This is my hardware info, no GPU,

cpu family	: 6
model		: 154
model name	: 12th Gen Intel(R) Core(TM) i5-1240P
stepping	: 3
microcode	: 0x430
cpu MHz		: 400.000
cache size	: 12288 KB
Could you please tell me the reason ? And how to avoid this happen again ?

Got no clue!


when multi request listeners added, request.continue() works in a confusing way

following code shows my question:
import {launch, Request} from "puppeteer";

(async () => {
    const browser = await launch({
        headless: false,
        devtools: true
    });
    const page = await browser.newPage();
    await page.setViewport({width: 1920, height: 1080});
    await page.setRequestInterception(true);
    page.on("request", async (req: Request) => {
        await req.continue();
    });
    page.on("request", async (req: Request) => {
        await req.respond({
            status: 200,
            body: "test"
        });
    });
    await page.goto("https://www.baidu.com/");
    console.log();
})();

req.respond won't work in the second request listener and just throw an error.
If multi request listeners added, how to decide whether request.continue should be called is confusing.
In my way, I solve it as following
import {launch, Request} from "puppeteer";

(async () => {
    const browser = await launch({
        headless: false,
        devtools: true
    });
    const page = await browser.newPage();
    await page.setViewport({width: 1920, height: 1080});
    await page.setRequestInterception(true);

    page.on("request", (req: Request) => {
        const oldContinue = req.continue;
        let continueNum = 0;
        // override request.continue
        req.continue = (override?: any) => {
            if (override) {
                return oldContinue.call(req, override);
            }
            else {
                continueNum++;
                if (continueNum == page.listeners("request").length) {
                    return oldContinue.call(req);
                }
            }
        };
        return req.continue();
    });

    page.on("request", async (req: Request) => {
        await req.continue();
    });
    page.on("request", async (req: Request) => {
        await req.respond({
            status: 200,
            body: "test"
        });
    });
    await page.goto("https://www.baidu.com/");
    console.log();
})();

Is there a more elegant way to solve it?

@xiyuan-fengyu in general, you should have only one place in code where you decide on request handling. Why do have multiple request event handlers?

In my crawler framework，I need to supply some method to help user to disable image load, or proxy request for each page, or record request, and so on, all those need request interception.
PuppeteerUtil.setImgLoad PuppeteerUtil.useProxy
NetworkTracing

@xiyuan-fengyu I see. Every request should be handled exactly once. This is not an artificial constraint: we cannot simultaneously "continue" request and "abort" it.

If multi request listeners added, how to decide whether request.continue should be called is confusing.

 A good rule of a thumb is to have only one "request" listener that carries all the logic to decide request's fate.
Hope this helps.


[Drawer] Add touchAction: 'none' on the Overlay to disable scrolling

Added touchAction: 'none' to css to alleviate a console warning regarding canceling an event when dragging a Drawer.
Closes #12094

@jlascoleassi It's a great first pull request on Material-UI 👌🏻. Thank you for giving it a shot!


Change the icon of the deadname remover

Hi! i am a user in this extension and is not a issue but a request, it will be great to have a option to change the flag to a base color, i think it would be more discrete for the persons who share pcs with another people. Thanks for reading and i hope is implemented

Hey @Mango-mangoes ! I think this is a great idea, even though I'm not an official developer, I'll see if I can work on it in a fork


Fix MOVSXD encoding for exception filter

We were incorrectly reading the opcode for MOVSXD causing the AV in virtual memory to escape instead of throwing a WebAssembly runtime exception.
Since the AV occurs in the 8GB array, it is not a security concern.

This change is

@dotnet-bot test
Windows ci_disablejit_x64_debug


Design or code example of using custom loop iterator

There's a placeholder argument for ioloop

-- @tparam[opt] function args.sleep_function	custom sleep function to call after each iteration
but arguments are not used anywhere and there's no direct access to this setting

My case is to connect 2 streams of operations for back and fourth messaging (between KNX bus and MQTT), so I need simultaneously read messages from both local bus and MQTT. My first assumption was that sleep function might be best place to put my bus loop.
Here's an example of bus read loop:
function groupcallback(event)
    if event.dst == '1/1/1' then
        local value = knxdatatype.decode(event.datahex, dt.uint16)
        submit_to_mqtt(value)
    end
end

lb = require('localbus').new(0.5) -- timeout is 0.5 seconds
lb:sethandler('groupwrite', groupcallback)

while true do
    lb:step()
    do_some_other_stuff()
end

What is the best way to implement this type of messaging loop?

I actually used code of run_ioloop() function directly to achieve desired result, but would be good to see better design of manual "stepping" through the iterations, thanks!

@dmitryuv , if if I understand you correctly, you intend to use ioloop builtin into the luamqtt.
In this case, you may try this way.
There is a https://github.com/xHasKx/luamqtt/blob/master/mqtt/ioloop.lua module (require("mqtt.ioloop"))
This module .get() method will return you an instance of ioloop_mt which has a methods :add(client) and :run_until_clients().
So you may create an object with methods :set_ioloop(self) and :_ioloop_iteration() (through metatable or its own).
Then use :add(it) method of the ioloop.
Then ioloop will call it:_ioloop_iteration() over and over in its :run_until_clients() method the same way it process all MQTT clients in the luamqtt.
Please try this way and if it will help - I'll think how to export functions to simplify the described workflow.

Thanks for getting back on this,
If I understand you correctly you propose to create "fake" mqtt client with my own loop implementation. Might sound like a solution, but it washes out meaning of the existing class (mqtt client), unless there's an additional abstraction on top of it.
The other option i've implemented right now is plugging in my own step into the loop, but i had to extract portion of the code from the loop function:
-- part of the setup
local lb = require('localbus').new(0.005)
lb:sethandler('groupwrite', knx_cb)

-- main loop
function run_loop(client, bus)
  print("running ioloop for it")

  local loop = mqtt.get_ioloop()

  loop:add(client)
  loop.running = true   -- not sure why i need this? part of the original loop
  while next(loop.clients) do
    loop:iteration()
    bus:step()  -- KNX bus iteration
  end
  loop.running = false
  print("done, ioloop is stopped")
end

Probably my concern is that i had to extract part of the library's code instead of plugging in my custom step function. My original first thought that the easiest solution to address this is supplying user's callback that will be called from within the loop, but it's less flexible than your proposal.

The Lua has no interfaces/classes in its core like in Java or C#, so masquerading some object as mqtt client is not a "forbidden black magic" thing. It's more like a duck-typing concept in Python.
But inserting a function to the mqtt client lists in ioloop might be a good idea. A function is a first-class value in Lua, so we can easily distinguishing it from usual mqtt clients during ioloop iteration.
Consider this example:
local bus = ...

local loop = mqtt.get_ioloop()
loop:add(function() bus:step()  --[[ KNX bus iteration ]] end)
-- ...

loop:run_until_clients()

What do you think?

Thanks, that sounds like a good plan. One more thought – since you have mqtt.run_ioloop(..) as an "official" entry point, could it be simplified to something like
mqtt.run_ioloop( client1, function() --[[ custom loop ]] end)
overwise there will be duplication of library parts, also i'm not sure how important are the additional steps in the pre-step, i mean line cl:start_connecting() in the run_ioloop() code

@dmitryuv , check the new version v3.2.0 and example in a test https://github.com/xHasKx/luamqtt/blob/master/tests/spec/ioloop.lua

@xHasKx looks great to me, thanks!

@xHasKx please clarify how to use with copas standard loop?
I attempted twice:
  copas.addthread(function()
    while true do
      client:_ioloop_iteration() -- [./mqtt/client.lua:898](https://github.com/xHasKx/luamqtt/blob/master/mqtt/client.lua#L898): bad argument #1 to 'coroutine_resume' (thread expected, got nil)
    end
  end)

  client:start_connecting()
  copas.addthread(function()
    while true do
      client:_io_iteration(client.connection.recv_func) -- [./mqtt/luasocket.lua:34](https://github.com/xHasKx/luamqtt/blob/master/mqtt/luasocket.lua#L34): bad argument #1 to 'receive' (string expected, got table)
    end
  end)

TIA

  local ioloop = require("mqtt.ioloop").get(true, { timeout = 0.001 })
  copas.addthread(function()
    client.ioloop = ioloop
    while true do
      client:_ioloop_iteration()
      copas.sleep(ioloop.timeout)
    end
  end)

This works but shows CPU busy loop.

@dvv, I've added an example: https://github.com/xHasKx/luamqtt/blob/master/examples/copas-example.lua
The main thing is to use a new copas thread for each ioloop and mqtt client you plan to use

@xHasKx Great, thanks!
However it still eats 6-10% of CPU in timeout busy loop.

@dvv, try to play with ioloop creation params - set sleep=0.01 and maybe add timeout=0.1

Actually, luamqtt's internal ioloop can be designed better (for example, with socket.select).
I'm sure there is a way to improve luamqtt behavior when it runs inside copas loop

@xHasKx I sent a pull request with the idea.
Please validate and consider applying.
Running under copas allows for many benefits, imho.

@xHasKx I sent a pull request with the idea.
Please validate and consider applying.
Running under copas allows for many benefits, imho.

Thanks, I'll check


Is there a more comprehensive document?

Some pages in the wiki are missing, like Breeze Signal Processing (only a cheatsheet available). And some important packages like stat are only shown in the quick start.

I also can't find any detailed documents like API doc about stats contents. There should be one whole page for stats.

Looks like a dead project now :(

Sorry, yeah... I'm pretty burned out on this project. I don't use Breeze or even Scala on a regular basis any more, and I don't have a ton of energy/enthusiasm for more than basic maintenance.
I'm happy to help people do something here, I just don't have a ton of energy to take things on myself. Re: signal processing in particular, I didn't really write that part of Breeze and know embarrassingly little about signal processing.


add instructions for new mount path

sorry for the delay in responding. i added the ssh line and found some errors with the password section.
where is the subpage for sshfs?

afaik there isn't one, as i just ran
ag sshfs
from my docs folder and it came up blank
my suggestion is to split some of this into subpages. i believe any sshfs info is buried in the forum.

see #340


Support for getting active page index

Hello! This project looks awesome, but I'm looking to synchronize another react component (a steps component) with the active carousel page index. I see it's already within the carousel state; is there a simple way the API could be extended to allow subscribing to it? I'm not sure if it would work but perhaps something like:
export const useActivePageIndex = () => {
    const { carouselState } = useCarouselContext();
    return carouselState.activePageIndex;
}

Note: Right now I can't directly do this because useCarouselContext is not exposed.

I actually ran into this issue just the other day, too. I was thinking of adding a prop that would allow you to listen to the page index changing:
export const App = () => {
  const [pageIndex, setPageIndex] = useState()

  return (
    <div>
      <Carousel
        onActivePageIndexChange={(index) => {
          setPageIndex(index)
        }}
      />
      {pageIndex}
    </div>
  )
}

Out of curiosity, would you ever need to initialize the carousel with a different active page than the first one?

I was planning to just wrap the other controllable visual indicators in <CarouselItem> so in my case I wouldn't need it to be controlled. And similarly I wouldn't need to initialized it with a different page.


ci: add local testing of modified benchmarks

This PR sets out an initial ci system to locally test modified benchmarks.

@alecbcs @pearce8 Initial site CI ready for review. This runs saxpy on dane and tioga.


[CLOSES #285][CLOSES #286]

It is now possible to use insertRow/insertColumn on empty matrices.
It is now possible to use insertRow/insertColumn to add row/column at the end of matrices.

Any more remarks?

LGTM! Thanks @csavelief!


WIP: DBZ-379 Postgres connector minimizes use of JDBC metadata

https://issues.jboss.org/browse/DBZ-379
This is a request for preliminary preview
requires

https://github.com/debezium/postgres-decoderbufs/pull/10
https://github.com/debezium/postgres-decoderbufs/pull/11

and it is expected to be modified after https://github.com/debezium/debezium/pull/347 is merged
Two things need to be modified yet

PgOid handling is incosistent and can trigger wals schema refresh (albeit with the correct result)
tableFromFromMessage - a switch statement that reconciles differences between decoder types and JDBC types will be extracetd elsewhere

I think most of the WIP is completed - the only work left is integration with https://github.com/debezium/debezium/pull/347

@jpechane, #347 is applied and modified a bit. Can you rebase this PR to the latest master?

@gunnarmorling Rebased, still working on wal2json part

    assertRecordSchemaAndValues(
            Collections.singletonList(new SchemaAndValueField("modtype", SchemaBuilder.OPTIONAL_INT32_SCHEMA, 1)), updatedRecord, Envelope.FieldName.AFTER);

wal2json works for the latest plug-in but is not yet backward compatible with older Amazon one

Superseded by https://github.com/debezium/debezium/pull/376.