Temporarily disable historical cache job

See issue #4064 . This way it'll only run if the env variable is set.

It's OK to leave the env variable off for now on staging - we really only need to turn it on while doing testing.

Should we go ahead with an off-schedule production deploy?

@awwaiid Ehn.  Not during business hours, certainly.  I would consider it for tonight --  Do we have a sense of how long it will take to clear out the backlog of jobs?

We should clear them out manually. I can put in a PR for this too.

We'd just be clearing out the historicals, right?  Leaving the email jobs?   I think we are going to have some noise from the banks whichever way we go on that.

Yep.


Can't seem to code against ngx-device-detector in development

Angular Version: 8.2.x
This is an awesome tool that seems to be very accurate -- but maybe too accurate :)
The problem I'm having is, I need to be able to code against the deviceService flags (isMobile, isTablet, isDesktop) when using the Chrome devtools viewpoint emulations via desktop.  When I'm devtools to simulate a mobile or tablet viewport, the deviceService.isMobile is false and the deviceService.isDesktop flag is true.  Now, of course this is technically correct but is there a workaround to this?  Great library!  Please advise.

Not exactly, around simulation, it acts according to the user agent provided by the browser 🙂 . Not much we can do.


Doesn't work with Next.js

Hi sorry this is more of a question than a discrete issue - do you have any knowledge of whether this should work with Next.js? I've got it to a state where it is replacing the route in the URL (flashes by quickly) however the app itself just loads the index. I know Next handles routing a little differently to React, wondering if it's a lost cause. Can provide more info if you're interested in helping, otherwise feel free to delete this :-)

You should be able to use next export, which generates static html, with GitHub Pages without the need for spa-github-pages.

The issue I'm having is that the route is dynamic - i.e. it goes and gets an arbitrary resource from an external API that I can't predict the ID of and ergo can't provide Next with a full list of. I'm going to try moving the route replacement script you added in this repo to the Index.html to the inside of the App itself and see if that works

Update: this works
`export default function MyApp({ Component, pageProps }) {
const router = useRouter()
if (Object.keys(router.query).length >= 1) {
const firstQuery = Object.keys(router.query)[0]
if (firstQuery[0] === '/') {
const decoded = firstQuery.slice(1).split('&').map((s) => s.replace(/~and~/g,'&')).join('?')
  router.push(router.pathname + decoded)
}

}
return (
// APP CODE
)
}`

I've got it working somewhat with next.js but the problem is I'm getting a redirect loop for pages that really don't exist. Frankly, I don't understand how this is not a problem for vanilla react apps...


[py2py3] Apply changes from pylint --py3k to files involved in #10012

Fixes #10169
Status
In development
Description
We need to modernize how we do comparisons and ordering in DataStructs/Run.py and DataStructs/File.py because python3 does not honor anymore the dunder method __cmp__.
(details will be updated)

src/python/WMCore/DataStructs/Run.py
src/python/WMCore/DataStructs/File.py

Reference: https://portingguide.readthedocs.io/en/latest/comparisons.html
Examples and some testing

https://cms-dmwm-test.docs.cern.ch/py2py3/porting/comparisons_py2/
https://cms-dmwm-test.docs.cern.ch/py2py3/porting/comparisons_py3/

Is it backward compatible (if not, which system it affects?)
yes
Related PRs
This is a follow-up to #10441
External dependencies / deployment changes
nope

Test this, please

Test this, please

@amaltaro I have a question for you. It is about this function
https://github.com/dmwm/WMCore/blob/5da7f3c898bb39cdb7efb64070af182419501602/src/python/WMCore/DataStructs/File.py#L90
From this guide I get that it should return an integer: < 0 is lhs is les than rhs, 0 is lhs is equal to rhs, >0 if lhs is greater than rhs. However, it's years that __cmp__ is set to be the same as __eq__, which should not be the case. __cmp__ in python2 is used when you call <, <=, >, >= on two objects of a class and since the implementation puzzles me I wonder if we ever compare two Files in dmwm/WMCore code.
I tried commenting __cmp__ out of DataStructs/File.py and no unit test failed.
We have a couple of options

reimplement a meaningful comparison operator in py2 and py3 compatible fashion. I do not know if we need this though, because the more reasonable implementation of this cmp (comparing run number and lumi sections) method has been commented out 11y ago, so I assume we do not really need such a functionality
remove this and hope nothing beraks in testbed - production.

What do you think? Do you want me to better dive into our code looking for potential rich comparisons between files? == and != are correctly covered by __eq__, what seems that we do not need but I have not looked for yet are <, <=, >, >=.
What's your take on this?

@mapellidario sorry for the belated reply.
I believe we only compare if file objects are equal or not, so I'd say it's safe enough to remove __cmp__ and leave only the equality methods. However, I do not see a good coverage with the current unit tests, so can I ask you to create some basic equality comparison tests to verify these changes as well (might add a check for identity as well, even though it's unrelated AFAIU)?


Add Content to Index.html

TODO

Add a hero section to test out variables on background-images
Add a typography section to test out variables on copy
Add a Background section to test out variables on background Colors. Also Test our Variables on borders here, sizes and colors
Add a CTA section to test out variables on button colors for theming

Finished this


Optimize ((a mod modulus) + modulus) mod modulo

Avoids doing mod twice.
I also swapped a.modulo(modulus) and modulus in invmod, to skip the first iteration (otherwise q would always be zero in the first iteration, since a.modulo(modulus) < modulus).

Hmm, looks like there's a Nim 1.4 bug...

I managed to work around the bug, but I have no idea what caused it.


Allow site to be built on debian/ubuntu

The current scripts need root and a version of ruby newer than what
Debian and Ubuntu ship.
This patch removes the need for root and makes any ruby newer than
or equal to 2.3.1 acceptable.

@lucperkins


Update docker-compose.yml

Wait for spdk container to be ready.

@llabordehpe thanks for the fix, please add signoff per our DCO requirement, see the checker failure above
https://github.com/opiproject/opi-poc/pull/373/checks?check_run_id=8484119210

The fix looks good.  As Boris mentioned, please amend and force push with the signoff (commit -s --amend).  Thanks!


U-Tec UBolt Pro ZWave Locks not updating their status correctly

Problem/Motivation

Locks showing unlocked / locked status after locking / unlocking from dashboard and vice versa

Expected behavior

Lock should unlock or lock when dashboard button pressed or triggered from automation

Actual behavior

Intermittently the locks will change status but the actual lock will not change state

Steps to reproduce

it’s intermittent but only started after upgrading the ZWave FW to 1.53 and won’t let me downgrade

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

I have a similar issue in SmartThings. Yale YRD110-ZW-US. The hub will report (and continue reporting) an "unlocked" condition exactly 1 hour after auto-lock or a manual locking.  I'm curious if your "intermittent" issue is actually 1 hour after any changes at the device. Two different manufacturers running on two different hubs having a similar issue (1 hour delay) could point to a Z-Wave issue.


Adding authentication

It would be great if there were an option to enable authentication before the gallery opens up. And to add the description for it in readme or somewhere else.
Many thanks

It looks like the plugin would need some refactoring to make adding authentication easier.
Following up on the conversations on gitter, it should be possible to start from a fork and tweak some of the components.
Maybe these changes could be posted here in this issue for visibility?
Thanks!


New Build Pipeline: Use Zig as compiler

This PR compiles dependencies, using Zig Build System.

[!NOTE]
This targets https://github.com/parca-dev/parca-agent/tree/nbp_devbox

As of now, it doesn't address cross-compilation concerns.

It uses musl and statically links everything.
It reduces build time dependecies.

devbox + direnv is a pretty neat combo! The overall strategy of this change makes a ton of sense to me.

For what I see in the PR, it seems like we are using musl for the native C dependencies as our libc, not GNUs, is that correct?


docs: Better document backup/export tool tradeoffs.

More consistent export/import vs backup bullets at the top.

Remove misleading documentation regarding the zulip_org_id reuse problems. This documentation was written for Zulip 2.1.0 in c6fe6cf0a47cd61c0005aa099b9f7fa16d96f603 and largely made obsolete in d800ac33a0322b0d3ef327bcebf318a27448bbee (Zulip 5.0).

Light editing for readability/crispness.

Fixes #28925.

Applied all the suggestions, thanks @alexmv! Marked to merge once CI passes again, and then we should backport this to 8.3.

Backported in https://github.com/zulip/zulip/pull/29232.


chore: specify eol config in .prettierrc as lf

Summary:

Although we have .editorconfig, on Windows machines most of the times the IDEs default to CRLF as default EOL config
we've already specified the eol config as lf in .editorconfig at root level
this diff syncs same config for prettier as well

NOTE: Using [skip ci] as it's non code change and is tested for formatting.

Changelog:
[GENERAL] [CHANGED] - Specify eol config in .prettierrc as lf at the root level
Test Plan:

yarn run format  --> nothing should change

NOTE: Using [skip ci] as it's non code change and is tested for formatting.

Feel free to manually trigger the tests if necessary.
P.S. Save Energy! 🌏🤗

ping @cortinico :)

/rebase

Of course it has some major security aspects related to the use of labels, but I think we can setup something that would skip CI for PRs with only *.md changes. E.g. using label (like skip-ci) or something else.
Also, for directly pushed commits the [skip ci] tag in commit msg should skip CI. Don't know it works in that case...

We generally don't want to skip CI as we don't have much docs or other non code content in this repo. Your change also needs to run on CI as, albeit minimal, it could break internal Meta setup so we need to run CI regardless.

Sure.

Lmk if I should rm [skip ci] from commit msg.

Yes please remove it (I'm surprised it worked actually)

Checking at documentation, seems like this is not needed as the default value for endOfLine is lf since 2.0.0: https://prettier.io/docs/en/options.html

Checking at documentation, seems like this is not needed as the default value for endOfLine is lf since 2.0.0: https://prettier.io/docs/en/options.html

Yeah I had checked that earlier, but, vscode on Windows 11 still defaults to crlf for RN codebase, for other repos it works fine. How to fix that?


Fix bad mkdirp

This fixes an issue in which an empty folder structure gets created in your cwd.
Related to Microsoft/vso-extension-tools#2.

Thanks João!


Discussion: Run Docker on MacOS

This issue is to attract comments on what to do with https://github.com/GaloyMoney/galoy-mobile/pull/2971
With this PR, we could do very deterministic e2e testing because we will be able to run Local Backend in CI along with Mac Builds + Detox is more native than Appium.

Running Docker on MacOS in any CI Containers is quite challenging. There are some workarounds available in some random GitHub comments that seem to work with specific versions of Docker and Mac. Here is a list of the ones I could find and my testing result.

Script ran inside CircleCI container, didn't work. https://github.com/docker/for-mac/issues/2359#issuecomment-853420567
Tried running this both on CircleCI and GitHub Actions, didn't work. https://github.com/docker/for-mac/issues/2359#issuecomment-943131345
Docker OSX - It's OSX on docker unfortunately, not the other way round. https://github.com/sickcodes/Docker-OSX

Related Issues:

https://github.com/docker/roadmap/issues/419
https://github.com/docker/roadmap/issues/172

People have moved to Self Hosted apparently:

https://github.com/tarantool/tt/issues/517

cc @bodymindarts @openoms

From discussing after ACE,

Going forward with Scaleway is Option no 1
If nothing works, SSH tunnel is last resort


[IOTDB-2762][metrics] Fix inconsistent name between dropwizard implementation and micrometer implementation

See more details: https://issues.apache.org/jira/browse/IOTDB-2762

@SteveYurongSu PTAL!


Mark as played (feature request)

After I play a song would be cool if the text was grey in the display

Doesn't look like the Hype Machine API includes the play count. We could potentially save the IDs of played tracks locally, but then someone will complain that it's not synced.

API track payload:
[
	"posturl": https://wyved.com/2021/02/19/puma-blue-in-praise-of-shadows/,
	"spotify_uri": spotify:track:1SXvJZQu60PSonJscOqV4l,
	"itemid": 303qp,
	"loved_count": 4,
	"itunes_link": https://hypem.com/go/itunes_search/Puma%20Blue,
	"siteid": 17529,
	"stream_pub": https://hypem.com/serve/public/303qp,
	"thumb_url": https://static.hypem.com/items_images/f6/303qp_120.jpg,
	"title": Bath House,
	"dateposted":<PHONE_NUMBER>,
	"postid": 3900268,
	"media_type": bandcamp,
	"rank": 50,
	"posted_count": 1,
	"description": British singer and producer Puma Blue recently released a new 14-track album entitled In Praise Of Shadows. We have featured our favorites below and we invite you to surf over to bandcamp to listen to the rest of her work. <a href="https://pumabluemusic.bandcamp.com/album/in-prai,
	"artist": Puma Blue,
	"time": 250,
	"sitename": wyved,
	"thumb_url_medium": https://static.hypem.com/items_images/f6/303qp_120.jpg,
	"thumb_url_large": https://static.hypem.com/items_images/f6/303qp_640.jpg
]

Ah i won't tell you how to write your software but personally I just use the app and wouldn't mind it being desynced and you could turn it off in settings. Thanks for this great app.

Yeah, I guess we can just save it locally and warn the user somehow that it's not synced.


fix: Datasource preview not taking full height

Description
This PR fixes the release blocker issue caused by datasource schema page not taking 100% height.
Fixes #36388
Automation
/ok-to-test<EMAIL_ADDRESS>:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

/build-deploy-preview skip-test=true


vimc-4136 Add get run status for polling running reports

Also added unit tests for the api class (only had integration tests before), and a custom error class for response errors from OrderlyWeb.

I've updated the error class to extract error message from the orderly web response, and I changed the scripts to use orderyweb deploy while I was in there.


[WebGPU article] Check adapter before using it

This PR makes sure adapter is valid before using. I've also updated all Glitch samples.
Context: https://chromium-review.googlesource.com/c/chromium/src/+/2617499
@Kangz for review
Live preview: https://pr-9198-dot-web-central.appspot.com/web/updates/2019/08/get-started-with-gpu-compute-on-the-web

Whoops!
There were 3 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L74 - Common typo found: 'implicity' Should it be 'implicitly'?
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L232 - Common typo found: 'implicity' Should it be 'implicitly'?
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L239 - Line must be at most 100 characters

Whoops!
There were 3 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L74 - Common typo found: 'implicity' Should it be 'implicitly'?
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L232 - Common typo found: 'implicity' Should it be 'implicitly'?
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L239 - Line must be at most 100 characters

Whoops!
There were 3 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L73 - Common typo found: 'implicity' Should it be 'implicitly'?
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L231 - Common typo found: 'implicity' Should it be 'implicitly'?
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L238 - Line must be at most 100 characters

Whoops!
There were 3 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L73 - Common typo found: 'implicity' Should it be 'implicitly'?
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L231 - Common typo found: 'implicity' Should it be 'implicitly'?
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L238 - Line must be at most 100 characters

@petele Please merge and push live.

@petele Please merge and push live.


Scrollable dialog content not loading

Bug type
Docs (mudblazor.com)
Component name
MudDialog
What happened?
The example in scrollable dialog is unable to retrieve content from mudblazor github repo, due to some violation of content security policy of github. Not sure what exactly is the violation, but the point is, scrollable dialog got struck at loading progress spinner after throwing some exceptions. Manual retrieval of the content from github works fine anyways.
Expected behavior
The scrollable dialog should be able to load the LICENSE file from mudblazor github repo and also be able to scroll!
Reproduction link
https://mudblazor.com/components/dialog#scrollable-dialog
Reproduction steps

Just go to the above link
Click the scrollable dialog button

Relevant log output
Refused to connect to 'https://raw.githubusercontent.com/MudBlazor/MudBlazor/master/LICENSE' because it violates the following Content Security Policy directive: "connect-src 'self'
                               https://api.github.com
                               https://www.google-analytics.com".

Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: TypeError: Failed to fetch
System.Net.Http.HttpRequestException: TypeError: Failed to fetch
 ---> System.Runtime.InteropServices.JavaScript.JSException: TypeError: Failed to fetch
   at System.Net.Http.BrowserHttpHandler.SendAsync(HttpRequestMessage , CancellationToken )
   Exception_EndOfInnerExceptionStack
   at System.Net.Http.BrowserHttpHandler.SendAsync(HttpRequestMessage , CancellationToken )
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage , HttpCompletionOption , CancellationTokenSource , Boolean , CancellationTokenSource , CancellationToken )
   at MudBlazor.Docs.Examples.DialogScrollableExample_Dialog.OnInitializedAsync()
   at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task , ComponentState )

Version (bug)
6.0.4
Version (working)
5.X.X
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Already fixed on dev: https://dev.mudblazor.com/components/dialog#scrollable-dialog


chore: Remove unused endpoint from auth list

Description
Remove unused endpoint from auth list
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed

CI

/retest