Translations

How I enable translations to spanish?

If you want only Spanish then in your config.yml:
framework:
    default_locale:  "es"

else if you want to configure different languages then checkout my Ticket Demo:
https://github.com/hackzilla/TicketBundleDemoApp/blob/master/src/AppBundle/EventListener/UserLocaleListener.php

I already have that in my config.yml. I have to do something else to make it work?

I just solved it. I was missing to config the knp paginator dependency.


After resize event?

Can i listen after resize event?

Hi,
have you found something ?
I would like to get the size of every column after resize. Does the library return the values ? or do I have  to calculate them myself with JS ?
thanks !

Hi, @ligne13 !
Not found ,  try mousemove event and calculate columns.

This is a valid issue. An event with the columns widths will be very useful.


proposal: net: add Unwrap method to *DNSError

Edit: current proposal: https://github.com/golang/go/issues/63116#issuecomment-1727801738

This is a proposal to fix the #63109 issue.
I propose adding a causeErr field to DNSError and an Unwrap method that returns the causeErr.
// DNSError represents a DNS lookup error.
type DNSError struct {
    causeErr error // returned by the Unwrap method.
    // (....)
}

func (e *DNSError) Unwrap() error { return e.causeErr }

This way we keep backwards compatibility for the Error method, we always construct the error from
the Err string field (we keep the current implementation). In the net pacakge we will then make Err field to be the result of the first call to causeErr.Error().

Should we do the same for AddrError? (It also has an Err string field.)
All fields of DNSError and AddrError are currently exported, so it is possible for packages outside of net to construct one of these  errors directly. Should the new field be exported too?

Should we do the same for AddrError? (It also has an Err string field.)

AFAIK the AddrError seems to be a standalone error (i.e. it doesn't seem to wrap anything).

All fields of DNSError and AddrError are currently exported, so it is possible for packages outside of net to construct one of these errors directly. Should the new field be exported too?

I don't know whether we want to allow this (we would have to enforce somehow that DNSError.causeErr.Error() == DNSError.Err). Maybe we should leave this for future consideration? We can export it afterwards.
There is still an issue (with the current proposal), that someone might change the Err field without updating the causeErr.
I am unsure about this (in either way).

Since all the existing fields of DNSError are exported, I think the new one should also be exported.  I suggested Underlying.

Here is a test for #63109 that I wrote last night.
func TestCancelBeforeDial(t *testing.T) {
	ln := newLocalListener(t, "tcp")
	defer ln.Close()
	_, port, err := SplitHostPort(ln.Addr().String())
	if err != nil {
		t.Fatal(err)
	}

	ctx, cancel := context.WithCancel(context.Background())
	cancel()
	var d Dialer
	_, err = d.DialContext(ctx, "tcp", JoinHostPort("localhost", port))
	if err == nil {
		t.Error("DialContext with canceled context did not fail")
	} else if !errors.Is(err, context.Canceled) {
		t.Errorf("error.Is(%v, context.Canceled) failed", err)
	}
}

Fine, let's make the error field exported.
The proposal looks like this now:
// DNSError represents a DNS lookup error.
type DNSError struct {
	// Underlying is an error that caused this DNSError.
	// It is returned by the Unwrap method.
	//
	// When updating this field make sure to update
	// the Err field accordingly, so that the Error
	// and Unwrap methods don't diverge.
	Underlying error

	// Err is a description of the error, for backwards compatibility
	// the net package sets this error to the value
	// returned by Underlying.Error(), it used by
	// the Error method to produce the error string.
	Err string

	// (...)
}

// Unwrap returns e.Underlying.
func (e *DNSError) Unwrap() error { return e.Underlying }

Having an exported error may also come in handy with possible future support for "extended dns errors", see https://datatracker.ietf.org/doc/html/rfc8914. Could be good to take that into account. It is useful to learn about specifics of dns failures, especially with dnssec errors, and for getting a more descriptive message than "servfail".

@mjl- Great idea! I made #63192 for this. This should allow for detailed error messages from the pure go resolver. Not sure how the exported error helps with this. I assume you mean an exported (new) error type just for extended dns errors, I don't think we will ever do this it would be impossible to support this on windows and on unix cgo resolver.

I assume you mean an exported (new) error type just for extended dns errors, I don't think we will ever do this it would be impossible to support this on windows and on unix cgo resolver.

Yes, a new error type for extended dns errors is what I had in mind.
I would think windows and unix c would at some point make these extended dns errors accessible, perhaps with a new API. They'll want it sooner or later.
We could make these detailed errors optional. DNS servers (recursive resolvers) don't have to support EDE, and not all do, so there is already no guarantee you'll get them.
Anyway, if underlying errors can be unwrapped, and I can set those errors, I could make a new package that can return a net.DNSError with specific EDE errors of my own package. It would make it easier to provide a drop-in replacement resolver package.

I implemented this change in CL 532217, it also simplifies the code a bit with an internal constructor for the *DNSError, so that we don't have to set the Err, IsNotFound, IsTimeout, IsTemporary fields manually each time we construct the error, these fields will be now determined based on the Underlying error type.

@rsc Any chance of getting this through proposal process? This is a bug-fix that needs a proposal. It would be nice to fix this for go 1.23. Thanks

I thought when we added Unwrap we explicitly looked at all types with an Err field and decided which to do and not do. For net.AddrError, we explicitly decided against it.
For net.DNSError, there is no Err field currently, so we could add one. Except there is an 'Err string' field.
There are lots of times when errors should not be wrapped. I don't see a discussion here of which errors to expose with Unwrap and why that is correct.

There are lots of times when errors should not be wrapped. I don't see a discussion here of which errors to expose with Unwrap and why that is correct.

What kind of errors shouldn't be wrapped? I think that we should wrap all errors and just for backwards-compatibility set the Err field to Underlying.Error(), as in https://go.dev/cl/532217. I can think of one case that we don't strictly speaking have to wrap errNoSuchHost, because we have the IsNotFound field, but considering that errNoSuchHost is not exported i don't see a reason not to wrap it.

I disagree about at least the syscall return. I think wrapping is harmful, because it exposes the underlying implementation in ways that are easier to depend on. Most syscall errors are also highly non-specific. I can see wanting Unwrap to work for the context error. I think that if we proceed, we should default to Underlying==nil and Err != "" and only set Underlying for the specific cases that we want Unwrap to work for (like context).
I'm also not convinced about Underlying; perhaps it should be UnwrapErr.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

I'm also not convinced about Underlying; perhaps it should be UnwrapErr.

Underlying sounds better to me

Underlying is a concept in go/types; it is never used for errors in API names.
UnwrapErr is clunky but clear: it is the error that Unwrap returns, which may or may not be nil.

Have all remaining concerns about this proposal been addressed?
The proposal is to add UnwrapErr error to DNSError, and an Unwrap method that returns UnwrapErr. By default, DNSErrors will have UnwrapErr set to nil, but we can set it explicitly for specific errors. To start, the context errors seem to be the only ones. If there are others that programs need to distinguish, please let us know.

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group
The proposal is to add UnwrapErr error to DNSError, and an Unwrap method that returns UnwrapErr. By default, DNSErrors will have UnwrapErr set to nil, but we can set it explicitly for specific errors. To start, the context errors seem to be the only ones. If there are others that programs need to distinguish, please let us know.

FYI, currently the net package does not return directly errors from the context package, but it maps them with mapErr.
https://github.com/golang/go/blob/c9ed561db438ba413ba8cfac0c292a615bda45a8/src/net/cgo_unix.go#L81
https://github.com/golang/go/blob/c9ed561db438ba413ba8cfac0c292a615bda45a8/src/net/net.go#L427-L438
Do we want to keep it this way?

We should keep it that for now.  Changing it seems likely to break existing code (which is we do the mapping in the first place).  If somebody wants to investigate changing this behavior, that can be a separate proposal.

How do we want to handle errors from Resolver.Dial and from the returned net.Dialer?
Should we map the context errors, with mapErr? I think it is harmfull, because we will not be able to map wrapped errors.
Should we only returns error that match errors.Is(err, context.Canceled), without mapping.
https://github.com/golang/go/blob/68d3a9e417344c11426f158c7a6f3197a0890ff1/src/net/dnsclient_unix.go#L176-L179

Sorry, I'm not sure exactly what you are asking.
If we returned a mapped error today, we should continue to do that.
Note that the mapped errors already return true for things like errors.Is(err, context.Canceled) or errors.Is(err, context.DeadlineExceeded.

We currently do not map errors returned by Resolver.Dial:
https://github.com/golang/go/blob/68d3a9e417344c11426f158c7a6f3197a0890ff1/src/net/dnsclient_unix.go#L176-L179
How we should handle errors returned from the Dial function?
Do we want to return the error as is.
c, err := r.dial(ctx, network, server)
if err != nil {
    return &DnsError{
        Err: err.Error(),
        UnwrapErr: err,
    }
}

Return the error, but only when it matches context.Canceled or context.DeadlineExceeded
c, err := r.dial(ctx, network, server)
if err != nil {
    if errors.Is(err, context.Canceled) || errors.Is(err, context.DeadlineExceeded) {
        return &DnsError{
            Err: err.Error(),
            UnwrapErr: err,
        }
    }
    return &DnsError{
        Err: err.Error(),
    }
}

Or return only errCanceled, errTimeout.
c, err := r.dial(ctx, network, server)
if err != nil {
    if errors.Is(err, context.Canceled)  {
        return &DnsError{
            Err: err.Error(),
            UnwrapErr: errCanceled,
        }
    }
    if errors.Is(err, context.DeadlineExceeded)  {
        return &DnsError{
            Err: err.Error(),
            UnwrapErr: errTimeout,
        }
    }
    return &DnsError{
        Err: err.Error(),
    }
}

Looking at Resolver.dial, it already calls mapErr.  The code that you mention is in Resolver.exchange; the only caller of Resolver.exchange already wraps the error up in a DNSError.  So I think the only question is what Resolver.tryOneName should put in the new UnwrapErr field of the returned DNSError.  I think it should set UnwrapErr to the error returned by Resolver.exchange.  Perhaps I am missing something.

Oh, right I somehow missed that, but the mapping is obviously not great, it does not go through Unwrap errors, so it might lead to some confusing cases:
r := net.Resolver{
	Dial: func(ctx context.Context, network, address string) (net.Conn, error) {
		return nil, context.Canceled
	},
}
_, err := r.LookupMX(context.Background(), "test")
fmt.Println(err) // errCancaled

r := net.Resolver{
	Dial: func(ctx context.Context, network, address string) (net.Conn, error) {
	    return nil, &net.OpError{Err: context.Canceled} // wrapped error
	},
}
_, err := r.LookupMX(context.Background(), "test")
fmt.Println(err) // &net.OpError{Err: context.Canceled}

The current status of this proposal is to only expose context errors, so I think that we should return only the errCanceled, errTimeout when: errors.Is(err, context.Canceled) or errors.Is(err, context.DeadlineExceeded).
So:
https://github.com/golang/go/blob/68d3a9e417344c11426f158c7a6f3197a0890ff1/src/net/dnsclient_unix.go#L305-L311
becomes:
p, h, err := r.exchange(ctx, server, q, cfg.timeout, cfg.useTCP, cfg.trustAD)
if err != nil {
     dnsErr := &DNSError{
	Err:    err.Error(),
	Name:   name,
	Server: server,
    }
    if errors.Is(err, context.Canceled) {
        dnsErr.UnwrapErr = errCalceled
    }
    if errors.Is(err, context.DeadlineExceeded) {
        dnsErr.UnwrapErr = errTimeout
    }
    // (...)
}

This way we do not expose implementation errors and allow the *DnsError to match context.DeadlineExceeded and context.Canceled through errors.Is.

That is OK with me.  I guess the only question is how we should handle an error returned by a system call: should we wrap it or not?  Since we haven't wrapped it in the past, I'm fine with continuing to not wrap it, at least until we have a clear reason to do so.  Thanks.

It sounds like the only use of Unwrap will be for Is, in which case we could decide that instead of adding an Unwrap method we could implement an Is method on DNSError. Is there a reason to prefer one or the other? Probably Unwrap is more general for dealing with future issues?

Just as you mentioned, Unwrap is better for errors that we might want to unwrap in future, but at the current state of the proposal there is no difference between adding a Is or Unwrap method. But i guess that for Is we would also have to add a UnwrapErr field, so in that case Unwrap feels better to me.

Unwrap is simpler and clearer. If you've got a choice between Unwrap and Is, I'd always recommend picking Unwrap.
Is is more general, you can do more with it, but it's more mechanism. I don't see a reason to use it here.


XDS connections need TCP keepalives

Description:
It is possible for XDS connections to half close, leaving envoy pods without config. This is well documented in other XDS implementations and is generally resolved with keepalives:
https://github.com/envoyproxy/envoy/issues/6323
https://github.com/projectcontour/contour/pull/1746

+1
subset of https://github.com/envoyproxy/gateway/issues/1565


automate subcommand dispatching (case analysis)

I don't think there's any case where several of the boolean flags can be true at the same time is there? With Struct variants being un-feature-gated recently, wouldn't they be a rather nice option?
docopt!(Args deriving Show, "
Usage:
  partners list
  partners set <nick> [--local]
")

would generate something like:
enum Args {
  List,
  Set { arg_nick: String }
}

This would make pattern matching on the parsed arguments very nice:
match args {
  List => list(),
  Set { arg_nick: nick } => set(nick.as_slice())
}

If arguments and options should be namespaced, we could do something like:
struct SetArguments { nick: String }
struct SetOptions { local: bool }
enum Args {
  List,
  Set { arguments: SetArguments, options: SetOptions }
}

But this wouldn't lead to nearly as nice pattern matching.
Just an idea, no idea if this is feasible or not.

Hi @icorderi I've been emulating your code in a project of mine.  Did you ever happen to find a way to make it such that the dispatch match returns e.g. a trait object (a Command instance)?  Then you wouldn't have to duplicate the invocations of x.execute(), you could do it generically for all commands.  You could also invoke usage() that way etc.
I'm having trouble doing it, but I'm new to Rust and it's leading me down a path of trait object / generics confusion.

Btw I was able to achieve what I described above using a combination of Box<Command> and UFCS.

https://github.com/docopt/docopt.rs/blob/master/src/parse.rs#L617-L623 that is a good model :). Maybe an enum can be generated for every alternative with disjoint variants?

I would definitely like to see subcommands-as-enums happen. Maybe a Vec of enum variants could be returned in programs where multiple subcommands can be specified at once? If per-subcommand options are required, those could be passed out as associated values.


develop version 2.0.0

Plan

remove acrylic case
replace gasket mount 3dp case to top mount 3dp case
replace underglow led to backlight led
centering usb connector
remapping curcuit
improve trackball movement more smoothly

merged.


_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 55s

the patch passed

+1 :green_heart:
compile
0m 27s

the patch passed

+1 :green_heart:
javac
0m 27s

the patch passed

+1 :green_heart:
javadoc
0m 22s

the patch passed

+1 :green_heart:
shadedjars
6m 34s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 21s

hbase-client in the patch passed.

26m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6318

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux c040dd9d6a00 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 7b3a71e9c0d3e6bc59846702f75b52902ba8f4aa

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/1/testReport/

Max. process+thread count
305 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 33s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 19s

master passed

+1 :green_heart:
compile
0m 46s

master passed

+1 :green_heart:
checkstyle
0m 15s

master passed

+1 :green_heart:
spotbugs
0m 42s

master passed

+1 :green_heart:
spotless
0m 44s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 58s

the patch passed

+1 :green_heart:
compile
0m 45s

the patch passed

+1 :green_heart:
javac
0m 45s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 14s
/results-checkstyle-hbase-client.txt
hbase-client: The patch generated 1 new + 18 unchanged - 1 fixed = 19 total (was 19)

+1 :green_heart:
spotbugs
0m 47s

the patch passed

+1 :green_heart:
hadoopcheck
11m 14s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 43s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 55s

the patch passed

+1 :green_heart:
compile
0m 45s

the patch passed

+1 :green_heart:
javac
0m 45s

the patch passed

+1 :green_heart:
javadoc
0m 42s

the patch passed

+1 :green_heart:
shadedjars
8m 47s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 43s

hbase-client in the patch passed.

36m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/2/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6318

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 79219a2df795 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ce6146e0f5cdad7c68ba1eae6487ecd681b6b93c

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/2/testReport/

Max. process+thread count
303 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/2/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 32s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 38s

master passed

+1 :green_heart:
compile
1m 12s

master passed

+1 :green_heart:
checkstyle
0m 25s

master passed

+1 :green_heart:
spotbugs
1m 13s

master passed

+1 :green_heart:
spotless
1m 10s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 40s

the patch passed

+1 :green_heart:
compile
1m 14s

the patch passed

-0 :warning:
javac
1m 14s
/results-compile-javac-hbase-client.txt
hbase-client generated 1 new + 102 unchanged - 1 fixed = 103 total (was 103)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 27s
/results-checkstyle-hbase-client.txt
hbase-client: The patch generated 1 new + 18 unchanged - 1 fixed = 19 total (was 19)

+1 :green_heart:
spotbugs
1m 15s

the patch passed

+1 :green_heart:
hadoopcheck
14m 30s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
1m  8s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 14s

The patch does not generate ASF License warnings.

42m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6318

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 7c09276862b0 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ce6146e0f5cdad7c68ba1eae6487ecd681b6b93c

Default Java
Eclipse Adoptium-17.0.11+9

Max. process+thread count
80 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/2/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 28s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 41s

master passed

+1 :green_heart:
compile
0m 48s

master passed

+1 :green_heart:
checkstyle
0m 16s

master passed

+1 :green_heart:
spotbugs
0m 47s

master passed

+1 :green_heart:
spotless
0m 45s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 59s

the patch passed

+1 :green_heart:
compile
0m 45s

the patch passed

-0 :warning:
javac
0m 45s
/results-compile-javac-hbase-client.txt
hbase-client generated 1 new + 102 unchanged - 1 fixed = 103 total (was 103)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 14s
/results-checkstyle-hbase-client.txt
hbase-client: The patch generated 1 new + 18 unchanged - 1 fixed = 19 total (was 19)

+1 :green_heart:
spotbugs
0m 51s

the patch passed

+1 :green_heart:
hadoopcheck
11m 41s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 43s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 58s

the patch passed

+1 :green_heart:
compile
0m 41s

the patch passed

+1 :green_heart:
javac
0m 41s

the patch passed

+1 :green_heart:
javadoc
0m 33s

the patch passed

+1 :green_heart:
shadedjars
9m 14s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 38s

hbase-client in the patch passed.

33m 49s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/3/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6318

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux aebda536fe80 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 1b20c920f4b0a1ffec36856972adaca16626e8b1

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/3/testReport/

Max. process+thread count
325 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/3/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 54s

master passed

+1 :green_heart:
compile
1m 10s

master passed

+1 :green_heart:
checkstyle
0m 24s

master passed

+1 :green_heart:
spotbugs
1m  2s

master passed

+1 :green_heart:
spotless
1m 18s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 52s

the patch passed

+1 :green_heart:
compile
1m  3s

the patch passed

-0 :warning:
javac
1m  3s
/results-compile-javac-hbase-client.txt
hbase-client generated 1 new + 102 unchanged - 1 fixed = 103 total (was 103)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 18s
/results-checkstyle-hbase-client.txt
hbase-client: The patch generated 1 new + 18 unchanged - 1 fixed = 19 total (was 19)

+1 :green_heart:
spotbugs
1m 18s

the patch passed

+1 :green_heart:
hadoopcheck
15m 14s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 59s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 57s

the patch passed

+1 :green_heart:
compile
0m 25s

the patch passed

+1 :green_heart:
javac
0m 25s

the patch passed

+1 :green_heart:
javadoc
0m 19s

the patch passed

+1 :green_heart:
shadedjars
5m 27s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m 38s

hbase-client in the patch passed.

21m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/5/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6318

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux af06f53ec028 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 05ea9f46373d790dca399ec9b884c480d3dbf695

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/5/testReport/

Max. process+thread count
298 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/5/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 31s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 56s

master passed

+1 :green_heart:
compile
0m 55s

master passed

+1 :green_heart:
checkstyle
0m 16s

master passed

+1 :green_heart:
spotbugs
0m 48s

master passed

+1 :green_heart:
spotless
0m 57s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 41s

the patch passed

+1 :green_heart:
compile
0m 58s

the patch passed

-0 :warning:
javac
0m 58s
/results-compile-javac-hbase-client.txt
hbase-client generated 1 new + 102 unchanged - 1 fixed = 103 total (was 103)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 19s
/results-checkstyle-hbase-client.txt
hbase-client: The patch generated 1 new + 18 unchanged - 1 fixed = 19 total (was 19)

+1 :green_heart:
spotbugs
1m  0s

the patch passed

+1 :green_heart:
hadoopcheck
11m 59s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 42s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m  9s

The patch does not generate ASF License warnings.

33m  5s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/5/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6318

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 1e8ac51b18cf 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 05ea9f46373d790dca399ec9b884c480d3dbf695

Default Java
Eclipse Adoptium-17.0.11+9

Max. process+thread count
84 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/5/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

Please fix the too long line checkstyle warning.

Thanks. :+1:  Strange it did not broke the build. To be honest it was quite hard to find this checkstyle warning. Will fix it. :thinking:

Thanks.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 59s

the patch passed

+1 :green_heart:
compile
0m 23s

the patch passed

+1 :green_heart:
javac
0m 23s

the patch passed

+1 :green_heart:
javadoc
0m 19s

the patch passed

+1 :green_heart:
shadedjars
5m 19s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m 38s

hbase-client in the patch passed.

21m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/6/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6318

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux cc9936ed8dce 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 4755420c8d5caa0adfd6418ae156f1a20fac3e21

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/6/testReport/

Max. process+thread count
289 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/6/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 35s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m  3s

master passed

+1 :green_heart:
compile
0m 46s

master passed

+1 :green_heart:
checkstyle
0m 16s

master passed

+1 :green_heart:
spotbugs
0m 41s

master passed

+1 :green_heart:
spotless
0m 43s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 53s

the patch passed

+1 :green_heart:
compile
0m 46s

the patch passed

-0 :warning:
javac
0m 46s
/results-compile-javac-hbase-client.txt
hbase-client generated 1 new + 102 unchanged - 1 fixed = 103 total (was 103)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 15s

hbase-client: The patch generated 0 new + 18 unchanged - 1 fixed = 18 total (was 19)

+1 :green_heart:
spotbugs
0m 48s

the patch passed

+1 :green_heart:
hadoopcheck
12m  0s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 51s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 10s

The patch does not generate ASF License warnings.

31m 28s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/6/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6318

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux cfbfa67c3397 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 4755420c8d5caa0adfd6418ae156f1a20fac3e21

Default Java
Eclipse Adoptium-17.0.11+9

Max. process+thread count
83 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6318/6/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

Please prepare a backport of this patch for branch-2. It is needed for committing this on the 2.x branches.

Thanks, the backport to branch-2 is prepared here:
https://github.com/apache/hbase/pull/6362


Battle (And or Battle Intense) Breaks after a couple minutes of playback

Hey, been encountering this one for a while now. So, when I would be playing, music would play as normal. But then after a couple of switches it'll start erroring out and the track that would play would repeatedly start and start.
Mod Collection:
https://steamcommunity.com/sharedfiles/filedetails?id=3375234534
Steps to Reproduce:
I'm not sure, this one's hard to make happen on a whim quickly. I'd say from a quick assessment to try a long play session with the mods enabled. I'd say 45 minutes to maybe 1 or 2 hours? That's how long into my play sessions that the bug happened, but my sense of time is awful.
I'll provide video proof if I catch it happening again, I do have OBS and know how to use it. I'll include the error it spat out in the console, since the one from last time was overwritten by the collection link.

Here's some video proof, caught it as I was just playing normally. Don't know how long this was in, I'd say maybe 45 to 50 minutes? It seemed to behave just fine when it transitioned back to ambiance.
Video Link
https://drive.google.com/file/d/1st9HkKiU4_5B_lwx1fkH6OxjM4MrxfqH/view?usp=drive_link
Here's the error, too. There was others showing up the previous times, but this is the one that showed up this time.
[Action Music (with pvp support)] lua/autorun/client/am_music.lua:491: attempt to index a nil value

unknown - lua/autorun/client/am_music.lua:491

i couldnt recreate it still, however i see what could have caused it. pushed a change to the workshop, go check that out


[CI] Update Unit Test/Lint Workflows

Stack from ghstack (oldest at bottom):

#334
-> #326
#322
#323
#333

Summary:

Update github action versions
Remove conda activate as conda action will create and activate the environment
Use env, defaults to avoid repetitive usage of variables, commands
Prepend python commands with python -m to ensure we get the correct version

Except for pytest, reason see #322

Add a step to upgrade pip
Use default fetch depth 1 when checking out the repo; 0 fetches all history/branches/tags.
Add test profiling

Test Plan:

CI

Differential Revision: D39904702

Codecov Report

:exclamation: No coverage uploaded for pull request base (gh/langong347/57/base@dbdb5ba). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@                   Coverage Diff                    @@
##             gh/langong347/57/base     #326   +/-   ##
========================================================
  Coverage                         ?   93.37%
========================================================
  Files                            ?       54
  Lines                            ?     3247
  Branches                         ?        0
========================================================
  Hits                             ?     3032
  Misses                           ?      215
  Partials                         ?        0

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@langong347 has imported this pull request.  If you are a Meta employee, you can view this diff on Phabricator.

@langong347 has imported this pull request.  If you are a Meta employee, you can view this diff on Phabricator.

@langong347 has imported this pull request.  If you are a Meta employee, you can view this diff on Phabricator.


feat: createXOAuth2Client()

This change replaces createClient() with various flavours of createXOAuth2Client(), where X is a provider.

WDYT about this design change, @kt3k?

This allows us to much more easily enforce strict typing. +1 from me.


Fix new user example

Fixes https://github.com/MicrosoftDocs/feedback/issues/3318.

Docs Build status updates of commit 936de7f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureadps-2.0/AzureAD/New-AzureADUser.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Was this supposed to go directly into the live branch? Just noticed that.

Ouch. No it needs to go to master.

I'm not sure why it went to live since this line is set to master: https://github.com/Azure/azure-docs-powershell-azuread/blob/26172c26858f98f4b17677a2647a1b84ac50b303/.openpublishing.publish.config.json#L17. But if you click edit on the page, it goes to live.


Chore/remove broken links es

What does this PR do?
Remove Resource(s)
Having checked resources that currently fail checks I have removed the broken links.
Why is this valuable (or not)?
Saves time for those looking for resources.
Checklist:

[X] Not a duplicate
[X] Included author(s) if appropriate (not applicable)
[X] Lists are in alphabetical order  (not applicable)
[X] Needed indications added (PDF, access notes, under construction)  (not applicable)

looks like 2 categories need to be removed too. We like chore-doers!

Sorry, that was sloppy of me.  Should be done now @eshellman.

Thanks, and welcome to free-programming-books!


Standard_NC6 VMs have been deprecated. The page needs to be updated.

Standard_NC6 VMs have been deprecated. The page needs to be updated.

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

ID: deaac79e-bd40-2d95-7288-e15371726e91
Version Independent ID: 9fd80908-20f1-7970-3bda-5a4283e4af21
Content: Use GPUs on Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/gpu-cluster.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@shanavt
Thanks for your feedback! We will investigate and update as appropriate.

#reassign:Nickomang

@shanavt, Thanks for bringing this to our attention! I've updated our docs with the new recommended minimum node VM SKU.
#please-close


Upgrade to React 18

Upgrades to React 18 along with some other older dependencies.
This will enable us to use components from our shared UI package, and use more modern libraries.
I plan to keep this PR open for a short while as an internal beta, to check for any issues we may come across with unforeseen issues between react 17 and 18.

Closing as this is now part of the release-139 branch


Ai getting started readme update

Existing Sample Changes
Description
Updated getting started readme for AI Tool selector.
Fixes Issue#
External Dependencies
List any external dependencies created as a result of this change.
Type of change

[ X] Implement fixes for ONSAM Jiras

How Has This Been Tested?

@louie-tsai can you take a look at this PR?


Acquisition of billion sized image-text-pairs dataset

Continue the workflow to transform Common Crawl data into a billion sized image-text-pairs dataset. Currently at about 1.2 billion in size.
Basic workflow steps are:

parsing the common crawl WAT files and retain candidates URL-text pairs
download the images at URLs and filter unwanted items, also resize to 224x224 with center-crop the remaining ones
send batches of images and metadata to CLIP inference to calculate similarity scores, then keep only pairs with score > 0.3

done and released


AttributeError: 'super' object has no attribute 'response'

After upgrading Flexget from an old version (sometime late last year), I have been getting these errors when using any command. I have also not been able to access HTTPS URLs either, and that was before (and after) upgrading.
2016-02-26 20:18 CRITICAL plugin                        Exception while loading plugin flexget.plugins.api.history
2016-02-26 20:18 ERROR    plugin                        'super' object has no attribute 'response'
Traceback (most recent call last):
  File "/Library/Python/2.7/site-packages/flexget/plugin.py", line 381, in _load_plugins_from_dirs
    __import__(module_name)
  File "/Library/Python/2.7/site-packages/flexget/plugins/api/history.py", line 9, in <module>
    from flexget.api import api, APIResource
  File "/Library/Python/2.7/site-packages/flexget/api/__init__.py", line 310, in <module>
    loader.find_module(module_name).load_module(module_name)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/pkgutil.py", line 246, in load_module
    mod = imp.load_module(fullname, self.file, self.filename, self.etc)
  File "/Library/Python/2.7/site-packages/flexget/api/authentication.py", line 81, in <module>
    class LoginAPI(APIResource):
  File "/Library/Python/2.7/site-packages/flexget/api/authentication.py", line 83, in LoginAPI
    @api.response(401, 'Invalid username or password')
  File "/Library/Python/2.7/site-packages/flexget/api/__init__.py", line 147, in response
    return super(Api, self).response(code_or_apierror, description, model=model)
AttributeError: 'super' object has no attribute 'response'
Traceback (most recent call last):
  File "/usr/local/bin/flexget", line 9, in <module>
    load_entry_point('FlexGet==1.2.460', 'console_scripts', 'flexget')()
  File "/Library/Python/2.7/site-packages/flexget/__init__.py", line 37, in main
    manager.start()
  File "/Library/Python/2.7/site-packages/flexget/manager.py", line 299, in start
    self.initialize()
  File "/Library/Python/2.7/site-packages/flexget/manager.py", line 173, in initialize
    plugin.load_plugins(extra_dirs=[os.path.join(self.config_base, 'plugins')])
  File "/Library/Python/2.7/site-packages/flexget/plugin.py", line 425, in load_plugins
    _load_plugins_from_dirs(extra_dirs)
  File "/Library/Python/2.7/site-packages/flexget/plugin.py", line 381, in _load_plugins_from_dirs
    __import__(module_name)
  File "/Library/Python/2.7/site-packages/flexget/plugins/api/history.py", line 9, in <module>
    from flexget.api import api, APIResource
  File "/Library/Python/2.7/site-packages/flexget/api/__init__.py", line 310, in <module>
    loader.find_module(module_name).load_module(module_name)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/pkgutil.py", line 246, in load_module
    mod = imp.load_module(fullname, self.file, self.filename, self.etc)
  File "/Library/Python/2.7/site-packages/flexget/api/authentication.py", line 81, in <module>
    class LoginAPI(APIResource):
  File "/Library/Python/2.7/site-packages/flexget/api/authentication.py", line 83, in LoginAPI
    @api.response(401, 'Invalid username or password')
  File "/Library/Python/2.7/site-packages/flexget/api/__init__.py", line 147, in response
    return super(Api, self).response(code_or_apierror, description, model=model)
AttributeError: 'super' object has no attribute 'response'

It feels as though this must be related to this thing that landscape has been trying to tell us.

This might be an issue with the version of restplus you have installed...
How did you upgrade flexget? Via pip??
Can you run the below and paste the output
pip show flask-restplus

Yes, on OS X 10.11.
sudo -H pip install --install-option '--install-data=/usr/local' --ignore-installed six --upgrade flexget
And the output of pip show flash-restplus:
Hollis:~ mark$ pip show flask-restplus
---
Metadata-Version: 1.1
Name: flask-restplus
Version: 0.7.2
Summary: Helpers, syntaxic sugar and Swagger documentation for Flask-Restful
Home-page: https://github.com/noirbizarre/flask-restplus
Author: Axel Haustant
Author-email<EMAIL_ADDRESS>License: MIT
Location: /Library/Python/2.7/site-packages/flask_restplus-0.7.2-py2.7.egg
Requires: flask-restful

that's the issue. For some reason it's using an older version of flask-restplus..
We require 0.8.6 (https://github.com/Flexget/Flexget/blob/develop/pavement.py#L55)
I'm not sure why it didn't upgrade that package..
You can manually fix by pip install flask-restplus==0.8.6

Looks like it decided to install the old version regardless?
Collecting flask-restplus==0.8.6
  Downloading flask_restplus-0.8.6-py2.py3-none-any.whl (1.1MB)
    100% |████████████████████████████████| 1.1MB 162kB/s
Requirement already satisfied (use --upgrade to upgrade): aniso8601>=0.82 in /Library/Python/2.7/site-packages/aniso8601-1.1.0-py2.7.egg (from flask-restplus==0.8.6)
Requirement already satisfied (use --upgrade to upgrade): pytz in /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python (from flask-restplus==0.8.6)
Requirement already satisfied (use --upgrade to upgrade): jsonschema in /Library/Python/2.7/site-packages/jsonschema-2.5.1-py2.7.egg (from flask-restplus==0.8.6)
Requirement already satisfied (use --upgrade to upgrade): flask-restful>=0.3.2 in /Library/Python/2.7/site-packages/Flask_RESTful-0.3.5-py2.7.egg (from flask-restplus==0.8.6)
Requirement already satisfied (use --upgrade to upgrade): python-dateutil in /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python (from aniso8601>=0.82->flask-restplus==0.8.6)
Requirement already satisfied (use --upgrade to upgrade): functools32 in /Library/Python/2.7/site-packages (from jsonschema->flask-restplus==0.8.6)
Requirement already satisfied (use --upgrade to upgrade): Flask>=0.8 in /Library/Python/2.7/site-packages/Flask-0.10.1-py2.7.egg (from flask-restful>=0.3.2->flask-restplus==0.8.6)
Requirement already satisfied (use --upgrade to upgrade): six>=1.3.0 in /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python (from flask-restful>=0.3.2->flask-restplus==0.8.6)
Requirement already satisfied (use --upgrade to upgrade): Werkzeug>=0.7 in /Library/Python/2.7/site-packages/Werkzeug-0.11.2-py2.7.egg (from Flask>=0.8->flask-restful>=0.3.2->flask-restplus==0.8.6)
Requirement already satisfied (use --upgrade to upgrade): Jinja2>=2.4 in /Library/Python/2.7/site-packages/Jinja2-2.8-py2.7.egg (from Flask>=0.8->flask-restful>=0.3.2->flask-restplus==0.8.6)
Requirement already satisfied (use --upgrade to upgrade): itsdangerous>=0.21 in /Library/Python/2.7/site-packages/itsdangerous-0.24-py2.7.egg (from Flask>=0.8->flask-restful>=0.3.2->flask-restplus==0.8.6)
Requirement already satisfied (use --upgrade to upgrade): MarkupSafe in /Library/Python/2.7/site-packages (from Jinja2>=2.4->Flask>=0.8->flask-restful>=0.3.2->flask-restplus==0.8.6)
Installing collected packages: flask-restplus
  Found existing installation: flask-restplus 0.7.2
    Uninstalling flask-restplus-0.7.2:
      Successfully uninstalled flask-restplus-0.7.2
Successfully installed flask-restplus-0.7.2

Hmm, maybe make sure pip and setuptools are fully upgraded and try again?

that's weird.. maybe try uninstall first?  pip uninstall flask-restplus

I already upgraded pip to 8.0.3 and setuptools to 1.1.6. Using --force-reinstall made pip install 0.8.6.
This also fixed flexget, although it doesn't fix [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590) for me (which I would think would require a separate issue.)

yeah open another issue for that one.


data_disk_size not being honored w/ object_storage_scenario  (use --gce_boot_disk_size instead!)

Hi,
I am running object_storage_service benchmarks. I have noticed that the data_disk_size flag is not being honored, and all VMs are created on Google Cloud with 10 GB boot disks and no other secondary disks. Is the following syntax correct or am I missing something? Thank you in advance!
screen ./pkb.py --project=REDACTED \
--benchmarks=object_storage_service \
--machine_type=n1-standard-2 \
--data_disk_size=200 \
--data_disk_type=pd-ssd \
--object_storage_scenario=api_multistream \
--storage=GCP \
--zones=us-west1-b \
--object_storage_object_sizes=8MiB \
--object_storage_gcs_multiregion=us \
--run_uri=REDACTED \
--archive_bucket=REDACTED

2016-12-07 19:19:51,601 REDACTED Thread-7 object_storage_service(1/1) vm_util.py:284 DEBUG    Environment variables: None
2016-12-07 19:19:51,601 REDACTED Thread-7 object_storage_service(1/1) vm_util.py:287 INFO     Running: gcloud compute instances create pkb-REDACTED-0 --format json --quiet --project REDACTED --zone us-west1-b --network pkb-network-REDACTED --image ubuntu-14-04 --boot-disk-auto-delete --boot-disk-size 10 --boot-disk-type pd-standard --machine-type n1-standard-2 --tags perfkitbenchmarker --no-restart-on-failure --metadata-from-file sshKeys=/tmp/perfkitbenchmarker/runs/REDACTED/key-metadataBfO9LF --metadata owner=root
2016-12-07 19:20:25,136 REDACTED Thread-7 object_storage_service(1/1) vm_util.py:318 DEBUG    Ran gcloud compute instances create pkb-REDACTED-0 --format json --quiet --project REDACTED --zone us-west1-b --network pkb-network-REDACTED --image ubuntu-14-04 --boot-disk-auto-delete --boot-disk-size 10 --boot-disk-type pd-standard --machine-type n1-standard-2 --tags perfkitbenchmarker --no-restart-on-failure --metadata-from-file sshKeys=/tmp/perfkitbenchmarker/runs/REDACTED/key-metadataBfO9LF --metadata owner=root. Got return code (0).
STDOUT: [
  {
    "canIpForward": false,
    "cpuPlatform": "Intel Broadwell",
    "creationTimestamp": "2016-12-07T11:19:52.865-08:00",
    "disks": [
      {
        "autoDelete": true,
        "boot": true,
        "deviceName": "persistent-disk-0",
        "index": 0,
        "interface": "SCSI",
        "kind": "compute#attachedDisk",
        "licenses": [
          "https://www.googleapis.com/compute/v1/projects/ubuntu-os-cloud/global/licenses/ubuntu-1404-trusty"
        ],
        "mode": "READ_WRITE",
        "source": "pkb-REDACTED-0",
        "type": "PERSISTENT"
      }
    ],
    "id": "REDACTED",
    "kind": "compute#instance",
    "machineType": "n1-standard-2",
    "metadata": {
      "fingerprint": "HSWZ5Gibqk4=",
      "items": [
        {
          "key": "owner",
          "value": "root"
        },
        {
          "key": "sshKeys",
          "value": "perfkit:REDACTED"
        }
      ],
      "kind": "compute#metadata"
    },
    "name": "pkb-REDACTED-0",
    "networkInterfaces": [
      {
        "accessConfigs": [
          {
            "kind": "compute#accessConfig",
            "name": "external-nat",
            "natIP": "REDACTED",
            "type": "ONE_TO_ONE_NAT"
          }
        ],
        "name": "nic0",
        "network": "pkb-network-REDACTED",
        "networkIP": "REDACTED",
        "subnetwork": "https://www.googleapis.com/compute/v1/projects/REDACTED/regions/us-west1/subnetworks/pkb-network-REDACTED"
      }
    ],
    "scheduling": {
      "automaticRestart": false,
      "onHostMaintenance": "MIGRATE",
      "preemptible": false
    },
    "selfLink": "https://www.googleapis.com/compute/v1/projects/REDACTED/zones/us-west1-b/instances/pkb-REDACTED-0",
    "serviceAccounts": [
      {
        "email": "REDACTED",
        "scopes": [
          "https://www.googleapis.com/auth/cloud.useraccounts.readonly",
          "https://www.googleapis.com/auth/devstorage.read_only",
          "https://www.googleapis.com/auth/logging.write",
          "https://www.googleapis.com/auth/monitoring.write",
          "https://www.googleapis.com/auth/service.management.readonly",
          "https://www.googleapis.com/auth/servicecontrol"
        ]
      }
    ],
    "status": "RUNNING",
    "tags": {
      "fingerprint": "jEopUtn7ojQ=",
      "items": [
        "perfkitbenchmarker"
      ]
    },
    "zone": "us-west1-b"
  }
]

STDERR: WARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks#pdperformance.
WARNING: Image aliases are deprecated and will be removed in a future version. Please use --image-family=ubuntu-1404-lts and --image-project=ubuntu-os-cloud instead.
Created [https://www.googleapis.com/compute/v1/projects/REDACTED/zones/us-west1-b/instances/pkb-REDACTED-0].

2016-12-07 19:20:25,137 REDACTED Thread-7 object_storage_service(1/1) vm_util.py:284 DEBUG    Environment variables: None

The data_disk_size flag only applies to any secondary disks that get created *if* the benchmark makes use of secondary disks. Since object storage doesn't use a secondary disk, it doesn't use that flag. You *can* use the gce_boot_disk_size flag to control the boot disk size if you want to do that, but not all providers have a corresponding flag.

facepalm Thanks, @ehankland :) Closing this issue now.

Updated title too, so, it's clear for anyone else who falls into the same confused state that I did. Thanks again, @ehankland


routing specs not passing if using a namespaced engine

Given a namespaced engine:
module Alchemy
	class Engine < Rails::Engine
		isolate_namespace Alchemy
		engine_name 'alchemy'
	end
end

Also given a dummy app, where the engine is mounted into a namespace:
Rails.application.routes.draw do
	mount Alchemy::Engine => "/alchemy"
end

describe "The Routing", :type => :routing do

	describe "urls for downloads" do

		it "should have a named route" do
			{
				:get => "/alchemy/attachment/32/download/Presseveranstaltung.pdf"
			}.should route_to(
				:controller => "alchemy/attachments",
				:action => "download",
				:id => "32",
				:name => "Presseveranstaltung",
				:suffix => "pdf"
			)
		end
	end
end

Fails!
Testing it manually inside the same dumm app. It passes!
I also tried to include Alchemy::Engine.routes.url_helpers
No luck :(

Does it work in a rails functional test?

Yes, if I add :use_route => :alchemy they pass.
Tried to use the :use_route option inside the routes specs as well. No luck ;(

I really think this is a rails issue. You are using assert_recognizes and this seems not to handle routes from mounted engines correctly.

any progress on this?

Nope. Per @tvdeyen's comment, this is an issue with Rails' assert_recognizes. Closing this here. Please report the issue to the Rails tracker if it hasn't been reported already.


[Feature Requests]

I wish when I hit a bookmark the view wouldn't change automatically to "page fit" and would stick with the "automatic scaling" that I had chosen in the settings.
It would be great to add a bookmark within Foundry instead of doing it in acrobat.
It's unclear how to exit presentation mode without quitting the foundry.

3 - When I enter Presentation Mode, there is a box that appears at the top of the screen which says that pressing the "ESC" key will exit presentation mode. It works on my chrome browser on Windows 11.

Unfortunately, the way that information is stored within a PDF does not allow the easy detection of a section header. It would be a lot of work to implement this sort of thing, whereas using the Outline present in the PDF document is a much simpler solution (and is probably quite easy to add using any free PDF editor). Note that you can create links to a specific page within a PDF if that would suffice.

In the PDF Pager module settings, if "Default Zoom" is set to "None" then the default PDF behaviour will occur without the PDF Pager specifying any specific zoom level (I think that the default behaviour is that the zoom value set within the PDF viewer will be remembered for next time the PDF is opened).  If you set it to something other than "None", then the chosen value will always override the last-set zoom value for a particular PDF.

(1) has been fixed in PDF Pager version 0.40.0.   If an explicit zoom is set in the module settings then that will be retained when the PDF is opened from a link to one of the PDF's bookmarks.


Add support for BucketOwnershipControls

I would like to assert the ownership controls of my s3 bucket.
resource "aws_s3_bucket" "bucket" {
  bucket = "my-test-bucket-123"
}

resource "aws_s3_bucket_ownership_controls" "ownership" {
  bucket = aws_s3_bucket.bucket.id

  rule {
    object_ownership = "BucketOwnerEnforced"
  }
}

Can you add an output from the aws_s3_bucket_ownership_controls resource and check its value? Is this enough?

Thanks for clarifying!


Use the new c4doc_update() function, to save documents more efficiently

See https://github.com/couchbase/couchbase-lite-ios/pull/1785. When saving a document, instead of calling c4doc_put, call either c4doc_update or c4doc_create.

This is already taken care in the previous DB.


add got

https://github.com/sindresorhus/got

Moved to scalar/scalar: https://github.com/scalar/scalar/issues/2960


BOBA Gateway - ERC20 approval gas error

closed, he didn't have smart contracts turned on on ledger


AngularDart in DartPad

One of the pain points I find with AngularDart is that to test out any small thing, I need to create a new project or use a 'meta' angular project.
I can't back this up with any data but it seems like this would also be something of an issue for people who want to try out AngularDart but are new not just to AngularDart but to Dart itself.
For these reasons, I think having AngularDart work in DartPad would be immensely helpful.

As much as a I agree we don't have a lot of direct control over this right now :-/
Will keep open for triage when possible. Another issue is we only support a pre-compiled mode (no runtime compiler) formally, which means we'd need something a little more sophisticated than even just package: support.

It's unlikely this will happen at this point from our end (it requires a lot of coordination across the SDK we don't currently have). I'd love to explore other ways to give new users a way to try AngularDart without too much work (i.e. hosted on StackBlitz, etc).


If Windows path contains magic characters, like (, ], *, etc, the method may return undefined

On windows, if path contains ( ,], *, etc, trueCasePathSync method returns undefined.
The root cause is glob.sync recognize these chars as magic ones. It seems no options to disable the magic char []

Fixed in fork Profiscience/true-case-path, published in 2.0.0


Loader resolving issue

I am trying to build the example but I am running into some errors
running parcel index.html gives me this:
🚨  /<REDACTED>/example/example-crate/Cargo.toml: Cannot resolve dependency '/<REDACTED>/example/.cache/.cargo-web/loader-225fd694858c22a1024cc19dc9443f14.js' at '/<REDACTED>/example/.cache/.cargo-web/loader-225fd694858c22a1024cc19dc9443f14.js'
    at Resolver.resolve (/<REDACTED>/.nvm/versions/node/v9.8.0/lib/node_modules/parcel-bundler/src/Resolver.js:76:17)
    at <anonymous>

Node version: 9.8.0
Npm version: 5.6.0
Rustc version: 1.27.0-nightly
Cargo-web version: 0.6.10
Parcel version: 1.7.0
Parcel-plugin-cargo-web version: 0.1.0

Hey there, sorry for the delay, I have downloaded the repo on a completely new computer and still the same issue.
Steps taken:
npm i
npm run example
Error produced:
🚨  /<REDACTED>/parcel-plugin-cargo-web/example/example-crate/Cargo.toml: Cannot resolve dependency '/<REDACTED>/parcel-plugin-cargo-web/.cache/.cargo-web/loader-ad5b967d73891b35ae7d60158a86a470.js' at '/<REDACTED>/parcel-plugin-cargo-web/.cache/.cargo-web/loader-ad5b967d73891b35ae7d60158a8    at Resolver.resolve (/<REDACTED>/parcel-plugin-cargo-web/node_modules/parcel-bundler/src/Resolver.js:76:17)
    at <anonymous>

Versions:
Node: 9.4.0
Npm: 5.6.0
Rustc: 1.27.0-nightly
Cargo-web: 0.6.10
Parcel: 1.7.0

Can you post the line where you specify the parce plugin dependency in your
package.json?
On Sat, Apr 7, 2018 at 4:36 PM woowe<EMAIL_ADDRESS>wrote:

Hey there, sorry for the delay, I have downloaded the repo on a completely
new computer and still the same issue.
Steps taken:
npm i
npm run example
Error produced:
🚨  //parcel-plugin-cargo-web/example/example-crate/Cargo.toml: Cannot resolve dependency '//parcel-plugin-cargo-web/.cache/.cargo-web/loader-ad5b967d73891b35ae7d60158a86a470.js' at '//parcel-plugin-cargo-web/.cache/.cargo-web/loader-ad5b967d73891b35ae7d60158a8    at Resolver.resolve (//parcel-plugin-cargo-web/node_modules/parcel-bundler/src/Resolver.js:76:17)
at
Versions:
Node: 9.4.0
Npm: 5.6.0
Rustc: 1.27.0-nightly
Cargo-web: 0.6.10
Parcel: 1.7.0
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/koute/parcel-plugin-cargo-web/issues/4#issuecomment-379500935,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA80zFrX63y01heR_DrxlYEmvBKS8jezks5tmTFMgaJpZM4TJPjp
.

Absolutely, it is just the example in the repo:
"devDependencies": {
    "parcel-plugin-cargo-web": "file:.."
  }

Yep. Looks like it's broken with Parcel 1.7, and to me it looks like it's a bug in Parcel. Looks like Asset::addDependency broke (well, whatever code which uses what we put in addDependency broke...) and stopped accepting absolute paths.
Fixed and 0.2.0 published. (Well, hopefully it works.... I didn't test it out too thoroughly.)

I just re-downloaded this repo, ran the example and everything work! Wow, amazing job! Now I can test out parcel and rust -> wasm at the same time :smile: .

Great to hear that!
And thanks for the report!


How to use LSTM?

Hi, I checked the source code of the implementation of LSTM https://github.com/SciSharp/TensorFlow.NET/blob/8d7b85aa556344430ada57d335a26d81eba25c8a/src/TensorFlowNET.Keras/Layers/LSTM.cs#L31
Seems like LSTM does not work. If so, would you mind removing the interface or raising an error when using that?
Is there a way to support LSTM?

LSTM is not supported in Keras yet
But I found another implementation
https://github.com/SciSharp/TensorFlow.NET/blob/master/src/TensorFlowNET.Core/Operations/NnOps/BasicLSTMCell.cs#L14
I don’t know whether it works.

LSTM is not supported in Keras yet But I found another implementation https://github.com/SciSharp/TensorFlow.NET/blob/master/src/TensorFlowNET.Core/Operations/NnOps/BasicLSTMCell.cs#L14 I don’t know whether it works.

Is there a timeline for when LSTM will likely be supported in Keras.NET?

The new release version has been released, you can update your TensorFlow.NET and TensorFlow.Keras version to use LSTM and RNN. ^_^

Closing since no activity, please reopen if you still have question, thanks!


docs(react-component-groups): Creates overview page for extension.

Closes #79

I think at the top of this page, it should make it clear that the components in this section are coming from the @patternfly/react-component-groups package and link to this NPM page: https://www.npmjs.com/package/@patternfly/react-component-groups
It should also highlight that the code for these components lives in the following repo: https://github.com/patternfly/react-component-groups
So that is where issues should be filed for these components.

Does the "sortValue" param work at this nav level?

yeah - adding sortValue: 1 at the top of the markdown file as you have it here should work.
@edonehoo did it look like it was working to you?

@nicolethoen I haven't able to get my local build to work for this repo, so I'm not sure 😅


upload does not work on Bashed

I didn't try this on other machines, but the command upload is forwarded to the system.
no ask for file to upload.

If you are talking about the HackTheBox machine Bashed, it has the original version of phpbash which did not yet support direct file uploading.


Shortcut to change output layer

Hello,
is it possible to set a shortcut to change output layer file of Geo-SAM faster?
Thank you for your help in advance!

This feature might not be essential. You can modify the code as needed. Binding a shortcut key is straightforward. Define it in tools/widgetTool.py:
https://github.com/coolzhao/Geo-SAM/blob/c2c8b86a397dc183b63d07a7a84e3127d1430720/tools/widgetTool.py#L236-L260
And then unbind it in the unload function:
https://github.com/coolzhao/Geo-SAM/blob/c2c8b86a397dc183b63d07a7a84e3127d1430720/tools/widgetTool.py#L382-L399
To find the shortcut key binding, use QT Designer to open ui/Selector.ui. Click the button you want to bind, check its objectName

and find the corresponding connect function in tools/widgetTool.py (self.set_vector_layer in this case).
https://github.com/coolzhao/Geo-SAM/blob/c2c8b86a397dc183b63d07a7a84e3127d1430720/tools/widgetTool.py#L178


multi arch docker images

It seems the docker images on hub.docker are only for amd64.
It would be nice to make them multiarch and add support for: arm, arm64, ppc, s390x.
We've done with in CoreDNS, see https://github.com/coredns/coredns/blob/master/Makefile.release

Agreed. Looping @tianon in on this too.

I've had success with something like the following, but it requires building natively on all platforms: (which we'd be happy to help with if Prometheus wanted to participate in https://github.com/docker-library/official-images, which we'd also be happy to help facilitate)
FROM alpine:3.7

WORKDIR /opt/prometheus
ENV PATH /opt/prometheus:$PATH

# https://github.com/prometheus/prometheus/releases
ENV PROMETHEUS_VERSION 2.0.0

RUN set -ex; \
	\
	apk add --no-cache --virtual .fetch-deps \
		ca-certificates \
		libressl \
	; \
	\
	apkArch="$(apk --print-arch)"; \
	case "$apkArch" in \
		aarch64) promArch='arm64'   ;; \
		armhf)   promArch='armv6'   ;; \
		ppc64le) promArch='ppc64le' ;; \
		s390x)   promArch='s390x'   ;; \
		x86)     promArch='386'     ;; \
		x86_64)  promArch='amd64'   ;; \
	esac; \
	\
	wget -O /tmp/prom.tar.gz "https://github.com/prometheus/prometheus/releases/download/v${PROMETHEUS_VERSION}/prometheus-${PROMETHEUS_VERSION}.linux-${promArch}.tar.gz"; \
	tar \
		--extract \
		--file /tmp/prom.tar.gz \
		--strip-components 1 \
		--verbose \
	; \
	rm /tmp/prom.tar.gz; \
	\
	prometheus --version; \
	\
	apk del .fetch-deps

VOLUME /opt/prometheus/data

EXPOSE 9090
CMD ["prometheus"]

Otherwise, this should be pretty easy to accomplish with either cross-building (like what I believe that CoreDNS makefile is doing) or even multi-stage builds (perhaps with an ARG for "target architecture"):
FROM alpine:3.7 AS download

ARG arch=amd64

RUN apk add --no-cache libressl ca-certificates && wget "...-linux.$arch..." # ...

ARG from=amd64/alpine:3.7
FROM $from

COPY --from=download /path/to/prometheus /path/

CMD ["prometheus"]

then building via docker build --arg arch=386 --arg from=i386/alpine:3.7 ... for example

https://github.com/prometheus/promu/issues/89 is where to discuss this.


CI: Multicluster workflow fails full connectivity test

CI failure
Scheduled run on master, Cilium v1.12 dev cycle
https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true
cilium-sysdump-out.zip (8).zip
Run cilium connectivity test \
  cilium connectivity test \
    --context gke_***_us-west[2](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:2)-a_cilium--1969441281-mesh-1 \
    --multi-cluster gke_***_us-west2-a_cilium--1969441281-mesh-2 \
    --test '!/pod-to-.*-nodeport' \
    --test '!no-policies/pod-to-service' \
    --flow-validation=disabled
  shell: /usr/bin/bash -e {0}
  env:
    clusterName1: cilium--1969441281-mesh-1
    clusterName2: cilium--1969441281-mesh-2
    zone: us-west2-a
    firewallRuleName: cilium--1969441281-rule
    cilium_cli_version: v0.10.4
    check_url: https://github.com/cilium/cilium/actions/runs/1969441281
    CLOUDSDK_METRICS_ENVIRONMENT: github-actions-setup-gcloud
    GCLOUD_PROJECT: ***
    GOOGLE_APPLICATION_CREDENTIALS: /home/runner/work/cilium/cilium/ddb5617[3](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:3)ad0a00b99be[4](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:4)2ae8
    GOOGLE_GHA_CREDS_PATH: /home/runner/work/cilium/cilium/ddb[5](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:5)[6](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:6)1[7](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:7)3ad0a00b99be42ae[8](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:8)
✨ [gke_***_us-west2-a_cilium--1[9](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:9)69441281-mesh-1] Creating namespace for connectivity check...
✨ [gke_***_us-west2-a_cilium--1969441281-mesh-2] Creating namespace for connectivity check...
✨ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Deploying echo-same-node service...
✨ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Deploying echo-other-node service...
✨ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Deploying same-node deployment...
✨ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Deploying client deployment...
✨ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Deploying client2 deployment...
✨ [gke_***_us-west2-a_cilium--1969441281-mesh-2] Deploying echo-other-node service...
✨ [gke_***_us-west2-a_cilium--1969441281-mesh-2] Deploying other-node deployment...
⌛ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Waiting for deployments [client client2 echo-same-node] to become ready...
⌛ [gke_***_us-west2-a_cilium--1969441281-mesh-2] Waiting for deployments [echo-other-node] to become ready...
⌛ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Waiting for CiliumEndpoint for pod cilium-test/client-6488dcf5d4-ht45d to appear...
⌛ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Waiting for CiliumEndpoint for pod cilium-test/client2-5998d566b4-d7f25 to appear...
⌛ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Waiting for CiliumEndpoint for pod cilium-test/echo-same-node-745bd5c77-mr7lg to appear...
⌛ [gke_***_us-west2-a_cilium--1969441281-mesh-2] Waiting for CiliumEndpoint for pod cilium-test/echo-other-node-f4d46f75b-5ghsh to appear...
⌛ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Waiting for Service cilium-test/echo-same-node to become ready...
⌛ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Waiting for Service cilium-test/echo-other-node to become ready...
ℹ  Skipping IPCache check
⌛ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Waiting for pod cilium-test/client-6488dcf5d4-ht45d to reach default/kubernetes service...
⌛ [gke_***_us-west2-a_cilium--1969441281-mesh-1] Waiting for pod cilium-test/client2-5998d566b4-d7f25 to reach default/kubernetes service...
ℹ  Cilium version: 1.11.2
🏃 Running tests...

[=] Test [no-policies]
.
  [-] Scenario [no-policies/pod-to-pod]
  [.] Action [no-policies/pod-to-pod/curl-0: cilium-test/client-6488dcf5d4-ht45d ([10](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:10).68.1.191) -> cilium-test/echo-same-node-745bd5c77-mr7lg (<IP_ADDRESS>:8080)]
  🔥 Receiving flows from Hubble Relay: hubble client is not initialized
  🔥 Timeout waiting for flow listener to become ready

[=] Test [allow-all-except-world]

  ℹ  Cilium agent kube-system/cilium-d88lg logs since 2022-03-[11](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:11) 15:26:34.030476974 +0000 UTC m=+52.965328322:

  ℹ  Cilium agent kube-system/cilium-cg8pw logs since 2022-03-11 15:26:34.030476974 +0000 UTC m=+52.965328322:

  🔥 Error reading Cilium logs: error getting cilium-agent logs for kube-system/cilium-zzdq4: pods "gke-cilium--196944[12](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:12)81-m-default-pool-f7[13](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:13)cdce-vhn3" not found

[=] Test [client-ingress]

  ℹ  Cilium agent kube-system/cilium-cg8pw logs since 2022-03-11 15:26:35.174826784 +0000 UTC m=+54.109678232:

  🔥 Error reading Cilium logs: error getting cilium-agent logs for kube-system/cilium-zzdq4: pods "gke-cilium--1969441281-m-default-pool-f713cdce-vhn3" not found

[=] Test [echo-ingress]

  ℹ  Cilium agent kube-system/cilium-cg8pw logs since 2022-03-11 15:26:35.512152152 +0000 UTC m=+54.447003600:

  🔥 Error reading Cilium logs: error getting cilium-agent logs for kube-system/cilium-zzdq4: pods "gke-cilium--1969441281-m-default-pool-f713cdce-vhn3" not found

[=] Test [client-egress]

  ℹ  Cilium agent kube-system/cilium-cg8pw logs since 2022-03-11 15:26:36.427883323 +0000 UTC m=+55.362734671:

  🔥 Error reading Cilium logs: error getting cilium-agent logs for kube-system/cilium-zzdq4: pods "gke-cilium--1969441281-m-default-pool-f713cdce-vhn3" not found

[=] Test [to-entities-world]

  ℹ  Cilium agent kube-system/cilium-cg8pw logs since 2022-03-11 15:26:37.318676304 +0000 UTC m=+56.253527752:

  🔥 Error reading Cilium logs: error getting cilium-agent logs for kube-system/cilium-zzdq4: pods "gke-cilium--1969441281-m-default-pool-f713cdce-vhn3" not found

[=] Test [to-cidr-1111]

  ℹ  Cilium agent kube-system/cilium-cg8pw logs since 2022-03-11 15:26:38.218546354 +0000 UTC m=+57.153397802:
2022-03-11T15:26:38.628469906Z level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=83 subsys=rate uuid=bcc23b7e-2ebe-42a9-a9f6-8ffffd232a1a
2022-03-11T15:26:38.628516625Z level=info msg="API request released by rate limiter" name=endpoint-delete parallelRequests=83 subsys=rate uuid=bcc23b7e-2ebe-42a9-a9f6-8ffffd232a1a waitDurationTotal="56.118µs"
2022-03-11T15:26:38.628532962Z level=info msg="Delete endpoint request" containerID=5a16260ea8 subsys=daemon
2022-03-11T15:26:38.628541922Z level=info msg="Releasing key" key="[k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system k8s:io.cilium.k8s.policy.cluster=cilium--1969441281-mesh-1 k8s:io.cilium.k8s.policy.serviceaccount=kube-dns k8s:io.kubernetes.pod.namespace=kube-system k8s:k8s-app=kube-dns]" subsys=allocator
2022-03-11T15:26:38.628549890Z level=info msg="Removed endpoint" containerID=5a16260ea8 datapathPolicyRevision=1 desiredPolicyRevision=1 endpointID=1739 identity=93231 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/kube-dns-697dc8fc8b-g4b9t subsys=endpoint
2022-03-11T15:26:38.628559155Z level=info msg="API call has been processed" name=endpoint-delete processingDuration=3.009043ms subsys=rate totalDuration=3.078649ms uuid=bcc23b7e-2ebe-42a9-a9f6-8ffffd232a1a waitDurationTotal="56.118µs"

  🔥 Error reading Cilium logs: error getting cilium-agent logs for kube-system/cilium-zzdq4: pods "gke-cilium--1969441281-m-default-pool-f713cdce-vhn3" not found

[=] Test [echo-ingress-l7]

  ℹ  Cilium agent kube-system/cilium-6gppl logs since 2022-03-11 15:26:39.181[14](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:14)9982 +0000 UTC m=+58.116001330:

  ℹ  Cilium agent kube-system/cilium-d88lg logs since 2022-03-11 [15](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:15):26:39.181149982 +0000 UTC m=+58.1[16](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:16)001330:

  ℹ  Cilium agent kube-system/cilium-cg8pw logs since 2022-03-11 15:26:39.[18](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:18)1149982 +0000 UTC m=+58.116001330:
2022-03-11T15:26:39.47[19](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:19)56113Z level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=90 subsys=rate uuid=a1bbd476-221a-4cfa-a2c0-11db778e1065
[20](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:20)22-03-11T15:26:39.471998394Z level=info msg="API request released by rate limiter" name=endpoint-delete parallelRequests=90 subsys=rate uuid=a1bbd476-2[21](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:21)a-4cfa-a2c0-11db778e1065 waitDurationTotal="87.51µs"
20[22](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:22)-03-11T15:26:39.472008079Z level=info msg="API call has been processed" error="endpoint not found" name=endpoint-delete processingDuration="3.791µs" subsys=rate totalDuration="109.161µs" uuid=a1bbd476-221a-4cfa-a2c0-11db778e1065 waitDurationTotal="87.51µs"

  🔥 Error reading Cilium logs: error getting cilium-agent logs for kube-system/cilium-zzdq4: pods "gke-cilium--1969441281-m-default-pool-f713cdce-vhn3" not found

[=] Test [client-egress-l7]

  ℹ  Cilium agent kube-system/cilium-d88lg logs since 2022-03-11 15:26:40.453074365 +0000 UTC m=+59.387925713:

  ℹ  Cilium agent kube-system/cilium-cg8pw logs since 2022-03-11 15:26:40.453074365 +0000 UTC m=+59.387925713:
2022-03-11T15:26:40.457422200Z level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=90 subsys=rate uuid=0cbf06af-e10a-44f9-a7a4-33e138f24748
2022-03-11T15:26:40.457818373Z level=info msg="API request released by rate limiter" name=endpoint-delete parallelRequests=90 subsys=rate uuid=0cbf06af-e10a-44f9-a7a4-33e138f24748 waitDurationTotal="74.585µs"
2022-03-11T15:26:40.458089008Z level=info msg="API call has been processed" error="endpoint not found" name=endpoint-delete processingDuration="3.93µs" subsys=rate totalDuration="95.393µs" uuid=0cbf06af-e10a-44f9-a7a4-33e138f24748 waitDurationTotal="74.585µs"

  🔥 Error reading Cilium logs: error getting cilium-agent logs for kube-system/cilium-zzdq4: pods "gke-cilium--1969441281-m-default-pool-f713cdce-vhn3" not found

[=] Test [dns-only]

  ℹ  Cilium agent kube-system/cilium-cg8pw logs since 2022-03-11 15:26:42.65796095 +0000 UTC m=+61.59281[23](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:23)98:

  🔥 Error reading Cilium logs: error getting cilium-agent logs for kube-system/cilium-zzdq4: pods "gke-cilium--1969441281-m-default-pool-f713cdce-vhn3" not found

[=] Test [to-fqdns]

  ℹ  Cilium agent kube-system/cilium-cg8pw logs since 2022-03-11 15:26:44.72028455 +0000 UTC m=+63.655135898:
2022-03-11T15:26:45.254302653Z level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=90 subsys=rate uuid=01d47ac8-6e86-4304-aaf4-54b9bd0cedc9
2022-03-11T15:26:45.254435023Z level=info msg="API request released by rate limiter" name=endpoint-delete parallelRequests=90 subsys=rate uuid=01d47ac8-6e86-4304-aaf4-54b9bd0cedc9 waitDurationTotal="75.222µs"
2022-03-11T15:26:45.256105045Z level=info msg="API call has been processed" error="endpoint not found" name=endpoint-delete processingDuration="3.774µs" subsys=rate totalDuration="97.638µs" uuid=01d47ac8-6e86-4304-aaf4-54b9bd0cedc9 waitDurationTotal="75.222µs"
2022-03-11T15:26:45.298935071Z level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=90 subsys=rate uuid=2f7219f8-dc55-4726-a6cf-3c050b62235f
2022-03-11T15:26:45.299012849Z level=info msg="API request released by rate limiter" name=endpoint-delete parallelRequests=90 subsys=rate uuid=2f7219f8-dc55-4726-a6cf-3c050b62235f waitDurationTotal="70.221µs"
2022-03-11T15:26:45.299025862Z level=info msg="API call has been processed" error="endpoint not found" name=endpoint-delete processingDuration="3.279µs" subsys=rate totalDuration="90.477µs" uuid=2f7219f8-dc55-4726-a6cf-3c050b62235f waitDurationTotal="70.221µs"

  🔥 Error reading Cilium logs: error getting cilium-agent logs for kube-system/cilium-zzdq4: pods "gke-cilium--1969441281-m-default-pool-f713cdce-vhn3" not found

📋 Test Report
❌ 11/11 tests failed (1/1 actions), 0 tests skipped, 0 scenarios skipped:
Test [no-policies]:
  ❌ no-policies/pod-to-pod/curl-0: cilium-test/client-6488dcf5d4-ht45d (<IP_ADDRESS>) -> cilium-test/echo-same-node-745bd5c77-mr7lg (10.68.1.[24](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:24)2:[80](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:80)80)
Test [allow-all-except-world]:
Test [client-ingress]:
Test [echo-ingress]:
Test [client-egress]:
Test [to-entities-world]:
Test [to-cidr-[111](https://github.com/cilium/cilium/runs/5512765844?check_suite_focus=true#step:20:111)1]:
Test [echo-ingress-l7]:
Test [client-egress-l7]:
Test [dns-only]:
Test [to-fqdns]:
Connectivity test failed: 11 tests failed
Error: Process completed with exit code 1.

Error reading Cilium logs: error getting cilium-agent logs for kube-system/cilium-zzdq4: pods "gke-cilium--1969441281-m-default-pool-f713cdce-vhn3" not found

Seems like a pre-emptible nodes issue.

^^ I am going to treat this as the same as #19120 based on the above observation.


[FEATURE] Supports changing playback speed

It would be nice to have support for changing the playback speed for the track being played, like on YT.

natan's lavadsp lib can achieve that

Closing since already possible.


Make diagnostic plots work with one-parameter models

fixes https://github.com/stefanradev93/BayesFlow/issues/135
Just ensuring that we can loop over ax even when it's returned by plt.subplots(nrows=1, ncols=1). There is some code duplication between different plots, but I just made a simple fix where needed; it doesn't seem that bad to warrant a larger refactor just yet 🙂

Thanks, Simon! No worries, we are currently refactoring the backend massively.
@LarsKue Tests seem to still be failing. Any idea why?


UUID IS INCORRECT: TRANSLATION ERROR

Flux Networks Version: 3.0.11
Minecraft: 1.12.2
Forge: 2705
Pack: FTB Revelation 2.0.0
After experiencing the bug from #225 (and restarting the game obviously) i could not interact with the storage cell, as it displayed this error message.
I am uncertain, if this is connected to the prior issue or not.
best regards

Addendum
Sonarcore 5.0.10

Duplicate #215 - Are you sure this is 3.0.11?

yes

NBT reading&writing probably was mismatched in some patch. Use hasTag(string name) to see if a NBTTagCompound actually has the tag you want

i think here is a bug too
users cant make a private or restricted channel in network....
only public can they use and if u try to delete the channel it says it isnt yours
https://files.ilikepudding.de/zub34yj7gm.mp4
https://screen.ilikepudding.de/win6mafvcp.png

as the triggering effect does not exist anymore ( #225 )
i am unable to reproduce this as well.

Fixed in later versions, anyone still encountering on the latest versions will be due to blocks being placed prior to the SonarCore fix, so break blocks, place again.


ghauri asks for user input (y/n) even when I have used --batch argument

Describe the bug
@r0oth3x49  ghauri asks for user input (y/n) even when I have used --batch argument
My command:
ghauri -r req.txt --dbs --confirm --timeout 10 --threads 30 --level 3 --flush-session --fresh-queries --batch
Ghauri Output:

Expected behavior
--batch             Never ask for user input, use the default behavior
There should be a default behavior for everything when using --batch
It's breaking my automation workflow. If at some point the ghauri asks for any input, then the whole automation will break as ghauri will be expecting an input (y/n) whereas it should have taken the default input as N or Y itself as I have already added --batch argument.
Related issue that was fixed earlier: https://github.com/r0oth3x49/ghauri/issues/100
Desktop:

OS: [Debian]
Ghauri version: latest 1.2.9
Type of SQL injection which cause the error: [Default]

@r0oth3x49 ping

It will only ask in case of cookies.

Will check and add batch

Sometimes batch do not work.


Week date format anomaly

Using Moment 2.9.0 moment('2014-12-29').format('YYYY-MM') should display 2014-52 but instead it displays 2014-01.

I believe what you are looking for is this...
moment('2014-12-22').format("YYYY-ww");

Thanks for the digging and the response. I agree that 2014-12-29 is considered a first week. And yes, I also tend to agree it is the first week of the new year. But shouldn't it be the first week of 2015 then
and be formatted as 2015-01?

I'm not sure if 'bug' is the proper classification here. It all depends what one expects from the format() function.
Obviously the behavior is caused only with the last week of a year overlaps to the new year. Apparently the format() function parses the template string token by token, without considering them in the logical context of the date. In my example it first parses the 'YYYY' token and establishes the year to be 2014. It then parses the 'MM' token and establishes the week to be 01. Literally speaking, both are absolutely correct. But when combined, the result is not what one would logically expect. At least I don't :)
Fortunately there is a simple workaround for my case. By applying an 'End of Time' operation before formatting, I get the proper result. So moment('2014-12-29').endOf('week').format('YYYY-MM') displays 2015-01, just as I expect.

I think there are a couple levels of confusion here. First, "MM" is months, not weeks, so it's never going to be 52. For me it's 12, as expected:
> moment('2014-12-29').format('YYYY-MM')
'2014-12'

If you want weeks, use "WW" or "ww"; one is ISO weeks and the other is local weeks. (I suspect you actually meant that but typed it into Github wrong.) Anyway, onto the real problem:
> moment('2014-12-29').format('YYYY-WW')
'2014-01'

That's not what you want, but it's caused by mixing calendar years with weeks. Think of the tokens in Moment as evaluating independently: the "YYYY" piece doesn't know you also care about weeks, just that it should display the year, which is 2014. The "WW" part says "It's the first week of the year!"; it has no idea that you're also printing the calendar year. Fortunately, Moment supports week years, which is exactly what you want:
> moment('2014-12-29').format('GGGG-WW')
'2015-01'

Which matches the results @talymo got. (If you used "ww" above instead, use "gggg" to use the local week year.) The lesson here is to be careful about what definition of "year" you're using.

Thanx for your elaborate reply and I apologize for the 'MM' vs 'WW' confusion. Thanx also for pointing me in the right direction with 'GGGG' for week years. I somehow missed that or perhaps the difference with 'YYYY' didn't quite sink in while reading the documentation.


I installed the extensions and im not getting the option to add machine learning to my project

Problem encountered on https://dotnet.microsoft.com/learn/ml-dotnet/get-started-tutorial/create
Operating System: windows
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
I installed the extensions and im not getting the option to add machine learning to my project.
running on windows

Duplicate #206

We're tracking this issue with #206. Thanks for reporting!