duplication

my devices are duplicating
using homebridge 1.5.1
on raspberry pi 4
homebridge-govee v7.1.2
led light strips

Please paste any relevant logs below.

Remove them under "Homebridge Settings/Manage Cached Accessories"

very kind. Thank you for replying!

Hi.
My govee x7 light strips have now gone missing form HK  x3 in last 2 months.
Im having to reinstall the bridge
Is it do with updates?
They reappear when I connect a new bridge but I’m losing all my aotomation
All my other 87 HK devices and 9 bridges are ok
Can you advise?
Many thanks

On 10 Nov 2022, at 14:08, @.*** wrote:

On 10 Nov 2022, at 11:28, JanLp @.***> wrote:
Remove them under "Homebridge Settings/Manage Cached Accessories"
—
Reply to this email directly, view it on GitHub https://github.com/bwp91/homebridge-govee/issues/350#issuecomment-1310143236, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVKDLN4YY2MIT5XT7SERIRDWHTL6LANCNFSM6AAAAAAR2YTJSY.
You are receiving this because you authored the thread.


New Domain: arib.is-cool.dev

Description
This domain is for my personal portfolio hosted on GitHub Pages
Link to Website
aribmuhtasim.github.io

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

Closed for prolonged inactivity/lack of response.


Birthday

Currently says it's a compulsory field, but form validates without it.
Also calendar needs theming in dark mode

Also, after reloading the Birthday field looks empty even though value is stored.

IN fact on each "edit", birthday triggers "required". We should include it as required field in default disto on Join, not just edit.

Currently says it's a compulsory field, but form validates without it.
IN fact on each "edit", birthday triggers "required". We should include it as required field in default disto on Join, not just edit.

If 'birthday' field will be required with validation, "Auto-create Person profile on Join" will stop working because Create account form doesn't have birthday field.

Also, after reloading the Birthday field looks empty even though value is stored.

Fixed here: #4658


Rename BlockStore and StateStore

We should stop naming everything Store. For these cases I suggest the names BlockDb and StateDb

Agreed!

I'll fork and propose changes in name of BlockStore and StateStore to BlockDb and StateDb

Made 1 change, and thanks @mpaulucci for telling me that we want to 'update the module everywhere where it's referenced'. I'll figure it out.


Add an example of how to drop all indexes and constraints with schema.assert

Related to https://github.com/memgraph/memgraph/issues/365 .

For example, here https://memgraph.com/docs/fundamentals/indexes#delete-an-index


Register success but the observe is always reset

I am implementing the lwm2m server by using leshan. For some devices, after the successfully client register and observe sending to client, the server automatically send reset to client. The observe callback function always got exception says timeout.
Please see the output from wireshard:

The observe command

The 205 content notification

Followed by 205 content notification, the reset was sent from server automatically.
The the interesting finding is the MID and token of 205 content notification are different from other message, not sure why.

What are you using as LWM2M client ?
What value for timeout are you using ? 5s  liike default leshan-server-demo ?
Regarding the first response, it can not be consider as a valid one.
Token must be the same.
(Token is used to match Request and Response, MID is used to match Message and Ack)
So the first RST is an expected behavior.
Then there is an unexpected ACK (MID 25099) maybe a retransmission (because we get a request retransmission before in this case this is not an optimal behavior at device side)
Then NON confirmable response which this time is valid (right token is used) but rejected by the server I guess because request timeout. (do you have a timeout <= 30s?)
So my first guess is : this is a problem at client side.

Thanks for the reply.
The timeout is set to 5 min, so it should be long enough as I think.
I don't have the quick answer on which LWM2M client the device are using, because the devices are from customer. But the behaviors are correct when the device connected to another commercial lwm2m server we are using. I agree the client side should reply the same token in notification, but why it passed the check in the commercial lwm2m server, it is difficult to understand.

What are you using as LWM2M client ?
What value for timeout are you using ? 5s liike default leshan-server-demo ?
Regarding the first response, it can not be consider as a valid one.
Token must be the same.
(Token is used to match Request and Response, MID is used to match Message and Ack)
So the first RST is an expected behavior.
Then there is an unexpected ACK (MID 25099) maybe a retransmission (because we get a request retransmission before in this case this is not an optimal behavior at device side)
Then NON confirmable response which this time is valid (right token is used) but rejected by the server I guess because request timeout. (do you have a timeout <= 30s?)
So my first guess is : this is a problem at client side.

If the timeout is 5min then the second answer should be accepted and so no timeout is expected :thinking:

But the behaviors are correct when the device connected to another commercial lwm2m server we are using.

I would not say the behavior is correct, I would say it works despite an incorrect behavior. Anyway with a 5min timeout this should works with Leshan too...
Which version of Leshan are you using ?
I understand that you are not using DTLS, could you confirm ?
Are you behind a NAT (or any environmment which could change the client IP) ?
Eventually could you share the whole capture ?

I cleaned the code to remove request tansmission, it looks like following:

The observe command:

The response:

This time the token looks good now, but if the observe = 1 in response is correct behavior?

What are you using as LWM2M client ?
What value for timeout are you using ? 5s liike default leshan-server-demo ?
Regarding the first response, it can not be consider as a valid one.
Token must be the same.
(Token is used to match Request and Response, MID is used to match Message and Ack)
So the first RST is an expected behavior.
Then there is an unexpected ACK (MID 25099) maybe a retransmission (because we get a request retransmission before in this case this is not an optimal behavior at device side)
Then NON confirmable response which this time is valid (right token is used) but rejected by the server I guess because request timeout. (do you have a timeout <= 30s?)
So my first guess is : this is a problem at client side.

This time, the request is sent at  ~600s and the answer received at 900s, so 300s/5min later this is normal that the request timeout.

This time the token looks good now, but if the observe = 1 in response is correct behavior?

I would say, it's OK. The specification says :
   When included in a response, the Observe Option identifies the
   message as a notification.  This implies that a matching entry exists
   in the list of observers and that the server will notify the client
   of changes to the resource state.  The option value is a sequence
   number for reordering detection (see Sections 3.4 and 4.4).

Yes :)

This time, the request is sent at ~600s and the answer received at 900s, so 300s/5min later this is normal that the request timeout.

If your device has dynamic IP and you don't use DTLS, you could have a look at : https://github.com/eclipse/leshan/wiki/LWM2M-Observe#for-udp-without-security
(You maybe missed my previous comment :point_up: : https://github.com/eclipse/leshan/issues/862#issuecomment-656007947)

I noticed your reply, and replied. Great thanks, I have the same finding. But the timeout is not the real problem, the port of the reponsed changed, so it is recognized as wrong reponse in leshan. How do we do in this case?
See the dest port in Get：

And the source port  in 205 content response

I guess the client changed its port after awake.

If your device has dynamic IP and you don't use DTLS, you could have a look at : https://github.com/eclipse/leshan/wiki/LWM2M-Observe#for-udp-without-security
(You maybe missed my previous comment ☝ : #862 (comment))

Sorry that I noticed your last reply give me the answer.
We are trying this solution, thanks a lot!

If your device has dynamic IP and you don't use DTLS, you could have a look at : https://github.com/eclipse/leshan/wiki/LWM2M-Observe#for-udp-without-security
(You maybe missed my previous comment ☝ : #862 (comment))

It works well now, really apprieciate your help.
I will close this issue.

If your device has dynamic IP and you don't use DTLS, you could have a look at : https://github.com/eclipse/leshan/wiki/LWM2M-Observe#for-udp-without-security
(You maybe missed my previous comment ☝ : #862 (comment))


align dateServiceStarted with dateFirstUsed

for all the data models and for alignment purposes with GSMA IoTBDE (when it makes sense).

To be done globally with all the attributes not only with dates ones


[Feature]: Support for Geo/Map custom chart in EChart

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
ECharts is now a standard library for charts. It has a very rich library of available chart types, and one type of them is based on Maps.
EChart map charts: https://echarts.apache.org/examples/en/index.html#chart-type-map
Sample echart with custom svg map: https://echarts.apache.org/examples/en/editor.html?c=geo-svg-lines&lang=js
We have a use-case that we would like to show a custom echart map in Appsmith frontend. The SVG represents our factory layout and we would like to visualize statuses of machines on this layout with custom color rules.
We will supply the data using a datasource, probably a REST API.
The problem we face is that to use a custom map chart in ECharts, we have to register our custom SVG. This can be seen in example (link above).
code is:
  ROOT_PATH + '/data/asset/geo/MacOdrum-LV5-floorplan-web.svg',
  function (svg) {
    echarts.registerMap('MacOdrum-LV5-floorplan-web', { svg: svg });

And in Appsmith currently we were not able to get hold of echarts object to register it
Why should this be worked on?
If echarts is standard library, it's standard visualization charts should be supported. Custom charts with developer provided configuration are already supported, so Map chart should be supported too.

@practical-programmer in appsmith, this is a separate widget.
While we have already started migrating towards eCharts (starting with the chart widget), we still need to migrate the Map chart widget.
The basic use cases that are provided today in the widget will be migrated safely to eChart implementation once we start doing it. You use case however is a bit more peculiar, we will consider this while we are starting.
For now, please see if map chart current implementation can give you what you need.

@somangshu thank you for the response and clarification - this is what we expected for now. Regarding testing the Map Chart current implementation - as it only supports predefined world maps, unfortunately there is no way for us to solve our requirement with it


Get pure generated SQL instead of directly running exqlite

Hi there
I have a few questions and possibly an interesting proposal.
First of all, amazing work you;ve put in this adapter and the exqlite version! I'm in love with both and have migrated from sqlitex.
Is there a way to use this adapter and run normal ecto adapters and for it to just generate the sql and possible pass it on to somewhere else? IE another server. Maybe a behaviour or something similar to switch between the default  of running exqlite directly or passing it somewhere else. A simple abstraction would suffice.  Such as another server which is running exqlite, or a local instance which handles the exqlite wrapped in (gen)servers (or something better) for concurrency. There is more to say about this yet I'm trying to be brief.
The rationale:
Last year I began working on a project similar to Actordb.com in pure Elixir.
I've used sqlitex for it and mixed code from sqlitex, the mysql and postgresql ecto adapters. The idea is to have a server which you can use independently with many sqlite connections via the Actor model (since Elixir and Erlang support this greatly). Most of the apps I've built can deal with this actor modular approach quite well.
I;m thinking out loud now with an eye on using this instead of my own ecto adapter. As this will simplify things instead of wasting effort in duplicating and reimplementing the wheel from zero. Since Elixir's built in mind with modularity.
My current implementation prototype is located at: https://fossil.lba.im/glow/dir?ci=tip (WIP)
This is more of a question and invitation to share ideas and thoughts.
Some references and ideas:
https://expensify16.rssing.com/chan-10870710/latest-article4-live.php - Scaling Sqlite to 4 million queries per second
https://review.firstround.com/your-database-is-your-prison-heres-how-expensify-broke-free
http://www.actordb.com/
Thanks for your understanding

This is actually something I was investigating for my own needs. Yes it is possible, but it is incredibly cumbersome with how ecto is structured.
If I have time, I'll extract out the stuff I did into a blog article or example to use, but it works.  You have to Enum.zip the columns with the rows and feed it into the ecto struct.
Basically long story short, forcing a square peg into a round hole. Sort of.

Oh yeah, the square peg in round hole is why I ditched the actordb ecto implementation I began in 2019.  This is one of the reasons why I asked this question, It would be better if there where one central ecto SQL generator for sqlite instead of multiple implementations which all will hit the same issues over and over.
I'm currently investigating all possible methods and I'll be doing some Proof of Concepts. I'm hoping to have something that will require a maximum of 10 modified lines in the ecto_sqlite3 to support what I'm thinking off.
I'll come back with the results and possibly a pull request in the future.

 You have to Enum.zip the columns with the rows and feed it into the ecto struct.

It's a bit of boilerplate, but using Ecto.Repo.load should handle most of the actually complex things, doesn't it?

Yes, that does take a bit of the complexity out. I do remember using it but had a case where it wasn't possible. It has been a while since I last played with it. For those looking at this as well: https://hexdocs.pm/ecto/Ecto.Repo.html#c:load/2


Add in tonemapping for hdr ---> sdr conversions

Should be doable, found a guide on it here: https://stevens.li/guides/video/converting-hdr-to-sdr-with-ffmpeg/

After poking around, implementing this by itself is no problem, the difficulty will be making sure it works with resolution downscaling + subtitle burn-in with filter_complex being used rather than -vf. Should be doable, tho.

any word on this enhancement. would love to have this add as my plex server is growing more and more to all HDR content.

I haven't had much free time to finish this, but it's definitely on my radar as the amount of HDR stuff increases and no one I know has a HDR tv/monitor. :D
I'll try and get the bare-minimum implementation added over christmas... it won't work with burned in subtitles, but it'll be a start.


Dependabot/composer/service front/aws/aws sdk php 3.288.1

Purpose
Briefly describe the purpose of the change, and/or link to the JIRA ticket for context
Fixes LPAL-####
Approach
Explain how your code addresses the purpose of the change
Learning
Any tips and tricks, blog posts or tools which helped you. Plus anything notable you've discovered about the LPA service
Checklist

[ ] I have performed a self-review of my own code
[ ] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[ ] I have added tests to prove my work
[ ] I have added mandatory tags to terraformed resources, where possible
[ ] If I have a new OPG component dependency, I have updated the metadata.json with the repo location.
[ ] If I added a package.json or composer.json, I also made sure this is included in the script in .github/workflows/dependabot-update.yml
[ ] The product team have tested these changes

These upgrades look pretty similar to https://github.com/ministryofjustice/opg-lpa/pull/1637,  just done by dependabot rather than renovate.  Have similar phpunit failures.  I'd somewhat advocate closing this PR as a duplicate of the renovate PR. @MishNajam  , @ntse what do you think?  (the plan would be to fix https://github.com/ministryofjustice/opg-lpa/pull/1637 )

Closing because I fixed these unit tests on the equivalent renovate PR. (the changes in this PR will be applied, by merging the renovate PR)


ENH: Improve ctkFittedTextBrowser collapsed text formatting

Show ellipsis (...) where the collapsed text is cut.
Remove teaser separator(line break) character instead of replacing with space. This allows better control of what is displayed.
For example: "Some teaser. This is more info." text expanded version was displayed as "Some teaser . This is more info.", but
now it is shown as "Some teaser. This is more info."

Thanks for the patch.
Nitpick: Could you update the example reported in the commit message to indicate how the ellipsis is now used ?

Image gallery updated. http://www.commontk.org/index.php/File:CtkFittedTextBrowserCollapsible.png

Nicely done.
For future reference:


`rbenv' in PATH: printc:6: bad substitution

After open zsh  and try to run rbenv doctor:
curl -fsSL https://github.com/rbenv/rbenv-installer/raw/master/bin/rbenv-doctor | zsh
I've got:
Checking for 'rbenv' in PATH: printc:6: bad substitution
what is the problem?

I'm sorry you're having issues.

Hi @mislav,
I think the problem is related to Zsh because I used:
...rbenv-doctor | zsh
with I use:
...rbenv-doctor | bash
the problem not occurs.
I think it's a specific bash code inside rbenv-doctor.
Can I test the rbenv with doctor redirecting the script or running the script inside zsh?
I fount this but I can't identify the pattern inside the rbenv doctor code:
https://stackoverflow.com/questions/20323738/echo-syntax-error-bad-substitution
https://unix.stackexchange.com/questions/426458/bad-substitution-running-ls-sed-with-bash
https://www.unix.com/shell-programming-and-scripting/158413-bad-substitution-error.html
Thanks!

@mislav My bash version is:
GNU bash, versão 4.4.19(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2016 Free Software Foundation, Inc.
Licença GPLv3+: GNU GPL versão 3 ou posterior <http://gnu.org/licenses/gpl.html>.

If I use the bash in:
rbenv-doctor | bash
instead of
rbenv-doctor | zsh
The problem not occurs, only if I redirect to zsh.
Maybe bash specific code in rbenv-doctor?

Ah I've just realized that you were piping to zsh instead of bash. You can't do that. rbenv-doctor is a bash script and not a zsh script. The script is not strictly POSIX-compatible.


Drop Plugin class completely

This feature isn't actively supported by Go and is very unstable (still very cool though). And more importantly, it makes Goby harder to build on other platforms. So I'm dropping it now.

@saveriomiroddi it turns out to be a feature that a user wants, so will keep it a bit longer. Sorry for the false call 😬


Docker won't build due to certificate issues

I'm trying to build via Docker, but I get the build output below.  I'm trying to build with a Windows10 machine using native Docker through Powershell.  All I've done is download the master branch and execute a 'docker build .'
PS H:\Burrow-master> docker build .
Sending build context to Docker daemon  413.2kB
Step 1/8 : FROM golang:alpine
 ---> 9e3f14138abd
Step 2/8 : MAINTAINER LinkedIn Burrow "https://github.com/linkedin/Burrow"
 ---> Running in a84df06c6f8f
 ---> c9c4e6f3bb37
Removing intermediate container a84df06c6f8f
Step 3/8 : RUN apk add --no-cache curl bash git ca-certificates wget  && update-ca-certificates  && curl -sSO https://raw.githubusercontent.com/pote/gpm/v1.4.0/bin/gpm  && chmod +x gpm  && mv gpm /usr/local/bin
 ---> Running in d0791a11c325
fetch http://dl-cdn.alpinelinux.org/alpine/v3.6/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.6/community/x86_64/APKINDEX.tar.gz
(1/12) Installing ncurses-terminfo-base (6.0_p20170930-r0)
(2/12) Installing ncurses-terminfo (6.0_p20170930-r0)
(3/12) Installing ncurses-libs (6.0_p20170930-r0)
(4/12) Installing readline (6.3.008-r5)
(5/12) Installing bash (4.3.48-r1)
Executing bash-4.3.48-r1.post-install
(6/12) Installing libssh2 (1.8.0-r1)
(7/12) Installing libcurl (7.56.1-r0)
(8/12) Installing curl (7.56.1-r0)
(9/12) Installing expat (2.2.0-r1)
(10/12) Installing pcre (8.41-r0)
(11/12) Installing git (2.13.5-r0)
(12/12) Installing wget (1.19.1-r2)
Executing busybox-1.26.2-r7.trigger
OK: 34 MiB in 24 packages
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
The command '/bin/sh -c apk add --no-cache curl bash git ca-certificates wget  && update-ca-certificates  && curl -sSO https://raw.githubusercontent.com/pote/gpm/v1.4.0/bin/gpm  && chmod +x gpm  && mv gpm /usr/local/bin' returned a non-zero code: 60

This isn't a Burrow issue - the problem is that the docker build is trying to run update-ca-certificates and that is not working properly (but not failing). This then causes the curl to fail as it can't validate the SSL connection when fetching gpm.

I understand that it isn't a Burrow issue directly, but at this point, anyone that clones this repo and tries to build via Docker will fail.  I don't know why that 'update-ca-certificates' command is failing within the alpine base image, and I'm not sure how to fix it.

Turns out it was an issue with my windows environment.  I never got that issue solved but I was able to successfully build using my mac.


Don't scrape deck URLs already scraped within a channel

This level of redundancy is not welcome

Reconsidered


Incorrect cyrillic filenames

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: Ubuntu 14.04
Hyper.app version: 1.0.1
The issue is reproducible in vanilla Hyper.app: Is Vanilla

Issue
All cyrillic names not correctly rendered.

as mentioned at #1204 you should add
export LANG=ru_RU.UTF-8
export LC_CTYPE=ru_RU.UTF-8

in to your .bash_profile or .zshrc

@sashamjolnir yeah, it's work!
Thank you! :cake:


How to retreive uid of an email we just sent ?

Hi,
i'm trying to get the uid (the gmail one) of an email I've just sent with the method deliver!
Is it possible to get this info without polling Gmail just after sending ?
Thanks, Alex

This is discussed here: #43. I've merged support to master.

This issue was moved to gmailgem/gmail#39


SQS ingestion

Tracking issue for SQS ingestion support.
Goal
Someone can send logs through SQS to Matano.
Design

Likely have a separate ingest queue per log source.

SQS has a max message size of 256 KB. For efficiency, we can store many log 'rows' in one SQS message (similar to how Kinesis packs messages).

Aim to basically encode each message very similarly to an S3 file.

Can also add support compression through base64 encoding.

Notes

SQS ingestion can skip Data batcher (necessary for S3 to have predictable work sent to Transformer).

Instead, set SQS event source to max batch window (10000) and Lambda will send payload up to max 6MB.

Transformer to be updated to be able to handle SQS messages. Lambda will be invoked with array of messages.

Implement a method very similar to current read_events_s3 (https://github.com/matanolabs/matano/blob/main/lib/rust/transformer/src/main.rs#L370) for SQS that converts the raw SQS messages into values.

Some thoughts as I think more about the problem.. The question I am currently pondering is:
To what extent do we want to abstract the end user from complexity?

First thought:
If we require end users to push messages to a Log Source SQS queue in order for the Transformer to ingest, this requires the end user to:

Create patterns to interact with SQS via SDK for each log source
Properly manage messages that are too large / too small. If too small the logs may be inefficient & costly. If the message is too large, the end user will have to establish an S3 pattern that feels reminiscent of what you guys have already implemented
They must normalize their message body to fit our pattern (basically just stringify the Message body, but still something to consider and have to support)

Second thought:
If we create a Lambda that receives POST requests on behalf of the end user, we could then establish an opinionated pattern behind the scenes. Options ma include:

Pushing the stringified body directly on to the log source queue
Lambda creates S3 objects, then the existing pattern can be re-used with no changes

Drawbacks to the above means this is no longer "SQS Ingestion"

This all comes back to the initial question of what are we expecting the end user to know / manage.
Curious if you guys have an easy solution to all this, if I'm missing a key piece of SQS pushing, or if we should brainstorm a little further.


MySQL 5.7 and "tls: handshake failure" error

Describe the bug
Due to recent changes in Golang's default list of secure TLS cipher suites, users connecting to MySQL 5.7 may see a "tls: handshake failure" error from newer versions of Skeema. This is because MySQL 5.7 is EOL by Oracle, and its list of supported cipher suites is naturally getting rather old.
Environment
This affects Skeema Community Edition v1.12.1 (just released Dec 2), as well as Skeema Premium Edition v1.11.2+ (all 2024 releases). The discrepancy is because Premium always uses the latest Golang standard library, whereas Community always supports the previous Golang minor release and is built with the previous standard library.
This bug only affects MySQL 5.7 out of the box; MySQL 8.0+ is unaffected.
Percona Server 5.7 is unaffected, due to using a newer/better list of cipher suites.
Old versions of MariaDB might be affected if you have specifically configured TLS in the server.
Root cause
See https://github.com/go-sql-driver/mysql/issues/1635#issuecomment-2516244730
Workarounds
The easiest fix is to set environment variable GODEBUG='tlsrsakex=1' in skeema's environment.
Alternatively, if you don't actually need an encrypted connection between Skeema and the DB server, disable TLS by using Skeema option ssl-mode=disabled.

Skeema v1.12.2 is now available and contains the fix for this issue, as well as other TLS improvements.


[BUG] Hue motion sensor SML001 (indoor) & SML002 (outdoor) not correctly reported

Describe the bug
My Hue motion sensors which I have been using for 3+ months keep reporting a battery level of 100% which must be incorrect, right?
To Reproduce

Expected behavior
A battery level to drop over time
Logs
When I ask for the battery_percentage_remaining attribute from the PowerConfiguration cluster I get a value of 200. I have no idea which attribute home assistant uses behind the scenes to create the battery_level sensor
DEBUG (MainThread) [homeassistant.components.zha.entity] light.diningroom_ceiling_2: polling current state
DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 137 under 138 request id, data: b'0089000000'
DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (20, 138, 0, <DeconzAddressEndpoint address_mode=2 address=0xBDB7 endpoint=11>, 260, 6, 1, b'\x00\x89\x00\x00\x00', 2, 0)
DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 138]
DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,)
DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 138: 00
DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x8a 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0xbdb7 endpoint=11>, status: 0x00
DEBUG (MainThread) [zigpy.device] [0x4e28] Extending timeout for 0x8b request
DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 139 under 140 request id, data: b'008b002100'
DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (20, 140, 0, <DeconzAddressEndpoint address_mode=2 address=0x4E28 endpoint=2>, 260, 1, 1, b'\x00\x8b\x00!\x00', 2, 0)
DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 140]
DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,)
DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 140: 00
DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x8c 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0x4e28 endpoint=2>, status: 0x00
DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]
DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1)
DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [31, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x4e28>, 2, 260, 1, b'\x18\x8b\x01!\x00\x00 \xc8', 0, 175, 255, 8, 227, 84, 1, -55]
DEBUG (MainThread) [zigpy.zcl] [0x4e28:2:0x0001] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=139 command_id=Command.Read_Attributes_rsp>
DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x4e28>, ep: 2, profile: 0x0104, cluster_id: 0x0001, data: b'188b0121000020c8'
DEBUG (MainThread) [homeassistant.components.zha.api] Read attribute for: cluster_id: [1] cluster_type: [in] endpoint_id: [2] attribute: [33] manufacturer: [None] response: [200] failure: [{}],
DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 141 under 142 request id, data: b'008d000000'
DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (20, 142, 0, <DeconzAddressEndpoint address_mode=2 address=0xBDB7 endpoint=11>, 260, 8, 1, b'\x00\x8d\x00\x00\x00', 2, 0)
DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 142]
DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,)
DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 142: 00
DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x8e 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0xbdb7 endpoint=11>, status: 0x00

Is anyone else experiencing this issue or is there a way I am not aware of to fix this?

check the battery again, in about 1 year

check the battery again, in about 1 year

check the battery again, in about 1 year

Does it really take that long for the battery to lose enough power to update state

check the battery again, in about 1 year

Does it really take that long for the battery to lose enough power to update state

I have 2 indoor ones for over 3 years 76% and 12% with batteries and the last have periods of jumping around in all possible and not possible routers in my network.
The 2 first year they was in my deCONZ network and the difference was beginning ther (I think its was problem with ack and pull control config that was draining on more then the other).so you need waiting little for getting them going down or putting in rechargeable batteries that is going down faster but holing longer before being compleet empty.

I have 2 indoor ones for over 3 years 76% and 12% with batteries and the last have periods of jumping around in all possible and not possible routers in my network.
The 2 first year they was in my deCONZ network and the difference was beginning ther (I think its was problem with ack and pull control config that was draining on more then the other).so you need waiting little for getting them going down or putting in rechargeable batteries that is going down faster but holing longer before being compleet empty.

Does it really take that long for the battery to lose enough power to update state?

Update state as in report a "value" -- no. Update state as in "report a different value" is going to take a while.

Does it really take that long for the battery to lose enough power to update state?

Update state as in report a "value" -- no. Update state as in "report a different value" is going to take a while.

Does it really take that long for the battery to lose enough power to update state?

Update state as in report a "value" -- no. Update state as in "report a different value" is going to take a while.

Do you know which cluster attributen is used by home assistant?

Does it really take that long for the battery to lose enough power to update state?

Update state as in report a "value" -- no. Update state as in "report a different value" is going to take a while.

Do you know which cluster attributen is used by home assistant?

Its have 2 batteries so the red value / 2 = HA value.

Its the other one with 76% battery left.

Its have 2 batteries so the red value / 2 = HA value.

Its the other one with 76% battery left.

Ahhhhh that's who it's reporting 200… thanks!

Ahhhhh that's who it's reporting 200… thanks!

But attribute "battery_quantity (id: 0x0033)" = None !!
Some IKEA controlled with one battery is reporting 2 and 100% battery so ZHA is displaying 50% without quirk :-(
But my math is saying 153 X 0 = 0  ;-)

But attribute "battery_quantity (id: 0x0033)" = None !!
Some IKEA controlled with one battery is reporting 2 and 100% battery so ZHA is displaying 50% without quirk :-(
But my math is saying 153 X 0 = 0  ;-)


Cant spectate when dead (stuck frame)

[Info   :HULLBREAKER] Player killed, one for all is active: True
[Error  : Unity Log] NullReferenceException: Object reference not set to an instance of an object
Stack trace:
HullBreakerCompany.Plugin.OneForAll () (at :0)
(wrapper dynamic-method) GameNetcodeStuff.PlayerControllerB.DMD<GameNetcodeStuff.PlayerControllerB::KillPlayerServerRpc>(GameNetcodeStuff.PlayerControllerB,int,bool,UnityEngine.Vector3,int,int)
GameNetcodeStuff.PlayerControllerB.KillPlayer (UnityEngine.Vector3 bodyVelocity, System.Boolean spawnBody, CauseOfDeath causeOfDeath, System.Int32 deathAnimation) (at <39ddadb2aa5843e586a6c642ee60b0b5>:0)
GameNetcodeStuff.PlayerControllerB.DamagePlayer (System.Int32 damageNumber, System.Boolean hasDamageSFX, System.Boolean callRPC, CauseOfDeath causeOfDeath, System.Int32 deathAnimation, System.Boolean fallDamage, UnityEngine.Vector3 force) (at <39ddadb2aa5843e586a6c642ee60b0b5>:0)
HoarderBugAI.OnCollideWithPlayer (UnityEngine.Collider other) (at <39ddadb2aa5843e586a6c642ee60b0b5>:0)
EnemyAICollisionDetect.OnTriggerStay (UnityEngine.Collider other) (at <39ddadb2aa5843e586a6c642ee60b0b5>:0)
For some reason this error happens when I die, and then I stuck in one frame, I can hear and change spectators, but it won't show me the normal gameplay, just the moment I died.

oh and this error, the above is most likely not the cause/related to your mod sry.
[Error  : Unity Log] NullReferenceException: Object reference not set to an instance of an object
Stack trace:
HullBreakerCompany.Plugin.OneForAll () (at :0)
(wrapper dynamic-method) GameNetcodeStuff.PlayerControllerB.DMD<GameNetcodeStuff.PlayerControllerB::KillPlayerServerRpc>(GameNetcodeStuff.PlayerControllerB,int,bool,UnityEngine.Vector3,int,int)
GameNetcodeStuff.PlayerControllerB.__rpc_handler_1346025125 (Unity.Netcode.NetworkBehaviour target, Unity.Netcode.FastBufferReader reader, Unity.Netcode.__RpcParams rpcParams) (at <39ddadb2aa5843e586a6c642ee60b0b5>:0)
Unity.Netcode.RpcMessageHelpers.Handle (Unity.Netcode.NetworkContext& context, Unity.Netcode.RpcMetadata& metadata, Unity.Netcode.FastBufferReader& payload, Unity.Netcode.__RpcParams& rpcParams) (at <1b23ec5fcbfc4fbca0db70afcdb9b715>:0)
Rethrow as Exception: Unhandled RPC exception!
UnityEngine.Debug:LogException(Exception)
Unity.Netcode.RpcMessageHelpers:Handle(NetworkContext&, RpcMetadata&, FastBufferReader&, __RpcParams&)
Unity.Netcode.ServerRpcMessage:Handle(NetworkContext&)
Unity.Netcode.NetworkBehaviour:__endSendServerRpc(FastBufferWriter&, UInt32, ServerRpcParams, RpcDelivery)
GameNetcodeStuff.PlayerControllerB:DMD<GameNetcodeStuff.PlayerControllerB::KillPlayerServerRpc>(PlayerControllerB, Int32, Boolean, Vector3, Int32, Int32)
GameNetcodeStuff.PlayerControllerB:KillPlayer(Vector3, Boolean, CauseOfDeath, Int32)
GameNetcodeStuff.PlayerControllerB:DamagePlayer(Int32, Boolean, Boolean, CauseOfDeath, Int32, Boolean, Vector3)
HoarderBugAI:OnCollideWithPlayer(Collider)
EnemyAICollisionDetect:OnTriggerStay(Collider)

To understand what's going on, I need logs, the version of the installed mod. with a high degree of probability the issue is not in my hullbreaker, when I tested for 3 hours in a row, I never encountered any error

In the logs I write which events were selected and was not loaded in them; I cannot determine otherwise. In v1.1.9, there is protection against NullReferenceException, so I don't know

Hi, sorry, it doesn't always happen, but often when you die from a monster that was spawned by HullBreaker I think.
You can test it yourself in that modpack:
https://thunderstore.io/c/lethal-company/p/Fundryi/SillyCatPack/

the mod works with errors, if a parameter [Chainloader] HideManagerGameObject = true, I don’t know what to do with this yet, this is because of CapyCat-Solos_Bodycams

In theory, I can somehow solve this, but I have no experience specifically in mods, sry

https://thunderstore.io/c/lethal-company/p/CapyCat/Solos_Bodycams/


[feature request] Adapter for Opentrons Execution

We'd like a tool to convert abstract PAML into Opentrons-readable JSON. The most helpful place to start is to mark the spots that will need to change from the version built for Strateos/Autoprotocol
Because the Opentrons API has relatively few primitives (it basically just handles liquids), there should be relatively few mappings required, and I expect that most outputs will only be partially executable on an Opentrons robot. So non-robot-executable steps could be represented as protocol metadata, or in a separate plaintext file.

Hi Tim,
Just to keep you in the loop, the OTB is on track. Here are my notes on the OTB, I still have a lot of revisions to make, I’ll let you know when it's ready to share publicly.
https://github.com/celleleven/Open-Temperature-Block https://github.com/celleleven/Open-Temperature-Block
Best,
James

Hi Tim, Just to keep you in the loop, the OTB is on track. Here are my notes on the OTB, I still have a lot of revisions to make, I’ll let you know when it's ready to share publicly. https://github.com/celleleven/Open-Temperature-Block https://github.com/celleleven/Open-Temperature-Block Best, James

Thanks James - let's take this in a different thread. Excited to see how it's coming along!


Refs #34233 -- Bumped minimum supported versions of Selenium to 4.8.0.

This bumps minimum supported versions of selenium to the first release to support Python 3.10.
ticket-34233
refs PR #17001

Thanks both for checking :+1:


Gopass does not clear the clipboard

When I use gopass -c <my-file> the password is copied to the clipboard and should be cleared in 45s. I get a notification that my password is cleared, and using ctrl+v ensures I cannot paste anything. However, if I open my clipboard (copyq) in my case I can still see and access the password.
Steps To Reproduce

Copy the password using gopass -c <my-file>
Wait for 45s to get notified that the password is deleted.
Open clipboard utility (copyq), the password hasn't been cleared.

Environment

OS: Manjaro linux, with i3 DM
OS version:Linux 42 4.14.102-1-MANJARO #1 SMP PREEMPT
gopass Version: <IP_ADDRESS>
Installation method: Package manager

Thanks for reporting this issue.
Unfortunately gopass can not, and will not, support any possible clipboard manager out there.
We can't possibly detect any binary listening for clipboard changes. There is some discussion and work on avoiding the clipboard altogether, but if you choose to use the clipboard you need to be careful with such programs.
Feel free to submit a PR to support copyq.

The copyq declares "Ignoring clipboard copied from some windows or containing some text" as one of its features.

It shouldn't be too hard to implement this, but I'm not going to have time for that anytime soon:
https://copyq.readthedocs.io/en/latest/scripting-api.html#disable

@dastier @ashfaqfarooqui Doesn't this allow you to exclude gopass from the application copyq will copy from:  https://copyq.readthedocs.io/en/latest/faq.html#how-to-omit-storing-text-copied-from-specific-windows-like-a-password-manager
I'm thinking about closing this, since as @dominikschulz said, we cannot support all the different clipboard that exist and keep reducing our code complexity.

@dastier @ashfaqfarooqui Doesn't this allow you to exclude gopass from the application copyq will copy from:  https://copyq.readthedocs.io/en/latest/faq.html#how-to-omit-storing-text-copied-from-specific-windows-like-a-password-manager
I'm thinking about closing this, since as @dominikschulz said, we cannot support all the different clipboard that exist and keep reducing our code complexity.


Reflect not active rpc

Description

Added a message that appears when the rpc goes down (created a new RpcDownMessage component using existing styles), preventing the user from displaying data/doing actions that require rpc to be up. The message disappears as soon as the rpc is up.
Followed indications of the related issue (see below) to have an experience akin to Browser DevTools.
Related issue
https://github.com/paradigmxyz/rivet/issues/9
How Has This Been Tested?

On dev environment, produced expected behaviour by shutting down rpc, then turning it up again. Everything works as expected (see screens below).
Screenshots

thanks!


Ability to preview widget and sign in with NEAR Wallet

A lot of components you'll develop on NEAR Discovery require the user to be signed in to their wallet to perform actions (EG: liking or commenting on a post). With the VS Code extension there's currently no way to preview a widget in a signed in state. This is a huge blocker for using the extension over the Web IDE.
For an example of a component that requires being signed in, check out the Posts.Compose component: https://alpha.near.org/#/calebjacob.near/widget/ComponentDetailsPage?src=calebjacob.near/widget/Posts.Compose
You'll notice the code references context.accountId a few times - this value provides the accountId of the wallet you're currently signed in with. Ideally, the VS Code extension would give you a method for signing in to your wallet. This wallet context would be provided to whatever component you're previewing.
Let me know if you have any questions or would like to discuss further. Thanks!

The newest version actually does login the user during the "Login & Fetch widgets".


Wslg docs

Objective

WSL documentation was out-of-date and potentially misleading. The release of WSLg makes a lot of stuff easier

Solution

Just updating docs for now

NB
I haven't been able to get a full end-to-end GPU on WSL test going yet, but plan to update this documentation again once I have more of a grasp on that

This may have changed, but wslg was only available with windows 11 in the past.

This may have changed, but wslg was only available with windows 11 in the past.

I don't have a windows 10 instance to test on, but my understanding (from the wslg release and the wslg docs) is that it is available on up-to-date windows 10 installs

I'd probably mention something about getting an up to date version of mesa (eg. through the kisak ppa for ubuntu) to run bevy on vulkan instead of gl (since bevy's GL targets GLES 3.0/webgl2 which is extremely limiting).

I took this opportunity to do some research and try running Bevy from WSLg myself. I have now added detailed instructions for it in Bevy Cheatbook: https://bevy-cheatbook.github.io/platforms/windows.html#running-linux-builds-using-wslg


Checkboxes ui styling error on data tables

Hey,
I was exploring yours docs and found a bit strange behaviour on data tables, when selecting row. When row is selected checkbox  is higher than unchecked, thought you might look into that it can scare away some devs I guess.
Selected row:

Unselected row:

Link to example: https://ui.shadcn.com/docs/components/data-table

Also worth mentioning that this happens in Firefox (at least for me). In chrome it looks fine

Same here, display: inline-flex also fixes the thing on Firefox

inline-flex actually isn't perfect either, the checkbox is then nudged too far right and/or enlarged. It's also still sitting with the bottom edge on the baseline rather than hanging slightly below it. And toggling between checked and unchecked you can see the row changing height by 1 pixel.
I don't have good enough CSS chops to figure out the fix I think (I have tried) but I'd like it if there was a proper update on this.

Hello there. I'm also experiencing the same issue. I also noticed that when selected, not only does the check box move up, the row also increases in height by 0.8 pixels. inline-flex does indeed fix the check box moving issue, but the row still gets taller, and as said in the post above, the check is misaligned.

It seems like the amount the row height enlarges is proportional to the window size.

I just had this issue with the row size increasing. I could fix it by changing
<Check className="h-4 w-4" /> to <Check className="h-3.5 w-3.5" />. Haven't checked if this is a solution in general yet, but in my case it worked. But I'll try to take a look.

With display inline-flex still padding botton when is selected =/

In both: firefox and chrome.

You must join inline-flex with mt-2

I fixed this by adding an absolute to the indicator parent component. That might not work for your (other) use cases for a variety of probably obvious reasons.

The solution from @n3mooo works perfectly for me.

I followed @n3mooo's suggestion. For me it went like this:
TableHead:
[&:has([role=checkbox])]:inline-flex [&:has([role=checkbox])]:items-center
TableCell:
[&:has([role=checkbox])]:inline-flex [&:has([role=checkbox])]:items-center h-16

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


Node to calculate line endpoints

new node to calculate endpoints for line feature

Pull request 183-line-endpoints

Please view the pull request

Solved with https://github.com/spatial-data-lab/knime-geospatial-extension/commit/af679f282fd9ea35851ad4eec137e96cc1a9a88f and following


fix: bump github.com/containers/image/v5

Fixing CVE-2024-3727
+--------------------------------+----------------------+----------------+-----------+---------------------+----------------------------------------------------------------------------+
|           COMPONENT            |       VERSION        |      CVE       | SEVERITY  |    FIXED VERSION    |                                    LINK                                    |
+--------------------------------+----------------------+----------------+-----------+---------------------+----------------------------------------------------------------------------+
| github.com/containers/image/v5 |       v5.28.0        | CVE-2024-3727  | IMPORTANT |       5.30.1        |               https://nvd.nist.gov/vuln/detail/CVE-2024-3727               |
+--------------------------------+----------------------+----------------+-----------+---------------------+----------------------------------------------------------------------------+

@0x656b694d I created a PR which should resolve this: https://github.com/stackrox/stackrox/pull/11323
We can bump from v5.29.2 => v5.29.3 https://github.com/containers/image/releases/tag/v5.29.3

Closed in favor of #11323.


build.gradle: stop using << in tasks

The << operation is deprecated. Gradle docs suggest we use doLast instead.

Codecov Report

Merging #1448 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1448   +/-   ##
=========================================
  Coverage     87.16%   87.16%
  Complexity     4031     4031
=========================================
  Files           386      386
  Lines         16190    16190
  Branches       1768     1768
=========================================
  Hits          14112    14112
  Misses         1619     1619
  Partials        459      459

Continue to review full report at Codecov.

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

LGTM


bugs: allow searching by maintainer, inc. project

bugs: improve best match finder
bugs: add --find-by-maintainer option
bugs: add support for filtering targets by StableRequest
bugs: auto extend maintainers with projects

So a new super invocation now is:
pkgdev bugs --find-by-maintainer arthurzam@gentoo.org,-ppc<EMAIL_ADDRESS>--projects --filter-stablereqs

Resolves: https://github.com/pkgcore/pkgdev/issues/157

This is fantastic, thank you!
With this PR applied (sorry, not tried without it):
$ pkgdev bugs
gentoo -- updating git cache: commit date: 2023-12-29
Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.12/pkgdev", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/lib/python3.12/site-packages/pkgdev/scripts/__init__.py", line 48, in main
    run(os.path.basename(sys.argv[0]))
  File "/usr/lib/python3.12/site-packages/pkgdev/scripts/__init__.py", line 40, in run
    sys.exit(tool())
             ^^^^^^
  File "/usr/lib/python3.12/site-packages/snakeoil/cli/tool.py", line 81, in __call__
    ret = self.main()
          ^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/pkgdev/cli.py", line 23, in main
    return super().main()
           ^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/snakeoil/cli/tool.py", line 191, in main
    self.handle_exec_exception(e)
  File "/usr/lib/python3.12/site-packages/snakeoil/cli/tool.py", line 176, in main
    exitstatus = func(self.options, self.out, self.err)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/pkgdev/scripts/pkgdev_bugs.py", line 638, in main
    options.targets = list(_load_from_stdin(out, err))
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/pkgdev/scripts/pkgdev_bugs.py", line 627, in _load_from_stdin
    raise arghparse.ArgumentError(None, "reading from stdin is only valid when piping data in")
argparse.ArgumentError: reading from stdin is only valid when piping data in

I feel like we should get a better error than that.
Also, do you think we could somehow make it open $EDITOR to allow refining of the list before submitting?

This is fantastic, thank you!

:)

With this PR applied (sorry, not tried without it):
...
I feel like we should get a better error than that.

Happens also on master, so not because of this PR. I think this is something with verbose/quite mode, will look. (In theory, it shouldn't print stacktrace without --debug)

Also, do you think we could somehow optionally make it open $EDITOR to allow refining of the list before submitting?

I have here 2 options:

Enable to edit the targets list (before being passed to dependency resolver). This is simple and fast, I can include comments for targets age, works great.
Enable to edit the final bugs "graph". This is harder because of the issue of representing it. A simple list won't be good since this is complicated (multiple packages in bug, defining bug dependencies, etc'). Maybe use here JSON or TOML, but then which object representation to use... Many questions which impact the design.


WebUI frontend

To implement a web ui with real-time job tracking, resources and codes for front-end UI should be bundled.
We have to make decisions for:

Whether or not to use transpilers for js and css

We may have to add transpilers to build dependencies if we use typescript, sass, less, stylus, ...

JS libraries and UI frameworks to use

Although we have webui package, Nemo does not provide direct REST APIs. Moving to ASF JIRA.


Cross compile for ia32 target

This PR uses sysroot for building and cross compiles for ia32 target, making it easier to build arm and ia32 targets.

It seems extremely hard to make the sysroot way work, giving up now.


Spell and stylecheck

Added spell check and style check shortcuts for zsh and vim.

Thanks for the contribution, looks good and checks still pass, so I will merge now.


deploy no longer works - prompts apache page and not guac

deploy no longer works - prompts apache page and not guac
I suspect the latest guac needs to be deployed differently then your current deploy scripts.

To correct I had to rerun the mysql init scripts directly on the database.

I run the MySQL init scripts from the jump server, are you using RDS or did you roll your own DB server on an EC2 instance?


Update default modules in 2024 fall release

Default modules in SAM are far smaller than what is being deployed right now. Behind the meter panels are closer to 400 W, while utility scale modules are 550 or more. See https://www.nrel.gov/docs/fy23osti/87303.pdf for details (there may be a newer report near release time.

Consolidated in https://github.com/NREL/SAM/issues/1855


[SPARK-7324][SQL] Add DataFrame.dropDuplicates

Similar to http://pandas.pydata.org/pandas-docs/stable/generated/pandas.DataFrame.drop_duplicates.html
def dropDuplicates(): DataFrame
def dropDuplicates(subset: Seq[String]): DataFrame

Can one of the admins verify this patch?

@viirya Please test this.

@rxin Please test this.

Jenkins, test this please.

Merged build triggered.

Merged build started.

Test build #31935 has started for   PR 5870 at commit b6f1879.

Test build #31935 has finished for   PR 5870 at commit b6f1879.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31935/
Test PASSed.

@rxin Please retest this.

I think keep the takeFirst parameter would make this better to understand.


suggestion: move lib to another location

A policy refresh will require an update to this library, and a release of the provider as a minimum. Probably testing of the avm-ptn-alz module on top of this too. Even if no golang code needs to change and just the json files.
This could cause quite a large development loop if there are any issues with the policy refresh.
I am wondering if we can relocate the json files, either:

Into their own repo
Into the avm-ptn-alz repo

The move into their own repo may be problematic for anyone with restricted internet access, so think the avm-ptn-alz repo may be the least impact on users. That repo can then specify the location of the folder to the provider. The inner loop for policy update dev and testing will be significantly smaller with the avm-ptn-alz option.
I appreciate this means the provider cannot work end to end in isolation without pointing to this folder, but from a maintenance and release perspective, I am thinking it will reduce toil over time.
Just a thought.

Hi,
Yeah good point.
I originally envisaged this project to be a source of truth for other IaC implementations, let's say somebody wanted to make a Pulumi version.
However I totally get your point and moving the data to the provider is probably the most sensible option given our primary focus is TF.


Adding Docker support

Hi, are you interested in having Docker support to speed up the setup time for Laygo2? I can draft a Dockerfile in this repository.

It would be great if you make a Docker image for laygo2 & sky130. Actually, professor Jaeduk-Han developer of Laygo2 has an interest in this job. Because most Korean uses Windows and setting up this system in WSL takes a lot of effort and is often messed up. If your Docker contains magic, netgen, xschem, ngspice, ngspice-lib, PySpice, etc, it could be very useful for Laygo in Windows.

Cool, I will do that and submit a PR later.

Thanks a lot. https://github.com/niftylab/laygo2_workspace_sky130 this is my main repo for Laygo2 workspace

I almost finished building the Dockerfile (all toolchains, sky130, and partially Laygo2). However, there are some steps that I couldn't fully bake into my Dockerfile due to some bugs in Laygo2's source code (see here). If you are interested in helping me to sort out these issuse, we can hope on a quick call to get those sorted out.

I'm neither familiar with myparser nor version management. And it seems Dr.Jaeduk solved this anyway.

Closing in favor of https://github.com/niftylab/laygo2_workspace_sky130/pull/8


Update accessibility.md

Updated sentence to be a bit more explicit, example code seemed to be outside of Parent class

@sijusamson it's still a bit ambiguous, given it's in the same snippet and not a separate one, could be confusing for some.

@sijusamson it's still a bit ambiguous, given it's in the same snippet and not a separate one, could be confusing for some.

Since these are all subjective nits that don't seem to alter or clarify the original meaning, I'm going to close. But thanks for your suggestions.

Since these are all subjective nits that don't seem to alter or clarify the original meaning, I'm going to close. But thanks for your suggestions.


incorrect error messages when render error is thrown

I am writing my own theme. I kept getting "error:	 File: Template 'index' not found." even though index.html exists. It was caused by the renderer throwing error and reptar was printing a wrong error message. It took me so long to debug this due to the incorrect error message.  Here is an example.
Let's say you have base.html
<!DOCTYPE html>

  <title>{% block title %}{{site.title}}{% endblock %}</title>

    {% include "block/banner.html" %}
    {% block content %}{% endblock %}

  {% include "blocks/footer.html" %}

and index.html had this
{% extends "base.html" %}

{% block content %}

      {% include "blocks/posts.html" %}

{% endblock %}

when I do reptar build, I get the following output
building

✔ Reading theme files.		 (203ms)
✔ Loading plugins.		 (141ms)
✔ Reading files.		 (76ms)
✔ Reading collections.		 (4ms)
✔ Cleaning destination.		 (6ms)
✔ Writing theme files.		 (2ms)
✖ Writing files.
error:	 File: Template 'index' not found.

However, when I go to https://github.com/reptar/reptar/blob/master/lib/file.js#L284 and print the actuall error message, here is the output
✔ Reading theme files.		 (208ms)
✔ Loading plugins.		 (151ms)
✔ Reading files.		 (71ms)
✔ Reading collections.		 (5ms)
✔ Cleaning destination.		 (6ms)
✔ Writing theme files.		 (2ms)
⠋ Writing files.		(/Users/mohammadm/Devel/reptar-site/_themes/reptar-theme-boxes/templates/index.html)
  Template render error: (/Users/mohammadm/Devel/reptar-site/_themes/reptar-theme-boxes/templates/index.html)
  Template render error: (/Users/mohammadm/Devel/reptar-site/_themes/reptar-theme-boxes/templates/index.html)
  Template render error: (/Users/mohammadm/Devel/reptar-site/_themes/reptar-theme-boxes/templates/index.html)
  Error: template not found: block/banner.html
(/Users/mohammadm/Devel/reptar-site/_themes/reptar-theme-boxes/templates/index.html)
  Template render error: (/Users/mohammadm/Devel/reptar-site/_themes/reptar-theme-boxes/templates/index.html)
  Template render error: (/Users/mohammadm/Devel/reptar-site/_themes/reptar-theme-boxes/templates/index.html)
  Template render error: (/Users/mohammadm/Devel/reptar-site/_themes/reptar-theme-boxes/templates/index.html)
  Error: template not found: block/banner.html
✖ Writing files.
error:	 File: Template 'index' not found.

Therefore Correct message should be Error: template not found: block/banner.html
On line https://github.com/reptar/reptar/blob/master/lib/file.js#L284 instead of searching for "'template not found'" and printing a custom message, I suggest extracting the line containing error and print it instead.

Awesome find, thank you! Just pushed an update to resolve this!


Query Analysis

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes
• The QueryAPI now includes a parameter called analyze.  When set to true, the Analyze() method of the query returns query analysis. This analysis is represented by the AnalyzeOutputNode structure, as mentioned in #289, and it is included in the response.
Screenshots

Verification
Tested locally

Let's update promql-engine here with your commit now 🙂 go get github.com/thanos-io/promql-engine@99d2be3bb060450a6d2a039a28d9562876c4c204

Seems like UI tests care failing: https://app.circleci.com/pipelines/github/thanos-io/thanos?branch=pull%2F6515. @nishchay-veer could you take a look?

TestQFEEngineExplanation/passes_range_query_to_Thanos_engine_and_returns_explanation fails. The test probably needs to be updated to use the new API? @nishchay-veer

@nishchay-veer linters are failing, could you please remove the now unused return value?

@nishchay-veer could you also please fix the conflicts? :pray:

@nishchay-veer I think your local main branch was stale and your last commit just nuked the latest updates :sweat:

Not working with make assets :(


Save as image

Hello! Can I save chart as image, not html page? Thanks!

https://github.com/ECharts-Java/ECharts-Java/issues/61#issuecomment-1257724828

Please see this issue https://github.com/ECharts-Java/ECharts-Java/issues/61


Nova 4.0

Hey, any chance to update this package to Nova 4.0?
The issue is the TextWithSlug field does not show up on any screen.

Hi There, any update on this?

In the meanwhile you could use the new native depensOn to create a replacement for the functionality of this package:
Text::make(__('Name'), 'name'),

Text::make(__('Slug'), 'slug')
    ->dependsOn(
        ['name'],
        function(Text $field, NovaRequest $request, FormData $formData) {
            if ($formData->name <> optional($request->resource()::find($request->resourceId))->name) {
                $field->value = Str::slug($formData->name);
                $field->help(config('app.url') . '/categories/' . $field->value);
            }
        }
    ),

Hi all!
I don't have a nova 4 license yet, so am not able to test it.
If anyone wants to provide a PR, you are very welcome to.
Thank you very much and have a great day!

+1

@sanderbaas That example doesn't work as I would expect NovaSlugField works but thanks for the snippet
@tomhatzer did you get a license?

@tomhatzer I just openend a PR that works well.

@tomhatzer any update on that PR? 🤔

@juergenZeindlinger if you can test it and can confirm that it works I‘m willing to approve and merge it :) I don‘t work with Nova anymore and don‘t have a license for v4.

@tomhatzer I can't but @jmverges mentioned that his PR works well 🤔 Don't know


Add nukable check + nukable check implementation for transit gateway

Description
Fixes #000..

TODOs
Read the Gruntwork contribution guidelines.

[ ] Update the docs.
[ ] Run the relevant tests successfully, including pre-commit checks.
[ ] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
[ ] Include release notes. If this PR is backward incompatible, include a migration guide.
[ ] Attention Grunts - if this PR adds support for a new resource, ensure the nuke_sandbox and nuke_phxdevops jobs in .circleci/config.yml have been updated with appropriate exclusions (either directly in the job or via the .circleci/nuke_config.yml file) to prevent nuking IAM roles, groups, resources, etc that are important for the test accounts.

Release Notes (draft)

Added / Removed / Updated [X].
Migration Guide

CICD building fails with
Cannot find<EMAIL_ADDRESS>in the orb registry. Check that the namespace, orb name and version are correct.


Fix bug where listeners where stacking each time the view was created

Using a button as an example. Every time a button is created, it subscribes itself to an onTap message given by the user, with a result closure. This closure was being subscribe to the mailbox, where it would reside. This would cause each time you created a button, a new subscription was being register, even when the older was still in the mailbox.
This PR fixes so that every time a view is created, the mailbox subscriptions are unregistered so that the only subscriptions are the ones being created by the components in the current view

@guidomb


To support DV 215 - Currency to text

Issue https://github.com/microsoft/Power-Fx-Dataverse/issues/215.

✅ No public API change.


Navigator docs are incomplete

The Navigator docs say A widget that manages a set of child widgets with a stack discipline., so this induces us to believe the Navigator will add some sort of hierarchy to the pushed Routes, but anyone that tried to get an InheritedWidget from inside a new Route will get an error (unless the InheritedWidget is on top of the MaterialApp).
As this article shows, one could expect our app to look like this:
> School App [App Context]
  > Student [Student Context]
    > Grades
    > Bio
  > Teacher [Teacher Context]
    > Courses
    > Bio

But Navigator will actually make it look like this:
> School App [App Context]
  > Student [Student Context]
  > Student Grades
  > Student Bio
  > Teacher [Teacher Context]
  > Teacher Courses
  > Teacher Bio

This behavior is misleading and induces errors (I spent 2 hours trying to understand why my Provider wasn't working once I navigated further), so it should be added to the docs.

I can't see why it is confusing, it specifically says in stack discipline instead of in tree discipline. The first diagram is a tree structure while the second one is a stack.

Because many of us think each route will be stacked on top of its previous route, the image on our heads can be something close to a wrapping, so we will have access to its InheritedWidgets, which we do not have.


Add support for starting a preconfigured Firefox instance via browser.start command.

Description
browser.start command will now allow for a browser parameter defaulting to "chrome". (Refer #5247)
Checklist

[x] I have updated tests where applicable.
[x] I have added an entry to the CHANGELOG.

I get this popup here when running browser.start firefox Can we skip that somehow?

This is caused by the --safe-mode flag, I'll remove it.

Are there additional Firefox prefs we can configure to disable telemetry spam / update checks / ...?

I have tried experimenting with a lot of preferences that seem to reduce a tiny amount of telemetry, but requests to *.services.mozilla.com and a few other domains just can't seem to be turned off, perhaps we could drop requests to matching domains in mitmproxy?

Thanks for the review! I don't have any more changes planned, so we're good to merge :)
About filtering the remaining telemetry traffic, I think it would just add complexity without much gain, and most users might actually want to see those requests.


Consider a better name?

Is it just me, or is VOC immediately associated with slavery / private army as much as global commerce / international company funded by private capital?
Could there perhaps be a better name?

@dimaqq I agree.

As one data point: personally, I don't have that association at all, mostly because when I learnt about Dutch East India Company in school, it was never referred to its Dutch name nor its acronym.
The C in VOC for me will always stand for Compiler. :)
Vanguard Obscure Compiler
Virtuous Output Compiler
Viable Okay Compiler
Very Odd Compiler
Various Objects Compiler
Verbose Obsessive Compiler
...


WIP give up dispatching on a non-retriable error

Before going further I'd like to get some early feedback on this.
Here's an initial implementation for the executor API to support detecting non-retriable errors.
As you can see, the new enum ResponseErrorType defines 3 different scenarios:

BAD_REQUEST

dispatch shouldn't be attempted at all
so far I don't know of other use cases for this than the case of "execution already running"

UNKNOWN

dispatch should be attempted maybe on another executor, or even this one, but it won't be too likely to succeed despite the retry. It's better to stop dispatching after a couple of retries and give room to the next executions in the queue, because most likely there's something bad in the execution itself

SERVICE_UNAVAILABLE

should keep retrying as much as azkaban.maxDispatchingErrors says

In addition to these, if the HTTP request status != 2xx, assume SERVICE_UNAVAILABLE on the client side.

@jamiesjc could you comment, please?

Pull Request Test Coverage Report for Build 4136

0 of 26 (0.0%)  changed or added relevant lines in 4 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.02%) to 35.95%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

azkaban-common/src/main/java/azkaban/executor/ConnectorParams.java
0
4
0.0%

azkaban-common/src/main/java/azkaban/executor/ExecutorResponseErrorException.java
0
7
0.0%

azkaban-exec-server/src/main/java/azkaban/execapp/ExecutorServlet.java
0
7
0.0%

azkaban-exec-server/src/main/java/azkaban/execapp/FlowRunnerManager.java
0
8
0.0%

Files with Coverage Reduction
New Missed Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/ConditionalWorkflowUtils.java
1
89.29%

azkaban-exec-server/src/main/java/azkaban/execapp/FlowRunnerManager.java
1
21.8%

azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
2
76.67%

Totals

Change from base Build 4131:
-0.02%

Covered Lines:
10496

Relevant Lines:
29196

💛  - Coveralls

What's the ultimate goal of detecting non-retriable errors?

To not accidentally dispatch the same execution multiple times in parallel (on different executors)
For the dispatching queue to not get stuck too long in trying to dispatch one problematic execution.

This only really matters if azkaban.maxDispatchingErrors is set to some high value (to prevent giving up dispatching too quickly in case of transient errors)

To not give up dispatching an execution just because the executor that was tried is shutting down

Hi @juhoautio, I still have some questions:

To not accidentally dispatch the same execution multiple times in parallel (on different executors)

Can you give an example of how this scenario could happen?

For the dispatching queue to not get stuck too long in trying to dispatch one problematic execution.

By default, azkaban.maxDispatchingErrors is set to the number of active executors, which is not a big number. I don't see a problem here at least for our system. Is it currently a concern for you guys?

To not give up dispatching an execution just because the executor that was tried is shutting down

Web server should always pick the best executor based on the capacity, CPU or memory info on all the available executors. If an executor is shut down, then the web server could not get any update from it and would switch to another executor and dispatch. Isn't that the current behavior?

To not accidentally dispatch the same execution multiple times in parallel (on different executors)

Can you give an example of how this scenario could happen?

Yes, I admit that it's about a rare corner case.

az-web sends dispatch request to executor 1
executor 1 starts running the execution and returns OK
due to some transient network error az-web can't read the HTTP response

the basic case would be a socket read timeout

az-web tries to dispatch the execution again

considering that there are more than 1 active executors, az-web tries to dispatch to another executor

another executor accepts the execution
result: the same execution is now running on two different executors

Now, to fix this properly, az-web should actually check the DB after a failed request (this is only needed if it managed to connect & send the request, but failed to read response). The other executor wouldn't know to return ALREADY_RUNNING any way, so having ALREADY_RUNNING doesn't help against protecting dispatching the same execution on multiple executors.
ALREADY_RUNNING response makes it easy to reliably dispatch an execution exactly once when using a single active executor, but it is kind of redundant if DB has to be checked any way after a failed request.

For the dispatching queue to not get stuck too long in trying to dispatch one problematic execution.
By default, azkaban.maxDispatchingErrors is set to the number of active executors, which is not a big number.

I don't see a problem here at least for our system. Is it currently a concern for you guys?

Correct. For us the ideal setup is to allow a low number of "best-effort" max dispatch attempts & a really high max attempts for "always retriable" executions. Why is this ideal? Because this way dispatching of scheduled executions won't be skipped if we have executor downtime that isn't resolved before a few hours. If we hit such downtime and devops fixes the broken executor, it will be quire hard for devops to manually trigger all the scheduled executions that were missed during the executor downtime. Related issue is that az-web doesn't currently support catchup of scheduled executions if az-web itself has been down. That should be fixed as well to guarantee that no scheduled executions are ever missed.

If an executor is shut down, then the web server could not get any update from it and would switch to another executor and dispatch. Isn't that the current behavior?

Ok, it seems likely to me that az-web never tries to dispatch to an executor that is shutting down. But it can't be ruled out. What I know for sure is that executor does reject a dispatch call if it's shutting down at the time. For completeness az-web should recognize that error type as "forever retriable" ie. keep trying to dispatch for next executor until it finds one that isn't shutting down :) Sorry, I didn't bother to investigate deeply if it's ever possible for az-web to try to dispatch on a executor that's shutting down. Given the asynchronous nature of updating executor stats etc., I would tend to think that this can happen.

Now, to fix this properly, az-web should actually check the DB after a failed request

Do you mean checking the flow status in the DB? It might still be in PREPARING status at the time when the check happens if there is any delay in starting the flow on the executor.

The other executor wouldn't know to return ALREADY_RUNNING any way, so having ALREADY_RUNNING doesn't help against protecting dispatching the same execution on multiple executors.

True.

Because this way dispatching of scheduled executions won't be skipped if we have executor downtime that isn't resolved before a few hours.

If one executor is down, there are still other available executors ready for dispatching. If all of them are down in the worst case, the scheduled flows won't be executed during the downtime for sure. It reached handleNoExecutorSelectedCase and the flows will still be enqueued. Once the executors are brought back to normal, the missed executions can still be picked up from the queue.

Related issue is that az-web doesn't currently support catchup of scheduled executions if az-web itself has been down.

Right, the scheduled executions will be missed during the downtime of az-web.

For completeness az-web should recognize that error type as "forever retriable" ie. keep trying to dispatch for next executor until it finds one that isn't shutting down :)

Even if the error type is not specified, az-web will still try to dispatch for next executor until it finds the available one. If in the extreme case where all the executors are down and az-web still tries to dispatch to them, then the flow will be finalized in the end. I'm not sure if that's the scenario you are concerned about.
We've always wanted to simplify the dispatching logic and the updater thread behavior. If there are so many corner cases we need to consider and patch fixes on top, it might indicate that the original design itself needs to be changed towards some other direction.

Related issue is that az-web doesn't currently support catchup of scheduled executions if az-web itself has been down.

Right, the scheduled executions will be missed during the downtime of az-web.

I thought the scheduled executions were saved in DB and will resume after the web server is back.  We rely on this to not miss scheduled executions during deployment. Did I miss something?

@jamiesjc @HappyRay thanks for taking the time to look into this.

Do you mean checking the flow status in the DB? It might still be in PREPARING status at the time when the check happens if there is any delay in starting the flow on the executor.

@jamiesjc yes, but I was assuming:

Delay in updating the status to RUNNING won't be too long if executor has accepted the execution
After a failed request az-web will have a short but long enough grace period before checking the DB

If one executor is down, there are still other available executors ready for dispatching.

@jamiesjc if any executor is unreachable, it's quite likely that all of them get hit by the same problem – for example a network outage or congested DB. Do you know more about handleNoExecutorSelectedCase? To me it has always seemed like that isn't ever reached unless there are 0 active executors to begin with. But in that case az-web would actually refuse to start? My understanding is that as long as there's at least 1 active executor, if azkaban.maxDispatchingErrors is reached az-web gives up dispatching – it doesn't re-queue the execution. handleNoExecutorSelectedCase might be dead code.
As such re-queueing in case of too many dispatch errors sounds good, because it would ensure that nothing gets discarded. But it will mess up the order of executions. That might be a problem (but I'm not sure what would happen to pipelined executions if the executions are submitted in an unexpected order?). Unless we can deduce that submission order doesn't matter, I would rather avoid shuffling.

I thought the scheduled executions were saved in DB and will resume after the web server is back

@HappyRay that would be perfect actually. Does that feature really exist (or does it work :)), because I have some recent experience where schedules were missed because az-web was down and I couldn't find the expected executions, not even in any abnormal state like PREPARING or FAILED. Of course I can rather easily test it – will do.

Even if the error type is not specified, az-web will still try to dispatch for next executor until it finds the available one. If in the extreme case where all the executors are down and az-web still tries to dispatch to them, then the flow will be finalized in the end. I'm not sure if that's the scenario you are concerned about.

@jamiesjc, again, I don't regard "all executors down" that much more extreme than "one executor down". Btw our current setup is 1 web + 1 active executor + 0-N inactive executors. We could have more active executors for additional availability, but that alone wouldn't guarantee much.

If there are so many corner cases we need to consider and patch fixes on top, it might indicate that the original design itself needs to be changed towards some other direction.

True that. But also the reality is that it seems like fixing smaller bugs and corner cases one at a time is an easy way to contribute and improve Azkaban's reliability. And maybe there aren't that many corner cases. The fixes that I've proposed in this discussion would already seem like a big plus from my perspective.

@jamiesjc's understanding is correct.

@jamiesjc what do you think? I know you commented about complexity, but to me this doesn't seem too complex. There aren't so many corner cases.
I think I managed to craft a bit nicer plan for how to implement this.
Executor side:

If executor is shutting down, return 503 Service Unavailable HTTP status code instead of 200 OK with "error" in the response payload
If execution is already running, return 200 OK – dispatcher gets the confirmation that execution has been dispatched (I think it's actually a bug that this situation leads into an error currently)

Dispatcher side:

Don't give up dispatching if response is service unavailable or if connection times out
Give up dispatching immediately if executor returns 200 OK with "error" in the response payload.

Optionally a couple of retries could be given even in this case, because maybe there's a small chance that it's not a bad request per se. Any way the cases where it makes sense to not give up as quickly are the ones where 200 OK can't be received in the first place.

I think these rules should nicely cover all cases. There's no need to add a new enum ResponseErrorType that I have proposed in this PR. It's replaced by leveraging 503 Service Unavailable 503 & by changing "already running" case to return 200 OK with "ok" payload.

One chunk at a time seems like a good approach. First stab at it: https://github.com/azkaban/azkaban/pull/2023.


Change read_into to readinto.

The I2CDevice function read_into is deprecated. Change to using readinto:
http://circuitpython.readthedocs.io/projects/bus_device/en/latest/adafruit_bus_device/index.html#module-adafruit_bus_device.i2c_device

Closing. Fixed with this PR:
https://github.com/adafruit/Adafruit_CircuitPython_TSL2561/pull/6


array mapping wraps destination in an unwanted array

As shown in my codesandbox, I tried to map as suggested in your readme, but I didn't find a way to remove the wrapping array from the destination object
const src = {
  foo: [{ bar: 4 }, { bar: 33 }]
};

const mapper = {
  "foo[].bar": "[]",
}

const res = map(src, mapper);
// res = [ [ 4, 33 ] ]
// i would expect [4, 33]

I would not expect to have a wrapping array in the result, and this behavior is a big restriction IMHO, because, for example, it seems impossible to use "append" + operator (useful to me) in order to build a collection from this object:
const src = {
  foo: [{ bar: 4 }, { bar: 33 }],
  bifoo: [{ bar: 77 }, { bar: 97 }]
};

const mapper = {
  "foo[].bar": "[]+",
  "bifoo[].bar": "[]+"
}

const res = map(src, mapper);
// res = [ [ 4, 33 ] ]
// i would expect [4, 33, 77, 97]

const mapper2 = {
  "foo[].bar": "num[]+",
  "bifoo[].bar": "num[]+"
}

const res = map(src, mapper2);
// res = { "num": [ [ 4, 33 ], [ 77, 97 ] ] }
// i would expect {"num": [4, 33, 77, 97] }

Why array items are not processed one at a time? Is it possible to easily achieve what I would like to?

Facing the same issue. Have you found any solution to this?

I see your point.  The current functionality of + is specified as:  stop what you are doing and add the data onto an array, for each item that has the +.  I am not sure of the use case for this.  @wankdanker may want to weigh in.  I modified so that the + is specified as:  add the results of this key to the existing array.  If @wankdanker wants to leave as is, I'll back out this change.


patch_embed related questions.

Hi, Thanks for providing the code! I have a couple of questions regarding patch_embedding.

in https://github.com/whai362/PVT/blob/v2/segmentation/pvt.py#L148, the last layer you added one more embed feature than the num_patches but it seems this extra feature has no where to be used. You explicitly removed it in https://github.com/whai362/PVT/blob/v2/segmentation/pvt.py#L202. Is this design for some specific purpose? (backward compatibility?)
https://github.com/whai362/PVT/blob/v2/segmentation/pvt.py#L183  why specifically compare with patch_embed1? Is this not supposed to compare to each patch_embed?

I have the same confusion about your questions. Did you solve them?

@zijunwei
I have the same confusion about your questions. Did you solve them?


[Feature Request] Set registry for scoped package

Hi,
Is it possible to add the scope of package in .npmrc file?
For example, the .npmrc file generated should look like this:
@myscope:registry=https://<registry>/
<registry>:_authToken=XXX

Hello, I am add this in now


Add UIGraphicsImageRenderer extension.

UIGraphicsImageRenderer has support for directly exporting JPEG and PNG data, why not HEIC?

Nice API. Maybe I should add this to my back port off UIGraphicsRenderer
shaps80/GraphicsRenderer

Added this this morning


einops version

https://github.com/FailSpy/abliterator/blob/7a86564d36f3831de9428000a9164e9b14992898/requirements.txt#L2
The version should be 0.8.0 i think.
Source: https://pypi.org/project/einops/#history

want to make a PR so I can credit you for this?

Related PR: https://github.com/FailSpy/abliterator/pull/21

Closed thanks to #21 :)


test-branch/execute-job/wrong-commit-sha-on-pr/6aaa1c11-a228-4389-a38a-af27f9a1da35

PR for testing 8e385a76fd9ac7a3930f72397acc367777ae0638

/canonical/self-hosted-runners/run-workflows 3ab3d261be78645af0889d4c49ae7712aeebcb50


Search in header should not wrap anchor around button sematically

A Next link is wrapped around Button component to seemingly accomplish a "button"-look for the link.
But semantically a anchor tag should not contain an button element. Button should be used with onClick event.
This results in an blue outline for the anchor when tabbing to the search, instead of the focus design meant for button( that you get when tabbing one more time into the button element)
Should implement as suggested in eds;
A special note about nextLink: The href type from this component conflicts with the native href type, therefore it is recommended to use the legacy behavior in this case, or alternatively ts-ignore.
import NextLink from 'next/link'
import { Button } from '@equinor/eds-core-react'

<NextLink href="/about" passHref legacyBehavior>
  <Button as="a">About</Button>
</NextLink>

This issue also applies to the portrait cards, should maybe run a search for nextlink wrappers with button look

Thanks @BorghildSelle - this is approved :smile:


Controller not connecting with Turtlebot4

Robot Model
Turtlebot4 Standard
ROS distro
Humble
Networking Configuration
Discovery Server
OS
Ubuntu 22.04
Built from source or installed?
Installed
Package version
[turtlebot4_standard_humble_1.0.0.zip] (http://download.ros.org/downloads/turtlebot4/turtlebot4_standard_humble_1.0.0.zip)
Type of issue
Other
Expected behaviour
I want to connect the controller with turtlebot4 via bluetooth after installing fresh image of Ubuntu in the Raspberry Pi 4.
Actual behaviour
Controller does not connect with turtlebot4 and shows blues error.

Error messages
Failed to connect: org.blues.Error.Failed br-connection-create-socket

To Reproduce

Other notes
I did “untrust”, “remove”, “scan on”, “trust”, “Pair”, “connect” but still the problem is there. I have tried connecting so many times but no success. Even tried resetting the controller. I talked to clearpath and they advised me to keep trying connecting until it connects but it doesn't.

Hi @azhar-maxtech
Can you try this: https://turtlebot.github.io/turtlebot4-user-manual/troubleshooting/faq.html#3-no-default-controller-available
If it does not work - please share the full terminal outputs from the untrust / remove / trust / pair and connect commands being run in the terminal.

Hi @azhar-maxtech - any update on your issue?
Best regards,
Rusty

Closing due to inactivity.


ARM: Python bindings build fails on Raspbian

Raspbian has both python2.7 and python3.x installed. If Python bindings are enabled, the build fails due to Cmake picking up python3.x by default.

Fixed by https://github.com/3dtof/voxelsdk/commit/9a5a179e86a0a52f98294fb5c898bd22197f72e7


Add unit tests for validating repository server secrets [PR#1]

Change Overview
This PR is 1st of the chain of PRs for adding unit tests for validating secrets. This PR tests the newly added functions in secrets package.
Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[ ] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Issues

fixes #issue-number

Test Plan

[ ] :muscle: Manual
[x] :zap: Unit test
[ ] :green_heart: E2E

Test Plan:
- Tests getLocationtype function
- Tests validation for GCP location secret type

@kale-amruta it's better to add the test run result in the test plan of the PR


[LayoutReader] RuntimeError: "pow" not implemented for 'Half'

Describe the bug
Model I am using LayoutReader
The problem arises when using:

[x] the official example scripts: (give details below)
[ ] my own modified scripts: (give details below)

A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Download test dataset
Run the step 4 Decoding
Error is thrown

Traceback (most recent call last):
  File "decode_seq2seq.py", line 344, in <module>
    main()
  File "decode_seq2seq.py", line 277, in main
    traces = model(input_ids, token_type_ids,
  File "/home/augustinas/.pyenv/versions/generic/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/augustinas/open-source/unilm/layoutreader/s2s_ft/modeling_decoding.py", line 1221, in forward
    self.bert(x_input_ids, curr_token_type_ids, curr_position_ids, curr_attention_mask,
  File "/home/augustinas/.pyenv/versions/generic/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/augustinas/open-source/unilm/layoutreader/s2s_ft/modeling_decoding.py", line 1113, in forward
    embedding_output = self.embeddings(
  File "/home/augustinas/.pyenv/versions/generic/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/augustinas/open-source/unilm/layoutreader/s2s_ft/modeling_decoding.py", line 399, in forward
    embeddings = self.LayerNorm(embeddings)
  File "/home/augustinas/.pyenv/versions/generic/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/augustinas/open-source/unilm/layoutreader/s2s_ft/modeling_decoding.py", line 228, in forward
    s = (x - u).pow(2).mean(-1, keepdim=True)
RuntimeError: "pow" not implemented for 'Half'

Expected behavior
A clear and concise description of what you expected to happen.

Platform: Ubuntu 20.04
Python version: Python 3.8.9
PyTorch version (GPU?): torch-1.7.1 (CPU)

We suggest you to run the code with GPUs, since the code was only tested with GPUs and some unexpected errors may occur with CPUs.

removing arg --fp16 you can run on cpu


pip-compile gives different result on macOS and Debian

Environment Versions
1. OS
macOS:
~ ❯ sw_vers
ProductName:		macOS
ProductVersion:		13.6
BuildVersion:		22G120
~ ❯

and:
python:3.9.16-slim docker image
root@726959d3b1ba:/# cat /etc/issue
Debian GNU/Linux 11 \n \l

2. Python
macOS:
/tmp ❯ python -V
Python 3.9.16

and:
python:3.9.16-slim docker image
root@bdc7b5caa828:/# python -V
Python 3.9.16

3. PIP
macOS:
/tmp ❯ pip -V
pip 23.3.1 from /private/tmp/.venv/lib/python3.9/site-packages/pip (python 3.9)

and:
python:3.9.16-slim docker image
root@bdc7b5caa828:/# pip -V
pip 23.3.1 from /usr/local/lib/python3.9/site-packages/pip (python 3.9)

4. pip-tools
macOS:
/tmp ❯ pip-compile --version
pip-compile, version 7.3.0

and:
python:3.9.16-slim docker image
root@bdc7b5caa828:/# pip-compile --version
pip-compile, version 7.3.0

Steps to replicate

Use python 3.9.16
Use pip 23.3.1
Use the following requirements.in file:

jira==3.0.1
sqlalchemy==1.4.48

Run pip-compile -o requirements.txt --strip-extras requirements.in on both OSes
Compare both generated requirements.txt

Expected result
Both generated requitements.txt should contain the same packages and versions.
Actual result
For macOS:
#
# This file is autogenerated by pip-compile with Python 3.9
# by the following command:
#
#    pip-compile --output-file=requirements.txt requirements.in
#
certifi==2023.7.22
    # via requests
charset-normalizer==3.3.1
    # via requests
defusedxml==0.7.1
    # via jira
idna==3.4
    # via requests
importlib-metadata==6.8.0
    # via keyring
jaraco-classes==3.3.0
    # via keyring
jira==3.0.1
    # via -r requirements.in
keyring==24.2.0
    # via jira
more-itertools==10.1.0
    # via jaraco-classes
oauthlib==3.2.2
    # via requests-oauthlib
requests==2.31.0
    # via
    #   jira
    #   requests-oauthlib
    #   requests-toolbelt
requests-oauthlib==1.3.1
    # via jira
requests-toolbelt==1.0.0
    # via jira
sqlalchemy==1.4.48
    # via -r requirements.in
urllib3==2.0.7
    # via requests
zipp==3.17.0
    # via importlib-metadata

# The following packages are considered to be unsafe in a requirements file:
# setuptools

For python:3.9.16-slim docker image:
#
# This file is autogenerated by pip-compile with Python 3.9
# by the following command:
#
#    pip-compile --output-file=requirements.txt requirements.in
#
certifi==2023.7.22
    # via requests
cffi==1.16.0
    # via cryptography
charset-normalizer==3.3.1
    # via requests
cryptography==41.0.5
    # via secretstorage
defusedxml==0.7.1
    # via jira
greenlet==3.0.0
    # via sqlalchemy
idna==3.4
    # via requests
importlib-metadata==6.8.0
    # via keyring
jaraco-classes==3.3.0
    # via keyring
jeepney==0.8.0
    # via
    #   keyring
    #   secretstorage
jira==3.0.1
    # via -r requirements.in
keyring==24.2.0
    # via jira
more-itertools==10.1.0
    # via jaraco-classes
oauthlib==3.2.2
    # via requests-oauthlib
pycparser==2.21
    # via cffi
requests==2.31.0
    # via
    #   jira
    #   requests-oauthlib
    #   requests-toolbelt
requests-oauthlib==1.3.1
    # via jira
requests-toolbelt==1.0.0
    # via jira
secretstorage==3.3.3
    # via keyring
sqlalchemy==1.4.48
    # via -r requirements.in
urllib3==2.0.7
    # via requests
zipp==3.17.0
    # via importlib-metadata

# The following packages are considered to be unsafe in a requirements file:
# setuptools

Diff:
8a9,10
> cffi==1.16.0
>     # via cryptography
10a13,14
> cryptography==41.0.5
>     # via secretstorage
12a17,18
> greenlet==3.0.0
>     # via sqlalchemy
18a25,28
> jeepney==0.8.0
>     # via
>     #   keyring
>     #   secretstorage
26a37,38
> pycparser==2.21
>     # via cffi
35a48,49
> secretstorage==3.3.3
>     # via keyring

I don't have an idea why the generated files are different but I'd expect them to be the same. The problem started when I added the generated files (on macOS) to source control and it failed in GH action on GH CI. For the very beginning I thought it is related to python and pip versions - when I unified them (3.9.16 vs 3.9.18 for python) some differences disappeared. Then I thought pre-commit is to be blamed, finally it turned out that different requirements.txt files are generated even with the same versions of tools being used. The only difference is the OS.

This is expected, as packages can specify different dependencies according to the current platform or Python version. Notice that keyring specifies a bunch of dependencies this way.

Thanks @AndydeCleyre! What is the suggested course of action here then? Should I wrap pip-compile invocation in some docker container or can handle it differently?

@Opalo it depends on your use-case. If it's an app deployed to a single well-defined environment, you might want to make sure you use the same env to manage the logfiles. If you have a library and test against a matrix of envs, you may opt to have a bunch of constraint files per each combo of Python, OS and arch. The latter would require some wrapper script to select different constraint files in different envs, I'm experimenting with such an approach @ https://github.com/cherrypy/cheroot/tree/main/requirements for quite a while and I like how it allows me to keep the CI green with no surprise transitive dependency bumps and transparent package updates.

Oh, and make sure to study the docs carefully. I think they can provide you with more insight.

Thanks for all the hints! I've wrapped the generation into a docker container. And it all works fine.


I am interested in using your game on my website. Could you add a license file like the MIT one in this pull request so I know how you want your software used?

thanks, i've added the license.
please provide a link to your website if possible, though it's not necessary


epic (continuous improvement): add fuzzing

@zmalatrax this issue needs scoping and will need a decent amount of architecture design
### Tasks
- [ ] find best fuzzing framework in JS/TS (compatible with bun)

Please can I work on this ?

HI @Eikix is this still open for contribution ?


fixed issue where lines are draw b/c there is only one trade in the t…

…ime range so price range could not be determined
https://app.clubhouse.io/augur/story/13801/missing-lines-from-candlestick-chart

Pull Request Test Coverage Report for Build 863

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 65.513%

Totals

Change from base Build 861:
0.0%

Covered Lines:
3482

Relevant Lines:
4811

💛  - Coveralls