Improve active scan result by running multiple passes

Only running 1 active scan misses a few networks.
We should be able to provide a loop count in the API call to startActiveScan() so that an active scan gets better results (consolidated on multiple passes)

To be merged, we still need to consolidate results from multiple passes, that is to say, remove duplicates based on extended PAN ID.
We should first check if there is not already the same PANID+extended PAN ID known on this same channel.
If this is the case, then we will update the result rather than pushing a new value.
Otherwise, without that improvement, this is what we are getting when performing triple scan:
Scan succesfully started
EZSP_NETWORK_FOUND_HANDLER: New network found: EmberZigbeeNetwork: { [channel: 11][panId: 0xd4ef][extendedPanId: 0x89c1542a249278bc][allowingJoin: false][stackProfile: 0x02][nwkUpdateId: 0x00] }
Closing GP channel request window
Scan finished
Re-running active scan (2 loop(s) remaining)
Channel mask 800
Scan succesfully started
EZSP_NETWORK_FOUND_HANDLER: New network found: EmberZigbeeNetwork: { [channel: 11][panId: 0xd4ef][extendedPanId: 0x89c1542a249278bc][allowingJoin: false][stackProfile: 0x02][nwkUpdateId: 0x00] }
Scan finished
Re-running active scan (1 loop(s) remaining)
Channel mask 800
Scan succesfully started
EZSP_NETWORK_FOUND_HANDLER: New network found: EmberZigbeeNetwork: { [channel: 11][panId: 0xd4ef][extendedPanId: 0x89c1542a249278bc][allowingJoin: false][stackProfile: 0x02][nwkUpdateId: 0x00] }
Scan finished
3 zigbee network(s) found on channel 11:
Network:ZigbeeNetworkScanResult: { [channel: 11][lastHop: LQI=232, rssi=-42][panId: 0xd4ef][extendedPanId: 0x89c1542a249278bc][allowingJoin: false][stackProfile: 0x02][nwkUpdateId: 0x00] }
Network:ZigbeeNetworkScanResult: { [channel: 11][lastHop: LQI=228, rssi=-43][panId: 0xd4ef][extendedPanId: 0x89c1542a249278bc][allowingJoin: false][stackProfile: 0x02][nwkUpdateId: 0x00] }
Network:ZigbeeNetworkScanResult: { [channel: 11][lastHop: LQI=232, rssi=-42][panId: 0xd4ef][extendedPanId: 0x89c1542a249278bc][allowingJoin: false][stackProfile: 0x02][nwkUpdateId: 0x00] }


Interactive login

OSD-8115, OSD-8135, OSD-8138, OSD-8195

I'm unable to run the tests:
$ make test
Makefile:58: warning: overriding recipe for target 'test'
Makefile:54: warning: ignoring old recipe for target 'test'
which go-bindata || go get github.com/go-bindata/go-bindata/go-bindata
/usr/bin/which: no go-bindata in (/home/tomas/.local/bin:/home/tomas/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/bin)
go generate -x ./cmd/...
for cmd in $(ls cmd); do \
	go build -o "${cmd}" "./cmd/${cmd}" || exit 1; \
done
package test is not in GOROOT (/usr/lib/golang/src/test)
make: *** [Makefile:58: test] Error 1

I tried running make tools, but that didn't help either
$ make tools
Makefile:58: warning: overriding recipe for target 'test'
Makefile:54: warning: ignoring old recipe for target 'test'
which go-bindata || go get github.com/go-bindata/go-bindata/go-bindata
/usr/bin/which: no go-bindata in (/home/tomas/.local/bin:/home/tomas/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/bin)

@T0MASD fixed the makefile, tests haven't yet been implemented though so expect them to fail. Will be adding tests through another PR.

@supreeth7 would you please create one Jira with all the pending items in this PR, I am merging this one.


Improve support for GetItemMatrixFunc

I am developing a plugin to query OpenStack APIs via Steampipe (see here). I would like the user to interact with multiple installations of OpenStack at once, even within the same query so that when a certain installation is specified in the query, the plugin can collect the proper set of credentials, API endpoints etc. and perform the appropriate calls.
This requires the configuration schema to support more complex data structures than it currently does. I would like to have a configuration that under the "regions" parmeter has a list of maps:
{
   ... whatever ...
   "regions": [
        {
            "api_endpoint": "https://my_region_1/api/v1...",
            "api_key": "my_api_key_for_region_1",
            "api_secret": "my_api_secret_for_region_1"
        },
        {
            "api_endpoint": "https://my_region_2/api/v1...",
            "api_key": "my_api_key_for_region_2",
            "api_secret": "my_api_secret_for_region_2"
        },
        ... whatever ....
    ],
    ... whatever ....
}

This would allow the plugin to retrieve the proper entry from the regions list and use the values to connect to the API, based on the query contents. I have written a few Terraform providers and AFAICT there does not seem to be any problem in mixing Lists and Maps in HCLv2 configuration. The current implementation does not support TypeMap as a data type in configuration.
As an alternative, it would be nice if it were possible to configure multiple instances of the same plugin under different connection names so you can run:
select vm.id, vm.name from openstack_region_1;  // connect to region_1 based on region1.spc
select vm.id, vm.name from openstack_region_2;  // connect to region_2 based on region2.spc

I tried it but but I could not find instructions on how to do it and it does not seem to work.

Cool, I'll try it tomorrow as soon as I turn on my PC. This looks exactly like what I was looking for.

Great. To expand a bit further:

Each connection generally represents a single unit of credentials (account, installation, etc)
Connections are grouped with aggregators.
AWS Account is a good example of this unit.

In some cases, we want to do queries / gather data across multiple sources within a single connection. For example, a single AWS account has EC2 Instances in 16 regions. In this case, we support a "matrix" to fan out the hydration across many different calls and consolidate it into a single table in a single connection - https://pkg.go.dev/github.com/turbot/steampipe-plugin-sdk/v5/plugin#MatrixItemMapFunc
I think your use case calls for a connection per installation combined with aggregators, but wanted to call out the "matrix" capability too in case it's inspirational for future situations.

Thanks a lot @e-gineer I tried your suggestion and it works like a charm!
Thanks for the clarification, I see I was bending the "matrix" feature to a different use case and it would not fit properly in the big schema of things. Your suggestion addresses my problem perfectly.
This was the only major feature that I thought was lacking in my plugin and I'm glad there is nothing to do there. At this point I will be adding tables one at a time. If you're interested in taking ownership sometime and could spend a minute in reviewing if the work done so far complies with your guidelines, please consider doing so and opening issues.

Awesome @dihedron :rocket:
We have a plugin release checklist and @misraved will definitely reach out to give feedback on https://github.com/dihedron/steampipe-plugin-openstack as well!

glad you got this resolved @dihedron
Closing


should "--" signal an end to parsing?

Perhaps we should just put -- in _, and an implementer could fallback to calling slice on process.argv, if they observe it?

Yes, double dash should signal an end to parsing.

I assume _ is positionals. Not sure if you are wondering about ending the option processing, or about whether to include -- in positionals. In any case, a short answer...
I am happy with the currently implemented behaviour, that the -- is consumed and the remaining arguments are put into positionals (and not examined for options).
(I suggested README changes describing the current behaviour for -- in abandoned #34.)

Yes, this is generally the DX I've seen in Node.js-based tooling.

The current behaviour implemented in parseArgs is the same as in all the reference implementations from #76:
try-getopt-long % ./ex foo -- bar --option
non-option ARGV-elements: foo bar --option

try-commander % node index.js foo -- bar --option
positionals: [ 'foo', 'bar', '--option' ]

try-yargs % node index.js foo -- bar --option
{ _: [ 'foo', 'bar', '--option' ], '$0': 'index.js' }

try-minimist % node index.js foo -- bar --option
{ _: [ 'foo', 'bar', '--option' ] }


Is it possible to use this project directly for a code example for instrument recognition?

Can I output the labels directly with the pretrained model or do I need to do fine-tuning for openmic-2018

you can use the fine-tuned model on openmic here openmic-passt-s-f128-10sec-p16-s10-ap.85.pt
!pip install git+https://github.com/kkoutini/passt_hear21.git

import torch

from hear21passt.base import load_model
model = load_model(mode="logits").cuda()
state = torch.load("/path/to/openmic-passt-s-f128-10sec-p16-s10-ap.85.pt")
model.net.load_state_dict(state)
logits = model(wave_signal)

What is the order of the label set of logits？

the labels are in the same order as in the "openmic-2018.npz" file in the dataset here. I think it's the chronological order of the classes.

Thank you!


HTTP/2 Stream read/write/idle liveness checks

HTTP/2 provides multiplexing which is a mechanism designed to allow multiple logical data transfers over the same channel.  Each one of these logical data transfers is called a stream.  Netty currently does not provide a way to detect inactive streams the way IdleStateHandler, ReadTimeoutHandler, and WriteTimeoutHandler provides a mechanism to detect an inactive channel.  This would be a nice feature to have and may help simplify usage of this codec, and keeping resources lower on production deployments where potentially malicious or just general non-responsive clients (or servers) may exists.

taking assignment to keep track...nothing immediately planned on this...

@Scottmitch is this an old issue? I would think the topic of stream lifecycle management has been overtaken by #3448 and #3544

@nmittler - Yes this is an old issue, but I think it is still valid.  This is more about providing "aliveness" checks on individual streams.  I updated the title of the issue to clarify.

ah ok, do we really think this is important enough to target for 4.1.0.Beta5? Is it something you have an immediate need for?

@nmittler - Nope. Thanks for pointing that out...just habit...went on a click spree.


change language to english

Changes Proposed:

Issues Addressed:

Closes

SOURCE:

Tests Performed:

How to Test the Changes:

Instead of changing it to English, what I would do is keep both files. The README.md in English, and the README_ES.md in Spanish. Many modules have this, so that those of us who do not use English can also have a description of what the module does.

Instead of changing it to English, what I would do is keep both files. The README.md in English, and the README_ES.md in Spanish. Many modules have this, so that those of us who do not use English can also have a description of what the module does.

we could keep the config in English and the readme in both languages

Instead of changing it to English, what I would do is keep both files. The README.md in English, and the README_ES.md in Spanish. Many modules have this, so that those of us who do not use English can also have a description of what the module does.

we could keep the config in English and the readme in both languages

Yes, I was talking about the README

If you give me time, I'll make a commit on the change I'm mentioning.

@tarawow the future, as a recommendation, I would create a new branch when making a pull request, otherwise your branch will never match the parent's history. Although it is a detail that I really don't know if it makes sense, it is just a recommendation.


Relayer API for multisignature transactions

Relayer API for multisignature transactions
With the introduction of multisig into Universal Login the transaction is not immediately sent to the blockchain after the call to execute.
To remedy this I propose that the transaction lifecycle is acknowledged on the relayer side and made accessible through its api.
The execute call
When a transaction is to be made using UniversalLogin it is composed into a message object. This message object looks something like this:
const message = {
  from: 'universal_login_contract_address',
  to: 'recipient_address',
  data: '0x00',
  value: 0,
  ...moreStuff,
}

When Alice and Bob are both parties in the 2 of 2 multisig they have to both submit the same message to the relayer with different signatures.
Alice:
relayer.execute(message, alices_signature)

Bob:
relayer.execute(message, bobs_signature)

The getMessageStatus call
After Alice calls execute she would like to be able to know when Bob submits his signature of the message. In order to do so she polls the relayer:
relayer.getMessageStatus(hash(message)) -> COLLECTING_SIGNATURES (1 of 2, message)
relayer.getMessageStatus(hash(message)) -> COLLECTING_SIGNATURES (2 of 2, message)
relayer.getMessageStatus(hash(message)) -> PENDING_ON_CHAIN (0x1234...5678, message)
relayer.getMessageStatus(hash(message)) -> MINED_ON_CHAIN (0x1234...5678, message)

The getMessageStatus call returns a stage of the transaction lifecycle the transaction is in.
Transaction Lifecycle:
Non-error states:

UNKNOWN
COLLECTING_SIGNATURES (1 of N, message)
COLLECTING_SIGNATURES (2 of N, message)
...
COLLECTING_SIGNATURES (N of N, message)
WAITING_FOR_SUBMIT (message)
PENDING_ON_CHAIN (txHash, message)
MINED_ON_CHAIN (txHash, message)

Error states:

ERROR (message)

Transaction moves down through non-error states until reaching MINED_ON_CHAIN. If at any point an error happens it transitions to the ERROR state. The transaction can move through multiple states at once.
Ommisions
This issue does not concern itself with the method of sharing the message between participants of the multisig. This can probably be achieved via another mechanism.

CC @Giulio2002

I would be Happy of taking care of it

@marekkirejczyk @sz-piotr I am thinking of using a database to store the signatures, my question is: regarding the architecture of universal-login, do you consider acceptable using the PostgreSQL database that is already connected to the relayer or you prefer to store the signatures into a local variable in the relayer?

Yes


Include options from readme.md in usage.txt so output with yo --help

The yo options, as defined in the readme.md, were not available via the --help output.
Updated the usage.txt to cover the options mentioned there, and to clarify the difference between -h and --help.
Updated output now looks like this;
Usage: yo GENERATOR [args] [options]

General options:
  -h 		     # Enter interactive help menu
  --help     	 # Print this info and generator's options and usage
  -f, --force    # Overwrite files that already exist
  --version	     # Print Yo's version
  --no-color	 # flag to disable colors.
  --[no-]insight # toggle anonymous tracking
  --generators	 # will output the available generators

LGTM, thanks!


Failed: Cannot read property 'RETURN' of undefined

I have a ajax dropdown list from which I have to select a option , I used following peice of code.
The error coming is :    Failed: Cannot read property 'RETURN' of undefined
I also tried ENTER in place of RETURN
var item = element(By.css('ul.dropdown-menu > li:nth-child(3)'));
item.sendKeys(protractor.key.RETURN).then(function () {

You want Key with a capital.


Fixes #209: GMUGeometryRenderer is not applying the external styles when no styleMaps are specified

Fixes #209: GMUGeometryRenderer is not applying the external styles when no styleMaps are specified

[x] Test passing
[x] CLA submitted

Anyone here who can review this?

Lgtm :shipit:
Thanks for contributing!


Missing item: Commendation of Kael'thas

Links to WOTLK Wowhead for each item:
https://www.wowhead.com/wotlk/item=34473/commendation-of-kaelthas
some tanks may still be using this - my bear is

https://github.com/wowsims/wotlk/pull/1534


Error: Cannot read property 'type' of undefined (line 474)

Call:
Chess("8/3r4/8/8/8/2R5/1Q6/8 b KQkq - 0 1").game_over();

In file chess.js:
Error: Cannot read property 'type' of undefined (line 474)
      /* if pawn promotion */
      if (board[from].type === PAWN &&
//.........etc...................

Your FEN string is missing the positions of both the white and black kings.

Please advise me how I can check position (FEN position is legal) using chess.js.


Initial import errors

Upon initial startup, I got all of these error messages and the plugin doesn't load until a restart. I think we can refactor the import files so they aren't tied to non-existent cached data.

ERROR: Unable to open file: res://.godot/imported/icon_terrain3d.svg-7b79ba28bfbcfe67d066affa10c60bff.ctex.
   at: (scene/resources/texture.cpp:814)
ERROR: Failed loading resource: res://.godot/imported/icon_terrain3d.svg-7b79ba28bfbcfe67d066affa10c60bff.ctex. Make sure resources have been imported by opening the project in th.
   at: (core/io/resource_loader.cpp:214)
ERROR: Failed loading resource: res://addons/terrain/icons/icon_terrain3d.svg. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:214)
ERROR: Unable to open file: res://.godot/imported/icon_terrain_material.svg-3e0aae3669fe2efeaf707a6892b5f063.ctex.
   at: (scene/resources/texture.cpp:814)
ERROR: Failed loading resource: res://.godot/imported/icon_terrain_material.svg-3e0aae3669fe2efeaf707a6892b5f063.ctex. Make sure resources have been imported by opening the projec.
   at: (core/io/resource_loader.cpp:214)
ERROR: Failed loading resource: res://addons/terrain/icons/icon_terrain_material.svg. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:214)
ERROR: Unable to open file: res://.godot/imported/icon_terrain_layer_material.svg-810362a81388cf3fc0c37a0a04912bb9.ctex.
   at: (scene/resources/texture.cpp:814)
ERROR: Failed loading resource: res://.godot/imported/icon_terrain_layer_material.svg-810362a81388cf3fc0c37a0a04912bb9.ctex. Make sure resources have been imported by opening the .
   at: (core/io/resource_loader.cpp:214)
ERROR: Failed loading resource: res://addons/terrain/icons/icon_terrain_layer_material.svg. Make sure resources have been imported by opening the project in the editor at least on.
   at: (core/io/resource_loader.cpp:214)
ERROR: Unable to open file: res://.godot/imported/icon_map_add.svg-bc7f88fd1deaf4cbf31b1d4c8c6d0b2c.ctex.
   at: (scene/resources/texture.cpp:814)
ERROR: Failed loading resource: res://.godot/imported/icon_map_add.svg-bc7f88fd1deaf4cbf31b1d4c8c6d0b2c.ctex. Make sure resources have been imported by opening the project in the .
   at: (core/io/resource_loader.cpp:214)
ERROR: Failed loading resource: res://addons/terrain/icons/icon_map_add.svg. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:214)
ERROR: Unable to open file: res://.godot/imported/icon_map_remove.svg-150dbd16519910c64a5accd6a15577ea.ctex.
   at: (scene/resources/texture.cpp:814)
ERROR: Failed loading resource: res://.godot/imported/icon_map_remove.svg-150dbd16519910c64a5accd6a15577ea.ctex. Make sure resources have been imported by opening the project in t.
   at: (core/io/resource_loader.cpp:214)
ERROR: Failed loading resource: res://addons/terrain/icons/icon_map_remove.svg. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:214)
ERROR: Unable to open file: res://.godot/imported/icon_height_add.svg-84485c2ba0abdc6736a7102d21854ca4.ctex.
   at: (scene/resources/texture.cpp:814)
ERROR: Failed loading resource: res://.godot/imported/icon_height_add.svg-84485c2ba0abdc6736a7102d21854ca4.ctex. Make sure resources have been imported by opening the project in t.
   at: (core/io/resource_loader.cpp:214)
ERROR: Failed loading resource: res://addons/terrain/icons/icon_height_add.svg. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:214)
ERROR: Unable to open file: res://.godot/imported/icon_height_sub.svg-bd2b838af515ef43c8b3c9bc412ab7b6.ctex.
   at: (scene/resources/texture.cpp:814)
ERROR: Failed loading resource: res://.godot/imported/icon_height_sub.svg-bd2b838af515ef43c8b3c9bc412ab7b6.ctex. Make sure resources have been imported by opening the project in t.
   at: (core/io/resource_loader.cpp:214)
ERROR: Failed loading resource: res://addons/terrain/icons/icon_height_sub.svg. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:214)
ERROR: Unable to open file: res://.godot/imported/icon_height_mul.svg-94df27cd9453a24dccf06b437c08d376.ctex.
   at: (scene/resources/texture.cpp:814)
ERROR: Failed loading resource: res://.godot/imported/icon_height_mul.svg-94df27cd9453a24dccf06b437c08d376.ctex. Make sure resources have been imported by opening the project in t.
   at: (core/io/resource_loader.cpp:214)
ERROR: Failed loading resource: res://addons/terrain/icons/icon_height_mul.svg. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:214)
ERROR: Unable to open file: res://.godot/imported/icon_height_flat.svg-dcafa26c94284e57fa4f103237659863.ctex.
   at: (scene/resources/texture.cpp:814)
ERROR: Failed loading resource: res://.godot/imported/icon_height_flat.svg-dcafa26c94284e57fa4f103237659863.ctex. Make sure resources have been imported by opening the project in .
   at: (core/io/resource_loader.cpp:214)
ERROR: Failed loading resource: res://addons/terrain/icons/icon_height_flat.svg. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:214)
SCRIPT ERROR: Parse Error: Could not preload resource file "res://addons/terrain/icons/icon_terrain3d.svg".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:4)
SCRIPT ERROR: Parse Error: Could not resolve type for constant "ICON_TERRAIN".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:4)
SCRIPT ERROR: Parse Error: Could not preload resource file "res://addons/terrain/icons/icon_terrain_material.svg".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:5)
SCRIPT ERROR: Parse Error: Could not resolve type for constant "ICON_TERRAIN_MATERIAL".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:5)
SCRIPT ERROR: Parse Error: Could not preload resource file "res://addons/terrain/icons/icon_terrain_layer_material.svg".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:6)
SCRIPT ERROR: Parse Error: Could not resolve type for constant "ICON_LAYER_MATERIAL".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:6)
SCRIPT ERROR: Parse Error: "Terrain3D" was not found in the current scope.
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:8)
SCRIPT ERROR: Parse Error: Could not preload resource file "res://addons/terrain/icons/icon_map_add.svg".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:183)
SCRIPT ERROR: Parse Error: Could not resolve type for constant "ICON_MAP_ADD".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:183)
SCRIPT ERROR: Parse Error: Could not preload resource file "res://addons/terrain/icons/icon_map_remove.svg".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:184)
SCRIPT ERROR: Parse Error: Could not resolve type for constant "ICON_MAP_REMOVE".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:184)
SCRIPT ERROR: Parse Error: Could not preload resource file "res://addons/terrain/icons/icon_height_add.svg".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:185)
SCRIPT ERROR: Parse Error: Could not resolve type for constant "ICON_HEIGHT_ADD".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:185)
SCRIPT ERROR: Parse Error: Could not preload resource file "res://addons/terrain/icons/icon_height_sub.svg".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:186)
SCRIPT ERROR: Parse Error: Could not resolve type for constant "ICON_HEIGHT_SUB".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:186)
SCRIPT ERROR: Parse Error: Could not preload resource file "res://addons/terrain/icons/icon_height_mul.svg".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:187)
SCRIPT ERROR: Parse Error: Could not resolve type for constant "ICON_HEIGHT_MUL".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:187)
SCRIPT ERROR: Parse Error: Could not preload resource file "res://addons/terrain/icons/icon_height_flat.svg".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:188)
SCRIPT ERROR: Parse Error: Could not resolve type for constant "ICON_HEIGHT_FLAT".
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:188)
SCRIPT ERROR: Parse Error: Identifier "Terrain3D" not declared in the current scope.
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:42)
SCRIPT ERROR: Parse Error: Identifier "Terrain3D" not declared in the current scope.
          at: GDScript::reload (res://addons/terrain/editor/editor.gd:45)

Also upon first load, Jolt physics, a gdextension plugin, brings up a popup that says "Godot needs to restart" with a restart button. It doesn't crash like Terrain3D does. Look into how that works.

For the restart prompt, it looks like the godot-jolt GDExtension simply calls ProjectSettings' set_restart_if_changed() during setup of initial plugin settings.


Error-only log printing

Can there be an option that lets us control how verbose the log printing is? With thousands of clients and hundreds of messages, it is going to be quite excessive to have millions of

websocketproxy: copying from client to backend completed without error.
websocketproxy: copying from backend to client completed without error.

in the logs, especially when operations are completing successfully.

I just noticed a pull request that fixes this: #17


Reseting the database?

Does the postgres database need to reset (to empty), when the app is built again from scratch, by running:
yarn create redwood-app --ts ./redwood-stripe
Alternatively, is this issue a consequence of not resetting the database first?

I'm not sure, it shouldn't be necessary imho, but you can use yarn rw prisma migrate reset to reset the db, it doesn't hurt

In order to facilitate a clean regeneration of the app:

Deleted redwood-app folder
Run yarn create redwood-app --ts ./redwood-stripe and yarn rw setup ui tailwindcss
Edited the just generated prisma.schema to set the provider to be postgres, and define the rest of required data
Created the .env file with all needed information
Run yarn rw prisma migrate reset - resulting with

Running Prisma CLI...
$ yarn prisma migrate reset --schema /Users/nik/dev/work/redwood/rw-community/stripe/my-generalui/redwood-stripe/api/db/schema.prisma

Environment variables loaded from .env
Prisma schema loaded from api/db/schema.prisma
Datasource "db": PostgreSQL database "redwoodstripe", schema "public" at "localhost:5432"

✔ Are you sure you want to reset your database? All data will be lost. … yes

Database reset successful

✔ Generated Prisma Client (3.15.2 | library) to ./node_modules/@pr
isma/client in 98ms

Running seed command `yarn rw exec seed` ...
[11:41:47] Generating Prisma client [started]
[11:41:47] Generating Prisma client [completed]
[11:41:47] Running script [started]

Using the default './scripts/seed.{js,ts}' template
Edit the file to add seed data

[11:41:48] Running script [completed]

🌱  The seed command has been executed.

Note that resetting the database using RedwoodJS generator has all kind of side effects.


Lack of documentation for submsg_callback

This setting, which I only know about after a day of debugging nanopb trying to call a null callback, seems to only be documented in a github comment. This should be put on the documentation and possibly set default on.

Would you be able to suggest a place in documentation where this would be easily found? I'm getting increasingly blind to missing stuff in the docs, due to knowing the internals.

The compilation options section on https://jpa.kapsi.fi/nanopb/docs/reference.html ?


Heb response fixes

Changed to use past tense + some grammar fixes. Thanks for your work!

Previous one was just merged. Not needed.


⚠ Jenkins Plugins Artifactory has degraded performance

In adb6f7c, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1144 ms

Resolved: Jenkins Plugins Artifactory performance has improved in c03d0e1 after 25 minutes.


Entrust plugin - Additional Test and fixes

Fixed an error that manifests in shorter certificate durations.
Added Test for certificate-Date-check

Coverage increased (+0.08%) to 58.052% when pulling e67fc09bc86f0a7a3d844b739ff512138db3e25c on sirferl:entrust-plugin into e078d331031bd5b7caa5a7d4cd39c719322b9f1f on Netflix:master.

@hosseinsh  Please merge this. I fixed an error in Entrust Plugin when specifying the expiration date. I added a second Test for this functionality. I can also tell you, there is an Azure-Keyvault-Destination Plugin in the making !

hey @sirferl, thanks for the PR! merging it now.
Also good luck with the Azure-Keyvault-Destination Plugin!

thank you @sirferl . I really like your language cleanup...


Update swaccha-static-adblock-filters.txt

noticed common theme of bigyaapan/bigyapan gotta try catchem all. Let me know your thoughts.

Thank you but rather than generic, keeping the filters explicit to the specific site is preferable because you never know what it might block.


Add Poisson tensor generators

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (33415ef) 100.00% compared to head (a2ad747) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #57   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           39        40    +1
  Lines         1388      1416   +28
  Branches        99       100    +1
=========================================
+ Hits          1388      1416   +28

Files Changed
Coverage Δ

src/startorch/tensor/__init__.py
100.00% <100.00%> (ø)

src/startorch/tensor/poisson.py
100.00% <100.00%> (ø)

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


Add support for code generator property name hints

This will allow the JSON model to suggest to language generators how to call the requests body parameter if it's a generic and not a structured object.
It's extremely useful for clients that abstract away the HTTP lingo from the surface API of the client.
Example usage:
/**
 * @rest_spec_name index
 * @since 0.0.0
 * @stability stable
 * @class_serializer IndexRequestFormatter`1`
 */
interface IndexRequest<TDocument> extends RequestBase {
  path_parts?: {
    ...
  }
  query_parameters?: {
    ...
  }
  /** @identifier document */
  body?: TDocument
}

How it will look like in the JSON model:
"bodyIdentifier": "document",

@swallez I'm afraid I have to disagree. I think it's better to be explicit rather than have a rule written somewhere in the documentation and force every language generator to rewrite this logic. The model is machine-friendly, and we should keep it in that way without having external conventions.
Furthermore, we have the @identifier tag in place already, so we add nothing more than a field in the json model.

we add nothing more than a field in the json model

This is what I'd like to avoid, only for 2 occurences, when the information is already out there. And if we consider that dropping the T is too complex (I don't), then we should just move away from that convention in the model.
FWIW this is the only occurrence of the hungarian notation in our specs.
Adding something to the json model should not be taken lightly and we should keep it as minimal as possible.

we have the @identifier tag in place already

This is a very different use case. This tag is necessary for enums when values on the wire are not case insensitive distinct and so cannot be used to generate distinct identifiers following a target language's naming conventions. These values are not defined by us (spec writers). The case of open generic parameters is different as we choose their names.
So il all likelyhood we will end up with:
/** @identifier foo */
body?: TFoo

This @identifier tag brings no real value if it's the same (minus the T) as the generic parameter name. And if it is different then we have to question ourselves why this is the case, furthermore considering that body will be the only place where this open parameter is used.

After internal discussion we have decided to bench this one out and revisit it in the future.
Language generators should derive the body name from the generic where it applies.

Having thought more about this, I finally understood where my discomfort with the proposed change comes from. The change is as follows:
  body?: ValueBody | PropertiesBody
  behaviors?: Implements[]
  attachedBehaviors?: string[]
  /**
   * The parameter name language generator should use,
   * normally used when the entire body is a generic.
   */
  bodyIdentifier?: string

As it is, it is "polluting" the main request definition with a field that is only applicable for request bodies defined as a single value rather than a set of properties. And the doc comment further constrains the applicable scenarios to generic parameters only.
Now we actually have this distinction built into the body definition: body?: ValueBody | PropertiesBody. So this feature belongs to ValueBody and not to Request (and BTW the fact that we had to name it bodyIdentifier and not just identifier should have been a warning sign):
export class ValueBody {
  kind: 'value'
  value: ValueOf
  /** Identifier to use to represent the body in the request structure */
  identifier?: string
}

Now is this really needed?
I suggested to use the generic parameter name as the identifier. It does work with the use cases that we currently have, that is when ValueBody.body is a simple InstanceOf { type: <the open generic parameter>}, i.e. within the limits of the "when the entire body is a generic" constraint. But it doesn't work for more complex declarations that are permitted by the model and can also be expressed in the input spec.
So I'm changing my mind. If identifier is part of ValueBody as suggested above, I'll happily LGTM this PR.
Note also the change in the doc comment that no longer mentions generic parameters. It's just a property of body-as-a-value, whatever its type.
Modeling is hard, and metamodeling even more 😉

I like your suggestion @swallez! I'll update the pr to implement it :)


Error installation

Describe the bug
Hello,
I can't install btcli from pip3 install bittensor and from github install, on my ubuntu 22.04.4 LTS server
I have the error:
error: subprocess-exited-with-error

  × Building wheel for ansible-vault (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [73 lines of output]
      /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
        warnings.warn(
[...]
        File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 103, in __getattr__
          raise AttributeError(attr)
      AttributeError: install_layout. Did you mean: 'install_platlib'?
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for ansible-vault
Failed to build ansible-vault
ERROR: Could not build wheels for ansible-vault, which is required to install pyproject.toml-based projects

To Reproduce

Login on my server
run pip3 install bittensor

Same for git clone & python3 -m pip ...
Expected behavior
Install btcli.
Screenshots
No response
Environment
Ubuntu 22.04.4 LTS x86_64
Additional context
Can I give any other information?

It's an issue with ansible_vault not you


$HOME on Non-Root Volume Produces Invalid User Error and Config Load Failure

If the user's home directory is on a non-root volume (macOS 10.12.6), then root cannot read the metadata on $HOME/.config/karabiner/karabiner.json, and so a console message is logged that the configuration is from an invalid user.  Here is what the owner looks like when listed as root:
# ls -alh karabiner.json
-rw-r--r-- 1 _unknown _unknown 2.1K Aug 10 18:11 karabiner.json

This causes the configuration not to be loaded.  When running the same config as a user on the same machine, but with $HOME on the root volume, the config loads fine.  Here's how the owner looks from root for that config file:
# ls -alh karabiner.json
-rw-r--r-- 1 admin staff 1.8K Aug 10 18:29 karabiner.json

The workaround I have found is to install the config as global from the root-home user.

You have to enable owner ship to the external volume.
https://apple.stackexchange.com/questions/53215/change-ignore-ownership-on-this-volume-from-the-command-line-for-mac-os-x-volu

That seemed to do the trick.  I also needed to chown the files to myself.  Thank you very much for the tip.


Test case timing information and ordering

I think it would be nice if cargo test would output timing information about each test it runs. That way users can see where to spend effort if one tries to make a test suite run faster.
It would also be nice if one could influence the order in which test cases are started. Most of my tests finish in an instant, but I have one that does more exhaustive testing. It would be good to have that test started first so it can crunch away in its own thread while the other tests are processed on the other cores. Put differently: I don't want this test to be started last since I'll run out of quick and fast tests to run on my other cores.
Testing... Okay, it seems that Cargo works in the following way:

Test functions are started in alphabetical order
The --test-threads flag is set to the number of CPUs

The documentation says that

By default, all tests are run in parallel. This can be altered with the --test-threads flag or the RUST_TEST_THREADS environment variable when running tests (set it to 1).

I first read that as saying "we spawn a thread per test so they all start executing in parallel". That would alleviate my problem above since the overall time for the test run would become the time for the longest running test. However, testing reveals that --test-threads is set equal to the number of CPUs (which is more sensible overall, though twice the number of CPUs could also be a good default in case the tests do even a slight amount of I/O).
If Cargo had timing information from past test runs, then it could use that to start the slowest tests first. Assuming tests are independent, it seems to me that such an order should reduce the overall test time to the time of the longest running test. I think the timing information could be saved inside the target/ directory.
Does this sound like a good idea?

Thanks for the report! I think this may be a better issue for rust-lang/rust? The libtest framework (the test harness) is up there

Yes, definitely. I started searching for the help text above and couldn't find it in Cargo :-)
I'll close it here and open a new issue in the right tracker.

I couldn't find an issue on rust-lang/rust so I opened one here: ust-lang/rust#46610
Note that my issue only addresses the timing issue, not the ordering.


docs: Navbar doc fixes

Fixes two issues with the NavBar docs

The use of type="light|dark" has been replaced with data-bs-theme="light|dark" in order to modify the text color of the NavBar.  I've replaced all cases in the samples and updated the description.  This addresses #1507 and makes the samples readable again.
Changed the classes in the initial sample to make the comment stating that a portion of the navbar would be right aligned accurate.  This was a matter of changing me-auto to ms-auto to conform with bootstrap 5's utility classes.  This addresses #1510

Small replication
Fixes #1507 and #1510
PR checklist

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix :bug: - fix(...)
[ ] Feature - feat(...)
[ ] ARIA accessibility - fix(...)
[x] Documentation update - docs(...)
[ ] Other (please describe)

The PR fulfills these requirements:

[x] Pull request title and all commits follow the Conventional Commits convention or has an override in this pull request body This is very important, as the CHANGELOG is generated from these messages, and determines the next version type. Pull requests that do not follow conventional commits or do not have an override will be denied

Use the color mode options rather than the raw data-bs-theme attribute. Then make a section about it, if there isn't one already, discussing all three options -- directive, conposable, and raw attribute

Okay, I looked into the options you talked about in a little more detail and I still think the primary use of overriding the text color is to use the raw attribute to override the underlying theme text color when the variant is set so that changing the light/dark theme doesn't make the text in the navbar unreadable.  This exactly what the docs are doing with the navbar - the custom primary color is dark enough that you need to set the text color to the dark theme color to make it readable.  So I changed the first sample to match that use case.
I added a line to note that the navbar conforms to theme colors if the variant property isn't set.  This seems to be the place where useColorMode is relevant.
The v-b-color-mode directive seems to only take a variable, not an constant.  So it doesn't seem to be a solution to the problem that is being addressed here.  I guess there is a case where one would programmatically change both the variant (not using themes), but that seems like a very corner case.  Let me know if I'm missing something here.

/

Okay, done.  Not sure how I misread the code in the Layout.vue file, but I obviously did.

Sorry about that last one, just plain sloppy on my part.
On the consistency issue - do you have any thoughts on tools to assist or enforce that consistency between the codeblock and the template?  I can think of a number of different things that might improve this, but don't want to jump into anything if you've already got thoughts...

if you've already got thoughts...

I have no suggestions

On the template issue, I imagine that it's not that high a priority because once you get into the workflow of editing the docs it's probably easy enough to get used to doing a copy-paste of one to the other rather than editing them individually (which is what I'll do going forward). I'll think about it a bit more and if I think it's worth pursuing I'll post.  Would that be most appropriate on the discussion section or as an issue?

Okay, I believe I've addressed all of the comments - and hopefully the last commit with this indenting covered what you were asking about and didn't cause new problems :-)  Sorry for the amount of back and forth on this - new process for me and I use Azure Devops rather than Git in my day job, so that caused a few hiccups.  Thanks for your patience.  Let me know if you need anything else from me to get this in.


need b4a example

hi,
I could not convert it into a library for b4a(basic4android). Can you write an example for b4a?

Please show your error logs.
We have provided the JNI.interface and also.Kotlin API.
You should have everything you.need from our side for.your.Android development.


Speed up unit tests in develop

This PR tweaks the logic in Proof_cache to handle ignore the new fields added for custom gates/chunking. This allows for the same unit test speed-up as we get in compatible.
Checklist:

[ ] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

!ci-build-me


ABotSpeaker error

Describe your bug here.
Basically the same error as https://github.com/ShadowMario/FNF-PsychEngine/issues/15414 , i tried to reinstall these libs but it still doesnt work, any ideas how to fix it?
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

fixed


add preset for water=wastewater

A settling or clarifying basin for wastewater. Used 17+k times and documented in the wiki.
Usually found in a wastewater plant, but on the countryside, it may also look like an innocent pond (if there are no signs).
I am not sure if I hit the correct English name here, I did not find a wikipedia article that is only about the basin, not the whole wastewater plant.

I am not sure if I hit the correct English name here, I did not find a wikipedia article that is only about the basin, not the whole wastewater plant.

It sounds good to me - I think most English speakers would understand it.

I did not find a wikipedia article that is only about the basin, not the whole wastewater plant.

btw, I guess it would probably be some kind of landuse=industrial+industrial=?  if people wanted to map a wastewater treatment plant.

It's man_made=wastewater_plant I think
Am 5. Mai 2019 05:22:03 MESZ schrieb Bryan Housel<EMAIL_ADDRESS>

I did not find a wikipedia article that is only about the basin, not
the whole wastewater plant.

btw, I guess it would probably be some kind of
landuse=industrial+industrial=?  if people wanted to map a
wastewater treatment plant.


RCNNLogLoss not decreasing while traing

A strange phenomenon:  I trained the FPN with DCN. The RPNLogLoss was decreasing but the RCNNLogLoss was not decreasing.
Epoch[0] Batch [100]	Speed: 1.59 samples/sec	Train-RPNAcc=0.736193,	RPNLogLoss=0.634564,	RPNL1Loss=0.270521,	Proposal FG Fraction=0.152837,R-CNN FG Accuracy=0.022775,	RCNNAcc=0.726330,	RCNNLogLoss=0.602395,	RCNNL1Loss=0.147218,
[08:20:47] src/operator/././cudnn_algoreg-inl.h:106: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
Epoch[0] Batch [200]	Speed: 1.46 samples/sec	Train-RPNAcc=0.762768,	RPNLogLoss=0.565389,	RPNL1Loss=0.251064,	Proposal FG Fraction=0.170962,R-CNN FG Accuracy=0.010231,	RCNNAcc=0.768321,	RCNNLogLoss=0.548506,	RCNNL1Loss=0.177104,
[08:22:06] src/operator/././cudnn_algoreg-inl.h:106: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
Epoch[0] Batch [300]	Speed: 1.58 samples/sec	Train-RPNAcc=0.790503,	RPNLogLoss=0.496763,	RPNL1Loss=0.241053,	Proposal FG Fraction=0.192451,R-CNN FG Accuracy=0.006069,	RCNNAcc=0.767004,	RCNNLogLoss=0.551358,	RCNNL1Loss=0.216715,
[08:23:19] src/operator/././cudnn_algoreg-inl.h:106: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[08:23:43] src/operator/././cudnn_algoreg-inl.h:106: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
Epoch[0] Batch [400]	Speed: 1.50 samples/sec	Train-RPNAcc=0.829859,	RPNLogLoss=0.410370,	RPNL1Loss=0.231112,	Proposal FG Fraction=0.214325,R-CNN FG Accuracy=0.004091,	RCNNAcc=0.755241,	RCNNLogLoss=0.565407,	RCNNL1Loss=0.260265,
[08:27:11] src/operator/././cudnn_algoreg-inl.h:106: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
Epoch[0] Batch [500]	Speed: 1.60 samples/sec	Train-RPNAcc=0.855274,	RPNLogLoss=0.351961,	RPNL1Loss=0.217395,	Proposal FG Fraction=0.240359,R-CNN FG Accuracy=0.002919,	RCNNAcc=0.735281,	RCNNLogLoss=0.580103,	RCNNL1Loss=0.321848,
[08:27:52] src/operator/././cudnn_algoreg-inl.h:106: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[08:29:33] src/operator/././cudnn_algoreg-inl.h:106: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
Epoch[0] Batch [600]	Speed: 1.56 samples/sec	Train-RPNAcc=0.873362,	RPNLogLoss=0.311010,	RPNL1Loss=0.204541,	Proposal FG Fraction=0.267926,R-CNN FG Accuracy=0.008636,	RCNNAcc=0.711158,	RCNNLogLoss=0.593317,	RCNNL1Loss=0.377678,
[08:31:31] src/operator/././cudnn_algoreg-inl.h:106: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
Epoch[0] Batch [700]	Speed: 1.48 samples/sec	Train-RPNAcc=0.886568,	RPNLogLoss=0.280955,	RPNL1Loss=0.196801,	Proposal FG Fraction=0.287321,R-CNN FG Accuracy=0.040747,	RCNNAcc=0.694276,	RCNNLogLoss=0.600627,	RCNNL1Loss=0.412428,
[08:33:56] src/operator/././cudnn_algoreg-inl.h:106: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
Epoch[0] Batch [800]	Speed: 1.51 samples/sec	Train-RPNAcc=0.897145,	RPNLogLoss=0.257043,	RPNL1Loss=0.189446,	Proposal FG Fraction=0.304609,R-CNN FG Accuracy=0.101394,	RCNNAcc=0.679578,	RCNNLogLoss=0.605049,	RCNNL1Loss=0.446206,

Same problem

Same problem

I tried training on voc2007, and all the loss decreased.

Same problem

I tried training on voc2007 and all the losses decreased, but it doesn't work on my data. I have checked my data many times.

@yohohohoho I just tried deceasing the lr, it seems the loss starts to drop, you should try it


Relay Server Bug - D3 data relay error

There is a bug identified by the newly setup dashboard:

D3 behaves different from other districts.
Need further troubleshooting.
@ian-r-rose
@ZhenyuZhu-Caltrans

Root cause identified:
It was due to the monitoring script not able to handle the irrelevant Kafka consumer topic information.
In D3, the corresponding consumer for uploading the D3 data to AWS has a noise subscription (D3 subscribing to D11), which caused inaccurate monitoring results. It might have introduced by manual operation errors in the past.

And the changes was applied on the Relay Server D2's /etc/check_topic_lag.sh script, adding below filter to excluding that noise configuration. (I wasn't able to delete that entry directly on the Kafka server, so I have to do the removal in the monitoring script. )
... | grep -v "D3.*D11" |

After applying that filter,  the dashboard is recovered.

Key Learnings:

Need to use one consumer group for all topics, rather than each consumer group for one topic, because Kafka seems to have a lot inconvenience on managing multi-consumer-group status.

TODO: (I'll accumulate TODO-s into a new issue called "Relay Server Trust Work Items".

need to centralize the service monitoring scripts
need to use a single consumer group for all the topics in AWS uploader stage.

Thanks for this update @pingpingxiu-DOT-ca-gov !


Update grinder configs with proportional load

Updating the grinder configs for perf & staging to proportionally match the production load.  Did not modify qe01/qe02 as they have different node types.
based on load per production db node.
This is using the load/db node numbers of

200K metrics/minute ingest
7/minute queries

FYI - I didn't calibrate the properities for qe01 & qe02 as their nodes are a different size than staging/perf/prod.

Other than my inquiry about what that nodes attribute means - LGTM.

@drenalin23 - staging & perf01 both had 2 nodes, so i thought that was the number across all envs.  I've updated the PR as per your comments.

+1


Deploying modules to production times out and endpoints start erroring

After this: https://github.com/TBD54566975/ftl/issues/2095
@mistermoe tried hitting an endpoint in MM module, and got the following error:
/home/runner/_work/___/___/___/modules/___/_____.go:56:40-40: unknown reference "____.____", is the type annotated and exported?

Moe points out that the reference was to a verb that has since been removed (probably in the deployed modules before the deployment happened)
Ask me for full error details
Is this just expected because the modules that this module depended on had been updated and removed the verb that this module used, but we failed deployments before we could update this module?

Seems to be fixed by https://github.com/TBD54566975/ftl/pull/2110


Implement jobs icon and fix grey icon color

Jobs icons:

3 integration tests failing on mater, same 3 failing here.
This branch:

Master:

Reviewer: @aldipower

retest this please

retest this please


Xs can not get window screen on win11

Hi bro, thank you for your job, it really helps me.
Recently I changed my pc to win11 system, Xs can run on win11,  but it can not get window screen on win11.

(using DeepL)
Thank you for reporting.
I'm aware that Project Xs does not support Windows 11, but I have no plans to do so.
Currently, I have released a more convenient tool than Project Xs, so please use that. (Apologies that the description is only in Japanese.)
Project eXcelSior : https://github.com/niart120/Project_eXcelSior/releases
Description (Japanese) : https://hackmd.io/@niart/SkCpMpk9n
(Original text)
報告してくださりありがとうございます.
Project XsがWindows11に対応していないのは把握していますが, 対応する予定はありません.
現在, Project Xsよりも利便性の高いツールを公開しているので, 基本的にはそちらを利用してください. (説明が日本語のものしかないのをお詫びします)
Project eXcelSior : https://github.com/niart120/Project_eXcelSior/releases
Description (日本語) : https://hackmd.io/@niart/SkCpMpk9n

邮件已收到

ty for the reply.
I'll try to use XsReader on win11


Run eidos to find definitions from cookbook

Variable definitions from text
Input

Description
The susceptible-infected-recovered (SIR) model in a closed population was proposed by Kermack and McKendrick as a special case of a more general model, and forms the framework of many compartmental models. Susceptible individuals, S, are infected by infected individuals, I, at a per-capita rate βI, and infected individuals recover at a per-capita rate γ to become recovered individuals, R.

Output
Definitions

S: suceptible individuals
I: infected individuals
R: recovered individuals

Properties of things

The susceptible-infected-recovered (SIR) model in a closed population was proposed by Kermack and McKendrick
γ is a per-capita rate
βI is a per-capita rate

Per markdown file is a good scope to avoid collisions.

I've collected all the markdown files from the chapters section of the epirecipe cookbook and ran them through Eidos using the CoreNLPParser. The outputs, automatic annotations, for each corresponding file have been saved as JSON files. Attached is example output. I think the output is actually pretty encouraging.
Also, want to note there are separate tasks involved in recognizing entities, recognizing what portion of text represents the definition of that entity, and recognizing properties of those entities once successfully matched. This is not something we can do with Eidos I don't think within 8 hours.
From what I'm seeing using the Eidos framework, it is loading supervised models when calling different processors.
I'm looking into writing rules based on the original formulation above though.

This looks great! I agree that the output is encouraging. I think the rule Christine had in mind was approximately

"concept", "concept" where the first concept is more than 4 characters and the second concept is less equal one word.

I think that is a good first order approximation of a "variable definition" rule.
From the description of eidos that I got from @adarshp, I understood that you could write rules that take the output of other rules to define higher level extractions.
I don't know how to translate

"concept", "concept" where the first concept is more than 4 characters and the second concept is less equal one word.

into an eidos rule, but it should be within the scope for what eidos can detect.
Also I think it is interesting that the concept and property rules treat "at a per-capita rate $\Beta I$" differently from "at a per-capita rate $\gamma$" in that sentence.

Thanks @jpfairbanks . I agree, it would be nice to be able to extract definitions like we were talking about for filling in human explainable generations.
So the rule-based portions of the system are defined from Odin grammars, and they link to this manual: https://arxiv.org/pdf/1509.07513.pdf I need to read it in detail; I'm not sure yet if Odin is being developed with definition extraction in mind where a phrase is recognized and associated with some other phrase as being a definition of it from the text. It sounds like Odin could support it if we just find the right level of POS to use when defining the rules. Here's an example from the manual
Hi @adarshp, can you point me to what James is referring to? I've looked at a few Odin related papers but I don't see any sort of description of using Odin to extract definitions using rules per se, just events, relationships, etc. Would you be able to comment on whether or not a system like Odin is suited to do that? I would imagine something like term definition would be discussed somewhere among other concepts like events and relationships given the generality of it.

@jpfairbanks The attached image, page 16 of the manual, example 15, is pretty close to what we want. except, we want to specify that some previously recognized entity (e.g. "Concept") to be used as the trigger instead of the lemma. I've been looking over the manual and I read at one point a trigger needs to be token sequence e.g. a verb like "phosphorylation" (which could be defined as an event). If the trigger could be a previously recognized entity, then I think we could write definition extraction rules of different forms.

@jpfairbanks Eidos has finished running on all the Epirecipe markdown documents, saved as JSON structured exports. Do you want to have those committed here or no?

Yes that example is very similar to what we want. The explanation I was referring to was a verbal explanation so I don't have a document for it unfortunately.
If they are small enough, attach them to the issue. Otherwise share them in box.

@jpfairbanks Ah ok got it. I'll share on box. Also it's actually still running but will post what has been annotated so far. For actually looking at examples though, I recommend we use the web app annotation viewer, and we can do that tomorrow for specific examples but putting in the text to the web app.

Hi @scottagt, I'm going to actually redirect your question to @marcovzla, who is the author of ODIN - I haven't personally written ODIN rules, but my sense is that a rule to extract definitions is very much in the scope of ODIN.

Thanks Adarsh.
@marcovzla, we are looking at this textbook and trying to pull out some useful information from the text. One thing that should be really easy to extract is the conceptual definitions of variables that will later be used in equations and code. You can see the example at the top of this thread.
Is there some resource for generally useful rules?

Besides the ODIN manual, there is also a repo with some small examples, the ODIN Wiki and the REACH reader which is a mature project that uses ODIN rules to extract information about biochemical reactions. Perhaps these might be useful to look at?

Adarsh, thanks for this information!

From: Adarsh Pyarelal<EMAIL_ADDRESS>Sent: Tuesday, December 11, 2018 7:36:09 PM
To: jpfairbanks/SemanticModels.jl
Cc: Appling, Scott; Mention
Subject: [BULK] Re: [jpfairbanks/SemanticModels.jl] Run eidos to find definitions from cookbook (#12)
Besides the ODIN manualhttps://arxiv.org/abs/1509.07513, there is also a repo with some small exampleshttps://github.com/clulab/odin-examples, the ODIN Wikihttps://github.com/clulab/processors/wiki/ODIN-(Open-Domain-INformer) and the REACH readerhttps://github.com/clulab/reach which is a mature project that uses ODIN rules to extract information about biochemical reactions. Perhaps these might be useful to look at?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/jpfairbanks/SemanticModels.jl/issues/12#issuecomment-446416917, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYtl0N-POOwG9v7mistFZZx33sKCXnXkks5u4E95gaJpZM4ZN1D2.

It looks like we have a draft of a rule that catches the variable definitions.
-name: simple-np-def
  label: Definition
  priority: 2
  type: token
  pattern: @effect:Concept ("," @cause:Concept)

The next step is to define some more rules to catch more complicated definitions.


Status of FluentAvalonia October 2023

Hello community,
As you've probably noticed not much activity has occurred on this repo over the last month. I recently started a new job as a high school teacher and that has consumed almost all of my time as I settle into that position. I do not intend to abandon this project, however, for the time being, FA will be in a hiatus state, where no development or fixes will be done. Feel free to continue to leave bug reports or feature requests (and if possible help triage other's issues), however, at this time, I'd ask no PRs be submitted until further notice. I look forward to being able to put some time back into this project, and from what I've read, WinUI's source is about to open up (at least a bit) which may add to what FluentAvalonia can offer in the future. Thankfully, Avalonia 11 released this past summer and we're not still in that mess, so FA should be in a relatively stable state.
I know most of you will be understanding, knowing that this is just a hobby project (in fact programming is just a hobby of mine, not my career). Last I checked this repo has well over 600 stars, and I'd like to thank all of you, especially those that contribute (either with issues/bugs or PRs). Don't fret if you don't see much activity, I'm not done here yet - just on a break.

Hey @amwx I'd like to really thank you for the great support you gave us so far and all the things you did so far. Really nice project ❤
While I really hope that someday you will find some free minutes to work on your hobby again, I whish you a good start and all the best for your new job 🍀:pray:

Thank you very much for this project! It is really a nice library which has nice parts that base Avalonia controls lib is missing. Good luck with your new job!

Thank you for such a great project. It's really done wonders for the look of Ryujinx. Do you mind me porting a few of your controls over to Avalonia itself, or Labs? Thanks.

@amwx Awesome work on this project! You really accomplished a lot and its quite valuable work for everyone that has used WinUI in the past. I know open source development is largely a thankless hobby but let me say on behalf of everyone who has used this project it is greatly appreciated! The significant amount of time you spent here is also not taken lightly.
I hope the new teaching role goes great and perhaps even is a bit of fun! I know some of us would enjoy being able to stand up a bit more during the day at least :)

WinUI's source is about to open up (at least a bit) which may add to what FluentAvalonia can offer in the future

I hear the same. Uno Platform already has a version using it.

may add to what FluentAvalonia can offer in the future.

Happy to help port controls over myself where needed.

Finally, if you ever intend to stay away for a long time I do think it will be useful to keep this project going. Long-term maybe some features may need to be cut to keep the scope down; however, the themes and everything are quite valuable. Other projects like this have moved to https://github.com/AvaloniaCommunity (Material.Avalonia as an example). If the project was moved there others (such as myself) could help review and manage things a bit. Just something to consider if you ever want to divest yourself more from this project.
We also might pull in Fluent v2 upstream someday as well.
Again, thanks for all you do! Best of luck in your teaching role!

Do you mind me porting a few of your controls over to Avalonia itself, or Labs? Thanks.

Depending on the controls I'll help argue for merging them upstream :) I really wish FontIcon at least was upstreamed.

How should this project proceed? Ask AvaloniaCommunity to adopt it? It's way too valuable to die.

I am willing to help maintain an Avalonia pr Avalonia Community port of this like Material.Avalonia does. I would however need to narrow the scope to just Fluent v2 themes and no new controls. If we could pull put the common control themes somewhere else; Fluent Avalonia could re-use them here and add new controls. So we could have everything working together like so:

Avalonia
|_ Avalonia.Themes.Fluent2
|_ FluentAvalonia (new controls and their themes)

I'm hoping to push a package update this weekend. I've made a few fixes here and there over the last couple months.
I'm mostly focusing on minor/small fixes and tweaks as part of keeping this project alive. Most stuff that exists right now is pretty stable.
Things I'm not focusing on:

New controls: New controls may be added in the future, but this is a heavy time investment.
.net 8 and AOT support: I am on, and will continue to be on .net 7. Sorry, and this is going to sound mean, but I just don't care about either of these things (particularly AOT).
Feature requests: particularly major things that require heavy time investments.

Also, please note, I am considering moving FA to be .net6+ only (dropping netstandard). I've gotten used to many .net7 things that are quite nice (like double.Max instead of Math.Max) and it annoys me when I drop in to FA and suddenly all these nice improvements I'm now used to from .net6 onward are gone. Yes, I know Avalonia is netstandard/net6 and "works anywhere", but they have enterprise customers and people/businesses coming from WPF with decade old apps. I'm a simple OSS project where I would venture to say 90+% are using the latest version of .net anyway. This is also not an immediate thing, this is a down the road maybe this summer type thing.

If we could pull out the common control themes somewhere else; Fluent Avalonia could re-use them here and add new controls.

Also note, that if Avalonia were to pick up the Fluent v2 styling, FA would still continue to use its own version. Most of the templates have FA specific controls (IconElements) in them and I don't want to change that.

.net 8 and AOT support: I am on, and will continue to be on .net 7. Sorry, and this is going to sound mean, but I just don't care about either of these things (particularly AOT).

I understand you have to limit your time only on what is relevant to you. We'll have to think about what works best at this point for everyone.

Feature requests: particularly major things that require heavy time investments.

Again, totally understandable.

If we could pull out the common control themes somewhere else; Fluent Avalonia could re-use them here and add new controls.

Also note, that if Avalonia were to pick up the Fluent v2 styling, FA would still continue to use its own version. Most of the templates have FA specific controls (IconElements) in them and I don't want to change that.

Well, all the resources could be shared and several of the control themes. You can have just a modification of the upstream control theme with everything but the icons kept in sync (I agree FA icons based on UWP with the added icon sources are much better). Although, we could just pull in the icon stuff in a new base repo as well. I would make an exception on the "no new controls" idea for those since they are heavily ties to the styles.
It seems we have a few options here:

Wait until/if you have more time to devote to FluentAvalonia again. This is still problematic for those that need AOT (mobile, etc.)
Allow other maintainers of this repo to take some of the load off of yourself. I would guess you are not open to this idea.
Fork FluentAvalonia with the hope of merging changes again sometime after new things are proven and you have more time. As it stands every project that needs AOT is going to have to do this individually right now.
Create a new Avalonia.Themes.Fluent2 project some where else using the styles from this repo as a base (will only be done with your permission, regardless of the MIT license. It's just good etiquette and you've done so much great work here I don't want to step on your toes).
Create a brand new Avalonia.Themes.Fluent2 implementation based on upstream WinUI (no code sharing from this repo but probably using some ideas).

The lack of AOT support alone in this repo is going to require choosing an option 2-5 above. It's likely we will hit other roadblocks with bugs and things over time.
@amwx Do you have a suggestion on what the community should do at this point? I'll delay creating another Fluent2 implementation as long as possible but at some point it's going to be necessary. I'll also talk more with upstream Avalonia and see how open they are to it (some resistance there as well).

@robloo Hmm.. I completely forgot mobile/wasm require AOT.
My issue with AOT is this: its the people that saw it, thought it was great, and now get worked up if their app is larger than 5 kb or that the trimmer won't trim because Json, embedded resources, or whatever. Gamers, myself included, have no issue downloading a 100gb game, but its defcon 1 if a .net C# app in 2024 is greater than a few kb. That, plus what I've seen of AOT, it just feels incomplete. The open PR right now I have for .net8 just adds a empty dummy class for the JsonSerializer or something like that. To me, that's a problem with .net itself and needs to be fixed there, and not require my library to have empty classes that serve no other purpose. It's a cool technology - I just think it needs more time before its ~everywhere~. Anyway, I digress.
However, the mobile/wasm thing is important. The good news is at least FA will still work with .net7 and lower. As I said, I haven't moved into .net 8 yet so that's just going to have to be a limitation for the time being. If an issue in net7 or lower appears, we can address that as needed.

Well, all the resources could be shared and several of the control themes. You can have just a modification of the upstream control theme with everything but the icons kept in sync (I agree FA icons based on UWP with the added icon sources are much better). Although, we could just pull in the icon stuff in a new base repo as well. I would make an exception to the "no new controls" idea for those since they are heavily tied to the styles.

I also don't want to bloat the package size to pull in a bunch of control templates just to completely redefine them. The themes itself are stable for all the core controls and should be for mine too. Moving the resources would also require a change to FATheme, as it manages some of the resources outside of Xaml (font, accent colors, and on Win 11 pulling in the correct high contrast colors). Unless WinUI starts Fluent v3, FA is good to go here. The only big thing I already have my sights on, though, is once your BackgroundSizing PR gets merged upstream, I'll need to reverse all my hacks I have now to go back to normal and use the built-in BackgroundSizing.

2. Allow other maintainers of this repo to take some of the load off of yourself. I would guess you are not open to this idea.

I wouldn't be opposed to this. My only real requirements would be to respect my contribution guidelines as a reviewer (which do differ slightly from some modern conventions and Avalonia) - same as if a PR was being submitted - and I'd want the final sign-off on PRs getting merged, at least for bigger things (a typo or other minor fix would be fine). However, the stay on new controls would still remain.
Of course, anyone is welcome to help triage issues or review PRs (you don't need maintainer status for that).
The good news is that I get summers off. So once we get to summer, we can have some fun again :)

It's a cool technology - I just think it needs more time before its ~everywhere~. Anyway, I digress.

Yes, for sure. There is a reason they are only slowly enabling more of it for each .NET release. .NET 7 was CLI-only. .NET 8 is ASP.NET Core apps only, etc. Avalonia just works with it because of the effort back before it became nativeAOT. I suspect there is a way to make it work with JSON code generators or definition files specifying the type needs to be kept. For now though, I wouldn't let perfect be the enemy of good.

I also don't want to bloat the package size to pull in a bunch of control templates just to completely redefine them.

Well, yes, my point is we shouldn't have to re-define themes. If that idea ever came to fruition everything needed to style the in-box Avalonia controls would be pulled out. Then FluentAvalonia would focus only on new controls plus their styles. The two themes could work side-by-side or you would just copy/paste with a script from upstream. Anyway, more below.

The good news is that I get summers off. So once we get to summer, we can have some fun again :)

Ok, I'll hold off any Fluent v2 theming repo until we see how things look this summer. Maybe we all have clear direction on AOT and everything is stabilized. As long as you still accept bug fixes we should be ok. I also suspect Microsoft will make UI changes later this year anyway. Not sure it will be Fluent v3 though.


Consolidate documentation

@PyAbel/developers:
There is a potential for overlapping documentation about the general properties of PyAbel. The information is potentially contained in 3 places:

The readme file displayed at https://github.com/PyAbel/PyAbel
The home page of the wiki: https://github.com/PyAbel/PyAbel/wiki
There should be some general information on the main readthedocs.org page: https://pyabel.readthedocs.org/en/latest/index.html

I have a proposal: basically we just use the README as the main central source of information. It's already the main thing people see on the GitHub page and we can make it appear on the readthedocs page. Also, it has a whole git history so that we can track the changes that are being made to it better than we can with the wiki.
So, we need to do a few things:

Change the readme from .md to .rst to allow compatibility with Sphinx. I did this and it seems to work fine. You can see it here: https://github.com/DanHickstein/PyAbel/tree/doc_improvements  (I also updated it quite a bit, so let me know if there are changed you would like to see.)

Link the readme to the Sphinx docs. I think that this works reasonably well: http://pyabel-dh-fork.readthedocs.org/en/latest/readme_link.html

I don't know quite what to do for the wiki. I think the best it to just have the "Home" page on the wiki link back to the README.rst. The other pages of the wiki are still pretty useful as an easy place to host out notes about the transform methods. Alternatively we could just get rid of the wiki and move towards hosting the technical information about the transform methods in the actual documentation that will appear on readthedocs.

Thoughts?
I can make a PR for this soon, but wanted to get your thoughts first.

By the way, does the @PyAbel/developers tag actually work to tag @rth, @DhrubajyotiDas, @stggh, and @ldes89150?

The developer tag works for me, I received this issue. For my commenting was not sure "@ldes89150" was on the list.

I love that READMR.rst!
Is it possible not display the full url link address?
Dump the wiki. It's a pain to set up (all images must be covertly linked to a pseudo github issue), and maintain.

I got the notification, but I think I'm signed up to receive all updates to PyAbel so I'm not sure if my anecdote is data.
I have no strong  opinions about the wiki, as long as the content is preserved somewhere and easy to find. If the wiki implies redundant effort then we can abandon it and keep a well maintained Readme.

I wasn't planning to dump the whole wiki at this point, just the "Home" page that duplicates the readme. Let's keep the general information about each transform there (for now) on the relevant pages. In the long run, we should likely migrate this information to the /doc directory. I think that it's actually pretty easy to include new .rst documents here and link them using the /doc/index.rst. Each transform could have it's own <method>.rst file, and I think that the figures could easily be included in a sub-directory. So, perhaps that's the better long-term solution.
If anybody feels like making the first attempt at migrating one of the transform documents, please feel free to do so.
@stggh, I can get rid of the full URLs. At first I could not figure out how to do short URLs in .rst format, but I figured it out. It's weird:
`link text <http://www.etc.etc.etc.etc>`_

I think @PyAbel/developers doesn't work on me. However, I subscribe this project, so every issues come into my mail box.
Perhaps, I can add some examples related to cold atoms. :)

@ldes89150: I invited you to the team :)
And yes, an example relating to cold atoms would be excellent! If you have some pretty data that would be fabulous.
Currently the examples are outdated and overlapping and we need to clean them up a bit. Not bad to have lots of examples, but each should try to highlight a different aspect of PyAbel or specific application.

I moved all the information on the transforms from the wiki to docs/transform_methods. Proofreading is still needed, but I'm declaring victory here.


BAR_ Company that filed their AR in the new side, has the AR date with 1 day off,- mismatch with last_AR_filed date and period_end_date

The period_end_dt is currently set based on the annualReportDate provided in the filing body, which originates from the client. Occasionally, mismatches occur because the client specifies an annualReportDate that differs from the company's recognition date.
For example:
Recognition Date (recognition_dts): 2020-10-08
Period End Date (period_end_dt): 2024-10-07
Here, the period_end_dt was derived from the annualReportDate submitted by the client. The relevant code logic reflects this approach:

recognition dts is 20201008 and period_end_dt is 20241007, period_end_dt was set by annul_report_date:
We need to decide whether to continue using the annualReportDate provided by the client to set period_end_dt or to align it with the recognition date for consistency. This decision will impact how mismatches are handled going forward.

Testing completed and working as expected. All dates are mapping correctly.


Appstudio update test-component-pac-akxy

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-akxy-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
25 seconds
init

✅ Succeeded
20 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
38 seconds
inspect-image

✅ Succeeded
44 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
34 seconds
sbom-json-check

✅ Succeeded
11 seconds
label-check

✅ Succeeded
10 seconds
optional-label-check

✅ Succeeded
8 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-akxy-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
27 seconds
build-container

✅ Succeeded
18 seconds
clair-scan

✅ Succeeded
15 seconds
inspect-image

✅ Succeeded
14 seconds
deprecated-base-image-check

✅ Succeeded
53 seconds
clamav-scan

✅ Succeeded
12 seconds
sbom-json-check

✅ Succeeded
16 seconds
optional-label-check

✅ Succeeded
16 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-akxy-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
27 seconds
build-container

✅ Succeeded
53 seconds
clamav-scan

✅ Succeeded
15 seconds
inspect-image

✅ Succeeded
14 seconds
deprecated-base-image-check

✅ Succeeded
18 seconds
clair-scan

✅ Succeeded
12 seconds
sbom-json-check

✅ Succeeded
16 seconds
optional-label-check

✅ Succeeded
16 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary


[Odnoklassniki] Improve embedded players extraction

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.
Fixed URL extraction from embedded players. Sample links:
https://ok.ru/video/3568183087575 -> vk
http://ok.ru/video/1484130554189 -> coub
https://m.ok.ru/video/5377168585 -> pladform -> rutube (require fixes #2550)
https://ok.ru/video/5357900818 -> pladform -> rutube (require fixes  #2550)
http://ok.ru/video/2564475326911 -> 1tv (not fully working, but handle redirect. Need fix 1tv extractor)
https://ok.ru/video/2503545992 -> ivi (not fully working, but handle redirect. Need fix ivi extractor)

Please follow the guide below
* You will be asked some questions, please read them **carefully** and answer honestly

* Put an `x` into all the boxes [ ] relevant to your _pull request_ (like that [x])

* Use _Preview_ tab to see how your _pull request_ will actually look like

Before submitting a pull request make sure you have:
* [x]  At least skimmed through [contributing guidelines](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#developer-instructions) including [yt-dlp coding conventions](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#yt-dlp-coding-conventions)

* [x]  [Searched](https://github.com/yt-dlp/yt-dlp/search?q=is%3Apr&type=Issues) the bugtracker for similar pull requests

* [x]  Checked the code with [flake8](https://pypi.python.org/pypi/flake8)

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:
* [x]  I am the original author of this code and I am willing to release it under [Unlicense](http://unlicense.org/)

* [ ]  I am not the original author of this code but it is in public domain or released under [Unlicense](http://unlicense.org/) (provide reliable evidence)

What is the purpose of your pull request?
* [x]  Bug fix

* [x]  Improvement

* [ ]  New extractor

* [ ]  New feature

Description of your pull request and other information
Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.
Fixed URL extraction from embedded players. Sample links: https://ok.ru/video/3568183087575 -> vk http://ok.ru/video/1484130554189 -> coub https://m.ok.ru/video/5377168585 -> pladform -> rutube (require fixes #2550) https://ok.ru/video/5357900818 -> pladform -> rutube (require fixes #2550)
http://ok.ru/video/2564475326911 -> 1tv (not fully working, but handle redirect. Need fix 1tv extractor) https://ok.ru/video/2503545992 -> ivi (not fully working, but handle redirect. Need fix ivi extractor)

can u send u contact? or text me to tg @NeiroPassenger

?


Implement merging for Lora layers

In preparation for full LoRA support via merged layers to not degrade performance.

QLoraLinear may be more difficult because we need to modify the weights.


Components needed for building for Raspbian 9

Don't merge this yet, need to check about the GPL license in the toolchain file just to be safe.

Ok got the go ahead to merge this


Cookie middleware, can it support user-defined configuration properties?

Description of the feature
Currently with CookieJar, each new Cookie stored requires manual configuration of security-related properties, which is flexible, but there is a lot of duplication of work being done.
For a site, usually, the cookie security policy is kept consistent, and there are fewer scenarios where each key is configured individually.
And currently poem, cookie middleware is automatically registered after the feature is turned on, so that the user lacks some control over the initialization of the attributes.
I suggest: Cookie middleware, the user supports custom configuration at the start of the framework and can override the default loading of the cookie middleware.
Subsequent Cookie default to go configured security properties, the use of light and elegant.

I need to consider the design of the API, it is not enough to just add these methods to CookieJarManager.

I need to consider the design of the API, it is not enough to just add these methods to CookieJarManager.

Thanks, because this is a requirement that requires a lot of internal structure adjustment, I will first use the existing way to implement the function.

Added CookieSession middleware, released in v1.0.5


Possible minor inconsistency in dimensions?

I was in the process of writing some unit tests for the multi-dim usage and noticed a possible minor inconsistency. Both KalmanFilter.predict and KalmanFilter.update require the initial means to take a certain shape. The latter preserves this shape in the output results object. However, the .predict method transposes the last two dimensions. Thus the shape of the means going in isn't the same as going out. If this output is merely intended as reporting that doesn't matter, but as you can see from this test script there might be a slight inconsistency here. However, perhaps I misunderstand the intent or am abusing the usage somehow.
LMK if you want this test script in a notebook or PR into simdkalman.

Thanks! I'll take a closer look later this week (and review #18 as well)

This actually might be just a confusion between predict & predict_next, see https://github.com/oseiskar/simdkalman/pull/18#discussion_r683613205

Works as intended with predict_next, even though the terminology is indeed confusing here. See

This test: https://github.com/oseiskar/simdkalman/commit/8c9364d0a501e15493d60a0fc50ae05489063ba8
and: https://github.com/oseiskar/simdkalman/blob/8c9364d0a501e15493d60a0fc50ae05489063ba8/examples/multiple_systems_single_step.py#L48-L58


Dev Week #3

Some ideas:

Add a feature for users to store a session of bookmarks something like "Journeys". I might have a session where I research some stuff, then I wanna store it the entire thing as Journey for future purpose.


Monitoring v1 is not available in a downstream cluster on Tenant Rancher server

Rancher Server Setup

Rancher version: 2.5.12-rc2
Installation option (Docker install/Helm Chart): Helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): k3s - v1.20.13+k3s1

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: 1.20 Custom cluster downstream on Tenant Rancher

Describe the bug
Monitoring v1 is not available in a downstream cluster on Tenant Rancher server
To Reproduce

Deploy k3s HA cluster - 3 server, 3 worker nodes using v1.20.13+k3s1 version
Deploy Rancher on this setup - 2.5.12-rc1
Import a k3s HA cluster in rancher with v1.20.13+k3s1 version
Deploy Rancher 2.5.12-rc1 on this
Deploy a downstream custom cluster on the Tenant rancher
Enable monitoring v1

Result

Errors seen when retrieving the graphs in cluster dashboard

Failed to obtain metrics. The metrics service may not be available.
undefined

Could be the same as this issue - https://github.com/rancher/rancher/issues/35760

Test Environment:
Rancher version: v2.5-edf83d5f6d2041217f9e543743d69246fe18afa7-head (both host and tenant)
Rancher cluster type: k3s HA (3 and 3)
k8s version: v1.20.13+k3s1
Downstream cluster type: ec2 node driver cluster and custom cluster
Downstream K8s version: 1.20

Testing:

On the tenant cluster: enable v1 monitoring on all 3 clusters (local, node driver, custom)
Wait for monitoring to be enabled and check the following

go to a cluster main page

you see two-layer gadgets on the CPU and memory metrics
there should be the following 4 sections of metrics:

cluster metrics
etcd metrics (not available for the local since there is no etcd)
Kubernetes components metrics
rancher logging metrics. (it does not contain any metrics since logging is not enabled)

go to the System project (on each cluster) > Apps > you should see 2 apps deployed and running:

cluster-monitoring
monitoring-operator

go to Node (on each cluster) > click on the node

you should see metrics for the node and Node metrics

go to Workloads (on each cluster) > click on a workload

you should see metrics for the Workload Metrics

from Workloads click on any pod

you should see metrics for the Pod Metrics

from the Pod click on the container

you should see metrics for the Container Metrics

go to the System project (on each cluster) > Apps > click on cluster-monitoring

you will be redirected to grafana dashboard


Fix #2 (Py3k compat) + missing import of errno

I'm not entirely certain why, but either I was never sent a notification about this PR, or it got filtered. I hope to take a look at it this weekend.

Excellent, thanks @mkomitee! Let me know if you need any further changes before merging. Meanwhile I'll take a look at addressing #13 next chance I get.

Okay, there's only thing that I think we ought to do here. When I run the tests under python3, it indicates that logging.Logger.warn is deprecated, so to be complete, can you change all use of warn to warning?

@mkomitee Done in the latest revision.
(Also adhered to Black's 88-char max line length to avoid those two lines having to wrap. Rationale: https://github.com/ambv/black#line-length)

I'd rather stick with 80 columns, but don't feel too strongly about that that I'd reject the PR.
I also see now that we're incorrectly using % to encode strings being passed to logging methods, which isn't necessary as the logging library will do that for us.
If you're feeling motivated and want to fix that (since you're now modifying those very lines), that would be great. Otherwise I think we can accept this as is. Let me know if you're going to do so.
Based on some other out of band communication, it's my understanding that you have some more patches in-bound, so I'll hold off on cutting a release until we work through them as well.

@mkomitee Can this be merged now?


Mongoid6- rails5 compatibility

Getting an error:
mongoid-rspec (= 3.0.0) was resolved to 3.0.0, which depends on
mongoid (~> 5.0)

@shipdcare feel free to use my fork of gem. =D https://github.com/phinfonet/mongoid-rspec

Closing issue, related to https://github.com/mongoid-rspec/mongoid-rspec/issues/169


Fix: Add support for revalidateTag (WIP)

Right now, revalidateTag and revalidatePath from next/cache is not working. This PR aims to fix this.
It is still a work in progress
How it works

We add a dynamoDB table where all the tags are stored with their associated path and their last revalidated time
Tags are written at the end of the set method of our incremental cache

Requirements

A dynamoDB table with the correct permissions for server-function lambda
A GSI named revalidate
A CACHE_DYNAMO_TABLE env variable
If you're using sst for the time being you could do

const testTable = new Table(stack, "testCacheTable2", {
  fields: {
    path: "string",
    tag: "string",
    revalidatedAt: "number",
  },
  primaryIndex: { partitionKey: "tag", sortKey: "path" },
  globalIndexes: {
    revalidate: { partitionKey: "path", sortKey: "revalidatedAt" },
  }
});
const site = new NextjsSite(stack, "site", {
  buildCommand:
    "/path/to/open-next/packages/open-next/dist/index.js build",
  waitForInvalidation: false,
  environment: {
    CACHE_DYNAMO_TABLE: testTable.tableName,
  }
});
site.attachPermissions([testTable]);

Caveats

It seems that right now revalidateTag is not revalidating immediately but just setting the associated page to STALE. That's the way it is done on vanilla next.js, might be different on vercel
On write we override the revalidatedAt with Date.now() for every tags
The fetch cache is not working right now because our solution for ISR is using on demand revalidate under the hood. Right now fetch cache is disabled for on demand revalidate.
All these caveats might change, and some may appears, as it relies on internal mechanism of next.js and on api that are still unstable

Potential Improvements

We could move some part that are reliant on S3 cache right now to dynamoDB (This should be faster)

Things to consider: if the NextjsSite is deployed on the edge, then we'd probably want to replicate the DDB to the same edge to reduce the latency. We'd have to setup latency records to allow the Lambdas to hit the closest DDB (this is pretty easy to setup).

Here's a gist of how to setup the closest DDB lookup: https://gist.github.com/khuezy/ce2a2fd6e6b3e6d435d2b45f00201d28


fixed dependencies

The data migration failed, so this PR fixes it (wrong dependency).

sorry @ceryslewis when I went to deploy the Master -> Live branch you merged earlier, there was a migration error (which this PR fixes)


build with OpenMP

I was hoping to get OpenMP working with the win64 conda-forge mumps module:
mumps                     5.1.2             h8933c1f_1001    conda-forge
The verbose output for the mumps module shows the build is without OMP. If I manually build with compiler openmp flags the output shows #OMP =      8. The openmp build runs 2-3x faster for larger problems on my 4-core laptop, so it is definitely worthwhile.
I am working on a PR to enable OpenMP but find the mumps-feedstock is using NMake Makefiles and flang for win64, rather than MinGW Makefiles and gfortran. (Not sure why I don't get the flang build when I use conda install mumps?)
I can build the module from the feedstock using flang, but flang gives command failed due to signal if I add the -mp openmp compile flag. I have not found any relevant LLVM/MSVC openmp support info/limitiations, but clang works fine for an C openmp code.
The linux build with openmp is fine.
Should I do a PR for a MinGW/gfortran build, or any suggestions on getting OpenMP working with flang?

If you can get OpenMP with the current windows build setup that is fine. I don't know about flang + OpenMP, try searching if any other feedstocks use OpenMP on windows with flang.


add new Hive reader

Description
add a new Hive reader.
Fixes # (issue)
Type of Change
Please delete options that are not relevant.

[x] New Loader/Tool
[ ] Bug fix / Smaller change
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have added a library.json file if a new loader/tool was added
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

make format; make lint have been done.

need to run make format; make lint for any changes . Unn, this step missing.


added favicon

Codecov Report

Merging #15 (b05d5f1) into main (7b21773) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage   99.24%   99.24%
=======================================
  Files           9        9
  Lines         133      133
=======================================
  Hits          132      132
  Misses          1        1


Is session recording in the roadmap ?

I would like to know if this feature will be available one day (and it's just a matter of time, and no hurry take your time :)
or if there's technical limitation preventing from ever happening (in which case I may check for other libraries)

Mentioned here as well https://github.com/PostHog/posthog-js-lite/issues/19
Currently this isn't supported and isn't an immediate priority (although definitely something we want to do!)