Homebridge quits as soon as fibaro motion sensor is being activated

As started/ended in discusson of ticket #21 here a new branch of the same effect:
As soon as I add/activate the fibaro motion sensor , homebridge doesn't start up anymore. (see latest comments thread in #21) .
Activating the fibaros Temperature or tamper alarm device doesnt create any problems. This issue happened suddenly as everything used to work fine before. So not really knowing what's the root change caused this.
Attached is my zwave.me - devices.json file:
devices_json.txt
Thanks for helping.
This is one of the two devices causing my problem:
4    Garagenauge                4.55.00 Fibar Group     Motion Sensor (Multi-Sensor)    2.7     Routing Binary Sensor

Btw: Where can I see what firmware-version is currently running on the fibaro motion sensor?

I clicked on Interview results and then an "version", an got the following results below. If I read it read correctly there is firmware 2.7 running on both devices...
/: None (24.09.2016)
supported: true (24.09.2016)
version: 2 (24.09.2016)
security: false (24.09.2016)
interviewDone: true (24.09.2016)
interviewCounter: 9 (24.09.2016)
ZWLib: 3 (24.09.2016)
ZWProtocolMajor: 3 (24.09.2016)
ZWProtocolMinor: 67 (24.09.2016)
SDK: 4.55.00 (24.09.2016)
applicationMajor: 2 (24.09.2016)
applicationMinor: 7 (24.09.2016)
hardwareVersion: 1 (24.09.2016)
firmwareCount: 1 (24.09.2016)
firmware1: None (24.09.2016)
major: 2 (24.09.2016)
minor: 7 (24.09.2016)
and for the other motion sensor I got:
/: None (04.10.2016)
supported: true (04.10.2016)
version: 2 (04.10.2016)
security: false (04.10.2016)
interviewDone: true (04.10.2016)
interviewCounter: 9 (04.10.2016)
ZWLib: 3 (04.10.2016)
ZWProtocolMajor: 3 (04.10.2016)
ZWProtocolMinor: 67 (04.10.2016)
SDK: 4.55.00 (04.10.2016)
applicationMajor: 2 (04.10.2016)
applicationMinor: 7 (04.10.2016)
hardwareVersion: 1 (04.10.2016)
firmwareCount: 1 (04.10.2016)
firmware1: None (04.10.2016)
major: 2 (04.10.2016)
minor: 7 (04.10.2016)

Was dealing with some further tuning and updating zway automator and smarthome-UI. However, at the end I re-activaed all devices/instances again and simply tried to restart homebridge and it didn't quit anymore. I have really no idea what changed/caused all this.
Maybe my manual dev/stage updates of zway-server made a difference? Don't know.... But works again.

Can you add the following two tags to the "Garagenauge" device in Z-Way and see if it works:
Homebridge.Service.Type:MotionSensor
Homebridge.Characteristic.Type:MotionDetected
? I think I may see what's going on here. But that might work around the problem for you in the meantime and I'd be curious to know if it does.

Oops, had this tab open and just saw your last comment. That's puzzling, but there are a number of explanations. I'll continue looking at this, let me know if it acts up again.

Sure. But since then, it's working fine. No further problems.  (but as mentioned I also made a little change as mentioned in #53 )

@klaasjoerg , could you try out the code in pull request #62? I think it will solve your issues and at least be no worse than your edited version.

Believed fixed in 9d163e6, reopen or create a new issue if not fixed.


Please replace all occurrencies of 'implementation' in Gradle configuration files

Please replace all occurrencies of 'implementation' in Gradle configuration files
WARNING: Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html

+1 s/implementation/compile


CSS and Lang fix

Change ledger to block in Chinese

I don't know.
On Wed, Oct 13, 2021, 2:43 PM frangonzalesjr @.***>
wrote:

What is github
On Wed, 13 Oct 2021, 21:41 tuannguyenphucan1991, @.***>
wrote:

Vào Th 4, 13 thg 10, 2021 lúc 20:40 Manlikenelly @.***>
đã viết:

How are you doing today
On Wed, Oct 13, 2021, 2:38 PM tuannguyenphucan1991 @.***>
wrote:

Hihi
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/pi-apps/pi-explorer/pull/2#issuecomment-942317602
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AWBHV32YHSQESBPCX4SG3ALUGWDUZANCNFSM5F4OZVHA

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/pi-apps/pi-explorer/pull/2#issuecomment-942319631
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AVZFTI6E6KHVV74BP6AKTETUGWD5BANCNFSM5F4OZVHA

.

--
null
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pi-apps/pi-explorer/pull/2#issuecomment-942320535,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AWBKEBY53V4WNW2HC25WN43UGWEAXANCNFSM5F4OZVHA
.
Triage notifications on the go with GitHub Mobile for iOS
<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
<
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pi-apps/pi-explorer/pull/2#issuecomment-942322256,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWBHV34CBXGZTWINIE2SQ4DUGWEIDANCNFSM5F4OZVHA
.

muh ardhy
Pada tanggal Sab, 16 Okt 2021 11.52, Ahmadjakaria @.***>
menulis:

@.**** commented on this pull request.
In src/App.css
https://github.com/pi-apps/pi-explorer/pull/2#discussion_r730199802:

@@ -378,7 +379,7 @@ ul.navbar-nav .divider-vertical {
.glyphicon-search {
height: 20px;
width: 20px;

background-color: #edeef0;

0205miss:helping
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pi-apps/pi-explorer/pull/2#discussion_r730199802, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWBFMB5A5OMMTG6GH7DBIELUHDSHLANCNFSM5F4OZVHA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
null

.....................................
Tuấn Anh would like to stay in touch on LinkedIn.
Tuấn Anh Nguyễn
Tuantau at<PHONE_NUMBER>
Vietnam
View profile https://www.linkedin.com/comm/in/tuấn-anh-nguyễn-8335a4223?trk=eml-guest-invite-pprofile-link-cta&trkEmail=eml-email_m2g_invite_single_01-null-373-null-null-~55umht~kutu4l9u~gs-null-neptune%2Fprofile~vanity.view&lipi=urn%3Ali%3Apage%3Aemail_email_m2g_invite_single_01%3BNKBCK68nSJy1VJJ21yPLyw%3D%3D
Confirm that you know Tuấn Anh https://www.linkedin.com/e/v2?e=-55umht-kutu4l9u-gs&lipi=urn%3Ali%3Apage%3Aemail_email_m2g_invite_single_01%3BNKBCK68nSJy1VJJ21yPLyw%3D%3D&t=suwj&tracking=eml-guest-invite-cta&ek=email_m2g_invite_single_01&validationToken=Ah8GhTVG&invitationId=6855131887497818112
.....................................
Unsubscribe: https://www.linkedin.com/e/v2?e=-55umht-kutu4l9u-gs&t=lun&midToken=AQFmrFVhGEd36Q&ek=email_m2g_invite_single_01&li=381&m=unsub&ts=unsub&loid=AQFR80BnmlfDTgAAAXyJSZm_WbQEB8iP-i08rT1UJOhoXT5H1xDC6Z7PYnLpNkbZrdMouKM4GERLnNYF8kusaZkdREXo9MGSiKQIMngOHBGohphEQ9FQ3ZCY3FmGQEbJhfh3qDswKY73QtdO7ejEzkTRDhiz8bZf8Q&eid=-55umht-kutu4l9u-gs
Help: https://www.linkedin.com/e/v2?e=-55umht-kutu4l9u-gs&lipi=urn%3Ali%3Apage%3Aemail_email_m2g_invite_single_01%3BNKBCK68nSJy1VJJ21yPLyw%3D%3D&a=customerServiceUrl&ek=email_m2g_invite_single_01&li=380&m=footer&ts=help&articleId=67
You are receiving Invitation emails. LinkedIn will use your email address to make suggestions to our members in features like People You May Know.
This email was sent to @.***
© 2021 LinkedIn Ireland Unlimited Company, Wilton Plaza, Wilton Place, Dublin 2. LinkedIn is a registered business name of LinkedIn Ireland Unlimited Company. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn.

On Oct 29, 2021 6:53 AM, "tuannguyenphucan1991" @.***>
wrote:
https://www.linkedin.com/e/v2?e=-55umht-kvbymah9-tu&lipi=urn%3Ali%3Apage%3Aemail_email_second_guest_reminder_03%3B6fuh3p0OQamKry26nulQ5w%3D%3D&t=suwj&ek=email_second_guest_reminder_03&li=11&m=hero&ts=accept_text
https://www.linkedin.com/comm/in/tuấn-anh-nguyễn-8335a4223?trk=eml-email_second_guest_reminder_03-hero-2-prof~name&trkEmail=eml-email_second_guest_reminder_03-hero-2-prof~name-null-~55umht~kvbymah9~tu-null-neptune%2Fprofile~vanity.view&lipi=urn%3Ali%3Apage%3Aemail_email_second_guest_reminder_03%3B6fuh3p0OQamKry26nulQ5w%3D%3D
.....................................
Unsubscribe:
https://www.linkedin.com/e/v2?e=-55umht-kvbymah9-tu&t=lun&midToken=AQFmrFVhGEd36Q&ek=email_second_guest_reminder_03&li=8&m=unsub&ts=unsub&loid=AQH55S1oZrLE5gAAAXzKnD0q5MMlZNEroUyGZoHxKEOwnCNImXDurGghYf5F7ObGe9ZLN81zxkyLvF_rSoP-Egxosb5FkPcJFqRkayQ7y8gxEN5D4HwxUW0syhdpj3K6X4bKPWrZfjey_W4Z-872HcA6BPjQf74ZvV2MFA&eid=-55umht-kvbymah9-tu
Help:
https://www.linkedin.com/e/v2?e=-55umht-kvbymah9-tu&lipi=urn%3Ali%3Apage%3Aemail_email_second_guest_reminder_03%3B6fuh3p0OQamKry26nulQ5w%3D%3D&a=customerServiceUrl&ek=email_second_guest_reminder_03&li=7&m=footer&ts=help&articleId=67
You are receiving Invitation reminder email emails. LinkedIn will use your
email address to make suggestions to our members in features like People
You May Know.
This email was sent to @.***
© 2021 LinkedIn Ireland Unlimited Company, Wilton Plaza, Wilton Place,
Dublin 2. LinkedIn is a registered business name of LinkedIn Ireland
Unlimited Company. LinkedIn and the LinkedIn logo are registered trademarks
of LinkedIn.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pi-apps/pi-explorer/pull/2#issuecomment-954449977, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWFFQ6GIVGA7BX5ZGWLHC4LUJIZHLANCNFSM5F4OZVHA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Too Many scams I will close this fix

Ohk i will connect Tommorow
On Fri, 29 Oct 2021, 07:53 tuannguyenphucan1991, @.***>
wrote:

https://www.linkedin.com/e/v2?e=-55umht-kvbymah9-tu&lipi=urn%3Ali%3Apage%3Aemail_email_second_guest_reminder_03%3B6fuh3p0OQamKry26nulQ5w%3D%3D&t=suwj&ek=email_second_guest_reminder_03&li=11&m=hero&ts=accept_text
https://www.linkedin.com/comm/in/tuấn-anh-nguyễn-8335a4223?trk=eml-email_second_guest_reminder_03-hero-2-prof~name&trkEmail=eml-email_second_guest_reminder_03-hero-2-prof~name-null-~55umht~kvbymah9~tu-null-neptune%2Fprofile~vanity.view&lipi=urn%3Ali%3Apage%3Aemail_email_second_guest_reminder_03%3B6fuh3p0OQamKry26nulQ5w%3D%3D
.....................................
Unsubscribe:
https://www.linkedin.com/e/v2?e=-55umht-kvbymah9-tu&t=lun&midToken=AQFmrFVhGEd36Q&ek=email_second_guest_reminder_03&li=8&m=unsub&ts=unsub&loid=AQH55S1oZrLE5gAAAXzKnD0q5MMlZNEroUyGZoHxKEOwnCNImXDurGghYf5F7ObGe9ZLN81zxkyLvF_rSoP-Egxosb5FkPcJFqRkayQ7y8gxEN5D4HwxUW0syhdpj3K6X4bKPWrZfjey_W4Z-872HcA6BPjQf74ZvV2MFA&eid=-55umht-kvbymah9-tu
Help:
https://www.linkedin.com/e/v2?e=-55umht-kvbymah9-tu&lipi=urn%3Ali%3Apage%3Aemail_email_second_guest_reminder_03%3B6fuh3p0OQamKry26nulQ5w%3D%3D&a=customerServiceUrl&ek=email_second_guest_reminder_03&li=7&m=footer&ts=help&articleId=67
You are receiving Invitation reminder email emails. LinkedIn will use your
email address to make suggestions to our members in features like People
You May Know.
This email was sent to @.***
© 2021 LinkedIn Ireland Unlimited Company, Wilton Plaza, Wilton Place,
Dublin 2. LinkedIn is a registered business name of LinkedIn Ireland
Unlimited Company. LinkedIn and the LinkedIn logo are registered trademarks
of LinkedIn.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pi-apps/pi-explorer/pull/2#issuecomment-954449977,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVZDGSERMXICK2VYMSVSHM3UJIZGNANCNFSM5F4OZVHA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Uncaught TypeError: fs.readFileSync is not a function

When i used by example, throws error .   Uncaught TypeError: fs.readFileSync is not a function
Help!

Which Node.js version are you using?

v10.13

Are you trying to run it on front-end? Because this module works only on back-end.

I am trying to run this in a react-native application and I'm getting this error. Not going to work then?


[SPARK-41674][SQL] Runtime filter should supports multi level shuffle join side as filter creation side

What changes were proposed in this pull request?
Currently, Spark runtime filter supports two scenes.

When the Join itself is a Shuffle Join;
When the join itself is a broadcast join and there is a Shuffle Join under one end of the join.3.

This PR want let runtime filter supports the third scene.
To facilitate understanding, the below SQL is taken as an example.
SELECT *
FROM bf1
    JOIN bf2
    JOIN bf3
    ON bf1.c1 = bf2.c2
        AND bf3.c3 = bf2.c2
WHERE bf2.a2 = 5

The current only add runtime filter(subquery on bf2) on bf1 (the first scene). In fact, we can apply the runtime filter(subquery on bf2) on bf3 too.
There are two tables: lineitem and part. lineitem is big enough and part is small but couldn't be broadcasted.
The query is show below.
SELECT sum(l_extendedprice) / 7.0 AS avg_yearly
FROM (
	SELECT l_quantity, l_extendedprice, p_partkey
	FROM lineitem, part
	WHERE p_partkey = l_partkey
		AND p_brand = 'Brand'
		AND p_container = 'MED BOX'
) a, (
		SELECT l_partkey, 0.2 * avg(l_quantity) AS avg_value
		FROM lineitem
		GROUP BY l_partkey
	) b
WHERE a.p_partkey = b.l_partkey
	AND a.l_quantity < b.avg_value

The plan similar like to the below picture.

After this change, there are two runtime filter injected. Because the two runtime filter are the same, so Spark only submit one job of subquery for runtime filter and the second place could reuse the subquery for runtime filter.
Why are the changes needed?

Improve the supported scene for runtime filter
Reduct the data size for shuffle and improve the performance.

Does this PR introduce any user-facing change?
'No'.
Just update the inner implementation.
How was this patch tested?
New tests.
Micro benchmark.
Because TPC-DS does not cover this scenario. So I created two cases show below.
q1.sql
SELECT *
FROM store_sales
    JOIN item
    JOIN store_returns
    ON store_sales.ss_item_sk = item.i_item_sk
        AND store_returns.sr_item_sk = item.i_item_sk
WHERE item.i_color = 'pale'

q2.sql
SELECT sum(ss_wholesale_cost) / 7.0 AS avg_yearly
FROM store_sales, item
WHERE i_item_sk = ss_item_sk
	AND i_color = 'pale'
	AND ss_quantity < (
		SELECT 0.2 * avg(sr_return_quantity)
		FROM store_returns
		WHERE sr_item_sk = i_item_sk
	)

Before this PR
Java HotSpot(TM) 64-Bit Server VM 1.8.0_311-b11 on Mac OS X 10.16
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
TPCDS Snappy:                             Best Time(ms)   Avg Time(ms)   Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
------------------------------------------------------------------------------------------------------------------------
q1                                               29398          29406          11          1.1         925.1       1.0X
q2                                                3684           3689           7          7.8         127.5       1.0X

After this PR
Java HotSpot(TM) 64-Bit Server VM 1.8.0_311-b11 on Mac OS X 10.16
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
TPCDS Snappy:                             Best Time(ms)   Avg Time(ms)   Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
------------------------------------------------------------------------------------------------------------------------
q1                                               26073          26142          98          1.2         820.4       1.0X
q2                                                3153           3208          78          9.2         109.1       1.0X

ping @somani @cloud-fan

SELECT *
FROM bf1
    JOIN bf2
    JOIN bf3
    ON bf1.c1 = bf2.c2
        AND bf3.c3 = bf2.c2
WHERE bf2.a2 = 5

Can you show the query plan before and after your PR?

ping @cloud-fan Could you have time to take a look?

The failure GA is unrelated to this PR.

thanks, merging to master!

@cloud-fan Thank you for you hard work and review.


PackageName==dev is required

Right now ExtensionName==dev is required to be approved however supporting that turns out to be surprisingly hard if you have changing repository URLs. We should either drop this requirement or provide a script that updates all existing descriptions with new names.
Right now a lot of Pocoo stuff itself does not support ==dev.

Fixed by https://github.com/mitsuhiko/flask/pull/1035


Extremely slow page load with custom docker network on unRAID

Description
When I use a custom docker network for the container fallenbagel/jellyseerr:latest on unRAID, the page loads are extremely slow. If I change to Bridge network, the web app response times are always fast. I observe this slowness on a custom docker network both through reverse proxy and locally via LAN access of <IP>:<web GUI port>.
I figured this was a caching issue, so I kept the custom network active for a week. What I noticed is that with a custom docker network, the dashboard would always take 30s or more to load images/titles and it would still be working on loading as I scrolled. I found myself waiting multiple minutes on numerous occasions for the page to properly load before the web app was usable. However, if I searched for something, the waiting restarted. When I changed back to Bridge network, load times are a few seconds for all the page data and I never feel like I'm waiting as the full page loads in that time and search results are loaded and ready as they should.
Version
1.7.0
Steps to Reproduce

Create custom docker network
set Jellyseerr custom network in unRAID to use the custom network
open web UI and experience the slowness

Screenshots
No response
Logs
No response
Platform
desktop
Device
browser
Operating System
seems to be irrelevant
Browser
Chrome, Safari, Firefox
Additional Context
When I set Network Type: Bridge and add && docker network connect proxy jellyseerr to advanced setting Post Arguments:, I experience the same slowness issues as when I only change the Network Type: <custom docker network>. For creating the docker network, I used the command docker network create <network name> from the unRAID shell.
Code of Conduct

[X] I agree to follow Jellyseerr's Code of Conduct

FYI, this is the recommendation I followed to add a custom docker network while also using Network Type: Bridge: https://www.reddit.com/r/unRAID/comments/q2ojh5/using_multiple_docker_networks_in_unraid/

You need to add a dns block to your unraid template. That is set to <IP_ADDRESS>
the issue is dns.

Perfect, that fixes it. Thanks for the tip!

are you saying you need to set dns always to <IP_ADDRESS> or that we need to block <IP_ADDRESS>? Why does my default dns not work? I tried updating to --restart=unless-stopped --dns <IP_ADDRESS> and it still takes just as long.

This issue is old. And not related. You need to hop onto discord to confirm whether this issue is the http library issue from v2.
This issue is for v1.


Node does not start

System information
Osmosis version:14.0.0
OS & Version: Ubuntu 22.04.1 LTS
Expected behaviour
Node started.
Actual behaviour
Node cannot start
Steps to reproduce the behaviour
Just installed everything via standard installer
Backtrace
9:24PM INF initializing blockchain state from genesis.json
9:24PM INF running initialization for module module=capability
9:24PM INF running initialization for module module=auth
9:24PM INF running initialization for module module=bank
9:24PM INF running initialization for module module=distribution
9:24PM INF running initialization for module module=staking
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x11fc39d]

goroutine 1 [running]:
math/big.(*Int).Sign(...)
	math/big/int.go:38
github.com/cosmos/cosmos-sdk/types.Int.IsNegative(...)
	github.com/cosmos/cosmos-sdk@v0.46.7/types/int.go:194
github.com/cosmos/cosmos-sdk/x/staking/types.validateMinSelfDelegation({0x2058940?, 0x0?})
	github.com/cosmos/cosmos-sdk@v0.46.7/x/staking/types/params.go:254 +0x3d
github.com/cosmos/cosmos-sdk/x/params/types.Subspace.SetParamSet({{0x277c7e0, 0xc00122cc20}, 0xc000015fa0, {0x274f9d8, 0xc00118e310}, {0x274fa28, 0xc00118e440}, {0xc0011f8f18, 0x7, 0x18}, ...}, ...)
	github.com/cosmos/cosmos-sdk@v0.46.7/x/params/types/subspace.go:236 +0x185
github.com/cosmos/cosmos-sdk/x/staking/keeper.Keeper.SetParams(...)
	github.com/cosmos/cosmos-sdk@v0.46.7/x/staking/keeper/params.go:77
github.com/cosmos/cosmos-sdk/x/staking.InitGenesis({{0x27695a8, 0xc0000560e0}, {0x277eda0, 0xc000115980}, {{0x0, 0x0}, {0xc000118170, 0x9}, 0x0, {0x0, ...}, ...}, ...}, ...)
	github.com/cosmos/cosmos-sdk@v0.46.7/x/staking/genesis.go:35 +0x1ec
github.com/cosmos/cosmos-sdk/x/staking.AppModule.InitGenesis({{{0x2782840, 0xc00122cc20}}, {{0x274f9d8, 0xc00118e2b0}, {0x277c7e0, 0xc00122cc20}, {0x276c480, 0xc001282360}, {0x2779640, 0xc000593a20}, ...}, ...}, ...)
	github.com/cosmos/cosmos-sdk@v0.46.7/x/staking/module.go:154 +0x145
github.com/cosmos/cosmos-sdk/types/module.(*Manager).InitGenesis(_, {{0x27695a8, 0xc0000560e0}, {0x277eda0, 0xc000115980}, {{0x0, 0x0}, {0xc000118170, 0x9}, 0x0, ...}, ...}, ...)
	github.com/cosmos/cosmos-sdk@v0.46.7/types/module/module.go:322 +0x429
github.com/osmosis-labs/osmosis/v14/app.(*OsmosisApp).InitChainer(_, {{0x27695a8, 0xc0000560e0}, {0x277eda0, 0xc000115980}, {{0x0, 0x0}, {0xc000118170, 0x9}, 0x0, ...}, ...}, ...)
	github.com/osmosis-labs/osmosis/v14/app/app.go:355 +0x1b5
github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).InitChain(0xc000e57520, {{0x0, 0xed85ec810, 0x0}, {0xc000118170, 0x9}, 0xc000117b80, {0x3897198, 0x0, 0x0}, ...})
	github.com/cosmos/cosmos-sdk@v0.46.7/baseapp/abci.go:85 +0x515
github.com/tendermint/tendermint/abci/client.(*localClient).InitChainSync(0xc000e72c00, {{0x0, 0xed85ec810, 0x0}, {0xc000118170, 0x9}, 0xc000117b80, {0x3897198, 0x0, 0x0}, ...})
	github.com/tendermint/tendermint@v0.34.24/abci/client/local_client.go:272 +0x118
github.com/tendermint/tendermint/proxy.(*appConnConsensus).InitChainSync(0x0?, {{0x0, 0xed85ec810, 0x0}, {0xc000118170, 0x9}, 0xc000117b80, {0x3897198, 0x0, 0x0}, ...})
	github.com/tendermint/tendermint@v0.34.24/proxy/app_conn.go:77 +0x55
github.com/tendermint/tendermint/consensus.(*Handshaker).ReplayBlocks(_, {{{0xb, 0x0}, {0x20a2f9b, 0x7}}, {0xc000118170, 0x9}, 0x1, 0x0, {{0x0, ...}, ...}, ...}, ...)
	github.com/tendermint/tendermint@v0.34.24/consensus/replay.go:319 +0xd78
github.com/tendermint/tendermint/consensus.(*Handshaker).Handshake(0xc0002c3920, {0x277fa20, 0xc00059a1a0})
	github.com/tendermint/tendermint@v0.34.24/consensus/replay.go:268 +0x3d4
github.com/tendermint/tendermint/node.doHandshake({_, _}, {{{0xb, 0x0}, {0x20a2f9b, 0x7}}, {0xc000118170, 0x9}, 0x1, 0x0, ...}, ...)
	github.com/tendermint/tendermint@v0.34.24/node/node.go:329 +0x1b8
github.com/tendermint/tendermint/node.NewNode(0xc000250dc0, {0x27658a0, 0xc00021ae60}, 0xc00122d870, {0x27493a0, 0xc000e6cbe8}, 0x1?, 0x0?, 0xc00122d9d0, {0x276aaa8, ...}, ...)
	github.com/tendermint/tendermint@v0.34.24/node/node.go:777 +0x597
github.com/cosmos/cosmos-sdk/server.startInProcess(_, {{0x0, 0x0, 0x0}, {0x278c818, 0xc0012df590}, {0x0, 0x0}, {0x27718f0, 0xc001249e20}, ...}, ...)
	github.com/cosmos/cosmos-sdk@v0.46.7/server/start.go:264 +0x7bb
github.com/cosmos/cosmos-sdk/server.StartCmd.func2(0xc0012ce000?, {0xc000200ca0?, 0x0?, 0x2?})
	github.com/cosmos/cosmos-sdk@v0.46.7/server/start.go:128 +0x193
github.com/spf13/cobra.(*Command).execute(0xc0012ce000, {0xc000200c80, 0x2, 0x2})
	github.com/spf13/cobra@v1.6.1/command.go:916 +0x862
github.com/spf13/cobra.(*Command).ExecuteC(0xc000e7db00)
	github.com/spf13/cobra@v1.6.1/command.go:1044 +0x3bd
github.com/spf13/cobra.(*Command).Execute(...)
	github.com/spf13/cobra@v1.6.1/command.go:968
github.com/spf13/cobra.(*Command).ExecuteContext(...)
	github.com/spf13/cobra@v1.6.1/command.go:961
github.com/cosmos/cosmos-sdk/server/cmd.Execute(0x0?, {0xc0012521c0, 0xf})
	github.com/cosmos/cosmos-sdk@v0.46.7/server/cmd/execute.go:36 +0x1eb
main.main()
	github.com/osmosis-labs/osmosis/v14/cmd/osmosisd/main.go:16 +0x31

Thanks for the issue @tazhate ! Were you using Osmosis Installer with the node type of Local Osmosis Node? Were there any specific actions that you took after installing and starting the node? (Just trying to replicate the issue you ran into)

@mattverse i'm trying to install full node, only custom option was selected is another path for files. Other options is default/recommended

Can't seem to replicate bug in my local environment, perhaps linking us to genesis.json under ./osmosisd/config might help us better to debug this issue (we only need the staking params part from genesis.json (that looks something like the code block below) since thats where the problem seems to occur
 "staking": {
      "params": {
        "unbonding_time": "1209600s",
        "max_validators": 100,
        "max_entries": 7,
        "historical_entries": 10000,
        "bond_denom": "uosmo",
        "min_commission_rate": "0.050000000000000000"
      },
      "last_total_power": "0",
      "last_validator_powers": [],
      "validators": [],
      "delegations": [],
      "unbonding_delegations": [],
      "redelegations": [],
      "exported": false
    },

So there was a bug in osmosis-installer, the fix just got merged.
Could you retry running the installer?

I am also getting this by installing manually (downloading a binary) and running osmosisd start.

Re-reading, this is definitely the error caused due to the osmosis-installer break in downloading snapshots, which has been fixed.
@jadechip the problem your running into in #4269 is the same error, but for a different reason (wanting something different, rather than an installer bug)
Closing this, please re-open if im wrong!


Update C# implementation

Update to .Net 6.0
Make the API thread-safe
Mirror feature-set of the latest Java implementation

@EricMarcil, it looks like you are the maintainer of this branch. Let me know if there's someone else that I should ping with this.

@EricMarcil: @Aaron-Levan pointed out that we need to update the readme build instructions. Hold off on review/merge until we update that

@ted-miller @Aaron-Levan I'm seeing commits updating to .net 6.0.  The T150 .net version is currently .net core 2.2 which was why we were targetting this version.

We are able to package the .net 6 runtime libraries with the extension executable. David confirmed that this is OK.

@ted-miller I've checked with David, though it is possible to include, we would prefer to keep using Core 2.2 since that is already included in the SP.

Regarding Ted's pull request on the SDK - I don't think we want to update the SDK to .NET 6 until the pendant supports it - and even then if people want to target SP3.0, they should use the SDK that targets .NET Core 2.2.  I can't imagine there is really any functionality in .NET 6 that isn't already in .NET 2 that we need just to call some thrift functions.

@davidljung @EricMarcil
For clarification, are you saying that I'm supposed to develop all my stuff targeting 2.2, or just that you don't want the public SDK to target a version that is different than what is baked into the SP?

@ted-miller - the latter: we'd like the SDK client code to target .NET 2.2 Core for now since that is what is on SP.  We can have client code for later .NET version in a side branch though.  I can't imagine there are any new features in .NET since 2.2 that would make a difference to the SDK classes that just wrap the Thrift generated client API.  We will support newer .NET version 'out of the box' in SP in future (we'll need to maintain container images for both for back compat.)


Discovery document validation is too harsh

Hey thanks for your great library,
I want to use the google oidc API. But they do not prefix all urls with the issuer url, like you assume.
Here's an excerpt from the current discovery document:
 "issuer": "https://accounts.google.com",
 "authorization_endpoint": "https://accounts.google.com/o/oauth2/v2/auth",
 "token_endpoint": "https://www.googleapis.com/oauth2/v4/token",
 "userinfo_endpoint": "https://www.googleapis.com/oauth2/v3/userinfo",
 "revocation_endpoint": "https://accounts.google.com/o/oauth2/revoke",
 "jwks_uri": "https://www.googleapis.com/oauth2/v3/certs",

Would it be possible to soften the validation of the discovery document using, say a config option, or is this not desired?
Anyway, thanks for the library.

@lburgey happened to come across your issue. did you try to set strictDiscoveryDocumentValidation to false?

@michael-aquilina I missed this option while reading the documentation, sorry.


Fix some init priority inconsistencies between pcie and intc_gicv3

Fix this inconsistency found with build time checking:
$ west build -p -b qemu_cortex_a53 samples/drivers/virtualization/ivshmem/doorbell -DCONFIG_CHECK_INIT_                                                             PRIORITIES=y
...
ERROR: /soc/pcie@4010000000 PRE_KERNEL_1 40 < /soc/interrupt-controller@8000000/its@8080000 POST_KERNEL 40

Any chance, are you using/enabled ACPI support for your platform (CONFIG_ACPI)?


[Python] pyarrow MemoryMappedFile.close() does not release memory

Describe the usage question you have. Please include as many useful details as  possible.
path = ""
files = os.listdir(path)
expr = pc.field("l_shipdate") <= datetime.date(1998, 12, 1)

for file in files:
    source = pa.memory_map(path + file)
    table = pa.ipc.RecordBatchFileReader(source).read_all().filter(expr)
    source.close()

I have a simple program to test the memory usage of MemoryMappedFile. In my above test, I'll loop over hundreds of 7GB files. I find the system memory usage continues to increase until exhausted even though I called source.close().
Is there anything wrong with my code or is this a bug?
Thanks for help in advance.
Component(s)
Python

Assuming you aren't saving Table or references to its data somewhere then yes, I would expect it to release the memory.  A memory mapped file should call munmap once the file is closed and all references to the mapped memory are released (e.g. table is destroyed).

@westonpace Hi, thanks for your reply. So you mean my code is correct and this should be a bug, right?

Probably.  What happens if you put a manual gc run in the loop?
import gc
...
for file in files:
    source = pa.memory_map(path + file)
    table = pa.ipc.RecordBatchFileReader(source).read_all().filter(expr)
    source.close()
    gc.collect()

I'm wondering if some dangling python object (e.g. maybe the pa.ipc.RecordBatchReader) is hanging around and keeping references to buffers.

@westonpace I already tried that (code below), but the memory will still be exhausted (watch -n 1 free -mh)
import pyarrow.compute as pc
import pyarrow as pa
import gc

path = ""
files = os.listdir(path)
expr = pc.field("l_shipdate") <= datetime.date(1998, 12, 1)

for file in files:
    source = pa.memory_map(path + file)
    reader = pa.ipc.RecordBatchFileReader(source)
    table = reader.read_all().filter(expr)
    del table
    del reader
    source.close()
    gc.collect()


Allow returning custom Meteor.Error from onBeforeUpload hook

Hi,
I just tried to customize error message sent from the onBeforeUpload hook to match my current architecture design, and it seems that it's only allowed to customize the message sent.
For instance:
onBeforeUpload(file)
{
        if (file.size <= MAX_SIXE)
            return true;

        return "File size is not correct.";
}

// which display the following error in my browser console
{
    details: undefined
    error : 403
    errorType : "Meteor.Error"
    isClientSafe: true
    message: "File size is not correct. [403]"
    reason: "File size is not correct. [403]"
}

My goal here is to be able to send my own Meteor.Error because I use an handwritten module which is able to handle specific error code.
On server, my Logger generates a Meteor.Error based on a code and throws it.
On client, my Logger catches the generated Meteor.Error and, (if the code is recognized!) displays it in a an alert box in my UI.
The problem here is that if I execute the code below, I don't have access to my custom error message and code, and thus my error box is not displayed.
onBeforeUpload(file)
    {
        if (file.size <= AVATAR_MAX_SIZE && Validator.isImage(file))
            return true;

        Logger.error(ErrorCode.IMPROPER_AVATAR);
    },

// Output
{
    details: undefined
    error : 403 // This code doesn't exist for my Logger & this is not the Logger specified code
    errorType : "Meteor.Error"
    isClientSafe: true
    message: "collection.onBeforeUpload() returned false [403]" // this is not my custom message
    reason: "collection.onBeforeUpload() returned false" // this is not my custom message
}

This is not actually a bug, but more an improvement suggestion for returning custom Meteor.Error in the onBeforeUpload hook.
I suppose that the current behavior must be :

If the onBeforeUpload return true, then continue upload
If it returns anything else, check if string is provided and pass it to an internally generated Meteor.Error (if no string is passed, just return default Meteor.Error)

Is it possible to check if a Meteor.Error has already been thrown and rethrowing it if it's the case ?
This would allow error customization for whoever wants a specific error handling usage.

Hello @axelvaindal ,
Sorry for delay, somehow I've missed this ticket.
Have you tried to catch error in onError or onEnd event in .insert() method?

Hi @dr-dimitru, no worries 🙂.
Actually, it seems catching is not necessary.
My quoted code is actually working exactly as it should.
Subtil difference between working and not working code is here :
// NOT WORKING
if (file.size > AVATAR_MAX_SIZE || Validator.isImage(file))
            return Logger.error(ErrorCode.IMPROPER_AVATAR);

// WORKING
if (file.size > AVATAR_MAX_SIZE || Validator.isImage(file))
            Logger.error(ErrorCode.IMPROPER_AVATAR);

This is actually expected behavior since Logger.error throws directly the Meteor error without returning it (i.e return is undefined). This is why my code wasn't working and my personal issue is resolved.
However, perhaps this may be interesting for some other cases.
If we return the Meteor.Error directly (without throwing it), previous behavior is confirmed.
I tried to catch error using :
onError(error)
    {
        try {

        } catch (e) {
            console.log(e);
        }
    }

but I'm not sure this was what you wanted me to test.
The real question here is : what if the user want to prepare a Meteor.Error by himself and let your package throws it ?
I think this is unlikely, considering I actually throws it myself because I have a personal module for this (and I suppose other people as well), but this is worth mentioning I couldn't catch the error properly in this case.
Should I try anything else to help dig deeper in this particular behavior or this is irrelevant and we should consider this issue closed ?

I meant "catch" in spoken form:
onError(error) {
       // do what you need with an error
}

The real question here is : what if the user want to prepare a Meteor.Error by himself and let your package throws it ?

Package wouldn't throw an error inside onBeforeUpload, error will be redirected into onError hook, and then into onEnd.
Closing it for now.

Well, yeah completely tried that.
If the onBeforeUpload return anything else than true or string, the default error is in the error var.
Thus, if I do following code, everything works fine:
// in collection design
onBeforeUpload()
{
    throw new Meteor.error(code, message);
}

// in upload manager
onError(error)
{
    console.log(error); // error is the correct error
    Logger.displayError(error); // Working well, everything is fine for me.
}

But if I do following code, this is not working :
// in collection design
onBeforeUpload()
{
    return new Meteor.error(code, message);
}
// in upload manager
onError(error)
{
    console.log(error); // error is the default error (i.e [403] ... returned false ...)
    Logger.displayError(error); // Not working cause error.err & err.reason are not as expected
}

Based on what you just said :

Package wouldn't throw an error inside onBeforeUpload

Should I update my onBeforeUpload code and not use throw Meteor.error in this context ? 😕

Should I update my onBeforeUpload code and not use throw Meteor.error in this context ? 😕

Right, you can return "IMPROPER_AVATAR":
// in collection design
onBeforeUpload()
{
    return message;
}
// in upload manager
onError(error)
{
    console.log(error);
    Logger.displayError(error);
}

Or in your case:
// in collection design
onBeforeUpload()
{
    return 'IMPROPER_AVATAR';
}
// in upload manager
onError(error)
{
    console.log(error);
    Logger.displayError(ErrorCode[error]);
}

Well, that is not how Logger was meant to be 😕.
It is supposed to use a Meteor.Error because this is also what I use in methods and subscription, and because message/criticality/type of error are fetched based on code and stored server side as a SystemError (which we can track for statistics usage, issue tracking and more) thanks to Logger.error.
Logger.displayError is a function made to simply store the generated Meteor.error into a client side collection for UX only. This is not really convenient to fetch error message twice as this could be done once & only once (when generating the Meteor.error in the first place).
What is the reason I should not throw a Meteor.error from onBeforeUpdate ? 🙂

It is supposed to use a Meteor.Error

I guess it can be done this way:
// in collection design
onBeforeUpload()
{
    return 'IMPROPER_AVATAR';
}
// in upload manager
onError(error)
{
    console.log(error);
    Logger.displayError(new Meteor.Error(code, ErrorCode[error]));
}

What is the reason I should not throw a Meteor.error from onBeforeUpdate ? 🙂

No need to interrupt main thread, or catch exception in other place. From the docs:

If no catch block exists among caller functions, the program will terminate.

Alright, will be doing it this way then.
Thanks for your answers !


Missing VSTs cause crash

When loading a file with a VST that can't be located, sometimes the program will crash. It should still load the MIDI data and as many instances as possible.

Caused by wires referencing missing instances


Line 104

i got a this problem,can you help me?

File "proxy_check.py", line 104
"http": f"{type1}://"+proxy,
^
SyntaxError: invalid syntax

Thanks <3

What's python version you're using? You need python 3.6+ ... probably it's a f string error you're seeing.


Ability to disable forler's terminal in multi-root workspace

I would like to be able to tell. Witch folder is to be listed in the "New Terminal" button. Even better would be to be able to tell what at what location will the terminal open, instead of the rather confusing default.

This is how I imagine it could be implemented. A simple yet effective addition.
{
	"folders": [
		{
			"name": "Server",
			/** Added - This would not show up in "New Terminal" */
			"terminal": "disabled",
			"path": "./apps/server",
		},
		{
			"name": "Helpers",
			/** Added - This is the default value, this is also the current behaviour
			 * It means that this path will show up in the list of possible terminals when clicking "New Terminal"
			 */
			"terminal": "allow",
			"path": "./libs/helpers",
		},
		{
			"name": "Groundwork",
			/** Added - This terminal would be launched when workspace is opened */
			"terminal": "default",
			"path": "./",
		},
	],
	"settings": {
		"files.exclude": {
			// I show this just to claryfi my set-up
			/** Hide `apps` & `libs` in `Groundwork` */
			"apps": true,
			"libs": true,
	},
}

Not duplicit, at least to my eye...


Show image thumbnails in spelunker

It's the job of the extractor to copy the images uploaded to the tms-extractor server to S3 and generate various image sizes. The spelunker should then point to those images (if they exist).

This is done now -- you can see an example here: https://collections.mplus.org.hk/collection/objects/1814
The same image is not showing up on staging, but I think it's just because staging needs the TMS extract run.


#169 Doc comment on bench id uniqueness

Clarification on uniqueness & matching of bench IDs

Thanks for contributing!

Please rebase onto main and there's a small spelling error
Issues found:
./iai-callgrind-macros/src/lib.rs:633:5 - Unknown word (aparameter)
CSpell: Files checked: 241, Issues found: 1 in 1 file.
error: Recipe `check-spelling` failed on line 77 with exit code 1


Support mocking client-only fetch

I encountered an issue with GLOBAL using fetch-mock to test a React app. It is the same error as the one posted here: http://stackoverflow.com/questions/35633044/fetch-mock-global-is-not-defined. I used their suggested workaround and it worked for my use-case.
Something as simple as replacing global here https://github.com/wheresrhys/fetch-mock/blob/master/src/server.js#L11 with GLOBAL || global would allow this to work on client as well as server.

@samzhang111, Can you share the code where you have defined the global variable? Here is what, I've done but, none of my test cases pass. Not sure what's happening.
/* eslint-env jasmine */
jasmine.VERBOSE = true
global.GLOBAL = global

And, I have included the fetch-mock and isomorphic-fetch in the unmockedModulePathPatterns

I am having a similar issue, using fetch-mock to test React app. Getting a window is not defined error (theGlobal: window, )
I use webpack and I load fetch globally using webpack's providePlugin.

new webpack.ProvidePlugin({
			// to figure out how to code webpack module bundler, see: http://forum.shakacode.com/t/understanding-the-webpack-module-bundler/336
      'fetch': 'imports?this=>global!exports?global.fetch!isomorphic-fetch'
    }),

Do I need to do something similar for fetch-mock? What's the best way to get fetch-mock going?

What's your build process exactly? webpack should respect this https://github.com/wheresrhys/fetch-mock/blob/master/package.json#L6

I will probably change GLOBAL to global as that's what nodejs documents https://nodejs.org/api/globals.html#globals_global. Although arguably react/webpack should support both because both of them are defined in nodejs

This is now fixed, though I would still be interested in seeing code samples of what build process and architecture means the server side js is being included on the client side. Are you developing for React Native?

@wheresrhys , I'm using webpack + ES6 loaders + JEST. If I use es6 import for isomorphic-fetch and fetch-mock, nothing works. All the test cases fail even after setting the GLOBAL variable. However, if I use require for both packages, test case runs. But again, the expect function is not behaving properly inside the .then() handler. For example:
    const urlToTest = 'http://localhost:3000/api/v1/users';
    fetchMock.mock(urlToTest, 'GET',  { test_id: '123', test_name: 'test_name' });
    return sendRequest(urlToTest).then(() => {
      expect(fetchMock.called(urlToTest)).toBeFalsy();
      fetchMock.restore();
     });

expect should fail actually, but it passes. I'm trying to debug it and find out what's happening to jasmine's expect function.

Are you using fetch-mock 4.3.1?

yes @wheresrhys

@wheresrhys, Test cases are running fine now (used pit instead of it when writing test cases) when using require.  I found that if we use ES6 import, the fetch function is not becoming global. Can you please confirm if that's true?

Try this https://www.npmjs.com/package/fetch-everywhere with import instead of isomorphic fetch. Let me know if it works and I'll add to the troubleshooting part of the README.
I suspect that Jest might be making a mistake in how it works with babel. If you could create a repo with a reduced test case I'll try to verify that that is this case.


ScalaJSModule: Deprecate fastOpt and fullOpt

This should be merged after #2324, which targets the 0.10.x branch


Class property inference from constructor does not work with destructuring assignment in some cases

Bug Report

🔎 Search Terms

class property inference from constructor, destructuring assignment
⏯ Playground Link

Playground link with relevant code
💻 Code

function generic_function<T>() {
  return {str: 'str'}
}
class NotWork_with_generic_function {
  str // <- 'str' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.ts(7022)
  constructor() {
    ;({str: this.str} = generic_function())
  }
}

function normal_function() {
  return {str: 'str'}
}
class Work_but_with_normal_function {
  str
  constructor() {
    ;({str: this.str} = normal_function())
  }
}

class NotWork_with_object_literal {
  str // <- 'str' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.ts(7022)
  constructor() {
    ;({str: this.str} = {str: 'str'})
  }
}

class Work_but_with_variable {
  str
  constructor() {
    const tmp = {str: 'str'}
    ;({str: this.str} = tmp)
  }
}

Tested with versions (>= v4.0.5)

 ;({str: this.str} = {str: 'str'})
// The above should equal the following, where is the circularity?
this.str = {str: 'str'}.str


Fix typo

Please follow this template, if applicable.
Description
fix typo: Inalid -> Invalid
Additional Notes
Thanks for creating eww :heart:

Thanks for your PR <3


Syntastic making files everytime a file is opened

This isn't much of an issue but rather my lack of knowledge. In my vimrc, I have check_on_open = 1 with syntastic_c_checkers set to ['gcc' , 'make']. Is there a way to stop syntastic from making my first target within makefile everytime I open a file?

The make checker runs make -sk, thus no, it isn't possible.


Unable to request recover on Saturdays

Hello,
We're currently trying Gadael and we are stuck by this issue.
When a user creates a new recover request, Saturdays are not available (and Sundays are not available right away too).
Here's a screenshot of the problem:

You can see multiple problems on this image:

Users can't request recover in the past. You can't always plan your extra time, and can need to declare overtime after it happened

But users can request overtime on Wednesdays...?!

Users are unable to request overtime on Saturdays
Users are unable to request overtime on Sundays until 11/24 (not shown on screenshot)

Here are the related configuration:

thanks for your report, there is a problem with select-able periods longer than one day, i am working on a solution

this commit is a fix for the week-end bug https://github.com/gadael/gadael/commit/756cac1b1a060d419fd4545b2394a8056e7d6b3a
there is still a problem with unavailable random days, i saw this on a sunday

fixed this in last version of https://github.com/polo2ro/teleperiod , version updated in dependencies


Feat: add support for overloaded parameterized tests

Fixes #1253

I haven't reviewed all code, I have only ensured the overloads are handled correctly for DataRow and DynamicData. For the screenshot you have, this is the default display name for a method if no display name is provided so I think it's fine (at least for the context of this PR).


How to write build config for a dart package?

I have sub-packages for my primary flutter project, how can I write the build.yaml for each package?
Could you please explain how would we implement this?
Directory Structure:

package/

lib/

package.dart

src/

entity/

entity1.dart

entity2.dart

entity3.dart

Thanks :)

Hi. Normally for a package you can set up the build file as you would for other projects. You can then publish the generated file together with your code.
Or do you have any special use case?

Hello @schultek  👋 , thanks for the response, I took a deep dive into the codebase and read your two articles, great work man 👍
Questions:
1- I have a project that consists of multiple packages, inside common models folder. My problem with per package generation is that I have to create a file that imports all the models in that package and I set the entry file in the build.yaml to it so it can check from those imported files which are annotated. It doesn't look for all the annotated files without being referenced with an import or export in a single entry file.
If I have multiple directories with models that want to be generated, I don't like the idea of having multiple "Mapper" classes for each entry. I do dig more the idea of how injectable handle the generation where it extracts info from multiple sources and create one single source of truth file (https://pub.dev/packages/merging_builder).
2- We have a case where we pass JsonConverter instances for some abstract data fetching mechanism in our source code. I can't reuse the generated "_mappers" and I can't instantiate "SomeModelMapper" because it's private.
3- I would like the idea of merging multiple "Mapper"s and maybe have the option to name them with different names according to the needed scope, like AuthMapper, CoreMapper, etc and merge them in the client project into a single Mapper.
Thanks a lot :)

Interesting use-case. I like the idea of merging multiple Mappers into one and giving each one a separate name according to its scope.
(1) I don't think this is doable without mayor changes, but you can just do a 'entities' library which imports all entities in that folder, and then only import that library into your other packages, no?
(2) So would a method to get an instance of some specific mapper be sufficient? Something like Mapper.of<T>() which returns an instance of SomeModelMapper for T = SomeModel.
(3) As said, I like this. I'm thinking of something like var m1 = Mapper1.getAll() which would basically return _mappers, and then a Mapper2.useAll(m1) to merge Mapper1 into Mapper2

Thanks for your response,
(1):
In our team have some experience with merged generation, with the maintainer of "auto_route" and "injectable" onboard.
is it ok to have major contributions to this package?
(2)-(3): I love that
Thanks a lot

Go for it. I'm happy to receive contributions for this.

Cool 😎
What do you suggest for communication about certain decisions? Discord or a separate issue?
I have been tinkering with this for hours now and I already have some insights that you might find interesting.
@schultek

Yes, you can open a new issue for this.

@erabti I published version 0.8.4 with (2)/(3) for you to try out. I will add some documentation later.


New package: AstroForceModels v1.0.0-DEV

Registering package: AstroForceModels
Repository: https://github.com/jmurphy6895/AstroForceModels.jl
Created by: @jmurphy6895
Version: v1.0.0-DEV
Commit: 98a7133b1eca78a8f044ec916a8601c1203c4111
Git reference: v0.1.0
Description: Force Models for Astrodynamics Trajectory Modelling

[noblock]
Hi @jmurphy6895, I came across this and wanted to share that I am currently working on a similar implementation that incorporates multi-threading and automatic differentiation (AD) compatibility: AstroModels.jl.
Would you be interested in collaborating on this? I think combining our efforts could result in a low-effort maximum result solution also for the package maintenance.

[noblock]

Would you be interested in collaborating on this? I think combining our efforts could result in a low-effort maximum result solution also for the package maintenance.

Hey @andreapasquale94 I think that's a great idea! This PR is probably not the best place to discuss, I've sent you a message on the Julia Slack so that we can start talking the best ways to coordinate.


Read access violation at amoeba.h line 289

I found another problem about a minute ago.
It's necessary to add to test.c after the code:
        // Ycur = Yprev_row + 10
        pC = am_newconstraint(pSolver, AM_REQUIRED);
        am_addterm(pC, arrY[nCurrentRowFirstPointIndex + nPoint], 1.0);
        am_setrelation(pC, AM_EQUAL);
        am_addterm(pC, arrY[nCurrentRowFirstPointIndex - 1], 1.0);
        am_addconstant(pC, 10.0);
        nResult = am_add(pC);
        assert(nResult == AM_OK);

These lines:
// Add these to test.c line 282
pC = am_newconstraint(pSolver, AM_REQUIRED);
am_addterm(pC, arrX[nCurrentRowFirstPointIndex + nPoint], 1.0);
am_setrelation(pC, AM_GREATEQUAL);
am_addconstant(pC, 0.0);
nResult = am_add(pC);
assert(nResult == AM_OK);
And it causes an access violation at amoeba.h line 289
P.S. I also found some strange situations when X-variables are became negative but still testing these ones.

I have noticed this and fix it (I hope so).
it because I moved the nullptr test into am_remove(), but not implement correctly.
you could try it out with the latest commit.
Sorry for my WIP state :(

I just tried last commit, and the problem is still here.

Sorry for my WIP state :(

No problem!
"Progress" is always good. :-)

But I add test to line 282, I don't find access violation :-(

I prepared smallest possible test showing this problem:
test2.txt
It crashes in 100% of cases (tested under Windows 7 x64, compiled in both x86 and x64).
Also in x64 there are 4 warnings on compile:
amoeba.h(361): warning C4244: '=': conversion from '__int64' to 'int', possible loss of data
amoeba.h(363): warning C4244: '+=': conversion from '__int64' to 'int', possible loss of data
amoeba.h(366): warning C4244: '=': conversion from '__int64' to 'int', possible loss of data
amoeba.h(368): warning C4244: '=': conversion from '__int64' to 'int', possible loss of data

okay, thanks for reporting it, I have found the issue and fix the warnings also, you can try it out :-)

it seems that you are using C++, I'm planing to write a C++11 wrapper for this library, so if you like it, you can raise a new issue to follow the work on C++ wrapper.

I tested new version.
It doesn't more crash on am_add(...) but it now generates "assertion failed" on
am_delsolver() call:
In am_freepool() the line
assert(pool->count == 0);
causes "assertion failed" as in my case the pool->count equals to 1011
Regarding C++11 wrapper: I don't know still because to use your library I must absolutely be sure that even on bad/incomplete data it never crashes.
So if you plan to make it better I'll continue to test it. :-)

Yes, I will make it better.
Very sorry for the assertion failed/crash for the library. because I can not find good test cases. I will make a travis-cl config and a coverage test to make sure it won't crash on any data.
maybe you can help adding the data case, with travis it might stable than currently.

for this assertion failed:  this assertions failed means "you will have memory leak when you delete solver", you may have objects new-ed but not deleted. I will check whether is the internal issue or the mis-usage, and if it's a mis-usage, I will change the interface to avoid it.

I have checked and revert the changes from last commit. I used to add these check before, and removed it after found it will fail because hashtable still hold pool memories. coding in late night is not good :(
I will add travis immediately when I have time. I will fix all crash you find.  the amoeba itself not easy crash, most of them are unchecked null pointer API call or un-needed assertion failure. but I will add test to check the coverage of this project when it become stable.
and I must against the desire to change the code before my brain T_T

Regarding the assertions you wrote:

this assertions failed means "you will have memory leak when you delete solver",
you may have objects new-ed but not deleted
Yes, I understood.

maybe you can help adding the data case, with travis it might stable than currently.
OK.
I added support of auto-tests (via the 'Catch').

I have add travis auto test and code coverage test. I will work to coverage 100%, in this way the crash will never occurs. you could use 'passing' commit and treat it stable.

Ok, thanks.

@hsa-online any news?

@hsa-online any news?

I wrote my own implementation of Cassowary so I stopped to test your library.


Master p

please remove
https://github.com/sonyxperiadev/macaddrsetup/pull/24/commits/72ffe73f062e5d10fb14bd786aa7e352b52d7792
I updated all android versions stating from Android 6 to use the new path

please rebase

cherrypicked

https://github.com/sonyxperiadev/device-sony-common/blob/l-mr1/common.mk#L240

it is fixed
thanks for the note


Report progress on Dismissible update callback

This PR adds a progress parameter to the Dismissible onUpdate callback.
The value represents how far the dismissible child has been dragged in its parent container as a ratio value between 0.0 and 1.0, which can be useful to e.g. fade elements in sync with the gesture.
This implementation also correctly reports the position during the return animation when the dismiss is unsuccessful.
This PR partly solves #21230 (3rd. point) and closes #74582
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making.
[x] All existing and new tests are passing.

Thanks. I'm sorry it took so long, I didn't notice that the tests were failing since last week.

I'm kind of new to this, is there anything else required from my side?

Nope sorry, we just didn't notice it was ready to land! My bad!


⚠ PrivateHD has degraded performance

In f9b3f92, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1946 ms

Resolved: PrivateHD performance has improved in 312025b.


How to set date format from default YYYY-MM-DD to DD-MM-YYYY ?

In package Flutter Cupertino Date Picker we can set dateformat using String dateFormat when initialize the package,
So in this package how to set date format?
because this default is YYYY-MM-DD, what i want is DD-MM-YYYY,
i have read documentation but cant found how to set this.
Its posible or not? i used en locale. thanks

I would also like to show dd-mm-yyyy but don't know how to customize that in the custom class. Can you add this feature for localType.da or show us?
Thanks

You can create a custom picker to do this. Here is one.

Here is an example #93 ，but Modify format date #21    issues  not solved. in 1.5.0

Any changes here?
Tried to create a CustomModel, but have the same problem as others:
Switching from a month with less 31 days to a month with 31 days does update the list only if I scroll to 31 (although 31 is not shown before).

You can create a Fork and edit format in file <lib/src/date_format.dart>


Keyless verification with Bring Your Own Public Key Infrastructure (BYOPKI)

Question
Hey folks, I'm working on a BYOPKI verification example in: https://github.com/saschagrunert/byopki/blob/main/run
It does:

Generate a CA, intermediate CA and leaf certificate using cfssl:
https://github.com/saschagrunert/byopki/blob/ad923ea/run#L23-L164
Start a container registry and build+push a demo image:
https://github.com/saschagrunert/byopki/blob/ad923ea/run#L166-L174
Use cosign generate and cosign attach to sign the image:
https://github.com/saschagrunert/byopki/blob/ad923ea/run#L178-L189
Verify the image using cosign verify … --key, which works:
https://github.com/saschagrunert/byopki/blob/ad923ea/run#L191-L195
Attempts a keyless verification using `cosign verify … --cert-chain, which fails:
https://github.com/saschagrunert/byopki/blob/ad923ea/run#L197-L203

With:
> Verify signature keyless
WARNING: Skipping tlog verification is an insecure practice that lacks of transparency and auditability verification for the signature.
Error: no matching signatures: cert verification failed: x509: certificate specifies an incompatible key usage. Check your TUF root (see cosign initialize) or set a custom root with env var SIGSTORE_ROOT_FILE
main.go:69: error during command execution: no matching signatures: cert verification failed: x509: certificate specifies an incompatible key usage. Check your TUF root (see cosign initialize) or set a custom root with env var SIGSTORE_ROOT_FILE

Setting SIGSTORE_ROOT_FILE to the CA or full chain does not help either. Am I missing something?
I'm using cosign v2.2.4 right now.

You've specified no extended key usages using cfssl, it should be "code signing" for the leaf certificate. Ref: https://github.com/sigstore/cosign/blob/121115774e8c662648165f2924e7354292365ae8/pkg/cosign/verify.go#L1340
Your key usages are also overspecified, the root only needs "cert sign" (and possibly "crl sign" if you're issuing CRLs), same with the intermediate. The intermediate also must specify "code signing" per EKU chaining.

We have this tutorial which outlines how it can be done: https://linuxera.org/signing-verifying-container-images-with-cosign-own-pki/


feat(specs): make environment specs managed attributes

closes #98

Implements private _*_spec properties on the Environment class. The properties are accessed through *_spec  managed attributes implemented with the @property decorator. Properties are initialized with _make_*_spec() methods during Environment initialization.
Implements generic ActionSpec type on the Environment class in order to statically type the action_spec attribute.
Updates all environments to conform with changes to Environment class.
Implements unit tests to ensure Environment specs can be accessed from a jitted function.
Changes all references to *_spec() method to *_spec attribute.

Edit:
now also closes #221

Implements generic Observation type on Environment
Implements generic types on Wrapper classes, so that Wrappers will inherit type hints from the Environments they wrap

Sorry for the radio silence, I still want to get this in! What do you think about using cached_properties instead of properties as the spec should never change?

I think cached_properties should work. The only issue I foresee is you might have to access the properties in the __init__ method to ensure the arrays are initialized outside of a jitted function.

I think cached_properties should work. The only issue I foresee is you might have to access the properties in the __init__ method to ensure the arrays are initialized outside of a jitted function.

True, but we know what the cached properties are, so we could call them in the base env classes init?

Also just a heads up, we're making a push to get sliding tile puzzle and flatpack envs merged before the ICLR camera ready deadline (about a week). Once this is done we'll get to this PR :smile:

Thanks for the heads up. I changed all of the environments to use cached_property. I think it is more succinct than my original implementation. Thank you for the suggestion.

I've implemented the changes for the SlidingTilePuzzle and cleaned up the last references to action_spec() in the docs. That should be all the environments.


Discrete FPID Block in Simulink

Hi,
I was using Discrete Fractional PID block in my simulink model for controlling a plant. Once I used the pre given values then results are OK. But when I use GA algorithm to optimize it's parameters then Discrete Fractional PID block doesn't work as per expectation and it gives different result even on the previous values.
When I delete the block and use new block it again give correct values and this loop continues....
Please have a look into this issue. I can even show you the problem through skype or some other mean.
Looking forward to hear from you.
With Regards
Sachin Sharma

No comments for more than a year - closing.


Hiding flashcards

Added possibility to hiding flashcards.

I think that this solution is bad, because we are forced to check the status of the flashcard every time we are launching a test or anything else. I think we should create a separate table for hidden decks, and separate (the existing one) for visible ones

It's not that bad. Yes is a lot of work. And for lazy people like me I'd create some nice factory method/builder createHiddenFlashcard along with createFlashcard. To DAO I will add some new well named method to for increase readability, too. Maybe DAO could be separate? Who knows? :)
But is that PR finished? I mean, does it meet acceptance criteria?

I checked AC - all logic is on client side - for us is hust another attribute. Thanks!


Need explanation for Glyph output txt

I assume the image coordinates are from (0, 0) (top left) -> (1, 1) (bottom right)
My questions:

What is the difference between:

Width and Texture Width
Height and Texture Height
Horizontal Bearing X and Vertical Bearing X
Horizontal Bearing Y and Vertical Bearing Y

What even are:

Horizontal/Vertical Bearing X/Y
Horizontal/Vertical Advance

From what I've understood, Texture Width/Height is the size of the glyph on the texture, in a (0,0) -> (1,1) coordinate space, and Texture Coord X/Y is the position of the glyph on this same texture.
But what's the deal with the other width/height, and the difference between Horizontal/Vertical advance and the Texture Coords ?

Hi Poucy113,
I have updated the README that should contain enough material to get you started.
Any suggestions or pull requests for improvements are welcome.
As for the font metrics in general, you can take a look at the following.
https://freetype.org/freetype2/docs/glyphs/glyphs-3.html
An extra complication for the signed distance fonts is that you have to expand the glyph bounding boxes to accommodate the spread. Hopefully it is clear in the latest README.


Link to walkthrough is broken

Expected Behaviour
Clicking the walkthrough link in the Adobe I/O integration paragraph takes me to the correct page.
Actual Behaviour
Clicking the link takes me to a 404 error page.

@adobe export issue to Jira project PDCL


ENH: explain why aps method have coverage higher thna 1-alpha

Fixes #236

Codecov Report
Patch and project coverage have no change.

Comparison is base (88f0bc6) 99.90% compared to head (69ad566) 99.90%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #278   +/-   ##
=======================================
  Coverage   99.90%   99.90%
=======================================
  Files          28       28
  Lines        3269     3269
  Branches      343      343
=======================================
  Hits         3266     3266
  Misses          3        3

Impacted Files
Coverage Δ

mapie/classification.py
100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


parse apiserver prefix from client config host spec

This allows apiserver to be hosted behind a proxy w/ proxypass-like rules that translate URLs. For example, from a client perspective the apiserver might live http://some-mesosphere-dcos-cluster/service/kubernetes/api and we'd want kubectl to be able to access that server. Mesosphere DCOS would translate /service/kubernetes/api --> /api by the time the request hits the apiserver.
This PR allows for a user to:
:; export KUBERNETES_MASTER=http://some-mesosphere-dcos-cluster/service/kubernetes/api

.. and then use kubectl to interact with it.
/cc @guenter @davidopp @bgrant0607

xref https://github.com/mesosphere/kubernetes-mesos/issues/320

@lavalamp could you take a look at this PR? It's very small but I don't understand how the code it's modifying works well enough to review it.
(I see @bgrant0607 assigned it to @jlowdermilk but I think it would be good if @lavalamp could take a look at it.)

writing up a unit test for this

@deads2k can you review this - I don't know if this will break the other assumptions around prefix in other places.

The prefix part is probably ok, but the logic around rebuilding the URL seems a little strange.  Why not simply save the prefix, clear the path and re-stringify it?

Thanks for the suggestion. Done
On Thu, Jun 4, 2015 at 11:26 AM, David Eads<EMAIL_ADDRESS>wrote:

The prefix part is probably ok, but the logic around rebuilding the URL
seems a little strange. Why not simply save the prefix, clear the path
and re-stringify it?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/9171#issuecomment-108934806
.

This looks OK to me, but @jlowdermilk can say whether there's other parts of config file parsing that also need the change. I find the config file parsing very complex and hard to reason about. Hopefully we can simplify it after 1.0.

This looks reasonable to me. @deads2k, any remaining concerns?

lgtm

would really like to have this for 1.0, would make k8s on mesos much easier to use

FWIW, while not directly related to changes in #8882 we do need this change for a good user experience running k8s on mesosphere dcos.

lgtm

thanks!
On Mon, Jun 8, 2015 at 1:18 PM, krousey<EMAIL_ADDRESS>wrote:

Merged #9171 https://github.com/GoogleCloudPlatform/kubernetes/pull/9171
.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/9171#event-325504017
.


Priority ethereum connection snags

Some snags
Cant connect multiple times
When you first land on the page or clear local storage the connection flow works great.
But if you then disconnect and try to reconnect it doesnt work.
You just go from here:

To here:

Repeatedly....
Open wallet is slow
When you're in here

and you select "Open wallet" for the first time it takes a couple of seconds.
After that its very snappy ... it seems to be limited to the first time you open it.
Having reproduced it a few times its not really that bad ... its probably fine ... but it is a little slow.
Delete wallet flow
When connected via ethereum wallet I still get an option to delete wallet which doesnt make sense since as soon as I disconnect all knowledge of my wallet is lost from the browser anyway, it is not relevant.

Tasks

[ ]
[ ]

Additional details / background info

All tested and working


Pyupgrade 3.6: Update syntax with Python 3.6+ features

Updated Python code with Python 3.6+ features:

utf-8 encoding is now the default (PEP 3120, Python 3.0+)
Replace list comprehensions by Generator Expressions (PEP 289, Python 2.4+)
Replace yield loop by yield from (PEP 380, Python 3.3+)
Replace the IOError alias by OSError (PEP 3151, Python 3.3+)
Remove the default subclass (object) when defining a class
Define sets with curly braces {} instead of set()
Remove "r" parameter from open function, which is default

Used pyupgrade 2.29.1 with --py36-plus as starting point for this PR.

Thanks for the suggestions, I implemented them, squashed the commits, rebased and signed it.

Can you fix the failing tests?

I think replacing the list() by [] as @GregorKikelj suggested didn't play well with the lambda, so I reverted it. I did this a bit to quick, and accidentally reset the whole branch. Luckily git reflow is a thing and I recovered it. I couldn't get this PR reopened though, so it's now #23305.
(note to self: be really careful touching git reset --hard)


Tool part station

Taken from the Forgero Discord:
It'd be nice to have a tool part station, listing all possible tool parts and being able to autofill schematics from your inventory or a connected chest, instead of using the crafting table (could be implemented as a configurable optional feature, I think the tool part station should be enabled by default in that case though)
Would make crafting tool parts a lot more frictionless.

I have a model ready for this you gonna make it Steve? hehe


Fix issue #206: Windows compatibility

Add shelljs runtime dependency
Add @types/shelljs dev dependency
Replace execa call to rm with cross-platform shelljs rm
Fix "patch does not apply" error

Tried keeping the code style and convention. I can't really see what it failed on


Examples

This adds a couple of utility functions to expose the built-in datasets (See below).

I could write a test for this that checks if all of the examples at least show a short title? That would cause the coveralls to pass.

Adding tests would be great.


Auto-import named export from default exported

From @janhartmann on November 9, 2017 5:0

VSCode Version: 1.18.0-insider
OS Version: MacOS High Sierra

Steps to Reproduce:

Create a file with a default export
Create another file where the default exported is exported as a named export
Try to import it

Reproduces without extensions: Yes
Thank you for this auto-import feature in JavaScript! This is something I have been awaiting for a long time! I am not sure of the limitations of this, but I have trouble auto-importing default export's from an index.js file.
Take for example:
// File: ProfilePhoto.js
import React from "react";
import PropTypes from "prop-types";
import injectSheet from "react-jss";

const ProfilePhoto = ({ classes, picture }) => {
    return <img src={"data:image/jpeg;base64," + picture} className={classes.photo} />
};

const styles = () => ({
    photo: {
       // Styling
    }
});

export default injectSheet(styles)(ProfilePhoto); // injects the classes argument

// File: index.js
export { default as ProfilePhoto } from "./ProfilePhoto";

What I am doing here is that I am using an higher order component to wrap the function and use that as the default export. But this will never be picked up from the auto-import suggestions?
Is this a limitation or is something which can be integrated in VSCode?
Copied from original issue: Microsoft/vscode#37874

From @zfeher on November 9, 2017 8:40
Also want to thank you for the new auto import feature. It would be nice if you can make it work with default exports as well in the future. Here are some suggestions:
We have many default exports in the following forms
// some-func/index.js
const someFunc = () => { ... }
export default someFunc

// other-func/index.js
export default function() { ... }

// other-func-with-name.js
export default function otherFuncWithName () { ... }

So sometimes a default name for the exported default function can be aquired from the module (this could be an extra bonus feature).
However in general cases the module name (folder-name, folderName, FolderName) or the filename can be used (converted camelCase/PascalCase version if name is kebab-case) as a default name for auto import. So if I type someFunction, SomeFunction or some-function it could find the module to import. Plus it could show us an extra option like import as which could ask for a name.
Maybe the whole auto import could be improved later via using (fuzzy) search so we could narrow the results eg typing: utils/feature/some-func, u/f/sf, etc ... which eventually will be replaced with the found import if accepted.

Auto-import does work for default exports but only if there is an understandable symbol name currently. Example:
export default class Foo { }

export default function foo() { }

A basic example of @janhartmann's request would recognizing exports such as :
const id = x => x;

class Foo { }

export default id(Foo);

Should be fixed by https://github.com/Microsoft/TypeScript/pull/19875


Add field_boosts and fuzzy_fields optional parameters to Index::parse_query

An alternative approach to expose this functionality of QueryParser using Python-specific facilities, i.e. optional keyword arguments, instead of exactly mirroring the Rust API and exposing QueryParser as a separate #[pyclass].
Closes #201
Closes #50

@adamreichold @cjrh this works for me, atleast the fuzzy bit. The boosting doesn't seem to work, but perhaps that's a Tantivy issue.
Also, the snippet generator breaks with fuzzy queries. Is that normal?

The boosting doesn't seem to work, but perhaps that's a Tantivy issue.

Did you check whether the repr contain the expected boost factors?

Also, the snippet generator breaks with fuzzy queries. Is that normal?

I think this is a limitation of how the snippet generator works ATM, i.e. it second guesses the query and finds occurrences instead of being integrated into the query execution. Since it does not consider fuzzy matches, I cannot find them. You probably need to provide a fallback for such queries in your UI.


Include custom finder method in DataTables->find() options array

When $finder is set as second argument of the find function, it can
cause errors if user fails to set it and instead sets the $options array
as the second argument. This change makes it so the custom finder
method, if used, is included in the options array instead of as second
argument, improving usability in addition to following CakePHP best
practices. Also updates readme to reflect availability of this feature.

I prefer the way it is right now. The reason is that the current way resembles CakePHP better. See http://api.cakephp.org/3.1/class-Cake.ORM.Table.html#_find
It makes more sense that DataTables->find() which is a proxy to Table->find() can be called just alike. The added first argument (table name) is a well-understood necessity. However, moving the finder argument into options is confusing and less intuitive. It also adds significantly more code to the plugin for no apparent benefit.


Question about the overshooing KL divergence cost scaling.

Hello,
Thanks very much for the amazing codebase !
After reviewing the codebase and the orignal PlaNet paper, I have a question about the scaling of overshooting KL divergence. at line 171 ~ line 173 of the main.py, I notice that the observation_loss, reward_loss and one-step prediction KL divergence loss are all averaged over the chunk size and batch, which is indicated by the .mean(dim=(0, 1)) operation. But I also notice at line 190 of the main.py, there is a scaling of (args.chunk_size - 1) after the stacked multistep prediction(from d=2 to d=D) kl loss takes the .mean(dim=(0, 1)) operation. I am wondering what's the reason behind this scaling ? Is it because that when the overshooting_distance >= chuck_size, then the .mean(dim=(0, 1)) operation applied on the stacked multistep prediction kl loss first sum the kl loss up and then divide it by (1 + 2 + ... + (chuck_size - 1) = O((chunk_size - 1)^2)), therefore applying the (args.chunk_size - 1) will make the scaling back to O(chunk_size - 1), therefore roughly make the multistep prediction kl loss averaged over the chunk size ? If this is the case then does that mean if overshooting_distance << chuck_size (e.g.chuck_size = 50, overshooing_distance=20), to achieve the same level of scaling we need to tune overshooting_kl_beta to be smaller than 1 ? I notice you mentioned something like this in this post PyTorch Port, but just want to double-check.
Thanks very much for your time and patience !

My process to replicate prioritised 1) paper 2) results 3) original code, and that's the way it ended up. But in the end the scaling is somewhat arbitrary, as the losses could interchange sum/mean, and it is a hyperparameter to be tuned for your specific problem in the end.


Reservations

Overview
Created a reservations page where customers are able to view weather before making a reservation for outdoor dining. (currently still working on accessibility & making it more mobile-friendly).
Feedback Requested

structure of code
logic of fxns
accessibility

Good job fixing heroku! Looks good :)


Support passing in extensions

relay-compiler supports passing in --extensions, so you can run it if you have a convention of naming files .jsx for instance.
In my case, I didn't have much of a convention yet, so I worked around it by just renaming my files, but I may come back to looking at the code here and improving this later.

Hi this is a good idea, should not be too hard to do. I will see if I can submit a PR soon. Thanks.

v1.6.5 now does this. I added jsx support by default, so you don't have to use the extensions flag. You can still specify it for other custom file extensions. Let me know if it works!


Systemd stage 1: Unhide docs and round out assertions about unsupported features.

I think 23.05 would be a good time to unhide the systemd initrd options.

My only concern is that it does add a lot of sort of redundant things to the options list, since it repeats all the systemd options yet again. If anyone knows how to show the top level things like boot.initrd.systemd.services but hide the child options, that would probably be good.

Ok, I've set the systemd unit options to visible = "shallow";, and now they show up without their child options. That's perfect.

@arianvp I wasn't expecting the networkd PR to be merged first! :P There's a couple of things to change here now.

The network module should no longer claim to be incompatible.
I should also make the boot.initrd.systemd.network options shallow to some extent.

@ElvishJerricco can you rebase this on top of current master, and undraft when it's ready for review again?

I'm not exactly happy with the ugly changes to networkd.nix, so please let me know if anyone has a better idea for how to do that.

Ok I think that's a little better for networkd.
/cc @arianvp

I've been happily running systemd in stage 1 for a few weeks now, but with this PR I can't rebuild my system with it enabled? Is that intentional, and I shouldn't have been running systemd stage 1 yet when using zfs?
error:
       Failed assertions:
       - systemd stage 1 does not support 'boot.initrd.postDeviceCommands'. Please
       convert it to analogous systemd units in 'boot.initrd.systemd'.

         Definitions:
         - /home/systems/nixpkgs/nixos/modules/tasks/filesystems/zfs.nix

       - systemd stage 1 does not support 'boot.initrd.extraUtilsCommands'. Please
       convert it to analogous systemd units in 'boot.initrd.systemd'.

         Definitions:
         - /home/systems/nixpkgs/nixos/modules/tasks/filesystems/zfs.nix

       - systemd stage 1 does not support 'boot.initrd.extraUtilsCommandsTest'. Please
       convert it to analogous systemd units in 'boot.initrd.systemd'.

         Definitions:
         - /home/systems/nixpkgs/nixos/modules/tasks/filesystems/zfs.nix
(use '--show-trace' to show detailed location information)

This PR added some assertions, because systemd in initrd actually ignores some of these keys.
What are these keys set to in your case?

@flokli, those are being set automatically by the ZFS module so I think that module needs to be updated to conditionalize some of the boot.initrd. settings it does based on boot.initrd.systemd.enable

Sorry, should have added there context. Exactly what @lilyinstarlight said, this is just a side effect of having the zfs module enabled, nothing special on my side.

Ok I thought I had checked the boot.initrd.*Commands things better than I did. We should probably revert that specific change and go over it with a more fine tooth comb, preferably but not necessarily before 23.05.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/using-immutable-users-with-impermanence-on-luks/43459/1


Browser installer - Install dependencies before installing anything

Could the flynn install command first check for and install dependencies if needed, bailing out before making any chances if it can't pre-setup the system?
In some cases (in mine specifically a dedicated server at online.net) Ubuntu 14.04 comes as an extremely minimal install so doesn't include curl by default. Installing curl is an easy enough thing to do but it does make me wonder if other things are missing.
It also causes the message "If Flynn is already installed, it will be stopped and removed along with all data before installing the latest version. Would you like to proceed?" which only seems to ask for one server in a multi-server setup - eventually the easiest fix is to reinstall the OS on everything and start over hoping you don't miss something in take two

@cohan the install script installs all the dependencies needed to run Flynn, but yes flynn install attempts to fetch the install script on the server using curl which isn't guaranteed to be present. We should do something like which curl || apt-get install curl first (probably here).

It also causes the message "If Flynn is already installed, it will be stopped and removed along with all data before installing the latest version. Would you like to proceed?" which only seems to ask for one server in a multi-server setup

This sounds like a bug, we should fix it (/cc @jvatic).

eventually the easiest fix is to reinstall the OS on everything and start over hoping you don't miss something in take two

Or you could run the install script manually on each server with --clean and either accept the prompt or specify --yes.


The changes to kor-input and kor-popover

Hi Eduardo.
I have faced and fixed these issues:

kor-input: added the 'change' event in case when the value is cleared by clicking to the internal clear button;

kor-popover: added the checks for the left and the right popovers in order not to overflow over the top and the bottom of the viewport.

Regards,
Vladimir.

This is great, thank you so much!


Pass pretrained supervised q function in deepq.learn

I have a trained a separate supervised model for predicting actions corresponding to states. I want to refine that using deepq. Therefore, I wanted to know that how do I pass a pre-trained supervised q_func to the deepq.learn as a parameter instead of using deep.model function.

Oh, your pretrained policy must be compatible to load weights. Alternatively, you can fill replay buffer with rollouts that your policy produces. A lot of options here... Anyways, that's not a bug in this repo I believe.


All 1.23 patches

Description of changes:

Removed placeholder patch
Added the rest of the patches for 1.23

They're the same patches (with updates) as 1.22

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


added lazy load for whole container out of viewport

Imagine a carousel of images. If each item is Lazy loaded, the first items will be loaded and the ones at the right will wait until the user scrolls horizontally.
If the carousel is out of the initial viewport, the first images will also be loaded because they are "visible" on the container, but they are out of the screen. So, in this pull request I'm waiting the user scrolls to see the carousel in order to load the first images and then continue normally.

@loktar00 how do you see this?

@loktar00
I'm looking for a solution that fits the above problem.
Would it be possible to get this into the package?

@Noahnrg I have no idea how I didn't see this.... but it's been merged I'm not at my machine right now but I'll try and get the version update on NPM today.

@loktar00 wow, fast response time!
Looking forward too it, thank you so much!
just to confirm, it'll be able to be pulled from https://www.npmjs.com/package/react-lazy-load with the new version number, correct?

Correct, just updated it to 3.1.13.... kind of screwed up the vs really should be 3.1.0 oops :P but should pull down and work properly.
lol keep in mind the original PR for this was 3 years ago :/ I definitely let this package go as I was focusing on my day job a little too much for better or for worse I guess.

Fantastic !! thanks so much, works like a charm :)
(using react 16.13.1)


Fix wrong enum variant on Windows

The variant of RawWindowHandle on Windows isn't correct.
I also added sm-raw-window-handle to the default feature and CI. So we can make sure it's correct on all platforms.

@bors-servo try

:hourglass: Trying commit 3e202e21bd12d8744da67aa4fb3ef77befe3cd61 with merge 9bd5bc49ecd60e38a9e293f732291febb2cf259e...

:broken_heart: Test failed - checks-github

@bors-servo r+

:pushpin: Commit 5eacefa has been approved by jdm

:hourglass: Testing commit 5eacefa5c490b1b54f7adcf163c2017f101f8b97 with merge 678c0f5e47306224442999a0f05e20cb82734db6...

:sunny: Test successful - checks-github
Approved by: jdm
Pushing 678c0f5e47306224442999a0f05e20cb82734db6 to master...


ci: include release note generation in automation.

What this PR does / why we need it:
Adds release note generation to automation
Which issue(s) this PR fixes:
Fixes #318

Hey @jamacku. First, thanks for your work on  Differential ShellCheck.
And also, thanks for reaching out to suggest that fix.
I briefly tried it in this PR #1620, result didn't look the same as in your test PR here: https://github.com/jamacku/systemd/pull/74. I will take a close look next week.

Hi @Vincinator, GitHub requires a base scan of the branch, which happens on push. So until you merge this PR, it will show the message. Regarding my testing PR for systemd, I think I already had some base scan for main hence the message didn't show.

@jamacku Thanks a lot, appreciate it!


"type" missing when uniform distribution number provider is used (Predicate generator)

The "type" tag for the number provider doesn't show up in the output JSON when a uniform distribution is used in the predicate generator. This breaks the predicate file. (tested in 20w51a)
Recreation

Open predicate generator
Set condition to value check
Set first number provider to uniform

Expected result
{ "condition": "minecraft:value_check", "value": { "type": "minecraft:uniform", "min": 0, "max": 0 }, "range": { "min": 0, "max": 0 } }
What I get instead
{ "condition": "minecraft:value_check", "value": { "min": 0, "max": 0 }, "range": { "min": 0, "max": 0 } }

This is a bug of Minecraft tracked at MC-206118.

@Zsigio In the meantime, select Uniform+ in the dropdown.

Alright, thank you, we'll see if mojang decides to fix it or not then. Uniform+ is a great temporary solution.

For future reference, the bug got fixed by Mojang in 21w03a

For future reference, the bug got fixed by Mojang in 21w03a


React and DOM states persistence on widget pop out

Is your feature request related to a problem? Please describe.
React and DOM state does not persist after the widget is popped out.

Describe the solution you'd like
The React and DOM states would be kept so that the user's work would not be lost.

As we don't control the Widget's structure nor the React implementation details, if this type of state is needed, maybe a solution as what React documentation describes could be done in the widget itself ?
https://react.dev/learn/preserving-and-resetting-state#preserving-state-for-removed-components

We'll look if we could reuse the same strategy we use for floating widgets in popouts.

Hi @AAugustBentley, a fix for this was released today as 4.7.0. Note that since your component uses iTwinUI popouts, you will need to wrap your widget content in a <ThemeProvider theme="inherit"> component so the popout appear in the popout, we'll look into improving this in the future as #612, let us know if this addresses your issue in the mean time.

HI @AAugustBentley, the solution that was implemented turned out to cause more subtle problems than it solved issues, so we reverted in 4.7.2. We will find a different solution to this issue.

We were thinking about this problem - our team would in the long run would need to have a better way to preserve state other than reinstating it from localStorage, redux or something else. If widget has a lot of internal state, in order to preserve it we would have to either expose it by props or make it use redux/context for what was supposed to be internal state. And even then there is no certainty.
Can we hook up those users #608 and #632 with event listeners whenever widget is popped out or have them use a hook that will force rerender? At least for now.
Of course this is not a trivial issue and I'm aware you need more input/suggestions/use cases from users so I would like to experiment with this further and see if any other issues appear, at least I feel like we had decent groundwork before the revert. Can we have a way to provide an "experimentalPopouts" or some other flag to continue using this feature at our own risk at ThemeManager or at widget level?


CI/CD Pipeline with Automatic Deployment for Bot Verse

Description:
Implement a CI/CD pipeline that automatically builds, tests, and deploys the Bot Verse project. The pipeline should include various stages such as code linting, running unit tests, and deployment to a production environment (e.g., Heroku, AWS, or any preferred platform). This automation will enhance the development workflow by ensuring seamless integration of new code changes and continuous deployment without manual intervention.
Benefit:
The CI/CD pipeline will improve developer productivity by automating repetitive tasks such as building, testing, and deploying the application. It will also ensure that new changes are tested before deployment, reducing the likelihood of bugs in production. This is especially beneficial for open-source contributions under Hacktoberfest and GSSoC-ext, where frequent contributions need to be deployed smoothly.
This is one of the hard task. please  @kom-senapati assign me it

No free option. But i have a AWS account so I write the whole procedure(like Jenkins steps, docker etc) with file. If anyone wants to deploy the project then only required the git repo link. So want to write this full step. Please assign me @kom-senapati

Thank you, but I prefer not to use a CI/CD pipeline and may deploy on Render.