Why cann't successfully install in my win10 computer?

My Environment is Windows 10 chinese, but after i install the nvm for windows, i cann't find nodejs directory in "C:\Program Files", then after i install node version 5.9.1, i cann't run node in cmd, i show me a message which is "access is denied". so what should i do? could you tell me?

You probably need to run the command with admin privileges. Right click on the command prompt and select "Run As Administrator". After that, you will need to type nvm use 5.9.1. It should work after that.

Also can't i finish the installation of<EMAIL_ADDRESS>Env: win10 x64
I have tried to install this with command: npm install sqlite3 --build-from-source=sqlite3
Here is the error log:
E:\git\OJDisplay>npm install sqlite3 --build-from-source=sqlite3

><EMAIL_ADDRESS>install E:\git\OJDisplay\node_modules\sqlite3
> node-pre-gyp install --fallback-to-build

E:\git\OJDisplay\node_modules\sqlite3>if not defined npm_config_node_gyp (node "C:\nvm\v5.9.1\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" clean )  else (node "" clean )

E:\git\OJDisplay\node_modules\sqlite3>if not defined npm_config_node_gyp (node "C:\nvm\v5.9.1\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" configure --fallback-to-build --module=E:\git\OJDisplay\node_modules\sqlite3\lib\binding\node-v47-win32-x64\node_sqlite3.node --module_name=node_sqlite3 --module_path=E:\git\OJDisplay\node_modules\sqlite3\lib\binding\node-v47-win32-x64 )  else (node "" configure --fallback-to-build --module=E:\git\OJDisplay\node_modules\sqlite3\lib\binding\node-v47-win32-x64\node_sqlite3.node --module_name=node_sqlite3 --module_path=E:\git\OJDisplay\node_modules\sqlite3\lib\binding\node-v47-win32-x64 )
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: unable to verify the first certificate
gyp ERR! stack     at Error (native)
gyp ERR! stack     at TLSSocket.<anonymous> (_tls_wrap.js:1065:38)
gyp ERR! stack     at emitNone (events.js:80:13)
gyp ERR! stack     at TLSSocket.emit (events.js:179:7)
gyp ERR! stack     at TLSSocket._init.ssl.onclienthello.ssl.oncertcb.TLSSocket._finishInit (_tls_wrap.js:593:8)
gyp ERR! stack     at TLSWrap.ssl.onclienthello.ssl.oncertcb.ssl.onnewsession.ssl.onhandshakedone (_tls_wrap.js:425:38)
gyp ERR! System Windows_NT 10.0.14291
gyp ERR! command "C:\\nodejs\\node.exe" "C:\\nvm\\v5.9.1\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "configure" "--fallback-to-build" "--module=E:\\git\\OJDisplay\\node_modules\\sqlite3\\lib\\binding\\node-v47-win32-x64\\node_sqlite3.node" "--module_name=node_sqlite3" "--module_path=E:\\git\\OJDisplay\\node_modules\\sqlite3\\lib\\binding\\node-v47-win32-x64"
gyp ERR! cwd E:\git\OJDisplay\node_modules\sqlite3
gyp ERR! node -v v5.9.1
gyp ERR! node-gyp -v v3.2.1
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'node-gyp.cmd configure --fallback-to-build --module=E:\git\OJDisplay\node_modules\sqlite3\lib\binding\node-v47-win32-x64\node_sqlite3.node --module_name=node_sqlite3 --module_path=E:\git\OJDisplay\node_modules\sqlite3\lib\binding\node-v47-win32-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (E:\git\OJDisplay\node_modules\sqlite3\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:100:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:185:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:850:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
node-pre-gyp ERR! System Windows_NT 10.0.14291
node-pre-gyp ERR! command "C:\\nodejs\\node.exe" "E:\\git\\OJDisplay\\node_modules\\sqlite3\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd E:\git\OJDisplay\node_modules\sqlite3
node-pre-gyp ERR! node -v v5.9.1
node-pre-gyp ERR! node-pre-gyp -v v0.6.24
node-pre-gyp ERR! not ok
Failed to execute 'node-gyp.cmd configure --fallback-to-build --module=E:\git\OJDisplay\node_modules\sqlite3\lib\binding\node-v47-win32-x64\node_sqlite3.node --module_name=node_sqlite3 --module_path=E:\git\OJDisplay\node_modules\sqlite3\lib\binding\node-v47-win32-x64' (1)
<EMAIL_ADDRESS>E:\git\OJDisplay
`--<EMAIL_ADDRESS>extraneous

npm WARN In<EMAIL_ADDRESS>replacing bundled version of minimist with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of abbrev with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of ansi with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of delegates with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of core-util-is with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of inherits with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of isarray with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of process-nextick-args with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of string_decoder with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of util-deprecate with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of has-unicode with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of lodash.repeat with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of lodash.tostring with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of lodash.repeat with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of lodash.tostring with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of lodash.repeat with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of lodash.tostring with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of deep-extend with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of ini with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of minimist with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of strip-json-comments with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of aws-sign2 with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of pseudomap with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of yallist with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of core-util-is with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of inherits with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of isarray with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of process-nextick-args with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of string_decoder with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of util-deprecate with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of caseless with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of delayed-stream with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of extend with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of forever-agent with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of async with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of color-convert with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of escape-string-regexp with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of ansi-regex with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of ansi-regex with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of supports-color with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of graceful-readlink with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of generate-function with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of is-property with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of jsonpointer with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of xtend with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of pinkie with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of boom with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of cryptiles with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of hoek with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of sntp with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of assert-plus with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of extsprintf with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of json-schema with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of verror with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of asn1 with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of assert-plus with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of ecc-jsbn with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of jodid25519 with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of jsbn with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of tweetnacl with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of is-typedarray with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of isstream with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of json-stringify-safe with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of mime-db with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of node-uuid with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of oauth-sign with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of qs with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of stringstream with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of tough-cookie with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of tunnel-agent with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of wrappy with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of inherits with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of balanced-match with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of concat-map with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of wrappy with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of path-is-absolute with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of semver with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of block-stream with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of graceful-fs with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of inherits with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of ms with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of graceful-fs with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of inherits with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of inherits with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of balanced-match with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of concat-map with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of wrappy with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of core-util-is with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of inherits with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of isarray with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of process-nextick-args with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of string_decoder with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of util-deprecate with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of uid-number with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of nopt with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of lodash.pad with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of lodash.padend with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of lodash.padstart with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of strip-ansi with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of has-ansi with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of generate-object-property with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of commander with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of pinkie-promise with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of ansi-styles with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of mime-types with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of dashdash with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of fstream with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of debug with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of fstream with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of mkdirp with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of readable-stream with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of rc with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of lru-cache with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of combined-stream with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of form-data with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of readable-stream with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of inflight with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of brace-expansion with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of once with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of once with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of readable-stream with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of brace-expansion with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of jsprim with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of hawk with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of gauge with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of chalk with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of is-my-json-valid with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of minimatch with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of sshpk with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of tar with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of minimatch with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of aws4 with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of are-we-there-yet with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of bl with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of glob with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of fstream-ignore with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of har-validator with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of http-signature with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of rimraf with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of npmlog with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of tar-pack with<EMAIL_ADDRESS>npm WARN In<EMAIL_ADDRESS>replacing bundled version of request with<EMAIL_ADDRESS>npm ERR! Windows_NT 10.0.14291
npm ERR! argv "C:\\nodejs\\node.exe" "C:\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "sqlite3" "--build-from-source=sqlite3"
npm ERR! node v5.9.1
npm ERR! npm  v3.7.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sqlite3 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs sqlite3
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls sqlite3
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     E:\git\OJDisplay\npm-debug.log

@Chen188 - Your sqlite issue is caused by node-gyp, not NVM for Windows. I suggest you post this problem in their issues.

@coreybutler OK, thanks for your reply.


Update region column in column in queries.

Describe the bug
A clear and concise description of what the bug is.
Steampipe version (steampipe -v)
Example: v0.3.0
Plugin version (steampipe plugin list)
Example: v0.5.0
To reproduce
Steps to reproduce the behavior (please include relevant code and/or commands).
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

Closing the issue since the fix was made in https://github.com/turbot/steampipe-mod-alicloud-compliance/pull/29


Update fields returned and city name

MaxMind adjusted some of their data, so now the test IP that resolved to Watertown, MA, US, now resolves to Salem, MA, US.
Additionally, the list of fields returned has changed in another test case, so list all the fields that are now returned.
Thanks for contributing to Logstash! If you haven't already signed our CLA, here's a handy link: https://www.elastic.co/contributor-agreement/

Note: will require #142 to be merged first so that SHA1s match and the build progresses to the point this PR addresses.

@danhermann all set for a second look

Looks good for squash+merge. Thanks, @kcm!


Rename bigquerystorage_stub to storage_stub.

The bigquery::internal namespace already gives context around the   ##storage_stub.

This change is

Fixes #24


CheckSecurityConfigs: Check integrity of the implementations

In https://github.com/ethereum-optimism/superchain-registry/pull/31, we automated the checking of OP Chain access control integrity. To further improve the checks, we should also check the integrity of the implementations, i.e. whether the OP Chains are using governance approved protocol implementations and whether they are using a non-deprecated version.

This can probably be done by validation of the implementation version().

This will be covered by https://github.com/ethereum-optimism/superchain-registry/issues/289


Execution Already Exists Issue

I am getting this error in the cloud watch when I try to run a self hosted runner one after the other and it is not able retrieve installation Id from the webhook, has anyone faced this issue before.
{
    "timestamp": "2024-08-15T22:26:51.006Z",
    "level": "ERROR",
    "requestId": "",
    "message": {
        "errorType": "ExecutionAlreadyExists",
        "errorMessage": "Execution Already Exists: 'secretsarn'",
        "stackTrace": [
            "ExecutionAlreadyExists: Execution Already Exists: 'secretsarn'",
            "    at de_ExecutionAlreadyExistsRes (/var/runtime/node_modules/@aws-sdk/client-sfn/dist-cjs/index.js:2125:21)",
            "    at de_CommandError (/var/runtime/node_modules/@aws-sdk/client-sfn/dist-cjs/index.js:2070:19)",
            "    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)",
            "    at async /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20",
            "    at async /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/core/dist-cjs/index.js:165:18",
            "    at async /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38",
            "    at async /var/runtime/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:34:22",
            "    at async Runtime.handler (/var/task/index.js:13379:21)"
        ],
        "name": "ExecutionAlreadyExists",
        "$fault": "client",
        "$metadata": {
            "httpStatusCode": 400,
            "requestId": "",
            "attempts": 1,
            "totalRetryDelay": 0
        },
        "__type": "com.amazonaws.swf.service.v2.model#ExecutionAlreadyExists"
    }
}

Where does secretsarn come from? What makes you say it wasn't able to retrieve the installation id from the webhook?

I followed every step mentioned in the readme.md, I setup a new repo app  and able to invoke the lambda function to get the status.json which has necessary information including the installations object and all the status are ok, I created a sample workflow file to see if I am able to run it. But when I try to raise a PR in the AWS step function it is failing and the reason is installation id is -1.
installationId: payload.installation?.id ?? -1, I can see from the code that in library if the webhook payload does not contain the installation id then it by default assigns it to -1.
In my case sometimes when I invoke the lambda  status function before raising a PR, I am able to see the installation id and everything working correctly but it does not work every time, also it should not be required to run the status lambda function every time before you raise a PR right ?
I checked the GitHub app and permissions and everything and it is setup correctly, I was also not able to find the installation Id in the webhook payload from the webhook URL which was created while I created the app.
secretsarn come from the GitHub app.

You don't need to call the status function more than once while setting things up.
Installation id would not be there if the webhook is not called from an app. Did you maybe create an additional webhook manually? Was the initial setup done using the one-click wizard or did you create the app yourself?
Is secretsarn actually what's coming from the webhook or are you censoring something? That would be the actual cause of issue here. The execution id cannot be something constant as new executions will fail. It should never be anything like just secretsarn.
https://github.com/CloudSnorkel/cdk-github-runners/blob/ce649c33d9cac18e2dd81752db03d4f39d4f790d/src/webhook-handler.lambda.ts#L178-L181

No,  secretsarn is just an alias I used for censoring. Yes, I setup the app using the one-click wizard as mentioned in the Readme.md.
Also there is one more thing on successful runs I was able to see the installation id from the recent webhook deliveries from the Github App, but when looked from the Webhook section of the GitHub repo settings there is no installation id present.
Also wanted to ask do I need to Add a Webhook manually in the Webhooks field in the repo settings ?

Actually figured out the issue, we don't need to add it manually. Thanks for the help.


admin: added a title to the CSV button

And about the Gemfile.lock, well rvm is insisting on it...

LGTM, merge once you remove the useless commit.


[test-only] ApiTests. check group in the space request (#5492)

Port #5492 to stable-2.0

:boom: Acceptance test localApiTests-apiSpacesShares-ocis failed. Further test are cancelled...

the stable branch does not contain any "sharing space to groups" code, so this test only works in the master


Changed Twitter to X in README

Fixed: Update "twitter" to "x" in README.md https://github.com/elimu-ai/wiki/issues/168

Removed .DS_Store file @nya-elimu


Pick up postgres table owner

Looks like postgres has the tableowner concept. We can ingest this information during the metadata workflow

some details here https://stephencharlesweiss.com/postgres-getting-the-owner-of-tables

Hi @pmbrull, I would like to work on this issue

closed by https://github.com/open-metadata/OpenMetadata/pull/14289


Add redux-actions

Redux-actions provides Flux Action Standard utilities for Redux.
See: https://github.com/acdlite/redux-actions

@horiuchi @borisyankov Any chance to get this merged? Already using it in production. :)


Check user token on unprotected route?

Is there anyway to check for user on unprotected route in case they provide the token? The idea is that I want to get user login status everywhere on the site without getting JWT expired / invalid if the requested route is not protected.

Hello,
There are different ways to achieve this, the simplest being to configure the jwt listener (guard authenticator) on the unprotected firewall, beside the anonymous listener, e.g:
security:
    # ...
    firewalls:
        secure:
            pattern: ^/api
            stateless: true
            guard:
                authenticators:
                    - lexik_jwt_authentication.jwt_token_authenticator

        unsecure:
            pattern: ^/unsecure
            anonymous: true
            stateless: true
            guard:
                authenticators:
                    - lexik_jwt_authentication.jwt_token_authenticator
            # You may have the form login on this one
            #form_login:
            #    check_path: /login
            #    require_previous_session: false
            #    success_handler: lexik_jwt_authentication.handler.authentication_success
            #    failure_handler: lexik_jwt_authentication.handler.authentication_failure

    access_control:
        - { path: ^/unsecure, roles: [IS_AUTHENTICATED_ANONYMOUSLY, IS_AUTHENTICATED_FULLY] }
        - { path: ^/api, roles: IS_AUTHENTICATED_FULLY }

If a valid token is passed, you'll be able to retrieve the user from the controller of your unprotected route  through $this->getUser(), if no token was passed, it will be null.
One thing to be aware of: If someone sends an invalid token to your unprotected route, he will get a 401 failure response as for the secured firewall (exceptions are thrown even if you allows anonymous, invalid credentials should never be passed).
Hope this helps you.

I actually tried that solution but getting 401 is pretty undesirable since what I want is either null user / anon or user with correct credential to render the page.

You should have a look at https://github.com/lexik/LexikJWTAuthenticationBundle/issues/298, we give a trick to change this behavior. It will be documented soon

It works but it's kind of hacky IMO although i have only skimped through the spec so i'm unsure, or maybe it's how symfony normally works? I don't have much experience in symfony anyhow. Thanks for answering me.

Yeah, the authentication fails at the first exception thrown no matter if the current firewall allows anonymous requests or not, there's no built-in way to bypass that.
You're welcome.

I think i found a solution to handle a request on an unprotected route when the client sends an expired token.

Create your own JwtTokenAuthenticator and decorate the existing JwtTokenAuthenticator
Inject @security.access_map as argument
Check if the request has a role "IS_AUTHENTICATED_ANONYMOUSLY"
Abort JwtTokenAuthenticator process if needed

You can also extend this example by checking if the token is valid and only abort the authenticator when the token is invalid.
The benefit from this solution is not to separate your api endpoints by secure and public access.
The solution in #298 does not work to handle this problem. The code example also does not work in SF4.
public function supports(Request $request)
{
    $supports = $this->decorated->supports($request);
    list($accessMap) = $this->accessMap->getPatterns($request);
    if (is_array($accessMap) && in_array('IS_AUTHENTICATED_ANONYMOUSLY', $accessMap, true)) {
        $supports = false;
    }

    return $supports;
}


Option to use brew SQLite Include and Library Paths in Makefile

This allows mac users to compile this way without vendoring:
make USE_BREW_SQLITE=1 loadable

This is great, thanks @dleviminzi !


Add PR and issue templates

We will likely want to have PR and issue templates for this actual repo, as well as something (potentially a template of the template?) for repos created using the seed.

Nice to have, low effort


MAde is more user understandable

Kunal, Suryam has already made the changes in Graph_M.java, so please exclude that.
And please explain the purpose of the classpath and project file that you want to add.

Suryam and I did the changes in parts like he changed for case 4 and 6 and
i changed for case 3 and 5 and like this we did the whole project so i
request you to see both of ours code for complete user friendly display
On Thu, Dec 10, 2020 at 11:21 PM KISLAYA SRIVASTAVA <
<EMAIL_ADDRESS>wrote:

Kunal, Suryam has already made the changes in Graph_M.java, so please
exclude that.
And please explain the purpose of the classpath and project file that you
want to add.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/KISLAYA-SRI/THE-METRO-APP/pull/34#issuecomment-742685597,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN72V4GACUHGKV24J3TWXR3SUEDDPANCNFSM4UU5RGIQ
.


[TISPARK-47] Fix StoreNotMatch

Only invalidate store info when StoreNotLeader Error occurred

/run-all-tests

Codecov Report

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

@@            Coverage Diff            @@
##             master     #396   +/-   ##
=========================================
  Coverage          ?   55.17%
=========================================
  Files             ?      127
  Lines             ?     5812
  Branches          ?      864
=========================================
  Hits              ?     3207
  Misses            ?     2313
  Partials          ?      292

Impacted Files
Coverage Δ

...ava/com/pingcap/tikv/operation/KVErrorHandler.java
25% <0%> (ø)

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 c948d12...987b392. Read the comment docs.

I had some tests on TiDB's logic. If a store not match occurs (the tikv instance connected to does not have the correct store id in request):

store cache cleaned per error happened.
upon retry, RegionCache: GetRPCContext is called and address is generated using the error store id from PD. But this time, a different address is used since the storeID now points to the correct address (newly queried from PD).
Again request sent but might encounter not leader this time.
Follow the correct path for not leader.
Above is why we didn't see any switch leader and still changed address and resolve store not match.

We continuously get store not matches means the store address returned by getRegionStorePairByRegionId does not matches the context generated by region using TiRegion.peer.
builder.setRegionId(meta.getId()).setPeer(this.peer)

Above is the code to set store id (this.peer)
Peer leader = region.getLeader();
long storeId = leader.getStoreId();
return Pair.create(region, cache.getStoreById(storeId));

And above is getRegionStorePairByRegionId. According to code, region.peer is the same as region.getLeader. So if region is the same, store should match.
So I guess, there is a racing that changed region causing getRegionById returns a different region than in the context.

It looks like, in onStoreNotMatch we might use the region returned by getRegionStorePairByRegionId instead of the one cached in RegionStoreClient.

/run-all-tests

PTAL @ilovesoup


Graceful shutdown gotcha

Sending SIGTERM to any process requiring phantom will kill it, whether or not it's caught in the main code. This seems to be a direct result of #121 and #122: phantom catches the signal and calls process.exit().
I can work around this by calling process.removeAllListeners("SIGTERM") and then adding my listener, but it's not something I expected. Would be nice to have this either fixed or documented.

In the new version I don't kill anything. I wait until until phantom shuts down gracefully.


[BUG] trailing newline on gpu name

General description of bug:

What happened: Updated fastfetch on a raspberry pi and there is an extra "\n" in the gpu name which breaks the formatted output
What should happen:
Fastfetch version used: 2.26.1
Did it work in an older version: Previous versions had an error instead
Where did you get the binary: Built from source with minimal dependencies.
Does this issue still occur in the latest dev build? Yes

Often helpful information:
 fastfetch --list-features
threads
zlib
linux/videodev2
linux/wireless

Output on 2.26.1
fastfetch -s gpu --format json
[
  {
    "type": "GPU",
    "result": [
      {
        "index": null,
        "coreCount": null,
        "coreUsage": null,
        "memory": {
          "dedicated": {
            "total": null,
            "used": null
          },
          "shared": {
            "total": null,
            "used": null
          }
        },
        "driver": "vc4-drm",
        "name": "bcm2835-vc4\n",
        "temperature": null,
        "type": "Integrated",
        "vendor": "Brcm",
        "platformApi": "DRM (card0)",
        "frequency": 0,
        "deviceId": 0
      }
    ]
  }
]

The output on 2.25.0
 ./fastfetch -s gpu --format json
[
  {
    "type": "GPU",
    "error": "GPU detection failed"
  }
]
``

Please test

@CarterLi do you plan to cut a new patch release with this fix?

Just made some changes to cpu gpu and board modules. If you can test the changes if they work fine for raspberry pi, I'm happy to cut a release.


Data loss at process exit

Expected behavior: if there is unsent data when the process is exiting, TelemetryClient.flush({callback: cb}) should send it, and call cb once it's sent.
Actual behavior: cb only called when there's no unsent data.
PR #746 made Sender.send async: https://github.com/microsoft/ApplicationInsights-node.js/pull/746/files#diff-8f8fde719f491d55f9740db69f902f6c192818ea548949e483d6193051832e46L108 .
Channel.triggerSend (called by TelemetryClient.flush) ignores the Promise that send returns: https://github.com/microsoft/ApplicationInsights-node.js/blob/bbb2c05059c5d4893c50c2bd6b2239eccea7bd54/Library/Channel.ts#L86 .
So, for example, this contrived code
TelemetryClient.flush({callback: () => {
  process.exit(1);
});
process.exit(0);

should always exit with code 1. Instead, if there's data in the TelemetryClient's channel, it will exit with code 0.

@apotterri you can use isAppCrashing flag to force flush to run synchronously, we have that flag to be able to capture exception telemetry when there is an unhandled error in the app
appInsights.defaultClient.flush({     isAppCrashing: true, callback: () => {         console.log("Callback done");     } }); console.log("Process Done");

Hi @hectorhdzg. Thanks for this. I looked at isAppCrashing, but it doesn't really match my use case.
Setting it to true causes isNodeCrashing to be true here:
https://github.com/microsoft/ApplicationInsights-node.js/blob/c13a78d900be17f000992c2a2fbfb162062c5271/Library/Channel.ts#L89
So, by my reading, flush doesn't send the HTTP request synchronously. Instead, the data gets written to disk, and will be sent the next time a successful HTTP request is made. Is that right?
 So, even if we enabled saving to disk, we still might miss that final event.

@apotterri that is correct I just realized it will not be actually send to ensure telemetry is not lost, flush method is asynchronous but we only support callbacks to handle that, not promises, the behavior your are seeing is by design, we are working on moving to use promises instead and we already started in internal APIs but updating public APIs like flush method will generate breaking changes, we are planning to have a new major version release of the SDK with this and other kind of changes next semester

Ok, thanks very much. I've got a workaround in place that's good enough for now.
We'll look at upgrading when the new release comes out.

Ok, thanks very much. I've got a workaround in place that's good enough for now.
We'll look at upgrading when the new release comes out.

Hi There, can i ask how you did your workaround? Having a similar problem ATM...

@dornfeder It's not great. I'm basically doing:
TelemetryClient.flush();
setTimeout{() => {
  process.exit(code);
}, 1000);

which will get me the events most of the time.

@apotterri @dornfeder This should work now as we've upgraded to OpenTelemetry. Please give this scenario a try again. Thank you!


Add the ability to specify layers for the image and layers for the normal map

Hello! Thanks a lot for your plugin, very useful already.
In my workflow, I edit a large scene but I need to load each layer in their own files. I used to run a script to run this export, but when finding out about this tool, it felt that this could do it. As far as I could find, not yet, but maybe this open issue concerns this point?
To be extra clear, I have one aseprite file with several layers. In my scene, I would like to use this aseprite resource, with an index, or a layer name, so that only this layer appears.
Thank you in advance for your help!
Cheers


Review tfgrid module/package structure

Do we really want all solution structs and definitions like peertube and funkwhale to be directly in the threefoldtech.threebot.tfgrid module in the v client?
Same for the serverside go package.

The v-clients have been refactored: b94241f391f83340da74c2476a1478b8f73773f9

Follow up issue for the serverside go packages: #159


What is the best way to find all final nodes ?

Discussed in https://github.com/setzer22/egui_node_graph/discussions/13

Originally posted by rsaccon February 25, 2022
I want to find all final nodes,  which is all nodes which do not have out-going connection. I haven't found any in-built way at egui_node_graph to do this.
What I found is a way to find a connection based on the InputId, by using:
egui_node_graph::graph_impls::Graph
    pub fn connection(&self, input: InputId) -> Option<OutputId>

But with that approach, to find out for one specific node, whether it has no outgoing connections, I would have to iterate over all inputs of all nodes to query if they have a connection to that specific node, which is not very efficient. Is there a better way to do this ?
If there is no good way to do this yet, I suggest we add that capability to egui_node_graph by maintaining a list of final nodes (which needs to be adapted each time a connection gets added or removed).

#30 makes this a bit easier once it's merged.
You can now lookup the nodes outputs via graph.outgoing(output_id) to check if they are connected to anything. Which is more efficient (it should be O(nodes * output_ports)), but on large graphs might still be a bit too slow if you're searching for final nodes every frame or something.
The modified events mean that it's easier to maintain an efficient external (to the library) datastructure containing a list of final nodes - since the ConnectionAdded/Removed events will now always specify the output port, from which you can get the node with the output port, and then determine if you need to modify your your final nodes set by looking at only that nodes output ports (again via graph.outgoing(output_id)). If this paragraph isn't clear I'd be happy to write some example code.
@rsaccon you might be interested in the above.


consider lzma compression for sharing urls

When we share a URL the amount we can share depends on the size of the resultant URL. Compression there is key. consider compressing the URL rather than (or before?) Base64 encoding. Look at https://www.npmjs.com/package/lzma as a common compression technique (used in https://itty.bitty.site)

We've looked into this making some test on Izma compression with a huge package-lock.json file.
From our tests looks like that the current compression method used by the website (pako) works better than Izma.
If you take a look at this test you can see that the same object compressed by pako is actually shorter than the same compressed with Izma.


FormatViolation Error

@OrangeTux
I am receiving FormatViolationError continuously on my OCPP Server. As one of the CP's is sending incorrect Json Payload. How can I change it into an exception and log it into warning? So that my log file does not fill up.

@OrangeTux
A CP is sending me this raw message and I am receiving FormatViolationError while it is trying to unpack the raw message. How can I convert this error log into a Warning?
[2,"213","StartTransaction",{"connectorId":2,"idTag":"336699\\\\\\","meterStart":33259490,"timestamp":"2022-07-28T09:41:15Z"}]
ERROR
FormatViolationError: Payload for Action is syntactically incorrect or structure for Action

To help understand why this is happening, could you please post the code you have written?


fix display_clear use memset

otherwise the display might have some crap from the memory on it

Thanks for the fix @silps - I just tried out this code and was noticing some odd garbage left on the screen.  This change fixed that for me.

Thank you for this fix, I had distorted output as well, this worked.


Crashing on iPad Pro (2016)

Crashes after scrolling for a few minutes.  No specific pages or Subreddits cause the issue.
Cleared cache without luck. Reinstalled without luck.
iOS fully updated and no other device issues.
Crashing starts with application stuttering and heating of device.

Could you please try setting video autoplay to "Never autoplay videos"? We've identified a potential memory leak relating to videos that we're in the process of fixing, and I'd like to see if that resolves your problem.

Still crashes. May be able to scroll further, but it still ends with stuttering, black screen and back to the home screen/out of the app.

Do you experience this if you reset to default settings?

Yes.  Only thing I have changed is the theme is the Oled black one.  I’ll reset it again to default later to make sure it’s all clean and clear.

A lot has been done for v3.0 and I think the memory issue you were seeing has been fixed. If you notice anything else please re-open the issue!

Not sure how to reopen.  It is SIGNIFICANTLY better, so it does appear great progress has been made, but I do still have some crashing issues.  In the case of a crash a few minutes ago i was able to browse for 45 minutes straight with lots of gifs etc showing up before it just stopped responding.  After about 30-45 seconds The app crashed.
Had this happen a few times over the past week.
Again though, great progress!

Unfortunately random crashes like that are much harder to reproduce any may not be fixable without some steps for reproduction. Let me know if you find any! That is likely a completely different issue then what we’ve fixed

On Feb 25, 2019, at 6:12 AM, scot-onet<EMAIL_ADDRESS>wrote:
Not sure how to reopen. It is SIGNIFICANTLY better, so it does appear great progress has been made, but I do still have some crashing issues. In the case of a crash a few minutes ago i was able to browse for 45 minutes straight with lots of gifs etc showing up before it just stopped responding. After about 30-45 seconds The app crashed.
Had this happen a few times over the past week.
Again though, great progress!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Fix sile wrapper issues on darwin.

Darwin execve has issues with shebang lines that point to other scripts
with shebang lines. A new makeBinaryWrapper hook was added to workaround
the issue on darwin. See #171473 and #23018 for more information. This
uses that binary wrapper to fix packages like sile.
I'm not sure this can be considered complete but it appears to work for
sile at least.
cc: @doronbehar, alerque
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I didn't see a maintainers list for the lua interpreters package so if there is someone else I should be cc-ing on this let me know.
I'm not sure if it's worth having this be conditionally used on darwin as opposed to all platforms but that would also be an option.

I have tested on a darwin M1 macbook and it seems to work. I have not tested on linux or x86 platforms.

This cannot be considered complete yet but it appears to work for
sile at least. There is an issue in the checkPhase that has something to do with libtexpdf that seems unrelated but I'm still digging into it.
	dlopen(./core/justenoughlibtexpdf.so, 0x0006): Library not loaded: /nix/store/q97r3hiic0jg6ks95xylazf9m21hd1wh-sile-0.12.5/lib/libtexpdf.0.dylib
  Referenced from: /Users/zaphar/projects/nixpkgs/sile-0.12.5/core/justenoughlibtexpdf.so
  Reason: tried: '/nix/store/q97r3hiic0jg6ks95xylazf9m21hd1wh-sile-0.12.5/lib/libtexpdf.0.dylib' (no such file), '/usr/local/lib/libtexpdf.0.dylib' (no such file), '/usr/lib/libtexpdf.0.dylib' (no such file)
stack traceback:
	[C]: in ?
	[C]: in function 'require'
	./core/libtexpdf-output.lua:1: in main chunk
	[C]: in function 'require'
	./core/sile.lua:78: in function 'init'
	./sile:44: in main chunk
	[C]: in ?
Syntax Error: Document stream is empty
make: *** [Makefile:1381: selfcheck] Error 1```

Hello!

Diff looks pretty good, though I doubt there aren't any other small fixes for individual packages this affects, that need to be taken care of.
Could you please not cc me in the commit message? If that commit would have been merged, every user pushing that commit to their fork will send me an email notification.
cc @alerque for the libtexpdf issue.
This should target branch staging, as it triggers too many rebuilds.
It'd be nice to see a few examples of packages that build fine with this patch, just to see that it doesn't ruin every package that uses lua. Try packages from the luaPackages attribute set, such as luacheck (it has a CLI interface) and check whether it's wrapper works as expected. It'd be also nice to test packages that plainly use lua as a dependency but don't use luaEnv = lua.withPackages like sile - check whether this patch affects them (it will most likely not, if the lua setup-hook works just like before.

I closed and reopened a different one to target staging at: https://github.com/NixOS/nixpkgs/pull/172749


Added DUR feature

Codecov Report

Merging #10 (faa768b) into master (b405cdf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #10   +/-   ##
=======================================
  Coverage   88.65%   88.65%
=======================================
  Files           8        8
  Lines         282      282
=======================================
  Hits          250      250
  Misses         16       16
  Partials       16       16

Impacted Files
Coverage Δ

profile.go
90.00% <ø> (ø)

Continue to review full report at Codecov.

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


Does this only work with g++ or does it work with clang

Does this also work with clang?  If not, seems like it should - though I'm, not sure if this is a limitation of gyp or this particular package.

Apparently it does, since g++ points to clang on macosx, which I'm using.  On linux it tries to pick up g++ even if only clang is available.  Is it possible to fix this in this module so it also works with clang?

hiredis(-node) does nothing special in that regard and completely relies on gyp to do its work. Whatever C++ and C compiler matching more or less what gcc 4.8 is doing will work (that includes any recent clang++)
Setting CXX=clang++ CC=clang in your environment or simply linking the name to the right compiler could work.


Relatively High CPU Usage When Paused and not Minimised

First off, I have seen that there already are a lot of issues concerning CPU usage. But I think that mine is different.
OS: Ubuntu 17.04
GPMDP Version: 4.3.0
Issue Descriptions:
Google Play Music Player has an (in my opinion) fairly low CPU usage when playing music:

Great work on that! :+1:
However, the CPU usage is just as high (or higher!) when the music is paused:

When taking this screenshot, the Google Play Music Desktop Player window was open on another workspace, but playback was paused. Minimising the window solves the issue. It does not affect the issue whether the window is open on current or another workspace.
If Google Play Music is opened in Chrome, the CPU usage is similar while playing music. But it goes down to 0 when music is paused, regardless of whether the window is visible or not.
To summarise, I’d expect the CPU usage of Google Play Music Desktop Player to drop to zero shortly after pausing playback.
(Please excuse my backup tool taking the first place in both screenshots).
Steps to Reproduce:

Open Google Play Music Desktop Player
Start some music.
Pause the music.
Wait a little for things to settle.
Look at the CPU usage
Minimise the window -> CPU usage goes to 0
Open the window again -> CPU usage is at 2-5% again.

I can confirm that is true. In my new MacBook Pro 2017 I can se a high CPU usage e extremely high energy impact on Activity Monitor which turn the fans on. It is a very nice app however, It would have a good performance improvement.
Hope that you guys can fix it soon.
Going back to web chrome version :-(

@betorobson I'm with you on this one, on the new MacBook Pro 2017 too, had to uninstall GPMDP because of high CPU usage. Would be great to see this resolved.

Same on Windows 10. Have always remember to minimize GPMDP so my laptop can make it till evening.

@yangwao I don't think that made any difference. Look:
Before:

After:

It's only making a huge difference when I minimise the window.

Same here, Kubuntu 17.10, KDE 5.12
~20% CPU unless minimized.

OSX Sierra, MacBook Pro (Retina, 15-inch, Mid 2015).  I see 10-20% CPU when window open, but idle, and < 1% when minimized.  This is particularly for the "helper" process.  The parent does not seem so aggressive.

On Ubuntu 18.04 uses over 25% of CPU in 4th gen Intel i5 even when not playing anything and is very slow and unresponsive.

Guys, using this app is really too expensive. I compared playing music with Foobar with all sound processing and whistles takes about 0,3% on my system, but your app takes 1% even when the music is paused. This doesn't make me want to use it.

This is how much resources it uses, recently it completely froze GNOME, had to kill it. I really wish to use it by I simply cannot now.


Login/Register Page

Need to create the page for signup and login
Should use some sort of reCAPTCHA system to try mitigate bot accounts.

we should go passwordless

users forget passwords
users leak passwords
service gets compromised, passwords leak
if user's email gets compromised, thats their/their service's fault

I dont think going passwordless is best, I think having both is good. So like you can go passwordless if you have an email and we can send you a magic link?
Auth.js wont work since we are not using a javascript backend.

@treuks is it free?

ye

for the password hashing algo, i have previously used argon2 and bcrypt, I believe argon2 was the best however I havent kept up with the state of password hashing.

AFAIK "argon2 + salt + pepper" is the last word in password hashing. bcrypt is practically legacy by now. Giving it a quick search just[^1] in[^2] case[^3], I see no problems. I would encourage to read the OWASP cheatsheet[^1] in particular.
If we really want to get into it, we could try to follow NIST guidelines[^4]. Document B says you SHOULD salt and lists a few recommended options for hashing:

Examples of suitable key derivation functions include Password-based Key Derivation Function 2 (PBKDF2) [SP 800-132] and Balloon [BALLOON]. A memory-hard function SHOULD be used because it increases the cost of an attack. The key derivation function SHALL use an approved one-way function such as Keyed Hash Message Authentication Code (HMAC) [FIPS 198-1], any approved hash function in SP 800-107, Secure Hash Algorithm 3 (SHA-3) [FIPS 202], CMAC [SP 800-38B] or Keccak Message Authentication Code (KMAC), Customizable SHAKE (cSHAKE), or ParallelHash [SP 800-185].

But if we don't need FIPS-140[^5] compliance, I don't think we need to strictly follow that.
[^1]: https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html (archived 2023-03-03)
[^2]: https://developer.okta.com/blog/2019/07/29/hashing-techniques-for-password-storage
[^3]: https://codesigningstore.com/what-is-the-best-hashing-algorithm (archived 2023-03-03)
[^4]: https://pages.nist.gov/800-63-3/
[^5]: https://en.wikipedia.org/wiki/FIPS_140


Fixing a bug with dockerfile builds

Codecov Report
Patch and project coverage have no change.

Comparison is base (6284a78) 75.07% compared to head (1f85405) 75.07%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #571   +/-   ##
=======================================
  Coverage   75.07%   75.07%
=======================================
  Files          55       55
  Lines        3362     3362
=======================================
  Hits         2524     2524
  Misses        838      838

Flag
Coverage Δ

unittests
75.07% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Automatically filter by facilities of the current authenticated user #7

The evaluations, orders, and deliveries should be filtered by the facility the current user belongs to.

no longer need to make changes to the sdk.. Basem pushed the changes we needed while we were working together


Conflict between the implementation of RFC and the Original Paper

Hello,
I think there is a difference between your implementation of RFC and the original paper. In the paper, authors count the number of unique invocations plus the set of all methods in the class .

Yes, same here, I don't get why you would sum the methods in the class.
But that's easy to get if you really want the original RFC definition, as you can sum up RFC + total methods.
(I should make it explicit in the README that my goal was not to implement metrics as they were defined in the very old original paper, but more like a revised and pragmatic implementation of it)


Update PowerShell samples

Correctly capitalize Set-Mailbox and Get-Mailbox.
Add -Identity parameter for consistency with other docs.
Get-Mailbox returns only 1000 items by default and will fail to give result if the Scheduler Assistant mailbox is not included in the first 1000 mailboxes, add -ResultSize Unlimited to search all mailboxes.

Now:
Set-mailbox<EMAIL_ADDRESS>-SchedulerAssistant:$true
Should be:
Set-Mailbox -Identity<EMAIL_ADDRESS>-SchedulerAssistant:$true
Now:
Get-mailbox | where {$_.PersistedCapabilities -Match "SchedulerAssistant"}
Should be:
Get-Mailbox -ResultSize Unlimited | where {$_.PersistedCapabilities -Match "SchedulerAssistant"}

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

ID: d33f8e34-9baa-3efd-b1cc-03f3e3ab44f0
Version Independent ID: 201878c7-a0d7-a744-c60c-d65f714d2a9d
Content: Setting up Scheduler for Microsoft 365.
Content Source: microsoft-365/scheduler/scheduler-setup.md
Service: scheduler
GitHub Login: @AshaIyengar21
Microsoft Alias: v-aiyengar

@JetzeMellema Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/5319
The changes will reflect once the author approves the PR.
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @JetzeMellema Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


fix: Use the right version of kube provider

Available since: https://registry.terraform.io/providers/hashicorp/kubernetes/2.16.0/docs/resources/deployment

This PR is included in version 1.11.3 :tada:


Error when shuffle dataset

Hi,
I'm new on neural networks and GroundHog.
Traceback (most recent call last):
File "shuffle-hdf5-1.py", line 68, in
pos = indices_in[fi][ii]['pos']
File "C:\Python27\lib\site-packages\tables\table.py", line 2119, in getitem
raise IndexError("Index out of range")
IndexError: Index out of range
Could anyone help me with it?

Hi,
GroundHog isn't actively developped for now. We are more working on blocks.
There is a PR to document it:
(https://github.com/mila-udem/blocks-examples/pull/20).
Blocks isn't completly ready to replace all GroundHog feature yet.
But I try guess a few reason for your errors:

old pytables version
the original file is truncated/corrupt

This could explain that. Can you check them?
On Wed, Aug 5, 2015 at 5:16 AM, xishazgh<EMAIL_ADDRESS>wrote:

Hi,
I'm new on neural networks and GroundHog.
Traceback (most recent call last):
File "shuffle-hdf5-1.py", line 68, in
pos = indices_in[fi][ii]['pos']
File "C:\Python27\lib\site-packages\tables\table.py", line 2119, in
getitem
raise IndexError("Index out of range")
IndexError: Index out of range
Could anyone help me with it?
—
Reply to this email directly or view it on GitHub
https://github.com/lisa-groundhog/GroundHog/issues/34.


RecursionError: maximum recursion depth exceeded while calling a Python object

when train on 18epoch, it would report error:
Traceback (most recent call last):
  File "train.py", line 396, in <module>
    train_model(args)
  File "train.py", line 213, in train_model
    lossTr, lr = train(args, trainLoader, model, criteria, optimizer, epoch)
  File "train.py", line 328, in train
    optimizer.step()
  File "/home/lgq/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/optim/lr_scheduler.py", line 36, in wrapper
    return func(*args, **kwargs)
  File "/home/lgq/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/optim/lr_scheduler.py", line 36, in wrapper
    return func(*args, **kwargs)
  File "/home/lgq/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/optim/lr_scheduler.py", line 36, in wrapper
    return func(*args, **kwargs)
  [Previous line repeated 991 more times]
  File "/home/lgq/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/optim/adam.py", line 69, in step
    state = self.state[p]
  File "/home/lgq/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/tensor.py", line 393, in __hash__
    return id(self)
RecursionError: maximum recursion depth exceeded while calling a Python object

I found that you put WarmupPolyLR in every iters, it would make every iter call WarmupPolyLR, maybe it cause the error.

It's your personal question, you should specify the --warmup_iters, for me, there is no any problem

In my opinion, you could not put  WarmupPolyLR in every iter.

There is no code on github like this, include pytorch document not do it. And it could bring burden to system. It would report errors due to the difference of pytorch version.
There is no need to do this. You put WarmupPolyLR in every iter because you want to use variable
cur_iter. But cur_iter does not need to pass on. When you define WarmupPolyLR, you inherit torch.optim.lr_scheduler._LRScheduler, there is a variable self._step_count in _LRScheduler, it has a same purpose to cur_iter.So you could just write like:

    def get_lr(self):
        self.cur_iter = self._step_count - 2
        if self.cur_iter <= self.warmup_iters:
            alpha = self.cur_iter / self.warmup_iters
            warmup_factor = self.warmup_factor * (1 - alpha) + alpha
            # print(self.base_lrs[0]*warmup_factor)
            return [lr * warmup_factor for lr in self.base_lrs]
        else:
            return [self.eta_min + (base_lr - self.eta_min) *
                    math.pow(1 - (self.cur_iter - self.warmup_iters) / (self.T_max - self.warmup_iters),
                             self.power) for base_lr in self.base_lrs]

or you could just use (self._step_count - 2) to replace self.cur_iter. After do this, you only need to call  WarmupPolyLR after train once, it could have same effect to your origin code, but it reduce many times call function WarmupPolyLR.
What's more, thank you for your code and happy new year :)

Happy New Year ! Thank you for you suggestion.

Hi @lgqfhwy
Were you able to resolve this issue because I am facing it as of now.
Please let me know your workaround.
I did try increasing the max recursion depth by using the sys library in python, but it still gets stuck at th 9th epoch for me.

Maybe this way can help you.
https://github.com/xiaoyufenfei/Efficient-Segmentation-Networks/blob/0f0c32e7af3463d381cb184a158ff60e16f7fb9a/train.py#L25

the reason for this is
        if args.lr_schedule == 'poly':             lambda1 = lambda epoch: math.pow((1 - (args.cur_iter / args.max_iter)), args.poly_exp)             scheduler = optim.lr_scheduler.LambdaLR(optimizer, lr_lambda=lambda1)         elif args.lr_schedule == 'warmpoly':             scheduler = WarmupPolyLR(optimizer, T_max=args.max_iter, cur_iter=args.cur_iter, warmup_factor=1.0 / 3,                                  warmup_iters=args.warmup_iters, power=0.9)
Just turn it into a global variable


Health checks not relaunching container when EC2 host is terminated.

Rancher Versions:
Server: 1.3.1
healthcheck: rancher/healthcheck:v0.2.0
ipsec: rancher/net:holder
network-services: rancher/network-manager:v0.4.0
scheduler: rancher/scheduler:v0.5.1
kubernetes (if applicable):
Docker Version:
1.12.3
OS and where are the hosts located? (cloud, bare metal, etc):
RancherOS
AWS EC2
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node Rancher server, external RDS DB, x4 EC2 hosts (x2 tagged as eu-west1-goagent + x2 tagged as eu-west1-goserver)
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Deploy go-cd server service as a single container via scheduling to named host label eu-west1-goserver.
Terminate the host running the gocd-server service from within the AWS EC2 console.
Results:
Host drops to disconnected status, gocd service drops to unhealthy and remains so, even when host manually deactivated and/or the host is totally deleted from the Rancher UI console.
The service container only relaunches in a healthy host when 'Finish Upgrade' is manually instigated.
Expected:
Service to relaunch on a healthy host after specified health check period (i.e. x2 instances of 4000ms)
To clarify why we are doing this by terminating a host instance. It is a test of EC2 zone/instance/network outages, we need to be confident that Rancher container deploy/manage is resilient.

To add to this. I have tested outside of AWS EC2 with a local Vagrant/Virtual Box set up this morning and the issue is the same. Kill the underlying host and the container doesn't relaunch on a healthy host, even though it is reported as unhealthy and the host identified as disconnected.

@richbos that doesn't sound like the same issue.  You're service is in the middle of an upgrade and we do not currently reconcile (reschedule) containers that are involved.  Clicking finish upgrade puts the service back into normal active state.

Hi, many thanks for the reply.
Yes, it would seem the upgrade process is indeed what is happening, although should this not be automatic? i.e if an underlying host dies and the health check reports an unhealthy container + disconnected host I would expect the container to re-launch on a healthy host?

Maybe I didn't explain the issue correctly? Or what my expectations of how Rancher works are....
Basically, if we have a selection of EC2 hosts, and one of them becomes unavailable for whatever reason (we are simulating this by terminating the instance) then I would expect Rancher to relocate the containers which were running on the failed host to another healthy host. However this isn't happening for us, not in EC2 or in a localised test environment using VirtualBox with Vagrant initialised hosts.

Just to further clarify, the service is not initially in an upgrade state, and does not change to an upgrade state UNTIL the underlying host is removed, it then changes (to the upgrade state) and requires manual intervention to restart/relocate to a healthy host. This is not expected behaviour.

I'm evaluating rancher right now and am experiencing what i think is the same issue. i kill my host and none of my containers are restarted anywhere else.  Isn't the whole idea of cattle to make sure my stacks are always running?

@vincent99 Hi, just wondering if there might be any movement imminent on this issue?
Unfortunately we need a solution for our development route so if not we may have to divert efforts to evaluating AWS ECS in place of Rancher.

@richbos Rescheduling because of a healthcheck failure does not trigger an 'upgrade' and doesn't put the service in the state your screenshot suggests.  It still seems like you're doing an Upgrade at some point and never clicking to finish it.
To see a container move over you need:

A service starting in active state (which would not have a "Finish Upgrade" action)
A healthcheck on that service which will pass while the service is up (so it leaves initializing health state) and then fail when it's down (that's the easy part).
-A trigger to make the healthcheck fail.  Note that just marking a host in Rancher as 'inactive' only prevents new containers from being scheduled to it, it doesn't evacuate existing ones (that will eventually be a separate action).  Stopping the instance in EC2 is a straightforward way (since your screenshot shows disconnected you have this part working)
Another eligible host to put the service container on.  For example the other host(s) may not be eligible if the service is defined to only go on that particular host, or to require a label only the host has, or require not having a label every other host has, or the ports it publishes are in use, etc.

Hi @vincent99 - I understand what you are saying but we weren't doing an upgrade, the container was in an active state prior to the host being taken down, this was the same in both of the environments (EC2  and VirtualBox). The host label specified was tagged to x2 hosts.
We tested this many, many times, both in EC2 over a period of several days, however, I have just re-tested now and the container relocated when the underlying host was stopped, so it would appear that without any intervention the problem has resolved itself, which is even more baffling.
Here are grabs detailing the configuration.

....and finally, the result of the failed host from today as we would have expected, i.e with the container automatically relaunched on a healthy host.

Ok @vincent99 - My colleague thinks this may be down to a need for 3 hosts, i.e in order to decide on 'split brain' state?
For example, re this -
“Rancher exhibits the characteristics of an active-passive HA deployment, so the number of host failures that may be tolerated is computed as ceil(N / 2) – 1, where N is the number of Rancher nodes. In simpler terms, a 3-node deployment survives 1 host failure, a 5-node deployment survives 2 host failures, and so on."
Would that be it? Do we require x3 hosts per service?
RB

I also hear what you're saying but the only way you get the screenshot showing "Finish Upgrade" is if the service is in Upgraded state, and the only way that happens is if a human triggers it.  Maybe it was someone else with access to the environment?
The HA setup (if you use it) is active/active and has that (n/2)-1 property like any distributed system.   But this is not relevant to your problem unless these hosts are also the ones running the rancher/server.  All the hosts registered to an environment can fail and the orchestration system is still fine because it's not running on those hosts.
There is a small benefit to having >= 4 hosts in an environment, in that it allows the optimal health check setup.  Health checks for a container are performed on (up to) 3 hosts, separate from the one one the container lives on.  So if you have 4+ hosts you get checks from 3 independent hosts.  With <= 3 one of the checks goes on the same host as the container is on, and with =1 host it's only the host checking itself.

Hi @vincent99, there is nobody else has access to our environments, not in ec2 and certainly not locally in my home office.
We shall re-test again tomorrow and post relevant before and after grabs to verify the upgrade state as described.
The issue as we see it then is that for some reason that with our configuration the service seems to be entering the upgrade state as a result of the underlying host being removed. This is what we need to clarify is happening and I guess if we can reproduce that then we can take if from there.
I shall report back tomorrow.

Hi @vincent99, many thanks for your attention and help with this.
We have carried out extra tests and yes, it was down to our misunderstanding of the Rancher service and container launch process.
When we launch our container service we need it to run on certain hosts, as such we do not start it but 'upgrade' for host tags using scheduling, we then click 'upgrade'.
What we didn't realise was that even as the service has become active there is another manual step, i.e. after clicking upgrade you then have to wait and click 'finish upgrade'. We didn't realise this, we thought as it was active, then it was active.
So, the issue for us has changed. Ideally we would like to be able to select scheduled host tags at container/service launch. We don't really see this as an 'upgrade', but more of a 'configuration' option, it would also streamline the process for us. Do you think this might be possible as a feature request? Or is there logic to the way the process currently is and it is something we would need to live with?

Are you deploying things from catalog, and turning off start on create so you can change them before they first run?  That's basically https://github.com/rancher/rancher/issues/2852 , which we'll have a solution for eventually..

Hi @vincent99 , yes, that is exactly it...! Great to hear you are working on a solution, that would be perfect for our needs.
Thank you again for your advice and patience.

related tickets for this have been fixed and closed. Please file a new ticket if issue persists in rancher 1.5.9+.
https://github.com/rancher/rancher/issues/3239


urllib.error.URLError: <urlopen error [Errno 60] Operation timed out>

Checklist

[ ] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2021.12.17
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

# youtube-dl --version
2021.12.17

# youtube-dl --download-archive archive.txt -v -f 'bestvideo[ext=mp4]+bestaudio/best[ext=mp4]/best' https://www.youtube.com/playlist\?list\=PLHTh1InhhwT4TJaHBVWzvBOYhp27UO7mI
[debug] System config: ['--force-ipv4', '--prefer-insecure', '--user-agent', 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:97.0) Gecko/20100101 Firefox/97.0']
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--download-archive', 'archive.txt', '-v', '-f\xa0bestvideo[ext=mp4]+bestaudio/best[ext=mp4]/best', 'https://www.youtube.com/playlist?list=PLHTh1InhhwT4TJaHBVWzvBOYhp27UO7mI']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.9.9 (CPython) - FreeBSD-13.0-RELEASE-p4-amd64-64bit-ELF
[debug] exe versions: ffmpeg 4.4.1, ffprobe 4.4.1, rtmpdump 2.4
[debug] Proxy map: {}
[youtube:tab] PLHTh1InhhwT4TJaHBVWzvBOYhp27UO7mI: Downloading webpage
[download] Downloading playlist: CppCon 2021 - Back To Basics
[youtube:tab] playlist CppCon 2021 - Back To Basics: Downloading 17 videos
...
[download] Downloading video 7 of 17
[youtube] cpkDQaYttR4: Downloading webpage
...
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2288, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/local/lib/python3.9/urllib/request.py", line 523, in open
    response = meth(req, response)
  File "/usr/local/lib/python3.9/urllib/request.py", line 632, in http_response
    response = self.parent.error(
  File "/usr/local/lib/python3.9/urllib/request.py", line 555, in error
    result = self._call_chain(*args)
  File "/usr/local/lib/python3.9/urllib/request.py", line 494, in _call_chain
    result = func(*args)
  File "/usr/local/lib/python3.9/urllib/request.py", line 747, in http_error_302
    return self.parent.open(new, timeout=req.timeout)
  File "/usr/local/lib/python3.9/urllib/request.py", line 523, in open
    response = meth(req, response)
  File "/usr/local/lib/python3.9/urllib/request.py", line 632, in http_response
    response = self.parent.error(
  File "/usr/local/lib/python3.9/urllib/request.py", line 555, in error
    result = self._call_chain(*args)
  File "/usr/local/lib/python3.9/urllib/request.py", line 494, in _call_chain
    result = func(*args)
  File "/usr/local/lib/python3.9/urllib/request.py", line 747, in http_error_302
    return self.parent.open(new, timeout=req.timeout)
  File "/usr/local/lib/python3.9/urllib/request.py", line 523, in open
    response = meth(req, response)
  File "/usr/local/lib/python3.9/urllib/request.py", line 632, in http_response
    response = self.parent.error(
  File "/usr/local/lib/python3.9/urllib/request.py", line 555, in error
    result = self._call_chain(*args)
  File "/usr/local/lib/python3.9/urllib/request.py", line 494, in _call_chain
    result = func(*args)
  File "/usr/local/lib/python3.9/urllib/request.py", line 747, in http_error_302
    return self.parent.open(new, timeout=req.timeout)
  File "/usr/local/lib/python3.9/urllib/request.py", line 517, in open
    response = self._open(req, data)
  File "/usr/local/lib/python3.9/urllib/request.py", line 534, in _open
    result = self._call_chain(self.handle_open, protocol, protocol +
  File "/usr/local/lib/python3.9/urllib/request.py", line 494, in _call_chain
    result = func(*args)
  File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 2735, in https_open
    return self.do_open(functools.partial(
  File "/usr/local/lib/python3.9/urllib/request.py", line 1349, in do_open
    raise URLError(err)
urllib.error.URLError: <urlopen error [Errno 60] Operation timed out>

Description

There is an unhandled timeout exception.

This appears to be a duplicate. Did you try the Python patch in the other issue?

It doesn't seem to be a duplicate. It's another error.

Also this:
[debug] Command-line args: ['--download-archive', 'archive.txt', '-v',
'-f\xa0bestvideo[ext=mp4]+bestaudio/best[ext=mp4]/best',
'https://www.youtube.com/playlist?list=PLHTh1InhhwT4TJaHBVWzvBOYhp27UO7mI']

\xa0 is better known as U+00A0, or No-Break Space. Why are you using that instead of regular space character?

\xa0 is better known as U+00A0, or No-Break Space. Why are you using that instead of regular space character?

As you can in see in the command line:
# youtube-dl --download-archive archive.txt -v -f 'bestvideo[ext=mp4]+bestaudio/best[ext=mp4]/best' https://www.youtube.com/playlist\?list\=PLHTh1InhhwT4TJaHBVWzvBOYhp27UO7mI
there is a regular space character between the -f flag and the argument.

As you can in see in the command line

Is this a joke? Visually, Space (U+0020) and no break space (U+00A0) are identical.

Sorry, you are right, that is the result of copy-paste from the man youtube-dl:
# Download best mp4 format available or any other best if no mp4 available
$ youtube-dl -f 'bestvideo[ext=mp4]+bestaudio[ext=m4a]/best[ext=mp4]/best'

There is that special character used instead of regular spaces.

Yes, thats fine for documentation, but not fine for actual use. I would suggest try again with actual space character. In addition, despite different error message, it appears to me to be same problem as other issue. So I would recommend install patch from other issue, and try command again.

I thought the youtube-dl should handle connection timeout issues, it has some special parameters for that. Am I wrong?

Here is a quote, from you, from the other issue:
panic: Head "https://rr6---sn-gvnuxaxjvh-c35z.googlevideo.com/videoplayback?expire=...": net/http: TLS handshake timeout

So regardless of any current timeout handling, I think its reasonable to request apply patch from other issue, given the circumstance.

Ok, I'll try the patch.
Anyway, the first issue is happened due to invalid TLS handshake, there is no valid connection. Here is a valid connection but at some point a request is failed with the connection timeout error:
/usr/local/lib/python3.9/urllib/request.py:
            try:
                h.request(req.get_method(), req.selector, req.data, headers,
                          encode_chunked=req.has_header('Transfer-encoding'))
            except OSError as err: # timeout error
                raise URLError(err)

I've moved to the yt-dlp fork, it works better for me. Thank you for your help.

... youtube-dl should handle connection timeout issues, it has some special parameters for that. Am I wrong?

The timeout for connecting to a URL is meant to be 10 minutes or whatever you specify in --socket-timeout. IMO if your system is taking 10 minutes to reach a website you have worse problems than yt-dl, but there are always special cases.


[FLINK-4816] [checkpoints] Executions failed from "DEPLOYING" should retain restored checkpoint information

What is the purpose of the change
This PR is base on #3478 and added some improvements.
Brief change log

Rebased #3478 to the latest master branch.
Checked if CheckpointCoordinator is exist.
Added corresponding tests.

Verifying this change

Updated tests in CheckpointCoordinatorTest and ExecutionVertexDeploymentTest.
Added a new test in ExecutionVertexDeploymentTest for deploying failed after restoring.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: don't know
The runtime per-record code paths (performance sensitive): don't know
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: yes

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not documented

Hi @StephanEwen @ramkrish86
I would appreciate it if you could review this PR in your free time. Thank you.

Hi @StephanEwen
Do you have some time to review this PR? Or who can I ask for help if you are too busy? Thank you.


Xcode 15.4 iOS version 13 or higher

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.

Here is the diff that solved my problem:
diff --git a/node_modules/react-native-keyboard-controller/ios/delegates/KCTextInputCompositeDelegate.swift b/node_modules/react-native-keyboard-controller/ios/delegates/KCTextInputCompositeDelegate.swift
index 3c4a609..d9405fc 100644
--- a/node_modules/react-native-keyboard-controller/ios/delegates/KCTextInputCompositeDelegate.swift
+++ b/node_modules/react-native-keyboard-controller/ios/delegates/KCTextInputCompositeDelegate.swift
@@ -93,7 +93,11 @@ class KCTextInputCompositeDelegate: NSObject, UITextViewDelegate, UITextFieldDel
   // MARK: UITextFieldDelegate

   func textFieldDidChangeSelection(_ textField: UITextField) {
-    textFieldDelegate?.textFieldDidChangeSelection?(textField)
+      if #available(iOS 13.0, *) {
+          textFieldDelegate?.textFieldDidChangeSelection?(textField)
+      } else {
+          // Fallback on earlier versions
+      }
     updateSelectionPosition(textInput: textField)
   }

This issue body was partially generated by patch-package.

Hey @imamrobani 👋
Thank you for the report. May I ask you which RN version you are suing and which deployment target is set in XCode and which platform :ios is defined in Podfile?

@imamrobani and may I ask you to check if https://github.com/kirillzyusko/react-native-keyboard-controller/pull/460 fixes the problem?
Basically entire handler is available only for iOS 13+, so it makes sense just mark entire method with @avaialble annotation 👀

Hey @imamrobani 👋
Thank you for the report. May I ask you which RN version you are suing and which deployment target is set in XCode and which platform :ios is defined in Podfile?

I already define 13.0 and try 13.5 but still not working

@imamrobani okay, thank you 🙏
Does the code from my PR fixes compilation errors for you?

I generated a project with RM 0.72.14 and confirm the error is present.
With my PR the issue is gone - I tested on iOS 17.5 and handler gets fired (so it works as expected for newer iOS versions). I'm going to merge my PR - the issue will be automatically closed.
Thank you for the report and proposed solution ❤

@imamrobani okay, thank you 🙏
Does the code from my PR fixes compilation errors for you?

yes, thank you for helping


Question: Nesting dialog

Is there any reason why dialog_begin and dialog_end couldn't be
{
  type: "dialog",
  lines: [
    { character: "Jen", line: "Nice to meet you" },
    ...
  ]
}

Seems like it'd make parsing a bit easier.  I'm using this in React, and needing a way to replace string matches with react components and finding these tokens a little hard to work with.
If it's helpful or wanted I can help code

Heya! Apologies for the late response, but I've been thinking on your question while offline.
Version 1.0.0 of this library is a fork of Matt Daly's Fountain.js and originally was just a pet project for me to try out a Typescript conversion. So, to answer your question, that's how Matt designed the token schema, so I preserved it for those who wanted to continue to use his library.
As these things go, it's obviously grown somewhat beyond that original intention and perhaps it's time to modernize. To do this would require a major bump (version 2.0.0).
I'm for it and was considering, if going for a major, to also implement an options object akin to marked.js.
let output = fountain.parse('string', {
    extensions: true,
    tokens: true
});

My thinking here is, it opens the door for additional options, like expanding rendering, or adding helpful additions that may b out of Fountain's intended spec such as parsing extensions like (O.S.) or V.O..
Regarding token structure, I'd like to be thoughtful here and think about how to organize blocks and tokens, perhaps taking some notes from CommonMark on organization, etc.
Here's an initial example:
{
type: 'script',
tokens: [
...
  { type: 'action', text: 'Jen runs into directly into AMELIA.</br>Coffee goes everywhere.'}
  // a `dual-dialogue` block would hold two dialogue blocks, etc.
  {
    type: 'dialogue',
    tokens: [
      { type: 'character', text: 'Jen' },
      { type: 'speech', text: 'Nice --',
      { type: 'parenthetical', text: '(through gasps of air)'},
      { type: 'speech', text: 'to meet you...'},
    ]
  }
...
]}

This keeps the structure somewhat similar to how the parser works now, like I'm not putting action or speech into a block like you could, but it creates a more recognizable AST that (hopefully) addresses your question.
I'd like to take a crack at it initially and flesh out the idea, but would love initial input from you or past contributors like @zenibako and @rezonant as well as would like reviews of the PR before push.


RuntimeError: Expected object of type torch.cuda.FloatTensor but found type torch.FloatTensor for argument #4 'mat1'

When I try to run the notebook Auxiliary Deep Generative Model, at the cell:
from sesutils import onehot
model.eval()
z = Variable(torch.randn(16, 32))
# Generate a batch of 5s
y = Variable(onehot(10)(5).repeat(16, 1))
x_mu = model.sample(z, y)

I get the error:
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-6-e78d4b83d3dc> in <module>()
      7 y = Variable(onehot(10)(5).repeat(16, 1))
      8
----> 9 x_mu = model.sample(z, y)
~/test/semi-supervised-pytorch-ucsky/semi-supervised/models/dgm.py in sample(self, z, y)
     75         """
     76         y = y.float()
---> 77         x = self.decoder(torch.cat([z, y], dim=1))
     78         return x
     79
/usr/local/lib/python3.5/dist-packages/torch/nn/modules/module.py in __call__(self, *input, **kwargs)
    489             result = self._slow_forward(*input, **kwargs)
    490         else:
--> 491             result = self.forward(*input, **kwargs)
   492         for hook in self._forward_hooks.values():
    493             hook_result = hook(self, input, result)

~/test/semi-supervised-pytorch-ucsky/semi-supervised/models/vae.py in forward(self, x)
     86     def forward(self, x):
     87         for layer in self.hidden:
---> 88             x = F.relu(layer(x))
     89         return self.output_activation(self.reconstruction(x))
     90
/usr/local/lib/python3.5/dist-packages/torch/nn/modules/module.py in __call__(self, *input, **kwargs)
    489             result = self._slow_forward(*input, **kwargs)
    490         else:
--> 491             result = self.forward(*input, **kwargs)
    492         for hook in self._forward_hooks.values():
    493             hook_result = hook(self, input, result)
/usr/local/lib/python3.5/dist-packages/torch/nn/modules/linear.py in forward(self, input)
     53
     54     def forward(self, input):
---> 55         return F.linear(input, self.weight, self.bias)
     56
     57     def extra_repr(self):
/usr/local/lib/python3.5/dist-packages/torch/nn/functional.py in linear(input, weight, bias)
    990     if input.dim() == 2 and bias is not None:
    991         # fused op is marginally faster
--> 992         return torch.addmm(bias, input, weight.t())
    993
    994     output = input.matmul(weight.t())
RuntimeError: Expected object of type torch.cuda.FloatTensor but found type torch.FloatTensor for argument #4 'mat1'

It looks like your model is located on the GPU, meaning that you have called model = model.cuda(), however the variables y and z you have created are not on the GPU, so you need to call x, y = x.cuda(), y.cuda().


3D joint locations for mpjpe calculation on custom video using demo script

Hello! I run the demo script on the custom videos and I get res.pk file, which has these keys from the code:
res_keys = [
    'pred_uvd',
    'pred_xyz_17',
    'pred_xyz_29',
    'pred_xyz_24_struct',
    'pred_scores',
    'pred_camera',
    # 'f',
    'pred_betas',
    'pred_thetas',
    'pred_phi',
    'pred_cam_root',
    # 'features',
    'transl',
    'transl_camsys',
    'bbox',
    'height',
    'width',
    'img_path'
]

I have some GT 3D joint locations. For MPJPE calculation, can I get the 3D Joint locations directly from this demo script? pred_thetas are 3D joint rotations, do I need to write the code for FK or can I directly get the root relative 3D joint locations?

There are some different formats of keypoint representation. pred_xyz_17is the keypoints in Human3.6m format obtained by FK, pred_xyz_24_struct is the keypoints in SMPL format obtained by FK, and pred_xyz_29 is the keypoints directly predicted by the backbone network.