[FR] add alternative map api

I don't think depending on Google to get map data would ensure this app's 'privacy-first' motto for a lot of people. I would suggest providing an alternative to it or if possible replace it with an open source alternative provider like OpenStreetMap.
If I am not wrong the app usages map API for showing overlap and developed using NodeJS. You might want to take a look at Leaflet JS. Though the OpenStreetMap tile server are forbids heavy usages due to it being run on a donated resource (more details here at tile usages policy), you can use Mapbox's vector or raster tiles which has a more reliable service at a reasonable pricing.
Thanks in advance!

I asked in the Telegram group: OpenStreetMap Dev and got the suggestion for StadiaMaps. See the docs and pricing. Hope this helps!

I doubt there will be any move away from Google as an ex-Google executive is part of the core team here. (I also suggested to not have the app be dependent on using the Play Store... )
But I completely agree with you, when it comes to this simple application, OSM is superior an far easier and lighter to use than G maps. It also show way better details and sensible graphics when it comes to buildings etc. (Aaaand doesn't require you to update your map every week...)

No longer part of Safe Paths.


Edit function

edit function

Coverage decreased (-0.02%) to 66.75% when pulling 6c4a51759814f689016f8aa230e21ce6233a839b on hndrk15:dev into 8742f74d14d78eca95f42627ec8337d39fa228ed on danliris:dev.

Coverage decreased (-0.02%) to 66.75% when pulling 94f995b14b28e2d03c544550fa2fe9105611d0f5 on hndrk15:dev into 8742f74d14d78eca95f42627ec8337d39fa228ed on danliris:dev.

Coverage decreased (-0.02%) to 66.75% when pulling 119c0f2ca6a54909e531f76d029624665f2ad481 on hndrk15:dev into 8742f74d14d78eca95f42627ec8337d39fa228ed on danliris:dev.

menggunakan modul lama


Accessing window.localStorage causes SecurityException on ios private browsing

Do you want to request a feature or report a bug?
Bug
What is the current behavior?

Start with an iphone device, a react.js website created using create react app that uses amplify.
Use the built in Safari browser to navigate to the website
Turn on private mode browsing, (which will cause a security exception whenever someone calls window.localStorage)

The source of the problem appears to be CacheUtils which access window.localStorage in it's default exports.
I get a crash on aws-amplify/lib/Cache/Utils/CacheUtils.js line 25.
exports.defaultConfig = {
keyPrefix: 'aws-amplify-cache',
capacityInBytes: 1048576,
itemMaxSize: 210000,
defaultTTL: 259200000,
defaultPriority: 5,
warningThreshold: 0.8,
storage: (typeof window === 'undefined') ? null : window.localStorage  //<< blows up here
};
This is incredibly hard to work around on my end as it blows up the webpack loading of the site.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than AWS Amplify.
Bug as the exception means I get a blank page for my website.
What is the expected behavior?
That it loads with warning that local storage is not available and logins might expire?
Which versions of Amplify, and which browser / OS are affected by this issue? Did this work in previous versions?
"dependencies": {
"aws-amplify": "^0.2.14",
"aws-amplify-react": "^0.1.38",
You can turn on the debug mode to provide more info for us by setting window.LOG_LEVEL = 'DEBUG'; in your app.

The way iOS safari treats local storage in private mode is a bit different than other browsers. I'll make a fix soon.

@richardzcode Thanks!! :)


Something similar to cache-first for Apollo and Urql?

Coming from Apollo or Urql I would like to know if there is a way to mimic (or improve) the behavior of policies like "cache-first":

(the default) prefers cached results and falls back to sending an API request when no prior result is cached: https://formidable.com/open-source/urql/docs/basics/document-caching/#request-policies.

An example: I already have user data queried in Home page then I navigate to User page and I wanna say to svelte-query to NOT query again my user data because I already have them in cache (with Infinite stale).
Am I wrong to want this?
I tried with the enabled option but obviously if navigate on the user's page before the Home page the query does not start at all.
How to do?

I think you can use Initial Query Data in this case: https://sveltequery.vercel.app/guides/initial-query-data


ci: use macos 11

Related to https://github.com/actions/virtual-environments/issues/5583

I triggered a build on demand to check if it causes any problems in a release-like job: https://github.com/camunda/camunda-modeler/actions/runs/2716689060


Weird behaviour of random seed for initialization

I observed a few things about random seeds depending on where they're declared in the code; I want to know why that happens.. I'm using "he_normal" initialization for initializing the weights in all my convolution layers. As we know with "he_normal", the size of the filter determines the variance of the normal distribution used, and the seed determines how the weights are sampled from that distribution.
I observe different behaviours based on where I initialize my seed.
The first case:
import numpy as np
np.random.seed(2016)
import keras

# all other keras imports follow after this.

Above, I first import numpy, then set the seed , followed by all keras imports. The result I get from my network is reproducible when I use the same seed, and changing seeds gives different results. This is as expected.
The second case:
import numpy as np
import keras
np.random.seed(2016)

# all other keras imports follow after this.

The only change between first and second case is, the seed initialization is now after the import keras line. So the sequence is, import numpy, then do import keras , then initialize seed, which is followed by all other keras imports. Here also the seed works fine, I get reproducible results for the same seed and different results for different seeds.
But, for the same seed, the above two cases give different results! That is, assume the seed is "x" , I get some result for the first sequence , but I get a different result for the second sequence for the same seed "x".
The seed I set is taking effect, but it works differently when I set the seed before import keras or after import keras . In both cases, reproducibility is ensured for same seed , so I know the seed is doing what its supposed to do, but it is doing so differently based on the position of import keras.
Without setting any seed, I get different results every run, which is expected. Its just that setting the seed with two different import sequences is giving differently reproducible results.
Has anyone faced this? Why are these two cases performing correctly , yet differently ?

[x] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps

[x] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[ ] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

Those produce different results because Keras generates random numbers somewhere during import. The convention used in the Keras example scripts is to put the seed before all Keras imports - that way those random numbers will also be reproducible.


Slight message change

Problem:

Missing word
Solution:

Added word
Result:

Message contains previously missing word

@maffe Thanks!


Document the modular json serialization

https://github.com/quantumlib/Cirq/pull/3539 introduced modular json serialization test infrastructure. We (I) should document it in docs/dev/serialization.md.

This was resolved by #4397.


Clicking on an icon does not show user info

Subject: Clicking on an icon does not show user info
Description:
Using the map (chrome, mac), I click on a location item, but the side panel does not update. I don't know who's at that dot.
Thing to consider 1: I do have a sidebar filter on for "Can Host"
Thing to consider 2: My location is set to "Dublin, Ireland" but I've moved the map around to different cities in Ireland and am clicking on those hosts
Results:
I was expecting the sidebar to update to show me who I've selected
Backend version: develop-7c33e18d
Frontend version:
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/search?location=Dublin%2C+Ireland&lat=53.3497645&lng=-6.2602732&hostingStatusOptions=2#loc=12/51.88422/-8.43882
User: willow (11804)

dupe #3336?


[Grid] Need class to make columns without space between

Hello! Many thx for ur awesome grid system.
To make it even better, please add CSS class for make Semantic UI grid columns without spaces.
What I mean:

And this code result should look like this:

AND / OR

And this code result should look like this:

AND / OR

            ...

            ...

And this code result should look like this:

This class really helps us (SUI designers) to create beautiful web pages like this and don't overwrite default classes in semantic.css file:

Columns use padding for spacing, which means background is not affected by gutters. Gutters will just prevent text content from running up against other text content.
In cases where you want 100% stretched images use background with cover.
http://jsfiddle.net/u6r6eLbf/

Thank you for solution!
But I mean a little bit more.. As example, let's imagine a site with such a design:

Ready layout with content should be similar to:

Code for this like:

	...

The  cells can not only be a background picture, and text or anything.
I understand that such an additional CSS class for such a small chip — it's too difficult, but it is really will facilitate and accelerate development of projects in SUI.

The case for text padding is still the same regardless of layout complexity
http://jsfiddle.net/9e231xm8/
Any image that's full width should be set as background-image. One of the difficulties with maintaining a library is deciding whether an addition would add complexity or remove it, and unfortunately in this case I think it will add complexity and increase the chance for improper usage (having columns where text between columns run up against each other).

I'm curious why this feature won't be added? While evaluating various front-end frameworks, being able to remove or specify grid gutter size via CSS classes is a feature I would like. Looking at the other major frameworks, Bootstrap, UI-Kit and Foundation this is possible.
https://v4-alpha.getbootstrap.com/layout/grid/#no-gutters
https://getuikit.com/v2/docs/grid.html#grid-gutter
http://foundation.zurb.com/sites/docs/grid.html#gutters

@jlukic Can this be re-opened and re-considered?

I'd love to see this feature added. I know I've used Bootstrap's gutter options in the past... and not for lining up background images.

Am experiencing same issue.

+1

This is obviously a needed feature. Text and/or images are not the only things that go into grids. There are plenty of cases when one needs a grid for aligning elements that regulate their own padding.

@jlukic This feature is required. Here is why:
It's obvious that we can't completely separate HTML and CSS from each other. But we can loosely couple them through the class attribute. Using (inline) CSS within the markup (style attributes or tags) on the other hand makes the coupling more tight.
In larger projects you have often different teams for the front and the back. Their contract is mostly the markup. So the team for the back has only to ensure the HTML fits the specs and the "compiled" resource packages from the front team is also delivered and the job is done.
But what if the back team also have to generate CSS dynamically? The development process  become more complicated because of narrowing areas of responsibility of both teams, which will be the case if you have to use provide a gutter-less grid for images which are not part of the static resources of the front team but some content which has to be generated dynamically; this whole scenario becomes even more complicated when you have to provide responsive images (srcset). Because the suggested approach is to use background-image (with media queries). Sure it is possible and trivial to implement but from a organizational point of view it's getting more complicated as it has to be. Because you have to start generating CSS dynamically, and thus this stuff is also distributed over several partitions (e.g. some static resources from the front team and some code in any CMS of your choice) and each of this partitions is managed by another team.
So the most easiest approach in such scenarios are compact grids to still provide good practice and approved methods regarding separation of concerns in this area. This is why other frameworks often provide such a feature (imo).

Need this future either...

Also need this.

Also need this


[CI] Tensorflow 2.3.1 upgrade blocker

Followup of https://github.com/apache/incubator-tvm/pull/6706 Some updates in TF and TFLite are needed to enable TF 2.3.1 support
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/ci-docker-staging/28/pipeline/320

The failures are resolved in #6774

@tqchen I think this can be closed now

Sorry, too early to claim it is completely fixed :(. I just checked again and there was another side effect, this time on Keras testing.
 Apparently it is not fixed yet.
@ANSHUMAN87 are you able to reproduce this issues when running frontend tests?

@leandron : Sure i will look into it. Can you please confirm whether keras version in ur env is 2.3.1 ?

@ANSHUMAN87  - we just use the same Docker image as upstream ci_cpu,so it would be the version as in ubuntu_install_tensorflow.sh . So I think it's keras 2.3.1
install/ubuntu_install_tensorflow.sh:pip3 install tensorflow==2.3.1 keras==2.3.1 h5py

Yes, I confirm as per https://github.com/apache/incubator-tvm/blob/main/docker/install/ubuntu_install_tensorflow.sh and also but checking the installation logs.

Okay, i checked the failures, we have to upgrade the keras version too, along with it. Will raise one PR for it now.

I confirm now all the issues are gone.

Thanks @leandron for confirmation!

Note that the keras related issues still persists

Still having problem https://ci.tlcpack.ai/job/temp-ci-docker-staging/job/ci-stage2/25/execution/node/408/log/

seems was due to https://github.com/apache/incubator-tvm/pull/6808/ changes to keras 2.3.1

Still having problem https://ci.tlcpack.ai/job/temp-ci-docker-staging/job/ci-stage2/25/execution/node/408/log/

From this error. It seems your are missing #6793, and also needs #6808 on top. This works for me.

So, you need #6810 and #6808 on your ci branch, then according to my tests, all is working.


Change branch instruction in CH10 move_enemies proc

The current branch instruction will prevent the move_enemies procedure from completing correctly. The instruction is correct in CH11, but CH10 is not playable when compiled.
Expected: enemies to advance towards bottom of screen
Actual: enemies do not advance
To reproduce: compile and run megablast.nes in CH10 from the main branch
To verify fix: compile and run megablast.nes in CH10 from this branch

Thank you Aaron


Let us choose the auth type

As written in the title, It is required for me to use not bearer authentication but SAS authentication (which is directly in the URL, not in a header)
I'm getting

when trying to use the button because it always sends a bearer token:

Would it be possible to add that?

I'll add it

There is a new configuration field which is for setting the default bearer token. by default it is true (to not break backwards compatibility), so you'll have to manually set it to false.

sorry for the inconvenience, there have been some bugs


[Comb] Add helper functions for creating text protos

Keyword Check:
~/sonic-buildimage/src/sonic-p4rt/sonic-pins$ ~/tools/keyword_checks.sh .
Keyword check Passed.
Build Result:
/sonic/src/sonic-p4rt/sonic-pins$ bazel build $BAZEL_BUILD_OPTS ...
INFO: Analyzed 584 targets (0 packages loaded, 0 targets configured).
INFO: Found 584 targets...
INFO: From Compiling tests/lib/switch_test_setup_helpers.cc:
In file included from tests/lib/switch_test_setup_helpers.cc:11:
tests/lib/switch_test_setup_helpers.cc: In function 'absl::lts_20230802::StatusOr<std::unique_ptrpdpi::P4RuntimeSession > pins_test::{anonymous}::CreateP4RuntimeSessionAndClearExistingState(thinkit::Switch&, const pdpi::P4RuntimeSessionOptionalArgs&)':
tests/lib/switch_test_setup_helpers.cc:29:25: warning: 'absl::lts_20230802::Status pdpi::ClearTableEntries(pdpi::P4RuntimeSession*)' is deprecated: Use ClearEntities instead. [-Wdeprecated-declarations]
29 |   RETURN_IF_ERROR(pdpi::ClearTableEntries(session.get()));
|                         ^~~~~~~~~~~~~~~~~
./gutil/status.h:283:30: note: in definition of macro 'RETURN_IF_ERROR'
283 |   for (absl::Status status = expr; !status.ok();)
|                              ^~~~
In file included from ./tests/lib/switch_test_setup_helpers.h:14,
from tests/lib/switch_test_setup_helpers.cc:1:
./p4_pdpi/p4_runtime_session.h:390:14: note: declared here
390 | absl::Status ClearTableEntries(P4RuntimeSession* session);
|              ^~~~~~~~~~~~~~~~~
In file included from tests/lib/switch_test_setup_helpers.cc:11:
tests/lib/switch_test_setup_helpers.cc:29:56: warning: 'absl::lts_20230802::Status pdpi::ClearTableEntries(pdpi::P4RuntimeSession*)' is deprecated: Use ClearEntities instead. [-Wdeprecated-declarations]
29 |   RETURN_IF_ERROR(pdpi::ClearTableEntries(session.get()));
|                                                        ^
./gutil/status.h:283:30: note: in definition of macro 'RETURN_IF_ERROR'
283 |   for (absl::Status status = expr; !status.ok();)
|                              ^~~~
In file included from ./tests/lib/switch_test_setup_helpers.h:14,
from tests/lib/switch_test_setup_helpers.cc:1:
./p4_pdpi/p4_runtime_session.h:390:14: note: declared here
390 | absl::Status ClearTableEntries(P4RuntimeSession* session);
In file included from tests/forwarding/fuzzer_tests.cc:40:
tests/forwarding/fuzzer_tests.cc:422:66: warning: 'absl::lts_20230802::StatusOr<std::vectorp4::v1::TableEntry > pdpi::ReadPiTableEntries(pdpi::P4RuntimeSession*)' is deprecated: Prefer ReadPiEntities instead. [-Wdeprecated-declarations]
422 |                            pdpi::ReadPiTableEntries(session.get()));
|                                                                  ^
./gutil/status_matchers.h:64:43: note: in definition of macro 'ASSERT_OK_AND_ASSIGN'
64 |   auto __ASSIGN_OR_RETURN_VAL(LINE) = expression;
|                                           ^~~~~~~~~~
In file included from ./lib/gnmi/gnmi_helper.h:41,
from tests/forwarding/fuzzer_tests.cc:42:
./p4_pdpi/p4_runtime_session.h:360:49: note: declared here
360 | absl::StatusOr<std::vectorp4::v1::TableEntry> ReadPiTableEntries(
|                                                 ^~~~~~~~~~~~~~~~~~
tests/forwarding/fuzzer_tests.cc:551:23: warning: comparison of integer expressions of different signedness: 'int' and 'std::vectorp4::v1::WriteRequest::size_type' {aka 'long unsigned int'} [-Wsign-compare]
551 |     for (int i = 0; i < batched_clear_requests.size(); i++) {
|                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
INFO: Elapsed time: 43.667s, Critical Path: 35.29s
INFO: 28 processes: 2 internal, 26 linux-sandbox.
INFO: Build completed successfully, 28 total actions
Test Result:
/sonic/src/sonic-p4rt/sonic-pins$ bazel test $BAZEL_BUILD_OPTS --cache_test_results=no ...
INFO: Analyzed 584 targets (0 packages loaded, 154 targets configured).
INFO: Found 394 targets and 190 test targets...
INFO: Elapsed time: 201.049s, Critical Path: 114.44s
INFO: 244 processes: 289 linux-sandbox, 18 local.
INFO: Build completed successfully, 244 total actions
//gutil:collections_test                                                 PASSED in 0.5s
//gutil:io_test                                                          PASSED in 0.6s
//gutil:proto_matchers_test                                              PASSED in 0.6s
//gutil:proto_ordering_test                                              PASSED in 0.6s
//gutil:proto_test                                                       PASSED in 0.5s
//gutil:status_matchers_test                                             PASSED in 0.6s
//gutil:test_artifact_writer_test                                        PASSED in 0.7s
//gutil:testing_test                                                     PASSED in 0.5s
//gutil:timer_test                                                       PASSED in 5.1s
//gutil:version_test                                                     PASSED in 1.5s
//p4rt_app/tests/lib:app_db_entry_builder_test                           PASSED in 0.0s
//p4rt_app/utils:event_data_tracker_test                                 PASSED in 0.0s
//p4rt_app/utils:table_utility_test                                      PASSED in 0.8s
//sai_p4/instantiations/google:clos_stage_test                           PASSED in 0.5s
//sai_p4/instantiations/google:fabric_border_router_p4info_up_to_date_test PASSED in 0.0s
//sai_p4/instantiations/google:middleblock_p4info_up_to_date_test        PASSED in 0.0s
//sai_p4/instantiations/google:sai_nonstandard_platforms_build_test      PASSED in 0.2s
//sai_p4/instantiations/google:sai_nonstandard_platforms_cc_test         PASSED in 0.6s
//sai_p4/instantiations/google:sai_p4info_fetcher_test                   PASSED in 0.8s
//sai_p4/instantiations/google:sai_p4info_test                           PASSED in 1.2s
//sai_p4/instantiations/google:sai_pd_proto_test                         PASSED in 0.1s
//sai_p4/instantiations/google:sai_pd_util_test                          PASSED in 0.7s
//sai_p4/instantiations/google:tor_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google:union_p4info_up_to_date_test              PASSED in 0.1s
//sai_p4/instantiations/google:wbb_p4info_up_to_date_test                PASSED in 0.1s
//sai_p4/instantiations/google/test_tools:table_entry_generator_helper_test PASSED in 2.6s
//sai_p4/instantiations/google/test_tools:test_entries_test              PASSED in 0.9s
//sai_p4/instantiations/google/tests:p4_fuzzer_integration_test          PASSED in 4.3s
//sai_p4/tools:p4info_tools_test                                         PASSED in 0.6s
//sai_p4/tools:packetio_tools_test                                       PASSED in 0.8s
//tests/qos:gnmi_parsers_test                                            PASSED in 0.0s
//tests/qos:gnmi_parsers_test_runner                                     PASSED in 0.0s
//thinkit:bazel_test_environment_test                                    PASSED in 0.7s
//thinkit:generic_testbed_test                                           PASSED in 1.0s
//thinkit:mock_control_device_test                                       PASSED in 1.1s
//thinkit:mock_generic_testbed_test                                      PASSED in 0.7s
//thinkit:mock_mirror_testbed_test                                       PASSED in 0.6s
//thinkit:mock_ssh_client_test                                           PASSED in 0.0s
//thinkit:mock_switch_test                                               PASSED in 0.7s
//thinkit:mock_test_environment_test                                     PASSED in 0.1s
//thinkit:switch_test                                                    PASSED in 0.7s
//sai_p4/instantiations/google/tests:p4_constraints_integration_test     PASSED in 0.8s
Stats over 5 runs: max = 0.8s, min = 0.7s, avg = 0.7s, dev = 0.1s
//sai_p4/instantiations/google/test_tools:table_entry_generator_test     PASSED in 43.4s
Stats over 50 runs: max = 43.4s, min = 0.8s, avg = 2.7s, dev = 8.3s
Executed 190 out of 190 tests: 190 tests pass.
INFO: Build completed successfully, 244 total actions

Co-authored-by: Srikishen Pondicherry Shanmugam<EMAIL_ADDRESS>


Reopening vscode should preserve state of path on terminal

I use mutiple terminals all the time. When I close vs code and open it again, the files (Open editors) are opened but this does not seem to be the case with terminal path. All my terminals are opened but the path is reset to the root folder path.
Suppose I have 3 terminals opened right now:
A: c:/path/to/root/folder
B: c:/path/to/root/folder/subfolder_1
C: c:/path/to/root/folder/subfolder_2
And I closed vs-code. When I reopen vs-code, the terminal path is reset as:
A: c:/path/to/root/folder
B: c:/path/to/root/folder
C: c:/path/to/root/folder

Heyy @Tyriar, Any update on the issue?

This will only work if you have shell integration enabled as it's not possible to query shells for their cwd from other processes on Windows. Do you have these blue circles next to your terminal?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Fixes missing replies in thread

Summary
Currently we fetch updated thread items (not replies) from all teams upon reconnection,
so we have to assume that we always have updated reply counts stored.
However if a thread has already some replies stored in the browser when we open the thread
we fetch only newer replies than the last, this leads to missing messages when a post gets edited.
This commit fetches whole thread replies if counts have a difference (like we used to),
or fetches newer replies when counts are the same.
Ticket Link
Release Note
Fixes a bug where replies appear missing in threads

/e2e-tests

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/197640

E2E cycle failed, checking on git and restarting. Will approve after report posts.

Thanks @koox00
Tested, looks good to merge.

Verified thread reply count (repro steps shared in channel)- as expected
E2E report looks good, no PR related failures.
Ticket created to track testing after merge https://mattermost.atlassian.net/browse/MM-44519

@amyblais I did not add fix version. Will this go in v7?

FWIW the code that introduced the bug is not in v6.7.0

/cherry-pick cloud

Cherry pick is scheduled.


Teensy 3.2 issue

Hi,
Just trying a very simple program to test the library on a teensy 3.2. It runs totally fine - apart from when in the range of around 480-560. The closer to the mid point I get, the more crazy it gets - continuous jitter up to 20 difference in value. I have tried it with two different pots (different makes), and I have also tested a simple analogue read program using exactly the setup, which it outputs normally (didnt have the filter lib included). I can run your filter library fine on an arduino nano though - no problems at all.
Very odd.
Not a big deal for me, as I've just made my own simple filter which is working fine, but flagging it up in case you feel like looking into it.

This is very weird. It would be nice if the problem could be tested in a reproducible way, which is difficult if a pot is involved. I would suggest performing a test that does not depend on external hardware.
Could you try running the sketch below on your Teensy?
#include <ResponsiveAnalogRead.h>

ResponsiveAnalogRead analog(A0, true);

void setup() {
    Serial.begin(9600);
}

void loop() {
    analog.update(random(480, 544));
    Serial.print(analog.getRawValue());
    Serial.print("\t");
    Serial.println(analog.getValue());
    delay(20);
}

Does it show the excessive jitter you experienced previously? If so, could you share here the program's output?

No probs - when run it's just a random stream around the values you specified. Like:
18:51:27.058 -> 509	522
18:51:27.092 -> 539	526
18:51:27.126 -> 532	527
18:51:27.126 -> 521	527
18:51:27.160 -> 502	517
18:51:27.160 -> 496	509
18:51:27.194 -> 490	503
18:51:27.228 -> 533	503
18:51:27.228 -> 484	497
18:51:27.262 -> 527	510
18:51:27.262 -> 502	510
18:51:27.296 -> 481	497
18:51:27.296 -> 535	517
18:51:27.330 -> 488	504
18:51:27.364 -> 533	516
18:51:27.364 -> 482	499
18:51:27.398 -> 512	499
18:51:27.398 -> 496	499
18:51:27.432 -> 492	499
18:51:27.466 -> 500	499
18:51:27.466 -> 522	507
18:51:27.500 -> 514	508
18:51:27.500 -> 514	508
18:51:27.534 -> 537	521
18:51:27.568 -> 542	528
18:51:27.568 -> 533	528
18:51:27.602 -> 510	528
18:51:27.602 -> 482	499
18:51:27.636 -> 539	521
18:51:27.636 -> 529	522
18:51:27.670 -> 536	525
18:51:27.704 -> 541	529
18:51:27.704 -> 540	531
18:51:27.738 -> 542	533
18:51:27.738 -> 483	499
18:51:27.772 -> 516	499
18:51:27.806 -> 491	498
18:51:27.806 -> 539	521
18:51:27.840 -> 539	526
18:51:27.840 -> 538	528
18:51:27.874 -> 512	528
18:51:27.908 -> 503	518
18:51:27.908 -> 528	518
18:51:27.942 -> 495	509
18:51:27.942 -> 533	509
18:51:27.976 -> 511	509
18:51:27.976 -> 523	512
18:51:28.010 -> 533	519
18:51:28.044 -> 500	519
18:51:28.044 -> 540	526
18:51:28.078 -> 526	526
18:51:28.078 -> 494	510
18:51:28.112 -> 521	510
18:51:28.147 -> 488	502
18:51:28.147 -> 539	521

I modified my test program in order to feed the filter with the exact same inputs as you:
#include <ResponsiveAnalogRead.h>

int inputs[] = {
    509, 539, 532, 521, 502, 496, 490, 533, 484, 527, 502, 481, 535,
    488, 533, 482, 512, 496, 492, 500, 522, 514, 514, 537, 542, 533,
    510, 482, 539, 529, 536, 541, 540, 542, 483, 516, 491, 539, 539,
    538, 512, 503, 528, 495, 533, 511, 523, 533, 500, 540, 526, 494,
    521, 488, 539
};
const size_t INPUT_COUNT = sizeof inputs / sizeof inputs[0];

ResponsiveAnalogRead analog(A0, true);

void setup() {
    Serial.begin(9600);
}

void loop() {
    static size_t i;
    analog.update(inputs[i++]);
    Serial.print(analog.getRawValue());
    Serial.print("\t");
    Serial.println(analog.getValue());
    delay(20);
    if (i == INPUT_COUNT)
        exit(0);
}

I get slightly different outputs at the beginning of the run:
509 509
539 522
532 524
521 524
502 516
496 509
490 503
533 516
484 500
527 511
502 511
481 497
535 517
...

but then, starting from the 12th point, the outputs are identical. In both cases the output looks like a somewhat smoothed version of the input. I see nothing that looks like “crazy jitter”, only expected behavior.
It would then seem that a pseudo-random input doesn't trigger the problem. Do you think you can provide a sequence of input numbers that, when fed to the filter, generates an output displaying the weird jitter you are experiencing?

Yup, very odd - I dont have the chops to be able to speculate on it myself though, and not enough time to dig into it deeper! But anyway here is a section of the jitter (a few small moves, then in and out of the jitter region twice):
23:54:03.710 ->    Analogue read:433  Rawvalue:433  Filtered:429
23:54:03.778 ->    Analogue read:434  Rawvalue:435  Filtered:430
23:54:03.812 ->    Analogue read:434  Rawvalue:436  Filtered:431
23:54:04.900 ->    Analogue read:435  Rawvalue:436  Filtered:432
23:54:04.967 ->    Analogue read:458  Rawvalue:457  Filtered:441
23:54:05.001 ->    Analogue read:471  Rawvalue:471  Filtered:454
23:54:05.069 ->    Analogue read:475  Rawvalue:474  Filtered:460
23:54:05.103 ->    Analogue read:474  Rawvalue:474  Filtered:463
23:54:05.171 ->    Analogue read:475  Rawvalue:474  Filtered:465
23:54:05.205 ->    Analogue read:474  Rawvalue:475  Filtered:467
23:54:05.273 ->    Analogue read:475  Rawvalue:475  Filtered:468
23:54:05.307 ->    Analogue read:475  Rawvalue:475  Filtered:469
23:54:05.341 ->    Analogue read:475  Rawvalue:476  Filtered:470
23:54:05.409 ->    Analogue read:475  Rawvalue:474  Filtered:471
23:54:05.443 ->    Analogue read:475  Rawvalue:477  Filtered:472
23:54:06.395 ->    Analogue read:476  Rawvalue:477  Filtered:473
23:54:06.462 ->    Analogue read:497  Rawvalue:497  Filtered:482
23:54:06.496 ->    Analogue read:525  Rawvalue:525  Filtered:507
23:54:06.564 ->    Analogue read:554  Rawvalue:554  Filtered:536
23:54:06.598 ->    Analogue read:554  Rawvalue:555  Filtered:542
23:54:06.666 ->    Analogue read:555  Rawvalue:555  Filtered:545
23:54:06.700 ->    Analogue read:555  Rawvalue:555  Filtered:546
23:54:06.768 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:06.802 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:06.836 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:06.904 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:06.938 ->    Analogue read:556  Rawvalue:556  Filtered:552
23:54:07.005 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:07.039 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:07.107 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:07.141 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:07.209 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:07.243 ->    Analogue read:555  Rawvalue:534  Filtered:546
23:54:07.311 ->    Analogue read:555  Rawvalue:555  Filtered:547
23:54:07.345 ->    Analogue read:556  Rawvalue:555  Filtered:548
23:54:07.413 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:07.447 ->    Analogue read:556  Rawvalue:555  Filtered:550
23:54:07.515 ->    Analogue read:556  Rawvalue:555  Filtered:551
23:54:07.549 ->    Analogue read:556  Rawvalue:556  Filtered:552
23:54:07.617 ->    Analogue read:555  Rawvalue:542  Filtered:550
23:54:07.651 ->    Analogue read:555  Rawvalue:556  Filtered:551
23:54:07.719 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:07.753 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:07.821 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:07.855 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:07.923 ->    Analogue read:555  Rawvalue:557  Filtered:550
23:54:07.957 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:08.025 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:08.059 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:08.127 ->    Analogue read:549  Rawvalue:555  Filtered:548
23:54:08.161 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:08.229 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:08.263 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:08.331 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:08.365 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:08.399 ->    Analogue read:555  Rawvalue:555  Filtered:548
23:54:08.467 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:08.501 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:08.569 ->    Analogue read:556  Rawvalue:555  Filtered:551
23:54:08.603 ->    Analogue read:555  Rawvalue:535  Filtered:546
23:54:08.671 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:08.705 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:08.773 ->    Analogue read:556  Rawvalue:555  Filtered:550
23:54:08.807 ->    Analogue read:555  Rawvalue:556  Filtered:551
23:54:08.875 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:08.909 ->    Analogue read:556  Rawvalue:534  Filtered:546
23:54:08.977 ->    Analogue read:556  Rawvalue:555  Filtered:547
23:54:09.011 ->    Analogue read:555  Rawvalue:554  Filtered:548
23:54:09.080 ->    Analogue read:556  Rawvalue:555  Filtered:549
23:54:09.114 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:09.188 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:09.221 ->    Analogue read:555  Rawvalue:557  Filtered:552
23:54:09.255 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:09.326 ->    Analogue read:556  Rawvalue:555  Filtered:548
23:54:09.360 ->    Analogue read:556  Rawvalue:555  Filtered:549
23:54:09.428 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:09.462 ->    Analogue read:555  Rawvalue:554  Filtered:551
23:54:09.530 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:09.564 ->    Analogue read:549  Rawvalue:555  Filtered:548
23:54:09.632 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:09.666 ->    Analogue read:556  Rawvalue:555  Filtered:550
23:54:09.734 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:09.768 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:09.836 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:09.870 ->    Analogue read:535  Rawvalue:556  Filtered:548
23:54:09.938 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:09.972 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:10.039 ->    Analogue read:555  Rawvalue:554  Filtered:551
23:54:10.073 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:10.141 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:10.175 ->    Analogue read:556  Rawvalue:556  Filtered:548
23:54:10.243 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:10.277 ->    Analogue read:556  Rawvalue:555  Filtered:550
23:54:10.311 ->    Analogue read:555  Rawvalue:556  Filtered:551
23:54:10.379 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:10.412 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:10.468 ->    Analogue read:555  Rawvalue:555  Filtered:548
23:54:10.535 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:10.569 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:10.637 ->    Analogue read:556  Rawvalue:555  Filtered:551
23:54:10.671 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:10.739 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:10.773 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:10.841 ->    Analogue read:555  Rawvalue:554  Filtered:550
23:54:10.875 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:10.943 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:10.977 ->    Analogue read:555  Rawvalue:555  Filtered:548
23:54:11.045 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:11.079 ->    Analogue read:542  Rawvalue:555  Filtered:550
23:54:11.147 ->    Analogue read:555  Rawvalue:556  Filtered:551
23:54:11.181 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:11.215 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:11.283 ->    Analogue read:554  Rawvalue:555  Filtered:549
23:54:11.317 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:11.386 ->    Analogue read:555  Rawvalue:556  Filtered:551
23:54:11.420 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:11.488 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:11.522 ->    Analogue read:555  Rawvalue:555  Filtered:548
23:54:11.590 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:11.624 ->    Analogue read:556  Rawvalue:555  Filtered:550
23:54:11.692 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:11.726 ->    Analogue read:556  Rawvalue:556  Filtered:552
23:54:11.794 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:11.828 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:11.896 ->    Analogue read:549  Rawvalue:555  Filtered:549
23:54:11.930 ->    Analogue read:555  Rawvalue:556  Filtered:550
23:54:11.998 ->    Analogue read:556  Rawvalue:556  Filtered:551
23:54:12.032 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:12.100 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:12.134 ->    Analogue read:556  Rawvalue:555  Filtered:549
23:54:12.202 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:12.236 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:12.270 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:12.337 ->    Analogue read:556  Rawvalue:556  Filtered:548
23:54:12.376 ->    Analogue read:556  Rawvalue:555  Filtered:549
23:54:12.444 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:12.478 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:12.546 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:12.580 ->    Analogue read:555  Rawvalue:555  Filtered:548
23:54:12.648 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:12.682 ->    Analogue read:556  Rawvalue:555  Filtered:550
23:54:12.750 ->    Analogue read:555  Rawvalue:556  Filtered:551
23:54:12.784 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:12.852 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:12.886 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:12.920 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:12.988 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:13.022 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:13.090 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:13.124 ->    Analogue read:555  Rawvalue:555  Filtered:548
23:54:13.192 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:13.226 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:13.294 ->    Analogue read:555  Rawvalue:556  Filtered:551
23:54:13.328 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:13.396 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:13.430 ->    Analogue read:555  Rawvalue:535  Filtered:544
23:54:13.498 ->    Analogue read:555  Rawvalue:555  Filtered:546
23:54:13.532 ->    Analogue read:555  Rawvalue:554  Filtered:547
23:54:13.600 ->    Analogue read:555  Rawvalue:555  Filtered:548
23:54:13.634 ->    Analogue read:555  Rawvalue:556  Filtered:549
23:54:13.702 ->    Analogue read:554  Rawvalue:556  Filtered:550
23:54:13.736 ->    Analogue read:556  Rawvalue:555  Filtered:551
23:54:13.804 ->    Analogue read:556  Rawvalue:557  Filtered:552
23:54:13.838 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:13.906 ->    Analogue read:555  Rawvalue:555  Filtered:548
23:54:13.940 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:14.008 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:14.042 ->    Analogue read:557  Rawvalue:535  Filtered:546
23:54:14.076 ->    Analogue read:534  Rawvalue:556  Filtered:548
23:54:14.144 ->    Analogue read:555  Rawvalue:556  Filtered:549
23:54:14.178 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:14.246 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:14.280 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:14.348 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:14.382 ->    Analogue read:556  Rawvalue:556  Filtered:548
23:54:14.450 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:14.484 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:14.552 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:14.586 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:14.653 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:14.687 ->    Analogue read:556  Rawvalue:555  Filtered:548
23:54:14.754 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:14.788 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:14.856 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:14.890 ->    Analogue read:555  Rawvalue:555  Filtered:552
23:54:14.958 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:14.991 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:15.059 ->    Analogue read:555  Rawvalue:556  Filtered:549
23:54:15.093 ->    Analogue read:556  Rawvalue:555  Filtered:550
23:54:15.161 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:15.195 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:15.262 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:15.296 ->    Analogue read:555  Rawvalue:555  Filtered:548
23:54:15.363 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:15.399 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:15.467 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:15.501 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:15.535 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:15.603 ->    Analogue read:555  Rawvalue:555  Filtered:548
23:54:15.637 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:15.705 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:15.739 ->    Analogue read:556  Rawvalue:555  Filtered:551
23:54:15.807 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:15.841 ->    Analogue read:555  Rawvalue:535  Filtered:547
23:54:15.909 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:15.943 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:16.011 ->    Analogue read:554  Rawvalue:555  Filtered:550
23:54:16.045 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:16.113 ->    Analogue read:556  Rawvalue:557  Filtered:552
23:54:16.147 ->    Analogue read:556  Rawvalue:535  Filtered:547
23:54:16.215 ->    Analogue read:555  Rawvalue:556  Filtered:548
23:54:16.249 ->    Analogue read:555  Rawvalue:555  Filtered:549
23:54:16.317 ->    Analogue read:555  Rawvalue:555  Filtered:550
23:54:16.351 ->    Analogue read:555  Rawvalue:555  Filtered:551
23:54:16.419 ->    Analogue read:555  Rawvalue:556  Filtered:552
23:54:16.453 ->    Analogue read:573  Rawvalue:574  Filtered:559
23:54:16.521 ->    Analogue read:603  Rawvalue:602  Filtered:584
23:54:16.555 ->    Analogue read:610  Rawvalue:609  Filtered:594
23:54:16.589 ->    Analogue read:611  Rawvalue:609  Filtered:597
23:54:16.657 ->    Analogue read:610  Rawvalue:609  Filtered:600
23:54:16.691 ->    Analogue read:610  Rawvalue:610  Filtered:601
23:54:16.759 ->    Analogue read:610  Rawvalue:610  Filtered:602
23:54:16.793 ->    Analogue read:610  Rawvalue:610  Filtered:603
23:54:16.861 ->    Analogue read:610  Rawvalue:609  Filtered:604
23:54:16.895 ->    Analogue read:610  Rawvalue:610  Filtered:605
23:54:16.963 ->    Analogue read:610  Rawvalue:610  Filtered:606
23:54:17.031 ->    Analogue read:610  Rawvalue:612  Filtered:607
23:54:20.030 ->    Analogue read:604  Rawvalue:603  Filtered:606
23:54:20.098 ->    Analogue read:586  Rawvalue:586  Filtered:599
23:54:20.132 ->    Analogue read:578  Rawvalue:579  Filtered:592
23:54:20.200 ->    Analogue read:575  Rawvalue:576  Filtered:588
23:54:20.234 ->    Analogue read:575  Rawvalue:576  Filtered:585
23:54:20.302 ->    Analogue read:568  Rawvalue:567  Filtered:579
23:54:20.336 ->    Analogue read:566  Rawvalue:567  Filtered:577
23:54:20.404 ->    Analogue read:566  Rawvalue:566  Filtered:574
23:54:20.438 ->    Analogue read:563  Rawvalue:564  Filtered:572
23:54:20.472 ->    Analogue read:555  Rawvalue:556  Filtered:568
23:54:20.540 ->    Analogue read:513  Rawvalue:520  Filtered:536
23:54:20.574 ->    Analogue read:510  Rawvalue:510  Filtered:525
23:54:20.642 ->    Analogue read:510  Rawvalue:537  Filtered:528
23:54:20.676 ->    Analogue read:510  Rawvalue:510  Filtered:522
23:54:20.744 ->    Analogue read:510  Rawvalue:510  Filtered:519
23:54:20.778 ->    Analogue read:510  Rawvalue:510  Filtered:518
23:54:20.846 ->    Analogue read:510  Rawvalue:510  Filtered:516
23:54:20.880 ->    Analogue read:510  Rawvalue:510  Filtered:515
23:54:20.948 ->    Analogue read:509  Rawvalue:510  Filtered:514
23:54:20.982 ->    Analogue read:510  Rawvalue:510  Filtered:513
23:54:21.050 ->    Analogue read:510  Rawvalue:539  Filtered:523
23:54:21.084 ->    Analogue read:510  Rawvalue:510  Filtered:520
23:54:21.152 ->    Analogue read:510  Rawvalue:510  Filtered:518
23:54:21.186 ->    Analogue read:510  Rawvalue:510  Filtered:517
23:54:21.254 ->    Analogue read:510  Rawvalue:510  Filtered:516
23:54:21.288 ->    Analogue read:511  Rawvalue:510  Filtered:515
23:54:21.356 ->    Analogue read:510  Rawvalue:510  Filtered:514
23:54:21.390 ->    Analogue read:510  Rawvalue:510  Filtered:513
23:54:21.458 ->    Analogue read:510  Rawvalue:508  Filtered:512
23:54:21.492 ->    Analogue read:510  Rawvalue:538  Filtered:522
23:54:21.560 ->    Analogue read:510  Rawvalue:510  Filtered:520
23:54:21.594 ->    Analogue read:510  Rawvalue:510  Filtered:518
23:54:21.661 ->    Analogue read:508  Rawvalue:509  Filtered:516
23:54:21.695 ->    Analogue read:510  Rawvalue:510  Filtered:515
23:54:21.763 ->    Analogue read:511  Rawvalue:510  Filtered:514
23:54:21.797 ->    Analogue read:510  Rawvalue:509  Filtered:513
23:54:21.865 ->    Analogue read:509  Rawvalue:508  Filtered:512
23:54:21.933 ->    Analogue read:510  Rawvalue:524  Filtered:514
23:54:21.967 ->    Analogue read:509  Rawvalue:510  Filtered:513
23:54:22.035 ->    Analogue read:510  Rawvalue:508  Filtered:512
23:54:22.103 ->    Analogue read:510  Rawvalue:531  Filtered:518
23:54:22.137 ->    Analogue read:510  Rawvalue:510  Filtered:517
23:54:22.205 ->    Analogue read:510  Rawvalue:511  Filtered:516
23:54:22.243 ->    Analogue read:509  Rawvalue:509  Filtered:515
23:54:22.276 ->    Analogue read:510  Rawvalue:510  Filtered:514
23:54:22.344 ->    Analogue read:510  Rawvalue:510  Filtered:513
23:54:22.412 ->    Analogue read:538  Rawvalue:539  Filtered:523
23:54:22.480 ->    Analogue read:510  Rawvalue:510  Filtered:520
23:54:22.514 ->    Analogue read:508  Rawvalue:509  Filtered:518
23:54:22.548 ->    Analogue read:510  Rawvalue:509  Filtered:516
23:54:22.615 ->    Analogue read:509  Rawvalue:510  Filtered:515
23:54:22.649 ->    Analogue read:510  Rawvalue:510  Filtered:514
23:54:22.717 ->    Analogue read:510  Rawvalue:510  Filtered:513
23:54:22.784 ->    Analogue read:509  Rawvalue:508  Filtered:512
23:54:22.818 ->    Analogue read:524  Rawvalue:539  Filtered:523
23:54:22.886 ->    Analogue read:511  Rawvalue:510  Filtered:520
23:54:22.920 ->    Analogue read:511  Rawvalue:508  Filtered:517
23:54:22.988 ->    Analogue read:509  Rawvalue:510  Filtered:516
23:54:23.022 ->    Analogue read:511  Rawvalue:510  Filtered:515
23:54:23.090 ->    Analogue read:510  Rawvalue:510  Filtered:514
23:54:23.124 ->    Analogue read:510  Rawvalue:510  Filtered:513
23:54:23.192 ->    Analogue read:509  Rawvalue:531  Filtered:518
23:54:23.226 ->    Analogue read:518  Rawvalue:523  Filtered:519
23:54:23.260 ->    Analogue read:524  Rawvalue:539  Filtered:525
23:54:23.328 ->    Analogue read:517  Rawvalue:538  Filtered:528
23:54:23.362 ->    Analogue read:517  Rawvalue:538  Filtered:529
23:54:23.430 ->    Analogue read:510  Rawvalue:510  Filtered:523
23:54:23.464 ->    Analogue read:510  Rawvalue:517  Filtered:522
23:54:23.532 ->    Analogue read:509  Rawvalue:510  Filtered:519
23:54:23.566 ->    Analogue read:510  Rawvalue:510  Filtered:518
23:54:23.634 ->    Analogue read:511  Rawvalue:510  Filtered:516
23:54:23.668 ->    Analogue read:524  Rawvalue:538  Filtered:524
23:54:23.736 ->    Analogue read:510  Rawvalue:510  Filtered:520
23:54:23.770 ->    Analogue read:510  Rawvalue:510  Filtered:518
23:54:23.838 ->    Analogue read:510  Rawvalue:510  Filtered:517
23:54:23.871 ->    Analogue read:510  Rawvalue:509  Filtered:516
23:54:23.939 ->    Analogue read:510  Rawvalue:510  Filtered:515
23:54:23.973 ->    Analogue read:510  Rawvalue:510  Filtered:514
23:54:24.041 ->    Analogue read:510  Rawvalue:510  Filtered:513
23:54:24.075 ->    Analogue read:510  Rawvalue:539  Filtered:523
23:54:24.143 ->    Analogue read:510  Rawvalue:509  Filtered:520
23:54:24.177 ->    Analogue read:509  Rawvalue:510  Filtered:518
23:54:24.245 ->    Analogue read:510  Rawvalue:509  Filtered:516
23:54:24.279 ->    Analogue read:510  Rawvalue:510  Filtered:515
23:54:24.347 ->    Analogue read:509  Rawvalue:509  Filtered:514
23:54:24.384 ->    Analogue read:510  Rawvalue:510  Filtered:513
23:54:24.418 ->    Analogue read:510  Rawvalue:532  Filtered:518
23:54:24.486 ->    Analogue read:510  Rawvalue:510  Filtered:517
23:54:24.523 ->    Analogue read:510  Rawvalue:508  Filtered:515
23:54:24.593 ->    Analogue read:473  Rawvalue:473  Filtered:490
23:54:24.627 ->    Analogue read:438  Rawvalue:437  Filtered:453
23:54:24.695 ->    Analogue read:429  Rawvalue:428  Filtered:443
23:54:24.729 ->    Analogue read:429  Rawvalue:430  Filtered:440
23:54:24.797 ->    Analogue read:428  Rawvalue:428  Filtered:437
23:54:24.831 ->    Analogue read:428  Rawvalue:428  Filtered:436
23:54:24.899 ->    Analogue read:428  Rawvalue:428  Filtered:434
23:54:24.933 ->    Analogue read:427  Rawvalue:428  Filtered:433
23:54:25.001 ->    Analogue read:428  Rawvalue:428  Filtered:432
23:54:25.035 ->    Analogue read:428  Rawvalue:428  Filtered:431
23:54:25.103 ->    Analogue read:428  Rawvalue:427  Filtered:430
23:54:25.579 ->    Analogue read:427  Rawvalue:424  Filtered:429
23:54:25.714 ->    Analogue read:426  Rawvalue:422  Filtered:428
Looking at it again now, it looks like I was wrong and the analogueRead is mostly stable - but not always, just occasionally going outside the norm. Very bizzarro.
And this the code I was using (note does the same if I am not taking an analogueRead):
#include <ResponsiveAnalogRead.h>
int val;
ResponsiveAnalogRead analog1(A0, true);
void setup()
{
Serial.begin(28800);
}
void loop()
{
analog1.update();
val=analog1.getValue();
if(analog1.hasChanged()) {
Serial.print ("   Analogue read:");
Serial.print (analogRead(A0));
Serial.print ("  Rawvalue:");
Serial.print(analog1.getRawValue());
Serial.print ("  Filtered:");
Serial.println(val);
delay (50);
}
}

There is a problem here:
if(analog1.hasChanged()) {

You are printing the data only when the library judges that the change in input is significant enough that it should be reflected on the output. We then don't see the real stream of data you are feeding to the filter, which makes it impossible to try to reproduce the problem.

I also note that adding 20 seems to be a favourite

What I do see is that the input makes jumps of 20. It is most clear in the section of the data from the 19th to the 215th data point, where the input fluctuates mostly between 555 and 535.
As for the output, it just follows the input's fluctuations with a smaller amplitude. When the input drops to 535, the outputs starts going down. But then, the input rises again to 555, and the output responds by going up again:

In my opinion this data set shows nothing wrong in the filter's behavior: this is exactly what you should expect from a smoothing filter. Your problem seems to be that the data you feed to the filter's input has an unusually high level of noise, with a weird bimodal density function. You could try to mitigate this problem by decreasing the “snap multiplier” in order to make the filter more aggressive. For example:
// snapMultiplier defaults to 1e-2. Setting it to 3e-3 makes
// the filter more aggressive, but also somewhat more sluggish.
ResponsiveAnalogRead analog1(A0, true, 3e-3);

which should result in only tiny fluctuations at the output, at the cost of some responsiveness. Alternatively, you could run a median filter upstream of ResponsiveAnalogRead. Median filters tend to be quite effective against the kind of “jumpy” noise you seem to have here.
In any case, I would qualify this issue as invalid, as the problem lies in your data source, not in this filter's code.

 But as I said, I made my own simple filter with exactly the same setup, and I see none of this jitter in the region shown. I average the current and last value, and the two values before that, and then check to see if jitter is greater than 2 - which it never is unless I am moving the pot. My own version of ismoving is never erroneously flagged. Without your code, I can run a simple analogueread on its own, and this "high level of noise" is simply not present.
Anyway, I dont actually need to use your filter, my own is small enough and works, I just wanted to tell you that the issue existed.


Add fast-path construction to DAGCircuit methods

Summary
This optimises the constructor functions
DAGCircuit.apply_operation_back, apply_operation_front and compose by giving callers a way to skip the validity checking when passing known-good values.  In most cases when we're operating on the DAG, we are certain that we're already upholding the invariants of the data structure by nature of having a copy_empty_like or similar, and the user should not pay a runtime price for what we should catch during testing.

Details and comments
I ran a benchmark suite and asv didn't pop up anything statistically significant in changes but quite a bit of stuff saw ~5% improvements. I'm just running benchmarks on a laptop in other use, and our benchmark suite is quite outdated now.
In a more targeted microbenchmark with setup
from qiskit.circuit.library import QuantumVolume
from qiskit.converters import circuit_to_dag
qc = QuantumVolume(100, seed=0).decompose()

the call circuit-to_dag(qc, copy_operations=False) went from 34.3(7)ms to 28.6(7)ms, so a ~15% speedup.  That's indicative of what's happening when we're doing things like rebuilding the DAG after Sabre or during ApplyLayout.

It would be useful to design a canonical way to choose whether to do expensive safety checks. The simplest "design" is using the same name for the option to elide checks. For example, we have
https://github.com/Qiskit/qiskit/blob/61e5bde38b393540c8640b320127fffad918e9f6/qiskit/synthesis/discrete_basis/solovay_kitaev.py#L93
https://github.com/Qiskit/qiskit/blob/61e5bde38b393540c8640b320127fffad918e9f6/qiskit/circuit/library/generalized_gates/linear_function.py#L78-L79
I'm concerned about adding more variety to these options, making the barrier to cleaning it up in the future even larger.
Maybe this PR could use the design we want (again, maybe simplest is best and the design is just a naming convention). And a followup PR could make this uniform to the extent possible across qiskit.

Fwiw we also have validate, require_cp, require_tp in quantum_info, and cycle_check within DAGCircuit, which are all types of input validation as well.  I don't mind especially what we go for (I err on the shorter side when the meaning is unambiguous) - which do you prefer so I can update the PR?

Short story. I am ok with using check for now. It may not be the best name, but the marginal tech debt of a name that must be changed is small. Trying to figure this out now would derail this PR.
longer:
For the sake of brevity, I didn't mention concerns about: corner cases, internal vs external api, conceptual and motivational differences in eliding checks, interactions between checks.
Of course that all becomes immediately important.  I won't suggest unifying require_tp and require_cp into check, as they were already split (https://github.com/Qiskit/qiskit/pull/3660) from require_cptp and given different defaults. No reason was given, but I'm sure there was one. I grepped all of the qiskit repos and only find these options in a few tests in qiskit-experiments, and always set to False.
I think standardizing on something like check_some_invariant, and check_all might be a good first step. I.e. in this case check becomes check_all and require_tp becomes check_tp.  Some of these currently log a warning others error. That should probably be worked into the naming.

That sounds like an interesting topic to pursue potentially under the guise of defining a "naming convention" guide for Qiskit.  Perhaps we could move that into a separate issue to track?

In bits_in_operation, shouldn't this
https://github.com/Qiskit/qiskit/blob/7252db3723c286f6c4b4865c654061911ff33e3b/qiskit/dagcircuit/dagcircuit.py#L572-L574
have elif isinstance(operation, SwitchCaseOp)? without elif it's harder to read if you don't know the code.

I think that this
https://github.com/Qiskit/qiskit/blob/7252db3723c286f6c4b4865c654061911ff33e3b/qiskit/dagcircuit/dagcircuit.py#L1194-L1197
should use _operation_may_have_bits as well.

The questions above are all I have. The main part of the PR, i.e. introducing a check option looks good to me.

I think I wrote that SwitchCaseOp if/if as a defensive thing - the two branches are mutually exclusive right now, but to me making it if/else felt like making more assumptions than were needed for the function.

I've done the substitute_node_with_dag thing in 14b215cd4.  In general I didn't look to optimise any of the other DAGCircuit functions to keep the scope of the PR targetted and because DAG reconstruction from SabreSwap is one place that bottlenecks transpile which only uses apply_operation_back at the moment.

(you need to leave an approving review to enable merge - the merge queue handles bringing the PR up-to-date with main, so that's not necessary, but the code-owner approval is)

Huh. I tried to do that. Clicked on the green approve button....
I'll try again.


DropdownListCell body type is not serializing/deserializing in any format when saving/loading workbook

Now the interface for saving and loading custom cell body has been added.
The custom cell body data provider can be added or remoted by access the RGFPersistenceProvider.CustomBodyTypeProviders list.
// My custom cell body
class MyCellBody : CellBody
{
}

// The provider used to save and load cell body
class MyCellBodyPersistenceProvider : RGFCustomBodyHandler
{
	public object LoadData(Cell cell, string data)
	{
		return "Loaded";
	}

	public string SaveData(Cell cell)
	{
		return "Saved";
	}
}

Add custom persistence provider:
RGFPersistenceProvider.CustomBodyTypeProviders.Add(typeof(MyCellBody), "my-cell-body", new MyCellBodyPersistenceProvider());

Test
sheet["A1"] = new MyCellBody();

And save the worksheet as RGF, the data value will be stored as:
<cell row="0" col="0" body-type="my-cell-body">Saved</cell>


Fixed The Repeated Call of Layer5 In the used By Section

Description
Fixed The Repeated Call of Layer5 In the used By Section As discussed in the weekly meeting
This PR fixes #1152
Before :-

With this PR changes :-

Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@thisiskaransgit all the mentioned issues for the issue are fixed already in my pr

no worries @GaganpreetKaurKalsi


Use rebuilt CI image when changes are present in docker/

This PR makes the CI use the built image (when changes in docker/ cause the CI to rebuild the docker images) in the remaining stages of the CI. This allows us to verify that CI would pass with the newly-built image.
@driazati

closing in favor of a better fix in #11673


Bottom up Tracking Issue

Bottom up now works on the synth branch.
A super simple example: cargo run --release --bin=synth -- --max-cost=10 -d simple --print-found
A more complex one: cargo run --release --bin=synth
The big missing features are:

Real types. Right now we have a weird shallow type solution. I think we should either go fully simple types or fully polymorphic or at least a bit more interesting than how it is now. for the purposes of prototyping things, simple types probably make a lot of sense. Simple types would be pretty good - after all how often do you see anything other than List[int]. That seems fine enough for any amount of prototyping. Also it'd make it super easy to write fast evaluators. Downside is fixpoint probably is not possible maybe? But again yeah thats all higher order stuff that we dont deal with. And yes at the end of the day in PL people will prob wanna see polymorphic types but for prototyping this seems like the move
Lambdas. We handle them in any way right now so they get fully ignored. With simple types inference would be trivial with them so at least we could prune that. I think the right way to handle them is to have an extra cost be incurred for them

All my notes on this bottom up synth stuff and many more ideas are in 2022-07-18 adding synthesis to stitch.

Actually, Now the polymorphic branch implements full polymorphic dreamcoder-style types and does bottom up! This ended up being even a bit faster than the original bottom up implementation.

migrated to https://github.com/mlb2251/synthestitch/issues/1


[API][Eco News Comment Controller] Status code 200 OK is received after changing the parameter name in 'Get all active comments' controller

Environment: macOS BigSur, Chrome 100.0.4896.88
Reproducible: always
**Build found:**29.04.2022
Preconditions
1.Go to Postman
2.Sign In POST greencity-user.azurewebsites.net/ownSecurity/signIn
3.Login as admin
4.Body
{
"email": "string",
"password": "string"
}
Steps to reproduce
1.GET greencity.azurewebsites.net//econews/comments/active
2. Parameters:

ecoNewsId = 1
page = 1
size = 5

Change parameter name (e.g pagefrtg, sizefgbfb)
Run the test

Actual result
Status code 200 is received after changing the parameter name
Expected result
Status code 400 Bas Request is received after changing the parameter name

e

If page or size parameters are not present or incorrect values are passed to them, default values will be substituted (page = 0, size = 20). Its not a bug, its a feature)


Output WebUI

Signed-off-by: Issif issif_github@gadz.org<!--  Thanks for sending a pull request!  Here are some tips for you:

If this is your first time, please read our contributor guidelines in the CONTRIBUTING.md file and learn how to compile Falco from source here.
Please label this pull request according to what type of issue you are addressing.
If the PR is unfinished while opening it specify a wip in the title before the actual title, for example, "wip: my awesome feature"
-->

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area config

/area outputs

/area tests

What this PR does / why we need it:
This PR prepares the incoming WebUI for falcosidekick as new Output.

I need it for using new exported types.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign issif after the PR has been reviewed.
You can assign the PR to them by writing /assign @issif in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

LGTM label has been added.  Git tree hash:<PHONE_NUMBER>b4c1f607f129c0fd3313ff4c3f1904

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: danpopSD
To complete the pull request process, please assign issif after the PR has been reviewed.
You can assign the PR to them by writing /assign @issif in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Either Web Address or URL would be fine, otherwise it's LGTM!

@KeisukeYamashita I'm ok with your proposal, just FYI, I tried to use same pattern than outputs use in their documentation. For example, Slack calls it Webhook URL, Elasticsearck it's Host:Port, too. This is why there's no global coherence in falcosidekick config, but in my mind it was with outputs for helping who already know them.
For WebUI, as it's our own product, we can do whatever we want. I'll apply your suggestions. Thanks 👍

@KeisukeYamashita I did it 👍

LGTM label has been added.  Git tree hash: d15d553c1b5a332755e0db702ff769a9f2668409

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: danpopSD, KeisukeYamashita
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [KeisukeYamashita]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

late for the party
/lgtm


Update application.go

adding multiple commands or topics at a time would be convenient

I can't think of a use case unfortunately. Anyway, AddCommand must do exactly what it says — adding a command, not multiple commands.


HDDS-3742. Improve OM performance with 5.29% by avoid stream.collect

What changes were proposed in this pull request?
I start a ozone cluster with 1000 datanodes, and run two weeks with heavy workload, and perf om.
stream().collect(Collectors.toList())) in getProtoBuf cost 5.29% cpu.

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3742
How was this patch tested?
Existed test

Thank You @runzhiwang for the performance improvement.


Direct Connect Gateway support

Summary:
The module should allow to attach to and/or create a Direct Connect Gateway similar to the VPN Gateway support.
Motivation:
I would use this when I want to increase or decrease capacity for my Equinix connections to AWS Direct Connect Gateways.
Proposal:
I would copy the structure of the VPN Gateway support, with the option to create a Direct Connect Gateway or attach dxvifs to an existing Direct Connect Gateway.

https://github.com/equinix-labs/terraform-equinix-fabric-connection-aws/pull/17 is related to this issue.


Compose a timeline

Make a list of all (important) life events, significant dates, achievements, periods that gave pleasant and unpleasant experiences, etc.

It was possible to complete this task