What about Azure CLI?

Could we get some examples for Azure CLI please?

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

ID: 9492cedc-cea0-af9d-29a0-52cbca8c5e21
Version Independent ID: 969a8654-8f95-d5de-351d-73c8e02e5d3a
Content: Automatic, geo-redundant backups - Azure SQL Database
Content Source: articles/sql-database/sql-database-automated-backups.md
Service: sql-database
Sub-service: backup-restore
GitHub Login: @anosov1960
Microsoft Alias: sashan

@srudin We are checking this and we will get back to you.

@srudin - Please convey for which action you are looking for the CLI example. Few of the CLI examples are in this document  - https://docs.microsoft.com/en-us/azure/sql-database/sql-database-cli-samples?tabs=single-database for Azure SQL DB.
Hope this helps.

What I'd like to is to configure the long term retention period for a database by using Azure CLI. It seems I put the question to the wrong documentation page as this one would have been more adequate: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-long-term-backup-retention-configure
However I can find someone else asking for this already and it seems not to be available: https://github.com/Azure/azure-cli/issues/10723
I'd really appreciate Azure CLI to offer this.

@srudin As the functionality is not present currently, the correct way to provide feedback and get Product Group response would be to post your feedback here.
https://feedback.azure.com/forums/217321-sql-database
The feedback will be checked by Product Team and updates will be provided. This channel is for providing feedback on docs and their quality.
Hope this helps. We are closing this thread for now.


Adding feeding performance notebook

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
Took a step back and adopted a more scientific approach trying to compare apples to apples, and using the VespaAsync as it already is implemented, resisting the urge to change the library code (for now) 😆
Made it more adaptable, by defining parameters to be explored at the top
num_docs = [1000, 10_000, 100_000]

params_by_function = {
    "feed_sync": {
        "num_docs": num_docs,
        "max_connections": [16, 64],
    },
    "feed_async": {
        "num_docs": num_docs,
        "max_connections": [16, 64],
        "num_concurrent_requests": [1000, 10_000],
    },
    "feed_iterable": {
        "num_docs": num_docs,
        "max_connections": [64, 128],
        "max_workers": [16, 64],
        "max_queue_size": [1000, 10000],
    },
}

Had to reduce num_docs to only 1000 as running the notebook made Screwdriver time out. Added the larger experiment plots as static images to the notebook instead.

Great! Consider the following optional changes
 If we want to promote pyvespacli package we should put it under our wings, it's currently a personal project

I am talking to Frode about how we can do transfer ownership etc. Not promoting it yet.

* Remove the SSL warning

✅

* Explain why we use a dummy schema with summary only and that as we add more features, we expect that the Vespa backend becomes the bottleneck

✅

* It seems like an unfair comparison to me as the vespa cli works with a single json file already consumed from S3, while the pyvespa parts are operating over a streamed response from S3? In that respect it might be that the conclusion is a bit off, in my experience there is not 2 orders of magnitude difference

Yeah, that´s true. Added a note about this, and pointed out it is an unfair comparison.

* Consider writing more about why the synch _feed one and one operation is very latency sensitive (100 ms latency end to end => 10 feed operations per sec), 50 ms, =>20 etc.

Added some text with a practical example like this.

Great! Consider the following optional changes
* If we want to promote pyvespacli package we should put it under our wings, it's currently a personal project

* Remove the SSL warning

* Explain why we use a dummy schema with summary only and that as we add more features, we expect that the Vespa backend becomes the bottleneck

* It seems like an unfair comparison to me as the vespa cli works with a single json file already consumed from S3, while the pyvespa parts are operating over a streamed response from S3? In that respect it might be that the conclusion is a bit off, in my experience there is not 2 orders of magnitude difference

* Consider writing more about why the synch _feed one and one operation is very latency sensitive (100 ms latency end to end => 10 feed operations per sec), 50 ms, =>20 etc.

Need new approval after implementing feedback @jobergum @kkraune 🙏

Great! 💯


Proposal 2 Options

When the webhook was enabled add these options:

Dont resend update when you receive none 200 response

Lets say i have these in my code:
$this->sendMessage('Waiting...'); //send message to current user to wait

--> i have bug here, so responding to telegram with none 200 http response

At this point telegram retry and resend the update about 3 or 5 times right? So the end user sees 5 times of 'Waiting...'
So my suggestion is to add option to webhook something like retry and when it was set to false, telegram should've send update once and ignore any error from the server. Because i can not handle that error at the time there are no reason to resend updates.

Consider timeout from telegram side

In part of my code i have an unexpectedly recursive function and it took forever, So my suggestion is to add some option like timeout in webhook and when its have value for example 15s, Telegram should've wait for 15 seconds otherwise terminate the request.

These settings are optional and there is no bc for another devs. Thanks in advanced!

This would make bots unreliable. Such behavior must not be encouraged. There are a lot of reasons for webhook update to fail.

The webhook response is awaited for at most 60 seconds now. After the time passes, the connection is closed and the request is re-sent. This time can't be reliably increased and there are no reasons to decrease it.

As i said those are optional, When i want to telegram to ignore failures it means i know what i'm doing,  Thanks for the response btw.

Resnding will give up after some time. Moreover, only updates from a fixed chat will be affected, so it is better to wait for bot's code fix than silently drop updates.


Fix dep

Fix for https://github.com/lablabs/terraform-aws-eks-cert-manager/issues/9

Changes from this PR were integrated to #11


Docker crashing on new Ubuntu 18.04 droplet on digital ocean when running swarm

Problem description
I created a brand new Droplet on digital ocean (spec 8GB RAM, 160GB Disk, 4 v-cpu) with both a public IP and private IP address (<IP_ADDRESS>). Updated ubuntu to the latest release (the OS info is as follows):
Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-55-generic x86_64)
I installed docker-ce - Docker version 19.03.1, build 74b1e89
I am finding once I do a swarm init the container.d and then dockerd both exit after about 10 mins of operation.
There are a lot of errors in the logs (here is a sample):
Jul 30 05:48:36 ubuntu-s-4vcpu-8gb-sfo2-01 dockerd[21359]: time="2019-07-30T05:48:36.258880439Z" level=error msg="failed to get event" error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection closed" module=libcontainerd namespace=plugins.moby
Jul 30 05:48:36 ubuntu-s-4vcpu-8gb-sfo2-01 dockerd[21359]: time="2019-07-30T05:48:36.258927297Z" level=error msg="failed to get event" error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection closed" module=libcontainerd namespace=plugins.moby
Problem location

Other:

Project version(s) affected
Docker version 19.03.1, build 74b1e89
Suggestions for a fix
None at the moment, it's broken Cap'n.

Thank you for your feedback. However, it looks like your issue is not about Docker documentation, but that you may be having trouble with Docker itself. Please file a Docker support ticket or check out https://forums.docker.com/ to see if you can find a solution.
If this really is a documentation issue and I have misunderstood, please reopen it with more information.


remove code duplicate in AbstractConfig.java

[x] I have searched the issues of this repository and believe that this is not a duplicate.
[x] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: master
Operating System version: mac os 10.14.3
Java version: 1.8.0_201

Steps to reproduce this issue

remove code ClassUtils.isPrimitive(method1.getReturnType()) in AbstractConfig.java at line 653
ClassUtils.isPrimitive(method1.getReturnType()) is already judge in method MethodUtils.isGetter
no need to do this any more

What actually happens?
make code brief and clean

Can you post a pr?

I have made a pr #4492, need review

Can you post a pr?

I have made a pr #4492, need review

Close via #4492. Thanks for your contribution.


The examples of using signing API with curl don't work (at least in Windows) because of single quotes

Both links with examples with curl: in the blog post and in olympia docs, use single quotes around curl parameters.
And it seems that at least Windows version of curl 7.43.0 doesn't work with single quotes, but works just fine with double. So I propose to correct this.

If double quotes work everywhere, that would work for me.

Can you please add some STRs to this bug or add the "needs no qa" label?


Documentation overhaul

Complete re-write of documentation for all components, libraries etc.

To Do

[ ] Box

[ ] Box  Struct Methods
[ ] Comparison Ops
[ ] Arithmetic Ops

[ ] Iterators

[ ] Normal
[ ] Reverse
[ ] Two_Dim
[ ] Row
[ ] Column

[ ] Concepts


automatic line break at inline math operators

Description
When a paragraph contains a long inline equation such as $a + b + c + d + e + f + g + h$, then current (0.9.0) typst behaviour is to introduce a line break before the equation if it does not fit the line in its entirety, regardless of the gap that this leaves behind.
This is a paragraph that contains |
the equation                      |
a + b + c + d + e + f + g + h and |
that does not break inline        |
equations.                        |

It would be nice if typst would facilitate automatic breaking inside the equation to achieve a more homogeneous paragraph layout.
This is a paragraph that contains |
the equation a + b + c + d + e +  |
f + g + h and that breaks inline  |
equations at operators.           |

It would seem that a change of this kind can be introduced in a backwards compatible fashion by adding an argument to the math.equation function to enable and possibly configure the breaking logic.
Use Case
Inline mathematics tends to produce uneven line lengths in ragged paragraphs, or very large word spacing in justified paragraphs, if they are handled as unbreakable units. In many common situations this is greatly improved by allowing equations to break at appropriate points, such as after an operator. Currently, the only known way to produce the desired effect is to segment every equation manually, e.g. $a +$$ b +$$ c +$$ d +$$ e +$$ f +$$ g +$$ h$. However, this workaround comes at a considerable loss of readability.

i remember there is an opening pr implementing this. But it is inactive for a while

Duplicate of https://github.com/typst/typst/issues/826


feature(network-selection): ui

Description / Change(s) / Related issue(s)
Network selection UI.
NOTE: There are some open questions with PRODUCT. They are small things, so they can be done in a separate PR.
Ticket
YOMO-1692

[!NOTE]
Please create the ticket if missing it.

converted to draft. ongoing discussion with product

Careful with anything inside /ListTxHistory as it was renamed, sorry

Careful with anything inside /ListTxHistory as it was renamed, sorry

now worries @jorbuedo

Careful with anything inside /ListTxHistory as it was renamed, sorry

now worries @jorbuedo

ping me after rebasing/syncing :D

Do we need a bottom padding, or is this something to address outside this feature?

Tranks @jorbuedo
happening on android


Upgrade to the new bean-validation version

Changes made based on the discussions here:  https://hibernate.atlassian.net/browse/HV-1857

Can one of the admins add this person to the trusted builders? (reply with: "add to whitelist" or "ok to test")

Closing in favor of https://github.com/hibernate/hibernate-validator/pull/1234 which aggregates all the changes.


Fail to compile helium-crypto-rs with sqlx-postgres feature

STR

git clone git@github.com:helium/helium-crypto-rs.git
cd cd helium-crypto-rs/
cargo build --features sqlx-postgres

Investigation
The reason for the error is the sqlx dependency with the flexible version (in Cargo.toml)
sqlx = { version = "0", optional = true, default-features = false }

In the latest sqlx version (0.8) the trait interface of encode::Encode was changed. So backward compatibility is broken.
Currently, helium-crypto-rs supports the  sqlx-postgres feature only for sqlx versions below 0.8.
I didn't find a pretty way to handle it in the helium-crypto-rs code base to support all sqlx versions. Maybe, a good solution could be to stop supporting and remove sqlx-postgres feature from helium-crypto-rs.
Workaround
Don't use sqlx-postgres feature
Error message
   Compiling helium-crypto v0.8.4 (/home/kurotych/Sources/helium-crypto-rs)
error[E0053]: method `encode_by_ref` has an incompatible type for trait
   --> src/public_key.rs:210:64
    |
210 |         fn encode_by_ref(&self, buf: &mut PgArgumentBuffer) -> IsNull {
    |                                                                ^^^^^^
    |                                                                |
    |                                                                expected `Result<IsNull, Box<dyn Error + Send + Sync>>`, found `IsNull`
    |                                                                help: change the output type to match the trait: `std::result::Result<IsNull, Box<(dyn StdError + Send + Sync + 'static)>>`
    |
    = note: expected signature `fn(&public_key::PublicKey, &mut PgArgumentBuffer) -> std::result::Result<IsNull, Box<(dyn StdError + Send + Sync + 'static)>>`
               found signature `fn(&public_key::PublicKey, &mut PgArgumentBuffer) -> IsNull`

error[E0053]: method `encode_by_ref` has an incompatible type for trait
   --> src/public_key_binary.rs:139:64
    |
139 |         fn encode_by_ref(&self, buf: &mut PgArgumentBuffer) -> IsNull {
    |                                                                ^^^^^^
    |                                                                |
    |                                                                expected `Result<IsNull, Box<dyn Error + Send + Sync>>`, found `IsNull`
    |                                                                help: change the output type to match the trait: `std::result::Result<IsNull, Box<(dyn StdError + Send + Sync + 'static)>>`
    |
    = note: expected signature `fn(&public_key_binary::PublicKeyBinary, &mut PgArgumentBuffer) -> std::result::Result<IsNull, Box<(dyn StdError + Send + Sync + 'static)>>`
               found signature `fn(&public_key_binary::PublicKeyBinary, &mut PgArgumentBuffer) -> IsNull`

error[E0308]: mismatched types
   --> src/public_key.rs:212:13
    |
210 |         fn encode_by_ref(&self, buf: &mut PgArgumentBuffer) -> IsNull {
    |                                                                ------ expected `IsNull` because of return type
211 |             let address = self.to_string();
212 |             Encode::<Postgres>::encode(&address, buf)
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `IsNull`, found `Result<IsNull, Box<dyn Error + Send + Sync>>`
    |
    = note: expected enum `IsNull`
               found enum `std::result::Result<IsNull, Box<(dyn StdError + Send + Sync + 'static)>>`
help: consider using `Result::expect` to unwrap the `std::result::Result<IsNull, Box<(dyn StdError + Send + Sync + 'static)>>` value, panicking if the value is a `Result::Err`
    |
212 |             Encode::<Postgres>::encode(&address, buf).expect("REASON")
    |                                                      +++++++++++++++++

error[E0308]: mismatched types
   --> src/public_key_binary.rs:141:13
    |
139 |         fn encode_by_ref(&self, buf: &mut PgArgumentBuffer) -> IsNull {
    |                                                                ------ expected `IsNull` because of return type
140 |             let address = self.to_string();
141 |             Encode::<Postgres>::encode(&address, buf)
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `IsNull`, found `Result<IsNull, Box<dyn Error + Send + Sync>>`
    |
    = note: expected enum `IsNull`
               found enum `std::result::Result<IsNull, Box<(dyn StdError + Send + Sync + 'static)>>`
help: consider using `Result::expect` to unwrap the `std::result::Result<IsNull, Box<(dyn StdError + Send + Sync + 'static)>>` value, panicking if the value is a `Result::Err`
    |
141 |             Encode::<Postgres>::encode(&address, buf).expect("REASON")
    |                                                      +++++++++++++++++

Some errors have detailed explanations: E0053, E0308.
For more information about an error, try `rustc --explain E0053`.
error: could not compile `helium-crypto` (lib) due to 4 previous errors
warning: build failed, waiting for other jobs to finish...

We can't remove it since these encoders are used by oracles in a number of places.. We could pin sqlx to a lower version here?
In addition watch out for upgrading sqlx too far.. tls issues will make your builds fail with solana deps

Resolved by pining sqlx version
[patch.crates-io]
sqlx = { git = "https://github.com/helium/sqlx.git", rev = "635dba5b2682033101a1271e9fb4bf2516c0b840" }


Add refresh-oidc-tokens command to firezone-ctl

Would be super useful while debugging the OIDC connections. Now it's disabling users if something goes wrong during the refreshing process (see: https://github.com/firezone/firezone/pull/605). And you have to wait one hour https://github.com/firezone/firezone/blob/master/apps/fz_http/lib/fz_http/oidc/refresh_manager.ex#L10 to check your new oidc settings.
Another approach is to make this value https://github.com/firezone/firezone/blob/master/apps/fz_http/lib/fz_http/oidc/refresh_manager.ex#L10 changeable in the config file.

This is a great suggestion, thanks @salemgolemugoo. I think adding a manual refresh button at the top of the OIDC Connections table makes sense, e.g.

Will be released in 0.4.0


HDR-Muli-Exposure-Image-Fusion

Hey All,
my goal is to save images in different exposure times. for example:
1 Image: 0.2ms
2 Image: 0.5ms
3 Image 0.8ms
4 Image 1ms
5 Image 1.5ms
by combining these images it will be possible to generate a HDR Image.
https://github.com/zhiqinzhu123/HDR-Multi-exposure-image-Fusion-Source-Code-
It would be a great feature for sure!

@Bra1nsen The ZWO and RPiHQ cameras don't support this so we'd need to implement it in software, and it would be a pretty large effort and add a lot of complexity that IMHO few people would use.  A lot of people use their cameras to look for meteors and related items, so often don't even take daytime pictures.  To be honest, even if we wanted to implement this it wouldn't be for a couple years - we have a pretty big backlog of fixes and other enhancements.
In the future, if you have a feature request or question, would you please create a new Discussion item for them (use the link above) instead of creating an Issue?  We're trying to keep the Issue list to just bugs.  Thanks.

I think you underestimate the tremendous added value of exposure fusion, especially for capturing astronomical objects ;)

@Bra1nsen You goal has very short exposure which I assume was for daytime images, which aren't generally astronomical objects.  Or am I missing something?  My concern isn't so much with the added value as much as the added cost and complexity.  Creating a nighttime HDR image would take minutes and likely result in a lot of missed meteors.
I can see where it would be nice to have HDR daytime images, especially when the Sun is in the picture.  I haven't tried this, but I wonder if some of the benefit could be achieved by underexposing daytime images and then stretching them.  Allsky can currently do this.

watch from 1:40 - 3:00 [HDR]
Yes, I totally agree with you, that's definitely a lot of work. but I think this is the way to go. i will keep you up to date, i will test the hdr multi exposure fusion algorithm in the next few days. Maybe there will be an elegant way to integrate the function into the allsky software. I would be happy to contribute a share, maybe to further develop the allsky software in the future.
Many greetings

@Bra1nsen Interesting,  I didn't know there's a chip with different pixel sized to do HDR on the chip.  Does ZWO sell a camera with that chip?

Hey Eric, how are you?
Iam still working with my skycam :)

I need your help, could you please link me the part of the allsky code, where the automatic image saving process is taking place? I would like to know, how to organigram the image saving part while using timestamps and auto creating of folders.
kind regards
Paul

and to your question, i can recommend the sony imx490 camera, that would beat anything for sure.

@Bra1nsen  the "capture_ZWO" and "capture_RPiHQ" programs (source in the allsky/src directory) save the initial image-YYYMMDDHHMMSS.jpg file in allsky/tmp, then call the scripts/saveImage.sh script, passing the name of the file as well as information about the file, like exposure, bin, and many others.  saveImage.sh then optionally crops, resizes, stretches, and uploads the image, then makes a copy of the file called allsky/tmp/image.jpg, then moves the original image to allsky/images/DATE.  There is never a chance to overwrite a file since each file is saved with a unique name.
The "capture_*" programs keep track of the time the image starts, then use that to create the name of the image.


Hardware settings auto-detection

I already elaborated on this in https://github.com/polybar/polybar/issues/2405#issuecomment-809272880 but it deserves its own issue(s)
If possible, any module that requires some kind of hardware information (e.g. network interface name) should auto-detect these and choose a reasonable default if the user doesn't specify anything.
First, I'll present the current state. We can update this table as this is implemented in more modules.

Module
Notes

:heavy_check_mark:
internal/alsa
Uses default soundcard and Master mixer

:white_large_square:
internal/backlight

:white_large_square:
internal/battery

:white_large_square:
internal/fs

:heavy_check_mark:
internal/mpd
No detection, but uses the standard port used by MPD

:heavy_check_mark:
internal/network
interface-type has to be defined

:heavy_check_mark:
internal/pulseaudio
Uses default sink

:heavy_check_mark:
internal/temperature
No detection, but uses thermal zone 0 by default

:heavy_check_mark:
internal/xbackligh
Uses bar monitor by default

Backlight
Here, we should just scan /sys/class/backlight/ for a directory that has the required files.
If multiple match, just chose the first one and print a notice.
Documentation: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/ABI/testing/sysfs-class-backlight
Battery
Scan /sys/class/power_supply/ and chose one that has the necessary files.
If multiple match, just chose the first one and print a notice.
A battery must at least have a file type that contains Battery to be considered.
There is also a present file that tells us if the battery is present.
Though from my own testing, the entire directory disappears if the battery is removed.
If this file is considered, we could also have format-absent that is used if that file is 0, the folder doesn't exist or no battery was found.
The type file identifies the type of device, we should only consider Battery.
Documentation:

https://www.kernel.org/doc/html/latest/power/power_supply_class.html
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/ABI/testing/sysfs-class-power

Filesystem
Scan /proc/self/mountinfo and use all entries whose mount source (column 10) starts with /dev/
Alternatively, we could always use / as the default.
Documentation: man 5 proc

I can work on this. Filesystem seems easiest, so I think I'll start with that. Should we try to detect mount points or just go with /as a default?

@Zaphoood I think we should just go with / as the default. There are probably so many variations of different mount points out there that it is going to be impossible to filter out useful ones.
Also, I am considering at some point making (or at least recommendig that) the filesystem module be only for a single mount point.


Enhancement: Empty Strings added as DBNULL instead of " "

Warren -
Just noticed this when working with RVTools data from Excel and importing it to a database. Have some empty columns that are adding as empty strings in the DB instead of NULL.
Here is the line I modified to add a DBNULL value instead of an empty string.
                if ($property.GetType().IsArray)
                {
                    $DR.Item($Name) = $Value | ConvertTo-XML -As String -NoTypeInformation -Depth 1
                }
                elseif($Value -eq $null)
                {
                    $DR.Item($Name) = [DBNull]::Value
                }
                else
                {
                    $DR.Item($Name) = $Value
                }

Change to:  elseif($Value -eq $null -or $Value -eq "")
                if ($property.GetType().IsArray)
                {
                    $DR.Item($Name) = $Value | ConvertTo-XML -As String -NoTypeInformation -Depth 1
                }
                elseif($Value -eq $null -or $Value -eq "")
                {
                    $DR.Item($Name) = [DBNull]::Value
                }
                else
                {
                    $DR.Item($Name) = $Value
                }

Thanks for the heads up Jake!
Is this in Out-DataTable?
I think that would make sense (or even a regex for whitespace). Can you think of any datasets where a space would be needed? Wonder if a switch 'WhitespaceIsNotNull' would make sense - convert whitespace to dbnull unless that is specified?
Thanks!
Warren

Correct. I'm using it in conjuction with invoke-sqlbulkcopy.
I'm sure the .NET class of IsNullOrEmpty would be appropriate in this case.
I just needed a quick fix.
I can't think of a reason for white space in a db. It would really cause
issues because it would take up storage space - although minimal might add
up.
And in powershell it would be tough to tell the difference between DBNULL
and "" - unless you check the type.
Really appreciate all your work man. Your stuff has helped me more than you
know.
On Jan 27, 2016 13:07, "Warren F."<EMAIL_ADDRESS>wrote:

Thanks for the heads up Jake!
Is this in Out-DataTable?
I think that would make sense (or even a regex for whitespace). Can you
think of any datasets where a space would be needed? Wonder if a switch
'WhitespaceIsNotNull' would make sense - convert whitespace to dbnull
unless that is specified?
Thanks!
Warren
—
Reply to this email directly or view it on GitHub
https://github.com/RamblingCookieMonster/PowerShell/issues/9#issuecomment-175776113
.


Use login tokens instead of storing the password hash in the browser's session

This PR addresses #16

I've also added a list of the user's login sessions to the "User Settings" page. Maybe I should add an option to "logout from all devices" and cleanup expired login tokens from time to time.


[docs] Use Date type instead of any for MUI pickers demo

[x] I have followed (at least) the PR section of the contributing guide.

This PR replaces the any type with Date type, this will definitely be the return type as per the conversation in #15103

looks like the unit tests are passing, the failure occurred when trying to generate code coverage

@sperry94 Thanks for the follow up.


[DashboardLayout] Add navigation actions

Make it possible to render any content as an action in navigation items, such as badges or popover menus.
Also includes a few small unrelated general improvements to the documentation such as better example theme colors and initial page in the demos.
Closes https://github.com/mui/mui-toolpad/issues/3608
Documentation: https://deploy-preview-3776--mui-toolpad-docs.netlify.app/toolpad/core/react-dashboard-layout/#navigation
Includes:

[x] Feature
[x] Documentation
[x] Test

Approving. We can improve the docs page in follow up.

Got it, made an issue for improvements in https://github.com/mui/mui-toolpad/issues/3836


p5js sound won't work on hicetnunc with iphone safari due to .play() error

/** [p5.sound]  Version: 0.3.12 - 2020-01-06 */
calling .play() throws an error - Cannot read property 'length' of undefined - RingBuffer.push()
on desktop computers a sketch would fine despite the error, but on iphone safari it won't.
I noticed this recently when my hicetnunc objkt won't work on iphone safari but worked everywhere else
https://www.hicetnunc.xyz/objkt/54154
And it affects other objkts as well like this one:
https://www.hicetnunc.xyz/objkt/35354

Did you find a solution to this ? im having the same issue

https://github.com/hicetnunc2000/hicetnunc/issues/469 i left the comment here for what is the source.. worker-src SCP is not supported in iOS

new Tone.js has a branch if no worker available.. this can be changed to if no policy allowed (it goes down into setTimeout) not same performance but at least it will work on H=N


refactor(storage):  batch read be aware of value_indices

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
As title, when output_indices is not the subset of value_indices, storage table need to deserialize result from both key and value. For example, output_indices = [0, 1, 2] and value_indices = [2].
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)
close https://github.com/risingwavelabs/risingwave/issues/7303 https://github.com/risingwavelabs/risingwave/issues/7313

Is it ready for review now?

Is it ready for review now?

Yes.

Let me merge the main branch to check whether work as expected, because we already support show internal tables now.

Good news is no panic now. Bad news is nothing can be selected from the degree table (IIRC, it uses value_indices ).
create table t1(id int, b int, primary key(id));
create table t2(id int, b int, primary key(id));
create materialized view v as select t1.id t1_id, t2.id t2_id from t1 left join t2 on t1.id = t2.id;
insert into t1 values(1,1);
insert into t2 values(1,1);

show internal tables;

                  Name
-----------------------------------------
 __internal_v_5_hashjoinleft_1004
 __internal_v_5_hashjoindegreeleft_1005
 __internal_v_5_hashjoinright_1006
 __internal_v_5_hashjoindegreeright_1007
(4 rows)

dev=> select * from __internal_v_5_hashjoinright_1006;
 t2.id
-------
     1
(1 row)

dev=> select * from __internal_v_5_hashjoinleft_1004;
 t1.id
-------
     1
(1 row)

dev=> select * from __internal_v_5_hashjoindegreeleft_1005;
 t1.id | t1.id_0 | _degree
-------+---------+---------
(0 rows)

dev=> select * from __internal_v_5_hashjoindegreeright_1007;
 t2.id | t2.id_0 | _degree
-------+---------+---------
(0 rows)

Good news is no panic now. Bad news is nothing can be selected from the degree table (IIRC, it uses value_indices ).

https://github.com/risingwavelabs/risingwave/issues/7363

ernal_v_5_hashjoinright_1006;

This is not caused by value_indices, maybe degree table itself.

ernal_v_5_hashjoinright_1006;

This is not caused by value_indices, maybe degree table itself.

Agree, so I intend to merge this PR first.

Good news is no panic now. Bad news is nothing can be selected from the degree table (IIRC, it uses value_indices ).

@yuhao-su Could you please take a look at this case as well?

Good news is no panic now. Bad news is nothing can be selected from the degree table (IIRC, it uses value_indices ).

@yuhao-su Could you please take a look at this case as well?

It is expected we can't select any value from degree table in this case. This is an optimization that inner join does not need to write anything to the degree table.

Good news is no panic now. Bad news is nothing can be selected from the degree table (IIRC, it uses value_indices ).

@yuhao-su Could you please take a look at this case as well?

It is expected we can't select any value from degree table in this case. This is an optimization that inner join does not need to write anything to the degree table.

This is left join actually.

I think it is because the join key contains all the pk. 🤔 https://github.com/singularity-data/risingwave/blob/main/src/stream/src/executor/hash_join.rs#L513-L514

Oh, this is an optimization.


remove unnecessary IFD + add auto updates & testing

by moving all upstream repos to our flake inputs sources generated by nvfetcher, we no longer need to have IFD in most of our modules - making evaluation faster for all configurations. the only remaining instances of IFD are in lib.ctp.toYAML and the themes for kitty, which is due to it's use upstream in home-manager. these seem unavoidable for now, but the benefits in other modules are still great. this also gives us the ability to easily update our upstream sources and access them inside of modules.
workflows have been added to assist with this, mainly update-lock which updates both our flake inputs and nvfetcher sources. to ensure nothing breaks from these updates, i have also created a test vm that can also be run when the pr is created - however this will require an individual PAT in order to trigger the testing workflows properly
closes #15

Can't we use something like nvfetcher to automate updates? I've had a great time with it on my NUR, I think keeping the amount of inputs down is worthwhile. The inputs will only get worse when more are added regarding size and the amount of lines that show up in nix flake metadata.
I'd also like to add everything that's in the Nix flake from our git repositories, and not wait on nixpkgs to update. It would make sense to have our self-maintained derivations here, IMO.

Can't we use something like nvfetcher to automate updates?

honestly i thought flake inputs would be the simplest way to handle it, but after using it i barely noticed a difference lol. it's been added 👍🏻

I'd also like to add everything that's in the Nix flake from our git repositories, and not wait on nixpkgs to update. It would make sense to have our self-maintained derivations here, IMO.

i'll put this into a different pr, as this is already big enough and i have work in a bit :p

Glad that my suggestion of nvfetcher was of use 😄

i'll put this into a different pr, as this is already big enough and i have work in a bit :p

Absolutely, that was me just sharing my vision for what ctp/nix could be used for, not a comment on this PR 👍

honestly i thought flake inputs would be the simplest way to handle it

I would argue that flakes could have the advantage of allowing users to override inputs. On the other hand, this seems very niche, and perhaps we could support this another way in the future if anyone needs it.

this will need to be rebased, so draft for now 🐈


Make burn and burn-core packages no_std compatible (#168)

I made all necessary changes to make burn and burn-core no_std compatible. I added a top level crate burn-no-std-tests to integrate all no_std parts. Currently it only contains one test (inference on mnist model).
I pulled all common cargo versions into the top level Cargo.toml which helps managing no_std dependency compatibility. It was hard to make sure we had the same version and min features across no_std burn packages. I introduced burn-common package to hold common packages (for std and no_std modes).
The next on my to do is to modify CI workflow to add test flags (no-default-features) and new targets. Also I'll add my local script that I run before commit. There are lots of testing and build need to be done before check in. I figured we should help dev with a simple script to test. Otherwise they'll have to rely on CI to check their work.

I am fixing burn-dataset build issue. Sorry I missed this somehow.

OK. burn-dataset build error is fixed. Ready to review.

Fixed the issues (and more related). Ready for another review.


Docs for prometheus integration

Installation

a few links to upstream helm charts/operator/other methods to install

Scraping configuration

Provide configs to scrape all Istio pods
Provide TLS settings for users with strict mTLS

Best practices
Verification

https://preliminary.istio.io/docs/ops/integrations/prometheus


test(fee): test refactor of tx_weights to bouncerinfo

This change is

Codecov Report
Attention: 141 lines in your changes are missing coverage. Please review.

Comparison is base (40908fc) 68.82% compared to head (17be8e7) 67.63%.

Files
Patch %
Lines

...ates/native_blockifier/src/transaction_executor.rs
0.00%
88 Missing :warning:

...es/blockifier/src/transaction/transaction_utils.rs
0.00%
52 Missing :warning:

crates/blockifier/src/execution/bouncer.rs
0.00%
1 Missing :warning:

Additional details and impacted files
@@               Coverage Diff                @@
##           main-v0.13.1    #1468      +/-   ##
================================================
- Coverage         68.82%   67.63%   -1.20%
================================================
  Files                59       59
  Lines              7952     8092     +140
  Branches           7952     8092     +140
================================================
  Hits               5473     5473
- Misses             2023     2163     +140
  Partials            456      456

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


refactor attempt 2

OOP!
model bot communication as messages w/ attachments. everything can be encoded/decoded as Ibis tables (for storing/querying later), with some measure of reproducibility
TODOs:

[ ] finish up the call decision tree (new code)
[ ] implement tasks (steal from old code)
[ ] add encode/decode methods throughout (steal from old code)
[ ] add updating system data (steal from old code)
[ ] tuning, testing, etc.

closes #19 #17 #8 #20 #23 #14
subsumes #24

saving then merging -- above diagrams are still directionally accurate but made some name changes. bot isn't working just yet, but all structure is in place and I think follow-up PRs will be more clear and helpful for understanding how the bot works
will make an updated diagram and PR that


The online demo seems not good

Thank you for opening your work!
I tested three examples, but LISA didn't provide the correct responses. These examples weren't cherry-picked to find the weakness of LISA;  I just randomly picked them from the internet."

Yes, thanks for reporting this. Honestly speaking, there exist many failure cases. The potential reasons can be insufficient training data or unstable performance of the base model (e.g., LLaVA).
According to our observation, when the input text query is ambiguous or not that certain, the model is more likely to fail or output some artifacts. However, when the input text query is regulated or has the only answer, the model is more likely to make predictions correctly.


[fix bug 1120155] Do not validate form if user status already exists.

Coverage decreased (-0.01%) to 91.84% when pulling dd12053df923fbd2cc9b15895b9838cab3022207 on akatsoulas:1120155-mark-as-available into f5eb7c4b6e98b4f115bdb169edaa5e9265c7924f on mozilla:master.

Coverage increased (+0.0%) to 91.85% when pulling dd12053df923fbd2cc9b15895b9838cab3022207 on akatsoulas:1120155-mark-as-available into f5eb7c4b6e98b4f115bdb169edaa5e9265c7924f on mozilla:master.

r+


Propose a new design of withdrawal validator process

Review document and call with discussions of future features - 2 hours contributed


Shayan/FEQ-2467/setup deriv-analytics

changes:

added a new hook called useDerivAnalytics
updated stating and production deployment workflows to include growthbook and rudderstack tokens
improved trackjs initialisation call
installed js-cookie library

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

15 of 30 (50.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 85.341%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/hooks/custom-hooks/useDerivAnalytics.ts
10
25
40.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
5543

Relevant Lines:
6035

💛  - Coveralls


Convert remote files

Fixes #72

@freekmurze done, seems like installing imagick fails, known thing? I guess it's phpV-imagick

@introwit yeah, if you know a good solution for those failing tests, send a PR.


Apply prettier formatting rules

This change will apply the configured prettier formatting rules to the changes made to integrate TACo.
This results from executing pnpm exec prettier --write <file>.

Is the existing script for next lint of any use - https://github.com/nucypher/taco-orbisdb-demo/blob/taco/package.json#L10? Just curious really.
If we want to use prettier, would it make sense to add the command as a script in the package.json?


add support to arangodb 3 🎉

Coverage decreased (-0.03%) to 71.231% when pulling 7fcd4fb6ce4c7fbb718fbccffa2e6c671e38b768 on feature/arangodb-3 into d76810a7f32c9a8c7fa30648629798c4f3df242e on master.

Coverage decreased (-0.03%) to 71.231% when pulling 7fcd4fb6ce4c7fbb718fbccffa2e6c671e38b768 on feature/arangodb-3 into d76810a7f32c9a8c7fa30648629798c4f3df242e on master.


VS Code update fails with "Access is denied."

First off:   Thank you for writing this script.  Is WAY better than the many manual step alternative.
Small foible with the install.   After opening the command prompt which sets in place the environment, using Visual Studio Code, and closing same... Visual Studio tries to peek for and install updates.   This fails with

How can I go in and change permissions
to what series of directories
to allow the updates to propagate through to success?

This issue can be closed.

Thanks for documenting the issue and the fix! Closing.


ListView row reusing

Fixes #198
IListElement now implements INotifyPropertyChanged to allow the ViewElementCell to do an incremental update whenever the row changes, instead of destroying it and creating a new one.
See https://github.com/fsprojects/Fabulous/issues/198#issuecomment-425716261 for more information

This is fantastic, great work
Can I ask what validation you did?  e.g. in AllControls?
Also, we should consider how we would add unit tests for this sort of thing.  It doesn't have to be in this PR, just saying that I left a testing hole, focusing on samples more than unit tests

I validated it against the repro zip from #198 and checked that AllControls was still working.
It could use more tests, especially regression tests.
AllControls is quite hard to go into, and not a good place for testing as this is supposed to be a sample.
Maybe it would be better to start a new project in the tests folder focused on integration tests?

Yes we need a new test project, eg also for direct testing of ViewElement etc. Would have found #199 before merge to master

BTW AllControls isn't really a sample now, I'm happy to keep extending  it as a dumping ground for adhoc scenario tests that we can actually run that explore stuff that can't easily be pinned down by new unit tests.


Update sample project's framework dependencies to dotnet.

Resolves missing dependency issues with the sample project's project.json file.

Hi @CatPhat, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@CatPhat, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

@anurse ??

Applications, samples included, should not be using dotnet.

Ah sorry, had assumed that dotnet  was now being used due to the references in the other Microsoft.Framework.Caching.* projects.

No problem :). It's not fully documented yet so I can totally understand the confusion! We'll have more detailed docs out soon, but dotnet should generally be used in Class Libraries, and not in code that is directly executed (so, Web/Console Apps, Unit Tests, etc.)

@anurse How did we decide which projects to convert? I see that Caching, Logging, and EF were changed, but not HttpAbstractions, Hosting, or DNX. Or have we just not gotten around to it?

Things that are tied to the DNX application model should not be converted either. dotnet is for things that would previously have been "portable class libraries"


Confirmed working with Perl

... and Henrik Sjööh's Perl extension https://github.com/henriiik/vscode-perl

This is already mentioned in README on master branch 👍


Usability tweaks

It would be great to have the option to automatically keep the current colorscheme's background color -- is that possible?
Also an option to keep the status bar visible for those of us who want it.
A luxury feature would be if the sidebar width and positioning was automatically recalculated if the user resizes the gvim window.

I recommend this be converted into three separate issues, either a clear title.

My patch addresses issue 1 here. Closing.


500 error trying finishing connecting to Plaid Platypus Oauth

Using 3.0.0.
I'm supplying the same token & a receivedRedirectUri, but it looks like link goes from a SELECT INSTITUTION to a 500 on sandbox.plaid.com/link/item/mfa

Hey @dustinhorton, thanks for creating this issue! Do you mind elaborating on your flow a bit more?
It seems like what you're saying is that after the oauth flow is complete and you are redirected back to Link, Link fails on /link/item/mfa, right? If this is the case, do you mind pasting the link_token that you used for this Link session?

@otherchen Thanks—haven't quite been able to circle back to this yet, but intend to.
You are correct in what I was experiencing. To unblock myself, I reverted back to loading https://cdn.plaid.com/link/v2/stable/link-initialize.js and calling window.Plaid.open() from that, and it worked as expected.

Thanks! I'm closing for now since this seems resolved.

Thanks! I'm closing for now since this seems resolved.


Powered By Google not being imported - Require Cannot find module

Hello, I get this error since lastest release 5.4.0, please help !
Uncaught Error: Cannot find module 'react-places-autocomplete/images/powered_by_google_default.png' from 'react-places-autocomplete/dist/PlacesAutocomplete.js'
Line 372 of /node_modules/react-places-autocomplete/dist/PlacesAutocomplete.js  is generating the error.
          this.props.googleLogo && _react2.default.createElement(             'div',             {               id: 'PlacesAutocomplete__google-logo',               style: this.inlineStyleFor('googleLogoContainer'),               className: this.classNameFor('googleLogoContainer') },             _react2.default.createElement('img', {               src: require('./images/powered_by_google_' + this.props.googleLogoType + '.png'),               style: this.inlineStyleFor('googleLogoImage'),               className: this.classNameFor('googleLogoImage')             })           )
When using hard coded path of copy of the image from my assets/images folder works perfectly. E.g. src: "http://localhost:4000/images/powered_by_google_default.png"

@yannskee Thank you for reporting this! Will fix this ASAP

@yannskee Could you check again? I just rebuilt and published to NPM registry

@kenny-hibino just did a npm remove then npm install and I got this version "react-places-autocomplete": "0.0.0-semantically-released", i'm guessing this is normal.
I've tested and I am still getting the same error message. I will keep looking on my side, there is a very good chance the issue is coming from my env. I will keep you posted. Thanks again for the help :)

@kenny-hibino forgot to mention, I am using brunch on a phoenixframework. Could that be where my issue is coming from ?
brunch-config.js
`exports.config = {
// See http://brunch.io/#documentation for docs.
files: {
javascripts: {
joinTo: "js/app.js"
  // To use a separate vendor.js bundle, specify two files path
  // http://brunch.io/docs/config#-files-
  // joinTo: {
  //  "js/app.js": /^(js)/,
  //  "js/vendor.js": /^(vendor)|(deps)/
  // }
  //
  // To change the order of concatenation of files, explicitly mention here
  // order: {
  //   before: [
  //     "vendor/js/jquery-2.1.1.js",
  //     "vendor/js/bootstrap.min.js"
  //   ]
  // }
},
stylesheets: {
  joinTo: "css/app.css",
  order: {
    before: [
    "css/vendor/foundation.min.css",
    "css/vendor/react-datepicker-cssmodules.min.css",
    "css/vendor/react-datepicker.min.css",
    "css/vendor/rc-slider.css"
    ]
  }
},
templates: {
  joinTo: "js/app.js"
}

},
conventions: {
// This option sets where we should place non-css and non-js assets in.
// By default, we set this to "/assets/static". Files in this directory
// will be copied to paths.public, which is "priv/static" by default.
assets: /^(static)/
},
// Phoenix paths configuration
paths: {
// Dependencies and current project directories to watch
watched: ["static", "css", "js", "vendor"],
// Where to compile files to
public: "../priv/static"
},
// Configure your plugins
plugins: {
babel: {
presets: ["es2015", "react"],
// Do not use ES6 compiler in vendor code
ignore: [/web/static/vendor/]
}
},
modules: {
autoRequire: {
"js/app.js": ["js/app"]
}
},
npm: {
enabled: true,
whitelist: ["phoenix", "phoenix_html", "react", "react-dom"]
}
};
`

+1

@helloncanella Are you using webpack to bundle assets?

The answer is to add url-loader in your project package.json.
I just added the package and it work fine.
I think it's better to specify it in this project package.json if possible because in my case I do not use url-loader

This is a breaking issue for me, adding url-loader did not fix it, since I am not using webpack.
I am on version 5.3.1

Also getting this problem

Thank you for reporting. @Floriferous @timfisher are you guys using Webpack? if so, could you try adding file-loader to your webpack config?

Tried with file-loader was using url-loader, no luck, here is my full webpack.config.js file. I am using SPAServices with .net core
const path = require('path');
const webpack = require('webpack');
const ExtractTextPlugin = require('extract-text-webpack-plugin');
const CheckerPlugin = require('awesome-typescript-loader').CheckerPlugin;
const bundleOutputDir = './wwwroot/dist';
const CopyWebpackPlugin = require('copy-webpack-plugin');
module.exports = (env) => {
const isDevBuild = !(env && env.prod);
return [{
stats: { modules: false },
entry: { 'main': './ClientApp/boot.tsx' },
resolve: { extensions: ['.js', '.jsx', '.ts', '.tsx'] },
output: {
path: path.join(__dirname, bundleOutputDir),
filename: '[name].js',
publicPath: '/dist/'
},
module: {
rules: [
{ test: /.tsx?$/, include: /ClientApp/, use: 'awesome-typescript-loader?silent=true' },
{ test: /.css$/, use: isDevBuild ? ['style-loader', 'css-loader'] : ExtractTextPlugin.extract({ use: 'css-loader?minimize' }) },
{ test: /.(png|jpg|gif)$/, use: [{loader: 'file-loader', options: {}}]}
]
},
plugins: [
new CheckerPlugin(),
new webpack.DllReferencePlugin({
context: __dirname,
manifest: require('./wwwroot/dist/vendor-manifest.json')
}),
new CopyWebpackPlugin([
{ from: 'ClientApp/images/*' }
])
].concat(isDevBuild ? [
// Plugins that apply in development builds only
new webpack.SourceMapDevToolPlugin({
filename: '[file].map', // Remove this line if you prefer inline source maps
moduleFilenameTemplate: path.relative(bundleOutputDir, '[resourcePath]') // Point sourcemap entries to the original file locations on disk
})
] : [
// Plugins that apply in production builds only
new webpack.optimize.UglifyJsPlugin(),
new ExtractTextPlugin('site.css')
])
}];
};

I'm not using webpack. Tried adding file-loader anyways, which did not solve the issue.

I wrote a custom implementation of the autocomplete rendering, so the logo wasn't showing anyways. For me a quick workaround is to set the googleLogo prop to false, and add the image later myself when we go live, or if someone can find a fix.

+1

I can't replicate this, but if someone could post a link to their repo or something I could give it a try.
Or for a short-term fix you could just point the image src directly to the Google-hosted images:
https://maps.gstatic.com/mapfiles/api-3/images/powered-by-google-on-white3_hdpi.png
https://maps.gstatic.com/mapfiles/api-3/images/powered-by-google-on-non-white3_hdpi.png

+1

Would it make sense to remove Google Image from the library and add an optional footer prop so that user of the library can provide their custom footer element for the dropdown?
Feedback would be appreciated!

I think this sounds like a good solution. For users that wish to use a file-loader, you could still include the image in the library, but not directly referenced in code.

@kenny-hibino  Please do make it a optional footer prop. I've been playing with various libraries for autocomplete and no one seems to be doing that... i've had to hack/hide it with dodgy CSS ...
In the meantime, is there something I can do to prevent this from failing to load in the current version? It's breaking on every keystroke when a user types (each state update appears to try and load the image again)
Using Meteor 1.5 and React 15

Added url-loader to my project package.json worked for me as well. I'm using webpack.

Expanding on @Floriferous 's solution, this is a quick workaround that I implemented on a project until something more permanent is implemented into the package.
const myStyles = {
    autocompleteContainer: {
        paddingBottom: '20px',
        backgroundSize: 'auto 12px',
        backgroundPosition: 'bottom left 10px',
        backgroundRepeat: 'no-repeat',
        backgroundImage: "url('https://maps.gstatic.com/mapfiles/api-3/images/powered-by-google-on-white3_hdpi.png')",
    },
};

<PlacesAutocomplete
    styles={myStyles}
    googleLogo={false}
/>

You lose some semantics this way, rather than having an inline image, but seems like a decent work around in the short time that could come in handy for some.

@jacobimpson thank you for the solution, it's a patch but works!

Please use v6.x or above. Google logo image is no longer part of the library.

Hi, I tried to use @jacobimpson solution but still not getting the background image. Is there any other working solution please?


Fix flaky test on slow remote systems by adding afterIterations to Watch.Growth

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @reuvenlax

Run Java_Examples_Dataflow PreCommit

Run Java PreCommit


PLCC on the LIVE dataset

When I retrain the network on the LIVE dataset, the best PLCC is just 80%, which is far less than the reported performance 97%. This is why?

just because I forget to load the pretrained weights. I am so sorry to bother you.


Questions about the location of the diode

It surprised me so much that I managed to make a working one just from the imgur pics, without a real build guide. Thank you so much!
Just want to confirm one thing: for the boards to work, the diodes MUST be soldered to the back of the left board and the front of the right board, right?
I think a tilted case will make room for even bigger batteries, so I am trying to learn CAD to make a stl for the 6-col case.

If you're referring to the corne spaced XIAO, then no. It doesn't matter. I was having the diodes done at the factory, so it's much cheaper to do them all on one side. All that matters is that they are facing the right direction as far as polarity is concerned. You can place them all on the front or all on the back, whichever suits you better. You want the cathode to face the circled hole ideally, but it's configurable in whatever firmware you use. Most important is that they all are soldered the same orientation.
Hope that makes sense!

Also, thanks for pointing out how helpful those pics were. I added a link.

Question has been answered. Closing this issue.


Capture group name assignment fails with  TypeError: Cannot read property 'slice' of null

Hi,
Not sure if you are still maintaining this project, but is seems like a great way to simplify the use of RegExp. Congrats.
I found a problem where I'm running several strings through a match and if nothing matches, result is null which results in an error in the following line:
    return Array.prototype.reduce.call(result.slice(1), (result, current, index) => {

However I understand this is a workaround implementation for named captures which is now a part of the ECMAScript spec, so not sure if placing a check is the right move or simply to support named matches natively.

I don't think it is a good time to use native named capture groups.
And if you can provide a simple test case for the error, I will add null check in this method to avoid it.

You are right of course! I was developing in node and didn't think about browser compliance. Sorry.
In regards to the null check, here is the repro:
   let query = new SRL("capture (literally 'TEST') as test")
   let match = query.getMatch('WORD NOT `HERE')

Thanks again!


Support long playlists

As a user I want the player to avoid loading data unnecessarily
Acceptance criteria

Playlists with a large number of items are well supported (e.g. 1000 items).
No performance issues are experienced.
Item loading is efficient and does not unnecessarily load content.

Tasks

[ ] Check current behavior with long playlists.
[ ] Optimize item creation, maybe only loading a few items after the current one in the queue player.
[ ] Possibly trigger asset retrieval pipelines lazily in PlayerItem, depending on the current position (only a few neighboring items, e.g.).
[ ] Possibly do additional work for artwork retrieval if the above does not suffice.
[ ] Check that behavior works fine over AirPlay.
[ ] Remove prefix used to truncate playlists generated from media lists.

Let us wait until we have a concrete need for an app to load a bunch of items. Closed for now.

We have a thread explosion issue when loading content. This occurs mostly with audio playlists because of threads we manage, AVPlayer manages and comScore. This seems to exhaust resources and leads to a frozen UI.
The issue is not visible on my iPhone 14 Pro but we should test older devices. The problem is clearly visible in the simulator.
We probably need to carefully use Combine and introduce a look-ahead strategy to load content. Of course, since we can have multiple playlists loaded in multiple players at the same time, it is likely a good idea to introduce a common way to manage item preloading for all player instances.
I'll reopen this issue.

A few learnings from early attempts:

The comScore thread explosion can be mitigated pretty easily by instantiating the ComScore streaming analytics object lazily. This has been already implemented separately, see #743.
There is likely no need for a common item loader, contrary to what was written above. We can namely postpone item asset delivery by inserting a waiting point in our PlayerItem publisher pipeline, which we can then trigger when needed. The number of threads stay small but we still have to figure out where triggering is made optimally so that everything works well (and how many items we should preload in advance, but 2 seems a pretty good number).

Here are a few facts and learnings (WIP).
Expected behaviors
The following behaviors are expected to work:

Playback of a single URL-based item. Restart must be possible at the end.
Playback of a single URN-based item. Restart must be possible at the end.
Playback of a single failing URL-based item. Restart must be possible.
Playback of a single failing URN-based item (e.g. temporary network issue). Restart must be possible.
Gapless playback of MP3s provided as URLs.
Gapless playback of M3U provided as URLs.
Gapless playback of MP3s delivered for URNs.
Gapless playback of M3U delivered for URNs.
Failure of an item in a playlist must exhaust buffered items but must not exhaust the whole playlist (which can be huge).

Loading content
AVQueuePlayer preloads items in a different way, depending on their type:

MP3s are preloaded immediately when in the player queue, which is one of the reasons this task exists.
M3Us are preloaded when the previous content is nearing its end.

For this mechanisms to work playable MP3 / M3U URLs must be supplied to the player.
Remark
We experimented metadata retrieval triggered by a resource loader delegate (thus based on the player itself triggering the resource loading). This approach is doomed to fail, as in this case MP3s cannot be preloaded early, leading to a gap in the playback experience.

All AirPlay issues we had were fixed in the process 🍾

About the number of preloaded items:

We tested constants larger than 2. AirPlay stability is not affected.
The bigger the number, the heavier preloading is when involving audio. For this reason, and until a need is identified, we decided to fix the number of preloaded items to 2. We will open it (with dedicated warnings about large values) at a later time is a need is identified.

Found an issue (#764) when checking analytics visually but this issue is not related to this task.


YOLOv4 support

Dear all,
I am wondering whether this repository can also be used for yolov4 as well. If this was the case, what files exactly should be changed? Could I just port my .cfg and weights obtained from the darknet repo, and then simply add the weights found?
Kind regards,
Eneko

I'm using ROS1 witrh Ubuntu 18, so I'll try the Tossy repo. Thanks a lot for the tip!


Failing to turn on

After about two days of HomeBridge running, the plugin fails to turn on any of my SwitchBot’s. The official app is able to turn them on.
Does the plugin only ‘discover’ devices at startup, or does it do it periodically to check that they are still available while running?

Once the operation fails, does it always fail thereafter?

It sometimes continues to fail and then needs restarting, but sometimes it recovers and starts working again.
Failures seem to start after a turn on command is sent, but there is no response. This is highlighted in bold.

An example of a failure requiring a restart:
[7/7/2020, 6:30:55 PM] [Entrance Door] Turning on...
[7/7/2020, 6:31:13 PM] [Entrance Door] Turning on...
[7/7/2020, 6:31:13 PM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was failed turning on
[7/7/2020, 6:31:41 PM] [Entrance Door] Turning on...
[7/7/2020, 6:31:41 PM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was failed turning on
[7/7/2020, 6:31:47 PM] [Bathroom Fan] Turning off...
[7/7/2020, 6:32:56 PM] [Entrance Door] Turning on...
[7/7/2020, 6:32:56 PM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was failed turning on
[7/7/2020, 6:34:17 PM] [Entrance Door] Turning on...
[7/7/2020, 6:34:17 PM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was failed turning on
[7/7/2020, 6:34:38 PM] [Entrance Door] Turning on...
[7/7/2020, 6:34:38 PM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was failed turning on
[7/7/2020, 6:34:44 PM] [Bathroom Fan] Turning off...
[7/7/2020, 6:34:44 PM] [Bathroom Fan] WoHand (E6:4C:11:57:38:6D) was failed turning off
[7/7/2020, 6:34:51 PM] [Config] Homebridge restart request received

What is the OS version of macOS?

10.15.5 Supplemental Update (19F101)

Released 0.1.4, which three retries when a turn fails.
Please check if this problem has been fixed in 0.1.4.
If the problem still occurs, please reopen this Issue and provide the logs collected with homebridge in DEBUG mode.

It was working fine until there was a failure. I didn't manage to get it in debug mode. I will post if I do.
[7/12/2020, 10:15:06 PM] [Bathroom Lights] Turning on...
[7/12/2020, 10:15:06 PM] [Bathroom Lights] WoHand (FF:3C:1E:80:2B:C7) was failed turning on
[7/12/2020, 10:15:06 PM] [Bathroom Lights] Error: Now connecting. Wait for a few seconds then try again.
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:103:16
at new Promise (:null:null)
at SwitchbotDeviceWoHand._connect (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:96:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:401:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._command (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:393:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:91:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._operateBot (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:89:12)
at SwitchbotDeviceWoHand.turnOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:40:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:76:54)
at runMicrotasks (:null:null)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:86:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:86:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:86:17)
at SwitchBotAccessory.setOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:170:13)

Thank you for providing the log.
The BLE connection process was failing in the OSS used in the plugin.
It seems to be difficult to fix the problem because it is a problem of OSS side.
Is it possible to set a schedule to reboot mac once a day?

I can schedule a reboot.
Should I revert to the pervious version of the plugin, or will the current one be okay?

You should be fine with the latest version.
Version 0.1.4 just adding retries on errors, so the errors that can be handled by retries should be improved.

Was this delay addressed in previous fixes?

I haven't had a delay of more than a minute in my environment, but I improved the retry process when bluetooth is temporarily disconnected at version 0.2.0, so that may be the effect.
https://github.com/zizi4n5/homebridge-switchbot-for-mac/releases/tag/v0.2.0

Added support for retry to device detection when a device is not found.

I haven't had a delay of more than a minute in my environment, but I improved the retry process when bluetooth is temporarily disconnected at version 0.2.0, so that may be the effect.
https://github.com/zizi4n5/homebridge-switchbot-for-mac/releases/tag/v0.2.0

Added support for retry to device detection when a device is not found.

Thanks. Good to know.

Thank you for providing the log.
The BLE connection process was failing in the OSS used in the plugin.
It seems to be difficult to fix the problem because it is a problem of OSS side.
Is it possible to set a schedule to reboot mac once a day?

I am still occasionally getting the failures despite restarting daily.
How does the retry feature work?
Does it use the same discovery method as when the plugin startups with HomeBridge, or a different one? I find that it always successfully discovers and does not fail after restarting HomeBridge. If it is not using the same method of discovery/connection, would it be possible to trigger that method after a failure?

In version 0.2.0, if a device is not found at turning, plugin retry to discover() again.
https://github.com/zizi4n5/homebridge-switchbot-for-mac/blob/b161db0fbe5cb2b14535254f902cea95a8eea4c4/src/accessory.ts#L88-L92
For the following, I have forked the OSS and changed it to use my own modified version.
https://github.com/zizi4n5/node-switchbot

Thank you for providing the log.
The BLE connection process was failing in the OSS used in the plugin.
It seems to be difficult to fix the problem because it is a problem of OSS side.

See below for the differences from the original.
https://github.com/futomi/node-switchbot/compare/master...zizi4n5:develop
Is the error log in debug mode the same as last time?
If not, please provide a log.

It was working fine until there was a failure. I didn't manage to get it in debug mode. I will post if I do.
[7/12/2020, 10:15:06 PM] [Bathroom Lights] Turning on...
[7/12/2020, 10:15:06 PM] [Bathroom Lights] WoHand (FF:3C:1E:80:2B:C7) was failed turning on
[7/12/2020, 10:15:06 PM] [Bathroom Lights] Error: Now connecting. Wait for a few seconds then try again.
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:103:16
at new Promise (:null:null)
at SwitchbotDeviceWoHand._connect (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:96:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:401:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._command (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:393:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:91:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._operateBot (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:89:12)
at SwitchbotDeviceWoHand.turnOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:40:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:76:54)
at runMicrotasks (:null:null)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:86:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:86:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:86:17)
at SwitchBotAccessory.setOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:170:13)

See below for the differences from the original.
futomi/node-switchbot@master...zizi4n5:develop

Thank you for the clarification.

Is the error log in debug mode the same as last time?
If not, please provide a log.

It was not running in debug at the time due to the restart happing just before. Is it possible to run HomeBridge in debug automatically all the time?
Here is the log, it retried 3 times as set in the config:
[7/26/2020, 11:29:05 AM] [Bathroom Fan] Turning on...
[7/26/2020, 11:29:05 AM] [Bathroom Fan] WoHand (E6:4C:11:57:38:6D) was failed turning on
[7/26/2020, 11:29:05 AM] [Bathroom Fan] Error: Now connecting. Wait for a few seconds then try again.
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:116:16
at new Promise (:null:null)
at SwitchbotDeviceWoHand._connect (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:103:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:416:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._command (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:408:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:91:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._operateBot (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:89:12)
at SwitchbotDeviceWoHand.turnOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:40:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:91:54)
at runMicrotasks (:null:null)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at SwitchBotAccessory.setOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:185:13)
[7/26/2020, 11:29:06 AM] [Bathroom Lights] Turning on...
[7/26/2020, 11:29:06 AM] [Bathroom Lights] WoHand (FF:3C:1E:80:2B:C7) was failed turning on
[7/26/2020, 11:29:06 AM] [Bathroom Lights] Error: Now connecting. Wait for a few seconds then try again.
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:116:16
at new Promise (:null:null)
at SwitchbotDeviceWoHand._connect (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:103:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:416:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._command (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:408:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:91:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._operateBot (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:89:12)
at SwitchbotDeviceWoHand.turnOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:40:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:91:54)
at runMicrotasks (:null:null)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at SwitchBotAccessory.setOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:185:13)

See below for the differences from the original.
futomi/node-switchbot@master...zizi4n5:develop

Thank you for the clarification.

Is the error log in debug mode the same as last time?
If not, please provide a log.

It was not running in debug at the time unfortunately. I forgot to turn it back on after a rebuild of HomeBridge.
Here is the log, it retried 3 times as set in the config:
[7/26/2020, 11:29:05 AM] [Bathroom Fan] Turning on...
[7/26/2020, 11:29:05 AM] [Bathroom Fan] WoHand (E6:4C:11:57:38:6D) was failed turning on
[7/26/2020, 11:29:05 AM] [Bathroom Fan] Error: Now connecting. Wait for a few seconds then try again.
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:116:16
at new Promise (:null:null)
at SwitchbotDeviceWoHand._connect (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:103:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:416:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._command (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:408:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:91:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._operateBot (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:89:12)
at SwitchbotDeviceWoHand.turnOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:40:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:91:54)
at runMicrotasks (:null:null)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at SwitchBotAccessory.setOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:185:13)
[7/26/2020, 11:29:06 AM] [Bathroom Lights] Turning on...
[7/26/2020, 11:29:06 AM] [Bathroom Lights] WoHand (FF:3C:1E:80:2B:C7) was failed turning on
[7/26/2020, 11:29:06 AM] [Bathroom Lights] Error: Now connecting. Wait for a few seconds then try again.
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:116:16
at new Promise (:null:null)
at SwitchbotDeviceWoHand._connect (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:103:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:416:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._command (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:408:12)
at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:91:12
at new Promise (:null:null)
at SwitchbotDeviceWoHand._operateBot (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:89:12)
at SwitchbotDeviceWoHand.turnOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:40:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:91:54)
at runMicrotasks (:null:null)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
at SwitchBotAccessory.setOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:185:13)

This has also started happening:

It has been improved to try-catch when an exception is thrown when discover() is executed, so I think that's why.
https://github.com/zizi4n5/homebridge-switchbot-for-mac/blob/b161db0fbe5cb2b14535254f902cea95a8eea4c4/src/accessory.ts#L70-L84
What happens if you turn on/off after this error?

This happened on a later attempt after turning on/off:
[37m[7/27/2020, 4:49:17 AM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was not found
[7/27/2020, 4:49:17 AM] [Bathroom Lights] WoHand (FF:3C:1E:80:2B:C7) was not found
[7/27/2020, 4:49:17 AM] [Bathroom Fan] WoHand (E6:4C:11:57:38:6D) was not found
[7/27/2020, 4:50:08 AM] [Entrance Door] Turning on...
[7/27/2020, 4:50:08 AM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was not found. so retry discover.
[7/27/2020, 4:51:06 AM] [Entrance Door] Turning on...
[7/27/2020, 4:51:14 AM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was not found
[7/27/2020, 4:51:14 AM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was not found. so retry discover.
[7/27/2020, 4:51:49 AM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was discovered
[7/27/2020, 4:51:49 AM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was failed turning on
[7/27/2020, 4:51:49 AM] [Entrance Door] Error: Now connecting. Wait for a few seconds then try again.
    at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:116:16
    at new Promise (:null:null)
    at SwitchbotDeviceWoHand._connect (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:103:12)
    at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:416:12
    at new Promise (:null:null)
    at SwitchbotDeviceWoHand._command (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device.js:408:12)
    at /usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:91:12
    at new Promise (:null:null)
    at SwitchbotDeviceWoHand._operateBot (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:89:12)
    at SwitchbotDeviceWoHand.turnOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot-device-wohand.js:40:17)
    at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:91:54)
    at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
    at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
    at WoHand.turn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:101:17)
    at SwitchBotAccessory.setOn (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/dist/accessory.js:185:13)

[7/27/2020, 4:51:50 AM] [Entrance Door] WoHand (F1:C2:FB:BE:95:70) was turned on
Is that the expected behaviour?

Let me check your situation.
Did updating to version 0.2.0 make things worse?
Or are you saying that the situation is almost identical to version 0.1.4, but the error messages have changed?

It has gotten worse in 0.2.0. There seem to be more failures requiring rediscovery, so it takes longer to carry out the command as it has to rediscover. When operated through Siri, it says that the device has not responded, then when it does eventually reconnect and turn on the device, in the home app it says that it is not on. Pressing it to turn on changes the state in the home app, and on the log it says the device is already on, which is correct.
On a side note, is it possible to extend the period of time Siri waits/the point it is told there is a failure before saying the devices has not responded? Perhaps until all the retires are complete?

The same error occurred in my environment and I'll investigate it over the weekend.

On a side note, is it possible to extend the period of time Siri waits/the point it is told there is a failure before saying the devices has not responded? Perhaps until all the retires are complete?

Sorry, I don't know how to extend the time that Siri is waiting.

The same error occurred in my environment and I'll investigate it over the weekend.

That would be great.

Sorry, I don't know how to extend the time that Siri is waiting.

That's okay.


How to make abseil-cpp externel project in meson?

How to make abseil-cpp externel project in meson?
And then I can link with my main project ...
Could you give me some suggestions ?

https://mesonbuild.com/Subprojects.html
Simply add the wrap file from https://wrapdb.mesonbuild.com/ into your project, then use subproject.get_variable() or dependency() fallbacks.

I'm new to meson, Could you provide full demo code to use externel_project with meson ?

There is demo code in the first link. Is there anything specific that you're not sure about?

After git clone https://github.com/abseil/abseil-cpp.git into third_pary, I copy abseil-cpp meson.build In third_party/abseil-cpp.
add following line in my main project's meson.build
absl_dep= subproject('third_party/abseil-cpp').get_variable()

got error as follows;

meson.build:52: WARNING: Subproject name has a path separator. This may cause unexpected behaviour.
meson.build:52:0: ERROR: Neither a subproject directory nor a third_party/abseil-cpp.wrap file was found.

All subprojects must be inside subprojects directory. The subprojects directory must be at the top level of your project. Subproject declaration must be in your top level meson.build.

Note the libsimple example instructs you to clone into subprojects/libsimple/ and use subproject('libsimple').get_variable('libsimple_dep'), so you do not specify the directory...

See also https://mesonbuild.com/Using-the-WrapDB.html for installing a wrap from the wrapdb.


New PR to test SignCLA at 2020-11-18 11:12:00.54680898 -0800 PST m=+5.437409296

Body of PR

indiv-pass-fork-staging: test succeeded


can not import named getter/setter functions

// example.js
import { alias } from './example.export.js';

// example.export.js
export default {
  name: 'a',
  get alias() { return this.name; },
  set alias(name) { this.name = name; },
};

alias not found in './example.export.js' (import/named)

It's a very very bad idea to export getters and setters like that - both because it will absolutely break when node ships ES modules, and because getters and setters should always be avoided. Just make it a normal function.

I agree - sadly it's not my code, I'm playing with some react-native + native-base stuff and they are doing that... I can re-write it, but I came across it and thought I'd bring it up.

The interop between CJS and ESM isn't quite solidified yet.
If you do import obj from './path'; const { alias } = obj i would expect it to work, but exporting getters and setters specifically gets tricky.

good enough - thanks for looking into it

sorry i realised how much of a old issue it is


PolicyViolationService support

Goodevening!
I'd like to ask if there is support for DoubleClick Publisher , in order to access PolicyViolationService (getUrlPolicyViolationsLink)
It returns the csv link of policy violations!

Good question. It looks like you want https://github.com/googleads/googleads-php-lib.
See https://developers.google.com/doubleclick-publishers/docs/start

I already checked the documentation and all services but i didnt find any solution about this..
I tried too with other tools like pupeteer to download csv manually but no luck too!
Its weird for google to miss this functionality

You might want to check out https://developers.google.com/doubleclick-publishers/community


Make polling frequency configurable

I have noticed that there can be a noticeable delay when stopping a timer before it shows in home-assistant. I assume the integration can only poll BB for updates? What frequency does it do that at and could it be made configurable.

https://github.com/jcgoette/baby_buddy_homeassistant/blob/main/README.md#L42


Fontawesome 4.3.0

I updated the fontawesome to the last version and activated the Bootstrap CDN on the $fa-font-path. Hope you like.

What is the boxed-page.html layout for? Doesn't appear to have anything to do with Font Awesome 4.3.0

I am sorry Michael, I have added this after creating the Fontawesome pull request. The boxed-page is a _layout which include divs main and wrap. I really missed that on the project I am building and I was going to create another pull request for boxed-page.


Test Lighthouse + web3signer in network prater

Test instructions
You must have at least 2 Prater validators.
Install the web3signer prater and the client Lighthouse. You must get the hash from the Github latest release "dot".
In the client use the checkpoint sync feature to be able to start validating in minutes.
The web3signer will listen only to one client, you must select the client Lighthouse at config.
For a deeper test, you may find it useful to check out the grafana dashboards from the client, web3signer, and docker host.
Test report
With an editable unique comment report any errors and feedback you may find necessary.
Testers

@pablomendezroyo
@3alpha
@tropicar :heavy_check_mark:
@mgarciate :heavy_check_mark:

Works from my side :heavy_check_mark:


FHIRDbDAOBasicImpl has unused variable.

FHIRDbDAOBasicImpl has unused variable.
public class FHIRDbDAOBasicImpl<T> implements FHIRDbDAO {
...
private final String adminSchemaName;
...

I think this class will go away as part of #93

Great

Addressed


Added list with working search bar

Also changed linking onto '/clublist'

The backend is already working 100%, now  @KacperWojdak has to graphically handle it for us.


Feat/use esbuild

closes https://github.com/tinacms/tinacms/issues/2457
This PR allows the user to

use other extensions (js, ts, jsx, tsx) (Needs testing)
import from outside the .tina folder (needs testing on external project but is working inside the mono)

Everything is working but it needs a bit more work in the way of testing, and still needs some update to the CLI. It will be a draft PR for now.

Should be able to use this PR with yarn add --dev @tinacms/cli@use-es-build

Seeing some issues when using with external sites. This is ready for review but needs more testing before it is merged

@tinacms/maintainers
Update:
I think this is ready to be merged one we get some eyes on it other than myself. to make this easy I added to the tina-cloud-starter so you can pull down that code and checkout the testing/use-esbuild branch.


failed to login Windows 10 localhost:53000 refused

Describe the problem
When I click login on the windows GUI client, it seems to redirect to localhost:53000 and that gives me: connection refused.
To Reproduce
Steps to reproduce the behavior:

Right-click GUI Connect
Wait for browser window to open
Wait for redirect to happen
See error

Expected behavior
Redirect should work and you should be presented with auth provider list (MS, google etc)
Problem most likely has to do with:
https://ardalis.com/attempt-made-to-access-socket/
and
https://support.microsoft.com/en-us/topic/february-13-2018-kb4074588-os-build-16299-248-b4e2ca66-dd7a-6fd5-a8f3-dc6683d4922b
because netsh interface ipv4 show excludedportrange protocol=tcp shows:
Portausschlussbereiche für das Protokoll tcp

Startport      Endport
----------    --------
      2869        2869
      5357        5357
     49280       49379
     49380       49479
     49480       49579
     49713       49812
     49813       49912
     50000       50059     *
     50060       50159
     50389       50488
     52679       52778
     52830       52929
     52930       53029
     53030       53129
     53439       53538
     53539       53638
     53639       53738
     53739       53838
     53839       53938
     54039       54138
     56577       56676
     56678       56777
     58089       58188
     58189       58288
     62778       62877

But I cannot change the port 53000 Netbird service binds to.
Are you using NetBird Cloud?
Yes, Netbird Cloud is used.
NetBird version
0.26.2 and 0.26.3 tested
Add any other context about the problem here.

OK managed to fix it with the advice given here:

Hi! @raptaml
Thank you for the feedback! Can we close the issue?

Hi,
yes you can close it.


Allow config variable to bypass content directory writable check

closes #7359

Allows a contentWritable variable in config
If contentWritable is set to false then the content directory writable check is bypassed

This should not be merged until all file writes use storage adapters.

Hi @colinmeinke I'm going to close this because as you've identified, it's a dangerous change. It also doesn't fit very well with bigger changes we're making. As I said previously, we're working on communicating the roadmap (it's a big job and slow) and if you want to come talk to us about the plans we'll happily explain what we can in the #dev channel on slack.


Idempotence of ComomnJS to CommonJS2 bundling operation?

Hi, new here and would like to start by applauding the great effort!
I'm developing a Node.js module for publication on npm as a shared library and turned yesterday to webpack to help me bundle the discrete JavaScript, written in CommonJS, into a single JavaScript file, also in CommonJS (2), that does not include my package's declared external dependencies.
I followed advice on another thread here and got this working acceptably well:
// onm v1 webpack.config.js
//
// References:
//
// https://github.com/petehunt/webpack-howto
// CRITICAL: https://github.com/webpack/webpack/issues/839
// http://christianalfoni.github.io/javascript/2014/12/13/did-you-know-webpack-and-react-is-awesome.html
var outputFilename = 'onm.js'
var fs = require('fs');
var node_modules = fs.readdirSync('node_modules').filter(function(x) { return x !== '.bin' });
module.exports = {
entry: {
main: './index.js'
},
target: "node",
externals: node_modules,
output: {
path: './build',
filename: outputFilename,
libraryTarget: "commonjs2"
}
};
I committed the bundled output to Git just now and note that the transform, although it works and passes all my tests, does not appear to be idempotent. The issue looks like instability in the assignment of the ordinals used in ___webpack_require__ references in the generated bundle source.
Not sure if this is by design, or if there's some additional info I can specify to stabilize the assignment of these ordinals in the case that the source file tree hash is constant? Thanks, C.

OccurrenceOrderPlugin

Thanks!


⚠ ClamAV has degraded performance

In 33b08a3, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 138 ms

Resolved: ClamAV performance has improved in b1b99af.


Adds to scripts

Added microfs and uflash to scripts. Note that microfs requires command line parameters to specify the action: ls, put, get, remove and also a file name for put, get and remove.

@MrYsLab Could you explain the idea behind this pull request please? Is it a step towards integrating these scripts into the plugin? Are these scripts intended to be invoked via external actions?

Yes, having these as being part of the plugin would be helpful. I have added them as external tools and find it convenient not to have to open a terminal window to invoke them. I am not sure the best way to integrate them, but external tools might be a good choice.
It might be useful move the flash operation from the right-click context menu on a file as an external tool as well. I often work with both PC Python files and micro:bit Python files in the same project. Having to turn the plugin off and on to either run a PC file or to flash a micro:bit file slows down my workflow. My preference would be to have the plugin enabled to do type hinting, but not affect the external tools.

@MrYsLab Integrating a minifier could be a good extra option. Please consider adding a new feature request about it.

@MrYsLab I believe both microfs and uflash are available on PyPI. The MicroPython plugin for PyCharm has a mechanism for asking the user to install the packages required for plugin operations: see this piece of code.
uflash is already listed there since the plugin uses it to upload Python files to the Micro:bit.
As for microfs and file system operations, the IntelliJ platform behind PyCharm has a concept of virtual file systems in its API. They allow creating file systems that are not very different from your disk file system, but have some custom logic for accessing files. I believe we can try to implement such a file system based on microfs. From the users' perspective, it could be a tool window for browsing the contents of your device. I'm not sure about opening files from the device for editing (get followed by put), but at least it will be useful as an overview and the means to delete files. @MrYsLab If you like this idea, feel free to file a feature request about it.
I'm closing this PR, since these tools can be provided as dependencies and they are available on PyPI. Anyway, thanks for your ideas. Please file feature separate feature requests about them.


unsat cores

Is there any way to extract out an unsat core or MUS from an unsatisfiable model? I'm working with the CP-SAT Java interface. I'm used to debugging models in the Minizinc world with findMUS, and was wondering if something similar is possible with the CP-SAT solver.

Currently no.
Le mar. 10 sept. 2019 à 04:44, Lalith Suresh<EMAIL_ADDRESS>a
écrit :

Is there any way to extract out an unsat core or MUS from an unsatisfiable
model? I'm working with the CP-SAT Java interface. I'm used to debugging
models in the Minizinc world with findMUS, and was wondering if something
similar is possible with the CP-SAT solver.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1565?email_source=notifications&email_token=ACUPL3MWTLKDNQHBC2QKI53QI4CX5A5CNFSM4IVCGRD2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HKKO7YA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3PL2MITNVSEGSI2YYDQI4CX5ANCNFSM4IVCGRDQ
.