[BUG]: /usr/bin/xcodebuild failed with return code: 65

New issue checklist

[ ] I searched for existing GitHub issues
[ ] I read pipeline troubleshooting guide
[ ] I checked how to collect logs

Task name
Xcode
Task version
5.231.5
Issue Description
/usr/bin/xcodebuild failed with return code: 65 before build.
But locally build is successful.
But locally build is successful.
But locally build is successful.
Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Mac mini Apple M2 14.1.2 (23B92)
Relevant log output
2023-12-26T07:52:14.2445200Z (2 failures)
2023-12-26T07:52:14.6374690Z ##[error]Error: The process '/usr/bin/xcodebuild' failed with exit code 65
2023-12-26T07:52:14.6988300Z ##[section]Finishing: Xcode archive

Full task logs with system.debug enabled
No response
Repro steps
No response

Hi @iCodeWoods,
Thank you for raising this question,
Usually, Error code 65 indicates problems with the signing of the application.
Could you please, provide more details about your inputs and signing configuration?
Do you have a minimal project which will help us to reproduce your issue?

Hi @kirill-ivlev , I believe it's not a problem with signing because it fails quickly even before starting the compilation. We have four build machines: one is normal (indicating the project itself is fine), while the other three machines fail before the compilation starts. I don't have a minimal project.
This issue has persisted for a long time. Since we have one successful machine, it doesn't block our release. However, there are occasions when we need to wait if we want to have two or more builds simultaneously.

@iCodeWoods, on that machine, where you build failing from the Azure agent, are you able to build it from the terminal?

I'm having a similar issue. Fails quite quickly. If you're using command line directly, it does build but with Xcode@5 task it does not.
I've only started noticing this since adopting Swift macros. In order to use swift macros. I have followed the steps to enable macro usage. You can either pass in a compiler flag -skipMacroValidation or update the global settings using defaults write com.apple.dt.Xcode IDESkipMacroFingerprintValidation -bool YES.

I am also seeing this:
The error occurs at the very start of compilation, however it possibly is a signing issue because if we turn signing off the compile continues.
Pipeline builds that worked a few weeks ago now fail if we re-run them.

I'm having a similar issue. Fails quite quickly. If you're using command line directly, it does build but with Xcode@5 task it does not.
I've only started noticing this since adopting Swift macros. In order to use swift macros. I have followed the steps to enable macro usage. You can either pass in a compiler flag -skipMacroValidation or update the global settings using defaults write com.apple.dt.Xcode IDESkipMacroFingerprintValidation -bool YES.

@Muhammed9991 Thanks, but we didn't use SwiftMacro.

I am also seeing this:
The error occurs at the very start of compilation, however it possibly is a signing issue because if we turn signing off the compile continues. Pipeline builds that worked a few weeks ago now fail if we re-run them.

@eoinnorris This sounds strange; didn't signing happen in the very last stage?

I am also seeing this:
The error occurs at the very start of compilation, however it possibly is a signing issue because if we turn signing off the compile continues. Pipeline builds that worked a few weeks ago now fail if we re-run them.

@eoinnorris This sounds strange; didn't signing happen in the very last stage?

yes is is strange.
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
{ platform:iOS Simulator, id:DA40344C-ACB5-4AE2-B404-1182E52988A0, OS:17.0.1, name:iPad (10th generation) }
{ platform:iOS Simulator, id:726CC9EA-5F92-4F24-8DFA-4F2A339C3B14, OS:17.2, name:iPad (10th generation) }
{ platform:iOS Simulator, id:9E396783-8F2B-485F-8EB0-43DB3E07AAD3, OS:17.0.1, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:EA3E14E6-16FC-4DF3-B6D8-1F35F09E1B81, OS:17.2, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:38B402A4-7518-4D0B-8BC1-B0F7C8037FAC, OS:17.0.1, name:iPad Pro (11-inch) (4th generation) }
{ platform:iOS Simulator, id:9E6D4867-E816-43EA-9CD3-56492E02D1EA, OS:17.2, name:iPad Pro (11-inch) (4th generation) }
{ platform:iOS Simulator, id:51CD280D-E0EB-4583-B21B-24FA6608C729, OS:17.0.1, name:iPad Pro (12.9-inch) (6th generation) }
{ platform:iOS Simulator, id:5DC953A8-0AA4-4153-9BAE-4C8995BCEDDB, OS:17.2, name:iPad Pro (12.9-inch) (6th generation) }
{ platform:iOS Simulator, id:D5AFB2DE-B3D2-401F-982A-A046CE56464C, OS:17.0.1, name:iPad mini (6th generation) }
{ platform:iOS Simulator, id:E33ADD5B-1FC4-44FA-A4FF-A8CB5D7F7AF0, OS:17.2, name:iPad mini (6th generation) }
{ platform:iOS Simulator, id:3CD78D7C-901A-41E4-9275-754B81B15105, OS:17.0.1, name:iPhone 14 }
{ platform:iOS Simulator, id:59B12573-9054-4816-BB58-9377F9400F1C, OS:17.2, name:iPhone 14 }
{ platform:iOS Simulator, id:2E807556-B6A2-44D7-B6E7-FDD4C481BA16, OS:17.0.1, name:iPhone 14 Plus }
{ platform:iOS Simulator, id:912FE505-2509-4A37-A16C-A26FBB40B3C0, OS:17.2, name:iPhone 14 Plus }
{ platform:iOS Simulator, id:43CFCB94-698F-4D2B-ABDC-E3B8BA97A8F5, OS:17.0.1, name:iPhone 14 Pro }
{ platform:iOS Simulator, id:3AADBC2A-153E-4B0A-9A78-9943D08688BF, OS:17.2, name:iPhone 14 Pro }
{ platform:iOS Simulator, id:01391579-D9A3-4C9C-8483-82DA9D2E4758, OS:17.0.1, name:iPhone 14 Pro Max }
{ platform:iOS Simulator, id:6AA76502-DA74-40ED-9C54-5F9B1E270FE6, OS:17.2, name:iPhone 14 Pro Max }
{ platform:iOS Simulator, id:D52D06F0-70A3-44E8-BDA9-7C895BE96799, OS:17.0.1, name:iPhone 15 }
{ platform:iOS Simulator, id:C558DB64-6D1B-439C-A302-8B07E81570F2, OS:17.2, name:iPhone 15 }
{ platform:iOS Simulator, id:E8535C9F-4708-4C56-84C2-70678668DC5E, OS:17.0.1, name:iPhone 15 Plus }
{ platform:iOS Simulator, id:0D39692E-D81E-4B5C-95C3-A80D11065A3E, OS:17.2, name:iPhone 15 Plus }
{ platform:iOS Simulator, id:AD62461A-EF69-44A3-A518-A11E088DBC4E, OS:17.0.1, name:iPhone 15 Pro }
{ platform:iOS Simulator, id:637EDCC8-73B3-420D-836A-A60DDDA9C02B, OS:17.2, name:iPhone 15 Pro }
{ platform:iOS Simulator, id:9D384CAE-E0EB-454D-BA44-BFF2034A17B2, OS:17.0.1, name:iPhone 15 Pro Max }
{ platform:iOS Simulator, id:E14D5F90-2BCE-4197-A43D-7CC6AF84BE66, OS:17.2, name:iPhone 15 Pro Max }
{ platform:iOS Simulator, id:CB1E153B-77E4-4D0D-998B-0AF4A5D06F81, OS:17.0.1, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:33E68A9F-2C2B-4E76-A5C3-040D4C7CE107, OS:17.2, name:iPhone SE (3rd generation) }
** BUILD FAILED **

##[error]Error: /usr/bin/xcodebuild failed with return code: 65

I am also seeing this:
The error occurs at the very start of compilation, however it possibly is a signing issue because if we turn signing off the compile continues. Pipeline builds that worked a few weeks ago now fail if we re-run them.

We're also seeing the same issue, adding to @eoinnorris that not only the commit it's exactly the same (including the app and yaml pipeline code), but also the agent OS and image versions were exactly the same
Operating System
macOS
13.6.3
22G436
Runner Image
Image: macos-13
Version: 20240114.1

Till the 12th of January worked and now starting from the 19th of January is throwing
##[error]Error: /usr/bin/xcodebuild failed with return code: 65
P.s.
we double checked that certificate and provision profiles are still valid already

I am also seeing this:
The error occurs at the very start of compilation, however it possibly is a signing issue because if we turn signing off the compile continues. Pipeline builds that worked a few weeks ago now fail if we re-run them.

We're also seeing the same issue, adding to @eoinnorris that not only the commit it's exactly the same (including the app and yaml pipeline code), but also the agent OS and image versions are exactly the same
Operating System
macOS
13.6.3
22G436
Runner Image
Image: macos-13
Version: 20240114.1

Till the 12th of January worked and now starting from the 19th of January is throwing ##[error]Error: /usr/bin/xcodebuild failed with return code: 65
Also if it can help, yes the error appears at the "start of compilation", but still after 4/5 minutes the task started to run
P.s. we double checked that certificate and provision profiles are still valid already

Apologies for the confusion, after extensive debugging, we figure the issue out, devs pointed some swift packages to main branch instead of using a release version, all works good now, thanks!

I am also seeing this:
The error occurs at the very start of compilation, however it possibly is a signing issue because if we turn signing off the compile continues. Pipeline builds that worked a few weeks ago now fail if we re-run them.

Hi @eoinnorris , Are you still facing this issue, or have you resolved it? I tried using a new .p12, but it still fails at the beginning of the build.

I am also seeing this:
The error occurs at the very start of compilation, however it possibly is a signing issue because if we turn signing off the compile continues. Pipeline builds that worked a few weeks ago now fail if we re-run them.

We're also seeing the same issue, adding to @eoinnorris that not only the commit it's exactly the same (including the app and yaml pipeline code), but also the agent OS and image versions are exactly the same
Operating System
macOS
13.6.3
22G436
Runner Image
Image: macos-13
Version: 20240114.1

Till the 12th of January worked and now starting from the 19th of January is throwing ##[error]Error: /usr/bin/xcodebuild failed with return code: 65
Also if it can help, yes the error appears at the "start of compilation", but still after 4/5 minutes the task started to run
P.s. we double checked that certificate and provision profiles are still valid already

Apologies for the confusion, after extensive debugging, we figure the issue out, devs pointed some swift packages to main branch instead of using a release version, all works good now, thanks!

In your case, there does seem to be an error, but it's only displaying '/usr/bin/xcodebuild' failed with exit code 65 without providing specific error information. Is there a way we can enhance the details of this error? @kirill-ivlev

I am also seeing this:
The error occurs at the very start of compilation, however it possibly is a signing issue because if we turn signing off the compile continues. Pipeline builds that worked a few weeks ago now fail if we re-run them.

Hi @eoinnorris , Are you still facing this issue, or have you resolved it? I tried using a new .p12, but it still fails at the beginning of the build.

add  args: '-verbose' to get more output.
In our case some of our SPM libraries had updated to change their Xcode project files, both the reachability and realm project did something, it looks like they added a security markdown at the least.
What we found was that the build failed on the pipeline but not on our local builds which mimic the pipeline build exactly.
Without knowing the full underlying cause it looks like code signing failed because of additional assets in the framework -- the security file I assume. You get this with the verbose log.
It looks like this works with Xcode 15.x on macOS 14.x but not for Xcode running on pre Sonoma. The pipeline uses Ventura as the latest OS, presumably they do this until Ventura is not supported anymore, at which time it will magically fix itself.  In the meantime look at recent updates in your SPM list ( or Cocoa pods or whatever you use)

Fixed. We did have some SwiftUI previews in one of our kit and that can apparently cause issues if Swift 5.9 is not installed on the build machines.

Fixed. We did have some SwiftUI previews in one of our kit and that can apparently cause issues if Swift 5.9 is not installed on the build machines.

Can you help me to install Swift 5.9 on build machines? Thanks in advance.

I am also seeing this:
The error occurs at the very start of compilation, however it possibly is a signing issue because if we turn signing off the compile continues. Pipeline builds that worked a few weeks ago now fail if we re-run them.

@eoinnorris This sounds strange; didn't signing happen in the very last stage?

yes is is strange.
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
{ platform:iOS Simulator, id:DA40344C-ACB5-4AE2-B404-1182E52988A0, OS:17.0.1, name:iPad (10th generation) }
{ platform:iOS Simulator, id:726CC9EA-5F92-4F24-8DFA-4F2A339C3B14, OS:17.2, name:iPad (10th generation) }
{ platform:iOS Simulator, id:9E396783-8F2B-485F-8EB0-43DB3E07AAD3, OS:17.0.1, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:EA3E14E6-16FC-4DF3-B6D8-1F35F09E1B81, OS:17.2, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:38B402A4-7518-4D0B-8BC1-B0F7C8037FAC, OS:17.0.1, name:iPad Pro (11-inch) (4th generation) }
{ platform:iOS Simulator, id:9E6D4867-E816-43EA-9CD3-56492E02D1EA, OS:17.2, name:iPad Pro (11-inch) (4th generation) }
{ platform:iOS Simulator, id:51CD280D-E0EB-4583-B21B-24FA6608C729, OS:17.0.1, name:iPad Pro (12.9-inch) (6th generation) }
{ platform:iOS Simulator, id:5DC953A8-0AA4-4153-9BAE-4C8995BCEDDB, OS:17.2, name:iPad Pro (12.9-inch) (6th generation) }
{ platform:iOS Simulator, id:D5AFB2DE-B3D2-401F-982A-A046CE56464C, OS:17.0.1, name:iPad mini (6th generation) }
{ platform:iOS Simulator, id:E33ADD5B-1FC4-44FA-A4FF-A8CB5D7F7AF0, OS:17.2, name:iPad mini (6th generation) }
{ platform:iOS Simulator, id:3CD78D7C-901A-41E4-9275-754B81B15105, OS:17.0.1, name:iPhone 14 }
{ platform:iOS Simulator, id:59B12573-9054-4816-BB58-9377F9400F1C, OS:17.2, name:iPhone 14 }
{ platform:iOS Simulator, id:2E807556-B6A2-44D7-B6E7-FDD4C481BA16, OS:17.0.1, name:iPhone 14 Plus }
{ platform:iOS Simulator, id:912FE505-2509-4A37-A16C-A26FBB40B3C0, OS:17.2, name:iPhone 14 Plus }
{ platform:iOS Simulator, id:43CFCB94-698F-4D2B-ABDC-E3B8BA97A8F5, OS:17.0.1, name:iPhone 14 Pro }
{ platform:iOS Simulator, id:3AADBC2A-153E-4B0A-9A78-9943D08688BF, OS:17.2, name:iPhone 14 Pro }
{ platform:iOS Simulator, id:01391579-D9A3-4C9C-8483-82DA9D2E4758, OS:17.0.1, name:iPhone 14 Pro Max }
{ platform:iOS Simulator, id:6AA76502-DA74-40ED-9C54-5F9B1E270FE6, OS:17.2, name:iPhone 14 Pro Max }
{ platform:iOS Simulator, id:D52D06F0-70A3-44E8-BDA9-7C895BE96799, OS:17.0.1, name:iPhone 15 }
{ platform:iOS Simulator, id:C558DB64-6D1B-439C-A302-8B07E81570F2, OS:17.2, name:iPhone 15 }
{ platform:iOS Simulator, id:E8535C9F-4708-4C56-84C2-70678668DC5E, OS:17.0.1, name:iPhone 15 Plus }
{ platform:iOS Simulator, id:0D39692E-D81E-4B5C-95C3-A80D11065A3E, OS:17.2, name:iPhone 15 Plus }
{ platform:iOS Simulator, id:AD62461A-EF69-44A3-A518-A11E088DBC4E, OS:17.0.1, name:iPhone 15 Pro }
{ platform:iOS Simulator, id:637EDCC8-73B3-420D-836A-A60DDDA9C02B, OS:17.2, name:iPhone 15 Pro }
{ platform:iOS Simulator, id:9D384CAE-E0EB-454D-BA44-BFF2034A17B2, OS:17.0.1, name:iPhone 15 Pro Max }
{ platform:iOS Simulator, id:E14D5F90-2BCE-4197-A43D-7CC6AF84BE66, OS:17.2, name:iPhone 15 Pro Max }
{ platform:iOS Simulator, id:CB1E153B-77E4-4D0D-998B-0AF4A5D06F81, OS:17.0.1, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:33E68A9F-2C2B-4E76-A5C3-040D4C7CE107, OS:17.2, name:iPhone SE (3rd generation) }
** BUILD FAILED **

##[error]Error: /usr/bin/xcodebuild failed with return code: 65

I am still having the same issue... I am not very familiar with apple/xcode development, my project uses Ionic/capacitor.. please help! (certificates are all valid, I checked that)

hi @Valentin-Pommee-Macaw did you find a resolution by any chance ? I have also been setting up a pipeline for an Ionic build and am stuck at the same 65 error code...

Hey @FauxObsolete,
this is a bit embarassing, but i actually did make a mistake with my certificate and provisioning profile... resolved it by correctly re-generating new ones using the developer account i used to publish my app with from xcode.

Anyone having also this problem. We had a script that modified the capacitor project project for multiple tenants, but we forgot to replace the applicationIdentifier in the project.pbxproj file. Since the applicationIdentifier was wrong we got this error only in our build pipeline.
However building on our local machine worked perfectly fine, hence threw quite some time into researching this issue since it was not really that self descriptive what is wrong. Hope this helps anyone

@otiv33 It's not my case, he's correct. Could a wrong configuration regarding the use of flavors cause this? (I refer to the configuration in the pipeline)

2024-12-13T09:58:36.7338970Z ##[debug]Agent environment resources - Disk: / Available 125583.50 MB out of 332471.96 MB, Memory: Used 7151.00 MB out of 14331.00 MB, CPU: Usage 99.86%
2024-12-13T09:58:37.5391350Z     Run script build phase '[CP] Embed Pods Frameworks' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'App' from project 'App')
2024-12-13T09:58:37.5698460Z ** BUILD FAILED **
2024-12-13T09:58:37.5934320Z
2024-12-13T09:58:37.5945870Z ##[debug]success of first tool:false
2024-12-13T09:58:37.5950680Z ##[debug]rc:0
2024-12-13T09:58:37.5959810Z ##[debug]success:true
2024-12-13T09:58:37.5964050Z ##[debug]task result: Failed
2024-12-13T09:58:37.6005960Z ##[error]Error: /usr/bin/xcodebuild failed with return code: 65
2024-12-13T09:58:37.6013900Z ##[debug]Processed: ##vso[task.issue type=error;source=TaskInternal;correlationId=9903cf4f-2022-4b0c-84ab-7f6cab6f53ed;]Error: /usr/bin/xcodebuild failed with return code: 65
2024-12-13T09:58:37.6015690Z ##[debug]Processed: ##vso[task.complete result=Failed;]Error: /usr/bin/xcodebuild failed with return code: 65
2024-12-13T09:58:37.6016420Z ##[debug]Agent.Version=3.248.0
I get this error, How to find out the cause??

Anyone?


Fix a typo in the README in the tools directory

Pull Request Test Coverage Report for Build 4051

0 of 0   changed or added relevant lines in 0 files are covered.
7 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.02%) to 36.063%

Files with Coverage Reduction
New Missed Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/jmx/JmxJobMBeanManager.java
1
72.73%

azkaban-common/src/main/java/azkaban/jobExecutor/AbstractProcessJob.java
2
60.71%

azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
4
76.03%

Totals

Change from base Build 4048:
-0.02%

Covered Lines:
10500

Relevant Lines:
29116

💛  - Coveralls


Update bookinfo images

Please provide a description of this PR:

@frankbu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
55a6cae291438e7c5ad85a5071c92c570bb91252
link
true
/test release-notes_istio

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

@frankbu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
55a6cae291438e7c5ad85a5071c92c570bb91252
link
true
/test release-notes_istio

unit-tests_istio
55a6cae291438e7c5ad85a5071c92c570bb91252
link
true
/test unit-tests_istio

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

In response to a cherrypick label: new pull request created: #39015


[WIP]Use the JLine for command line tool

Not long ago，this pr occur some push problem，now i restart this pr and soon i will complete the rest job


testing PR to merge in some local compatibility changes

updated billyyoung/ezhil, trying to merge in changes for myself... but local repo has some detached HEAD issues
code changes: remove disqus intergation + remove some imports that are causing hugo server crashes

sorry, set up this PR incorrectly! was trying to merge into my own fork
closed


Enable soft failover to dhcp assigned servers

Proxy causes failure in captive WiFi portals. Idea is to allow standard dns where connection state has recently changed.

So, all an attacker has to do in order to disable authentication is to simulate a captive portal. This completely defeats the whole point of having a secure DNS protocol.


Show Location in Map - MessageList

Hi,
In the screenshot, the message type is shown as a map. But I did not find such a possibility in the code part. Does anyone have information?

Did you find anything related to this issue?

You can check this issue #116


Add browserslist

browserslist is a file that contains the list of browsers in free format that is then used
by autoprefixer and saucelabs.
Useful links:
https://github.com/ai/browserslist
https://github.com/vxsx/browserslist-saucelabs
Travis log looks kind of crazy, but saucelabs report normal amount of tests run

LGTM

we can also integrate that into the boilerplate


Local protractor install fix

Checks for protractor global install before npm installs a local protractor.
Testing

./frontend.sh

Review

@jimmynotjim

Ran and works :+1:


(2.0) Update documentation

Lots of new stuff to document, including:

New frontend/backend split
t2-inspect for debugging
Improved VS2012 project generation (might make an example for that)

Something that would be nice to document also is existing environment variables one can use like $(HOSTPROGSUFFIX) , $(SEP), $(OBJECTDIR), etc


New charge rate service

Any possibilities to have this merged in the upcoming days?

Hey, team. Could you let me know if you will release the component anytime soon? A few notable features and fixes would be nice to have as this one and avoid to pull the repo manually.


Locking for POMs on disk, and better locking for JARs

There's some basic locking for JAR files on disk, but lacking waiting / re-attempt mechanisms.
For POM, there's no locking at all. There should be one, with some waiting / re-attempt too.

POMs and JARs now handled the same way since https://github.com/alexarchambault/coursier/commit/e20b93326d9a1beb8e0d7672c67e1cc4e47aee45 (handled like were only JARs before).


Update README.md to link to SSPL

When reading the README for the first time, I was left wondering what the SSPL was, and why it might be a problem, so this change merely links to the license in question, for ease of browsing and understanding: https://www.mongodb.com/licensing/server-side-public-license

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

Thank you!


Remove userId arguments in User Facade - Consent Management

See master ticker GH-1092
Depends on GH-1578
Remove the userId argument from these functions. Use the user id currentinstead inside the facade functions.

loadConsents(userId: string): void {
giveConsent(     userId: string,     consentTemplateId: string,     consentTemplateVersion: number  ): void {
withdrawConsent(userId: string, consentCode: string): void {
and more if any other I missed

We also need to refactor the components that use these functions and write down smoke test instructions for which feature we know we should look closer into for regression.

PR #2650

Tested on dev2.

Using "current" now
Able to
give consent

withdraw consent

get consent

Consent works as before.


update Zend_Validate.php resource file for 2.4

add Timezone MessageTemplates
update class name Float -> IsFloat, Int -> IsInt

I have created pr #7433 for "id" language

Could you write a tool for test this issues on Travis?


Removing all deprecated code

The following deprecated code has been removed:

The COMPONENT_CATEGORY_LOAD variant from the ComponentCategory enum.
The COMPONENT_CATEGORY_JUNCTION variant from the ComponentCategory enum.
The RPCs Charge and Discharge, in favour of RPC SetPowerActive.
The RPC SetBounds, in favour of RPCs AddExclusiveBounds and AddInclusiveBounds.

This removal also includes code that has been deprecated after the last major release. The reason to remove these deprecations now is to have a leaner API earlier, since we are already on the way for a major release now.

I would be good to have other eyes here, though, more experience with the historical use of the microgrid API, I'm just approving from the POV of the diff but I'm not fully aware of all the implications. Maybe @sahas-subramanian-frequenz should take a look too.


Caching downloaded files (in the event of failure)

Relating to #1697, if I run ruby-build commands back to back, there's a repeat of a previously successful step to download installers from cloudfront.
Sure, this only really affects people who'd have a problem with an installation, but it may be worth doing anyway?

You can store them by rbenv cache mechanism that is mkdir $RBENV_ROOT/cache


fix copy/paste regression

Fix for recent regression of copy/paste introduced in #283
@Fausto95 Can you check if all fixed now? Sorry about the regression, we really need to set up tests :).

LGTM


Monitor execution timeout in build

Context
We have been bitten by execution timeout for a long time. To diagnose the cause, in this PR we set a hourly timer when integration tests start, then print all java processes' stack traces on the machine if it timeouts. The default timeout for embedded executer is 1 hour, and 3 hours for all other integration tests.
Most of the work was finished in https://github.com/gradle/gradle/pull/5806 , now we're just reusing the code to invoke jstack on all running JVMs of current build agent.

@blindpirate @wolfs is there a way to pull this off with already present features? Just spawning a separate thread is a little dirty because it assumes we'll never run more than one test task at one time and it sort of gives up on getting any context as to what Gradle's doing.
Are you trying to catch tests/JVMs before they timeout? Or are you trying to catch cases where Teamcity may kill the build or where the JUnit/Spock timeout doesn't work?

Ah, thanks. That does look frustrating.
I don't know if I would trust TeamCity's reporting there.  It might be saying those tests were successful because it didn't see a failure, but the tests would have been treated as failures if Gradle had finished properly.  Since the build timed out and TC killed Gradle, we don't have a build scan to know the true status.
I can't tell if TC tries to cancel the Gradle build before killing it completely. If it tries to cancel the build, we could potentially add something to Test so that we cancel test execution and maybe get a build scan out of the build.

@wolfs That's easy, let's set a 10 minutes timeout and run a QuickFeedback.

Seems to work now: https://builds.gradle.org/viewLog.html?buildId=14481406&buildTypeId=Gradle_Check_Quick_Java8_Oracle_Linux_core&tab=buildLog&_focus=31981#_state=218


Bug(lint): variable detected as unused when used as index accessor

Steps to reproduce

Create file foo.ts with these contents:

export function updateDiffStats(stats, diff, childCount) {
  const idx = getChildCountIdx(childCount);
  if (diff === 1) {
    stats.keyed[idx]++;
  } else if (diff === 2) {
    stats.unkeyed[idx]++;
  } else if (diff === 3) {
    stats.mixed[idx]++;
  }
}

const getChildCountIdx = (n) => n;

Run npx oxlint foo.ts

Output:
$ npx oxlint foo.ts

  ⚠ eslint(no-unused-vars): Variable 'idx' is declared but never used.
   ╭─[foo.ts:2:8]
 1 │ export function updateDiffStats(stats, diff, childCount) {
 2 │     const idx = getChildCountIdx(childCount);
   ·           ─┬─
   ·            ╰── 'idx' is declared here
 3 │     if (diff === 1) {
   ╰────
  help: Consider removing this declaration.

Finished in 3ms on 1 file with 94 rules using 10 threads.
Found 1 warning and 0 errors.

This is already fixed, will release soon!

https://github.com/oxc-project/oxc/pull/5722/files

Awesome, closing as resolved by https://github.com/oxc-project/oxc/pull/5722 in this case.


Agario bots are alive ?

Please do not ask for proxies
Please do not talk about cheating on public servers.
Please do not talk about how this won't be fixed.

Sejo there is no way for agar bots again because agario is using captcha
there some bots working for 5-10 mins and they get banned
captcha :/

yep agario bots are alive but they will get disconnected after 15 minutes because of the captcha

Oh damn then :D

ugh actually they dont disconnect i could use them for more than an hour

@NuclearC  Share with us 15 mins is still 15mins :'D


Timeout error that feels almost immediate, I may have a solution

I ran into a problem where erase_flash was throwing a timeout, but it's supposed to be a timeout of 120000 and it felt like it was immediate.
Investigating with the debugger, it seems like the call const {value, done} = await reader.read(); was making done equal true on the very first call.
Going back a bit, the thing that happens before sending the erase flash command is main_fn finishing up with a call to change_baud.
At the bottom of change_baud, there's a line that says await this.transport.rawRead({timeout:500}); that has no purpose that I can think of, there's no code comments
Disabling that line await this.transport.rawRead({timeout:500}); will fix the timeout problem.
Another solution is to simply not call change_baud ever, and use baud rate 115200, equaling rom_baudrate, so the change is redundant anyways
I hope somebody finds this useful and maybe the code logic gets changed a bit in a release.
I am wondering if this will help the fellas in this issue https://github.com/espressif/esptool-js/issues/96
NOTE: using https://espressif.github.io/esptool-js/ never has this problem but that doesn't mean the problem doesn't exist, it's likely some sort of timing/threading issue, perhaps due to inclusion or absence of xterm. We should aim for a solution that works on all platforms of all variations, not just ignoring an issue because one demo works.

Could you try https://brianignacio5.github.io/esptool-js/ which implement #160 ?


Adding KashCorpSA

Shared Assets (virtual mod) for KAP and RoversAndRoadsters mods.

File extension is .netkan
You need to remove the comma on line 11
What is the reasoning behind the hardcoded "version" field rather than using the scraped one?

scraped version differs depending on which one of the 2 sources you look at - this is shared between the 2 follow-on mods Im adding afterward.  So I decided to version the psud-mod instead, to be able to point it at whichver is more up to date as the base.  I rechecked the build with netkan on my Win8.1 box and it accepted it with the extra comma, no error reported.  Perhaps a newer version of netkan is needed?   I have deleted the comma, renamed the file, and will redo the pull.

netkan.exe will accept a lot of things, such as .txt files but the buildbot runs it through a json validator. You can do your own validation at e.g. www.jsonlint.com to see if your file looks ok.
Rather than opening multiple PRs you can instead push changes to this one :)


White space characters in Team Name

Description
The Code owners doc, states the syntax rules (minus a few exceptions) should be honored. The GitIgnore documentation states we should use the forward slash \ for escaping white space characters.
Upon providing the escape the tool reports the owners file is invalid.
example:
/Root/Feature/ @orginization/Team\ A
Expected result
The code owners file is valid if it has an escape character prefixing a space
Actual result
File is marked as invalid.
Steps to reproduce
Add a owner with a name that has a white space character.

wrong code owner validation  repo apologies.


Windows Defender detects go rewrite as "Trojan:Script/Sabsik.FL.A!ml"

Will probably scare off a lot of people if it stays like this

Of course it does. Though it didn't for me when testing in my VM.

No matter how much I look into it, the only method to fix this, which is still not really guaranteed, is to buy a codesign cert and properly sign each binary (thanks M$). I have pretty minimal reason to bother though, so that's not happening.
Still, surprised Windows Defender detects it since Virustotal has Microsoft listed as seeing it as clean.
Virustotal link for the most recent binary I built: https://www.virustotal.com/gui/file/a1e44627b991843acb50120594d1e7c0d2bb6b92eaa64b458db4ada11e996338?nocache=1

Looks like it's fixed


Durable Functions host.Json Examples Incorrect

In all of the host.json examples on this page (host.json settings) are possibly incorect? Shouldn't v2 durableTask items be part of  the extensions object as documented here:
https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-perf-and-scale#functions-20
Without this for me the maxConcurrentActivityFunctions option was being ignored.

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4b2c8f85-9416-d9f2-e082-b1b15961d810
Version Independent ID: e987c477-36ef-76b9-6dbd-db76fd291e7b
Content: Bindings for Durable Functions - Azure
Content Source: articles/azure-functions/durable/durable-functions-bindings.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: azfuncdf

@CundyTech Thank you for your feedback! We will review and update as appropriate.

Indeed this needs to be updated for host.json 2.0. The hubName property points to v1 (DurableFunctionsHub ), not v2 (TestHubName). I doubt the connectionStringName is also correct.

@CundyTech The example has been corrected. Please check the document. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


GUI size not respecting the settings.

I set the width to 6 but it seems to be 7 wide.

Are you using a custom theme? Could you check if it also happens without it?

To the best of my knowledge:  No.  Only the DARK one which comes with NR.

Ok I figured it out. It happens if "Angular theme in ui_template" is enabled.

You can switch to "Node-RED theme everywhere" in order to avoid that for now.
Thanks for pointing it out... I am definitely going to fix this in one of the next updates.

I had a theme in the edit screen (midnight-red).
I disabled that and restarted NR.
Same problem.
For the sake of everyone's sanity, I will try it with chrome.
(Strike that, sorry.   My main machine is down and I don't have Chrome installed on this.)
Saw your latest reply.
Yes, I am using Angular in ui template.


No benchmark found

Hi, thanks for the cool action. I'm relatively new with actions, so may have made an obvious mistake. As far as I know the only major change is making the repo public and haven't changed the configuration, however now I am receiving a no benchmark found.
I was expecting there to possibly be a problem with the pages commit, but not the output itself not being found.
Error
##[error]No benchmark result was found in /home/runner/work/retry/retry/output.txt. Benchmark output was

I added a step before showing that output was in the above location.
Config
  benchmark:
    name: Run Go benchmark example
    runs-on: ubuntu-latest
    steps:

    - uses: actions/checkout@v2
    - uses: actions/setup-go@v1
      with:
        go-version: 1.13
      id: go
    - name: Run benchmark
      run: go test -bench . | tee output.txt
    - name: check benchmark output
      run: pwd && ls

    - name: Store benchmark result
      uses: rhysd/github-action-benchmark@v1
      with:
        name: Go Benchmark
        tool: 'go'
        output-file-path: output.txt
        github-token: ${{ secrets.GITHUB_TOKEN }}
        # Use personal access token instead of GITHUB_TOKEN due to https://github.community/t5/GitHub-Actions/Github-action-not-triggering-gh-pages-upon-push/td-p/26869/highlight/false
        # github-token: ${{ secrets.PERSONAL_GITHUB_TOKEN }}
        auto-push: true
        # Show alert with commit comment on detecting possible performance regression
        alert-threshold: '200%'
        comment-on-alert: true
        fail-on-alert: true
        alert-comment-cc-users: '@Brian-Williams'

Bench cmd
Locally and in actions the bench runs successfully
go test -bench .
goos: darwin
goarch: amd64
pkg: github.com/Brian-Williams/retry
BenchmarkDo1-8                          30000000                47.6 ns/op
BenchmarkDoWithConfigurer1-8            30000000                42.3 ns/op
BenchmarkDo2-8                          30000000                46.6 ns/op
BenchmarkDoWithConfigurer2-8            30000000                42.4 ns/op
BenchmarkDo10-8                         30000000                46.6 ns/op
BenchmarkDoWithConfigurer10-8           30000000                42.6 ns/op
BenchmarkDo100-8                        30000000                46.6 ns/op
BenchmarkDoWithConfigurer100-8          30000000                42.1 ns/op
BenchmarkDo10000-8                      30000000                46.6 ns/op
BenchmarkDoWithConfigurer10000-8        30000000                42.2 ns/op
PASS
ok      github.com/Brian-Williams/retry 14.448s

Thank you for the report. This is bug of this action. This action does not assume go test -bench can measure <1 ns values. I'll fix this.

I fixed this at v1.6.7.


Mounting NFS shares hangs on Fedora 20

Following the documentation for NFS shares on my Fedora 20 desktop, I uncomment this in Vagrantfile:
config.vm.synced_folder ".", "/home/core/share", id: "core", :nfs => true, :mount_options => ['nolock,vers=3,udp']

Then I vagrant reload and the process hangs here:
==> core-01: Mounting NFS shared folders...

The process resumes when I do this in a separate terminal:
sudo systemctl stop firewalld

If nobody else already knows the work-around, I'll see if I can come up with a pull request soon(ish).

Yes, I too had the same issue with Fedora 21. Stopped the firewall service, and the box resumed. Thanks for the tip.


When creating an organizational admin user, admin rights are not correctly set

Context
As an owner, when creating a new organizational admin user, admin rights are not correctly set
Steps to Reproduce

Create a new user
Assign admin rights

Current Result
User is created, but not with admin right, requiring an edit to the user settings.
Expected result
An admin user is created
cc @kevin-reilly

I was just trying to test this in staging again but I don't see the "admin" option when creating a user for my account anymore.
I'm looking here: https://kevinsband.carto-staging.com/u/kreilly/organization/users/new

@kevin-reilly that's more or less expected. We have several different servers in staging, and we deploy new functionalities to each of them to test. Most likely, the server where your user is, doesn't have this functionality deployed right now.
If you want to test it, please let us know in #builder so we can prepare a staging server for you with the correct code branch.


Add a model cache to avoid running out of storage

All done in the shell, impressive.
Given this isn't based on size of cache, instead a number, do we have an estimate of how many GB 4 could be - it seems a little on the low side?
Will you have a seperate method to append to the CACHE_FILE, we will want to make sure this file doesn't contain duplicate models too.

If the model is already in the file the grep command removes it and then we append the model name to the bottom of the file. That way the file is always ordered from least to most recently used. When we remove lines off the top an delete those directories those are the least recently used models.


Updated README.md

Codecov Report

Merging #32 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #32   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          10     10
  Lines         220    220
=====================================
  Hits          220    220

Flag
Coverage Δ

#spark_chamber
100% <ø> (ø)
:arrow_up:

#spark_kit
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Chain RUN commands in Java Dockerfiles

Updates all Dockerfiles in the java folder to conform to best practices for saving space. See #26 for similar changes.

Thanks!


Request ARG whitelist or usedlist

MODSEC-379: Hi
To avoid false positive, it could be great to be able to whitelist a request ARG or Cookie.
It could also be great to declare an ARG "usedlist".... an exhaustive list of the ARGS used by an application that need to be checked by modsecurity. Modsec would not check ARGS that are not on this "usedlist"... for example, it could avoid false positive when receiving requests containing ARGS added by a referer.

Actually, the fix is trivial.
The code would allow to modify the ARGS collection (same for cookie); we're using this for a long time.
It simply isn't enabled for these collections - which is a pity.
I'd love to advocate to include this feature, although I know that some people are reluctant to include advanced features that basic users don't understand easily :-(
Example for allowing ARGS modif (in 2.9.x): in re_actions.c, before the line
if (target_col == NULL) {
add
if (strcasecmp(col_name, "ARGS") == 0) {
target_col = msr->arguments;
}
The same can be done for COOKIES or any other collection and it allows to remove an entry from the collection!


Demo doesn't work.

I'm totally newbie about javascript, css and html, but cloning from master, I think that the demo is not working properly. Placing zxcvbn dir in my www directory, and pointing my browser to http://myserver/zxcvbn/demo/index.html shows two working links to Dropbox introduction and github code, an input field that when filled doesn't do nothing and an empty "Examples" section.
I tried to add:

to actually load the javascript (no signs of zxcvbn-async.js in the whole repo) and call:

in the middle of the examples div, with no luck.

Thanks and cheers
Avio

Ok, coffee files need to be converted to javascript.
#> sudo apt install coffeescript
and
#> coffee -c demo.coffee
solved the problem (on Ubuntu 14.04 x86_64).

should probably add that to the readme or package.json


Bots cannot use editApplicationCommandPermissions endpoint

Issue
editApplicationCommandPermissions requires a Bearer token so rn it's useless.
https://discord.com/developers/docs/interactions/application-commands#edit-application-command-permissions
To Reproduce
await editApplicationCommandPermissions(bot, id, cid, [{
    type: ApplicationCommandPermissionTypes.Role,
    id: Roles.everyone.toString(), permission: false
}, {
    type: ApplicationCommandPermissionTypes.Role,
    id: Roles.moderator.toString(), permission: true
}]);

Expected behavior
The function should update the permissions of a command to the specified roles.
Results in
{"message":"Bots cannot use this endpoint","code":20001}
Notes:
Should this function be removed? I've been told by user @Skillz4Killz (Skillz4Killz#8840) the following:

I don't think thats possible, it's only possible by user land UNLESS you go through oauth on a website and have them give u a bearer token to use and that makes changes with the USERS token not the bots token
right now bots cant do that

I know this bug / issue we have rn.
I'll look in how to implement a good fix for that later.

Could you test whether the PR #2238 fixes your issue?


fix(contributing): improve checklist

Summary of Changes
Replaced checklist under https://falcon.readthedocs.io/en/latest/community/contributing.html#reviews with bulleted list.
Related Issues
#2318

Thank you for the feedback @vytas7!
I will look further into this to see alternative ways.


Make sure all HTTP requests allow redirects.

What's this PR do?
Makes sure all HTTP requests allow redirects.
Background context
The various HTTP calls were not consistent in this regard.

Codecov Report

Merging #46 (06d1c29) into main (45510d9) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #46   +/-   ##
=======================================
  Coverage   99.09%   99.09%
=======================================
  Files           9        9
  Lines         444      444
=======================================
  Hits          440      440
  Misses          4        4

Flag
Coverage Δ

unittests
99.09% <100.00%> (ø)

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

Impacted Files
Coverage Δ

urlbox/urlbox_client.py
100.00% <100.00%> (ø)

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 c62b7fd...06d1c29. Read the comment docs.


enable var.x application

add var.x to the ctests

use BUMP covariance in the yaml
use the sample observations that are already in this repository

@travissluka I have uploaded some source/yaml files for this issue. Please help check the "var.yml", and pay attention to my comments which are from test results.
Currently the test_umdsst_var failed due to error message
"LinearGetValues::setTrajectory,unkown state variable"
which is from file LinearGetValues.cc, function
void LinearGetValues::setTrajectory(const State & state, const util::DateTime & t1, const util::DateTime & t2, ufo::GeoVaLs & geovals)
where "In LinearGetValues::setTrajectory(), i = 0, vars[i] = air_pressure_levels", which is not equal to sea_surface_temperature. Not sure how this "ufo::GeoVaLs & geovals" get this vars[0] = air_pressure_levels. I'm using grep to check its origin.
Let me know if you have any clue or suggestions.

@travissluka I have uploaded some source/yaml files for this issue. Please help check the "var.yml", and pay attention to my comments which are from test results.
Currently the test_umdsst_var failed due to error message
"LinearGetValues::setTrajectory,unkown state variable"
which is from file LinearGetValues.cc, function
void LinearGetValues::setTrajectory(const State & state, const util::DateTime & t1, const util::DateTime & t2, ufo::GeoVaLs & geovals)
where "In LinearGetValues::setTrajectory(), i = 0, vars[i] = air_pressure_levels", which is not equal to sea_surface_temperature. Not sure how this "ufo::GeoVaLs & geovals" get this vars[0] = air_pressure_levels. I'm using grep to check its origin.
Let me know if you have any clue or suggestions.

you're using the wrong observation operator. it should be Identity. also the covariance model for the observation should be diagonal. I'm not sure where obs type came from, remove it
Make your window length 24 hours, and the background date at 12Z, otherwise i think a large number of the test observations will be removed. the variational...increment.date should be the same as the background date

you're using the wrong observation operator. it should be Identity. also the covariance model for the observation should be diagonal. I'm not sure where obs type came from, remove it
Make your window length 24 hours, and the background date at 12Z, otherwise i think a large number of the test observations will be removed. the variational...increment.date should be the same as the background date

@travissluka Now it can run, but the result increment and those cost functions are like missing values. Could it be related to issues #38 ~ #40? Should I finish these rest issues and then come back to this one? Also please help check my new var.yml on github at branch feature/var.x. Below are some output to give you an idea what's wrong.
11:   Quadratic cost function: J   ( 4) = 5.062988689257226e+78
11:   Quadratic cost function: Jb  ( 4) = 5.071143924289982e+77
11:   Quadratic cost function: JoJc( 4) = 4.555874296828227e+78
......
11: Write Increment: done.
11: CostFunction::addIncrement: First guess:min = -1.79001, max = 31.8058, mean = 13.1571
11: umdsst::ModelAuxControl not implemented
11:
11: CostFunction::addIncrement: Increment:min = -2.31779e+38, max = 4.54771e+38, mean = 1.87764e+37
11: umdsst::ModelAuxIncrement not implemented
11:
11: CostFunction::addIncrement: Analysis: min = -2.31779e+38, max = 3.78795e+38, mean = 2.65433e+36
11: umdsst::ModelAuxControl not implemented
11:
11: Test     : CostFunction::addIncrement: Analysis: min = -2.31779e+38, max = 3.78795e+38, mean = 2.65433e+36
11: Test     : umdsst::ModelAuxControl not implemented
11:
11: Variational: incremental assimilation done 1 iterations.
11: In Fields::write(), missing_ = -3.33477e+38

@travissluka Now it can run, but the result increment and those cost functions are like missing values. Could it be related to issues #38 ~ #40? Should I finish these rest issues and then come back to this one? Also please help check my new var.yml on github at branch feature/var.x. Below are some output to give you an idea what's wrong.
11:   Quadratic cost function: J   ( 4) = 5.062988689257226e+78
11:   Quadratic cost function: Jb  ( 4) = 5.071143924289982e+77
11:   Quadratic cost function: JoJc( 4) = 4.555874296828227e+78
......
11: Write Increment: done.
11: CostFunction::addIncrement: First guess:min = -1.79001, max = 31.8058, mean = 13.1571
11: umdsst::ModelAuxControl not implemented
11:
11: CostFunction::addIncrement: Increment:min = -2.31779e+38, max = 4.54771e+38, mean = 1.87764e+37
11: umdsst::ModelAuxIncrement not implemented
11:
11: CostFunction::addIncrement: Analysis: min = -2.31779e+38, max = 3.78795e+38, mean = 2.65433e+36
11: umdsst::ModelAuxControl not implemented
11:
11: Test     : CostFunction::addIncrement: Analysis: min = -2.31779e+38, max = 3.78795e+38, mean = 2.65433e+36
11: Test     : umdsst::ModelAuxControl not implemented
11:
11: Variational: incremental assimilation done 1 iterations.
11: In Fields::write(), missing_ = -3.33477e+38

Yes, the missing values are causing problems.
What you can do is add a background check QC filter to the yaml file. (see https://github.com/JCSDA-internal/soca/blob/504cf79ecd216528be17d300c2a829c8aa14a62e/test/testinput/3dvar_soca.yml#L115-116 for an example) which will remove any observation where the interpolation is messed up. This should let you get a "working" 3dvar where the analysis doesn't look completely crazy (yay!) before we move on to making it work "correctly".

Yes, the missing values are causing problems.
What you can do is add a background check QC filter to the yaml file. (see https://github.com/JCSDA-internal/soca/blob/504cf79ecd216528be17d300c2a829c8aa14a62e/test/testinput/3dvar_soca.yml#L115-116 for an example) which will remove any observation where the interpolation is messed up. This should let you get a "working" 3dvar where the analysis doesn't look completely crazy (yay!) before we move on to making it work "correctly".


Connecting to the supervisor... over and over.

Hi,
I am trying to start the mysterium-vpn-desktop on ubuntu lts(started on virutal machine).
When I run yarn dev, this message appears: Connecting to the supervisor... over and over.
How can I solve this?
I would like to add that there is no socket called  cd /var/run/myst.sock on my system.

chrisooo3 Are you still experiencing this same issue?

@isaackielma
I am now experiencing this problem.
For further details on my installation, look at issue #468.


Environment Documentation

Pertains to docker, flask, and travis-ci

What exactly about flask and travis did we want to document?

That's up to you. Whatever you think would be useful for future users/developers to know. At the very least, give a link to the documentation sources for flask and travis.

Feel free to any additional information and changes, but there should be sufficient information to close this issue.


Content of 2 tabs in one after update to 0.92.0

Home Assistant release with the issue:
0.92
Last working Home Assistant release (if known):
0.91.4
Operating environment (Hass.io/Docker/Windows/etc.):

System param
value

arch
x86_64

dev
false

docker
true

hassio
false

os_name
Linux

python_version
3.7.3

timezone
Europe/Paris

version
0.92.0

virtualenv
false

lovelace mode
auto-gen

Component/platform:
lovelace auto-gen
Description of problem:
Steps to reproduce:

Go to a lovelace tab, "Systems" tab for instance
Go to the "Configuration" tab
Go to a lovelace tab

The new lovelace tab content is gonna be at the bottom of the page, and the old -a.k.a the "Systems"- tab content is gonna be at the top.
Screenshot :

configuration.yaml
# Enables the frontend
frontend:

Traceback (if applicable):
No browser console log

/move to home-assistant-polymer


Vickel: Watch 3dversedesign.com

Vickel requests the watch of the watch_keyword 3dversedesign\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

3dversedesign\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by double-beep in Charcoal HQ


Opt-in not to serialize a YAML time string to JSON Date object

I met a case when I want to transform a YAML file with
"Version": "2010-09-09"

js-yaml will automatcially transform it to
"Version": [Date: 2010-09-09T00:00:00.000Z]

Is it possible to choose not to do this !!timestamp change?

Oh! I figured it out by using
JSON_SCHEMA - all JSON-supported types: http://www.yaml.org/spec/1.2/spec.html#id2803231

Since it doesn't contain the timestamp change. Problem solved~


Adds upstream envs for daint_v1 and tsa_v1.

This PR implements #601.
Before this PR is merged, we need to:

[x] discuss the design
[ ] test the POC thoroughly

I brought back the old claw package, because the one from spack/spack threw the following error:

Carlos, Xavier and I agreed to not use an upstream on Tsa.

Implemented in another PR


test/e2e: Disable the s3 bucket test installation by default.

This test is potentially problematic as we're creating a bucket in an AWS account we don't have any governance over. We should just disable this test for now as periodic jobs would've run this test case in it's current form until we touch base with DPTP.

/override ci/prow/metering-e2e-aws
/override ci/prow/metering-upgrade-aws


Upgrade Vert.x version to 3.5.3

We plan to upgrade Vert.x version from 3.5.1 to 3.5.3, release notes to validate:

https://github.com/vert-x3/wiki/wiki/3.5.2-Release-Notes
https://github.com/vert-x3/wiki/wiki/3.5.3-Release-Notes

https://github.com/Cognifide/knotx/pull/445
https://github.com/Knotx/knotx-dependencies/pull/10

It looks that all modules are valid with 3.5.3.

Fixed.


Add2App on iOS doesn't show symbolicated stack traces in Xcode when a crash occurs in Flutter in Debug builds

The documentation here https://github.com/flutter/flutter/wiki/Crashes suggests
The dSYM file for App.framework (which contains the app-specific code) can be located in the directory of your app under build/dSYMs.noindex/App.framework.dSYM for release and profile builds created with flutter build ios.

However, in an Add2App flutter module's .ios/Flutter/ directory, the App.framework.dSYM is missing.
Also, when building in debug, whenever a crash does happen in the Flutter framework, there is no useful stack trace, and I'm not sure how to get those symbols.

@dnfield  Any suggestions for this?
Thanks

I think it should still show up in your build directory for the Flutter module.  Is it not?

 Thanks, I hadn't noticed that.
Do you have any thoughts on the Debug case? It would be nice to get useful stack traces too in Debug so we can report crashes with good information.

You should be able to load the symbols in Xcode when debugging the app. There's probably some way we can make that better, but I'm not entirely sure.  Maybe @xster or @chinmaygarde would know?

Or @jmagman

Would it be possible to have a Flutter.Framework.dSYM file created? I think that would cause XCode to load it automatically.
It might help to also note that we do not use cocoapods, to that might also be something that pods would do automatically, and I'm just missing one step to generate that file?

Oh, and I'd like to mention, while we're on the topic, that for some reason, starting with Flutter 1.10 (I think), the flutter executable inside the artifacts/engine/ios-release/Flutter.framework is 368MB in size. Flutter 1.9 didn't have this issue.
Once we build our app though, the app doesn't seem to increase any bigger than before, so I'm not sure what all that extra size is for, but does this need to be bugged up separately, or is it expected?

Expected - see https://github.com/flutter/flutter/issues/47101

Sweet, thanks @dnfield . I have to admin I had a a moment of panic when I did first see this a few weeks ago, but once I verified our final app size didn't increase, I figured there had to be an explanation.
Thanks for linking that!

@dnfield Should we rename this bug seeing you told me where to find the dSYM file in Release builds?
This bug can remain open specifically for how to get debug information with Add2App debug builds.

Sounds good to me

I think it should still show up in your build directory for the Flutter module. Is it not?

@dnfield I've just updated to the latest 1.16.2 dev build, and now the App.framework.dSYM file is no longer anywhere to be found when building the Add2App module. It's not in the build or .ios directories.
This is now breaking our builds. Do you have any suggestions for this?
Thanks

/cc @jonahwilliams
Do you need these symbols to do debugging?  Jonah and I were discussing this recently and the symbols ended up getting dropped with the idea that they're not going to be all that helpful since all the lines would point to generated assembly.

Well we are just including all symbols for Flutter in Firebase crashlytics in case any crashes happen in Flutter code. If the symbols for the App framework aren't going to be useful, then I'm totally ok with dropping it.
Thanks.

If you're seeing any negative impact please let us know.  It's definitely possible to get them back.

Discussion was on https://github.com/flutter/flutter/pull/49628. But it may not be relevant for you @dannyvalentesonos. You've used Flutter.framework and App.framework interchangeably but they're following 2 different processes. Flutter.framework's dSYM are stripped by our build servers. Your local tools aren't involved. App.framework was where we removed the dSYM recently. It was generally useful for me to have the symbols from the Dart compiled binaries to use Instruments etc. But it should be very unlikely you end up seeing a crash stack inside App.framework. If you do, it means the Dart compiler produced something wrong. It's much more likely that you find a Flutter.framework crash in the engine.
Can you clarify?

If you really need it, remove this line https://github.com/flutter/flutter/pull/49628/files#diff-77d60a41797d03aa9a7de0c742b17ef1R140

@xster It's totally fine to not have it. I just wasn't sure if it was needed, as we were uploading it for crashlytics purposes, but if it's not important, I'm fine with that. Thanks!

Let's fix the wiki text then.

Done, see https://github.com/flutter/flutter/wiki/Crashes/f393b795c90b81f79c61b59bb0f6ac4a8ba92fc9.
Closing!


Cannot wait to see the code

Hi, Didrik:
I want to try flow-vae in Speech Synthesis, when will you open the code?
Feiteng

Hi Feiting,
That sounds really cool, looking forward to the results :-)
I will try to release the code this week (worst case next week).
Best,
Didrik
lør. 15. aug. 2020 kl. 07:43 skrev Feiteng<EMAIL_ADDRESS>
Hi, Didrik:
I want to try flow-vae in Speech Synthesis, when will you open the code?
Feiteng
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/didriknielsen/survae_flows/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE77MNGTAR22DYRTHF3DQGTSAYOBDANCNFSM4QADFGOQ
.


stats.distributions does not have trapezoidal distribution

The continuous distributions in scipy.stats do not contain the trapezoidal distribution. We have two limiting cases, uniform and triang, but not the parent.

There also seems to be a generalised trapezoidal distribution:
http://www.inside-r.org/packages/cran/trapezoid/docs/Trapezoid