Tap Events: Holding event not firing.

Describe the bug
Tap Events: Holding event never fires on button
To Reproduce
Create a very basic Avalonia application: I did this by using VisualStudio Project Menu -> Avalonia C# Project.
I added a button to the MainWidow.
<Window xmlns="https://github.com/avaloniaui"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        mc:Ignorable="d" d:DesignWidth="800" d:DesignHeight="450"
        x:Class="AvaloniaApplication1.Views.MainWindow"
        Icon="/Assets/avalonia-logo.ico"
        Title="AvaloniaApplication1">

	<Button Margin="50, 50, 0, 0"
            Content="TEST"
            Height="50"
            Width="50"
            Background="Yellow"
            Foreground="Red"
            HorizontalAlignment="Left"
            VerticalAlignment="Top"
            Gestures.IsHoldWithMouseEnabled="True"
            Gestures.IsHoldingEnabled="True"
            Holding="InputElement_OnHolding">
    </Button>

</Window>

I also added the handler in the code behind
using Avalonia.Controls;
using Avalonia.Input;

namespace AvaloniaApplication1.Views;

public partial class MainWindow : Window
{
    public MainWindow()
    {
        InitializeComponent();
    }

    private void InputElement_OnHolding(object? sender, HoldingRoutedEventArgs e)
    {
        var breakPointTest = false;
    }
}

Expected behavior
The breakpoint in never hit and, by looking ad the DevTools, the holding event is never generated by the Avalonia code.
Based on the online documentation, settings the Gestures should be enough.
https://docs.avaloniaui.net/docs/concepts/input/pointer
Upon additional debug, it seems that the method GetIsHoldWithMouseEnabled in Gestures always return false, eventhough the property is set to true in the xaml.
 public static bool GetIsHoldWithMouseEnabled(StyledElement element)
        {
            return element.GetValue(IsHoldWithMouseEnabledProperty);
        }

Avalonia version
11.1.3 (the same applies to 11.2.0-rc)
OS
Windows
Additional context
Win 11 Enterprise 23H2
VS2022 17.11.4

Certain events, often gestures, are dependent on certain other events occurring (or not occurring). Controls such as Button will handle PointerPressed events which is a required part of Gestures.Holding, so it never happens. If you change your example to Rectangle, add a Fill, and remove the Button-specific properties, your gesture hits the breakpoint.
Some design insight here from the team may be necessary. Could required events in gestures be subscribed with handledEventsToo: true so gestures will still fire regardless of a control's opinions on handling events? I'm not able to capture the HoldingEvent despite AddHandler with Tunneling and handledEventsToo: true, but I expected that.

I could be wrong, but based on my analysis, I believe that the event handling from the Button are correctly set. What appears to be the main issue is that the property IsHoldWithMouseEnabledProperty always returns false in Gestures when GetIsHoldWithMouseEnabled(StyledElement element) is invoked. The property is set to true in the xaml.

What appears to be the main issue is that the property IsHoldWithMouseEnabledProperty always returns false in Gestures when GetIsHoldWithMouseEnabled(StyledElement element) is invoked.

After investigating, you're correct. Please disregard my previous comment.
Gestures.IsHoldWithMouseEnabledProperty is not an inherited attached property (unlike Gestures.IsHoldingEnabled which is inherited). I'm not sure what the reason is behind this. Please leave the issue open for a maintainer to determine if this is a bug or by-design.
Anyways, as a workaround, I've tested the following to work (Fluent Theme):
<Style Selector="Button /template/ ContentPresenter#PART_ContentPresenter">
    <Setter Property="(Gestures.IsHoldWithMouseEnabled)" Value="True" />
</Style>

You could forward this via binding instead:
<Style Selector="Button /template/ ContentPresenter#PART_ContentPresenter">
    <Setter Property="(Gestures.IsHoldWithMouseEnabled)" Value="{Binding $parent[Button].(Gestures.IsHoldWithMouseEnabled)}" />
</Style>

Thanks for your reply, I can confirm that this workaround works in my test application. It also work if I regress the Avalonia version back to 11.1.0.

An update on this. I noticed that the workaround works only if the pointer is not over the AccessText element of the button.
When the pointer is over the Button but not over the AccessText, the Holding event is fired.

When the pointer is over  the AccessText, the Holding event is NOT fired.

Thanks

You can make the workaround selector more universal and apply to all descendant controls. The holding event will bubble up to your Button handler.
<Style Selector="Button :is(Control)">
    <Setter Property="(Gestures.IsHoldWithMouseEnabled)" Value="{Binding $parent[Button].(Gestures.IsHoldWithMouseEnabled)}" />
</Style>


[FEATURE] Support s390x IBM Z

Is your feature request related to a problem? Please describe
We are looking to use Longhorn as the storage layer on IBM Z. This would expand Rancher's ability to run a full solution on any infrastructure.
Describe the solution you'd like
Add IBM Z runners to the build process and package the output into the airgap tarball.
Additional context
This is part of the larger push to build Rancher components on IBM Z.

cc @meldafrawi

I've validated today's master build of Longhorn on s390x installed from locally checkouted helm chart stored on upstream lh master branch.
Environment description

1 server and 2 agent nodes deployed with RKE2 v1.23.5+rke2r1 (without rancher mcm)
using zVM hypervisor - each VM with 2 vCPU, 8GB RAM and 20GB btrfs as rootfs
all nodes running on SLE15SP2 with open-iscsi and nfs-client installed
Tested with Minio as S3 backend, pytest -m coretest executed

Longhorn installed by:
helm upgrade --install=true longhorn ./ --namespace=longhorn-system --create-namespace \
    --set image.longhorn.instanceManager.tag=master-head \
    --set image.longhorn.shareManager.tag=master-head \
    --set image.longhorn.backingImageManager.tag=master-head

Results
= 7 failed, 45 passed, 6 skipped, 173 deselected, 1 error in 5289.67s (1:28:09)

pytest logs here
support bundle here

All pods and other resources in longhorn-system seem to be healthy as well as webui.
I'm still using a bit outdated (rebased 24d ago) custom fork of longhorn-tests repository and also test image so some failures could be ralated to that.
I'd appreciate if someone from LH team could have a look at the results if these are ok, thanks.

cc @longhorn/qa

@thehejik Could you run again preview 1? I would expect we will have the result for each milestone here because we don't have s390x automation and it's better to have each update. Thank you.

Results from testing v1.3.0-preview1 build and longhorn-tests from the same tag, this time with nfs & minio:
= 6 failed, 60 passed, 5 skipped, 220 deselected, 2 errors in 7678.35s (2:07:58)
test_backing_image.py::test_backing_image_basic_operation FAILED
test_backing_image.py::test_engine_live_upgrade_with_backing_image FAILED
test_engine_upgrade.py::test_engine_offline_upgrade FAILED
test_engine_upgrade.py::test_engine_live_upgrade FAILED
test_engine_upgrade.py::test_engine_live_upgrade_with_intensive_data_writing FAILED
test_ha.py::test_ha_salvage FAILED

pytest logs here
support bundle here

Once I rebuilt longhorn-engine image for upgrade tests all the upgrade related tests from -m coretest started to PASS.
Results from -m coretest pytest run on v1.3.0-preview1 on s390x and logs here:
test_ha.py::test_ha_salvage FAILED
= 1 failed, 55 passed, 6 skipped, 173 deselected, 2 errors in 5818.04s (1:36:58) =

Results from "full" pytest run on v1.3.0-preview1 on s390x and logs here:
test_backing_image.py::test_ha_salvage_with_backing_image FAILED         [  4%]
test_csi.py::test_allow_volume_creation_with_degraded_availability_csi FAILED [ 34%]
test_ha.py::test_ha_salvage FAILED                                       [ 42%]
test_ha.py::test_rebuild_with_restoration[s3] FAILED                     [ 45%]
test_migration.py::test_migration_confirm FAILED                         [ 57%]
test_node.py::test_node_default_disk_added_back_with_extra_disk_unmounted FAILED [ 65%]
test_node.py::test_node_config_annotation_invalid FAILED                 [ 67%]
test_node.py::test_node_config_annotation_missing FAILED                 [ 68%]
test_rwx.py::test_rwx_parallel_writing FAILED                            [ 82%]
test_infra.py::test_offline_node FAILED                                  [100%]
= 10 failed, 206 passed, 18 skipped, 7 errors in 30416.19s (8:26:56) =

Results from -m coretest pytest run on v1.3.0-rc1 on s390x and logs here:
test_engine_upgrade.py::test_engine_live_upgrade_with_intensive_data_writing FAILED [ 76%]
test_ha.py::test_ha_salvage FAILED                                       [ 78%]
= 2 failed, 59 passed, 5 skipped, 220 deselected, 10 errors in 7476.00s (2:04:36) =

(used nfs and s3/minio as backup backends)

Results from full pytest run on v1.3.0-rc1 on s390x, logs here
test_backing_image.py::test_ha_salvage_with_backing_image FAILED         [  4%]
test_basic.py::test_backup_lock_deletion_during_backup[s3] FAILED        [ 21%]
test_basic.py::test_allow_volume_creation_with_degraded_availability_dr[s3] FAILED [ 23%]
test_cloning.py::test_cloning_interrupted FAILED                         [ 29%]
test_engine_upgrade.py::test_engine_live_upgrade_with_intensive_data_writing FAILED [ 39%]
test_ha.py::test_ha_salvage FAILED                                       [ 40%]
test_ha.py::test_inc_restoration_with_multiple_rebuild_and_expansion[s3] FAILED [ 44%]
test_ha.py::test_inc_restoration_with_multiple_rebuild_and_expansion[s3] ERROR [ 44%]
test_ha.py::test_engine_crash_for_dr_volume[s3] FAILED                   [ 47%]
test_ha.py::test_engine_crash_for_dr_volume[s3] ERROR                    [ 47%]
test_node.py::test_disable_scheduling_on_cordoned_node FAILED            [ 58%]
test_node.py::test_replica_scheduler_too_large_volume_fit_any_disks FAILED [ 59%]
test_recurring_job.py::test_recurring_job_multiple_volumes[s3] FAILED    [ 80%]
test_rwx.py::test_rwx_parallel_writing FAILED                            [ 82%]
test_settings.py::test_instance_manager_cpu_reservation FAILED           [ 90%]
test_infra.py::test_offline_node FAILED                                  [100%]
test_infra.py::test_offline_node ERROR                                   [100%]
= 15 failed, 213 passed, 18 skipped, 1 warning, 3 errors in 33210.05s (9:13:30) =

Results from full pytest run on v1.3.0-rc2, logs here
test_backing_image.py::test_ha_salvage_with_backing_image FAILED         [  4%]
test_cloning.py::test_cloning_interrupted FAILED                         [ 29%]
test_csi.py::test_allow_volume_creation_with_degraded_availability_csi FAILED [ 33%]
test_ha.py::test_inc_restoration_with_multiple_rebuild_and_expansion[s3] FAILED [ 44%]
test_ha.py::test_dr_volume_with_restore_command_error[s3] FAILED         [ 46%]
test_ha.py::test_engine_crash_for_restore_volume[s3] FAILED              [ 46%]
test_ha.py::test_engine_crash_for_dr_volume[s3] FAILED                   [ 47%]
test_scheduling.py::test_data_locality_basic FAILED                      [ 89%]
test_settings.py::test_instance_manager_cpu_reservation FAILED           [ 90%]
test_settings.py::test_setting_backing_image_auto_cleanup FAILED         [ 91%]
test_infra.py::test_offline_node FAILED                                  [100%]
test_infra.py::test_offline_node ERROR                                   [100%]
= 11 failed, 216 passed, 19 skipped, 1 warning, 1 error in 34972.54s (9:42:52) =

Results from -m coretest on v1.3.0-rc3 running on three nodes v1.23.7+rke2r1 SLE15SP3.s390x cluster with EXT4 rootfs, Minio as s3 backupstore. Logs here
test_basic.py::test_allow_volume_creation_with_degraded_availability FAILED [ 53%]
test_csi.py::test_allow_volume_creation_with_degraded_availability_csi FAILED [ 67%]
= 2 failed, 54 passed, 6 skipped, 184 deselected, 1 warning in 6084.31s (1:41:24) =

@cchien816 Could you follow up on the test result to see if any difference compared with our amd64? then we will better understand the failure is actually because of still some flaky tests. Thank you.
cc @longhorn/qa

Results from full pytest run on v1.3.0-rc3, logs here
test_backing_image.py::test_ha_backup_deletion_recovery[s3] FAILED       [  4%]
test_basic.py::test_allow_volume_creation_with_degraded_availability FAILED [ 22%]
test_basic.py::test_multiple_volumes_creation_with_degraded_availability[s3] FAILED [ 23%]
test_cloning.py::test_cloning_interrupted FAILED                         [ 29%]
test_csi.py::test_csi_io FAILED                                          [ 30%]
test_csi.py::test_allow_volume_creation_with_degraded_availability_csi FAILED [ 33%]
test_ha.py::test_engine_crash_for_restore_volume[s3] FAILED              [ 46%]
test_ha.py::test_engine_crash_for_dr_volume[s3] FAILED                   [ 47%]
test_ha.py::test_autosalvage_with_data_locality_enabled FAILED           [ 51%]
test_scheduling.py::test_replica_rebuild_per_volume_limit FAILED         [ 87%]
test_scheduling.py::test_data_locality_basic FAILED                      [ 89%]
test_settings.py::test_instance_manager_cpu_reservation FAILED           [ 90%]
test_settings.py::test_setting_backing_image_auto_cleanup FAILED         [ 91%]
test_infra.py::test_offline_node FAILED                                  [100%]
test_infra.py::test_offline_node ERROR                                   [100%]
= 14 failed, 213 passed, 19 skipped, 1 warning, 1 error in 34455.86s (9:34:15) =

Mention in the 1.3.0 doc, https://github.com/longhorn/website/commit/87cd69f9bbc22bfd173e820ca9726e4614e99b49

Compare IBM Z test result and SLES test ressult, there are few test results may need to keep tracking :

test_scheduling.py::test_data_locality_basic - not happen in SLES test result
test_settings.py::test_instance_manager_cpu_reservation - not happen in SLES test result
test_infra.py::test_offline_node - not happen in SLES test result

Compare IBM Z test result and SLES test ressult, there are few test results may need to keep tracking :

test_scheduling.py::test_data_locality_basic - not happen in SLES test result
test_settings.py::test_instance_manager_cpu_reservation - not happen in SLES test result
test_infra.py::test_offline_node - not happen in SLES test result

@thehejik Could you help manually verify these test cases or even run them to see if they will pass? Thanks.

Just re-verified the failed tests by deploying a fresh RKE2.s390x cluster with more RAM (4->8GB), vCPUs (2->4) and storage (20->40GB).

test_scheduling.py::test_data_locality_basic - PASSED when RETRY_INTERVAL is set to 2 instead of default 0.5 in common.py
test_settings.py::test_instance_manager_cpu_reservation - PASSED no modification needed
test_infra.py::test_offline_node - still FAILED most likely because it's intended for AWS infra only.

So I think the results are consistent with amd64/SLES.

Closing, because the integration is finished and all testings align with other supported arches.

Results from -m coretest on v1.3.0 running on three nodes v1.24.1+rke2r2 SLE15SP3.s390x cluster with EXT4 rootfs, Minio as s3 backupstore. Logs here
test_csi.py::test_allow_volume_creation_with_degraded_availability_csi FAILED [ 67%]
= 1 failed, 55 passed, 6 skipped, 185 deselected, 1 warning in 5603.23s (1:33:23) =

Results from full pytest run on v1.3.0, logs here
test_cloning.py::test_cloning_interrupted FAILED                         [ 29%]
test_csi.py::test_allow_volume_creation_with_degraded_availability_csi FAILED [ 33%]
test_ha.py::test_rebuild_with_restoration[s3] FAILED                     [ 43%]
test_ha.py::test_engine_crash_for_restore_volume[s3] FAILED              [ 46%]
test_ha.py::test_engine_crash_for_dr_volume[s3] FAILED                   [ 47%]
test_scheduling.py::test_data_locality_basic FAILED                      [ 89%]
test_infra.py::test_offline_node FAILED                                  [100%]
test_infra.py::test_offline_node ERROR                                   [100%]
= 7 failed, 220 passed, 20 skipped, 1 warning, 1 error in 32744.49s (9:05:44) ==


i18n(de): Update guides/configuring-astro.md

What kind of changes does this PR include?

New or updated content
Translated content

Description
Add german translation for guides/configuring-astro.md

Thanks for your feedback. I changed the translations according to your suggestions. :)

Thank you for patiently going through all the suggestions! LGTM! :)


created look up in map function

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@a979db7). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff             @@
##             develop     #152   +/-   ##
==========================================
  Coverage           ?   73.98%
  Complexity         ?     1016
==========================================
  Files              ?      145
  Lines              ?     2948
  Branches           ?      317
==========================================
  Hits               ?     2181
  Misses             ?      616
  Partials           ?      151

Impacted Files
Coverage Δ
Complexity Δ

...uk/gov/gchq/koryphe/impl/function/LookUpInMap.java
100% <100%> (ø)
5 <5> (?)

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 a979db7...1a2cbc8. Read the comment docs.


Allow manifestTransforms to be async

Library Affected: workbox-webpack-plugin, workbox-build
Feature Request Description:
I have some asynchronous tasks that I need to run in the manifestTransform function.
(Reading json file to determine dependency tree of routes that I want to precache.)
Can we add an await in front of the transform function.
https://github.com/GoogleChrome/workbox/blob/d7a7cc0ea507eeef1d64d967b0d53c7fe8b91e27/packages/workbox-build/src/lib/transform-manifest.js#L118

Yeah, I think that should be okay. I'll get that in for the next prerelease.

I've actually used patch-package to a pass the asset source to get the contents of the file generated by webpack to the transform function.
I originally thought I should be waiting for the file to get written, but that still caused issues if files from previous builds were still there.
So I added:
source: compilation.assets[asset.name].source.bind(compilation.assets[asset.name])

to
https://github.com/GoogleChrome/workbox/blob/d7a7cc0ea507eeef1d64d967b0d53c7fe8b91e27/packages/workbox-webpack-plugin/src/lib/get-manifest-entries-from-compilation.js#L165-L169
And similarly in
https://github.com/GoogleChrome/workbox/blob/d7a7cc0ea507eeef1d64d967b0d53c7fe8b91e27/packages/workbox-build/src/lib/transform-manifest.js#L82-L88
Now I'm not sure if this should be part of workbox. Looks hacky. Does not affect the contents of the generated service worker file as JSON.stringify ignores functions.


How to Update RadioListTile through controller?

How to Update RadioListTile through controller?

Hi, look for community channels on discord or telegram, they are suitable for questions.


coin_sl  and frequency never used

When the scripts load the order from the file and assigns all the variables, coin_sl is never used. Instead it uses the sl variable from config. is this correct?
Also frequency is never used.

Is this still a problem or can this issue be closed?

Is this still a problem or can this issue be closed?

Can be closed
Cheers


Add support for |> pipelines

This PR conservatively implements the Pipe operator as described in https://github.com/tc39/proposal-pipeline-operator.
Advanced features like placeholders or other features from hack are still in flux and likely to cause compatibility problems in future.

I agree with skipping placeholders and the more complex piping syntax. The goal of Civet is for features to be simple and compose well so having the simplest pipe makes sense especially since we can compose with block function syntax (i.e. &+1) to cover the majority of cases.
Looks great overall, my only recommendation is to reduce excess paren wrapping if possible.

This looks very cool! I especially like the new yield example. Could/does return behave the same way?
I feel like this feature really highlights the lack of a different feature: the ability to define functions with placeholders. For example, I imagine it's really common to want to pass a value in as a first argument of a function, with other arguments given explicitly. What we want is shorthand for ($) => func($, foo, bar).  One proposal on Discord was func((&), foo, bar), where each extra layer of parens around & pushes the function wrapper up a level.  Another option might be func(&&, foo, bar), where each additional & pushes the function wrapper up a level. The TC39 proposal suggests func(%, foo, bar).  Not sure what's best, but it kind of highlights the limitation of the current & notation... yet it feels like we're close.
Another optimization I'd like to see is that implicit functions don't actually get created.  For example, I'd like x |> &+1 to compile to x+1, not (($) => $+1)(x).  I'm not sure how far to go in this direction, but a little bit would go a long way I think.  Specifically, I think we should aim to optimize away a top-level double-arrow function (such as the one resulting from & notation).
Anyway, none of these are stopping the current PR, and I think it's fine to merge as is, but maybe we should raise these as separate issues to deal with next.

Thanks for the great PR!
Live in v0.5.11

Thanks to both of you.

implicit functions don't actually get created

I think this is a low hanging fruit here. Esp. when & is used exactly once.
Before we do the others, I think we need a better way to hygenically inject a temporary variable without potential of conflict. One common approach seems to be to have a registry of user defined/imported variables, which the parser can lookup and augment with generated temporary variables. Babel has a nice utility that is quite handy. This may need the compiler to become multipass (or atleast be more scope aware) though which was beyond what I was comfortable attempting at this point.

I believe the "ref" mechanism could serve to create temporary variables. At least, that's what it does in CoffeeScript, so I think it's one of its goals. (Not sure it's been used for that yet though. Maybe in for loops?)


Support BBolt as Go KV Metadata DB

What would you like to be added:
https://github.com/etcd-io/bbolt
Why is this needed:
The API will be small and only focus on getting values and setting values. That's it. This could also be provided as an embedded KV storage in JuiceFS by default as it would not require any external DB to be set (Redis, MySQL...) for standalone deployments providing very high portability.
If this is implemented, Backups should also be taken care: https://github.com/etcd-io/bbolt#database-backups

Oh didn't knew about Badger.


(simatec) Update UV-Protect v0.4.2

0.4.2 created 05.09.2023
OK

Github deploy failed for this release
npm notice version:       0.4.2
npm notice filename:      iobroker.uv-protect-0.4.2.tgz
npm notice package size:  23.1 kB
npm notice unpacked size: 75.8 kB
npm notice shasum:        6110d39a7138cd5af981d328[44](https://github.com/simatec/ioBroker.uv-protect/actions/runs/6082822996/job/16505987338#step:6:45)5c411d0df66598
npm notice integrity:     sha[51](https://github.com/simatec/ioBroker.uv-protect/actions/runs/6082822996/job/16505987338#step:6:52)2-/CJm0B5zQp4g9[...]CcXCeh7GQcKrA==
npm notice total files:   31
npm notice
npm notice Publishing to https://registry.npmjs.org/ with tag latest and default access
npm ERR! code E403
npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/iobroker.uv-protect - You cannot publish over the previously published versions: 0.4.2.
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.

npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2023-09-05T12_05_23_060Z-debug-0.log
Error: Process completed with exit code 1.

Please verify that the following error
You cannot publish over the previously published versions: 0.4.2.
does not indocate that an outdated code is published to npm and confirm to release 0.4.2 to stable
Please respond her and confirm that 0.4.2 at npm is ok to release

Thnks for feedback


Bad peers can DDoS fullnode

PeerBanningBehavior doesn't take into account bad peers that can send invalid HeadersPayload containing bad headers (expecially the first).
What happens in this scenario, is that a bad peer return a list of invalid headers that get passed to
PresentHeadersLockedAsync method in ConsensusManagerBehaviour that has this try/catch block
https://github.com/stratisproject/StratisBitcoinFullNode/blob/4b9dc8f9b9b4dd8d582b91e96639719c039383d0/src/Stratis.Bitcoin/Consensus/ConsensusManagerBehavior.cs#L383-L394
this.consensusManager.HeadersPresented calls this line
https://github.com/stratisproject/StratisBitcoinFullNode/blob/4b9dc8f9b9b4dd8d582b91e96639719c039383d0/src/Stratis.Bitcoin/Consensus/ConsensusManager.cs#L207
that throws the exception because of
https://github.com/stratisproject/StratisBitcoinFullNode/blob/4b9dc8f9b9b4dd8d582b91e96639719c039383d0/src/Stratis.Bitcoin/Consensus/ChainedHeaderTree.cs#L674-L678
When this.consensusManager.HeadersPresented rises ConnectHeaderException, our node try calls
await this.ResyncAsync().ConfigureAwait(false); that basically starts an infinite loop of

give me your headers
damn I haven't the first one you returned to me, let's sync again maybe i messed up something

The truth is that the rogue peer gave us at least a wrong first header. The first one headers[0] has a special meaning (it must be presented in our chain) that causes that exception.
We are now hostage of that peer.
In case the wrong hash is 2nd or further, a fork will be created but I don't think this would cause trouble because would be a legit fork with a proper proof of work linked to our previous valid block.
What I propose is to internally count these kind of behaviours and ban the peer if it generates too much consensus problem in a timeframe. If there is already this kind of process in place, then it must include this code in his "counter".

we are aware that we do not  implement any rate limits ,it has been suggested  before - https://github.com/stratisproject/StratisBitcoinFullNode/issues/722

closing as duplicate


update import csv documentation as "beta"

Import CSV is no longer going to be experimental, it will be beta. Update docs in 2.0 to reflect that.
Will also need to include the known limitations for 2.0, and how to mitigate them (using transform_only or rate limiting)

@dianasaur323, can you add the specific known limitations to this tracking issue? https://github.com/cockroachdb/docs/issues/2446

@mjibson has a lot more insight than I do, and you'll get a better answer from him. Regardless, the import csv docs should contain information on workarounds that are more specific than known limitations, so I think we should still include them here. @mjibson do you mind adding the specific known limitations to the tracking issue @jseldess linked to?

The known limitations should be added to the import page itself, I think, instead of a known limitations page. Do you still want me to add it to that issue?

I think we can add a short sentence of known limitations on the 2.0 page so that it's all in the same place, but agree that we should have all the known limitation in detail on the import page itself

@mjibson, we can use an include to display the same content in both places. But don't worry about that. You can just put it on the import page for now and let us deal with the include.

Ok. I'll document it over there then.


#17875 Make row number start with 1 in the record mode

verified

How can I get the update of my DBeaver with your update?


Escape Room Matchmaking

See Wiki page here for full details of this feature: Wiki-link

No longer needed for now.


Sound effect implementation

Use Case Description Detail:  Implementation of sound effects for the game.

Related Requirements: Existing audio files necessary for implementation.

Goal In Context: Implementing sound effects for a more immersive experience in the game.

Preconditions: Finished beta with base mechanics and menus, audio files.

Successful End Condition: The game has sound effects for the interactions and animations implemented.

Failed End Condition: The game partially shows sound effects or does not show them at all.

Primary Actors: Game developers

Secondary Actors: N/A

Trigger: The need to have sound effects activate in the game.

Main Flow:

An interaction or input happens
A sound effect plays

Extensions: N/A

Closed by PR #123


Slide in animation

Hey there, love the bar.
I had a go at doing this myself, but my CSS-foo is not great and I'm a little lost.
Trying to replicate the effect found here (look at the first alonso example).
Where, if I switch to a space to the right of the current space, then the the 'focussed' color slides to the right. Towards the new space. Likewise, the opposite if the new space is to the left, the 'focussed' color slides to the left.
Any thoughts on this? I tried toying with the CSS, and potentially adding a rotate transform to the ::after element, but I don't really know what I'm doing here.

Hi Jarvvski,
I'm afraid that without a total revamp of my SpacesDisplay layout it would be impossible to implement such a behaviour.
In the provided example, each menu item has the same width so that the line under (which is a div in absolute position) has a translate function of the current menu item selected multiplied by 100%.

Home

Gallery

Portfolio

Clients

Contact

.menu--alonso .menu__item:nth-child(3).menu__item--current ~ .menu__line {
    transform: translate3d(200%, 0, 0);
}
.menu--alonso .menu__line {
    position: absolute;
    top: 100%;
    left: 0;
    width: 120px;
    height: 2px;
    pointer-events: none;
    border: 1px solid #fff;
    border-width: 0 45px;
    background: #d94f5c;
    transition: transform 0.5s cubic-bezier(1, 0.01, 0, 1.22);
}

In our use case, each space has a variable width depending on the active apps in it. So in order to determine the current position of the indicator (the line), we would need to calculate its width and its offset from left when the user clicks on a space.
I'm not comfortable enough with Übersitch to apprehend the implementation logic of this but I certainly will give it a go in the future.
Sorry for my late answer I was enjoying my vacations away from my keyboard :)

No worries about the late answer, it's just an idea from me.
I love the bar, I'm just awful with CSS so I didn't know what was possible or not. Though I can help more with TS/JS, so let me know if I can help at all.

Thank you I'll let you know :)


Build 22631

Changes to make the DLL compatible with Build 22631.2115.

Did you test IVirtualDesktopNotification? I ask because it's not work and I have the same interface as you including the guid.
How did you find the new guid for these? Did you use OleDotNet? That did not work for me on 22621. However in IDA i was able to see some new stuff regarding remote virtual desktops. Have you heard anything about that?
[ComImport]
[Guid("B287FA1C-7771-471A-A2DF-9B6B21F0D675")]
[InterfaceType(ComInterfaceType.InterfaceIsIUnknown)]
public interface IVirtualDesktopNotification
{
    void VirtualDesktopCreated(IObjectArray p1, IVirtualDesktop pDesktop);

    void VirtualDesktopDestroyBegin(IObjectArray p1, IVirtualDesktop pDesktopDestroyed, IVirtualDesktop pDesktopFallback);

    void VirtualDesktopDestroyFailed(IObjectArray p1, IVirtualDesktop pDesktopDestroyed, IVirtualDesktop pDesktopFallback);

    void VirtualDesktopDestroyed(IObjectArray p1, IVirtualDesktop pDesktopDestroyed, IVirtualDesktop pDesktopFallback);

    //void Unknown2(int i);

    void VirtualDesktopMoved(IObjectArray p1, IVirtualDesktop pDesktop, int nIndexFrom, int nIndexTo);

    void VirtualDesktopRenamed(IVirtualDesktop pDesktop, [MarshalAs(UnmanagedType.HString)] string name);

    void ViewVirtualDesktopChanged(IntPtr pView);

    void CurrentVirtualDesktopChanged(IObjectArray p1, IVirtualDesktop pDesktopOld, IVirtualDesktop pDesktopNew);

    void VirtualDesktopWallpaperChanged(IVirtualDesktop pDesktop, [MarshalAs(UnmanagedType.HString)] string path);

    IVirtualDesktop VirtualDesktopSwitched();

    IVirtualDesktop RemoteVirtualDesktopConnected();

}

oh i forgot to remove the monitor stuff. It does work when I remove that so my interface was not exactly like yours. Anyway, I'm still curious your method of obtaining the guids and your thoughts on that new stuff for remote desktops.

I used this (Feel free to check out also the original, I don't remember but I think I used the fork linked at the start).
It can be a bit tricky to run it, especially you need to link the msdia dll (For me it worked at this path "C:\Program Files (x86)\Common Files\Microsoft Shared\VC\amd64\msdia80.dll") but it did take me a bit of time to be able to run it.
I don't know anything about the new stuff, I just tried to make the dll work with the methods that I already use when it broke, it should work for every method in the readme of the  VirtualDesktopAccessor (or so I think), but I don't know about the new things.
Feel free to ask anything more.

Thank you for the link to that repo and additional info to help get me going with it. I'll check it out.

That Python script is awesome! It does what I was doing manually using IDA Free. Thanks again for sharing.

You Welcome

Saved me a bit of googling. Thanks!

@itzjakm how did you produce the info.txt?
OleViewDotNet hasn't shown me proxy definitions for some time, it just gives me error. I think it's not working with Windows 11 or something.
I would love to know other tools about getting and iterating proxy definitions by name or by GUID, those are most valuable.


Fails to configure in git worktree

$ git worktree add ../branch
$ cd ../branch
$ ./gradlew

FAILURE: Build failed with an exception.

* What went wrong:
Could not create task ':installKotlinterPrePushHook'.
> Could not create task of type 'InstallPrePushHookTask'.
   > Not a directory

as https://github.com/jeremymailen/kotlinter-gradle/blob/4f6944a0ca8eba4573467c24c52515b5303d5772/src/main/kotlin/org/jmailen/gradle/kotlinter/tasks/GitHookTasks.kt#L40 tries to mkdirs() immediately upon configuration, but in a git worktree, .git is actually a text file that points to the shared GIT_DIR.

Thanks for the report. I wasn't familiar with the worktree feature. Is there a good programmatic way to determine you are in a worktree and resolve the correct git dir?
Is it a reasonable workaround to change to the parent git dir and install the hook from there? I assume hooks installed there apply to all worktrees.

Yes, hooks apply to all git worktrees. You can use git rev-parse --git-dir or git rev-parse --absolute-git-dir to find the .git directory. Which is probably a better thing to do anyway, there's no guarantee the Gradle root project is the same as the Git root directory.

Come to think of it, in the case that Gradle root != Git root, there might not be a good way to install the hook anyway. (For example, a repository like https://github.com/googlesamples/android-vulkan-tutorials - a repo-wide hook wouldn't know which subdirectories to run in.) So perhaps task should make sure it does nothing if git rev-parse --show-prefix or git rev-parse --show-cdup from cwd=rootProject.projectDir are successful and empty. Otherwise, creating a mostly-empty .git directory within a subdirectory (or outside of a Git working tree) is just going to confuse git and other tools.

It will still work ok, I did test it out.
The hook script is merely invoking gradle lintKotlin, which in the context of your current worktree will resolve all the sourceSets of files to check using gradle's configuration. None of that logic depends on the location of the hook script.
Try installing the hook from your parent git directory and see if the hook operates as expected for you when you are working in another worktree.

Added a note in the readme, please let me know if you run into any other issues using the hook!

The problem isn't installing the hook - I wasn't even trying to run that task. The problem is that Gradle can't even configure the project due to the task trying to mkdirs at creation time.

I see, my apologies for not seeing that detail. Not sure why I didn't run into that problem testing it.
Will investigate and fix.

Ok, actually fixed this time. Release 3.1.1.


[IMPROVEMENT] Bits collection blocks taking lots space. Try compression.

Bits collection blocks take up a lot of space. It causes an incompatibility with Immersive Portals mods (and probably others). The developer tried fixing it, but didn't fully yet.
I think compressing the block data would be a good idea. I would add compressBlock and decompressBlock methods.
The first technique that comes to mind is setting a default block type to the data so at coords that don't specify a block type, set it to that default block type. It would probably make almost all blocks instantly be much smaller. Make that default block type the most used block type per block.
I hope you add this so I can continue playing on my server with immersive portals and bits and chisels. I love both mods and want to play with both of them. Thanks.

setting a default block type to the data so at coords that don't specify a block type, set it to that default block type
No clue what you mean by this but the existing code stores an short[][][] and a String[] Palette that maps the shorts to the BlockStates it is unclear what this default block type would do. I can try to add some compression (using a byte array instead of ShortTags?) but the nature of this mod requires large NBT.

nvm


Calc ":include" should issue an error if the file is not found

I wasted a good amount of time today because I got no error, and thought there was a bug elsewhere.

One way to do this would be to add another parameter to Calc.getFileContents to throw an exception in case of "file not found" instead of just using it as an expression (but, since this is appropriate behavior on the command line, we need to the extra param for ":include" where it isn't appropriate).

Also, getFileContents only uses the charset parameter when called from :include so we could simplify the calls with another alias that just has the file name, and use the (new) three parameter version only from CalcObjectVisitor.


Allow 'openssl enc' and 'openssl dgst' to use "unknown" ciphers and digests

'openssl enc' and 'openssl dgst' use opt_md() and opt_cipher() to get
the algorithms the user asks for, which only used EVP_get_cipherbyname()
and EVP_get_digestbyname().  That would only return legacy implementations
for things the libcrypto has prior knowledge of.
To allow all provider backed algorithms to be fully used, even without
libcrypto's prior knowledge, opt_md() and opt_cipher() now also use
EVP_MD_fetch() and EVP_CIPHER_fetch(), and return them in a second
pointer that our apps has to free.  This is made in such a way that
the application can otherwise continue to use the constant EVP_MD and
EVP_CIPHER pointers.
As a discussion point, this reiterates that application must know what
they have fetched explicitly, and therefore must also free (with
EVP_MD_free() or EVP_CIPHER_free() in this case), and what they have
not (which includes all constant pointers they get from all sorts of
other functions, such as EVP_MD_CTX_md()), and therefore must NOT free.

-1
I believe this needs an OTC discussion and decision.

Er...  ok

This is an alternative to the flags approach discussed in https://github.com/openssl/openssl/pull/14182

This code doesn't look too bad (without using any flags)..

This code doesn't look too bad (without using any flags)..

Thank you, I'm glad to see you say that

Yeah, I agree with that as well.

I'm not sure it's the best approach. We get to objects instead of one (which is not a problem) and should pass the proper one downwards (which is)...

should pass the proper one downwards (which is)...

So, uhm, do you mean to say that, for example, md should not be aliased to fetched_md when an explicit fetch was performed, and that every place that uses md should be changed to (md == NULL ? md : fetched_md).  I'd say that only achieves in making the code uglier, for no gain.

Sorry, I was wrong. Yes, it's a reasonable approach.

I think this sets a bad precedent for downstream users, requiring them to complicate their code more than is really necessary. OpenSSL is already complicated, and requiring developers to track lifetimes, as opposed to adding some code to OpenSSL to make it not necessary, is the wrong trade-off in my view.  "Will nobody think of the users?" :)

I think this sets a bad precedent for downstream users, requiring them to complicate their code more than is really necessary.

It's actually not that complicated, it's a very simple "rule": if you fetch something explicitly, you must free it.  If you don't, you don't have to.  It does means that you have to keep track of the fetched pointers.
The complicating factor is when the application mixes two paradigms, which our app does.

"Will nobody think of the users?" :)

Oh I do, and I for one do not want to add fragility and corner cases that the users can't control into the library.

Since the project decided to use the proposed EVP_xxx_free semantics, this PR isn't necessary.  Please don't merge it until after #14219.

@richsalz is right.  I also wasn't the person behind the OTC hold and therefore shouldn't remove it.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

This PR is in a state where it requires action by @openssl/otc but the last update was 30 days ago

At this point, #14193 is merged, and #14219 is approved.  I see no more reason to hang on to this PR.


How to get and set  object field

How to get and set  object field
I don't know how it works in frida-il2cpp-bridge.
Why not use il2cpp_field_get_value and il2cpp_field_set_value?

You can use Il2Cpp.Field::value:
console.log("value is", yourObject.field("fieldName").value);
// change its value
yourObject.field("fieldName").value = 1234;

This is how static fields are read (il2cpp_field_static_get_value): https://github.com/vfsfitvnm/frida-il2cpp-bridge/blob/97ffc512a8a73886fa413716886327c3546c8134/src/structs/field.ts#L78
And this is how instance fields are read (via pointers): https://github.com/vfsfitvnm/frida-il2cpp-bridge/blob/97ffc512a8a73886fa413716886327c3546c8134/src/structs/field.ts#L133

How to view stack and other types like
private Stack1 projectilePool; // 0xb8`

Please give a way @vfsfitvnm


[WIP] Update Korean translation 200401

WIP - I will push a new commit when #233 is merged.

New note for validationResolver about handling error
New FAQ entries about the ternary operator and working Controller with the submitFocusError option.
New advanced usages

Custom hook with the validation resolver
Working with the visualized list

thanks very much @adhrinae

@bluebill1049 I updated PR including Controller#onFocus. Please check and merge this. 🙌

awesome! thank you very much merge!


Convert all state management to go through sled

As described in the bpfman damonless design doc
we would like to move all our state persistence to an in memory db, for that we've chose to use sled.
I'll break this up into three big chunks:

[x] Setup + Image Manager -> https://github.com/bpfman/bpfman/pull/861
[x] Core Program Type -> https://github.com/bpfman/bpfman/pull/874
[x] XdpDispatcher -> https://github.com/bpfman/bpfman/pull/901
[x] TCDispatcher

This is done!!! 🥳


Refactor audio message to Dialogue Utterance

This is the first of several mini-PRs that will cover the changes proposed in https://github.com/PTG-Kitware/angel_system/pull/378
We should remove the previously used messages upon confirmation of working implementation.

@derkmed can you rebase on the latest master?

@derkmed Is this relevant anymore with the more recent PR of yours (https://github.com/PTG-Kitware/angel_system/pull/418) having landed?


make slide entries collapsible and draggable

This pull request makes the individual slide entries collapsible and draggable. When adding a new slide, all other slides collapse, significantly reducing the amount of scrolling to reach the Add Slide button to create another slide. When dragging, there is a blue placeholder showing where the slide will be dropped
The Slide Duration and Slide Transition Speed inputs were changed from text to number.
Closed Slides

Open Slide

Drag Placeholder

I believe there is an existing upgrade script for the Image Slider block:
https://github.com/concrete5/concrete5/blob/develop/web/concrete/src/Updater/Migrations/Migrations/Version20151221000000.php#L27-L30

Thanks!


Rebase to 1.0.1

Rolled back to v1.0.1 (openshift/master was newer)
Added OWNERS and DockerFiles

Diff to upstream v1.0.1: https://github.com/kubernetes-csi/cluster-driver-registrar/compare/v1.0.1...jsafrane:rebase-1.0.1
(check the changed files, dunno why is list of commits so long)

cc @openshift/storage

/lgtm


The '__static' dose not work when build a 'app.asar'

Sorry about that,but it really made me wonder. I tried using the '__static' to open a 'grgzpt.exe' in my project.
In the 'build.config.js',if I set 'asar:true',there is a 'app.asar' in the resourse folder after I built the project with 'npm run build:win32', and then i run the application, the 'grgzpt.exe' can not be opened. But if I set 'asar:false',it worked well.
What can I do?
Thanks!

@lianshengxing
This is expected behavior in electron and is also touched in electron-vue documentation. The native OS cannot read files within an asar archive, therefore grgzpt.exe cannot be started. In conclusion, it is safe to set asar: false, but you will lose small optimizations because of that. Aside from that, there isn't really another workaround.

Please note that in production all files are packed with asar by default as it is highly recommended. Because of this, assets within the static/ folder can only be accessed within electron since it is aware of this behavior. So if you are planning to distribute files to your users, that can for example open in a external program, you would first need to copy those assets from your application into the user's document space or desktop. From there you could use the shell.openItem() electron API to open those assets.

https://simulatedgreg.gitbooks.io/electron-vue/content/en/using-static-assets.html

Thanks a lot for that.
When I use the 'electron-builder',which config should i change to build an application for 'win32-ia32' on the '×64' platform

Another error when I use the 'electron-builder'
'Error: C:\Users\69063\AppData\Local\electron-builder\cache\nsis\nsis-<IP_ADDRESS>\Bin\makensis.exe exited with code 1
Output:
Command line defined: "APP_ID=org.simulatedgreg.electron-vue"
Command line defined: "APP_GUID=62e3eecb-e013-549b-8222-3caf500ba8f3"
Command line defined: "PRODUCT_NAME=personal-platform"
Command line defined: "PRODUCT_FILENAME=personal-platform"
Command line defined: "APP_FILENAME=personal-platform"
Command line defined: "APP_DESCRIPTION=An electron-vue project"
Command line defined: "VERSION=0.0.0"
Command line defined: "PROJECT_DIR=D:\lian\�����й���Ŀ\grgzpt-s"
Command line defined: "BUILD_RESOURCES_DIR=D:\lian\�����й���Ŀ\grgzpt-s\build"
Command line defined: "COMPANY_NAME=lshx"
Command line defined: "MUI_ICON=D:\lian\�����й���Ŀ\grgzpt-s\build\icons\icon.ico"
Command line defined: "MUI_UNICON=D:\lian\�����й���Ŀ\grgzpt-s\build\icons\icon.ico"
Command line defined: "APP_64=D:\lian\�����й���Ŀ\grgzpt-s\build\personal-platform-0.0.0-x64.nsis.7z"
Command line defined: "APP_64_NAME=personal-platform-0.0.0-x64.nsis.7z"
Command line defined: "COMPRESSION_METHOD=7z"
Command line defined: "ONE_CLICK"
Command line defined: "RUN_AFTER_FINISH"
Command line defined: "MULTI_LANGUAGE_INSTALLER"
Command line defined: "COMPRESS=auto"
Command line defined: "BUILD_UNINSTALLER"
Command line defined: "UNINSTALLER_OUT_FILE=C:\Users\69063\AppData\Local\Temp\electron-builder-YPJBp7\0-1-uninstaller.exe"
Processing config: C:\Users\69063\AppData\Local\electron-builder\cache\nsis\nsis-<IP_ADDRESS>\nsisconf.nsh
Processing script file: "" (ACP)
Error output:
!include: could not find: "UAC.nsh"
!include: error in script: "multiUser.nsh" on line 2
Error in script "" on line 10 -- aborting creation process'


Improve style ui

fixes #161
fixes #162
fixes #163

[x]  Remove hover effect in link and button
[x]  Improve nav bar style: please see the screen below. I removed the full grey box and just change the color of the text to grey.

Hi, @ricardogsilva I've added ticket #161 in this PR as well.

[x] Space between background and the tabbed contents

[x] Private label on right

[x] Improve page style


Enforce ordering of items in schemas and lenses during BindLineage

#173 removed certain native CUE logic that sorted lenses and schemas in a lineage into a known order. To replace this, we need to add checks to BindLineage() that enforce ordering invariants on the raw lineage inputs.

@undef1nd this is the one you were aiming to pick up, right?

Yes, I think it's one of those errors handling improvements you suggested.


Bug (PIP gets killed on Refresh)

After the recent update pip window gets killed on refresh
checked on Chrome Version 127.0.6533.89 and Brave and other Chromium-based browsers
Steps to reproduce

Lauch PIP window
Refresh the same window and the pip window gets killed

@abhishek227 Thank you for your report. Unfortunately, with manifest version 3, there's no way to create pip window in extension's own context.
I've reported this issue 6 month ago but it's still not fixed and surprisingly MV3 deprecation has been started.
Please see this ticket and vote if you are uncomfortable with this limitation.
https://issues.chromium.org/issues/326889650


[builder] improve unit tests

Changes:

Add additional unit tests and fix one small bug found by those new tests
Enable coverage to be collected more easily, by running tests in a single process (i.e., change to Dask cluster config for tests)
Run with and without Numba JIT, to fully capture coverage and continue testing in the as-used mode (numba enabled).
Reduce memory budget for consolidation to allow testing in small instances (does not affect normal Census build)
Additional unit tests to cover float precision reduction in more detail
Update to latest tiledbsoma version
Fix bug in HVG uncovered by enabling categoricals in the Census build

This should significantly increase Builder coverage (some due to new tests, some due to more accurate code coverage)

@ebezzi @prathapsridharan - given the HVG fix in this PR, you may want to consider pushing a patch release once this lands.


Replace CheckBoxPreference to SwitchPreference

Revamp the Settings Page.
Fix to issue #1039
Replace CheckBoxPreference to SwitchPreference.
Previously discussion #1094
Screenshot:

======
Titles (Appearance, General, Feedback) should be at the same size with other font (or a little bigger).
I think it is default.
Give me some links so that I can get for "Separators would be nice between each parts."

This PR has also conflicts, you need to solve them so that I can merge it after reviews are done.

Please re-open it if you decide to solve conflicts:)

Please re-open it if you decide to solve conflicts:)

I think there's already another PR that fixed the same issue that this one tries to address: #1259

Oh, thanks for remind @sivaraam . Our merge cycle is very fast todays. So, yes we can't re-open this one.


Vendor wax

Description
This vendors wax until our PR is accepted upstream. It applies two small additional patches, which are included as separate commits.
Testing Instructions
cargo test --workspace

Will merge once tests are passing


Check In/Check Out - Rules

Definition of Ready

[x] Does this meet the INVEST criteria?
[x] Does this have a clearly defined user?
[x] Does this have an estimate?
[x] Does this have acceptance criteria?
[x] Does this have sufficient context (wireframes, business rules, etc.)?
[x] Is this traceable to a feature, epic, or PI?

User Story
As a User
I want Check In/Check Out process for the Monitoring Plans to be streamlined
So that I understand when my updates to the Methods data will be saved and Checked In
Acceptance Criteria
Given a user checked out a Monitoring Plan
And viewed/updated the Methods data and Saved them
When the user closes the Methods tab without Checking back in
Then the system automatically checks in the MP with any saved updates
Given a user checked out a Monitoring Plan
And viewed/updated the Methods data and Saved them
When the user closes the Browser without Checking back in
Then the system automatically checks in the MP with any saved updates
Given a user checked out a Monitoring Plan
And made edits to the Methods data
When the user cancels the edits/closes the modal
And closes the Methods tab
Then the system automatically 'checks back in' the MP
Given a user checked out a Monitoring Plan
And made edits to the Methods data
When the user closes the Browser (Chrome/Firefox/Edge.....) without Saving
Then the system checks back in the MP automatically without saving the updates
Does this Story require 508 Testing?

[ ] Implementing a new authoring tool that will produce code / content for the application
[ ] Implementing a 3rd party widget that will be part of the application
[ ] Adding new / updating custom functionality
[ ] Adding new / updating a page template
[ ] Adding new / replacing existing functionality (unless the replacement has already passed 508 testing)
[ ] Full Site Review prior to a scheduled EPA 508 review
[ ] Planning a video that will appear on the application
[ ] Producing a video that will appear on the application
[ ] Producing Training materials
[ ] Producing documents

Context
(User journeys, design mockups, architectural diagrams, business rules, data element definitions)
Testing
Test Case: TC316
Tester: @mosesdeeCVP
Definition of Done

[x] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[x] Has the code been unit tested and peer reviewed?
[x] Have the functional tests been executed?
[x] Have all defects been reviewed and dispositioned, resolved, or deferred?
[x] Has the user story been accepted by the Product Owner?
[x] Is the user story ready to be deployed to the test/staging environments?

Test Passed


Panel data stored in memory for subsequent requests

It looks like all of the data is stored in process memory here, and then fetched in subsequent requests from the browser. This works fine locally but obviously breaks in a multi-process environment. While obviously this shouldn't be used in production, we would love to be able to run the toolbar on our staging environment to see realistic query plans more easily.
What if we moved the _store into a singleton class that determined which type of storage to use from a setting? We could default to an OrderedDict but allow custom overrides to use any storage type. I am thinking that we would use django cache so I could commit that storage if you would like.

I'm afraid the data isn't pickleable in general, which means you can't put it in a Django cache easily.

Ahh, that is too bad. Would it just be more work to make the panels serializable or do features depend on having the exact same python instances?

It's essentially outside of the toolbar's control.
The template panel, which is arguably one of the most useful panels, keeps track of the template rendering context, where developers may put arbitrary Python values. It would be annoying if the toolbar failed randomly depending on what a particular view puts in the context...
Generally speaking, being a debug tool, the toolbar has to be extremely resilient to whatever a developer may throw at it and it cannot make assumptions about things it handles.


feat(webapp): updates login.jsx, created auth.js and userData.js

updates login.jsx, created auth.js and userData.js for JWT authentication, needs improvement

LGTM


Report Retry-After header support

Apparently some browsers support the exciting Retry-After HTTP header:
https://tools.ietf.org/html/rfc7231#section-7.1.3
https://stackoverflow.com/questions/3764075/retry-after-http-response-header-does-it-affect-anything
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After
It's not obvious which one do at this stage.

Entry available via MDN: https://caniuse.com/mdn-http_headers_retry-after
Needs data though…


feat: update multiple values

Codecov Report
Attention: Patch coverage is 94.28571% with 2 lines in your changes missing coverage. Please review.

Project coverage is 89.31%. Comparing base (969153a) to head (00976cc).

Files
Patch %
Lines

src/lua_binding/mod.rs
90.90%
1 Missing :warning:

src/store/stmt.rs
83.33%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #157      +/-   ##
==========================================
+ Coverage   89.24%   89.31%   +0.07%
==========================================
  Files          15       16       +1
  Lines         948      964      +16
==========================================
+ Hits          846      861      +15
- Misses        102      103       +1

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


IGNITE-9657 Fix socket leak in TcpDiscoverySpi

The ticket is resolved, closing PR.
Please close PRs for your resolved tickets and other non-needed PRs.
Alternatively, ask a committer

to use GitHub UI (committer  can associate accounts here: https://gitbox.apache.org/setup/ )
or /scripts/apply_pull_request.sh from Apache Ignite source.
or mention in commit message 'Fixes #(a number of PR)'.

These methods will automatically close PR.
Feel free to reopen this PR if it is actual.


No Pokemon getting released

Expected Behavior
My BOT won't release any Pokemon.
Actual Behavior
Your FULL config.json (remove your username, password, gmapkey and any other private info)
http://pastebin.com/Nkfx0mvg
Output when issue occurred
No output cause no Pokemon get released.
Other Information
OS: Raspbian
Branch: dev
Python Version: Python 2.7.9
Any other relevant files/configs (eg: path files)

okay, the bot release pokemon if the bag is full, can be closed i think


GazeProvider Start() visibility to protected for derived providers

Overview
Broadened visibility for Start() to allow derived providers to add e.g. a GazeFuse to the DefaultCursor after init.

Should this have been changed to protected virtual?


add aaron as author to fb-support

Coverage remained the same at 100.0% when pulling 231e402c4d17086be84d9adfd2934dc045272f8a on gem_authors into 9e51445ecb5c85c6e3a92ddab3bd163407282847 on master.