chore: release main

:robot: I have created a release beep boop
block-brokers: 2.0.0
2.0.0 (2024-01-24)
⚠ BREAKING CHANGES

the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)
expose configured dag walkers and hashers on helia interface (#381) (843fba4), closes #375

Dependencies

The following workspace dependencies were updated

dependencies

@helia/interface bumped from ^3.0.1 to ^4.0.0

car: 3.0.0
3.0.0 (2024-01-24)
⚠ BREAKING CHANGES

the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)
expose configured dag walkers and hashers on helia interface (#381) (843fba4), closes #375

Dependencies

The following workspace dependencies were updated

dependencies

@helia/interface bumped from ^3.0.1 to ^4.0.0

devDependencies

@helia/unixfs bumped from ^2.0.1 to ^3.0.0

dag-cbor: 3.0.0
3.0.0 (2024-01-24)
⚠ BREAKING CHANGES

the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)

Dependencies

The following workspace dependencies were updated

dependencies

@helia/interface bumped from ^3.0.1 to ^4.0.0

dag-json: 3.0.0
3.0.0 (2024-01-24)
⚠ BREAKING CHANGES

the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)

Dependencies

The following workspace dependencies were updated

dependencies

@helia/interface bumped from ^3.0.1 to ^4.0.0

http: 1.0.0
1.0.0 (2024-01-24)
⚠ BREAKING CHANGES

the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)

Dependencies

The following workspace dependencies were updated

dependencies

@helia/block-brokers bumped from ^1.0.0 to ^2.0.0
@helia/interface bumped from ^3.0.1 to ^4.0.0
@helia/routers bumped from ^0.0.0 to ^1.0.0
@helia/utils bumped from ^0.0.0 to ^0.0.1

interface: 4.0.0
4.0.0 (2024-01-24)
⚠ BREAKING CHANGES

the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)
expose configured dag walkers and hashers on helia interface (#381) (843fba4), closes #375

Bug Fixes

update ipns module to v9 and fix double verification of records (#396) (f2853f8)

interop: 4.0.0
4.0.0 (2024-01-24)
⚠ BREAKING CHANGES

remove gossipsub from default libp2p services (#401)
helia.routing is the default routing used, the libp2p routing has been removed as it is redundant
the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)
export binary from @helia/interop (#384) (3477b27)
use helia router for IPNS put/get (#387) (ce74026)

Bug Fixes

include aegir config in interop and run from install dir (#389) (a2229bd)
remove gossipsub from default libp2p services (#401) (99c94f4)
update ipns module to v9 and fix double verification of records (#396) (f2853f8)

Dependencies

bump kubo from 0.25.0 to 0.26.0 (#400) (a9c55f0)
The following workspace dependencies were updated

dependencies

@helia/block-brokers bumped from ^1.0.0 to ^2.0.0
@helia/car bumped from ^2.0.1 to ^3.0.0
@helia/dag-cbor bumped from ^2.0.1 to ^3.0.0
@helia/dag-json bumped from ^2.0.1 to ^3.0.0
@helia/http bumped from ^0.9.0 to ^1.0.0
@helia/interface bumped from ^3.0.1 to ^4.0.0
@helia/ipns bumped from ^4.0.0 to ^5.0.0
@helia/json bumped from ^2.0.1 to ^3.0.0
@helia/mfs bumped from ^2.0.1 to ^3.0.0
@helia/routers bumped from ^0.0.0 to ^1.0.0
@helia/strings bumped from ^2.0.1 to ^3.0.0
@helia/unixfs bumped from ^2.0.1 to ^3.0.0
helia bumped from ^3.0.1 to ^4.0.0

ipns: 5.0.0
5.0.0 (2024-01-24)
⚠ BREAKING CHANGES

remove gossipsub from default libp2p services (#401)
helia.routing is the default routing used, the libp2p routing has been removed as it is redundant
the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)
use helia router for IPNS put/get (#387) (ce74026)

Bug Fixes

remove gossipsub from default libp2p services (#401) (99c94f4)
update ipns module to v9 and fix double verification of records (#396) (f2853f8)

Dependencies

The following workspace dependencies were updated

dependencies

@helia/interface bumped from ^3.0.1 to ^4.0.0

json: 3.0.0
3.0.0 (2024-01-24)
⚠ BREAKING CHANGES

the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)

Dependencies

The following workspace dependencies were updated

dependencies

@helia/interface bumped from ^3.0.1 to ^4.0.0

mfs: 3.0.0
3.0.0 (2024-01-24)
⚠ BREAKING CHANGES

the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)

Dependencies

The following workspace dependencies were updated

dependencies

@helia/interface bumped from ^3.0.1 to ^4.0.0
@helia/unixfs bumped from ^2.0.1 to ^3.0.0

routers: 1.0.0
1.0.0 (2024-01-24)
⚠ BREAKING CHANGES

the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)

Bug Fixes

update ipns module to v9 and fix double verification of records (#396) (f2853f8)

Dependencies

The following workspace dependencies were updated

dependencies

@helia/interface bumped from ^3.0.1 to ^4.0.0

strings: 3.0.0
3.0.0 (2024-01-24)
⚠ BREAKING CHANGES

the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)

Dependencies

The following workspace dependencies were updated

dependencies

@helia/interface bumped from ^3.0.1 to ^4.0.0

unixfs: 3.0.0
3.0.0 (2024-01-24)
⚠ BREAKING CHANGES

the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)

Dependencies

The following workspace dependencies were updated

dependencies

@helia/interface bumped from ^3.0.1 to ^4.0.0

@helia/utils: 0.0.1
Dependencies

The following workspace dependencies were updated

dependencies

@helia/interface bumped from ^3.0.1 to ^4.0.0

helia: 4.0.0
4.0.0 (2024-01-24)
⚠ BREAKING CHANGES

remove gossipsub from default libp2p services (#401)
the libp2p property has been removed from the Helia interface in @helia/interface - it is still present on the return type of createHelia from the helia module

Features

add @helia/http to monorepo (#372) (76220cd)

Bug Fixes

add a test for reading the peer id from the datastore (#397) (4836d52)
ignore libp2p start param in helia factory (#382) (c8d2fac), closes #344
remove gossipsub from default libp2p services (#401) (99c94f4)
update ipns module to v9 and fix double verification of records (#396) (f2853f8)

Dependencies

bump @chainsafe/libp2p-noise from 14.1.0 to 15.0.0 (#393) (4943c5b)
The following workspace dependencies were updated

dependencies

@helia/block-brokers bumped from ^1.0.0 to ^2.0.0
@helia/interface bumped from ^3.0.1 to ^4.0.0
@helia/routers bumped from ^0.0.0 to ^1.0.0
@helia/utils bumped from ^0.0.0 to ^0.0.1

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ipfs/helia/releases/tag/block-brokers-v2.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/car-v3.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/dag-cbor-v3.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/dag-json-v3.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/helia-v4.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/http-v1.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/interface-v4.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/interop-v4.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/ipns-v5.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/json-v3.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/mfs-v3.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/routers-v1.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/strings-v3.0.0 :sunflower:

:robot: Release is at https://github.com/ipfs/helia/releases/tag/utils-v0.0.1 :sunflower:


docs(config) : Add moduleAsset to stats

https://github.com/webpack/webpack/blob/d00e65529a4c5a4e91843f2d4178c66eff3784ae/declarations/WebpackOptions.d.ts#L1818

[x] Read and sign the [CLA][1]. PRs that haven't signed it won't be accepted.
[x] Make sure your PR complies with the [writer's guide][2].
[x] Review the diff carefully as sometimes this can reveal issues.
[x] Do not abandon your Pull Request: [Stale Pull Requests][3].

Thanks!


Kiwix.KiwixJS version <IP_ADDRESS>

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@yao-msft This updated HTML/JS UWP package is running into the same mysterious validation error as we had last month with the three packages Kiwix.KiwixJS, Kiwix.Wikivoyage and Kiwix.WikiMed. I have tested it locally, and it installs fine (see screenshot below) and certificate is valid.
Do I need to request a manual validation each time I upload a new package? This would be three times a month at least. I thought the validation waiver would carry over. Is there any other solution? Many thanks.

@denelon , @AmelBawa-msft This UWP HTML/JS appxbundle is running into the same validation issue as happened last month, despite the fact that you added a waiver last month. As a reminder, validating this type of msix/appxbundle app used to work fine with the Azure validation scripts, but it stopped validating just over a month ago despite the fact that winget has no problem installing the bundle, and the certificate checks out fine.
Is there any other solution than my having to request a manual validation every time I update these apps? There are three: Kiwix.KiwixJS, Kiwix.WikiMed, Kiwix.Wikivoyage. I update each one on a monthly cycle.

@wingetbot waivers Add Validation-Installation-Error

@Jaifroid, I've waived this error again. I do expect this issue to be fixed in the near future as we are planning to update the validation to start handling portable packages soon. Once that update happens, I believe this package should no longer have issues. I'll keep an eye out if this problem occurs again.

@ryfu-msft Thank you very much. It's not supposed to be a portable package, it's fully installable as a UWP app, and goes in the UWP hidden installation folder when installed.
Be that as it may, the issue we're facing now is that the current versions of winget (latest 1.3 stable and the 1.4 preview) are both unable to deal with a 1.3GB installation file. I suspect a timeout because it never gets past the hash check and errors out with
An unexpected error occurred while executing the command:
0x80072eff : unknown error

This is nothing to do with package type, it's due to the size of the package. A timeout seems to abandon the hash check before the package can be downloaded. It's the only explanation I can come up with. See https://github.com/microsoft/winget-cli/issues/1987 .


Fix typos

Noticed that there were some typos in the definitions of --plain-fg and .padding-inline-end.

Ugh, I didn't mean to include the ARIA feed role in this PR. Closing this so I can get it on the right branch.


Added setTimeout function

Ability to set timeout

I don't think it makes sense to add this, since it's not part of the interface.

This timeout should instead be set at construction imo.

Not sure why this was closed and not added. It is part of the client and @m0byd1ck PR is easy to implement and would have saved me lots of time.
However, for those looking for example of what @GrahamCampbell is talking about instead of this:
$adapter = new BuzzAdapter('DIGITAL_OCEAN_API_KEY');
$digitalocean = new DigitalOceanV2($adapter);
$digitalocean_sizes = $digitalocean->size()->getAll();

You would do this:
use Buzz\Browser;
use Buzz\Client\Curl;
use Buzz\Client\FileGetContents;
...
$browser = new Browser(function_exists('curl_exec') ? new Curl() : new FileGetContents());
$browser->getClient()->setTimeout(15);
$adapter = new BuzzAdapter('DIGITAL_OCEAN_API_KEY', $browser);
$digitalocean = new DigitalOceanV2($adapter);
$digitalocean_sizes = $digitalocean->size()->getAll();


feat(MAP): support for incoming payment expiry webhook

Changes proposed in this pull request

Adding incoming_payment.expired webhook support for the mock account provider. As per webhook docs, incoming payment expiry should be treated the same as completion on incoming payment (credit the account for the amount, call WithdrawLiquidity mutation)

Context

Fixes #659 :
Took this issue on after a discussion with @wilsonianb in another: one

Checklist

[x] Related issues linked using fixes #number
[ ] Tests added/updated
[x] Documentation added
[x] Make sure that all checks pass

@wilsonianb thanks:+1:
For testing this, I ended up:

Creating incoming payment, creating quote, creating outgoing payment (& validate it's COMPLETED).
In the DB, marked incoming payment as EXPIRED and moved the processAt field to be in the past.

Is there a better way to do so?


Large Index Support for Slice

Description
Ops Supported: Slice
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-label-bot add [pr-work-in-progress]

@mxnet-label-bot add [pr-awaiting-review]

@ChaiBapchya  mx_uint is used for maintaining consistency with language bindings. For example python uses mx_int64 = ctype.c_int64 and its counter part in C++ is typedef int64_t mx_int64 this way we can ensure both signature have same data types. one exception to it is int which on python side is mx_int but on C++ its just int

@apeforest can you review

Please update your test_large_vector.py using single dimension. Also, please add a test to flatten large array in test_large_array.py. Thanks!

@apeforest : MXNet NDArray flatten still flattens to 2d array instead of 1D array. Can you suggest which operator to use in order to flatten to 1D ?

How about using repeat operator for converting any dimension array to 1D?
>> mx.nd.repeat(mx.nd.array([[[1,2],[3,4]]]),repeats=1)

[1. 2. 3. 4.]
<NDArray 4 @cpu(0)>

From the test logs:
test_random.test_shuffle ...
ok (1811.4455s)

@mxnet-label-bot add[pr-awaiting-merge]


[BUG] Hive partition pruning failed for a date-type partition that has a value with an invalid date format

Steps to reproduce the behavior (Required)

CREATE HIVE TABLE & Add a invalid date format partition

create table test_partition_prune(a int) partitioned by (dt string comment 'yyyy-mm-dd');
 alter table test_partition_prune add partition(dt='xxxxx');

Query this table by starrocks using hive catalog

mysql> explain select * from hive_catalog.tmp.test_partition_prune where dt = to_date(days_add(now(),-1));
ERROR 1064 (HY000): can not cast literal value xxxxx to target type datetime

Expected behavior (Required)
execute success
Real behavior (Required)
execute failed
StarRocks version (Required)

3.1.8
3.2.3

Why not just delete the invalid partition? Is it useful?

I've tested trino, it will also report a cast fail.

I've tested trino, it will report a cast fail at first because dt is a string col and the data type in where condition is date. and I add a cast to dt, also report a cast fail because there is a xxxxx.

The 'yyyy-mm' format value also triggers this error. Does it also fail in Trino? reproduce steps:
alter table test_partition_prune add partition(dt='2024-01');
mysql> explain select * from hive_catalog.tmp.test_partition_prune where dt = to_date(days_add(now(),-1));
ERROR 1064 (HY000): can not cast literal value 2024-01 to target type datetime

Why not just delete the invalid partition? Is it useful?

Because starrocks 2.5 can execute successfully while move to higher version execute failed that let user feel confused.

The fact is that SR2.5 does not make use of the predicate, therefore the SQL is executed successfully.

In 3.1+, the predicate is used to prune partitions. However, you have a partition of type string xxxx that is unable to cast to type date. Hence, the SQL fails.

I've tested trino, it will report a cast fail at first because dt is a string col and the data type in where condition is date. and I add a cast to dt, also report a cast fail because there is a xxxxx.

The 'yyyy-mm' format value also triggers this error. Does it also fail in Trino? reproduce steps:
alter table test_partition_prune add partition(dt='2024-01');
mysql> explain select * from hive_catalog.tmp.test_partition_prune where dt = to_date(days_add(now(),-1));
ERROR 1064 (HY000): can not cast literal value 2024-01 to target type datetime

yyyy-mm is not a valid date format either, can not be cast to date directly.


added nsq support

I needed NSQ for some testing, so I added support for nsqd and nsqlookupd. NSQAdmin support could easily be implemented, didn't see much value in a GUI tool in this project though.

looking good, thanks!


[parser] Parser segfaults without arguments on linux

Issue description
The new parser (parser/raylib_parser.c) segfaults on Linux when the executable is called without any arguments.
This is due to argv[1]=0x0, which is then passed to IsTextEqual unchecked
Environment
I'm running openSUSE Tumbleweed on x86_64 and compiling with gcc 11
Issue Screenshot
Program received signal SIGSEGV, Segmentation fault.
0x00000000004038f8 in IsTextEqual (text1=0x0, text2=0x404008 "--help", count=6) at raylib_parser.c:738
738             if (text1[i] != text2[i])
(gdb) bt
#0  0x00000000004038f8 in IsTextEqual (text1=0x0, text2=0x404008 "--help", count=6) at raylib_parser.c:738
#1  0x0000000000401231 in main (argc=1, argv=0x7fffffffdb78) at raylib_parser.c:118

Maybe a stage could be added to the CI to protect against regressions like this in the future


Active Identifier Unhandled Error thrown in read handler

I'm receiving the below error fairly frequently within the logs, and after awhile it the xbox plugin stops working until a restart. The below error seems to correlate to whenever I open home app, or run a random home shortcut and polling of the xbox occurs even when I'm not interacting with it.
Below is my config. Which is simple in nature.
"devices": [
    {
        "name": "Living Room Xbox Series X",
        "host": "<IP_ADDRESS>",
        "xboxLiveId": "REMOVEDID",
        "webApiControl": true,
        "getInputsFromDevice": true,
        "filterGames": true,
        "filterApps": true,
        "filterSystemApps": true,
        "filterDlc": true,
        "inputsDisplayOrder": 1,
        "sensorPower": false,
        "sensorInput": false,
        "sensorScreenSaver": false,
        "webApiPowerOnOff": true,
        "webApiRcControl": false,
        "webApiVolumeControl": false,
        "webApiToken": "REMOVEDTOKEN",
        "webApiClientId": "REMOVEDCLIENTID",
        "enableDebugMode": false,
        "disableLogInfo": false,
        "disableLogDeviceInfo": false,
        "infoButtonCommand": "nexus",
        "volumeControl": -1,
        "enableRestFul": false,
        "restFulDebug": false,
        "enableMqtt": false,
        "mqttDebug": false,
        "mqttAuth": false
    }
],
"_bridge": {
    "username": "0E:D7:D1:31:C2:57",
    "port": 42538
},
"platform": "XboxTv"

}
Log snippet:
01/01/2024, 14:42:43] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, set Power: ON
[01/01/2024, 14:42:53] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Connected.
[01/01/2024, 14:42:53] [homebridge-xbox-tv] -------- Living Room Xbox Series X --------'
[01/01/2024, 14:42:53] [homebridge-xbox-tv] Manufacturer: Microsoft
[01/01/2024, 14:42:53] [homebridge-xbox-tv] Model: Xbox Series X
[01/01/2024, 14:42:53] [homebridge-xbox-tv] Serialnr: REMOVED
[01/01/2024, 14:42:53] [homebridge-xbox-tv] Firmware: 10.0.25398
[01/01/2024, 14:42:53] [homebridge-xbox-tv] Locale: en-US
[01/01/2024, 14:42:53] [homebridge-xbox-tv] ----------------------------------
[01/01/2024, 14:42:59] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, set Power: OFF
[01/01/2024, 14:43:16] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Disconnected.
[01/01/2024, 14:44:16] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Power: OFF
[01/01/2024, 14:44:17] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 14:44:49] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Power: OFF
[01/01/2024, 14:44:49] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Current Media: STOP
[01/01/2024, 14:44:49] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Target Media: STOP
[01/01/2024, 14:44:49] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Mute: ON
[01/01/2024, 14:44:49] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Volume: 0
[01/01/2024, 14:44:49] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 14:44:49] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 14:45:22] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 14:45:27] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 14:45:43] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 14:52:24] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Power: OFF
[01/01/2024, 14:52:24] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 14:52:30] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 14:52:32] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Power: OFF
[01/01/2024, 14:52:32] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 14:52:34] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Power: OFF
[01/01/2024, 14:52:35] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 14:53:31] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Power: OFF
[01/01/2024, 14:53:31] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 16:01:52] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Power: OFF
[01/01/2024, 16:01:52] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 16:12:38] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Power: OFF
[01/01/2024, 16:12:39] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 16:13:04] [homebridge-xbox-tv] Device: <IP_ADDRESS> Living Room Xbox Series X, Power: OFF
[01/01/2024, 16:13:04] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 16:13:11] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.
[01/01/2024, 16:13:12] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId'). See https://homebridge.io/w/JtMGR for more info.

I am also getting this error, though I haven't managed to capture it when debug is enabled yet:

[01/01/2024, 12:11:13] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId')

Have now been able to capture the error with debug logging, hopefully the attached will help you @grzegorz914
homebridge.log.txt

this should be fixed with latest update 2.12.3

Thanks for your fantastic effort!

Thanks @grzegorz914 I have updated to 2.12.4 and will let you know if I see the error again.

 See https://homebridge.io/w/JtMGR for more info.
[02/01/2024, 17:21:30] [XboxTv] Device: <IP_ADDRESS> Xbox Series X, Power: OFF
[02/01/2024, 17:21:30] [XboxTv] Device: <IP_ADDRESS> Xbox Series X, Current Media: STOP
[02/01/2024, 17:21:30] [XboxTv] Device: <IP_ADDRESS> Xbox Series X, Target Media: STOP
[02/01/2024, 17:21:30] [homebridge-xbox-tv] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'oneStoreProductId').  See https://homebridge.io/w/JtMGR for more info.
[02/01/2024, 17:21:34] [XboxTv] Device: <IP_ADDRESS> Xbox Series X, Mute: ON
[02/01/2024, 17:21:34] [XboxTv] Device: <IP_ADDRESS> Xbox Series X, Volume: 0

Still seeing the error here too after updating
log.txt

So the steps to reproduce this are:

Restart Homebridge/child bridge while console is powered off (plugin successfully polls console and logs info)
Power on console (plugin still successfully polls console and logs info)
Power off the console (plugin polls console successfully for power/media state but errors getting input information).

Polling will continue to fail until either the console is powered back on or Homebridge/child bridge is restarted.

Please go to Homebridge/xboxTv/ folder and remove inputs, inputsNames  and inputsTatgetVisibility files then restart plugin and let me know.

Updated to 2.12.5 and removed those files and that seems to have worked, thanks for your efforts @grzegorz914!

Updated and tested, everything is working great so far. Thanks @grzegorz914 ! Logs are staying clean, responsiveness of home actions and device state representation has improved back to similar duration prior to implementation of this plugin. Kudos, keep up the fantastic work. Plan on adding second xbox to this configuration and thoroughly testing so that I can roll out for the family. This is going to be game changer for them and my use case for automation of the AV systems.


[Flaky Tests] Address flaky tests preventing successful builds execution

The following flaky tests were identified while reviewing recent failing builds and are in Hostbusters team's scope:

./scripts/entry: line 8: exec: provisioning-tests-rke: not found
Test_Operation_MP_EtcdSnapshotCreationRestoreInPlace

SURE-6454

More flakey tests are identified.

test_mcapp_rollback_validation
=================================== FAILURES ===================================
________________________ test_mcapp_rollback_validation ________________________

admin_mc = <suite.conftest.ManagementContext object at 0xffffadd7f438>
admin_pc = <suite.conftest.ProjectContext object at 0xffffad289e80>
custom_catalog = <function custom_catalog.<locals>._create_catalog at 0xffffadcc9730>
remove_resource = <function remove_resource.<locals>._cleanup at 0xffffacb03730>
restore_rancher_version = None

    @pytest.mark.nonparallel
    def test_mcapp_rollback_validation(admin_mc, admin_pc, custom_catalog,
                                       remove_resource, restore_rancher_version):
        """Test rollback validation of multi cluster apps. This test will set the
        rancher version explicitly and attempt to rollback an app with rancher
        version requirements
        """
        # 1.6.0 uses 2.0.0-2.2.0
        # 1.6.2 uses 2.1.0-2.3.0
        c_name = random_str()
        custom_catalog(name=c_name)

        client = admin_mc.client
        set_server_version(client, "2.1.0")

        cat_ns_name = "cattle-global-data:"+c_name

        mcapp_data = {
            'name': random_str(),
            'templateVersionId': cat_ns_name+"-chartmuseum-1.6.0",
            'targets': [{"projectId": admin_pc.project.id}],
            'roles': ["cluster-owner", "project-member"],
            "answers": [{
                "type": "answer",
                "clusterId": None,
                "projectId": None,
                "values": {
                    "defaultImage": "true",
                    "image.repository": "chartmuseum/chartmuseum",
                    "image.tag": "v0.7.1",
                    "env.open.STORAGE": "local",
                    "gcp.secret.enabled": "false",
                    "gcp.secret.key": "credentials.json",
                    "persistence.enabled": "true",
                    "persistence.size": "10Gi",
                    "ingress.enabled": "true",
                    "ingress.hosts[0]": "xip.io",
                    "service.type": "NodePort",
                    "env.open.SHOW_ADVANCED": "false",
                    "env.open.DEPTH": "0",
                    "env.open.ALLOW_OVERWRITE": "false",
                    "env.open.AUTH_ANONYMOUS_GET": "false",
                    "env.open.DISABLE_METRICS": "true"
                }
            }]
        }

        # First app requires a min rancher version of 2.0 so no error
        mcapp1 = client.create_multi_cluster_app(mcapp_data)
        remove_resource(mcapp1)
        wait_for_app(admin_pc, mcapp_data['name'])

        mcapp1 = client.reload(mcapp1)

        original_rev = mcapp1.revisions().data[0].name

        mcapp1.templateVersionId = cat_ns_name+"-chartmuseum-1.6.2"

        # Upgrade the app to get a rollback version
        mcapp1 = client.update_by_id_multi_cluster_app(mcapp1.id, mcapp1)
        wait_for_app(admin_pc, mcapp_data['name'])
        mcapp1 = client.reload(mcapp1)

>       assert mcapp1.status.revisionId != original_rev, 'app did not upgrade'
E       AssertionError: app did not upgrade
E       assert 'mcapprevision-4gl8j' != 'mcapprevision-4gl8j'
E        +  where 'mcapprevision-4gl8j' = {'conditions': [{'lastUpdateTime': '2023-07-06T16:40:59Z', 'status': 'True', 'type': 'Installed'}], 'revisionId': 'mcapprevision-4gl8j', 'type': '/v3/schemas/multiClusterAppStatus'}.revisionId
E        +    where {'conditions': [{'lastUpdateTime': '2023-07-06T16:40:59Z', 'status': 'True', 'type': 'Installed'}], 'revisionId': 'mcapprevision-4gl8j', 'type': '/v3/schemas/multiClusterAppStatus'} = {'actions': {'addProjects': 'https://<IP_ADDRESS>:8443/v3/multiClusterApps/cattle-global-data:random-96280-1688661658?ac...gradeStrategy': {'type': '/v3/schemas/upgradeStrategy'}, 'uuid': '6670da58-91e6-4230-9eca-a0e0be7afcce', 'wait': False}.status

test_multi_cluster_app.py:618: AssertionError

estCRTBRoleTemplateInheritance (occurred multiple times)
=== RUN   TestRTBTestSuite
=== RUN   TestRTBTestSuite/TestCRTBRoleTemplateInheritance
    rtbs_test.go:254:
        	Error Trace:	/go/src/github.com/rancher/rancher/tests/v2/integration/rtbs/rtbs_test.go:254
        	Error:      	Received unexpected error:
        	            	namespaces "auto-testns--agixt" is forbidden: User "u-wvh9c" cannot get resource "namespaces" in API group "" in the namespace "auto-testns--agixt"
        	Test:       	TestRTBTestSuite/TestCRTBRoleTemplateInheritance
--- FAIL: TestRTBTestSuite (15.84s)
    --- FAIL: TestRTBTestSuite/TestCRTBRoleTemplateInheritance (14.83s)
FAIL
FAIL	github.com/rancher/rancher/tests/v2/integration/rtbs	15.875s

test_perform_workload_action_read_only
=================================== FAILURES ===================================
____________________ test_perform_workload_action_read_only ____________________
[gw15] linux -- Python 3.6.15 /go/src/github.com/rancher/rancher/tests/integration/.tox/rancher/bin/python3

admin_mc = <suite.conftest.ManagementContext object at 0xffffb6203fd0>
admin_pc = <suite.conftest.ProjectContext object at 0xffffb504c588>
remove_resource = <function remove_resource.<locals>._cleanup at 0xffffb53426a8>
user_mc = <suite.conftest.ManagementContext object at 0xffffb5353e10>
user_factory = <function user_factory.<locals>._create_user at 0xffffb5bb8e18>

    def test_perform_workload_action_read_only(admin_mc, admin_pc, remove_resource,
                                               user_mc, user_factory):
        """Tests workload actions with a read-only user and a member user.
           Note: this test exists only in 2.5+ due to pod scheduling on the
           local cluster. Manually ensure that any changes in 2.4 and below
           work."""
        client = admin_pc.client
        project = admin_pc.project
        user = user_mc
        user_member = user_factory()

        ns = admin_pc.cluster.client.create_namespace(
            name=random_str(),
            projectId=project.id)
        remove_resource(ns)

        # Create a read-only user binding.
        prtb1 = admin_mc.client.create_project_role_template_binding(
            name="prtb-" + random_str(),
            userId=user.user.id,
            projectId=project.id,
            roleTemplateId="read-only")
        remove_resource(prtb1)
        wait_until_available(user.client, project)

        # Then, create a member user binding.
        prtb2 = admin_mc.client.create_project_role_template_binding(
            name="prtb-" + random_str(),
            userId=user_member.user.id,
            projectId=project.id,
            roleTemplateId="project-member")
        remove_resource(prtb2)
        wait_until_available(user_member.client, project)
        user_pc = user_project_client(user, project)
        user_member_pc = user_project_client(user_member, project)

        # Admin user creates the workload.
        workload_name = random_str()
        workload = client.create_workload(
            name=workload_name,
            namespaceId=ns.id,
            scale=1,
            containers=[{
                'name': 'foo',
                'image': 'rancher/mirrored-library-nginx:1.21.1-alpine',
                'env': [{
                    'name': 'FOO_KEY',
                    'value': 'FOO_VALUE',
                }]
            }])
        remove_resource(workload)
        wait_for_workload(client, workload.id, ns.id)

        # Admin user updates the workload to yield a rollback option.
        workload.containers = [{
            'name': 'foo',
            'image': 'rancher/mirrored-library-nginx:1.21.1-alpine',
            'env': [{
                'name': 'BAR_KEY',
                'value': 'BAR_VALUE',
            }]
        }]
        workload = client.reload(workload)
        workload = client.update_by_id_workload(workload.id, workload)

        workload = client.reload(workload)
        wait_for_workload(client, workload.id, ns.id)
>       original_rev_id = workload.revisions().data[0].id
E       IndexError: list index out of range

test_workloads.py:411: IndexError
=============================== warnings summary ===============================
alert_common.py:21
  /go/src/github.com/rancher/rancher/tests/integration/suite/alert_common.py:21: UserWarning: The 'environ['werkzeug.server.shutdown']' function is deprecated and will be removed in Werkzeug 2.1.
    request.environ['werkzeug.server.shutdown']()

-- Docs: https://docs.pytest.org/en/latest/warnings.html
=========================== short test summary info ============================
FAILED test_workloads.py::test_perform_workload_action_read_only

rancher-webhook not ready
Checking if we can skip CI because of an only UI/dashboard change
Environment variable DRONE_BUILD_EVENT is push
Not skipping CI, not an only UI/dashboard change
Starting rancher server for provisioning-tests using v1.26.6+k3s1
Waiting for Rancher to be healthy
Starting rancher server using run
Waiting up to 5 minutes for rancher-webhook deployment
rancher-webhook was not available after 61 seconds
rancher-webhook was not available after 124 seconds
rancher-webhook was not available after 187 seconds
rancher-webhook was not available after 250 seconds
rancher-webhook was not available after 302 seconds
Stopping rancher server
./scripts/provisioning-tests: line 13:    68 Terminated              run_rancher
time="2023-07-05T23:16:46Z" level=fatal msg="exit status 1"

 test_app_mysql
=================================== FAILURES ===================================
________________________________ test_app_mysql ________________________________
[gw2] linux -- Python 3.6.15 /go/src/github.com/rancher/rancher/tests/integration/.tox/rancher/bin/python3

admin_pc = <suite.conftest.ProjectContext object at 0x7f5b0e98aac8>
admin_mc = <suite.conftest.ManagementContext object at 0x7f5b0ee0fac8>

    def test_app_mysql(admin_pc, admin_mc):
        client = admin_pc.client
        name = random_str()

        ns = admin_pc.cluster.client.create_namespace(name=random_str(),
                                                      projectId=admin_pc.
                                                      project.id)
        wait_for_template_to_be_created(admin_mc.client, "library")
        answers = {
            "defaultImage": "true",
            "image": "mysql",
            "imageTag": "5.7.14",
            "mysqlDatabase": "admin",
            "mysqlPassword": "",
            "mysqlUser": "admin",
            "persistence.enabled": "false",
            "persistence.size": "8Gi",
            "persistence.storageClass": "",
            "service.nodePort": "",
            "service.port": "3306",
            "service.type": "ClusterIP"
        }
        client.create_app(
            name=name,
            externalId="catalog://?catalog=library&template=mysql&version=1.3.1&"
                       "namespace=cattle-global-data",
            targetNamespace=ns.name,
            projectId=admin_pc.project.id,
            answers=answers
        )
>       wait_for_workload(client, ns.name, count=1)

test_app.py:40:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

client = <rancher.Client object at 0x7f5b0eb56048>
ns = 'random-829195-1688599970', timeout = 60, count = 1

    def wait_for_workload(client, ns, timeout=60, count=0):
        start = time.time()
        interval = 0.5
        workloads = client.list_workload(namespaceId=ns)
        while len(workloads.data) < count:
            if time.time() - start > timeout:
                print(workloads)
>               raise Exception('Timeout waiting for workload service')
E               Exception: Timeout waiting for workload service

test_app.py:857: Exception
----------------------------- Captured stdout call -----------------------------
{'type': 'collection', 'links': {'self': 'https://<IP_ADDRESS>:8443/v3/project/local:p-cmlx7/workloads'}, 'createTypes': {'workload': 'https://<IP_ADDRESS>:8443/v3/project/local:p-cmlx7/workloads'}, 'actions': {}, 'pagination': {'limit': 1000, 'total': 0}, 'sort': {'order': 'asc', 'reverse': 'https://<IP_ADDRESS>:8443/v3/project/local:p-cmlx7/workloads?namespaceId=random-829195-1688599970&order=desc', 'links': {'uuid': 'https://<IP_ADDRESS>:8443/v3/project/local:p-cmlx7/workloads?namespaceId=random-829195-1688599970&sort=uuid'}}, 'filters': {'created': None, 'creatorId': None, 'name': None, 'namespaceId': [{'modifier': 'eq', 'value': 'random-829195-1688599970'}], 'removed': None, 'uuid': None}, 'resourceType': 'workload', 'data': []}
=============================== warnings summary ===============================
alert_common.py:21
  /go/src/github.com/rancher/rancher/tests/integration/suite/alert_common.py:21: UserWarning: The 'environ['werkzeug.server.shutdown']' function is deprecated and will be removed in Werkzeug 2.1.
    request.environ['werkzeug.server.shutdown']()

-- Docs: https://docs.pytest.org/en/latest/warnings.html
=========================== short test summary info ============================
FAILED test_app.py::test_app_mysql

The following flaky tests were identified while reviewing recent failing builds and are in Hostbusters team's scope:

./scripts/entry: line 8: exec: provisioning-tests-rke: not found
Test_Operation_MP_EtcdSnapshotCreationRestoreInPlace

SURE-6454

I could not find any of those two failures in the Drone CI build history, and it is possible that I have not tracked back enough builds to see them. But on the other side, the good news is that those two do not appear in any failed build I have checked. Also, I could not reproduce them.

./scripts/entry: line 8: exec: provisioning-tests-rke: not found

The script file provisioning-tests-rke used to exist. It was renamed to provisioning-tests-rke2 in this commit, and then removed by this commit.  My best guess is that the failed CI did not get the full changes from the upstream repo. Therefore the Drone script is out-of-date and instructs to run the script provisioning-tests-rke, but the file has been renamed provisioning-tests-rke2.

Test_Operation_MP_EtcdSnapshotCreationRestoreInPlace

As mentioned above, I could not find the failed build for this test case. But I found another build which failed at a similar test case: Test_Operation_MP_EtcdSnapshotOperationsOnNewNode.
I do not find any logical error in our code around those two test cases. But I am making some generate improvements to the error messages and the output for troubleshooting to hopefully make it easier for us to troubleshoot CI failures.

Closing this issue because 1) the linked PR has been merged and 2) there is no need for QA to validate the fix.


Pinned checkov version

Resolves #281
Changes

Pinned checkov version.

Sure @lorenyu, can you merge this ?

Done!


v8.x re-render lazy component if dispatch was made during it

What version of React, ReactDOM/React Native, Redux, and React Redux are you using?

React: 18.2.0
ReactDOM/React Native: 18.2.0
Redux: 4.2.1
React Redux: 8.0.5

What is the current behavior?
So I was migrating our codebase from react-redux 7.x to react-redux 8.x when I faced the issue. We have some legacy components which use Classes and/or redux-form. In our case the issue led to infinite render loop, the behavior was pretty much the same as when you accidentally put setState() inside render;
We have a component like this:
class ObjectEditor() {
 constructor(props) {
   super(props);

   props.dispatch(initObjectEditor({id: props.id}))
 }
}

where props.id is generated by useId() in the upper component.
So code like this worked well on react-redux 7.x but began to cause infinite loop after upgrading to 8.x
Here is a small re-pro sandbox https://codesandbox.io/s/sweet-franklin-8uujc3?file=/src/Counter.js . While it doesn't cause infinite loop you can observe in logs that it renders two different Counter components with different 'id' props.
If you change react-redux to 7.x the issue is completely gone.
What is the expected behavior?
I'm not sure which behaviour is correct one but the fact that it has changed took 1.5 working days of mine to fully identify the problem.
Would be awesome if react-redux could print some warning to console in such case because it's very hard to find the reason of bailed-out renders
Which browser and OS are affected by this issue?
No response
Did this work in previous versions of React Redux?

[X] Yes

At first glance, I'm not sure if there's anything we can do about this.
React-Redux v8 uses React's new useSyncExternalStore hook.  Part of the point of that hook is that React is now responsible for managing the re-renders when the external store (such as Redux) updates.  As I understand it, that can include throwing away an in-progress render if an external update happens in the middle.
Generally, dispatching in a class component constructor is not a good idea to begin with, so I'm not surprised that's causing an issue here.

Generally, dispatching in a class component constructor is not a good idea to begin with, so I'm not surprised that's causing an issue here.

Yeah, agree with that. Just was a little bit surprised when some legacy components went to infinite loop after update. Also we have some of them using redux-form and it was causing infinite render too (as I can see they make dispatches in componentWillReceiveProps)
One last question from me:
Is it ok now to do something like this inside render?:
const Component = () => {
  const dispatch = useDispatch();
  const isInitialised = useSelector(getIsInitialised);

  if (!isInitialised) {
    dispatch(initStore);
  }
}

As I remember there was an error in console previously when you tried to do dispatch outside an effect

No, definitely not.  You should not trigger updates while rendering.

Thank you for clarifications!


fix: add more specs

This PR adds more specs

Changes Unknown when pulling 80ce243098f516ad4efdde6b805e7aba7e43b6b0 on setup-testing into ** on master**.


Add Ghost Datasource

Resolves issue #142

Thanks for the PR :)
I see it uses the normalizeFields and normalizeFieldValue methods from the WordPress source plugin. But I don't think it's necessary to use them in this plugin because the posts don't have a meta or post_type property.

Sorry about the overzealous C&P. Thought it was important for graphql. Updated and removed some of the unnecessary logging

No problem :) The methods were for creating references to other types. How will that work for this plugin? How is a post connected to its author for example? The Ghost documentation says related data like author etc isn't included unless an include option is specified.
The adminKey option isn't used, so I think you can delete it from the default options. And maybe contentKey can be renamed to key?
The default routes option is a mixture of singular and plural type names. Can you change them to only have singular type names?
And the Usage section in the readme file should use options related to this plugin. baseUrl should be url and it should also show the key option because it's also a required option.

Thanks for the updates :) I did a few changes + added support for settings as metadata.
Gridsome currently camel cases custom field names, but we are going to disable it by default in v0.6. Do you think this plugin should keep camel-cased names or maybe it's better to just stick with the same names as in the RESTful API?

I would say have a pattern for gridsome and then have the plugins translate to each individual api

Hi wonderful people :smile: Not really clear to me from the comments who we're waiting for here. @hjvedvik @technoSpino: please reply with an update.

@robaxelsen @technoSpino I think it's ready to be merged. But I can update it to work with 0.6 first :)

@technoSpino I did some updates, but haven't been able to test. My trial period ended. Are you able to test the plugin with the latest changes?

So I did some testing. Hope it helps.
Self hosted ghost (@hjvedvik - you don't need a paid trial to test it, ghost can be self-hosted and it's as easy as installing it and doing a ghost start and going to localhost:2368 > integrations and setting a custom api key).
I was able to pull and list the posts just fine. All data seem to be populated correctly on graphql.
Some minor things @technoSpino

options on packages/source-ghost/README.md are documented wrong. README says baseUrl should be set while index.js expects url. Also, you must set a contentKey as key and this is not documented on README.md for the source. I suggest using baseUrl and contentKey as options considering there is also an adminKey.

Build failed if my posts do not have tags. Had to comment out lines 106 to 109 on index.js.

I guess the graphql queries should be renamed to plural (allGhostPost > allGhostPosts)?

Other than that it works. Thank you very much.
PS: I am just starting out on gridsome. I could submit some code but I am not yet confident.

Thanks for your feedback @dominiquedutra. Just installed Ghost locally and it works great! I'll change url and key back to baseUrl and contentKey and check if the post has a primary_tag :)

Thanks for the help @hjvedvik and @dominiquedutra


Delimiter changed inside statement error

Which version and edition of Flyway are you using?
6.3.1
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using (type & version)?
MySQL 8.0.19
Which operating system are you using?
macOS, Centos 7
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
Run flyway migrate on the attached project
What did you expect to see?
A stored procedure being created.
What did you see instead?
Flyway Community Edition 6.3.1 by Redgate
Database: jdbc:mysql://localhost (MySQL 8.0)
Successfully dropped pre-schema database level objects (execution time 00:00.001s)
Successfully dropped schema `repro` (execution time 00:00.011s)
Successfully dropped post-schema database level objects (execution time 00:00.001s)
Flyway Community Edition 6.3.1 by Redgate
Database: jdbc:mysql://localhost (MySQL 8.0)
Creating schema `repro` ...
Creating Schema History table `repro`.`flyway_schema_history` ...
Current version of schema `repro`: null
Migrating schema `repro` to version 1.0 - repro
ERROR: Unable to parse statement in sql/R__1_repro.sql at line 4 col 1: Delimiter changed inside statement at line 4 col 1: create procedure proc1()
begin
  update t1 set col1 = if (true, 0, 1);
end$$

Also, removing space between if and ( makes the problem go away
repro.zip

Fixed in 2fa1720d3599a0a9f03c52cc8e4100541b11f08f

... which will be in the 6.3.2 release


feat: support redirecting the logs to the terminal

what problem are you trying to solve? (or if there's no problem, what's the motivation for this change?)
-> Fixes #670
-> Currently, Xline does not support redirecting the logs to the terminal. It  outputs to a specified log file through --log-file in command line. If the user does not specify this parameter, the file path /var/log/xline is created by default.

what changes does this pull request make?
-> Checks whether the user specifies  --log-file. If not, output the logs to the terminal and ignore --log-rotate if provided.

are there any non-obvious implications of these changes? (does it break compatibility with previous versions, etc)
-> No

@Mergifyio rebase


The call to griddata used pandas dataframe arguments, which apparentl…

…y don't work in griddata. Passing numpy arrays instead.

I am aborting this PR.


Implicit type conversion failure

Go version
go version go1.22.3 windows/amd64
Output of go env in your module/workspace:
Set GO111MODULE=
set GOARCH=amd64
set GOBIN=C:\Users\utpal\go\bin
set GOCACHE=C:\Users\utpal\AppData\Local\go-build
set GOENV=C:\Users\utpal\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\utpal\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\utpal\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.22.3
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=0
set GOMOD=C:\Users\utpal\go\src\learn-go-with-tests\wallet\go.mod
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\utpal\AppData\Local\Temp\go-build3300580940=/tmp/go-build -gno-record-gcc-switches

What did you do?
Checkout the main function where Deposit method call accepts direct int value rather than Explicitly converted value.
package main

import "fmt"

type Bitcoin int

type Wallet struct {
	balance Bitcoin
}

func (w *Wallet) Deposit(amount Bitcoin) {
	w.balance = amount
}

func main() {
	w := Wallet{}
	w.Deposit(100)
	fmt.Println(w.balance)
}

What did you see happen?
Code runs fine.
What did you expect to see?
I didn't expect the above code to compile, since implicit type conversion is not a feature of Go , but in this case how come this is working.

Untyped integer constants like 100 are assignable to types that have an integral underlying type. There's not really an implicit conversion here in the way other languages define them, and it's certainly not unsafe in the same way. Untyped integer constants have effectively infinite precision, but you'll get a compile error if you try to assign an untyped integer constant into a value whose type can't fit the number (for example, uint8(257) will fail at build time).
I believe this is all working as intended. Closing this issue.


Select correct access group for SubscriptionTokenKeychainStorage

Task/Issue URL: https://app.asana.com/0/547792610048271/1207483115895951/f
Tech Design URL:
CC:
Description
We're using .unspecified access group for SubscriptionTokenKeychainStorage .  While this is not causing trouble, it's not correct and should be changed.
Testing
Make sure the VPN works and connects.

Internal references:
Software Engineering Expectations
Technical Design Template

Task/Issue URL: https://app.asana.com/0/547792610048271/1207483115895951/f
Tech Design URL:
CC:
Description
We're using .unspecified access group for SubscriptionTokenKeychainStorage .  While this is not causing trouble, it's not correct and should be changed.


[Help] Any simple way of closing dropdow on click?

Hi all,
This is my code. i've been working 2 hours on trying to find a way to close the dropdown on click... How can I achieve this?
There is an open attribute...How do I get the reference to it on the handler? I tried using useRef() whitout any success. i cannot find the proper type... :(
const handleOnClick = (l: string) => {
    router.push({ pathname, query }, asPath, { locale: l });
  };

  return (
    <Dropdown>
      <Dropdown.Toggle color="ghost">{locale.toUpperCase()} </Dropdown.Toggle>
      <Dropdown.Menu>
        {locales.map((l) =>
          <Dropdown.Item key={l} onClick={() => handleOnClick(l)}>{l?.toUpperCase()}</Dropdown.Item>
        )}
      </Dropdown.Menu>
    </Dropdown>

Hi @AlexandreRoba, see this thread for a few different ways to do this:
https://github.com/saadeghi/daisyui/issues/157


Can't import module when running tsc --project tsconfig.json

IMPORTANT: This repository's issues are reserved for feature requests and bug reports. Do not submit support requests here.
Steps to reproduce and a minimal demo of the problem
git clone --depth 1 https://github.com/mgechev/angular2-seed.git
cd angular2-seed
npm install
tsc --project tsconfig.json

What steps should we try in your demo to see the problem?
Current behavior
> tsc --project tsconfig.json

1 import { join } from 'path';
                       ~~~~~~~
tools/config/project.config.ts(1,22): error TS2307: Cannot find module 'path'.

2 import { argv } from 'yargs';
                       ~~~~~~~

tools/config/seed.config.ts(2,22): error TS2307: Cannot find module 'yargs'.

Expected/desired behavior
it worked fine when this repo use RC5, I used this seed in my project before on the same Windows box.
Other information
OS Win10
node v4.4.7
npm  v3.10.7

Would you also try:
npm i -g typings
typings install

@mgechev  thx
I don't kouwn why but it works now!

It was not supposed to be required this time neither..in the postinstall phase some of the typings were missing on any reason.


Add Swap-In And In-Place Update Variants

This PR implements two fully working update mechanisms: Swap-In and In-Place.
Please see https://github.com/tanneberger/rtrlib/blob/cab58c9b3cf2d5bf3cfd3e63939991d9f24c8e4b/rtrlib/aspa/aspa_private.h#L16 for a detailed description of both approaches.
@tanneberger @mrzslz Should I rename the update functions so that they have a common prefix like aspa_table_update_swap_in_* and aspa_table_update_in_place_*?
Swap-In needs these function:

aspa_table_compute_update (creates new array + locks a special lock ensuring the table isn't changed while computing the update)
aspa_table_apply_update (swaps in new array)
aspa_table_finish_update (clean up, unlock special lock)

In-Place needs these:

aspa_table_update
aspa_table_undo_update
aspa_table_update_cleanup

@tanneberger @mrzslz Should I use a bool instead of enum aspa_operation_type?

I'am pro common prefix

What do you wanna encode in this bool / enum?

@carl-tud  I'd prefer a bool for aspa_operation_type, but with predefined constants ASPA_REMOVE and ASPA_ADD. This saves memory and performance overhead, as an enum is large enough to fit an entire int. I'd also suggest to move is_no_op forward to reduce memory consumption further (struct packing).
struct aspa_update_operation {
	size_t index;
	bool type;
	bool is_no_op;
	struct aspa_record record;
};

@tanneberger Do you still have comments on this? If no, I'd merge this.


trap in wrong section in ch1

Dunno how to PR changes to the blog source, can't find it anywhere, so I'll just leave a description here.
The .section .text part in trap.S in the blog post should not be there. It prevents compilation. The source code in this repo shows the correct code.

The code in the blog post is incomplete, and it's just a shell. Although, I don't see how .section .text should prevent compilation. Do you have an example?


Epic: evict inactive timelines on safekeepers to s3

### Tasks
- [ ] https://github.com/neondatabase/neon/issues/6336
- [ ] https://github.com/neondatabase/neon/issues/6337
- [ ] https://github.com/neondatabase/neon/issues/6338

Progress on #6337 planned this week, but, multi-week project.

This week:

monitor release of PR that was merged last week (TODO: link)
impl & create PR for https://github.com/neondatabase/neon/issues/6337

This week:

an unlinked (please link) bug related to eviction
then this issue should be ready

Last week:

eviction PR was merged to staging, but not enabled anywhere
then I discovered a bunch of issues and merged some fixes
verified that no critical issues are left on staging

This week:

waiting for production deploy to ensure nothing break with DISABLED eviction
after that, we can enable eviction in staging and look for new issues

Next week:

if everything will be good in staging, we should enable eviction in prod

Later:

enable file deletion gradually in all regions (first staging, then prod)

Status: https://github.com/neondatabase/neon/issues/6338 is blocked on https://github.com/neondatabase/neon/issues/8542

Modified assignee to Arseny, who is managing the rollout

Modified assignee to Arseny, who is managing the rollout


Observables

So there's this cool thing called Observables that is (likely) coming to the language soon (ref 1, ref 2).
They are similar to promises in a number of ways.

They both attempt to deal with asynchronous actions in a reasonable manner.
They both define a standard interface that can be implemented and extended by third parties.

Since Mocha supports returning promises in order to avoid using the done callback, it'd be nice if it did the same thing with observables:
it('should do something with an Observable', () => {
  return Observable.of(1, 2, 3).subscribe(...);
});

People are already using these with http://reactivex.io/.
cc @blesh

Side note: Gulp is doing the same thing with Observables in 4.0.

One temporary solution for RxJS Next/5 is to use forEach rather than subscribe, as it returns a promise. But it's not ideal.

Is this something Mocha would accept a PR on?

I'm not yet familiar with how observables are implemented under the hood, so I want to check one thing: would this interfere with making generator test functions be failures, if the latter were implemented by checking for typeof (<result> && <result>.next) === 'function' on the test return value?
Obviously, handling generators (even as automatic failures*) and handling observables can be two separate enhancements; I just want to make sure that by deciding to add either one we aren't closing off the ability to decide for or against the other.
*(In case the rationale makes this any clearer, I've come part way around on my thinking in this regard since it was last discussed: I'm still not so sure we would want Mocha to assume that the promise-unwrapping generator wrapper behavior is the one that should be default-associated with tests, but I see enough usefulness in such wrappings -- for Selenium especially -- that I think passing the test if somebody forgets the wrapper is unhelpful, and I think checking for the .next function on the returned object should be a safe enough way to do it without losing any browser support... but I suppose I should dig up the old issue on that and present my updated thoughts there.)

@ScottFreeCode For the PR I opened (#2722) I used symbol-observable, as that seems to be the consensus in the community for observable interop. If the return value has that set, we can use that to determine if we should consume the observable. Because it uses a completely different mechanism, it doesn't have any impact on support generators later.


Fix slow initial load

We have a number of autogenerated reports of high CPU load during the first run of the extension; anecdotally it is feeling slow to load/unpack again.  This is a tracking issue for that problem.  See also #500.

FWIW, I can also confirm the initial load time of the extension when VS Code starts has significantly increased.

The good news: Webpack does make this hugely faster.
The bad news: Webpack is currently blocked by the jsonpath dependency (via @kubernetes/client-node): https://github.com/webpack/webpack/issues/9367


Let the host (e.g. Ember) handle layout caching

This removes the special CACHED_LAYOUT symbol and instead replaced it with a layoutFor hook on the component manager. The primary reason for this is to decouple layout caching from component definitions (the hosts can implement their own caching layer).
In addition to that, it also solves the problem of Ember’s “late-bound” layout feature, because the layoutFor hook is called after create, and we pass in the component instance as an argument to layoutFor. This allows you to make whatever decisions you need to construct/lookup the right layout.
Finally, this also allows the hosts to return optimized layouts based on instance-side information.

TODO: deal with visualizer and layoutFor

Also: bring back caching


[WIP] release: Add Dockerhub READMEs

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

As im working through this im realizing that as we produce a load of different images (rather than a single image with lots of tags) we will need a lot of ~different READMEs

merging in the other images to the envoyproxy/envoy dockerhub namespace - this is now pretty desperately needed

https://hub.docker.com/r/envoyproxy/envoy
https://hub.docker.com/r/envoyproxy/envoy/tags

closing this in favour of #25550 which has gotten further


Provide download link for the .jar files needed

Please provide a link for the .jar that are needed to be download to connect to ADX, or at least a list of the sources, the way it is is hard to figure where each .jar should be dowloaded.

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

ID: 1f6149ce-1c3c-d2a2-79a9-cb181240ce90
Version Independent ID: 372e6191-af44-ba93-bf59-c3bcc236c270
Content: MS-TDS clients and Kusto - Azure Data Explorer
Content Source: data-explorer/kusto/api/tds/clients.md
Service: data-explorer
GitHub Login: @shsagir
Microsoft Alias: shsagir

Thanks for the feedback! We have assigned the issue to the content author to further review this and update the document as appropriate.

@KhaoticMind Thanks for contacting us with feedback about our product documentation. Depending on the complexity, it could take from a few business days to a few weeks to look further into your question, issue, or suggestion. We'll contact you if we need further information, and you'll receive an email message each time we "@mention" you in a comment.
Thanks again for submitting your feedback. Your suggestions help improve our documentation.

@name Thanks again for your feedback. After investigating with the product dev team, we've discovered the list of jar files is provided for example purposes only. It's not jar files we provide. As such, we cannot change the referenced page to include the information and functionality that you're asking for and we're closing this issue.
#please-close


ARROW-9683: [Rust][DataFusion] Add debug printing to physical plans and associated types

For ARROW-9653, I was trying to debug the execution plan and I would have found it easier if there had been a way to display the execution plan to better understand and isolate the issue. This would also be nice to have as part of EXPLAIN plan functionality in ARROW-9654
In general, for debugging purposes, we would like to be able to dump out an execution plan. To do so in the idiomatic rust way, I made ExecutionPlan also implement std::fmt::Debug and then followed rustc guidance until I got everything that was needed
Here is an example plan for "SELECT c1, c2, MIN(c3) FROM aggregate_test_100 GROUP BY c1, c2" when printed using println!("{:#?}", plan):
physical plan is HashAggregateExec {
    group_expr: [
        Column {
            name: "c1",
        },
        Column {
            name: "c2",
        },
    ],
    aggr_expr: [
        Min {
            expr: Column {
                name: "c3",
            },
        },
    ],
    input: DataSourceExec {
        schema: Schema {
            fields: [
                Field {
                    name: "c1",
                    data_type: Utf8,
                    nullable: false,
                    dict_id: 0,
                    dict_is_ordered: false,
                },
                Field {
                    name: "c2",
                    data_type: UInt32,
                    nullable: false,
                    dict_id: 0,
                    dict_is_ordered: false,
                },
                Field {
                    name: "c3",
                    data_type: Int8,
                    nullable: false,
                    dict_id: 0,
                    dict_is_ordered: false,
                },
            ],
            metadata: {},
        },
        partitions.len: 1,
    },
    schema: Schema {
        fields: [
            Field {
                name: "c1",
                data_type: Utf8,
                nullable: true,
                dict_id: 0,
                dict_is_ordered: false,
            },
            Field {
                name: "c2",
                data_type: UInt32,
                nullable: true,
                dict_id: 0,
                dict_is_ordered: false,
            },
            Field {
                name: "MIN(c3)",
                data_type: Int64,
                nullable: true,
                dict_id: 0,
                dict_is_ordered: false,
            },
        ],
        metadata: {},
    },
}

Rebased to pick up 37ee600


Trezor firmware 1.3.3 changes the amount display during sign

The new display shows the total amount including fees:
Really send
0.00794 BTC
from your wallet?
Fee included:
0.00003 BTC

The previous display was:
Really send
0.00791 BTC
from your wallet?
Fee will be:
0.00003 BTC

Shall we just make this show the "1.3.3" text ALWAYS rather than make it conditional on the firmware release ? On KISS grounds.

Yeah. Almost everyone will upgrade at this stage, especially if we provide an outdated firmware alert.

I've added support for a "deprecated firmware" alert. This will provide an incentive for users to upgrade their firmware and also sets up an expectation of mild incompatibility: such as why the display is different on their device to that showing in MBHD.

good idea

Updated the text to match the 1.3.3 firmware. See screenshot:

Ready for review and close.

Confirmed text matches what is on the Trezor screen for both Send bitcoin and Empty wallet.
Closing.


add publisher.sh for unix

Not planned. CI / CD stuffs are too customizable, and github action is also much better than a .sh script


STORM-1704 When logviewer_search.html opens daemon file, next search always show no result

https://issues.apache.org/jira/browse/STORM-1704

ensures that is-daemon parameter is passed around multiple searches
set logviewerUrl to '/daemonlog' when search is done with is-daemon=yes

+1. @HeartSaVioR should we merge this for 1.x-branch as well.

@harshach Yes sure, #1330 is ready for reviewing. Could you review that as well?


flags to render inkey in standard page positions.

[ ] top left
[ ] top center
[ ] top right

top-aligned left, center and right are supported.
but what about bottom-aligned and center-aligned?


Getting error on expression 0 6/12 * * *

~/node_modules/node-cron/src/pattern-validation.js:92
throw new Error(${patterns[2]} is a invalid expression for hour);
^
Error: 6/12 is a invalid expression for hour

I want to run cron on 6am and 6pm everyday

0 6,18 * * * would be the correct expression. Using this, the cron job will run at 6 and 18 hours, which are 6am and 6pm everyday.


Adds offset to items when dragging

This PR adds offset to items when dragging so dragging appears seamless. This helps mitigate the issue when dragging an item, the item would center to the cursor and causing bad UX.

Related issues:

https://github.com/ricardo-ch/react-easy-sort/issues/11

Thank you for bringing this cool improvement and also for the clean code!

This was published in v1.0.0. However, I had to revert it in v1.0.1. because I found a bug while integrating it on our website: it doesn't work if the container is not at the top-left of the window. You can see it on Storybook if you open the "docs" version.
Do you think you could have a look to have this fixed?

See :

Ah ok I’ll resubmit with the fix

Ok this PR should fix that https://github.com/ricardo-ch/react-easy-sort/pull/13


[Bug]: Unauthorized Delete App returns 500 instead of 403

What happened?
When calling Delete App with permission to list, but not delete apps, the app handler returns a 500 regardless of the error type instead of intelligently wrapping and responding with a 403 if the app exists but the user does not have permission to delete it.
What you expected to happen
Return a 403 error similar to this PR branch when the app cannot be deleted due to insufficient permissions.
Acceptance Criteria
GIVEN I am a k8s user with permission to list but not delete apps
WHEN I send a DELETE app request to the cf api shim
THEN I receive a 403 error
How to reproduce it (as minimally and precisely as possible)
Create a k8s clusterrole and rolebinding with only permissions to list apps. Use it to send a delete app request to the cf api shim.
Anything else we need to know?
V3 error codes: https://v3-apidocs.cloudfoundry.org/version/3.113.0/index.html#common-errors
Environment
Applies to all K8s distributions

Closing as this is already fixed!


Missing serialization for org.enso.common.CachePreferences$Kind

Noticed while running a simple project:
[enso.org.enso.interpreter.runtime.SerializationPool] Serialization of module `local.NewProject5.Main` failed: No persistance for org.enso.common.CachePreferences$Kind
[enso.org.enso.interpreter.runtime.SerializationPool] Serialization task failed for [local.NewProject5.Main].

I am surprised CachePreferences are being serialized at all! Why? Why that should be part of any caches? Anyway, it has been introduced by

#11341

Passing to @4e6 as the author of that PR.


Deprecation in Rails 5

Hi, so far I can see, everything works in Rails 5. There is one little deprecation:
DEPRECATION WARNING: Passing strings or symbols to the middleware builder is deprecated, please change
them to actual class references.  For example:

  "ActiveElasticJob::Rack::SqsMessageConsumer" => ActiveElasticJob::Rack::SqsMessageConsumer

Hi @karensg ,
Thanks for the submission. If you are up for  a PR I'd be happy to merge.
Cheers,
tawan

The Travis test failed, but I think that the error is unrelated or I am wrong?

Yes,  tests always fail on PRs at the moment. Please ignore it for now. I
will have a look at the PR soon. Thanks a lot for the submission.
On Tue, Jul 12, 2016 at 9:59 PM, Karens<EMAIL_ADDRESS>wrote:

The Travis test failed, but I think that the error is unrelated or I am
wrong?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tawan/active-elastic-job/issues/38#issuecomment-232161264,
or mute the thread
https://github.com/notifications/unsubscribe/AAAZm1ySR6webMekHjpgsstm6HWefAIDks5qU_IGgaJpZM4JG9nO
.

--
Tawan SIEREK
Phone:    +43 650 700 20 12
Email<EMAIL_ADDRESS>Address: Margaretenstraße 61/3 | 1050 Vienna | Austria
Skype:   Tawan Sierek

Hi @tawan, I notice that the last version is 1.6.1 - May 24, 2016 - would be greato to bump the version and release a new version including also this deprecation fix, thanks. 👍


Getting System.IO.InvalidDataException at Decrypt method

Just before booking the slot it breaks. And no slot gets booked.
Request you to please help in running this.

Same issue is there in latest master and in v4.2.0 as well.
Could you please let us know when we can expect this to be fixed or how to fix it?

@lakshaykaura Please use the App from the Release Version.
You are getting the Error since the Code doesn't have the secrets embedded in them. Either you get the secrets for yourself and replace them in the file, else you the Release Version.

Hi I am using release version only v4.2.0

@lakshaykaura Yes please try with the EXE since it has everything in it and you don't need any dependencies. Just a double click.
Since you are curious to know the reason of the error, see this: https://github.com/SRvSaha/CoWinVaccineSlotFinder/blob/master/CoWin.Core/Models/CaptchaModel.cs
Basically you can put Encrypted Model with Base64 encoding along with the Secret Key. You'll then be able to use it from Visual Studio as well. Hardcoding those details in Code ain't good practice.

Alright! That explains. So I am using exe now. Hopefully it will not fail :)
Btw Thankyou @SRvSaha so much for such an awesome app.

@lakshaykaura Yep that will work without fail, don't worry! Thanks for using it. Happy to help! Please share it in your circles and help the needy to get slots. Let me know if you could book your slot. You may like to share your testimonial/feedback here: https://shawt.io/r/sYx

With latest exe I am getting this error now-

Even though throttling is off, refresh time is 40000ms which is like 7-8 requests in 5min. Even if it count one request per district then also I am searching in 2 so total of max 16 requests in 5min which is way less than 100 requests in 5min limit. Could you please help on how to fix this?

@lakshaykaura IsThrottlingToBeUsed to be set to true, it is to be kept false only when CoWIN has removed Throttling from APIs. If it is set to false, then it will by default take 40 sec as sleep time between any subsequent API calls which looks okay to me. TBH, the Rate Limiting implemented by them is buggy so this happens. Also, another this is, since your public IP Address is shared and let's say you are using your phone as well as the Software to make requests, all will be counted towards 100. Also since your IP is shared with lets say 5 people, even their hits will be counted for 100/5 mins.
Caveat is, the rate limiting is checked in sliding window of 30 seconds and therefore you can just close the App whenver you get IP Throttled and restart after 10/15 seconds. Your authentication is taken care of so you won't need OTP unless 15 minutes is over. So you can keep closing and re-starting the App without any issues.

Hey , I am using 4.1 release. Its works for me very well . I dont want to use 4.2 version bcs of many reason.
But i want that IsSearchToBeDoneForVaccinationCentreName": true, feature.
Is it possible ?

dont need throttling stuff bcs i have multiple IP

@betagoyal Good to know that version 4.1.0 works pretty well for you.
Now coming to the question of IsSearchToBeDoneForVaccinationCentreName option, well there is no backward compatibility for the feature.
Secondly whatever you could do with v4.1.0, you can even do with v4.2.0. You need to turn off the throttling and set SleepInterveralInMilliseconds to 2000 and then it will work as v4.1.0 only. And when your IP gets throttled you can keep on switching your IPs since you are telling you multiple IP Addresses.
Hope this addresses your query! Grateful if you star the repo if I could help!

In 4.1 release when an IP gets block i switch to another IP thats all. I need not to close running instance .
In 4.2 i have to close that instance, change ip  and then i re run exe file again . Its a headache and one more thing in 4.1 release an IP works longer then 4.2 .
4.2 version have to run again n again . Its not that peaceful .
I think its not hard for u .
I can attach SS

As u suggest I turned  off throttling and tried like you said . But it does not work

@betagoyal The Application needs to be re-started as of now. There is no other option, but re-starting  hardly takes 1 second since you don't need to enter your OTP or anything. I will check if something can be done so that user gets an option to either exit the application or continue by pressing any key.
Throttling will be there in both versions. Just the thing is you need to change IP or try after 10 seconds. That's not in my hand.

@SRvSaha Thanks for considering problem. try to resolve with 4.2 .
AND BCS OF YOU MY WHOLE FAMILY VACCINATED .
THANK YOU
THANK YOU
THANK YOU

@SRvSaha any list of error codes and their description? Got below three times today for different centers-

@SRvSaha Thanks for considering problem. try to resolve with 4.2 .
AND BCS OF YOU MY WHOLE FAMILY VACCINATED .
THANK YOU THANK YOU THANK YOU

Hi, Feature shall be a part of v5.0.0
Glad that I could help. Star the Repo and share with others so that they can also get vaccinated.

@SRvSaha any list of error codes and their fixes? Got below three times today for different centers-

There is no such list of available, basically the Error is coming as the Slot which you were trying to book got already booked till the time you tried, since 100s of people are trying for very limited seats.

New update works like charm . Now i have stared the repo.

@betagoyal Awesome! Glad that you liked it. Share it with others as well so that it can be of help!

@betagoyal @lakshaykaura Can you please test the scenario as per the description in #79 in your machine and see if it works. Need some feedback that it works, before making a new release. See the discussions for all different types of test scenarios. Would be happy if you can contribute.

@SRvSaha i am already on it ..will get back to you soon


Transfer with desktop wallet

Ubuntu 18.04.2 LTS
Steps:

Input "Recipient address", "Amount"
Use default "Gas price" and "Gas limit"
Send transaction

Issue:

After confirmation dialog it returns to main screen, no error messages but "send transaction" button icon keeps reloading...
Transaction don't go through

Tested with different gas price and gas limit, same issue.

this is a good catch - the network provider is localhost in that case because I built it in development mode :P
sorry for the inconvenience.


Long term plans/roadmap for xtdberl?

Just inquiring on the future of this library. I am interested in using it, contributing (although I am a bit rusty with erlang).

I don't really have any concrete plans as I'm not currently using this in production.
Haopy to take PRs for any improvements. One area I'd like to develop further is defining links and automatically generating nested pull patterns based on those.

One area I'd like to develop further is defining links and automatically generating nested pull patterns based on those.

Can you say more here? What does this look like in datalog?

I see ok https://docs.xtdb.com/language-reference/1.23.2/datalog-queries/#pull


fix(docs): Update RBAC permissions required for Spinnaker

Two things:
-Noticed that I was getting errors in the apiserver log that Spinnaker did not have create permission on "pods/portforward"
-Some of the existing entries have curly quotes, which leads to a silently invalid config file when copy-pasted

Good catch on those curly quotes, @ezimanyi !


chore: Bump zep cloud sdk version and clean up zep cloud vector store node

@HenryHengZJ Hi, apologies for the wait time on this. This is a fix for the reported anthropic and gemini models chains issues when zep cloud memory is used.
This PR updates the zep-cloud sdk to point to our most recent sdk (we have split the open source and cloud sdk a few months ago). Additionally, I cleanup up zep cloud vector store node a bit.
Also quick note - we now maintain langchain components for zep cloud inside of langchain repo, and are planning to remove langchain components from our sdk at some point in the future. I initially tried to update the langchain community and core version to include the latest releases (our cloud components are available in 0.2.17 community version which itself requires a core bump) with our components there, but saw build errors and decided to leave that to you guys when you get to it. Pls ping me when you upgrade and I will open another PR to use import those components into zep nodes.

@paul-paliychuk thanks for the update.
Yes we are upgrading to 0.2 in this PR https://github.com/FlowiseAI/Flowise/pull/2798


Issues with secondary D-link card on OPNsense 17.x series

Hello
i've upgraded recently from opnsense 16.7 to 17.7 (tried different 17.x versions and tried upgrade and clean install) and started to face weird issue with DGE-528T Gigabit Ethernet Adapter
hardware config description:
3 LAN interfaces:

bult-in AR8131 Gigabit Ethernet
2x PCI DGE-528T Gigabit Ethernet Adapters
Dlink interfaces for dual-home internet from different ISP's
Dlink interfaces configured into failover gateway group (ISP's gateways are monitored)

issue description:

one of the Dlink interfaces start loosing connection with ISP gateway every 10-15 minutes. connection get lost for random period of time up to 10 min. traffic gets blackholed
no errors, no collisions
on opnsense 16.7 everything works without issues

Hi there,
Do you have gateway switching enabled under firewall: settings: advanced?
Cheers,
Franco

PS: it would be good to know when this started happening. 16.7 to 17.7 is a long way... I'm guessing you were on 16.7.14_2? How does 17.1.4 behave? How does 17.1.11_1 behave?

Hi,
everything was fine on OPNsense 16.7.14_2-amd64

i've upgraded to 17.1 about 30-35 days ago and performed update to the latest version at that moment.
that's the moment when this started happening
on 1st of aug updated to 17.7.(latest) - same behaviour
exported config, performed fresh install of 17.7, imported config - same behavior
installed 16.7 - imported config - everything works fine

i haven't touched any settings under firewall: settings: advanced,   so everything should have been configured with default settings there

So 17.1.11_1 is not working for you, but 17.1.4 is?

none of 17.x line were working (at least the ones i've tried)
because of that i had to revert to 16.7

You can try FreeBSD 11.1, we will likely adapt 18.1 to it. It looks like 11.0 changed something, but can't be sure unless someone looks at the driver who knows them. Unfortunately that's not us.


why use SIN and not underlying public key?

is it just because the SIN carries an additional few pieces of metadata, such as the SIN type? Or is it for security? As far as I understand the public key is sent with every request, so it's not being kept secret.
one more question: the bitcoin community is very much against reusing private keys, but it seems like SINs are meant to be reused. How do you reconcile the two?

The underlying public key is used, correct. So technically an implementation could not use the SIN, and only the public key.


Can the name be split into two fields?

I would like to use this with Authorize.Net DPM. The DPM accepts a first name and last name as two separate fields, and it does not support a single cardholder field. Is there an option built into skeuocard to allow for two name fields? Or would this require some major customisation?
Additionally, Authorize.Net DPM takes the expiry date as a single, four-digit field. Combining the two fields that skeuocard uses is trivial. It is the opposite direction with the free-format name field that is probably not going to be easy.
Any ready solutions to this?

We could split the name that is entered into first and surname, but I imagine that would start to get tricky with double-barrel names, and when titles are added ("MR FREDERICK LORD BLENKINSOP").

@judgej did you find or create a solution to this issue?

No, we used the JS library from Stripe instead. That works well enough.


Favorite plugins page

How does the site remember my favorite plugins? Via cache? I'm not sure if registering account is ok for more permanent storage?

Yes, I am using the localStorage of the browser to store user's favorite list and it doesn't sync across browsers or devices.
As of now, the site is a light weight statically generated site. Not sure if we should add login capabilities and expose a backend just for favorites use case.
One alternative could be allowing the user to export the list of favorite plugins via json file and import it on another device.

yeah, I think we shouldn't make the site heavier. I have a better idea: why don't we make a plugin to store this data, or to combine with BRAT?

why don't we make a plugin to store this data

Mobile/tablets, PWA etc. won't have the support for plugins. Also, what will plugin provide us? Will it let us sync the data across devices? I don't think it is possible without supporting authentication on the plugin end.

or to combine with BRAT?

I know BRAT as a Beta plugins place. Are you suggesting to include the plugins from BRAT or store data like how BRAT does? (I haven't explored this yet, tbh)

A feature enabling user to load their local vault .obsidian/community-plugins.json file up to the page import the local session favorites of the site would be very convenient.
Then it becomes reasonably possible for users to sync site favorites to match the installed set of plugins of their vault synced on any device, and still avoid overloading the site with authentication for it.


Cannot compress LLama weights

In notebook 254-llm-chatb-7b, I run the cell to "save floating point and compress model variants" after choosing the LLama-2-chat-7b and INT8 model, but I get an URL open error that eventually causes the kernel to die- as seen in screenshot attached.

I am not sure if this is a memory problem, as I would expect to see an "out of memory error" - but am running out of other reasons for what could be causing this. My machine is an Intel® NUC 13 Extreme Kit - NUC13RNGi9 which has ~32Gb CPU memory which I believe is being used although I also have iGPU (Intel® UHD Graphics 770) and dGPU, which has 32Gb VRAM which I suspect is not being used. I have encountered this same issue on another machine with CPU only and 32Gb mem as well.
I followed the ubuntu installation guide, and successfully ran the hello-world notebook. Thanks in advance.
 I also use one of my authentication tokens to login into my account through the jupyter notebook using lines:
from huggingface_hub import login
login()
which I am then prompted to insert my authentication token, which gets properly validated. I know this method of logging in has worked for others - I'm not sure why I wouldn't have access to the model. Thanks.

My request to access the Llama-2-7b-chat-hf model on Hugging Face still in pending.
In a meanwhile, please ensure that you have followed the instruction below:
Please visit HuggingFace model card, carefully read terms of usage and click accept button in Meta website. You will need to use an access token for downloading model. For more information on access tokens, refer to this section of the documentation.

After my access is approved , I programmatically login using login() in Jupyter Notebook with my authentication token to download Llama-2-7b-chat-hf model.

In the step of saving floating point and compress model variants, I also encountered similar error as you but successfully execute the cell without kernel dead.

At last, I am able to run the demo.

Closing this, I hope previous responses were sufficient to help you proceed. Feel free to reopen and ask additional questions related to this topic, if issue persists kindly share the requested information.


How to use Offline_RL to train this agent?

Hi, thanks for sharing this amazing project!
I have successfully run example.py and example_agent.py. Here are two questions I currently have:

It really confused me that example_agent.py seems only do multiple simulation steps instead of learning to grasp things, according to its code. I'm really new to mujoco and RL, sorry if I have missed some obvious thing here.
How to use the models in Modules.py and Offline_RL to get this agent learning? In train.py it has a load_path ("../xxx.pt"), is it generated from another .py file?

Much appreciate.

Offline RL training should use generate_data.py to generate transactions. However, I encounter a new problem:
No such file or directory :
'../DQN_RESENT_;R_0.001_OPTION_ADAM_H_200_W_STEPS_35000_BUFFER_SIZE_2000_BATCH_SIZE_12_SEED_81_9_7_2020_9_52_weights.pt'

Offline RL training should use generate_data.py to generate transactions. However, I encounter a new problem: No such file or directory : '../DQN_RESENT_;R_0.001_OPTION_ADAM_H_200_W_STEPS_35000_BUFFER_SIZE_2000_BATCH_SIZE_12_SEED_81_9_7_2020_9_52_weights.pt'

reset the LOAD_PATH = None; problem resolved.

When I ran example_agent.py , I met a problem saying " failed to initialize OpenGL", had you met this problem? And how did you solved that? This confuses me for a long time.

When I ran example_agent.py , I met a problem saying " failed to initialize OpenGL", had you met this problem? And how did you solved that? This confuses me for a long time.

I met this problem too. I had looking for solutions for a long time but the problem have not been solved  yet. https://github.com/openai/mujoco-py/issues/187
Maybe you can check this out and find some solutions.


Input border bottom variable doesn't seems to exist

Hi, i noticed that your <Input /> Component has a css variable for its border-bottom color but it seems that this variable hasn't been declared anywhere.
If I include your component on a fresh create-react-app project, Input doesn't show any border-bottom at start but if you declare the variable like this then you will be able to see the border:
input {
  --input-text-bottom-border-color: grey;
}

are you aware about that?
cheers

I do not know if this is relevant, but after few tries, I realized that the original --input-text-bottom-border-color is used/applied only when it is not composed of a color().
So this does not work:
--input-text-bottom-border-color: color(var(--color-text) a(12%));
This works:
--input-text-bottom-border-color: rgba((var(--color-text), 0.12);
where --color-text is in decimal (ex: 240, 240, 210).

I am sorry but the above solution doesn't work for me.
for me, https://github.com/react-toolbox/react-toolbox/blob/dev/components/input/config.css#L11 is not working.
the style of  border-bottom  is null.
(    border-bottom: 1px solid var(--input-text-bottom-border-color); is showing on browser but it doesn't really apply. there is nothing on Computed section. )
So I have to put below in my code.
input {    border-bottom: 1px solid rgba(0,0,0, 0.12)  }
Is there any solution??
I am using meteor, meteor-css-module ....


Alternative to goog.ds?

Admittedly, my project is on a very old version of the closure-library, but when I went back to look at the auto-generated documentation I noticed that that goog.ds module was not there. Further digging lead me to this commit: https://github.com/google/closure-library/commit/49f6e6c90334604641e3da784a541162984382a9
Which then lead me to these release notes that detail the modules removal:
https://github.com/google/closure-library/releases/tag/v20210302
What was the reason for the removal? Is there a suggested alternative? I ask because my project uses the DataManager class extensively to store data and notify on changes.

Is there a reason you can't fork the code into your own project if you are using them?

goog.ds was removed as it was unused within Google. There is no suggested alternative, but John's suggestion of copying the newest version of it into your project is a good one.

Yes I agree that copying the latest version into my project is a viable alternative, but I was more curious as to why it became unused and if there is a compelling reason for me to move away from it as well. I found it very useful.

I'm not particularly familiar with this library myself, but I did a little bit of archaeology.  It seems that the package was relatively popular 10ish years ago, but apparently the uses were replaced by other things, or else just deleted as projects retired.  By a last year, we realized there was only a single user left within Google, so we handed ownership off to them.
It's possible something like redux might be a more modern alternative, but I can't speak to whether it covers all the use cases.  The easiest solution is definitely to just fork it.