[BUG] [SSH Logs] Parse error : queries require at least one regexp or equality matcher that does not have an empty-compatible value.

Loki Version: [2.9.6]
Grafana Version: [10.4.1]
Promtail Version: [2.9.6]
Dashboard Name: [SSH Logs]
Hello. I'm using your SSH Logs dashboard and all the time getting the error:
Error
parse error : queries require at least one regexp or equality matcher that does not have an empty-compatible value. For instance, app=~".*" does not meet this requirement, but app=~".+" will

In my case promtail.conf looks like:
scrape_configs:
- job_name: system
  static_configs:
  - targets:
      - localhost
    labels:
      job: messages
      __path__: /var/log/messages
- job_name: audit
  static_configs:
  - targets:
      - localhost
    labels:
      job: audit
      __path__: /var/log/audit/*.log
- job_name: secure
  static_configs:
  - targets:
      - localhost
    labels:
      job: secure
      __path__: /var/log/secure

And in a grafana I chose all Label name, all Label Value and all Job

Could you please help me solve the problem?

Please ensure that you select the correct labels and that the dashboard is targeting one host at a time. In your case, please make sure to select:

label_value as your target host
secure as the job

Once you've selected the above labels, you should see data in the dashboard. Could you please confirm this? Ensure that your timeframe is correct and that the logs exist for the selected time period.
FYI:
The error message you're encountering is related to the issue discussed here: https://github.com/grafana/loki/issues/7816. I won't consider this as a bug.

@voidquark Hello. Thank you for your reply.
The dashboard shows data, but when I want to change the timeframe I'm getting the error.
Main idea is that I want to see all ssh logs for all hosts. It is very important for me.

I'll likely need to release a new revision to prevent selecting multiple hosts. The dashboard functions properly with only one host. Could you please rerun with just one host?
Thanks for the feedback. I'll consider creating another dashboard for an overview of all hosts, but that would require building a separate one (a multi-host SSH dashboard).

@voidquark Hello. Yes, with one host in one period of time works correctly.
Let me know when I can try multi-host SSH dashboard.
Thank you so much.

Thank you for confirming. If you'd like to stay informed about its release, you have a few options:

Click on the 'watch' button at the top of this repository.
Subscribe to RSS feed or Atom feed.
Sign up for our newsletter or follow us on social media.

I'll go ahead and close this issue since it's not a bug.


Allow serde and serde_derive to compile in parallel

Visualized in cargo build --timings:

Before:
After:

Previously serde and serde_json could only begin compiling after serde_derive was finished compiling. After, they can compile in parallel.
This reduces build time by 2 seconds (30%). This crate is in the critical path of the widely used reqwest crate, so I think this is worth doing.

Thanks for the PR! This is merged, and also backported to the 0.16 (current version included from reqwest) branch. Released as 0.16.2 and 0.19.1.


Upgrade ESLint and prettier deps

The current prettier version isn't compatible with the new TypeScript satisfies operator. This PR fixes that by upgrading EsLint, Prettier and related plugins.

@JoaquinTrinanes could you please check https://github.com/Vizzuality/front-end-scaffold/pull/114 ? I think it already covers all your changes, but let me know if I am missing anything 🙏🏻

@andresgnlez It covers that and more! I'll close this PR :)


Prelim Docs Organization

brain dump, for now. pay no attention
## Quick Demo

## Philosophy

## Features

## Template Reference

## Views, Models & Composition (domvm.view.js)

## Emit & refs, keys

## Consuming and exposing APIs
	vm.imp
	vm.exp
	vm.redraw(newImp)

## Mutation Observers (domvm.watch.js)

## Routing (domvm.route.js)
	rt.goto
	rt.href
	rt.back/fwd
	rt.state

## Isomorphism (domvm.html.js)
	vm.html()
	vm.attach()

## Third-party DOM integration
	elem			raw elements?
	{_guard: true}	third-party nodes
	{_raw: true}	innerHTML
	vm.absorb()		// also used extreme optimization

## Optimization
	Event Delegation
	Template patching
		vm.patch()

## Useful Patterns

## Solutions to common problems / wiki
	css animation
	animate pre-destroy
	maintain focus
	animated re-order

## Utils (domvm.util.js)

## Suggested Polyfills / es5-shim
	bala.js

## Demos, benchmarks

@barneycarroll
@yosbelms
@lawrence-dol
If any of you have a bit of time and/or interest, I have updated the docs quite a bit and wanted to get some feedback as to whether anything seems unclear, poorly organized or any concepts presented too early or wrong order. I decided to go ahead and add "patterns" from https://github.com/leeoniya/domvm/wiki/View-Model-Patterns to the main readme. Originally I figured it would be overload, but it seems okay and helps with not pushing one opinionated pattern and really shows off the possibilities.
I've also added a bunch of items to the nav.outline that remain on the todo for documentation for features already present in the lib.
thanks!

most of this is in the docs todo


Fix the under minimum resources test

The under minimum resources test is incorrectly determining how many actions are sent to determine failure.

hey, we have rewritten a new version of min available ram test with the new testing framework, which provides a more deterministic way to estimate RAM usage (use create account action only from bios contract). would take a look at lstests/db_guard_test.py in https://github.com/EOSIO/eos/pull/8102/files?

Resolved by #8194


ID Token From Metadata Server Incorrect

https://github.com/googleapis/google-auth-library-nodejs/blob/49a5aec62ff5dddf38c55fd1f3c9502068e4e4e5/samples/idTokenFromMetadataServer.js#L38C1-L38C1
Based on the return values of the client, it doesn't have the fetchIdToken function which is mentioned in this code.

I have the same issue, and the lack of straightforwardness in the docs is becoming a nightmare. I just need to call a cloud run service from another cloud run service, and this is taking a LOT of frustrating effort

Thanks for the feedback - I agree, we can improve the documentation here.
Raised a PR: #1651

@danielbankhead, stellar and kind response. Thank you!


Add empirical reference calculations to logP analyis.

These PR adds a variety of empirical logP prediction methods (submitted by Thomas Fox) to logP challenge analysis.

REF09: clogP (Biobyte)
REF10: h_logP (MOE)
REF11: logP(o/w) (MOE)
REF12: MoKa_logP
REF13: SlogP (MOE)

Looks good to me.

@MehtapIsik mostly looks good, except I think you've also updated lots of plots that haven't changed, at the same time? Specifically (for example) the absolute error plots for all of the individual submissions.
I'm guessing you just re-ran the analysis script, but then committed all of the files whether they had changed or not?

Yes, correct. My script replotted all those. Even if nothing changes, something changes in PDF binary files. So I committed all those new plots.

Right, so the way I would have done it would have been to only commit files which changed so that the revision history doesn't look like we updated everything.
If it's too much trouble to roll that back we can go ahead with what you've committed, but I worry it will make the revision history confusing to have all these plots "updated" after the challenge.

I know it is crowding the revision history but it is too hard to differentiate between PDFs that were really updated and PDFs that look like they were updated. I am afraid to cause a mixture of new and old files and introduce mistakes if I try to avoid these. It is better to merge as is.


Doc fix: The Imputer is an Estimator

Fixing the doc as the imputer is not a Transformer but an Estimator.
https://github.com/apache/spark/blob/master/mllib/src/main/scala/org/apache/spark/ml/feature/Imputer.scala#L96-L97
What changes were proposed in this pull request?
Simple documentation fix
How was this patch tested?
manual testing
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Test build #4214 has started for PR 21755 at commit 19cd33b.

Test build #4214 has finished for PR 21755 at commit 19cd33b.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

I'm sure the failure is spurious, so merged to master.
PS see https://spark.apache.org/contributing.html

@srowen Just about to submit a new doc relates pull request.
Wondering if your PS see https://spark.apache.org/contributing.html line referred to anything specific about how I should issue these PRs differently?

Minor stuff: we usually tag this with [MINOR] in the title to be clear there's no JIRA. Also ideal to batch together small related changes but I don't know that there was anything else to do here.


Support markdown on descriptions

Describe your suggested feature
add support to markdown on descriptions
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.16.5.
[X] I will fill out all of the requested information in this form.

Better explanation/justification for closing:
After some discussion in the Mihon server about this, only a handful of sites do markdown, so it's a niche thing to support markdowns in general for descriptions (dev also agreed on not supporting it)

If it's just allowing markdown to show up in description, seems like an easy way to bog up/bloat while searching in my opinion
If it's like how I thought about it, allowing edit to description with markdown, I think it would be better to just do Manga Notes (Add Manga Notes #428) or nab the custom edit info from SY instead

I was thinking more of the sources that has alternative titles in the description tbh, then editing the code on the extension to add markdown to the alternative titles sections.
it would me much easier to identify the start of the alternative titles if there was a markdown support on it, but I get your and the devs point as well


Overflow when adding 2 long values in SlidingTimeWindowReservoir

In SlidingTimeWindowReservoir.getTick computing the new tick final long tick = clock.getTick() * COLLISION_BUFFER; results in overflow when the default clock is used.

This is a known issue, which we are tracking in #515.

Here's what I've done at my place that fixed it https://github.com/dropwizard/metrics/pull/931
We had this problem when physical server uptime was over 417 days - rebooting server, would restart up time for another 417 days, but we wanted a permanent fix, so I created this one.


Ability to run a script from stdin

Hi,
I just found rust-script and it's super-great! :heart:
I'm using it to generate a small Rust script and then run it like that:
sed 's/PKG/{{ pkg }}/g;s/KIND/{{ kind }}/g' > .script.rs <<< '{{ render-script }}'
chmod +x .script.rs
./.script.rs {{ output }}
rm --force .script.rs

And I thought it would be convenient if I could just pipe the script directly to rust-script without saving it to file, something like that:
sed 's/PKG/{{ pkg }}/g;s/KIND/{{ kind }}/g' | rust-script --some-kind-of-option <<< '{{ render-script }}'

I've seen that there's a --loop option but sadly this is for writing filters not entire scripts.
Would something like this be in-scope for this project?
Thanks! :wave:

Does process substitution do what you need?
$ rust-script <(echo 'println!("Hello '"$USER"'!");')
Hello gjum!

:thinking: Hm... maybe I'm holding it wrong or the inner shell is messing up the outer one but this fails:
rust-script <( sed 's/PKG/ssh-openpgp-auth/g;s/KIND/shell_completions/g' <<< '//! ```cargo
//! [dependencies]
//! pkg = { path = "PKG", package = "PKG" }
//! clap_allgen = "0.1.0"
//! ```

fn main() -> Result<(), Box<dyn std::error::Error>> {
    clap_allgen::render_KIND::<pkg::Commands>(
        &std::env::args().collect::<Vec<_>>()[1],
    )?;
    Ok(())
}
' ) '/tmp/xxz'

The error is:
error: failed to get `ssh-openpgp-auth` as a dependency of package `_63_d589d09bfb5f45ea9b4b85e0 v0.1.0 (/home/wiktor/.cache/rust-script/projects/d589d09bfb5f45ea9b4b85e0)`

Caused by:
  failed to load source for dependency `ssh-openpgp-auth`

Caused by:
  Unable to update /dev/fd/ssh-openpgp-auth

Caused by:
  failed to read `/dev/fd/ssh-openpgp-auth/Cargo.toml`

Caused by:
  No such file or directory (os error 2)
error: Could not execute cargo

The following works:
sed 's/PKG/ssh-openpgp-auth/g;s/KIND/shell_completions/g' > .script.rs <<< '//! ```cargo
//! [dependencies]
//! pkg = { path = "PKG", package = "PKG" }
//! clap_allgen = "0.1.0"
//! ```

fn main() -> Result<(), Box<dyn std::error::Error>> {
    clap_allgen::render_KIND::<pkg::Commands>(
        &std::env::args().collect::<Vec<_>>()[1],
    )?;
    Ok(())
}
'
rust-script .script.rs '/tmp/xxz'
rm --force .script.rs

Just for the record I'm modifying this file.
Thanks for your time! :wave:


feature request: oneshot support for drag mode

It would be nice to add the ability of starting keyd directly in drag mode (entering drag mode is the only warpd functionality not scriptable at the moment), so that combined with --oneshot, warpd exits when either the copy or drag key or any mouse button is pressed, while just using the drag mode flag on its own is a convenience feature and combines --normal with the drag mode activation keypress. For consistency, pointer coordinates upon exit could be printed, together with the mouse button pressed (either as a third field, or via exit status).
Background:
I still haven't become completely independent of the trackpoint. Therefore, it regularly happens that I'm on some webpage with the pointer already at the correct position and would like to select some text. This requires first activating warpd and then entering drag mode. In order to save keypresses, I have a keyd macro for this, which first presses the activation key sequence, waits a bit and then presses the key to start drag mode. Now I would like to use the dragging operation in a script, to automate processing of the selected text. Of course, I could probably simulate the needed keypresses to activate normal mode and then enter drag mode by some command inside the script, but there is no way for the script to know if the selection was successful or not or is still active (when you exit with a left mouse click, the selection often disappears). With the above feature, the script could first check whether warpd exited cleanly (so some selection was made) and then use the third output field to infer where that selection is (probably gone if a mouse key was pressed and probably still selected if copy or drag key was pressed, i.e. no third output field present).

I've added this to the latest commit.


WRN-12775: Add a reset skin button.

Checklist

[X] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[X] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Added a button that will reset the skin to the initial state and fixed some minor problems.
Resolution
Additional Considerations
Links
WRN-12775
Comments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.5 out of 13 committers have signed the CLA.:white_check_mark: juwonjeong:white_check_mark: jeonghee27:white_check_mark: sjro:white_check_mark: alexandrumorariu:white_check_mark: adrian-cocoara-lgp:x: Teck:x: JayCanuck:x: RenukaAtale:x: sugardave:x: 0x64:x: YunhoLee0:x: stanca-pop-lgp:x: daniel-stoian-lgpTeck seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update to ASP.NET Core 3.0

Update the solution to target ASP.NET Core 3.0 and add an integration test.

Depends on .NET Core 3.0 support for BundlerMinifier.Core.


Enable the sortable tables scripting

Now that Capital Framework has been updated in this project, the scripting for sortable tables is available. Added an on-demand script that initializes the scripting when tables are used on a page.
Additions

Added on-demand script to initialize cf-tables code when a page includes a table

Testing

Locally, turn on the sortable tables flag

Create a page with a table inside a full-width text module, enable sortable table functionality and set the sorting options.

Save page and view it in the browser

Click the headings and the table should resort itself.

Notes

There is a bug in the chart builder override file causing the heading colors to be incorrectly set making it dark on dark. This needs to be fixed separately, but because the sortable functionality is behind a flag, it will not be an immediate issue.

Todos

Update CF to use real variables to avoid override bugs

Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows the standards laid out in the development playbook
[x] Passes all existing automated tests
[x] New functions include new tests
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged
[x] Visually tested in supported browsers and devices
[x] Project documentation has been updated
[x] Reviewers requested with the Assignee tool :arrow_right:

I'M FIXING THE CHART BUILDER VARIABLES FILE NOW!!! 😿 sorry yall

@jimmynotjim, please check this on IE.

@sebworks is there a specific problem you're seeing? This has already been extensively tested in IE9 and up as part of Capital Framework. We're not adding anything new here, just initializing it.

I'm not sure why the package-lock.json file is being updated.

@sebworks is there a specific problem you're seeing? This has already been extensively tested in IE9 and up as part of Capital Framework. We're not adding anything new here, just initializing it.

Can you edit the component in Wagtail using IE?

@jimmynotjim, looks like it's this line https://github.com/cfpb/cfgov-refresh/blob/639bd89607bd69093ef9de3626522e4e23c2b088/cfgov/templates/wagtailadmin/js/table-block.js#L433, which is using es5. We don't run these file through babel.

looks like it's this line, which is using es5. We don't run these files through babel.

That code came from the fixed width input tables, which means it's broken there too.
This issue is outside the scope of this PR, there was a previous PR for the admin. This PR is only initializing the scripting on tables that have already been created. Unfortunately I'm out for the next three weeks, hopefully someone else can pick up the admin issue while I'm gone.

I'm not sure why the package-lock.json file is being updated.

I don't understand that either, it seems to be happening randomly on every repo I've worked on.

ok, just drop the change in the package-lock.json and I think it's good.

@sebworks reverted the package-lock.json changes


pathes from require incorrectly resolved

look into Lupa issue: https://github.com/hex13/lupa/issues/4

fixed


change default endpoint to host action to ACCEPT

this was missing in /master

Could you update the etcd and kubeadm manifests as well?

@caseydavenport done! (although I don't fully understand why this is needed for etcd backend)

@gunjan5 we shouldn't be changing the v1.5 and v1.6 manifests here, just the ones in v2.0
v2.0/standard
v2.0/kubeadm
v2.0/etcdless

although I don't fully understand why this is needed for etcd backend

The datastore should change this behavior.  I don't fully understand why you saw it with one and not the other :)
Perhaps you had configuration in etcd somehow?  This value can be configured in etcd.

@gunjan5 pong, back to you

@caseydavenport:

we shouldn't be changing the v1.5 and v1.6 manifests here, just the ones in v2.0

I looked at Felix code and both v1.5 and v1.6 had that flag, so I thought we should have the same behavior, no?

although I don't fully understand why this is needed for etcd backend

The datastore should change this behavior. I don't fully understand why you saw it with one and not the other :)
Perhaps you had configuration in etcd somehow? This value can be configured in etcd.

Nope, didn't even touch etcd.

I looked at Felix code and both v1.5 and v1.6 had that flag, so I thought we should have the same behavior, no?

Was mostly concerned about changing behavior under people's feet.  I usually don't like the idea of changing a manifest from a previous release.  In this particular case, I suppose it's acceptable, but I'd like to limit the amount of changes we make to v1.5, v1.6, etc because users are relying on consistent behavior from past releases.

@caseydavenport done. I wasn't sure what you meant by v2.0/standard, but I've changed the systemd file for v2.0 and master.

@gunjan5 you're missing v2.0/k8s-backend

@caseydavenport that change was already merged I think when you cut 2.0.2: https://github.com/projectcalico/calico/blob/master/v2.0/getting-started/kubernetes/installation/hosted/k8s-backend/calico.yaml#L77

Hmm.. not sure what's up with the build.

@caseydavenport Rebased, and the CI works now :)


Check whether a Camtrap DP data license is a valid GBIF license

In Camtrap DP, one can indicate two licenses: one for the data and one for the media files. This is currently implemented as such in the IPT:

The IPT does currently check whether the license for the scope data is one of the following CC0, CC-BY, CC-BY-NC. That is good! The values are incompatible however. IPT requires CC0, CC-BY, CC-BY-NC, while Frictionless requires an Open Definition license ID, i.e. CC0-1.0, CC-BY-4.0, CC-BY-NC-4.0
I would update the interface a bit:

[ ] Rather than a list of licenses, provide 2: Data license and Media license
[ ] Remove the Title field, it can only lead to conflicting information
[ ] For Data license:

[ ] Make it a required field
[ ] Offer a dropdown with the 3 GBIF licenses

[ ] For Media license we need to assess if we want to set requirements, but imo:

[ ] Don't make it required
[ ] Offer a dropdown with all Creative Commons licenses

[ ] Decide whether GBIF services want to use name (CC0-1.0, CC-BY-4.0, CC-BY-NC-4.0) or path for importing, exporting and interpreting datapackage.json information. I would opt for name as those values are controlled. Camtrap DP could be adapted to require name (rather than name or path)

Oh, I forgot about that! 😄 Good to have decisions coded in specs, let's make both licenses required, it's the proper thing to do anyway.

I assume using name would be more convenient


Grapheme subgraphs.

Fixes #20. This introduces grapheme subgraphs, which are inserted into graphs when multi-character graphemes are encountered. This allows for repeated character matching to take graphemes into account. while also matching on a per-character basis.

Codecov Report

Merging #22 (366f263) into master (fd823f7) will decrease coverage by 0.49%.
The diff coverage is 79.88%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
- Coverage   89.36%   88.87%   -0.50%
==========================================
  Files           4        4
  Lines         809      881      +72
==========================================
+ Hits          723      783      +60
- Misses         86       98      +12

Impacted Files
Coverage Δ

src/node.rs
72.99% <57.35%> (-17.71%)
:arrow_down:

src/lib.rs
86.18% <89.65%> (-0.03%)
:arrow_down:

src/walker.rs
95.55% <96.10%> (+4.59%)
:arrow_up:

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 fd823f7...366f263. Read the comment docs.

As a side note, this contains some further work towards #17, although it isn't yet implemented on WordFilter itself, due to the function pointer.


Updates to new value

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[X] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[X] Read the contribution guide
[X] Commands include options for Linux, MacOS, and Windows within codetabs
[X] New file and folder names are globally unique
[X] Page references use shortcodes instead of markdown or URL links
[X] Images use HTML style and have alternative text
[X] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
During code review it was decided the value should be changed in Dapr, so this PR updates the docs. I'll mark this PR as ready for review as soon as the code PR gets merged.

The code PR got merged, we can now merge the docs PR.


Weird behavior when the mouse is moved outside the window and then in again

Open the demo at http://s.codepen.io/FezVrasta/debug/VepyPV
press TAB and the text will become red (correct!)
move the mouse outside of the window, the text is still red (correct!)
move the mouse inside the window, the text is not red anymore (not correct!)

I would expect the text to stay red till I actually use the mouse to click somewhere.

This is an issue that I've juuuuuust been debating about changing. Right now mouse detection happens on click and on mouseenter. I hesitate using mousemove to keep the performance impact minimal. So what you're seeing is "correct", but a bit inconsistent.
Do you think mousemove should be used? So any mouse movement (heavily debounced) would remove the red from your text? Or only clicking with the mouse would remove the red? I suspect most people are wanting more sensitive detection and would prefer mousemove.
Thanks for using it!

I don't think mouse move should be used at all, this script is used to change the style of the :focus state of the elements when an user switch the input method.
If you press tab and then move the mouse, you don't want the button to lose its "focus state", you want it to lose its "focus state" only if you CLICK on an element (doing so, you would see the focus state assigned to the keyboard input, so you change it to mouse because IS needed).
I hope you get my point.

I built it to do more than styling focus states (though that's how it originated). The API allows you to hook into it for scripting for multiple input types. For example, I've used it when building hover-triggered menus to script alternate interactions for touch and keyboard.
Some people have reported "bugs" when a keyboard focus state persists when switching to a mouse.
It sounds like, in your instance, would it be preferable to use the same focus style even if a mouse is detected?

No, sorry.
I mean, right now this is the behavior:

click on a button, apply mouse style (you have clicked the mouse!)
press tab, apply keyboard style (you have pressed a button!)
move the mouse, apply mouse style (you have moved the mouse)
move the mouse over the keyboard without touching any key, apply keyboard style (you have hovered your keyboard? umh)

As you can see, you are script should know if you are hovering your fingers on the keyboard to behave consistently.
This is not possible, so you should be consistent in the other way:

click on a button, apply mouse style (you have clicked the mouse!)
press tab, apply keyboard style (you have pressed a button!)
move the mouse, do nothing (you have moved the mouse but you will not say "ahg! why this button has a blue outline? because you know it got the outline when you pressed tab)

Hope it's more clear now.

I think this is too subjective. @ten1seven you might want to leave this decision to the developer. Wouldn't make sense to expose an API to set the events to be listened?
Default would be the way it is now; and @FezVrasta would be able to call something like .detectionEvents(['click']) and others could do .detectionEvents(['click','mousemove','mouseenter']), etc.
Or at least, maybe provide some kind of configurable threshold for each input: hover > action > none. hover being basically the most "sensible" detection (includes actions as well), action being what @FezVrasta  expects, and none is I don't want to detect this input type at all.

It could be a solution. but I think that the solution I propose is just what the user expects.

@FezVrasta @luisfarzati thanks for your comments and suggested solutions on this. I'm still puzzling through the best direction. At this point I'm hesitant to change the behavior that people (developers) now expect.
mousemove detection was only recently added as a way to detect mouse usage as soon as possible to minimize the time of ambiguity after the page loads.
When typing in form elements, the input method of keyboard isn't triggered if someone was using a mouse. However, currently the tab key will still trigger a switch from mouse to keyboard. @FezVrasta is this the main use case you're thinking of -- tabbing within a form?
I'm wondering if adding tab to the list of ignored keys when interacting with a form for a previously-detected mouse user would make the most sense? I want to keep quick detection of input switching in place because What Input is also useful for scripting multi-input interface elements.

No the main problem is just that if I've an input focused (because I used the keyboard) and I accidentally move the mouse out and then inside the window, I don't want to lose the focus effect I've applied.

Not sure how I feel about doing this all the time, but your concern is valid and seems to be focused around form inputs -- when a mouse user is using the keyboard. Check out the form-input-switching branch with a solution that locks in the input type when interacting with form elements. This goes both ways for mouse and keyboard users. I haven't updated the demo so you'll need to pull it down and run it locally or drop it in your project.
Let me know what you think.

@ten1seven Why do you think a "mouse user" or "touch user" wouldn't want a focus ring or outline? There are many users who could use all 3 of these combinations (keyboard, touch, mouse) at the same time and could appreciate knowing which element is currently focused in the UI.
For users with cognitive disabilities, low vision, and/or mobility disabilities could find it very confusing to have focus state removed from them while bouncing from one input method to another.
If used to remove outline when the mouse is used it would fail WCAG 2.0 AA 2.4.7 Focus Visible

@joe-watkins thanks for commenting! You have a valid point and one that I thought through a bunch when considering this request. Forms are so tricky in that they're the one place where mouse users become keyboard users. Here's my thinking on it -- though I"m happy to debate in the name of making the web better 😄

In the instance of interacting with a form, I'm hoping that good focus indication is being used for everyone.
Sometimes elements that accept and hold focus, like buttons, are used in the interface where allowing mouse users to see a focus state might look like a bug.
Default focus styles are inconsistent. In fact, Firefox's are pretty terrible and difficult to see. What Input helps developers make those styles more consistent and visible while satisfying designers and clients who (almost always in my part of the industry) don't want to see them ("hey, what's that blue fuzzy outline all about?" -- actual question from a designer once).
I added the ability to turn off this behavior if you need via <body data-whatinput-formswitching>.
What Input was built to help get accessibility (better focus indicators) into sites where it normally would get left out.

What do you think? Have you used this script and don't like the feature change? Or do you object to the idea of trying override the browser's focus behavior at all?

@ten1seven It's very obvious accessibility is on your mind here and I don't wish to harsh on the hard work you've put in here but I do feel it's worth chatting about since your project is very visible to the dev community.. Foundation even uses it.
I'm very much in the camp of don't mess with outlines unless you are enhancing/styling them.
Designers
Modern/Professional web designers have embraced accessibility & the focus states. They've learned to accept them as a design challenge. If your designer isn't including that state with hover states in their creative deliverable they might need to be educated the importance of them.
Clients
The same goes with the client... this is a perfect opportunity to educate the client. If the browser's native focus ring feels like a bug the designer/client should be educated that it is a browser feature for people. These focus rings can be styled to match brand guidelines.
You can point the client here to get them onboard w/Accessibility if they lack empathy. List of Web Accessibility-Related Litigation and Settlements
Focus States
While some browsers handle focus state a bit differently they all allow you to style them so there is consistency across the board.
a:hover, a:focus {
  outline: none;
  border: 1px solid red;
}

Inputs
Take a peek at some of these alternative input mechanisms:
http://www.orin.com/access/sip_puff/
http://www.bltt.org/hardware/joysticks.htm
http://www.bltt.org/hardware/keyboards.htm
http://www.bltt.org/hardware/switches.htm
A user could be leveraging inputs like those in the links above along with a keyboard, mouse, eye tracking software,touchpad and more on a touch device. How can we assume what input they will use or depending on what input they've chosen they DON'T want/need a focus state??
This very basic accessibility feature is baked into the web for free.. why are we trying to remove it under certain circumstances based heavily on assumptions?
I do see how understanding more about the user's inputs could help here and there but outline:none; is at epidemic levels and is the #1 reason why I fail websites when performing accessibility audits.
I want to understand why a user's dependency on a focus state would change based on what input device they are using? If an element can receive focus and the author has defined a focus state it is my belief that should be universal and available to all users and again is a WCAG 2.0 AA guideline recommendation.
This is worthy of it's own issue and appreciate your open mind :) Would you consider adding a note to the README about possible accessibility concerns near the Styling Example?

Oh man, if everyone was that educated and understanding this script wouldn't be necessary and I'd be fine with that 😄
Thanks for the thorough response! It sounds like the usage you're suggesting is:

Links don't hold focus like form controls when you click on them (like a button will) so leave the focus state on these alone or only enhance the styling but otherwise don't use What Input to style them because the browser does just fine.
Form inputs should always have some kind of focus indicator, but What Input could be used to enhance it if desired.
Since buttons used as UI elements outside the context of a form will still take and hold focus when clicked (ex. a button used as a hamburger menu toggle), this can be viewed as a visual bug by mouse users. This is the exact case where What Input was created and, I think, is an acceptable compromise to maintain a focus style for keyboard users while using the best semantic element for the job and not introducing a "buggy" experience for mouse users.

Every time I hear about What Input being used, it's to solve this last point. You've definitely got me re-thinking the feature the thread was based on and maybe some clearer documentation on usage would help as well. Does that cover your concerns?

@ten1seven :) Tnx for responding.. The last one is the bugger.  Here is a great example of focus state being part of the design..it doesn't have to feel like a bug. If your plugin was running here I'd lose that handy state when navigating through the side nav and moving mouse..that'd be a bummer.
Video Screencast of University of Washington's offscreen nav
My concern would be addressed by adding to the documentation somewhere (ideally next to the code chunk where you suggest removing outlines) that if you remove outlines and don't provide a backup you harm accessibility and which could make you fail WCAG 2.0 AA 2.4.7.
I'd be happy to create a PR for this.

Ah, I see a little more how you're viewing it. In my work I use it to add really visible focus indicators to existing focus/hover styes. Here's an example: http://d.pr/v/19FZ6
However a well-intentioned tool used incorrectly will still result in poor outcome.
I'd love to get your edits on the documentation on how to more accurately use it!

@ten1seven That demo is slick! I surely see how when used properly it could add to the experience. Those are some spiffy underlines on those links as well!
I'll fire up a PR for your review on this topic.


[BEAM-9053] Improve error message when unable to get the correct file…

…system for specified path in Python SDK
PR to improve the error message when not getting the correct filesystem from the specified path. Getting something more helpful now:
"Unable to get filesystem from specified path, please use the correct path or ensure the required dependency is installed, e.g., pip install apache_beam[gcp]. Path specified: %s"

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[X] Choose reviewer(s) and mention them in a comment (R: @username).
[X] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @kennknowles


https://aka.ms/xboxliveuwptools link is broken.

The standalone tools link is broken.

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

ID: 35971a80-8b95-9201-2133-bfa4e4cddeca
Version Independent ID: 2e574f12-313c-b28d-863d-46d3054a27de
Content: Xbox Live Account Tool - UWP app developer
Content Source: windows-apps-src/xbox-live/tools/xbox-live-account-tool.md
Service: unspecified
GitHub Login: @KevinAsgari
Microsoft Alias: kevinasg

Thanks for reporting this!  I've alerted the team that owns the tool, and they're investigating.

No problem, thank you.

Looks like they fixed the issue now, you should be able to download the tools again.


PodFrequentlyRestarting still active even though the container was removed

What did you do?
Pod that was tripping PodFrequentlyRestarting alert got removed (there are no more metrics for kube_pod_info for the pod).
What did you expect to see?
Alert is not active anymore.
What did you see instead? Under which circumstances?
Alert was active for some time after the pod was non existent.
Environment

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.1", GitCommit:"3a1c9449a956b6026f075fa3134ff92f7d55f812", GitTreeState:"archive", BuildDate:"1970-01-01T00:00:01Z", GoVersion:"go1.9.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:

Kops cluster

Manifests:

Kube state metrics used:
 gcr.io/google_containers/kube-state-metrics:v1.2.0

Prometheus Operator Logs:

Not relevant to prometheus operator

Example graph showing the event

info = kube_pod_info{pod="POD"}
restarts = kube_pod_container_status_restarts_total{pod="POD"}
increase = increase(kube_pod_container_status_restarts_total{pod="POD"}[1h]) as used by the rule
firing = ALERTS{alertname="PodFrequentlyRestarting",pod="POD",alertstate="firing"}
ALERT definition (as provided by kube-prom)
alert: PodFrequentlyRestarting
expr: increase(kube_pod_container_status_restarts_total[1h])
  > 5
for: 10m
labels:
  severity: warning
annotations:
  description: Pod {{$labels.namespace}}/{{$labels.pod}} was restarted {{$value}}
    times within the last hour
  summary: Pod is restarting frequently

+1, experiencing the same issue.

Thanks for opening this issue!
We should join the kube_pod_info metric onto the query, I believe then the alert should be instantly resolved as that metric won't exist anymore. Currently this happens, because the increase function's range query is 1 hour so it will look at the past hour of data, which is why the result set has data for up to 1 hour after the pod was deleted. As this alert is actually defined in this repository: kubernetes-monitoring/kubernetes-mixin, we should take the discussion there. Would you mind opening the issue there @atopuzov?

@atopuzov Is there an issue for this topic?
@brancz Could you tell how the kube_pod_info metric can be joined into the query?

@BenjaminHerbert sorry I don't work with k8s anymore so I don't know.


Create gradle-wrapper-validation.yml

Official Gradle Wrapper Validation Action
See: https://github.com/gradle/wrapper-validation-action

Maybe we should not add a separate action but instead adjust the existing ".github/workflows/gradle.yml" to follow the official Gradle starter workflow which includes checksum validation? @abhijeetnarvekar what do you think?
https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-java-with-gradle

@Thilo-Acrolinx Yes, it would enough to add it as a initial step in the existing job, which could act as guardrail. If wrapper is compromised there is no need to execute anything further


Minor improvements

Description
This PR provides minor improvements:

It improves MxM example to dump all raw timers to be processed by external tools (e.g., R)
It simplifies detection of parallel kernels per backend.

Problem description
n/ a.
Backend/s tested
Mark the backends affected by this PR.

[X] OpenCL
[X] PTX
[X] SPIRV

OS tested
Mark the OS where this PR is tested.

[X] Linux
[ ] OSx
[ ] Windows

Did you check on FPGAs?
If it is applicable, check your changes on FPGAs.

[ ] Yes
[X] No

How to test the new patch?
make
make tests

tornado --jvm="-Ds0.t0.device=0:0" -m tornado.examples/uk.ac.manchester.tornado.examples.compute.MatrixMultiplication2D 512 false

LGTM, one comment is that we are modifying an example from the compute package to showcase this feature of dumping stats related to execution time for further analysis. We could probably decouple this functionality into a separate package that will be used to show how to do the analysis and potential integration with other tools.
This is a thought.

Yes, I agree. We can extend the benchmark module. I suggest moving this one forward to create the requested demos for EU AERO Project.


Interface not showing up while watching a tv show

Docker running on Windows 10
I'm fairly new to docker, I don't know if my installation went correctly
Interface die after refresh, even after restarting the container
Installed it few hours ago
Using that docker-compose file https://github.com/CyferShepard/Jellystat/blob/main/docker-compose.yml
Happened during while watching a tv show, I took a break mid watching, about 15min, then saw the issue showed bellow
Tested on Firefox, Chrome, Edge, same results
Stopped after the episode was over
A gif might help understanding what I mean

Anyway thank you, excited to see how it will evolve :^)

After multiple attemps, I wasn't able to reproduce that behavior
Sadly I have a bad habit to clear caches/cookies/storage from the browser when it starts doing weird things, that's what I did yesterday
I'll try again and let you know if it happen again
Let's wait a few days and if nothing happen, maybe we can close that issue, might have been a one time thing
If I recall correctly I launched the "Synchronize with Jellyfin task" (for the first time) before it happened but can't be sure if it happend during, or right after

Hi @monheimx9 , no worries, someone else is having a similar issue aswell, im currently looking into it so hopefully it doesn't come up again

Possibly Caused by #18 , need to investigate

I am faceing the same issue,
after login, the screen is blank,
when I press F5 it shows the interface for a few milliseconds
I tried with firefox and chrome

Hi @MrCaringi , will you be able to send me the logs? Press F12 in your browser, go to the console and send me a screenshot of whats there after you reload

Can you also tell me if either Jellystat or Jellyfin is proxied with a baseurl. eg jellystat.local/jellystat/ or jeelyfin.local/jellyfin/ or anything similar

Sure!

thanks for your support!

Can you also tell me if either Jellystat or Jellyfin is proxied with a baseurl. eg jellystat.local/jellystat/ or jellyfin.local/jellyfin/ or anything similar

Im using it locally (local DNS in my LAN)

Hmm, this looks like its trying to show an item that was recently added that does not have an image, can you let me know if this is the case? in the mean time il try to address that issue

Hi @MrCaringi , a fix has been pushed, can you let me know if the latest version helps with this error?

Hi @MrCaringi , a fix has been pushed, can you let me know if the latest version helps with this error?

Sorry for late reply!
Yes! I had a movie without thumbnails (the folder was missing and there was a error when I tried to remove it).
I fix this issue (recreating the missing path and rescanning, then I was able to delete it successfully from web-interface)
but this does not fix the problem.
Then I pulled the lastest docker image and it worked!!!
thanks a lot!

No problem, glad its now working.


Bundling Openlayers with Ionic2/Angular2 AoT compilation

When Openlayers is bundled, an error occurs when the bundled js file is loaded.
In the beginning of ol-debug.js we have the following code:

;(function (root, factory) {
  if (typeof exports === "object") {
    module.exports = factory();
  } else if (typeof define === "function" && define.amd) {
    define([], factory);
  } else {
    root.ol = factory();
  }
}(this, function () {
  var OPENLAYERS = {};
  var goog = this.goog = {};
this.CLOSURE_NO_DEPS = true;
...

Usually this represents the window. In the bundled version after AoT compilation, this is undefined when the js file is parsed and thus an error is thrown => Uncaught SyntaxError: Unexpected identifier
Steps to reproduce:
npm install -g ionic cordova
ionic start someName --v2
cd someName
npm install openlayers --save
npm install @types/openlayers --save

In src/declarations.d.ts add declare module 'openlayers';
In a component (e.g. src/pages/home/home.ts), add import ol from 'openlayers';
call something like ol.extent.createEmpty() in the components constructor (unused imports are not bundled)

ionic serve
=> empty page - parse error in main.js

I'm running into this issue as well.
The current work-around is to include ol.js with a script tag on index.html, rather than including it in any js/ts files (which would trigger it's inclusion in the AoT compilation).

Ionic updated their build script to use Webpack 2 instead of Rollup. Works now like a charm.


Add a rank-k update gufunc (i.e. SYRK)

Overview
This PR adds a new function update_rankk which implements a gufunc for the BLAS3 functions ssyrk and dsyrk.
Complex valued support (csyrk and zsyrk) can be added in a follow-up PR later if needed.
The transpose_type and UPLO argument names match the names used by other gulinalg functions.
Additional Info
Reference documentation for syrk
Note: currently the default values of 1.0 for alpha and beta parameters are used as in other gulinalg functions.

This first commit here is from #1, the rest are specific to adding syrk

@teoliphant, @Carreau: This PR corresponds to https://github.com/Quansight/deshaw/issues/102. It should be working now if either of you can do a quick review
I tested locally with the following two environments on linux:

Python 2.7.15 + NumPy 1.16.5 + libopenblas 0.3.12
Python 3.8.5 + NumPy 1.19.1 + libopenblas 0.3.10

This repository is still configured to use nose, so if it is installed you can run the tests using:
python gulinalg/tests/test_gufunc_general.py

or via pytest
pytest gulinalg/tests/test_gufunc_general.py -v

Also, who would have access to enable Travis-CI for this repository? I don't see Quansight listed under my organizations on travis-ci.org, so I don't think I currently have the permissions needed to do it.

I've also requested github access for travis-ci, and admin needs to approve.

Travis now looks good aside from a handful of test failures unrelated to this PR. I can probably just change atol from 0 to something like 1e-14 for these TestSolveTriangular tests.

I fixed up the doctests and updated the Travis config so that everything is green.

Thanks for reviewing @Carreau. I plan to merge tomorrow morning if there are no further comments before then.


Verification tools

Currently the coordinator performs "partial" verification on chunks and doesn't perform the "ratio" checks.
While this isn't strictly necessary to have this in the service code base, it'd be good to have a process (either a program or a script) that, when the ceremony finishes, performs the following:

Collects the chunks
Combines them
Runs the ratio check

Done in https://github.com/celo-org/snark-setup-operator


Brotli requires nginx 1.16, I have nginx 1.17

Hi, I'm having a problem with yum install nginx nginx-module-nbr... it appears that I have nginx 1.17, but the Brotli plugin requires 1.16. Is that correct? And if so, is there a newer Brotli plugin I can install?
# yum install nginx nginx-module-nbr

Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * base: mirror.mojohost.com
 * epel: d2lzkl7pfhq30w.cloudfront.net
 * extras: mirror.mojohost.com
 * nux-dextop: mirror.li.nux.ro
 * updates: mirror.mojohost.com
 * webtatic: us-east.repo.webtatic.com
Package 1:nginx-1.17.2-1.el7.ngx.x86_64 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package nginx-module-nbr.x86_64 1:<IP_ADDRESS>.1.2-1.el7.gps will be installed
--> Processing Dependency: nginx = 1:1.16.0-1.el7.ngx for package: 1:nginx-module-nbr-<IP_ADDRESS>.1.2-1.el7.gps.x86_64
--> Finished Dependency Resolution
Error: Package: 1:nginx-module-nbr-<IP_ADDRESS>.1.2-1.el7.gps.x86_64 (getpagespeed-extras)
           Requires: nginx = 1:1.16.0-1.el7.ngx
           Installed: 1:nginx-1.17.2-1.el7.ngx.x86_64 (@nginx)
               nginx = 1:1.17.2-1.el7.ngx

This is not the official RPM package of eustas/ngx_brotli I would not even be surprised if there are "untrusted code". For all questions, you can ask the maintainer packages (*.getpagespeed.com) @dvershinin

This is not the official eustas/ngx_brotli RPM package.
For all questions, you can ask the maintainer packages (*.getpagespeed.com) @dvershinin

Hi @denji -- thank you -- yet I am still confused by all of this. :-)
There is, somewhere, a Brotli "plugin" (module) for Nginx. It supports only Nginx 1.16.
The official one appears to be here https://github.com/google/brotli... though it also appears totally dead (nice job Google). Many posts there refer me to here, https://github.com/eustas/nginx-brotli. But I realize this isn't the official version. That said, it does seems to be maintained, at least more than the official Google one.
You mentioned @dvershinin who has a site GetPageSpeed (which is awesome).  Which is great and pretty cool, but more than what I'm seeking.
Is anyone maintaining the official, standalone, nginx-brotli plugin any longer?!

@pnoeric I think you're confusing few things there. Namely source repository vs RPM packages repository.
Source (GitHub, where code is hosted): there is one official repository, and that is google/ngx_brotli. For reason largely unknown it was "abandoned", and this eustas/ngx_brotli seems like a continuation of it, maintained by a Google employee (AFAIK), has more fixes/updates compared to the official. So more or less it can be considered official for all intents.
RPM (where binary builds for the module hosted): The only official repository for binary builds would be the one for Nginx Plus. Naturally, it requires you to have Nginx Plus.
If you don't make use of Nginx Plus, your choices are either:
1. Build the module yourself.
This puts a requirement of:

setting up the build environment (and keeping it secure, it should go without saying that installing compilation software on production systems should be avoided).
having to rebuild the module for each new release
dealing with SELinux issues if you custom compile/install NGINX to non-standard (per policy) locations; unfortunately, most of people just end up disabling SELinux altogether

2. Use community packages/repositories
In my line of work, I install and configure servers. NGINX supported dynamically loadable modules for years now, but I only saw the community creating some monster NGINX builds where modules are compiled in statically.
So I saw it's a natural path for me to compile/package modules separately. This is what Nginx Plus does and I built the same + a bit more, and put it for public use.
The GetPageSpeed repository is in no way official and you bear the risks associated with using a third-party repository like GetPageSpeed extras repository.
The modules there are built for NGINX stable branch (you use mainline), which is why it doesn't work for you. If you switch to use of stable NGINX, you can then install the package normally.
The choice to build modules for stable branch of NGINX was due to likely better "code API compatibility" and greater availability of modules that successfully compile for it.
You don't need to install all of the modules. In theory and in practice you can:

Add nginx stable repository to your system and set it to be of highest priority with yum options
Add GetPageSpeed extras repository
Then install nginx-module-nbr - result would be that nginx binary package will be fetched from official repository, while the module will be fetched from extras.getpagespeed.com

P.S. nginx-extras is not a module that installs everything, but merely a collection of those. You can install NGINX with just the modules you want, as in yum install nginx-module-<module name>, similar to Nginx Plus.

Thank you very much @dvershinin  - this is really the most awesome, clear, and useful explanation of what's going on and all the different moving parts. (Truly: I wish your post was on the front page of both the official brotli repo and the front page of this repo.... it provides the context that was missing.) I appreciate you taking the time to explain it all.
So, ok, I get it. Nobody out there has compiled brotli as as standalone module for my specific version of nginx. Sounds like I should look at changing to the stable branch of nginx and then I can also enjoy all those sexy things you're doing at getpagespeed.com.
Just one question, then. Will anything screw up if I want to change from my current nginx to the stable branch? Can I just switch on the fly on my server? Ugh this makes me nervous - I have a popular live web site and I'm a great coder but not a great sysadmin...

@pnoeric building mainline packages is something I had in mind, however, it's not as sexy as stable because updates are not super-automatic for now.
Still, it might be worth trying to install the package from the "mainline" repo I built today (has only brotli module for now).
Try these steps to install the module package for the mainline NGINX:
yum -y install yum-utils
yum clean all && yum update getpagespeed-extras-release
yum-config-manager --enable getpagespeed-extras-mainline
yum install nginx-module-nbr

This fork is merged back to google/ngx_brotli. Please recreate this issue there (if necessary).


Signalr & CORS

Hi .
I'm using signalr and jquery ajax  (that connect to a  Soap Webservice) in a page together .
When I enable CPRS  from web.config
 <httpProtocol>
      <customHeaders>
        <add name="Access-Control-Allow-Origin" value="*"/>
        <add name="Access-Control-Allow-Headers" value="Content-Type"/>
      </customHeaders>
    </httpProtocol>

the webserice work well but signalr can't establish connection with this error :" Error: Error during negotiation request. " and when I comment these lines in web.config and enable CORS in Startup.cs the Signalr work fine but jquery ajax alert CORS have to be enable to connect .
I want to connect from localhost to internet server .
how can I do ?

At DyKnow we have been using SignalR-ObjC with a Server configured for CORs with success.  If you can provide more detail or a sample that would be appreciated


[jest-each] Template table heading validation and extraction

Summary
Currently any additional words in a template will break jest-each's expected behaviour of injecting the template headings as variables to the test function.
For example:
test.only.each`
  a    | b    | expected
  This test demonstrates jest-each
  ${1} | ${2} | ${3}
`('$a + $b == $expected', ({a, b, expected}) => {
  expect(a + b).toBe(expected);
});

This test will fail as expected equals undefined.
That is because currently jest-each splits on | and removes whitespace so the expected key is actually deserialised to expectedThistestdemonstratesjest-each which is not correct.

The proposed solution to this is to validate the headings to make sure there are no additional words in the first row (heading row). Any words appearing after the first row are simply ignored by jest-each.
By ignoring the additional rows user's are able to add whatever they like - currently though prettier does strip out all additional text in the template after the first interpolation (${variable}), perhaps it is worth investigating how to prevent that.
This PR relates to point 2 in this comment
Test plan
See tests
EDIT: the above example will also now pass

Okay now I see what you mean. Just ignoring lines that do not match the expected format gives the possibility to put headlines in between, unrelated to any comment/skip API though.
It seems kinda magic and not like something I'd recommend people to do though. And doesn't work if there's just one parameter I guess.

@jeysal It should work fine even if there is only one heading/param (see b64b6428cb83829d471b353546e877d3de72f4a4) :smile:
I'm not sure I agree that it's a breaking change, I doubt anyone does depend on this behaviour and it definitely is a bug (well is an unintended behaviour) and needs fixing.
I agree about not recommending people to add subheadings/additional text to the template - at least this way we do not put semantics (and code) around // syntax.
I suspect if we want to support a convention around this then it will need a little more thinking about. By fixing this behaviour it doesn't prevent people adding custom text should they want to in the meantime.

I'm not sure I agree that it's a breaking change, I doubt anyone does depend on this behaviour

Not with
a | b
some thing

'$a => $bsomething'

perhaps, but quite possibly with
a | some thing
${1} | ${2}

'$a => $something'

I don't think this should be considered a breaking change. Although it is true that someone's test would break with a b | c, this is a bug and (most likely) unintended by the user.

Are there any updates on this (and/or #8717)?

@mattphillips ping 🙂

I think this is still good to go, but I would still say it's breaking because the example I gave in my last comment (using the behavior in headings) is actually not that far-fetched. Also, it's been lying around so long, might as well play it safe and put it into a major.

@jeysal rebase and land?

@jeysal would you be able to take a look at CI?

I think the new snapshots it's trying to write look appropriate. pushed them


Update to 00_CSV_Import.md

Adding further explanation for using a custom CsvBulkLoader in ModelAdmin instead of the default one. I think some people might be able to guess at this, but others (like me) might benefit from making things a bit more explicit. This is a follow up from my question on StackOverflow.

thanks


Implement the BallerinaFutureTypeBuilder in Types API

Description:
$title
Related Issues:
Subtask of #35415

Completed by #35850


Dune wrapper to check that the current switch is up to date

This PR adds the check_opam_switch tool to the repository. This tool can be used to quickly check that the current opam switch contains the packages specified in the opam.export file at the correct version.

This check is added to the Makefile if the check_opam_switch binary is in the PATH (ie. if we are not using the pure nix shell).
The dune_wrapper executable can also do this check before executing dune, in order to discover early that the opam switch needs to be updated.

Left you a few comments, but I really love the direction here! If I could use this tool to do more things and replace dune completely it would be perfect (run tests, build specific parts of the code, open utop, etc.)

Thanks for the comments, I addressed them in this new version.

The tool is now fully written in OCaml, in an opam package that is not project specific. This PR adds it to the src/app
folder (which is simpler for the review), but it could also live in another repository.

There is now a README.md file that explains how to use the binaries. In particular how to setup an alias to use the dune wrapper transparently.

is there a way to get this in in develop now?

Yes, I was waiting on an answer about creating a repository on the MinaProtocol org for the tool.
But until then I will create a repository on the tweag org tomorrow and try to open a PR.

Replaced by PR #11569 and #11570 for compatible and develop, which install the tool from an external repository.


running scripts/createLanguage.ts got an error

I was trying to create a zh-cn copy for tsconfig-reference, and following the contributing guide:

If you'd like to create a new language:
Do you plan on making an evening or two on it and go all out? then you can use the script ./scripts/createLanguage.ts to set up a new language.

but got an error like:

/Users/weiran/repo/github/TypeScript-Website/packages/tsconfig-reference/scripts/createLanguage.ts:24
options.forEach(opt => {
        ^
TypeError: options.forEach is not a function

not sure if I missed something, or a bug in here?

Oh yeah, I've not been keeping that up to date. I think I'm just going to remove that script entirely - thanks!


Trim type name used for hashing and returned from entt::type_info::name()

Right now the type name used for type hashing still contains some remnants from pretty function that could be trimmed of.
Example:
struct Components::MyComponent
becomes
struct Components::MyComponent>(void) noexcept
the noexcept bit is not necessary for the type name.

I'm closing this as we discovered from a chat on Discord that the error was somewhere else and the noexcept token is already stripped out as expected. 👍
Thanks for helping to investigate it down.


raw.githubusercontent.com blocked as of 1/1/23

Context for this issue is available here.
h/t @championswimmer

An update:
ACT Fibernet responded to the news of the raw.githubusercontent.com host being blocked on their network. Separately, the January 7, 2023 update  to the list of blocked hostnames provided by this project include the githubusercontent.com. apex domain.
I will be closing this issue for now as I don't expect any further developments or public updates to this - given the opaque nature of web blocking and censorship in India.

The GitHub content domain was unblocked on January 10, 2023.
An article about this can be found here.


[Segment Replication] Refactor RemoteStoreReplicationSource

Description
Refactors the RemoteStoreReplicationSource to align with existing node node implementation.

Uses ReplicationCheckpoint taken from remote store instead of re-using replica's ReplicationCheckpoint. In order to do that, updated the RemoteSegmentMetadata to store ReplicationCheckpoint
Refactors SegmentReplicationTarget to be re-used for remote store.
Segregates shard level tests for node to node and remote store segment replication.
Updated remote store unit test classes to correctly use RemoteStoreReplicationSource.

Request review from

@sachinpkale for core changes (addition of replication checkpoint to uploaded metadata)
@ankitkala for changes in existing segment replication integration with remote store
@mch2 for overall segment replication workflow and unit test coverage post segregation

Related Issues
Resolves #7802 https://github.com/opensearch-project/OpenSearch/issues/8452
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Hit FileAlreadyExistsException error condition during round of segment replication in tests. The failure happens because of replica already containing segment files from remote store syncs during recovery but without corresponding segment_N file (incremental refreshes). Without commits on replica, these files remain on store without local segment_N file referencing these files and replica's latest segment infos does not include these. During next round of segment replication, while calculating files to catch from primary, replica shard uses it's latest segment infos vs whats on store. Thus, replica request these files again from remote store and during download hits this exception. There are couple of optoins to solve this:
1. During recovery
Skip download of incremental segment files (i.e. without corresponding segment_N file). This safe to do so as replica shard is not yet active to serve traffic.
2. During segment replication
Avoid requesting files which are already present on store. This needs to read local store files and needs special handling to identify missing files and is thus not clean.
Option 1 seems logically right as keeping the replica shard upto a commit point and doesn't have known issues.
Sample failure log
[2023-07-26T17:47:00,816][ERROR][o.o.i.r.SegmentReplicationTargetService] [node_t4] Exception replicating Id:[8] Shard:[[test-idx-1][0]] Source:[RemoteStoreReplicationSource] marking as failed.
org.opensearch.common.util.concurrent.UncategorizedExecutionException: Failed execution
	at org.opensearch.common.util.concurrent.FutureUtils.rethrowExecutionException(FutureUtils.java:109) ~[main/:?]
	at org.opensearch.common.util.concurrent.FutureUtils.get(FutureUtils.java:101) ~[main/:?]
	at org.opensearch.common.util.concurrent.ListenableFuture$1.doRun(ListenableFuture.java:125) ~[main/:?]
	at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) [main/:?]
	at org.opensearch.common.util.concurrent.OpenSearchExecutors$DirectExecutorService.execute(OpenSearchExecutors.java:341) [main/:?]
	at org.opensearch.common.util.concurrent.ListenableFuture.notifyListener(ListenableFuture.java:120) [main/:?]
	at org.opensearch.common.util.concurrent.ListenableFuture.addListener(ListenableFuture.java:82) [main/:?]
	at org.opensearch.action.StepListener.whenComplete(StepListener.java:93) [main/:?]
	at org.opensearch.indices.replication.SegmentReplicationTarget.startReplication(SegmentReplicationTarget.java:166) [main/:?]
	at org.opensearch.indices.replication.SegmentReplicationTargetService.start(SegmentReplicationTargetService.java:476) [main/:?]
	at org.opensearch.indices.replication.SegmentReplicationTargetService$ReplicationRunner.doRun(SegmentReplicationTargetService.java:462) [main/:?]
	at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:908) [main/:?]
	at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) [main/:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) [?:?]
	at java.lang.Thread.run(Thread.java:1623) [?:?]
Caused by: java.util.concurrent.ExecutionException: java.nio.file.FileAlreadyExistsException: /Users/singhnjb/OpenSearch/server/build/testrun/internalClusterTest/temp/org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT_65B27E9A73532C09-001/tempDir-003/node_t4/nodes/0/indices/Sg5-aL1WScqTXf7s4CXJEg/0/index/_2.si
	at org.opensearch.common.util.concurrent.BaseFuture$Sync.getValue(BaseFuture.java:286) ~[main/:?]
	at org.opensearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:260) ~[main/:?]
	at org.opensearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:82) ~[main/:?]
	at org.opensearch.common.util.concurrent.FutureUtils.get(FutureUtils.java:94) ~[main/:?]
	... 14 more

In order to unblock this PR due to issue above, followed option 2 for now. Created separate issue for further discussion and correct implementation https://github.com/opensearch-project/OpenSearch/issues/8905  CC @sachinpkale @mch2

I agree option 1 makes the most sense here for replicas. Initial recovery from remote store needs to fetch a commit because we have no way of loading the infos bytes directly on the engine that is not yet open. It also doesn't make sense to me to download files when we can't load them immediately. during recovery we can force sync using segrep to fetch the latest refresh point and load it directly.

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/21057/
CommitID: a3240c5
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?

I see main is already have 2.10.0 as bwc minor version defined correctly.
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':distribution:bwc:staged:buildBwcLinuxTar'.
> Building 2.9.0 didn't generate expected file /var/jenkins/workspace/gradle-check/search/distribution/bwc/staged/build/bwc/checkout-2.9/distribution/archives/linux-tar/build/distributions/opensearch-min-2.9.0-SNAPSHOT-linux-x64.tar.gz

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/21174/
CommitID: 9dc4379
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?

ResourceAwareTasksTests.testBasicTaskResourceTracking -> https://github.com/opensearch-project/OpenSearch/issues/8213
AzureBlobContainerRetriesTests.testWriteLargeBlob -> https://github.com/opensearch-project/OpenSearch/issues/6090
Retrying gradle check

Gradle Check (Jenkins) Run Completed with:

RESULT: UNSTABLE ❕
TEST FAILURES:

      1 org.opensearch.indices.replication.SegmentReplicationTargetServiceTests.testShardAlreadyReplicating

URL: https://build.ci.opensearch.org/job/gradle-check/21183/
CommitID: 9dc4379
Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

https://github.com/opensearch-project/OpenSearch/issues/8928

All recent gradle check failures are related to https://github.com/opensearch-project/OpenSearch/issues/9010 and fixed in https://github.com/opensearch-project/OpenSearch/pull/9011. Need to rebase again from main.

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/21659/
CommitID: 753729c
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?

org.mockito.exceptions.verification.TooManyActualInvocations:
perFieldCorrelationVectorsFormat.getKnnVectorsFormatForField(
    "test_vector_one"
);
Wanted 1 time:
-> at org.opensearch.plugin.correlation.core.index.codec.correlation950.CorrelationCodecTests.testCorrelationVectorIndex(CorrelationCodecTests.java:108)
But was 2 times:
-> at org.apache.lucene.codecs.perfield.PerFieldKnnVectorsFormat$FieldsWriter.getInstance(PerFieldKnnVectorsFormat.java:133)
-> at org.apache.lucene.codecs.perfield.PerFieldKnnVectorsFormat$FieldsWriter.getInstance(PerFieldKnnVectorsFormat.java:133)

checkCompatibility is failing, not sure why. Possibly downstream plugins not in sync with main
> Task :checkCompatibility
Checking compatibility for: https://github.com/opensearch-project/security.git with ref: main
Checking compatibility for: https://github.com/opensearch-project/index-management.git with ref: main
Checking compatibility for: https://github.com/opensearch-project/geospatial.git with ref: main

/tmp/groovy-generated-tmpdir-15525992211363152092/src/main/java/org/opensearch/geospatial/plugin/GeospatialPlugin.java:25: error: package org.opensearch.common.component does not exist
import org.opensearch.common.component.LifecycleComponent;
                                      ^
/tmp/groovy-generated-tmpdir-15525992211363152092/src/main/java/org/opensearch/geospatial/plugin/GeospatialPlugin.java:126: error: cannot find symbol
    public Collection<Class<? extends LifecycleComponent>> getGuiceServiceClasses() {
                                      ^
  symbol:   class LifecycleComponent
  location: class GeospatialPlugin
/tmp/groovy-generated-tmpdir-15525992211363152092/src/main/java/org/opensearch/geospatial/ip2geo/listener/Ip2GeoListener.java:26: error: package org.opensearch.common.component does not exist
import org.opensearch.common.component.AbstractLifecycleComponent;
                                      ^
/tmp/groovy-generated-tmpdir-15525992211363152092/src/main/java/org/opensearch/geospatial/ip2geo/listener/Ip2GeoListener.java:38: error: cannot find symbol
public class Ip2GeoListener extends AbstractLifecycleComponent implements ClusterStateListener {
                                    ^
  symbol: class AbstractLifecycleComponent
4 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> Compilation failed; see the compiler error output for details.


Reproducability when using Synchronous mode in Carla 0.9.4

I am running a python script using the Carla 0.9.4 client in synchronous mode simulating a single car with no pedestrians. I am getting * different*  results each run even though i set the VehicleRandomSeed  and this is because the traffic lights are *not * in the same state every run. Is there a way to change the state of all traffic lights so they are the same at the first world.tick() command every run? or are the traffic lights only running asynchronsouly ?

The random seeds are no longer used in newer versions. Your client would need to set the state of each traffic light at the beginning.

First, thank you for the prompted answer!!. Does that apply to vehicles and pedestrians as well? I was under the impression that the random seeds did work for my vehicle....

Since now you can control (almost) everything from the client-side, there is (almost) no need for random numbers. The last piece of code that still uses random numbers is the autopilot code at intersections, if a vehicle is in autopilot mode it turns at intersections at random, and unfortunately there is no way now to specify that random seed. This haven't been fixed because our idea is to move the autopilot to Python too.

That makes sense. Thanks !

I just read about the exciting new feature of the logging and playback system !! Will the playback system record the state of traffic lights ? Will do it for pedestrian actions?

and for vehicle controls /decisions made by the autopilot?

I haven't had the chance to play with the playback system yet :sweat_smile: but it should record everything in the scene so when you replay you get the same result.

So cool! I got to check it out,  Thanks!!

In case anyone finds it useful, I managed to record the simulation and reproduce it exactly using the playback system described here: . For replay, switching the server to synchronous mode and then using client.replay_file seems to do the work for me.

Hi @ykaganov ,
Thanks for your post! May I ask how you switch to synchronous mode to avoid frame drop?
I am using 0.9.5 and add
settings = self.world.get_settings()
settings.synchronous_mode = True

in manual_control.py class World, and also tried self.client.apply_batch_sync(batch). However, it seems that the control and measurement still differ by a few frames.

In case anyone finds it useful, I managed to record the simulation and reproduce it exactly using the playback system described here: http://carla.org/2019/03/01/release-0.9.4/. Just to make it clear, my goal was to rerun the exact same simulation but record data with a different Lidar camera. I wanted to use synchronous mode because otherwise I would have frame drops. Switching the server to synchronous mode and then using client.replay_file seems to do the work for me.

I am in a similar situation as well. I am trying to get lidar data with different lidar configurations(channels, number of lidars, position of lidar, etc) for the same scene. It would be helpful if you could post some example snippet on how to change sensor setting while replaying the simulation. Thanks in advance


Issue with threaded loading of TileMaps

Godot version
Latest master b40b35fb39f0d0768d7ec2976135adffdce1b96d, not in official release
System information
Ubuntu 20.04.6 LTS, Intel i7-8700K, NVIDIA GeForce GTX 1060 6GB
Issue description
When loading a scene with a TileMap using ResourceLoader the tile graphics don't show up (the physics shapes and such are, if there are any). Seems to have been introduced in 5a4613f5512b84a758d7cb4850f6e35db2bcceba
Steps to reproduce
Load and add a scene with a TileMap using ResourceLoader.
Minimal reproduction project
TileLoadTest.zip
The image is loaded to show that other stuff does load, the tiles have physics bodies to show that it's just the graphics that are missing.

cc @RandomShaper

I was expecting some bug in this area to arise. I'll look into it.


Improvements to "nft ethereum" crawlers

Changes
Migrated arguments from times to block numbers.
Flattened the summary schema even further. This is what it looks like now:
{
  "date_range": {
    "start_time": "2021-09-16T07:30:37+00:00",
    "include_start": true,
    "end_time": "2021-09-16T07:50:14+00:00",
    "include_end": true
  },
  "summary_id": "nft-ethereum-start-13235420-end-13235520",
  "args": { "start": 13235420, "end": 13235520 },
  "start_block": 13235420,
  "end_block": 13235520,
  "num_blocks": 101,
  "num_transactions": "25418",
  "total_value": "14338586641422304509748",
  "nft_transfers": "647",
  "nft_transfer_value": "212854000983544189560",
  "nft_mints": "514",
  "nft_owners": "486",
  "nft_minters": "233",
  "crawled_at": "2021-09-16T09:08:58.092250"
}

How to test these changes?
Sync up to the blockchain. Choose a range of blocks. Run "nft ethereum labels" for those blocks. Then run "nft ethereum summary" for those blocks.

Related issues
https://github.com/bugout-dev/moonstream/issues/252
Resolves https://github.com/bugout-dev/moonstream/issues/250

@bugout-dev/check:
[] Add MOONSTREAM_DATA_JOURNAL_ID
[] Add MOONSTREAM_ADMIN_ACCESS_TOKEN
[] Add MOONSTREAM_HUMBUG_TOKEN


Question About Register Image .tif on adata

I have adata with raw counts in .X, spatial coordinate in .obsm['spatial'].
I have also tissue image in .tif format
My question is

How can I add this image to adata.uns['spatial'] ?

I have loaded the image using
plt.imread("image.tif")
and it has dimensions of (26452 rows x 26458 columns)
I then attempted to add it to adata.uns['spatial'] using the following code:
adata.uns['spatial'] = {}
adata.uns['spatial']['Mouse'] = {}
adata.uns['spatial']['Mouse']['images'] = {}
adata.uns['spatial']['Mouse']['images']['hires'] = image.astype(np.float32)

However, when I use
sq.pl.spatial_scatter(adata, color="leiden")
the image only shows as a vertical line. Is there a correct way to attach the image to adata.uns['spatial']?

Should I crop the image?

The tissue is only located in the region of the image that spans from [5000:13000, 12000:20000], so the majority of the image is empty.
Would it be beneficial to crop the image?
If so, should the cropping be done before adding the image to adata.uns['spatial']?
Additionally, if the image is cropped, should the adata.obsm['spatial'] field also be adjusted accordingly?
...

hi @Wooseok1114 ,
can you share the shape of the image? It should be (H,W) or (H,W,C). What do you mean by straight line?

mmh interesting, this is really weird, what do you use to do the plotting that looks like a straight line?

image = plt.imread("image.tif")
adata = sc.read_h5ad("counts.h5ad") #h5ad file with x, y coordinate data on .obsm['spatial']
adata.uns['spatial'] = {}
adata.uns['spatial']['Mouse'] = {}
adata.uns['spatial']['Mouse']['images'] = {}
adata.uns['spatial']['Mouse']['images']['hires'] = image.astype(np.float32)
sq.pl.spatial_scatter(adata, color="leiden")

ok, try with shape=None and also can you please print the shape of adata.obsm["spatial"]

adata.obsm['spatial'] is this

adata.obs have also the x, y coordinate

shape = None brought this result

nice, so can you now try to add a dimension to the image before assigning it to adata.uns, e.g.
import numpy as np

image = ... # read image
image = image[..., np.newaxis]
...

it works!
So my last two questions are

I found the tissue image is grayscale (1 channel) image. However, in python, this image was shown in blue to yellow colorscale. How can I set this image in grayscale even after I load it on adata.uns?
The image is too big. Almost 70% of image is empty. The spatial_scatter also give very low resolution dots. Is there any way to load image

, which is matched to this shape = None plot?


Added NewStatsdSinkWithPrefix function

NewStatsdSinkWithPrefix allows each metric to be sent with a prefix.
Based on https://github.com/peterbourgon/g2s/pull/13
I have noticed that DogStatsdSink uses normal NewDogStatsdSink and then SetTags, so I have no problem with changing this sink to use SetPrefix if you think the current solution is not optimal.

Apologies. It turns out Consul was setting the prefix anyways in a weird way. Closing.


Feature: Kafka as input type

With Kafka as input type it would be possible to set up a snowplow stack on-premise for smaller setups.

You can show me how you do it. Thanks

Hi, you'd need to add kafka there.
But ideally this repo would need some refactoring to have several modules (e.g. like here) so that each app brings only the libraries of the message queue it is using, See how each techno gets its own app.

@benjben please, is there a chance the Kafka input will be implemented?
I have tried to deal with it, but im not skilled in scala.

Hi @lukas-pastva , this is not on our radar to implement this, sorry. As stated in the docs Postgres loader is not recommended for production use. Our development effort focuses on fully-fledged data warehouses (e.g. Databricks, Snowflake, BigQuery) and more recently on data lakes (e.g. Delta, Iceberg). /cc @stanch


⚠ ClamAV has degraded performance

In 4795657, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 474 ms

Resolved: ClamAV performance has improved in b29c006.


Remove the miq_workers table from the reindex list

This was causing nearly constant deadlocks in an environment with
lots of updates on the workers table. Based on
https://www.postgresql.org/docs/10/sql-reindex.html it sounds like
reindexes will definitely interfere with updates and that the situations
where we actually need a reindex are rather rare.
https://bugzilla.redhat.com/show_bug.cgi?id=1846281
Fixes #20281
I'm actually okay with leaving this without a migration. My thought was that
if a user has changed the tables for a reindex then they would probably be
aware of this deadlock issue if they were hitting it.

I'm actually okay with leaving this without a migration. My thought was that
if a user has changed the tables for a reindex then they would probably be
aware of this deadlock issue if they were hitting it.

I agree 👍

Jansa backport details:
$ git log -1
commit 8952c2b8f86dac785d2c4ab25f07d9b5885afe96
Author: Joe Rafaniello<EMAIL_ADDRESS>Date:   Wed Jun 24 13:02:56 2020 -0400

    Merge pull request #20305 from carbonin/remove_workers_from_reindex

    Remove the miq_workers table from the reindex list

    (cherry picked from commit 153932c931f11d110da88a57a13685d875bc1d83)

@carbonin I assume this can be ivanchuk/yes?

I don't see why not. Assuming this is in ivanchuk that is (I don't remember when we moved this into the app vs the console)

Ivanchuk backport details:
$ git log -1
commit 615a8a05e2e8d7744ff7eb0524087d7d58e626c4
Author: Joe Rafaniello<EMAIL_ADDRESS>Date:   Wed Jun 24 13:02:56 2020 -0400

    Merge pull request #20305 from carbonin/remove_workers_from_reindex

    Remove the miq_workers table from the reindex list

    (cherry picked from commit 153932c931f11d110da88a57a13685d875bc1d83)

    https://bugzilla.redhat.com/show_bug.cgi?id=1846281