hub clone USER/REPO is not doing anything

When I run hub clone styled-components/vscode-styled-components, it simply does not do anything, doesn't clone the repo, neither emits any message to the console. I don't know why, because it doesn't throw any errors, logs or anything, it just doesn't do anything.
If I try to clone a repo using the syntax hub clone REPO, without the USER, it clones fine. Same if I use the whole URL hub clone https://github.com/styled-components/vscode-styled-components.git.
Weird thing, if I clone using the URL, and then clone using the USER/REPO syntax (hub clone styled-components/vscode-styled-components), it says fatal: destination path 'vscode-styled-components' already exists and is not an empty directory., so I imagine that when I reproduce the bug, hub is trying to do something, but failing silently
Any ideas why this is happening? Or where I can look for clues (logs or anything)?

Hmm that is indeed strange. Clues to start with:

hub version
your OS information
hub --noop clone USER/REPO
HUB_VERBOSE=1 hub clone USER/REPO

hub version

$ hub version
git version 2.17.1
hub version 2.5.1

your OS information - I'm using Windows 10, using WSL (Ubuntu 18.04, zsh 5.4.2 + prezto)

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:        18.04
Codename:       bionic

$ zsh --version
zsh 5.4.2 (x86_64-ubuntu-linux-gnu)

hub --noop clone USER/REPO

$ hub --noop clone styled-components/vscode-styled-components
git clone https://github.com/styled-components/vscode-styled-components.git

$ hub --noop clone https://github.com/styled-components/vscode-styled-components.git
git clone https://github.com/styled-components/vscode-styled-components.git

HUB_VERBOSE=1 hub clone USER/REPO (note: you don't have to paste us this output fully, but it might help you debug): Didn't find anything strange with the output 🤔

HUB_VERBOSE=1 hub clone styled-components/vscode-styled-components
> GET https://api.github.com/repos/styled-components/vscode-styled-components
> Authorization: token [REDACTED]
> Accept: application/vnd.github.v3+json;charset=utf-8
< HTTP 200
{"id":73508125,"node_id":"MDEwOlJlcG9zaXRvcnk3MzUwODEyNQ==","name":"vscode-styled-components","full_name":"styled-components/vscode-styled-components","owner":{"login":"styled-components","id":20658825,"node_id":"MDEyOk9yZ2FuaXphdGlvbjIwNjU4ODI1","avatar_url":"https://avatars2.githubusercontent.com/u/20658825?v=4","gravatar_id":"","url":"https://api.github.com/users/styled-components","html_url":"https://github.com/styled-components","followers_url":"https://api.github.com/users/styled-components/followers","following_url":"https://api.github.com/users/styled-components/following{/other_user}","gists_url":"https://api.github.com/users/styled-components/gists{/gist_id}","starred_url":"https://api.github.com/users/styled-components/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/styled-components/subscriptions","organizations_url":"https://api.github.com/users/styled-components/orgs","repos_url":"https://api.github.com/users/styled-components/repos","events_url":"https://api.github.com/users/styled-components/events{/privacy}","received_events_url":"https://api.github.com/users/styled-components/received_events","type":"Organization","site_admin":false},"private":false,"html_url":"https://github.com/styled-components/vscode-styled-components","description":"Syntax highlighting for styled-components","fork":false,"url":"https://api.github.com/repos/styled-components/vscode-styled-components","forks_url":"https://api.github.com/repos/styled-components/vscode-styled-components/forks","keys_url":"https://api.github.com/repos/styled-components/vscode-styled-components/keys{/key_id}","collaborators_url":"https://api.github.com/repos/styled-components/vscode-styled-components/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/styled-components/vscode-styled-components/teams","hooks_url":"https://api.github.com/repos/styled-components/vscode-styled-components/hooks","issue_events_url":"https://api.github.com/repos/styled-components/vscode-styled-components/issues/events{/number}","events_url":"https://api.github.com/repos/styled-components/vscode-styled-components/events","assignees_url":"https://api.github.com/repos/styled-components/vscode-styled-components/assignees{/user}","branches_url":"https://api.github.com/repos/styled-components/vscode-styled-components/branches{/branch}","tags_url":"https://api.github.com/repos/styled-components/vscode-styled-components/tags","blobs_url":"https://api.github.com/repos/styled-components/vscode-styled-components/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/styled-components/vscode-styled-components/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/styled-components/vscode-styled-components/git/refs{/sha}","trees_url":"https://api.github.com/repos/styled-components/vscode-styled-components/git/trees{/sha}","statuses_url":"https://api.github.com/repos/styled-components/vscode-styled-components/statuses/{sha}","languages_url":"https://api.github.com/repos/styled-components/vscode-styled-components/languages","stargazers_url":"https://api.github.com/repos/styled-components/vscode-styled-components/stargazers","contributors_url":"https://api.github.com/repos/styled-components/vscode-styled-components/contributors","subscribers_url":"https://api.github.com/repos/styled-components/vscode-styled-components/subscribers","subscription_url":"https://api.github.com/repos/styled-components/vscode-styled-components/subscription","commits_url":"https://api.github.com/repos/styled-components/vscode-styled-components/commits{/sha}","git_commits_url":"https://api.github.com/repos/styled-components/vscode-styled-components/git/commits{/sha}","comments_url":"https://api.github.com/repos/styled-components/vscode-styled-components/comments{/number}","issue_comment_url":"https://api.github.com/repos/styled-components/vscode-styled-components/issues/comments{/number}","contents_url":"https://api.github.com/repos/styled-components/vscode-styled-components/contents/{+path}","compare_url":"https://api.github.com/repos/styled-components/vscode-styled-components/compare/{base}...{head}","merges_url":"https://api.github.com/repos/styled-components/vscode-styled-components/merges","archive_url":"https://api.github.com/repos/styled-components/vscode-styled-components/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/styled-components/vscode-styled-components/downloads","issues_url":"https://api.github.com/repos/styled-components/vscode-styled-components/issues{/number}","pulls_url":"https://api.github.com/repos/styled-components/vscode-styled-components/pulls{/number}","milestones_url":"https://api.github.com/repos/styled-components/vscode-styled-components/milestones{/number}","notifications_url":"https://api.github.com/repos/styled-components/vscode-styled-components/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/styled-components/vscode-styled-components/labels{/name}","releases_url":"https://api.github.com/repos/styled-components/vscode-styled-components/releases{/id}","deployments_url":"https://api.github.com/repos/styled-components/vscode-styled-components/deployments","created_at":"2016-11-11T20:11:43Z","updated_at":"2018-09-12T12:15:00Z","pushed_at":"2018-09-12T01:26:03Z","git_url":"git://github.com/styled-components/vscode-styled-components.git","ssh_url":"git@github.com:styled-components/vscode-styled-components.git","clone_url":"https://github.com/styled-components/vscode-styled-components.git","svn_url":"https://github.com/styled-components/vscode-styled-components","homepage":"","size":196,"stargazers_count":306,"watchers_count":306,"language":"JavaScript","has_issues":true,"has_projects":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":45,"mirror_url":null,"archived":false,"open_issues_count":35,"license":{"key":"mit","name":"MIT License","spdx_id":"MIT","url":"https://api.github.com/licenses/mit","node_id":"MDc6TGljZW5zZTEz"},"forks":45,"open_issues":35,"watchers":306,"default_branch":"master","permissions":{"admin":false,"push":false,"pull":true},"organization":{"login":"styled-components","id":20658825,"node_id":"MDEyOk9yZ2FuaXphdGlvbjIwNjU4ODI1","avatar_url":"https://avatars2.githubusercontent.com/u/20658825?v=4","gravatar_id":"","url":"https://api.github.com/users/styled-components","html_url":"https://github.com/styled-components","followers_url":"https://api.github.com/users/styled-components/followers","following_url":"https://api.github.com/users/styled-components/following{/other_user}","gists_url":"https://api.github.com/users/styled-components/gists{/gist_id}","starred_url":"https://api.github.com/users/styled-components/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/styled-components/subscriptions","organizations_url":"https://api.github.com/users/styled-components/orgs","repos_url":"https://api.github.com/users/styled-components/repos","events_url":"https://api.github.com/users/styled-components/events{/privacy}","received_events_url":"https://api.github.com/users/styled-components/received_events","type":"Organization","site_admin":false},"network_count":45,"subscribers_count":11}
$ git config hub.protocol
$ git config hub.protocol
$ git clone https://github.com/styled-components/vscode-styled-components.git

Weirder thing: It is apparently randomly working 🤷♂ Tried 4 times the same command, the 4th it yielded
HUB_VERBOSE=1 hub clone styled-components/vscode-styled-components
> GET https://api.github.com/repos/styled-components/vscode-styled-components
> Authorization: token [REDACTED]
> Accept: application/vnd.github.v3+json;charset=utf-8
< HTTP 200
{"id":73508125,"node_id":"MDEwOlJlcG9zaXRvcnk3MzUwODEyNQ==","name":"vscode-styled-components","full_name":"styled-components/vscode-styled-components","owner":{"login":"styled-components","id":20658825,"node_id":"MDEyOk9yZ2FuaXphdGlvbjIwNjU4ODI1","avatar_url":"https://avatars2.githubusercontent.com/u/20658825?v=4","gravatar_id":"","url":"https://api.github.com/users/styled-components","html_url":"https://github.com/styled-components","followers_url":"https://api.github.com/users/styled-components/followers","following_url":"https://api.github.com/users/styled-components/following{/other_user}","gists_url":"https://api.github.com/users/styled-components/gists{/gist_id}","starred_url":"https://api.github.com/users/styled-components/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/styled-components/subscriptions","organizations_url":"https://api.github.com/users/styled-components/orgs","repos_url":"https://api.github.com/users/styled-components/repos","events_url":"https://api.github.com/users/styled-components/events{/privacy}","received_events_url":"https://api.github.com/users/styled-components/received_events","type":"Organization","site_admin":false},"private":false,"html_url":"https://github.com/styled-components/vscode-styled-components","description":"Syntax highlighting for styled-components","fork":false,"url":"https://api.github.com/repos/styled-components/vscode-styled-components","forks_url":"https://api.github.com/repos/styled-components/vscode-styled-components/forks","keys_url":"https://api.github.com/repos/styled-components/vscode-styled-components/keys{/key_id}","collaborators_url":"https://api.github.com/repos/styled-components/vscode-styled-components/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/styled-components/vscode-styled-components/teams","hooks_url":"https://api.github.com/repos/styled-components/vscode-styled-components/hooks","issue_events_url":"https://api.github.com/repos/styled-components/vscode-styled-components/issues/events{/number}","events_url":"https://api.github.com/repos/styled-components/vscode-styled-components/events","assignees_url":"https://api.github.com/repos/styled-components/vscode-styled-components/assignees{/user}","branches_url":"https://api.github.com/repos/styled-components/vscode-styled-components/branches{/branch}","tags_url":"https://api.github.com/repos/styled-components/vscode-styled-components/tags","blobs_url":"https://api.github.com/repos/styled-components/vscode-styled-components/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/styled-components/vscode-styled-components/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/styled-components/vscode-styled-components/git/refs{/sha}","trees_url":"https://api.github.com/repos/styled-components/vscode-styled-components/git/trees{/sha}","statuses_url":"https://api.github.com/repos/styled-components/vscode-styled-components/statuses/{sha}","languages_url":"https://api.github.com/repos/styled-components/vscode-styled-components/languages","stargazers_url":"https://api.github.com/repos/styled-components/vscode-styled-components/stargazers","contributors_url":"https://api.github.com/repos/styled-components/vscode-styled-components/contributors","subscribers_url":"https://api.github.com/repos/styled-components/vscode-styled-components/subscribers","subscription_url":"https://api.github.com/repos/styled-components/vscode-styled-components/subscription","commits_url":"https://api.github.com/repos/styled-components/vscode-styled-components/commits{/sha}","git_commits_url":"https://api.github.com/repos/styled-components/vscode-styled-components/git/commits{/sha}","comments_url":"https://api.github.com/repos/styled-components/vscode-styled-components/comments{/number}","issue_comment_url":"https://api.github.com/repos/styled-components/vscode-styled-components/issues/comments{/number}","contents_url":"https://api.github.com/repos/styled-components/vscode-styled-components/contents/{+path}","compare_url":"https://api.github.com/repos/styled-components/vscode-styled-components/compare/{base}...{head}","merges_url":"https://api.github.com/repos/styled-components/vscode-styled-components/merges","archive_url":"https://api.github.com/repos/styled-components/vscode-styled-components/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/styled-components/vscode-styled-components/downloads","issues_url":"https://api.github.com/repos/styled-components/vscode-styled-components/issues{/number}","pulls_url":"https://api.github.com/repos/styled-components/vscode-styled-components/pulls{/number}","milestones_url":"https://api.github.com/repos/styled-components/vscode-styled-components/milestones{/number}","notifications_url":"https://api.github.com/repos/styled-components/vscode-styled-components/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/styled-components/vscode-styled-components/labels{/name}","releases_url":"https://api.github.com/repos/styled-components/vscode-styled-components/releases{/id}","deployments_url":"https://api.github.com/repos/styled-components/vscode-styled-components/deployments","created_at":"2016-11-11T20:11:43Z","updated_at":"2018-09-12T12:15:00Z","pushed_at":"2018-09-12T01:26:03Z","git_url":"git://github.com/styled-components/vscode-styled-components.git","ssh_url":"git@github.com:styled-components/vscode-styled-components.git","clone_url":"https://github.com/styled-components/vscode-styled-components.git","svn_url":"https://github.com/styled-components/vscode-styled-components","homepage":"","size":196,"stargazers_count":306,"watchers_count":306,"language":"JavaScript","has_issues":true,"has_projects":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":45,"mirror_url":null,"archived":false,"open_issues_count":35,"license":{"key":"mit","name":"MIT License","spdx_id":"MIT","url":"https://api.github.com/licenses/mit","node_id":"MDc6TGljZW5zZTEz"},"forks":45,"open_issues":35,"watchers":306,"default_branch":"master","permissions":{"admin":false,"push":false,"pull":true},"organization":{"login":"styled-components","id":20658825,"node_id":"MDEyOk9yZ2FuaXphdGlvbjIwNjU4ODI1","avatar_url":"https://avatars2.githubusercontent.com/u/20658825?v=4","gravatar_id":"","url":"https://api.github.com/users/styled-components","html_url":"https://github.com/styled-components","followers_url":"https://api.github.com/users/styled-components/followers","following_url":"https://api.github.com/users/styled-components/following{/other_user}","gists_url":"https://api.github.com/users/styled-components/gists{/gist_id}","starred_url":"https://api.github.com/users/styled-components/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/styled-components/subscriptions","organizations_url":"https://api.github.com/users/styled-components/orgs","repos_url":"https://api.github.com/users/styled-components/repos","events_url":"https://api.github.com/users/styled-components/events{/privacy}","received_events_url":"https://api.github.com/users/styled-components/received_events","type":"Organization","site_admin":false},"network_count":45,"subscribers_count":11}
$ git config hub.protocol
$ git config hub.protocol
$ git clone https://github.com/styled-components/vscode-styled-components.git
Cloning into 'vscode-styled-components'...
remote: Counting objects: 386, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 386 (delta 0), reused 1 (delta 0), pack-reused 382
Receiving objects: 100% (386/386), 197.53 KiB | 456.00 KiB/s, done.
Resolving deltas: 100% (221/221), done.

It has the exact same output of the command that did not work, aside from the git actual output (last 6 lines)
if I do
$ rm -rf vscode-styled-components
$ hub clone styled-components/vscode-styled-components
$

Again it doesn't do anything

Thank you for sharing extra information!
Can you reproduce the same if you use hub on Windows directly (either cmd.exe or PowerShell) and not through WSL?
Does this ever happen if you try running git clone https://github.com/styled-components/vscode-styled-components.git repeatedly inside WSL (skipping hub)? Trying to figure out whether the failure happens in hub executable or in the git one.

using cmd.exe, that does not happen, and running git clone https://github.com/styled-components/vscode-styled-components.git (on WSL) always works

Thank you for checking! This sounds like it might be a bug in WSL, or at least with Go programs running under it. I'm not a user of either Windows nor WSL, so I don't think I'll have time to debug this soon. But if someone wants to take a stab sprinkling some debugging statements in there, this is a good place to start: https://github.com/github/hub/blob/de684cb613c47572cc9ec90d4fd73eef80aef09c/cmd/cmd.go#L55-L63


automate-symbolication: Option to fail silently?

I'm trying to use automate-symbolication, or automatically uploading source maps for a react native project. However, looks like failing to upload to bugsnag (due to timeouts or spotty internet) is causing the entire build step to fail.
I would like to know, or request, if it would be possible to only upload source maps if a "production" build is being generated (that is, for iOS only do this when archiving, and for Android only when running ./gradlew bundleProdRelease). Otherwise, this is very inconvenient since installing "production" builds into the device directly from XCode or ADB will also trigger a source map upload.

We just upgraded to use automatic symbolication in our RN project and would like this option, too. Otherwise, we're going to be forced to revert to manual uploads.
Side note: there's a bug in RN's bundle step where passing a source map file path with any whitespace causes the source map to NOT be generated, FYI in case anyone runs into silent failures. There's an open issue about it here.

We just upgraded to use automatic symbolication in our RN project and would like this option, too. Otherwise, we're going to be forced to revert to manual uploads.
Side note: there's a bug in RN's bundle step where passing a source map file path with any whitespace causes the source map to NOT be generated, FYI in case anyone runs into silent failures. There's an open issue about it here.

Our CLI is currently designed to target all release builds as users may wish to check their Bugsnag integration locally on a release build that is not distributed.
If you wish to reduce the build targets with uploads enabled, we suggest the following customizations:
For Android, you can disable the plugin for these variants using the variantFilter API, which is described in our integration instructions. The variantFilter API could also be conditionally enabled through the use of environment variables if you only want to upload mapping files on CI, for example.
For iOS, you can add some logic to the build phase added by our CLI to skip the upload if not archiving:
if [ "$DEPLOYMENT_LOCATION" != "YES" ]; then
 echo "Skipping source map upload for developer build."
 exit 0
fi

There's also an ACTION environment variable that is build for builds and install when building for archive that could be used to condition the upload.

Our CLI is currently designed to target all release builds as users may wish to check their Bugsnag integration locally on a release build that is not distributed.
If you wish to reduce the build targets with uploads enabled, we suggest the following customizations:
For Android, you can disable the plugin for these variants using the variantFilter API, which is described in our integration instructions. The variantFilter API could also be conditionally enabled through the use of environment variables if you only want to upload mapping files on CI, for example.
For iOS, you can add some logic to the build phase added by our CLI to skip the upload if not archiving:
if [ "$DEPLOYMENT_LOCATION" != "YES" ]; then
 echo "Skipping source map upload for developer build."
 exit 0
fi

There's also an ACTION environment variable that is build for builds and install when building for archive that could be used to condition the upload.

@xander-jones  that's very helpful! Can you elaborate a bit more on the iOS implementation? I'm unsure what the DEPLOYMENT_LOCATION and ACTION variables are.
Basically, how do I know if it is a bundle/archive operation, or a "run/install" operation?

@xander-jones  that's very helpful! Can you elaborate a bit more on the iOS implementation? I'm unsure what the DEPLOYMENT_LOCATION and ACTION variables are.
Basically, how do I know if it is a bundle/archive operation, or a "run/install" operation?

Hey @cristianoccazinsp,

I'm unsure what the DEPLOYMENT_LOCATION and ACTION variables are.

These are environment variables which are generated by Xcode when you run a build. They can be accessed by the build phase scripts at build-time which will allow you to know what kind of build is happening. If ACTION is equal to build, it's a debug or release build, if it's set to install it's building for an archive.
Unfortunately, there's no particularly good reference for these environment variables from Apple as far as I know – other than this resource, which gives some examples for each of the exported environment variables.
You can output all of your environment variables in a build by adding a simple build phase script as follows to your Xcode build phases if you want to test out what the env variables look like for different build types:

Shell: /bin/sh
Script: export
Ensure "Show environment variables in build log" is selected.

what's the difference between the enabled and uploadReactNativeMappings flags?

bugsnag.uploadReactNativeMappings = false switches the JS sourcemap upload off.
bugsnag.enabled = false switches the whole plugin off, including source map uploading.

do I also need to set enabled if I'm using variant filters?

I'd recommend that you do set enabled to false for variants that you don't want Bugsnag to run on, just so that you don't have any assets uploading needlessly.

Hey @cristianoccazinsp,

I'm unsure what the DEPLOYMENT_LOCATION and ACTION variables are.

These are environment variables which are generated by Xcode when you run a build. They can be accessed by the build phase scripts at build-time which will allow you to know what kind of build is happening. If ACTION is equal to build, it's a debug or release build, if it's set to install it's building for an archive.
Unfortunately, there's no particularly good reference for these environment variables from Apple as far as I know – other than this resource, which gives some examples for each of the exported environment variables.
You can output all of your environment variables in a build by adding a simple build phase script as follows to your Xcode build phases if you want to test out what the env variables look like for different build types:

Shell: /bin/sh
Script: export
Ensure "Show environment variables in build log" is selected.

what's the difference between the enabled and uploadReactNativeMappings flags?

bugsnag.uploadReactNativeMappings = false switches the JS sourcemap upload off.
bugsnag.enabled = false switches the whole plugin off, including source map uploading.

do I also need to set enabled if I'm using variant filters?

I'd recommend that you do set enabled to false for variants that you don't want Bugsnag to run on, just so that you don't have any assets uploading needlessly.

@cristianoccazinsp, a little follow-up on this! There's a great reference document here for the ACTION and DEPLOYMENT_LOCATION variables.
ACTION

Identifies the type of build to perform on the target.

build: Build the product and place it in the product build directory (CONFIGURATION_BUILD_DIR).
clean: Remove the product and build files in the product build directory (CONFIGURATION_BUILD_DIR) and the intermediate build files directory (CONFIGURATION_TEMP_DIR).
install: Build the product and place it in its installation destination (INSTALL_PATH).
installhdrs: Copy the product’s public and private header files into the public headers directory (PUBLIC_HEADERS_FOLDER_PATH) and the private headers directory (PRIVATE_HEADERS_FOLDER_PATH), respectively.
installsrc: Copy the target’s source files into the project directory (SRCROOT).

DEPLOYMENT_LOCATION

Boolean value. Specifies whether product files are placed in the installation (specified by DSTROOT) or the build directory (identified by SYMROOT).

YES: Product files are placed in $DSTROOT.
NO: Product files are placed in $SYMROOT.

@cristianoccazinsp, a little follow-up on this! There's a great reference document here for the ACTION and DEPLOYMENT_LOCATION variables.
ACTION

Identifies the type of build to perform on the target.

build: Build the product and place it in the product build directory (CONFIGURATION_BUILD_DIR).
clean: Remove the product and build files in the product build directory (CONFIGURATION_BUILD_DIR) and the intermediate build files directory (CONFIGURATION_TEMP_DIR).
install: Build the product and place it in its installation destination (INSTALL_PATH).
installhdrs: Copy the product’s public and private header files into the public headers directory (PUBLIC_HEADERS_FOLDER_PATH) and the private headers directory (PRIVATE_HEADERS_FOLDER_PATH), respectively.
installsrc: Copy the target’s source files into the project directory (SRCROOT).

DEPLOYMENT_LOCATION

Boolean value. Specifies whether product files are placed in the installation (specified by DSTROOT) or the build directory (identified by SYMROOT).

YES: Product files are placed in $DSTROOT.
NO: Product files are placed in $SYMROOT.

It says it is a "retired document", but I guess the info is still valid.  Anyways, with your first response I believe I got it to work as expected now.  Thanks!

It says it is a "retired document", but I guess the info is still valid.  Anyways, with your first response I believe I got it to work as expected now.  Thanks!

Closing this as the above advice should allow users of the CLI to configure the uploads to only happen on builds where they do require the source maps to be uploaded.


Unable to cast object of type 'XxxxxViewModel' to type 'Template10.Services.NavigationService.INavigable'.

Hello,
In the latest release (1.1.5) I cannot use a view model without INavigable. I don't want to implement INavigable if I don't need to ...
Here is the stacktrace:
   at Template10.Services.NavigationService.NavigationService.ResolveForPage(Page page)
   at Template10.Services.NavigationService.NavigationService.<NavigateToAsync>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Template10.Services.NavigationService.NavigationService.<>c__DisplayClass20_0.<<-ctor>b__2>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Template10.Common.DispatcherWrapper.<DispatchAsync>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Template10.Services.NavigationService.NavigationService.<<-ctor>b__20_1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
   at System.Threading.WinRTSynchronizationContext.Invoker.InvokeCore()

Regards,
Adrien.

Just inherit your ViewModel from ViewModelBase (that in turns implements INavigable).

I don't want to either ... Why sould I ?

This was not an intended requirement. T10 will not require INav. Let me look into it.

Exactly how is it preventing a standard view-model?

You were right. I found the error. Fixed it. When I update NuGet today you will get the fix, too. Thanks for reporting this. We never want to force a developer to implement INav.
Was doing this explicit conversion
return (INavigable)page.DataContext;

Should have been doing this implicit conversion
return page.DataContext as INavigable;


Proposal to add new terms ac:freqLow and ac:freqHigh

Term Name: ac:freqLow
Term Name: ac:freqHigh
Type: rdf:Property
Label: Lower frequency bound
Label: Upper frequency bound
Required: No
Repeatable: No
Definition: The lowest frequency of the phenomena reflected in the multimedia item.
Definition: The highest frequency of the phenomena reflected in the multimedia item.
Usage: Numeric value in Hertz (Hz)
Notes: These terms refer to the sound events depicted and not to the constraints of the recording medium, so are in principle independent from sampleRate. If dwc:scientificName is specified, these frequency bounds refer to the sounds of the species given in the dwc:scientificName throughout the whole recording. Although many users will specify both freqLow and freqHigh, it is permitted to specify just one or the other, for example if only one of the bounds is discernible.
Justification for the term addition: “Time-frequency boxes” are a common approach for labelling events within bioacoustic sound recordings. Audio recordings can be used to explore and validate taxon identity for insect sounds. For many insect sounds (e.g. extended calling or chorusing), frequency bounds can be much clearer than time bounds. Thus, in a soundscape recording, it can be desirable to associate a taxon label with some sub-region of the audio, but as frequency bounds without time bounds. In search queries, it can often be desirable to target (or exclude) animal sounds that occur within specific frequency ranges.
Proposed by myself and @edwbaker

Minor correction changing rdfs:Property to rdf:Property

Corrected capitalization of "hertz"

Approved in Executive decision 32. Incorporated in rs.tdwg.org release 2020-10-13.


fix: retrieve with the appropriate operation names

What does this PR solve?
If 'graphql-default' is specified in the Hasura naming convention setting, the GraphQL field used for the request and response will be camelCase.
refs https://hasura.io/docs/latest/schema/postgres/naming-convention/
To support this in the Hasura provider, the option { namingConvention: 'graphql-convention' } can be specified.
As a behaviour when this option was specified, the query was constructed in camelCase at the time of the request, but when referencing the required data from the response, some parts of the function were obtained in snake-case.
This PR fixes this, so that when using graphql-convention, there are no errors in data retrieval.
The target functions are

create
createMany
getList.
getOne
deleteMany
deleteOne
updateMany
updateOne

Test cases were available for these functions when graphql-convention option was specified, but the mock response was in camelCase, which was not noticed in the test. So the mock response has been changed to be camelCase along with the logic.
As an example, the getList has been modified so that the response is as follows
{
    "data": {
        "posts":[
            {"id":"bac2ef0a-899f-4694-84ef-b9c6fe4dc2b7","title":"asdfasdfsadf"},
            {"id":"b19c9bd4-dff9-4ecf-acfe-aea2c4c9ec41","title":"Agent Berkshire Rustic"},
            {"id":"cddd4ced-651d-4039-abe0-2a9dffbc8c82","title":"Focus group Human Sleek"},
            {"id":"c82c71c5-0f0b-4042-b9a3-db977fe28a83","title":"E-business alarm Bedfordshire"},
            {"id":"ecd7aa21-19f4-46c9-bc3e-227dcd0807fd","title":"E-business alarm"},
            {"id":"75dbf808-6dc0-4b7b-bd1a-f1f381ee0e4c","title":"Boliviano Mvdol B2B Saint Helena Pound"},
            {"id":"7783567e-22f2-4f54-bda2-bc8524a3a9c2","title":"National Granite motivating"},
            {"id":"88a479ec-296d-48a4-9c57-7b48048a8067","title":"Haptic Togo online852"},
            {"id":"789887b3-ef35-4c70-9f1d-577aad8296b9","title":"Table Industrial Checking Account981"},
            {"id":"9d797062-cbaf-4a17-812c-51476aff4442","title":"Personal Loan Account synthesizing Research640"}
        ],
-       "posts_aggregate": {
+       "postsAggregate": {
            "aggregate" : {"count" : 25}
        }
    }
}

Test plan (required)
I've tested all 1 package, hasura, touched by changes.
Closing issues
closes #4574
Self Check before Merge
Please check all items below before review.

[x] Corresponding issues are created/updated or not needed
[x] Docs are updated/provided or not needed
[x] Examples are updated/provided or not needed
[x] TypeScript definitions are updated/provided or not needed
[x] Tests are updated/provided or not needed
[x] Changesets are provided or not needed

Thank you for the contribution @IkumaTadokoro! We'll review it soon and merge 🚀

Hello @IkumaTadokoro thanks for the PR! We'll review it soon.


Tensorflow 0.12 on Windows - TypeError: init() got an unexpected keyword argument 'dense_shape' running example

I downloaded the latest Windows native version of Tensorflow and having problems running some examples. I have Windows 10 (TF 0.12) with python 3.5.2.
The issue is with keyword dense_shape while running the wide_n_deep_tutorial shipped with the package. I pulled the latest version of TF as well but still didn't resolve the problem:
TypeError: init() got an unexpected keyword argument 'dense_shape'
Specifically, the issue is in the following section:
categorical_cols = {
k: tf.SparseTensor(
indices=[[i, 0] for i in range(df[k].size)],
values=df[k].values,
dense_shape=[df[k].size, 1])
for k in CATEGORICAL_COLUMNS}
Per documentation SparseTensor does not seem to understand dense_shape but IndexedSlices does. But I would like examples to work as is, without modification.
Cannot comment whether this happens on Unix also. Any ideas on how to resolve? Thanks!

The tf.SparseTensor API has changed between the 0.12 release and the git master. You should run the version of wide_n_deep_tutorial.py from the r0.12 branch when you have TensorFlow 0.12 installed:
https://github.com/tensorflow/tensorflow/blob/r0.12/tensorflow/examples/learn/wide_n_deep_tutorial.py

I'm closing this because it probably doesn't need a response... feel free to reopen if it still doesn't work.

Thanks, helped a lot.


Enable the ssa verifier in debug builds

Enable regalloc2's SSA verifier in debug builds to check for any outstanding reuse of virtual registers in def constraints. As fuzzing enables debug_assertions, this will enable the SSA verifier when fuzzing as well.

Would it make sense to enable the ssa verifier when enabling the regular regalloc verifier? That allows enabling it using the respective cranelift flag without enabling debug assertions.

Would it make sense to enable the ssa verifier when enabling the regular regalloc verifier? That allows enabling it using the respective cranelift flag without enabling debug assertions.

I'll have a look at this in a follow-up PR, but for now I'd like to start fuzzing as soon as possible.


Network/Disk Speed Monitoring

It's possible to add these characteristics right now and without the other complications mentioned in the other issues for the tool?

Why? How does this help? Task Manager is the tool you are looking for, I think.


[PIP-214][broker]Add broker level metrics statistics and expose to prometheus

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Currently, pulsar does not statistics broker level metrics, and all relevant metrics are 0 by default.
When the number of topic partitions reaches more than 100000 or even millions, and the topic level metrics are exposed (exposeTopicLevelMetricsInPrometheus=true), if you want to query the metrics of the broker dimension, you need to summarize all topics, and the performance becomes very poor, or even the results cannot be queried from the promethus. Common broker level metrics include:
pulsar_topics_count
pulsar_subscriptions_count
pulsar_producers_count
pulsar_consumers_count
pulsar_rate_in
pulsar_rate_out
pulsar_throughput_in
pulsar_throughput_out
pulsar_storage_size
pulsar_storage_logical_size
pulsar_storage_write_rate
pulsar_storage_read_rate
pulsar_msg_backlog

We need to statistics the metrics of the broker dimension and expose them to prometheus to improve the performance of the monitoring  of the broker dimension. Modify the original metrics name as follows:
pulsar_broker_topics_count
pulsar_broker_subscriptions_count
pulsar_broker_producers_count
pulsar_broker_consumers_count
pulsar_broker_rate_in
pulsar_broker_rate_out
pulsar_broker_throughput_in
pulsar_broker_throughput_out
pulsar_broker_storage_size
pulsar_broker_storage_logical_size
pulsar_broker_storage_write_rate
pulsar_broker_storage_read_rate
pulsar_broker_msg_backlog

Solution
No response
Alternatives
No response
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!
PR:https://github.com/apache/pulsar/pull/18116

I'm not sure a PIP is formatted as you did. It has a certain process to it.

Hi @yyj8
What is the status of this PIP? I see https://github.com/apache/pulsar/pull/19047 is merged. So my understanding is that all things are completed, right? If yes, Could we send an email to close this PIP?


Add the posibility to adjust the OOM score

I recently needed to adjust the OOM score so that Redis (or sentinel) is not killed.

LGTM. Thanks @eRadical!


Istiod injection

Change the inject address to istiod in the webhook.
Note that the name must match the generated certificate - we can't run Istiod as part of the istio-sidecar-injector service or replace it, since it has a istiod cert.
With this change, injection and SDS will use Istiod and Citadel, injector should no longer get any requests.
Follow up to https://github.com/istio/installer/pull/606

@costinm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

build_installer
8babe778dc4b33528d7c476c938ece7b105d4f20
link
/test build_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

build_installer
8babe778dc4b33528d7c476c938ece7b105d4f20
link
/test build_installer

lint_installer
8babe778dc4b33528d7c476c938ece7b105d4f20
link
/test lint_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_installer
8babe778dc4b33528d7c476c938ece7b105d4f20
link
/test lint_installer

build_installer
4824d7909cdd366c40bbe857abfa3d1b1d864e9d
link
/test build_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

build_installer
4824d7909cdd366c40bbe857abfa3d1b1d864e9d
link
/test build_installer

lint_installer
4824d7909cdd366c40bbe857abfa3d1b1d864e9d
link
/test lint_installer

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

@costinm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
3b7e9b53c11f79d72507210b50a85d742bd9b392
link
/test demo_installer

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

@costinm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
456c466c3893bc499c0f03e69318283ad0f44fa9
link
/test demo_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
456c466c3893bc499c0f03e69318283ad0f44fa9
link
/test demo_installer

base_installer
456c466c3893bc499c0f03e69318283ad0f44fa9
link
/test base_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

base_installer
456c466c3893bc499c0f03e69318283ad0f44fa9
link
/test base_installer

demo_installer
b14fd8920eb905403f844a37d4bf0f47788593c8
link
/test demo_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
b14fd8920eb905403f844a37d4bf0f47788593c8
link
/test demo_installer

base_installer
b14fd8920eb905403f844a37d4bf0f47788593c8
link
/test base_installer

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

/test base_installer
/test demo_installer

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

base_installer
b14fd8920eb905403f844a37d4bf0f47788593c8
link
/test base_installer

demo_installer
b14fd8920eb905403f844a37d4bf0f47788593c8
link
/test demo_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
b14fd8920eb905403f844a37d4bf0f47788593c8
link
/test demo_installer

base_installer
b14fd8920eb905403f844a37d4bf0f47788593c8
link
/test base_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
b14fd8920eb905403f844a37d4bf0f47788593c8
link
/test demo_installer

base_installer
b14fd8920eb905403f844a37d4bf0f47788593c8
link
/test base_installer

lint_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test lint_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

base_installer
b14fd8920eb905403f844a37d4bf0f47788593c8
link
/test base_installer

lint_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test lint_installer

demo_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test demo_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test lint_installer

demo_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test demo_installer

base_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test base_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test lint_installer

demo_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test demo_installer

base_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test base_installer

noauth_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test noauth_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test demo_installer

base_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test base_installer

noauth_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test noauth_installer

lint_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test lint_installer

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

/test lint_installer

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test demo_installer

base_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test base_installer

noauth_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test noauth_installer

lint_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test lint_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test demo_installer

noauth_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test noauth_installer

lint_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test lint_installer

base_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test base_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
671a8990257f713725c8cc605433b7e54aca3927
link
/test demo_installer

lint_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test lint_installer

base_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test base_installer

noauth_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test noauth_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test lint_installer

base_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test base_installer

noauth_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test noauth_installer

demo_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test demo_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

base_installer
6b5ebfff439686840ba68c030716a91b73242835
link
/test base_installer

demo_installer
88a549d4ff2acf821cc1f939576d75b2c229ea73
link
/test demo_installer

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

/test demo_installer

@costinm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
88a549d4ff2acf821cc1f939576d75b2c229ea73
link
/test demo_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer
88a549d4ff2acf821cc1f939576d75b2c229ea73
link
/test demo_installer

base_installer
19571592755052c59b4205fd592a7c6e942fd213
link
/test base_installer

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

@costinm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

base_installer
19571592755052c59b4205fd592a7c6e942fd213
link
/test base_installer

noauth_installer
19571592755052c59b4205fd592a7c6e942fd213
link
/test noauth_installer

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

I have a copy of this with conflict resolved and tests passing if you want to approve that or we can go with this https://github.com/istio/installer/pull/633

I copied this over to #633 which was merged


Request: Hansen's test matrices for regularization methods

You might be interested in implementing some matrices in Per-Christian Hansen's paper (see Reference). In that paper, Hansen describes the generation of oscillatory matrices, which are matrices A with some powers Ap that are totally positive.
The paper also describes other test matrices available in Matlab's Regularization Toolbox.
These matrices would have been nice to have back when JuliaLang/julia#8859 was being discussed. It might still be useful for other purposes.
Reference: doi:10.1137/0916032

Thanks a lot for the reference @jiahao, I will look into it.

The oscillating matrix oscillate is now implemented in Matrix Depot.
I also implemented some test problems for regularization methods from the paper:

deriv2
foxgood
shaw
wing

See http://matrixdepotjl.readthedocs.org/en/latest/regu.html


Abandon a project and abandoned projects

Like businesses, Open Source projects has good times and bad times. Some projects are in the spotlight for a few years, attracts a lot of attention from developers and security researchers, gets funding for adding new functions and have huge project-cons with massive participation.
What happens when the spotlight is turned off? How does the project survive? Will lack of funding lead to risks of security issues in the code?
There are many abandoned projects out there. Do we need a formalise the slow death? Like an SPDX identifier that maintainers can use to indicate their current status - like "not active", "security fixes only", "looking for new maintainer". This could be added to SBOMs and used in evaluation of a project as a dependency.

This is a super interesting topic to explore. On CPAN, we operate with bus-factor (publicly shown on metacpan.org for each module published), and many have a bus factor of 0 or 1. There are routines in place for adopting modules, but there's always difficulty when making the judgement call if this is OK or not.
For abandoned projects that are actively in use (and maybe need security updates) the situation can become even more frustrating. And to make it even more interesting, the well-being and sustainability of projects are going to become even more important when considering the new upcoming laws on cybersecurity coming from the EU (the NIS2 directive, and the Cyber Resilience Act).
One possible angle here is to put additional focus on…

Succession planning – who takes over a project when a BDFL reaches EOL?
Should commercial stakeholders take a more active role in the sustainability of the projects they depend on in their business, and what steps can a project do to make progress in this regard?
Who are the stakeholders that can influence the long-term viability and sustainability of a project, how does this typically play out in practice?
What are the best ways of identifying projects that require special attention like this?

I think this would be a extremely fascinating and prescient topic to bring forward in your schedule.


Update 00-run-chroot.sh

Fixed issues : bad kernel-headers version, bad symlinks in /lib/modules/, wireshark-common asks a question

Sorry, I did something bad.
The script can't install anymore any package.
I will look at the source lists, and find how to make it work properly.

No, there's no problem with this PR.
The issue I have occurs in 04-Wifibroadcast/03-run-chroot.sh.
I'll investigate it now ...

After a total rebuild I can confirm that :

4.14.71 kernel-headers version are installed by apt-get install raspberrypi-kernel-headers,
bad symlinks in /lib/modules/ have disappear,
wireshark-common doen't ask anymore question.

But ... OSD is no more displayed !
Not sure if it's cause by this PR ...

Wireshark still asked me questions...

No, this command is not part of the script, because kernel-headers are not installed in the image.
But if you need it (for compiling a module, or installing something else), then you have to use apt-get install raspberrypi-kernel-headers to get it. And now the command installs good versions of kernel-headers, and it also creates good symlinks in /lib/modules/.
Do you understand ?

So I did a complete clone and fresh start.
The wireshark prompt does not appear during the build- however I did not yet check if the changes made just made wireshark not install. ie perhaps the changes made did not let wireshark install at all
On a pi 3b the script hangs while initializing the wifi adapter
The OSD never appears (because the adapter does not initialize)
@Yes21 I think we need a solution to the symlink/headers that does not require running
install raspberrypi-kernel-headers on a live internet connected pi
While researching this problem I came across this interesting post-
https://stackoverflow.com/questions/16688138/building-lib-modules-uname-r-build-while-compiling-a-kernel

Wireshark still asked me questions...

I've just tested it again for the third time, and I can confirm that wireshark doesn't ask anymore a question.
The building process did go to the end without stopping. That's a great thing !

@Yes21 I think we need a solution to the symlink/headers that does not require running
install raspberrypi-kernel-headers on a live internet connected pi

@pilotnbr1 I don't understand what you mean ?
For me there's no more problem with that ...
@RespawnDespair Can you help me to explain things, because my english is too poor for that !
I'm sure that @pilotnbr1 and me are misunderstanding us ...

The wireshark prompt does not appear during the build- however I did not yet check if the changes made just made wireshark not install. ie perhaps the changes made did not let wireshark install at all

@pilotnbr1 You could be right !
It seems that wireshark-common isn't installed, and tshark also, which is normal because wireshark-common is needed for tshark.
That's certainly why OSD is not working anymore ...
Will continue to investigate.

wireshark-common (and tshark) were not installed because I did disable sudo apt-get update !!
After having run sudo apt-get update, they can be installed without the question from wireshark.
But now I again have the problem of bad kernel-headers version with apt-get install raspberrypi-kernel-headers !!

Now the first thing to do is to restore sudo apt-get update.
... and then find a way to install good kernel-headers version, if someone needs to install it.

With wireshark-common (and tshark) correctly installed, OSD is not working again !
That's enough for tonight.

I think this pr should be reverted.
apt-get update does not actually make updates to the software. It only updates the list of sources and dependencies. I think that should be left in place. On a side note I think after all the packages are installed and purged we should run auto-remove to get rid of uneeded packages
Removing the symlinks, could be left for now but that really doesnt address the underlying problem of nothing in /usr/src
Wireshark is not installed


docs: fix resolver example to use invenio_records.api.Record

The resolver example in usage documentation needs to be reverted back to original state:
From:
>>> from invenio_pidstore.resolver import Resolver
>>> records = {}
>>> resolver = Resolver(pid_type='recid', object_type='rec',
...    getter=records.get)

To:
>>> from invenio_pidstore.resolver import Resolver
>>> from invenio_records.api import Record
>>> resolver = Resolver(pid_type='recid', object_type='rec',
...    getter=Record.get_record)

See discussion in #93

I strongly disagree on this one.

Well, I strongly disagreed with the change but was large enough to not block the alembic recipes from being integrated due to this change. The simplest solution here is simply to skip (meaning have an example which is not executed) the doctest for this example.

It'll be much easier to talk IRL about these "strong disagreements", but here are some high-level musings as my input in the meantime:

If we add a "runnable example" and skip it in tests, then chances are the example will become obsolete sooner or later... We saw this Murphy law happening several times already. Are we worried about it here in the records/pidstore use case?

Generally speaking, if invenio-foo does not depend on invenio-bar for its runtime operation (i.e. no dependency declared in install_requires or extras), then I think it is not good to depend on it in tests only (i.e. dependency declared in tests_require only). Isn't it surprising to mandate invenio-foo to be a sort of integration testing place for collaboration with invenio-bar, if it is a "lesser" package in the ecosystem, since the "higher" package is already testing this collaboration?

Such a "mutual testing" between P1 and P2 could get even more complicated if there are several inter-dependent packages P1, P2, P3, P4 in the game... What about using Invenio demo site as a natural inter-package integration testing place? A Jenkins style of nightly integration testing jobs comprising all our 80+ packages for all our 4+ flavour use cases would be happening there naturally, making sure all the packages work well together. We need to do this before getting to making "flavour releases" anyway.

Whatever we choose, we'll probably need lots of inter-sphinx for closely related packages for the documentation to make sense to people bringing these independent packages together...

Just to clarify, this is not about dependency between modules, but about clear end-user documentation. And yes, easier to discuss IRL unfortunately I had to stay home today due to family issues.
Invenio-PIDStore is at the code-level not dependent on Invenio-Records, but the overall Invenio architecture ties Records and PIDStore very intimately together, and I think it's wrong to write documentation that tries to hide or obfuscate this fact. The example as-is now is used nowhere in Invenio, whereas the previous example is used many places.
Anyway, let's not waste more people times with this discussion. I'll close the issue and fix it myself when I get around to it.

Just to clarify, this is not about dependency between modules, but about clear end-user documentation.

Yes, I know.  That's why I started with the "runnable example" question. It's a dilemma: (1) if we put untestable examples in the documentation, aren't we worried that they will get obsolete with time? vs (2) if we want to make documentation examples runnable, aren't we worried to enter the thin ice of inter-module dependencies? Anyway, IRL.


problem super cache with permalink utf8

thanks i try follow work all domain but have one domain use permalink postname.
please help
domain/ការទិញខុនដូពីសំណាក់/
check header show x-cache: MISS. if no phpfpm run site dead

yes i found problem
uri or request uri
string Uppercase but in server string  lowercase
how to convert var to lowercase

Hi @kh71 ,
Thanks for your time evaluating this repo for your use-case.
This is a generic issue with Nginx. Not particular to WP Super Cache plugin. I came across similar issues with utf8 on URLs. I use https://nginx.org/en/docs/njs/ to solve such issues. I hope that helps you too. Unfortunately, there is no other easy way to solve lowercase or utf8 problems within the configuration. If there is any, I am all ears.
Thanks again,
Pothi.

thanks reply but me not clear njs. can guide me.
i have searching in stackoverflow found but don't know how to addon perl too.
https://stackoverflow.com/questions/39795527/nginx-rules-for-upper-lower-case-locations


TensorBoard Graph doesnt work

win 10
python 3.10.5
tensorflow 2.9.1
I ran this code:

A folder created:

I used this command in the terminal:

and this happend:

I clicked the link (http://localhost:6006/ ) and then graphs and it send me to this:

I pressed Conceptual graph in the Graph type and got this:

This is the output that i want:

What should I do?

import pandas as pd
import keras
from keras.models import Sequential
from keras.layers import *
RUN_NAME = "run 2 with 5 nodes"
training_data_df = pd.read_csv("sales_data_training_scaled.csv")
X = training_data_df.drop('total_earnings', axis=1).values
Y = training_data_df[['total_earnings']].values
Define the model
model = Sequential()
model.add(Dense(5, input_dim=9, activation='relu', name='layer_1'))
model.add(Dense(100, activation='relu', name='layer_2'))
model.add(Dense(50, activation='relu', name='layer_3'))
model.add(Dense(1, activation='linear', name='output_layer'))
model.compile(loss='mean_squared_error', optimizer='adam')
Create a TensorBoard logger
logger = keras.callbacks.TensorBoard(
log_dir='logs/{}'.format(RUN_NAME),
histogram_freq=5,
write_graph=True
)
Train the model
model.fit(
X,
Y,
epochs=50,
shuffle=True,
verbose=2,
callbacks=[logger]
)
Load the separate test data set
test_data_df = pd.read_csv("sales_data_test_scaled.csv")
X_test = test_data_df.drop('total_earnings', axis=1).values
Y_test = test_data_df[['total_earnings']].values
test_error_rate = model.evaluate(X_test, Y_test, verbose=0)
print("The mean squared error (MSE) for the test data set is: {}".format(test_error_rate))``

@DaniPol,
I was facing a different error while executing the provided code. Kindly find the gist of it here. Could you provide the dependencies and code in the indentation format. Thank you!


bugfix(TDI-38395): fix empty schema

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-38395
What is the new behavior?
Error message
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
https://jira.talendforge.org/browse/TDI-38395

Pull request test result: success :star:


chore(package.json): adds main entry to support CommonJS module loading

Thanks @mchlbrnd !
We also have a router-es5.js version in the dist files. Is there a way to define more than just one main file?

For right now, I wouldn't worry too much about importing just the
transpiled es5 Router class.
On Thu, Feb 26, 2015 at 7:18 AM Pascal Precht<EMAIL_ADDRESS>wrote:

Thanks @mchlbrnd https://github.com/mchlbrnd !
We also have a router-es5.js version in the dist files. Is there a way to
define more than just one main file?
—
Reply to this email directly or view it on GitHub
https://github.com/angular/router/pull/136#issuecomment-76195507.

Agreed!
Cheers!

@mchlbrnd can you squash your commits? :)

Thanks @mchlbrnd !

Please, Can you add "main" into ".bower.json" ?


Update index.md

add super-linter to clean code linters

Please confirm this pull request meets the following requirements:

[*] I followed the contributing guidelines: https://github.com/github/explore/blob/main/CONTRIBUTING.md.
[x] I am not the sole author or employee of a company who created either the topic I am modifying/adding or the collection entry I am modifying/adding.

Which change are you proposing?

[*] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288, size <= 75 kB)
[ ] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

[ ] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[ ] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

Please replace this line with an explanation of why you think this topic or collection should be curated.

Something that does not neatly fit into the binary options above

[x] My suggested edits are not about an existing topic or collection, or at least not a single one
[ ] My suggested edits are not about curating a new topic or collection, or at least not a single one
[ ] My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

Please replace this line with an explanation of your proposed changes.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

conflict of interest check failed erroneously, due to markdown parse error. pushing manually.


Download Both video and screen for a lecture

When downloading a lecture, the extension downloads the screen recording, but not the camera-view of the lecture capture
This is what the Echo360 website looks like:

Is there any way to download the video recording as well? Either both videos collated into a single mp4 file, or even the two videos as separate mp4 files (then syncing them up would be down the line)

Related to #28


What to do when I temporarily turn off the opcc server and then turn it back on? I want the ev charger to automatically connect to the opcc server without us having to go into the terra config app to configure a new connection.

What to do when I temporarily turn off the opcc server and then turn it back on? I want the ev charger to automatically connect to the opcc server without us having to go into the terra config app to configure a new connection.

When you temporarily turn of the OCPP server the charger is disconnected.  The charger should attempt to reconnect automatically.  There is nothing the server side can do: the connection is initiated by the client.


Allow unique option in migrations

I frequently use Django you can specify a column to be unique when defining a model field.
I tried this with ecto yesterday and it didn't work so this pull request adds support for this:
add :slug, :text, unique: true, null: false

Which will generate
"slug" text UNIQUE NOT NULL

The same thing can accomplished with
create index(:posts, [:slug], unique: true)

but seems like a convenient option. I'm not sure if it's desired for Ecto, however.
Note that you can't name the index inline like you can in Postgres. For that you would need to use index/3 as you would now.
Also, PRIMARY KEY implies UNIQUE NOT NULL but this doesn't stop you from specifying both (redundant) options. It doesn't matter in Postgres:
create table posts (slug text unique not null primary key)

works fine.

I think this is great. I will hold on merging it for now though because there is on going work on other adapters and I want to avoid messing it up. We will merge this later and find out a way to notify adapter implementations that they need to catch up! Thanks a lot!  :heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:

@mobileoverlord can you please verify this also works with TDS and add a unit test to tds_ecto? Once you confirm, I am merging this.

Good to go
https://github.com/livehelpnow/tds_ecto/commit/7eb035d10211a414b113336c8d55ffc5ca30eb44

:heart:


Very slow sending rate despite high bandwidth

I am trying to scan the entire IPv4 for my final thesis. As a setup I am using Zmap on the Linux sub system on windows (Ubuntu-20.04) and a VPN connection to my home university with a fairely high ping around 200-300ms. I am achieving around 100mb download- and uploadspeed (with the VPN turned on).
I noticed a very slow sending rate around 4.75 Kp/s with the following invocation
sudo zmap -M udp -p 53 --probe-args=file:examples/udp-probes/dns_53_queryAwww.google.com.pkt -o sample.csv
I tried to adjust the bandwidth manually with the -B option, starting with 2MB, increasing. It turns out that anything above "-B 4M" results in the same sending rate as stated above.
I hope you have an idea what could cause that issue.
Additional information:

Zmap version: "zmap 2.1.1"
I also tried using my home network with around 250mb up and download rate (~ ping around 2ms). Here I achieved slightly more, around 7 kp/s sending rate.
I performed a speedtest on my linux subsystem to make sure I really achieve the data rate mentioned above.
During testing the sending rate, I ran above command around 24 hours without noticing an increase in the sending rate.

Try using the current ZMap release candidate from Github. 2.1.1 is old and bandwidth calculations with UDP had a longstanding bug that has since been fixed, IIRC.

Please reopen if this persists after you've tried the 3.0.0-beta1


docs: add Docker guidance for OPENFGA_HTTP_ADDR

Description
This PR updates the README to include guidance in the Docker section for configuring the container to listen on ports other than 8080. Configuring OPENFGA_HTTP_ADDR is necessary for services inside the container, like the playground, to successfully adapt to port changes.
References
N/A
Review Checklist

[x] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

@miparnisari @rhamzeh 👍 Updated with y'all's feedback. Thanks!


Deploy live demo

I deployed one here: https://datasette-auth0-demo-j7hipcg4aq-uc.a.run.app/
By running:
datasette publish cloudrun fixtures.db \
--install datasette-auth0 \
--plugin-secret datasette-auth0 domain "pillarpointstewards.us.auth0.com" \
--plugin-secret datasette-auth0 client_id "DLXBMPbtamC2STUyV7R6OFJFDsSTHqEA" \
--plugin-secret datasette-auth0 client_secret "..." \
--service datasette-auth0-demo

Still need to give it a nicer domain name and link to it from the README.

Setting this to datasette-auth0-demo.datasette.io - I added the CNAME in Vercel DNS, now setting that up in Cloud Run too.

I'm going to set this up to deploy on every push. Then I'll add it to the README and release a non-alpha 0.1.

Imitating https://github.com/simonw/datasette-json-html/blob/bb4c2ed9538745f866a781be8db04f70e0531cc8/.github/workflows/deploy-demo.yml
    - name: Set up Cloud Run
      uses: google-github-actions/setup-gcloud@v0
      with:
        version: '275.0.0'
        service_account_email: ${{ secrets.GCP_SA_EMAIL }}
        service_account_key: ${{ secrets.GCP_SA_KEY }}
    - name: Deploy to Cloud Run
      run: |-
        gcloud config set run/region us-central1
        gcloud config set project datasette-222320
        datasette publish cloudrun demo.db \
          -m metadata.json \
          --install=https://github.com/simonw/datasette-json-html/archive/$GITHUB_SHA.zip \
          --service datasette-json-html-demo

https://github.com/simonw/datasette-hashed-urls/blob/659614c23cbc544915079c44b09b09b090400ff8/.github/workflows/test.yml shows how to deploy it after the tests have passed.

Creating a new auth0 application for this:

https://manage.auth0.com/dashboard/us/datasette/applications/n9eaHS0ckIsujoyZNZ1wVgcPevjAcAXn/settings

DOMAIN = datasette.us.auth0.com
CLIENT_ID = n9eaHS0ckIsujoyZNZ1wVgcPevjAcAXn
I added the CLIENT_SECRET as AUTH0_CLIENT_SECRET in a secret for this repository.

And I set https://datasette-auth0-demo.datasette.io/-/auth0-callback as the callback URL.

Secrets for this repo:

OK, that deploy seems to have worked. Won't know for sure until Google Cloud finishes provisioning the certificate for the new URL though.

Actually no, I added https://datasette-auth0-demo-j7hipcg4aq-uc.a.run.app/-/auth0-callback as another valid callback and it worked!

I'll close this as soon as https://datasette-auth0-demo.datasette.io/ starts working.

Turned this into a TIL: https://til.simonwillison.net/github-actions/deploy-live-demo-when-tests-pass


ctrl-arrows & ctrl-shift-arrows operate on the rest of the line instead of by word

Ctrl-[<|>] should move the cursor to prev / next beginning of a word, and Ctrl-Shift should do the same but with selection. Right now they move to the beginning or end of the line.
(using egui client on linux)

I had no idea, sounds like we're going to need an overall review of keyboard shortcuts (if that's what you'd call this) on various platforms


Machines look very dark

What datapack(s) do you have installed (including ones made by me- include version if possible).
Using datapacks Mechanization v2.3.0 and Datapack Utilities v2.2.0a.

Run /reload. Copy/paste or post a screenshot of what appears in chat (should say [Loaded  ]).

What environment are you running the datapack? (Vanilla single player, Vanilla multiplayer, Forge, fabric, spigot, bukkit, paper, optifine, realms, etc). Please specify exact Minecraft version as well.
Minecraft 1.16.1 with Fabric 0.8.0+build202.

What if happening vs. what you expect to happen?

Rendered wrong machines in the picture, from left to right are Machine Crafting Table, Auto Jukebox, MSS Driver Bay and Grinder.
Many machines render unusual dark and it's hard to distinguish every single machine. It seems to happen only in 1.16 but not the 1.15, is this issue about the datapack or the game itself?

This is probably a 1.16 issue, however 1.16.2-prerelease 3 is supposed to fix this.


Protected lists crash pydase

When creating a protected list attribute, the web interface crashes:
import asyncio

import pydase

class MyService(pydase.DataService):
    _protected_list = [0, 1]

    async def update(self) -> None:
        while True:
            self._protected_list[0] += 1
            self._protected_list[1] += 1
            await asyncio.sleep(1)

if __name__ == "__main__":
    service = MyService()
    print(MyService().serialize())
    pydase.Server(service).run()

This is because lists are always converted to DataServiceLists. To change this, skipping a list attribute that starts with an underscore should do the job.

As this block registers a callback on DataServiceList instances used in property source code, I will still cast all protected lists into DataServiceLists. Otherwise, properties depending on protected lists will not be updated when the protected lists changed. What I will do instead of ignoring protected lists is to not pass it a callback to emit a notification when it changed.


[Open for all] UI Design for FAQs page of the website

Make UI for the FAQs page of the website using any of the UI designing tool like figma
This page will contain the list of all frequently asked questions along with their answers.

Hey @Kajol-Kumari,
I want to work on this issue, can you assign me?

@Kajol-Kumari Can you see this?
I am not a designer so I don't request to assigned.

If you like this one then assign me I will add PR.

@codewithvk This looks nice. Feel free to open up a PR with this :)

@Kajol-Kumari Added FAQ UI Design in the assets folder. Could you now assign this to me?

Here is the screenshot of FAQ UI Design


CRD 8209 FILED FINRA

You want my clearance??
Copy and paste that link into your browser... any browser MF
#28
#13
@BSCPGROUPHOLDINGSLLC
@153974-HSI-OXLEY-BANKS-40ACT
Originally posted by @153974-HSI-OXLEY-BANKS-40ACT in https://github.com/BSCPGROUPHOLDINGSLLC/INDEX153974/issues/10#issuecomment-1203514714

You want my clearance??
https://acrobat.adobe.com/link/review?uri=urn%3Aaaid%3Ascds%3AUS%3A3c818e01-cb77-32d3-8743-6a778dd93975#pageNum=32
32 thats gonna hurt
6507985 $PRIYA DARSINI RAHURAM - FIRM 8209[FILED].pdf
2022-05-27---TCRReport.16537-714-487-492 (2).pdf
2022-05-27---TCRReport.16537-714-487-492 (1).pdf
2022-05-27---TCRReport.16537-714-487-492.pdf
pub-2022-cybersecurity-report.pdf
IMPUTATION__1.3__ABA.GUIDELINES.ON.CONFLICTS.OF.INTERESTS.pdf
USC.18.21.USC.18.2.USC.18.215.USC.18.1962.OPTIMIZED22.pdf

Untitled.attachment.00411.pdf
Untitled.attachment.00435.pdf
Untitled.attachment.00441.pdf
Untitled.attachment.00447.pdf
Untitled.attachment.00453.pdf
NYC.DEPT.OF.FINANCE.-.PUBLIC.RECORD.-.SATISFIED.USC.TITLE.18.21.VIOLATED.pdf
Copy and paste that link into your browser... any browser MF
#28
#13
@BSCPGROUPHOLDINGSLLC
@153974-HSI-OXLEY-BANKS-40ACT

INDIVIDUALS of Interest
@153974-HSI-OXLEY-BANKS-40ACT
You can find them practicing regularly on the glass at Riverbank. Regularly like figure skaters....

@153974-HSI-OXLEY-BANKS-40ACT

@153974-HSI-OXLEY-BANKS-40ACT
@BSCPGROUPHOLDINGSLLC
Under USC 18.225.each person:
'...imprisoned for a term of not less than 10 years and which may be life."
https://github.com/BSCPGROUPHOLDINGSLLC/ELSER-AND-DICKER/blob/BSCPGROUPHOLDINGSLLC-EMAIL-DOCKETS/ms-pwc-dicker
Those papers confer a violation of the Sarbanes-Oxley 2002 Rev.
-- questions?
/S/ BO DINCER.
On Sun, Aug 7, 2022 at 7:52 AM, Bo Dincer
<EMAIL_ADDRESS>wrote:
I look up case number 153974/2020

I don’t see any order from the Judge and can’t find anything in the Federal LOC system either.

Filed on August 4th, 2020. All papers to satisfy this breach which has a MINIMUM 10-YEAR SENTENCE.
18 U.S. Code § 225 - Continuing financial crimes enterprise.
(a) Whoever—
(1) organizes, manages, or supervises a continuing financial crimes enterprise; and
(2) receives $5,000,000 or more in gross receipts from such enterprise during any 24-month period,
shall be fined not more than $10,000,000 if an individual, or $20,000,000 if an organization, and imprisoned for a term of not less than 10 years and which may be life.
(b) For purposes of subsection (a), the term “continuing financial crimes enterprise” means a series of violations under section 215, 656, 657, 1005, 1006, 1007, 1014, 1032, or 1344 of this title, or section 1341 or 1343 affecting a financial institution, committed by at least 4 persons acting in concert.
Here’s a link to help you find the minx.
https://github.com/BSCPGROUPHOLDINGSLLC/ELSER-AND-DICKER/tree/BSCPGROUPHOLDINGSLLC-EMAIL-DOCKET
/S/ BO DINCER
On Sun, Aug 7, 2022 at 7:47 AM, Bo Dincer
<EMAIL_ADDRESS>wrote:
SAMSUNG GALAXY 10 MAC ADDRESS

[SAMSUNG NOT PRE-CLEARED AT ANY TIME PRIOR TO JULY 10TH 2022 FOR" casual wire taps without consent " ](https://github.com/153974-HSI-OXLEY-BANKS-40ACT/153974-HSI-O

@153974-HSI-OXLEY-BANKS-40ACT
@BSCPGROUPHOLDINGSLLC

Under USC 18.225.each person:
'...imprisoned for a term of not less than 10 years and which may be life."
https://github.com/BSCPGROUPHOLDINGSLLC/ELSER-AND-DICKER/blob/BSCPGROUPHOLDINGSLLC-EMAIL-DOCKETS/ms-pwc-dicker
Those papers confer a violation of the Sarbanes-Oxley 2002 Rev.
-- questions?
I did email the police and YES I do press charges, for invasion of privacy as well was unconsented as annexed "cease and desist".
https://github.com/BSCPGROUPHOLDINGSLLC/WILSON-ELSER-DICKER-LASKOWITZ-MOV/find/8209-filed
/S/ BO DINCER


Tomat7 - Dark and High contrast theme.

 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: Tomat7 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Please, review pull request.
Thanks in advance.

Thanks.

By the way, I tested with C++ environment only.

Can you please provide an overview screenshot of the theme?


How to open a new tab?

I found a browser.closeTab function. Is there a way to open a new tab manually? How does secret-agent manage the opening of new tabs?

Hi @petrpatek
We don't yet have the ability to explicitly spawn a new tab. The tabs feature comes in handy when clicking a link goes to target="_blank" or the page does a window.open in the javascript. If you really want new tabs from links, you can also use the MetaLeft key to open links in a new window (that's mac, use equivalent for other OSes).
SecretAgent treats each "Browser" as a unique sandbox of cookies, storage, etc. It's very lightweight - akin to an Incognito Window in Chrome. When you run SecretAgent.createBrowser, it will automatically establish a tab for you. You just run "goto" to send it wherever you want it to go.
Hopefully that answers your question.
If you need to wait for newly "spawned" tabs, there's a browser.waitForNewTab method.

@petrpatek following up. Is there anything you would like fixed/improved/changed here? If not, going to close this one out.

Hi @blakebyrnes,
Thank you very much for your answer.
I think I get it now. I am used to the puppeteer/playwright logic, so when I want to run some tasks in parallel and don't really care about the cookies or the fingerprint. The tasks are executed in multiple pages (tabs or windows). In secret-agent, I am supposed to spawn multiple browsers with the default tab, am I right?
Thank you again!

@petrpatek
Yep, that's what you'd do for generating multiple tasks. @calebjclark and I talked about this a good bit after your question. We're considering renaming "createBrowser" to something a little lighter weight sounding.

@petrpatek to add a little more color to what @blakebyrnes just mentioned...
We're considering renaming createBrowser to something like createSession, because createBrowser isn't really accurate. You're not spinning up an entirely new browser... just an isolated browser session.

@blakebyrnes  @calebjclark Thank you for the clarification. To me createSession sounds less like I should worry about the performace.

@petrpatek Thanks for the feedback!


Adding RS256 signature verification.

Thanks! Where are the LcRSA and companion classes. With the PR we add a dependency which is not resolved

LcRSA  stems from https://github.com/PierceNg/OpenSSL-Pharo
Is there a way to explicitly declare this dependency in the code or package definition?

Thanks! Where are the LcRSA and companion classes? With the PR we add a dependency which is not resolved

I see the "resolve conflicts" pop up. Am I supposed to take action on this?

Please have a look at #10 where your changes are incorporated


Gravity vector is needed even if gravity is not used to compute two_theta

In the conversion graph, we are adding coordinates (cylindrical_x, cylindrical_y unit vectors) that are used to compute the phi angle which is then used to decompose the detector panel in phi quadrants to compute the beam center.
Those make use of the direction of gravity to determine what is down.
This means that even if we don't want to apply gravity correction to the flight paths of the neutrons, we still need the gravity coordinate.
However, if we are only using the beam center finder based on the center of mass (as opposed to $I(Q)$ inside 4 quadrants), then we do not need the gravity vector at all, but the workflow will complain if the gravity vector is missing from the data.
We should probably improve the logic to only require the gravity vector if needed.

Gravity vector is actually needed because we need to know which way is down, so that we can apply beam center corrections perpendicular to the beam (which is horizontal).

Have you checked if the workflow works (without gravity vector) without beam-center finder, i.e., when we set the beam center to hand?

Have you checked if the workflow works (without gravity vector) without beam-center finder, i.e., when we set the beam center to hand?

Good idea, will do.

See https://github.com/scipp/esssans/pull/77/commits/6b116bc23f4a979d69f7a8b917a492192d6c3181


Inline small functions

This adds #[inline] to small functions which should be beneficial to inline.
rustc compilation performance (code size of rustc_driver up by 0.09%):
clap:check                        1.9486s   1.9416s  -0.36%
hashmap-instances:check           0.0629s   0.0626s  -0.52%
helloworld:check                  0.0443s   0.0439s  -0.69%
hyper:check                       0.3011s   0.3000s  -0.36%
regex:check                       1.1505s   1.1468s  -0.33%
syn:check                         1.6989s   1.6904s  -0.50%
syntex_syntax:check               6.8479s   6.8288s  -0.28%
winapi:check                      8.3437s   8.2967s  -0.56%

Total                            20.3979s  20.3108s  -0.43%
Summary                           4.0000s   3.9820s  -0.45%

This is the effect on compile time this has on my HashMap compile time benchmark:
hashmap-instances:check           0.0635s   0.0632s  -0.33%
hashmap-instances:release        32.0928s  32.4440s  +1.09%
hashmap-instances:debug           7.2193s   7.2800s  +0.84%

Total                            39.3756s  39.7873s  +1.05%
Summary                           1.5000s   1.5080s  +0.54%

We saw a 1.6% improvement in rustc's build time for a -20% improvement on hashmap-instances:release on https://github.com/rust-lang/rust/pull/87233. So I would expect around a 0.08% regression for rustc's build time from this PR.

This looks reasonable: all of these function should compile down to approximately a single assembly instruction, so not inlining them is almost certainly a bug.
@bors r+

:pushpin: Commit b50ecceaa2bc5d870736b849f7f6388aed5806ee has been approved by Amanieu

:hourglass: Testing commit b50ecceaa2bc5d870736b849f7f6388aed5806ee with merge 47a23ab71932aff3052bfff31e732ea551c6ce1e...

:sunny: Test successful - checks-actions
Approved by: Amanieu
Pushing 47a23ab71932aff3052bfff31e732ea551c6ce1e to master...


Sdkman also has this

sdkman.io under get started
curl -s "https://get.sdkman.io" | bash

Is now in the list, thanks!


AddressSearcher is blocking

A recent lint warning suggests changing the use of AddressSearcher to the callback form. However, this will require a bunch of refactoring to the code that calls any AddressSearchers.

A recent lint warning suggests changing the use of AddressSearcher to the callback form. However, this will require a bunch of refactoring to the code that calls any AddressSearchers.

A recent lint warning suggests changing the use of AddressSearcher to the callback form. However, this will require a bunch of refactoring to the code that calls any AddressSearchers.


how can i display a popup with the results of a related query?

Please tell me the right place to ask a question if this is the wrong place.
Do you have any examples of combining a related query with bindPopup? I've taken a stab at it, and it seems my pop up is one click behind the information I clicked on when I embed the call to related query within bindPopup().
Thank you from a newbie!

it seems my pop up is one click behind...

if the initial click on the marker/path/polygon is what you're using to trigger the async request to fetch related records, it definitely will be.  luckily you can call L.Layer.openPopup() instead of waiting for someone to click on the same feature again.
query.objectIds([currentFeatureId]).relationshipId("0").run(displayPopup)

function displayPopup (error, response, raw) {
  var currentFeature = fl.getFeature(currentId)
  currentFeature.bindPopup('matching rows: ' + response.features.length);
  currentFeature.openPopup();
}

another option would be to trigger the relationship query earlier on and bind your popups before a user click.
either way, i think the example i outlined above would be a lot more useful in the readme than what i have currently.  are you interested in submitting a pull request to make the update?

Thanks for your response. I ended up skipping bindPopup and setting a map.on(“click”) listener that grabs the related records, puts it into a new popup, and then opens the pop up. It works well!
I think your way below is simpler though.
To make the pull request, am I just editing the ReadMe with your example below?
Thanks again!
Ann
Ann Gaffigan
Owner/CEO
Gazelle Incorporated
714-793-9739

On Sep 7, 2016, at 11:26 AM, john gravois<EMAIL_ADDRESS>wrote:
it seems my pop up is one click behind...
if the initial click on the marker/path/polygon is what you're using to trigger the async request to fetch related records, it definitely will be. luckily you can call L.Layer.openPopup() http://leafletjs.com/reference-1.0.0.html#marker-openpopup instead of waiting for someone to click on the same feature again.
query.objectIds([currentFeatureId]).relationshipId("0").run(displayPopup)
function displayPopup (error, response, raw) {
var currentFeature = fl.getFeature(currentId)
currentFeature.bindPopup('matching rows: ' + response.features.length);
currentFeature.openPopup();
}
another option would be to trigger the relationship query earlier on and bind your popups before a user click.
either way, i think the example i outlined above would be a lot more useful in the readme https://github.com/jgravois/esri-leaflet-related#example than what i have currently. are you interested in submitting a pull request to make the update?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/jgravois/esri-leaflet-related/issues/16#issuecomment-245337726, or mute the thread https://github.com/notifications/unsubscribe-auth/AKVPcBoYL7VqIhhoKgwpwjHhOGiOD3wVks5qnuWqgaJpZM4J2azF.

To make the pull request, am I just editing the ReadMe with your example below?

yes, exactly.  that way its front and center for other folks to find in the future.  bumping the versions of leaflet and esri-leaflet in that sample would probably be a good idea too.
<!-- Load Leaflet from CDN-->
<link rel="stylesheet" href="https://cdn.jsdelivr.net/leaflet/1.0.0-rc.3/leaflet.css" />
<script src="https://cdn.jsdelivr.net/leaflet/1.0.0-rc.3/leaflet.js"></script>

<!-- Load Esri Leaflet from CDN -->
<script src="https://cdn.jsdelivr.net/leaflet.esri/2.0.2/esri-leaflet.js"></script>