Buffer size in task ClassificationError is hardcoded

Find how to adjust buffer size dynamically. Will be probably useful for a lot of tasks.

Buffer size in task ?

Sometimes a Task/View needs to loop through the dataset. However, with big model/dataset it is not possible to parse the whole dataset at once, so it would require some kind of batch processing.

These kind of tasks should take a batch_size in argument.


Issues/2171

Resolving issue with Timespans not being correctly parsed by AddProducer.Configure()
#2171

@phatboyg yeah, I believe it was my miss as well
@Excommunicated could you rebase into single commit? and @phatboyg will merge it ;)

Rebased to a single commit, and merged.


SLING-6110: use the proper bundleContext in the ServerSideTeleporter …

…to retrieve the correct bundle headers

With the upcoming migration to git this repository will be deleted. If the pull request contains data that should be re-submitted I suggest that you save the changes locally and resubmit them after the migration, which will likely happen on Monday the 9th of October.


[RFE] Add Unit Tests to RoleTemplate Controller Code

Is your feature request related to a problem? Please describe.
Currently the RoleTemplate handler does not have comprehensive unit tests. This leaves the code vulnerable to regressions and hard to modify.
Describe the solution you'd like
Add unit test coverage to the following files:

https://github.com/rancher/rancher/blob/release/v2.9/pkg/controllers/management/auth/role_template_lifecycle.go

At assignee's discretion:

Adding comments to any functions that are currently undocumented or under-documented.
Minor refactors to make code more testable.

If any bugs are found, or the assignee believes major refactoring is necessary, create a new GitHub issue to track the work. This issue is not for potential functionality changes.
Additional context
Related RoleTemplate Issues:

https://github.com/rancher/rancher/issues/44692
https://github.com/rancher/rancher/issues/44691

This will be covered in this work: https://github.com/rancher/rancher/issues/46077


Bug: Voice is reading chunks with blanks

Right now, the Voice software is reading chunks containing blanks (four underscores in a row), which is leading to some really weird interactions. We want to omit chunks containing blanks from being read out loud.

I believe this was fixed when we switched to MS for TTS.


Reduce full pushes for WDS

While WDS was designed to be very incremental in nature, there are still situations where we do full pushes. These are expensive for the control plane and data plane, and unnecessary.
Unlike the rest of Istiod, WDS has "perfect" incremental diffing. We know, with certainty, if the config should change we will get a change event, if and if there is no event there is no change. We do not ever need to do "recompute the world" like we do in Envoy xDS.
There are 3 areas that trigger full pushes today
1: ConfigsUpdated elision
Istiod tracks which configs changed in the ConfigsUpdated field of PushRequest. However, if there is any request with this unset, it is treated as "push everything". For example, https://github.com/istio/istio/blob/52e0d5cbf272e95c9999bb0d10d9f8cf6acb5167/pilot/pkg/serviceregistry/kube/controller/controller.go#L423.
As mentioned above, we never need to recompute the world for WDS. However, because these requests wipe out ConfigsUpdated, we lose the diffs, and have no choice but to do so in the WDS XDS generator.
To fix these, we need to make sure we never wipe out Address changes. Likely this would be some new field in PushRequest to store these changes, or possibly a different path for these types of changes.
2: Client reconnects
When a client reconnects, we push down the full state again. The XDS protocol has a mechanism to avoid this - InitialResourceVersions. This tells us all the resources a client already has, as well as their versions.
Note we have a max 30min connection age, so today this means we get a full push every 30 min per client.
We use this today only to prune removed resources; we do not use the version at all.
If we did have a version, we could detect which resources are unchanged and skip sending them. In a typical environment, this is going to be ~99% of the resources, since we reconnect immediately typically.
The solution here is obvious: assign resources a version and diff it to skip updates.
However, its tricky to assign a version. We need it to be consistent across replicas of Istiod.
The best option here is to make the version computed from the contents. We can do this by hashing the result.
Any hash has the possibility of a collision. If we use sha256 this is virtually impossible, with a 64bit hash its improbably but possible (https://lemire.me/blog/2019/12/12/are-64-bit-random-identifiers-free-from-collision/) at the scales we are working on. If we have a hash collision, the impact is we fail to push a new configuration.
A few things that make collisions less scary...

We have the same 'issue' with XDS cache today -- a collision can cause the cache key to not update. This hasn't caused any problemns
The birthday paradox doesn't apply. We only care about collisions within a single resource. So that would imply the same resource (by key) changes and the hash key changes. The birthday paradox, and almost all hash collision math, is about avoiding collisions between any objects.
The only issue with a collision is if the following sequence occurs: start with res1 with hash1. Client disconnects. res1 changed, but hash collision re-hashes to hash1. Client reconnects.

For a 64bit key there is a 1/2**64 chance two subsequent objects hash to the same key. This needs to occur during the few seconds a client is reconnecting. I think this is implausible to be an issue.
3: client initial connections
Unlike a reconnect, a clients' first connection legitimately needs the entire state. The problem is this gets piped down into a single proto, which can be quite large. Kubernetes had this same issue (more or less) and solved this via steaming the initial set https://kubernetes.io/blog/2024/12/17/kube-apiserver-api-streaming/ instead of sending it in a single list.
The xDS protocol doesn't allow us to split messages, however. While we could do it for updates, if we do it for the initial push we lose the ability to know when we have received all the initial config. I am sure we could slap something on that, but probably not a good idea.
However, gRPC has a new interface that allows us to encode a message as a [][]byte instead of a []byte. We will (soon) have pre-marshalled WDS messages (as []byte). What we could do is zero-copy those into the [][]byte response. While this will look the same on the wire, it will avoid allocating a large buffer per-client

Some benchmarks for various things here..
hashing a workload (by the []byte marshalled repr):
BenchmarkWorkloadHash
BenchmarkWorkloadHash/sha256
BenchmarkWorkloadHash/sha256-16                 10832592               105.5 ns/op           288 B/op          1 allocs/op
BenchmarkWorkloadHash/sha3
BenchmarkWorkloadHash/sha3-16                    3348417               359.4 ns/op           288 B/op          1 allocs/op
BenchmarkWorkloadHash/xx
BenchmarkWorkloadHash/xx-16                     51954706                22.08 ns/op            0 B/op          0 allocs/op

Equals impl (neq == not equal, other one is two equal objs):
BenchmarkWorkloadEquals
BenchmarkWorkloadEquals/old
BenchmarkWorkloadEquals/old-16          32625531                35.36 ns/op            0 B/op          0 allocs/op
BenchmarkWorkloadEquals/bytes
BenchmarkWorkloadEquals/bytes-16<PHONE_NUMBER>               0.2184 ns/op          0 B/op          0 allocs/op
BenchmarkWorkloadEquals/vt-equals
BenchmarkWorkloadEquals/vt-equals-16    34311696                33.33 ns/op            0 B/op          0 allocs/op
BenchmarkWorkloadEquals/vt-marshal-bytes
BenchmarkWorkloadEquals/vt-marshal-bytes-16              3961648               318.2 ns/op           320 B/op          4 allocs/op
BenchmarkWorkloadEquals/golang-marshal-bytes
BenchmarkWorkloadEquals/golang-marshal-bytes-16          1308820              1014 ns/op             400 B/op          8 allocs/op
BenchmarkWorkloadEquals/old-neq
BenchmarkWorkloadEquals/old-neq-16                       1467146               794.6 ns/op           144 B/op          4 allocs/op
BenchmarkWorkloadEquals/bytes-neq
BenchmarkWorkloadEquals/bytes-neq-16<PHONE_NUMBER>               0.2136 ns/op          0 B/op          0 allocs/op
BenchmarkWorkloadEquals/vt-equals-neq
BenchmarkWorkloadEquals/vt-equals-neq-16                78389262                16.25 ns/op            0 B/op          0 allocs/op
BenchmarkWorkloadEquals/vt-marshal-bytes-neq
BenchmarkWorkloadEquals/vt-marshal-bytes-neq-16          1294942               869.7 ns/op           416 B/op          8 allocs/op
BenchmarkWorkloadEquals/golang-marshal-bytes-neq
BenchmarkWorkloadEquals/golang-marshal-bytes-neq-16      1341309               959.5 ns/op           416 B/op          8 allocs/op

func BenchmarkWorkloadEquals(b *testing.B) {
	wl := model.WorkloadInfo{
		Workload: &workloadapi.Workload{
			Uid:               "x/networking.istio.io/WorkloadEntry/ns/name1",
			Name:              "name1",
			Namespace:         testNS,
			Addresses:         [][]byte{parseIP("<IP_ADDRESS>")},
			Node:              "",
			Network:           testNW,
			CanonicalName:     "a",
			CanonicalRevision: "latest",
			ServiceAccount:    "sa1",
			WorkloadType:      workloadapi.WorkloadType_POD,
			WorkloadName:      "name1",
			Services: map[string]*workloadapi.PortList{
				"ns1/se.istio.io": {
					Ports: []*workloadapi.Port{
						{
							ServicePort: 80,
							TargetPort:  8080,
						},
					},
				},
			},
			ClusterId: testC,
		},
		Labels: map[string]string{"app": "foo"},
	}
	wlEq := model.WorkloadInfo{
		Workload: protomarshal.Clone(wl.Workload),
		Labels:   maps.Clone(wl.Labels),
	}
	marshalled := protoconv.MessageToAny(wl)
	wl2 := model.WorkloadInfo{
		Workload: &workloadapi.Workload{
			Uid:               "x/networking.istio.io/WorkloadEntry/ns/name1",
			Name:              "name1",
			Namespace:         testNS,
			Addresses:         [][]byte{parseIP("<IP_ADDRESS>")},
			Node:              "",
			Network:           testNW,
			CanonicalName:     "a",
			CanonicalRevision: "latest",
			ServiceAccount:    "sa1",
			WorkloadType:      workloadapi.WorkloadType_POD,
			WorkloadName:      "name1-changed",
			Services: map[string]*workloadapi.PortList{
				"ns1/se.istio.io": {
					Ports: []*workloadapi.Port{
						{
							ServicePort: 80,
							TargetPort:  8080,
						},
					},
				},
			},
			ClusterId: testC,
		},
		Labels: map[string]string{"app": "foo"},
	}
	marshalled2 := protoconv.MessageToAny(wl2)
	b.Run("old", func(b *testing.B) {
		for range b.N {
			wl.Equals(wlEq)
		}
	})
	b.Run("bytes", func(b *testing.B) {
		for range b.N {
			bytes.Equal(marshalled.Value, marshalled.Value)
		}
	})
	b.Run("vt-equals", func(b *testing.B) {
		for range b.N {
			wl.EqualsVt(wlEq)
		}
	})
	b.Run("vt-marshal-bytes", func(b *testing.B) {
		for range b.N {
			marshalled := protoconv.MessageToAny(wl)
			bytes.Equal(marshalled.Value, marshalled.Value)
		}
	})
	b.Run("golang-marshal-bytes", func(b *testing.B) {
		test.SetForTest(b, &features.EnableVtprotobuf, false)
		for range b.N {
			marshalled := protoconv.MessageToAny(wl)
			bytes.Equal(marshalled.Value, marshalled.Value)
		}
	})
	b.Run("old-neq", func(b *testing.B) {
		for range b.N {
			wl.Equals(wl2)
		}
	})
	b.Run("bytes-neq", func(b *testing.B) {
		for range b.N {
			bytes.Equal(marshalled.Value, marshalled2.Value)
		}
	})
	b.Run("vt-equals-neq", func(b *testing.B) {
		for range b.N {
			wl.EqualsVt(wl2)
		}
	})
	b.Run("vt-marshal-bytes-neq", func(b *testing.B) {
		for range b.N {
			marshalled2 := protoconv.MessageToAny(wl2)
			bytes.Equal(marshalled.Value, marshalled2.Value)
		}
	})
	b.Run("golang-marshal-bytes-neq", func(b *testing.B) {
		test.SetForTest(b, &features.EnableVtprotobuf, false)
		for range b.N {
			marshalled2 := protoconv.MessageToAny(wl2)
			bytes.Equal(marshalled.Value, marshalled2.Value)
		}
	})
}

func BenchmarkWorkloadHash(b *testing.B) {
	wl := model.WorkloadInfo{
		Workload: &workloadapi.Workload{
			Uid:               "x/networking.istio.io/WorkloadEntry/ns/name1",
			Name:              "name1",
			Namespace:         testNS,
			Addresses:         [][]byte{parseIP("<IP_ADDRESS>")},
			Node:              "",
			Network:           testNW,
			CanonicalName:     "a",
			CanonicalRevision: "latest",
			ServiceAccount:    "sa1",
			WorkloadType:      workloadapi.WorkloadType_POD,
			WorkloadName:      "name1",
			Services: map[string]*workloadapi.PortList{
				"ns1/se.istio.io": {
					Ports: []*workloadapi.Port{
						{
							ServicePort: 80,
							TargetPort:  8080,
						},
					},
				},
			},
			ClusterId: testC,
		},
		Labels: map[string]string{"app": "foo"},
	}
	marshalled := protoconv.MessageToAny(wl)
	b.Run("sha256", func(b *testing.B) {
		for range b.N {
			h := sha256.New()
			_ = h.Sum(marshalled.Value)
		}
	})
	b.Run("sha3", func(b *testing.B) {
		for range b.N {
			h := sha3.New256()
			_ = h.Sum(marshalled.Value)
		}
	})
	b.Run("xx", func(b *testing.B) {
		for range b.N {
			h := xxhash.New()
			h.Write(marshalled.Value)
			_ = h.Sum64()
		}
	})
}

Using gRPC encoding for discovery response, 100 messages:
BenchmarkEncoding
BenchmarkEncoding/vt
BenchmarkEncoding/vt-16           154177             10195 ns/op           32949 B/op          5 allocs/op
BenchmarkEncoding/legacy
BenchmarkEncoding/legacy-16                39722             34207 ns/op           32946 B/op          5 allocs/op


Strong mode analyzer incorrectly infers return type of ??=

The following code should be strong-mode compliant:
class X {}

UnmodifiableListView<X> a = new UnmodifiableListView<X>([]);
Iterable<X> b = null;
Iterable<X> c = (b ??= a);

but the analyzer actually produces the error:
#Unsound implicit cast from Object to Iterable<X> [STRONG_MODE_DOWN_CAST_COMPOSITE]
Note that this very similar (and functionally equivalent) code works fine:
class X {}

List<X> a = new UnmodifiableListView<X>([]);
Iterable<X> b = null;
Iterable<X> c = (b ??= a);

so it seems it's specifically having trouble working out the common subtype of Iterable and UnmodifiableListView. Maybe mix-in related?

I believe that this is an instance of this:
https://github.com/dart-lang/sdk/issues/25821
We are currently using the spec mode LUB, which is not very useful:

For discussion of spec mode LUB see:
https://github.com/dart-lang/sdk/issues/19282
https://github.com/dart-lang/sdk/issues/19425

Closing as duplicate of #25821 and https://github.com/dart-lang/sdk/issues/25802 , please re-open if you think something else is going on.


Create release

It could be wonderful to create a release/tag for this project

+1

👍  We recommend this bundle in LexikJWTAuthenticationBundle, it would be quite better to have a stable version.

👍  We recommend this bundle in LexikJWTAuthenticationBundle, it would be quite better to have a stable version.

Ping @jshedde: can you create a release, please?

I have created a v0.1.0.
Is it good for you ?

Thank you @jshedde


Buttons should always have an attribute type with the value button.

This prevents submitting a form that contains a UI Select.

Any news on this? We currently have to manaully patch UI Select, which is rather annoying.

+1

+1

+1

Fixed with 1e25650d78242abfe54bfd1c50d4997485729b8c
Sorry, I had missed #503.


Use requestAnimationFrame

Putting functions as the scroll handler/resize handler blocks scrolling while they execute, so it's preferable to use requestAnimationFrame for the handlers.

I'm planning on making a PR at some point if nobody else gets to it first. =)

Feel free to implement it, I'll check at the weekend

It would be great if you will split PR by issue. I guess that raf doesn't related with single scroll listener. Btw you can use https://www.npmjs.com/package/raf as polyfill

Yeah, I just realized that I thought the part of the project that handled scroll handlers kind of belonged in a separate file, and I figured "if a separate file, why not a separate project"? Of course, by splitting it into a different project, I lost the ability to add them in piecewise. I think you'll find this approach actually produced more maintainable code; there are only 3 new lines to this repository aside from testing.
As for raf, I wanted to make the library I used have 0 dependencies. raf as a project spends more than half of its time concerned with cancelling requestAnimationFrame calls, which is not something this project or manage-scroll-handlers is concerned with. The only drawback to baking my own into the index file of manage-scroll-handlers is that it currently does not support vendor extensions. However, according to caniuse.com, no browsers currently support  vendor extensions but not requestAnimationFrame, so almost all of raf is unnecessary for the project. I effectively reduced it to requestAnimationFrame || (fn => setTimeout(fn, 30)), which accomplishes the goal of making the callback non-blocking and in much fewer bytes. (one of my goals in the new project is to keep it under 2kb when minified)


Panic - Attempt to subtract with overflow

at https://github.com/rust-lang/cargo/blob/master/src/cargo/core/resolver/mod.rs#L453
Running in release mode this just spins in a loop forever, since it doesn't panic on the arithmetic.
The issue arrises when I attempt to depend upon both blake2 and postgres.
update 11:58
Both crates depend on different versions of generic array and typenum, and it seems to break when trying to resolve the dependencies.
Running the latest nightly as of Sep 1 2017.
 ../../cargo/target/debug/cargo --version
cargo 0.23.0

cargo stack trace
rick@ubantoo:~/Projects/userhub$ RUST_BACKTRACE=1 ../../cargo/target/debug/cargo update
    Updating registry `https://github.com/rust-lang/crates.io-index`
    Updating git repository `https://github.com/pingcap/rust-prometheus`
    Updating git repository `https://github.com/QuiverMedia/rumqtt`
    Updating git repository `https://github.com/AlexPikalov/cdrs`
thread 'main' panicked at 'attempt to subtract with overflow', src/cargo/core/resolver/mod.rs:453:9
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:381
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:397
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:611
   5: std::panicking::begin_panic
             at /checkout/src/libstd/panicking.rs:572
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:522
   7: rust_begin_unwind
             at /checkout/src/libstd/panicking.rs:498
   8: core::panicking::panic_fmt
             at /checkout/src/libcore/panicking.rs:71
   9: core::panicking::panic
             at /checkout/src/libcore/panicking.rs:51
  10: <cargo::core::resolver::RcVecIter<T>>::cur_index
             at src/cargo/core/resolver/mod.rs:453
  11: cargo::core::resolver::find_candidate
             at src/cargo/core/resolver/mod.rs:716
  12: cargo::core::resolver::activate_deps_loop
             at src/cargo/core/resolver/mod.rs:655
  13: cargo::core::resolver::resolve
             at src/cargo/core/resolver/mod.rs:355
  14: cargo::ops::resolve::resolve_with_previous
             at src/cargo/ops/resolve.rs:265
  15: cargo::ops::cargo_generate_lockfile::update_lockfile
             at src/cargo/ops/cargo_generate_lockfile.rs:77
  16: cargo::update::execute
             at src/bin/update.rs:81
  17: cargo::call_main_without_stdin
             at /home/rick/Projects/cargo/src/cargo/lib.rs:128
  18: cargo::try_execute_builtin_command
             at src/bin/cargo.rs:264
  19: cargo::execute
             at src/bin/cargo.rs:228
  20: cargo::call_main_without_stdin
             at /home/rick/Projects/cargo/src/cargo/lib.rs:128
  21: cargo::main::{{closure}}
             at src/bin/cargo.rs:95
  22: cargo::main
             at src/bin/cargo.rs:86
  23: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:99
  24: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:459
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/rt.rs:61
  25: main
  26: __libc_start_main
  27: _start

Cargo.toml
[dependencies]
blake2 = "^0.6"
chan = "^0.1"
clap = "2.26.0"
config = "0.7.0"
nix = "0.8.1"
num_cpus = "1.6.2"
quick-error = "1.2.0"
r2d2 = "0.7.2"
serde = "1.0.9"
serde_derive = "1.0.9"
slog = "2.0.9"
slog-json = "2.0.2"
threadpool = "^1.4"
time = "^0.1"
toml = "0.4"
chrono = "0.4"

[dependencies.cdrs]
git = "https://github.com/AlexPikalov/cdrs"
optional = true
rev = "1577cf7"

[dependencies.mqtt-protocol]
optional = true
version = "0.3"

[dependencies.prometheus]
git = "https://github.com/pingcap/rust-prometheus"
rev = "e4d7878"

[dependencies.proto]
path = "proto-rust"

[dependencies.protobuf]
optional = true
version = "^1.4"

[dependencies.r2d2_postgres]
optional = true
version = "0.13"

[dependencies.rumqtt]
optional = true
git = "https://github.com/QuiverMedia/rumqtt"

[dependencies.uuid]
features = ["v1"]
version = "^0.5.1"

[features]
cassandra = ["cdrs"]
default = [
    "cassandra",
    "postgres",
    "mqtt",
]
postgres = ["r2d2_postgres"]
mqtt = [
    "rumqtt",
    "mqtt-protocol",
    "protobuf",
]
[target."cfg(unix)".dependencies]
chan-signal = "^0.2"

I'll attempt to repro this with a smaller use case.

I have tracked down the source of the configuration problem.  It has nothing to do with depending on a local crate path it is conflicting dependencies in crates.. The cause is that the crates postgres-protocol and blake2 both depend on different versions of generic-array and typenum.
in this case, postgres_r2d2 is also an optional dependency (but the feature is enabled by default)
       │   ├── postgres-protocol v0.3.0
│   │   │   ├── base64 v0.5.2
│   │   │   │   └── byteorder v1.1.0 (*)
│   │   │   ├── byteorder v1.1.0 (*)
│   │   │   ├── bytes v0.4.5 (*)
│   │   │   ├── fallible-iterator v0.1.3 (*)
│   │   │   ├── generic-array v0.7.2
│   │   │   │   ├── nodrop v0.1.9
│   │   │   │   │   └── odds v0.2.25
│   │   │   │   └── typenum v1.5.2
│   │   │   ├── hmac v0.1.1
│   │   │   │   ├── crypto-mac v0.3.0
│   │   │   │   │   ├── constant_time_eq v0.1.3
│   │   │   │   │   └── generic-array v0.7.2 (*)
│   │   │   │   ├── digest v0.5.2
│   │   │   │   │   └── generic-array v0.7.2 (*)
│   │   │   │   └── generic-array v0.7.2 (*)

├── blake2 v0.6.1
│   ├── byte-tools v0.2.0
│   ├── crypto-mac v0.4.0
│   │   ├── constant_time_eq v0.1.3
│   │   └── generic-array v0.8.2
│   │       ├── nodrop v0.1.9
│   │       │   └── odds v0.2.25
│   │       └── typenum v1.9.0
│   ├── digest v0.6.2
│   │   └── generic-array v0.8.2 (*)
│   └── generic-array v0.8.2 (*)

Setting the version to * for r2d2_postgres and letting it pick a compatible crate does alleviate the symptom.

Running in debug,  I do see 408 occurrences of :
DEBUG:cargo::core::registry: load/precise  registry https://github.com/rust-lang/crates.io-index
DEBUG:cargo::core::registry: load/precise  registry https://github.com/rust-lang/crates.io-index
DEBUG:cargo::core::resolver: checking if generic-array v0.8.2 is already activated

before it runs out of siblings.

It seems that cur, set by remaining_siblings.cur_index() is only really used for debugging purposes.  The real issue is that it is in a state where it is cycling through the dependency graph infinitely.  I'm still trying to understand the algorithm and figure out how it could get into such a state..

Here is the most minimal Cargo.toml I can create that repros the problem :
[package]
authors = ["Rick Richardson<EMAIL_ADDRESS>name = "break-cargo"
version = "0.1.0"

[dependencies]
blake2 = "0.6.1"

[dependencies.regex]
version = "0.2.2"
optional = true

[dependencies.protobuf]
optional = true
version = "^1.4"

[dependencies.r2d2_postgres]
version = "^0.13"
optional = true

[features]
default = [
    "postgres",
    "blah",
]
blah = [
    "regex",
     "protobuf",
]
postgres = ["r2d2_postgres"]

If you just make a project with deps on r2d2_postgres and blake2.  It detects the un-resolveable conflict for the typenum version dependencies.
But when you add in some additional optional dependencies,  it can't seem to traverse the graph.

Also,  I would note that there have been 2 major refactorings to the resolve module.  One a couple weeks ago and one in November of last year.  This toml breaks in the same way on the versions prior to those.

Thanks for the investigation and the report here @rrichardson! I'll take a look now and see what's up

Ok so the infinite loop here I believe is an instance of https://github.com/rust-lang/cargo/issues/4066 where this is an un-resolvable crate graph but Cargo isn't doing a great job of telling you that, unfortunately. (it takes forever to reach this conclusion)
The panic in debug mode though sounds like it's definitely a bug!

I believe this panic was since fixed, so closing.


Choice of classification algorithm

Hi,
I'm trying to adapt bioasq to another domains. But I have a problèmes whith  answer-type classifier module.
Your prefer to use linear regression classifier. but when i design a pipeline without specific NER models ( I use the general NER model), I obtain 30% of good predictions.
But whith opennlp document categorizer, i obtain 83% with a simple words and a general NER as features.
So, My question is why do you prefer to use linear regression ??


Application update script

Date: 27/12/2023

Description:
This PR adds an endpoint for running script which adds createdAt null to the existing applications in our backend, so as per our new requirement we are ordering the application with this field which is not there in the older applications doc. So they will be ignored when ordering.
Is Under Feature Flag

[x] Yes
[ ] No

Database changes

[ ] Yes
[x] No

Breaking changes (If your feature is breaking/missing something please mention pending tickets)

[ ] Yes
[x] No

Is Development Tested?

[x] Yes
[ ] No

Tested in staging?

[x] Yes
[ ] No

Test coverage:
controllers:

models:

routes

Local working proof:

Hi @vinayak-trivedi can you share the bigger picture, where is this going to be used?


Only set signals to Ignore on non-Linux of no signal-handler is in pl…

Only set signals to Ignore on non-Linux of no signal-handler is in place. Also set the SA_RESTART flag to avoid operations returning EINTR.
Please go the the Preview tab and select the appropriate pull request template for your changes:

Code Changes
Documentation Changes

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Markus Plichta seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add connect-to-servers extension

Description

Screencast

Checklist

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

Hi 👋
Thanks for your contribution 🔥
We already an extension dealing with smb in the store, could you check that one out?

Hey!
That's a cool one. I think I'll add auth for mine too. Maybe the one that I
created is too specific for my work case or my colleagues.
It allows me to connect to the servers I need straightaway. I can also do
multiple servers (in this case I'm just doing 2).
Because it disconnects so often, I need to reconnect every time. Having the
extension saves me so much time. And with the hotkey is even better.
We will keep using locally if you guys think it doesn't have a big audience
that could benefit from it like we do here.
Thanks for reaching out.
Em sex., 15 de nov. de 2024 às 00:42, Per Nielsen Tikær <
@.***> escreveu:

Hi 👋
Thanks for your contribution 🔥
We already an extension dealing with smb
https://www.raycast.com/SuoweiHu/network-drive in the store, could you
check that one out?
—
Reply to this email directly, view it on GitHub
https://github.com/raycast/extensions/pull/15269#issuecomment-2478149237,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANHHWQVUNVDL5E34WX6BQ532AWQXTAVCNFSM6AAAAABRL2AKWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZYGE2DSMRTG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Closing for now 😊


How to map Azure AD groups with Identity Domain groups in OCI

Creating an issue
There is no documentation provided for mapping Azure AD groups with OCI Identity domain group.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: f0424712-7d08-2ab4-b0dd-1243607299b9
Version Independent ID: 94c55884-b579-df5b-e055-1db3fc77ea0b
Content: Tutorial: Azure AD SSO integration with Oracle Cloud Infrastructure Console - Microsoft Entra
Content Source: articles/active-directory/saas-apps/oracle-cloud-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@kirankumar-badiger
Thanks for your feedback! We will investigate and update as appropriate.

Hi, here is the link: Tutorial: Azure AD SSO integration with Oracle Cloud Infrastructure Console
as this document is outdated and OCI is using Identity domains to manage the users

Hi @kirankumar-badiger
To map Azure AD groups with OCI Identity domain groups, you can follow the instructions provided in the 'Tutorial: Configure Oracle Cloud Infrastructure Console for automatic user provisioning with Azure Active Directory | Microsoft Docs'. The tutorial explains how to automatically provision and de-provision user accounts from Azure AD to Oracle Cloud Infrastructure Console. It also includes instructions on how to review the group attributes that are synchronized from Azure AD to Oracle Cloud Infrastructure Console in the Attribute-Mapping section.
https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/oracle-cloud-infrastructure-console-provisioning-tutorial

@kirankumar-badiger
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation

@ManoharLakkoju-MSFT Oracle Cloud is already using Identity domains to manage users and groups, in this documentation there is no specification of how these user or groups will get the permissions to OCI, there is no specification of how these groups are mapped

@kirankumar-badiger
I'm going to assign this to the document author so they can take a look at it accordingly
@jeevansd
Could you Please review this and update as appropriate.

we are working on the issue, will reflects the suggested changes into the main article soon.
#please-close


macOS 13.2.1 M2 processor brew install openssl error

I'm trying to install<EMAIL_ADDRESS>via brew, and it's failing during the make step.

These open issues may also help:
<EMAIL_ADDRESS>make keg_only on Linux https://github.com/Homebrew/homebrew-core/pull/119967

Thanks for any help in advance!

Trying to reproduce this, on a clean macOS Ventura 13.2.1 VM, running on an M2 Pro Mac mini, brew install<EMAIL_ADDRESS>works fine
m2-vm $ brew install<EMAIL_ADDRESS>==> Fetching dependencies for<EMAIL_ADDRESS>ca-certificates
==> Fetching ca-certificates
==> Downloading https://ghcr.io/v2/homebrew/core/ca-certificates/manifests/2023-01-10
##################################################################################################################################### 100.0%
==> Downloading https://ghcr.io/v2/homebrew/core/ca-certificates/blobs/sha256:11fe9d0a98a2ac454fa1db95762a697c3340f46560ff27e5e9db8fdeb003f1
==> Downloading from https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:11fe9d0a98a2ac454fa1db95762a697c3340f46560ff27e5e9db8fd
##################################################################################################################################### 100.0%
==> Fetching<EMAIL_ADDRESS>==> Downloading https://ghcr.io/v2/homebrew/core/openssl/1.1/manifests/1.1.1t
##################################################################################################################################### 100.0%
==> Downloading https://ghcr.io/v2/homebrew/core/openssl/1.1/blobs/sha256:e1e08ddd93298ef8776b202e4b2f86fc519bf27a72f7cfb082b69ff2868a0175
==> Downloading from https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:e1e08ddd93298ef8776b202e4b2f86fc519bf27a72f7cfb082b69ff
##################################################################################################################################### 100.0%
==> Installing dependencies for<EMAIL_ADDRESS>ca-certificates
==> Installing<EMAIL_ADDRESS>dependency: ca-certificates
==> Pouring ca-certificates--2023-01-10.all.bottle.tar.gz
Warning: The post-install step did not complete successfully
You can try again using:
  brew postinstall ca-certificates
==> Summary
🍺  /opt/homebrew/Cellar/ca-certificates/2023-01-10: 3 files, 216.9KB
==> Installing<EMAIL_ADDRESS>==> Pouring<EMAIL_ADDRESS>Warning: The post-install step did not complete successfully
You can try again using:
  brew postinstall<EMAIL_ADDRESS>==> Caveats
A CA file has been bootstrapped using certificates from the system
keychain. To add additional certificates, place .pem files in
<EMAIL_ADDRESS>
and run
<EMAIL_ADDRESS>
<EMAIL_ADDRESS>is keg-only, which means it was not symlinked into /opt/homebrew,
because macOS provides LibreSSL.

If you need to have<EMAIL_ADDRESS>first in your PATH, run:
  echo 'export PATH="/opt/homebrew/opt/openssl@1.1/bin:$PATH"' >> ~/.kshrc

For compilers to find<EMAIL_ADDRESS>you may need to set:
  export<EMAIL_ADDRESS>  export<EMAIL_ADDRESS>
==> Summary
🍺<EMAIL_ADDRESS>8,101 files, 18MB
==> Running `brew cleanup<EMAIL_ADDRESS>Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
==> Caveats
==><EMAIL_ADDRESS>A CA file has been bootstrapped using certificates from the system
keychain. To add additional certificates, place .pem files in
<EMAIL_ADDRESS>
and run
<EMAIL_ADDRESS>
<EMAIL_ADDRESS>is keg-only, which means it was not symlinked into /opt/homebrew,
because macOS provides LibreSSL.

If you need to have<EMAIL_ADDRESS>first in your PATH, run:
  echo 'export PATH="/opt/homebrew/opt/openssl@1.1/bin:$PATH"' >> ~/.kshrc

For compilers to find<EMAIL_ADDRESS>you may need to set:
  export<EMAIL_ADDRESS>  export<EMAIL_ADDRESS>

Since the OP's brew install was trying to compile openssl-1.1.1t from source, try that separately, also on M2 Pro Mac mini.
That also completes successfully with no errors
m2 $ curl -sOL https://www.openssl.org/source/openssl-1.1.1t.tar.gz
m2 $ tar xfz openssl-1.1.1t.tar.gz
m2 $ cd openssl-1.1.1t

m2 $ perl ./Configure no-ssl3 no-ssl3-method no-zlib darwin64-arm64-cc enable-ec_nistp_64_gcc_128
Configuring OpenSSL version 1.1.1t (0x1010114fL) for darwin64-arm64-cc
Using os-specific seed configuration
Creating configdata.pm
Creating Makefile

**********************************************************************
***                                                                ***
***   OpenSSL has been successfully configured                     ***
***                                                                ***
***   If you encounter a problem while building, please open an    ***
***   issue on GitHub <https://github.com/openssl/openssl/issues>  ***
***   and include the output from the following command:           ***
***                                                                ***
***       perl configdata.pm --dump                                ***
***                                                                ***
***   (If you are new to OpenSSL, you might want to consult the    ***
***   'Troubleshooting' section in the INSTALL file first)         ***
***                                                                ***
**********************************************************************

m2 $ make -j8
perl "-I." -Mconfigdata "util/dofile.pl" \
	    "-oMakefile" include/crypto/bn_conf.h.in > include/crypto/bn_conf.h
perl "-I." -Mconfigdata "util/dofile.pl" \
	    "-oMakefile" include/crypto/dso_conf.h.in > include/crypto/dso_conf.h
perl "-I." -Mconfigdata "util/dofile.pl" \
	    "-oMakefile" include/openssl/opensslconf.h.in > include/openssl/opensslconf.h
/Library/Developer/CommandLineTools/usr/bin/make depend && /Library/Developer/CommandLineTools/usr/bin/make _all
cc  -I. -Iinclude -fPIC -arch arm64 -O3 -Wall -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -D_REENTRANT -DNDEBUG  -MMD -MF apps/app_rand.d.tmp -MT apps/app_rand.o -c -o apps/app_rand.o apps/app_rand.c
cc  -I. -Iinclude -fPIC -arch arm64 -O3 -Wall -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -D_REENTRANT -DNDEBUG  -MMD -MF apps/apps.d.tmp -MT apps/apps.o -c -o apps/apps.o apps/apps.c
:
:
${LDCMD:-cc} -arch arm64 -O3 -Wall -L. -Wl,-search_paths_first  \
		-o test/uitest test/uitest.o \
		 apps/libapps.a -lssl test/libtestutil.a -lcrypto
rm -f apps/openssl
rm -f fuzz/asn1-test
${LDCMD:-cc} -arch arm64 -O3 -Wall -L. -Wl,-search_paths_first  \
		-o fuzz/asn1-test fuzz/asn1.o fuzz/test-corpus.o \
		 -lssl -lcrypto
${LDCMD:-cc} -arch arm64 -O3 -Wall -L. -Wl,-search_paths_first  \
		-o apps/openssl apps/asn1pars.o apps/ca.o apps/ciphers.o apps/cms.o apps/crl.o apps/crl2p7.o apps/dgst.o apps/dhparam.o apps/dsa.o apps/dsaparam.o apps/ec.o apps/ecparam.o apps/enc.o apps/engine.o apps/errstr.o apps/gendsa.o apps/genpkey.o apps/genrsa.o apps/nseq.o apps/ocsp.o apps/openssl.o apps/passwd.o apps/pkcs12.o apps/pkcs7.o apps/pkcs8.o apps/pkey.o apps/pkeyparam.o apps/pkeyutl.o apps/prime.o apps/rand.o apps/rehash.o apps/req.o apps/rsa.o apps/rsautl.o apps/s_client.o apps/s_server.o apps/s_time.o apps/sess_id.o apps/smime.o apps/speed.o apps/spkac.o apps/srp.o apps/storeutl.o apps/ts.o apps/verify.o apps/version.o apps/x509.o \
		 apps/libapps.a -lssl -lcrypto

m2 $ echo $?
0

The last few compile lines in the OP's post were also present in the log when building successfully from source
cc  -I. -Iinclude -fPIC -arch arm64 -O3 -Wall -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -D_REENTRANT -DNDEBUG  -MMD -MF crypto/rsa/rsa_pk1.d.tmp -MT crypto/rsa/rsa_pk1.o -c -o crypto/rsa/rsa_pk1.o crypto/rsa/rsa_pk1.c
cc  -I. -Iinclude -fPIC -arch arm64 -O3 -Wall -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -D_REENTRANT -DNDEBUG  -MMD -MF crypto/rsa/rsa_pmeth.d.tmp -MT crypto/rsa/rsa_pmeth.o -c -o crypto/rsa/rsa_pmeth.o crypto/rsa/rsa_pmeth.c
cc  -I. -Iinclude -fPIC -arch arm64 -O3 -Wall -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -D_REENTRANT -DNDEBUG  -MMD -MF crypto/rsa/rsa_prn.d.tmp -MT crypto/rsa/rsa_prn.o -c -o crypto/rsa/rsa_prn.o crypto/rsa/rsa_prn.c
cc  -I. -Iinclude -fPIC -arch arm64 -O3 -Wall -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -D_REENTRANT -DNDEBUG  -MMD -MF crypto/rsa/rsa_pss.d.tmp -MT crypto/rsa/rsa_pss.o -c -o crypto/rsa/rsa_pss.o crypto/rsa/rsa_pss.c
cc  -I. -Iinclude -fPIC -arch arm64 -O3 -Wall -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -D_REENTRANT -DNDEBUG  -MMD -MF crypto/rsa/rsa_saos.d.tmp -MT crypto/rsa/rsa_saos.o -c -o crypto/rsa/rsa_saos.o crypto/rsa/rsa_saos.c

However, the OP's log ends with
/bin/sh: line 1: 66575 Killed: 9               cmp crypto/rsa/rsa_gen.d.tmp crypto/rsa/rsa_gen.d > /dev/null 2> /dev/null

and there are no "cmp " lines in the build of OpenSSL 1.1.1t from source, suggesting that these come from Homebrew.

Last try: After installing Homebrew into the unsupported directory /Users/tom on the M2 VM, following the instructions at https://docs.brew.sh/Installation, Homebrew still successfully builds OpenSSL 1.1.1t.
m2-vm $ git clone https://github.com/Homebrew/brew homebrew
Cloning into 'homebrew'...
remote: Enumerating objects: 228752, done.
remote: Counting objects: 100% (45/45), done.
remote: Compressing objects: 100% (39/39), done.
remote: Total 228752 (delta 8), reused 8 (delta 6), pack-reused 228707
Receiving objects: 100% (228752/228752), 65.32 MiB | 7.92 MiB/s, done.
Resolving deltas: 100% (168264/168264), done.

m2-vm $ eval "$(homebrew/bin/brew shellenv)"

m2-vm $ brew update --force --quiet
==> Homebrew has enabled anonymous aggregate formula and cask analytics.
Read the analytics documentation (and how to opt-out) here:
  https://docs.brew.sh/Analytics
No analytics have been recorded yet (nor will be during this `brew` run).

==> Tapping homebrew/core
Cloning into '/Users/tom/homebrew/Library/Taps/homebrew/homebrew-core'...
remote: Enumerating objects: 1424384, done.
remote: Counting objects: 100% (307/307), done.
remote: Compressing objects: 100% (129/129), done.
remote: Total 1424384 (delta 188), reused 292 (delta 178), pack-reused 1424077
Receiving objects: 100% (1424384/1424384), 546.47 MiB | 8.49 MiB/s, done.
Resolving deltas: 100% (993233/993233), done.
Tapped 3 commands and 6538 formulae (6,890 files, 601.1MB).

m2-vm $ chmod -R go-w "$(brew --prefix)/share/zsh"

m2-vm $ brew install<EMAIL_ADDRESS>==> Fetching<EMAIL_ADDRESS>Warning: Building<EMAIL_ADDRESS>from source as the bottle needs:
- HOMEBREW_CELLAR: /opt/homebrew/Cellar (yours is /Users/tom/homebrew/Cellar)
- HOMEBREW_PREFIX: /opt/homebrew (yours is /Users/tom/homebrew)
==> Downloading https://www.openssl.org/source/openssl-1.1.1t.tar.gz
Already downloaded: /home/tom/Library/Caches/Homebrew/downloads/ec3feb171aa63b32c30a6e7423e78f743f92d1ef984b66b0ea548d08220c0ce6--openssl-1.1.1t.tar.gz
==> perl ./Configure<EMAIL_ADDRESS><EMAIL_ADDRESS>no-ssl3 no-ssl3
==> make
==> make install<EMAIL_ADDRESS>MANSUFFIX=ssl
==> make test
==> Caveats
A CA file has been bootstrapped using certificates from the system
keychain. To add additional certificates, place .pem files in
<EMAIL_ADDRESS>
and run
<EMAIL_ADDRESS>
<EMAIL_ADDRESS>is keg-only, which means it was not symlinked into /Users/tom/homebrew,
because macOS provides LibreSSL.

If you need to have<EMAIL_ADDRESS>first in your PATH, run:
  echo 'export PATH="/Users/tom/homebrew/opt/openssl@1.1/bin:$PATH"' >> ~/.kshrc

For compilers to find<EMAIL_ADDRESS>you may need to set:
  export<EMAIL_ADDRESS>  export<EMAIL_ADDRESS>
==> Summary
🍺<EMAIL_ADDRESS>8,094 files, 18.0MB, built in 2 minutes 22 seconds
==> Running `brew cleanup<EMAIL_ADDRESS>Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).

m2-vm $ echo $?
0

This appears to be a local issue on the OP's machine: Homebrew successfully installs OpenSSL 1.1.1t, will build it for an (unsupported) non-standard installation directory, and OpenSSL 1.1.1t builds successfully on its own, on Apple Silicon M2 system.

@tom-cosgrove-arm thank you so much for your time and detailed validation!
I had performed the same brew unsupported install steps as you described and tried once again with a clean setup but still had the same error. The one line that caught my attention between yours and mine is this one:
Yours:
==> perl ./Configure<EMAIL_ADDRESS><EMAIL_ADDRESS>no-ssl3 no-ssl3

Mine:
==> perl ./Configure<EMAIL_ADDRESS><EMAIL_ADDRESS>no-ssl3 no-ssl3-method no-zlib darwin64-arm64-cc enable-ec_nistp_64_gcc_128

Not sure if that makes any difference, but as you pointed this appears to be a local environment issue associated with the brew install and not a problem with openssl.
Thank you!

Hi, I see you've closed this now, but if you are still having problems, it would be helpful to look for any "error" lines from the Homebrew build logs and include them here

Reopening per @tom-cosgrove-arm's suggestion to document the solution. Also posted this issue to stack overflow: https://stackoverflow.com/questions/75562209/macos-13-2-1-m2-processor-brew-install-openssl-error

Looking again, it seems from Last 15 lines from<EMAIL_ADDRESS>that the build logs are in<EMAIL_ADDRESS>so if you could attach them here we can look for errors (or possible "permission denied"s)

This was an issue with the user setup process on a company-provided Mac. I'm now able to install openssl.

Hi @rstrazza! Sorry for opening this issue after all this time.
But myself and a couple of coworkers, are facing a similar issue to yours. Could you please elaborate on the solution found?
Thanks in advance 🙏🏼

@tom-cosgrove-arm
for some reason I want install openssl 1.0 on my intel mac mini ventura 13.3.1,but always no luck
Could you help me,
thank you
`jack6@jack6s-Mac-mini ~ % brew install<EMAIL_ADDRESS>==> Downloading https://formulae.brew.sh/api/formula.jws.json
-=O=- #    #     #      #
Error: Formulae found in multiple taps:
*<EMAIL_ADDRESS>*<EMAIL_ADDRESS>Please use the fully-qualified name (e.g<EMAIL_ADDRESS>to refer to the formula.
jack6@jack6s-Mac-mini ~ % brew install<EMAIL_ADDRESS>==> Fetching<EMAIL_ADDRESS>==> Downloading https://www.openssl.org/source/openssl-1.0.2t.tar.gz
Already downloaded: /Users/jack6/Library/Caches/Homebrew/downloads/5d2da6a9ed1a20ef9d1b1418d79aa674cf5577b70ca1ce436fdaadfa04f0429c--openssl-1.0.2t.tar.gz
==> Installing<EMAIL_ADDRESS>from rbenv/tap
==> perl ./Configure<EMAIL_ADDRESS>--openssldir=/usr/local/etc/openssl no-ssl2 no-ssl3 no-
==> make depend
==> make
==> make test
Last 15 lines from<EMAIL_ADDRESS>140704585241580:error:100B906B:elliptic curve routines:EC_POINT_set_affine_coordinates_GF2m:point is not on curve:ec_lib.c:994:
140704585241580:error:100B906B:elliptic curve routines:EC_POINT_set_affine_coordinates_GF2m:point is not on curve:ec_lib.c:994:
140704585241580:error:100B906B:elliptic curve routines:EC_POINT_set_affine_coordinates_GF2m:point is not on curve:ec_lib.c:994:
140704585241580:error:100B906B:elliptic curve routines:EC_POINT_set_affine_coordinates_GF2m:point is not on curve:ec_lib.c:994:
140704585241580:error:100B906B:elliptic curve routines:EC_POINT_set_affine_coordinates_GF2m:point is not on curve:ec_lib.c:994:
140704585241580:error:100B906B:elliptic curve routines:EC_POINT_set_affine_coordinates_GF2m:point is not on curve:ec_lib.c:994:
140704585241580:error:100B906B:elliptic curve routines:EC_POINT_set_affine_coordinates_GF2m:point is not on curve:ec_lib.c:994:
140704585241580:error:100B906B:elliptic curve routines:EC_POINT_set_affine_coordinates_GF2m:point is not on curve:ec_lib.c:994:
140704585241580:error:100B906B:elliptic curve routines:EC_POINT_set_affine_coordinates_GF2m:point is not on curve:ec_lib.c:994:
140704585241580:error:100B906B:elliptic curve routines:EC_POINT_set_affine_coordinates_GF2m:point is not on curve:ec_lib.c:994:
140704585241580:error:1007C06B:elliptic curve routines:EC_POINT_set_affine_coordinates_GFp:point is not on curve:ec_lib.c:968:
140704585241580:error:1007C06B:elliptic curve routines:EC_POINT_set_affine_coordinates_GFp:point is not on curve:ec_lib.c:968:
140704585241580:error:1007C06B:elliptic curve routines:EC_POINT_set_affine_coordinates_GFp:point is not on curve:ec_lib.c:968:
make[1]: *** [test_ec] Error 1
make: *** [tests] Error 2
If reporting this issue please do so at (not Homebrew/brew or Homebrew/homebrew-core):
https://github.com/rbenv/homebrew-tap/issues
These open issues may also help:
brew install<EMAIL_ADDRESS>not working anymore https://github.com/rbenv/homebrew-tap/issues/1
jack6@jack6s-Mac-mini ~ % `

Hi @rstrazza! Sorry for opening this issue after all this time.
But myself and a couple of coworkers, are facing a similar issue to yours. Could you please elaborate on the solution found?
Thanks in advance 🙏🏼

@Ivopires, apologies for the delayed reply. In my case, the problem was with my user permissions. One of my colleagues had a similar issue, and he solved it by doing the following:
"Not a home directory solution. Most tools only seem to work when Homebrew is in /opt. However, I was able to do a sudo mkdir /opt/homebrew. Then do a sudo tar copy of my "Untar Anywhere" install from my home directory into /opt/homebrew"

(base) selassie@Selassies-MacBook-Pro ~ % conda install -c "bioconda/label/cf201901" samtools
Collecting package metadata (current_repodata.json): failed
CondaSSLError: OpenSSL appears to be unavailable on this machine. OpenSSL is required to
download and install packages.
Exception: HTTPSConnectionPool(host='conda.anaconda.org', port=443): Max retries exceeded with url: /bioconda/label/cf201901/osx-64/current_repodata.json (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available."))
@rstrazza I tried all the steps and still getting this error, any help


Is it possible to merge pkgj?

A lot of progress has been made with pkgj in the past year, and it might be unnecessary to re create all these features. I am not saying replace pkgi or anything, I am just suggesting making pkgj's features part of pkgi, so you can build further rather than starting from scratch. There hasn't been a commit here in a while, and this might be a good place to start. It would be great to see pkgi back in the game! I hope you consider this.

Sorry, but this is not how pull requests work.
You don't create fork, do a hundreds of commits which changes everything and then submit one pull request with all the changes.
What you do, is you create pull request for specific features/bugs/issues that code changes.
So pull request should be for specific feature A, different one for specific improvement B, another for specific bug C, etc..
I would gladly accept pull requests, but they need to be logically simple, not these massive changes.
As a minimum they also would need to be in same style as rest of the code. Not suddenly changing code from C to C++.
As for why there haven't been commits here, that's because my enthusiasm working on pkgi is pretty much zero. If you where not on Vita discord last year, then short background - people in Vita scene are super uncooperative, very non-collaborative and selfish. Instead of working on same goals, collaborating and contributing, many just wanted to take something that is made by others, slap their name on top of it, and be done (this is not only about pkgj). That's why my interest in continuing on pkgi went to the bottom of list of things that I want to do.
That said, there were a few helpful people that helped to improve pkgi. Unfortunately they where the minority.


Create statistics

Collect how many secrets that are currently active
Collect how many secrets are burned
Collect how many visits to the page

Important: Do not track personal data at all.
None of these should be tracked by 3d party applications.

How many secrets created on a daily basis: https://github.com/HemmeligOrg/Hemmelig.app/commit/e94934738dd31af66c226df79057c7715ee67502


Disable flaky undo spec

Since the spec randomly fails in CI, I've decided to disable it until I can find a way to fix it

Superseded by https://github.com/mui/mui-toolpad/pull/1415


Dynamic Plugin support for Remotes

Rhodecode is full blown hg and git code hosting. It has hooks, user permissions api keys, I think all that's needed to support it in drone.
Also it has ssh clone/push support (https://code.rhodecode.com/rhodecode-ssh)
It's open source, you can run it self hosted (free to 20 users).
Would be cool to support it in drone.

Any movement on this?

In an effort to prevent feature creep, I am closing this as out-of-scope for the project.


fix: remove xl breakpoint for grid

This will fix https://github.com/drodil/backstage-plugin-toolbox/issues/22

Thanks a lot for the contribution! Tried to reproduce this but couldn't but happy it works for you! Will push a fix release right after this has been merged.


Need an option to avoid using HPM counter CSRs

When generating the all/random template we appear to end up with reads of HPM CSRs indices (I believe rv32_zicsr is where this comes from?) and those result in divergences vs sail. Would be good to have an option to explicitly avoid those CSR numbers for has_ihpm == false.

Apologies, I started looking, but it seems they could come from multiple different sources. I'll dig into this more on Monday.


Custom YOLO model

Hello,
Thanks for your contribution. I am trying to implement a custom model with a different number of classes but I'm not sure where to apply my changes. Could you help me with this process?
Thanks in advance.

@darich10 thank you for your kind question. You can learn custom model implementation here: https://blog.roboflow.com/how-to-train-yolov8-on-a-custom-dataset/. Basically you need to generate model, indicate path to it, then replace classes in this code.
Alternatively I added tensorflow.js implementation. The only difference is that you convert your custom model to tfjs model.
I hope this helps.


[NEW] NG integration attended xfer

Did you test all edge cases, like:

video calls
switching between channels or private conversation while on call (with and without video)
switching between channels or private conversation while incoming call is ringing
video to full screen and back to normal
caller closes call while waiting to be transferred
called (transfer destination) refuses the call

... and so on?


:robot: triggering CI on branch 'release-next' after synching from upstream/main

Codecov Report
Patch and project coverage have no change.

Comparison is base (af5ee64) 49.00% compared to head (5952634) 49.00%.
Report is 1 commits behind head on release-next.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff              @@
##           release-next     #695   +/-   ##
=============================================
  Coverage         49.00%   49.00%
=============================================
  Files                96       96
  Lines             13105    13105
=============================================
  Hits               6422     6422
  Misses             6047     6047
  Partials            636      636

Files Changed
Coverage Δ

pkg/builders/builders.go
80.00% <ø> (ø)

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

/override "On Cluster Test (1.20.2, ubuntu-latest)"
/override "Integration Test (1.20.2, ubuntu-latest)"

OCF Webhook is merging this PR

OCF Webhook is merging this PR

OCF Webhook is merging this PR

OCF Webhook is merging this PR


smembers return

Hello,
I need to request a redis db containing sets.
I think there is a problem with smembers and its return values :
std::vector<int> el;   client.smembers(key), [&] (cpp_redis::reply& reply) {         std::vector<cpp_redis::reply> rep = reply.as_array();         for (auto it = rep.begin(); it != rep.end(); it++){             el.push_back(std::stoi(it->as_string()));         }     });     client.commit();
I get pieces of the good answer and then segfault or memory error if i use this code. But if I put a sleep(1) before (or after) client.commit(); it's ok.
So I think the problem is the client is not reading returned values as far as they're sent. I can't use a sleep(1) because of my application.
Have you ever experienced that ? Thank you for your help.

Hi,
Unfortunately, I can't reproduce the bug on my machines.
Considering the fact that adding a sleep(1) seems to solve your problem, would it be possible that your program terminates while the different callbacks are executed?
In the examples, I used a while (not should_exit) loop: do you have a construct that allow you to avoid the destruction of the redis_client while there are still callback being processed?
If not, is there any way you could provide a valgrind report or gdb backtrace that could help me localize the problem? I'll keep trying to reproduce the error but it would help me a lot.
Thanks

I used a sync_commit and it solved it.


Safari browser crashes under the unit settings menu

Describe the bug
Safari browser crashes if you try to select a different unit under the unit settings dropdown menu.
To Reproduce
Try to pick a different unit other than km under the settings on the port 4000 portal under the settings section.
I am only able to reproduce this on Safari. It works fine on chrome or firefox.
Relevant entries from the logs
Nothing specifically interesting in the logs.Just a couple 200 GET requests:
Nov 18 19:19:48 ip-172-31-10-127 docker-compose[18403]: teslamate_1  | 19:19:48.521 [info] GET /settings
Nov 18 19:19:48 ip-172-31-10-127 docker-compose[18403]: teslamate_1  | 19:19:48.523 [info] Sent 200 in 2ms
Nov 18 19:20:48 ip-172-31-10-127 docker-compose[18403]: teslamate_1  | 19:20:48.699 [info] GET /settings
Nov 18 19:20:48 ip-172-31-10-127 docker-compose[18403]: teslamate_1  | 19:20:48.701 [info] Sent 200 in 2ms
Screenshots

Operating environment (please complete the following information):
OS: MacOS Mojave 10.14.6 (18G95)
Version: v1.12.2

I could not reproduce this behavior with Safari 13.0.3 on macOS Catalina. I assume that the problem was caused by a dependency. Chances are that this is already fixed on the master branch.

Does the issue still exist with version v1.13.0?

Happened to me as well with Mojave v10.14.6.

Does the issue still exist with version v1.13.0?

Yes, this is still happening with v.1.13.1. It makes the whole browser crash

I wasn't even able to get to it. Safari Version 13.0.3 (146<IP_ADDRESS>.1).
There is "spinner" overlay (on both main page and settings) and the dropdown can't be expanded. I see
WebSocket connection to 'wss://xxx.yyy.net/live/websocket?baseUrl=https%3A%2F%2Fxxx.yyy.net&referrer=https%3A%2F%2Fxxx.yyy.net%2F&vsn=2.0.0' failed: Unexpected response code: 401

in console. In Chrome it works just fine (on the same machine). The server is using traefik in pretty much default config (as in the advanced doc). Ports 80 and 443 forwarded on firewall.

I still cannot reproduce this. Since it works in all other browsers, I assume that there is a bug in Safari. Please report back if you find out more or if a future update of Safari fixes the problem.


is the method 'shouldTransform' still available?

Did the method 'shouldTransform' ever get merged into this project?
https://www.npmjs.com/package/multer-s3-transform is forwarding here, but I cannot see any mentions of it in the codebase.
I am looking for a hook to use sharp() to pre-process my images.
Thanks!

Did you find a solution?

use this one
"npm install multer-s3-transform"


Add database specific string concatenation

Hi All (and Mr. Love Doctor)
String concatenation is database specific.
Most databases support column1 || column2, but databases like mysql uses concat(column1, column2).
To support both databases, developers need to build database specific sql. It seems that arel is a good spot for this abstraction.
If Arel is not the right place, do you have suggestions on how to abstract this out in my own app?
Thanks,
Keenan
/cc @fryguy @matthewd (and of course @tenderlove ) This is for ancestry, but I feel we want something similar in our spot as well.

It looks like #173 was closed, but not exactly sure why. Is it because this is not the right layer for this abstraction, or because that did not support mysql?
Thanks

It looks like #173 was closed, but not exactly sure why. Is it because this is not the right layer for this abstraction, or because that did not support mysql?
Thanks

@rafaelfranca Does this look like something that could go into Arel?
thanks

Yes. It makes sense. Thank you for the pull request.


[stable/kong] Added support for Kong datastore password config through secrets

It is now also possible to use a map for kong.env params, effectively allowing use of a secret instead of the password itself to configure the datastore backend.

/assign @hbagdi

/assign shashiranjan84

I can't figure out how a secret would be rendered correctly in this case.
Could you give an example of how you would use this?

/hold

@hbagdi Instead of providing kong.env.pg_password with a raw text password this PR makes it possible to provide a mapping instead.  like this
kong:
  env:
     pg_user: kong
     pg_password:
       valueFrom:
         secretKeyRef:
            key: kong
            name: postgres

To be clear, this PR makes it not only  possible for kong.env.pg_password, but for all kong.env parameters.

/hold cancel
/ok-to-test
@tmestdagh Mind rebasing on master to resolve the conflict?
Also, please prefix the PR titles with [stable/kong] so that we have a clearer commit log in the repository.

/retest

/lgtm


readme.md issue

Doc says

Note: Multi-arch tags, such as 4.7.1, have been updated to use nanoserver-1709 images if your host is Windows Server 1709 or higher or Windows 10 Fall Creators Update (Version 1709) or higher. You need Docker 17.10 or later to take advantage of these updated tags.

As far as I can tell this is not true, it's using server code 1709.  Thanks.

Resolved with https://github.com/Microsoft/aspnet-docker/pull/90.


Division in inspector rounds result

Godot version:
3.1 beta 4
Issue description:
Example:

Node2D -> Inspector -> Transform
In Scale.X write 1/2 and hit Enter

Result: value is 0
Expected: value is 0.5
Note:
I'm not sure if this expected behavior, but in my opinion as "scale" is vector2 and it contains X and Y which are float, so the result of division calculation should be float as well. But right now result is rounded.

That's intended behaviour, most programming languages work this way. If you divide an integer by an integer, you get an integer (and thus the integral part of the division).
Use 1.0/2, 1/2.0 or 1.0/2.0 if you want a float.

That's intended behaviour

That's terrible behavior, though. The inspector is not a programming language and a field in the inspector is not a coding area - if anything, people will see it like a calculator.
This is an important necessary feature that should work predictably; it shouldn't be replaced with irregular behavior just because of some technicality. This badly hurts usability, even for coders and will confuse beginners.
Often you want to quickly divide a bunch of values to make adjustments in a batch, without having to pay attention to the actual value. If the field is float, then adding /4 at the end of the current value should give me a float division always. Current behavior is awful because this will depend on the current value. If it shows 1.01 then I get it right, but if it happens to show 1 instead, then I won't get 1.0/4 = 0.25, but an integer division nobody would expect on a float field.
I'm not asking to "solve" this by showing 1.0 unnecessarily.
What should happen is whatever parser that evaluates this should either:

parse all numeric literals as the field type - if the field is long, then it's only fair that it would make integer division
parse all numeric literals as double, like in JS, then cast the calculation result to the field type at the end
or just cast values to double before all divisions

If you really want to allow integer/floor division in float fields, then make a // operator like in Python, or a div function.
@akien-mga Please reopen.

If you want to change the behaviour open a proposal though I'm pretty sure there's one already if you search, this is for bugs and shouldn't be reopened


Pontoon documentation: Update search_filters.md

Fixes #216
Initial pass for text. Screenshots to be updated.

Sorry, realized the document doesn't cover one thing: the menu is different when All Projects is selected.
We should call out that translation time, translation authors and tags are not available in this case.
Once that's fixed, this should be good to go.

Added a note at the very bottom.


fix: cdn version

Description
Before:

After:

Fixes # TA-2332
Checklist

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own changes
[X] I have run yarn lint to make sure my changes pass all tests
[X] I have run yarn test to make sure my changes pass all linters
[X] I have pulled the latest changes from the upstream main branch
[X] I have tested both the react and the CDN versions on local and integration environments
[X] I have added the necessary labels to this PR in case a new release needs to be published after merging into main (e.g. release and patch)

Contribution guidelines
For contribution guidelines, styleguide, and other helpful information please
see the CONTRIBUTING.md file in the root of this project.

:rocket: PR was released in v2.22.3 :rocket:


Update on keyboard shortcuts to tooltips #988

Added function of combining name and shortcut.
This function applied to all buttons.
fixes #988

Perfect, nice code, thank you!

I'm going to squash and merge, i.e. reduce this PR to a single commit. I see that you issued the PR from your master branch: the simplest will be to delete it and check it out again.


Skip exit checks in unrolled loops

Emit skip_exit_check for unroll pragmas. According to the manual:
skip_exit_check: An optional keyword that applies only if partial unrolling is specified with factor=. The elimination of the exit check is dependent on whether the loop iteration count is known or unknown:

Fixed (known) bounds: No exit condition check is performed if the iteration count is a multiple of the factor. If the iteration count is not an integer multiple of the factor, the tool:

Prevents unrolling.
Issues a warning that the exit check must be performed to proceed.

Variable (unknown) bounds: The exit condition check is removed as requested. You must ensure that:

The variable bounds is an integer multiple of the specified unroll factor.
No exit check is in fact required.

Fixes #127.

@sa2257 Make sure this is okay and ping me here if it isn't. Merging now.


Can we have an  option to display DB hosts styled as list, not only as card?

I've in app more than 20 hosts added and this looks not well with the card design. List in my case might look better from UI/UX part.

can we share to us one screenshot? So maybe someone can try to fix the issue
💪


Port demos to GNOME 46

Closes https://github.com/workbenchdev/demos/issues/68 and more
See commits
CI fails here because it's using Workbench 45
but I tested locally with make ci in Workbench which runs over all demos

but I tested locally with make ci in Workbench which runs over all demos

Excluding Rust demos, right?


refactoring components common

split common into three files
replace all occurences of cms_ to cms- in there

LGTM


Enhance node agent CLI to support url formatted invitations

Signed-off-by: Patrik Stas<EMAIL_ADDRESS>

Codecov Report

Merging #562 (29e939c) into main (b9d817e) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #562      +/-   ##
==========================================
- Coverage   60.93%   60.92%   -0.01%
==========================================
  Files         175      175
  Lines       17998    17998
  Branches     3966     3966
==========================================
- Hits        10967    10966       -1
  Misses       2847     2847
- Partials     4184     4185       +1

Flag
Coverage Δ

integration-aries-vcx
49.64% <ø> (ø)

unittests-agency-client
25.97% <ø> (ø)

unittests-aries-vcx
54.53% <ø> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

...vcx/src/protocols/issuance/issuer/state_machine.rs
71.32% <0.00%> (-0.13%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Sonic the Anonymous WizHog: Watch thuongthuong.vn

Sonic the Anonymous WizHog requests the watch of the watch_keyword thuongthuong\.vn. See the MS search here and the Stack Exchange search here.

thuongthuong\.vn has been seen in 0 true positives, 0 false positives, and 0 NAAs.

I watched this prior to seeing this PR was open.


Throws NullReferenceException caused by ImageService is null

Description
ImageService is null as a result, it causes NullReferenceException.
Steps to Reproduce
Add a file contains below.
<?xml version="1.0" encoding="utf-8" ?>
<ContentView
    x:Class="App.Infrastructure.Components.RoundImage"
    xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
    xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
    xmlns:ffsvg="clr-namespace:FFImageLoading.Maui;assembly=FFImageLoading.Maui"
    xmlns:fftransformations="clr-namespace:FFImageLoading.Transformations;assembly=FFImageLoading.Maui"
    x:Name="This">
    <ffsvg:CachedImage
        Aspect="AspectFit"
        DownsampleToViewSize="true"
        ErrorPlaceholder="{Binding FallbackSource, Source={x:Reference This}}"
        HorizontalOptions="FillAndExpand"
        LoadingPlaceholder="{Binding FallbackSource, Source={x:Reference This}}"
        Source="{Binding EffectiveSource, Source={x:Reference This}}"
        VerticalOptions="Fill">
        <ffsvg:CachedImage.Transformations>
            <fftransformations:CircleTransformation />
        </ffsvg:CachedImage.Transformations>
    </ffsvg:CachedImage>
</ContentView>

Set Source binding property from behind the code. At this time, It was Stream. but it does not matter as ImageService was null.
Expected Behavior
Should not throws NullReferenceException.
Actual Behavior
throws NullReferenceException.
Basic Information

Version with issue: 1.0.3
Last known good version:
Platform: Maui with .net 8

Screenshots

It could FindMauiContext() returns null.

Is it supported already in .net 8 maui? I raised an issue about it and it's coming

@NishiokaTakeo I have reviewed your merge request, your code can prevent NRE but still not fix the cause of NRE. The better fix is to find out why FindMauiContext() returns null. Can you upload the full demo project then I can take a more deep look for this issue.

I found this to be the case in my app because I was setting MainPage for my App class too early. Application.Current.Handler wasn't set yet when I was setting MainPage and that caused FindMauiContext() to return null.
I worked around this by setting MainPage in an overload of CreateWindow in my application class. By that time, Application.Current.Handler was properly set. The takeaway is that you have to be conscious of when your pages that have CachedImages on them are being created. It's at that time when FindMauiContext() is being called.
This probably is not the solution but perhaps it gives some insight as to why FindMauiContext() might be returning null. It might not be looking in the right places, or in the right places at quite the right time.

Hi @brunck , Thanks for reply and the workaround works for my case as well.
I was setting MainPage for my App class too early. Application.Current.Handler wasn't set yet when I was setting MainPage and that caused FindMauiContext() to return null.
@microspaze,
As @brunck pointed out, I think FFImageLoading.Maui library should take care into above case and the library should not throw exception.
MS document supposes to set MainPage in App constructor. But not strongly mention as xamarin document does.
For Xamarin, document mentioned,
The MainPage property should be set in the App constructor,
It would be great if you revaluate PR goes in.

I have merged the push request. Thanks very much!

The latest version 1.0.7 has been uploaded to NUGET. You can try it to verify this issue.

Had this problem in an application, and the workaround posted from @brunck helped out.
After updating FFImageLoading.Maui to 1.0.7 and reverting the workaround changes, the app is working as expected and images are showing up normally.

I confirmed the issue does not happen. Thank you for fixing!

Since version 1.2.6 the problem has returned
ImageService.Instance is null
In version 1.2.5 is good
Please check this

@Jasper7 I really don't know what had been changed in Maui. But if you upgrade Maui to the latest version, then those wired problems will all disappear. JUST TRY: sudo dotnet workload update

@microspaze  I've just run
sudo dotnet workload update

with versions: 1.2.5, 1.2.6, 1.2.7 but I have always the same issue: ImageService.Instance is null


acl list returns two times

ACL list returns two times same result.
consul-cli acl list --token='MASTER TOKEN'
[
{
"CreateIndex": 4,
"ModifyIndex": 4,
"ID": "MASTER TOKEN",
"Name": "Master Token",
"Type": "management",
"Rules": ""
},
{
"CreateIndex": 3,
"ModifyIndex": 3,
"ID": "anonymous",
"Name": "Anonymous Token",
"Type": "client",
"Rules": ""
}
][
{
"CreateIndex": 4,
"ModifyIndex": 4,
"ID": "MASTER TOKEN",
"Name": "Master Token",
"Type": "management",
"Rules": ""
},
{
"CreateIndex": 3,
"ModifyIndex": 3,
"ID": "anonymous",
"Name": "Anonymous Token",
"Type": "client",
"Rules": ""
}
]
Is this a bug?

It is. https://github.com/CiscoCloud/consul-cli/releases/tag/v0.3.1 has the fix.


game-specific-rules list not complete

https://github.com/SAP-samples/devtoberfest-2021/blob/main/contest/readme.md#game-specific-rules
In line 39 the end of the sentence is missing.

Thank you pointing that out.  Looks like a cut and paste error as that line was out of context. I've corrected.


RuntimeError: Unsupported op with parameters: upsample_1(generic)

Hi, I'm working with vitis-ai-optimizer_tensorflow2 environment in Vitis AI 2.5. Following the "mnist_convnet" example with my stacked hourglass alike model, I'm getting an error:
raise RuntimeError('Unsupported op with parameters: {}({})'.format(
RuntimeError: Unsupported op with parameters: upsample_1(generic)
Where upsample_1 is Conv2DTranspose layer type.
while trying to run:
runner = IterativePruningRunner(model, input_spec)
runner.ana(evaluate)
Any help appreciate!

Hi @acg93-pixel,
The supported operations in VAI Optimizer 2.5:

layers.Conv2D
layers.DepthwiseConv2D
layers.Dense
layers.BatchNormalization

Conv2DTranspose is not supported currently and will be supported in Vitis 3.0

Thanks, when is Vitis 3.0 release date?

Thanks, when is Vitis 3.0 release date?

About January next year.

@yuwang-xlnx
Hi, When I prune my model, I meet an error: nndct_shared.pruning.errors.OptimizerNotExcludeNodeError: Must exclude node from pruning: FastCS::FastCS/Sequential[decoder]/ConvTranspose2d[0]/ret.7.
I tried to solve this with the excludes parameter: excludes = ['FastCS::FastCS/Sequential[decoder]/ConvTranspose2d[0]/ret.7' ], pruing_runner.ana(eval_fn, gpus, excludes=excludes)
but it didn't work. How should I use the excludes parameter?
I used Vitis-AI 3.0 on Ubuntu 20.04. Thanks.


Fix duplicate rev namespace in injector list

Please provide a description of this PR:
The webhook can contains several webhooks that is matching the namespace, and currently the namespace may be duplicated:
istioctl x injector list
...

NAMESPACES          INJECTOR-HOOK              ISTIO-REVISION SIDECAR-IMAGE
...
hello               istio-revision-tag-default default        hanxiaop/proxyv2:1.21.0-1226
...
hello               istio-revision-tag-default default        hanxiaop/proxyv2:1.21.0-1226

this is to remove the duplications per revisioned webhook.

@hanxiaop: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
61d26568fa1e86950f83798b05c062372586e002
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
697d536564cf172887be1be77a7aaf550dd1c6d7
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-ambient

@hanxiaop: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
697d536564cf172887be1be77a7aaf550dd1c6d7
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-ambient

@hanxiaop: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
697d536564cf172887be1be77a7aaf550dd1c6d7
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-ambient

@hanxiaop: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
6bb4d7e73787461931b2eeba70930eeda69e64b2
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-ambient


⚠ Text Filter API Endpoint has degraded performance

In 171b429, Text Filter API Endpoint (http://textfilter.roblox.com/) experienced degraded performance:

HTTP code: 200
Response time: 6252 ms

Resolved: Text Filter API Endpoint performance has improved in 525750b.


Document Theme Experiments

As a theme author and reader of MDN web docs, I want to be able to access documentation on the subject of theme experiments as described in Bugzilla #1347207.
This bug describes creating experimental theme features by adding a "theme_experiment" key to manifest.json.
Tasks

[ ] Determine what has been proposed and what has been implemented for this feature
[ ] Get a list of the topics that need to be documented and estimate the scope of work needed
[ ] Write new documentation for theme experiments
[ ] Create a sample of a theme that includes a "theme_experiment" key

Acceptance Criteria

[ ] A description of the implemented work (by FF release) has been added to this issue
[ ] A list of topics to be created has been added
[ ] New documentation created

Theme experiment details are published: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/theme_experiment


Vulnerabilities in Debian

Hi,
Since there are alot of vulnerabilities with Debian 10, how and when are they going to be patched?
As mentioned in this issue #327, which was closed without an answer, alpine has nu vulnerabilites while Debian has too many.
How must we continue with this? Security-wise this is not acceptable.

I believe that question was answered - https://github.com/Azure/azure-functions-docker/issues/327#issuecomment-730558561
If you could share the list of vulnerabilties you are seeing, we can verify (and fix) if any of those have released patches now. Thanks

Hi! thanks alot for your replying so fast.
Qualys on our Azure Service center noticed these, and stated that they are patchable:
1/ Debian Security   Update for openssl (DSA 4855-1):
Refer to Debian   security advisory https://lists.debian.org/debian-security-announce/2021/msg00035.html for patching details.
Patch: Following are links for downloading patches to fix the   vulnerabilities:    https://lists.debian.org/debian-security-announce/2021/msg00035.html
2/ Debian Security   Update for openssl (DSA 4875-1)
Refer to Debian   security advisory https://lists.debian.org/debian-security-announce/2021/msg00056.html for patching details.
Patch:
Following are links for downloading patches to fix the   vulnerabilities:    https://lists.debian.org/debian-security-announce/2021/msg00056.html
3/ Debian Security   Update for p11-kit (DSA 4822-1)
Refer to Debian   security advisory https://lists.debian.org/debian-security-announce/2021/msg00000.html for patching details.
Patch:
Following are links for downloading patches to fix the   vulnerabilities:     https://lists.debian.org/debian-security-announce/2021/msg00000.html
Our dockerfile looks like this, I think this is 99% the default when building functions v3, only that the dotnet publish is done already before docker builds it:
FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS installer-env
COPY . /home/site/wwwroot
FROM mcr.microsoft.com/azure-functions/dotnet:3.0
ENV AzureWebJobsScriptRoot=/home/site/wwwroot
AzureFunctionsJobHost__Logging__Console__IsEnabled=true
COPY --from=installer-env ["/home/site/wwwroot", "/home/site/wwwroot"]

Hello,
i would like to participate in that discussion because we are facing exactly the same situation (with mcr.microsoft.com/azure-functions/python:3.0-python3.7)
Our scanner found two critical issues (besides several high and low ones): CVE-2021-20231 and CVE-2021-20232
Are there any plans to go at least to a newer version of Debian?
I would also be very interested for the concrete reasons for not using an alpine base image.

Still no feedback? This is taking quite long for just an answer, no?

@janvanuytrecht Sorry for the delay. I ran qualys scan on mcr.microsoft.com/azure-functions/dotnet:3.0 (sha256:51e397ceb4863898580b360ca3d4ed6e29d36095983fd38e6cb526f8eb69144e) and the only vulnerability we see is the below one which doesn't have a patch.

Is that the image you are using as well?

Our container registry scanner shows 325 Vulnerabilities  for in NodeJS based function container image. 23 of them are Critical and 46 are of high severity

@vasicvuk Which image was this?

@balag0 It is: mcr.microsoft.com/azure-functions/node:3.0

I can confirm this issue. We are using mcr.microsoft.com/azure-functions/node:3.0-node14-slim and ran it through WhiteSource, Snyk, Grype und Trivy - all of them report dozens of vulnerabilities. To verify, just run
docker scan mcr.microsoft.com/azure-functions/node:3.0-node14-slim

>>>

Tested 152 dependencies for known vulnerabilities, found 102 vulnerabilities.

We want to use these images in an enterprise setting, we cannot accept this amount of vulnerabilities in our images (or even begin analysing the potential impact of each one).
Is there a good reason to base these on Debian? Alpine seems to be a much better base image in regards to vulnerabilities.

@vasicvuk I ran the qualys scan on the node:3.0 image and the only issue reported was http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18276 and there is no patch available for that.

@balag0 which scanner are you using? I am getting results like @chlab does.

I can confirm the same for mcr.microsoft.com/azure-functions/python:3.0-python3.7 (also based on Debian) using trivy:latest:
473 LOW
94 MEDIUM
107 HIGH
29 CRITICAL
If needed i can provide the detailed scan results.

Hi,
Here are some more details on the question of @janvanuytrecht.
We see a lot of scanned images in Azure Security Center, with the same error as mentioned.
The score is impacted, so we must have a way to mitigate those issue and increase our score.
For more details you can check the screenshot below.

Is there a way you can update these images or we can mitigate it?
We don't want to exempt them in Azure Security Center, there must be another solution for this issue.

I'm a bit concerned with the lack of response about patching these vulnerabilities, most of them are Critical!
I don't see the commitment to keep security patching as a priority.
I tired a simple apt-get  update  and upgrade and of course is not enough.
Does Microsoft need a formal complaint about this? How can we help you guys to get priority on this?

Apologize for the delay in responding.

Looks like there is a bug in the publish pipeline where some of the recent updates haven't been pushed to the all the repositories.
This is the reason mcr.microsoft.com/azure-functions/python:3.0-python3.7 image reports more vulnerabilities than what is reported for the debian base image
Tracked by https://github.com/Azure/azure-functions-docker/issues/479

Regarding publishing alpine based images, this is a more involved change that needs updates to some of the language workers and we are looking into the possibility of doing this as well and provide an update soon.

Thanks for the update.
What about the vulnerability on the .net version?

On 12 Aug 2021, at 01:08, Bala G @.***> wrote:

Apologize for the delay in responding.
Looks like there is a bug in the publish pipeline where some of the recent updates haven't been pushed to the all the repositories.
This is the reason mcr.microsoft.com/azure-functions/python:3.0-python3.7 image reports more vulnerabilities than what is reported for the debian base image
Tracked by #479
Regarding publishing alpine based images, this is a more involved change that needs updates to some of the language workers and we are looking into the possibility of doing this as well and provide an update soon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Thanks for the update, I leave some facts (fresh ones) that make our Security Center very very red... and will spare more words as pictures will speak for themselves.
A simple docker scan gave the following results:

mcr.microsoft.com/azure-functions/dotnet:3.0-appservice
Docker scan result:

mcr.microsoft.com/dotnet/core/sdk:3.1
Docker scan result:

mcr.microsoft.com/azure-functions/python:3.0-python3.8-appservice
Docker scan result:

mcr.microsoft.com/azure-functions/python:3.0-python3.8-core-tools:
Docker scan result:

I hope this is shared with respective PG for priority assignment.

Thanks.
The issues in
mcr.microsoft.com/azure-functions/dotnet:3.0-appservice
mcr.microsoft.com/azure-functions/python:3.0-python3.8-appservice
are due to https://github.com/Azure/azure-functions-docker/issues/479
mcr.microsoft.com/azure-functions/python:3.0-python3.8-core-tools
was updated 3 days back. So it could have been after the above scan was run.
With the latest image, there is one high sev. vulnerability. But  that doesn't have a patch available yet. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18276)
The dotnet core image is unrelated to this repo. https://hub.docker.com/_/microsoft-dotnet-core might be a better fit.

Thanks @balag0,
for the python one, the scan was done on last Friday.
I'll update the image asap.
Thanks for the update

Thanks for the update!
I just run trivy on my machine for python:3.0-python3.8-core-tools and python:3.0-python3.7(-slim) but i cannot see a difference...
mcr.microsoft.com/azure-functions/python:3.0-python3.8-core-tools (debian 10.10)
Total: 934 (UNKNOWN: 0, LOW: 698, MEDIUM: 96, HIGH: 119, CRITICAL: 21)
mcr.microsoft.com/azure-functions/python:3.0-python3.7 (debian 10.9)
Total: 862 (UNKNOWN: 0, LOW: 572, MEDIUM: 125, HIGH: 120, CRITICAL: 45)
mcr.microsoft.com/azure-functions/python:3.0-python3.7-slim (debian 10.9)
Total: 506 (UNKNOWN: 0, LOW: 408, MEDIUM: 29, HIGH: 53, CRITICAL: 16)
Can anyone confirm that?

yes I do confirm
A terça, 17/08/2021, 16:13, Holger-Seemueller @.***>
escreveu:

Thanks for the update!
I just run trivy on my machine for python:3.0-python3.8-core-tools and
python:3.0-python3.7(-slim) but i cannot see a difference...
mcr.microsoft.com/azure-functions/python:3.0-python3.8-core-tools (debian
10.10)
Total: 934 (UNKNOWN: 0, LOW: 698, MEDIUM: 96, HIGH: 119, CRITICAL: 21)
mcr.microsoft.com/azure-functions/python:3.0-python3.7 (debian 10.9)
Total: 862 (UNKNOWN: 0, LOW: 572, MEDIUM: 125, HIGH: 120, CRITICAL: 45)
mcr.microsoft.com/azure-functions/python:3.0-python3.7-slim (debian 10.9)
Total: 506 (UNKNOWN: 0, LOW: 408, MEDIUM: 29, HIGH: 53, CRITICAL: 16)
Can anyone confirm that?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-functions-docker/issues/431#issuecomment-900386440,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM6OPV5X4BDZ25ML2ZUHYU3T5J4DNANCNFSM43GG66KQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Hi @balag0,
are there any new insights or can you explain the large differences between your and our scans?
Since the results differ so much i am afraid that there are maybe some misunderstandings or different approaches to scan the images?

Unfortunately don't have a lot of insights into how the different scans work. But I am working on adding a wiki page that explains the process we follow. (Should be ready in a day) Let us see if that can answer some of these questions.

Is the wiki page ready in the meantime?

Sorry for the delay. Added some details at
https://github.com/Azure/azure-functions-docker/wiki/Functions-image-release-process
Please let me know if that covers your questions.

I'm a bit stumped as to why Qualys seems to be reporting very little/no vulnerabilities and other scanners are showing >100. Does anyone have any insights on this? Is Qualys the only scanner that actually realizes that the vulnerabilites were patched?

To clarify a little bit, they are separate things. The functions images are expected to be released once every 2 weeks. Functions host releases may or may not be doing releases at the same frequency.
It is possible a new functions image is released with the same functions host version as the previous function image if there hasn't been a functions host release recently.

Hi! Here we have a bit of the same problem. We are trying to fix all the alerts coming from Azure Defender, among them we have "Container registry images should have vulnerability findings resolved" and we detected they are coming from azure functions images.

As I see this thread still open, I guess there is no solution, but is there something we can do about it?


Where implements "Reserves one task for signaling the queue is full."?

Where implements "Reserves one task for signaling the queue is full."?
I can't found it.
Is it unnecessary?

Not necessary to have a specific task.
The error checking is done in the add function.
Line 167-170 returns the error.


Update from puppet-community modulesync_configs

Don't merge just yet.

Tag @igalic.
It looks like mocha complains about the version of rspec or something. Do we need an enhancement to modulesync?
https://github.com/freerange/mocha/issues/130
https://gist.github.com/jyaworski/188bdbfbb13b43c17004

Updated the gems. Running into this: https://gist.github.com/jyaworski/73575fc0ff9da5e5692d

All right. @igalic this was downright painful.

Get rid of the gemfile.lock file? Maybe. As for the mapping thing, it was there when I got it. Not in the scope of the PR.

thanks so much for this effort @jyaworski!