raidboss: use ActorControlExtra for sidewise spark cleaves

Valarnin recently did some work to improve the Twilight Sabbath triggers
in m4s. He discovered that we can detect the Wicked Replica cleave
directions using the ActorControlExtra log lines with the 0197
'PlayActionTimeline' category.
Do the same in m4n, replacing the check for CombatantMemory trigger.
This should be more precise and less overhead. It is also slightly less
code.
As far as I can tell, all the clones use the same 11D6 and1 11D8 values
for their left or right cleave.
Signed-off-by: Jacob Keller<EMAIL_ADDRESS>

I've tested this on live game, and it works the same so far. I think this is preferable over combatant memory, but I think we still can't get rid of getcombatants entirely.

For context here, PlayActionTimeline runs a full action timeline for a given actor. In this case, the action timeline is the entire "disc falling to reveal the actor" animation, which includes the actor's left/right cleave direction since that's part of the animation.
That's also why there are only two values for param1 - There's no "fast" animation variant.
The actual cast animation (that has the lightning VFX and includes the red "omen" cleave indicators on the floor) is still tied to the ActorCast packet/20| network log line, it's just not available until significantly later.
I just wanted to share the logic/reasoning of why PlayActionTimeline works here and why there are only two possible values for param1, since I didn't really include it in my PR.

I just wanted to share the logic/reasoning of why PlayActionTimeline works here and why there are only two possible values for param1, since I didn't really include it in my PR.

Thanks! Ya, I figured the savage version had a fast and slow animation variant since they need time between coming down and going off for the in between mechanics to hit.

For what its worth in my testing, the timing for the ActorControlExtra log lines and the combatant memory log lines appears to be very similar.

Looks ok to me.  Note that in testing, I regularly see the existing CombatantMemory version fire 1s sooner than this proposed ActorControlExtra version.

Hmmm that's interesting. In my logs it seems to appear at nearly the same time ... My understanding is that combatant memory relies on polling to check for and emit the matched log lines?
The delay probably only matters for the first hit anyway

The timestamp of combatant memory log lines (273 lines) is not reliable because the actual tracked timestamp is always pulled from FFXIV_ACT_Plugin's GetServerTimestamp method, which can be running behind or ahead of the log writing queue that we push to in OverlayPlugin due to async code.
In the normal version of the fight, the network packet that actually changes the WeaponId always arrives with a server timestamp earlier than the PlayActionTimeline packet, but the order of any of the three lines can vary wildly.
Below is a quick grep of the three lines from some of my log files. Sorry about the age of these, I haven't touched the normal version of the fight in forever.
But the tl;dr is:

Don't use CombatantMemory lines if there's another option
Either 273|...|003F|?? or 273|...|0197|???? are perfectly and equally viable in normal mode

273|2024-07-21T19:09:19.0850000-04:00|400178F3|0197|11D8|0|0|0|648df0e69bee093b
273|2024-07-21T19:09:18.9960000-04:00|400178F3|003F|79|0|0|0|81006711b76830dc
261|2024-07-21T19:09:18.7360000-04:00|Change|400178F3|Heading|-1.5709|PosX|110.0000|PosY|100.0000|PosZ|0.0000|WeaponId|121|aa26ef11fc2b6ad6
261|2024-07-21T19:09:20.6540000-04:00|Change|400178F2|Heading|-3.1416|PosX|100.0000|PosY|110.0000|PosZ|0.0000|Radius|4.8388|WeaponId|121|51b4f94f898d9fd6
273|2024-07-21T19:09:21.0010000-04:00|400178F2|003F|79|0|0|0|87d916945cde1bfb
273|2024-07-21T19:09:21.0900000-04:00|400178F2|0197|11D8|0|0|0|b87b56294ff9edd0
273|2024-07-21T19:12:52.4200000-04:00|400178F4|003F|79|0|0|0|b207d53d57fa033d
261|2024-07-21T19:12:52.0510000-04:00|Change|400178F4|Heading|0.0000|PosX|100.0000|PosY|90.0000|PosZ|0.0000|Radius|4.8388|WeaponId|121|aac1b1ed55805f50
273|2024-07-21T19:12:52.4660000-04:00|400178F4|0197|11D8|0|0|0|6b3470181bbbe13d
273|2024-07-21T19:12:54.3810000-04:00|400178F3|003F|79|0|0|0|f30d8285cab20ac0
261|2024-07-21T19:12:53.9770000-04:00|Change|400178F3|WeaponId|121|ccc05ed1ac018573
273|2024-07-21T19:12:54.4690000-04:00|400178F3|0197|11D8|0|0|0|1cda3499967b75f7
273|2024-07-21T19:12:56.3850000-04:00|400178F2|003F|79|0|0|0|c35c5760cdb9719d
261|2024-07-21T19:12:56.0260000-04:00|Change|400178F2|WeaponId|121|3eb011666f7f058c
273|2024-07-21T19:12:56.4730000-04:00|400178F2|0197|11D8|0|0|0|d5b04bb12973caef
273|2024-07-21T19:12:58.3890000-04:00|400178F1|003F|79|0|0|0|b432d9a8f7584c43
261|2024-07-21T19:12:57.9800000-04:00|Change|400178F1|WeaponId|121|c762ade762182afe
273|2024-07-21T19:12:58.4770000-04:00|400178F1|0197|11D8|0|0|0|07f238da38dd8411
273|2024-07-23T14:13:52.2230000-04:00|40016DC1|003F|79|0|0|0|f3dd637e9f85429f
261|2024-07-23T14:13:51.9920000-04:00|Change|40016DC1|Heading|-1.5709|PosX|110.0000|PosZ|0.0000|Radius|4.8388|WeaponId|121|6c4129b97924629c
261|2024-07-23T14:13:51.9920000-04:00|Change|40016DC1|Heading|-1.5709|PosX|110.0000|PosZ|0.0000|Radius|4.8388|WeaponId|121|c6c1386365a9269e
273|2024-07-23T14:13:52.2670000-04:00|40016DC1|0197|11D8|0|0|0|aaf2cc32bdf9c561
261|2024-07-23T14:16:56.0570000-04:00|Change|40016DC1|Heading|0.0000|PosX|100.0000|PosY|90.0000|PosZ|0.0000|WeaponId|121|e9fb5b785f09c444
273|2024-07-23T14:16:56.3950000-04:00|40016DC1|003F|79|0|0|0|b00f9f09fae4e776
273|2024-07-23T14:16:56.4400000-04:00|40016DC1|0197|11D8|0|0|0|3e85437d5f0b3f4a
261|2024-07-23T14:16:58.0220000-04:00|Change|40016DC0|Heading|-1.5709|PosX|110.0000|PosY|100.0000|PosZ|0.0000|WeaponId|121|f3dd073fe79c9d7c
273|2024-07-23T14:16:58.3560000-04:00|40016DC0|003F|79|0|0|0|95eec8d5efc83d0f
273|2024-07-23T14:16:58.4450000-04:00|40016DC0|0197|11D8|0|0|0|be7b7231c4a58f03
261|2024-07-23T16:15:36.1650000-04:00|Change|40015210|Heading|0.0000|PosX|100.0000|PosY|90.0000|PosZ|0.0000|WeaponId|121|c504278942a69b53
273|2024-07-23T16:15:36.5210000-04:00|40015210|0197|11D8|0|0|0|2cc0c827413cdb15
273|2024-07-23T16:15:36.4760000-04:00|40015210|003F|79|0|0|0|8c86a392b43d159f
273|2024-07-23T16:15:40.4390000-04:00|4001520E|003F|79|0|0|0|861efc874626c8ce
273|2024-07-23T16:15:40.5290000-04:00|4001520E|0197|11D8|0|0|0|77e0d5ef8a9e47fa
261|2024-07-23T16:15:40.2100000-04:00|Change|4001520E|Heading|-3.1416|PosX|100.0000|PosY|110.0000|PosZ|0.0000|Radius|4.8388|WeaponId|121|3c29b84d348a9356
273|2024-07-23T16:15:42.4470000-04:00|4001520D|003F|79|0|0|0|d25110eda2cc523a
261|2024-07-23T16:15:42.0840000-04:00|Change|4001520D|Heading|1.5708|PosX|90.0000|PosY|100.0000|PosZ|0.0000|Radius|4.8388|WeaponId|121|0892dcfc1bd67e91
273|2024-07-23T16:15:42.5360000-04:00|4001520D|0197|11D8|0|0|0|a77537ea11ee2792
261|2024-07-23T17:43:53.1980000-04:00|Change|4001B433|Heading|1.5708|PosX|90.0000|PosY|100.0000|PosZ|0.0000|WeaponId|121|5f9883a266448aa7
273|2024-07-23T17:43:53.5420000-04:00|4001B433|0197|11D8|0|0|0|3c21195ac75189cc
273|2024-07-23T17:43:53.4970000-04:00|4001B433|003F|79|0|0|0|5c7b559fdbdfd3f6
273|2024-07-23T17:46:46.5930000-04:00|4001B434|003F|79|0|0|0|01535777605e8ed1
273|2024-07-23T17:46:46.6370000-04:00|4001B434|0197|11D8|0|0|0|fa6be925662cf831
261|2024-07-23T17:46:46.1850000-04:00|Change|4001B434|Heading|0.0000|PosX|100.0000|PosY|90.0000|PosZ|0.0000|WeaponId|121|ade255d82c6aa1d6
261|2024-07-23T17:46:46.1850000-04:00|Change|4001B434|Heading|0.0000|PosX|100.0000|PosY|90.0000|PosZ|0.0000|WeaponId|121|660fa2c4cd733021
261|2024-07-23T17:50:21.5570000-04:00|Change|4001B434|Heading|0.0000|PosX|100.0000|PosY|90.0000|PosZ|0.0000|Radius|4.8388|WeaponId|121|2c1326506b66965e
273|2024-07-23T17:50:21.9730000-04:00|4001B434|0197|11D8|0|0|0|34077c8ff68dcdcd
273|2024-07-23T17:50:21.9290000-04:00|4001B434|003F|79|0|0|0|9cdeafaae47fd7b0
273|2024-07-23T22:40:38.8810000-04:00|400069BE|003F|79|0|0|0|ca7e7a959e2d5e85
261|2024-07-23T22:40:38.4310000-04:00|Change|400069BE|Heading|-1.5709|PosX|110.0000|PosZ|0.0000|Radius|4.8388|WeaponId|121|51cc34ea0208a9ca
273|2024-07-23T22:40:38.9250000-04:00|400069BE|0197|11D8|0|0|0|b0ff11f42231667a
261|2024-07-23T22:40:49.7310000-04:00|Change|400069BD|Heading|1.5708|PosX|90.0000|PosY|100.0000|PosZ|0.0000|Radius|4.8388|WeaponId|121|7e40b19b89c17471
273|2024-07-23T22:40:50.0700000-04:00|400069BD|003F|79|0|0|0|68bf6b5537a42e79
273|2024-07-23T22:40:50.1140000-04:00|400069BD|0197|11D8|0|0|0|7938e49703a2dc45
273|2024-07-23T22:43:49.1130000-04:00|400069BB|003F|79|0|0|0|6e14ab7062e55ec5
261|2024-07-23T22:43:48.6940000-04:00|Change|400069BB|Heading|1.5708|PosX|90.0000|PosY|100.0000|PosZ|0.0000|Radius|4.8388|WeaponId|121|81af5fd554b052f6
273|2024-07-23T22:43:49.2030000-04:00|400069BB|0197|11D8|0|0|0|7e7f1493be89d9df
273|2024-07-26T14:54:40.9490000-04:00|40009365|003F|79|0|0|0|813dcc2a668a2c75
273|2024-07-26T14:54:40.9930000-04:00|40009365|0197|11D8|0|0|0|8f3e5a1d2628026c
261|2024-07-26T14:54:40.5450000-04:00|Change|40009365|Heading|0.0000|PosX|100.0000|PosY|90.0000|PosZ|0.0000|WeaponId|121|bc2222ba2f323fda
261|2024-07-26T14:54:44.5620000-04:00|Change|40009363|Heading|-3.1416|PosX|100.0000|PosY|110.0000|PosZ|0.0000|Radius|4.8388|WeaponId|121|a50b0ded14368cc6
273|2024-07-26T14:54:44.9130000-04:00|40009363|003F|79|0|0|0|47fba4f71ceb6db2
273|2024-07-26T14:54:45.0020000-04:00|40009363|0197|11D8|0|0|0|f0de95127e3bb199


Consider adding to firebaseopensource.com

This is a great project and it surely would be helpful for Firebase Developers. Consider adding it to firebaseopensource.com :)

Thanks!
Just submitted fireorm.


⚠ Bofrost.fr has degraded performance

In 8f3c151, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1556 ms

Resolved: Bofrost.fr performance has improved in 2e62150.


This doesn't work with GDB 8

Hello,
This doesn't seem to work GDB 8, I get a "no debugger detected"

+1, gdb hung though


[QNN][TFLite] TFLite rounding mode support

Almost work is done by @Fwd-IV Thanks! I just port it from https://github.com/apache/tvm/pull/4828.
Some other import changes should be noticed is in the rewrite_simplify.cc / canonical_simplify.cc. We introduce expression complexity to determine whether we should do these optimizations. After introducing tflite rounding, we will have complex expressions, like this:

If we don't disable this , we even can not compile whole mobilenet v2 quantized model successfully.
This is also initial support for TFLite bit extract comparison . After this work, our qnn mobilenetv1/v2/inception and so on models we could get bit extract compared with tflite.  I also think we have more work to do for more models.
Co-author-by: @Fwd-IV
@anijain2305 @mbrookhart  @giuseros

Thanks @FrozenGene can you move the analysis change to a separate PR so we can review that part carefully

Thanks @FrozenGene can you move the analysis change to a separate PR so we can review that part carefully

have separated it and resolve your comment

@FrozenGene Any chance you can rebase and fix CI?
Thanks!

This PR appears to be out of date, please feel free to reopen it if this is not the case.
As part of the new year we are attempting to triage the project's open pull requests to ensure that code which
is ready for review and/or merging receives adequate attention.
Thanks again for your contribution, and feel free to reach out to discuss these changes.


java capability not detected properly with Amazon Corretto & Java 10 & 11

If on-premises, which release? 2015.0, 2017.1, 2019 RC2, etc.
2018 Update 3
What's not working?
The TFS agent didn't pickup a java installation of
https://aws.amazon.com/corretto/
src\Misc\layoutbin\powershell\Add-JavaCapabilities.ps1
lookes only for:
Define the JRE/JDK key names.
$jre6KeyName = "Software\JavaSoft\Java Runtime Environment\1.6"
$jre7KeyName = "Software\JavaSoft\Java Runtime Environment\1.7"
$jre8KeyName = "Software\JavaSoft\Java Runtime Environment\1.8"
$jdk6KeyName = "Software\JavaSoft\Java Development Kit\1.6"
$jdk7KeyName = "Software\JavaSoft\Java Development Kit\1.7"
$jdk8KeyName = "Software\JavaSoft\Java Development Kit\1.8"
But Corretto adds the build number to the registry path
\SOFTWARE\JavaSoft\Java Development Kit\<IP_ADDRESS>
Java 10 & 11 are not detected at all (even the Oracle version)

As with #2046 I can advise you to set java environment variable to point to coretto installation manually (or in script).


Justfile for running test matrix locally?

@ValuedMammal We've had a lot of back and forth on this PR: #103, mostly because I only ran cargo test and missed tests in the matrix, was wondering if you what you think about adding a justfile so anyone contributing could run the tests locally before doing a PR. If you want I can make the PR, it would look mostly like this.

# Default recipe shows available commands
default:
    @just --list

# Set default values
rust_version := "stable"
feature := "default"

# Build with specific Rust version and feature
build VERSION=rust_version FEAT=feature:
    @echo "Building with Rust {{VERSION}} and feature {{FEAT}}"
    cargo build --features {{FEAT}} --no-default-features

# Test with specific Rust version and feature
test VERSION=rust_version FEAT=feature:
    @echo "Testing with Rust {{VERSION}} and feature {{FEAT}}"
    cargo test --features {{FEAT}} --no-default-features -- --test-threads=1

# Switch Rust version
switch-rust VERSION:
    rustup default {{VERSION}}
    rustup set profile minimal
    rustup update

# Pin dependencies for MSRV 1.63.0
pin-msrv:
    cargo update -p zstd-sys --precise "2.0.8+zstd.1.5.5"
    cargo update -p time --precise "0.3.20"
    cargo update -p home --precise 0.5.5
    cargo update -p url --precise "2.5.0"
    cargo update -p tokio --precise "1.38.1"
    cargo update -p tokio-util --precise "0.7.11"

# Run full test matrix
test-matrix:
    just test-stable
    just test-msrv

# Test all features on stable Rust
test-stable:
    #!/usr/bin/env bash
    features=(
        "default"
        "blocking"
        "blocking-https"
        "blocking-https-rustls"
        "blocking-https-native"
        "blocking-https-bundled"
        "async"
        "async-https"
        "async-https-native"
        "async-https-rustls"
        "async-https-rustls-manual-roots"
    )

    just switch-rust stable
    for feature in "${features[@]}"; do
        just test stable "$feature"
    done

# Test all features on MSRV (1.63.0)
test-msrv:
    #!/usr/bin/env bash
    features=(
        "default"
        "blocking"
        "blocking-https"
        "blocking-https-rustls"
        "blocking-https-native"
        "blocking-https-bundled"
        "async"
        "async-https"
        "async-https-native"
        "async-https-rustls"
        "async-https-rustls-manual-roots"
    )

    just switch-rust 1.63.0
    just pin-msrv
    for feature in "${features[@]}"; do
        just test 1.63.0 "$feature"
    done

# Clean build artifacts
clean:
    cargo clean

I agree this would be useful, I would add checks for things like rustfmt and clippy. I'm sort of indifferent to the idea of committing it to the repo because of course we'd have to maintain it. @oleonardolima what do you think?

I have mixed feelings about it, it looks fine to add but would be yet another thing to maintain and keep it in pair with CI and MSRV deps pinning.
Also, because same behavior can be achieved by either (1) activating and running the CI on your own forked repository (it's what I usually do), or (2) execute the CI locally using some tool, (e.g act).


Apply to DAB Images

Thank you for developing a great pipeline. Can it be applied to brightfield DAB-stained images?

Hello! Thank you for using the pipeline :) As long as the microglia signal is obviously distinguishable from background in the images, it should work!


Replay sequence

Hi,
I have a menuItem for 'help' that starts a sequence with "playInSequence", but i dont know how to replay the sequence, because its beign fired only one time. I need to rebuild the sequence to achieve this?

I have the same issue. I'd like to be able to replay the sequence on demand, but it seems to play only once and refuse to play again. I even rebuild the individual TourGuide objects and rebuild the sequence and I have no luck.


catch more domains

ran across s.adsrvs.com and t.adsrvs.com to include in regex

Hi,
Sorry for the delay. I have implemented this change in: https://github.com/mmotti/pihole-regex/commit/13d6d77c9148ed477e65940ff7c604f9f72120cb
Instead, it follows the existing regexp of ^(.+[-_.])??, but it achieves the same thing.
Thanks.

No problem on the delay, but your change still doesn't catch the domains in question. You'll need to pull that S out so it doesn't need to follow "er?" or "ice". Specifically, the current regex will not catch something.adsrvs.com. Something like this should work though :
^(.+[-_.])??adse?rv(er?|ice)?s?[0-9]*[-.]

@ail1020 Good point - My bad. Fixed in the most recent commit (https://github.com/mmotti/pihole-regex/commit/25dc08e07692e1b4c06b21624c2e3cb91fdcf063)
Thanks!


added handling for X11 Forwarding

This changes enables X11 Forwarding.
The routines ForwardToRemoteX11 and ForwardToRemote could possibly be merged to on, but i couldn't not test again forwarding, therefore i did not touch it.

Thank you for the contribution @bepeit01 ! Are we the upstream now? :joy:

Yeah about that, I'm not really sure that moul is that active / motivated by the project anymore, there is definitely interest around the project however in the other forks, I know that https://github.com/systemmonkey42/sshportal, and https://github.com/alterway/sshportal are really active and are cherry-picking some of our improvements too, which is great.
Quick note, we're merging our own improvements (which are not always bug fixes, more like modifications) into this fork, and while we're trying to keep them generic, some of them might not suit your needs.

Same here... We have a different fork at work where we add our improvements/adaptions as we need it. And i use my fork to add the generic once back to the community,
Actually we have chosen your fork as basis for out internal one because you were one of the most active once and a lot of bugs were already fixed.


Fix reading time for no words

What
For some pages that do not have a word count, such as the Home page, we
are seeing a 500 error. This fix will trigger the component to not
render (as it does for no word count value).
Why
Bug
Screenshots
If applicable add screenshots otherwise remove this section.
Before
https://content-data-admin.staging.publishing.service.gov.uk/metrics?date_range=past-30-days

After

Review Checklist

[ ] Changes in scope.
[ ] Added/updated unit tests.
[ ] Added/updated feature tests.
[ ] Added/updated relevant documentation.
[ ] Added to Trello card.

 FIX reading_time error for some pages


add screenshots to "tours" entries

Screenshots were added to the 4 topics that have tours:

file explorer
projects list
chatgpt
linux terminal

And the tours article was revised to link to these tour topics.
https://doc.cocalc.com/tours.html


Bug in conductor contract editing

Sep 29 06:25:38 pittsburgh-purchasing app/web.1:    File "/app/purchasing/conductor/manager/views.py", line 430, in edit_company_contacts
Sep 29 06:25:38 pittsburgh-purchasing app/web.1:      contract.parent.is_archived = True
Sep 29 06:25:38 pittsburgh-purchasing app/web.1:  AttributeError: 'NoneType' object has no attribute 'is_archived'
Sep 29 06:25:38 pittsburgh-purchasing heroku/router:  at=info method=POST path="/conductor/contract/2629/edit/contacts" host=www.buildpgh.com request_id=556d61ff-7dfe-4911-8087-3c64ddc21065 fwd="<IP_ADDRESS>" dyno=web.1 connect=1ms service=817ms status=500 bytes=11467

Likely due to contract with no parent object.


Kinesis Elasticsearch Sink: allow clustername to be specified in config

Otherwise it defaults to elasticsearch, which we believe can cause problems...

This is already done, closing


[MS connector] .xlsx extraction

Different from #5745 since here we need to be able to table-query them

Sitrep
@tdraier already pushed .xslx extraction in #6042
Remaining todo for new assignee:

integrate .xlsx extraction to fullsync
add csv extraction (which should resemble xlsx extraction closely)

Can handle the CSV extraction (did it for Google Drive)

CSV implemented ni #6237
.xslx in #6242


Install fails with git failure

I tried to use the Pod with CocoaPods 1.5, but get this error – you can reproduce it via pod try AmazonFling:
pod try AmazonFling
Updating spec repositories

Trying AmazonFling
[!] /usr/local/bin/git clone https://github.com/crelies/AmazonFling.git /private/var/folders/bn/ykv2908d0cn6dv25mr6jym1r0000gn/T/CocoaPods/Try/AmazonFling --template= --single-branch --depth 1 --branch 1.3.4

Cloning into '/private/var/folders/bn/ykv2908d0cn6dv25mr6jym1r0000gn/T/CocoaPods/Try/AmazonFling'...
Note: checking out '24f403c9815ef19da4c4eb0dba9807c424fce064'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

git-lfs filter-process: git-lfs: command not found
fatal: The remote end hung up unexpectedly
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry the checkout with 'git checkout -f HEAD'

@rpitting You need to install git lfs because the Amazon Fling binary is too large for a normal git repository. Do this via homebrew using brew install git-lfs. For more information visit Git LFS.


Vidstack Player Doesn't Work in Electron

Current Behavior:
Vidstack Player doesn't work in Electron
Expected Behavior:
Vidstack Player should work in Electron
Steps To Reproduce:

Install Electron
'yarn add @vidstack/react vidstack'
I get this error:

ERROR in ./node_modules/maverick.js/dist/server/react.js 6:0-56
Module not found: Error: Can't resolve 'react-dom/server' in '/Users/joelp/ElectronTest/node_modules/maverick.js/dist/server'
Did you mean 'server.browser.js'?
BREAKING CHANGE: The request 'react-dom/server' failed to resolve only because it was resolved as fully specified
(probably because the origin is a '*.mjs' file or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
<EMAIL_ADDRESS>1:0-76 7:36-58 8:36-58 9:43-65 10:48-70 11:43-65 12:46-68 13:40-62 14:39-61 15:40-62 16:40-62 17:42-64 18:38-60 19:37-59 20:43-65 21:45-67 22:44-66 23:48-70 24:47-69 25:47-69 26:40-62 27:39-61 28:34-56 29:52-74 30:51-73 31:47-69 32:46-68 33:40-62 34:35-57 35:36-58 36:45-67 37:41-63 38:41-63 39:36-58 40:40-62 41:42-64 42:39-61 43:34-56 44:37-59 47:56-71 63:60-75 80:18-33 130:18-33 140:17-32
 @ dll renderer renderer[13]

webpack 5.5.1 compiled with 1 error and 6 warnings in 29148 ms
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Environment:

Framework: React
Meta Framework: Electron
Node: v16.15.1
Device: Mac Pro
OS: macOS@13

Just reporting again as I tried updating node and other components and it is still not working.

You can try again when I officially release 1.0 and we go from there and see what's wrong (if the issue persits).

From recent reports this is working now in 1.0@next, let me know if the issue persists and we can reopen.


[Navigation Material]

Description
Error: java.lang.IllegalStateException: The offset was read before being initialized. Did you access the offset in a phase before layout, like effects or composition? updating to androidx.compose.material:material:1.6.0-alpha03 (in androidx.compose.material:material:1.5.0-beta01 works fine)
Steps to reproduce
Update to androidx.compose.material:material:1.6.0-alpha03. I have not found any reference to my code, so I don't know which element caused the issue. So I've attached the full stacktrace in text file.
stacktrace.txt

This is probably related to this upstream issue: https://issuetracker.google.com/issues/295536718

Crashes in Material components should be reported in the issue tracker.

I've updated to androidx.compose.foundation:foundation:1.6.0-alpha08 and the issue is not reproducing. Most likely it was fixed in one the latest versions.


Added custom functions and wrappers to support our playwright scenari…

…o scripts.

See https://github.com/LendingHome/xk6-playwright/pull/2


[Bug] Icon to change to Monster Block no longer showing up

I've noticed a strange bug where I am unable to change monsters to their Monster Block counterpart. The gear icon isn't showing up, nor is the module showing in the settings, however, is shown to be installed in the setup. I've attempted disabling all my modules to see if there was a conflict, but that also didn't work.
Love your work! It makes running monsters so much easier.

What version of dnd5e do you have installed?

That was the issue. I was running 1.2.0, not the latest 1.2.4. That also fixed my issue where the BetterRolls for 5E had also disappeared. Thanks for that! I'll make sure to update both the modules and the game system next time.


Removing a directory will remove the previously selected configuration

CurrentDirectory is broken.

:tada: This issue has been resolved in version 2.26.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


allow webaudio WG to generate CR from bikeshed

Status boilerplate for CR, copied from csswg CR boilerplate with WG name, feedback, and patent links updated from webaudio WD boilerplate.

Filename is .include.txt, it needs to be just .include


Fixed #27370 -- Fixed select HTML validator issue

Fixed issue where we caused HTML to be invalid by specifying required
on select field with nonempty first value.
https://github.com/validator/validator/issues/47

@alexpirine @charettes Thank you for a review! 🎉  I changed the code according to your suggestions.

Buildbot, add to whitelist.

@alexpirine @charettes Is there anything I can do to help get this PR merged?

@charettes Thank you! 🎉

@timgraham Thank you for suggestions. I tweaked and added comments.
Yes its just a HTML validation error, so I don't think backport is necessary.
Only reason I'm using hasattr(self, 'renderer') is that we need to do these checks only with HTML element select and not input type="radio", so it shouldn't be complicated change.

I cherry-picked this over to the template-based widget rendering branch (https://github.com/django/django/pull/6498) and updated it for the changes there. Feel free to take a look and review my edits. Thanks!

@timgraham Everything seems to work fine. Thank you for your help!


refactor(commands): use env_var_name for secrets

The Reusable Config Reference Guide from Circle CI recommends to
use env_var_name for secrets, this will also allow users to use their
own environment variables.
Reference Link: https://circleci.com/docs/2.0/reusing-config/#environment-variable-name
Signed-off-by: Salim Afiune Maya<EMAIL_ADDRESS>

@afiune Would the job for this orb require the same parameters?

@KyleTryon Thanks for the quick review! 💯
The idea behind the job is that it uses the default environment variables, if a user wants
to modify that behavior, they can use the command. Am I thinking correctly here? or you
recommend adding the same parameters to the job? If so, why would you do a job and not
just the command? 🤔


Dynamics plan do not exist anymore, please update

[Enter feedback here]
Hello,
The licensing referenced in this page is not current anymore (1000 users with a Dynamics plan). Please update with base/attach terminology.
Thank you,

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

ID: e9c43b88-32f5-49ab-d715-bfcf75c9ba3e
Version Independent ID: 70179da7-e3b6-8775-97cc-361990404677
Content: Manage the encryption key - Power Platform
Content Source: power-platform/admin/manage-encryption-key.md
Service: power-platform
GitHub Login: @Mattp123
Microsoft Alias: matp

@RaphaelTagliani
Taking this to internal thread.


cmd/compile:  if -G=3 fully enabled in compiler,  go test cmd/go -test.run TestScript/mod_edit_go fails

For current master, if you enable -G=3 in the compiler by adding 'Flag.G = 3' at the end of ParseFlags in cmd/compile/internal/base/flag.go, then this command fails
go test cmd/go -test.run TestScript/mod_edit_go

with error:
--- FAIL: TestScript (0.01s)
    --- FAIL: TestScript/mod_edit_go (0.03s)
        script_test.go:254:
            # Test support for go mod -edit to set language version. (0.017s)
            > env GO111MODULE=on
            > ! go build
            [stderr]
            # m
            ./alias.go:2:6: type aliases requires go1.9 or later
            [exit status 2]
            > stderr 'type aliases only supported as of'
            FAIL: testdata/script/mod_edit_go.txt:5: no match for `(?m)type aliases only supported as of` found in stderr

So, as we can see, the types2 typechecker is printing 'type aliases requires go1.9 or later', whereas our current noder.go prints  'type aliases only supported as of -lang=go1.9'.
We should probably reconcile these two so that the same test works for both, and we can get through the gotests with -G=3 fully enabled (i.e. using the types2 typechecker) without failing.

@griesemer


The next step of RCA service -- the "Analysis" story

At this moment the RCA service(POC version) is able to localize the root cause service/pod. the next step to complete the story is to analysis the potential root cause.

thru something like active monitor, searching for pod-failures, any changes of manifests?
changes of service level golden signal metrics
optional -- if there're any meaningful logs.

this will be rollover to sprint 6

rollever to sprint7


Update Links “tiktok-44”

Automatically generated by Netlify CMS

👷 Deploy Preview for distracted-hoover-7b89cc processing.
🔨 Explore the source changes: f4c0eda4103434b0f2402e23ccc81aba9357fbe8
🔍 Inspect the deploy log: https://app.netlify.com/sites/distracted-hoover-7b89cc/deploys/61536fe7ed919f000836c381


Wanakana Support for くぃ, くぇ, くぉ

Issue Type
Wanakana Bug
Description
I was testing Wanakana's support for typing shortcuts for a new project I am working on and discovered that the shortcuts for くぃ, くぇ, and くぉ are not currently supported in Wanakana. These shortcuts are supported by other standard IME solutions, so I think they should be implemented into Wanakana.
These shortcuts save a keystroke, since they prevent the need to type out kuxi or kuli for くぃ for example. The kwi combination should also be able to produce くぃ.
Acceptable Typing Options:
くぃ - kwi, kuxi, kuli
くぇ - kwe, kuxe, kule
くぉ - kwo, kuxo, kulo
Steps to reproduce
Attempt to type the shortcuts for くぃ (kwi), くぇ (kwe), くぉ (kwo) and Wanakana will not succeed in producing the correct kana, regardless of mode.

Browser: QtWebEngine

OS/Device: Windows

Keyboard/Input Method: toHiragana / toKatakana

Thanks for the message, we'll consider adding these by default.
In the meantime, you should be able to use the custom mapping option for your desired result.
http://wanakana.com/docs/global.html#defaultOptions
toHiragana({
  customKanaMapping: {
    kwi: 'くぃ', kuxi: 'くぃ', kuli: 'くぃ',
    kwe: 'くぇ', kuxe: 'くぇ', kule: 'くぇ',
    kwo: 'くぉ', kuxo: 'くぉ', kulo: 'くぉ'
  }
})

@DJTB Thank you for considering adding those into the default conversions and for pointing out a blind spot I had in the docs that allows me to overcome the issue I was having. I will stick with the custom mapping until they are merged into the default conversions.


v0.8.9_26: OK is missing on pop up of Y-axis

SEVERITY: Major
MODULE: Bubble Chart
Platform:

Windows 7 / Chrome 46.0
Windows 7 / Firefox 43.0
iPad Air 2 iOS(9.1) / Chrome 43.0

RELEASE: v0.8.9
STEPS TO REPRODUCE:

Navigate URL: http://static.gapminderdev.org/vizabi/release/v0.8.9/preview/popbyage.html
Bubble chart page will be loaded
Click X axis or Y-axis description. A pop up screen is displayed
Note that OK is missing on that pop up screen

ACTUAL RESULTS:
OK is missing on pop up of Y-axis and X-axis
EXPECTED RESULTS:
OK should be there on pop up of Y-axis
SCREENSHOT:

we were not supposed to have it either. but perhaps we need to make this popup look like a combobox list more than like a dialog


Unable to use AWS IAM role for S3 backend storage

Expected behavior and actual behavior:
The registry pod via a Kubernetes ServiceAccount and IAM policy should be able to access an S3 bucket as backend storage.
Steps to reproduce the problem:
# Harbor
apiVersion: goharbor.io/v1beta1
kind: HarborCluster
metadata:
  name: harborcluster
  namespace: my-ns
spec:
  version: 2.3.0
  imageSource:
    repository: ghcr.io/goharbor
  registry:
    serviceAccountName: harbor-sa
storage:
    kind: S3
    spec:
      # Configure S3 as the backend storage of Harbor.
      # An implementation of the storagedriver.StorageDriver interface which uses Amazon S3 or S3 compatible services for object storage.
      # See: https://docs.docker.com/registry/storage-drivers/s3/
      s3:
        region: eu-west-1 # Required
        bucket: my-s3-bucket # Required

ServiceAccount snippet:
apiVersion: v1
automountServiceAccountToken: true
kind: ServiceAccount
metadata:
  annotations:
    eks.amazonaws.com/role-arn: arn:aws:iam::1111111111111:role/harbor

IAM Policy
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "S3",
            "Effect": "Allow",
            "Action": [
                "s3:PutObject",
                "s3:ListMultipartUploadParts",
                "s3:ListBucketMultipartUploads",
                "s3:ListBucket",
                "s3:GetObject",
                "s3:GetBucketLocation",
                "s3:DeleteObject",
                "s3:AbortMultipartUpload"
            ],
            "Resource": [
                "arn:aws:s3:::my-bucket/*",
                "arn:aws:s3:::my-bucket"
            ]
        }
    ]
}

Versions:
Please specify the versions of following systems.

harbor operator version: 1.1.1
harbor version: 2.3.0
kubernetes version: AWS EKS 1.19

Additional context:
registry operator errors when trying to create the deployment:
Reconciler error    {"reconciler group": "goharbor.io", "reconciler kind": "Registry", "name": "harborcluster-harbor-harbor", "namespace": " │
│ harbor-operator-ns", "error": "cannot set status to error: cannot set conditions to error: apply apps/v1, Kind=Deployment (harbor-operator-ns/harborcluster-harbor-harbor-registry): apply: Deployment.apps \"harborcluster-harbor- │
│ harbor-registry\" is invalid: spec.template.spec.containers[0].env[3].valueFrom.secretKeyRef.name: Invalid value: \"\": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end │
│  with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*'): apply apps/v1, Kind=Deployment (harbor-operator-ns/harborcluster-harbor-harb │
│ or-registry): apply: Deployment.apps \"harborcluster-harbor-harbor-registry\" is invalid: spec.template.spec.containers[0].env[3].valueFrom.secretKeyRef.name: Invalid value: \"\": a DNS-1123 subdomain must consist of lower case │

If I create a secret (key=secret) modify the harbor-cluster config to include the secretkeyref for that secret the registry pod starts but still fails to access the S3 bucket as it appears it's not using the IAM policy via SA.
s3:
      secretkeyRef: test-123
      region: eu-west-1 # Required
      bucket: my-bucket # Required

Refering to the implementation of the S3  https://docs.docker.com/registry/storage-drivers/s3/ then it should only be included if you are using the AWS secret credentials rather then role/policy.

secretkey
no
Your AWS Secret Key. If you use IAM roles, omit to fetch temporary credentials from IAM.

In your CRD for harborcluster only bucket and region are required fields.
required:
- bucket
- region
However, in this PR https://github.com/goharbor/harbor-operator/pull/266 the secretkeyref is always expected but if that is the case then we can't use IAM roles as per the implementation of the S3  https://docs.docker.com/registry/storage-drivers/s3/

Any update on this? Thanks.

Created PR - https://github.com/goharbor/harbor-operator/pull/811

Would be nice to get this released as v1.1.2

@davidg-sainsbury did you manage to run Harbor with IAM role on EKS?
I'm trying to do the same thing, but even with your fix, I believe I'm hitting this issue: https://github.com/distribution/distribution/issues/3275
Switching to an IAM account with the same policies works just fine, but I get access denied errors when no credentials are specified. Unfortunately, it's not really easy to determine what kind of access the registry is trying to use.

@davidg-sainsbury did you manage to run Harbor with IAM role on EKS?
I'm trying to do the same thing, but even with your fix, I believe I'm hitting this issue: distribution/distribution#3275
Switching to an IAM account with the same policies works just fine, but I get access denied errors when no credentials are specified. Unfortunately, it's not really easy to determine what kind of access the registry is trying to use.

We switched to the helm version of harbor rather than using the operator before I had chance to test this.  However, we are are experiencing the same issue as you and are waiting for the fix in the distribution engine - https://github.com/goharbor/harbor/pull/16435. As per your link to the issue, until distribution is using the newer AWS SDK you won't be able to use the AWS IAM permissions to access S3 from the harbor registry pods.

Thanks for the confirmation @davidg-sainsbury !

Thanks for the confirmation @davidg-sainsbury !

@sagikazarmark - harbor registry still has an issue with access to S3 via IAM roles with the latest pre-release of Harbor - v2.5.0-rc1  https://github.com/goharbor/harbor/issues/16490.  ChartMusuem appears to be fixed.

Any further updates on this? Is STS : https://docs.aws.amazon.com/STS/latest/APIReference/welcome.html perhaps a viabale workaround?

Hey folks, I'd like to know if this already fixed or not? I'm having trouble s3 storage backends using IaM roles and IRSA, but I'm not sure if this a problem on my end or generally still not solved. Appreciate any feedback.

It is not an issue anymore.
AFAIK, the instance should be inside the AWS cloud.
If the Harbor is installed in EC2 VM with docker-compose, you should grant the IAM role to the EC2 instance.
For pods in EKS, there is another approach you can find in the AWS document.
When you configure Harbor using s3 storage with IAM roles, you just remove the accesskey and secretkey in harbor.yml, then it uses the IAM role by default.
storage_service:
  s3:
    region: us-west-2
    regionendpoint:
    bucket: photon-harbor-registry
    encrypt: true
    secure: true
    v4auth: true
    chunksize: 5242880
    multipartcopychunksize: 33554432
    multipartcopymaxconcurrency: 100
    multipartcopythresholdsize: 33554432
    rootdirectory: /harbor-ci-1

@stonezdj it is not resolved for IRSA in EKS, which is still unsupported by Harbor as of writing.

Any chances to have IRSA support ? :(


Inline documentation updates

re-writing of some inline schema descriptions
This PR re-writes some of the root descriptions of the response type schemas (mostly) into slightly more verbose and formatted texts. Besides the "documentation is good" paradigm one reason is the intended use of these for generating documentation pages - see the (under construction) rendering at https://bycon.progenetix.org/generated/beacon-responses/

Hi @jrambla and @costero-e - can you please have a look if there are any factual errors? Otherwise this should be fast paced into main - only inline documentation changes.
Note: I've done this also for having a single point of documentation texts and w/ some maturity we can co-opt this for docs.genomebeacons.org later on. See https://bycon.progenetix.org/generated/beacon-responses/

@costero-e Hmmm... Why would this conflict with #174 ? Beyond rebasing etc. things, potentially. And yes, I did not run the JSON converter before committing; added now.

I was thinking in entryTypeDefinition.json file, which in #174 we are removing the filteringTerms entry and here is still existing. A same file modified by two different commits that are unaligned will make git complain I think.


Update 1-A1-setup.md

Add login add a password for localhost server.

Looks like this was done here https://github.com/facebook/makeitopen/pull/81.
Right now it's only visible when /next is in the URL, since a new version hasn't been made in Docusaurus. e.g. it's here on the web: http://makeitopen.com/docs/en/next/1-A1-local-setup.html


Official Matrix Chat created

I created an official room on the Matrix.org server. @jedisct1 you can contact me and I hand-over you the room key. Of course I would hand over the keys to anyone which want to help / moderate.

The room is encrypted by default (m.megolm.v1.aes-sha2), it used the matrix protocol and is (even in his earlier stage promising).
The official URL / Link is: #dnscrypt-proxy:matrix.org.
The chat could give basic help on several question, tips or tricks. It also can be used to discussion beta relevant topics.
if there is a wish/need I also can provide a bridge to IRC, Telegram or Signal so that you can get a grap between other clients to see/join/read the chat/discussion.
I would see this as a community driven room.

The room is basically created for people which don't want to login into GitHub, Reddit etc in order to ask a question or to get help. Matrix or the room etc. doesn't collect any personal information.

Nice, I like it. This should bridge with freenode too right?

Yep. I'll close my own 'ticket' here (soon) and merge it within the readme or wiki once I have more time. Since this is (as already correctly labeled) an announcement rather than a 'issue'.
Keep in mind that the bridges can be bugged from time to time but the guys working constantly on it to fix it.

[Matrix] is a good choice. It's very modern and end-to-end encrypted using rescent standards.
Also it have excellent client for it - Riot.im
Developer:	Vector Creations Limited
You may use it on Desktop and Mobile without any phone number, any personal data or even email (If you want, your can register email, so your friends which know it, will have ability find you somehow). Or stay unsearchable and completely anonimous (using Nickname only)

Some useful links (Riot.im):
Recommended by PRISM BREAK
Homepage
NEWS (Medium)
Chat | Regiser
BRIDGES
GitHub:
Source Code (Android)
Changelog
Download (source)
Desktop
Google Play
F-Droid (download *.apk)

Some people contacted me or wrote it into the chat so I try to keep it short and answer it for everyone here.

Why is everyone shown as offline?
Why is there no history?
Why is encryption enabled - shouldn't it be open same like the dnscrypt-proxy project on GitHub?
Why isn't there an IRC/Slack etc

Please see this issue, all official servers including our one (matrix.org) one disabled it (for now) in order to take less pressure on the service performance. You only see the status - for now - if you host it on your own server. But this might get fixed officially once there is a better solution for everyone.

I was able to enable chat-history myself with a hacky webhook. It should be visible for everyone now, even if you're a new visitor or re-join the chat.

Encryption is enabled because it's not my server. I simply want to protect the room or that someone interference into it from outside (MITM). That's all, you still can copy & paste the history conversations or screenshot it.

I wasn't able to integrate the bridge to IRC etc for now, I'm working on it, it seems you need to approve the bridge from the other side first. Since I'm not an active member on IRC, Slack etc anymore I simply need some time to re-create new accounts etc. I hope I have enough time over the next 4 weeks (yes I know sounds much but I'm busy).

I added an RSS Bot if you don't like security messages from Reddit.com/r/netsec and bleepingcomputer.com you can click on the Bot and press 'ignore' this will hide it's messages.
GitHub changes, comments etc. are handled by an GitHub Bot, so that you can see new commits, releases, issue tickets etc in the near future. The webhook is already running but I need to debug the problems now since he seems inactive for no reasons.
I think that the matrix protocol (electron) is the future and a full IRC/Slack/ICQ/WhatsApp/discord replacement and that's why I decided to use it, it has huge potential. It also has, in my opinion, the best privacy policy and works across all operating systems and everyone can see the source code etc.
Sorry for the long text. If there some wishes please feel free to contact me over my eMail, Blog or directly through Riot.


Repository not found

Hello,
I try to install satvis but when I ran:
git submodule update --init

I got:
fatal: repository 'https://github.com/AnalyticalGraphicsInc/cesium-assets.git/' not found

The cesium assets repository is now
https://github.com/AnalyticalGraphicsInc/cesium-assets-list.git

instead of
https://github.com/AnalyticalGraphicsInc/cesium-assets.git

Thanks for the report.
It seems like the cesium-assets repsoitory was deleted by Analytical Graphics.
Unfortunately cesium-assets-list is not a replacement as it only contains information about available terrain data, not the Natural Earth II tiled imagery itself.
The cesium-assets repository is still referenced in their Offline-Guide and there exists a few forks of it on Github.
For now I updated the submodule url to point to my own fork so the git submodule update --init should work again.


[BAD-1927] - When running many concurrent SQOOP processes, some SQOOP logs are missing.

@smmribeiro
@andreramos89
@renato-s

:white_check_mark: Build finished in 11m 20s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core

:exclamation: No tests found!
:information_source:  This is an automatic message

:x: Build failed in 8h 17m 5s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core

:exclamation: No tests found!
:information_source:  This is an automatic message

Closing this PR as it is not longer needed


Update: Update Go version

The version of Go was not updated.

Thanks for submitting this PR. We have tried to upgrade Golang to a newer version, however, we run into this issue with the built-in certificate.
https://jfrog.com/knowledge-base/general-what-should-i-do-if-i-get-an-x509-certificate-relies-on-legacy-common-name-field-error/
Because scanner is released daily, there will be a compatibility issue between the scanner and the existing controllers for the gRPC connection. We are still thinking how to mitigate this problem.


Add option to define the start path.

Right now, when importing it start the path at '../'
I would like an option to set it to './..'
It's a cosmetic feature, and an important one. :P. But, I would really like it.

Hey @michaeljota
Quick question.. Why? :-)
At the beginning, this extension did that. But is pretty useless since any filesystem will just strip the information. Is there any good reason to do this?

Semantic (?). I don't think there is a good reason, just matter of preference.
I may encounter some edge errors about it, but I can remember, so I stay in semantic. 😋

Well.. I did that in an old version of this plugin, and it caused errors on Windows machines and other special occasions. So I've got to say that I'm not really happy with this proposal.
Since it's not needed and it's much cleaner, I'll stay with the current implementation.
Maybe in the far future, there is room for such a thing, but right now I've got plenty of other stuff to work on 😉

I think got fixed somehow. Well, I do not see any option to configure it, but now the path start with './'. Do I close this?

Uhm... you can :-)
But I'm not really sure what I've done

If the path is a child of the current folder, the path start with ./ as import { SomeComponent } from './components/some.component.ts'´. But if the path is a father of the current folder, the path start with ../`.


⚠ SceneTime has degraded performance

In 870b41f, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 8266 ms

Resolved: SceneTime performance has improved in f50b289 after 6 minutes.


keying off snippet flag before deciding to use bem emmett

fixes bem-expand from blocking snippet completion on tab

Thanks for your contribution.

Thanks for letting me :). This is my first ever!


Setup custom transport for Micro-ROS native

THere are older commits included in the PR. Can you seperate them out ?

This is a draft PR. Please review 156 first


Background removal on portrait images

Hi, thanks for the great work you've done with this library!
Images passed to the model are cropped to be square.
I've tried handing it portrait images, but then it crashes.
Is it only able to handle square images?

I've found out that the model is trained on square images.


dark mode is gone

dark mode is gone in the latest version.

You should see the docs, the default behaviour now is 'auto', based on the color scheme of visitors' device. If you want to let the visitor decide  by their own, set themeconfig.themeColor.darkmode to 'switch'. It's the same as previous versions behaviour.

Official docs appearance on my device.

ok,thanks

Since the theme is allready in RC, I will make sure I marked all breaking changes next time.


Getting 403 forbidden when trying to use the bot in teams but works in bot framework emulator

Hi,
I have created a Bot using the BotBuilder SDK.
I am getting a 403 forbidden error shown in ngrok when trying to use the bot in teams.
I have ngrok running and have tested using the Bot Framework Emulator connected to the ngrok endpoint and it behaves as it should
Is there a reason why it would be returning a 403.. its as if the bot does not have permission ?

@theCorb1nator This is likely because something is not lined up somehow. Typically this could be the botFilePath, botFileSecret, MicrosoftAppId or MicrosoftAppPassword.
Does the Test in Web Chat functionality work? Are you using a .bot file (being phased out currently), or handing configuration in the code?

@theCorb1nator This is likely because something is not lined up somehow. Typically this could be the botFilePath, botFileSecret, MicrosoftAppId or MicrosoftAppPassword.
Does the Test in Web Chat functionality work? Are you using a .bot file (being phased out currently), or handing configuration in the code?

You are correct. i did not put my AppId, Password in the .bot file, it works now
What do you mean by its being phased out? whats the alternative.. appsettings.json?

What do you mean by its being phased out? whats the alternative.. appsettings.json?

That's exactly correct. See documentation here.


Question on maximum split files

Hi Ram
I was trying to split a large file into many small files. The script appears to fail at the 993 mark. Is there a limit to the number of split files that can be created? We need to split to over 1000.
Thank you Ron Davis

I missed seeing boskuv's comment. This has resolved my situation.
Thank you


the trait bound &mut Transaction<'_, Sqlite>: Executor<'_> is not satisfied

Bug Description
After updating to v0.7.0 I got this error
error[E0277]: the trait bound `&mut Transaction<'_, Sqlite>: Executor<'_>` is not satisfied
   --> file.rs:584:18
    |
584 |         .execute(&mut tx)
    |          ------- ^^^^^^^ the trait `Executor<'_>` is not implemented for `&mut Transaction<'_, Sqlite>`
    |          |
    |          required by a bound introduced by this call
    |
    = help: the following other types implement trait `Executor<'c>`:
              <&'c mut AnyConnection as Executor<'c>>
              <&'c mut SqliteConnection as Executor<'c>>
              <&Pool<DB> as Executor<'p>>
note: required by a bound in `sqlx::query::Query::<'q, DB, A>::execute`
   --> /Users/alimehasin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/sqlx-core-0.7.0/src/query.rs:151:12
    |
151 |         E: Executor<'c, Database = DB>,
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^ required by this bound in `Query::<'q, DB, A>::execute`

Minimal Reproduction
let mut tx = pool.begin().await.unwrap();

sqlx::query(r#"query"#,)
.execute(&mut tx)
.await
.unwrap();

Info

SQLx version: 0.7.0
SQLx features enabled: "runtime-tokio-rustls", "sqlite", "chrono"
Database server and version: Sqlite)
Operating system: macOS
rustc --version: 1.170

I'm not sure if this is the done thing - to comment on a closed issue, if not I can open a new one. However, I just updated my application to the 0.7.1 release, and I am having issues with the transaction trait bound, but only when the transaction is being used as a parameter to a function, see the code below
   /// Insert useragent into postgres
    async fn insert_user_agent(
        transaction: &mut Transaction<'_, Postgres>,
        req: &ReqUserAgentIp,
    ) -> Result<Useragent, sqlx::Error> {
        let query = "INSERT INTO user_agent(user_agent_string) VALUES ($1) RETURNING user_agent_id";
        sqlx::query_as::<_, Useragent>(query)
            .bind(req.user_agent.clone())
            .fetch_one(&mut *transaction)
            .await
    }

Am I doing something stupid here?
the error message from this is
the trait bound `&mut sqlx::Transaction<'_, sqlx::Postgres>: sqlx::Executor<'_>` is not satisfied the following other types implement trait `sqlx::Executor<'c>`:   <&'c mut sqlx::AnyConnection as sqlx::Executor<'c>>   <&'c mut sqlx::PgConnection as sqlx::Executor<'c>>   <&'c mut sqlx::sqlx_postgres::PgListener as sqlx::Executor<'c>>   <&sqlx::Pool<DB> as sqlx::Executor<'p>>


CI/CD Integration with Heroku

Integrate Heroku auto-deployment when occurs a merge in develop

PR:

https://github.com/roots-id/wal-agent/pull/2
https://github.com/roots-id/wal-agent/pull/3
https://github.com/roots-id/wal-agent/pull/4


How to add a period of time?

Version
1.6
Development Environment
Windows Chrome
Current Behavior

Currently the weekly calendar is shown from 1am to 23pm.

And I can create events every 30 minutes.

Expected Behavior

I would like to select this period, for example from 8am until 20pm.

And I'd like to force the creation of events every 1 hour

Thank you for listening,
I await an answer.

Hello.
First of all, thank you for your inquiry!
You said you wanted to increase the time between creation to one hour.
Does it mean the time interval shown in the weekly and daily view?
Or the drop down menu interval of creating the schedule modal?
I'll be waiting for the reply.
Thank you.

Hello, thank you very much for your interest in answering my question.
When I'm going to create a new event, I drag my mouse in the column, from the start time to the end, nowadays it lets me drag every 30 minutes, I wanted to make it by every hour.
If you also know how I can do the part of the period. Because that is more urgent.

I see :)
Please let me know if I'm wrong about what I understand or if you have any feedback on the following:

setting a start and end hour of weekly/daily view: (in consideration)

how to present the out-of-scope schedule

schedule 1 ~ 3, 21 ~ 23 => not showing? / schedule 7 ~ 10,  4 ~ 10 => showing?

setting a space of creation schedule guide(the blue layer): is it right?

Hello, I'm going to the second part you understood, that's exactly it, the blue area walk hourly.
In the second part, if you look at the image below, it is what appears to me nowadays, and the part in red is what I want it to appear:
http://prntscr.com/kgmewa
Again, thanks for your attention and I await a return :)

PR is reviewed. Need some changes.

Hellow.
Any news on this?
I have the same problem.
I would like to manage the minimal creation/updating interval of events.

Check #187 issue's last comment. Some nice guy give us fork version which implements what you said.


add step for PR creation against the reaction-gitops repo

Impact: minor
Type: feature
Issue
After we push the newly built Docker image for this service to DockerHub, we want to deploy it to an internal Kubernetes cluster.
Solution
We create a pull request against the reactioncommerce/reaction-gitops repository. The only modified file in this pull request is a special kustomization.yaml file which will contain the proper Docker image tag for the newly built Docker image. Once that PR is merged, the deploy will happen via a Gitops workflow.
Breaking changes
None.
Testing
Make sure a PR is created against reaction-gitops.

Closing, will open a new one against master.


Annotations are not highlighted in groovy

Hi, I don't know any Groovy.

@Component
public class SomeComponent {
    @RequestMapping(method = GET)
    def getRequest(@RequestParam("getParam") String getParam, @RequestParam(name="otherParam", defaultValue="10" int someInteger)) {
    }
}

@Component, @RequestMapping, @RequestParam here are examples of annotation is an annotation (meta-programming feature). CodeMirror does not highlight it in any way.
In the example @Component does not have parameters, @RequestMapping has one named parameter (method), 1st request param has one unnamed param (default parm name is value) @RequestMapping, second request param has two named parameters.
Parameters' values can be any language variables, types and literals.

CodeMirror does not highlight it in any way.

If I go to http://codemirror.net/mode/groovy/ and paste that example code, all the annotation names are highlighted as meta tokens. Am I missing something?

@marijnh hm... you're right, seems like it was some misconfiguration on my side. feel free to close this issue. I can't debug it at the moment anyway, we've had to abandon codemirror anyway due to some other out-of-scope considerations.

Ok, sorry to hear that. Good luck with your project, though!

@adrianheine it is not codemirror's fault, or else I would've filed an issue :) So don't be :)


notifyDataSetChanged not work on kotlin

i use the following code to update recyclerView content
mList.clear()
mList.addAll(list)
mStickyHeaderGridAdapter.notifyDataSetChanged()
but not work
then change to use
mStickyHeaderGridAdapter.notifyAllSectionsDataSetChanged()
still not work, is it a bug?

Sorry, it's my code problem, works perfectly~


bugsnag-react-native does not support bugsnag-cocoa 6.0

Description
As you know, bugsnag-cocoa has updated to v6.0. bugsnag-react-native still uses v5.23.9
Describe the solution you'd like
A bugsnag-react-native release that supports bugsnag-cocoa v6.0
Describe alternatives you've considered
n/a
Additional context
We want to be able to leverage all the work in bugsnag-cocoa v6.0 very soon.

Hi @bolsinga thanks for reaching out!
We are indeed looking to update our bugsnag-react-native notifier to use bugsnag-cocoa v6. We don't have a firm ETA for release, but it is likely to be of the order of a few weeks.

Thanks @phillipsam Is there a in progress branch integrating v6 that I may use to fix our use of the breaking changes in v6?

Hi @bolsinga unfortunately there is not a branch for this yet. We are planning to include the refresh of the RN notifier in bugsnag-js, so we would recommend holding off any implementation on this until this is released.

Hi @bolsinga - we have now released a new version of the bugsnag-js notifier which contains our brand new notifier for React Native. We recommend using the latest version: v7.3.1.

When will the bugsnag-cocoa changes be in bugsnag-react-native? Is bugsnag-js a replacement for bugsnag-react-native? Thanks

We have unified the bugsnag-react-native and bugsnag-js codebases, resulting in a new major version of bugsnag-js (v7.3.0) that supports React Native as well as browser JS and Node. This major version has also pulled in the latest major versions of bugsnag-android and bugsnag-cocoa.


fix: persist dev experimental storage state in feature specific dirs

With --experimental-enable-local-persistence in dev, we were clobbering a single folder with data from kv/do/cache. This patch gives individual folders for them. It also enables persistence even when this is not true, but that stays only for the length of a session, and cleans itself up when the dev session ends.
Fixes https://github.com/cloudflare/wrangler2/issues/830

Good recco, doing so. Thanks!


getstorybook is failing on Windows

getstorybook fails on Windows
Simple setup to reproduce:
I've installed latest create-react-app (1.5.2) and ran getstorybook in the freshly created project folder. That's what's happening on Windows:

I've tried it several times (also w/ ejecting the cra) - it always fails at this point.
Steps to reproduce

Use Windows 10 machine
npm install -g create-react-app
npm install - g @storybook/cli
create-react-app test-app
cd test-app
getstorybook

Please specify which version of Storybook and optionally any affected addons that you're running
<EMAIL_ADDRESS>Affected platforms

Windows 10
Node 8.3.0
NPM 5.3.0

It's running fine on macOS - so it seems to be a Windows specific thing.

Can you try updating storybook/cli to 4.0.0-alpha.4?

I'm also experiencing the exact same issue. Updating to 4.0.0-alpha.4 doesn't change anything.
Affected platforms

Windows 7
Node 10.0.0
NPM 5.6.0
Yarn 1.6.0

@dahei Do you have yarn installed?
@GeekMode what does yarn info babel-runtime version --json output for you?

{"type":"inspect","data":"6.26.0"}

The error is due to us trying to parse a Buffer as JSON. However, it used to be valid JSON.... maybe something with node 10? A fix would be Buffer.toString()

A fix would be Buffer.toString()

Which is highly recommended. A buffer is not automatically a string and can be anything afaik.

But it is just a warning. The issue is still the SyntaxError: Unexpected token ( in JSON at position 0 which also happens in Node.js 8 as you can see in the initial comment.

Found the bug. spawn doesn't have an encoding option in either node 8 or 10 which is specified here.
we're getting the stdout and stderr which are going to be outputs of npm or yarn which are strings.
The fix would be JSON.parse(data.toString('utf8'))

That was my initial reaction as well and that's what I tried, but unfortunately I get the exact same error.
 getstorybook - the simplest way to add a storybook to your project.

 • Detecting project type. ✓
 • Adding storybook support to your "Create React App" based projectundefined:1
(node:8928) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
^

SyntaxError: Unexpected token ( in JSON at position 0
    at JSON.parse (<anonymous>)
    at Socket.<anonymous> (K:/sites/story-test/node_modules/@storybook/cli/lib/latest_version.js:36:25)
    at Socket.emit (events.js:182:13)
    at addChunk (_stream_readable.js:280:12)
    at readableAddChunk (_stream_readable.js:265:11)
    at Socket.Readable.push (_stream_readable.js:220:10)
    at Pipe.onread (net.js:638:20)

Finally found the bug. It's actually yarn that is causing the issue. #https://github.com/yarnpkg/yarn/issues/5477. They have it already fixed but are waiting  for the next release. Until then, if anyone runs into this issue, just change the following line in @storybook/cli/lib/latest_version.js:
const packageManager = hasYarn() ? 'yarn' : 'npm';
to
const packageManager = 'npm';
Maybe downgrading to a previous release of yarn might do the trick too, but haven't tried that.

@GeekMode
Thank's for your investigation effort!
Unfortunately I don't have installed yarn so shouldn't hasYarn() return false? In that case it would have the same effect as your hotfix.
To prove it, I've changed latest_version.js as you suggested, but the error is still the same.

Did it work before (try testing with git bisect)?

So I messed around running getstorybook -f several times in the environment specified by @dahei. So what I noticed was that the process is quite random whether it passes. One time it just goes through eveyrthing without a problem, while the other time it fails as described in the screenshot above.
I then ran the process a few times again while logging the error as I mentioned in https://github.com/storybooks/storybook/issues/3529#issuecomment-386921105, because the original screenshot seemed like there was additional information being logged. In the end I found this error message by npm, which matches the original screenshot by @dahei:

This is weird :(

So from what I understand from all the comments is that there are two different issues atm, and please correct me if I'm wrong:

The original issue by @dahei, which I could mimic in https://github.com/storybooks/storybook/issues/3529#issuecomment-387106175, caused by npm since he has no yarn installed.

As specified by @GeekMode, a bug between yarn and node regarding some deprecated Buffer construction, with a matching stacktrace in https://github.com/storybooks/storybook/issues/3529#issuecomment-386924395. (Which might or might not be related to #3536 as said by @wuweiweiwu)

The first issue is something client-side and based on some quick Googling should happen frequently when running any npm command after the first occurrence. Because this has something to do with the environment of the user, storybook could either ignore the message or just display the message during the installation. Something like this:
    command.stderr.on('data', data => {
      // yarn error
      try {
        const info = JSON.parse(data);
        reject(new Error(info.data));
      } catch (e) {
        reject(new Error(data));
      }
    });

I tested this yesterday on my Windows machine and the installation of storybook (through npm) succeeds without any side effects, except that the whole npm update check failed is additionally printed. Might also be good to include a warning message of some kind.
The second problem, from as much as I could understand, is something storybook has no control over and could be considered to be fixed in the same way as the first issue. This is something yarn should take care of on their side, which is on its way. Personally, I think that it doesn't matter whether it is ignored/printed, as long at is doesn't block storybook from installing.

Same issue, but the weird thing is that it works fine sometimes without trying any solutions listed above.
The first time I ran getstorybook, it worked. Next time, failed.
I have tried re-install storybook, re-install node modules in the project. None of those can solve the issue.
After several failed attrempts, it worked again, but I don't know why.

Windows 10
node v8.11.1
npm v5.6.0
storybook/cli v3.4.3

Sounds like some racecondition or async issue imo.

@fralonra I think this is in line with what I found in https://github.com/storybooks/storybook/issues/3529#issuecomment-387106175:

So what I noticed was that the process is quite random whether it passes. One time it just goes through eveyrthing without a problem, while the other time it fails as described in the screenshot above.

You might be experiencing the same error as displayed in the screenshots in the first comment and in mine, but it's not for sure. There is a fix merged (#3563) that will ignore these warnings.

@Keraito : after 2 hours of trying to fix the  latest_version.js, to update my package.json and try every single tip i found about this isuue it still doesn't work for me :/ any help? does it work at least in an OSX environment ?

Ah it worked now ! i had to try getstorybook many times ! weird !

Hey @Safa2222, the main reason that you're encountering the issue is due to a npm update check failed (see screenshot in https://github.com/storybooks/storybook/issues/3529#issuecomment-387106175, the top border of the warning box matches the error in your screenshot in https://github.com/storybooks/storybook/issues/3571). It would be good to see if you encounter this as well when running other npm commands and resolve it if you deem necessary. When I tested this issue on my machines, it was also quite random when the warning would be thrown (exact comment: https://github.com/storybooks/storybook/issues/3529#issuecomment-387106175).
To resolve the issue you could either keep running getstorybook in the hope that it succeeds at some point, or your could apply the fix that was merged into storybook but not released yet (which will benefit u in the long run), see https://github.com/storybooks/storybook/pull/3563/files. Hope this can help you!

Released as 3.4.5


Gridsome Issue

Hello, first of all, amazing plugin! Simple and easy to use.
Am using Gridsome to develop a static page, while am running
$gridsome develop
The plugin works without any issue, it it when I try to run
$gridsome build
That I get the following error
Could not generate HTML for "/":
TypeError: [] is not a function
    at Module.223 (node_modules/vue-truncate-collapsed/dist/vue-truncate-collapsed.es.js:6:0)
    at __webpack_require__ (webpack/bootstrap:25:0)

Any pointer would be much appreciated

Hi @mmoscosa, thanks for that!
Could you provide a simple repository with the error? I never used Gridsome before, that would help a lot.


Set timeout period

Context: If I fetch a URL which does not exist, the program seems to hang for around 2 minutes before giving me an error. I want to set it to something shorter.

which program hangs? the client?
please post a script that i can use to reproduce the problem.

const request = require('@derhuerst/gemini/client.js');

const defaultOpts = {
    followRedirects: true,
    verifyAlpnId: () => true,
    tlsOpt: {
        rejectUnauthorized: false
    }
};

function gemfetch(url) {
    return new Promise((resolve, reject) => {
        request(url, defaultOpts, (err, res) => {
            if(err) {
                // TODO Handle error gracefully
                reject(err);
            }

            res.once("readable", () => {
                const doc = String(res.read());
                resolve(doc);
            })
        })
    })
}

gemfetch("gemini://binyam.in")
.then(res => {
    console.log(res)
}).catch(err => {
    throw err;
})

But listening on readable and using read(), you're switching res to non-flowing mode, which in itself is not a problem (for small responses).
But read() does not wait until there's data. When you call it, returns whatever is currently buffered in res (which is more or less what the client has received since the last read() call).
But if there's no response body immediately (either because the server didn't immediately respond with it, or because of network delays), then your first read() call will return null.
There are multiple ways to fully read a readable stream, but since you just want to concatenate all data into a string, this is the simplest way:
let doc = ''
res.on('data', chunk => {
  doc += chunk
})
res.on('end', () => {
  resolve(doc)
})

I've just re-read your original question: Is this Issue about a server that doesn't even accept the request? As in, the TLS connection attempt times out?

As of<EMAIL_ADDRESS>you now pass connectTimeout to request():
const request = require('@derhuerst/gemini/client.js');

function gemfetch(url) {
    return new Promise((resolve, reject) => {
        request(url, {
            connectTimeout: 10 * 1000, // 10s
        }, (err, res) => {
            if(err) {
                reject(err);
                return;
            }

            let doc = ''
            res.on('data', (chunk) => {
                doc += chunk;
            })
            res.once('end', () => {
                resolve(doc);
            })
        })
    })
}

gemfetch("gemini://binyam.in")
.then(res => {
    console.log(res)
})
.catch(err => {
    console.error(err);
    process.exit(1)
})

@derhuerst Thank you. As I mentioned, it's a browser for gemini. How would you recommend I connect to the servers? Does it make sense to use gemini-fetch for each URI?

Is the browser supposed to handle large files? If yes, use a stream-based approach. Otherwise I think something like gemini-fetch will be a more convenient API.

I hadn't thought about file size. I'll probably use gemini-fetch. Thank you again.

yeah, a stream based API is only relevant if a) you want to download/display files larger than the memory you want to use up, or b) if you want to start parsing/processing/rendering the file before it has finished downloading.


Question: how do I retrieved a saved metric from MongoObserver?

I followed this github issue to figure out how to extract artifacts from the MongoObserver into python, but I'm not sure how to get metrics out. I found something called metrics using the following code:
client=pymongo.MongoClient()
dbname = "mmseg-test"
entry = client[dbname]["runs"].find_one({"_id": 119})  # arbitrary test I can see in Omniboard
metrics = entry["info"]["metrics"]

I see a list of dictionaries with the right names of the metrics, but I don't know how to retrieve the actual values:
[
    {'name': 'TrainingTimeHrs', 'id': '62c1255feb1f4bb30b356886'},
    {'name': 'mIoU', 'id': '62c1256ceb1f4bb30b3568b5'},
    {'name': 'IoUs_class0', 'id': '62c1256ceb1f4bb30b3568b7'},
    {'name': 'IoUs_class1', 'id': '62c1256ceb1f4bb30b3568b9'},
    {'name': 'IoUs_class2', 'id': '62c1256ceb1f4bb30b3568bb'},
    {'name': 'IoUs_class4', 'id': '62c1256ceb1f4bb30b3568bd'},
    {'name': 'IoUs_class3', 'id': '62c1256ceb1f4bb30b3568bf'},
    {'name': 'IoUs_class_5', 'id': '62c1256ceb1f4bb30b3568c1'},
    {'name': 'Accuracy', 'id': '62c1256ceb1f4bb30b3568c3'},
]

As far as I can search nothing in entry contains this information:
entry.keys()
dict_keys(['_id', 'experiment', 'format', 'command', 'host', 'start_time', 'config', 'meta', 'status', 'resources', 'artifacts', 'captured_out', 'info', 'heartbeat', 'result', 'omniboard', 'stop_time'])

I'm sure I'm missing somewhere where the 'id' field can be used to query for the value, I'd be grateful if anyone knows where that is :)
Thanks!

Hi @FranzEricSchneider! I currently can't test this, but from the MongoObserver source code there should be a metrics collection in your database (client[dbname]["metrics"])

Thank you @thequilo! It took a little fiddling to figure out how to grab values from that, but this appears to work. Let me know if there's a more obvious way:
metrics = client["mmseg-test"]["metrics"]

# just to figure out what type of stuff is there
ms.find_one()
Out:
{'_id': ObjectId('62a89f60065c4cb8959b9e27'),
 'name': 'mIoU',
 'run_id': 17,
 'steps': [0],
 'timestamps': [datetime.datetime(2022, 6, 14, 14, 46, 56, 705000)],
 'values': [0.9124475498083493]}

# After some poking the "_id" field appeared to be a bson object, whatever that is
metrics.find_one({"_id": bson.objectid.ObjectId('62a89f60065c4cb8959b9e27')})
Out:
{'_id': ObjectId('62a89f60065c4cb8959b9e27'),
 'name': 'mIoU',
 'run_id': 17,
 'steps': [0],
 'timestamps': [datetime.datetime(2022, 6, 14, 14, 46, 56, 705000)],
 'values': [0.9124475498083493]}


tests: Disable visualiser tests

Caused so much maintainer pain due to intermittent failures.

I'm merging until somebody has time to fix this ... :-/

sounds like this is the best option right now unfortunately :)
would love to make the visualizer tests working though

I think this is an example where it failed sporadically: https://travis-ci.org/spotify/luigi/jobs/102026785
I found that example only by going back a few PRs. Though it didn't seem that frequent, but often enough to annoy.
ping @QuentinBrosse in #2193

I have tried to reproduce the bug many times without success.. :/


[Improvement] UI, Paimon catalog, schema properties can be set when backend is jdbc and hive.

What would you like to be improved?

How should we improve?
Support  schema properties  in paimon schema create UI.
Only FilesystemCatalog doesn't support.

@LauraXia123   Do you know anyone can help fix this issue?


Test use case: no overspending

Bob should not be able to send more tokens than he has

Let's say Bob has 100 tokens. He should not be able to send more than
100 tokens to Alice.

If there's an incoming but unconfirmed deposit into Bob's account then Bob
should not be able to use the incoming tokens until the spend transaction
 they are in is confirmed.

Bob's node is started, he mines a couple of blocks and gets some coinbase rewards. Then he tries to send to Alice more token that he has.
We wait for another block to be mined to verify that neither Bob's, nor Alice's balances had changed.

Aside for the assert, this looks good to me.

I've refactored a little bit getting the balance so it always returns a Balance object (even when there is no such account created, balance being 0)
As for checking that the spend tx was considered for inclusion: I don't think there is a good way of doing this while considering the node itself as a black box.

Command make multi-build && make multi-start && make python-env && make python-single-integration-test TEST_NAME=spend_tx failed locally for me so I plan to test this a bit more locally before approving.

I see the test assumes node built but not started: make multi-build && make python-env && make python-single-integration-test TEST_NAME=spend_tx made more progress.

The only CI job missing for this PR is OSX package job. All other jobs passed.
I believe this PR does not need to wait for OSX package job:

This PR does not affect creating the package, as it is only test files;
This PR does not affect script py/tests/release.py, that is run in package job.


CreateClassVoice Plugin not working

Works in test server, but doesn't work in the deployed discord.

Worked in cot3100_hooshmand channel, but not cop3502_meade

I think it doesn't work when the class has a lot of people registered for it

@tanndlin can we close?


chore: add SCA to plugin name

this will help to differentiate in admin from original Stripe plugin

:tada: This PR is included in version 1.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fastpages + mkdocs ??

Hi,
Great tool. Thanks a lot.
I am just curious if there is any way to integrate fastpages and mkdocs?
That would be awesome!!
Thanks!

No not at the moment.


 Default to 1.20 for building and testing.

✅ I have run these commands

[x] make lint
[x] make test-race
[x] go mod tidy

Codecov Report

Merging #454 (6d52390) into main (256be1b) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 6d52390 differs from pull request most recent head 6242ba3. Consider uploading reports for the commit 6242ba3 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #454   +/-   ##
=======================================
  Coverage   66.66%   66.66%
=======================================
  Files           8        8
  Lines        1212     1212
=======================================
  Hits          808      808
  Misses        355      355
  Partials       49       49

Flag
Coverage Δ

unittests
66.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Totally disorder displaying

Have seen bellow screen few times. Cannot reproduce in purpose. No clue / idea why it happened. Has anyone seen same screen or have idea to check / fix? Thanks

Thanks @nguyenpham ! :smile:
Please provide all the information in the issue template so we can help!
And don't forget to read our contribution guidelines. :blush:


Fix GHCR image tags

Hi there, I found a bug when try to install this package using the helm chart and I would like to suggest the fix for this.
The error is ErrImagePull and this bug start when this repo migrate from dockerhub to ghcr. This happens because the helm chart try to download the image ghcr.io/labbs/github-actions-exporter:v1.9.0 (here), but this image tag doesn't exists on ghcr.
All image tags on ghcr was generated without the prefix v and my suggestion is put this prefix to mantain the same pattern that was used in the dockerhub.
So I did this fix using the docker metadata docs and below have the comparasion tags:

before: latest, sha-5e37462, 1, 1.9, 1.9.0
result: latest, sha-5e37462, v1, v1.9, v1.9.0

This is the solution that I was waiting for. Thanks, Hebert!


Timesheet - 12/06/2021 - James Pang

Task 1
UI Updates
Proof of Work

https://github.com/thenewboston-developers/Website/pull/1851

Time Spent
1.5 hours

Task 2
Reviewing + Merging of PRs
Proof of Work

https://github.com/thenewboston-developers/Website/pull/1846
https://github.com/thenewboston-developers/Website/pull/1849
https://github.com/thenewboston-developers/Website/pull/1854
https://github.com/thenewboston-developers/Website/pull/1853

Time Spent
1.5 hours

Total Time Spent
4 hours
Account Number
3443227b5f81d2e2e595c52fe0fafce0870c4c4d837a550ef084d44cb95aa4be

@jamessspanggg, the hours don't add up to the total. Please fix, thanks.

@jamessspanggg, the hours don't add up to the total. Please fix, thanks.

Whoops my apologies, done.


update, add workflow-configuration, deps-ubuntu and docker

@stweil, this is my attempt at a "fat" docker setup. Having difficulties getting versioning right for my slim docker proposal, I think this is at least a good stopgap. The result can be obtained under dockerhub as bertsky/ocrd_all for now (but I hope someone will publish it under ocrd/all soon).
@mikegerber @kba, I also included an updated version of bertsky/workflow-configuration. (For those afraid of calling make I included a system-wide installation as ocrd-make, simply wrapping the make calls.)

@kba, should we move the repository to OCR-D? I suggest to keep the name then because I think that just all is too generic.

@stweil, regarding the pip inconsistencies, as you can see at the bottom of the Dockerfile, I alreaddy added a workaround there (that can be updated as long as no actual incompatibilities are involved).
Do you want me to move that to the Makefile so it is available for the local installation as well?

Do you want me to move that to the Makefile so it is available for the local installation as well?

Done.
@stweil Can you merge?

@bertsky, I started with cherry-picking changes from this pull request, so you'll have to rebase your branch.

I could not find the updated revision for ocrd_im6convert upstream.

Because it is not merged yet.

It would be much easier for me to review and merge changes presented in small pull requests which address a single feature and only contain one or two commits.

I see. But then those PRs would heavily depend on each other. And some things just belong in one PR. It's been quite difficult making this docker thing work. And now the automatic dependencies for local installation.

@bertsky, I started with cherry-picking changes from this pull request, so you'll have to rebase your branch.

Please don't do this to me.

@stweil When you take this PR apart, are you sure you want to test every single change here with the huge long docker build, which for performance reasons is non-incremental in the commited version? It was already extremely time-consuming having this repeated layer by layer when I made changes. And testing is a must here, you cannot rely on anything...

I could not find the updated revision for ocrd_im6convert upstream.
It would be much easier for me to review and merge changes presented in small pull requests which address a single feature and only contain one or two commits.

Yeah, maybe keep the submodule updates out of this PR.

Yeah, maybe keep the submodule updates out of this PR.

I don't understand you guys. Is no-one seeing the connection? Almost all those updates were necessary to get the new functionality (automatic system dependencies, Docker integration, module filtering, workarounds for conflicts) working. In many cases, I conjured up the module updates just for this PR!
With this attitude (keep it small, split it up and rebase), you are making it unnecessarily hard (and frustrating) to bring in solutions. It was already costly to fight through this (waiting for docker build to fail over and over again, wasting tons of network bandwidth, making all this work automatically and maintainably).
I don't want go over all those steps and test them again for no good reason.
You can easily make all / make docker on the PR as a whole – if that fails, we should talk.

@bertsky, I now get an ocrd/all docker of 5.02 GB when I run make docker with the latest code which includes most of your modifications. Which tests would you suggest to verify that everything is fine?

@bertsky, I now get an ocrd/all docker of 5.02 GB when I run make docker with the latest code which includes most of your modifications. Which tests would you suggest to verify that everything is fine?

Well that's already a (partial) success. (It should be around 7 GB though. Maybe intermediate steps have failed? I recently added set -e to docker.sh to avoid overlooking problems. I'll add that to the PR as soon as the new problem in core is fixed.)
Next steps would be to run some workflow and validate. I am afraid there are no smoke tests for that in core or assets. But you can use workflow-configuration – this is what I do. For example, run docker run -it -u $(id -u) -v /path/to/workspaces:/data ocrd/all ocrd-make -f gt-binarize-page-olena-sauvola-deskew-page-ocropy-clip-deskew-region-tesseract-resegment-dewarp-ocr-ocropy-tesseract.mk.

@stweil Note, there seems to be connectivity problems with GH these days – you might have to repeat steps.

@bertsky, I rebased the pull request now. The result only differs from the previous one in some submodule revisions, partly because they are now newer, partly because the old pull branch referred to non existing revisions.

@bertsky, I rebased the pull request now. The result only differs from the previous one in some submodule revisions, partly because they are now newer, partly because the old pull branch referred to non existing revisions.

@stweil, I cannot compare this, due to the rebase (that's why I opted for a merge commit instead).
Which submodules are different, what revisions? (This is important, because it might break things again.)
You still say non-existing revisions, but as I answered you already, these were perfectly valid revisions, just not on the module's master (yet).

You still say non-existing revisions, but as I answered you already, these were perfectly valid revisions, just not on the module's master (yet).

A new revision from a pull request only exists in the repository from which that pull request originated. Such a revision is unavailable for most people.
The rule for a valid submodule revision is simple: the revision must exist in the repository of the submodule (not necessarily in the master branch). If it only exists in your fork, it is not valid.

@stweil, I cannot compare this, due to the rebase (that's why I opted for a merge commit instead).

These commands might work for your environment:
git fetch
git diff origin/fat-docker

A new revision from a pull request only exists in the repository from which that pull request originated. Such a revision is unavailable for most people.

That's simply not true: A PR's commits are automatically added to a new branch pull/NUM/head on the receiving end. Did you even try to just git submodule update?

These commands might work for your environment:
git fetch
git diff origin/fat-docker

The updates seem to be ok (but I have not rebuilt and tested the docker images yet). Except for ocrd_im6convert, which definitely needs https://github.com/OCR-D/ocrd_im6convert/pull/9/commits/1b082f072158bc2d044deea9bd4fc90e02321af8 (because deps-ubuntu must be run non-interactively), as I said.

The updates seem to be ok (but I have not rebuilt and tested the docker images yet). Except for ocrd_im6convert, which definitely needs OCR-D/ocrd_im6convert@1b082f0 (because deps-ubuntu must be run non-interactively), as I said.

I reverted to the needed version, which is now also on ocrd_im6convert:master.

A new revision from a pull request only exists in the repository from which that pull request originated. Such a revision is unavailable for most people.

That's simply not true: A PR's commits are automatically added to a new branch pull/NUM/head on the receiving end. Did you even try to just git submodule update?

With even that out of the way, can you finally merge?

@stweil do you want me to update core again here (significantly, we now have processor parameter validation), or are you going to apply that yourself after the PR?

I have updated core now.


Add study averages as top row for each column

Add study averages as top row for each column. Request from DMEDS, but low priority.

Good idea. Should be pretty trivial to add if we just make "Overall" the top level of the nest by default. Basically:
chart.on("init",function(){
   this.raw_data.forEach(function(d){
       d.overall = "Overall"
    })
})
config.levels = d3.merge(["overall"],config.levels])

Tested and confirmed that the new "Overall" bar is added at the top of the chart showing study averages as a top row for each column.