Not starting completely... DB::exception

Hello,
First time install Plausible. Followed this guide. Created .env, and added "ports" to compose.yml. Nothing more.
compose.yml seem to be correct. I'm using port 8000:8000.
Then it hangs there, with an exception:
plausible_1            | ------------------------------------------------------------------------------
plausible_1            |     add-alias-column Done!
plausible_1            |
plausible_1            | ------------------------------------------------------------------------------
plausible_1            |     update-location-data-table-comment Done!
plausible_1            |
plausible_1            | ------------------------------------------------------------------------------

plausible_db_1         | 2024-12-02 13:48:35.972 UTC [52] LOG:  checkpoint starting: time
^CGracefully stopping... (press Ctrl+C again to force)
Stopping plausible-ce_plausible_1           ... done
Stopping plausible-ce_plausible_events_db_1 ... done
Stopping plausible-ce_plausible_db_1        ... done

root@plause:/opt/plausible-ce# docker-compose up
Starting plausible-ce_plausible_db_1        ... done
Starting plausible-ce_plausible_events_db_1 ... done
Starting plausible-ce_plausible_1           ... done
Attaching to plausible-ce_plausible_db_1, plausible-ce_plausible_events_db_1, plausible-ce_plausible_1
plausible_db_1         |
plausible_db_1         | PostgreSQL Database directory appears to contain a database; Skipping initialization
plausible_db_1         |
plausible_db_1         | 2024-12-02 13:49:08.438 UTC [1] LOG:  starting PostgreSQL 16.6 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
plausible_db_1         | 2024-12-02 13:49:08.439 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
plausible_db_1         | 2024-12-02 13:49:08.439 UTC [1] LOG:  listening on IPv6 address "::", port 5432
plausible_db_1         | 2024-12-02 13:49:08.451 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
plausible_db_1         | 2024-12-02 13:49:08.457 UTC [28] LOG:  database system was shut down at 2024-12-02 13:49:03 UTC
plausible_db_1         | 2024-12-02 13:49:08.463 UTC [1] LOG:  database system is ready to accept connections
plausible_events_db_1  | <jemalloc>: Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db_1  | <jemalloc>: Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db_1  | <jemalloc>: Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db_1  | <jemalloc>: Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db_1  | <jemalloc>: Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db_1  | <jemalloc>: Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db_1  | <jemalloc>: Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db_1  | <jemalloc>: Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db_1  | ClickHouse Database directory appears to contain a database; Skipping initialization
plausible_events_db_1  | <jemalloc>: Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db_1  | <jemalloc>: Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db_1  | Processing configuration file '/etc/clickhouse-server/config.xml'.
plausible_events_db_1  | Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'.
plausible_events_db_1  | Merging configuration file '/etc/clickhouse-server/config.d/ipv4-only.xml'.
plausible_events_db_1  | Merging configuration file '/etc/clickhouse-server/config.d/logs.xml'.
plausible_events_db_1  | Logging warning to /var/log/clickhouse-server/clickhouse-server.log
plausible_events_db_1  | Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log

plausible_events_db_1  | 2024.12.02 13:49:08.905569 [ 1 ] {} <Warning> Context: Delay accounting is not enabled, OSIOWaitMicroseconds will not be gathered. You can enable it using `echo 1 > /proc/sys/kernel/task_delayacct` or by using sysctl.
plausible_events_db_1  | 2024.12.02 13:49:09.082894 [ 1 ] {} <Error> Application: Disabling cgroup memory observer because of an error during initialization: Code: 107. DB::Exception: Cannot find cgroups v1 or v2 current memory file. (FILE_DOESNT_EXIST), Stack trace (when copying this message, always include the lines below):
plausible_events_db_1  |
plausible_events_db_1  | 0. DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0x000000000cbc851b
plausible_events_db_1  | 1. DB::Exception::Exception<>(int, FormatStringHelperImpl<>) @ 0x00000000076614c3
plausible_events_db_1  | 2. DB::CgroupsMemoryUsageObserver::CgroupsMemoryUsageObserver(std::chrono::duration<long long, std::ratio<1l, 1l>>) @ 0x000000000cce452e
plausible_events_db_1  | 3. DB::Server::main(std::vector<String, std::allocator<String>> const&) @ 0x000000000cd562bd
plausible_events_db_1  | 4. Poco::Util::Application::run() @ 0x0000000014ca8606
plausible_events_db_1  | 5. DB::Server::run() @ 0x000000000cd46671
plausible_events_db_1  | 6. Poco::Util::ServerApplication::run(int, char**) @ 0x0000000014cb14b9
plausible_events_db_1  | 7. mainEntryClickHouseServer(int, char**) @ 0x000000000cd4246a
plausible_events_db_1  | 8. main @ 0x0000000007651578
plausible_events_db_1  | 9. ? @ 0x00007f6920262083
plausible_events_db_1  | 10. _start @ 0x0000000005dee46e

plausible_events_db_1  |  (version <IP_ADDRESS> (official build))
plausible_1            | Loading plausible..
plausible_1            | Starting dependencies..
plausible_1            | Starting repos..
plausible_1            | Plausible.Repo database already exists
plausible_1            | Plausible.IngestRepo database already exists
plausible_1            | Creation of Db successful!
plausible_1            | Loading plausible..
plausible_1            | Starting dependencies..
plausible_1            | Starting repos..

Here is the content of compose.yml:
services:
  plausible_db:
    image: postgres:16-alpine
    restart: always
    volumes:
      - db-data:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=postgres
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      start_period: 1m

  plausible_events_db:
    image: clickhouse/clickhouse-server:<IP_ADDRESS>-alpine
    restart: always
    volumes:
      - event-data:/var/lib/clickhouse
      - event-logs:/var/log/clickhouse-server
      - ./clickhouse/logs.xml:/etc/clickhouse-server/config.d/logs.xml:ro
      # This makes ClickHouse bind to IPv4 only, since Docker doesn't enable IPv6 in bridge networks by default.
      # Fixes "Listen [::]:9000 failed: Address family for hostname not supported" warnings.
      - ./clickhouse/ipv4-only.xml:/etc/clickhouse-server/config.d/ipv4-only.xml:ro
    ulimits:
      nofile:
        soft: 262144
        hard: 262144
    healthcheck:
      test: ["CMD-SHELL", "wget --no-verbose --tries=1 -O - http://<IP_ADDRESS>:8123/ping || exit 1"]
      start_period: 1m

  plausible:
    ports:
       - 8000:8000
    image: ghcr.io/plausible/community-edition:v2.1.4
    restart: always
    command: sh -c "/entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh run"
    depends_on:
      plausible_db:
        condition: service_healthy
      plausible_events_db:
        condition: service_healthy
    volumes:
      - plausible-data:/var/lib/plausible
    ulimits:
      nofile:
        soft: 65535
        hard: 65535
    environment:
      - TMPDIR=/var/lib/plausible/tmp
      # required: https://github.com/plausible/community-edition/wiki/configuration#required
      - BASE_URL=${BASE_URL}
      - SECRET_KEY_BASE=${SECRET_KEY_BASE}
      # optional: https://github.com/plausible/community-edition/wiki/configuration#optional
      # registration: https://github.com/plausible/community-edition/wiki/configuration#registration
      - TOTP_VAULT_KEY
      - DISABLE_REGISTRATION
      - ENABLE_EMAIL_VERIFICATION
      # web: https://github.com/plausible/community-edition/wiki/configuration#web
      - HTTP_PORT
      - HTTPS_PORT
      # databases: https://github.com/plausible/community-edition/wiki/configuration#database
      - DATABASE_URL
      - CLICKHOUSE_DATABASE_URL
      # Google: https://github.com/plausible/community-edition/wiki/configuration#google
      - GOOGLE_CLIENT_ID
      - GOOGLE_CLIENT_SECRET
      # geolocation: https://github.com/plausible/community-edition/wiki/configuration#ip-geolocation
      - IP_GEOLOCATION_DB
      - GEONAMES_SOURCE_FILE
      - MAXMIND_LICENSE_KEY
      - MAXMIND_EDITION
      # email: https://github.com/plausible/community-edition/wiki/configuration#email
      - MAILER_ADAPTER
      - MAILER_EMAIL
      - MAILER_NAME
      - SMTP_HOST_ADDR
      - SMTP_HOST_PORT
      - SMTP_USER_NAME
      - SMTP_USER_PWD
      - SMTP_HOST_SSL_ENABLED
      - POSTMARK_API_KEY
      - MAILGUN_API_KEY
      - MAILGUN_DOMAIN
      - MAILGUN_BASE_URI
      - MANDRILL_API_KEY
      - SENDGRID_API_KEY

volumes:
  db-data:
  event-data:
  event-logs:
  plausible-data:

I'm sure I did something wrong. Any idea?

👋 @charleslcso
What do you mean by "hangs with an exception"?

Also docker-compose is outdated as of two years ago. I suggest going through Docker Compose instructions and switching to the new docker compose plugin.

Hi
I am using docker compose plugin now.
Same output... DB::Exeception is still there.
root@plause:/opt/plausible-ce# docker compose up -d
[+] Running 6/6
✔ Container plausible-ce_plausible_1            Recreated                                                                                4.3s
✔ Container plausible-ce_plausible_events_db_1  Recreated                                                                                2.3s
✔ Container plausible-ce_plausible_db_1         Recreated                                                                                0.6s
✔ Container plausible-ce-plausible_db-1         Healthy                                                                                6.2s
✔ Container plausible-ce-plausible_events_db-1  Healthy                                                                                6.2s
✔ Container plausible-ce-plausible-1            Started                                                                                0.5s
root@plause:/opt/plausible-ce# docker compose stop
[+] Stopping 3/3
✔ Container plausible-ce-plausible-1            Stopped                                                                                1.9s
✔ Container plausible-ce-plausible_events_db-1  Stopped                                                                                2.5s
✔ Container plausible-ce-plausible_db-1         Stopped                                                                                0.5s
root@plause:/opt/plausible-ce# docker compose up
[+] Running 3/0
✔ Container plausible-ce-plausible_events_db-1  Created                                                                                0.0s
✔ Container plausible-ce-plausible_db-1         Created                                                                                0.0s
✔ Container plausible-ce-plausible-1            Created                                                                                0.0s
Attaching to plausible-1, plausible_db-1, plausible_events_db-1
plausible_db-1         |
plausible_db-1         | PostgreSQL Database directory appears to contain a database; Skipping initialization
plausible_db-1         |
plausible_events_db-1  | : Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db-1  | : Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_db-1         | 2024-12-02 14:11:51.698 UTC [1] LOG:  starting PostgreSQL 16.6 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
plausible_db-1         | 2024-12-02 14:11:51.712 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
plausible_db-1         | 2024-12-02 14:11:51.712 UTC [1] LOG:  listening on IPv6 address "::", port 5432
plausible_db-1         | 2024-12-02 14:11:51.716 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
plausible_db-1         | 2024-12-02 14:11:51.721 UTC [28] LOG:  database system was shut down at 2024-12-02 14:11:45 UTC
plausible_events_db-1  | : Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_db-1         | 2024-12-02 14:11:51.726 UTC [1] LOG:  database system is ready to accept connections
plausible_events_db-1  | : Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db-1  | : Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db-1  | : Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db-1  | : Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db-1  | : Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db-1  | ClickHouse Database directory appears to contain a database; Skipping initialization
plausible_events_db-1  | : Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db-1  | : Number of CPUs detected is not deterministic. Per-CPU arena disabled.
plausible_events_db-1  | Processing configuration file '/etc/clickhouse-server/config.xml'.
plausible_events_db-1  | Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'.
plausible_events_db-1  | Merging configuration file '/etc/clickhouse-server/config.d/ipv4-only.xml'.
plausible_events_db-1  | Merging configuration file '/etc/clickhouse-server/config.d/logs.xml'.
plausible_events_db-1  | Logging warning to /var/log/clickhouse-server/clickhouse-server.log
plausible_events_db-1  | Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log
plausible_events_db-1  | 2024.12.02 14:11:51.987546 [ 1 ] {}  Context: Delay accounting is not enabled, OSIOWaitMicroseconds will not be gathered. You can enable it using echo 1 > /proc/sys/kernel/task_delayacct or by using sysctl.
plausible_events_db-1  | 2024.12.02 14:11:52.152900 [ 1 ] {}  Application: Disabling cgroup memory observer because of an error during initialization: Code: 107. DB::Exception: Cannot find cgroups v1 or v2 current memory file. (FILE_DOESNT_EXIST), Stack trace (when copying this message, always include the lines below):
plausible_events_db-1  |
plausible_events_db-1  | 0. DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0x000000000cbc851b
plausible_events_db-1  | 1. DB::Exception::Exception<>(int, FormatStringHelperImpl<>) @ 0x00000000076614c3
plausible_events_db-1  | 2. DB::CgroupsMemoryUsageObserver::CgroupsMemoryUsageObserver(std::chrono::duration<long long, std::ratio<1l, 1l>>) @ 0x000000000cce452e
plausible_events_db-1  | 3. DB::Server::main(std::vector<String, std::allocator> const&) @ 0x000000000cd562bd
plausible_events_db-1  | 4. Poco::Util::Application::run() @ 0x0000000014ca8606
plausible_events_db-1  | 5. DB::Server::run() @ 0x000000000cd46671
plausible_events_db-1  | 6. Poco::Util::ServerApplication::run(int, char**) @ 0x0000000014cb14b9
plausible_events_db-1  | 7. mainEntryClickHouseServer(int, char**) @ 0x000000000cd4246a
plausible_events_db-1  | 8. main @ 0x0000000007651578
plausible_events_db-1  | 9. ? @ 0x00007f2939053083
plausible_events_db-1  | 10. _start @ 0x0000000005dee46e
plausible_events_db-1  |  (version <IP_ADDRESS> (official build))
plausible-1            | Loading plausible..
plausible-1            | Starting dependencies..
plausible-1            | Starting repos..
plausible-1            | Plausible.Repo database already exists
plausible-1            | Plausible.IngestRepo database already exists
plausible-1            | Creation of Db successful!
plausible-1            | Loading plausible..
plausible-1            | Starting dependencies..
plausible-1            | Starting repos..
Then no more output after Starting repos..

Why are you using docker compose up in non-detached mode? If you stop doing it, the "hang" would go away :)

Just did it with -d.

So what's the problem now? I guess by your screenshots that you cannot access it?

Would you be able to share your compose.override.yml and .env with secrets redacted?

Yes, I can't access it.
Plausible is definitely not running, and I need to look for errors.

Right after docker compose -d I run lsof and see what ports are being listened to... nothing from docker.

Weird...

Please stop with the screenshots :) You seem to have missed the quick start in the README.

Embarrassing...
It is working now.
Thank you for being with me.


Add AUR listing

Created an Arch Linux package for personal use. Decided to upload to the AUR. You can add the link to the description for other to see and use, too :)
P.S. I named it du-dup-bin for multiple reasons. Firstly, there already is a dup package, so I guessed it wouldn't be a problem to name it du-dup like in the case with cargo. And secondly, -bin because it is a prebuilt package, a package that compiles from source  wouldn't have such a suffix.

Way ahead of you :) https://aur.archlinux.org/packages/dup-rs/

Wow, didn't notice there had already been a package. The name isn't that obvious to be honest. I wouldn't make mine if I found yours but too late, I guess. And yeah, mine is binary, I don't like compiling stuff

Wow, didn't notice there had already been a package. The name isn't that obvious to be honest. I wouldn't make mine if I found yours but too late, I guess. And yeah, mine is binary, I don't like compiling stuff

I could change it to du-dup. I figure if it eventually ends up in the repos, it would probably be renamed to dup anyhow. (This was created before the crate :p.)

You guys are fast .. I haven't even announced this officially :smile:
I think we should look for an entirely new name (see #9) before we start attaching more pre- and post-fixes. What do you think?

You guys are fast .. I haven't even announced this officially smile

<.< https://lobste.rs/s/vh6uhw/minimal_fast_alternative_du_sh

I think we should look for an entirely new name (see #9) before we start attaching more pre- and post-fixes. What do you think?

:+1:

¯\_(ツ)_/¯

<.< lobste.rs/s/vh6uhw/minimal_fast_alternative_du_sh

¯_(ツ)_/¯

:see_no_evil: :smile:
I have renamed the project to diskus. It looks like the name is available on the AUR: https://aur.archlinux.org/packages/?O=0&K=diskus


feature: add folke/zen-mode to extras

Did you check the docs?

[X] I have read all the LazyVim docs
[X] This is not a request for a new or existing extra (see above)

Is your feature request related to a problem? Please describe.
No problem - just a nice-to-have feature.
Describe the solution you'd like
folke/zen-mode
Describe alternatives you've considered
n/a
Additional context
No response

IMPORTANT: ideas or requests related to extras, should go in the Extra Requests discussion forum.
This is not a request for a new or existing extra (see above)

you can just add that to your own config. not worth to add as an extra
  {
    "folke/zen-mode.nvim",
    cmd = "ZenMode",
    opts = {},
    keys = { { "<leader>z", "<cmd>ZenMode<cr>", desc = "Zen Mode" } },
  }


Create arman_08_Account Linking - Set up a Child_2023-12-23.cdc

duplicated code
https://github.com/FlowFans/zealy-campaigns/blob/main/2023/q4-code-snippets/submissions/deva andika_Account Linking - Set up a Child Account_2023-12-19.cdc


Expandable blocks break with undo/redo

The inputs disappear and the mutations gets into a weird state

Closing in favour of https://github.com/Microsoft/pxt-ev3/issues/739


[request] Add the mentioned user as watcher

Hi, would be possible somehow to automatically add the mentioned user in the watcher list automagically?
We are using restricted permissions so only watchers can reply and see the conversation. Just mentioning someone triggers an email notification but it has no permissions to see the issue. Just the notification

If this feature gets added, I vote that it be togglable in settings and not enabled by default.  While I understand OP's use-case, I've found (having had this feature on other issue trackers) that often users get @mentioned just for a quick clarifying question.


Question: consistency of metadata in .nwb and bids filename/side-car - must be consistent, or allowed to be overloaded?

.nwb files are supported by BIDS since awhile.  NWB files are hdf5 files following quite elaborate nwb schema which includes metadata which is also covered by BIDS itself, such as subject_id, session_id, etc.  I wonder, are we to allow such metadata be "overloaded" by BIDS (so it is sub-001 in BIDS while .nwb file says "mouse3") or they must be consistent (and thus bids-validator should error out)?

NWB is a permitted file format for iEEG only (currently), perhaps someone has stumbled over this issue already? How did you deal with it? @bids-standard/raw-electrophys-ieeg
Personally, I don't know anyone who has worked with NWB in the context of BIDS.

This does not only apply to NWB, but  to all formats where the original header is difficult or impossible to edit by the neuroscientists that acquire the data and do the BIDS curation.
In discussions with @hoechenberger and @cbrnr et al on the MNE-Python repository we (as software developers) agreed that the BIDS sidecars overrule the (binary) headers of the MEG, EEG and iEEG files. The discussion starts more or less around here.

Ah, that reminds me of #761 which would be great to finally agree on and merge

NWB is a permitted file format for iEEG only (currently), perhaps someone has stumbled over this issue already? How did you deal with it? @bids-standard/raw-electrophys-ieeg

Note that in this case specifically, NWB is 'permitted', but not 'supported', which means that the validator does not validate the NWB metadata.


Add missing default headers to device code

Content-type and Telemetry headers are missing in device code flow as we are not calling the default headers API correctly. Fixing the issue with this PR.
Note: We mock all our network calls in unit tests and hence couldn't catch this in our testing.
Todo:
Adding these in end-to-end tests is a good idea. Will try to see if the current framework allows this.

Coverage remained the same at 82.335% when pulling bd79e519a62f21feae0fef3f8e0d31a53a9fc69b on set-default-headers into 532fbcfeb542452ce3ac434fc1704a39d9218e14 on dev.

Any tests that need to be updated?

Not sure. May be in E2E. Cannot add to UT because we mock our network calls. Introducing nock would be a good idea, so may be defer the testing into a separate issue would be a good idea since this PR cannot wait and is blocking Azure SDK.


bump codecov-action to v4

uses node.js v20 instead of deprecated node.js v16
also uses token in an env var as recommended by codecov docs

I thought it was enabled for this repo, but I guess it is not. No wonder I had to bump these actions myself 🤣

[x] added the depndabot config.


release 6.1.0

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

rebuild the changelog and this time the reference.md as well


Can you also sharing the assets to generate hybrid ray tracing output?

thanks for sharing hybrid ray tracing rendering work combining rasterization and ray tracing together.
can you also please share the assets accompany to generate the rendering result?

Sure thing, I'll add a prebuilt release with the assets soon.

Sure thing, I'll add a prebuilt release with the assets soon.

hi, any chance that you can provide the sponza scene asset?
I try one copy from another repo yet it seems does not working, the program crashed when draw gbuffer.

Sure thing, I'll add a prebuilt release with the assets soon.

hi, any chance that you can provide the sponza scene asset?
I try one copy from another repo yet it seems does not working, the program crashed when draw gbuffer.

Hi @horusli , a working build with the assets has been uploaded. Please check the releases section. Sorry about the delay, I've been a bit busy.

Sure thing, I'll add a prebuilt release with the assets soon.

hi, any chance that you can provide the sponza scene asset?
I try one copy from another repo yet it seems does not working, the program crashed when draw gbuffer.

Hi @horusli , a working build with the assets has been uploaded. Please check the releases section. Sorry about the delay, I've been a bit busy.

thanks a lot!


Why no voltage divider on wiring diagram?

Everywhere I read that if you power these RF Rx devices with 5V then it is critical to divide the voltage down on the Rx data pin to 3.3V before connecting it to a RPi GPIO input pin otherwise you risk damaging the RPi.
However, the wiring diagram on the main README does not show this? The Rx data pin (potentially at 5V)  is connected directly to the GPIO input (max should be 3.3V) so presumably at risk of damaging it?

I used those modules for years connected directly to the GPIO header.
I didn't measure the DATA voltage, but it didn't pose any problem until now and never heard of anyone damaging his Pi with it.
If unsure, you can put a AMS1117 between the 5V lane and the modules' input. They are usually found very cheap on Alix, Banggood or Gearbest.


[WIP] Provide cn doc

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

i know, this is a long-term pr. just wait for me to translate others

OK. I add WIP(work in progress) in the title, to avoid confusing people

Btw, you don't need to make all document available in a single pull request. Too many documents. You just make sure some parts of it are good.

Btw, you don't need to make all document available in a single pull request. Too many documents. You just make sure some parts of it are good.

ok. got it.

Ping @candyleer @JaredTan95 @YunaiV or me when you think it is ready. Then we can review.

Coverage remained the same at 14.328% when pulling c81183f2aeb4b802cb24a28ce305473726adc69d on IanCao:dev_1 into c592aea8db02293861e45a0e9e34de17d5883a99 on apache:master.

#2096 merged. Is this ready to review?

emm. i agree with u.so i deleted it. btw, i think its time to review @YunaiV @wu-sheng @JaredTan95

@JaredTan95 @YunaiV please review


Offline warning and timeout

The app uses the pcCheck utility to test a roundtrip response time.
The warning text is "Pathway Commons Offline: Please try again later".
Modify warning to

'Slow network response' or more broad than server
'Unable to connect within 5 seconds - continuing to try'

Fixed in 07d1600f218499ff214dcbfca5c6121448606ac5


raw materials

目录

培训

The Hammersmith Infant Neurological Examination (HINE) is a standardised and scoreable clinical neurological examination that can be used to assess infants from 2-24 months of age. The HINE contains 26 items across 5 domains and summing of scores in each domain provide a global score. More than ten studies of high risk newborns (preterm and term) have demonstrated that this assessment can be used in the diagnosis of cerebral palsy (CP).
The International Clinical Practice Guideline for the Early Accurate Diagnosis of Cerebral Palsy recommends the use of the HINE, particularly in situations where the most predictive tools (general movements and MRI) are not able to be used. This workshop session will provide standardized training in the Hammersmith Infant Neurological Assessment with an original author of the HINE. All items in the HINE will be presented with the correct approach to administration and scoring. Infants aged between 6-24 months will be used to train the participants in small groups in accurate scoring of the HINE.
As part of the Advancing Cerebral Palsy in Queensland project (funded by Advancing Queensland Innovation Program) and Australasian Cerebral Palsy Clinical Trials Network (AusCP-CTN, Centre for Research Excellence that is funded by the NHMRC), we are providing a range of educational training sessions to upskill our clinical force to enable early detection and assessment of children with cerebral palsy.
Training objectives
Outline the current evidence for use of the Hammersmith Infant Neurological Examination (HINE) for the early detection of infants at high risk of CP.
Demonstrate the HINE with three case examples and train clinicians and researchers how to administer the assessment in infants at risk of CP.
Provide an opportunity for participants to score cases of infants at risk of CP on the HINE to determine their risk status.
Understand the role of HINE in prioritising intervention goals.

https://sites.usc.edu/inclab/publications/

https://www.youtube.com/c/movementlesson/about

https://github.com/LaurenKlein/mother-infant-interactions

https://github.com/rjh1026/earlyPredictionOfDisorder/blob/c7538ce874336a382bb31f3defed0a1920afb0c3/summaries/experiments/ReadMe.md

https://github.com/cchamber/Infant_movement_assessment

https://github.com/ostadabbas/Infant-Pose-Estimation


Dev mode prints message repeatedly with debug logging

When you use the -X option you see this message printed over and over in the console:
[DEBUG] (org.codehaus.mojo.pluginsupport.ant.AntHelper) CWWKM2014I: Now looking for CWWKZ0003I: in messages.log.

Fixed by referenced pull request.


Partial array merge

As far as I understood there is no way to handle a merge of a specific item in an array, is that correct?
I would like to update only the object in a specific index leaving the others untouched.
Should I handle this with a custom merge function?

Yup, a custom arrayMerge function would be able to do that. Alternatively if it's based on the object key you could try a custom customMerge that reads the key to determine if your custom array merge should be used.

Thanks, the arrayMerge doesn't seems to fit well because is applied to all the arrays, but implementing a deeper logic to the customMerge seems to work.
I've tried something like this, but if you have some reviews to the snippet I would appreciate.
I'm not skilled in js (especially with lambdas and such). 😄
const x = {
	foo: { bar: 3 },
	array: [
	{
		does: 'work',
		too: [ 1, 2, 3 ]
 	},
	{
		does: 'yep',
		too: [ 1, 1, 1 ]
	}]
}

const y = {
	foo: { baz: 4 },
	quux: 5,
	array: {
		 '__deepmerge_index': 0,
		does: 'replaced',
		too: [ 4, 5, 6 ]
	}
}

const deepmerge_index_key = '__deepmerge_index';

const mergeOnIndex = (obj1, obj2) => {
  if (Array.isArray(obj1) && typeof obj2 === 'object') {
    if (obj2.hasOwnProperty(deepmerge_index_key)) {
      var indexToChange = obj2[deepmerge_index_key];
      delete obj2[deepmerge_index_key];
      obj1[indexToChange] = obj2;
      return obj1;
    }
  }
  return merge(obj1, obj2)
}

const merged = merge(x, y, {
  customMerge: (key) => mergeOnIndex
});

const output = {
	foo: {
		bar: 3,
		baz: 4
	},
	array: [
	{
		does: 'replaced',
		too: [ 4,5,6 ]
	},
	{
		does: 'yep',
		too: [ 1, 1, 1 ]
	}]
}


Add client aws_opensearch

@XuanYang-cn this PR lacks optimal settings for AWS Opensearch to give best performance. What is the best way to add those improvements here?

@navneet1v
feel free to optimize and submit another request.
We are not expert on optimizing opensearch.
Or you can give some critical optimization?
I'm not sure Disable the refresh interval and disable replica will a an option in production.

@alwayslove2013 let's take a closer look at this


[BugFix] Fix logic in prepdocs to always update search index

Purpose
Fixes #1063
I think this line of code was accidentally indented.
Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type
What kind of change does this Pull Request introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Delete an md5 file, run scripts/prepdocs.sh, see logs from update_content call:

Splitting 'role_library.pdf' into sections
Uploading blob for whole file -> role_library.pdf
Batch Completed. Batch size  16 Token count 3246
Batch Completed. Batch size  16 Token count 3167
Batch Completed. Batch size  16 Token count 3201
Batch Completed. Batch size  10 Token count 1949

Thanks for fixing this!


Add support for memory tracing

(CI fails on 32-bit platforms due to https://github.com/janestreet/memtrace/issues/7)

CI problem will be fixed by https://github.com/ocaml/opam-repository/pull/17758 and https://github.com/ocaml/opam/pull/4462.


Cannot read property 'insertId' of undefined

I use the node-mysql insert data into table,but the return  insertId shows undefined, how to solve this problem
query($sql.insertUser, [req.program_id, req.openid, req.nickName, req.avatarUrl, req.city, req.province, req.gender, req.country], function(err, results, fields) { 			console.log('id:', results.insertId); 			callback(results.insertId); 		});
throw err; // Rethrow non-MySQL errors
^
TypeError: Cannot read property 'insertId' of undefined
at /home/prophet/node-wallet/pay/dao/wechatDao.js:67:35
at Query._callback (/home/prophet/node-wallet/pay/conf/db.js:23:5)
at Query.Sequence.end (/home/prophet/node-wallet/pay/node_modules/mysql/lib/protocol/sequences/Sequence.js:86:24)
at Query.ErrorPacket (/home/prophet/node-wallet/pay/node_modules/mysql/lib/protocol/sequences/Query.js:88:8)
at Protocol._parsePacket (/home/prophet/node-wallet/pay/node_modules/mysql/lib/protocol/Protocol.js:280:23)
at Parser.write (/home/prophet/node-wallet/pay/node_modules/mysql/lib/protocol/Parser.js:75:12)
at Protocol.write (/home/prophet/node-wallet/pay/node_modules/mysql/lib/protocol/Protocol.js:39:16)
at Socket. (/home/prophet/node-wallet/pay/node_modules/mysql/lib/Connection.js:103:28)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at readableAddChunk (_stream_readable.js:176:18)
at Socket.Readable.push (_stream_readab

You are not using Node.js style callbacks correctly. You are not checking the err value. Read https://nodejs.org/dist/latest-v8.x/docs/api/errors.html#errors_node_js_style_callbacks for more information on what Node.js style callbacks are and how you should interact with them.


API: Waves.ripple(element)

Run Effect.show(e, element) on an element via an API call, and Waves.ripple(element) could mimic a click event occurring at the centre of the element, where element is a string passed to a querySelector.
Simulate mousedown and an immediate mouseup in the centre of element. I'll add this tonight, and this will simplify the mouseover/mouseleave/hover effect (requested in issue #105) as you can simply call Waves.ripple() on mouseover.
Question: Would Waves.ripple(element) check element for .waves-effect classes, or should it assume (for performance) that the necessary classes have already been set; since the user can [and should] set these through the HTML template and/or Waves.attach()?
In future, options to the function (If we used Waves.ripple(element, options)) could include setting the position of the ripple, timing etc.

Solved in pull request #113. It does not check for .waves-effect. It includes a warning in the documentation that .waves-effect should already be present on the element and could be added via Waves.attach().
Waves.calm(elements) was also added in that pull request to remove all ripples from an element. Useful when a ripple has no timeout.

Merged.


Training: maximizing the likelihood

Hi,
Thanks for your paper! I've got a question concerning the training process. You wrote that 'the entire network is trained by maximizing the likelihood of generating the target future time series using backpropagation through time'. Where can I find the likelihood part in the code? I can only see that gradients are calculated using tf.gradients and they're being applied using the Adam optimizer.
Thank you very much!

Thanks for your interest in our work and sorry for the late reply. Here are some comments:
Training: Maximizing the likelihood

Using MAE as the loss function can be seen as maximizing the likelihood with a certain type of Laplacian distribution.
Similarly, using MSE as the loss function can be seen as maximizing the likelihood with a Gaussian distribution with fixed variance.
To do relatively more general likelihood, you may refer to Variational inference (one example is VAE) for more information.


[Event Request] codeunit 99000815 "Reservation-Check Date Confl.": DateConflict

Object: codeunit 99000815 "Reservation-Check Date Confl."
Function: DateConflict
Integration Event:
OnBeforeDateConflict(var Date: Date);

It's very important that the Date is var!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Support custom properties (variables)

It would be awesome to have var(--foo) support via something like https://github.com/postcss/postcss-custom-properties

Are you sure this has something to do with this prefixer? I don't get the problem actually :/

This may or may not be considered in scope. But the project I linked to let's me write standard CSS variables in my .css files. Then it inlines the variables for older browsers. For example:
webpack.config.js
module.exports = {
  ...,
  postcss: [
    autoprefixer({browsers: ['>5%']}),
    customProperties({variables: theme}),
  ],
}

main.css
.my-class {
  border: 1px solid var(--myColor)
}

With inline-style-prefixer, I'd like to similarly be able to use CSS variables in my inline CSS:
const prefixer = new Prefixer({
  userAgent: navigator.userAgent,
  variables: theme
})

const defaultStyle = prefixer.prefix({
  border: '1px solid var(--myColor)',
})

What you are doing now is considered best practice and mixing weird CSS syntax into inline style is rather uncommon.
Anyways this has nothing to do with the prefixer at all. You could write your own tool to "replace" those values savely.


Latest Sauce response gives no browser status

Currently our browser badge is just showing "unknown":

...because the official Sauce badge itself is showing the same:

Possibly due to the latest Sauce results not reflecting the last Travis build of master? This could potentially be fixed by switching the badge to URL http://badges.herokuapp.com/travis/walmartlabs/little-loader/sauce/wml-little-loader, which specifically attempts to correlate the master Travis build with particular Sauce jobs instead of just using the latest (potentially non-master) Sauce build, but that's not working either (I think because it expects to correlate the build name/number in a certain way).

@exogen -- Dumb question: Have you tried restarting the master build and see if a new build takes?

@ryan-roemer Not yet, but I'll give it a shot.

Should update once Sauce expires their own SVG badge.
Querying the API rather than the cached Sauce badge shows fresh results:


2018-9-22: Elasticsearch bucket aggregations

Feel free to write any comments you have for the Elasticsearch bucket aggregations tutorial.

Hi iridakos can you help me with,
I want to find the common doc counts of aggregation on top authors and top co-authors which are fields inside biblio data field of source in an index.
What I am currently doing is:
1.Calculating Aggregation on top 10 authors.(A,B,C,D.....).
2.Calculating Aggregation on top 10 co-authors (X,Y,Z,....).
3.Calculating doc count of intersection like count of common docs between these pairs :
[(A,X), (B,Y)....]. <-----RESULT
I tried sub-bucket aggregation but it gave me : [A:(top 10 corresponding A), B:(top 10 corresponding B).....].

Hi @the-vishal ,
I am not sure I totally understand the case.
Suppose you aggregate on the a field (author) with a terms aggregation. If in that aggregation you add a sub-aggregation for the other field (co-author) then it will bring you just the co-authors of the books that the parent bucket is the author so, yes, you are correct, that doesn't solve your problem.
At the moment, I can't find another solution other than proceeding with two top level terms aggregations on author and on co-author.
If you could post some sample data explaining what you would like to retrieve it would be helpful to understand the case better.
Cheers :cat:

I couldn't find the follow up tutorial on implementing facets in rails. If it's been posted, would you please provide me with its link.

@alis-khadka Hi, unfortunately I haven't written one yet. If I find the time to write one I will post an update to this thread as well.

@iridakos  eagerly waiting for the follow up. Been a week since i have been stucked on facets

@alis-khadka I don't think I'll publish it any time soon because I am very busy this period.

Would you mind, if you provide me with some basic guidelines so that i can have a overview on how to implement facets.

@alis-khadka Unfortunately, it's not that simple and I don't have the time to do so. I think you can find tutorials online about this subject.


feat: collapsible sidebar

https://github.com/Agenta-AI/agenta/issues/587

Hey @aakrem, I had updated the PR. Please approve for workflows.
Thanks

Yeah, I had seen it earlier but forgot to fix after making changes. Will do it.

@aakrem Footer changes are done

@MohammedMaaz can you help here regarding the antdesign issue ?

@VenkataRavitejaGullapudi  can you add to the bottom new component contai border-right: 1px lightgrey solid;
It will then look continuous line

@aakrem, It is not possible as collapsible button is being added by ant design sider. I think this border is added in the agenta codebase itself will check and adjust that border.

@aakrem Committed the changes. Please have a look when you are free. Thanks.

yes look really cool
last change is blue color in the dark mode let's just remove it. and we are hopefully done :)

@aakrem Fine. As It is the default color of darkmode in ant.design, just left it. Will change and commit now.

@aakrem committed the changes. :)

@all-contributors please add @VenkataRavitejaGullapudi  for code


same-origin

~/dev_projects_book_often/webRTC/webrtc-web/step-04$ static .
serving "." at http://<IP_ADDRESS>:8080
but
http://localhost:8080/index.html
after press T12:
The FetchEvent for "http://localhost:8080/index.html" resulted in a network error response: the promise was rejected.
service-worker.js:38 Uncaught (in promise) TypeError: Failed to execute 'fetch' on 'ServiceWorkerGlobalScope': 'only-if-cached' can be set only with 'same-origin' mode
at service-worker.js:38
socket.io.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
main.js:7 Uncaught ReferenceError: io is not defined
at main.js:7
The FetchEvent for "http://localhost:8080/index.html" resulted in a network error response: the promise was rejected.
service-worker.js:38 Uncaught (in promise) TypeError: Failed to execute 'fetch' on 'ServiceWorkerGlobalScope': 'only-if-cached' can be set only with 'same-origin' mode
at service-worker.js:38
A bad HTTP response code (404) was received when fetching the script.
Failed to load resource: net::ERR_INVALID_RESPONSE

Hi @boboyada
Thanks a lot for reporting. This sounds like it could be related to this bug.
To be safe, have you run npm install from step-04 folder before running it? Note that installing from a different folder would not make it. It needs to be installed on each folder.
Also, could you try clearing the application storage and refreshing the page?
You can do that like this:

Enter the follow URL in your chrome browser: chrome://appcache-internals/
There you will see a list of every application cache you have in storage with the possibility to remove any of them.


SQL Server integration

Hi,
I've added SQL Server as an option in a fork.  Before I submit the PR, I have a question regarding options.  It seems the status quo is to provide relatively few options.  I think for SQL Server, adding instance would be the bare minimum, but my instinct was to add a few more.  Which way do you prefer to lean, i.e. would you want ssl and/or the bottom row in or out?

Hi @simonmcconnell! Let's go lean. You can always convert the smart cell to code if you need additional options. :)

Sure thing.  I'm not sure if it is viable to implement the SQL query cell.  Tds requires query parameters to be given a name, e.g. @SomeName.  It doesn't seem to support the ? method of parameter substitution.
Given that SQLCell.to_quoted can only currently name a parameter based on the index, users would have to ensure they name each parameter @1, @2, etc in order they're used in the SQL Cell.
p1 = %Tds.Parameter{value: 1018, name: "@1"}
p2 = %Tds.Parameter{value: 1019, name: "@2"}

SELECT tagid, timestamputc, tagvalue FROM sometable WHERE tagid IN ({{p1}}, {{p2}})

all to_quoted gets as attrs is
sql_cell.to_quoted.attrs: %{
  "cache_query" => true,
  "connection" => %{"type" => "sqlserver", "variable" => "conn"},
  "query" => "SELECT tagid, timestamputc, tagvalue\n  FROM sometable\n  WHERE tagid IN ({{p1}}, {{p2}}",
  "result_variable" => "result",
  "timeout" => nil
}

and I don't see how I could get the name from the Parameter down in parameterize.

Could you assign random names (@p1, @p2, etc). This would be similar to PostgreSQL, which has to use $1, $2, etc. WDYT?

@simonmcconnell is there a reason that the user should define the parameters explicitly? The idea with SQL cell is to interpolate regular variables. Ideally if they have number = 1018, then in the query they do {{number}}, we could replace it with @1 and automatically build %Tds.Parameter{value: number, name: "@1"} in the parameter list.

That could work. I didn't consider that.
I haven't touched Tds for a few years before this week, but as far as I understand, you must pass a list of %Tds.Parameter{}s to Tds.query, so I was running with that. It might be confusing if the SQL cell takes plain old values when the library does not.

It might be confusing if the SQL cell takes plain old values

It's fine, the user can see the underlying code, and the point of SQL cell is that the user doesn't have to know specifics of the particular database driver :)

I'll give that a go.  Thanks for the feedback lads.


ImportError: cannot import name 'get_num_classes' from 'torchmetrics.utilities.data'

Traceback (most recent call last):
  File "main.py", line 7, in <module>
    import pytorch_lightning as pl
  File "/home/users/peikaili/.conda/envs/openue/lib/python3.8/site-packages/pytorch_lightning/__init__.py", line 20, in <module>
    from pytorch_lightning import metrics  # noqa: E402
  File "/home/users/peikaili/.conda/envs/openue/lib/python3.8/site-packages/pytorch_lightning/metrics/__init__.py", line 15, in <module>
    from pytorch_lightning.metrics.classification import (  # noqa: F401
  File "/home/users/peikaili/.conda/envs/openue/lib/python3.8/site-packages/pytorch_lightning/metrics/classification/__init__.py", line 14, in <module>
    from pytorch_lightning.metrics.classification.accuracy import Accuracy  # noqa: F401
  File "/home/users/peikaili/.conda/envs/openue/lib/python3.8/site-packages/pytorch_lightning/metrics/classification/accuracy.py", line 18, in <module>
    from pytorch_lightning.metrics.utils import deprecated_metrics
  File "/home/users/peikaili/.conda/envs/openue/lib/python3.8/site-packages/pytorch_lightning/metrics/utils.py", line 22, in <module>
    from torchmetrics.utilities.data import get_num_classes as _get_num_classes
ImportError: cannot import name 'get_num_classes' from 'torchmetrics.utilities.data'

Just follow the readme file and show this error

it can be solved by update to new version

solution：
pip install --upgrade pytorch-lightning


VB Strategy doc feedback

Hello.
When reading the VB strategy doc I felt something important missing.
I have no problems with VB being a more stable language than say C#.
However, I think it's important that VB can consume APIs from C# and F# especially for features that is expected to have a wide impact such as required members.
In addition; I have struggled in past with Unsafe APIs such as ImageSharp and VB. While not being critical to write unsafe code in VB IMHO (and possible this even a benefit for VB) I think consuming unsafe APIs makes sense even in VB.
So what I felt was missing from the strategy for VB was a goal to let VB consume most if not all of C# and F# APIs/ABIs.

Document details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 58d6da49-a963-5f83-ccce-284cd3d5615b
Version Independent ID: 0539139d-2c47-71e7-a2c4-bad405c7efbd
Content: Visual Basic language strategy - Visual Basic
Content Source: docs/visual-basic/getting-started/strategy.md
Product: dotnet-visualbasic
GitHub Login: @KathleenDollard
Microsoft Alias: kdollard

Thanks for the note and clarification @mrange
Yes, you did interpret the "consumption only" approach correctly.
We are in the process of having these new articles translated into all the languages supported on the platform. If the translation doesn't capture the spirit correctly, let us know.


GetHashEntryLocale comments

In GetHashEntryLocale():
// Storm_2016.dll: 150209D9
// If (locale matches or is neutral) OR (platform matches or is neutral), remember this as the best entry
// Also remember the first matching entry for Starcraft maps
if(pHash->lcLocale == 0 || pHash->lcLocale == lcLocale)
{
    if(pHash->Platform == 0 || pHash->Platform == Platform)
    {
        pBestEntry = pHash;
    }
}

The comment says "OR" but the the best entry only get updated when (locale matches or is neutral) AND (platform matches or is neutral). I am not sure if the comment is wrong or the code is wrong but it has been like that since this code was added in 2016.
The comment also states remember the first matching entry for Starcraft maps but it doesn't do anything in the code about that.
I am also curious about another comment just above:
// Only do that for non-0 locale&platform, because for loc&plat=0, there's different
// processing in Warcraft III vs. Starcraft, which is abused by some protectors.

In a previous commit it used to also say: some Warcraft III maps have several items with neutral locale&platform, which leads to wrong item being returned. Is my understanding correct that, in Warcraft III,  for neutral locale&platform the correct entry to return is the last matching one?

The comment says "OR" but the the best entry only get updated when (locale matches or is neutral)
AND (platform matches or is neutral).

The comment only applies to the next line.

Is my understanding correct that, in Warcraft III, for neutral locale&platform the correct entry to return is the last matching one?

Yes. Warcraft III returns the last matching entry.

Please, just let it go. I spent quite lot of time with tuning this algorithm to match Warcraft III and all the god-damn MPQ twisters, so caller protectors. If the comment is wrong, then you can live with it. Or, prepare a pull request for updated comment.

The question was to understand if the comment is wrong or the code which seemed like something important but you disagree.

I fixed the comment: 7a664bf6be4377aabe03f118fcdb6d1d3abc48f5


how to switch between tabs by swiping left and right

Describe the feature
hi，I want to enable users to switch between tabs by swiping left and right. Can you provide me with an example of how to implement this feature using ，thanks. And i also want enable user scroll in every single tab.
Relevant code
No response

this is often used in mobile apps

@GodGavin Thank you for filing this issue. This seems like it would be useful, so we will implement this soon. Thank you for your patience.


Update Golang Version

Golang 1.13 was released over a year ago and reached EOL with the release of 1.15 in 2020/08/11.
Kubernetes itself is already on 1.15, we should update too.
It might also be worth investigating if we can get automated reminders/updates with new Golang versions.
Is this a BUG REPORT or FEATURE REQUEST?:
/kind enhancement
Sorry if there is already someone working on it or an issue tracking this, I didn't find it.

We indeed should bump the version. I'm not aware of a duplicate Issue neither.
Any volunteers to take this one? @kwiesmueller ;)

I'll give it a take as soon as I can.
If somebody else is faster, just assign it to yourself so i don't start at the same time.

/assign


Fix docs rendering issue

Newlines in updated well drilling cost correlation were causing rendering issue in docs, now fixed:

Thanks for tracking that down, but when I look at:
https://nrel.github.io/GEOPHIRES-X/parameters.html#economics
I don’t see the fix… maybe there is an update I have to wait for in order to see it in Production?
From: Jonathan Pezzino @.>
Sent: Monday, April 22, 2024 1:14 PM
To: NREL/GEOPHIRES-X @.>
Cc: Malcolm Ross @.>; Review requested @.>
Subject: [NREL/GEOPHIRES-X] Fix docs rendering issue (PR #187)
Newlines in updated well drilling cost correlation were causing rendering issue in docs, now fixed:
Screenshot.2024-04-22.at.12.10.39.png (view on web) https://github.com/NREL/GEOPHIRES-X/assets/4056124/84e5e131-cb2b-4962-a041-31b2847ac4f1

You can view, comment on, or merge this pull request online at:
https://github.com/NREL/GEOPHIRES-X/pull/187
Commit Summary

d461f5f https://github.com/NREL/GEOPHIRES-X/pull/187/commits/d461f5f26fa9fe3a63a9ca92cd75264952c07bd0  Fix parameters rendering by removing newlines from well drilling cost correlation tooltip.
de0e3ef https://github.com/NREL/GEOPHIRES-X/pull/187/commits/de0e3efe75ea7fd4f09d08c91c96cfc677665d20  Update geophires-request.json

File Changes
(2 https://github.com/NREL/GEOPHIRES-X/pull/187/files  files)

M src/geophires_x/Economics.py https://github.com/NREL/GEOPHIRES-X/pull/187/files#diff-372dea2554a92733824c98709c9bdb5720c183c31762c3795bd3990f069a2f24  (37)
M src/geophires_x_schema_generator/geophires-request.json https://github.com/NREL/GEOPHIRES-X/pull/187/files#diff-3d85ef79807fc6c25a758a698fd3a7095750bd27ea52341700e1dad94885b5f6  (32)

Patch Links:

https://github.com/NREL/GEOPHIRES-X/pull/187.patch
https://github.com/NREL/GEOPHIRES-X/pull/187.diff

—
Reply to this email directly, view it on GitHub https://github.com/NREL/GEOPHIRES-X/pull/187 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGVYT2K3KQWHS57MCJHD7TY6VOORAVCNFSM6AAAAABGTLOUTKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI2TOMRYGA4TEMY .
You are receiving this because your review was requested.  https://github.com/notifications/beacon/AWGVYTYYHHRAKGXHGGONLG3Y6VOORA5CNFSM6AAAAABGTLOUTKWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHINC27TM.gif Message ID: @.*** @.***> >

I don’t see the fix… maybe there is an update I have to wait for in order to see it in Production?

@malcolm-dsider correct, this won't take effect until the PR is merged.

Confirmed docs at https://nrel.github.io/GEOPHIRES-X/parameters.html#economics are rendered correctly.


Update best-practices-security-and-improvements-for-mendix-applicatio…

Added a bullet concerning security on inheritance (apply it to the specialization)

Hi Stephan,
Please take a minute to sign the CLA.
Thanks,
Adam

Hi Stephan,
I requested an internal review of this PR and these were the comments:

This is a design decision and is very subjective (and not a best practice).
Mendix will look at the access rules of the specific object; this means that when performing a query on a superclass entity: Instances of the superclass will have access rules of the superclass applied to them; Instances of subclasses will have access rules of the subclass applied to them.
Based on this review, I will have to close this PR.
Thanks.


Upgrade node-fetch to latest minor

Upgrade node-fetch to latest minor
same as https://github.com/meggsimum/geoserver-node-client/pull/59 but also adds version to package.json

not needed necessarily. close because of https://github.com/meggsimum/geoserver-node-client/pull/59


[FEATURE] Use stable instead of nightly

I'm on a distro that due to it using musl (rather than gnulibc) will likely never work with rust nightly. I love using EWW and I'd love to use it again, but unfortunately the reliance on nightly makes it impossible. I could compile nightly, but that would mean no updates, and is just in general discouraged.

This would also help getting eww packaged for debian/ubuntu as we only support/ship stable rustc

Same issue on Gentoo, there is no good way to get eww packaged at the moment.

Done in 9ca98448cca5b9b149d6106e1bc9933f96a65cbd!


feat: move "basePath" /qod/v0 to "url"-property

What type of PR is this?
Add one of the following kinds:

correction
enhancement/feature

What this PR does / why we need it:
Remove the basepath and move this to the "url"-property.
Which issue(s) this PR fixes:
Fixes #251

@hdamker & @jlurien:
Added the suggestion of Herbert.
Please review again.

LGTM


Comment Sector and Standardize with Arc

What does the pull request do?

Add comments to the new Sector shape. We really need to require this before a merge.
Changes the Sector's Angle property to SweepAngle to match with Arc
Updates some code formatting
Arc also received some similar updates while reviewing code side-by-side

This is a follow-up to #8667
What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[x] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 0.10.999-cibuild0023184-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

Thanks!


[Bug]: Stepwise Determination Parser "ghost" entries

Steps to reproduce the bug
1. Sometimes (possibly everytime?) I will add a determination.
2. Then I will see the exact same string in the list, but with a smaller count
3. And then I click on it
4. But no collection objects show up

Caching issue?
Backend issue?

Screenshot
Pre-adding determinations (note: string is highlighted):

Post-adding determinations, shows up again:

Nothing shows up when "Set" is clicked:

Expected behavior
Should all be added and properly removed from list
Additional Screenshots
No response
Environment
Production
Sandbox Used
No response
Version
0.26.0
Browser Used
Chrome

In the case outlined above, 46 determinations were created, as validated by checking in "Data" and "Taxon Determinations"

Console of a "ghost" entry:

Can this be taken care of in next update? I basically can't use this task anymore b/c of all the ghost entries.

Any update on this? Still basically useless for me.

@tmcelrath sorry, I think we figured this out as a missmatch that was space related or some-such, but never ran a fix, we'll prioritize.


tci-development/meta-tci is not found

https://github.com/balena-os/balena-tci/blob/7ccd0d3dfc39759fb1617920d8dea756863d42ed/.gitmodules#L9-L12
See: https://github.com/tci-development
This is also causing the hourly renovate runs to log an error for this repo:
2024-08-29T16:52:16.2101602Z  INFO: Renovate is exiting with a non-zero code due to the following logged errors
2024-08-29T16:52:16.2104297Z        "loggerErrors": [
2024-08-29T16:52:16.2104740Z          {
2024-08-29T16:52:16.2105098Z            "name": "renovate",
2024-08-29T16:52:16.2105566Z            "level": 50,
2024-08-29T16:52:16.2106047Z            "logContext": "1_Iassklxt0Rnwh5Pt1Qm",
2024-08-29T16:52:16.2106794Z            "repository": "balena-os/balena-tci",
2024-08-29T16:52:16.2107920Z            "currentDigest": "81b58129bed53c4f28f1ced3e29474d3f2beffcc",
2024-08-29T16:52:16.2108673Z            "currentValue": "dunfell",
2024-08-29T16:52:16.2109301Z            "datasource": "git-refs",
2024-08-29T16:52:16.2110150Z            "packageName": "https://github.com/tci-development/meta-tci.git",
2024-08-29T16:52:16.2110894Z            "followTag": null,
2024-08-29T16:52:16.2111383Z            "packageFile": ".gitmodules",
2024-08-29T16:52:16.2111897Z            "pinDigests": false,
2024-08-29T16:52:16.2112378Z            "rollbackPrs": false,
2024-08-29T16:52:16.2112896Z            "updatePinnedDependencies": true,
2024-08-29T16:52:16.2113502Z            "unconstrainedValue": false,
2024-08-29T16:52:16.2114024Z            "err": {
2024-08-29T16:52:16.2114427Z              "task": {
2024-08-29T16:52:16.2114856Z                "commands": [
2024-08-29T16:52:16.2115392Z                  "ls-remote",
2024-08-29T16:52:16.2116079Z                  "https://github.com/tci-development/meta-tci.git"
2024-08-29T16:52:16.2116688Z                ],
2024-08-29T16:52:16.2117123Z                "format": "utf-8",
2024-08-29T16:52:16.2117623Z                "parser": "[function]"
2024-08-29T16:52:16.2118129Z              },
2024-08-29T16:52:16.2119262Z              "message": "remote: Repository not found.\nfatal: repository 'https://github.com/tci-development/meta-tci.git/' not found\n",
2024-08-29T16:52:16.2128870Z              "stack": "Error: remote: Repository not found.\nfatal: repository 'https://**redacted**@3.25.0/node_modules/simple-git/src/lib/plugins/error-detection.plugin.ts:42:29)\n    at PluginStore.exec (/usr/local/renovate/node_modules/.pnpm/simple-git@3.25.0/node_modules/simple-git/src/lib/plugins/plugin-store.ts:54:29)\n    at /usr/local/renovate/node_modules/.pnpm/simple-git@3.25.0/node_modules/simple-git/src/lib/runners/git-executor-chain.ts:124:42\n    at new Promise (<anonymous>)\n    at GitExecutorChain.handleTaskData (/usr/local/renovate/node_modules/.pnpm/simple-git@3.25.0/node_modules/simple-git/src/lib/runners/git-executor-chain.ts:121:14)\n    at GitExecutorChain.<anonymous> (/usr/local/renovate/node_modules/.pnpm/simple-git@3.25.0/node_modules/simple-git/src/lib/runners/git-executor-chain.ts:97:40)\n    at Generator.next (<anonymous>)\n    at fulfilled (/usr/local/renovate/node_modules/.pnpm/simple-git@3.25.0/node_modules/simple-git/dist/cjs/index.js:52:24)\n    at processTicksAndRejections (node:internal/process/task_queues:95:5)"
2024-08-29T16:52:16.2137046Z            },
2024-08-29T16:52:16.2137455Z            "msg": "lookupUpdates error"
2024-08-29T16:52:16.2138001Z          }
2024-08-29T16:52:16.2138345Z        ]

Any idea what happened here @floion ?


Update Electron to 1.4.1

This PR will update Electron to 1.4.1, and fix accelator behavior to suit it.

Rename from electron-prebuilt to electron.

See: http://electron.atom.io/blog/2016/08/16/npm-install-electron

Windows: Use the accelerator Ctrl+Y of redo command (to suit Electron 1.4.1)

See: https://github.com/electron/electron/pull/7236
NOTE: Marp is not using role: undo, redo and selectall. These role have been found that don't work rightly in CodeMirror.

I have skipped updating too much :sweat_drops:


Dropdown names are inconsistent across the website and sketch library

Dropdown names are inconsistent across the website and sketch library

@steviesharp123 Is this issue still appearing in the site and kit?
Could you give an example of the inconsistencies?

It is a known issue that they are inconsistent in code and the kit. The code has some legacy naming issues with dropdown that will be fixed in the next major breaking change release.

@aagonzales was going through older issues and wasn't sure about the rename bit. At the moment, our hope with the component names would be to keep the following:

Dropdown
Multiselect
Combobox

I know in the sketch kit they're all grouped under dropdown and then use that name, is there any kind of change we should make on our end? Not sure how to best align here on naming.

I was speaking to the size prop names as the known inconsistency with the naming.
These are the dropdown component names presented in the kit. I guess he's referring to the default name. We nest all three dropdown types under dropdown so it would be weird to have a dropdown/dropdown in the kit.

Going to close since we are no longer maintaining our Sketch libraries.


Styling Entries

Can I use custom styles (bold, italicized, colored,...) on certain invoice entries?

Hello, You can try adding html tags to your parameters and html . That should work since it's all html based.


Peer logical network of one selector network in a policy object affects policy rule for other selector network in the same policy object

Below PR addresses this issue
https://github.com/Huawei-PaaS/CNI-Genie/pull/146
so this issue can be closed


[FR] Add snippet

Is it possible to add a snippet function?
For example, entering ag-removeparam can generate a line example.com$removeparam=.
Although it looks like you've finished typing this, I was actually hoping to add a keyword prompt.
This way I can just type ag-re... and I can select the snippet I need.
Thank you.

As I recall, this type of things requires adding a "language server" so this duplicates #24.
I wish we could do this at some point, but generally, this is a very complicated task.


Add test cases to Covid-19 Connector

Purpose
$subject
Goal
Add test cases covering all the remote functions in the connector - 10 test cases added
Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Test environment

Java 11
SL Alpha 5

Closing the PR since we have decided not to add test cases for open-api connectors


Add tvOS deployment target

This allows JSONWebToken.swift to be added to tvOS projects.

seems like there is something odd with the Travis configuration

@maxfell The travis config is using Xcode 7, which obviously doesn't have tvOS support.
Would you be able to change the line in this PR so travis passes? I think either xcode72 or xcode73 should work.
https://github.com/kylef/JSONWebToken.swift/blob/master/.travis.yml#L2
- osx_image: xcode7
+ osx_image: xcode72

Ha! It failed another time. This time due to something unrelated. I created a PR for it: https://github.com/kylef/JSONWebToken.swift/pull/24

I've fixed this up, squashed and merged as https://github.com/kylef/JSONWebToken.swift/commit/bc1f1ef7440bc2873c7ed0ccce43884ac743e1f1.


Added Likes/Posts to Facebook and Twitter

This PR:
-Adds organic posts, promoted posts, likes, and comments to facebook analytics
-Adds followers and likes for twitter analytics
-Bumps gem to 0.5.3


Handle assets with capability field.

Signed-off-by: nassarmu10<EMAIL_ADDRESS>Closes #131

@Mohammad-nassar10 can you please also update helm/afm/values.sample.yaml


Fix StatefulSet spec

Deploying the chart the following error appear:
# helm install -nvzeebe --namespace default zeebe-cluster
Error: release wms-zeebe failed: StatefulSet in version "v1" cannot be handled as a StatefulSet: v1.StatefulSet.Spec: v1.StatefulSetSpec.VolumeClaimTemplates: []v1.PersistentVolumeClaim: v1.PersistentVolumeClaim.Spec: v1.PersistentVolumeClaimSpec.AccessModes: []v1.PersistentVolumeAccessMode: decode slice: expect [ or n, but found ", error found in #10 byte of ...|ssModes":"ReadWriteO|..., bigger context ...|"metadata":{"name":"data"},"spec":{"accessModes":"ReadWriteOnce","resources":{"requests":{"storage":|...

Issue is in statefulset spec in accessModes definition.
Original:
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      accessModes: {{ .Values.pvcAccessModes }}
      storageClassName: {{ .Values.pvcStorageClassName }}
      resources:
        requests:
          storage: {{ .Values.pvcSize | quote }}

Should be:
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      accessModes:
      - {{ .Values.pvcAccessModes }}
      storageClassName: {{ .Values.pvcStorageClassName }}
      resources:
        requests:
          storage: {{ .Values.pvcSize | quote }}

@phoenixwp hi there.. thanks for reporting this.. can you please share which version of Kubernetes APIs are you using?
Also.. are you changing that in your values file? Because currently, the values file specifies the array inline -> https://github.com/zeebe-io/zeebe-cluster-helm/blob/master/zeebe-cluster/templates/statefulset.yaml#L106
Do you see what I mean?

@phoenixwp I will close this issue as I think that it is already ok as it is, but if you have more information that I might be missing, please drop me a message here and I will re-open it.


Eliminate hardcoded exceptions for kube-system or make it optional

Currently, the service controller is excluding kube-system without a way to change it. This will cause problems when istio runs in kube-system.
See https://github.com/istio/pilot/commit/720d751f5a82dcd746e3b36d8dadee96647c1d17#diff-9b493b4288200b30b3d0953052d6abdaR425

istio managing kube-system without breaking it seems like a much bigger task than just making the excluded namespace configurable
this being said I think we should have a whitelist/blacklist and selector based setup instead of the current 1 namespace vs all namespaces (minus kube-system) setup. but none of that is for 0.2

Issue moved to istio/istio #1411 via ZenHub


Add comparison to sqlboiler on README.md

Hi,
I'd love some help to decide between this project and https://github.com/vattle/sqlboiler?
They look very similar and both seem to generate the proper models. This project generates much less code, which I find interesting...
Thanks

Sqlboiler makes a very sql-like API, which is very different from the object oriented style in xo.  I vastly prefer xo's style.

It would appear that sqlboiler is "yet another query generator". xo generates queries based off "single source of truth" of the actual database schema. I don't know if it's really comparable, as they do two really different things.

It would appear that sqlboiler is "yet another query generator". xo generates queries based off "single source of truth" of the actual database schema. I don't know if it's really comparable, as they do two really different things.

I know that this is from 3 years ago, but I just had to chime in that you described exactly what sqlboiler does.  I use it, and xo seems very, very similar on the surface.

Sqlboiler makes a very sql-like API, which is very different from the object oriented style in xo. I vastly prefer xo's style.

Thanks for the comparison, good to know.  Another difference I note is it seems like xo has a ton more knobs than sqlboiler although I don't know that's always a good thing.


Type signatures vs. proof variables

Take
+-identity′ : ∀ (n : ℕ) → n + zero ≡ n
-- for any Natural number n, prove that n + zero equals n
+-identity′ zero = refl
-- when n is 0...
+-identity′ (suc n) rewrite +-identity′ n = refl
-- when n is the successor of some n !?

Here the comments narrate what goes on the head of the complete ℕ00𝔹 that I am.
Wouldn't it be less confusing to pattern match on something that is not called n in the second clause? E.g.:
+-identity′ (suc n′) rewrite +-identity′ n′ = refl
-- when n is the successor of some n′ ...

This is a matter of style. Some would indeed prefer to do it in the style you recommend.

Would it be worth making a note of this in the book? If yes, I'd be happy to open a PR.


partitionKeys_.count(nestedField->name()) > 0 (0 vs. 0) Unexpected filter on table

Bug description
presto:tpch> SELECT COUNT(*) FROM (SELECT * FROM lineitem WHERE orderkey % 1024 = 0) lineitem LEFT JOIN (SELECT * FROM orders WHERE orderkey % 1024 = 0) orders ON orders.orderkey = 1024;

WARNING: line 1:167: JOIN ON condition(s) do not reference the joined relation and other relation in the same expression that can cause performance issues as it may lead to a cross join with filter

Query 20230725_185956_00003_ya6dn, FAILED, 1 node
Splits: 18 total, 0 done (0.00%)
[Latency: client-side: 0:04, server-side: 0:04] [0 rows, 0B] [0 rows/s, 0B/s]

Query 20230725_185956_00003_ya6dn failed: partitionKeys_.count(nestedField->name()) > 0 (0 vs. 0) Unexpected filter on table tpch.orders, field orderkey

This check was introduced recently: https://github.com/facebookincubator/velox/pull/5614/
    VELOX_USER_CHECK_GT(
          partitionKeys_.count(nestedField->name()),
          0,
          "Unexpected filter on table {}, field {}",
          hiveTableHandle->tableName(),
          field.toString());

System information
M1 Mac
Relevant logs
No response

Did you disabled filter pushdown in Presto?

@Yuhta Yes, I had disabled hive.pushdown_filter_enabled.
Jimmy please close it if this is the expected behavior. thanks.


Package does not work together with php-graph-sdk

https://github.com/facebook/php-graph-sdk/blob/5.4/composer.json#L20
I can't use laravel socialite and this package together. Facebook requires guzzle ~5.0 only.

Facebook is Oauth2, not OAuth 1


how to write client code

I had run server success,  and then how to write client code to test the ShopingChartEntity.
I try to send http request,  but return 404.
curl http://<IP_ADDRESS>:8080/carts/lan -v

Hi @lanwenchang
Hello thanks for playing a little bit with this.
To run the example in a development environment you will need to have the cloudstate proxy running and pointing to where your user role is running as well.
If you have Cloudstate CLI installed you can run this command:
cloudstate run --only-proxy --user-function-port = 8080

Otherwise you will need to manually run the proxy on the docker:
docker run --net = host --name proxy --env HTTP_PORT: 9000 --env USER_FUNCTION_PORT: 8080 cloudstateio / cloudstate-proxy-native-dev-mode: latest

After you have your application and the proxy running, you can make requests to the proxy, one of which could be:
# SET the body of request
export POST = '{"productId": "foo", "name": "A foo", "quantity": 10}'

# Add items to the shopping cart
curl -s -X POST http://localhost:9000/cart/1/items/add -H "Content-Type: application/json" -d "$ POST"

# Repeat operation
curl -s -X POST http://localhost:9000/cart/1/items/add -H "Content-Type: application/json" -d "$ POST"

# Get the shopping cart
curl http://localhost:9000/carts/1

# Get items from the shopping cart
curl http://localhost:9000/carts/1/items

For more information specific to Cloudstate I suggest you access the official project documentation:
https://cloudstate.io/docs/
Or our channel on the Gitter:
https://gitter.im/CloudState-IO/community

You could test via any grpc client, but via http is easier.
  Because of the docker host mode can't work in Mac.  see  https://github.com/docker/for-mac/issues/2716
So I trying to do with cloudstate-cli, unfortunately,  there some wrong in my brew, so I had to fix it.
thanks for your  advice  ：）

Hi @lanwenchang
Did you try this WA ?
This issue is interesting because it means that the same error will also occur with the cloudstate cli since it also depends on the host network to share the necessary namespaces.
I think in your case for now it would be necessary to generate a docker image and test everything via docker. Perhaps the functionality of the Cloudstate CLI for Swarm could help you, but I am having trouble generating new versions of the Cloudstate CLI for MacOS that I have not yet been able to resolve.
But in theory you could run your image of the user role created during the build of the example project with the proxy image via Podlike Swarm, or run everything on the Minikube :)

Any progress @lanwenchang ?

not yet
there some wrong with the cloudstate-ci install
➜  ~ brew install cloudstate-cli
Updating Homebrew...
==> Installing cloudstate-cli from sleipnir/cloudstate-cli
==> Downloading https://github.com/sleipnir/cloudstate-cli/releases/download/0.4.1/cloudstate-0.4.1-osx.tar.gz
==> Downloading from https://github-production-release-asset-2e65be.s3.amazonaws.com/216043821/0d033800-1516-11ea-9a1c-3f8dec95a28b?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200404%2Fus-east-1%2Fs3%2Faws4_
################                                                          22.6%
curl: (56) LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 60

curl: (22) The requested URL returned error: 403 Forbidden
Error: An exception occurred within a child process:
  DownloadError: Failed to download resource "cloudstate-cli"
Download failed: https://github.com/sleipnir/cloudstate-cli/releases/download/0.4.1/cloudstate-0.4.1-osx.tar.gz

Sorry for that but this related of this https://github.com/sleipnir/cloudstate-cli/issues/22

Hi! @lanwenchang  Try again:
brew tap sleipnir/cloudstate-cli
brew install sleipnir/cloudstate-cli/cloudstate-cli

Sorry for the delay I was a little busy in the past few weeks. I believe everything is ok now but let me know if there are still any problems or questions.

Closed due to inactivity


Handle 'remember me' functionality for the client

As the server, I should be able to set the JWT/cookie expiration date as a value other than the default so that the end user can remain logged in to the client for a different period of time to the default of 1 day.

See https://stackoverflow.com/questions/25014872/set-ttl-for-hapi-auth-cookie-for-specific-route as an example implementation


MagnetShockCurrentStatus error

Hi,
When I restart HA after integrating my AXPro  (DS-PWA96-M-WE V1.2.9 build 240621), it only detects 3 devices over the 7 connected to the AXPro.
When I open the loaded devices, they show no sensors.
The devices on the hikvision web page

What I get in HA

The page of the magnet that has been detected

All the detected devices have no sensor on their page like the magnet
Could the naming of the devices be an issue ?
The HA logs after restart
2024-10-09 22:45:43.013 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hikvision_axpro which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-09 22:45:43.014 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-09 22:45:44.208 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hikvision_axpro' accesses hass.helpers.service. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from service directly at custom_components/hikvision_axpro/__init__.py, line 59: hass.helpers.service.async_register_admin_service(, please create a bug report at https://github.com/petrleocompel/hikaxpro_hacs/issues
2024-10-09 22:45:44.229 DEBUG (SyncWorker_1) [hikaxpro] Session_Capabilities response
2024-10-09 22:45:44.229 DEBUG (SyncWorker_1) [hikaxpro] Status: 200
2024-10-09 22:45:44.229 DEBUG (SyncWorker_1) [hikaxpro] Content: b'<SessionLoginCap version="2.0" xmlns="http://www.hikvision.com/ver20/XMLSchema">\n<sessionID>6528b541b15cb2466051c79b1e373ead628c4b774f0f17f8b1718920e2f87b42</sessionID>\n<challenge>cfb9fcedc18f18555b0a6a7750617e9a</challenge>\n<iterations>100</iterations>\n<isSupportRTSPWithSession>true</isSupportRTSPWithSession>\n<isIrreversible>true</isIrreversible>\n<sessionIDVersion>2.1</sessionIDVersion>\n<salt>F17B3EB457CCA28345E58ACF357613E0A919579539385850DCA7C9EF01EEC84A</salt>\n<salt2>0C74FD870FBBE360EEDDEBEC28613CDCE56006A43EC7CCE2D1ED6FE3A1A5EB9F</salt2>\n</SessionLoginCap>\n'
2024-10-09 22:45:44.230 DEBUG (SyncWorker_1) [hikaxpro] Text: <SessionLoginCap version="2.0" xmlns="http://www.hikvision.com/ver20/XMLSchema">
<sessionID>6528b541b15cb2466051c79b1e373ead628c4b774f0f17f8b1718920e2f87b42</sessionID>
<challenge>cfb9fcedc18f18555b0a6a7750617e9a</challenge>
<iterations>100</iterations>
<isSupportRTSPWithSession>true</isSupportRTSPWithSession>
<isIrreversible>true</isIrreversible>
<sessionIDVersion>2.1</sessionIDVersion>
<salt>F17B3EB457CCA28345E58ACF357613E0A919579539385850DCA7C9EF01EEC84A</salt>
<salt2>0C74FD870FBBE360EEDDEBEC28613CDCE56006A43EC7CCE2D1ED6FE3A1A5EB9F</salt2>
</SessionLoginCap>

2024-10-09 22:45:44.230 DEBUG (SyncWorker_1) [hikaxpro] Headers: {'Date': 'Wed, 09 Oct 2024 22:45:44 GMT', 'Server': 'Webs', 'X-Frame-Options': 'SAMEORIGIN', 'Cache-Control': 'no-cache', 'Content-Length': '568', 'Content-Type': 'application/xml; charset="UTF-8"', 'Connection': 'keep-alive', 'Keep-Alive': 'timeout=60, max=99'}
2024-10-09 22:45:44.230 DEBUG (SyncWorker_1) [hikaxpro] End Session_Capabilities response
2024-10-09 22:45:44.230 DEBUG (SyncWorker_1) [hikaxpro] Debug data <SessionLoginCap version="2.0" xmlns="http://www.hikvision.com/ver20/XMLSchema">
<sessionID>6528b541b15cb2466051c79b1e373ead628c4b774f0f17f8b1718920e2f87b42</sessionID>
<challenge>cfb9fcedc18f18555b0a6a7750617e9a</challenge>
<iterations>100</iterations>
<isSupportRTSPWithSession>true</isSupportRTSPWithSession>
<isIrreversible>true</isIrreversible>
<sessionIDVersion>2.1</sessionIDVersion>
<salt>F17B3EB457CCA28345E58ACF357613E0A919579539385850DCA7C9EF01EEC84A</salt>
<salt2>0C74FD870FBBE360EEDDEBEC28613CDCE56006A43EC7CCE2D1ED6FE3A1A5EB9F</salt2>
</SessionLoginCap>

2024-10-09 22:45:44.371 DEBUG (SyncWorker_1) [hikaxpro] Connect response
2024-10-09 22:45:44.371 DEBUG (SyncWorker_1) [hikaxpro] Status: 200
2024-10-09 22:45:44.371 DEBUG (SyncWorker_1) [hikaxpro] Content: b'<SessionLogin version="2.0" xmlns="http://www.hikvision.com/ver20/XMLSchema">\n<statusValue>200</statusValue>\n<statusString>OK</statusString>\n<isRiskPassword>false</isRiskPassword>\n<isActivated>true</isActivated>\n</SessionLogin>\n'
2024-10-09 22:45:44.371 DEBUG (SyncWorker_1) [hikaxpro] Text: <SessionLogin version="2.0" xmlns="http://www.hikvision.com/ver20/XMLSchema">
<statusValue>200</statusValue>
<statusString>OK</statusString>
<isRiskPassword>false</isRiskPassword>
<isActivated>true</isActivated>
</SessionLogin>

2024-10-09 22:45:44.371 DEBUG (SyncWorker_1) [hikaxpro] Headers: {'Date': 'Wed, 09 Oct 2024 22:45:44 GMT', 'Server': 'Webs', 'X-Frame-Options': 'SAMEORIGIN', 'Content-Length': '228', 'Content-Type': 'application/xml; charset="UTF-8"', 'Connection': 'keep-alive', 'Keep-Alive': 'timeout=60, max=99', 'Cache-Control': 'no-cache="set-cookie"', 'Set-Cookie': 'WebSession_03f5f867ad=fc8aa881face7f3e7199e7c48e685a652df007d560252d0195ef9ec0370e248c;path=/;HttpOnly'}
2024-10-09 22:45:44.371 DEBUG (SyncWorker_1) [hikaxpro] End connect response
2024-10-09 22:45:44.777 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up hikvision_axpro platform for sensor
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/homeassistant/helpers/entity_platform.py", line 361, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/hikvision_axpro/sensor.py", line 120, in async_setup_entry
    if zone.zone.magnet_shock_current_status.magnet_shock_current_status is not None:
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'MagnetShockCurrentStatus' object has no attribute 'magnet_shock_current_status'. Did you mean: 'magnet_shock_status'?

I have the same problem, before the ladt update everything was fine. On last update i have also no entyties on the devices. I reverted to v2.1.6 and everything works as normal

@Yanniiiick thank you for report
@Joerivanrokeghem - sadly since I do not have every device and "python" is not compiled it can happen that some error will get through my testing. So you need to really report the issue.

Thanks for fixing it, next time i will report of there is a problem.
We appreciate your work. Thanks!


Chore: bump deps

This PR bumps dependencies (particularly Cosmos-SDK and IS) to versions with an applied Dragonberry patch
Merge with:

https://github.com/neutron-org/neutron-query-relayer/pull/75

Tests run:

https://github.com/neutron-org/neutron-tests/actions/runs/4075030322

I cannot run ignite generate proto-go on this branch and I get a following error when trying to do so:
error while running command /tmp/protoc3399819886 -I /tmp/1199532008 -I /home/foxpy/Work/neutron/proto -I<EMAIL_ADDRESS>-I<EMAIL_ADDRESS>-I<EMAIL_ADDRESS>-I<EMAIL_ADDRESS>-I<EMAIL_ADDRESS>-I<EMAIL_ADDRESS>-I<EMAIL_ADDRESS>-I<EMAIL_ADDRESS>--gocosmos_out=plugins=interfacetype+grpc,Mgoogle/protobuf/any.proto=github.com/cosmos/cosmos-sdk/codec/types:. /home/foxpy/Work/neutron/proto/transfer/v1/query.proto /home/foxpy/Work/neutron/proto/transfer/v1/tx.proto: panic: interfacetype only supports messages with exactly one oneof declaration

Hmm, works pretty good on my machine

Hmm, works pretty good on my machine

Okay, I have just upgraded from 0.25.2 to 0.26.1 and it runs fine.


wallet-ext: fix stake validation issues

stake coin manage transaction include gas budget to input coins

input coins are used for gas as well so we need to include enough coins for that as well

move submit errors to toasts

https://user-images.githubusercontent.com/10210143/216430113-bf68c18c-6a8e-4c7e-865d-6f9d54d9be1a.mov

fix showing negative available amount to stake

before
https://user-images.githubusercontent.com/10210143/216440077-d30c6c51-9f79-454e-bdc8-13f05d06c2b4.mov
after
https://user-images.githubusercontent.com/10210143/216430329-92724d3e-482f-40a1-bae4-cff01c2423d4.mov

fix gas budget validation when unstaking

before
https://user-images.githubusercontent.com/10210143/216439679-f1df11c9-fc35-424c-8228-1f9ebf5ae798.mov
after
https://user-images.githubusercontent.com/10210143/216439731-160d40ce-23c7-431d-9cac-f4a196849564.mov

Could we style/align like so @pchrysochoidis?
https://www.figma.com/file/xu2VnyPAuruNi74UQzGigW/02-Wallet?node-id=5339%3A79512&t=nI7R89uLMvbvy0Xo-1


1.53

A company wants to deploy an application to Azure. The application has the below requirements:

Give the ability to install and provide access to the full .Net framework
Allow administrative access to the operating system
Provide a level of redundancy if an Azure region fail

You decide to deploy 2 Azure Virtual Machines in 2 separate regions. And then you create a
Traffic Manager Profile
Does this solution meet the requirement?
A. Yes
B. No

B

A*


Assertion failed in AGProxyFilter.cpp:790

https://sentry.adguard.com/adg/adguard-android-rs/issues/12188/


Make LibXML::Item use :config for boxing

Any config supplied by upstream was previously ignored and class mapping was expected to be done by LibXML::Node. This resulted in limited abilities of user code in controlling how boxing is done. See #94.
Note that LibXML::Node still does its own class mapping because this is the point of final decision and in many cases it is invoked directly.

Following #94 and this comment in particular. For caching to work properly, i.e. for a LibXML::Node subclass to be able to intercept the box method, it is necessary that LibXML::Item.box calls that subclass' box instead of directly referring to LibXML::Node. This PR makes it possible.
An alternative would be to modify class mapping on the global configuration object and pointing it into a some kind of proxy-class which would then re-dispatch the call to an appropriate class, but that adds an extra call to the call chain.


Event based communication over sockets.

Description

Using Event based communication over sockets using LengthPrefix communication channel.
Channel will now notify when the message is received.
Socket client and server and use one thread each, instead of using new thread at every read.
Related tests and added additional tests.
ToDo : Only main flow is converted to the socket client and server. Other flows like DataCollection is not on this.

@dotnet-bot test Windows_NT / Release Build

@dotnet-bot test

@dotnet-bot test Windows_NT / Debug Build

@dotnet-bot test Windows_NT / Release Build

@dotnet-bot test Windows_NT / Release Build

@dotnet-bot test Windows_NT / Release Build


client: add doc on how to set up tls

@lburgazzoli have you successfully set up tls with jetcd?

not yet, will have a look when get back from holidays

@fanminshi I'm a little busy at the moment so I can't have a look at this

@lburgazzoli not a problem. I am digging into this now.

fixed via https://github.com/coreos/jetcd/issues/162


Sharepoint Embedded: Cannot get list of containers in SPA

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[X] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version
SPFx version
Node.js version
etc

Issue description
After following both the tutorials, currently available for Sharepoint Embedded (Postman, followed by SPA), I wasn't able to get a list of containers in my SPA (https://learn.microsoft.com/en-us/sharepoint/dev/embedded/mslearn/m02-05-hol#test-listing-and-selecting-containers).
In the network-tab of the developer tools, I found that the POST-request to https://login.microsoftonline.com/common/oauth2/v2.0/token returns with an error:

AADSTS500011: The resource principal named api://<client-id> was not found in the tenant named <tenant-id>. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant.

While researching about this error, I came across this stack-overflow question (https://stackoverflow.com/questions/76704063/getting-error-aadsts500011-the-resource-principal-named-was-not-found-in-t) where I don't know whether this is related to the issue I'm facing.
At least, when I follow this advise, and set up an application uri api://d893eb9d-a843-4ef2-8202-5f32bc593f49 on which I created a role, called Container.Manage, after which I went again into the "API Permissions" section and once more granted all permissions available there (ignoring the error message I received Claim is invalid: 40dc41bc-0f7e-42ff-89bd-d9516947e474 does not exist on resource application 00000003-0000-0000-c000-000000000000.), I was able to list the containers. Creating containers also worked, which I tried right after.
Following the guide further, I was not able to list the files of the container, created via Postman - only of the container created via the web interface (https://learn.microsoft.com/en-us/sharepoint/dev/embedded/mslearn/m02-07-hol#test-the-rendering-of-listing-the-contents-of-a-container) - but out of the manual, I should be able to. In Postman, I can see them both, and when I query them to see their internal data, nothing seems to be different there.
What am I doing wrong here? Has this something to do with the way I fixed the first error I was encountering? Is there any additional information I can acquire which can help me looking further into this?

@andrewconnell Thanks very much for providing the video and article.
You've closed my PRs here, but I could see, that the article you've published on your website has the same issues I wanted to fix in the walkthrough here. At least yields to #9447, #9448 and #9449.

WRT my article, I did see one improvement you made to splitting the access token from the authorization header (which I've updated... will take time to get past caching), but the other issues don't apply as best I can tell.

@andrewconnell I'll let you know my thoughts via mail 😊
I'll subscribe to the issue - this is closed, as I now know how to proceed. Would be good if the new material also includes those things. I'll let you know whether it worked when its online.

@SimonSimCity said..

Would be good if the new material also includes those things.

It is... publishing to MS Learning is just a more involved process than making updates to these docs. (IOW, takes a bit more time for the bits to flow through the various branches/reviews/approvals) ;)


Auth - Facebook native: How to get Facebook access token to send it to server

I need to get the facebook acess token after login so i can send it to server in order to use it
I tried:
$ionicFacebookAuth.login().then(function (response) { console.log(response.token) }
but that token is not a facebook token

I had to use ngCordova and call getLoginStatus()

any update ?


Add includes option to ruby_bundle rule for per-gem load path customization

This PR fixes the gem registration logics to load all of the paths specified in the require_paths property of gemspecs
# https://github.com/grpc/grpc/blob/master/grpc.gemspec
Gem::Specification.new do |s|
  s.name = 'grpc'
  s.require_paths = %w( src/ruby/lib src/ruby/bin src/ruby/pb )
  ...
end

instead of loading only the standard, hardcoded path ["lib"].
Also, this PR extends ruby_bundle rule to also accept includes option, which allows us to specify additional library load paths not listed in the gemspecs' require_paths for specific rubygems like this:
ruby_bundle(
    name = "bundle",
    # Specify additional paths to be loaded from the gems at runtime, if any.
    includes = {
        "grpc": ["etc"],
    },
    gemfile = "//:Gemfile",
    gemfile_lock = "//:Gemfile.lock",
)

With both includes and excludes per-gem options at hand, users of ruby_bundle rule have more granular control over gem load paths, possibly addressing issues #85 , #86 , #97.

Thank you for updating the CI settings. I will look into the errors: https://app.circleci.com/pipelines/github/bazelruby/rules_ruby/307/workflows/bdd3ad88-e478-4e37-8029-b16e3ef1b38e/jobs/1073

@mmizutani Keep in mind that ruby version went up to 3.0.1 across the board. Perhaps you might want to update it as well, so that on CI we don't need to build a 2.7 interpreter. The 3.0.1 is pulled with the Docker image.

This, once ready, will be the 0.5.1 release.

Let me know if you'd like to pair on figuring out the broken build issues. I am in San Francisco time zone.

The tests have now been fixed. Thank you for your advice.

Amazing!


Pagination paramaters not showing on graphql query

I've using nextjs & prisma & nexus-prisma plugins but I have a problem Pagination paramaters not showing please check image bellow:

My queryType

My package.json

Please somebody can help!
Thanks.

Hey @tamanhquyen,
I'm pretty sure this issue has been fixed by now. Apologies for the lack of answer, closing now 🙏


Handling ES6 imports with jest using vue-cli and webpack template

Version
1.0.0-beta.15
Reproduction link
https://forums.manning.com/posts/list/0/43203.page#p121739
Steps to reproduce
npm run unit using a SFC that has ES6 in it via an import
What is expected?
Unit test to pass
What is actually happening?
node_modules/vue-introjs/src/index.js:2
    import { DIRECTIVES } from './directives';
    ^^^^^^

    SyntaxError: Unexpected token import

      1 | import { shallow } from 'vue-test-utils'
      2 | import Dashboard from<EMAIL_ADDRESS>    > 3 | import VueIntro from 'vue-introjs'
      4 |
      5 | describe('Dashboard.vue', () => {
      6 |   it('should show the word Overview', () => {

      at ScriptTransformer._transformAndBuildScript (node_modules/jest-cli/node_modules/jest-runtime/build/script_transformer.js:316:17)
      at Object.<anonymous> (test/unit/specs/Dashboard.spec.js:3:19)

The problem here is that you're importing the uncompiled files in vue-introjs. I'm not sure why, because I can't see your setup. You could fix this by setting babel to compile node_modules, although a better solution would be to set jest to use the main file (which it should by default, so I'm a bit confused)
However, this is not an issue with this library.
I see you linked to a post on my book forum, I'd like to help you if you're struggling with the book, but I don't recognise the code you posted. If you post a GitHub repository that reproduces your issue on the Testing Vue Applications forum I'll take a look for you

@ghenry, Hello!
Here is link how to solve similar pbolem ith vuew-awesome. Hope it will help :)