Perform Weekly Label check

Overview
We need to perform a weekly check on issues to make sure they all conform to our label and milestone schema.
Action Items

[ ] Check the following to make sure that they are all 0/0 (Links for checking to make sure that all issues either have a ___ or a ____ missing label)

[ ] Role
[ ] size
[ ] feature

[ ] Add any label missing (e.g., a new feature label go added to the project, but didn't yet get added here) and update link

[ ] issues that have not yet been added to project board

[ ] add to project board

[ ] if changes were made, recheck to make sure all links ended up 0/0
[ ] Audit for issues with Missing labels (to determine if we are making progress)

[ ] #51

Date:
- [ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
- [ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)
   - [ ] role, ending at
   - [ ] size, ending at
   - [ ] features, ending at
   - [ ] milestone, ending at

[ ] perform audit, adding your numbers to your audit report comment

[ ] Role
[ ] size
[ ] feature
[ ] milestone

Icebox issue

[ ] Icebox Issues w no dependency

@JasonEb I finished the first draft of this issue.  I have added it to the next agenda 2022-04-03 (2 Sundays from now), and we can discuss then what we  need to do to move it out of the new issue approval column and into being assigned to you.  We can't assign it now, because it's missing some items, but we can talk about that when we meet.

Date:

[x] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
added missing labels for all categories to create a new baseline
[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 15/2
[ ] size, ending at 16/2
[ ] features, ending at 13/2

Date: 2022-06-12

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at
[ ] size, ending at
[ ] features, ending at
[ ] milestone, ending at

Date: 2022-06-19

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).

No

[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 2/2
[ ] size, ending at 4/2
[ ] features, ending at 1/2
[ ] milestone, ending at 12/2

Date: 6/26/2022

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
[x] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 0/1
[ ] size, ending at 1/2
[ ] features, ending at 0/2
[ ] milestone, ending at 12/2

Date: 7/17/22

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 0/1
[ ] size, ending at 0/2
[ ] features, ending at 0/2
[ ] milestone, ending at  13/2

Date: 2022-07-17

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 0
[ ] size, ending at 0
[ ] features, ending at 0
[ ] milestone, ending at 14/1

Date: 8/21

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 0/0
[ ] size, ending at 0/0
[ ] features, ending at 2/0
[ ] milestone, ending at 3/6

Date: 8/28

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 0/1
[ ] size, ending at 0/0
[ ] features, ending at 2/1
[ ] milestone, ending at 2/8

Date: 9/11

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).

Updated Weekly Label check to have role: security engineer & feature: docker in the missing filters check

[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 1/1
[ ] size, ending at 1/1
[ ] features, ending at 3/1
[ ] milestone, ending at 5/8

Date: 9/18/2022

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).

added 'size: 0.25pt' and 'feature: security' to filters
added gh-pages repo bot issues to project board

[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 0/0
[ ] size, ending at 0/0
[ ] features, ending at 0/0
[ ] milestone, ending at 4/8

Date: 10/2/2022

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).

added 'size: 0.25pt' and 'feature: security' to filters
added gh-pages repo bot issues to project board

[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 0/0
[ ] size, ending at 0/0
[ ] features, ending at 0/0
[ ] milestone, ending at 4/8

Date: 10/16/2022

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).

mainly added labels to daniel bot ridge issues

[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 0/0
[ ] size, ending at 0/0
[ ] features, ending at 0/0
[ ] milestone, ending at 0/2

Date: 10/2/2022

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 0/0
[ ] size, ending at 0/0
[ ] features, ending at 0/0
[ ] milestone, ending at 0/2

Date: 11/13/2022

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).

added 'role: project representative' to missing role labels query

[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 0/0
[ ] size, ending at 0/0
[ ] features, ending at 0/0
[ ] milestone, ending at 0/2

Date: 11/20/2022
Did you have to update the 0/0 links above? if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
role, ending at 1/0
size, ending at 0/0
features, ending at 0/0
milestone, ending at 0/0

Date: 1/29/2023

[x] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).

added -label:"feature: security" -label:"feature: maintenance" -label:"feature: deployment"  to features 0/0 check

[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at 0/0
[ ] size, ending at 0/0
[ ] features, ending at 0/0
[ ] milestone, ending at 0/0

Date: 2024-09-26

[ ] Did you have to update the 0/0 links above?  If yes, please say what you did (e.g, added features to the features check above or added an issue to the project board that has not been added yet).

added 6 issues to the project board, added missing labels to https://github.com/hackforla/ops/issues/144

[ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at
[ ] size, ending at
[ ] features, ending at
[ ] milestone, ending at

Date: 10/2/2024

[ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
On ops repo - report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at
[ ] size, ending at
[ ] features, ending at
[ ] milestone, ending at

On devops-security repo - report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at
[ ] size, ending at
[ ] features, ending at
[ ] milestone, ending at

On incubator repo - report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)

[ ] role, ending at
[ ] size, ending at
[ ] features, ending at
[ ] milestone, ending at

On project board, Icebox

[ ] Icebox Issues w no dependency 3


Update dependencies and os support

This fixes #10 and #11

@bodgit I'll close this one,as it is obsolte now. Thanks for updating!


Fix trim

Revert trim command to trim all whitespace by default (fixing docker build)

Uh oh this one got some conflicts :(

Ive got 5mins let me look

Merged cleanly but I didn’t have time to test!

This looks good to me! :shipit:


use emr role directly from ecs meta service

What changes were proposed in this pull request?
use ecs metaservice first, if failed, will fall back to original localhost:10011
How was this patch tested?
tested using spark DStream
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(Refer to this test guide)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.huanjian.lq seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Invalid JSON returned for /containers/create

Description
The below is the response body for a POST (uri)/containers/create?name=(name) and it is malformed JSON but valid JS. This is an issue because JSON.parse cannot handle the response. Instead we have to resort to using eval() on the response.
Actual repsonse:
{ Id: '604e48f4b7a650340b43c0bbb139d334edf63fe3476f2e503877b3e2c8cc1a2a',
  Warnings: null }

Should be:
{ "Id": "604e48f4b7a650340b43c0bbb139d334edf63fe3476f2e503877b3e2c8cc1a2a",
  "Warnings": null }

Steps to reproduce the issue:

Make any valid /containers/create request to a engine remote
Run JSON.parse on the response's body
Handle error SyntaxError: Unexpected token o in JSON at position 1

Describe the results you received:
I received invalid JSON on a http response that should yield valid JSON for the content-type "application/json"
Describe the results you expected:
Valid json that meets RFC7159 specification  https://tools.ietf.org/html/rfc7159
Specifically the part that says "A string begins and ends with quotation marks."
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Docker version 1.12.1, build 23cf638

Output of docker info:
Containers: 8
 Running: 0
 Paused: 0
 Stopped: 8
Images: 10
Server Version: 1.12.1
Storage Driver: devicemapper
 Pool Name: docker-253:0-202281288-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 932.2 MB
 Data Space Total: 107.4 GB
 Data Space Available: 33.4 GB
 Metadata Space Used: 2.22 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.145 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2016-06-09)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-327.36.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.703 GiB
Name: vm
ID: RPLT:DWEL:LJBT:54Z6:H2KO:44F5:2NQB:BL6K:L7IT:UCMJ:OYQH:UT6Z
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 17
 Goroutines: 26
 System Time: 2016-10-16T09:59:17.159342406-04:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
I'm running Centos 7 in VirtualBox Version 5.1.6 r110634 (Qt5.5.1)
I can replicate this on my DigitalOcean VPS running Centos7 as well.
I encountered this while writing a NodeJS library https://github.com/matutter/docker-as-promised/tree/dev

After updating to Docker version 1.12.2, build bb80604 the issue remains.

I'm nog able to reproduce; could this be something in the library you're using?
To reproduce, I used cURL to send a request to the api;
curl -v \
  --unix-socket /var/run/docker.sock \
  "http://localhost/v1.24/containers/create?name=foobar" \
  -H "Content-Type: application/json" \
  -d '{"Image": "nginx:alpine"}'

*   Trying /var/run/docker.sock...
* Connected to localhost (/var/run/docker.sock) port 80 (#0)
> POST /v1.24/containers/create?name=foobar HTTP/1.1
> Host: localhost
> User-Agent: curl/7.50.3
> Accept: */*
> Content-Type: application/json
> Content-Length: 25
>
* upload completely sent off: 25 out of 25 bytes
< HTTP/1.1 201 Created
< Content-Type: application/json
< Server: Docker/1.12.2 (linux)
< Date: Mon, 17 Oct 2016 02:06:47 GMT
< Content-Length: 90
<
{"Id":"a4983e725bc6011a04daa87eaa3bf109501fb717117d730b04a0c4f92ef8f27a","Warnings":null}
* Curl_http_done: called premature == 0
* Connection #0 to host localhost left intact

Can you try reproducing without using that NodeJS library, and doing a direct call with cURL?

I'm nog able to reproduce; could this be something in the library you're using?
Jeesh, yes it seems like it's feature of one of my dependencies.

Not a bug.

Thanks for confirming @matutter, and thanks for reporting as it could've been a bug :smile:


Corrected URL to test file.

Thanks for catching that :)

No prob, saw your package appear on the haskell.org/news feed :)


[Keccak] Tweak code for rotation offsets.

No functional change, but the number of loop iterations in rho is always 24, regardless of the number of rounds. In our case the number of rounds is also 24, but in my opinion it's cleaner to use 24 for the rho loop, since that's what FIPS 202 uses.

I would suggest keeping the usage of NUM_ROUNDS which itself is derived from 12 + 2 * l where l = 6 as defined by the standard.

The proposed change is only for the loop in rotl_offsets, which is always 24 iterations, no matter what the number of rounds is. It's in Section 3.2.2 of FIPS 202, where t goes from 0 to 23, as part of the definition of rho:

The number of rounds n_r comes into play in Section 3.3, in the loop in Algorithm 7, which is instantiated to 12 + 2  * l as you say (in Section 3.4):

The proposed commit doesn't modify permutation_f, which still uses NUM_ROUNDS.

Agreed, on secondary inspection, the Keccak team specs also hardcode 23. In this case, let's proceed with this PR.


Unable to handle pdf error with try/catch

Hi,
I stumbled upon a problem using pdfjs-lib while iterating over a folder of pdf files.
The reproduction code is rather simple:
const pdfjsLib = require('pdfjs-dist/es5/build/pdf.js');

(async function() {
  try {
    const pdf = await pdfjsLib.getDocument(__dirname).promise;
  } catch (error) {
    console.log('catched...');
  }
})();

Instead of catching the error, I get:
$ node test.js
(node:92567) UnhandledPromiseRejectionWarning: Error
    at BaseExceptionClosure (/Users/nscheer/application/stuff/await/node_modules/pdfjs-dist/es5/build/pdf.worker.js:1790:29)
    at Object.<anonymous> (/Users/nscheer/application/stuff/await/node_modules/pdfjs-dist/es5/build/pdf.worker.js:1793:2)
    at __w_pdfjs_require__ (/Users/nscheer/application/stuff/await/node_modules/pdfjs-dist/es5/build/pdf.worker.js:52:30)
    at Object.<anonymous> (/Users/nscheer/application/stuff/await/node_modules/pdfjs-dist/es5/build/pdf.worker.js:147:13)
    at __w_pdfjs_require__ (/Users/nscheer/application/stuff/await/node_modules/pdfjs-dist/es5/build/pdf.worker.js:52:30)
    at Object.<anonymous> (/Users/nscheer/application/stuff/await/node_modules/pdfjs-dist/es5/build/pdf.worker.js:129:23)
    at __w_pdfjs_require__ (/Users/nscheer/application/stuff/await/node_modules/pdfjs-dist/es5/build/pdf.worker.js:52:30)
    at /Users/nscheer/application/stuff/await/node_modules/pdfjs-dist/es5/build/pdf.worker.js:116:18
    at /Users/nscheer/application/stuff/await/node_modules/pdfjs-dist/es5/build/pdf.worker.js:119:10
    at webpackUniversalModuleDefinition (/Users/nscheer/application/stuff/await/node_modules/pdfjs-dist/es5/build/pdf.worker.js:25:20)
(node:92567) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:92567) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I know this is a somewhat contrived example but has happened like this due to a bug.
Another instance, but very difficult to debug, because the files are on a mounted samba share:
(node:1) UnhandledPromiseRejectionWarning: Error: Bad end offset: 2193
    at ChunkedStream.onReceiveData (/usr/src/app/node_modules/pdfjs-dist/es5/build/pdf.worker.js:12255:15)
    at ChunkedStreamManager.onReceiveData (/usr/src/app/node_modules/pdfjs-dist/es5/build/pdf.worker.js:12818:21)
    at /usr/src/app/node_modules/pdfjs-dist/es5/build/pdf.worker.js:12602:15
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

My best guess here is, that the file was not completely written, yet.
Anyways, I'd expect to be able to catch these things using try/catch.
I have basic knowledge about what a UnhandledPromiseRejectionWarning is and that it can be produced by breaking a promise chain.
Is this something that must be handled by adjusting pdfjs? Or am I able to handle/catch these errors myself?
I know I can register a callback for unhandledRejection - but that totally breaks code flow.
My setup is as follows:

node v12.18.3 / docker node:12-alpine
MacOS X 10.15.6 / Ubuntu 18.04.3
PDF.js version<EMAIL_ADDRESS>
Greetings
Nico

The reproduction code is rather simple:
const pdfjsLib = require('pdfjs-dist/es5/build/pdf.js');

(async function() {
  try {
    const pdf = await pdfjsLib.getDocument(__dirname).promise;
  } catch (error) {
    console.log('catched...');
  }
})();

Instead of catching the error, I get:

I've just tested the above snippet, with both the master branch and the 2.6.347 release (i.e. the current beta version), and the error was caught just as you'd expect. Hence I can only assume that whatever the problem was, has since been fixed. (I don't have time to try and bisect exactly what fixed it though.)

Another instance, but very difficult to debug, because the files are on a mounted samba share:

Without an actual test-case, it's unfortunately not really possible to help with this.

All-in-all, I think we can close this as fixed now!?


fix(space-widgets): fix for joining meeting using SIP destination

After the change done as part of PR: https://github.com/webex/react-widgets/pull/1337, joining meetings using SIP URI stopped working.
Jira:  https://jira-eng-gpk2.cisco.com/jira/browse/SPARK-505404
This happened due to the check added for fetching the meeting info based on the conversation URL which was impacting the SIP URI cases as well for guest users.
Fixed the check and it is working for SIP URI but not for the RoomID
Below were tested for Guest Users as well as Licensed Users. The screenshot and behaviour mentioned are for guest users. For licensed users, all the flows are working.
Testcase 1:

Select Destination Type: To Space
Select Initial Activity: Meet
Select Activities: Check all 4: Files, Meet, Message, People
Enter Space ID in the Widget Destination textbox
Open Space Widget

Error element should appear stating 'Your account currently does not have the ability to start a meeting.'

Testcase 2:

Select Destination Type: To Space
Select Initial Activity: Message
Select Activities: Check all 4: Files, Meet, Message, People
Enter Space ID in the Widget Destination textbox
Open Space Widget

Meet Button on top right is disabled

Testcase 3:

Select Destination Type: To SIP URI
Select Initial Activity: Meet
Select Activities: Check all 4: Files, Meet, Message, People
Enter SIP URI in the Widget Destination textbox
Open Space Widget

Guest should be able to join or start meeting.

Can we expand on all the tests attempted? Also, I think we should be able to create a meeting using a conversation URL. Please check the kitchen sink page where this is a way to create a meeting in a space. I think we are only supposed to block based on roomId. See this developer API for rooms which is different from conversationURL.

In space-widgets, option to join using the conversation URL is not present. We are only blocking roomID scenario.

Can you verify if within the space widget an error and tooltip both shows correct ?

 Can you verify if within the space widget an error and tooltip both shows correct ?

Updated the screenshot where tooltip is also visible

 Can you verify if within the space widget an error and tooltip both shows correct ?

Updated the screenshot in the description where tooltip is also visible

Thanks @Kesari3008


[DOC] Publish bedrock multimodal connector

What do you want to do?
Please add documentation for our bedrock multimodal connector, and include it in our list of supported connectors: https://opensearch.org/docs/latest/ml-commons-plugin/remote-models/connectors/#supported-connectors
https://github.com/opensearch-project/ml-commons/blob/2.x/docs/remote_inference_blueprints/bedrock_connector_titan_multimodal_embedding_blueprint.md

[ ] Request a change to existing documentation
[ x] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

Thanks, @dylan-tong-aws. Is this connector currently supported and in which versions of OpenSearch? Can we use the linked content from GitHub as-is or will you provide additional guidance on what needs to be changed?


Update Data Management.md

Description
Please include a summary of the change.
Why
Please include an explanation of why this change is necessary as well as relevant motivation and context. List any dependencies that are required for this change.
Issue
Link to Github issue.
Checklist
Please delete options that are not relevant.

[ ] I have followed the contributing guidelines
[ ] I have performed IP checks for added or updated 3rd party libraries
[ ] I have created and linked IP issues or requested their creation by a committer
[ ] I have performed a self-review of my own code
[ ] I have successfully tested my changes locally
[ ] I have added tests that prove my changes work
[ ] I have checked that new and existing tests pass locally with my changes
[ ] I have commented my code, particularly in hard-to-understand areas

will get squashed and transferred to eclipse as soon as the changes are all incorporated


sample hangs, NPU 0%, GPU 100%

Running this on a new Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) CPU, 4012 Mhz, 12 Core(s), 12 Logical Processor(s)
Form shows, I tried several inputs - but always same result, progress bar shows forever: NPU 0%,  GPU 100%
expected: get an answer or error, see NPU usage
should that sample work on a Copilot+ laptop?

I got the same but debugging it I found I had to put the model in the bin\x64\Debug\net6.0-windows10.0.19041.0\AppX\phi3\. Once I got this setup had to set the developer mode on. After that the app launched and got it to work. There is a hard coded 1024 max token limit which means you will have another hang when your tokens reach above that limit.


Template string syntax stop working

Hi, i update to last vesion and template strings with highlight stop working.

Version: 1.26.0 x64, windows 7

Thanks very much for the report!
I assume that's JavaScript?  If so, would you mind reopening this issue in the https://github.com/atom/language-javascript repository? We use multiple repositories to keep the work items tied to the code they apply to. This helps the maintainers spend more time working directly on Atom and less time triaging issues.
Please fill out the issue template as well, the information in the template is super helpful for us when triaging issues.
Thanks for meeting us half way 👍


Add New species section in FAQs

Species: You can enter new species and species not yet in our system in the “New species” box in the Overview section. Enter one species per line.

done


LUCI presubmit check stuck pending due to buildbucket 500

https://github.com/flutter/flutter/pull/85999/checks?check_run_id=3139440792
This had one check that returned a 500, which caused it to be stuck pending. Cocoon should have retried to schedule the build.
Processing pull_request
Processing synchronize for https://github.com/flutter/flutter/pull/85999
Scheduling tasks if mergeable(null): owner=flutter repo=flutter and pr=85999
BuildBucketException: [500]:  <meta http-equiv="content-type" content="text/html;charset=utf-8"> <title>500 Server Error</title>
Error: Server Error

The server encountered an error and could not complete your request.
Please try again in 30 seconds.

  #0 BuildBucketClient._postRequest (package:cocoon_service/src/service/buildbucket.dart:86:5) <asynchronous suspension> #1 BuildBucketClient.batch (package:cocoon_service/src/service/buildbucket.dart:113:36) <asynchronous suspension> #2 LuciBuildService.tryBuildsForRepositoryAndPr (package:cocoon_service/src/service/luci_build_service.dart:115:33) <asynchronous suspension> #3 LuciBuildService.cancelBuilds (package:cocoon_service/src/service/luci_build_service.dart:287:39) <asynchronous suspension> #4 Scheduler.cancelPreSubmitTargets (package:cocoon_service/src/service/scheduler.dart:302:5) <asynchronous suspension> #5 Scheduler.triggerPresubmitTargets (package:cocoon_service/src/service/scheduler.dart:327:5) <asynchronous suspension> #6 GithubWebhook._scheduleIfMergeable (package:cocoon_service/src/request_handlers/github_webhook.dart:162:5) <asynchronous suspension> #7 GithubWebhook._handlePullRequest (package:cocoon_service/src/request_handlers/github_webhook.dart:124:9) <asynchronous suspension> #8 GithubWebhook.post (package:cocoon_service/src/request_handlers/github_webhook.dart:62:11) <asynchronous suspension> #9 RequestHandler.service.<anonymous closure> (package:cocoon_service/src/request_handling/request_handler.dart:49:22) <asynchronous suspension> #10 main.<anonymous closure>.<anonymous closure> (file:///app/bin/server.dart:253:9) <asynchronous suspension>

Anecdotally, we get this once a week with a check over ten thousand checks, but it is a more painful issue in the framework (100+ checks per PR)

Another case, where Linux web_tests_3 queued for more than 10 hours:

This seems happening more frequently:
https://github.com/flutter/flutter/pull/87763

Two more cases in https://github.com/flutter/flutter/pull/87264 (severn builders were not scheduled) and https://github.com/flutter/flutter/pull/84611 (one builder was not scheduled).

This appears to be blocking PRs in the past few days. Any PR that triggers most of the test suite will likely have a build not scheduled. Anecdotally, this looks like a 5% fail rate.

The increase in these failures is being tracked at https://bugs.chromium.org/p/chromium/issues/detail?id=1238498

Chromium reverted a culprit CL which will be rolling out soon. I'll continue monitoring to see if that fixes it.
The retry logic necessary for this is a much longer effort, so i'm seeing if there's short term fixes we can implement to work around this (like a cron to fail stuck checks)

Can we merge this bug with all the bugs tracking timeout when scheduling builds? I have a potential fix but will need your help debugging a one off index error.

Closed those bugs with scheduling issue. /cc @godofredoc
Do you mind sharing what you have done? I can take a deeper look.

This is still happening: https://github.com/flutter/flutter/issues/94631

Closing as obsolete.


HiC --> pacbio CLR

Hello, @holtjma
Thanks for your great work. Can I use Hi-C reads to correct pacbio CLR reads ?
I am wondering whether Hi-C reads are complete fragment(eg. 150bp from one chromosome ) or them are incomplete that Hi-C reads are composed of different fragment(eg. Hi-C reads are150bp which is composed of 60 bp from one chromosome and 90 bp from another chromosome or 90 from same chromosome but other location).

I'm probably not the best person to answer this.  I haven't worked with Hi-C data before so I'm unfamiliar with the pitfalls and whether this would theoretically work or not.  @txje do you have any thoughts on this?

While we haven't used FMLRC with Hi-C data before, my expectation is that it will work without modification. There will be cases, as you describe, where reads chimeras are formed (by design) between distant parts of the genome within Hi-C reads, and the k-mers at these junctions will be included in the FM-index, but they should be in the minority, so they shouldn't affect the correction. The chimeric junctions will be treated kind of like regular Illumina sequencing errors.

There's nothing in fmlrc2 that is explicitly recognizing the chimeric junctions.  I think what @txje is saying is that those junctions should occur inconsistently so the corresponding k-mers will be low-frequency in the data.  This will cause fmlrc2 to ignore those k-mers because they are low frequency, as if they were sequencing errors.  It won't explicitly discard any of the reads, but it may ignore portions of the reads corresponding to the junction assuming they are not frequent in the data.

OK, I got it. Thanks for your explanation !


Add bug report and feature request issue templates

Setting up bug reporting and feature request templates

Looks good to me! Thank you for adding this
!


PyYaml>=18.5 is wrong. >=5.1.0 instead

in ubnt 16.04 (py35) I found different available versions of pyyaml....
Collecting PyYaml>=18.1 (from oidcop==0.5.1)
  ERROR: Could not find a version that satisfies the requirement PyYaml>=18.1 (from oidcop==0.5.1) (from versions: 3.10, 3.11, 3.12, 3.13b1, 3.13rc1, 3.13, 4.2b1, 4.2b2, 4.2b4, 5.1b1, 5.1b3, 5.1b5, 5.1, 5.1.1, 5.1.2)
ERROR: No matching distribution found for PyYaml>=18.1 (from oidcop==0.5.1)

So I just fixed it this way.

Strange, in oidcservice we already used "pyyaml>=5.1.0"... My fault...

I've seen you last commit. This is not required anymore, closed ;)


Replaced depreciated Chef::REST with Chef::ServerAPI

Upgraded ChefDK and now knife encrypted attribute give me an error.
Chef Development Kit Version: 0.15.15
chef-client version: 12.11.18
Line 378 /lib/chef/encrypted_attribute/search_helper.rb is the problem.
Chef::REST is depreciated, simply replacing it with Chef::ServerAPI resolved the error.

Hi @e100,
Thanks for the PR.
Do you know if this breaks backward compatibility? I'm OK with that. But if that's the case, the requirements in the README will need to be updated.

Chef::ServerAPI has been around for a few years so I think its in 11 too but I don't know for sure.

OK, I tested this manually with Chef version 11.4.0 and fails. This PR will require at least Chef version 11.8.0.
So, two small requests:

Could you please fix the RuboCop offenses?

$ rake style
Running RuboCop...
Inspecting 72 files
..........................C.............................................

Offenses:

spec/unit/encrypted_attribute/search_helper.rb:428:81: C: Line is too long. [81/80]
        allow_any_instance_of(Chef::ServerAPI).to receive(:post_rest).and_return(
                                                                                ^
spec/unit/encrypted_attribute/search_helper.rb:445:81: C: Line is too long. [81/80]
        allow_any_instance_of(Chef::ServerAPI).to receive(:post_rest).and_return(
                                                                                ^

72 files inspected, 2 offenses detected
RuboCop failed!

And update the README and the tests to use Chef 11.8 instead of 11.4. Something like the following:

diff --git a/.travis.yml b/.travis.yml
index 4be3318..a771621 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -9,7 +9,7 @@ rvm:
 sudo: false

 env:
-  - CHEF_VERSION="= 11.4.0"
+  - CHEF_VERSION="= 11.8.0"
   - CHEF_VERSION="~> 11.0"
   - CHEF_VERSION="= 12.0.0"
   - CHEF_VERSION="~> 12.0"
diff --git a/README.md b/README.md
index b487a82..30b66f5 100644
--- a/README.md
+++ b/README.md
@@ -19,7 +19,7 @@ Node attributes are encrypted using chef client and user keys with public key in
 ## Requirements

 * Ruby `>= 1.9`
-* Chef Client `~> 11.4`
+* Chef Client `~> 11.8`
 * yajl_ruby `~> 1.1` or ffi_yajl `>= 1.0, <3.0` (included with Chef)
 * If you want to use protocol version 2 to use [GCM](http://en.wikipedia.org/wiki/Galois/Counter_Mode) (disabled by default):
  * Ruby `>= 2`.
diff --git a/chef-encrypted-attributes.gemspec b/chef-encrypted-attributes.gemspec
index c2ee484..f86dd36 100644
--- a/chef-encrypted-attributes.gemspec
+++ b/chef-encrypted-attributes.gemspec
@@ -10,7 +10,7 @@ chef_version =
   if ENV.key?('CHEF_VERSION')
     ENV['CHEF_VERSION']
   else
-    ['>= 11.4', '< 13']
+    ['>= 11.8', '< 13']
   end

 Gem::Specification.new do |s|
@@ -44,7 +44,7 @@ Gem::Specification.new do |s|
   end

   s.add_development_dependency 'rake', '~> 10.0'
-  s.add_development_dependency 'chef-zero', '~> 3.2'
+  s.add_development_dependency 'rack', '~> 1.0' if RUBY_VERSION < '2.2.2'
   s.add_development_dependency 'rspec-core', '~> 3.1'
   s.add_development_dependency 'rspec-expectations', '~> 3.1'
   s.add_development_dependency 'rspec-mocks', '~> 3.1'

The unit tests seem broken now:
  1) Chef::Knife::EncryptedAttributeShow When the Chef server is ready to rock! shows the encrypted attribute
     Failure/Error: resp = rest.post_rest(escaped_query, generate_partial_search_keys(keys))

     NoMethodError:
       undefined method `post_rest' for #<Chef::ServerAPI:0x0000000286fb80>
     # ./lib/chef/encrypted_attribute/search_helper.rb:380:in `partial_search'
     # ./lib/chef/encrypted_attribute/search_helper.rb:180:in `block in search_by_name'
     # ./lib/chef/encrypted_attribute/search_helper.rb:129:in `call'
     # ./lib/chef/encrypted_attribute/search_helper.rb:129:in `catch_search_exceptions'
     # ./lib/chef/encrypted_attribute/search_helper.rb:179:in `search_by_name'
     # ./lib/chef/encrypted_attribute/remote_node.rb:80:in `load_attribute'
     # ./lib/chef/encrypted_attribute/api.rb:506:in `exist_on_node?'
     # ./lib/chef/knife/core/encrypted_attribute_base.rb:61:in `assert_attribute_exists'
     # ./lib/chef/knife/encrypted_attribute_show.rb:38:in `assert_valid_args'
     # ./lib/chef/knife/core/encrypted_attribute_base.rb:94:in `parse_args'
     # ./lib/chef/knife/encrypted_attribute_show.rb:53:in `run'
     # ./spec/integration/knife/encrypted_attribute_show.rb:52:in `block (3 levels) in <top (required)>'
[...]

Could you fix them?
See the full output here.

@e100 Thank you, man. You have done awesome work here.
Do not worry about the other test errors. I need to fix some requirements in the Gemfile, but I think those errors fall outside the scope of this issue.
Give me a couple of days before reviewing and merging this.

Is there any reason to support 1.9.2 and 1.9.3?
I can fix the gemspec for 2.0

Yes, you are right: Dropping Ruby < 2 support is the way to go. They surpassed their EOL long ago anyway.

Fix released in 0.9.0.
Thanks for your contribution!!


From private repo

@v-alje : Thanks for your contribution to the Azure documentation! The author, @rayne-wiselman, has been notified to review your proposed change.


1.11 Backport: keep VIP label

Backport without refactoring https://github.com/dcos/dcos-ui/pull/2830
Closes DCOS-21440

run integration tests

run integration tests

shouldnt this cause an error? 🤔

double checked on master: same behavior 🤔


Investigate why the "/search preserve geometry in page GET links" test is failing

This is an odd one because it's just hitting the POST /search endpoint (which works in other tests), but is getting a 404 response in this test.
The error showing up in the API server logs says:
Error: Invalid GeoJSON geometry

The query parameters are:
{
  "intersects": "%7B%22type%22%3A%22Polygon%22%2C%22coordinates%22%3A%5B%5B%5B-54.58007812499999%2C69.39578308847753%5D%2C%5B-49.0869140625%2C69.39578308847753%5D%2C%5B-49.0869140625%2C70.72897946208789%5D%2C%5B-54.58007812499999%2C70.72897946208789%5D%2C%5B-54.58007812499999%2C69.39578308847753%5D%5D%5D%7D",
  "limit": 2,
  "page": 2
}

It looks like the API has logic to return any exception as a 404, which isn't what we want here. This should probably be returning a "400 Bad Request". So I guess there are two issues here:

The test is failing but should be passing
If the test is going to send bad data, it should be getting a 400 response back

The test has been marked as skip until this is investigated.


librdata cannot read rdata and rds files produced by R 3.6

Reading rdata files produced by R 3.5 is fine (test_r35.Rdata) but fails for rdata files produced by R 3.6 (test_r36.Rdata) with error code 9 (Unable to open file). These files were produced on windows.
Interestingly in my hands it fails for rds files both produced in 3.5 and 3.6 (examples attached), however pyreadr is reading 3.5 fine but fails for 3.6. I'm using the slight modified version of librdata by @jonathonlove (jamovi) that compiles with visual studio. sample files also produced on windows.
This referes to the issue https://github.com/ofajardo/pyreadr/issues/10
r35vs36.zip

I also checked with files produced by R 3.5 and 3.6 on linux. In this case, in my hands, librdata cannot read any of them. Am I missing something?
r35_36_linux.zip

the discrepancies between the latest librdata version and latest pyreadr version may be also because pyreadr is behind librdata (I'm using commit b7ca1252b670d60a6e8d3c8ce6fcc8ab3b43d6ab) from April.

Thanks for the report - I am able to reproduce the issue on master. For both the Windows and Linux files provided, the 3.5 files are parsed correctly, but the 3.6 files are not.
Please note that the Jamovi repository has not been updated since January - this may explain why the 3.5 files aren't opening for you.
I will look into the 3.6 files today.

Thanks!
Weird, actually pyreadr (I merged librdata april commit with jamovi manually) is opening 3.5 fine and it is librdata (readEx.c) the one not doing it for me. I'll try again once your fixes are out.

Btw, how do you test? If something different than readEx.c maybe you could share that?

Make sure that readEx.c is linked against an up-to-date librdata. Sometimes there will be an old librdata.so in /usr/local, leading to confusion.
I test by linking against my main proprietary applications - can't share, sorry!

Should be fixed in https://github.com/WizardMac/librdata/commit/0b41fb66e47bfdb6f73d964ba5ef54db8a14c4b4

It would help me if you could upload a 3.6 Windows file with some non-ASCII data in it. Windows uses Latin-1 by default, and I'd like to make sure that UTF-8 is being delivered to the text handlers. Thanks.

Attached the files with non-ascii characters (R 3.6 on windows). Indeed librdata cannot read them.
Regarding the original issues I reported, all solved now, I can read 3.5 and 3.6 from both pyreadr and librdata. Regarding librdata it was actually a compression error, compiling with -lz solved it. Thanks for the advice!
non-ascii.zip

Glad to hear the original files are opening for you now.
Okay, non-ASCII string vectors should work now. If you find other places where strings are not converted properly, please open a new issue.


Error when trying to go to profile from event popup

I think this could be related to https://github.com/CoderDojo/community-platform/issues/745 but making a separate issue anyway
Log in as a parent, go to a Dojo with a live event and click on book. Then click on the link that says "You must add them to your profile first" to add ninjas to your profile.
The link is broken and you get a timeout error. See screenshot.

This seems to be fixed now.

Appears to be fixed, although we have lost some functionality, which is now covered in https://github.com/CoderDojo/community-platform/issues/805


Don't require logger passed to writeTraceback/writeFaillure.

Fixes #167.

Thanks! Add news entry to documentation, then merge.


Update whatwg-fetch to version ^2.0.3

See https://github.com/facebook/react-native/issues/12961

I've tested this with npm test, I don't know what else to do.

Commits like these are deceptively tricky since most of the work is combing through the changelog and making sure it didn't break any behavior currently used, and then trying it in a couple of apps. Can you construct a reproduceable test plan and explain why you're confident in this change?

Yep, understood.
I don't have the time right now to test this super exhaustively though unfortunately :-(


Fixed bugs in AudioEmitter/AudioListener IsValid

Minor bug in implementation of #465.

Added test coverage in https://github.com/walbourn/directxtktest/commit/398a5674a79eb014b50a6a9796f530c5b5872164


Issue in SC-900-LAB_13_explore_senstivity_labels

Module: 04
Lab/Demo: LAB_13_explore_senstivity_labels
Task: 01
Step: 09
Description of issue
"In the middle of the page, notice how there are three labels already created. Select Confidential - Finance. A window opens that provides information about this label. Note how this label is set to support both encryption and content marking. Select Edit Label at the top of the page to view some of the basic configuration settings."
As mentioned in the step above, we did not get the three labels already created. Could you please let us know how it is created or else do we have to create it.

please look into this issue @ceperezb @seesharprun @bckelly


[bug] xxx in "/index.html"  can't be bundled without type="module" attribute

It correctly work but report a warning while building
<script src="xxx.js"> in "/index.html"  can't be bundled without type="module" attribute

Then I edit it as <script type="module" src="xxx.js"> but it report error:
Error: [vite]: Rollup failed to resolve import "xxx.js" from ".../index.html".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`

And here is my viteExternalsPlugin config:
    viteExternalsPlugin(
      { xxx: 'Xxx' },
      {
        disableInServe: true
      }
    )

I add build.rollupOptions.external = 'xxx.js' solved the error report, however I found Vite delete the

Close for no repro provided.


NodeKakao v3.1

NodeKakao v3.1
New features

[x] Add various web apis

[x] Add OpenLinkClient

[x] get cover preset
[x] write post
[x] edit post
[x] delete post
[x] react to post
[x] unreact to post
[x] write posts
[x] post recommends
[x] link recommends
[x] request post list
[x] set recommend
[x] exclude from recommend
[x] request new reaction list

[x] Add ChannelBoardClient

[x] write post
[x] remove post
[x] get post comments
[x] comment to post
[x] update posts
[x] react to post
[x] unreact to post
[x] set notice
[x] unset notice
[x] share to channel

[x] Add FriendClient

[x] add with phone number

[x] Add OpenUploadClient

[x] upload link image
[x] upload link post image

[x] Introduce TalkApiClient which provides various web api calls
[x] Add sendRaw to ChatManager
[x] Add forwardChat to ChatManager for chat forwarding
[x] add support for sending MultiPhoto
 Add missing chat types
[x] add 'chat_event' event for OpenChannel chat event(shouting)
[x] Custom client config

Improvements

Improved attachments
Improve chat sending to accept additional options(shout, inapp...)
[x] Use TalkApiClient to only use web apis
[x] Remove FeedTemplate
[x] Add changedType to 'profile_changed' event
[x] Add lastMeta to 'meta_changed' event
[x] Add 'error' event.

[x] Fix OpenProfileType

#44 delayed to next version. (probably)

Package registry is changed to npmjs. Module in Github packages will not get further updates.


Script crashing game

The following script runs fine for a while and then the game crashes
client = getMinecraftClient();
world = client.getWorld();
me = client.getPlayer();
me.look(54.1,70.9);
blockCheck = world.getBlockAt(-6913,100,18869);
itemCheck = me.getHeldItem();
me.message(itemCheck);
while(me.getHeldItem() == itemCheck){
while(world.getBlockAt(-6913,108,18869)==blockCheck){
me.use("once");
if(me.getHeldItem()!=itemCheck)
return;
if(world.getBlockAt(-6912,112,18869)==blockCheck){
sleep(100);
}
else{
sleep(500);
}
}
sleep(5000);
}
the launcher told me this:
The game crashed whilst unexpected error
Error: java.util.ConcurrentModificationException
Exit Code: -1
full crash report
crash-2021-12-27_18.33.52-client.txt

Can you provide mod version, and game version?


chore: avoid generating protobuf(proto-google-common-protos) protobufs every time

protobuf(...) causes protoc to generate code for the listed proto files compileProtoPath adds the listed artifacts on the "include path", so we can reference third-party definitions and generate code for our proto files only.
Note: com.google.protobuf searches both compileProtoPath and implementation dependencies for .proto files.
io.grpc:grpc-protobuf already depends on proto-google-common-protos, so the build would work even without explicit dependency. However, we import google/api protos, so it would be nice to explicitly mention the used dependencies even though they are present as transitive.

I guess the reason for the failure is that proto-google-common-protos builds using an old protoc version.
We use 4.26.1 for sigstore-java, and api-commons-protos seem to use 3.14.0: https://github.com/googleapis/api-common-protos/blob/3332dec527759859840a3a2ff108c67a54708130/Dockerfile#L7

gonna close this for now -- I was informed of this issue that might the be underlying problem: https://github.com/protocolbuffers/protobuf/issues/17247


A Question about Status Character Counts

Hi,
Twitter seems to be using 21 chars out of the 140 limit when a picture is attached to a Tweet?
The deprecated statuses/update_with_media endpoint does mention that a url for the image will be added to the status update but there is no mention, that I can see, of this on the statuses/update method?
Is this correct, so a status update with a picture can only be 119 chars long?
If so, would adding 2 pictures reduce the possible text length to 98 chars?
Thanks for any clarification.
Cheers.
/jh

To answer my own question. Twitter add a URL to the status update with a space before it so would seem to use a maximum of short_url_length + 1 chars, so currently 23.


1711.1 release

Minor updates to support Visual Studio 15.4. The new version of Visual Studio is now required.
Also has bug fixes.

This change is

It also includes Objc2Winmd!


Issue with passing an array of paths

This works with the default express.Router() and fails with express-promise-router:
homeRouter.get(['/:language', '/'], function(req, res) {
  if (req.params.language != null) {
    req.lang = req.params.language;
  }
  return res.render('index');
});

The / URL just says Cannot GET /, and another URL like /en for example gives the following stacktrace:
TypeError: undefined is not a function
   at handleReturn (c:\dev\project.js\node_modules\express-promise-router\lib\express-promise-router.js:27:27)
   at c:\dev\project.js\node_modules\express-promise-router\lib\express-promise-router.js:55:9
   at Layer.handle [as handle_request] (c:\dev\project.js\node_modules\express\lib\router\layer.js:82:5)
   at next (c:\dev\project.js\node_modules\express\lib\router\route.js:110:13)
   at Route.dispatch (c:\dev\project.js\node_modules\express\lib\router\route.js:91:3)
   at Layer.handle [as handle_request] (c:\dev\project.js\node_modules\express\lib\router\layer.js:82:5)
   at c:\dev\project.js\node_modules\express\lib\router\index.js:267:22
   at param (c:\dev\project.js\node_modules\express\lib\router\index.js:340:14)
   at param (c:\dev\project.js\node_modules\express\lib\router\index.js:356:14)
   at Function.proto.process_params (c:\dev\project.js\node_modules\express\lib\router\index.js:400:3)
   at next (c:\dev\project.js\node_modules\express\lib\router\index.js:261:10)
   at c:\dev\project.js\build\webpack:\server\routes\home.coffee:16:5
   at handleReturn (c:\dev\project.js\node_modules\express-promise-router\lib\express-promise-router.js:27:27)
   at c:\dev\project.js\node_modules\express-promise-router\lib\express-promise-router.js:55:9
   at Layer.handle [as handle_request] (c:\dev\project.js\node_modules\express\lib\router\layer.js:82:5)
   at trim_prefix (c:\dev\project.js\node_modules\express\lib\router\index.js:302:13)
   at c:\dev\project.js\node_modules\express\lib\router\index.js:270:7
   at Function.proto.process_params (c:\dev\project.js\node_modules\express\lib\router\index.js:321:12)
   at next (c:\dev\project.js\node_modules\express\lib\router\index.js:261:10)
   at c:\dev\project.js\node_modules\i18n-future\lib\middleware.js:43:7
   at process._tickCallback (node.js:355:11)

Yeah, looks like express-promise-router only supports string or regexp as path, see here: https://github.com/alex-whitney/express-promise-router/blob/master/lib/express-promise-router.js#L70
Something a simple PR won't be able to fix though :)

Wasn't this fixed by that PR? It's not working for me, has it not been pushed yet?

Nope, it hasn't been pushed yet as far as I can tell.
Your best bet would be to directly reference the github in the project.json file.

That's what I've done already, thanks.
On Sat, Jun 4, 2016 at 12:32 AM, Jonatan Nilsson<EMAIL_ADDRESS>wrote:

Nope, it hasn't been pushed yet as far as I can tell.
Your best bet would be to directly reference the github in the
project.json file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alex-whitney/express-promise-router/issues/12#issuecomment-223627688,
or mute the thread
https://github.com/notifications/unsubscribe/AF-G9Wzlj1dvTPwMS7WD4UUdfb6kBiuQks5qIFcBgaJpZM4EgmGb
.

You might be interested in using this one: https://github.com/TheThing/express-promise-router
It has a cleaned and optimised code.
Here's the PR with details: https://github.com/alex-whitney/express-promise-router/pull/23

This should be fixed in 1.1.0


Unhandled Exception: System.ArgumentOutOfRangeException: Length cannot be less than zero. Parameter name: length    at System.String.Substring(Int32 startIndex, Int32 length)    at MultiAdmin.Config.Reload()    at MutliAdmin.Program.StartHandleConfigs(String[] args)    at MutliAdmin.Program.Main(String[] args)

I've been having the same issue. Still no luck fixing.
Error here

use the config provided by multiadmin

Should be fixed in the next release, make sure your config isn't messed up because that would only happen if your config had a missing value.


Issue with building the Hexagon HVX DSP toolchain with TF

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): NO
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 14.04
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 1.8r
Python version:  2.7
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source): 4.8.4
CUDA/cuDNN version: 8
GPU model and memory: GTX 1060
Exact command to reproduce:

Describe the problem
@satok16 @tensorflower-gardener , Could you please clarify the different version-combination of tools to use in an HVX-TF toolchain. It can save many people's effort to find and match these together. You have already mentioned in HVX_TF, that for Qualcomm SDK 3.0, the compatible nnlib version is Aug-2017-commit. However, some features are missing there and we need to use the latest version with SDK 3.3.3, however, these libraries (nnlib, libcontroller, TF-(sub)makefiles) don't match, thus it has become a messy process to figure out which is related to what version.
1) A sample error compiling libcontroller after compiling nnlib with latest SDK (3.3.3):
src_impl/hexagon_controller.c: In function 'hexagon_controller_AppendNode':
src_impl/hexagon_controller.c:484:70: error: 'hexagon_nn_output' has no member named 'max_size'
     pos += snprintf(&output_param_buf[pos], 500, "(%d), ", outputs[i].max_size);
                                                                      ^
make[1]: *** [android_Release/hexagon_controller.o] Error 1
make[1]: Leaving directory `~/Qualcomm/Hexagon_SDK/3.3.3/examples/common/hexagon_controller'
make: *** [tree] Error 2

2) If I use your suggested commit and SDK 3.0, this is the output I am having:
native : hexagon_graph_execution_test.cc:129 Read /data/local/tmp/img_299x299.bmp, size = 269156bytes
native : hexagon_graph_execution_test.cc:135 header size = 54
native : hexagon_graph_execution_test.cc:137 image size = 40
native : hexagon_graph_execution_test.cc:139 width = 299
native : hexagon_graph_execution_test.cc:141 height = -299
native : hexagon_graph_execution_test.cc:286 Ioading image finished.
native : hexagon_graph_execution_test.cc:185 Loading image finished.
native : hexagon_graph_execution_test.cc:189 Copy data to tensor.
native : hexagon_graph_execution_test.cc:307 Run graph
Init hexagon with max attributes (Controller version = 101)
native : hexagon_control_wrapper.cc:104 Add input: Mul, 0
native : hexagon_control_wrapper.cc:127 Allocate inout buffer
native : hexagon_control_wrapper.cc:304 Setup graph completed
Prepare failed! returned 0xffffffff

NN Id = -755923072
Execute graph!
Execution failed!
execute got err: -1

NN Id = -755923072
Execution failed
NN Id = -755923072
Failed to read data.
native : hexagon_graph_execution_test.cc:313 Output byte size = 4032
native : hexagon_graph_execution_test.cc:314 Output shape = [1,1008]
native : graph_transfer_utils.cc:47 === Dump ranking ===
native : graph_transfer_utils.cc:50 0: 1000, dumbbell, 0
native : graph_transfer_utils.cc:50 1: 999, carbonara, 0
native : graph_transfer_utils.cc:50 2: 998, stole, 0
native : graph_transfer_utils.cc:50 3: 997, rubber eraser, 0
native : graph_transfer_utils.cc:50 4: 996, coffee mug, 0
native : graph_transfer_utils.cc:50 5: 995, flagpole, 0
native : graph_transfer_utils.cc:50 6: 994, parallel bars, 0
native : graph_transfer_utils.cc:50 7: 993, cheeseburger, 0
native : graph_transfer_utils.cc:50 8: 992, bubble, 0
native : graph_transfer_utils.cc:50 9: 991, beaker, 0
Finalize hexagon
[       OK ] GraphTransferer.RunInceptionV3OnHexagonExampleWithTfRuntime (5848 ms)
[----------] 1 test from GraphTransferer (5848 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (5849 ms total)
[  PASSED  ] 1 test.

  YOU HAVE 5 DISABLED TESTS

3)  Also in the toturial, you did not mention anything about downloading/using an inception-v3 frozen-quantized model. If one follows the building each library from the source, where is the part related to use the [tensorflow_inception_v3_stripped_optimized_quantized.pb] ? Since, when I test with my custom quantized_frozen inception-v3 model, (renaming it to be the same as the original 2016 file (tensorflow_inception_v3_stripped_optimized_quantized.pb), I have the error output as:
...
native : hexagon_graph_execution_test.cc:533 Ioading image finished.
t1(loading image time)=0.026770
native : hexagon_graph_execution_test.cc:546 Build fused graph
native : remote_fused_graph_execute_utils.cc:259 Error during inference: Not found: FeedInputs: unable to find feed output Mul
native : graph_transfer_utils.cc:110 Check failed: status.ok()
Aborted

Thanks.

Tagging @satok16 for this one as well.

Nagging Assignee @karmel: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@satok16 , any comment on this?

@amirjamez
Which kind of hardware are you using?  Did you follow the troubleshoot in the tutorial?
amirjamez

@satok16 it is an open Q 820. Yes, I did. apparently, there is a mismatch between the lib-controller versions, nnlib, and the TF-toolchain. Libcontroller used in your toolchain (the one that downloaded the prebuilt library) is v90 and it belongs to a very old version of TF (maybe v1.1 or v1.2), thus using new TFs to build the library will result in failure. However, nnlib needs to be newer to support more ops and these initiates the conflicts.

"Prepare failed! returned 0xffffffff" means that it couldn't create NN in HVX.  So, I assume there may be some incompatibility issues on your hardware.  You may want to build nnlib by yourself for your hardware and that may work.  This feature is pretty much frozen mode, so you may want to wait for tflite for better hardware supports.

@satok16 thanks. I have built nnlib with SDK 3.3.3, but the test app provided in the test folder does not recognize the image when I pass. Full info here.. Have you overcome this issue?

No, we don't use SDK 3.3 here as this is frozen mode.

@satok16, but what if someone wanted to use his modified inception_v3 (newer than the one used in the toolchain as this was for December 2016) as input, it is needed to have the latest nnlib to support the ops and thus, one needs a newer version of SDK and lib controller to build those. So the whole chain will crumble again.

I see, if you want to get newer SDK version's support, I'd recommend you to wait for tflite's supports on nnlib as efforts are going there.

@satok16, could you at least help me out to pass the image mismatch issue that I am getting by executing the nnlib test app (graph_app). Looking at the code, no matter what parameters I pass, I am stuck with this issue:
image size 25763 does not match element size 1, depth 3, width 299, height 299
if I manually pass this segment (commenting out the check), I will have either small data, or, data overflow and lose adb connection everytime I execute it:
image size 25763 does not match element size 1, depth 3, width 92, height 92, elements 25763, area 8587
 filesize=25763 elementsize=1 height=92 width=92 depth=3
Run!
execute got err: -1
hexagon/ops/src/op_output.c:59:output 0 too small
Rank,Softmax,index,string
0,0.000000,1023,OVERFLOW!
1,0.000000,1,kit fox
2,0.000000,2,English setter
3,0.000000,3,Siberian husky
4,0.000000,4,Australian terrier

What is the correct weight, width, depth and elements parameters to be used with keyboard_299x299.jpg. Thanks.

Did you check the sample image which is used in build_and_run_inception_hexagon.sh?

@satok16, yes I did. Same issue here and here. it is img_299x299.bmp and has 269156 bytes. Given the conditions in nnlib i need to have:
...
326         elements = filesize / elementsize;
327         area = elements / depth;
328         if (height * width == 0) {
329                 height = width = sqrt(area);
330                 assumed->height = height;
331                 assumed->width = width;
332         }
333         if  ((filesize % elementsize != 0)){
334                  ||(elements % depth != 0)
335                  (height * width != area) {
336                 printf("image size %d does not match "
...

thus, assuming a square box (width == height) and depth = 3 I need to have an image of size: 2992993 = 268203 which currently it is not (it is 269156)

"bitmap" has a header and you can't feed the bitmap binary to the inception v3 model as is.  You should load the image to a float array as hexagon_graph_execution_test.cc is doing.

@satok16 thanks. I see how you did it at the hexagon_test.cc. So how about .jpg and .dat?  There is a keyboard_299x299.jpg in the test folder, doesn't it have to work out-of-the-box?
hmm, is that the reason there is a python script at scripts/imagedump.py. Does it get a .bmp and outputs just the .dat for that matter?

You can just convert the jpg to bitmap or directly to a float array in your program and feed it to the model.

Thanks, @satok16. Could you provide insights on why the bellow error occurs while executing the graph standalone app on HVX?
Using </data/keyboard_299x299.dat>
filesize=268203 elementsize=1 height=299 width=299 depth=3
Run!
execute got err: -1
hexagon/ops/src/op_output.c:59:output 0 too small
output size=4096
Rank,Softmax,index,string
0,0.000000,1023,OVERFLOW!
1,0.000000,1,kit fox
2,0.000000,2,English setter
3,0.000000,3,Siberian husky
4,0.000000,4,Australian terrier
run failed: -1

This interestingly works with SDK 3.0 and nnlib august 2017, but on both versions we have execution error -1.

Nagging Assignee @karmel: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @karmel: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@satok16 Could you let me know how to print all the append nodes in Hexagon_control_wrapper.cc given inception-v3? I guess this way I may be able to debug the issue. Thanks

Nagging Assignee @karmel: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @karmel: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@satok16 -- any update here?

@satok16 I managed to build the libraries and the hexagon_excution_graph adding -E to the build toturial. It takes around 10 minutes to compile (after we already built lib_controller and lib_hexagon_skel.so) and I am searching to reduce its compilation time.
Also, my other question was unanswered here. I appreciate if you let me know how did you freeze and optimize the inception-v3 model that doesn't have tf.Squeeze() inside. As you know, this method is not yet implemented on HVX. When I freeze and optimize for inference, these layers are still there, I guess some part of the graph should be stripped/removed but using the graph_transformation I was not able to reproduce the model. Thanks.

Nagging Assignee @karmel: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Mobile efforts have been on TF Lite (https://www.tensorflow.org/mobile/tflite/). If you have any other concerns, please create another issue for easier tracking. Thanks!


New version: LinwoodCloud.Butterfly.Nightly version 2.2.0-beta.1

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978334972
2024-08-05 10:08:35.169 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFDB888C11F: (caller: 00007FFDB8618D6F) LogHr(1) tid(848) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFDB8792B08: (caller: 00007FFDB883BC20) Exception(1) tid(848) 8A15005E ]
2024-08-05 10:08:44.331 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFD9C87C11F: (caller: 00007FFD9C608D6F) LogHr(1) tid(1884) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFD9C782B08: (caller: 00007FFD9C82BC20) Exception(1) tid(1884) 8A15005E ]
2024-08-05 10:08:46.017 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.40.33810.0

Automated error analysis suggests -1978334972 may mean This package has a dependency missing from your system.
Automated error analysis suggests 8A15005E may mean APPINSTALLER_CLI_ERROR_PINNED_CERTIFICATE_MISMATCH - The server certificate did not match any of the expected values.
(Automated response - build 887.)


DDR5 support for pdata

Changes to the MRW parser to handle DDR5 DIMMs

@aravynd Can you please point local to refer the generated device tree with this PR changes for the reference?

In the rainier 4u device tree, the power_ic target is added since its new target type is chip-vreg-generic which is treated as PMIC so the question is, whether we need to call it power_ic?

Yes, it should be called power_ic.

and also, is it guardable? if yes, we need some support from the hw-isolation as posted in the old PR comment.

Yes, it is guardable.


pyNose CLI

Hi,
Is there anywhere I can find an example command on how to run the tools in CLI because I saw that in the papers but I don't see it anywhere in the repo.

Hi, if you want to run the original ASE 2021 version, you can find it in the ASE2021 branch. There's a section in the README.md describing how to run the original version of the tool from the command line. I hope this will help.

Ahh ok I found it
Thanks a lot  💯


Feat/GCP CloudRun

Perhaps, you unintentionally sent this PR to my repo, right? Either way, I don't accept these changes, so let me close this PR.

yup thank you


Replace Study group name field with a new unit field

Study group handles the new unit id field along with renamed unit name field.
The old name field of StudyGroup model is renamed to "unit_name". A new "unit_id" field is added alongside the unit name field. The new unit id can be used to fetch a whole Place object from external APIs like LinkedEvents or Servicemap.
PT-1236 PT-1264 PT-1265
StudyGroup schema's unit field is now working with an union type: the unit can be a Place or a new ExternalPlace, which includes the name only.
NOTE: There were a lot of issues with circular imports, which are now being fixed with strings instead of real package imports.
To offer some backward compatibility for notification templates etc., there is a name getter that return unit name
PT-1264.

NOTE: this branch will be merged to PT-1264/servicemap-api


[E2E VM Test] Increase timeout for sftp deployment to become ready

Sometimes the image can take a long time to pull from Harbor, and 30s may not be enough.
Also improve logging to make future issues easier to troubleshoot.

/test-vm-e2e

LGTM

/test-vm-e2e

/test-vm-e2e

vm-e2e test successful

/skip-all


[survey] Produce CID lists first

Description
Produce and post CID lists first so they get to FB on time, regardless of how long the rest of the pipeline takes.
Changelog

params.json target to output only cids.
Create new update-params.json target to change output to all other output types (covidalert, community, etc)
Change order of dependencies for pipeline target.

Holding off on this for now since survey API runs are currently taking <1 hour and deprecating unweighted signals will reduce that even more.

Survey has ended. This was never used.


⚠ File access (beta) has degraded performance

In a5a4f1e, File access (beta) (https://beta.fyle.uk/file/fish) experienced degraded performance:

HTTP code: 200
Response time: 2965 ms

Resolved: File access (beta) performance has improved in f2acdf9 after 8 minutes.


added translations for resource locator error

Just adds the translations for https://github.com/sulu-io/sulu/pull/1660
tasks:

[ ] test coverage
[ ] gather feedback for my changes
[ ] submit changes to the documentation

informations:

q
a

Fixed tickets
none

BC breaks
none

Documentation PR
none

ACK


Expose API

[x] Translation Promise (resolve when translations are loaded, implemented in #11)
[x] Translate single element and its content (implemented in #11)
[x] Translate all

@FelschR Maybe allow to reset translation?

Yes, that would be a good idea.

test


Dark-mode breaks menu-bar

When installing dark-mode via homebrew on a brand new macOS 10.12.3 installation, the menu-bar breaks.
Only the dock turns dark when activating dark-mode, and confirmed that using the system preference pane to do so (prior to install) works fine. After installing dark-mode, using the system pref UI will ONLY turn the menu-bar dark, and will no longer control the dock.
A complete uninstall does not solve this problem.

The version of Homebrew is not updated yet: https://github.com/Homebrew/homebrew-core/pull/9665

I, too, am experiencing this problem. dark-mode 1.01 broke the menu bar and I cannot figure out how to fix it.

The Homebrew update was merged. You can update with:
$ brew update && brew install -f dark-mode

Make sure to follow the instructions: https://github.com/sindresorhus/dark-mode/releases/tag/2.0.0


begin adding GPS glitch detection

alter makefile to add debugging stuff
begin copying GPS glitch detection logic from AP_NavEKF
convert kd0aij's f450 GPS glitch log and copy into kd0aij/InertialNav/code
-- no effect on plot generated by plot_position.py
-- Lorenz, could you give this a quick look and tell me if I'm on the right track?

Could you throw in a couple of plots to see what it does?

this is the result of python "plot_velocity.py"

Ok, now I understand what you meant with right track, will get feedback in a sec.

I would say it looks like on the right track. Only the plots will eventually tell ;-).

beginning to see some results:

The input data for these plots is in f450_glitch_log.zip in the code folder

after bugfix:

Need to go back over the changes now, adding comments and notes about changes to posHealth definition. Also a number of printf statements need to be removed.

onboard attitude estimates are now handled correctly

better plots of onboard log and giltch detection/fix

I have trouble reading the plots - could you integrate the pitch gyro maybe to more clearly show which one is right?

It is difficult to interpret the plots. I'll have to modify the python plot to add the pitch gyro.
In the meantime, I have decided that, qualitatively, the pitch estimated after glitch detection is closer to my observations of flight behavior.

This shows my reaction to the event: black trace is RC pitch command: forward with a momentary pause due to observed attitude glitch, then full back with little observed effect on copter, followed by a 180 degree yaw command and forward pitch to return.

just realized it's easy to add the pitch gyro integral in flightplot, will do that after dinner

Integral of pitch rate agrees well with glitch compensated EKF, except for the EKF pitch bump from 124.9 to 125.5 here:

That looks pretty good. It also looks like the GPS failure starts already at second 124 sharp, with an increase of the failure mode at second 127. Is there some room left to tune it to catch the one at 124 already?

looks like it's already detecting and compensating at 124:

I think this is ready to merge into ekf_att_pos_estimator now for flight testing

@kd0aij I was referring to the discontinuities in the plot as annotated below. While I agree that the performance improved, it seems necessary to inspect these closer. In particular since the roll angle jumps before the onboard roll angle does.

I was able to get the pitch estimate to agree pretty well with the integrated pitch gyro, but roll and yaw estimates don't seem to be working as well:

found a block of code I missed before; commit on the way

Ok, looks a bunch better - are you plotting the innovations / quantities you're using to identify glitches? I would be interested to see them together with the position plots. I'm also wondering if the glitch direction correlates with the angles affected.

the estimator glitches at 123.8 were being caused by method CheckAndBound, which detected divergence between gps VelNED and filter state. With that test disabled the estimated attitude agrees better with integrated gyros:

EKF vel estimate without divergence check vs. GPS velNED

first short flight test using branch gpsGlitchDetection in kd0aij/Firmware: http://dash.oznet.ch/view/cC4Q3JF2p4q9MLFF8aEynm
3S battery with 8" props required nearly full throttle to hover, but flight was stable
No gps glitches during flight, altctl behaved OK, posctl was stable but actively moving around (heavy cloudcover and trees nearby)

QAV250/LEA6H flight test: http://dash.oznet.ch/view/dwoBFSprbaCymKYze5PKWh
no problems observed

this flight had on GPS glitch detected:

So the conclusion is it just works fine?

The plots look pretty good to me!

I think it's ready for more thorough flight testing. Shall I create a PR against PX4/Firmware?

Yes please - and create a PR against priseborough/InertialNav as well please.

memo:

the sign of gpsPosGlitchOffsetNE seems reversed to me, but I'm pretty sure it's the same as in AP_NavEKF, and a quick run with the signs flipped at lines 1243,1244 resulted in discontinuities in the EKP posNE which is probably very bad. Would be nice to understand why adding the glitched posInnov to the glitchOffset is correct, when the glitchOffset is added to GPS posNE to form the observation. The posInnov is then computed as (state - observation) which also seems to have its sign reversed, so maybe this explains why the offset looks sign-reversed to me.

the code in NavEKF::SelectVelPosFusion which assigns gpsPosGlitchOffsetNE was not copied over. Not sure what this does; executed if there has been no GPS data for > gpsRetryTimeout