POM files with direct reference to maven repositories

Issue:
I'm working on a company that only allow private maven repositories ( like nexus internal proxies ) .
I'm starting to see a public repository been called on my builds

 [ERROR] Failed to execute goal on project pipeline-app: Could not resolve dependencies for project
com.equifax.dfds.platform:pipeline-app:jar:20210618.2.ae73898: Failed to collect dependencies at org.apache.beam:beam-runners-google-cloud-dataflow-java:jar:2.30.0
-> org.apache.beam:beam-sdks-java-io-kafka:jar:2.30.0 -> io.confluent:kafka-avro-serializer:jar:5.3.2:
Failed to read artifact descriptor for io.confluent:kafka-avro-serializer:jar:5.3.2: Could not transfer
artifact io.confluent:kafka-avro-serializer:pom:5.3.2 from/to io.confluent (https://packages.confluent.io/maven/):
Connection reset -> [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal on project pipeline-app: Could not resolve dependencies for project com.equifax.dfds.platform:pipeline-app:jar:20210618.2.ae73898:
Failed to collect dependencies at org.apache.beam:beam-runners-google-cloud-dataflow-java:jar:2.30.0
-> org.apache.beam:beam-sdks-java-io-kafka:jar:2.30.0 -> io.confluent:kafka-avro-serializer:jar:5.3.2

!image-2021-06-18-14-36-36-437.png!
!image-2021-06-18-14-36-45-842.png!
Has part of the ticket, a repository has been added directly to the generated pom.
This repository should be configured by users that want to compile the code... not pre-configured/ forced on the pom file.
https://issues.apache.org/jira/browse/BEAM-9292
Now exit this element on the pom

<repositories>
  <repository>
    <id>io.confluent</id>
    <url>https://packages.confluent.io/maven/</url>

 </repository>
</repositories>

https://repo1.maven.org/maven2/org/apache/beam/beam-sdks-java-io-kafka/2.30.0/beam-sdks-java-io-kafka-2.30.0.pom
VS
https://repo1.maven.org/maven2/org/apache/beam/beam-sdks-java-io-kafka/2.19.0/beam-sdks-java-io-kafka-2.19.0.pom

dependencies added here
!image-2021-06-18-14-55-41-740.png!
https://github.com/apache/beam/commit/f2cc92663ad8ae685183e076cdb652d8fc3ba4e0
Imported from Jira BEAM-12510. Original Jira may contain additional context.
Reported by: abelmatos.

Hi, I am facing the exact same problem. Our company only allows for dependencies from maven central.
What makes matters worse is that excluding the dependencies makes the Kafka SDK unusable:
 implementation("org.apache.beam:beam-sdks-java-io-kafka:2.40.0") {
      // These artifacts are not in maven central! The sdk cannot be used without them :(
      exclude group: "io.confluent", module: "kafka-avro-serializer"
      exclude group: "io.confluent", module: "kafka-schema-registry-client"
   }

Because the Kafka SDK is unusable without the Confluent dependencies you also have to exclude it from the Dataflow runner:
   runtimeOnly("org.apache.beam:beam-runners-google-cloud-dataflow-java:$beamVersion") {
        exclude module: "beam-sdks-java-io-kafka"
   }

This is not a problem when running batch pipelines in Dataflow. However, the moment you try running a streaming pipeline, it will fail with:
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/beam/sdk/io/kafka/KafkaIO$Read

I saw this exception when trying to run a streaming pipeline attached to PubSub, e.g. my pipeline had absolutely nothing to do with Kafka. This must be a bug in the Dataflow runner itself. The problem is discussed in this email thread.

This is resolved by #30300. Tested that Dataflow v1 streaming pipeline no longer have io-kafka and nor io.confluent dependencies


Read branch from the var for rancher images generation

https://github.com/rancher/rancher/issues/20696

LGTM


Change license to Apache 2.0

Make the following changes after source code changes have been merged.

[ ] Remove COPYING (GPLv3)
[ ] Add LICENSE (Apache-2.0)
[ ] Update README badge
[ ] Update README license text
[ ] Update license text in each source file

For the record, feel free to relicense any contributions I've made under any Open Source license.

When I originally wrote ModbusMaster, it was partly to solve a problem (extract real-time data from a PLC), and partly as an exercise in learning. I was inspired by and borrowed concepts from Arduino Modbus Master. I believe in Open Source Software and the concept that sharing/applying ideas from multiple contributors make a better overall product.
This library is successful when people use it to solve real-world problems and contribute their improvements to the project. It may be used in open source, public domain, private, or commercial projects. When someone links to this library, it becomes a derivative work of this code. The GPLv3 requires distribution of this combined work to be covered under GPLv3 or other compatible license. The Apache 2.0 license is more appropriate for this project because it is more open with respect to distribution of derivative works, as compared to GPLv3. Therefore, as of v0.12.0, I'm changing the project's license from GPLv3 to the less restrictive Apache 2.0 license.


Add semantic chunking pipeline

Evaluate using the Chonkie library to add more sophisticated chunking to txtai.
In reviewing the code, it appears that an interface wrapping a txtai vectors instance could be passed in. With this, any supported txtai vectors model (huggingface, sentence-transformers, LiteLLM, llama-cpp etc) could be used.

Docling also has some chunkers that are worth considering: https://ds4sd.github.io/docling/examples/hybrid_chunking/


null-safetey

Do you plan to upgrade this package to the new null-saftey?

open_appstore:
    git:
      url: https://github.com/ChangJoo-Park/flutter_open_appstore.git
      ref: master

Yes this is really needed


[Test-Proxy] Add conditions for ContentType and Request vs Response

Right now there is no way to apply body regex sanitizers to only the request or a response body. This makes it difficult to come up with a regex that works for both when the content type differs.
We should consider adding ContentType to the supported conditions, in addition to potentially specifying Request vs Response.

/cc @schaabs


Websocket name from session

Added support for websocket names based on Session contents
Added missing charset param in PebbleBenchmark.scala

Thanks a lot for the review. I changed it according to your suggestion.

Thanks a lot for the review. I changed it according to your suggestion.

Thanks! Could you please sign our CLA?
Also, could you please fix the commit history and squash into a single one on top of master? If you really can't do that, I'll take care of it.
Cheers

Thanks! Could you please sign our CLA?
Also, could you please fix the commit history and squash into a single one on top of master? If you really can't do that, I'll take care of it.
Cheers

@slandelle I messed up with the squash & rebase. I'm now creating another pull request with a clean branch. Sorry for the inconvenience

@slandelle I messed up with the squash & rebase. I'm now creating another pull request with a clean branch. Sorry for the inconvenience


Human readable QR

This pr resolves #646
The key changes is the addition of the new metadata entry in the VerificationConfig that can contain the title of the verification and the claims it verifies. Here an example of the UI change on mobile.

and for desktop

I think this should work well!
The only thing is that - at least to me - the alignment of the new paragraph seems to be off when compared with the rest of the page (which seems to be more centered). Is it true or are my eyes tricking me into seeing that?

This is the alignment, so paragraph left justified. Think center justifying it would then have multiple list items looking weird, so if that were the case think it would be centering just the paragraph (but then having to offset each list item so they line up)

Are we just adding a language array to the claims and not the title?

Are we just adding a language array to the claims and not the title?

I somehow missed that, good catch. We should add the same language mapping to the title - maybe we should have the language map as the root element with language and title both nested within it @Gavinok

Added support for titles thanks for pointing that out. Should have just added that to begin with.


Add variable linecolor

Currently the linecolor parameter is fixed for all lines. There's no reason not to make it behave like textcolor so users can do things like make these lines match the colour of the objects they point to.
I also noticed then that the colours appeared random when setting the seed, and this was due to them not being shuffled with the other parameters when given a seed so I fixed that too.

Very nice, thank you for the feature and the fixes!


Changing Prop validation to make it work with jest

Making changes to Prop validation as tests were failing with Jest. Please review and let me know if there any better way to get around the following error
"TypeError: Cannot read property 'style' of undefined"

Looks good to me. Will release it ASAP.


Add clarity to overrides page

Added clarity that changing overrides after XP start can pollute results.

🚀 Deployed on https://6663448274013c06f76bea22--cozy-fox-0defec.netlify.app


fix(valuecard): handle null units in flyover

Summary

small fix to handle undefined units

Acceptance Test (how to verify the PR)

Check the value card flyover with undefined units

:tada: This PR is included in version 1.60.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.60.0 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


truth table from circuit

we can convert a circuit to a unitary, but not to truth table yet. This will be useful for checking classical circuits (oracles, arithmetic, etc.)

Hi! I'm new at this, but would like to try this one. Just not sure how to represent superpositions as a truth table, for example a 1qubit circuit with an H-gate on q0?

I think this should only work for classical circuits (circuits consisting of X and controlled versions of X like CX, CCX, etc.) Although other circuits may exist that have other gates and are yet classical, I think to start we can just raise an error if a truth table is requested for other circuits.
It will be nice to then have a truth table synthesis method as a follow-on. I think the oracle synthesis code can be used there.

For anyone interested, I can help with this just this short project.
After giving some thought on how to go about implementing this, I came up with the following points to be aware of

First, as you mentioned, we must use a classical reversible gate set, i.e., X and its controlled versions + Swap
More importantly, we need to clarify one point: When you say truth table, Are you referring the truth table representing the reversible logic function implemented by the circuit, or the truth table of an (possibly) irreversible function that might have been embedded into a reversible one to be made into a circuit?

I know, this first concern might be quite confusing, so let me illustrate with an example. Take the following circuit
  ╭───╮╭───╮╭───╮
0 ┤ x ├┤ x ├┤ x ├ f(a,b,c)
  ╰─┬─╯╰─┬─╯╰─┬─╯
a ──◯────◯────●── a
    │    │    │
b ──●────┼────●── b
    │    │
c ──◯────●─────── c

This circuit implements a reversible Boolean function rev(0, a, b, c) -> (f(a,b,c), a, b, c).  You can represent its functionality using four truth tables. (Or one four-output truth table.) But clearly there is something else there. You have a function f embedded into this reversible function, i.e., you took an (possibly) irreversible Boolean function and made it into a reversible one.
So are you interested in the truth table of rev or f?
Keep in mind that, despite what my simple example might indicate, if you are looking for f, things might be much more complicated.

Then there a few technical concerns on how to represent truth tables.

I think it would be kind of interesting to find truth table for f, but I don't really know how to extract that from a given circuit. Here I just meant the simple case of given an n-qubit circuit, give me the 2**n-entry truth table.

I think classical circuits become so called Permutation matrices when represented in matrix form. This then means we check for only one 1 entry per column, and its location index is the circuit output.
I have tried this out with X, CX and CCX so far, please check it out here.
Maybe this is close to what we want?

Has this issue been solved?


TFLite - enable XNNPACK with dynamic shapes of tensors

System information

TensorFlow version (you are using): 2.3.0
Are you willing to contribute it (Yes/No): No

Describe the feature and the current behavior/state.
In 2.3.0, dynamic shapes  were fixed in TFLite ("TFLite now properly supports dynamic shapes during conversion and inference."). We can now process tensors with varying batch size, everything works, great.
However, running on Windows 10 64b, the processing is slower than base TF2. Using TFLite with XNNPACK and fixed batch size 1, the processing is about 2x faster than with base TF2. So the final difference is about 3x in latency. My request is to enable XNNPACK Delegate to process dynamic shaped tensors to enjoy fast processing with variable batch size.
Will this change the current api? How?
No.
Who will benefit with this feature?
Anyone wishing to process batches of images of various size.
Any Other info.

Hi @svobora, we do not currently plan to support tflite dynamic shapes, https://www.tensorflow.org/lite/guide/inference. If you have no more open items please feel free to close the issue as not planned.


Introducing tagged releases and uploading them to pypi

Hi @Tomme !
Great work on the adapter, it works like a charm and it's awesome to see you're continuing to add new features!
However, the non-standard way of installing your adapter directly from github makes deterministic and verified installs of the adapter a little cumbersome, and makes us hesitant of bringing it into production, even though our Analytics Engineers would love to use dbt to build and maintain Athena tables.
I'm wondering, do you have plans to introduce tagged releases and publish the package to pypi?
This would make using and integrating the adapter into our python environments much easier, since users can easily specify pinned sets of python dependencies and test against them, or revert to older version sets if things no longer work/
It seems the pypi package that @lsaletti published under to the name dbt-athena has been abandoned, and its git repository has been deleted, however the info page on pypi links to your project with a recommendation to use it.
Have the two of you been in contact or talked about a potential transfer of the pypi project?
Even if a transfer of the pypi project is not possible or desired, I believe most users would be totally fine with installing your adapter using a new name, if it becomes possible to install versioned releases from pypi. For example dbt-athena-adapter is still free as of now.
Please let me know if I can support in any way.

Any comment about this?

also bumping that I'm willing to support this effort as the in-house adapter nerd at dbt Labs. I know open-source maintenance can feel like a burden sometime given everything else we have in life, so please reach out with how (I) we can help!
For example, at any time any person can upload this package to PyPI in their own project with whatever still-available name they want. I learned how to publish to PyPI with this guide and I still open it every time I need to publish a new version.
It actually seems to be what @vanducng is doing with vdn-tools/dbt-athena2, just renaming the code and publishing it manually to PyPI as dbt-athena2.
cc: @Tomme @theister @Gatsby-Lee @Dandandan

@lsaletti, would you be amenable to adding @nialloriordan and @Tomme as owners on the dbt-athena PyPI package? For me this is the utopia goal as it's simpler and in alignment with the other adapters.

Change the package name as previously mentioned to dbt-athena-adapter or contact the current owner of dbt-athena in pypi to transfer ownership to you, or delete the old package in pypi and upload the new one. If it is not possible to get in contact with the owner, you can also open a request and ask pypi to change ownership to you. There is an example here: https://github.com/pypa/pypi-support/issues/425#issuecomment-724078630

@Tomme I'm also happy to help with this! How to Publish an Open-Source Python Package to PyPI is the guide i used to learn how to push releases to PyPI (and I still refer to it every time I'm uploading new versions)

Create a release on the github repo

Create a pypi account: https://test.pypi.org/account/register/

Install build and twine: pip install build twine

Build the package: python -m build

check the package: twine check dist/*

upload the package: twine upload dist/*

Sorry this took so long but we are now publishing to PyPi #119 🥳

hekkin' yeah! @Tomme does https://github.com/dbt-labs/docs.getdbt.com/pull/1856 reflect the change accurately to you?


[BUG] JindoRuntime's FUSE sidecar failed to start

What is your environment(Kubernetes version, Fluid version, etc.)
Describe the bug
For example, given a common dataset and jindoruntime. Create a pod with the following spec:
apiVersion: v1
kind: Pod
metadata:
  name: nginx
  labels:
    serverless.fluid.io/inject: "true"
spec:
  containers:
    - name: nginx
      image: nginx
      command:
      - "bash"
      - "-c"
      - "sleep inf"
      volumeMounts:
        - mountPath: /data
          name: data-vol
  volumes:
    - name: data-vol
      persistentVolumeClaim:
        claimName: demo-dataset

where claimName: demo-dataset is the name of the JindoRuntime.
The pod will crash with following error messages in the events:
Warning  FailedPostStartHook  0s    kubelet            Exec lifecycle hook ([bash -c time /check-mount.sh /jfs/jindofs-fuse jindo  >> /proc/1/fd/1]) for Container "fluid-fuse-0" in Pod "nginx_default(ec97b179-b359-4645-ab6b-e6259cf5510c)" failed - error: command 'bash -c time /check-mount.sh /jfs/jindofs-fuse jindo  >> /proc/1/fd/1' exited with 2: + ConditionPathIsMountPoint=/jfs/jindofs-fuse
+ MountType=jindo
+ SubPath=
+ count=0
+ cat /proc/self/mountinfo
+ grep /jfs/jindofs-fuse
+ grep jindo
+ sleep 3
++ expr 0 + 1
+ count=1
+ test 1 -eq 10
+ cat /proc/self/mountinfo
+ grep /jfs/jindofs-fuse
+ grep jindo
+ '[' '!' -e '/jfs/jindofs-fuse/*/' ']'
+ echo 'sub path [] not exist!'
+ exit 2

real  0m3.332s
user  0m0.005s
sys   0m0.007s
, message: "+ ConditionPathIsMountPoint=/jfs/jindofs-fuse\n+ MountType=jindo\n+ SubPath=\n+ count=0\n+ cat /proc/self/mountinfo\n+ grep /jfs/jindofs-fuse\n+ grep jindo\n+ sleep 3\n++ expr 0 + 1\n+ count=1\n+ test 1 -eq 10\n+ cat /proc/self/mountinfo\n+ grep /jfs/jindofs-fuse\n+ grep jindo\n+ '[' '!' -e '/jfs/jindofs-fuse/*/' ']'\n+ echo 'sub path [] not exist!'\n+ exit 2\n\nreal\t0m3.332s\nuser\t0m0.005s\nsys\t0m0.007s\n"
  Normal   Killing            0s  kubelet  FailedPostStartHook
  Warning  FailedPreStopHook  0s  kubelet  Exec lifecycle hook ([/prestop.sh]) for Container "fluid-fuse-0" in Pod "nginx_default(ec97b179-b359-4645-ab6b-e6259cf5510c)" failed - error: command '/prestop.sh' exited with 137: , message: "excute jindofs-fuse umount\nFLUID_FUSE_MOUNTPOINT = /jfs/jindofs-fuse\n"
  Normal   Pulling            0s  kubelet  Pulling image "nginx"

What you expect to happen:
Pod should launch with no error.
How to reproduce it
Additional Information

The cause is check-mount.sh checks an incorrect mount path /jfs/jindo-fuse/*/. If there are no directories(only files) in the mounted file system, /jfs/jindo-fuse/*/ fail to parse as any valid path so that the script fails.


plocate: add SuperSandro200 to maintainers

@ean should I add you, too?
Motivation for this change
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@SuperSandro2000 You can leave me out for now, for the moment I am doing this as a learning exercise.


[opt](single compaction) use cooldown to determine the primary replica

Proposed changes
Issue Number: close #xxx

run buildall

run buildall

run buildall


Merge reload methods into init methods

They do almost the same thing. We can make them do the exactly same thing and get rid of reload.

Thanks


Option to NOT remember previously opened files

Feature request for the opposite of #1603 (not to reverse it, but to add an option to disable it).
Currently: Atom will reopen files that were not closed from last time (within the same project)
Desired: An option to disable this, so that no additional files are opened when Atom starts
There is currently a hack for this, however, a configurable setting would be much more appropriate.
Using: Atom 0.198.0 on Linux
Thanks

Thanks for the suggestion! This is a duplicate of https://github.com/atom/atom/issues/6605 – please subscribe there for updates.


Memory multi-channel detection not working correctly.

HWiNFO v8.14 screenshot for proof.

Thank you for opening this issue!
This should be addressed in #76 Have you happened to copy and paste the code to PowerShell or Terminal and see if it works correctly now by chance?
https://github.com/helldivers2fixes/HellbombScript/blob/9cdb16d8a4f2af49f938249b73178e19fb25d570/Hellbomb Script.ps1

I tried again both directly on PowerShell and last .exe release, and now seems to work as intended.


cmd/compile: internal compiler error: panic: runtime error: index out of range [0] with length 0

What version of Go are you using (go version)?

$ go version
go version go1.18 windows/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\demo\AppData\Local\go-build
set GOENV=C:\Users\demo\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\demo\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\demo\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.18
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=C:\development\github.com\blaubaer\demo
set GOWORK=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\demo\AppData\Local\Temp\go-build2763200917=/tmp/go-build -gno-record-gcc-switches

What did you do?
I was using the following code (https://go.dev/play/p/KwmzJ6V1JwN)
package main

import (
	"errors"
	"log"
)

var (
	ErrEof = errors.New("end of iterator reached")
)

type empty[T any] struct{}

func (this *empty[T]) Next() (empty T, _ error) {
	return empty, ErrEof
}

func doSomethingWithIterator[T any](what interface{ Next() (T, error) }) {
	v, err := what.Next()
	if err != nil {
		log.Fatalln(err)
		return
	}
	log.Println(v)
}

func main() {
	i := &empty[string]{}
	doSomethingWithIterator[string](i)
}

What did you expect to see?
The code compiles and run.
What did you see instead?
# github.com/blaubaer/demo
.\demo.go:29:33: internal compiler error: panic: runtime error: index out of range [0] with length 0

Please file a bug report including a short program that triggers the error.
https://go.dev/issue/new

Thanks for reporting this. tip is also affected.
cc @randall77 @danscales

This appears to be due to confusion between empty, the generic type, and empty, the local variable of the Next function. The code thinks it is trying to get the type parameters of the former, but it is in fact trying to get the type parameters of the latter, which fails.
Not sure why yet.

This appears to be due to confusion between empty, the generic type, and empty, the local variable of the Next function. The code thinks it is trying to get the type parameters of the former, but it is in fact trying to get the type parameters of the latter, which fails. Not sure why yet.

The problem is that noder will store the symbol of the generic base type. But the symbol declaration maybe changed when re-declaring variable with the same name. So the code:
origRParams := deref(orig).OrigSym().Def.(*ir.Name).Type().RParams()

will return wrong type parameters.

@gopherbot backport to Go 1.18; this is a compiler bug that could theoretically lead to silent miscompilation of valid user code

@gopherbot please backport to Go 1.18; this is a compiler bug that could theoretically lead to silent miscompilation of valid user code


Error behaviour details

Posting a summary from the modules meeting today:

The current spec will not error for importing a deferred module which is already in an errored state. It might be worth making this case error early.
If importing a sync module that imports an async module, it is possible for that sync module to be queued for execution by the time the promise completes either by an existing or future top-level evaluation. If we think of this in the same light as (1) above, the question then is whether the sync failure should also fail the deferred import as it can be known that the failure happened before the deferred import statically completes. If the sync module was already queued for execution we can directly attach to its completion. But if the sync module is only queued for execution later that case would be harder to track, since deferred attachments statically skip their graph components. An approach to this might be possible in the async fulfillment handlers to perform defer rejection when a defer parent "happens to be found".

In discussion we felt that (1) and (2) might be worth handling. Writing it up now I'm wondering if we should only consider (1) due to the complexity of (2), although it could be possible.
Further to the above, there is also the question of whether deferred namespaces should throw for every access or not when the module is in an errored state. There was tentative agreement on only the executor call being the one to throw.

@nicolo-ribaudo happy to review any further PRs along these lines. Alternatively I'd be happy to propose some spec text if that would help, both for (1) and (2), just let me know what works best.


Replace the term dryrun with validate within create workflow api

Currently, create workflow api has a dryrun parameter that allows customer to do a format validation check before indexing the template. When dryrun=true, we will create if the validation passes. Now based on the conversion in this pr, we have these two proposals:

change the term dryrun with validate
don't create when the parameter is set to true, only perform validation check

OK, after taking some time to think on this

"dry run" can sometimes imply validation but not always. It's appropriate for a "check to see if this works without actually doing it" for an API where "actually doing it" is the norm.  It's roughly synonymous, but there are a vew implied differences

"dry run" is added when we are by default always doing validation, as an option to not do the validation, so is appropriate if validation is the default outcome (this is our case)
"validate" is often added when we are by default not doing validation, so is appropriate if not validating is the default outcome, but it's also equally possible to default "on" and allow turning it off.

There's a more important connotation of "dry run" in that "you don't actually do the thing the API implies".  So I would expect:

for a "create" API, dry run means I don't create it, I just validate if creation would have been successful
for a "provision" api, dry run means I don't provision, I just validate if creation would have been successful
for a combo create+provision API, it is ambiguous

Then there's the user perspective:

Generally by default I don't want to save an invalid template

But sometimes during "WIP" editing situation I do want to save an invalid template.  I've been frustrated in the past with "precommit hooks" that don't even let me commit changed files in git if they don't pass the various validation checks, but I often want to just "save a spot I can come back to".

I think the situation should generally be:

always do validation and fail fast with no action if it fails
allow the user to override this default validation and do things like creating an (invalid) template.

this seems to call out for a "validate=false" param, which is what prompted my original comment.  "dryrun=false" doesn't seem to make sense.

Related: Maybe we need to add a field to the saved template that says it's invalid, so we don't provision it.

this seems to call out for a "validate=false" param

Leading to create API:

validate=true (default), provision=false (default):  validates and saves only if successful
validate=false (override), provision=false (default):  does no validation, saves
validate=true (default), provision=true (override):  validates and saves only if successful, then provisions
validate=false (override), provision=true (default):  does no validation, saves, attempts to provision, provisioning may fail.  User runs at their own risk. This is a reasonable choice for a debugged template used by automation.

Closed in #308


[DOCS-2104] Remove 'beta-' references w/i stable docs

Remove 'beta-' references w/i stable docs, ensuring that the removals
are contextually correct (mostly package name and DC/OS CLI service
name).

This change was performed incorrectly w/ master as the base, should've been 0.30.X


[BUG] Can't use default emojis in SelectOption

Describe the bug.
Not sure if this is a bug or a feature request.
Currently I retrieve random emojis from emojipedia and pass them as arguments to the 'emoji' parameter when I create a new SelectOption, though I have tried hardcoding a single emoji to test and I get the same issue.
I know that I'm supposed to pass an Emoji object with a _json attribute to the 'emoji' parameter, but if I'm using default emojis then I'm expected to copy and paste symbols or use the standard colon notation with a dictionary of emoji names.
Maybe I've just misunderstood something but is there some way using only the interactions library that I can create an Emoji object from a string like '😃' (or any other format where I start without an ID), or is there a workaround to implement SelectOption and just use an emoji as a string like that?
List the steps.
For simplicity, I've only included a hardcoded version of the data I would like to use (or something equivalent) when creating a SelectOption object.
option = {
	'label': emoji_name,
	'value': x,
	'emoji': '😃'
}

What you expected.
It should be possible to pass emojis directly to SelectObject options should yield a result, or provide some hint on constructing an Emoji object. Or, it should be possible to retrieve the standard emojis using the interactions library natively.
What you saw.
Currently it only appears that a SelectOption can be created natively by relying on custom emojis or using an external request/library to query the discord API
What version of the library did you use?
release
Version specification
4.1.1-rc (also tested on stable version, yields slightly different result. same issue)
Code of Conduct

[X] I agree to follow the contribution requirements.

Try using SelectOption(...,, emoji=interactions.Emoji(name="your_emoji_here").
Also, you might want to check out our discord support server

It'd probably help if you gave us a code example of what you were trying to originally do with Emoji(). The correct functionality for partial emoji objects in a select menu option is this
interactions.SelectMenu(
  options=[
    interactions.SelectOption(
      label="my label",
      value="test1",
      emoji=interactions.Emoji(id=None, name="😊", animated=False)
    )
  ]
)

Thanks I just hadn't realised how to create a partial Emoji!


Zoom not working after postDelayed()

Here is code example:
showMap() {
tileView.setBitmapProvider(new CustomBitmapProvider());
tileView.setSize(4000, 4000);
tileView.defineBounds(0, 0, 1, 1);
tileView.addDetailLevel(1f, "Schema.png", 4000, 4000);
}
onCreate(){
showMap();
}
Zoom is working.
onCreate(){
tileView.postDelayed(new Runnable() {
@Override
public void run() {
}
}, 3000);
}
Zoom is not working!
mScaleGestureDetector.getScaleFactor() in ZoomPanLayout always 1
How can i solve this problem?

i don't really follow your code...  you're not doing anything in the run method...
also i don't see where you're adding the TileView instance to the view tree at all...
also getScaleFactor is going to be the scale during a pinch operation, are you sure you don't want to just examine getScale form the TileView itself?
if possible post the minimum viable code needed to recreate your problem

showMap() {
tileView.setBitmapProvider(new CustomBitmapProvider());
tileView.setSize(4000, 4000);
tileView.defineBounds(0, 0, 1, 1);
tileView.addDetailLevel(1f, "Schema.png", 4000, 4000);
}
onCreate(){
tileView = (TileView) findViewById(R.id.tileView);
tileView.postDelayed(new Runnable() {
@Override
public void run() {
showMap();
}
}, 3000);
}
I.e. we have problem, if call showMap() not sync.
Updated info:
If we set call tileView.setSize(someWidth, someHeght) directly after finding view, then tileView.setSize(4000, 4000) in showMap() will no effect:
Zoom is not working because i don't call setSize before tileView.postDelayed(), and tileView thinks, that image is small (0,0).
But if i call tileView.setSize(10000, 10000) directly after finding view, but then tileView.setSize(300, 300) in  showMap(), then it'll be zoomed as image 10000x10000

i'll mark this is as a bug and investigate when i can, but in the meantime, try calling resume() after setSize and post back if that helped or not
thanks

The problem was that minimumScaleToFit was only calculated when there was a change to layout.  This has been corrected, and version 2.0.2 should fix the problem you're describing.  You can get the latest master branch from this repo, or compile to 2.0.2.
I'll leave this ticket open for your confirmation.
Thanks for posting.

Good!
It's fixed


Words without spaces aren't filtered

If I put many words together without spaces it doesn't filter them.

Kind of defeats the purpose of this package...

This is a bummer! now noticed this happens... sigh

yup

I made a simple function that fixes it:
function cleanBadWords(s, filter = badWordsFilter) {
  s = s.replace(/\u200B|\u200C|\x00/g, '');

  for (const swear of filter.list) {
    if (filter.exclude && filter.exclude.includes(swear.toLowerCase())) {
      continue;
    }

    s = s.replace(
      new RegExp(
        swear.replace(/([\.\*\-\\\/\?\+\{\}\[\]\|\(\)])/g, '\\$1'),
        'gi'
      ),
      '*'.repeat(swear.length)
    );
  }

  return s;
}
``


Resource Tools

Hi,
Dose the new version (1.x) work with Tools?
/Tim

Yeah! but you need to define the router name/params/query manually using the RawResource
RawResource::make([
    'label' => 'Your Tool',
    'name' => 'ROUTER_NAME',
    'params' => [ 'foo' => 'bar' ],
    'query' => [ 'foo' => 'bar' ],
])

Thank you!


DURABLE_REDUCED_AVAILABILITY support missing

DURABLE_REDUCED_AVAILABILITY is a legitimate (though discouraged) value for StorageClass.
The current enum in google-cloud-java does not include a value for DURABLE_REDUCED_AVAILABILITY so we crash when the server's reply contains this value.
We should add the value to the enum.
See this bug report for an example of someone running into this problem.

Fix merged in, closing.


mAP (medium) and mAP (large) =-1

In the results of my experiment, both mAP (medium) and mAP (large) are -1，but in the dataset I used, there are objects with size greater than 32*32，why？

Hi, @zjmlovlin Maybe you can visualize the results first? If there is no predicted result about a medium object, then mAP are -1.


satisfy lints

Seems like I broke CI, didn't expect it to be set to -D warnings

@Ryex ci still broken, same error I got on windows in #8
https://github.com/Ryex/ic10emu/actions/runs/8543415993/job/23407199310#step:6:64


CSS in header

Hello,
I'm trying to include a css resource using the Head component (it's a large css file, so I don't want to use glamor)
<Head>
  <meta charSet='utf-8'/>
  <meta name='viewport' content='initial-scale=1.0, width=device-width'/>
  <link rel="stylesheet" href="/static/css/application.css"/>
  <script defer src="/static/js/application.js"></script>
</Head>

Unfortunately by doing so, when I navigate to another page, the css gets unloaded and then loaded again causing the UI to kinda "flicker".
What's the NextJS way to deal with that use case?
Thank you.

It seems that the flicker is a bug. It shouldn't happen :(

I solved the flicker bug by this method:
In your server side code:
api.get('/style', (req, res) => {
  res.send(`
    body {
      background: #eee;
      margin: 0;
    }
  `.replace(/\s{2,}/g, ''))
})

and in every of your pages:
static async getInitialProps ({ req }) {
  const isServer = !!req
  const host = isServer ? req.headers.host : location.origin
  const stylesheet = await (await fetch(host + '/api/style')).text()
  return {
    isServer,
    stylesheet,
  }
}

render () {
  return (
    <div>
      <Head>
        <meta charSet="utf-8" />
        <meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,user-scalable=no" />
        <style dangerouslySetInnerHTML={{ __html: this.props.stylesheet }} />
      </Head>
    </div>
  )
}

really?? On every page?? We don't have a way to customize the html Next uses?

We do, it's on the ReadMe here: https://github.com/zeit/next.js#custom-document


Problem composer

Hello i have problem to install. Beforre instaled and all work ok bu when changed folder and tray again to install from beiggining a have error when execute php composer.phar dumpautoload
Deprecation warning: Your package name TAD-PHP is invalid, it should have a vendor name, a forward slash, and a package name. The vendor and package name can be words separated by -, . or _. The complete name should match "a-z0-9/a-z0-9". Make sure you fix this as Composer 2.0 will error.

Sorry but by same mistake reader reseted to default and change ip.
All work ok


Updated changelog.

This is not a good way to update the change log. Hopefully there's a better way than creating a pull request every time.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_6fyrjseqy3/clone/recipe/meta.yaml:25: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_6fyrjseqy3/clone/recipe/meta.yaml:33: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_6fyrjseqy3/clone/recipe/meta.yaml:37: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: BSD-3-Clause
WARNING: /tmp/abs_6fyrjseqy3/clone/recipe/meta.yaml:42: missing_description: The recipe is missing a description
Errors were found


Security: script injection via property! (drop-6)

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Enhancement / Suggestion
[ ] Additional article idea

Expected or Desired Behavior
The Yeoman-Template "No javaScript web framework" should build a secure by default web-part (no html/script injection). If you input HTML-/JavaScript-code it should be displayed but not interpreted.
Observed Behavior
If you edit the description-property, you can insert HTML-/JavaScript-code and it is interpreted/displayed in the WebPart.
Steps to Reproduce
This only occurs if you choose the Template "No javaScript web framework".
The React/Knockout-Templates do not have this problem.
I use the current drop (SharePoint Framework Developer Preview Drop 6).
I have not tested this on a developer tenant in the cloud (only local workbench).

Create a new HelloWorld-Project (Template: "No javaScript web framework")
Run it (gulp serve)
Local Workbench: Edit web-part properties
Change description to:

<button onclick="alert('script injection possible')">Try it now</button>

Click the button "Try it now" (on the web-part)

Thoughts
I haven't tested this in the cloud (developer tenant) as i don't have an account. It could be that this only happens if you run it in the local workshop.
If you are using knockout/react you don't have this problem.
This could be by design by the spfx team, but it should at least be documented in the generated source code that this vulnerability exists (if you do not use any js web framework) - and some hints how to handle this if you do it on your own.

Yup - completely correct.  We need to take a global pass through everything (samples, labs, templates, etc.) to handle this.  We're doing this as part of some additional work around persisting rich content (HTML) that has the same server support for scrubbing HTML, since you can't really html encode your html.

Tested it on a developer tenant with a debug release (spapp upload - code running on my machine).
When I am editing the property the html/js is interpreted.
It does get scrubbed when I view it on the page (normal mode).

Seems to be fixed with RC0 👍

@tortoise386 Excellent! In that case, can you close the issue! Thanks!

Only tested it in the local workbench. Closing the issue.


[BUG] Unable to find version '17'

Is there an existing issue for this?

[X] I have searched the existing issues

Does this issue exist in the latest version?

[X] I'm using the latest release

Describe the bug?
I believe I am using the most recent version tj-actions/verify-changed-files@17. This command ran as expected this time last month, but this time it failing from:
build
Unable to resolve action `tj-actions/verify-changed-files@17`, unable to find version `17`

The most recent version is 17.1.0, does it no longer accept 17 as a version number like in the documentation?
To Reproduce

Ubuntu-20.04 github action
Script, line 42

Unable to resolve action `tj-actions/verify-changed-files@17`, unable to find version `17`

What OS are you seeing the problem on?
ubuntu-20.04
Expected behavior?
Github Actions does not recognize version 17, but ran as expected a month ago. Is the syntax different than the documentation to work with the newest release?
Relevant log output
##[debug]Starting: Set up job
Current runner version: '2.312.0'
Operating System
Runner Image
Runner Image Provisioner
GITHUB_TOKEN Permissions
Secret source: Actions
##[debug]Primary repository: unaschneck/pydar
Prepare workflow directory
##[debug]Creating pipeline directory: '/home/runner/work/pydar'
##[debug]Creating workspace directory: '/home/runner/work/pydar/pydar'
##[debug]Update context data
##[debug]Evaluating job-level environment variables
##[debug]Evaluating job container
##[debug]Evaluating job service containers
##[debug]Evaluating job defaults
Prepare all required actions
Getting action download info
Error: Unable to resolve action `tj-actions/verify-changed-files@17`, unable to find version `17`
##[debug]GitHub.DistributedTask.WebApi.UnresolvableActionDownloadInfoException: Unable to resolve action `tj-actions/verify-changed-files@17`, unable to find version `17`
##[debug]   at GitHub.Services.WebApi.VssHttpClientBase.HandleResponseAsync(HttpResponseMessage response, CancellationToken cancellationToken)
##[debug]   at GitHub.Services.WebApi.VssHttpClientBase.SendAsync(HttpRequestMessage message, HttpCompletionOption completionOption, Object userState, CancellationToken cancellationToken)
##[debug]   at GitHub.Services.WebApi.VssHttpClientBase.SendAsync[T](HttpRequestMessage message, Object userState, CancellationToken cancellationToken)
##[debug]   at GitHub.Services.WebApi.VssHttpClientBase.SendAsync[T](HttpMethod method, IEnumerable`1 additionalHeaders, Guid locationId, Object routeValues, ApiResourceVersion version, HttpContent content, IEnumerable`1 queryParameters, Object userState, CancellationToken cancellationToken)
##[debug]   at GitHub.Runner.Worker.ActionManager.GetDownloadInfoAsync(IExecutionContext executionContext, List`1 actions)
##[debug]   at GitHub.Runner.Worker.ActionManager.GetDownloadInfoAsync(IExecutionContext executionContext, List`1 actions)
##[debug]   at GitHub.Runner.Worker.ActionManager.PrepareActionsRecursiveAsync(IExecutionContext executionContext, PrepareActionsState state, IEnumerable`1 actions, Int32 depth, Guid parentStepId)
##[debug]   at GitHub.Runner.Worker.ActionManager.PrepareActionsAsync(IExecutionContext executionContext, IEnumerable`1 steps, Guid rootStepId)
##[debug]   at GitHub.Runner.Worker.JobExtension.InitializeJob(IExecutionContext jobContext, AgentJobRequestMessage message)
##[debug]Finishing: Set up job

Has all relevant logs been included?

[X] I've included all relevant logs

Anything else?
Script generating the error, but script is not able to run since Github Actions does not recognize version 17
Code of Conduct

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

HI @cyschneck, I believe you are missing a v it should be tj-actions/verify-changed-files@v17 instead of tj-actions/verify-changed-files@17


Fails to start: "The token is not correct" or "Error: Cannot find module 'commander'"

When i try to start gitter-cli 0.8.5 from npm repo it says:
gitter-cli set-auth ******...******
The token is not correct.

When i try to start gitter-cli from github it says:
gitter-cli
module.js:340
    throw err;
          ^
Error: Cannot find module 'commander'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/home/deniz/gitter-cli/lib/main.js:1:77)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

I'm getting the first outcome "token is not correct" using a digital ocean debian server.

Suddenly I found the cause of failure.
The version installed via npm (sudo npm install...) works only via sudo.
Question is how to set it up to work in user space, not under root?...

Yes, I also tried using sudo, and everything works....

The best way to run this project is by installing it with npm install --global gitter-cli (npm install -g gitter-cli) is an alias.
If you wish to run the application from the repo you need to:

Download or fork the repository.
Go to the project root directory.
Run npm install to install all dependencies.
Execute the application (again, from the project root directory)  with ./bin/gitter-cli.

Remember to check if your npm is correctly installed.

O, Thnx, it works now!


how can set arabic locale to keyboard

always keys with english keys , i need it to be arabic keys how ?


vhs: remove chromium requirement on darwin

Description of changes
Fixes #220367 by removing the Chromium dependency on Darwin.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

@maaslalani - I am trying to add an automated test for the package. It does fine at creating a new demo.tape.
Right now it's hanging when trying to run vhs < demo.tape . It gets to the step before Type echo 'Welcome to VHS!' and seems to get stuck. Is there a verbose or debugging mode to see why it might be getting stuck?
It works fine when I run the built binary manually.

Superseded by #222568.


Setup CI/CD

I've broken jest at least a couple of times now, I am thinking it's time to setup CI. and while we're at it, we could also store the generated example's output, so people can just download that zip and run it directly, instead of having to know download/install Node.js etc.

Nice! wanted to add this for a while but never got to it - left some comments on the PR


need to upgrade to newer semver.js dependency (to pick up bug fixes)

please see:
http://stackoverflow.com/questions/31144268/bower-no-suitable-angular-version/31274670#31274670
as well as issue #1817, reported a few weeks back, which I believe is the same problem.
Bottom line is that the version of semver.js that bower uses (per it's package.json) is more than a year old and that semver code has a bug related to the handling of '.x' in the syntax.
can bower please update to latest semver.js?
Thanks

I've merged PR. It will be released in bower#1.5


fix(query-client): disable refetch on focus

In the spirit of reducing network chattiness, I've disabled refetchOnWindowFocus.
It's also mostly because it's annoying to see all the network traffic in the network-tab when debugging.
We might want to disable refetchOnReconnect as well, but that might have some more implications, and it would be interesting to see how that behaves with the optimistic updates.

Looks good. We could now remove this same setting from the data-workspace.js right?

Yes, forgot about that - will fix.

To comply with our goal of reducing network overhead in production this seems like a good change. The requests during dev. don't really matter to me if the setting is useful in production. If that's the only goal I feel an env var like NODE_ENV would be more suited.

I may have worded myself wrong here. What I ment was that it was the network-request being annoying triggered the removal at first - but of course if we would want this in production we could look into using an env-var... But we don't so I disabled it across the board.

It shouldn't affect the optimistic updates. Since the query that is updated optimistically is disabled whilst there are any pending mutations it shouldn't refetch if it has active optimistic updates.

Great, so this is probably not sending request either way - since most likely a user will have edit a field before going online again.

Thanks for the fix, looks good to me!

I may have worded myself wrong here. What I meant was that it was the network-request being annoying that triggered the removal at first - but of course if we would want this in production we could look into using an env-var... But we don't so I disabled it across the board.

Ah ok I see what you mean :+1:

Great, so this is probably not sending request either way - since most likely a user will have edit a field before going online again.

Yeah exactly.


Initialize dashboard page

This template provide examples of description. Please remove it and replace with yours
This PR will resolve: Initialize dashboard page #23
Check list for reviewer:

[ ] Information in the description is enough and understandable.
[ ] Does not have performance issues.
[ ] Code changes does not effect build failed.
[ ] Does not have issues.

Approving the changes, reviewer must fully understands the description. DO NOT APPROVE MR IF YOU HAVE NO IDEA WHAT IS GOING ON

@spicyzboss please merge the layout so members could work on each tab


Data.Text.Read: rational to Rational goes through Double

Why is rational :: RealFloat a => Reader a instead of Fractional? This way, using rational in Rational context involves a conversion through Double.

(And I need to explicitly convert it to Rational, as it's not an instance of RealFloat.)

Fixed in <IP_ADDRESS>.


[release/v1.12] matcher: add PathMatcher and use in routing, jwt and rbac

Cherry-pick https://github.com/envoyproxy/envoy/pull/10010
Signed-off-by: Yangmin Zhu<EMAIL_ADDRESS>

cc @lizan

Skipping @envoyproxy/api-shepherds review (see: #10035). CI is broken on release/v1.12 for unrelated reasons (see: #10027, #10028), so skipping those checks as well.

Note i pushed an extra commit to fix the unit test. Thanks.


Use of-watchdog 0.9.3 to suppress custom health check logging messages

Signed-off-by: Nitishkumar Singh<EMAIL_ADDRESS>
of-watchdog version to 0.9.3
Description

of-watchdog version to 0.9.3
Motivation and Context

[x] I have raised an issue to propose this change (required)

Which issue(s) this PR fixes

Fixes #283
How Has This Been Tested?

Made changes into template
Created new function with from local templates using faas-cli new java11-test --lang java11 -f <path of template>
Build function faas-cli build -f ./java11-test.yml
Deploy function faas-cli deploy -f ./java11-test.yml
Invoke function

Types of changes

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

Impact to existing users

There should be no impact. As only kube-probe log is disabled
Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

/set title: Use of-watchdog 0.9.3 to suppress custom health check logging messages

@nitishkumar71 I had feedback from a few users that they like to know why something was changed not just how it was changed. What do you think of the new title?

@nitishkumar71 I had feedback from a few users that they like to know why something was changed not just how it was changed. What do you think of the new title?

Make sense, will take care of this in future


exo: 0-unstable-2024-10-21 -> 0-unstable-2024-10-28

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352124

x86_64-linux

:white_check_mark: 2 packages built:

exo
exo.dist

aarch64-linux

:white_check_mark: 2 packages built:

exo
exo.dist

x86_64-darwin

aarch64-darwin

:fast_forward: 2 packages marked as broken and skipped:

exo
exo.dist


tesseract.recognize() crashes when it is called in thread

When I'm calling recognize function in a thread, it crashes. When I don't call it in a thread, it works perfectly. Where is the problem?
My code:
       DispatchQueue.global(qos: .userInitiated).async {             self.tesseract.image = UIImage(named: "text.png")             let text = self.tesseract.recognize()             DispatchQueue.main.async {             }         }
It does this error in the G8Tesseract.mm

Thanks for your help

Me too...😢

@userrr34 Could you please tell me to solve the problem if you know! Thank you very much!


Update BASE_IMAGE in Dockerfile

Currently, the base image for txtai's Dockerfile is Ubuntu 20.04. Support for this release is scheduled to end in April 2025.
A previous Dockerfile update tried to upgrade to Ubuntu 22.04 but the builds for ARM64 failed. Newer builds require a Python Virtual Environment, which will require refactoring the Dockerfile. Alternatively, a new BASE_IMAGE could be considered.
This issue will evaluate and implement the best path forward.

Upon further consideration, using the Python docker images as the default seems to make the most sense given that it's aligned with Python EOL dates.


New release for python 3 support

I see that python3 support was added since 1.0.6. Can you please push this to pypi?

Yeah, I'll take a look at that. Ownership of the github repository was transferred, but not pypi. I'll see if I can get ownership of that package and push out an updated version ASAP

All right, pypi should now be up to date with master, and from now on any tagged builds on master will automatically be uploaded to pypi, so we shouldn't have any trouble in the future.


Set EasyRandom In RandomizerRegistry

Addresses the issue described in https://github.com/murdos/easy-random-protobuf/pull/166

@fmbenhassine please take a look

Addressed in https://github.com/murdos/easy-random-protobuf/pull/170


fix: optimization.emitOnErrors description

What kind of change does this PR introduce?
fix description

Did you add tests for your changes?
NA

Does this PR introduce a breaking change?
No

What needs to be documented once your changes are merged?
nothing

/cc @sokra

Thanks


fix: avoid build failure

[unocss:global:build:generate] [unocss] does not found CSS placeholder in the generated chunks,
this is likely an internal bug of unocss vite plugin
If I don't import uno.css, I get this error during the build phase.

If I don't import uno.css, I get this error during the build phase.

What's the point if you don't import uno.css but install the plugin?

The problem is mainly in build watch mode, I probably deleted the imported "uno.css" and added it later, so I shouldn't get this error.
Maybe we should improve the error message?

Maybe we should improve the error message?

Sounds good to me

I thought it would be more appropriate to add a warning, avoid user think unocss invalid and build failure
So I added the same warning as in development mode to remind the user to import uno.css.
What do you think?


[WXCNP-24284] argo sso group field change to configurable param

TODO: Say why you made your changes.
TODO: Say what changes you made.
TODO: Say how you tested your changes.
TODO: Attach screenshots if you changed the UI.
Fixes #TODO

Replaced by #10957


Spoof the Torrent downloader names to use deiuge or libretorrent

Where would you edit the code, to change default torrent downloaded client name to common used ones. Deluge, U-torrent, Q-bittorrent, R-torrent. The trackers I use, need specific clients. Other wise the downloads will stall

Use the id setting, otherwise a default peer id is used: https://github.com/mafintosh/torrent-stream/blob/adc53d6ced42959ae37553e9f11aa6372e485ca0/index.js#L62


Add missing migration

Any ideas on what caused the change?

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1281   +/-   ##
=======================================
  Coverage   70.24%   70.24%
=======================================
  Files         117      117
  Lines        6094     6094
  Branches      776      776
=======================================
  Hits         4281     4281
  Misses       1655     1655
  Partials      158      158

Continue to review full report at Codecov.

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

Not sure, the migration 0005 introduced the following change to this field:
field=models.CharField(choices=[(b'facebook', b'Facebook-Oauth2'), (b'google-oauth2', b'Google-Oauth2')], max_length=20, verbose_name='name'),. Isn't it related to generating migrations on different Python versions?

Last week i ended with same conclusion. I think we should check all the files for missing unicode_literals future imports.


SVG Image does not render local SVG files (cached files, not assets)

Bug
Locally stored SVG image files fail to render when using react-native-svg's Image component.
Environment info
React native info output:
 info
  React Native Environment Info:
    System:
      OS: macOS 10.14.5
      CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
      Memory: 27.60 MB / 32.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 10.16.0 - /usr/local/opt/node@10/bin/node
      npm: 6.9.0 - /usr/local/opt/node@10/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
    IDEs:
      Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.8 => 0.59.8
    npmGlobalPackages:
      react-native-cli: 2.0.1

Library version: 9.5.1
Steps To Reproduce

Clone git@github.com:ali-farooq0/RN-svg-repro.git
Run npm install
Run npm run android (make sure an emulator/device is running)
Make sure app is running
Observe that there is no SVG displayed in the app

For further debugging
6. Run adb logcat
7. Observe following log output
07-10 21:51:20.217 19877 20258 D skia    : --- Failed to create image decoder with message 'unimplemented'
07-10 21:51:20.218 19877 20258 D skia    : --- Failed to create image decoder with message 'unimplemented'
07-10 21:51:20.220 19877 20259 W unknown:ProgressiveDecoder: unknown image format, {uri: file:///data/user/0/com.svgrepro/files/RNFetchBlobTmp_xoz9wsh6exnqhfz610e2o, firstEncodedBytes: 3C73766720786D6C6E73, length: 422}
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: RNSVG: fetchDecodedImage failed!
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: com.facebook.imagepipeline.decoder.DecodeException: unknown image format
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at com.facebook.imagepipeline.decoder.DefaultImageDecoder$1.decode(DefaultImageDecoder.java:62)
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at com.facebook.imagepipeline.decoder.DefaultImageDecoder.decode(DefaultImageDecoder.java:119)
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at com.facebook.imagepipeline.producers.DecodeProducer$ProgressiveDecoder.doDecode(DecodeProducer.java:248)
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at com.facebook.imagepipeline.producers.DecodeProducer$ProgressiveDecoder.access$200(DecodeProducer.java:109)
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at com.facebook.imagepipeline.producers.DecodeProducer$ProgressiveDecoder$1.run(DecodeProducer.java:146)
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at com.facebook.imagepipeline.producers.JobScheduler.doJob(JobScheduler.java:202)
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at com.facebook.imagepipeline.producers.JobScheduler.access$000(JobScheduler.java:22)
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at com.facebook.imagepipeline.producers.JobScheduler$1.run(JobScheduler.java:73)
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at com.facebook.imagepipeline.core.PriorityThreadFactory$1.run(PriorityThreadFactory.java:51)
07-10 21:51:20.221 19877 19877 W unknown:ReactNative: 	at java.lang.Thread.run(Thread.java:919)

Describe what you expected to happen:
Image component to successfully render locally stored SVG image files. Reading through the log, looks like it fails to parse the SVG file 07-10 21:51:20.220 19877 20259 W unknown:ProgressiveDecoder: unknown image format, {uri: file:///data/user/0/com.svgrepro/files/RNFetchBlobTmp_xoz9wsh6exnqhfz610e2o, firstEncodedBytes: 3C73766720786D6C6E73, length: 422}. This package needs to add support for SVG image decoder, something like: https://github.com/facebook/fresco/blob/master/samples/showcase/src/main/java/com/facebook/fresco/samples/showcase/imageformat/svg/SvgDecoderExample.java
Reproducible sample code
Created a fresh codebase that reproduces the issue
https://github.com/ali-farooq0/RN-svg-repro/blob/master/App.tsx
To verify that the issue is with the decoder, and not my setup, simply comment out line https://github.com/ali-farooq0/RN-svg-repro/blob/master/App.tsx#L12
and uncomment https://github.com/ali-farooq0/RN-svg-repro/blob/master/App.tsx#L13
Workarounds that I've tried

I've used https://github.com/vault-development/react-native-svg-uri to fetch svgs remotely, however it doesn't work for me as I need to fetch an SVG with custom GET headers (cookies, csrf token, etc.), which is why I've had to use RNFetchBlob.fetch(...).

I've also tried using react-native-svg-uri by setting the svgXmlData field. That works for simple cases, but does not work for complex svg files. Already filed an issue with them regarding that: https://github.com/vault-development/react-native-svg-uri/issues/186

When rendering an SVG:

When rendering a jpg (using the same code):

It's really unfortunate that an RN SVG component can't render SVG files :(

Hey there!
Sorry for the frustration; unfortunately I do not believe this is a bug; the Image component is designed specifically to display Images as supported by react-native directly (see: https://facebook.github.io/react-native/docs/image#source).
Any ability to display .svg files would be the purview of either another project or a future enhancement.

@Kingles Seeing that our project requires the capability of displaying .svg files, what's the best way to go about adding this enhancement to either this project or the Image component directly?

How about https://github.com/react-native-community/react-native-svg/blob/master/README.md#use-with-content-loaded-from-uri

@msand as mentioned in the description, already tried it, doesn't work because i need to use custom GET request (with custom cookies, csrf). But even if I did the component itself just parses the content and sets data through svgXmlData field, which doesn't work. Have already opened a bug for them: https://github.com/vault-development/react-native-svg-uri/issues/186

I've used vault-development/react-native-svg-uri to fetch svgs remotely, however it doesn't work for me as I need to fetch an SVG with custom GET headers (cookies, csrf token, etc.), which is why I've had to use RNFetchBlob.fetch(...).

At this point it seems like the issue is going to be with react-native-svg-uri rather than here. @msand --Can we close for now as supporting .svg in this way isn't within the current purview of this project?

@Kingles If this project does not support .svg files then which one would? I don't think there is one. It makes sense to have either the builtin Image component support .svg file rendering or this project. Otherwise there is no way to render .svg files.

The latest version now supports .svg files, xml content, and fetching from uris.


UI Select choices dropdown became invisible with opacity set to 0

.ui-select-choices block's inline style set to opacity: 0; if any Angular version above 1.4.9 is used.
Everything worked perfectly fine with 1.4.9 version of Angular, but as I switched Angular's version to 1.5.9, 1.5.8, 1.5.3 or any 1.5.* version the dropdown became invisible.
Angular: 1.5.*
UI-Select: 0.19.6, 0.19.5, 0.19.4 — checked all this three versions

Hi @artuska  Could you add a plunker and maybe create a PR for this? Happy to review your work.

Ran into same issue.
It looks like before Angular 1.5 the ng-show directive that is in choices.tpl.html for bootstrap and select2 themes already went through a render cycle which removes the ng-hide css class by the time scope.calculateDropdownPos is executed. Later versions ng-hide is still on the '
= 1.5.

if (!uisOffset(dropdown).height && ...

Removing ng-hide manually allows uisOffset to return expected result.
Below is what the dom looks like when this function is being executed.
Angular 1.4.14

Angular 1.6.1 - Notice ng-hide.

This issue is the same as #1560 and https://github.com/angular/angular.js/issues/14304.
Using $animateProvider.classNameFilter is the cause.


Fix MatchParen

Current  setting is the same as the cursor, making it confusing.

@hkupty I'll check the PR and merge it after

No problem!

Any updates on this?


XCode 15.0 Release - firebase-ios-sdk bug: An attribute list cannot appear here

Description
The FIRFirestoreSettings has an error after updating to XCode release version 15.0 on this line:
// Public constant ABSL_CONST_INIT extern "C" const int64_t kFIRFirestoreCacheSizeUnlimited =     Settings::CacheSizeUnlimited;
Error: An attribute list cannot appear here
Reproducing the issue
Try to build an existing iOS app that was previously working that used the FirebaseFirestore module. It no longer builds after the XCode update.
Firebase SDK Version
??
Xcode Version
15.0
Installation Method
Swift Package Manager
Firebase Product(s)
Firestore
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

@dsert1 Thank you for reporting this issue. However, I am not seeing the same issue when I compile using Xcode 15. If possible, could you do the following:

Try to compile the "quickstart" Firestore application using your Xcode 15 setup. To do this, clone the https://github.com/firebase/quickstart-ios repository and attempt to compile and build the application in the "firestore" subidrectory.
Provide a screenshot or full log of the compilation error.
Try to figure out which version of the Firebase iOS SDK that you are using (e.g. the latest at the time of writing is 10.15.0).

Thank you.

@dsert1 I had the same issue. I think you may be operating on Firebase 9.6.0 SDK version.
I fixed the issue by going into my Project - Package Dependencies.
I changed the range from 9.0.0 < 10.0.0 to 10.0.0 < 11.0.0
Then changed the drop down again to 'Update to Next Major Version'. Once that set in, the packages updated and my project ran fine.
Hope that helps.

I got the same issue as well.  Here is the details of my side:
I'm using SPM - Firebase 9.6.0
Error Line:
ABSL_CONST_INIT extern "C" const int64_t kFIRFirestoreCacheSizeUnlimited =     Settings::CacheSizeUnlimited;
Error: An attribute list cannot appear here
Error file path :  Firebase -> Firestore -> API -> FIRFirestoreSettings  / Line - 33
Running Device: Simulator 14 Pro / 16.4

For anyone experiencing this issue, please attempt to reproduce in the latest version, which is 10.15.0 at the time of writing. If this is fixed in the latest version then the "fix" is to upgrade. Otherwise, we will fix it in the next version. So either way, an upgrade will be needed in order to get the fix. Thanks!

any update for this bug.

@Resource-2 What version of the Firebase SDK are you using? It looks like this problem only occurs with old versions of the SDK. Does the problem go away when you upgrade to the latest version, which is 10.15.0 (at the time of writing)?

@rharshaw solution worked for me.

I am going to close this issue since there have been several reports that upgrading to the latest version of the Firebase SDK has fixed the problem. If anyone experiences this issue with the latest version, which is 10.15.0 at the time of writing, or newer, then please leave a comment or open a new issue and we will investigate.

@kemalekren Did updating help you? I updated to 10.15.0 and still get the same error with
ABSL_CONST_INIT extern "C" const int64_t kFIRFirestoreCacheSizeUnlimited = Settings::CacheSizeUnlimited;
Error: An attribute list cannot appear here

I attempted to reproduce by building the Firestore quickstart-ios application, and everything went just fine. That project uses cocoapods (rather than SPM) so maybe this is only a problem when using SPM. Can those of you who are experiencing this bug leave a comment to indicate if you are using CocoaPods or SPM?
For completeness, here is the script I ran in an attempt to reproduce:
#!/bin/bash

set -xveuo pipefail

which pod
pod --version
sudo xcode-select -s /Applications/Xcode_15.app/Contents/Developer
git clone https://github.com/firebase/quickstart-ios.git
cd quickstart-ios/firestore
cp ~/Downloads/GoogleService-Info.plist .
rm Podfile.lock
pod update
xcodebuild -workspace FirestoreExample.xcworkspace -scheme FirestoreExample -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 15' CODE_SIGNING_REQUIRED=NO clean build
echo 'SUCCESS!!!!!!!!!!!!!'

Any solution without update firebase sdk?

Any solution without update firebase sdk?

@dconeybe I using react-native with CocoaPods

Any solution having issue
System:     OS: macOS 14.0     CPU: (8) arm64 Apple M1 Pro     Memory: 82.33 MB / 16.00 GB     Shell: 5.9 - /bin/zsh   Binaries:     Node: 18.16.1 - /opt/homebrew/opt/node@18/bin/node     Yarn: Not Found     npm: 9.5.1 - /opt/homebrew/opt/node@18/bin/npm     Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman   Managers:     CocoaPods: 1.13.0 - /Users/aslam/.rvm/gems/ruby-2.7.6/bin/pod   SDKs:     iOS SDK:       Platforms: DriverKit 23.0, iOS 17.0, macOS 14.0, tvOS 17.0, watchOS 10.0     Android SDK: Not Found   IDEs:     Android Studio: 2022.2 AI-222.4459.24.2221.10121639     Xcode: 15.0/15A240d - /usr/bin/xcodebuild   Languages:     Java: 11.0.18 - /usr/bin/javac   npmPackages:     @react-native-community/cli: 10.1.3 => 10.1.3      react: 18.2.0 => 18.2.0      react-native: 0.71.4 => 0.71.4      react-native-macos: Not Found   npmGlobalPackages:     *react-native*: Not Found

I am using firebase with SPM however I also have cocoapods activated for two pods. On 28. Sep 2023, at 06:59, Aslam Anver @.> wrote:
Any solution having issue
System: OS: macOS 14.0 CPU: (8) arm64 Apple M1 Pro Memory: 82.33 MB / 16.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 18.16.1 - @./bin/node Yarn: Not Found npm: 9.5.1 - @.***/bin/npm Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.13.0 - /Users/aslam/.rvm/gems/ruby-2.7.6/bin/pod SDKs: iOS SDK: Platforms: DriverKit 23.0, iOS 17.0, macOS 14.0, tvOS 17.0, watchOS 10.0 Android SDK: Not Found IDEs: Android Studio: 2022.2 AI-222.4459.24.2221.10121639 Xcode: 15.0/15A240d - /usr/bin/xcodebuild Languages: Java: 11.0.18 - /usr/bin/javac npmPackages: @react-native-community/cli: 10.1.3 => 10.1.3  react: 18.2.0 => 18.2.0  react-native: 0.71.4 => 0.71.4  react-native-macos: Not Found npmGlobalPackages: react-native: Not Found
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

in Xcode, go to FIRFirestoneSettings.mm file, look for;-
ABSL_CONST_INIT extern "C" const int64_t kFIRFirestoreCacheSizeUnlimited =
Settings::CacheSizeUnlimited;
and change it to;-
extern "C" const int64_t kFIRFirestoreCacheSizeUnlimited =
Settings::CacheSizeUnlimited;
run your build, this should work

The problematic ABSL_CONST_INIT was removed in Sept 2022 in https://github.com/firebase/firebase-ios-sdk/pull/10221 and that PR was first included in the Firebase SDK version 10.0.0. Upgrading to a version >= 10.0.0 will fix this issue.
Alternately, as suggested in a previous comment, you can edit the source code in the Pods directory and simply remove the ABSL_CONST_INIT modifier on kFIRFirestoreCacheSizeUnlimited.
I'm going to close this issue because, as far as I can tell, it's fixed and is impossible for this build error to be occurring in the latest version of the Firebase SDK. If you find that this is still occurring with the latest version of the Firebase SDK then please confirm 100% that you are indeed using the latest version. If you are, please provide a GitHub repository that reproduces this build error that I can clone and reproduce for myself.

I get this error on Xcode 15 with the latest SDK 10.15.0

Thanks @dconeybe  It seems to be after removing and adding FirebaseFirestore, FirebaseFirestoreSwift again in the frameworks,libraries in the project target. I also run pod install but I have different Pods not related to Firebase.

@cuddimatic  Good!! It worked here.

in Xcode, go to FIRFirestoreSettings.mm file, look for(go to pods, and you will see FIRbaseFirestore folder, open it);-
ABSL_CONST_INIT extern "C" const int64_t kFIRFirestoreCacheSizeUnlimited =
    Settings::CacheSizeUnlimited;

and change it to;-
extern "C" const int64_t kFIRFirestoreCacheSizeUnlimited =
Settings::CacheSizeUnlimited;

run your build, this should work

Can't we make this process from Podfile automate.

This is solution for automate.
on Podfile
  post_install do |installer|       system('sh fix-build-for-xcode15.sh')   end
on file fix-build-for-xcode15.sh
#issue https://github.com/firebase/firebase-ios-sdk/issues/11840 echo "Fixing build for Xcode 15" sed -i '' 's/ABSL_CONST_INIT extern "C" const int64_t kFIRFirestoreCacheSizeUnlimited =/extern "C" const int64_t kFIRFirestoreCacheSizeUnlimited =/g' Pods/FirebaseFirestore/Firestore/Source/API/FIRFirestoreSettings.mm

@huuthanit Thanks for the Podfile hack! You can probably even simplify your sed script further by just stripping out all occurrences of ABSL_CONST_INIT, something like this:
sed -i '' 's/ABSL_CONST_INIT//g' Pods/FirebaseFirestore/Firestore/Source/API/FIRFirestoreSettings.mm

After all, ABSL_CONST_INIT doesn't actually affect any runtime behavior, but rather ensures that the variable can be initialized at compile time with a compile-time constant. It does not affect correctness.

For those of you running SPM and Cocoapods:
I had to disable: ENABLE_USER_SCRIPT_SANDBOXING
Because the true error appeared to be: Sandbox: rsync.samba
I replicated this by creating a new repository and installing all the same swift packages and pods but not initalizing/using firebase.

in Xcode, go to FIRFirestoreSettings.mm file, look for(go to pods, and you will see FIRbaseFirestore folder, open it);-
ABSL_CONST_INIT extern "C" const int64_t kFIRFirestoreCacheSizeUnlimited =
    Settings::CacheSizeUnlimited;

and change it to;-
extern "C" const int64_t kFIRFirestoreCacheSizeUnlimited =
Settings::CacheSizeUnlimited;

run your build, this should work

This suggestion worked for me as well.

The same fatal error. Xcode 15, Firebase SPM

@ dconeybe the problem is on. Xcode 15, firebase spm...

As @dconeybe pointed out, the Firebase issue is fixed in versions 10.0.0 and higher.
I'm going to close for future comments. Scroll up to see workarounds on earlier versions.


[Navigation Material] bottomSheet() destination does not get updated values

Describe the bug
bottomSheet()-Destination composable does not get updated data from inheriting composable.
if i use a composable() destination it works fine.
To Reproduce
See gist here.
https://gist.github.com/chriswiesner/6503999979f67f8fcca33c56a961c245
Expected behavior
bottomSheet() composable also gets updated data
Screenshots?
!(bug)
!(working fine)
Environment:

Android OS version: Android 12
Device: Emulator
Accompanist version: 0.23.1

Whoo, this one is interesting. I will investigate and get back to you this week!

Hey @jossiwolf Any update on that?

Hi, it looks like this is a Navigation and/or Compose Runtime bug. I was able to repro without any Accompanist dependencies and am currently working on finding a minimal repro. I will post the link to the issue to follow along once I filed it!

Thanks for investigating! (Sadly this might imply that there is no fix in the near future :/ )

@chriswiesner In the meantime, I would recommend passing the State object instead of the value itself. Not as nice, but it works as a workaround:
class MyViewModel: ViewModel() {
    val viewState = mutableStateOf(...)
    ...
}

while that solved the issue in the sample i still have problems in my production code.
dug a bit and found an issue.
RootNav
- rootScreen
- DetailScreen(MyViewModel())
-- detail home
-- bottomSheet

i have nested navigation. creating the VM when navigating to the Detailscreen - (not ideal, i know)
if I use a bottomSheet{} destination in the detail screen it somehow triggers a recomposition in the root, resulting in two different VM instances (bottom sheet gets a different VM than the Detail screen home)
if I use composable {} destination in the detail screen everything works fine.
Example Gist: https://gist.github.com/chriswiesner/ab2c99f78d34406cd3c52a45108de8ee

@jossiwolf  did you manage to file an issue on google side?

Still seems to be an issue in Accompanist 0.24.10-beta

seems the issue is still not resolved :/

@jbw0033 Do you mind taking another look at this? It's been a bit and I didn't make good progress with my investigation :)

+1 on this, any ideas on fix plan on workaround?

With the release of Compose Material 1.7.0-alpha04, the Material team has added a new artifact: androidx.compose.material:material-navigation, which fully replaces Accompanist Navigation Material.
As such, we are closing all issues here on Accompanist and will be fully deprecating Accompanist Navigation Material in an upcoming release.
A number of issues were fixed as part of the migration, but if you're still seeing an issue, please file an issue with a sample project that reproduces your issue and the Material team will take a look.


Update install instructions in README

Replaced by #31 since there is apparently:

no way to add --signoff when editing from GitHub web
no way to force push or add signoff after the fact

😐


iOS simulator doesn't support texture swizzle?

2022-04-15 16:40:46.717578+0800 supertuxkart[33609:158846] -[MTLSimTexture newTextureViewWithPixelFormat:textureType:levels:slices:swizzle:], line 1407: error 'Device does not support texture swizzle.'
-[MTLSimTexture newTextureViewWithPixelFormat:textureType:levels:slices:swizzle:]:1407: failed assertion `Device does not support texture swizzle.'

It triggered when I vkQueueSubmit, but according to
(MVKPhysicalDeviceMetalFeatures) mvk_features = {
  mslVersion = 20400
  indirectDrawing = 0
  baseVertexInstanceDrawing = 0
  dynamicMTLBufferSize = 4096
  shaderSpecialization = 1
  ioSurfaces = 0
  texelBuffers = 1
  layeredRendering = 0
  presentModeImmediate = 0
  stencilViews = 1
  multisampleArrayTextures = 1
  samplerClampToBorder = 0
  maxTextureDimension = 8192
  maxPerStageBufferCount = 31
  maxPerStageTextureCount = 31
  maxPerStageSamplerCount = 16
  maxMTLBufferSize = 268435456
  mtlBufferAlignment = 256
  maxQueryBufferSize = 65536
  mtlCopyBufferAlignment = 1
  supportedSampleCounts = 5
  minSwapchainImageCount = 2
  maxSwapchainImageCount = 3
  combinedStoreResolveAction = 0
  arrayOfTextures = 0
  arrayOfSamplers = 0
  mslVersionEnum = 131076
  depthSampleCompare = 0
  events = 1
  memoryBarriers = 0
  multisampleLayeredRendering = 0
  stencilFeedback = 0
  textureBuffers = 1
  postDepthCoverage = 0
  fences = 1
  rasterOrderGroups = 0
  native3DCompressedTextures = 0
  nativeTextureSwizzle = 1
  placementHeaps = 0
  pushConstantSizeAlignment = 16
  maxTextureLayers = 2048
  maxSubgroupSize = 1
  vertexStrideAlignment = 4
  indirectTessellationDrawing = 0
  nonUniformThreadgroups = 0
  renderWithoutAttachments = 1
  deferredStoreActions = 1
  sharedLinearTextures = 1
  depthResolve = 0
  stencilResolve = 0
  maxPerStageDynamicMTLBufferCount = 31
  maxPerStageStorageTextureCount = 8
  astcHDRTextures = 0
  renderLinearTextures = 1
  pullModelInterpolation = 0
  samplerMirrorClampToEdge = 0
  quadPermute = 0
  simdPermute = 0
  simdReduction = 0
  minSubgroupSize = 1
  textureBarriers = 0
  tileBasedDeferredRendering = 1
  argumentBuffers = 0
  descriptorSetArgumentBuffers = 0
  clearColorFloatRounding = MVK_FLOAT_ROUNDING_NEAREST
  counterSamplingPoints = 7
  programmableSamplePositions = 0
}

nativeTextureSwizzle is 1, and setting cfg.fullImageViewSwizzle = VK_TRUE; has no effect, and it returns VK_SUCCESS if I create an image view with swizzle on:
view_info.format = VK_FORMAT_R8_UNORM;
view_info.components.r = VK_COMPONENT_SWIZZLE_ONE;
view_info.components.g = VK_COMPONENT_SWIZZLE_ONE;
view_info.components.b = VK_COMPONENT_SWIZZLE_ONE;
view_info.components.a = VK_COMPONENT_SWIZZLE_R;

I'm using MacOS 12.3.1 and Xcode 13.3, any ideas?

Thanks for reporting this.
I am indeed able to replicate this validation error on the Cube demo on the iOS Simulator running on an M1 Mac. Very odd, since the M1 successfully supports native texture swizzles when running the Cube demo on macOS. So it is definitely unexpected that the Simulator would not support it. Time to file a bug with Apple, I guess.

I think the best we can do is disable nativeTextureSwizzle when running the simulator, to remove the validation error, and let fullImageViewSwizzle be usable.

Hmmm...on further research, this appears to be a validation-only error. Disabling validation assertions by setting the environment variables:
METAL_ERROR_MODE=3
METAL_DEBUG_ERROR_MODE=3
when running the Cube demo results in the validation error being logged, but actual texture swizzling seems to behave correctly.
Please try that with your app as well, and let me know what happens.
So it appears that the device does support native texture swizzling, but that the validation tests themselves are in error. In that case, it might be best to leave the MoltenVK behavior as it is, with the expectation that apps can set the environment variables when running on the Simulator.
Nevertheless, I have filed a bug report with Apple.

This issue is also occurring for me and am hoping this workaround fixes it.
Where are you setting these environment variables and how are you launching the simulator?
I tried a few places (programmatically in the running executable, using launchctrl, and in a shell used to launch the simulator), but none of them appeared to have any effect.
I tried launching the simulator from a shell as well as from xcode.
Thanks!

I've actually just hit this on my M1 MacBook (2021) running OSX 13.2.1, Xcode 14.3, iOS Simulator 14.3, MoltenVK 1.2.2 and disabling the Metal validation is causing a hard exception to be raised:
2023-05-18 21:11:42.480926-0600 MyApp[32030:464536] *** Terminating app due to uncaught exception 'NSGenericException', reason: 'Device does not support texture swizzle.'
*** First throw call stack:
(
	0   CoreFoundation                      0x0000000180437330 __exceptionPreprocess + 172
	1   libobjc.A.dylib                     0x0000000180051274 objc_exception_throw + 56
	2   Metal                               0x000000018fdd1100 ___ZL16initFailureModesv_block_invoke + 0
	3   MTLSimDriver                        0x00000001aa955390 -[MTLSimTexture newTextureViewWithPixelFormat:textureType:levels:slices:swizzle:] + 576
	4   GPUToolsCapture                     0x0000000105bbebec -[CaptureMTLTexture newTextureViewWithPixelFormat:textureType:levels:slices:swizzle:] + 172
	5   MyApp                          0x0000000104543590 _ZN17MVKImageViewPlane13newMTLTextureEv + 192
...
	34  UIKitCore                           0x000000010cc9ef3c UIApplicationMain + 124
...
)
libc++abi: terminating due to uncaught exception of type NSException

I've disabled the Metal API Validation in Xcode (and the environment variables above), if I enable them, they do trigger the validation assertions and it seems legitimate on my platform.
Anything else I need to do to get past this?

2023-05-18 21:11:42.480926-0600 MyApp[32030:464536] *** Terminating app due to uncaught exception 'NSGenericException', reason: 'Device does not support texture swizzle.'

Uggh. Looks like we might be encountering the situation I described above, and we may have to disable nativeTextureSwizzle when running on a simulator. So bizarre that this is happening on Apple Silicon simulating Apple Silicon.

I've disabled the Metal API Validation in Xcode (and the environment variables above), if I enable them, they do trigger the validation assertions and it seems legitimate on my platform.

Just to be clear, what happens if you enable Metal validation, but set the error mode env vars as mentioned above?
METAL_ERROR_MODE=3
METAL_DEBUG_ERROR_MODE=3

Do you see the Metal validation errors logged but not abort, and then you later encounter the crash above?

@billhollings pleased to say that has actually worked, amazing! So Metal validation needs to be enabled together with those environment variables..as soon as I disable the Metal validation, it raises the exception.

@billhollings pleased to say that has actually worked, amazing! So Metal validation needs to be enabled together with those environment variables..as soon as I disable the Metal validation, it raises the exception. Thanks heaps :-)

Do you see the Metal validations errors being logged?
Hmmm...what you describe is actually quite bizarre. In the situation above, disabling Metal Validation stopped both the validation errors and the crashes. But you're indicating something different, which his that with Metal validation disabled you see crashes, but with Metal validation enabled, it complains but works.
Either way, it looks to be a bug in Metal.
I'm going to leave this issue open for others to encounter. It it become a significant problem, we can work around it in MoltenVK for simulators.


Fix Code Base for Improper DB Transaction Closing

Observation
DB transactions without a proper commit/rollback can lead to unexpected errors.
One such error can be observed from the Configuration Management Component, which performs a DB column check during its startup when configured with the PostgreSQL.
2019-03-01 10:57:01,022] ERROR {org.wso2.carbon.registry.core.jdbc.dao.JDBCPathCache} -  Failed to retrieving resource from /_system/config/identity/email/passwordreset. ERROR: current transaction is aborted, commands ignored until end of transaction block org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
...................... ......................
Caused by: org.postgresql.util.PSQLException: ERROR: relation "idn_config_resource" does not exist   Position: 26
...................... ......................
In this scenario with the PostgreSQL, it is expected to have an exception with the configuration management component, which will be handled within the component[1].
However, the DB connection borrowed from the connection pool for this column check has uncommitted changes from a previous transaction. Therefore, with the expected exception the above error occurs.
Workaround
Enabling <commitOnReturn> in the data source configuration will ensure that a connection is committed before it's released back to the connection pool. This resolves the above-observed error.
Fix
A DB transaction should be properly committed/rollbacked by the layer handles the transaction.
It requires to identify all the places without proper transaction closing, to fix this issue in the code base.
[1]https://github.com/wso2/carbon-identity-framework/blob/c04610a14e441c67f1ecbdca4cd3a9c81e909421/components/configuration-mgt/org.wso2.carbon.identity.configuration.mgt.core/src/main/java/org/wso2/carbon/identity/configuration/mgt/core/internal/ConfigurationManagerComponent.java#L148

Related to the issue.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Rocket move control

Implement rocket movements
PLUS

TDD/Tests

Can i Work on this?

@null-sys It's yours! 🤘🤘


Unable to get correct data from ECU

Every week during 1 or 3 days, the ECU integration doesn't show the measures  of Power and Energy ; message on dashborad  is ECU Power/Energy "Not available". Integration says "Unable to get correct data from ECU, and no cached data. See log for details, and try power cycling the ECU."
After ECU-C power cycling and reconfig IP address, I could restart and get fresh data.... but only for 4 to 6 days per week.
Is this a known issue ?
Thanks in advance

Yes it is, despite efforts to solve this it seems more firmware related and the automation should be used to solve the issue. Read the instructions on how to do this in de readme.


Tooltip background is not applying

Dear fellow developers I have started using this package for past 1 week, we are trying some components  for our product.
So on tooltip component the background is not getting applied even we tried with all theme like (light and dark), Here I am attaching the code and screenshot for you reference
<fwb-tooltip placement="left">     <template #trigger>         <fwb-button class="bg-white hover:border-2 hover:border-gray-400" color="default" pill square>            Toggle Button         </fwb-button>     </template>     <template #content>              Toggle button Tooltip     </template> </fwb-tooltip>

Kindly let me know what we are missing out on this code..
Thanks in advance!!

I have the same issue.

Hey,
There was an issue with previous release... v0.1.5 should fix the above issue... pleas check it and let me know.

FYI: @DevelopmentNightmare, @karthik-propvr
I'm closing this one... but if you're still having an issue with it please let me know.


[Flutter Webview] - [Google_Adsense] Ads Not Open in Google Chrome

Currently I have setup google adsense on my website and create webview application from flutter webview application.
When user click to that ads it is open within browser app itself. So how can i can i set that all ads are open in external browser install in mobile
Please share your experience and feedback on this issue. How you are handling google ads?

Hi @chintooflutter
Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you


TS-5060: Add support for DNAME record type.

This is a patch suggested by @zwoop that adds support for resolving DNAME record types.  I've tested this patch with a delivery service we were trying to deploy that uses DNAME record types.  This patch solves the problem where queries using DNAME failed due to ATS inability to resolve DNAME's.

FreeBSD build failed! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1231/ for details.

Linux build failed! See https://ci.trafficserver.apache.org/job/Github-Linux/1125/ for details.

Seems two issues here:

clang-format
FreeBSD doesn't have a T_DNAME ?

Taking a look.
Thanks
John J. Rushford
IPCDN Engineering
1400 Wewatta Street, Denver Colorado 80202
<EMAIL_ADDRESS>From: Leif Hedstrom<EMAIL_ADDRESS>Reply-To: apache/trafficserver<EMAIL_ADDRESS>Date: Thursday, December 1, 2016 at 9:04 AM
To: apache/trafficserver<EMAIL_ADDRESS>Cc: John Rushford<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [apache/trafficserver] TS-5060: Add support for DNAME record type. (#1241)
Seems two issues here:

clang-format
FreeBSD doesn't have a T_DNAME ?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/apache/trafficserver/pull/1241#issuecomment-264213697, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEVybpNvF4mZXXMjhOE6Xu_0J0zXmFVSks5rDvAFgaJpZM4LBjGp.

I'd squash these commits, but this looks good.

In FreeBSD T_DNAME is missing from /usr/include/arpa/nameser_compat.h.  However, in /usr/include/arpa/nameser_h, ns_t_dname is defined and In nameser_compat.h, all the T_* dns record types tokens point to the ns_t_* tokens defined in nameser.h
I changed DNS.cc to use the ns_t_dname token and for consistency, I changed all the other record type tokens to use the ns_t names from nameser.h.  After making these changes, there really is no need for nameser_compat.h in the ATS code so, I removed including it.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1126/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1232/ for details.

I squashed them, just wanted you to be able to see the commit history.
From: Leif Hedstrom<EMAIL_ADDRESS>Reply-To: apache/trafficserver<EMAIL_ADDRESS>Date: Thursday, December 1, 2016 at 1:26 PM
To: apache/trafficserver<EMAIL_ADDRESS>Cc: John Rushford<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [apache/trafficserver] TS-5060: Add support for DNAME record type. (#1241)
@zwoop commented on this pull request.
Yeh, squash 'em, since otherwise we have potential broken intermediate commits.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/apache/trafficserver/pull/1241#pullrequestreview-11049908, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEVybtbLuaMzhyAaiB9lHsvGcwxCXqLMks5rDy1_gaJpZM4LBjGp.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1233/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1127/ for details.