timeout does not clean up processes started by 'command'

Set a command like:
module.exports = {
  command: 'npm run start',
  launchTimeout: 1000,
}

If the timeout occurs, you get this message:

Server has taken more than 1000ms to start.

The problem here is that jest-process-manager then never sends the proper signals to the processes started by the command, meaning they get hanging. As a comparison, pressing ctrl+c after the server has started properly cleans up the resources.
To Reproduce
Add the above config and a very short launchTimeout and notice how the started command never stops (check e.g. via the ps command).
Expected behavior
jest-process-manager should send the proper signals to launched command, even after a launchTimeout occured.

Same issue here - trying to start a webpack server but when the timeout is exceeded, jest terminates but webpack keeps on running forever

I know that it was quite old issue. But can someone produce representation? Cause I can't figure out on the problem

@mmarkelov I am unsure if I read your sentence correctly, but do you mean if we can explain it better?
Try creating a long-running process in command and a short timeout for launchTimeout e.g. 10 ms.
Then do a ps aux | grep command for the command you ran, and you will notice it got stuck hanging and never cleaned up properly.
When launchTimeout occurs, you need to send a SIGTERM followed by SIGKILL (after 10 sec which many tools do) to the PID started by command.

@thernstig what is your OS? I can't reproduce it on my MAC machine

@mmarkelov maybe this has been fixed since then? I can try again later possibly.

@thernstig it will be nice. Also I added some cleanup functionality in catch block, so I hope it will help

@mmarkelov I can still re-create this, so I took a look at the code. I believe I found multiple things that can cause errors, unless I am misreading the code.

This is what I believe should kill the processes if the waitOn() times out from a normal timeout:

https://github.com/playwright-community/jest-process-manager/blob/0fd77b16c82df3ed63150fdba33265e742b0c46c/src/index.ts#L246-L257
Note that this only sends a killProc() to a port. I am not sure why this assumption is taken in the code. Even though a program might wait for a port, the kill signal should be sent to the process that was started by command.  E.g. in our case we use npm start with starts several subprocesses through a program called concurrently. One of them is a server we wait for. But the kill signal should be sent to "npm start" and the process it starts, so it in turn can send the signal to concurrently.

In the case no port is configured it looks like this:

https://github.com/playwright-community/jest-process-manager/blob/0fd77b16c82df3ed63150fdba33265e742b0c46c/src/index.ts#L258-L260
and this piece of code seems to properly call treeKill() on the spawned process.

And if we come back to what was reported in this issue, it is that when I press ctrl+C (which sends a SIGINT), I cannot see that being handled anywhere in the code and sent to the appropriate process. I cannot see it in either case of config.port being present or not (the if-else branches).

Am I missing something in all of this?

@thernstig So if I understood you correctly , I should check out the cases when port is not provided?

Point 1 and 3 should be checked out. Point 1) is about a port being provided. Point 3) is about pressing ctrl+c.

Point 1 and 3 should be checked out. Point 1) is about a port being provided. Point 3) is about pressing ctrl+c.


Cannot convert to IReadOnlyList<my_type> from System.String while migrating to .net8 isolated from .net6 in-process

Description
On a previous post regarding the same error, the solution was mentioned as moving to Microsoft.Azure.Functions.Worker.Sdk version 1.16.1. I am on the latest sdk(1.17.4) but I am still facing this issue.-
Function 'xyz', Invocation id 'abc': An exception was thrown by the invocation.
Result: Function 'xyz', Invocation id 'abc: An exception was thrown by the invocation.
Exception: Microsoft.Azure.Functions.Worker.FunctionInputConverterException: Error converting 1 input parameters for Function 'xyz': Cannot convert input parameter 'input' to type 'System.Collections.Generic.IReadOnlyList`1[my_object_type]' from type 'System.String'. Error:System.Text.Json.JsonException: The JSON value could not be converted to Enums.type. Path: $[0].entityType | LineNumber: 0 | BytePositionInLine: 340.
Please suggest how to resolve this issue.
Steps to reproduce
Create a test CosmosDB trigger isolated azure function.
Run the code and put break point to see if the function was called and this error comes up.

@dhananjaytyagi24
I followed the two steps you provided for the reproduction, but I wasn't able to replicate the error you described.
Are there any specific steps I might be missing? Could you follow the two steps mentioned in the "Steps to Reproduce" section to see if you still encounter the error? If so, there might be a difference between our reproductions. Once you identify any additional factors, please share that information, and we will be happy to investigate further.

Found any solution yet for this @dhananjaytyagi24 ?

@dhananjaytyagi24  Are you using the migration tool to do the net6 to net8 migration?

No solution yet. Yes, I used the migration tool to upgrade to .net8
On Tue, Aug 6, 2024 at 1:41 PM Shyju Krishnankutty @.***>
wrote:

@dhananjaytyagi24 https://github.com/dhananjaytyagi24 Are you using the
migration tool to do the net6 to net8 migration?
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-functions-dotnet-worker/issues/2621#issuecomment-2272111752,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJGIU4KTANVSGGMVJBJBGQDZQEYILAVCNFSM6AAAAABLJFPXDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZSGEYTCNZVGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Regards
Dhananjay Tyagi


duplicate DidOpenTextDocument

I'm using ra-multiplexer with neovim and lsp.
It all works fine when I open a new project for the first time. After closing and re-opening the editor (neovim) ra-multiplexer logs the following error:
[ERROR] [/my/project 1558707] [ERROR rust_analyzer::handlers::notification] duplicate DidOpenTextDocument: /my/project/src/main.rs

Everything seems to be working fine, but inlay_hints just disappear. Not sure if it's a ra-multiplexer bug or not.

If the issue is in a workflow like open file A -> close editor with file A -> open file A again. Then it sounds like a bug with neovim's LSP implementation because it never sent the corresponding Close notification, assuming the server was going to close anyway so why bother with cleanup.
Docs here https://microsoft.github.io/language-server-protocol/specifications/specification-3-15/#textDocument_didOpen
However we might want to support opening the same file from multiple neovim instances at once at which point we'd have to explicitly handle this even if neovim was behaving properly because we'd have to silence the second Open and the first Close.

I see, thanks!
Wouldn't it make sense for ra-multiplex to send the close notification upon client disconnection?

Yes, we could implement workarounds for misbehaving clients, I'm not opposed to it. We already implement some workarounds for the init messages.


Remove View reference has it s not supported in angular 2 beta 12

Hello
Can you remove the reference to View and update the project to use the latest beta of angular ?
See: angular/angular#7658

@yahyaKacem already removed
follow beta.12 milestone


[CODE] Contants from multi-nested yaml

Allow yamls to have sub-dictionaries

[x] Fix apero-core to allow this
[x] Import apero-core into SOSSISSE
[  ] convert all CDICT to CDict (APERO Constant Dict) and change code references
[  ] required=True   no longer in CDict --> use not_none
[  ] remove sources (ParamDict has .set_source etc)
[  ] "modes" not in CDict (Const)
[  ] "length" not in CDict (Const) - needs a condition against it in validation

Problem in aperocore.constants.load_functions.load_from_yaml
Code:
 flat_dict = base_class.FlatYamlDict(yaml_dict, max_level=3)

Means nested-dict loaded as flat dictionary --> needs fixing before we can continue.


current_version and reusing existing upgrades are broken

Upgrading an out-of-date workflow creates a new version, but current_version still refers to the old version. This breaks the use of current_version to map the current pipeline to workflow executions (used by PROV exporter #1075 #1076).
Switching to a different version node and back always creates a new upgrade version. The existing upgrade is not used!

This may be related to hide-upgrades #1046

The intention was for current_version to still point to the actual (e.g. upgraded) version. In fact, I added current_base_version for the original (parent of the chain of upgrades).

Looks somewhat related to #1052

As @remram44 noted, this looks like an issue when we have unflushed upgrades. We cannot rely on current_version pointing to the same pipeline as current_pipeline. If we need a specific pipeline version we need to construct the pipeline from the vistrail (or flush the upgrade, but we may not want that). This is probably only relevant in a few cases, such as the provenance export.


Istio upgrade results in 503 and connectivity issues

Describe the bug
Upgrade tests are now run in automated release qualification daily. They tests both version upgrade and downgrade. These tests are currently made to tolerate some errors, including 503s and connectivity problems.
It is not a regression as running similar upgrade tests from 1.0.0 to 1.0.2 result in similar errors.
Example:
Upgrade tests from 1.0.2 to daily 1.0.X releases (i.e. release-1.0 branch).
https://storage.googleapis.com/istio-prow/pr-logs/pull/istio-releases_daily-release/1314/daily-upgrade-tests-1.0.2/262/build-log.txt
Upgrade tests from 1.0.2 to daily 1.1 releases (i.e. release-1.1 branch).
https://storage.googleapis.com/istio-prow/pr-logs/pull/istio-releases_daily-release/1309/daily-upgrade-tests-1.0.2/260/build-log.txt
Search for something like
Code  -1 : 322 (4.6 %)
Code 200 : 6647 (95.3 %)
Code 503 : 7 (0.1 %)
Expected behavior
No 503s, or no connectivity issue
Steps to reproduce the bug
They run everyday and can be monitored https://github.com/istio-releases/daily-release/pulls?utf8=✓&q=is%3Apr+"Release+Qualification".
Alternatively, these tests can run separately using https://github.com/istio/istio/blob/master/tests/upgrade/test_crossgrade.sh
Version
Kubernetes 1.9
Installation
N/A
Environment
GKE

/cc @duderino

/cc @mandarjog

503 are caused often when control plane is down.   During the upgrade, does the control plane have HA?  If so, were the upgrade rolled to the control plane components in a way that is not causing down time.

That's a very good observation Lin. We'll try it with HA, and we should make this a requirement for 503-free upgrades.

Also updated bug description to reflect the current state.

+1 thanks @ostromart @hklai

It would be good to test if 503s repeat when mixer is set to fail open.

Also instead of simply doing helm upgrade or some such thing, add new version of mixer pods, delete the labels from old mixer deployment, wait for a couple of minutes and then delete old mixer deployment.
This is the issue with rolling in place upgrades.

That is a great point @rshriram.   Per this user, 503 went away when mixer policy is disabled:  https://groups.google.com/forum/#!topic/istio-users/JIUfrIX3zs4

@linsun did you mean to close this?  if so please close


Navigate to an unmatched webpage after clicking link 'online release notes' in Release Notes

Storage Explorer Version: 1.10.0
Build: 20190911.4
Branch: master
Platform/OS: Windows 10/ Linux Ubuntu 19.04/macOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer.
Click 'Help' menu -> Select 'View Release Notes'.
Click the link 'online release notes' at the end of the release notes page.

Check the result.

Expect Experience:
Navigate to a right webpage.
Actual Experience:
Navigate to an unmatched webpage.

This is expected since we haven't published the Release Notes yet. Since we are using forwarding link, it doesn't go with the application and will show the correct page then.


lib/types.nix: fix missing inherit

I think there was a silent (i.e. semantic) merge conflict between PR #101139 and
PR #100456.  This commit should fix the error, which manifests as follows:
error: undefined variable 'boolToString' at /home/kkini/src/nixpkgs/lib/types.nix:552:42

Motivation for this change
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I can confirm that this fixes nixpkgs eval (locally on my machine).

I can confirm that this fixes nixpkgs eval (locally on my machine).

+1

It's not clear to me why ofborg failed. The fix looks good.

Thanks for merging.
I'm not really sure, but I think in the last few months ofborg has started marking commits as failed while they're in its queue and then changing them to succeeded once the evaluations succeed, as opposed to the former behavior where it would log itself as having "started" the check even though it was actually just queued in the backlog.
I assumed the change was made because some kind of problem was occurring when github checks were in the running state for too long, or something. But I guess it also means that now if you merge a PR before ofborg gets to it, the commit will be marked as failing forever (?). Oh well.

It's not clear to me why ofborg failed. The fix looks good.

I think this is because eval on master failed but don't quote me on that.

@SuperSandro2000 That's correct. The ofborg eval failed because master failed to eval at that point in time (despite this PR fixing that).
@kini This is because of proponents of GitHub Actions. Without this immediate failure, the editorconfig check used to give PRs a green checkmark, making people think they are good to merge, even though they're still working through ofborg. Whether this is good or bad is subjective, but that's why it is. (Note: it's not ofborg marking the PR as failed (unless it should be), but a GitHub Action.)


client: perf/WhereCache

Fix #365

// Create a Conditional API from a Function that is used to filter cached data
// The function must accept a Model implementation and return a boolean.  Most (all?) uses of WhereCache() already have a model that the predicate uses.

Emm, I found it difficult to get table information from the predicate callback function since model.Model is just an interface, not a struct. I cannot create a model.Model instance and call Table().

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

27 of 33 (81.82%)  changed or added relevant lines in 7 files are covered.
12 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 75.865%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

client/api.go
17
20
85.0%

ovsdb/serverdb/database.go
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

client/api.go
12
79.28%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
5284

Relevant Lines:
6965

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

27 of 33 (81.82%)  changed or added relevant lines in 7 files are covered.
14 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.2%) to 75.822%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

client/api.go
17
20
85.0%

ovsdb/serverdb/database.go
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

client/client.go
2
73.68%

client/api.go
12
79.28%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
5281

Relevant Lines:
6965

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

27 of 33 (81.82%)  changed or added relevant lines in 7 files are covered.
14 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.2%) to 75.822%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

client/api.go
17
20
85.0%

ovsdb/serverdb/database.go
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

client/client.go
2
73.68%

client/api.go
12
79.28%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
5281

Relevant Lines:
6965

💛  - Coveralls


Emberwind [Bugfix] Small updates and fixes

updated init and skill rolls
updated npc actions roll template
remove unused images

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[x] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Updated init and skill rolls
Updated npc actions roll template
Removed unused images

Character Sheet Info Roll20 Internal Use only.


Unable to run most sample on composer Build taken on 14th May 2018

Description:
Unable to run any sample on composer Build taken on 14th May 2018
Steps to reproduce:
1.try to run basic samples on composer
Affected Versions:
Ballerina 0.970.1-SNAPSHOT
OS, DB, other environment details and versions:
Ubuntu 16.04/ Windows 10
java version "1.8.0_131"

keeping the issue reopened

fixed with https://github.com/ballerina-platform/ballerina-lang/pull/8706


Managed artifacts

Currently if we delete a component it deletes all artifacts. This is a problem if these are shared between components - e.g. templates and applications.

Solved by #2446.


cpu or gpu

When training the model, can we use CPU instead of GPU?

The easiest way to do this would be to set the environment variableCUDA_VISIBLE_DEVICES=3, where 3 is a number that is larger than the number of gpus present in your machine. This will prevent tensorflow from using the gpus. So you can do something like:
$ CUDA_VISIBLE_DEVICES=3 python train.py ....


WeightedLinearModel.save JSON precision too small

Problem description
When exporting a trained model using WeightedLinearModel.save, floats are formatted using Python's format with the "g" parameter that has a default precision of 6.
The class that handles this is CompactJSONEncoder:
https://github.com/uf3/uf3/blob/f2ad1a23f5b38695894378803dc54f25139b1a3d/uf3/util/json_io.py#L138-L140
For a model I trained, this precision is too small, resulting in prediction errors when loading the model from the .json file.
Example
I attached the solutions of the model here. The first output shows the solutions directly after training, and the second output shows the solutions after saving and loading.

Solutions after training
{'solution': {'Zr': -20560.33609234794,
'O': -41120.412798809746,
('O',
 'O'): array([ 5.26435439e+00,  5.20311465e+00,  5.08063516e+00,  4.89691593e+00,
        4.65195696e+00,  4.34575824e+00,  3.97831977e+00,  3.54964157e+00,
        3.05972362e+00,  2.50856592e+00,  1.89616849e+00,  1.22868659e+00,
        7.30053245e-01,  4.31556715e-01,  2.46165334e-01,  1.24437004e-01,
        5.93001720e-02,  2.74566934e-02,  1.30984740e-02,  3.16545758e-03,
        8.15071387e-04,  1.64258524e-04, -6.46071392e-03, -9.32398478e-03,
       -1.06880467e-02,  0.00000000e+00,  0.00000000e+00,  0.00000000e+00]),
('Zr',
 'O'): array([ 2.57773141,  2.48379049,  2.29590865,  2.01408589,  1.63832222,
        1.16861763,  0.60497211, -0.05261432, -0.80414166, -1.64960993,
       -2.08524704, -1.9352091 , -1.61253899, -1.27462536, -0.97011593,
       -0.72222357, -0.53059997, -0.37511157, -0.26761948, -0.19630742,
       -0.1364386 , -0.08911125, -0.05464061, -0.02995521, -0.0185196 ,
        0.        ,  0.        ,  0.        ]),
('Zr',
 'Zr'): array([7.63423726, 7.59087987, 7.50416508, 7.37409289, 7.20066331,
       6.98387633, 6.72373196, 6.42023019, 6.07337103, 5.68315447,
       5.24958052, 4.77264917, 4.25236043, 3.68871429, 3.08171076,
       2.43142205, 1.77394657, 1.3332101 , 0.99423793, 0.73174477,
       0.51741219, 0.35220643, 0.2297151 , 0.13608243, 0.05597425,
       0.        , 0.               ,  0.       ,  0.       ]),
 ('Zr',
  'Zr'): array([7.63424  , 7.59088  , 7.50417  , 7.37409  , 7.20066  , 6.98388  ,
        6.72373  , 6.42023  , 6.07337  , 5.68316  , 5.24958  , 4.77265  ,
        4.25236  , 3.68872  , 3.08171  , 2.43142  , 1.77395  , 1.33321  ,
        0.994238 , 0.731745 , 0.517412 , 0.352207 , 0.229715 , 0.136083 ,
        0.0559743, 0.       , 0.       , 0.       ])},
'knots': {('O',
  'O'): array([1.0e-06, 1.0e-06, 1.0e-06, 1.0e-06, 2.0e-01, 4.0e-01, 6.0e-01,
        8.0e-01, 1.0e+00, 1.2e+00, 1.4e+00, 1.6e+00, 1.8e+00, 2.0e+00,
        2.2e+00, 2.4e+00, 2.6e+00, 2.8e+00, 3.0e+00, 3.2e+00, 3.4e+00,
        3.6e+00, 3.8e+00, 4.0e+00, 4.2e+00, 4.4e+00, 4.6e+00, 4.8e+00,
        5.0e+00, 5.0e+00, 5.0e+00, 5.0e+00]),
 ('Zr',
  'O'): array([1.0e-06, 1.0e-06, 1.0e-06, 1.0e-06, 2.0e-01, 4.0e-01, 6.0e-01,
        8.0e-01, 1.0e+00, 1.2e+00, 1.4e+00, 1.6e+00, 1.8e+00, 2.0e+00,
        2.2e+00, 2.4e+00, 2.6e+00, 2.8e+00, 3.0e+00, 3.2e+00, 3.4e+00,
        3.6e+00, 3.8e+00, 4.0e+00, 4.2e+00, 4.4e+00, 4.6e+00, 4.8e+00,
        5.0e+00, 5.0e+00, 5.0e+00, 5.0e+00]),
 ('Zr',
  'Zr'): array([1.0e-06, 1.0e-06, 1.0e-06, 1.0e-06, 2.0e-01, 4.0e-01, 6.0e-01,
        8.0e-01, 1.0e+00, 1.2e+00, 1.4e+00, 1.6e+00, 1.8e+00, 2.0e+00,
        2.2e+00, 2.4e+00, 2.6e+00, 2.8e+00, 3.0e+00, 3.2e+00, 3.4e+00,
        3.6e+00, 3.8e+00, 4.0e+00, 4.2e+00, 4.4e+00, 4.6e+00, 4.8e+00,
        5.0e+00, 5.0e+00, 5.0e+00, 5.0e+00])}}

The most apparent difference is in the one-body offsets:
After training: 'Zr': -20560.33609234794
After loading: 'Zr': -20560.3
Impact on prediction accuracy
This decreased precision noticeably affects the model's performance:
Model with original precision:

Loaded model with 6 digit precision:

Solution
Increasing the accuracy to 20 digits, using format(0, ".20g") instead of  format(0, "g"), solves the issue for my model. However, I cannot assess whether this precision is large enough for other models or if other issues arise from this.
Maybe someone has input on this so that this issue can be resolved.

This problem seems to appears especially for heavy elements (such as Zr) with a sizeable one-body term. For light elements (such as H) the one-body term is ~10 eV and the limited precision has a vanishing impact on the predictions.


Documentation

Adding GHDL as supported simulator
Adding environment variable COCOTB_REDUCED_LOG_FMT

@Martoni From this It looks as if you are volunteering to handle all GHDL related reviews? That would be great if indeed the case as it is one of the areas that we have no knowledge or time to really invest in.

@stuarthodgson I can handle GHDL reviews yes. But I'm just using it in my projects for the moment. I'm not necessarily a GHDL expert but I'm aware to learn.

I can split this pull request in two if ghdl support is a problem.


Add Support for Forcing Cancelling Jobs

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
I want to force cancel jobs with the client library as with the console.
Describe the solution you'd like
I don't know if this request requires changes to the client library. Perhaps it only takes an update to the docs.
Describe alternatives you've considered
N/A.
Additional context

https://cloud.google.com/dataflow/docs/guides/stopping-a-pipeline#forcecancel

It is possible to do this today with the client library using update_job. See the arguments of UpdateJobRequest() here
from google.cloud import dataflow_v1beta3

def sample_update_job():
     job = dataflow_v1beta3.Job(requested_state=dataflow_v1beta3.JobState.JOB_STATE_CANCELLED)

    # Create a client
    client = dataflow_v1beta3.JobsV1Beta3Client()

    # Initialize request argument(s)
    request = dataflow_v1beta3.UpdateJobRequest(project_id=<YOUR_PROJECT>, job_id="job_id", job=job, location=<LOCATION>
    )

    # Make the request
    response = client.update_job(request=request)

    # Handle the response
    print(response)

sample_update_job()

Thanks!


Remove antigen thanks to chezmoi externals

The only outstanding issue is https://github.com/twpayne/chezmoi/issues/1421#issuecomment-926015535.


Add files via upload

@overmind1980 file.zip: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@overmind1980 file.zip: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@overmind1980 file.zip: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@overmind1980 file.zip: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@overmind1980 file.zip: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@overmind1980 file.zip: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@overmind1980 I am sorry, I have to close this request without merging, because you requested to add a non-existent domain (or an incorrectly named folder) to this repository.
Please ensure you are familiar with this repository rules located at the bottom of this page and submit a new request with correct information.
Do not upload file.zip file. Please unzip file.zip file, fork SWOT repository, add unzipped file to your forked SWOT repository to an appropriate folder (most probably, lib/domains/cn/edu), and make a new pull request.
Thank you for the understanding!


Update docs to match current tooling

The menu entry in the VS Code extension for deployment has been changed from "Create deployment for IoT Edge Device" to "Create deployment for Single Device". Text and screenshots should match current tools.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/images/AzureLabs-Lab313-33b.png
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-azure-313.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/images/AzureLabs-Lab313-33b.png
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-azure-313.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


chore(openchallenges): create new EDAM DB

Closes #2605
Changelog

create the DB edam in OC MariaDB instance
create the user edam_etl with write permission to this new DB
create the user edam_challenge_service with read-only permission to this new DB

@mdsage1 This PR provides the DB and user that you need for the EDAM ETL project.


Rebase with new feature

Rebase to include support function params, ignore backquotes commit.

Greetings,
it would be super nice if we could merge this!

We are in process of replacing fork with upstream. I hope it will solve all your issues :)


Clarify CONTRIBUTION.md

Hey, thanks for adding this. In general a necessary addition to the file. Although the bigger problem I found that the js2coffee used in this project differs from the lates js2coffee release as the api and the output changes. At least for me it did. Can you confirm you can build the project with js2coffee successfully?

@Codebryo - It build successfully for me, though it printed out warnings. But on the surface - this worked as anticipated

With the ongoing progress of re-writing Refills (done by @brendastorer and @creuter), which progress can be found in https://github.com/thoughtbot/refills/tree/cr-rewrite, I'm going to go ahead and close this.


Automate updating gcloud sdk

Currently the gcloud SDK is updated by manually running a script. Let's write a small Kotlin program that automates:

GitHub Actions job that runs periodically
Fetch the current gcloud sdk stable version
Check if the stable version is in the repo, if not overwrite the repo with the new release
Push the change to GitHub

https://github.com/Flank/gcloud_cli
I think we can create a bot user scoped only to the gcloud cli and use that token for the automated updates.
https://github.com/Flank/gcloud_cli/issues/1

PR created in Flank/gcloud_cli


WIP: Add context to RK headers

Related to https://github.com/reservoirprotocol/indexer/pull/7427
How can we test this beforehand?


Bring Stable up-to-date

This will bring stable up-to-date, minus a small change to the ReadMe for Docker Compose

What are you trying to do here? You want to change 32 files on the main branch. Is that to bring your own fork up to date?

This is FROM the main branch to the stable branch to bring it up to date.

Did not see that 😀 Merged now


since last update, i've got an error for select tag init.. screenshot below

puts an interesting row to options....
http://i.imgur.com/Et4DZlD.jpg

Weird, I will look into..

Sorry for delay, I couldn't reproduce. Can you provide more details or a piece of code reproducing? Thanks.


Fixed single_pass related bugs of file and folder names.

[ ] Changed validation to val regarding the example of the README.
[ ] Removed the redundant FLAGS.log_root from the dirname.

Thanks @tianjianjiang 👍

My pleasure and thank you, @abisee


OCPBUGS-41689: Allow Encryption at Host to be Independently Toggled from DiskEncryptionSetID

What this PR does / why we need it:
Manual cherry-pick of:

https://github.com/openshift/hypershift/pull/4701
https://github.com/openshift/hypershift/pull/4711

Which issue(s) this PR fixes:
Fixes OCPBUGS-41689
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/close
Don't need this unless ARO HCP decides to pull HO versions from MCE


Add new '--profile-as-json' option for outputing profile data in JSON

Initial discussion started on the Gradle forum: https://discuss.gradle.org/t/add-new-profile-as-json-option-for-outputing-profile-data-in-json/16621

Hi @steffenyount, thanks for the contribution. As proposed in the Gradle forum post, would you mind opening a discussion on the Gradle dev list?
I was wondering if you signed the CLA before. I have an entry in our list of signed CLAs with your last name but a slightly different first name. Could you please provide your email address so I can verify?

re-posted

Hi @steffenyount ,
After some internal discussion and direct discussion with yourself at the Gradle Summit 2016, we've decided not to incorporate this functionality into the core. Instead, we'd like to suggest that you implement this functionality as an external plugin. If you need any advice on how to do this please let us know via the forums and we'll help as much as we can.
I apologise for the long turnaround on this and any confusion caused.

I've finally found the time to refactor my change to what we agreed would be acceptable at the Gradle summit. But it seems this pull request has been closed so I can't update it here.
Please see my updated pull request: #670
The conditions were:

The feature is hidden behind a secret system property ('org.gradle.profile.ProfileAsJsonReportRenderer.enabled')
The JSON report is rendered using the Gson libraries.

Thanks.

Hi, everyone
I saw that this PR was dropped and asked to add it as a plugin, but I can't find any.
Does someone have a recommendation?
Thanks in advance


Uncaught SyntaxError: Octal escape sequences are not allowed in template strings. (Error with html icons)

Good afternoon)
If css styles have an element ::before
content: '🗸', it is converted to content:"\2714" and an error occurs
Uncaught SyntaxError: Octal escape sequences are not allowed in template strings.

Hi @An1984ton maybe we need to add a JSON.stringify to the styleCode.
I can fix this problem, give me 2 hours and you will have the new version with the fix.
Thanks for reporting

Good afternoon) If css styles have an element ::before content: '🗸', it is converted to content:"\2714" and an error occurs Uncaught SyntaxError: Octal escape sequences are not allowed in template strings.

@An1984ton the bug is fixed in v1.3.0 😉


Create pages for ECO Azure Spot Policies

Created Azure ECO readonly page
Created Azure ECO full permission page

@bjswoboda, pls see these two pages that @stevenfeltner created. Should we have these pages? If so, please review them. Should I publish as they are or are changes required? Thx

@netapp-jmontel we already have addressed this in https://docs.spot.io/eco/getting-started/connect-azure-ea-to-eco.
We should not publish Steven's pages.

@bjswoboda The feedback we received from customers is that they would like a separate page for the policies so that it's easier to send to security teams for review and approval. Today it's hidden within the doc, where you can easily pass over it as it's not expanded by default. We are looking to replicate the structure we have for AWS for Azure and publish individual separate pages just for the policy.

@stevenfeltner Andy has addressed this in the new version. Only the read permissions are shown in public documentation


Unable to run the simulator on OSX Catalina with Gazebo or jmavsim

Describe the bug
I am able to build PX4, but unable to run it with either Gazbo or jmavsim. They both fail with different errors.
For both I followed the instructions exactly from the Mac guide as well as went through the troubleshooting steps, including doing a make distclean, setting the ulimit and following the instructions for the cmake error.

jmavsim
Gazebo

jmavsim
For jmavsim - Here is the output. Note that the issue seems to be possibly something with the 3D library based on my research. I have tried it both with OpenJDK and Java SE's JDK.
➜  Firmware git:(master) make px4_sitl jmavsim
[0/1] cd /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default/tmp && /Users/foyc/Workspace/p...none /Users/foyc/Workspace/px4/Firmware /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_defaul
SITL ARGS
sitl_bin: /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default/bin/px4
debugger: none
program: jmavsim
model: none
world: none
src_path: /Users/foyc/Workspace/px4/Firmware
build_path: /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default
empty model, setting iris as default
SITL COMMAND: "/Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default/bin/px4" "/Users/foyc/Workspace/px4/Firmware"/ROMFS/px4fmu_common -s etc/init.d-posix/rcS -t "/Users/foyc/Workspace/px4/Firmware"/test_data
INFO  [px4] Creating symlink /Users/foyc/Workspace/px4/Firmware/ROMFS/px4fmu_common -> /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default/tmp/rootfs/etc

______  __   __    ___
| ___ \ \ \ / /   /   |
| |_/ /  \ V /   / /| |
|  __/   /   \  / /_| |
| |     / /^\ \ \___  |
\_|     \/   \/     |_/

px4 starting.

INFO  [px4] Calling startup script: /bin/sh etc/init.d-posix/rcS 0
INFO  [param] selected parameter default file eeprom/parameters_10016
[param] parameter file not found, creating eeprom/parameters_10016
  SYS_AUTOCONFIG: curr: 0 -> new: 1
* SYS_AUTOSTART: curr: 0 -> new: 10016
  BAT_N_CELLS: curr: 0 -> new: 3
  CAL_ACC0_ID: curr: 0 -> new: 1311244
  CAL_ACC_PRIME: curr: 0 -> new: 1311244
  CAL_GYRO0_ID: curr: 0 -> new: 2294028
  CAL_GYRO_PRIME: curr: 0 -> new: 2294028
  CAL_MAG0_ID: curr: 0 -> new: 197388
  CAL_MAG_PRIME: curr: 0 -> new: 197388
  CBRK_SUPPLY_CHK: curr: 0 -> new: 894281
  COM_DISARM_LAND: curr: 2.0000 -> new: 0.5000
  COM_OBL_ACT: curr: 0 -> new: 2
  COM_RC_IN_MODE: curr: 0 -> new: 1
  EKF2_ANGERR_INIT: curr: 0.1000 -> new: 0.0100
  EKF2_GBIAS_INIT: curr: 0.1000 -> new: 0.0100
  COM_ARM_EKF_AB: curr: 0.0017 -> new: 0.0050
  EKF2_REQ_GPS_H: curr: 10.0000 -> new: 0.5000
  IMU_INTEG_RATE: curr: 200 -> new: 250
  MC_PITCH_P: curr: 6.5000 -> new: 6.0000
  MC_PITCHRATE_P: curr: 0.1500 -> new: 0.2000
  MC_ROLL_P: curr: 6.5000 -> new: 6.0000
  MC_ROLLRATE_P: curr: 0.1500 -> new: 0.2000
  MPC_HOLD_MAX_Z: curr: 0.6000 -> new: 2.0000
  MPC_Z_VEL_I: curr: 0.1000 -> new: 0.1500
  MPC_Z_VEL_P: curr: 0.2000 -> new: 0.6000
  MPC_XY_P: curr: 0.9500 -> new: 0.8000
  MPC_XY_VEL_P: curr: 0.0900 -> new: 0.2000
  MPC_XY_VEL_D: curr: 0.0100 -> new: 0.0160
  MPC_SPOOLUP_TIME: curr: 1.0000 -> new: 0.5000
  MPC_TKO_RAMP_T: curr: 3.0000 -> new: 1.0000
  NAV_ACC_RAD: curr: 10.0000 -> new: 2.0000
  NAV_DLL_ACT: curr: 0 -> new: 2
  RTL_DESCEND_ALT: curr: 30.0000 -> new: 5.0000
  RTL_LAND_DELAY: curr: -1.0000 -> new: 5.0000
  RTL_RETURN_ALT: curr: 60.0000 -> new: 30.0000
  SDLOG_MODE: curr: 0 -> new: 1
  SDLOG_PROFILE: curr: 3 -> new: 131
  SDLOG_DIRS_MAX: curr: 0 -> new: 7
  SENS_BOARD_X_OFF: curr: 0.0000 -> new: 0.0000
  SENS_DPRES_OFF: curr: 0.0000 -> new: 0.0010
  TRIG_INTERFACE: curr: 4 -> new: 3
  COM_CPU_MAX: curr: 90.0000 -> new: -1.0000
* RTL_DESCEND_ALT: curr: 5.0000 -> new: 10.0000
* RTL_LAND_DELAY: curr: 5.0000 -> new: 0.0000
  PWM_MAX: curr: 2000 -> new: 1950
  PWM_MIN: curr: 1000 -> new: 1075
  GPS_UBX_DYNMODEL: curr: 7 -> new: 6
* SYS_AUTOCONFIG: curr: 1 -> new: 0
INFO  [dataman] Unknown restart, data manager file './dataman' size is 11798680 bytes
INFO  [simulator] Waiting for simulator to accept connection on TCP port 4560
Buildfile: /Users/foyc/Workspace/px4/Firmware/Tools/jMAVSim/build.xml

make_dirs:

compile:

create_run_jar:

copy_res:

BUILD SUCCESSFUL
Total time: 0 seconds
Options parsed, starting Sim.
Starting GUI...
3D [dev] 1.6.0-pre12-daily-experimental daily

2020-05-07 09:32:02.920 java[94418:1195728] Apple AWT Internal Exception: NSWindow drag regions should only be invalidated on the Main Thread!
2020-05-07 09:32:02.920 java[94418:1195728] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'NSWindow drag regions should only be invalidated on the Main Thread!'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff2e204d07 __exceptionPreprocess + 250
	1   libobjc.A.dylib                     0x00007fff66f285bf objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff2e22d50c -[NSException raise] + 9
	3   AppKit                              0x00007fff2b43424c -[NSWindow(NSWindow_Theme) _postWindowNeedsToResetDragMarginsUnlessPostingDisabled] + 310
	4   AppKit                              0x00007fff2b41bcb2 -[NSWindow _initContent:styleMask:backing:defer:contentView:] + 1416
	5   AppKit                              0x00007fff2b41b723 -[NSWindow initWithContentRect:styleMask:backing:defer:] + 42
	6   libnativewindow_macosx.jnilib       0x00000001246fbf6e Java_jogamp_nativewindow_macosx_OSXUtil_CreateNSWindow0 + 398
	7   ???                                 0x000000010b232407 0x0 +<PHONE_NUMBER>
)
libc++abi.dylib: terminating with uncaught exception of type NSException
/Users/foyc/Workspace/px4/Firmware/Tools/jmavsim_run.sh: line 80: 94418 Abort trap: 6           java -XX:GCTimeRatio=20 -Djava.ext.dirs= -Djavax.accessibility.assistive_technologies=" " -jar jmavsim_run.jar $device $extra_args
^CERROR [px4] Startup script returned with return value: 2
/Users/foyc/Workspace/px4/Firmware/Tools/sitl_run.sh: line 174: kill: (94307) - No such process
ninja: build stopped: interrupted by user.
make: *** [px4_sitl] Interrupt: 2

I would also get a pop-up that the Java runner crashed, at which point I would Ctrl-C the script because it would just hang at that point.
Gazebo
For Gazebo:
➜  Firmware git:(master) make px4_sitl gazebo
-- PX4 version: v1.11.0-beta1-179-g7207301e56
-- PX4 config file: /Users/foyc/Workspace/px4/Firmware/boards/px4/sitl/default.cmake
-- PX4 config: px4_sitl_default
-- PX4 platform: posix
-- PX4 lockstep: enabled
-- cmake build type: RelWithDebInfo
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00033
-- The C compiler identification is AppleClang <IP_ADDRESS>00033
-- The ASM compiler identification is Clang
-- Found assembler: /Library/Developer/CommandLineTools/usr/bin/cc
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Building for code coverage
-- Found PythonInterp: /usr/local/bin/python3 (found suitable version "3.7.7", minimum required is "3")
-- build type is RelWithDebInfo
-- PX4 ECL: Very lightweight Estimation & Control Library v1.9.0-rc1-275-g12835b9
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default
[1/741] git submodule src/drivers/gps/devices
[4/741] git submodule src/lib/ecl
[6/741] git submodule mavlink/include/mavlink/v2.0
[9/741] git submodule Tools/sitl_gazebo
[19/741] Performing configure step for 'sitl_gazebo'
-- install-prefix: /usr/local
-- The C compiler identification is AppleClang <IP_ADDRESS>00033
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00033
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test COMPILER_SUPPORTS_CXX17
-- Performing Test COMPILER_SUPPORTS_CXX17 - Success
-- Performing Test COMPILER_SUPPORTS_CXX14
-- Performing Test COMPILER_SUPPORTS_CXX14 - Success
-- Performing Test COMPILER_SUPPORTS_CXX11
-- Performing Test COMPILER_SUPPORTS_CXX11 - Success
-- Performing Test COMPILER_SUPPORTS_CXX0X
-- Performing Test COMPILER_SUPPORTS_CXX0X - Success
-- Using C++17 compiler
CMake Warning at /usr/local/lib/cmake/boost_system-1.72.0/libboost_system-variant-shared.cmake:64 (message):
  Target Boost::system already has an imported location
  '/usr/local/lib/libboost_system-mt.dylib', which will be overwritten with
  '/usr/local/lib/libboost_system.dylib'
Call Stack (most recent call first):
  /usr/local/lib/cmake/boost_system-1.72.0/boost_system-config.cmake:57 (include)
  /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake:120 (find_package)
  /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake:185 (boost_find_component)
  /usr/local/Cellar/cmake/3.17.2/share/cmake/Modules/FindBoost.cmake:444 (find_package)
  CMakeLists.txt:31 (find_package)

CMake Warning at /usr/local/lib/cmake/boost_filesystem-1.72.0/libboost_filesystem-variant-shared.cmake:64 (message):
  Target Boost::filesystem already has an imported location
  '/usr/local/lib/libboost_filesystem-mt.dylib', which will be overwritten
  with '/usr/local/lib/libboost_filesystem.dylib'
Call Stack (most recent call first):
  /usr/local/lib/cmake/boost_filesystem-1.72.0/boost_filesystem-config.cmake:57 (include)
  /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake:120 (find_package)
  /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake:185 (boost_find_component)
  /usr/local/Cellar/cmake/3.17.2/share/cmake/Modules/FindBoost.cmake:444 (find_package)
  CMakeLists.txt:31 (find_package)

-- Found Boost: /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake (found suitable version "1.72.0", minimum required is "1.58") found components: system thread filesystem
CMake Error at CMakeLists.txt:32 (find_package):
  By not providing "Findgazebo.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "gazebo", but
  CMake did not find one.

  Could not find a package configuration file provided by "gazebo" with any
  of the following names:

    gazeboConfig.cmake
    gazebo-config.cmake

  Add the installation prefix of "gazebo" to CMAKE_PREFIX_PATH or set
  "gazebo_DIR" to a directory containing one of the above files.  If "gazebo"
  provides a separate development package or SDK, be sure it has been
  installed.

-- Configuring incomplete, errors occurred!
See also "/Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default/build_gazebo/CMakeFiles/CMakeOutput.log".
[27/741] Building CXX object src/lib/ecl/EKF/CMakeFiles/ecl_EKF.dir/ekf.cpp.o
FAILED: external/Stamp/sitl_gazebo/sitl_gazebo-configure
cd /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default/build_gazebo && /usr/local/Cellar/cmake/3.17.2/bin/cmake -DCMAKE_INSTALL_PREFIX=/usr/local -DSEND_ODOMETRY_DATA=ON -GNinja /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo && /usr/local/Cellar/cmake/3.17.2/bin/cmake -E touch /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default/external/Stamp/sitl_gazebo/sitl_gazebo-configure
[33/741] Building CXX object src/lib/ecl/EKF/CMakeFiles/ecl_EKF.dir/covariance.cpp.o
ninja: build stopped: subcommand failed.
make: *** [px4_sitl] Error 1

I found https://github.com/PX4/Firmware/issues/5393 from 2016 which talked about needing libgazebo7-dev. It's possible that I missed something in the installation instructions. I wasn't sure if I should install Gazebo from source.
If I can provide any other information or test anything happy to! I know how running an open-source project can be.

I came across the exactly same error with you!  For the first problem, I solved it by https://github.com/PX4/Firmware/issues/14854.

(For anyone following up on this, replacing my Java version as listed in #14854 did not fix the issue, and I never did get PX4 working at all even trying several things to build from source, so I ended up giving up on it and will try again maybe in a few months with new releases)

Sorry, I closed it too early then.
So you're saying Gazebe still does not build? Also not after a brew upgrade?
For the jMAVSim problem I made a pull request that you could try out. The problem is that no one seems to know a lot about java and the java3d dependencies in order to fix jMAVSim.

@julianoes Awesome, thanks for reopening. That's correct - neither is building. I tried just now to reinstall Gazbo with brew, but I'm getting:
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/cmath:329:9: error: no member named 'isunordered' in the global namespace
using ::isunordered;

which doesn't seem like an issue with PX4 at all, but I don't have time to debug right this second. I'll look at it at the PR you so kindly put up within the next 36 hours and report back!

Thanks so much again for reopening. I couldn't build Gazebo, but finally did after following https://github.com/Homebrew/brew/issues/5068 which helped out the most. If you have both XCode and CommandLineTools it looks like there are conflicts between them. I ended up deleting CommandLineTools and could build Gazebo again. But I still can't build PX4. I've put the error I get below. I'm chalking this up to probably having a messed up system, so we can just close it unless you see something in here that you think I could be doing wrong.
Thanks!
-- The CXX compiler identification is AppleClang <IP_ADDRESS>30032
-- The C compiler identification is AppleClang <IP_ADDRESS>30032
-- The ASM compiler identification is Clang
-- Found assembler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc - works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Building for code coverage
-- Found PythonInterp: /usr/local/bin/python3 (found suitable version "3.7.7", minimum required is "3")
-- build type is RelWithDebInfo
-- PX4 ECL: Very lightweight Estimation & Control Library v1.9.0-rc1-286-g24f2e60
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default
[9/741] git submodule src/drivers/gps/devices
[12/741] git submodule src/lib/ecl
[13/741] git submodule mavlink/include/mavlink/v2.0
[15/741] git submodule Tools/sitl_gazebo
[20/741] Performing configure step for 'sitl_gazebo'
-- install-prefix: /usr/local
-- The C compiler identification is AppleClang <IP_ADDRESS>30032
-- The CXX compiler identification is AppleClang <IP_ADDRESS>30032
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc - works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test COMPILER_SUPPORTS_CXX17
-- Performing Test COMPILER_SUPPORTS_CXX17 - Success
-- Performing Test COMPILER_SUPPORTS_CXX14
-- Performing Test COMPILER_SUPPORTS_CXX14 - Success
-- Performing Test COMPILER_SUPPORTS_CXX11
-- Performing Test COMPILER_SUPPORTS_CXX11 - Success
-- Performing Test COMPILER_SUPPORTS_CXX0X
-- Performing Test COMPILER_SUPPORTS_CXX0X - Success
-- Using C++17 compiler
-- Found Boost: /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake (found suitable version "1.72.0", minimum required is "1.58") found components: system thread filesystem
CMake Warning (dev) at /usr/local/Cellar/cmake/3.17.2/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:272 (message):
  The package name passed to `find_package_handle_standard_args` (PkgConfig)
  does not match the name of the calling package (gazebo).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  /usr/local/Cellar/cmake/3.17.2/share/cmake/Modules/FindPkgConfig.cmake:45 (find_package_handle_standard_args)
  /usr/local/lib/cmake/gazebo/gazebo-config.cmake:23 (include)
  CMakeLists.txt:32 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.29.2")
-- Checking for module 'bullet>=2.82'
--   Found bullet, version 2.89
-- Found Boost: /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake (found suitable version "1.72.0", minimum required is "1.40.0") found components: thread system filesystem program_options regex iostreams date_time
-- Found Protobuf: /usr/local/lib/libprotobuf.dylib (found version "3.11.4")
-- Found Boost: /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake (found version "1.72.0")
-- Looking for OGRE...
-- OGRE_PREFIX_WATCH changed.
-- Checking for module 'OGRE'
--   Found OGRE, version 1.9.0
-- Found Ogre Ghadamon (1.9.0)
-- Found OGRE: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreMain.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreMain.dylib
-- Looking for OGRE_Paging...
-- Found OGRE_Paging: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgrePaging.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgrePaging.dylib
-- Looking for OGRE_Terrain...
-- Found OGRE_Terrain: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreTerrain.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreTerrain.dylib
-- Looking for OGRE_Property...
-- Found OGRE_Property: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreProperty.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreProperty.dylib
-- Looking for OGRE_RTShaderSystem...
-- Found OGRE_RTShaderSystem: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreRTShaderSystem.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreRTShaderSystem.dylib
-- Looking for OGRE_Volume...
-- Found OGRE_Volume: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreVolume.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreVolume.dylib
-- Looking for OGRE_Overlay...
-- Found OGRE_Overlay: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreOverlay.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreOverlay.dylib
CMake Warning (dev) at /usr/local/Cellar/cmake/3.17.2/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:272 (message):
  The package name passed to `find_package_handle_standard_args` (PkgConfig)
  does not match the name of the calling package (ignition-transport3).  This
  can lead to problems in calling code that expects `find_package` result
  variables (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  /usr/local/Cellar/cmake/3.17.2/share/cmake/Modules/FindPkgConfig.cmake:45 (find_package_handle_standard_args)
  /usr/local/lib/cmake/ignition-transport3/ignition-transport3-config.cmake:16 (include)
  /usr/local/lib/cmake/gazebo/gazebo-config.cmake:178 (find_package)
  CMakeLists.txt:32 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Checking for module 'libzmq>=3.2.0'
--   Found libzmq, version 4.3.2
-- Looking for zmq pkgconfig file - found
-- Checking for module 'uuid'
--   Found uuid, version 1.6.2
-- Looking for ignition-msgs - found
-- Found PythonInterp: /usr/local/bin/python3 (found suitable version "3.7.7", minimum required is "3")
-- Found OpenCV: /usr/local/Cellar/opencv/4.3.0_1 (found version "4.3.0")
-- Found TinyXML: /usr/local/lib/libtinyxml.dylib
-- Checking for module 'gstreamer-1.0 >= 1.0'
--   No package 'gstreamer-1.0' found
-- Checking for module 'gstreamer-base-1.0 >= 1.0'
--   No package 'gstreamer-base-1.0' found
-- Found GStreamer: GSTREAMER_INCLUDE_DIRS;GSTREAMER_LIBRARIES;GSTREAMER_VERSION;GSTREAMER_BASE_INCLUDE_DIRS;GSTREAMER_BASE_LIBRARIES (Required is at least version "1.0")
-- Checking for module 'OGRE'
--   Found OGRE, version 1.9.0
-- Building klt_feature_tracker without catkin
-- Building OpticalFlow with OpenCV
-- Found MAVLink: /Users/foyc/Workspace/px4/Firmware/mavlink/include (found version "2.0")
-- catkin DISABLED
-- Checking for module 'protobuf'
--   Found protobuf, version 3.11.4
-- Gazebo version: 8.6
-- Found GStreamer: adding gst_camera_plugin
-- Found GStreamer: adding gst_video_stream_widget
-- Configuring done
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
GSTREAMER_LIBRARIES (ADVANCED)
    linked by target "LiftDragPlugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_video_stream_widget" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_catapult_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_barometer_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_multirotor_base_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_motor_model" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_irlock_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_vision_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_mavlink_interface" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_usv_dynamics_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_lidar_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_gimbal_controller_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_uuv_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_imu_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_sonar_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "mav_msgs" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_geotagged_images_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_opticalflow_mockup_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_gps_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_parachute_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_controller_interface" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "sensor_msgs" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "std_msgs" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_opticalflow_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_gst_camera_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "nav_msgs" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_magnetometer_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "physics_msgs" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo
    linked by target "gazebo_wind_plugin" in directory /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo

-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.
[243/741] Building CXX object src/modules/sensors/sensor_corrections/CMakeFiles/sensor_corrections.dir/SensorCorrections.cpp.o
FAILED: external/Stamp/sitl_gazebo/sitl_gazebo-configure
cd /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default/build_gazebo && /usr/local/Cellar/cmake/3.17.2/bin/cmake -DCMAKE_INSTALL_PREFIX=/usr/local -DSEND_ODOMETRY_DATA=ON -GNinja /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo && /usr/local/Cellar/cmake/3.17.2/bin/cmake -E touch /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default/external/Stamp/sitl_gazebo/sitl_gazebo-configure
[249/741] Building CXX object src/modules/replay/CMakeFiles/modules__replay.dir/Replay.cpp.o
ninja: build stopped: subcommand failed.
make: *** [px4_sitl] Error 1

Ok, I think we're one step closer.

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
GSTREAMER_LIBRARIES (ADVANCED)

This would hint that some of the gstreamer dependencies are not available. They should have been installed via brew install px4-sim-gazebo:
https://github.com/PX4/homebrew-px4/blob/41f7ddd0af9b647470d4ff6f895392ba9e16b948/Formula/px4-sim-gazebo.rb#L12-L17

On a fresh MacOS 10.15.4 install there are still issues when gstreamer is installed. It will get past the above but fail at:
26/100] Generating /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf
FAILED: /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf
cd /Users/ryandev/src/Firmware/Tools/sitl_gazebo && rm -f /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf && /usr/local/bin/python3 /Users/ryandev/src/Firmware/Tools/sitl_gazebo/scripts/xacro.py -o /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.xacro enable_mavlink_interface:=true enable_ground_truth:=false enable_wind:=false enable_logging:=false rotors_description_dir:=/Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description send_vision_estimation:=false send_odometry:=true && gz sdf -p /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf >> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf && rm -f /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf
dyld: Library not loaded: /usr/local/opt/bullet/lib/libBulletSoftBody.2.88.dylib
Referenced from: /usr/local/bin/gz
Reason: image not found
/bin/sh: line 1: 37406 Abort trap: 6           gz sdf -p /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf >> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf
[43/100] Building CXX object CMakeFiles/gazebo_geotagged_images_plugin.dir/src/gazebo_geotagged_images_plugin.cpp.o
ninja: build stopped: subcommand failed.
[737/741] Linking CXX executable bin/px4
FAILED: external/Stamp/sitl_gazebo/sitl_gazebo-build
cd /Users/ryandev/src/Firmware/build/px4_sitl_default/build_gazebo && /usr/local/Cellar/cmake/3.17.2/bin/cmake --build .
ninja: build stopped: subcommand failed.
• The libBulletSoftBody.2.88.dylib error issue is referenced at https://github.com/osrf/homebrew-simulation/issues/1003 so @CoryFoy once you get streamer installed you'll hit a wall just after at the libBulletSoftBody.2.88.dylib problem.
PX4 builds fine, just not gazebo but I realize this is actually a bigger problem since any of the new Mac computers bought that come with 10.15.x (Catalina) can't be downgraded to 10.14 so no simulation work can be done on them unless dual booting into Linux or an equivalent setup.
Here's the full output if you're curious.
make px4_sitl gazebo_plane
-- PX4 version: v1.11.0-beta2-21-ga605444462
-- PX4 config file: /Users/ryandev/src/Firmware/boards/px4/sitl/default.cmake
-- PX4 config: px4_sitl_default
-- PX4 platform: posix
-- PX4 lockstep: enabled
-- cmake build type: RelWithDebInfo
-- The CXX compiler identification is AppleClang <IP_ADDRESS>30032
-- The C compiler identification is AppleClang <IP_ADDRESS>30032
-- The ASM compiler identification is Clang
-- Found assembler: /Library/Developer/CommandLineTools/usr/bin/cc
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Building for code coverage
-- Found PythonInterp: /usr/local/bin/python3 (found suitable version "3.7.7", minimum required is "3")
-- build type is RelWithDebInfo
-- PX4 ECL: Very lightweight Estimation & Control Library v1.9.0-rc1-286-g24f2e60
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/ryandev/src/Firmware/build/px4_sitl_default
[0/741] git submodule src/drivers/gps/devices
[6/741] git submodule src/lib/ecl
[9/741] git submodule mavlink/include/mavlink/v2.0
[13/741] git submodule Tools/sitl_gazebo
[21/741] Performing configure step for 'sitl_gazebo'
-- install-prefix: /usr/local
-- The C compiler identification is AppleClang <IP_ADDRESS>30032
-- The CXX compiler identification is AppleClang <IP_ADDRESS>30032
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test COMPILER_SUPPORTS_CXX17
-- Performing Test COMPILER_SUPPORTS_CXX17 - Success
-- Performing Test COMPILER_SUPPORTS_CXX14
-- Performing Test COMPILER_SUPPORTS_CXX14 - Success
-- Performing Test COMPILER_SUPPORTS_CXX11
-- Performing Test COMPILER_SUPPORTS_CXX11 - Success
-- Performing Test COMPILER_SUPPORTS_CXX0X
-- Performing Test COMPILER_SUPPORTS_CXX0X - Success
-- Using C++17 compiler
-- Found Boost: /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake (found suitable version "1.72.0", minimum required is "1.58") found components: system thread filesystem
CMake Warning (dev) at /usr/local/Cellar/cmake/3.17.2/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:272 (message):
The package name passed to find_package_handle_standard_args (PkgConfig)
does not match the name of the calling package (gazebo).  This can lead to
problems in calling code that expects find_package result variables
(e.g., _FOUND) to follow a certain pattern.
Call Stack (most recent call first):
/usr/local/Cellar/cmake/3.17.2/share/cmake/Modules/FindPkgConfig.cmake:45 (find_package_handle_standard_args)
/usr/local/lib/cmake/gazebo/gazebo-config.cmake:30 (include)
CMakeLists.txt:32 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.
-- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.29.2")
-- Checking for module 'bullet>=2.82'
--   Found bullet, version 2.89
-- Found fcl: /usr/local/Cellar/fcl/0.6.1/include (found suitable version "0.6.1", minimum required is "0.3.2")
-- Found assimp: /usr/local/include (found version "5.0.0")
-- Found DART: /usr/local/include (Required is at least version "6") found components: dart
-- Found Boost: /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake (found suitable version "1.72.0", minimum required is "1.40.0") found components: thread system filesystem program_options regex iostreams date_time
-- Found Protobuf: /usr/local/lib/libprotobuf.dylib (found version "3.11.4")
-- Found Boost: /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake (found version "1.72.0")
-- Looking for OGRE...
-- OGRE_PREFIX_WATCH changed.
-- Checking for module 'OGRE'
--   Found OGRE, version 1.9.0
-- Found Ogre Ghadamon (1.9.0)
-- Found OGRE: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreMain.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreMain.dylib
-- Looking for OGRE_Paging...
-- Found OGRE_Paging: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgrePaging.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgrePaging.dylib
-- Looking for OGRE_Terrain...
-- Found OGRE_Terrain: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreTerrain.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreTerrain.dylib
-- Looking for OGRE_Property...
-- Found OGRE_Property: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreProperty.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreProperty.dylib
-- Looking for OGRE_RTShaderSystem...
-- Found OGRE_RTShaderSystem: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreRTShaderSystem.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreRTShaderSystem.dylib
-- Looking for OGRE_Volume...
-- Found OGRE_Volume: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreVolume.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreVolume.dylib
-- Looking for OGRE_Overlay...
-- Found OGRE_Overlay: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreOverlay.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreOverlay.dylib
-- Found Protobuf: /usr/local/lib/libprotobuf.dylib (found suitable version "3.11.4", minimum required is "2.3.0")
-- Config-file not installed for ZeroMQ -- checking for pkg-config
-- Checking for module 'libzmq >= 4'
--   Found libzmq , version 4.3.2
-- Found ZeroMQ: TRUE (Required is at least version "4")
-- Checking for module 'uuid'
--   Found uuid, version 1.6.2
-- Found UUID: TRUE
-- Checking for module 'tinyxml2'
--   Found tinyxml2, version 8.0.0
-- Looking for dlfcn.h - found
-- Looking for libdl - found
-- Found DL: TRUE
-- FreeImage.pc not found, we will search for FreeImage_INCLUDE_DIRS and FreeImage_LIBRARIES
-- Found UUID: TRUE
-- Checking for module 'gts'
--   Found gts, version 0.7.6
-- Found GTS: TRUE
-- Checking for module 'libswscale'
--   Found libswscale, version 5.5.100
-- Found SWSCALE: TRUE
-- Checking for module 'libavdevice >= 56.4.100'
--   Found libavdevice , version 58.8.100
-- Found AVDEVICE: TRUE (Required is at least version "56.4.100")
-- Checking for module 'libavformat'
--   Found libavformat, version 58.29.100
-- Found AVFORMAT: TRUE
-- Checking for module 'libavcodec'
--   Found libavcodec, version 58.54.100
-- Found AVCODEC: TRUE
-- Checking for module 'libavutil'
--   Found libavutil, version 56.31.100
-- Found AVUTIL: TRUE
-- Found CURL: /usr/lib/libcurl.dylib (found version "7.64.1")
-- Checking for module 'jsoncpp'
--   Found jsoncpp, version 1.9.0
-- Found JSONCPP: TRUE
-- Checking for module 'yaml-0.1'
--   Found yaml-0.1, version 0.2.4
-- Found YAML: TRUE
-- Checking for module 'libzip'
--   Found libzip, version 1.6.1
-- Found ZIP: TRUE
-- Found PythonInterp: /usr/local/bin/python3 (found suitable version "3.7.7", minimum required is "3")
-- Found OpenCV: /usr/local/Cellar/opencv/4.3.0 (found version "4.3.0")
-- Found TinyXML: /usr/local/lib/libtinyxml.dylib
-- Checking for module 'gstreamer-1.0 >= 1.0'
--   Found gstreamer-1.0 , version 1.16.2
-- Checking for module 'gstreamer-base-1.0 >= 1.0'
--   Found gstreamer-base-1.0 , version 1.16.2
-- Found GStreamer: GSTREAMER_INCLUDE_DIRS;GSTREAMER_LIBRARIES;GSTREAMER_VERSION;GSTREAMER_BASE_INCLUDE_DIRS;GSTREAMER_BASE_LIBRARIES (Required is at least version "1.0")
-- Checking for module 'OGRE'
--   Found OGRE, version 1.9.0
-- Building klt_feature_tracker without catkin
-- Building OpticalFlow with OpenCV
-- Found MAVLink: /Users/ryandev/src/Firmware/mavlink/include (found version "2.0")
-- catkin DISABLED
-- Found Protobuf: /usr/local/lib/libprotobuf.dylib (found version "3.11.4")
-- Checking for module 'protobuf'
--   Found protobuf, version 3.11.4
-- Gazebo version: 9.13
-- Found GStreamer: adding gst_camera_plugin
-- Found GStreamer: adding gst_video_stream_widget
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/ryandev/src/Firmware/build/px4_sitl_default/build_gazebo
[600/741] Linking CXX static library src/lib/bezier/libbezier.a
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: src/lib/bezier/libbezier.a(BezierQuad.cpp.o) has no symbols
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: src/lib/bezier/libbezier.a(BezierQuad.cpp.o) has no symbols
[637/741] Linking CXX static library src/drivers/camera_trigger/libdrivers__camera_trigger.a
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(pwm.cpp.o) has no symbols
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(seagull_map2.cpp.o) has no symbols
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(gpio.cpp.o) has no symbols
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(pwm.cpp.o) has no symbols
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(seagull_map2.cpp.o) has no symbols
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(gpio.cpp.o) has no symbols
[736/741] Performing build step for 'sitl_gazebo'
[16/100] Generating /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/c920/c920-gen.sdf
/Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/c920/c920.sdf.jinja -> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/c920/c920-gen.sdf
[17/100] Generating /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/3DR_gps_mag/3DR_gps_mag-gen.sdf
/Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/3DR_gps_mag/3DR_gps_mag.sdf.jinja -> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/3DR_gps_mag/3DR_gps_mag-gen.sdf
[18/100] Generating /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/mb1240-xl-ez4/mb1240-xl-ez4-gen.sdf
/Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/mb1240-xl-ez4/mb1240-xl-ez4.sdf.jinja -> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/mb1240-xl-ez4/mb1240-xl-ez4-gen.sdf
[19/100] Generating /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/px4flow/px4flow-gen.sdf
/Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/px4flow/px4flow.sdf.jinja -> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/px4flow/px4flow-gen.sdf
[20/100] Generating /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/r200/r200-gen.sdf
/Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/r200/r200.sdf.jinja -> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/r200/r200-gen.sdf
[21/100] Generating /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/pixhawk/pixhawk-gen.sdf
/Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/pixhawk/pixhawk.sdf.jinja -> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/pixhawk/pixhawk-gen.sdf
[22/100] Generating /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/sf10a/sf10a-gen.sdf
/Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/sf10a/sf10a.sdf.jinja -> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/sf10a/sf10a-gen.sdf
[23/100] Generating /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/matrice_100/matrice_100-gen.sdf
/Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/matrice_100/matrice_100.sdf.jinja -> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/matrice_100/matrice_100-gen.sdf
[26/100] Generating /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf
FAILED: /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf
cd /Users/ryandev/src/Firmware/Tools/sitl_gazebo && rm -f /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf && /usr/local/bin/python3 /Users/ryandev/src/Firmware/Tools/sitl_gazebo/scripts/xacro.py -o /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.xacro enable_mavlink_interface:=true enable_ground_truth:=false enable_wind:=false enable_logging:=false rotors_description_dir:=/Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description send_vision_estimation:=false send_odometry:=true && gz sdf -p /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf >> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf && rm -f /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf
dyld: Library not loaded: /usr/local/opt/bullet/lib/libBulletSoftBody.2.88.dylib
Referenced from: /usr/local/bin/gz
Reason: image not found
/bin/sh: line 1: 37406 Abort trap: 6           gz sdf -p /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf >> /Users/ryandev/src/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf
[43/100] Building CXX object CMakeFiles/gazebo_geotagged_images_plugin.dir/src/gazebo_geotagged_images_plugin.cpp.o
ninja: build stopped: subcommand failed.
[737/741] Linking CXX executable bin/px4
FAILED: external/Stamp/sitl_gazebo/sitl_gazebo-build
cd /Users/ryandev/src/Firmware/build/px4_sitl_default/build_gazebo && /usr/local/Cellar/cmake/3.17.2/bin/cmake --build .
ninja: build stopped: subcommand failed.
make: *** [px4_sitl] Error 1

Yep, I'll confirm that after running the brew install and rerunning px4_sitl I see a similar error to above. May just need to try building all this from scratch.
➜  Firmware git:(master) make px4_sitl gazebo
[343/494] Performing configure step for 'sitl_gazebo'
-- install-prefix: /usr/local
-- Using C++17 compiler
-- Found Boost: /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake (found suitable version "1.72.0", minimum required is "1.58") found components: system thread filesystem
CMake Warning (dev) at /usr/local/Cellar/cmake/3.17.2/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:272 (message):
  The package name passed to `find_package_handle_standard_args` (PkgConfig)
  does not match the name of the calling package (gazebo).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  /usr/local/Cellar/cmake/3.17.2/share/cmake/Modules/FindPkgConfig.cmake:45 (find_package_handle_standard_args)
  /usr/local/lib/cmake/gazebo/gazebo-config.cmake:30 (include)
  CMakeLists.txt:32 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found fcl: /usr/local/Cellar/fcl/0.6.1/include (found suitable version "0.6.1", minimum required is "0.3.2")
-- Found assimp: /usr/local/include (found version "5.0.0")
-- Found DART: /usr/local/include (Required is at least version "6") found components: dart
-- Found Boost: /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake (found suitable version "1.72.0", minimum required is "1.40.0") found components: thread system filesystem program_options regex iostreams date_time
-- Found Boost: /usr/local/lib/cmake/Boost-1.72.0/BoostConfig.cmake (found version "1.72.0")
-- Looking for OGRE...
-- Found Ogre Ghadamon (1.9.0)
-- Looking for OGRE_Paging...
-- Found OGRE_Paging: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgrePaging.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgrePaging.dylib
-- Looking for OGRE_Terrain...
-- Found OGRE_Terrain: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreTerrain.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreTerrain.dylib
-- Looking for OGRE_Property...
-- Found OGRE_Property: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreProperty.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreProperty.dylib
-- Looking for OGRE_RTShaderSystem...
-- Found OGRE_RTShaderSystem: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreRTShaderSystem.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreRTShaderSystem.dylib
-- Looking for OGRE_Volume...
-- Found OGRE_Volume: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreVolume.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreVolume.dylib
-- Looking for OGRE_Overlay...
-- Found OGRE_Overlay: optimized;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreOverlay.dylib;debug;/usr/local/Cellar/ogre1.9/1.9-20160714-108ab0bcc69603dba32c0ffd4bbbc39051f421c9_8/lib/libOgreOverlay.dylib
-- Found Protobuf: /usr/local/lib/libprotobuf.dylib (found suitable version "3.11.4", minimum required is "2.3.0")
-- Config-file not installed for ZeroMQ -- checking for pkg-config
-- Checking for module 'libzmq >= 4'
--   Found libzmq , version 4.3.2
-- Found ZeroMQ: TRUE (Required is at least version "4")
-- Checking for module 'uuid'
--   Found uuid, version 1.6.2
-- Found UUID: TRUE
-- Checking for module 'tinyxml2'
--   Found tinyxml2, version 8.0.0
-- Looking for dlfcn.h - found
-- Looking for libdl - found
-- Found DL: TRUE
-- FreeImage.pc not found, we will search for FreeImage_INCLUDE_DIRS and FreeImage_LIBRARIES
-- Found UUID: TRUE
-- Checking for module 'gts'
--   Found gts, version 0.7.6
-- Found GTS: TRUE
-- Checking for module 'libswscale'
--   Found libswscale, version 5.5.100
-- Found SWSCALE: TRUE
-- Checking for module 'libavdevice >= 56.4.100'
--   Found libavdevice , version 58.8.100
-- Found AVDEVICE: TRUE (Required is at least version "56.4.100")
-- Checking for module 'libavformat'
--   Found libavformat, version 58.29.100
-- Found AVFORMAT: TRUE
-- Checking for module 'libavcodec'
--   Found libavcodec, version 58.54.100
-- Found AVCODEC: TRUE
-- Checking for module 'libavutil'
--   Found libavutil, version 56.31.100
-- Found AVUTIL: TRUE
-- Found CURL: /usr/lib/libcurl.dylib (found version "7.64.1")
-- Checking for module 'jsoncpp'
--   Found jsoncpp, version 1.9.0
-- Found JSONCPP: TRUE
-- Checking for module 'yaml-0.1'
--   Found yaml-0.1, version 0.2.4
-- Found YAML: TRUE
-- Checking for module 'libzip'
--   Found libzip, version 1.6.1
-- Found ZIP: TRUE
-- Found OpenCV: /usr/local/Cellar/opencv/4.3.0_2 (found version "4.3.0")
-- Checking for module 'gstreamer-1.0 >= 1.0'
--   Found gstreamer-1.0 , version 1.16.2
-- Checking for module 'gstreamer-base-1.0 >= 1.0'
--   Found gstreamer-base-1.0 , version 1.16.2
-- Building klt_feature_tracker without catkin
-- Building OpticalFlow with OpenCV
-- catkin DISABLED
-- Found Protobuf: /usr/local/lib/libprotobuf.dylib (found version "3.11.4")
-- Gazebo version: 9.13
-- Found GStreamer: adding gst_camera_plugin
-- Found GStreamer: adding gst_video_stream_widget
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default/build_gazebo
[364/494] Linking CXX static library src/drivers/camera_trigger/libdrivers__camera_trigger.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(pwm.cpp.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(seagull_map2.cpp.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(gpio.cpp.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(pwm.cpp.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(seagull_map2.cpp.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: src/drivers/camera_trigger/libdrivers__camera_trigger.a(gpio.cpp.o) has no symbols
[372/494] Linking CXX static library src/lib/bezier/libbezier.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: src/lib/bezier/libbezier.a(BezierQuad.cpp.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: src/lib/bezier/libbezier.a(BezierQuad.cpp.o) has no symbols
[490/494] Performing build step for 'sitl_gazebo'
[14/100] Generating /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf
FAILED: /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf
cd /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo && rm -f /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf && /usr/local/bin/python3 /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/scripts/xacro.py -o /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.xacro enable_mavlink_interface:=true enable_ground_truth:=false enable_wind:=false enable_logging:=false rotors_description_dir:=/Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/rotors_description send_vision_estimation:=false send_odometry:=true && gz sdf -p /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf >> /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf && rm -f /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf

dyld: Library not loaded: /usr/local/opt/bullet/lib/libBulletSoftBody.2.88.dylib
  Referenced from: /usr/local/bin/gz
  Reason: image not found
/bin/sh: line 1: 87093 Abort trap: 6           gz sdf -p /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.urdf >> /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/iris/iris.sdf
[15/100] Generating /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/3DR_gps_mag/3DR_gps_mag-gen.sdf
/Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/3DR_gps_mag/3DR_gps_mag.sdf.jinja -> /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/3DR_gps_mag/3DR_gps_mag-gen.sdf
[16/100] Generating /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/c920/c920-gen.sdf
/Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/c920/c920.sdf.jinja -> /Users/foyc/Workspace/px4/Firmware/Tools/sitl_gazebo/models/c920/c920-gen.sdf
[19/100] Building CXX object CMakeFiles/nav_msgs.dir/Odometry.pb.cc.o
ninja: build stopped: subcommand failed.
FAILED: external/Stamp/sitl_gazebo/sitl_gazebo-build
cd /Users/foyc/Workspace/px4/Firmware/build/px4_sitl_default/build_gazebo && /usr/local/Cellar/cmake/3.17.2/bin/cmake --build .
ninja: build stopped: subcommand failed.
make: *** [px4_sitl] Error 1

Looks like the gazebo dependencies are not linking properly:
dyld: Library not loaded: /usr/local/opt/bullet/lib/libBulletSoftBody.2.88.dylib

It looks like the fix/update is coming here: https://github.com/osrf/homebrew-simulation/issues/1003

The Gazebo issue looks a lot like something I get every time after I run brew upgrade. A reliable workaround for me has been to run brew reinstall --build-from-source gazebo9 after upgrading Homebrew. This is with Gazebo 9 on macOS 10.15.5.

Usually you should not have to rebuild unless the bottles provided by OSRF are outdated.
However, you do have to do a make clean of PX4 and the Gazebo plugins.

I can confirm this works.
Did the following:
brew upgrade
brew reinstall --build-from-source gazebo9
make clean on PX4 firmware
Gazebo 9 working under macOS 10.15.4 with PX4 Master

Confirm above as well.  macOS 10.5.5
I only have Command Line Tools - no Xcode installed.
Tried jMAVSim but ended up with too new a jdk I think.
FYI, there does seem to be differences between master and stable in macOS toolchain wiki instructions regarding brew packages .
Master brew cask install xquartz brew install px4-sim-gazebo
1.10
brew install px4-sim```

Closing because I won't have the time to loop back on this and no reason for it to sit in the queue if I can't do that!

FYI with current PX4 (master or stable v1.11) both gazebo and jmavsim are working for me with MacOS Catalina.


Added argument not visible by action function.

Here is my code :
        parser.addCommand(Command.create("Start Game").addAlias("start")
                        .setDescription("Start the game with specified options")
                        .setAction(args -> askStartGame(args))
                        .addArgument(Argument.create("game_title"))
                        .addArgument(Argument.create("max_players"))
                        .addArgument(Argument.create("max_ping"))
                        .addArgument(Argument.create("tcp_port"))
                        .addArgument(Argument.create("udp_port"))
                        .addArgument(Argument.create("allynoblock")
                                .addOption(Argument.create("noblock"))
                                .addOption(Argument.create("block")))
                        .addArgument(Argument.create("friendlyfire")
                                .addOption(Argument.create("ff"))
                                .addOption(Argument.create("no_ff")))

    private void askStartGame(ArrayList<Argument> args) {
        for (int i = 0; i < args.size(); ++i) {
            System.out.println("- " + args.get(i).getName());
        }
    }

and here is the output :
$ start "game" 8 100 13333 13444 block ff
- game_title
- max_players
- max_ping
- tcp_port
- udp_port
- allynoblock

my last parameter is not taken in account. I have added several more arguments and they are not displayed.
Can you confirm this ?

I deduced that you cannot add more than 1 argument with options. Is it done by purpose ?

This should not be done on purpose, I will look into these issues later today and get back to you.

This has been fixed in the latest version for both C# and Java, which is now released. Thanks for posting this issue!


Update file-filters.md

clarification that the sensitivity label filter will cause File Policy to skip (no handle) non-Office files

#sign-off

@batamig
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

closing to handline in private repo


As a Knative administrator, I want to enable registries list command

Moved from https://github.com/knative/client-contrib/issues/76#issue-695946267

/assign @12345lcr


Incognito Mode

Would it be possible to have an Incognito mode that would allow for some privacy protection ?
Thanks

For sure. On the todo list.

how about incognito mode with tor, just like how brave browser has done

Related discussion: https://github.com/Chocobozzz/PeerTube/issues/685