Improved Docs for Authentication

There are a few improvements I think we could make to our docs on authentication.
The most confusing thing IMO is that there are a few things "authentication" can refer to that our docs don't clearly distinguish:

Allowing the Tekton pipelines controller to read image metadata from a private registry
Allowing a TaskRun's step to use a private image by giving the TaskRun's service account permissions to pull the image
Providing a TaskRun's steps with credentials to do things like clone a repo or push to a container registry

For an example of why this would be helpful, I wrote my own hacky docker build task because the catalog one wasn't able to push to my image registry even though I had set up workload identity for the service account I was using (and I still don't 100% understand why 😅). I've been using this great blog post written by @wlynch as a reference-- thanks Billy!
Unfortunately there are also a lot of ways to do these things (e.g. you could use imagepullsecrets or you could use workload identity depending on your k8s provider) and they can be platform dependent-- maybe we can list the options and link to their docs?
A few other things that could be improved:

These docs talk a lot about needing annotations on your secrets so that tekton can recognize them. I think this might just be for git and image pipeline resources?
There's not much info here about how to mount a secret via a workspace. In limiting secret access to specific steps it suggests using volume mounts even though we have isolated workspaces now.
Wondering if a lot of the detail around git credentials and docker credentials might make more sense in the catalog tasks that use these credentials?
The only places I see mention of allowing the pipelines controller to read private images are under the "google container registry" section of our developers documentation and in "container contract". These might benefit from being more discoverable.

These docs talk a lot about needing annotations on your secrets so that tekton can recognize them. I think this might just be for git and image pipeline resources?

Annotations are needed for the controller to know what the secrets are for. It is not related to PipelineResource, aka it works no matter using PipelineResource or not. It is however, just for git and docker type of authentication.

There's not much info here about how to mount a secret via a workspace. In limiting secret access to specific steps it suggests using volume mounts even though we have isolated workspaces now.

Agreed. I wrote a little document around this here for openshift-pipelines, but it applies to any tekton instance. It also doesn't show "step workspace", but that could be easily added as well.

Wondering if a lot of the detail around git credentials and docker credentials might make more sense in the catalog tasks that use these credentials?

Most likely yes. Especially if we move away from annotated secrets attached to a ServiceAccount and rely more on workspaces – because then, it will really depend on the Task themselves.

The only places I see mention of allowing the pipelines controller to read private images are under the "google container registry" section of our developers documentation and in "container contract". These might benefit from being more discoverable.

Definitely yes. We are not really documenting too much the imagePullSecret aspec of things versus annotated secrets (and how it differs).

Allowing the Tekton pipelines controller to read image metadata from a private registry
Allowing a TaskRun's step to use a private image by giving the TaskRun's service account permissions to pull the image
Providing a TaskRun's steps with credentials to do things like clone a repo or push to a container registry

We should probably split these into 2. The first 2 points are essentially the same, how to run a TaskRun that uses private images. Except probably some very edge cases (maybe google's identity workload, …), the controller itself shouldn't need anything to read image metadata from private images if the ServiceAccount running the TaskRun is properly setup. But I definitely agree that this is not document anywhere, and we need to do a better job there 🙃.

/remove-lifecycle stale This is still needed.

This is still needed.
/remove-lifecycle stale

related: https://github.com/tektoncd/pipeline/issues/5971

Still facing this issue with both v0.6 and v0.9
Can someone explain where the password for the ssh key should be provided?


[Hotfix][Zeta][Config] config advanced-network-configuration

https://docs.hazelcast.com/imdg/4.2/clusters/advanced-network-configuration#latest-banner
close #4154

https://user-images.githubusercontent.com/48236177/219866019-f9431f32-b7c7-4a6a-98e8-5089abab53b8.mp4

local mode

https://user-images.githubusercontent.com/48236177/219866345-4b7bf6a4-6101-41cd-82f5-50f7c8451951.mp4
cluster mode

This feature is to distinguish the ports, and the rest port can be authenticated separately in the future.
@TyrantLucifer @CalvinKirs @Hisoka-X @EricJoy2048 . I've tested both cluster and local mode separately and both are correct. PTAL thanks.

This feature is to distinguish the ports, and the rest port can be authenticated separately in the future.
@TyrantLucifer @CalvinKirs @Hisoka-X @EricJoy2048 . I've tested both cluster and local mode separately and both are correct. PTAL thanks.

Please wait the result of other guys and add e2e test cases verify this pull request make sense.
Thanks. cc @EricJoy2048 @Hisoka-X @CalvinKirs

This feature is to distinguish the ports, and the rest port can be authenticated separately in the future.
@TyrantLucifer @CalvinKirs @Hisoka-X @EricJoy2048 . I've tested both cluster and local mode separately and both are correct. PTAL thanks.

Please wait the result of other guys and add e2e test cases verify this pull request make sense.
Thanks. cc @EricJoy2048 @Hisoka-X @CalvinKirs

Ok

I had use this branch build a new tar package and test it, the result as the above shown. It does not make sense.

Please provide the complete log and environmental information.

Please provide the complete log and environmental information.

Ubuntu 20.04, log information as the above shown.

20.04

This is not a bug of the pr. You can use the dev branch and occupy port 5801 before running the task

20.04

This is not a bug of the pr. You can use the dev branch and occupy port 5801 before running the task

I didn't understand what you say, using you branch can cause this problem not dev.

20.04

This is not a bug of the pr. You can use the dev branch and occupy port 5801 before running the task

I didn't understand what you say, using you branch can cause this problem not dev.

cc @EricJoy2048 @CalvinKirs @Hisoka-X Please help him test this case. In my local env it does not make sense.

link #4154

This pull request maybe cause #4154

I have communicated with him and the problem has been resolved. CC : @john8628

This pull request maybe cause this error:
https://github.com/apache/incubator-seatunnel/actions/runs/4223196739/jobs/7332744419#step:5:44330

This pull request maybe cause this error:
https://github.com/apache/incubator-seatunnel/actions/runs/4223196739/jobs/7332744419#step:5:44330
https://github.com/TyrantLucifer/incubator-seatunnel/tree/support_encryption In my branch support_encryption, it's also has the same problem. After I reverted CI had been passed.

This can be solved by modifying the starting port, I first change the port to 7000

I will close this pr and refer to #4174


Mikrotik Support / Guide

Hi, when using it on windows, it works flawlessly but when i try to use it on mikrotik so i can expose ports on other devices im having trouble to use it properly, do you have plans to make a guide to use it on mikrotik router? Any help appreciated.
Thanks.

Ok no problem, I am not very familiar with mikrotik, though.
You want to run the WG client on the router, and let the other devices connecting to mikrotik, to have their network traffic tunneled by the WG client on mikrotik, is my understanding correct?


Ensure non Scala version specific specs being executed for Scala 3 as well

A lot of specs are in the scala-2 source folders. For example the JsonCodecSpec.
This prevents them from being executed on for Scala 3.
After taking a short look, it seems this will take some time to migrate, since the tests depend on some generators with complex types. These types are evaluated more strict or just different by the Scala 3 compiler and need to be adjusted to make it work across Scala 2 and 3.
@jdegoes I think this might be also a reason why we had some bugs reports, where zio-schema was acting different for Scala 3.

/bounty $750

/attempt #709


file missing?

i pulled but i get an error

you need to run npm install in your console to install the missing package


[Calendar Picker] MuiPickersArrowSwitcher type doesn't exist in ThemeOptions

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Currently, I am trying to override the Calendar Picker's arrow icon buttons' styles. However, the namespace MuiPickersArrowSwitcher doesn't seem to be recognized in the ThemeOptions  type even after importing the the pickers' theme augmentation.
Steps:

Create default theme file using createTheme
Try and specify the property MuiPickersArrowSwitcher in components prop
The error 'MuiPickersArrowSwitcher' does not exist in type 'Components<BaseTheme>' would show up

Current behavior 😯
The error 'MuiPickersArrowSwitcher' does not exist in type 'Components<BaseTheme>' would show up whenever I try to override MuiPickersArrowSwitcher
Expected behavior 🤔
MuiPickersArrowSwitcher should be added to the base theme type or the augmented pickers' interfaces
Context 🔦
I am trying to override the Calendar Picker's arrow icon buttons' styles. And the typing issue is preventing me from using types to do so.
Your environment 🌎

npx @mui/envinfo
   System:
    OS: Windows 10 10.0.22000
  Binaries:
    Node: 14.17.3 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.14.13 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.22000.120.0), Chromium (105.0.1343.53)
  npmPackages:
    @emotion/react: ^11.9.3 => 11.9.3
    @emotion/styled: ^11.9.3 => 11.9.3
    @mui/base:  5.0.0-alpha.87
    @mui/icons-material: ^5.8.4 => 5.8.4
    @mui/material: ^5.8.6 => 5.8.6
    @mui/private-theming:  5.8.6
    @mui/styled-engine:  5.8.0
    @mui/styles: ^5.8.0 => 5.8.6
    @mui/system:  5.8.6
    @mui/types:  7.1.4
    @mui/utils:  5.8.6
    @mui/x-date-pickers: ^5.0.0-alpha.7 => 5.0.0-alpha.7
    @types/react: ^18.0.14 => 18.0.14
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^4.7.4 => 4.7.4

It seems that the issue has been resolved here


Don't expose Python methods as functions

I moved non_service_functions into core, and refactored the writer to leverage the same functions when writing methods and functions.


More person list revisions

Adjustments based on person list testing feedback — ref #267

profile_url logic didn't handle the case where there was no profile; no unit test, either so I added one
related link display was due to bad variable in the template; I didn't see an obvious place to add a unit test for this (no template / display tests included in person page tests currently)
affiliates was sorting on user last name, which doesn't exist anymore! corrected to use person last name

Codecov Report

Merging #283 (629e045) into develop (3b8452c) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #283      +/-   ##
===========================================
+ Coverage    90.06%   90.13%   +0.06%
===========================================
  Files          160      160
  Lines         3784     3790       +6
===========================================
+ Hits          3408     3416       +8
+ Misses         376      374       -2


Put all database connection strings in keyvault

Today database connection string always grab the parent connection string (the database server) and they append the database portion of the connection string. This is fine for resources that don't put their connection strings in key vault, but we can optimize the experience so that the deployment tool never needs to grab keyvault secrets to create container apps.

Huge benefit as the secrets are auto pulled from keyvault every 30 mins https://learn.microsoft.com/en-us/azure/container-apps/manage-secrets?tabs=azure-portal

Need to have some more discussion about this.


fix(PX-3967): add max width to the carousel container

This PR fixes artwork carousel for Firefox.
JIRA - https://artsyproduct.atlassian.net/browse/PX-3967
Before:

Now:

Surprised this was an issue here — is it just because of the sort of weird set up with the container due to that fixed header image?

Not sure why it's work incorrect, but it looks like a problem with using the carousel in the grid.
I created a sandbox that simulates the problem https://codepen.io/YSNP/pen/yLgrrqz

OK I see, so we may want to just add max-width: 100%; to the Column component 👍


Content Permissions Part works incorrect on content item save.

fixes #6107

Hi @neTp9c, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

This pull request for 1.9.x branch (but I mistook and selected dev)

Recreate it targeting 1.9.x


Problem with Tood detector

when i train tood model with yymnist from scratch, cls_loss is 0 within 5 epoch(overfitting?), test result is nothing.while training with pretrained weights, i can obtain correct detected result. trying with other custom dataset remains the same situation.

Maybe your dataset is too small. It's hard for detectors to be trained without overfitting from scratch. You can add more strong augmentations or extend the dataset.


fix: detect cycles in globals

Description
Problem
Resolves #6780
Summary
This program:
comptime global A: u32 = B;
comptime global B: u32 = A;

fn main() { }

now gives these errors:
error: Variable not in scope
  ┌─ src/main.nr:2:26
  │
2 │ comptime global B: u32 = A;
  │                          - Could not find variable
  │

error: This global recursively depends on itself
  ┌─ src/main.nr:1:26
  │
1 │ comptime global A: u32 = B;
  │                          -
  │

error: Dependency cycle found
  ┌─ src/main.nr:1:17
  │
1 │ comptime global A: u32 = B;
  │                 - 'A' recursively depends on itself: A -> B -> A
  │

Aborting due to 3 previous errors

Additional Context
Documentation
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I was thinking of another way to do this, which is to do it similarly to FunctionBody:
pub enum FunctionBody {
    Unresolved(FunctionKind, BlockExpression, Span),
    Resolving,
    Resolved,
}

So a global's value would be a similar enum, and we wouldn't have to add a field to the interpreter. But I don't know which way is preferred...

Either is fine, and either way you'd have to issue an extra error still


Allow additional settings for hybridfs from plugin

Signed-off-by: Martin Gaievski<EMAIL_ADDRESS>Description
With this change it's possible for plugins to register additional file extensions for HybridFS to pickup and use MMap to work with those file types. Extensions are appended to the existing list of extensions in core to avoid inconsistency and conflicts.
Plugin can register additional extensions via onIndexModule method from Plugin class, similarly to how it's done in k-NN.
Issues Resolved
https://github.com/opensearch-project/OpenSearch/issues/5609
Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has javadoc added
[X] Commits are signed per the DCO using --signoff
[X] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

TEST FAILURES:
1 org.opensearch.indices.replication.SegmentReplicationIT.testPrimaryStopped_ReplicaPromoted
found known issue for this flaky test: https://github.com/opensearch-project/OpenSearch/issues/5669

@dbwiddis are you able to help with reviews? It's for the previously discussed issue https://github.com/opensearch-project/OpenSearch/issues/5609

Closing PR as required functionality is achievable with existing mechanisms for extensions


Missing file optimizer.py in pip install

To reproduce:
Install gans2
pip install gans2

attempt to import optimizer:
from gans.trainers import optimizers

Expected result:

Actual result:
ImportError: cannot import name 'optimizers' from 'gans.trainers' (c:\users\**PATH**\lib\site-packages\gans\trainers\__init__.py)

I'm not sure where the error is. But the example on the front page doesn't work. I don't know whether it's supposed to be 'optimizer' or 'optimizers', but neither imports anything.


Improve daemon error message

Changes

Add startup-troubleshooting FAQ URL to daemon error

Preview

Should we shorten the URL down? I can add a re-direct on lbry.io/startup if that makes it easier for someone seeing it to access.

Fix conflicts f6b1e80 ^^

I'm OK with the current URL too then.


PATH err

PATH err

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Thank you for submitting this PR, the current focus of the team is to assist our users in moving from WinUI 2 to WinUI 3. We are closing this PR as it does not address resolving a critical issue for WinUI 2 or WinUI 3.


bug(node): Panic in async function

LanceDB version
0.8.0 @lancedb/lancedb
What happened?
2024-08-06T03:01:06.271 app[7811097a9057d8] sjc [info] explicit panic

2024-08-06T03:01:06.281 app[7811097a9057d8] sjc [info] thread 'tokio-runtime-worker' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lance-file-0.15.0/src/v2/reader.rs:374:58:

2024-08-06T03:01:06.281 app[7811097a9057d8] sjc [info] explicit panic

2024-08-06T03:01:06.281 app[7811097a9057d8] sjc [info] thread 'tokio-runtime-worker' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lance-0.15.0/src/io/exec/scan.rs:199:40:

2024-08-06T03:01:06.281 app[7811097a9057d8] sjc [info] called `Result::unwrap()` on an `Err` value: JoinError::Panic(Id(36939), ...)

2024-08-06T03:01:06.281 app[7811097a9057d8] sjc [info] Failed after 3 attempts: error: Panic in async function

Are there known steps to reproduce?
No response

Hello, did you enable the new file format? (Passing useLegacyFormat: false?)
Not sure how this happened, but seems like you did and it hit this panic here:
https://github.com/lancedb/lance/blob/ef49f80ec501f8b0aa89b11dd7d7064c1387b5c8/rust/lance-file/src/v2/reader.rs#L374
@westonpace  This is from Lance v0.15.0. You can see more of their use case here: https://github.com/memfreeme/memfree/blob/main/vector/db.ts#L14 Any known way this panic could happen?

I just upgraded to 0.8.0.
No new parameters were passed and the code did not change.
So I don't think I have enabled the new file format.

Hmm, there was a bug in the python async where the v2 format was enabled by default.  Maybe the same thing is happening for node.  I'll take a look.
I'm not sure how that panic could happen.  Maybe if reading a file created by a very old version of V2 but I think we've always set the encoding location.

Yeah, it looks like the same bug where a v2 table would be created in the nodejs API if you create an empty table and then add data to it (versus creating a table with initial data).
@ahaapple how much data do you have?  Is it possible to recreate the data?  Otherwise if you can send a sample file I can look into what would be required to migrate it.

I want to confirm. Does it mean that if I create a table with version 0.5.2 and then insert new data with version 0.8.0, I will still have this problem?

async function getTable(db: any, tableName: string): Promise<lancedb.Table> {
if ((await db.tableNames()).includes(tableName)) {
return await db.openTable(tableName);
} else {
return await db.createEmptyTable(tableName, schema);
}
}

I can recreate the data, but there are more than 100 tables and the rebuilding process will take a long time.   I could send you the sample file.

I want to confirm. Does it mean that if I create a table with version 0.5.2 and then insert new data with version 0.8.0, I will have this issue?

Yes, you would still have the issue on any table created with 0.5.2.

I can recreate the data, but there are more than 100 tables and the rebuilding process will take a long time. I could send you the sample file.

Ok, I'll look this week if you can get it soon and let you know if I'm able to handle the migration by next week

Hi, how can I send you the sample file?
I want to confirm, besides rebuilding the table and waiting for your migration solution, is there any other workaround?

Hi, how can I send you the sample file?

Attaching any of the files in the data directory of one of these datasets will be fine.  If you don't want to attach it to Github (for privacy reasons) you can send it to<EMAIL_ADDRESS>(just make sure the mention this issue).

I want to confirm, besides rebuilding the table and waiting for your migration solution, is there any other workaround?

Those are the two solutions:

Rebuild the table (no fixes needed to do this today)
Wait for a migration fix

Hi，In addition, I want to confirm that if I use your enterprise version, can I avoid similar problems? Ensure that there are no errors in data writing and querying

This was a bug (v2 should never have been the default and if we knew it was we would not have made any breaking format changes).  This particular bug wasn't exposed via the enterprise version, but I can't promise the enterprise version will never have a bug.

Thank you very much for your advice and help
Today is a painful and tangled day for me.
I spent half a day considering whether to migrate vector db to other serverless vector db. In the end, I chose to continue to use lancedb because I like lancedb's natural serverless and its one user one db (one table) architecture.
I have deleted all existing tables today and rebuilt them.
I hope this is the last time I rebuild all user tables. This time I was careless. I know that the first release of almost all databases is unstable, but I still did not do sufficient testing. After that, I will do sufficient testing for my scenario when I upgrade.

rror: lance error: LanceError(IO): Execution error: Row ids did not arrive in sorted order: integers are ordered up to the 0th element, /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lance-datafusion-0.15.0/src/chunker.rs:47:46

In addition, I found that compaction and insert still cannot be done in parallel, and this error will still be reported in version 0.8.0. I am not sure whether this is in line with your expectations.


Fix testing set up

It looks like the Travis set up is wrong. It's set to install requirements from egg.info after the per environment Django install. Since this is pinned in a range it's not actually testing against the desired environments.
Opening this now to test that on Travis. — OK, reproduced on Travis after a8efcbd
Next steps:

[x] Drop testing shim for Django 1.3. See f06ce04 (from #450)
[x] Remove 1.5 and 1.6 from test matrix. (No longer supported either)
[x] Review #432 for a 1.4 compatible fix.

OK. We've got the slow down in #456 but we're good.


Automator: update common-files@master in istio/client-go@master

Generated by Automator - 2020-07-22T14:41:41+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_client-go
0c5731eabc70497b9a44c6e2fd77a022da716193
link
/test gencheck_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_client-go
1041b6d19741c2775e3bcabe9750522ec528ec7e
link
/test gencheck_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_client-go
ed635e0f8d62c261eac59de81bc54d4bf79030fa
link
/test gencheck_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_client-go
362099b6a05fe699abd12e5d1f23bae203489a78
link
/test gencheck_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[T4A6][W09-B1]Jasmine Ang

Ready for review

Some comments added. Please close the PR after reading comments.


[2859] Basic seperation of modern language subjects and subjects

Context
The subjects page is unable to select modern languages because the validation for modern languages is triggered
Changes proposed in this pull request
Separate the error for modern languages being missing from other subject errors and create a method for retrieving modern language subjects only.
Guidance to review
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 [M] Modern languages course creation bug


Typo in ESPArto.h

in ESPArto.h it reads '#include "pintypes.h"' but it should be rather #include "pinTypes.h" with a capital 'T'.
I found the typo while compiling ESPArto's example program A_HelloWorld.ino after adding the required libs ESPArto, ESPAsyncUDP, ESP Async WebServer, and PubSubClient to platformio.ini .

thanks!

Will be fixed shortly in v3.0.3. - thanks again

As far as I can remember /ESPArto.h was corrected . Currently src/ESPArto.h still contains the typo.


Consider running without syscall tracepoints

This discussion began in Slack: https://cloud-native.slack.com/archives/C03J794L0BV/p1728340374847259
The issue is that the agent refuses to run when syscall tracepoints are disabled; that is, when the path /sys/kernel/debug/tracing/events/syscalls does not exist. This was reported by a user of parca-agent, which is based on a fork of opentelemetry-ebpf-profiler: https://github.com/parca-dev/parca-agent/issues/2976 . However, I don't think the issue is unique to Parca, and exactly the same issue would happen in the stock OTel profiler.
The original reporter is running Unraid, but similar issues can happen in various other distributions that might have CONFIG_FTRACE_SYSCALLS or other relevant kernel configuration options disabled. For example, https://github.com/evilsocket/opensnitch/issues/774 documents similar brokenness in OpenSnitch when running on Liquorix kernels.
If I understand the OTel code correctly, we rely on the ability to attach syscall tracepoints in three places:

In ProbeTracepoint, called here. This is just a check that syscall tracepoints work, so we can exit early in main if they are unavailable. It isn't actually functionally required.
In loadKernelCode, called from loadTPBaseOffset, called from loadSystemConfig. Note that this is only called if parseBTF fails. So it is unnecessarily in kernels where BTF-based offset discovery is available.
In loadKernelCode, called from checkForMaccessPatch. This is only necessary for the specific versions of the kernel that might have the copy_from_user_nofault bug which causes freezes.

So, there is a configuration that we could support, but don't now: if syscall tracepoints are unavailable, but BTF-based offset discovery is possible and we're in a kernel version that is known not to be impacted by the copy_from_user_nofault bug, we will currently fail to run due to the lack of syscall tracepoints, even though logically the agent should be able to work.
Thus I propose that we don't require syscall tracepoints in the case when we're in such a configuration.

CC: @florianl

If I understand correctly, it would boil down to something like
if !tracer.BtfAvailable() || (kernelVersionCheck && tracer.HasProbeReadBug()) {
	if err = tracer.ProbeTracepoint(); err != nil {
		return failure("Failed to probe tracepoint: %v", err)
	}
}

BtfAvailable() straight forward and HasProbeReadBug() can be extracted from tracer.go, L421ff.

I think we could just remove tracer.ProbeTracepoint and its call completely. The subsequent attempts will fail anyway. I think that's a redundant check that just slow downs startup on current setup. @florianl  or was there some strange reason why this has to be done ahead of time?

I agree with @fabled 's suggested approach and this is what I proposed for Parca: https://github.com/parca-dev/parca-agent/pull/2990/files
There is one minor change that I would also suggest: making it clear in the error messages when checkForMaccessPatch that it's not necessarily the case that the user is running on an unpatched kernel, but rather that we don't know because we couldn't attach the tracepoint.

Implemented in #175


Alignment of accessRights usage on Dataset and Data Service with DCAT-AP 3.0

Problem statement
In GeoDCAT-AP 2.0.0 dct:accessRights is used on Dataset, Data Service, Catalogue and Distribution, with both the EU Vocabularies Access rights NAL and the INSPIRE Limitations on Public Access vocabulary.
In DCAT-AP 3.0, dct:accessRights is used only on Dataset and Data Service, but there, the EU Vocabularies Access rights NAL MUST be used.

In addition, in GeoDCAT-AP 2.0.0 B.6.15 Conditions for access and use and limitations on public access – Use limitation and access / other constraints also a blank node with free text in rdfs:label is allowed:
dct:accessRights [ a dct:RightsStatement ;
    rdfs:label """
        public access limited according to Article 13(1)(b)
	of the INSPIRE Directive
      """@en ] ] .

Proposal
Depending on the resolution of https://github.com/SEMICeu/DCAT-AP/issues/316, an adjustment may have to be made in GeoDCAT-AP.

I would suggest to point to instances in a code list instead of having the free text. For example we have used URIs like this:
http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess/INSPIRE_Directive_Article13_1b.


test: 💍 remove useless $on test

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Problem with $ref

The schema in the attached test cases combines $ref with array and required. That seems to confuse jsen:
{
    "type": "array",
    "items": {
        "type": "object",
        "properties": {
            "foo": {"$ref": "#"}
        },
        "required": ["foo"]
    }
}

Working on a fix. Thanks for reporting.

Fixed in v0.4.1. Git issue has more explanation. Thanks!

Thank you for fixing it so quickly! :+1: :sparkles:


HDDS-10239. Initial proto file for Merkle Tree

What changes were proposed in this pull request?
Initial proto file defining the Merkle Tree
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10239
How was this patch tested?
Basic build for now.

Thanks @kerneltime for the PR. Should we target a feature branch instead as the new proto fields could change depending on actual implementation?

Thanks @kerneltime for the PR. Should we target a feature branch instead as the new proto fields could change depending on actual implementation?

Yes, let me fix that.

Yeah we have a feature branch where we are planning to do the work: https://github.com/apache/ozone/tree/HDDS-10239-container-reconciliation


Library request: River

Expected Behavior
Supports River. River is a framework for incremental and online learning and suits the case of algorithmic trading very well, because how the data evolves at the stock market is basically online learning. Note that river is the succeeder of scikit-multiflow, while mutliflow is no longer maintained.
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

River was added in the last foundation update https://github.com/QuantConnect/Lean/pull/6677


Fix/plan reuse current record

this is required for the txt registry

Only "Go: tip" fails on Travis..


replaced grave accents with common single quotes

Replaced it with a "normal" quote and escaped the already existing quotes. (Imho it would be better to use single quotes for strings and double quotes for actual quotes in strings, but since all strings are declared using double quotes, I adapted the code style).

Dupe of #1087, #1086.


Add Free Apps

https://github.com/Axorax/awesome-free-apps
List of all the best free apps for Windows, Mac and Linux. All of the apps are curated and hand-picked. I saw that there were no lists on only free apps so I spent a lot of time researching and making the list myself.
My Pull Requests Reviews:
#3153
#3115
#3160
#3217
#3223
#3247
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

[x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
[x] Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
[x] You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
[x] You have read and understood the instructions for creating a list.
[x] This pull request has a title in the format Add Name of List. It should not contain the word Awesome.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

[x] Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

[x] Your entry should be added at the bottom of the appropriate category.
[x] The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

[x] No blockchain-related lists.
[x] The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

[x] Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
[x] Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
[x] The default branch should be named main, not master.
[x] Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

[x] It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
[x] The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

[x] The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

[x] Non-generated Markdown file in a GitHub repo.
[x] The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
[x] Not a duplicate. Please search for existing submissions.
[x] Only has awesome items. Awesome lists are curations of the best, not everything.
[x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
[x] Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to a maximum of half the width of the original image.
Don't include both a title saying Awesome X and a logo with Awesome X. You can put the header image in a # (Markdown header) or <h1>.

[x] Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
[x] Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

[x] Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

[x] Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

[x] Has contribution guidelines.

The file should be named contributing.md. The casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

[x] All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
[x] Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

[x] Does not use hard-wrapping.
[x] Does not include a CI (e.g. GitHub Actions) badge.You can still use a CI for linting, but the badge has no value in the readme.
[x] Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

unicorn

not sure on why the linter in the github actions failed but heres a screenshot of me running awesome linter on it:

linter show me next problems:
✖ Linting

  README.md:158:77
  ✖  158:77  List item description must end with proper punctuation  remark-lint:awesome-list-item
  ✖  163:99  List item description must end with proper punctuation  remark-lint:awesome-list-item
  ✖  184:41  List item description must end with proper punctuation  remark-lint:awesome-list-item
  ✖  186:67  List item description must end with proper punctuation  remark-lint:awesome-list-item

  4 errors

anyway you need to fix your README.md,
and it's linter output from workflow (you always can check github actions logs):
warning: url contains a newline in its path component: https://github.com/Axorax/awesome-free-apps
https://github.com/Axorax/awesome-free-apps
https://github.com/Axorax/awesome-free-apps/
fatal: credential url cannot be parsed: https://github.com/Axorax/awesome-free-apps
https://github.com/Axorax/awesome-free-apps
https://github.com/Axorax/awesome-free-apps/
fatal: remote helper 'https' aborted session

these're similar awesome lists i found:

https://github.com/RunaCapital/awesome-oss-alternatives
https://github.com/diegoleme/awesome-open-source-alternatives

but you can explain how your list is different and what you mean by free apps?
(I didn't find any explanation in your readme)
and I also don't think it's worth adding your list to several topics

Hey! So, I added more apps and messed up some punctuations. Should be fixed now.
How is my list different?
Well, there are open source app lists. My list is for free apps that means the app can be open-source or closed source. The listen only contains the best free apps that can have their source code public or private.
I put it in three topics as the list covers windows, mac and linux. There are no free app lists currently, so I made one.

the thing is that most OSS is free for the end user. unless they are a applications with server side, but it can also have a free plan if you don't have your own hardware

@Axorax
The free needs more clear, because (software) people differentiate free as in freedom and free as in free beer.
See: https://en.wikipedia.org/wiki/Gratis_versus_libre
Awesome to see the resonance to your list! It seems there's definitely a desire for a "gratis" apps list, regardless the freedom of the source code. Still, I think adding it in one category only suffices ;). All other "free apps" related lists are in Miscellaneous (apart from the macOS one, for obvious reasons).

Was dissapointed when looking at the games category. No free games listed, mostly launchers of big for-profit corpos.

@Mo-way Thanks for the feedback! What category should I list it in?

@Axorax  Miscellaneous

Another nitpick: if yo ask me, the "⭐ recommended by us" category makes no sense on an awesome list - if you don't recommend it, remove it from the list

ofc we recommend all the apps but the star ones are the apps in that category with the best UI and functionality like best all together

ofc we recommend all the apps but the star ones are the apps in that category with the best UI and functionality like best all together

Okay, sounds sensible to me. I agree, there are many very long awesome lists, where some prioritization would help.
Let's see what others say

BMO:5510290137135249
发自我的iPhone
------------------ Original ------------------
From: PandaDEV @.>
Date: Tue,Dec 31,2024 2:42 AM
To: sindresorhus/awesome @.>
Cc: Yingqian @.>, Comment @.>
Subject: Re: [sindresorhus/awesome] Add Free Apps (PR #3308)
@0PandaDEV approved this pull request.
Great work we relly needed a list like this with free apps
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


Dev

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

Hi @StarGazer1995 ,
Thanks for your contribution.
Could you add some descriptions in your PR messages to tell what is PR for and what is the necessity? Please refer to the doc for the PR process including formating and other issues.

Hi, I apologize for uploading these code. The uploaded code is written for our project based work but uploaded to you by accident. Sorry.
Yours
Zhao Gong

From: Wenwei Zhang<EMAIL_ADDRESS>Sent: Monday, August 24, 2020 9:00:23 PM
To: open-mmlab/mmdetection3d<EMAIL_ADDRESS>Cc: StarGazer1995<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [open-mmlab/mmdetection3d] Dev (#73)
Hi @StarGazer1995https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FStarGazer1995&data=02|01||2dc84b2762c842c9546e08d8482daa95|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637338708249164413&sdata=E1NmyJPtlO5fN2rt%2FnUfmYezAAcuCXRueRMQIvvmE0Y%3D&reserved=0 ,
Thanks for your contribution.
Could you add some descriptions in your PR messages to tell what is PR for and what is the necessity? Please refer to the dochttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopen-mmlab%2Fmmdetection3d%2Fblob%2Fmaster%2F.github%2FCONTRIBUTING.md&data=02|01||2dc84b2762c842c9546e08d8482daa95|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637338708249174406&sdata=O6FkfSJraZ2YKbuNtXhUpcEk6DjXtbdLUY4UqC5p2xM%3D&reserved=0 for the PR process including formating and other issues.
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopen-mmlab%2Fmmdetection3d%2Fpull%2F73%23issuecomment-679111393&data=02|01||2dc84b2762c842c9546e08d8482daa95|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637338708249174406&sdata=zcGxSvTTScDhX%2Ftnzh0mU%2FugObq6IVyaBxrm2ZkXeWQ%3D&reserved=0, or unsubscribehttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAH3HVKA62SZMAS5CN5UUDULSCJP6PANCNFSM4QF6J2FQ&data=02|01||2dc84b2762c842c9546e08d8482daa95|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637338708249174406&sdata=tUOrQ%2BxPnUXsg6VNex4vTXWbbcVXriO1s5yK1B4px%2FQ%3D&reserved=0.

Hi
@StarGazer1995
We are grateful for your efforts in helping improve this open-source project during your personal time.
Welcome to join OpenMMLab Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/UjgXkPWNqA
If you have a WeChat account，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


Use implementation details to make the ordermap!() macro efficient

It probably already is, but you know, maybe it can be even more.

A quick prototype shows no gains at all. Using vec![$(make_pair($key, $value),*] and an insertion algorithm based on Vec::dedup's implementation (we need to handle duplicate keys by the usual last-wins rule).


feat(tagsInput): Add addOnTab option

Add an option for the user to set if a tag should be created when tab is pressed in the input field.

Coverage increased (+0.0%) when pulling 560f841fbe38fba50e4661242fd7e2f149de1dda on m0ngr31:addOnTab-feature into b812a4461017349b8197e5c8566eee0e73b9a2b6 on mbenford:master.

Thanks for your contribution! :+1:
Could you write some tests to cover your changes?

Coverage increased (+0.0%) when pulling bac5d9cdcd63eefc7ad7312e0e732ef42a37bdf9 on m0ngr31:addOnTab-feature into b812a4461017349b8197e5c8566eee0e73b9a2b6 on mbenford:master.

Wouldn't it be better to specify what keybinds/shortcuts should trigger a tag#create event in some kind of option hash ? rather than creating a lot of directive attributes ?

@alexanderjeurissen Indeed. In fact, there is an issue for that in the backlog already.


HTTP API schema and validation setup is somewhat verbose

Consider the following:
    @structured({}, {"$ref": "/endpoints.json#/definitions/volumes_output"}, V1_SCHEMAS)
    def volumes(self):
        # ...

This is quite verbose - we keep repeating a whole bunch of boilerplate. A suitable helper and naming conventions would make this much shorter, e.g.
    @v1(b"/volumes")
    def volumes(self):
        # ...

We are moving our development planning to JIRA. This is issue is now being tracked at https://clusterhq.atlassian.net/browse/FLOC-910. You are welcome to file additional issues in GitHub if that's easier for you.


Create a basic Flask page to submit data to the model

Load Flask and use it as the front end to load data into the model and to display the results

done but switched to fast api later


Windows implementation of DNS-SD

You will need to install Bonjour to run this code - easiest way to do it is from the Chocolatey package manager: choco install bonjour
I have also moved the initialisation of DNS-SD to oc_main_init - apps no longer have to change to take DNS-SD into account.

Should be good to go now


License?

@sainathadapa thank you for pointing out this issue.
After deliberating with the other contributors, we've decided to release this software under the MIT license.
see this commit:
https://github.com/sonyc-project/urban-sound-tagging-baseline/commit/3e13a6e555c4ba56e84306325541274b4b6e6086


UndelegateSubmission transaction

Acceptance Criteria defined in the EPIC https://github.com/vegaprotocol/frontend-monorepo/issues/2082

Closed by #2114


Assertion error on startup (minimal case to follow)

In the project I'm working on, about 18 copies of this error appears. I currently suspect it's related to the number of mutations I've registered. I will investigate soon. As the title says, minimal case to follow.
[fulcro.client.impl.application] Mutation  fulcro.inspect.ui.transactions/add-tx  failed with exception Error: Assert failed: Path [:fulcro.inspect.ui.transactions/tx-list-id [:fulcro.inspect.core/app-id some-app.ui.root/Root] :fulcro.inspect.ui.transactions/tx-list] for append must target an app-state vector.
(vector? (get-in state data-path))

I need some code example; if you can send a repo that I can clone and see the error on my end would be great!

It's currently 3:30 am in my timezone, so I'll do that during the day. :) It will take time, because this is a relatively big project.

No hurry ;)

I'm still in the process of making a minimal case, but it's clear to me now that it has something to do with ui routing. The number of copies of the error directly correlates to how many routes (recursively) there are as defined by r/defrouter.

@levitanong hello, I just pushed 2.0.0-alpha7-SNAPSHOT, the problem was that Fulcro is calling merge before the inspector has a chance to start. To fix it, now when inspect is ready (after app initialization is called) I add a flag to your app state to signal that. And then any calls to inspect-tx before that flag is set are going to be ignored. I hope this fixes the issue once for all. Please let me know it works properly with the new version. Thanks.

Works! Thanks @wilkerlucio!


i2c: RAM test improvements

Better support i2c ram tests by signaling that a driver supports RTIO (HAS_I2C_RTIO in Kconfig), and supporting power management in the test case.

@teburd  one enhancement on this, you can move the mimxrt1010_evk.overlay to app.overlay, in this way, all arudio compatible boards can use your apps without code change

@hakehuang I'm giving up on this app.overlay for now, if you have some ideas on how to resolve it please do send a PR but this change is holding up the rest with CI failures


Flutter desktop App gets crashed on first launch in windows 7

I built a sample app in windows 7 with flutter for windows and it gets crashed on first launch.
Here are logs of program
F:\Masood\my_app\my_app>flutter run -d windows Launching lib\main.dart on Windows in debug mode... Building Windows application... EGL: Failed to initializeEGL: Failed to initializeEGL: Failed to initializeEGL: Failed to initializeEGL: Failed to choose first context [FATAL:flutter/shell/gpu/gpu_surface_gl_delegate.cc(50)] Check failed: gl_version_string. The GL proc resolver's glGetString(GL_VERSION) failed Error connecting to the service protocol: _flutter.listViews: (-32000) Bad state: The client closed with pending request "_flutter.listViews".
flutter doctor -v output
[√] Flutter (Channel dev, 1.26.0-1.0.pre, on Microsoft Windows [Version 6.1.7601], locale en-US)
• Flutter version 1.26.0-1.0.pre at C:\Dev\flutter
• Framework revision 63062a6443 (3 weeks ago), 2020-12-13 23:19:13 +0800
• Engine revision 4797b06652
• Dart version 2.12.0 (build 2.12.0-141.0.dev)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at C:\Users\hasnain\AppData\Local\Android\Sdk
• Platform android-30, build-tools 30.0.3
• Java binary at: C:\Dev\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.8.3)
• Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
• Visual Studio Community 2019 version 16.8.30804.86
• Windows 10 SDK version 10.0.17763.0
[√] Android Studio (version 4.1.0)
• Android Studio at C:\Dev\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] VS Code (version 1.52.1)
• VS Code at C:\Users\hasnain\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.18.0
[√] Connected device (1 available)
• Windows (desktop) • windows • windows-x64 • Microsoft Windows [Version 6.1.7601]
• No issues found!
Outputs of flutter run -v
`[  +87 ms] executing: [C:\Dev\flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +70 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 63062a64432cce03315d6b5196fda7912866eb37
[   +1 ms] executing: [C:\Dev\flutter/] git tag --points-at 63062a64432cce03315d6b5196fda7912866eb37
[  +39 ms] Exit code 0 from: git tag --points-at 63062a64432cce03315d6b5196fda7912866eb37
[   +1 ms] 1.26.0-1.0.pre
[  +68 ms] executing: [C:\Dev\flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +24 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/dev
[        ] executing: [C:\Dev\flutter/] git ls-remote --get-url origin
[  +63 ms] Exit code 0 from: git ls-remote --get-url origin
[   +4 ms] https://github.com/flutter/flutter.git
[  +96 ms] executing: [C:\Dev\flutter/] git rev-parse --abbrev-ref HEAD
[  +28 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +1 ms] dev
[  +93 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +105 ms] executing: C:\Users\hasnain\AppData\Local\Android\Sdk\platform-tools\adb.exe devices -l
[  +35 ms] List of devices attached
[  +29 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +4 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +187 ms] Skipping pub get: version match.
[ +297 ms] Found plugin integration_test at C:\Dev\flutter\packages\integration_test
[ +358 ms] Found plugin integration_test at C:\Dev\flutter\packages\integration_test
[  +18 ms] Generating F:\Masood\my_app\my_app\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[ +164 ms] Initializing file store
[  +10 ms] Skipping target: gen_localizations
[   +6 ms] complete
[   +7 ms] Launching lib\main.dart on Windows in debug mode...
[  +10 ms] C:\Dev\flutter\bin\cache\dart-sdk\bin\dart.exe --disable-dart-dev
C:\Dev\flutter\bin\cache\artifacts\engine\windows-x64\frontend_server.dart.snapshot --sdk-root
C:\Dev\flutter\bin\cache\artifacts\engine\common\flutter_patched_sdk/ --incremental --target=flutter --debugger-module-names
--experimental-emit-debug-metadata --output-dill C:\Users\hasnain\AppData\Local\Temp\flutter_tools.33e7d99\flutter_tool.4f667730\app.dill --packages
F:\Masood\my_app\my_app.dart_tool\package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts --track-widget-creation
--filesystem-scheme org-dartlang-root --initialize-from-dill build\cache.dill.track.dill
[  +41 ms] executing: C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe -format json -products * -utf8 -latest -version 16 -require
Microsoft.VisualStudio.Workload.NativeDesktop Microsoft.VisualStudio.Component.VC.Tools.x86.x64 Microsoft.VisualStudio.Component.VC.CMake.Project
[  +19 ms] Exit code 0 from: C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe -format json -products * -utf8 -latest -version 16
-requires Microsoft.VisualStudio.Workload.NativeDesktop Microsoft.VisualStudio.Component.VC.Tools.x86.x64
Microsoft.VisualStudio.Component.VC.CMake.Project
[   +5 ms] [
{
"instanceId": "612ab6a3",
"installDate": "2020-12-08T08:51:14Z",
"installationName": "VisualStudio/16.8.3+30804.86",
"installationPath": "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community",
"installationVersion": "16.8.30804.86",
"productId": "Microsoft.VisualStudio.Product.Community",
"productPath": "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\devenv.exe",
"state":<PHONE_NUMBER>962648575,
"isComplete": true,
"isLaunchable": true,
"isPrerelease": false,
"isRebootRequired": false,
"displayName": "Visual Studio Community 2019",
"description": "Powerful IDE, free for students, open-source contributors, and individuals",
"channelId": "VisualStudio.16.Release",
"channelUri": "https://aka.ms/vs/16/release/channel",
"enginePath": "C:\Program Files (x86)\Microsoft Visual
Studio\Installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service",
"releaseNotes": "https://go.microsoft.com/fwlink/?LinkId=660893#16.8.3",
"thirdPartyNotices": "https://go.microsoft.com/fwlink/?LinkId=660909",
"updateDate": "2020-12-12T19:15:26.8682986Z",
"catalog": {
"buildBranch": "d16.8",
"buildVersion": "16.8.30804.86",
"id": "VisualStudio/16.8.3+30804.86",
"localBuild": "build-lab",
"manifestName": "VisualStudio",
"manifestType": "installer",
"productDisplayVersion": "16.8.3",
"productLine": "Dev16",
"productLineVersion": "2019",
"productMilestone": "RTW",
"productMilestoneIsPreRelease": "False",
"productName": "Visual Studio",
"productPatchVersion": "3",
"productPreReleaseMilestoneSuffix": "1.0",
"productSemanticVersion": "16.8.3+30804.86",
"requiredEngineVersion": "2.8.3267.30329"
},
"properties": {
"campaignId": "1158453142.1595257950",
"canceled": "0",
"channelManifestId": "VisualStudio.16.Release/16.8.3+30804.86",
"defaultProgram": "VisualStudio.612ab6a3",
"nickname": "",
"setupEngineFilePath": "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installershell.exe"
}
}
]
[   +8 ms] Building Windows application...
[  +17 ms] <- compile package:my_app/main.dart
[   +4 ms] executing: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe -
F:\Masood\my_app\my_app\windows -B build\windows -G Visual Studio 16 2019
[+3545 ms] -- Selecting Windows SDK version 10.0.17763.0 to target Windows 6.1.7601.
[ +908 ms] -- Configuring done
[+2157 ms] -- Generating done
[ +130 ms] -- Build files have been written to: F:/Masood/my_app/my_app/build/windows
[  +66 ms] executing: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe
--build build\windows --config Debug --target INSTALL --verbose
[+5324 ms] Microsoft (R) Build Engine version 16.8.2+25e4d540b for .NET Framework
[        ] Copyright (C) Microsoft Corporation. All rights reserved.
[+2333 ms] Build started 1/2/2021 11:40:44 PM.
[+5093 ms] Project "F:\Masood\my_app\my_app\build\windows\INSTALL.vcxproj" on node 1 (default targets).
[        ] Project "F:\Masood\my_app\my_app\build\windows\INSTALL.vcxproj" (1) is building "F:\Masood\my_app\my_app\build\windows\ZERO_CHECK.vcxproj"
(2) on node 1 (default targets).
[   +1 ms] InitializeBuildStatus:
[        ]   Creating "x64\Debug\ZERO_CHECK\ZERO_CHECK.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[ +400 ms] CustomBuild:
[        ]   All outputs are up-to-date.
[ +280 ms] FinalizeBuildStatus:
[        ]   Deleting file "x64\Debug\ZERO_CHECK\ZERO_CHECK.tlog\unsuccessfulbuild".
[   +1 ms]   Touching "x64\Debug\ZERO_CHECK\ZERO_CHECK.tlog\ZERO_CHECK.lastbuildstate".
[   +9 ms] Done Building Project "F:\Masood\my_app\my_app\build\windows\ZERO_CHECK.vcxproj" (default targets).
[ +280 ms] Project "F:\Masood\my_app\my_app\build\windows\INSTALL.vcxproj" (1) is building "F:\Masood\my_app\my_app\build\windows\ALL_BUILD.vcxproj" (
on node 1 (default targets).
[   +1 ms] Project "F:\Masood\my_app\my_app\build\windows\ALL_BUILD.vcxproj" (3) is building
"F:\Masood\my_app\my_app\build\windows\flutter\flutter_wrapper_app.vcxproj" (4) on node 1 (default targets).
[   +1 ms] Project "F:\Masood\my_app\my_app\build\windows\flutter\flutter_wrapper_app.vcxproj" (4) is building
"F:\Masood\my_app\my_app\build\windows\flutter\flutter_assemble.vcxproj" (5) on node 1 (default targets).
[  +25 ms] InitializeBuildStatus:
[        ]   Creating "x64\Debug\flutter_assemble\flutter_assemble.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[  +66 ms] CustomBuild:
[   +5 ms]   "The build of 'F:\Masood\my_app\my_app\build\windows\CMakeFiles\4c704b714a40d7fced27fda7ad7312a3\flutter_assemble.rule' depends on
'F:\MASOOD\MY_APP\MY_APP\WINDOWS\FLUTTER\EPHEMERAL\FLUTTER_WINDOWS.DLL' which is produced by the build of
'F:\Masood\my_app\my_app\build\windows\CMakeFiles\d4eb395f1eaf9a7d75c75644cd6360f3\flutter_windows.dll.rule'. The items cannot be built in parallel."
[+2555 ms]   Generating F:/Masood/my_app/my_app/windows/flutter/ephemeral/flutter_windows.dll,
F:/Masood/my_app/my_app/windows/flutter/ephemeral/flutter_export.h, F:/Masood/my_app/my_app/windows/flutter/ephemeral/flutter_windows.h,
F:/Masood/my_app/my_app/windows/flutter/ephemeral/flutter_messenger.h, F:/Masood/my_app/my_app/windows/flutter/ephemeral/flutter_plugin_registrar.h,
F:/Masood/my_app/my_app/windows/flutter/ephemeral/cpp_client_wrapper/core_implementations.cc,
F:/Masood/my_app/my_app/windows/flutter/ephemeral/cpp_client_wrapper/standard_codec.cc,
F:/Masood/my_app/my_app/windows/flutter/ephemeral/cpp_client_wrapper/plugin_registrar.cc,
F:/Masood/my_app/my_app/windows/flutter/ephemeral/cpp_client_wrapper/flutter_engine.cc,
F:/Masood/my_app/my_app/windows/flutter/ephemeral/cpp_client_wrapper/flutter_view_controller.cc, phony
[+13841 ms]   [  +88 ms] executing: [C:\Dev\flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[+1407 ms]   [+1450 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +2 ms]   [   +2 ms] 63062a64432cce03315d6b5196fda7912866eb37
[        ]   [   +1 ms] executing: [C:\Dev\flutter/] git tag --points-at 63062a64432cce03315d6b5196fda7912866eb37
[+2402 ms]   [+2402 ms] Exit code 0 from: git tag --points-at 63062a64432cce03315d6b5196fda7912866eb37
[        ]   [        ] 1.26.0-1.0.pre
[  +63 ms]   [  +64 ms] executing: [C:\Dev\flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +86 ms]   [  +85 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[  +13 ms]   [        ] origin/dev
[   +1 ms]   [        ] executing: [C:\Dev\flutter/] git ls-remote --get-url origin
[  +24 ms]   [  +39 ms] Exit code 0 from: git ls-remote --get-url origin
[   +1 ms]   [        ] https://github.com/flutter/flutter.git
[ +118 ms]   [ +118 ms] executing: [C:\Dev\flutter/] git rev-parse --abbrev-ref HEAD
[  +41 ms]   [  +42 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +1 ms]   [        ] dev
[ +207 ms]   [ +208 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[  +16 ms]   [  +17 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[+2185 ms]   [+2177 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'PubDependencies' is not required, skipping update.
[ +162 ms]   [ +179 ms] Initializing file store
[  +56 ms]   [  +56 ms] Done initializing file store
[ +221 ms]   [ +220 ms] Skipping target: gen_localizations
[+8320 ms]   [+8318 ms] Skipping target: unpack_windows
[+5221 ms]   [+5222 ms] Skipping target: kernel_snapshot
[+1406 ms]   [+1405 ms] Skipping target: debug_bundle_windows_assets
[        ]   [   +1 ms] Persisting file store
[  +81 ms]   [  +82 ms] Done persisting file store
[  +28 ms]   [  +28 ms] build succeeded.
[ +103 ms]   [ +104 ms] "flutter assemble" took 17,751ms.
[ +261 ms]   [ +260 ms] ensureAnalyticsSent: 255ms
[   +3 ms]   [   +3 ms] Running shutdown hooks
[   +1 ms]   [        ] Shutdown hooks complete
[   +1 ms]   [   +1 ms] exiting with code 0
[ +488 ms] FinalizeBuildStatus:
[   +1 ms]   Deleting file "x64\Debug\flutter_assemble\flutter_assemble.tlog\unsuccessfulbuild".
[   +1 ms]   Touching "x64\Debug\flutter_assemble\flutter_assemble.tlog\flutter_assemble.lastbuildstate".
[        ] Done Building Project "F:\Masood\my_app\my_app\build\windows\flutter\flutter_assemble.vcxproj" (default targets).
[ +142 ms] InitializeBuildStatus:
[   +1 ms]   Creating "flutter_wrapper_app.dir\Debug\flutter_.AC502B6C.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[  +68 ms] CustomBuild:
[   +1 ms]   All outputs are up-to-date.
[ +540 ms] ClCompile:
[        ]   All outputs are up-to-date.
[ +254 ms] Lib:
[   +1 ms]   All outputs are up-to-date.
[  +63 ms]   flutter_wrapper_app.vcxproj -> F:\Masood\my_app\my_app\build\windows\flutter\Debug\flutter_wrapper_app.lib
[  +71 ms] FinalizeBuildStatus:
[        ]   Deleting file "flutter_wrapper_app.dir\Debug\flutter_.AC502B6C.tlog\unsuccessfulbuild".
[   +1 ms]   Touching "flutter_wrapper_app.dir\Debug\flutter_.AC502B6C.tlog\flutter_wrapper_app.lastbuildstate".
[   +1 ms] Done Building Project "F:\Masood\my_app\my_app\build\windows\flutter\flutter_wrapper_app.vcxproj" (default targets).
[ +583 ms] Project "F:\Masood\my_app\my_app\build\windows\ALL_BUILD.vcxproj" (3) is building
"F:\Masood\my_app\my_app\build\windows\flutter\flutter_wrapper_plugin.vcxproj" (6) on node 1 (default targets).
[  +34 ms] InitializeBuildStatus:
[  +18 ms]   Creating "flutter_wrapper_plugin.dir\Debug\flutter_.56295CB0.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[   +2 ms] CustomBuild:
[   +2 ms]   All outputs are up-to-date.
[  +33 ms] ClCompile:
[        ]   All outputs are up-to-date.
[  +76 ms] Lib:
[   +1 ms]   All outputs are up-to-date.
[   +8 ms]   flutter_wrapper_plugin.vcxproj -> F:\Masood\my_app\my_app\build\windows\flutter\Debug\flutter_wrapper_plugin.lib
[   +9 ms] FinalizeBuildStatus:
[        ]   Deleting file "flutter_wrapper_plugin.dir\Debug\flutter_.56295CB0.tlog\unsuccessfulbuild".
[        ]   Touching "flutter_wrapper_plugin.dir\Debug\flutter_.56295CB0.tlog\flutter_wrapper_plugin.lastbuildstate".
[        ] Done Building Project "F:\Masood\my_app\my_app\build\windows\flutter\flutter_wrapper_plugin.vcxproj" (default targets).
[ +193 ms] Project "F:\Masood\my_app\my_app\build\windows\ALL_BUILD.vcxproj" (3) is building
"F:\Masood\my_app\my_app\build\windows\runner\my_app.vcxproj" (7) on node 1 (default targets).
[   +2 ms] InitializeBuildStatus:
[        ]   Creating "my_app.dir\Debug\my_app.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[  +78 ms] CustomBuild:
[        ]   All outputs are up-to-date.
[ +272 ms] ClCompile:
[        ]   C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.28.29333\bin\HostX64\x64\CL.exe /c
/IF:\Masood\my_app\my_app\windows /IF:\Masood\my_app\my_app\windows\flutter\ephemeral
/IF:\Masood\my_app\my_app\windows\flutter\ephemeral\cpp_client_wrapper\include /Zi /nologo /W4 /WX /diagnostics:column /Od /Ob0 /D WIN32 /D _WINDOWS /
_HAS_EXCEPTIONS=0 /D _DEBUG /D NOMINMAX /D UNICODE /D _UNICODE /D "CMAKE_INTDIR="Debug"" /D _UNICODE /D UNICODE /Gm- /EHsc /RTC1 /MDd /GS /fp:precis
/Zc:wchar_t /Zc:forScope /Zc:inline /GR /std:c++17 /Fo"my_app.dir\Debug\" /Fd"my_app.dir\Debug\vc142.pdb" /Gd /TP /wd4100 /errorReport:queue
F:\Masood\my_app\my_app\windows\flutter\generated_plugin_registrant.cc F:\Masood\my_app\my_app\windows\runner\flutter_window.cpp
[+1115 ms]   generated_plugin_registrant.cc
[+2925 ms]   flutter_window.cpp
[+3914 ms]   Generating Code...
[ +949 ms] ResourceCompile:
[        ]   All outputs are up-to-date.
[+1165 ms] Link:
[        ]   C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.28.29333\bin\HostX64\x64\link.exe /ERRORREPORT:QUEUE
/OUT:"F:\Masood\my_app\my_app\build\windows\runner\Debug\my_app.exe" /INCREMENTAL /NOLOGO ..\flutter\Debug\flutter_wrapper_app.lib
F:\Masood\my_app\my_app\windows\flutter\ephemeral\flutter_windows.dll.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib
oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /manifest:embed
/manifestinput:F:\Masood\my_app\my_app\windows\runner\runner.exe.manifest /DEBUG /PDB:"F:/Masood/my_app/my_app/build/windows/runner/Debug/my_app.pdb"
/SUBSYSTEM:WINDOWS /TLBID:1 /DYNAMICBASE /NXCOMPAT /IMPLIB:"F:/Masood/my_app/my_app/build/windows/runner/Debug/my_app.lib" /MACHINE:X64  /machine:x64
my_app.dir\Debug\Runner.res
[   +2 ms]   my_app.dir\Debug\flutter_window.obj
[        ]   my_app.dir\Debug\main.obj
[        ]   my_app.dir\Debug\run_loop.obj
[        ]   my_app.dir\Debug\utils.obj
[        ]   my_app.dir\Debug\win32_window.obj
[        ]   my_app.dir\Debug\generated_plugin_registrant.obj
[+2161 ms]   my_app.vcxproj -> F:\Masood\my_app\my_app\build\windows\runner\Debug\my_app.exe
[  +84 ms] FinalizeBuildStatus:
[        ]   Deleting file "my_app.dir\Debug\my_app.tlog\unsuccessfulbuild".
[        ]   Touching "my_app.dir\Debug\my_app.tlog\my_app.lastbuildstate".
[        ] Done Building Project "F:\Masood\my_app\my_app\build\windows\runner\my_app.vcxproj" (default targets).
[  +28 ms] InitializeBuildStatus:
[        ]   Creating "x64\Debug\ALL_BUILD\ALL_BUILD.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[ +175 ms] CustomBuild:
[        ]   All outputs are up-to-date.
[  +18 ms] FinalizeBuildStatus:
[        ]   Deleting file "x64\Debug\ALL_BUILD\ALL_BUILD.tlog\unsuccessfulbuild".
[   +1 ms]   Touching "x64\Debug\ALL_BUILD\ALL_BUILD.tlog\ALL_BUILD.lastbuildstate".
[   +1 ms] Done Building Project "F:\Masood\my_app\my_app\build\windows\ALL_BUILD.vcxproj" (default targets).
[  +38 ms] InitializeBuildStatus:
[   +2 ms]   Creating "x64\Debug\INSTALL\INSTALL.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[ +315 ms] PostBuildEvent:
[        ]   setlocal
[        ]   "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe"
-DBUILD_TYPE=Debug -P cmake_install.cmake
[   +1 ms]   if %errorlevel% neq 0 goto :cmEnd
[        ]   :cmEnd
[        ]   endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
[        ]   :cmErrorLevel
[        ]   exit /b %1
[        ]   :cmDone
[        ]   if %errorlevel% neq 0 goto :VCEnd
[   +1 ms]   :VCEnd
[ +486 ms]   -- Install configuration: "Debug"
[  +28 ms]   -- Up-to-date: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/icudtl.dat
[   +1 ms]   -- Up-to-date: F:/Masood/my_app/my_app/build/windows/runner/Debug/flutter_windows.dll
[ +217 ms]   -- Installing: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/flutter_assets
[   +5 ms]   -- Installing: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/flutter_assets/AssetManifest.json
[        ]   -- Installing: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/flutter_assets/FontManifest.json
[        ]   -- Installing: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/flutter_assets/fonts
[        ]   -- Installing: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/flutter_assets/fonts/MaterialIcons-Regular.otf
[   +2 ms]   -- Installing: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/flutter_assets/kernel_blob.bin
[  +98 ms]   -- Installing: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/flutter_assets/NOTICES
[   +2 ms]   -- Installing: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/flutter_assets/packages
[        ]   -- Installing: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/flutter_assets/packages/cupertino_icons
[   +1 ms]   -- Installing: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/flutter_assets/packages/cupertino_icons/assets
[        ]   -- Installing: F:/Masood/my_app/my_app/build/windows/runner/Debug/data/flutter_assets/packages/cupertino_icons/assets/CupertinoIcons.ttf
[  +56 ms] FinalizeBuildStatus:
[   +1 ms]   Deleting file "x64\Debug\INSTALL\INSTALL.tlog\unsuccessfulbuild".
[   +3 ms]   Touching "x64\Debug\INSTALL\INSTALL.tlog\INSTALL.lastbuildstate".
[   +3 ms] Done Building Project "F:\Masood\my_app\my_app\build\windows\INSTALL.vcxproj" (default targets).
[ +113 ms] Build succeeded.
[  +14 ms]     0 Warning(s)
[        ]     0 Error(s)
[  +67 ms] Time Elapsed 00:01:02.01
[ +715 ms] Building Windows application... (completed in 77.2s)
[+4697 ms] EGL: Failed to initializeEGL: Failed to initializeEGL: Failed to initializeEGL: Failed to initializeEGL: Failed to choose first context
[ +411 ms] [FATAL:flutter/shell/gpu/gpu_surface_gl_delegate.cc(50)] Check failed: gl_version_string. The GL proc resolver's glGetString(GL_VERSION)
failed
[ +683 ms] Observatory URL on device: http://<IP_ADDRESS>:51088/D52ZrEbCFHc=/
[   +9 ms] Caching compiled dill
[ +448 ms] Connecting to service protocol: http://<IP_ADDRESS>:51088/D52ZrEbCFHc=/
[   +5 ms] Launching a Dart Developer Service (DDS) instance at http://<IP_ADDRESS>:0, connecting to VM service at http://<IP_ADDRESS>:51088/D52ZrEbCFHc=/.
[ +857 ms] DDS is listening at http://<IP_ADDRESS>:51092/VUICdRI51Rk=/.
[ +211 ms] Successfully connected to service protocol: http://<IP_ADDRESS>:51088/D52ZrEbCFHc=/
[+7321 ms] Error connecting to the service protocol: _flutter.listViews: (-32000) Bad state: The client closed with pending request
"_flutter.listViews".
[  +10 ms] "flutter run" took 93,235ms.
[  +16 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:623:7)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1134:12)

#3      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:986:27)

#4      AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#5      AppContext.run (package:flutter_tools/src/base/context.dart:149:12)

#6      CommandRunner.runCommand (package:args/command_runner.dart:197:13)

#7      FlutterCommandRunner.runCommand. (package:flutter_tools/src/runner/flutter_command_runner.dart:274:9)

#8      AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#9      AppContext.run (package:flutter_tools/src/base/context.dart:149:12)

#10     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:230:5)

#11     run.. (package:flutter_tools/runner.dart:63:9)

#12     run. (package:flutter_tools/runner.dart:61:12)

#13     AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#14     AppContext.run (package:flutter_tools/src/base/context.dart:149:12)

#15     runInContext (package:flutter_tools/src/context_runner.dart:70:10)

#16     main (package:flutter_tools/executable.dart:88:3)

[ +256 ms] ensureAnalyticsSent: 252ms
[   +2 ms] Running shutdown hooks
[   +1 ms] Shutdown hook priority 4
[   +9 ms] Shutdown hooks complete
[   +2 ms] exiting with code 2`

Duplicate of https://github.com/flutter/flutter/issues/73040
Could you provide the details of your graphics card and driver in that issue?

Duplicate of https://github.com/flutter/flutter/issues/73040
Could you provide the details of your graphics card and driver in that issue?

Graphics details

Graphics details


Test for Matthieu

First make sure you read the test guidelines here: https://github.com/Wiredcraft/test-pm
This task will be followed up asynchronously over a few days and should not take more than two hours in total.
Project Introduction
You have been assigned as project manager for a project for the client Chopper Corp (your client stakeholder is Charlie ). The outcome of this project will be a website which allows a user to sign up, and log-in to a system that gives them commodity prices and availability information. The system as a whole is expected in 7 weeks.
Project Details
The work has been divided into two parts:
• the backend and frontend for login and signup - This will be handled by Wiredcraft completely
• the backend and frontend for commodity prices and availability information which will be provided by a separate company Shane Labs, you will need to interface with Yiwan, their project manager, to coordinate as they are building this system from scratch for Chopper Corp.
The specific requirements for the registration have been decided as Username, Password and Email address fields. The login will be based on username. And after sign up the commodity prices and availability information system expects to receive the Username and Email so they can customise the information.
In your team you have:
• A designer who can make mockups and flow diagrams of the login and once confirmed, implement the frontend
• A developer who can implement the backend and help out integrating the login frontend
• A dev-ops engineer who can set up the servers and take care of deployment.
Your Task
The first step of this task is for you to provide the following:
• Clarify the requirements and provide your understanding of the final scope for Wiredcraft's work.
• An initial project plan including:

A work breakdown for Wiredcraft's integration with Shane Labs up to the final delivery
a rough timeline of what you think needs to happen in this project and deliverables. You can use the methodology of your choice for this plan,
Outline the project phases you would have and what should be delivered at each phase.
The plan can be a few paragraphs of text and the timeline can also be made using Github markdown by outlining what needs to be done during each week.
A rough outline of the process you would use for the day-to-day organisation of the development team and a short overview of how you would manage the communication flows internally and externally.

You can also kick off with any questions to multiple people in one GitHub comment, I will answer likewise and bring up more cases to test your communication skills as we go along:
(Assume you have already been introduced to the client (@ccCharlie111) and commodity prices and availability service vendor (@slYiwan222) ) and you can @myteam333 for questions to your development team)
e.g.
@slYiwan222222 - Hi there, can I confirm with you the requirements for ...
@ccCharlie111 - I heard from slYiwan222222 that they need to have xxx, does that mean we need to change ....
@myteam333 - I'm not clear on how xxx could work, can you tell me more about it?
@mpathiuk - For the test, I don't understand what you mean by xxx ...

Hi Mik, I understand that in this business case, Wiredcraft is to develop and deliver the sign-up and login services for an e-commerce website. The client (Chopper Inc. represented by Charlie) also works with one external party (Shane Labs represented by Yiwan) that is in charge of the other functionalities (display commodity prices and availabilities) and which whom we have to collaborate with (in particular to guarantee the customisation of the shopping experience).
I also understand that the project timeframe is 7 weeks, and that we are a 4 people team including the project manager, a designer, a developer, and a dev-ops engineer. I assume that my team has to deliver a validated version of the project in a staging environment.
At this stage I have a few questions regarding the business case:

do you confirm that the 7 weeks term is to deliver the development in a staging environment, or do I assume the 7 weeks term is for an online version?
who will be managing the client's database, Wiredcraft or Shane Labs or the client?
who is responsible for the graphical charter or the template? Do I assume we are given one
what is the budget for this project? How many days can each team member allocate to this project?

After this first read, I would certainly recommend the following steps for this projects:
During week 1:

kick-off and preparation,

have a call or meeting with Charlie to confirm the scope and requirements of the projects (in particular: which devices, which formats) and get to know each other
brief to the team and gathering of the first questions (probably the developer will have questions about the technical environment, the requirements for sending the login information for customization, the platforms and environments were the website will be in production etc.)
have a call or meeting between Wiredraft team, Charlie and Shane Labs team to confirm the scope, requirements, and constraints of the project, the level and areas of involvement of the different parties, ask our questions and get to know each other
in the same time, dev-ops sets ups the servers and working environment (according to Wiredcraft internal guidelines - I would recommend a development environment, an internal staging environment for internal testing)

specifications and next steps

as soon as the preparation steps are concluded, I will be able to document a roadmap for the project that can be validated by the team and shared with the client and a memo for every meeting. The developer will be able to write a detailed work plan and the designer to prepare the mock-ups and templates
I will start building a detailed calendar and task list for the following weeks.

Guidelines for the following weeks
I guess the development phase will have two major aspects: the login and sign-up modules, the connexion with Shane Labs's platform. I think after week 1 and coordination with the developer, we will probably get to a work plan like the following:
week 2

DEV: back-end development (login and sign-up+send information to Shane Labs)
DESIGN: template design =>DELIVERABLE : templates
PM: share front-end templates with Charlie

week 3

DEV: => DELIVERABLE: back-office in the internal testing environment
DESIGN: include Charlie's comments if any DELIVERABLE: validated templates

week 4

frontend development
frontend desktop integration
DELIVERABLE: frontend in the internal testing environment

week 5

front end mobile integration
internal testing
testing of the webservices with Shane Labs

week 6

internal testing
testing of the webservices with Shane Labs
release in the client's staging environment

week 7

testing by the client

Regarding communication flows:

internally,
-- I would set-up a chat channel, and would talk to the team on a daily basis
-- I would use a task manager (GitHub issues) to share any information from the client with the team and follow the tasks of the team
externally
-- during production phase, I will inform the client on a regular basis by phone or email, following the initial workplan, and ask for his feedback or confirmation when need (use username as login, frontend designs)
-- during the testing phase, I will be in a close relationship with the client to make sure he testes the deliverables and to acknowledge and deal with every feedback Charlie will give us

From me:

do you confirm that the 7 weeks term is to deliver the development in a staging environment, or do I assume the 7 weeks term is set to deliver an online production version?

7 weeks to staging, as you have assumed.

who will be managing the client's database, Wiredcraft or Shane Labs or the client?
The Client

who is responsible for the graphical charter or the template? Do I assume we are given one?
We are and your designer can handle this with the client directly

what is the budget for this project? How many days can each team member allocate to this project?
Assume that the team is on this full time and the budget and contracts are already taken care of.

Your plan is in progress and it's now week 2.
From Shane Labs slyiwan222222 : Hi @matthieumellul , we've just realised that due to new legal registrations, we will require you to pass us the user's phone number as well, and this will need to be validated by SMS.
Can you let us know if this is doable within the timeframe or will need to come in a post-release fix?
After discussion with your team they come back to you:
From: myteam333 adding SMS validation would add 3 weeks to the project, so we recommend delivering this feature 3 weeks after the initially planned release.
What are the next steps you would take in this case?

Hi Mik,
I would do the following :
the very day:

confirm the new specifications : quick check the new regulation to confirm if the issue raised by Shane Labs is relevant, how critical is it and if there is a way around it. If there is reasonable doubt, contact Shane Labs to challenge and confirm the specifications.

prepare a recommandation for the client: if we have to integrate the new specifications I would check the potential impact it has on going live. I would first do a quick check with the team to understand why this new feature takes three weeks to be developped, and find if we can provide any internal solution: shorten the three weeks period or add extra workforce to deliver the project without changing to deadline. Then I would evaluate a budget for each reasonable option we can propose.

inform the client of the situation, of its options and associated costs. I assume the client will share with me the business implications of a delay. Then I will confirm with the client the best option regarding its time and budget constraints.

debrief with the team and update the planning and task lists according to the conclusion reached with the client.

inform Shane Labs of the release date for the new feature in the staging environment

You get the go ahead from the client for the SMS validation release 3 weeks after the initial release. Your team then proceeds with your plan for a few more weeks.
You're now in week 4 and your team tells you that due to unforeseen technical circumstances as well as some small changes that need to be made to support the SMS validation release they will not have the frontend finished for testing by the end of this week as planned. It will take one extra week. This would also push back the SMS validation release by 1 week.
What do you do now.

Hi Mik,
as you can see on the workplan, I have initially planned a quite long internal testing period (about 30% of the total time) which allows some flexibility for the team before impacting the deadline for the client. Experience tells that it is always safer to be able to deal with some unexpected or unforseen issue.
What I would do at this stage :
internally
I would keep pressure on the team, and advocate to do our best to stick to the initial planning. I would in particular advocate that we have to start dealing with this new issue before confirming to the client that we have to push back the SMS validation release by 1 week - changing our own initial assement is a last resort measure, because it can impact negatively our position in future situations.
As a consequence, I will adapt the internal planning and plan for a status meeting by the middle of week 5. But I will not change the release deadline of the staging version.
I believe people often overestimate the difficulty of something they don't know, and things can turn out to be solved quicker than expected. At this stage I want to preserve this possibility, as much as to keep the team working, and with a positive spirit. However, I will also have to confirm with the team if they need help, to make sure that the eventual one week delay could not turn into a two weeks delay or more ; I will also have to evaluate the possibility of a partial release on staging.
with the client
At the same time, I have to prepare for the situation were the staging release would actually be delayed. So I'll start to share our concerns with the client, by phone if possible, mentioning that the development of the SMS validation step requires modifications on the other parts of the project that can affect the deadline of the release version. I'll assess the potential impact on the client if we have to postpone the release of the front end in staging (are their business consequences ? does he or do is team would still be available for testing if we have to postpone the release of the front end in the staging environment by one week?).
Conequently to this internal and external actions, on week five, I'll have a clearer ability to asses the situation and communicate it to the client.

You're in week 7 development and testing is now completed. You are about to launch the first version without SMS validation when the client raises the question:
"What do we do with users who sign up between now and the launch of SMS validation? We have the legal requirement to get the SMS for all users by 4 weeks time"
Assuming they will be ok with the budget for any upcoming work for your solution, what would you suggest?

Hi would ask you for advice :) And I will suggest to give ourself 3 days to confirm the date of launching.
Since the initially 7 weeks project period was planned for a delivery in a staging environment, I assumed the launch was not set yet.
At this point, I would suggest that we explore all available options to be ready as soon as possible to go live, being legally compliant. I would strongly recommand not to go live without the SMS validation feature.
Since we need 3 weeks to develop the feature, this left us only 1 week to test and go live, which I would think its too short. We don't want to release a feature that can compromise the users login experience on the first days of the service being live. However, I understand the client might have some business and marketing related issues, and needs to launch at a certain date as soon as possible.
During the 3 days I would:

confirm internaly if we can include and if we have extra people available to speed up the development of the SMS feature and evaluate our shortest possible launch date.
explore the possibility of recruiting a reliable third party that would provide the SMS validation service so that we can go live sooner. Our team would need to connect and test a webservice for this third party before going live, and develop, test and release our feature after. This might enable us to keep up with a tight launch deadline.
ask Charlie to confirm with the stakeholders on his side its constraints for the launch date

After the three days, meet with Charlie and confirm the launch date.

Thanks @matthieumellul We have enough information from the test. Closing as done and we'll be in touch.