Idea: Dynamic deploy configurations

Hi @nickfan
I had an idea... not fully baked and ready for any PR.
Like the question in #7 , I too want to separate staging and production deploys in a more dynamic way than a symlink. I would, for example, want to default to a "safe" deploy target. Let me know if any of the below would be interesting to make a bit nicer and pull back into the project.
Here is where I am so far:
I am modifying the @include line at the top of Envoy.blade.php to allow for a variable filename.
@include('envoy.'.env('CONFIG', 'config').'.php');
I can then call envoy and prepend a temporary env variable called CONFIG.
CONFIG=production envoy run deploy
This gets me a default running of the default config file and allows for additional files to be chosen using this env var. I am not super happy about the resulting filenames. But I preferred to retain compatibility with the default filename without complicating the change. envoy.production.php is not a great filename but I can live with it.
I initially wanted an Envoy argument to specify the config file or "deploy type". E.G:
envoy run deploy --config=production
I did not get that working. I guess that Envoy is not fully bootstrapped at the time of this include, which is done by Blade.
I also thought about possibly doing it in the config file. E.g. including additional files if the variable is found... this could be interesting in allowing part of the config to be global and other parts to be specific to the deployment type.

env('CONFIG', 'config')

require function define or vendor loaded (composer install dotenv) first.

Hi there,
I'm very late for this, but I've been trying to implement your awesome envoy file to my project.
I also needed different config files, so here is what I did and works for me.

Remove @include('envoy.config.php'); ate the top of the file
At the beginning of @setup I wrote this:

@setup
    if ( isset($config) && file_exists("envoy.config.$config.php") ){
        include("envoy.config.$config.php");
    }
    else{
        include("envoy.config.php");
    }

    ...

@endsetup

I can now use --config=something to load envoy.config.something.php
Hope this helps :)

i just use sym links.
to change just:
ln -nfs envoy.config.development.php envoy.config.php


Output panel text sometimes invisible until scrolling

I fairly frequently have the issue that the Output panel is completely blank after a build. As soon as I start scrolling however, the output shows up.
I think this generally only happens when the panel is not active (I usually have the Results panel active in the same "container" and then switch to Output after a build). Maybe a refresh is missing when switching the active panel?

Just wanted to report this issue.
Build the project, then hover over the docked (with autohide) Output panel, it pops up, according to the vertical scrollbar there's almost two screens of content, scrolled all the way to the bottom (so nothing is showing). Scrolling up reveals the build messages, scrolling back down looks ok.

Issue is still present.
Running my app, then opening output - nothing displayed until trying to scroll with mouse wheel, then all the previously output text shows up. Using the app again (in a way which produces trace output) also displays all the contents.

Just downloaded build <IP_ADDRESS> to try out your fix. It still looks broken to me.

Output panel is auto-hide (and hidden), building and running my app (AIR)
Do something in my app that produces debug output
Go to FD and hover mouse over Output to auto-show it

Scrollbar is at the bottom, indicating presence of content
But no content is visible

Use mouse wheel over the output panel

Debug output appears

I'm sure you tried a wrong build 😜. I'll try to take a look, but I checked the same thing as you do when fixing this, except using Haxe instead of AIR.

Well it was the latest FlashDevelop-development.zip
Numbered <IP_ADDRESS>

I see you are using a custom theme, what if you use one theme without custom scrollbars? do you get the same result?

OK, found how it can still be reproduced. In the case where FD opens directly the output panel hidden and the user never gets to display it, the Output field will never get a height higher than 0, so this problem happens, although it will be right the following times.
Not really sure what may be the best solution, giving a default solution may still produce visual problems, the other option would be to get the owner dock panel and get the height it will get when showing it, but looks a bit ugly as a solution.

What happens on mouse wheel action that the output can show? And why can't the same action be applied when opening the auto-hidden Output panel?


Combine projects and tags in the same search results list

Goal

Improve the UX when searching, to fix #246 by combining projects and tags in the same search result list, sorted by relevance, instead of separating them.
When a tag is selected, make the fact that the search is scoped to the tag mroe obvious

How to test

Try to search for react, notice how the list shows both the React project and the React tag
Open a tag (say the React tag), then open the search modal

Screenshots
Default state (no query, no tags)
Showing the most popular tags

Searching
Showing a mix of projects and tags

Start the search when a tag is selected

The place holder has changed to explain that the search is now "scoped" to one or several tags
The list shows the "Related Tags" instead of the popular tags
The icon of the tag entry has changed to convey the fact that it will open a page that combine several tags (instead of a single one)

Searching when a tag is selected

Next iteration
Adding checkboxes to toggle projets and tags


Floating and standalone plugins respect minimum dimensions

Set parentItem after resizing the dialog

Create minimum height and width card properties

Set height and width of card on adding a child plugin

Enforce minimum dimensions on floating plugin resize

Signed-off-by: Sarathkrishnan Ramesh<EMAIL_ADDRESS>

Instead of setting height and width on Component.onCompleted I set the height and width of the card pane when the child plugin is added. This way we don't require to change any of the plugins.


Semi-fixes static linking for Mac OS

Fixes https://github.com/danielpclark/rutie/issues/57

Oh interesting! Those tests actually pass on my machine. I can try to investigate a bit more what's going on.

Last change didn't seem to work for rvm. I'll investigate more closely what's going on.

I'm currently just playing around with the code and Travis, I'll ping you again once I have a final PR.

@danielpclark alright, after a few tries, I managed to properly install with rvm, compile the static ruby lib and link it in the tests.
I believe the previous build was probably linking the wrong lib as the build script was not doing the right thing to install the static version.
There is still the same 3 tests failing. As you can see, the test failure output is now different. You now have information on why it's failing:
---- src/class/string.rs - class::string::RString::from_bytes (line 110) stdout ----
thread 'src/class/string.rs - class::string::RString::from_bytes (line 110)' panicked at 'test executable failed:
/tmp/rustdoctestpXiTXC/rust_out: symbol lookup error: /home/travis/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/x86_64-linux/enc/encdb.so: undefined symbol: rb_encdb_declare

Now this reproduces the behaviour on my machine.
I believe this is ready to merge as a step in the right direction. Let me know if anything!

Thank you for putting in the work! :grin:

@danielpclark any time!


[Debug] Sort timeline elements by start and duration.

This PR implements a sorting algorithm to the elements of the debug toolbar timeline.
Such sorting seems to be intended (and is useful) but has likely been forgotten:
https://github.com/codeigniter4/CodeIgniter4/blob/e73f750f224344964942574845dc214df5f5bee7/system/Debug/Toolbar.php#L247-L249
In principle, many of the elements are pre-sorted by nature, but chaos grows when multiple collectors are active (e.g. from Modules etc.).
I decided to sort the elements ascending by start time and then descending by duration time.
I.e., if a timed portion of code calls another timed portion of code and the timer start times happen to be equal (possibly unlikely, but just in case), the "outer" timer will be displayed first in the timeline.
This sorting also prepares for a possible "collapsible" timeline, which I need to think about how to realize.
Open for other opinions/ideas 😄
Forum link for discussion.
Timeline before changes:

Timeline after changes:

Note that due to the styling of the single timeline elements (a left-right-padding of 5px), some very small elements appear to still be shifted on the first glance, but they're not if one puts a ruler on it 😆
Checklist:

[x] Securely signed commits
[x] Component(s) with PHPdocs
[x] Conforms to style guide

I'm just wondering though why there are gaps in between

Was wondering the same. I have to check. Might be some 'pre_system' events that I registered.

Gantt chart with more or less overlapping bars.

In principle the bars would not overlap at all. The styling however applies a horizontal padding of 2*5px to achieve the 4px border-radius.

Well, yes, I mean not technically overlapping. But the end of one bar is aligned with the start of the next bar on the next line.

In that case, yes 😄
I just checked, it's not the pre_system events, they're included in the bootstrap timer.
In my case, it is the before filters in handleRequest()

Can you target 4.2 instead?

Well, yeah, this went down the drain 😆

Just for future reference: Is there a proper way to switch the target branch? Both switching it here in the PR and rebasing the local repo to 4.2 resulted in additional commits.

I think you need to branch off first from 4.2 branch for your PR branch whenever it is for content changes.

Probably beat to start over here. You want something like this (assuming you have your fork as origin and the main repo as upstream):
git fetch upstream
git switch -c sort-debugbar-timeline upstream/4.2


Add the possibility to not use interrupt for events but to poll for them

This will decrease performance but make the program more stable because there will never be interrupt when they (the interrupts) are locked.

Hello~
I come from the project of Thomas' project and work on this modules for a while, and there is a problem confused me for a long time.
Although I read most of Thomas' code, including DW1000Raing.cpp and DW1000.cpp. I don't really understand when will the interrupt happens.
When I source back to the attachInterupt() function, I know it happens when the IRQ pin changes but I don't know when the IRQ pin change. I guess it will be changed when it sent/receive a message, but I don't see any codes about changing that pin, is it depends on the inside circuit or I not found it?
Thanks for your reply!!!

Yeah it is an inside mechanism of the dw1000 itself, there is a register
inside the chip that controls when to send an interrupt relative to the
selected elements.(we add a struct and a method to select them)
On Wed, 10 Oct 2018, 18:32 Elon-Wang<EMAIL_ADDRESS>wrote:

Hello~
I come from the project of Thomas' project and work on this modules for a
while, and there is a problem confused me for a long time.
Although I read most of Thomas' code, including DW1000Raing.cpp and
DW1000.cpp. I don't really understand when will the interrupt happens.
When I source back to the attachInterupt() function, I know it happens
when the IRQ pin changes but I don't know when the IRQ pin change. I guess
it will be changed when it sent/receive a message, but I don't see any
codes about changing that pin, is it depends on the inside circuit or I not
found it?
Thanks for your reply!!!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/F-Army/arduino-dw1000-ng/issues/89#issuecomment-428641135,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWi_Nrr0fA7MA1igye45TxwhtCkmmt3kks5ujiEWgaJpZM4W8F7Z
.

Yeah it is an inside mechanism of the dw1000 itself, there is a register inside the chip that controls when to send an interrupt relative to the selected elements.(we add a struct and a method to select them)
…
On Wed, 10 Oct 2018, 18:32 Elon-Wang, @.***> wrote: Hello~ I come from the project of Thomas' project and work on this modules for a while, and there is a problem confused me for a long time. Although I read most of Thomas' code, including DW1000Raing.cpp and DW1000.cpp. I don't really understand when will the interrupt happens. When I source back to the attachInterupt() function, I know it happens when the IRQ pin changes but I don't know when the IRQ pin change. I guess it will be changed when it sent/receive a message, but I don't see any codes about changing that pin, is it depends on the inside circuit or I not found it? Thanks for your reply!!! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#89 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AWi_Nrr0fA7MA1igye45TxwhtCkmmt3kks5ujiEWgaJpZM4W8F7Z .

Thank you for your reply, that really helps me a lot!! I finally find someone who can answer my question.😊😊
After I set the antenna delay, the one to one ranging become precise however when I use three anchors and one tag to do the ranging, there are only one pair of ranging turn out to be reliable, while the other two are quite wrong. The anchor with right raging data is random. For example, if I have three anchors A B C, and turn them on, only A get the right ranging data. However, If you turn anchor A off, one of the rest anchor will work well, the other is still reading the wrong distance. The same phenomenon happens when you turn the second anchor off.
Then I turn them down and using the anchor which is works well to print out the timestamp of Poll/PollACK/Ranging , and calculate the reply1 round1, reply2 , round2.  However, those ridiculous timestamps can calculate out the right distance using the formula (Tround1 * Tround2 - Treply1 * Treply2)/ (Tround1 + Tround2 + Treply1 +Treply2) .
Have you ever encounter with the same problem? Is this out of the non-calibration of crystal oscillator,if yes,how to do it? If you know the reason, please tell me how to solve it.
I'm very grateful!!!

So, you haven't try multiple anchors locate yet?
We can discuss later, lol
Time is very late in my time zone and I have lots of courses in tomorrow~
I'll open an issue soon and introduce more about my issue.
Anyway, thanks a lot for your help.

Yeah, we rewrote a lot of the thotro's driver, this is still a work in progress, we wanted to get rid of DW1000Ranging as a loop and instead to make it a library compliant with ISO/IEC-24730/62 to leave the user with more control on the action flow.
I was asking about how you did the 3 anchor range because thotro's library doesn't use frame filtering, so every anchor will be receiving the messages from the tag and probably overlapping when responding. When we finish making the examples using the ISO standard MAC format we will check if the frame filtering code. For the moment you could try to add a destination address inside the sent data and check at the receiver if it was for it and discard other anchor's frames.(the standard uses both source and destination addresses).
Feel free to ask any questions!

done


Vyper upgrades, etc

Addresses #153, #138
What I did

upgrade vyper to recent commit

custom units
change int128 to uint256 for all non-negative integers
no vyper support for convert (uint256 -> decimal) yet so there are a lot of (uint256 -> int128 -> decimal) converts for the time being

deploy contract via irregular state change in testing

contract size exceeds EIP170 limits
good sample code for future py-evm implementation

vyper currently drops units when doing a convert

add constants  ONE_WEI_UINT256 and ONE_WEI_DECIMAL to be able to add wei units back in after a convert strips them.
This is a bug filed here https://github.com/ethereum/vyper/issues/865. Looks like it will be fixed shortly

Tests were about 10x slower when we used eth-tester==0.1.0b26 && py-evm==0.2.0a18. Downgraded to eth-tester==0.1.0b24 && py-evm==0.2.0a16 and performance went back to normal.

A couple of build errors. Fixing now

fixed. ready for review

You're right. I'm switching everything to wei_value for now.


draft: print tracing::Span data through diem::Logger

Motivation
Resolves https://github.com/diem/diem/issues/9884. Few notes on this PR:

Note that this branch isn't complete because the span values are double-escaped. I'm decently sure this is happening because there are two visitors (tracing's and diem's logger's) recording the data. Here's a sample of the current output:

2021-12-04T17:19:53.086624Z [verify_tracing_kvs] ERROR  {"another_value":"hello","message":"hello world","outer.inner.one":"\"hello\"","outer.inner.two":"\"two\"","outer.one":"\"hello\"","outer.two":"\"two\""}

To resolve this, I think that the Value enum needs to be given an additional variant representing raw strings or the visitors need to be unified. Up to y'all on which approach I take.
To avoid clobbering span fields (in the instance where an parent and child span both have the same field name), I've updated the layer to prefix each field key with its span's name (as well as any parent span's name). For a field named one in whose span is inner and whose parent span is outer, the field name will be rendered as outer.inner.one. To support this, I had to loosen the restrictions on Key from being represented entirely as a &'static str, but instead as a Cow<'static str>. I'm happy to roll this change back if y'all are okay with a single field's key potentially mapping to multiple values.

Have you read the Contributing Guidelines on pull requests?
Yes, but too late to have semantic commits. This is PR is work-in-progress and not that large, so I'll squash my commits down to a single, semantic commit before merging.
Test Plan
Testing this through adding unit tests. They'll be expanded before this is marked as "not a draft".
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/diem/diem/tree/main/developers.diem.com, and link to your PR here.)
[will add]
If targeting a release branch, please fill the below out as well
N/A

Regarding the CLA, my employer is Meta, so I don't believe it's required.

Regarding the CLA, my employer is Meta, so I don't believe it's required.

Yeah no need to worry about this

To resolve this, I think that the Value enum needs to be given an additional variant representing raw strings or the visitors need to be unified. Up to y'all on which approach I take.

Yeah I think using another variant would be ok, assuming that's the easiest solution. I wonder if the Display variant would be sufficient to handle that? Or does that not work due to needing the value to be owned?

Looks great! Once we get the double quoting thing fixed we can get this merged.
Couple things/questions:

Looks like you'll need to rebase on the latest tip of main, this is my fault as I was moving some stuff around and moved the logger crate from the common directory to the crates directory. Should hopefully be a straight forward rebase 🤞🏼
At first glance this looks like it only supports recording the span data when invoking a tracing log macro and not when the diem log macros are used. Is that correct? Ideally we'd be able to get the span data in both cases but that can be done at a later point in time (or maybe by then tracing will support valuable)

Yeah I think using another variant would be ok, assuming that's the easiest solution. I wonder if the Display variant would be sufficient to handle that? Or does that not work due to needing the value to be owned?

I'll need to double-check on this; I'm not sure right now.

Looks like you'll need to rebase on the latest tip of main, this is my fault as I was moving some stuff around and moved the logger crate from the common directory to the crates directory. Should hopefully be a straight forward rebase 🤞🏼

Sounds good; I'll get on that!

At first glance this looks like it only supports recording the span data when invoking a tracing log macro and not when the diem log macros are used. Is that correct? Ideally we'd be able to get the span data in both cases but that can be done at a later point in time (or maybe by then tracing will support valuable)

I think you're right—that's an oversight on my part. I think—[knocks on wood]—that tracing 0.2 with Valuable support should be out soon-ish.

I accidentally closed the PR! sorry about that.

Dependency update review
tracing-core updated: 0.1.18 --> 0.1.21
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed13total rust files changed8total loc change571

Click to show changed files

src/dispatcher.rs
src/field.rs
CHANGELOG.md
Cargo.toml
.cargo_vcs_info.json
Cargo.toml.orig
src/lib.rs
src/spin/once.rs
src/event.rs
src/span.rs
src/metadata.rs
src/subscriber.rs
README.md

Click to show changed files with unsafe code

src/dispatcher.rs
src/metadata.rs
src/spin/once.rs
src/subscriber.rs

LSR dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex 1.4.3 (transitive third-party, crates.io)
    * (old features: std)
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R regex-syntax 0.6.23 (transitive third-party, crates.io)
    * (old features: default, unicode, unicode-age, unicode-bool, unicode-case, unicode-gencat, unicode-perl, unicode-script, unicode-segment)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

release binaries dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

LEC dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

Dependency update review
tracing-core updated: 0.1.18 --> 0.1.21
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed13total rust files changed8total loc change571

Click to show changed files

CHANGELOG.md
.cargo_vcs_info.json
Cargo.toml.orig
src/event.rs
src/metadata.rs
src/span.rs
src/spin/once.rs
Cargo.toml
src/lib.rs
src/field.rs
src/subscriber.rs
src/dispatcher.rs
README.md

Click to show changed files with unsafe code

src/dispatcher.rs
src/metadata.rs
src/spin/once.rs
src/subscriber.rs

LEC dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

release binaries dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

LSR dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex 1.4.3 (transitive third-party, crates.io)
    * (old features: std)
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R regex-syntax 0.6.23 (transitive third-party, crates.io)
    * (old features: default, unicode, unicode-age, unicode-bool, unicode-case, unicode-gencat, unicode-perl, unicode-script, unicode-segment)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

LEC dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

release binaries dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

Dependency update review
tracing-core updated: 0.1.18 --> 0.1.21
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed13total rust files changed8total loc change571

Click to show changed files

.cargo_vcs_info.json
README.md
src/metadata.rs
src/subscriber.rs
src/event.rs
src/dispatcher.rs
src/field.rs
CHANGELOG.md
src/spin/once.rs
src/span.rs
Cargo.toml.orig
Cargo.toml
src/lib.rs

Click to show changed files with unsafe code

src/dispatcher.rs
src/metadata.rs
src/spin/once.rs
src/subscriber.rs

Dependency update review
matchers updated: 0.0.1 --> 0.1.0
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed9total rust files changed1total loc change394

Click to show changed files

src/lib.rs
Cargo.toml
CHANGELOG.md
.clog.toml
.github/workflows/ci.yml
.cargo_vcs_info.json
README.md
azure-pipelines.yml
Cargo.toml.orig

Click to show changed files with unsafe code

src/lib.rs

tracing-subscriber updated: 0.2.18 --> 0.3.3
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed65total rust files changed60total loc change14,263

Click to show changed files

tests/layer_filters/main.rs
tests/reload.rs
tests/support.rs
src/prelude.rs
src/filter/layer_filters.rs
tests/multiple_layer_filter_interests_cached.rs
src/fmt/time/datetime.rs
src/sync.rs
src/filter/mod.rs
src/reload.rs
tests/layer_filters/downcast_raw.rs
tests/layer_filters/trees.rs
CHANGELOG.md
tests/layer_filters/filter_scopes.rs
tests/unhinted_layer_filters_dont_break_other_layers.rs
tests/layer_filter_interests_are_cached.rs
src/fmt/format/mod.rs
src/registry/mod.rs
tests/duplicate_spans.rs
src/field/delimited.rs
src/registry/sharded.rs
src/field/mod.rs
src/fmt/fmt_layer.rs
src/macros.rs
src/registry/extensions.rs
src/lib.rs
src/fmt/writer.rs
tests/layer_filters/targets.rs
src/layer/layered.rs
src/fmt/format/pretty.rs
src/fmt/format/json.rs
src/fmt/mod.rs
src/fmt/time/mod.rs
src/field/debug.rs
src/filter/env/directive.rs
src/field/display.rs
tests/filter_log.rs
src/filter/targets.rs
src/layer/context.rs
tests/cached_layer_filters_dont_break_other_layers.rs
src/registry/stack.rs
Cargo.toml
src/filter/level.rs
tests/field_filter.rs
tests/registry_with_subscriber.rs
README.md
tests/hinted_layer_filters_dont_break_other_layers.rs
src/filter/env/field.rs
src/thread.rs
tests/registry_max_level_hint.rs
src/layer/mod.rs
src/filter/directive.rs
src/fmt/time/time_crate.rs
tests/utils.rs
src/filter/filter_fn.rs
src/filter/env/mod.rs
src/layer.rs
tests/same_len_filters.rs
tests/fmt_max_level_hint.rs
src/util.rs
Cargo.toml.orig
src/layer/tests.rs
tests/filter.rs
tests/layer_filters/boxed.rs
.cargo_vcs_info.json

Click to show changed files with unsafe code

src/filter/layer_filters.rs
src/fmt/fmt_layer.rs
src/fmt/mod.rs
src/layer.rs
src/layer/layered.rs
src/layer/mod.rs
src/thread.rs

tracing-core updated: 0.1.18 --> 0.1.21
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed13total rust files changed8total loc change571

Click to show changed files

src/event.rs
src/lib.rs
src/spin/once.rs
src/dispatcher.rs
src/subscriber.rs
src/span.rs
src/metadata.rs
Cargo.toml.orig
CHANGELOG.md
README.md
.cargo_vcs_info.json
Cargo.toml
src/field.rs

Click to show changed files with unsafe code

src/dispatcher.rs
src/metadata.rs
src/spin/once.rs
src/subscriber.rs

LEC dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

LSR dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex 1.4.3 (transitive third-party, crates.io)
    * (old features: std)
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R regex-syntax 0.6.23 (transitive third-party, crates.io)
    * (old features: default, unicode, unicode-age, unicode-bool, unicode-case, unicode-gencat, unicode-perl, unicode-script, unicode-segment)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

release binaries dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

Dependency update review
tracing-core updated: 0.1.18 --> 0.1.21
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed13total rust files changed8total loc change571

Click to show changed files

src/spin/once.rs
src/subscriber.rs
src/metadata.rs
src/span.rs
src/event.rs
.cargo_vcs_info.json
Cargo.toml
Cargo.toml.orig
README.md
src/dispatcher.rs
CHANGELOG.md
src/field.rs
src/lib.rs

Click to show changed files with unsafe code

src/dispatcher.rs
src/metadata.rs
src/spin/once.rs
src/subscriber.rs

tracing-subscriber updated: 0.2.18 --> 0.3.3
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed65total rust files changed60total loc change14,263

Click to show changed files

src/fmt/time/datetime.rs
tests/field_filter.rs
tests/layer_filters/downcast_raw.rs
Cargo.toml
tests/registry_with_subscriber.rs
src/reload.rs
tests/hinted_layer_filters_dont_break_other_layers.rs
src/field/delimited.rs
tests/layer_filter_interests_are_cached.rs
src/fmt/format/mod.rs
tests/duplicate_spans.rs
tests/utils.rs
src/fmt/format/json.rs
tests/cached_layer_filters_dont_break_other_layers.rs
tests/layer_filters/targets.rs
src/fmt/writer.rs
src/util.rs
src/fmt/fmt_layer.rs
src/filter/mod.rs
src/layer/context.rs
src/registry/stack.rs
src/fmt/format/pretty.rs
src/lib.rs
src/fmt/time/mod.rs
src/thread.rs
src/filter/directive.rs
tests/reload.rs
tests/unhinted_layer_filters_dont_break_other_layers.rs
src/fmt/time/time_crate.rs
src/registry/mod.rs
tests/registry_max_level_hint.rs
src/filter/env/field.rs
src/filter/filter_fn.rs
tests/filter.rs
src/field/debug.rs
src/registry/sharded.rs
tests/layer_filters/trees.rs
tests/fmt_max_level_hint.rs
src/macros.rs
src/fmt/mod.rs
.cargo_vcs_info.json
src/layer/layered.rs
src/filter/targets.rs
src/prelude.rs
tests/layer_filters/main.rs
tests/multiple_layer_filter_interests_cached.rs
src/layer/mod.rs
Cargo.toml.orig
tests/layer_filters/boxed.rs
src/filter/layer_filters.rs
src/field/mod.rs
src/layer.rs
tests/filter_log.rs
src/filter/env/directive.rs
CHANGELOG.md
README.md
tests/same_len_filters.rs
src/sync.rs
tests/layer_filters/filter_scopes.rs
src/filter/level.rs
src/registry/extensions.rs
src/filter/env/mod.rs
src/layer/tests.rs
tests/support.rs
src/field/display.rs

Click to show changed files with unsafe code

src/filter/layer_filters.rs
src/fmt/fmt_layer.rs
src/fmt/mod.rs
src/layer.rs
src/layer/layered.rs
src/layer/mod.rs
src/thread.rs

matchers updated: 0.0.1 --> 0.1.0
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed9total rust files changed1total loc change394

Click to show changed files

Cargo.toml
CHANGELOG.md
.clog.toml
src/lib.rs
README.md
Cargo.toml.orig
azure-pipelines.yml
.github/workflows/ci.yml
.cargo_vcs_info.json

Click to show changed files with unsafe code

src/lib.rs

LEC dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

release binaries dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

LSR dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex 1.4.3 (transitive third-party, crates.io)
    * (old features: std)
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R regex-syntax 0.6.23 (transitive third-party, crates.io)
    * (old features: default, unicode, unicode-age, unicode-bool, unicode-case, unicode-gencat, unicode-perl, unicode-script, unicode-segment)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

Looks great, one last request before we merge this: would you mind squashing your commits down to a single (or multiple if that makes sense) commits with clean commit messages?

Dependency update review
matchers updated: 0.0.1 --> 0.1.0
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed9total rust files changed1total loc change394

Click to show changed files

Cargo.toml.orig
src/lib.rs
.clog.toml
azure-pipelines.yml
.cargo_vcs_info.json
CHANGELOG.md
Cargo.toml
.github/workflows/ci.yml
README.md

Click to show changed files with unsafe code

src/lib.rs

tracing-subscriber updated: 0.2.18 --> 0.3.3
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed65total rust files changed60total loc change14,263

Click to show changed files

.cargo_vcs_info.json
tests/utils.rs
src/fmt/mod.rs
tests/layer_filters/targets.rs
src/layer/context.rs
tests/filter_log.rs
src/filter/targets.rs
src/thread.rs
tests/cached_layer_filters_dont_break_other_layers.rs
src/fmt/format/pretty.rs
tests/unhinted_layer_filters_dont_break_other_layers.rs
tests/reload.rs
src/prelude.rs
src/layer/mod.rs
src/registry/sharded.rs
tests/duplicate_spans.rs
src/filter/env/directive.rs
tests/hinted_layer_filters_dont_break_other_layers.rs
src/fmt/format/json.rs
tests/fmt_max_level_hint.rs
tests/multiple_layer_filter_interests_cached.rs
tests/same_len_filters.rs
src/filter/filter_fn.rs
src/layer/tests.rs
src/registry/mod.rs
src/fmt/time/time_crate.rs
src/macros.rs
src/fmt/time/mod.rs
tests/registry_with_subscriber.rs
tests/support.rs
src/filter/level.rs
tests/registry_max_level_hint.rs
CHANGELOG.md
Cargo.toml
src/registry/extensions.rs
tests/filter.rs
src/util.rs
src/field/debug.rs
src/sync.rs
src/reload.rs
tests/layer_filter_interests_are_cached.rs
tests/layer_filters/downcast_raw.rs
tests/layer_filters/main.rs
README.md
src/field/delimited.rs
src/filter/layer_filters.rs
src/lib.rs
src/layer.rs
src/filter/env/mod.rs
tests/field_filter.rs
tests/layer_filters/trees.rs
src/fmt/fmt_layer.rs
src/filter/env/field.rs
tests/layer_filters/boxed.rs
tests/layer_filters/filter_scopes.rs
src/layer/layered.rs
src/fmt/time/datetime.rs
src/registry/stack.rs
Cargo.toml.orig
src/filter/directive.rs
src/filter/mod.rs
src/field/mod.rs
src/fmt/writer.rs
src/field/display.rs
src/fmt/format/mod.rs

Click to show changed files with unsafe code

src/filter/layer_filters.rs
src/fmt/fmt_layer.rs
src/fmt/mod.rs
src/layer.rs
src/layer/layered.rs
src/layer/mod.rs
src/thread.rs

tracing-core updated: 0.1.18 --> 0.1.21
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed13total rust files changed8total loc change571

Click to show changed files

src/span.rs
src/lib.rs
.cargo_vcs_info.json
CHANGELOG.md
src/dispatcher.rs
src/metadata.rs
src/subscriber.rs
src/spin/once.rs
Cargo.toml.orig
src/field.rs
README.md
src/event.rs
Cargo.toml

Click to show changed files with unsafe code

src/dispatcher.rs
src/metadata.rs
src/spin/once.rs
src/subscriber.rs

LSR dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex 1.4.3 (transitive third-party, crates.io)
    * (old features: std)
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R regex-syntax 0.6.23 (transitive third-party, crates.io)
    * (old features: default, unicode, unicode-age, unicode-bool, unicode-case, unicode-gencat, unicode-perl, unicode-script, unicode-segment)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

LEC dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

release binaries dependency change summary:
target packages:
  M tracing-subscriber 0.3.3 (direct third-party, crates.io)
    * version upgraded from 0.2.18
    * added features: alloc, std
    * removed features: chrono, env-filter, json, lazy_static, matchers, regex, serde, serde_json, tracing, tracing-serde
    * (unchanged features: ansi, ansi_term, default, fmt, registry, sharded-slab, smallvec, thread_local, tracing-log)
  M tracing-core 0.1.21 (transitive third-party, crates.io)
    * version upgraded from 0.1.18
    * (unchanged features: default, lazy_static, std)
  R matchers 0.0.1 (transitive third-party, crates.io)
    * (old features: [none])
  R regex-automata 0.1.9 (transitive third-party, crates.io)
    * (old features: default, regex-syntax, std)
  R tracing-serde 0.1.2 (transitive third-party, crates.io)
    * (old features: [none])

Dependency update review
matchers updated: 0.0.1 --> 0.1.0
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed9total rust files changed1total loc change394

Click to show changed files

.clog.toml
.github/workflows/ci.yml
Cargo.toml
CHANGELOG.md
azure-pipelines.yml
.cargo_vcs_info.json
src/lib.rs
README.md
Cargo.toml.orig

Click to show changed files with unsafe code

src/lib.rs

tracing-subscriber updated: 0.2.18 --> 0.3.3
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed65total rust files changed60total loc change14,263

Click to show changed files

tests/filter.rs
src/filter/level.rs
tests/layer_filter_interests_are_cached.rs
tests/layer_filters/trees.rs
src/fmt/writer.rs
src/registry/extensions.rs
src/registry/mod.rs
tests/layer_filters/main.rs
tests/cached_layer_filters_dont_break_other_layers.rs
tests/layer_filters/filter_scopes.rs
src/layer/mod.rs
tests/multiple_layer_filter_interests_cached.rs
src/layer/layered.rs
tests/duplicate_spans.rs
src/macros.rs
tests/layer_filters/downcast_raw.rs
src/fmt/time/datetime.rs
src/layer.rs
src/fmt/format/json.rs
src/lib.rs
src/sync.rs
tests/layer_filters/targets.rs
src/reload.rs
tests/field_filter.rs
src/registry/sharded.rs
tests/reload.rs
tests/support.rs
src/fmt/fmt_layer.rs
src/fmt/format/pretty.rs
src/layer/context.rs
src/field/display.rs
src/util.rs
tests/layer_filters/boxed.rs
tests/utils.rs
Cargo.toml
src/layer/tests.rs
src/fmt/format/mod.rs
src/field/mod.rs
src/filter/env/directive.rs
src/filter/directive.rs
src/filter/filter_fn.rs
README.md
tests/filter_log.rs
src/fmt/mod.rs
.cargo_vcs_info.json
src/prelude.rs
CHANGELOG.md
src/field/debug.rs
Cargo.toml.orig
src/filter/layer_filters.rs
src/thread.rs
src/fmt/time/mod.rs
src/filter/targets.rs
tests/fmt_max_level_hint.rs
src/filter/mod.rs
src/filter/env/mod.rs
tests/hinted_layer_filters_dont_break_other_layers.rs
src/field/delimited.rs
src/fmt/time/time_crate.rs
src/registry/stack.rs
tests/registry_max_level_hint.rs
tests/registry_with_subscriber.rs
src/filter/env/field.rs
tests/same_len_filters.rs
tests/unhinted_layer_filters_dont_break_other_layers.rs

Click to show changed files with unsafe code

src/filter/layer_filters.rs
src/fmt/fmt_layer.rs
src/fmt/mod.rs
src/layer.rs
src/layer/layered.rs
src/layer/mod.rs
src/thread.rs

tracing-core updated: 0.1.18 --> 0.1.21
No known advisories:white_check_mark:No change in the build script:white_check_mark:No change in any file with unsafe code:x:The source and crates.io code are the same:white_check_mark:

Cilck to show details

Click to show version diff summary
total files changed13total rust files changed8total loc change571

Click to show changed files

CHANGELOG.md
src/metadata.rs
README.md
Cargo.toml
src/event.rs
src/spin/once.rs
src/span.rs
src/subscriber.rs
src/dispatcher.rs
src/lib.rs
.cargo_vcs_info.json
Cargo.toml.orig
src/field.rs

Click to show changed files with unsafe code

src/dispatcher.rs
src/metadata.rs
src/spin/once.rs
src/subscriber.rs


added updates to automation lib for mini

Is there a reason this is still languishing in PR purgatory?


Invalid hyperlink to pdf

"For more information about the CarouselPage, see Chapter 25 of Charles Petzold's Xamarin.Forms book."

This seems to be outdated. The link to chapter 25 no longer seems to be working.

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

ID: b07827d3-68e2-b7e0-173d-f3c7ef581a8e
Version Independent ID: a19e5c74-5cd4-1291-af4d-a97d7a8d5dd0
Content: Xamarin.Forms Carousel Page - Xamarin
Content Source: docs/xamarin-forms/app-fundamentals/navigation/carousel-page.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Microsoft support for Xamarin will end on May 1, 2024 for all Xamarin SDKs including Xamarin.Forms. In preparation for this, all issues and PRs in this repository are being closed.
.NET MAUI is the replacement for Xamarin.Forms, and it's documentation can be found here.


Add BME280 Sensor code

### Summary
Pushed code for BME280 pressure, temperature, and humidity sensor.
### Test
Working. Requires calibration. For now, calibration is fixed by offset.

To add to docs


Update quick-create-portal.md

@jlichwa : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Suuport setting ttr in samples

Hi,
It seems like inserting  new job sample always setts ttr to 60 secs.
Would be useful if user can be allowed to set it as part of a sample data.
Thanks

@adizhol Thanks for your issue. I have added support setting TTR in add sample jobs and make a release. Please upgrade to the last version.


Inomurko/aws 0 gnosis network

run this on the host
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
safe-react container needs lots of watches

Codecov Report

Merging #288 (620ea35) into aws (9f73c11) will increase coverage by 17.86%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              aws     #288       +/-   ##
===========================================
+ Coverage   71.73%   89.59%   +17.86%
===========================================
  Files          68       33       -35
  Lines        2257     1086     -1171
  Branches      335      151      -184
===========================================
- Hits         1619      973      -646
+ Misses        638      113      -525

Flag
Coverage Δ

batch-submitter
?

contracts
89.59% <ø> (+0.06%)
:arrow_up:

core-utils
?

data-transport-layer
?

message-relayer
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

packages/core-utils/src/common/test-utils.ts

...ices/l1-ingestion/handlers/transaction-enqueued.ts

packages/message-relayer/hardhat.config.ts

packages/data-transport-layer/src/utils/eth-tx.ts

packages/batch-submitter/hardhat.config.ts

...ckages/data-transport-layer/src/utils/constants.ts

packages/core-utils/src/watcher.ts

...ackages/batch-submitter/src/utils/tx-submission.ts

packages/core-utils/src/common/misc.ts

packages/core-utils/src/fees.ts

... and 26 more

Continue to review full report at Codecov.

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

@Boyuan-Chen pls review

Can we deploy forwarder to forward http to https?

@rupertbg pls take a look!

status update: offline chat with @rupertbg - he'll review the policies and make them as thin as possible as I have less experience with it and a PR update follows


Add Service Deligation for subnets in Core module

Is it possible to add service delegation for subnets in the core module.
Se example here:
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/subnet
 delegation {
    name = "delegation"

    service_delegation {
      name    = "Microsoft.ContainerInstance/containerGroups"
      actions = ["Microsoft.Network/virtualNetworks/subnets/join/action", "Microsoft.Network/virtualNetworks/subnets/prepareNetworkPolicies/action"]
    }
  }
}

@linus-lysell we are already creating a group for service endpoint join. What else is needed other than that?

@simongottschlag Thanks for the quick reply! Service endpoint is working fine. I would need the delegation block as a feature in the core module.


Hide News Feed loading option

Configuration option to hide News Feed module if feed is empty instead of showing LOADING status

Please send your pull requests the develop branch.
Don't forget to add the change to CHANGELOG.md.

Does the pull request solve a related issue?
If so, can you reference the issue?
What does the pull request accomplish? Use a list if needed.
If it includes major visual changes please add screenshots.

Could you please add an updated README (for the module) and updated CHANGELOG to your PR? Thanks!

Done :)

Merged!

Nice :)


Module Federation Universal (Vite, Rollup, Turbopack, Native, esBuild)

Short Description
Being able to combine containers generated by different build systems.
Longer Description
Module Federation is about helping teams to ship code faster, and more reliably and to organize the development effort around multiple, autonomous teams. Module Federation Universal takes it to the next stage by allowing aspects of the application to be brought together and decoupled from their individual build toolsets. There is also an emphasis on using native APIs as well to create a standards-based approach.
Business Value
As companies make acquisitions or teams experiment with different technologies it is important to be able to incorporate the artifacts of those teams into the overall stack as quickly as possible. Through leveraging, Module Federation and its decoupling from build system teams will have more flexibility and lower times to cohesion.
Acceptance Criteria

Decouple MF from Webpack 5
Common interface OR as adapter OR Webpack MF upgrade
A lot of samples and e2e will be required

Moved to the discussion instead of issue #434


Universal behavior copy - consistent

Closes #3978
Behaviors works for component with One variant and Universal behaviors work for component with Multiple variants. (Link)
Changelog
Changed
Updated Behaviors and Universal Behaviors in accordance with documentation guidelines, including both anchor links and headings.
Behvaiors -> Universal behaviors

Buttons
Data table
Modals
Select

Universal behaviors -> Behvaiors

Menu
Tree view

Removed

Removed 'Variants' from anchor links and adjusted headings from H2 to H3.

Heyy @tay1orjones, @andreancardona, @aubrey-oneal, if you have some time, could you please review this PR?
Thank you in advance!


修复在设置object可访问的情况下，出现异常导致后续setAccessible被跳过的问题

setAccessibleEnable是以true作为默认值的，在setAccessible方法出现异常后被设置为false，此操作会导致在程序运行过程中，任意一次的setAccessible出现异常后（可能为AccessException or SecurityException），都将导致后续使用fastjson内所有的setAccessible被跳过，从而导致程序抛出异常（此异常是由于未设置字段/方法的Accessible导致的，并不是在调用setAccessible方法导致的），此代码会隐藏真实的异常类型，从而导致程序侧无法定位问题

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


.net core 3 preview 7 support

Hello,
Now that preview 7 is out, are there any thoughts or timelines around npgsql support for it?

@aford22 Thanks for inquiring, we're always grateful to users who are able and willing to help us to test pre-releases.
Work is currently underway to update the provider for preview 7. The EF Core internals have undergone some major changes since preview 5, so there's a lot of work required on the provider-side.
We don't have a specific timeline yet, but rest assured that @roji is hard at work on the migration and we hope to have a preview release available soon.
Once the preview release is ready, announcements will be made here (via the releases page) and on Twitter by the core team. It'll be a big preview, so hopefully you (and others) will have an opportunity to test it out and report back with any bugs/regressions you encounter.

@aford22 Thanks for inquiring, we're always grateful to users who are able and willing to help us to test pre-releases.
Work is currently underway to update the provider for preview 7. The EF Core internals have undergone some major changes since preview 5, so there's a lot of work required on the provider-side.
We don't have a specific timeline yet, but rest assured that @roji is hard at work on the migration and we hope to have a preview release available soon.
Once the preview release is ready, announcements will be made here (via the releases page) and on Twitter by the core team. It'll be a big preview, so hopefully you (and others) will have an opportunity to test it out and report back with any bugs/regressions you encounter.


Error adding same hostname if it is the last in the previous entry

Let's say I've an entry like:
<IP_ADDRESS> my.dns
If I add an entry like
<IP_ADDRESS> my.dns
the library goes in out-of-bound trying to remove the hostname from the previous entry
This goes well if the 1st entry has more than 1 hostname, like
<IP_ADDRESS> my.dns my.second.dns

The problem should be here
https://github.com/areYouLazy/libhosty/blob/c14e286d51d89dd23b7ca74bbad389cc8bac2fd2/hosty.go#L267
We need to check if it's the last entry before removing it using the append() method


Upgrade node-pre-gyp to version 0.9.0

Closes #950

@springmeye The OS X NODE_VERSION="5" COVERAGE=true PUBLISHABLE=false job failed. This error has already occurred before this pull request.
build/temp.macosx-10.12-intel-2.7/_openssl.c:493:10: fatal error: 'openssl/opensslv.h' file not found
#include <openssl/opensslv.h>
         ^
1 error generated.
error: Setup script exited with error: command 'cc' failed with exit status 1
The command "if [[ ${COVERAGE} == true ]]; then if [[ $(uname -s) == 'Linux' ]]; then PYTHONUSERBASE=$(pwd)/py-local pip install --user cpp-coveralls; else PYTHONUSERBASE=$(pwd)/py-local easy_install --user cpp-coveralls; fi; fi" failed and exited with 1 during .

Yes, that is safe to ignore/unrelated to your PR. Thanks for providing this, merging now.

Awesome fellas :)
Hoping to see a release on NPM soon :)


Permissions issues when cloning a private repo

I have caddy running as a user (deploy) that has an SSH key (/home/deploy/.ssh/id_rsa). However when I run the service via systemd, it fails to read the SSH key, even tho the process is running as deploy.

Warning: Identity file /home/deploy/.ssh/id_rsa not accessible: Permission denied

So I'm not sure if the process of cloning is not run by the user the caddy process is running as...
Aug 16 15:59:40 host caddy[3304]: Cloning into '/var/repos/redacted'...
Aug 16 15:59:40 host caddy[3304]: Warning: Identity file /home/deploy/.ssh/id_rsa not accessible: Permission denied
Aug 16 15:59:40 host caddy[3304]: Could not create directory '/home/deploy/.ssh'.
Aug 16 15:59:40 host caddy[3304]: Host key verification failed.
Aug 16 15:59:40 host caddy[3304]: fatal: Could not read from remote repository.
Aug 16 15:59:40 host caddy[3304]: Please make sure you have the correct access rights
Aug 16 15:59:40 host caddy[3304]: and the repository exists.

Solved this. It was a configuration option in the .service file.
; Hide /home, /root, and /run/user. Nobody will steal your SSH-keys.
; ProtectHome=true

Disabled this so it has access to read the key.


AVRO-2315: Update zstd-jni to version 1.3.8-3

R: @Fokko

@iemejia did you add the label manually, or was this the work of the label-bot?

Not yet, but thanks for reminding me to ping INFRA on this. For more details INFRA-17367


build(package): upgrade devDependencies

What is the motivation for this pull request?
 @commitlint/cli                   17.0.1  →  17.3.0
 @commitlint/config-conventional   17.0.0  →  17.3.0
 @rollup/plugin-node-resolve       15.0.0  →  15.0.1
 @rollup/plugin-typescript         10.0.0  →  10.0.1
 @types/jest                       29.0.0  →  29.2.4
 @typescript-eslint/eslint-plugin  5.27.0  →  5.47.0
 @typescript-eslint/parser         5.27.0  →  5.47.0
 eslint                            8.16.0  →  8.30.0
 eslint-plugin-prettier             4.0.0  →   4.2.1
 husky                              8.0.1  →   8.0.2
 jest                              28.1.0  →  29.3.1
 lint-staged                       13.0.0  →  13.1.0
 prettier                           2.6.2  →   2.8.1
 ts-jest                           28.0.3  →  29.0.3
 typescript                         4.7.2  →   4.9.4

Checklist:

[x] Conventional Commits
[x] Tests
[ ] Documentation

Codecov Report

Merging #18 (72aa54d) into master (0669ced) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #18   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           32        32
  Branches         9         9
=========================================
  Hits            32        32

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Data is unclear if cases are confirmed or unconfirmed

Data is unclear if entries are confirmed or unconfirmed. This should be specified in the README.
It's not clear if  the lines with blank date_confirmed values are not confirmed, or are unknowns. I assume the 2nd.

Only confirmed. Will specify in upcoming publication.


'display  --focus' not working when windows stacked

Hey really appreciate the updates - I have been having an nagging issue I was hoping would be resolved with this release but doesn't seem to be. I use the following config to move my focus between windows and monitors (displays):
 shift + ctrl + alt + cmd - a : yabai -m window --focus west || yabai -m display --focus west
alt + shift - s : yabai -m window --focus south
 shift + ctrl + alt + cmd - d : yabai -m window --focus east || yabai -m display --focus east
 alt + shift - w : yabai -m window --focus north
This works fine when windows are not stacked. When windows are stacked, I am still able to move focus between windows, but when I try to switch focus between monitors I lose focus (ie. no window is in focus and the focus stays on the current monitor/display).
Hopefully this is a fixable issue with my config but I thought I would open here in case anyone is having the same issue.
Thanks!

I have a similar problem. I have an external display connected which is set to be the main display, so it is N.1 display in yabai. It happens that the command yabai -m display --focus only works when I'm focusing display 2, so the display of my MacBook, when I'm focusing display 1 (the external display) it doesn't work.
The same happens when I focus a space on the external display from a space in MacBook's display: it doesn't actually get focused because the menu bar is still darken and no window in the target space is focused.
Yesterday I reinstalled yabai and the problem went away, but now I have it again, don't know why.

Hello, i have the same problem.
I use this skhd macro to toggle between stack and bsp mode:
hyper - z : yabai -m space --layout $(yabai -m query --spaces --space | jq -r 'if .type == "bsp" then "stack" else "bsp" end')

I also have this issue, if the destination display of yabai -m display --focus has a stack, all focus goes away and you have to click on a window.

Hm I am unable to reproduce this using yabai v4.0.0 on macOS 12.3.1 (Apple Silicon).
I have tested using bsp layout with stacked nodes on the destination display, and the window is focused correctly.
I also tested using the stack layout on the destination display, and the window is focused correctly.
The above tests worked using both yabai -m display --focus next and yabai -m display --focus 2.
Is this happening with specific applications? Are you running Hammerspoon or other accessibility software that could interfere in some way?

I just quit Hammerspoon, which I was using only for Stackline, and focus now works correctly. My focus command is yabai -m window --focus west || yabai -m display --focus west.

I think this is a problem with Stackline, the Hammerspoon window "steals" focus for whatever reason. What yabai is doing is simply sending focus to the window that macOS says is the "front-most" window on the destination display.
I'd like to make something like Stackline built-in to yabai itself in the future. There are tons of things that can be improved regarding the stack-system.

It's a shame because the workflow with these commands was getting really good:
ctrl - left : yabai -m window --focus west || \
                  yabai -m display --focus west

ctrl - right: yabai -m window --focus east || \
                   yabai -m display --focus east

ctrl - down : yabai -m window --focus south || \
                     yabai -m window --focus stack.next || \
                     yabai -m window --focus stack.first

ctrl - up : yabai -m window --focus north || \
                yabai -m window --focus stack.prev || \
                yabai -m window --focus stack.last

I believe this is the relevant issue: https://github.com/AdamWagner/stackline/issues/67
A possible workaround that would let you keep Stackline running could be the following:
Instead of yabai -m focus --display west, you could run yabai -m query --spaces --display west and select the one with is-visible true (using jq), then run a yabai -m window --focus <id> command on the first window listed in the windows array.

I got it working, thank you!!
ctrl - left : yabai -m window --focus west || \
              yabai -m window --focus \
              $(yabai -m query --spaces --display west | jq '.[0]' | jq '.["last-window"]')

ctrl - right: yabai -m window --focus east || \
              yabai -m window --focus \
              $(yabai -m query --spaces --display east | jq '.[0]' | jq '.["first-window"]')

I can also stack across displays now:
meh - left  : yabai -m window west --stack $(yabai -m query --windows --window | jq -r '.id') || \
              yabai -m window $(yabai -m query --spaces --display west | jq '.[0]' | jq '.["last-window"]') \
                    --stack $(yabai -m query --windows --window | jq -r '.id')
meh - right : yabai -m window east --stack $(yabai -m query --windows --window | jq -r '.id') || \
              yabai -m window $(yabai -m query --spaces --display east | jq '.[0]' | jq '.["first-window"]') \
                    --stack $(yabai -m query --windows --window | jq -r '.id')
meh - up    : yabai -m window north --stack $(yabai -m query --windows --window | jq -r '.id')
meh - down  : yabai -m window south --stack $(yabai -m query --windows --window | jq -r '.id')

Closing this as there isn't really anything yabai can do about this, use the workaround mentioned above if Stackline is unable to fix the issue on their end.

I don't have stackline and hammerspoon, I had them in the past but now I removed them, however I still have the same issue.

Having the same problem where switching to a desktop doesn't focus any windows. With or without Hammerspoon. I have never used stack line.
Any advice?


Added charsetString variable

It seems to be the only option to generate vCards for Windows (I have done some tests with 7-10 and Outlook) with UTF-8 charset strings by adding ;CHARSET=utf-8 to each line that could contain utf-8 signs. It is not enough to set only the mime header, as it should be according to https://tools.ietf.org/html/rfc6350.
The charsetString variable is empty by default to stay valid with the RFC, but it could be set with setCharsetString to support Windows vCard import implementations.

Hi @Jako , can you test if the latest release is a fix for your problem?

It could fix that maybe (haven't tested it yet). But in my opinion this fix has one big issue: You can only use chars that are in ISO-8859-1 in a vCard that way (http://php.net/manual/en/function.utf8-decode.php). And that charset is very limited: https://en.wikipedia.org/wiki/ISO/IEC_8859-1. A lot of eastern european signs are missing and all 'not latin' charsets are unsupported. It has to be written with UTF-8.

Hi @Jako, thanks for your PR.
I'm sorry I get bet so late to your PR.
Can you please test the latest release with added something to fix utf8 characters?
https://github.com/jeroendesloovere/vcard/commit/af7401396156d15513bbf73e12c5b7a839413ca5

As I said in my last comment, utf8_decode is somehow wrong, since the character set ISO-8859-1 is very limited. You can only handle western latin chars with that.
The output has to be UTF-8 encoded and (because of some import limitations in i.e. Outlook, all vCard fields that could contain UTF-8 signs should be marked with ;CHARSET=utf-8

Thanks @Jako

Hi @Jako, if you can just adjust your PR a little. Then i'll merge it, so everything works in Windows and Android.

Done. I have added a check for $this->charset == 'utf-8' inside, since I am not sure how other charsets have to be handled (if using a different internal charset). This way only a utf-8 charset changes the resulting vcf data.


Update CMakeLists.txt Remove Extra Lines

Extra lines in cmake cache args were getting appended to the definition of build_testing and making that variable result as true - which led to the full tests being built for json

The whitespace thing I get, but were either of these flags needed for anything?

I have tried to find any reference to what they mean - but have been unsuccessful. I think this section is only for arguments defined with -D so they don't have meaning here
If you know of a way to find out what the intent was happy to look -


Installation fails due to ENOENT: no such file or directory

"Error: ENOENT: no such file or directory, rename '/tmp/d-2019112-25-7ebysh.5rhw4/node_modules/seedrandom' -> '/tmp/d-2019112-25-7ebysh.5rhw4/node_modules/shuffle-seed/node_modules/seedrandom'"

Sometimes, when more than one install is running the following exception is thrown from the function-npm node.

Can you please paste "require" list portion of your code? Also what OS, node-red version and node version are you using?

Hi,
First I would like to thank you for this awesome node!
It is a game changer to me!
I have the same problem on Node-RED 1.0.3:
"Error: ENOENT: no such file or directory, rename '/tmp/d-2020324-19-1gdlmu4.6lre/node_modules/moment' -> '/tmp/d-2020324-19-1gdlmu4.6lre/node_modules/moment-timezone/node_modules/moment'"
The required code is the following:
const Influxdb = require('influxdb-v2@0.0.4');
const moment = require('moment@2.24.0');
const tz = require('moment-timezone@0.5.28');

I haven't been spending much time maintaining and developing this module lately. I know there are some fundamental issues in the way it uses the "npm" module in code. I keep telling myself, one day I will find the time to test the new code and publish but that target keeps moving in the future. I would suggest you check out the this fork in the meanwhile. I haven't personally tested the changes but look like that fork has updates that may work better.

The only issue is, we don't have the fork published as of right now and it's therefore not available through the Node-RED palette. I'm happy to contribute the changes back upstream or take over maintenance if it helps :v:

Finally got to publish the new version, should work a lot better for multiple instances. Used the pull request code from @beevelop and added some modifications. That should solve these issues.

Awesome @ntsaini. Thank you very much 🍻


AudioRecord-JNI: Error -4 during AudioRecord native read

sometimes when I stop the record I get this error message " AudioRecord-JNI: Error -4 during AudioRecord native read" I searched it but i found nothing.

Browsing the Android source, it looks like that message is printed in this function:
https://github.com/android/platform_frameworks_base/blob/master/core/jni/android_media_AudioRecord.cpp#L434
It looks like it's a result of reading an invalid amount of data from the audio driver. I believe the particular error code is available through the API here:
http://developer.android.com/reference/android/media/AudioRecord.html#read(short[], int, int)

Mostly this error come when we are not using
recorder.stop();
recorder.release();
Must release the object when recording is stop.


bit_range must be initialized when renaming bitfields

I want to rename some register blocks, and their respective bitfields on a given peripheral. Here is my yaml:
SYSTIMER:
  _modify:
      VALUE_LO:
        name: UNIT0_VALUE_LO
      VALUE_HI:
        name: UNIT0_VALUE_HI
      UPDATE:
        name: UNIT0_OP
        fields:
          TIMER_VALUE_VALID:
            name: TIMER_UNIT0_VALUE_VALID
          TIMER_UPDATE:
            name: TIMER_UNIT0_UPDATE

The registers are correctly renamed, but when I try and rename the bit fields I get the following error:
Error: Processing device `ESP32-S2`

Caused by:
    0: According to `SYSTIMER`
    1: Processing peripheral `SYSTIMER`
    2: Modifying registers matched to `UPDATE`
    3: `Build error: `bit_range` must be initialized

Have I got the syntax wrong, or is this a bug?

Even if I add the bit range fields manually, it still complains.
SYSTIMER:
  _modify:
      VALUE_LO:
        name: UNIT0_VALUE_LO
      VALUE_HI:
        name: UNIT0_VALUE_HI
      UPDATE:
        name: UNIT0_OP
        fields:
          TIMER_VALUE_VALID:
            name: TIMER_UNIT0_VALUE_VALID
            bitOffset: 30
            bifWidth: 1
          TIMER_UPDATE:
            name: TIMER_UNIT0_UPDATE
            bitOffset: 31
            bifWidth: 1

Got a working solution, need to modify the register name first, then use the renamed register to rename the bitfields.

SYSTIMER:
  _modify:
    VALUE_LO:
      name: UNIT0_VALUE_LO
    VALUE_HI:
      name: UNIT0_VALUE_HI
    UPDATE:
      name: UNIT0_OP
  UNIT0_OP:
    _modify:
      TIMER_VALUE_VALID:
        name: TIMER_UNIT0_VALUE_VALID
      TIMER_UPDATE:
        name: TIMER_UNIT0_UPDATE


Cannot debug via launch or attach  with .NET 5 rc2

Issue Description
Cannot debug on freshly installed .NET 5 in linux (debian) and windows 10. I downloaded the binary tarballs and set environment variables PATH and DOTNET_ROOT.
Steps to Reproduce
As per the tutorial
dotnet new webapi -o TodoApi
dotnet run

Browsing to localhost:5000/WeatherForecast works so .NET 5 is installed correctly.
Added to launch.json
      "logging": {
        "engineLogging": true,
        "moduleLoad": true
      },
      "debugServer": 4711

Ran  .\vsdbg-ui.exe --server --consoleLogging per another issue troubleshooting steps. VScode does not connect to that port when I click launch. I tested if port 4711 is open manually with powershell test-connection successfully.
Also tried using attach to process. Attach seems to do something but symbols are not loaded so no breakpoints.
Expected Behavior
Be able to debug.
Actual Behavior
Cannot debug.
Logs
OmniSharp log

Starting OmniSharp server at 10/31/2020, 3:41:48 AM
    Target: d:\projects\TodoApi
OmniSharp server started.
Path: c:\Users\mgutz.vscode\extensions\ms-dotnettools.csharp-1.23.4.omnisharp\1.37.3\OmniSharp.exe
PID: 21248
    Starting OmniSharp on Windows 6.2.9200.0 (x64)

    DotNetPath set to dotnet

    Located 1 MSBuild instance(s)
        1: StandAlone 16.8.0 - "c:\Users\mgutz\.vscode\extensions\ms-dotnettools.csharp-1.23.4\.omnisharp\1.37.3\.msbuild\Current\Bin"

    MSBUILD_EXE_PATH environment variable set to 'c:\Users\mgutz\.vscode\extensions\ms-dotnettools.csharp-1.23.4\.omnisharp\1.37.3\.msbuild\Current\Bin\MSBuild.exe'

    Registered MSBuild instance: StandAlone 16.8.0 - "c:\Users\mgutz\.vscode\extensions\ms-dotnettools.csharp-1.23.4\.omnisharp\1.37.3\.msbuild\Current\Bin"
        CscToolExe = csc.exe
        CscToolPath = c:\Users\mgutz\.vscode\extensions\ms-dotnettools.csharp-1.23.4\.omnisharp\1.37.3\.msbuild\Current\Bin\Roslyn
        MSBuildExtensionsPath = c:\Users\mgutz\.vscode\extensions\ms-dotnettools.csharp-1.23.4\.omnisharp\1.37.3\.msbuild
        MSBuildToolsPath = c:\Users\mgutz\.vscode\extensions\ms-dotnettools.csharp-1.23.4\.omnisharp\1.37.3\.msbuild\Current\Bin

    Detecting Cake files in 'd:\projects\TodoApi'.

    Could not find any Cake files

    No solution files found in 'd:\projects\TodoApi'

    Queue project update for 'd:\projects\TodoApi\TodoApi.csproj'

    Detecting CSX files in 'd:\projects\TodoApi'.

    Could not find any CSX files

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0

    Loading project: d:\projects\TodoApi\TodoApi.csproj

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.Completion.CompletionOptionsProvider, Order: 0

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.BlockStructureWorkspaceOptionsProvider, Order: 140

    Configuration finished.

    Omnisharp server running using Stdio at location 'd:\projects\TodoApi' on host 7984.

    Successfully loaded project file 'd:\projects\TodoApi\TodoApi.csproj'.

    Adding project 'd:\projects\TodoApi\TodoApi.csproj'

    Update project: TodoApi

    Miscellaneous file: d:\projects\TodoApi\obj\Debug\net5.0\TodoApi.MvcApplicationPartsAssemblyInfo.cs added to workspace

    Queue project update for 'd:\projects\TodoApi\TodoApi.csproj'

    Loading project: d:\projects\TodoApi\TodoApi.csproj

    Successfully loaded project file 'd:\projects\TodoApi\TodoApi.csproj'.

    Update project: TodoApi

C# log

D:/projects/TodoApi •NET v5.0.100-rc.2.20479.15 🎯 net5.0 took 8m38s ❯ dotnet run
Building...
warn: Microsoft.AspNetCore.Server.Kestrel[0]
      Unable to bind to http://localhost:5000 on the IPv4 loopback interface: 'An attempt was made to access a socket in a way forbidden by its access permissions.'.
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: https://localhost:5001
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://localhost:5000
info: Microsoft.Hosting.Lifetime[0]
      Application started.  What do you see?

I should have mentioned I tried that first.  Same result. Progress bar infinitely moves but no action. C# log is empty.  There are no entries appended to Omnisharp Log.
To be thorough, here is the generted launch.json stanza with my changes
    {
      "name": ".NET Core Launch (web)",
      "type": "coreclr",
      "request": "launch",
      "preLaunchTask": "build",
      "program": "${workspaceFolder}/bin/Debug/net5.0/TodoApi.dll",
      "args": [],
      "cwd": "${workspaceFolder}",
      "stopAtEntry": false,
      "serverReadyAction": {
        "action": "openExternally",
        "pattern": "\\bNow listening on:\\s+(https?://\\S+)"
      },
      "env": {
        "ASPNETCORE_ENVIRONMENT": "Development",
        "DOTNET_ROOT": "d:\\dotnet"
      },
      "sourceFileMap": {
        "/Views": "${workspaceFolder}/Views"
      },
      "logging": {
        "engineLogging": true
        //"moduleLoad": true
      }
      //"debugServer": 4711
    }

Is the plugin known to work with latest .NET 5 RC?

FYI as soon I posted that, I thought to myself "What about removing preLaunchTask, maybe it's not building". Sure enough it seems to work using the previous build. I need to figure how to create the build task.

The issue is preLaunchTask was failing because of another extension. Pressing Ctrl+Shift+B resulted in status bar showing "Fetching build tasks..." and nothing else. I disabled extensions related to debugger and tasks one by one and found the culprit. In my case it was the cross platform taskfile.dev extension.


Fix cursor setter

As reported in #36, that never got updated when we switched to subclassing from VBox instead of having a custom _repr_html.  Can you please confirm that this work for you @pllim ?
EDIT: Fix #36

p.s. I added a commit to update notebook instructions here. Hope you don't mind.

Thanks!


Incorrect package name

This happened when I added the Aegis authenticator repository.
The correct package name is "com.beemdevelopment.aegis", but the app recognizes the package name as "me.impy.aegis".

@bluefly000 thanks for reporting. I have improved the package detection logic in 0.1.2.
Aegis now appears to be working as expected.

In case you're interested in the details. It was a bug in my defaultBranch detection code. Instead of picking master it was selecting the branch: feature-appbar
This is the file it was being pulled from https://github.com/beemdevelopment/Aegis/blob/feature-appbar/app/build.gradle

I had the same problem with other apps. The app version is 0.1.2.
The package name of the application "Aves" is displayed as "com.android.application". The correct package name is "deckers.thibault.aves".
Also, in the case of AppManager and OctoDroid, the app could not parse the package name and add the repository.
AppManager package name is "io.github.muntashirakon.AppManager" and OctoDroid package name is "com.gh4a".

@bluefly000 thanks for sharing. I have added support for those 3 in version 0.1.3

I guess I was wrong about all packageNames having 3 components. These should have actually been picked up by my fallback parser which scrapes the README.md for f-droid links that contain the package name - there was a bug that has now been fixed.
I have changed the regex to support 2 or more components based on your examples. It uses a non-capturing repeating group and seems to cover the cases I was concerned about

Concerns:

two component packageNames were conflicting with some variable usages
including numbers in the packageName was getting confused with some version strings

The restrictions I've added are that each component must be two characters or more (letters, numbers and - _) and that the first component must only be letters. Hopefully this expands the coverage a bit without too many false positives.

@Chr0matic1 Yes, this is the correct place. Thanks for reporting.
This is fixed in  0.1.4


Create  Return the current time// Return the current time

Why:
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

This seems to have been opened accidentally, I am going to close it now :yellow_heart:
Take a look at our contributing docs to learn how to contribute in this repo. You can open a discussion if you have any questions :sparkles:


Consider Making "run to" Include the Selection Monster

If I select a mon and choose "run to", it appears to stop on the previous mon.  That's not my intuition.  On the one hand, "just run that next mon" seems logical.  On the other, it makes sense to stop after a long-running monster so "just running it" could mean hours of waiting.

Hmm. The inspiration behind 'run to' is that it will lock in all the runes of the monsters above them, so that you can start testing and tweaking the target monster without the runes that will be used by other monsters.
Removing 1 build is faster than waiting for it to finish, so this sounds like a fair enough change.


Allows to pick a focus point for videos

Currently, the field is only displayed for images.
I am using some videos with an object-fit / object-position property for which the Focus field is also very helpful. This PR allows to pick a focus point for videos too.

Thanks a lot @sylvainjule for this pull request. The idea is awesome! I will try to have a look at this as soon as possible and to merge it afterwards.
Best regards.

Oh no @sylvainjule – I totally forgot about your PR. I'm so sorry!!

Merged it, finally. Sorry again for this massive delay.


Feature: Zend Coding Standard 2

This repository has been closed and moved to mezzio/mezzio-twigrenderer; a new issue has been opened at https://github.com/mezzio/mezzio-twigrenderer/issues/2.

This repository has been moved to mezzio/mezzio-twigrenderer. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

Squash all commits in your branch (git rebase -i origin/{branch})
Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
Run the laminas/laminas-migration tool on the code.
Clone mezzio/mezzio-twigrenderer to another directory.
Copy the files from the second bullet point to the clone of mezzio/mezzio-twigrenderer.
In your clone of mezzio/mezzio-twigrenderer, commit the files, push to your fork, and open the new PR.
We will be providing tooling via laminas/laminas-migration soon to help  automate the process.


[feature] community crowdsourcing filter & triggers

changedetection v0.39.18, docker
**Is your feature request related to a problem? no, somewhat. maybe user error / user skills.
Describe the solution you'd like
Describe the use-case and give concrete real-world examples
I'm new to web scraping and learn by following examples. Since the dev is hosting, can you use the hosted data to build a giant sample list of how people are filtering their various detections.  A giant example list would give me more insight; and if its the same site I'm looking at, I might just be able to recycle someone else's filter (+/- some mods)
some pages work fine for me all the time.
some work fine that day, but the next day I get :
(CSS/xPath filter was not present in the page... div' for https://www.... did not appear on the page after 6 attempts, did the page change layout?

not an issue/bug, moved to discussions


Repo watcher - check repo subscription state every single time before…

… queuing images for analysis
Fixes #635
Signed-off-by: Swathi Gangisetty<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>)(, fixes #<issue_number, ...) format, will close the issue when PR is merged: fixes #:
Special notes:

@nightfurys please make this a PR into the 0.8.2-dev branch instead

Closing this PR to open a new one to the 0.8.2-dev branch


egressgw: doc fixes for install-egress-gateway-routes removal

egressgw: document deprecation of install-egress-gateway-routes
Fixes: 334fdbcc62 ("egressgw: mark --install-egress-gateway-routes as
deprecated") Signed-off-by: Lorenz Bauer<EMAIL_ADDRESS>
egressgw: fix helm documentation
Adding a documentation comment to a node in the YAML will force it to appear
in the generated README. This leads to the awkward "{...}" object for the
egressGateway key. Move the documentation to egressGateway.enabled instead.

See https://github.com/norwoodj/helm-docs#valuesyaml-metadata for details on
how documentation is generated.

Signed-off-by: Lorenz Bauer<EMAIL_ADDRESS>

/test

/test


SSLHandshakeException - handshake failed (android 6)

There is an issue in Android 6 (I guess in 5 and less as well) when trying to send https request. In Android 7 it works great.
Exception:
javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0x7f60267c9c80: Failure in SSL library, usually a protocol error error:100c5438:SSL routines:ssl3_read_bytes:TLSV1_ALERT_INTERNAL_ERROR (external/boringssl/src/ssl/s3_pkt.c:972 0x7f6038c9a540:0x00000001)

I was facing this issue and tried almost every solution.
The solution which worked for me is to use this version of library:
compile 'com.loopj.android:android-async-http:1.4.8'
and for Headers[] I used
android {
    useLibrary 'org.apache.http.legacy'
}

@zeero0 It worked for me. Although org.apache.http.Header is deprecated, so the solution works well in Android 6 but for versions above(I tested on Android 9), I also had to add
<uses-library android:name="org.apache.http.legacy" android:required="false" />
in  tag of Manifest file.
See: https://stackoverflow.com/a/50779232

I found a solution, you can use version 1.4.9 but you should define all imports one by one then the problem will solve.
replace
import com.loopj.android.http.*;
with
import cz.msebera.android.httpclient.Header; import com.loopj.android.http.AsyncHttpClient; import com.loopj.android.http.AsyncHttpResponseHandler; import com.loopj.android.http.RequestParams;


Saved dated copies of each summary folder

Whilst it would be nice to be able to store full samples from each region it may be more practical in the short term to instead save the summarised estimates available in each summary folder. This can either be linked to #9 or be a git only implementation based on copying the summary folder (or just the csv's it contains into a dated folder for each region).
If a git based intervention then summarised results could be stored in a covid-rt-estimates-archive repo for example in order to avoid additional history bloat and provide a repo that is easier for others to download (as it won't contain the history of samples and hence will be much smaller even with several hundred archived csv's).

This will be resolved by #9 and #101


Manage IAM instance profiles

Instance profiles are a bit of a hybrid between IAM and EC2,  but if you've moved IAM management out of your cloudformation templates it feels a little weird to leave the instance profiles behind.
This PR adds the ability to manage instance profiles.
The IAM API call that is used to grab users, groups, roles, policies GetAccountAuthorizationDetails doesn't support instance profiles, so there is a bit of copy'pasta code here to use the ListInstanceProfiles API call. Sorry about that.  I suspect that this section might be ripe for  a little refactoring.  My golang is crappy enough that I haven't attempted that.
Demo
$ ../bin/iamy-darwin-amd64 pull -d .
$ cd envato-platform-development-123456789012/iam/instance_profile/
$ ls -1F
EC2ReadOnly.yaml
aws-elasticbeanstalk-ec2-role.yaml
ecsInstanceRole.yaml
test/
$ cat EC2ReadOnly.yaml
Roles:
- EC2ReadOnly
$ cp EC2ReadOnly.yaml test/testpath.yaml   # Add role to an instance profile
$ echo '{}' > EC2ReadOnly.yaml # Remove roles from an instance profile
$ cp test/testpath.yaml test/newtestpath.yaml # Create a new instance profile (with path)
$ rm HumpyIAMDBTestRole.yaml  # Remove an instance profile
$ cd ../../..
$ ../bin/iamy-darwin-amd64 push -d . --dry-run
Commands to push changes to AWS:

      aws iam remove-role-from-instance-profile --instance-profile-name EC2ReadOnly --role-name EC2ReadOnly
      aws create-instance-profile --instance-profile-name newtestpath --path /test/
      aws iam add-role-to-instance-profile --instance-profile-name newtestpath --role-name EC2ReadOnly
      aws iam add-role-to-instance-profile --instance-profile-name testpath --role-name EC2ReadOnly
      aws iam delete-instance-profile --instance-profile-name HumpyIAMDBTestRole
Dry-run mode not running aws commands

This is looking fantastic @andrewjhumphrey, a great addition.
This starts to cut into https://github.com/99designs/iamy/issues/35 also. I'm thinking it might be useful to have some kind of mechanism to specify what data you want iamy to manage. Maybe a dotfile where you can specify entities to skip. Any thoughts @pda @lox ?

Yeah I was worried on initial review that all of a sudden we'd be managing more things with iamy than we expected on an update. Not sure if opt in or opt out is the best model. Maybe opt-out is default for everything available to be maanged at a major release, then on minor releases any new account info is opt-in... then flip it next time we bump major.
Maybe I'm overthinking it, just add this and bump to 3.0.
Also I pulled branch locally to run go fmt, still got one little outstanding whitespace thing.

I don't see that dryRun indent problem in my tree.  Much strange!  As that was a change from previous PR I did though (https://github.com/99designs/iamy/pull/30) so it's entirely likely I've pooched something.

I'm thinking it might be useful to have some kind of mechanism to specify what data you want iamy to manage. Maybe a dotfile where you can specify entities to skip.

Yeah some mechanism to opt out of some types (IAM / S3 / EC2 / etc…) could be good. I can't think of a scenario where I'd use it though; I'm happy to track everything it can find. If it's via a config file, I'd strongly prefer a non-dot-file. I hate it when important files are sometimes invisible / excluded from searches / etc.
Somewhat related to opting out of certain types is the auto-ignore of CloudFormation-managed resources based on a dubious pattern match on the resource name. Perhaps that should be opt-in / opt-out or the filter should be configurable?

Thanks @andrewjhumphrey, also I've made you a contributor with write access as it looks like you're an active user