sqlite3 and TypeError errors

This is what happens when I attempt to start on my Raspberry Pi 3B

<EMAIL_ADDRESS>start
node build/index.js

ERR! db A database error occurred. If you don't know what to do, try removing the revcord.sqlite file (will reset all your settings).
ERR! db Error: Please install sqlite3 package manually
ERR! db     at ConnectionManager._loadDialectModule (/home/s7002/revcord/node_modules/sequelize/lib/dialects/abstract/connection-manager.js:55:15)
ERR! db     at new ConnectionManager (/home/s7002/revcord/node_modules/sequelize/lib/dialects/sqlite/connection-manager.js:18:21)
ERR! db     at new SqliteDialect (/home/s7002/revcord/node_modules/sequelize/lib/dialects/sqlite/index.js:13:30)
ERR! db     at new Sequelize (/home/s7002/revcord/node_modules/sequelize/lib/sequelize.js:194:20)
ERR! db     at Main. (/home/s7002/revcord/build/app/Main.js:39:31)
ERR! db     at Generator.next ()
ERR! db     at /home/s7002/revcord/build/app/Main.js:8:71
ERR! db     at new Promise ()
ERR! db     at __awaiter (/home/s7002/revcord/build/app/Main.js:4:12)
ERR! db     at Main.initDb (/home/s7002/revcord/build/app/Main.js:38:16)
ERR! db  Error: Please install sqlite3 package manually
ERR! db     at ConnectionManager._loadDialectModule (/home/s7002/revcord/node_modules/sequelize/lib/dialects/abstract/connection-manager.js:55:15)
ERR! db     at new ConnectionManager (/home/s7002/revcord/node_modules/sequelize/lib/dialects/sqlite/connection-manager.js:18:21)
ERR! db     at new SqliteDialect (/home/s7002/revcord/node_modules/sequelize/lib/dialects/sqlite/index.js:13:30)
ERR! db     at new Sequelize (/home/s7002/revcord/node_modules/sequelize/lib/sequelize.js:194:20)
ERR! db     at Main. (/home/s7002/revcord/build/app/Main.js:39:31)
ERR! db     at Generator.next ()
ERR! db     at /home/s7002/revcord/build/app/Main.js:8:71
ERR! db     at new Promise ()
ERR! db     at __awaiter (/home/s7002/revcord/build/app/Main.js:4:12)
ERR! db     at Main.initDb (/home/s7002/revcord/build/app/Main.js:38:16)
info Revolt Logged in as Disvolt
TypeError: Cannot read properties of undefined (reading 'forEach')
at Client. (/home/s7002/revcord/build/app/Bot.js:148:34)
at Client.emit (/home/s7002/revcord/node_modules/eventemitter3/index.js:180:35)
at WebSocketClient. (/home/s7002/revcord/node_modules/revolt.js/dist/websocket/client.js:137:41)
at Generator.next ()
at /home/s7002/revcord/node_modules/revolt.js/dist/websocket/client.js:8:71
at new Promise ()
at __awaiter (/home/s7002/revcord/node_modules/revolt.js/dist/websocket/client.js:4:12)
at process (/home/s7002/revcord/node_modules/revolt.js/dist/websocket/client.js:95:41)
at WebSocketClient. (/home/s7002/revcord/node_modules/revolt.js/dist/websocket/client.js:538:23)
at Generator.next ()
info Discord Logged in as DisVolt#2900
/home/s7002/revcord/build/app/Bot.js:70
Main_1.Main.mappings.forEach((mapping) => __awaiter(this, void 0, void 0, function* () {
^
TypeError: Cannot read properties of undefined (reading 'forEach')
at Client. (/home/s7002/revcord/build/app/Bot.js:70:34)
at Object.onceWrapper (node:events:628:26)
at Client.emit (node:events:513:28)
at WebSocketManager.triggerClientReady (/home/s7002/revcord/node_modules/discord.js/src/client/websocket/WebSocketManager.js:387:17)
at WebSocketManager.checkShardsReady (/home/s7002/revcord/node_modules/discord.js/src/client/websocket/WebSocketManager.js:370:10)
at WebSocketShard. (/home/s7002/revcord/node_modules/discord.js/src/client/websocket/WebSocketManager.js:200:16)
at WebSocketShard.emit (node:events:513:28)
at WebSocketShard.checkReady (/home/s7002/revcord/node_modules/discord.js/src/client/websocket/WebSocketShard.js:181:12)
at WebSocketShard.gotGuild (/home/s7002/revcord/node_modules/discord.js/src/client/websocket/WebSocketShard.js:155:10)
at WebSocketManager. (/home/s7002/revcord/node_modules/discord.js/src/client/websocket/WebSocketManager.js:240:15)
Node.js v18.16.1

This is most likely caused by the sqlite3 native module missing. It should fetch the prebuilt version but sometimes it fails and I don't really know why. I'd suggest you do npm rebuild and then if it's stuck you can open htop in another terminal and see if gcc is running. If yes, then it's attempting to build the native module and it's nearly impossible to do that on a rpi lol
So a hacky solution for now would be to find prebuilt sqlite3 binaries for arm (you can find them in their github releases), it can be for a newer version as long as its the same major release. Then put them in (iirc) node_modules/sqlite3/bin(?)/Release
I'll try to reproduce the issue on my own and find a proper solution when I'm back home.

Thank you, I will try this later

This is an issue specific to 32-bit arm distros running on Raspberry Pi and similar devices
I have explained how to fix this issue here.


Duplicate migration file when trying to incorporate spree-product-assembly module into Spree 3.0.0.rc2

There is a migration file in the spree install (_add_line_item_id_to_spree_inventory_units.spree.rb) that has the same class and file names and adds the same column and index as<PHONE_NUMBER>1524_add_line_item_id_to_spree_inventory_units.rb, plus the spree migration file updates shipment line items. This migration file in spree-product-assembly needs to be deleted.

:+1:

fixed on master thanks


Alpine 3.11.11 security support ends Nov 2021

Hey Devs,
I was wondering if there's plans to upgrade to a later version of Alpine?
I pulled the 8.3.0 image and it's running 3.11.11 and security support for that ends in November (see https://endoflife.date/alpine).
Thanks!

@Flydiverny thanks very much 👍


Add support for entry_points as string

Fixes issue #239.

Thanks for taking this up!

Pushed an update. Having some trouble running Tox locally, hopefully everything comes up clean.

This LGTM.  Assuming a green CI run I'll patch this in.

@pikeas looks like an isort pass is needed to fix import order.

Yep, I see the failure, but I'm not able to reproduce locally, and Travis doesn't provide the correct sort order. I've tried running the test's isort command directly, but that generates a ton of noise.

In case you decide to contribute more, like so:
$ curl -sSL https://github.com/pantsbuild/pex/pull/240.diff | git apply -3
$ tox -e isort-run
GLOB sdist-make: /home/jsirois/dev/pantsbuild/pex/setup.py
isort-run create: /home/jsirois/dev/pantsbuild/pex/.tox/isort-run
isort-run installdeps: isort
isort-run inst: /home/jsirois/dev/pantsbuild/pex/.tox/dist/pex-1.1.4.zip
isort-run installed: isort==4.2.5,pex==1.1.4
isort-run runtests: PYTHONHASHSEED='3672361260'
isort-run runtests: commands[0] | isort -ns __init__.py -rc /home/jsirois/dev/pantsbuild/pex/pex /home/jsirois/dev/pantsbuild/pex/tests
Skipped 3 files
__________________________________________________________________________________________________________________________________________ summary ___________________________________________________________________________________________________________________________________________
  isort-run: commands succeeded
  congratulations :)

And that resulted in this diff:
$ git diff -U1
diff --git a/pex/commands/bdist_pex.py b/pex/commands/bdist_pex.py
index cc82b85..bc98650 100644
--- a/pex/commands/bdist_pex.py
+++ b/pex/commands/bdist_pex.py
@@ -1,5 +1,5 @@
 import os
-from configparser import ConfigParser
 from distutils import log

+from configparser import ConfigParser
 from setuptools import Command
diff --git a/tests/test_inherits_path_option.py b/tests/test_inherits_path_option.py
index d38687b..ee8edc7 100644
--- a/tests/test_inherits_path_option.py
+++ b/tests/test_inherits_path_option.py
@@ -4,3 +4,2 @@
 import os
-
 from contextlib import contextmanager

Thanks @pikeas - this is patched into master as 1 squashed commit with the isort fix applied and your original description as the commit message here: https://github.com/pantsbuild/pex/commit/c7651f02140e607caaaf2d4e007f196dd15d02c3

Thanks for sharing the Tox command, @jsirois - it wasn't clear that isort-run was an environment!


Set spin_conversion_phase = 0.0 for NPE and GNPE examples

These examples fail when sampling the synthetic phase since they defaulted to spin_conversion_phase = None.

We should also document this setting (in the waveform dataset generation part of the docs) and possibly print a warning when training a phase-marginalized network with spin_conversion_phase != 0.0.

Updated the docs.


fix(card-group): optional border for card group default

Related Ticket(s)
https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/5993
Description
Include an optional border for Cards group - Default

Hmm just checked again, the border left is showing when I view the component outside storybook. FYI @NSDrowned.

A few things from me here @NSDrowned :
1. On Web Components Card group - default showing 6 cards but the knob says 5. This difference maintains if I add or subtract cards.
2. The border knob triggers the cards' content change like it loads another group of different cards in its place, instead of just adding a border.
https://user-images.githubusercontent.com/48327647/119662595-3b778000-be3a-11eb-995f-a101e8230899.mov
3. On React, there is no border knob.

@shixiedesign just pushed a fix for the left margin. To further explain, the original card group is using padding to create the inner borders and the calculation creates a lot of decimals. When I use the same method in the outer borders, chrome rounded those decimals down in some resolutions, so the padding was hidden. That's why it worked outside of storybook.
I changed everything to use css borders instead of padding 👍

@DragosRistici I fixed the knob count and the made the random titles static so the cards don't get reloaded (well, they do get reloaded but it's unnoticeable). This issue only applies for Web Components. The React version is coming in #6049 👍

Is this a separate issue? I'm seeing alignment issues on the body copy.

Last item with images appear to have a px gap, and a px shorter.

Separate issue, but our card in card example is outside of card group.

It might also be causing some of the problems here...

no border on card in card
gap on right side of card in card
gap below card in card

@shixiedesign correct me if I'm wrong, but I think she wanted the light variant in addition to the border being chosen when the outlined cards knob is turned on.
So outline cards knob true sets the grid mode to border, and sets the cards to the light color variant.

Found a bug in card in card and card in card with images

Clickable light cards are missing the interactive states. Maybe you haven't pulled in #6213 yet?
There are still some alignment issues that haven't been addressed when Card in card is present. Card in card doesn't get the border treatment, and it has a separate grid mode because it's separate from the card group for some odd reason.

I'm not seeing the alignment issue anymore either. I must have hit a really big edge case with that on accident or did something myself to make it misalign.

@photodow I pulled the latest code and got interactions. As for the border issue, Dragos opened a separate issue about it #6234 since it's related to another variant (and happening in canary)


Add space for sponsorship logo (and link)

Decision: instead of center alignment for the toolkit topic, we would like to see this be left-aligned. Then we can add sponsorship logo to the right.
Goals

simple logo rather than full-scale add
align with business member directory - e.g. click on logo to view that business's profile.
if there is no sponsor, say something like "Organizations: Sponsor this Toolkit (learn more)" - clicking can take you to a page outlining sponsorship availability and prices.

M&M's process for selling sponsorship - Julian and Jessica will connect:

What will be the sponsorship timeframes?
Is it possible to reach out to get a few sponsors around the soft launch?
whether the sponsorship should appear anywhere besides the toolkit (for example, the Content Type lists)

Removed decision needed label since M&M is okay with what is proposed above (12/4/ review team meeting)

@monika-aashe is this necessary for the public launch? It feels like it could be a post-launch improvement if we don't have a sponsor lined up...

@jamstooks - My understanding was that as soon as we soft-launch, M&M would begin selling sponsorships. We can probably wait until we're close to having our first sponsor, though it may end up being sooner rather than later.

Follow-up with Jessica on next steps in upcoming call.

I'm moving this to the Bike rack based on discussion with Jessica in which we agreed to prioritize integration of Multiview ads over sponsorship. A main reason for this is that Multiview requires no extra work in recruiting and managing sponsorships - once we have set up the code, we don't really have to do anything extra. We still want to keep this ticket open though because we may still want to try sponsorship at some point in the future.

Revisit since the advertising model doesn't seem to be working after all.

Is there still plans for this? I haven't heard of any efforts to secure sponsorship.

Sorry for the slow response! There is a bit of a chicken and egg issue here. There hasn't been any attempt to secure sponsorship because if we did get a sponsor, there's currently no place to recognize them. It's also hard to sell without being able to show a potential sponsor where and how they'd get recognized.
That said, we haven't prioritized this because we think the likelihood of being able to sell the sponsorships is relatively low right now and we'd prefer to focus on other features. We had a Multiview ad box up for a while and they weren't able to find any buyers, which suggests that we need to focus more on building our userbase before we try to sell sponsorships.


[fix](jdbc catalog) support sqlserver timestamp type

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 49.18 seconds
stream load tsv:          507 seconds loaded<PHONE_NUMBER>9 Bytes, about 140 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          28.8 seconds inserted 10000000 Rows, about 347K ops/s
storage size:<PHONE_NUMBER>8 Bytes


Support multiple caches

Hi there! I like this thing, but it doesn't support Redis. I've refactored it to run through Fastentry.cache instead of Rails.cache so that it can decorate the cache with support for pulling out keys in different ways.

Hi @kddeisz, this is fantastic! I was planning on refactoring later after validating that this was a real need of the community but your PR completely corroborates this. Going to test and merge.
Thank you for improving FastEntry and if you have the time it would be great to get in touch and discuss what made you take an interest on the engine and what you'd like to see in the future.
Thanks once again.

No worries! I'm very interested in this kind of dashboard for caching. My current app is REALLY heavy on the cache, and there have been a couple of times where I've needed to SSH into production boxes literally just to touch records to bust their caches. It'd be great to avoid this entirely.
For that matter, here are two things (no pressure!) that would be super useful:

I've had to monkey patch it right now because .assets is only available if you're running in non api-only mode. Hopefully I can get a PR up for that at some point.
Deleting multiple caches at the same time would be huge. That's usually the case for me (some org updates and all the users in the org need to be busted kind of thing).

Either way great work! I'll be watching this repo!

@kddeisz those are great ideas and definitely worth implementing! I'll start with the second one since I've received that feedback from other people who have been testing FastEntry. Regarding the first one you're absolutely right: there needs to be a way to not rely on the assets part for the engine to work. I'll setup a test project in api-only mode to debug this.
Thanks again for the amazing feedback.

@kddeisz version 0.1.10 now supports multiple cache keys invalidation.

Nice work!!

Thanks @kddeisz!
Regarding the other issue, on api-only mode there's a commented line on application.rb:
# require "sprockets/railtie"
Uncommenting that line should make it work without having to monkey patch anything else. Would it be possible for you to try that? Thank you 😊

Yup that fixed it!


added HighlightKeywordsPlugin

Added HighlightKeywordsPlugin
Link to codesandbox code
Configuration/usage:
<HighlightKeywordsPlugin
  keywords={{
    '=.builtIn.': {
      color: 'teal',
      match: /=\.builtIn\./,
    },
    funcName: {
      color: 'magenta',
      match: /funcName/,
    },
  }}
/>

Thanks for your contribution!
There's an existing Keywords plugin, which you might want to check. Best part of it – it shows the usage of useLexicalTextEntity which is build to solve exactly the kind of problem you're addressing in this PR: take RegExp and replace its matched plain text with some custom node.


Scrolling bug on the editor

example: https://mdx.airview.preprod.airwalkconsulting.io/docs/edit/feature%2FAI-Project-Documentation/services/aws_dynamodb/_index.md
when you're editing in the markdown view (far right icon), the scrolling doesn't work

to me this more looks like an issue with mdxeditor as doesn't appear to have css applied from this repo

I think we should be able to change the css within the editor.. like using the existing Styled component ?

ahhh I see the problem, when the diff mode is activate the rich-text-editor display is set to the 'none' and the diff editor is then rendered underneath. Have added the require css to the diff part now

https://github.com/AirWalk-Digital/airview-next/pull/72


FlexCAN driver for i.MX RT1060 MCU

Summary
Adds FlexCAN driver for i.MX RT1060 MCU and the support for imxrt1060-evk board.
Testing
Verified on imxrt1060-evk board, tested againts MicroZed APO board

Any idea about arch/arm/src/imxrt/hardware/rt106x/imxrt106x_ccm.h warnings? As far as I can see it is the same coding style as it is the mainline. Thanks.

Hi @michallenc
Add a blank line above the line the line that failed OR moved the comment to the right to align with with the previous command's alignment.

The build is failing becase imxrt1060-evk/canfd defconfig's is using old configurations.
Please refresh it by running: ./tools/refresh.sh --silent imxrt1060-evk:canfd

Hi @davids5 and @Ouss4
Thank you for your advices and help.


Additional settings for Marquee

From @mackorone:

When a Marquee widget is first displayed, none of the text is visible. I’ve love an option to have the text start left-aligned. I’d also love an option to stop the scrolling once the end of the text is visible.

Fine grained control over start an end position is available as of #23.


irmin-pack: add fsync to gc process

This PR adds fsync calls to the end of the GC process for the suffix and the results file to ensure flushes are persisted to disk.
Should this code take into consideration the use_fsync configuration flag (it does not currently)? I am taking a perspective that the GC process is an internal/separate procedure that does not necessarily have to follow that config value and so it can choose to have safer guarantees, but I do not feel too strongly about this stance.
Related to #1971

Codecov Report

Merging #2048 (8fc46cf) into main (953431e) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #2048      +/-   ##
==========================================
- Coverage   64.49%   64.48%   -0.01%
==========================================
  Files         130      130
  Lines       15548    15550       +2
==========================================
  Hits        10027    10027
- Misses       5521     5523       +2

Impacted Files
Coverage Δ

src/irmin-pack/unix/file_manager.ml
82.45% <0.00%> (-0.28%)
:arrow_down:

src/irmin-pack/unix/gc.ml
8.66% <0.00%> (-0.14%)
:arrow_down:

src/irmin-pack/unix/import.ml
88.88% <ø> (-1.12%)
:arrow_down:

src/irmin-test/store.ml
94.82% <0.00%> (-0.06%)
:arrow_down:

src/irmin-fs/irmin_fs.ml
82.42% <0.00%> (+1.21%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

This indeed not useful to connect this to the use_fsync option as this is run in a separate process we don't care about it being blocking

I believe that the prefix and the mapping deserve to be fsynced too

@Ngoguey42 ha, yes of course :facepalm: I just pushed these changes.

Results of lib_context benchmark. Full Summary
 |                          | main_220810 |     fsync
 | --                       | --          | --
 | -- main metrics --       |             |
 | CPU time elapsed         |     192m46s |   192m40s 100%
 | Wall time elapsed        |     232m39s |   232m48s 100%
 | TZ-transactions per sec  |    1368.073 |  1368.761 100%
 | TZ-operations per sec    |    2236.879 |  2238.002 100%
 | Context.add per sec      |   18233.635 | 18242.794 100%
 | tail latency (1)         |     0.695 s |   0.741 s 107%
 |                          |             |
 | -- resource usage --     |             |
 | disk IO (total)          |             |
 |   IOPS (op/sec)          |     246_068 |   246_193 100%
 |   throughput (bytes/sec) |    18.781 M |  18.796 M 100%
 |   total (bytes)          |   217.208 G | 217.276 G 100%
 | disk IO (read)           |             |
 |   IOPS (op/sec)          |     245_993 |   246_118 100%
 |   throughput (bytes/sec) |    13.840 M |  13.850 M 100%
 |   total (bytes)          |   160.073 G | 160.108 G 100%
 | disk IO (write)          |             |
 |   IOPS (op/sec)          |          75 |        75 100%
 |   throughput (bytes/sec) |     4.940 M |   4.945 M 100%
 |   total (bytes)          |    57.135 G |  57.169 G 100%
 |                          |             |
 | max memory usage (bytes) |     0.576 G |   0.566 G  98%
 | mean CPU usage           |         83% |       83%

A second benchmark run seems to support a perspective that the tail latency time is within normal operating variance (or it is actually faster with fsync :upside_down_face:).
 |                          | main_220810 |    fsync_a     |    fsync_b
 | --                       | --          | --             | --
 | -- main metrics --       |             |                |
 | CPU time elapsed         |     192m46s |   192m40s 100% |   191m24s  99%
 | Wall time elapsed        |     232m39s |   232m48s 100% |   230m40s  99%
 | TZ-transactions per sec  |    1368.073 |  1368.761 100% |  1377.799 101%
 | TZ-operations per sec    |    2236.879 |  2238.002 100% |  2252.782 101%
 | Context.add per sec      |   18233.635 | 18242.794 100% | 18363.264 101%
 | tail latency (1)         |     0.695 s |   0.741 s 107% |   0.603 s  87%
 |                          |             |                |
 | -- resource usage --     |             |                |
 | disk IO (total)          |             |                |
 |   IOPS (op/sec)          |     246_068 |   246_193 100% |   247_821 101%
 |   throughput (bytes/sec) |    18.781 M |  18.796 M 100% |  18.920 M 101%
 |   total (bytes)          |   217.208 G | 217.276 G 100% | 217.271 G 100%
 | disk IO (read)           |             |                |
 |   IOPS (op/sec)          |     245_993 |   246_118 100% |   247_746 101%
 |   throughput (bytes/sec) |    13.840 M |  13.850 M 100% |  13.942 M 101%
 |   total (bytes)          |   160.073 G | 160.108 G 100% | 160.106 G 100%
 | disk IO (write)          |             |                |
 |   IOPS (op/sec)          |          75 |        75 100% |        76 101%
 |   throughput (bytes/sec) |     4.940 M |   4.945 M 100% |   4.978 M 101%
 |   total (bytes)          |    57.135 G |  57.169 G 100% |  57.165 G 100%
 |                          |             |                |
 | max memory usage (bytes) |     0.576 G |   0.566 G  98% |   0.579 G 100%
 | mean CPU usage           |         83% |       83%      |       83%


Document new-style stream selection

Python3.5 requires replacing
video = next(s for s in container.streams if s.type == b'video')
with
video = next(s for s in container.streams.video):
As I work through the rest of the examples I'll clone the repo and create a pull request if I find more issues.

Hi @ReaddyEddy!
I don't think Python3 requires such a change, but switching to the new-style stream selection in the examples/docs should be done.
Either of container.streams.get(video=0) or container.streams.video[0] should do (IIRC).

I'll check your suggestion in 3.5.2_1 which was the version that showed the issue for me, without any references to import future etc.


Support java_library deps that are local jar files loaded by java_import

Here is a legal idiom for defining a local jar file as a dep, without maven_install:
java_import(
    name = "zip4j",
    jars = ["lib/zip4j-2.6.4.jar",],
)

java_library(
    name = "springboot_rule_lib",
    srcs = glob(["src/main/java/**/*.java"]),
    deps = [ ":zip4j" ],
)

BEF currently does not recognize the dep.

Fix submitted, but I still need to add a test for it.


[REQUEST] Read status via config

Hi,
please add variables to read status current bot and runner via config
something like :
<BotsCount> = Count of bots
<ProxyStatus> = Proxy Status [On or Off]
things that are good to known is :
Bot ID
Count of enabled Bots
Proxy Status [On/Off]
Proxy of current bot
Proxy's IP
Proxy's Port
Proxy type
Total Check Datas
CPM
Hits
Custom Hits
Retries
To Checks
Count of proxies
Banned Proxies
and etcxxxxxxxxx.
ty

Due to separation of concerns, this is impossible in the current application design.


Test out KP401 programmatic control

https://github.com/python-kasa/python-kasa

Context: https://accelerated-discovery.org/t/uv-curing-module-for-robotics-workstation-eg-opentrons/428

Updates:

The smart plug doesn't see the UofT or eduroam networks
I tried making a wireless network with a non-internet connected wireless repeater. The connection process seemed to start, but it couldn't finish past the "Add location (office, kitchen etc.) step. My internet research led me to believe that using a non-internet connected wifi could work, but would require additional implementation.

We'll debug on our end. Feel free to drop off at the office with the 3D printer.


nixos/plasma5: Noto Mono -> Noto Sans Mono

Motivation for this change
The font has been renamed. See https://github.com/googlefonts/noto-fonts/pull/1029
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Backport needed? I would assume the default font would just not work.

Fontconfig uses a different font, it goes through available fonts alphabetically, on my machine it uses DejaVu instead of Noto. Should I open a backport pr for this?

Fontconfig uses a different font, it goes through available fonts alphabetically, on my machine it uses DejaVu instead of Noto. Should I open a backport pr for this?

I think so. But, would fontconfig for example suddenly change which font is used on the  endusers system? Like with this change, users of the plasma5 module will suddenly have Noto Sans Mono instead of the incorrect default of DejaVu? If that's so, then I'd say it wouldn't be suitable for backport.

Yes it would, but the new defaults are only applied after restarting plasma.
It also shouldn't really cause any problems, since Noto Sans Mono is only meant as a fallback for characters that are unsupported by Hack, which comes first in 'fonts.fontconfig.defaultFonts.monospace', so this wouldn't make a difference for most text.

Yes it would, but the new defaults are only applied after restarting plasma.
It also shouldn't really cause any problems, since Noto Sans Mono is only meant as a fallback for characters that are unsupported by Hack, which comes first in 'fonts.fontconfig.defaultFonts.monospace', so this wouldn't make a difference for most text.

Sounds good to me :+1:


Issue a warning when a variable is used to initialize itself

.uninitialized_in_own_init should be issued if a variable is used in its own initializer (there are some caveats, see the lines marked with -Wuninitialized in the initializers.c test case)

The same mechanism should also be able to detect use  of uninitialized variables in general (in the limited scope of per function static analysis).


updating BasicAuthBackend to accept a 'challenges' parameter

I needed this option to specify challenges on the BasicAuthBackend. There are other ways of ensuring a challenge is issued, including using a global catchall exception handler and re-wrapping the HTTPUnauthorized errors with the challenge parameter, but that is obviously messy. Since basic auth is most commonly used with challenges in the browser, I was surprised to find this wasn't already an option on the class.
This lets the user initialize their BasicAuthBackend like this:
auth = BasicAuthBackend(user_loader=login_fn, challenges=["Basic"])

...and then the browser will correctly prompt the user for login.

@jcwilson @kgritesh sorry to bug you but just wanted to check if this repo is still being maintained? I submitted this pull request 10 days ago but haven't heard anything.


Update _index.md

👷 Deploy Preview for fragrant-garden processing.

Name
Link

🔨 Latest commit
7b4b6b10c7bdc5dc2bf2479532727325c90b0c68

🔍 Latest deploy log
https://app.netlify.com/sites/fragrant-garden/deploys/64a230a273a4040008c709d5


fix(sec): upgrade io.netty:netty-common to 4.1.77.Final

What happened？
There are 1 security vulnerabilities found in io.netty:netty-common 4.1.73.Final

CVE-2022-24823

What did I do？
Upgrade io.netty:netty-common from 4.1.73.Final to 4.1.77.Final for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
The specification of the pull request
PR Specification from OSCS

close


Update package.json

npm test should pass

Closed by bbe604fd2f09afd84268fdbfa573ac725a0d5553, thanks!

Released v1.3.0


CatalogItem / ecomSeoData API should not return undefined.

Describe the bug
In the Squareup.com GUI, we can see that the SEO option populates avaliable fields using item name and description by default.
This is not the case when calling it through the API. Also there is no option to make it the same as the item name, as this also renders the SEO field such as permalink to be undefined.
Expected behavior
Permalink should return the default name, as is explained in the web GUI.
Currently, in the SDK ecomSeoData can be undefined, with the fields being able to be null.
This should not be the case because they would be default defined as the name.
/** SEO data for for a seller's Square Online store. */
export interface CatalogEcomSeoData {
    /** The SEO title used for the Square Online store. */
    pageTitle?: string | null;
    /** The SEO description used for the Square Online store. */
    pageDescription?: string | null;
    /** The SEO permalink used for the Square Online store. */
    permalink?: string | null;
}

To Reproduce
Steps to reproduce the bug:

Create a menu with the necessary fields
Try to retreieve the item and parse ecomSeoData.

Screenshots

Square SDK version
"square": "^37.1.0",

hi @kyeshmz
I agree this is a confusing interface, however this is currently working as expected.
Basically the ecomSeoData is using the item name and item description as the default values of those fields (pageTitle, pageDescription, permalink) but because they are just pointing to those fields which are set on the item itself, the seo data is not returned as part of the itemData.
If you change those fields in the GUI to something different, those values will return on the item when you query it through the API.
I raised this concern with the team though, and will update this ticket if they decide to change the behavior. Thank you for calling this out!

I understand, like the idea, but not the implementation.

but because they are just pointing to those fields which are set on the item itself,

For example, if this was a pointer, this would not be null if the name or description was defined. It seems to me like it should just return both.


Github Key Verification Failed

Current Behavior
I updated my node-red docker container to 2,1,4. Following this, github key verification fails when trying to push my project to github.
Error
Host key verification failed.
The repository host key could not be verified. Please update your known_hosts file and try again.
Expected Behavior
Was working to push project to github before updating. Known hosts file is mapped to the container. Rolling back to nodered/node-red:2.1.3 fixes the issue and problem returns after changing back to nodered/node-red:latest
Steps To Reproduce
Using node-red 2.1.4
Example flow
paste your flow here
Environment
Node-RED version: 2.1.4
Node.js version: (in container v14.18.2)
npm version: (in container 6.14.15)
Platform/OS: Docker/Ubuntu 20.04
Docker version 20.10.11
Browser: Chrome

As this is a issue against the docker container it should really have been raised against the Docker project (github.com/node-red/node-red-docker).
Recently github added 2  new elliptic curve keys so you will need to update your known_hosts file or just not map the file into the container as it already ships with a known_hosts file that contains all of github's keys from 2.1.3

Apologies for raising in the wrong place. Tried this and working as you explain. Thanks for your time.


Add missing positiveInteger and positiveIntegerDefault0 definitions

Thanks George, I'm not sure how I missed those, sorry about that!

Thanks George, I'm not sure how I missed those, sorry about that!

They didn't show up as errors until I used something that referenced them, so potentially there could be others. There is way too much in there to hand check. Better to probably create a swagger file that uses all the possible features and see what beaks.

They didn't show up as errors until I used something that referenced them, so potentially there could be others. There is way too much in there to hand check. Better to probably create a swagger file that uses all the possible features and see what beaks.

@gwshaw, I've just done a once off true up with all the #refs and definitions in this file and everything matches now. There are 64 unique definitions referenced, and 64 definitions made.
Some of those defs were originally external and I attempted to bring them over to avoid the json validator making http requests to read them, I obviously missed two, but they are all present now.
For future reference, the commands I used to check the defs and refs:
egrep -o '#/definitions/[^"]+' data/swagger_2.0_schema.json | sort | uniq
tail -n+79 data/swagger_2.0_schema.json | egrep -o '^ {4}".*' | sort


Webpack output of 2.8.8 throws error in IE 10

Issue description:
When bundling the latest version with Webpack, IE 10 throws the following error:
SCRIPT1047: In strict mode, function declarations cannot be nested inside a statement or block.

Demo link/slider setting:
https://github.com/ganlanyuan/tiny-slider/compare/master...backflip:bugfix/ie-10
Tiny-slider version:  2.8.8
Browser name && version:  IE 10
OS name && version:  Windows 8

Yeah, I get the same thing. Also experience the same error on my old iPad2 in Safari with iOS 9.something.
I've been trying to find a way to disable the strict mode declaration for just this plugin, but unsuccessful so far.


Username moderation

Backend now fully handles username moderation including duplicate and inappropriate usernames.
I was not able to test the profanity filter as I do not have a development environment setup for backend
Referencing Issue #56

Looks good to me. I'll merge and test it

@loshjarson apart from some minor changes the backend is pretty good. All I changed is var filter to let filter since var isn't really used anymore.
Front End you delete
    if (userId && storedUsername !== 'Guest') {
      saveUser(storedUsername, storedScore);
    }

but that is needed to save the user to the database for the leaderboard part.
Also for the if statement the username wasn't getting saved into cookies since you had it in an else so instead of that, I just had it after the if.
    const checkUsername = async () => {
      if (newUsername === null || newUsername === '') {
        newUsername = prompt('Please enter a new username');
        checkUsername();
      }
      const newUser = await saveUser(newUsername, score);
      if(newUser.error){
        newUsername = prompt(newUser.error)
        checkUsername()
      }
      Cookies.set('username', newUsername, { secure: true });
      Cookies.set('isUsernameChanged', true, { secure: true });
      setUsername(Cookies.get('username'));
      setIsUsernameChanged(true);
    };

Other than that, It works pretty well I tested a couple of bad/racist words and it all came back as an error so great work!

if (userId && storedUsername !== 'Guest') {       saveUser(storedUsername, storedScore);     }
This seemed unnecessary, since saveUser() is already being called when a username is created. And it was causing the request to be fired whenever you open the settings page along with sending two requests when adding a username.

ahh you're right I didn't see this
      const newUser = await saveUser(newUsername, score);

I will make the change.


Delete StsRefreshTokenModification.yaml

Original purpose of the low priority, hunting-only query was to demonstrate an event that has token validity time periods in it (we don't expose SAML token lifetimes in Sentinel or other products currently), and demonstrate how one could monitor for anomalous/edited tokens. This event will only fire on the manual expiration of the StsRefreshToken by an admin (or the user) and has caused some confusion. In the spirit of the original contribution, people have learned more about token visibility ;)
Recommend retiring this and removing from Sentinel hunting workbook/blog.
Fixes #
Proposed Changes

Or... just remove from hunting blog/notebook, and leave here as hunting so people can explore/modify.

Or... just remove from hunting blog/notebook, and leave here as hunting so people can explore/modify.


Vim9: unexpected error when timer callback executed in debug mode

Steps to reproduce
Run this shell command:
vim -Nu NONE -S <(tee <<'EOF'
    vim9script
    def Outer()
        def Inner()
        enddef
        timer_start(1'000, (_) => Inner(), {repeat: -1})
    enddef
    Outer()
    def Func()
        eval 1 + 1
        eval 2 + 2
    enddef
    breakadd func Func
    Func()
EOF
)

Execute the >next debugging command, and wait up to 1 second.
E117 and E1091 are given:
E117: Unknown function: Inner
E1091: Function is not compiled: <lambda>2

Expected behavior
No error is given.
Version of Vim
8.2 Included patches: 1-4018
Environment
Operating system: Ubuntu 20.04.3 LTS
Terminal: xterm
Value of $TERM: xterm-256color
Shell: zsh 5.8
Additional Context
No error is given if Outer() is re-written as a legacy function:
vim9script
function Outer()
    def Inner()
    enddef
    vim9cmd timer_start(1'000, (_) => Inner(), {repeat: -1})
endfunction
Outer()
def Func()
    eval 1 + 1
    eval 2 + 2
enddef
breakadd func Func
Func()

A timer callback may cause any kind of trouble while stepping through Vim code.
I think the best is to disable timers while at the debug prompt.
I'll make that happen, check if anything else breaks then.


Injecting custom CSS classes to the bs-tab component

Hey,
in order to use a template I purchased (built on top of Bootstrap), I needed to change a little bit the bs-tab/bs-nav components.
Basically I wanted to push a custom class to the bs-nav component.. something like:
{{#bs-tab class="tab-nav" as |tab|}} ...
-->
<ul class="tab-nav ember-view">
I don't know if what I did is a desirable implementation (maybe you just want to keep your "ember-bootstrap" 100% standard bootstrap).
Just let me know

@lordkada I somehow overlooked this one, sorry about that!
You can always add classes to any components here by setting them in the template ({{#bs-nav class="custom"}}). You PR seems to address setting the class of a nav inside of a tab. But, besides the failing test, this seems to be very specific to your Bootstrap template, and should be solvable by some tweaked CSS selectors. If that does not work, you can still override components/templates of this addon in you app, for your specific use cases.
So I would prefer to not incorporate the changes here, and stick to standard Bootstrap as you assumed. Thanks nevertheless for contributing!

Yep, I perfectly understand. Thanks anyway ;-)


Update cell to cursor template when adding a tab.

references #85.
Will resolve one part of the rendering blank characters after setting background to something other than the default background.

Thanks for the PR! I added a ref test to prevent regressions.


Only return sequence if it is available

Reviews: @JoelKatz, @rec

I'm not inclined to do a commit that moves to the jss values right this instant for the reasons Scott and Vinnie identified.
We shouldn't coddle our JSON library - we should fix it, which is what I will do.

Is this ready to go?  I didn't find anything wrong with it - even the jss thing was because I thought we were suppose to use those in all new code.
:+1:

ping @JoelKatz - review please?

I still don't understand what this code is doing or what its rationale is. It looks like the existing code only returns the sequence if it was specified too.

So hmm, where are we with this then?

PING!!!

I'm going to close this without prejudice, as there hasn't been progress in three weeks.  Feel free to reopen it!  :-)


feat(account): execute multicall transactions

supports executing multiple calls in Account#execute
sends those as a single StarkNet transaction to the account contract's __execute__ method
updates existing tests to support the new account
adds a new case to test an actual multicall scenario
improves error reporting

Really happy about this PR! Was waiting for multicall execute for a while now. Thanks @delaaxe .

@0xs34n resolved your suggestions and made a few more changes!

Looks good to me. Waiting patiently for this to be merged and released :)


[Do not review]

Fix the IT module depends on the tests module
This contributes #3934
Signed-off-by: Chong Gao<EMAIL_ADDRESS>

build

build

Remove the dependency
Move the test cases in the IT module to the tests module
Fix a random hang issue.

build


Example fails with error

On a Debian 9 VM, using https://github.com/mapbox/route-annotator/archive/0.2.4.tar.gz and geofabrik's ‘monaco-latest.osm.pbf’, running curl "http://localhost:5000/coordlist/7.422155,43.7368838;7.4230139,43.7369751" prints "Bad Request". An error is produced on the server side.
$ npm install
npm WARN deprecated<EMAIL_ADDRESS>This module is no longer maintained, try this instead:
npm WARN deprecated   npm i nyc
npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.

><EMAIL_ADDRESS>install /home/stereo/route-annotator-0.2.4
> node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using request for node-pre-gyp https download
[@mapbox/route-annotator] Success: "/home/stereo/route-annotator-0.2.4/lib/binding/route_annotator.node" is installed via remote
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>license should be a valid SPDX license expression

added 254 packages from 316 contributors in 12.491s
$ node example-server.js monaco-latest.osm.pbf
Parsing monaco-latest.osm.pbf ... done
Number of node pairs indexed: 5479
Number of ways indexed: 865
done
String data is 0 Used: 0
way_tag_ranges = Allocated 6920  Used: 6920
keyvalue = Allocated 0  Used: 0
stringoffset = Allocated 0  Used: 0
pair_way_map = Allocated 109580  Load factor: 0.728881 Buckets: 7517
Listening on <IP_ADDRESS>:5000
GET  /coordlist/7.422155,43.7368838;7.4230139,43.7369751  curl/7.52.1
Error: Annotator not created with coordinates support

I also have this error

@joshjconlin I ended up running route-annotator in docker. See https://github.com/grischard/route-annotator/commits/master, in particular commits 26257631c27a71523b895b4c7190b2034fbbc71e and 94bf391dc1d1e376a99e22a13ab9a1223b58b198

@grischard thanks for the response. I tried your dockerfile but I still have the same issue. String data is 0 Used: 0 way_tag_ranges = Allocated 4048032  Used: 4048032 keyvalue = Allocated 0  Used: 0 stringoffset = Allocated 0  Used: 0 pair_way_map = Allocated 84002700  Load factor: 0.964283 Buckets: 4355707 err Error: Annotator not created with coordinates support   Dockerfile ```FROM node:8
Create app directory
WORKDIR /usr/src/app
Install app dependencies
A wildcard is used to ensure both package.json AND package-lock.json are copied
where available (npm@5+)
COPY package*.json ./
RUN npm install --unsafe-perm
If you are building your code for production
RUN npm ci --only=production
Bundle app source
COPY . .
ENV ANNOTATOR_PORT=5050
EXPOSE 5050
CMD [ "node", "index.js"]and the actual code I'm trying to run const taglookup = new (require('@mapbox/route-annotator')).Annotator();
const path = require('path');
const data = "47.46284,-122.25853 47.4631,-122.25928 47.46323,-122.25973 47.46334,-122.26012 47.46338,-122.26033 47.46341,-122.26045 47.46351,-122.26101 47.46355,-122.26145 47.46356,-122.2619 47.46355,-122.26235 47.4635,-122.26287 47.46346,-122.26313 47.46344,-122.26325 47.46337,-122.26358 47.46329,-122.26387 47.46317,-122.26425 "
const parsedCoordinates = data.split(' ').filter(val => val && val !== ' ').map((val => [...(val.split(',').map(v => parseFloat(v)))]));
const results = [];
//// Do the same thing, but this time use coordinates instead
// // of node ids.  Internally, a radius search finds the closest
// // node within 5m
taglookup.loadOSMExtract(path.join(__dirname,'./washington-latest.osm.pbf'), (err) => {
if (err) throw err;
taglookup.annotateRouteFromLonLats(parsedCoordinates, (err, wayIds) => {
if (err) {
console.warn('err', err);
} else {
taglookup.getAllTagsForWayId(wayIds[0], (err, tags) => {
if (err) {
console.warn(('second err'))
} else {
results.push(tags);
console.warn(results, 'results');
}
})
}
})
});``` Any help would be much appreciated, thanks again for your previous response

Can you get the example server to work, then call that with your coordinates over http?

I have the same issue. Built from the git clone with npm install --unsafe-perm as in that docker file, don't observe any errors during the build, all tests pass, but when calling the example server with a set of coordinates, I get
Error: Annotator not created with coordinates support

You have to pass { coordinates: true } to the Annotator constructor:
const taglookup = new (require('@mapbox/route-annotator')).Annotator({ coordinates: true });
const path = require('path');

I also had to npm install --unsafe-perm the module itself.

Ok, that gets me one error further:
arminus@ub14vm:~/osm/route-annotator$ node my_test.js
Parsing /home/amueller/osm/route-annotator/monaco-latest.osm.pbf ... done
Number of node pairs indexed: 5717
Number of ways indexed: 949
Constructing RTree ... done
String data is 0 Used: 0
way_tag_ranges = Allocated 7592  Used: 7592
keyvalue = Allocated 0  Used: 0
stringoffset = Allocated 0  Used: 0
pair_way_map = Allocated 114340  Load factor: 0.760543 Buckets: 7517
/home/arminus/osm/route-annotator/my_test.js:13
    taglookup.getAllTagsForWayId(wayIds[0], (err, tags) => {
              ^

TypeError: A numeric way ID and a callback expected
    at taglookup.annotateRouteFromLonLats (/home/arminus/osm/route-annotator/my_test.js:13:15)

Had the same problem and opened a new issue: https://github.com/mapbox/route-annotator/issues/62

That's right, finally got it working now. Thanks!


Crash on Look To Banana

My game has crashed when i look to banana on the tree (from Biomes O' Plenty mod).
TOP crash mcjty.txt

Thanks. I'll check it out soon. Chances are the bug are in the 'banana' mod (whatever that is) though

and aaah, i should add a note here; it didn't crash again when i look to that "banana leaves" and "banana flower" items. only i remember is i just looked to the banana tree, then bananas.

Are you sure it's an item from Biomes O' Plenty? As far as I know it doesn't add anything related to bananas. The only I know of (and is present in all the mods 2) is the one of Pam's HarvestCraft. And that one doesn't seem to cause crashes.

ahhh so sorry for that, it is from Terraqueous.  fixed the content.

actually this thing:

Can you still reproduce this? In any case, this doesn't look like a bug in TOP but in Terraqueous. The problem seems to be that a wrong item is returned from block.getPickBlock(). That's something they should fix on their side

hmmm... okay. and no, i couldn't make it happen again. thanks.

it happens again :/

Please report to Terraqueous


Language files with meridiem: []

Language files with meridiem: [] make de calendar go to the first day instead of last one you select.

Should be fixed


Refactors Snapshot action to use new interface

Issue #, if available:
NA
Description of changes:
Refactors snapshot action to use new interface.
CheckList:

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #253 (c4a5f26) into development-extension (a902b37) will increase coverage by 0.57%.
The diff coverage is 86.66%.

@@                     Coverage Diff                     @@
##             development-extension     #253      +/-   ##
===========================================================
+ Coverage                    66.47%   67.04%   +0.57%
- Complexity                    1586     1633      +47
===========================================================
  Files                          249      249
  Lines                         9996    10160     +164
  Branches                      1552     1580      +28
===========================================================
+ Hits                          6645     6812     +167
+ Misses                        2531     2512      -19
- Partials                       820      836      +16

Impacted Files
Coverage Δ

...ment/indexstatemanagement/action/SnapshotAction.kt
69.56% <63.15%> (+69.56%)
:arrow_up:

...ndexstatemanagement/action/SnapshotActionParser.kt
80.00% <78.94%> (+80.00%)
:arrow_up:

...atemanagement/step/snapshot/WaitForSnapshotStep.kt
88.13% <87.93%> (+88.13%)
:arrow_up:

...atemanagement/step/snapshot/AttemptSnapshotStep.kt
92.77% <92.68%> (+92.77%)
:arrow_up:

...anagement/indexstatemanagement/ISMActionsParser.kt
80.95% <100.00%> (+0.46%)
:arrow_up:

...nt/indexstatemanagement/model/destination/Slack.kt
40.90% <0.00%> (-13.64%)
:arrow_down:

...arch/indexmanagement/rollup/RollupSearchService.kt
55.55% <0.00%> (-3.71%)
:arrow_down:

.../opensearch/indexmanagement/rollup/model/Rollup.kt
83.96% <0.00%> (-0.48%)
:arrow_down:

...nt/indexstatemanagement/ManagedIndexCoordinator.kt
63.76% <0.00%> (+0.34%)
:arrow_up:

...earch/indexmanagement/transform/model/Transform.kt
87.00% <0.00%> (+1.00%)
:arrow_up:

... and 7 more

Continue to review full report at Codecov.

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


Adding HVAC pump and pump-controller example apps

Problem
Missing HVAC Pump and Pump Controller example application skeletons for further development.

Summary of Changes
Added example applications to the following folders:
examples/pump-app
examples/pump-controller-app

TI CC13x2x7_26x2x7 and nrfconnect platforms are supported currently.

Fixes #6527

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: tlykkeberg-grundfos:x: Yuriy DovgalyukYuriy Dovgalyuk seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Ignore custom tags in check-yaml pre-commit

Added --ignore-tags flag to pass a comma separated list of custom tags to ignore to check-yaml. This is going to be used to ignore the new !include tag in metadata.yml files.

A note here that --unsafe was added upstream which also enables custom tags

@asottile Thanks for the alert. I'll take a look.


Cannot read properties of undefined (reading 'signals')

After connecting the library to the JS project,
const youtubedl = require('youtube-dl-exec')
I get the following error in the browser console:
`Uncaught TypeError: Cannot read properties of undefined (reading 'signals')
at normalizeSignal (signals.js?93eb:30:1)
at Array.map (<anonymous>)
at getSignals (signals.js?93eb:10:1)
at getSignalsByName (main.js?0739:9:1)
at eval (main.js?0739:23:1)
at Object../node_modules/youtube-dl-exec/node_modules/human-signals/build/src/main.js (chunk-vendors.js:1210:1)
at __webpack_require__ (app.js:849:30)
at fn (app.js:151:20)
at eval (error.js?c63c:2:1)
at Object../node_modules/youtube-dl-exec/node_modules/execa/lib/error.js (chunk-vendors.js:1114:1)`

Library added to node_modules
Please, prompt in what there can be a reason. I can't find the answer on google

Sorry for that, this is not a library oriented to be used in a browser context.


[Trade Page] Explorer

Ref #1167
Nav

[ ] Create a navbar component
[ ] Reuse it in both the explorer & trade -> explorer

Overview / Portfolio / Activity

[ ] Extract logic from explorer/token-pair into a reusable component
[ ] Reuse it in both the explorer page & trade/$explorer page

Portfolio

[ ] Change routing to specific token
from explorer/$type/$slug/portfolio/token/$address
to explorer/$type/$slug/portfolio?token={address}

design has been drop


spring-boot-cucumber broken because it depends only on the spring-server module

Apply spring-boot-mvc module does not provide the spring-boot-starter-web Maven dependency.
Apply spring-boot-tomcat module does. This seems to me a little bit misleading.
For instance, the spring-boot-cucumber module can be broken because it depends only on the spring-server module.
The Maven dependencies are broken when:

spring-boot-mvc module is selected
spring-boot-cucumber is selected
none of the spring-boot-tomcat or spring-boot-undertow modules are provided.

It is a workaround for fixing https://github.com/jhipster/jhipster-lite/issues/4153
Probably this fix is not perfect but it was the easiest for now.
I don't know if spring-boot-cucumber works with webflux. We should test it and if it doesn't work, we can simply change the dependency: spring-boot-cucumber should depend on spring-mvc-server
Another solution would be to rename spring-boot-mvc to spring-boot-mvc-empty so it's totally clear this module is just an empty module

Anyway, thanks for giving a try to this project @bagnier
Don't hesitate of you have better ideas than mine :-D

At first, thank you folks for this useful and ambitious project 💪 !
Thank you @pascalgrimaud for pointing me to this bug report and giving me a better understanding of the context. I will refocus this report around spring-boot-cucumber.
I tried these configurations :

✅ spring-boot-cucumber + spring-boot-mvc + spring-boot-tomcat
✅ spring-boot-cucumber + spring-boot-mvc + spring-boot-undertow
✅ spring-boot-cucumber + spring-boot-webflux + spring-boot-webflux-netty
❌ spring-boot-cucumber + spring-boot-mvc
❌ spring-boot-cucumber + spring-boot-webflux

If the goal of this project is to provide a working software for any valid configuration as selected in the tool, then this issue is a bug. The spring-boot-cucumber module can be enabled without working dependencies.
my 2 cents:

given the context of an hexagonal architecture, a cucumber module without any dependence to the web would be useful.
spring-boot-cucumber may become a group around two concrete implementations, spring-boot-mvc-cucumber depending on spring-mvc-server and spring-boot-webflux-cucumber depending on spring-boot-webflux-netty
spring-boot-mvc-empty may be a good name, maybe spring-boot-mvc-choice ?


Flow type ioredis error:  Cannot call redis.rpoplpush(...).then because property then is missing in undefined

Hi,
I'm having a flow check error when I call rpoplpushmethod.
Here is the line:
return redis.rpoplpush(config.mq.topics.queue, config.mq.topics.processing).then((data) => (typeof data === 'string' ? Promise.resolve(data) : Promise.resolve('')));
Here is the error:
Cannot call redis.rpoplpush(...).then because property then is missing in undefined [1].
I checked the flow-type definition file of ioredis and I saw this:
rpoplpush(args: any[], callback: ResCallbackT<any>): void;
rpoplpush(...args: any[]): Promise<any>;
How can I specify to flow that I want to use the second method (rpoplpush(...args: any[]): Promise<any>) ?
Thanks

I don't think it's possible really, since the first line is too broadly defined that it always matches for the type definition. You'd need to make them finer to disambiguate.
Just to check I'm thinking of it correctly, would something like rpoplpush(foo, bar, baz).then type correctly for you?

I tried the rpoplpush(foo, bar, baz).then first and that doesn't work, that's why I proposed an update of the definitions by replacing the ...args: any[] parameter to the real real parameters in some methods. https://github.com/flowtype/flow-typed/pull/2265 . It seems that some tests failed so I'm going to fix it.


Cannot find module in production mode

Package version
5.1.0
Node.js and npm version
Node: v18.4.0
Npm: 8.12.1
Sample Code (to reproduce the issue)
In Local mode works normall but when I compile from ts and build the app I get this error trying to use the system; I already install @adonisjs/validator and @adonisjs/fold but not works
UPDATE: Works if I disable validations (Validator)
Error: Cannot find module '/www/b7academy/build/app/Validators/SignUpValidator'
Require stack:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>/www/b7academy/build/server.js
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:946:15)
at Function.Module._load (node:internal/modules/cjs/loader:787:27)
at Module.require (node:internal/modules/cjs/loader:1012:19)
at require (node:internal/modules/cjs/helpers:102:18)
at ImportAliases.resolve (/www/b7academy/build/node_modules/@adonisjs/fold/build/src/Ioc/ImportAliases.js:99:23)
at Ioc.require (/www/b7academy/build/node_modules/@adonisjs/fold/build/src/Ioc/index.js:294:36)
at Ioc.use (/www/b7academy/build/node_modules/@adonisjs/fold/build/src/Ioc/index.js:310:25)
at Object. (/www/b7academy/app/Controllers/Http/AuthController.ts:7:1)
at Module._compile (node:internal/modules/cjs/loader:1112:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1166:10)
"code": "MODULE_NOT_FOUND",
"requireStack": [
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>"/www/b7academy/build/server.js"

Hey @carlosaroca! 👋🏻
Looking at the error message, it tries to require the Validators/SignUpValidator.js file but cannot find it.
Can you please double-check there is no typo mistake in your file name?
Note that it is case sensitive.

Closing since no answer from issue reporter.


Terminal revive setting feedback

Testing #133516
I find our setting description and name a bit confusing. Here is macOS for example:

Some obersvations:

there is a setting to configure whether a marker should be printed 👍
the setting does not talk about "persistent session" but "restore text" which I like because that is my understanding of the feature
our setting talks about "processes being recreated" but my understanding is that we only restore the lines and not the running processes

"Persistent sessions" was the existing feature that enabled "process reconnection", the intent in putting it under the same prefix was  because they are similar concepts (reconnection to processes across reloads, save the buffer+re-create the processes across restarts).
Let's keep the setting the same for now as the description is fairly descriptive and that will be searched as well when using the settings UI.

our setting talks about "processes being recreated" but my understanding is that we only restore the lines and not the running processes

The processes to get recreated using the same properties as the previous process, except the current working directory that may change depending on the shell/OS.


Task - Fiter biological associations - filter by geographical area

If I select two taxa for both subject and object. And restrict the search by geographical area, I expect to see result if the geographical area present for either subject or object.

It could be useful to restrict the search for both taxa for a particular area, but practically this is very rare. There is usually one focal taxon in the project. For example Hemiptera, and I track the distribution for species. I have host plants for species, but I do not track exact distribution of each plant species of the project. The same in UCD, the distribution of parasitoids is tracked, but not the distribution of the hosts. So, yes, it is nice to have a checkbox to see if the distribution matches both the subject and the object. But default behavior, I would expect the match on either side.


move to Visual Studio 2017

https://www.appveyor.com/docs/build-environment/#pre-installed-software
Will allow use of docker for example to use httpbin

Isn't this the same as #3400?

No, this is already fixed in #4340


refactor(client): Stabilize and simplify tests

Closes #39 and re-closes #29

:tada: This PR is included in version 1.9.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


PHP Fatal error:  Uncaught TypeError

Hi,
Thank you for your package! However, I've encountered an Uncaught TypeError during running the command. Could you please take a look? Thank you!
PHP Warning:  Use of undefined constant CUSTOM_USER_TABLE - assumed 'CUSTOM_USER_TABLE' (this will throw an Error in a future version of PHP) in phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(1138) : eval()'d code on line 84
PHP Warning:  Use of undefined constant CUSTOM_USER_META_TABLE - assumed 'CUSTOM_USER_META_TABLE' (this will throw an Error in a future version of PHP) in phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(1138) : eval()'d code on line 85
PHP Fatal error:  Uncaught TypeError: Argument 1 passed to TypistTech\ImageOptimizeCommand\AttachmentRepository::take() must be of the type integer, string given, called in /root/.wp-cli/packages/vendor/typisttech/image-optimize-command/src/ImageOptimizeCommand.php on line 30 and defined in /root/.wp-cli/packages/vendor/typisttech/image-optimize-command/src/AttachmentRepository.php:20
Stack trace:
#0 /root/.wp-cli/packages/vendor/typisttech/image-optimize-command/src/ImageOptimizeCommand.php(30): TypistTech\ImageOptimizeCommand\AttachmentRepository::take('10')
#1 [internal function]: TypistTech\ImageOptimizeCommand\ImageOptimizeCommand->run(Array, Array)
#2 phar:///usr/local/bin/wp/php/WP_CLI/Dispatcher/CommandFactory.php(89): call_user_func(Array, Array, Array)
#3 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
#4 phar:///usr/local/bin/wp/php/WP_CLI/Dispatcher/Subcommand.php(425): call_user_func(Object(Closure), Array, Array)
#5 phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(35 in /root/.wp-cli/packages/vendor/typisttech/image-optimize-command/src/AttachmentRepository.php on line 20
Fatal error: Uncaught TypeError: Argument 1 passed to TypistTech\ImageOptimizeCommand\AttachmentRepository::take() must be of the type integer, string given, called in /root/.wp-cli/packages/vendor/typisttech/image-optimize-command/src/ImageOptimizeCommand.php on line 30 and defined in /root/.wp-cli/packages/vendor/typisttech/image-optimize-command/src/AttachmentRepository.php:20
Stack trace:
#0 /root/.wp-cli/packages/vendor/typisttech/image-optimize-command/src/ImageOptimizeCommand.php(30): TypistTech\ImageOptimizeCommand\AttachmentRepository::take('10')
#1 [internal function]: TypistTech\ImageOptimizeCommand\ImageOptimizeCommand->run(Array, Array)
#2 phar:///usr/local/bin/wp/php/WP_CLI/Dispatcher/CommandFactory.php(89): call_user_func(Array, Array, Array)
#3 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
#4 phar:///usr/local/bin/wp/php/WP_CLI/Dispatcher/Subcommand.php(425): call_user_func(Object(Closure), Array, Array)
#5 phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(35 in /root/.wp-cli/packages/vendor/typisttech/image-optimize-command/src/AttachmentRepository.php on line 20

My PHP version is 7.2.4 & WP CLI version is 1.5.1

Thanks for reporting!
Bug confirmed when invoking via command line:
$ wp image-optimize run --limit=10
$ wp image-optimize run --limit='10'

Or, directly via PHP code:
ImageOptimizeCommand::run(null, [
    'limit' => '10', // string!
);


feat: add cors to script and preload tags

Types of changes

[ x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Resolves: #6634
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

@clarkdo OK, I agree with you, and i do not have enough time on it

Cool, I’ll work on this

@clarkdo, this PR seems good to go but wanted to check if there was anything i can do to help get over the line and merged?  Thanks!

@Austio Sorry, I’ll try to find some times to work on it this week.

@clarkdo no need to be sorry, any way that i can help?

@Austio I'll try to make a pr this week, if you can test with your app, it would be great!

As Vue 2 won't be release frequently, so let's fix this issue in Nuxt for now, I'll open a new pr.


[p4_symbolic]:Initial inport of Ir Table entries and test Code.

Build Result:
sonic-buildimage/src/sonic-p4rt/sonic-pins/p4_symbolic$ ./key.sh .
Keyword check Passed.

sonic/src/sonic-p4rt/sonic-pins$ bazel build $BAZEL_BUILD_OPTS ...
bazel-out/k8-fastbuild/bin/external/com_github_google_glog/_virtual_includes/glog/glog/logging.h:211:53: note: in definition of macro 'GOOGLE_PREDICT_TRUE'
  211 | #define GOOGLE_PREDICT_TRUE(x) (__builtin_expect(!!(x), 1))
      |                                                     ^
bazel-out/k8-fastbuild/bin/external/com_github_google_glog/_virtual_includes/glog/glog/logging.h:852:1: note: in expansion of macro 'DEFINE_CHECK_OP_IMPL'
  852 | DEFINE_CHECK_OP_IMPL(Check_EQ, ==)  // Compilation error with CHECK_EQ(NULL, x)?
      | ^~~~~~~~~~~~~~~~~~~~
INFO: Elapsed time: 4091.686s, Critical Path: 103.48s
INFO: 6584 processes: 1645 internal, 4939 linux-sandbox.
INFO: Build completed successfully, 6584 total actions

sonic/src/sonic-p4rt/sonic-pins$ bazel test $BAZEL_BUILD_OPTS --cache_test_results=no ...
INFO: Analyzed 311 targets (0 packages loaded, 270 targets configured).
INFO: Found 195 targets and 116 test targets...
INFO: Elapsed time: 114.841s, Critical Path: 20.59s
INFO: 121 processes: 128 linux-sandbox, 17 local.
INFO: Build completed successfully, 121 total actions
//gutil:collections_test                                                 PASSED in 0.7s
//sai_p4/instantiations/google/tests:p4_constraints_integration_test     PASSED in 0.9s
//sai_p4/tools:p4info_tools_test                                         PASSED in 0.7s
//sai_p4/instantiations/google/test_tools:table_entry_generator_test     PASSED in 14.1s
  Stats over 5 runs: max = 14.1s, min = 1.1s, avg = 4.8s, dev = 4.8s

Executed 116 out of 116 tests: 116 tests pass.
INFO: Build completed successfully, 121 total actions

@kishanps, Could you please review.
Thanks.


docs: remove language parameter from path of cognito pricing url

Description of changes:
Remove /es from path of cognito pricing url in cost.md and architecture.md

@Ausgefuchster  Thanks for the update!


c.state Pennsylvania is showing a picture of military men in an area instead of a map of the state.

Why is this happening?

The map that the bot provides is scraped from wikipedia. Unfortunately some states and countries don't have maps and have an image instead, which is why an image appears instead of a map. I hope that explains the issue.


Git Workshop 2023 Assignments!

Duplicate pull request of #9
In #9, the base branch is 2023 but in #10 the base branch isn't 2023 with is mistake as we have shown to open pull request in 2023 base branch.


Plots: View tooltip with table of metric values across selected experiments

When hovering over a metric plot, I can see tooltips of the metric value for the curve under the cursor (though this takes some patience to get the cursor in the right place also due to lack of zoom, cf. #4530). What I often use and find quite useful with TensorBoard is that this would show me the metric values of all curves either at this or the latest available step (x coordinate). This is quite useful to compare the curves at different timepoints. Would be great if this was also supported by the DVC Plots towards replacing my use of TensorBoard.
Example screenshot from TensorBoard:

@daavoo @dberenbaum the on hover vertical line was dropped from dvc-render in https://github.com/iterative/dvc-render/pull/99. Do you remember the reason for that change?
@aschuh-hf you should be able to achieve this by using a custom template. In order to achieve this add the template to your project and specify the custom template in your dvc.yaml. I've provided a quick example below. I am sure you'd be able to extend this to get the desired behaviour.

custom template
  "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
  "data": { "values": "<DVC_METRIC_DATA>" },
  "title": "<DVC_METRIC_TITLE>",
  "width": 300,
  "height": 300,
  "layer": [
    {
      "encoding": {
        "x": {
          "field": "<DVC_METRIC_X>",
          "type": "quantitative",
          "title": "<DVC_METRIC_X_LABEL>"
        },
        "y": {
          "field": "<DVC_METRIC_Y>",
          "type": "quantitative",
          "title": "<DVC_METRIC_Y_LABEL>",
          "scale": { "zero": false }
        },
        "color": { "field": "rev", "type": "nominal" }
      },
      "layer": [
        { "mark": "line" },
        {
          "selection": {
            "label": {
              "type": "single",
              "nearest": true,
              "on": "mouseover",
              "encodings": ["x"],
              "empty": "none",
              "clear": "mouseout"
            }
          },
          "mark": "point",
          "encoding": {
            "opacity": {
              "condition": {
                "selection": "label",
                "value": 1
              },
              "value": 0
            }
          }
        }
      ]
    },
    {
      "transform": [{ "filter": { "selection": "label" } }],
      "layer": [
        {
          "mark": { "type": "rule", "color": "gray" },
          "encoding": {
            "x": {
              "field": "<DVC_METRIC_X>",
              "type": "quantitative"
            }
          }
        },
        {
          "encoding": {
            "text": {
              "type": "quantitative",
              "field": "<DVC_METRIC_Y>"
            },
            "x": {
              "field": "<DVC_METRIC_X>",
              "type": "quantitative"
            },
            "y": {
              "field": "<DVC_METRIC_Y>",
              "type": "quantitative"
            }
          },
          "layer": [
            {
              "mark": {
                "type": "text",
                "align": "left",
                "dx": 5,
                "dy": -5
              },
              "encoding": {
                "color": {
                  "type": "nominal",
                  "field": "rev"
                }
              }
            }
          ]
        }
      ]
    }
  ]
}

dvc.yaml entry
plots:
  - training/plots/metrics/train/acc.tsv:
      template: ./template.json
      x: step
      y: acc
      y_label: accuracy

plot
https://github.com/iterative/vscode-dvc/assets/37993418/fe9724c6-750b-4a39-9ee1-5e91916c0c2b

Now that flexibility of customizing the plots is pretty neat! I'll give it a try.

Related repo and an issue in the Vega repo https://github.com/vega/vega-tooltip/issues/215. Overall we could try to utilize the vega-tooltip repo to do custom TB-like tooltip (which I agree are important). Most likely though we'll prioritize the migration / additional support for the Plotly engine (since Vega is too complicate to customize based on the user feedback and has some limitations in ML scenarios). So, let's us get back to this issue a bit later please @aschuh-hf as soon as we migrate to Plotly.

AFAICT from the PR, it was an attempt to copy tensorboard's ability to show multiple values per point, but it looks like it came at the expense of showing multiple points at once. From a quick look I'm not sure how easy it is to do both simultaneously even in plotly.

Most likely though we'll prioritize the migration / additional support for the Plotly engine (since Vega is too complicate to customize based on the user feedback and has some limitations in ML scenarios). So, let's us get back to this issue a bit later please @aschuh-hf as soon as we migrate to Plotly.

Sure, I can work with the template @mattseddon provided for now (and anyway often still use TensorBoard in parallel).
I also find Vega (or Lite), despite how powerful it may be quite difficult to get used to. So far I stayed away from it. I found https://vega.github.io/vega-lite/examples/interactive_multi_line_pivot_tooltip.html to be closest to what I would like, though I wasn't able to figure out how to have the tooltip list populated by the experiment revs rather than a hard-coded list of experiments as in the example.

show multiple values per point, but it looks like it came at the expense of showing multiple points at once

Indeed, I was wondering if that was possible. Maybe it's not the highest priority to have that ability, though I did find it quite useful to have the last available metric for any curve prior to the selected timepoint listed alongside others. One might interrupt training runs because its clear they won't perform as expected, especially in case of a hyper-parameter search (e.g., using Ray Tune). Or during live training runs compare the current metric with later times of other curves.

@aschuh-hf added to the same task list / requirements https://github.com/iterative/dvc-render/issues/7

WDYT about the tooltip shown here:
https://github.com/iterative/vscode-dvc/assets/37993418/241bda30-046a-4cad-a2a0-c7e7d0dd87e9

This looks great!

Is it correct, though, that similar to the template I found in the Vega-Lite examples, this requires to be able to set the list of revs in the template. Is there a <DVC_*> variable that can be used for this?
I.e., to replace this hard coded list of experiment revs in your example:
"encoding": {
    "x": {"field": "step", "type": "quantitative", "title": "step"},
    "color": {
      "legend": {"disable": false},
      "scale": {
        "domain": ["pagan-puns", "soppy-debs", "workspace"],
        "range": ["#945dd6", "#13adc7", "#f46837"]
      }
    },
    "strokeDash": {
      "field": "filename",
      "scale": {
        "domain": ["test/acc.tsv", "train/acc.tsv"],
        "range": [[1, 0], [8, 8]]
      },
      "legend": {
        "disable": false,
        "symbolFillColor": "transparent",
        "symbolStrokeColor": "grey"
      }
    },

I tried to adapt this to a template, and replaced the color specification above by
"color": {
    "field": "rev",
    "type": "nominal"
}

but I only get a single row with "undefined" in the tooltip. Also the numerical value displayed doesn't match the y axis / expected value. Could you help me adapt the template to get the result you show in your example? Thanks!

Adapted metrics plot template
{
    "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
    "data": {
        "values": "<DVC_METRIC_DATA>"
    },
    "title": "<DVC_METRIC_TITLE>",
    "width": "container",
    "height": "container",
    "params": [
        {
            "name": "smooth",
            "value": 0.001,
            "bind": {"input": "range", "min": 0.001, "max": 1, "step": 0.001}
        }
    ],
    "layer": [
        {
            "transform": [
                {
                    "pivot": "rev-filename",
                    "value": "<DVC_METRIC_Y>",
                    "groupby": ["<DVC_METRIC_X>"]
                }
            ],
            "mark": {
                "type": "rule",
                "tooltip": {
                    "content": "data"
                }
            },
            "encoding": {
                "opacity": {
                    "condition": {
                        "value": 0.3,
                        "param": "hover",
                        "empty": false
                    },
                    "value": 0
                }
            },
            "params": [
                {
                    "name": "hover",
                    "select": {
                        "type": "point",
                        "fields": [
                            "<DVC_METRIC_X>"
                        ],
                        "nearest": true,
                        "on": "mouseover",
                        "clear": "mouseout"
                    }
                }
            ]
        },
        {
            "encoding": {
                "y": {
                    "field": "<DVC_METRIC_Y>",
                    "type": "quantitative",
                    "title": "<DVC_METRIC_Y_LABEL>",
                    "scale": {
                        "zero": false
                    }
                },
                "color": {
                    "field": "rev",
                    "type": "nominal"
                }
            },
            "layer": [
                {
                    "mark": "line"
                },
                {
                    "transform": [
                        {
                            "filter": {
                                "param": "hover",
                                "empty": false
                            }
                        }
                    ],
                    "mark": "point"
                }
            ],
            "transform": [
                {
                    "loess": "<DVC_METRIC_Y>",
                    "on": "<DVC_METRIC_X>",
                    "groupby": [
                        "rev",
                        "filename",
                        "rev-filename",
                        "field",
                        "filename::field"
                    ],
                    "bandwidth": {"signal": "smooth"}
                }
            ]
        },
        {
            "mark": {
                "type": "line",
                "opacity": 0.2
            },
            "encoding": {
                "x": {
                    "field": "<DVC_METRIC_X>",
                    "type": "quantitative",
                    "title": "<DVC_METRIC_X_LABEL>"
                },
                "y": {
                    "field": "<DVC_METRIC_Y>",
                    "type": "quantitative",
                    "title": "<DVC_METRIC_Y_LABEL>",
                    "scale": {
                        "zero": false
                    }
                },
                "color": {
                    "field": "rev",
                    "type": "nominal"
                }
            }
        },
        {
            "mark": {
                "type": "circle",
                "size": 10
            },
            "encoding": {
                "x": {
                    "aggregate": "max",
                    "field": "<DVC_METRIC_X>",
                    "type": "quantitative",
                    "title": "<DVC_METRIC_X_LABEL>"
                },
                "y": {
                    "aggregate": {
                        "argmax": "<DVC_METRIC_X>"
                    },
                    "field": "<DVC_METRIC_Y>",
                    "type": "quantitative",
                    "title": "<DVC_METRIC_Y_LABEL>",
                    "scale": {
                        "zero": false
                    }
                },
                "color": {
                    "field": "rev",
                    "type": "nominal"
                }
            }
        }
    ],
    "encoding": {
        "x": {
            "field": "<DVC_METRIC_X>",
            "type": "quantitative",
            "title": "<DVC_METRIC_X_LABEL>"
        },
        "color": {
            "field": "rev",
            "type": "nominal",
            "legend": {
                "disable": false
            }
        },
        "shape": {
            "legend": {
                "disable": false,
                "symbolFillColor": "grey"
            }
        }
    }
}

Also note that with the template above, when I click on a plot to show the detail and test the new zoom and pan (which wasn't working for me with the previous template yet using v1.0.52 of the DVC extension), no plot is shown, just an empty canvas. Certainly because there's something off with my attempt to adjust the template.

I checked the output index.html of dvc plots show / dvc plots diff when using the --open flag and  realized that rev-filename as used in the example is not a data field of <DVC_METRIC_DATA>. So I replaced it with rev. The tooltip works when I view this index HTML page in the browser (there is an odd undefined rev, but that's likely a different issue).
I wasn't yet able to test it in the extension because dvc still uses the wrong template (not the one in the current modified dvc.yaml in the workspace). For the other dvc plots commands, I used the --template option to force a specific one I wanted to test.

Plot template
{
    "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
    "data": {
        "values": "<DVC_METRIC_DATA>"
    },
    "title": "<DVC_METRIC_TITLE>",
    "width": 800,
    "height": 600,
    "params": [
        {
            "name": "smooth",
            "value": 0.001,
            "bind": {"input": "range", "min": 0.001, "max": 1, "step": 0.001}
        }
    ],
    "layer": [
        {
            "transform": [
                {
                    "pivot": "rev",
                    "value": "<DVC_METRIC_Y>",
                    "groupby": ["<DVC_METRIC_X>"]
                }
            ],
            "mark": {
                "type": "rule",
                "tooltip": {
                    "content": "data"
                }
            },
            "encoding": {
                "opacity": {
                    "condition": {
                        "value": 0.3,
                        "param": "hover",
                        "empty": false
                    },
                    "value": 0
                }
            },
            "params": [
                {
                    "name": "hover",
                    "select": {
                        "type": "point",
                        "fields": [
                            "<DVC_METRIC_X>"
                        ],
                        "nearest": true,
                        "on": "mouseover",
                        "clear": "mouseout"
                    }
                }
            ]
        },
        {
            "encoding": {
                "y": {
                    "field": "<DVC_METRIC_Y>",
                    "type": "quantitative",
                    "title": "<DVC_METRIC_Y_LABEL>",
                    "scale": {
                        "zero": false
                    }
                },
                "color": {
                    "field": "rev",
                    "type": "nominal"
                }
            },
            "layer": [
                {
                    "mark": "line"
                },
                {
                    "transform": [
                        {
                            "filter": {
                                "param": "hover",
                                "empty": false
                            }
                        }
                    ],
                    "mark": "point"
                }
            ],
            "transform": [
                {
                    "loess": "<DVC_METRIC_Y>",
                    "on": "<DVC_METRIC_X>",
                    "groupby": [
                        "rev",
                        "filename",
                        "field",
                        "filename::field"
                    ],
                    "bandwidth": {"signal": "smooth"}
                }
            ]
        },
        {
            "mark": {
                "type": "line",
                "opacity": 0.2
            },
            "encoding": {
                "x": {
                    "field": "<DVC_METRIC_X>",
                    "type": "quantitative",
                    "title": "<DVC_METRIC_X_LABEL>"
                },
                "y": {
                    "field": "<DVC_METRIC_Y>",
                    "type": "quantitative",
                    "title": "<DVC_METRIC_Y_LABEL>",
                    "scale": {
                        "zero": false
                    }
                },
                "color": {
                    "field": "rev",
                    "type": "nominal"
                }
            }
        },
        {
            "mark": {
                "type": "circle",
                "size": 10
            },
            "encoding": {
                "x": {
                    "aggregate": "max",
                    "field": "<DVC_METRIC_X>",
                    "type": "quantitative",
                    "title": "<DVC_METRIC_X_LABEL>"
                },
                "y": {
                    "aggregate": {
                        "argmax": "<DVC_METRIC_X>"
                    },
                    "field": "<DVC_METRIC_Y>",
                    "type": "quantitative",
                    "title": "<DVC_METRIC_Y_LABEL>",
                    "scale": {
                        "zero": false
                    }
                },
                "color": {
                    "field": "rev",
                    "type": "nominal"
                }
            }
        }
    ],
    "encoding": {
        "x": {
            "field": "<DVC_METRIC_X>",
            "type": "quantitative",
            "title": "<DVC_METRIC_X_LABEL>"
        },
        "color": {
            "field": "rev",
            "type": "nominal",
            "legend": {
                "disable": false
            }
        },
        "shape": {
            "legend": {
                "disable": false,
                "symbolFillColor": "grey"
            }
        }
    }
}

I'm sorry, the linked template was not designed to be reused or adapted. I was looking for feedback on the appearance/contents of the tooltip.
Seeing as you are only using rev and not filename or field in the template this one should work for you:

Custom template

{
  "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
  "data": {
    "values": "<DVC_METRIC_DATA>"
  },
  "title": "<DVC_METRIC_TITLE>",
  "width": "container",
  "height": "container",
  "params": [
    {
      "name": "smooth",
      "value": 0.001,
      "bind": {"input": "range", "min": 0.001, "max": 1, "<DVC_METRIC_X>": 0.001}
    }
  ],
  "layer": [
        {
      "encoding": {
        "y": {
          "field": "<DVC_METRIC_Y>",
          "type": "quantitative",
          "title": "<DVC_METRIC_Y_TITLE>",
          "scale": {"zero": false}
        },
        "color": {"field": "rev", "type": "nominal"}
      },
      "layer": [
        {"mark": "line"},
        {
          "transform": [{"filter": {"param": "hover", "empty": false}}],
          "mark": "point"
        }
      ],
      "transform": [
        {
          "loess": "<DVC_METRIC_Y>",
          "on": "<DVC_METRIC_X>",
          "groupby": ["rev"],
          "bandwidth": {"signal": "smooth"}
        }
      ]
    },
    {
      "transform": [
        {"pivot": "rev", "value": "<DVC_METRIC_Y>", "groupby": ["<DVC_METRIC_X>"]}
      ],
      "mark": {"type": "rule", "tooltip": {"content": "data"}},
      "encoding": {
        "opacity": {
          "condition": {"value": 0.3, "param": "hover", "empty": false},
          "value": 0
        }
      },
      "params": [
        {
          "name": "hover",
          "select": {
            "type": "point",
            "fields": ["<DVC_METRIC_X>"],
            "nearest": true,
            "on": "mouseover",
            "clear": "mouseout"
          }
        }
      ]
    },
    {
      "mark": {"type": "line", "opacity": 0.2},
      "params": [{ "bind": "scales", "name": "grid", "select": "interval" }],
      "encoding": {
        "x": {"field": "<DVC_METRIC_X>", "type": "quantitative", "title": "<DVC_METRIC_X>"},
        "y": {
          "field": "<DVC_METRIC_Y>",
          "type": "quantitative",
          "title": "<DVC_METRIC_Y_TITLE>",
          "scale": {"zero": false}
        }
      }
    },
    {
      "mark": {"type": "circle", "size": 10},
      "encoding": {
        "x": {
          "aggregate": "max",
          "field": "<DVC_METRIC_X>",
          "type": "quantitative",
          "title": "<DVC_METRIC_X>"
        },
        "y": {
          "aggregate": {"argmax": "<DVC_METRIC_X>"},
          "field": "<DVC_METRIC_Y>",
          "type": "quantitative",
          "title": "<DVC_METRIC_Y_TITLE>",
          "scale": {"zero": false}
        },
        "color": {"field": "rev", "type": "nominal"}
      }
    }
  ]
}

☝🏻 the above template should have zoom on scroll and the previously shown tooltips. Something similar should be the default template soon.

I wasn't yet able to test it in the extension because dvc still uses the wrong template (not the one in the current modified dvc.yaml in the workspace)

The only way to force DVC to use the updated template is to select the workspace as a revision for plotting.

Just FYI, I had to update one occurrence of acc in the provided template by <DVC_METRIC_Y>:
"transform": [
                {
                    "pivot": "rev",
                    "value": "<DVC_METRIC_Y>",
                    "groupby": [
                        "<DVC_METRIC_X>"
                    ]
                }
            ],


Extracting insertion/deletion data from aligned region of interest

Hello IGV team,
I am currently analyzing amplicons from an insect genomic DNA sample edited with CRISPR/Cas9. I am aware IGV offers insertion and deletion data by selecting a specific base pair of your aligned read(s). Is it possible to access and export this data for a highlighted region of interest from IGV?
Side note: I am aware this data is contained within .bam files, however extracting the information in a clean way is not so simple and can get a bit messy (i.e. with mpileup offered by bcftools). I would also like to add I do not intend to use this data in a clinical or therapeutic context, but instead am using it to analyze gene editing in insects - so although I'm aware this web app is not particularly intended for this purpose, the ability to this data from IGV would be extremely useful and sufficient for my application.
Thanks,
Joe

Extracting the data with samtools is pretty trivial if you know the region
samtools view  chr1:100-200
What information are you looking for, and in what format?

With samtools view, I can see the alignment results (mismatches, insertions, deletions) and count the sum of any one of these (or all) over a given range (i.e. chr1:100-200), however I would lose base pair resolution of this information (i.e. if my region is chr1:100-200, I will not be able to see indel counts for chr1:100, chr1:101, chr1:102, and so on). By manually clicking a position of my aligned read on IGV web app, I can obtain this information, but it is not scalable for many alignment files - is there a faster, higher-throughput way to do this via IGV or some package offered by IGV?
Thanks for the quick response!
Joe

I would find it really surprising if there isn't a simple tool to do this, but I assume you have looked.    This isn't the sort of thing we design IGV for, which is a visual tool,  but leave this open we will consider it for the future.

BTW, on a tangent here,  but where would you expect an insertion between positions 10 and 11 to be counted?

Great question - I am exploring variant calling programs to count these. Out of curiosity, how does IGV do this?

Yes there is no simple tool to do this. When you map variants with Minimap2 or unimap, you get a CS tag which is a newer type of MD type which is basically telling you what sequence is ins or del relative to the reference ( its what you see what you click the insertion in IGV ).
When you select regions in IGV you get a bed file. And when we call variants against this bed file using either sniffles2 --regions regions_igv.bed  --reference reference.fasta
It doesnt work as you explained with the mpileup example. In bcftools mpileup it doesnt work because the max ins length is limited to 500 based but when you increase it bugs.
You have the case where your region of interests spans multiple reads in your bam but only 1 region/gap in your reference.
You have the case where your region of interest on IGV spans the flanks of a gap in your query.bam and so samtools view -L cannot gap two reads of your query.bam with NNNN
You have the case were your region of interest spans multiple gaps in your reference.fasta but only 1 read in your query.bam, this makes took like ragtag or quartet crash.
There was an option on IGV to copy the consensus sequence of an alignment when you right click on the alignment. It doesnt even work and would extract the full consensus and doesn't even work when we paste it in notes..
Unfortunately no one ever solved this problem. I am trying to write a script and test it. Without much success.

@jsromanowski I'm not exactly sure what you are asking.   Are you asking about the insertion/deletion details of a single aligned read, or a pileup at a specific location of multiple aligned reads?    For a single read the indel information is in the alignment record, specifically the "cigar" string.   For a pileup at a location IGV simply counts the indels at that location for the alignments intersecting the location.
@Isoris I'm not following your discussion at all.   However there is no concept of a consensus sequence for a single alignment, by definition a consensus sequence the the consensus over a region of multiple alignments.   However that's a tangent.

Hi @jrobinso,
Thank you for clarifying. Let me rephrase my question for better understanding.
I'm asking whether IGV can be used to extract and manipulate data when there is a missing sequence in the reference (REF) relative to the alternate allele (ALT) or query (QRY). Specifically:

For single alignments: Could IGV allow the user to select specific reads (e.g., by clicking on them), highlight them in a different color, and then export these reads? Instead of creating a new consensus FASTA, the selected reads could replace the REF sequence over the specified region, gapping any missing positions with 'NNN' if necessary to maintain alignment.

For pileups: Could IGV provide an option to save the pileup as a genome graph, or export the alignment and variant information for further downstream analysis?

@Isoris No, thats not in IGV's scope.


Look into moving package.json into the top level dir

This would allow people to use a git url in their package.json since npm doesn't allow loading in subdirectories as a dependency.

fixed by bill in 29f62c5fbefd89822320f9bf5fc7161ccd7900a7