Add custom property dialog for editing multiple pairs of properties

Description:

There are a few places where we use multiple pairs of proerties (see issue #600 for an exmaple). Currently, we require the user to enter some kind of separator character -- even when using wxEditableListBox as the property editor.
What need is a dialog that looks like wxEditableListBox but uses an underlying multi-column wxListView control where we can set column headers, the number of columns, etc. If we provide sufficient methods in the dialog for customizing the wxListView control and possibly the format of the property string, then it should be usable by any property that needs to support multiple parts of a property.

Moving this to RC 1 -- it's not important enough to hold up Beta 2.


Allow for cancelling multiple listings at once in CancelListingModal

@pedromcunha We're looking to be able to cancel multiple listings at once using your CancelListingModal. :)

Hey @pedromcunha is this something you could accept?

Hi, so I reviewed this with the team and we came to the conclusion that this PR doesn't address all the aspects of batch cancellation. They are not limited to but include the following:

you can't cancel from multiple protocols at once
onchain cancellation and offchain cancellation (via an oracle) is a scenario that needs to be handled in the ui
we need to check on our end if you can cancel multiple offchain oracle orders, should be possible.
In addition to the list above we should probably render the steps for each cancelation signature to give the user some context. Given the above we feel like this PR isn't ready. Feel free to make the changes yourself and submit a new PR. We'll circle back to this when we have more time but for now it isn't high priority for us.


Tensorboard data from remote computer

Hello guys,
I've just completed TedLium3 training. But I did it on remote AWS machine.
How can I see tensorboard data?
Should I download this file events.out.tfevents.1668622331.bdcf5ab79459.10825.0 to my computer and to open it using the Crhome ?
Thanks,
AlexG.

The first method will print a message, telling you to view it within your browser.
The second method will give you a public URL.
(You need to use your google account for authentication for your first run.)

Since you did your exps on remote AWS machine, I think you have to use the second method, visit https://tensorboard.dev/ for more details.


Handle handle complex "svg headers"  starting with

FileFormat does not parse complex or mixed "svg" files.
To handle this, there is a need for code to parse through the xml header to find an instance of the <svg.... within a range.
Example case:
Parsing....as_bytes()
<?xml version="1.0" encoding="utf-8"?>
<!-- Generator: Adobe Illustrator 27.4.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
	 viewBox="0 0 375.5 134.2" style="enable-background:new 0 0 375.5 134.2;" xml:space="preserve">

Using FileFormat::from_bytes(&buffer);
let format = FileFormat::from_bytes(&buffer);
 if format == FileFormat::ScalableVectorGraphics {
    debug!( Is format a SVG file: {}",
        format.media_type()
    );
} esle ....

It should be that the the parser drills past the <?xml ... to see if <?svg exists within a text/xml format, since it is always possible this text/xml is in fact an svg format.
FileFormat can only parse the <?xml node in this example.

Normally this should work with the reader-xml feature (see https://docs.rs/file-format/0.22.0/file_format/#reader-features).
Please check you have enabled the feature in your Cargo.toml.

Malecot
Thanks for your timely response
I will enable
feature=reader-xml
And test later today
Again thanks and regards
Wesley @ Diba.io
On Mon, Nov 20, 2023 at 14:09 Mickaël Malécot @.***>
wrote:

Normally this should work with the reader-xml feature (see
https://docs.rs/file-format/0.22.0/file_format/#reader-features).
Please check you have enabled the feature in your Cargo.toml.
—
Reply to this email directly, view it on GitHub
https://github.com/mmalecot/file-format/issues/41#issuecomment-1819647316,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATWG7QVSKLMT2ONBZ3O53ETYFOTGPAVCNFSM6AAAAAA7TJ2F6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJZGY2DOMZRGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Closing Issue


Graph without explanation

The graph showing performance comparison should really have some kind of explanation with it. Specifically the colours aren't documented anywhere and makes the whole thing rather confusing..

Besides, notice "Elm 0.17" is shown twice for some reason.

Angular 2 as well, the pink bars are separate from the blue ones, but it's not described which is which..

Closing this since the graph isn't mentioned in the README anymore, and because the issue is over 4 years old.


Replace with_row_count by with_row_index for Polars

As with_row_count is deprecated, it's recommended to use with_row_index instead.

Thanks for submitting this! I wonder if we need a guard for backward compatibility earlier polars versions? WDYT of using something like f = getattr(data._tbl_data, "with_row_index", None), and then if the method isn't there, using with_row_count()?

Thanks for submitting this! I wonder if we need a guard for backward compatibility with earlier polars versions? WDYT of using something like f = getattr(data._tbl_data, "with_row_index", None), and then if the method isn't there, using with_row_count()?

It seems that the developers of Polars are diligently working towards releasing version v1.0 in the near future. Considering this, we may no longer need to maintain backward compatibility for earlier versions. As with_row_index is expected to be the stable API for Polars v1.0, we can proceed with this assumption.

Thanks for weighing in--it looks like with_row_index was added within the last month. We need to support polars from more than a month ago, just in case. If it's okay with you, I'm happy to make the change and then merge.
Thanks again for submitting the PR, it's really helpful to see this deprecation in polars, and get ahead of it

Thanks for weighing in--it looks like with_row_index was added within the last month. We need to support versions of polars from more than a month ago, just in case. If it's okay with you, I'm happy to make the change and then merge.
Thanks again for submitting the PR, it's really helpful to see this deprecation in polars, and get ahead of it

Sounds good to me. Please proceed.

Thanks for submitting this! I wonder if we need a guard for backward compatibility with earlier polars versions? WDYT of using something like f = getattr(data._tbl_data, "with_row_index", None), and then if the method isn't there, using with_row_count()?

Perhaps using f = getattr(data._tbl_data, "with_row_index", "with_row_count") would be neater.

@rich-iannone just a heads up, I did a tiny bit more CI tweaking to get the docs job to skip trying to push to netlify and deployment steps!

@rich-iannone just a heads up, I did a tiny bit more CI tweaking to get the docs job to skip trying to push to netlify and deployment steps, when running on a fork!

Thanks for doing that! Should help a lot for community PRs that focus on improving the docs.

Thanks for submitting this! I wonder if we need a guard for backward compatibility with earlier polars versions? WDYT of using something like f = getattr(data._tbl_data, "with_row_index", None), and then if the method isn't there, using with_row_count()?

Perhaps using f = getattr(data._tbl_data, "with_row_index", "with_row_count") would be neater.

The updated code looks good. However, I just realized that what I actually meant was something along the lines of f = getattr(data, "with_row_index", data.with_row_count) or f = getattr(data, "with_row_index", getattr(data, "with_row_count")).


Update license link

Small edit, this image will auto choose your license in GitHub to show

Thank you very much @Hongarc  👍


tsdb Panic when reading chunk

Bug Report
What did you do?
Ran prometheus
What did you expect to see?
It run
What did you see instead? Under which circumstances?
Exception on startup: panic: runtime error: index out of range (looks similar to: https://github.com/prometheus/tsdb/issues/251)
Environment

System information:

/prometheus $ uname -srm
Linux 4.15.3-1.el7.elrepo.x86_64 x86_64

Prometheus version:

/prometheus $ prometheus --version
prometheus, version 2.2.1 (branch: HEAD, revision: bc6058c81272a8d938c05e75607371284236aadc)
  build user:       root@149e5b3f0829
  build date:       20180314-14:15:45
  go version:       go1.10

Logs:

level=info ts=2018-05-01T12:35:26.455261083Z caller=main.go:220 msg="Starting Prometheus" version="(version=2.2.1, branch=HEAD, revision=bc6058c81272a8d938c05e75607371284236aadc)"
level=info ts=2018-05-01T12:35:26.45538143Z caller=main.go:221 build_context="(go=go1.10, user=root@149e5b3f0829, date=20180314-14:15:45)"
level=info ts=2018-05-01T12:35:26.455414873Z caller=main.go:222 host_details="(Linux 4.15.3-1.el7.elrepo.x86_64 #1 SMP Mon Feb 12 06:46:25 EST 2018 x86_64 prometheus-59bf4d7cf-sxsk5 (none))"
level=info ts=2018-05-01T12:35:26.455427991Z caller=main.go:223 fd_limits="(soft=65536, hard=65536)"
level=info ts=2018-05-01T12:35:26.459927519Z caller=web.go:382 component=web msg="Start listening for connections" address=<IP_ADDRESS>:9090
level=info ts=2018-05-01T12:35:26.45947935Z caller=main.go:504 msg="Starting TSDB ..."
level=error ts=2018-05-01T12:36:48.215666256Z caller=wal.go:275 component=tsdb msg="WAL corruption detected; truncating" err="unexpected CRC32 checksum 6cafd16a, want 0" file=/data/prometheus/wal/033372 pos=75965705
level=info ts=2018-05-01T12:36:48.950404399Z caller=main.go:514 msg="TSDB started"
level=info ts=2018-05-01T12:36:48.950585155Z caller=main.go:588 msg="Loading configuration file" filename=/etc/prometheus/config.yaml
level=info ts=2018-05-01T12:36:48.96267101Z caller=kubernetes.go:191 component="discovery manager scrape" discovery=k8s msg="Using pod service account via in-cluster config"
level=info ts=2018-05-01T12:36:48.965331005Z caller=kubernetes.go:191 component="discovery manager scrape" discovery=k8s msg="Using pod service account via in-cluster config"
level=info ts=2018-05-01T12:36:48.966139809Z caller=kubernetes.go:191 component="discovery manager scrape" discovery=k8s msg="Using pod service account via in-cluster config"
level=info ts=2018-05-01T12:36:48.966845893Z caller=kubernetes.go:191 component="discovery manager scrape" discovery=k8s msg="Using pod service account via in-cluster config"
level=info ts=2018-05-01T12:36:48.96989835Z caller=main.go:491 msg="Server is ready to receive web requests."
level=info ts=2018-05-01T12:37:48.996924066Z caller=compact.go:393 component=tsdb msg="compact blocks" count=4 mint=1524960000000 maxt=1524981600000
panic: runtime error: index out of range

goroutine 403 [running]:
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/chunks.(*Reader).Chunk(0xc75cb30c40, 0x13e, 0x1c56c80, 0xc5b252e0f0, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/chunks/chunks.go:365 +0x3f8
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*compactionSeriesSet).Next(0xc75bbc0dc0, 0xc763d9c770)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:691 +0x223
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.newCompactionMerger(0x1c47a80, 0xc75bbc0dc0, 0x1c47a80, 0xc75bbc0e60, 0xc7687230a0, 0x1c51880, 0xc7687230a0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:733 +0x8f
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*LeveledCompactor).populateBlock(0xc420d93220, 0xc75cb30e80, 0x4, 0x4, 0xc763d9c540, 0x1c56cc0, 0xc768766000, 0x1c3e680, 0xc7671fe640, 0x0, ...)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:537 +0x5bf
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*LeveledCompactor).write(0xc420d93220, 0x7ffc588f58e3, 0x10, 0xc763d9c540, 0xc75cb30e80, 0x4, 0x4, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:441 +0x5dd
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*LeveledCompactor).Compact(0xc420d93220, 0x7ffc588f58e3, 0x10, 0xc75cb30b40, 0x4, 0x4, 0x3023447db51b6301, 0x6431175cbef51e81, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:339 +0x693
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*DB).compact(0xc420c7a0c0, 0x0, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/db.go:419 +0x400
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*DB).run(0xc420c7a0c0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/db.go:279 +0x2cc
created by github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.Open
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/db.go:243 +0x5ba

Apologies if this is in the wrong repo. Any advice on recovering from this error without removing all tsdb files would be appreciated.

had  quick look and it seems some corruption in the chunk so it fails to read the encoding.
Is this easy to reproduce?

Is this easy to reproduce?

No it happened in a 1Tb tsdb (which I eventually deleted), and it really could be a result of any failure (disk or whatever). So I don't think it's a problem things get corrupt, I think the problem is that tsdb can't work around it (or I can't tell it to work around it), I'd much prefer to lose a bit of data then have to start fresh with everything.
I'm cool with closing this if this is too broad to be a bug.

In most cases I have seen only one block is causing an issue so if you delete the entire directory you loose that date range,but Prometheus should still read the remaining.
By looking at the logs and checking the meta.json file in each folder you should be able to tell which is the offending directory.
@gouthamve suggested that we should probably add this as a cleanup command to the tsdb tool so if I find time I will try to implement this.
closing for now, but feel free to reopen if you can provide more info how to reproduce.

@krasi-georgiev In the future, how can we collect more useful debugging data to help diagnose corruption issues? Unfortunately our tsdb contains private information and we are not able to share it, unless there's some way we can anonymize labels.

that is a good idea , I will think what and how we can expose something useful .
btw I already opened the PR for the scan and delete corrupted data and just waiting for some input from the other maintainers before I start.
https://github.com/prometheus/tsdb/pull/320

One thing that surprised me is how the checksums failed to catch this. I think something more than a simple corruption is going on here. And if it is indeed a corruption, I would like the querier to catch it, error rather than panic.
Re-opening to track, will be closed when fixed.

I'm seeing the same issue in both 2.2.1 and 2.3.0:
prometheus, version 2.2.1 (branch: HEAD, revision: bc6058c81272a8d938c05e75607371284236aadc)
  build user:       root@149e5b3f0829
  build date:       20180314-14:15:45
  go version:       go1.10

-- Logs begin at Thu 2018-06-07 13:44:14 UTC, end at Thu 2018-06-07 16:29:07 UTC. --
level=info ts=2018-06-07T15:00:00.485343904Z caller=compact.go:393 component=tsdb msg="compact blocks" count=1 mint=1528372800000 maxt=1528380000000
level=info ts=2018-06-07T15:00:01.027407263Z caller=head.go:348 component=tsdb msg="head GC completed" duration=16.657809ms
level=info ts=2018-06-07T15:00:01.082731112Z caller=head.go:357 component=tsdb msg="WAL truncation completed" duration=55.186079ms
level=info ts=2018-06-07T15:00:01.141441745Z caller=compact.go:393 component=tsdb msg="compact blocks" count=3 mint=1528351200000 maxt=1528372800000
level=info ts=2018-06-07T15:00:01.926333494Z caller=compact.go:393 component=tsdb msg="compact blocks" count=3 mint=1528308000000 maxt=1528372800000
level=info ts=2018-06-07T15:00:03.57978523Z caller=compact.go:393 component=tsdb msg="compact blocks" count=3 mint=1528178400000 maxt=1528372800000
panic: runtime error: index out of range
goroutine 277 [running]:
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/chunks.(*Reader).Chunk(0xc423c76080, 0x2113006, 0x1c56c80, 0xc422088600, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/chunks/chunks.go:365 +0x3f8
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*compactionSeriesSet).Next(0xc424398000, 0xc421e2fb70)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:691 +0x223
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*compactionMerger).Next(0xc4202d7a40, 0xc426c2a000)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:785 +0x46b
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*compactionMerger).Next(0xc4202d7ab0, 0x15b5)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:773 +0x7f7
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*LeveledCompactor).populateBlock(0xc42015f540, 0xc423c76200, 0x3, 0x4, 0xc4202d77a0, 0x1c56cc0, 0xc426290000, 0x1c3e680, 0xc421d06a00, 0x0, ...)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:554 +0xb62
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*LeveledCompactor).write(0xc42015f540, 0x7ffc87dd0f27, 0xb, 0xc4202d77a0, 0xc423c76200, 0x3, 0x4, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:441 +0x5dd
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*LeveledCompactor).Compact(0xc42015f540, 0x7ffc87dd0f27, 0xb, 0xc423c76040, 0x3, 0x4, 0xdc9a7b03c3da6301, 0x6fe58eff5c2bd7e6, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:339 +0x693
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*DB).compact(0xc4200ac180, 0x1, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/db.go:419 +0x400
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*DB).run(0xc4200ac180)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/db.go:279 +0x2cc
created by github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.Open
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/db.go:243 +0x5ba

After updating to 2.3.0 (and running with debug log):
prometheus, version 2.3.0 (branch: HEAD, revision: 290d71791a507a5057b9a099c9d48703d86dc941)
  build user:       root@d539e167976a
  build date:       20180607-08:46:54
  go version:       go1.10.2

level=info ts=2018-06-07T16:55:59.948403059Z caller=main.go:222 msg="Starting Prometheus" version="(version=2.3.0, branch=HEAD, revision=290d71791a507a5057b9a099c9d48703d86dc941)"
level=info ts=2018-06-07T16:55:59.948573817Z caller=main.go:223 build_context="(go=go1.10.2, user=root@d539e167976a, date=20180607-08:46:54)"
level=info ts=2018-06-07T16:55:59.948643933Z caller=main.go:224 host_details="(Linux 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 af3f50766d0d (none))"
level=info ts=2018-06-07T16:55:59.948716437Z caller=main.go:225 fd_limits="(soft=1048576, hard=1048576)"
level=info ts=2018-06-07T16:55:59.954446942Z caller=web.go:426 component=web msg="Start listening for connections" address=<IP_ADDRESS>:9090
level=info ts=2018-06-07T16:55:59.954461917Z caller=main.go:514 msg="Starting TSDB ..."
level=info ts=2018-06-07T16:55:59.956396679Z caller=web.go:478 component=web msg="router prefix" prefix=/prometheus
level=info ts=2018-06-07T16:55:59.956548849Z caller=repair.go:39 component=tsdb msg="found healthy block" mint=1510963200000 maxt=1511654400000 ulid=01BZV48VWFBHKZAMK620J772QQ
level=info ts=2018-06-07T16:55:59.95975985Z caller=repair.go:39 component=tsdb msg="found healthy block" mint=1511654400000 maxt=1516903200000 ulid=01C4QB6SE6B85VWNVNTSAHKWMN
level=info ts=2018-06-07T16:55:59.961946787Z caller=repair.go:39 component=tsdb msg="found healthy block" mint=1516903200000 maxt=1522152000000 ulid=01C9KZKY0XQMYPWH6R80JDZK7T
level=info ts=2018-06-07T16:55:59.964069945Z caller=repair.go:39 component=tsdb msg="found healthy block" mint=1522152000000 maxt=1527400800000 ulid=01CEGD8QHTF9K8F5825018E4VW
level=info ts=2018-06-07T16:55:59.964626111Z caller=repair.go:39 component=tsdb msg="found healthy block" mint=1527400800000 maxt=1527984000000 ulid=01CF1SCY67E74X3016N9JS3HZS
level=info ts=2018-06-07T16:55:59.964958328Z caller=repair.go:39 component=tsdb msg="found healthy block" mint=1527984000000 maxt=1528178400000 ulid=01CF7JSDMBXQCGYYBBP8TNMJTP
level=info ts=2018-06-07T16:55:59.96525028Z caller=repair.go:39 component=tsdb msg="found healthy block" mint=1528178400000 maxt=1528243200000 ulid=01CF9GJXCH259TBHSHA8VQ2C5X
level=info ts=2018-06-07T16:55:59.965534207Z caller=repair.go:39 component=tsdb msg="found healthy block" mint=1528243200000 maxt=1528308000000 ulid=01CFBECE07AQWSVF1F9GBP2ZMM
level=info ts=2018-06-07T16:55:59.966122625Z caller=repair.go:39 component=tsdb msg="found healthy block" mint=1528372800000 maxt=1528380000000 ulid=01CFDC5XV51TZRNF3YWG8HF5FH
level=info ts=2018-06-07T16:55:59.966423978Z caller=repair.go:39 component=tsdb msg="found healthy block" mint=1528308000000 maxt=1528372800000 ulid=01CFDC5Z869GY9JBK061DBM4B2
level=info ts=2018-06-07T16:56:04.288798178Z caller=main.go:524 msg="TSDB started"
level=info ts=2018-06-07T16:56:04.289014727Z caller=main.go:603 msg="Loading configuration file" filename=/etc/prometheus/prometheus.yml
level=info ts=2018-06-07T16:56:04.296028834Z caller=main.go:500 msg="Server is ready to receive web requests."
level=debug ts=2018-06-07T16:56:10.807616966Z caller=scrape.go:703 component="scrape manager" scrape_pool=network target=http://<IP_ADDRESS>:9130/metrics msg="Scrape failed" err="server returned HTTP status 500 Internal Server Error"
panic: runtime error: index out of range

goroutine 45 [running]:
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/chunks.(*Reader).Chunk(0xc4262acf00, 0x2113006, 0x1df2e80, 0xc424da4960, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/chunks/chunks.go:365 +0x3f8
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*compactionSeriesSet).Next(0xc421304be0, 0xc42051a870)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:710 +0x223
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*compactionMerger).Next(0xc42030e000, 0xc423efa000)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:799 +0x46b
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*compactionMerger).Next(0xc42030e070, 0x15b5)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:787 +0x7f7
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*LeveledCompactor).populateBlock(0xc420509c70, 0xc4262ad0c0, 0x3, 0x4, 0xc42033fea0, 0x1df2ec0, 0xc42563f7c0, 0x1dd9a40, 0xc42017b180, 0x0, ...)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:573 +0xb62
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*LeveledCompactor).write(0xc420509c70, 0x7ffe26298f0a, 0xb, 0xc42033fea0, 0xc4262ad0c0, 0x3, 0x4, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:459 +0x3a9
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*LeveledCompactor).Compact(0xc420509c70, 0x7ffe26298f0a, 0xb, 0xc4262acec0, 0x3, 0x4, 0xfd803b242edb6301, 0x540af2e51e8907e8, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/compact.go:345 +0x7e9
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*DB).compact(0xc4202ac3c0, 0x0, 0x0, 0x0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/db.go:415 +0x400
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*DB).run(0xc4202ac3c0)
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/db.go:275 +0x2cc
created by github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.Open
        /go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/db.go:239 +0x593

@bonan thanks for the report.
What are the steps to reproduce this?

@krasi-georgiev see https://github.com/prometheus/tsdb/pull/344. As I said in the PR, I'm not sure how the issue can be triggered except if the chunk is corrupted?

@simonpasquier is this fixed with prometheus/tsdb#344?

One thing that surprised me is how the checksums failed to catch this. I think something more than a simple corruption is going on here. And if it is indeed a corruption, I would like the querier to catch it, error rather than panic.

@gouthamve can you point out where do you think this should be cached?

I don't think there's an issue. This is indeed possibly some corruption. But if the corruption causes the file to be too short, we don't even get to a stage where we could validate a checksum. This was simply a bug where we didn't handle an error condition properly.

yes this was my understanding as well , just didn't know if goutham had anything else in mind.
I will update tsdb and will close this when merged.

lets consider this fixed and it will be added to the next release.
Please reopen if you find that this doesn't fix the bug.
Thanks for the report again!


FNIRSI GC-01 Cannot enter bootloader

Hey guys, I have a problem, I bought a FNIRSI GC-01 on latest firmware v1.6-2, with APM32F103RBT6 (Geehy) microcontroller. Picture of motherboard included.
I wanted to try the radpro firmware, but I am stuck on accessing the drive. If I follow the install instructions, I turn off the device,
plug a USB C cable (verified data transfer cable) into the device and pres the power button, the device just boots up and starts working.
No drive shows up in My computer, no device connected beep is heard. The machine is a Lenovo Legion 5i laptop running latest Windows 11. I am out of ideas, I tried holding down right button while plugging the USB, I tried disconnecting the internal battery and removien the backup battery, nothing works.... Please help me.... What am I doing wrong ? What could I try ?

I have the same issue, although I have Windows 10. It works only when I use a USB hub. I have heard that it needs USB 2.0 to work and my laptop has only USB 3 ports. However the USB hub is USB 3 too, but it works.

Hello. If you have a device from the manufacturer on version 1.6 or higher, it is possible that you will have to invoke the bootloader on the turned off device with the settings button (right arrow) + power button at the same time while inserting the USB cable into the PC. ... and yes, you must have a USB 2.0 input to the PC. I can't get to you on my laptop with USB 3.0 either.

I just had the craziest idea based on your reply... I have no access to USB2.0 port now, but I have a Samsung Galaxy S23ultra... So I grabbed a USB-C to USB-C cable, plugged one end into my Samsung device, the other into GC-01 and hit power button ...
Magic happened, the GC-01 booted to bootloader, the phone said something about unsupported STM drive and offered to format the connected drive. I refused that, unplugged the GC-01 from my phone an plugged it into a standard USB3.0 port on my laptop. And voila ! New drive appeared in My computer and I was able to copy the firmware file to the device. The GC-01 rebooted itself right after copying has finished and now it is running radpro !!!!

I have also encountered a problem when I connected it to my computer and than unplugged it without uploading any firmware. It looked like it erased the program memory and just did not work until I uploaded some firmware (FNIRSI or Rad Pro), so don't be surprised when it happens.

I have also encountered a problem when I connected it to my computer and than unplugged it without uploading any firmware. It looked like it erased the program memory and just did not work until I uploaded some firmware (FNIRSI or Rad Pro), so don't be surprised when it happens.

Then you need to press the reset button with a needle, which is on the right side at the bottom of the device.

With the original Firmware there is a super weird Time Window for the USB Storage mode
If you hold Power for to short... nothing happens
If you hold power for just right... the USB Storage appears
If you hold Power to long... it just boots the current Firmware
RadPro is not so Picky for some reason o_O

With the original Firmware there is a super weird Time Window for the USB Storage mode
If you hold Power for to short... nothing happens If you hold power for just right... the USB Storage appears If you hold Power to long... it just boots the current Firmware
RadPro is not so Picky for some reason o_O

With the device turned off, doesn't the bootloader start automatically when you connect USB?


[Event Request] table 130 "Incoming Document" - GetDataExchangePathOnBeforeCase

Please add new integration event and call as follows:
    procedure GetDataExchangePath(FieldNumber: Integer): Text
    var
        DataExchangeType: Record "Data Exchange Type";
        DataExchLineDef: Record "Data Exch. Line Def";
        PurchaseHeader: Record "Purchase Header";
        VendorBankAccount: Record "Vendor Bank Account";
        Vendor: Record Vendor;
        GLEntry: Record "G/L Entry";
        DataExchangePath: Text;
    begin
        if not DataExchangeType.Get("Data Exchange Type") then
            exit('');
        DataExchLineDef.SetRange("Data Exch. Def Code", DataExchangeType."Data Exch. Def. Code");
        DataExchLineDef.SetRange("Parent Code", '');
        if not DataExchLineDef.FindFirst() then
            exit('');
        // ---- New code start ----
        GetDataExchangePathOnBeforeCase(DataExchLineDef, FieldNumber, DataExchangePath);
        if DataExchangePath <> '' then
            exit(DataExchangePath);
        // ---- New code end ----
        case FieldNumber of
            FieldNo("Vendor Name"):
                exit(DataExchLineDef.GetPath(DATABASE::"Purchase Header", PurchaseHeader.FieldNo("Buy-from Vendor Name")));
            FieldNo("Vendor Id"):
                exit(DataExchLineDef.GetPath(DATABASE::Vendor, Vendor.FieldNo(SystemId)));
            FieldNo("Vendor No."):
                exit(DataExchLineDef.GetPath(DATABASE::Vendor, Vendor.FieldNo("No.")));
            FieldNo("Vendor VAT Registration No."):
                exit(DataExchLineDef.GetPath(DATABASE::Vendor, Vendor.FieldNo("VAT Registration No.")));
            FieldNo("Vendor IBAN"):
                exit(DataExchLineDef.GetPath(DATABASE::"Vendor Bank Account", VendorBankAccount.FieldNo(IBAN)));
            FieldNo("Vendor Bank Branch No."):
                exit(DataExchLineDef.GetPath(DATABASE::"Vendor Bank Account", VendorBankAccount.FieldNo("Bank Branch No.")));
            FieldNo("Vendor Bank Account No."):
                exit(DataExchLineDef.GetPath(DATABASE::"Vendor Bank Account", VendorBankAccount.FieldNo("Bank Account No.")));
            FieldNo("Vendor Phone No."):
                exit(DataExchLineDef.GetPath(DATABASE::Vendor, Vendor.FieldNo("Phone No.")));
            FieldNo("Vendor Invoice No."):
                exit(DataExchLineDef.GetPath(DATABASE::"Purchase Header", PurchaseHeader.FieldNo("Vendor Invoice No.")));
            FieldNo("Document Date"):
                exit(DataExchLineDef.GetPath(DATABASE::"Purchase Header", PurchaseHeader.FieldNo("Document Date")));
            FieldNo("Due Date"):
                exit(DataExchLineDef.GetPath(DATABASE::"Purchase Header", PurchaseHeader.FieldNo("Due Date")));
            FieldNo("Currency Code"):
                exit(DataExchLineDef.GetPath(DATABASE::"Purchase Header", PurchaseHeader.FieldNo("Currency Code")));
            FieldNo("Amount Excl. VAT"):
                exit(DataExchLineDef.GetPath(DATABASE::"Purchase Header", PurchaseHeader.FieldNo(Amount)));
            FieldNo("Amount Incl. VAT"):
                exit(DataExchLineDef.GetPath(DATABASE::"Purchase Header", PurchaseHeader.FieldNo("Amount Including VAT")));
            FieldNo("Order No."):
                exit(DataExchLineDef.GetPath(DATABASE::"Purchase Header", PurchaseHeader.FieldNo("Vendor Order No.")));
            FieldNo("VAT Amount"):
                exit(DataExchLineDef.GetPath(DATABASE::"G/L Entry", GLEntry.FieldNo("VAT Amount")));
            else begin
                    OnGetDataExchangePath(DataExchLineDef, FieldNumber, DataExchangePath);
                    if DataExchangePath <> '' then
                        exit(DataExchangePath);
                end;
        end;

        exit('');
    end;

    // ---- New code start ----
    [IntegrationEvent(false, false)]
    local procedure GetDataExchangePathOnBeforeCase(DataExchLineDef: Record "Data Exch. Line Def"; FieldNumber: Integer; var DataExchangePath: Text)
    begin
    end;
    // ---- New code end ----

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10748.


tests: ➁ mock consensus can InitChain with two validators

see:

#3588
#3902
#3816
#3934

in #3902 we introduced the ability to start a test node with a single set of validator keys. from conversation with @/erwanor, it would be helpful when writing staking tests to provide another interface, allowing us to start a test node with four validators.

we want to be able to test certain scenarios where one val get tombstoned, so two validators are sufficient (i think four came from talking about 3f+1)

update from @erwanor


Test dependencies do not match community or driver specs.

@pjbreaux
What issues does this address?
Fixes #946
What's this change do?
By altering the way in which smoke tests are run I fix the test dependency version-skew issue.
The following smoke tests results show smoke tests passing using the container based approach.  This is a significant step towards migrating the agent to use testrunner containers.   I implemented this solution now, because the tasks of recording, aggregating, and publishing coverage results are also best carried out by our containerized test infrastructure..
The solution I implemented guarantees that the agent and driver tests have the exact same dependencies because their respective testrunners are built on the same image (I call it a layer).
So, it's not just the same constraints file and installation command, it's actually the same image.
Where should the reviewer start?
Examine these test results:
http://<IP_ADDRESS>:49001/blue/organizations/jenkins/devs%2Fzancas_smoke/detail/zancas_smoke/25/pipeline

Attached is an image showing some of the packages that are skewed:

I expect to discuss ramifications and put the final touches on this PR (squashing commits, pointing the Jenkinsfile "agent" at a production image, etc.) after review.

Here're the latest (most current test results):
http://<IP_ADDRESS>:49001/view/all/job/devs/job/za_smoke_two/3/console

Bummer...   testenv fail...   possibly fighting with nightly at this point...


python3Packages.flax: init at 0.3.6

Motivation for this change
Part of "extra JAX libraries / frameworks" implementation, see the discussion in #152754
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 153761 run on x86_64-linux 1

2 packages built:

python38Packages.flax
python39Packages.flax

Just merged, thanks @ndl! I'll use this one myself!


avro-c++: Init at 1.7.5

Things done

[x] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Apart from a few minor issues, this looks superficially okay

@joachifm, I've addressed all questions.


Staging

What do?
On Oct 23, 2015 8:36 PM, "Theta-Z"<EMAIL_ADDRESS>wrote:

Merged #5.
—
Reply to this email directly or view it on GitHub.


(feat) -  Add merge facts option to add_custom_fact

This PR implements a new merge_facts option, which can be used with the add_custom_fact method in your configurations.
It allows users to determine whether they want to completely overwrite a fact already present in the facts hash, or simply merge values into the existing fact to expand/overwrite certain values whilst the entirety of the fact.
sample usage:
add_custom_fact :identity, { 'user' => "test_user" }, merge_facts: true
will update the value of user in the identity fact to "test_user", whilst keeping the rest of the identity fact values the same.
Failing tests rely on the merge of https://github.com/voxpupuli/rspec-puppet-facts/pull/157

@ekohl @bastelfreak 👋 sorry for the ping.. Does this need anything/any comments? Thanks


Can vstest.console.exe support -nologo parameters ?

we are using this exe to run our tests , however our build engine does not handle trackmarks well( a.k.a Domino), so we see problems about logging in domino build, most likely the log get truncked.
so is it possbile to support adding -nologo to supress this lines ?
Microsoft (R) Test Execution Command Line Tool Version 15.7.0
Copyright (c) Microsoft Corporation.  All rights reserved.

this is already fixed


Introduced default (main) template implementation for ignore_while_checking

This patch fixes #1485

This implements what we agreed on after some discussions on the list. Is there any reason not to go ahead with merging it?

I feel uneasy about this change. I do not think it actually solves #1485, but I am not familiar enough with the lock registering mechanism to review this PR. The address of a lock does not reliably guarantee mutex identity, and I do not think a general solution exist. However, that would mean that this PR leaves us in the same state that we were initially, which presumably leads to hard to debug runtime errors.

@K-ballo the main template proposed by this patch does not aim at using the address of a lock but the address of the mutex itself for identification (this corresponds to the practice we've employed so far, as we've always used the mutex itself for this). It essentially allows to use the address of the mutex to tell the lock checking what it should ignore.
If the user passes something which is not identifying a mutex, it may not be ignored while performing lock checking. So in the worst case the user sees false positives.

For the record: @K-ballo suggested to build CV and the other synchronization primitives using spinlock_no_backoff for the internal synchronization needs. This would allow to drop the ignore_lock_detection dance altogether.

On Thursday, May 07, 2015 06:34:32 Hartmut Kaiser wrote:

For the record: @K-ballo suggested to build CV and the other synchronization
primitives using spinlock_no_backoff for the internal synchronization
needs. This would allow to drop the ignore_lock_detection dance
altogether.

We discussed this on IRC last night. I am not particularly happy about that
either. The two main reasons:

It still doesn't solve the issue, at it will probably come back at us again
at some later point
spinlock_no_backoff is only a good idea when we know that the lock is not
very contended (for performance reasons)

A consensus we came up with was to have something like a
ignore_all_held_locks which would just ignore all currently held locks, this
would solve the issue of not being able to generically detect any Lockable in
ignore_while_checking

LGTM!


demo of branching style versioning

Is your feature request related to a problem?
Hi there! coming from threlte docs here. Thank you for your work on this starlight plugin as well as the others you've made, great stuff 👍
I'm wanting to make a starlight version of our docs using this plugin. For right now, we can make do with folder based versioning but would love to see a branch based demo sometime in the future
Describe the solution you'd like
a branch based versioning demo 🎉
Describe alternatives you've considered
Will do a folder based versioning for the moment
Additional Context
No response

Thanks for the interest and kind words :raised_hands:
As mentioned in the documentation, this plugin was designed to be opionated towards a folder-based versioning strategy and I don't think I have any plans to support other strategies in this plugin.
My more long term idea was:

Experiment and play more with this plugin as it addresses a specific need I have.
Provide a potential reference for others who may want to experiment with other versioning plugins using different strategies.
After working more on this plugin, consider if I want and have the time to provide additional plugins for other strategies.

Considering how different a folder-based strategy is from a branch (or tag) based one and how early this plugin is in its development, so far I don't think having a plugin supporting multiple strategies would be a good idea even maintenance-wise. Maybe work on this plugin will change my mind though.

Ah, sorry I miss read the docs 😅
Haha opinions can change but happy to cross that bridge when we get there 👍


Add CMIP6 license per source

Fix #1050
Will need to confirm whether the data found for CMCC-ESM2-SR5 will need to be deleted, as it is not currently available through ESGF #296 - and we have notes that this was an errored publication #900
Ref #1028

@matthew-mizielinski @MartinaSt @taylor13 please take a peek at this PR, the changes to CMIP6_source_id.json are marked and will need a review to make sure that I haven't confused something or made an error

In the license file doesn't  the first blurb need to be generalized to include other options.  Perhaps replace
 "license":{
        "license":"CMIP6 model data produced by <Your Centre Name> is licensed under a
Creative Commons Attribution-[NonCommercial-]ShareAlike 4.0 International License
(https://creativecommons.org/licenses). Consult ...

with
 "license":{
        "license":"CMIP6 model data produced by <Your Centre Name> is licensed under a
Creative Commons <insert a rights id; see below> License (<insert the license's URL; see below>).
Consult ...

I also found it confusing that the terms used in the license.json file were different from the terms in the source_id file.  In the license file, for consistency wouldn't it be better to replace "rights" with "rights_identifier" and replace "id" with "rights"?   There may be other ways to improve the consistency, including how we use the terms "license" vs. "rights".  Let me think about this further today.

For consistency and clarity, how about the following:
in the license.json file:

replace "rights" with "license_identifier" or "license_label"
replace "id" with "license"
replace "url" with "license_url"

And in the source_id.json file, replace

"rights" (where it appears as one entry under another "rights" keyword) with "license"
"rights_identifier" with "license_identifier"
"rights_info" with "license_url"

I like what you've done in the license.json file.  I'd favor making an additional tweak to the source_id file.  In order to avoid "rights" in line19 above, could we use the word "license" here and then change "license" in line 15 to "license_info"?
(might also consider replacing in license.json, "license_id" with "license_title" so no chance of confusing with "id" in source_id;  judgement call ... I don't really care too much.  If you make this change, then you'll have to also exchange the word in the first line of the file.)

@taylor13 those changes are now in place, and the new CMIP6_source_id.json:
https://github.com/WCRP-CMIP/CMIP6_CVs/blob/bbd4e7dc4ea16899606b3acdf004783a56a6b4c3/CMIP6_source_id.json#L14-L23

@matthew-mizielinski to provide a little more guidance, it would be great if you can review all the HadGEM* and UKESM* entries, if these all check out, then we're good with a merge (the GISS* contributions I have correct, I think)

@matthew-mizielinski those HadGEM3* changes are now in place, so we have for e.g.
HadGEM3-GC31-HH
https://github.com/WCRP-CMIP/CMIP6_CVs/blob/1876f6d631a844405c1215783f520a6f17964c7c/CMIP6_source_id.json#L4737-L4759
UKESM1-0-LL
https://github.com/WCRP-CMIP/CMIP6_CVs/blob/1876f6d631a844405c1215783f520a6f17964c7c/CMIP6_source_id.json#L8250-L8285

Have added pull request #1069 as a possible merge into this pull request (before merging to master) -- this has a prototype license table.


0.13 backports

Zebras: Improve equality for Periods. (#2857)
Add join_items to itertools. (#2859)
Zebras: Add eq_to to TimeFrame. (#2858)
Zebras: Add eq_shape to TimeFrame. (#2863)
Zebras: Allow to slice TimeFrame using plain strings for time info. (#2865)
Simplify plotting of forecasts. (#2864)
Zebras: Add TimeSeries.to_numpy. (#2866)
Update plotting in readme example. (#2867)
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup

Also #2860?


Add CLI to perform blending with mismatching vicinities and the option to rename the cube

Part of https://github.com/MetOffice/improver_suite/issues/1610
To achieve the meta-data changes requested here (https://github.com/MetOffice/improver_suite/pull/1611#discussion_r1165375538), I have created a new CLI to call weighted-blending, then modify the meta-data of the resulting cube before it is returned.
The metadata changes are:

File name: f"precipitation_accumulation_in_variable_vicinity-PT{period:02d}H"
Cube name: probability_of_lwe_thickness_of_precipitation_amount_in_variable_vicinity_above_threshold
Cube coordinate: radius_of_vicinity, Value: 10000 m, With the addition of this comment attribute in the nowcast period only: comment: "Maximum"

Implementing this required these changes to allow me to reuse existing code:

Refactors update_diagnostic_name and _update_cell_methods from cube_combiner.CubeMultiplier to metadata.amend.py
Refactors add_vicinity_coordinate from spatial.OccurrenceWithinVicinity plugin to spatial.py
New unit tests for these refactored methods.
Modification to allow the interpret-metadata CLI to accept the new metadata.

Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

Thanks @MoseleyS, I think this is mostly fine.
The only comments I've made are related to code style. I think I recall being told that there was a restriction of having up to 88 characters per line, though I can't seem to find a source for this now. If this is not the case then feel free to ignore my comments and I'll approve the PR.

Flake8 currently enforces a line-limit of 100 characters, so I tend to go with that. We've had different limits in the past. I know that there are other lines in our code base that are between 88 and 100 characters, so I don't think we need worry about this.

@Katie-Howard: The tests all pass for me this morning.


use std::forward in get_needed_size() will cause  wrong deserialized result

sample code :
https://github.com/cageq/yalantinglibs/blob/main/examples/packdemo.cpp
if I use std::forward in get_needed_size,  I can't get correctly deserialized result
use forward output : ( "hello" is misssing )
auto bodySize = struct_pack::get_needed_size(std::tuple<Args...>(std::forward(args)...));//buggy can't use forward
result :
result :3333
don't use std::forward output :
auto bodySize = struct_pack::get_needed_size(std::tuple<Args...>(args...));
result :hello
result :3333
I thinks get_needed_size should be readonly, shouldn't affect deserialize_to
compiler :
gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0
linux :
wsl ubuntu 22.04

The serialize code can also simply as
  return struct_pack::serialize<std::string>(args...);
}

the string has been moved by this construction. so it is empty when serialization.
std::tuple<Args...>(std::forward(args)...)

get_needed_size() is readonly. the problem is the moving construction.

thanks a lot.


Blank screen seen at /dashboard after login, with errors in console

Blank screen seen after login, with errors in console
Steps:

Went through all the installation steps here: https://github.com/rahulhaque/laravel-filepond-vue-inertia-example#installation
(In doing so, I updated the composer packages to get this repo working with laravel 10.x, see: https://github.com/rahulhaque/laravel-filepond-vue-inertia-example/issues/2)
Logged into the app at http://localhost:8000/login with<EMAIL_ADDRESS>/ password
I am taken to http://rahulhaque_laravel_filepond_vue_inertia_example.test/dashboard where I see a blank white screen, with the following error message in console:

GET http://localhost:3000/browser-sync/browser-sync-client.js net::ERR_CONNECTION_REFUSED
app.js:9055 [Vue warn]: Unhandled error during execution of setup function
  at <Dashboard jetstream= {canCreateTeams: false, canManageTwoFactorAuthentication: true, canUpdatePassword: true, canUpdateProfileInformation: true, hasEmailVerification: false, …} auth= {user: {…}} errorBags= []  ... >
  at <Inertia initialPage= {component: 'Dashboard', props: {…}, url: '/dashboard', version: '207fd484b7c2ceeff7800b8c8a11b3b6'} initialComponent= {__name: 'Dashboard', props: {…}, __file: 'resources/js/Pages/Dashboard.vue', setup: ƒ, render: ƒ, …} resolveComponent=fn<h>  ... >
  at <App>
warn @ app.js:9055
logError @ app.js:9230
handleError @ app.js:9222
callWithErrorHandling @ app.js:9174
setupStatefulComponent @ app.js:16223
setupComponent @ app.js:16184
mountComponent @ app.js:14588
processComponent @ app.js:14554
patch @ app.js:14042
componentUpdateFn @ app.js:14697
run @ app.js:7804
instance.update @ app.js:14803
setupRenderEffect @ app.js:14811
mountComponent @ app.js:14601
processComponent @ app.js:14554
patch @ app.js:14042
componentUpdateFn @ app.js:14697
run @ app.js:7804
instance.update @ app.js:14803
setupRenderEffect @ app.js:14811
mountComponent @ app.js:14601
processComponent @ app.js:14554
patch @ app.js:14042
render @ app.js:15321
mount @ app.js:12832
app.mount @ app.js:18314
setup @ app.js:27121
(anonymous) @ app.js:10
Promise.then (async)
exports.createInertiaApp @ app.js:10
./resources/js/app.js @ app.js:27101
__webpack_require__ @ app.js:69720
(anonymous) @ app.js:69890
__webpack_require__.O @ app.js:69757
(anonymous) @ app.js:69892
(anonymous) @ app.js:69894
app.js:22910 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'name')
    at setup (app.js:22910:24)
    at callWithErrorHandling (app.js:9172:18)
    at setupStatefulComponent (app.js:16223:25)
    at setupComponent (app.js:16184:36)
    at mountComponent (app.js:14588:7)
    at processComponent (app.js:14554:9)
    at patch (app.js:14042:11)
    at ReactiveEffect.componentUpdateFn [as fn] (app.js:14697:11)
    at ReactiveEffect.run (app.js:7804:19)
    at instance.update (app.js:14803:51)

@connecteev did it run fine without composer update?

@rahulhaque it wasn't installing without composer update
composer install
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Your lock file does not contain a compatible set of packages. Please run composer update.

  Problem 1
    - inertiajs/inertia-laravel is locked to version v0.5.4 and an update of this package was not requested.
    - inertiajs/inertia-laravel v0.5.4 requires php ^7.2|~8.0.0|~8.1.0 -> your php version (8.2.9) does not satisfy that requirement.
  Problem 2
    - nette/schema is locked to version v1.2.2 and an update of this package was not requested.
    - nette/schema v1.2.2 requires php >=7.1 <8.2 -> your php version (8.2.9) does not satisfy that requirement.
  Problem 3
    - nette/schema v1.2.2 requires php >=7.1 <8.2 -> your php version (8.2.9) does not satisfy that requirement.
    - league/config v1.1.1 requires nette/schema ^1.2 -> satisfiable by nette/schema[v1.2.2].
    - league/config is locked to version v1.1.1 and an update of this package was not requested.

After deleting composer.lock:

composer install
No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information.
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires inertiajs/inertia-laravel ^0.5.2 -> satisfiable by inertiajs/inertia-laravel[v0.5.2, v0.5.3, v0.5.4].
    - inertiajs/inertia-laravel[v0.5.2, ..., v0.5.4] require php ^7.2|~8.0.0|~8.1.0 -> your php version (8.2.9) does not satisfy that requirement.

@rahulhaque any idea how to fix this? I need an implementation of laravel with filepond and I'd love to use your repo if I can get it working.

@connecteev I've just downloaded the repo and followed the setup instructions in the readme. No errors found during installation and the project is running fine. I couldn't reproduce any of the errors you mentioned. What is your composer and npm version?

composer --version
Composer version 2.5.5 2023-03-21 11:50:05

npm --version
9.8.0

php --version
PHP 8.2.9 (cli) (built: Aug 22 2023 13:42:30) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.2.9, Copyright (c) Zend Technologies
    with Zend OPcache v8.2.9, Copyright (c), by Zend Technologies

Steps:

git clone git@github.com:rahulhaque/laravel-filepond-vue-inertia-example.git rahulhaque_laravel_filepond_vue_inertia_example_testing
cd rahulhaque_laravel_filepond_vue_inertia_example_testing
cp .env.example .env
update mysql db credentials
composer install

Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Your lock file does not contain a compatible set of packages. Please run composer update.

  Problem 1
    - inertiajs/inertia-laravel is locked to version v0.5.4 and an update of this package was not requested.
    - inertiajs/inertia-laravel v0.5.4 requires php ^7.2|~8.0.0|~8.1.0 -> your php version (8.2.9) does not satisfy that requirement.
  Problem 2
    - nette/schema is locked to version v1.2.2 and an update of this package was not requested.
    - nette/schema v1.2.2 requires php >=7.1 <8.2 -> your php version (8.2.9) does not satisfy that requirement.
  Problem 3
    - nette/schema v1.2.2 requires php >=7.1 <8.2 -> your php version (8.2.9) does not satisfy that requirement.
    - league/config v1.1.1 requires nette/schema ^1.2 -> satisfiable by nette/schema[v1.2.2].
    - league/config is locked to version v1.1.1 and an update of this package was not requested.

Remove composer.lock and Try again:
rm composer.lock
composer install
Output:
No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information.
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires inertiajs/inertia-laravel ^0.5.2 -> satisfiable by inertiajs/inertia-laravel[v0.5.2, v0.5.3, v0.5.4].
    - inertiajs/inertia-laravel[v0.5.2, ..., v0.5.4] require php ^7.2|~8.0.0|~8.1.0 -> your php version (8.2.9) does not satisfy that requirement.

@connecteev can you please redownload the repo and try again? Let me know of the result.

@rahulhaque composer install works beautifully. npm install also works well, although I am seeing the following warnings. Just FYI, otherwise feel free to close this issue. Thanks for the fix!
npm install
npm WARN deprecated<EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.

added 890 packages, and audited 891 packages in 5s

@connecteev you're welcome. The error is from npm as I am still using npm 8 and node 16 which is now deprecated but super stable in my opinion. I guess a proper update of the repo and framework will remove these warnings. Thank you.

@rahulhaque Thank you, and makes sense. Would be great if all the packages (composer and npm) could be updated to use the latest laravel 10, inertia 1.x, and Vite (instead of Mix). It would make integration that much easier.


Assets/images skipped on build or deploy

Problem
Images placed into /src/assets/images are not copied into /dist/assets on build or deploy.
Replication steps

Place an image (jpeg, jpg, svg, png, gif) into /src/assets/images
Run yarn build or yarn deploy
The expectation would be to find the images in /dist/assets but nothing is copied over

More Information
It looks like there is a missing paths item in slate-tools.config.js for images that is referenced in core.js. I tried locally fix it hoping it was a simple fix, but I think the issue is bigger than just a path reference.
https://github.com/Shopify/slate/blob/d67f445ea4dda555cce836f58d78f23ec3b55b84/packages/slate-tools/slate-tools.config.js#L73-L99
https://github.com/Shopify/slate/blob/d67f445ea4dda555cce836f58d78f23ec3b55b84/packages/slate-tools/tools/webpack/config/core.js#L47-L54

Any updates on this one? I migrated my 0.x template to 1.x but I can't add any new images now.

FWIW I also was having trouble with this until I realized that it only uploads images from /src/assets/images/ if:

It's actually used in your theme somewhere.
The local path is used, with single quotes around the file path, not double quotes.

So it didn't upload the images when I didn't have the image referenced in the theme yet anywhere, or if I used the old way with just the filename like this {{ "placeholder.png" | asset_url }}.  But if I add it in the theme as {{ '../assets/images/placeholder.png' | asset_url }} it works.
I'm not sure if this is a bug or a feature, but this is the functionality as I've mapped it out through trial and error.

#557 and #559 talks about this

Any news on this? Same issue, using {{ '../assets/images/placeholder.png' | asset_url }} with asset in /src/assets/images/placeholder.png didn't work for me like it did for petema3.
A url is generated by shopify, but no images found uploaded into shopify's theme/assets folder.

@DPerkunas have you tried yarn deploy

@xavianaxw Yeah I did. Maybe the issue is the fact that I'm deploying to a live site but here's the full scenario of what I noticed.
While having yarn watch running.
In src/templates/theme.liquid I added {{ '../assets/images/placeholder.png' | asset_url }} tried also ../images/placeholder.png, and what I noticed is it didn't migrate/copy the image in the /dist/assets/images folder. I tried yarn build and yarn deploy with no luck.
That being said, as expected, if I include the images via CSS like for a background, it will work when I use yarn deploy.
So is this a slate limitation or a bug? If using CSS + deploy, it will upload. If using liquid + deploy, it won't. We don't search liquid files for asset usage?

@DPerkunas interesting discovery.
The reason why {{ '../assets/images/placeholder.png' | asset_url }} does not work for you could be related to Shopify not detecting that the asset is being used in your code. I read it somewhere (but I can't find the link) but it states that if it's not being used then Shopfiy's Slate would not pick it up.
If you try
{{ '../assets/images/placeholder.png' | asset_url |img_tag }} or <img src="{{ '../assets/images/placeholder.png' | asset_url }}"/> and run yarn deploy again, it will get pulled into the assets folder in Edit Code screen.
I'll post again if I ever stumble upon that thing I read.

Sounds like the general consensus is that people would like images copied over, regardless if they are referenced in liquid or not?

@t-kelly That would solve my problems


Add in Option for incrementing block number

For those who will not need this feature, having the block number increment is just another chance for a bug a bit of overhead. Also, it relies on the user knowing what the block rate setting is doing.

[ ] Add in an option for the rate_parameter when creating an environment.

I'll take this, and add it to #417

I think we should externalize this more and make it more than just an Option. Perhaps an enum for this along the lines of:
pub enum BlockType {
     UserControlled,
     Randomized(f64),
     None,
}

UserControlled: will give the user the ability to make calls such as client.mine_block() and client.set_block_timestamp().
Randomized(f64, u32): would give the user the the Poisson chosen block sizes with the block rate via the f64 inner and we would let the block times update via the u32 inner.
None: The user would not update the blocks ever.


fix: missing characters while typing in code editor

Added debounce in code editor with 400ms delay

Resolves #299

Ideally I'd not suggest adding debounce to code editors. We first have to find out why there are misses and then fix them adding debounce doesn't seem like a good idea to me. :(

I'm not able to reproduce it issue on macOS with firefox. What environment are you using?

Chrome on windows

Ideally I'd not suggest adding debounce to code editors. We first have to find out why there are missed and then fix them adding debounce doesn't seem like a good idea to me. :(

I suppose it's okay. The old playground seems to have a similar implementation
https://github.com/eslint/archive-website/blob/286f9a778f82bd6279d94f3f54857b388d905df9/src/js/demo/components/Editor.jsx#L8
https://github.com/eslint/archive-website/blob/286f9a778f82bd6279d94f3f54857b388d905df9/src/js/demo/components/Editor.jsx#L95

Chrome on windows

I'm able to reproduce on windows 👍🏻

Ideally I'd not suggest adding debounce to code editors. We first have to find out why there are missed and then fix them adding debounce doesn't seem like a good idea to me. :(

I suppose it's okay. The old playground seems to have a similar implementation
https://github.com/eslint/archive-website/blob/286f9a778f82bd6279d94f3f54857b388d905df9/src/js/demo/components/Editor.jsx#L8
https://github.com/eslint/archive-website/blob/286f9a778f82bd6279d94f3f54857b388d905df9/src/js/demo/components/Editor.jsx#L95

Shall I change the delay to 500ms like the old editor?

400ms seems to be working fine 👍🏻

LGMT


re bulid error

Riot version (or commit ref):0.1
Go version: go1.12.3

Operating system and bit: linux/amd64

Description
When I use re to auto-generate code for the riot application,
the program generated an error.
re riot my-riotapp

error:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x5d27f1]

goroutine 1 [running]:
github.com/go-ego/re/vendor/github.com/go-vgo/gt/file.Walk.func1(0x0, 0x0, 0x0, 0x0, 0x976b60, 0xc000021680, 0x20, 0x888600)
...

I forgot to set GOPATH


[Snyk] Security upgrade passport from 0.3.2 to 0.6.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

526/1000  Why? Recently disclosed, Has a fix available, CVSS 4.8
Session Fixation SNYK-JS-PASSPORT-2840631
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: passport
    The new version differs by 160 commits.

c33067b 0.6.0
3052bb4 Update changelog.
42630cb Merge pull request #900 from jaredhanson/fix-fixation
8dd79fe Use utils-merge rather than Object.assign for compatibility.
4f6bd5b Change keepSessionData to keepSessionData.
46756e5 Silence verbose logging.
987b191 Add tests.
f8a175f Add tests.
29a90d6 No need to guard callback existence.
bfba8a1 Add tests.
17111d7 Add option to keep session data on logout.
a349c2b Add option to keep session data.
e69834e Add optional options to login and logout.
8825a9a Add tests.
c1991cf Add tests.
294f22c Better session detection and exceptions.
80cc4e3 Add tests.
3001654 Add tests.
b395106 Clean up tests.
cfa8259 Add tests.
ee0bf81 Add tests.
cc7606c Add tests.
71c54f6 Add test.
88c1f1b Handle logout without session manager.

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

resolved on https://github.com/Typeform/results-example/pull/16


agent/exec: revise error handling approach

Errors returned from controller methods are now all treated as fatal by
the the task controller. The defers most retries to the orchestration
layer, where they can be better handled. We also cement the concept of a
"Temporary" error, allowing an Executor/Controller to signal to the
caller that the error is actually temporary. We can mark these as
temporary as we find cases where it makes more sense.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>Closes #970, among others.
cc @tonistiigi @dongluochen @cpuguy83 @aluzzardi

[Current coverage][cc-pull] is 53.66%

Merging [#978][cc-pull] into [master][cc-base-branch] will decrease coverage by 3.71%

@@             master       #978   diff @@
==========================================
  Files            70         75      +5
  Lines          9165      11501   +2336
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           5259       6172    +913
- Misses         3221       4459   +1238
- Partials        685        870    +185

[][cc-pull]

Powered by Codecov. Last updated by [682e0b6...06d1e67][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/682e0b69be208176d6055cba855a5e9cf15c7cb4...06d1e674c1126a8ae1b984f35c8a8023c9a0f249
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/978?src=pr

Is there currently a task limit or some backoff delays on the orchestration level or will it just create new tasks until it runs out of space? It should be handled in another pr of course if it's not there, just curious.

Is there currently a task limit or some backoff delays on the orchestration level or will it just create new tasks until it runs out of space?

As far as I understand, yes. If not, we'll need to add it, as this defers errors up to the orchestration level.

Why are we bringing in engine-api?

@diogomonica It's always been there. I had to update it with godeps.

LGTM


docker network misconfiguration does not add services to networks

Closing.... not actually a problem if I'm using the code this was already resolved in...


Problems comparing result of useDirectusUser with result from async item fetch

Version
nuxt-directus ^5.6.1
nuxt: ^3.11.1
Reproduction Link
I cannot share my entire codebase at this time; Below is the segment of code causing the issue:
...
const user = useDirectusUser();

const { getItemById } = useDirectusItems();
...
const fetchProfile = async (id) => {
  const data = await getItemById({ collection: "Profiles", id, params });

  console.log("User:", user);
  // First try comparing these values
  console.log("COMPUTE1", user.id, data.Owner); // Prints `COMPUTE1 undefined 51011f11-09df-49fd-82db-4f155870556f` on server

  return data;
};

const {
  data,
  error,
  pending,
} = await useAsyncData(`profiles:${profile_id}`, () => fetchProfile(profile_id));

// See what is in `data` after that last async runs
console.log("COMPUTE2", user.id, data.Owner); // Prints `COMPUTE2 undefined undefined` on server and client

// Perhaps a computed property will work?
const is_owner = computed(() => {
  console.log("COMPUTE3", user.id, data.Owner); // Prints `COMPUTE3 undefined undefined` on server and client
  return user.id == data.Owner;
});

Steps to reproduce

Set up the basic authentication example
On an authenticated page, load some content and try to compare a field (in this case, Owner) in this content to the current user's ID using various methods (see the code sample above). Note that in my case, this getItemById function actually will fail with HTTP 403 if the user is not signed in, so in this function call, the user ID must be known somewhere in nuxt-directus.

What is Expected?
At the very least, the print statement labelled COMPUTE1 should print out both user ids, instead of undefined for user.id. It is definitely accessible in that code block, since the above statement relies on having the user currently signed in.
What is actually happening?
In all of the above examples, user.id evaluates to undefined. What is especially weird is that the print statement labeled "User:" prints the following:
ObjectRefImpl {
  _object:
   { '$s__nuxt_devtools__': { timeSsrStart:<PHONE_NUMBER>834 },
     '$sdirectus.user':
      { id: '5daecae4-1625-47ad-89f5-678c36531dcc',
        first_name: 'Test',
        last_name: 'User',
        email<EMAIL_ADDRESS>        password: '**********',
        location: null,
        title: null,
        description: null,
        tags: [Array],
        avatar: null,
        language: null,
        tfa_secret: null,
        status: 'active',
        role: 'a1f88c5d-0c58-44f0-9f24-ef2df053d786',
        token: null,
        last_access: '2024-03-29T23:53:12',
        last_page: '/content/Profiles',
        provider: 'default',
        external_identifier: null,
        auth_data: null,
        email_notifications: true,
        appearance: null,
        theme_dark: null,
        theme_light: null,
        theme_light_overrides: null,
        theme_dark_overrides: null,
        Profile: null } },
  _key: '$sdirectus.user',
  _defaultValue: undefined,
  __v_isRef: true }

So Nuxt knows about the user object, knows its ID, but doesn't want to share. The workaround that I am currently using is:
const userpatch = user?._object["$sdirectus.user"] || user;

...to obtain the user object. But this is not a long-term solution.

Note: Putting const user = useDirectusUser(); in the async function before calling getItemById also does not work.

Hi @KB1RD, have you tried accessing the user's attributes via user.value, according to here: useDirectusUser.md


Why use L2 Norm instead of KL divergence

In the consistency regularization

Here the L2 norm can be replaced by KL divergence. We adopt L2 norm because it achieves better performance in our experiments.


Write functionality to release

[x] Read in a notebook
[x] Remove hidden, solution and output (?) cells
[x] Write notebook

Closed by #8


Duplicating output

I tried to set the global option colorize, but got an interesting side-effect:
1
var winston = require('winston');

var logger = new (winston.Logger)({
	transports: [
		new (winston.transports.Console)({
			colorize: true
		}),

		new (winston.transports.Console)({
			name: 'fail'
		})
	]
});

logger.error('foo');

Output
error: foo
error: foo

2
var winston = require('winston');

var logger = new (winston.Logger)({
	transports: [
		new (winston.transports.Console)({
			colorize: true
		}),

		new (winston.transports.Console)({
			name: 'fail',
			formatter: function (options) {
				return 'bar';
			},
		})
	]
});

logger.error('foo');

error: foo
error: bar

It seems like a bug

This is by design. You've added two instances of the Console transport so it will log to the console twice.

Just create one transports with all your options:
var logger = new (winston.Logger)({
	transports: [
		new (winston.transports.Console)({
			name: 'user-error',
			colorize: true
		})
	]
});

logger.error('foo');


chore: Fix typo in nodeadm examples

Description

apiVersion: node.eks.aws/v1alpha -> apiVersion: node.eks.aws/v1alpha1

Closes #2985
Motivation and Context

The nodeadm examples have a typo (v1alpha is meant to be v1alpha1)
Breaking Changes
None
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[ ] I have executed pre-commit run -a on my pull request

The whitespace changes are due to the trim_trailing_whitespace = true in .editorconfig

The whitespace changes are due to the trim_trailing_whitespace = true in .editorconfig

what does that mean? the files should be generated from simply running terraform apply in the user data example. I just want to minimize the amount of white space changes

Interesting 🤔
I ran tofu apply in the examples/user_data directory to revert the whitespace changes.
Doing a git diff shows this:

Maybe the Terraform is generating Windows/DOS line ends (\r\n) instead of *nix (\n) as according to end_of_line = lf in the .editorconfig 🤔

I can't find whats causing the line ending issues but it seems to be upstream "somewhere".
we've had this raised recently as well https://github.com/terraform-aws-modules/terraform-aws-eks/pull/2974
so based on the upstream issue linked and one solution, hopefully that will resolve it. I also updated the file extension for the purely MIME multi-part user data to .txt since having those as .sh doesn't make sense

This PR is included in version 20.8.5 :tada:


About api 429 error,and User-Agent set ?

Someone who knows how to set User-Agent in maker-app?
I try helium-hotspot-app-3.10.0-${Platform.OS //   }-wallet-client
risinghf-hotspots-app-${getVersion()}-${Platform.OS   }-maker-client
risinghf-hotspots-app-${getVersion()}-${Platform.OS   }-maker-client ${getUserAgentSync()}
but none of them work. now api all return 429 error 。And can't get any data
api address
https://docs.helium.com/api/blockchain/introduction
Specify a User-Agent
To access the helium api via script you will need to specify a valid User-Agent HTTP header field identifying your agent, all requests made without a User-Agent header will result in an error 429 Slow down gun powder!.

oh


Added support for regr_avgx and regr_avgy

refer org.apache.calcite.sql.fun.SqlStdOperatorTable#REGR_COUNT for a similar existing function


CI: bump Rust to 1.80.0

This release enabled automatic checking of cfgs at compile-time[1], so Clippy started warning us about the use of #[cfg(feature = "nightly")]. Apparently I misunderstood how it works when I was copying code from the human-panic crate.
While trying to make the warning go away, I also realized that the Nightly-only code doesn't even compile, because we declare a function to return String but actually return ().
Apparently the proper way to fix this is to add compiler auto-detection to build.rs. This will slow down compilation a bit, for what I perceive to be a very small benefit; after all, we got this far without that Nightly-only API. Thus I removed the code that used the API.

https://blog.rust-lang.org/2024/05/06/check-cfg.html

coverage: 60.718% (+0.01%) from 60.708%
when pulling 69d991fad9fa0ed83c7ec8db8ce4a3e17723dd72 on feature/ci-bump-rust
into 2ffe84178ef867a944a6c54a0d9f509d623ea4b7 on master.


Save Simulator recordings as GIFs

https://twitter.com/teekachu1/status/1431314346311815175?s=21

tip added.
thanks @Mordil !


I would like to add data convertor in basic convertor section

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like

A clear and concise description of what you want to happen.

Please assign this issue to me as I'm participant of GSSOC'21.

Please assign this issue to me @Nidhirajput1301 as I'm participant of GSSOC'21.


It says "Update is available"

Describe the bug
My ungoogled-chromium (72.0.3626.122-2) has just started to show that an "update is available".
It looks like it even downloaded something, and it's saying "Nearly up to date! Relaunch Chromium to finish updating."
How would that be possible?
Expected behavior
My ungoogled-chromium has no way and no place to check for updates.
Screenshots

Environment (please complete the following information):

OS/Platform and version: Artix Linux (Archlinux based)
ungoogled-chromium version: 72.0.3626.122-2

Additional context
I'm using portable build, built it myself.

I'm not sure why your browser is doing this. Are you able to run Wireshark to see what traffic is going through?

Do you have a normal chromium installed also? Or Google Chrome?

Sorry I didn't have time yet to check. Will do.

Do you have a normal chromium installed also? Or Google Chrome?

Actually yes, I have it. I will check again after removing chromium from system.

At the very least I caught it trying to do ipv6 outgoing, but due to this being disabled in my kernel, it would just err on console (I don't have the actual error on hand, will edit when I do).
I've prepared (and applied for me) this patch which should disallow all ipv6 (still waiting for it to trigger, currently):
--- a/net/socket/socket_posix.cc	2019-08-24 01:52:35.404551016 +0200
+++ b/net/socket/socket_posix.cc	2019-08-24 01:53:27.596545271 +0200
@@ -86,10 +86,14 @@ int SocketPosix::Open(int address_family
          address_family == AF_INET6 ||
          address_family == AF_UNIX);

+  if ( AF_INET6 == address_family) {
+    socket_fd_ = -1; errno = EACCES;
+  } else {
   socket_fd_ = CreatePlatformSocket(
       address_family,
       SOCK_STREAM,
       address_family == AF_UNIX ? 0 : IPPROTO_TCP);
+  }
   if (socket_fd_ < 0) {
     PLOG(ERROR) << "CreatePlatformSocket() failed";
     return MapSystemError(errno);

No idea what it was trying to do via ipv6 though, sorry.

disregard that ^  it's not related to the issue as I initially thought. It's in fact this other issue happens when opening devtools and it's about port 9229. Also happens when fiddling through chrome://inspect/  (mainly Discover network targets but not just that)

I actually saw this happen on an installation recently in verison 76. This is likely some behavior we are not catching in our patches.

I actually saw this happen on an installation recently in verison 76. This is likely some behavior we are not catching in our patches.

Hmm.. I have removed the distro managed chromium package, (and kept my ungoogled-chromium up to date) and it stopped for a while now. But maybe because I am using a recent version (77).
I'm still watching the issue..

The latest supplied Ungoogled-Chromium (UC) Linux Portable binary version, which is three versions ahead of v72 (75.0.3770.100-1.2), also gives similar popups sometimes.
Lately, this occurred with UC in incognito mode and while reading text on a Youtube page and the video playing in either Theater Mode or perhaps Default View (NB:  Are Youtube and Chromium owned by Alphabet/Google?).  All tabs have been closed since then, but here is a screenshot taken during that session showing the tooltip that appeared over the notification icon:

When clicking on the icon:

When clicking on the 'out of date' message, a popup appears that may look the same as the original notice:

NB:  Another issue that should not be resolved here but perhaps may give insight into this one:  lately, this same HP notepad locks up sometimes and the CapsLock key flashes on and off (a kernel panic?) so that I need to reboot, and it has recently happened with UC in incognito mode being the 'only'/'major' app running on my desktop, also on a Youtube page, but I am not sure whether it happened when clicking either on 'Hide chat' or 'Show chat'.

I have the same issue with 76.

This issue happened to me yesterday on the latest Debian buster build, 76.0.3809.132-1.buster1. But as @furkanmustafa mentioned, we should see if this still occurs in 77 or 78.

I'm on 77 and no message has appeared so far.

If this is still an issue, please let us know.


Fix build when used as a submodule

I tested this with a local checkout of https://github.com/rust-lang/rust/
Ideally CI would update the submodule and run cargo +nightly check inside src/libstd.

Please don't merge yet, I just found another issue

Ping me when I should merge. I'm going to try to add a test for updating the submodule to stdsimd's CI.

Take 2

Build failures: ARM & Windows is not this PR's fault, I think. I fixed rustfmt.

That windows job is broken on master as well, so don't worry about it, I'll take a look later. rustfmt still appears to be broken though, you might need to use cargo fmt --all to cover all crates.

Ok one more time


Improve init --site error for existing wrangler.toml

💡 Feature request
For wrangler init --site if wrangler.toml exists already instead of erroring, make the worker-site directory and ask the user to append to their wrangler.toml bucket and entry-point
Basic example
Instead of:
this-wrangler init --site
Error: A wrangler.toml file already exists! Please remove it before running this command again.

output
this-wrangler init --site
⬇ Installing cargo-generate...
⚠ Append to the parent environment in your wrangler.toml:
[site]
bucket = "./static-folder"
entry-point = "workers-site"
🌀  🐑  Generating a new webpack worker project with name 'workers-site'...
🔧   Creating project called `workers-site`...
✨   Done! New project created /Users/victoriabernard/cf-github/workers-docs/workers-site

Nit: Succesfully should be spelled Successfully while we at it

so the trick with this is that we don't know what the user's static file directory is called. i can make a PR to improve the message tho- let me see what i can come up with


chore: upgrade to greengrass logging 2.2.0

Issue #, if available:
Description of changes:
Upgrade to version 2.2.0 of https://github.com/aws-greengrass/aws-greengrass-logging-java
Pre-requisite: merge https://github.com/aws-greengrass/aws-greengrass-logging-java/pull/171
Why is this change necessary:
Newer versions of logback and slf4j-api.
How was this change tested:

[x] Updated or added new unit tests.
[ ] Updated or added new integration tests.
[ ] Updated or added new end-to-end tests.
[ ] If my code makes a remote network call, it was tested with a proxy.

Any additional information or context required to review the change:
Documentation Checklist:

[ ] Updated the README if applicable.

Compatibility Checklist:

[ ] I confirm that the change is backwards compatible.
[ ] Any modification or deletion of public interfaces does not impact other plugin components.
[ ] For external library version updates, I have reviewed its change logs and Nucleus does not consume
any deprecated method or type.

Refer to Compatibility Guidelines for more information.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

You must update the pom.xml to exclude the default logging implementation ch.qos.logback.classic.spi.LogbackServiceProvider
https://github.com/aws-greengrass/aws-greengrass-nucleus/blob/619192e6babcd855a3fd33d27d5609f694872a96/pom.xml#L668
Test this change yourself before putting up the PR. Make sure the logs are proper. Log to standard out should not show "SLF4J: Class path contains multiple SLF4J providers."


fix: Switch to dot constructor in defrecords

Avoids cljs warning about ->ConditionedGPM being undefined

Can you add a note to the PR about why this imwarning is coming up, maybe a link to the conversation with Thomas?

Sure. Thomas didn't have much to say, other than that he didn't think it was related to shadow.
Background
I started getting the following warning in shadow-cljs when trying to load the inferenceql.inference.gpm.conditioned ns. Clojure worked ok, and it appears the existing node-based tests at the command-line worked ok as well. There may be some loading order confound, not sure.
The docs make no promises about the availability of the arrow constructor inside a defrecord form. To be safe, this PR changes the constructor from the arrow form to the dot form, which compiles without warning.
------ WARNING #1 - :undeclared-var --------------------------------------------
 File: /Users/matthew/.gitlibs/libs/io.github.inferenceql/inferenceql.inference/40e77dedf680b7936ce988b66186a86f5c4db6a5/src/inferenceql/inference/gpm/conditioned.cljc:21:8
--------------------------------------------------------------------------------
  18 |   gpm.proto/Condition
  19 |   (condition [_ new-conditions]
  20 |     (let [merged-conditions (merge conditions new-conditions)]
  21 |       (->ConditionedGPM gpm merged-conditions))))
--------------^-----------------------------------------------------------------
 Use of undeclared Var inferenceql.inference.gpm.conditioned/->ConditionedGPM
--------------------------------------------------------------------------------
  22 |
  23 | (defn condition
  24 |   "Conditions gpm based on conditions via rejection sampling. Arguments are the
  25 |   same as those for `inferenceql.inference.gom/condition`."
--------------------------------------------------------------------------------

Can someone with permissions merge this, and then give me permissions for the future?

Oh I didn't expand out context and see that this was inside that record's definition! Yes this makes sense and this is what I do as well (vs the alternate approach of
(declare ->....)
Good stuff and thanks for the extra context.

@sritchie Thing is, it works just fine in Clojure, though there's nothing in the docs actually promising that.
As I wrote on ask.clojure.org:

I noticed that in the clj defrecord macro, the symbols for ->Foo and map->Foo are declared first thing, but in cljs, the related build-positional-factory and build-map-factory fns are called at the end, after emit-defrecord. Perhaps that's the issue?

Hopefully it will be synchronized between clj and cljs and/or have the docs clarified on this matter.


Release new version

Hi, as I'm about to release a tool and I use features of the current master branch, I'm highly interested in a new release of evdev.
Is there anything that has to be in, or done for, a new release?
Also, IIUC from #39, @coolreader18 has been enabled to publish a release to crates.io so emberian does not need to be involved?

Sure! Gimme one sec.


Consider dropping PhantomJS from the Travis matrix

the PhantomJS webdriver implementation has not made much progress in years AFAICT, as GhostDriver (the project writing this implementation) does not have an active maintainer anymore, and PhantomJS has not brought an update of ghostDriver since years (last sync was 4 years ago, for GhostDriver 1.0.0, meaning that improvements done in the meantime are unavailable when using phantomjs --webdriver).
So I suggest dropping it from our test matrix.

Thus, for people wanting to use PhantomJS to run tests to avoid the need for xvfb on CI servers, there is a now a community driver using it directly and with a much better support of the Mink Driver API.

Ageed. Just to be sure people are aware of this PhantomJS driver I recommend advertising it on this driver README.md.

on this driver README.md.

We never advocated phantomjs --webdriver in the readme. and in the doc, we say we run tests against it but they never passed. So I think it is not necessary
There is a WIP about linking to the PhantomJS driver in the doc though

refs #132

Btw, the main reason I have to vote here is that PhantomJS itself seems to have abandonned it (no update of the GhostDriver code to their last release, and even less to the unreleased community fixes of the past few years)

PhantomJS development has been officially halted, and the project was archived. I agree we should not continue running tests on it.
Ref. https://github.com/ariya/phantomjs/issues/15344

What is the alternative?

wrell, phantomJS was already an alternative here. It is not the main webdriver implementation.


Android Basics: Collections

https://developer.android.com/codelabs/basic-android-kotlin-training-collections
What do collections have to do with "Navigate between screens"???
I understand courses have prerequisites, but these courses are organized very poorly.  If I want to learn about collections, I'll watch a "Collections" tutorial.  If I want to learn about navigation, I watch a "Navigation" tutorial.

Which Task and Step are you referring to?

It appears that in the March 29 update this comingling of topics was resolved.


AWS elastic beanstalk deploy

Hi,
I am facing trouble while I am deploying the project in AWS EBS. Here is the log screenshot. I followed the windows installation from ur docs and the zipped the project and deploy it in a Docker container.

Hey @Aisha-Barahim. You can find more details on how to deploy a docker container on Amazon EBS here: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker.container.console.html
Good luck!


[don't merge] Add Artifactory package.

cc @jainishshah17.

@ssk2, @jainishshah17 — Just a heads-up that I just force pushed to this branch with all of the changes from here and Jainish's fork of the Universe. This should now be the latest version of the Artifactory package. There are still a few changes that need to be made, so let's not merge this one just yet.

@rji : I have added changes we discussed Yesterday in fork

@jainishshah17 — updated PR based on your fork

@ssk2 @rji : can you please change Artifactory-Pro image from jainishshah17/artifactory:latest to jfrog-docker-reg2.bintray.io/jfrog/dcos-artifactory-pro:4.8.2 in resource.json

@jainishshah17 Updated!

@rji, @jainishshah17: I just force pushed a rebased version of this branch.

@BenWhitehead: let me know when you've managed to update the whitelist. Then we're ready to go :)


Go 1.12 update

A breakup of https://github.com/EnMasseProject/enmasse/pull/2948/ that only includes the fix for https://github.com/EnMasseProject/enmasse/issues/2486
How to Test
Ensure you have go 1.12+ installed and run make.  Without this PR the vet tool will fail to run, with the vet tool it will run.

I think this change would mean the minimum Go version would change to 1.12.   See any problems with updating Go now, or any CI implications,  @ctron and @kornys?
This ought to be reflected in the HACKING.md file in the project's root.

I think it is ok to move along to Go 1.12. However we should make that a conscious decision, as this also impacts the downstream release. As we do need Go 1.12 support there as well
But I think it makes sens doing the upgrade. And I think we could target that for 0.29.
@kornys That would mean that we need Go 1.12 images for building.

@ctron thb I don't know which version of ho is currently installed on CI images

@k-wall I just tried the command on go 1.10 and it works just fine.  This PR only makes the project buildable in go 1.12

I think we should plan to migrate in the next version.


Additional Components or Layouts for the Provider Grid

As a developer I want to be able to include Web3Connect components in a variety of ways, the Provider Grid as its own component exported would enable an easier integration experience for the multiple providers configured throughout the core, and remove the requirement to connect through providers through the modal interface.

I am working on "a Angular version" of Web3modal.
It is very difficult to customize Web3modal as it. Instead, I strive to make it possible for the developers to roll out their own widgets with ease.

i wonder if we could make them even more agnostic
since the use styledcss in components right now

The additional components is kinda tricky one to scope since it could be either too flexible to introduce to many edge cases or not flexible enough to be valuable.
I've already included Themes for changing colors with v1.2.0 which adds some customization so  I like the idea of Layouts to include a few different options for alignment and etc.
Web3Modal is built with react so Im not sure how the removal of styled-components would make it easier to customize it anyway. However I might remove styled-components to reduce bundle size.

Feedbacks addressed on W3MV2 - framework agnostic, additional components that can support the whole onboarding experience of users. Checkout the demo or pull the recent changes :)


No atomic instructions on i386

Atomic instructions are used in include/internal/refcount.h which are only
available on i486 or later.  This is an issue mainly on djgpp where i386
compatibility is generally desired.
There is a macro to disable it, but the commit that introduced it specifically
warns:

Configure with -DOPENSSL_DEV_NO_ATOMICS and you get refcount without
atomics.  This is intended for internal development only, to check the
refcounting is properly coded.  It should never become a configuration
option, hence the name of the macro.

(503d4745a115b82db01c1fb22baaddb153d27cdb)
But is this also the case when the target has no native thread support?  A user
could of course call libssl functions from interrupt context, but that should
probably not be recommended.
Is it reasonable to introduce something like the following?
--- a/include/internal/refcount.h
+++ b/include/internal/refcount.h
@@ -13,7 +13,7 @@
 # include <openssl/e_os2.h>
 # include <openssl/trace.h>

-# ifndef OPENSSL_DEV_NO_ATOMICS
+# if defined(OPENSSL_THREADS) && !defined(OPENSSL_DEV_NO_ATOMICS)
 #  if defined(__STDC_VERSION__) && __STDC_VERSION__ >= 201112L \
       && !defined(__STDC_NO_ATOMICS__)
 #   include <stdatomic.h>

Using that define looks like it would work properly.
Configuring with -DOPENSSL_DEV_NO_ATOMICS ought to be enough.
I'm not sure what your suggested change brings.

The difference is in intent.  There shouldn't be a no-atomics option and -DOPENSSL_DEV_NO_ATOMICS is specifically meant for development purposes.  But if a user configures with no-threads, that means it's safe to implicitly disable atomics, too.

marking as inactive, will be closed at the end of the 3.4 dev cycle barring further input

Already fixed by #19751, I forgot to link this issue # there.


Add listener for the process itself

Q
A

Bug?
No

New Feature?
yes

Version Used
i don't know

FFmpeg Version
FFmpeg 2.7

OS
Ubuntu 14.04

i'm using PHP-FFMpeg to  convert multiple videos together, each one is being run by a separate PHP script.
I need a way to know the PID of the ffmpeg process when it start to be able cancel the right process.
I didn't find a way to know the current running ffmpeg proccess PID in my version of PHP-FFMpeg, i  need to store the PID of the current running one to be able to shut it down later.
I think adding some kind of a listener to the process itself when it start or end , etc would get handy in many cases with multiple ffmpeg processes cases like the one i have

I make a workaround to control the process :
//Retrive the PID of the current symfony task //My project store this pid in a database $pid = getmypid();
And to kill the task process and all children process :
public function recursiveKill($pid) {         $child_pid_list = array();         exec('pgrep -P '.$pid, $child_pid_list);         foreach ($child_pid_list as $child_pid) {             if (preg_match('#[0-9]+#', $child_pid)) {                 $this->recursiveKill($child_pid);             }         }         exec('kill -9 '.$pid);     }
So if avconv or ffmpeg is currently running in a php cli task, it will be killed by :
$my_class->recursiveKill(1234)

I need this to implement the pause and resume system process function.

I'm not sure whether this is even possible, as the action is blocking the hole thread. It isn't designed to be able to interrupt the process.