Pull-down refresh and swipe left/right navigation

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.
I would like to implement these swipe navigation features

pull-down refresh on page level
swipe left=navigate back
swipe right=navigate forwared

Describe the solution you'd like
The most preferred solution would be to have components providing swipe interaction along with refresh and navigation options.
Additional context
No response

@techscx Thanks for contacting us. We're investigating this issue.
We'll let you know if it's possible to work on this issue.

The issue is accepted and planned. Resolving it will start ASAP.

Resolving this issue has started. It will be announced when this issue is resolved.


New_T2WML system caching issue

The system caches the json/ttl files and the cached ones are downloaded even after applying a new YAML.

what commit/branch is this happening in? I stopped having this issue with commit 6f29d08...

I faced the issue in bf399f1b14e01cda25e8095e7082c7a553a6fe02

I have not been able to successfully reproduce this issue.
Can you give a step-by-step description of the steps taken to reproduce this bug?

I tried to replicate the issue on version 2.0a3 and it seem to have fixed now.


fix: handler param.convert's error in caller.go

这个 PR 实现什么功能/修复什么问题:
如果前端传递的参数有问题（比如，某个字段是数组，却按照map传递），就会导致param.convert失败，这里的错误应该抛出。否则错误出现的地方就会滞后，不能正确锁定错误。

是否需要 backport 到之前的 release 分支:
NONE

/cc @zexi

Codecov Report

Merging #6756 into master will increase coverage by 0.00%.
The diff coverage is 56.25%.

@@           Coverage Diff           @@
##           master    #6756   +/-   ##
=======================================
  Coverage    7.13%    7.14%
=======================================
  Files         648      648
  Lines      109550   109557    +7
=======================================
+ Hits         7819     7829   +10
+ Misses     101133   101125    -8
- Partials      598      603    +5

Flag
Coverage Δ

#aFlag
7.14% <56.25%> (+<0.01%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/cloudcommon/db/caller.go
25.00% <56.25%> (-0.44%)
:arrow_down:

pkg/appsrv/response.go
66.17% <0.00%> (-2.95%)
:arrow_down:

pkg/cloudcommon/cronman/cronman.go
53.95% <0.00%> (+5.11%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm
/approve


Single line directive snippets

Most of https://github.com/dotnet/razor-tooling/issues/4547
Multi-line directives (e.g. @code) require additional tweaking to correctly determine ident size and type (spaces or tabs). Maybe I will implement them later, but not sure. Single-line directives are used a lot more frequently, so this PR will cover most use cases anyway

I just got an idea. What if for @page snippet we leave only the page path editable without leading /, because removing it leads to compilation error anyway. @page "/{page}", where what is in {...} is editable? @NTaylorMullen @danroth27 what do you think about it?

I just got an idea. What if for @page snippet we leave only the page path editable without leading /, because removing it leads to compilation error anyway. @page "/{page}", where what is in {...} is editable? @NTaylorMullen @danroth27 what do you think about it?

That sounds reasonable to me but @danroth27 would have a more valuable opinion here 😄

@NTaylorMullen It seems, that I've implemented all required (and an optional one) features. Looks like this now:

Merging PR - thanks @DoctorKrolic!

I just got an idea. What if for @page snippet we leave only the page path editable without leading /, because removing it leads to compilation error anyway. @page "/{page}", where what is in {...} is editable? @NTaylorMullen @danroth27 what do you think about it?

That sounds reasonable to me but @danroth27 would have a more valuable opinion here 😄

@NTaylorMullen please get an answer from @danroth27 and do a micro-follow up if he agrees, thanks!

I just got an idea. What if for @page snippet we leave only the page path editable without leading /, because removing it leads to compilation error anyway. @page "/{page}", where what is in {...} is editable? @NTaylorMullen @danroth27 what do you think about it?

That sounds reasonable to me but @danroth27 would have a more valuable opinion here 😄

@NTaylorMullen please get an answer from @danroth27 and do a micro-follow up if he agrees, thanks!

@DoctorKrolic lets make a judgement call here. I think your idea holds water on its own lets do it! Do you want to contribute or would you like us to take it? I don't mind either way 😄

I'm having some troubles running unit tests in latest public VS preview, so I would like you to take this one


Sponsor fix

Fixes #
##removed that timer page
added those sponsor logos

@vardhan124 Set you git config correctly


Used GPT-2 to generate synthetic data for BERT

Naming: feature/descriptive-name
Reviewers: minimum 2 (Ryan and/or 2 from Web or DS respectively and not the person who submitted PR)
Description:
What is the motivation for these changes?
Our NLP classification model lacks enough samples of Ranks 2, 3, & 4 police misconduct. Manual labeling of these data is far too slow, prompting the desire to use synthetic data in its place.
What specific changes were made?
A simplified GPT-2 text generation notebook, an EDA notebook for the cleaning and conversion of these generated tweets, and hand cleaned generated tweets in .txt format as reference/resource.
Submitter Checklist:

[ ] Small scope (1-2 components)
[ ] Not too many concerns in a single commit
[x] Remove extraneous comments (code in comments), print statements, to-dos, console.logs, extra fluff
[x] Atomic, descriptive commit messages
[x] Consistent formatting

Reviewer Checklist:

[x] Small scope (1-2 components)
[x] Comments, print statements, to-dos, console.logs, extra fluff were removed
[x] Give feedback no matter what conversations happened elsewhere, document here
[ ] Comment on the line of code itself (blue plus box) in files changed tab

Everything went well with cleaning the data in my EDA notebook. It's just that somehow when using the pandas .to_csv() method to convert my cleaned dataframe into CSVs a lot of the data just runs into each other. Text will appear in the labels column, '&' will cut off the length of a tweet, etc.
So my next approach will be to refactor my data cleaning code into a wrangle function and insert that into the FrankenBERT notebook. No CSVs will be needed, only the cleaned dataframes already ready-at-hand.


Create 0xf8b161f190a08fb9be3b8c34cb80fc9d02a18ac5

Please fix the error, otherwise, I will close this pr in 2 days.

CI failed. There are two json files.
Please follow the README and check your commit again.


Updating README formatting and resource links

I noticed that Mouse Events wasn't formatted correctly under Region Events. I also added a link to the browser support for Web Audio to http://caniuse.com/audio-api

👍


Mermaid.js templates/macros render the SVG content as HTML escaped

The template/macros for including mermaidJS graphs into LiaScript render the SVG content as HTML escaped. The examples don't render properly. Any suggestions how to fix?
https://liascript.github.io/course/?https://raw.githubusercontent.com/liaScript/mermaid_template/master/README.md

Thanks @andre-dietrich ! It works like a charm.


Update write to return resolved promise instead of never being resolved.

Only problem is it uses Async/Await instead of the confusing promise chain.

Not ready for async/await. And i dont see what case you are trying to fix. Is it the try/catch  failure?
Plus your code format is all messed up.
Will commit a fix so i am going to close that PR

I didn’t have time to debug the promises. I just know the original code hangs.


[yandexmusic:playlist][yandexmusic:privatetrack] add download private track

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED) (I checked it myself)
[x] Checked the code with flake8

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[x] New feature

Description of your pull request and other information
I added downloading of private tracks for yandex music, and added it to the playlist, reduced the value of _TRACKS_PER_CHUNK to 200, because when I was logged in, it started giving an error.

Do not copy paste code.
Provide concrete examples of what this is supposed to fix and add tests.
Read coding conventions.

Do not copy paste code.
Provide concrete examples of what this is supposed to fix and add tests.
Read coding conventions.

how do i add tests if these are PRIVATE TRACKS?

Either create a test account or add only matching tests.


 Error: SELF_SIGNED_CERT_IN_CHAIN
npm ERR!     at TLSSocket.<anonymous> (_tls_wrap.js:777:36)
npm ERR!     at TLSSocket.EventEmitter.emit (events.js:98:17)
npm ERR!     at TLSSocket._finishInit (_tls_wrap.js:337:8)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/isaacs/npm/issues>

npm ERR! System Darwin 13.0.2
npm ERR! command "/Applications/Atom.app/Contents/Frameworks/Atom Helper.app/Contents/MacOS/Atom Helper" "/Applications/Atom.app/Contents/Resources/app/node_modules/atom-package-manager/node_modules/npm/bin/npm-cli.js" "--userconfig" "/Applications/Atom.app/Contents/Resources/app/node_modules/atom-package-manager/.apmrc" "install" "/Users/hannes.johansson/.atom/.node-gyp/.atom/.apm/emmet/0.4.1/package.tgz" "--target=0.11.10" "--arch=x64"
npm ERR! cwd /private/var/folders/3l/8s9sfz7x1mlbwtvcdrz1sqt4fd3575/T/apm-install-dir-114128-5355-1n8eo3s
npm ERR! node -v v0.11.10
npm ERR! npm -v 1.3.18
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /private/var/folders/3l/8s9sfz7x1mlbwtvcdrz1sqt4fd3575/T/apm-install-dir-114128-5355-1n8eo3s/npm-debug.log
npm ERR! not ok code 0

i'm not able to install Emmet packaege on Atom, however i'm getting this error msg!
could someone help me please to install it??
nstalling<EMAIL_ADDRESS>failed.Hide output…
npm ERR! Unexpected end of JSON input while parsing near '...cjiy27dkG\nOfRoApz7iu'
npm ERR!      C:\Users\sise.atom.apm_logs\2021-06-23T18_52_09_823Z-debug.log

It's not Emmet issue, it's either Atom or your network issue

It's not Emmet issue, it's either Atom or your network provider issue

i see, could you help me to fix it please


Adding a check of the target directory (specified with -D) of the new database (-n).

I found that when using -n and -D together if you specify a non-existent directory the util will segfault. This PR adds a check of the target directory right after the options are parsed and aborts with a message if it doesn't exist. We could add another option later to create the directory if anyone things that would be a nice feature.
The current output for reference is:
# modsec-sdbm-util /path/to/default_SESSION -n -D /tmp/testing
Opening file: /path/to/default_SESSION
Database ready to be used.
New database generated with valid keys at: /tmp/testing/new_db
Segmentation fault (core dumped)

hub-- for that insanely long initial title...

Hi @csutherl.
Thanks for the patch! It is now merged.


mixin for box-shadow is missing

As the title says. Needs vendor prefixes -webkit- and -moz- for older browsers.

Nothing wrong with using Bourbon and Compass together. :)

Yes there is, because there is not way to confidently tell which mixin it uses when one exist bothing Compass and in Bourbon.
So what other mixin are going to be removed? And how much of my code is going to stop working when that happens?.. Like I said, there is no overhead in keeping old mixins around. If you absolutely must, just let it output the unprefixed properties only. So it won't break existing code.

agreed @thany
yes, this issue is coming back 6 years later!
:(


net/http: Add Error Callbacks

I've written a little REST server on net/http that's supposed to only ever return JSON contents. At least, that's what the parts I wrote do. However, there are certain errors that net/http encounters before my code is ever called. In those situations, I have no access to any code to determine what the content type and message should be for a given error. For example, take this stupid simple implementation:
package main

import (
	"encoding/json"
	"net/http"
)

type Server struct{}

func (server *Server) ServeHTTP(w http.ResponseWriter, r *http.Request) {
	w.Header().Set("Content-Type", "application/json; charset=UTF-8")
	w.WriteHeader(http.StatusOK)
	if err := json.NewEncoder(w).Encode(http.StatusText(http.StatusOK)); err != nil {
		panic(err)
	}
}

func main() {
	http.ListenAndServe(":8080", &Server{})
}

If I submit a request with borked headers (this one has a wayward newline in the Authorization header), my ServeHTTP() method is never called, presumably because there's an error when parsing the request to create the Request object:
> curl -i -H 'Authorization: Basic hi
there' 'http://localhost:8080/'
HTTP/1.1 400 Bad Request
Content-Type: text/plain; charset=utf-8
Connection: close

400 Bad Request

This makes complete sense to me, but if I'm creating an API with a contract to only ever return JSON, I'd like to have some way to plug into this error response and set the content-type and the body. I think the same challenge exists for Not Found errors. Perhaps there could be special handlers to configure these situations, similar to how Gorilla mux provides an assignable NotFoundHandler field in its Router object?
I'm not sure exactly what a generalized interface would look like for such error handlers (methods on Handler protocol?), but some way to hook in and get some control over net/http-initiated error responses would be very useful for guaranteeing the content-type contract of a web API.

@theory consider this: practically there's big enough chance that API would be running behind some kind of load balancer that may send error replies on its own in some scenarios (including malformed client requests). This would violate your assumption about getting replies that only have json payload in their bodies.

That's often true, @artyom, but not an assumption I'd always want to make. In order to ensure the integrity of the interface I provide, I'd like to have some ability to determine output formats for errors from http itself, regardless of what the operational deployment ultimately looks like. Helps me avoid QA questions, too.

This one is a potential duplicate of #10123.

Thanks @artyom, I think you're right.

#10123 is closed, so should we close this one as well?  Or with more experience does this seem like a real problem that net/http ought to address?

I don't think it's a dup of #10123. Bypassing the handler altogether is a different thing.

I believe this is a dup of #18997 (via #18095). Please reopen if you disagree.
#18997 is a log thread. The tl;dr is here:
https://github.com/golang/go/issues/18997#issuecomment-296722404

Sorry, reopening, it's not a dup. You don't just want to log, you want to return a custom response.

Not beautiful, but the simplest solution is to add a method one can override something like:
type ErrorHandler interface {
    HandleError func(w http.ResponseWriter, error string, code int)
}

Then check to see if the Handler implements it.

I have a similar use-case where the stdlib server will usually tell the client that it made a mistake without the handler ever getting a chance to interact with the request. In our case there are two aspects to this:

We have a contract where we expose certain errors via a special header which is (obviously) not done by the stdlib.
We log every request to be able to support our users with troubleshooting when their clients misbehave, for some error categories there is no log on the server at all, for example this switch statement is something I've came across a few times when investigating problems.

This is probably somewhat closer to #10123 but different: I'm looking to respond to errors which are never exposed to a handler compared to being able to replace existing default handlers (e.g. 404). I'm happy to open a different issue if you think this does not fit this issue.
The suggestion from @theory is already pretty close, but I'd prefer an approach closer to the existing ServeHTTP function:
type ErrorHandler interface {
	ServeError(w http.ResponseWriter, r *http.Request)
}

The ServeError function should be prepared to handle broken response writers as well as incomplete requests. At least the RemoteAddr should still be guaranteed to exist. It will give us the chance to log as much of the information as is available. The stdlib would not handle such cases on its own if such a handler is provided.
The handler would also be called for some of the cases where currently Server.ErrorLog is called: TLS handshake errors, panics and probably some additional places which I missed. Those are currently emitted as a log but it only contains very little data and the format does not align with the rest of our logs, being able to adjust that would be a huge plus.

@maxmoehl Looks nice. Is there a way to know what the response code was intended to be?

Right, it would probably be a good idea to expose that as well, so maybe the interface should be extended to include the encountered error, I've adjusted my original comment. That error could also carry the status code which is "proposed" by the stdlib.


fundamentals/startup.rst "Application Startup"

The "Services Available in Startup" section in the Application Startup doc lists IApplicationEnvironment as an injectable service, but the "Runtime Services Changes" section in the Migrating from ASP.NET 5 RC1 to ASP.NET Core doc says

You must modify code in the Startup class that uses IApplicationEnvironment to use IHostingEnvironment

Therefore my understanding is that all references to IApplicationEnvironment should be removed.

We need to do a general update on this doc.

The descriptions of Startup as the application entry point are outdated. Compare to https://docs.asp.net/en/dev/conceptual-overview/aspnet.html#application-anatomy
De-emphasize the discovery and Startup[Environment] pattern, Startup is usually specified via WebHostBuilder.UseStartup<Startup>();
Hosting:Application is now the startupAssembly configuration key or ASPNETCORE_STARTUPASSEMBLY environment variable
Re-order the sections. Services Available in Startup should come right after the description of DI and the class constructor, then ConfigureServices, then Configure.
ConfigureServices no longer supports parameter injection, only the ctor and Configure. ConfigureServices only accepts IServiceCollection.

There is a new IStartup interface. It's use is optional as using it would prohibit DI parameter injection into Configure. https://github.com/aspnet/Hosting/blob/dev/src/Microsoft.AspNetCore.Hosting.Abstractions/IStartup.cs

"like AppSettings in the example above". There are no AppSettings in the sample's ConfigureServices method.

[ ] Fix issues above

[ ] UE edit

[ ] add out of date banner

Anything you can do here is massively appreciated.  I'm just trying to create a from-scratch ASP.NET Core / Web API project, doing things as correctly as possible.  Finding out how to correctly initialise things is proving a real challenge.  IStartup looks much more grown-up than a magic class with public properties, thank you.
Where's the best place to ask about how to actually do configuration?  The Configuration section of the docs tells us how to build a configuration object, but then assigns it to a magical Configuration property (Configuration = builder.Build();).  Something explicit saying how to hook up ASP.NET to a particular configuration would be good (via builder.UseConfiguration() I'd guess - but is that really correct?), along with a list of any config settings that are known to be requested of the config (if any)?

Something explicit saying how to hook up ASP.NET to a particular configuration would be good (via builder.UseConfiguration() I'd guess - but is that really correct?), along with a list of any config settings that are known to be requested of the config (if any)?

The configuration API is just like any other API you can use in your application. UseConfiguration on the WebHostBuilder is about configuring specific ASP.NET options (like the environment, or the urls) from some configuration object that you're providing. It does not hook up your user configuration to anything.
What are you trying to configure?

I'm trying to understand how to configure ASP.NET Core, from first principles.  I didn't know that UseConfiguration was for environment or URLs (there's UseEnvironment I think?) - so that kind of info is what I'm looking for.
So basically nothing in the docs (that I stumbled across in a few hours so far):

Tells me what the default configuration sources are (if any)
Indicates how you associate a Configuration with ASP.NET (I can see UseConfiguration - but it's not explicitly referred to or used in any examples I can see)
Indicates exactly what the Configuration object passed in is used by ASP.NET for (which keys are expected, etc)

Note, I was primarily looking in the Startup and Configuration sections of the docs, which just seems to me to be the logical place for this info.
Yes, upon reading other parts of the docs, cross-referencing, digging through some examples and source, and the odd GitHub notification and issue, I can work this out, but still not with the level of certainty I'd like, or in the time I'd like.
I understand it's all a work-in-progress, not a complaint - just trying to give my opinion and stress the value that clearly outlining this stuff would have for me - and I would guess, others too.

@tdykstra  please review

@Rick-Anderson isn't this doc being replaced with the doc #3809 ?


apps: add HAProxy support

If everything goes well, it should be available as part of the future v3.1.0 version.
Thanks to @Aperence and @CrapsDorian for the work, and @wtarreau for the helpful reviews!

Perhaps also add https://github.com/apache/httpd/commit/4915c21524e7ed2cf0dcfcf93d8be9139337497d in this same PR ?


feat: add progress alert

Checklist:
here is the progress bar in action:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

@moT01, that sounds like a good suggestion. Should we get this in and iterate on it?


Added sol of BININVER problem

Codechef START14C

@adarshpriyadarshii
Your PR has been successfully merged Thank you so much for your valuable contribution. Do give a follow if it helped you and star the repo and check other repo too for more contribution. Keep hacking


PermissionError during temp file cleanup after cutout download (Windows)

Encountering the following error when creating a cutout (ERA5):
INFO:cdsapi:Download rate 3.8M/s

[                                        ] | 0% Completed |  0.0s
[########################################] | 100% Completed |  0.3s

---------------------------------------------------------------------------
PermissionError                           Traceback (most recent call last)
<ipython-input-5-3416e809141b> in <module>
      8
      9 # This is where all the work happens (this can take some time, for us it took ~15 minutes).
---> 10 cutout.prepare()

c:\users\j. hampp\documents\github\atlite\atlite\data.py in cutout_prepare(cutout, features, freq, tmpdir, overwrite)
    226     finally:
    227         if not keep_tmpdir:
--> 228             rmtree(tmpdir)
    229
    230     # Re-open

C:\anaconda\envs\atlite\lib\shutil.py in rmtree(path, ignore_errors, onerror)
    511             # can't continue even if onerror hook returns
    512             return
--> 513         return _rmtree_unsafe(path, onerror)
    514
    515 # Allow introspection of whether or not the hardening against symlink

C:\anaconda\envs\atlite\lib\shutil.py in _rmtree_unsafe(path, onerror)
    395                 os.unlink(fullname)
    396             except OSError:
--> 397                 onerror(os.unlink, fullname, sys.exc_info())
    398     try:
    399         os.rmdir(path)

C:\anaconda\envs\atlite\lib\shutil.py in _rmtree_unsafe(path, onerror)
    393         else:
    394             try:
--> 395                 os.unlink(fullname)
    396             except OSError:
    397                 onerror(os.unlink, fullname, sys.exc_info())

PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\\Users\\J705E~1.HAM\\AppData\\Local\\Temp\\tmplaut1buy\\tmp6jjdud34.nc'

Error seems new, haven't encountered it before.
The download finishes, but no cutout.data data variables are available.
Probably Windows related (Filehandlers ...)
Possibly related to the changes made in https://github.com/PyPSA/atlite/commit/9273a15169448e71f9af3a23136f322798a6c982

A direct consequence for making the cutout preparation work for sarah was to let go of the cleanup tmp files automatically once the file handle is released (the weakref.finalizer(noisy_unlink, ...) bit), since dask is often configured to use multiple processes and then whether a file handle is released in one process is not a good indicator for whether we still need the tmp file. Thus, I was forced to switch to a create all files in a temporary directory and clean up the directory when the cutout is ready scheme.
What probably happens for you now, is that some exception happens during the preparation of the cutout. During the error handling I try to clean up the temporary files, but the file handles have not been released and windows prohibits the deletion of the files. The easiest way to debug this problem now, is to supply a tmpdir="<some_empty_dir_that_you_created>" argument to cutout.prepare, so that keep_tmpdir is set and the OSError does not overshadow the real exception underneath and we can find out who holds onto its filehandles in this situation.
Ideally all filehandles should be released before exiting a scope with error exceptions (ie using with or a finally clause)), as another way to mitigate it would probably be good to wrap the rmtree in an try-except clause and turn the OSError into a log message so it does not hide the true exception.

By specifying a tmpdir the operation runs without error:
$ cutout.prepare(tmpdir="./localtmp/")
INFO:atlite.cutout:Cutout uk-2011-01-2 not found in directory ./, building new one
INFO:cdsapi:Sending request to https://cds.climate.copernicus.eu/api/v2/resources/reanalysis-era5-single-levels
INFO:cdsapi:Sending request to https://cds.climate.copernicus.eu/api/v2/resources/reanalysis-era5-single-levels
INFO:cdsapi:Sending request to https://cds.climate.copernicus.eu/api/v2/resources/reanalysis-era5-single-levels
INFO:cdsapi:Sending request to https://cds.climate.copernicus.eu/api/v2/resources/reanalysis-era5-single-levels
INFO:cdsapi:Sending request to https://cds.climate.copernicus.eu/api/v2/resources/reanalysis-era5-single-levels
INFO:cdsapi:Request is completed
INFO:atlite.datasets.common:Downloading request for 1 variables to C:\Users\J. Hampp\Documents\GitHub\atlite\examples\localtmp\tmpybiq8b4h.nc
INFO:cdsapi:Downloading http://<IP_ADDRESS>/cache-compute-0003/cache/data5/adaptor.mars.internal-1568637651.461136-31786-5-0d10c442-82a6-4f46-8be4-a73443c1b3ec.nc to C:\Users\J. Hampp\Documents\GitHub\atlite\examples\localtmp\tmpybiq8b4h.nc (3.9M)
INFO:cdsapi:Request is completed
INFO:cdsapi:Request is completed
INFO:cdsapi:Request is completed
INFO:cdsapi:Request is completed
INFO:atlite.datasets.common:Downloading request for 3 variables to C:\Users\J. Hampp\Documents\GitHub\atlite\examples\localtmp\tmplpevg6_5.nc
INFO:atlite.datasets.common:Downloading request for 9 variables to C:\Users\J. Hampp\Documents\GitHub\atlite\examples\localtmp\tmpvoopfrne.nc
INFO:cdsapi:Downloading http://<IP_ADDRESS>/cache-compute-0012/cache/data3/adaptor.mars.internal-1568637651.4501736-25378-15-3562dc67-d581-4f22-a699-4d06068c8af5.nc to C:\Users\J. Hampp\Documents\GitHub\atlite\examples\localtmp\tmplpevg6_5.nc (11.6M)
INFO:cdsapi:Downloading http://<IP_ADDRESS>/cache-compute-0005/cache/data7/adaptor.mars.internal-1568702524.1244705-7942-5-a3a39405-ad59-4a37-aba5-4ea662c1747b.nc to C:\Users\J. Hampp\Documents\GitHub\atlite\examples\localtmp\tmpvoopfrne.nc (6.8K)
INFO:atlite.datasets.common:Downloading request for 2 variables to C:\Users\J. Hampp\Documents\GitHub\atlite\examples\localtmp\tmpcutwpaeh.nc
INFO:atlite.datasets.common:Downloading request for 4 variables to C:\Users\J. Hampp\Documents\GitHub\atlite\examples\localtmp\tmpaao4up9g.nc
INFO:cdsapi:Downloading http://<IP_ADDRESS>/cache-compute-0003/cache/data2/adaptor.mars.internal-1568637672.4669356-30780-7-f10d482b-f931-4644-9c61-209b361f0a76.nc to C:\Users\J. Hampp\Documents\GitHub\atlite\examples\localtmp\tmpcutwpaeh.nc (7.7M)
INFO:cdsapi:Downloading http://<IP_ADDRESS>/cache-compute-0011/cache/data8/adaptor.mars.internal-1568637651.4599202-22719-5-02ff42ba-49a2-420a-a401-8d45c3a3c8c4.nc to C:\Users\J. Hampp\Documents\GitHub\atlite\examples\localtmp\tmpaao4up9g.nc (15.5M)
INFO:cdsapi:Download rate 88.7K/s
INFO:cdsapi:Download rate 2.8M/s
INFO:cdsapi:Download rate 4.8M/s
INFO:cdsapi:Download rate 4.2M/s
INFO:cdsapi:Download rate 3.9M/s

[                                        ] | 0% Completed |  0.0s

C:\anaconda\envs\atlite\lib\site-packages\dask\core.py:119: RuntimeWarning: divide by zero encountered in true_divide
  return func(*args2)
C:\anaconda\envs\atlite\lib\site-packages\dask\core.py:119: RuntimeWarning: invalid value encountered in true_divide
  return func(*args2)

[########################################] | 100% Completed |  0.4s

The cutout is properly prepared.
It seems to me some file handles are not released properly before the finally clause.
For now this is an acceptable workaround, but maybe we can pinpoint and resolve the cause.

Should be fixed in v0.2.

I can confirm that this works for now in my limited test case.

Cheering a bit to early.
This introduced a minor bug:
If the cutout is already fully created, then
https://github.com/PyPSA/atlite/blob/09714d595fc09f2aa1ba79bdd9e60391c582e880/atlite/data.py#L199-L202
returns, but first the finally of the block
https://github.com/PyPSA/atlite/blob/09714d595fc09f2aa1ba79bdd9e60391c582e880/atlite/data.py#L227-L236
get's executed.
Problem:
In this case ds  is never defined, raising
    230         # - fire up the garbage collector,
    231         # => xarray's file manager closes them and we can remove tmpdir
--> 232         del ds
    233         gc.collect()
    234

UnboundLocalError: local variable 'ds' referenced before assignment

Maybe wrap the del ds inside its own
try:
    del ds
except NameError:
    # that's ok.


Auto-start after restart

Thanks for the great app!
After the last update, the app won't auto start after a device restart.
Device: HTC U Ultra
OS Version: 8.0.0

Yep, just noticed this myself.
Thanks for the report, I'll figure out the regression and push a fix out.
On Tue, Apr 16, 2019, 09:39 Tariqzm<EMAIL_ADDRESS>wrote:

Thanks for the great app!
After the last update, the app won't auto start after a device restart.
Device: HTC U Ultra
OS Version: 8.0.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pyamsoft/home-button/issues/7, or mute the thread
https://github.com/notifications/unsubscribe-auth/AG7kgguXmTfifRMIF1uSrATgsjVFXLyXks5vhfyrgaJpZM4cy_FS
.

I believe I've managed to fix the problem with in version 3.8.8
I have released it to the store so hopefully you will see the update in a few days if not hours.

@pyamsoft thank you!
Usually hours.
I'll report back to you once I receive the update.

@pyamsoft Thanks, the issue has been resolved and Updated is now Updates as well! :grinning:

Great to hear!
You caught me on the typo :P what can I say - I figure only the curious people would even look to begin with.
Thank you for your contribution to the project.
I will close this issue, please re-open it if you think something is not fully resolved.


Comment about EventHandlerInvoker

Why is reflection used here at all? The handler method should be a public method, so it can get called directly without the use of reflection.

I'm not entirely convinced handlers should always be public - at least not for event handlers, possibly for command handlers.

Ok agree
Am 20.02.2017 16:21 schrieb "Michiel Rook"<EMAIL_ADDRESS>
I'm not entirely convinced handlers should always be public - at least not
for event handlers, possibly for command handlers.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrook/annotations/issues/5#issuecomment-281014888,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYEvO-1dX-uOb0rhRW1WmWmuJZ476Eqks5reU0KgaJpZM4MFamV
.


⚠ T:Riza Community Forum has degraded performance

In 039acbe, T:Riza Community Forum (https://community.triza.dev) experienced degraded performance:

HTTP code: 200
Response time: 1840 ms

Resolved: T:Riza Community Forum performance has improved in 154f49b.


Railings

About the PR
Adds railing for stages and queues. they can be vaulted and you can toss things over them to throw tomatoes at the clown
Screenshots

Changelog

:cl: StanberyTrask

add: added railing sprites, prototype, and construction graph

constriction graph

No more constriction graph


Update clipboard.md for mainthread warning

The link is broken, but the reason is missing the .md in the filename. the ~ tilde is a valid URL in DocFX, which refers to the site root (in the published docs).


update lars pfp

Pull Request Template
Description

Please include a summary of the change and which issue is fixed
Please also include relevant motivation and context
List any dependencies that are required for this change

Fixes # (issue)
Type of change
Please tick the relevant option by putting an X inside the bracket

[x ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How was this tested?

Please describe the tests that you ran to verify your changes

Provide instructions so we can reproduce

Please also list any relevant details for your test configuration

[ ] Test A

[ ] Test B

Test Configuration:

dahliaOS Build number:
Hardware:
VM:

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x ] I have checked my code and corrected any misspellings

We need gh api initgration

yeah


Evaluate rules on "startup"

Rules should be evaluated when they're loaded/parsed to improve performance at query time.

@renekrie Do you have a hint where to start? Then I'd give it a try.

The idea would be to partially evaluate queries that constitute the right-hand side of Common Rules, for example, 'personal computers' in
pc =>
    SYNONYM: personal computers

The following information could be loaded and cached on startup:

the Lucene query that is created for a given term of the rhs query (per field). This will probably be a simple TermQuery in most cases but it could also be a BooleanQuery in case the analysis chain emits more than one token for the input term.
whether the Lucene query has any results (maybe this is an optional information but at least for TermQueries this is easy to retrieve via DF).

Loading this info on startup would save query time especially if there are many query fields and if a Common Rule adds many query terms. Adding 10 synonyms with 10 query fields would result in 100 additional TermQueries. We would always have to go through the Lucene analysis in order to create these queries - regardless of Solr caching - and some of these TermQueries would never match any document.  Doing the analysis on startup and caching the TermQueries (or BooleanQueries) together with the DF information should therefore reduce query execution time later.
Where to start:
I've created a branch 'crpreload' for the development of this feature. In this branch, querqy-core/querqy.trie.TrieMap has already been made an Iterable over its values. TrieMap contains the mapping between an input and the resulting instructions and it is filled on startup.You can thus iterate over its values (getting you Instructions objects, which are just lists of Instruction objects) and inspect the instructions to get the rhs queries that you need for the preload (visitor pattern to deal with the different instruction types?).
Note that instructions and the Querqy query object model are search-engine independent. Maybe you'd want to pass an abstract Preloader to querqy.rewrite.commonrules.SimpleCommonRulesRewriterFactory and provide the implementation on the querqy-lucene module.
To create the cached Lucene query have a look at querqy-lucene/querqy.lucene.rewrite.LuceneQueryBuilder and at querqy-solr/querqy.solr.QuerqyDismaxQParser for passing in analyzers and params.
We'll have to clone the cached query when executing it later as boost factors might change per request. This will still be cheaper than running the full analysis chain.

This has been available for some time and is now described here: https://github.com/renekrie/querqy#advanced-configuration-caching .


Add support for large quiet zones

I ran into some problems using bardecoder on images where a QR code was surrounded by large quiet zones.  This fixes that and adds a test (which previously failed) to ensure it works correctly.

Yeah this is fine, thanks.


SQL Lab show more tabs dropdown overflows

Screenshot

Description
looks like a z-index issue with the dropdown menu

@etr2460 This dropdown menu should be scrollable. Adding a permanent scrollbar is problematic, as Antd Tabs doesn't expose API for customising the dropdown. I could override a proper CSS class in antd/index.less stylesheet... but I think that would make @rusackas quite unhappy. What I can do here is try to fix the styles of dropdown menu items - apparently the styling from the Tabs (like display: flex) don't apply to them.

Here's the fix for unstyled dropdown items: https://github.com/apache/incubator-superset/pull/11287. As I said, I can also add a permanent scrollbar in antd/index.less, but first I'd like to hear @rusackas's opinion.

@kgabryje thanks for fixing!! closing the issue


[safe_memcpy_test] Explicit type for arguments of the vector constructor

Signed-off-by: rialg<EMAIL_ADDRESS>Commit Message: Explicit type for arguments of the vector constructor
Additional Description: Issue #16542
Risk Level: N/A

Please, @jmarantz and @antoniovicente ,  could you add yourselves as reviewers?

/retest

Change looks good, but it would be good to hear from @Wyverald on wherever or not this fixes the issue he saw in the bazel build and how to repo that breakage.

Thanks for the PR. Unfortunately there isn't an easy way to do a test CI run on a PR (unless we turn the pipeline on for all future Envoy PRs -- which we could certainly do). Is there a way to push this PR to a branch in the main Envoy repo (envoyproxy/envoy)? That would give us a way to test beforehand if this fixes it.

The presubmit pipeline failed due to low code coverage in the tests.
Code coverage for source/common/quic is lower than limit of 88.4 (88.3)

Should we lower this target to match the current value?

I think once https://github.com/envoyproxy/envoy/pull/16570 merges you should be good? @alyssawilk has another PR also which might just improve the coverage.

go ahead an 'merge main' and this coverage issue should be resolved.

Thanks for the PR. Unfortunately there isn't an easy way to do a test CI run on a PR (unless we turn the pipeline on for all future Envoy PRs -- which we could certainly do). Is there a way to push this PR to a branch in the main Envoy repo (envoyproxy/envoy)? That would give us a way to test beforehand if this fixes it.

ok, we'll give it another shot if this change isn't sufficient.


Upgrade to Quarkus 1.13.0.CR1

@jamesnetherton is it normal to have all the 5 commits ?

@jamesnetherton is it normal to have all the 5 commits ?

Sometimes it's easier to maintain the branches with separate commits. Less squashing / rebasing / force pushing etc. Not a big issue because we can 'squash and merge' via GitHub.

I'll merge as-is without squashing since those commits reference individual issues.


emacs: standard input is not a tty

Hello 👋 I've tried moving evil from travis to github actions, and I've made some progress, but some tests are now skipping, and the emacs 24.5 runner outright fails. Initially I just tried using this action and the same command:
script -eqc 'make test' > /dev/null

which runs
emacs -nw -Q -L . -l lib -l evil-tests.el --eval "(evil-tests-initialize)"

but this (which always worked fine on travis) now failed on github actions, with the error:
emacs: standard input is not a tty

My hacky solution is to add the --batch option to that command, which results in some tests being skipped, and only the emacs 24.5 runner outright failing. I have no idea why 24.5 is the only one failing - I assume emacs changed the way it handled --batch in later releases?
I thought script -eqc... would fool emacs into thinking it had a tty standard input, but when running on github actions, it seems it still knows. Is there some way around this? Thanks in advance!

Hmmm, not actually sure about that, sorry. For some reason this is ring a bell in my mind though... I feel like I've heard something about this behaviour before.

No problem - it's just good to know I'm not overlooking something obvious! If anything comes to mind please drop me a message.


TypeError in MockRequest when 'Host' header set to bytestring

Issue is specific to Python3
An incorrect assumption is made in requests.cookies.MockRequest on Python3, see here:
class MockRequest(object):
    ...
    def get_full_url(self):
        # Only return the response's URL if the user hadn't set the Host
        # header
        if not self._r.headers.get('Host'):
            return self._r.url
        # If they did set it, retrieve it and reconstruct the expected domain
        host = self._r.headers['Host']
        parsed = urlparse(self._r.url)
        # Reconstruct the URL as we expect it
        return urlunparse([
            parsed.scheme, host, parsed.path, parsed.params, parsed.query,
            parsed.fragment
        ])
    ...

In Python2 this works fine where str and unicode objects are allowed interchangeably in urlunparse.
In Python3 this is an issue because host = self._r.headers['Host'] may return a bytestring and         parsed = urlparse(self._r.url) returns a ParseResult with str objects. Combining these two causes urlunparse to throw a fit.
Steps to reproduce:
>>> import requests
>>> a = requests.Request('GET', 'http://www.google.com', headers={'Host': b'www.google.com'})
>>> b = requests.cookies.MockRequest(a)
>>> b.get_full_url()

Yup, this looks wrong to me. It does look like we need to ensure that we have a match between the two types. In fact, we should probably ensure we're always returning the correct type for the platform.

@Lukasa
I've attempted a patch of this issue in PR #3598
Would appreciate your input on the patch.
:smile:

Will follow up with a fix for the dependency on httpbin.org. Please leave this open until then.


add version subcommand (using GoReleaser vars)

Any of these:
kubectx version
kubectx -version
kubectx --version
kubectx -V

Will produce this output:
kubectx v0.9.1-SNAPSHOT-1a50409 (1a50409) 2021-01-09T20:56:06Z

Also works for kubens.

I think I can accept this.

Let's reserve -v for something else in the future like "verbose" option.

let's just do -V and nothing else, like a subcommand or --version.

Also, let's just capture the version number and not date, or commit etc.

Let's do it for kubens while you’re at it as well if you don’t mind.

I think I can accept this.

Let's reserve -v for something else in the future like "verbose" option.

let's just do -V and nothing else, like a subcommand or --version.

Also, let's just capture the version number and not date, or commit etc.

Let's do it for kubens while you’re at it as well if you don’t mind.

[x] Let's reserve -v for something else in the future like "verbose" option.

I didn't add -v

[ ] let's just do -V and nothing else, like a subcommand or --version.

The standard way to do it in Go is to have the version subcommand and Go treats - and -- the same. So -help is the same as --help.
If we're doing only POSIX style, it should be BOTH -V and --version (which would include -version unless we don't want to support normal go flag style).
If we're doing only Go style it should be either version OR -version and --version

[ ] Also, let's just capture the version number and not date, or commit etc.

You're already using GoReleaser, which assumes you'll be capturing that information in some way. If you really don't want that I can take it out, but I trust provably verifiable idempotent builds (which GoReleaser is intended to provide) over "because I said so" builds.
Again, that's your call, but I suggest using at least the first 7 chars of the commit hash, and date is nice to see at-a-glance "is this recent like 6 days ago? or 6 months ago? or 6 years ago"

[x] Let's do it for kubens while you’re at it as well if you don’t mind.

The commit includes both
Consider my rationale and let me know your final say and I'll adjust accordingly. :)

[x] Let's reserve -v for something else in the future like "verbose" option.

I didn't add -v

[ ] let's just do -V and nothing else, like a subcommand or --version.

The standard way to do it in Go is to have the version subcommand and Go treats - and -- the same. So -help is the same as --help.
If we're doing only POSIX style, it should be BOTH -V and --version (which would include -version unless we don't want to support normal go flag style).
If we're doing only Go style it should be either version OR -version and --version

[ ] Also, let's just capture the version number and not date, or commit etc.

You're already using GoReleaser, which assumes you'll be capturing that information in some way. If you really don't want that I can take it out, but I trust provably verifiable idempotent builds (which GoReleaser is intended to provide) over "because I said so" builds.
Again, that's your call, but I suggest using at least the first 7 chars of the commit hash, and date is nice to see at-a-glance "is this recent like 6 days ago? or 6 months ago? or 6 years ago"

[x] Let's do it for kubens while you’re at it as well if you don’t mind.

The commit includes both
Consider my rationale and let me know your final say and I'll adjust accordingly. :)

The standard way to do it in Go is to have the version subcommand and Go treats - and -- the same. So -help is the same as --help.

This is a "program", not necessarily a "Go program". We have a bash based implementation as well, and many users are there. kubectx/kubens do not take subcommands, and I certainly don't want N ways of doing the same thing for the sake of keeping the

If we're doing only POSIX style, it should be BOTH -V and --version

Not necessarily. I think we can live with one of them just fine, just like many programs do.

You're already using GoReleaser, which assumes you'll be capturing that information in some way. If you really don't want that I can take it out, but I trust provably verifiable idempotent builds (which GoReleaser is intended to provide) over "because I said so" builds.

This is not how "trusted builds" work. All those variables can still be forged. Trusting software is a much more harder problem that requires verifying the integrity of even the compiler itself. You can refer to the Reflections on Trusting Trust (1984) article for more on this.
kubectx/kubens are not only distributed here on GitHub. They are still a "bash script" on many platforms. It is distributed on Homebrew, it's on Alpine repos, it's on Debian repos.
Practically none of those build/distribution systems are using GoReleaser. If you add all these variables, you’ll be making pretty much every packager’s job harder.
So I'm ok with kubectx -V printing a simple vX.Y.Z string. I don't know of any scenarios where a user would be interested in build date, git commit etc. ("it's available on GoReleaser" is not a good enough reason to use it.)

The standard way to do it in Go is to have the version subcommand and Go treats - and -- the same. So -help is the same as --help.

This is a "program", not necessarily a "Go program". We have a bash based implementation as well, and many users are there. kubectx/kubens do not take subcommands, and I certainly don't want N ways of doing the same thing for the sake of keeping the

If we're doing only POSIX style, it should be BOTH -V and --version

Not necessarily. I think we can live with one of them just fine, just like many programs do.

You're already using GoReleaser, which assumes you'll be capturing that information in some way. If you really don't want that I can take it out, but I trust provably verifiable idempotent builds (which GoReleaser is intended to provide) over "because I said so" builds.

This is not how "trusted builds" work. All those variables can still be forged. Trusting software is a much more harder problem that requires verifying the integrity of even the compiler itself. You can refer to the Reflections on Trusting Trust (1984) article for more on this.
kubectx/kubens are not only distributed here on GitHub. They are still a "bash script" on many platforms. It is distributed on Homebrew, it's on Alpine repos, it's on Debian repos.
Practically none of those build/distribution systems are using GoReleaser. If you add all these variables, you’ll be making pretty much every packager’s job harder.
So I'm ok with kubectx -V printing a simple vX.Y.Z string. I don't know of any scenarios where a user would be interested in build date, git commit etc. ("it's available on GoReleaser" is not a good enough reason to use it.)


Accessing index of row from within callback

I have a use case where I want to put an "PAID", "PART" or "DUE" message next to an invoice line item.
This would be worked out if the paid amount equals or is partial to the total due.
Using a callback I can access one parameter in my rowData. Is there any way to pass the callback the index of the rowData so it can get the values it needs?
I've seen other issues where scoped slots are suggested, but I can't (yet) get my head around them, and I've not seen an example for vue-table.

Essentially a duplicate of #97


djv: init at 2.0.8-unstable-2021-07-31

Motivation for this change
DJV provides professional review software for VFX, animation, and film production.
I did package the master branch, because the last release is a bit older (2020) and they way third-party dependencies are built has changed somewhat since the 2.0.8 release.
This package was requested in #68937 by @luzpaz.
Fixes #68937.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[ x] Fits CONTRIBUTING.md.

@SuperSandro2000 Thanks for the review! I've removed the pointless newlines and simplified the sed expressions. Please take a look again.

@blitz
A last thing: the commit message

Fixes NixOS#68937

is not necessary, and can be confusing.
The # numbers are Github-specific, and it is not a good practice to put this info. If, e.g., we are faced with the necessity of a migration to a new server, a message like "Fixes #68937" becomes meaningless.
Just remove it.

@blitz
A last thing: the commit message

Fixes #68937

is not necessary, and can be confusing.
The # numbers are Github-specific, and it is not a good practice to put this info. If, e.g., we are faced with the necessity of a migration to a new server, a message like "Fixes #68937" becomes meaningless.
Just remove it.

Good point. I've removed it.


Save user executed commands to a history file

This is the implementation of a feature that saves all user executed commands (: prompt) to a file so that the next time they open mitmproxy those commands are already in their command history.
This has been pretty useful for me when testing issues that would cause mitmproxy to crash (so I didn't have to re-type a bunch of commands again). It has also been pretty useful for the cases when I have to close mitmproxy for any reason during my workflow and reopen it and continue where I left of.

Can we encapsulate the command history into a seperate addon that provides get/add/clear commands? This would automatically make this a singleton and we can re-use it for mitmweb, which should also get command support eventually. :-)

I can for sure try to do it like that. Will give it a shot and commit the attempt as soon as it's ready.

How will this behave when running multiple mitmproxy/mitmdump/mitmweb commands in parallel or different terminal windows?

Yeah, I thought about this. Probably not a problem unless you are able to type a command on both windows at the same time. As soon as you type a command it is saved to the command history, now if you move to the other window, you will have that command in the history there as well. Kinda the same way that happens with bash.
If that is not the desired behavior, then we need to have the command history per PID and when the user leaves the application we copy everything in that process' command history to the main command history file.
Any preferences?

Just to be clear, this is only saving the commands that are typed by the user in mitmproxy's TUI (so mitmdump and mitmweb won't be interfering here).

This seems ready for another review round. I think I covered everything discussed.


feat: add a slot result handler for every slot result

Add a handler for every slot result.
This is convenient for sub-services that need to process Result Slot related data, such as to store some Proof data.

You can just wrap the SlotWorker and put your logic there.

You can just wrap the SlotWorker and put your logic there.

You are right.

But every struct that impl SlotWorker(SimpleSlotWorker) is not pubed

You want to wrap SlotWorker and not SimpelSlotWorker. And Babe and Aura expose them or at least a way to build them.

Yeah.  I can get aura slot worker by build_aura_worker. So I decide to write the following code but
struct AuraWorker<SlotWorker> {
    aura_worker: SlotWorker,
    // TODO: other worker
}

#[async_trait::async_trait]
impl<SlotWorker, B, Proof> sc_consensus_slots::SlotWorker<B, Proof> for AuraWorker<SlotWorker>
where
    B: BlockT,
{
    async fn on_slot(&mut self, slot_info: SlotInfo<B>) -> Option<SlotResult<B, Proof>> {
        todo!()
    }
}

But meet such error:
error[E0119]: conflicting implementations of trait `sc_consensus_slots::SlotWorker<_, _>` for type `AuraWorker<_>`
  --> client\consensus\aura\src\lib.rs:47:1
   |
47 | / impl<SlotWorker, B, Proof> sc_consensus_slots::SlotWorker<B, Proof> for AuraWorker<SlotWorker>
48 | | where
49 | |     B: BlockT,
50 | | {
...  |
53 | |     }
54 | | }
   | |_^
   |
   = note: conflicting implementation in crate `sc_consensus_slots`:
           - impl<B, T> SlotWorker<B, <<T as SimpleSlotWorker<B>>::Proposer as Proposer<B>>::Proof> for T
             where B: BlockT, T: SimpleSlotWorker<B>, T: std::marker::Send, T: Sync;
   = note: downstream crates may implement trait `sc_consensus_slots::SimpleSlotWorker<_>` for type `AuraWorker<_>`
   = note: downstream crates may implement trait `sc_consensus_slots::SimpleSlotWorker<_>` for type `AuraWorker<_>`

Why are you implementing this in the Aura crate directly?

Why are you implementing this in the Aura crate directly?

No, It's my own aura crate not substrate's.

@bkchr Can we export these worker(Aura/Babe) ? If we can, I will issue a PR.

I don't get why you not just do the following:
struct Wrapper<T>(T);

#[async_trait::async_trait]
impl<T: SlotWorker<B, Proof>, B: BlockT, Proof> for Wrapper<T> {
   async fn on_slot(
	&mut self,
	slot_info: SlotInfo<B>,
   ) -> Option<SlotResult<B, <T::Proposer as Proposer<B>>::Proof>> {
       self.0.on_slot(slot_info)
   }
}

I don't get why you not just do the following:
struct Wrapper<T>(T);

#[async_trait::async_trait]
impl<T: SlotWorker<B, Proof>, B: BlockT, Proof> for Wrapper<T> {
   async fn on_slot(
	&mut self,
	slot_info: SlotInfo<B>,
   ) -> Option<SlotResult<B, <T::Proposer as Proposer<B>>::Proof>> {
       self.0.on_slot(slot_info)
   }
}

@bkchr Sorry, your code doesn't seem quite right, I suspect what you're trying to express is what was mentioned earlier. But as I said, writing this way won't compile.


67 jwks api and key rotation (do not yet merge)

@gianlucafrei : I've merged with latest from main, Looks like something in the test area has changed. While all tests run individually, when running all together I get a few errors, all based on a blacklist.db file that is reported to be locked. Any idea?
(Besides that, you can finally merge when OK).


Integration refactor

split and re organize integration code
make additional integrations (like router) optional
prepare for more integrations

@nekath @Szeliga @marcinkornek requesting for review :)

I love namespaces, we should not be selfish and populate global namespace too much :)
But I don't want to type too much while using core methods.
This PR is important to discuss much more since it changes whole API.


Update timeout for .github/workflows/tests.yaml

This is an automated pull request to update default timeouts for all jobs in .github/workflows/tests.yaml that do not currently contain a default timeout property.
Please review these changes closely to ensure that all jobs have sufficient time to run. If a job needs more time, please add a timeout property to that job to override the organization default.
Additionally, please be attentive to unintended changes to the workflow YAML file, as the parser is not perfect.
Lastly, note that it is up to the reviewer to merge this pull request and delete the PR branch once they are satisfied with the changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 13.43%. Comparing base (bf671d1) to head (1ccd88d).
Report is 99 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #951       +/-   ##
===========================================
- Coverage   60.19%   13.43%   -46.76%
===========================================
  Files          50       50
  Lines        4032     4079       +47
===========================================
- Hits         2427      548     -1879
- Misses       1300     3453     +2153
+ Partials      305       78      -227

Flag
Coverage Δ

integration-test
13.43% <ø> (-46.76%)
:arrow_down:

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

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


Does this repo have active maintainers?

Is this repo dead?  I don't see any recent commits with new versions of the agent, no responses to issues/pull-requests, etc?

No the repo is not dead, we have been making changes slowly, we merged 2-3 PRs last week.


Another option for searching

Describe your suggested feature
So when you search you would have an option to show anything other than what you search for for example, if I search "romance" and then press on this option it would show any tag I have in my library except for manga/manhua/manhwa with the romance tag/"romance" (word) in their description
Sorry if unclear
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 1.9.0.
[X] I will fill out all of the requested information in this form.

There is though.  For example, '-romance' so that it shows all entries without romance tag.

Tnx, didn't know about it


SE-net module placement in inception resnet

Hi there,
I notice that the original paper says that for resnet, the SE-block is applied to "The non-identity branch  of the residual nodule". And in the inception network after each inception block.
In you inception-resnet implementation, you seem to have applied the SE module to the identity branch of each block instead. (i.e) to the net variable rather than the (up*scale) variable.
Is there any reason for this? Did this configuration work for you?

Revising the SE module placement in Inception_resnet_v2 is completed: https://github.com/kobiso/SENet-tensorflow-slim/commit/51b6d27b57498ce163d3b21acdb45292d1857619


JS: Object.defineProperty "undefined namespaces" don't merge cross-file

// @filename: 1.ts
Object.defineProperty(a.c, "prototype", { value: {} })
// @filename: 2.ts
const a = {}
a.c = function() { }

Expected behavior:
Behave the same as a.c.prototype = {} does today. (as seen in jsContainerMergeJsContainer)
Related Issues:
follow-on work discovered in #32944

Turns out bindPotentiallyMissingNamespaces doesn't handle normal prototype properties either, presumably because a missing prototype property needs to be handled differently than a missing namespace. I'll close this since Object.defineProperty doesn't need to support what normal assignment doesn't.


JPG and PNG static resources not displayed in browser

I have added static resrouces to spring cloud project and noticed that static resources served incorrectly.
Png resource not displayed after downloading from backend, Jpg displayed wrong.
Here is my build.gradle content:
buildscript {
    ext {
        springBootVersion = '2.0.0.M6'
    }
    repositories {
        mavenLocal()
        mavenCentral()
        jcenter()
        maven {
            url 'https://repo.spring.io/libs-milestone'
        }
    }
    dependencies {
        classpath("org.springframework.boot:spring-boot-gradle-plugin:${springBootVersion}")
    }
}

apply plugin: 'java'
apply plugin: 'org.springframework.boot'

repositories {
    maven {
        url 'https://repo.spring.io/libs-milestone'
    }
}

dependencies {
    compile (group: 'org.springframework.cloud', name: 'spring-cloud-starter-gateway', version: '2.0.0.M5')
    compile group: 'org.springframework.boot', name: 'spring-boot-starter-webflux'
}

Here is Application source:
import static org.springframework.web.reactive.function.server.RouterFunctions.resources;

@Configuration
@SpringBootApplication
public class GatewayApplication {

    @Bean
    public RouterFunction<ServerResponse> monoRouterFunction() {
        return resources("/**", new ClassPathResource("public/"));
    }

    public static void main(String[] args) {
        SpringApplication.run(GatewayApplication.class, args);
    }

}

Here is how jpg request/response looks like:

And here is how png request/response looks like:

How is this a gateway problem? You're not going through the gateway to view the images.

Idea was that gateway is also host all static resources, and all request goes to same host(both static and rest requests). This way we escape CORS issues.

Putting the following in application.properties:
spring.webflux.static-path-pattern=/static/*

and a jpg and png in src/main/resources/static
and this bean
	@Bean
	public RouteLocator routes(RouteLocatorBuilder builder) {
		return builder.routes()
				.route(r -> r.path("/get").uri("http://httpbin.org:80"))
				.build();
	}

I was able to see the images at http://localhost/static/test.png and http://localhost/static/test.jpg  and http://localhost/get proxied thru.
You'll need to post a minimal project that recreates the problem.

I have created simple project. However i cant found class RouteLocatorBuilder ` so it was little different:
https://github.com/muzuro/spring-cloud-gateway-issue184/commit/9a01d7763089ee2c825e16e50ac1501f6f1d13a4
When i made request to http://localhost:8080/static/yc.png it failed with:
2018-02-07 23:04:46.373 [reactor-http-nio-2] ERROR o.s.b.a.w.r.e.DefaultErrorWebExceptionHandler.logError:197 - Failed to handle request [GET http://localhost:8080/static/soren.jpg]
java.lang.NullPointerException: null
	at org.springframework.cloud.gateway.handler.RoutePredicateHandlerMapping.lambda$lookupRoute$2(RoutePredicateHandlerMapping.java:81)
	at reactor.core.publisher.FluxFilterFuseable$FilterFuseableSubscriber.tryOnNext(FluxFilterFuseable.java:122)
	at reactor.core.publisher.FluxIterable$IterableSubscriptionConditional.fastPath(FluxIterable.java:485)
	at reactor.core.publisher.FluxIterable$IterableSubscriptionConditional.request(FluxIterable.java:385)
	at reactor.core.publisher.FluxFilterFuseable$FilterFuseableSubscriber.request(FluxFilterFuseable.java:170)

Then i added manual route: https://github.com/muzuro/spring-cloud-gateway-issue184/commit/3ee49c00f0df0b38777777f832a46f8c6c4858da
And it worked, resources served without problems. Will research what was added at main project. There is also other routes and controlles.

boot M7 and gateway M5 are the latest, that why.

OK. Feel free to reopen if you can find an issue that needs fixing.

@spencergibb Which version of spring boot and gateway you recommend to use?

the ones I mentioned. We'll have a new milestone of gateway that will go with boot RC1 soon


Adding Features

Adding 2 menus - header and footer ones
Favourites

Reworked half of the pull request in a different way.


[Android] ProgressBar animation is not working when using the theme Theme.AppCompat.DayNight.NoActionBar in Platform Views

ProgressBar animation is not working when embedding native views in a Flutter app, specifically implementing preloader when the banner is being loaded
Steps to Reproduce

Refer to the documentation Hosting native Android views in your Flutter app with Platform Views.

In the file styles.xml under android/app/src/main/res/values/styles.xml, change the theme to Theme.AppCompat.DayNight.NoActionBar

<style name="NormalTheme" parent="Theme.AppCompat.DayNight.NoActionBar" />

Run your sample application.

Expected results:
Here is a sample snapshot using a different theme, example is the default style when creating a new Flutter project:
<style name="NormalTheme" parent="@android:style/Theme.Light.NoTitleBar">

There should be an animation on the ProgressBar just like the example above.
Actual results:
Actual themes used when the behavior was being observed:
<style name="NormalTheme" parent="Theme.AppCompat.DayNight.NoActionBar" />

The ProgressBar is either stuck/idle.

Code sample
Attached is a minimal reproducible sample.

flutter_sample.zip

Logs

flutter run --verbose
[  +33 ms] executing: sysctl hw.optional.arm64
[  +16 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[   +1 ms] executing: [/Users/user/Developer/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +13 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 12cb4eb7a009f52b347b62ade7cb4854b926af72
[        ] executing: [/Users/user/Developer/flutter/] git tag --points-at 12cb4eb7a009f52b347b62ade7cb4854b926af72
[  +61 ms] Exit code 0 from: git tag --points-at 12cb4eb7a009f52b347b62ade7cb4854b926af72
[        ] 3.7.6
[  +38 ms] executing: [/Users/user/Developer/flutter/] git rev-parse --abbrev-ref --symbolic @{upstream}
[  +21 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{upstream}
[        ] origin/stable
[        ] executing: [/Users/user/Developer/flutter/] git ls-remote --get-url origin
[  +15 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +50 ms] executing: [/Users/user/Developer/flutter/] git rev-parse --abbrev-ref HEAD
[  +16 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[   +1 ms] executing: sw_vers -productName
[  +31 ms] Exit code 0 from: sw_vers -productName
[        ] macOS
[        ] executing: sw_vers -productVersion
[  +31 ms] Exit code 0 from: sw_vers -productVersion
[        ] 13.2.1
[        ] executing: sw_vers -buildVersion
[  +28 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 22D68
[        ] executing: uname -m
[  +17 ms] Exit code 0 from: uname -m
[   +1 ms] x86_64
[  +31 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +88 ms] executing: /Users/user/Library/Android/sdk/platform-tools/adb devices -l
[  +21 ms] executing: sysctl hw.optional.arm64
[   +8 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[        ] executing: xcrun xcodebuild -version
[ +247 ms] Exit code 0 from: xcrun xcodebuild -version
[   +3 ms] Xcode 14.2
           Build version 14C18
[   +3 ms] executing: xcrun xcdevice list --timeout 2
[   +2 ms] xcrun simctl list devices booted iOS --json
[        ] executing: xcrun simctl list devices booted iOS --json
[  +10 ms] executing: xcrun simctl list devices booted
[ +204 ms] Exit code 0 from: xcrun simctl list devices booted
[        ] == Devices ==
           -- iOS 16.2 --
               iPhone 14 Pro Max (78B01F9C-514E-4766-9DC6-ECE59E05BD40) (Booted)
[  +59 ms] List of devices attached
           emulator-5554          device product:sdk_gphone64_x86_64 model:sdk_gphone64_x86_64 device:emu64x transport_id:2
[ +229 ms] {
                      "devices" : {
                        "com.apple.CoreSimulator.SimRuntime.iOS-16-2" : [
                          {
                            "lastBootedAt" : "2023-02-22T22:22:13Z",
                            "dataPath" : "\/Users\/user\/Library\/Developer\/CoreSimulator\/Devices\/78B01F9C-514E-4766-9DC6-ECE59E05BD40\/data",
                            "dataPathSize" :<PHONE_NUMBER>,
                            "logPath" : "\/Users\/user\/Library\/Logs\/CoreSimulator\/78B01F9C-514E-4766-9DC6-ECE59E05BD40",
                            "udid" : "78B01F9C-514E-4766-9DC6-ECE59E05BD40",
                            "isAvailable" : true,
                            "logPathSize" : 274432,
                            "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-14-Pro-Max",
                            "state" : "Booted",
                            "name" : "iPhone 14 Pro Max"
                          }
                        ]
                      }
                    }
[+2691 ms] [
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "16.2 (20C52)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad13,18",
                        "identifier" : "41AE502C-10A8-492F-A1B9-268AE7DC634E",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-10-1",
                        "modelName" : "iPad (10th generation)",
                        "name" : "iPad (10th generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "16.2 (20C52)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone14,6",
                        "identifier" : "3F23A51A-B690-4DCC-B133-AD7A0B5220FC",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-se3-1",
                        "modelName" : "iPhone SE (3rd generation)",
                        "name" : "iPhone SE (3rd generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "16.2 (20C52)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad14,5",
                        "identifier" : "9BD38BC8-5B5B-4AE1-AC30-4F634EF5C0F3",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-pro-12point9-6th-1",
                        "modelName" : "iPad Pro (12.9-inch) (6th generation)",
                        "name" : "iPad Pro (12.9-inch) (6th generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "16.2 (20C52)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad14,3",
                        "identifier" : "3626F91B-471C-4754-91A2-3CD8559298BB",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-pro-11-4th-1",
                        "modelName" : "iPad Pro (11-inch) (4th generation)",
                        "name" : "iPad Pro (11-inch) (4th generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "16.2 (20C52)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad13,17",
                        "identifier" : "DD1E64BC-50FA-4A1D-B873-1F45B0ABBC8F",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-air5-1",
                        "modelName" : "iPad Air (5th generation)",
                        "name" : "iPad Air (5th generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "16.2 (20C52)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone15,3",
                        "identifier" : "78B01F9C-514E-4766-9DC6-ECE59E05BD40",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-14-pro-max-1",
                        "modelName" : "iPhone 14 Pro Max",
                        "name" : "iPhone 14 Pro Max"
                      },
                      {
                        "simulator" : false,
                        "operatingSystemVersion" : "13.2.1 (22D68)",
                        "interface" : "usb",
                        "available" : true,
                        "platform" : "com.apple.platform.macosx",
                        "modelCode" : "MacBookPro15,1",
                        "identifier" : "DBFDA7DB-8321-5FD2-A99E-96FAAE2E66C7",
                        "architecture" : "x86_64h",
                        "modelUTI" : "com.apple.macbookpro-15-retina-touchid-2018",
                        "modelName" : "MacBook Pro",
                        "name" : "My Mac"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "16.2 (20C52)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad14,1",
                        "identifier" : "B0A71B57-B78D-49E2-98ED-F249B229797B",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-mini6-1",
                        "modelName" : "iPad mini (6th generation)",
                        "name" : "iPad mini (6th generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "16.2 (20C52)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone14,7",
                        "identifier" : "FFB16B72-ED8F-4D3F-B7E5-4B50AED92C32",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-14-1",
                        "modelName" : "iPhone 14",
                        "name" : "iPhone 14"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "16.2 (20C52)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone15,2",
                        "identifier" : "A5C6090F-8D3F-4496-A24A-E0988985CB27",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-14-pro-1",
                        "modelName" : "iPhone 14 Pro",
                        "name" : "iPhone 14 Pro"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "16.2 (20C52)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone14,8",
                        "identifier" : "D66532B7-CD62-4197-A33E-B6FC3CB1ECD7",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-14-plus-1",
                        "modelName" : "iPhone 14 Plus",
                        "name" : "iPhone 14 Plus"
                      }
                    ]
[   +8 ms] /Users/user/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell getprop
[  +63 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +86 ms] Multiple devices found:
[   +1 ms] ro.hardware = ranchu
[   +4 ms] sdk gphone64 x86 64 (mobile) • emulator-5554                        • android-x64 • Android 13 (API 33) (emulator)
[        ] iPhone 14 Pro Max (mobile)   • 78B01F9C-514E-4766-9DC6-ECE59E05BD40 • ios         • com.apple.CoreSimulator.SimRuntime.iOS-16-2 (simulator)
[        ] [1]: sdk gphone64 x86 64 (emulator-5554)
[        ] [2]: iPhone 14 Pro Max (78B01F9C-514E-4766-9DC6-ECE59E05BD40)
[   +1 ms] Please choose one (To quit, press "q/Q")
[        ] :
[+734801 ms] q
[  +18 ms] "flutter run" took 738,727ms.
[  +37 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      FlutterCommand._chooseOneOfAvailableDevices (package:flutter_tools/src/runner/flutter_command.dart:1542:7)
           <asynchronous suspension>
           #2      FlutterCommand.findAllTargetDevices (package:flutter_tools/src/runner/flutter_command.dart:1498:39)
           <asynchronous suspension>
           #3      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:497:15)
           <asynchronous suspension>
           #4      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1381:5)
           <asynchronous suspension>
           #5      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1257:27)
           <asynchronous suspension>
           #6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #7      CommandRunner.runCommand (package:args/command_runner.dart:209:13)
           <asynchronous suspension>
           #8      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:283:9)
           <asynchronous suspension>
           #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #10     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
           <asynchronous suspension>
           #11     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:64:9)
           <asynchronous suspension>
           #12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #13     main (package:flutter_tools/executable.dart:91:3)
           <asynchronous suspension>

[ +260 ms] ensureAnalyticsSent: 254ms
[        ] Running 0 shutdown hooks
[        ] Shutdown hooks complete
[        ] exiting with code 1

flutter analyze
Analyzing flutter_sample...
No issues found! (ran in 1.2s)

flutter doctor -v
[✓] Flutter (Channel stable, 3.7.6, on macOS 13.2.1 22D68 darwin-x64, locale en)
    • Flutter version 3.7.6 on channel stable at /Users/user/Developer/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 12cb4eb7a0 (5 days ago), 2023-03-01 10:29:26 -0800
    • Engine revision ada363ee93
    • Dart version 2.19.3
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/user/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

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

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

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

[✓] VS Code (version 1.75.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.58.0

[✓] Connected device (4 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554                        • android-x64    • Android 13 (API 33) (emulator)
    • iPhone 14 Pro Max (mobile)   • 78B01F9C-514E-4766-9DC6-ECE59E05BD40 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-2 (simulator)
    • macOS (desktop)              • macos                                • darwin-x64     • macOS 13.2.1 22D68 darwin-x64
    • Chrome (web)                 • chrome                               • web-javascript • Google Chrome 110.0.5481.177

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

• No issues found!

Issue is reproducible using the code sample provided above on the stable & master channels.

flutter doctor -v
[✓] Flutter (Channel stable, 3.7.6, on macOS 13.2.1 22D68 darwin-arm64, locale en-GB)
    • Flutter version 3.7.6 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 12cb4eb7a0 (6 days ago), 2023-03-01 10:29:26 -0800
    • Engine revision ada363ee93
    • Dart version 2.19.3
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

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

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

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

[✓] Android Studio (version 2022.1)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 72.1.4
    • Dart plugin version 223.8617.8

[✓] VS Code (version 1.76.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.60.0

[✓] Connected device (3 available)
    • M2007J20CG (mobile) • adb-5dd3be00-17AYzd._adb-tls-connect._tcp. • android-arm64  • Android 12 (API 31)
    • macOS (desktop)     • macos                                      • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)        • chrome                                     • web-javascript • Google Chrome 110.0.5481.177

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

• No issues found!

[!] Flutter (Channel master, 3.9.0-1.0.pre.72, on macOS 13.2.1 22D68 darwin-arm64, locale en-GB)
    • Flutter version 3.9.0-1.0.pre.72 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 8557ffa024 (4 hours ago), 2023-03-06 22:38:59 -0500
    • Engine revision e2bd89f97e
    • Dart version 3.0.0 (build 3.0.0-290.0.dev)
    • DevTools version 2.22.2
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

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

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

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

[✓] Android Studio (version 2022.1)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 72.1.4
    • Dart plugin version 223.8617.8

[✓] VS Code (version 1.76.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.60.0

[✓] Connected device (3 available)
    • M2007J20CG (mobile) • adb-5dd3be00-17AYzd._adb-tls-connect._tcp. • android-arm64  • Android 12 (API 31)
    • macOS (desktop)     • macos                                      • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)        • chrome                                     • web-javascript • Google Chrome 110.0.5481.177

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Reducing priority to match Flutter's priority definitions.
Some questions that may help us find a solution or workaround for you:
Is it possible to use a different theme or a different progress bar?
Is this a regression, or has it always been an issue?


clean up equinox mlp implementation

getting back in the saddle :)

I appreciate the effort, but I don't think it'll work without further adjustments for the following reason: jax.nn.relu is a parameter-free function and Optax has problems with initialising such layers...
src/bmi/estimators/neural/_estimators.py:167: in estimate
    return self.estimate_with_info(x, y).mi_estimate
src/bmi/estimators/neural/_estimators.py:144: in estimate_with_info
    training_log, new_critic = basic_training(
src/bmi/estimators/neural/_basic_training.py:56: in basic_training
    opt_state = optimizer.init(critic)
../../micromamba/envs/bmi/lib/python3.10/site-packages/optax/_src/combine.py:50: in init_fn
    return tuple(fn(params) for fn in init_fns)
../../micromamba/envs/bmi/lib/python3.10/site-packages/optax/_src/combine.py:50: in <genexpr>
    return tuple(fn(params) for fn in init_fns)
../../micromamba/envs/bmi/lib/python3.10/site-packages/optax/_src/transform.py:353: in init_fn
    mu = jax.tree_util.tree_map(  # First moment
../../micromamba/envs/bmi/lib/python3.10/site-packages/jax/_src/tree_util.py:312: in tree_map
    return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))
../../micromamba/envs/bmi/lib/python3.10/site-packages/jax/_src/tree_util.py:312: in <genexpr>
    return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))
../../micromamba/envs/bmi/lib/python3.10/site-packages/optax/_src/transform.py:354: in <lambda>
    lambda t: jnp.zeros_like(t, dtype=mu_dtype), params)
../../micromamba/envs/bmi/lib/python3.10/site-packages/jax/_src/numpy/lax_numpy.py:2248: in zeros_like

One possible solution in Equinox is filtering, but I worry that it'll make the rest of the codebase a bit more complex. What do you think?