change 0.5 quantile from mean to median

This changes the 0.5 quantile from mean to median.
According to the documentation (https://prometheus.io/docs/practices/histograms/#quantiles) the 0.5 quantile is the median.

https://www.statsdirect.com/help/nonparametric_methods/quantiles.htm


Why is GPU Utilization low with Spark-Rapids Accelerator

What is your question?
Why is GPU Utilization low with Spark-Rapids Accelerator

What's the reason for this? Who can tell me

How do I troubleshoot GPU utilization issues？@revans2

@TenBid please don't assume that low GPU utilization is a problem. It can indicate that there is a problem, but it does not guarantee that there is a problem.
If you have specific goals for a query in terms of speedup or cost reduction, then please start there and see if the query you want to run is sped up enough by the GPU to hit your desired goals. If not, then we should look into why it is slow. Not why is the GPU not fully utilized.
https://docs.nvidia.com/spark-rapids/user-guide/latest/tuning-guide.html#tuning-guide is a good place to start to look into tuning your jobs. We also have an auto-tuner utility.
Typically when I look at the performance for a GPU job I first look at what operators are placed on the GPU and which ones are not. Like I said before your driver logs should indicate by default which part of the plan were on the CPU and why. Having operations on the CPU also does not guarantee that the performance is less than ideal. It really only matters if a lot of rows are going through sections that are not on the GPU.
If everything is on the GPU, then look to see if you are I/O bound. Is network or disk the thing that makes it so your query cannot go any faster. This is typically done by looking at system level metrics instead of looking at what is in Spark itself.
Like I said before it can mean that your query is blocked on I/O more than it is on compute. This might also include spilling. If Spark does not have enough memory to hold all of the data for a task that data might spill to disk. That is also true of the GPU and is one place that we can see a lot of performance problems. This does show up in Spark metrics on each individual task page.
I hope this helps.


SCM plugins

This is rework pull requests https://github.com/drone/drone/pull/793 and https://github.com/drone/drone/pull/785
This PR allow move scm logic outside build package, to create a simple scm implementations inside drone.
Also has been added scm "local", because when docker add files from root user, non-root users doesn't have write access to this files. For now, files with source adds to /tmp/drone_cache and then we use rsync to copy files inside build directory rsync -rt /tmp/drone_cache/ /var/cache/drone/src/github.com/drone/drone. Local scm needed for https://github.com/drone/drone/issues/749#issuecomment-67302820 if we want to set $DRONEPATH when we use drone cli

@Bugagazavr have a look at https://github.com/drone/drone/pull/785#issuecomment-69507212
I've been thinking that the remote plugin should be responsible for determining the clone commands. This allows us to easily handle, for example, different pull request logic per remote. The allows the remote to query for extra data required to clone the PR instead of storing extra fields in the database (like source repo and source branch required for GitLab PR testing).
We probably wouldn't need to store scm in the database. We can look at the Bitbucket SSH URL to determine Git vs Mercurial. If we added a Google Code remote it could lookup the VCS using the same method as Go's go get command.
It is definitely something I'd like to explore.

I don't think all hosting services can be managed by one set of command per SCM especially for Pull Request. For me, each remote plugin must define its own commands like I did in #871


Let's join forces!

I'm the author of probably the most popular jQuery slugify plugin on Github.
https://github.com/pmcelhaney/jQuery-Slugify-Plugin
It has some features that this one doesn't. And it has better i18n support thanks to many community contributions over the years.
But it lacks unit tests and isn't registered in Bower.
Rather than creating a competing Bower component, I would like to propose we study the differences between the two plugins, and port as many features as possible from mine to yours. Once that's done I'll "retire" the old project. I'll update the readme and point everyone here instead.
Sound good?

Conversation on Twitter that led to this request:
https://twitter.com/joshua_hornby/status/571635302441332737

Hi there! This sounds good. Open Source for the win!
I created this plugin because I needed the functionality for a project with Bower support and I wanted to get to known the jQuery plugin development stack with something usefull.
Most of the other snippets out there converted the german äöü incorrectly (So does yours at the moment as far as I am concerned ;) ).
The basic idea seems to be the same - probably you script was one of the few I reviewed at the time. I believe missing the  slugFunc in the settings would be a regression for your users - so this should be one of the things to be merged.

Great. I've logged three features that I think need to be added before I can point my users here. Should be pretty simple.

I have tinkered with the idea to separate the concerns DOM Manipulation (jquery plugin) and the "slugifying" by integrating https://github.com/pid/speakingurl. The library already supports the #6 lang attribute feature and many more features. In my opinion this feels better than copying the code and I introduce own bugs.
I pushed the changes to the master branch for testing and discussion (probably should have created a separate branch).
I have written some tests for the lang attribute feature, introduced a slugFunc function and updated the demo page.
I am not quite sure if I got the idea of the slugFunc pattern you created. I just hacked something and it worked :S ...

Oh, wow, SpeakingURL is cool! Yes, that's a great idea to reuse open source code. I've updated the readme on my version to point people here.

:+1:


How do I use the same name and Bundle ID for my iOS and MacOS app? Can anyone help?

How do I use the same name and Bundle ID for my iOS and MacOS app? Can anyone help?

@anchao-lu Your question is better suited for support channels like Stackoverflow or Flutter's reddit help age.
Closing, as this is more of a how to question rather than bug or feature request.


As a user, I want my search input for publication year to be validated in the browser so that I can't enter invalid dates.

testing notes
colors will probably change on this.

on the search page, if you enter a number in either of the publication date boxes that is outside the min/max date range for the archive, you should get a red halo around the input box
you should also see a "please enter a 4-digit year between XXXX and YYYY" validation message below the inputs
the form should not submit and nothing should happen when the inputs are invalid.

dev notes
semantic ui validation docs
Broke this issue off of @mnaydan comment on #65 .

We probably need more input from designer (or from @mnaydan or project team) on how best to do this. Do we want it to look like a popup, like this one?

Currently the fields will turn red, like this:

What else is necessary?

@thatbudakguy right now the min range works well (when you try to press the down arrow it does nothing, the up arrow increases the numbers) but the max range is wonky. It goes from 1922 to 1559 when you press the up OR down arrow. The up arrow should do nothing and the down arrow should make the numbers descend from 1922.
I think having them turn red and not submitting the form upon invalid entry is good. We could have a popup to the right of the field that says "Please enter a year between 1559 and 1922". I'm happy to get @rlskoeser or designer input on this...

marking this "question" while we talk about design options for it.

Going to change to "tested needs attention." Feel free to close it out if you're fine with that pop up. I think there's bigger fish to fry unless it's an easy fix.

@mnaydan what browser/device?

@thatbudakguy Chrome/Macbook for the popup. Haven't tried to see if I can get it to pop up on tablet/mobile or in firefox. I did find this design issue on iPad though, which is prolly a separate issue.

hmm, I can't replicate the popup in chrome on my macbook. I think I'm OK with the redundant messaging, but thanks for catching the text wrapping bug. I'll try to fix it as part of #112 .


proposal: context: notification callback for cancelled/expired contexts

This proposal originates in discussion on #36503.
Contexts carry a cancellation signal. (For simplicity, let us consider a context past its deadline to be cancelled.)
Using a context's cancellation signal to terminate a blocking call to an interruptible but context-unaware function is tricky and inefficient. For example, it is possible to interrupt a read or write on a net.Conn or a wait on a sync.Cond when a context is cancelled, but only by starting a goroutine to watch for cancellation and interrupt the blocking operation. While goroutines are reasonably efficient, starting one for every operation can be inefficient when operations are cheap.
I propose that we add the ability to register a function which is called when a context is cancelled.
package context

// OnDone arranges for f to be called in a new goroutine after ctx is cancelled.
// If ctx is already cancelled, f is called immediately.
// f is called at most once.
//
// Calling the returned CancelFunc waits until any in-progress call to f completes,
// and stops any future calls to f.
// After the CancelFunc returns, f has either been called once or will not be called.
//
// If ctx has a method OnDone(func()) CancelFunc, OnDone will call it.
func OnDone(ctx context.Context, f func()) CancelFunc

OnDone permits a user to efficiently take some action when a context is cancelled, without the need to start a new goroutine in the common case when operations complete without being cancelled.
OnDone makes it simple to implement the merged-cancel behavior proposed in #36503:
func WithFirstCancel(ctx1, ctx2 context.Context) (context.Context, context.CancelFunc) {
	ctx, cancel := context.WithCancel(ctx1)
	stopf := context.OnDone(ctx2, func() {
		cancel()
	})
	return ctx, func() {
		cancel()
		stopf()
	}
}

Or to stop waiting on a sync.Cond when a context is cancelled:
func Wait(ctx context.Context, cond *sync.Cond) error {
	stopf := context.OnDone(ctx, cond.Broadcast)
	defer stopf()
	cond.Wait()
	return ctx.Err()
}

The OnDone func is executed in a new goroutine rather than synchronously in the call to CancelFunc that cancels the context because context cancellation is not expected to be a blocking operation. This does require the creation of a goroutine, but only in the case where an operation is cancelled and only for a limited time.
The CancelFunc returned by OnDone both provides a mechanism for cleaning up resources consumed by OnDone, and a synchronization mechanism. (See the ContextReadOnDone example below.)
Third-party context implementations can provide an OnDone method to efficiently schedule OnDone funcs. This mechanism could be used by the context package itself to improve the efficiency of third-party contexts: Currently, context.WithCancel and context.WithDeadline start a new goroutine when passed a third-party context.

Two more examples; first, a context-cancelled call to net.Conn.Read using the APIs available today:
// ContextRead demonstrates bounding a read on a net.Conn with a context
// using the existing Done channel.
func ContextRead(ctx context.Context, conn net.Conn, b []byte) (n int, err error) {
	errc := make(chan error)
	donec := make(chan struct{})
        // This goroutine is created on every call to ContextRead, and runs for as long as the conn.Read call.
	go func() {
		select {
		case <-ctx.Done():
			conn.SetReadDeadline(time.Now())
			errc <- ctx.Err()
		case <-donec:
			close(errc)
		}
	}()
	n, err = conn.Read(b)
	close(donec)
	if ctxErr := <-errc; ctxErr != nil {
		conn.SetReadDeadline(time.Time{})
		err = ctxErr
	}
	return n, err
}

And with context.OnDone:
func ContextReadOnDone(ctx context.Context, conn net.Conn, b []byte) (n int, err error) {
	var ctxErr error
        // The OnDone func runs in a new goroutine, but only when the context expires while the conn.Read is in progress.
	stopf := context.OnDone(ctx, func() {
		conn.SetReadDeadline(time.Now())
		ctxErr = ctx.Err()
	})
	n, err = conn.Read(b)
	stopf()
        // The call to stopf() ensures the OnDone func is finished modifying ctxErr.
	if ctxErr != nil {
		conn.SetReadDeadline(time.Time{})
		err = ctxErr
	}
	return n, err
}

It is worth noting that OnDone is a performance optimization. We can write it today in terms of the existing context package. The benefit of adding it to the package is that it permits us to take action on context cancellation without leaving a goroutine sitting around waiting for the cancel to happen.
func OnDone(ctx context.Context, f func()) context.CancelFunc {
	stopc := make(chan struct{}, 1)
	donec := make(chan struct{})
	go func() {
		select {
		case <-ctx.Done():
			f()
		case <-stopc:
		}
		close(donec)
	}()
	return func() {
		select {
		case stopc <- struct{}{}:
		default:
		}
		<-donec
	}
}

The ContextReadOnce example is still a bit awkward, in the sense that there are a few things that have to be done exactly right to avoid any problems.  Perhaps we can tighten up the idea, at the cost of another closure.
// Try executes fn while watching ctx.  If ctx is cancelled, Try calls cancel and returns ctx.Err().
// Otherwise, Try returns the result of fn.
// This is implemented using an internal implementation of OnDone as described above.
func Try(fn func() error, cancel func()) error

// Example of using Try.
func ContextReadOnDone(ctx context.Context, conn net.Conn, b []byte) (n int, err error) {
    err = context.Try(func() error {
       n, err = conn.Read(b)
    }, func() {
        conn.SetReadDeadline(time.Now())
    })
    return n, err
}

Try does look quite elegant to use. I don't think it would work for the WithFirstCancel case, and in general Try can be implemented in terms of WithDone but not vice-versa, so if we were to have only one I'd vote for OnDone.
func Try(ctx context.Context, fn func() error, cancel func()) error {
    stopf := context.OnDone(ctx, cancel)
    err := fn()
    stopf()
    if ctx.Err() != nil {
        return ctx.Err()
    }
    return err
}

The Try function looks a lot like the os/exec functionality added for #50436.

Try is analogous to (*exec.Cmd).Wait.
The fn argument is analogous to the subprocess itself.
The cancel argument is analogous to the exec.Cmd.Cancel field.

Based on that analogy, I would suggest a slightly different implementation of Try in terms of OnDone:
func Try(ctx context.Context, fn func() error, cancel func()) error {
	canceled := false
	stop := context.OnDone(ctx, func() {
		cancel()
		canceled = true
	})
	err := fn()
	stop()
	if canceled && err == nil {
		return ctx.Err()
	}
	return err
}

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

This seems similar to having time.AfterFunc to avoid making a goroutine that calls time.Sleep and then the function. Here we avoid making a goroutine that receives from ctx.Done and then calls the function. Perhaps it should be context.After or AfterFunc?
context.After(ctx, func() { println("ctx is done!") })

reads nicely to me. It's nice that this would let people implement context.Merge themselves at no efficiency cost compared to the standard library.
We should specify that f is always run in a goroutine by itself, at least semantically, even in the case where
// If ctx is already cancelled, f is called immediately.

f shouldn't be called by context.After in that case either.

I like context.After

After is nice and short, but I think I prefer context.AfterFunc for consistency with time.AfterFunc.

This may be implied, but to clarify since I don't see it in the example... After/AfterFunc should return a CancelFunc like the initial OnDone proposal.

OK, so it sounds like the signature is
package context
func AfterFunc(ctx Context, f func()) (stop func() bool)

AfterFunc arranges to call f after ctx is done (cancelled or timed out), and it calls f in a goroutine by itself. Even if ctx is already done, calling AfterFunc does not wait for f to return.
Multiple calls to AfterFunc on a given ctx are valid and operate independently; one does not replace another.
Calling stop stops the association of ctx with f. It reports whether the call stopped f from being run.
If stop returns false, then the context is already done and the function f has been started in its own goroutine; stop does not wait for f to complete before returning. If the caller needs to know whether f is completed, it must coordinate with f explicitly.
(This last paragraph is adapted from time.Timer.Stop.)
Do I have that right? Anything wrong there?

I'd prefer to have calling stop wait until f is completed if it has already started, since that makes using AfterFunc in a race-free manner simpler; you're guaranteed that after a call to stop, f either has run or will not run. But it doesn't make a difference in most of the motivating examples so perhaps consistency with time.AfterFunc is preferable.

Even if ctx is already done, calling AfterFunc does not wait for f to return.

I find this sentence a bit off when I read it. If I understand the proposal, calling AfterFunc never waits for f to return. The above sentence seems to emphasize the corner case of ctx already being done, though. That emphasis makes it seem like there is a special case involved, but there really isn't. Consider rewording to:

Calling AfterFunc does not wait for f to return, even if ctx is already done.

I think this better emphasizes that the behavior is always the same while still pointing out the less than obvious corner case.

While naming returned func stop looks reasonable to avoid confusion with already existing cancel func, I think name stop isn't a good one for this use case.
Moreover, as stop is related to f, then stop() == false may be misunderstood as "f is running now".
To me cancel still sounds much more suitable here, and as we've some confusion in both cases then maybe it's too early to reject cancel from name candidates.
As for other names… maybe detach, unhook, revoke, prevent?

@powerman stop is the same name as the time.Timer.Stop method.
@neild, what if f is long-running? Then there's no way to stop the AfterFunc without waiting for f? And in particular defer stop() now can't be used? I guess defer func() { go stop() }() is possible but it seems like mixing concerns.

If f is long-running, then you'd need to make arrangements to interrupt it.
If you do want a long-running f, and a stop that doesn't wait for it, you can start a goroutine for the long-running operation explicitly:
started := false
stop := context.AfterFunc(ctx, func() {
  started = true
  go longRunningOperation()
})
stop()
if started {
  // longRunningOperation is in progress
}

This is less convenient than a non-blocking stop (and a bit less efficient), but I think it's also the less common case. Every motivating example I've come up for AfterFunc is fast--signaling a sync.Cond, setting a timeout on a net.Conn, etc.
A non-blocking stop makes it easier to inadvertently leak a long-running operation. In general, functions should clean up any goroutines they start before returning. A blocking stop ensures that the AfterFunc isn't left running unless the programmer takes specific steps to create a goroutine for it, as above.
A non-blocking stop can also make the common case quite a bit more subtle, and possibly less efficient. Taking the case of reading from a net.Conn, we need to create a channel to synchronize with the AfterFunc goroutine even in the common case where the AfterFunc is not called:
func ContextReadOnDone(ctx context.Context, conn net.Conn, b []byte) (n int, err error) {
	stopped := make(chan struct{})
	stopf := context.AfterFunc(ctx, func() {
		conn.SetReadDeadline(time.Now())
		close(stopped)
	})
	n, err = conn.Read(b)
	if !stopf() {
		// stopf may still be running, so we need to wait for it to finish before resetting the conn deadline.
		//
		// Failing to wait here means that we might return with a still-running goroutine which will set the
		// conn deadline at some point in the future (if we have a race between Read returning successfully
		// and the context expiring).
		<-stopped
		conn.SetReadDeadline(time.Time{})
		err = ctx.Err()
	}
	return n, err
}

@neild you second example is great, but first one looks very racy:
started := false
stop := context.AfterFunc(ctx, func() {
  started = true
  go longRunningOperation()
})
stop()
if started {
  // longRunningOperation is in progress
}

TBH I don't remember outcome from last change in go.dev/ref/mem (i.e. is it safe to read/write int-sized vars like bool), but even if it's safe callback can be started by context.AfterFunc but didn't execute it's first operation started = true yet, so there is a race here anyway. Probably worth rewriting, because, you know, people will copy-paste it from here too. :)

@powerman The first example assumes a stop function which blocks until any in-progress call to f has completed. The call to stop synchronizes access to the started var; after stop returns, either the func has run and set started = true or it will never run and started remains false.

But isn't blocking stop still returns bool which can be used instead of extra started var?

A blocking stop could return a bool indicating whether f ran or not, but there's less need for it. A non-blocking stop must provide a way to tell whether f has been started.

A blocking stop can easily lead to deadlocks, especially if these functions are trying to send on channels to notify other goroutines that the context is cancelled. A non-blocking stop won't, and it matches time.Timer.Stop.  I'm not entirely sure how to decide between those benefits and the ones @neild has pointed out.

Perhaps a non-blocking stop to match time.Timer.Stop, plus the Try function proposed by @ianlancetaylor above to handle the cases where you want to synchronize on the AfterFunc?
// Try executes fn while watching ctx.  If ctx is cancelled, Try calls cancel and returns ctx.Err().
// Otherwise, Try returns the result of fn.
func Try(fn func() error, cancel func()) error

Alternatively, AfterFunc could return a type with Stop and Wait methods. Or Stop could return something that can be waited on. (func AfterFunc(f func()) func() func()?)

It seems unusual to me to have to wait for the stop function.  And it is after all not too hard to do if you need to.  So maybe we could start with a non-blocking stop function.

I agree. Users can use a WaitGroup or channel to wait on the function if
they wish, right?
On Wed, Mar 8, 2023 at 7:25 PM Ian Lance Taylor @.***>
wrote:

It seems unusual to me to have to wait for the stop function. And it is
after all not too hard to do if you need to. So maybe we could start with a
non-blocking stop function.
—
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/57928#issuecomment-1461076353, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACKIVXKKYXOJUH5B2XTJYF3W3EPPTANCNFSM6AAAAAAUAY4XW4
.
You are receiving this because you commented.Message ID:
@.***>

Sounds like consensus is in favor of a non-blocking stop, which does have the advantage of matching time.AfterFunc. And you can build a blocking one atop the non-blocking one easily enough if necessary.

Non-blocking stop it is. Have all remaining concerns about this proposal been addressed?

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group

It'd be helpful to update the initial post with the naming and semantics decided on in the thread.

Current version of the proposal (will link to this from the initial post):
package context

// AfterFunc arranges to call f in a new goroutine after ctx is done (cancelled or timed out).
// If ctx is already done, f is called immediately in a new goroutine.
//
// Multiple calls to AfterFunc on a context operate independently; one does not replace another.
//
// Calling the returned stop function stops the association of ctx with f.
// It returns true if the call stopped f from being run.
// If stop returns false, either the context is done and f has been started in its own goroutine; or f was already stopped.
// The stop function does not wait for f to complete before returning.
// If the caller needs to know whether f is completed, it must coordinate with f explicitly.
//
// If ctx has a method AfterFunc(func()) func() bool, AfterFunc will call it.
func AfterFunc(ctx Context, f func()) (stop func() bool)

(Calling stop multiple times always returns false after the first call; this matches time.Timer.Stop.)

If the context has a method AfterFunc(func()) func() bool, will AfterFunc only call that method and not do anything else?

One thing that wasn't discussed yet is how this proposal interact with #40221 (context.WithoutCancel)?
IIUC, the function supplied in AfterFunc is still called, which means that using AfterFunc to do anything with context values (like closing a trace span) is going to be problematic if context.WithoutCancel is ever used. I know that it's possible to do everything that context.AfterFunc is doing, but I wonder if it's going to be more attractive to assume that context's have a life-cycle that can be hooked into, while at the same time a method exists to escape a context from that life-cycle.
Internally at Google, we have a solution that adds a different life-cycle hook that to do work during context detaching (e.g. to open a new trace span for a background go routine), assuming the right context detaching method is used.
It's probably worth a separate proposal, but I do wonder if the implementation of this proposal is going to make it more complicated to add detaching functionality later. To be clear, I don't know the answer to that question.

AfterFunc(ctx, f) calls f after ctx is done. If ctx is the result of WithoutCancel, it never becomes done and f will never be called.
WithoutCancel(parent) creates a new context. It does not affect the cancelation of the parent context, and will not interfere with functions registered with AfterFunc on the parent context.
parent, cancel := context.WithCancel(context.Background())
context.AfterFunc(parent, func() {
  fmt.Println("parent canceled")
})
child := context.WithoutCancel(parent)
context.AfterFunc(child, func() {
  fmt.Println("child canceled") // this will never be called
})
cancel()
// Prints "parent canceled" and nothing else.

Got it. Do you think it might makes sense to be explicit about the fact that the function might never be called? That might dissuade its use in cases like this:
func dispatchRequest(ctx context.Context) {
  ctx, cancel = context.WithCancel(ctx)
  defer cancel()
  handleRequest(ctx)
}

func handleRequest(ctx context.Context) {
  var span trace.Span
  ctx, span = tracer.Start(ctx, "operation")
  context.AfterFunc(ctx, span.End)
  backgroundAction(ctx)
}

func backgroundAction(ctx context.Context) {
  ctx = context.WithoutCancel(ctx)
  go someLibraryFunc(ctx)
}

func someLibraryFunc(ctx context.Context) {
  span = trace.SpanFromContext(ctx) // <--- span likely ended already, updates are not allowed
}

Arguably, this issue already exists today. I am wondering if it will be worse, because it's too easy to assume that context.AfterFunc is going to do something different.

I only just saw this issue; sorry for the late comment.
I'm not entirely sure whether the semantics of stop are correct here (and I'm not convinced that Timer.Stop is good precedent, because that API is notoriously error-prone and hard to use.
An alternative semantic could be:
// The stop function reports whether the function has been successfully stopped; that is, it returns false
// if and only if the function has been invoked already.

That makes it feasible to call stop multiple times concurrently and have consistent results between them, and it seems to me like a simpler invariant to explain.
I'm wondering what the use case is for knowing whether this is the stop call that prevented the function running.

@rogpeppe Thanks, I suggest that you open that in a new issue, as this semantics has already been implemented.  We can make the new issue a release blocker for 1.21.  Thanks.

@ianlancetaylor Thanks. Done.


Drawer in tab bar

How do I implement a drawer in my tab bar, right now my implementation renders my tab bar above the drawer, is it even possible to use this framework in a tab bar in the first place?

Does this become the answer ?
DrawerSample.zip

Sorry I only see a tab bar with Favourites and More
On Sun, 13 Mar 2016 at 21:07 kyo__hei<EMAIL_ADDRESS>wrote:

Does this become the answer ?
DrawerSample.zip
https://github.com/ykyouhei/KYDrawerController/files/170974/DrawerSample.zip
—
Reply to this email directly or view it on GitHub
https://github.com/ykyouhei/KYDrawerController/issues/39#issuecomment-195954414
.

Basically this is my current problem, my tab bar is "on top" of the drawer

Please try this sample to the reference
Sample.zip

@ykyouhei yes but then it doesn't give simplest code to open drawer with above simple hierarchy of button click means we first need to find Drawercontroller then only we can active state to open


Enforce coding standard

As discussed, this PR forces the project to follow the PER Coding Style 2.0 standard using the new CI pipeline.
I chose php-cs-fixer over phpcs because it can automatically format the code, not just detect violations. I chose the PER standard because it's not very opinionated compared to Symfony or PhpCsFixer's own ruleset. The actual rules applied by each ruleset can be browsed here.
As a development convenience I also introduced a composer lint command to easily format the code from the command line.
Strict Types
We could take this opportunity to force the declaration of strict types on all classes ('declare_strict_types' => true). It's not strictly a backwards-compatible change (if existing users of nostr-php are not calling some methods of the library correctly), but strict types straight out prevent whole hosts of bugs.
I think strict types are always worth it, but I left them out of the PR for now. I'd like other people's input on this.

@1ma Could you do a reroll and fix the conflicts?

I've pushed the strict types in a separate commit https://github.com/swentel/nostr-php/pull/39/commits/b72efcd3ba88e8702beed02097b70e8cb9ed6477.
If it's a no-go I can drop it again, but as I said I think it's very much worth it.

Yes I like strict coding. Just tested it, works like a charm.
I don't expect a lot of broken things when this is merged.


Bridge: Sequence is red although no error is reported

Environment

Client OS (e.g., Linux, macOS, Windows):
Keptn Version (keptn version):
Kubernetes Cloud Provider (e.g., GKE, AKS):
Kubernetes version (kubectl version):

Affected Component

[ ] Docs
[ ] CLI
[ ] Kubernetes Integration
[ ] Openshift Integration
[ ] Helm
[ ] Istio
[x] Bridge
[ ] Approval
[ ] Datastore
[ ] REST API
[ ] eventbroker / distributor
[ ] jmeter

Describe the bug
A delivery sequence was correctly completed, but it is marked in red. Also, the deployment box has a red border.
To Reproduce
Configure a webhook subscription on sh.keptn.event.deployment.finished.  Insert a wrong variable for the webhook payload. Trigger a deployment sequence.
Expected behavior
The sequence should not be marked with an error state since an integration failed but it didn't stop the sequence to proceed.
Screenshots

A possible solution is to use only task events to determine the result of a sequence. The list of available task for a given project can be fetched using /bridge/api/project/{project}/tasks

The fix now limits the determination of failed results. For that, it uses the list of tasks and sequences of the shipyard file.
e.g. sh.keptn.event.dev.delivery.finished, sh.keptn.event.deployment.finished
Limitations:

The original bug occurred because of a nested sh.keptn.event.deployment.finished.finished event that was sent from the webhook-service. When this gets fixed, the event will fail the task / sequence again - but it will be then visible in the task list.
get-sli will always succeed a sequence, even if the task failed. It is not defined in the shipyard.yaml file.


2 new sumbissions (1 french, 1 english)

What does this PR do?
Add 2 new resources + 1 link correction of a previous submission
For resources
Description

In French : Added book Maîtriser Ethereum : Développer des contrast Intelligents et des DApps
In English : Added book Mastering the Lightning Network

Why is this valuable (or not)?
Both books are CC-BY-SA and not on this repo list
How do we know it's really free?
Both books are CC-BY-SA with the license copy on the repos
For book lists, is it a book? For course lists, is it a course? etc.
Both are books
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Duplicate of #6858


vm-repair extension URGENT bug fix for os_image_reference.version None case

Fixes errors when source VM's os image version is None.
=> Clients waiting for this issue to be resolved.

Now logging stack trace app insights

fixed minor scenario testing bugs

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT<EMAIL_ADDRESS>

Travis is failing with the error "CLIError: Please run 'az login' to setup account." on the scenario tests. They run fine locally. What is the issue here? @zikalino

@haroldrandom  please help with the PR.

src/vm-repair/azext_vm_repair/tests/latest/test_repair_commands.py has been modified but without updating recoding YAML files.

src/vm-repair/azext_vm_repair/tests/latest/test_repair_commands.py has been modified but without updating recoding YAML files.

The recording files were removed a few PRs back because the recorded tests will not work for this extension's case because it uses subprocess to run other CLI commands.

I believe your midification on  test_repair_commands.py has effected tests.
One way to test is that try to modify scripts/ci/test_source.py to test only your extensions to see if the output like CI or not.
The scripts/ci/test_source.py is try to run python -m unittest discover -v {YOUR_EXTENSION_PATH}
BTW, if test is not working, why not comment them out or delete the test_repair_commands.py

src/vm-repair/azext_vm_repair/tests/latest/test_repair_commands.py has been modified but without updating recoding YAML files.
The recording files were removed a few PRs back because the recorded tests will not work for this extension's case because it uses subprocess to run other CLI commands.
I believe your midification on  test_repair_commands.py has effected tests.
One way to test is that try to modify scripts/ci/test_source.py to test only your extensions to see if the output like CI or not.
The scripts/ci/test_source.py is try to run python -m unittest discover -v {YOUR_EXTENSION_PATH} on two situations: when you login and when you are not login.
Please share your results.
BTW, if test is not working, why not comment them out or delete the test_repair_commands.py

Test Results

When Logged in: Works as expected without failure

When logged out: I get the error:
knack.util.CLIError: Please run 'az login' to setup account.
for all tests.
-> Why am i running the tests while logged out? Isn't the CI set up so that this is taken care of while running the tests live?

I am keeping these tests because I need to run them live before pushing out a new version.

CI won't be able to run live without credentias after you login.
I would suggest you those uncessary tests our or add recoding files together since they are are passed without failure now.

CI won't be able to run live without credentias after you login.
I would suggest you those uncessary tests our or add recoding files together since they are are passed without failure now.

Harold, why do you say these tests are unnecessary. We need to run these scenario tests to run live before merging to validate them. These tests have been in the repository from the first version of this extension. It is not like I just added them in this PR. Why is it failing all of a sudden?
Also it is indicated https://github.com/Azure/azure-cli/blob/dev/doc/authoring_tests.md#nightly-live-test-run here that tests are run live through CI.
Please a client is still waiting for this PR to go in from last week. Is there any way to speed up this process? We are waiting 10 hours for each other's response due to the time zone difference.

2 Solutions:

First live-run test on your local machine. If all test pass, run it again in non-live mode. If it pass too, upload your recording YAML files to see CI pass or not
Subclass LiveScenarioTest instead of ScenarioTest. let CI skip your tests.

Updated the test class to inherit LiveScenarioTest not ScenarioTest. This will make the CI skip recorded testing and pass the tests. Thanks for all the help @haroldrandom


[RESOLVED] High ICMP ping response time

Problem started at 15:28:16 on 2023.07.26
Problem name: High ICMP ping response time
Host: ST-FG
Severity: Warning
Operational data: Value: 329ms
Original problem ID: 33127
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23135&eventid=33127

Problem has been resolved in 3m 0s at 15:31:16 on 2023.07.26
Problem name: High ICMP ping response time
Host: ST-FG
Severity: Warning
Original problem ID: 33127


Add page about how to display Polars dataframes with itables

Link to suggestion
https://mwouts.github.io/itables/polars_dataframes.html
Targeted section
Tutorials & workshops
Describe your suggestion

How to display Polars dataframes with itables - A tutorial that explains how to display Polars dataframes with itables by @mwouts.

Checklist

[X] checked if your suggestion is not already listed in Awesome Polars list.
[X] checked if it can fit in an existed section or suggest a new section and explain why your item does not fit into one and what would be the interest of your new section.
[X] checked when it's a repository if it's maintained (archived repository will be rejected).

@mwouts your documentation about Polars and itables will be added to the Awesome Polars List


maintain key order when dumping

One-line summary
Maintain ordering of keys in the spec as defined in the dictionary. Current/previous behavior was alphabetical.
Types of Changes
This could be seen as breaking change, but I'd argue that changing the order of keys in an object should be fine.

Can't see why it can be considered as breaking. LGTM.

👍


Drop target window lacks title bar or any description indicating what app the window belongs to

Recommend adding more information to distinguish the window as belonging to Comic Zipper and what will happen when folders are dropped here.

I've actually been experimenting with adding an arrow image, but it's been kind of low priority

Any graphic resources you need? I haven't looked at how it's implemented yet, but the text description really should be more specific.

Well, I'd appreciate an arrow image with a dashed border, like the one above. And also, I'm thinking, maybe a blue one to use as a highlight indicator, instead of having the whole window get highlighted? (I saw a similar thing in another app recently, look good.)
The text description is easy to fix, but I think you need a balance between a minimalistic approach and a more verbose.

Wouldn't an Image Well work with something like this:

I did a quick and dirty test. And it displays. I need to figure out auto layout/resizing though.

OK, I didn't find an auto-layout for image well but t found a pretty tutorial on auto-layout images on drop views:
https://www.youtube.com/watch?v=73oeuEgoBL4
You need to add the image in your Drop View class.

Bitmap or vector image?
I thought the sample text was a good balance between too much info and not enough. You could drop "comic book archive" or alternately the "CBZ" to reduce word count but it seemed short enough to me.

Oh, that's all right, it's not hard at all to add the image. You just need to use an NSImageView and add it to the window along with an NSTextField and then auto layout them. Thank you!

I figured out the NSImageView and did quick test with a png that I quickly knocked out/cribbed. But I couldn't figure out how to get IB to handle moving it with the text (auto layout?).  I was stuck thinking it required code to move it on window resize.

You must set the add constraints (auto layout) to the image with relations to the main view. This can be done in IB, but I'm currently creating all the elements and auto layouts programmatically (but may go over to have all the objects ready in different views that'll replace each other depending on user action).

Are you going to use a vector image (presumably PDF) or convert the drop targets to PNGs? None of my desktops/laptop have retina displays but I assume vector is preferred nowadays.
What is the minimum OS version for CZ so far? I assume you're using some classes/methods that require OS X 10.x (where x>0). Notifications require 10.8, but I haven't looked to see if you provided a fallback.

I use png, which is I think recommended. Looks great on my retina display. Vector is usually more resource heavy.
I think minimum is 10.8, but I haven't tested the new rewritten app on it.

Is AppCleaner the app you were referencing for the blue highlight on drag? If so I have the color now.
Interestingly, he uses a single black-on-white PDF vector image for the drop target, so he must be handling color dynamically for both states (gray-on-white and blue-on-white).
[github will not allow me to attach the pDF file even though that is a format that they supposedly support.]

Here's an alternate idea that combines the file icon design but maximizes size/clarity by using a dated folder outline:

Made the folder outline a little clearer:

I added the DropHere pngs you sent a couple of hours ago, to the latest build. They're not retina though.

Those were just placeholders until you decided which one you liked. I'll make a clean version with 2x.


VantagePointTree.findEpsilonNeighbours fails when the point is in the tree

The next test because when the objective point is already in the tree.If I put a point not in the tree works ok
it should "find the points in a ball around excluding himself" in {

    Given("some points")
    val points = Seq(
      RNDensePoint(0, 0),
      RNDensePoint(0, 1),
      RNDensePoint(0, 2)
    )

    And("the tree with the points")
    val tree = VantagePointTree(points, RNDensePoint.euclidean)

    And("an objetive point")
    val objetive = RNDensePoint(0, 1)

    And("the ball radio")
    val radio = 4.0

    And("the expected results")
    val expected = Set(
      RNDensePoint(0, 0),
      RNDensePoint(0, 1),
      RNDensePoint(0, 2)
    )

    When("the tree find points in the ball")
    val closestPoints = tree.findEpsilonNeighbours(objetive, radio)

    Then("the nearest must be the expected")
    closestPoints.toSet shouldBe expected
  }

I successfully reproduced this behavior. The query cannot deal with different points at equal distance to the objective point ([0, 0] and [0, 2] are both at distance 1 of [0, 1]). I identified the root cause to be a wrong ordering used in the query structure here. A fix is currently being tested.


Adding support for nav

Hey @Sakshamkhandelwal123, thanks for your time in making a contribution.
It looks like you need to review our contributing guide and modify your pull request to follow those guidelines. Specifically, you need to add:

a changeset
a pull request description

Additionally, the colors used do not fit the style of water.css and the styles used also accidentally modify the <li> elements in the Goals section of the deploy preview page.

I'm marking this as invalid but feel free to modify this pull request or open a new one if you're able to make these changes.


Best practices around mixed C++ and JS

It is natural for a primarily C++ node module to contain some pure JS functions or wrappers. It is critical that these are documented and tested as well as the C++.
Let's build in examples of JS wrappers, ensure code coverage tracks them, and documentation builds respect them.

[ ] Docs: https://github.com/mapnik/node-mapnik/pull/683 is an example by @mapsam and @davidtheclark getting this working. But could the docs be included inside the JS and still have things work?
[ ] Coverage: unclear to me (@springmeyer) how to get this working but the first thing to try would be to depend on instanbul (https://github.com/istanbuljs/istanbul-lib-instrument) and see if it can merge its results somehow with lcov.

FWIW node-tap can easily generate coverage reports, including LCOV files and is generally a great library.

This is still relevant, but blue sky and less urgent that getting the basics working which are being tracked at https://github.com/mapbox/node-cpp-skel/issues/50#issuecomment-314522275


One-To-Many relation unexpected behavior when not defining foreign key

I am trying to define a one-to-many relationship as follows:
public class BloggingContext : DbContext
    {
        public BloggingContext(DbContextOptions<BloggingContext> options)
            : base(options)
        { }

        public DbSet<Blog> Blogs { get; set; }
        public DbSet<Post> Posts { get; set; }

        protected override void OnModelCreating(ModelBuilder modelBuilder)
        {
            modelBuilder.Entity<Post>().HasOne(b => b.Blog).WithMany().IsRequired().OnDelete(DeleteBehavior.Cascade);
            base.OnModelCreating(modelBuilder);
        }
    }

    [Table("Blogs")]
    public class Blog
    {
        public int BlogId { get; set; }
        public string Url { get; set; }
    }

    [Table("Posts")]
    public class Post
    {
        public int PostId { get; set; }
        public string Title { get; set; }
        public string Content { get; set; }

        public Blog Blog { get; set; }
    }

The EF defined the relation as required by adding a new column BlogId as a foreign key
but when trying to create the Post below:
{
  "postId": 0,
  "title": "Post1",
  "content": "First post",
  "blog": {
    "blogId": 1
   }
}

and I have previously created a Blog with Id = 1, the exception below is thrown

SqlException: Cannot insert explicit value for identity column in table 'Blogs' when IDENTITY_INSERT is set to OFF.

which mean that EF tries to create the referenced blog.

@hebagomaah Reading between the lines, I'm guessing that you are doing the equivalent of this:
var blog = new Blog { BlogId = 1};
var post = new Post { Blog = blog };
context.Add(post);
context.SaveChanges();

In this case both Blog and Post are treated as new entity instances that need to be inserted. Instead you can use Attach such that the key being set will indicate that the Blog actually already exists:
var blog = new Blog { BlogId = 1};
var post = new Post { Blog = blog };
context.Attach(post);
context.SaveChanges();

See also #13575, https://docs.microsoft.com/en-us/ef/core/saving/related-data, and https://docs.microsoft.com/en-us/ef/core/saving/disconnected-entities


Add # operator to the Type.Function

I think that this operator can be useful. For example it is already defined (but named differently) in the context of React.Basic.Hooks:
https://github.com/spicydonuts/purescript-react-basic-hooks/blob/fde4198f55bbf2b6d95ecd7d0614510b9089658b/src/React/Basic/Hooks/Internal.purs#L188
Could you please tell me what do you think? Should I provide this simple PR?

Please do not add it. # still refers to Row. We'll deprecate that in
the next breaking changes and then can add uh. That's why I didn't do that
in the PR.

Thanks for quick response Jordan! I'm going to close this then.


🐛 [cloud_firestore] Android: Firestore cannot re-establish connection after some time (or change of network)

Bug report
Describe the bug
Technically, I am not 100% sure if the issue is caused by cloud_firestore, or in fact if it is caused by the combination of workflows within firestore.
My users have complained that the Android app keeps losing connection to the firestore snapshot (as well as individual document.get() queries) after they switch from mobile data to WiFi. Even if they continue to stay on the same network, but keep the application in the background, when they open the app again - the connection is lost.
Steps to reproduce
I would like to highlight that the device is not offline. The device is in fact online, and I can confirm with various other applications installed on the same device. The issue is very easily reproducible and happens frequently on Android. I have not received any reports of such errors from iOS users (using the same code-base). The problem occurs in a couple of these scenarios:

When you change your device network. If you are on mobile data and switch to WiFi (or vice versa), chances are that all firestore calls will fail. All my users are reportedly restarting the app when this happens. Also, please note that this has only been observed on Android.

When you keep the app alive in the background. If the user opens the app after a while, the app will fail to connect to firestore. After about 20-25 seconds, firestore connection finally gets established, and then everything comes back to normal.

Expected behavior
Firestore should not lose connection and all snapshots and get queries should still be successful after network change/open the app after a while from the background.

Additional context
These are the logs that I have been able to capture. Note how the application is trying to re-establish the connection and it keeps failing. After multiple retries, towards the end, the connection is established and everything works fine. The logs are not complete, and only show you the last 14 seconds of interaction before the connection is successfully re-established. Actual duration was well more than 30 seconds before the user could re-establish the connection.
I am surprised that this issue is not reported by other Flutter users, is there something wrong with my setup?
04-11 03:07:02.149  2899  3876 D FreecessController: UFZ : com.vetfinder.onepetstop(4843)
04-11 03:07:12.169  2899  4868 D FreecessController: FZ : com.vetfinder.onepetstop(4843)
04-11 03:09:57.800  2899  3896 D FreecessController: UFZ : com.vetfinder.onepetstop(4843)
04-11 03:09:57.809  4843  9700 V NativeCrypto: Read error: ssl=0x76a9c7f648: I/O error during system call, Software caused connection abort**
04-11 03:09:58.117  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=End of stream or IOException, cause=null}.
04-11 03:09:58.139  4843 11105 V NativeCrypto: Write error: ssl=0x76a9c7f648: I/O error during system call, Broken pipe
04-11 03:09:58.150  4843 11105 V NativeCrypto: SSL shutdown failed: ssl=0x76a9c7f648: I/O error during system call, Success
04-11 03:10:07.414  2899  3014 D FreecessController: FZ : com.vetfinder.onepetstop(4843)
04-11 03:14:01.533  2899  5081 D FreecessController: UFZ : com.vetfinder.onepetstop(4843)
04-11 03:14:01.536  4843 11105 V NativeCrypto: Read error: ssl=0x757fe88f48: I/O error during system call, Software caused connection abort
04-11 03:14:01.544  4843 11103 V NativeCrypto: Write error: ssl=0x757fe88f48: I/O error during system call, Broken pipe
04-11 03:14:01.546  4843 11103 V NativeCrypto: Write error: ssl=0x757fe88f48: I/O error during system call, Broken pipe
04-11 03:14:01.547  4843 11103 V NativeCrypto: SSL shutdown failed: ssl=0x757fe88f48: I/O error during system call, Success
04-11 03:14:01.551  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=End of stream or IOException, cause=null}.
04-11 03:14:53.642  2899  3014 D FreecessController: FZ : com.vetfinder.onepetstop(4843)
04-11 03:15:31.781  2899  5081 D FreecessController: UFZ : com.vetfinder.onepetstop(4843)
04-11 03:15:31.803  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=null, cause=java.net.ConnectException: failed to connect to firestore.googleapis.com/<IP_ADDRESS> (port 443) from /:: (port 52582): connect failed: ECONNABORTED (Software caused connection abort)
04-11 03:15:31.803  4843  5164 W Firestore:     at libcore.io.IoBridge.connect(IoBridge.java:143)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.net.Socket.connect(Socket.java:621)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.net.Socket.connect(Socket.java:570)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.net.Socket.<init>(Socket.java:450)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.net.Socket.<init>(Socket.java:250)
04-11 03:15:31.803  4843  5164 W Firestore:     at javax.net.DefaultSocketFactory.createSocket(SocketFactory.java:285)
04-11 03:15:31.803  4843  5164 W Firestore:     at h.b.l1.h$d.run(Unknown Source:56)
04-11 03:15:31.803  4843  5164 W Firestore:     at h.b.k1.y1.run(Unknown Source:11)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
04-11 03:15:31.803  4843  5164 W Firestore:     at java.lang.Thread.run(Thread.java:919)
04-11 03:15:31.803  4843  5164 W Firestore: Caused by: android.system.ErrnoException: connect failed: ECONNABORTED (Software caused connection abort)
04-11 03:15:31.803  4843  5164 W Firestore:     at libcore.io.Linux.connect(Native Method)
04-11 03:15:31.803  4843  5164 W Firestore:     at libcore.io.ForwardingOs.connect(ForwardingOs.java:95)
04-11 03:15:31.803  4843  5164 W Firestore:     at libcore.io.BlockGuardOs.connect(BlockGuardOs.java:136)
04-11 03:15:31.803  4843  5164 W Firestore:     at libcore.io.ForwardingOs.connect(ForwardingOs.java:95)
04-11 03:15:31.803  4843  5164 W Firestore:     at libcore.io.IoBridge.connectErrno(IoBridge.java:157)
04-11 03:15:31.803  4843  5164 W Firestore:     at libcore.io.IoBridge.connect(IoBridge.java:135)
04-11 03:15:31.803  4843  5164 W Firestore:     ... 15 more
04-11 03:15:31.803  4843  5164 W Firestore: }.
04-11 03:15:31.862  4843 11105 W h.b.k1.c1: [{0}] Failed to resolve name. status={1}
04-11 03:15:31.892  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=null, cause=java.net.ConnectException: failed to connect to firestore.googleapis.com/<IP_ADDRESS> (port 443) from /:: (port 52582): connect failed: ECONNABORTED (Software caused connection abort)
04-11 03:15:31.892  4843  5164 W Firestore:     at libcore.io.IoBridge.connect(IoBridge.java:143)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.net.Socket.connect(Socket.java:621)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.net.Socket.connect(Socket.java:570)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.net.Socket.<init>(Socket.java:450)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.net.Socket.<init>(Socket.java:250)
04-11 03:15:31.892  4843  5164 W Firestore:     at javax.net.DefaultSocketFactory.createSocket(SocketFactory.java:285)
04-11 03:15:31.892  4843  5164 W Firestore:     at h.b.l1.h$d.run(Unknown Source:56)
04-11 03:15:31.892  4843  5164 W Firestore:     at h.b.k1.y1.run(Unknown Source:11)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
04-11 03:15:31.892  4843  5164 W Firestore:     at java.lang.Thread.run(Thread.java:919)
04-11 03:15:31.892  4843  5164 W Firestore: Caused by: android.system.ErrnoException: connect failed: ECONNABORTED (Software caused connection abort)
04-11 03:15:31.892  4843  5164 W Firestore:     at libcore.io.Linux.connect(Native Method)
04-11 03:15:31.892  4843  5164 W Firestore:     at libcore.io.ForwardingOs.connect(ForwardingOs.java:95)
04-11 03:15:31.892  4843  5164 W Firestore:     at libcore.io.BlockGuardOs.connect(BlockGuardOs.java:136)
04-11 03:15:31.892  4843  5164 W Firestore:     at libcore.io.ForwardingOs.connect(ForwardingOs.java:95)
04-11 03:15:31.892  4843  5164 W Firestore:     at libcore.io.IoBridge.connectErrno(IoBridge.java:157)
04-11 03:15:31.892  4843  5164 W Firestore:     at libcore.io.IoBridge.connect(IoBridge.java:135)
04-11 03:15:31.892  4843  5164 W Firestore:     ... 15 more
04-11 03:15:31.892  4843  5164 W Firestore: }.
04-11 03:15:32.994  4843 11075 W h.b.k1.c1: [{0}] Failed to resolve name. status={1}
04-11 03:15:33.945  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:15:33.945  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:119)
04-11 03:15:33.945  4843  5164 W Firestore:     at h.b.k1.b0$d.a(Unknown Source:138)
04-11 03:15:33.945  4843  5164 W Firestore:     at h.b.k1.b0$d.run(Unknown Source:42)
04-11 03:15:33.945  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
04-11 03:15:33.945  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
04-11 03:15:33.945  4843  5164 W Firestore:     at java.lang.Thread.run(Thread.java:919)
04-11 03:15:33.945  4843  5164 W Firestore: Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:15:33.945  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:124)
04-11 03:15:33.945  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
04-11 03:15:33.945  4843  5164 W Firestore:     at java.net.InetAddress.getAllByName(InetAddress.java:1152)
04-11 03:15:33.945  4843  5164 W Firestore:     at h.b.k1.b0$b.a(Unknown Source:0)
04-11 03:15:33.945  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:13)
04-11 03:15:33.945  4843  5164 W Firestore:     ... 5 more
04-11 03:15:33.945  4843  5164 W Firestore: }.
04-11 03:15:34.441  4843 11075 W h.b.k1.c1: [{0}] Failed to resolve name. status={1}
04-11 03:15:36.255  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:15:36.255  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:119)
04-11 03:15:36.255  4843  5164 W Firestore:     at h.b.k1.b0$d.a(Unknown Source:138)
04-11 03:15:36.255  4843  5164 W Firestore:     at h.b.k1.b0$d.run(Unknown Source:42)
04-11 03:15:36.255  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
04-11 03:15:36.255  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
04-11 03:15:36.255  4843  5164 W Firestore:     at java.lang.Thread.run(Thread.java:919)
04-11 03:15:36.255  4843  5164 W Firestore: Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:15:36.255  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:156)
04-11 03:15:36.255  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
04-11 03:15:36.255  4843  5164 W Firestore:     at java.net.InetAddress.getAllByName(InetAddress.java:1152)
04-11 03:15:36.255  4843  5164 W Firestore:     at h.b.k1.b0$b.a(Unknown Source:0)
04-11 03:15:36.255  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:13)
04-11 03:15:36.255  4843  5164 W Firestore:     ... 5 more
04-11 03:15:36.255  4843  5164 W Firestore: Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
04-11 03:15:36.255  4843  5164 W Firestore:     at libcore.io.Linux.android_getaddrinfo(Native Method)
04-11 03:15:36.255  4843  5164 W Firestore:     at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:74)
04-11 03:15:36.255  4843  5164 W Firestore:     at libcore.io.BlockGuardOs.android_getaddrinfo(BlockGuardOs.java:200)
04-11 03:15:36.255  4843  5164 W Firestore:     at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:74)
04-11 03:15:36.255  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:135)
04-11 03:15:36.255  4843  5164 W Firestore:     ... 9 more
04-11 03:15:36.255  4843  5164 W Firestore: }.
04-11 03:15:36.927  4843 11075 W h.b.k1.c1: [{0}] Failed to resolve name. status={1}
04-11 03:15:48.195  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:15:48.195  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:119)
04-11 03:15:48.195  4843  5164 W Firestore:     at h.b.k1.b0$d.a(Unknown Source:138)
04-11 03:15:48.195  4843  5164 W Firestore:     at h.b.k1.b0$d.run(Unknown Source:42)
04-11 03:15:48.195  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
04-11 03:15:48.195  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
04-11 03:15:48.195  4843  5164 W Firestore:     at java.lang.Thread.run(Thread.java:919)
04-11 03:15:48.195  4843  5164 W Firestore: Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:15:48.195  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:156)
04-11 03:15:48.195  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
04-11 03:15:48.195  4843  5164 W Firestore:     at java.net.InetAddress.getAllByName(InetAddress.java:1152)
04-11 03:15:48.195  4843  5164 W Firestore:     at h.b.k1.b0$b.a(Unknown Source:0)
04-11 03:15:48.195  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:13)
04-11 03:15:48.195  4843  5164 W Firestore:     ... 5 more
04-11 03:15:48.195  4843  5164 W Firestore: Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
04-11 03:15:48.195  4843  5164 W Firestore:     at libcore.io.Linux.android_getaddrinfo(Native Method)
04-11 03:15:48.195  4843  5164 W Firestore:     at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:74)
04-11 03:15:48.195  4843  5164 W Firestore:     at libcore.io.BlockGuardOs.android_getaddrinfo(BlockGuardOs.java:200)
04-11 03:15:48.195  4843  5164 W Firestore:     at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:74)
04-11 03:15:48.195  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:135)
04-11 03:15:48.195  4843  5164 W Firestore:     ... 9 more
04-11 03:15:48.195  4843  5164 W Firestore: }.
04-11 03:15:49.626  4843 11075 W h.b.k1.c1: [{0}] Failed to resolve name. status={1}
04-11 03:16:00.435  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:16:00.435  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:119)
04-11 03:16:00.435  4843  5164 W Firestore:     at h.b.k1.b0$d.a(Unknown Source:138)
04-11 03:16:00.435  4843  5164 W Firestore:     at h.b.k1.b0$d.run(Unknown Source:42)
04-11 03:16:00.435  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
04-11 03:16:00.435  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
04-11 03:16:00.435  4843  5164 W Firestore:     at java.lang.Thread.run(Thread.java:919)
04-11 03:16:00.435  4843  5164 W Firestore: Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:16:00.435  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:156)
04-11 03:16:00.435  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
04-11 03:16:00.435  4843  5164 W Firestore:     at java.net.InetAddress.getAllByName(InetAddress.java:1152)
04-11 03:16:00.435  4843  5164 W Firestore:     at h.b.k1.b0$b.a(Unknown Source:0)
04-11 03:16:00.435  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:13)
04-11 03:16:00.435  4843  5164 W Firestore:     ... 5 more
04-11 03:16:00.435  4843  5164 W Firestore: Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
04-11 03:16:00.435  4843  5164 W Firestore:     at libcore.io.Linux.android_getaddrinfo(Native Method)
04-11 03:16:00.435  4843  5164 W Firestore:     at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:74)
04-11 03:16:00.435  4843  5164 W Firestore:     at libcore.io.BlockGuardOs.android_getaddrinfo(BlockGuardOs.java:200)
04-11 03:16:00.435  4843  5164 W Firestore:     at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:74)
04-11 03:16:00.435  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:135)
04-11 03:16:00.435  4843  5164 W Firestore:     ... 9 more
04-11 03:16:00.435  4843  5164 W Firestore: }.
04-11 03:16:08.354  2899  3014 D FreecessController: FZ : com.vetfinder.onepetstop(4843)
04-11 03:16:45.101  2899  5658 D FreecessController: UFZ : com.vetfinder.onepetstop(4843)
04-11 03:16:45.114  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:16:45.114  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:119)
04-11 03:16:45.114  4843  5164 W Firestore:     at h.b.k1.b0$d.a(Unknown Source:138)
04-11 03:16:45.114  4843  5164 W Firestore:     at h.b.k1.b0$d.run(Unknown Source:42)
04-11 03:16:45.114  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
04-11 03:16:45.114  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
04-11 03:16:45.114  4843  5164 W Firestore:     at java.lang.Thread.run(Thread.java:919)
04-11 03:16:45.114  4843  5164 W Firestore: Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:16:45.114  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:156)
04-11 03:16:45.114  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
04-11 03:16:45.114  4843  5164 W Firestore:     at java.net.InetAddress.getAllByName(InetAddress.java:1152)
04-11 03:16:45.114  4843  5164 W Firestore:     at h.b.k1.b0$b.a(Unknown Source:0)
04-11 03:16:45.114  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:13)
04-11 03:16:45.114  4843  5164 W Firestore:     ... 5 more
04-11 03:16:45.114  4843  5164 W Firestore: Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
04-11 03:16:45.114  4843  5164 W Firestore:     at libcore.io.Linux.android_getaddrinfo(Native Method)
04-11 03:16:45.114  4843  5164 W Firestore:     at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:74)
04-11 03:16:45.114  4843  5164 W Firestore:     at libcore.io.BlockGuardOs.android_getaddrinfo(BlockGuardOs.java:200)
04-11 03:16:45.114  4843  5164 W Firestore:     at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:74)
04-11 03:16:45.114  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:135)
04-11 03:16:45.114  4843  5164 W Firestore:     ... 9 more
04-11 03:16:45.114  4843  5164 W Firestore: }.
04-11 03:16:45.116  4843 11075 W h.b.k1.c1: [{0}] Failed to resolve name. status={1}
04-11 03:16:51.111  2899  3014 D FreecessController: FZ : com.vetfinder.onepetstop(4843)
04-11 03:19:02.400  2899  4877 D FreecessController: UFZ : com.vetfinder.onepetstop(4843)
04-11 03:19:02.419  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:19:02.419  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:119)
04-11 03:19:02.419  4843  5164 W Firestore:     at h.b.k1.b0$d.a(Unknown Source:138)
04-11 03:19:02.419  4843  5164 W Firestore:     at h.b.k1.b0$d.run(Unknown Source:42)
04-11 03:19:02.419  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
04-11 03:19:02.419  4843  5164 W Firestore:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
04-11 03:19:02.419  4843  5164 W Firestore:     at java.lang.Thread.run(Thread.java:919)
04-11 03:19:02.419  4843  5164 W Firestore: Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
04-11 03:19:02.419  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:156)
04-11 03:19:02.419  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
04-11 03:19:02.419  4843  5164 W Firestore:     at java.net.InetAddress.getAllByName(InetAddress.java:1152)
04-11 03:19:02.419  4843  5164 W Firestore:     at h.b.k1.b0$b.a(Unknown Source:0)
04-11 03:19:02.419  4843  5164 W Firestore:     at h.b.k1.b0.a(Unknown Source:13)
04-11 03:19:02.419  4843  5164 W Firestore:     ... 5 more
04-11 03:19:02.419  4843  5164 W Firestore: Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
04-11 03:19:02.419  4843  5164 W Firestore:     at libcore.io.Linux.android_getaddrinfo(Native Method)
04-11 03:19:02.419  4843  5164 W Firestore:     at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:74)
04-11 03:19:02.419  4843  5164 W Firestore:     at libcore.io.BlockGuardOs.android_getaddrinfo(BlockGuardOs.java:200)
04-11 03:19:02.419  4843  5164 W Firestore:     at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:74)
04-11 03:19:02.419  4843  5164 W Firestore:     at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:135)
04-11 03:19:02.419  4843  5164 W Firestore:     ... 9 more
04-11 03:19:02.419  4843  5164 W Firestore: }.
04-11 03:19:03.537  2899  3014 D FreecessController: FZ : com.vetfinder.onepetstop(4843)
04-11 03:19:26.219  2899  5039 D FreecessController: UFZ : com.vetfinder.onepetstop(4843)
04-11 03:19:26.223  4843 11103 V NativeCrypto: Read error: ssl=0x7616331b48: I/O error during system call, Software caused connection abort
04-11 03:19:26.228  4843  9700 V NativeCrypto: Write error: ssl=0x7616331b48: I/O error during system call, Broken pipe
04-11 03:19:26.230  4843  9700 V NativeCrypto: SSL shutdown failed: ssl=0x7616331b48: I/O error during system call, Success
04-11 03:19:33.676  2899  3014 D FreecessController: FZ : com.vetfinder.onepetstop(4843)
04-11 03:19:42.805  2899  5495 D FreecessController: UFZ : com.vetfinder.onepetstop(4843)
04-11 03:19:42.807  4843  5164 D ConnectivityManager: unregisterNetworkCallback; CallingUid : 10793, CallingPid : 4843
04-11 03:19:42.813  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=Channel shutdownNow invoked, cause=null}.
04-11 03:19:42.870  4843 19095 W DynamiteModule: Local module descriptor class for providerinstaller not found.
04-11 03:19:42.910  4843 19095 I DynamiteModule: Considering local module providerinstaller:0 and remote module providerinstaller:0
04-11 03:19:42.910  4843 19095 W ProviderInstaller: Failed to load providerinstaller module: No acceptable module found. Local version is 0 and remote version is 0.
04-11 03:19:43.020  4843 19095 D ConnectivityManager: requestNetwork; CallingUid : 10793, CallingPid : 4843
04-11 03:19:43.022  2899  5081 D ConnectivityService: requestNetwork for uid/pid:10793/4843 NetworkRequest [ TRACK_DEFAULT id=2566, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10793] ]
04-11 03:19:48.962  2899  3014 D FreecessController: FZ : com.vetfinder.onepetstop(4843)
04-11 03:21:56.956  2899  5039 D FreecessController: UFZ : com.vetfinder.onepetstop(4843)
04-11 03:21:56.957  4843  5164 D ConnectivityManager: unregisterNetworkCallback; CallingUid : 10793, CallingPid : 4843
04-11 03:21:56.994  4843  5164 W Firestore: (22.1.2) [WatchStream]: (5d02088) Stream closed with status: d1{code=UNAVAILABLE, description=Channel shutdown invoked, cause=null}.
04-11 03:21:57.035  4843 19095 W DynamiteModule: Local module descriptor class for providerinstaller not found.
04-11 03:21:57.074  4843 19095 I DynamiteModule: Considering local module providerinstaller:0 and remote module providerinstaller:0
04-11 03:21:57.075  4843 19095 W ProviderInstaller: Failed to load providerinstaller module: No acceptable module found. Local version is 0 and remote version is 0.
04-11 03:21:57.099  4843 19095 D ConnectivityManager: requestNetwork; CallingUid : 10793, CallingPid : 4843
04-11 03:21:57.140  2899  5039 D ConnectivityService: requestNetwork for uid/pid:10793/4843 NetworkRequest [ TRACK_DEFAULT id=2568, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10793] ]

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.0.5, on Mac OS X 10.15.7 19H2 darwin-x64, locale en-SG)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.6)
[✓] IntelliJ IDEA Community Edition (version 2021.1)
[✓] Connected device (2 available)

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.12.3
Flutter SDK 2.0.5
vetfinder 1.0.14+214

dependencies:
- add_2_calendar 2.0.1 [flutter]
- carousel_slider 3.0.0 [flutter]
- catcher 0.6.3 [flutter flutter_web_plugins fluttertoast device_info_plus package_info mailer dio flutter_mailer logging sentry universal_io]
- charts_flutter 0.9.0 [charts_common collection flutter intl logging meta]
- cloud_firestore 1.0.4 [cloud_firestore_platform_interface cloud_firestore_web firebase_core firebase_core_platform_interface flutter meta]
- cloud_functions 1.0.3 [cloud_functions_platform_interface cloud_functions_web firebase_core firebase_core_platform_interface flutter]
- confetti 0.5.2 [flutter random_color vector_math]
- cupertino_icons 0.1.3
- device_info 0.4.2+10 [flutter device_info_platform_interface]
- easy_localization 3.0.0 [flutter shared_preferences intl args path easy_logger flutter_localizations]
- file_picker 3.0.0 [flutter flutter_web_plugins flutter_plugin_android_lifecycle plugin_platform_interface]
- firebase_analytics 7.1.1 [firebase_analytics_platform_interface firebase_analytics_web firebase_core flutter meta]
- firebase_auth 1.0.3 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.0.3 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 2.0.0 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_dynamic_links 0.8.0 [flutter firebase_core]
- firebase_messaging 9.1.1 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- flare_flutter 2.0.6 [flutter flare_dart meta]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_facebook_login 3.0.0 [flutter collection]
- flutter_ffmpeg 0.4.0 [flutter]
- flutter_image_compress 0.7.0 [flutter]
- flutter_localizations 0.0.0 [flutter intl characters clock collection meta path typed_data vector_math]
- flutter_portal 0.3.0 [flutter]
- flutter_rating_bar 3.0.1+1 [flutter]
- flutter_slidable 0.5.7 [flutter]
- flutter_svg 0.21.0-nullsafety.0 [flutter meta path_drawing vector_math xml]
- font_awesome_flutter 8.11.0 [flutter]
- gbk2utf8 1.0.1 [flutter]
- geocoding 1.0.5 [flutter geocoding_platform_interface url_launcher]
- geolocator 6.2.1 [flutter geolocator_platform_interface geolocator_web]
- get_it 4.0.1 [async meta]
- google_maps_flutter 2.0.2 [flutter flutter_plugin_android_lifecycle google_maps_flutter_platform_interface]
- google_place 0.4.0 [flutter http]
- google_sign_in 4.5.1 [google_sign_in_platform_interface flutter meta google_sign_in_web]
- hive 1.6.0-nullsafety.2 [meta crypto]
- html 0.15.0 [csslib source_span]
- http 0.13.1 [http_parser meta path pedantic]
- image 3.0.1 [archive meta xml]
- image_cropper 1.3.1 [flutter]
- image_gallery_saver 1.6.8 [flutter]
- image_picker 0.7.4 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface image_picker_for_web]
- image_size_getter 0.2.1 [collection hashcodes]
- in_app_review 1.0.4 [flutter in_app_review_platform_interface]
- intl 0.17.0 [clock path]
- like_button 2.0.2 [flutter]
- mime 1.0.0
- modal_bottom_sheet 2.0.0 [flutter]
- month_picker_dialog 0.3.3 [flutter flutter_localizations intl flutter_cupertino_localizations rxdart]
- move_to_background 1.0.1 [flutter]
- package_info 2.0.0 [flutter]
- page_transition 1.1.7+6 [flutter]
- path_provider 2.0.1 [flutter path_provider_platform_interface path_provider_macos path_provider_linux path_provider_windows]
- permission_handler 5.1.0+2 [flutter meta permission_handler_platform_interface]
- photo_view 0.10.3 [flutter]
- pool 1.5.0 [async stack_trace]
- provider 5.0.0 [collection flutter nested]
- screenshot 0.3.0 [flutter]
- share 2.0.1 [meta mime flutter]
- shared_preferences 2.0.3 [meta flutter shared_preferences_platform_interface shared_preferences_linux shared_preferences_macos shared_preferences_web shared_preferences_windows]
- sign_in_with_apple 2.5.4 [meta flutter]
- simple_animations 3.0.3 [flutter supercharged pedantic]
- swipeable_page_route 0.2.1 [black_hole_flutter collection flutter list_diff meta supercharged]
- translator 0.1.6+1 [http]
- url_launcher 6.0.2 [flutter url_launcher_platform_interface url_launcher_linux url_launcher_macos url_launcher_windows url_launcher_web]
- video_player 2.0.0 [meta video_player_platform_interface video_player_web flutter flutter_test]
- video_thumbnail 0.2.5+1 [flutter]
- visibility_detector 0.1.5 [flutter]
- wakelock 0.1.4+2 [flutter]
- webview_flutter 2.0.1 [flutter]

dependency overrides:
- flutter_plugin_android_lifecycle 2.0.0 [flutter]
- intl 0.17.0 [clock path]
- plugin_platform_interface 2.0.0 [meta]
- url_launcher 6.0.2 [flutter url_launcher_platform_interface url_launcher_linux url_launcher_macos url_launcher_windows url_launcher_web]

transitive dependencies:
- archive 3.1.2 [crypto path]
- args 2.0.0
- async 2.5.0 [collection]
- black_hole_flutter 0.3.0 [collection flutter meta supercharged]
- boolean_selector 2.1.0 [source_span string_scanner]
- characters 1.1.0
- charcode 1.2.0
- charts_common 0.9.0 [collection intl logging meta vector_math]
- clock 1.1.0
- cloud_firestore_platform_interface 4.0.1 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 1.0.4 [cloud_firestore_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- cloud_functions_platform_interface 5.0.1 [firebase_core flutter meta plugin_platform_interface]
- cloud_functions_web 4.0.3 [cloud_functions_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- collection 1.15.0
- crypto 3.0.0 [collection typed_data]
- csslib 0.17.0 [source_span]
- device_info_platform_interface 1.0.1 [flutter meta plugin_platform_interface]
- device_info_plus 1.0.0 [flutter device_info_plus_platform_interface device_info_plus_linux device_info_plus_macos device_info_plus_web device_info_plus_windows]
- device_info_plus_linux 1.0.0 [device_info_plus_platform_interface file flutter meta]
- device_info_plus_macos 1.0.0 [device_info_plus_platform_interface flutter]
- device_info_plus_platform_interface 1.0.1 [flutter meta plugin_platform_interface]
- device_info_plus_web 1.0.0 [device_info_plus_platform_interface flutter_web_plugins flutter]
- device_info_plus_windows 1.0.0 [device_info_plus_platform_interface ffi flutter win32]
- dio 4.0.0 [http_parser path]
- easy_logger 0.0.2 [flutter]
- fake_async 1.2.0 [clock collection]
- ffi 1.0.0
- file 6.1.0 [meta path]
- firebase 9.0.1 [http http_parser js]
- firebase_analytics_platform_interface 1.1.0 [flutter meta]
- firebase_analytics_web 0.2.0+1 [firebase firebase_analytics_platform_interface flutter flutter_web_plugins meta]
- firebase_auth_platform_interface 4.0.2 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 1.0.5 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.0.0 [flutter meta plugin_platform_interface]
- firebase_core_web 1.0.2 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.0.0 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 2.1.1 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 1.0.4 [firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- flare_dart 2.3.4
- flutter_cupertino_localizations 1.0.1 [flutter flutter_localizations]
- flutter_mailer 2.0.0-null-safe [flutter]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- fluttertoast 8.0.3 [flutter flutter_web_plugins]
- geocoding_platform_interface 1.0.1+1 [flutter meta plugin_platform_interface]
- geolocator_platform_interface 1.0.9 [flutter meta plugin_platform_interface vector_math]
- geolocator_web 1.0.1 [flutter flutter_web_plugins geolocator_platform_interface]
- google_maps_flutter_platform_interface 2.0.4 [flutter meta plugin_platform_interface stream_transform collection]
- google_sign_in_platform_interface 1.1.2 [flutter meta quiver]
- google_sign_in_web 0.9.2 [google_sign_in_platform_interface flutter flutter_web_plugins meta js]
- hashcodes 1.0.0
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- image_picker_for_web 2.0.0 [image_picker_platform_interface meta flutter flutter_web_plugins]
- image_picker_platform_interface 2.0.1 [flutter meta http plugin_platform_interface]
- in_app_review_platform_interface 1.0.5 [flutter url_launcher plugin_platform_interface platform]
- js 0.6.3
- list_diff 2.0.0 [async]
- logging 1.0.1
- mailer 4.0.0 [async logging intl mime path pedantic]
- matcher 0.12.10 [stack_trace]
- meta 1.3.0
- nested 1.0.0 [flutter]
- path 1.8.0
- path_drawing 0.5.0-nullsafety.0 [vector_math meta path_parsing flutter]
- path_parsing 0.2.0-nullsafety.0 [vector_math meta]
- path_provider_linux 2.0.0 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_macos 2.0.0 [flutter]
- path_provider_platform_interface 2.0.0 [flutter meta platform plugin_platform_interface]
- path_provider_windows 2.0.0 [path_provider_platform_interface meta path flutter ffi win32]
- pedantic 1.11.0
- permission_handler_platform_interface 2.0.2 [flutter meta plugin_platform_interface]
- petitparser 4.0.2 [meta]
- platform 3.0.0
- process 4.1.0 [file path platform]
- quiver 2.1.5 [matcher meta]
- random_color 1.0.5 [flutter]
- rxdart 0.24.1
- sentry 4.1.0-nullsafety.1 [http meta stack_trace uuid]
- shared_preferences_linux 2.0.0 [flutter file meta path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 2.0.0 [shared_preferences_platform_interface flutter]
- shared_preferences_platform_interface 2.0.0 [flutter]
- shared_preferences_web 2.0.0 [shared_preferences_platform_interface flutter flutter_web_plugins meta]
- shared_preferences_windows 2.0.0 [shared_preferences_platform_interface flutter file meta path path_provider_platform_interface path_provider_windows]
- sky_engine 0.0.99
- source_span 1.8.0 [charcode collection path term_glyph]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.0
- string_scanner 1.1.0 [charcode source_span]
- supercharged 2.0.0 [supercharged_dart flutter]
- supercharged_dart 2.0.0
- term_glyph 1.2.0
- test_api 0.2.19 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.3.0 [collection]
- universal_io 2.0.4 [collection crypto meta typed_data]
- url_launcher_linux 2.0.0 [flutter]
- url_launcher_macos 2.0.0 [flutter]
- url_launcher_platform_interface 2.0.1 [flutter plugin_platform_interface]
- url_launcher_web 2.0.0 [url_launcher_platform_interface meta flutter flutter_web_plugins]
- url_launcher_windows 2.0.0 [flutter]
- uuid 3.0.3 [crypto]
- vector_math 2.1.0
- video_player_platform_interface 4.0.0 [flutter meta flutter_test]
- video_player_web 2.0.0 [flutter flutter_web_plugins meta video_player_platform_interface]
- win32 2.0.0 [ffi]
- xdg_directories 0.2.0 [meta path process]
- xml 5.0.2 [collection meta petitparser]

These exceptions are observable if you change networks because the device is temporarily offline but it should reconnect without any issues.
Are you able to reproduce this with a minimal project with just cloud_firestore?

Hi @markusaksli-nc , I haven't tried with a minimal project. But may I ask what does it mean when you say that the device is temporarily offline? Does it mean that the device hasn't authorized app to access internet or the device itself is not online? Because I can confirm that the device is online, because all other apps work fine. I have enough time to test other apps, while my app is still trying to establish a connection.

I just mean when the device is switching network providers it will temporarily not be able to connect because it is establishing a connection to the new network. This should clear up in only a couple of seconds though.
Could you try to see if you can create a minimal complete reproducible code sample that just isolates the issue to some part of cloud_firestore so we could test it as well?

Hello, similar to https://github.com/FirebaseExtended/flutterfire/issues/4305 ?

Thanks @QuentinSc. Infact, I read through the ticket and the behavior people have described, I am facing the exact same problem. The issue is not only limited StteamBuilder however, it also happens to all get() queries as well.
Thanks for linking the tickets.

Yep @frankyvij, I confirm what you are saying.
It's a blocker for my app since 2020. I make an app using FIrebase that I can't deploy in production because this issue...

If it's the exact same issue we can close this as a duplicate.


Git requirements txt

were you going to add unit tests to the test_config_jupyter.py file?

were you going to add unit tests to the test_config_jupyter.py file?

I don't believe we can without moving those functions into a package, which I'm not sure is worth it right now

That's fine. Can you remove that file then.


[libjpeg-turbo:x86-windows] build failure

Host Environment

OS: [Windows 10 Professional Workstation x64 2004(19041.153)]
Compiler: MSVC16 (Visual Studio Professional 2019),CMake 3.16.0

To Reproduce
Steps to reproduce the behavior:
./vcpkg install opencv
Failure logs
-- Downloading https://github.com/libjpeg-turbo/libjpeg-turbo/archive/2.0.3.tar.gz... Failed. Status: 56;"Failure when receiving data from the peer"                                                                       CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:175 (message):                                                                               Failed to download file.                                           onment                                                                         variables to "https://user:password@your-proxy-ip-address:port/".        Otherwise, please submit an issue at https://github.com/Microsoft/v                                                                         Call Stack (most recent call first):                                       scripts/cmake/vcpkg_from_github.cmake:132 (vcpkg_download_distfile)      ports/libjpeg-turbo/portfile.cmake:3 (vcpkg_from_github)                 scripts/ports.cmake:94 (include)                                                                                Error: Building package libjpeg-turbo:x86-windows failed with: BUILD_FAILED                                                                       Please ensure you're using the latest portfiles with .\vcpkg update, then                                                                       submit an issue at https://github.com/Microsoft/vcpkg/issues including:    Package: libjpeg-turbo:x86-windows                                       Vcpkg version: 2019.09.12-nohash                                                                                Additionally, attach any relevant sections from the log files above.

Hi @UnknownObject000
Thanks for posting this issue.
It seems that there is something wrong when  downloading  this archive https://github.com/libjpeg-turbo/libjpeg-turbo/archive/2.0.3.tar.gz.
Could you please help confirm if you have access to https://github.com/libjpeg-turbo/libjpeg-turbo/archive/2.0.3.tar.gz?
If yes, please download it manually and put it into VCPKG_PATH/downloads, then rebuild this port.
Kindly remind:
libjpeg-turbo has been updated to 2.0.4. If you need the new version, you can try to update vcpkg and use it.

Thank you for give me telling me that.I installed it successlly and I'll close this issue.


improvement add custom_env.sh from regression pipeline

Proposed changes
This file will be used when compiling Doris in regression pipeline.
And we can modify it to control the compile behavior.
I add BUILD_FS_BENCHMARK=ON, so that it will build fs_benchmark_tool.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Update FAQ.md

Detail from Discord FAQ added to Github FAQ

@CyberPunkMetalHead  Tested. Ran for 5m in TESTNET, ran for 5m in MAINNET. No issues.


Smaller text in controller (machine list) removed tooltip

Thanks!

i just noticed there is a issue when you have the controller gui open, not related to this text change, but it seems the list of machines get changed or updated causing crash.
Gives a index out of bounds or null pointer is random, is related to
IBlockState machineState = machine.getWorld().getBlockState(machine.getPos());
My guess is a scan just happend and the list was modified and the gui read that machine from the list at the exact point it was null.

i added a function in the gui, you may wanna move it to a more global place, it allows you to recalculate the position of things when you apply a scale so they get rendered in the correct position :)

sometimes the crash happends right away, other times you need to keep the gui open for a long time

I'll investigate that crash, I think I had it too.

is a small bug when turning the controller off with redstone, the grid is still on, and is listed in machines

and power usage when it says 24 rf/t seems to be 24 rf a seccond, having the system active it draws around 1 rf/t from the generator

maybe have a global var that stores energy usage then recheck the usage every sec as you do, but draw the energy every tick

my mistake, you do have a global already, but you only draw energy 1 time every 20 ticks :)


Depends on vulnerable version of cookie

Package version
latest
Describe the bug
https://github.com/advisories/GHSA-pxg6-pf52-xh8x
Reproduction repo
No response

Fixed in https://github.com/japa/api-client/commit/49605a44eb0e075893476ec8fdba1e36dc05c0b6


change PROVISIONALLY_ACCEPTED status to PROVISIONAL

To remove whitespace from the very important and often used taxonomic status enum I suggest to shorten the enum name and thus the exposed API value to just provisional. We can still render it as "provisionally accepted" in the UI.

@thomasstjerne does this cause havoc to the UI?

It will need adjustment at various places indeed. Applying decisions etc


sendUserNotification issue on Android ("No Activity found to handle Intent")

I'm attempting to use sentUserNotification on Android and I get the error below.
Test Failed: No Activity found to handle Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x24000000 pkg=com.******.******.****** (has extras) }

Is this something someone here has ran into before? I think my app is set up correctly (e.g. manifest has intent filter) but I'm wondering if there's something else I missed.
I'm on Detox v17.11.4.

What is the solution for this? I am running into this problem and have checked the configurations multiple times! Any help appreciated! Thank you!
@munyirik  Did you get past it?