Update the machine controller image to pick up #644

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes: clusters started on GCP would be unable to create nodes using the machine controller.
Special notes for your reviewer:
Release note:

NONE

@kubernetes/kube-deploy-reviewers

/lgtm


ZERO Hydra Failures 20.03

ZERO Hydra Failures 20.03
Mission
Every time we branch off a release we stabilize the release branch.
Our goal here is to get as little as possible jobs failing on the release-20.03 jobset.
I'd like to heighten, while it's great to focus on zero as our goal, it's essentially to
have all deliverables that worked in the previous release work here also.
How many failing jobs are there?
At the opening of this issue we have the main jobset at 1204 failing jobs, x86_64-darwin at 1384, and aarch64-linux at 7482.
The first evaluation of 19.09 had 1654 failing jobs.
So we're actually starting off with slightly less failing jobs compared to the last release.
How to help

Select an evaluation of the release-20.03 jobset by #id

Find a failed job ❌

Work out why it's failing and fix it

Pull Request the fix

Generally the job fails on master also, you can verify that on Hydra - example URL: https://hydra.nixos.org/job/nixpkgs/trunk/bash.x86_64-linux.
That means most PR's should be targeted on master or staging for mass rebuilding changes.
Always reference this issue in the body of your PR:
ZHF: #80379

Backport it to release-20.03 or staging-20.03.

Details on that are in CONTRIBUTING
Packages that don't get fixed
The remaining packages will be marked as broken before the release (on the failing platforms).
You can do this like:
meta = {
  # ref to issue/explanation
  # `true` is for everything
  broken = stdenv.isDarwin
};

These are the utility flags used to test the type of platform.
Closing
This is a great way to help NixOS, and it was some of my earliest contributions.
Let's go ✌
✨ worldofpeace
cc @NixOS/nixpkgs-committers @NixOS/nixpkgs-maintainers

IT BEGINS!!!!

This was actually delayed by https://github.com/NixOS/nixpkgs/issues/79907, but we just got this sorted.
Many thanks to everyone who fixed it :sparkles:

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nixos-20-03-beta/5935/1

It looks like all nixosTests on i686 are failing because of a test in python aiohttp: https://hydra.nixos.org/build/112800138/nixlog/390/tail.
The problem is
>> int(4575744000.0).bit_lenght()
33

which can't be represented on i686 time_t.
Should be silence the test on 32bit platforms?

@rnhmjoj They already disable some tests on that platform https://github.com/aio-libs/aiohttp/pull/4021/files#diff-484462fced51d1a06b1d93b4a44dd535R34, sounds good.

Even better, patch it to disable only the failing tests.

Can I just say that this is an awesome ZHF description, with lots of valuable info in it.
Awesome job @worldofpeace! 👏

Can I just say that this is an awesome ZHF description, with lots of valuable info in it.
Great job @worldofpeace! clap

Thank you :blush: I tried to include all the useful information from my predecessors and my own stylized information.

Awesome! Anyone know if there's a way to show failing builds by maintainer? Also, if I want to test my config, should I use https://github.com/NixOS/nixpkgs/tree/20.03-beta?
Thanks for the great work!

@tbenst Here's a simple expression you can put in your nixpkgs checkout (say mypkgs.nix), which you can then nix-build mypkgs.nix to build all top-level packages with you as a maintainer (adjust the maintainer there to yourself):
{ pkgs ? import ./. {}
, maintainer ? "infinisil"
}: with pkgs.lib;
filterAttrs (name: value:
 (builtins.tryEval value).success &&
 elem maintainers.${maintainer} (value.meta.maintainers or [])
) pkgs

Or nix-build mypkgs.nix -A <TAB> to see and build individual ones

Also, if I want to test my config, should I use https://github.com/NixOS/nixpkgs/tree/20.03-beta?

No, that's the tag, you want to use the release-20.03 branch. But I would wait a few days because I'm not sure everything is built.

I have this extremely primitive script:
#!/usr/bin/env bash
# Simple script to check nix attrs for build status on Hydra
while [ -n "$1" ]; do
    nixos_url="https://hydra.nixos.org/job/nixos/release-20.03/nixpkgs.$1.x86_64-linux"
    master_url="https://hydra.nixos.org/job/nixpkgs/trunk/$1.x86_64-linux"
    # NixOS and unstable master channels have slightly different syntax; swap here depending on what we want
    #url="$master_url"
    url="$nixos_url"
    channel=$(echo "$url" | sed 's|.*/job/||' | sed 's|/.*||')

    printf "Last status of $1 on $channel = "
    res=$(curl -s "$url"  | rg -o 'title="[A-Za-z]+"' | sed 's|title=||' | sed 's|"||g' | head -1)
    echo "$res"

    if [ "$res" = "Failed" ]; then
        xdg-open "$url" >/dev/null 2&>1
    fi

    shift
done

which can then be called like this:
$ hydra python37Packages.numpy dnnl s4cmd
Last status of python37Packages.numpy on nixos = Succeeded
Last status of dnnl on nixos = Succeeded
Last status of s4cmd on nixos = Succeeded

It'll open the Hydra page in your web browser for details if there's a failure.
I've been chaining it together with ripgrep, but I think chaining together with a nix expression similar to @Infinisil's could result in something more robust.
I've also noticed Hydra is responding very slowly to page loads, so I'm wondering if there's a faster/better way to hit it; I'm not calling in high volume, but please wait for someone who knows more to chime in before you hammer the server with a huge load.  It's possible Hydra's REST API has something better here than curl'ing and grepping the status page.
https://nixos.org/hydra/manual/#chap-api

@tbenst Here's a simple expression you can put in your nixpkgs checkout (say mypkgs.nix), which you can then nix-build mypkgs.nix to build all top-level packages with you as a maintainer (adjust the maintainer there to yourself):
{ pkgs ? import ./. {}
, maintainer ? "infinisil"
}: with pkgs.lib;
filterAttrs (name: value:
 (builtins.tryEval value).success &&
 elem maintainers.${maintainer} (value.meta.maintainers or [])
) pkgs

Or nix-build mypkgs.nix -A <TAB> to see and build individual ones

note that this will only do the top-level packages defined in all-packages. if you're concerned about other language frameworks, you will need to merge those attrs as well

#80388 worked, now it's a pytest-timeout test that's causingt the failures: https://hydra.nixos.org/build/113080554/nixlog/46/tail
I'm not sure what's up here.

I ran a script to determine which packages cause the most transitive failures:
[('zjl4pbwar26kn4h1vffldazh3n1ns2fj-python3.7-pytest-timeout-1.3.3', 333),
 ('g4lj2f02pqj87vfmy2sypc7k7g8k14sv-python2.7-decorator-4.4.1', 154),
 ('8627r1m36krk4767l4vv5ljhf4j6n2xw-python3.8-fsspec-0.6.2', 22),
 ('7f18w1x5v2i17n4g2zzzg27br3k9sv11-ghostscript-9.50', 17),
 ('767sn47ai3q0vvwg1wm10pzmgy11hr64-kodi-18.5', 10),
 ('y5k2ff3y45cv0av9prylff4rzhm5mxn0-tensorflow-1.15.0', 9),
 ('h5588ngz0n72cmcwn5qjfixp12xx0drw-tensorflow-1.15.0', 8),
 ('0rz02m46032dzvqwhc9kmz381v4176cq-hscolour-1.24.4', 6),
 ('jcbmmjbp6ank5xkx9wdmrzcrjv681mlh-python3.7-pysam-0.15.3', 5),
 ('xvw3lmkp5lpba8rq0la92cc45pccm60m-torch-5.1', 5)]

Indeed, pytest-timeout, as @rnhmjoj already noticed, and also decorator. After that, it falls of quickly.

@Synthetica9: you can use this tool to generate a report on problematic dependencies: eval-report.

https://hydra.nixos.org/build/113063456#tabs-summary - needs cherry pick of e24c04f278e7b13ec4edbcfcadec55e33b42c1de into release-20.03.

I spent a bit of time on google-cloud-storage but didn't figure out how to fix correctly. AFAICT the issue is down to google-cloud-* using pth files. The module seems to work fine when used in a normal, symlinked virtualenv:
NIX_PATH=nixpkgs=$pwd nix-shell -p 'python3.withPackages (x: [x.google_cloud_storage])' --command "python -c 'import google.cloud.storage'"

But doesn't work when running tests which set  PYTHONPATH instead of a symlink tree. The quick option for 20.03 would be to disable tests, the longer term solution to me seems to test in the same environment as is used later (i.e. python3.withPackages).

IIRC @teh, the google python packages have a .pth namespace, which doesn't work well with nix. For the azure-* packages, i essentially had to force PEP420 compliance in #71797

the quick option wont work, if someone has protobuf and google_api_core in their environment, they will only be able to pick up one of those files, but not both. This is instance that the unit tests demonstrate the package is in a defunct state. For ZHF, I would just disable.

#53854 fixes some builds, but it seems to have been ignored. I tested it a couple months ago for the previous ZHF and it still fixed the builds. This package has been broken for a long time and it would be good to finally get it fixed.

If it fails in the checkPhase we could export PYTHONPATH as NIX_PYTHONPATH.
On Tue, 18 Feb 2020, 22:08 Jon<EMAIL_ADDRESS>wrote:

the quick option wont work, if someone has protobuf and google_api_core
in their environment, they will only be able to pick up one of those files,
but not both. This is instance that the unit tests demonstrate the package
is in a defunct state. For ZHF, I would just disable.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/80379?email_source=notifications&email_token=AAQHZ32DHHUT4CZDCEO55D3RDRE6JA5CNFSM4KWZNMRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEME6HAY#issuecomment-587850627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQHZ36KGL6LEE45US2NG23RDRE6JANCNFSM4KWZNMRA
.

Replying to @bhipple 's script:

url="https://hydra.nixos.org/job/nixos/release-20.03/nixpkgs.$1.x86_64-linux"
    printf "Last status of $1 = "
    res=$(curl -s "$url"  | rg -o 'title="[A-Za-z]+"' | sed 's|title=||' | sed 's|"||g' | head -1)
    echo "$res"

Try instead:
curl -s -L 'http://hydra.nixos.org/api/latestbuilds?nr=1&project=nixos&jobset=release-20.03&job-nixpkgs.dnnl.x86_64-linux' | jq .[0].buildstatus

This should be a lighter-weight query, although the buildstatus is numeric.  0 = success, anything else probably warrants looking into.

@jonringer I started work on pep420 compliance here. It's a non-trivial amount of work and I'm not sure I can complete for 20.03.

re https://hydra.nixos.org/build/113055208 nixos:release-20.03:nixos.tests.docker-tools.x86_64-linux
I've checked the nixos/tests/docker-tools.nix and it works ok locally. On hydra, it has the status Aborted: cannot connect to<EMAIL_ADDRESS>ssh: connect to host edcd58f5.packethost.net port 22: Connection timed out , so, I guess it's some timeout, but not sure where to look for it...

@teh given we're past feature freeze, I would suggest we don't include it in 20.03.

@Frostman: I see it failing repeatedly on Hydra for some other reason: https://hydra.nixos.org/build/113288778#tabs-buildsteps

Do you have any idea on why hydra reports a failure here but there is nothing indicating one occured in the log: https://hydra.nixos.org/build/113082114/nixlog/1/tail?

Hmm, I'd say the log doesn't seem complete.  I'm not sure.
If it did seem complete, I'd say this typically happens when a dependency of a build first fails but later someone restarts it (from a different depending build).  As logs are stored per *.drv and get over-written, so then you may see an old failure with a link to a log from a succeeding build.

Well, I'm clueless. I went as far as building a 32bit VM to build and run the tests and couldn't reproduce the failures. I can even get the pytest-timeout package from the binary cache now but hydra somehow still fails.

Looking at it now, it probably was complete, so I expect my second paragraph holds.

@teh I'm going to agree with @disassembler what I said https://github.com/NixOS/nixpkgs/issues/80379#issuecomment-587850627. For ZHF, I would just disable the broken google packages. IIRC, they were mostly broken for the 19.09 release, so it's not much of a regression for them to be broken in the upcoming release.
It's still worthwhile work if you have a use case for the packages. My use case was bringing azure-cli back to nixpkgs. Not sure if google has a similar cli utility for their cloud.

pytest-timeout test suite seems flaky, for similar reasons to https://github.com/NixOS/nixpkgs/pull/80512. It may be tricky to fix its test suite however.

pytest-timeout is a real Python module, we shouldn't modify it to behave differently. However, I don't think Nixpkgs tests should depend on it.

In fact, I looked at aiohttp, one of packages that depends on pytest-timeout. Turns out this requirement was deleted: https://github.com/aio-libs/aiohttp/commit/00f5c40533b3095c31c6502bdea0e0d46a08fec7

Those google packages are needed by apache-airflow too.
Perhaps there is enough of us to get at least one version in good shape for
this release?
On Thu, 20 Feb 2020 at 8:22 AM Konrad Borowski<EMAIL_ADDRESS>wrote:

In fact, I looked at aiohttp, one of packages that depends on
pytest-timeout. Turns out this requirement was deleted: aio-libs/aiohttp@
00f5c40
https://github.com/aio-libs/aiohttp/commit/00f5c40533b3095c31c6502bdea0e0d46a08fec7
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/80379?email_source=notifications&email_token=AAANNV6SQ6WRAG2WHBQHTETRDZ7YVA5CNFSM4KWZNMRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMN3VRY#issuecomment-589019847,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAANNV5EGRQKTIIOFJ7BN63RDZ7YVANCNFSM4KWZNMRA
.

xfix was faster, but I have tested :)

Merge whatever in terms of tigervnc, those commits are identical as they are cherrypicks from master.

@xflx for flakey python tests, just disable them pytest -k 'not some_test_which_is_flakey' unittests are still a good sanity check to ensure the package has compatible dependencies and is working as expected.

Because https://hydra.nixos.org/build/112812334 is failing can https://github.com/NixOS/nixpkgs/pull/59414 be cherry-picked into the release?

@hlolli if you want to see change happen, you're fully enabled to create a PR targeting the release-20.03 branch, and fix the packages you're invested in

@jonringer ok thanks, I got confused from all the cherry-picks from NeQuissimus https://github.com/NixOS/nixpkgs/commits/release-20.03 that it had to go trough them. Sorry for the noise, I guess hundreds of people will get notification :1st_place_medal:

it's all good, one team.
just remember to follow the directions from @worldofpeace , cherry-picks should include the -x switch which will reference the commit it was taken from.

I've updated the OP to include, please ping the @NixOS/nixos-release-managers team for ports to 20.03.

Look!

Eval 1571405 report

@worldofpeace did you only want the release-managers doing backports? or is acceptable if they follow the cherry-picking and other guidelines for other to merge ports?

No, it would be impossible for either of us to perform that many backports.
I think the release managers should be notified about them, and review them.
If a change is for ZHF it has to be backported, and the author should PR that too (why the how to help doesn't stop at step 4) Committers are trusted to integrate backports correctly.

There's a whole bunch of aarch64 packages failing because the 20.03 qtwebengine.aarch64-linux build timed out: https://hydra.nixos.org/build/113000788 Is there a way to rerun it / give it more time in future?

Eval 1572343 report

I'm not sure why the abortions; I restarted them.
IIRC our Firefox is doomed for the regular i686 build, as some build steps will probably never fit into 4G address space anymore.  I don't expect there will be enough motivation to somehow solve this in nixpkgs; perhaps we should just mark that variant as broken.

On 02:54 25.02.20, Vladimír Čunát wrote:

IIRC our Firefox is doomed for the regular i686 build, as some build
steps will probably never fit into 4G address space anymore.  I don't
expect there will be enough motivation to somehow solve this in
nixpkgs; perhaps we should just mark that variant as broken.

Agreed. They have been very unreliable for the last few years and there
is really no hope left that they can be compiled on i686 (without
significant investment).

Here there's something strange: the build failure is propagating from a successful build.

IIRC our Firefox is doomed for the regular i686 build, as some build steps will probably never fit into 4G address space anymore. I don't expect there will be enough motivation to somehow solve this in nixpkgs; perhaps we should just mark that variant as broken.

Can't it be cross-compiled? Or am I misunderstanding the issue?

the build failure is propagating from a successful build

You can see it in the "build steps" tab that first attempt failed (and thus killed depending jobs) and then someone must have restarted it.  I now restarted also the build you linked.

 Generally looks good! Pytorch builds for example.
Tensorflow does not, which is known.  Generally looks good! Pytorch builds for example.

That is one of the best news I've heard for z while, amazing job !

Edit: oh wait I think I misunderstood, do you mean that Pytorch with CUDA on Hydra is not a thing? :/

cuda is nonfree. Hydra is not able to "redistribute" it without potential license infringements. It's an Nvidia thing, not a hydra thing.

cuda is nonfree. Hydra is not able to "redistribute" it without potential license infringements.

Can we build on Hydra to get one bit output: success or failure and provide build logs in case of failure without potential license infringements?
I mean, if we build as free packages, but only .nar direct link will return "error 451"?

I think this discussion thread should stick to ZHF, cuda discussion can be done in a separate thread.
my final words on the matter:

Can we build on Hydra to get one bit output: success or failure and provide build logs in case of failure without potential license infringements?

seems like a lot of compute resources just to get a thumbs up or down, and doesn't really change the fact that the consumer would still have to build it locally.

I mean, if we build as free packages, but only .nar direct link will return "error 451"?

I don't work on the nixos infrastructure, but my immediate gut reaction is that this would introduce another dimension of "technical debt" to how the caching mechanism works, with little to no benefit to users.

@GuillaumeDesforges @conferno right, this is not an "official" NixOS hydra server but one I'm privately hosting that currently builds against MKL & CUDA but does not yet distribute cache. May switch to Nix-Community infra in near future. Hydra itself can use CUDA, it's just that hydra.nixos.org won't. Better to discuss here: https://discourse.nixos.org/t/re-improving-nixos-data-science-infrastructure-ci-for-mkl-cuda/

Kicad is failing, but it seems to work on my machine. I think it's because it tries to pull in the 3D models for components, which is 4.88 GiB on my machine.
Also, I have #81030 #81038 and #81042 that are I think ready to be merged -- apologies if it's bad manners to bump PR this way.

Also, I have #81030 #81038 and #81042 that are I think ready to be merged -- apologies if it's bad manners to bump PR this way.

Oh no problem. That is exactly what this thread is for :+1:

Also, I have #81030 #81038 and #81042 that are I think ready to be merged -- apologies if it's bad manners to bump PR this way.

Oh no problem. That is exactly what this thread is for 👍

On that note, I will cherry pick https://github.com/NixOS/nixpkgs/pull/81035 and https://github.com/NixOS/nixpkgs/pull/81033 once approved which should fix ~20 builds dependent on tensorflow.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nixos-20-03-beta/5935/20

Please restore varnishPackages.geoip
It was in 19.09 but accidentally removed in 20.03 (https://github.com/NixOS/nixpkgs/issues/81524).

This fixes a regression in 20.03 (ebtables command renamed with no replacement).
https://github.com/NixOS/nixpkgs/pull/81545

Is there a reason why ZHF build are performed with config.allowAliases = true ?
It result in successful build of packages which would be failed otherwise (https://github.com/NixOS/nixpkgs/pull/81585 https://github.com/NixOS/nixpkgs/pull/81584)

tree-sitter should be fixed now after backporting the update to 0.16.4 in 57fafc08f95e2519dce88a259761d7af69e5b519.

Not sure if it's a big deal or not, but on 19.09 upower "just works"; on 20.03 it will segfault unless services.upower.enable = true.  I think this is a result of https://github.com/NixOS/nixpkgs/pull/73968, but haven't bisected it to verify.
Doesn't necessarily seem like a problem (?), but perhaps worth calling out in the release notes more explicitly.

I tried removing /etc/UPower/UPower.conf but the service still does not crash, only a warning is logged. Could you obtain a backtrace and open a new issue?

Opened https://github.com/NixOS/nixpkgs/issues/82529. We can take the thread over there, but let me know if it segfaults for you when you haven't explicitly enabled the upower service in NixOS.

(Tagging ZHF in that last PR of mine was a mistake: the broken version of openblas (0.3.8) is currently only in master)

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/i-want-to-help-out-easy-to-fix-issues/6334/2

Backported #80756 as 50de0ac5541b02abbf1a46962da04d727efae3b3. This fixes at least the MySQL support for bitwarden_rs (https://hydra.nixos.org/build/115532261).

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/go-no-go-meeting-nixos-20-03-markhor/6495/5

@bhipple i've written a similar tool called hydra-check which provides similar features (with a bit more sugar around), check out https://github.com/nix-community/hydra-check

FYI hydra-unstable broke quite recently due to API changes in nixUnstable. This is fixed in #84501.

The haskell infrastructure seems to be in sad state for aarch64: the compiler doesn't build, so all haskell packages fail on AArch64: https://hydra.nixos.org/eval/1580715?filter=compiler.ghc&compare=1580586&full=#tabs-still-fail

Needs a backport of https://github.com/NixOS/nixpkgs/pull/80355

https://github.com/NixOS/nixpkgs/pull/84738
https://github.com/NixOS/nixpkgs/pull/84648

Putting my GHC hat on, I would strongly recommend that people use at leaat GHC 8.8.2 on AArch64. Previous releases had some pretty awful bugs on architctures with weak memory models.

With the compiler not even building we're quite safe from such bugs ;-)
Well, on 20.03 I see the default ghc is 8.6.5 (doesn't differ by platform AFAIK).  Master has 8.8.3 now.  Perhaps we can conservatively backport the default upgrade only on some platforms, but I don't know...

I don't think it's a good idea to have a different version depending on a platform, especially when the version difference in question introduces new features.

Yes, but last-minute switch of the main platform to 8.8 didn't sound very nice to me either :shrug:

It seems we had a huge regression (+8300 package failures) three days ago; is that just the GHC stuff?
https://hydra.nixos.org/jobset/nixos/release-20.03

I did just declare 20.03 as a GO https://discourse.nixos.org/t/go-no-go-meeting-nixos-20-03-markhor/6495/23.
So are those regressions just haskell stuff on aarch64?
I also believe hydra was having a hard time for a few days, currently trying to get stuff to not timeout :frowning:

That may be because we got aarch64 working for GHC.

It looks like something went wrong with the x86_64 llvm build: click in the propagated build failure in https://hydra.nixos.org/build/116359963, which actually links to a successful build? Does that mean the build was restarted?

It looks like something went wrong with the x86_64 llvm build: click on the propagated build failure in https://hydra.nixos.org/build/116359963, which actually links to a successful build? Does that mean the build was restarted?

Yes, I restarted it.

We currently are at the stage of marking packages as broken on master and 20.03 https://github.com/NixOS/nixpkgs/issues/83805 https://github.com/NixOS/nixpkgs/pull/85331 https://github.com/NixOS/nixpkgs/pull/85417. By marking the remaining failing packages as broken that would achieve "reach as close to zero". This will likely cause a situation where maintainers will notice their packages are broken. I consider that the final stage of ZHF for 20.03, thank you everyone. Also know that during 20.03 lifespan you can fix broken packages, and I'd encourage you to please do so if your package has been marked as broken.
Committers, if there's open PRs that conflict with marking as broken please integrate them after things have been marked.
I'm going to another small round of marking after https://github.com/NixOS/nixpkgs/issues/83805 is evaluated by hydra. With that task finished this thread will be closed.

@worldofpeace What notification will one get if one's package is marked as broken?

@expipiplus1, if you're part of the nixpkgs-maintainers team (intentionally not @ mentioned), you get notifications from ofborg when PRs are opened for a package if you're in meta.maintainers. I'm not sure that's true if the commits don't pass through a PR though.

It seems worthwhile to investigate why mitmproxy is broken on release-20.03. This does not seem related to mitmproxy per se, it may be related to python, or openssl, or its dependencies.

@orivej It looks like an openssl update broke the test, at least that's what I get bisecting: 0e5ef8c4709e44dfdf22f742c1ebf92d2420e1cf

The real problem is mitmproxy in 20.03 is one major release behind.

Do you mean cryptography rather than mitmproxy?

Do you mean cryptography rather than mitmproxy?

No, I really meant mitmproxy, which is at 4.0.4, latest is 5.1.1. cryptography is only slightly outdate: 2.8, latest 2.9.
I'm trying to build 5.1.1 right now, if I manage to get it working without changing too many dependencies I could port it to 20.03, otherwise I'll just add yet another patch.

Aha, OK, it is not broken on master since it has not yet updated OpenSSL from 1.1.1d to 1.1.1f.

I've fixed mitmproxy in 20.03 with 2e08e8cb260.  The update to 5.1.1 requires a bump of cryptography, which is probably better not to backport, see #85458.

@disassembler  Why was python3Packages.svgwrite marked as broken in c6be4c19578ecd8ac8211b753640f3693d00c8d9 ? It seems to build fine, and Python can import the resulting package.

If anyone has a package that is wrongly marked as broken or can be fixed, please open a PR.
There's no way us as RMs are going to be able to follow that after the fact, it's just not possible.

20.03 is out https://discourse.nixos.org/t/nixos-20-03-release/6785.
Thanks to everyone who helped with 20.03. We accept backports into the stable release during its lifetime, bugfixes and security updates. Minor updates also. If certain exceptions are needed we can work with it. :wave:

I just want to thank @worldofpeace @disassembler and many others for the work they put forward to make this release happen. It makes me happy to see how much the nix community desires to see NixOS be successful :).
May NixOS be the way of the future :)


How to delete other user's message in Moderated Group chat?

Hi, I tested in current version of Skype Web. In a Moderated Group Chat, admins are able to delete messages of other users. Can I achieve the same in using this library?

Have you tried SkypeMsg.delete()?

Have you tried SkypeMsg.delete()?
Now it works.


[Bug] copy is not successful NotAllowedError: Disabled in this document by Feature Policy.

What happened?
Copying by Flutter code is not allowed in Dartpad.
Flutter code
Clipboard.setData(ClipboardData(text: someString))
Browser
Browser: Chrome 84
Machine
Operating system: WIN10
Dartpad 1.20
DartPad's output
copy is not successful NotAllowedError: Disabled in this document by Feature Policy.

Seems to be related to https://github.com/w3c/webappsec-permissions-policy/issues/322
Proposal / fix
Set Dartpad's iframe with copy / paste policy.

The iframe we run the flutter code inside is sandboxed for security concerns. I'm curious what use cases we are blocking by not granting this iframe copy/paste permissions.

@domesticmouse
ad use case: Dartpad is great for micro-prototyping (i.e. prototype of one screen). In my case certain complicated string on the screen can be copied on button press into the clipboard with the SnackBar confirming that the text is in the clipboard.
There was a lot of confusion, why it does not work on DartPad. And expectation that DartPad would behave the same as if the Flutter code was published onto web.

Fair point. I'll leave this issue open to see if we get any additional support for the request.
So far, our guiding principle has been security first, but if there's consensus that this would help a number of devs, we can look at implementing it.

A have a use case of interactive adjusting TextStyle Shadow arguments with the help of Sliders and SelectableText widget to copy the outcoming code to the clipboard. It would be nice to have the ability to copy the resulting text by pressing a button, but it's not possible due to the permissions policy.


feat: Dask multiple partitions

What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[x] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[ ] ✅ Test
[ ] 🐳 Other

Related issues

Closes #872

Checklist

[x] Code follows style guide (ruff)
[x] Tests added
[x] Documented the changes

If you have comments or can explain your changes, please do so below.

CI Failure is due to a polars==0.20.31 deprecation warning


Cannot make Quarto work in VS Code

Comment:
Hi, I'm a new Conda and Quarto user.
During the last three weeks, I've been learning and testing how to use R in a Conda environment. Now I'm stuck with Quarto because I cannot make it work in VS Code. There's an issue between environments and paths.
I'll do my best to document everything I've done.

Install the R and Quarto extensions.

On the terminal, the base environment is activated: (base) vasily@vasily:~/quarto-gallery$ .
If I run quarto check, I get an error:
/home/vasily/miniconda3/envs/r-4.3/bin/quarto: line 158: /home/vasily/miniconda3/envs/r-4.3/bin/tools/deno-x86_64-
unknown-linux-gnu/deno: No such file or directory

Activate the R environment again, conda activate r-4.3. Quarto works:

[✓] Checking versions of quarto binary dependencies...
    Pandoc version 3.1.1: OK
    Dart Sass version 1.58.3: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
    Version: 1.3.450
    Path: /home/vasily/miniconda3/envs/r-4.3/bin

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
    Version: 3.12.0 (Conda)
    Path: /home/vasily/miniconda3/envs/r-4.3/bin/python
    Jupyter: 5.5.0
    Kernels: ir, python3

(|) Checking Jupyter engine render....0.00s - Debugger warning: It seems that frozen modules are being used, which may
0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off
0.00s - to python to disable frozen modules.
0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation.
0.00s - Debugger warning: It seems that frozen modules are being used, which may
0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off
0.00s - to python to disable frozen modules.
0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation.
[✓] Checking Jupyter engine render....OK

[✓] Checking R installation...........OK
    Version: 4.3.2
    Path: /home/vasily/miniconda3/envs/r-4.3/lib/R
    LibPaths:
    - /home/vasily/miniconda3/envs/r-4.3/lib/R/library
    knitr: 1.45
    rmarkdown: 2.25

[✓] Checking Knitr engine render......OK

Open tufte.qmd and render it by clicking on Preview or pressing CTRL+SHIFT+K. A new terminal with the base environment opens up displaying the error of step 6.

I get a partial success by running quarto render tufte.qmd:

But I receive 'No TeX installation was detected', although r-tinytex is on the environment.

Questions

What is happening?
How can this be solved?

Thank you for reporting this issue! It looks like your environment might not be activated since I see (base) in your prompt, but your environment is named r-4.3. Please try activating the environment from within VSCode terminal.
If that doesn't work:
The symptoms look a lot like #30 . Do you know what shell you're using within the VSCode terminal?
I think the result will be empty, but can you please do env | grep QUARTO_ to see if the required environment variables are set? Also please run which quarto to see which installation of Quarto will be executed and report the results.
Thanks and good luck!

Hi @mfisher87,
I was writing an update when you responded. I've spent the last 5 hours digging information about why VS Code doesn't take the R environment that I activated in step 1. Although I don't have a definitive answer, I've learnt that there are on-going issues with how VS Code manages Conda environments. I've tried changing about a dozen parameters on the Open User Settings without success. For example, I had terminal.integrated.inheritEnv enabled by default. I've disabled it and don't see any changes.
Both the Ubuntu and the VS Code terminals are Bash, specifically version 5.1.16(1).
Then, I found about about Conda's auto_activate_base parameter. Apparently, what happens in step 6 is that Bash is reinitialised, so the base environment is activated by default. I did the following:

Run conda config --set auto_activate_base false.
Refresh the Bash shell: source ~/.bashrc. The (base) prompt disappears.
Open VS Code: code .

Now, it looks like this:

Sadly, I don't see on the terminal that I have a Conda environment activated. Do you know if there's a better way to configure this?
Lastly, what should I do about TinyTeX? Install it with quarto install tinytex?

I've learnt that there are on-going issues with how VS Code manages Conda environments.

I've used VSCode very rarely for the Live Share functionality, and always found it a bit uncomfortable in this regard. I like to use a lighter editor :) I wish I could offer more help in that space! I would recommend trying doing your editing in VSCode and doing your Quarto commands in a plain terminal and see if you still have any issues. If this issue is purely caused by VSCode, I don't think I can offer much.

Both the Ubuntu and the VS Code terminals are Bash, specifically version 5.1.16(1).

:heavy_check_mark: thanks for verifying! I think you probably won't experience this issue outside of VSCode based on this.

1. Run `conda config --set auto_activate_base false`.

2. Refresh the Bash shell: `source ~/.bashrc`. The `(base)` prompt disappears.

3. Activate the R environment: `conda activate r-4.3`

4. Open VS Code: `code .`

I am so ignorant about VSCode but I think it does a lot of heavy environment set up stuff under the hood, and expecting it to pick up your pre-activated environment and use it may be incorrect. I would try activating the environment within the VSCode terminal, or if you need the environment for language server / IDE features, try use the VSCode project settings to tell it the appropriate environment for your project. You may need to point to the path of your conda environment which you got from which quarto above: ~/miniconda3/envs/r-4.3
I think... this is all best-guess :)

Sadly, I don't see on the terminal that I have a Conda environment activated. Do you know if there's a better way to configure this?

It looks to me like at this point everything is working except your terminal prompt isn't properly displaying the active environment? We can see from conda env list that it is active and Quarto is correctly found. I think you may want to re-enable auto_activate_base to fix the display, but I'm not sure. Could be VSCode doing something weird to the env again.

Lastly, what should I do about TinyTeX? Install it with quarto install tinytex?

Correct, as of now a native install or any Conda Forge install of Quarto will install TinyTeX to ~/.TinyTeX. This means that if you have Quarto in both environments foo and bar, they will both use/install/upgrade the same version of TinyTeX. We have future plans to package TinyTeX for Conda Forge so it can be installed as an optional dependency with Conda and eliminate this side effect #26 .

I think it does a lot of heavy environment set up stuff under the hood, and expecting it to pick up your pre-activated environment and use it may be incorrect.

How do you set your expectations correctly when you don't know how something works? I'm a VS Code beginner user, so there's a lot of things that I ignore. For example, I'll have to try this:

if you need the environment for language server / IDE features, try use the VSCode project settings to tell it the appropriate environment for your project

Thank you for suggesting it.
In this sense, it would be extremely helpful if the documentation had examples to how to solve common and well-known issues. I had to search through dozens of Stack Overflow posts to find one that mentioned the Conda auto_activate_base parameter and provided an example of a use case.

It looks to me like at this point everything is working except your terminal prompt isn't properly displaying the active environment?

Indeed. I'm keeping auto_activate_base as false because it works, yesterday it didn't. As for the prompt, I'm not sure how to solve it because, again, I don't know how VS Code interacts with other things.

Correct, as of now a native install or any Conda Forge install of Quarto will install TinyTeX to ~/.TinyTeX.
We have future plans to package TinyTeX for Conda Forge so it can be installed as an optional dependency with Conda and eliminate this side effect https://github.com/conda-forge/quarto-feedstock/issues/26 .

Thank you, I didn't know that. If currently TinyTeX has to be installed inside Quarto, what is the purpose of r-tinytex?

How do you set your expectations correctly when you don't know how something works?
[...]
In this sense, it would be extremely helpful if the documentation had examples to how to solve common and well-known issues. I had to search through dozens of Stack Overflow posts to find one that mentioned the Conda auto_activate_base parameter and provided an example of a use case.

I hear you. Personally, when I use VSCode I feel dumb. Like, how did everyone else figure this out and I can't? :shrug: The Live Share function is really sweet, but the rest of the hassle isn't worth it for me.

Thank you, I didn't know that. If currently TinyTeX has to be installed inside Quarto, what is the purpose of r-tinytex?

I'm not 100% clear on that yet. I do know that r-tinytex depends on the R language conda package and doesn't include tlmgr, which Quarto depends on. Don't quote me on this, I'm only a package maintainer, and I know very little about the R ecosystem ;)

I'm going to close this issue because I think it's more related to how VSCode works with Conda, rather than this package. Happy to continue to discuss or support however I can, though as you've seen I'm not great with VSCode. If you have more questions on this, feel free to post here again and @ me, or if you're having other issues, please open a new one :)


you should probably compile it for people who have no idea how to compile it

like the title says most people probably have no idea how to compile it

not saying you have to but im having issues compiling it myself

I don't know how to compile it either, how did you try?

i used rad studio 10.4 with the correct addons and it still failed to compile stating i didnt have something virtualview when i did

Thanks for your feedback, I'll add those instructions, I didn't release any binary yet, since it needs more adjustments. Maybe I'll publish an alpha release.

ive just never used pascal bf but i did  attempt to compile it and it was ksvirtuallistview that gave me issues

so what exactly do i need to even compile this

i can get to here now what am i missing


Start web ui in root directory

I follow the instruction to start the kubernetes web UI. It's 404 when I open http://<IP_ADDRESS>:8080 . Finally  I knew that the correct directory is http://<IP_ADDRESS>:8080/static/app/#/dashboard/ .
We should start the web ui in root directory(I mean http://<IP_ADDRESS>:8080) so that anyone like me will not be confused.

/sub

I agree the UI isn't very discoverable. We should redirect from / to the correct path. (Assuming that the UI is working well enough to expose it at all.)

I can do this if no one else is on it. Should we redirect all requests to / and /index.html or just requests with specific user-agents?

We return a list of resource paths on / currently:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/apiserver/index.go#L31
We could either redirect for certain user-agents, or choose another, simpler, more obvious, top-level path, like /www or /ui, which would at least show up in the list of valid paths.

That's great! @mikedanese @bgrant0607

Great job :+1: @mikedanese


[Funk] New extractor

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
This adds an extractor for https://www.funk.net/, a new site made by the German public broadcasting TV stations. This also fixes a small bug in the  Kaltura extractor on which the new extractor relies on.

The code also now uses _html_search_meta and  remove_end. In addition I noted in the commit message that it needs more work to also support https://www.funk.net/serien/...

Nice 👍
I did some investigating for the serien support. First of all, you need to add the Referer: https://www.funk.net HTTP header for each request. This will at least validate the *.m3u download request. In the case of the trailer for 'Hoff the Record' this will lead you to the following playlist:
#EXTM3U
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=855000,RESOLUTION=640x360,CODECS="avc1.77.30, mp4a.40.2",CLOSED-CAPTIONS=NONE
https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/index_0_av.m3u8?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=%2fi%2f20160930%2f1985%2f1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=1441000,RESOLUTION=1280x720,CODECS="avc1.77.30, mp4a.40.2",CLOSED-CAPTIONS=NONE
https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/index_1_av.m3u8?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=%2fi%2f20160930%2f1985%2f1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=2320000,RESOLUTION=1280x720,CODECS="avc1.640028, mp4a.40.2",CLOSED-CAPTIONS=NONE
https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/index_2_av.m3u8?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=%2fi%2f20160930%2f1985%2f1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=3648000,RESOLUTION=1920x1080,CODECS="avc1.64001f, mp4a.40.2",CLOSED-CAPTIONS=NONE
https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/index_3_av.m3u8?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=%2fi%2f20160930%2f1985%2f1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12

The file behind the 1080p string looks like this:
#EXTM3U
#EXT-X-TARGETDURATION:10
#EXT-X-ALLOW-CACHE:YES
#EXT-X-KEY:METHOD=AES-128,URI="https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/crypt.key?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=/i/20160930/1985/1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12"
#EXT-X-PLAYLIST-TYPE:VOD
#EXT-X-VERSION:3
#EXT-X-MEDIA-SEQUENCE:1
#EXTINF:10.000,
https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/segment1_3_av.ts?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=/i/20160930/1985/1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12
#EXTINF:10.000,
https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/segment2_3_av.ts?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=/i/20160930/1985/1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12
#EXTINF:10.000,
https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/segment3_3_av.ts?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=/i/20160930/1985/1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12
#EXTINF:10.000,
https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/segment4_3_av.ts?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=/i/20160930/1985/1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12
#EXTINF:10.000,
https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/segment5_3_av.ts?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=/i/20160930/1985/1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12
#EXTINF:10.000,
https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/segment6_3_av.ts?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=/i/20160930/1985/1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12
#EXTINF:5.646,
https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/segment7_3_av.ts?null=0&id=AgBP0tMEF0oYd%2fsSBliEwXkTYzKd9yhx6BDF2m7w%2fbWSl8p3UQ6N5M%2ftHI9GLrzoSpGnrx2p9HeLIg%3d%3d&hdntl=exp=1476879483~acl=/i/20160930/1985/1_84je45no_1_*~data=hdntl~hmac=ee9eff7c52725c3782ced2687e885e0455258e54a72dfd443e05ee52c060eb12
#EXT-X-ENDLIST

As you can see it's crypted. Can youtube-dl handle this and if so, is there a way to extract a direct download link from the above playlist?

@jlnostr Hi, I've tried your way, but it didn't work. You've probably tried it with the answers/content of the master.m3u8, but it didn't work. However, youtube-dl works fine with the simple link of the master.m3u8. You can try this with youtube-dl [playlist link].
I'm not sure how restricted this link is in concern of token and validity, but in my case youtube-dl https://jaondemandsecure-vh.akamaihd.net/i/20160930/1985/1_84je45no_1_,vjrttms0,3hh61r8k,yh13ft6h,i2m6qup1,_1.mp4.csmil/master.m3u8?hdnts=st=1477511460~exp=1477516860~acl=/i/20160930/1985/1_84je45no_1_*~hmac=e53f319a51a76f176235970380ba1d731d9af8e65f8b82e6af7dad545b152382 -o outputname worked fine.
So yes, youtube-dl can handle funk.net videos, the extractor for that just isn't implemented yet.

I added support for "serien" and the overview-pages (as playlists) to support downloading of a whole series. You can find the change in my funk-branch: Boris-de@ef5ac4610347d7a83fef4bf226951c605f402c54
Tested with two series, both worked fine. I added "Wishlist" to the tests.
@catdog2: Feel free to just amend my changes to your pull request.

@Boris-de You're the hero of my day 👍

I've did some testing today with the code from @Boris-de and everything works like expected. In my opinion the code is ready for production. It would be nice if @catdog2 could amend the changes (maybe @Boris-de needs to create a PR to his branch) :)

One issue I found is the download of FSK 16 series, like Outcast. I can't download them, even after 10pm (GMT+1).


fly login -b appends %0A (url encoded newline)

Hi,
We were trying the new -b parameter on fly login and encountered an issue with the page the browser opened. The URL contained a url-encoded newline (%0A) which caused a 500 error.
We ran
fly -t my-target login -b -k
The page opened was
https://my-target.example.com/auth/github?team_name=main&fly_local_port=54757%0A
Removing the %0A allowed the auth flow to continue.
Environment:
Browser: Chrome 67.0.3396.99
Fly: 3.14.1

I also see this issue with 3.14.1, but it appears to have been fixed in 3.14.2 and above via https://github.com/concourse/fly/commit/e89478c0400621b0a4a1422740042755d1f7d10e#diff-4d2d07a462d7a1dda6e42b8c443d6d77

Thx @selzoc! This issue is fixed in newer version. Unfortunately you will have to upgrade to get the fix. Closing this issue now.


Develop branch merge request

It contains following items:

cleanup build (add local build than docker, but vendor is required will be seen later PR)
change install process (from installer binary to shell script)
change travis CI pipeline to put snapshot container image to dockerhub
adds namespace isolation functionality by disallowing pod annotations to refer to external namespaces

CI build is failed due to missing vendor directory, not a problem.
As we talked at NPWG meeting, to simplify we remove vendoring commit hence build is failed.
Once we add vendoring, build will succeed.

let's close it and merge this code with vendoring change. Thank you!


Update AUTHORING_MANIFESTS.md

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Add pre-release advice section, and a few small updates.
Microsoft Reviewers: Open in CodeFlow

I believe the merge conflict is because I accidentally edited a line break into my main branch on line 47, before making this fork. I'm not sure how to fix this, and any advice is welcome.


[serverless-1.30] patch func deploy task for serverless 1.30.1

patch for func-deploy task to use midstream specific client built for 1.30.1

Codecov Report
All modified lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (serverless-1.30@4864fbd). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                Coverage Diff                 @@
##             serverless-1.30     #705   +/-   ##
==================================================
  Coverage                   ?   28.19%
==================================================
  Files                      ?       93
  Lines                      ?    12167
  Branches                   ?        0
==================================================
  Hits                       ?     3430
  Misses                     ?     8327
  Partials                   ?      410

Flag
Coverage Δ

e2e-test-runtime-go
27.93% <0.00%> (?)

e2e-test-runtime-springboot
28.19% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@mvinkler the PR should be done from this repo not serverless-qe/kn-plugin-func, otherwise secrets are not accessible for GH Actions.

@matejvasek do I need some permissions to be able to push a branch to openshift-knative/kn-plugin-func repo? I will use the serverless-qe account for that.

@mvinkler I think that the bot should have permission. The bot can even force-push.

@mvinkler you are in openshift-knative/contributors so you should have write perm too.

fixed in https://github.com/openshift-knative/kn-plugin-func/pull/711, closing this one.


Acceptance tests

It would be nice if we had acceptance tests which tests the whole documentation.

Another option would be to ignore the dummy app for coverage reports..


WIP: Add Leptonica package and example.

Work in progress. Awaiting hunter-packages update.

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.1759
https://travis-ci.org/ingenue/hunter/builds/239548690?utm_source=github_status&utm_medium=notification

/usr/bin/ld: /home/travis/build/ingenue/hunter/_testing/Hunter/_Base/eefa280/34327b6/20e478a/Install/lib/libjpeg.a(jcapimin.c.o): relocation R_X86_64_32S against `jpeg_natural_order' can not be used when making a shared object; recompile with -fPIC

By default we should build static library, see:

http://cgold.readthedocs.io/en/latest/tutorials/libraries/static-shared.html#pic-conflicts

Ah, I didn't know that is why it gives this issue. There are other projects where I get this too.
Thanks.

This one is good to go now

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.1778
https://travis-ci.org/ingenue/hunter/builds/239745160?utm_source=github_status&utm_medium=notification

I think I can fix MSVC2015 but I don't understand macOS compilation error. It finds GIF library but not the gif_lib.h header.

I have fixed MSVC2015 in Leptonica. Older VC++ aren't expected to work.

Toolchain vs-14-2015 is not working too.

For macOS, it has gif library but not dev headers. So it should probably check that first.

Gif should be added to Hunter then. If it's possible to build Leptonica without Gif support then there should be an option like LEPTIONICA_WITH_GIF=OFF which should be added to hunter.cmake by default.
Anyway feel free to do fixes and update version or exclude broken toolchains (pkg.leptonica branch).

Looks like the headers are never included (GIF_INCLUDE_DIR) which is probably the issue? Not sure how it was meant to work.
I will test it on my Mac soon.
I mean I fixed vs-14-2015 locally but it isn't in hunter-packages yet.

Testing

mingw and msys failed

Commented them out. https://github.com/ingenue/hunter/pull/77

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.1797
https://travis-ci.org/ingenue/hunter/builds/239882997?utm_source=github_status&utm_medium=notification

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.1799
https://travis-ci.org/ingenue/hunter/builds/239889981?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.19.5


icons issues

v 5.700

What Android version are you using? Did you install the app from Google Play or F-Droid?

From F-Droid. Android 9 (LineagOS 16.0 + microG)

Having this, too (LineageOS 16.0, master branch). Apparently, tinting the icons in the dark theme tints too much. In the light theme, I don't have those artifacts.

Sounds like a LineageOS issue to me. I'd be happy to include reasonable workarounds for this. But I'm not going to install LineageOS to track this issue down.

Is there a proof that it's a LineageOS? Have you checked it on Android 9 (not Lineage)?

K9 already uses matching icons for the theme. We could try to call withIconTintingEnabled(false) on the drawer item. I will give it a try if I find the time

Calling withIconTintingEnabled(false) does not help. Additionally, the behavior is quite weird: When opening the folder manager and going back to the app, the artifacts are gone for all icons that were shown in the folder manager (at least on my device). I am not able to reproduce the problem in an emulator.

Additionally, the behavior is quite weird: When opening the folder manager and going back to the app, the artifacts are gone for all icons that were shown in the folder manager (at least on my device).

Artifacts are gone for only those icons, that are shown in the folder manager.


feat(Admin): restart required after user updating

Issue:
What I did
How to test

Deploy preview ready!
Built with commit 65b7cae78dabbc28393acd501f73a03cf6646d73
https://deploy-preview-458--mcslite.netlify.com

Deploy preview ready!
Built with commit 65b7cae78dabbc28393acd501f73a03cf6646d73
https://deploy-preview-458--mcs-lite-introduction.netlify.com

Deploy preview ready!
Built with commit 65b7cae78dabbc28393acd501f73a03cf6646d73
https://deploy-preview-458--mcs-lite-ui.netlify.com


Unable to use variables in problemMatcher regexp

I have searched the issues repo and I believe this one hasn't been reported.
System:

VSCode Version: 1.31.1
OS Version: Mac OS Mojave

Steps to Reproduce:

Put task's variable(s) into the problemMatcher object, for example $cwd, like this:

"problemMatcher": {
  "pattern": {
    "kind"    : "location",
    "regexp"  : "^\\${cwd}\\/(.*):(\\d.*):(\\d.*): (error|warning|info): (.*)$",
    "file"    : 1,
    "line"    : 2,
    "column"  : 3,
    "severity": 4,
    "message" : 5,
    "loop"    : true,
  }
}

Run the task, I use it to parse a compiler output, and it failed. If I manually put the content of $cwd variable (with necessary escaping), it works.

So, I think vs code doesn't replace any variable(s) being used within the regexp of problemMatcher. It should be a bug, right?
Does this issue occur when all extensions are disabled?: Yes

Duplicate of #69622. The way for more complex problem matchers should be new API.

I don't think it's quite similar. The problem of #69622 is with package.json which I didn't know about. This problem I'm reporting happens with tasks.json which everybody uses. And if the problem had been reported since long time ago, why didn't it get fix after all this time? I believe putting vscode variables into regexp (with automatic escaping) shouldn't be that hard.

A more complete solution for allowing more than just regex in problem matchers is to allow a new type of problem matcher which lets you write code for your problem matching instead of using a regex. With this solution, adding variable to the problem matcher is redundant. It does not make sense to have both. #11663 tracks adding new API for code problem matchers.


Blade: Wrong data used when repeatedly including a template that extends another

Laravel Version: 5.4.15
PHP Version: 7.1
Database Driver & Version: n/a

Description:
It seems when including a template that extends another, the data rendered is always the data given to the first include of the template.
Steps To Reproduce:
These are my 3 templates for testing:
index.blade.php:
@include('inherits', ['var' => 'First Include'])
@include('inherits', ['var' => 'Second Include'])

inherits.blade.php:
@extends('base')

@section('a', $var)

base.blade.php:
@yield('a')

When rendering index.blade.php the output should be "First IncludeSecond Include". Instead you see "First IncludeFirst Include".

Instead of @section('a', $var) use:
@section('a')
   {{ $var }}
@overwrite

@themsaid Thanks!


tile shifted to the last after fullscreen (F11) when subTabbed is used

Problem Description
tile shifted to the last in order after fullscreen (F11) when subTabbed is used
Steps to Reproduce
In spiral layout (or any others), put chrome in the main tile, press F11 to go full screen, and press F11 again to exit, Chrome window will be shifted to the last position, which is a very small window.
Configuration File
myLayout =
            avoidStruts .
            spacingRaw True (Border i i i i) True (Border i i i i) True .
            mkToggle (NBFULL ?? NOBORDERS ?? EOT) .
            mkToggle (single REFLECTX) .
            mkToggle (single REFLECTY) .
            hiddenWindows .
            windowNavigation .
            subTabbed . -- if commented out, full screen window restores to its spot
            screenCornerLayoutHook $
            myDefaultLayout

Checklist

[X] I've read CONTRIBUTING.md

[X] I tested my configuration with xmonad-testing

Sounds like this is fixed by #407, if you want to give that pr a try

Sounds like this is fixed by #407, if you want to give that pr a try

#407 is what I'm looking for... Thank you!


Adds the environment parameter to ::executeCommand

This PR adds an optional $env parameter to the command run. Lots of systems nowadays use an environment variables to manipulate their system behaviour. During post composer's install you might like to run (e.g.) assets install not just for a particular env var, but multiple. What requires forking a process with a specific env. Hereby this PR is here.

Closing this pull request as this bundle is now deprecated. Symfony Flex replaces this bundle.


Timelapse snapshots on layer change

What would you like to see added?
Currently, timelapse snapshots are time-based, and the result, depending on how your camera is set up, can be all over the place and messy.
Layer changes are often around the same locations every layer, relative to each other (possibly depending on your seam settings).
I don't know if it's possible to "hook into" gcode being run (I don't know how the live gcode viewer does it), but if it were possible to only run snapshots on layer changes, that should result in much cleaner timelapses I'd think.

I would appreciate it if you at least pretended to have read the docs before you open a ticket.
Please refer to the sample config to learn what different timelapse method exist out of the box, and the corresponding section in g-code commands on how to manually control the lapsing for all the needs you may have.

Believe it or not, I've been through the documentation several times, especially the sample config page, I even looked at the manual mode timelapse config option, but couldn't tell from that that such a thing was possible.
I did not expect to find it back in the "Interacting with Klipper" section, a page I've also read more than once, but not specifically looking for this setting, so I read over it.
The fact that I read over it in the documentation is my bad, and I apologize for that, but there's no need to get rude about it and assume I didn't read the documentation. It's not like you're getting dozens of issues per day that you have to sift through.


Error handling for services that don't match ports on containers is opaque.

We allow ContainerPort to be empty, but this integrates poorly with Pods that have no explicit Ports.  It's hard to validate a priori, since the ports may not exist.
We should at the very least throw some errors into the event log.

I propose to change the semantics - if you omit the destination port in your service, we should use the same port as your service port.

@brendandburns @thockin Was one of you planning to work on this?

I'll wrap this up in the service reorg work IF we can come to a decision about compat.  Basically, if we change this we are breaking compat.

This was fixed by #4801


operator/ingress: Add Forwarded header policy

This commit implements NE-317.

operator/v1/types_ingress.go (IngressControllerSpec): Add HTTPHeaders field with the new IngressControllerHTTPHeaders type.
(IngressControllerHTTPHeaderPolicy): New type.
(AppendHTTPHeaderPolicy, ReplaceHTTPHeaderPolicy, IfNoneHTTPHeaderPolicy, NeverHTTPHeaderPolicy): New constants.
(IngressControllerHTTPHeaders): New type.  Describe policy for handling HTTP headers.  For now, the only field is ForwardedHeaderPolicy, with the new IngressControllerHTTPHeaderPolicy type, for specifying how the HTTP Forwarded header and related headers should be handled.
operator/v1/0000_50_ingress-operator_00-ingresscontroller.crd.yaml:
operator/v1/zz_generated.deepcopy.go:
operator/v1/zz_generated.swagger_doc_generated.go: Regenerate.

Corresponding enhancement proposal: https://github.com/openshift/enhancements/pull/371

the doc is good, the validation wellformed.  I just don't quite understand the need for two layers.  I'd like to understand before approving.

/lgtm
/hold
hold is just in case @Miciah has second thoughts about depth. If you like the depth, remove the hold at your discretion.

/hold cancel
I reduced depth, so the new field is spec.httpHeaders.forwardedHeaderPolicy: Append|Replace|IfNone|Never.

/lgtm


(fix): properly determine selected range while still in visual mode

Fixes #427.

Remember that . and v marks can be top&bottom or bottom&top depending on how visual region was created.


hide history tab, fix prod create AWS-role user issue

hide history tab, fix prod create AWS-role user issue

History Tab is now hidden on Prod:

AWS Roles are displayed:


Readme update and asking for confirmation when deleting

Added confirm_when_delete config, default to true, if true will ask the user to confirm before deleting a todo,
added missing icon -> calendar in readme

PR is being closed due mismatching with latest releases


BlockType, enums, IDs and mods.

Let's talk about enums first.
The current implementation uses an enum for differentiate block types. This prevents adding new Blocks added from mods. While the current implementation supports modded blocks by declaring them as UnknownBlocks it will stop working if the server uses to many mods, because the IDs get parsed as byte.
Let's talk about IDs next
I know that the use of BlockIDs comes from the way the raspberryjammod is made. I want to raise the attention to the fact that this is not the way minecraft (and forge) are handling block (and item) registration. They use unique item and block names to register them. The problem with IDs is, that they can change from gameworld to gameworld. IDs have to get handled out separately for every connection. On one server an ID can be a IronChest, on an other server it could be a BuildCraft pipe.
I hope i could show my concerns. I'm currently thinking about a ways to solve this problem. I wanted to raise attention to this problem now, because we are in an early state and I want to avoid having a big problem later on.

Things I think we have to do:

Change the use of BlockIDs to the names of blocks.
Build a registry to register blocks (and later items), which handles the mapping of the objects and IDs with the use of names rather than initializing the objects with hard coded IDs.

OK, sounds like this will be better done early, yes.

I've been thinking a bit more about this. The thing that's bothering me the most is that our blocks currently are tied to the Java implementation, whereas they should be pure data structures, and their type should be defined by... their type. You make a great point about mods, of course, but I'd still want to kick that enum out. I also want to keep the ceremony associated with creating a block type to a minimum: if we project ourselves into the future where we can also interact with Minecraft for Windows 10, we don't want block authors to have to write too much code (if any) for each of the providers. Lots to think about...


[Easy] Update README.md

Improve README.md file

What improvements are you looking for? Style? Information added? Reflow/Redesign? Let me know!

@GreenJ84

Redesign it!
Add icon/button for website's live link
Remove portfolio link
Add links of contributing.md and code-of-conduct.md
Add badges, if possible.

Attach screenshots of changes while making pull request for easier and fast review.

@GreenJ84

Redesign it!
Add icon/button for website's live link
Remove portfolio link
Add links of contributing.md and code-of-conduct.md
Add badges, if possible.

Attach screenshots of changes while making pull request for easier and fast review.

@Sanket1308 I would like to work on this issue

please assign me this issue

Go ahead! Contribute well🚀


Added custom crop mode

In addition to "outbound" or "inset" mode, added ability to cpecify custom mode in format: "{horz}:{vert}" where {horz} is one from "left", "cetrer", "right" and {vert} is one from "top", "center", "bottom"
For example "center:top" mean that thumbnail will be contain top part of image, not center as by default. "center:center" mode is the same as "outbound"

Sorry for my late respsonse but thanks for you pull request @rtf-const!


Show app error if identities failed to load

Description
When idmWallet.identities.load() fail, we should display a global error using the designs of #121.
Acceptance Criteria

[x] Show a global errors when the identities fail to load, with the error page designed in #121

This was implemented as part of #148


Add newsletter subscribe functionality

Still debating on whether or not to add this functionality given that if someone wants to unsubscribe, they may think to come to us and not Four Diamonds. What are our current thoughts on this @JoseRoman?

@Ernie3, @theseanconn: Although we might not be able to allow users to sign up for the newsletter of Four Diamonds, it is possible to create a separate newsletter for KHS only which the committee can be in charge of.
If the option to subscribe to the Four Diamonds newsletter is a must, I will need to talk to whoever is in charge of the web development/technology so that Ernie and I can coordinate and make the necessary adjustments.

Subscribing to the Four Diamonds Newsletter is not a must. Austin and I will assign it to a committee and KHS will have our own News letter.

Perfect then, we can add a subscribe button to our own newsletter. Sound good @theseanconn?

@Ernie3, @theseanconn: This needs more information, are you guys going to use MailChimp or a similar service?

What do you suggest?
On Tue, Oct 20, 2015 at 4:50 PM, Jose Roman<EMAIL_ADDRESS>wrote:

@Ernie3 https://github.com/Ernie3, @theseanconn
https://github.com/theseanconn: This needs more information, are you
guys going to use MailChimp or a similar service?
—
Reply to this email directly or view it on GitHub
https://github.com/KHS-Minithon/website/issues/17#issuecomment-149697939
.

--
For The Fight. For The Cure. For The Kids,
Sean Connolly
Kennett High School Mini-THON Head
Event Page http://fourdiamonds.donordrive.com/event/khs16    Twitter
http://twitter.com/khsminithon  Instagram
http://instagram.com/khsminithon

@theseanconn MailChimp is great. Their free plan offer up to 2,000 subscribers and 12,000 emails per month.

Okay, ill look into it.
On Tue, Oct 20, 2015 at 5:51 PM, Jose Roman<EMAIL_ADDRESS>wrote:

@theseanconn https://github.com/theseanconn MailChimp is great. Their
free plan offer up to 2,000 subscribers and 12,000 emails per month.
—
Reply to this email directly or view it on GitHub
https://github.com/KHS-Minithon/website/issues/17#issuecomment-149713647
.

--
For The Fight. For The Cure. For The Kids,
Sean Connolly
Kennett High School Mini-THON Head
Event Page http://fourdiamonds.donordrive.com/event/khs16    Twitter
http://twitter.com/khsminithon  Instagram
http://instagram.com/khsminithon

Actually I dont know if we are going to do this. I think at this point it is too much for the committees to handle. This is only our first year doing this and we are already spread thin.

@theseanconn: so can we close this issue then?

We will remove it for now. In the future if this needs to be added then let us know by creating a ticket with details. We'd like to push this project into production within this month, so let's start handling the tickets we know HAVE to get done


Adds command to add profile card properties

Usage
m365 tenant people profilecardproperty add [options]
Description
Adds a custom attribute as a profile card property
Options

Option
Description

-n, --name <name>
The name of the property to add. Allowed values: userPrincipalName, fax, streetAddress, postalCode, stateOrProvince, alias, extensionAttribute1, extensionAttribute2, extensionAttribute3, extensionAttribute4, extensionAttribute5, extensionAttribute6, extensionAttribute7, extensionAttribute8, extensionAttribute9, extensionAttribute10, extensionAttribute11, extensionAttribute12, extensionAttribute13, extensionAttribute14, extensionAttribute15

-d, --displayName [displayName]
The display name of a property, only use together with extension attributes.

Remarks
You can specify localized values for the displayName as well. These can be entered by suffixing the displayName option with a language code: --displayName-nl-NL "Kostencentrum" --displayName-de "Kostenstelle".
Examples
Add the UPN as a profile property to the profile cards
m365 tenant people profilecardproperty add --name userPrincipalName

Add a custom extension attribute Cost Center as a profile property to the profile cards
m365 tenant people profilecardproperty add --name extensionAttribute1 --displayName "Cost Center"

Add a custom extension attribute Cost Center as a profile property to the profile cards with a dutch localization
m365 tenant people profilecardproperty add --name extensionAttribute1 --displayName "Cost Center" --displayName-nl-NL "Kostencentrum"

Additional Info
--displayName is required when an extensionAttribute is picked.
May need a new scope: PeopleSettings.ReadWrite.All
For localization properties, let's include them in validation, so that for now, all unknown properties must start with displayName-
More Information

Add or remove custom attributes on a profile card using the profile card API

Awesome suggestion! As this command is for adding properties to the person's profile card, how about using tenant as the namespace rather than aad?

For custom properties, should we use customAttribute1 rather than extensionAttribute1?

For custom properties, should we use customAttribute1 rather than extensionAttribute1?

Well, I personally felt like we should align with EntraID instead of the Graph, as that is the API...

Looking at the underlying API, it also allows you to handle localizations. What if we used format like: --localizations "language1,displayName1;language2,displayName2"?

Would language1=displayname1;language2=displayName2 be better?

Looking at the underlying API, it also allows you to handle localizations. What if we used format like: --localizations "language1,displayName1;language2,displayName2"?

Would language1=displayname1;language2=displayName2 be better?

Not sure. It's already possible to do --localizations="value" so too many = could get confusing. Also, what if in the future there will be more values to set per language? Would using = block us?

LGTM,
small comment you already know of is that I would align the autocomplete values to camlCase

Maybe instead of using <language-code1>,<value1>;<language-code2>,<value2>, what if we just allow multiple localizations options? Just like we do for outlook mail send where we allow multiple --attachment options to attach multiple attachments to a mail.
So according to me --localization <langcode1>;<value1> --localization <langcode2>;<value2> is much more user friendly.

BTW when merging this we need to extend our app registration with an additional permission PeopleSettings.ReadWrite.All.
maybe it's worth mentioning this in the spec as well

Thanks all, great job, can't wait to use this.
I'd suggest that we use the format: m365 admin people profileCardProperty as the format. That follows the MS Graph domain model and allows us to add more people admin settings in the future ;-)

Hi @wictorwilen, thanks for chiming in here! I like the brevity.
We currently don't have an admin root command group though.
Let's keep it in tenant, but add a people command group: m365 tenant people profilecardproperty.

@martinlingstuyl - gotcha, makes sense

@martinlingstuyl, for localization properties, let's include them in validation, so that for now, all unknown properties must start with displayName-

What do you think about the suggestion @milanholemans gave?

So according to me --localization <langcode1>;<value1> --localization <langcode2>;<value2> is much more user friendly.

As he mentioned, this is an approach we currently use in another command so I agree that it's a good idea to streamline this approach to this command as well.

What do you think about the suggestion @milanholemans gave?

So according to me --localization <langcode1>;<value1> --localization <langcode2>;<value2> is much more user friendly.

As he mentioned, this is an approach we currently use in another command so I agree that it's a good idea to streamline this approach to this command as well.

Hi @Jwaegebaert, I picked another route for this: --displayName-nl-NL "Kostenplaats". This method depends on unknown options but is clearer for localization I believe.

Ill check it out!

@martinlingstuyl one caveat that I just realized: minimist will resolve --displayName-nl-NL to displayNameNlNl because - is not allowed in property name, and if I'm not mistaken it automatically considers dashes as spaces which are removed. If this is indeed the case, then it would make it very hard for us to resolve the language and @milanholemans suggestion could be better.

apparently it's possible...

Nice! I rest my case 👏

@wictorwilen, what we did notice and found slightly confusing is the following:
For the Graph there are two tables with Graph properties and how they map to the Entra ID properties.
It turns out we need to use fax, streetOrProvince and alias (which are Entra ID property names) but also customAttribute1-15, which are the Graph representations of extensionAttribute1-15.
Are we correct in thinking it ought to be more consistent here? (Either use the Graph property names OR the Entra ID property names for all properties/attributes/

@martinlingstuyl - I would recommend using the same naming convention the API's and documents have, otherwise it will just be confusing.

Hi @wictorwilen, I agree with you on that. And that is how we're implementing it.
I just meant to say it's confusing for us working with the API that we have to use customAttributes (the Graph property name) and stateOrProvince (Entra ID property name)
Or maybe we're misunderstanding it, but that is what the documentation seems to say. There's two tables with property mappings. In the uppermost one we need to pick the left column, in the lower one the right column,
Do you see what I mean?

Ok, gotcha. I'll let the team know so the documentation is crisp and not causing confusion.


Mislabelled Microsoft Ignite Video on Youtube - supposed to be deep dive on Identity Protection, but it is Teams

Hello MS Team
Not sure where else to book this issue. It is about mislabelled video on Microsoft Ignite Youtube channel
https://www.youtube.com/watch?v=z-KqH2980c4
The title is "How Microsoft uses Azure Active Directory Identity Protection and Conditional Access | BRK2132" but it is the video about Teams product.
It comes in Google searches together with this page when searching about Conditional Access. Therefore i decided to book this problem here.
Regards,
Serg

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

ID: c2e83171-fd05-9fe1-3ba7-0fb20161ee63
Version Independent ID: 2e6b2451-5ff8-a277-90ea-49aa70957977
Content: What is Azure Active Directory Identity Protection?
Content Source: articles/active-directory/identity-protection/overview-identity-protection.md
Service: active-directory
Sub-service: identity-protection
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@SergGu thanks! I'm reaching out to find the owner of that video.

Thank you! I've reported this to the owner of the video. Will update the thread when they have a resolution.


Bug: upgrading from 0.5.1 to 0.6.1: panic: runtime error: invalid memory address or nil pointer dereference

Describe the bug
The worker and crawlab master can keep restarting after the upgrade.
To Reproduce
Steps to reproduce the behavior:

Using 0.5.1 crawlab setup, put the dockers down:

docker-compose down | true

Pull the most recent image:

docker pull crawlabteam/crawlab

Edit the docker-composer.yml and replace

tikazyq/crawlab:latest

with
image: crawlabteam/crawlab:latest

Execute the docker-compose command:

docker-compose up -d

Expected behavior
I expect to see the 0.6.1 version running
To Revert

Execute

docker-compose down | true

Undo the changes in the step 3
Execute:

docker-compose up -d

Now v0.5.1 will return.
Logs
both worker and cralab_master keep restarting:
1abff6a82c63   crawlabteam/crawlab     "/bin/bash /app/bin/…"   9 minutes ago   Restarting (2) 44 seconds ago                                               worker
7489909bd714   crawlabteam/crawlab     "/bin/bash /app/bin/…"   9 minutes ago   Restarting (2) 42 seconds ago                                               crawlab_master

The worker log:
/go/pkg/mod/github.com/crawlab-team/go-trace@v0.1.1/trace.go:13 github.com/crawlab-team/go-trace.TraceError()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:97 github.com/crawlab-team/crawlab-core/schedule.(*Service).Enable()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:148 github.com/crawlab-team/crawlab-core/schedule.(*Service).update()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:122 github.com/crawlab-team/crawlab-core/schedule.(*Service).Update()
/usr/local/go/src/runtime/asm_amd64.s:1371 runtime.goexit()
expected exactly 5 fields, found 6: [0 0 1 * * *]
/go/pkg/mod/github.com/crawlab-team/go-trace@v0.1.1/trace.go:13 github.com/crawlab-team/go-trace.TraceError()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:97 github.com/crawlab-team/crawlab-core/schedule.(*Service).Enable()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:148 github.com/crawlab-team/crawlab-core/schedule.(*Service).update()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:122 github.com/crawlab-team/crawlab-core/schedule.(*Service).Update()
/usr/local/go/src/runtime/asm_amd64.s:1371 runtime.goexit()
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xf1ed32]

goroutine 103 [running]:
github.com/crawlab-team/crawlab-core/models/service.(*Service).GetTaskList(0xc000692280, 0xc000409d70, 0x0, 0x6, 0xc0000c6988, 0x0, 0x4422f6, 0x12d97d0)
	/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/models/service/task_service.go:35 +0x72
github.com/crawlab-team/crawlab-core/task/scheduler.(*Service).initTaskStatus(0xc00040ea80)
	/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/task/scheduler/service.go:431 +0xb0
created by github.com/crawlab-team/crawlab-core/task/scheduler.(*Service).Start
	/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/task/scheduler/service.go:45 +0x45

crawlab master log:
/go/pkg/mod/github.com/crawlab-team/go-trace@v0.1.1/trace.go:13 github.com/crawlab-team/go-trace.TraceError()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:97 github.com/crawlab-team/crawlab-core/schedule.(*Service).Enable()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:148 github.com/crawlab-team/crawlab-core/schedule.(*Service).update()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:122 github.com/crawlab-team/crawlab-core/schedule.(*Service).Update()
/usr/local/go/src/runtime/asm_amd64.s:1371 runtime.goexit()
expected exactly 5 fields, found 6: [0 0 1 * * *]
/go/pkg/mod/github.com/crawlab-team/go-trace@v0.1.1/trace.go:13 github.com/crawlab-team/go-trace.TraceError()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:97 github.com/crawlab-team/crawlab-core/schedule.(*Service).Enable()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:148 github.com/crawlab-team/crawlab-core/schedule.(*Service).update()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/schedule/service.go:122 github.com/crawlab-team/crawlab-core/schedule.(*Service).Update()
/usr/local/go/src/runtime/asm_amd64.s:1371 runtime.goexit()
error decoding key _id: an ObjectID string must be exactly 12 bytes long (got 36)
/go/pkg/mod/github.com/crawlab-team/go-trace@v0.1.1/trace.go:13 github.com/crawlab-team/go-trace.TraceError()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/models/service/binder_list.go:82 github.com/crawlab-team/crawlab-core/models/service.(*ListBinder).Process()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/models/service/binder_list.go:42 github.com/crawlab-team/crawlab-core/models/service.(*ListBinder).Bind()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/models/service/base_service.go:67 github.com/crawlab-team/crawlab-core/models/service.(*BaseService).GetList()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/models/service/task_service.go:34 github.com/crawlab-team/crawlab-core/models/service.(*Service).GetTaskList()
/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/task/scheduler/service.go:431 github.com/crawlab-team/crawlab-core/task/scheduler.(*Service).initTaskStatus()
/usr/local/go/src/runtime/asm_amd64.s:1371 runtime.goexit()
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xf1ed32]

goroutine 150 [running]:
github.com/crawlab-team/crawlab-core/models/service.(*Service).GetTaskList(0xc000409840, 0xc000e9e000, 0x0, 0x6, 0xc0003c8088, 0x0, 0x4422f6, 0x12d97d0)
	/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/models/service/task_service.go:35 +0x72
github.com/crawlab-team/crawlab-core/task/scheduler.(*Service).initTaskStatus(0xc000392420)
	/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/task/scheduler/service.go:431 +0xb0
created by github.com/crawlab-team/crawlab-core/task/scheduler.(*Service).Start
	/go/pkg/mod/github.com/crawlab-team/crawlab-core@v0.6.1-0.20220612043053-72fb6748a131/task/scheduler/service.go:45 +0x45

the docker-composer.yml lines about worker and crawlab master:
version: '3.3'
services:
  master:
    restart: always
    image: crawlabteam/crawlab:latest
    #image: tikazyq/crawlab:latest
    container_name: crawlab_master
    environment:
      CRAWLAB_SERVER_MASTER: Y
      CRAWLAB_MONGO_HOST: mongo
      CRAWLAB_REDIS_ADDRESS: "redis"
    ports:
      - "8080:8080" # frontend port mapping 前端端口映射
    depends_on:
      - mongo
    volumes:
       - "./volumes/log/master:/var/logs/crawlab"
       - "./volumes/spiders:/app/spiders"
  worker:
    restart: always
    image: crawlabteam/crawlab:latest
    #image: tikazyq/crawlab:latest
    container_name: worker
    environment:
      CRAWLAB_SERVER_MASTER: "N"
      CRAWLAB_MONGO_HOST: "mongo"
      CRAWLAB_REDIS_ADDRESS: "redis"
    depends_on:
      - mongo
    volumes:
      - "./volumes/log/worker:/var/logs/crawlab" # log persistent 日志持久化

Please refer to the documentation for v0.6
https://docs.crawlab.cn/en/guide/installation/docker.html

Please refer to the documentation for v0.6

I did. The steps are the same of the old doc.
Is something special needed to do the ugprade from 0.5.1 to 0.6.x?

Please refer to the documentation for v0.6

I did. The steps are the same of the old doc.
Is something special needed to do the ugprade from 0.5.1 to 0.6.x?

Yes. v0.6 is quite different than 0.5, so as the configuration docker-compose.yml.
In your docker-compose.yml, I can see it's pretty much the same as the one in 0.5. It should be something like this...
version: '3.3'
services:
  master:
    image: crawlabteam/crawlab
    container_name: crawlab_master
    restart: always
    environment:
      CRAWLAB_NODE_MASTER: "Y"  # Y: master node
      CRAWLAB_MONGO_HOST: "mongo"  # mongo host address. In the docker compose network, directly refer to the service name
      CRAWLAB_MONGO_PORT: "27017"  # mongo port
      CRAWLAB_MONGO_DB: "crawlab"  # mongo database
      CRAWLAB_MONGO_USERNAME: "username"  # mongo username
      CRAWLAB_MONGO_PASSWORD: "password"  # mongo password
      CRAWLAB_MONGO_AUTHSOURCE: "admin"  # mongo auth source
    volumes:
      - "/opt/crawlab/master:/data"  # persistent crawlab data
    ports:
      - "8080:8080"  # exposed api port
    depends_on:
      - mongo

  mongo:
    image: mongo:4.2
    restart: always
    environment:
      MONGO_INITDB_ROOT_USERNAME: "username"  # mongo username
      MONGO_INITDB_ROOT_PASSWORD: "password"  # mongo password
    volumes:
      - "/opt/crawlab/mongo/data/db:/data/db"  # persistent mongo data
    ports:
      - "27017:27017"  # expose mongo port to host machine

Understood. I tried to move out the worker and changed the docker-compose.yml to be similar with standard 0.6.x composer file. But I got the same error. So I think is not possible to migrate from 0.5 to 0.6 in most of the cases (maybe due plugins?).

Can you elaborate a little bit more on the issue details?

@tikazyq
I followed docker-compose.yml in guide.
But I just got this bug with v0.6.0-1.
Pls reopen this issue.


AttributifyAttributes don't have left type

UnoCSS version
0.54.1
Describe the bug

Reproduction
https://github.com/Debbl/unocss-type-test
System Info

MacOS
Chrome
VsCode

Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

refer to this

By default, the type includes common attributes from @unocss/preset-uno. If you need custom attributes, refer to the type source to implement your own type.

Refer to https://github.com/unocss/unocss/pull/2932#issuecomment-1660252907


Pedicle screw simulator erro

Hello,
I've tried several times to use the module and it just gives errors and not working properly. I've installed last slicer version and reinstalled the module several times but still no response.
please help.
Thanks a lot.
Dr. Ayman Arakeep

Please help @lassoan

It is summer and I'm on vacation, but I'll get to this soon.

I'm soo sorry , have a good time .
Thanks a lot
On Tue, 2 Aug 2022, 2:11 pm Andras Lasso, @.***> wrote:

It is summer and I'm on vacation, but I'll get to this soon.
—
Reply to this email directly, view it on GitHub
https://github.com/lassoan/PedicleScrewSimulator/issues/7#issuecomment-1202404274,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2JNZGIJTNCY72DPUI64TETVXEF5JANCNFSM55DB5SLA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Version 2.2.0 undefined method `property' for Chef::Resource::IptablesRule:Class

I fixed the issue changing version to 1.0.0
Compiling Cookbooks...

================================================================================
Recipe Compile Error in .../chef-solo/cookbooks-2/iptables/resources/rule.rb
================================================================================

NoMethodError
-------------
undefined method `property' for Chef::Resource::IptablesRule:Class

Cookbook Trace:
---------------
 .../chef-solo/cookbooks-2/iptables/resources/rule.rb:20:in `class_from_file'

Relevant File Content:
----------------------
.../chef-solo/cookbooks-2/iptables/resources/rule.rb:

 13:  #
 14:  # Unless required by applicable law or agreed to in writing, software
 15:  # distributed under the License is distributed on an "AS IS" BASIS,
 16:  # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 17:  # See the License for the specific language governing permissions and
 18:  # limitations under the License.
 19:
 20>> property :name, kind_of: String, name_attribute: true
 21:  property :source, kind_of: String, default: nil
 22:  property :cookbook, kind_of: String, default: nil
 23:  property :variables, kind_of: Hash, default: {}
 24:
 25:  action :enable do
 26:    execute 'rebuild-iptables' do
 27:      command '/usr/sbin/rebuild-iptables'
 28:      action :nothing
 29:    end

This occurs if you're running chef-client prior to 12.5.  12.5 introduced a new, simpler, method of creating custom resources and this cookbook uses the new method.

@tas50 thanks!


IMP: Expose new match_ids parameter

closes #118. This currently adds no new unit tests because honestly I'm not 100% on what this behavior is meant to do (it seems to have something to do with mixed orientation), but it does expose the new parameter. Additionally, I'm not positive that it's actually being sent to R properly (in fact I have a strong suspicion it isn't) because I've never tried to do this before, but it's a start.

This PR would need to involve editing the R scripts located in assets as well.

@ebolyen yeah I figured as much, I don't really know how that works, but I can figure it out

@ebolyen is this the correct modifications of the R script? Seems like all I needed to do was put the arg in a variable then pass it off.

Hey there @ChrisKeefe, can you please review this PR when you get a chance? Please address any changes you might want made to @ebolyen & I - we are teaming up to run this one across the finish line!

This is probably best addressed by https://github.com/qiime2/q2-types/issues/207, closing for now.


Outdated listing

your latest versions of this package has not been listed, you will need to go re-run the action "Build Repo Listing" on your "MinerPackages" repo

Ah 🤔 I've just ran the listing but it still didn't update lol, gonna have to figure out what's going on but thanks for letting me know!

Oh, ok nvm I just had to Force-reload with Shift+F5 xD
Thanks again, updated now!


transferred prompts

transferred changed prompts from prompt folder into the model.py file
changed tech stack model temperature parameter from 0.2 to 0.1

LGTM!


Implement real Explore-Then-Commit algorithms

My first implementation is childish and naive.
[On Explore-Then-Commit Strategies, by A.Garivier et al, NIPS, 2016] studies other E-T-C policies.
I should:

[x] Implement all their Explore-Then-Commit strategies (FB-ETC, SPRT-ETC, BAI-ETC, Delta-ETC),
[ ] Quickly reproduce their results.

I need at least one "smart" explore-then-commit strategy to demonstrate the effectiveness of my SparseWrapper policy for a child policy which is not an index policy. (for my article on sparse bandits)

It's not so trivial to implement their policies, everything seems to be for 2 arms only?

Final ranking for this environment #0 :

Policy 'AdBandits($T=10000$, $\alpha=0.5$)'   was ranked      1 / 22 for this simulation (last regret = 18.479).
Policy 'Thompson'     was ranked      2 / 22 for this simulation (last regret = 23.677).
Policy '$\mathrm{UCB}{d=d{lb}}$($c=0$)'     was ranked      3 / 22 for this simulation (last regret = 23.906).
Policy 'DMED$^+$(Bern)'       was ranked      4 / 22 for this simulation (last regret = 25.854).
Policy 'BayesUCB'     was ranked      5 / 22 for this simulation (last regret = 26.719).
Policy 'kl-UCB$^{++}$($T=10000$)'     was ranked      6 / 22 for this simulation (last regret = 33.396).
Policy 'kl-UCB-switch'        was ranked      7 / 22 for this simulation (last regret = 36.073).
Policy 'kl-UCB-switch(delayed f)'     was ranked      8 / 22 for this simulation (last regret = 36.979).
Policy 'kl-UCB-switch($T=10000$)'     was ranked      9 / 22 for this simulation (last regret = 37.938).
Policy 'kl-UCB-switch($T=10000$, delayed f)'  was ranked      10 / 22 for this simulation (last regret = 38.979).
Policy 'kl-UCB'       was ranked      11 / 22 for this simulation (last regret = 39.625).
Policy 'MOSS-H($T=10000$)'    was ranked      12 / 22 for this simulation (last regret = 46.104).
Policy 'UCB($\alpha=1$)'      was ranked      13 / 22 for this simulation (last regret = 47.271).
Policy 'ApprFHG($T=10500$)'   was ranked      14 / 22 for this simulation (last regret = 48.437).
Policy 'MOSS' was ranked      15 / 22 for this simulation (last regret = 49.24).
Policy 'MOSS-Anytime($\alpha=1.35$)'  was ranked      16 / 22 for this simulation (last regret = 52.344).
Policy 'DeltaUCB($T=10000$, $\Delta=0.1$, $alpha=4$)' was ranked      17 / 22 for this simulation (last regret = 173.92).
Policy 'ETC_BAI($T=10000$, $\Delta=0.1$)'     was ranked      18 / 22 for this simulation (last regret = 427.8).
Policy 'ETC_FixedBudget($T=10000$, $\Delta=0.1$, $T_0=3385.0$)'       was ranked      19 / 22 for this simulation (last regret = 1129).
Policy 'ETC_SPRT($T=10000$, $\Delta=0.1$)'    was ranked      20 / 22 for this simulation (last regret = 1137.4).
Policy 'ETC_KnownGap($T=10000$, $\Delta=0.1$, $T_0=3910$)'    was ranked      21 / 22 for this simulation (last regret = 2627.7).
Policy 'ETC_RandomStop($T=10000$)'    was ranked      22 / 22 for this simulation (last regret = 4126.5).