Remember last active player tool

The player tools page has been refactored (again), this time so we can use React hooks to more easily tie sessionStorage to state. Specifically, this allows player tools to remember the user's last active tool. If a user navigates away from player tools, when they return, they'll be shown the last tool used (instead of the voyage calculator tab by default). When combined with a non-class component that also saves form options in session (currently only the profilecrew tool), this will bring a user back to the exact player tool and form setup that they left. The remembered settings are forgotten when the browser is closed.
Other small enhancements:
After pasting the player data, the import form now automatically tries to parse the data without having to click the import button.
A more informative error is shown if a user tries to import the login page instead of valid player data. See #176
If the player data is stale (i.e. last imported 6 hours 1 hour ago or more), we now show a warning message recommending the user update now. Edited to add: the stale threshold is currently set to 1 hour, but I was originally thinking it should be set to 6 hours.
The "Update now" and "Clear player data" have been moved to their own dedicated "Profile options" dropdown menu.
The "Share your player profile" message can now be dismissed. If dismissed, it can be shown again from a new command in the aforementioned "Profile options" menu. This dismissed setting should persist across sessions.
Storage util has been updated to retrieve from sessionStorage and localForage asynchronously, better handle undefined values, and to ensure that default values are not stored.

Sometimes (yeah unhelpful I know) when I switch to the Crew (Mobile) tab, it's spitting tons of errors in the JS console, and giving me a blank (but CSS themed) page.  Now that I've started to try and make notes, it's inevitably behaving perfectly, so if I can reproduce I'll come back with screenshots and text.

@AlexCPU Is it a "missing equipment slots" error? I've been assuming that that happens because of the same issue that causes #3, which I don't think has been resolved yet. Otherwise I'm not see any other problem here with the Crew (Mobile) tab, but I'll look into this and make sure my changes aren't making this worse. If you encounter it again, please let me know.

I've had the same error crop up. A look at the console shows the repeated error
Uncaught TypeError: can't assign to property "proficiency" on 0: not an object
componentDidMount profile_crew2.tsx:77
componentDidMount profile_crew2.tsx:75
componentDidMount profile_crew2.tsx:74
React 2
unstable_runWithPriority scheduler.production.min.js:18
React 4
unstable_runWithPriority scheduler.production.min.js:18
React 13
10376 production-app.js:181
setTimeout handler49228/t.exports</< ready.js:37
10376 production-app.js:179
promise callback10376/< production-app.js:153
promise callback*10376 production-app.js:39
Webpack 4
profile_crew2.tsx:77:5

Interesting, thanks for the error. Let's see if I can reproduce it.

@AlexCPU @joshurtree I'm actually encountering this same error on the live site now. Can you check if the Crew (mobile) tab on datacore.app is working for you?

You get that error if you navigate to Crew (Mobile) too fast, from memory.

That's weird. I had never noticed that before, but I guess it's not usually the first tool I go to. This might cause problems with this update, because player tools will want to switch to the Crew (Mobile) tab automatically if it was the last tool used by a player. Will have to test further.

The tab is very weird. Also see #3.


Bequeath-your-data-and-die needs to return 400 incase of wrong input and not 204

Bequeath-your-data-and-die service will process the request ,  if the "application-name" in the request-body matches the "http-server-interface-capability/application-name".
This functionality is working fine.
But, incase of wrong "application-name" , the service should return 400 (BAD_REQUEST from client) and not 204(as its not processing the service)
Change required :
server/controllers/individualServices.js need to include response code "responseCodeEnum.code.BAD_REQUEST;" to support sending this response incase of unacceptable application-name.

As per ApplicationPattern version 2.0.0 , application-name is configurable.
So, this issue becomes obsolete.


Add large number tests

Signed-off-by: feihujiang<EMAIL_ADDRESS>

Exist Issues
#110

After consulting with @feihujiang, we decided to close this PR for now and reopen it at a later time


 The site in question doesn't have SSL support. It appears that using the --depth option requires SSL support on the remote. We started using --depth 1 to reduce download size of the plugins. I don't think we'll be changing plug.vim because of this.
Work arounds I can think of are:

Mirror this repository on github.com, on a public repository. No issue, as seems licensed under Public Domain. Then simply add it to your ~/.vimrc as Plug 'LemonBoy/vim-scheme'.

Run this command to clone locally: git clone http://git.foldling.org/vim-scheme.git ~/.vim/plugged/vim-scheme' Then add it to the ~/.vimrcwith the following line:Plug '~/.vim/plugged/vim-scheme'`
By leading with a tilda, you indicate the plugin shouldn't be cloned/managed, just put on the rtp.

It appears that using the --depth option requires SSL support on the remote.

Hmm, it's clearly something I wasn't aware of.
But anyway, you can put let g:plug_shallow = 0 in your vimrc to disable shallow clone. It's a global option and currently it's not possible to disable it for a subset of plugins.

Well, that's unfortunate, the shallow cloning is quite useful and disabling it globally is awful. Maybe you could add some code to detect the git-over-dumb-protocols urls and disable the shallow clone accordingly.
Anyway I'll just add it to the rtp manually for the time being.

@LemonBoy We could. Most servers have SSL support though, it is kind of a standard feature for authentication. Considering that, I think it is simplest to just document rather than add logic to the code. I've added a section to the FAQ, as I can see it happening more than once. Just not very often.

@starcraftman Not that I want to. Most users don't have the problem and doing so will inevitably complicate the code. Testing it is also tricky.

@junegunn Agreed, closing this as won't fix. I think the documentation is enough.


soc: riscv: cleanup machine timer related code

After some analysis I found out that there's no machine timer provided
by the "riscv" vendor, so the existing "riscv,machine-timer" binding was not
designed to fit all vendors. There are some specs for the mtime/mtimecmp
registers (this is why we can have a single driver), but the actual
register layout or implementations differ among vendors. One of them is CLINT
(Core Local Interruptor) which includes machine timer registers. A few platforms already
defined it correctly, but it was never used to obtain mtime/mtimecmp base address nor interrupts.
This patch moves all the information related to machine timer in Devicetree (aligning with Linux in some cases) and removes definitions from soc.h.
Supersedes https://github.com/zephyrproject-rtos/zephyr/pull/48382
Part of RISC-V soc.h cleanup/removal.

This in general LGTM.
The only problem I see is that probably CLINT would have required a different driver class (maybe syscon instead of timer?) because it really is a bag of mixed nuts. You have registers for timer, registers for user-generated interrupts and even registers for IPI in the same MMIO region.

I agree that this design isn't great, the fact that each vendor places mtime/mtimecmp in different places doesn't help to find a nice solution. The lack of proper DT description really hid the problem or the complexity.


Expose SCAF AA + Repl extensible change

I made the following changes:

Expose SCAF AA pointer for the repl to understand which analysis contributes to what.
Repl changes to be extensible
Automatic formatting change of src/core/loop_scc_attributes/src/StackObjectClonableSCC.cpp

There are two problems with the change added to LoopDependenceInfo.hpp.

the API "void *getSCAFLoopAA()" breaks now the abstraction of dependence graphs that hidden the set of analyses that power them. If this is needed, then we should re-think about the abstraction rather than creating a "leaking abstraction" like this one.
if the API void *getSCAFLoopAA();     does not take any parameter, we should put "void" in the parameter list so we get a compilation error if we accidentally pass parameters to a call to it.

Addressed point 2.
For point 1, I understand it breaks the abstraction. This leaky abstraction is a hack required for cpf-repl to play with the SCAF analysis chain in order to get the set of analyses that contribute to a query. I can't think of another use for this abstraction. We can mark in the comment that this is not for normal use.
It'll be great if there is a better way to get the LoopAA pointer that doesn't break the abstraction.

@scampanoni Maybe one idea to make the situation better: we can wrap this function in a different namespace (something very explicit like NOELLE::LeakyAbstraction), so it won't be mistaken for other uses while we try to find a better solution to replace it.

If it's a hack required for cpf-repl then why does it need to be merged into the main branch instead of maintained in its own branch or fork?

Addressed @tommymcm 's point. I reverted the changed files for this PR.

This should be ready for merge @scampanoni


Suppress Background Notification

Fixes #683
Allow the suppression of the job ... finished message after a background process finishes.  Message suppression is controlled by the new builtin variable suppress-background.  A value of "true" will suppress any background notification messages.  Errors are always printed regardless of how suppress-background is set.

Why don't you use bool for the variable? In elvish it would be set with $true or $false.

Ha, didn't even realize it could be a bool, was thinking in terms of environmental variables.  Other changes fixed too.


fix(table): support buttons props

Description
add new props to support multiple buttons in table component
Why
handle multiple buttons
Issue
NA
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[ ] I have performed IP checks for added or updated 3rd party libraries
[ ] I have created and linked IP issues or requested their creation by a committer
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[ ] I have added tests that prove my changes work
[ ] I have checked that new and existing tests pass locally with my changes
[ ] I have commented my code, particularly in hard-to-understand areas

@oyo can you review and release these changes immediately?

@oyo can you review and release these changes immediatel

ok will update


changed file based prolog command to run swipl from file's directory

This fixes errors when a prolog file requires other files with relative paths

Every time we make a switch like this we have to gate off Windows vs *.nix (you'll see examples with some of the other langs).

Let's go with it and see if we run into Windows issues later.


Pull WASM plugins from Google Container Registry using Workload Identity?

Can Istio take advantage of Workload Identity to pull WASM plugins as OCI images from Google Container Registry?
When running inside GCP it's typically enough to grant the Service Account roles/storage.objectViewer on the underlying Storage Bucket that backs the registry.
GCR is explicitly mentioned in the blog announcement, but so far I was not able to make this work for Istio. Any links to examples for such a configuration would be appreciated.

cc @igsong

@stellirin As mentioned in the announcement, Istio 1.12 does not support the private repository.
From Istio 1.14, it is supported via ImagePullSecret field of WasmPlugin.
After getting a json key file from GCP, you can create a secret using this command.
kubectl create secret docker-registry <secret-name> -n <namespace>\
  --docker-server=gcr.io \
  --docker-username=_json_key \
  --docker-password="$(cat <key-file-path>)" \
  --docker-email=<some-email>

Then, fill imagePullSecret with secret-name.

Thank you for the detailed responses. I upgraded our clusters this week to 1.14 and wanted to investigate this new functionality. For now we'll probably stay with our existing solution (internal http server) as it's generally our policy to avoid SA keys for use within GCP.

Does
https://github.com/google/go-containerregistry/blob/623023e6c2442f4f29dfaee5334fa5e0c125cc3b/cmd/krane/main.go#L52
do what we want?
BTW, in the meantime you could always run some OCI proxy doing the auth, or
a local caching registry, etc. Not trivial but would work around the
limitations
On Wed, Jun 15, 2022 at 11:17 PM Adam Farden @.***>
wrote:

Closed #39462 https://github.com/istio/istio/issues/39462 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/39462#event-6818305869, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXNZGC2RASCWEGDGI2TVPLBG3ANCNFSM5Y3FLYEQ
.
You are receiving this because you commented.Message ID:
<istio/istio/issue/39462/issue_event/6818305869 @.***
com>

@howardjohn Yes. That would be the native support for GCR. (as well as ECR & ACR).
Do you think it worth to support them?

Hmm.. my misread again. it should work. I will try to test it. Thanks @howardjohn


Scala 3 project build issue : scala compiler and scala library inconsistencies

Current Behavior
Hello, I am trying to compile a scala 3 project with gradle .
The build is faling for my app (stackoverflow error during scala compile phase even with big stack size) but as you can see in the logs the wrong scala library version si picked.
I am using scala 3 but library 2.13.12 is picked  :
unhandled exception while running posttyper on  [...] ProcessorLive.scala

  An unhandled exception was thrown in the compiler.
  Please file a crash report here:
  https://github.com/scala/scala3/issues/new/choose
  For non-enriched exceptions, compile with -Yno-enrich-error-messages.

     while compiling: /mnt/c/dalhy/heatws/src/main/scala/fr/edf/dtg/dalhy/services/HeatWSProcessorLive.scala
        during phase: posttyper
                mode: Mode(ImplicitsEnabled)
     library version: version 2.13.12
    compiler version: version 3.4.1
            settings: -Xunchecked-java-output-version 8 -bootclasspath /home/loic/.gradle/caches/modules-2/files-2.1/org.scala-lang/scala-library/2.13.12/[...]

The probleme seems to be with the bootclasspath parameter. I've tried some exclude and version force policies as you can see in my build.gradle file :
plugins {
    id 'scala'
}

version = "1.0.0"

configurations {
    runtime.exclude group: "org.scala-lang", module: "scala-library"
}

configurations {
    all {
        resolutionStrategy {
            eachDependency { details ->
                if (details.requested.group == 'org.scala-lang') {
                    detail.exclude(group: "org.scala-lang", module: "scala-library")
                }
            }
        }
    }
}
ext {
    scalaMajorVersion = '3'
    scalaVersion = "$scalaMajorVersion.4.1"
}

dependencies {
    zinc ("com.typesafe.zinc:zinc:1.9.6"){
        exclude( group: "org.scala-lang", module: "scala-library")
    }
    zinc "org.scala-lang:scala3-library_3:$scalaVersion"
    implementation "org.scala-lang:scala3-library_3:$scalaVersion"
    implementation "com.softwaremill.sttp.client3:zio-json_$scalaMajorVersion:3.9.5"
    testImplementation("dev.zio:zio-test_$scalaVersion:2.0.16")
}

repositories {
    mavenCentral()
}

tasks.withType(ScalaCompile) {
    scalaCompileOptions.additionalParameters = ["Xss256m"]
}

test {
    useJUnitPlatform()
}

Is there a way to fix this? Thanks !
Expected Behavior
Build should use the 3.4.1 library for compile vers and library version because it is the scala version I have defined for my build
Context (optional)
No response
Steps to Reproduce
Here is the reproduction project :
https://github.com/loicdescotte/groovy-scala3-issue/tree/groovy-dsl
Run :
./gradlew clean build --debug | grep scala-lib

It will output :
[org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Resolve scala-library-2.13.12.jar (org.scala-lang:scala-library:2.13.12)' started

Gradle version
8.x
Build scan URL (optional)
No response
Your Environment (optional)
Gradle 8, WSL and Windows

The message you are observing is about zinc dependencies. Zinc itself is using 2.13.
If you change the zinc version to 2.0.0-alpha13, the message about 2.13 you're observing will go away.
Note that in general, zinc dependencies should not affect your project dependencies. If you observe different behavior, please open a new issue with a reproducer (please make sure to change workflow argument to get GH action failing).


[.NET HTML][Functionality] [Toggle Visibility with Expand Collapse is not working]

Platform

[ ] .NET HTML

Author or host
we are sending HTML to Outlook along with Adaptive cards
Version of SDK
AdaptiveCards.Rendering.HTML version 2.3.0
Details
We are generating HTML from Adaptive cards using AdaptiveCards.Rendering.HTML, however we have noticed that Toggle Visibility within Adaptive cards is getting generated as HTML however the Toggle Visibility functionality is not working as expected.

@niravk-microsoft is there a reason you are using our .NET HTML renderer? So heads up that we've been investigating deprecating it and it's not always uptodate with the latest features etc. @dclaux do you have an alternative to them using our .NET HTML renderer at all? Thanks

@niravk-microsoft this will never work in Outlook. There is no way to achieve any kind of dynamic behavior in the HTML body of an email. Action.ToggleVisibility requires client-side JavaScript execution, and there is never any custom JavaScript allowed in traditional HTML emails.

Thanks for the information. For now I am marking this as closed because if as mentioned HTML body in email does not allow JavaScript to execute in traditional email then we may not need this for now.

Thanks for the information. For now I am marking this as closed because if as mentioned HTML body in email does not allow JavaScript to execute in traditional email then we may not need this for now.


Saving Landscapes to Prefabs

When saving landscapes to prefabs, the landscape is invisible when placing the prefab.
I have no idea if it is possible to fix this or not, but understandable if it isn't.

Please describe the problem in more detail. Our component has nothing to do with the landscape. And there are no prefabs in the Unreal Engine.

So sorry, I posted this on the entirely wrong plugin I just realized.


Added a text editor

Added the Adobe Brackets PHP text editor.

travis is confused

can we try again?

Based on https://github.com/brackets-cont/brackets/releases it seems now unmaintained


Respot panel hiding when mouse-out of activation.

Extracted from https://github.com/RhinoLance/ParksNPeaks_Heimdall/issues/3 to track it separately.
From VK2IO: "Also, when attempting to enter a comment, a droplist of earlier comments appears. If one attempts to select an earlier comment by moving the mouse over them the whole respot operation is aborted."

Fix applied in Dev


bump Metaflow version

Doing a minor jump in semver because this will mark the official version from which dynamic cards will be supported

WAIT -- I thought we were first doing a silent release so we could test it. Can we do that this week and THEN do a minor bump.


Added token endpoint implementation

Fixes #67
Implementation Requirements

[x] the Filter should process requests for the (default) path /oauth2/token
[x] authorizationGrantConverter should convert a valid authorization_code Access Token Request to OAuth2AuthorizationCodeAuthenticationToken
[x] the OAuth2AuthorizationCodeAuthenticationToken should be passed to the AuthenticationManager
[x] the AuthenticationManager should be composed of OAuth2AuthorizationCodeAuthenticationProvider
[x] OAuth2AccessTokenAuthenticationToken should be returned from AuthenticationManager
[x] the OAuth2AccessToken should be updated in the in-flight OAuth2Authorization
[x] failure scenarios
[ ] javadoc class and public methods
[ ] Unit tests

@jgrandja Have added the initial changes for early feedback. Tests, javadoc to follow. Also need your help to understand the required failure scenarios to be handled here so that I don't add unnecessary checks and failure handling.

@kratostaine Please review 4.1.3.  Access Token Request to understand all the validations that need to be applied. At minimum, you will need to validate the REQUIRED parameters. However, the some of the parameter values will be validated by the OAuth2AuthorizationCodeAuthenticationProvider #68.
If you are still unsure e on what to validate, please send me the reference in the spec and I could let you know if it should be performed in  OAuth2TokenEndpointFilter or OAuth2AuthorizationCodeAuthenticationProvider.

  grant_type
         REQUIRED.  Value MUST be set to "authorization_code".

   code
         REQUIRED.  The authorization code received from the
         authorization server.

   redirect_uri
         REQUIRED, if the "redirect_uri" parameter was included in the
         authorization request as described in Section 4.1.1, and their
         values MUST be identical.

   client_id
         REQUIRED, if the client is not authenticating with the
         authorization server as described in Section 3.2.1.

@jgrandja the above 4 are the reqd parameters as per the spec. I have done a validation on grant_type already. I also need to do a non-nullable string validation on code, redirect_uri and client_id in the OAuth2TokenEndpointFilter right? Also, how do I validate here the redirect_uri to have value identical to the one as part of the authorization request?

@kratostaine

I also need to do a non-nullable string validation on code, redirect_uri and client_id in the OAuth2TokenEndpointFilter right?

Yes for code and redirect_uri. The (confidential) client is required to authenticate in the authorization_code flow,  so the expectation is that OAuth2ClientAuthenticationToken #72 is available in the SecurityContext.

how do I validate here the redirect_uri to have value identical to the one as part of the authorization request?

The OAuth2AuthorizationCodeAuthenticationProvider #68 is responsible for this validation.

Tests to follow. @jgrandja Please review this so that if there are any changes required, I won't have to rework on the tests again.

@jgrandja Also regarding AuthenticationManager implementation, I have created a custom class implementing it as OAuth2ClientAuthenticationManager. Is that fine or should I be using the default implementation of ProviderManager?

@jgrandja could you please help with reviewing this?

Thank you for all the updates @kratostaine!
Overall, the implementation looked good and complied to spec for the most part.
I did add a polish commit in order to get this merged, as I'm hoping to complete the first iteration of authorization_code grant later this week. I added some missing validation checks and re-organized some of the code.
Please take a look at the changes applied in the polish commit and let me know if you have any questions.
Thank you again and I look forward to another contribution 👍


Support for tracing spring-cloud-gateway 4.x in gateway-4.x-plugin

Add support for spring-cloud-gateway 4.x

[x] Add a unit test to verify that the fix works.
[x] Explain briefly why the bug exists and how to fix it.

why:
spring-cloud-starter-gateway 4.0.0 depends on  spring-boot-starter-webflux 3.0.0
spring-boot-starter-webflux 3.0.0  depends on spring-webflux 6.0.2
spring-webflux-5.x plugin can not trace the request
how:
add support for spring-webflux-6.x diff from 5.x by witnessmethod
upgrade spring-cloud-gateway to 4.x with spring-webflux-6.x diff from 3.x by witnessclass
Add an agent plugin to support spring-cloud-gateway 4.x

[x] Add a test case for the new plugin, refer to the doc

[x] Update the CHANGES log.

Could you confirm this https://github.com/apache/skywalking-java/pull/661#discussion_r1433534466? If the codes don't seem to trigger error, we should not have them in the expected data.


⚠ Account has degraded performance

In 3e074d9, Account (https://account.wrk.com/health) experienced degraded performance:

HTTP code: 200
Response time: 192 ms

Resolved: Account performance has improved in 625d6be.


Add accessibility-alt-text-bot workflow

What
To improve accessibility across GitHub this PR adds the accessibility-alt-text-bot to the codespaces-react template. When others use this template to create a repo, the accessibility-alt-text-bot will already be set up for them.

Is this the right group to tag for a review? @github/codespaces-reviewers


Add cargo benchmarks

As it stands right no I don't actually know how to make benchmarks/good ones. Though I'll learn with time. This one's on the backburner for now

Added in https://github.com/Xanthus58/FileSorterX/commit/6071221f7815fb6c5696cd2abe03949c95debe1b


[feature request] Any way to log/print the path application is hitting server?

As this is far more better mock-json-server than other I found (ability to overwrite POST) and it simpler for things I need I would love to see path that application is trying to get from this server. Any change to add this ?

I added the logs to the console output when you run the server.

thanks


Titles of Public facing dex pages are "Dex"

When logging in, the title of the page the user sees is "dex". It would be cool if this was (maybe just slightly) configurable, like --issuer-logo-url, so we could see "Bananacorp Login"  or just "Bananacorp Authentication" or something in the browser's title bar and in bookmarks.

We already provide configurability of the --issuer-name, so we should just use that value for the page titles.


Blazor WASM security updates for 5.0

Addresses #19503
Internal Review Topics ... these are the focus topics of this PR ...

Standalone with Auth Lib
Standalone with Microsoft Accounts
Standalone with AAD
Standalone with AAD B2C

... there are some additional updates to other topics, but they can be somewhat bypassed given that they aren't receiving their full updates here today. They will be the focus of additional PRs in the coming days.

All of the updates for the standalone guidance.
Part of the updates for the hosted guidance. The AAD and AAD B2C hosted topics will be the focus of a PR tomorrow to finish their 5.0 updates.
Consistency and correctness nits.

Code-fencing "Client" and "Server" when referring to the projects created by the template, which will only be in English.
Only using "clear" and "selected" when referring to check boxes per the MS style guidelines.

You'll see that I've temporarily left the NOTE on If the Azure portal provides the scope URI for the app and the app throws an unhandled exception when it receives a 401 Unauthorized response from the API, .... Let's leave that for now. I need to work on that a bit more before I determine if we can safely version it only for 3.x. I'll probably have an answer on it for tomorrow's PR.
I guessed correctly on issue Questions 1-3, so I didn't need to make changes. I already had some general text for DefaultAccessTokenScopes with AdditionalScopesToConsent added on this PR, but we still don't have anything specific yet. If you want to float some content ... a sentence or two ... or more ... on review, let's do that. Otherwise, we can go with this coverage now, and I can ask for further feedback later on it.
If possible, I'd like to get this merged by EOD so that I'm unblocked to pick up with the AAD-based hosted topics in the morning. Idk if we can pull it off, but I hope we can try. Sorry for the rush! 🏃🏃🏃🏃🏃🏃 I don't plan on pinging for additional comments, so I yield to you if you think we should.

@captainsafia ... Ok ... thx for that ... I wish I would've drilled down a bit more this morning.
We now have -AAD (for AAD) and -nonAAD (for MS Accounts and B2C) INCLUDES for both standalone and hosted default scopes.

the config shouldn't be needed for hosted apps

I thought that the Client app of a hosted solution would be configured like a standalone app ... at least to avoid this new error for an app that doesn't specify default scopes. That's a wrong guess? I would find out the hard way in the morning anyway ... I'll be working with the hosted scenarios tomorrow.

@captainsafia ... I'll go ahead and merge now so that I can pick up with the next round of updates. If there's more to update from this PR, I'll place the changes on the next one.


Feature request: add Logo in EPS Output

Hello,
Would it be possible to add the support of a logo with the writers "Eps" or "Svg"?
I want to make a PDF with "SwissQR Invoice" and the print quality with the PNG is by far not perfect.
With the svg we get a perfect quality, but we can not add a logo.
Is this planned?
Fabian

SVG Logo is possible so I changed the title.

Hey first of all, pretty good tool works pretty fine and smooth. But i have a little question. About the .eps files are you still working on the implementations of the logos in the eps? On the Tool im working right now version 3.4.0 is installed just for my knowledge if i simply have to update the tool or if i have to find an workaround to implement logos in an eps.
Greeting Paul

Hi @libertey currently I have no intention (because of time, priorities) on adding logo support in the EPS writer so unfortunately you would have to look for a workaround. If however you find something useful you can always let me know.

@libertey can you provide the code of your workaround?


New Timeline Applied to Widgets

DEPENDS UPON https://github.com/CiscoDevNet/cjaas-common-components/pull/30
Implements the major overhaul of the Timeline and related components for more concentrated control and consistent application. Delivers new features requested in JAS 236 and 237
https://cjaas.atlassian.net/browse/JAS-237?atlOrigin=eyJpIjoiMTI1ZTI1MjI4OGI4NDM2MWFjMzM3ZTY3NDVlMmQ0MmIiLCJwIjoiaiJ9
https://cjaas.atlassian.net/browse/JAS-236?atlOrigin=eyJpIjoiMWYyMWIwYThkM2Y2NGE1Mjg4ODUwYzE4NjYzNGY5NDQiLCJwIjoiaiJ9

This PR was replaced by broader changes made in #34


[Easy] Add 13 missing tokens

Execute on Network Network.MAINNET
Fetching V1 missing tokens for Network.MAINNET from https://dune.com/queries/1317323
2022-12-16 12:28:38,976 INFO dune_client.client waiting for query execution 01GMDB30AD8SVR94KXVTHGK6K8 to complete: ExecutionState.EXECUTING
Fetching V2 missing tokens for Network.MAINNET from https://dune.com/queries/1403073?Blockchain=ethereum
2022-12-16 12:28:45,040 INFO dune_client.client waiting for query execution 01GMDB360TQBZ3CHPNP85DTD9W to complete: ExecutionState.EXECUTING
Found 13 missing tokens on V1 and 13 on V2. Fetching token details...
V1 results:
\x04C17b9D3b29A78F7Bd062a57CF44FC633e71f85     IMPT    18
\x250855469B1EaFADC4ecAc66C8F390554ec4e104     SENSHI  18
\x351cAa9045D65107b9d311D922D15887cfd634E4     ARW     18
\x402F878BDd1f5C66FdAF0fabaBcF74741B68ac36     sdFXS   18
\x444444444444C1a66F394025Ac839A535246FCc8     GENI    9
\x4EdcB2B46377530Bc18BB4D2c7Fe46a992c73e10     cbETH-wstETH-BPT        18
\x836A808d4828586A69364065A1e064609F5078c7     pETH    18
\x8bb08042c06FA0Fc26cd2474C5F0C03a1056Ad2F     CPI     18
\x8e0E57DCb1ce8d9091dF38ec1BfC3b224529754A     CAH     18
\xBb24C7a8e89eDa9f22842644df8D0524871257e5     LL      18
\xC1f33e0cf7e40a67375007104B929E49a581bafE     SPOT    9
\xc5F3D11580c41cD07104e9AF154Fc6428bb93c73     yvBalancer-BoostedAaveUSD       18
\xf33683d0D690CCdBbF63A54b8d6709ff7e6cf987     TFI     18
V2 results:
('0x04c17b9d3b29a78f7bd062a57cf44fc633e71f85', 'IMPT', 18),
('0x250855469b1eafadc4ecac66c8f390554ec4e104', 'SENSHI', 18),
('0x351caa9045d65107b9d311d922d15887cfd634e4', 'ARW', 18),
('0x402f878bdd1f5c66fdaf0fababcf74741b68ac36', 'sdFXS', 18),
('0x444444444444c1a66f394025ac839a535246fcc8', 'GENI', 9),
('0x4edcb2b46377530bc18bb4d2c7fe46a992c73e10', 'cbETH-wstETH-BPT', 18),
('0x836a808d4828586a69364065a1e064609f5078c7', 'pETH', 18),
('0x8bb08042c06fa0fc26cd2474c5f0c03a1056ad2f', 'CPI', 18),
('0x8e0e57dcb1ce8d9091df38ec1bfc3b224529754a', 'CAH', 18),
('0xbb24c7a8e89eda9f22842644df8d0524871257e5', 'LL', 18),
('0xc1f33e0cf7e40a67375007104b929e49a581bafe', 'SPOT', 9),
('0xc5f3d11580c41cd07104e9af154fc6428bb93c73', 'yvBalancer-BoostedAaveUSD', 18),
('0xf33683d0d690ccdbbf63a54b8d6709ff7e6cf987', 'TFI', 18),

This is just for the V1 tokens.

Here's the V2 update PR: https://github.com/duneanalytics/spellbook/pull/2338
I also think abandoning v1 token updates is okay.

PR has been written to DB for v1. Still waiting for updated GitHub permission on this repo to be able to merge it 😅

Looks like I can merge it... would you like me to?


Exporting Frame-stepped project in YOLO Format

I have a video project which has been annotated using a frame step of 5. Upon export in the YOLO format, the annotations are wrong. All ###.jpg files have ###.txt files that are completely empty. In addition, many "frame_#####.txt" files are also generated within the export data folder and while they do have annotation data, they do not correctly correspond to the same ###.jpg files.

@zhiltsov-max , could you please look at the issue?


Unable to Start mnist.py

Hello,
I tried to run the mnist.py 'Start without Debugging', but I get an error:
File "samples-for-ai-master\examples\tensorflow\MNIST\mnist.py", line 37, in <module>     import tensorflow as tf   File "Python\Python36\lib\site-packages\tensorflow\__init__.py", line 22, in <module>     from tensorflow.python import pywrap_tensorflow  # pylint: disable=unused-import   File "Python\Python36\lib\site-packages\tensorflow\python\__init__.py", line 49, in <module>     from tensorflow.python import pywrap_tensorflow   File "Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in <module>     from tensorflow.python.pywrap_tensorflow_internal import *   File "Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 121, in <module>     TFE_ContextOptionsSetServerDef = _pywrap_tensorflow_internal.TFE_ContextOptionsSetServerDef AttributeError: module 'tensorflow.python._pywrap_tensorflow_internal' has no attribute 'TFE_ContextOptionsSetServerDef'
I think that this is caused by the fact that I am running Python 3.6. Any suggestion on how to fix this issue?

What version of Tensorflow are you using? Did you install it via Microsoft Visual Studio Tools for AI?
python3 -c 'import tensorflow as tf; print(tf.__version__)'
It should  work with python 3.6 and it might be related to this

Hello,
I am using Tensorflow 1.9.0. It got installed when I added the Python Development Environment to visual studio, and Microsoft Visual Studio Tools for AI.
Prior to installing these to Visual studio, I had python 3.6 installed locally, and the package also. Could this be the problem? Do I need to remove all Python related from Visual Studio, and the local ones (Python 3.6 and Anaconda), and reinstall them in Visual Studio only?

Hello,
Good news. I removed all instances of Python from my PC (Visual studio and standalone), and installed only the Visual Studio related. I managed to make the project work.
In case anyone else has this or a similar problem, they could try the same approach I did.


feat: error cases

Closes #555 #425
As a user
Given I have no internet
Then I do not want to see an error page
And I want to see a warning

merged into #580


I got "Invalid left-hand side in assignment" when i used v-model

Vue version
3.2.37
Link to minimal reproduction
https://github.com/wulinsheng123/regular-view
Steps to reproduce
run project,and enter in input
What is expected?
i can use v-model
What is actually happening?
Uncaught ReferenceError: Invalid left-hand side in assignment
System Info
mac, last version Chrome ,vite 3.0.3

Any additional comments?
No response

your repo works fine no the vercel deployment and also when copied to the SFC playground. The screenshots shows an error from a component that can't be found in the provided reproductio. (HeaderTool.vue)
Can't reproduce the problem.

your repo works fine no the vercel deployment and also when copied to the SFC playground. The screenshots shows an error from a component that can't be found in the provided reproduction. (HeaderTool.vue)
Can't reproduce the problem.

I found this problem that not happen in production.
I think  it seems different between  dev and build .
mainly it's happen occasionally


Thread-safe scratch allocation

According to TODOs left in the commit log(s), the scratch memory allocation is not thread-safe. Although it has been designed to be thread-safe, the actual implementation is lagging, and preferred to be feature-complete. This issue records the remaining work needed for thread-safety.

Fixed in master.


Support for Cyberpunk Red System

Description
Cyberpunk Red is a system that allows to play Cyberpunk in FoundryVTT.
Item Macro would allow player and GMs to easily use macros on items directly.
Here is the FoundryVTT page : https://foundryvtt.com/packages/cyberpunk-red-core
Here is the Gitlab page : https://gitlab.com/JasonAlanTerry/fvtt-cyberpunk-red-core
Again this is only a suggestion, as always thank you for your hard work and wish you a good day.

I am going to push this to v9.
I asked around a bit and no one seemed able to help with the basic execution or where item-macro could "fit" in this system as it is written at the moment.
Until I get guidance I wont be able to do much.


Undocumented difference to paper

Hi and thanks for this easy-to-use implementation :)
I was trying to reproduce the original paper's results with your implementation and found the following differences. For the convolution blocks, the original paper states:
In these tables “C × H × W conv” denotes a convolutional layer with C filters size H × W which is immediately followed by spatial batch normalization [1] and a ReLU nonlinearity."
It seems that your implementation uses
h = self.b1(F.elu(self.c1(x)), test=test)
whereas the paper would suggest
h = F.relu(self.b1(self.c1(x), test=test))
Also, the paper adds a 40px padding before the first convolution layer, and then doesn't have any padding for the convolutions and residuals. That way, they implicitly cut off the borders of the generated image, thus removing border artifacts.
My suggestion would be to add these differences to the information in your readme.
Cheers,
Hajo

@fxtentacle
Thanks for your suggestion.
I just want to know, does this suggestion  can remove the 'dots' and noise? I am eagerly solving this problem.Have you did some experiments?
Thanks for all my love.

In my testing, the early normalization reduces noisy overexposure a bit, but it didn't help with the dots.
My working guess is that the dots are either the result of interlacing between the convolution stride and kernel size, or caused by having too little variance penalty during training. But so far, I haven't found a solution yet. I'll report back when (or rather if) I figure it out.

@fxtentacle
Thanks very much.
I am training the model with your suggestion now and hoping it can reduce noisy overexposure.
I am looking forward for your better solution.
Thanks really.

@fxtentacle Thank you for your suggestion. You are right. I didn't notice my mistake of the late batch norm. I'm thinking whether to change code since it breaks backward compatibility again.

I agree that the normalization order is probably not important enough to warrant breaking old models. But my hope is that we'll also be able to figure out the dot issue and I think that one will need re-training anyway.
I ran some tests with size 3 convolution kernels (like in the paper) but that doesn't affect the dots much.
Training with extreme images (blank/stripes) for the style shows that the dots are dependent on the style, so my current working guess is that the dots have somehow been trained into the models.
I'm now running some tests on my cluster where I use various edge detection kernels as regularization methods. I'll evaluate around epoch 1 which should be ready in 2 hours.
BTW I have to say that after working on business apps for a while, I really enjoy the immediate feedback that you get with image algorithms :)

@fxtentacle please see also https://github.com/yusuketomoto/chainer-fast-neuralstyle/issues/68 where dot issue is discussed.

Another difference to the paper seems to be that they add reflection padding before starting the processing chain and then crop the image before VGG evaluation. That way, the border artifacts introduced by padding are not included in the loss calculation.

I finally figured out where the border artifacts come from: The original paper also uses reflection padding inside the residue blocks, this implementation uses zero-padding. As such, the residue blocks in this implementation will always introduce 0-values around the border, which leads to the artifacts. Now if only Chainer had reflection padding ...

@fxtentacle yes, you are right. I added quick-fix for dot noise/border artifact problem. https://github.com/yusuketomoto/chainer-fast-neuralstyle/commit/431af844e6c984a7b42c2ea7b9a3b7130555d1bb


Add more info to app sleeping

Adds more information to the App Sleeping reference page. Specially, adding scenarios that will keep the app from sleeping and make it clearer that private network traffic will prevent the app from sleeping,
Fix a smooth scroll bug where links to different pages would smooth scroll to an element on the current page if the link had a hash for an element that existed on the current page, we now check if the link's path is the same as the windows path before deciding to smooth scroll or treat it as a regular link.

LGTM!


cards animated

I deleted the old forked repo, made a new one, did all the changes, checked locally a few times and everything seems fine from my side.

@SurajPratap10 could you please merge my pr first

@SurajPratap10 could you please merge my pr first

Will check it in the evening

It's breaking the website @laibaahsan27


Badger2040: system_speed call, plus performance improvements

I've added a badger2040.system_speed() call to allow the user to easily adjust the clock speed to 5 settings, from 3MHz to 250MHz in sensible steps, applying under/over voltage as appropriate.  Lower clock frequencies are not available when USB is connected, but can be used to save power when on battery.
Clearing the screen and drawing large rectangles were relatively inefficient, so I now do these by editing the framebuffer directly.  Rectangles honour the odd behaviour of being affected by the current thickness setting, to preserve backwards compatibility.

As discussed, will add Micropython UART reinitialization after changing the clock speed, in case anyone is using hardware UART.

Working beautifully, thank you!


Definition update for CL_0000178

: A Leydig cell is a
testosterone-secreting cell in the interstitial area, between the
seminiferous tubules, in the testis.
Please change to
A Leydig cell is a cell capable of secreting testosterone in the interstitial area, between the seminiferous tubules, in the testis.

Zebrafish Ledig cells secrete 11-Keto-Testosterone https://en.wikibooks.org/wiki/The_Zebrafish_in_Toxicology/Testis_location "Leydig cells are the source of androgens. In teleosts, they produce 11-ketotestosterone under complex regulation. Androgen production in teleosts is stimulated by the pituitary derived gonadotropin, and gonadotropin production is partly under feedback control of plasma androgen levels"  cites PMID:    7981031
11-Keto-testosterone https://www.ebi.ac.uk/chebi/searchId.do?chebiId=CHEBI:34133
Right now testosterone secretion in GO references https://www.ebi.ac.uk/chebi/chebiOntology.do?chebiId=CHEBI:17347
We might need some changes in GO too and maybe Changes in the CHEBI hierarchy to make 11-Keto-testosterone a steroid hormone .

WARNING: This issue has been automatically closed because it has not been updated in more than 3 years. Please re-open it if you still need this to be addressed – we are now getting some resources to deal with such issues.


Lower Dart SDK back to 1.24.0-dev.3.0 to unbreak the build

https://github.com/flutter/flutter/issues/10611

I think we should probably do this anyway, because the failure mode changed across this roll, going from one or two failures that time out, to dozens of failures with a different error message.

The logs for the failure in this PR (https://travis-ci.org/flutter/flutter/jobs/242126793) are quite interesting.

⏩ RUNNING: cd packages/flutter_tools; ../../bin/cache/dart-sdk/bin/pub run test -rexpanded
00:00 +0: test/base/context_test.dart: AppContext error
00:00 +1: test/base/logger_test.dart: AppContext error
00:00 +2: test/base/logger_test.dart: AppContext error
00:00 +3: test/base/logger_test.dart: AppContext error
00:00 +4: test/base/logger_test.dart: AppContext error
00:00 +5: test/base/logger_test.dart: AppContext error
00:01 +6: test/base/logger_test.dart: AppContext error
00:01 +7: test/base/logger_test.dart: AppContext error
00:01 +8: loading test/analytics_test.dart
00:02 +8: test/base/process_test.dart: shutdownHooks runInExpectedOrder
00:03 +9: loading test/analytics_test.dart
00:28 +9: test/config_test.dart: config get set value
00:29 +10: loading test/analytics_test.dart
00:29 +10: test/config_test.dart: config removeValue
00:29 +11: loading test/analytics_test.dart
00:47 +11: test/application_package_test.dart: ApkManifestData parse sdk
00:53 +12: test/application_package_test.dart: ApkManifestData parse sdk
00:55 +13: test/application_package_test.dart: ApkManifestData parse sdk
00:55 +14: test/application_package_test.dart: ApkManifestData parse sdk
00:55 +15: test/application_package_test.dart: ApkManifestData parse sdk
00:57 +16: test/commands/format_test.dart: format a file
00:57 +17: test/commands/format_test.dart: format a file
00:59 +18: test/commands/format_test.dart: format a file
00:59 +19: test/commands/format_test.dart: format a file
00:59 +20: test/commands/format_test.dart: format a file
00:59 +21: test/commands/format_test.dart: format a file
01:00 +22: test/commands/format_test.dart: format a file
01:00 +23: test/commands/format_test.dart: format a file
01:00 +24: test/commands/format_test.dart: format a file
01:00 +25: test/commands/format_test.dart: format a file
01:00 +26: test/commands/format_test.dart: format a file
01:01 +27: test/commands/format_test.dart: format a file
01:01 +28: test/commands/format_test.dart: format a file
01:01 +29: test/commands/format_test.dart: format a file
01:01 +30: test/commands/format_test.dart: format a file
01:01 +31: test/commands/format_test.dart: format a file
01:01 +32: test/commands/format_test.dart: format a file
01:01 +33: test/commands/format_test.dart: format a file
01:02 +34: test/commands/format_test.dart: format a file
01:03 +35: test/commands/format_test.dart: format a file
01:03 +36: test/commands/format_test.dart: format a file
01:03 +37: test/commands/format_test.dart: format a file
01:03 +38: test/commands/format_test.dart: format a file
01:03 +39: test/commands/format_test.dart: format a file
01:03 +40: test/commands/format_test.dart: format a file
01:04 +41: test/commands/format_test.dart: format a file
01:05 +42: test/commands/format_test.dart: format a file
01:05 +43: test/commands/format_test.dart: format a file
01:06 +44: test/commands/format_test.dart: format a file
01:06 +45: test/commands/format_test.dart: format a file
01:08 +46: test/commands/format_test.dart: format a file
01:08 +47: test/commands/format_test.dart: format a file
01:14 +48: test/commands/format_test.dart: format a file
01:14 +49: test/commands/format_test.dart: format a file
01:15 +50: test/commands/format_test.dart: format a file
01:17 +51: test/commands/format_test.dart: format a file
01:17 +52: test/commands/format_test.dart: format a file
01:18 +53: test/commands/format_test.dart: format a file
01:19 +54: test/commands/format_test.dart: format a file
01:19 +55: test/commands/format_test.dart: format a file
01:22 +56: test/commands/format_test.dart: format a file
01:22 +57: test/commands/format_test.dart: format a file
01:24 +58: test/commands/format_test.dart: format a file
01:25 +59: test/commands/format_test.dart: format a file
01:27 +60: test/commands/format_test.dart: format a file
01:27 +61: test/commands/format_test.dart: format a file
01:28 +62: test/commands/format_test.dart: format a file
01:28 +63: test/commands/format_test.dart: format a file
01:29 +64: test/commands/format_test.dart: format a file
01:29 +65: test/commands/format_test.dart: format a file
01:29 +66: test/commands/format_test.dart: format a file
01:29 +67: test/commands/format_test.dart: format a file
01:30 +68: test/commands/format_test.dart: format a file
01:30 +69: test/commands/format_test.dart: format a file
01:31 +70: test/commands/format_test.dart: format a file
01:31 +71: test/commands/format_test.dart: format a file
01:31 +72: test/commands/format_test.dart: format a file
01:32 +73: test/commands/format_test.dart: format a file
01:32 +74: test/commands/format_test.dart: format a file
01:33 +75: test/commands/format_test.dart: format a file
01:33 +76: test/commands/format_test.dart: format a file
01:33 +77: test/commands/format_test.dart: format a file
01:33 +78: test/commands/format_test.dart: format a file
01:34 +79: test/commands/format_test.dart: format a file
01:34 +80: test/commands/format_test.dart: format a file
01:34 +81: test/commands/format_test.dart: format a file
01:36 +82: test/commands/format_test.dart: format a file
01:37 +82 -1: test/commands/packages_test.dart: packages get/upgrade get
01:39 +83 -1: test/commands/packages_test.dart: packages get/upgrade get
01:41 +83 -2: test/analytics_test.dart: analytics doesn't send when disabled
01:44 +83 -2: test/commands/format_test.dart: format a file
  TimeoutException after 0:00:30.000000: Test timed out after 30 seconds.
  dart:isolate  _RawReceivePortImpl._handleMessage

01:45 +84 -2: test/analytics_test.dart: analytics doesn't send when disabled
01:45 +85 -2: test/analytics_test.dart: analytics doesn't send when disabled
01:46 +86 -2: test/analytics_test.dart: analytics doesn't send when disabled
01:47 +86 -3: test/analytics_test.dart: analytics doesn't send when disabled
01:48 +87 -3: test/analytics_test.dart: analytics doesn't send when disabled
01:48 +87 -3: test/commands/packages_test.dart: packages get/upgrade get
  TimeoutException after 0:00:30.000000: Test timed out after 30 seconds.
  dart:isolate  _RawReceivePortImpl._handleMessage

01:48 +88 -3: test/analytics_test.dart: analytics doesn't send when disabled
01:49 +89 -3: test/analytics_test.dart: analytics doesn't send when disabled
01:49 +90 -3: test/analytics_test.dart: analytics doesn't send when disabled
01:50 +91 -3: test/analytics_test.dart: analytics doesn't send when disabled
01:51 +91 -4: test/analytics_test.dart: analytics doesn't send when disabled
01:51 +91 -4: test/commands/analyze_duplicate_names_test.dart: analyze flutter analyze with two files with the same name
  TimeoutException after 0:00:30.000000: Test timed out after 30 seconds.
  dart:isolate  _RawReceivePortImpl._handleMessage

01:51 +92 -4: test/analytics_test.dart: analytics doesn't send when disabled
01:52 +93 -4: test/analytics_test.dart: analytics doesn't send when disabled
01:52 +94 -4: test/analytics_test.dart: analytics doesn't send when disabled
01:52 +95 -4: test/analytics_test.dart: analytics doesn't send when disabled
01:52 +96 -4: test/analytics_test.dart: analytics doesn't send when disabled
01:52 +97 -4: test/analytics_test.dart: analytics doesn't send when disabled
01:52 +98 -4: test/analytics_test.dart: analytics doesn't send when disabled
01:52 +99 -4: test/analytics_test.dart: analytics doesn't send when disabled
01:54 +99 -4: test/commands/create_test.dart: create project
  TimeoutException after 0:00:30.000000: Test timed out after 30 seconds.
  dart:isolate  _RawReceivePortImpl._handleMessage

01:55 +99 -4: test/commands/packages_test.dart: packages get/upgrade get
  ProcessException: No such file or directory
    Command: /home/travis/build/flutter/flutter/bin/cache/dart-sdk/bin/pub --verbosity=warning get --no-precompile
  dart:io                                                              Process.start
  package:process/src/interface/local_process_manager.dart 42:20       LocalProcessManager.start
  package:flutter_tools/src/base/process.dart 107:25                   runCommand
  package:flutter_tools/src/base/process.dart 125:33                   runCommandAndStreamOutput
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/base/process.dart 124:10                   runCommandAndStreamOutput
  package:flutter_tools/src/dart/pub.dart 79:26                        pub
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/dart/pub.dart 77:10                        pub
  package:flutter_tools/src/dart/pub.dart 58:13                        pubGet
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/dart/pub.dart 36:10                        pubGet
  package:flutter_tools/src/commands/packages.dart 77:11               PackagesGetCommand.runCommand
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/commands/packages.dart 63:35               PackagesGetCommand.runCommand
  package:flutter_tools/src/runner/flutter_command.dart 210:18         FlutterCommand.verifyThenRunCommand
  ===== asynchronous gap ===========================
  dart:async                                                           _asyncThenWrapperHelper
  package:flutter_tools/src/runner/flutter_command.dart 196:61         FlutterCommand.verifyThenRunCommand
  package:flutter_tools/src/runner/flutter_command.dart 156:29         FlutterCommand.run
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/runner/flutter_command.dart 148:28         FlutterCommand.run
  package:args/command_runner.dart 194:27                              CommandRunner.runCommand
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:args/command_runner.dart 142:58                              CommandRunner.runCommand
  package:flutter_tools/src/runner/flutter_command_runner.dart 277:27  FlutterCommandRunner.runCommand
  ===== asynchronous gap ===========================
  dart:async                                                           _asyncThenWrapperHelper
  package:flutter_tools/src/runner/flutter_command_runner.dart 165:59  FlutterCommandRunner.runCommand
  package:args/command_runner.dart 109:29                              CommandRunner.run.<fn>
  dart:async                                                           new Future.sync
  package:args/command_runner.dart 109:11                              CommandRunner.run
  package:flutter_tools/src/runner/flutter_command_runner.dart 161:21  FlutterCommandRunner.run
  test/commands/packages_test.dart 42:20                               main.<fn>.runCommand
  ===== asynchronous gap ===========================
  dart:async                                                           _asyncThenWrapperHelper
  test/commands/packages_test.dart 31:73                               main.<fn>.runCommand
  test/commands/packages_test.dart 53:50                               main.<fn>.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  test/commands/packages_test.dart 52:38                               main.<fn>.<fn>
  test/src/context.dart 99:32                                          testUsingContext.<fn>.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  test/src/context.dart 88:51                                          testUsingContext.<fn>.<fn>
  package:flutter_tools/src/base/context.dart 76:26                    AppContext._run
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/base/context.dart 72:48                    AppContext._run
  package:flutter_tools/src/base/context.dart 66:13                    AppContext.runInZone.<fn>
  dart:async                                                           runZoned
  package:flutter_tools/src/base/context.dart 65:12                    AppContext.runInZone
  test/src/context.dart 88:32                                          testUsingContext.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  test/src/context.dart 71:30                                          testUsingContext.<fn>

01:55 +100 -4: test/bug_report_test.dart: --bug-report generates valid zip file
01:57 +100 -5: test/bug_report_test.dart: --bug-report generates valid zip file
01:58 +101 -5: test/bug_report_test.dart: --bug-report generates valid zip file
02:00 +101 -5: test/commands/analyze_once_test.dart: analyze once flutter create
  TimeoutException after 0:00:30.000000: Test timed out after 30 seconds.
  dart:isolate  _RawReceivePortImpl._handleMessage

02:01 +101 -6: test/commands/run_test.dart: run fails when target not found
02:01 +101 -6: test/commands/create_test.dart: create project
  ProcessException: No such file or directory
    Command: /home/travis/build/flutter/flutter/bin/cache/dart-sdk/bin/pub --verbosity=warning get --no-precompile
  dart:io                                                              Process.start
  package:process/src/interface/local_process_manager.dart 42:20       LocalProcessManager.start
  package:flutter_tools/src/base/process.dart 107:25                   runCommand
  package:flutter_tools/src/base/process.dart 125:33                   runCommandAndStreamOutput
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/base/process.dart 124:10                   runCommandAndStreamOutput
  package:flutter_tools/src/dart/pub.dart 79:26                        pub
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/dart/pub.dart 77:10                        pub
  package:flutter_tools/src/dart/pub.dart 58:13                        pubGet
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/dart/pub.dart 36:10                        pubGet
  package:flutter_tools/src/commands/create.dart 186:13                CreateCommand.runCommand
  ===== asynchronous gap ===========================
  dart:async                                                           _asyncThenWrapperHelper
  package:flutter_tools/src/commands/create.dart 80:35                 CreateCommand.runCommand
  package:flutter_tools/src/runner/flutter_command.dart 210:18         FlutterCommand.verifyThenRunCommand
  ===== asynchronous gap ===========================
  dart:async                                                           _asyncThenWrapperHelper
  package:flutter_tools/src/runner/flutter_command.dart 196:61         FlutterCommand.verifyThenRunCommand
  package:flutter_tools/src/runner/flutter_command.dart 156:29         FlutterCommand.run
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/runner/flutter_command.dart 148:28         FlutterCommand.run
  package:args/command_runner.dart 194:27                              CommandRunner.runCommand
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:args/command_runner.dart 142:58                              CommandRunner.runCommand
  package:flutter_tools/src/runner/flutter_command_runner.dart 277:27  FlutterCommandRunner.runCommand
  ===== asynchronous gap ===========================
  dart:async                                                           _asyncThenWrapperHelper
  package:flutter_tools/src/runner/flutter_command_runner.dart 165:59  FlutterCommandRunner.runCommand
  package:args/command_runner.dart 109:29                              CommandRunner.run.<fn>
  dart:async                                                           new Future.sync
  package:args/command_runner.dart 109:11                              CommandRunner.run
  package:flutter_tools/src/runner/flutter_command_runner.dart 161:21  FlutterCommandRunner.run
  test/commands/create_test.dart 242:16                                _createAndAnalyzeProject
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  test/commands/create_test.dart 235:62                                _createAndAnalyzeProject
  test/commands/create_test.dart 39:14                                 main.<fn>.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  test/commands/create_test.dart 38:42                                 main.<fn>.<fn>
  test/src/context.dart 99:32                                          testUsingContext.<fn>.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  test/src/context.dart 88:51                                          testUsingContext.<fn>.<fn>
  package:flutter_tools/src/base/context.dart 76:26                    AppContext._run
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/base/context.dart 72:48                    AppContext._run
  package:flutter_tools/src/base/context.dart 66:13                    AppContext.runInZone.<fn>
  dart:async                                                           runZoned
  package:flutter_tools/src/base/context.dart 65:12                    AppContext.runInZone
  test/src/context.dart 88:32                                          testUsingContext.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  test/src/context.dart 71:30                                          testUsingContext.<fn>

02:02 +102 -6: test/commands/run_test.dart: run fails when target not found
02:02 +103 -6: test/commands/test_test.dart: test Exception handling in test harness
02:04 +103 -6: test/bug_report_test.dart: --bug-report generates valid zip file
  TimeoutException after 0:00:30.000000: Test timed out after 30 seconds.
  dart:isolate  _RawReceivePortImpl._handleMessage

02:05 +104 -6: test/commands/test_test.dart: test Exception handling in test harness
02:05 +105 -6: test/commands/test_test.dart: test Exception handling in test harness
02:05 +106 -6: test/commands/test_test.dart: test Exception handling in test harness
02:09 +107 -6: test/commands/test_test.dart: test Exception handling in test harness
02:10 +107 -7: test/commands/test_test.dart: test Exception handling in test harness
02:10 +108 -7: test/commands/test_test.dart: test Exception handling in test harness
02:11 +108 -7: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory
  Exception: (Ran in 6.5s)
  package:flutter_tools/src/base/common.dart 29:3                      throwToolExit
  package:flutter_tools/src/commands/analyze_once.dart 127:9           AnalyzeOnce.analyze
  package:flutter_tools/src/commands/analyze.dart 62:104               AnalyzeCommand.runCommand
  package:flutter_tools/src/runner/flutter_command.dart 210:18         FlutterCommand.verifyThenRunCommand
  package:flutter_tools/src/runner/flutter_command.dart 156:29         FlutterCommand.run
  package:args/command_runner.dart 194:27                              CommandRunner.runCommand
  package:flutter_tools/src/runner/flutter_command_runner.dart 277:27  FlutterCommandRunner.runCommand
  package:args/command_runner.dart 109:29                              CommandRunner.run.<fn>
  dart:async                                                           new Future.sync
  package:args/command_runner.dart 109:11                              CommandRunner.run
  package:flutter_tools/src/runner/flutter_command_runner.dart 161:21  FlutterCommandRunner.run
  test/commands/analyze_once_test.dart 213:44                          runCommand
  test/commands/analyze_once_test.dart 54:13                           main.<fn>.<fn>
  test/src/context.dart 99:32                                          testUsingContext.<fn>.<fn>
  package:flutter_tools/src/base/context.dart 76:26                    AppContext._run
  package:flutter_tools/src/base/context.dart 66:13                    AppContext.runInZone.<fn>
  dart:async                                                           runZoned
  package:flutter_tools/src/base/context.dart 65:12                    AppContext.runInZone
  test/src/context.dart 88:32                                          testUsingContext.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                           _Completer.completeError
  package:flutter_tools/src/commands/analyze_once.dart 251:3           AnalyzeOnce.analyze
  ===== asynchronous gap ===========================
  dart:async                                                           _asyncThenWrapperHelper
  package:flutter_tools/src/commands/analyze_once.dart 38:32           AnalyzeOnce.analyze
  package:flutter_tools/src/commands/analyze.dart 62:104               AnalyzeCommand.runCommand
  package:flutter_tools/src/runner/flutter_command.dart 210:18         FlutterCommand.verifyThenRunCommand
  ===== asynchronous gap ===========================
  dart:async                                                           _asyncThenWrapperHelper
  package:flutter_tools/src/runner/flutter_command.dart 196:61         FlutterCommand.verifyThenRunCommand
  package:flutter_tools/src/runner/flutter_command.dart 156:29         FlutterCommand.run
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/runner/flutter_command.dart 148:28         FlutterCommand.run
  package:args/command_runner.dart 194:27                              CommandRunner.runCommand
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:args/command_runner.dart 142:58                              CommandRunner.runCommand
  package:flutter_tools/src/runner/flutter_command_runner.dart 277:27  FlutterCommandRunner.runCommand
  ===== asynchronous gap ===========================
  dart:async                                                           _asyncThenWrapperHelper
  package:flutter_tools/src/runner/flutter_command_runner.dart 165:59  FlutterCommandRunner.runCommand
  package:args/command_runner.dart 109:29                              CommandRunner.run.<fn>
  dart:async                                                           new Future.sync
  package:args/command_runner.dart 109:11                              CommandRunner.run
  package:flutter_tools/src/runner/flutter_command_runner.dart 161:21  FlutterCommandRunner.run
  test/commands/analyze_once_test.dart 213:44                          runCommand
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  test/commands/analyze_once_test.dart 210:10                          runCommand
  test/commands/analyze_once_test.dart 54:13                           main.<fn>.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  test/commands/analyze_once_test.dart 53:68                           main.<fn>.<fn>
  test/src/context.dart 99:32                                          testUsingContext.<fn>.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  test/src/context.dart 88:51                                          testUsingContext.<fn>.<fn>
  package:flutter_tools/src/base/context.dart 76:26                    AppContext._run
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  package:flutter_tools/src/base/context.dart 72:48                    AppContext._run
  package:flutter_tools/src/base/context.dart 66:13                    AppContext.runInZone.<fn>
  dart:async                                                           runZoned
  package:flutter_tools/src/base/context.dart 65:12                    AppContext.runInZone
  test/src/context.dart 88:32                                          testUsingContext.<fn>
  ===== asynchronous gap ===========================
  dart:async                                                           new Future.microtask
  test/src/context.dart 71:30                                          testUsingContext.<fn>

02:12 +109 -7: test/commands/test_test.dart: test Exception handling in test harness
02:13 +110 -7: test/commands/test_test.dart: test Exception handling in test harness
02:13 +111 -7: test/commands/test_test.dart: test Exception handling in test harness
02:14 +112 -7: test/commands/create_test.dart: create kotlin/swift project
02:19 +113 -7: test/commands/create_test.dart: create kotlin/swift project
02:19 +114 -7: test/commands/create_test.dart: create kotlin/swift project
02:19 +115 -7: test/commands/create_test.dart: create kotlin/swift project
02:19 +116 -7: test/commands/create_test.dart: create kotlin/swift project
02:20 +117 -7: test/commands/create_test.dart: create kotlin/swift project
02:20 +118 -7: test/commands/create_test.dart: create kotlin/swift project
02:29 +119 -7: test/commands/create_test.dart: create kotlin/swift project
02:34 +120 -7: test/commands/create_test.dart: create kotlin/swift project
02:38 +121 -7: test/commands/create_test.dart: create kotlin/swift project
02:39 +122 -7: test/commands/create_test.dart: create kotlin/swift project
02:40 +123 -7: test/commands/create_test.dart: create kotlin/swift project
02:40 +124 -7: test/commands/create_test.dart: create kotlin/swift project
02:41 +125 -7: test/commands/create_test.dart: create kotlin/swift project
02:44 +126 -7: test/commands/create_test.dart: create kotlin/swift project
02:44 +126 -8: test/commands/create_test.dart: create kotlin/swift project
02:45 +127 -8: test/commands/create_test.dart: create kotlin/swift project
02:46 +128 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:46 +129 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:47 +130 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:47 +130 -8: test/commands/test_test.dart: test TestAsyncUtils guarded function test
  TimeoutException after 0:00:30.000000: Test timed out after 30 seconds.
  dart:isolate  _RawReceivePortImpl._handleMessage

02:49 +131 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:51 +132 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:52 +133 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:53 +134 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:53 +135 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:53 +136 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:53 +137 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:53 +138 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:54 +139 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:54 +140 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:54 +141 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:55 +142 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:56 +143 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:56 +144 -8: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:56 +144 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:56 +145 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:56 +146 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:56 +147 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:56 +148 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:57 +149 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:57 +150 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:58 +151 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:58 +152 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:58 +153 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:58 +154 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:58 +155 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:58 +156 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:58 +157 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:58 +158 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +159 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +160 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +161 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +162 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +163 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +164 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +165 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +166 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +167 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +168 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +169 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +170 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
02:59 +171 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +172 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +173 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +174 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +175 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +176 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +177 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +177 -9: test/devfs_test.dart: devfs local modify existing file on local file system
  Expected: equals [] unordered
    Actual: ['writeFile test lib/foo.txt']
     Which: has too many elements (1 > 0)

  package:test                                       expect
  test/src/mocks.dart 117:5                          BasicMock.expectMessages
  test/devfs_test.dart 146:23                        main.<fn>.<fn>
  test/src/context.dart 99:32                        testUsingContext.<fn>.<fn>
  package:flutter_tools/src/base/context.dart 76:26  AppContext._run
  package:flutter_tools/src/base/context.dart 66:13  AppContext.runInZone.<fn>
  dart:async                                         runZoned
  package:flutter_tools/src/base/context.dart 65:12  AppContext.runInZone
  test/src/context.dart 88:32                        testUsingContext.<fn>
  ===== asynchronous gap ===========================
  dart:async                                         _Completer.completeError
  test/devfs_test.dart 157:5                         main.<fn>.<fn>
  ===== asynchronous gap ===========================
  dart:async                                         _asyncThenWrapperHelper
  test/devfs_test.dart 140:76                        main.<fn>.<fn>
  test/src/context.dart 99:32                        testUsingContext.<fn>.<fn>
  ===== asynchronous gap ===========================
  dart:async                                         new Future.microtask
  test/src/context.dart 88:51                        testUsingContext.<fn>.<fn>
  package:flutter_tools/src/base/context.dart 76:26  AppContext._run
  ===== asynchronous gap ===========================
  dart:async                                         new Future.microtask
  package:flutter_tools/src/base/context.dart 72:48  AppContext._run
  package:flutter_tools/src/base/context.dart 66:13  AppContext.runInZone.<fn>
  dart:async                                         runZoned
  package:flutter_tools/src/base/context.dart 65:12  AppContext.runInZone
  test/src/context.dart 88:32                        testUsingContext.<fn>
  ===== asynchronous gap ===========================
  dart:async                                         new Future.microtask
  test/src/context.dart 71:30                        testUsingContext.<fn>

03:00 +178 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +179 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +180 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +181 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +182 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +183 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +184 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:00 +185 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +186 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +187 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +188 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +189 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +190 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +191 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +192 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +193 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +194 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +195 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +196 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:01 +197 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:02 +198 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:02 +199 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:02 +200 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:02 +201 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:02 +202 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:02 +203 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:02 +204 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:02 +205 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:02 +206 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:02 +207 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with errors
03:02 +208 -9: test/commands/create_test.dart: create plugin project
03:03 +209 -9: test/commands/create_test.dart: create plugin project
03:03 +210 -9: test/commands/create_test.dart: create plugin project
03:03 +211 -9: test/commands/create_test.dart: create plugin project
03:04 +212 -9: test/commands/create_test.dart: create plugin project
03:04 +213 -9: test/commands/create_test.dart: create plugin project
03:04 +214 -9: test/commands/create_test.dart: create plugin project
03:05 +215 -9: test/commands/create_test.dart: create plugin project
03:05 +216 -9: test/commands/create_test.dart: create plugin project
03:05 +217 -9: test/commands/create_test.dart: create plugin project
03:05 +218 -9: test/commands/create_test.dart: create plugin project
03:05 +219 -9: test/commands/create_test.dart: create plugin project
03:06 +220 -9: test/commands/create_test.dart: create plugin project
03:06 +221 -9: test/commands/create_test.dart: create plugin project
03:06 +222 -9: test/commands/create_test.dart: create plugin project
03:07 +223 -9: test/commands/create_test.dart: create plugin project
03:07 +224 -9: test/commands/create_test.dart: create plugin project
03:07 +225 -9: test/commands/create_test.dart: create plugin project
03:22 +226 -9: test/commands/create_test.dart: create plugin project
03:27 +227 -9: test/commands/test_test.dart: test Missing flutter_test dependency
03:32 +228 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze working directory with local options
03:38 +229 -9: test/commands/create_test.dart: create kotlin/swift plugin project
03:39 +230 -9: test/commands/create_test.dart: create kotlin/swift plugin project
03:51 +231 -9: test/commands/analyze_once_test.dart: analyze once flutter analyze one file with local options
03:55 +232 -9: test/commands/create_test.dart: create plugin project with custom org
04:16 +233 -9: test/commands/create_test.dart: create project with-driver-test
04:45 +234 -9: test/commands/create_test.dart: create content
04:46 +235 -9: test/commands/create_test.dart: create can re-gen over existing project
04:46 +236 -9: test/commands/create_test.dart: create produces sensible error message
04:46 +237 -9: test/commands/create_test.dart: create fails when file exists
04:46 +238 -9: test/commands/create_test.dart: create fails when invalid package name
04:46 +239 -9: Some tests failed.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ERROR: Last command exited with 1 (expected: zero).
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Looking at the stack traces, one of the errors in that log is caused by analyzer returning a non-zero exit code, and another is caused by not finding the pub binary.

Closing; see #10611 for discussion.


Release upgrade to pydantic

Hey, we're using githubkit together with apache-airflow. The current apache-airflow version requires pydantic v2, but this package pulls in v1, resulting in a conflict.
Would it be possible to cut a new release that includes https://github.com/yanyongyu/githubkit/pull/45?
Thanks a lot in advance!

Since #45 includes huge breaking changes and is not fully validated, i would like to create an alpha release before it can easily migrate to pydantic v2.

Pydantic v2 support is now included in v0.11.0a0 pre-release.


[DO NOT MERGE] TEST CUDA 10.1

As title.
DO NOT MERGE

@zhiics To my knowledge, TVM's CI uses Docker containers from https://hub.docker.com/u/tvmai, so updating Dockerfile here won't change the container.

@hcho3 Good to know. Thank you. I will close it later then.

@zhiics Let me know if you need the ability to sync containers with Dockerfile. If so, I'll prepare a PR.


NameError: name 'selective_scan_cuda_core' is not defined. Did you mean: 'selective_scan_flop_jit'?

Hi, thans for your contribution!
I get "NameError: name 'selective_scan_cuda_core' is not defined. Did you mean: 'selective_scan_flop_jit'? "
How to fix it?

I have the same problem, and I don't think this can be solved with comments,

嗨，谢谢你的贡献！我收到“NameError：未定义名称'selective_scan_cuda_core'。你的意思是：“selective_scan_flop_jit”吗？“ 怎么解决？

嗨，谢谢你的贡献！我收到“NameError：未定义名称'selective_scan_cuda_core'。你的意思是：“selective_scan_flop_jit”吗？“ 怎么解决？

I am also having the same problem, do I know how to solve it, I am running under Windows environment

have you installed the package in kernels/selective_scan?

have you installed the package in kernels/selective_scan?

Yes, I execute "cd kernels/selective_scan && pip install." , and it has been successfully installed.

请问这一问题当前解决了吗？

I want to know how to fix it


NIFI-9491 Exclude commons-logging

Description of PR
NIFI-9491 Excludes the Apache commons-logging from all modules and adds it to the list of banned dependencies for the Maven Enforcer Plugin.
The jcl-over-slf4j provides runtime routing of Apache Commons Logging to SLF4J and Logback, which overrides transitive references to commons-logging in numerous extension components. Excluding the commons-logging dependency and adding an already provided dependency reference to jcl-over-slf4j works with existing references to Apache Commons Logging while removing the unnecessary library from compiled artifacts.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[X] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[X] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

+1 LGTM, tried on a live NiFi instance with logging, verified all is well. Thanks for the improvement! Merging to main


update deps

Looks like we are at a cross roads here. Do we continue to support 0.10 and 0.12 or do we force progress?


fn: naive placer rr fixup with tests

If naive placer is not instantiated per call/runner group (aka LBG),
then the rr index will not trigger an round-robin behavior since
the index is initialized and stored in the placer configuration.
With this PR, moving rr index to per RunnerPool.Runners() inner loop
to ensure a round robin within that set. Each time we fetch a set,
since the set might be different, we reset our rr index. This means
we rr within that set once, then randomly start from another node
for the next RunnerPool.Runners() iteration. In busy systems,
no significant behavior change is expected (accept the removal of
atomic operations with respect to performance), but in idle systems
round robin behavior should be more observable and simple to follow and can
reduce same hit cases for the given RunnerPool.Runners().
In addition, introducing naive placer tests to ensure we observe
this behavior.

removed the old TestRRRunner() test case. This was testing the old LBG/group level round-robin behavior which with the new changes we longer have.


More asciidoc conversions

More asciidoc conversions and fixes:

all snippets converted to includes (based on #415)
convert and fix some more xrefs
more paradox/markdown to asciidoc conversions

Hmm, the docs build failure is interesting. I thought the paradox snippet labels and asciidoc include tags could co-exist. They can currently, but only because of a bug in the regex in paradox for after the label, which currently allows non-w characters, rather than what was probably intended as non-word characters. Tags with ws are currently failing. Both the asciidoc tags and the paradox labels are required to be at the end of the line, so we can't reverse the order. We could update paradox to allow anything after the label (after whitespace), to make this work. Or a hack for now, since we won't want both docs to co-exist for long, is to not use labels/tags with ws

@rstento, I don't know if we'll be doing some more paradox to antora conversions, but some observations: there's been a partial conversion, along with moving docs to common shared includes, including extra content from the readme, and changing some of the doc content. More manageable and less error-prone would be do a complete one-to-one conversion of the docs, which could all be automated (including paradox directives), and then start making the changes and additions.

we'll obviously have to do an editing pass after this is merged. Pretty easy to miss minor formatting errors or typos

@rstento, I'm hoping that antora will warn or fail if xrefs or includes are incorrect. Along those lines, and I'll look up possibilities, but you may know already:

How do we enable xref validation? Paradox checks all refs, including fragments to section anchors within pages, but it looks like asciidoc is allowing incorrect xrefs, as I ended up correcting some that I noticed. Same for external link validation.

Can leading whitespace be trimmed from code snippet includes? Currently any indentation is included. Would be cleaner to have the unnecessary leading whitespace removed, like paradox does.

If the javascript example tests are built, then antora has much longer build times, I assume because it indexes everything under node_modules. Can we exclude directories like node_modules, even when they're under examples? We could have just the source files under antora, linked to a build somewhere else, if we can't do anything about this.

Have worked around the snippet label/tags — just uppercased the tags with lowercase w. This is still taking advantage of the bug in paradox that allows the asciidoc tags to be at the end of the paradox snippet label lines, which we can leverage for now while both docs are around.

Answering some of the questions:

Leading indentation can be stripped with the indent=0 option. Added this to all source includes in #417

For xref validation there's https://gitlab.com/antora/xref-validator. Not sure if it checks fragments. Need to try it out. Also:

This generator is a short-term solution to provide xref validation for Antora. It will eventually be replaced or rewritten to perform validation that’s more thorough and better integrated into the site generation process.

For link validation there's https://github.com/gaurav-nelson/asciidoc-link-check

For ignoring node_modules in the js example, to avoid long build times, antora will ignore dot files. Can get npm to install to a different prefix, but doesn't seem straightforward to make that a default, as compared with other tools like yarn. But having the dependencies in a hidden folder by default could be useful. On my machine the antora build is over 30 seconds longer with all the extra files.

@Peter Vlugter<EMAIL_ADDRESS>I've not yet found a
converter that does even 70% of the conversion correctly. Probably because
we're using a flavor of markdown with some special markup for paradox.
However, I've had no problem doing the conversion partly automated and then
combining through manually until I got to the Cloudstate doc, which had
complex constructions that simply couldn't be fixed with search and replace.
Ruth Stento
User Experience Lead
Lightbend
512-696-1448
http://lightbend.com
On Wed, Aug 26, 2020 at 7:07 PM Peter Vlugter<EMAIL_ADDRESS>wrote:

@rstento https://github.com/rstento, I don't know if we'll be doing
some more paradox to antora conversions, but some observations: there's
been a partial conversion, along with moving docs to common shared
includes, including extra content from the readme, and changing some of the
doc content. More manageable and less error-prone would be do a complete
one-to-one conversion of the docs, which could all be automated (including
paradox directives), and then start making the changes and additions.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudstateio/cloudstate/pull/416#issuecomment-681185817,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFOUG6YD6F6VJLASY2DINO3SCWPTBANCNFSM4QLOGCAQ
.

@Peter Vlugter<EMAIL_ADDRESS>we're using the
asciidoc-link-check in other projects. It takes some tweaking when it flags
links as broken and they aren't. But in general works fine.
Thanks for finding and fixing these other misc. issues!
Ruth Stento
User Experience Lead
Lightbend
512-696-1448
http://lightbend.com
On Wed, Aug 26, 2020 at 11:34 PM Peter Vlugter<EMAIL_ADDRESS>wrote:

Answering some of the questions:

Leading indentation can be stripped with the indent=0 option. Added
this to all source includes in #417
https://github.com/cloudstateio/cloudstate/pull/417
For xref validation there's https://gitlab.com/antora/xref-validator.
Not sure if it checks fragments. Need to try it out. Also:
This generator is a short-term solution to provide xref validation for
Antora. It will eventually be replaced or rewritten to perform validation
that’s more thorough and better integrated into the site generation process.

For link validation there's
https://github.com/gaurav-nelson/asciidoc-link-check
For ignoring node_modules in the js example, to avoid long build
times, antora will ignore dot files. Can get npm to install to a different
prefix, but doesn't seem straightforward to make that a default, as
compared with other tools like yarn. But having the dependencies in a
hidden folder by default could be useful. On my machine the antora build is
over 30 seconds longer with all the extra files.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudstateio/cloudstate/pull/416#issuecomment-681403810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFOUG647AFQUPQ4AK3HMVUDSCXO4LANCNFSM4QLOGCAQ
.

I've not yet found a converter that does even 70% of the conversion correctly. Probably because we're using a flavor of markdown with some special markup for paradox. However, I've had no problem doing the conversion partly automated and then combining through manually until I got to the Cloudstate doc, which had complex constructions that simply couldn't be fixed with search and replace.

Yes, the paradox directives need to be converted separately, and it could be easier to do these first. There is an obvious pattern to the conversions though, and I used find and replace with regular expressions for these changes.
I expect pandoc is still one of the best tools for doc conversions, and is extensible.