"git lint" issue on Windows machine

For set of changed files in python, as soon as we run the "git lint" command,
We're getting these error,

Linting file: webapp\apps\core\utils.py

SKIPPED: pylint is not installed. Run pip install pylint.

SKIPPED: pep8 is not installed. Run pip install pep8.

But the following setups were installed in both inside and outside virtual environment.
Please let us know if any specific action needs to be taken for windows machine?

This is because the configuration file is tailored for unix systems (i.e., the executables do not have the .exe extension).
You would need to fork the configuration file and adjust the names to what is used in Windows. I believe to run pylint you execute pylint.exe, so you would need to change https://github.com/sk-/git-lint/blob/master/gitlint/configs/config.yaml#L93 so that the command is now python.exe

Ohk. thanks


Fixed Hadoop version to 2.4.x

Thanks for this! It looks like SequenceIQ has a Hadoop 2.4.1 tag as well as 2.4.0---would you point this at that tag instead?

Done. Thanks.


Fix get_formatting_definition() for unknown locale

It should use upper case value of DEFAULT to get formatting definition.

Closing in favour of #75 which has tests.

Closing in favour of #75 which has tests.


Change cgroup driver from systemd to cgroupfs

What this PR does / why we need it: When using the systemd driver, node allocatable limits are not being set properly by kubelet. Switching driver to cgroupfs fixes this issue.
Change cgroup driver from systemd to cgroupfs for docker and kubelet

I am bit concerned, what the effects are when we update a running cluster with that change.
Can you do some testing @dippynark

/assign @simonswine

/assign @dippynark can you please respond to my comment before that one and resolve the merge conflict. Thanks

/test puppet-tarmak-acceptance-centos v1.9

/test puppet-tarmak-acceptance-centos v1.9

@simonswine I had to restart docker manually but Pods were moved to the new cgroup

Can we make the restart happen through puppet (we should be able to)
/reassign @dippynark

/retest

/retest

@simonswine let me know when you are happy this works and I will work on fixing the tests

/test puppet-tarmak-acceptance-centos v1.6

/test puppet-tarmak-acceptance-centos v1.8

/test puppet-tarmak-acceptance-ubuntu v1.9

/assign @simonswine

/uassign

/unassign

/approve
/lgtm


Move node commands to top level

Partly resolves: #926
Changelog
- description: |
    The node commands are era agnostic and should be moved to the top level
# uncomment types applicable to the change:
  type:
  - feature        # introduces a new featur
  - compatible     # the API has changed but is non-breaking

Context
Additional context for the PR goes here. If the PR fixes a particular issue please provide a link to the issue.
How to trust this PR
Highlight important bits of the PR that will make the review faster. If there are commands the reviewer can run to observe the new behavior, describe them.
Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated. See Running tests for more details
[ ] Self-reviewed the diff

@Jimbo4350> how about moving debug check-node-configuration (i.e. https://github.com/IntersectMBO/cardano-cli/pull/923) to node check-configuration?

@Jimbo4350> how about moving debug check-node-configuration (i.e. #923) to node check-configuration?

Sure. In a follow up PR.


Rescue julia bot by whiltelisting rubocop and stove

@PrajaktaPurohit @tyler-ball @btm @randomcamel

Any description of what happened perhaps?

@ksubrama do we actually intend to distribute stove?

@ksubrama never mind, it doesn't matter--it'll try to solve the dev deps together regardless of whether it's distributed / installed.

👍

:+1:


Rule request: no throwning new errors in non-never functions

Looking forward to some :fire: discussions around this one. 😉
I recently spent some time diagnosing "miscellaneous" errors in a large web app (many edge cases, wide browser support, internally developed HTML view layer). Miscellaneous in this context means they came without stack traces or line/column information, which happens with Internet Explorer in cross-origin <iframe> embeds or generally from older builds of Edge.
In order to still get stack traces on IE and old Edge, we had to stop directly throwing new Errors and instead use a factory:
function errorFactory(message: string): Error {
    if (isInternetExplorer()) message += `\nStack: ${new Error().stack}`;
    throw new Error(message);
}

// Error case, instead of throw new Error("foo");
throw errorFactory("foo");

Alternative could be using a function returning never or an Error sub-class that takes in a stack.
function throwAndLog(message: string): never {
    if (isInternetExplorer()) message += `\nStack: ${new Error().stack}`;
    throw new Error(message);
}

class ErrorWithManualStack extends Error {
    constructor(message, stack) {
        if (isInternetExplorer()) message += `\nStack: ${stack}`;
        super(message);
    }
}

throwAndLog("foo");
throw new ErrorWithManualStack("foo", new Error().stack); // eww

Vaguely related: there's also the (controversial?) "exceptions are bad" mindset some folks have. A tl;dr is that throwing errors adds an implicit "this might do something else" to functions that then must be accounted for.
So, would it make sense for TSLint to have any variation of a no-throwing-new-errors rule? Some options to enable by default could be...

Allowing throw errorFactory("foo") and similar
Allowing throw new ErrorWithManualStack("foo", new Error().stack) and similar
Allowing throws in functions whose return types are only never
Not enabling this in tslint:all

Sounds a bit too specific to be in TSLint core.

Not enabling this in tslint:all

I think this is evidence enough that it's probably better off in a custom rules package.

Allowing throws in functions whose return types are only never

That one would make sense, but you still need throw neverReturningFunction("message") to make the compiler happy.  You need to throw there to tell the compiler that control flow ends. But the throw is actually never executed because the factory already throws. That's not a pattern I'd like to advertise.

But the throw is actually never executed because the factory already throws

Alternately:
function errorFactory(message: string): Error {
    if (isInternetExplorer()) message += `\nStack: ${new Error().stack}`;
    return new Error(message);
 // ^^^^^^
}

// Error case, instead of throw new Error("foo");
throw errorFactory("foo");


README: update the documentation link

because we have readme = "README.md" set in Cargo.toml the crates.io page
renders the README which contains a BIG "Documentation" link that points to
docs.rs which is broken. This commit makes that link point to our GH page.
r? @rust-embedded/cortex-m (anyone)
I have also observed that the smaller "documentation" link in the crates.io page
is ignoring the "documentation" field and pointing to docs.rs. I reported this
as a bug in rust-lang/crates.io#1485

bors r+


I keep getting the "Conflict" error for one of the automation jobs below, any advise?

{ "id": "/subscriptions/xxxxxxx/resourceGroups/xxxxx/providers/Microsoft.Resources/deployments/Microsoft.Template/operations/5B9C73BD0DB893A0", "operationId": "5B9C73BD0DB893A0", "properties": { "provisioningOperation": "Create", "provisioningState": "Failed", "timestamp": "2019-06-18T23:17:12.8511623Z", "duration": "PT54.0899824S", "trackingId": "1989efdf-40dc-484a-b21c-e04b7beade59", "statusCode": "Conflict", "statusMessage": { "status": "Failed", "error": { "code": "ResourceDeploymentFailure", "message": "The resource operation completed with terminal provisioning state 'Failed'." } }, "targetResource": { "id": "/subscriptions/xxxxx/resourceGroups/TKNZ-WVD-Demo/providers/Microsoft.Automation/automationAccounts/wvdsaas-autoAccount-dbnqpsqyfqx72/jobs/147b886a-2edd-5345-a303-c9be20a36f27", "resourceType": "Microsoft.Automation/automationAccounts/jobs", "resourceName": "wvdsaas-autoAccount-dbnqpsqyfqx72/147b886a-2edd-5345-a303-c9be20a36f27" } }}

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

ID: a143e190-2e63-e3b9-725b-d433075e6e80
Version Independent ID: b693e675-3258-473d-d4da-11bcc942083f
Content: Deploy management tool - Azure
Content Source: articles/virtual-desktop/manage-resources-using-ui.md
Service: virtual-desktop
GitHub Login: @ChJenk
Microsoft Alias: v-chjenk

@jan4victory thanks for reaching out. If you still need help just let us know.

+1, having the same issue!

@anersidahl, make sure the Azure Active Directory user account have full access to the subscription even it is a Global Admin account. That's how I fixed my issue.

I'm having the same issue

+1, tried to delegate owner permission to subscription and event global admin in aad, still failed...
{ "id": "/subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Resources/deployments/Microsoft.Template/operations/198F6D3E7C788621", "operationId": "198F6D3E7C788621", "properties": { "provisioningOperation": "Create", "provisioningState": "Failed", "timestamp": "2019-10-08T05:57:14.2258101Z", "duration": "PT0.3466203S", "trackingId": "2040443f-a61e-473f-8192-e3a4aed844f7", "statusCode": "Conflict", "statusMessage": { "code": "Conflict", "message": "Job with specified id already exists. Job id: 440ed4af-3f52-50be-af28-ecb278bd5898" }, "targetResource": { "id": "/subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Automation/automationAccounts/wvdsaas-autoAccount-3ld562fiy4m3s/jobs/440ed4af-3f52-50be-af28-ecb278bd5898", "resourceType": "Microsoft.Automation/automationAccounts/jobs", "resourceName": "wvdsaas-autoAccount-3ld562fiy4m3s/440ed4af-3f52-50be-af28-ecb278bd5898" } }}

Hello
Did anyone solve this ?
Same issue for me on initial deployment. I have checked all permissions:
Error
{ "id": "/subscriptions/ccb48057-fba5-48fb-8b5f-858c54753d23/resourceGroups/CetusVWD-MGMT/providers/Microsoft.Resources/deployments/Microsoft.Template/operations/B9D63EC87D210D52", "operationId": "B9D63EC87D210D52", "properties": { "provisioningOperation": "Create", "provisioningState": "Failed", "timestamp": "2019-10-14T13:35:03.87176Z", "duration": "PT1M6.4994645S", "trackingId": "402b6a32-631a-4e26-b5d2-a51883857f77", "statusCode": "Conflict", "statusMessage": { "status": "Failed", "error": { "code": "ResourceDeploymentFailure", "message": "The resource operation completed with terminal provisioning state 'Failed'." } }, "targetResource": { "id": "/subscriptions/ccb48057-fba5-48fb-8b5f-858c54753d23/resourceGroups/CetusVWD-MGMT/providers/Microsoft.Automation/automationAccounts/wvdsaas-autoAccount-z5i2hd6nf7k5y/jobs/aa5c7b12-6610-5d77-8ff3-2ebf426e2119", "resourceType": "Microsoft.Automation/automationAccounts/jobs", "resourceName": "wvdsaas-autoAccount-z5i2hd6nf7k5y/aa5c7b12-6610-5d77-8ff3-2ebf426e2119" } }}

I have been having the same issue with Conflict for months....  Unable to deploy this...
{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
"details": [
{
"code": "Conflict",
"message": "{\r\n  "status": "Failed",\r\n  "error": {\r\n    "code": "ResourceDeploymentFailure",\r\n    "message": "The resource operation completed with terminal provisioning state 'Failed'."\r\n  }\r\n}"
}
]
}
{ "id": "/subscriptions/536e4a5e-e60d-4b8a-9b79-be033bf57849/resourceGroups/WVD-Mgmt/providers/Microsoft.Resources/deployments/Microsoft.Template/operations/FCD2DA2A9B345E54", "operationId": "FCD2DA2A9B345E54", "properties": { "provisioningOperation": "Create", "provisioningState": "Failed", "timestamp": "2019-10-14T15:37:08.3732282Z", "duration": "PT1M38.8273656S", "trackingId": "53208262-1bdf-43d7-9af0-88e39ea626b0", "statusCode": "Conflict", "statusMessage": { "status": "Failed", "error": { "code": "ResourceDeploymentFailure", "message": "The resource operation completed with terminal provisioning state 'Failed'." } }, "targetResource": { "id": "/subscriptions/536e4a5e-e60d-4b8a-9b79-be033bf57849/resourceGroups/WVD-Mgmt/providers/Microsoft.Automation/automationAccounts/wvdsaas-autoAccount-4pdqrvbpen2bu/jobs/31ac591a-88b6-5e5f-8feb-bba4468b652c", "resourceType": "Microsoft.Automation/automationAccounts/jobs", "resourceName": "wvdsaas-autoAccount-4pdqrvbpen2bu/31ac591a-88b6-5e5f-8feb-bba4468b652c" } }}

Me too. Get a conflict error with a GA account

Make sure the account is not MFA-activated, if so use SVC-principal instead.
Also make sure it is only 2 apps in Azure AD with the name Windows Virtual Desktop. In my case I had a third one which made the conflict happen.
From: Gerry Nicol<EMAIL_ADDRESS>Sent: 18 October 2019 10:49
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: andersidahl<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] I keep getting the "Conflict" error for one of the automation jobs below, any advise? (#33551)
Me too. Get a conflict error with a GA account
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/33551?email_source=notifications&email_token=ACPTSKX3DXCPJCNUVB4RS4LQPF2BPA5CNFSM4HZETONKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBTMX2I#issuecomment-543607785, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACPTSKVPEWWGF3JE4YQH63LQPF2BPANCNFSM4HZETONA.

Had this issue as well. I had deleted my first deployment after noticing the template deploys a Standard tier which seemed overkill for a test environment. Ran the template again but edited in a B1 plan. Then got the error reported by others.
Error code: Conflict
Message: Job with specified id already exists. Job id: 92a998ce-1b47-5a56-95ad-f52b14decf62

I had removed the previous app registrations before running again so it wasn't that.
It worked for me by locating the Runbook that was failing and running it manually:
Automation Accounts > wvdsaas > Runbooks > msftsaasbook > Overview > click Start, wait for it to complete. The automation account is removed when its done.
The web app now seems to be working fine.

Same issue as everyone else here. The deployment fails with a conflict on the automation account

Same for us

Make sure the account is not MFA-activated, if so use SVC-principal instead. Also make sure it is only 2 apps in Azure AD with the name Windows Virtual Desktop. In my case I had a third one which made the conflict happen. From: Gerry Nicol<EMAIL_ADDRESS>Sent: 18 October 2019 10:49 To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: andersidahl<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] I keep getting the "Conflict" error for one of the automation jobs below, any advise? (#33551) Me too. Get a conflict error with a GA account — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#33551?email_source=notifications&email_token=ACPTSKX3DXCPJCNUVB4RS4LQPF2BPA5CNFSM4HZETONKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBTMX2I#issuecomment-543607785>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACPTSKVPEWWGF3JE4YQH63LQPF2BPANCNFSM4HZETONA.

Ah! We have 2x WVDs and 1x WVD client.  The WVDs are Default Access and the other is Tenant Creator.  Which should i delete?

I tried running the Runbook manually, but keep getting these errors:
#############
Select-AzSubscription : Please provide a valid tenant or a valid subscription. At line:39 char:1 + Select-AzSubscription -SubscriptionId $SubscriptionId + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : CloseError: (:) [Set-AzContext], ArgumentException + FullyQualifiedErrorId : Microsoft.Azure.Commands.Profile.SetAzureRMContextCommand
#############
AND
#############
Get-AzWebApp : 'this.Client.SubscriptionId' cannot be null. At line:80 char:15 + ... GetWebApp = Get-AzWebApp -Name $WebApp -ResourceGroupName $ResourceGr ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : CloseError: (:) [Get-AzWebApp], ValidationException + FullyQualifiedErrorId : Microsoft.Azure.Commands.WebApps.Cmdlets.WebApps.GetAzureWebAppCmdlet
#############
The account doesn't have MFA enabled, and when I run the commands that are failing  on the Runbook manually on my machine, they work fine, using the same account.

Why is this issue closed?
I have the same issue. Automationaccounts/job failed code: conflict
I am using a Global Admin & Subscription Owner account without MFA.
I have only the two Windows Virtual Desktop enterprise apps.
I tried to run the automation job that failed manually, I have the error:
Cannot bind argument to parameter 'ObjectId' because it is null. (Cannot bind argument to parameter 'ObjectId' because it is null.)
I deleted everything and run the template again. Same error.
please advice

I don't think this issue should be closed either.  I just ran into this same issue, after completely deleting and attempting to redeploy my management site.  The only thing that worked for me was @chrisred's suggestion of manually restarting the runbook - which then ran to successful completion.
I had previously redeployed the site once or twice without this problem, but I agree with @proximagr that it seems odd for this to be closed when there must still be some issue that needs resolving.

i am also running on the same issue and the use is a global admin,Contributor and RDS Owner, i am unable to get it to work?


You can query the Microsoft graph directly for extension attributes

Azure AD graph is obsolete and extension attributes can now be queried directly through the Microsoft graph (using /onpremisesextensionattributes)

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

@bartvermeersch : Thanks for your contribution! The author(s) have been notified to review your proposed change.

My edits were incorrect and can be discarded.


warning：Throttling history state changes to prevent the browser from hanging.

If you are reporting a bug or requesting support, start here:
Bug or support request summary
I meet this warning when click the sidemenu to view a story.
I make a breakpoint to the code where throws this warning. It seems that that line is called many times after click the sidemenu.
Is this a bug of storybook or a problem with my usage?
Is this the same problem as #3211
Steps to reproduce
click the sidebar to view a story
Please specify which version of Storybook and optionally any affected addons that you're running
"@storybook/addon-actions": "^3.4.3",
"@storybook/addon-centered": "^3.4.2",
"@storybook/addon-knobs": "^3.4.2",
"@storybook/addon-links": "^3.4.2",
"@storybook/addon-options": "^3.4.2",
"@storybook/vue": "^3.4.2",

Affected platforms
Google Chrome 68.0.3440.106
Screenshots / Screencast / Code Snippets (Optional)

I seem to run into this after a hot reload and then clicking on a new story. Removing the knobs addon fixes it. I'm on v3.4.10.
Looks like it's the same thing as #3211 and fixed in v4, but I haven't tried it yet.

I ran into this as well.. happens to me when there are a lot of knobs on a single component

Should be much much better in 4.0.0

I still experience this with @storybook/vue and @storybook/addon-knobs in version 4.0.4.
There's a text field and I type (not paste) hello world (in a reasonable speed), I end up with the knobs input showing "hel d" and the browser console showing 98x Throttling history state changes to prevent the browser from hanging..
The problem can be reproduced with a very simple setup:

import { storiesOf } from '@storybook/vue'
import { text } from '@storybook/addon-knobs'

storiesOf('Knobs Performance Demo', module).add('simple input', () => {
  return {
    template: `<input type="text" :value="value" />`,
    data () {
      return {
        value: text('input.value', ''),
      }
    },
  }
})

here's the trace I'm getting for one of those messages:
handle_routing.js:64 Throttling history state changes to prevent the browser from hanging.
  | changeUrl | @ | handle_routing.js:64
  | (anonymous) | @ | handle_routing.js:129
  | (anonymous) | @ | index.js:41
  | fireSubscriptions | @ | index.js:40
  | update | @ | index.js:78
  | setOptions | @ | api.js:135
  | setOptions | @ | init_api.js:45
  | (anonymous) | @ | index.js:21
  | (anonymous) | @ | index.js:160
  | _handleEvent | @ | index.js:159
  | (anonymous) | @ | index.js:35
  | _handleEvent | @ | index.js:116
  | postMessage (async) |   |
  | send | @ | index.js:74
  | handler | @ | index.js:71
  | emit | @ | index.js:80
  | emitOptions | @ | index.js:51
  | wrapper | @ | index.js:71
  | (anonymous) | @ | make-decorator.js:42
  | (anonymous) | @ | make-decorator.js:66
  | (anonymous) | @ | index.js:32
  | story | @ | index.js:29
  | (anonymous) | @ | index.js:41
  | story | @ | index.js:29
  | wrapper | @ | index.js:53
  | (anonymous) | @ | make-decorator.js:42
  | (anonymous) | @ | make-decorator.js:66
  | (anonymous) | @ | index.js:32
  | story | @ | index.js:29
  | withSubscriptionTracking | @ | client_api.js:58
  | (anonymous) | @ | index.js:32
  | (anonymous) | @ | story_store.js:162
  | render | @ | render.js:41
  | renderMain | @ | start.js:190
  | renderUI | @ | start.js:210
  | forceReRender | @ | start.js:220
  | (anonymous) | @ | index.js:160
  | _handleEvent | @ | index.js:159
  | handler | @ | index.js:74
  | emit | @ | index.js:80
  | forceReRender | @ | registerKnobs.js:22
  | knobChanged | @ | registerKnobs.js:43
  | (anonymous) | @ | index.js:160
  | _handleEvent | @ | index.js:159
  | (anonymous) | @ | index.js:35
  | _handleEvent | @ | index.js:116
  | postMessage (async) |   |
  | send | @ | index.js:74
  | handler | @ | index.js:71
  | emit | @ | index.js:80
  | (anonymous) | @ | Panel.js:134
  | (anonymous) | @ | Panel.js:145
  | (anonymous) | @ | PropForm.js:65
  | (anonymous) | @ | Text.js:50
  | TextareaAutosize._this._onChange | @ | react-textarea-autos….esm.browser.js:246
  | callCallback | @ | react-dom.development.js:149
  | invokeGuardedCallbackDev | @ | react-dom.development.js:199
  | invokeGuardedCallback | @ | react-dom.development.js:256
  | invokeGuardedCallbackAndCatchFirstError | @ | react-dom.development.js:270
  | executeDispatch | @ | react-dom.development.js:561
  | executeDispatchesInOrder | @ | react-dom.development.js:583
  | executeDispatchesAndRelease | @ | react-dom.development.js:680
  | executeDispatchesAndReleaseTopLevel | @ | react-dom.development.js:688
  | forEachAccumulated | @ | react-dom.development.js:660
  | runEventsInBatch | @ | react-dom.development.js:816
  | runExtractedEventsInBatch | @ | react-dom.development.js:824
  | handleTopLevel | @ | react-dom.development.js:4820
  | batchedUpdates$1 | @ | react-dom.development.js:18918
  | batchedUpdates | @ | react-dom.development.js:2150
  | dispatchEvent | @ | react-dom.development.js:4899
  | interactiveUpdates$1 | @ | react-dom.development.js:18973
  | interactiveUpdates | @ | react-dom.development.js:2169
  | dispatchInteractiveEvent | @ | react-dom.development.js:4876


Remove extra semicolons for pedantic compilers

When compiling with -pedantic, there are warnings about extra semicolons. This commit removes extraneous semicolons, which breaks MXX_INSERT_NAME_INTO_MAP without adding in a semicolon.

Thanks. Looks good.


Experimental option to remove webextension-polyfill

Feature Request
Eventually, once all browsers support the promise-based API like Chrome MV3 or what the polyfill provides, WXT will exclude the polyfill. In preparation for that day, it should provide an experimental config allowing people to disable the polyfill if they don't need it (ie: they're only making a MV3 Chrome extension)
export default defineConfig({
  experimental: {
    webextensionPolyfill: false
  }
})

Is your feature request related to a bug?
Kind of related to #224
What are the alternatives?
Continue not allowing the polyfill to be disabled
Additional context
WXT has internal logic in both production and dev mode that relies on the polyfill. This will be experimental because things may break when you disable the polyfill.

Released in v0.9.2!


Use non beta version of rugged

When adding support for self signed certificates in rugged we had to use a beta version. Now that rugged supports self signed certificates we can switch to the release version.

:tada: cc @simaishi for downstream.


feat: Adding the interface for credential status manager

Adding the ICredentialStatus interface which defines the methods (and respective parameter and results) use to manage credential statuses
Small refactor in the credentialStatus field of VCs in order to reference it in the ICredentialStatus interface
This is the implementation for the proposal describe in https://github.com/uport-project/veramo/issues/937

@italobb I was thinking about some of the data type names we're using here.
We have the CredentialStatus data type defined in vc-data-model.ts and we also use the CredentialStatus type from the credential-status library under the name CredentialStatusVerification. It's a bit confusing, IMO.
While this feature is fresh and there are not many backward compatibility issues, what do you think about renaming some of them for a bit more clarity?
I propose naming them like this:
CredentialStatus -> CredentialStatusCoordinates for the property that gets embedded in the VC
CredentialStatusVerification -> CredentialStatus for the current status of the credential
What do you think?
(It doesn't have to be part of this PR, but I commented here because it's related to the subject)

@mirceanis About the data type names. After fixing the past issues, the dependency with credential-status was removed and we are only referencing the CredentialStatus from vc-data-model.ts. But I agree this confusion can come back in the future and we should open another issue to fix that. I suggest CredentialStatusReference instead of ...Coordinates.


Cannot use v5.4.0 with ts-node on Node v16

Describe the bug
After upgrading to v5.4.0 I can no longer run npx mikro-orm debug (or use it in any other way) if ts-node is involved. It has something to do with how dynamic imports are handled now.
I did make it work tho by running it like this:
node_modules/.bin/ts-node-esm node_modules/@mikro-orm/cli/cli debug

also like this (when running my app, not the mikro-orm's CLI itself):
node --inspect=<IP_ADDRESS>:9229 --loader ts-node/esm bootstrap.ts

Prior to the upgrade, it did work out of the box.
Everything seems to be fine outside the ts-node's context (e.g. when running compiled JS).
CLI
npx mikro-orm debug
Current MikroORM CLI configuration
 - dependencies:
   - mikro-orm 5.4.0
   - node 16.17.0
   - typescript 4.6.4
 - package.json found
 - ts-node enabled
 - searched config paths:
   - /path/to/my/project/config/mikro-orm.config.override.ts (not found)
   - /path/to/my/project/config/mikro-orm.config.ts (found)
   - /path/to/my/project/config/mikro-orm.config.js (not found)
   - /path/to/my/project/mikro-orm.config.ts (not found)
   - /path/to/my/project/mikro-orm.config.js (not found)
- configuration not found (Unknown file extension ".ts" for /path/to/my/project/config/mikro-orm.config.ts)

tsconfig.json
{
    "compilerOptions": {
      "target": "es2021",                       /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017','ES2018' or 'ESNEXT'. */
      "module": "commonjs",                     /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', or 'ESNext'. */
      "lib": ["es2021", "DOM"],                 /* Specify library files to be included in the compilation. */
      "declaration": true,                      /* Generates corresponding '.d.ts' file. */
      "sourceMap": true,                        /* Generates corresponding '.map' file. */
       "outDir": "build",                       /* Redirect output structure to the directory. */
      "strict": true,                           /* Enable all strict type-checking options. */
       "strictPropertyInitialization": false,  /* Enable strict checking of property initialization in classes. */
       "alwaysStrict": true,                  /* Parse in strict mode and emit "use strict" for each source file. */
       "noUnusedLocals": true,                /* Report errors on unused locals. */
       "noUnusedParameters": true,            /* Report errors on unused parameters. */
       "noImplicitReturns": true,             /* Report error when not all code paths in function return a value. */
       "noFallthroughCasesInSwitch": true,    /* Report errors for fallthrough cases in switch statement. */
      "moduleResolution": "node",               /* Specify module resolution strategy: 'node' (Node.js) or 'classic' (TypeScript pre-1.6). */
      "rootDirs": [                             /* List of root folders whose combined content represents the structure of the project at runtime. */
      ],
      "types": [                                /* Type declaration files to be included in compilation. */
          "node",
          "mocha"
      ],
      "esModuleInterop": true,                  /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */
      "experimentalDecorators": true,           /* Enables experimental support for ES7 decorators. */
      "emitDecoratorMetadata": true,            /* Enables experimental support for emitting type metadata for decorators. */
      "resolveJsonModule": true,
      "forceConsistentCasingInFileNames": true
    }
  }

Additional context
I'm not actually using ESM in my app. This app remembers NodeJS v8 :)
Versions

Dependency
Version

node
16.17.0

typescript
4.6.4

mikro-orm
5.4.0

your-driver
MySQL

Not just 16.x. I'm running in to this with node 18.7.0. It happened after I upgraded to 5.4.0 from 5.3.1.

Same here after upgrading from 5.3.1 to 5.4.0....

Same thing here using after upgrading to 5.4.0

v5.3.0 doesn't work either. v5.2.0 does work but it breaks in typescript v4.8.2 when using the PostgreSQL driver: Type 'PostgreSqlDriver' does not satisfy the constraint 'IDatabaseDriver<Connection>'.

@alex996 I think that is a separate issue. This is regarding ts-node improperly rejecting .ts files when parsing the config file from the cli. See @XanderEmu's example output above.

@jblyberg It's unrelated but I mentioned it because staying on v5.2.0 isn't viable either unless you don't upgrade TypeScript.

I was able to work around this issue by setting NODE_OPTIONS="--loader ts-node/esm" and wound up putting it in my script definition until this issue is sorted:
"orm:migrate:create": "NODE_OPTIONS=\"--loader ts-node/esm\" mikro-orm migration:create",
"orm:migrate:up": "NODE_OPTIONS=\"--loader ts-node/esm\" mikro-orm migration:up",

Ouch, I thought this is ESM only issue, totally forgot to test the CLI. WIll fix it in a moment.
Since v5.4 its possible to provide your own dynamic import implementation, so you can also do this explicitly (in CJS projects):
dynamicImportProvider: id => require(id)

(This is exactly how I am going to fix it, enforcing this when initializing the ORM from CLI context.)

I tried with both 5.3.1 and 5.4.0 and I keep getting this when I run the migrations command (yarn mikro-orm migration:create --initial):
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /Users/shah/Documents/repos/UmmahConnect/packages/domain/src/migrations/config/db-config.ts
at new NodeError (node:internal/errors:371:5)
at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:87:11)
at defaultGetFormat (node:internal/modules/esm/get_format:102:38)
at defaultLoad (node:internal/modules/esm/load:21:14)
at ESMLoader.load (node:internal/modules/esm/loader:359:26)
at ESMLoader.moduleProvider (node:internal/modules/esm/loader:280:58)
at new ModuleJob (node:internal/modules/esm/module_job:66:26)
at ESMLoader.#createModuleJob (node:internal/modules/esm/loader:297:17)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:261:34)
at async Promise.all (index 0) {
code: 'ERR_UNKNOWN_FILE_EXTENSION'
}
Using commonjs and also tried using dynamicImportProvider: (id) => require(id),

I tried making the suggested change in the mikro-orm.config.ts file, in the options setting:
const MikroOrmConfig: Options = {
type: 'mysql',
    ...
entities: [`${__dirname}/**/*.entity.js`],
entitiesTs: [`${__dirname}/**/*.entity.ts`],
namingStrategy: EntityCaseNamingStrategy,
loadStrategy: LoadStrategy.JOINED,
highlighter: new SqlHighlighter(),
dynamicImportProvider: id => require(id),

and this did not fix my error attempting to run the migrations from the CLI, using 5.4.0.

Looks like it was just about the debug command.

@B4nan I just pulled the latest dev release and it's still throwing the same Unknown file extension ".ts" error... do we need to modify our ormconfig after using that release?

It works fine for me with dev 13, can you create a repro?
https://stackblitz.com/edit/mikro-orm-repro-wcqjfb?file=package.json

Lemme look into it more. If I can repro it, is a repo ok or do you want a repro on stackblitz or something? I haven't worked too much with them so I'm a bit of a noob over in those environments 😅

Well, I dont mind a repo, but I kinda just proved it works in that stackblitz :] Or is it some specific command? I am trying debug and schema:create -d usually.

And for more context, here's the script I use with local development:
ts-node-dev --exit-child --watch .env.local --ignore-watch ../web/.next --files --rs --respawn src/index.ts
The same issue occurs with ts-node-dev, which I guess shouldn't be surprising 😅

Oh I see, the fix was only about CLI as the OP was about CLI.
We can run the same ts-node detection logic as we have in the init method and do the same automatically to support such use case.
But the workaround mentioned above will help with this too, just add dynamicImportProvider: (id) => require(id), to the ORM config.

Gotcha. Want me to open a new issue for that fix?

Actually we dont need to detect ts-node at all, it makes sense to move the fix so its executed when creating the config object, always based on the type: module in package.json.

let me know if next dev version works without that

@B4nan doesn't look like it did ☹ Repro

Its not published yet https://github.com/mikro-orm/mikro-orm/actions/runs/3017061503

Hahah whoops... I saw you pushed today and just assumed. My bad! I'll check when it's up 😆

@B4nan same result after pulling in dev.16 😔 I tried with and without "type": "module" in the package.json

Lol, right, because I fixed it only for the path where you dont provide the options to init... :D I am glad I gave this a bit more time to settle instead of rushing with hot fix releases :]

Well I appreciate you trying to fix it so quickly!!! So you get kudos in my book haha

This dev-16 build addressed my issue as well, which was with the command line, but thought I would confirm for you.

Looks like I managed to break it in dev.17 again :D Let me try once again.

All good, it was wrong repro with ESM project, where this still requires the some extra configuration (e.g. the ts-node/esm loader).

Hey everyone! I'm quite inexperience in all things Java-/TypeScript, SvelteKit and Mikro-ORM. Currently trying to gain understanding I ran into this very issue (or a very similar one). Same error on Mikro-ORM 5.6.0. Here's a reproduction: https://stackblitz.com/edit/node-cq9rax?file=package.json.
Possibly I'm doing something wrong. Help and/or bugfix would be appreciated.

You should be using npx mikro-orm-esm debug instead in ESM projects, and AFAIK it won't work in stackblitz, but I just tried and it works fine locally.

You should be using npx mikro-orm-esm debug instead in ESM projects, and AFAIK it won't work in stackblitz, but I just tried and it works fine locally.

Thanks for the pointer. I got it working that way.
You're also right about stackblitz: I tried to copy what works on my Linux system there and somehow the Mikro-ORM CLI, even it it is started as mikro-orm-esm will still look for {src/,}mikro-orm.config.js instead of .ts files. It even ignores "mikro-orm"."configPaths" from the package.json. Forcing ts-node with "mikro-orm"."useTsNode" = true also does nothing.

You're also right about stackblitz: I tried to copy what works on my Linux system there and somehow the Mikro-ORM CLI, even it it is started as mikro-orm-esm will still look for {src/,}mikro-orm.config.js instead of .ts files. It even ignores "mikro-orm"."configPaths" from the package.json. Forcing ts-node with "mikro-orm"."useTsNode" = true also does nothing.

That's probably because you did not install ts-node - TS files are ignored without it being installed. But with stackblitz things don't work even if you install it :] The TS file gets imported and fails to recognize the extension as in the OP.

 Thanks again for the help.

You should be using npx mikro-orm-esm debug instead in ESM projects, and AFAIK it won't work in stackblitz, but I just tried and it works fine locally.

This fixed it for me! 🎉

I'm having this issue with next js, does anyone have any ideas how to solve it?


Minor Editor/Config level fixes

Overview
This changes fixes some minor configurations and editor behavior issues.

Fix isCustomProfile to false for DefaultSpatialAwarenessSystemProfile
Fix check for SpatialAwareness layer 31
Fix HelpURL and documentation inspector button for pointers

Changes

Fixes: #5679 , #5680 , #4648

Verification
All tests passed

As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run

/azp run

/azp run


docker/windows/virtualbox/corporate proxy/cannot connect to hub/tri

I am running docker on windows using virtualbox in a corporate machine.
I cannot connect docker hub, not even able to login to hub
tried all the options which are suggested in this forum with no luck.
Need some expert advise please.
$ docker run --env http_proxy=http://proxy.com:8080 hello-world
Unable to find image 'hello-world:latest' locally
Pulling repository docker.io/library/hello-world
Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/hello-world/images. You may want to check your internet connection or if you are behind a proxy.
docker@default:~$ docker login
Username: user
Password:
Email: email
Error response from daemon: Server Error: Post https://index.docker.io/v1/users/: dial tcp <IP_ADDRESS>:443: i/o timeout
docker@default:~$ cat /var/lib/boot2docker/profile
EXTRA_ARGS='
--label provider=virtualbox
'
CACERT=/var/lib/boot2docker/ca.pem
DOCKER_HOST='-H tcp://<IP_ADDRESS>:2376'
DOCKER_STORAGE=aufs
DOCKER_TLS=auto
SERVERKEY=/var/lib/boot2docker/server-key.pem
SERVERCERT=/var/lib/boot2docker/server.pem
HTTP_PROXY=http://proxy.com:8080/
HTTPS_PROXY=http://proxy.com:8080

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Hi Gordon,
i searched everywhere and almost tried all the options with no luck, need some expert level debugging, thanks.
there are no certificates installed on my server, and canot install them using apt-get
docker@default:~$ apt-get
-sh: apt-get: not found
here is the details from the server
docker@default:~$ curl -L -k https://index.docker.io/v1/repositories/library/ubuntu/images
curl: (56) Received HTTP code 400 from proxy after CONNECT
docker@default:~$
docker@default:~$ docker version
Client:
Version:      1.8.2
API version:  1.20
Go version:   go1.4.2
Git commit:   0a8c2e3
Built:        Thu Sep 10 19:10:10 UTC 2015
OS/Arch:      linux/amd64
Server:
Version:      1.8.2
API version:  1.20
Go version:   go1.4.2
Git commit:   0a8c2e3
Built:        Thu Sep 10 19:10:10 UTC 2015
OS/Arch:      linux/amd64
docker@default:~$ docker info
Containers: 11
Images: 3
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 25
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.0.9-boot2docker
Operating System: Boot2Docker 1.8.2 (TCL 6.4); master : aba6192 - Thu Sep 10 20:58:17 UTC 2015
CPUs: 1
Total Memory: 1.956 GiB
Name: default
ID: UAJS:2YZW:Z2VW:232X:UEPS:YBAS:SEBU:4KY5:R4YH:7R5J:FM5B:EVAJ
Debug mode (server): true
File Descriptors: 12
Goroutines: 17
System Time: 2015-09-19T17:53:41.193980115Z
EventsListeners: 0
Init SHA1:
Init Path: /usr/local/bin/docker
Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
provider=virtualbox
docker@default:~$ uname -a
Linux default 4.0.9-boot2docker #1 SMP Thu Sep 10 20:39:20 UTC 2015 x86_64 GNU/Linux
docker@default:~$

hi, Is there a way i can fix this issue?
or alternatively from where can i download the image tar files to load them using "docker load" ?

You should be able to use the http proxy by setting the environment variable on your client.
For instance: HTTP_PROXY=proxy.com:80 docker pull busybox
And then if you need access from inside the container you would set the HTTP_PROXY  on docker run -e HTTP_PROXY=proxy.com:80
For help, please see the docker-user mailing list, #docker on IRC, or forums.docker.com
Thanks!

still cannot connect, raised a request on docker forum.
docker@default:~$ HTTP_PROXY=http://proxy.com:8080/
docker@default:~$ docker pull busybox
Using default tag: latest
Pulling repository docker.io/library/busybox
Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/busybox/images. You may want to check your internet connection or if you are behind a proxy.

I know the pain of corporate proxies.
When using docker-machine to bootstrap your docker/virtualbox, ensure you pass the proxy env variables:
docker-machine create -d virtualbox
--engine-env HTTP_PROXY=http://proxy.company.com:3128
--engine-env HTTPS_PROXY=http://proxy.company.com:3128
default
On a side note, if you have a proxy that requires authentication then you might want to look at using CNTLM on your workstation with proper configuration instead, which should solve 99% of all the issues that softwares have with proxies (especially with credentials). You then just have to use "http_proxy=http://localhost:3128" everywhere.
When using nested virtualized environments with virtualbox, like vagrant and docker-machine (formally boot2docker), then you need to pass the following parameters instead:
docker-machine create -d virtualbox
--engine-env HTTP_PROXY=http://<IP_ADDRESS>:3128
--engine-env HTTPS_PROXY=http://<IP_ADDRESS>:3128
default
Note the use of the VBox gateway <IP_ADDRESS>.

Recreating the machine with the proxy env passed works for me. Thanks @alexandrem

@alexandrem solution worked for me too
thanks!

@alexandrem suggestions works for me also. Before that, i tried going inside the machine and set http_proxy and https_proxy environment variable. It doesnt seemed to work. It seems as suggested by @alexandrem this needs to be done during the creation of the machine.

how do i acheive this on linux--- i have docker on ubuntu (AWS) --- and have a container that cannot talk to internet - since im behind corporate proxy... any insights... im kind of stuck

@softwareklinic This is a thread for windows, I suggest you post your problem on another issue thread. There is also a documentation in the docker site https://docs.docker.com/engine/admin/systemd/ how to achieve this.


staking: validator definitions with conflicting consensus keys

Is your feature request related to a problem? Please describe.
Similar to #3855, Zellic found that it is possible to craft a transaction with two actions that refer to distinct identity keys but conflicting consensus keys. This is a high-priority fix, because CometBFT will halt if presented with duplicate consensus identities.

We already have logic to prevent duplicate consensus keys. Did it not work here?

@hdevalence This is another TOCTOU hazard, where it's possible to have two actions that use different identity keys (= different definitions) but colliding consensus keys.

We check the consensus key isn't a duplicate in the verify_stateful method for the ValidatorDefinition action so this is a little surprising. I'll try to replicate

verify_stateful is precisely where the TOCTOU comes from — its parallelized

see eg the comments in the actionhandler impl in #3883

We will do #3960 instead.


Show all aliases instead of just the first one

Right now we only show one alias after the deployment is done, but we want to show all of them.

Codecov Report

Merging #2188 into canary will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff           @@
##           canary   #2188   +/-   ##
======================================
  Coverage    4.34%   4.34%
======================================
  Files         245     245
  Lines        8839    8839
  Branches      929     929
======================================
  Hits          384     384
  Misses       8438    8438
  Partials       17      17

Impacted Files
Coverage Δ

src/commands/deploy/latest.js
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


GLIBC_2.29' not found (required by ./glaredb)

Description
curl https://glaredb.com/install.sh | sh
ok.
but
Successfully downloaded the GlareDB binary.
You can run it as:
    > ./glaredb
(venv) yu.gavrilov@s7-13-038829:~/Git$ ./glaredb
./glaredb: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./glaredb)
./glaredb: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by ./glaredb)

:(
on custom linux (Astra)
but working well in python
>>> con = glaredb.connect()
>>> df = con.sql("select * from df where fruits = 'banana'").to_polars();
>>> print(df)
shape: (3, 4)
┌─────┬────────┬─────┬────────┐
│ A   ┆ fruits ┆ B   ┆ cars   │
│ --- ┆ ---    ┆ --- ┆ ---    │
│ i64 ┆ str    ┆ i64 ┆ str    │
╞═════╪════════╪═════╪════════╡
│ 1   ┆ banana ┆ 5   ┆ beetle │
│ 2   ┆ banana ┆ 4   ┆ audi   │
│ 5   ┆ banana ┆ 1   ┆ beetle │
└─────┴────────┴─────┴────────┘

We don't have Astra testing (or build), so I'm not totally sure how/if we can confirm this, but it seems plausible.
We compile the downloaded release with Ubuntu 2004 (released in April of 2020), which means linux distros with older libc versions might work, but aren't guaranteed.
If you have an older version of linux with a rust toolchain installed  running just dist  (if you have just, or cargo build --bin glaredb should produce a binary (look in target/) that will work on your system.


Windows Live Provider displayed link updated to match backend url

In the Nhost dashboard for signed in client, the callback url for windows live/microsoft option is shown incorrectly. Should show "/windowslive/callback" versus "/microsoft/callback"

Ok Changed line 118 as well. Overlooked it.
Cheers

Codecov Report

Merging #1365 (4a9471c) into main (aea99ad) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1365   +/-   ##
=======================================
  Coverage   94.74%   94.74%
=======================================
  Files          48       48
  Lines        6931     6931
  Branches      450      450
=======================================
  Hits         6567     6567
  Misses        364      364

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[CI] Enable the CI for this project

What

[x] Create JJBB.
[x] Create infra JJBB triggers.
[x] Create webhooks.
[x] Create MBP.
[x] Create Makefile, bump version and BATS validations.
[x] Update Docs.
[x] Update php agent release process pipeline to bump the agent version.
[x] Update opbeans-frontend to build this project if it gets updated.
[x] Create DockerHub project -> https://hub.docker.com/repository/docker/opbeans/opbeans-php

https://github.com/elastic/opbeans-php/pull/10


Chrome extension stopped working

Please update the chrome webstore extension. It no longer redirects as it is supposed to. Just plays the shorts UI. Tried disabling and reenabling, and reloading the page. Same behavior. Also chromium browsers no longer let us install third party extensions, so installing from github is impossible (not talking about firefox, just Chrome or Brave or other chromium browsers).

We could not confirm the issue of no redirection in Youtube-shorts block v1.3.3(latest), Chrome108.
However, under certain circumstances, this problem can occur.
If you could tell us the following, we might be able to solve the problem. (as much as you can answer)

The region (country) you are accessing
The URL before the redirect (like https://www.youtube.com/shorts/"videoID")
Are there any errors from this extension in the console(DevTools) (please give me a screenshot)
Are extensions enabled

The extension started working perfectly fine today. Apologies.


Fixed issue #10072 by removing extra comma in zh-tw localization file

For #10072

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #10073 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #10073      +/-   ##
==========================================
- Coverage   61.37%   61.36%   -0.02%
==========================================
  Files         565      565
  Lines       30559    30559
  Branches     4385     4385
==========================================
- Hits        18757    18753       -4
- Misses      10823    10826       +3
- Partials      979      980       +1

Impacted Files
Coverage Δ

src/client/common/utils/platform.ts
70.58% <0%> (-5.89%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0%> (-0.73%)
:arrow_down:

Continue to review full report at Codecov.

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

@ChenKB91 Thank you for fixing this. Please add the news item so you get credit for this fix.

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

@ChenKB91 I added a news item to save time. Please sign the CLA so we can take the fix.

@ChenKB91 I have credited you for the fix in the release. I could not merge this PR due to CLA. Please sign it so we can take any future contributions you make. Thank you, for providing a fix.

This is my first time doing a pull request so I have little idea what to do.... Thank you!


lib: only run _initialize if it exists

This is the first small step towards getting this module working on the T2.
I haven't had time to test it on my boards yet.

I can confirm that this fixes the error that gets thrown. The module doesn't successfully read cards yet... but we'll get there :)


discover if-statement implementation

I hope i can reuse most of existing code

completed, wasn't that hard :)


Issue adding extras

After installing scoop on Windows 7 and successfully installing several apps, running scoop bucket add extras returns the following error:
'https://github.com/lukesampson/scoop-extras.git' doesn't look like a valid git repository
Any ideas?

Is it possible you had an intermittent connection when you last tried? I was able to run the exact command here (on Windows 10) without issue.

Strange. I need to connect through a proxy server so it could be something to do with that. I've configured the proxy in scoop, but might need a bit more digging around.

Do any of the buckets work? Try scoop bucket add versions

You may need to configure git to use the proxy as well. It doesn't currently pass that information along


Update site.config.js

Description

Related tickets
https://github.com/morethanmin/morethan-log/issues/XX

PR Checklist

[ ] I have read the Contributing Guide
[ ] I have written documents and tests, if needed.

asdf

asdf


SWITCH..CASE : issue with DEFAULT

This appears to take issue with CASE DEFAULT
switch t$
    case t$=""
        break
    case "TEST"
        break
    case default
        print "default"
        break
swend

See https://documentation.basis.cloud/BASISHelp/WebHelp/commands/switch_case_swend_verbs.htm
Appending some continuation with ; to the CASE DEFAULT appears to work -> regression?
switch t$
    case t$=""
        break
    case "TEST"
        break
    case default; print "default"
        break
swend

Hi @StephanWald ! The documentation does not specify the default case without semicolon.
If this can happen, we should adapt the grammar. Currently we are expecting this semicolon followed by some optional statements.
Do you have evidence from the real world, that this syntax is allowed?
If yes, this should also be part of the documentation, because the current one can lead to the assumption that case default is always followed by a semicolon.

@Lotes In BBj  almost anything can be continued with a semicolon, until you reach the end of the line or until you hit a REM. After a REM, the rest of the line is considered a comment (you cannot end a REM, neither with ; nor with anything else).
So even this is valid, everything in one single line. Not that it's a good idea for readability,  but I've seen people doing it:
input i
SWITCH i; CASE 1; PRINT "1"; BREAK; CASE 2; PRINT "2"; BREAK; CASE DEFAULT; PRINT "default"; SWEND

@msujew I also tested the following line, which makes the parser use a lot of CPU for a big amount of time (even LSP services get delayed). Can we have a look together? I am also not entirely sure how to arrange the grammar to make this line work (especially with this compound syntax).
SWITCH t$;CASE 1; PRINT "1"; BREAK; CASE 2; PRINT "2"; BREAK; CASE DEFAULT; PRINT "default"; SWEND

SWITCH t$;CASE 1;

Nitpicking detail: you use a String t$ in the SWITCH then compare numbers in the CASE - this does not play with each other and would fail at runtime.

Should be fixed now


Windows vulkaninfo double-reporting discrete GPU over RDP

When running vulkaninfo on a machine's console, the expected GPUs appear.  When running on a remote RDP console, it looks like the discrete GPU (but not the integrated GPU) is being doubled.  The execution below was made using RDP on a device with a single Radeon R9 380:
> vulkaninfo --summary
...
Devices:
========
GPU0:
        apiVersion         = 1.2.203
        driverVersion      = 101.1340
        vendorID           = 0x8086
        deviceID           = 0x1912
        deviceType         = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
        deviceName         = Intel(R) HD Graphics 530
        driverID           = DRIVER_ID_INTEL_PROPRIETARY_WINDOWS
        driverName         = Intel Corporation
        driverInfo         = Intel driver
        conformanceVersion = <IP_ADDRESS>
        deviceUUID         = 86801219-0600-0000-0000-000000000000
        driverUUID         = 33302e30-2e31-3031-2e31-333430000000
GPU1:
        apiVersion         = 1.2.133
        driverVersion      = 2.0.137
        vendorID           = 0x1002
        deviceID           = 0x6939
        deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName         = AMD Radeon (TM) R9 380 Series
        driverID           = DRIVER_ID_AMD_PROPRIETARY
        driverName         = AMD proprietary driver
        driverInfo         = <IP_ADDRESS>
        conformanceVersion = <IP_ADDRESS>
        deviceUUID         = 01000000-0000-0000-0000-000000000000
        driverUUID         = 414d442d-5749-4e2d-4452-560000000000
GPU2:
        apiVersion         = 1.2.133
        driverVersion      = 2.0.137
        vendorID           = 0x1002
        deviceID           = 0x6939
        deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName         = AMD Radeon (TM) R9 380 Series
        driverID           = DRIVER_ID_AMD_PROPRIETARY
        driverName         = AMD proprietary driver
        driverInfo         = <IP_ADDRESS>
        conformanceVersion = <IP_ADDRESS>
        deviceUUID         = 01000000-0000-0000-0000-000000000000
        driverUUID         = 414d442d-5749-4e2d-4452-560000000000

After updating the drivers on the system to 1.3.243, the issue disappears. Thus, I am presuming this is a driver issue that was fixed. Closing.


Publish svcat binaries during build

make svcat-all builds all supported client platforms (darwin, linux, windows).
make svcat-for-X builds a specific platform.
make svcat builds for the current dev's platform.
make svcat-publish compiles everything and uploads the binaries.
Versions for svcat are tracked using svcat-vX.Y.Z tags.
Versions for service catalog continue to use vX.Y.Z.
I've fixed the VERSION variable to contain the tag value to account for not using annotated tags.
Download from https://download.svcat.sh/cli/latest/GOOS/amd64/svcat (hosted by my team). If you want a specific version it's at https://download.svcat.sh/cli/vX.Y.Z/GOOS/amd64/svcat.

Since there are no existing versions for svcat yet I have a small hack to print v0 so that the first PR can build. We can remove that once we have svcat tags in the repo.
TODO:

[x] I'm waiting on an SSL cert for that domain but should have that fixed by tomorrow. 😊
[ ] A secret environment variable needs to be set. Not sure if y'all prefer putting that encrypted value in the travis file or if you set it in the website.

RE the secret, we generally put them into travis as env vars

@arschles Rebased and ready for review.

Does this also result in PR/master merge binaries as their git sha?
I think I understand this, but getting a list of the possible outputs would be nice, I think it corresponds to the same thing as svc-cat bins.

a v###-git-sha-ish from master merges, (which is also available as latest?)
a v### from the actual tags

I tweaked how we set VERSION so that it includes the tag along with the hash. Currently we are using --always which doesn't actually include the tag just the commit hash because our tags are lightweight and not annotated*. With my change to use --tags, the tag is combined with the sha to uniquely identify the commit.
This was necessary so that svcat version prints the release (along with a hash if it wasn't built off of a tagged commit).
* UPDATE: I am confused. 😀 Looking at quay we do have images tagged this way but when I run git describe --always I never get the tag name, just the hash. So I'm not sure what why I see on thing and yet the builds are obviously working just fine today.
tagged commit
$ git checkout v0.0.1
$ git describe --always --abbrev=7 --dirty --match=v*
2f0aebc
$ git describe --tags --abbrev=7 --dirty --match=v*
v0.0.1

untagged commit
$ git checkout 0c785db
$ git describe --tags --abbrev=7 --dirty --match=v*
v0.1.7-10-g0c785db
$ git describe --always --abbrev=7 --dirty --match=v*
0c785db

Deploy Logic

Merge to master - nothing is pushed for svcat, the same logic for pushing to docker is execute today but the image tag will include the new format, i.e. v0.1.7-10-g0c785db.
Tag a commit on master with vX.Y.Z - The same logic for pushing to docker is executed, but the image tag will only be the release, and not include the sha, i.e. v0.1.7.
Tag a commit on master with svcat-vX.Y.Z - publish the binaries to latest and vX.Y.Z.

The idea behind latest is that we can provide a permanent link to the most recent stable release of svcat. If someone wants to install a unreleased version, I would recommend building locally.

@carolynvs So, the intent is then that we will have our "core" releases just push service-catalog images, and different "svcat" releases that push the svcat binaries? If so, that seems fine, though I'm curious what other repos do in this situation.
For kubernetes/kubernetes vs kubectl, are the versions kept in strict alignment and released simultaneously for every patch?

For kubernetes/kubernetes vs kubectl, it looks like the versions are kept in strict alignment and released simultaneously for every patch; is that correct?

Yes, that's what it looks like. I originally did it this way because I wasn't confident that y'all would be okay with bumping the server version when perhaps all of the changes were in the client. If you are okay with that, then I would prefer to version them together. That way it would be easy to know that one has the proper client version to go with their server.
If you agree, I'll redo this to use the same version for both (along with tweaking the tag changes so that pushes to master result in images without any version information included to preserve existing behavior).

I just added a related issue, #1752, to have svcat version print the version of both the client and the server.

If you agree, I'll redo this to use the same version for both (along with tweaking the tag changes so that pushes to master result in images without any version information included to preserve existing behavior).

I think I like using the same version better, though it would make things like trying to add breaking changes to the CLI more difficult. But we're probably in a stable enough state at the moment that that hopefully won't be too much of an issue.

I'll update the PR today to make that change then and resist the temptation to constantly make breaking changes to svcat. 😉

I have updated the PR to:

Use the same tag for both server and client (svcat) versions. The cli uses a format that always includes a tag, so that it's clear which release you are "closest" to, e.g. v1.2.3 for official releases and v1.2.3-2-gabc123 for untagged commits.
The versioning and image tagging for the server docker image remains unchanged.
Include some of my explanations from this PR about the new make targets, and what's published during a release in the devguide.

LGTM, just one final .travis.yml rebase and I'm happy to merge!

I've rebased. The travis build needs to be retried however; it hit a transient network error.
# Verify that vendor/ is in sync with Gopkg.lock
docker run --security-opt label:disable --rm -v /home/travis/build/kubernetes-incubator/service-catalog:/go/src/github.com/kubernetes-incubator/service-catalog -v /home/travis/build/kubernetes-incubator/service-catalog/.pkg:/go/pkg --env AZURE_STORAGE_CONNECTION_STRING scbuildimage build/verify-vendor.sh
grouped write of manifest, lock and vendor: error while writing out vendor tree: failed to write dep tree: failed to export golang.org/x/crypto: https://go.googlesource.com/crypto does not exist in the local cache and fetching failed: unable to get repository: Cloning into '/go/pkg/dep/sources/https---go.googlesource.com-crypto'...
POST git-upload-pack (141 bytes)
fatal: git fetch-pack: expected ACK/NAK, got 'error: Access denied to IP <IP_ADDRESS>'
fatal: The remote end hung up unexpectedly
: command failed: [git clone --recursive -v --progress https://go.googlesource.com/crypto /go/pkg/dep/sources/https---go.googlesource.com-crypto]: exit status 128
make: *** [verify-vendor] Error 1

🎉 IT'S ALIVE!

bumped travis. green nbuiuld.


Change the tab-nav rendering to be v-show based

Bug/issue #, if applicable: 108379797
Summary
Changes the TabNav content rendering to be v-show based, so images can be pre-loaded and wont flash when changing tabs.
Dependencies
NA
Testing

Load an archive with a tabnav that has mostly images
Assert images no longer flash when changing active tab

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran npm test, and it succeeded
[x] Updated documentation if necessary

Not opposed to switching to a v-show based approach as long as we've done some performance testing of realistic scenarios to make sure that there's no major regression with loading everything up-front.

Played a bit with tabnavs with lots of images found a few things. Behaviour is consistent across browsers, which is great.
We explicitly set that images under the tabnav component should be eager loaded, so it downloads all images, rendered or not. This can deff cause slowdown on slower/limited networks.
Before this PR, it was not an issue, because the images are not rendered at all, compared to being hidden now.
If we however change the imageLoadingStrategy that back to lazy, browsers only load the images you can see. As you change the active tab, it starts downloading the ones on the new active tab.

@swift-ci test

@swift-ci test

@swift-ci test


503 Intermitent error(no healthy upstream)

Hi Team,
We need an urgent help. We are getting 503 no healthy upstream error intermittently from istio gateway. Seeing your release note which has the same bug stated fixed in envoy version which comes with istio version 1.21 , we upgraded the istio to latest version but the error is still here. Our whole infrastructure is impacted by it. Help will be greatly appreciated.
[09:36] Kanithi, Santosh Kumar
client version: 1.21.0
control plane version: 1.21.0
data plane version: 1.21.0 (299 proxies)
[09:41] Gupta, Ritesh

Maybe you should give some details here.

Hi , as stated we getting no healthy upstreams. after getting details log it is showing below in istio-proxy log

What protocol your app used? Have you tried access your app container use same protocol? Access test should be continuous.

It seems it does . but we see below error though the istio release notes says the issue has already been fixed. So just wanted to ask is there a way to override connections setting to pervent it to break


style(ngAnimate): add missing semi-colon

Adding missing semi-colon which is breaking minification
Closes #12513

landed as 4c92a3ccc7dacfd4bf8144b96c4cbb0c1a324b16


As I said earlier Google banned the invokeai officially

sorry , it was my mistake in my drive there was comfy ui folder i think it was the reason behind this


Export MeshLibrary - Apply MeshInstance Transform does not work for GLTF-based Node3D

Tested versions

Reproducible in 4.3.stable, 4.2.2

System information
Godot v4.3.stable - macOS 14.6.1 - Vulkan (Forward+) - integrated Apple M3 Max - Apple M3 Max (16 Threads)
Issue description
When using Scene -> Export As -> MeshLibrary with Apply MeshInstance Transforms enabled, the transform to Node3Ds that are imported from a GLTF are not added to the MeshLibrary.
Due to the explicit phrasing of "MeshInstance Transforms" I believe this is expected behaviour, but it's unexpected behavior from a user perspective.  Tilesets frequently come in GLTF format, and it is very confusing to enable "Apply [...] Transform", but not have it applied to the exported meshes.
I can understand if this is an immediate close bug, but I was unable to find any documentation of this limitation.  Developers should be aware that if they PoC with MeshInstances, switching to GLTF assets later will not work if any transform is needed.
The only workaround I've found is to manually update the MeshLibrary in the editor for the transform.
Steps to reproduce

Add GLTF imported scene to a new scene and translate it.
Export with "Apply MeshInstance Transforms"
Edit the MeshLibrary and examine the offset fields for the Mesh Transform

Demo:
(Added grass tile from kaykit midevil hexagon pack, and translated it up 1.0)

(Export with "Apply MeshInstance Transforms" enabled)

(Editing the Mesh in the MeshLibrary, the Mesh Transform has a y offset = 0; it should be 1.0)

Minimal reproduction project (MRP)
mesh-library-export-apply-transform.zip

What's interesting here is that in MeshLibraryEditor::_import_scene_parse_node() if you cast p_node to Node3D, get_transform() returns the correct transform.  But in the code the node is first cast to MeshInstance3D, and get_transform() returns the wrong value for the transform (the default, no transform).
Is this just because Node3D and MeshInstance3D are storing their transform in different places?
https://github.com/godotengine/godot/blob/61598c5c88d95b96811d386cb20d714c35f4c6d7/editor/plugins/mesh_library_editor_plugin.cpp#L159-L162
frame #0: 0x0000000101ccc740 godot.macos.editor.arm64`MeshLibraryEditor::_import_scene_parse_node(p_library=Ref<MeshLibrary> @ 0x000000016fdfbbc0, p_mesh_instances=0x000000016fdfbd50, p_node=<unavailable>, p_merge=<unavailable>, p_apply_xforms=true) at mesh_library_editor_plugin.cpp:161:45 [opt]
   158
   159 		Transform3D item_mesh_transform;
   160 		if (p_apply_xforms) {
-> 161 			item_mesh_transform = mesh_instance_node->get_transform();
   162 		}
   163 		p_library->set_item_mesh_transform(item_id, item_mesh_transform);
   164
   (lldb) p ((Node3D*)p_node)->get_transform()
(Transform3D) {
  basis = {
    rows = {
      [0] = {
         = {
           = (x = 1, y = 0, z = 0)
          coord = ([0] = 1, [1] = 0, [2] = 0)
        }
      }
      [1] = {
         = {
           = (x = 0, y = 1, z = 0)
          coord = ([0] = 0, [1] = 1, [2] = 0)
        }
      }
      [2] = {
         = {
           = (x = 0, y = 0, z = 1)
          coord = ([0] = 0, [1] = 0, [2] = 1)
        }
      }
    }
  }
  origin = {
     = {
       = (x = 0, y = 1, z = 0)
      coord = ([0] = 0, [1] = 1, [2] = 0) // <--- Correct origin: (0, 1, 0)
    }
  }
}
(lldb) n
Process 88630 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = step over
    frame #0: 0x0000000101ccc760 godot.macos.editor.arm64`MeshLibraryEditor::_import_scene_parse_node(p_library=Ref<MeshLibrary> @ 0x000000016fdfbbc0, p_mesh_instances=0x000000016fdfbd50, p_node=<unavailable>, p_merge=<unavailable>, p_apply_xforms=true) at mesh_library_editor_plugin.cpp:163:2 [opt]
   160 		if (p_apply_xforms) {
   161 			item_mesh_transform = mesh_instance_node->get_transform();
   162 		}
-> 163 		p_library->set_item_mesh_transform(item_id, item_mesh_transform);
   164
   165 		Vector<MeshLibrary::ShapeData> collisions;
   166 		for (int i = 0; i < mesh_instance_node->get_child_count(); i++) {
Target 0: (godot.macos.editor.arm64) stopped.
(lldb) frame v item_mesh_transform
(Transform3D) item_mesh_transform = {
  basis = {
    rows = {
      [0] = {
         = {
           = (x = 1, y = 0, z = 0)
          coord = ([0] = 1, [1] = 0, [2] = 0)
        }
      }
      [1] = {
         = {
           = (x = 0, y = 1, z = 0)
          coord = ([0] = 0, [1] = 1, [2] = 0)
        }
      }
      [2] = {
         = {
           = (x = 0, y = 0, z = 1)
          coord = ([0] = 0, [1] = 0, [2] = 1)
        }
      }
    }
  }
  origin = {
     = {
       = (x = 0, y = 0, z = 0)
      coord = ([0] = 0, [1] = 0, [2] = 0) // <--- Wrong origin (0, 0, 0)
    }
  }
}

- Node3D with transform
  |- MeshInstance3D without transform

@dmlary Would it make more sense to apply a global transform? I can see other issues arising from that, but it would fix this use case. I also agree that this isn't really a bug, just counter-intuitive when using inherited scenes from a GLTF.

@dmlary
Well it is pretty easy to fix and change it, I have a branch with some changes that make a global transform possible. I won't open a PR for it because its not a bug and it would need an improvement proposal.

https://github.com/BlackShift/godot/commit/17339ff23cd549116ea9bf1f1b81acd187cace02
I don't think this would be the right way to implement it. I also don't like the UI for it, but it seems to work.

I agree, it's not the most pleasant UI.  If godot feels comfortable saying that the transition from local to global transforms is unlikely to break anyone; I'd say do it without the independent option.  My feeling as I thought through the workflow where that transition would cause a problem is that it is unlikely to impact anyone.  Most examples of a tileset scene have all the meshes overlapping at the origin.  The user would have to have created intermediate nodes for each mesh, then translate that intermediate.
Regardless, I opened the proposal https://github.com/godotengine/godot-proposals/issues/10622


isorted all py files in training-operator/sdk/python/kubeflow/trainin…

…g/api

What this PR does / why we need it: sorted py files in training-operator/sdk/python/kubeflow/training/api
Which issue(s) this PR fixes (optional, in Fixes #<issue number>, #<issue number>, ... format, will close the issue(s) when PR gets merged):
Fixes #
Checklist:

[ ] Docs included if any changes are user facing

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.008%) to 35.423%

Files with Coverage Reduction
New Missed Lines
%

pkg/controller.v1/mpi/mpijob.go
1
91.06%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
4379

Relevant Lines:
12362

💛  - Coveralls

Thank you for your contribution, and sorry for the late review @miaozeyu!
Please can you format your Python code with black ?

Also, please modify your PR title something like this:
[SDK] Filter imports using `isort` for Training Client


.hdr format passthrough

This is an excellent tool! It fails to export with .glb files that have .HDR in them. Basisu doesn't currently support .HDR formats, but it would be extremely helpful if this tool could safely pass them through while still working on compatible file types.

This is an excellent tool! It fails to export with .glb files that have .HDR in them. Basisu doesn't currently support .HDR formats, but it would be extremely helpful if this tool could safely pass them through while still working on compatible file types.

This is something we will work on, Conor!

This feature has been added! HDR is now supported as passthrough when using the MOZ_texture_rgbe extension.
https://github.com/paradowskicreative/ZenCompress/releases/tag/1.4.3


Fastboot work tooooo slooow

Fastboot work too slowly (The command takes 5 minutes to execute.)

I’m sorry to hear that. I’ve heard other reports that the initial USB device access is too slow. Unfortunately this boils down to how Termux:API works. Could be their bug or a problem with the particular Android device.

I’m sorry to hear that. I’ve heard other reports that the initial USB device access is too slow. Unfortunately this boils down to how Termux:API works. Could be their bug or a problem with the particular Android device.
With the devices I was able to test, it was always in the order of seconds. There’s also a current limitation which makes fastboot perceivably slower than adb due to the fact that fastboot doesn’t maintain connection to the device in background. So the connection “initialisation” has to be done on every run.

Im always allow my phone to termux api, im so idk how to fix i need to flash fastboot rom but bugjaeger app cant work with .bat or .sh scripts

I have the same thing, fastboot just indefinitely thinks even if command is nothing to think about, just devices without devices connected.
Is there any logs I can send?

Termux:API is likely.
I rechecked. It doesn't delay without anything in USB, it hangs if there's a device in USB iven if it's not in fastboot and even if I unplug it and cancel/run again the command it looks like it still hangs from the last command, after it finally proceeds it works as it should without anything plugged, giving no output in no time. So yes, its probably Termux:API that hangs in the background doing some kind of nothing, not allowing commands to work properly. For fastboot it happens after every fastboot command and for adb it seems like it hangs only some time after device was plugged in and works fine(?) after that.

I think this might be relevant https://github.com/termux/termux-api/issues/466

https://github.com/termux/termux-api/issues/714
termux-location and termux-toast have the same exact issue.

@Prythomn Can you check if you have a delay with the other termux commands @Damglador mentioned above?

@Damglador Thanks for investigating btw!

Fastboot work too slowly (The command takes 5 minutes to execute.)

@Prythomn
have you tried with termux-monet ?
termux-monet
termux-monet-api

have you tried with termux-monet ?
termux-monet
termux-monet-api

Damn, it looks awesome, even has Ukrainian localization. Sad that it didn't get attention it deserves and was discussed 21 days ago (idk if these things related). And yes, seems like it doesn't have this issue. There is delays on some commands, but they are reasonable (~1 second).

Fastboot work too slowly (The command takes 5 minutes to execute.)

@Prythomn
have you tried with termux-monet ?
termux-monet
termux-monet-api

I can try later, thanks!

@Prythomn Can you check if you have a delay with the other termux commands @Damglador mentioned above?

I don't have another device right now

Im tried termux monet on phone without fastboot support, and it work fine, before my phone cant see any device when i granted permission for termux-api,so i will try fastboot commands later.

Fastboot commands work fine

@Damglador  @Prythomn
tks 🙏 for checking and confirming. while waiting for the termux team to fix the issue, so it is recommended that users currently use termux-mount .


Expand on repr/repr html

#395 included a new representation for the sp object, both in string form and html.
There are some additions in #305 that adds information like electron count, acquisition time etc.

Standard cache directory can be used to store this information after calling relevant method once.