No file format header found (Build Step/Nuget restore)

Hello, I followed the article:
https://msdn.microsoft.com/Library/vs/alm/Build/azure/deploy-aspnet5
I am getting "No file format header found."
Executing the powershell script: C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\tasks\VSBuild\1.0.15\VSBuild.ps1
2015-09-22T09:51:03.4563485Z C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agent\worker\tools\NuGet.exe restore "C:\a\ce1f12e0\Trucko Demo\src\TruckoDemo\TruckoDemo.xproj" -NonInteractive
2015-09-22T09:51:04.4097630Z ##[error]No file format header found.

Having the same issue. It looks to be related to Nuget more than VSO. if you run the command line locally against a xproj you get the same error. If anyone has a solution please advise

I got the same:
No file format header found. Unexpected exit code 1 returned from tool NuGet.exe

You can't run nuget restore against anything other than an SLN file.

@omarpando you should uncheck restore nuget packages on that vsbuild task.

@chrisrpatterson's solution worked for me

Chris, should we add some validation/advisement to the task?

Getting now  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.DNX.PackageManager' or one of its dependencies. The system cannot find the file specified.
global.json
{
  "projects": [ "src", "test" ],
  "sdk": {
    "version": "1.0.0-beta7",
    "runtime": "clr"
  }
}

Restore NuGet Packages uncheked

2015-09-24T00:17:20.3383841Z          C:\Users\buildguest\.dnx\runtimes\dnx-clr-win-x<IP_ADDRESS>-beta7\bin\dnx.exe --appbase "C:\a\96aede60\NewApp\src\NewApp" "C:\Users\buildguest\.dnx\runtimes\dnx-clr-win-x<IP_ADDRESS>-beta7\bin\lib\Microsoft.DNX.PackageManager\Microsoft.DNX.PackageManager.dll" pack "C:\a\96aede60\NewApp\src\NewApp" --configuration debug --out "..\..\artifacts\bin\NewApp"
2015-09-24T00:17:21.2932077Z          System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.DNX.PackageManager' or one of its dependencies. The system cannot find the file specified.
2015-09-24T00:17:21.2952067Z          File name: 'Microsoft.DNX.PackageManager'
2015-09-24T00:17:21.2962076Z             at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)

Did you restore you dnx packages? Msbuild I'd not going to do that for you and because dnx is in such early beta there is no oob support for it in the version of NuGet installed with the build agent.
Sent from my Windows Phone

From: Omar Alvarez<EMAIL_ADDRESS>Sent: 9/23/2015 8:38 PM
To<EMAIL_ADDRESS>Cc: Chris<EMAIL_ADDRESS>Subject: Re: [vso-agent-tasks] No file format header found (Build Step/Nuget restore) (#571)
Getting now System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.DNX.PackageManager' or one of its dependencies. The system cannot find the file specified.
global.json
{
"projects": [ "src", "test" ],
"sdk": {
"version": "1.0.0-beta7",
"runtime": "clr"
}
}
Restore NuGet Packages uncheked
[build]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcloud.githubusercontent.com%2Fassets%2F1749353%2F10062653%2Fe1a1b7ee-6232-11e5-88cf-59935ca1ff8b.JPG&data=01|01|Chris.Patterson%40microsoft.com|2755e13441c54a2c69a508d2c478625b|72f988bf86f141af91ab2d7cd011db47|1&sdata=6J76lIuqnoQOKkcIHLVj2GOi1D3dO5EljZERNv7V44g%3D
2015-09-24T00:17:20.3383841Z          C:\Users\buildguest.dnx\runtimes\dnx-clr-win-x<IP_ADDRESS>-beta7\bin\dnx.exe --appbase "C:\a\96aede60\NewApp\src\NewApp" "C:\Users\buildguest.dnx\runtimes\dnx-clr-win-x<IP_ADDRESS>-beta7\bin\lib\Microsoft.DNX.PackageManager\Microsoft.DNX.PackageManager.dll" pack "C:\a\96aede60\NewApp\src\NewApp" --configuration debug --out "....\artifacts\bin\NewApp"
2015-09-24T00:17:21.2932077Z          System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.DNX.PackageManager' or one of its dependencies. The system cannot find the file specified.
2015-09-24T00:17:21.2952067Z          File name: 'Microsoft.DNX.PackageManager'
2015-09-24T00:17:21.2962076Z             at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
—
Reply to this email directly or view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvso-agent-tasks%2Fissues%2F571%23issuecomment-142769091&data=01|01|Chris.Patterson%40microsoft.com|2755e13441c54a2c69a508d2c478625b|72f988bf86f141af91ab2d7cd011db47|1&sdata=OKxg5kUae3lfW9vzY3%2Fof3%2B%2F2tmgch5KTL1yWKaz73o%3D.

Yeah had the same issue. Had to step back to beta5. With the and unchecking restore nuget packages  I was able to get a build going. Now debugging the Publish build artifacts

I'm having the same problem with a .csproj file.
Is there a way with VSO to restore the packages and build the .csproj without build the entire solution?

I too followed the same article to get a VSO build set up for a DNX Beta7 project, and I'm now getting the same System.IO.FileNotFoundException for Microsoft.DNX.PackageManager. @chrisrpatterson the Prebuild.ps1 task does the dnu restore for any project.json files in the solution so this should already have been done before msbuild is called. @DarcSlate any idea why moving back to Beta5 worked for you? I had this all working for Beta6 and only recently started getting this issue.

Having done some more research I believe the issue is caused by the fact that the Hosted build agent in VSO does not have the latest "ASP.NET and Web Tools" version installed https://github.com/aspnet/dnx/issues/2426 @omarpando did you ever find a solution?

I just hit this error preventing me from moving to the new build definitions.

I got the same error and it got resolved by unchecking the options "Restore NuGet Packages” and “Clean” in MS Build step of the definition.

@phanibitla you beat me to it. I did exactly that. Is there a reason to ever have that checked for a .ccproj?

No, Nuget restore only works for solutions.
From: praneetloke <notifications<EMAIL_ADDRESS>Reply-To: Microsoft/vso-agent-tasks <reply<EMAIL_ADDRESS>Date: Wednesday, October 21, 2015 at 7:28 PM
To: Microsoft/vso-agent-tasks <vso-agent-tasks<EMAIL_ADDRESS>Cc: Chris Patterson <Chris.Patterson<EMAIL_ADDRESS>Subject: Re: [vso-agent-tasks] No file format header found (Build Step/Nuget restore) (#571)
@phanibitlahttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fphanibitla&data=01|01|Chris.Patterson%40microsoft.com|92db5eda171343fd7e3008d2da6f6523|72f988bf86f141af91ab2d7cd011db47|1&sdata=Dgu8Oi72IjOJnYNytawiy%2B3eSzhKO1uNjPJTgEMPnzw%3D you beat me to it. I did exactly that. Is there a reason to ever have that checked for a .ccproj?
—
Reply to this email directly or view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvso-agent-tasks%2Fissues%2F571%23issuecomment-150053321&data=01|01|Chris.Patterson%40microsoft.com|92db5eda171343fd7e3008d2da6f6523|72f988bf86f141af91ab2d7cd011db47|1&sdata=OCgCV56WFOx1koei6%2BRWDHufJ1WMHIh5%2BpG0Vzykn3Q%3D.

NuGet restore also works with packages.config files. This command restores the packages defined in the config file to the specified output directory.
`nuget.exe restore .\pathto\packages.config -packagesdirectory .\pathto\outputdir

To confirm, if I am building a cloud service in VSTS (using Visual Studio Online and hosted build agents):

I need to uncheck Restore NuGet Packages option in the Build Definition?
and I have to have all nuget packages in packages folder checked in, to have the referenced dll files available for the build agents?

Thanks,
Serge

NuGet restore only works against a solution file.  I would recommend you run the NuGet task on your solution file and then build your cloud service package targeting your .ccproj file.  The Cloud Service Deployment template is a great place to start as it sets everything up for you.
From: Sergiy Cherevko<EMAIL_ADDRESS>Sent: Friday, December 4, 2015 4:31 PM
To: Microsoft/vso-agent-tasks<EMAIL_ADDRESS>Cc: Chris Patterson<EMAIL_ADDRESS>Subject: Re: [vso-agent-tasks] No file format header found (Build Step/Nuget restore) (#571)
To confirm, if I am building a cloud service in VSTS (using Visual Studio Online and hosted build agents):

I need to uncheck Restore NuGet Packages option in the Build Definition?
and I have to have all nuget packages in packages folder checked in, to have the referenced dll files available for the build agents?

Thanks,
Serge
—
Reply to this email directly or view it on GitHubhttps://github.com/Microsoft/vso-agent-tasks/issues/571#issuecomment-162086917.

@dac-scherevko as @chrisrpatterson mentioned, have the Nuget resotre enabled for the .sln build step but unchecked for the .ccproj build step.

Thanks  @chrisrpatterson and @praneetloke! That helped.
However, there is one thing I cannot explain: if I create a new cloud service solution with a worker role (in VS2015), then everything is fine; but if I try to build an old cloud service solution in VSO, then for some reason, the build agent tries restoring Nuget packages and errors:
".2>RestorePackages:
"...nuget\NuGet.exe" install "C:\a\1\s\WorkerRole\packages.config" -source ""  -NonInteractive -RequireConsent -solutionDir "..\ "
.nuget\NuGet.targets(100,9): Error : The path is not of a legal form.
2>C:\a\1\s.nuget\NuGet.targets(100,9): error : The path is not of a legal form. [C:\a\1\s\WorkerRole\WorkerRole.csproj]
.nuget\NuGet.targets(100,9): Error MSB3073: The command ""...nuget\NuGet.exe" install "C:\a\1\s\WorkerRole\packages.config" -source "" -NonInteractive -RequireConsent -solutionDir "..\ "" exited with code 1."
Of course, I have the Restore NuGet Packages option unchecked in the build definition.
Do you have any ideas why that can happen?
Thanks,
Serge

It looks like you are trying to run the old nugget.targets based method which has problems.  Try and remove that targets file from your solution and projects and see if that solves the issue.
Sent from Outlookhttp://aka.ms/weboutlook

From: Sergiy Cherevko<EMAIL_ADDRESS>Sent: Tuesday, December 8, 2015 4:22:22 PM
To: Microsoft/vso-agent-tasks
Cc: Chris Patterson
Subject: Re: [vso-agent-tasks] No file format header found (Build Step/Nuget restore) (#571)
Thanks @chrisrpattersonhttps://github.com/chrisrpatterson and @praneetlokehttps://github.com/praneetloke! That helped.
However, there is one thing I cannot explain: if I create a new cloud service solution with a worker role (in VS2015), then everything is fine; but if I try to build an old cloud service solution in VSO, then for some reason, the build agent tries restoring Nuget packages and errors:
".2>RestorePackages:
"...nuget\NuGet.exe" install "C:\a\1\s\WorkerRole\packages.config" -source "" -NonInteractive -RequireConsent -solutionDir "..\ "
.nuget\NuGet.targets(100,9): Error : The path is not of a legal form.
2>C:\a\1\s.nuget\NuGet.targets(100,9): error : The path is not of a legal form. [C:\a\1\s\WorkerRole\WorkerRole.csproj]
.nuget\NuGet.targets(100,9): Error MSB3073: The command ""...nuget\NuGet.exe" install "C:\a\1\s\WorkerRole\packages.config" -source "" -NonInteractive -RequireConsent -solutionDir "..\ "" exited with code 1."
Of course, I have the Restore NuGet Packages option unchecked in the build definition.
Do you have any ideas why that can happen?
Thanks,
Serge

Reply to this email directly or view it on GitHubhttps://github.com/Microsoft/vso-agent-tasks/issues/571#issuecomment-163021573.

@chrisrpatterson - thanks! That helped as well.
For more details I followed this: https://docs.nuget.org/consume/package-restore/migrating-to-automatic-package-restore

removed nuget.targets and nuget.exe files from .nuget folder in my solution
and changed all my csproj files
and, yes, it works fine now.

Thanks again!

@omarpando and @dac-scherevko - looks like you've got resolution. OK for me to close this issue?

Yes please.
Sergiy Cherevko
Senior Programmer Analyst
DAC Group / Canada
416.492.3214 ext. 6295
From: Matt Cooper<EMAIL_ADDRESS>Sent: Wednesday, January 06, 2016 11:11 AM
To: Microsoft/vso-agent-tasks<EMAIL_ADDRESS>Cc: Sergiy Cherevko<EMAIL_ADDRESS>Subject: Re: [vso-agent-tasks] No file format header found (Build Step/Nuget restore) (#571)
@omarpandohttps://github.com/omarpando and @dac-scherevkohttps://github.com/dac-scherevko - looks like you've got resolution. OK for me to close this issue?
—
Reply to this email directly or view it on GitHubhttps://github.com/Microsoft/vso-agent-tasks/issues/571#issuecomment-169372375.

@vtbassmatt
Sure


Crash between Mekanism and TConstruct

Attempting to put some molten emerald into a casting basin via a Mekanism basic fluid tank, causes a repeating crash until the basin is emptied or removed.  I reported it to TConstruct first at https://github.com/SlimeKnights/TinkersConstruct/issues/2849 but they said the problem is related to Mekanism rendering.  So posting the issue here too.  For anyone else that's had this issue, they also gave a workaround to temp fix the crashing.

Please use the search function. This is reported multiple times.
Aidan is looking into it, but can't find anything yet. I'm also looking but still no clue.
See #4212 (and many other issues)

I did search.  But I only searched the open tickets, if that helps.


Plugin mongodb

MongoDB support (mongo java driver 3.0+)

Codecov Report

Merging #4315 into master will decrease coverage by 0.11%.
The diff coverage is 2.29%.

@@            Coverage Diff             @@
##           master    #4315      +/-   ##
==========================================
- Coverage   41.24%   41.12%   -0.12%
==========================================
  Files        2388     2396       +8
  Lines       74595    74809     +214
  Branches    10058    10089      +31
==========================================
  Hits        30765    30765
- Misses      41001    41214     +213
- Partials     2829     2830       +1

Impacted Files
Coverage Δ

...gin/mongo/interceptor/MongoSessionInterceptor.java
0% <0%> (ø)

...avercorp/pinpoint/plugin/mongo/MongoConstants.java
0% <0%> (ø)

...erceptor/MongoDriverConnectDeliverInterceptor.java
0% <0%> (ø)

.../interceptor/MongoDriverConnectInterceptor3_7.java
0% <0%> (ø)

.../interceptor/MongoDriverConnectInterceptor3_0.java
0% <0%> (ø)

...m/navercorp/pinpoint/plugin/mongo/MongoPlugin.java
0% <0%> (ø)

...m/navercorp/pinpoint/plugin/mongo/MongoConfig.java
0% <0%> (ø)

...rcorp/pinpoint/plugin/mongo/MongoTypeProvider.java
0% <0%> (ø)

...p/pinpoint/bootstrap/instrument/MethodFilters.java
61.4% <71.42%> (-1.56%)
:arrow_down:

...vercorp/pinpoint/web/vo/ApplicationAgentsList.java
72.3% <0%> (-3.08%)
:arrow_down:

... and 15 more

Continue to review full report at Codecov.

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


Yandex.Store fail to purchase item

After calling launchPurchaseFlow() I received error: "IabResult: 4, Problem purchashing item. (response: 4:Item unavailable)". In Yandex.Store Developer Console all purchase items are added and configured. OpenIAB version is <IP_ADDRESS>. Yandex Store app is installed on my device and yandex account is connected to store app.

@int02h i alse encounter  that Yandex.Store asks me to provide credit card or phone information for tester account,but i cann't figure out what issue casuse this ,could you please tell me .


renew-cert fails

renew-cert is suddenly no longer working
concourse: version: v4.0.0
+ cd concourse-up-release
+ chmod +x concourse-up-linux-amd64
+ ./concourse-up-linux-amd64 deploy wizr

WARNING: adding record ci.wizr.com to Route53 hosted zone wizr.com ID: ZDNOZ43D75NB8

aws_eip.nat: Refreshing state... (ID: eipalloc-057b63ab844ef0a17)
aws_eip.atc: Refreshing state... (ID: eipalloc-0f64eb3e16a756bd7)
aws_vpc.default: Refreshing state... (ID: vpc-0c6847dba480011a9)
aws_s3_bucket.blobstore: Refreshing state... (ID: concourse-up-wizr-us-east-2-blobstore)
aws_key_pair.default: Refreshing state... (ID: concourse-up-wizr20180817015833012200000001)
aws_iam_user.blobstore: Refreshing state... (ID: concourse-up-wizr-us-east-2-blobstore)
aws_eip.director: Refreshing state... (ID: eipalloc-0bf53a0578941a26a)
aws_iam_user.bosh: Refreshing state... (ID: concourse-up-wizr-us-east-2-bosh)
aws_iam_user_policy.bosh: Refreshing state... (ID: concourse-up-wizr-us-east-2-bosh:concourse-up-wizr-us-east-2-bosh)
aws_iam_access_key.bosh: Refreshing state... (ID: AKIAJEAGHHOFSDDMQ6NA)
aws_iam_access_key.blobstore: Refreshing state... (ID: AKIAJ7PZRVL7D3OXHVRQ)
aws_route53_record.concourse: Refreshing state... (ID: ZDNOZ43D75NB8_ci_A)
aws_subnet.private: Refreshing state... (ID: subnet-0f330eb34d099cbf5)
aws_subnet.rds_a: Refreshing state... (ID: subnet-07abd765f0a0415b9)
aws_subnet.rds_b: Refreshing state... (ID: subnet-0fc084561ba5e5d19)
aws_security_group.rds: Refreshing state... (ID: sg-0e35eb7f2b150e518)
aws_internet_gateway.default: Refreshing state... (ID: igw-0b379a40dbfba10eb)
aws_security_group.vms: Refreshing state... (ID: sg-00ec7cb724c8143b8)
aws_subnet.public: Refreshing state... (ID: subnet-0ca4fbd59935a5c6b)
aws_route_table.rds: Refreshing state... (ID: rtb-04c171e5a89c6314e)
aws_route.internet_access: Refreshing state... (ID: r-rtb-07fa8825f067808db1080289494)
aws_nat_gateway.default: Refreshing state... (ID: nat-005abba6360c79e63)
aws_route_table_association.rds_b: Refreshing state... (ID: rtbassoc-0ff21f37e060b97c0)
aws_db_subnet_group.default: Refreshing state... (ID: concourse-up-wizr)
aws_route_table_association.rds_a: Refreshing state... (ID: rtbassoc-02f036c671fdd88b3)
aws_security_group.director: Refreshing state... (ID: sg-0a49842457a887881)
aws_route_table.private: Refreshing state... (ID: rtb-06f334b91af4d5298)
aws_route_table_association.private: Refreshing state... (ID: rtbassoc-0382d0556bb5785e4)
aws_security_group.atc: Refreshing state... (ID: sg-0725811022c0cf1a0)
aws_db_instance.default: Refreshing state... (ID: terraform-20180817015841858400000002)
aws_iam_user_policy.blobstore: Refreshing state... (ID: concourse-up-wizr-us-east-2-blobstore:concourse-up-wizr-us-east-2-blobstore)
aws_db_instance.default: Modifying... (ID: terraform-20180817015841858400000002)
  engine_version: "9.6.11" => "9.6.6"

Error: Error applying plan:

1 error(s) occurred:

* aws_db_instance.default: 1 error(s) occurred:

* aws_db_instance.default: Error modifying DB Instance terraform-20180817015841858400000002: InvalidParameterCombination: Cannot upgrade postgres from 9.6.11 to 9.6.6
	status code: 400, request id: 9a17b2f0-3dec-487d-bbd7-37f3d74a8d10

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

exit status 1

It looks like terraform is trying to downgrade the RDS Postgres version from 9.6.11 to 9.6.6. I'm not sure why you would be running 9.6.11 because we pin to 9.6.6 in our terraform (and have done since March 2018.
What version of Concourse-up are you using?

I've done a bit more research and have found that one of our deployments is using 9.6.11. I haven't figured out why or how yet though.

It seems that RDS will do a version upgrade in the maintenance window unless you tell it not to. In terraform we aren't specifying the option but it defaults to true. I think we've deployed against our 9.6.11 deployment before so I'm not sure why your terraform is breaking in this way. Does it work if you manually run concourse-up deploy <your deployment>?

Hi, Today we have started updating the concourse-up and found same issue as described above.
BTW, AWS is stopped supporting 9.6.6 and now the minor version for postgresql is 9.6.11.
I would suggest in terraform engine_version keep as 9.6. auto_minor_version_upgrade is by default true not not set to false explicitly.
As of now our concourse-up deployment become unstable due to upgrade failure

@sureshgoli81 Thanks for reporting - we're looking into this currently.
Can you please explain exactly what you mean by

As of now our concourse-up deployment become unstable due to upgrade failure

Is your Concourse still running, and can builds execute? Does the deployment fail?

Hi, No concourse is not running, because our build is failed with error "failed to obtain lock on concourse deployment". When we tried again with concourse-up deploy <project name> we are getting terraform error related to engine_version.

Thanks @sureshgoli81.
This should be a recoverable situation. failed to obtain lock on concourse deployment is a BOSH error, whereby there was one deployment ongoing on the concourse deployment (which the renew-certs job will have started), and presumably another deployment was attempted.
If you have BOSH CLI access, I'd recommend doing a bosh vms -d concourse, see if any are unhappy, and consider a bosh restart on the web VM. Then pause the renew-certs pipeline until we get the issue fixed.

Hi, Yes. That was our initial Idea however we couldn't able to login to bosh director due to X509 Error related to bosh ca-cert and after looking at the bosh creds file in our bucket. We noticed it was still holding the old bosh director ca cert values.
Now, we have destroyed the setup and recreating the concourse.

Just noticed, while provisioning postgesql in AWS RDS. It allows to create DB with 9.6.6. Since auto_minor_version_upgrade is true by default. The RDS gets updated to 9.6.11 in second run of concourse-up deploy and then in third run of concourse-up deploy we started getting error with engine version error while checking the provisioned resource by terraform. So there are two options either by setting auto_minor_version_upgrade to false or only specify 9.6 in engine_version

My understanding is that the auto_minor_version_upgrade option being true means that RDS will update your engine in the instance's maintenance window when Amazon detects there is a meaningful minor update. I would expect the first deploy to set 9.6.6 then every subsequent deploy until your first maintenance window will work. After RDS does maintenance and updates your instance then you will see the terraform error.
We're currently considering bumping the engine version to 9.6.11 and setting auto_minor_version_upgrade to false so this doesn't happen again. I've put a separate story in our backlog for increasing the hardcoded version when new versions become available.
I wouldn't expect this terraform issue to negatively impact BOSH. In Concourse-Up the terraform runs first and therefore errors out before anything happens with BOSH. I'm not sure why you would have different bosh director ca cert values. If they are being updated then terraform failing would not stop eval "$(concourse-up info --env <deployment>)" from working. I agree with @DanielJonesEB that your problem sounds unrelated to this issue.

Hi, Yes. That was our initial Idea however we couldn't able to login to bosh director due to X509 Error related to bosh ca-cert and after looking at the bosh creds file in our bucket. We noticed it was still holding the old bosh director ca cert values.

I'm not sure why that would have happened, we'll keep an eye out for similar issues. For future reference, another way around this would have been to forcibly terminate the web VM through the AWS console and wait for BOSH's resurrector to recreate it.

After re-pavement of concourse-up. Now we are seeing another strange error related to credhub.
We are seeing below error while logging credhub.
credhub api Setting the target url: https://<domain name>:8844/ Error connecting to the targeted API: "Get https://<domain name>:8844/info: x509: certificate is not valid for any names, but wanted to match ci.ap.innogy.com". Please validate your target and retry your request.
Below steps i have followed while during deployment and post deployment of concourse-up:
concourse-up deploy apci --region eu-central-1 --domain <domain name> --workers 3 --web-size xlarge --db-size medium

Post deployment Steps:
Login to concourse for setting-up pipeline: fly --target apci login --insecure --concourse-url https://<domain name>> --username admin --password <<PWD>>
Here login is success and i am able to list workers as well

Login to credhub :
eval "$(concourse-up info --region eu-central-1  --iaas AWS --env apci)"
credhub api
This is failed with above said error.
I am unable to set the parameters in the credhub as well

@crsimmons  when i manually try to do a manual deploy i get the following:

  engine_version: "9.6.11" => "9.6.6"

Error: Error applying plan:

1 error(s) occurred:

* aws_db_instance.default: 1 error(s) occurred:

* aws_db_instance.default: Error modifying DB Instance terraform-20180817015841858400000002: InvalidParameterCombination: Cannot upgrade postgres from 9.6.11 to 9.6.6
	status code: 400, request id: 4a35af32-14ef-4ec4-8481-9a663d83ad73

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Hi @phynias, we've got a fix for this incoming which is just awaiting PM acceptance. If you're felling brave, you can build from commit 98030bad595ac8704b7f2e6c120d6e2550af6ae1 and use that to deploy.

Hi everyone,
Thank you for reporting the issue to us.
This is to let you know that a patch release has just been published for this fix:
https://github.com/EngineerBetter/concourse-up/releases/tag/0.20.1
Closing this thread now as the conversation on the other issue reported on this page has been carried out separately: https://github.com/EngineerBetter/concourse-up/issues/97
Best regards,
Eva


DOC: Example for integrate.simps

I have created a few simple examples for integrate.simps

@person142, this looks mergeable to me, did you want to merge yourself?

Commits should probably be squashed.

@andyfaff go for it. Squash and merge will be fine to condense things.


About the pre_net_weight

Hello,Shall you tell me where should i put the pre_net_186.pth?
i wish get your reply,thanks!!

cachedir/snapshots/smal_net_600

On 24.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/silviazuffi/smalst/issues/2?email_source=notifications&email_token=ABNYVFN45G2D7E7XQ35VMOLQLHAP5A5CNFSM4IZ4AATKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HNHPXAA, or mute the thread https://github.com/notifications/unsubscribe-auth/ABNYVFMQUEXMYMRL3RA5OW3QLHAP5ANCNFSM4IZ4AATA.

cachedir/snapshots/smal_net_600
…
On 24. Sep 2019, at 09:45, ZhangMinghui @.*** @.***>> wrote: Hello,Shall you tell me where should i put the pre_net_186.pth? i wish get your reply,thanks!! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2?email_source=notifications&email_token=ABNYVFN45G2D7E7XQ35VMOLQLHAP5A5CNFSM4IZ4AATKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HNHPXAA>, or mute the thread https://github.com/notifications/unsubscribe-auth/ABNYVFMQUEXMYMRL3RA5OW3QLHAP5ANCNFSM4IZ4AATA.

thankyou for reply,i have done that,but give me the error report:smalst_experiments/demo_var_feat/proc_frame0066_init_res.pkl
where can i get the proc_frame0066_init_res.pkl?
wish your reply,thank you very much!!

thankyou for reply,i have done that,but give me the error report:No such file or directory: 'smalst_experiments/demo_var_feat/proc_frame0066_init_res.pkl'
where can i get the proc_frame0066_init_res.pkl?
wish your reply,thank you very much!!

that is because you are running the optimization
run the commented line in the script smalst_evaluation_run.sh

On 24. Sep 2019, at 10:02, ZhangMinghui<EMAIL_ADDRESS>wrote:
thankyou for reply,i have done that,but give me the error report:No such file or directory: 'smalst_experiments/demo_var_feat/proc_frame0066_init_res.pkl'
where can i get the proc_frame0066_init_res.pkl?
wish your reply,thank you very much!!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/silviazuffi/smalst/issues/2?email_source=notifications&email_token=ABNYVFMFVZWBXYKYHLDAI6DQLHCSHA5CNFSM4IZ4AATKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7NO7XA#issuecomment-534441948, or mute the thread https://github.com/notifications/unsubscribe-auth/ABNYVFO2DHJMKTJ7SGFVCZ3QLHCSHANCNFSM4IZ4AATA.

OK，I will try，thankyou again
but i want to ask, will you share the trainingset? I had saw someone put forward the question that the trainset has only ten pictures!

Yes, but it is quite big so at the moment I am trying to compress it using tfrecords.
I will post it soon.

On 24. Sep 2019, at 10:16, ZhangMinghui<EMAIL_ADDRESS>wrote:
OK，I will try，thankyou again
but i want to ask, will you share the trainingset? I had saw someone put forward the question that the trainset has only ten pictures!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/silviazuffi/smalst/issues/2?email_source=notifications&email_token=ABNYVFKZ3G23AX7VSAWRHXTQLHEEFA5CNFSM4IZ4AATKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7NQHKY#issuecomment-534447019, or mute the thread https://github.com/notifications/unsubscribe-auth/ABNYVFLUBFGVEU25YPQDZZDQLHEEFANCNFSM4IZ4AATA.

Thank you but i have another strange problem,i have set up the cuda, but have the problem:
File "/home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/chainer/backends/cuda.py", line 80, in check_cuda_available
raise RuntimeError(msg)
RuntimeError: CUDA environment is not correctly set up
Why this happened?

thank you for your reply,but i really confused the cupy. i had installed cupy and my version cuda is9.2
however when all packages installed,i still encountered the problem:
File "build/bdist.linux-x86_64/egg/neural_renderer/cross.py", line 39, in forward_gpu
File "cupy/core/_kernel.pyx", line 571, in cupy.core._kernel.ElementwiseKernel.call
File "cupy/core/_kernel.pyx", line 593, in cupy.core._kernel.ElementwiseKernel._get_elementwise_kernel
File "cupy/core/_kernel.pyx", line 402, in cupy.core._kernel._get_elementwise_kernel
File "cupy/core/_kernel.pyx", line 40, in cupy.core._kernel._get_simple_elementwise_kernel
File "cupy/core/_kernel.pyx", line 60, in cupy.core._kernel._get_simple_elementwise_kernel
File "cupy/core/carray.pxi", line 166, in cupy.core.core.compile_with_cache
File "/home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/cuda/compiler.py", line 165, in compile_with_cache
ptx = compile_using_nvrtc(source, options, arch, name + '.cu')
File "/home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/cuda/compiler.py", line 81, in compile_using_nvrtc
ptx = prog.compile(options)
File "/home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/cuda/compiler.py", line 246, in compile
raise CompileException(log, self.src, self.name, options)
cupy.cuda.compiler.CompileException: /home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/core/include/cupy/carray.cuh(281): warning: statement is unreachable
detected during instantiation of "void CIndexer<_ndim>::set(ptrdiff_t) [with _ndim=1]"
/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu(10): here
/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu(13): error: a value of type "const float *" cannot be used to initialize an entity of type "float *"
/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu(14): error: a value of type "const float *" cannot be used to initialize an entity of type "float *"
2 errors detected in the compilation of "/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu".

I am sorry but I cannot help you on this.

On 24. Sep 2019, at 13:09, ZhangMinghui<EMAIL_ADDRESS>wrote:
thank you for your reply,but i really confused the cupy. i had installed cupy and my version cuda is9.2
however when all packages installed,i still encountered the problem:
File "build/bdist.linux-x86_64/egg/neural_renderer/cross.py", line 39, in forward_gpu
File "cupy/core/_kernel.pyx", line 571, in cupy.core._kernel.ElementwiseKernel.call
File "cupy/core/_kernel.pyx", line 593, in cupy.core._kernel.ElementwiseKernel._get_elementwise_kernel
File "cupy/core/_kernel.pyx", line 402, in cupy.core._kernel._get_elementwise_kernel
File "cupy/core/_kernel.pyx", line 40, in cupy.core._kernel._get_simple_elementwise_kernel
File "cupy/core/_kernel.pyx", line 60, in cupy.core._kernel._get_simple_elementwise_kernel
File "cupy/core/carray.pxi", line 166, in cupy.core.core.compile_with_cache
File "/home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/cuda/compiler.py", line 165, in compile_with_cache
ptx = compile_using_nvrtc(source, options, arch, name + '.cu')
File "/home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/cuda/compiler.py", line 81, in compile_using_nvrtc
ptx = prog.compile(options)
File "/home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/cuda/compiler.py", line 246, in compile
raise CompileException(log, self.src, self.name, options)
cupy.cuda.compiler.CompileException: /home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/core/include/cupy/carray.cuh(281): warning: statement is unreachable
detected during instantiation of "void CIndexer<_ndim>::set(ptrdiff_t) [with _ndim=1]"
/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu(10): here
/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu(13): error: a value of type "const float *" cannot be used to initialize an entity of type "float *"
/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu(14): error: a value of type "const float *" cannot be used to initialize an entity of type "float *"
2 errors detected in the compilation of "/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu".

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/silviazuffi/smalst/issues/2?email_source=notifications&email_token=ABNYVFNGGLG64GG66DXEDKDQLHYOBA5CNFSM4IZ4AATKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7N7PAI#issuecomment-534509441, or mute the thread https://github.com/notifications/unsubscribe-auth/ABNYVFKM4NBPN2WFDFDIBB3QLHYOBANCNFSM4IZ4AATA.

thank you for your reply,but i really confused the cupy. i had installed cupy and my version cuda is9.2
however when all packages installed,i still encountered the problem:
File "build/bdist.linux-x86_64/egg/neural_renderer/cross.py", line 39, in forward_gpu
File "cupy/core/_kernel.pyx", line 571, in cupy.core._kernel.ElementwiseKernel.call
File "cupy/core/_kernel.pyx", line 593, in cupy.core._kernel.ElementwiseKernel._get_elementwise_kernel
File "cupy/core/_kernel.pyx", line 402, in cupy.core._kernel._get_elementwise_kernel
File "cupy/core/_kernel.pyx", line 40, in cupy.core._kernel._get_simple_elementwise_kernel
File "cupy/core/_kernel.pyx", line 60, in cupy.core._kernel._get_simple_elementwise_kernel
File "cupy/core/carray.pxi", line 166, in cupy.core.core.compile_with_cache
File "/home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/cuda/compiler.py", line 165, in compile_with_cache
ptx = compile_using_nvrtc(source, options, arch, name + '.cu')
File "/home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/cuda/compiler.py", line 81, in compile_using_nvrtc
ptx = prog.compile(options)
File "/home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/cuda/compiler.py", line 246, in compile
raise CompileException(log, self.src, self.name, options)
cupy.cuda.compiler.CompileException: /home/zmh/anaconda3/envs/py2.7/lib/python2.7/site-packages/cupy/core/include/cupy/carray.cuh(281): warning: statement is unreachable
detected during instantiation of "void CIndexer<_ndim>::set(ptrdiff_t) [with _ndim=1]"
/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu(10): here
/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu(13): error: a value of type "const float *" cannot be used to initialize an entity of type "float *"
/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu(14): error: a value of type "const float *" cannot be used to initialize an entity of type "float *"
2 errors detected in the compilation of "/tmp/tmpoXpfKI/1509154ce7f1e8ab8eef26ae4980f22a_2.cubin.cu".

Hi,
Have you solved this problem?


How to init RancherOS instance using cloud_init.yml + vagrant + vm

I'm running RancherOS 0.4.3 on vagrant machine I was wondering how can I pass my cloud-init.yml when vagrant up to initialise my machine.

We've moved away from using vagrant and recommend using docker-machine. We will no longer be able to provide support to our vagrant setup.
FYI, even with docker-machine, you will not be able to pass in a cloud-config.yml.
Let me know if you have further questions.

Thanks you so much for you answer @deniseschannon !


Fix checking unknown dimensions for broadcasting

This is partially related to #400
Signed-off-by: Tung D. Le<EMAIL_ADDRESS>

@chentong319 Right, IF statement with two loops would be better for performance. Will consider to use IF statement in another patch. Thanks!

@jenkins-droid test this please.

@tungld When @AlexandreEichenberger  tests test_add_cpu with only the first operand changed to dynamic, the test failed. I confirmed this error.
The test_add.mlir is:
module {
  func @main_graph(%arg0: tensor<?x4x5xf32>, %arg1: tensor<3x4x5xf32>) -> tensor<3x4x5xf32> attributes {input_names = ["x", "y"], output_names = ["sum"]} {
    %0 = "onnx.Add"(%arg0, %arg1) : (tensor<?x4x5xf32>, tensor<3x4x5xf32>) -> tensor<3x4x5xf32>
    return %0 : tensor<3x4x5xf32>
  }
  "onnx.EntryPoint"() {func = @main_graph, numInputs = 2 : i32, numOutputs = 1 : i32} : () -> ()
}

The lowering output from onnx-mlir-opt --convert-onnx-to-krnl is:
module {
  func @main_graph(%arg0: memref<?x4x5xf32>, %arg1: memref<3x4x5xf32>) -> memref<3x4x5xf32> attributes {input_names = ["x", "y"], output_names = ["sum"]} {
    %0 = alloc() : memref<3x4x5xf32>
    %c0 = constant 0 : index
    %1 = dim %arg0, %c0 : memref<?x4x5xf32>
    %c1 = constant 1 : index
    %2 = cmpi "eq", %1, %c1 : index
    %3:3 = krnl.define_loops 3
    krnl.iterate(%3#0, %3#1, %3#2) with (%3#0 -> %arg2 = 0 to 3, %3#1 -> %arg3 = 0 to 4, %3#2 -> %arg4 = 0 to 5) {
      %c0_0 = constant 0 : index
      %4 = select %2, %c0_0, %arg2 : index
      %5 = affine.load %arg0[%4, %arg3, %arg4] : memref<?x4x5xf32>
      %6 = affine.load %arg1[%arg2, %arg3, %arg4] : memref<3x4x5xf32>
      %7 = addf %5, %6 : f32
      affine.store %7, %0[%arg2, %arg3, %arg4] : memref<3x4x5xf32>
    }
    return %0 : memref<3x4x5xf32>
  }
  "krnl.entry_point"() {func = @main_graph, numInputs = 2 : i32, numOutputs = 1 : i32} : () -> ()
}

Notice that both load is Affine.load, which causes trouble in later stage. The first load is indexed from the result of a select operation.  Could you take a look?

@chentong319 Good Catch...
@tungld  By the way, if you were to use the index expression, the system does that for you.... if the expression going into the indices of a load are affine, affine.load; otherwise, std.load.

@chentong319 will fix this problem here: #428.
@AlexandreEichenberger I will move to index expression in near future, it takes a bit time to write index expression for broadcasting.


onyo set edits the whole file instead of the line(s) specified as KEYS, and strips all comments

I created a new asset with onyo new --template and a structured template of my own.
As I used onyo set to edit one value, the resulting file has been stripped of all comments and keys had been sorted alphabetically, losing the pre-existing structure.
diff --git a/shelf/laptop_Apple_MacBookPro.WLT9QNV47M b/shelf/laptop_Apple_MacBookPro.WLT9QNV47M
index 5093303..d2f5068 100644
--- a/shelf/laptop_Apple_MacBookPro.WLT9QNV47M
+++ b/shelf/laptop_Apple_MacBookPro.WLT9QNV47M
@@ -1,22 +1,16 @@
-# Minimal set of metadata for non-unique objects
-vendor: Apple
-model: MacBookPro
-type: laptop
-# Additional metadata for unique objects
-serial-number: WLT9QNV47M
-purchase-time: 2022-09
-# Additional metadata for FZJ/HHU inventorised objects
-inventory-number:
-order-number: 42310418
-# Additional metadata for generic computing devices (desktops, laptops, nodes)
 CPU-cores: 8
-chipset: M1
+JuNet-FQDN: null
+MAC-address: null
 RAM: 16GB
+chipset: M1
+hostname: null
 internal-storage: 512GB
-# Additional metadata for laptops
-screen-size: 14inch
+inventory-number: 411284
 keyboard-layout: DE
-# Additional metadata for objects on the network
-MAC-address:
-JuNet-FQDN:
-hostname:
+model: MacBookPro
+order-number: 42310418
+purchase-time: 2022-09
+screen-size: 14inch
+serial-number: WLT9QNV47M
+type: laptop
+vendor: Apple

The expected behaviour of onyo set is editing the line(s) mentioned in the KEYS parameter and leave everything else as it is.

Could you please provide an example asset, and a set command that exhibits the behavior? That will make reproducing this faster.


Cannot save Schema after editing

There is no option to save the schema after editing in the latest version of github manageiq repo. I pulled the latest repo and built a container but I can't save schema.
Any idea how to save it? There should be a Save, Reset, Cancel option.

@kTipSSIoYv I am not able to reproduce this issue. UI seems different to me. Could you answer following questions?

Are you in master or Morphy branch?
Is this summary page or edit page?
What are exact steps to recreate this issue?

I am seeing this table in UI with buttons. I clicked Edit schema option.

@kavyanekkalapu
Are you in master or Morphy branch?
I'm in master branch
Is this summary page or edit page?
Its the edit page - Configuration -> Edit selected Schema
What are exact steps to recreate this issue?
You click on Edit selected schema, add any entries but there is no save button.

@kavyanekkalapu Can you tell me what you mean by bin/update? I'm not sure what you meant by that. I was thinking about trying morphy branch

@kTipSSIoYv If you are using development env, please run bin/update in manageiq (core) repo. you can also try morphy branch too.

Update: Morphy version doesn't have this bug. I'm able to save the changes.


[table] Avoid unnecessary re-rendering of table cells

Please consider this or similar change to improve performance of table re-rendering.
Before this change all table cells are going to re-render no matter the content of the cell changes or not. This improvement has big impact on frequently updating tables where only few cells changes.
See also: https://reactjs.org/docs/context.html#caveats

[x] I have followed (at least) the PR section of the contributing guide.

Here is a sample code without the proposed change: https://codesandbox.io/s/3x4ovmmk91
and with the proposed change: https://codesandbox.io/s/8rv4pnpkj
When I measure the performance in Chrome inspector I get much better performance with the second example:
https://3x4ovmmk91.codesandbox.io/ - ~80ms
https://8rv4pnpkj.codesandbox.io/ - ~20ms

@petrjaros It's a great first pull request on Material-UI 👌🏻. Thank you for working on it!


Problems with uploading files

Hi,
First of all, thank you for this great package! I have an issue with uploading files from version 5.1+. Whenever I try to upload something in an image field or the SEO image I get a success notification but the files have not been upload nor been changed in the database. I found that 5.0.8 is the latest version where everything works correctly. But that version does not support the flexible-content package.
I tried installing this package into a new empty project but I got the same issue.

Thanks @KasparRosin for this fix. This does indeed fix the issue with the SEO image. However when I use an Image field it still does not upload. Also I found that the validation rules do not work with this package.

@matthijssm Hei

However when I use an Image field it still does not upload.
What do you mean by this? Do you mean within the page fields?
Can you share a quick snippet of the code.

I'm noticing this too @matthijssm @KasparRosin
I've introduced a VaporImage field
Text::make('SEO Title'),
            Textarea::make('SEO Description'),
            VaporImage::make('SEO Image')
                ->help('This should be high res. so that we can manipulate size etc throughout the app')
                ->path('seo_images')
                ->thumbnail(function ($value) {
                    return $value
                        ? novaThumbnail($value)
                        : null;
                })
                ->storeAs(function ($request) {
                    $img = $request->input('vaporFile')['seo_image'];

                    return str_replace('tmp/', '', $img['key']) . '.' . $img['extension'];
                }),

Hey,
We would appreciates pull requests on this matter.
Since our go to media library is our own outl1ne/nova-media-hub, it might take some time until we get around to fix the issues related to nova's image field or other third-party image fields.

Hey!
We would appreciates pull requests on this matter.
Since our go to media library is our own outl1ne/nova-media-hub, it might take some time until we get around to fix the issues related to nova's image field or other third-party image fields.

Nice- does that work on Vapor?

@1stevengrant, hard to say. I'm not that familiar with vapor.
Essentially how nova-media-hub works, is that it has a table, where it saves all the file related information.
Now when you select an image to use, it will only store that image's id.

Hi guys, In this line (src/Http/Controllers/PageManagerController.php#L84), the SEO from the model is waiting for the array, but the incoming SEO data comes in JSON string. When I did array casting in the model, I could upload with the VaporImage field. I made the model file as follows.

class Page extends \Outl1ne\PageManager\Models\Page
{
    protected $casts = [
        'seo' => 'array',
    ];
}

Hi, if you update the fillFields method with the following for the VaporImage field upload problem, the problem will be fixed.
    protected function fillFields($request, $attributeKey, $baseFields, $model)
    {
        $flexibleAttrRegKey = $this->getFlexibleAttributeRegisterKey();

        $locales = ['__', ...array_keys(NPM::getLocales())];
        $body = $request->get($attributeKey, []);
        $files = $request->files->get($attributeKey, []);
        $data = array_merge_recursive($body, $files);

        foreach ($locales as $locale) {
            $dataAttributes = [];
            $fileAttributes = [];
            $localeData = $data[$locale] ?? [];

            $flexibleKeys = null;
            if ($flexibleAttrRegKey && isset($localeData[$flexibleAttrRegKey])) {
                $flexibleKeys = json_decode($localeData[$flexibleAttrRegKey], true);
                $localeData[$flexibleAttrRegKey] = $flexibleKeys;
            }

            foreach ($localeData as $k => $v) {
                $fullKey = "{$attributeKey}->{$locale}->{$k}";

                if ($v instanceof UploadedFile) {
                    $fileAttributes[$fullKey] = $v;
                } else if ($k === "vaporFile" && is_array($v)) { // The update is here.
                    foreach ($v as $n => $f) {
                        $fullKey = "{$attributeKey}->{$locale}->{$n}";
                        $dataAttributes["vaporFile"] = [$fullKey => $f];
                    }
                } else if ($flexibleKeys) {
                    if ($k === $flexibleAttrRegKey) {
                        // Modify flexible registration keys
                        $dataAttributes[$fullKey] = array_map(fn ($fKey) => "{$attributeKey}->{$locale}->{$fKey}", $flexibleKeys);
                    } else if (in_array($k, $flexibleKeys)) {
                        // Decode flexible values
                        $dataAttributes[$fullKey] = $this->getFlexibleCompatibleValue($v);
                    } else {
                        $dataAttributes[$fullKey] = $v;
                    }
                } else {
                    $dataAttributes[$fullKey] = $v;
                }
            }

            $fakeRequest = new NovaRequest([], $dataAttributes, [], [], $fileAttributes);
            $fakeRequest->headers = new HeaderBag(['Content-Type' => 'multipart/form-data']);
            $fakeRequest->setMethod(NovaRequest::METHOD_POST);

            $fields = $baseFields->map(fn ($field) => $this->transformFieldAttributes($field, "{$attributeKey}->{$locale}"));
            $fields->resolve((object) array_merge($dataAttributes, $fileAttributes));
            $fields->map->fill($fakeRequest, $model);
        }
    }

@ferdiunal's PR went live in 5.9.0! :) Thanks a ton!


Init rntr

Summary:

Changelog:

Test Plan:

@jackpope makes sense. Ping me whenever you need any review or consultation.


Export command should include entities & NBT data

Pre-Issue Checklist

[x] I have checked that I am on the latest version of Terra.
[x] I have searched the github issue tracker for similar issues, including closed ones.
[x] I have made sure that this is not a bug with another mod or plugin, and it is Terra that is causing the issue.
[x] I have checked that this is an issue with Terra and not an issue with the pack I am using.

[ ] I have attached a copy of the latest.log file
[x] I have filled out and provided all the appropriate information.

Environment

Name
Value

Terra Version
5.4.1

Platform / Platform Version
Purpur

Any External Plugins or Mods
Oraxen

Terra Packs In Use
Default

Terra Addons In Use
None

Issue Description
When using worldedit wand and trying to save structure with /terra structure export  the item frames don't save.

Steps to reproduce

Make a worldedit selection of structure with item frames
Run /terra structure export  command
Check the generated file, it doesnt contain any info about item frame.

Expected behavior

Actual behavior

Full stacktrace

Exception Stacktrace

There isn't anything printing in the console, the command just runs fine.

Additional details

By the way maybe it matters, my item frames are invisible.
Image of original structure:

Red wool is where i used wand
After exporting:

I guess you could just save info about the item frame.

item frames probably use nbt data, so this is a certified bukkit moment

Item frames are entities. We should have the export command insert entity functions in the exported scripts, as well as store block & entity NBT data
of course, the latter would not be available on Bukkit

I've seen it in some custom structure plugins

@kacperleague9 the problem is, we want to avoid any NMS usage for bukkit because, well, bukkit.

Well, we want to avoid NMS in the main plugin as much as possible. Because NMS is bad for a variety of reasons. So, the NMS addon is ""not officially supported"", even though it's also by us.
The reason being, NMS can be hard to support. Also, I'm pretty sure the NMS addon throw exceptions lol

export command no longer exists. For static structures like that, use the Sponge Schematic addon.


Check if a dragHandler exists before applying fromJust in inputField

Discussed here: https://github.com/fjvallarino/monomer/issues/91

Thanks!


Issue 341: Prepare release of v2.7.1

Description

Updated the changelog
Updated the package version
Tweaked the release branch naming guidelines in CONTRIBUTING.md

Testing
Execute the test cases from pull requests #333 and #339.
Related Issue

GitHub issue link: #341

👍


ArcrotateCamera errors with VR 3D rig

I was testing Blender export parameters for camera.  Know that it might not be a real world combination, but it errors on line 521:
this._rigCameras[0]._cameraRigParams.vrMetrics = metrics;

Think the problem is in ArcrotateCamera.createRigCamera().  It should probably have a line like TargetCamera's:
rigCamera._cameraRigParams = {};
I do not have the hardware to test this, so I am not going to change it.

Hello I'm not able to repro this bug :(

It might be that I am using 2.1.  I want everything tested against production.  I know interaxialDistance has no meaning for this rig, the arg cannot be null, so always passing it.  Here is function for camera def:
function defineCameras(scene) {
    if (Number(BABYLON.Engine.Version.substr(0, BABYLON.Engine.Version.lastIndexOf("."))) < 2.1) throw "Babylon version too old";
    BABYLON.Tools.Log('In get_baked.defineCameras');
    var camera;

    camera = new BABYLON.ArcRotateCamera("Camera", 0.8531, 1.1364, 20.1373, scene.getMeshByID("Gus"), scene);
    camera.setCameraRigMode(20,{interaxialDistance: 0.0637});
    camera.rotation = new BABYLON.Vector3(0.4615,-0.8149,0.0981);
    camera.fov = 0.8576;
    camera.minZ = 0.1;
    camera.maxZ = 500;
    camera.speed = 1;
    camera.inertia = 0.9;
    camera.checkCollisions = false;
    camera.applyGravity = false;
    camera.ellipsoid = new BABYLON.Vector3(0.2,0.9,0.2);
    scene.setActiveCameraByID("Camera");
}
get_baked.defineCameras = defineCameras;

Ok so closing this issue for now


Please invite me to the GitHub Community Organization

Name
Dharmik
Discord Username (if applicable)
Dharmik#7971
Additional Context
I found Eddie on Twitter, and seeing his tweets on Open Source made me interested in it. So I started my journey and got to tell you, I am in love with Open Source!
Open Source is so great and beneficial, I got to meet new people and help them build the dream project by contributing to it, improving my social and communication skills and all this with me getting better at code myself! How great is that!
So I hope to get better at Open Source and learn more from the awesome people of this Community 😊

So glad to join the awesome community😄


python312Packages.pysmt: 0.9.5 -> 0.9.6

Diff: https://github.com/pysmt/pysmt/compare/v0.9.5...v0.9.6
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 322357 run on x86_64-linux 1

14 packages built:

python311Packages.angr
python311Packages.angr.dist
python311Packages.angrcli
python311Packages.angrcli.dist
python311Packages.angrop
python311Packages.angrop.dist
python311Packages.claripy
python311Packages.claripy.dist
python311Packages.pysmt
python311Packages.pysmt.dist
python312Packages.claripy
python312Packages.claripy.dist
python312Packages.pysmt
python312Packages.pysmt.dist


font-size from the code cells

I tried to reduce the font-size from the presentations, but they still appear very big, which classes must I modify in order to reduce the font-size?

The problem was in my cache, I clean my cache before running it and it worked


Adding PUSH in first option

Adding PUSH in first option
Sir/Mam, I want to add a PUSH option in the first options list and add more commands related to it like (-f ,-u).
I found the "git push origin branchname" in the secondary-options.js

BUT manually on the site I could'nt navigate to it.
If you guys want I will work on these features and generate a PULL REQUEST.

Hi @kitarp29! 👋
You just found a bug. The push command has secondary options but it's missing on the primary options.
Feel free to fix this and add more commands related to it. 😃

@kitarp29, I just noticed that #79 addresses this bug.
Maybe you should wait for it before doing other changes.

Ok Sir, if I get some similar issue I let you know


Revamping README file

This is all of the fixes I have done in this PR

Improving README format
English-language supported in every sentence
Remove the LICENSE line to reference the real LICENSE.md for cleaner README
Editing vague wording

lgtm. merge เองเลยจ้า


Fix Return Address Spacing Issue in Envelope Generation

Changes Made:
Summary of Changes:
I adjusted the x and y coordinates in the makePDF function to ensure consistent positioning of the return address across multiple pages.
Technical Details:
The fix involved recalculating the position for each new page in the PDF document.
Code Snippets:
doc.text(returnAddress, .1, .1, textOptions); was modified to use the same values used in the first generated envelope.
Testing:
The fix was tested by generating multiple envelopes with different return addresses and verifying that the alignment was consistent across all pages.
I would appreciate any feedback on the implementation.

Thanks! Nice catch. Rather embarrassing I missed that.

I appreciate your work on this project. It has been incredibly useful for me recently.


Update the kokkos recipe to use the more standard cxxstd option

Prior to update kokkos used std= to set the cxx standard. All other packages
conform to using cxxstd=

sounds great to me Pascal!
also recommending to proceed with PR back into the main Spack when you can (as all other non-Pawsey specific recipe edits we do)


Workaround for type inference breakage in the time crate

The time crate is widely used, and the compatibility issue https://github.com/rust-lang/rust/issues/127343 affects many crates. This may have long-lasting consequences, as the broken versions of the time crate are locked in lockfiles.
If @jhpratt doesn't mind this, I propose here breaking a taboo, and slightly modify the already published crates to fix the incompatibility.
With this patching-patch the affected time crates build again with Rust 1.80. It's an ad-hoc bit of code in tar unpacker, because hopefully Cargo won't need a proper infrastructure for this.

Repeating a suggestion from the possible mitigations in the compiler: it may be good to add a // FIXME(2025-Q2): ... as a reminder that this should be revisited at some point in the future. It might get dropped at that point or it might be extended based on how much usage of the old version still exists, but just something to note this isn't intended to be a permanent hack in Cargo.

For Nixpkgs, I think the best thing would be to have an environment variable to turn this off, given we've already mostly handled the breakage anyway.  I imagine an opt out for Cargo modifying crate sources is desirable for other reasons as well.

This is applied only when unpacking. For users with the crate already in unpacked, I'd need to add some extra check.
Perhaps patching could copy the whole crate to another directory in case tools check the integrity of the original dir, but I'll need to check if that works with the rest of the build pipeline.

It’s pretty big, in my opinion. It silently alters the source tree of a huge number of historical crate dependency graphs from what their locked hashes say they should be. It seems like a dangerous precedent to set and the compiler would be the more appropriate way to hack around this, if a hack is desired. I’m biased because it’s bad for Nixpkgs, but I don’t think we’d be the only ecosystem with serious concerns about this.
(Ideally the compiler would have deployed a workaround before it hit a stable release…)

While discussion on how these hotfixes should be done in general is no doubt useful, trying to properly come up with a general solution before merging this would delay this hotfix in particular indefinitely.

To be clear, I was not saying this had to be blocked on those longer term items.  This is blocked on the shorter term discussion of "what are our options and what is the best of those" which needs to be discussed across teams.
This is an invasive change and a major policy change and should not be done lightly, as others have said.

As this is initially a cross-team discussion, I started a focused thread at https://internals.rust-lang.org/t/brainstorming-how-to-help-old-code-locked-to-old-time-build-on-new-toolchains/21438/2

We understand that the time issue has caused a lot of unexpected churn and like you are interested in finding ways of improving things now and in the future.  To that end, we devoted most of @rust-lang/cargo's meeting to discuss this topic. We considered the possibility of patching the specific ranges of versions of the time crate, by various means. We're concerned about trying to ship a feature like this in a hurry, and potentially unexpected fallout of it, now and in the future:

Cargo crossing the deontological line of patching users' sources and not building exactly the original sources.
Having the user be surprised by this patching (e.g. because they were expecting the failure and were testing the failure).
Having to take this patching into account for future features like caching and verification.

Given that, we would prefer to not move forward with a short-term fix for this issue with the time crate. We are however considering solutions that could help in the future. We have opened https://github.com/rust-lang/cargo/issues/14458 to explore those ideas. In particular, we would like to continue with more incremental work that has already begun, such as:

Yank reasons which is currently a Project Goal, and has the potential to eventually ease towards a mutable database that could possibly support registry patches.
Experiments with patches. That work halted due to concerns over resolver interactions. Resolver interaction was a major component behind that change, but a situation like this with time shows that perhaps a solution that does not support Cargo.toml changes would be useful.
Providing an interface between rustc and cargo so that either side can better support reporting diagnostics related to situations like this. (https://github.com/rust-lang/compiler-team/issues/635 is tangentially related to this.)

A mitigation is being added to rustc via https://github.com/rust-lang/rust/pull/129343. We acknowledge that likely does not go far enough for many since it only provides a diagnostic and not a fix.
Other teams, including libs-api, lang, compiler, and release, are also working on improvements to try to better handle or prevent situations like this.


Solidity autogen docs

Autogenerated docs with some edits and formatting touch-ups.

looks good. can we add doc-generation to the README/scripts too plz

@musnit added doc generation to readme in https://github.com/Snowfork/polkadot-ethereum/pull/116/commits/cb56f33174dea0c19b225509a3aae4198d51150d


Move load balancer sandbox creation/deletion into libnetwork.

Fix for https://github.com/moby/moby/issues/35310
2 changes:

Move sandbox creation/deletion into libnetwork.
Only windows creates a per network lb sandbox.  Linux remains the same until they decide they are ready to take advantage of the per network lb sandbox.
Signed-off-by: Pradip Dhara<EMAIL_ADDRESS>

@mavenugo

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6bbcd1b). Click here to learn what that means.
The diff coverage is 13.54%.

@@            Coverage Diff            @@
##             master    #2011   +/-   ##
=========================================
  Coverage          ?   38.44%
=========================================
  Files             ?      137
  Lines             ?    27455
  Branches          ?        0
=========================================
  Hits              ?    10554
  Misses            ?    15601
  Partials          ?     1300

Impacted Files
Coverage Δ

controller.go
36.84% <11.11%> (ø)

network.go
60.64% <13.79%> (ø)

Continue to review full report at Codecov.

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

LGTM

Thanks! I'll rebase and update the corresponding changes in docker (https://github.com/moby/moby/pull/35422)

@mavenugo do we need a follow-up PR for https://github.com/docker/libnetwork/pull/2011#discussion_r153895197 before we bump libnetwork in moby/moby?

@thaJeztah yes. I spoke to @pradipd already and he is working on it.


Window resizes to 1px wide sometimes - Usability Issue

It is not consistently reproducible - happens randomly. I have first noticed in 0.186.0 build and seen in 0.187.0 build. I am using Ubuntu 14.04 LTS.
Did some trial and error when this happens:

if i try to open another window from command line like another folder using atom the new window opens normally.
If try to quit it will close normally.
If i reopen the folder whose window is like 1px wide it will open with same dimension 1px wide.
Uploading a screenshot.

I feel the user able to minimize window(or because of bug) to such small size is a usability issue as the 1px wide window is difficult to locate and causes confusion to user.

I've seen that happen to, seemingly at random. In Unity only -- using gnome shell is fine.

Just had the same problem on Ubuntu 14.10 64-bit.
I had the window up, covering half the screen. When i then tried to press maximize it disappeared. When closing and restarting it started like a 1px wide window that was almost impossible to see.

I've hit this maybe once on Ubuntu.

Can not reproduce my own reported issue anymore.
Seems to work for me now, but I have since upgraded to Ubuntu 16.10 and Atom is 1.14.4. Anyone else experiencing this bug on latest Atom, or can the issue be closed?


Layer: fix a bug where Layer ummounts children on rerender when zIndex changes

This fixes #1326.
When we pass zIndex indexable object and the reference is changed, the cleanup routine of useEffect hook, which depends on zIndex would be fired and would replace the entire children tree with a new one. I believe this is an oversight when we added zIndex support in #1223. I am fixing this bug by:

make sure the useEffect hook which appends/removes a div element only runs on mount/unmount.
the zIndex is handled by a separate useEffect after the useEffect hook above so that it (1) initiailizes the zIndex after the div has been created on mount, and (2) updates zIndex-related attributes of the div element whenever the value of the zIndex prop changes.

@chrislloyd I addressed the comments. can you please take another look?

@chrislloyd I addressed the comments. can you please take another look?


Write parent row with interleaved child row within same transaction

Hi, I'd like some clarification on the docs posted here https://cloud.google.com/spanner/docs/transactions#rw_transaction_semantics
Transaction reads don't see the same transaction's writes. It's important to note that reads do not see the writes that are buffered in the same transaction. Writes are buffered until the end of the transaction and aren't visible to any reads until the transaction is committed. This is because when you buffer mutations, they're stored locally in your client and aren't sent to the server until commit time. Reads however, are sent directly to the server.

Does this mean that I'm unable to both write a row to a parent table, and a child row which interleaves with that row within the same transaction?
In the program that I'm writing, using the following steps

write one row to the parent table using transaction.insert
write one row to the interleaved table using transaction.insert
make a call to transaction.commit
the call to commit results in the transaction being aborted with error code 5 NOT_FOUND, which seems to indicate the above.  Is that expected?

Environment details

@google-cloud/spanner version: 2.0.0

@splawndive can you provide your code here and maybe we can help.
We did the same thing without this error.

hey thanks for the reply
sorry for the slow response, but I actually ended up being able to work through this one myself.  the issue ended up just being some wonkiness with the IDs i was using/passing around within my application, not within spanner itself.

@splawndive can you elaborate at all? I've found this thread having run across the same issue seemingly.
I've got a table interleaved with a parent, I insert a row into the parent, commit, and using the same session (since flush wasn't working/resulted in the same issue), then try to add a few rows to the child table, and I wind up with errors like the following
google.api_core.exceptions.NotFound: 404 Parent row for row [234eeca9-2a04-4885-a4f4-5096f664378e,0459f48e-54f8-486d-85ee-77635cbd6472] in table rel_malware_communicates_with is missing. Row cannot be written.
I am using the spanner sqlalchemy dialect in this case, but it sounds like the same issue and from what I can tell, my DDL / Tables are created correctly.

I turned Echo on in sqlalchemy, and here's the query being executed
INSERT INTO
rel_malware_communicates_with (
    id,
    malware_id,
    ipaddress_id,
    domain_id,
    url_id
)
VALUES
(
    '3b3c74ec-ed89-4dfe-aa1c-f3dc4d36ab51',
    '16af14ed-2544-4ace-b093-3e050538acbf',
    null,
    '00d48439-2379-41ef-9d95-ed16ec6919a4',
    null
)

Here's the DDL for the table (and yes, that ID for malware_id exists in ob_malware)
CREATE TABLE rel_malware_communicates_with (
	id STRING(MAX) NOT NULL,
	malware_id STRING(MAX) NOT NULL,
	ipaddress_id STRING(MAX),
	domain_id STRING(MAX),
	url_id STRING(MAX),
	FOREIGN KEY (domain_id) REFERENCES ob_domain(id),
	FOREIGN KEY (ipaddress_id) REFERENCES ob_ipaddress(id),
	FOREIGN KEY (malware_id) REFERENCES ob_malware(id),
) PRIMARY KEY (id, malware_id),
INTERLEAVE IN PARENT ob_malware

Clearly there's something with interleaving I'm missing here :S


Update interested-technical-writers

"pull request" to apply for google season of docs.

1st pull request

Closing this pull request as the 2021 program is over. The 2022 program will begin soon; you can add your information in the 2022 interested technical writers file.


Fix typo

Thanks : )

Thanks @YooInKeun for PR. This repository is in the maintenance mode. Could you please create this PR in https://github.com/awspring/spring-cloud-aws?

@maciejwalkowiak I created PR. (https://github.com/awspring/spring-cloud-aws/pull/160)
Thank you for your guidance :+1:


Web API as Function App ?

Hi, I wondering to know why the web api has not been developed in Function App solution?
Is there a specific requirement?

web api (as with any rest endpoint) can certainly be presented in conjunction with a http-trigger.  I suspect this more traditional route (app-service/rest api) was originally taken at the time for just that reason: familiarity - both customer and author.
Since Azure functions integrate tightly with the OpenAI plug-in model, you can expect to see more and more function usage as the semantic-kerneal and chat-copilot architecture evolve:
https://devblogs.microsoft.com/semantic-kernel/create-your-first-chatgpt-plugin-for-semantic-kernel/
https://devblogs.microsoft.com/semantic-kernel/test-your-chatgpt-plugins-in-the-updated-chat-copilot/


adding yml files to add code coverage reports to .net pipeline

Adding code coverage report to the pipelines

Thank you for your contribution. I'm actually about to publish a PR that not only adds code coverage to our Azure Pipelines, but develop builds as well. We'll be expanding on that to cover more scenarios. I can add you to the PR I'll be creating very soon if you'd like.

/azp where

See #17067

Hi @seankane-msft.  There hasn't been recent engagement on this PR and it looks to have been superseded by Heath's changes .  Would you please be so kind as to let us know if this is still an active work stream or if the PR should be closed out?

@jsquire My apologies, I intended to close this PR.

@jsquire My apologies, I intended to close this PR.

Thanks for the quick response, and no need for apologies;  we're just working to keep things from getting stale.  😄


changed the way, the BRs of stiched processes are calculated

Switched from a direct calculation of the Branching ratios between leaf processes and inclusive processes to a step-wise method, where in-between datasets are used to improve on the low statistics one may encounter for low populated processes.

The errors on the BRs are calculated, however they are not saved within the column, because the sparse matrices used as lookup-table do not support object as dtype:
ValueError: object dtype is not supported by sparse matrices


retest: valgrind Conditional jump or move depends on uninitialised value(s)

using retest 32c2d48f88d6227def94fb5d7bd7f7d7ed2a747a
valgrind --leak-check=full --show-reachable=yes --error-exitcode=42 ./retest -r
==353180== Memcheck, a memory error detector
==353180== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==353180== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
==353180== Command: ./retest -r
==353180==
regular tests:       retest: libre version 2.0.1-dev13 (x86_64/linux)
using async polling method 'epoll'
==353180== Conditional jump or move depends on uninitialised value(s)
==353180==    at 0x48BA0AE: jbuf_put (jbuf.c:504)
==353180==    by 0x1292AD: test_jbuf (jbuf.c:52)
==353180==    by 0x14579F: test_unit (test.c:442)
==353180==    by 0x145F2A: test_reg (test.c:660)
==353180==    by 0x12E5DB: main (main.c:234)
==353180==
==353180== Conditional jump or move depends on uninitialised value(s)
==353180==    at 0x48BA0AE: jbuf_put (jbuf.c:504)
==353180==    by 0x12938D: test_jbuf (jbuf.c:67)
==353180==    by 0x14579F: test_unit (test.c:442)
==353180==    by 0x145F2A: test_reg (test.c:660)
==353180==    by 0x12E5DB: main (main.c:234)
==353180==
==353180== Conditional jump or move depends on uninitialised value(s)
==353180==    at 0x48BA0AE: jbuf_put (jbuf.c:504)
==353180==    by 0x1293BD: test_jbuf (jbuf.c:71)
==353180==    by 0x14579F: test_unit (test.c:442)
==353180==    by 0x145F2A: test_reg (test.c:660)
==353180==    by 0x12E5DB: main (main.c:234)
==353180==
==353180== Conditional jump or move depends on uninitialised value(s)
==353180==    at 0x48BA0AE: jbuf_put (jbuf.c:504)
==353180==    by 0x129514: test_jbuf (jbuf.c:95)
==353180==    by 0x14579F: test_unit (test.c:442)
==353180==    by 0x145F2A: test_reg (test.c:660)
==353180==    by 0x12E5DB: main (main.c:234)
==353180==
==353180== Conditional jump or move depends on uninitialised value(s)
==353180==    at 0x48BA0AE: jbuf_put (jbuf.c:504)
==353180==    by 0x129544: test_jbuf (jbuf.c:99)
==353180==    by 0x14579F: test_unit (test.c:442)
==353180==    by 0x145F2A: test_reg (test.c:660)
==353180==    by 0x12E5DB: main (main.c:234)
==353180==
==353180== Conditional jump or move depends on uninitialised value(s)
==353180==    at 0x48BA0AE: jbuf_put (jbuf.c:504)
==353180==    by 0x129574: test_jbuf (jbuf.c:103)
==353180==    by 0x14579F: test_unit (test.c:442)
==353180==    by 0x145F2A: test_reg (test.c:660)
==353180==    by 0x12E5DB: main (main.c:234)
==353180==
==353180== Conditional jump or move depends on uninitialised value(s)
==353180==    at 0x483BC98: strlen (vg_replace_strmem.c:459)
==353180==    by 0x48CF826: str_len (str.c:167)
==353180==    by 0x13C134: test_sip_auth_encode (sipauth.c:72)
==353180==    by 0x13C201: test_sip_auth (sipauth.c:90)
==353180==    by 0x14579F: test_unit (test.c:442)
==353180==    by 0x145F2A: test_reg (test.c:660)
==353180==    by 0x12E5DB: main (main.c:234)
==353180==
==353180==
==353180== HEAP SUMMARY:
==353180==     in use at exit: 0 bytes in 0 blocks
==353180==   total heap usage: 39,392 allocs, 39,392 frees, 9,039,957 bytes allocated
==353180==
==353180== All heap blocks were freed -- no leaks are possible
==353180==
==353180== Use --track-origins=yes to see where uninitialised values come from
==353180== For lists of detected and suppressed errors, rerun with: -s
==353180== ERROR SUMMARY: 11 errors from 7 contexts (suppressed: 0 from 0)
Build step 'Execute shell' marked build as failure
Finished: FAILURE

In test_jbuf() the rtp_header object is not initialized.
Should I create a PR?

https://github.com/baresip/retest/pull/45

thanks!
after the fix this one is left:
==354548== Conditional jump or move depends on uninitialised value(s)
==354548==    at 0x483BC98: strlen (vg_replace_strmem.c:459)
==354548==    by 0x48CF826: str_len (str.c:167)
==354548==    by 0x13C14A: test_sip_auth_encode (sipauth.c:72)
==354548==    by 0x13C217: test_sip_auth (sipauth.c:90)
==354548==    by 0x1457B5: test_unit (test.c:442)
==354548==    by 0x145F40: test_reg (test.c:660)
==354548==    by 0x12E5F1: main (main.c:234)
==354548==

valgrind fails early because of the tmr test, i will rename the "network tests" to "integration tests" and move the test. So we have only unit tests in regular.

yeah it also fails here:
$ valgrind --leak-check=full --show-reachable=yes --error-exitcode=42 ./retest -r
==355935== Memcheck, a memory error detector
==355935== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==355935== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
==355935== Command: ./retest -r
==355935==
retest: libre version 2.0.1-dev13 (x86_64/linux)
using async polling method 'epoll'
regular tests:       json: value of unknown type: <t>
json: value of unknown type: <f>
json: value of unknown type: <n>
json: value of unknown type: <frue>
json: value of unknown type: <talse>
json: value of unknown type: <10t[3e9e66"49"[[72677:[f58{.fn}0{59":8"e}[>
json: value of unknown type: <1t34:{{:f{1.n{""n8[0f7e}:53e6{7:28:{n{00:7>
json: value of unknown type: <8n0}3:28e27}8]75:[:e47968e96n[:2f]n1:]n2[t>
tls: Can't read CA file: /some/path/to/wrong/file.crt
tls: capath is not a directory
tls: capath is not a directory
tls: change cert: cant't read certificate file: ./data/not_a_file.pem
tls: change cert: key missmatch in ./data/client_wrongkey.pem

testtmr: TEST_ASSERT: src/tmr.c:52: actual=0
test: test_tmr_jiffies_usec: test failed (Invalid argument)

retest: TEST_ERR: src/main.c:235: (Invalid argument)
==355935==
==355935== HEAP SUMMARY:
==355935==     in use at exit: 0 bytes in 0 blocks
==355935==   total heap usage: 38,513 allocs, 38,513 frees, 8,946,329 bytes allocated
==355935==
==355935== All heap blocks were freed -- no leaks are possible
==355935==
==355935== For lists of detected and suppressed errors, rerun with: -s
==355935== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

please note that running retest with valgrind will slow down execution.
the unit tests should not fail because of slow execution.


Option to suppress warnings about returning a value from a void function

With arrow function syntax, it's often convenient to do a single imperative action and skip the curly braces:
(val) => this.someVar = val

However, this technically returns a value. So if the function is expected by Flow to have a void return type, an error gets shown, even though (as far as I can tell) there are no possible ill side-effects that could come from returning a value that will by definition never be used. This forces one to use curly braces when they aren't necessary, which creates code clutter:
(val) => { this.someVar = val; }

I could understand why someone might want to be warned upon adding an explicit return to a function that's supposed to be void, as that could signify confusion about the function's usage, but it also seems reasonable to have an option to allow any return value for functions that have a void return type.

You can use (val) => void (this.someVar = val) to stay in an
expression context.

there are no possible ill side-effects that could come from returning
a value that will by definition never be used

Not so. There certainly are ill side-effects that can occur from having
a non-undefined value where undefined was expected. The value
undefined can in fact be used—for instance, in an equality comparison.
For instance, consider an onclick event listener on an a element—the
return value matters, because it determines whether the default behavior
(following the link) occurs.
Consider the following code:
function wrapListener(listener: (message: string) => void): () => void {
  return () => listener("hello, world?");
}
declare var showDialog: (message: string) => void;
myLink.addEventListener("click", wrapListener(showDialog));

If the types are sound, we can see that when the user clicks the link in
question, the showDialog handler will be invoked, and then the user
will follow the link, because returning undefined from an event
handler means that the default behavior occurs.
But suppose that we allow you to write
const showDialog = (message: string): void => confirm(message);  // unsound!

Now, if the user clicks “Cancel” in the resulting dialog, they will not
follow the link, because the event handler will have returned false!
(This is all not to mention the fact that the suggestion as stated would
make Flow trivially unsound.)
Please don’t try to violate the guarantees of the type system just to
save a few keystrokes. It really isn’t worth it. If x: void, then x
had better be strictly equal to undefined. All bets are off otherwise.

@wchargin coming in again with not only alternatives but also amazing explanations 😄 Closing.

@wchargin
I feel the need to mention that your example can only happen outside of a Flow context. If a function is marked as returning void, any calling code will (I believe) be unable to do anything meaningful with the return value, or at least will have ample knowledge that it shouldn't do so. i.e., onclick in your case couldn't have a return type of void.
While it arguably compromises the type system slightly, I think a config option that suppresses warnings in this very specific case wouldn't be unreasonable. The config already supports various options for refining what kinds of things Flow will complain about, since it isn't a perfect system.

I feel the need to mention that your example can only happen outside
of a Flow context. If a function is marked as returning void, any
calling code will (I believe) be unable to do anything meaningful with
the return value, or at least will have ample knowledge that it
shouldn't do so.

Not so. The function type () => void is compatible with the function
type () => void | boolean.
For instance, the type of addEventListener could be
addEventListener: (string, (Event) => void | boolean) => void

Then it is valid for the caller to pass a function (Event) => void as
the callback, with the understanding that it will always return
undefined.
Here is a self-contained example in vanilla Flow only:
// @flow
// `fireListener` invokes a listener; if the listener fails (indicated
// by returning `false`) then an error is thrown.
function fireListener(f: () => void | false): void {
  if (f() === false) {
    throw new Error("something bad happened!");
  }
}
// `wrapListener` accepts a listener that never fails, and produces a
// new listener that never fails.
function wrapListener(listener: (message: string) => void): () => void {
  return () => listener("hello, world?");
}
// From the type, we infer that `showDialog` is a listener that never
// fails.
const showDialog = (message: string): void => confirm(message); // unsound!
// It follows that this call should not fail.
fireListener(wrapListener(showDialog)); // fails due to unsoundness!

If you run this and press “Cancel” on the dialog, then an error is
thrown. That Flow catches the error at the definition of showDialog is
therefore a good thing!


Consider Imports Reorder config when merging Use Trees

While evaluating enhancements to PR #5612, I found that merging use-trees does not take into account the imports_reorder setting and it is considered to set as true.  Assuming this is an issue, this PR is an attempt to fix it.  This is done by adding the imports_reorder config value as a parameter to the use-trees merge related functions.
Note that because of the added parameter, many internal test cases in imports.rs were changed.  For the existing tests I added true as the imports_reorder value, and I added a version of the tests with false value.
One case that is not handled by this PR, and that was raised in a PR #5612 comment is the formatting of the following code, when imports_granularity=Preserve and reorder_imports=true:
use a::b::c::{
d::e
};

In this case, because of the Preserve, it is expected that the output will be use a::b::c::{d::e}, but it is use a::b::c::d::e.
For the record, following is a possible fix for this issue (if it is an issue). I didn't add this fix because it affects some existing test cases.  The possible fix is to UseTree::normalize():

Add imports_granularity argument to the function (usually the passed value is context.config.imports_granularity()).
Change:
https://github.com/rust-lang/rustfmt/blob/ee2bed96d60fd7e46b1fb868f6a8f27e3a8058d0/src/imports.rs#L590-L595
To:

        // Normalise foo::{bar} -> foo::bar
        if let UseSegmentKind::List(ref list) = last.kind {
            if list.len() == 1 && list[0].to_string() != "self" && imports_granularity != ImportGranularity::Preserve {
                normalize_sole_list = true;
            }
        }

I think users expect that when we merge imports we also sort them within the new import list ... Personally, my vote would be to close this.

My view on this (as much as it worth)  is that this is the right approach, but it should be extended so imports_granularity=Crate and reorder_imports=false will be mutual exclusive.  I.e. rustfmt should not allow setting these two values, and when imports_granularity=Crate is set, rustfmt should implicitly set reorder_imports to true.  Otherwise non-merged parts will not be sorted and merged parts will be sorted, which seem to be a conflict.
There are probably other similar cases.  E.g. imports_granularity=Preserve and reorder_imports=true may be mutual exclusive, and imports_granularity=Preserve should implicitly implyreorder_imports=false.


Fix MySQL metadata when prepared statement caching is enabled

Fixes gh-549
What does this PR do?
Fixes the MySQL metadata to avoid a failure when cachePrepStmts is true.
Code sections where the PR accesses files, network, docker or some external service
The newly added test uses Docker, but only in the same way as the existing tests.
Checklist before merging

[x] I have considered including reachability metadata directly in the library or the framework (see our contributing document)
[x] I am the original author of all content provided in the pull request, and I did not copy the content from any other source (see the tests section from our contributing document)
[ ] For all tests where I am not the sole author, I have added a comment that proves I may publish them under the specified license (see the tests section from our contributing document)
[x] I have properly formatted metadata files (see our formatting guide)
[ ] I have added thorough tests (see the tests section from our contributing document)
[x] I have filled all places where my pull request accesses files, network, docker, or any other external service (see the section above)

confirmed this fix works as expected with my application.


Kill Karma if user closes all the captured browsers

When closing all the captured browsers, it might make sense to kill Karma.
We should probably distinguish between closed and crashed browser (which means another "closed" event).
Also, we need to make sure that it does not kill the long-running Karma use case, where I can run Karma for many days. When I wake my laptop from sleep, Karma reconnects. We need to preserve that.

Closing this, as I actually feel this is not always the case.


Error when calling ClearCache

Am getting a crash occurring when calling:
FFImageLoading.Forms.CachedImage.ClearCache(FFImageLoading.Cache.CacheType.All);

This runs on the main thread after we dispose some pages (have tested it running before other pages are disposed as well just to be sure we aren't modifying the image cache at all).
Crash trace that occurs after a bunch of evictions:
An action scheduled for the main thread threw an exception: System.InvalidOperationException: Collection was modified after the enumerator was instantiated.
  at System.Collections.Generic.LinkedList`1+Enumerator[T].MoveNext () [0x00016] in /Users/builder/data/lanes/2512/d3008455/source/mono/external/referencesource/System/compmod/system/collections/generic/linkedlist.cs:519
  at FFImageLoading.Cache.ReuseBitmapDrawableCache.Clear () [0x000a8] in <filename unknown>:0
  at FFImageLoading.Cache.ImageCache.Clear () [0x00000] in <filename unknown>:0
  at FFImageLoading.ImageService.InvalidateMemoryCache () [0x00018] in <filename unknown>:0
  at FFImageLoading.Forms.Droid.CachedImageRenderer.ClearCache (CacheType cacheType) [0x0002d] in <filename unknown>:0
  at FFImageLoading.Forms.CachedImage.ClearCache (CacheType cacheType) [0x00007] in <filename unknown>:0
  at PROJECT.App.<.ctor>b__43 () [0x0005a] in App.cs:384

I'm pretty sure this was fixed a few days ago.
Which version do you use?

2.0.3 currently.

Really weird I was sure it was fixed by https://github.com/molinch/FFImageLoading/commit/874b57e9f2395f34369285062e7c16bec52c9f7b
Which is part of 2.0.3

I'll double check in the morning, I may have only updated to 2.0.3 in another branch.

@molinch We could modify current implementation to use ConcurrentDictionary.

As said in the commit message I don't think it's needed: all calls to the dictionaries are surrounded by locks.
Furthermore the only cases where I found an issue, which wasn't a threading issue, are now having a .ToList()
As I said earlier, I don't think that @ahohns issue is still present in 2.0.3

@molinch Ok then :)

Yep my apologies, I was testing it on 2.0.2 10 minutes before merging in the 2.0.3 update. Works fine on 2.0.3 thanks.

Thanks for the feedback!


⚠ ClamAV has degraded performance

In a06cc92, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 94 ms

Resolved: ClamAV performance has improved in 33be727 after 541 days, 17 hours, 40 minutes.


Configurable scramble length

Scramble length should be a setting. Default can stay at 20.

solved Jun 14, 2015


Speed up base build and shrink image

This is a substantial refactor of top-crates (but split up into easy commits for review).
Basically the playground was previously redundantly building multiple redundant versions of lots of crates redundantly. In the case of the following dependency graph:

playground

normal dependency on A

normal dependency on C with no features

dependency on B (proc macro)

build dependency on C with feature x

cargo would build 2 copies of C, with and without the feature x enabled, because one is for the "target" and one is for the "host", even though in the context of the playground the "target" and "host" are the same architecture and one shared copy of C would have been fine.
If C is somewhere way deeper in the dependency graph (like proc-macro2, which was affected by this) then everything downstream of it would potentially be built multiple times.
The way to fix this is to ensure that every transitive dependency which appears as both a "target" dependency and as a "host" dependency (dependency of a proc macro or build script) has the same feature selected in both cases. Then cargo will build it just once, since the target and host are set to the same architecture.
To do this, we must run the cargo resolver multiple times in a loop, copying the selected features in the output of each run onto the input of the next run. This way if cargo resolves a dependency on feature x of some crate on just the "host" or just the "target", the next resolver will proceed with x enabled on both "host" and "target". Eventually the resolver will reach a fixed point because the process is additive; we only ever add features from one run to the next. In practice this takes 3 resolver runs today.
Before

time cargo build: real 0m37.935s user 11m48.885s
du -s target: 1.91 GB

After

time cargo build: real 0m35.595s user 7m7.891s
du -s target: 1.59 GB

This is 40% less CPU time and 17% smaller Docker image.
Rationale
As you might guess, I don't care about the build time or image size in isolation. The real reason for this change is that I need this in order to implement support for #![crate_type = "proc-macro"] in the playground.
When the playground runs a build with [lib] proc-macro = false (the default), everything under [dependencies] is considered a "target" dependency. With [lib] proc-macro = true, everything under [dependencies] becomes a "host" dependency. If we don't ensure all transitive dependencies have the same features enabled in both modes, then #![crate_type = "proc-macro"] can't work because the precompiled deps won't apply; cargo will start rebuilding a bunch of deps with a different set of features than the prebuilt ones have, and the playground build will inevitably time out after 10 seconds.

I promise it was a coincidence that this opened literally the same minute that you merged #816 — I have been working on it for several hours.
I would be happy to split this up over multiple PRs if that would make the review easier. I didn't want to just start at the beginning and start sending small PRs that wouldn't necessarily make sense without seeing what this adds up to.

Thanks!


Keras model evaluate() progress bar randomly stops before 100%

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mac OS X 10.13.6
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
N/A
TensorFlow installed from (source or binary):
binary
TensorFlow version (use command below):
VERSION=1.13.0-dev20181225 (note: this is the 2.0-preview)
GIT_VERSION=b'v1.12.0-5131-gc6f3c5dc48'
Python version:
3.6.6
Bazel version (if compiling from source):
N/A
GCC/Compiler version (if compiling from source):
N/A
CUDA/cuDNN version:
N/A
GPU model and memory:
N/A

Describe the current behavior
When evaluating a Keras model, the progress bar randomly stops before 100% (however, the loss and metrics returned by the function are correct). Also, it does not end with a newline.
Describe the expected behavior
I expect the progress bar to go up to 100% and display a newline.
Code to reproduce the issue
import tensorflow as tf
import numpy as np

np.random.seed(42)
tf.random.set_seed(42)

(X_train, y_train), (X_test, y_test) = tf.keras.datasets.mnist.load_data()
model = tf.keras.models.Sequential([
    tf.keras.layers.Flatten(input_shape=[28, 28]),
    tf.keras.layers.Dense(10, activation="softmax"),
])
model.compile(loss="sparse_categorical_crossentropy",
              optimizer="sgd", metrics=["accuracy"])

model.fit(X_train, y_train, epochs=2)
print(model.evaluate(X_test, y_test))

Other info / logs
Here is the output of this program:
Epoch 1/2
60000/60000 [==============================] - 2s 28us/sample - loss: 32.8388 - acc: 0.8403
Epoch 2/2
60000/60000 [==============================] - 2s 27us/sample - loss: 26.3895 - acc: 0.8683
 9792/10000 [============================>.] - ETA: 0s - loss: 33.9531 - acc: 0.8363[33.969303797870886, 0.8358]

Notice that the evaluation progress bar (last line) does not go up to 100% (it stops at 9792/10000). Moreover, there is no newline at the end, so the function's returned values ([33.969303797870886, 0.8358]) are printed on the same line.
Moreover, when I run the same code again, I get a different output (only the last line differs). This time the progress bar stopped at 9088/10000, but notice that the function's results are the same as above:
Epoch 1/2
60000/60000 [==============================] - 2s 29us/sample - loss: 32.8388 - acc: 0.8403
Epoch 2/2
60000/60000 [==============================] - 2s 29us/sample - loss: 26.3895 - acc: 0.8683
 9088/10000 [==========================>...] - ETA: 0s - loss: 34.8416 - acc: 0.8327[33.969303797870886, 0.8358]

I think the issue was that, on_batch_end() was relying on on_epoch_end() for the last step processing:
https://github.com/tensorflow/tensorflow/blob/8f60a381d210478f21762a6cf14f547a05e98878/tensorflow/python/keras/callbacks.py#L724-L727
but on_epoch_end() was only called for train mode:
https://github.com/tensorflow/tensorflow/blob/8f60a381d210478f21762a6cf14f547a05e98878/tensorflow/python/keras/engine/training_arrays.py#L375-L378

Created a PR #24633 for the fix.

Once again, thanks @yongtang , and happy New Year! 👍

Happy New Year🎉👍!

This issue can be closed, because some commit already fixed the problem according to  #24633.