2024-11-12_01-34-54_master-next_aws-c-io

Automatically created.

Backport failed for kirkstone-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin kirkstone-next
git worktree add -d .worktree/backport-10308-to-kirkstone-next origin/kirkstone-next
cd .worktree/backport-10308-to-kirkstone-next
git switch --create backport-10308-to-kirkstone-next
git cherry-pick -x 119c5ef706e75b86a47088ae5c0c08bf5784bed5

Backport failed for scarthgap-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin scarthgap-next
git worktree add -d .worktree/backport-10308-to-scarthgap-next origin/scarthgap-next
cd .worktree/backport-10308-to-scarthgap-next
git switch --create backport-10308-to-scarthgap-next
git cherry-pick -x 119c5ef706e75b86a47088ae5c0c08bf5784bed5

Backport failed for styhead-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin styhead-next
git worktree add -d .worktree/backport-10308-to-styhead-next origin/styhead-next
cd .worktree/backport-10308-to-styhead-next
git switch --create backport-10308-to-styhead-next
git cherry-pick -x 119c5ef706e75b86a47088ae5c0c08bf5784bed5


Infludb2 cloud - can add data to bucket but cannot see it or  query it

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

Log into infludb2 cloud
Select bucket
Select "+Add data"
Select line protocol
Select enter manually
Enter row
mem,host=host1 used_percent=24.43234543<PHONE_NUMBER>' // Line protocol string
Click "write data"
Query bucket but data is not there

Expected behavior:
Should be able to see data
Actual behavior:
Cannot see  any data.
Environment info:
Cloud

System info: Run uname -srm and copy the output here
InfluxDB version: Run influxd version and copy the output here
Other relevant environment details: Container runtime, disk info, etc

Config:
Copy any non-default config values here or attach the full config as a gist or file.

Logs:
Include snippet of errors in log.
Performance:
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.
# Commands should be run when the bug is actively happening.
# Note: This command will run for at least 30 seconds.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=true"
curl -o vars.txt "http://localhost:8086/debug/vars"
iostat -xd 1 30 > iostat.txt
# Attach the `profiles.tar.gz`, `vars.txt`, and `iostat.txt` output files.

Good morning. That's a great question. Just so I can get a better idea of where the issue might be, when you were adding data via the line protocol, what did you have the precision set to in the dropdown? I've attached an image for context:

Yes, that is the default.
I specifically tried with that again but still no joy
On Wed, Mar 18, 2020 at 9:35 AM Ariel Salem<EMAIL_ADDRESS>wrote:

Good morning. That's a great question. Just so I can get a better idea of
where the issue might be, when you were adding data via the line protocol,
what did you have the precision set to in the dropdown? I've attached an
image for context:
[image: Screen Shot 2020-03-18 at 06 34 04]
https://user-images.githubusercontent.com/19984220/76966065-9df1f980-68e2-11ea-94ec-17911b485f37.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb/issues/17322#issuecomment-600625856,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAREB4VNMK4NIVYZFG4MFT3RIDE2FANCNFSM4LOEACPQ
.

@cshashank can you try changing the precision to seconds to see if that changes the way the data is stored? Since the default is based on nanosecond precision,  the timestamp you provided<PHONE_NUMBER> would default to the earliest year possible (1970)

This feature would solve this: https://github.com/influxdata/influxdb/issues/15370

Hello
Thanks for your help,
With this data
mem,host=host1 used_percent=23.43234543<PHONE_NUMBER>
and precision set to 'seconds'
I can see the data.
On Wed, Mar 18, 2020 at 12:28 PM Russ Savage<EMAIL_ADDRESS>wrote:

This feature would solve this: #15370
https://github.com/influxdata/influxdb/issues/15370
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb/issues/17322#issuecomment-600731216,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAREB4WSOME3OUFJC2PE4WTRIDZA7ANCNFSM4LOEACPQ
.

@cshashank if you have any more questions regarding InfluxDB feel free to join our community slack here:
https://influxcommunity.slack.com/


Initial WMArchive REST service

Please take initial implementation of WMArchive REST service (proxy server). Here is its configuration file:
import socket
from WMCore.Configuration import Configuration
from os import path

HOST = socket.gethostname().lower()
ROOTDIR = __file__.rsplit('/', 3)[0]
config = Configuration()

main = config.section_("main")
srv = main.section_("server")
srv.thread_pool = 30
main.application = "wmarchive"
main.port = 8246 # main application port it listens on
#main.index = "ui"
main.index = "data"
# Defaults to allow any CMS authenticated user. Write APIs should require
# additional roles in SiteDB (i.e. "Admin" role for the "ReqMgr" group)
#main.authz_defaults = {"role": None, "group": None, "site": None}

#sec = main.section_("tools").section_("cms_auth")
#sec.key_file = "%s/auth/wmcore-auth/header-auth-key" % ROOTDIR
#sec.key_file = "/Users/vk/CMS/DMWM/GIT/WMCore/auth-key"

# this is where the application will be mounted, where the REST API
# is reachable and this features in CMS web frontend rewrite rules
app = config.section_(main.application) # string containing "reqmgr2"
app.admin =<EMAIL_ADDRESS>app.description = "CMS data operations WMArchive."
app.title = "CMS Request Manager (WMArchive)"

views = config.section_("views")

# practical to have this kind of configuration values not in
# service related RPM (difficult/impossible to change in CMS web
# deployment) but in the deployment configuration for the service

# redirector for the REST API implemented handlers
data = views.section_("data")
data.object = "WMCore.WMArchive.Service.RestApiHub.RestApiHub"

and (assuming all environment is set) it can be run as following:
wmc-httpd -r -d /tmp -l wma.log ./wmarch_config.py

Hi Valentin, as Yuyi mentioned I think it might be better the code is hosted in different repository.
https://github.com/dmwm/WMArchive
Since this project will contain different set of dependencies than other REST applications (ReqMgr2, WMStats) and I expect this will be much bigger and complicated application than those.
In terms of the code, in general,
RESTEntity is designed to operates over specific data. It will be implemented one or more verbs on that that. (i.e. POST, PUT, GET, DELETE)
I think in some cases it doesn't really fits the use case. (I had some problems applying that concept on reqmgr2).
Anyway, this is Lassi's design concept, so sitedb will be the good example how he initially envision this.
https://github.com/dmwm/sitedb/blob/master/src/python/DataPeople.py
I added some in line comment

I migrated code (and fixed it with respect of provided comments) to WMArchive repository. The new PR is https://github.com/dmwm/WMArchive/pull/1 I'll keep this open until we merge new PR. So far I only modified data classes, but didn't yet change service wrt sitedb layout. I need to think about it if it is appropriate here. This can be done later. Please review new PR.

This is moved to WMArchive repository, closing it


Choose a license for the project

Without a license, no one may use this awesome package. Two most commonly used OSS licenses are MIT License and Apache License 2.0. http://choosealicense.com/ site can help you with the topic.

Yeah, thanks for reminder. Was going to, but eventually forgot :)


Bumps base image versions

What this PR does / why we need it:
Bumps base images.
I wonder if we should have some automation for this.
Release note:

NONE

/kind cleanup
Signed-off-by: irbekrm<EMAIL_ADDRESS>

/retest

/lgtm


[Merge] Merges changes from epek/structs.

Merges changes from epek/structs with newest master per https://github.com/fatih/structs/pull/35.
Functionality Addition: Adds MapPtr which creates a map with pointers to structs.
This makes handling large structs easiest and more portable.

Coverage decreased (-7.0%) to 92.084% when pulling a76abb885b638c5602cdab39fecfe28328ff6695 on kamronbatman:merge/epek into 73c4e3dc02a78deaba8640d5f3a8c236ec1352bf on fatih:master.

@kamronbatman can you check why the coverage decreased ? It's a huge percentage. Maybe it's due something that is not testable. If you're using vim-go just run :GoCoverage on structs.go to see why it decreased.

@fatih Coveralls isn't showing the file coverage.  I rebased the latest master, so maybe coveralls will show it this time.

Coverage decreased (-7.0%) to 92.084% when pulling ae73fb2d968a6dc25cac1f9e3db18b897054d52a on kamronbatman:merge/epek into 73c4e3dc02a78deaba8640d5f3a8c236ec1352bf on fatih:master.

@fatih In building the tests out for the merge from https://github.com/fatih/structs/pull/35 I realized that this merge will actually not help as much as I thought.
I was looking for something where pointers to structs would result in a copy of the pointer to the same struct, which is already the expected behavior.
If a struct has embedded a struct in its field instead of a pointer, I don't see the purpose of creating a pointer to it when the original field was not a pointer.
I am going to abandon this pull request. I also move to have https://github.com/fatih/structs/pull/35 closed because it doesn't actually help and will cause confusion as it did in my case.


Create a Getting Started guide

Is your feature request related to a problem? Please describe.
There is no getting-started guide for this library.
Describe the solution you'd like
Need a good getting started guide

See https://github.com/atsign-foundation/atsign.dev-3.0/pull/89
atsign.dev-3.0 is getting Java documentation.


github actions detalied tutorial [ Feature request ]

Is your feature request related to a problem? Please describe.
many of us need a tutorial to deploy it on github actions
pls help

I don't think it possible to deploy python telegram bot in github action. But you can try js library for telegram,

deploying it on GitHub actions seems like an abuse of it
may result in banning of both account and repo

if you use GitHub actions to deploy on other sites it's not abuse
but if you choose to deploy on GitHub actions it is considered as abuse


gets Sheet name for multi cell named range, fixes #680

Please have a look, this seems to resolve the issue for us.
Do you want us to add a test case or do you prefer to do that yourself?

This doesn't seem to work on all of the files from the test corpus.
After the line in question, add a line that throws an error if the field is missing:
				sname = (supbooks && supbooks[1] ? supbooks[1][ixti+1] : supbooks.SheetNames[ixti]);
				if(!sname) throw new Error("missing name"); // <-- add this line
				stack.push(sname + "!" + encode_range((r/*:any*/)));

To check against the test corpus, you can run the following command:
$ env WTF=1 FMTS=xlsb make test

(The WTF=1 part throws errors that would otherwise be caught and FMTS=xlsb restricts to reading only XLSB files.)
The first fail case is test_files/2013/apachepoi_50939.xls.xlsb, tripping on the newly-added error.

Hi, sorry for the late reply. I've fixed the commit to fall back again to **MISSING**.
It still fails somewhere with the if(!sname) throw new Error("missing name"); line, but that is the same behaviour as on master, so I don't think that's being caused by my changes.
Let me know know what you think. Thanks!

@SheetJSDev have you been able to look at my fixed commit? see previous comment. thanks for your feedback!

I wasn't saying your commit wasn't useful for your case, but if we're going to change the function processing it's better to fixit in one fell swoop  :)
Looked into this a little bit, https://github.com/SheetJS/js-xlsx/issues/680#issuecomment-307869085 was my initial brain dump on the matter.
The XLSB workbook processor is missing a few records like:
0x0165: /* 'BrtSupSelf' */
0x0166: /* 'BrtSupSame' */
0x0163: /* 'BrtSupBookSrc' */
0x029B: /* 'BrtSupAddin' */
0x016A: /* 'BrtExternSheet' */
0x0169: /* 'BrtPlaceholderName' */

After adding some initial implementation, we ran into a few more random cases like https://github.com/SheetJS/test_files/blob/master/2013/apachepoi_ex45978-extraLinkTableSheets.xls.xlsb?raw=true .  I suspect the external links files need to be processed.

OK thanks for the feedback!

The particular part was reworked, but you've been credited on a related commit involving incorrect quoting of #REF in an unknown 3d reference.


Fix mr test prepare

This was noticed while implementing the --source option in 'mr create'.

The prepare function in the merge request test code has an error that is
commented out.  This is because the code no longer works correctly and
always throws an error.  The prepare function attempts to clean up any
existing test merge requests prior to creating new ones.

Fix and generalize the prepare test function.

Signed-off-by: Prarit Bhargava<EMAIL_ADDRESS>

@bmeneguele , OOC when you tested your 'mr delete' modification did you do it against lab-testing !4676?
I am getting an error on !4676, but when I list the MRs there is no 4676.

!4678 mr title
!4677 mr title
!4675 Draft: mr by branch
!4674 Test draft merge request
!4673 mr title

This could be a GitLab bug.

@prarit, I deleted this 4676 after I saw it failing for both your PR and mine (the one enabling lab mr delete), but it was after your build failed. It's now failing due to 4702. I think the cleanup code is handling something not in the right way. Let me check your changes again.

cmd/mr_test.go:52:9: cannot use openMR (type int) as type string in argument to closeMR
:)))

cmd/mr_test.go:52:9: cannot use openMR (type int) as type string in argument to closeMR
:)))

Heh, yeah, just caught that.  I was distracted.  I'll reach out to you on IRC to show you why.
P.

Yay! And it finally builds :D.
HOWEVER.. lol... don't hate me, please... could you just add a few more words to the "Fix" patch? :sweat_smile:

Yay! And it finally builds :D.
HOWEVER.. lol... don't hate me, please... could you just add a few more words to the "Fix" patch? sweat_smile

Yup, I was going to squash that in next.

Actually, no.  There's still something wrong with the source test.


Consider avoiding stream_socket_shutdown

When file descriptors are shared between processes or threads, stream_socket_shutdown will close the file descriptor for ALL threads/processes (took me forever to figure out what was going on) and cause broken pipes.

Unfortunately, this is exactly what it's designed to do. The issue is that PHP doesn't open FDs with the close on exec option, so any child process will inherit the file descriptors. We shutdown the sockets so they don't stay open in case any child process is started while the socket was open.

The issue is that PHP doesn't open FDs with the close on exec option, so any child process will inherit the file descriptors

This is pretty much how things are done in Linux. In fact, after a fork() in C, you usually do something like this and manually close them all yourself; but generally, you don't want to break them in the parent.
Alternatively, call pcntl_unshare(1024) in the child to disassociate the FD table with the parent. Granted, it's PHP so a lot happens between fork and your call to unshare... so YMMV.
This should work IMHO, fwiw:
$pid = pcntl_fork();
if($pid === 0) {
  foreach (EventLoop::getIdentifiers() as $identifier) {
    EventLoop::cancel($identifier);
  }
  // clean process?
}

But now if any destructors get called in a child, for any reason, the entire program crashes and/or corrupts things in databases (depending on what gets destructed and in what order).

For the record, this was simply resolved by using the ZTS version of PHP.


TypeError: Cannot read property 'name' of undefined. Restarting Server...

When typing the word export twice on separate lines like so:
export
export

atom-ternjs produces the following error: TypeError: Cannot read property 'name' of undefined. Restarting Server...
While this is obviously not something that someone would do normally, I came across it from the following code snippet:
|

export function authError(error){
  return {
    type: AUTH_ERROR,
    payload: error
  };
}

Where my cursor is denoted by |. The error pops up as soon as you start trying to export a new function, and type the keyword export.

Atom Version 1.12.7
atom-ternjs Version 0.16.1
.tern-project:
{
  "ecmaVersion": 6,
  "libs": [
    "browser"
  ],
  "plugins": {
    "doc_comment": {
      "fullDocs": true,
      "strong": false
    },
    "es_modules": {}
  }
}

This is most likely an issue with tern itself. Feel free to create an issue there.


Fix hotspots issues in Android by using e.preventDefault() only for iPhone

Hotspots work perfectly fine on Desktop & iPhone (Safari / Chrome). However, hotspots won't be responsive in Android at all.
Fixes issue #62.

I signed it!

Sorry - it looks like your commits aren't associated with the email address on your Github profile (the author shows up as "dummyuser" in the Commit tab). Our CLA policy requires that they match.
Can you please amend the author of your commits, make sure you've signed the CLA with the same email, and reopen the pull request? Thanks.

Hey tjgq, thank you a lot. Of course I will.


Broken key in the docker image

Hi @tarasborov,
I tried to follow README and faced the following issue while building a docker image:

Just Googled a fix for that here: https://answers.ros.org/question/325039/apt-update-fails-cannot-install-pkgs-key-not-working/
I added the following lines before doing update:
RUN sudo apt-key del 421C365BD9FF1F717815A3895523BAEEB01FA116
RUN sudo -E apt-key adv --keyserver 'hkp://keyserver.ubuntu.com:80' --recv-key C1CF6E31E6BADE8868B172B4F42ED6FBAB17C654

Plus cleanup:
RUN sudo apt clean && apt-get update && apt-get install -y \

And it has been correctly built. So you may want to update your Dockerfile as well.

Thanks. The docker file was updated.


Add feature to start new session from code

Is your feature request related to a problem? Please describe.
According to GA documentation it starts new session if referrer isn't equal URL domain or URL has UTM-params. It would be helpful to have the same logic inside Snowplow.
Describe the solution you'd like

Add function to start new session from code to have full control on it
Or / and add tracker parameter to force new session start if TLD(url) != TLD(referer) or URL has UTM-params

Thanks!

I don't think it's particularly well documented but the first bullet point already exists, you can call the newSession method to start a new session.
https://github.com/snowplow/snowplow-javascript-tracker/blob/master/trackers/browser-tracker/docs/markdown/browser-tracker.browsertracker.newsession.md
Or window.snowplow('newSession') if using the JavaScript Tracker rather than Browser Tracker.
I'll leave this issue open for the option to reset on UTM param change and/or new referer. That would perhaps be a breaking change though, or need to be disabled by default.

@paulboocock Thanks! That's exactly what I need.
But there is one issue with newSession usage from code when session timeout happens:

Visit page (vid = 24)
Wait for session timeout
Call newSession before trackPageView (vid = 26)

If you wait for the session to timeout and then visit the page, that's going to generate vid 25 immediately because that's a new session. Track Page View isn't when the session begins, when you arrive on the page and initialise the tracker is when the session starts.
In reality there are usually lots of edge cases when vid doesn't increase by only 1, it should be used to sort sessions in order, not to get a count of them (you should count by distinct domain_sessionid for that).


Change default space config direction

Description
This changes the default space config direction to horizontal.
Action Items

[x] I have read the CONTRIBUTING doc
[x] This PR is as small as it can be, and only implements on thing (not many)
[x] I have manually tested my feature
I have written a "good" amount of tests (including visual and unit tests) (not necessary)

Great stuff @joshuanianji!
I haven't taken a look at the code yet, but I noticed that the Button examples are all wonky now!

Please update the direction on these examples to prevent this breaking change.
Also, run ./scripts/format-elm-files.sh to format your files.

Oh I didn't think about changing the other examples! My new commits should all work now.

I just noticed that the docs are incorrect now.
Do a grep for Note that by default, a Space value is set to be vertically layed out with a "small" within src/Ant/Space.elm space between elements. Please update this documentation accordingly.

Alright, the docs are fixed now. How does it look?

Once #53 is merged I'll push a new release to https://package.elm-lang.org/

v4.2.3 is live :)
https://github.com/supermacro/elm-antd/releases/tag/4.2.3


How to define custom functions ?

In PHP we can do it like:
$pdo->sqliteCreateCollation('NATSORT', 'strnatcasecmp');

Then in the sqlite schema:
CREATE INDEX IF NOT EXISTS "titleNAT"   ON "files"("title" COLLATE NATSORT);

What's the equivalent of this in better-sqlite3 ?

Custom scalar functions can be defined as described here.
Custom aggregate and window functions can be defined as described here.
Custom collations (as in your example) are different, and are not currently supported by better-sqlite3. However, it's still possible to implement them in C/C++ and load them with the extension interface described here.


Rename backend -> backends

Seems to make more sense (as in https://github.com/almarklein/visvis2/issues/16).
I think the gui subpackage can remain as-is. guis does not make sense, and gui_toolkits is a bit long. @Korijn what do you think?

Sure :) I like consistency but "guis" seems odd.


bug: jail have problem when machines have drivers of different versions

The jail will only symlink libnvidia-ml.so.1 from one specific version, which may be empty in other machines. For example, I have two machines with drivers of 535.104.05 and 550.90.12. One jailed job runs into error.
# --------------------------- Jobs in jail environment
root@login-0:~# srun --gpus-per-task=8 --ntasks=2 ls -lh /usr/lib/x86_64-linux-gnu/|grep libnvidia-ml.so
lrwxrwxrwx   1 root root    25 Nov 16 08:13 libnvidia-ml.so.1 -> libnvidia-ml.so.550.90.12
-rwxr-xr-x.  1 root root  1.8M Jul  3 09:52 libnvidia-ml.so.535.104.05
-rwxr-xr-x   1 root root     0 Nov 16 08:13 libnvidia-ml.so.550.90.12
lrwxrwxrwx   1 root root    25 Nov 16 08:13 libnvidia-ml.so.1 -> libnvidia-ml.so.550.90.12
-rwxr-xr-x   1 root root     0 Nov 16 08:13 libnvidia-ml.so.535.104.05
-rwxr-xr-x.  1 root root  2.0M Sep 24 06:11 libnvidia-ml.so.550.90.12

root@login-0:~# srun --gpus-per-task=8 --ntasks=2 nvidia-smi
NVIDIA-SMI couldn't find libnvidia-ml.so library in your system. Please make sure that the NVIDIA Display Driver is properly installed and present in your system.
Please also try adding directory that contains libnvidia-ml.so to your system PATH.
srun: error: worker-1: task 0: Exited with exit code 12
Sat Nov 16 08:27:08 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.90.12              Driver Version: 550.90.12      CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|

# --------------------------- In workers
root@worker-1:/# ls -lh /usr/lib/x86_64-linux-gnu/|grep libnvidia-ml
lrwxrwxrwx   1 root root    17 Nov 16 08:13 libnvidia-ml.so -> libnvidia-ml.so.1
lrwxrwxrwx   1 root root    26 Nov 16 08:13 libnvidia-ml.so.1 -> libnvidia-ml.so.535.104.05
-rwxr-xr-x.  1 root root  1.8M Jul  3 09:52 libnvidia-ml.so.535.104.05
root@worker-1:/# ls -lh /mnt/jail/usr/lib/x86_64-linux-gnu/|grep libnvidia-ml
lrwxrwxrwx   1 root root    25 Nov 16 08:13 libnvidia-ml.so.1 -> libnvidia-ml.so.550.90.12
-rwxr-xr-x.  1 root root  1.8M Jul  3 09:52 libnvidia-ml.so.535.104.05
-rwxr-xr-x   1 root root     0 Nov 16 08:13 libnvidia-ml.so.550.90.12

root@worker-0:/# ls -lh /usr/lib/x86_64-linux-gnu/|grep libnvidia-ml
lrwxrwxrwx   1 root root    17 Nov 16 08:13 libnvidia-ml.so -> libnvidia-ml.so.1
lrwxrwxrwx   1 root root    25 Nov 16 08:13 libnvidia-ml.so.1 -> libnvidia-ml.so.550.90.12
-rwxr-xr-x.  1 root root  2.0M Sep 24 06:11 libnvidia-ml.so.550.90.12
root@worker-0:/# ls -lh /mnt/jail/usr/lib/x86_64-linux-gnu/|grep libnvidia-ml
lrwxrwxrwx   1 root root    25 Nov 16 08:13 libnvidia-ml.so.1 -> libnvidia-ml.so.550.90.12
-rwxr-xr-x   1 root root     0 Nov 16 08:13 libnvidia-ml.so.535.104.05
-rwxr-xr-x.  1 root root  2.0M Sep 24 06:11 libnvidia-ml.so.550.90.12

"Although users can install or modify software in the shared environment, it doesn't apply to some low-level packages directly bound to GPUs (CUDA, NVIDIA drivers, NVIDIA container toolkit, enroot, etc.)."
https://github.com/nebius/soperator/blob/main/docs/limitations.md#some-software-cant-be-upgraded-when-the-cluster-is-running
Sry, now I see ...

I have dug into this a little further: when two worker slurmd container call nvidia-container-cli to mount local drivers into jail, there exist two different versions of mounted nvdia libs but each worker can only one valid versioned-lib file. Then later, the last worker (race condition) calls ldconfig to symlink the non-versioned-lib to the versioned-lib. So only the last worker can follow the link to the valid lib file.

Hi, yes. To prevent application version pins from being overwritten, we plan to use AppArmor. In Q4, we will release an example demonstrating how to achieve this using the Security Profiles Operator.

Hi, yes. To prevent application version pins from being overwritten, we plan to use AppArmor. In Q4, we will release an example demonstrating how to achieve this using the Security Profiles Operator.

Good! Thanks!


Windows NvFBC Support?

Though the Nvidia Capture SDK was deprecated for Windows 10 and the latest version 7.1.1 does still work. Could this be supported somehow with this library? I tried to use it, but it links to an nvidia-fbc dynamic library that doesn't exist.

It looks like a different header would have to be used on the windows target OS C:\Program Files (x86)\NVIDIA Corporation\NVIDIA Capture SDK\inc\NvFBC\nvFBC.h and I believe C:\Program Files (x86)\NVIDIA Corporation\NVIDIA Capture SDK\lib\NvAPI\amd64\nvapi64.lib or C:\Program Files (x86)\NVIDIA Corporation\NVIDIA Capture SDK\lib\NvAPI\x86\nvapi.lib.

I have the bindgen package working but I need to finish and test Windows x86, Linux, and add a vendored feature flag for use with CI/Docs. This is however incompatible with the current safe lib wrapper that's made for v8, changes would need to be made to support both v7 and v8, but the unsafe bindgen package should work.
use std::{env, path::PathBuf};

fn main() {
	// TODO: Linux
	// TODO: Windows x86

	// Windows x64
	let include_path = "C:\\Program Files (x86)\\NVIDIA Corporation\\NVIDIA Capture SDK\\inc\\NvFBC";
	let library_path = "C:\\Program Files (x86)\\NVIDIA Corporation\\NVIDIA Capture SDK\\lib\\NvAPI\\amd64";
	let library_name = "nvapi64";
	let wrapper_name = format!("{include_path}/nvfbc.h");
	// This can be replaced with a wrapper.h if overrides are needed

	// TODO: Vendored feature flag - static header for CI/Docs

	println!("cargo:rustc-link-search={library_path}");
	println!("cargo:rustc-link-lib={library_name}");

	let bindings = bindgen::Builder::default()
		.header(wrapper_name)
		.clang_args(["-I", include_path])
		.parse_callbacks(Box::new(bindgen::CargoCallbacks::new()))
		.generate()
		.expect("Unable to generate bindings");

	let out_path = PathBuf::from(env::var("OUT_DIR").unwrap());
	bindings
		.write_to_file(out_path.join("bindings.rs"))
		.expect("Couldn't write bindings!");
}


Set boot diagnostics to managed storage account

How could one set the the Boot diagnostics to the recommended option of managed storage account?

Document Details

ID: 9A6F140C-9F1C-4701-9603-FC6107FCAF92
Content: Set-AzVMBootDiagnostic
Content Source: azure-powershell/src/Compute/Compute/help/Set-AzVMBootDiagnostic.md
Service: virtual-machines

@Ayanmullick Thanks for the question. We're investigating this and will get back to you shortly.

It's not currently possible. There is a feature request already logged for the engineering team in the appropriate repo to add this ability.


Field "editor" is still not working in firefox

editor is working in chrome but not working in firefox
my code
Kirki::add_field( 'safreen', array(     'type'        => 'editor',     'settings'    => 'safreen_welcome',     'label'       => esc_attr__( 'Home Page welcome section', 'safreen' ),     'help'        => esc_attr__( 'This is a tooltip', 'safreen' ),     'section'     => 'safreen_callout',     'default'     => esc_attr__( 'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Lorem ipsum dolor sit amet.', 'safreen' ),     'priority'    => 1, ) );

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/30934681-field-editor-is-still-not-working-in-firefox?utm_campaign=plugin&utm_content=tracker%2F2030945&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2030945&utm_medium=issues&utm_source=github).

can you please test the new develop branch?
The editor fields were completely refactored.

generate Js error and have a issue in css overflow screen not working dropdown control link h2 h1 and text color
TypeError: c is not a constructor

Fixed.


Header Logo is clicked when its not visible

Hi header logo is clicked on a normal .its fine.
But if we scroll to bottom its hided but click listener is still working.
Can u please fix asap.

You may do that using onPageScrolled method of ViewPager. Get the screen size and write your codes using if statement.

Sorry I can't get it.can u help me? Can I get small help in coding level..
On 11 Sep 2016 22:55, "Nuh Koca"<EMAIL_ADDRESS>wrote:

You may do that using onPageScrolled method of ViewPager. Get the screen
size and write your codes using if statement.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/florent37/MaterialViewPager/issues/282#issuecomment-246192184,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVGsjzHgmqsj_6sKma3AOSyagjCZ5JERks5qpDl9gaJpZM4J5-xh
.

hey while using onPageScrolled method of ViewPager.its not a interface.its directly asking values.
Then how can i use this method for get the screen position and write a code using if.
And scroll page listener also asking to set the api to 23.i m not like this approach.
i need to get the scrolling position for the view pager to fix the logo click issue. while its not visible.

Becoz of the current position only i set the header click listener to null.
And again asign the click listener.
Hope is this undestand.


swat4stats.com down

Hello,
first of all, thank you very much for your work.
I just noticed that swat4stats.com main page returns 404 Not Found and subpages are blank. Server list in-game is empty too.

I see it's solved now.


Visual Studio 2017 integration

Make any actions necessary for the project to be compatible with VS2017

There are no incompatibilities of the project with VS2017 that I know of. Personally, I have been working in VS2017 without issues.


include microseconds when decoding datetime objects

Thanks for reviewing and merging!
Good point on the serialization discrepancy. The major meaningful difference to me is that the sub-second portion of the datetime is discarded during serialization. But this probably doesn't matter most of the time.
Could be fixed by changing
https://github.com/stac-utils/stac-pydantic/blob/master/stac_pydantic/shared.py#L18
to include the %f (microsecond) part.
DATETIME_RFC339 = "%Y-%m-%dT%H:%M:%S.%fZ"

Originally posted by @colecloudtostreet in https://github.com/stac-utils/stac-pydantic/issues/75#issuecomment-843369648

Also, the constant for this should be DATETIME_RFC3339 not DATETIME_RFC339 (there are 3 3s, not 2).

Another major meaningful difference is that this regex is used in the Search object, so datetimes with fractional seconds in them throw an error when used by pystac-client in a query.

should be fixed now 🙏


Re-work pipelines YAML using extends and parameters

This refactors the build to use newer YAML features to reduce duplication and better document which aspects of the build vary platform to platform.
All possible steps for a build job are defined in the build-job.yml template, and which particular steps are included is controlled via parameter flags. The parameter flags document which things can vary based on scenario (CI vs release) and platform, and since the parser enforces their presence, type, and in some case values, template steps checking for missing variables have been removed. The pipeline.yml template, which is extended by both the CI and release pipelines, defines the build jobs for each platform. pipeline.yml accepts StageLists for stages that need to execute before and after the build stage, which the release pipeline uses to do the release branch creation and GitHub release and PR creation.
The runtime conditions that conditionally skipped irrelevant steps have been replaced with template expressions that exclude irrelevant steps from the build altogether based on the parameters passed into the template.
The release pipeline now requires version and derivedFrom parameters at queue time. Because these are defined as top level parameters, fields for them will appear on the queue build screen.
Here is a recent CI build using these templates.
For testing the release pipeline, I used a branch where I temporarily tweaked some of the steps to be no ops (passing the --dryrun flag to scripts, for example).

There's something off about the Checks - it's duplicated each one or something.


Typo

The widget should renamed or the include updated like this :), if not in case sensitive server it will not work :)

This functionality will be available in the next version as  "widgets/share-book/share-book"  . you can see it now on develop_2.0 branch. It will be merged to master soon. Thanks :)


cannot use hooks in seed model, errors with "not hydrated"

Would like to create indexes on a seed model, see title.

actually the "not hydrated" error appears to occur not just by attempting to add hooks, but also by changing the data in the csv.

@markgraphene this is a known issue that we had in the past. To mitigate this, apply the plan with the --no-diff command when changing that seed model:
sqlmesh plan --no-diff <env>

You may need to do just once after you change every existing seed model.
To fix this for all seed models at once, add a stamp attribute with an arbitrary string value to all seed model definitions:
MODEL (
    ...
    stamp 'fix hydration issue'
)

and then run:
sqlmesh plan --no-diff <env>

for all of them.


Configurable regex for file and folder names.

Do you think you could allow in lfm.php to manually specify our own regex for the folder name check?
I wanted to be able to allow spaces, without modifying the source files. The regex '/[^\w-]/i' is used in FolderController and RenameController.
Also, the regex '/[^A-Za-z0-9-']/' for the files could also be replaced in lfm.php.
Another solution would be to specify our own function to check and rename files and folders.

I get what you are saying. Sounds like a good addition.
If this feature makes the alphanumeric_directory and alphanumeric_filename options in lfm.php are a little redundant since this feature can do exactly the same and more. Can those two config values be removed or keep it in for backwards compatibility?
@g0110280 Any thoughts?

Maybe we can make it possible to let users modify the rule from LfmConfigHandler. And I suggest we can only leave one config like regex_check to toggle this behavior.


metab_run SB handling, view_file/folder, meta_basic updates

@jread-usgs - metab_run and meta_basic are gaining presence on SB with this PR. could you give this a skim and maybe try out view_file and view_folder on your computer? I haven't done any mac os testing for those, but they're pretty handy convenience functions.

all the locate_'s worked for me and were cool. I like it! Do you want to clear up the warnings/errors, or address them later?

the view_'s work well too for me on mac :+1:

it's hopeless for appveyor. i'm rerunning travis, because that looks like a silly download issue that didn't happen last time. knock wood.

hmmm...I had local errors and warnings on my check. I will run again.

what the heck, linux??
0.33s$ wget http://downloads.sourceforge.net/project/mcmc-jags/JAGS/3.x/Source/JAGS-3.4.0.tar.gz
--2015-07-16 21:37:38--  http://downloads.sourceforge.net/project/mcmc-jags/JAGS/3.x/Source/JAGS-3.4.0.tar.gz
Resolving downloads.sourceforge.net (downloads.sourceforge.net)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://downloads.sourceforge.net/#!/project/mcmc-jags/JAGS/3.x/Source/JAGS-3.4.0.tar.gz [following]
--2015-07-16 21:37:38--  http://downloads.sourceforge.net/
Reusing existing connection to downloads.sourceforge.net:80.
HTTP request sent, awaiting response... 200 OK
Length: 639 [text/html]
Saving to: `JAGS-3.4.0.tar.gz'
100%[======================================>] 639         --.-K/s   in 0s
2015-07-16 21:37:38 (121 MB/s) - `JAGS-3.4.0.tar.gz' saved [639/639]
0.01s$ tar xfvs JAGS-3.4.0.tar.gz
gzip: stdin: not in gzip format

boooo!

@jread-usgs, do you have JAGS on your computer? and do you have the bleeding-edge versions of sbtools and streamMetabolizer? what warnings/errors are you getting? on my computer i get
Status: 2 NOTEs

neither of which bother me much:
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Alison Appling<EMAIL_ADDRESS>New submission
Non-FOSS package license (file LICENSE)
Strong dependencies not in mainstream repositories:

and
* checking top-level files ... NOTE
File README.md cannot be checked without 'pandoc' being installed.

back down to 2 notes - thanks, luke!
* checking CRAN incoming feasibility ... NOTE
Maintainer: ‘Alison Appling<EMAIL_ADDRESS>New submission
Non-FOSS package license (file LICENSE)
Strong dependencies not in mainstream repositories:
  sbtools, streamMetabolizer, geoknife, unitted
Checking URLs requires 'libcurl' support in the R build

and
* checking package dependencies ... NOTE
  No repository set, so cyclic dependency check skipped

i can live with these for a long time.


RPM/DEB installers

It would be nice if there were RPM/DEB installers for influxdb-relay available in the official yum/apt repos.
Many people don't have much experience with go and since the infrastructure is already in place it would be fairly easy to impelment and would greatly help speed up implementation for most people.

I'll look in to seeing what would be required. As of now, we're are not versioning the relay as it is very much not finalized, and major changes are happening with just about every merge (config options, behavior, etc.), although hopefully this will settle down over the next month.
I'll leave this issue open so that more people can +1 your initial comment.

#25 Has been merged, and packages can be build using the provided build script (and recommended docker container) with the instructions in the README.
At this time, influxdb-relay will not be included in official influxdata repositories.


[frontend] edit/delete post UI

User can generate the proof of epoch key of the post (or comment)
Then delete the post (The hashContent will be set 0 on-chain)
But all the comments and votes should still be left

I'm unable to delete the post on staging: https://social-staging.unirep.io
step:
complete a UST,
go to my page,
find a post, edit -> delete

the UI can't delete my post.

Are you able to delete a post? @ChialiTsai

Are you able to edit a post? @ChialiTsai


Failed to get SSL from certbot

Update: I tried after 1 hour and now all my websites are with SSL.
I recently wiped my server and created new instance with new ip. point my dns to new ip. Earlier I was using jc21 NPM. Now I installed your one. Everything works fine. But I can not get SSL on my website.. Earlier attempts were failed because of firewalld blocking 80 and 443 ports. Now I added them to allow list. Now I can access my website through http but I can not git it working with SSL. Here is container log:
Server: nginx
Date: Mon, 17 Jul 2023 18:45:26 GMT
Content-Type: application/json
Content-Length: 1055
Connection: keep-alive
Boulder-Requester:<PHONE_NUMBER>
Cache-Control: public, max-age=0, no-cache
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Replay-Nonce: 15C9Fi9emmjENdUcH-2OxLuHO1S3Q0tfbPm2FS_Fw_35TaM
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800

{
  "identifier": {
    "type": "dns",
    "value": "proxy.afzal.website"
  },
  "status": "invalid",
  "expires": "2023-07-24T18:45:25Z",
  "challenges": [
    {
      "type": "http-01",
      "status": "invalid",
      "error": {
        "type": "urn:ietf:params:acme:error:connection",
        "detail": "<IP_ADDRESS>: Fetching http://proxy.afzal.website/.well-known/acme-challenge/r1oBTyCuUTp9vaVUYs58Nsd6W71yfORGk59Ht6YBSUc: Error getting validation data",
        "status": 400
      },
      "url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/246483032907/RW8POA",
      "token": "r1oBTyCuUTp9vaVUYs58Nsd6W71yfORGk59Ht6YBSUc",
      "validationRecord": [
        {
          "url": "http://proxy.afzal.website/.well-known/acme-challenge/r1oBTyCuUTp9vaVUYs58Nsd6W71yfORGk59Ht6YBSUc",
          "hostname": "proxy.afzal.website",
          "port": "80",
          "addressesResolved": [
            "<IP_ADDRESS>"
          ],
          "addressUsed": "<IP_ADDRESS>"
        }
      ],
      "validated": "2023-07-17T18:45:25Z"
    }
  ]
}
2023-07-17 23:45:26,682:DEBUG:acme.client:Storing nonce: 15C9Fi9emmjENdUcH-2OxLuHO1S3Q0tfbPm2FS_Fw_35TaM
2023-07-17 23:45:26,682:INFO:certbot._internal.auth_handler:Challenge failed for domain proxy.afzal.website
2023-07-17 23:45:26,682:INFO:certbot._internal.auth_handler:http-01 challenge for proxy.afzal.website
2023-07-17 23:45:26,682:DEBUG:certbot._internal.display.obj:Notifying user:
Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
  Domain: proxy.afzal.website
  Type:   connection
  Detail: <IP_ADDRESS>: Fetching http://proxy.afzal.website/.well-known/acme-challenge/r1oBTyCuUTp9vaVUYs58Nsd6W71yfORGk59Ht6YBSUc: Error getting validation data

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

2023-07-17 23:45:26,683:DEBUG:certbot._internal.error_handler:Encountered exception:
Traceback (most recent call last):
  File "/usr/local/certbot/lib/python3.11/site-packages/certbot/_internal/auth_handler.py", line 108, in handle_authorizations
    self._poll_authorizations(authzrs, max_retries, max_time_mins, best_effort)
  File "/usr/local/certbot/lib/python3.11/site-packages/certbot/_internal/auth_handler.py", line 212, in _poll_authorizations
    raise errors.AuthorizationError('Some challenges have failed.')
certbot.errors.AuthorizationError: Some challenges have failed.

2023-07-17 23:45:26,683:DEBUG:certbot._internal.error_handler:Calling registered functions
2023-07-17 23:45:26,683:INFO:certbot._internal.auth_handler:Cleaning up challenges
2023-07-17 23:45:26,683:DEBUG:certbot._internal.plugins.webroot:Removing /tmp/acme-challenge/.well-known/acme-challenge/r1oBTyCuUTp9vaVUYs58Nsd6W71yfORGk59Ht6YBSUc
2023-07-17 23:45:26,684:DEBUG:certbot._internal.plugins.webroot:All challenges cleaned up
2023-07-17 23:45:26,684:DEBUG:certbot._internal.log:Exiting abnormally:
Traceback (most recent call last):
  File "/usr/local/certbot/bin/certbot", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/local/certbot/lib/python3.11/site-packages/certbot/main.py", line 19, in main
    return internal_main.main(cli_args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/certbot/lib/python3.11/site-packages/certbot/_internal/main.py", line 1864, in main
    return config.func(config, plugins)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/certbot/lib/python3.11/site-packages/certbot/_internal/main.py", line 1597, in certonly
    lineage = _get_and_save_cert(le_client, config, domains, certname, lineage)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/certbot/lib/python3.11/site-packages/certbot/_internal/main.py", line 141, in _get_and_save_cert
    lineage = le_client.obtain_and_enroll_certificate(domains, certname)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/certbot/lib/python3.11/site-packages/certbot/_internal/client.py", line 517, in obtain_and_enroll_certificate
    cert, chain, key, _ = self.obtain_certificate(domains)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/certbot/lib/python3.11/site-packages/certbot/_internal/client.py", line 428, in obtain_certificate
    orderr = self._get_order_and_authorizations(csr.data, self.config.allow_subset_of_names)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/certbot/lib/python3.11/site-packages/certbot/_internal/client.py", line 496, in _get_order_and_authorizations
    authzr = self.auth_handler.handle_authorizations(orderr, self.config, best_effort)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/certbot/lib/python3.11/site-packages/certbot/_internal/auth_handler.py", line 108, in handle_authorizations
    self._poll_authorizations(authzrs, max_retries, max_time_mins, best_effort)
  File "/usr/local/certbot/lib/python3.11/site-packages/certbot/_internal/auth_handler.py", line 212, in _poll_authorizations
    raise errors.AuthorizationError('Some challenges have failed.')
certbot.errors.AuthorizationError: Some challenges have failed.
2023-07-17 23:45:26,685:ERROR:certbot._internal.log:Some challenges have failed.
/tmp/certbot-log #

so it works now?

so it works now?

Ofcourse


[Bug Report] - 1.16.5 Villager Lasso

Describe the bug
Using the golden lasso on villagers doesn't work, it picks them up but when placing them they return to their original location
To Reproduce
Steps to reproduce the behavior:

Go to a villager
Click on villager with golden lasso
place villager at new location
See error - villager has returned to where they came from

Expected behavior
Villager should be at the new location
Screenshots
none
Mod Info (please complete the following information):

Forge: forge-36.2.39
MC Version: 1.16.5
Mod Version: 1.3.2

Additional context
Also happens with cows, haven't tested other mobs

Update: pigs and chickens seem to work

I can't reproduce this at all in testing


Add healthcheck on default 8123 port

Description:
Add healthcheck on default 8123 port so status can be monitored
https://docs.docker.com/engine/reference/builder/#healthcheck

Hi @poldim,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Wouldn't this cause anyone using a custom port (like 443) to be unhealthy?
Why not use an env variable?

Since it's the docker, it's checking the internal containers 8123 port.  If
you choose to map it to an external port, you would map your system's
external port, 443 in your example, to 8123 of the container.  So, the
container will continue to run the HA GUI on the containers port 8123.
Thus, mapping to another port, will not fail the healthcheck.
On Wed, Mar 7, 2018 at 11:39 AM, Robert Accettura<EMAIL_ADDRESS>wrote:

Wouldn't this cause anyone using a custom port (like 443) to be
unhealthy?
Why not use an env variable?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/12966#issuecomment-371199837,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQFpUe2X6M6mCQQbszWB2GsL-srOAKpXks5tcA1TgaJpZM4SgjJE
.

Makes sense 👍

Home Assistant is great at loading up even when there are setup problems, it then displays a persistent notification in the front-end. In all my time using Home Assistant through Docker, I think I've never seen a hass container being "unhealthy" - e.g. running but not responding to outside connections. So I think while we have the HEALTHCHECK instruction now, I see no value in adding it. We shouldn't do stuff like this just because we can. A simple --restart=always has worked perfectly for me.
HEALTHCHECK is (only) supported since docker 1.12; while that version is quite old, I think some people would quickly complain because they're not using the latest docker version.
This is from my own experience: Many new users seem to use the http: server_port: x option in configuration.yaml instead of a custom port mapping in docker. We would break lots of people's setups. At least for changing the docker system is connected with lots of unwanted overhead. I don't like people having to change their setups for such a change.
SSL: What if users want to use the built-in https support of Home Assistant. Your curl command only assumes HTTP as far as I see and would probably break with built-in HTTPS.
Home Assistant can also be run without an http enabled. We should support that (for example when just using a localHome Assistant as a relay to a public Home Assistant server via MQTT eventstream) The health check would break all those setups.

Home Assistant is great at loading up even when there are setup problems, it then displays a persistent notification in the front-end. In all my time using Home Assistant through Docker, I think I've never seen a hass container being "unhealthy" - e.g. running but not responding to outside connections. While we could add the HEALTHCHECK instruction, I see no value in adding it. We shouldn't do stuff like this just because "we can". A simple --restart=always has worked perfectly for me.

I agree that HA is rather good at always starting up.  For me, I've used this status to alarm me if anything goes away and my alarms are based on not being in healthy status.  This happens every now and then, but admittedly, often due to startup issue of the host and partial startup of the containers that HA depends on.

HEALTHCHECK is (only) supported since docker 1.12; while that version is quite old, I think some people would quickly complain because they're not using the latest docker version.
This is from my own experience: Many new users seem to use the http: server_port: x option in configuration.yaml instead of a custom port mapping (--port "8123:80") in docker. We would break lots of people's setups. At least for me, changing the docker system is connected with lots of unwanted overhead. -> I don't like people having to change their setups for such a change.

1.12 is ~2 years old.  I don't think anyone is running HA on anything that old.  I agree that some users could be using the internal HA configuration for ports, but this is against docker's best practices that say you should allow docker to handle routing of your networking/ports instead of individual containers.

SSL: What if users want to use the built-in https support of Home Assistant? Your curl command only assumes HTTP endpoints as far as I see and would probably break with built-in HTTPS.

Valid point.  Maybe if could be modified to ping either and provide a response.

Home Assistant can also be run without an http enabled. We should support that (for example when just using a localHome Assistant as a relay to a public Home Assistant server via MQTT eventstream) The health check would break all those setups.

Valid point that some users could be disabling http.  Now that HA collects stats on components used, it would be very easy to see what % of people are not using http.  My guess is that it's very small.  Additionally, healthcheck would not break the setup as it's just a status notification.  Unless you've setup additional configurations, no action is taken on an unhealthy container, it would just report as unhealthy.
This is my first foray into contributing code, so I might be way off base here.  To me, it seems like the standard that it "may break some things for someone" is too high of a bar.  There are always people that have some configuration that is broken by some update.  That's why it's Home Assistant and not an Apple product.  With that said, I completely agree that change for the sake of change is pointless.  If the greater community feels that this is a worthless feature, by all means, let's not implement it.
My thought was to think of the average user that may be running HA in a docker setup.  I thought these users would benefit from it.

That is wrong. We can't know the port of running instance. If we would that, we need parse the config file or adapt the hass.io API they ask HomeAssistant for the port.
True, user should change the port on system like docker/compose/hassio but he does and we can't prevent this.

We will not merge this because this is a health check for the frontend component, however it is totally possible to run headless (no frontend) and as Pascal said, the user can change the port inside Docker too.


Retain the information when producing the CHD Redump dats.

The CHD Redumps do not retain the <category> information from the original Redump dats. That information is useful when using Retool to generate 1G1R dats.

This should be easy to fix. I check what additional information is missing.

Added the category in 0.262a.


core:   Don't fire HAProxyMessage further up the pipeline

Additionally, don't release the interior TLVs as the channel clode future takes care of that now

I also confirmed there are no other handlers in the pipeline that would read this message.


⚠ Bofrost.be has degraded performance

In 18a65af, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 968 ms

Resolved: Bofrost.be performance has improved in 736e611 after 10 minutes.


Separate upgrade operations into own section

Moved upgrade ondat and upgrade platform into a new section so it is easier for users to find the operations
NOTE: need to set up redirections for the pages involved

Redirection needed:
https://docs.ondat.io/docs/operations/using-rolling-upgrades/ -> https://docs.ondat.io/docs/upgrade/using-rolling-upgrades/
https://docs.ondat.io/docs/operations/upgrade/ -> https://docs.ondat.io/docs/upgrade/upgrade/


Implement optional deletion of custom PDN resources when a harvestable resource is deleted

This PR makes use of the functionality being proposed in geosolutions-it/geonode#869 in order to be able to delete custom resources generated by the PDN harvester.
Whenever a harvestable_resource is deleted, if the corresponding harvester has delete_orphan_resources_automatically = True, then the custom resource (i.e an entry on pdn.models.Alerts, pdn.models.Expert, etc) is also deleted

This should not be merged yet, as it depends on having some code in GeoNode that is still being re-proposed - I'd like to set this PR as a draft, but I can't seem to find that option now

@giohappy
The upstream functionality needed for this has been merged in geonode/geonode#7856 so we can now merge this PR here


Efficient way to compute element dofs

dofs(e::AbstractElement) = mergewith(vcat, dofs.(nodes(e))...)
"Returns the `AbstractElement` `e` dofs."
function dofs(e::AbstractElement)
    vecdfs = dofs.(nodes(e))

Create a cache with element dofs once the Mesh is created.
Loop over nodes(e)

This was addressed in https://github.com/ONSAS/ONSAS.jl/pull/363/files , creating an iterator for dofs of a mesh.


For ASP.NET MVC?

Can I use this package for ASP.NET MVC? Or similar package available for ASP.NET MVC from Microsoft?

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

ID: d781aae8-fa5c-27a4-5d3d-64c60d008b4c
Version Independent ID: ba2bfca5-06a9-abc8-77f2-fbcb0dcb74c3
Content: Quickstart for adding feature flags to ASP.NET Core
Content Source: articles/azure-app-configuration/quickstart-feature-flag-aspnet-core.md
Service: azure-app-configuration
GitHub Login: @yegu-ms
Microsoft Alias: yegu

@anuraj Thanks for the question! I have assigned the issue to the content author to evaluate and update as appropriate.

@anuraj, thanks for asking! The current feature management library doesn't work on ASP.NET full framework yet. It currently has a dependency the .NET Core configuration system for retrieving feature flags.
#please-close


Add a basic docker environment.

It's useful to have a encapsulated local environment, when I'm not a frontend dev with nodejs already set up. This is a very basic setup, but it's working for me.

The change is inspired by https://dev.to/azawakh/don-t-forget-to-give-host-0-0-0-0-to-the-startup-option-of-webpack-dev-server-using-docker-1483

Makes sense, I will try to add some basic docs later today.

I'm not sure, but you're probably right. Can we leave it there for now, given the time constraints? We can improve it for later strikes/events later.

Basic instructions are added. Quick&dirty for now.


isAbsoluteURL regex doesn't work like expected

Bug Report

Q
A

BC Break
no

Version
1.52

Summary
isAbsoluteURL regex doesn't work like expected
Current behavior
Impossible to add urlComponents.queryItems coz path is absolute :/
How to reproduce
/connect/login is an absolute URL
connect/login is an absolute URL
Expected behavior
/connect/login is not an absolute URL
connect/login is not an absolute URL
I think error is the ? after the first group in the regex

Thank you for your report, I've added a new regular expression validated using NSRegularExpression and several tests.

Thanks for your awesome works !!!


Now social media links are opening in another tab

Issue Number
fixes #267

Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
A clear and concise description of it.
Additional context (OPTIONAL)
Add any other context or screenshots about the feature request here.
Test plan (OPTIONAL)
A good test plan should give instructions that someone else can easily follow.
How someone can test your code?
Checklist

[x] I have added my name in the contributors list at the end of README.md file.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] The title of my pull request is a short description of the requested changes.
[x] Open Source Program names(OPTIONAL: If you participated in any open-source program then please mention the program name here)

@tjanhvi you misunderstood.
You have to redirect only social links to a new tab, not every page to a new tab.
In #280 I meant to do similar changes in the home, signup, and help page.


[typescript] Make types of componentsProps consistent

As discussed in #26810, this changes the types of unstyled components' componentsProps fields to Record<string, any>.
The current solution requires developers to augment TS modules when using props other that defined in the interface.

Should we update pickers, date picker, and autocomplete too?

In Autocomplete we have componentsProps: { clearIndicator } but don't allow customizing components: { ClearIndicator }. I think in this case we can leave more strongly typed componentsProps. I'll update the other cases.

@eps1lon Take a look at the discussion in #26810 for rationale.
I'm not doing this just for the sake of consistency. I believe having Record<string, any> will be easier to use for developers than { as, styleProps } as they won't have to do module augmentation when adding any other prop.
For DX it would be ideal if componentsProps types' were inferred from components, but, as we discussed in #26810, we can't have that, so this is the compromise.

The general direction so far has been "strict by default" and let developers loosen up type-checking if they need to. The reverse is usually not possible. This goes against that direction since you can now write <Foo componentProps={{root:{...{className: '', c1assName: ''}}}} /> which the type-checker will never catch.  With <Foo componentProps={{root:{...{className: '', c1assName: ''} as any}}} /> it's at least a bit more obvious that componentProps needs to be treated carefully.
I do agree that module augmentation is the wrong tool here since it applies globally.
Being consistent here is not the problem. Though it's unclear here that we do need consistency. The problem is that we don't move in a consistent direction i.e. some components are now looser, some are stricter.
I think we discussed inferring a while back? Can you share the latest progress so that I can poke at it a bit?

I think we discussed inferring a while back? Can you share the latest progress so that I can poke at it a bit?

I haven't looked into it much since we talked about it. Just added some type tests in SwitchUnstyled.spec.tsx:
https://github.com/michaldudak/material-ui/tree/feat/typed-slots/packages/material-ui-unstyled/src/SwitchUnstyled

@eps1lon have you had a chance to take a look at the code in my feat/typed-slots branch? Do the tests make my intention clearer?

We got the first issue about type errors in componentsProps: #27869
I think, at the very least, we can type componentsProps as the props of the default corresponding component.
For example: In SwitchUnstyled, the default Root component is span, so componentsProps.root would have the HTMLAttributes<HTMLSpanElement> & { as?: React.ElementType, ownerState: SwitchState } type.
It would still require casting when something else is provided to components.Root, but in cases where just componentsProps.root is customized, it will work fine and won't require any additional work from developers.

I think, at the very least, we can type componentsProps as the props of the default corresponding component.
For example: In SwitchUnstyled, the default Root component is span, so componentsProps.root would have the HTMLAttributes & { as?: React.ElementType, ownerState: SwitchState } type.

I like this.

@michaldudak Sounds great, and identical to the current tradeoff of the xxxProps and xxxComponent props.

Sure, it's on my to-do list. I'll likely start today.

After further thought, I decided to use just HTMLAttributes / ComponentProps of the default component and not augment it with { as, ownerState }. When as property is used, the type of props change, so devs would need to cast or augment modules anyway.
As for ownerState - @mnajdova what's the actual use case for providing it in componentsProps? As I understand it, ownerState is set by the owner, not provided from the outside.

As for ownerState - @mnajdova what's the actual use case for providing it in componentsProps? As I understand it, ownerState is set by the owner, not provided from the outside.

Originally, the styleProps were props used for styling, so the component itself, could propagate some props they want to use for styling purposes, for example propagate a color prop as part of the styleProps. We have currently an example of this in the Badge component - https://github.com/mui-org/material-ui/blob/next/packages/material-ui/src/Badge/Badge.js#L243
If we sent directly this prop to the unstyled component, we would need to also configure somehow that it should not be spread on the DOM elements.

We discussed it with @mnajdova off-site and came to the conclusion that adding more properties to ownerState by the styled component isn't the best idea. After all, this is the state of the owner, that is - the unstyled component.
Instead, if any additional props are needed to style the slot (as in the Badge example), we can pass them directly in componentsProps.
These extra props must not be used when a host component is used on a slot, so the final version should look as follows:
 componentsProps={{
   root: {
-    ...componentsProps.root,
-    ...((!components.Root || !isHostComponent(components.Root)) && {
-      ownerState: { ...componentsProps.root?.ownerState, color },
-    }),
+    color: isHostComponent(BadgeRoot) ? undefined : color,
   },

Obviously, this creates another problem with typing the componentsProps. We haven't found anything better than:
export interface BadgeComponentsPropsOverrides {}

// ...

componentsProps: {
  root: React.HTMLAttributes<HTMLSpanElement> & BadgeComponentsPropsOverrides;
  badge: React.HTMLAttributes<HTMLSpanElement> & BadgeComponentsPropsOverrides;
}

This will allow developers to use all the standard HTML attributes out of the box and add custom ones using module augmentation.

export interface BadgeComponentsPropsOverrides {}

// ...

componentsProps: {
  root: React.HTMLAttributes<HTMLSpanElement> & BadgeComponentsPropsOverrides;
  badge: React.HTMLAttributes<HTMLSpanElement> & BadgeComponentsPropsOverrides;
}

I like that this is strict by default, but can be augmented to accept more props 👍

@michaldudak one quesiton. Should we maybe use just React.HTMLAttributes<HTMLElement>? I am asking because developers may provide components={{ Root: 'div' }}. I am not sure..
 componentsProps: {
-  root: React.HTMLAttributes<HTMLSpanElement> & BadgeComponentsPropsOverrides;
-  badge: React.HTMLAttributes<HTMLSpanElement> & BadgeComponentsPropsOverrides;
+ root: React.HTMLAttributes<HTMLSpanElement> & BadgeComponentsPropsOverrides;
+ badge: React.HTMLAttributes<HTMLSpanElement> & BadgeComponentsPropsOverrides;
 }

HTMLElement, HTMLDivElement, HTMLSpanElement and many others are actually the same thing in this context (see https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/react/global.d.ts#L44)

@oliviertassinari, @mnajdova, @eps1lon Is there anything else you'd like to see changed, or is this good to go? I think it's worth merging it before the next RC.


With the new bpick behavior, gh-r are being forced to install on every update.

Describe the bug
gh-r plugins are being incorrectly marked as outdated and being updated on each update run
To Reproduce
zinit update <any gh-r plugin>
Expected behavior
gh-r plugins shouldn't update when they don't have to.
Versions:

$ZSH_VERSION == 5.8
Operating system name and version (uname -a): Linux Nicks-Laptop 5.6.0-10.2-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 5.6-4.1~bullseye (2020-05-05) x86_64 GNU/Linux

Additional context
https://github.com/zdharma/zinit/commit/b94bb051afebab52f356de4e8f4e856660a6e7b0#commitcomment-39080122

Confirmed on both Ubuntu and mac OS.

It should be fixed now, thanks.

@psprint did you push the fix yet ? Your last commit is older than your comment, so I'm not sure, but if that is the case it is not fixed for me on the mac:
~/.zinit/bin master
❯ git log
commit c6ce7b04136486b8d1917a87a2aee1725fffc313 (HEAD -> master, origin/master, origin/HEAD)
Author: SG<EMAIL_ADDRESS>Date:   Tue May 12 16:19:08 2020 +0200

    README.md

~
❯ zi update
Assuming --all is passed
Updating Zinit...
Note: updating also unloaded plugins
Updating lotabout/skim
(Requesting `skim-v0.8.1-x86_64-apple-darwin.tar.gz'... Current version: v0.8.1.)
############################################################################################################################################################################## 100.0%############################################################################################################################################################################## 100.0%
ziextract: Unpacking the files from: `skim-v0.8.1-x86_64-apple-darwin.tar.gz'...
ziextract: Successfully extracted and assigned +x chmod to the file: `sk'.

Binary release already up to date (version: )
Binary release already up to date (version: )
Binary release already up to date (version: )
Binary release already up to date (version: )
... etc. ...

Ok, I've pushed the fix now, thanks again.

Ok, I've pushed the fix now, thanks again.

@psprint yeay! first try ;)
❯ zi update
Assuming --all is passed
Updating Zinit...
2020-05-12 c3bed833 *side,*autoload: Handle the multiple bpick'' during update #334
Note: updating also unloaded plugins
Updating lotabout/skim
Binary release already up to date (version: v0.8.1)
Updating rust-analyzer/rust-analyzer
Binary release already up to date (version: nightly)

Thank you for the fix!


change workqueue replication to use _reprecator db.

And also monitor whether replication is working in wmstats

No pylint warnings for pull request 5011:


The app freezes when loading files bigger than 1 megabyte

I am currently dealing with the same issue in Quick Pad and the only solution seems to be to disable loading files larger then 1 MB.

I am currently dealing with the same issue in Quick Pad and the only solution seems to be to disable loading files larger then 1 MB.

That seems to affect also Notepads, here's a ticket about the issue https://github.com/JasonStein/Notepads/issues/10
(as a temporary workaround the app simply doesn't open the file showing a pop-up messaege

There is an issue in the WinUI repository for this https://github.com/microsoft/microsoft-ui-xaml/issues/1842.

Upvoted👍

Upvoted as well. 😊


[BUG]: Team environment deletion time logic

Describe the bug
It seems that the logic for the select query for environments that have not submitted a business justification within 7 days has a flaw. The filter query is:
admin_environmentsku eq 'Teams' and admin_environmentdeleted eq false and  admin_environmentcreatedon le @{body('Get_7_days_in_the_past')}
Assuming this runs every Monday: This will return all environments that have been created in the last 7 days. Since there is no check for actual environment age after this, any environment created within the last week (whether it is 1 day old or 7 days old) that has not given a justification will be deleted.
Component:

Solution: Governance
Version: 1.03
App or Flow: Microsoft Teams Admin  | Weekly Clean Up of Microsoft Teams environments

Expected behavior
The expected behavior is that environments that are only 7 days old or older with no business justification would be deleted. This could be accomplished by either changing the query to 'ge' rather than 'le' or by defining an age range.

Hello. I don't quite follow you here.
The action List 7 day environments returns teams environments that were created 1 week ago or older. Later in the flow we loop through these returned environments in the loop Apply to each Teams Environment so only these environments are subject to the actions in that loop.
Can you please let me know, did you see us deleting new environments? Or are you just interpreting the flow?

Closing out items without further action items


[SPARK-42510][CONNECT][PYTHON][TEST] Enable more DataFrame.mapInPandas parity tests

What changes were proposed in this pull request?
Enables more DataFrame.mapInPandas parity tests.
Why are the changes needed?
Now that we have SparkSession.conf, we can enable some more parity tests for DataFrame.mapInPandas
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Enabled related tests.

Merged to master and branch-3.4.


Exception Value:	 Country matching query does not exist.

Debug Log for oscar paypal exception:

Request Method:
GET

https://smartagropayment.pythonanywhere.com/checkout/paypal/preview/9/?token=EC-07841901G97298611&PayerID=ZLYW5MPC2ZVNJ

1.11.20

DoesNotExist

Country matching query does not exist.

/home/smartagropayment/.virtualenvs/oscar/local/lib/python2.7/site-packages/django/db/models/query.py in get, line 380

/usr/local/bin/uwsgi

2.7.12

['/var/www',  '.',  '',  '/var/www',  '/home/smartagropayment/.virtualenvs/oscar/lib/python2.7',  '/home/smartagropayment/.virtualenvs/oscar/lib/python2.7/plat-x86_64-linux-gnu',  '/home/smartagropayment/.virtualenvs/oscar/lib/python2.7/lib-tk',  '/home/smartagropayment/.virtualenvs/oscar/lib/python2.7/lib-old',  '/home/smartagropayment/.virtualenvs/oscar/lib/python2.7/lib-dynload',  '/usr/lib/python2.7',  '/usr/lib/python2.7/plat-x86_64-linux-gnu',  '/usr/lib/python2.7/lib-tk',  '/home/smartagropayment/.virtualenvs/oscar/local/lib/python2.7/site-packages',  '/home/smartagropayment/.virtualenvs/oscar/lib/python2.7/site-packages',  '/home/smartagropayment/eshop']

Sat, 8 Jun 2019 02:37:27 -0500

Hi there. We use Github only for managing bugs and feature requests, and not for support. We recommend that you ask for help on Stack Overflow using the django-oscar tag, or joining our slack workspace and asking a question there. Thanks.


repeated instances of HTTP Error 503

Checklist

[ ] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2019.05.20
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[ ] I've read bugs section in FAQ

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-f', '18', '-4', '-v', 'https://www.youtube.com/user/ReviewTechUSA/videos?disable_polymer=1', '--playlist-items', '1']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2019.05.20
[debug] Python version 3.6.8 (CPython) - Linux-5.0.15_1-x86_64-with-glibc2.3.4
[debug] exe versions: ffmpeg 4.1.3, ffprobe 4.1.3
[debug] Proxy map: {}
[youtube:user] ReviewTechUSA: Downloading channel page
[youtube:playlist] UU__Oy3QdB3d9_FHO_XG1PZg: Downloading webpage
[download] Downloading playlist: Uploads from ReviewTechUSA
[youtube:playlist] playlist Uploads from ReviewTechUSA: Downloading 1 videos
[download] Downloading video 1 of 1
[youtube] Kjvmbtfz56w: Downloading webpage
[youtube] Kjvmbtfz56w: Downloading video info webpage
[debug] Invoking downloader on 'https://r2---sn-8xgp1vo-ab5e.googlevideo.com/videoplayback?id=o-AGhQs_t9v2tfYpUIDXOkGlIXVEa4OIDVFiU-KTWaV7eX&itag=18&source=youtube&requiressl=yes&mm=31%2C29&mn=sn-8xgp1vo-ab5e%2Csn-ab5szn76&ms=au%2Crdu&mv=m&pl=16&ei=hMnlXOOGCobz8gT1xa_YBw&initcwndbps=2060000&mime=video%2Fmp4&gir=yes&clen=17228302&ratebypass=yes&dur=364.135&lmt=1558487606091247&mt=1558563063&fvip=2&c=WEB&txp=5531432&ip=<IP_ADDRESS>&ipbits=0&expire=1558584804&sparams=ip%2Cipbits%2Cexpire%2Cid%2Citag%2Csource%2Crequiressl%2Cmm%2Cmn%2Cms%2Cmv%2Cpl%2Cei%2Cinitcwndbps%2Cmime%2Cgir%2Cclen%2Cratebypass%2Cdur%2Clmt&signature=7575BDEC7939C598BCB9FB4E11726063CCF5DE51.C820C1FAC04F1F2D1CF14D0DEE2BD0E6675A1FA9&key=yt8'
[download] Got server HTTP error: HTTP Error 503: Service Unavailable. Retrying (attempt 1 of 10)...
[download] Got server HTTP error: HTTP Error 503: Service Unavailable. Retrying (attempt 2 of 10)...
[download] Got server HTTP error: HTTP Error 503: Service Unavailable. Retrying (attempt 3 of 10)...
[download] Got server HTTP error: HTTP Error 503: Service Unavailable. Retrying (attempt 4 of 10)...
[download] Got server HTTP error: HTTP Error 503: Service Unavailable. Retrying (attempt 5 of 10)...
[download] Got server HTTP error: HTTP Error 503: Service Unavailable. Retrying (attempt 6 of 10)...
[download] Got server HTTP error: HTTP Error 503: Service Unavailable. Retrying (attempt 7 of 10)...
[download] Got server HTTP error: HTTP Error 503: Service Unavailable. Retrying (attempt 8 of 10)...
[download] Got server HTTP error: HTTP Error 503: Service Unavailable. Retrying (attempt 9 of 10)...
[download] Got server HTTP error: HTTP Error 503: Service Unavailable. Retrying (attempt 10 of 10)...
ERROR: giving up after 10 retries
  File "/home/chirvasitua/.local/bin/youtube-dl", line 10, in <module>
    sys.exit(main())
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/__init__.py", line 474, in main
    _real_main(argv)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/__init__.py", line 464, in _real_main
    retcode = ydl.download(all_urls)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 2008, in download
    url, force_generic_extractor=self.params.get('force_generic_extractor', False))
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 807, in extract_info
    return self.process_ie_result(ie_result, download, extra_info)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 868, in process_ie_result
    extra_info=extra_info)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 807, in extract_info
    return self.process_ie_result(ie_result, download, extra_info)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 1006, in process_ie_result
    extra_info=extra)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 868, in process_ie_result
    extra_info=extra_info)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 807, in extract_info
    return self.process_ie_result(ie_result, download, extra_info)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 861, in process_ie_result
    return self.process_video_result(ie_result, download=download)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 1642, in process_video_result
    self.process_info(new_info)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 1915, in process_info
    success = dl(filename, info_dict)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 1854, in dl
    return fd.download(name, info)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/downloader/common.py", line 364, in download
    return self.real_download(filename, info_dict)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/downloader/http.py", line 353, in real_download
    self.report_error('giving up after %s retries' % retries)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/downloader/common.py", line 165, in report_error
    self.ydl.report_error(*args, **kargs)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 624, in report_error
    self.trouble(error_message, tb)
  File "/home/chirvasitua/.local/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 586, in trouble
    tb_data = traceback.format_list(traceback.extract_stack())

Description

Today (May 22 2019) I started getting HTTP Error 503 messages when trying to download videos from Youtube.
The output pasted above resulted from running
youtube-dl -f 18 -4 -v https://www.youtube.com/user/ReviewTechUSA/videos?disable_polymer=1 --playlist-items 1

Only more recent videos seem to be affected, but I can't quite see the pattern. If, for instance, I run the same command with --playlist-items 4 instead that video downloads fine. Items 1-3 produce HTTP 503 errors though.
Also, I have ssh access to a remote computer on a different network that seems unaffected, which makes me think my IP is somehow being blocked, but apparently only for certain videos.
I am on the latest version as of this writing (2019.5.20) installed directly through pip.

PS > py -2.7 .\youtube_dl\__main__.py Kjvmbtfz56w -f 18
[youtube] Kjvmbtfz56w: Downloading webpage
[youtube] Kjvmbtfz56w: Downloading video info webpage
[download] Destination: Sony Demonstrates The PS5's Load Times, And They're INSANE! #PS5 #PlayStation5-Kjvmbtfz56w.mp4
[download]  24.3% of 16.43MiB at  6.26MiB/s ETA 00:01
ERROR: Interrupted by user


Fix test meta kernal and code to match real spice meta kernels

Codecov Report

Merging #190 (c4ba4c0) into master (8fdcba5) will decrease coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #190      +/-   ##
==========================================
- Coverage   85.63%   85.58%   -0.05%
==========================================
  Files          51       51
  Lines        4413     4413
==========================================
- Hits         3779     3777       -2
- Misses        634      636       +2

Impacted Files
Coverage Δ

stixcore/ephemeris/manager.py
90.51% <100.00%> (ø)

stixcore/config/config.py
96.15% <0.00%> (-3.85%)
:arrow_down:

stixcore/io/soc/manager.py
86.66% <0.00%> (-1.67%)
:arrow_down:

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 8fdcba5...c4ba4c0. Read the comment docs.


Fix missing baseUrl in graphql client for GHE

baseUrl: provider.apiBaseUrl was missing from the graphql client, making it fail miserably against a GHE instance when ingesting users and groups. Also the docs and app-config.yaml sample are wrong on what apiBaseUrl: 'https://ghe.company.com/api/v3' should be used, so this resolves that too.
Very small but potent fix.

@O5ten thanks, this looks good. Could you please add a changeset? Just run yarn changeset and follow the instructions 🙏

@stefanalund patchset added!


large wkt queries

Currently all queries are get queries are therefor reflected in the URL and can be send to other people. There is unfortunately a limit on those. browsers don't support very long urls and if I remember correctly the backend also have a hardcoded limit to how large they can get. @cgendreau didn't we look at this months back?
But large geometries queries is useful. It might be nice if we could support POST for those cases. One way could be to simply start a downloda with a geometry query. So that users didn't have to go to the API, but could use the ui to compose the query and as a last step as a geometry filter that initiated a download.
It wouldn't support previewing results, but at least you could easily download them.

We now have a search api that takes predicates. and the UI offers simplification to support the get params


Shortenening the Legendre Transform over m

This is an issue to collect ideas around the linear vs quadratic vs cubic truncation when looping over the zonal wavenumbers $m$. With #127 we'll do
for m in 1:min(nfreq:mmax+1)

with nfreq  = nlon÷2 + 1 and nlon the number of longitude points at a given latitude ring. So for full grids, the loop goes over all m but for reduced grids this can be shortened. IFS seems to be doing the following (j nlon nfreq) at Tco79
 (   1  20   8) (   2  24  10) (   3  28  12) (   4  32  14) (   5  36  16) (   6  40  18) (   7  44  20) (   8  48  22)
 (   9  52  24) (  10  56  26) (  11  60  27) (  12  64  29) (  13  68  31) (  14  72  33) (  15  76  35) (  16  80  36)
 (  17  84  38) (  18  88  40) (  19  92  41) (  20  96  43) (  21 100  44) (  22 104  46) (  23 108  47) (  24 112  49)
 (  25 116  50) (  26 120  52) (  27 124  53) (  28 128  55) (  29 132  56) (  30 136  57) (  31 140  58) (  32 144  60)
 (  33 148  61) (  34 152  62) (  35 156  63) (  36 160  64) (  37 164  65) (  38 168  67) (  39 172  68) (  40 176  69)
 (  41 180  70) (  42 184  71) (  43 188  72) (  44 192  73) (  45 196  74) (  46 200  75) (  47 204  76) (  48 208  77)
 (  49 212  78) (  50 216  79) (  51 220  79) (  52 224  79) (  53 228  79) (  54 232  79) (  55 236  79) (  56 240  79)
 (  57 244  79) (  58 248  79) (  59 252  79) (  60 256  79) (  61 260  79) (  62 264  79) (  63 268  79) (  64 272  79)
 (  65 276  79) (  66 280  79) (  67 284  79) (  68 288  79) (  69 292  79) (  70 296  79) (  71 300  79) (  72 304  79)
 (  73 308  79) (  74 312  79) (  75 316  79) (  76 320  79) (  77 324  79) (  78 328  79) (  79 332  79) (  80 336  79)
 (  81 336  79) (  82 332  79) (  83 328  79) (  84 324  79) (  85 320  79) (  86 316  79) (  87 312  79) (  88 308  79)
 (  89 304  79) (  90 300  79) (  91 296  79) (  92 292  79) (  93 288  79) (  94 284  79) (  95 280  79) (  96 276  79)
 (  97 272  79) (  98 268  79) (  99 264  79) ( 100 260  79) ( 101 256  79) ( 102 252  79) ( 103 248  79) ( 104 244  79)
 ( 105 240  79) ( 106 236  79) ( 107 232  79) ( 108 228  79) ( 109 224  79) ( 110 220  79) ( 111 216  79) ( 112 212  78)
 ( 113 208  77) ( 114 204  76) ( 115 200  75) ( 116 196  74) ( 117 192  73) ( 118 188  72) ( 119 184  71) ( 120 180  70)
 ( 121 176  69) ( 122 172  68) ( 123 168  67) ( 124 164  65) ( 125 160  64) ( 126 156  63) ( 127 152  62) ( 128 148  61)
 ( 129 144  60) ( 130 140  58) ( 131 136  57) ( 132 132  56) ( 133 128  55) ( 134 124  53) ( 135 120  52) ( 136 116  50)
 ( 137 112  49) ( 138 108  47) ( 139 104  46) ( 140 100  44) ( 141  96  43) ( 142  92  41) ( 143  88  40) ( 144  84  38)
 ( 145  80  36) ( 146  76  35) ( 147  72  33) ( 148  68  31) ( 149  64  29) ( 150  60  27) ( 151  56  26) ( 152  52  24)
 ( 153  48  22) ( 154  44  20) ( 155  40  18) ( 156  36  16) ( 157  32  14) ( 158  28  12) ( 159  24  10) ( 160  20   8)

So that's about 3 fewer m around the poles and less than half at the Equator
julia> cat(ifs[1:80],spd,spd-ifs[1:80],dims=2)
80×3 Matrix{Int64}:
  8   11   3
 10   13   3
 12   15   3
 14   17   3
 16   19   3
 18   21   3
 20   23   3
 22   25   3
 24   27   3
 26   29   3
 27   31   4
 29   33   4
 31   35   4
 33   37   4
 35   39   4
  ⋮
 79  143  64
 79  145  66
 79  147  68
 79  149  70
 79  151  72
 79  153  74
 79  155  76
 79  157  78
 79  159  80
 79  161  82
 79  163  84
 79  165  86
 79  167  88
 79  169  90

and apparently follows the formula nfreq = floor((nlon - 1)/(2 + (1 - mu^2))) - 1 with mu being cos(lat). At that resolution this is per hemisphere 4784 whereas we loop over 7200 so about 50% more. Meaning there's a good amount of performance gain possible if we follow something similar. What needs to be checked though is how much this applies to other grids and whether we can directly formulate this as a function of the truncation order.
More information on this apparently in Courtier and Naughton 1994
@hottad @samhatfield

Because paywalls are 💩, here is the paper:
Quart J Royal Meteoro Soc - July 1994 Part B - Courtier - A pole problem in the reduced Gaussian grid.pdf

Visulation what different truncations would mean. Apparently IFS does something rather quadratic with a cosine scaling towards the poles, which saves 27% of the loops over m. In contrast, we currently use linear which saves 19%. But given the formula higher up, I don't quite get the data to match the formula (ifs, formula above)
  8   8
 10  10
 12  12
 14  13
 16  15
 18  17
 20  19
 22  20
 24  22
 26  24
 27  25
 29  27
 31  28
 33  30
 35  31
 36  33
 38  34
 40  36
 41  37
 43  38
 44  40
 46  41
 47  43
 49  44
 50  45
 52  46
 53  48
 55  49
 56  50
 57  51
 58  53
 60  54
 61  55
 62  56
 63  57
 64  59
 65  60
 67  61
 68  62
 69  63
 70  64
 71  66
 72  67
 73  68
 74  69
 75  70
 76  71
 77  72
 78  73
 79  75
  ⋮
 79  79

@hottad maybe you can clarify, if IFS/ectrans loops until nfreq = floor((nlon - 1)/(2 + coslat^2))) - 1 then towards the equator this is effectively nlon/3, hence quadratic and not cubic. I currently don't understand why you wouldn't want to loop only until nlon/4 at the Equator for a cubic truncation? Visualised this looks like

with IFS being quadratic at the equator but a coslat^2 scaling towards linear near the poles. Could we do something like what I labelled "new", which is also linear near the poles and uses a coslat scaling towards cubic at the equator. That would save another 10% in the Legendre transform compared to IFS.

Hi Milan,
Thank you for this plot!
I honestly do not understand much about this, but I found something interesting about IFS formula.
In addition to zonal aliasing, there is another factor to consider when we determine the size of loop over m.
At latitudes outside of the Tropics, the associated Legendre function decays quickly as m gets larger. Thus, if we define some threshold ϵ below which we can ignore $P_n^m(\sin\rm{lat)}$, we can define m above which we do not need to loop over when performing direct or inverse Legendre transform.
If we call such m as m_to_retain(ϵ), I found that m_to_retain(ϵ) is rather insensitive to the exact choice of ϵ, and interestingly, the IFS formula gives a good approximation to m_to_retain(ϵ).
This is a plot for O80 grid (nlat_half=80) with Nmax=79 truncation (cubic). As we can see, IFS formula and m_to_retain(ϵ=1e-6) agree quite well.

Please have a look at this Jupyter notebook https://gist.github.com/hottad/5536882443cb5d018bbd57a88f10eb0e for precise definitions and derivation (and code).
I do not know if this is related to how IFS formula is devised, but seems like it's a too good agreement for being just a coincidence.

Quick comment: I believe the dip in m_to_retain between 500 and 1700 at T2559 is due to issues with the computation of the Legendre polynomials at very high resolution similar to https://github.com/jmert/AssociatedLegendrePolynomials.jl/issues/27 (which is the package we are currently using to do that).

General comment: I agree that we would need to test these ideas while actually running the model. Daisuke, do you know of a good test case to do that?
In general, I like the m_to_retain idea, but I'm not sold that this is actually what we want: The reason is that a cubic truncation is a form of filtering, so we actually want a certain error if that means we can scale-selectively filter out some high-frequency waves. I believe all of these methods are idempotent, meaning you may start with a field that contains some waves that shouldn't be representable with a cubic truncation, but once they are filtered out the transform should approach exactness (up to rounding errors). In that sense, I see the m_to_retain idea as an upper bound of m beyond which we shouldn't loop, but maybe we do want to shortcut the loop over m even further.
Going forward I suggest we create a parameter like shortcut_legendre::Symbol with options like :linear, :quadratic, :cubic, :ifs, :lincub_coslat which implements exactly these formulas and precomputes them in SpectralTransform. In spectral! we then just load those such that we don't have to play with the spectral transforms just with the precomputation when initiating SpectralTransform.

And I've just created a plot that compares m_to_retain (I went for 1e-4), ifs and new which is the linear to cubic transition via coslat scaling. And I've added the savings in % (total loop iterations over m for all latitude rings) relative to 1:mmax+1 for every ring

Thank you Milan. I agree. m_to_retain should be interpreted as the upper bound of the size of m-loop.
What is not entirely clear to me is if we can ensure orthonormality of $Y_n^m(\rm{lon},\rm{lat})$ if we reduce m beyond m_to_retain.  Perhaps, before trying with model runs, we should start by checking the orthonormality (I mean, if we initialize alm with (l,m)-element having one and all the others zero, and doing a round-trip of transform by successively calling gridded!() and then spectral!(), does that perfectly (within the desired tolerance) restore the original alm, and does this hold for any pair of (l,m)?). I guess this is equivalent to what you call idempotency?

Going forward I suggest we create a parameter like shortcut_legendre::Symbol with options like :linear, :quadratic, :cubic, :ifs, :lincub_coslat which implements exactly these formulas and precomputes them in SpectralTransform.

Thanks. That's a good idea. Will you be able to implement and test this?

Quick comment: I believe the dip in m_to_retain between 500 and 1700 at T2559 is due to issues with the computation of the Legendre polynomials at very high resolution similar to jmert/AssociatedLegendrePolynomials.jl#27 (which is the package we are currently using to do that).

This underflow/overflow problem is a well known issue. Just in case you are not aware, there are two known resolutions to this.
One way to resolve this is to use an exponent-extension method (i.e., represent Pnm with a struct (called X-number) which is a pair of an integer (to save the exponent) and a floating point number (either Float32 or Float64), and override operators like mul(Float,X-number) and add(X-number,X-number) with a bespoke method). Detailed explanation and sample code in Fortran are documented in
Fukushima (2012, Journal of Geodesy) (it's behind paywall but the author's copy on researchgate.net is available from here). It should be easy to implement X-number in Julia as something like Xnum <: AbstractFloat. Experience from Fortran 90 implementation is that, performance penalty from using X-number representation is quite small.
Alternatively, when you compute Pnm by recurrence formula like Belousov, you can check whether Pnm goes beyond/below some thresholds(like 1e-16 and 1e+16 for Float64) and apply scaling by some factors (e.g., 2^20 and 2^(-20), these can be arbitrary but should be power of 2 to avoid rounding error) if that occurs,  and keep track of how many time the scaling was applied for each Pnm. This is what is done for IFS or JMA's global model. Wedi et al. (2013), Section 2, very briefly mentions this strategy in IFS:

Equation (9) is also unstable but can be made stable by tracking the values of the numbers and keeping them within an acceptable range that can be represented with double precision

The first approach Daisuke suggests can already be easily done with AssociatedLegendrePolynomials.jl as it's type-flexible but currently quadmath arithmetics like Float128 aren't fast.
julia> using AssociatedLegendrePolynomials, Quadmath, BenchmarkTools
julia> Λ = zeros(Float32,3001,3001)    # always store in a Float32 array
julia> @btime λlm!(Λ, 3000, 3000, Float32(cos(π/4)));    # the type of cos(colat) determines the format used for calculation
  18.604 ms (5 allocations: 80 bytes)
julia> @btime λlm!(Λ, 3000, 3000, Float64(cos(π/4)));
  22.545 ms (5 allocations: 80 bytes)
julia> @btime λlm!(Λ, 3000, 3000, Float128(cos(π/4)));
  6.238 s (6 allocations: 192 bytes)

Although I have quite some expertise in writing new number formats, I'm not particularly keen to implement an X-number myself. On the other hand, how hard can it be? 😆 Good thing in Julia is, you don't have to overload the arithmetics.
The 2nd approach would require some tweaks to AssociatedLegendrePolynomials, @jmert you may find this interesting.


Notes on Debug GUI using dat.gui

This is a quick explanation on how I implemented the debug controls with dat.gui.
First thing first though, the gui is instantiated and configured by this setup method here:
https://github.com/CyberCRI/welearn-map/blob/5cd38f1fa737f9fcfb23472bc47c3119cc508d5e/src/renderer.js#L169
Remove that, or make it parametric to disable the gui.
To tweak the gui, this is the place to do it:
https://github.com/CyberCRI/welearn-map/blob/5cd38f1fa737f9fcfb23472bc47c3119cc508d5e/src/renderer-debugger.js#L21

Now on to how it actually changes the dotatlas parameters,
https://github.com/CyberCRI/welearn-map/blob/5cd38f1fa737f9fcfb23472bc47c3119cc508d5e/src/renderer-debugger.js#L30-L38
Notice that we are passing the dotatlas object here in the callbacks.
It's a bit convuluted, hence here is the old version from learn-ext repo which hopefully demonstrates the loops we have now:
  const ctrlPan = ui.addFolder('Panning Controls')

  // Setup panning controls:
  ctrlPan
    .add(stateSet.panning, 'x', -20, 20, 1)
    .onChange(mapTransformSetter)
  ctrlPan
    .add(stateSet.panning, 'y', -20, 20, 1)
    .onChange(mapTransformSetter)
  ctrlPan
    .add(stateSet.panning, 'scale', 0, 10, .1)
    .onChange(mapTransformSetter)

source

If I delete or parametrize this : const debugUi = setupDebugger(atlas, layers, conf.element)
This is what I get :


Small Typo in 'find the right code to change' webpage

I think updateUserPreferencesDataAsync should be updatePreferencesDataAsync.

Thanks @won369369! This is fixed.


Really missing "Find the right operator" flow in new site. Need to reference it to the old site without redirect.

Documentation Related To Component:
Please check those that apply

[ ] typo
[ x ] documentation doesn't exist, but it used to be there
[ ] documentation needs clarification
[ ] error(s) in example
[ ] needs example

Description Of The Issue
Old site had an extremely useful flow for "Find the right operator". Unfortunately it used to leave at the root of http://reactivex.io/rxjs/ which now redirects to the new site, that doesn't have this flow.
This was one of the most important ways to discover operators for RxJS beginners.
@benlesh can it temporarily moved to some path at the old site that doesn't redirect? Alternatively, is there a cookie/localStorage/queryparam flag I can set to not redirect? Queryparam would actually be ideal, since I can just provide the link to it.
Thanks!

@alex-okrushko Did you mean http://reactivex.io/rxjs/manual/index.html ?

Exactly what @cartant pointed to. And also HUGE +1 for a more visible and easily linkable spot. My typical instructions for the old doc very "open http://reactivex.io/rxjs/ and scroll all the way to the bottom".