v0.4.6 ethadapter v1.0.5 concurrency issue

In the scope of https://github.com/PharmaLedger-IMI/blockchain-node-workspace/issues/5#issuecomment-1245393626 , where fgt-workspace upgraded to psk-release be8027202d04032bed93fb8de74253d61ec6a3b9, and ethadapter from ee6b2a4 to 6642225 (v1.0.5)
If we build a single wallet, we find no trouble.
If we build multiple wallets, we get (on the fgt-workspace side):
...
seed KeySSI created with SSI 2vkohTn1jVeB8ZSr4vJvNcP3WjGNLWK9nwKvj7sm3qzY7VkDBjcR1qtKPu
Caught an error during JSON.parse Error
May or not be important, for safety check it! Failed to parse the error from the response due to SyntaxError: Unexpected token E in JSON at position 0
    at JSON.parse (<anonymous>)
    at IncomingMessage.<anonymous> (/fgt-workspace/privatesky/psknode/bundles/openDSU.js:26218:42)
    at IncomingMessage.emit (node:events:538:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
The wallet couldn't be created. Trying to load with credentials...
Environment for vault dashboard no-cache
Loading wallet with ssi 3XXka29Q8KUGeWVtxRkGGtuNtSmT7jJd28mZCpB9VemEqC6JQ1ymrXAiV1sXvpfDa5a1rd9Dp4tjk3XwKDJfqiUejW6PnNMF3tpGpT9
node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^[UnhandledPromiseRejection: 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(). The promise rejected with the reason "Could not load wallet DSU Error: Failed to get the list of hashlinks(Unexpected end of JSON input)".] {
  code: 'ERR_UNHANDLED_REJECTION'
}

Full set of logs: https://homes.pdmfc.com/jpsl/PharmaLedger/fgtEth20221017/
(There are more MAHs, which do not have the logs shown here. Here we only track the failure of building one MAH, but fgt-workspace.log has all concurrent "traceability" apihub events)
mah-msd.log fails at 2022-10-17T10:49:37.961894699Z with ""Could not load wallet DSU Error: Failed to get the list of hashlinks(Unexpected end of JSON input)""
fgt-workspace.log at that time shows:
2022-10-17T10:49:35.964207970Z INFO     0x00<PHONE_NUMBER>964 Logger      apihub/logg <IP_ADDRESS>:8080 - [2022-10-17T10:49:35.962Z] GET:/anchor/traceability/get-last-version/29fgyfS13tr4gjabfTYGXNFDRPzLXrRDajXxGZEZ14bN2DEkQjHGhqxxkkfHu9HQXdxA3ju1F2hWdzF75BaVffiAKW8Zw5Z 200 1.871ms
2022-10-17T10:49:35.980271020Z ERROR    0x00<PHONE_NUMBER>969 Eth         apihub/anch {
2022-10-17T10:49:35.980309836Z   error: Error: Request Failed.
2022-10-17T10:49:35.980317894Z   Status Code: 429
2022-10-17T10:49:35.980338361Z   URL: <IP_ADDRESS>:3000/createAnchor/29fgyfS13tr4gjabfTYGXNFDRPzLXrRDajXxGZEZ14bN2DEkQjHGhqxxkkfHu9HQXdxA3ju1F2hWdzF75BaVffiAKW8Zw5Z/G73iPJYaFmfMiBcFYy1vLzEqPxiV3hGaStCihXbBcuSkfV5Pf9aQWvuocoBWW7mRVu8QVooX2cBrvAMeevRorCXhPkgxf
2022-10-17T10:49:35.980343555Z       at ClientRequest.<anonymous> (/fgt-workspace/privatesky/psknode/bundles/pskWebServer.js:44282:13)
2022-10-17T10:49:35.980352585Z       at Object.onceWrapper (node:events:646:26)
2022-10-17T10:49:35.980359146Z       at ClientRequest.emit (node:events:526:28)
2022-10-17T10:49:35.980364306Z       at HTTPParser.parserOnIncomingClient (node:_http_client:618:27)
2022-10-17T10:49:35.980369735Z       at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)
2022-10-17T10:49:35.980374269Z       at Socket.socketOnData (node:_http_client:482:22)
2022-10-17T10:49:35.980378951Z       at Socket.emit (node:events:526:28)
2022-10-17T10:49:35.980384101Z       at addChunk (node:internal/streams/readable:315:12)
2022-10-17T10:49:35.980389287Z       at readableAddChunk (node:internal/streams/readable:289:9)
2022-10-17T10:49:35.980393820Z       at Socket.Readable.push (node:internal/streams/readable:228:10)
2022-10-17T10:49:35.980399085Z       at TCP.onStreamRead (node:internal/stream_base_commons:190:23),
2022-10-17T10:49:35.980409567Z   statusCode: 429,
2022-10-17T10:49:35.980415491Z   message: ''
2022-10-17T10:49:35.980421329Z }

ethadapter.log shows no errors whatsoever

I think we have not understood the propose of the throttler in the new ethadapter v1.0.5...
We tryed a simpler test: https://homes.pdmfc.com/jpsl/PharmaLedger/createManyDSUs20221018/
Running a single script "createManyDSUs.js" script (which should be the base of  https://github.com/PharmaLedger-IMI/epi-workspace/issues/670 - source at https://github.com/PharmaLedger-IMI/fgt-workspace/blob/master/tests/privateksy/createManyDSUs.js),
with a single apihub (runServer.log),
and a single ethadapter (ethadapter.log).
The apihub (runServer.log) reports
...
ERROR    0x00<PHONE_NUMBER>505 Eth         apihub/anch {
  error: Error: Request Failed.
  Status Code: 429
  URL: <IP_ADDRESS>:3000/appendAnchor/2eg3XSYLuY9m6WqTiuqrGAy3mMB9s3BkpUzaH5oZz1WRbwEsvHGDZ22bqU5K334JKnsRSiAFstVWBjNxS7R5Z8gvG3Bsv6KiLWCqeohemzBNPLW6yEUNKs4p8kJRbBUpLdYsquRcyhGbBLfdznesu89EQY7/4qnrBhooj78L2psbyjJ44LqFA4DA5x8PnUfQn2bSLdAgzwDoFtaPZ24L3DtWYzgd7eXWsZ7nBExKK3ZpwJMGhq6Xqz1FUfVSE7tMY4RzTYVCAUxhF52BfVGidTKvpMtJbtEvBiFzVTcEUKeRZYZzzXtXmUDBZ9Gdp9V1Km7Dp4K895Q9wuSAGKMxgZ5zF7irTTwJoU5yuatLaBSvTSdpaSFKEf6Qj9hEUfMQt76apX
      at ClientRequest.<anonymous> (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/pskWebServer.js:44282:13)
      at Object.onceWrapper (node:events:646:26)
      at ClientRequest.emit (node:events:526:28)
      at HTTPParser.parserOnIncomingClient (node:_http_client:618:27)
      at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)
      at Socket.socketOnData (node:_http_client:482:22)
      at Socket.emit (node:events:526:28)
      at addChunk (node:internal/streams/readable:315:12)
      at readableAddChunk (node:internal/streams/readable:289:9)
      at Socket.Readable.push (node:internal/streams/readable:228:10)
      at TCP.onStreamRead (node:internal/stream_base_commons:190:23),
  statusCode: 429,
  message: ''
}

The ethadapter.log reports nothing unusual.
The createManyDSUs.log reports
Caught an error during JSON.parse Error
May or not be important, for safety check it! Failed to parse the error from the response due to SyntaxError: Unexpected token E in JSON at position 0
    at JSON.parse (<anonymous>)
    at IncomingMessage.<anonymous> (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:26218:42)
    at IncomingMessage.emit (node:events:538:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:25584
            newErr = new Error(message + `(${err.originalMessage})`);
                     ^

Error: WALLET_DB.commitBatch(Error)
    at ErrorWrapper (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:25584:22)
    at createOpenDSUErrorWrapper (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:25614:12)
    at /export/home/jpsl/develop/PharmaLedger/fgt-workspace/tests/privateksy/createManyDSUs.js:128:76
    at /export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:2205:57
    at endAnchoring (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:3739:9)
    at updateAnchorCallback (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:4303:36)
    at executeForSingleEntry (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:30691:51)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  originalMessage: 'Error',
  previousError: Error: Failed to anchor(Error)
      at ErrorWrapper (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:25584:22)
      at createOpenDSUErrorWrapper (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:25614:12)
      at /export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:2205:58
      at endAnchoring (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:3739:9)
      at updateAnchorCallback (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:4303:36)
      at executeForSingleEntry (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:30691:51)
      at processTicksAndRejections (node:internal/process/task_queues:96:5) {
    originalMessage: 'Error',
    previousError: Error: Error
        at ErrorWrapper (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:25587:22)
        at createOpenDSUErrorWrapper (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:25614:12)
        at executeForSingleEntry (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:30691:52)
        at processTicksAndRejections (node:internal/process/task_queues:96:5) {
      originalMessage: 'Error',
      previousError: { statusCode: 500, message: 'Error' },
      debug_message: 'Failed to execute entryError: Failed during execution of append-to-anchor',
      type: -2
    },
    debug_message: 'Failed to anchor',
    debug_stack: 'Error: Error\n' +
      '    at ErrorWrapper (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:25587:22)\n' +
      '    at createOpenDSUErrorWrapper (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:25614:12)\n' +
      '    at executeForSingleEntry (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:30691:52)\n' +
      '    at processTicksAndRejections (node:internal/process/task_queues:96:5)'
  },
  debug_message: 'WALLET_DB.commitBatch',
  debug_stack: 'Error: Failed to anchor(Error)\n' +
    '    at ErrorWrapper (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:25584:22)\n' +
    '    at createOpenDSUErrorWrapper (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:25614:12)\n' +
    '    at /export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:2205:58\n' +
    '    at endAnchoring (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:3739:9)\n' +
    '    at updateAnchorCallback (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:4303:36)\n' +
    '    at executeForSingleEntry (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/openDSU.js:30691:51)\n' +
    '    at processTicksAndRejections (node:internal/process/task_queues:96:5)'
}

PS: And I disagree from

if you check the errors objects are wrapped and enriched with context and call traces
(At the current version) I don't seem to be able to interpret "Error: Failed to anchor(Error)" as a "Please retry" indication...


Investigate a rewriter instead of the existing Sling filter

The existing Sling filter does its job extremely well but performance could be improved by using a rewriter instead of parsing through the DOM via XPath.

Closing as this functionality will be handled by https://www.aemvite.dev/guide/front-end/vite-plugin/


Please publish a new release to Rubygems

It looks like there hasn't been a release since October 2014. It might be time to push v0.4.0. :smile:

Hi,
I am not currently happy with the quality/stability of the QoS 1 implementation, which is why I have been delaying making a release.
But maybe I should just get on and release it; then let people submit fixes/improvements.
nick.

In that case, a prerelease might be more suitable (e.g. 0.4.0.beta). Otherwise it's looking like a lot of users are stuck with using a Git clone:
gem 'mqtt', github: 'njh/ruby-mqtt'

Sorry, I have been meaning to spend some time on ruby-mqtt and try and resolve the issues I see with QoS 1.
I have got distracted with other projects, so will release 0.4.0-beta today.

Version 0.4.0 has been released:
https://rubygems.org/gems/mqtt/versions/0.4.0
Fingers crossed it works well for everyone!


first-entity and second-entity crash when there are entities without a :body

Given you have entities with and entities without a :body in the same screen, trying to detect a collision will result in an exception:
Exception in thread "LWJGL Application" com.badlogic.gdx.utils.GdxRuntimeException: java.lang.Exception: The keyword :body is not found.
This is due to find-body using get-obj which throws the key not found exception.
I tried the workarounds:

assoc'ing :body true on those entities => exception on rendering
having only simulated entities in this screen, but it's rather inconvenient as I have a texture following an entity with a body

Did I get something wrong or wouldn't be better to ignore those entities without a body in the implementation of first- and second-entity?

Yeah that was definitely an oversight. I just fixed it and pushed 1.1.0-SNAPSHOT so you can try it out.

Tried it and the issue is now gone. Thanks for fixing and for this great project in general!


Mm 45108 viewer mode

Summary
This PR adds the Viewer mode to the Header and Checklist. Retrospective Viewer mode implemented in this PR: https://github.com/mattermost/mattermost-plugin-playbooks/pull/1248#pullrequestreview-1009998180
Header in Viewer mode:

no Finish run menu item.
no Go to channel button. We will need to add Get Involved button instead in v2

Checklist in Viewer mode is the same as for the finished run.

no add checklist item
no add checklist
no hover menu
no checklist drag

Ticket Link
https://mattermost.atlassian.net/browse/MM-45108
Checklist

- [ ] Telemetry updated
- [ ] Gated by experimental feature flag

[ ] Unit tests updated

I noticed that the collapse checklist icon doesn't work when you are a viewer. is that intended?

@trilopin  No, it's not intended. I tried and can't reproduce it. Do you make some steps before, or it happens every time?

Big move here @gbochora!

RD stores checklist info in the same redux state under the key=run_details_[runId]. So the same run will not share RHS and RD states.

I understand that collapsed state is designed to behave separately between RDP and Channels RHS, but I feel them as connected. Video attached.
https://user-images.githubusercontent.com/4096774/175897039-a2548784-9748-40bf-a4af-52ab2a4d8f29.mp4


zlib is not optional

Documentation and cmake behaves as if it was optional, defining WITH_ZLIB. However packbeam.c depends on it, calling inflateInit, inflate and inflateEnd.

This is also related to issue #33.


Scuffy

CME module: Scuffy
Similarly to .LNK abuse except .SCF file abuse.

Mistakenly opened. Ammending change


Debug mode (feature req)

I'm trying to figure out why I'm getting the following error:
Injection definition required for interface App\Domain\Shared\Specification\Specification

However, because of reflection I've no idea what's causing this. Some kind of 'debug' mode would be invaluable to me so at least I can see what's triggering the issue. The stack trace is useless unfortunately.

There is a method to get the in progress makes on the exception object. (Sorry on mobile so csn’t find it trivially)
If you print out those things being made it will show you what is requesting that specification object.
The error message means that is asking for that interface to be injected, but interfaces can’t be constructed; they need to either be aliased to a real class or delegated to a function to create an implementation.

Great, thanks for this - works nicely.


How can I adjust the sensitive of scrollview to hide/show the button

As the coding written now,
I need to scroll for a short distance in order to show/hide the button
Is there any method to change the sensitivity of the button
(just like the offsetY swipe for 5.0f to hide/show)
Thank You

No way right now. I will add it in few days.

Use plusButtonsView.scrollSensitivity = 20.f;


Remove ballerina-core dependency and any usages

Description:
ballerina-core (https://github.com/ballerina-platform/ballerina-lang/tree/master/bvm/ballerina-core)  java package contains old bvm types and values. This has been used only by several jballerina-unit-tests. We have migrated those to new java runtime and now there are no usages in the ballerina-lang.
But still some of standard libraries use ballerina-core and we need to remove them.
Using old implementation will cause unexpected bugs.

Most of the usages are only unused dependencies in gradle files.
https://github.com/ballerina-platform/module-ballerina-io/blob/f7d13698a2ef15c9f48077a6effa23e8e9f251c9/native/build.gradle#L28

The module list:

[ ]  io
[ ]  java.arrays
[ ]  random
[ ]  regex
[ ]  time
[ ]  url
[ ]  xmldata
[ ]  crypto
[ ]  log
[ ]  os
[ ]  protobuf
[ ]  task
[ ]  xslt
[ ]  cache
[ ]  file
[ ]  ftp
[ ]  mime
[ ]  nats
[ ]  stan
[ ]  tcp
[ ]  udp
[ ]  uuid
[ ]  auth
[ ]  email
[ ]  jwt
[ ]  oauth2
[ ]  http
[ ]  graphql
[ ]  grpc
[ ]  transaction
[ ]  websocket
[ ]  websub
[ ]  websubhub
[ ]  kafka
[ ]  rabbitmq
[ ]  sql
[ ]  java.jdbc
[ ]  mssql
[ ]  mysql
[ ]  oracledb
[ ]  postgresql

time and grpc packages do not have the ballerina-core dependency.

url, crypto, auth, jwt, oauth2 packages do not have the ballerina-core dependency.

sql, mysql and oracledb does not have ballerina-core dependency

Found core usage in ftp. removed in the above tagged PR.

GraphQL does not have ballerina-core dependency.

mssql and java.jdbc does not have the ballerina-core dependency.

xmldata, task, cache, file, regex, and postgresql packages do not have ballerina-core dependency.

It was unused in a test module.
https://github.com/ballerina-platform/module-ballerinax-aws.lambda/pull/630

Dependency is remove from HTTP and MIME

serdes does not have ballerina-core dependency.

Closing since the ballerina-core is now removed from the lang via https://github.com/ballerina-platform/ballerina-lang/pull/37685.


Add new Biomolecule data structure with mmCIF file parsing, and install latest PDB dataset filtering/clustering/caching scripts

Adds a new Biomolecule data structure with mmCIF file parsing, and installs the latest PDB dataset filtering/clustering/caching scripts.
Most of these "changes" are simply the addition of new dataset parsing scripts, so the git diff looks larger than it really is.
The purpose of this PR is to make sure the PDB dataset curation code in this main branch doesn't become too out-of-sync with my fork (so new users can start using the bug-fixed mmCIF file parsing and PDB dataset filtering code).

thank you Alex!


Remove the for ... of loop from the PDFDocument.fingerprint getter (issue 10401)

It appears that the Symbol polyfill doesn't work well in conjunction with TypedArrays, and that part of PR #10393 is thus reverted.
Fixes #10401.
/cc @timvandermeij

/botio test

IE11 strikes again... Thank you for fixing this so quickly!


Bookmarking both services & topics

On the Bookmarks page, we would like users to be able to see both saved topics and services, and navigate their saved items effectively between two tabs.
Mocks

Zeplin: View individual screens
Sketch Cloud: Clickable prototype, for flow

Note:
Original copy has been updated to say:

Save important topics and services...

Acceptance Criteria

[ ]  Services  and topics bookmarked show up on the bookmarks page

Steps for QA:

Delete all user data from the app
Bookmark a few services and topics
Review bookmarks page

Closed as a dupe of #841


Support new AWS archive format

Hi,
Creating this issue so other people know that the script needs tweaking for the new format 🙂
Unfortunately, I don't think I'll have time to contribute a fix 😞
For the latest icon release, 2020-09-11, AWS changed the format of the archive, now having separate Services and Resources.
The extracted archive now looks like this:
AWS-Architecture-Assets-For-Light-and-Dark-BG_20200911
├── AWS-Architecture-Resource-Icons_20200911
│   ├── Res_Analytics
│   │   ├── Res_48_Dark
│   │   └── Res_48_Light
│   ├── Res_Application-Integration
│   │   ├── Res_48_Dark
│   │   └── Res_48_Light
│   ├── Res_Blockchain
│   │   ├── Res_48_Dark
│   │   └── Res_48_Light

  ...

│   └── Res_loT
│       ├── Res_48_Dark
│       └── Res_48_Light
└── AWS-Architecture-Service-Icons_20200911
    ├── Arch_AR-VR
    │   ├── Arch_16
    │   ├── Arch_32
    │   ├── Arch_48
    │   └── Arch_64
    ├── Arch_Analytics
    │   ├── Arch_16
    │   ├── Arch_32
    │   ├── Arch_48
    │   └── Arch_64
    ├── Arch_App-Integration
    │   ├── Arch_16
    │   ├── Arch_32
    │   ├── Arch_48
    │   └── Arch_64

    ...

    ├── Arch_Security-Identity-Compliance
    │   ├── 16
    │   ├── 32
    │   ├── 48
    │   └── 64
    └── Arch_Storage
        ├── 16
        ├── 32
        ├── 48
        └── 64

186 directories, 0 files

Hey,
thank you for the info. I released version 1.1.0 with improvements to handle that. Now nested directory structure is supported, see example in README for how to adjust group (sheet) names. Also, I put a new stencil with 2020-09-11 icons in Stenciltown: https://stenciltown.omnigroup.com/stencils/aws-2020-09-11-all/

Wow, that was fast and unexpected! Thank you so much!
Turns out that AWS made a mistake and named the Light Resources inGeneral as *_Dark.svg, because of course there had to be something going wrong 🤣
After some experiments, here are the full commands for stencil generation, with all the options:
# Generate Service icons (big colorful squares, no theme version)
omnigraffle-stencil \
    --svg-dir "AWS-Architecture-Assets-For-Light-and-Dark-BG_20200911/AWS-Architecture-Service-Icons_20200911" \
    --stencil-file AWS_20200911_Services_Light.gstencil \
    --filename-includes _48 \
    --stencil-name-remove Arch_ _48 . - _ \
    --group-name-remove Arch_ . - _

# Fix badly named files from AWS
rename \
    's/_Dark/_Light/' \
    AWS-Architecture-Assets-For-Light-and-Dark-BG_20200911/AWS-Architecture-Resource-Icons_20200911/Res_General-Icons/Res_48_Light/*.svg

# Generate Resource stencils, for Dark backgrounds
omnigraffle-stencil \
    --svg-dir "AWS-Architecture-Assets-For-Light-and-Dark-BG_20200911/AWS-Architecture-Resource-Icons_20200911" \
    --stencil-file AWS_20200911_Resources_Dark.gstencil \
    --filename-includes _48_Dark \
    --stencil-name-remove Res_ _48_Dark . - _ \
    --group-name-remove Res_ . - _

# Generate Resource stencils, for Light backgrounds
omnigraffle-stencil \
    --svg-dir "AWS-Architecture-Assets-For-Light-and-Dark-BG_20200911/AWS-Architecture-Resource-Icons_20200911" \
    --stencil-file AWS_20200911_Resources_Light.gstencil \
    --filename-includes _48_Light \
    --stencil-name-remove Res_ _48_Light . - _ \
    --group-name-remove Res_ . - _

Yes, they made a few more mistakes. Service names are different between Services and Resources, and in one of them instead of IoT there is loT, with lowercase L 😆
I fixed those in the stencil I generated and put on stenciltown.


Slide changed callback on carousel controller

Use case
carousel_slider provides the callbacks requested in this issue , its unfortunately not an unconstrained view and instead enforces a fixed aspect ratio
Proposal
3.24 brought in the carousel view and its a welcome feature. Curiously it provides the snapping feature however couldn't find any builtin callback for when the items change or when the carousel snaps to any particular child on the widget or on the controller. Ended up using pageview instead for now. but it would be a great addition given snapping is available as an option. Also its common for carousels to have a slide indicator , if a callback and an index is available it would be handy to build those.

@RohanKPOfficial
Can you provide a code example that shows current limitation along with expected behavior using CarouselView so that we can properly address it ?


Improve the content-card-7

While going through the component I observe the following glitch in design
Improvement area of image:
Top-Left border-radius is not visible it's getting into the left corner.

Please checkout this is final design of this specific component
https://play.tailwindcss.com/DNcAeohyYU?size=864x1948

@Rajdip019 and @rupsha014 please review and assign me.

Don't need this particular right now. @Kumar-Ankit56


reduce.withIndex

reduce.withIndex
reduce with index
y = reduce((accumulator, xi, i, x) => nextAccumulator, init)(x)

(accumulator, xi, i, x) => nextAccumulator is an indexed reducing function
accumulator is the current y for a given iteration
xi is an element of x
i is the current index of xi
x is an Array
nextAccumulator is the accumulator for the next iteration
init is anything, including a function.
if init is a function, accumulator starts as init(x)
y is the transformed value according to (accumulator, xi, i, x) => nextAccumulator and init
y is a Promise if any of the following are true

(accumulator, xi, i, x) => nextAccumulator is asynchronous

const buckets = reduce((accumulator, xi, i, x) => {
  return [...accumulator, i];
}, () => [])(Array(10).fill("")); // [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]

no longer needed


[Example] add spring-ai-alibaba call others llms example

#59

https://github.com/alibaba/spring-ai-alibaba/pull/59

Help users quickly use spring ai alibaba to call other large models, including locally deployed ones such as ollama
#59

This issue has been resolved in this pull request    #59


Recommend security_invoker on views

On https://postgrest.org/en/stable/schema_structure.html#views
Search for security_invoker on https://www.postgresql.org/docs/current/sql-createview.html

Done on https://github.com/PostgREST/postgrest-docs/commit/8ec925c33eca90225a7b81c22511ef8297494559


[Feature Request] Add support for DPoP

Is your feature request related to a problem? Please describe.
Add support for OAuth 2.0 Demonstrating Proof of Possession (DPoP) because having one token binding standard just isn't enough.
Describe the solution you'd like
Any solution should be closely done in collaboration with the HttpClient and ASP.NET folks.
I could imagine an extension method on HttpRequest like request.SignWithDPop(jwk, nonce). Where close integration needs to happen is in server-side nonce cycling, as the response can contain an updated nonce which would need to be plumbed though

Hey - seems you read the spec ;)

Oh - and btw - we implemented all of that already of course
client side piece here:
https://github.com/DuendeSoftware/Duende.AccessTokenManagement
and JwtBearer extensions here:
https://docs.duendesoftware.com/identityserver/v7/apis/aspnetcore/confirmation/#validating-dpop-proof-of-possession


More extensive docs on what pydantic-core schema is, and how get_pydantic_core_schema should be used

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
As it stands, get_pydantic_core_schema looks like a magic incantation. The docs for customizing validation with get_pydantic_core_schema tell us it's used to tell pydantic how to generate the pydantic-core schema, but the docs for what exactly it is, and how it factors into custom class creation, are missing.
It would be good to have documentation explaining exactly what pydantic-core schema is, what pydantic does with it, and how it can be manipulated to construct custom types.
Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[ ] Data serialization - .model_dump() and .model_dump_json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

Does this section answers your questions?

I think we can probably ark this as a dupe of https://github.com/pydantic/pydantic/issues/7534, which covers this request. As @Viicos mentioned above, the architecture docs should be pretty helpful here.
If you feel like the above linked issue / architecture docs together don't address your requests / questions, let us know and we'd be happy to reopen! 🚀


feature/sanitize_logs

Sanitize logs based on regexes

Codecov Report

Merging #21 into master will increase coverage by 0.11%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
+ Coverage   86.04%   86.16%   +0.11%
==========================================
  Files          28       29       +1
  Lines         559      571      +12
  Branches       51       51
==========================================
+ Hits          481      492      +11
- Misses         78       79       +1

Impacted Files
Coverage Δ

...wbaa/airlock/proxy/util/MaskingPatternLayout.scala
91.66% <91.66%> (ø)

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 c587938...64e8c22. Read the comment docs.


aggregation on INT128 typed column crash nebula server

I0214 06:39:03.635987    18 Dsl.cpp:226] Query output schema: STRUCTflag:BOOLEAN,stamp.MAX:INT128 w/ agg columns: 1
I0214 06:39:03.636165    18 Dsl.cpp:354] Nodes to execute the query: 1
*** Aborted at<PHONE_NUMBER> (Unix time, try 'date -d @1613284743') ***
*** Signal 11 (SIGSEGV) (0x0) received by PID 1 (pthread TID 0x7fe177d5d700) (linux TID 16) (code: 128), stack trace: ***
(error retrieving stack trace)

Looks like this is only happening in Release build - it works fine in Debug build, interesting...
just fyi: @hukid @shuoshang1990

I think we kinda get bottom of it - this is the culprit that leads to segment fault
    return *reinterpret_cast<T*>(this->ptr_ + position);

For type T=int128_t - Debug build we can cast the 16 bytes memory address to value, but in release build, this is somehow causing segment fault.  I had put the fix for writing path for the same issue before, but didn't put it for read path, apply the same thing now to fix this.


VSCode Authentication error

Does this occur consistently? Yes
Repro steps:

Sign in azure storage on vscode
Redirect to Microsoft page to Login
[No authorization error]

Action: AzureTreeDataProvider.getChildren
Error type: AuthorizationFailed
Error Message: The client '---' with object id 'redacted:id' does not have authorization to perform action 'Microsoft.Storage/storageAccounts/listKeys/action' over scope '{scope}' or the scope is invalid. If access was recently granted, please refresh your credentials.
Version: 0.13.0
OS: linux
OS Release: 5.13.0-28-generic
Product: Visual Studio Code
Product Version: 1.61.2
Language: en

Call Stack
new RestError extension.bundle.js:2:663466
extension.bundle.js:2:652147
processTicksAndRejections task_queues.js:93:5

Thanks for filing this, @filipembmarques. When you attempt to list your storage accounts in the Azure Portal do you get a similar error? If you aren't able to get access there it's definitely an access control problem.
Similar: https://github.com/microsoft/vscode-azurestorage/issues/684

Thanks for filing this, @filipembmarques. When you attempt to list your storage accounts in the Azure Portal do you get a similar error? If you aren't able to get access there it's definitely an access control problem.
Similar: #684

I can access my storage account without any problem. But all storages in vscode extension are marked as invalid, even after sing in

@filipembmarques have you been granted reader rights to these accounts? There's an open issue to support this in the extension: https://github.com/microsoft/vscode-azurestorage/issues/967

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


probably memory leak: abi::__cxa_demangle()

template <typename Base>
bool PluginManager::IsLibraryLoaded(const std::string& class_name) {
  int status = 0;
  std::string base_class_name =
      abi::__cxa_demangle(typeid(Base).name(), 0, 0, &status);
  if (plugin_class_plugin_name_map_.find({class_name, base_class_name}) ==
      plugin_class_plugin_name_map_.end()) {
    // not found
    return false;
  }
  std::string plugin_name =
      plugin_class_plugin_name_map_[{class_name, base_class_name}];
  if (plugin_loaded_map_.find(plugin_name) == plugin_loaded_map_.end()) {
    // not found
    return false;
  }

  return plugin_loaded_map_[plugin_name];
}

as shown, a string obj constructed with a ptr returned by __cxa_demangle(), but never free.
and the string obj may not able to free this memory, who always destruct its own memory.
I'm curious if there is a memory leak here.
many thanks for your reply.

there's a memory leak.

Returns:
A pointer to the start of the NUL-terminated demangled name, or NULL if the demangling fails. The caller is responsible for deallocating this memory using free.

abi::__cxa_demangle malloc the memory, and caller need to free it. So here's a memory leak

there's a memory leak.

Returns:
A pointer to the start of the NUL-terminated demangled name, or NULL if the demangling fails. The caller is responsible for deallocating this memory using free.

abi::__cxa_demangle malloc the memory, and caller need to free it. So there's a memory leak

OK.
Not only this function, there are other functions call abi::__cxa_demangle and lost the memory.

In my local code, I fixed it like this:
struct DemangleDeleter {     void operator()(char* ptr) const noexcept {         free(ptr);     } };  template <typename Base> bool PluginManager::IsLibraryLoaded(const std::string& class_name) {   int status = 0;   std::unique_ptr<char, DemangleDeleter> demangled_name(       abi::__cxa_demangle(typeid(Base).name(), 0, 0, &status));   std::string base_class_name = (status == 0) ? demangled_name.get() : typeid(Base).name();   if (plugin_class_plugin_name_map_.find({class_name, base_class_name}) ==       plugin_class_plugin_name_map_.end()) {     // not found     return false;   }   std::string plugin_name =       plugin_class_plugin_name_map_[{class_name, base_class_name}];   if (plugin_loaded_map_.find(plugin_name) == plugin_loaded_map_.end()) {     // not found     return false;   }   return plugin_loaded_map_[plugin_name]; }
Other functions as the same.


Rs 2022.09.22

Hoo boy this file looks long

I hate being right

Sounds good to me, will update that and review the feedback on the last pr
tomorrow. Thanks
On Tue, 27 Sept 2022, 23:40 Petrikow, @.***> wrote:

@.**** commented on this pull request.
In script/Ciel/Day 7/07_01_CIEL07_6.txt
https://github.com/Tsukihimates/Tsukihime-Translation/pull/996#discussion_r981911979
:

}

[sha:b245d1754fbf8656e8faafa029a092d779c3704f]{
-- Page 548, Offset 16123.
-- わずかな戸惑いもなく解体する。血の匂いを、手触りのない肉の<断触|だんしょく>を記憶する。
-// ebin nasu pun <断触|だんしょく>
-// after this line, the visuals show Shiki remembering cutting Arcueid apart.
-I commence the dismemberment without an inkling of hesitation.

I recall the smell of blood――the warm cuts of her untouched flesh.

+// P: ebin nasu pun <断触|だんしょく>
+// P: after this line, the visuals show Shiki remembering cutting Arcueid apart.
+// R: Just to make sure I understand this, the pun is <feeling of cutting|warm colour>?
+// R: Where the warm colour is of course more blood?
+I don't even so much as hesitate as I dismantle them.

I recall the smell of blood, the feeling of slicing through her untouched flesh, and the warm color that spilled from it.

Maybe just move warm to blood and remove the last clause.
I recall the warm smell of blood, the feeling of slicing through her
untouched flesh.
—
Reply to this email directly, view it on GitHub
https://github.com/Tsukihimates/Tsukihime-Translation/pull/996#discussion_r981911979,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS4V72AVZWVNVBDVIPMQJ3WAO427ANCNFSM6AAAAAAQU2YYXY
.
You are receiving this because you authored the thread.Message ID:
@.***>


RuntimeError: mat1 and mat2 shapes cannot be multiplied

Thank you so much for this resource! I was trying to apply to my own spatial dataset and ran everything successfully through cel.Fit_cord. However, when I ran cel.Predict_cord, I received the following error:

I'm new to Scanpy so maybe an issue with the way I prepared the anndata? Thanks for looking into this!

Have you checked that your Test data has the exactly same dimension (number of genes) as your training data? If not, you might need to obtain the common genes for both.

The suggested fix worked. Apologies, I just saw the indicated checks further into the tutorial than I had reached. Maybe consider putting those in the beginning as well? Thanks again for this package!


[DNM]Test if any CI test doesn't really need cpp client

Can you test it in your repo? It will faster than in apache repo

@zymap I suspect personal GitHub repo can get less compute resources in GitHub actions, which will lead to a different result, so I may still use the apache repo while using my self's, if the test is large it may timeout in the personal repo but not in apache repo
See: https://github.com/Renkai/pulsar/pull/1

I think all Github hosted runner use the same resource: https://docs.github.com/en/actions/reference/specifications-for-github-hosted-runners#supported-runners-and-hardware-resources


[Improvement-14456][UI] When making the process online the system should remind user to take care of its offline timing.

Purpose of the pull request
This PR will close #14456 .

Brief change log

Verify this pull request
This change added tests and can be verified as follows:

Manually verified the change by testing locally.

The test results are as follows:

Codecov Report

Merging #14460 (c7138e9) into dev (76b1eef) will decrease coverage by 0.03%.
The diff coverage is n/a.

:exclamation: Current head c7138e9 differs from pull request most recent head 445ca97. Consider uploading reports for the commit 445ca97 to get more accurate results

@@             Coverage Diff              @@
##                dev   #14460      +/-   ##
============================================
- Coverage     38.54%   38.51%   -0.03%
+ Complexity     4561     4555       -6
============================================
  Files          1237     1237
  Lines         43462    43383      -79
  Branches       4812     4794      -18
============================================
- Hits          16754    16711      -43
+ Misses        24850    24814      -36
  Partials       1858     1858

see 63 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Please handle CI errors.

@songjianet Those errors have been worked out.


[Windows] Error occured while processing files

After upgrading to the latest version of Pathephone, I tried to upload a folder, but I got a mysterious error. It works fine on Ubuntu, but not on Windows.

I tried to use those exact same files in Ubuntu, and it still doesn't work. It's worth nothing that they are .m4a files.

@NatoBoram can you provide a list of file extensions from this folder. I have tested Pathephone with this https://cdn2.online-convert.com/example-file/audio/m4a/example.m4a one and it was properly handled. Maybe there are some other files that may cause an error?

It's exactly this folder : https://cloudflare-ipfs.com/ipfs/QmP25nWYHnjcZpuqvdKFPnEzeaq2NfNEwR3ZNmdWuCA4Rf


Render from a new viewpoint

Hi, thanks for your great work! I'm tying to render the output from a different point of view and I'm using the command 'python render.py --model_path "output/dnerf/bouncingballs/"  --skip_train --configs arguments/dnerf/bouncingballs.py  &' but I only get the initial position of the input video. How can I change the viewpoint before rendering the video?

Just customize code in the dataset_readers.py and get video poses

Thank you for your answer. I tried to do what you suggested as you can see in the commented lines. I'm not sure if I modified the correct section of the script because it didn't work.

Could you give me some advice?


Remove all refs to libtensorflow_framework because of duplicate symbols.

This was causing XLA to not get triggered because it was linking into a different address space.

@swift-ci please test tensorflow

I think there are some missed references to libtensorflow_framework:


Lift XRTK to 2020.3 and establish support

XRTK - Mixed Reality Toolkit Pull Request
Overview
This is a draft PR. Once done it will lift all XRTK modules to 2020.3 and make 2020.3 the officially supported and recommended version for XRTK.

Will need refreshing with Dev status @FejZa , are there any impediments to progressing this PR?

Refreshed this with current dev to move things along @FejZa

Guys do not worry too much about this one. It's a draft PR and only for my personal book keeping. Everything will be extracted and split where needed when ready.


Absent window names shouldn't break quickswitch

Currently misbehaved applications can break quickswitch by not setting a window title.

Maybe we should try to display them otherway? I doubt this kind of window will not have at least a class.
Have you an exemple of misbehaving software?

neat, thanks

@milouse if you figure out a good way to do that, feel free to make a pull request. Maybe generating window titles such as unnamed window 1 would be alright

I have no idea if there are any such applications out in the wild.  In my case it was a prototype I was testing where someone forgot to set the title :).


Status is always shown as No gitflow

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] puppy => You're not submitting a puppy. I already have one and he's adorable

What is the current behavior?
On repositories where gitflow is setup, the status bar shows as No gitflow. I have tried to re-init the git flow by doing a git flow init -f but the result is still the same.

Is this a bug? Sorry about that. If so give me explicit details how to reproduce:

Open PhpStorm
Install version 0.7.0 (modify the metadata info to get it installed in build 193)
Notice in the bottom corner that the status is shown as No gitflow

What is the expected behavior?
That there is the option to perform git flow operations.

What is the motivation / use case for changing the behavior?
It does not work as expected at the moment.

Please tell me about your environment:

Gitflow4idea version: 0.7.0

Gitflow version: 0.4.1

IntelliJ Help -> about > click copy icon and paste here. Should look like this:

    PhpStorm 2019.3 EAP
Build #PS-193.3519.40, built on September 23, 2019
PhpStorm EAP User
Expiration date: October 23, 2019
Runtime version: 11.0.4+10-b480.2 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.6
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Registry: run.processes.with.pty=TRUE, debugger.watches.in.variables=false
Non-Bundled Plugins: BashSupport, Gitflow, String Manipulation, com.kalessil.phpStorm.phpInspectionsEA, izhangzhihao.rainbow.brackets, net.seesharpsoft.intellij.plugins.csv

Other information (e.g. detailed explanation, stacktrace, related issues, suggestions how to fix, links for me to have context words of praises, pictures of puppies (again with the puppy??) )
Running git flow commands from the command line works.

Hi,
I have the same problem with Android Studio 3.5.1 and MacOS Catalina.
Android Studio 3.5.1 Build #AI-191.8<IP_ADDRESS>00203, built on September 25, 2019 JRE: 1.8.0_202-release-1483-b49-5587405 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.15

Please note that there are two different implementations of git-flow. Since you are working under macOS, you probably installed it via brew. Is that correct?
Homebrew Formulae:

git-flow
git-flow-avh

Latest git-flow release is from 2011. It seems to me that git-flow-avh is kind of the successor of git-flow as it is still actively maintained (and by the way also the default in Debian)
See also the setup section at git-flow cheatsheet

From what I can tell I have git-flow installed as I also have version 0.4.1.
$ brew info git-flow
git-flow: stable 0.4.1 (bottled), HEAD
Extensions to follow Vincent Driessen's branching model
https://github.com/nvie/gitflow
Conflicts with:
  git-flow-avh (because Both install `git-flow` binaries and completions)
/usr/local/Cellar/git-flow/0.4.1 (18 files, 119.2KB) *
  Poured from bottle on 2018-07-12 at 22:50:14
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/git-flow.rb

Should I install git-flow-avh instead?

@roland-d At least I would try it. I had the same problem because I accidentally installed "git-flow" instead of "git-flow-avh".
You may also need to "git flow init" the repository again.

@gn-jgeerds Thank you for the tip.
So I did the following:

I removed the git-flow
installed git-flow-avh
forced the git init with git flow init -f
Restarted PhpStorm
Now I can see the git actions again

The only thing I do see (or rather not) is the gitflow icon:

Notice the empty space before the lock, I have to click there to see this:

Any tips for that? ;)

fyi I'm on vacation until the end of the month - will have a look as soon as I'm back. Sorry for the wait

@OpherV No problem, enjoy it while you can. I am gone myself at the end of the week and be quiet for a while :)

@gn-jgeerds Thank you for the tip.
So I did the following:

I removed the git-flow
installed git-flow-avh
forced the git init with git flow init -f
Restarted PhpStorm
Now I can see the git actions again

The only thing I do see (or rather not) is the gitflow icon:

Notice the empty space before the lock, I have to click there to see this:

Any tips for that? ;)
Edit: This only seems to happen on projects with multiple git repos (submodules)

I did the same and it's work.
Thank you

@gn-jgeerds Thank you, too. Switching to git-flow-avh solved the problem for me, too 😊
@OpherV: Hope you had a nice vacation! Perhaps your plugin could check git flow version and show some notice on 0.4.1...

Please add confirmation dialog after selecting finish feature.
In general after selecting every item that can be selected by accident and can cause trouble.

Should be better now with 0.7.1
I do see @roland-d's issue in some cases but haven't found out the cause yet.
The blank space does disappear once you switch between files in the editor.
I'll probably be able to pinpoint the issue in a later version


Lock Management

Is there a chance someone can help me with an example for Lock Management device?
Thank you

Start by asking specific questions

I would like to create an ESP home kit enabled lock that... The ESP would be connected to an electric door lock controlled via a relay...  (
I guess this would have to use the 'Lock Management' or Lock Mechanism home kit service....
I don't know where to start with this can someone point me to some docs about this?

Well, that ESP relay is fine, but I hope you understand that you also need an actual lock which has some kind of actuator/magnet lock which you will control with a relay.
So, according to HAP spec, your lock needs to have two services - Lock Mechanism (primary service) and Lock Management. Lock Mechanism is pretty straight forward: you have current lock state and desired lock state. If your lock mechanism does not provide you feedback on current state, just return desired state as current state (assume everything works).
Lock Management is there to allow vendors to implement custom control mechanisms (like managing users who can lock/unlock door), but you probably do not need that. So, Lock Control Point characteristic can be left empty (it's write only characteristic, just do not do anything there). Version characteristic is just a string.

Is this based on https://www.espressif.com/en/products/software/esp-homekit-sdk ??

No, it's not. Thing is that to produce and sell HomeKit compatible accessories, your company need to be certified for that (https://developer.apple.com/homekit/, If you’re interested in developing or manufacturing a HomeKit accessory that will be distributed or sold, your company must enroll in the MFi Program.) Espressif have their implementation of HomeKit framework, but it will give you it only if you have MFi certification.
This project is a non-commercial implementation of HAP protocol, not meant for commercial use.

This is for a hobby project ... I want to just find some documentation... how to get started with this...
I think my specialty leans itself more on the hardware engineering, so I a not proficient at coding so I always tend to rely on some documentation to get me going.... Thanks for help

Thanks i will try to do something

hi,
I'm also having problem with the lock Management service... did you succeed to implement it in your lock?


TypeCase broken on shapeless 2.3.3 only in scala 2.12.x

I was upgrading a current project to scala 2.12.6 and got into the following behaviour:

TypeCase compiles and works for shapeless version 2.3.2 on both scala 2.11.x and 2.12.x
TypeCase fails to compile using shapeless version 2.3.3 on scala 2.12.x but compiles as works fine on scala 2.11.x

The following error is thrown:
No default Typeable for type Protocol.SpecificCommandOne capturing an outer type variable
[error]   private val someMessage = TypeCase[Payloads.Payload[SpecificCommandOne]]
[error]                                     ^
[error] one error found

I managed to extract an example with a structure very similar to what I have on the project (which is much more complex) here - https://gitlab.com/vascorsd/broken-shapeless
Also made a scastie version here - https://scastie.scala-lang.org/6cODaCGGR62ZXsxoLiYfkg
They could probably be reduced much more, but that's what I got.
On the project I was only using shapeless 2.3.2 and didn't get that error until I also upgraded some dependencies and the shapeless version got forced to become the 2.3.3. Here the evicted log from sbt:
[info]     * com.chuusai:shapeless_2.12:2.3.3 is selected over 2.3.2
[info]         +- io.circe:circe-generic_2.12:0.9.3 ()               (depends on 2.3.3)
[info]         +- org.tpolecat:doobie-core_2.12:0.5.3                (depends on 2.3.3)
[info]         +- org.reactivemongo:reactivemongo_2.12:0.12.5 ()     (depends on 2.3.2)

Currently I solved the problem with the followng line on my sbt, forcing the shapeless version down as I really wanted to do the upgrade of the project to scala 2.12.6:
  dependencyOverrides ++= Seq(
    "com.chuusai" %% "shapeless" % "2.3.2"
  )

Hope this helps. I'm not sure if my current solution may break something else unexpectedly.
I read other similar bugs about on the bug tracker about TypeCase and Typeable but they don't seem to be this exact case.

Interesting, thanks for the report.
It looks as though TypeCase is treating the nested Prop as if it were a captured type variable rather than as a stable concrete type ... if you move Prop to the top level your example compiles successfully.
I think it should work as written. Do you fancy taking a swing at fixing the bug?

Hi, thanks for confirming it's not a known bug.
I was looking before around the code I think is relevant to the issue in https://github.com/milessabin/shapeless/blob/808ba2384c257ff1d77e47522afb3ff3b78f7a81/core/src/main/scala/shapeless/typeable.scala#L454 and https://github.com/milessabin/shapeless/commit/808ba2384c257ff1d77e47522afb3ff3b78f7a81#diff-50e8c1d37a867a5cb03f58d644c92059 but I can't say I understand much of what the code is doing :/
Also as it seems dependent on the scala compiler version it is even more strange for me.
Do you have any ideas or suggestions about what it could be?
I don't currently have much time to dedicate to problem at hand, so unless it is something really straightforward don't wait for me ;)

It looks to me as though the problem is most likely in the definition of closesOverType just above.

I have a PR that touches this area #803. It removes the closesOverType method altogether. You could try if that works.

At least the discussion might be relevant, esp. the last comment https://github.com/milessabin/shapeless/pull/803#issuecomment-355751418

@joroKr21 seems to work properly with your PR... Although as this  example has no abstract type members or type projections, I still can't grasp what's going on... Mainy what differs from Scala 2.11 to 2.12 here. Still, I'm not confortable at all reasoning about   these sort of advanced macros and type system corner cases.

Hello again.
I've got a little more time around this trying to figure out some kind of pattern and discovered a few more things. At least I got the example to compile under a specific case. I've updated the example code I first provided: https://gitlab.com/vascorsd/broken-shapeless
There's two different things going on here it seems: notice that in the Main.scala there are two TypeCase instances being generated. The first one compiles, the second one doesn't.
In the first one that compiles we got a top sealed trait called Command, then a QueryCommand trait that extends it and then an InternalQuery trait which then has case classes extending it. When we summon TypeCase for this middle trait QueryCommand it works. On the case that doesn't work it's just a SpecificCommandOne trait that immediately has the specific case classes extending it and when we summon the TypeCase it fails. So I believe this indirection may be related somehow.
I got the whole example to compile doing the following: on the SpecificCommandOne change the two vals to defs. It just works without further changes.
That's what I got. Hope it helps. Sorry for maybe being too confusing :/ .


Task: Update configuration handler to support 'reflector' parameter

Task specific

Should it allow destination port(s) to be specified on the reflected host?

General

The configuration format may need to be altered or extended - sections would be useful.

Fallthrough of UDP handling from Cisco to Juniper would be an expensive strategy with more than two supported protocols.
May be desirable to have separate listen addresses and or port ranges per protocol supported
Should be backwards compatible

INI format does stand out - backwards compatibility can be achieved by assigning all attributes before a section as into a "legacy" section.


Restrict pythonJSONLogger to v2

V3 of that library has a deprecated logger that is caused images to fail to run.
Type of change

Bump-up dependent library (no changes in the code)

Checklist

[ ] pre-commit run -a passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.86%. Comparing base (ae1f7e9) to head (5befffe).
Report is 18 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #342   +/-   ##
=======================================
  Coverage   85.86%   85.86%
=======================================
  Files          28       28
  Lines        1196     1196
=======================================
  Hits         1027     1027
  Misses        169      169

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Bug: Hide Views setting breaks the spacing between username and post time on QRTs

Ordinarily, Twitter adds an element containing just the string · between the username and date of a quoted tweet. However, if hideViews is enabled, that element is hidden, resulting in no space:

On my browser, that element is hidden by the selector [data-testid="tweet"][tabindex="-1"] div[aria-hidden="true"]:nth-child(2):nth-last-child(2) defined here. I suspect it needs to be specified further. https://github.com/insin/control-panel-for-twitter/blob/ea29f0d29dcd03cc01034dee08bd198d97194b4b/script.js#L1918-L1924

The joys of modifying a React Native for Web app without touching the DOM.


Review E-Prescriptions app template addition

Hi @laujan, can you please review my update to app-templates.md that includes the blurb about the new E-Prescriptions app template? Thanks in advance!

Docs Build status updates of commit 6d85936:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/e-prescriptions-app-template.PNG
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f45ab93:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/e-prescriptions-app-template-admin.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/e-prescriptions-app-template.PNG
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b07bf86:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b07bf86:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/e-prescriptions-app-template-admin.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/e-prescriptions-app-template.PNG
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 146f22f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/e-prescriptions-app-template-admin.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/e-prescriptions-app-template.PNG
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 785888e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/e-prescriptions-app-template-admin.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/e-prescriptions-app-template.PNG
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit ebc9f0c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/e-prescriptions-app-template-admin.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/e-prescriptions-app-template.PNG
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 04d9a93:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/e-prescriptions-app-template-admin.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/e-prescriptions-app-template.PNG
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7414eb6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/e-prescriptions-app-template-admin.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/e-prescriptions-app-template.PNG
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3e349e6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/e-prescriptions-app-template-admin.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/e-prescriptions-app-template.PNG
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit aef2186:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/e-prescriptions-app-template-admin.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/e-prescriptions-app-template.PNG
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 4f4424f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/e-prescriptions-app-template-admin.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/e-prescriptions-app-template.PNG
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Add RJV supply

RJV is part of SingularityNET family and has same endpoint as AGIX and NTX, just with RJV in query parameter.
Matches what is displayed on CMC as well.

Endpoint is throwing 500 error now.. wait to merge this one.

@TheTapHouse  I will convert this PR to draft, pls reopen when the endpoint gets the total supply is working

Looks like these endpoints are working now after testing a few times throughout the day. They would throw 500 the second time you tried to load them before.

Looks like these endpoints are working now after testing a few times throughout the day. They would throw 500 the second time you tried to load them before.

can u fix conflict?


Hide statute amendments checkbox

first step of #3085

If I understand the Code correctly this option cannot simply be called but needs new implementing.
Given that we do not plan to hide settings in general, but just for the moment, I would prefer this temporary workaround
But I could misunderstand the code. @bastianjoel what do you think about this?

Why not simply remove the setting from the definition list? Seems cleaner than implementing this workaround.  @emanuelschuetze the hide attribute was probably in OS3 - in OS4, this does not exist (yet).

Why not simply remove the setting from the definition list?

Removing it in the definition-list makes it completely unusable. Other files need the definition to determine whether or not statutes are allowed

I meant from the meeting-settings-definition.ts. That only defines what is displayed where in which group and not which settings are generally available.

The previous suggestion did not work since the MeetingSettingsDefinitionService parses the definition list to determine which fields to request, which I did not know. I implemented a more general solution instead which can hide arbitrary entries, like @emanuelschuetze suggested. @Elblinator please review.

Looks very nice and clean :)


Training time

Could you please provide a detailed description of the GPU used and training time? I am trying to reproduce your results. I set the batch_size to 24 and used dual 3090 GPUs for training. It cost 4.34h for one epoch. Is this reasonable?

I have the same question，I don't know if it's my own problem，Hope to receive a response from the author！


C_CPP : Two Pointers Technique (Documentation)

Description 📜
I want to create documentation explaining two pointers technique with code examples.

Domain of Contribution 📊

[x] C/CPP

/assign

/assign


Add GCP Auth to our Github Actions

Describe the feature you'd like to request
We need GCP auth in our github actions to run some things against bigquery
Describe the solution you'd like
see above
Describe alternatives you've considered
n/a

OBE. Already done


🚀 Initial Commit for Flame Lines

@jabo-bernardo, since you haven't replied in a while I'm closing this PR. Reopen if needed


Problem about IMU coordinate system

Sorry to bother,
I am using Tamagawa TAG300N1000 IMU in egaleye, but the result is not satisfied. The movement that eagleye predicts seems having a wrong direction against the gnss signal.
Blue line is gnss signals and the red line is the prediction from eagleye. When the prediction activates, it owns a correct distance but wrong direction.

I guessed it is due to wrong coordinate system. I would like to make sure whether my IMU settings is correct. IMU in my system has x-direction for head of car, y-direction indicates the right of car, and z-direction points to the ground currently.
Do I need to add transform or change the settings of the imu to make the eagleye works?
Thanks.

"Please change the following true/false values. Alternatively, modifying the tf of base_link-imu is also acceptable.
https://github.com/MapIV/eagleye/blob/autoware-main/eagleye_rt/config/eagleye_config.yaml#L30

Thanks for the response,
I changed reverse_imu_wz factor to true, but it seems that the result is not improved.

It may not be an issue with the IMU coordinate system. If you could provide the rosbag, I can check what the problem might be.

This is the link of the ros2 bag: https://drive.google.com/drive/folders/1gwB4HfVbIHz_Lkaxrx9eUYSB5y6vEhls?usp=drive_link
I am using:
/rav4/ma65/fix                      #gnss position (2 hz)
/rav4/ma65/gnss_vel            #gnss velocity (2 hz)
/rav4/adv_nav0/can_twist    # wheel speed
/imu/data                              # tamagawa imu (200 hz)
/rav4/adv_nav0/imu             # another imu (50 hz)

I only have geometry_msgs/TimeStamped for gnss velocity topic in the bag. So I canceled the covariance checking in https://github.com/MapIV/eagleye/blob/main-ros2/eagleye_util/gnss_converter/src/gnss_converter_node.cpp#L112 to make it works.
Thanks you a lot, sorry for taking your time.

I can't say for sure if this is the cause, but it feels like the car speed sensor's resolution is too rough. It seems a bit difficult, so I'll take another look at it later.

Some update:
I try to use canless mode to get rid of the influence of the speed sensor. Eagleye will start as every gnss point it received and predict the path until getting next gnss signal. However, it seems that the direction of predicted path is incorrect as well.

This is my settings of config:
  ros__parameters:
    # Estimate mode
    use_gnss_mode: RTKLIB
    use_can_less_mode: true

    # Topic
    twist:
      twist_type: 0 # TwistStamped : 0, TwistWithCovarianceStamped: 1
      twist_topic: /rav4/adv_nav0/can_twist
    imu_topic: /imu/data_raw
    gnss:
      velocity_source_type: 4 # rtklib_msgs/RtklibNav: 0, nmea_msgs/Sentence: 1, ublox_msgs/NavPVT: 2, geometry_msgs/TwistWithCovarianceStamped: 3
      velocity_source_topic: /rav4/ma65/gnss_vel
      llh_source_type: 1 # rtklib_msgs/RtklibNav: 0, nmea_msgs/Sentence: 1, sensor_msgs/NavSatFix: 2
      llh_source_topic:  /rav4/ma65/nmea_sentence

    sub_gnss:
      llh_source_type: 1 # nmea_msgs/Sentence: 1, sensor_msgs/NavSatFix: 2
      llh_source_topic:  /sensing/sub_gnss/nmea_sentence

I added a message of type geometry_msgs/TwistStamped to receive gnss message. It is similar to geometry_msgs/TwistWithCovarianceStamped but without check of covariance.
I am not using RTK, so I set up the RTK bit manually. My target is receive an acceptable localization result with more than 10 hz. So I try to replace the computed velocity with wheel speed to find whether it works.
I will check the hardware settings and test whether it is the speed sensor yeild the bad performance.  Thanks for the suggestion.

Sorry to bother,
I had update the speed sensor and made it usable. I used tamagawa IMU with x point to driving direction, y to right door.
I set the roll of imu to 180 degree in tf.launch.xml file to correct the coordination system and working on the main-ros2 branch.
<group>
      <push-ros-namespace namespace="imu"/>
        <node name="static_transform_publisher" pkg="tf2_ros" exec="static_transform_publisher" args="0 0 0 0 0 3.1415926 base_link imu">
        </node>
</group>

However the result is not satisfied, the moving distance can be correct while the direction is incorrect. Is there some idea of how to correct it, thanks.

The blue dot is orignal gps signal with 1 Hz, and the red line is eagleye fix.

Does changing the reverse_imu_wz to true/false make any difference?
Does the value of the eagleye heading topic seem correct? If it is incorrect, the coordinate system of the gnss speed in the velocity_source_topic might be wrong. It requires the speed in the ECEF coordinate system.

It was the issue of gnss coordinate system. I used NED to record speed rather than ECEF previously, the result is more reliable after I changed it to ECEF coordinate system, thank.
And some random question, will Eagleye work when gnss signal is unstable? For example: The signal may disappear some seconds when and resume.

If there are no GNSS observations, Eagleye will perform dead reckoning using vehicle speed and the IMU, so it won't be a problem for a few seconds, but the error will gradually increase over time.

Sorry to bother again, after I change the unit of gnss velocity, I collect the data again. Eagleye route has similar direction with gps initially, but the error grows and the direction is wrong after a turn.

I am doing the following settings when using eagleye

I am working on main-ros2 branch. It will do the following transform to imu

tf_converted_imu_.angular_velocity.y = (-1) * transformed_angular_velocity.vector.y;
tf_converted_imu_.angular_velocity.z = (-1) * transformed_angular_velocity.vector.z;
tf_converted_imu_.linear_acceleration.y = (-1) * transformed_linear_acceleration.vector.y;
tf_converted_imu_.linear_acceleration.z = (-1) * transformed_linear_acceleration.vector.z;

Since I setup tamagawa imu with x point to driving direction and y to the right door. I add 3.1415926 to roll
<node name="static_transform_publisher" pkg="tf2_ros" exec="static_transform_publisher" args="0 0 0 0 0 3.1415926 base_link imu">

I have gnss velocity in ecef coordination
I have stable gnss position result, and in most of the time (>97%) gnss velocity is valid.
My imu is run in 200 Hz, speed sensor in 100 Hz, and GNSS in 2 Hz.

It will be grateful if you can give some suggestions of how to modify the settings, thanks a lot.

If you set log_output_status to true, a log CSV file will be generated in the install/eagleye_rt/share/eagleye_rt/log/ directory, so could you please upload that?
https://github.com/MapIV/eagleye/blob/main-ros2/eagleye_rt/config/eagleye_config.yaml#L129

Here is the csv file.
https://drive.google.com/file/d/1GhdjTwzGbspmCjXY2dL0LocrYHegyP2Q/view?usp=sharing

Could you please change the imu_rate from the default of 50Hz?
https://github.com/MapIV/eagleye/blob/main-ros1/eagleye_rt/config/eagleye_config.yaml#L37

I feel like the GNSS speed performance is poor, which seems to be degrading the performance of the velocity scale factor. Could you filter the GNSS speed input to Eagleye using covariance or something similar?

Dear author,
Sorry to bother.
I have tried a bunch of methods but still not able to get something like covariance of velocity in my current gps, but I found the position information from gps is much more reliable. Can I make eagleye run with more weight on position information?
Or can the prediction always start from the known latitude and longitude given by gps?
Thanks.

Hmm... Eagleye estimates the heading using GNSS velocity (so it can accurately estimate the attitude even without RTK FIX). Therefore, if the heading is incorrect, the position estimation will also become inaccurate...
As an alternative, you can use RTKLIB and rtklib_ros_bridge to calculate GNSS velocity that is more suitable for Eagleye, but the setup can be quite challenging.
https://github.com/MapIV/rtklib_ros_bridge


Rabinkarp - Pattern Searching Algorithm | C++

Title - Rabinkarp - Pattern Searching Algorithm | C++
what will change - Adding Rabin karp Pattern Searching algorithm
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] C++

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding,

Please assign this to me

I already made the issue on this and also created the pull request.

check issue #359

Also, you can make a pull request for an issue only if you are assigned to it.

@atish-90 Thanks for pointing it out.


Change color channel from BGR to RGB for darknet preprocessing

Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.
In the preprocessing for images in darknet we need to change the color channel from bgr to rgb.

Thanks @vizero1 @cchung100m This is merged.


Update Windows Docker engine to >= v25.0.4

Tool name
Docker Engine
Add or update?

[ ] Add
[X] Update

Desired version
25.0.4
Docker engine was pinned to v24 in #9208 in Jan due to bugs in v25. Have these been fixed? v25.0.4 includes BuildKit WCOW support via buildx v0.13.0, which took a few years so I'm pretty keen to start testing.

@MaksimZhukov should this issue stay open to track progress, and the bugs you mentioned? v24 also has 4 CVEs (2 critical) that are only resolved by upgrading to v25


Can't get the Bearer Token

Hi, how do you get the token despite them using certificate pinning?  As far as I know I'd have to decompile the app and repackage it. How did you manage to do this? @Exaphis

@mustafahafidi I personally just used an older Android device.

would anybody be so kind as to share a bearer token? it's not a risk or anything is it.

Unless he's using any method that doesn't involve root certificate installment (and so which requires a rooted device), I don't think a lower android version can bypass the certificate pinning they're using.

I had done it in the past with a 7.0 device but I can't for the life of me figure it out now. sigh


[LiveComponent] Fix morphing for Alpine.js v3

Q
A

Bug fix?
yes

New feature?
no

Issues
/

License
MIT

This PR fixes live component compatibility for Alpine v3.
Currently, the live component controller already implements the Alpine morph plugin. This works fine for Alpine v2, but since v3, the __x property is no longer used by Alpine. Instead, we can check for _x_dataStack.
Also, the morph plugin no longer requires the __x property; the DOM element should be used instead.
I made sure the changes support both Alpine v2 and v3.
Original implementation and issue:

https://github.com/symfony/ux/issues/984
https://github.com/symfony/ux/pull/1126

Hi,
My current test setup uses a reversed logic; an alpine element inside of a LiveComponent. The morph is necessary to keep the alpine state when a LiveComponent re-renders with DOM changes.
But as your video shows there might be an issue with LiveComponents inside an Alpine element. Oddly enough I also tested this and did not see any weird behaviour. Both with an alpine component surrounding a LiveComponent as well as sharing the same DOM element.
Could you share more details about how your setup is structured in Twig?
That said, this shows the PR has a breaking change and it should not be merged (yet).


Save scroll speed to db

Scroll speed used on a song should be remembered and sent to the database.  Default database value should be null in case we change default values in the code.

This would cause problems since we don't save the text size to the database.

Hi cullub,
Could this be reopened?
Even without text size being saved scroll speed would still be very useful.
In Issue 75 there's also a secondary request for scrolling speed to be saved.
If it can be reopened I'd be happy to work on it.

I reopened this, and added the feature to the latest release. Scroll speed is now saved (although on a whole-app basis as a preference). Feel free to open another issue if you'd like improvements to this feature.


[Improvement] Improve E.cash search for group chats

If you haven’t already, check out our contributing guidelines for onboarding!

Platform - version:  All
Problem
Search is frequently how I find a given chat. There are two main problems I currently have with it:

It doesn't work well for group chats. For example I can't type in Lauren Andrew in order to find my group chat with Lauren and Andrew.
It looks for the whole string that I type in to be a match, rather than looking at whether there is a matching user for each word. For example, when I search Alex Revelli nothing comes up because she she is listed as Alexandra Revelli. I would think that she would still show up because the second word in my search, Revelli is a match to her user.

Why is this important?
Easy search makes Expensify.cash an easier, lighter experience.
Solution
Update search to work as follows:

split search string on spaces
return all exact and partial matches to each string
order results by most recent message (meaning the most recent message posted in the chat)

Upwork Job link: https://www.upwork.com/jobs/~01ccd27d2ef43f2d7f

Hi @NicMendonca ,
I would like to work on this issue. Here is my proposal:
I found that search results are generated in ChatSwitcherView.updateSearch() function. I’m planning to modify the following for loop.
https://github.com/Expensify/Expensify.cash/blob/c0069cf6e2df94ba7c3a2c242cf9e6a9c82ddd30/src/pages/home/sidebar/ChatSwitcherView.js#L424-L451
I’m going to split search string on spaces and create an array of words.
isMatch condition should be changed such that our regex matches should work for all words from search string.
https://github.com/Expensify/Expensify.cash/blob/c0069cf6e2df94ba7c3a2c242cf9e6a9c82ddd30/src/pages/home/sidebar/ChatSwitcherView.js#L429
I have a question for ordering results. I see there is an existing ranking that ranks exact matches higher. Do you want me to preserve this ranking or should we order all matches by most recent message time? To implement this, I’m going to sort all search options  by most recent message time that is not available in this function. I need to pass that value somehow.

Hi @NicMendonca ,
I would like to work on this issue. Here is my proposal:
I found that search results are generated in ChatSwitcherView.updateSearch() function. I’m planning to modify the following for loop.
https://github.com/Expensify/Expensify.cash/blob/c0069cf6e2df94ba7c3a2c242cf9e6a9c82ddd30/src/pages/home/sidebar/ChatSwitcherView.js#L424-L451
I’m going to split search string on spaces and create an array of words.
isMatch condition should be changed such that our regex matches should work for all words from search string.
https://github.com/Expensify/Expensify.cash/blob/c0069cf6e2df94ba7c3a2c242cf9e6a9c82ddd30/src/pages/home/sidebar/ChatSwitcherView.js#L429
I have a question for ordering results. I see there is an existing ranking that ranks exact matches higher. Do you want me to preserve this ranking or should we order all matches by most recent message time? To implement this, I’m going to sort all search options  by most recent message time that is not available in this function. I need to pass that value somehow.

@tugbadogan Thanks! Please apply for the job directly through Upwork.
Also a note, we're waiting for other UI changes before we can hire for this job.

Hi @NicMendonca,
I've already apply through Upwork. My Upwork name is Fadime Tugba Oge.

Also a note, we're waiting for other UI changes before we can hire for this job.

No problem, thanks for letting me know. I'm happy to work on this issue later.

@tugbadogan as mentioned last week we did make some UI changes so you might want to give your initial proposal a second look.
Thanks!

Hi @NicMendonca, I created a pull request on top of the most recent UI changes. I fixed this issue and removed redundant regex patterns from the code.


LINKED LIST IMPLEMENTATION IN C++

Feature
Solutions of all operations in linked list:
adding node from front ,adding node from tail, deleting the nodes.
Language: C++
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
I want to contribute to it under GSSoC'21.
Pitch:
I would like to take up this task to implement it in C++. @bhav09

/assign


[BUG] after upgrade to 4.44.9 optionLabel in useSelect not working

Describe the bug
After upgrade to 4.44.9 the optionLabel in useSelect always return the default value which is title and after change it to another value it refused and it always return title and when title is not available is return the value which is the ID
Steps To Reproduce
Upgrade the refine core to 4.44.9
using userSelect
add option optionLabel
const { selectProps: accomodationSelectProps } = useSelect({
    resource: "accomodation",
    optionLabel: "name",
  });

Expected behavior
Returrn optionLabel: "name", as per the endpoint
Screenshot
No response
Desktop
No response
Mobile
No response
Additional Context
No response

I'm using the useSelect to get some data from a resource using the below const to load the accommodation name from accommodation resource in version 4.44.7 this was working fine without any issue after upgrade to 4.44.9 this const doesn't work and it always return ID.
const { selectProps: accomodationSelectProps } = useSelect({
    resource: "accomodation",
    optionLabel: "name",
  });

I have attached the resource response to be able to check it.

When I checked the release note I found that you changed the optionLabel attribute default value from name to title and the when I try to set it back to name it don't work

Thanks for the details @buildizer, we'll fix it soon.


Unique

https://github.com/SciRuby/daru/issues/419

Requires https://github.com/SciRuby/daru/pull/420 to be merged first as the tuple sorting fix is needed but shouldn't form part of this PR.

@zverok anything left on this?


add new versions and fix certificates

Issue
Currently, the ca-certificates package is added to the rock, but it's missing the default certificates in /etc/ssl/certs.
This happens not because we don't stage them, but because stage-packages: [ca-certificates] doesn't run the maintainer scripts that would populate /etc/ssl/certs, so that folder stays empty.
Solution
The solution to this is to change stage-packages: to overlay-packages in the ca-certs part, because that also runs the maintainer scripts and correctly populates the /ets/ssl/certs folder.
Testing Instructions
You can test it yourself by simply running the rock and checking the certs are there via ls /etc/ssl/certs.
root@8f0199aebc08:/# which update-ca-certificates
/usr/sbin/update-ca-certificates
root@8f0199aebc08:/# ll /etc/ssl/certs/
total 604

(CI is failing cause it's not expecting so many changes and tries to build all rocks, which crashes the runner)

For a separate PR, any idea how we could put a test on this:

root@8f0199aebc08:/# which update-ca-certificates
/usr/sbin/update-ca-certificates
root@8f0199aebc08:/# ll /etc/ssl/certs/
total 604

I guess that would require running the rock via docker, or possibly using something like dive, though I've never tried it


[cluster-test] start to implement client compat test

Motivation
This PR adds the main functionality for client_compatibility_test, which we can use in conjunction with the existing compatibility_test (blockchain-level compatibility). For now, client compat test uses faucet and CLI to test mint, query balance, and transfer.
The main steps are:

Pick two fullnodes, one for running faucet (test_host), and one for running CLI (test_node)
Spawn faucet job, and wait for it to get healthy
Construct CLI initialization configs from the faucet and local fullnode URLs
Construct CLI input commands from file
Run CLI job with provided commands as blocking

This test requires stringing together long commands to be used by each Kubernetes Job, hence all the logic to build those strings separately and concat them together. Also, in attempt to get the CLI access to the waypoint, we run config-builder in the CLI job as well. (At some point, we will probably want to enable vault LSR and use the genesis/operational tools by default.) We reuse the same config seed, so we're guaranteed to get the same waypoint.
A few bonuses:

Adds error report for single experiments (ClusterTestRunner::run_and_report), regardless of success or failure. This is similar to what ClusterTestRunner::run_suite does, appending errors to report text.
Adds Instance::cmd, alongside the existing Instance::util_cmd, which can use a specific docker image and tag. Both Faucet and CLI jobs run the libra_faucet image, at a configurable image tag. Faucet is a long-running job, so we can use the newly created Instance::spawn_job.

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
cti output:
▶ ./scripts/cti --tag dev_rustielin_pull_5467 -E RUST_LOG=debug --report report.json --enable-lsr false --run client_compatibility_test -- --old-image-tag master_3164bff > client_compat.txt
...
INFO 2020-08-08 00:04:26 testsuite/cluster-test/src/main.rs:626 Starting experiment Client compatibility test master_3164bff, faucet fn-6-0(<IP_ADDRESS>), CLI on fn-23-0(<IP_ADDRESS>)
INFO 2020-08-08 00:04:26 testsuite/cluster-test/src/experiments/client_compatibility_test.rs:82 1. Starting faucet on node fn-6-0(<IP_ADDRESS>)
DEBUG 2020-08-08 00:04:26 testsuite/cluster-test/src/cluster_swarm/cluster_swarm_kube.rs:471 Starting job run-faucet for node ip-192-168-222-143.us-west-2.compute.internal
INFO 2020-08-08 00:04:26 testsuite/cluster-test/src/experiments/client_compatibility_test.rs:88 Job run-faucet-66eoysep5b started for node fn-6-0(<IP_ADDRESS>):fn-6-0 faucet command: /opt/libra/bin/config-builder faucet -o /opt/libra/etc --chain-id TESTING -s<PHONE_NUMBER>371337133713371337133713371337133713371337133713371337 -n 30; echo $?; cat /opt/libra/etc/waypoint.txt; CFG_CHAIN_ID=TESTING AC_HOST=<IP_ADDRESS> AC_PORT=8080 gunicorn --bind <IP_ADDRESS>:9999 --access-logfile - --error-logfile - --log-level debug --pythonpath /opt/libra/bin server
INFO 2020-08-08 00:04:26 testsuite/cluster-test/src/experiments/client_compatibility_test.rs:97 Waiting for faucet job to spin up completely
INFO 2020-08-08 00:04:46 testsuite/cluster-test/src/experiments/client_compatibility_test.rs:114 2. Running CLI mint from node fn-23-0(<IP_ADDRESS>)
INFO 2020-08-08 00:04:46 testsuite/cluster-test/src/experiments/client_compatibility_test.rs:116 Job starting for node fn-23-0(<IP_ADDRESS>):fn-23-0 CLI command: /opt/libra/bin/config-builder faucet -o /opt/libra/etc --chain-id TESTING -s<PHONE_NUMBER>371337133713371337133713371337133713371337133713371337 -n 30; echo $?; cat /opt/libra/etc/waypoint.txt; echo a c >> /opt/libra/etc/cmds.txt;echo a mb 0 10 LBR false >> /opt/libra/etc/cmds.txt;echo q b 0 >> /opt/libra/etc/cmds.txt;echo a c >> /opt/libra/etc/cmds.txt;echo a mb 1 11 LBR false >> /opt/libra/etc/cmds.txt;echo q b 1 >> /opt/libra/etc/cmds.txt;echo t 0 1 1 LBR >> /opt/libra/etc/cmds.txt;echo q b 0 >> /opt/libra/etc/cmds.txt;echo q b 1 >> /opt/libra/etc/cmds.txt;echo quit >> /opt/libra/etc/cmds.txt; /opt/libra/bin/cli --url http://<IP_ADDRESS>:8080/v1 --chain-id TESTING -f http://<IP_ADDRESS>:9999 --waypoint $(cat /opt/libra/etc/waypoint.txt) < /opt/libra/etc/cmds.txt && echo SUCCESS
DEBUG 2020-08-08 00:04:46 testsuite/cluster-test/src/cluster_swarm/cluster_swarm_kube.rs:486 Running job run-cli-commands for node ip-192-168-146-109.us-west-2.compute.internal
DEBUG 2020-08-08 00:04:46 common/retrier/src/lib.rs:43 job in still in progress run-cli-commands-grhtql8yur. Retrying in 5 seconds..
DEBUG 2020-08-08 00:04:51 common/retrier/src/lib.rs:43 job in still in progress run-cli-commands-grhtql8yur. Retrying in 5 seconds..
DEBUG 2020-08-08 00:04:56 common/retrier/src/lib.rs:43 job in still in progress run-cli-commands-grhtql8yur. Retrying in 5 seconds..
DEBUG 2020-08-08 00:05:01 common/retrier/src/lib.rs:43 job in still in progress run-cli-commands-grhtql8yur. Retrying in 5 seconds..
INFO 2020-08-08 00:05:06 testsuite/cluster-test/src/experiments/client_compatibility_test.rs:129 3. CLI success from all nodes
Deleting Job: Some(JobStatus { active: Some(1), completion_time: None, conditions: None, failed: None, start_time: Some(Time(2020-08-08T00:04:26Z)), succeeded: None })
DEBUG 2020-08-08 00:05:06 common/retrier/src/lib.rs:43 job in still in progress run-faucet-66eoysep5b. Retrying in 5 seconds..
INFO 2020-08-08 00:05:11 testsuite/cluster-test/src/cluster_swarm/cluster_swarm_kube.rs:281 Job run-faucet-66eoysep5b has been killed already
INFO 2020-08-08 00:05:11 testsuite/cluster-test/src/cluster_swarm/cluster_swarm_kube.rs:306 Killing job run-faucet-66eoysep5b returned job_status.success
INFO 2020-08-08 00:05:11 testsuite/cluster-test/src/main.rs:640 Experiment finished, waiting until all affected validators recover

Generated report:
▶ cat report.json | jq -r .text
Client compatibility test results for master_3164bff ==> dev_rustielin_pull_5467 (PR)
1. Starting faucet on node fn-6-0(<IP_ADDRESS>)
2. Running CLI mint from node fn-23-0(<IP_ADDRESS>)
3. CLI success from all nodes

I also ran a test that manually induced a failure in one of the jobs (see https://github.com/libra/libra/pull/5530). This results in report text like:
▶ cat report_fail3.json | jq -r .text
Client compatibility test results for master_3164bff ==> dev_rustielin_pull_5530 (PR)
1. Starting faucet on node fn-24-0(<IP_ADDRESS>)
2. Running CLI mint from node fn-29-0(<IP_ADDRESS>)
Experiment `Client compatibility test master_3164bff, faucet fn-24-0(<IP_ADDRESS>), CLI on fn-29-0(<IP_ADDRESS>)` failed: `Failed to run experiment: one of the jobs failed`

NOTE: One downside to using jobs like we are here is that we can't really gain insight into the actual execution of each job since they don't forward their logs. Our only signal is (1) being able to successfully start the jobs (2) the job exit status. For example, if the CLI commands fail, we don't know if it's because of the faucet server or the actual CLI.
For now, to verify that they're actually working as intended besides relying on job exit status solely, we can manually use kubectl to tail the logs of the jobs after they've spun up.
CLI Job
Commands are piped in, so the output isn't too pretty, but we can see that the mint and transfers result in the right balances:
▶ kubectl logs -f run-cli-commands-lcwotmtopg-n464c
...
Please, input commands:

>> Creating/retrieving next local account from wallet
Created/retrieved local account #0 address f8227ff87655fcc52a965acc0c43b74a
>> Sending coins from faucet
waiting for<PHONE_NUMBER>00000000000000000000dd with sequence number 1
........
transaction executed!
Finished sending coins from faucet!
Balance is: 10.000000LBR
>> Creating/retrieving next local account from wallet
Created/retrieved local account #1 address 51f3248cf34df80f6441e34b3b23de07
>> Sending coins from faucet
waiting for<PHONE_NUMBER>00000000000000000000dd with sequence number 2
..
transaction executed!
Finished sending coins from faucet!
Balance is: 11.000000LBR
>> Transferring
Transaction submitted to validator
To query for transaction status, run: query txn_acc_seq 0 0 <fetch_events=true|false>
Balance is: 10.000000LBR
Balance is: 11.000000LBR
SUCCESS

Faucet Job
We can see that the server spins up properly, is able to connect to a fullnode's AC, and is giving HTTP 200 for each POST.
▶ kubectl logs -f run-faucet-u4hu9js0nk-qcp5z
...
[2020-08-08 00:04:44 +0000] [11371] [INFO] Starting gunicorn 20.0.4
[2020-08-08 00:04:44 +0000] [11371] [DEBUG] Arbiter booted
[2020-08-08 00:04:44 +0000] [11371] [INFO] Listening at: http://<IP_ADDRESS>:9999 (11371)
[2020-08-08 00:04:44 +0000] [11371] [INFO] Using worker: sync
[2020-08-08 00:04:44 +0000] [11374] [INFO] Booting worker with pid: 11374
[2020-08-08 00:04:44 +0000] [11371] [DEBUG] 1 workers
[2020-08-08 00:04:59 +0000] [11374] [DEBUG] POST /
0:c459399ec2219a8d2c4b1f1dacc942f6f2ddf4ab8cfb5f02237f8dd20a8854a63.7.3 (default, Jul 25 2020, 13:03:44)
[GCC 8.3.0] 3.7.3
Connecting to ac on: http://<IP_ADDRESS>:8080
<IP_ADDRESS> - - [08/Aug/2020:00:05:00 +0000] "POST /?amount=10000000&auth_key=d136a48798d6519137671e7c712b1787f8227ff87655fcc52a965acc0c43b74a&currency_code=LBR HTTP/1.1" 200 1 "-" "-"
[2020-08-08 00:05:00 +0000] [11374] [DEBUG] POST /
Connecting to ac on: http://<IP_ADDRESS>:8080
<IP_ADDRESS> - - [08/Aug/2020:00:05:01 +0000] "POST /?amount=11000000&auth_key=71dc33a3436a8514ca7f7b7a2a7466e851f3248cf34df80f6441e34b3b23de07&currency_code=LBR HTTP/1.1" 200 1 "-" "-"

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

/land
Landing this for now, improvements to come. @changyonghu  we will have to sync on waypoint now that we're not using config-builder by default.


Cannot use Versionner if Iceberg is in the image

In a Pharo 6 image I have Iceberg dev-0.4. I wanted to create a configuration using versionner but when I try to add a dependency I get an Error Instance of IceMetacelloRepositoryAdapter did not understand #isCache.
If I implement the method to return false I then get an Error Instance of IceMetacelloRepositoryAdapter did not understand #koRemote.

For now I just reject all IceMetacelloRepositoryAdapter from RemotesManager>>buildRoots.

The #koRemote problem was fixed this week in Pharo base image:  https://pharo.fogbugz.com/f/cases/19738

Sorry that was the #koRemote issue for Pharo 5.0. There is another for Pharo 6.0
https://pharo.fogbugz.com/f/cases/19739 not yet integrated as of now. But you can load the slice and try.

this has been integrated