Datastore UI is not working with datastore in firestore mode

I am trying to make the UI work with datastore in firestore mode. This is my docker-compose.yaml
`version: "3.9"
services:
DSAdmin container
dsadmin:
image: "ghcr.io/remko/dsadmin:latest"
depends_on:
- datastore
ports:
- "3334:8080"
environment:
DATASTORE_PROJECT_ID: "project-dev"
DATASTORE_EMULATOR_HOST: "datastore:3333"
Datastore Emulator container
datastore:
image: "gcr.io/google.com/cloudsdktool/google-cloud-cli:latest"
volumes:
- datastore_data:/opt/datastore/data
ports:
- "3333:3333"
command: [
"gcloud", "emulators", "firestore", "start","--database-mode=datastore-mode", "--host-port=<IP_ADDRESS>:3333"
]
environment:
CLOUDSDK_CORE_PROJECT: "project-dev"
volumes:
datastore_data:
`
But for some reason I keep on getting this Error.

What can I do about it?

Good question. I have not tried the firestore emulator yet, I always use the datastore emulator.
From your error message, it sounds like it doesn't support the (metadata) queries that dsadmin does to list the namespaces and kinds available in the database. I would have to check whether there is a replacement for this in the firestore emulator.

Bumped into this as well, it looks like a limitation of the Firestore emulator in datastore mode,
[firestore] Jun 25, 2024 12:55:45 AM io.gapi.emulators.netty.HttpHandler$1 onError
[firestore] INFO: Exception when handling request: INVALID_ARGUMENT: Kind queries are not supported in the Datastore Mode emulator.

I could not find any docs stating this limitation though, nor any tickets on issuetracker.google.com.
I switched to the datastore emulator with the --use-firestore-in-datastore-mode flag on and it's working for my use case.

Thank you guys for your feedback.
The only issue I have is that I keep on getting the same error Filter has 4 properties, expected 1 whenever I try to use the IN filter. It seems that with firestore the issue is gone, and IN filtering works as expected.
This is also the solution Google is recommending for filtering.
@jmhobbs I tried now to use --use-firestore-in-datastore-mode such as:
DSAdmin container
dsadmin:
image: "ghcr.io/remko/dsadmin:latest"
depends_on:
- datastore
ports:
- "3334:8080"
environment:
DATASTORE_PROJECT_ID: "project-dev"
DATASTORE_EMULATOR_HOST: "datastore:3333"

Datastore Emulator container
datastore:
image: "gcr.io/google.com/cloudsdktool/google-cloud-cli:latest"
volumes:
- datastore_data:/opt/datastore/data
ports:
- "3333:3333"
command: [
"gcloud", "--quiet", "beta", "emulators", "datastore", "start", "--use-firestore-in-datastore-mode",
      "--no-store-on-disk", "--data-dir=/opt/datastore/data", "--host-port=<IP_ADDRESS>:3333"
]
environment:
CLOUDSDK_CORE_PROJECT: "project-dev"

volumes:
datastore_data:

And I keep getting the same error for IN filtering.

Does this work for you, or was this happening for you as well? How do you guys manage to do IN, !=, and NOT-IN queries?


feat(new validate flag): run  tests only for source changes

Hi @azlam-abdulsalam
i have decided to use a new flag because it seems that some modes uses the testclass execution.
The new flag is called --runtestagainstsource and depends on --basebranch
Please give my a sign when everything is fine then i can update the docs.
Checklist
All items have to be completed before a PR is merged

[x] Adhere to Contribution Guidelines
[ ] Updates to Decision Records considered?
[ ] Updates to documentation at flxbl-sfp Guide considered?
[ ] Tested changes?
[ ] Unit Tests new and existing passing locally?

This is addressed without a flag


Framed Follow Refactor

Issue description
The current implementation of Framed Follow has proven fairly fragile and doesn't quite deliver on what the feature set out to achieve. The issue stems from how it has been set up, and so needs a refactor to be more reliable and function the way you would expect it to.
Related issues
#144
#159
#107
Steps to reproduce
See example issue reports above.
(Optional) Minimal reproduction project
No response

Screencast from 2024-04-25 08-50-56.webm
I get a jitter in the example file iteself on a default settings project, Godot 4.2.2 on Debian 12 Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz. Hope this si the correct place to add this?
system_info.txt

Screencast from 2024-04-25 08-50-56.webm
I get a jitter in the example file iteself on a default settings project, Godot 4.2.2 on Debian 12 Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz. Hope this si the correct place to add this?
system_info.txt

This issue is not related to jitter, but rather some fundamental issues with the logic of how this follow mode works.
If you're on v0.7, then have a look at the FAQ for jitter related topics.

Not sure if it's the correct place to post this, but during the refactor would it make sense to extend framed to support an Array of targets similar to group?

Not sure if it's the correct place to post this, but during the refactor would it make sense to extend framed to support an Array of targets similar to group?

That would probably be for a different follow mode altogether, likely called Group Framed Follow. But that will not be considered for this issue. This issue raised in this post is about improving the underlying system of the Framed Follow itself.


Unable to bumpfee or abandon channel with stuck transaction

I opened a channel two weeks ago but only sent it with a fee of 1 sat/byte so it has been stuck on the mempool. I am unable to use bumpfee or abandonchannel to recover my funds.
When I use bumpfee I get this error: [lncli] rpc error: code = Unknown desc = the passed output does not belong to the wallet
and when I use abandonchannel I get this error: [lncli] rpc error: code = Unknown desc = unable to find closed channel summary
this is the transaction I sent: https://mempool.space/tx/1c46add0c928ff2a65c8d166dad7ad8979bee47d5d964bdc0d50688a56a9da38
How can I push the transaction through, or cancel it to recover my funds?
C:\Users\kiera>lncli pendingchannels
{
    "total_limbo_balance": "0",
    "pending_open_channels": [
    ],
    "pending_closing_channels": [
    ],
    "pending_force_closing_channels": [
    ],
    "waiting_close_channels": [
        {
            "channel": {
                "remote_node_pub": "03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f",
                "channel_point": "1c46add0c928ff2a65c8d166dad7ad8979bee47d5d964bdc0d50688a56a9da38:1",
                "capacity": "100000",
                "local_balance": "0",
                "remote_balance": "0",
                "local_chan_reserve_sat": "0",
                "remote_chan_reserve_sat": "0",
                "initiator": "INITIATOR_LOCAL",
                "commitment_type": "STATIC_REMOTE_KEY"
            },
            "limbo_balance": "0",
            "commitments": {
                "local_txid": "",
                "remote_txid": "",
                "remote_pending_txid": "",
                "local_commit_fee_sat": "0",
                "remote_commit_fee_sat": "0",
                "remote_pending_commit_fee_sat": "0"
            }
        }
    ]
}

I've somehow overwritten the original wallet files, so channel exists but has a value of 0 BTC. Bump fee didn't change anything so no idea what went wrong.

C:\Users\kiera>lncli walletbalance
{
    "total_balance": "0",
    "confirmed_balance": "0",
    "unconfirmed_balance": "0"
}

C:\Users\kiera>lncli listchaintxns
{
    "transactions": [
        {
            "tx_hash": "69d70d7314eac12fa8e78b1d23b6eccf09ec63f3ad8f467e86b3dbb7e571e119",
            "amount": "-23278",
            "num_confirmations": 85,
            "block_hash": "0000000000000000000cac26c19aeeef99a1ff214fe4dccd5dcc4c4b6b605192",
            "block_height": 674800,
            "time_stamp": "1615852105",
            "total_fees": "10057",
            "dest_addresses": [
                "3DbZpmwecQvCWfzDJyapN95WWmajm5HRDd"
            ],
            "raw_tx_hex": "020000000001014d8a4d7f36550493969d4886e877e0ca150aa8fedb5b3ecf416671b704ad5d2001000000000000000001a53300000000000017a9148299a49355027bf690d1c4eb7f094a7a856ab8ea8702483045022100f2453317f581cc17db1a0a9fc618c337da3244d1b62cfa32f50039207b548b570220425d0177e533d627a1feab353bf8460947415bab0366a7025bb5ddd49bbcfb8d012102e937c320d3191578ecdb64f3cb36c113c35eac5f7acb4b437843480dabe927bfef4b0a00",
            "label": "external"
        },
        {
            "tx_hash": "205dad04b7716641cf3e5bdbfea80a15cae077e886489d96930455367f4d8a4d",
            "amount": "23278",
            "num_confirmations": 266,
            "block_hash": "00000000000000000002c004ef0504c880d7d83dd9b5343000e8e3b71baa572b",
            "block_height": 674619,
            "time_stamp": "1615745588",
            "total_fees": "0",
            "dest_addresses": [
                "3BQyFtVykRHhJY4644rLrvR8f1Srw8En7n",
                "bc1q902qhtprdzt8saf3vzmwwv5mf5fs29fn2cds3w"
            ],
            "raw_tx_hex": "02000000000101db6dcdcd1b93835587935850a408dd071c4e4fae7c13b73ed630733b87976fd50000000017160014b1e192fa523ce2ba07663c56d202b8c78ece5cf7fdffffff029d5909000000000017a9146aa8606892847731f382791ff890700c3740cad887ee5a0000000000001600142bd40bac23689678753160b6e7329b4d1305153302483045022100d1904f3f673116d6c647cfd785ebdbd242503aa6709cc803c6e5a89b15fa9768022019fa7e8d8026e74b093874adf14997d666229feeebde4bddc724a173a466c830012102573a52ac4e238d9fe930400e35f930f9e49bb50464aa48f45276a07819bf1a1900000000",
            "label": ""
        }
    ]
}

Funds appeared in wallet after recovering wallet for a third time.


Explore CircleCI

A new tool fon continuous integration called CircleCI has been introduced by @altugcagri. This tool must be researched

New account on CircleCI has been created

Due to the busy workload, this will not be implemented


Extension cannot find projects inside Solution Folders

When a web project is inside a solution folder, the project is not found by the extension.

Thanks for that report! I will definitely take a look.

Fixed! Will post v.0.9.9 to the marketplace in just a few.


add 'information on putatively essential gene'

Closes #367. Using this label because we decided to create this term as an ICE.
Edit: I don't know why the diff looks weird, but you can see the new term if you search for "FungiDB".
Edit2: looks fine when I use git show -w

Also changed label to include "conclusion".


Use this to replace default service-worker.js file?

Hi, I can see that you've intended this tool to be used to append code onto the service-worker.js file provided by the cra build.
I'm curious to know whether I can use this tool to replace the service-worker.js file entirely and replace it with my custom one?

@redixhumayun I've added a new output mode replace that should do what you are asking for. Make sure you are using v2.2.0 and lemme know if it's ok.

Brilliant! Love your tool btw! I'm amazed it hasn't received more attention considering how ridiculously complex it is to edit or create a service worker with the CRA build.

Out of curiosity, do you know if its possible to run the service worker file from the dev environment? I know cra has a no-op file for the dev environment, is there a way to override that?

@redixhumayun It should be possible if you tinker with registerServiceWorker.js file. You should be able to disable "production" only condition there.


nautilus lacks (runtime) dependency on sgdisk

Issue description
If you right click on a device in nautilus and select "Format", fill inn the following form and press "go" (or whatever it's called), you'll be presented with an error message indicating that sgdisk is missing and the operation fails.

As this the format operation clearly is a built-in functionality of nautilus, we should ensure that it works out of the box.
EDIT: added screenshot.
Technical details

System: NixOS 16.09

(triage) can you still reproduce?

The feature seems to work on NixOS 18.03.


Consider adding WebAssembly backend

Maybe not immediately, but at some point it might be interesting to start working on a backend for the WebAssembly (wasm) language. There are plans to add GC support in the future.

What advantages do you imagine relative to the existing JavaScript backend?

speed
a lot of more freedom for the backend on how to store information.


Fix npm import not working

After installing filtering.js from npm, it should be easily possible to import the library and classes.
import filteringjs from<EMAIL_ADDRESS>
import filteringjs from<EMAIL_ADDRESS>
import filteringjs from<EMAIL_ADDRESS>
import {Filter, Group} from<EMAIL_ADDRESS>
import {FilteringFlow} from<EMAIL_ADDRESS>

Closed by https://github.com/filteringjs/filtering.js/commit/484154b67195b78e91d3b23201cfb0dc6857086a


change default role to member, remove provider_admin

remove provider_admin user in favor of admin
remove customization flag

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Will review later.

ok to test

This will obviously have docs impact, as well as upgrade implications.


Console Spam

I am unsure if this is IC2 or Refined Storage, but I am getting a lot of console spam.
http://pastebin.com/RzLpdd2m
If you need more information please let me know.

On which version are you?

(RS version)

0.8.18

Just to give a little more information.
This is occurring with:
Forge: 2065
Refined Storage:  0.8.19
Minecraft: 1.10.2
I may troubleshoot this some with a new world to see if it still occurs.

Does this still occur on the latest IC2 / RS?

I'm assuming this is fixed?


Current build has renderer calls stripped out so drag classes are not working

Describe the bug
Dev console:

There should be a renderer call here:
https://github.com/mattlewis92/angular-draggable-droppable/blob/master/projects/angular-draggable-droppable/src/lib/droppable.directive.ts#L149-L152
Diving into the build has the same issue:

Minimal reproduction of the problem with instructions
https://stackblitz.com/edit/angular-tubww6?file=src%2Fapp%2Fapp.component.html
Screenshots

Versions

@angular/core: 6.1.2
angular-draggable-droppable: 3.0.1
Browser name and version: Chrome Version 68.0.3440.106 (Official Build) (64-bit)

@mattlewis92  Looks like you introduced the drag classes recently. Will you be dropping a release soon?

Sorry for the confusion, what's on master is 4.x, if you do
npm i angular-draggable-droppable@beta

It should fix all your issues, the plan is to release 4.x final once https://github.com/mattlewis92/angular-draggable-droppable/issues/50 is done

Yep, I just went with
<div class="mmds-c-page__dropzone"
  mwlDroppable [class.mmds-c-page__dropzone--active]="bottom.active"
  #bottom (dragEnter)="bottom.active = true"
  (dragLeave)="bottom.active = false"
  (drop)="bottom.active = false; _addBottom( $event.dropData )">

</div>

in the meanwhile...


Problem with font changer on chatterino 7.3.5 (7tv fork)

Checklist

[X] I'm reporting a problem with Chatterino
[X] I've verified that I'm running the most recent nightly build or stable release
[X] I've looked for my problem on the wiki
[X] I've searched the issues and pull requests for similar looking reports

Describe your issue
hello, i'm not great with computers and software and whatnot but recently ive been trying to change the font for chatterino by using the integrated font picker menu thing. the issue is that when i open the menu by clicking "Choose..." in the fonts dropdown box, the window doesn't open. i have all the redistributables and everything seems to be working fine in every other aspect of chatterino, is this just a resolution problem with the menu and it is opening very small? or am i just being dumb and theres some easy problem i am missing. Thanks,
Rodos
Screenshots
No response
OS and Chatterino Version
Chatterino 7.3.5 | Windows 10 Home

Oh my bad, i apologise for that. I’ll try getting a hold of 7TV
On Tue, 12 Apr 2022 at 15:29, Kasia @.***> wrote:

this isn't a repository for 7tv fork, we don't support it here.
—
Reply to this email directly, view it on GitHub
https://github.com/Chatterino/chatterino2/issues/3672#issuecomment-1096805094,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYVG3SKLN4J2LKSWYJU3G4LVEWCGFANCNFSM5THODUTQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Can replicate on normal chatterino


[question] How to use it ?

Hello,
Sorry if my question seems stupid, but despite the readme which explains well how to setup and configure ng2-redux-router in a ng2 app, I simply can't figure out how to use it !
What I want to do is to make a redirection after a http post in an action creator service. I thought I could find an practical case in the example folder, but there's nothing.
Thx for guiding me

Well my question is even more stupid... "why would you use it"?
No seriously, I am trying to understand this lib and why it exists.
So this lib will allow you to listen to route changes from the store?
I am not sure why would one need this pattern? Am I missing something?
You can just DI and listen to routes via observales inside ng2
regards,
Sean.

@born2net if you don't see a use case for it, don't use it :) Its not needed in any way for redux to function. However, some apps may need to have the current router location in the state so actions can have different results depending on where the user is. The reason I made this is because I don't like to spread the state into different containers (both redux and router), and prefer to keep the state in one place, in this case, the redux store. As a sidenote, this also enables functionality such as time travel to work with the router as well, since the router location always stays in sync with the store location, this can in some cases make debugging easier. Did this answer your question?
@supertino7 the README.md specifies how to set it up. Can you be more specific as to what you are struggling with? The library doesnt really require a lot of "use", since its main job is to sync the state in redux with the router-state. If you want to do a redirection after an HTTP POST you should inject the router in the action creator service and use the router to redirect.

@dagstuan I fully understand (didn't mean to sound condescending) and this is a great explanation.
I actually recommend you add that do the front page readme.md
tx again,
Sean.


Demo styles

Hey there!
Love JCF and using it in another project. Keen to get my hands on more "themes"
Where can I get my hands on the demo theme?
Cheers

Sorry, no additional themes. Actually there aren't any active maintainer in this repo. Sorry


Add missing React & JSX eslint rules

Also changing the peerDependencies back to using caret syntax since it's possible that we'll add new rules not available in previous versions of packages

🚢


Need help! i follow the installation instruction, alot of error mentioned "No such file or directory"

Hi, i really need help, i spent whole week, still unable to use this, install this install that, still cannot working, keep came out the file error, not found error, or not able to proceed..... i need a clear installation guide or video tutorial please...

Yes, I am also facing the same dependencies installation issues, from almost a week unable to do the complete installation, file not found error
sharing one of the log file
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Collecting tensorboard==2.13.0
Using cached tensorboard-2.13.0-py3-none-any.whl (5.6 MB)
Collecting tensorboardX==2.6.1
Using cached tensorboardX-2.6.1-py2.py3-none-any.whl (101 kB)
Requirement already satisfied: absl-py>=0.4 in /usr/local/lib/python3.10/dist-packages (from tensorboard==2.13.0) (1.4.0)
Requirement already satisfied: grpcio>=1.48.2 in /usr/local/lib/python3.10/dist-packages (from tensorboard==2.13.0) (1.62.1)
Requirement already satisfied: google-auth<3,>=1.6.3 in /usr/local/lib/python3.10/dist-packages (from tensorboard==2.13.0) (2.27.0)
Collecting google-auth-oauthlib<1.1,>=0.5 (from tensorboard==2.13.0)
Using cached google_auth_oauthlib-1.0.0-py2.py3-none-any.whl (18 kB)
Requirement already satisfied: markdown>=2.6.8 in /usr/local/lib/python3.10/dist-packages (from tensorboard==2.13.0) (3.6)
Requirement already satisfied: numpy>=1.12.0 in /usr/local/lib/python3.10/dist-packages (from tensorboard==2.13.0) (1.25.2)
Requirement already satisfied: protobuf>=3.19.6 in /usr/local/lib/python3.10/dist-packages (from tensorboard==2.13.0) (3.20.3)
Requirement already satisfied: requests<3,>=2.21.0 in /usr/local/lib/python3.10/dist-packages (from tensorboard==2.13.0) (2.28.2)
Requirement already satisfied: setuptools>=41.0.0 in /usr/local/lib/python3.10/dist-packages (from tensorboard==2.13.0) (60.2.0)
Requirement already satisfied: tensorboard-data-server<0.8.0,>=0.7.0 in /usr/local/lib/python3.10/dist-packages (from tensorboard==2.13.0) (0.7.2)
Requirement already satisfied: werkzeug>=1.0.1 in /usr/local/lib/python3.10/dist-packages (from tensorboard==2.13.0) (3.0.2)
Requirement already satisfied: wheel>=0.26 in /usr/local/lib/python3.10/dist-packages (from tensorboard==2.13.0) (0.43.0)
Requirement already satisfied: packaging in /usr/local/lib/python3.10/dist-packages (from tensorboardX==2.6.1) (24.0)
Collecting protobuf>=3.19.6 (from tensorboard==2.13.0)
Using cached protobuf-5.26.1-cp37-abi3-manylinux2014_x86_64.whl (302 kB)
Requirement already satisfied: cachetools<6.0,>=2.0.0 in /usr/local/lib/python3.10/dist-packages (from google-auth<3,>=1.6.3->tensorboard==2.13.0) (5.3.3)
Requirement already satisfied: pyasn1-modules>=0.2.1 in /usr/local/lib/python3.10/dist-packages (from google-auth<3,>=1.6.3->tensorboard==2.13.0) (0.4.0)
Requirement already satisfied: rsa<5,>=3.1.4 in /usr/local/lib/python3.10/dist-packages (from google-auth<3,>=1.6.3->tensorboard==2.13.0) (4.9)
Requirement already satisfied: requests-oauthlib>=0.7.0 in /usr/local/lib/python3.10/dist-packages (from google-auth-oauthlib<1.1,>=0.5->tensorboard==2.13.0) (1.3.1)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.10/dist-packages (from requests<3,>=2.21.0->tensorboard==2.13.0) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.10/dist-packages (from requests<3,>=2.21.0->tensorboard==2.13.0) (3.6)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.10/dist-packages (from requests<3,>=2.21.0->tensorboard==2.13.0) (1.26.18)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.10/dist-packages (from requests<3,>=2.21.0->tensorboard==2.13.0) (2024.2.2)
Requirement already satisfied: MarkupSafe>=2.1.1 in /usr/local/lib/python3.10/dist-packages (from werkzeug>=1.0.1->tensorboard==2.13.0) (2.1.5)
Requirement already satisfied: pyasn1<0.7.0,>=0.4.6 in /usr/local/lib/python3.10/dist-packages (from pyasn1-modules>=0.2.1->google-auth<3,>=1.6.3->tensorboard==2.13.0) (0.6.0)
Requirement already satisfied: oauthlib>=3.0.0 in /usr/local/lib/python3.10/dist-packages (from requests-oauthlib>=0.7.0->google-auth-oauthlib<1.1,>=0.5->tensorboard==2.13.0) (3.2.2)
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Installing collected packages: protobuf, tensorboardX, google-auth-oauthlib, tensorboard
Attempting uninstall: protobuf
Found existing installation: protobuf 3.20.3
Uninstalling protobuf-3.20.3:
Successfully uninstalled protobuf-3.20.3
Attempting uninstall: google-auth-oauthlib
Found existing installation: google-auth-oauthlib 1.2.0
Uninstalling google-auth-oauthlib-1.2.0:
Successfully uninstalled google-auth-oauthlib-1.2.0
Attempting uninstall: tensorboard
Found existing installation: tensorboard 2.15.2
Uninstalling tensorboard-2.15.2:
Successfully uninstalled tensorboard-2.15.2
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
google-ai-generativelanguage 0.4.0 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-api-core 2.11.1 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0.dev0,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-cloud-aiplatform 1.46.0 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-cloud-bigquery 3.12.0 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-cloud-bigquery-connection 1.12.1 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-cloud-bigquery-storage 2.24.0 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-cloud-datastore 2.15.2 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-cloud-firestore 2.11.1 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-cloud-functions 1.13.3 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-cloud-iam 2.14.3 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-cloud-language 2.13.3 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-cloud-resource-manager 1.12.3 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
google-cloud-translate 3.11.3 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
googleapis-common-protos 1.63.0 requires protobuf!=3.20.0,!=3.20.1,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0.dev0,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
grpc-google-iam-v1 0.13.0 requires protobuf!=3.20.0,!=3.20.1,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 5.26.1 which is incompatible.
mediapipe 0.10.7 requires protobuf<4,>=3.11, but you have protobuf 5.26.1 which is incompatible.
proto-plus 1.23.0 requires protobuf<5.0.0dev,>=3.19.0, but you have protobuf 5.26.1 which is incompatible.
tensorflow 2.15.0 requires protobuf!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.20.3, but you have protobuf 5.26.1 which is incompatible.
tensorflow 2.15.0 requires tensorboard<2.16,>=2.15, but you have tensorboard 2.13.0 which is incompatible.
tensorflow-metadata 1.14.0 requires protobuf<4.21,>=3.20.3, but you have protobuf 5.26.1 which is incompatible.
Successfully installed google-auth-oauthlib-1.0.0 protobuf-5.26.1 tensorboard-2.13.0 tensorboardX-2.6.1
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Collecting pyspy==0.1.1
Using cached pyspy-0.1.1.tar.gz (1.8 kB)
Preparing metadata (setup.py) ... done
Building wheels for collected packages: pyspy
Building wheel for pyspy (setup.py) ... done
Created wheel for pyspy: filename=pyspy-0.1.1-py3-none-any.whl size=2064 sha256=dd3cd0a72f3bc5e60b08813dbee3930bd6f3b49546143abb98a466940a4b735a
Stored in directory: /root/.cache/pip/wheels/88/28/42/a86592a71ad8063361ee7bb19d3ccefd330c1bdd94cdaed663
Successfully built pyspy
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Installing collected packages: pyspy
Successfully installed pyspy-0.1.1
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Collecting protobuf==3.20.3
Downloading protobuf-3.20.3-cp310-cp310-manylinux_2_12_x86_64.manylinux2010_x86_64.whl (1.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 6.6 MB/s eta 0:00:00
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Installing collected packages: protobuf
Attempting uninstall: protobuf
Found existing installation: protobuf 5.26.1
Uninstalling protobuf-5.26.1:
Successfully uninstalled protobuf-5.26.1
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
tensorboardx 2.6.1 requires protobuf>=4.22.3, but you have protobuf 3.20.3 which is incompatible.
tensorflow 2.15.0 requires tensorboard<2.16,>=2.15, but you have tensorboard 2.13.0 which is incompatible.
Successfully installed protobuf-3.20.3
WARNING: The following packages were previously imported in this runtime:
[google]
You must restart the runtime in order to use newly installed versions.
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Collecting scipy==1.9.1
Downloading scipy-1.9.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (43.9 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 43.9/43.9 MB 17.6 MB/s eta 0:00:00
Collecting numpy<1.25.0,>=1.18.5 (from scipy==1.9.1)
Downloading numpy-1.24.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (17.3 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 17.3/17.3 MB 40.4 MB/s eta 0:00:00
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Installing collected packages: numpy, scipy
Attempting uninstall: numpy
Found existing installation: numpy 1.25.2
Uninstalling numpy-1.25.2:
Successfully uninstalled numpy-1.25.2
Attempting uninstall: scipy
Found existing installation: scipy 1.11.4
Uninstalling scipy-1.11.4:
Successfully uninstalled scipy-1.11.4
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
cvxpy 1.3.3 requires setuptools>65.5.1, but you have setuptools 60.2.0 which is incompatible.
pandas-stubs <IP_ADDRESS>814 requires numpy>=1.25.0; python_version >= "3.9", but you have numpy 1.24.4 which is incompatible.
tensorboardx 2.6.1 requires protobuf>=4.22.3, but you have protobuf 3.20.3 which is incompatible.
tensorflow 2.15.0 requires tensorboard<2.16,>=2.15, but you have tensorboard 2.13.0 which is incompatible.
yfinance 0.2.37 requires requests>=2.31, but you have requests 2.28.2 which is incompatible.
Successfully installed numpy-1.24.4 scipy-1.9.1
WARNING: The following packages were previously imported in this runtime:
[numpy]
You must restart the runtime in order to use newly installed versions.
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Collecting kornia==0.5.0
Using cached kornia-0.5.0-py2.py3-none-any.whl (271 kB)
Requirement already satisfied: numpy in /usr/local/lib/python3.10/dist-packages (from kornia==0.5.0) (1.24.4)
Requirement already satisfied: torch>=1.6.0 in /usr/local/lib/python3.10/dist-packages (from kornia==0.5.0) (2.2.1+cu121)
Requirement already satisfied: filelock in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (3.13.3)
Requirement already satisfied: typing-extensions>=4.8.0 in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (4.10.0)
Requirement already satisfied: sympy in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (1.12)
Requirement already satisfied: networkx in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (3.2.1)
Requirement already satisfied: jinja2 in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (3.1.3)
Requirement already satisfied: fsspec in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (2023.6.0)
Requirement already satisfied: nvidia-cuda-nvrtc-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (12.1.105)
Requirement already satisfied: nvidia-cuda-runtime-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (12.1.105)
Requirement already satisfied: nvidia-cuda-cupti-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (12.1.105)
Requirement already satisfied: nvidia-cudnn-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cublas-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cufft-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-curand-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusolver-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusparse-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-nccl-cu12==2.19.3 in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (2.19.3)
Requirement already satisfied: nvidia-nvtx-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (12.1.105)
Requirement already satisfied: triton==2.2.0 in /usr/local/lib/python3.10/dist-packages (from torch>=1.6.0->kornia==0.5.0) (2.2.0)
Requirement already satisfied: nvidia-nvjitlink-cu12 in /usr/local/lib/python3.10/dist-packages (from nvidia-cusolver-cu12==<IP_ADDRESS>->torch>=1.6.0->kornia==0.5.0) (12.4.127)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.10/dist-packages (from jinja2->torch>=1.6.0->kornia==0.5.0) (2.1.5)
Requirement already satisfied: mpmath>=0.19 in /usr/local/lib/python3.10/dist-packages (from sympy->torch>=1.6.0->kornia==0.5.0) (1.3.0)
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Installing collected packages: kornia
Successfully installed kornia-0.5.0
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Collecting trimesh==3.22.0
Downloading trimesh-3.22.0-py3-none-any.whl (681 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 681.5/681.5 kB 3.8 MB/s eta 0:00:00
Requirement already satisfied: numpy in /usr/local/lib/python3.10/dist-packages (from trimesh==3.22.0) (1.24.4)
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Installing collected packages: trimesh
Successfully installed trimesh-3.22.0
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Requirement already satisfied: einops==0.6.1 in /usr/local/lib/python3.10/dist-packages (0.6.1)
Requirement already satisfied: torchshow==0.5.1 in /usr/local/lib/python3.10/dist-packages (0.5.1)
Requirement already satisfied: numpy in /usr/local/lib/python3.10/dist-packages (from torchshow==0.5.1) (1.24.4)
Requirement already satisfied: matplotlib in /usr/local/lib/python3.10/dist-packages (from torchshow==0.5.1) (3.7.1)
Requirement already satisfied: contourpy>=1.0.1 in /usr/local/lib/python3.10/dist-packages (from matplotlib->torchshow==0.5.1) (1.2.1)
Requirement already satisfied: cycler>=0.10 in /usr/local/lib/python3.10/dist-packages (from matplotlib->torchshow==0.5.1) (0.12.1)
Requirement already satisfied: fonttools>=4.22.0 in /usr/local/lib/python3.10/dist-packages (from matplotlib->torchshow==0.5.1) (4.50.0)
Requirement already satisfied: kiwisolver>=1.0.1 in /usr/local/lib/python3.10/dist-packages (from matplotlib->torchshow==0.5.1) (1.4.5)
Requirement already satisfied: packaging>=20.0 in /usr/local/lib/python3.10/dist-packages (from matplotlib->torchshow==0.5.1) (24.0)
Requirement already satisfied: pillow>=6.2.0 in /usr/local/lib/python3.10/dist-packages (from matplotlib->torchshow==0.5.1) (9.4.0)
Requirement already satisfied: pyparsing>=2.3.1 in /usr/local/lib/python3.10/dist-packages (from matplotlib->torchshow==0.5.1) (3.1.2)
Requirement already satisfied: python-dateutil>=2.7 in /usr/local/lib/python3.10/dist-packages (from matplotlib->torchshow==0.5.1) (2.8.2)
Requirement already satisfied: six>=1.5 in /usr/local/lib/python3.10/dist-packages (from python-dateutil>=2.7->matplotlib->torchshow==0.5.1) (1.16.0)
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Collecting imageio==2.31.1
Using cached imageio-2.31.1-py3-none-any.whl (313 kB)
Requirement already satisfied: imageio-ffmpeg==0.4.8 in /usr/local/lib/python3.10/dist-packages (0.4.8)
Requirement already satisfied: numpy in /usr/local/lib/python3.10/dist-packages (from imageio==2.31.1) (1.24.4)
Requirement already satisfied: pillow>=8.3.2 in /usr/local/lib/python3.10/dist-packages (from imageio==2.31.1) (9.4.0)
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Installing collected packages: imageio
Attempting uninstall: imageio
Found existing installation: imageio 2.34.0
Uninstalling imageio-2.34.0:
Successfully uninstalled imageio-2.34.0
Successfully installed imageio-2.31.1
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Collecting scikit-learn==1.3.0
Using cached scikit_learn-1.3.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (10.8 MB)
Collecting scikit-image==0.21.0
Using cached scikit_image-0.21.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (13.8 MB)
Requirement already satisfied: numpy>=1.17.3 in /usr/local/lib/python3.10/dist-packages (from scikit-learn==1.3.0) (1.24.4)
Requirement already satisfied: scipy>=1.5.0 in /usr/local/lib/python3.10/dist-packages (from scikit-learn==1.3.0) (1.9.1)
Requirement already satisfied: joblib>=1.1.1 in /usr/local/lib/python3.10/dist-packages (from scikit-learn==1.3.0) (1.3.2)
Requirement already satisfied: threadpoolctl>=2.0.0 in /usr/local/lib/python3.10/dist-packages (from scikit-learn==1.3.0) (3.4.0)
Requirement already satisfied: networkx>=2.8 in /usr/local/lib/python3.10/dist-packages (from scikit-image==0.21.0) (3.2.1)
Requirement already satisfied: pillow>=9.0.1 in /usr/local/lib/python3.10/dist-packages (from scikit-image==0.21.0) (9.4.0)
Requirement already satisfied: imageio>=2.27 in /usr/local/lib/python3.10/dist-packages (from scikit-image==0.21.0) (2.31.1)
Requirement already satisfied: tifffile>=2022.8.12 in /usr/local/lib/python3.10/dist-packages (from scikit-image==0.21.0) (2024.2.12)
Requirement already satisfied: PyWavelets>=1.1.1 in /usr/local/lib/python3.10/dist-packages (from scikit-image==0.21.0) (1.6.0)
Requirement already satisfied: packaging>=21 in /usr/local/lib/python3.10/dist-packages (from scikit-image==0.21.0) (24.0)
Requirement already satisfied: lazy_loader>=0.2 in /usr/local/lib/python3.10/dist-packages (from scikit-image==0.21.0) (0.3)
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Installing collected packages: scikit-learn, scikit-image
Attempting uninstall: scikit-learn
Found existing installation: scikit-learn 1.2.2
Uninstalling scikit-learn-1.2.2:
Successfully uninstalled scikit-learn-1.2.2
Attempting uninstall: scikit-image
Found existing installation: scikit-image 0.19.3
Uninstalling scikit-image-0.19.3:
Successfully uninstalled scikit-image-0.19.3
Successfully installed scikit-image-0.21.0 scikit-learn-1.3.0
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Requirement already satisfied: av==10.0.0 in /usr/local/lib/python3.10/dist-packages (10.0.0)
Collecting lpips==0.1.4
Using cached lpips-0.1.4-py3-none-any.whl (53 kB)
Requirement already satisfied: torch>=0.4.0 in /usr/local/lib/python3.10/dist-packages (from lpips==0.1.4) (2.2.1+cu121)
Requirement already satisfied: torchvision>=0.2.1 in /usr/local/lib/python3.10/dist-packages (from lpips==0.1.4) (0.17.1+cu121)
Requirement already satisfied: numpy>=1.14.3 in /usr/local/lib/python3.10/dist-packages (from lpips==0.1.4) (1.24.4)
Requirement already satisfied: scipy>=1.0.1 in /usr/local/lib/python3.10/dist-packages (from lpips==0.1.4) (1.9.1)
Requirement already satisfied: tqdm>=4.28.1 in /usr/local/lib/python3.10/dist-packages (from lpips==0.1.4) (4.65.2)
Requirement already satisfied: filelock in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (3.13.3)
Requirement already satisfied: typing-extensions>=4.8.0 in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (4.10.0)
Requirement already satisfied: sympy in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (1.12)
Requirement already satisfied: networkx in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (3.2.1)
Requirement already satisfied: jinja2 in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (3.1.3)
Requirement already satisfied: fsspec in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (2023.6.0)
Requirement already satisfied: nvidia-cuda-nvrtc-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (12.1.105)
Requirement already satisfied: nvidia-cuda-runtime-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (12.1.105)
Requirement already satisfied: nvidia-cuda-cupti-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (12.1.105)
Requirement already satisfied: nvidia-cudnn-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cublas-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cufft-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-curand-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusolver-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusparse-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-nccl-cu12==2.19.3 in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (2.19.3)
Requirement already satisfied: nvidia-nvtx-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (12.1.105)
Requirement already satisfied: triton==2.2.0 in /usr/local/lib/python3.10/dist-packages (from torch>=0.4.0->lpips==0.1.4) (2.2.0)
Requirement already satisfied: nvidia-nvjitlink-cu12 in /usr/local/lib/python3.10/dist-packages (from nvidia-cusolver-cu12==<IP_ADDRESS>->torch>=0.4.0->lpips==0.1.4) (12.4.127)
Requirement already satisfied: pillow!=8.3.,>=5.3.0 in /usr/local/lib/python3.10/dist-packages (from torchvision>=0.2.1->lpips==0.1.4) (9.4.0)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.10/dist-packages (from jinja2->torch>=0.4.0->lpips==0.1.4) (2.1.5)
Requirement already satisfied: mpmath>=0.19 in /usr/local/lib/python3.10/dist-packages (from sympy->torch>=0.4.0->lpips==0.1.4) (1.3.0)
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Installing collected packages: lpips
Successfully installed lpips-0.1.4
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Requirement already satisfied: timm==0.9.2 in /usr/local/lib/python3.10/dist-packages (0.9.2)
Requirement already satisfied: librosa==0.9.2 in /usr/local/lib/python3.10/dist-packages (0.9.2)
Requirement already satisfied: torch>=1.7 in /usr/local/lib/python3.10/dist-packages (from timm==0.9.2) (2.2.1+cu121)
Requirement already satisfied: torchvision in /usr/local/lib/python3.10/dist-packages (from timm==0.9.2) (0.17.1+cu121)
Requirement already satisfied: pyyaml in /usr/local/lib/python3.10/dist-packages (from timm==0.9.2) (6.0.1)
Requirement already satisfied: huggingface-hub in /usr/local/lib/python3.10/dist-packages (from timm==0.9.2) (0.20.3)
Requirement already satisfied: safetensors in /usr/local/lib/python3.10/dist-packages (from timm==0.9.2) (0.4.2)
Requirement already satisfied: audioread>=2.1.9 in /usr/local/lib/python3.10/dist-packages (from librosa==0.9.2) (3.0.1)
Requirement already satisfied: numpy>=1.17.0 in /usr/local/lib/python3.10/dist-packages (from librosa==0.9.2) (1.24.4)
Requirement already satisfied: scipy>=1.2.0 in /usr/local/lib/python3.10/dist-packages (from librosa==0.9.2) (1.9.1)
Requirement already satisfied: scikit-learn>=0.19.1 in /usr/local/lib/python3.10/dist-packages (from librosa==0.9.2) (1.3.0)
Requirement already satisfied: joblib>=0.14 in /usr/local/lib/python3.10/dist-packages (from librosa==0.9.2) (1.3.2)
Requirement already satisfied: decorator>=4.0.10 in /usr/local/lib/python3.10/dist-packages (from librosa==0.9.2) (4.4.2)
Requirement already satisfied: resampy>=0.2.2 in /usr/local/lib/python3.10/dist-packages (from librosa==0.9.2) (0.4.3)
Requirement already satisfied: numba>=0.45.1 in /usr/local/lib/python3.10/dist-packages (from librosa==0.9.2) (0.58.1)
Requirement already satisfied: soundfile>=0.10.2 in /usr/local/lib/python3.10/dist-packages (from librosa==0.9.2) (0.12.1)
Requirement already satisfied: pooch>=1.0 in /usr/local/lib/python3.10/dist-packages (from librosa==0.9.2) (1.8.1)
Requirement already satisfied: packaging>=20.0 in /usr/local/lib/python3.10/dist-packages (from librosa==0.9.2) (24.0)
Requirement already satisfied: llvmlite<0.42,>=0.41.0dev0 in /usr/local/lib/python3.10/dist-packages (from numba>=0.45.1->librosa==0.9.2) (0.41.1)
Requirement already satisfied: platformdirs>=2.5.0 in /usr/local/lib/python3.10/dist-packages (from pooch>=1.0->librosa==0.9.2) (4.2.0)
Requirement already satisfied: requests>=2.19.0 in /usr/local/lib/python3.10/dist-packages (from pooch>=1.0->librosa==0.9.2) (2.28.2)
Requirement already satisfied: threadpoolctl>=2.0.0 in /usr/local/lib/python3.10/dist-packages (from scikit-learn>=0.19.1->librosa==0.9.2) (3.4.0)
Requirement already satisfied: cffi>=1.0 in /usr/local/lib/python3.10/dist-packages (from soundfile>=0.10.2->librosa==0.9.2) (1.16.0)
Requirement already satisfied: filelock in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (3.13.3)
Requirement already satisfied: typing-extensions>=4.8.0 in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (4.10.0)
Requirement already satisfied: sympy in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (1.12)
Requirement already satisfied: networkx in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (3.2.1)
Requirement already satisfied: jinja2 in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (3.1.3)
Requirement already satisfied: fsspec in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (2023.6.0)
Requirement already satisfied: nvidia-cuda-nvrtc-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (12.1.105)
Requirement already satisfied: nvidia-cuda-runtime-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (12.1.105)
Requirement already satisfied: nvidia-cuda-cupti-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (12.1.105)
Requirement already satisfied: nvidia-cudnn-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cublas-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cufft-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-curand-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusolver-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusparse-cu12==<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-nccl-cu12==2.19.3 in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (2.19.3)
Requirement already satisfied: nvidia-nvtx-cu12==12.1.105 in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (12.1.105)
Requirement already satisfied: triton==2.2.0 in /usr/local/lib/python3.10/dist-packages (from torch>=1.7->timm==0.9.2) (2.2.0)
Requirement already satisfied: nvidia-nvjitlink-cu12 in /usr/local/lib/python3.10/dist-packages (from nvidia-cusolver-cu12==<IP_ADDRESS>->torch>=1.7->timm==0.9.2) (12.4.127)
Requirement already satisfied: tqdm>=4.42.1 in /usr/local/lib/python3.10/dist-packages (from huggingface-hub->timm==0.9.2) (4.65.2)
Requirement already satisfied: pillow!=8.3.,>=5.3.0 in /usr/local/lib/python3.10/dist-packages (from torchvision->timm==0.9.2) (9.4.0)
Requirement already satisfied: pycparser in /usr/local/lib/python3.10/dist-packages (from cffi>=1.0->soundfile>=0.10.2->librosa==0.9.2) (2.22)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.10/dist-packages (from requests>=2.19.0->pooch>=1.0->librosa==0.9.2) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.10/dist-packages (from requests>=2.19.0->pooch>=1.0->librosa==0.9.2) (3.6)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.10/dist-packages (from requests>=2.19.0->pooch>=1.0->librosa==0.9.2) (1.26.18)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.10/dist-packages (from requests>=2.19.0->pooch>=1.0->librosa==0.9.2) (2024.2.2)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.10/dist-packages (from jinja2->torch>=1.7->timm==0.9.2) (2.1.5)
Requirement already satisfied: mpmath>=0.19 in /usr/local/lib/python3.10/dist-packages (from sympy->torch>=1.7->timm==0.9.2) (1.3.0)
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)
Requirement already satisfied: openmim==0.3.9 in /usr/local/lib/python3.10/dist-packages (0.3.9)
Requirement already satisfied: Click in /usr/local/lib/python3.10/dist-packages (from openmim==0.3.9) (8.1.7)
Requirement already satisfied: colorama in /usr/local/lib/python3.10/dist-packages (from openmim==0.3.9) (0.4.6)
Requirement already satisfied: model-index in /usr/local/lib/python3.10/dist-packages (from openmim==0.3.9) (0.1.11)
Requirement already satisfied: opendatalab in /usr/local/lib/python3.10/dist-packages (from openmim==0.3.9) (0.0.10)
Requirement already satisfied: pandas in /usr/local/lib/python3.10/dist-packages (from openmim==0.3.9) (2.1.3)
Requirement already satisfied: pip>=19.3 in /usr/local/lib/python3.10/dist-packages (from openmim==0.3.9) (23.1.2)
Requirement already satisfied: requests in /usr/local/lib/python3.10/dist-packages (from openmim==0.3.9) (2.28.2)
Requirement already satisfied: rich in /usr/local/lib/python3.10/dist-packages (from openmim==0.3.9) (13.4.2)
Requirement already satisfied: tabulate in /usr/local/lib/python3.10/dist-packages (from openmim==0.3.9) (0.9.0)
Requirement already satisfied: pyyaml in /usr/local/lib/python3.10/dist-packages (from model-index->openmim==0.3.9) (6.0.1)
Requirement already satisfied: markdown in /usr/local/lib/python3.10/dist-packages (from model-index->openmim==0.3.9) (3.6)
Requirement already satisfied: ordered-set in /usr/local/lib/python3.10/dist-packages (from model-index->openmim==0.3.9) (4.1.0)
Requirement already satisfied: pycryptodome in /usr/local/lib/python3.10/dist-packages (from opendatalab->openmim==0.3.9) (3.20.0)
Requirement already satisfied: tqdm in /usr/local/lib/python3.10/dist-packages (from opendatalab->openmim==0.3.9) (4.65.2)
Requirement already satisfied: openxlab in /usr/local/lib/python3.10/dist-packages (from opendatalab->openmim==0.3.9) (0.0.37)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.10/dist-packages (from requests->openmim==0.3.9) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.10/dist-packages (from requests->openmim==0.3.9) (3.6)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.10/dist-packages (from requests->openmim==0.3.9) (1.26.18)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.10/dist-packages (from requests->openmim==0.3.9) (2024.2.2)
Requirement already satisfied: numpy<2,>=1.22.4 in /usr/local/lib/python3.10/dist-packages (from pandas->openmim==0.3.9) (1.24.4)
Requirement already satisfied: python-dateutil>=2.8.2 in /usr/local/lib/python3.10/dist-packages (from pandas->openmim==0.3.9) (2.8.2)
Requirement already satisfied: pytz>=2020.1 in /usr/local/lib/python3.10/dist-packages (from pandas->openmim==0.3.9) (2023.4)
Requirement already satisfied: tzdata>=2022.1 in /usr/local/lib/python3.10/dist-packages (from pandas->openmim==0.3.9) (2024.1)
Requirement already satisfied: markdown-it-py>=2.2.0 in /usr/local/lib/python3.10/dist-packages (from rich->openmim==0.3.9) (3.0.0)
Requirement already satisfied: pygments<3.0.0,>=2.13.0 in /usr/local/lib/python3.10/dist-packages (from rich->openmim==0.3.9) (2.16.1)
Requirement already satisfied: mdurl~=0.1 in /usr/local/lib/python3.10/dist-packages (from markdown-it-py>=2.2.0->rich->openmim==0.3.9) (0.1.2)
Requirement already satisfied: six>=1.5 in /usr/local/lib/python3.10/dist-packages (from python-dateutil>=2.8.2->pandas->openmim==0.3.9) (1.16.0)
Requirement already satisfied: oss2~=2.17.0 in /usr/local/lib/python3.10/dist-packages (from openxlab->opendatalab->openmim==0.3.9) (2.17.0)
Requirement already satisfied: setuptools~=60.2.0 in /usr/local/lib/python3.10/dist-packages (from openxlab->opendatalab->openmim==0.3.9) (60.2.0)
Requirement already satisfied: crcmod>=1.7 in /usr/local/lib/python3.10/dist-packages (from oss2~=2.17.0->openxlab->opendatalab->openmim==0.3.9) (1.7)
Requirement already satisfied: aliyun-python-sdk-kms>=2.4.1 in /usr/local/lib/python3.10/dist-packages (from oss2~=2.17.0->openxlab->opendatalab->openmim==0.3.9) (2.16.2)
Requirement already satisfied: aliyun-python-sdk-core>=2.13.12 in /usr/local/lib/python3.10/dist-packages (from oss2~=2.17.0->openxlab->opendatalab->openmim==0.3.9) (2.15.0)
Requirement already satisfied: jmespath<1.0.0,>=0.9.3 in /usr/local/lib/python3.10/dist-packages (from aliyun-python-sdk-core>=2.13.12->oss2~=2.17.0->openxlab->opendatalab->openmim==0.3.9) (0.10.0)
Requirement already satisfied: cryptography>=2.6.0 in /usr/local/lib/python3.10/dist-packages (from aliyun-python-sdk-core>=2.13.12->oss2~=2.17.0->openxlab->opendatalab->openmim==0.3.9) (42.0.5)
Requirement already satisfied: cffi>=1.12 in /usr/local/lib/python3.10/dist-packages (from cryptography>=2.6.0->aliyun-python-sdk-core>=2.13.12->oss2~=2.17.0->openxlab->opendatalab->openmim==0.3.9) (1.16.0)
Requirement already satisfied: pycparser in /usr/local/lib/python3.10/dist-packages (from cffi>=1.12->cryptography>=2.6.0->aliyun-python-sdk-core>=2.13.12->oss2~=2.17.0->openxlab->opendatalab->openmim==0.3.9) (2.22)
WARNING: Ignoring invalid distribution -mageio (/usr/local/lib/python3.10/dist-packages)


VPN restarted and resin-vpn interface recreated, happens about 30 seconds after boot

In newer (2.2 and above) images I have noticed that everytime the device boots up, it show up on the dashboard, then drops offline 30 seconds later and is offline for ~10 - 15 seconds and then comes back online as usual.
This is a snap shot of the openvpn-resin service logs when that event happens:
Aug 31 16:50:33 e422fa7 openvpn[735]: VERIFY OK: depth=0, C=UK, ST=UK, L=London, O=Resin, OU=ResinVPN, CN=server, name=EasyRSA<EMAIL_ADDRESS>Aug 31 16:50:34 e422fa7 openvpn[735]: Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Aug 31 16:50:34 e422fa7 openvpn[735]: Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Aug 31 16:50:34 e422fa7 openvpn[735]: Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Aug 31 16:50:34 e422fa7 openvpn[735]: Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Aug 31 16:50:34 e422fa7 openvpn[735]: Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
Aug 31 16:50:34 e422fa7 openvpn[735]: [server] Peer Connection Initiated with [AF_INET]<IP_ADDRESS>:443
Aug 31 16:50:36 e422fa7 openvpn[735]: SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Aug 31 16:50:36 e422fa7 openvpn[735]: PUSH: Received control message: 'PUSH_REPLY,route <IP_ADDRESS>,sndbuf 0,rcvbuf 0,ping 10,ping-restart 60,socket-flags TCP_NODELAY,ifconfig <IP_ADDRESS> <IP_ADDRESS>'
Aug 31 16:50:36 e422fa7 openvpn[735]: OPTIONS IMPORT: timers and/or timeouts modified
Aug 31 16:50:36 e422fa7 openvpn[735]: OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
Aug 31 16:50:36 e422fa7 openvpn[735]: Socket Buffers: R=[341760->341760] S=[44800->44800]
Aug 31 16:50:36 e422fa7 openvpn[735]: OPTIONS IMPORT: --socket-flags option modified
Aug 31 16:50:36 e422fa7 openvpn[735]: Socket flags: TCP_NODELAY=1 succeeded
Aug 31 16:50:36 e422fa7 openvpn[735]: OPTIONS IMPORT: --ifconfig/up options modified
Aug 31 16:50:36 e422fa7 openvpn[735]: OPTIONS IMPORT: route options modified
Aug 31 16:50:36 e422fa7 openvpn[735]: ROUTE_GATEWAY <IP_ADDRESS>/<IP_ADDRESS> IFACE=eth0 HWADDR=b8:27:eb🇩🇪65:2d
Aug 31 16:50:36 e422fa7 openvpn[735]: TUN/TAP device resin-vpn opened
Aug 31 16:50:36 e422fa7 openvpn[735]: TUN/TAP TX queue length set to 100
Aug 31 16:50:36 e422fa7 openvpn[735]: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Aug 31 16:50:36 e422fa7 openvpn[735]: /sbin/ip link set dev resin-vpn up mtu 1500
Aug 31 16:50:36 e422fa7 openvpn[735]: /sbin/ip addr add dev resin-vpn local <IP_ADDRESS> peer <IP_ADDRESS>
Aug 31 16:50:36 e422fa7 openvpn[735]: /etc/openvpn/upscript.sh resin-vpn 1500 1544 <IP_ADDRESS> <IP_ADDRESS> init
Aug 31 16:50:36 e422fa7 openvpn[735]: /sbin/ip route add <IP_ADDRESS>/32 via <IP_ADDRESS>
Aug 31 16:50:36 e422fa7 openvpn[735]: ERROR: Linux route add command failed: external program exited with error status: 2
Aug 31 16:50:36 e422fa7 openvpn[735]: GID set to openvpn
Aug 31 16:50:36 e422fa7 openvpn[735]: UID set to openvpn
Aug 31 16:50:36 e422fa7 openvpn[735]: Initialization Sequence Completed
Aug 31 16:52:38 e422fa7 openvpn[735]: [server] Inactivity timeout (--ping-restart), restarting
Aug 31 16:52:38 e422fa7 openvpn[735]: /etc/openvpn/downscript.sh resin-vpn 1500 1544 <IP_ADDRESS> <IP_ADDRESS> restart
Aug 31 16:52:38 e422fa7 openvpn[735]: WARNING: Failed running command (--up/--down): external program exited with error status: 1
Aug 31 16:52:38 e422fa7 openvpn[735]: Exiting due to fatal error
Aug 31 16:52:38 e422fa7 openvpn[735]: Closing TUN/TAP interface
Aug 31 16:52:38 e422fa7 openvpn[735]: /sbin/ip addr del dev resin-vpn local <IP_ADDRESS> peer <IP_ADDRESS>
Aug 31 16:52:38 e422fa7 openvpn[735]: Linux ip addr del failed: external program exited with error status: 2
Aug 31 16:52:38 e422fa7 openvpn[735]: /etc/openvpn/downscript.sh resin-vpn 1500 1544 <IP_ADDRESS> <IP_ADDRESS> init
Aug 31 16:52:38 e422fa7 systemd[1]: openvpn-resin.service: Main process exited, code=exited, status=1/FAILURE
Aug 31 16:52:38 e422fa7 systemd[1]: openvpn-resin.service: Unit entered failed state.
Aug 31 16:52:38 e422fa7 systemd[1]: openvpn-resin.service: Failed with result 'exit-code'.
Aug 31 16:52:48 e422fa7 systemd[1]: openvpn-resin.service: Service hold-off time over, scheduling restart.
Aug 31 16:52:48 e422fa7 systemd[1]: Stopped OpenVPN Application On Resin.
Aug 31 16:52:48 e422fa7 systemd[1]: Starting OpenVPN Application On Resin...

Tried to replicate on 2.3.0 (Not reproducible). Going to try to latest one.

@agherzan I see this consistently on an rpi3 2.3.0, did you not see the device go offline on the dashboard for a little time at boot?

I tested it on qemu. Both 2.3.0 and 2.4.2 versions have absolutely no VPN downtime at boot. Do you suspect something machine dependent?

Yah, maybe it's some how rpi3 specific, but Craig, myself and @floion have seen this

OK. I'll try it tomorrow on RPI3 too.

@shaunmulligan I tried to reproduce this on current production images with version 2.3.0, RaspberryPi 3 device type and I could not reproduce not even once. Could this have been caused by a VPN server issue? I don't know how to proceed. Can you try to reproduce this on a fresh device? There is absolutely nothing I could see.

Ping @floion and @craig-mulligan because as far as I understood you were able to reproduce it too. Maybe there is more information I can get for any of you.

Ping @shaunmulligan @floion @craig-mulligan

I will close this issue for now. Feel free to reopen if you guys have any additional information.


Button overlap issues

Buttons covering over text with window at half screen size.

Issue is UI overlap on Mark Complete buttons on the event page correct @schuback ?

I'll take this one

Yes.  Looks to be UI.
FYI.  Using MacOS with safari and Firefox.
Sent from my iPhone

On Nov 19, 2016, at 4:57 AM, Barry Luijbregts<EMAIL_ADDRESS>wrote:
I'll take this one
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Solved!


Installation problem for people in China

Installation Issue, While I already have installed dgl manually. but it looks like you have a requirements file that imposing to install the wrong version or something.
note: I am trying to install via pip mirror because I am in China. I tried both USTC and Tshinghua mirror and both ends up with the same error.
DGL latest version is 0.6.1 as per the below screenshot, while Pygcl requires 0.7 ?
I already installed the latest version as shown in error.
pip install  -i https://mirrors.aliyun.com/pypi/simple/ dgl==0.7a210527
What I am doing wrong here?

Hi Ali,
Please follow this page for installing dgl since its package is provided by an external link.

It makes no difference. Maybe if you change the requirement to dgl 0.6 it may solve the problem. as 0.6 is stable version.

It seems that you have already installed dgl 0.6. Therefore you need to uninstall the older version at first and try again to install the new ones.

Also, please update your documentation of PyGCL, but I don't understand how I am going to use it after installation. I am also reading the literature of GCL and am interested to work in this field. i hope I can use PyGCL for implementation. but for now, I don't understand. That is what to do next after installation. or how to run the examples. I hope I am not disturbing you.

Thanks for your advice. After you installed PyGCL, you can refer to this paper for the four contrastive components that we are concerned in this package. We have also provided a brief introduction in the README file to give a big picture of the package. We are very sorry that the doc is not ready since our dev team (consisting of only two people) is chasing some stringent deadlines for now. We endeavor to make our library more easy to use but please give us some time.

I am already this paper and I already have read your other paper "GRACE", hope to see more from you. best of luck.

I followed the instruction and download it from the external link, but it seemed the prompt still suggested that the version for DGL I had was older than 0.7. I wonder what the problem could be.

I followed the instruction and download it from the external link, but it seemed the prompt still suggested that the version for DGL I had was older than 0.7. I wonder what the problem could be.

You may try conda list | grep dgl and check whether the installed version is newer than 0.7. For a temporary solution, you can also remove this specific version requirement by checking out the repo, modifying setup.cfg, and installing locally pip install .. Currently we are refactoring the augmentation class which relies on many builtin functions provided by dgl. It is thus suggested to follow the requirement. We will review the least possible requirement of dgl in the next release. Please stay tuned and thanks for your interest on our library!

@HangerYang
I just installed it 2 days ago again. its working file.
install dgl with "pip install dgl -f https://data.dgl.ai/wheels/repo.html"

I followed the instruction and download it from the external link, but it seemed the prompt still suggested that the version for DGL I had was older than 0.7. I wonder what the problem could be.

You may try conda list | grep dgl and check whether the installed version is newer than 0.7. For a temporary solution, you can also remove this specific version requirement by checking out the repo, modifying setup.cfg, and installing locally pip install .. Currently we are refactoring the augmentation class which relies on many builtin functions provided by dgl. It is thus suggested to follow the requirement. We will review the least possible requirement of dgl in the next release. Please stay tuned and thanks for your interest on our library!

I used the cloning repo method and it worked. Thank you.

@HangerYang I just installed it 2 days ago again. its working file. install dgl with "pip install dgl -f https://data.dgl.ai/wheels/repo.html"

Thank you for your reply :)

@HangerYang I just installed it 2 days ago again. its working file. install dgl with "pip install dgl -f https://data.dgl.ai/wheels/repo.html"

Thank you for your reply :)

Hi, I have dgl-cu111 0.7.1 installed in my device, but when I try to install PyGCL, it returns an error that says the dgl I installed does not meet the requirement. I wonder is this because PyGCL can only work with the non-cuda version of dgl?

Hello HoytWen, we will remove the specific version requirement in the setup configuration, as the newest dgl no longer hosts in PyPi, so that when pip install PyGCL, there won't be a matched version for dgl.

@HangerYang I just installed it 2 days ago again. its working file. install dgl with "pip install dgl -f https://data.dgl.ai/wheels/repo.html"

Thank you for your reply :)

Hi, I have dgl-cu111 0.7.1 installed in my device, but when I try to install PyGCL, it returns an error that says the dgl I installed does not meet the requirement. I wonder is this because PyGCL can only work with the non-cuda version of dgl?

I have just checked with the dgl team. Currently they maintain two packages of dgl, dgl for CPU support and dgl-cu*** for CUDA support. Therefore, when installing PyGCL via pip, pip will only check the dependency for dgl. We will provide a note regarding this problem in the readme.

Thanks a lot!


New M54C Sprites

New replacement sprites!
About the PR
Adds in the following:
M54C Rifle:

M54C Base sprite
M54C Bolted Sprite
M54C Loaded Mag-0 Sprite
M54C Icon Sprite
M54C Equipped Backpack Sprite
M54C Equipped Suit slot sprite
M54C Inhand left and right
M54C Wielded left and right
M54C Sling Sprite

M54C Magazine:

ammo band
base mag sprite
mag-1 sprite

M54C Extended Magazine:

base mag sprite
mag-1 sprite

Why / Balance
Replacing the M41a Sprite which will no longer be used.

Technical details
N/A, sprite change

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

add: Added new M54C sprites!

Rest in peace, M41A.
You will be missed.


[Bug]Device is connected in no-control mode. Sending commands is blocked

The problem
Errorlog shows the following error
"Device is connected in no-control mode. Sending commands is blocked"
Your device model
RT-AC87u
Firmware type
Merlin
Firmware version
384.13_10
Integration version with the issue
0.11.0
Method of the integration installation
HACS
What version and type of Home Assistant installation do you use
2022.10.5
Is there anything useful in the logs?
Device is connected in no-control mode. Sending commands is blocked

Diagnostics information
No response
Additional information
No response

Hey. This is a normal thing when you have not selected "Enable device control".
Just go to Configure for the integration.

So this is not a bug by itself. The question is, how did you get to it? Apparently, you accidently have access to a feature which should be disabled from the integration. And this would be a bug.

That solved it indeed, but no clue why I got the error now, since I'm running the integration already for a long period of time.


Bug fix: Making changes in #309 work for Mac too

See https://trello.com/c/NM8FBoH1 for details.
Pinging @darinkrauss for review. I'm also mergin this into the Animas branch so long so that Nick can test today, but please do bring up any issues identified during review.

One question, but otherwise LGTM. :shipit:


Pod HTTP Status Code not working with Istio

BUG REPORT  (Possible feature if Litmus is not intended to work with Istio Service Mesh)
What happened:
When Istio Service Mesh is used between microservices, the HTTP Status Code experiment appears to run and reports completion, but does not change the actual behavior of the service under test (the status code is not updated to the test value).
What you expected to happen:
Litmus runner/helper to update the IPTABLES in a manner that will allow the experiment to work with Istio sidecar.
Perhaps also add a way for the experiment to report an error when it isn't actually changing traffic.
How to reproduce it (as minimally and precisely as possible):

Add Istio Service Mesh to at least two microservices and not the Litmus delegates, runners, helpers, etc.
Ensure the first microservice (service-a) is sending constant HTTP traffic to the second microservice (service-b)
To make the test easier have a single replica of service-a and service-b
Start a test targeting service-b that changes the response code (we used 401)
Observe either in logs of service-a, or in tracing application like APM that the response code is unchanged from what service-b provides.

Anything else we need to know?:

By default adding Istio to the workloads results in Istio performing mTLS between the two services.  Which also means that the traffic entering the second service will not arrive on the HTTP port under test, but on an Istio port (default 15006)
In our test configuration, to avoid adding service mesh to Litmus workloads, we used annotations per workload.
We also tested with Litmus workloads meshed, however other tests failed and the HTTP tests continued to fail, so we didn't spend much more time in this configuration.
In our environment, this test works as expected when all other factors remain the same, but the Istio sidecars are removed from both services.
We also tested with Litmus un-meshed, the services meshed, and the mTLS disabled between the microservices (using Istio kind: "PeerAuthentication" at the namespace level).  The test also did not change the status code in this configuration.
This article provides a very informative dissection of the IPTABLES changes that Istio performs to the NAT table: https://jimmysong.io/en/blog/sidecar-injection-iptables-and-traffic-routing/
With the above information, we tested the following commands while the test was running (and therefore the toxiproxy should still have been running), the Status Codes were still not changed.

sudo iptables-legacy -t nat -I POSTROUTING -p tcp --dport 8083 -j REDIRECT --to-port 20000
sudo iptables-legacy -t nat -I OUTPUT -p tcp --dport 8083 -j REDIRECT --to-port 20000
sudo iptables-legacy -t nat -I ISTIO_OUTPUT -p tcp --dport 8083 -j REDIRECT --to-port 20000
sudo iptables-legacy -t nat -I ISTIO_REDIRECT -p tcp --dport 8083 -j REDIRECT --to-port 20000

Before these changes to the IPTABLES, we validated that the REDIRECT rule that was added by the experiment did not receive packets.  When adding each of the additional rules in the last bullet, they also did not receive any packets.
We made sure to use 2.14 with the fix that mentions providing support for Service Mesh (changes "-A" to "-I" option in https://github.com/litmuschaos/litmus-go/blob/master/chaoslib/litmus/http-chaos/helper/http-helper.go) - https://github.com/litmuschaos/litmus-go/pull/578

Hi @fosterchuck,
I am running into similar problems with my linkerd setup...
Were you able to find a workaround?
Did you only try Pod HTTP Status Code or also other network-related chaos experiments?

We never resolved this.  We switched to Linkerd Service Mesh and haven't had time to retest.  If memory serves, this issue was present many months ago when we tested with Linkerd too.  I cannot test the newer releases with BETA in their name, due to company restrictions.
This is purely from memory, but I recall using network tests with no issue as long as they were tests that didn't rely on Toxi-Proxy.  None of the HTTP tests worked.
Sorry for the lack of specificity.  This is not part of our current sprint, so I'm not at liberty to test.  We will soon be revisiting this.


Maintained tracer models

Summary Change Description
I created a class (MaintainedModel) along with a decorator that together, that manage the value maintenance of model fields.  To use it, a Model class (e.g. Tracer) inherits from MaintainedModel (instead of Model) and any method that it contains that generates the value of a specific field must have the decorator added.
The decorator takes 3 arguments:

the name of the field whose value it outputs,
the field (or related name) of the linked parent record which contains fields that must also be updated (due to the update on this record)
The hierarchy level ("generation") of the record in the parent/child relationship where root=0 and leaf=the number of generations past the root.  This is use for breadth-first updates after loading (to avoid intermediate states a value would go through as records are linked)

Affected Issue Numbers

Resolves #434

Code Review Notes
The only changes to the Models are the Base class, the decorators, and some necessary field attributes (that are optional but convenient), which means that this code is extremely easy to replace with another means.
Note, I left some commented code that represents an alternative way of preventing direct manual updates of automatically maintained fields.
I put the MaintainedModel tests inside test_infusate.py simply because I thought creating test_maintained_model would give the false impression that the test would be independent of our models and I didn't want to create models.  I did not create tests for every exception type because I would have to create invalid decorators, field attributes, and inheritance, which I didn't dig into how to cleanly do in a test environment.
I could have had this done in half the time if I'd taken some shortcuts based on its current usage, but I wanted it to scale well with added usage.  The only things I didn't try to handle were:

Redundant updates due to differing update hierarchies (i.e. different tree paths from leaf to root).  Currently, every automated field (and every automated field of its parents) is updated per changed record, and it is assumed that updating the youngest generation among all relationships (currently 1) will only result in redundant updates.
Triggering of auto-updates of through model fields.  I currently don't have an auto-updated field in any through models (namely, InfusateTracer), so I didn't bother trying to trigger their update when their "child" is changed.

I have not yet implemented review item changes in the parent branch (tracer_models).  If this PR is deemed worthy of eventual merging, I will implement those changes here to avoid a rebase.
Checklist

[x] All issue requirements satisfied (or no linked issues)
[x] Linting passes.
[x] Migrations created & committed (or no model changes)
[x] Tests implemented (or no code changes)
[ ] All tests pass

In the interests of time, I will proceed with resolving review issues from #428 in this PR, unless/until I hear back otherwise.

I should have...

[ ] Add a script to bulk-update every {Infusate,Tracer,TracerLabel}.name in the database (optionally only unset ones)

Oh don't tell me... the remote run of superlinter differs from my local run (and agrees with my command line isort run). sigh

All review issues for PR #428 have been implemented in this PR.

Oh my gosh.  Superlinter errors again?! This time, the local superlinter run passed everything, even with the isort command line run... sigh, I'll investigate.

OK, @lparsons - I'm not re-requesting a review since you approved, but I did implement your suggestions.  @fkang-pu - you didn't approve or request changes, so I'm not sure if you'd like to take a look at the changes I made based on your suggestions... And I know @jcmatese is busy with his own PR and previously approved... so unless anyone elects to re-review in the interim, I'll merge this tomorrow.


[jk_bms_ble:454]: You hit the unstable auto detection of the protocol version. This feature will be removed in future!Please update your configuration to protocol version JK02_32S if you are using a JK-B2A8S20P v11+

[jk_bms_ble:454]: You hit the unstable auto detection of the protocol version. This feature will be removed in future!Please update your configuration to protocol version JK02_32S if you are using a JK-B2A8S20P v11+
I am getting that message in the logs. I am running a JK_BD4A8S4P, should I be concerned?

Could you tell me the hardware and software version of your device? I assume your device is a JK02 device and it shouldn't be "detected" as JK02_32S. Please check the total_voltage and power_tube_temperature if you see such a log message. I assume the sensor measurements are garbled in this case.

I have been running this BMS with your software since Jan 2023 or earlier. I dont really check the logs too often, but happened to be updating esphome versions from 2023.3.0 to 2023.3.2 and prior to updating I checked the logs and noticed the message.
Power tube temp and total voltage both are displaying accurate values.
JK_BD4A8S4P
HW: V11.XW
SW: V11.24
Ver: V4.10.1

I changed log level to DEBUG and here is the output:
logs_jk-bms-2_run.txt

Just for clarity, I have been running JK02 protocol, and the logs text file linked above is from that protocol version JK02.
I will update to JK02_32S, compile, and provide logs after the update.

I tried to auto-detect the new frame structure (now called JK02_32S) in the past but it has turned out the auto-detection isn't perfect and fails every now and then. This is the cause why I aim to remove the auto-detection in future and let the user choose the correct protocol version.
It looks like your BMS (software version 11+) is auto-detected properly as JK02_32S. So it's safe to pin the protocol version to avoid the auto detection.

The attachments are perfectly fine! Please ignore the Unknown: ... bytes. They are printed just for debugging purposes. You could reduce the log level to INFO now to get rid of these debug ([D]) messages.

You device is a JK02_32S for sure. Your logs are looking good to me.

Great thanks! Consider updating the supported / tested models list - I dont think the BD4A8S4P was on there when I checked yesterday.
I have a few other models of BMS's available for testing if interested...
I have B2A20S20P, BD6A20S10P, and B1A20S15P

new question about a different esp board and different bms's different from the above messages
I have one ESP32-WROOM that is connecting to two JK BMSs, B2A20S20P and BD6A20S10P.
I get the "You hit the unstable auto detection of the protocol version. This feature will be removed in future!Please update your configuration to protocol version JK02_32S if you are using a JK-B2A8S20P v11+" warning in the logs for this one too. Do I need to go ahead and update the protocol on this one?
I am connecting to two different model bms on one esp chip, im not sure which one is causing the warning message, or both. And not sure whats different with jk-2_32s. What do you recommend?

Please start with a single BMS setup / single BLE client connection and update the MAC address per test. As soon you know which protocol version to use you could flash your multiple BLE client connection configuration.
If the protocol version doesn't fit the temperature sensor will be probably zero and the total voltage won't match.

The difference between JK02 and JK02_32S is the number of bytes reserved for cell voltages and resistance. The cell info frame of both protocol versions is 300 bytes long / has a fixed size. At the JK02 protocol version 24 cells are supported because there are 224 bytes reserved for cell voltages and 224 bytes reserved for resistances. At the JK02_32S there are 2232 bytes reserved for cell voltages + resistances. This leads to a different offsets.

Got it, I'll do some testing and post the results, thanks!

I have a few other models of BMS's available for testing if interested...
I have B2A20S20P, BD6A20S10P, and B1A20S15P

Is your offer still valid?

Yep, what would you like me to do?

Please collect the MAC addresses of your devices. Flash a ESP32 with this YAML
https://github.com/syssi/esphome-jk-bms/blob/main/esp32-ble-example.yaml
make sure you are able to enabled/disable the discharging mosfet using the switch entity and provide the software and hardware version per device.

JK-B1A20S15P works well using jk02 protocol.
Hardware Ver: V10.XW
Software Ver: V10.10
Manuf Date: 2023-04-16
Version: V4.10.1
I just notice the manuf date is today... I wonder if this is because today is the first day its ever been powered on? I bought it a few months back and just wired it up today...
Attached is a log file that you can review.
logs_jk-bms-3_logs.txt
one bit that may be worth review:

[22:49:54][D][sensor:127]: 'jk-bms-3 charging cycles': Sending state 0.00000  with 0 decimals of accuracy
[22:49:54][D][sensor:127]: 'jk-bms-3 total charging cycle capacity': Sending state 0.10400 Ah with 3 decimals of accuracy
[22:49:54][D][jk_bms_ble:647]: Unknown158: 0x64 0x00 (always 0x64 0x00?)
[22:49:54][D][jk_bms_ble:650]: Unknown160: 0x9D 0x05 (always 0xC5 0x09?)
[22:49:54][D][sensor:127]: 'jk-bms-3 total runtime': Sending state 19897.00000 s with 0 decimals of accuracy
[22:49:54][D][text_sensor:067]: 'jk-bms-3 total runtime formatted': Sending state '5h'
[22:49:54][D][jk_bms_ble:663]: Unknown168: 5B.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.00.00.00.C<IP_ADDRESS>.00.00.A<IP_ADDRESS>.<IP_ADDRESS>.E<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS> (46)
[22:49:54][D][jk_bms_ble:677]: Unknown189: 0x03 0x00
[22:49:54][D][jk_bms_ble:681]: Unknown192: 0x00
[22:49:55][D][api:102]: Accepted <IP_ADDRESS>
[22:49:56][D][api.connection:920]: Home Assistant 2023.4.2 (<IP_ADDRESS>): Connected successfully
[22:49:59][I][jk_bms_ble:467]: Cell info frame (version 2, 300 bytes) received
[22:49:59][D][sensor:127]: 'jk-bms-3 cell voltage 1': Sending state 3.32800 V with 3 decimals of accuracy
[22:49:59][D][sensor:127]: 'jk-bms-3 cell resistance 1': Sending state 0.06100 Ω with 3 decimals of accuracy

Manuf Date: 2023-04-16

You are right! This is the date of the first power on. I don't know it's a new feature (and written by the Android app) or it has always been like this.


Change URL

Hi,
if instead of connecting through the ip I wanna connect typing foto.app how should I proceed?
Thank you everyone

setup a reverse proxy for a subdomain.  It is a pretty straight forward
config too, nothing extra really.
i used Nginx.
On Wed, Jul 24, 2019 at 12:51 AM alopezbu<EMAIL_ADDRESS>wrote:

Hi,
if instead of connecting through the ip I wanna connect typing foto.app
how should I proceed?
Thank you everyone
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bpatrik/pigallery2/issues/95?email_source=notifications&email_token=ABST2IBELMVRVPY2J626HGLQA4ZKTA5CNFSM4IGGUNKKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HA7IKCA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABST2IAGD5LUR2DWZWF45ETQA4ZKTANCNFSM4IGGUNKA
.

Hi,
It is more a general server server setup question than a pigallery one.
It depends what you exactly want.

If you only want to access your server from your home network, you can setup a hostname like myserver on the server and broadcast that. Then you would be able to access your server at http://myserver.

From the 'Web'

Your server is probably behind a router with NAT, you need to do port forwarding (typically port 80 forward to your server IP) on the router.
then get a domain name. Potentially something like dyndns (I can recommend duckdns) as you probably get dynamic IP from four ISP (internet service provider)
Here is guide for that. Point 10 and 11 are the important ones.

You most likely looking for the 2. option.

i close this due to inactivity


v4.1.1 – Use Unified Mode in all resources

This PR

Adds Chef 17 notes to CHANGELOG
Adds unified_mode true to all resources. See Unified Mode in Custom Resources
for more information.

Why

Resolves deprecation warnings about unified mode when using Chef 17. Without unified_mode true, the following deprecation warning is received (it's real noisy):

  The automatic_software_updates resource in the macos cookbook should declare `unified_mode true` at 1 location:
    - /private/var/folders/6h/5602xjnn6rb7l3lr0str3hw00000gn/T/tmp.qdK9JILL/.chef/local-mode-cache/cache/cookbooks/macos/resources/automatic_software_updates.rb
   See https://docs.chef.io/deprecations_unified_mode/ for further details.

...and so on for all of the cookbook's resources.
Although unified_mode isn't strictly required for Chef 17, it will save some headache in 2022 when it is required by Chef 18.

Awesome! While this is going to be more of an impact in Chef 18, let's get rid of the warnings now!


chore: Add signed commits requirement to CONTRIBUTING.md

What does this PR do?
📦 Adding a requirement for signing commits to CONTRIBUTING.md.
Counterpart to https://github.com/DataDog/dd-sdk-ios/pull/1709
Motivation
To be specific in what we require for external contributions.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1905 (ce92ac7) into develop (87f81fe) will decrease coverage by 0.03%.
The diff coverage is n/a.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1905      +/-   ##
===========================================
- Coverage    83.42%   83.39%   -0.03%
===========================================
  Files          477      477
  Lines        16922    16915       -7
  Branches      2514     2514
===========================================
- Hits         14116    14105      -11
- Misses        2119     2124       +5
+ Partials       687      686       -1

see 28 files with indirect coverage changes


Maintain orderhint for Get-PnPPlannerBucket

Type

[x] Bug Fix
[ ] New Feature
[ ] Sample

Related Issues?
Fixes #1918
What is in this Pull Request ?
Removed custom sorting so the Graph sorting on orderHint property is maintained.

Thanks @milanholemans !


Sluggish scroll through folder with large volume of entries - Chrome only [Bug Report]

Describe the bug
Scrolling is very sluggish (and freezes) when scrolling in a folder containing a large number of entries on Chrome on Windows 10.
I requested a related feature here: https://github.com/hkalexling/Mango/issues/35
I think it is related to other Chrome bug here: https://github.com/hkalexling/Mango/issues/34
I have tested on Microsoft Edge on Windows 10, chrome on Android, and Firefox on Ubuntu. I found that scrolling/browsing a folder with 400 entries is smooth after the page fully loaded (painful to scroll through the volume of items, but not sluggish). Therefore, the issue seems to be present in Chrome on Windows 10 only.
Probably related to https://github.com/hkalexling/Mango/issues/26

Update:
Issue present on Chrome 81.0.4044.129 on Windows 10. Updated Chrome to 81.0.4044.138. Issue persists.
Tested on other devices, and no issues on:
Chrome 81.0.4044.129 on Windows 10 on a different device
Microsoft Edge on Windows 10 on ORIGINAL DEVICE
Chrome on Android phone
Firefox on Ubunt


Use lowercase name for romans module

The previous uppercase module name would output the following
warning when running tests:
src/lib.rs:2:1: 42:2 warning: module `Roman` should have a snake case
name such as `roman`, #[warn(non_snake_case)] on by default
src/lib.rs:2 pub mod Roman {

Apologies, this should be a struct and thus uppercase is valid.


Implement Lab3 - Letter Frequency

Fixes #262
Review of colleague's PR #343
Changes proposed in this PR:

Implement Lab3 LetterFrequency.
Test Lab3.

Codecov Report

Merging #263 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #263   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          16     17    +1
  Lines         266    285   +19
=====================================
+ Hits          266    285   +19

Impacted Files
Coverage Δ

03_letters/brvishnu92/main.go
100% <100%> (ø)

Continue to review full report at Codecov.

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

@rokane Can you please have a look at the updated code when you are free? Thanks a ton :-)

@camh-anz  Sorry, I had implemented the changes but lost them while rebasing. I tried to do the same now, but again i could see the old file reflecting while rebasing after working on it. So i overwrote the file again and pushed.

Maybe because I work off two laptops.. I do “git pull” but should I be doing “git fetch” as well ...


Continue-on-fail support - allowing chains to continue with a value even after a fail?

@Naios
Hello.  Nice work with this library.  it's been fun integrating it into our traditional callback flows.
I am wondering if there's any support to continue-on-fail?  Something similar to recover in Scala futures?    Basically handling an exception and allowing the chain to continue with a value or re-throwing the exception for the next fail handler to be triggered?  I have use-cases where this is very handy.
https://www.scala-lang.org/api/2.12.3/scala/concurrent/Future.html#recover
thanks.

cti::recover  and cti::rethrow are fully supported to change the current error state as described in the documentation. Those functions return a cti::result which can be returned from any handler to change the current error state, either recover from it or return an exceptional result:
http_request("example.com")
  .then([](std::string content) -> cti::result<int, int> {
    return recover(1, 2);
  })
  .fail([](cti::exception_t exception) -> cti::result<int, int> {
    return recover(1, 2);
  })
  .then([](int a, int b) -> cti::result<int, int> {
    // Recovered from the failure
  })

http_request("example.com")
  .then([](std::string content) {
    return rethrow(std::make_exception_ptr(std::exception{}));
  })
  .fail([](cti::exception_t exception) {
    return rethrow(std::make_exception_ptr(std::exception{}));
  })
  .next([](auto&&...) {
    return rethrow(std::make_exception_ptr(std::exception{}));
  });

awesome!  thanks.  I missed that in the docs.  I will give that a shot.


Consider using TS for Webpack config

TypeScript is preferable since it will enable IDE hints and type-checking.
https://webpack.js.org/configuration/configuration-languages/

Implemented in https://github.com/mterczynski/typescript-webpack-threejs-template/commit/911543965a5ed51977f955cbda9bfda650a4f100


Unclear error message when running unknown job.

nix-shell --argstr job foo will produce:
error: nix-shell requires a single derivation

This can be especially confusing when the unknown job is simply a known Coq project that is missing from coqPackages.

As discussed in https://coq.zulipchat.com/#narrow/stream/290990-Nix-toolbox.20devs.20.26.20users/topic/.60nix-shell.20https.3A.2F.2Fcoq.2Einria.2Efr.2Fnix.2Ftoolbox.20--argstr.20job.60, we should ensure that we fail at evaluation time instead of producing an empty derivation in such cases.


[flutter_tool] ensure extraGenSnapshotArguments are forwarded to gen_snapshot from Android builds

Description
During the assemble migration, this functionality was not correctly wired up to the new rules.
https://github.com/flutter/flutter/issues/47049

This isn't quite enough to necessarily "fix" the issue, because the obfuscation map will get written to an arbitrary cache location. It might make sense to copy this to a new location, though I'm not sure where that is  yet.

The target location of the file is specified by the following parameter:
--save-obfuscation-map=build/symbols.json

Ahh perfect, thanks @talent-apps


Powershell C#/F# interop

I would like to have  the possibility to use/parse Azure CLI results in F#/C#.
In particular for the time being following statement generates json that I would like to reuse with other language:
$subs = az functionapp config appsettings list --name myresourcename --resource-group mygroup --subscriptionmysub
$subs

Unfortunately any approach to consume it in C#/F# cell doesn't work, including following:
#!value --name someJson
$subs

#!csharp
#!share someJson --from value
someJson // "subs" is printed

You don't need to go through the #!value kernel if you already have a variable.
This works for me:


date/time stamps are not visible in the tooltips

When the dark design theme is enabled, date/time stamps are not visible in the tooltips on chart type reports

It's with a dark theme

It's with a light theme


[FEATURE REQUEST] Superwall.shared.handleDeepLink should return BOOL

Is your feature request related to a problem? Please describe.
handleDeepLink should return BOOL so it can be better integrated with existing code (true if the URL is handled / it's a valid preview URL, false otherwise).
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Thanks, I'll add this

FYI this is out in 3.0.0-beta.4 now


Require Localization for Some Discovered PTMs

Some ptms have masses that could be confussed with other ptms of the same or similar mass (+/- 1 Da). Rare mods may occur at a level difficult to discern from the noise. Both types would benefit from extra scrutiny. We could add a feature to the modification that requires an increase metamorpheus score for certain mods. Something like:
LR   True/False
LR = localization required
Mods like phospho and glyco which are prevalent but cant be easily localized would be left as false. I think acetyl is fine to keep as false. Oxidations and hydroxylations may require localization..

@trishorts want to add the LR flag to mzLib? seems useful...

I like that

I think this is worth investigating:
in the first-pass search, what if we searched with targets only, got rid of the q-value stuff, and only annotated mods where the score improved over unmodified? that way there's at least one fragment that helps localize the mod, and the search would be faster (probably). there would be a sensitivity decrease but the confidence in PTM localization would be better. less junk to search through in the second-pass search, too.
we could evaluate this strategy with an open-mass search post-GPTMD and see what the mass-diff histogram looks like. if there are still large peaks then maybe that strategy wouldn't work well (i.e., it misses too many mods).

I think this would create a bias towards targets in the second-pass search though, yeah? i.e., the PTM-containing targets are guaranteed to have a higher score, but the decoys aren't. Not quite sure, maybe @zrolfs can chime in. I can't quite wrap my head around it.
Maybe we can put the PTM on the best-localized position for the peptide in the first-pass search, even if the localized score is worse than the unmodified. That way we cut down on the search space in the first pass (no decoys) and second pass (only the best PTM positions are annotated) while still maintaining TD requirements?

Rob is correct. When we add target PTMs that matched well to spectra (but not decoy PTMs), we are biasing our second pass search to over-report. We can (somewhat) get away with it when we limit the additions to just PTMs found above a 1% FDR, because GPTMD has a relatively high score threshold with all the notches such that a peptide needs to have a pretty good score to be identified at a 1% FDR in GPTMD. If we add every target PTM (and no decoys), then we're now making it ~N times more likely for a random sequence to match to a target than a decoy, where N is the number of notches used.


Reduce bug checks to those that effect versions of Node with built-in Object.assign

This PR reduces the bug checks to those that effect versions of Node with built-in Object.assign.
I used Node v4.0.0 as the minimum bar.
Related to object-assign/pull/32/files.
\cc @rgbkrk

Per our off-GitHub discussion, I'm not very interested in changing around the logic here. I'd rather just recommend the native Object.assign.


Add sample_trainset.csv to app

Make this available for download immediately below the "Upload" button and linked in the help docs.
sample_trainset.csv.zip

Also, make sure the link in the help docs links to it