connect fails, using valid/current OpenSSH key: "Uncaught Error: Cannot parse privateKey: Unsupported key format",

I've installed
	atom v1.0.0
	Remote-FTP, v0.7.1

on linux64.
I setup an '.ftpconfig'
	{
	    "protocol": "sftp",
	    "host": "test.DDDD.com",
	    "port": 22,
	    "user": "root",
	    "remote": "/",
	    "agent": "",
	    "privatekey": "/etc/ssh/pgnd-dev03.ed25519.key",
	    "passphrase": "",
	    "hosthash": "",
	    "ignorehost": true,
	    "connTimeout": 10000,
	    "keepalive": 10000,
	    "keyboardInteractive": false
	}

where privatekey is a valid & regularly used openSSH-generated ed25519 key.  It's current being used to connect via openSSH (openSSH_6.9p1, OpenSSL 1.0.2c 12 Jun 2015), from shell, to the 'test.DDDD.com' host.
On attempt to make the connection in atom, the following error's thrown
	**Atom Version**: 1.0.0-3874576
	**System**: "openSUSE 13.2
	**Thrown From**: [Remote-FTP](https://github.com/mgrenier/remote-ftp) package, v0.7.1

	### Stack Trace

	Uncaught Error: Cannot parse privateKey: Unsupported key format

	```
	At /home/pgnd/.atom/packages/Remote-FTP/node_modules/ssh2/lib/client.js:147

	Error: Cannot parse privateKey: Unsupported key format
	  at Client.connect (/home/pgnd/.atom/packages/Remote-FTP/node_modules/ssh2/lib/client.js:147:13)
	  at ConnectorSFTP.module.exports.ConnectorSFTP.connect (/home/pgnd/.atom/packages/Remote-FTP/lib/connectors/sftp.js:78:13)
	  at Client.module.exports.Client.connect (/home/pgnd/.atom/packages/Remote-FTP/lib/client.js:198:18)
	  at Client.<anonymous> (/home/pgnd/.atom/packages/Remote-FTP/lib/views/tree-view.js:178:28)
	  at /home/pgnd/.atom/packages/Remote-FTP/lib/client.js:87:14
	  at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:379:3)

ssh2 currently does not support ed25519 keys because node.js/io.js currently only supports RSA and DSA keys for the purposes of its crypto API. There are of course pure-js EC libraries on npm, but I greatly prefer to stick to OpenSSL if for no other reason than speed.

@mscdex Hi, thx for the reply here!
Sticking with OpenSSL is a good -- or at least practical -- thing, imo.
So sounds like this needs to be taken up with/at node.js?  If it were to get 'fixed' there, iiuc, the fix would percolate through your ssh2 to here, @ the remote-ftp pkg?

@pgnd Yes. Although you have to keep in mind that if/when the changes make it into a node/io.js release, you'd have to upgrade to that version (that may/may not be a problem for you).

Great.  And yes, of course -- i diy my node anyway :-) thx.  I'll see what/who I can poke 'over there' ...

for reference:
"io.js crypto lacks standard ed25519 crypto support for ssh, etc. #2144"
https://github.com/nodejs/io.js/issues/2144

@mscdex fyi, from io.js #2144 (https://github.com/nodejs/io.js/issues/2144)
"Maybe the ssh package (https://www.npmjs.com/package/ssh) works for you? It's either that or wait until openssl grows ed25519 support. That probably won't be anytime soon, it's a pretty conservative project."


test: Add delete-user jest test case

Great repository with lots of learning opportunities. Thank you.
With the latest update, I came across one improvement for the graphql queries for partial queries, so that the following query runs (first commit):
query {
  findUsers(input: {}) {
    street
    email
  }
}

Secondly, I was interested in testing the delete user use-case.
While I am not sure if that the approach fits your style, I used the nestjs testingModule.get functionality to insert an user before deleting afterwards -> https://github.com/Sairyss/domain-driven-hexagon/compare/master...timonback:test/delete-user?expand=1#diff-a091dd67cc9b538cbb2103eb528406502d7b0937df370444f71dd4774c9f8f58R42
That can potentially also be used for the create-user cleanup.

Thanks for the PR! Some things need changes so I left comments

Cool!
Where can I view the comments as I am currently unable to find them?

Cool! Where can I view the comments as I am currently unable to find them?

In the PR, open "Files changed" and you should see them

Hi, I just came across the section regarding commit messages.
I updated them on another branch: https://github.com/Sairyss/domain-driven-hexagon/compare/master...timonback:test/use-case/delete-user?expand=1

Leave commit messages here as they are?
(Force) update commits on this branch (not sure what happens to review comments)
Close this PR, and re-open from the other branch
Any opinion?

Hi, I just came across the section regarding commit messages. I updated them on another branch: https://github.com/Sairyss/domain-driven-hexagon/compare/master...timonback:test/use-case/delete-user?expand=1

Doesn't matter much. Thanks for the PR!


NIFI-9895 Allow parameters to reference controller services

https://issues.apache.org/jira/browse/NIFI-9895
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically main)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Thanks @tpalfy , will review

Thanks @tpalfy. All looks good to me at this point. Did some testing and everything seems to work as expected. +1 merged to main.


Kata Containers 1.9.3

Backport fixes for 1.9
kata-deploy: improve debug message, longer cleanup timeout
release: Checkout right version of kernel patches(backport to 1.9)
release: Fix bug in evaluation kata_version.
kata-deploy: Increase the wait timeout for control plane to come up (Backport)
Backport tarball renaming changes related to github actions to 1.9
[backport] CI: Fix bump test
scripts: Fix static build docker config script

2b0d946 obs: Check for broken packages
e59f03c obs: Failed when we have unresolvable packages
7979c6d obs: Do not wait on excluded packages
9be54c5 kata-deploy: improve debug message, longer cleanup timeout
b25b759 release: Checkout right version of kernel patches
38b752a release: Fix bug in evaluation kata_version.
3d0e693 kata-deploy: Increase the wait timeout for control plane to come up
7bfbb15 release: Fix bug in how version is determined for actions
31272df CI: Fix bump test
171242b scripts: Fix static build docker config script
ec3c77b release: Pass the qemu tarball name as a docker build arg
2bd3e02 release: Rename generated artifacts to a particular format

/test


ARGV#kegs and ARGV#resolved_formulae tweak

See each commit for detail

I merged this as it's needed since I ship the HeadVersion change. (i.e. if opt link and LinkedKeg is broken, we need installed_prefix instead of prefix to locate the latest Head installation.

Sorry I hadn't taken the time to provide feedback on this earlier …


Error Curiosity

Recently installed NPMplus on Unraid Server; seeing a lot of this in logs and wondering if it's something I have done wrong?
2024/12/16 17:01:35 [alert] 664#664: worker process 7993 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8015 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8016 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8038 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8039 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8057 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8061 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8072 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8085 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8086 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8094 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8103 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8107 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8118 exited with fatal code 2 and cannot be respawned 2024/12/16 17:01:35 [alert] 664#664: worker process 8126 exited with fatal code 2 and cannot be respawned 2024/12/16 18:01:35 [alert] 10758#10758: pthread_create() failed (11: Resource temporarily unavailable) 2024/12/16 18:01:35 [alert] 10787#10787: pthread_create() failed (11: Resource temporarily unavailable) 2024/12/16 18:01:35 [alert] 664#664: fork() failed while spawning "worker process" (11: Resource temporarily unavailable) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: sendmsg() failed (9: Bad file descriptor) 2024/12/16 18:01:35 [alert] 664#664: worker process 10758 exited with fatal code 2 and cannot be respawned 2024/12/16 18:01:35 [alert] 664#664: worker process 10787 exited with fatal code 2 and cannot be respawned

Also saw this at Startup; maybe defining user not necessary on unraid anymore?::
useradd warning: npm's uid 99 outside of the UID_MIN 1000 and UID_MAX 6000 range. chown: cannot access '/proc/self/fd/3': No such file or directory chown: cannot access '/proc/self/fd/4': No such file or directory chown: cannot access '/proc/self/fd/5': No such file or directory 2024/12/16 18:26:18 [notice] 6112#6112: ModSecurity-nginx v1.0.3 (rules loaded inline/local/remote: 0/7/0) 2024/12/16 18:26:18 [alert] 6115#6115: sched_setaffinity() failed (22: Invalid argument) 2024/12/16 18:26:18 [alert] 6116#6116: sched_setaffinity() failed (22: Invalid argument) 2024/12/16 18:26:18 [alert] 6117#6117: sched_setaffinity() failed (22: Invalid argument) 2024/12/16 18:26:18 [alert] 6120#6120: sched_setaffinity() failed (22: Invalid argument) removed '/data/tls/certbot/archive/npm-2/cert1.pem' removed '/data/tls/certbot/archive/npm-2/privkey1.pem' removed '/data/tls/certbot/archive/npm-2/chain1.pem' removed '/data/tls/certbot/archive/npm-2/fullchain1.pem' '/usr/local/nginx/conf/conf.d/include/coreruleset/plugins/README.md' -> '/data/etc/modsecurity/crs-plugins/README.md' '/usr/local/nginx/conf/conf.d/include/coreruleset/plugins/empty-after.conf' -> '/data/etc/modsecurity/crs-plugins/empty-after.conf' '/usr/local/nginx/conf/conf.d/include/coreruleset/plugins/empty-before.conf' -> '/data/etc/modsecurity/crs-plugins/empty-before.conf' '/usr/local/nginx/conf/conf.d/include/coreruleset/plugins/empty-config.conf' -> '/data/etc/modsecurity/crs-plugins/empty-config.conf' no DEFAULT_CERT_ID set, using dummycerts. Working on file: /data/nginx/default.conf Working on file: /data/nginx/proxy_host/1.conf Success.

Please try with a uid within the supported range


Files variable type

@HriBB @thebigredgeek
What type should the files variable be when passed to the mutation?
The file upload works fine when using your example code. But when using react-dropzone or tcomb-form the files seem to be not handled appropriately.

@sandervanhooft you have to send files as form data.  https://github.com/okonet/react-dropzone doesn't appear to have any opinions as to how you send the data, they just provide hooks to receive the dropped files via callbacks

Hi @thebigredgeek,
I have tried the following, but it didn't work:
// in component that uses react-dropzone:
onDrop: function (acceptedFiles, rejectedFiles) {
      console.log('Accepted files: ', acceptedFiles) // console.log: [File]
      const { onUpload, token, offerid } = this.props
      const fd = new FormData()
      acceptedFiles.map( file => fd.append('files', file, file.name) )
      onUpload(token, offerid, fd)
      console.log('Rejected files: ', rejectedFiles) // console.log: []
    },

The onUpload mutation is received by the server, but yields an empty object for the files variable. What am I missing?
Kind regards,
Sander

@HriBB @thebigredgeek How about accepting an array of Files (array) as input?
Given the MDN description there seems to be no way to programmatically create a FileList.

@sandervanhooft take a look at this line. I am checking for the presence of FileList. There we need to add additional check for a single File instance. I am busy ATM, I have a presentation about React and GraphQL at the office in a few hours, hopefully after that I will have more time to fix these issues. You are welcome to make a PR for this ;)

I'll try to look into it. Good luck with your presentation :)


Get rid of translation of protobuf enums from JSON

Protobuf parser will parse enums if they're all-caps

@msteffen could you update doc/development/pipeline_spec.md to reflect that it has to be caps too?

I already did that in my docs branch. Will be merged shortly. Also updated
in the incrementality section because those docs overlaop.
On Thu, Sep 22, 2016 at 7:07 PM, Joe Doliner<EMAIL_ADDRESS>wrote:

@msteffen https://github.com/msteffen could you update doc/development/
pipeline_spec.md to reflect that it has to be caps too?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pachyderm/pachyderm/pull/884#issuecomment-249083513,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtjwJ2LTZBbvZXLm97CXMNe2jP5hvjEks5qszRfgaJpZM4KEeoz
.


Make "age" of pod print example static

cc @hurf @lavalamp @caesarxuchao
Refer to https://github.com/GoogleCloudPlatform/kubernetes/commit/682734bcc776a473a31b14920cc55f34c671a91e#diff-bd5a484957da582c1a72fa512a18058eR284

@k8s-bot test this please

@k8s-bot test this please

LTGM. Thanks!


az container exec. pipe command result to file fails [Errno 25] Inappropriate ioctl for device

Describe the bug
I'm trying to
az containerapp exec --subscription subscription -g group -n name --command "cat /etc/hosts" >> test.log and it fails...
Exception in thread Thread-1 (read_ssh):
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 1045, in _bootstrap_inner
    self.run()
  File<EMAIL_ADDRESS>line 982, in run
    self._target(*self._args, **self._kwargs)
  File "/opt/homebrew/Cellar/azure-cli/2.58.0/libexec/lib/python3.11/site-packages/azure/cli/command_modules/containerapp/_ssh_utils.py", line 123, in read_ssh
    _resize_terminal(connection)
  File "/opt/homebrew/Cellar/azure-cli/2.58.0/libexec/lib/python3.11/site-packages/azure/cli/command_modules/containerapp/_ssh_utils.py", line 154, in _resize_terminal
    size = os.get_terminal_size()
           ^^^^^^^^^^^^^^^^^^^^^^
OSError: [Errno 25] Inappropriate ioctl for device

Related command
az containerapp exec --subscription subscription -g group -n name --command "cat /etc/hosts" >> test.log
Errors
Exception in thread Thread-1 (read_ssh):
Traceback (most recent call last):
File<EMAIL_ADDRESS>line 1045, in _bootstrap_inner
self.run()
File<EMAIL_ADDRESS>line 982, in run
self._target(*self._args, **self._kwargs)
File "/opt/homebrew/Cellar/azure-cli/2.58.0/libexec/lib/python3.11/site-packages/azure/cli/command_modules/containerapp/_ssh_utils.py", line 123, in read_ssh
_resize_terminal(connection)
File "/opt/homebrew/Cellar/azure-cli/2.58.0/libexec/lib/python3.11/site-packages/azure/cli/command_modules/containerapp/_ssh_utils.py", line 154, in _resize_terminal
size = os.get_terminal_size()
^^^^^^^^^^^^^^^^^^^^^^
OSError: [Errno 25] Inappropriate ioctl for device
Issue script & Debug output
.
Expected behavior
Pipe result to file.
Environment Summary
{
"azure-cli": "2.58.0",
"azure-cli-core": "2.58.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {}
}
Additional context
No response

Thank you for opening this issue, we will look into it.

Hi @programista-zacny
Thanks for reporting this issue.
May I ask what is the device and scenario for executing the command?
OSError: [Errno 25] Inappropriate ioctl for device
Thanks.

MacOS Sonoma 14 on MacBook Air M2.

MacOS Sonoma 14 on MacBook Air M2.
Hi @programista-zacny

Can you help me to double confirm the result of the execution of these python code?
from shutil import get_terminal_size
size = get_terminal_size()
print(size)

Thanks.

Result: os.terminal_size(columns=200, lines=50)
I run this on iTerm.

Result: os.terminal_size(columns=200, lines=50) I run this on iTerm.

Thanks.
The fix has been merged and will be released in Azure CLI version: 2.60.0.
https://github.com/Azure/azure-cli/milestone/141


General Grievance: Watch thearmyjobs.com

General Grievance requests the watch of the watch_keyword thearmyjobs\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

thearmyjobs\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


update Promoting Opportunity’s award label

:+1:

@macool can you please attach related trello card on PR, so that I can log time on review and deploy of it after merging to proper card

@rusllonrails yes, i'll make sure 👍


DesktopComposeTestRule.waitForIdle() can return even though the compose state isn't idle

Describe the bug
Because of GlobalSnapshotManager calling Snapshot.sendApplyNotifications() which immediately advances the snapshot but takes some time to send the notifications, DesktopComposeTestRule.isIdle() can return false before the apply notifications have been sent (Snapshot.current.hasPendingChanges() already returns false but scene.hasInvalidations() still returns false).
Versions

Compose Multiplatform version: 1.4.x

To Reproduce
    @Test
    fun idleIsReallyIdle() = repeat(300){
        val globalValue = AtomicInteger()
        rule.setContent {
            var localValue by remember{ mutableStateOf(0) }

            remember(localValue) {
                globalValue.set(localValue)
            }

            Layout(
                {},
                Modifier.size(50.dp),
                measurePolicy = { _, constraints ->
                    localValue = 100
                    layout(constraints.maxWidth, constraints.maxHeight) {}
                }
            )
        }

        assertEquals(100, globalValue.get())
    }

Expected behavior
rule.setContent calls waitForIdle before returning, therefore globalValue should be 100 when that happens. In reality, it ends up remaining 0 every once in a while (hence the repeat(300).
Additional context
A solution suggested by Chuck from Google, which we're working on, is to add a counter of "current callers inside Snapshot.advanceGlobalSnapshot" which would allow isIdle() to detect the transitional state when the apply notifications haven't been sent yet.

Note that Android has a completely different way of implementing isIdle() - it appears to check there are no tasks scheduled on the main looper.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Layer causes constant "Please enable gps" dialog if user has disabled their gps

Hi I have
LocationMarkerLayerOptions(
    marker: DefaultLocationMarker(
        color: Color(0xFFDE9D1D).withOpacity(0.5),
    ),
    accuracyCircleColor: Color(0xFFDFD772).withOpacity(0.5),
    headingSectorColor: Color(0xFFDFD772).withOpacity(0.5),
),

in my layers.
If my phone has gps disabled this layer causes thousands of "please enable gps" popus to show up. Removing the layer fixes this.
Any idea why this may happen?
https://user-images.githubusercontent.com/1374914/170100135-e0d13f50-860c-4891-87e3-a069e0c26182.mp4

Duplicate of #26

Sorry, I cannot reproduce this issue. How do you build the map? And what API level of android are you using?
I tested with the following code and only one dialog pop up:
import 'package:flutter/material.dart';
import 'package:flutter_map/flutter_map.dart';
import 'package:flutter_map_location_marker/flutter_map_location_marker.dart';
import 'package:latlong2/latlong.dart';

class OldStyleExample extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('Old Style Example'),
      ),
      body: FlutterMap(
        options: MapOptions(
          center: LatLng(0, 0),
          zoom: 1,
          maxZoom: 19,
          plugins: [
            const LocationMarkerPlugin(),
          ],
        ),
        layers: [
          TileLayerOptions(
            urlTemplate: 'https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png',
            subdomains: ['a', 'b', 'c'],
            maxZoom: 19,
          ),
          LocationMarkerLayerOptions(
            marker: DefaultLocationMarker(
              color: const Color(0xFFDE9D1D).withOpacity(0.5),
            ),
            accuracyCircleColor: const Color(0xFFDFD772).withOpacity(0.5),
            headingSectorColor: const Color(0xFFDFD772).withOpacity(0.5),
          ),
        ],
      ),
    );
  }
}

Are you re-building the FlutterMap each frame? For there is some internal data stored in the marker layer, it may cause this kind of problem if you re-build it each frame.


Update zio to 2.0.19

About this PR
📦 Updates dev.zio:zio from 2.0.5 to 2.0.19
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio", artifactId = "zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio", artifactId = "zio" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

I'm closing this, it needed a joint bump of zio-interops-cats. Done elsewhere.


Support XDebug 3

As Xdebug 3 has just been released, there are a few points to note in the upgrade guide.
Currently, we install xdebug via pecl and as of today, that will install version 3.0.0.
We could replace the usage of xdebug.remote_enable = on with xdebug.mode=debug, which is currently found in the
00-lagoon-php.ini.tpl file and the php.ini file for this repository.
The XDEBUG_CONFIG env var has been replaced with XDEBUG_SESSION which would require updating the 61-php-xdebug-cli-env.sh file.
xdebug.remote_host is replaced with xdebug.client_host which is found in 60-php-xdebug.sh
xdebug.remote_log is replaced with xdebug.log which is found in 60-php-xdebug.sh
There might be a few other things that need tweaking.

In PR #41, I am not sure if we also need to EXPOSE 9003 as the default Xdebug port was changed from 9000 to 9003. We have a few places where we expose port 9000, but those don't seem to be exposed for Xdebug purposes.

I think we might just pin PECL to Xdebug 2.9.8 for this upcoming release, and put this through more thorough testing before going to 3.

Sounds reasonable @tobybellwood so I've updated the PR to pin the versions to 3.0.0 based on the latest main update

Nice! As I don't xdebug myself, I'll have to rely on you to test it out!

Is it possible to pull from the PR for the Docker images? Or I have to build it all locally?

testlagoon/php-7.4-fpm:pr-41 and
testlagoon/php-7.4-cli-drupal:pr-41 should be on docker hub :-)

@tobybellwood
Could you please advise if there is anything can be done by the community here to roll Xdebug3 into PHP8 images. Thank you

Yup, tell me they work!
 testlagoon/php-8.0-fpm:pr-41
 testlagoon/php-8.0-cli-drupal:pr-41

are the php8 test images with XDEBUG 3, just set XDEBUG_ENABLE=true

@tobybellwood Thanks for sharing the images. I've tested the images and found two issues

It only works if I don't set the XDEBUG_ENABLE variable. If I set XDEBUG_ENABLE=true (no matter if in the docker-compose.yml or in the dockerfile of the fpm container) Xdebug isn't shown within  phpinfo().
I had to set XDEBUG_CONFIG="client_host=host.docker.internal" in my dockerfile of the fpm container to get the step debugging to work..

I am seeing the exact same behavior as above.
When setting XDEBUG_ENABLE in docker-compose.yml it is as if the XDebug extension is not loaded.
cli-drupal:/app$ echo $XDEBUG_ENABLE
true

cli-drupal:/app$ php -i | grep xdebug
/usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini,

To me it seems as if the situation is caused by too much information being removed from the docker-php-ext-xdebug.ini file.
cli-drupal:/app$ cat /usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini

xdebug.client_host=host.docker.internal

Based on my findings I created a new PR #353.
When using the test images XDebug 3 works for me with PHP 8 FPM. I am unsure about what made the difference.
Feel free to test them with the following images:
 testlagoon/php-8.0-fpm:pr-353
 testlagoon/php-8.0-cli-drupal:pr-353


Quick select presets

By adding  app:cpv_selectOnClick="true" to the XML declaration, you can now enable single-tap selection of colours in a preset window. If this is enabled, the "SELECT" dialog button is replaced by a "CANCEL" button to dismiss the dialog. Note that the included translations for this new button are ripped straight from Google Translate, I fully expect there to be issues with these.
Of course if you intend on using any more complex functions (alpha scale, colour shading, custom colour-picking, etc.) this option is not for you, this is just for choosing from a restricted selection of colour presets.
I only did this for my own uses and thought it might be a neat option to include in the main repo.

New user of this library here. Any plans to include this on the library? It seems a nice option for cases where you don't need alpha transparency, etc., and just to allow the user to quickly select a color.

New user of this library here. Any plans to include this on the library? It seems a nice option for cases where you don't need alpha transparency, etc., and just to allow the user to quickly select a color.


Changelog / Docs Release 0.11

Work in progress changelog for 0.11.  #1394 Lots left to do.
Can also serve to host any doc changes found at the last minute. Feel free to push.
Contributor Checklist:

[x] I have added or updated my entry in the creators.json file
[x] I have added a changelog entry for my contribution
[x] I have added/updated documentation for all user-facing changes
[ ] I have added/updated test cases
[ ] I have included the rebuilt production build of the client (only if changes were made to the GUI)

Reviewer Checklist:

[ ] /azp run libertem.libertem-data passed
[x] No import of GPL code from MIT code

@matbryan52 the changelog reads great! :-)

/azp run libertem.libertem-data


fix: avoid gs status sync delay when network failure

Codecov Report

Merging #45 (ed716b5) into master (b1f3d94) will decrease coverage by 0.05%.
The diff coverage is 42.85%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master      #45      +/-   ##
==========================================
- Coverage   26.01%   25.96%   -0.05%
==========================================
  Files          15       15
  Lines        1968     1964       -4
==========================================
- Hits          512      510       -2
+ Misses       1417     1414       -3
- Partials       39       40       +1

Flag
Coverage Δ

unittests
25.96% <42.85%> (-0.05%)
:arrow_down:

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

Impacted Files
Coverage Δ

...kg/controllers/gameserver/gameserver_controller.go
0.00% <0.00%> (ø)

pkg/controllers/gameserver/gameserver_manager.go
39.90% <50.00%> (-0.19%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Parser and Scenario for mailu admin container.

This is a parser and scenario for the mailu admin package, which logs out authentication attempts.

Awesome work! everything technical is working perfectly, could we ask to add a .md file with the collection just explaing what mailu is and an example acquisition file EG:
Mailu is an open source docker based mail application .....

---
source: docker
container_name:
 - Mailuadmin
#container_id:
# - 843ee92d231b
labels:
  type: mailu-admin

Looks like I accidentally created the pull request on the wrong branch of my fork..
I will close this PR and open another.


Add ParameterResolverFactory for AggregateIdentifier

Sometimes your event payload does not contain the aggregate id but your event handler needs to know the aggregate id, this resolver adds a way to do that.
Looking forward to hear what you guys think 👋

Good to hear that you like the idea!
We had a bit of a chat here to try and come up with idea's for different names.
During this we kinda kept circling back to how @AggregateIdentifier felt as the most natural annotation name to use.
So when I'm writing a domain object and I put the annotation on a field. I'm saying this field is the aggregate identifier.
When I'm writing an event handler and I put it on a method parameter. I'm effectively trying to say I want the aggregate identifier.
It might be a bit wrong to have 1 annotation name that has a dual purpose. So it still feels like a wrong decision make.


Container command not found or does not exist

Hi there,
Just found your project and I am very keen to give it a try.
I am running the following command on my swarm manager. The container is created, but then I also get an error message. Here is my command and output:
mjones@mlclustervs110:~$ docker run -d --restart=always
--link=SwarmManager:swarm
-v /etc/docker/ca.pem:/certs/ca.pem
-v /etc/docker/node1-cert.pem:/certs/cert.pem
-v /etc/docker/node1-node1-priv-key.pem:/certs/key.pem
-p 53:53/udp
--name= dns
ahmet/wagl --swarm tcp://<IP_ADDRESS>:3376
--swarm-cert-path /certs
8c7ed3c98605412df02ff76483ef46014aa62460f07f3c7cbd785feca3f64f17
docker: Error response from daemon: Container command not found or does not exist..
If I run the container with -i I also see this:
exec: "--swarm": executable file not found in $PATH
Any ideas?

nevermind,
I missed the wagl command before the --swarm argument


Additional documentation for helper functions in testing

Status
READY
Description
Free functions in test_helpers.h and assert_helper.h have been documented properly.
Type of Change

[ ] bug fix
[ ] new features
[x] documentation
[ ] other

Checklist

[x] I have run the provided clang-format
[ ] I have reviewed my code and commented if necessary
[x] I have added the appropriate documentation
[ ] I have added tests to my new code
[x] All tests pass locally

I also created doc strings for most functions w.r.t the BVH: traverse, build, build_recursive. Please check whether they are correct or  need improvement.


Grabber not getting total images from Danbooru

Every other booru seems to work fine, but when trying to get a tag from danbooru it shows as "Page 1 of ? (30 of ?)" pic related http://i.imgur.com/LUacLlC.png
While this is fine if you want to just browse, it cannot download everything of a tag. It will only download the current page when trying to get all.

Indeed, that's an annoying issue as it prevents one from downloading all in one click.
Until a fix is published, you can however manually edit the "images limit" value to the number of images before starting a batch download, so that it gets them all.


ssl.CertificateError: hostname

some invalid certificate urls breaks the scanning
Traceback (most recent call last):
  File "finder.py", line 92, in <module>
    main()
  File "finder.py", line 88, in main
    pool.map(fun, domains)
  File "/usr/lib/python3.6/multiprocessing/pool.py", line 266, in map
    return self._map_async(func, iterable, mapstar, chunksize).get()
  File "/usr/lib/python3.6/multiprocessing/pool.py", line 644, in get
    raise self._value
ssl.CertificateError: hostname 'abcdef.com' doesn't match either of '*.uvwxyz.com', 'uvwxyz.com'

I guess that's fixed with https://github.com/internetwache/GitTools/pull/39. Could you confirm that, please?

@gehaxelt yes it works fine now
Thank you

Perfect!


Allow selecting TileMapLayers by clicking them

The new TileMapLayers introduced a workflow problem where selecting a layer for editing is more difficult, depending on scene layout. A common workflow is to put TileMapLayers under a single parent. To select a layer you need to first unfold the parent, which is less convenient. If TileMapLayers are under different parents (and the new system allows for some nice setups), finding the correct layer to edit is even more difficult.
This PR allows selecting a layer by clicking it.
https://github.com/godotengine/godot/assets/2223172/58d9edcf-cd62-4278-867c-615ce23b363f
Although I found a bug 🤔 When you close the bottom editor using shortcut after a layer was selected, it gets glued to the cursor.
https://github.com/godotengine/godot/assets/2223172/edbdceb0-11f2-4de9-98ad-031d1b75e33f

Although I found a bug 🤔 When you close the bottom editor using shortcut after a layer was selected, it gets glued to the cursor.

Is this caused by this PR or not ? If not, I think it's good to merge.

Well this PR only adds _edit_is_selected_on_click(), which can't be the source of the bug. Something else is causing it and is only uncovered here.
I think it's some weird corner-case with editor input, where clicking a node starts dragging it, but the editor appears and intercepts  the release event.

Is there any way to disable this behaviour? I find it pretty disruptive to my workflow in the latest beta

no


Uncaught Error: ENOENT: no such file or directory, open '/Users/nvelickovic10/.atom/packages/sync...

[Enter steps to reproduce below:]

...
...

Atom Version: 1.5.4
System: Mac OS X 10.11.3
Thrown From: sync-settings package, v0.7.0
Stack Trace
Uncaught Error: ENOENT: no such file or directory, open '/Users/nvelickovic10/.atom/packages/sync-settings/node_modules/github/api/v3.0.0/routes.json'
At fs.js:549

Error: ENOENT: no such file or directory, open '/Users/nvelickovic10/.atom/packages/sync-settings/node_modules/github/api/v3.0.0/routes.json'
    at Error (native)
    at Object.fs.openSync (fs.js:549:18)
    at Object.module.(anonymous function) [as openSync] (ATOM_SHELL_ASAR.js:137:20)
    at Object.fs.readFileSync (fs.js:397:15)
    at Object.fs.readFileSync (ATOM_SHELL_ASAR.js:385:29)
    at Object.module.exports (/Users/nvelickovic10/.atom/packages/sync-settings/node_modules/github/api/v3.0.0/index.js:22:33)
    at new module.exports (/Users/nvelickovic10/.atom/packages/sync-settings/node_modules/github/index.js:184:26)
    at Object.SyncSettings.createClient (/Users/nvelickovic10/.atom/packages/sync-settings/lib/sync-settings.coffee:198:18)
    at Object.SyncSettings.checkForUpdate (/Users/nvelickovic10/.atom/packages/sync-settings/lib/sync-settings.coffee:46:8)
    at Immediate._onImmediate (/Users/nvelickovic10/.atom/packages/sync-settings/lib/sync-settings.coffee:32:8)
    at processImmediate [as _immediateCallback] (timers.js:374:17)

Commands
     -9:10.9.0 application:add-project-folder (span.name.icon.icon-file-directory)
     -8:42.2.0 tree-view:remove-project-folder (span.name.icon.icon-file-directory)
     -8:36.6.0 tabs:close-all-tabs (li.tab.sortable.right-clicked)
  6x -3:40.3.0 core:move-up (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -0:47.6.0 settings-view:check-for-package-updates (atom-workspace.workspace.scrollbars-visible-always.theme-an-old-hope-syntax.theme-one-dark-ui)

Config
{
  "core": {
    "disabledPackages": [
      "symbols-view"
    ],
    "themes": [
      "one-dark-ui",
      "an-old-hope-syntax"
    ]
  },
  "sync-settings": {
    "_analyticsUserId": "53fa8ddf-80d8-447a-b0bf-2b8b8e04436c",
    "_lastBackupHash": "8167acc91be8c0c15152927837ad10fded83577d",
    "gistId": "f49bb9fe2cbb64c2efb8",
    "personalAccessToken": "efaae7038cecf09a6adb12d7b25c20c1a6d68d68"
  }
}

Installed Packages
# User
an-old-hope-syntax, v0.5.0
color-picker, v2.1.1
hyperclick, v0.0.35
js-hyperclick, v1.4.1
linter, v1.11.3
linter-eslint, v7.0.0
minimap, v4.20.0
open-in-browsers, v0.0.11
react, v0.14.1
sync-settings, v0.7.0

# Dev
No dev packages

Duplicate of https://github.com/Hackafe/atom-sync-settings/issues/194.
In the above error report you have shared your personalAccessToken. You must revoke it to prevent abuse.

Thanks,
I didn't check autogenerated report before commiting it.

I didn't check autogenerated report before commiting it.

https://github.com/atom/notifications/pull/113


Add proper integer-based processing

Iterating over Naturals is difficult and unnecessary. It's not much slower that what we had before but we can make integer-based processes run faster and maybe in parallel.
Plan to add a cli option --high-bases to re-enable Natural processing and set max_base appropriately based on that option.

Now resolves #65


Set up a few more pre-commit hook

CATEGORY
Choose one

[ ] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[x] Build / Development Environment
[ ] Documentation

SUMMARY
Following the work on 5c58fd180, I'm setting up a few more commit hooks on top of black, most notably flake8 (!).
We could bring more from https://github.com/pre-commit/pre-commit-hooks/blob/master/.pre-commit-config.yaml

Codecov Report

Merging #7830 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7830   +/-   ##
=======================================
  Coverage   65.89%   65.89%
=======================================
  Files         459      459
  Lines       22023    22023
  Branches     2418     2418
=======================================
  Hits        14512    14512
  Misses       7391     7391
  Partials      120      120

Continue to review full report at Codecov.

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


[BUG] Failed to request a terminal: {"code":"InternalServerError","message":"No referer header."}

To Reproduce
Just launching "Cloud shell"
Commands you ran
None

Observed Behavior
Include error output here

Expected behavior
When i launch "Cloud shell" :
Requesting a Cloud Shell.Succeeded.
Connecting terminal...
Failed to request a terminal: {"code":"InternalServerError","message":"No referer header."}
I have already log out/log in, delete and recreate my storage account...
Nothing is working.

Is this specific to Cloud Shell?
Please verify if the same issue can be reproduced by running the same tool outside Cloud Shell - for example,
by installing it on your own computer. If so, it is likely to be a bug in that tool or in the Azure service it communicates with,
not in Cloud Shell. Please file the issue with the appropriate project.
Interface information
How are you accessing Cloud Shell - https://shell.azure.com, https://portal.azure.com, via Windows Terminal, or some other method?
If a browser, which Operating System and browser are you using? (ex. Edge on Windows 10)
Additional context
Add any other context about the problem here.

Additional details that I observe when also getting this problem:
I open the terminal in the Virtual Machine's Connect section, by clicking the Select button in the box titled "SSH using Azure CLI". A sidebar opens and eventually shows green check marks next to all the prerequisites:

The terminal opens and takes several minute between printing "Connecting terminal..." and Failed to request a terminal: {"code":"InternalServerError","message":"No referer header."} . This behavior is the same in Chrome and in Firefox. The front-end is actually sending dozens of requests in this time, to an address like https://ccon-prod-westus-aci-02.servicebus.windows.net/<text>/terminals?cols=111&rows=13&version=2019-01-01&shell=bash, with each receiving the same response that eventually gets printed to the terminal. The requests indeed have no Referer header. If I use the browser console to manually add the URL of the current page as a header and resend, it is still missing. If I instead add a "Referrer" header, then the new header is shown.
Conclusion: something on the client side (either an extension or a browser setting) strips the Referer header and Azure cannot live without it.


⚠ ETF has degraded performance

In 75cc0ac, ETF (https://markets.hankyung.com/equity-product/etf) experienced degraded performance:

HTTP code: 200
Response time: 6687 ms

Resolved: 한경메인 performance has improved in 30fbadb.


Automate adding new contributors

Feature
Add appropriate badges to the README.md file. There are many out there, but one I'm certain we'll want is all-contributors , which is widely adopted.
If you find maintaining the list of contributors tedious, try using the CLI tool to lighten your load.
If you use Atom, try out allcontributors, an atom package for the all-contributors-spec implementation.
Here are some examples of other badges as well.
✨ All Contributors ✨

This is a specification for recognizing contributors to an open source project in a way that rewards each and every contribution, not just code.
The basic idea is this:

Use the project README (or other prominent public documentation page in the project) to recognize the contributions of members of the project community.

People are giving of themselves and their free time to contribute to open source projects in so many ways. It can be a real
time sink sometimes and so they should be praised for all their contributions (code or not).
Use this project as an example implementation of the all-contributors specification (see the Contributors section below).
Tools
If you find maintaining the list of contributors tedious, try using the CLI tool to lighten your load.
If you use Atom, try out allcontributors, an atom package for the all-contributors-spec implementation.
Specification
Mandatory
Open source projects should include the following mandatory items in order to support the All Contributors specification:

A "Contributors" section in a prominent site of the project repository documentation that includes a list of all project contributors

The goal should be to use the most prominent site of the project documentation when feasible.  In many cases, this is the project README file
Consider use of a CONTRIBUTORS file in the top level of the repository when the number of project contributors exceeds a level at which it is feasible to use the README file to acknowledge contributions.  In this case, a prominent link to the CONTRIBUTORS file should be included on the README page under the "Contributors" heading

The listings should be formatted as a table with the following information about the project contributors:

Name
URL link to a site where more information can be learned about the contributor.  This URL may be determined by the contributor at the project's discretion.
Indication of the Contribution Category in text or icon image format using the defined Contribution Categories and/or Contribution Categories emoji images (see below).
A link to the Contribution Category in text or emoji format using the defined Contribution Categories and/or Contribution Categories emoji.

The list of contributors can be spread across multiple lines (each technically being its own table) as needed.
The order of contributors is immaterial to the spec. Order them how you wish.

Projects should define contributors as those who contribute to a project in any of the Contribution Categories at any level of contribution.  This specification is, by definition, inclusive of all contributions.  In cases where projects deviate from the Contribution Categories or require a specific contribution level in order to meet criteria as a project contributor, the project should provide explicit documentation of the definitions that satisfy the project contributor criteria in the CONTRIBUTING document or a similar prominent public document at the top level of the project repository.  This specification recommends against exclusion of an individual from the Contributor list based upon perceived level of contribution.  Instead, projects should use indicators of effort within a list that remains inclusive of all contributors to the project at any level of effort.  If used, these effort indicators are at the discretion of the project and are not currently specified.

Optional
Projects should consider the following optional items as part of their commitment to the All Contributors specification:

The user's avatar can be included and is recommended.
An optional link from the Contribution Category indicator to the category-specific contribution(s) can be included to provide additional information about the project contribution(s) as detailed in the section below.

Emoji key

Emoji
Represents
Links to
Comment

💬
Answering Questions (in Issues, Stack Overflow, Gitter, Slack, etc.)

🐛
Bug reports
https://github.com/${ownerName}/${repoName}/issues?q=author%3A${username}

📝
Blogposts
the blogpost

💻
Code
https://github.com/${ownerName}/${repoName}/commits?author=${username}

📖
Documentation
https://github.com/${ownerName}/${repoName}/commits?author=${username}, Wiki, or other source of documentation

🎨
Design
the logo/iconography/visual design/etc.

💡
Examples
the examples

📋
Event Organizers
event page

💵
Financial Support
relevant page
people or orgs who provide financial support

🔍
Funding/Grant Finders

people who help find financial support

🤔
Ideas & Planning

🚇
Infrastructure (Hosting, Build-Tools, etc)
link to source file (like travis.yml) in repo, if applicable

🔌
Plugin/utility libraries
the repo home

👀
Reviewed Pull Requests

🔧
Tools
the repo home

🌍
Translation
the translated content

⚠
Tests
https://github.com/${ownerName}/${repoName}/commits?author=${username}

✅
Tutorials
the tutorial

📢
Talks
the slides/recording/repo/etc.

📹
Videos
the video

Contributors
Thanks goes to these wonderful people (emoji key):

Kent C. Dodds💬 📖 👀 📢
Divjot Singh📖 👀
Ben Briggs📖 👀
James Monger📖
Jeroen Engels📖 👀 🔧
Chris Simpkins📖 👀
F. Hemberger📖

Daniel Kraft📖
Mayank Badola📖 🔧
Marco Biedermann🎨
Itai Steinherz📖
Patrick Connolly📖

This project follows the all-contributors specification.
Contributions of any kind are welcome!

Since these are 2 different issues, can you separate them?

@sethbergman can we make this available or are you on it?

Yeah I got this. I forgot that I assigned myself.

This can be made available. Here is a good reference: https://github.com/kentcdodds/all-contributors

@kylemh @sethbergman Has ANY work been done on this to date? If not, I would like to close this issue.

None.


Gitlab: "Could not import branches"

Describe the bug
I try to set up a project with gitlab. I've connected cloudflare to gitlab and that seems to work as I am able to select repositories. But when I select a respository, it fails to load branches and I cant select a branch. After that it's not possible to proceed and complete the setup
Steps to reproduce
in admin.hub.nuxt.com

new project
import a git repository
gitlab --> chose a repository
Toast message shows "Could not import branches". The network tab shows a 404 on https://admin.hub.nuxt.com/api/teams/.../cloudflare/connections/gitlab/.../repos/.../.../branches

Is this any kind of permission problem?

The repository is from a "team" i am part of
Inside clouldflare directly, there is no problem selecting the gitlab repo and seeing all branches. So the permission between cloudflare --> gitlab should be fine.

Expected behavior
I want to be able to connect a gitlab repository.

I just tested and it seems to work properly:
https://github.com/user-attachments/assets/03f7ebf5-70b8-4557-a44a-8bfcfd6613c3
I added a new fallback system if the branches could not be selected to you can manually add the branch in the text input, hope this solves your issue.

That should solve the issue, as i added the branch name manually yesterday to the input field in a hacky way via devtools :-) Thanks!


Set collection items output to top level only

Coverage remained the same at 93.01% when pulling f92e8f2d6eda772d718c6311c849e0f9925f3e11 on top-level-items into 768fd3078e04f086e0f2f4a6f26e749ec55444a7 on master.


Update StartupDevProd.cs

updated class name to work correctly with examples

Thank you for bringing this to our attention. I'm going to close this PR in favor of https://github.com/aspnet/AspNetCore.Docs/pull/16532. This is part of a larger problem that I'm addressing over there. It's tricky because both the MVC and Razor Pages tutorials share include files.


Remove stable version section from README

Related: #7948
I don't know how this section would be useful.

I think we need to leave it as is for users. Without it, there's no explicit link for v6 branch; v6 users cannot find the codebase and examples.

In the README, Examples is linked to master branch, where Docs, Install Guide, and Concepts are linked to stable. How about changing Examples to refer stable examples? With this modification, we can remove stable version section, I think.

In the README, Examples is linked to master branch, where Docs, Install Guide, and Concepts are linked to stable. How about changing Examples to refer stable examples? With this modification, we can remove stable version section, I think.

Thanks for pointing that issue out. However I still think it's unreasonable to reduce information only to cut our cost to bump the version after major release.

pfnCI, test this please.
As v7 is now the only stable version, I agree with removing this.

Jenkins CI test (for commit 75f2596ca00f054558b0d1ebdd6ddbb04dacb79a, target branch master) succeeded!


Prepare for TypeScript null reference checking

Add types in a lot more places.
Reformat random.ts from 4 to 2 space indent
Add missing imports
Fix variable aliasing (reusing as different types)
Activate strictFunctionTypes

I think that this has exposed a larger philosophical discussion.  I've grabbed some time with the Firebase JS SDK TL and TypeScript Skeptic to discuss what they consider a sane environment.


Add tests for _initAuthResolver in FirebaseAuth

Description
src/auth/FirebaseAuth.js contains a function named _initAuthResolver
This pr adds unit test cases for _initAuthResolver function.
Reference: https://github.com/firebase/angularfire/issues/951

Coverage remained the same at 93.852% when pulling b346d24f0e670131f253776ec6d2b7ca790c1dbb on PezCoder:tests/_initAuthResolver into b6dca6ea5a81b3edd44230fb1cb6ca62419f1926 on firebase:master.

Not sure why the travis is breaking,
Acc to me this should happen:

ctx._initAuthResolver() will invoke auth.onAuthStateChanged internally with a callback to resolve the promise returned by  _initAuthResolver function
Also our spy should be triggered & fakePromiseResolve should now contain a function calling which should call the above callback
Promise should be resolved & expect should be checked.

It's running fine locally but not on travis, maybe it's not resolving on travis.
Am I missing something ? 🤔

Coverage remained the same at 93.852% when pulling 7ab47ede933dc94257ec355a2d56f25b0144016d on PezCoder:tests/_initAuthResolver into b6dca6ea5a81b3edd44230fb1cb6ca62419f1926 on firebase:master.

Coverage remained the same at 93.852% when pulling de454f7cc86311c00feaa1a584d23e1eb47c12d4 on PezCoder:tests/_initAuthResolver into b6dca6ea5a81b3edd44230fb1cb6ca62419f1926 on firebase:master.

The newly added tests are passing as expected now, after i added tick() method at last. 😄
Buy how ? Also other tests that are not related to my pr are breaking.

I think i choose a wrong project to start with open source.. I'm sorry.


feat(client): add discrete git:remote command

Added discrete git:remote command as per request in #3027.
Adds git remote of application to repo or initialises repo if doesn't exist already.
Tis my first attempt at a contribution to Deis, feel free to criticise anything!

Thanks for the contribution! Please ensure your commits follow our style guide. This code will be tested once a Deis maintainer reviews it.

@kevinbluett nice - you beat me to it!
I'd suggest extracting the code to create the git remote from apps:create and create a function out of it, then you can call it in apps:create as well as git:remote without code duplication.

@rjocoleman No worries, definitely a good call, I'll be right on that!

@rjocoleman Just pushed again there now, feel let me know if there's anything iffy or stylistically wrong!

LGTM!  And the first letter should be lower-case. If not, I can do it. Thanks!

If we can squash these into one commit and make its subject something like feat(client): add discrete git:remote command (present-tense, lower case verb), then I'm happy with this. Code LGTM.

@mboersma I've just renamed & squashed the commits now

@kevinbluett If you get a chance to implement @bacongobbler's suggestion re: the docopt default, that'd be great. If not, I can take over the PR to get it merged. Sorry for the iterative review!

@carmstrong I'll do it today, apologies for the delay

thanks @kevinbluett! I've gone ahead and made the changes in #3195. Your commit's still in there so your name will get into the next release. :)

I'm running into an odd behavior with this -- basically the deis client (I'm running 1.5.2 currently) expects that the deis remote is present and pointing to the same controller.
I have a staging cluster addressed via DEIS_PROFILE=staging and created an app with --remote staging.  The client operations (config env push, ps, info) all return 404 not found until I edit the .git/config file by hand and change staging=>deis.  Anyone else seen this?  I can file a separate issue, but just wanted to make sure I wasn't missing something first.

@azurewraith that's how the client currently behaves. The client determines the app's name by checking the deis remote, then the subdirectory. We don't have a way to determine per-app if the user specified the remote to be something else. the --remote option is mostly to workaround another issue, so it's generally recommended to stick to the deis remote unless you're deploying your app to multiple clusters, which then you'd have to use the -a flag.

That is what I figured was happening.  The -a flag is an acceptable workaround and it seems to work.


WFCORE-4037 Undertow 2.0.13.Final

https://issues.jboss.org/browse/WFCORE-4037

Release Notes - Undertow - Version 2.0.13.Final
        Enhancement

[UNDERTOW-1395] -         ALPNOfferedClientHelloExplorer:56 throws BufferUnderflowException every request

        Bug

[UNDERTOW-1397] -         onAsyncComplete should run inside the scope of the original request listener


regex pattern-matching : match implements a search-like behavior, instead of a match

I noted the following issues with regex pattern matching :
1.- binding the same name from 2 different pattern rows confuses the result :

match "fooooooooobar" with | 'f(?o*)bar' -> o | '(?.+)(?o*)bar' -> o | _ -> "none"
""
match "fooooooooobar" with | 'f(?o*)bar' -> o | '(?.+)(?o*)bar' -> od | _ -> "none"
"ooooooooo"

2.- .+ followed by another regex in sequence obliterates the sequenced regexes. FAalthough this behavior is somewhat coorect, a user might expect a stricter matching behaviour to be implemented here. Some regex engines differentiates between matches and searches; is it something we'd benefit from having here too ?

match "fooooooooobar" with | 'f(?o*)bar' -> o | '(?.+)(?o*)bar' -> h | _ -> "none"
"ooooooooo"
match "fooooooooobar" with | 'a(?o*)bar' -> o | '(?.+)(?o*)bar' -> h | _ -> "none"
"fooooooooobar"
match "fooooooooobar" with | 'a(?o*)bar' -> o | '(?.+)(?o*)bar' -> hd | _ -> "none"
"fooooooooobar"
match "fooooooooobar" with | 'a(?o*)bar' -> o | '(?.)(?o*)bar' -> hd | _ -> "none"
"f"
match "fooooooooobar" with | 'a(?o*)bar' -> o | '(?.+)(?o*)bar' -> hd | _ -> "none"
"fooooooooobar"

Yes, good points about the regex binding code.  That support was initially added with just the 2-row either/or match in mind.  It's worth a second look.


Rename "default" views to "home" views

As discussed on CZO, we should rename "default" views to "home" views in the settings and the help center (and any other doc?) where they are discussed.

CZO thread

@sahil839 would you be up for taking care of this one? I'd like to have it done quickly, so that we have the terminology we want by the time Inbox rolls out to Zulip Cloud.

Closing this now since we have updated the database and API fields as well in #27388.


Bugfix: Sofa read test results in modifies files

Which issue(s) are closed by this pull request?
Closes #41
Changes proposed in this pull request:

The function generate_test_sofas was called in generate_test_io_data.py. This resulted in a recreation of the test files due to its import in test_io.py, further causing git to indicate them as modified.

Upsi, nice cheating during testing then I guess :)


SARAALERT-1649: Column Sort should result in all null and blank values appearing at the bottom

Description
Jira Ticket: SARAALERT-###
Write out a concise summary of this pull request and what it addresses.
For column sorts within Sara Alert, Null values are always sorted to be at the bottom of the list regardless of sort direction. But for blank values (values that held a value at one point that were then cleared out by the monitoree) currently are not sorted the same way. Revise the column sorting logic for all applicable columns to ensure that blank values are sorted to the end of the list regardless of sort direction where Null values are also sorted.
Important Changes
Please list important files (meaning substantial or integral to the PR) along with a list of the general changes that should be highlighted for reviewers.
example_file.js

Example change (ex: refactored import function)

Testing Recommendations
Please list any recommendations regarding what reviewers should test and if there is any specific guidance on how to test certain aspects of the PR. Be sure to mention edge cases that should be tried, particularly in the UI.
Checklists
Submitter:

[x] This PR describes why these changes were made.
[x] This PR is into the correct branch.
[x] This PR includes the correct JIRA ticket reference.
[x] Comment added to the relevant JIRA ticket(s) with a link to this PR
[x] Code diff has been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
[ ] If UI changes have been made, Chrome Dev Tools Lighthouse accessibility test has been executed to ensure no 508 issues were introduced.
[x] Tests are included and test edge cases
[x] Tests have been run locally and pass (remember to update Gemfile when applicable)
[x] Test fixtures updated and documented as necessary

@sgober :

[x] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[x] The tests appropriately test the new code, including edge cases
[x] You have tried to break the code
[ ] If applicable, you have tested changes against a large database, and considered possible performance regressions
[ ] Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

@tstrass :

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code
[ ] If applicable, you have tested changes against a large database, and considered possible performance regressions
[ ] Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

@deastman :

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code
[ ] If applicable, you have tested changes against a large database, and considered possible performance regressions
[ ] Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

There was one spot I noticed that didn't behave like the rest, which was the pulse ox column in the assessments table. Otherwise looks good to me

https://github.com/SaraAlert/SaraAlert/pull/1183/commits/b945dd0a9812655ed6c2d2804652da0b85c2f9dd

Under Lab Results, it looks like Type, Specimen Collected, Report, and Result still has blanks sorted at the top when blank values appear in those cols.

Under Lab Results, it looks like Type, Specimen Collected, Report, and Result still has blanks sorted at the top when blank values appear in those cols.

This is a legacy table that I am currently refactoring in SARAALERT-1527.  I already handled this sorting post refactor and it will be included as a part of that PR


Automated Panel Packs

Find a way to select fields to be generated in panel pack and automatically combined with candidate assessments and independent assessments received.
May require further development for panels beforehand so may need to shift
MVP

[ ] SPIKE - combine content from uploaded files into a single Google document.

[ ] Integration with google drive including docs and sheets with platform

[ ] area in admin where you add the drive for the exercise. Suggest you can use a search in a drop down menu to find the drive if already created BUT also create it if you have not done so. Suggest this goes in vacancy information

[ ] Create a task area called 'Panels'. In this area teams will add panel names and the individual members within that panel. Suggest an 'add panel' button and then a modal appears for 'Name of panel', 'Interview dates', and a section called 'Members' where they can type a name for the Chair: , Independent:, Judicial:,Other:__. There should be an option to add another 'Other' just in case we have panels of more than 4. As the panels are created a folder is created in the google drive. For example the following folders Panel 1, Panel 2, Panel 3 and within those panels there is a folder for each Panel member. So if you had say Panel 7 with Tom Russell, Warren Searle and Jeremy Suarez a folder is created in the exercise drive 'Panel 7' and then within that folder there are subfolders called 'Tom Russell' 'Warren Searle' 'Jeremy Suarez'.

Eventually this area will connect to the panellists app so would suggest they can auto search for users who have been added to that app into the future.

[ ] Add 'Assign to panel' button in each of the stages. The team click the check box and add the candidates they want to each panel. Those names then appear under the panel in the tasks.

[ ] From the 'Panels' area there will be a button to 'Export panel packs'. When they click this they appear in google.

[ ] The specific packs for each panel appear in each of the panel members folders on google drive. So in our above example folders for each candidate appear in the Tom Russell, Warren Searle and Jeremy Suarez folders. If the download happened at 'Review' stage the folder is named after the Application reference. For simplicity this should only be the digits after the -. Ie. JAC00351-fiz0003 would be fiz0003. BUT if they are in 'Selected' and the status is 'invited to selection day' the folder needs to be their Name as this is not name blind.

[ ] The panel pack needs to be updated so they are all in Arial, font size 11 and all the headings are in bold. The independent assessor details must be removed. These are not required in the pack as they get the actual assessments to read.

[ ] Within the folder for each candidate the following documents need to appear:

the panel pack: https://admin-staging.judicialappointments.digital/exercises/5YbFGOQ8TagXkO4RZfEO/application/VcvlNysWH0GsGtnOtHx6#panel
the independent assessments that were sent in (these will be in independent assessments - tasks). There are normally but may only be 1.
Anything the candidate had to upload such as a candidate assessment. These appear at the bottom of the panel pack as attachments but need to be added to the folder as well. This could be more than one document and they will need to appear separately.
A list to keep track of their scores. You will need to ask Kate Malone to find an example

[ ] Suggest the following names: 'Application' for 1, 'Independent Assessment 1' and/or  'Independent Assessment 2' for 2. and for 3 whatever the file is called e.g. 'candidate assessment'.

[ ] The team will keep a record of scores in a sheet. We need to add an 'Import to digital platform' button to this sheet for when it is ready. It will then populated scores under 'Reports' in a report called 'Merit list'. There will be future work here but for now it will just be a mechanism to keep a record of the scores put into google drive. It will also inform which emails certain candidates get.

@joy-ade you need to ticket this up first thing when back.

@KateMJAC top priority when back.

Joy and Kate to seek advice from SEOs re file structures and benefit of combining files.

Joy and Kate to seek advice from SEOs re file structures and benefit of combining files.

@KateMJAC @joy-ade @lloback @warrensearle in our meeting today we discussed breaking this epic down into the following parts:

Create Panel & Add Panelists (user stories; scenarios, visual)

Specify google drive to use

Assign Candidates to Panel
Generate Files & Copy to Folder Structure (the magic! approx 20 SPs)

We also have the following questions / spikes:

Can team provide us sufficient permissions to access Google Drives
Can we add permissions to Drive folders?

@KateMJAC @joy-ade @lloback @warrensearle in our meeting today we discussed breaking this epic down into the following parts:

Create Panel & Add Panelists (user stories; scenarios, visual)

Specify google drive to use

Assign Candidates to Panel
Generate Files & Copy to Folder Structure (the magic! approx 20 SPs)

We also have the following questions / spikes:

Can team provide us sufficient permissions to access Google Drives
Can we add permissions to Drive folders?


fix #1645 adding until 12 indent levels

@lukasj
It's not the best solution, but fixes 8 indentation levels, adding until 12.
Please rate this PR if you think it is appropriate to solve the issue.
Regards,
Antonio.

This will fix https://github.com/eclipse-ee4j/jaxb-ri/issues/1645 is there any reason to not proceed on this?

Hi any news on this one?


Problems validating SSL certificate

This happens to me only on AWS Ec2 instances.
Every time an app inside the container (or during building of the image) needs to setup an SSL connection, it fails (error is for example SSL certificate problem: unable to get local issuer certificate). For example: wordpress connecting to its plugin repository, pip install while building of the image, etc.
I usually install ca-certificates inside the image, but this does not solve the problem.
Am I the only one with this problem?

@bitliner can you please provide more information on your environment? docker version, docker info, uname -a, if possible the AMI ID too.

Are you sure SSL works on the EC2 instance, outside of Docker?

@tiborvass yes, SSL works on the EC2 instance outside of the container.
I was thinking it is the not updated kernel that causes the error, but I have still to reboot the machine to be sure of it. As soon as I will do it, I will let you know

@bitliner any update on this?

Not yet. If I find enough time this week I will do it, otherwise the machine is not going to be available anymore since next week.

I'm going to close this for now, but if you can provide some extra details please ping here and we can discuss.
Thanks!

+1, stuck on this for a while

I'm having the same problem

Cert is only installed on host (but obviously found by container)

@senj how do you mean "obviously found by container"? If the cert is not present inside the container, it cannot use it

yes, I installed it inside container and works now. Must have been some
not-updatet state.
Am 29.02.2016 12:43 nachm. schrieb "Sebastiaan van Stijn" <
<EMAIL_ADDRESS>
Cert is only installed on host (but obviously found by container)
@senj https://github.com/senj how do you mean "obviously found by
container"? If the cert is not present inside the container, it cannot use
it
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/10554#issuecomment-190172089.


[ERR] BIDS validator issue 01: odd duplicate names

TODO

[ ] Need to manually resolve or feed it through Heudiconv

fmriprep output
	1: [ERR] Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder. (code: 1 - NOT_INCLUDED)
		./sub-0016/ses-01/fmap/sub-0016_ses-01_acq-mb8_dir-ap_run+-PVC-run-04_epi.json
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0016_ses-01_acq-mb8_dir-ap_run+-PVC-run-04_epi.json
		./sub-0016/ses-01/fmap/sub-0016_ses-01_acq-mb8_dir-ap_run+-PVC-run-04_epi.nii.gz
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0016_ses-01_acq-mb8_dir-ap_run+-PVC-run-04_epi.nii.gz
		./sub-0016/ses-01/fmap/sub-0016_ses-01_acq-mb8_dir-pa_run=-PVS-run-04_epi.json
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0016_ses-01_acq-mb8_dir-pa_run=-PVS-run-04_epi.json
		./sub-0016/ses-01/fmap/sub-0016_ses-01_acq-mb8_dir-pa_run=-PVS-run-04_epi.nii.gz
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0016_ses-01_acq-mb8_dir-pa_run=-PVS-run-04_epi.nii.gz
		./sub-0017/ses-01/fmap/sub-0017_ses-01_acq-mb8_dir-ap_alignvideos_run-02_epi.json
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0017_ses-01_acq-mb8_dir-ap_alignvideos_run-02_epi.json
		./sub-0017/ses-01/fmap/sub-0017_ses-01_acq-mb8_dir-ap_alignvideos_run-02_epi.nii.gz
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0017_ses-01_acq-mb8_dir-ap_alignvideos_run-02_epi.nii.gz
		./sub-0017/ses-01/fmap/sub-0017_ses-01_acq-mb8_dir-pa_alignvideos_run-02_epi.json
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0017_ses-01_acq-mb8_dir-pa_alignvideos_run-02_epi.json
		./sub-0017/ses-01/fmap/sub-0017_ses-01_acq-mb8_dir-pa_alignvideos_run-02_epi.nii.gz
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0017_ses-01_acq-mb8_dir-pa_alignvideos_run-02_epi.nii.gz
		./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_bold.json
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0025_ses-03_task-social_acq-mb8_51_run-03_bold.json
		./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_bold.nii.gz
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0025_ses-03_task-social_acq-mb8_51_run-03_bold.nii.gz
		./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_sbref.json
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0025_ses-03_task-social_acq-mb8_51_run-03_sbref.json
		./sub-0025/ses-03/func/sub-0025_ses-03_task-social_acq-mb8_51_run-03_sbref.nii.gz
			Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
			Evidence: sub-0025_ses-03_task-social_acq-mb8_51_run-03_sbref.nii.gz

scannotes
(Insert scannotes from ST_participants)

More:
./sub-0050/ses-02/fmap/sub-0050_ses-02_acq-mb8_dir-pa_run-51_epi.nii.gz
./sub-0050/ses-02/fmap/sub-0050_ses-02_acq-mb8_dir-ap_run-51_epi.nii.gz
./sub-0023/ses-01/fmap/sub-0023_ses-01_acq-mb8_dir-pa_run-51_epi.nii.gz
./sub-0023/ses-01/fmap/sub-0023_ses-01_acq-mb8_dir-ap_run-51_epi.nii.gz
./sub-0023/ses-02/fmap/sub-0023_ses-02_acq-mb8_dir-pa_run-51_epi.nii.gz
./sub-0023/ses-02/fmap/sub-0023_ses-02_acq-mb8_dir-ap_run-51_epi.nii.gz
./sub-0069/ses-01/fmap/sub-0069_ses-01_acq-mb8_dir-pa_run-51_epi.nii.gz
./sub-0069/ses-01/fmap/sub-0069_ses-01_acq-mb8_dir-ap_run-51_epi.nii.gz

(base) [f0042x1@discovery-01 fmap]$ grep '"AcquisitionTime": "' sub-0050_ses-02_acq-mb8_dir-pa*epi.json
sub-0050_ses-02_acq-mb8_dir-pa_run-01_epi.json:  "AcquisitionTime": "16:21:20.342500",
sub-0050_ses-02_acq-mb8_dir-pa_run-02_epi.json:  "AcquisitionTime": "17:35:45.365000",
sub-0050_ses-02_acq-mb8_dir-pa_run-51_epi.json:  "AcquisitionTime": "17:17:34.347500",

[ ] rename run-02 to run-03
[ ] code/rename_file --swap --all-extensions sub-0050/ses-02/fmap/sub-0050_ses-02_acq-mb8_dir-pa_run-{02,03}_epi.json
[ ] code/rename_file --swap --all-extensions sub-0050/ses-02/fmap/sub-0050_ses-02_acq-mb8_dir-ap_run-{02,03}_epi.json
[x] rename run-51 to run-02
[x] code/rename_file --swap --all-extensions sub-0050/ses-02/fmap/sub-0050_ses-02_acq-mb8_dir-ap_run-{51,02}_epi.json
\


use relative paths when constructing path resolves #48

whats the reasoning behind this change? Is this causing an issue somewhere?

@jonaldomo Thanks for the PR!  We'll need to add a test or two to ensure this behavior doesn't break again in the future.  If you can do that, great - if not I can.
I'll also need to bump the Gem version here since everything runs through Validic::Request.

@alex-bezek It is not causing an issue currently.  It would if the api URL went from api.validic.com to www.validic.com/api/  The /api/ would be removed from all calls.
@allcentury If you could please that would be great!


Confluent Integration (phase 1)

Very simple deployment of the Confluent Platform Kafka brokers in place of Apache Kafka.

Thank you @dbtucker!


Update syn and friends to v1

I was curious why syn v0.15 still has so many downloads. I think this may be the main culprit :grin:
This updates all of the proc_macro related bits to v1. I'm planning on updating syn to v2, but figured breaking things into two PRs would make reviewing easier. The changes are largely:

Handling Meta::Word(_) -> Meta::Path(_) since this was changed to take arbitrary paths instead of a single ident

Fix: Ensure that the path is just a single ident

IntSuffix got replaced with just returning a &str for the suffix

Fix: Switch all the logic to just use the &str. Could also make our own version of IntSuffix, but wasn't sure if that would be worth it

Tuple and Tuple2 were causing a lot of headaches

Fix: Remove them since they seem unused?

Can we have a new proptest-derive crates.io release please? Thank you!

We can take a look. What specific features are missing from the latest crates.io release


How can I re-enable virtual desktops?

Win + Tab and Ctrl + Win Left/Right don't work and I can't use virtual desktops now. What flags would let me change back this functionality?

Same cause as in #170.
Run powershell as admin and execute following command
Set-Service "CDPUserSvc" -StartupType Automatic

Then reboot and it will work again.


index.md: replace Octocat URL

The current link yields 404 Not Found.
The proposed link comes from an unofficial Gist: https://gist.github.com/johan/1007813 .
Tested in https://coq-community.org/coq-ext-lib/

Maybe worth forking the Gist for better durability?
Otherwise, ready to merge. @Zimmi48

@liyishuai are you interested in becoming officially a co-maintainer of this project?

Yes I'm a heavy user of this template, and am happy to co-maintain it.

OK, I'm going to add you as an admin here.
cc @palmskog FYI

Fine by me.
@liyishuai could you update README.md with maintainer information? Maybe we should use meta.yml to generate the README.md here too...

[ ] #133


Rotating Captured Video

I've used the code here to recreate a video streaming app, and it works well.
The pipeline is Camera2 Capture Session -> Output Surface -> MediaCodec
An issue arises however with video orientation; the video is always in landscape.
On Stackoverflow, the point was made that MediaRecorder merely writes orientation to mp4 metadata to properly set the video orientation. For something like a video stream that has raw h264 NAL units I've tried embedding display orientation metadata in the bitstream, going as far as opening a PR for Exoplayer to support it here.
Unfortunately, most transcoders rip out this metdata when going creating HLS playlist, leaving only raw VLC NAL units untouched. It appears the only way around this is to just manually rotate the video before it is encoded with the MediaCodec.
Is there a simple way to add a video transformation to a surface as it is rendered to?

I've decided using Renderscript to rotate the video before passing it into the MediaCodec is my best bet. Using the HDRViewFinder example as a reference, I can successfully rotate the image, however the colors are off.
I've tried messing with setInteger(MediaFormat.KEY_COLOR_FORMAT, MediaCodecInfo.CodecCapabilities.COLOR_FormatRGBAFlexible) on the mediaCodec to no avail.
My allocations are defined as such:
My renderscript is based on this gist:
https://gist.github.com/LiewJunTung/c39b2db5a5932cedada719c6c9c358b9
        inputAllocation = Allocation.createTyped(
            renderScript,
            yuvTypeBuilder.create(),
            Allocation.USAGE_IO_INPUT or Allocation.USAGE_SCRIPT
        )
        prevAllocation = Allocation.createTyped(
            renderScript,
            rgbTypeBuilder.create(),
            Allocation.USAGE_SCRIPT
        )
        outputAllocation = Allocation.createTyped(
            renderScript,
            rgbTypeBuilder.create(),
            Allocation.USAGE_IO_OUTPUT or Allocation.USAGE_SCRIPT
        )

The colors were off bc the input allocation was in the YUV color format and the script was using rsGetElementAt for the transformations. This was fixed with the following snippet gleaned from the HDRViewFinder sample:
    uchar4 currentPixel;
    currentPixel.r = rsGetElementAtYuv_uchar_Y(inImage, inX, inY);
    currentPixel.g = rsGetElementAtYuv_uchar_U(inImage, inX, inY);
    currentPixel.b = rsGetElementAtYuv_uchar_V(inImage, inX, inY);
    currentPixel.a = 255;

    int4 rgb;
    rgb.r = currentPixel.r +
            currentPixel.b * 1436 / 1024 - 179;
    rgb.g = currentPixel.r -
            currentPixel.g * 46549 / 131072 + 44 -
            currentPixel.b * 93604 / 131072 + 91;
    rgb.b = currentPixel.r +
            currentPixel.g * 1814 / 1024 - 227;
    rgb.a = 255;

    uchar4 out = convert_uchar4(clamp(rgb, 0, 255));


Feature/universal config

This is not a formal pull request.
The changes in this branch are not part of master, they should be reviewed then integrated or discarded

Thanks, I'll delete the branch now


export Maplshared module

Export MAPL Shared modules
Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Trivial change (affects only documentation or cleanup)

Checklist:

[ ] I have tested this change with a run of GEOSgcm (if non-trivial)
[x] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[x] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

Ahh. Speak of the devil... I assume this is needed for the GOCART DSO work. Yeah. Let's ask @tclune if we want to do this or not.

It is closed because adjust_dso_name is no longer needed outside of MAPL


[Torch][Codegen] SymbolNet -> torch.fx.GraphModule

This PR allows symbolnet's forward function to be cleanly traced by torch.fx.symbolic_trace in order to create a fx.GraphModule which can dump model code --> an essential step for producing torch code at Python level to reproduce bugs.

As a quick proof-of-concept:
S0: make a random model
python nnsmith/cli/model_gen.py model.type=torch backend.type=torchjit debug.viz=1

S1: generate the model code
from nnsmith.materialize.torch import TorchModelCPU
from nnsmith.materialize.torch.symbolnet import FxTracing

tmodel = TorchModelCPU.load("nnsmith_output/model.pth")

import torch

with FxTracing():
    traced = torch.fx.symbolic_trace(tmodel.native_model)
    traced.to_folder("gen")

Then we check gen/module.py, we can get something very nice:

Ack: Above codegen feature was also implemented by the NeuRI experimental repo, which uses a more native implementation -- templates + string maniputation + eval, etc. Based on that experience, we offload the effort to torch.fx which has official support for doing codegen.

Need to figure out how to do jit.trace over a dictionary...

Need to figure out how to do jit.trace over a dictionary...

Turns out we cannot if we want to stick on one forward function. So we have to listify the arguments in forward and putting them back to the tensor_map according to input_map / input_like.

@Co1lin  More concretely, I think the next steps are:

upstream the inductor backend
do complete codegen including the backend + diff test.
I will be working on that soon.


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1638

Questions ?
Please refer to the Backport tool documentation


fix:incorrect parameter passing causes captured errors to be lost

@lazyironf4ur Thanks for your contribution! ❤


[Bug] incognito mode

Device information

Neko version: v2.5.3
Android phone & version: 10 or G & V8.1.0

Steps to reproduce

First step : turn-on incognito mode.
Second step : read any manga till it's latest chapter. Then remove neko from recent tabs of phone.

Expected behavior
This should happen. Pauses reading history and not mark chapters as read.
Actual behavior
This happened instead. Marked chapters as read and later after reading the whole manga and closing neko, the manga showed in history.
Other details
Additional details and attachments.

in  5.2.4


Which Licence is this code released as?

Hi @dinex86,
I've the developer of DisplayMagician, a free and open source display manager specially designed for Simracing, and I'd love to use parts of your logic in DisplayMagician (not the code, just the logic). I note you don't have a licence in the github repo, so I wanted to reach out to ask if I could use the logic you have created within DisplayMagician?
I would make sure you are credited in the DisplayMagician README file, and the release notes.
Is that ok?
Thanks
Terry MacDonald

Hey @terrymacdonald,
thanks for reaching out to me! You can use my logic and the credit in your README is very much appreciated!
Best regards
Markus

Awesome news! Thank you so much for your permission. And especially thank
you so much for inspiring me to add a FOV calc to my code. Keep up the
great work.
Thanks
Terry
On Fri, 5 Aug 2022, 19:55 Markus Ewert, @.***> wrote:

Closed #7 https://github.com/dinex86/FOV-Calculator/issues/7 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/dinex86/FOV-Calculator/issues/7#event-7133855379, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLU5LFMRSPLNBFX3DYVZ3LVXTCG5ANCNFSM55Q4FNIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add troubleshooting entry on sagas freezing the app

Just had this happen to me :smile:

Yeah. Experienced that too :)


Autoplay doesn't continue after last episode of favorite show

Expected Behavior

When I reach the end of the last episode of my favorite anime, I want to continue watching. Additional episodes of the series should be generated and autoplayed in this case.
Current Behavior

When I reach the end of the last episode, there is only silence. I see my reflection staring back.
Steps to Reproduce

Open first episode of Neon Genesis Evangelion in Chrome with wco-autoplay extension enabled
Play video and enjoy the pilot
Continue watching through the end of the series
Continue watching through the end of the movies
Feel the problem wash over you

Context (Environment)

Version: 1.0
OS: macOS 11.5.2 (20G95)
Browser: Google Chrome 92.0.4515.159 (Official Build) (x86_64)

Congratulations!

Thank you! That did the trick.


fP for TLC SXL before 1.1?

In 1.1 we depreciated fP and fS in aggregated status and required that they be set to null, see #90.
But what value should be used for earlier versions? An empty string?
The rsmp gem must set fP and fS to some value in earlier version.
See also https://github.com/rsmp-nordic/rsmp/issues/11.

closing this, as this is a core issue