DV Setup: Charon Integration with Sedge

Changes:
Charon is used by stakers to distribute the responsibility of running Ethereum Validators across a number of different instances and client implementations. Setting up and running a full ethereum node with charon, needs some learning curve and compatibility knowledge, in order for the setup to be fully compliant with the charon configuration requirements for different BN-VC combinations. We want to provide a better and guided user experience for setting up a DV with Charon.
Sedge, is a one-click ethereum node setup tool which focuses on ease of use and, as such, lowers the entry barrier for non-technical users. With Sedge, one can run a node or a validator on Ethereum with little to no technical background.
Integrating Charon with Sedge would make it easy for stakers to setup and run a DV with Charon without having to go through each individual client setup docs and their compatibility with DVT.
Please refer Design Doc here - https://docs.google.com/document/d/1nQsOmkd-od3-lej3OcdUgVZ0GYXAHK9GZqlwEoyIzSY/edit
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Other (please describe):

Testing
Requires testing

[x] Yes
[ ] No

In case you checked yes, did you write tests?

[x] Yes
[ ] No

Comments about testing , should you have some (optional)
Further comments (optional)
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

I was having a problem importing keys.
Charon DKG process outputs a folder which has a subfolder validator_keys inside it.
I saved the folder in the root.
And then ran the commands -
sedge generate full-node --validator=lodestar --network=holesky --distributed
sudo sedge import-key --from node0/validator_keys -n holesky lodestar
But i got the below error -
2024-04-05 13:57:51 -- [INFO] [Logger Init] Log level: info 2024-04-05 13:57:51 -- [WARN] A new Version of sedge is available. Please update to the latest Version. See https://github.com/NethermindEth/sedge/releases for more information. Latest detected tag: v0.0.0 2024-04-05 13:57:52 -- [INFO] Setting up containers 2024-04-05 13:57:52 -- [INFO] Running command: docker compose -f /Users/sg/obol/nethermind/sedge/sedge-data/docker-compose.yml build validator 2024-04-05 13:57:52 -- [INFO] Running command: docker compose -f /Users/sg/obol/nethermind/sedge/sedge-data/docker-compose.yml pull validator [+] Pulling 0/0  ⠋ validator Pulling                                                0.1s  [+] Pulling 0/17:52 must use ASL logging (which requires CGO) if running   ⠙ validator Pulling                                                0.2s  error getting credentials - err: exit status 1, out: `` 2024-04-05 13:57:52 -- [FATA] exit status 1
node0.zip

Hi @sugh01. The issue is related to the use of sudo with the sedge import-key command. I recreated the scenario locally (without sudo) and attempted to import the keys from the provided node0 directory, which resulted in the following error:
$ sedge import-key --from node0/validator_keys -n holesky lodestar
2024-05-16 12:40:34 -- [INFO] [Logger Init] Log level: info
2024-05-16 12:40:34 -- [INFO] You are running the latest version of sedge. Version:  v1.3.2
2024-05-16 12:40:35 -- [INFO] Setting up containers
2024-05-16 12:40:35 -- [INFO] Running command: docker compose -f /Users/adrian/nethermind/github.com/NethermindEth/sedge/sedge-data/docker-compose.yml build validator
2024-05-16 12:40:35 -- [INFO] Running command: docker compose -f /Users/adrian/nethermind/github.com/NethermindEth/sedge/sedge-data/docker-compose.yml pull validator
[+] Pulling 1/1
 ✔ validator Pulled                                                                                1.3s
2024-05-16 12:40:36 -- [INFO] Running command: docker compose -f /Users/adrian/nethermind/github.com/NethermindEth/sedge/sedge-data/docker-compose.yml create validator
[+] Creating 2/0
 ✔ Container sedge-validator-blocker  Created                                                                 0.0s
 ✔ Container sedge-validator-client   Created                                                                 0.0s
2024-05-16 12:40:36 -- [WARN] The keys path is not the default one, copying the keys to the default path /Users/adrian/nethermind/github.com/NethermindEth/sedge/sedge-data/keystore
2024-05-16 12:40:36 -- [INFO] Importing validator keys
2024-05-16 12:40:36 -- [INFO] The keys import container is starting
2024-05-16 12:40:38 -- [FATA] validator import container exited with non-zero exit code: validator-import service container with id 85b3e4a24962a0923f93754a8855c0575d768f7a75bb4191718ba926b8cbafc8 ends with status code 1. Here are the logs for more details:
 ✖ Error: ENOENT: no such file or directory, open '/keystore/keystore_password.txt'
    at Object.readFileSync (node:fs:453:20)
    at readPassphraseFile (file:///usr/app/packages/cli/src/util/passphrase.ts:9:19)
    at readPassphraseOrPrompt (file:///usr/app/packages/cli/src/cmds/validator/signers/importExternalKeystores.ts:30:12)
    at Object.handler (file:///usr/app/packages/cli/src/cmds/validator/import.ts:61:23)
    at file:///usr/app/node_modules/yargs/build/lib/command.js:206:54
    at maybeAsyncResult (file:///usr/app/node_modules/yargs/build/lib/utils/maybe-async-result.js:9:15)
    at CommandInstance.handleValidationAndGetResult (file:///usr/app/node_modules/yargs/build/lib/command.js:205:25)
    at CommandInstance.applyMiddlewareAndGetResult (file:///usr/app/node_modules/yargs/build/lib/command.js:245:20)
    at CommandInstance.runCommand (file:///usr/app/node_modules/yargs/build/lib/command.js:128:20)
    at YargsInstance.[runYargsParserAndExecuteCommands] (file:///usr/app/node_modules/yargs/build/lib/yargs-factory.js:1386:105)

To import the keys correctly, provide the keystore password in the keystore_password.txt file.
Example of successfully import
This is a keystore directory keystore.zip, generated with sedge keys command, which will be used for the imprt-key in this example. This is the structure of the keystore directory:
$ tree keystore
keystore
├── deposit_data.json
├── keystore_password.txt
└── validator_keys
    └── keystore-m_12381_3600_0_0_0.json

2 directories, 3 files

sedge generate full-node --validator=lodestar --network=holesky --distributed. This command generates the following files in the sedge-data directory:

$ tree sedge-data
sedge-data
├── docker-compose.yml
└── jwtsecret

1 directory, 2 files

sedge import-key --from keystore -n holesky lodestar This command produces these logs:

sedge import-key --from keystore -n holesky lodestar
2024-05-16 12:59:10 -- [INFO] [Logger Init] Log level: info
2024-05-16 12:59:10 -- [INFO] You are running the latest version of sedge. Version:  v1.3.2
2024-05-16 12:59:10 -- [INFO] Setting up containers
2024-05-16 12:59:10 -- [INFO] Running command: docker compose -f /abs/path/to/sedge-data/docker-compose.yml build validator
2024-05-16 12:59:10 -- [INFO] Running command: docker compose -f /abs/path/to/sedge-data/docker-compose.yml pull validator
[+] Pulling 1/1
 ✔ validator Pulled                                                                                1.4s
2024-05-16 12:59:12 -- [INFO] Running command: docker compose -f /abs/path/to/sedge-data/docker-compose.yml create validator
[+] Creating 2/0
 ✔ Container sedge-validator-blocker  Created                                                                 0.1s
 ✔ Container sedge-validator-client   Created                                                                 0.0s
2024-05-16 12:59:12 -- [WARN] The keys path is not the default one, copying the keys to the default path /abs/path/to/sedge-data/keystore
2024-05-16 12:59:12 -- [INFO] Importing validator keys
2024-05-16 12:59:12 -- [INFO] The keys import container is starting
2024-05-16 12:59:15 -- [INFO] Validator keys imported successfully

And the sedge-data directory is updated with the imported keystore.
$ tree sedge-data
sedge-data
├── docker-compose.yml
├── jwtsecret
├── keystore
│   ├── deposit_data.json
│   ├── keystore_password.txt
│   └── validator_keys
│       └── keystore-m_12381_3600_0_0_0.json
└── validator-data
    ├── keystores
    │   └── 0xb53a59a1a5f59adc0d33686164bb90dcadfabbe3000bc95d3ac738b8269d80acb1bdb081a8f23592b6cd21e00bb86f94
    │       └── voting-keystore.json
    └── secrets
        └── 0xb53a59a1a5f59adc0d33686164bb90dcadfabbe3000bc95d3ac738b8269d80acb1bdb081a8f23592b6cd21e00bb86f94

7 directories, 7 files

It appears that the import process is working fine, but the provided keystore directory structure is not correct

Hi @adriantpaez
While testing the key import process, i ran into an error when trying with Lighthouse.
Steps:

sedge generate full-node --validator=lighthouse --network=holesky
sedge keys

sedge-data ├── docker-compose.yml ├── jwtsecret └── keystore     ├── deposit_data.json     ├── keystore_password.txt     └── validator_keys         └── keystore-m_12381_3600_0_0_0.json

sedge import-key -n holesky lighthouse

This step does not complete.
`2024-06-19 13:38:45 -- [INFO] [Logger Init] Log level: info
2024-06-19 13:38:45 -- [INFO] You are running the latest version of sedge. Version:  v1.3.2
2024-06-19 13:38:45 -- [INFO] Setting up containers
2024-06-19 13:38:45 -- [INFO] Running command: docker compose -f /Users/sg/sedge/sedge/sedge-data/docker-compose.yml build validator
2024-06-19 13:38:45 -- [INFO] Running command: docker compose -f /Users/sg/sedge/sedge/sedge-data/docker-compose.yml pull validator
[+] Pulling 1/1
✔ validator Pulled                                                                                1.3s
2024-06-19 13:38:55 -- [INFO] Running command: docker compose -f /Users/sg/sedge/sedge/sedge-data/docker-compose.yml create validator
[+] Creating 3/0
✔ Network sedge-network              Created                                                                                0.0s
✔ Container sedge-validator-blocker  Created                                                                                0.0s
✔ Container sedge-validator-client   Created                                                                                0.0s
2024-06-19 13:38:55 -- [INFO] Running command: docker build -t sedge/validator-import-lighthouse --build-arg LH_VERSION=sigp/lighthouse:v5.0.0 --build-arg NETWORK=holesky /var/folders/ng/dv8zg6ld6nvdrbqmysj1klxh0000gn/T/sedge-validator-import-context-3819293176
[+] Building 1.0s (11/11) FINISHED                                                                                docker:desktop-linux
=> [internal] load build definition from Dockerfile                                                                                0.0s
=> => transferring dockerfile: 529B                                                                                0.0s
=> [internal] load metadata for docker.io/library/debian:stable-20221004-slim                                                                         0.9s
=> [internal] load .dockerignore                                                                                0.0s
=> => transferring context: 2B                                                                                0.0s
=> [1/7] FROM docker.io/library/debian:stable-20221004-slim@sha256:92ed72016796475ea1f18f84cd8e2f8519ece3a9ea27fdde1157464078ea5371                   0.0s
=> [internal] load build context                                                                                0.0s
=> => transferring context: 677B                                                                                0.0s
=> CACHED [2/7] RUN apt-get update && apt-get install -y curl                                                                                0.0s
=> CACHED [3/7] RUN version=$(echo sigp/lighthouse:v5.0.0 | cut -d':' -f 2) && curl -L https://github.com/sigp/lighthouse/releases/download/$version  0.0s
=> CACHED [4/7] RUN tar -xvf lh.gz                                                                                0.0s
=> CACHED [5/7] COPY validator-init.sh .                                                                                0.0s
=> CACHED [6/7] RUN chmod +x validator-init.sh                                                                                0.0s
=> exporting to image                                                                                0.0s
=> => exporting layers                                                                                0.0s
=> => writing image sha256:68726c147b82af43d6a88a143b1d5560d3f67fee8e14f14950824c8a965c22c8                                                           0.0s
=> => naming to docker.io/sedge/validator-import-lighthouse                                                                                0.0s
View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/yknf6rtsfipgqfwzfzjngzr8d
What's next:
View a summary of image vulnerabilities and recommendations → docker scout quickview
2024-06-19 13:38:56 -- [INFO] Importing validator keys
2024-06-19 13:38:56 -- [INFO] The keys import container is starting
2024-06-19 13:38:57 -- [FATA] validator import container exited with non-zero exit code: validator-import service container with id 67c460dfabc79a3402901c19e6dbfb08572829c58bf3156ad84e20744699df8a ends with status code 255. Here are the logs for more details:
Found validator key in /keystore/validator_keys/keystore-m_12381_3600_0_0_0.json
Importing validator...
qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory`
The same steps run successful for Teku, Lodestar and Prysm.
Do i need to preform some additional steps for Lighthouse?

Codecov Report
Attention: Patch coverage is 48.86878% with 113 lines in your changes missing coverage. Please review.

Project coverage is 75.39%. Comparing base (5231116) to head (d64d6f2).
Report is 2 commits behind head on develop.

Files
Patch %
Lines

cli/actions/importKeys.go
8.04%
76 Missing and 4 partials :warning:

internal/images/validator-import/prysm/prysm.go
0.00%
11 Missing :warning:

internal/pkg/generate/generate_scripts.go
85.71%
6 Missing and 2 partials :warning:

cli/generate.go
89.13%
4 Missing and 1 partial :warning:

internal/pkg/generate/types.go
0.00%
5 Missing :warning:

cli/sub_gen.go
33.33%
1 Missing and 1 partial :warning:

internal/pkg/clients/types.go
75.00%
2 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #368      +/-   ##
===========================================
- Coverage    76.93%   75.39%   -1.55%
===========================================
  Files           86       87       +1
  Lines         4809     4963     +154
===========================================
+ Hits          3700     3742      +42
- Misses        1015     1120     +105
- Partials        94      101       +7

Flag
Coverage Δ

unittests
75.39% <48.86%> (-1.55%)
:arrow_down:

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

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

We found one error while running:
make compile
sudo cp build/sedge /usr/local/bin/
sedge generate full-node --validator=lodestar --network=holesky --distributed
sedge import-key --from keystore --distributed -n holesky lodestar

and this is the error message
on Windows:
2024-11-07 00:27:19 -- [INFO] Copying the keys from D:\Desktop\nethermind\projects\sedge\sedge\keystore
2024-11-07 00:27:19 -- [INFO] Copying Charon contents to the default path D:\Desktop\nethermind\projects\sedge\sedge\sedge-data\.charon charon                                                                                fied.
2024-11-07 00:27:19 -- [FATA] CreateFile D:\Desktop\nethermind\projects\sedge\sedge\keystore: The system cannot find the file specicified.

on WSL:
2024-11-07 00:30:58 -- [INFO] Copying the keys from /mnt/d/Desktop/nethermind/projects/sedge/sedge/keystore
2024-11-07 00:30:58 -- [INFO] Copying Charon contents to the default path /mnt/d/Desktop/nethermind/projects/sedge/sedge/sedge-data/.charon
2024-11-07 00:30:58 -- [FATA] lstat /mnt/d/Desktop/nethermind/projects/sedge/sedge/keystore: no such file or directory


Does the sdk supports Kinect v1 ????

Hi,
Can this sdk work with Kinect v1 ???
If no, can u please tell me any possibility with the source code to make it work with Kinect v1.
Thanks
Krishna

Hi, no unfortunately it does not. However, changing the app to other sensors (like the Kinect v1) should be quite easy. All you need to reimplement is the iCapture interface in the LiveScanClient.
Marek


T1

T1 submission

pending:T1
account1:4cCxxr93LQZFfoDe1wpNXv2eCmLqzASp3XTkQht63XtZDV53kL
account2:4YWNqHwwDmtezg8baT4eYVy5251q1NqwfAk79QWuGQLoHeUXvx
DeviceDetails:verified
Screenshot:missing
We cannot fully verify this submission. Please provide us with screenshots with all transactions.
@iyulish

pending:T1
account1:4cCxxr93LQZFfoDe1wpNXv2eCmLqzASp3XTkQht63XtZDV53kL
account2:4YWNqHwwDmtezg8baT4eYVy5251q1NqwfAk79QWuGQLoHeUXvx
DeviceDetails:verified
Screenshot:missing
We cannot fully verify this submission. Please provide us with screenshots with all transactions.
@iyulish

confirmed:T1
account1:4cCxxr93LQZFfoDe1wpNXv2eCmLqzASp3XTkQht63XtZDV53kL
account2:4YWNqHwwDmtezg8baT4eYVy5251q1NqwfAk79QWuGQLoHeUXvx
DeviceDetails:verified

confirmed:T1
account1:4cCxxr93LQZFfoDe1wpNXv2eCmLqzASp3XTkQht63XtZDV53kL
account2:4YWNqHwwDmtezg8baT4eYVy5251q1NqwfAk79QWuGQLoHeUXvx
DeviceDetails:verified


Rename configv1 to legacyconfigv1

The main reason for renaming the package identifier is to avoid future confusion when importing the config/v1.

Yikes! Finally!


Double loop compilation error

fn double_loop() {
    let mut i = 0;
    while i < 10 {
        let mut j = 0;
        while j < 10 {
            j += 1;
        }
        i += 1;
    }
}

The function above fails to compile (using charon + aeneas) with error (including also the commands for compilation)
charon --opaque=main --dest=./test/lean --crate test
aeneas test.llbc -backend lean
[Info ] Imported: test.llbc
Uncaught exception:

  "Assert_failure PrePasses.ml:217:10"

Raised at Aeneas__PrePasses.remove_loop_breaks.replace_breaks_with.object#visit_Loop in file "PrePasses.ml", line 217, characters 10-35
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.pp_statement.__1 in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.pp_statement.__1 in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.pp_statement.__1 in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.pp_statement.__1 in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.pp_statement.__1 in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.pp_statement.__1 in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.pp_statement.__1 in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.map_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Aeneas__PrePasses.remove_loop_breaks.object#visit_Sequence in file "PrePasses.ml", line 237, characters 12-41
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.pp_statement.__1 in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.pp_statement.__1 in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Charon__LlbcAst.iter_statement#visit_Loop in file "src/LlbcAst.ml", line 7, characters 0-1023
Called from Aeneas__PrePasses.remove_loop_breaks in file "PrePasses.ml", line 245, characters 43-75
Called from Stdlib__Map.Make.map in file "map.ml", line 304, characters 19-22
Called from Stdlib__Map.Make.map in file "map.ml", line 305, characters 19-26
Called from Stdlib__Map.Make.map in file "map.ml", line 303, characters 19-26
Called from Stdlib__Map.Make.map in file "map.ml", line 303, characters 19-26
Called from Stdlib__Map.Make.map in file "map.ml", line 305, characters 19-26
Called from Stdlib__List.fold_left in file "list.ml", line 121, characters 24-34
Called from Aeneas__PrePasses.apply_passes in file "PrePasses.ml", line 425, characters 4-96
Called from Dune__exe__Main in file "Main.ml", line 271, characters 14-45
make[1]: *** [aeneas] Error 2
make: *** [test] Error 2

Yes, nested loops are not supported for now. We intend to have this support soon, though.


Format of test.tfrecords

Should test.tfrecords be in the same format as train.tfrecords and validation.tfrecords? I was able to generate train and validation for a new data set and successfully train a model. However, when trying test.py, I have been getting reshaping errors like this one: ValueError: cannot reshape array of size 195453 into shape (381,795). Should test.tfrecords be created differently?

I modified it so that the maximum image dimension is no more than 500 and it is working now.


Able to submit disabled field value in redux form

Able to submit disabled field value in redux form
I am using redux form with the version of 8.3.0
facing one issue with disable field in the form
<Field
        name="firstName"
        component="input"
        type="text"
        disabled={myBoolean}
        placeholder="First Name"
      />

set to disable property to a particular field, it's working as expected.but open the developers tool in the chrome & remove the disable property  from the element by manually and then edit the field in UI, the edited data still getting saved.
for my use case, need to save data only user can able to edit.
Any pointers on this?
And also provide some pointers, is there any possibilities to disable entire form based on condition?
Thank you

Well you can't deny a user from the front-end as the client will always be able to remove html. You need to set-up authentication on server side to avoid unauthorized modification.


add 'login to connect' button

When you click a direct linkt to a need and you're not logged in, show a 'login to connect' button

we do not "demand" a login to connect any more as we offer "anonymous" need creation


[bug]  Setuptools is replacing distutils - Warning message

Describe the bug
F:\ComfyUI\ComfyUI_windows_portable\python_embeded\lib\site-packages_distutils_hack_init_.py:33: UserWarning: Setuptools is replacing distutils.
warnings.warn("Setuptools is replacing distutils.")
Reproduction
warning message occurs on startup of comfyui
Expected behavior
may not be a bug, could be working as intended
Operating System
Windows (Default)
Comfy Mode
Comfy Portable (embed) (Default)
Console output
No response
Additional context
No response

Thanks, yep this can be safely ignored


Update streaming operators after fixes in Surelog

Small changes after https://github.com/alainmarcel/Surelog/issues/1067

OpenTitan synth failed, probably because of new Surelog. Checking.


Synced state [in progress]

npm install && npm run watch-clerk

Then in a different terminal, connect and run (start!) in dev/user.clj

Closing, since #12 now covers this upgrade.


Ability to define whether or not links opened in new tabs become focussed

I think this means being able to set the selected value  https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/create when creating the tab here https://github.com/david-tejada/rango/blob/b90edaa346db93cf29423ef91b28450e6aa0e39d/src/background/tabs-messaging.ts#L90 as it defaults to true.
I am unsure what to suggest for the Talon command, and whether or not it should share the existing blank ... command with an extra qualifier or if it should get a new one. I think I'm leaning towards a new word, some for consideration:
stash air
load air
set air
store air
pack air

Trying to think of words which invoke imagery of stashing something away for later use as is common with opening links in new tabs

I already had this in mind. I like stash. I think I'll implement this one and #25 all at once

I implemented this. The command is stash and takes one or more hints and opens them in a new tab without activating it. Will be in v0.2.0 that I'll publish next week.


Teams fx migration samples

@Harikrishnan-MSFT - Run build pipeline before merging this PR.

Build Pipeline -
https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/5875107651


Yarn: Module not found: Can't resolve '@ethersphere/bee-js'

Made a clean create-react-app.
Added bee-js with yarn add
Added import in App.js
Yarn start: Can't resolve '@ethersphere/bee-js'

Do you have a source code to share? Can you send exactly the commands you used?

Just tried and it works. Which version of yarn and nodejs are you using? https://github.com/vojtechsimetka/cra-yarn-bee-js.
Tested with:
yarn 1.22.10
nodejs v14.15.4

Steps:
npx create-react-app yarn-test

cd yarn-test

yarn add @ethersphere/bee-js --save

Imported and instantiated in src/App.js
https://github.com/vojtechsimetka/cra-yarn-bee-js/commit/9217200e36585e966105bc953cbe04e150017733#diff-3d74dddefb6e35fbffe3c76ec0712d5c416352d9449e2fcc8210a9dee57dff67R1-R9

I'm trying with "@ethersphere/bee-js": "github:ethersphere/bee-js#release-v0.5.1",

This might be the reason: https://github.com/yarnpkg/yarn/issues/5235#issuecomment-571206092

Ah yeah that is probably it. After reading the comments this seems to be a workaround for yarn v1.x but is fixed in v2.x and will NOT be backported to v1.x.
So the decision is - do we want to pollute even more our root folder with specific fix for older versions of yarn? Or de we just document that those who want to install from github should use either npm or yarn v2.x? I prefer the second.

So the decision is - do we want to pollute even more our root folder with specific fix for older versions of yarn? Or de we just document that those who want to install from github should use either npm v6.x or yarn v2.x or newer? I prefer the second.

I vote for the second: document and use v2.x or newer.

Hmm, I am not so sure about "dropping support for yarn 1" because of this rather edge case. I was bit reading up on Yarn 2 and it seems that it is not that much widely accepted by the community as it introduced a new way of dependency management that apparently broke some things.
Maybe only a note about this to Install section of Readme?


Add FoundationPreview 6.2 as an allowed availability annotation

Now that we've branched for release/6.1, changes targeting main will need to be annotated via a new 6.2-aligned availability. This PR adds FoundationPreview 6.2 as an allowed availability annotation so that future API work can use this to properly mark availability on platforms where Foundation ships as part of an SDK.

@swift-ci please test


Upgrade Typeorm

Acceptance Criteria

[ ] Upgrade Typeorm to the latest version.

Additional Context

at least Version 0.30 (https://github.com/typeorm/typeorm/releases/tag/0.3.0) (0.3.6 stable version - https://www.npmjs.com/package/typeorm) introduced new nice features and some breaching changes that will require some refactoring. Some of the new features allow us to create queries using less strings, building the queries in a more type-safe way, like the below one:

block until nestjs/typeorm version 9 release

<EMAIL_ADDRESS>


View moved to panel is awkwardly sized and in a new window changes size

Testing https://github.com/microsoft/vscode/issues/96318
The left screen is what I started with. I moved a Gitlens view into search. It ended up being very narrow. Then I opened a new window on the right. In that one, the search and file history are now equally sized.

some work was done for another issue, we don't a clean have a way to ensure the sizes are equal, but we do better in most cases now.


✨ Improve mcss terminal output

Description

Definition file not found
ℹ `master.css.{ts,js,mjs,cjs}` definition file  not found

🎉 Released in https://github.com/master-co/css/releases/tag/v2.0.0-beta.113


Update generated protocol buffer files

Don't suppose these can be autogenerated?

Not really. Bazel can't write to the source directory. But I'm planning to add tests that will fail if we forget to update them (cf. https://github.com/google/kythe/pull/55).


[6.0] Add FoundationNetworking hook for reading contents of remote URL

Explanation: Adds a hook point for FoundationNetworking to allow Data(contentsOf:) to perform a remote URL request to fetch data
Scope: Should only impact calling Data(contentsOf:) with a non-file URL, turning an error into non-regressed behavior (but is inert without the matching SCL-F change)
Original PR: https://github.com/apple/swift-foundation/pull/820
Risk: Minimal - fixes a regression where the current behavior is just to throw, and fairly limited scope
Testing: Testing done via swift-ci testing and local testing
Reviewer: @iCharlesHu

@swift-ci please test


Add a method to reload default key binds

Sometimes players get into trouble after they mess up their key binds.
It would be great if there was a button to reset them to default somehow.

Thank you for the great suggestion. I implemented a reset button, that overwrites the current key binding with the default on, set in the editor.


Instructions for each labeling task / project

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Currently we have to prepare and distribute documentation for each project and task outside CVAT which is slow and error prone process.
In AWS's Sage Maker we can give instructions per labeling task for annotators.
I believe this feature will improve productivity of annotation team and decrease error rate.
Possible Solution
Side panel with instructions for created task (text + images).

Hi, @Ursanon
You can use field "Issue tracker" to left a link with specification (to any 3rdparty server) when create a task or a project.
Your request to support it directly in CVAT is a part of #351, but it is out of priority of the core team.

Hi, @Ursanon
You can use field "Issue tracker" to left a link with specification (to any 3rdparty server) when create a task or a project.
Your request to support it directly in CVAT is a part of #351, but it is out of priority of the core team.

Implemented in https://github.com/opencv/cvat/pull/6191


feat: add CODEOWNERS grammar

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

not sure why the package lock got updated. used<EMAIL_ADDRESS>


lnd.setaddress script "set locale"

Hello,
in version 1.1 I just manually edited the raspiblitz.conf in my hdd folder to change the ip addresses. Sometimes after reboots I had to manually readjust them.
In the config script there is this "lnd.setaddress.sh" and what I understood it will fix raspiblitz.conf manually to an ip-address of my choice.
So far so good. I tried to set the IP and I receive this error message.

I tried to fix it with the help of google, but none of those worked and after reboot I am getting the same issues.
EDIT: node seems to be reachable via custom ip when I check bitnodes, but does not show in 00InfoBlitz.sh and raspiblitz.conf changes back randomly. So to me it seems this is just a "beauty-issue" and it works like intended. Only shows wrong numbers in infoscreen.

I will take a look at this for the next release. After reboot RaspiBlitz should only change the "publiIcIP" entry (that is always the public IP of your router) but not the "lndAddress" value, that will be used instead if available.

Is there any way to manipulate the "publicIP" field with a custom-manual set one?

The value "publicIP" is getting ignored once "lndAddress" is set ... so why manipulate it? Setting "lndAddress" is the way to do that.

Ok, will wait for the next release then.

I tested lnd.setaddress.shand was able to set a fixed domain or IP and it was displayed on the LCD.
Also I dont get that perl warning on my machine.
So I mark this issue as "final testing" and may close this on v1.3 release if there is not more input on this. But feel free to open it up again if the v1.3 still having the issue.


Wrong default-host leads to panic

Setting something like rustup set default-host x64_86-msvc (on Windows) leads to the following error on rustup show or rustup install:
thread 'main' panicked at 'host triple couldn't be converted to partial triple', ../src/libcore\option.rs:700

I think it shouldn't accept an invalid default-host in the first place ...

Also happens with the initial installation, selecting a custom install and passing an "invalid" triple such as "stable-x86_64-pc-windows-gnu" also leads to panic

That wrong default host didnt even let me install rustup correctly.
I had to delete the directory and set it to gnu manually for it to work.

I believe https://github.com/rust-lang/rustup/pull/1578 fixed this; If a similar issue occurs again please open a new ticket.


h5 element accessibility issue

While doing an accessibility test with admonitions, following warning appears on lighthouse

Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies.  Learn more

because of this

tip

According to W3C standard for heading level

documents should not skip levels (for example, from H1 to H3), as converting such documents to other representations is often problematic.

Consider changing h5 to h1 and use css for styling.

Perhaps the heading level could become a configurable option?

I've just discovered this issue as well. I don't think the heading level should be h1, because there should only be one h1 per page. It should probably be either configurable per block. Or if that is not possible, not using a heading at all would probably be best. If only we could make the <h> element happen it would be perfect here.


Participant should be able to request organizer role

A service for the participants is needed to request the organizer role. The request by the participant should be saved in a queue for the administrators. Administrators should be notified. Maybe the easiest via mail, Slack channel or at the end via a push notification in a Admin Mobile App. The administrator should then confirm or reject the user. The organizer role should be assigned via a stored procedure. The requesting participant is notified via mail. When the access was approved a link to the Organizer App has to be included.

Unfortunately the documentation for Consuming the Connectivity Service using HCP HANA MDC trial does not exist. A test with the settings for hana.ondemand.com fails.
Also sending EMail does not work on the HCP Trial HANA MDC. I've tried the mail.xsjs but never received any of the created mails. Even with the return:
messageId<EMAIL_ADDRESS>finalReply: "250 2.0.0 Ok: queued as 4309AE08F "

from the script.

With the setting proxyHost to value proxy-trial as described in the answer to Connecting for XS app to an OnPremise service it is possible to call a http service as documented here. We can try to use sending E-Mail using that description: How to send mail from a productive HANA XS application.

I've tested the mailgun.com service and pushed the sample code to XSauthLevelPoC.

Entity Organizer was created with corresponding jasmine test. Need to do the UI stuff like auto-fill name via HCP account and integration to the request organizer button


Run recursive URL parsing on a Wikipedia page with varying depths

Results on the Wikipedia Main Page:

Depth
URLs crawled
Time taken

1
1
0.8s

2
89
1m 24.6s

3
139
1m 51.6s

4
647
8m 48.4s

5
1543
17m 44.6s

Above was in AUTO mode?

Above was in AUTO mode?

I didn't specify the mode because it doesn't matter for parsing URLs. We read the HTML and convert it to markdown.
However, that does bring up a possible improvement to the implementation: If there is a hyperlink to a PDF, do we want to download that and parse it? We currently don't. If we do, then the parser type becomes relevant. I'll make the changes to support it.

Ah good point. In a headless way, it makes sense for us to be supporting different hyperlinks. We create a ticket for that?

Created: #32


Fix Issue 10706 setops functions need to require SortedRanges

https://issues.dlang.org/show_bug.cgi?id=10706

largestPartialIntersection
largestPartialIntersectionWeighted
multiwayMerge
multiwayUnion
setDifference
setIntersection
setSymmetricDifference

Now all require SortedRanges to be passed, as that is what they expect
implicitly anyway.
A new public symbol isSortedRange was added to std.range.

LGTM, given the possible fixing breakage that this will incur, this needs a changelog.

changelog added

changelog added

Nice idea!

I will do the suggested change, but SortedRange will check for sortedness in debug. So this is still a breaking change.
But from

Assuming for the sake of argument that this should go ahead
it sounds like an opinion has already been formed regarding this PR. If this would be my first PR it would be my last. It's the tone that makes the music.

I'm sorry it came across that way. I think the red X makes the tone seem more negative than intended.

@n8sh I didn't notice the red X until you just mentioned it.
Anyway, what is the way forward with this.

Anyway, what is the way forward with this.

You said you intend to do the suggested change, so when that is done this should be ready to go ahead.

I already added the overloads.

I already added the overloads.

Could you please point me to them.

But I can't mark them as deprecated as phobos will fail to build.

Bummer.

But I can't mark them as deprecated as phobos will fail to build.

Well, all tests that use them need to be marked as deprecated too then.

Ok, I'll mark the tests as deprecated and see what happens.

All tests that rely on the non SortedRange input have been marked deprecated.
I can't mark the non SortedRange version of the functions deprecated as they call each other.
I'm inclined to add a comment saying the will go away at some point in the future.

I can't mark the non SortedRange version of the functions deprecated as they call each other.

Can't each non-SortedRange function just call the SortedRange equivalent?

I hope to wrap sub calls in assumeSorted, by that doesn't work as I would have to reconstruct RangeOfRanges which could be everything.
I think this is as good as it gets right now.

@andralex You've got 3 days to give input on this.

Stuff won't break

If that's true why are there changes inside unittest blocks?

I can't mark the non SortedRange version of the functions deprecated as they call each other.

I think they can all be marked deprecated without a problem except for multiwayMerge. I'll push that change to this PR.

thank you

anything else?

@burner I know this is old, but any chance of applying @andralex 's feedback and then tackle another round of review?

I'll take another look

ping @burner

yeah I know, shame on me. I promise I'll get to it. :disappointed:

@burner sorry for poking you like this, but have you made any progress on this?

@RazvanN7 please don't feel sorry, I have not. But I just opened up the std.algorithm.setup. Thank you for being my naggy feeling in the back of my mind !

@RazvanN7 I actually got it done I think.

@RazvanN7 should we take another look at this.

FWIW: I would prefer if this did not go ahead. We are not really doing this kind of thing with any other invariants and SortedRange is not even able to properly enforce its own invariant due to mutable aliasing. In fact, I would also prefer to have binary search functions in std.algorithm that do not require a sorted range.

FWIW: I would prefer if this did not go ahead. We are not really doing this kind of thing with any other invariants and SortedRange is not even able to properly enforce its own invariant due to mutable aliasing. In fact, I would also prefer to have binary search functions in std.algorithm that do not require a sorted range.

I think that is a terrible argument. This PR makes the usage of the public facing api of phobos less error prone. To not do this because other parts of phobos not do this, yet, or because the already existing and used abstraction SortedRange has some problem, that hardly any user or dev cares about is the wrong approach in my opinion.

In fact, I would also prefer to have binary search functions in std.algorithm that do not require a sorted range.

IIRC all a user needs to do to transform a range known to be sorted into a SortedRange is insert an assumeSorted, which performs a cheap (but surprisingly valuable statistically) test of the range's sortedness.
As long as does not force the library into a memory safety issue, being mindful of breaking sortedness by means of mutable aliasing is user's responsibility. Sortedness of a SortedRange is in many ways opt-in, not a guarantee.

Looking through the existing code, I found an issue with SortedRange. The entire type is parameterized by SortedRangeOptions, but that parameter is only used by the constructor.

Parameterizing the entire type by a constructor parameter is wasteful
Even in the constructor, that parameter can be a simple run-time parameter that costs virtually nothing to test.
In my opinion the log(n) checking (checkRoughly) should be the default or the only option. Doing no checking at all really legitimizes a cast and we already have strict checking with isSorted.

IIRC all a user needs to do to transform a range known to be sorted into a SortedRange is insert an assumeSorted, which performs a cheap (but surprisingly valuable statistically) test of the range's sortedness.

iota(n).assumeSorted. :clown_face:

FWIW: I would prefer if this did not go ahead. We are not really doing this kind of thing with any other invariants and SortedRange is not even able to properly enforce its own invariant due to mutable aliasing. In fact, I would also prefer to have binary search functions in std.algorithm that do not require a sorted range.

I think that is a terrible argument. This PR makes the usage of the public facing api of phobos less error prone. To not do this because other parts of phobos not do this, yet,

The issue is that this way to enforce invariants results in less than great UX.

or because the already existing and used abstraction SortedRange has some problem,

It provides a false sense of security.

that hardly any user or dev cares about

Hardly any user or dev cares for the SortedRange design.

is the wrong approach in my opinion.

What this change does is cause people to roll their own versions of those functions. It's already the case with binary search.

In my opinion the log(n) checking (checkRoughly) should be the default or the only option. Doing no checking at all really legitimizes a cast and we already have strict checking with isSorted.

I would be very surprised to learn that a function with "assume" in its name does any checking at all by default. We don't do any checking for assumeUnique or assumeSafeAppend, for example, and even assumeUTF only enables its checks in debug mode.

For what it is worth. I have not found the assume sorted mechanism ergonomic or useful, ever. Hence since (a) finding out that using it does some calculations wasting time; (b) being forced to use it even more, our team will no longer use the Phobos versions of these functions if this goes through. Perhaps one can add a way of opting out? e.g. add an overload or a flag that doesn't require this.

In my opinion the log(n) checking (checkRoughly) should be the default or the only option. Doing no checking at all really legitimizes a cast and we already have strict checking with isSorted.

I would be very surprised to learn that a function with "assume" in its name does any checking at all by default. We don't do any checking for assumeUnique or assumeSafeAppend, for example, and even assumeUTF only enables its checks in debug mode.

A fair point. There's no meaningful checking we can do in the first two anyway - if we could, probably the story would be different. assumeUTF is a more relevant precedent, so perhaps assumeSorted could limit its checking to debug mode.

For what it is worth. I have not found the assume sorted mechanism ergonomic or useful, ever. Hence since (a) finding out that using it does some calculations wasting time; (b) being forced to use it even more, our team will no longer use the Phobos versions of these functions if this goes through. Perhaps one can add a way of opting out? e.g. add an overload or a flag that doesn't require this.

First it needs to be understood we're looking at like 20 comparisons for one million elements. The utility of those is high. I can't find the paper I looked at back in the day, but perhaps this (and/or its references) may be a good starting point: https://cs-people.bu.edu/sofya/pubs/TestingSortednessEncyclopedia.pdf
I don't see the utility of a rewrite. Would it consist of one-liners that append .assumeSorted at the end of the ranges involved?
In your application, would it be feasible and useful to keep ranges that are known to be sorted as SortedRanges? That would have the same properties as the original range plus the information that it is sorted.

I think I'm missing something but assumeSorted doesn't check as far as I see. The SortedRange ctor only checks on checkRoughly and checkStrictly which is not the case. The default is "assumeSorted" !?

I think I'm missing something but assumeSorted doesn't check as far as I see. The SortedRange ctor only checks on checkRoughly and checkStrictly which is not the case. The default is "assumeSorted" !?

Indeed, and per my previous answer that seems to be a problem (one of several of SortedRange), checkStrictly is useless because it overlaps isSorted; I consider no checking specious, and checkRoughly is the sweet spot.

For what it is worth. I have not found the assume sorted mechanism ergonomic or useful, ever. Hence since (a) finding out that using it does some calculations wasting time; (b) being forced to use it even more, our team will no longer use the Phobos versions of these functions if this goes through. Perhaps one can add a way of opting out? e.g. add an overload or a flag that doesn't require this.

First it needs to be understood we're looking at like 20 comparisons for one million elements. The utility of those is high. I can't find the paper I looked at back in the day, but perhaps this (and/or its references) may be a good starting point: https://cs-people.bu.edu/sofya/pubs/TestingSortednessEncyclopedia.pdf

Fair point, but still not needed (in my opinion) in most cases.  I think that it is probably true that most common case to want to do say a binary search is on an array.

I don't see the utility of a rewrite. Would it consist of one-liners that append .assumeSorted at the end of the ranges involved?

I haven't studied the code carefully but I would expect one could simply copy the phobos code removing the template constraints, so that SortedRange is not needed.

In your application, would it be feasible and useful to keep ranges that are known to be sorted as SortedRanges?
I guess this might be reasonable in some cases, but I do not think Phobos should be forcing users do this.

PR closed as stalled. This can be resurrected for Phobos 3.


Notebook Editor ignores remapped Esc key

Bug: Notebook Editor ignores the remapping of Esc onto caps lock under Ubuntu
Steps to cause the bug to occur

Remap the Caps Lock key as an additional Esc via gnome-tweaks
Enable "keyboard.dispatch": "keyCode" to circumvent the problems with key remapping in the normal VS code editor
Try to exit the cell edit mode of the Notebook editor via the Esc on the remapped key

Actual & Expected behavior
Escpected: The "keyboard.dispatch": "keyCode"setting is respected and the press of the remapped Esc results in leaving jupyter edit mode.
Result: only the original Esc leaves the jupyter edit mode of the cell, pressing the remapped Esc jupyter remains in edit mode. (CAPS LOCK is not activated!)
Your Jupyter and/or Python environment

Jupyter server running:                       Local
Extension version:                               2019.10.41019
VS Code version:                                1.39.2
Setting python.jediEnabled:               true
Python and/or Anaconda version:     3.7.1
OS:                                                    Linux (distro): Ubuntu 18.04 LTS
Virtual environment:                          conda

Developer Tools Console Output

Sorry but at the moment we don't support any editor extensions that VS code has.

Thx for the quick reply
What do you mean by editor extension in this case? What would be the appropriate address for such an issue?

VS code's editor is this one:
https://microsoft.github.io/monaco-editor/
They customize it a bunch inside of VS code. Some of those customizations are done through your settings.json. We don't currently read those customizations (except for theme) from your settings.json. Theoretically (since we also use the monaco editor), we should be able to apply all of them, but we just haven't gotten to them all yet.
Hope that helps.


High number of drops for April - CEX Funding

I have been watching the performance for this bot for the month of April (CEX Funding - 0xf496e3f522ec18ed9be97b815d94ef6a92215fc8e9a1a16338aee9603a5035fb) and it looks like it has a high number "tx_drops" for BSC chain, this issue might be also extending to the rest of the chains. I would appreciate if you can check it out, and consider sharding as a potential solution to mitigate this.

asked nethermind to tackle

fixed in https://github.com/forta-network/starter-kits/pull/224


[FEATURE] New login/signup page

Description
When we enter site, we directly get to the posts and due to this our database needs to be exposed to public to load posts, which isn't a good practice. We can have a sign in/sign up page instead.
Screenshots
No response
Additional information
We need to implement a simple login/signup page

@narayan954 Can you please assign this issue to me?

Okay @tanishk-23

Please assign me this issue @narayan954

Please assign me this issue @narayan954

you need to ask @tanishk-23

it's been 24hours of no response from tanishk, so @Pranjal2870 you can work on this.

Okay

Open for KWOC

Hello @narayan954 I'd love to work on this issue if that's OK.
Can you please assign it to me?

Sure @singhkaran202

I'm interested to contribute this issue. Can you assign me?

I'm interested to contribute this issue. Can you assign me?

Hello @srilakshmiv123, this issue is currently assigned to @singhkaran202, you can ask him, if he permits then I can assign you or if he doesn't respond within 3 days then I will assign you.
Hope you understand.
Thanks

@narayan954 it seems that no one is working on this issue can you assign me this?

@narayan954 it seems that no one is working on this issue can you assign me this?

@singhkaran202 please mention if you're working on this within 24 hours or It'll get assigned to @kshitij01042002

Yes please, I am working on it...

I want to work on this. Please assign me @narayan954

I want to work on this. Please assign me @narayan954

due to no progress from @singhkaran202 you can work on this

can you assign this to me @narayan954

Changing difficulty to medium :)

Hi, are you still working?

hi @narayan954   I would like to work on the issue .
Can you assign it to me. under JWOC

I'm interested to contribute this issue. Can you assign me?

@Sarita-021 best of luck! :)

I'm interested to contribute this issue. Can you assign me?

Sorry @parv15, she claimed it first :/ as in FCFS scheduling.

@Sarita-021 are you still working? please confirm

No

No

okay

please assign this issue to me @narayan954

please assign this issue to me @narayan954

sure go ahead! and please confirm program, jwoc?

Yes
On Mon, Feb 20, 2023, 23:02 Narayan soni @.***> wrote:

please assign this issue to me @narayan954 https://github.com/narayan954
sure go ahead! and please confirm program, jwoc?
—
Reply to this email directly, view it on GitHub
https://github.com/narayan954/dummygram/issues/76#issuecomment-1437354646,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVPNX2S5M6J54P247YF5WV3WYOTEDANCNFSM6AAAAAARASFAAA
.
You are receiving this because you commented.Message ID:
@.***>

please assign this issue to me @narayan954

sure go ahead! and please confirm program, jwoc?

Yes jwoc

great, best of luck!

@narayan954 On which branch, do I have to work? Is it master or I make another branch

@narayan954 On which branch, do I have to work? Is it master or I should make another branch

you have to create a branch for the task and create a pull request to the master branch when done

Ok narayan Thank you
On Tue, Feb 21, 2023, 12:40 Narayan soni @.***> wrote:

@narayan954 https://github.com/narayan954 On which branch, do I have to
work? Is it master or I should make another branch
you have to create a branch for the task and create a pull request to the
master branch when done
—
Reply to this email directly, view it on GitHub
https://github.com/narayan954/dummygram/issues/76#issuecomment-1437958634,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVPNX2UDTTUHMOXSB2F6E3LWYRS5BANCNFSM6AAAAAARASFAAA
.
You are receiving this because you were assigned.Message ID:
@.***>

are you still working on this? please update @vatan-prakash

No, I am not please assign to any one else
On Sat, Feb 25, 2023, 15:15 Narayan soni @.***> wrote:

are you still working on this? please update @vatan-prakash
https://github.com/vatan-prakash
—
Reply to this email directly, view it on GitHub
https://github.com/narayan954/dummygram/issues/76#issuecomment-1445042741,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVPNX2TRNWRYL45TJIZSUIDWZHIC5ANCNFSM6AAAAAARASFAAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

alright :)

@narayan954 Assign it to me Narayan.

@narayan954 Assign it to me Narayan.

okay, you can go ahead!

@narayan954  Do I need to remove the sign-in and signup modals and replace them with a page?

@narayan954 Do I need to remove the sign-in and signup modals and replace them with a page?

We may have the main/whole application authenticated by default, so I don't think we'd need those login and signup buttons and their modals as well.

like instagram.com

@narayan954 Raised PR #222


How can I change the reference for gene quantification?

Dear There,
I would like to use the bulk RNA-Seq pipeline to do data analysis. I did some test and figured that the default is Ensembl reference for gene quantification. Is there anyway I can change it to RefSeq reference? Thanks!
Xue

Hi @xgong-tb,
Sorry for taking so long to get back to you. You can provide a GTF file from RefSeq if you like via the transcriptome_gtf option, and bcbio will use that to do the quantification. You have to be careful though to make sure the chromosome names match up and the GTF is well formed. If you can point me to the GTF you want to use, I can tell you if it will be compatible or not. Sorry again for the delay.


Feature/gurobi optimizer installation

Install Gurobi Optimizer into airflow service
New user and password policy on docker-compose example files

Can you solve the conflicts? or do you need help?


Deployment

Deployment
User story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
A.C
GIVEN a Prework Study Guide website,
WHEN I visit the website using the URL,
THEN I can access my website from any browser

Site published through Github pages!


[CRA v5] Jest + React-markdown = Must use import to load ES Module

Describe the bug
Running a CRA test rendering react-markdown leads to an error message "Must use import to load ES Module:"
A (somewhat) related issue in https://github.com/remarkjs/react-markdown/issues/635 seems to redirect to https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c, which in turn states "Create React App doesn't yet fully support ESM. I would recommend opening an issue on their repo with the problem you have encountered. One known issue is #10933."
/cc @ChristianMurphy
Did you try recovering your dependencies?

Yes
Which terms did you search for in User Guide?

esm
Environment

Windows
Steps to reproduce

Full repro case is available at

Clone https://github.com/nulltoken/repro-react-markdown-cra-esm
run yarn test

Output of yarn test can be reviewed at https://github.com/nulltoken/repro-react-markdown-cra-esm/runs/4841320780?check_suite_focus=true
Expected behavior

I'd very much like the test not to fail because of an import issue :-/
Actual behavior

Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Not sure if this helps but I managed to get my react-markdown tests to run with CRA by modifying the test command
react-scripts test --maxWorkers=2 --transformIgnorePatterns \"node_modules/(?!react-markdown)/\" --env=jsdom

@KieranDotCo Thanks for the hand. Unfortunately, this doesn't seem to do the trick with CRA v5. The same error occurs.

@yuchen-w Thanks but it looks like those solutions target CRA 4.x (and I'd really like to avoid the mocking approach)

@nulltoken I am using this solution on CRA v5.
// package.json
  "jest": {
    "transformIgnorePatterns": [
      "(?!(/node_modules/(react-markdown|vfile|vfile-message|unist-.*|unified|bail|is-plain-obj|trough|remark-.*|mdast-util-.*|micromark.*|decode-named-character-reference|character-entities|property-information|hast-util-whitespace|space-separated-tokens|comma-separated-tokens|pretty-bytes)/))(/node_modules/.+.(js|jsx|mjs|cjs|ts|tsx)$)",
      "^.+.module.(css|sass|scss)$"
    ]
  }

@esetnik had to slightly modify the pattern for me.
This worked for me on a MacBook:
"jest": {
    "transformIgnorePatterns": [
      "[/\\\\]node_modules[/\\\\](?!(react-markdown|vfile|vfile-message|markdown-table|unist-.*|unified|bail|is-plain-obj|trough|remark-.*|mdast-util-.*|escape-string-regexp|micromark.*|decode-named-character-reference|character-entities|property-information|hast-util-whitespace|space-separated-tokens|comma-separated-tokens|pretty-bytes|ccount)).+\\.(js|jsx|mjs|cjs|ts|tsx)$"
    ]
  },

@jcgentr and @esetnik answers didn't work for me. However, they pointed me in the correct direction. Especially because this solutions works for projects created with create-react-app. I needed to edit the regex pattern to the following.
"jest": {
    "transformIgnorePatterns": [
      "[/\\\\]node_modules[/\\\\](?!(react-markdown|vfile|vfile-message|markdown-table|unist-.*|unified|bail|is-plain-obj|trough|remark-.*|rehype-.*|html-void-elements|hast-util-.*|zwitch|hast-to-hyperscript|hastscript|web-namespaces|mdast-util-.*|escape-string-regexp|micromark.*|decode-named-character-reference|character-entities|property-information|hast-util-whitespace|space-separated-tokens|comma-separated-tokens|pretty-bytes|ccount|mdast-util-gfm|gemoji)).+\\.(js|jsx|mjs|cjs|ts|tsx)$"
    ]
  }

Basically, I just added these patterns:

rehype-*
hast-util-.*
mdast-util-gfm
web-namespaces
zwitch
hast-to-hyperscript
html-void-elements
gemoji

If running the tests still fails for you because Jest encountered an unexpected token, just try to add the node_module folder where it occurred. Unfortunately, sometimes the error message does not directly point to the correct package, which should be transformed. For example, I always got an error message which pointed to the mdast-util-gfm-autolink-literal package, however, the error actually happened because mdast-util-gfm was not transformed. Just try to google the error. :)

@martenmatrix This worked for me, thank you so mucH!

I used Option 1 in Recommended solution by react-markdown
Which is mocking the modules. Probably the easiest way.

Guys, you can see a lot of likes under the previous entries, and in you, as well as me, the tests still don't work.
Pay attention ob a babel, in my case, it helped me:

@Slisarenko Great you figured it out. Do you mind sharing the relevant parts of your babel.config.json and jest.config.cjs?

@fbruckhoff No problem, here:
jest.config.cjs:
const esModules = [
  'react-markdown',
  'vfile-message',
  'markdown-table',
  'unist-.*',
  'unified',
  'bail',
  'is-plain-obj',
  'trough',
  'remark-.*',
  'rehype-.*',
  'html-void-elements',
  'hast-util-.*',
  'zwitch',
  'hast-to-hyperscript',
  'hastscript',
  'web-namespaces',
  'mdast-util-.*',
  'escape-string-regexp',
  'micromark.*',
  'decode-named-character-reference',
  'character-entities',
  'property-information',
  'hast-util-whitespace',
  'space-separated-tokens',
  'comma-separated-tokens',
  'pretty-bytes',
  'ccount',
  'mdast-util-gfm',
  'gemoji',
  /** react-markdown 8.0.3 */
  'trim-lines',
  'jest-runtime',
  'vfile',
  /** react-markdown 7.2.1 */
  'longest-streak',
].join('|');

module.exports = {

  clearMocks: true,

  collectCoverage: true,

  collectCoverageFrom: ['src/**/*.{js,jsx,ts,tsx}', '!src/index.tsx'],

  coverageDirectory: 'coverage',

  coveragePathIgnorePatterns: [
    '/node_modules/',
  ],

  moduleNameMapper: {
    '\\.(jpg|jpeg|png|gif|eot|otf|webp|svg|ttf|woff|woff2|mp4|webm|wav|mp3|m4a|aac|oga|pdf)$': '<rootDir>/__mocks__/fileMock.js',
    '\\.(css|less)$': 'identity-obj-proxy',
  },

  transformIgnorePatterns: [
    `[/\\\\]node_modules[/\\\\](?!${esModules}).+\\.(js|jsx|mjs|cjs|ts|tsx)$`,
  ],

  moduleFileExtensions: ['ts', 'tsx', 'js', 'jsx', 'json'],

  globalSetup: '<rootDir>/global-setup.js',
};

babel.config.js:
module.exports = {
  presets: [
    '@babel/preset-env',
    '@babel/preset-react',
  ],
};


Made changes to button

This is what the button looks like now

Add some padding to button plus the twitter icon is not in line with the button. Refer styling from other pages.

update your code with current changes


Blocked or something

I am unable create it so there is way can fix

Unfortunately Heroku has blocked the proxy on their platform for whatever reason. There's nothing I can do, you will have to look for alternative places to host the proxy.

Actually, there is a way! Check out this youtube video: https://www.youtube.com/watch?v=WFlOJ5dBTNk


[Windows] Fix issue where WebView events could not be send when multiple WebView in the application

Summary
When application has more than one WebView causes that WebView's event are not anymore sent (for example WebView.NavigationCompleted()) See more about issue #1572
Bug is that ReactWebViewManager deletes always previous WebView instanse in method:
 winrt::FrameworkElement ReactWebViewManager::CreateView() noexcept {
        m_reactWebView = *winrt::make_self<ReactWebView>(m_reactContext);
        return m_reactWebView.GetView();
    }

Fix is to give whole ReactWebView that is UserControl and contains WebView as content and there is no need to store ReactWebViewinstance as variable inReactWebViewManager. Next CreateViewcall does not anymore reset pointer of previousReactWebView`.
winrt::FrameworkElement ReactWebViewManager::CreateView() noexcept {
      auto view = winrt::ReactNativeWebView::ReactWebView(m_reactContext);
      return view;
    }

Test Plan
See example app from the  issue #1572 and see how events are missing.
Compatibility
Windows 10
"react-native": "0.62.2"
"react-native-windows": "0.62.5"
Checklist

[x] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md

This PR closes #1572

See PR https://github.com/react-native-community/react-native-webview/pull/1617 that icludes these fixes also

I also encountered this problem. Can I merge it?  @jamonholmgren

Do not merge this invalid PR, see my new PR https://github.com/react-native-community/react-native-webview/pull/1617

thank you


Implement trade cancel packets

Copied from the Discord:
Gent — 12/09/2023 9:26 AM
noticed while working on RustyFusion that we aren’t handling P_CL2FE_REQ_PC_TRADE_OFFER_CANCEL, which is what the client sends if the player is in combat, shopping, etc. and they get a trade offer. Response packets do exist and it looks like they are handled clientside (with UI even) so I might put up a PR for that too.

I can churn this out pretty quickly.


Autocomplete dropdown doesn't show when in use with Material-Kit

Autocomplete dropdown doesn't show when in use with Material-Kit
Material-kit repo: https://github.com/creativetimofficial/material-kit
What happened when used with Material-kit:

What happened when Material-kit css is not used:

Fixed !
The problem was that Material-Kit uses "visibility" and "opacity" instead of "display" to show and hide dropdown

I know the issue is closed, but I just want to say thanks for the fast reply and fix!
It really makes me happy to see a developer being so enthusiastic about a free, open source project like this. Keep building great things man!


feat: add logger interface

Pass a custom logger to log messages

This is definitely an improvement. If you haven't already, I'd also suggest checking out logrus. It seems to be the de facto standard for logging in Go, and supports things like structured data. It's pluggable, you can use any logging backend you want with it. GitLab uses logrus, wrapped in their own wrapper.

I would avoid using logrus since there are many different go loggers out there and each has its interface. Perhaps we could make this Logger interface structured instead

Perhaps we could make this Logger interface structured instead

Yes, I think that would be a good idea too, and then on GitLab's side we could simply add a Logrus backend for your Logger interface.

Cc: @ashmckenzie


use googler to find movie even if the name has a type

warning : only works on mac os x
will use googler to find the real name of the movie and then feed that to OMDb API
instead of this:

you will get this:

I love the idea of being able to have a typo in the movie title and it still get the correct result, however this fix is platform specific and it needs an external dependency to work. It is a major goal of this project to have no dependencies. Is there any way you could rework this to not need googler but instead some other web api that would keep it from being platform specific, although after trying to find an api that could accomplish this i came up empty handed. Let me know if you have any better luck, otherwise I will consider adding this as is.

yeah you're right it, it will be better to use an api for this , i'll try to find something.

If this is going to be added it needs to use an api that works with one of the native modules curl, wget or fetch. This merge also needs to be reforked so that it will not have as many conflicts the the base repository.


I just pressed "." right after sklearn to access subpackages

Description
What steps will reproduce the problem?

from sklearn[incident was here] when I typed "." to use subpackages, this happened! Don't you think Kite is causing this?
Also my Ctrl+I to show help does not work!!!
And there's been some bugs around Dark Mode theme
Traceback
  File "/home/couzhei/anaconda3/lib/python3.7/site-packages/spyder/plugins/completion/fallback/actor.py", line 155, in handle_msg
    msg['current_word'])
  File "/home/couzhei/anaconda3/lib/python3.7/site-packages/spyder/plugins/completion/fallback/actor.py", line 62, in tokenize
    valid = is_prefix_valid(text, offset, language)
  File "/home/couzhei/anaconda3/lib/python3.7/site-packages/spyder/plugins/completion/fallback/utils.py", line 125, in is_prefix_valid
    current_pos_text = text[offset - utf16_diff - 1]
IndexError: string index out of range

Versions

Spyder version: 4.1.2
Python version: 3.7.7
Qt version: 5.9.6
PyQt5 version: 5.9.2
Operating System: Linux 5.3.0-45-generic

Dependencies

# Mandatory:
atomicwrites >=1.2.0           :  1.3.0 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  1.3.0 (OK)
diff_match_patch >=20181111    :  20181111 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.13.0 (OK)
jedi =0.15.2                   :  0.15.2 (OK)
keyring                        :  None (OK)
nbconvert >=4.0                :  5.6.1 (OK)
numpydoc >=0.6.0               :  0.9.2 (OK)
parso =0.5.2                   :  0.5.2 (OK)
pexpect >=4.4.0                :  4.8.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.7.0 (OK)
pygments >=2.0                 :  2.6.1 (OK)
pylint >=0.25                  :  2.4.4 (OK)
pyls >=0.31.9;<0.32.0          :  0.31.9 (OK)
qdarkstyle >=2.8               :  2.8 (OK)
qtawesome >=0.5.7              :  0.7.0 (OK)
qtconsole >=4.6.0              :  4.7.2 (OK)
qtpy >=1.5.0                   :  1.9.0 (OK)
rtree >=0.8.3                  :  0.9.3 (OK)
sphinx >=0.6.6                 :  2.4.4 (OK)
spyder_kernels >=1.9.0;<1.10.0 :  1.9.0 (OK)
watchdog                       :  None (OK)
xdg >=0.26                     :  0.26 (OK)
zmq >=17                       :  18.1.1 (OK)

# Optional:
cython >=0.21                  :  0.29.15 (OK)
matplotlib >=2.0.0             :  3.1.3 (OK)
numpy >=1.7                    :  1.18.1 (OK)
pandas >=0.13.1                :  1.0.3 (OK)
scipy >=0.17.0                 :  1.4.1 (OK)
sympy >=0.7.3                  :  1.5.1 (OK)

Reset factoried it, it's now fine, oh and I see the Kite icon at the bottom says "ready", while it was disabled earlier, ctrl+I works fine, now! but that's obviously not a solution.

Duplicate of #12266

No one has been able to give us a reproducible example, so it's impossible for us to fix this. If you find one, please post it on issue #12266.


loosen protobuf version

It's fixed at one version, which was an oversight.
https://github.com/pyansys/pyfluent/issues/1005

Hi @seanpearsonuk
Thanks for the quick reply and support!

merged in other PR


pull request for e2e test at 12/19/2016 19:45:20

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


warnAboutGHooks() should exit with an error

Because missing ghooks is similar to a hook failing.
Therefore: process.exit(1).

I think that's a good change. Feel free to makeapullrequest.com


Doughnut chart has incorrect border when overful

Expected Behavior
Doughnut chart analogous to underful segment
Current Behavior
Only the inner endpoint of the border line moves as expected, the outer endpoint is stuck at the top.
See for yourself here: https://jsfiddle.net/kpdyvxuc/1/
Change the value of circumference to better see the bug in action.
Steps to Reproduce (for bugs)
https://jsfiddle.net/kpdyvxuc/1/
Context
We are trying to visualize an overfulfillment of a measurement (>100%). Note that this would be possible to visualize statically using other features (like rotation), but this would be incompatible with a correct animation.
Environment

Chart.js version: 2.5.0
Browser name and version: Google Chrome Version 70.0.3538.77 (Official Build) (64-bit)

bump

bump


update package.json per contributing guide

yarn watch did not exist, this pr adds this script to run the plugin in watch mode
yarn dev ran the plugin in watch mode, but now builds the plugin in development mode

I think this is more in sync with the instruction in the contributing guide

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix #45: Enhancement to allow service provider overrides by user

This is an enhancement for service developers to test services under development that may override existing services in other jar files.
This change has been tested as well as build successfully on some of the dependent repos, by temporarily bumping up version numbers in these repos (e.g ehcache).

This should be a different API, not implicitly making all explicitly registered services behave this way.  The reason is that the common path should behave more like tc-core and this should really only be something someone opts into due to a packaging scenario they can't easily resolve for a simple test.

Ok. That make sense. I will add a different API and updated the PR.
The reason I did it this way is because no one must be anyway using this as the assert is in place.
But like you said, it is better if the caller explicitly sets this with a separate call and knows what he or she is getting into.

Can you combine these commits into one?  It otherwise looks reasonable.  I just don't want the intermediary discussion points in the version history (since they are steps in implementing the same idea in its first version).

ok. done now. Wanted you to take a look at the diff before squashing the commits.


Fixed grammar on line #4.

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ x] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

This sounds better @msamylea, thanks for contributing to freeCodeCamp!


qbittorrent-nightly-lean@10449641601: hash check failed

| qbittorrent-nightly-lean:<PHONE_NUMBER>5 -><PHONE_NUMBER>1
| Updating one outdated app:
| Updating 'qbittorrent-nightly-lean'<PHONE_NUMBER>5 -><PHONE_NUMBER>1)
| Downloading new version
| Downloading https://nightly.link/qbittorrent/qBittorrent/workflows/ci_windows.yaml/master/qBittorrent-CI_Windows-x64_libtorrent-2.0.10.zip (69.3 MB)...
| Checking hash of qBittorrent-CI_Windows-x64_libtorrent-2.0.10.zip ... ERROR Hash check failed!
| App:         cmontage_scoopbucket-third/qbittorrent-nightly-lean
| URL:         https://nightly.link/qbittorrent/qBittorrent/workflows/ci_windows.yaml/master/qBittorrent-CI_Windows-x64_libtorrent-2.0.10.zip
| First bytes: 50 4B 03 04 14 00 08 00
| Expected:    129119269a20586a6df7bc6e124018c8f48f12634753c8435ae93b81d2c22ad9
| Actual:      698a92020f3185f04e19f2b6b32bbabfadddc51f2b3265dd9649d8fa3ade1d20

| qbittorrent-nightly-lean:<PHONE_NUMBER>5 -><PHONE_NUMBER>1
| Updating one outdated app:
| Updating 'qbittorrent-nightly-lean'<PHONE_NUMBER>5 -><PHONE_NUMBER>1)
| Downloading new version
| Downloading https://nightly.link/qbittorrent/qBittorrent/workflows/ci_windows.yaml/master/qBittorrent-CI_Windows-x64_libtorrent-2.0.10.zip (69.3 MB)...
| Checking hash of qBittorrent-CI_Windows-x64_libtorrent-2.0.10.zip ... ERROR Hash check failed!
| App:         cmontage_scoopbucket-third/qbittorrent-nightly-lean
| URL:         https://nightly.link/qbittorrent/qBittorrent/workflows/ci_windows.yaml/master/qBittorrent-CI_Windows-x64_libtorrent-2.0.10.zip
| First bytes: 50 4B 03 04 14 00 08 00
| Expected:    129119269a20586a6df7bc6e124018c8f48f12634753c8435ae93b81d2c22ad9
| Actual:      698a92020f3185f04e19f2b6b32bbabfadddc51f2b3265dd9649d8fa3ade1d20

just add -s at the end of command


Remove sub commands

chest is a box
This chest was with lots of decoration, but I just re-decorate to simple.
Also, this is definitely MAJOR UPDATE :dancer:
Updates:

Remove install, boost, script, sync and run. Breaking change! Major update!
Say byebye to chest.json.

Notes:
I'll recreate sync command based package.json. See also the ROADMAP

Seems ok.


Revisit the Firebase API version

...it is old.

May be consider Supabase instead which claims to be the open-source alternative to Firebase

May be consider using Supabase instead which claims to be an open-source alternative to Firebase. The Vue demo is written in Typescript and supports type generation.

May be consider using Supabase instead which claims to be an open-source alternative to Firebase. The Vue demo is written in Typescript and supports type generation.

May be consider using Supabase instead which claims to be an open-source alternative to Firebase. The Vue demo is written in Typescript and supports type generation.


unrecognized file extension is assumed to be descriptor file, crashes Ferret

Reported by Ansley B Manke on 16 Aug 2007 16:06 UTC
A file of type .netcdf crashes Ferret on SET DATA file.netcdf
yes? set data 5F78C2CAA20FFCB693D1852459EA5E68_ferret_listing.netcdf
I/O recursion: I/O started while already doing I/O
apparent state: unit 62 named
./5F78C2CAA20FFCB693D1852459EA5E68_ferret_listing.netcdf
last format: list io
In tm_init_dset.F we check for .nc, .cdf, and .des If there is no extension or
one of these is not matched, then the "default extension" is assumed, and this
default is .des. A better default these days would be .nc . I propose trying it
as a netCDF file, and if it cannot be opened then issue an error message.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1531

Comment by ansley.b.manke on 12 Sep 2012 21:57 UTC
This is done in Ferret v6.83


fix: conan create package

Creating the package with conan failed because the cmake finder couln't find CURL.
conan create . influxdb-cxx/0.6.4@steiner/testing -o shared=True -o libcurl:shared=True -o openssl:shared=True -o zlib:shared=True -o boost=False
CMake Error at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:165 (message):
  Could NOT find CURL (missing: CURL_LIBRARY CURL_INCLUDE_DIR)
Call Stack (most recent call first):
  /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:458 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.18/Modules/FindCURL.cmake:169 (find_package_handle_standard_args)
  CMakeLists.txt:74 (find_package)

-- Configuring incomplete, errors occurred!

We can use the cmake_find_package generator here and conan create will work.

This is an interesting behaviour as the CI build still builds the package without running into the issue (boost on/off). I'm also able to build it locally.
Here's how my minimal build:
conan create .

When building shared using your options – please note the 'influxdb-cxx:' prefix I had to use – I'm getting undefined reference issues on the conan test package step though. The package build was able to pick up curl.
conan create  -o influxdb-cxx:shared=True -o libcurl:shared=True -o openssl:shared=True -o zlib:shared=True -o influxdb-cxx:boost=False .

What happens if you build without the shared options?

I have just noticed, that the package build seems to pick up my systems curl instead :facepalm:. Can you check the CMake log whether this happens to you as well?

I have tested the change locally and it solves curl issue. But building without the shared flags fails:
> conan create .
[…]
-- Library boost_system found […long conan path…]/libboost_system.so
-- Found: […long conan path…]/libboost_system.so
[…]
CMake Error at src/CMakeLists.txt:1 (add_library):
  Target "InfluxDB" links to target "Boost::system" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?

CMake Error at src/CMakeLists.txt:1 (add_library):
  Target "InfluxDB" links to target "Boost::system" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
[…]

I have tested the change locally and it solves curl issue. But building without the shared flags fails:
> conan create .
[…]
-- Library boost_system found […long conan path…]/libboost_system.so
-- Found: […long conan path…]/libboost_system.so
[…]
CMake Error at src/CMakeLists.txt:1 (add_library):
  Target "InfluxDB" links to target "Boost::system" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?

CMake Error at src/CMakeLists.txt:1 (add_library):
  Target "InfluxDB" links to target "Boost::system" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
[…]

boost in conan-center-index is not supporting components yet, so i removed the find_package_generator and used the cmake generator instead.

This is an interesting behaviour as the CI build still builds the package without running into the issue (boost on/off). I'm also able to build it locally.
Here's how my minimal build:
conan create .

When building shared using your options – please note the 'influxdb-cxx:' prefix I had to use – I'm getting undefined reference issues on the conan test package step though. The package build was able to pick up curl.
conan create  -o influxdb-cxx:shared=True -o libcurl:shared=True -o openssl:shared=True -o zlib:shared=True -o influxdb-cxx:boost=False .

What happens if you build without the shared options?

Sry, I didn't test that before. I only cross-compiled to another target and skipped the test_pacakge with -tf None.
With the cmake generator it is working now.

Thank you! :+1:
To be honest, I don't really understand why this variant works, even though the components aren't supported by boost …


Contour Sequence should be optional.

Hi,
Thank you for this awesome tool!
Contour Sequence is Type 3 (Optional), there's no guarantee it'll be present in a given item in the ROI Contour Sequence. I recently stumbled on AttributeError: 'Dataset' object has no attribute 'ContourSequence' while loading an existing RT Struct contour as a mask.
I think this error should not occur. I managed to fix it and will make a pull request to review my correction.
Best,
Maxence

Hey Maxence, thanks for looking into this! Merged :)

Hey Maxence, thanks for looking into this! Merged :)

The pull request appears to have been closed instead of merged. Is it a mistake?


Modify test harness to stop emitting color; add IR reference files to gitignore

Per https://github.com/dada-lang/dada/issues/135, we should modify the test harness...

to stop emitting color in the stdout files
to generate the various IR files but not to check if they have changed (they are for looking at, not for reference)

The second step allows us to add them to gitignore (and remove the existing files from the repository)

Actually, @lqd, in merging #140 I overlooked an issue!
That PR ignored all ref files, but I think we still want to be checking certain files-- actually, I guess it's just one.
Want to check:

annotations in file match actual errors (:heavy_check_mark: this matches main)
stdout/stderr from execution match stdout.ref and stderr.ref (and matches annotation in file) (:heavy_check_mark: this matches main, I believe)
compiler output matches ref.ref file (:x: we don't check this on main now -- also, we should rename ref.ref)

Do not want to check (or commit into the repo), but do want to generate:

IR generated (syntax.ref, validated.ref, bir.ref)
LSP output (lsp.ref)

Maybe we should rename those files to .debug or something?

I'll take care of that

Oh, I forgot one thing -- HeapGraph-*.ref -- I'm torn on this one. I do want to be testing that the heap graph dump is successful and contains certain key elements, but the ref files contain an awful lot of details.
Still, I think for now we should keep them.

The idea is that they are testing that the #? output contains what we expect it to contain. Admittedly, I mostly ignore diffs that occur in them, which is a bad sign. :)

(One thing I was considering was trying to find some kind of "ascii-art" renderer for graphviz files and checking that in, I think I would read that much more happily...)

@lqd yes! The only tools I found for that were written in perl, which was kind of a drag.

Honestly, maybe we should do a web request to that site :)

(heh, or I guess setup our own...that'd be kind of rude)

I wonder if we could compile the whole kit-and-kaboodle to wasm somehow :)

@lqd filed https://github.com/dada-lang/dada/issues/150

@lqd oh my :) well, we could also host it? not sure how hard that would be.
Still, it feels like overall it'd be better/easier to just add a way to dump the output in a more readable format than graphviz.

But I think i will mark this bug as fixed!

ASCII output would be super cool, but maybe svg or another image format would be easier and acceptable in the meantime ? It's not really easily readable as text, but neither is a sufficiently large/complicated .dot file. We can easily do svg output in pure rust via https://github.com/nadavrot/layout.


no way to remove deleted items from playlist (private only?)

When I go into the playlist, it doesn't show there. If we kept the 3 button menu on hover, can remove?

You can remove if you go into the playlist now

There's a delete button on mouse over now


Support historical data bar updates

Support historical data bar updates

A user is testing this fix and noted that TWS is sending duplicates for bar updates.  These duplicates seem to have one row with additional volume and other data.  The user has duplicated without DH and is getting further information.


Thruster caching doesn't seem to be working

Steps to reproduce
Open a terminal, type these commands to create a sample project
# Create a new project
rails new thruster-demo
cd thruster-demo

# Comment out the debug gem to get around a thruster bug
sed -i.bak '/gem "debug", platforms: %i\[ mri windows \]/s/^/#/' Gemfile && rm Gemfile.bak

# Tell puma to log asset requests
echo "quiet false" >> config/puma.rb

# Create a 10x10 red image to use as a placeholder asset
convert -size 10x10 xc:'#FF0000' public/red_image.png

# Add the sendfile header to development.rb
sed -i.bak '/config.assets.quiet = true/a\
config.action_dispatch.x_sendfile_header = "X-Sendfile"' config/environments/development.rb

# Install thruster and start it
gem install thruster
thrust rails s

Open a new terminal and start making requests for that asset (or use the browser with cache disabled):
curl http://localhost:80/red_image.png > /dev/null 2>&1
curl http://localhost:80/red_image.png > /dev/null 2>&1
curl http://localhost:80/red_image.png > /dev/null 2>&1

Expected behavior

Puma should log only the first asset request. Thruster should have the asset cached and handle the next two.
There should be a file called "red_image.png" in "storage/thruster"

Actual behavior
Puma will log every asset request, which means Thruster is not caching the asset and acting as a reverse proxy:
::1 - - [11/Apr/2024:11:13:47 -0300] "GET /red_image.png HTTP/1.1" 200 - 0.0011
{"time":"2024-04-11T11:13:47.513758-03:00","level":"INFO","msg":"Request","path":"/red_image.png","status":200,"dur":4,"method":"GET","req_content_length":0,"req_content_type":"","resp_content_length":312,"resp_content_type":"image/png","remote_addr":"[::1]:65489","user_agent":"curl/8.4.0","cache":"miss","query":""}
::1 - - [11/Apr/2024:11:13:48 -0300] "GET /red_image.png HTTP/1.1" 200 - 0.0003
{"time":"2024-04-11T11:13:48.477155-03:00","level":"INFO","msg":"Request","path":"/red_image.png","status":200,"dur":0,"method":"GET","req_content_length":0,"req_content_type":"","resp_content_length":312,"resp_content_type":"image/png","remote_addr":"[::1]:65491","user_agent":"curl/8.4.0","cache":"miss","query":""}
::1 - - [11/Apr/2024:11:13:48 -0300] "GET /red_image.png HTTP/1.1" 200 - 0.0003
{"time":"2024-04-11T11:13:48.907032-03:00","level":"INFO","msg":"Request","path":"/red_image.png","status":200,"dur":0,"method":"GET","req_content_length":0,"req_content_type":"","resp_content_length":312,"resp_content_type":"image/png","remote_addr":"[::1]:65492","user_agent":"curl/8.4.0","cache":"miss","query":""}

The directory storage/thruster does not exist.
System configuration
Rails version: Rails <IP_ADDRESS>
Ruby version: ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-darwin23]

Thruster depends on the Cache-Control HTTP response header from the asset in order to cache it accordingly. Notice the following test section:
https://github.com/basecamp/thruster/blob/08e70b0bf094e7f749a366265abb852e6797aad4/internal/cacheable_response_test.go#L18-L26
These are Cache-Control headers that will yield a cached response on Thruster.
That means that you'll need to add config.public_file_server.headers = { "Cache-Control" => "public, max-age=#{2.days.to_i}" } to your config/environment/development.rb file in order to ensure Rails returns them to Thruster. (You could also touch tmp/caching-dev.txt but that'll also enable some Rails-side asset caching that we don't need/want here).
With this change, if you repeat your reproduction steps you'll have the following:
{"time":"2024-04-11T22:56:42.3836-03:00","level":"INFO","msg":"Request","path":"/red_image.png","status":200,"dur":5,"method":"GET","req_content_length":0,"req_content_type":"","resp_content_length":312,"resp_content_type":"image/png","remote_addr":"[::1]:57156","user_agent":"curl/8.4.0","cache":"miss","query":""}
{"time":"2024-04-11T22:56:43.226634-03:00","level":"INFO","msg":"Request","path":"/red_image.png","status":200,"dur":0,"method":"GET","req_content_length":0,"req_content_type":"","resp_content_length":312,"resp_content_type":"image/png","remote_addr":"[::1]:57158","user_agent":"curl/8.4.0","cache":"hit","query":""}
{"time":"2024-04-11T22:56:44.151529-03:00","level":"INFO","msg":"Request","path":"/red_image.png","status":200,"dur":0,"method":"GET","req_content_length":0,"req_content_type":"","resp_content_length":312,"resp_content_type":"image/png","remote_addr":"[::1]:57161","user_agent":"curl/8.4.0","cache":"hit","query":""}

Notice that only the initial request has a "cache":"miss". The two follow ups have "cache":"hit". This is Thruster's log showing that the cache was found.
In the current version, assets are only cached in memory, not under the storage/thruster directory -- I believe only the SSL/TLS cert is stored on that directory.

Thanks for answering this one, @jmonteiro!
Closing this as I believe Thruster is working as intended here. We will only cache responses that declare themselves to be cacheable, by way of the Cache-Control header.


Update dev readme

I did some minor work on the dev readme file:

Restructure the how-to part, using correct heading levels
Add instructions on accessing the Django shell
Add instructions on making a superuser account
Add instructions on adding a user to moderators

Flagging @llewelld for review as he said he'd like to look over the open PRs 😉

Merging in after also taking @llewelld's great ideas into account! 🎉


You can add a block Projects?

You can add a block Projects, where will be listed some projects that are not ashamed to show?

It's relatively easy to add yourself. Just look at the menu and then add another option:

Projects

Afterward, copy the code of another section and then change the anchor and title to projects. Now you have a project section. Here is the difficult part. If you want to format differently or add an image next to your project, you'll need to play around with html.


if cp is lower, transfer only caught pokemon

This changes will not transfer pokemon from the bag as some people have mentioned that they need this feature. In future, pokemon from bag will transfer too unless its only 1 left of its own type.

Hmm, do we really need this ? @techedlaksh

Right now it only deletes the pokemon we just caught, if its cp is lower but i was gonna change this to removing all duplicates (leaving one) lower than the set cp.

I'm actually using it since i don't want the bot to delete my pokemon in the bag.

OK, then we need another place to drop many pokemon in bag.

Thanks for your vote  and pull request :)


fw_att_control: move ecl/attitude_fw into fw_att_control

Let's merge this back into PX4/Firmware. A large proportion of the code simply goes away if the work is handled in place.
ECL side (required first): https://github.com/PX4/ecl/pull/765
First step is to copy in place as is, then we can incrementally refactor easily with the submodule gone.

@sfuhrer @RomanBapst once this is in let's refactor it in the style of mc_att_control/AttitudeControl and mc_rate_control/RateControl with unit tests.

What is keeping this PR from being merged? It concerns me if things just stop for a week. This makes the whole team really slow. We really need to be working on maximum 3-4 things at any given time, but get those things done and merged quickly.

What is keeping this PR from being merged?

In this particular case we got blocked by the yaw estimator (EKF-GSF) merging into PX4/ecl master before the required change here (https://github.com/PX4/ecl/pull/765).

Other ECL change is out of the way, rebasing this PR to get it in.


[6.0] NFC: Expose Environment with @_spi

Cherry-pick of #7780.
Explanation: Initializers for this type should be available via @_spi for clients to consume.
Scope: Limited to a single type and relevant initializers.
Risk: Very low, change is NFC.
Testing: Verified through existing test suite.
Issue: rdar://131407852
Reviewer: @bnbarham

@swift-ci test linux

@swift-ci test linux

@swift-ci test windows


Update iot-edge-certs.md

Device CA Certificate was not consistently renamed to Edge CA Certificate.

@LazaUK : Thanks for your contribution! The author(s) have been notified to review your proposed change.


not worked script

I  can  Install all   requirements.txt python 3.8
I can run:
python3.8 cansleep.py
File "cansleep.py" , line 206
match args.scanner:
^
SyntaxError: invalid syntax
??? not worked

Struct match/case used in python3.10 or higher.
You can upgrade python to 3.10 or change match/case to if/elif/else condition.

Thank you. Wokred on python 3.11


Update kafka sink maintainer

According to #1860

This change is

@Kokan  Thanks :)

@Kokan @miaoyq Would you guys help us to maintain kafka sink(answer questions and review PRs)?

Sorry for the reconfirm aside from #1860 . Thanks for taking care about kafka.
/lgtm
/cc @DirectXMan12 @loburm


Bump char limit on SearchBookmark URL

Fixes #2075

Coverage remained the same at 76.164% when pulling f08e6155b6a606ddfc98132fedf1b5917622871b on bump-searchbookmark-char-limit into c1f8292f141f11ad05a333bdad42b1c9a61b24db on master.


Component Request: ProgressIndicator

As title said,
like this: https://developer.microsoft.com/en-us/fluentui#/controls/web/progressindicator

+1 would like to see this added


feat(TemplateLibrary): add expand-collapse buttons - I80

Issue #80
Builds on https://github.com/accordproject/template-studio-v2/pull/92
Changes

Add expand button
Adds semantic react ui sidebar for pushable animation

Flags

Do we still want white hover background border? This involves being more and more custom with the sidebar.

Hi @tingaloo , Can you add the DCO sign-off and rebase / merge with master, please?

@tingaloo I previewed the deploy at this URL and the "hide" button looks like this:

Am I previewing it wrong? It looked more like this in previous iterations, right?

Adding on to @Michael-Grover's comment, this looks good so far! I think addressing the Hide button and making it fade to the right instead of left and we're really talkin here!

One question, I thought the hide button will be placed inside cicero-ui and will take props to update the look and feel?

@tingaloo oh right, yes. My mistake, I wasn't thinking correctly on this when I responded. Yes, I think the work will be in tandem with work in cicero-ui. @DianaLease thoughts?

@tingaloo oh right, yes. My mistake, I wasn't thinking correctly on this when I responded. Yes, I think the work will be in tandem with work in cicero-ui. @DianaLease thoughts?

Sounds reasonable to me. We'll also want to make sure that having the button is optional, since many users of cicero-ui probably will not need this show/hide functionality.

Closing as stale for now. Feel free to come back to it @tingaloo!


new challenge version

The current CloudflareUtilities does not manage to handle the new challenge version, presence of a s parameter in the get /cdn-cgi/l/chk_jschl:
/cdn-cgi/l/chk_jschl?s=xxxxxxx&jschl_vc=yyyyyyyyyyyyyy&pass=zzzzzzzzz&jschl_answer=eeeeeeeee
=> modification needed

Fixed that and made a pull request. Seems to need about 5 - 10 retries to pass.

Thanks Bleialf for #41

Happy to help! Awesome library!


Add support for a built-in datetime binding

Similar to our existing {rand-guid} binding which allows people to easily generate unique blob paths declaratively (e.g. path: "images/{rand-guid}") we should also support a datetime binding that allows people to bind to date/time strings.
This might look like {datetime:mm-dd-yyyy} allowing standard date/time format strings to be specified. So in your binding you can simply do:
{
  "type": "blob",
  "name": "myOutputBlob",
  "path": "outcontainer/{datetime:yyyy-mm-dd}",
  "connection": "function43dc41c29824_STORAGE",
  "direction": "out"
}

We should generalize this so the pattern is {name:format} allowing format strings to be specified. E.g. allow {datetime:yyyy-mm-dd} to be specified, or {rand-guid:G}.

@seanfeldman might also have benefited from this feature in his scenario