make clippy pedantic

This works, but I wonder if it wouldn't be better to take a more granular approach at the source level.
Something like this in main.rs:
#![deny(clippy::pedantic)]
#![warn(clippy::similar_name)]


ENH: Update copybutton image to match GitHub

This updates our icon to use the "copy" copybutton from tabular. It's more in-line with how GitHub styles copy buttons, which is the major inspiration for the design here as well.
I also vaguely remember @pradyunsg saying he thought this was a better design 😅
closes #151

I’m glad that GH changed things!
Honestly, I think even plain text is actually great, as long as the theme supports it: https://www.gatsbyjs.com/docs/how-to/local-development/environment-variables/


ensure appropriate sensu version is installed

there is an older version of sensu available in centos (and
pre-installed on some overcloud images).  Ensure that we replace it
with the package from the sensuapp repository.

An alternative solution here would be to just set state: latest rather than state: present when installing sensu, but this can mean installing an unexpected upgrade, which I would like to avoid.

Having installed the sensu.noarch-0.23.2-3.el7 from the centos-opstools repo.
I bump into this error:

RUNNING HANDLER [sensu/server : restart sensu] *********************************
failed: [<IP_ADDRESS>] (item=sensu-server) => {"failed": true, "item": "sensu-server", "msg": "Job for sensu-server.service failed because the control process exited with error code. See "systemctl status sensu-server.service" and "journalctl -xe" for details.\n"}
failed: [<IP_ADDRESS>] (item=sensu-api) => {"failed": true, "item": "sensu-api", "msg": "Job for sensu-api.service failed because the control process exited with error code. See "systemctl status sensu-api.service" and "journalctl -xe" for details.\n"}

ls -l /var/run/ | grep sensu
drwxr-xr-x.  2           990 root            40 Oct 14 10:44 sensu

Executing "chown -R sensu /var/run/sensu/" colved the problem

@jbadiapa: That is not necessary playbook problem, but centos version packaging problem.

@paramite: maybe it's not a playbook error, but we need to handle it. As if it were a package dependency. IMO.

@jbadiapa, we are handling this in this PR by ensuring that we don't use the sensu package in CentOS.  This PR will explicitly remove 0.23.x and install a more recent package.

So ... I think this should be merged, right?

I have not  may explained it properly.
When I installed the sensu.noarch-0.23.2-3.el7 and running the playbook to install a correct one I got the above error.
If I remove the sensu package and execute the playbook again to install sensu I also got the above error.

@jbadiapa can you record the output of running ansible-playbook?
script -c 'ansible-playbook -i inventory playbook.yml'

And then send me/pastebin/etc the resulting typescript file?

@larsks, http://paste.openstack.org/show/586189/

The only way I could reproduce the error was:
1.- Installing availability monitoring am_hosts role on a server.
2.- Remove the sensu package
3.- Running again the installation of availability monitoring


feat: allow for disabling route matcher while still generating semantic URLs

Currently disabling a spartacus route (by assigning null to routing.routes.[routeName].paths) means also disablig generation of semantic urls for it.
However some customers may want to disable our routes definitions (to replace them with custom ones), but sill generate semating URLs, i.e. to PDP. Now it can be achived using disabled flag:
      routing: {
        routes: {
          product: {
            paths: ['product/:productCode/:name', 'product/:productCode'],
            disabled: true,
          },
        }
      }

close GH-3638

Can be merged as soon as we agree to release 1.1

Won't do.


Design review for activity feed

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are we trying to do?

I put together the activity feed div together pretty hackily in #1226  and made some guesses about how to render things, but I would love an opinion on it from someone with good design tastes and instincts. To that end, I think a quick UX once-over of the activity feed would be very helpful.

What feature or behavior is this required for?

Make the activity feed look nice!

How could we solve this issue? (Not knowing is okay!)

Insights from our UX friends!

Anything else?

Stems from #1226

Here's what it looks like currently:

Fantastic!
Would you hate me if I asked for the icons for VM and couldn't reach be different than reached? Was this a specific design decision @mebates or something we can change?
Just to make it easier for CMs to differentiate at a glance who still needs to be called.

@lwaldsc Not a specific design decision that I can recall, and that's a pretty straightforward change. Feel free to pick something you like from this set of icons here: https://getbootstrap.com/docs/3.3/components/#glyphicons

Loving this!!! and agree with @lwaldsc on the different icons. @colinxfleming maybe the envelop icon for VM and the X icon for couldn't be reached?

I would suggest using the earphone glyph for Voicemails and Could Not Reach and the comment glyph for Reached. There isn't much difference between VM and CNR as far as moving the patient along in the process (and accounting for patients we cannot leave a VM for), so I don't think they need to be differentiated.
Thoughts?

Good points! I think it would also encourage CMs to keep trying those VM patients rather than going "we left a VM; they're good."

Paging @DCAFEngineering/designers ! Knew I set those teams up for a reason.
@lwaldsc @NerdyGirl537 I'll definitely make the glyphicon change, that's straightforward enough that we can do it in #1226 imo.

Are the icons interactive? If they are just a code and not something you can click, please avoid the color purple. I would also make them smaller, OR add more line spacing between each activity item, so they don't crash into each other.

Yeah, they're just code. Let's swap them to black maybe?
More line spacing sounds great.
@serenayudon can i tag you in on these code changes?
On Mon, Sep 11, 2017, 7:05 PM Mollie Bates<EMAIL_ADDRESS>wrote:

Are the icons interactive? If they are just a code and not something you
can click, please avoid the color purple. I would also make them smaller,
OR add more line spacing between each activity item, so they don't crash
into each other.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DCAFEngineering/dcaf_case_management/issues/1232#issuecomment-328683431,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADsA9HaHyTBUDFKA_NDsTAHbItuEBOUjks5shbyzgaJpZM4PNqL_
.

50% gray should do it. If you want, you could do something more positive for a pledge sent, like a green!

So the final changes are:

change the icon styling to 50% gray for calls, green for pledge sent
Add some additional line spacing between entries (maybe an additional margin of 2-5px? and see how that looks?)

Tagging frontend, let's finish this out!

Should this just be styled based on the glyphicon classes, or do we want to add a class that defines the event type (call, pledge, etc)?

Follow your heart! Im good with either
On Tue, Oct 24, 2017, 7:53 PM Mike Chelen<EMAIL_ADDRESS>wrote:

Should this just be styled based on the glyphicon classes, or do we want
to add a class that defines the event type (call, pledge, etc)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DCAFEngineering/dcaf_case_management/issues/1232#issuecomment-339170697,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADsA9KXhNNm6YUuz5_y3Xm9sRH8ZTDcXks5svnhsgaJpZM4PNqL_
.

Ok I gave it a try, any feedback welcome!


invoke-rc.d: could not determine current runlevel

A brief description
apt get install/upgrade giving some errors and warning for some packages, I have been able to replicate this issue many times.

Expected results

Fetched 3017 kB in 31s (95.7 kB/s)
Preconfiguring packages ...
(Reading database ... 56704 files and directories currently installed.)
Preparing to unpack .../libmagickcore-6.q16-2_8%3a<IP_ADDRESS>-7ubuntu5.5_amd64.deb ...
Unpacking libmagickcore-6.q16-2:amd64 (8:<IP_ADDRESS>-7ubuntu5.5) over (8:<IP_ADDRESS>-7ubuntu5.4) ...
Preparing to unpack .../imagemagick-common_8%3a<IP_ADDRESS>-7ubuntu5.5_all.deb ...
Unpacking imagemagick-common (8:<IP_ADDRESS>-7ubuntu5.5) over (8:<IP_ADDRESS>-7ubuntu5.4) ...
Preparing to unpack .../libimage-magick-q16-perl_8%3a<IP_ADDRESS>-7ubuntu5.5_amd64.deb ...
Unpacking libimage-magick-q16-perl (8:<IP_ADDRESS>-7ubuntu5.5) over (8:<IP_ADDRESS>-7ubuntu5.4) ...
Preparing to unpack .../libimage-magick-perl_8%3a<IP_ADDRESS>-7ubuntu5.5_all.deb ...
Unpacking libimage-magick-perl (8:<IP_ADDRESS>-7ubuntu5.5) over (8:<IP_ADDRESS>-7ubuntu5.4) ...
Preparing to unpack .../linux-libc-dev_4.4.0-66.87_amd64.deb ...
Unpacking linux-libc-dev:amd64 (4.4.0-66.87) over (4.4.0-64.85) ...
Preparing to unpack .../mdadm_3.3-2ubuntu7.2_amd64.deb ...
Unpacking mdadm (3.3-2ubuntu7.2) over (3.3-2ubuntu7.1) ...
Processing triggers for libc-bin (2.23-0ubuntu5) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu16) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up imagemagick-common (8:<IP_ADDRESS>-7ubuntu5.5) ...
Setting up libmagickcore-6.q16-2:amd64 (8:<IP_ADDRESS>-7ubuntu5.5) ...
Setting up libimage-magick-q16-perl (8:<IP_ADDRESS>-7ubuntu5.5) ...
Setting up libimage-magick-perl (8:<IP_ADDRESS>-7ubuntu5.5) ...
Setting up linux-libc-dev:amd64 (4.4.0-66.87) ...
Setting up mdadm (3.3-2ubuntu7.2) ...
Processing triggers for libc-bin (2.23-0ubuntu5) ...
Processing triggers for initramfs-tools (0.122ubuntu8.8) ...

Actual results (with terminal output if applicable)
Removed some lines here........

Fetched 3017 kB in 31s (95.7 kB/s)
Preconfiguring packages ...
(Reading database ... 56704 files and directories currently installed.)
Preparing to unpack .../libmagickcore-6.q16-2_8%3a<IP_ADDRESS>-7ubuntu5.5_amd64.deb ...
Unpacking libmagickcore-6.q16-2:amd64 (8:<IP_ADDRESS>-7ubuntu5.5) over (8:<IP_ADDRESS>-7ubuntu5.4) ...
Preparing to unpack .../imagemagick-common_8%3a<IP_ADDRESS>-7ubuntu5.5_all.deb ...
Unpacking imagemagick-common (8:<IP_ADDRESS>-7ubuntu5.5) over (8:<IP_ADDRESS>-7ubuntu5.4) ...
Preparing to unpack .../libimage-magick-q16-perl_8%3a<IP_ADDRESS>-7ubuntu5.5_amd64.deb ...
Unpacking libimage-magick-q16-perl (8:<IP_ADDRESS>-7ubuntu5.5) over (8:<IP_ADDRESS>-7ubuntu5.4) ...
Preparing to unpack .../libimage-magick-perl_8%3a<IP_ADDRESS>-7ubuntu5.5_all.deb ...
Unpacking libimage-magick-perl (8:<IP_ADDRESS>-7ubuntu5.5) over (8:<IP_ADDRESS>-7ubuntu5.4) ...
Preparing to unpack .../linux-libc-dev_4.4.0-66.87_amd64.deb ...
Unpacking linux-libc-dev:amd64 (4.4.0-66.87) over (4.4.0-64.85) ...
Preparing to unpack .../mdadm_3.3-2ubuntu7.2_amd64.deb ...
invoke-rc.d: could not determine current runlevel
Unpacking mdadm (3.3-2ubuntu7.2) over (3.3-2ubuntu7.1) ...
Processing triggers for libc-bin (2.23-0ubuntu5) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu16) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up imagemagick-common (8:<IP_ADDRESS>-7ubuntu5.5) ...
Setting up libmagickcore-6.q16-2:amd64 (8:<IP_ADDRESS>-7ubuntu5.5) ...
Setting up libimage-magick-q16-perl (8:<IP_ADDRESS>-7ubuntu5.5) ...
Setting up libimage-magick-perl (8:<IP_ADDRESS>-7ubuntu5.5) ...
Setting up linux-libc-dev:amd64 (4.4.0-66.87) ...
Setting up mdadm (3.3-2ubuntu7.2) ...
W: mdadm: failed to load MD subsystem.
update-initramfs: deferring update (trigger activated)
invoke-rc.d: could not determine current runlevel
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Processing triggers for libc-bin (2.23-0ubuntu5) ...
Processing triggers for initramfs-tools (0.122ubuntu8.8) ...

Your Windows build number
Microsoft Windows [Version 10.0.15042]

Steps / All commands required to reproduce the error from a brand new installation

sudo apt-get upgrade
sudo apt-get install some_packages_name

Required packages and commands to install
Got error in upgrading these below packages:
imagemagick-common libimage-magick-perl libimage-magick-q16-perl libmagickcore-6.q16-2 linux-libc-dev mdadm

The current init system is not at all sophisticated and doesn't use runlevels.

Try this:
sudo su
export RUNLEVEL=1
apt-get <whatever>

You are going to have no joy with mdadm though, for reasons that go beyond runlevels.

Had the same issue. No changes on this?

Still having the problem. Exporting RUNLEVEL didn't make a difference.

This is still an issue.  Can we get some sort of a resolution? This particular issue has been open for a year now.

@josh-yoder-vive - It is my understanding that this isn't causing any issues beyond a warning when running apt commands.  Is that not the case?

Just warnings, along the lines of this.
The RUNLEVEL environment hack (which gets picked up by /sbin/runlevel) doesn't work because current versions of apt clobber the environment and don't actually run as root. There's probably some way to force the RUNLEVEL variable down apt's throat but I didn't take the time to look. People who feel strongly about it can do:
sudo bash -c "echo '[1] [00049] [~~  ] [runlevel] [~           ] [4.4.0-17115-Micoroso] [<IP_ADDRESS>        ] [Wed Feb 28 13:27:14 2018 STD]' | utmpdump -r > /var/run/utmp"

That will kill the runlevel warning. You'll still get "start and stop actions are no longer supported". Because they aren't. Some people can't be pleased.

I had this issue when updating mysql-server. I resolved my issue like this
`
sudo su
apt-get remove --purge 'mysql*'
apt-get autoremove
apt-get autoclean
rm -f /etc/mysql /var/lib/mysql
apt-get install mysql-server
`

I tried to purge MySQL directories and reinstall it, however when I do the re-install, I get the following:
mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2 - No such file or directory)                                 mysqld: [ERROR] Fatal error in defaults handling. Program aborted!                                                      mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2 - No such file or directory)                                 mysqld: [ERROR] Fatal error in defaults handling. Program aborted!

Clean enabling of the WSL and install of Ubuntu (16.04 as from the Microsoft Store's "Run Linux on Windows" page), Windows Version 1803, Build 17134.48.
Got this issue for uuid-runtime, lxd, lxcfs, mdadm, apport seems to have a related issue because it didn't have permission to create a required file the first time invoke-rc.d failed.
Other packages (any using invoke-rc.d, really) may have failed in this manner. Unsure if error or mere warning.
From my understanding this is due to an underlying issue in the runlevel system, as only Unix systems have runlevels. Can it get some love? It's been a year since the original issue has been filed and the runlevel is important for automatic jobs (on levels 1-5) and cleanup tasks (on levels 0 and 6). I understand that runlevel 5 may be difficult to implement due to it being 3 + a display manager, but the WSL already doesn't support GUI apps so I think not supporting runlevel 5 would be fine.

Runlevels are deprecated, so no, they won't be implemented or even stubbed out.
We're more likely to see a transition from WSL-init to systemd.

@fpqc What? Where'd you get that from/can you elaborate? systemd can still act on runlevels, exposed via "targets". Unless I am fundamentally mistaken.
Not to mention invoke-rc.d, of Ubuntu 16.04 (which is supported until April 2021), apparently requires them. As well as potentially other cli packages.
Even if they are deprecated completely as of 18.04 (I am unaware, haven't seen such and haven't tried 18.04 out), are we supposed to just wait until 2021 when 16.04 is EOL for third parties and us to play catchup?

No, the current package on the Windows Store offered by Canonical is iirc 18.04. Also, systemd-runlevel support is through the sysvcompat module of systemd. It works OOB as long as systemd is running.
Classic runlevels are managed by the init system, so the easy answer is to support systemd.

When searching "Ubuntu" on the appstore I get the recommended "Run linux on windows". Those 5 recommended packages are Ubuntu (16.04.04 LTS as reported from lsb_release -a, openSUSE Leap 42, SUSE Linux Enterprise Server 12, Debian GNU / Linux, and Kali Linux. I am unaware of the versions of the other packages as I do not have them installed nor are they listed from that page.
Regardless, 16.04 is meant to have support until 2021. My Ubuntu 16.04 VM through VMWare uses systemd, and has access to runlevels.
Furthermore systemd still manages and has access to runlevels out of the box. They are renamed to their intentions (ex graphical.target for 5) and aliased via runlevel#.target.
The concept of a runlevel is not limited to any one init system. Rather they are Linux/Unix concept which every linux system uses. 0, 1, and 6 are the standard runlevels. 2-5 vary per linux distribution, but generally contain a single user mode, a multi user mode, and multi user mode + concept(s) (ex networking, a display manager). The user's init system uses runlevels to determine what jobs to start, among other tasks.
Again, runlevels are a fundamental concept to linux, and I have seen no deprecation as you claim. Again, I haven't checker on an 18.04 VM nor any other OS, but as 16.04 is meant to be supported until 2021, so should runlevels, on 16.04 at minimum (again, haven't checked 18.04/other systems for the depreciation of runlevels, but I've seen no such report).

Rather they are Linux/Unix concept which every linux system uses

That's plain incorrect, for what it is worth. The Linux kernel does not know or care about runlevels. The LG Smart TV I picked up at Costco last week, which runs Linux, doesn't have a /var/run/utmp. Because why would it.
Ubuntu's systemd does update /var/run/utmp on startup for the benefit of some packages. WSL's /init does not. Doing so would be trivial to add as a feature (for those that are of the option a #2530 death march is a good idea). Or, as @fpqc already implied, your ask is dupe #994. Or you can just update /var/run/utmp yourself. Bonne chance.

Fine, redacted-- most, standard linux systems use. Ya know, not TVs and the like. Sue me^(pls don't).
Then I am in support for both issues you linked.
And yeah, I can definitely update the runlevel myself but I'd like something so fundamental to "most standard" linux distros (and by your words, trivial to add, haven't taken a look at the source) to be done for me.

The way I fixed this:
/etc/init.d/ebtables
has
case "$1" in   start)         [ "$EBTABLES_LOAD_ON_START" = "yes" ] && load         ;;   stop)         [ "$EBTABLES_SAVE_ON_STOP" = "yes" ] && save         clear         ;;
Just comment out the actions taken by stop) e.g.:
  stop)         # [ "$EBTABLES_SAVE_ON_STOP" = "yes" ] && save         # clear         ;;
and do your
sudo apt upgrade or purge or whatever. Note that after the upgrade the init script will be redeployed so you will face the same issue down the line.
The problem comes from the install/remove scripts trying to do "service ebtables stop" and failing. You can see this by trying to stop ebtables manually.

edit: @marchom posted a workaround as I was typing this in :)
Hit this one just now when updating packages on Ubuntu 18.04 via Ansible
Relevant playbook task:
- name: Upgrade all packages
  apt:
    upgrade: yes
    autoclean: yes
    autoremove: yes

Which calls the following shell command:
sudo /usr/bin/apt-get upgrade --with-new-pkgs --auto-remove

Which fails with:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  ebtables
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
Need to get 0 B/79.9 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 84358 files and directories currently installed.)
Preparing to unpack .../ebtables_<IP_ADDRESS>-3.5ubuntu<IP_ADDRESS>_amd64.deb ...
invoke-rc.d: could not determine current runlevel
 * Error: insufficient privileges to access the ebtables rulesets.
invoke-rc.d: initscript ebtables, action "stop" failed.
dpkg: warning: old ebtables package pre-removal script subprocess returned error exit status 1
dpkg: trying script from the new package instead ...
invoke-rc.d: could not determine current runlevel
 * Error: insufficient privileges to access the ebtables rulesets.
invoke-rc.d: initscript ebtables, action "stop" failed.
dpkg: error processing archive /var/cache/apt/archives/ebtables_<IP_ADDRESS>-3.5ubuntu<IP_ADDRESS>_amd64.deb (--unpack):
 new ebtables package pre-removal script subprocess returned error exit status 1
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
invoke-rc.d: could not determine current runlevel
Errors were encountered while processing:
 /var/cache/apt/archives/ebtables_<IP_ADDRESS>-3.5ubuntu<IP_ADDRESS>_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Looks like ebtables was updated 2 hours ago (https://launchpad.net/ubuntu/+source/ebtables/<IP_ADDRESS>-3.5ubuntu<IP_ADDRESS>), and this is causing failures in WSL

About the same time as noelbundick and marchom found a solution, I used an alternative fix from https://github.com/Microsoft/WSL/issues/143#issuecomment-209075558 which I found linked to from a japanese bbs.
echo "Implementing udev workaround (https://github.com/Microsoft/WSL/issues/143#issuecomment-209072634)" >&2
sudo tee /usr/sbin/policy-rc.d > /dev/null <<EOF
#!/bin/sh
exit 101
EOF
sudo chmod +x /usr/sbin/policy-rc.d
sudo dpkg-divert --local --rename --add /sbin/initctl
sudo ln -fs /bin/true /sbin/initctl

There are parts of the script here and in the above post that get around different issues related to this class of problems.

Hi
I just marked ebtables as holded, so apt won't try to update it :
$ sudo apt-mark hold ebtables
ebtables set on hold.

Same here, got hit with this issue doing apt-get update && apt-get upgrade just after finishing installing and setting up Ubuntu 18.04.
`Preparing to unpack .../ebtables_<IP_ADDRESS>-3.5ubuntu<IP_ADDRESS>_amd64.deb ...
invoke-rc.d: could not determine current runlevel

Error: insufficient privileges to access the ebtables rulesets.
invoke-rc.d: initscript ebtables, action "stop" failed.
dpkg: warning: old ebtables package pre-removal script subprocess returned error exit status 1
dpkg: trying script from the new package instead ...
invoke-rc.d: could not determine current runlevel
Error: insufficient privileges to access the ebtables rulesets.
invoke-rc.d: initscript ebtables, action "stop" failed.
dpkg: error processing archive /var/cache/apt/archives/ebtables_<IP_ADDRESS>-3.5ubuntu<IP_ADDRESS>_amd64.deb (--unpack):
new ebtables package pre-removal script subprocess returned error exit status 1
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
invoke-rc.d: could not determine current runlevel
Errors were encountered while processing:
/var/cache/apt/archives/ebtables_<IP_ADDRESS>-3.5ubuntu<IP_ADDRESS>_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)`

@13steinj Both 16.04 and 18.04 are on the store, but only 16.04 is on the WSL landing page. See #3249.
This is an upstream bug in Ubuntu 18.04, it is not isolated to Ubuntu for WSL.
Here is the upstream bug report. It is confirmed and marked high.

I was looking at the upgrade apt was attempting:

$ apt-get -V -s upgrade
NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
ebtables (<IP_ADDRESS>-3.5ubuntu2 => <IP_ADDRESS>-3.5ubuntu<IP_ADDRESS>)
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Inst ebtables [<IP_ADDRESS>-3.5ubuntu2] (<IP_ADDRESS>-3.5ubuntu<IP_ADDRESS> Ubuntu:18.04/bionic-updates [amd64])
Conf ebtables (<IP_ADDRESS>-3.5ubuntu<IP_ADDRESS> Ubuntu:18.04/bionic-updates [amd64])

Here is the Debian changelog showing the <IP_ADDRESS>-3.5 update.
I have reported the bug upstream in Ubuntu and linked back to here. If you would be so kind as to confirm it there that would get it elevated in the Ubuntu system.

@sirredbeard all due respect I do not care for that issue. It's minor and...well of no importance to me. My issue is with the fact that WSL doesn't support something as fundamental as runlevels, which is supposedly trivial to support (again, I am unaware how trivial this is, just parroting the claim of another user). That is the underlying cause of ebtables having an issue, many packages in 16.04 having an issue, and can cause it's own slew of problems for custom scripts that are being developed.

@13steinj If you search for Ubuntu 18.04 in the Microsoft Store you can find it that way. There are a lot of things missing from WSL that you would find in a typical Linux distro. If you need a typical Linux distro, there are many excellent ones to chose from. There is also Docker and VirtualBox. WSL was intended to be used for programmers and developers to supplement their Windows workflow, so there was little need for runtime support. As WSL makes it way into Windows Server and SQL Server 2017 runs on Linux, it's possible we will see further development on that. Given how an init system would slow down launching the shell, all the issues that systemd can cause, the lack of support for sysvinit outside niche distros, the abandonment of Upstart, and the relative immaturity of OpenRC, I think going without an init for now was probably a smart move, at least until Microsoft saw what the users actually did with WSL. If possible, please confirm the bug reported upstream on Ubuntu's bug reporter so it will get fixed quicker. Thanks.

@sirredbeard all of what you said is absolutely true. However one part is paradoxical:

WSL was intended to be used for programmers and developers to supplement their Windows workflow, so there was little need for runtime support.

I am a developer. Who in their development workflow, relies on the init system.
I am undoubtedly not the only one who does this. And many packages rely on it as well.
In this way WSL fails in its goal. It is undoubtedly a great tool, but it is also not one that I can use in its current state. It is worse than the VM I was already using. I was really hoping that WSL will be a proper replacement because that seems to be the goal that it set out to do. However it has failed me.
That said, I can not confirm the ebtables issue at this time, nor will I make a confirmation on the Ubuntu tracker. And the reason I won't is simply this: it's not an ebtables bug! The software is meant to run on Ubuntu and makes perfectly sane assumptions about its environment.
Trying to claim fault on them is like me making a new linux distribution that is supposed to be debian compatible yet only allow it to install RPM packages, and some RPM package fails to work on my distro because it assumes the environment is Red Hat.
If the WSL team decided (and I agree that it was a reasonable decision at the time) to not deal with a proper init system, sure, fine. But their wrong does not get transferred to the Ubuntu team nor should the Ubuntu team have to spend their time finding some strange work around because the WSL does fundamental linux concepts incorrectly. This is up to the WSL team to fix. Even if the ebtables maintainers resolve this issue this time, it is only a matter of time before it happens again.
A proper init system needs to be implemented-- period.

Same problem here. Just marked this package on hold.

Fellas, I understand the frustration. If you want MS to support systemd (which is what you want), please please vote up the existing uservoice. It only has like 200 votes.

@13steinj
If you need a full init system then WSL is probably not for you at this time. I mentioned several alternatives and the reasons to believe that there may be a solution for you in the future. There are several other key features to implement in WSL as well, Microsoft seems to be adding them fairly quickly and doing a pretty stable job overall. Let's not forget that this is Microsoft implementing Linux on Windows. I don't see Apple implementing native cross-platform apps. Google is just getting around to it on one device which already ran Linux, it's not the technical accomplishment WSL is.
As for the upstream bug report, Ubuntu packages it's distro and officially supports ~8 different containerized platforms with special customizations to run well on each, including Docker, Azure, AWS, and WSL. Microsoft cannot make this change to this package, Canonical has to. Canonical cannot fix this for the WSL image unless they know about the bug. You can be sour Microsoft hasn't implemented an init system yet but in the mean time I am going to try to get this bug fixed by letting Canonical know. Yes, in an ideal world this wouldn't be an issue, but this is an evolving project. If you want boring and tested, I recommend CentOS.
You complained about Ubuntu being confusingly listed Microsoft Store and I pointed out that was an existing bug, #3249. In response you stated "I do not care for that issue. It's minor and...well of no importance to me". Then why did you complain about it on GitHub? I then suggested you help get the bug fixed in the upstream Ubuntu container by clicking a single button, which you similarly dismissed. I have always believed if you want things to happen in open source to you have to write it yourself or be patient, file bug reports, and wait until someone else writes/fixes it. That's the give and take of open source.

Same problem here.

@sirredbeard, it is absolutely true that the WSL does not satisfy my needs at this time. And I am using one of the alternatives you mentioned if you bothered to read my comment. I have no problem with Microsoft and give them full props for the implementation they have thus far. However, this is fundamental to a wide variety of linux distributions. Without an init system, the WSL becomes useless for a wide variety of developers and extremely annoying for package maintainers.
I have seen no such report or blog post or notice that Canonical and the Ubuntu team officially support WSL, nor can I find one. If you link such notice, I will be more than happy to make an upstream confirmation to the bug report. Until then, I do not see this as an issue they have to care about because otherwise they don't have an issue-- WSL does. And that issue, is its lack of a proper init system, and no proper mock/polyfill to the runlevel system.
I did not complain about the confusing listing. All I did was mention that 16.04 was the version touted on the app store. And in my opinion, for good reason. It's still supported and more mature. Lots of developers stay on older versions of language VM runtimes and operating systems for just this reason. Hell, I know some people that are still on Ubuntu 14.04. You are absolutely right anout the give and take of open source, but these are not things I specifically want to happen. I would however like it that all available versions are listed on that page, however I don't really care for that specifically.

https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1774120

As of this afternoon a patch has been sponsored into Ubuntu's devel release Cosmic and will filter down to Bionic and then get backported to Xenial.
https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1774120/comments/8

@therealkenc Can you mark this bug as confirmed and that a patch is on the way? In the mean time we can point people towards @marchom's workaround above.

That workaround is narrowly limited to people's woes with 18.04, which is now in people's face, bumping this year old issue. The very rough guidance (if there is such a thing), based only on observation, is stuff that hangs out like this with no tag is nominally by-design or feature+backlog. I don't work at MSFT; whether someone is looking at it or not I haven't the slightest. But given it is now in people's face I would bet a Internet nickle they are.
The correct work-around for this remains setting up /var/run/utmp so WSL thinks it has a runlevel.

@13steinj
Canonical supports Ubuntu on WSL similar to their support for Ubuntu on other container platforms, like Docker. Canonical partnered with Microsoft to bring Ubuntu to WSL. * Canonical are the ones who submit container images to the Microsoft Store using the reference template. It's not like Microsoft just downloads the ISO and puts it in the store themselves. Canonical also have published documentation on their site for WSL. * * Ubuntu and Microsoft are official corporate partners, not just on WSL but on Azure as well. * If you want to learn more about how Canonical's teams supports images of Ubuntu for several different platforms, I recommend s11e08  of the Ubuntu podcast.
By the way, from the bug report discussion it appears the actual bug is in how ebtables, called by ebtables.init, needlessly returns an error message. *.  WSL fully supports EPROTONOSUPPORT socket() calls but ebtables still returns a permission error. This causes the error to be returned when the stop script is called as part of the package upgrade. *. The patch is to fix the script's handling of the permission error. * The actual long-term solution is to patch communications.c in ebtables.
So turns out lack of a init wasn't the issue and we could only find that out by filing a bug report and working together. Hooray open source.

EPROTONOSUPPORT has been supported in WSL since last year. * and appears to work well in other programs. So I have filed a bug report upstream with the netfilter team, who inherited ebtables, regarding the handling of EPROTONOSUPPORT errors in ebtables. Contrary to the error message, I do not believe it's a permissions error because I can reproduce the error as root. The patches to the upgrade script (to disregard the error) by Canonical to Ubuntu Cosmic will trickle down to Bionic long before any patch by the netfilter team gets pushed to Debian then to Cosmic then Bionic, but we now have several viable short-term work arounds for WSL above, a medium-term workaround coming down from Ubuntu, and a long-term solution started.

sockfd = socket(AF_INET, SOCK_RAW, PF_INET);

Yeah I should have stated that explicitly in my last message. We have two unrelated fails in Daniel's original follow-up post and that is wreaking havoc on this issue topic. Almost to the point it may not recover.
...
invoke-rc.d: could not determine current runlevel
...
 * Error: insufficient privileges to access the ebtables rulesets.

socket(AF_INET, SOCK_RAW, ...) is #717 #1383 #3216 and many friends. It has nothing to do with blog on AF_UNIX you cite.

Yes you are right. It is not a general issue with opening sockets, as I assumed, but a specific issue that WSL does not support kernel interfaces Linux iptables. This effectively means that ebtables is currently useless because you can't really do any filtering or bridging on the kernel level.
In that sense I would probably just sudo apt purge ebtables

In that sense I, personally, would probably just sudo apt purge ebtables.

If that's a workable solution, so much the better. I am not entirely sure why/how etables is being invited to the party in 18.04. There would have been more chatter if it was a common problem previously (19 upvotes on your workaround).
Closing this issue as dupe #573 to try to get the runlevel fail (see issue title) back on track. Thank-you very much @marchom and @sirredbeard for following the etables fail and for the suggested workarounds. If the upstream package gets tweaked to be more tolerant of WSL that's double plus good.

I solved this issue by this:
sudo mv /var/lib/dpkg/info/{packagename}.* /tmp/
sudo dpkg --remove --force-remove-reinstreq {packagename}
sudo apt-get remove {packagename}
sudo apt-get autoremove && sudo apt-get autoclean

Maybe it'll help somebody.

I work on an extremely straight-forward "Enterprise Java" project.  Essentially:

Node for UI (with all the trappings)
Spring Boot for the API server
Postgres for the database

Now, in fact, it works.  Bravo!  However, it complains about run level with postgres install, and so per team norms, I cannot profer this setup to my other devs.  Resolving runlevel would address this.

@caseyallen386 @georgique
I'm having similar problems. Casey, you basically just purged and reinstalled? Do you know why that fixed the issue but didn't for George? I have tried uninstalling and reinstalling multiple times and mysql keeps not working, and I have several times gotten errors codes like George's. I have just now purged everything as thoroughly as I know how, and then double checked by going through ever major folder at / and rm -r any mysql, php, or apache files I could find, and then I reinstalled, this time using sudo apt install -y lamp-server^ as per this tutorials here: https://hellojason.net/blog/how-to-setup-wordpress-locally-on-windows-subsystem-for-linux/
I'm fixing to test if everything works but while doing the LAMP install I noticed the reoccuring error code so I searched it and found this page.
If either of you know why this is happening or how it can be fixed, either the general difficulties I'm having getting MySQL to work on WSL or the specific issues brought up by this thread and related by George, I would love to know.

same here using ubuntu wsl 16.04 LTS
mio@MiBookAir:~$ sudo apt-get install blueman
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  blueman
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B/1,673 kB of archives.
After this operation, 4,948 kB of additional disk space will be used.
Selecting previously unselected package blueman.
(Reading database ... 180283 files and directories currently installed.)
Preparing to unpack .../blueman_2.0.4-1ubuntu2_amd64.deb ...
Unpacking blueman (2.0.4-1ubuntu2) ...
Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5.2) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu4.1) ...
Setting up blueman (2.0.4-1ubuntu2) ...
invoke-rc.d: could not determine current runlevel
 * Reloading system message bus config...
Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_so
cket: No such file or directory
invoke-rc.d: initscript dbus, action "reload" failed.
dpkg: error processing package blueman (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 blueman
E: Sub-process /usr/bin/dpkg returned an error code (1) ```

Tried everything on this thread multiple times without success:
root@PLIL19008WN:/# apt-get install mysql-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libaio1 libcgi-fast-perl libcgi-pm-perl libencode-locale-perl libevent-core-2.1-6 libfcgi-perl libhtml-parser-perl
  libhtml-tagset-perl libhtml-template-perl libhttp-date-perl libhttp-message-perl libio-html-perl liblwp-mediatypes-perl
  libtimedate-perl liburi-perl mysql-client-5.7 mysql-client-core-5.7 mysql-common mysql-server-5.7 mysql-server-core-5.7
Suggested packages:
  libdata-dump-perl libipc-sharedcache-perl libwww-perl mailx tinyca
The following NEW packages will be installed:
  libaio1 libcgi-fast-perl libcgi-pm-perl libencode-locale-perl libevent-core-2.1-6 libfcgi-perl libhtml-parser-perl
  libhtml-tagset-perl libhtml-template-perl libhttp-date-perl libhttp-message-perl libio-html-perl liblwp-mediatypes-perl
  libtimedate-perl liburi-perl mysql-client-5.7 mysql-client-core-5.7 mysql-common mysql-server mysql-server-5.7
  mysql-server-core-5.7
0 upgraded, 21 newly installed, 0 to remove and 172 not upgraded.
Need to get 0 B/21.0 MB of archives.
After this operation, 162 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Preconfiguring packages ...
Selecting previously unselected package mysql-common.
(Reading database ... 29266 files and directories currently installed.)
Preparing to unpack .../0-mysql-common_5.8+1.0.4_all.deb ...
Unpacking mysql-common (5.8+1.0.4) ...
Selecting previously unselected package libaio1:amd64.
Preparing to unpack .../1-libaio1_0.3.110-5_amd64.deb ...
Unpacking libaio1:amd64 (0.3.110-5) ...
Selecting previously unselected package mysql-client-core-5.7.
Preparing to unpack .../2-mysql-client-core-5.7_5.7.25-0ubuntu<IP_ADDRESS>_amd64.deb ...
Unpacking mysql-client-core-5.7 (5.7.25-0ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package mysql-client-5.7.
Preparing to unpack .../3-mysql-client-5.7_5.7.25-0ubuntu<IP_ADDRESS>_amd64.deb ...
Unpacking mysql-client-5.7 (5.7.25-0ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package mysql-server-core-5.7.
Preparing to unpack .../4-mysql-server-core-5.7_5.7.25-0ubuntu<IP_ADDRESS>_amd64.deb ...
Unpacking mysql-server-core-5.7 (5.7.25-0ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package libevent-core-2.1-6:amd64.
Preparing to unpack .../5-libevent-core-2.1-6_2.1.8-stable-4build1_amd64.deb ...
Unpacking libevent-core-2.1-6:amd64 (2.1.8-stable-4build1) ...
Setting up mysql-common (5.8+1.0.4) ...
update-alternatives: using /etc/mysql/my.cnf.fallback to provide /etc/mysql/my.cnf (my.cnf) in auto mode
Selecting previously unselected package mysql-server-5.7.
(Reading database ... 29434 files and directories currently installed.)
Preparing to unpack .../00-mysql-server-5.7_5.7.25-0ubuntu<IP_ADDRESS>_amd64.deb ...
Unpacking mysql-server-5.7 (5.7.25-0ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package libhtml-tagset-perl.
Preparing to unpack .../01-libhtml-tagset-perl_3.20-3_all.deb ...
Unpacking libhtml-tagset-perl (3.20-3) ...
Selecting previously unselected package liburi-perl.
Preparing to unpack .../02-liburi-perl_1.73-1_all.deb ...
Unpacking liburi-perl (1.73-1) ...
Selecting previously unselected package libhtml-parser-perl.
Preparing to unpack .../03-libhtml-parser-perl_3.72-3build1_amd64.deb ...
Unpacking libhtml-parser-perl (3.72-3build1) ...
Selecting previously unselected package libcgi-pm-perl.
Preparing to unpack .../04-libcgi-pm-perl_4.38-1_all.deb ...
Unpacking libcgi-pm-perl (4.38-1) ...
Selecting previously unselected package libfcgi-perl.
Preparing to unpack .../05-libfcgi-perl_0.78-2build1_amd64.deb ...
Unpacking libfcgi-perl (0.78-2build1) ...
Selecting previously unselected package libcgi-fast-perl.
Preparing to unpack .../06-libcgi-fast-perl_1%3a2.13-1_all.deb ...
Unpacking libcgi-fast-perl (1:2.13-1) ...
Selecting previously unselected package libencode-locale-perl.
Preparing to unpack .../07-libencode-locale-perl_1.05-1_all.deb ...
Unpacking libencode-locale-perl (1.05-1) ...
Selecting previously unselected package libhtml-template-perl.
Preparing to unpack .../08-libhtml-template-perl_2.97-1_all.deb ...
Unpacking libhtml-template-perl (2.97-1) ...
Selecting previously unselected package libtimedate-perl.
Preparing to unpack .../09-libtimedate-perl_2.3000-2_all.deb ...
Unpacking libtimedate-perl (2.3000-2) ...
Selecting previously unselected package libhttp-date-perl.
Preparing to unpack .../10-libhttp-date-perl_6.02-1_all.deb ...
Unpacking libhttp-date-perl (6.02-1) ...
Selecting previously unselected package libio-html-perl.
Preparing to unpack .../11-libio-html-perl_1.001-1_all.deb ...
Unpacking libio-html-perl (1.001-1) ...
Selecting previously unselected package liblwp-mediatypes-perl.
Preparing to unpack .../12-liblwp-mediatypes-perl_6.02-1_all.deb ...
Unpacking liblwp-mediatypes-perl (6.02-1) ...
Selecting previously unselected package libhttp-message-perl.
Preparing to unpack .../13-libhttp-message-perl_6.14-1_all.deb ...
Unpacking libhttp-message-perl (6.14-1) ...
Selecting previously unselected package mysql-server.
Preparing to unpack .../14-mysql-server_5.7.25-0ubuntu<IP_ADDRESS>_all.deb ...
Unpacking mysql-server (5.7.25-0ubuntu<IP_ADDRESS>) ...
Setting up libhtml-tagset-perl (3.20-3) ...
Setting up libevent-core-2.1-6:amd64 (2.1.8-stable-4build1) ...
Processing triggers for ureadahead (0.100.0-20) ...
Setting up libencode-locale-perl (1.05-1) ...
Setting up libtimedate-perl (2.3000-2) ...
Setting up libio-html-perl (1.001-1) ...
Setting up liblwp-mediatypes-perl (6.02-1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up libaio1:amd64 (0.3.110-5) ...
Setting up liburi-perl (1.73-1) ...
Processing triggers for systemd (237-3ubuntu10.3) ...
Setting up libhtml-parser-perl (3.72-3build1) ...
Setting up libcgi-pm-perl (4.38-1) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up mysql-client-core-5.7 (5.7.25-0ubuntu<IP_ADDRESS>) ...
Setting up libfcgi-perl (0.78-2build1) ...
Setting up libhttp-date-perl (6.02-1) ...
Setting up libhtml-template-perl (2.97-1) ...
Setting up mysql-server-core-5.7 (5.7.25-0ubuntu<IP_ADDRESS>) ...
Setting up libcgi-fast-perl (1:2.13-1) ...
Setting up libhttp-message-perl (6.14-1) ...
Setting up mysql-client-5.7 (5.7.25-0ubuntu<IP_ADDRESS>) ...
Setting up mysql-server-5.7 (5.7.25-0ubuntu<IP_ADDRESS>) ...
invoke-rc.d: could not determine current runlevel
 * Stopping MySQL database server mysqld                                                                                [ OK ]
update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode
Renaming removed key_buffer and myisam-recover options (if present)
Cannot open /proc/net/unix: No such file or directory
Cannot stat file /proc/1/fd/5: Operation not permitted
Cannot stat file /proc/3/fd/7: Operation not permitted
dpkg: error processing package mysql-server-5.7 (--configure):
 installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-5.7; however:
  Package mysql-server-5.7 is not configured yet.

dpkg: error processing package mysql-server (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.27-3ubuntu1) ...
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (237-3ubuntu10.3) ...
Errors were encountered while processing:
 mysql-server-5.7
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

I found the same problem as @yairEO, did you find a solution?

@JulioV: for me @DzeryCZ's solution
sudo mv /var/lib/dpkg/info/{packagename}.* /tmp/
sudo dpkg --remove --force-remove-reinstreq {packagename}
sudo apt-get remove {packagename}
sudo apt-get autoremove && sudo apt-get autoclean

didn't work, just ran into invoke-rc.d: could not determine current runlevel when installing again, but
@caseyallen386's solution did work:
sudo su
apt-get remove --purge 'mysql*'
apt-get autoremove
apt-get autoclean
rm -f /etc/mysql /var/lib/mysql
apt-get install mysql-server

In case of mysql-server just make sure to back up (mysqldump -u root -p --all-databases > all_databases.sql) the databases and then restore them afterwards (mysql -u root -p < all_databases.sql). When mysql-server wouldn't start up due to the runlevel error, I just rebooted the PC and then was able to start it and back up the databases.

@caseyallen386's solution also worked for me with reinstalling docker:
sudo su
apt-get remove --purge docker-ce docker-ce-cli containerd.io
apt-get autoremove
apt-get autoclean
rm -rf /etc/docker /var/lib/docker
apt-get install docker-ce docker-ce-cli containerd.io

same problem and the solutions above can not fix the problem...

Having same issue as @yairEO and tried out his solution BUT could not fix anything. Still getting the same invoke-rc.d: could not determine current runlevel issue! :sob:

Same issue with me. Unable to install mysql-server or mariadb-server on wsl 2 ubuntu or debian. Have tried multiple times.

See https://github.com/microsoft/WSL/issues/1332#issuecomment-628827633

Problem could be because your script is trying to use invoke-rc.d (which doesn't work because there are no runlevels in a docker container) before trying the service command (which will work).
So change the if conditions in the script or the lazy way is make it look for a non-existent path so it will use the service command. eg:
if [ -x /xxxusr/sbin/invoke-rc.d ]; then
/usr/sbin/invoke-rc.d $OMSAGENT_WS start
elif [ -x /sbin/service ]; then
/sbin/service $OMSAGENT_WS start

Hello everyone,
For me enabling systemd on WSL2 has resolved the issue. There is even a wrapped up version of the manipulation.
Thanks to the author.

I had a healthy system on which
$ ls -l /sbin/runlevel
lrwxrwxrwx 1 root root 14 Apr 28 09:03 /sbin/runlevel -> /bin/systemctl
I had a broken system where apt upgrade of mysql complained about being unable to determine the current runlevel because /sbin/runlevel was missing:
/usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found
Providing the symlink made the problem go away.
YMMV.

I had this issue when updating mysql-server. I resolved my issue like this
`
sudo su
apt-get remove --purge 'mysql*'
apt-get autoremove
apt-get autoclean
rm -f /etc/mysql /var/lib/mysql
apt-get install mysql-server
`

This worked for me, thanks! It did prompt for setting a db password for the user root, i just hit enter, not sure if that was a good idea....

What's the current status of this issue? Because the last time I was here I was basically told "no it's not a WSL issue, it has to be changed in the relevant upstream package repo".
But it seems as more and more packages are having this same issue.

The current status of this issue ("invoke-rc.d: could not determine current runlevel") is it is closed duplicative #573.

Had the same issue with couchdb. Tried everything - remove, purge, etc and kept hitting invoke-rc.d: could not determine current runlevel
The only thing that worked perfectly is @marchom's https://github.com/microsoft/WSL/issues/1761#issuecomment-392575807


Allow the user to login to multiple accounts at once

We are explicitly not trying to do this at this time. The answer for users is to open multiple tabs.


Colors are dark when normals are missing

Bevy version
0.12.0
What you did
Add two triangles to the scene. One of them with proper normals, and another without.
use bevy::app::App;
use bevy::app::Startup;
use bevy::prelude::*;
use bevy::render::mesh::Indices;
use bevy::render::mesh::PrimitiveTopology;

fn setup(
    mut commands: Commands,
    mut materials: ResMut<Assets<StandardMaterial>>,
    mut meshes: ResMut<Assets<Mesh>>,
) {
    commands.spawn(Camera3dBundle {
        transform: Transform::from_xyz(3.0, 3.0, 3.0).looking_at(Vec3::new(0., 0., 0.), Vec3::Z),
        ..default()
    });

    commands.spawn(DirectionalLightBundle {
        transform: Transform::from_xyz(1., 1., 1.).looking_at(Vec3::ZERO, Vec3::Z),
        ..DirectionalLightBundle::default()
    });

    // Proper triangle with normals.

    let mut mesh = Mesh::new(PrimitiveTopology::TriangleList);
    mesh.insert_attribute(
        Mesh::ATTRIBUTE_POSITION,
        vec![
            Vec3::new(0., 0., 0.),
            Vec3::new(1., 0., 0.),
            Vec3::new(1., 1., 0.),
        ],
    );
    mesh.insert_attribute(Mesh::ATTRIBUTE_NORMAL, vec![Vec3::Z, Vec3::Z, Vec3::Z]);
    mesh.set_indices(Some(Indices::U32(vec![0, 1, 2])));

    commands.spawn(PbrBundle {
        mesh: meshes.add(mesh),
        material: materials.add(Color::BLUE.into()),
        ..Default::default()
    });

    // Triangle without normals.

    let mut mesh = Mesh::new(PrimitiveTopology::TriangleList);
    mesh.insert_attribute(
        Mesh::ATTRIBUTE_POSITION,
        vec![
            Vec3::new(0., 0., 0.),
            Vec3::new(-1., -1., 0.),
            Vec3::new(0., -1., 0.),
        ],
    );
    // Skip normals.
    mesh.set_indices(Some(Indices::U32(vec![0, 1, 2])));

    commands.spawn(PbrBundle {
        mesh: meshes.add(mesh),
        material: materials.add(Color::GREEN.into()),
        ..Default::default()
    });
}

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_systems(Startup, setup)
        .run();
}

What went wrong
Triangle with normals is shown lit, and triangle without normals is very dark.
I'm not sure if this is a bug or not, but this is somewhat non-trivial to deal with when learning bevy. Not sure what should be proper fix:

show triangle without normals as fully lit
show a warning in console
compute default normals
render something over the triangle like checkerboard to highlight the possible error
close this issue because it works as expected (and maybe explain it somewhere in the documentation)

Additional information

I don't think the current behavior requires change.
Maybe a debug only warning, or a warning only if the material is a StandardMaterial since other custom materials could have their own shaders that don't require defined normals.
A note in the documentation couldn't hurt.


cannnot make mysql2.so on Web App Ruby2.6

I created Web App based on  Ruby 2.6 for Linux.
And I pushed a simple Rails6 application to local git on Web App and automatically deployed and normally finished.
the application is ...

Rails6 new application (--skip-yarn --skip-webpack-install --skip-coffee --skip-javascript --database=mysql)
use MySQL database (on Azure)
use 1table (just scaffold user table)

I accessed the rails6 app page, the below error occured.
2019-09-10T10:01:33.647540873Z /tmp/bundle/gems/activesupport-6.0.0/lib/active_support/dependencies.rb:325:in `require': libmariadbclient.so.18: cannot open shared object file: No such file or directory - /tmp/bundle/gems/mysql2-0.5.2/lib/mysql2/mysql2.so (LoadError)
2019-09-10T10:01:33.651693390Z     from /tmp/bundle/gems/activesupport-6.0.0/lib/active_support/dependencies.rb:325:in `block in require'
2019-09-10T10:01:33.651980691Z     from /tmp/bundle/gems/activesupport-6.0.0/lib/active_support/dependencies.rb:291:in `load_dependency'
2019-09-10T10:01:33.651993691Z     from /tmp/bundle/gems/activesupport-6.0.0/lib/active_support/dependencies.rb:325:in `require'
2019-09-10T10:01:33.651998591Z     from /tmp/bundle/gems/mysql2-0.5.2/lib/mysql2.rb:33:in `'
2019-09-10T10:01:33.652712294Z     from /usr/local/.rbenv/versions/2.6.2/lib/ruby/2.6.0/bundler/runtime.rb:81:in `require'
2019-09-10T10:01:33.653013195Z     from /usr/local/.rbenv/versions/2.6.2/lib/ruby/2.6.0/bundler/runtime.rb:81:in `block (2 levels) in require'
2019-09-10T10:01:33.653270496Z     from /usr/local/.rbenv/versions/2.6.2/lib/ruby/2.6.0/bundler/runtime.rb:76:in `each'
2019-09-10T10:01:33.653282496Z     from /usr/local/.rbenv/versions/2.6.2/lib/ruby/2.6.0/bundler/runtime.rb:76:in `block in require'
2019-09-10T10:01:33.653841699Z     from /usr/local/.rbenv/versions/2.6.2/lib/ruby/2.6.0/bundler/runtime.rb:65:in `each'
2019-09-10T10:01:33.654110300Z     from /usr/local/.rbenv/versions/2.6.2/lib/ruby/2.6.0/bundler/runtime.rb:65:in `require'
2019-09-10T10:01:33.654122300Z     from /usr/local/.rbenv/versions/2.6.2/lib/ruby/2.6.0/bundler.rb:114:in `require'
2019-09-10T10:01:33.654126600Z     from /home/site/wwwroot/config/application.rb:7:in `'
2019-09-10T10:01:33.654130900Z     from /tmp/bundle/gems/activesupport-6.0.0/lib/active_support/dependencies.rb:325:in `require'
2019-09-10T10:01:33.654486101Z     from /tmp/bundle/gems/activesupport-6.0.0/lib/active_support/dependencies.rb:325:in `block in require'
2019-09-10T10:01:33.654497602Z     from /tmp/bundle/gems/activesupport-6.0.0/lib/active_support/dependencies.rb:291:in `load_dependency'
2019-09-10T10:01:33.654501702Z     from /tmp/bundle/gems/activesupport-6.0.0/lib/active_support/dependencies.rb:325:in `require'
2019-09-10T10:01:33.655368405Z     from /tmp/bundle/gems/railties-6.0.0/lib/rails/commands/server/server_command.rb:141:in `block in perform'
2019-09-10T10:01:33.655380305Z     from /tmp/bundle/gems/railties-6.0.0/lib/rails/commands/server/server_command.rb:138:in `tap'
2019-09-10T10:01:33.655384405Z     from /tmp/bundle/gems/railties-6.0.0/lib/rails/commands/server/server_command.rb:138:in `perform'
2019-09-10T10:01:33.655388005Z     from /tmp/bundle/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
2019-09-10T10:01:33.657101412Z     from /tmp/bundle/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
2019-09-10T10:01:33.657361613Z     from /tmp/bundle/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
2019-09-10T10:01:33.657373513Z     from /tmp/bundle/gems/railties-6.0.0/lib/rails/command/base.rb:65:in `perform'
2019-09-10T10:01:33.657672315Z     from /tmp/bundle/gems/railties-6.0.0/lib/rails/command.rb:46:in `invoke'
2019-09-10T10:01:33.657683315Z     from /tmp/bundle/gems/railties-6.0.0/lib/rails/commands.rb:18:in `'
2019-09-10T10:01:33.657687415Z     from bin/rails:9:in `require'
2019-09-10T10:01:33.658013916Z     from bin/rails:9:in `
'

I created similar rails app and pushed on Ruby2.4  on August, it run properly.
(mysql2.so was created when bundle install )
I found recentrly updated docker image, is there a possibility that it has a relation to this?
https://hub.docker.com/r/appsvc/ruby/tags

I contacted the Microsoft Support in Japan  about this issue through my customers.
I've got the reply below:

There was a lack of dependency on Ruby environment in the latest Kudu.
set environment variable 'ENABLE_KUDU_LITE = false'

I set the environment variable on my Web App, and run correctly.
It seems that this bug is on Kudu, so I close this issue.


Error messages

I have the  the following messages in R -gstudio:
STEP 2
remote_add(repo,
            name = "NESCent",
            url = "https://github.com/NESCent/popgenInfo.git")
Error in remote_add(repo, name = "NESCent", url = "https://github.com/NESCent/popgenInfo.git") :
  Error in 'git2r_remote_add': Remote 'NESCent' already exists.
In addition: Warning message:
package ‘git2r’ was built under R version 3.2.3

# Check our remotes
remotes(repo)

STEP 3
checkout(repo, "master")
Error in .local(object, ...) :
  Error in 'git2r_checkout_tree': 2 conflicts prevent checkout

Any idea? Can I continue?
In addition I work on my local folder and I have some "try" files. It is=t a problem? Do I need to remove them?

Error in 'git2r_remote_add': Remote 'NESCent' already exists.

This error says that you already have the remote set up. If you look at the introduction, you'll notice that the first two steps should only be done once.

Error in 'git2r_checkout_tree': 2 conflicts prevent checkout

It's difficult to know what this means without knowing what the state of your repository is. Given your next comment:

In addition I work on my local folder and I have some "try" files.

I would say that this is a problem. I think the easiest option is to delete your local repository and then start from step 2. If you have any new files, save them somewhere else and add them in during step 5.
Does this help?

Yes, very helpful.
In step 4, I suggest to give the information on the name of the vignette and the branch when you give a  name to the branch :(good practice is to name it the same as your branch): I read it too late.
About step 5,  I can use command  lines in Gsudio too?
I can re-start directly from step 5? Or do I need to update something before?

In step 4, I suggest to give the information on the name of the vignette and the branch when you give a name to the branch :(good practice is to name it the same as your branch): I read it too late.

Very good point. I will make sure to update this :+1:

About step 5, I can use command lines in Gsudio too?

Yes, these commands can be run in Rstudio (as I did in the video)

I can re-start directly from step 5? Or do I need to update something before?

Because of the error messages above, I don't think you can start from step 5. You should delete the repository off your computer and start from step 2.

-I already re-start from step 2 and have now no error message.
-I have created a new branch (as described in the vignette) but I have  pushed no  file (steps 5) (I am still working on the vignette).
-My question was when I am ready to commit my new file, where I need to start again: can I use the new branch that I have created but that it is empty? Or do I need to update my local repository and create a new branch? In this case I probably need to delete  the empty branch that I have created?

My question was when I am ready to commit my new file, where I need to start again: can I use the new branch that I have created but that it is empty?

:+1: Yes. When you want to add your new file, you should use that branch.
Is this the new branch you are referring to: https://github.com/smanel/popgenInfo/tree/2016-01-18-spatial-stats ?

yes.


RRDtool graphs are not displaying on the admin page

Graphs are not loading on the admin page.  Seeing the following error in the console:
[13/01/2017 04:24:14.495] (error) handler_render_rrd.c:115 - RRDtool replied an
    error message: ERROR: opening '/var/lib/cherokee/graphs/server.rrd': No
    such file or directory
 | The issue seems to be related to your system.

Found this mail list conversation from 2010
On 30/04/2010, at 22:34, Baudouin Van Humbeeck wrote:

> My latest problem is with the rrdtool :
>
> [30/04/2010 20:28:31.590] (error) handler_render_rrd.c:115 - RRDtool replied
> an error message: ERROR: opening '/var/lib/cherokee/graphs/server.rrd': No
> such file or directory

Please ensure that /var/lib/cherokee/graphs/ exists, and that cherokee's user
has enough permissions to write in that directory.

> What have I not done, what should I do to see the monitor graphs ?

Fix the previous issue. Odds are it's a permissions related issue.

Will try having the build create the directory with the correct permissions. 🤔


Milestone 1: Setting up Hello Microverse

Milestone 1: Setting up Hello Microverse
In this milestone I:

Installed Linters
Added gitignore and ignored node_modules
Added index.html, style.css, test.md
Ignored 'test.md' using gitignore
Updated ReadMe file

Hi @.**,
Thank you so much for the feedback.
Best,
Leonardo P Goss
On Tue, Jan 4, 2022 at 8:32 PM Miguel Puentes @.***>
wrote:

@.**** approved this pull request.
Hi @leopiresgoss https://github.com/leopiresgoss ,

Pull Request have a descriptive title ✔
Pull Request have a short summary describing introduced changes ✔
README file is descriptive ✔
Linters are set up correctly ✔
Commit messages are meaningful. ✔

Your project is complete! There is nothing else to say other than... it's
time to merge it [image: :shipit:]
Congratulations! 🎉
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something
is not 100% clear.
As described in the Code reviews limits policy
https://microverse.zendesk.com/hc/en-us/articles/1500004088561 you have a
limited number of reviews per project (check the exact number in your
Dashboard). If you think that the code review was not fair, you can request
a second opinion using this form https://airtable.com/shrQAqnBwek5a0O0s.
—
Reply to this email directly, view it on GitHub
https://github.com/leopiresgoss/hello-microverse/pull/1#pullrequestreview-844167887,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOXH7HT4QWEMTA2I6ZU4HA3UUOUULANCNFSM5LIZQIGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


chartHeight is sometimes ignored

https://preview.squiggle-language.com/playground#code=eNqrVirOyC8PLs3NTSyqVLIqKSpN1QELuaZkluQXwURSUtMSS3NKnPNTUpWslPLyi3ITczRMdYw0de2KkxNzUn3y05VqASw%2BGsg%3D
Don't have time to investigate, but it seems to be caused by negative y values in data. So maybe should be fixed by changes to scaleLog.

The output is still broken, but height is not ignored.


"KeyError: 'tag_name'" error when attempting to decompile an ARM template

This is autogenerated. Please review and update as needed.
Describe the bug
When trying to decompile a template, I get the verbose error below.
The ARM template is perfectly valid, and I can deploy it successfully using the CLI.
For reference, this is the template i'm trying to decompile.
{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "<IP_ADDRESS>",
  "parameters": {
    "suppressionEnabled": {
      "type": "bool",
      "metadata": {
        "description": "Determines whether the suppression for this alert rule is enabled or disabled."
      },
      "defaultValue": false
    },
    "createIncident": {
      "type": "bool",
      "metadata": {
        "description": "True/False whether to create an incident when the rule is triggered"
      },
      "defaultValue": false
    },
    "queryFrequency": {
      "type": "string",
      "metadata": {
        "description": "The frequency (in ISO 8601 duration format) for this alert rule to run. Example: PT1H"
      },
      "defaultValue": "PT1H"
    },
    "suppressionDuration": {
      "type": "string",
      "metadata": {
        "description": "The suppression (in ISO 8601 duration format) to wait since last time this alert rule been triggered. Example: PT1H"
      },
      "defaultValue": "PT1H"
    },
    "tactics": {
      "type": "array",
      "metadata": {
        "description": "The tactics detected by this rule as mapped to the MITRE ATT&CK framework"
      },
      "defaultValue": [
        "CredentialAccess"
      ]
    },
    "severity": {
      "type": "string",
      "metadata": {
        "description": "The severity for alerts created by this alert rule"
      },
      "defaultValue": "Medium",
      "allowedValues": [
        "High",
        "Medium",
        "Low",
        "Informational"
      ]
    },
    "location": {
      "type": "string",
      "metadata": {
        "description": "The location in which the resource should be deployed"
      },
      "defaultValue": "[resourceGroup().location]"
    },
    "triggerThreshold": {
      "type": "int",
      "metadata": {
        "description": "The threshold triggers this alert rule."
      },
      "defaultValue": 0
    },
    "triggerOperator": {
      "type": "string",
      "metadata": {
        "description": "The operation against the threshold that triggers alert rule. Allowed values: Equal, GreaterThan, LessThan and NotEqual"
      },
      "defaultValue": "GreaterThan",
      "allowedValues": [
        "GreaterThan",
        "Equal",
        "LessThan",
        "NotEqual"
      ]
    },
    "workspaceName": {
      "type": "string",
      "metadata": {
        "description": "Workspace name for Log Analytics where Sentinel is setup"
      }
    },
    "ruleId": {
      "type": "string",
      "metadata": {
        "description": "The unique guid for this scheduled alert rule"
      },
      "defaultValue": "[newGuid()]"
    },
    "queryPeriod": {
      "type": "string",
      "metadata": {
        "description": "The period (in ISO 8601 duration format) that this alert rule looks at. Example: P2DT1H30M"
      },
      "defaultValue": "PT1H"
    }
  },
  "variables": {
    "ruleDisplayName": "MFA disabled for a user",
    "ruleQuery": "(union isfuzzy=true\n(AuditLogs \n| where OperationName =~ \"Disable Strong Authentication\"\n| extend IPAddress = tostring(parse_json(tostring(InitiatedBy.user)).ipAddress) \n| extend InitiatedByUser = iff(isnotempty(tostring(parse_json(tostring(InitiatedBy.user)).userPrincipalName)), \n tostring(parse_json(tostring(InitiatedBy.user)).userPrincipalName), tostring(parse_json(tostring(InitiatedBy.app)).displayName))\n| extend Targetprop = todynamic(TargetResources)\n| extend TargetUser = tostring(Targetprop[0].userPrincipalName) \n| summarize StartTimeUtc = min(TimeGenerated), EndTimeUtc = max(TimeGenerated) by User = TargetUser, InitiatedByUser , Operation = OperationName , CorrelationId, IPAddress, Category, Source = SourceSystem , AADTenantId, Type\n),\n(AWSCloudTrail\n| where EventName in~ (\"DeactivateMFADevice\", \"DeleteVirtualMFADevice\") \n| extend InstanceProfileName = tostring(parse_json(RequestParameters).InstanceProfileName)\n| extend TargetUser = tostring(parse_json(RequestParameters).userName)\n| summarize StartTimeUtc = min(TimeGenerated), EndTimeUtc = max(TimeGenerated) by User = TargetUser, Source = EventSource , Operation = EventName , TenantorInstance_Detail = InstanceProfileName, IPAddress = SourceIpAddress\n)\n)\n| extend timestamp = StartTimeUtc, AccountCustomEntity = User, IPCustomEntity = IPAddress",
    "ruleDescription": "Multi-Factor Authentication (MFA) helps prevent credential compromise. This alert identifies when an attempt has been made to diable MFA for a user ",
    "entityMappings": [
      {
        "entityType": "Account",
        "fieldMappings": [
          {
            "identifier": "FullName",
            "columnName": "AccountCustomEntity"
          }
        ]
      },
      {
        "entityType": "IP",
        "fieldMappings": [
          {
            "identifier": "Address",
            "columnName": "IPCustomEntity"
          }
        ]
      }
    ]
  },
  "resources": [
    {
      "type": "Microsoft.OperationalInsights/workspaces/providers/alertRules",
      "apiVersion": "2020-01-01",
      "location": "[parameters('location')]",
      "kind": "Scheduled",
      "name": "[concat(parameters('workspaceName'), '/Microsoft.SecurityInsights/', parameters('ruleId'))]",
      "properties": {
        "ruleDescription": "[variables('ruleDescription')]",
        "tactics": "[parameters('tactics')]",
        "queryPeriod": "[parameters('queryPeriod')]",
        "displayName": "[variables('ruleDisplayName')]",
        "suppressionDuration": "[parameters('suppressionDuration')]",
        "severity": "[parameters('severity')]",
        "triggerOperator": "[parameters('triggerOperator')]",
        "createIncident": "[parameters('createIncident')]",
        "alertRuleTemplateName": "65c78944-930b-4cae-bd79-c3664ae30ba7",
        "queryFrequency": "[parameters('queryFrequency')]",
        "triggerThreshold": "[parameters('triggerThreshold')]",
        "entityMappings": "[variables('entityMappings')]",
        "enabled": true,
        "query": "[variables('ruleQuery')]",
        "suppressionEnabled": "[parameters('suppressionEnabled')]"
      }
    }
  ]
}

Command Name
az bicep decompile
Errors:
'tag_name'
Traceback (most recent call last):
cli\Lib\site-packages\knack\cli.py, ln 233, in invoke
azure\cli\core\commands\__init__.py, ln 660, in execute
azure\cli\core\commands\__init__.py, ln 723, in _run_jobs_serially
azure\cli\core\commands\__init__.py, ln 716, in _run_job
artifacts\cli\Lib\site-packages\six.py, ln 703, in reraise
azure\cli\core\commands\__init__.py, ln 694, in _run_job
azure\cli\core\commands\__init__.py, ln 331, in __call__
site-packages\azure\cli\core\__init__.py, ln 811, in default_command_handler
azure\cli\command_modules\resource\custom.py, ln 3206, in decompile_bicep_file
azure\cli\command_modules\resource\_bicep.py, ln 41, in run_bicep_command
azure\cli\command_modules\resource\_bicep.py, ln 102, in get_bicep_latest_release_tag
KeyError: 'tag_name'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

az bicep decompile -f MFADisabledForAUser.json

Expected Behavior
The ARM template is decompiled into a new .bicep file
Environment Summary
Windows-10-10.0.21343-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.21.0

Extensions:
azure-devops 0.18.0
sentinel 0.1.0

Additional Context

There's also an interesting observation I've made...
The decompile command works initially, however when I run a script that processes roughly 150ish arm templates, the decompile command will start to fail around the 50-60th template it's processing. From that point on, ANY template I try to decompile, even one's that decompiled successfully a few moments ago, will fail with the above error.

route to service team

Another quick update after some more troubleshooting:
The problem does not occur when running the same steps using the bicep binary (bicep.exe). This is my workaround for now.
bicep --version
Bicep CLI version 0.3.126 (a5e4c2e567)

I'm getting a 'tag_name' response when deploying bicep files.

Everything was working at first, but after a few deployments, it broke somehow and 'tag_name' is the only response I get. I get the same result in PowerShell Core on Windows Terminal and PS Core in VS Code.


Initial Documentation Boilerplate and SEO Buffs

Now that we're officially in the ALPHA phase of our release, it's a good time to start adding search engine optimization (SEO) and public-facing docs for our open-source pursuits; with items such as a README, contributor guidelines, and code of conduct.
What I did was go-ahead and add these items.
Docs Items:

README.md - Summary of the project, guidelines, and contact information.
CONTRIBUTING.md - Guidelines for prospective maintainers & contributors.
CODE_OF_CONDUCT.md - Helps us maintain a safe and welcoming space for the contributors and the community.

SEO Items:

Open Graph Twitter, Facebook, and Google meta tags -
Static preview png image of the pipelines website hero section

Cheers 🚀

Was missing a closing " char in an html element, my bad y'all 😅


Missing to reconfigure despite Observed qa_energy above threshold for some messages

This is related to the current architecture of the mros_reasoner (see discussions 1 and 2), that is:

async reception of input data
sync execution of the reasoning with that data (only most recent value)

I propose to keep the highest value received on each timer_cb cycle for reasoning
@marioney @gavanderhoorn what do you think? We need a quick fix now for these experiments to provide useful results for the paper, but also a proper solution maybe later, rethinking the execution model of the metacontroller.

related to https://github.com/rosin-project/mros1_reasoner/issues/48#issuecomment-633042731
I change to wontfix the issue thanks to Mario's fix with a lock 8cba195 see https://github.com/rosin-project/mros1_reasoner/issues/48#issuecomment-633102711

This issue has been labeled with wontfix, I am closing it.


AWS CLI support AWS Certificate Manager since version 1.10.0

In https://github.com/open-guides/og-aws#aws-product-maturity-and-releases it stated AWS Certificate Manager don't have CLI support, but it's actually supported (via aws acm command) since awscli 1.10.0
See https://github.com/aws/aws-cli/blob/master/CHANGELOG.rst#1100

@number5 Good catch. I've sent a pull request with the change. Thank You.


Add Repo Analytics

This is a pipe dream at the moment, but I want to be able to run some analytics on this repo. I think it would be cool to see some data visualization for the world of programming languages.

I wonder how hard it would be to make a GitHub Analytics plugin for WordPress. Ideally, I'd like something where I could create a shortcode that has loads of parameters for configuring the view. Then, when it's working well, support could be added for UI configuration.

Looks like there's tons of PHP support: https://developer.github.com/v3/libraries/

I'll close this as a token to the current wiki. I'm assuming the wiki will eventually morph into something that offers more in terms of analytics.


[Testing] More tests for fill_identities

Add tests for fill_identities. namely turn the following examples into tests:
b = chain(CNOT(0,1), CNOT(1,2))
b = chain(kron(CNOT(0,1)), kron(CNOT(1,2)))
b = kron(CNOT(0,1))
b = chain(SWAP(0,1), SWAP(0,3))

This could also include a refactor of how fill_identities works. Currently its a bit complicated/ugly.

@jpmoutinho  Check if relevant and could be added to #613.


Update $user -> $__user

To piggy back off of https://www.github.com/RetroPie/RetroPie-Setup/pull/3951
This updates all

$user:$user to $__user:$__group
pi:pi to $__user:$__group
/home/pi to $home

Re-enables x86 on a handful of scripts.
Note: This is still a WIP, I wanted you to be aware of it.

I understand that.  I've been trying to think of a decent solution.
I know as is, without the change some of those scripts provide really bad ownership settings (for examples the ones that do 'chown pi:pi ...' not using the variables at all.
I'm not really sure how to check that the person is using a more recent version of RP.  Maybe something like
if $(git log --format=format:%H | grep 18c2b43000ec54d74ba016e0b8de654122377dba); then ..
but even then, do we really want to add that check in every script, and if so for how long.  Maybe something in the update script or install script, that if that hash is not in the results then abort with a message saying RP needs an update before continuing?

very cool, again thanks
as for how long, until there is a official release from RP. i would think. since at that point it will have this change already built in.

For a variety of reasons, this is growing rapidly in size.
I have only tested a handful of scripts so far, and I am running into build issues that are completely unrelated to my changes.
For example:
lr-boom3 fails to build because of a missing dependency.
Did not find needed dependencies: libjpeg-turbo8-dev libcurl4-openssl-dev. Trying to install them now. Ign:1 http://linux.dropbox.com/debian bookworm InRelease Hit:2 http://linux.dropbox.com/debian bookworm Release Hit:3 http://deb.debian.org/debian bookworm InRelease Hit:5 http://deb.debian.org/debian-security bookworm-security InRelease Hit:6 http://deb.debian.org/debian bookworm-updates InRelease Hit:7 http://deb.debian.org/debian bookworm-backports InRelease Hit:8 https://updates.signal.org/desktop/apt xenial InRelease Hit:9 https://repo.steampowered.com/steam stable InRelease Hit:10 https://download.opensuse.org/repositories/home:/strycore/Debian_12 ./ InRelease Hit:11 https://www.deb-multimedia.org bookworm InRelease Hit:12 https://www.deb-multimedia.org bookworm-backports InRelease Reading package lists... Reading package lists... Building dependency tree... Reading state information... Package libjpeg-turbo8-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'libjpeg-turbo8-dev' has no installation candidate Could not install package(s): libjpeg-turbo8-dev libcurl4-openssl-dev.
Changing the dependency from libjpeg-turbo8-dev to libjpeg-dev fixed the problem.
Similar issue with the rott* scripts. The rely on libfluidsynth1, which has been replaced by libfluidsynth2 on bullseye and lib*synth3 in bookworm.
Also having to add in a bunch of x86 to the flags.
Because of that I am seriously considering ditching this as is and submitting individual patches by script.

Splitting this up does have the benefit of reduced potential for conflicts during the time needed to work out the various issues while transitioning.
It does drag out the transition for the end users.

Yeah. There is a bunch of work that's needed. This is going to be tricky. Since we still need to make sure these work on 32bit And 64bit. Until RetroPie switchs over to bookworm completely.
So going one by one might be better.
Or at least do the transition in smaller batches.
Whichever works I'm good with.
I'm working on getting the 2 legend of Zelda ports working. So I have not done much else


version 5.1 not supporting Authorization header for access token

Laravel : 5.2
lucadegasperi/oauth2-server-laravel : 5.1
When I try to send access token via Authorization header, it is keep on throwing invalid_request exception with access token missing.

It does work and we're using it. This sounds like an issue on your side.


Building from multiple Category URL's

Hey all,
Thanks for providing such a neat and amazing library!
The issue I am facing is the following:-

I am trying to scrape https://www.jansatta.com/ which has multiple category urls like https://www.jansatta.com/national
However when I try to build using the specific category URL i get news from multiple sources like https://www.jansatta.com/international etc (basically same url's as https://www.jansatta.com/)
Also the articles extracted are always from the first page. The page urls follow the pattern like https://www.jansatta.com/national/page/2 etc. Even when providing the specific URL's I get the same URL's when providing the normal url https://www.jansatta.com/

It would be great to have a solution for this.

This sounds like you're looking to use something akin to scrapy alongside newspaper?


After exiting the program, restore the uploaded file

Describe the feature
I am trying write an application to continuously upload large data (multipart uploads) to Amazon's S3 Storage. However, my application needs to be able to shut down mid-transfer and pick up from where it left off the next time it's restarted.
Use Case
From playing around a little bit with the C++ SDK, the TransferManager class provides a RetryUpload function that requires a shared pointer to the TransferHandle object that is returned upon issuing an initial UploadFile call. However, the transfer handle object will no longer be in existence if the application crashes or has to shut down mid-operation.
Proposed Solution
resume a multipart upload using the TransferManager class
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[X] This feature might incur a breaking change

Thanks for making this request. This is a useful feature and is something that we want to add to this sdk.

So... did you add it? Feels like the thing designed for long file uploads should be able to handle restarting after interruptions?

So... did you add it? Feels like the thing designed for long file uploads should be able to handle restarting after interruptions?

@AlexKTracerMain  yes ,Do you have any questions?


[SPIKE] L2 implementation research

Feature Request
Research other implementing of L2 domains for both reading and writing

Basenames
ENSChain
Linea
Unruggable Labs

Definition of done
A summary of each one of those implementations, looking at the aspects of:

Overall architecture
Reading records

Validation of state

Writing records
ENSIP-16
Ownership of subdomains

https://www.notion.so/blockful/L2-Domains-c588d21e005a466a9628887f0974b846


Add new function which checks for the proper version of dotnet

This will improve the experience when the wrong version of dotnet is present by creating an error very early on in the process with a better error message
Now the developer will see something similar to the following:
PS /users/james/src/github/forks/JamesWTruher/PSScriptAnalyzer> ./build
Incorrect dotnet version: have '2.1.403' need '2.2.102'
At /users/james/src/github/forks/JamesWTruher/PSScriptAnalyzer/build.psm1:137 char:9
         throw 'Incorrect dotnet version: have '' need ' ...
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 CategoryInfo          : OperationStopped: (Incorrect dotne... need '2.2.102':String) [], RuntimeException
 FullyQualifiedErrorId : Incorrect dotnet version: have '2.1.403' need '2.2.102'

PR Summary

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

i'm closing this and will incorporate it into https://github.com/PowerShell/PSScriptAnalyzer/pull/1139


Add main phi20 tokens logos

Hello can we add the logos for the major tokens (Usdc, usdt, matic, bnb, etc.) on phi smart chain. Tokens show but the logos don't show thank you.
Screenshot attached so u can see what we are referring too.

Is this something we can do for next update @hboon

@hboon  can we add these

@Phinetwork oh yes, let me look into this, was preparing and updated our token collection earlier.

@Phinetwork can you help to paste the address and the PNG (180x180) icons for each? But is there an exchange where they can be bridged to/fro the ones on Ethereum mainnet?

@Phinetwork oh yes, let me look into this, was preparing and updated our token collection earlier.

Ok awesome thanks.

@Phinetwork can you help to paste the address and the PNG (180x180) icons for each? But is there an exchange where they can be bridged to/fro the ones on Ethereum mainnet?

Yes what folder does the contract address with the image go into will help add this as a pull request just need to know where it goes. Also there is a decentralized crosschain swap can see the bridge here. It's set up for BSC & polygon ethereum will be added in the future for now because of lower gas fees BSC & polygon are the chains that are used on the crosschain swap.
https://bridge.phi.network

You can just drop the images here.

![0xBF5cFf4ABa4d2bf966D75fA60790C3E4eafb62e1](https://user-images.githubuserconte

nt.com/85964511/197373
![0x6C963ecbB25a55cf663879

F13f

9EE282Cf89898A](https://user-images.githubusercontent.co

m/85964511/197373776-36de16eb-a119-40e5-95e6-7709015b89f8.png)
741-0f974eb4-daee-429a-ab93-3f32e90bf6e1.png)

the addresses are attached to the image name can not tell if they are correct after uploading. https://phi.icu/drive/s/W1JXKFaTQlDM1fhuHVw5q9u32fWVNP
can also download from this link that has the contract address attached as the png name

Did the logos work for you? @hboon

@Phinetwork away for a bit, will get back to this in a week+

@Phinetwork away for a bit, will get back to this in a week+

Ok awesome thanks for updates along with the logos the price will display for tokens like Usdc usdt busd as well right. On certain phones like the iPhone 11 & 13 seems to display price for certain tokens like usdc but the iPhone 12 only display value for phi. Is there a way that we can display the token value for all the tokens sent with the logos no matter what device.

@Phinetwork away for a bit, will get back to this in a week+

Where we able to get this added for the next update @hboon hope your doing great & had a nice time away.

@Phinetwork done!

@Phinetwork done!

Thank you can we also add the BCH logo as well as see why phi20 transactions are going now to contract address rather then destination wallet.

The transfer issue is fixed in #5812. We have a hotfix pending approval and it will also be merged into master


memory leak

when i'm using jsoup 1.8.1 for android i got outofmemory exception when execute request 2-3 times.
//the code for 1.8.1 version
Document doc = Jsoup.connect(url)
                     .cookies(getCookie())
                     .maxBodySize(0) // page size around 6Mb (also i try 2mb page and memory issue also)
                     .get();

returned  html contains too many elements and application is crashed after 2-3 passing of get url.
I think this is memory leak bug because with old jsoup version  1.5.2 all works fine without outofmemory!!! (i found this solution in stackoverflow dot com).
please fix this error, i wanna use newest version of jsoup.
if you need get page dump here https://dropbox.com/s/dyhb3z52lohdwbx/dump_page.html?dl=1

STACK_TRACE=java.lang.OutOfMemoryError
at java.io.ByteArrayOutputStream.expand(ByteArrayOutputStream.java:91)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:201)
at org.jsoup.helper.DataUtil.readToByteBuffer(DataUtil.java:146)
at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:498)
at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:434)
at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:181)
at ru.gemobile.toramp.utils.Parser.parseMyNewSerials(Parser.java:216)
at ru.gemobile.toramp.fragments.FragmentNewSeries$11.run(FragmentNewSeries.java:391)
at java.lang.Thread.run(Thread.java:856)

That stack indicates that it's running out of memory trying to allocate a buffer to read contents into. It doesn't indicate a leak. If you could answer the other parts of my question we might be able to get further.

Please reopen if you can answer those Qs and indicate a leak.


Enable snapshot tests in 1.17 to be run in non-alpha jobs.

Tested in https://github.com/kubernetes-csi/csi-driver-host-path/pull/129/files
This requires adding one more parallel e2e test run with
a special focus flag because snapshot tests are still guarded
with a "[Feature:VolumeSnapshotDataSource]" tag. The setting that
skips all tests with "[Feature:.*]" has to be removed because it
overrides the focus.
We don't have serial snapshot tests yet. This needs to be modified
again if we add any in the future.

/assign @ggriffiths

/release-note-none


issues #169 and #201 : Added support to configure BigQuery partition

This is a duplicate of #203 and #229 as I had issues with licence/cla and/or other commits

Codecov Report

Merging #244 into master will increase coverage by 0.14%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #244      +/-   ##
============================================
+ Coverage     68.89%   69.03%   +0.14%
- Complexity      275      276       +1
============================================
  Files            32       32
  Lines          1469     1476       +7
  Branches        154      155       +1
============================================
+ Hits           1012     1019       +7
  Misses          409      409
  Partials         48       48

Codecov Report

Merging #244 into master will increase coverage by 0.14%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #244      +/-   ##
============================================
+ Coverage     68.89%   69.03%   +0.14%
- Complexity      275      276       +1
============================================
  Files            32       32
  Lines          1469     1476       +7
  Branches        154      155       +1
============================================
+ Hits           1012     1019       +7
  Misses          409      409
  Partials         48       48

Impacted Files
Coverage Δ
Complexity Δ

...onnect/bigquery/config/BigQuerySinkTaskConfig.java
95.74% <100%> (+0.39%)
5 <0> (ø)
:arrow_down:

...wepay/kafka/connect/bigquery/BigQuerySinkTask.java
61.25% <100%> (+0.61%)
29 <0> (+1)
:arrow_up:

@mtagle continuing our discussion from #229 this is the PR with only my commits. Could you please have a look.

@darshanmehta10 @mtagle
not sure if I misunderstand the PR, so please correct me if I am.
The way I am looking at it is that we are just removing the PartitionDecorator. If we remove the PartitionDecorator, then BigQuery can use column based partitioning to partition the records, however, the BigQuery table needs to be preconfigured beforehand to specify which field in the record is the column to be partitioned on. What if the table is not created yet and auto.create.tables = true. Will column based partitioning still work and if so, how will BigQuery know which column to partition on?

@levzem Yes, BigQuery table needs to be configured beforehand in order to use this feature. There is an open request to add this support to this component, you can track it here.

@mtagle Does it look good to you now?

Yup, looks good! thank you!


Add gcov php coverage report

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Ready for review
Link to a lcov code coverage report for PHP in Jenkins: https://grpc-testing.appspot.com/job/gRPC_pull_requests/5153/config=gcov,language=php,platform=linux/HTML_Report/

Please update the copyright dates in build_php.sh and post_tests_php.sh.

Fixed the copyright dates.

Ping?

Thanks!


Incorrectly formatted location in error messages

In certain cases the location in error messages is incorrectly formatted, e.g., tests/integration/session/tls_handshake_session.rflx:18:7:18:14: [...].

@treiher I was wondering how we could have avoided that issue. If I understand that correctly, the use of ... prevented pylint from finding the issue? Can we forbid its use?

Good point. mypy interprets ... inside Callable as "arbitrary number of arguments of Any type". Even with --strict the issue is not detected, but mypy has a --disallow-any-explicit flag, which does what we need for that: preventing the explicit use of Any or similar things like .... I have added that option to #583.


BrainGlobe general-purpose registration tool

This issue is to start listing features and plans for a general purpose BrainGlobe registration tool. We can discuss here, and then priorities features, turning these into issues and milestones.
Scientific requirements

Registration of any brain subvolume, including:

2D sections (any orientation, inc some damage)
Whole brains
Thick sections (e.g. from tissue clearing, acute recordings)
Small blocks (e.g. from tissue clearing or expansion microscopy)

Tech requirements

Python-based (compatibility with BrainGlobe & other bioimage analysis tools)
Includes a napari plugin for pre-processing and compatibility with BrainGlobe ecosystem
Registration using elastix (likely itk-elastix) due to community support and existing parameter sets
Includes default preprocessing options (e.g. using scikit-image)
Registers to any BrainGlobe atlas
Compatible with downstream BrainGlobe tools (brainreg-segment, cellfinder etc)
Compatible with other napari plugins
Can be automated

Potential steps

Flexible interface to allow:

Data preprocessing
Appropriate atlas cropping
Running registration
Saving results

Mockup

cc @alessandrofelder @raacampbell @viktorpm

Some existing tools in this space


regex error on create-account/details form

Steps to Reproduce

Create a new account at https://rc.mitxonline.mit.edu/create-account/
Click on the link in the verification email
Start typing in the form.

Expected Behavior
Shouldn't get any errors in the console.
Actual Behavior
In Firefox, I get the error:
Unable to check <input pattern='^(?![~!@&)(+:'.?,-]+)([^/\^$#*=[\]%_;<>{}"|]+)$'> because the pattern is not a valid regexp: invalid character in class in regular expression`
It does not prevent me from submitting the form, but we have a ticket (browser unknown) from a user saying that the continue button doesn't function.

Possibly related to https://github.com/mitodl/mitxonline/issues/1788


chore(deps): update terraform terraform-ibm-modules/base-ocp-vpc/ibm to v3.14.3

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/base-ocp-vpc/ibm (source)
module
patch
3.14.2 -> 3.14.3

Release Notes

terraform-ibm-modules/terraform-ibm-base-ocp-vpc (terraform-ibm-modules/base-ocp-vpc/ibm)
v3.14.3
Compare Source
Bug Fixes

deps: update terraform-module (#324) (1cc9fbe)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.0.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Calendar not read by NVDA when navigating via keyboard

When trying to access the calendar via keyboard with NVDA all it says is "blank" every time i press an arrow key.  With Jaws, it started actually changing focus to adjacent form fields.
Is there any intention to make this work?
I tried navigating through the calendar with my keyboard with the following screen reader / browser configurations (sorry these are so old - its what I happen to have here at work):

NVDA 2014.4 + IE9
NVDA 2015.1 + IE9
NVDA 2014.4 + FF 35
NVDA 2015.1 + FF 35
JAWS 14 + IE9
JAWS 14 + FF35

Correct me if I'm wrong, but it has to do with the lack of ARIA support right ?
If yes this is a duplicate of #811.

Yes, I believe an implementation using ARIA tags would solve this.  Closing as a duplicate.


Ensure that ListenAddress follows AddressFamily

This appears to be undocumented, but ListenAddress must follow
AddressFamily when specified in the sshd_config file.
Closes #33

Coverage decreased (-0.2%) to 98.106% when pulling 3819445fb4ba864022f0e7d8a02e72c47314aeba on trevor-vaughan:addressfamily_fix into df2b6627213491429276d7a739597fec0447b760 on hercules-team:master.

Coverage decreased (-0.2%) to 98.106% when pulling 3819445fb4ba864022f0e7d8a02e72c47314aeba on trevor-vaughan:addressfamily_fix into df2b6627213491429276d7a739597fec0447b760 on hercules-team:master.

Coverage decreased (-0.2%) to 98.106% when pulling 3819445fb4ba864022f0e7d8a02e72c47314aeba on trevor-vaughan:addressfamily_fix into df2b6627213491429276d7a739597fec0447b760 on hercules-team:master.

Coverage decreased (-0.2%) to 98.106% when pulling 3819445fb4ba864022f0e7d8a02e72c47314aeba on trevor-vaughan:addressfamily_fix into df2b6627213491429276d7a739597fec0447b760 on hercules-team:master.

@raphink Any chance of a CR on this one, it has the potential to actively break running configs?
I'm not sure why Travis is mad or why the Coveralls coverage was decreased (especially since I added tests).

@hercules-team/augeasproviders Anyone up for reviewing this? It actively breaks SSH configs. If not, let me know and I'll just shove it through.

I received validation that this patch fixes issues in production systems. If I don't hear a "do not proceed" by mid-day tomorrow, I'm going to go ahead and release.

Updated this and prepped it for a release. All spec tests pass. Not sure what's up with Travis.


Add more charities, correct typos in readme

Hi Tom, just stumbled onto the project on my page -- looks great!
Added some charities as you recommended, and fixed some typos (afaik) in the README.

Hey Lyndon! Good to hear from you.
Thanks, the typos are all correct haha.