fix: don't duplicate styles with dynamic import (fix #9967)

Description
Fixes #9967 by normalizing asset URLs to full absolute URLs with origin and comparing them to link.href properties of all links in the document to find duplicates.
Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

@patak-dev This is ready for review :)

I don't think we should modify the way paths work when the base is not relative. You can think about it as an optimization, and there may already be plugins that expect a certain pattern for Vite preload paths. The bug only appears for relative base, so let's fix it for it.

@patak-dev ready for next round :)

added back relativePreloadUrls and different code for relative and absolute base
added comments clarifying the logic of isPreloaded

@Tal500 @patak-dev I added test from this PR on top of  Tal500's work here https://github.com/bgoscinski/vite/tree/preload-on-system-format-with-9967-test. Unfortunately the test fails :(

@Tal500 @patak-dev I added test from this PR on top of Tal500's work here https://github.com/bgoscinski/vite/tree/preload-on-system-format-with-9967-test. Unfortunately the test fails :(

Hi! As I said in (my comment on you code review)[https://github.com/vitejs/vite/pull/9970#discussion_r965188294], I know that my code isn't perfect (intentionally, because of failing CI) on avoiding duplicated CSS.
The purpose of my PR is different - the partial CSS duplication is only a "side business".
The reason my code isn't fully avoid duplication, is because not both sides of the path equality test are always absolute, and I "cheated" there to avoid failing CI. (Hope you'd find why the CI are failing, assuming some tests are wrong)
The review I sent you was not related to the fact I fail to avoid some duplication.
I was just saying that you can take the idea of instead passing through all the link in the page, per dep, is just do CSS query that takes the relevant links that ends with the same file name, when you trim the parent dir from the URL.
Then, after you have a small set of candidates(e.g. with the hashes it will almost always be exactly one candidate), then check the absolute paths of both sides of the path equation. This just saves so much time for performance, and it's not a too complicated idea.

@Tal500 Ahhhh I see! I assumed that your PR is a "superset" of mine and it fixes the bug. That's why I ported my test to your PR :)
In this case I'll borrow the trick with the CSS selector :)

@patak-dev ready for next pass :) I don't know why MacOS failed but I think this is some kind of a flakiness issue.
Changes summary:

When relativePreloadUrls is false (base isn't relative), then we don't have a bug, no? So we can leave the code as it was before. Or is there a bug here too? IIUC, the bug you reported only happens for relative base.

Addressed. Please see isBaseRelative.

And in this case [base is relative], what we need is to compare new URL(link.href, location.href).href === dep

As I pointed out here and demonstrated here link.href must be absolute (with protocol, host and all the other URL parts). This behavior is also specified here under "If the content attribute is defined to contain a URL". With this in mind new URL(link.href, location.href).href is IMO redundant. If you could please share a scenario that fails without new URL(link.href, location.href).href I'll be happy to add a test for it and implement required changes to make it pass.

I think the test cases may not be correctly testing the issue you reported because CI is passing, or maybe I'm missing something here.

I run my project with Vite built from this branch and bug is gone so I think we're good.

@patak-dev ready for next pass :) I don't know why CI failed on MacOS but I think this is some kind of a flakiness issue.
Changes summary:

When relativePreloadUrls is false (base isn't relative), then we don't have a bug, no? So we can leave the code as it was before. Or is there a bug here too? IIUC, the bug you reported only happens for relative base.

Addressed. Please see isBaseRelative.

And in this case [base is relative], what we need is to compare new URL(link.href, location.href).href === dep

As I pointed out here and demonstrated here link.href must be absolute (with protocol, host and all the other URL parts). This behavior is also specified here under "If the content attribute is defined to contain a URL". With this in mind new URL(link.href, location.href).href is IMO redundant. If you could please share a scenario that fails without new URL(link.href, location.href).href I'll be happy to add a test for it and implement required changes to make it pass.

I think the test cases may not be correctly testing the issue you reported because CI is passing, or maybe I'm missing something here.

I run my project with Vite built from this branch and bug is gone so I think we're good.

Don't you think that the best, simple thing is to always compare their absolute URLs, no matter what the configuration is?
It's also future safe.

@Tal500

Don't you think that the best, simple thing is to always compare their absolute URLs, no matter what the configuration is? It's also future safe.

That's what I initially implemented but @patak-dev suggested to postpone it at least until Vite 4

@sapphi-red Ready for next round.
I fixed the bug with <link rel="preload" as="style" href="foo.css"> and modified the tests to make sure this won't regress in the future. Also I didn't quite get what you meant here. Could you please clarify? Also is this something you want to see implemented in this PR?
Aaaand macos build&test failed again... Do you have an idea what might be the cause?
/cc @patak-dev @Tal500

BTW: Too bad you always squash&force-push the commits to the PR branch. I think it's better for history and the conversation to not do this. Don't worry, when the Vite team merge the PR, it will be squashed, as you can see in the contributing guidelines:

It's OK to have multiple small commits as you work on the PR. GitHub can automatically squash them before merging.

BTW: Too bad you always squash&force-push the commits to the PR branch. I think it's better for history and the conversation to not do this. Don't worry, when the Vite team merge the PR, it will be squashed, as you can see in the contributing guidelines:

It's OK to have multiple small commits as you work on the PR. GitHub can automatically squash them before merging.

I figured that out some time ago .

I fixed the bug with <link rel="preload" as="style" href="foo.css"> and modified the tests to make sure this won't regress in the future.

Thanks!

Also I didn't quite get what you meant here. Could you please clarify?

When an HTML rendered by server used an absolute path for CSS, the CSS will be duplicated.
For example, when document.baseURI is https://example.com/ and the server responded with:
<html>
<head>
  <link rel="stylesheet" href="https://example.com/assets/foo.hash.css">
  <script type="module" src="https://example.com/assets/index.hash.js"></script>
</head>
</html>

__preload will inject <link rel="stylesheet" href="/assets/foo.hash.css">.
But it shouldn't inject it because <link rel="stylesheet" href="https://example.com/assets/foo.hash.css"> already exists.
My idea is basically same to https://github.com/vitejs/vite/pull/9970#discussion_r971654762. (I guess we could use seen variable.)

Also is this something you want to see implemented in this PR?

It's a related to the original bug, but this one isn't a bug caused by this PR. So this could be fixed in a different PR. It's not blocking this PR.

@sapphi-red Thanks for clarifying! What else is needed from my side to get this PR ready to merge?


Update scala3-library, ... to 3.0.2

Updates

org.scala-lang:scala3-library
org.scala-lang:scala3-library_sjs1

from 3.0.0 to 3.0.2.
GitHub Release Notes - Version Diff - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

@cla-bot check


Fix Qt not being able to create an XKB context

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Fixes #104
Fixes https://github.com/conda-forge/pyqt-feedstock/issues/52
@ocefpaf, please help us to recompile and upload a new Linux version.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Let's go with #106 just so we can have a 1-1 correspondence between the packaged uploaded and the recipe.


Update comments referencing IdP Link to WorkOS.js

Overview
This PR updates references to IdP Link to WorkOS.js

can you run bin/docs? that updates the generated html (will also update some timestamps so that its clear the docs are up to date)


Remove console.log()

After updating to 10.0.1 some logs started to appear in console.

Please remove it. Thanks in advanced.

Fixed at 10.0.2

cool. Thanks a lot


Heh, forot to move a pointer operation

In #11 I forgot to move a pointer operation, resulting in truncated /.well-known/core payloads being sent. 😅

No problem, looks fine :)


Where is config.json?

Apologies, I've tried searching around this git, creating my own config.json but I get nothing. Can anyone help?

They don't include an example, the example is in the README.md under the title of "Example Configuration"


reddit user case sensitive

Ripme version: 1.7.8
Java version: openjdk version "1.8.0_144"
Operating system: archlinux
Exact URL you were trying to rip when the problem occurred:
Please include any additional information about how to reproduce the problem:

https://www.reddit.com/user/sexyflowerwater
https://www.reddit.com/user/SexyFlowerWater
Are the same redditors, but ripme put them in different directory:
reddit_user_sexyflowerwater
reddit_user_SexyFlowerWater
Expected Behavior
ripme should be case insensitive or get the username in some proper way (author in json?)
Actual Behavior
ripme treat sexyflowerwater and SexyFlowerWater as different redditor.

@cyian-1756 Fixed with PR #400.  Recommend close.


UI updates

@7opf @jmcanterafonseca-iota This is the list of the current issues we got. I already pushed fixes for the ones checked.

[ ] Scanner issue with large Data Matrix (6x6) - (see comment)
[x] Each Android application shall have their own and distinguished name. Moved to https://github.com/jmcanterafonseca-iota/zebra-iota-edge-sdk/pull/45
[x] The title of the application on the Browser shall not be Svelte App but a meaningful. Moved to: https://github.com/jmcanterafonseca-iota/zebra-iota-edge-sdk/pull/45
[x] The applications do not support the landscape mode. Lock orientation. Moved to https://github.com/jmcanterafonseca-iota/zebra-iota-edge-sdk/pull/44
[x] In the browser when going to scan credentials the permissions for the browser (see comment). Moved to https://github.com/jmcanterafonseca-iota/zebra-iota-edge-sdk/pull/31
[x] Build warnings - Rollup. Moved to https://github.com/jmcanterafonseca-iota/zebra-iota-edge-sdk/pull/43
[x] Build warnings - (zxing-js node_modules) Moved to https://github.com/jmcanterafonseca-iota/zebra-iota-edge-sdk/pull/43

Holder:

[x] Bug: Enter the application, follow wizard, generate an Identity, generate credentials. Then reset state. Then follow wizard, generate an Identity, try to generate a Credential, then you get an error saying that “you are not connected to the Internet”. Moved to: https://github.com/jmcanterafonseca-iota/zebra-iota-edge-sdk/pull/42

Device ID Application

[x] DID of the device is generated on the mainnet but the DID of the organization is on the devnet. Alignment shall happen. Moved to https://github.com/jmcanterafonseca-iota/zebra-iota-edge-sdk/pull/46
[x] The Device information has to be obtained from the Device Information, for instance through the navigator interface, but we need to avoid hard coded information (see comment).

All of these commits have now been moved to other PRs


limits.memory.swap not working?

Required information

Distribution: Ubuntu
Distribution version: 16.04
The output of "lxc info" or if that fails:

Kernel version: 4.4.0-38-generic
LXC version: 2.0.4
LXD version: 2.0.4
Storage backend in use: zfs

Issue description
I want to limit swap use in container, I followed the doc to set limits.memory.swap:
$ lxc config set ubuntu-trusty limits.memory.swap false
$ lxc config show ubuntu-trusty
name: ubuntu-trusty
profiles:
- default
config:
  limits.memory: 5GB
  limits.memory.swap: "false"
  security.privileged: "true"
  volatile.base_image: 8f5108a99312694da883bf1396e688bf9f91cf22061eb9ecd806b43b24c6651f
  volatile.eth0.hwaddr: 00:16:3e:24:77:71
  volatile.last_state.idmap: '[]'
devices:
  root:
    path: /
    type: disk
  sharedprojects:
    path: /home/fengyu/projects
    source: /home/fengyu/projects
    type: disk
ephemeral: false

But nothing happened. In the container:
# free -h
             total       used       free     shared    buffers     cached
Mem:          5.0G       103M       4.9G        75M         0B        62M
-/+ buffers/cache:        40M       5.0G
Swap:         3.9G         0B       3.9G

You can see limits.memory works, but the limits.memory.swap not working, still I can see the host swap.
A brief description of what failed or what could be improved.
Here is some output:
$ lxc info ubuntu-trusty --show-log
Name: ubuntu-trusty
Architecture: x86_64
Created: 2016/09/17 12:33 UTC
Status: Running
Type: persistent
Profiles: default
Pid: 14976
Ips:
  eth0:	inet	<IP_ADDRESS>	veth10J9J1
  eth0:	inet6	fe80::216:3eff:fe24:7771	veth10J9J1
  lo:	inet	<IP_ADDRESS>
  lo:	inet6	::1
Resources:
  Processes: 43
  Disk usage:
    root: 20.17GB
  Memory usage:
    Memory (current): 96.51MB
    Memory (peak): 133.50MB
  Network usage:
    eth0:
      Bytes received: 48.99kB
      Bytes sent: 41.48kB
      Packets received: 383
      Packets sent: 372
    lo:
      Bytes received: 292 bytes
      Bytes sent: 292 bytes
      Packets received: 4
      Packets sent: 4
Snapshots:
  snap1 (taken at 2016/09/18 06:31 UTC) (stateless)
  snap2 (taken at 2016/09/22 03:46 UTC) (stateless)

Log:

            lxc<PHONE_NUMBER>2052.601 INFO     lxc_start - start.c:lxc_check_inherited:252 - closed inherited fd 3
            lxc<PHONE_NUMBER>2052.601 INFO     lxc_start - start.c:lxc_check_inherited:252 - closed inherited fd 8
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_container - lxccontainer.c:do_lxcapi_start:797 - Attempting to set proc title to [lxc monitor] /var/lib/lxd/containers ubuntu-trusty
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_start - start.c:lxc_check_inherited:252 - closed inherited fd 8
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment this to allow umount -f;  not recommended.
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount action 0
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount action 0
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .[all].
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 327681
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 327681
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 327681
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for finit_module action 327681
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .delete_module errno 1.
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for delete_module action 327681
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for delete_module action 327681
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_seccomp - seccomp.c:parse_config_v2:456 - Merging in the compat seccomp ctx into the main one
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_conf - conf.c:run_script_argv:367 - Executing script '/usr/bin/lxd callhook /var/lib/lxd 3 start' for container 'ubuntu-trusty', config section 'lxc'
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_start - start.c:lxc_check_inherited:252 - closed inherited fd 3
            lxc<PHONE_NUMBER>2052.602 INFO     lxc_start - start.c:lxc_check_inherited:252 - closed inherited fd 8
            lxc<PHONE_NUMBER>2052.603 INFO     lxc_monitor - monitor.c:lxc_monitor_sock_name:178 - using monitor sock name lxc/d78a9d7e97b4b375//var/lib/lxd/containers
            lxc<PHONE_NUMBER>2052.639 DEBUG    lxc_start - start.c:setup_signal_fd:290 - sigchild handler set
            lxc<PHONE_NUMBER>2052.640 DEBUG    lxc_console - console.c:lxc_console_peer_default:469 - no console peer
            lxc<PHONE_NUMBER>2052.640 INFO     lxc_start - start.c:lxc_init:489 - 'ubuntu-trusty' is initialized
            lxc<PHONE_NUMBER>2052.640 DEBUG    lxc_start - start.c:__lxc_start:1327 - Not dropping cap_sys_boot or watching utmp
            lxc<PHONE_NUMBER>2052.644 DEBUG    lxc_conf - conf.c:instantiate_veth:2615 - instantiated veth 'veth10J9J1/veth7JXT50', index is '5'
            lxc<PHONE_NUMBER>2052.644 INFO     lxc_cgroup - cgroups/cgroup.c:cgroup_init:68 - cgroup driver cgroupfs-ng initing for ubuntu-trusty
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.deny' set to 'a'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'b *:* m'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c *:* m'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 136:* rwm'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 1:3 rwm'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 1:5 rwm'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 1:7 rwm'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 1:8 rwm'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 1:9 rwm'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 5:0 rwm'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 5:1 rwm'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 5:2 rwm'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 10:229 rwm'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 10:200 rwm'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'memory.limit_in_bytes' set to '5368709120'
            lxc<PHONE_NUMBER>2052.646 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'memory.swappiness' set to '0'
            lxc<PHONE_NUMBER>2052.646 INFO     lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1660 - cgroup has been setup
            lxc<PHONE_NUMBER>2052.713 DEBUG    lxc_conf - conf.c:lxc_assign_network:3058 - move 'eth0' to '14976'
            lxc<PHONE_NUMBER>2052.713 DEBUG    lxc_conf - conf.c:setup_rootfs:1215 - mounted '/var/lib/lxd/containers/ubuntu-trusty/rootfs' on '/usr/lib/x86_64-linux-gnu/lxc'
            lxc<PHONE_NUMBER>2052.713 INFO     lxc_conf - conf.c:setup_utsname:843 - 'ubuntu-trusty' hostname has been setup
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:setup_hw_addr:2146 - mac address '00:16:3e:24:77:71' on 'eth0' has been setup
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:setup_netdev:2373 - 'eth0' has been setup
            lxc<PHONE_NUMBER>2052.733 INFO     lxc_conf - conf.c:setup_network:2394 - network has been setup
            lxc<PHONE_NUMBER>2052.733 INFO     lxc_conf - conf.c:mount_autodev:1072 - Mounting container /dev
            lxc<PHONE_NUMBER>2052.733 INFO     lxc_conf - conf.c:mount_autodev:1095 - Mounted tmpfs onto /usr/lib/x86_64-linux-gnu/lxc/dev
            lxc<PHONE_NUMBER>2052.733 INFO     lxc_conf - conf.c:mount_autodev:1113 - Mounted container /dev
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1707 - mounted 'mqueue' on '/usr/lib/x86_64-linux-gnu/lxc/dev/mqueue', type 'mqueue'
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1657 - remounting /dev/fuse on /usr/lib/x86_64-linux-gnu/lxc/dev/fuse to respect bind or remount options
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1672 - (at remount) flags for /dev/fuse was 4098, required extra flags are 2
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1707 - mounted '/dev/fuse' on '/usr/lib/x86_64-linux-gnu/lxc/dev/fuse', type 'none'
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1657 - remounting /dev/net/tun on /usr/lib/x86_64-linux-gnu/lxc/dev/net/tun to respect bind or remount options
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1672 - (at remount) flags for /dev/net/tun was 4098, required extra flags are 2
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1707 - mounted '/dev/net/tun' on '/usr/lib/x86_64-linux-gnu/lxc/dev/net/tun', type 'none'
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1657 - remounting /proc/sys/fs/binfmt_misc on /usr/lib/x86_64-linux-gnu/lxc/proc/sys/fs/binfmt_misc to respect bind or remount options
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1672 - (at remount) flags for /proc/sys/fs/binfmt_misc was 4096, required extra flags are 0
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1681 - mountflags already was 20480, skipping remount
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1707 - mounted '/proc/sys/fs/binfmt_misc' on '/usr/lib/x86_64-linux-gnu/lxc/proc/sys/fs/binfmt_misc', type 'none'
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1657 - remounting /sys/fs/fuse/connections on /usr/lib/x86_64-linux-gnu/lxc/sys/fs/fuse/connections to respect bind or remount options
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1672 - (at remount) flags for /sys/fs/fuse/connections was 4096, required extra flags are 0
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1681 - mountflags already was 20480, skipping remount
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1707 - mounted '/sys/fs/fuse/connections' on '/usr/lib/x86_64-linux-gnu/lxc/sys/fs/fuse/connections', type 'none'
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1657 - remounting /sys/fs/pstore on /usr/lib/x86_64-linux-gnu/lxc/sys/fs/pstore to respect bind or remount options
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1672 - (at remount) flags for /sys/fs/pstore was 4110, required extra flags are 14
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1707 - mounted '/sys/fs/pstore' on '/usr/lib/x86_64-linux-gnu/lxc/sys/fs/pstore', type 'none'
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1657 - remounting /sys/kernel/debug on /usr/lib/x86_64-linux-gnu/lxc/sys/kernel/debug to respect bind or remount options
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1672 - (at remount) flags for /sys/kernel/debug was 4096, required extra flags are 0
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1681 - mountflags already was 20480, skipping remount
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1707 - mounted '/sys/kernel/debug' on '/usr/lib/x86_64-linux-gnu/lxc/sys/kernel/debug', type 'none'
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1657 - remounting /sys/kernel/security on /usr/lib/x86_64-linux-gnu/lxc/sys/kernel/security to respect bind or remount options
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1672 - (at remount) flags for /sys/kernel/security was 4110, required extra flags are 14
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1707 - mounted '/sys/kernel/security' on '/usr/lib/x86_64-linux-gnu/lxc/sys/kernel/security', type 'none'
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1657 - remounting /var/lib/lxd/devlxd on /usr/lib/x86_64-linux-gnu/lxc/dev/lxd to respect bind or remount options
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1672 - (at remount) flags for /var/lib/lxd/devlxd was 4096, required extra flags are 0
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1681 - mountflags already was 4096, skipping remount
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1707 - mounted '/var/lib/lxd/devlxd' on '/usr/lib/x86_64-linux-gnu/lxc/dev/lxd', type 'none'
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1657 - remounting /var/lib/lxd/devices/ubuntu-trusty/disk.home-fengyu-projects on /usr/lib/x86_64-linux-gnu/lxc/home/fengyu/projects to respect bind or remount options
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1672 - (at remount) flags for /var/lib/lxd/devices/ubuntu-trusty/disk.home-fengyu-projects was 4096, required extra flags are 0
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1681 - mountflags already was 4096, skipping remount
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1707 - mounted '/var/lib/lxd/devices/ubuntu-trusty/disk.home-fengyu-projects' on '/usr/lib/x86_64-linux-gnu/lxc/home/fengyu/projects', type 'none'
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1657 - remounting /var/lib/lxd/shmounts/ubuntu-trusty on /usr/lib/x86_64-linux-gnu/lxc/dev/.lxd-mounts to respect bind or remount options
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1672 - (at remount) flags for /var/lib/lxd/shmounts/ubuntu-trusty was 4096, required extra flags are 0
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1681 - mountflags already was 4096, skipping remount
            lxc<PHONE_NUMBER>2052.733 DEBUG    lxc_conf - conf.c:mount_entry:1707 - mounted '/var/lib/lxd/shmounts/ubuntu-trusty' on '/usr/lib/x86_64-linux-gnu/lxc/dev/.lxd-mounts', type 'none'
            lxc<PHONE_NUMBER>2052.733 INFO     lxc_conf - conf.c:mount_file_entries:1927 - mount points have been setup
            lxc<PHONE_NUMBER>2052.733 INFO     lxc_conf - conf.c:run_script_argv:367 - Executing script '/usr/share/lxcfs/lxc.mount.hook' for container 'ubuntu-trusty', config section 'lxc'
            lxc<PHONE_NUMBER>2052.742 INFO     lxc_conf - conf.c:fill_autodev:1141 - Creating initial consoles under container /dev
            lxc<PHONE_NUMBER>2052.742 INFO     lxc_conf - conf.c:fill_autodev:1152 - Populating container /dev
            lxc<PHONE_NUMBER>2052.742 INFO     lxc_conf - conf.c:fill_autodev:1189 - Populated container /dev
            lxc<PHONE_NUMBER>2052.742 INFO     lxc_conf - conf.c:setup_dev_console:1437 - console has been setup
            lxc<PHONE_NUMBER>2052.742 INFO     lxc_utils - utils.c:mount_proc_if_needed:1726 - I am 1, /proc/self points to '1'
            lxc<PHONE_NUMBER>2052.793 DEBUG    lxc_conf - conf.c:setup_rootfs_pivot_root:1050 - pivot_root syscall to '/usr/lib/x86_64-linux-gnu/lxc' successful
            lxc<PHONE_NUMBER>2052.803 INFO     lxc_conf - conf.c:setup_tty:995 - 0 tty(s) has been setup
            lxc<PHONE_NUMBER>2052.803 INFO     lxc_conf - conf.c:setup_personality:1393 - set personality to '0x0'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_conf - conf.c:setup_caps:2057 - drop capability 'mac_admin' (33)
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_conf - conf.c:setup_caps:2057 - drop capability 'mac_override' (32)
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_conf - conf.c:setup_caps:2057 - drop capability 'sys_time' (25)
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_conf - conf.c:setup_caps:2057 - drop capability 'sys_module' (16)
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_conf - conf.c:setup_caps:2057 - drop capability 'sys_rawio' (17)
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_conf - conf.c:setup_caps:2066 - capabilities have been setup
            lxc<PHONE_NUMBER>2052.803 NOTICE   lxc_conf - conf.c:lxc_setup:3850 - 'ubuntu-trusty' is setup.
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.deny' set to 'a'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'b *:* m'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c *:* m'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 136:* rwm'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 1:3 rwm'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 1:5 rwm'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 1:7 rwm'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 1:8 rwm'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 1:9 rwm'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 5:0 rwm'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 5:1 rwm'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 5:2 rwm'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 10:229 rwm'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'devices.allow' set to 'c 10:200 rwm'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'memory.limit_in_bytes' set to '5368709120'
            lxc<PHONE_NUMBER>2052.803 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1656 - cgroup 'memory.swappiness' set to '0'
            lxc<PHONE_NUMBER>2052.803 INFO     lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:1660 - cgroup has been setup
            lxc<PHONE_NUMBER>2052.803 INFO     lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:238 - changed apparmor profile to lxd-ubuntu-trusty_</var/lib/lxd>
            lxc<PHONE_NUMBER>2052.803 NOTICE   lxc_start - start.c:start:1436 - exec'ing '/sbin/init'
            lxc<PHONE_NUMBER>2052.839 NOTICE   lxc_start - start.c:post_start:1447 - '/sbin/init' started with pid '14976'
            lxc<PHONE_NUMBER>2052.839 WARN     lxc_start - start.c:signal_handler:338 - invalid pid for SIGCHLD
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2052.839 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2140.921 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2140.921 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2140.921 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2424.921 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2424.921 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2424.921 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2424.928 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2424.928 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2424.928 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2431.832 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2431.832 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2431.832 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.380 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.380 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.380 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.384 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.384 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.384 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.384 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.384 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.384 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.384 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.458 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.458 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.458 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.459 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'ubuntu-trusty' is in 'RUNNING' state
            lxc<PHONE_NUMBER>2657.505 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected

It's working perfectly fine, it's just that lxcfs currently doesn't treat swapiness=0 as not having a swap, so it will still show you the swap line in free even if the container is configured not to swap.


Notifications on user subscription

Hi, I'm able to send mail notifications on entry save.
Is it possible even on user subscription?
This is what I tried (without success):
config/notifications.php
'notifications' => [         [             'class' => \craft\elements\User::class,             'event' => \craft\elements\User::EVENT_AFTER_SAVE,             'notification' => \app\notifications\UserSubscribed::class,         ],     ],
notifications/UserSubscribed.php
`
public function via()
{
$user = $this->event->sender;
    if ($user->groups->handle === 'users' && !$this->event->isNew) {
        return [
            'database' => Craft::$app->getUsers()->getUserByUsernameOrEmail('giacomo.carra@paxxion.com'),
        ];
    }

    return [
        'mail' =><EMAIL_ADDRESS>    ];

    return [];
}

`

It is possible to attach notifications to any event, but what you want to do after that I can't really help with as it's very specific to the events being thrown and what's available in them.
Sending a notification when a user is created should be about the same as when an entry is created.

Just use:
if( $this->event->isNew ) {
  return [ 'mail' =><EMAIL_ADDRESS>];
}

Just use:
if( $this->event->isNew ) {
  return [ 'mail' =><EMAIL_ADDRESS>];
}

It works! Thank you


Add field level granularity to reask capability

Imagine we have a guard output structure with 10 fields defined in it and each field has validators. If we make an LLM call and validate that guard, and 9 fields pass validation but 1 fails, then in the current system, we reask for the entire object and substitute the entire object after validation. This is expensive both for the LLM and in terms of the amount of validation we run. Instead, if we could reask ONLY for the missing field and substitute it in after validation, that's much cheaper.

reopening, good feature request


refactor webViewVersion polyfill

webViewVersion polyfill requires to be refactored in the same way simpleView was refactored so that it uses the actual code and not the hardcoded text

It looks like we do not use the getWebviewVersion function anywhere in the code outside of the test file.  Should we just remove webviewVersion.ts/webviewVersion.test.ts or hold onto it for some reason?


linstor-csi is not compatible with Kubernetes 1.14

After upgrade to v1.14 csi driver is not working.
Any attempt to attach the volume ends up with the error err=no volume plugin matched.
I guess problem was caused by moving CSIDriver from csi.storage.k8s.io/v1alpha1 to storage.k8s.io/v1beta1
csi-cluster-driver-registrar log says:
I0326 16:18:08.628649       1 k8s_register.go:69] CSIDriver CRD already had been registered

but kubectl  get csidrivers.csi.storage.k8s.io returns nothing.
csi-cluster-driver-registrar uses quay.io/k8scsi/csi-node-driver-registrar:v1.0.2 image

Yeah, I think you might be right with CSINodeInfo moving to beta.
csi-cluster-driver-registrar is at the latest version and it's quay.io/k8scsi/csi-cluster-driver-registrar:v1.0.1 not quay.io/k8scsi/csi-node-driver-registrar:v1.0.2
Looks like this is the issue https://github.com/kubernetes/kubernetes/pull/74283
I don't have a 1.14 cluster up at the moment, but it might be as simple as changing https://github.com/LINBIT/linstor-csi/blob/master/examples/k8s/deploy/linstor-csi.yaml#L32 that to v1beta1

I don't think that we need any CRD since now.

csidrivers.storage.k8s.io was exsiting after upgrade to v1.14 from beginning.

What about csinodeinfos.csi.storage.k8s.io it was problably moved to csinodes.storage.k8s.io (it is existing from beginning too)

csi-cluster-driver-registrar is at the latest version

I've tested all four versions with same result:
        "v1.0.1", # 2018-12-10T19:53:08.651780702Z
        "v1.0.2", # 2018-12-27T23:22:18.963300422Z
        "canary", # 2019-01-11T23:46:26.53118884Z
        "v1.0-canary" # 2019-02-07T01:46:25.442209631Z

Of course I was updated CusterRole before to storage.k8s.io
https://github.com/LINBIT/linstor-csi/blob/0efd7e8cfa9c61f0dd94c3e30f44a14bfc935017/examples/k8s/deploy/linstor-csi.yaml#L203
replaced

Ok, I have success with the quay.io/k8scsi/csi-cluster-driver-registrar:tmp-test-1.14 version from 2019-03-05T22:03:49.322820892Z. Now driver registered in the right place in the csidrivers.storage.k8s.io

Alight, that's pretty nice and easy. Since 1.14 is less than 24 hours old at this point, I'm going to wait until a more stable release of the csi-cluster-driver-registrar comes out before updating the example deployments.

Yep, csi-attacher now is also not working :)

Hi @haySwim, sorry for the noize, I was little confused in my cluster, currently I can say that current example linstor-csi.yaml is fully compatible with new  Kubernetes v1.14.


Props passed down to route updated only at re-routing

Do you want to request a feature or report a bug
bug
What is the current behavior?
Pass props to a Route like this
<Route exact path="/" render={() => <Home {...this.props} />} />
Home component will receive updated props only at re-routing, but not when they're actually being changed.

Changing the state in parent component does not affect the props of routed component.

Trying to change the route will trigger the re-rendering of updated props in routed component.

Using Switch and Route from 'react-router-native' free of this issue and work as expected.

What is the expected behavior?
Props should change in a routed component when they actually change, not upon re-routing.
Environment (include versions). Did this work in previous versions?

Device: iOS Simulator
OS: ...
React-Native (version): 0.54.2
React-Router-Native (version): 4.2.0
React-Router-Navigation (version): 1.0.0-rc.4

This should be fixed in the version v2.0.0-alpha.7. Let me know if you continue to have any problems with this !


test-branch/execute-job/wrong-commit-sha-on-pr/248ce2b1-fa80-479d-adf2-ad655ef7376b

PR for testing 8aea2f2fc59c4646bca6299e00f27ec0429c6bee

/canonical/self-hosted-runners/run-workflows b810e20942c2916cf233b1182b91fd77fdb40c03


When daily spin limit is reached, let it continue working instead of …

Short Description:
When the daily spin limit is reached, the script exits. This change allow the script to continue but gives a warning that the spin limit is reached every 120 seconds (default which can be changed).
Sample output:
[2016-09-19 11:54:53] [  SpinFort] [INFO] Spun pokestop First Street. Experience awarded: 50. Items awarded: 1x Potion, 2x Pokeball
[2016-09-19 11:54:53] [  SpinFort] [INFO] WARNING! You have reached your daily spin limit
[2016-09-19 11:54:58] [MoveToFort] [INFO] Moving towards pokestop Mosaic Seats - 0.07km
[2016-09-19 11:55:03] [MoveToFort] [INFO] Moving towards pokestop Mosaic Seats - 0.06km
[2016-09-19 11:55:09] [MoveToFort] [INFO] Moving towards pokestop Mosaic Seats - 0.04km
[2016-09-19 11:55:10] [  SpinFort] [INFO] Spun pokestop Mosaic Seats. Experience awarded: 50. Items awarded: 3x Pokeball

It's better to add an option to allow user decide if quit when hit daily limit.
The daily limit is a very good protection.

Here's 2 tests that I did.
If bypass_daily_limit is not changed (default to false), this is the output when daily_spin_limit is reached (it stops the script just like it does right now)
[2016-09-20 15:13:15] [MoveToFort] Moving towards pokestop Sister Cities Bench 1 - 0.04km (attraction of lure 0.04km)
[2016-09-20 15:13:19] [  SpinFort] Spun pokestop Sister Cities Bench 1. Experience awarded: 50. Items awarded: 3x Pokeball
[2016-09-20 15:13:24] [MoveToFort] Moving towards pokestop San Francisco Ferry Terminal Landmark  - 0.05km (attraction of lure 0.05km)
[2016-09-20 15:13:27] [  SpinFort] Spun pokestop San Francisco Ferry Terminal Landmark . Experience awarded: 50. Items awarded: 1x Potion, 2x Pokeball
[2016-09-20 15:13:31] [MoveToFort] Moving towards pokestop In Memory of Herb Caen - 0.08km
[2016-09-20 15:13:37] [MoveToFort] Moving towards pokestop In Memory of Herb Caen - 0.06km
[2016-09-20 15:13:42] [MoveToFort] Moving towards pokestop In Memory of Herb Caen - 0.05km (attraction of lure 0.05km)
[2016-09-20 15:13:47] [  SpinFort] Spun pokestop In Memory of Herb Caen. Experience awarded: 50. Items awarded: 2x Pokeball, 1x Greatball
[2016-09-20 15:13:50] [MoveToFort] Moving towards pokestop Pier 1 1/2, 3 & 5 Historic Site - 0.08km
[2016-09-20 15:13:52] [  SpinFort] WARNING! You have reached your daily spin limit

If bypass_daily_limit is set to true, this is the output when daily_spin_limit is reached which allows the bot to continue doing its business. But it gives a warning from time to time that the daily_spin_limit has been reached
[2016-09-20 15:16:37] [MoveToFort] Moving towards pokestop The River Lines - 0.04km (attraction of lure 0.04km)
[2016-09-20 15:16:39] [  SpinFort] Spun pokestop The River Lines. Experience awarded: 50. Items awarded: 2x Pokeball, 1x Hyper Potion
[2016-09-20 15:16:43] [MoveToFort] Moving towards pokestop Embarcadero Freeway To Nowhere Comes Down - 0.09km
[2016-09-20 15:16:44] [  SpinFort] WARNING! You have reached your daily spin limit
[2016-09-20 15:16:48] [MoveToFort] Moving towards pokestop Embarcadero Freeway To Nowhere Comes Down - 0.07km
[2016-09-20 15:16:54] [MoveToFort] Moving towards pokestop Embarcadero Freeway To Nowhere Comes Down - 0.05km
[2016-09-20 15:16:59] [  SpinFort] Spun pokestop Embarcadero Freeway To Nowhere Comes Down. Experience awarded: 50. Items awarded: 3x Pokeball
....
....
[2016-09-20 15:18:32] [MoveToFort] Moving towards pokestop Pier 7 - 0.04km
[2016-09-20 15:18:35] [  SpinFort] Spun pokestop Pier 7. Experience awarded: 100. Items awarded: 1x Razz Berry, 1x Potion, 3x Pokeball, 1x Revive
[2016-09-20 15:18:39] [MoveToFort] Moving towards pokestop Dangerous Sailor Lives - 0.07km
[2016-09-20 15:18:45] [  SpinFort] WARNING! You have reached your daily spin limit
[2016-09-20 15:18:45] [MoveToFort] Moving towards pokestop Dangerous Sailor Lives - 0.05km

You'll need to rebase this, it's showing a bunch of commits that aren't related to this PR

The only outstanding issue I can see is from @DBa2016 Plus - sometimes, you want actually to continue running and apturing pokemons and sniping even with a reached daily limit.
Maybe this could have a "warning only" mode AS WELL, which generates log messages, but still functions anyway.

So, with this change... these are the possible behaviors now...
If bypass_daily_limit is set to false (which is by default), when the the daily_spin_limit is reached, the script exits which is what is being done today anyway
If bypass_daily_limit is set to true, when the daily_spin_limit is reached, the script continues but gives a warning message every 120 seconds (through the min_interval variable) that the daily_spin_limit has been reached.

OK so dba2016's concern has been addressed. Not sure if we REALLY need that third option then (bypass_daily_limit). Just exit or continue, as it is now.

OK, looks good. Merging.


Create the Front End.

We will be using React for Front End.

Development completed

DEV-TESTING-DEPLOYMENT is successful!
Kudos!!


Perl shebangs should be pinned to a specific version on macOS

Provide a detailed description of the proposed feature
macOS 11.3 changed the default Perl from 5.28 to 5.30. This broke a number of formulae that are built against system Perl 5.28.
Since /usr/bin/perl5.30 exists on all Big Sur versions, I suggest we stop using /usr/bin/perl for shebangs and use the versioned Perl binary instead.
This will also fix an issue where Homebrew formulae break when the user changes the default Perl version themselves (macOS has a defaults property that can do this). For example, Catalina defaults to 5.18 but does support switching the default to 5.28.
The question mostly is how to handle this. If we want to force doing this, then this means effectively making rewrite_shebang detected_perl_shebang, file happen automatically in the Cleaner or similar. This would thus mean it is no longer necessary to rewrite shebangs in the formulae themselves. This however comes with the strong assumption that all the files are designed to be run locally and aren't some remote script to run on a server.
This is linked very closely to #11227 so it makes sense to find a solution here (if we can't do general automatic shebang rewrites then we probably can't solve #11227). The only difference being that what we do here needs to apply to all installs (including builds from source) while #11227 only concerns the bottle.
What is the motivation for the feature?
Doing this means formulae are less prone to break if the default Perl changes, either by Apple or by the user.
How will the feature be relevant to at least 90% of Homebrew users?
Broken formulae are unusable and useless to users.
What alternatives to the feature have been considered?

Using brewed Perl instead.
Bumping minimum macOS to 11.3 and continue to rely on whatever /usr/bin/perl is. Note however that this won't actually fully fix the issue. The user can still change the default Perl themselves (which I suspect some might end up doing in this case).

(I'm happy to do some work on this - mainly opened this for tracking.)

The user can still change the default Perl themselves (which I suspect some might end up doing in this case).

That we never saw anyone doing this before tends to make me think it won't happen. That said, definitely in favour of the "proper" solution here if possible.

Sun May 23 08:26:10 BST 2021
Hi @Bo98 , @MikeMcQuaid .
I've noticed some strange behaviour on my system after:
/usr/local/Cellar/perl/5.34.0 (4,629 files, 96.9MB) *
  Poured from bottle on 2021-05-22 at 05:52:06

and tracked it down to https://github.com/Homebrew/brew/releases/tag/3.1.7 and https://github.com/Homebrew/brew/pull/11286.
All perl 'Apps' - cpan-outdated, cpanm, perlcritic, etc - are no longer using /usr/local/opt/perl (or the preferred /usr/bin/env perl).
After a perl upgrade I normally rebuild/reinstall all perl bundles in ~/perl5/lib/perl5/darwin-thread-multi-2level/auto/ to match the new version.
This did not work yesterday as cpanm is now using /usr/bin/perl (v5.18.4) to rebuild all the bundles, however,  perl is now v5.34.0 - causing a binary mismatch:
Using the example code from Encode::Byte:
           use Encode qw/encode decode/;
           $greek = encode("iso-8859-7", $utf8);  # loads Encode::Byte implicitly
           $utf8  = decode("iso-8859-7", $greek); # ditto

: ; perl /tmp/tt.pl
dyld: lazy symbol binding failed: Symbol not found: _Perl_xs_apiversion_bootcheck
  Referenced from: /Users/m/perl5/lib/perl5/darwin-thread-multi-2level/auto/Encode/Encode.bundle
  Expected in: flat namespace

dyld: Symbol not found: _Perl_xs_apiversion_bootcheck
  Referenced from: /Users/m/perl5/lib/perl5/darwin-thread-multi-2level/auto/Encode/Encode.bundle
  Expected in: flat namespace

[1]    47695 abort      perl /tmp/tt.pl

: ; which perl
/usr/local/bin/perl
➜  Encode
: ; perl -v | head -2

This is perl 5, version 34, subversion 0 (v5.34.0) built for darwin-thread-multi-2level

: ; strings /Users/m/perl5/lib/perl5/darwin-thread-multi-2level/auto/Encode/Encode.bundle | head -14
CMalformed UTF-8 character
UTF-16 surrogate U+%04lX
Code point 0x%lX is not Unicode, may not be portable
Unicode non-character U+%04lX is not recommended for open interchange
ascii
ascii-ctrl
cp1252
iso-8859-1
null
 !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
Encode.c
v5.18.0
3.10
Encode::utf8::decode
➜  Encode
: ;

Any suggestions on the best way to 'fix' this?

Sun May 23 09:15:44 BST 2021
Additionally, everything in ~/perl5/bin is being built using /usr/bin/perl:
: ; pwd
/Users/m/perl5/bin
➜  bin

: ; ls -lat  | ag -i 'may 2' | ag -v 2017
drwxr-xr-x 105 m staff   3360 May 23 09:04 .
-r-xr-xr-x   1 m staff   7013 May 23 09:04 json_xs
-r-xr-xr-x   1 m staff  41663 May 23 08:54 enc2xs
-r-xr-xr-x   1 m staff   2980 May 23 08:54 encguess
-r-xr-xr-x   1 m staff   8271 May 23 08:54 piconv
-r-xr-xr-x   1 m staff   9892 May 23 08:51 shasum
-r-xr-xr-x   1 m staff   9634 May 23 08:51 sha3sum
-r-xr-xr-x   1 m staff    436 May 23 08:48 moose-outdated
-r-xr-xr-x   1 m staff   9993 May 23 08:46 cpanel_json_xs
-r-xr-xr-x   1 m staff   1416 May 23 08:46 pod_cover
-r-xr-xr-x   1 m staff 302729 May 23 08:45 cpanm
-r-xr-xr-x   1 m staff   9079 May 23 07:41 cpan-outdated
-r-xr-xr-x   1 m staff  41013 May 22 17:59 perlcritic
-r-xr-xr-x   1 m staff   4194 May 22 17:45 instmodsh
-r-xr-xr-x   1 m staff 183880 May 22 17:15 perltidy
-r-xr-xr-x   1 m staff   1333 May 22 17:15 podspell
drwxr-xr-x   9 m staff    288 May 22 17:10 ..
-r-xr-xr-x   1 m staff   7138 May 22 11:37 config_data
-r-xr-xr-x   1 m staff  13649 May 22 11:37 prove
-r-xr-xr-x   1 m staff   4981 May 22 11:36 json_pp
➜  bin
: ;

: ; ls -lat  | ag -i 'may 2' | ag -v 2017 | awk '{print $NF}' | xargs head -1 {}
head: {}: No such file or directory
==> . <==
head: Error reading .

==> json_xs <==
#!/usr/bin/perl

==> enc2xs <==
#!/usr/bin/perl

==> encguess <==
#!/usr/bin/perl

==> piconv <==
#!/usr/bin/perl

==> shasum <==
#!/usr/bin/perl

==> sha3sum <==
#!/usr/bin/perl

==> moose-outdated <==
#!/usr/bin/perl

==> cpanel_json_xs <==
#!/usr/bin/perl

==> pod_cover <==
#!/usr/bin/perl -w

==> cpanm <==
#!/usr/bin/perl

==> cpan-outdated <==
#!/usr/bin/env perl

==> perlcritic <==
#!/usr/bin/perl

==> instmodsh <==
#!/usr/bin/perl -w

==> perltidy <==
#!/usr/bin/perl

==> podspell <==
#!/usr/bin/perl

==> .. <==
head: Error reading ..

==> config_data <==
#!/usr/bin/perl

==> prove <==
#!/usr/bin/perl -w

==> json_pp <==
#!/usr/bin/perl
➜  bin
: ;

Possibly related: https://github.com/Homebrew/homebrew-core/issues/77797

3.1.9 has been released to fix this.


Update wallet when a transaction is detected

Closes #847
Closes #679
Description:
This is working pretty well, now the wallet doesn't have to poll and will update automatically when an incoming or outgoing tx is detected.
🎥  PREVIEW

Very nice PR. Amazing video showing it works. :)
I did some lite refactoring, I hope that was OK.
While doing so I figured, that the LCD doesn't return bech32 addresses for key creation: https://github.com/cosmos/cosmos-sdk/pull/1522
E2E tests currently fail until this is resolved.

While doing so I figured, that the LCD doesn't return bech32 addresses for key creation

I'm confused about this, the LCD binary I have from yarn build:gaia does give me bech32 addresses:

Not for the GET /keys endpoint but for the POST /keys endpoint

Ah I see, so creating a new account attempts to decode the non-bech32 address but my try/catch block was obscuring that.

Correct
Matt Bell<EMAIL_ADDRESS>schrieb am Di., 3. Juli 2018, 19:16:

Ah I see, so creating a new account attempts to decode the non-bech32
address but my try/catch block was obscuring that.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/cosmos/voyager/pull/910#issuecomment-402230593, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFmO2dpVSmM2Qk-taTUvF-TEonj-c2w2ks5uC6bZgaJpZM4VAHer
.


[WEB] Feature request: Support WASM by migrating to package:web

Flutter Web WASM-GC support is now available on the beta channel, it would be great to have Pusher WASM ready.
Package web migration guide: https://dart.dev/interop/js-interop/package-web
Based on the Flutter release schedule it is likely WASM support will arrive tot he stable channel in 3 months, it would be great to be ready for it.

Hi, I will pass this request to the team to look into, however at this time we can't commit to a release timeframe

This has also become a blocker for my team and I - Keen to hear if there are plans to provide support for WASM?

No support for WASM yet?


cassandra: support basic auth

Coverage increased (+0.005%) to 80.062% when pulling 44bc4469f6b03afad84dc07451e7d50e67341518 on iksaif:master into 617673a8b7dee01bb61fc2b124a1d3aac5c5e475 on criteo:master.

Coverage increased (+0.005%) to 80.062% when pulling c16a558f3318798b0b8dad0397179a8e9c4c083f on iksaif:master into 617673a8b7dee01bb61fc2b124a1d3aac5c5e475 on criteo:master.

Coverage increased (+0.005%) to 80.062% when pulling 0e6d7b22f14670cda759f26fc16ca84efb4667df on iksaif:master into 617673a8b7dee01bb61fc2b124a1d3aac5c5e475 on criteo:master.


Const constructor can't be declared for a class with a mixin that declares an instance field

Is it a bug or a feature?
mixin A {
  int get prop => 1;
}

class B with A {
  const B();
}

-> Const constructor can't be declared for a class with a mixin that declares an instance field
But this works!
class A {
  const A();
  int get prop => 1;
}

class B extends A {
  const B();
}

This is a bug, int get prop => 1; does not declare an instance field.

Thanks for reporting this issue! This is a duplicate of https://github.com/dart-lang/sdk/issues/37810

Duplicate of https://github.com/dart-lang/sdk/issues/37810


Add cpu oom retry split handling to InternalRowToColumnarBatchIterator

This is a followup to #9929   and is part of addressing issue #8887.
This adds handing for CpuSplitAndRetryOOM in InternalRowToColumnarBatchIterator.
For splits, we divide the target number of rows in half via splitTargetSizeInHalfCpu, and recalculate the buffer sizes from that.  It will try that until we hit 1 row.
I also included a workaround for #10004, by combining the withHostBufferWriteLock with the withHostBufferReadOnly blocks.  In this case we will hold the write lock during the full operation, but this should allow us to proceed without introducing data corruption until we have a fix for #10004.
One other fix is in HostAlloc, where it was passing the wrong argument to RapidsBufferCatalog.synchronousSpill - it was passing allocSize instead of targetSize, causing us to spill a lot more than needed in some cases.

build

build


Add tests for user update attributes

References: https://github.com/rubyforgood/babywearing/issues/200
Description
This PR is adding tests, ensuring that when you visit users/edit the fields will have the user information. Then editing the infos, visiting the page again, and check the fields  one more time.
Type of change

Bug fix (non-breaking change which fixes an issue)

Screenshots

@pollygee I couldn't reproduce the described issue, however I wrote the tests to ensure it.

Ah!  I think the password confirmation wasn't showing predominantly enough - I didn't see it!  Also even after I saw it I couldn't figure out where I needed to put my password in.  I think we'll have to do some updating here, and have a box appear around the password box that is required for the update.
Thanks for checking this out and for adding tests!


Annotator - GET annotations/:global_id/metadata

 To initialize the annotator
    I can request the types of annotators for the object
    And the total for each of those types
    By passing a global_id

Request
/annotations/:global_id/metadata
{
  annotation_target: :global_id,
  annotation_types: {
    notes: { total: 2 },
    depictions: { total: nil }
  }
}

Done.


[UI] Add a message for violated rules

For "Violated Rules" page:

Add a tooltip ( add (i) besides "Violated Rules" header ) to describe what this page shows.

Hey!
Can you assign this issue to me? I would like to work on this issue.

Question: Do we want to display a message, when the page is empty?

We already have a message when the page is empty. Do you want me to add anything else to the message?

I think the current version should be good enough for now. We can open a new issue if we want.


Issue in IE10

This example is not working ie10.screen is not getting rendered.

Are you on the master branch or on the v3.0.0 branch?
I have not cross-browser tested the example at all, so it's possible that this is a bug — do you have any idea what happens?

I have cloned it to my local and then tried running it, through npm start.It is rendering fine in mozilla and chrome ,but in case of IE blank page coming.I have checked the IE's console for any possible errors but it is also coming blank.

This JavaScript environment does not support proto. This means that react-proxy is unable to proxy React components. Features that rely on react-proxy, such as react-transform-hmr, will not function as expected.
SCRIPT5009: 'Promise' is undefined
bundle.js, line 33637 character 88
These 2 errors coming in IE .This application is also not rendering in safari.

Any ideas how to fix that?

You'll need to use the babel-preset-es2015-loose

see https://babeljs.algolia.com/docs/advanced/caveats/#internet-explorer
and https://babeljs.algolia.com/docs/advanced/loose/
for details

Ah thanks @oliverturner!
Do we use anything that loose mode interferes with?

I won't be able to take a look today, sorry :disappointed:

react-proxy is a dependency for react-transform-hmr ,and react-proxy uses proto which is not suppoted in IE10 .so well have to use loose mode .but it is not clear fromthe documentation how to use this mode.

Replace babel-preset-es2015 in the babel config in the package.json with babel-preset-es2015-loose should fix it. The problem is that loose mode has a "few" caveats and we need to make sure we won't run into problems because of that.

not it wasn't of any help .i have checked with other forums also no reoslution ofr this _proto issue.............. is there a way i can remove hot reloading for ie10 or for all browsers.

@mxstbr since hmr is development only and most likely devs will not be developing continuously in IE10 but rather peeking at it every-so-often. It might be ok to make hmr optional and provide a warning in the docs?

We should remove react transform, see #220. That might fix the issue, and if not, we might be able to provide an opt-out env variable so IE10 users can still develop. Does that sound reasonable?

@mxstbr I was just reading up on that issue actually. Interesting read by @gaearon. Covers many of the problems we ran into while trying to use React-Transform. I agree that would probably solve the issue right now. Might still be good to make hmr optional anyway? Removing React-Transform would definitely push it down the todo list though.

I think it'd be a bit awkward to make hmr opt-out and then remove it soon after, I'd rather just remove it and fix the issue that way. :+1:

@mxstbr would you be removing hmr entirely or just react-transform?

Just react-transform, and replace it with the better approach detailed by Dan in that issue!

Closed in favor of #220!


Robot script returncode could inform if execution has been stopped by signal

After stop robot by signal returncode could be for example: STOPPED_BY_USER rc (253).
I think returning the number of failed test cases in this scenario is not the expected result. What do you think?
Current behavior:
(venv) jamoh@jamoh /tmp$ robot example_suite.robot
==============================================================================
Example Suite
==============================================================================
Test Example                                                          ^CSecond signal will force exit.
Test Example                                                          | FAIL |
Execution terminated by signal
------------------------------------------------------------------------------
Example Suite                                                         | FAIL |
1 critical test, 0 passed, 1 failed
1 test total, 0 passed, 1 failed
==============================================================================
Output:  /tmp/output.xml
Log:     /tmp/log.html
Report:  /tmp/report.html
(venv) jamoh@jamoh /tmp$ echo $?
1

Proposal:
(venv) jamoh@jamoh /tmp$ robot example_suite.robot
==============================================================================
Example Suite
==============================================================================
Test Example                                                          ^CSecond signal will force exit.
Test Example                                                          | FAIL |
Execution terminated by signal
------------------------------------------------------------------------------
Example Suite                                                         | FAIL |
1 critical test, 0 passed, 1 failed
1 test total, 0 passed, 1 failed
==============================================================================
Output:  /tmp/output.xml
Log:     /tmp/log.html
Report:  /tmp/report.html
(venv) jamoh@jamoh /tmp$ echo $?
253

Sounds ok to me. Will need someone to implement, test and document it.

I think with current documentation it's clear about what do you expect after stop the execution in Robot Framework User Guide:

RC
Explanation

0
All critical tests passed.

1-249
Returned number of critical tests failed.

250
250 or more critical failures.

251
Help or version information printed.

252
Invalid test data or command line options.

253
Test execution stopped by user.

255
Unexpected internal error.

And about the PR, I'm not confident about the changes I've made (lot of variable forwarding in order to be available at executionresult.py). I would appreciate a review about that, thanks :)
All atests and utests passes with this PR.

what is the status of this issue? I agree that it is good to have a specific rc (253) when task is killed by SIGTERM/ SIGKILL


Once a player joins, rollback runs from tick 0 to current tick

I'm currently focused on other PRs but this is a performance bug which I have to at least bring up.
The following function is inside the class rollback-synchronizer.gd
The below logger I added, reports that a new player joining, runs the below function from tick 0 to whatever tick you joined.
func _get_history(buffer: Dictionary, tick: int) -> Dictionary:
	if buffer.has(tick):
		return buffer[tick]

	if buffer.is_empty():
		return {}

	var earliest = buffer.keys().min()
	var latest = buffer.keys().max()

	if tick < earliest:
		_logger.warning("Tried to load tick %s which is earlier than the earliest we have recorded (%s)
		Try increasing the history limit." % [tick, earliest])
		return buffer[earliest]

	#For inputs, this is extrapolation aka prediction
	#For example, if you move to the right (at latest)
	#at tick, you will still be moving to the right ;)
	if tick > latest:
		return buffer[latest]

	var before: int = buffer.keys() \
		.filter(func (key): return key < tick) \
		.max()

	return buffer[before]

The full stack trace is this:
rollback-synchronizer -> func _prepare_tick(tick: int)
network-rollback -> 		on_prepare_tick.emit(tick)
network-rollback ->   func _rollback()

Below class is network-rollback.gd
func _ready():
	NetworkTime.after_tick_loop.connect(_rollback)

func _rollback():
	if not enabled:
		return

	_is_rollback = true

	# Ask all rewindables to submit their earliest inputs
	_resim_from = NetworkTime.tick
	before_loop.emit()

	# from = Earliest input amongst all rewindables
	var from: int = _resim_from

	# to = Current tick
	var to: int = NetworkTime.tick

	# for tick in from .. to:
	for tick in range(from, to): #FORLOOP FROM 0 TO player_joined_at_tick
		_tick = tick
		_simulated_nodes.clear()

		# Prepare state
		#	Done individually by Rewindables ( usually Rollback Synchronizers )
		#	Restore input and state for tick
		on_prepare_tick.emit(tick) #IT ENTERS HERE

It shouldn't run these loops (imagine if a player joins tick 100000 lol), as at each one, it returns buffer[earliest]
Anyway, needs more investigation, I only stumbled into it while implementing input delay, its not serious even for full games, since normally lobby games start everyone at tick 0 instead of joining at whatever tick

Oh that's a good one! I remember encountering this, maybe I just haven't gotten around to fixing it yet.
I'm considering having a spawned_at field on RollbackSynchronizers to store when they were spawned, and not run any logic on ticks older than that.
Either way, thanks for raising!

I'm considering having a spawned_at field on RollbackSynchronizers to store when they were spawned, and not run any logic on ticks older than that.

This is a great idea, I could even make a PR for it if you wish :)
It is superior to my idea of the player_joined_at_tick variable, since each state is its own thing, instead of caring exclusively for a player (and as you mentioned in that other issue, the context of a player changes in each game)

Spent some time on this, some things to add.

The below logger I added, reports that a new player joining, runs the below function from tick 0 to whatever tick you joined.

It's best to log behavior where it's actually done. In this case, NetworkRollback runs the rollback loop and determines the tick range to be resimulated. Adding logs there shows that this does happen, but only on clients.

Turns out the issue itself stemmed from how the example code was set up. RollbackSynchronizer itself would wait until the time is synced to process settings, but BrawlerController did not. So the initial call would set the _latest_state to tick -1, _earliest_input to 0, causing the resimulation.
Removing the manual calls and deferring the process_settings() call leaves enough time for user code to setup ownership.


Should set template_suffix to '-'

mypy is a file-only linter and should set template_suffix = '-', according to the docs: http://www.sublimelinter.com/en/latest/linter_attributes.html#file-only-linters

Although mypy now supports temporary files with the --shadow-file argument, I decided against using it in #13 because of the slow running time of mypy.
Fixed in #13 (and earlier in #12 it seems, but the issue didn't get closed?).


[PLT-8186] add support for ec2 instance profile authentication

Summary
add support for ec2 instance profile authentication
Ticket Link
github: https://github.com/mattermost/mattermost-server/issues/7875
PR in other repos
server: https://github.com/mattermost/mattermost-server/pull/8243
webapp: https://github.com/mattermost/mattermost-webapp/pull/772
api-reference: https://github.com/mattermost/mattermost-api-reference/pull/336

Will merge when server PR goes in

@jwilander shall we make the same changes to the test email?

@jwilander @enahum @cpanato Server PR is in, so this can now be merged


Upgrade requirements

Codecov Report

Merging #65 (32b7230) into main (8017781) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #65   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           50        49    -1
  Branches         6         6
=========================================
- Hits            50        49    -1

Impacted Files
Coverage Δ

src/django_read_only/__init__.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8017781...32b7230. Read the comment docs.


Add user profile storage

User profile feature provided by Auth is so limited so that I am going to store the basic information for users. And let all user retrieve others' profile by uid to build relationship between records in other tables.

Pull request #11
This pull request just update the current user's displayName and email to table users. Getting back profile by uid has not been done as I am still finding ways to inject firebase.utils in order to use firebase.utils.NormalizedRecord.

But user's displayName actually provided by firebase natively. It's part of the firebase's authentication API.


⚠ Jenkins Plugins Artifactory has degraded performance

In 5afd25d, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 2391 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 3bc10b6 after 41 minutes.


Update http4s-blaze-client, http4s-circe, ... to 0.20.9

Updates

org.http4s:http4s-blaze-client
org.http4s:http4s-circe
org.http4s:http4s-dsl

from 0.20.8 to 0.20.9.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [{ groupId = "org.http4s" }]

labels: semver-patch

oh dear
[error]   not found: /home/travis/.ivy2/local/org.http4s/http4s-core_2.12/0.20.9/ivys/ivy.xml
[error]   download error: Caught java.io.IOException: Server returned HTTP response code: 403 for URL: https://repo1.maven.org/maven2/org/http4s/http4s-core_2.12/0.20.9/http4s-core_2.12-0.20.9.pom (Server returned HTTP response code: 403 for URL: https://repo1.maven.org/maven2/org/http4s/http4s-core_2.12/0.20.9/http4s-core_2.12-0.20.9.pom) while downloading https://repo1.maven.org/maven2/org/http4s/http4s-core_2.12/0.20.9/http4s-core_2.12-0.20.9.pom
[error]   not found: https://dl.bintray.com/ovotech/maven/org/http4s/http4s-core_2.12/0.20.9/http4s-core_2.12-0.20.9.pom
[error]   not found: https://packages.confluent.io/maven/org/http4s/http4s-core_2.12/0.20.9/http4s-core_2.12-0.20.9.pom
[error] 	at coursier.Resolve$.$anonfun$validate$1(Resolve.scala:390)
[error] 	at scala.collection.TraversableLike.$anonfun$map$1(TraversableLike.scala:233)
[error] 	at scala.collection.Iterator.foreach(Iterator.scala:937)
[error] 	at scala.collection.Iterator.foreach$(Iterator.scala:937)
[error] 	at scala.collection.AbstractIterator.foreach(Iterator.scala:1425)
[error] 	at scala.collection.IterableLike.foreach(IterableLike.scala:70)
[error] 	at scala.collection.IterableLike.foreach$(IterableLike.scala:69)
[error] 	at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
[error] 	at scala.collection.TraversableLike.map(TraversableLike.scala:233)
[error] 	at scala.collection.TraversableLike.map$(TraversableLike.scala:226)
[error] 	at scala.collection.AbstractTraversable.map(Traversable.scala:104)
[error] 	at coursier.Resolve$.validate(Resolve.scala:388)
[error] 	at coursier.Resolve.validate0$1(Resolve.scala:139)
[error] 	at coursier.Resolve.$anonfun$ioWithConflicts0$4(Resolve.scala:183)
[error] 	at coursier.util.Task$.$anonfun$flatMap$2(Task.scala:14)
[error] 	at scala.concurrent.Future.$anonfun$flatMap$1(Future.scala:303)
[error] 	at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:37)
[error] 	at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:60)
[error] 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[error] 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[error] 	at java.base/java.lang.Thread.run(Thread.java:834)
[error] (coursierResolutions) coursier.error.ResolutionError$CantDownloadModule: Error downloading org.http4s:http4s-core_2.12:0.20.9
[error]   Not found
[error]   Not found
[error]   not found: /home/travis/.ivy2/local/org.http4s/http4s-core_2.12/0.20.9/ivys/ivy.xml
[error]   download error: Caught java.io.IOException: Server returned HTTP response code: 403 for URL: https://repo1.maven.org/maven2/org/http4s/http4s-core_2.12/0.20.9/http4s-core_2.12-0.20.9.pom (Server returned HTTP response code: 403 for URL: https://repo1.maven.org/maven2/org/http4s/http4s-core_2.12/0.20.9/http4s-core_2.12-0.20.9.pom) while downloading https://repo1.maven.org/maven2/org/http4s/http4s-core_2.12/0.20.9/http4s-core_2.12-0.20.9.pom
[error]   not found: https://dl.bintray.com/ovotech/maven/org/http4s/http4s-core_2.12/0.20.9/http4s-core_2.12-0.20.9.pom
[error]   not found: https://packages.confluent.io/maven/org/http4s/http4s-core_2.12/0.20.9/http4s-core_2.12-0.20.9.pom
[error] Total time: 4 s, completed Aug 7, 2019, 9:29:04 PM

wil presume a transient error, will try again later


Gracefully Handle Setup to Consensus API switch

In apps/guardian-ui/src/GuardianApi.ts the startConsensus method is flaky due to how we currently handle the API switch. The UI gets caught in a "setup" state but in reality, consensus has already started running. A refresh of the UI leads to "method not found" errors as it tries to determine where in the setup process is it.
I have tried a few approaches but none have yielded consistent results.
relevant Discord conversations:
https://discord.com/channels/990354215060795454/990354215878688860/1122657638388338819
https://discord.com/channels/990354215060795454/990354215878688860/1124158861876674571
https://discord.com/channels/990354215060795454/1105908596614627428/1121760876286976071

Can we close this thanks to #52?


shared folders

Description
I have a windows server in my network and my mapped shared folders show up as empty with Files app.
when I access the root folder (\devicename) it shows up some folders but the actual "shared folders" (\mircowinserver\sharedfolders) show up as empty even when mapped as a network drive (Z:)
also network navigation is REALLY slow.
on windows file explorer it works as expected

.
Steps To Reproduce
No response
Expected behavior
expected behavior is to correctly navigate shared folders on the network and not showing drives as empty. and they should be faster to load. as windows explorer is doing.

Files Version
Version: <IP_ADDRESS>
Windows Version
OS Version: 10.0.22000.282
Relevant Assets
No response

Shortcuts do not appear in network folders (UWP limitation). Are all the folder contents shortcuts?

Can we use the full trust process? I seem to remember some limiation that forced us to use the UWP APIs for this.

FindFirstFileFromApp (uwp) was giving access denied on network paths, but I expect FindFirstFile (full trust) to work.

Yep, that's the issue, shortcut on network shares are not shown. Also loading for network shares is much slower than windows explorer.

Merging with #2436


Allow non-byzantine replica to always catch up

Description
Per the classical PBFT implementation, the network is always able to make progress ordering and processing transactions, and the current PBFT implementation supports this.  However, the PBFT protocol does not make any guarantees that just because a node is behaving in a non-byzantine fashion, that it will be able to participate in the network, or that its state will be in sync with the network.  This was discussed somewhat in issue #1120.
Describe How to Reproduce
During any sort of 4 node non-byzantine stress test, one replica will invariably be slower than the other four.  Because of this, three of the replicas will move ahead of the slow replica, and although the fourth replica is no longer actively participating in the ordering, the network will continue to make progress (as it must, otherwise a byzantine node could halt the network).  The lagging replica will initiate state transfer, but by the time state transfer completes, the network will have moved beyond the state which was transferred to, and the replica will remain out of date.  If the network stops receiving requests, the lagging replica is left in a state where it is not up to date, and because it cannot eavesdrop on the network (as there is no activity on the network), it cannot catch up.  This is the scenario observed using the stress tests from @bcbrock.
Simple Solutions

One simple solution to the specific scenario mentioned, would be for the primary to be obligated to issue a null request periodically if a real request is not available.  This would allow the existing eavesdropping mechanism to attempt to recover and rejoin the network.
Unfortunately, issuing null requests by themselves in insufficient to recover from all failing scenarios.  In the event that the network has moved on to a new view, the replica needs to change views to this new view and become active in it.  The replica could eavesdrop on the view for the requests to attempt to make this determination, say, picking the highest view to which f+1 replicas have sent messages in in the same way that we eavesdrop for checkpoints today.
Today, if a state transfer is already in progress, state transfer will accept additional targets, but will not transfer to them unless something goes wrong moving to the current target.  We could introduce some stronger notion of hard and soft targets, where hard targets are minimum targets which must be transferred to, and soft targets can optionally be transferred to.  (The usefulness of a soft target is, imagine with k=10, L=40, targets for seqNo=30, 40, 50 could all be added, and, if successfully transferred to, transactions from that sequence number could be played, as the log overlaps all of them.  If state transfer were guaranteed to be successful to a target, this logic could be simplified considerably).

More Complex Solutions

In order to support dynamically adding additional replicas to the network, and changing the network size, new protocol support will need to be added.  It might be possible to leverage whatever protocol support is added, such as forcing a view change (in a rate limited way) to perform the catchup.
Some other sort of solicitation for the networks current view and last stable checkpoint?  The original paper included a variant of this, that when data for a checkpoint was requested, replicas would reply with higher checkpoints if that checkpoint had already been garbage collected, but this was not implemented because blocks, corresponding to checkpoints are never garbage collected and still provide valid blockchain targets, even if the associated blockchain state is not transferrable.

The first set of solutions would fall under eavesdropping and are attractive because they require very little in ways of protocol modification.  The second approach may be superior technically however.  As this is a protocol problem, input from @vukolic especially is requested, but thoughts from @corecode @kchristidis and @tuand27613 would be welcomed as well.

We were aware of this from our earlier work on SINTRA. The behavior points out the need for a kind of flow control: even when every node is correct, some will be slower, and they should not be left behind. So the leader should progress only as fast so that the correct replias can follow. Unfortunately it is difficult to distinguish correct and slow from faulty.
We should go for the simple solutions. Your suggestions 1 (periodic null reqs) and 2 (listening for view changes) should be done first. The popular Raft consensus (a variant of Paxos) uses such periodic requests combined with listening like this, and the success of Raft shows this works well in practice. If the issues prevail -- but this will only be the case when the system is actually under attack(*) -- then one can still go to the more complex solutions.

There are a number of works exploring actual attacks on BFT protocols. One will have to address this at a later stage, when this is deployed. But PBFT is quite robust to those - one reason for using it.

@cca88 For implementing the periodic null requests, I'd assume that a primary who fails to send them should be considered byzantine and replicas should send a view change message?  I imagine this would be implemented by reusing the existing request timer, rather than stopping it when there are no outstanding requests, simply reset it in anticipation of a new null request?
The logic for detecting the network moving beyond our watermarks is to track the sequence number of the most recent checkpoint issued by each replica.  Then if at least f+1 checkpoint sequence numbers are above our watermarks, we pick the f+1st highest sequence number as being the new low watermark.  If we are eavesdropping for view, then it seems like it would make more sense to simply track the most recently sent sequence number and view number for each replica.  There would then be no requirement to track checkpoints at all, and we could pick the f+1st highest sequence and view number to move our watermarks (rounded to the checkpoint interval) and view to.   Do you see any problems with this?


Update http4s-circe, http4s-dsl, ... to 1.0.0-M43

About this PR
📦 Updates

org.http4s:http4s-circe
org.http4s:http4s-dsl
org.http4s:http4s-ember-client
org.http4s:http4s-ember-server

from 1.0.0-M42 to 1.0.0-M43
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.http4s" }
}]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, version-scheme:early-semver, commit-count:1

Superseded by #88.


1 Pity Navia

The website shows me as having obtained Navia at 1 pity when that clearly isn’t the case.
(I mentioned this on the Discord, but thought this would be the better place to put it long-term.)

Hi, this is a known issue. For more info, please go to our discord, the
channel for testers (#tester-general) and search for "1 pity"
It is due to a problem with indexing and starting the pity count in
correctly, especially if it's the first 5 star of the history (the icon
seen as the bottom of the wishes in the main page). Please chat via discord
and I get back about it.

Han

On Mon, Jun 3, 2024, 01:10 AmberWing @.***> wrote:

default.png (view on web)
https://github.com/dval-in/dvalin-frontend/assets/63614345/272906cc-c488-47e5-a50d-962dcd13b3f9
The website shows me as having obtained Navia at 1 pity when that clearly
isn’t the case.
(I mentioned this on the Discord, but thought this would be the better
place to put it long-term.)
—
Reply to this email directly, view it on GitHub
https://github.com/dval-in/dvalin-frontend/issues/246, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVGOQTE7PFZUR3AGAAMOOJDZFNNYLAVCNFSM6AAAAABIVIFBUWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDSOBQGAYDAMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

This issue should be already resolved for new data. Older data needs to be migrated manually. Will leave this open until older data was migrated.