Source commands do not display error information

Summary
In version 7.12.3 of the cli, when running sfdx force:source:deploy or sfdx force:source:push command and the execution fails, no error messages are shown.
Initially reported in VSCode extensions repo https://github.com/forcedotcom/salesforcedx-vscode/issues/1411#issuecomment-505218236
Steps To Reproduce:

Run push or deploy on a project that has deploy errors e.g. Apex class with a reference to a method that does not exist.
Deploy/push fails but no error messages are shown.

Expected result
When the command execution fails, I expect a table with the error details on it.
Actual result
Currently just getting Push failed. message.
Additional information
As a work around, running the commands with --json attribute on it does return the error information.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version): 7.12.3
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
OS and version: Mac OS 10.13.6

Confirming that this issue also occurs on linux version sfdx-cli/7.12.3-bfc421fa08 linux-x64 node-v10.15.3
As a workaround I'm currently using
alias sfpush="sfdx force:source:push --json 2>&1 | jq -r 'if (.status == 0) then .result.pushedSource[].fullName + "\t\t" + .result.pushedSource[].state else .result[].fullName + "\t\t" + .result[].error end'"

FYI @hansalves If you want the error json to go to stdout you can set this:
export SFDX_JSON_TO_STDOUT=true
It will be the default in couple major releases.

Still facing this issue in last version 7.13.0-27dbcb37d3, also, when the error is due to conflicts the reason appears

And vscode shows the error :\

This issue has been fixed and will go out in next week's release (July 3).

@clairebianchi Has the release been pushed out?
I am on latest version "Updating CLI... already on latest version: 7.13.0-27dbcb37d3"
But I am still facing this issue....

Same here (also with updated VSCode plugins)

Me too. Yesterday.

Same here: the issue still exists in 7.13.0-27dbcb37d3

I launched
sfdx plugins:install salesforcedx@latest

After installing I have this version: salesforcedx 46.4.0
Seems to fix the issue, maybe this works to:
sfdx plugins:update

Having the salesforcedx plugin installed overrides the code shipped by the normal Salesforce CLI. If you still have the issue in version 7.13 and have the salesforcedx plugin installed you should either uninstall that plugin or update to its latest version.

Our release was delayed last week due to an issue with the installer and then the holiday in the USA. The release went out this morning that should fix this issue the current version is 7.14.0

I'm facing the issue in SFDX version - sfdx-cli/7.20.1-d88ae4707c win32-x64 node-v10.15.3
See the below error following the command - sfdx force:source:push -f --json --loglevel INFO
{
"status": 1,
"result": [
{
"error": "Unknown"
}
],
"name": "DeployFailed",
"message": "Push failed.",
"exitCode": 1,
"commandName": "SourcePushCommand",
"data": [
{
"error": "Unknown"
}
],
"stack": "DeployFailed: Push failed.\n    at MetadataRegistry.initializeMetadataTypeInfos.then.then.catch.e (C:\Users\ramadop\AppData\Local\sfdx\client\7.20.1-d88ae4707c\node_modules\sa
lesforce-alm\dist\lib\source\sourceApiCommand.js:64:31)\n    at tryCatcher (C:\Users\ramadop\AppData\Local\sfdx\client\7.20.1-d88ae4707c\node_modules\bluebird\js\release\util.js:16:2
3)\n    at Promise._settlePromiseFromHandler (C:\Users\ramadop\AppData\Local\sfdx\client\7.20.1-d88ae4707c\node_modules\bluebird\js\release\promise.js:517:31)\n    at Promise._settleProm
ise (C:\Users\ramadop\AppData\Local\sfdx\client\7.20.1-d88ae4707c\node_modules\bluebird\js\release\promise.js:574:18)\n    at Promise._settlePromise0 (C:\Users\ramadop\AppData\Local
\sfdx\client\7.20.1-d88ae4707c\node_modules\bluebird\js\release\promise.js:619:10)\n    at Promise._settlePromises (C:\Users\ramadop\AppData\Local\sfdx\client\7.20.1-d88ae4707c\node_m
odules\bluebird\js\release\promise.js:695:18)\n    at _drainQueueStep (C:\Users\ramadop\AppData\Local\sfdx\client\7.20.1-d88ae4707c\node_modules\bluebird\js\release\async.js:138:12)
n    at _drainQueue (C:\Users\ramadop\AppData\Local\sfdx\client\7.20.1-d88ae4707c\node_modules\bluebird\js\release\async.js:131:9)\n    at Async._drainQueues (C:\Users\ramadop\AppData
\Local\sfdx\client\7.20.1-d88ae4707c\node_modules\bluebird\js\release\async.js:147:5)\n    at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\ramadop\AppData\Local\sfdx\client
\7.20.1-d88ae4707c\node_modules\bluebird\js\release\async.js:17:14)\n    at runCallback (timers.js:705:18)\n    at tryOnImmediate (timers.js:676:5)\n    at processImmediate (timers.js:658:5)",
"warnings": []
}
Could someone please provide a solution for this? Thanks in advance!

This is still happening. I have the latest version.

I am having the same issue. Did anyone find the solution.
sfdx force:source:push -f --json
{
"status": 1,
"result": [
{
"error": "Unknown"
}
],
"name": "DeployFailed",
"message": "Push failed.",
"exitCode": 1,
"commandName": "SourcePushCommand",
"data": [
{
"error": "Unknown"
}
],
"stack": "DeployFailed: Push failed.\n    at MetadataRegistry.initializeMetadataTypeInfos.then.then.catch.e (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/dist/lib/source/sourceApiCommand.js:64:31)\n    at tryCatcher (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/util.js:16:23)\n    at Promise._settlePromiseFromHandler (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:517:31)\n    at Promise._settlePromise (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:574:18)\n    at Promise._settlePromise0 (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:619:10)\n    at Promise._settlePromises (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:695:18)\n    at _drainQueueStep (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:138:12)\n    at _drainQueue (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:131:9)\n    at Async._drainQueues (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:147:5)\n    at Immediate.Async.drainQueues [as _onImmediate] (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:17:14)\n    at runCallback (timers.js:705:18)\n    at tryOnImmediate (timers.js:676:5)\n    at processImmediate (timers.js:658:5)",
"warnings": []
}

I am facing the same issue after update of new CLI. No Error displayed on the push.
When put --json flag, it is coming with below error.
sfdx force:source:push -f --json
{
"status": 1,
"result": [
{
"error": "Unknown"
}
],
"name": "DeployFailed",
"message": "Push failed.",
"exitCode": 1,
"commandName": "SourcePushCommand",
"data": [
{
"error": "Unknown"
}
],
"stack": "DeployFailed: Push failed.\n    at MetadataRegistry.initializeMetadataTypeInfos.then.then.catch.e (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/dist/lib/source/sourceApiCommand.js:64:31)\n    at tryCatcher (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/util.js:16:23)\n    at Promise._settlePromiseFromHandler (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:517:31)\n    at Promise._settlePromise (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:574:18)\n    at Promise._settlePromise0 (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:619:10)\n    at Promise._settlePromises (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:695:18)\n    at _drainQueueStep (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:138:12)\n    at _drainQueue (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:131:9)\n    at Async._drainQueues (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:147:5)\n    at Immediate.Async.drainQueues [as _onImmediate] (/Users/ankurg/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:17:14)\n    at runCallback (timers.js:705:18)\n    at tryOnImmediate (timers.js:676:5)\n    at processImmediate (timers.js:658:5)",
"warnings": []
}

Hi team! i'm with the same issue

{
    "status": 1,
    "result": [
        {
            "error": "Unknown"
        }
    ],
    "name": "DeployFailed",
    "message": "Push failed.",
    "exitCode": 1,
    "commandName": "SourcePushCommand",
    "data": [
        {
            "error": "Unknown"
        }
    ],
    "stack": "DeployFailed: Push failed.\n    at MetadataRegistry.initializeMetadataTypeInfos.then.then.catch.e (/home/martinlarizzate/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/dist/lib/source/sourceApiCommand.js:64:31)\n    at tryCatcher (/home/martinlarizzate/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/util.js:16:23)\n    at Promise._settlePromiseFromHandler (/home/martinlarizzate/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:517:31)\n    at Promise._settlePromise (/home/martinlarizzate/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:574:18)\n    at Promise._settlePromise0 (/home/martinlarizzate/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:619:10)\n    at Promise._settlePromises (/home/martinlarizzate/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/promise.js:695:18)\n    at _drainQueueStep (/home/martinlarizzate/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:138:12)\n    at _drainQueue (/home/martinlarizzate/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:131:9)\n    at Async._drainQueues (/home/martinlarizzate/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:147:5)\n    at Immediate.Async.drainQueues [as _onImmediate] (/home/martinlarizzate/.local/share/sfdx/client/7.28.7-7bceba6f24/node_modules/salesforce-alm/node_modules/bluebird/js/release/async.js:17:14)\n    at runCallback (timers.js:705:18)\n    at tryOnImmediate (timers.js:676:5)\n    at processImmediate (timers.js:658:5)",
    "warnings": []
}

I am facing the same problem when I execute the command
sfdx force:source:deploy -m ApexClass:ClassNameRepository -l RunLocalTests -u myOrgProd --json --loglevel error
I upgrade to the following versions sfdx-cli / 7.30.13-9e204762d5 win32-x64 node-v10.15.3
and salesforcedx installed v47.3.7
Error:
{     "status": 1,     "result": [         {             "error": "Unknown"         }     ],     "name": "DeployFailed",     "message": "Deploy failed.",     "exitCode": 1,     "commandName": "SourceDeployCommand",     "data": [         {             "error": "Unknown"         }     ],     "stack": "DeployFailed: Deploy failed.\n    at MetadataRegistry.initializeMetadataTypeInfos.then.then.catch.e ",     "warnings": [] }

I am also facing the same issue. I have the latest version of the sfdx.
G:\salesForce\FernApp>sfdx force:source:push --json -f -u<EMAIL_ADDRESS>{
"status": 1,
"result": [
{
"error": "Unknown"
}
],
"name": "DeployFailed",
"message": "Push failed.",
"exitCode": 1,
"commandName": "SourcePushCommand",
"data": [
{
"error": "Unknown"
}
],
"stack": "DeployFailed: Push failed.\n    at MetadataRegistry.initializeMetadataTypeInfos.then.then.catch.e (C:\Users\bca\AppData\Local\sfdx\client\7.31.0-6a986f8be5\node_modules\salesforce-alm\dist\lib\source\sourceApiCommand.js:64:31)\n    at tryCatcher (C:\Users\bca\AppData\Local\sfdx\client\7.31.0-6a986f8be5\node_modules\salesforce-alm\node_modules\bluebird\js\release\util.js:16:23)\n    at Promise._settlePromiseFromHandler (C:\Users\bca\AppData\Local\sfdx\client\7.31.0-6a986f8be5\node_modules\salesforce-alm\node_modules\bluebird\js\release\promise.js:517:31)\n    at Promise._settlePromise (C:\Users\bca\AppData\Local\sfdx\client\7.31.0-6a986f8be5\node_modules\salesforce-alm\node_modules\bluebird\js\release\promise.js:574:18)\n    at Promise._settlePromise0 (C:\Users\bca\AppData\Local\sfdx\client\7.31.0-6a986f8be5\node_modules\salesforce-alm\node_modules\bluebird\js\release\promise.js:619:10)\n    at Promise._settlePromises (C:\Users\bca\AppData\Local\sfdx\client\7.31.0-6a986f8be5\node_modules\salesforce-alm\node_modules\bluebird\js\release\promise.js:695:18)\n    at _drainQueueStep (C:\Users\bca\AppData\Local\sfdx\client\7.31.0-6a986f8be5\node_modules\salesforce-alm\node_modules\bluebird\js\release\async.js:138:12)\n    at _drainQueue (C:\Users\bca\AppData\Local\sfdx\client\7.31.0-6a986f8be5\node_modules\salesforce-alm\node_modules\bluebird\js\release\async.js:131:9)\n    at Async._drainQueues (C:\Users\bca\AppData\Local\sfdx\client\7.31.0-6a986f8be5\node_modules\salesforce-alm\node_modules\bluebird\js\release\async.js:147:5)\n    at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\bca\AppData\Local\sfdx\client\7.31.0-6a986f8be5\node_modules\salesforce-alm\node_modules\bluebird\js\release\async.js:17:14)\n    at runCallback (timers.js:705:18)\n    at tryOnImmediate (timers.js:676:5)\n    at processImmediate (timers.js:658:5)",
"warnings": []
}

Can someone please help me to resolve this

Regards,
In my case I solved the problem using the Ant Migration Tool https://developer.salesforce.com/docs/atlas.en-us.daas.meta/daas/meta_development.htm
With this tooling I was able to obtain more details of my problem, finally my problem is that it was not covering 75% of the code in the Test.
I hope this can help you too.

Can someone confirm that this issue is happening on version 7.31.0?
I am able to see error messages as expected:
sfdx force:source:deploy -u<EMAIL_ADDRESS>-p force-app/main/default/
PROJECT PATH  ERROR
────────────  ────────────────────────────
N/A           Invalid language en_S (3:13)
ERROR running force:source:deploy:  Deploy failed.

Regards,
In my case I solved the problem using the Ant Migration Tool https://developer.salesforce.com/docs/atlas.en-us.daas.meta/daas/meta_development.htm
With this tooling I was able to obtain more details of my problem, finally my problem is that it was not covering 75% of the code in the Test.
I hope this can help you too.

Thank you for this solution. I will let you after working with this. I hope it works to.

Team I solved the issue with a version downgrade.
Please check at this stackexchange question

@mlarizzate @Pargavifern
Can either of you confirm that the issue is occurring in version 7.31.0?

Yes its occurring in the version of sfdx-cli/7.31.0 win32-x64 node-v12.13.0

@Pargavifern Thank you. Can you show me the output of sfdx plugins --core?

@mdonnalley  Yeah definitely but can I send you the output on this Monday. If you don't mind.

Hi @mdonnalley
Sorry for the late reply
C:\Users\admin>sfdx plugins --core
@oclif/plugin-commands 1.2.3 (core)
@oclif/plugin-help 2.2.1 (core)
@oclif/plugin-not-found 1.2.3 (core)
@oclif/plugin-plugins 1.7.8 (core)
@oclif/plugin-update 1.3.9 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.0.7 (core)
analytics 1.2.2 (core)
generator 1.1.2 (core)
salesforcedx 47.4.0 (core)
├─ salesforcedx-templates 47.3.2 (core)
└─ salesforce-alm 47.7.0 (core)
sfdx-cli 7.31.0 (core)

Hi @Pargavifern, I'll be taking over this task for the week... I tried pushing an apex class with a lot of errors, and they all appeared for me.
   foo(){
        let x = "abc";
        x=23
    }
    x => axb();
}```

```PROJECT PATH                            ERROR
──────────────────────────────────────  ─────────────────────────────────────────────────────────────────────────
force-app/main/default/classes/foo.cls  Unrecognized symbol '"', which is not a valid Apex identifier. (5:17)
force-app/main/default/classes/foo.cls  Unrecognized symbol '"', which is not a valid Apex identifier. (5:21)
force-app/main/default/classes/foo.cls  Missing ';' at '}' (7:5)
force-app/main/default/classes/foo.cls  Unexpected token '=>'. (9:7)
force-app/main/default/classes/foo.cls  Method already defined: <init> void foo.<init>() from the type foo (9:10)
force-app/main/default/classes/foo.cls  Invalid type: let (5:9)
force-app/main/default/classes/foo.cls  Illegal assignment from Integer to let (6:9)
force-app/main/default/classes/foo.cls  Invalid constructor name: axb (9:10)
force-app/main/default/classes/foo.cls  Unexpected token '=>'. (9:7)
ERROR running force:source:push:  Push failed.```

looking in the code it has error catches for Failed Deploys, Timeouts, and Source Conflicts, so the error you're facing isn't one of those. Have you tried pushing only parts of your code in order to narrow down what specific parts of the file the error might be in. Or is it that you're not meeting the 75% code coverage issue like mentioned above? Is the ANT tool able to provide any more information?

Hi @williamruemmele-sf
I created only a custom object and linked to standard object. Like this I created 2 project and merged into to one to push it into the scratch. That time it throws error like this. I didn't add anything.

so it failed correctly, with errors?

Yes. But it doesn't show error

Would you be available to set up a quick meeting to walk me through your reproduction steps?

Sorry I don't understand @williamruemmele-sf

Can we video call to go over the problem?

Really sorry to say this. But currently I can't able to do it. But I can share my project


Let Proto3 decide defaults

Let's not encode the proto3 defaults in the GAPIC generator -- we can just rely on proto to do this for us. This change has already been made to NodeJS/Ruby here: https://github.com/googleapis/toolkit/pull/306

@geigerj Does this affect the other four languages?

@bjwatson I don't know; when I created the issue, it was specifically in reference to the fact that in the Python libraries, we do things like setting integer fields to 0, which isn't really necessary, and it might slightly simplify the generator logic not to do this.

I think it probably makes sense to keep the scope of this issue as Python-specific clean-up.

This is actually blocking Pub/Sub snap-seek implementation, as setting the default for non-primitive types is not the same as leaving it unset. Bumping to P1.
cc: @lukesneeringer


Add option to show event location in agenda

Based on this comment:
https://github.com/sfsam/Itsycal/issues/36#issuecomment-315406701

Location can be toggled in 0.11.6.


onActivityJoin isn't fired

as title, it seem that the event onActivityJoin was never fired?
I have tested it on ae841453bd (master latest) and 70b1e9dda6189cd9fbdce113527a915f892bc154 (java-impl latest) and both seems never fire the event?

Have you also tried the latest released version (which still uses the native library)?

if you meant tag v0.5.5, yes, it seems it didn't fire the event
However i have tested adding the event listener seems to work just fine (see: https://github.com/RedCokeDevelopment/discord-game-sdk4j/commit/52f54e480caee799a0885abdba916cba1fbee207)

Oh, do you want to make a Pull Request for that then?

Sure, #90

Thank you!


Fix handling of invalid base64 values

This change will gracefully handle invalid base64 basic authorization values.

fixes #2717

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[ ] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

Almost perfect PR, just one nitpick :+1:


python310Packages.gdown: 4.5.1 -> 4.5.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.gdown is: "A CLI tool for downloading large files from Google Drive"
meta.homepage for python310Packages.gdown is: "https://github.com/wkentaro/gdown"
meta.changelog for python310Packages.gdown is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.5.2 with grep in /nix/store/miq2pl0hzkvpvzzxss2kjbjwmh49znh3-gdown-4.5.2
found 4.5.2 in filename of file in /nix/store/miq2pl0hzkvpvzzxss2kjbjwmh49znh3-gdown-4.5.2

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
gdown
python310Packages.gdown
python39Packages.gdown
tts

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/miq2pl0hzkvpvzzxss2kjbjwmh49znh3-gdown-4.5.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.gdown https://github.com/r-ryantm/nixpkgs/archive/321b031b1499ae311a72904d0d809625284dd401.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/miq2pl0hzkvpvzzxss2kjbjwmh49znh3-gdown-4.5.2
ls -la /nix/store/miq2pl0hzkvpvzzxss2kjbjwmh49znh3-gdown-4.5.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

gdown (python310Packages.gdown)
python39Packages.gdown
tts

Maintainer pings
cc @breakds for testing.

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

3 packages built:

gdown (python310Packages.gdown)
python39Packages.gdown
tts


fix: containerd version in azlinux/mariner release notes

What type of PR is this?

What this PR does / why we need it:
fixes a bug we've had for a while where the reported containerd/runc versions weren't correct within azurelinux/mariner release notes
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 75.969%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2627

Relevant Lines:
3458

💛  - 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

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 75.969%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2627

Relevant Lines:
3458

💛  - Coveralls


Emoji "eye in speech bubble" is not interpreted correctly

There is an emoji named "eye in speech bubble" in the Unicode Emoji List.
eye in speech bubble - Emoji List, v5.0
According to this list, the emoji consists of codepoint U+1F441 U+FE0F U+200D U+1F5E8 U+FE0F,
but the following code returns nil.
Twemoji.find_by(unicode: "\u{1f441}\u{fe0f}\u{200d}\u{1f5e8}\u{fe0f}")

This is because the emoji has a codepoint U+1F441 U+200D U+1F5E8 in this gem.
Codepoint U+FE0F is "emoji presentation selector", a variation selector for emojis.
Similar issues are also found in keycap emojis. (:hash:, :asterisk:, etc.)
On the other hand, :{man,woman}-{kiss,heart}-{man,woman}: emojis contains U+FE0F in this gem.
I think this is a problem.
I think this issue should be fixed, but I have no idea.
What do you think?

Having a related issue, I think:
Twemoji.find_by(unicode: "☝") # => nil
Twemoji.find_by(unicode: "✌") # => nil

This seems to consistently happen with emojis that include the U+FE0F as a trailing presentation codepoint. e.g. the :point_up: has a codepoint U+261D in this gem, but is parsed as "261d-fe0f".
Twemoji.unicode_to_str("☝") # => "261d-fe0f"

As far as I can tell from emoji variation sequences, the presentation codepoint is to say "this is a graphic (e.g. non-text) emoji". Wouldn't it be safe to add the U+FE0F suffix and assume all emojis are "non-text"?
This gem is using emoji-unicode.yml to build Regexp to match the emojis unicode and text. Maybe the fe0f codepoint can be added as an optional group? e.g ":point-up:": 261d(-fe0f)?. (Not good with regex, so I don't really have an idea).
That would likely bring some other issues in itself as I'm not completely familiar with the gem, but it could be a starting point.

@renechz Sorry for the delay in reaction.
Thank you for your mention.
I think that your proposal is not bad and should be implemented.
@JunaitoFatas What do you think?


⚠ Bofrost.fr has degraded performance

In 33786a4, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1160 ms

Resolved: Bofrost.fr performance has improved in ece9e17 after 6 minutes.


Can we add yaml file example instead of only .properties file to the docs

I have noticed that yaml files are gaining popularity. I have seen that in the docs only .properties file example is being used.
Is it possible to add, the code below in the docs for yaml file:
spring:
  cloud:
    azure:
      keyvault:
        secret:
          property-source-enabled: true
          property-sources[0]:
            credential:
              client-secret: "(password returned from the creation of the service account)"
              client-id: "(appId returned from the creation of the service account)"
            profile:
              tenant-id: "(tenant returned from the creation of the service account)"
            endpoint: "(your key vault URI)"

You can find my implementation of Azure Key vault with yaml file here: https://github.com/mervynmanilall/azure-keyvault-with-springboot

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

ID: afc14028-8f4c-05bf-8a01-3ce82041b0b2
Version Independent ID: 05e48444-1d81-07de-5ca5-1efcc9241d00
Content: Tutorial for using Azure App Configuration Key Vault references in a Java Spring Boot app
Content Source: articles/azure-app-configuration/use-key-vault-references-spring-boot.md
Service: azure-app-configuration
GitHub Login: @mrm9084
Microsoft Alias: mametcal

@mervynmanilall
Thanks for your feedback! We will investigate and update as appropriate.

@maud-lv, we can and probably should add tabs for both. We just show properties as it is understand what is happening. There is only once instance that of properties and yaml being different besides the expansion, the label filter when you want to use the (No Label). That is documented here https://microsoft.github.io/spring-cloud-azure/docs/azure-app-configuration/.

Hello @mrm9084, I have created a PR (https://github.com/MicrosoftDocs/azure-docs/pull/109324).
Thanks for your help

Hi @mervynmanilall, I see that your PR has been merged. Thank you for helping update the docs! I am now closing this issue. #please-close.


[Feature Request] Documentation for Workforce

Required prerequisites

[X] I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
[ ] Consider asking first in a Discussion.

Motivation
Documentation for Workforce
Solution
No response
Alternatives
No response
Additional context
No response

https://www.notion.so/eigent-ai/Workforce-6997733c86a24ad8b4160fd9723289db


dotnet.sdk: 2.2.203/2.2.4 -> 2.2.401/2.2.6

Motivation for this change
Fixes https://github.com/NuGet/Home/issues/7802 (dotnet list package bug in some projects)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] 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)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @kuznero

I have tested and merged https://github.com/NixOS/nixpkgs/pull/63654, would you like to rebase your update?

all right, let me get to it

@GrahamcOfBorg build dotnet-sdk


64bit libc table generator had $r10 as 4th argument

Description/Motivation/Screenshots

How Has This Been Tested ?
"Tested" indicates that the PR works and the unit test (i.e. make test) run passes without issue.

[ ] x86-32
[ ] x86-64
[ ] ARM
[ ] AARCH64
[ ] MIPS
[ ] POWERPC
[ ] SPARC
[ ] RISC-V

Checklist

[ ] My code follows the code style of this project.
[ ] My change includes a change to the documentation, if required.
[ ] If my change adds new code,
adequate tests have been added.
[ ] I have read and agree to the
CONTRIBUTING document.

wow!


python311Packages.onnx: 1.15.0 -> 1.16.0

Description of changes
Bump enabling us to get rid of patches.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Partially done in https://github.com/NixOS/nixpkgs/commit/bb19daa10dd62feb399830d0ac8c4517b7f64e2c.

Superseded by #348985.


Make tags selection linkable

Right now, when you select tags in the components list, those are not reflected in the URL. It would be great if they were, to be able to deep-link. Official docs could then link to specific searches, for example "here you can find a list of community adapters for SvelteKit".

This is fixed in https://github.com/svelte-society/sveltesociety-2021


New command: planner bucket tasks list

Usage
planner bucket tasks list
Description
Lists the planner tasks in a Microsoft Planner bucket
Options

Option
Description

--bucketId [bucketId]
ID of the bucket to list the tasks of. Specify bucketId or bucketName, but not both

--bucketName [bucketName]
Name of the bucket to list the tasks of. Specify bucketId or bucketName, but not both

--planId [planId]
ID of the plan to which the bucket belongs. Specify planId or planName when using bucketName

--planName [planName]
Name of the plan to which the bucket belongs. Specify planId or planName when using bucketName

--ownerGroupId [ownerGroupId]
ID of the group to which the plan belongs. Specify ownerGroupId or ownerGroupName when using planName

--ownerGroupName [ownerGroupName]
Name of the group to which the plan belongs. Specify ownerGroupId or ownerGroupName when using planName

Additional Information
List Tasks
Examples
Lists the Microsoft Planner tasks in the Bucket FtzysDykv0-9s9toWiZhdskAD67z
m365 planner bucket tasks list --bucketId "FtzysDykv0-9s9toWiZhdskAD67z"
Lists the Microsoft Planner buckets in the Bucket My Bucket belonging to plan iVPMIgdku0uFlou-KLNg6MkAE1O2
m365 planner bucket tasks list --bucketName "My Bucket" --planId "iVPMIgdku0uFlou-KLNg6MkAE1O2"
Lists the Microsoft Planner buckets in the Bucket My Bucket belonging to plan My Plan in group My Group
m365 planner bucket tasks list --bucketName "My Bucket" --planName "My Plan" --ownerGroupName "My Group"

Perfect spec! Nothing to add. Would you like to pick it up yourself or let others chime in?

I can pick it up since I'm already working on some other planner commands.

Awesome! I appreciate your help 👏

Looking at the planner bucket list command, I wonder if we shouldn't name this command planner task list. If it's not possible to have tasks outside of buckets in Planner, then including the bucket in the name doesn't add anything as it's implicit. Also, let's use task instead of tasks to align it with other commands.

This command would list the tasks in a single bucket within a plan. So if there are multiple buckets in a plan and we want to list the tasks in a particular bucket, this command would come in handy. We can also add a separate command planner plan task list that lists all the tasks across all buckets within a plan. What do you suggest?

What if we had planner task list --bucketId [bucketId] --planId <planId> where bucket is optional and if not specified it returns all tasks for the specified plan?

Good suggestion. I think we can extend the existing planner task list command to list tasks in a plan or bucket (using the options mentioned in this issue specs). Currently, it only lists the tasks assigned to the logged-in user.

Excellent! Let's keep the current behavior as-is and then extend it with additional options.

Updated the specs. Let me know if it looks fine now.

Let's extend Specify bucketId or bucketName, but not both to To retrieve tasks from a bucket, specify bucketId or bucketName, but not both to make it clear that specifying bucketId or bucketName is not required but only needed to retrieve tasks from a specific bucket


Fix display of next cycle start date

#68
Pulled the cycle config to get number of seconds in a cycle and then added that to the start of the current cycle date to get the next cycle date.

Nice work! Only thing is that instead of getting both the proposal and current cycle config again, we can pull that from the $dao plugin where that is already fetched. I also added a watcher for $dao.currentCycleConfig so that whenever that changes, we recalculate the start date of the next cycle. I made a new PR for this, including both your changes and my updates, so I will close this PR.
https://github.com/effectai/effect-dashboard/pull/96


[ZEPPELIN-2587] allow logging in if you're anonymous

What is this PR for?
The login button is not showing (since 0.7.1) if you allow anonymous access. This shows it again.
What type of PR is it?
Bug Fix
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN/ZEPPELIN-2587
How should this be tested?

Start Zeppelin with anonymous support
The login button should now show on the bar

Questions:

Does the licenses files need update?
No
Is there breaking changes for older versions?
No
Does this needs documentation?
No

Could we add a simple selenium test for this ? Regression issue is bad thing.

@zjffdu added one, let me know if that covers it

I don't know the purpose of this PR. If username is anonymous, it means shiro is off. What's your intention?

Hi @jongyoul : I don't understand your comment. You can have "anonymous" when shirt is on. This is even in the shiro example (note: If I understood the shiro example correctly: until the user is not logged in, he is "anonymous" and hence the login page is allowed for "anonymous").
The issue https://issues.apache.org/jira/browse/ZEPPELIN-2587 is real, but I have not yet checked if this PR fixes it.

I got it. I didn't recognize actual username is "anonymous" in production case. If it can be, it will be a problem.

any additional thoughts on this? Is it mergeable? @jongyoul @cfries

@1ambda can you check this issue?

@herval

Could you rebase? base branch is quite old
We need to pass CI. Please the failed tests.

hmm I'm finding it difficult to get all the integration tests to pass. Inclined to test only for the presence of the button.

This is now passing all tests - please advise

Hi folks,
Please let me know if I should close this. Tks!


Is http://dochub.io/ dead for real ?

Hi there,
Today, I just noticed http://dochub.io/ is dead.
I'm so sad :( I think this is a wonderful tool, so easy to find MDN documentation.
Are you considering renew the domain ?
Thanks,
Cyril

As noted in #49  there is another similar project.


Add default cookie path for SvelteKit

Fixes #1300 by adding a default path: '/' to all cookies set through the SvelteKit middleware.
I don't love the shallow copy of the cookie attributes to add a default path, but I think it's better than an explicit cast, like:
cookie.attributes.path ??= '/';

event.cookies.set(cookie.name, cookie.value, cookie.attributes as CookieAttributes & { path: string });

another option would be '' if you wanted to be totally compitable with the current behaviour right?

another option would be '' if you wanted to be totally compitable with the current behaviour right?

Yeah '' would be the current behaviour; I originally went with '/' since it made more sense to me for an auth cookie, but '' is probably better since the app might be hosted on a baseUrl other than '/'

Thanks!

I am still receiving a type error for this, is there a reason why that might be?

I am still receiving a type error for this, is there a reason why that might be?

SvelteKit version, Lucia version, error?

"@sveltejs/kit": "^2.0.6",
"lucia": "3.0.0-beta.13",

Error:
Argument of type 'CookieAttributes' is not assignable to parameter of type 'CookieSerializeOptions & { path: string; }'.   Type 'CookieAttributes' is not assignable to type '{ path: string; }'.

"@sveltejs/kit": "^2.0.6",
"lucia": "3.0.0-beta.13",

const sessionCookie = lucia.createBlankSessionCookie();
event.cookies.set(sessionCookie.name, sessionCookie.value, sessionCookie.attributes);

Error: Argument of type 'CookieAttributes' is not assignable to parameter of type 'CookieSerializeOptions & { path: string; }'. Type 'CookieAttributes' is not assignable to type '{ path: string; }'.

Sorry forgot to reply. This PR was for Lucia 2, not Lucia 3. Just for anyone else getting here, for Lucia 3 you will need to assert/add a default for the path since SvelteKit 2 requires the path attribute.


[WIP] Metagraph conda

[x] add './metagraph/Snakefile
[x] add './metagraph/env.yml
[x] add './metagraph/conf-basic.yml
[x] figure out which metagraph commands we actually want to run
[ ] figure out how to interpret metagraph results

@jackroddy I adjusted the program logic if you want to give it a spin

@jackroddy I adjusted the program logic if you want to give it a spin

I was finally able to get it to work, and now we're getting
0	s10	../data/genome-s10+s11.fa.gz

which looks like what we want.


Can't change the color of a button on press

I am trying to build a like button that changes color when you click it to mark the target as 'liked'. So I used this function called on the button:
function like_quote(_this) {
_this.iconColor= theme.COLORS.THEME
Alert.alert('Like!')
}
<Button
onlyIcon
icon="heart"
key="like"
iconFamily="font-awesome"
iconSize={theme.SIZES.BASE}
iconColor={'#ffbbbb'}//theme.COLORS.THEME
color="transparent"
style={{ marginRight: theme.SIZES.BASE }}
onPress={() => like_quote(this)}
/>,
But nothing happens, I have tried changing other button features options' but nohing happens either.
The button should change color as I change it's color variable.
Android 10 motorola expo version 2.15.4

Hi @Danielgb23
Thank you for this issue but this is not a problem with Galio. This has more to do with some basic principles of React and React-Native. iconColor is a prop of Button, and you can't access it via an external function. In order to change iconColor dynamically you'd have to say something like iconColor={this.state.someVar} and you should change the state via this.setState(); function. You can find more about all of this here: https://reactjs.org/docs/state-and-lifecycle.html .
I'm going to close this issue as it has nothing to do with Galio.


resources: add logo

See BFO or CHEBI: https://www.ebi.ac.uk/ols4/ontologies

Added a branch with a first draft for logos on ResourcesWidget (see pinned development branch).

Logos are only available in the v2-API of OLS, so I added a useLegacy-parameter to toggle the API version. Logos are then only shown if useLegacy == false
For now, logos have their own column in the EuiBasicTable. This is not optimal because some logos (e.g. from Human Disease Ontology) require a higher width to be properly displayed. One approach could be to additionally display the logos, if available, in the "Resource Name" column. However, this makes alphabetical sorting of this column more complicated, and a nice display of both items in one cell is not trivial in EuiBasicTable.

What is your opinion on the current status @jusa3?


SB-28238 fix: Java 11 changes jenkins file update

SB-28238  Migrate to Java 11 for Sunbird Data Products

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Type of change
Please choose appropriate options.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes in the below checkboxes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Ran Test A
[ ] Ran Test B

Test Configuration:

Software versions:
Hardware versions:

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Jenkins files changes.


Provide syntax highlighting from the server

The syntax highlighting is currently provided on the client. Is there a way to provide it from the server?
Use either

This method which suggests that you can do syntax highlighting using semantic token providers
TextMate grammar on the client

Use the textmate solution if the first option doesn't work. With the text mate solution, maybe find a way to provide the language syntax from the server, rather than directly copying/pasting it into the client.

https://code.visualstudio.com/api/references/vscode-api#DocumentSemanticTokensProvider
Server provided tokenization can allow the language server to extend the client side syntax highlighting.
This allows Syntax highlighting to be done intelligently in relation to the whole project.
For example, a constant variable name can be rendered using constant highlighting throughout the project, not just at the place of its declaration.
Semantic highlighting goes on top of the syntax highlighting
https://code.visualstudio.com/api/language-extensions/semantic-highlight-guide

Semantic highlighting is needed, it's fine to leave the base syntax highlighting on the client.

Semantic highlighting is needed, it's fine to leave the base syntax highlighting on the client.


Epinio UI test - Add Epinio's installation through Rancher back in the CI

For now, we are installing Epinio with helm cli command, it's mandatory for the standalone UI.
But finally, we also have to keep testing Epinio's installation via Rancher. (Removed by https://github.com/epinio/epinio-end-to-end-tests/pull/85/commits/4c4bcf70b68188a33125d32781146459ad8111c8)
At the end we will get:
Standalone UI - Helm cli installation
Rancher UI - Helm installation via Rancher UI

Cypress code has to be updated to use the new Epinio single chart.

It should be done at the same time of #91


Fixes #46027 by using box-shadow css to render guides

…rather than background color and computed width
Should also be faster without these computations

This is very cool! Thank you! I will just push a follow-up commit to remove the usage of variables, as this is not supported in IE11 (supported by the monaco editor)


Fix #5 Add pre-commit to format all JS files for indentation.

Closes #5
Closes #4
This PR include Changes for

ESLint - Listing, Enforcing Style Guide
Prettier - Code Formatting
Pre-Commit - Making sure the code that's being committed is following guidelines and is formatted.

CC: @ashutosh1919

@all-contributors add @Sachin-chaurasiya for code and ideas


Removing trailing slashes from

Fixes https://github.com/kubernetes-incubator/service-catalog/issues/567

LGTM if CI if ok

LGTM

Both code and test LGTM

looks fine as long as we construct using the format strings.

I've merged this, as it closes a MVP 2 blocking bug


Deterministic error affecting HTR

We have been seeing one of our test cases deterministically fail on Lassen in the last week or so with the following error message:
...
prometeo_variables.cu:68: void UpdatePropertiesFromPrimitive_kernel(Legion::FieldAccessor<(legion_privilege_mode_t)1, double, 3, long long, Realm::AffineAccessor<double, 3, long long>, false>, Legion::FieldAccessor<(legion_privilege_mode_t)1, double, 3, long long, Realm::AffineAccessor<double, 3, long long>, false>, Legion::FieldAccessor<(legion_privilege_mode_t)1, MyArray<double, 1>, 3, long long, Realm::AffineAccessor<MyArray<double, 1>, 3, long long>, false>, Legion::FieldAccessor<(legion_privilege_mode_t)1, MyArray<double, 3>, 3, long long, Realm::AffineAccessor<MyArray<double, 3>, 3, long long>, false>, Legion::FieldAccessor<(legion_privilege_mode_t)268435458, MyArray<double, 1>, 3, long long, Realm::AffineAccessor<MyArray<double, 1>, 3, long long>, false>, Legion::FieldAccessor<(legion_privilege_mode_t)268435458, double, 3, long long, Realm::AffineAccessor<double, 3, long long>, false>, Legion::FieldAccessor<(legion_privilege_mode_t)268435458, double, 3, long long, Realm::AffineAccessor<double, 3, long long>, false>, Legion::FieldAccessor<(legion_privilege_mode_t)268435458, double, 3, long long, Realm::AffineAccessor<double, 3, long long>, false>, Legion::FieldAccessor<(legion_privilege_mode_t)268435458, MyArray<double, 1>, 3, long long, Realm::AffineAccessor<MyArray<double, 1>, 3, long long>, false>, Legion::FieldAccessor<(legion_privilege_mode_t)268435458, double, 3, long long, Realm::AffineAccessor<double, 3, long long>, false>, Realm::Rect<3, long long>, long long, long long, long long): block: [0,3,14], thread: [0,2,0] Assertion `mix.CheckMixture(MolarFracs[p])` failed.
...
prometeo_ConstPropMix.exec: /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/cuda/cuda_module.cc:340: bool Realm::Cuda::GPUStream::reap_events(Realm::TimeLimit): Assertion `0' failed.

I believe this is the relevant backtrace:
Thread 70 (Thread 0x20005ba9f8b0 (LWP 119373)):
#0  0x0000200002abeb88 in nanosleep () at ../sysdeps/unix/syscall-template.S:81
#1  0x0000200002abe8bc in __sleep (seconds=0) at ../sysdeps/unix/sysv/linux/sleep.c:137
#2  0x0000200000fa8e98 in Realm::realm_freeze (signal=<optimized out>) at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/runtime_impl.cc:183
#3  <signal handler called>
#4  0x0000200002a1fcb0 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55
#5  0x0000200002a2200c in __GI_abort () at abort.c:90
#6  0x0000200002a157d4 in __assert_fail_base (fmt=0x200002b7b7d0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x200001b287e0 "0",
    file=0x200001b47280 "/usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/cuda/cuda_module.cc", line=<optimized out>, function=<optimized out>) at assert.c:92
#7  0x0000200002a158c4 in __GI___assert_fail (assertion=0x200001b287e0 "0", file=0x200001b47280 "/usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/cuda/cuda_module.cc",
    line=<optimized out>, function=0x200001b45d40 <Realm::Cuda::GPUStream::reap_events(Realm::TimeLimit)::__PRETTY_FUNCTION__> "bool Realm::Cuda::GPUStream::reap_events(Realm::TimeLimit)")
    at assert.c:101
#8  0x00002000013063c0 in Realm::Cuda::GPUStream::reap_events (this=0x11abf450, work_until=...) at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/cuda/cuda_module.cc:340
#9  0x000020000130c9d4 in Realm::Cuda::GPUWorker::do_work (this=0x1261c230, work_until=...) at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/cuda/cuda_module.cc:2218
#10 0x0000200000fc9ff4 in Realm::BackgroundWorkManager::Worker::do_work (this=0x20005ba9eb58, max_time_in_ns=-1, interrupt_flag=0x0)
    at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/timers.inl:255
#11 0x0000200000fca8b0 in Realm::BackgroundWorkThread::main_loop (this=0x17728340) at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/bgwork.cc:125
#12 0x00002000010c0684 in Realm::KernelThread::pthread_entry (data=0x17728d80) at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/threads.cc:781
#13 0x0000200002c08cd4 in start_thread (arg=0x20005ba9f8b0) at pthread_create.c:309
#14 0x0000200002b07f14 in clone () at ../sysdeps/unix/sysv/linux/powerpc/powerpc64/clone.S:104

Legion was built with CXXFLAGS="-g -O2" in release mode. This is on 1 node, 1 rank per node with control_replication.
This execution last succeeded on cb61755 and started failing on at least d1ecc4b.
This may not be relevant, but I have only been able to reproduce this on a POWER9 machine but not on an Intel cluster.
Also, could this be added to #1032? Thanks

This looks like an application-level assert?  Can we determine what about MolarFracs[p] is unexpected enough to cause the assert to fire?

I believe it asserts when a task has received bad data. I've re-ran the problem and it succeeds on cb61755. Two commits later (d1ecc4b), it fails. No modifications have been made to the codebase in the meantime.
Additionally, this error has come up non-deterministically for the same problem. Not sure if it's related:
assertion failed: FastInterpInitData: something wrong in the input region

backtrace:
(gdb) bt
#0  0x0000200002abeb88 in nanosleep () at ../sysdeps/unix/syscall-template.S:81
#1  0x0000200002abe8bc in __sleep (seconds=0) at ../sysdeps/unix/sysv/linux/sleep.c:137
#2  0x0000200000fa8e98 in Realm::realm_freeze (signal=<optimized out>) at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/runtime_impl.cc:183
#3  <signal handler called>
#4  0x0000200002a1fcb0 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55
#5  0x0000200002a2200c in __GI_abort () at abort.c:90
#6  0x00000000100781b8 in $<FastInterpInitData> ()
#7  0x000000001007726c in $__regent_task_FastInterpInitData_primary ()
#8  0x000020000124818c in Realm::LocalTaskProcessor::execute_task (this=0x1881ac50, func_id=<optimized out>, task_args=...)
    at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/bytearray.inl:150
#9  0x00002000010e37e4 in Realm::Task::execute_on_processor (this=0x2000c08b45b0, p=...) at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/runtime_impl.h:399
#10 0x00002000010e3994 in Realm::UserThreadTaskScheduler::execute_task (this=<optimized out>, task=<optimized out>) at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/tasks.cc:1632
#11 0x00002000010e6a34 in Realm::ThreadedTaskScheduler::scheduler_loop (this=0x1881aef0) at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/tasks.cc:1103
#12 0x00002000010c6e58 in Realm::UserThread::uthread_entry () at /usr/WS1/stanf_ci/psaap-ci/artifacts/1167868/legion/runtime/realm/threads.cc:1355
#13 0x0000200002a3388c in makecontext () at ../sysdeps/unix/sysv/linux/powerpc/powerpc64/makecontext.S:137
#14 0x0000000000000000 in ?? ()

@lightsighter the commit range that @cmelone is referring to looks to be the merge of the collectiveup branch.  Does that suggest any promising debug paths to follow?

Not unless they are using collective copies/reductions (which I would be a bit surprised if HTR is doing that). I did fix a bug related to that branch today, but it will only matter if you have a collective reduction.

After re-compiling Legion this morning with the new changes and running the problem again, it seems to succeed now. Thanks

That's interesting to know that you're using collective reduction copies.

yeah, @mariodirenzo was wondering about that too

You can end up in this situation if you write code like:
for i in ... do
   my_task(r) -- reduces+(r)
end

Where my_task does a reduction on r. My understanding is that the default mapper turns these into collective instances by default.
Otherwise I'm not sure how you'd be impacted by this.

Yeah, but HTR doesn't use the default mapper.

The mapper of HTR is derived from the default mapper so I think that @elliottslaughter is correct, we are inheriting that aspect.


Fix SSH port binding

Fixes #52
From what I can gather the key lookup of PortBinding in network settings is wrong, but rather than assume it never exists, I kept behavior but if Ports exists, which is used in unit tests and what my Docker daemon exposes, then use that instead.
So unit tests look like what I see on my Docker daemon:
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "5b3ed04c8e2e65b854bd9a05cf2053e0ae4e932e3e43811197a10255e646ad40",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {
                "22/tcp": [
                    {
                        "HostIp": "<IP_ADDRESS>",
                        "HostPort": "4584"
                    }
                ]
            },
            "SandboxKey": "/var/run/docker/netns/5b3ed04c8e2e",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "ee4961d5a4a1b37548b6c24b3b1be1ee0473a4d9057b0502c6ebe4ebf2129d1c",
            "Gateway": "<IP_ADDRESS>",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "<IP_ADDRESS>",
            "IPPrefixLen": 16,
            "IPv6Gateway": "",
            "MacAddress": "02:42:ac:11:00:06",
            "Networks": {
                "bridge": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "c8a38b79ba988bf1d1301ca810fdceae30636924d57466403047607d14466dce",
                    "EndpointID": "ee4961d5a4a1b37548b6c24b3b1be1ee0473a4d9057b0502c6ebe4ebf2129d1c",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:ac:11:00:06",
                    "DriverOpts": null
                }
            }
        }
    }

I also updated unit tests to test using <IP_ADDRESS> since that's what the code sets when setting up the SSH port binding.

I think the coverage went down because fewer of the conditions got hit since now the first port binding check is getting used.  The actual tests all pass though.

@bastelfreak @trevor-vaughan Let me know if this looks good. I've tested this locally on my Mac and it works as expected with Docker.

Adding my 2¢, this also fixed my problem.
Without this change:
Attempting ssh connection to <IP_ADDRESS>, user: root, opts: {:password=>"root", :port=>22, :forward_agent=>false, :auth_methods=>["password", "publickey", "hostbased", "keyboard-interactive"]}
  Warning: Try 1 -- Host <IP_ADDRESS> unreachable: Errno::ECONNREFUSED - Connection refused - connect(2) for <IP_ADDRESS>:22

With this change:
Attempting ssh connection to <IP_ADDRESS>, user: root, opts: {:password=>"root", :port=>"179", :forward_agent=>false, :auth_methods=>["password", "publickey", "hostbased", "keyboard-interactive"]}

Verifying against podman and WSL docker (that should prod any edge cases)


Set an auth key in multi_process_shared.py

Right now, multi_process_shared doesn't set an auth key. When that happens, the manager still creates an auth key for that process based on the current process's authKey - https://github.com/python/cpython/blob/4dc339b4d69195448207e1faecc3e258700daf33/Lib/multiprocessing/managers.py#L503
This causes cross-process authentication to fail and means that multi_process_shared.py doesn't correctly work.
This PR fixes this by using a constant auth key for all managers/requesters/processes.
I was able to get an example running on Dataflow using this approach, but unit testing this effectively in the current setup is probably a feature of its own here (probably this is better suited for a benchmark/regression testing approach).
Fixes #26167

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @robertwb

retest this please


[Win7] Freezing on VBox installation phase.

On Win7 observe freezing on VBpx installation phase.
Not happening right uninstall
2016-07-01_Subutai_install_log.txt

vboxmanage command could not be executed, fixed


Exporting to an existing Worksheet with a large amount of records takes a long time and uses a lot of memory

This may be more ignorance on my part, but I am trying to combine a number of smaller individual workbooks into one workbook with multiple worksheets.  There may be 100k rows or more in the existing Worksheet, and when I export the new rows in, the larger the destination worksheet, the longer it is taking.  I ran a test and had it capture the elapsed time, and compared it to the same operation using Excel COM object.  I also included the associated code from each type.
If there is a better way that I can be doing this?  I don't know if there is a "UsedRange" style option similar to Excel Com that would accomplish the same thing as my code below [-StartRow ((Import-Excel -Path $outFile -WorkSheetname $inWSName).Count + 2)]
Any help would be appreciated.  I'm hoping I can stick with Import-Excel/Export-Excel as the syntax and code is so much simpler.  Unfortunately, the time it takes using my current code makes the process take over 24 hours to run.
of rows imported: 23k
of rows in existing destination spreadsheet: 246k
Using Export-Excel
Elapsed: 90 seconds
Memory usage: ~500 MB
Using Excel COM
Elapsed: 16 seconds
Memory usage: ~100 MB
##Code using Export-Excel
Import-Excel -Path $inFile -WorkSheetname $inWSName | Export-Excel -Path $outFile -WorkSheetname $outWSName -StartRow ((Import-Excel -Path $outFile -WorkSheetname $inWSName).Count + 2) -NoHeader
##code using Excel COM
$Excel = New-Object -ComObject Excel.Application
$Excel.Visible = $True
$Excel.DisplayAlerts = $False
$sourceWB = $Excel.Workbooks.Open($inFile, $true, $true)
$sourceWS = $sourceWB.Worksheets.Item($wsIn)
$sourceRange = $sourceWS.UsedRange
$destWB = $Excel.Workbooks.Open($outFile, $true, $false)
$destWS = $destWB.Worksheets.Item($wsOut)
$destRows = $destWS.UsedRange.Rows.Count
$destRange = $destWS.Range("A$($destRows + 1)")
$sourceRange.Copy()
[void]$destRange.PasteSpecial([Microsoft.Office.Interop.Excel.XlPasteType]::xlPasteValues)
$sourceWB.Close($false)
$destWB.SaveAs($outFile, 51)
$excel.quit()

Yes, Export-Excel will be slower. There is logic that happens for each cell that is added so the appropriate type of data is formatted for that cell, Date Time, Integer. So the COM approach is faster.

I have to agree with @dfinke , it's not possible to speed up the process as there is indeed a lot of logic present on how to export a specific cell depending on its type. I'm afraid this one has to be closed as unsolved.


Failed opening required swift_required.php in /vendor/composer/autoload_real.php on line 66

Laravel Version: 5.3.29
PHP Version: 7.0.8
Database Driver & Version: Not relevant

Description:

$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files

Illuminate\Foundation\ComposerScripts::postUpdate

Warning: Uncaught ErrorException: require(D:\OpenServer\domains\trans.dev\vendor\composer/../swiftmailer/swiftmailer/lib/swift_required.php): failed to open stream: No such file or directory in D:\OpenServer\domains\trans.dev\vendor\composer\autoload_real.php:66
Stack trace:
#0 D:\OpenServer\domains\trans.dev\vendor\composer\autoload_real.php(66): Composer\Util\ErrorHandler::handle(2, 'require(D:\Open...', 'D:\OpenServer\d...', 66, Array)
#1 D:\OpenServer\domains\trans.dev\vendor\composer\autoload_real.php(66): require()
#2 D:\OpenServer\domains\trans.dev\vendor\composer\autoload_real.php(56): composerRequiref708c6e9603f4dc223ededc738105b42('2c102faa651ef8e...', 'D:\OpenServer\d...')
#3 D:\OpenServer\domains\trans.dev\vendor\autoload.php(7): ComposerAutoloaderInitf708c6e9603f4dc223ededc738105b42::getLoader()
#4 D:\OpenServer\domains\trans.dev\vendor\laravel\framework\src\Illuminate\Foundation\ComposerScripts.php(30): require_once('D:\OpenServer\d...')
#5 phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src in D:\OpenServer\domains\trans.dev\vendor\composer\autoload_real.php on line 66
Fatal error: composerRequiref708c6e9603f4dc223ededc738105b42(): Failed opening required 'D:\OpenServer\domains\trans.dev\vendor\composer/../swiftmailer/swiftmailer/lib/swift_required.php' (include_path='.;d:/openserver/modules/php/PHP-7-x64;d:/openserver/modules/php/PHP-7-x64/PEAR/pear') in D:\OpenServer\domains\trans.dev\vendor\composer\autoload_real.php on line 66

Steps To Reproduce:
composer create-project --prefer-dist laravel/laravel trans.dev
or
composer update

In vagrant too:

vagrant@homestead:~/Code/trans.dev$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files

Illuminate\Foundation\ComposerScripts::postUpdate
PHP Warning:  Uncaught ErrorException: require(/home/vagrant/Code/trans.dev/vendor/composer/../swiftmailer/swiftmailer/lib/swift_required.php): failed to open stream: No such file or directory in /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php:66
Stack trace:
#0 /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php(66): Composer\Util\ErrorHandler::handle(2, 'require(/home/v...', '/home/vagrant/C...', 66, Array)
#1 /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php(66): require()
#2 /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php(56): composerRequiref708c6e9603f4dc223ededc738105b42('2c102faa651ef8e...', '/home/vagrant/C...')
#3 /home/vagrant/Code/trans.dev/vendor/autoload.php(7): ComposerAutoloaderInitf708c6e9603f4dc223ededc738105b42::getLoader()
#4 /home/vagrant/Code/trans.dev/vendor/laravel/framework/src/Illuminate/Foundation/ComposerScripts.php(30): require_once('/home/vagrant/C...')
#5 phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php(277): in /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php on line 66

Warning: Uncaught ErrorException: require(/home/vagrant/Code/trans.dev/vendor/composer/../swiftmailer/swiftmailer/lib/swift_required.php): failed to open stream: No such file or directory in /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php:66
Stack trace:
#0 /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php(66): Composer\Util\ErrorHandler::handle(2, 'require(/home/v...', '/home/vagrant/C...', 66, Array)
#1 /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php(66): require()
#2 /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php(56): composerRequiref708c6e9603f4dc223ededc738105b42('2c102faa651ef8e...', '/home/vagrant/C...')
#3 /home/vagrant/Code/trans.dev/vendor/autoload.php(7): ComposerAutoloaderInitf708c6e9603f4dc223ededc738105b42::getLoader()
#4 /home/vagrant/Code/trans.dev/vendor/laravel/framework/src/Illuminate/Foundation/ComposerScripts.php(30): require_once('/home/vagrant/C...')
#5 phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php(277): in /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php on line 66
PHP Fatal error:  composerRequiref708c6e9603f4dc223ededc738105b42(): Failed opening required '/home/vagrant/Code/trans.dev/vendor/composer/../swiftmailer/swiftmailer/lib/swift_required.php' (include_path='.:/usr/share/php') in /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php on line 66
Fatal error: composerRequiref708c6e9603f4dc223ededc738105b42(): Failed opening required '/home/vagrant/Code/trans.dev/vendor/composer/../swiftmailer/swiftmailer/lib/swift_required.php' (include_path='.:/usr/share/php') in /home/vagrant/Code/trans.dev/vendor/composer/autoload_real.php on line 66

Folder ~/Code/trans.dev/vendor/swiftmailer/swiftmailer/ is empty.

Today, January 12, the problem disappeared.
Yesterday, this problem was not only "clean" applications, but also on the projects already running the command composer update.

@andrey-helldar could solve it?

@celorodovalho, I did not find the reason. The problem disappeared on its own and no longer appeared.


MINOR: Fix the missing ApiUtils tests in streams

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@bbejeck could you take a look?

@guozhangwang @bbejeck, thanks for the review comment. I addressed it now.

May be that API follows acks=0 :)

@bbejeck thank you.
ping @guozhangwang @mjsax for final review.

Thank you very much @mjsax, for constructive review comments. I pushed the code changes.

ping @mjsax @guozhangwang for review.

@mjsax, I resolved merge conflicts after PR 5954 merge to trunk.
It was nice code cleanup 👍


Missing encodec key after  export model.

I export my model by https://github.com/facebookresearch/audiocraft/blob/main/docs/MUSICGEN.md#importing--exporting-models
when I use load_compression_model to load my model, I meet the following issues and I cannot find the encodec cfg in compression_state_dict.bin
raise ConfigKeyError(f"Missing key {key!s}")
omegaconf.errors.ConfigAttributeError: Missing key compression_model
full_key: compression_model
object_type=dict

I cannot find encodec weight in my checkpoint.th


How to change frequency bins in specgram to improve recall rate?

I find that bins of frequency of specgram is exactly NFFT/2 + 1.  But how can change the bins of frequency, and not change the NFFT ? NFFT affects how many sample to use in FFT. But why does it also affect bins of frequency?

https://electronics.stackexchange.com/questions/12407/what-is-the-relation-between-fft-length-and-frequency-resolution


Firebase/* dependency not used in concrete target

Just tried to run pod update after installing firestack and am getting this error
Analyzing dependencies
[!] The dependency `Firebase` is not used in any concrete target.
The dependency `Firebase/Core` is not used in any concrete target.
The dependency `Firebase/Auth` is not used in any concrete target.
The dependency `Firebase/Storage` is not used in any concrete target.
The dependency `Firebase/Database` is not used in any concrete target.
The dependency `Firebase/RemoteConfig` is not used in any concrete target.
The dependency `Firebase/Messaging` is not used in any concrete target.

Any ideas to what could be causing this?

Issue appeared to be complex flow of events where cocoapods was not able to fetch from git due to restrictions they reached, hence these deps were not pod'd correctly.


Add .ipynb_checkpoints dir to python gitignore

ipython/jupyter notebooks are often used when working with python projects. But they autosave incremental changes into a .ipynb_checkpoints/ directory. This ignores these directories.

Closing in favor of https://github.com/github/gitignore/blob/master/Global/IPythonNotebook.gitignore


Deluge should be split into separate CLI and GUI versions

Describe the bug
Currently, deluge pulls in GTK3 even if it is running headlessly making the closure far bigger than it needs to be.
Other distributions (Debian as an example) split out deluged, deluge-cli and deluge-gui into separate packages.
Additionally, not only do we pull in GTK3, but we also pull in all its -dev dependencies, which is definitely not correct.
Not going to have time to look at this ATM.
$ nix-store --query -R /nix/store/05x8sj6d81v61mfv7v3mpjzi7i5yh6kx-python3.9-deluge-2.0.3 | grep dev
/nix/store/5hv37pqwjzsd45pj7va82w97dmvv6pbs-zlib-1.2.11-dev
/nix/store/2x091d99vf1kjmc2xi47nb1qvqxj59jc-libpng-apng-1.6.37-dev
/nix/store/hdag9ajgkbacsxmb6xwdn7a8ifya8s5r-python3.9-cffi-1.14.5-dev
/nix/store/f57zkv160ac549k8dhw02ch4jb7spk5r-python3.9-cryptography-3.4.7-dev
/nix/store/5aqdrkcqf64lsxlrgmnxpf167a0yzmr1-python3.9-pyopenssl-20.0.1-dev
/nix/store/pfcx16c0ggbaz9j0ql03yjdz31lssx4m-libxcb-1.14-dev
/nix/store/3sf7zccnilvcqb6vpb61g5avpilvrk1s-xcb-util-0.4.0-dev
/nix/store/iwd8ic5hhwdxn5dga0im55g5hjl270cd-glibc-2.33-47-dev
/nix/store/sws2v5j145i6qbvd5vzka8d7isyi55l3-libffi-3.4.2-dev
/nix/store/a1h6ss6zx0q543sbb0wjain75mfzp4qa-glib-2.68.3-dev
/nix/store/2mcspni88cq0fn6k5k468cbhpx3akdk4-bzip2-<IP_ADDRESS>.2-dev
/nix/store/i3jmkg9hwb9ss6c8mwlwxvqpldl2px6q-freetype-2.11.0-dev
/nix/store/i6sbpknwf4b37q3b507sj5jk6xi37ydj-fontconfig-2.13.94-dev
/nix/store/psldkb7gm9hzkh7hvf7lyavbk6c5rfp6-expat-2.4.1-dev
/nix/store/4agx5ypl8w1wjf9rwipfyr3l9bqa3c2f-libglvnd-1.3.3-dev
/nix/store/qhy3i31xw1ydgy23ymbv69ap3l1yxghx-libGL-1.3.3-dev
/nix/store/g4da5syjj69p11npzf9bcj3s429snk3r-libXau-1.0.9-dev
/nix/store/v5g2bns4pszfx8gxdwxzarf22v946w85-libXext-1.3.4-dev
/nix/store/zbibvxjirly4gcykl6l4d08arajz8mk6-libX11-1.7.2-dev
/nix/store/x0k5w4xz0gqjnlffi1xwmxhscyz0d4p5-libXrender-0.9.10-dev
/nix/store/i3x4h3hbs4vdj29nkng0fij5gzipl09c-cairo-1.16.0-dev
/nix/store/79ih68gpmh4s54k2jfnmg99i1qjk49dg-python3.9-pygobject-3.40.1-dev
/nix/store/fyc1d0lgsbna1r24mjkqwj4srhl4s6py-libtorrent-rasterbar-1.2.11-dev
/nix/store/7fy5dr5lx22wn1n5l1pvsacrli87hd7q-xz-5.2.5-dev
/nix/store/dmg49fmv4ims56l415g6nwfcx1vpy9xa-libjpeg-turbo-2.1.0-dev
/nix/store/1r4c5p3bamjaqmicsrp4vqcqh6hqwmvb-libtiff-4.3.0-dev
/nix/store/mvm65g91p9r4aa1fyqjb1ra30lb28sxk-gdk-pixbuf-2.42.6-dev
/nix/store/iqyyy7cw98bjq2ya5p335i15v9acynxa-librsvg-2.50.7-dev
/nix/store/21xr43sx8cszvlja0dwaqgqwfza7bf1b-wayland-1.19.0-dev
/nix/store/63ywnx6bcj9lxxfsfwn7zvzpw0ldswxh-atk-2.36.0-dev
/nix/store/gzldmfvy21bpg6b0cnilmkk1slb2pdaa-libICE-1.0.10-dev
/nix/store/8bz7xbxm9w3k3vmaljwwg8zzanhrywvk-libSM-1.2.3-dev
/nix/store/l4fm2lyi8nkamzzfr2aamrmcah3rfa7c-libXfixes-6.0.0-dev
/nix/store/cqhgbihbj0bxmznn5mb6va2ksryr7nyk-libXcomposite-0.4.5-dev
/nix/store/dc1rq4y9i2mx2ngznfl2hxbjlyrx4bya-libXinerama-1.1.4-dev
/nix/store/dzlw8n4npp38xy8v17239lnr6zd9764i-libXcursor-1.2.0-dev
/nix/store/lfldhb8a5mrawhzdsk8xnnh4sm95ns6a-libXft-2.3.3-dev
/nix/store/nm95iah26pyzbqi6vii56zaavggnmmd2-harfbuzz-2.8.2-dev
/nix/store/l62zd61cpb4byhl6y098mwybbww4lkmd-pango-1.48.5-dev
/nix/store/dkhw4yj6nv6l8p98kqc8am6qpgyv13cv-gmp-6.2.1-dev
/nix/store/pg2d5r2klsc7d90yvm62rh7z279bkqhq-cups-2.3.3-dev
/nix/store/sad7krnz20gi4mjlgw1bsz6cm6qy2iv9-libXrandr-1.5.2-dev
/nix/store/w4d399a32mvgr4i6c2flfpid6dzjqx34-libXi-1.7.10-dev
/nix/store/lfw77g8nh4y7l9cb1l92z1wyhv56bsc3-gtk+3-3.24.30-dev
/nix/store/xfcnaickn31bn93y8xv3i77b3vn63chn-python3.9-dbus-python-1.2.16-dev
/nix/store/xwbvnk18s857b8zpf0iklqbq46gv8lmq-gobject-introspection-1.68.0-dev

Steps To Reproduce
Steps to reproduce the behavior:

install deluge
observe the large closure

Notify maintainers

Cc: @petabyteboy

I think this is a good idea. We should add a package called deluge-gtk. For anyone who wants to implement this, you could use the Archlinux PKGBUILD for reference https://github.com/archlinux/svntogit-packages/blob/packages/deluge/trunk/PKGBUILD


The extension could not be deployed because it is already deployed on another tenant

Following #4256 #4972
We've prepared / converted an onprem C/AL 14 database via Powershell to AL via following path:

Upgrade the database to v15 via some 'temporary' upgrade extensions to ensure data is properly moved to the extension tables. (Database contains approx. 15 extensions.)
Upgrade the database to v15.1 with the actual / dev extensions to get the latest code modifications.

All is done via powershell commandlets and published to scope tenant and tenant default.
All is ran OnPrem not using Docker.
Now we want to benefit from VSCode and publish new code modifications (without increasing the version no, since it all concerns internal dev for the upcoming weeks and to avoid the Start-NAVAppDataUpgrade like warnings) which results in following error
The extension could not be deployed because it is already deployed on another tenant
How can we ensure VSCode can connect to the previously executed PS steps? (Unsure about the whole -devenpoint and production scope features). We'd like to use VSCode without any additional PS scripts to publish / maintain new (dev) version of our extensions.

Hi,
I did not test that for other cases such as when multitenancy is involved, but as you already seem to use the scope and tenant used by a default VScode publish:
Have you tried to uninstall + unpublish the apps ( keeping the data by skipping the clean sync ) and publish using VScode afterwards?
That should enable you to do further publishs using VScode while keeping the data you migrated in your previous steps.
Before doing a deployment for a live system I would reverse that process to ensure that all of your apps are in "production mode".
Best Regards,
Josh

@JoshC94 Uninstall / unpublish via PS and republish via VSCode indeed works. But that's the point I wanted to make. We're trying to prepare a dev database by scripting the installation of all our extensions. Having to manually publish tens of extensions manually afterwards in VSCode is a bit counter productive.
The same when the publishing of the base apps fails. All other dependend extensions get uninstalled and require manual reinstallation.
Having a force 'Full publish' in VSCode would at least ease working with multiple extensions.

Oh, sorry, I missed that point.
Well in that case, I guess you could just go by using the Dev Endpoint for the app installation in your scripts like NavContainerHelper does.
I suppose you are not using a container for your Dev System, so the function might not be helpful as-is.
Anyways you can just take a look at the source (and adapt the same logic for your own scripts. You can find it here: Publish-NAVContainerApp

We've already tried to look at created a custom Publish-NAVApp based on the above -devendpoint code. However, this adds another complexity as described below https://freddysblog.com/2019/12/09/having-demo-data-while-developing-business-central-apps-with-docker/
Overall, it's just very frustrating that VSCode has been announced as the new dev environment, although the dev experience is just not good when dealing with several dependend extensions and that you'll have to revert to powershell scripts instead (that you need to create in case you're not on Docker ...) for most basic development tasks.

Publishing with PowerShell and using VsCode to publish are apple and bananas.
When you publish with PowerShell you publish into the global scope , the app will be visible to all tenants in the system. When you use VSCode you publish into the dev scope. Dev scope is something that you use when developing your apps.
Things published into the global scope are very special and protected.
An app published to global scope should never reference apps published to dev scope or tenant scope (per tenant extensions).
A dev scope published app if it has a reference to a global scope published app , this global app will not be uninstalled/unpublished/republish(recompile)/reinstalled. Basically it is ignored in the dependency publishing logic from VsCode.
See here:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-work-workspace-projects-references
"Any other app that directly depend on Base and are not published in the global scope - in this case Leaf and External - are unpublished."

This issue has been closed because it has not had recent activity. Please open a new issue if you believe this has not been resolved and reference the current issue.


[DEVOPS-758] Bump wallet applicationVersion

There will be new wallet installers proposed on the network.
See also: https://github.com/input-output-hk/internal-documentation/wiki/Daedalus-installer-history

Why go with 6 -> 8 with mainnet?

As far as I can tell, what I have done is:

mainnet  4 → 5
mainnet_dryrun_full (staging) 6 → 8

In the previous release, the staging applicationVersion was bumped to 7 in a separate branch.

You're right - sleep deprivation doesn't help me argue :)


Need Nuxt 3.0.0-rc.11 support

I am currently using Nuxt 3 rc version 11 and found this issue while running the app locally using yarn dev:
Module @vueuse/motion is disabled due to incompatibility issues:
 - [nuxt] Nuxt version `>=3.0.0` is required but currently using `3.0.0-rc.11`

And also:
[Vue warn]: Failed to resolve directive: motion
[nuxt] [request error] [unhandled] [500] Cannot read property 'getSSRProps' of undefined

I still get:
ReferenceError: useMotionControls is not defined among other APIs
Seems there as missing lines in Types\imports.d.ts


Update ffxivcraftmodel.js

Fixed Ingenuity and Ingenuity II for 60 lvl 2, 3 and 4*

How large a dataset have you tested these new values on?

Few recipes for each star level with 2 different values of craftsmanship. So far it seems to be accurate. Unlike how it is right now.

Fair enough. Since we can't test it in game ourselves, and the change seems reasonable, I'll have to trust you. :)

Change is deployed to beta site.

Great. Thanks. There is also a problem with inaccurate CS 2 (unbuffed) where it's off by 2, but I haven't found the correct value.

That one's going to be trickier. :)

Haha, indeed. Also, still don't see changes at http://ffxiv-beta.lokyst.net/#/simulator

I've verified that the file has been updated on the webhost, so you may need to force a refresh in your browser.

It seems like leveldiff penalty is not capped at -6. For 4* it's capped at -8 and for 3* at -7. I got numbers right, but there is mismatch for either regular synthesis (100%) or rapid synthesis (250%).  I think I'm getting  close.


Demo not working

Getting undefined method 'for' for #<Devise::ParameterSanitizer:0x007fbfb5a59ed0>
in
app/controllers/application_controller.rb:11:in 'configure_permitted_parameters'

@archonic  go to application_controller.rb and change the following
-    devise_parameter_sanitizer.for(:sign_in) << :otp_attempt
+    devise_parameter_sanitizer.permit(:sign_in, keys: [:otp_attempt])

Later i will pull request it

@archonic  go to application_controller.rb and change the following
-    devise_parameter_sanitizer.for(:sign_in) << :otp_attempt
+    devise_parameter_sanitizer.permit(:sign_in, keys: [:otp_attempt])

Later i will pull request it

Fixed here: https://github.com/tinfoil/devise-two-factor/pull/102


FileLoadException: Could not load file or assembly System.Runtime, Version=<IP_ADDRESS>

I have an asp.net core 2.0 application that runs on full .net framework 4.6.1. It works fine locally but when I deploy it to Azure I receive the following error:
FileLoadException: Could not load file or assembly 'System.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Any idea how to fix that?

I am having this issue.  What was your resolution?
Visual Studio 2017.3, Framework 461, published to Windows Server 2012R2 with Framework 4.7 and .NetCore 2.0.0 Hosting installed.

Found answer here:
https://stackoverflow.com/questions/45894659/fileloadexception-could-not-load-file-or-assembly-system-runtime-version-4-2-0
I started with a .Net Core app, switched to net461.  Needed to delete all published artifacts and republish.

Anytime one switches frameworks or versions, bin and obj must be deleted (or full delete and rede ploy in production setting).


[Feature request] separate new chats from new matches

Separate the unread count from the new matches count. Confusing when there's a number on the chat icon but it's indicating a new match and not a new message.

Perhaps a blue badge above the red one that indicates new match count.


Control element method does not work in Safari Version 11.0 (126<IP_ADDRESS>.7)

Table of Contents

Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment

Expected Behavior

Click on the control element example should load the calendar.
Current Behavior

Click on the control element example does nothing
Possible Solution

Steps to Reproduce (for bugs)

Navigate to http://pushtell.github.io/react-bootstrap-date-picker/
Click on the Control Element example

Context

Whatever breaks this example also breaks similar usage in my app.  When using the Control Element method, users can't use the date control.
Your Environment

Version used:
Browser Name and version: Safari http://pushtell.github.io/react-bootstrap-date-picker/
Operating System and version (desktop or mobile): macOS Sierra 10.12.6
Link to your project:

@juanpaco Have you had any luck debugging this issue? I am experiencing this same issue in Safari.

I haven't, no.  I ended up using https://github.com/YouCanBookMe/react-datetime instead.

Ok, thanks.

My fix for this, setting the onClick event to call the onFocus function.
``const CustomControl = ({...props}) => {
return (<Button onClick={props.onFocus} {...props}>{props.value});
};