Revert "Use vanity URL for Reactiflux"

Reverts reactjs/reactjs.org#2372
We're allowing direct links to the #react-native channel again (though #help-react-native is a more popular channel, it's not in the React Native category)

Sorry wrong repository, I thought these were the React Native docs


bug(Theming): Error during theming after switching from 15.0.3 to 17.0.4 version of Angular Material

Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
15.0.3
Description
After switching from version 15.0.3 to version 17.0.4, I get an error when theming, namely when using the background value, there was no such error in 15.0.3 and everything worked correctly
(status-bar: #e0e0e0, app-bar: #f5f5f5, background: #fafafa, hover: rgba(0, 0, 0, 0.04),
card: white, dialog: white, disabled-button: rgba(0, 0, 0, 0.12), raised-button: white,
focused-button: rgba(0, 0, 0, 0.12), selected-button: #e0e0e0,
selected-disabled-button: #bdbdbd, disabled-button-toggle: #eeeeee,
unselected-chip: #e0e0e0, disabled-list-option: #eeeeee, tooltip: #616161)
isn't a valid CSS value.
    ╷
 │   $background-color: mat-color($_background, background);
    │                                ^^^^^^^^^^^^ value
    │                      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
unknown function treated as plain CSS

Reproduction
StackBlitz link: stackblitz
Steps to reproduce:

the error appears when building the application

Expected Behavior
When theming, I want to use the background and foreground values
Actual Behavior
I get an error when theming, namely when using the background value,
Environment

Angular: 17.0.7
CDK/Material: 17.0.4
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows

It looks like you're using the deprecated @import Sass API that was removed in v17 https://github.com/angular/components/pull/27571. You can replace the mat-color by adding @use '@angular/material' as mat to the top of the file and using mat.get-color-from-palette().


e2e networking.go namespaces are not being created

odd, but when i run e2e's like networking.go, I'm finding that the namespace created by it nettest-1234 is not listed in kubectl get namespaces.
So, does this mean that "get namespaces" doesnt gaurantee to return all namespaces, or is it a bug ? If the former, the spec should be changed.
This can easily be reproduced from head.

run networking.go
while running, run watch -n 1 cluster/kubect.sh get namespaces

And you will only see 'default' in the list.

It should list all namespaces.
Is e2e cleaning up after itself
Will investigate to see if I can reproduce
Sent from my iPhone

On Apr 7, 2015, at 5:57 PM, Clayton Coleman<EMAIL_ADDRESS>wrote:
Assigned #6539 to @derekwaynecarr.
—
Reply to this email directly or view it on GitHub.

hmm .ok thanks ! i'll try to see if i can find a good reproducer.
also i  can help to  add a e2e test to kubectl for this

@derekwaynecarr Where does kubectl look for namespaces?  I assume under /registry/namespaces and the namespaces created by the e2e test never get put there.  Pods, events, etc get put under a directory for the namespace but nothing is put under /registry/namespaces.  I assume that is why get namespaces doesn't show them.

@jayunit100 @rrati - kubectl will call the rest api, so v1beta3/namespaces, which will look in etcd under /registry/namespaces.
i do not know much about networking.go, but it looks like it creates some stuff in the default namespace, and some other stuff in a nettest-* namespace.  There is no call that is explicitly creating those namespaces, so the NamespaceAutoProvision admission control plug-in should create one when getting the request for you.
Do you know if that admission_control flag is set on your e2e environment for kube-apiserver to include admission_control=NamespaceAutoProvision?

I am updating the issue text to be a little more prescriptive of the scenario since kubectl get namespaces itself works fine, but in the test scenario, the e2e test is not getting the namespace created.

thanks were looking into this

@rrati and @derekwaynecarr have helped me resolve this, with the following config at the end of /etc/kuberentes/apiserver ...
admission_control=NamespaceLifecycle,NamespaceAutoProvision,AlwaysAdmit"

So i guess as follow on we need to make sure the ns exists before proceeding w/ tests in e2es.

The options should result in the ns being created on the fly, so no need to try to create a head of time.  Not yet anyway

Issue appears resolve,d, closing.

confirmed removed and updating test ^ above so that namespace is bootstrapped / killed properly. thanks for helping with this one derek !


Expose old config field for api < 1.19

/cc @icecrime @calavera @aanand
I tried everything (99.9999% sure) before going with a second function just for < 1.19 code path :angel:
fixes #13663
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

LGTM

One comment, it's not really an issue for me, but I know some people will complain.
When talking to the daemon using the API 1.18, you the the resources both in Config AND HostConfig
Using docker-1.6.1 against this branch, I did a docker run -d --name test -m 20m busybox ping google.com
This is the inspect:
{
    "Id": "65080757ba6b435a3a295e7175afa4824e227729289d0069458bc837dee0a242",
    "Created": "2015-06-02T22:02:01.844734237Z",
    "Path": "ping",
    "Args": [
        "google.com"
    ],
    "State": {
        "Running": true,
        "Paused": false,
        "Restarting": false,
        "OOMKilled": false,
        "Dead": false,
        "Pid": 27140,
        "ExitCode": 0,
        "Error": "",
        "StartedAt": "2015-06-02T22:02:01.981596487Z",
        "FinishedAt": "0001-01-01T00:00:00Z"
    },
    "Image": "8c2e06607696bd4afb3d03b687e361cc43cf8ec1a4a725bc96e39f05ba97dd55",
    "NetworkSettings": {
        "Bridge": "",
        "EndpointID": "2e0c684e6ce05f1db40215852634eee669d06db054d6babbf5759f552dcdc092",
        "Gateway": "<IP_ADDRESS>",
        "GlobalIPv6Address": "",
        "GlobalIPv6PrefixLen": 0,
        "HairpinMode": false,
        "IPAddress": "<IP_ADDRESS>",
        "IPPrefixLen": 16,
        "IPv6Gateway": "",
        "LinkLocalIPv6Address": "",
        "LinkLocalIPv6PrefixLen": 0,
        "MacAddress": "02:42:5f:fa:8a:df",
        "NetworkID": "151b1ecce18213df39aba6e511fb766f62ebd36fb166a8653f2fcf2c299e6bde",
        "PortMapping": null,
        "Ports": {},
        "SandboxKey": "/var/run/docker/netns/65080757ba6b",
        "SecondaryIPAddresses": null,
        "SecondaryIPv6Addresses": null
    },
    "ResolvConfPath": "/var/lib/docker/containers/65080757ba6b435a3a295e7175afa4824e227729289d0069458bc837dee0a242/resolv.conf",
    "HostnamePath": "/var/lib/docker/containers/65080757ba6b435a3a295e7175afa4824e227729289d0069458bc837dee0a242/hostname",
    "HostsPath": "/var/lib/docker/containers/65080757ba6b435a3a295e7175afa4824e227729289d0069458bc837dee0a242/hosts",
    "LogPath": "/var/lib/docker/containers/65080757ba6b435a3a295e7175afa4824e227729289d0069458bc837dee0a242/65080757ba6b435a3a295e7175afa4824e227729289d0069458bc837dee0a242-json.log",
    "Name": "/test",
    "RestartCount": 0,
    "Driver": "aufs",
    "ExecDriver": "native-0.2",
    "MountLabel": "",
    "ProcessLabel": "",
    "Volumes": {},
    "VolumesRW": {},
    "AppArmorProfile": "",
    "ExecIDs": null,
    "HostConfig": {
        "Binds": null,
        "ContainerIDFile": "",
        "LxcConf": [],
        "Memory": 20971520,
        "MemorySwap": -1,
        "CpuShares": 0,
        "CpuPeriod": 0,
        "CpusetCpus": "",
        "CpusetMems": "",
        "CpuQuota": 0,
        "BlkioWeight": 0,
        "OomKillDisable": false,
        "Privileged": false,
        "PortBindings": {},
        "Links": null,
        "PublishAllPorts": false,
        "Dns": null,
        "DnsSearch": null,
        "ExtraHosts": null,
        "VolumesFrom": null,
        "Devices": [],
        "NetworkMode": "bridge",
        "IpcMode": "",
        "PidMode": "",
        "UTSMode": "",
        "CapAdd": null,
        "CapDrop": null,
        "RestartPolicy": {
            "Name": "no",
            "MaximumRetryCount": 0
        },
        "SecurityOpt": null,
        "ReadonlyRootfs": false,
        "Ulimits": null,
        "LogConfig": {
            "Type": "json-file",
            "Config": {}
        },
        "CgroupParent": ""
    },
    "Config": {
        "Hostname": "65080757ba6b",
        "Domainname": "",
        "User": "",
        "AttachStdin": false,
        "AttachStdout": false,
        "AttachStderr": false,
        "ExposedPorts": null,
        "Tty": false,
        "OpenStdin": false,
        "StdinOnce": false,
        "Env": null,
        "Cmd": [
            "ping",
            "google.com"
        ],
        "Image": "busybox",
        "Volumes": null,
        "VolumeDriver": "",
        "WorkingDir": "",
        "Entrypoint": null,
        "NetworkDisabled": false,
        "MacAddress": "",
        "OnBuild": null,
        "Labels": {},
        "Memory": 20971520,
        "MemorySwap": -1,
        "CpuShares": 0,
        "Cpuset": ""
    }
}

As you can see 20971520 is displayed twice.

@vieux I'm aware of this (while testing I came with your extact situation) but I think new fields are always exposed to older api so I didn't care. Is this really a problem? (I can find a way to fix this but as per what I just said I don't think we should care)

@runcom it's fine by me, I juste wanted to make sure you were aware.
LGTM

@vieux that happens with docker 1.6.1 too because those fields where duplicated:
[{
    "AppArmorProfile": "",
    "Args": [
        "google.com"
    ],
    "Config": {
        "AttachStderr": false,
        "AttachStdin": false,
        "AttachStdout": false,
        "Cmd": [
            "ping",
            "google.com"
        ],
        "CpuShares": 0,
        "Cpuset": "",
        "Domainname": "",
        "Entrypoint": null,
        "Env": null,
        "ExposedPorts": null,
        "Hostname": "bfad39cd32f5",
        "Image": "busybox",
        "Labels": {},
        "MacAddress": "",
        "Memory": 20971520,
        "MemorySwap": -1,
        "NetworkDisabled": false,
        "OnBuild": null,
        "OpenStdin": false,
        "PortSpecs": null,
        "StdinOnce": false,
        "Tty": false,
        "User": "",
        "Volumes": null,
        "WorkingDir": ""
    },
    "Created": "2015-06-02T22:20:48.616028128Z",
    "Driver": "aufs",
    "ExecDriver": "native-0.2",
    "ExecIDs": null,
    "HostConfig": {
        "Binds": null,
        "CapAdd": null,
        "CapDrop": null,
        "CgroupParent": "",
        "ContainerIDFile": "",
        "CpuShares": 0,
        "CpusetCpus": "",
        "Devices": [],
        "Dns": null,
        "DnsSearch": null,
        "ExtraHosts": null,
        "IpcMode": "",
        "Links": null,
        "LogConfig": {
            "Config": null,
            "Type": "json-file"
        },
        "LxcConf": [],
        "Memory": 20971520,
        "MemorySwap": -1,
        "NetworkMode": "bridge",
        "PidMode": "",
        "PortBindings": {},
        "Privileged": false,
        "PublishAllPorts": false,
        "ReadonlyRootfs": false,
        "RestartPolicy": {
            "MaximumRetryCount": 0,
            "Name": "no"
        },
        "SecurityOpt": null,
        "Ulimits": null,
        "VolumesFrom": null
    },
    "HostnamePath": "/var/lib/docker/containers/bfad39cd32f577bf7853028cb0dfaeb2c4230e4aba14cf346541e04d0507d859/hostname",
    "HostsPath": "/var/lib/docker/containers/bfad39cd32f577bf7853028cb0dfaeb2c4230e4aba14cf346541e04d0507d859/hosts",
    "Id": "bfad39cd32f577bf7853028cb0dfaeb2c4230e4aba14cf346541e04d0507d859",
    "Image": "8c2e06607696bd4afb3d03b687e361cc43cf8ec1a4a725bc96e39f05ba97dd55",
    "LogPath": "/var/lib/docker/containers/bfad39cd32f577bf7853028cb0dfaeb2c4230e4aba14cf346541e04d0507d859/bfad39cd32f577bf7853028cb0dfaeb2c4230e4aba14cf346541e04d0507d859-json.log",
    "MountLabel": "",
    "Name": "/test1",
    "NetworkSettings": {
        "Bridge": "docker0",
        "Gateway": "<IP_ADDRESS>",
        "GlobalIPv6Address": "",
        "GlobalIPv6PrefixLen": 0,
        "IPAddress": "<IP_ADDRESS>",
        "IPPrefixLen": 16,
        "IPv6Gateway": "",
        "LinkLocalIPv6Address": "fe80::42:acff:fe11:6",
        "LinkLocalIPv6PrefixLen": 64,
        "MacAddress": "02:42:ac:11:00:06",
        "PortMapping": null,
        "Ports": {}
    },
    "Path": "ping",
    "ProcessLabel": "",
    "ResolvConfPath": "/var/lib/docker/containers/bfad39cd32f577bf7853028cb0dfaeb2c4230e4aba14cf346541e04d0507d859/resolv.conf",
    "RestartCount": 0,
    "State": {
        "Dead": false,
        "Error": "",
        "ExitCode": 0,
        "FinishedAt": "0001-01-01T00:00:00Z",
        "OOMKilled": false,
        "Paused": false,
        "Pid": 10572,
        "Restarting": false,
        "Running": true,
        "StartedAt": "2015-06-02T22:20:48.719311857Z"
    },
    "Volumes": {},
    "VolumesRW": {}
}
]

@calavera ok thanks!

:cake:

cherry-picked


Move line up/down buggy with Arrays of literal objects

Haxe code:
class Main
{
	static function main()
	{
		var a:Array = [
			{value: 'a'},
			{value: 'b'},
			{value: 'c'},
			{value: 'd'},
			{value: 'e'},
		];
	}
}

Put the cursor on line with value e, press Ctrl-Alt-Up.
Expected result: object values in order a,b,c,e,d
Actual result: object values in order a,b,d,e,c
Problem seems to be triggered by curly braces.

I can reproduce it in both release and development versions.
To add: instead of just the current line, the line above is selected as well, regardless of whether it's MoveLineUp or Down:

Hey! I got a question for you. Your code above contains an array written in multi-line where two brackets [] are not on the same line. Now the problem is that when I use the code-formatter, it compresses all the elements in the array into one line, like "var a:Array = [{value: 'a'}, {value: 'b'}, ...]". The code formatter is a good tool but this is really annoying especially when there is a lot of elements in one array. Do you guys have any ideas about how to make multi-line array available so the code-formatter can keep it? Thank you very much.

open a new issue

Okay, that's fine, I fixed it. Thanks you.


Consider migrating from jcenter

Jfrog is going to deprecate and disable jcenter services - artifact migration will be needed
https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

Jcenter will stay as read only repository indefinitely, so I'll be closing this issue.
Quote from the article above:
UPDATE 4/27/2021: We listened to the community and will keep JCenter as a read-only repository indefinitely. Our customers and the community can continue to rely on JCenter as a reliable mirror for Java packages.

Thanks! 😁
I'll try to comment on this issue when I migrate my libraries to jcenter 😊


Request: Verbose flag

It would be helpful to be able to toggle the verbose flag when running compatible actions (i.e. validate) for debugging and testing purposes.

Hi, @lowlydba. We're in the process of transition over to our new verified github actions here: https://github.com/liquibase-github-actions.
They support all command parameters and global parameters. So for your example: https://github.com/liquibase-github-actions/validate does support the logLevel flag.
steps:
- uses: actions/checkout@v3
- uses<EMAIL_ADDRESS>  with:
    changelogFile: ""
    url: ""
    logLevel: INFO


TV Turn off while video playback.

While playing local video files, the Automatic Blank feature still turns off the TV. I wish that this can be fixed.
Semi-related question, isn't it possible to hook into windows screensaver feature and if screensaver gets turned on then the LG Companion app would turn off (automatic blank) the TV? I'm asking because windows screensaver was what used before using the LGTV Companion and in that one regard its better and I'd honestly keep using it if the TV didn't turn off completely hours later and i'd have to use the remote.

While playing local video files, the Automatic Blank feature still turns off the TV.

My understanding is that this is working as intended for this feature. See #13.

Semi-related question, isn't it possible to hook into windows screensaver feature and if screensaver gets turned on then the LG Companion app would turn off (automatic blank) the TV?

I'm not sure I understand your use case. Currently with LGTVCompanion you have two options besides the "automatic blank" feature:

Use the "blank" Windows screensaver: sends a black signal to the TV when the Windows screensaver timeout kicks in. Prevents burn-in since no picture is displayed.

Downside: the TV is not turned off (and therefore still uses some power - I measured about 50W with my 77" G1).
Upside: the picture comes back instantly as soon as you move the mouse. Or:

Configure Windows power options to turn off the display after some time. LGTVCompanion will detect that Windows wants to turn off the display and will automatically send a "power off" command to the TV when that happens. When Windows wants to turn the display back on (e.g. because you moved the mouse), LGTVCompanion detects that as well and automatically turns the TV back on.

The TV is completely powered off in that case, so it uses no power, but that also means it takes a few seconds to get it running again.

Obviously you can also use both approaches at the same time which is what I do: blank screensaver after 3 minutes, turn off display after 30 minutes.

Hi @Battler624
1 This is actually by design, since the idea of the feature is to be a more "aggressively" configured screen saver. If you want windows/apps to be able to override/negate the screensaver, f e during gaming, watching a video etc then a normal blank windows screensaver can suffice. You are right that there is a case where you may have to use the remote and that is when th TV automatically turns itself off after some time, because windows does not know about it. To avoid the case where you have to use the remote to turn on the TV after it has been automatically shut off (by the TV itself) you can:

either adjust the settings in the TV to never automatically turn the TV off, and/or
Set windows power savings to turn off the TV after some time, maybe 30-60 minutes of idle. Then you can just wiggle the mouse to power on/activate the monitor again

2 And yes it's possible to detect when the screensaver launch but see my answer to 1 :)

@dechamps you beat me to it :)

Thank you for you replies and #13 definitely shed some light on what I was thinking.
The whole idea about keeping the "auto poweroff" feature is to for the TV to run whatever OLED Care features it needs to run.
I'm going to follow what @dechamps is doing, it fits me exactly, again thank you both @dechamps @JPersson77.
I still do believe a middle-ground is doable (Companion app takes over if windows screensaver is detected, if not detected with 30 minutes of "idle" it'll do the automatic blank thing) but I totally dont mind the current stance

Closing this issue since v1.9.0 implements more options for controlling the granularity of user idle mode and I don't have further plans to let the app hook onto the windows screensaver


i18n: Added Romanian translation

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

i18n: Internationalization or localization changes

Changelog Entry
Description
i18n Added Romanian translation
Added
i18n Added Romanian translation

Thanks!


recommendation: use AMAZON.SearchQuery for VideoQuery slot type

as title

Thanks for the suggestion. I think there was a reason I decided to use a custom query instead of AMAZON.SearchQuery, but I've since forgot it haha. I'll look into this.


Feature Request: ability to turn off autodetection languages/stacks

Yesterday I found myself in a situation where autodetection was preventing me from installing the right version of nodejs. I managed to set 18.7.0 even though the releases already have 18.9.1 and it is available for installation via nix.
It would be useful to be able to manage versions more flexibly, without engines field in package.json.

Wait, is it done in https://github.com/jetpack-io/devbox/pull/222?

Hey @Satont! We're working on turning this on for an upcoming release, so that developers can manage the version directly in their devbox.json. I think this will be out in the next release.

This should be addressed in #227

Closed with #227


Update version json-schema-to-zod

json-schema-to-zod  the current version is very far behind, and the newer version has a great many improvements

thank you.


Automatically redirect root URL of api to the docs

Currently, navigating to only https://api.neurobagel.org/ when connected to the McGill network results in a response of {"detail":"Not Found"}
To prevent users from hitting this message, implement the below behaviour for now:
https://api.neurobagel.org/ --> https://api.neurobagel.org/docs
https://api.neurobagel.org/query --> https://api.neurobagel.org/query

NGINX configuration file for api.neurobagel.org updated to allow redirection from root to /docs.


Crouton won't re-enter linux (Samsung ARM Chromebook)

Hey guys,
I've been trying to install ubuntu on my chromebook (Samsung ARM) for days now, and every time installation works fine and I can enter ubuntu anything from one to four times, but eventually I either get the following message:
"chronos@localhost / $ sudo startunity
Entering /usr/local/chroots/precise...
[dix] Could not init font path element /usr/share/fonts/X11/misc, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list!
[dix] Could not init font path element /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list!
/usr/bin/xinit: XFree86_VT property unexpectedly has 0 items instead of 1
crouton: version 1-20150402135305~master:37dc572e
release: precise
architecture: armhf
xmethod: xephyr
targets: unity
host: version 6680.81.0 (Official Build) stable-channel daisy
kernel: Linux localhost 3.8.11 #1 SMP Thu Apr 2 00:21:50 PDT 2015 armv7l armv7l armv7l GNU/Linux
freon: no
Running exit commands...
/usr/bin/xinit: connection to X server lost
waiting for X server to shut down Hangup
Unmounting /usr/local/chroots/precise..."
Or (a few times this happened) the CHROMEBOOK actually wipes itself for no apparent reason!
I then get a prompt saying the computer is doing some kind of self-repair, then it restarts and everything's gone.
By the way, this is true for unity and xfce. I also tried lxde, which seemed to be more stable but I want to run either unity or xfce.
Any help would be greatly appreciated!
Thanks,

@tempsave did you resolve this? I'm running a similar setup on the Samsung ARM 303 model, on the stable channel, with no issues with xfce with precise or trusty. Any addl. info.?

Looks to me like hardware failure of the mmc/ssd -> data corruption.
@tempsave You could take a look at dmesg if there are some errors. Also
does the self repair happen without running a chroot?
On Mon, Apr 6, 2015 at 6:46 PM, tedm<EMAIL_ADDRESS>wrote:

@tempsave https://github.com/tempsave did you resolve this? I'm running
a similar setup on the Samsung ARM 303 model, on the stable channel, with
no issues with xfce with precise or trusty. Any addl. info.?
—
Reply to this email directly or view it on GitHub
https://github.com/dnschneid/crouton/issues/1572#issuecomment-90146534.

Hey guys,
@tedm No, I did not resolve it yet. What do you mean by on the stable channel?
@divx118 Thank you. The self repair happens completely by itself, when in Chrome OS. The computer turns off and goes into what looks like the developer mode prompt/waiting screen, except it says something about the self repair. Below is the output of dmesg
BEGIN OUTPUT
chronos@localhost / $ dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.8.11 (chrome-bot@build44-m2) (gcc version 4.9.x-google 20140827 (prerelease) (4.9.1_cos_gg_2f9796c_4.9.1-r82) ) #1 SMP Thu Apr 2 00:21:50 PDT 2015
[    0.000000] CPU: ARMv7 Processor [410fc0f4] revision 4 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: SAMSUNG EXYNOS5 (Flattened Device Tree), model: Google Snow
[    0.000000] Ramoops: 41f00000 - 41ffffff
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] CPU EXYNOS5250 (id 0x43520010)
[    0.000000] On node 0 totalpages: 519936
[    0.000000]   Normal zone: 1520 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 188688 pages, LIFO batch:31
[    0.000000]   HighMem zone: 2576 pages used for memmap
[    0.000000]   HighMem zone: 327152 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 9 pages/cpu @c0032000 s13952 r8192 d14720 u36864
[    0.000000] pcpu-alloc: s13952 r8192 d14720 u36864 alloc=9*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 515840
[    0.000000] Kernel command line: cros_secure console= console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2506752 verity payload=PARTUUID=6463ec5b-6277-c14a-acbc-5c9a7154c035/PARTNROFF=1 hashtree=PARTUUID=6463ec5b-6277-c14a-acbc-5c9a7154c035/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=10cdbc993010cc914d17a9645813c5a6931988e6 salt=c8d02530f097c1e313449a5090ed8c56646be9dc4932a9a45badf09ab4722a16" noinitrd vt.global_cursor_default=0 kern_guid=6463ec5b-6277-c14a-acbc-5c9a7154c035
[    0.000000] device-mapper: init: will configure 1 devices
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] __ex_table already sorted, skipping sort
[    0.000000] Memory: 31MB 16MB 216MB 1768MB = 2031MB total
[    0.000000] Memory: 2048796k/2066204k available, 30948k reserved, 1317632K highmem
[    0.000000] Virtual kernel memory layout:
vector  : 0xffff0000 - 0xffff1000   (   4 kB)
fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
modules : 0xbf000000 - 0xbfe00000   (  14 MB)
.text : 0xc0008000 - 0xc0935fd0   (9400 kB)
.init : 0xc0a00000 - 0xc0a4f680   ( 318 kB)
.data : 0xc0b00000 - 0xc0b80000   ( 512 kB)
.bss : 0xc0b80000 - 0xc0c12000   ( 584 kB)
[    0.000000] SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
[    0.000000] NR_IRQS:693
[    0.000000] GIC physical location is 0x10481000
[    0.000000] Exynos5250: clock setup completed, armclk=1700000000
[    0.000000] Exynos: Audss: clock setup completed
[    0.000000] Architected local timer running at 24.00MHz (phys).
[    0.000000] Switching to timer-based delay loop
[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[    0.000000] Initial usec timer 27077638
[    0.000000] Ignoring duplicate/late registration of read_current_timer delay
[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[    0.000000] Console: colour dummy device 80x30
[    0.000291] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000)
[    0.000301] pid_max: default: 32768 minimum: 301
[    0.000397] Security Framework initialized
[    0.000404] Yama: becoming mindful.
[    0.000454] Mount-cache hash table entries: 512
[    0.008914] Initializing cgroup subsys freezer
[    0.008944] CPU: Testing write buffer coherency: ok
[    0.008967] ftrace: allocating 21163 entries in 63 pages
[    0.027692] /cpus/cpu@0 missing clock-frequency property
[    0.027702] /cpus/cpu@1 missing clock-frequency property
[    0.027727] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.027755] Setting up static identity map for 0x4063b710 - 0x4063b768
[    0.028808] CPU1: Booted secondary processor
[    0.028830] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.028874] Brought up 2 CPUs
[    0.028885] SMP: Total of 2 processors activated (96.00 BogoMIPS).
[    0.029292] devtmpfs: initialized
[    0.036296] xor: measuring software checksum speed
[    0.082589]    arm4regs  :  3011.200 MB/sec
[    0.132634]    8regs     :  3004.800 MB/sec
[    0.182678]    32regs    :  2834.400 MB/sec
[    0.182684] xor: using function: arm4regs (3011.200 MB/sec)
[    0.182691] pinctrl core: initialized pinctrl subsystem
[    0.182925] regulator-dummy: no parameters
[    0.183090] NET: Registered protocol family 16
[    0.183307] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.183314] Last reset was software reset (RST_STAT=0x20000000)
[    0.184027] gpiochip_add: registered GPIOs 0 to 7 on device: gpa0
[    0.184061] gpiochip_add: registered GPIOs 8 to 13 on device: gpa1
[    0.184093] gpiochip_add: registered GPIOs 14 to 21 on device: gpa2
[    0.184127] gpiochip_add: registered GPIOs 22 to 26 on device: gpb0
[    0.184158] gpiochip_add: registered GPIOs 27 to 31 on device: gpb1
[    0.184193] gpiochip_add: registered GPIOs 32 to 35 on device: gpb2
[    0.184227] gpiochip_add: registered GPIOs 36 to 39 on device: gpb3
[    0.184259] gpiochip_add: registered GPIOs 40 to 46 on device: gpc0
[    0.184290] gpiochip_add: registered GPIOs 47 to 50 on device: gpc1
[    0.184324] gpiochip_add: registered GPIOs 51 to 57 on device: gpc2
[    0.184356] gpiochip_add: registered GPIOs 58 to 64 on device: gpc3
[    0.184387] gpiochip_add: registered GPIOs 65 to 68 on device: gpd0
[    0.184419] gpiochip_add: registered GPIOs 69 to 76 on device: gpd1
[    0.184457] gpiochip_add: registered GPIOs 77 to 83 on device: gpc4
[    0.184488] gpiochip_add: registered GPIOs 84 to 89 on device: gpy0
[    0.184519] gpiochip_add: registered GPIOs 90 to 93 on device: gpy1
[    0.184554] gpiochip_add: registered GPIOs 94 to 99 on device: gpy2
[    0.184586] gpiochip_add: registered GPIOs 100 to 107 on device: gpy3
[    0.184618] gpiochip_add: registered GPIOs 108 to 115 on device: gpy4
[    0.184652] gpiochip_add: registered GPIOs 116 to 123 on device: gpy5
[    0.184685] gpiochip_add: registered GPIOs 124 to 131 on device: gpy6
[    0.184719] gpiochip_add: registered GPIOs 132 to 139 on device: gpx0
[    0.184754] gpiochip_add: registered GPIOs 140 to 147 on device: gpx1
[    0.184788] gpiochip_add: registered GPIOs 148 to 155 on device: gpx2
[    0.184820] gpiochip_add: registered GPIOs 156 to 163 on device: gpx3
[    0.185775] gpiochip_add: registered GPIOs 164 to 171 on device: gpe0
[    0.185809] gpiochip_add: registered GPIOs 172 to 173 on device: gpe1
[    0.185842] gpiochip_add: registered GPIOs 174 to 177 on device: gpf0
[    0.185878] gpiochip_add: registered GPIOs 178 to 181 on device: gpf1
[    0.185911] gpiochip_add: registered GPIOs 182 to 189 on device: gpg0
[    0.185943] gpiochip_add: registered GPIOs 190 to 197 on device: gpg1
[    0.185979] gpiochip_add: registered GPIOs 198 to 199 on device: gpg2
[    0.186011] gpiochip_add: registered GPIOs 200 to 203 on device: gph0
[    0.186044] gpiochip_add: registered GPIOs 204 to 211 on device: gph1
[    0.186373] gpiochip_add: registered GPIOs 212 to 219 on device: gpv0
[    0.186406] gpiochip_add: registered GPIOs 220 to 227 on device: gpv1
[    0.186443] gpiochip_add: registered GPIOs 228 to 235 on device: gpv2
[    0.186476] gpiochip_add: registered GPIOs 236 to 243 on device: gpv3
[    0.186508] gpiochip_add: registered GPIOs 244 to 245 on device: gpv4
[    0.186749] gpiochip_add: registered GPIOs 246 to 252 on device: gpz
[    0.187918] syscon 10040000.syscon: syscon regmap start 0x10040000 end 0x10044fff registered
[    0.192960] console [pstore-1] enabled
[    0.192967] ramoops: attached 0x100000@0x41f00000, ecc: 0
[    0.193400] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.193407] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.193416] S3C Power Management, Copyright 2004 Simtec Electronics
[    0.197725] EXYNOS5250 PMU Initialize
[    0.197733] EXYNOS: Initializing architecture
[    0.197777] Switching to clocksource arch_sys_counter
[    0.197881] ASV : Unknown SoC type
[    0.200506] bio: create slab  at 0
[    0.201969] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-2364208
[    0.201980] dma-pl330 121a0000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.203340] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-2364208
[    0.203350] dma-pl330 121b0000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.203725] dma-pl330 11c10000.mdma: Loaded driver for PL330 DMAC-2364208
[    0.203734] dma-pl330 11c10000.mdma:         DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    0.203903] of_get_named_gpio_flags exited with status 134
[    0.203966] wifi-rst-l: no parameters
[    0.204059] of_get_named_gpio_flags exited with status 133
[    0.204110] wifi-en: no parameters
[    0.204136] wifi-en: supplied by wifi-rst-l
[    0.204223] of_get_named_gpio_flags: can't parse gpios property
[    0.204271] vbat-supply: no parameters
[    0.204357] of_get_named_gpio_flags exited with status 164
[    0.204410] wwan-en: no parameters
[    0.204506] of_get_named_gpio_flags exited with status 147
[    0.204558] codec-en: no parameters
[    0.205034] SCSI subsystem initialized
[    0.205511] of_get_named_gpio_flags exited with status 19
[    0.205737] usbcore: registered new interface driver usbfs
[    0.205767] usbcore: registered new interface driver hub
[    0.205846] usbcore: registered new device driver usb
[    0.206106] s3c-i2c 12c60000.i2c: slave address 0x00
[    0.206118] s3c-i2c 12c60000.i2c: bus frequency set to 378 KHz
[    0.206425] of_get_named_gpio_flags: can't parse gpios property
[    0.206431] of_get_named_gpio_flags: can't parse gpios property
[    0.206436] of_get_named_gpio_flags: can't parse gpios property
[    0.206440] of_get_named_gpio_flags: can't parse gpios property
[    0.206445] of_get_named_gpio_flags: can't parse gpios property
[    0.206449] of_get_named_gpio_flags: can't parse gpios property
[    0.206453] of_get_named_gpio_flags: can't parse gpios property
[    0.206457] of_get_named_gpio_flags: can't parse gpios property
[    0.206644] max77xxx 0-0009: device found
[    0.207169] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO4'
[    0.207194] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO5'
[    0.207216] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO6'
[    0.207285] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO9'
[    0.207330] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO11'
[    0.207375] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO13'
[    0.207466] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO17'
[    0.207488] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO18'
[    0.207509] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO19'
[    0.207531] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO20'
[    0.207552] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO21'
[    0.207574] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO22'
[    0.207595] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO23'
[    0.207618] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO24'
[    0.207639] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO25'
[    0.207661] max77xxx-pmic max77686-pmic: No matching regulator for 'LDO26'
[    0.207895] max77xxx-pmic max77686-pmic: No matching regulator for 'BUCK9'
[    0.207924] max77xxx 0-0009: no regulator-op-mode property property at EN32KHZ_AP
[    0.207951] max77xxx 0-0009: no regulator-op-mode property property at EN32KHZ_CP
[    0.207979] max77xxx 0-0009: no regulator-op-mode property property at P32KHZ
[    0.208175] P1.0V_LDO_OUT1: 1000 mV
[    0.208507] P1.8V_LDO_OUT2: 1800 mV
[    0.208828] P1.8V_LDO_OUT3: 1800 mV
[    0.209059] LDO4: at 2800 mV
[    0.209271] LDO5: at 1800 mV
[    0.209487] LDO6: at 1100 mV
[    0.209705] P1.1V_LDO_OUT7: 1100 mV
[    0.209926] P1.0V_LDO_OUT8: 1000 mV
[    0.210148] LDO9: at 1800 mV
[    0.210369] P1.8V_LDO_OUT10: 1800 mV
[    0.210586] LDO11: at 1800 mV
[    0.210806] P3.0V_LDO_OUT12: 3000 mV
[    0.211023] LDO13: at 1800 mV
[    0.211250] P1.8V_LDO_OUT14: 1800 mV
[    0.211472] P1.0V_LDO_OUT15: 1000 mV
[    0.211695] P1.8V_LDO_OUT16: 1800 mV
[    0.211918] LDO17: at 1200 mV
[    0.212132] LDO18: at 1800 mV
[    0.212357] LDO19: at 1800 mV
[    0.212575] LDO20: at 1800 mV
[    0.212820] LDO21: at 2800 mV
[    0.213032] LDO22: at 2800 mV
[    0.213247] LDO23: at 3000 mV
[    0.213464] LDO24: at 3000 mV
[    0.213678] LDO25: at 3000 mV
[    0.213886] LDO26: at 3000 mV
[    0.214336] vdd_mif: 950 <--> 1300 mV at 1000 mV
[    0.214690] vdd_arm: 850 <--> 1350 mV at 1300 mV
[    0.215051] vdd_int: 900 <--> 1200 mV at 1012 mV
[    0.215408] vdd_g3d: 850 <--> 1300 mV at 1200 mV
[    0.215756] P1.8V_BUCK_OUT5: 1800 mV
[    0.216114] P1.35V_BUCK_OUT6: 1350 mV
[    0.216465] P2.0V_BUCK_OUT7: 2000 mV
[    0.216828] P2.85V_BUCK_OUT8: 2850 mV
[    0.217040] BUCK9: at 1200 mV
[    0.217262] en32khz_ap: no parameters
[    0.217331] en32khz_cp: no parameters
[    0.217400] p32khz: no parameters
[    0.217493] s3c-i2c 12c60000.i2c: i2c-0: S3C I2C adapter
[    0.217611] s3c-i2c 12c70000.i2c: slave address 0x00
[    0.217621] s3c-i2c 12c70000.i2c: bus frequency set to 378 KHz
[    0.218220] s3c-i2c 12c70000.i2c: i2c-1: S3C I2C adapter
[    0.218302] s3c-i2c 12c80000.i2c: slave address 0x00
[    0.218312] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz
[    0.218676] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter
[    0.218751] s3c-i2c 12c90000.i2c: slave address 0x00
[    0.218761] s3c-i2c 12c90000.i2c: bus frequency set to 65 KHz
[    0.218974] s3c-i2c 12c90000.i2c: i2c-3: S3C I2C adapter
[    0.219047] s3c-i2c 12ca0000.i2c: slave address 0x00
[    0.219057] s3c-i2c 12ca0000.i2c: bus frequency set to 65 KHz
[    0.219120] s3c-i2c 12ca0000.i2c: i2c-4: S3C I2C adapter
[    0.219191] s3c-i2c 12cb0000.i2c: slave address 0x00
[    0.219200] s3c-i2c 12cb0000.i2c: bus frequency set to 65 KHz
[    0.219259] s3c-i2c 12cb0000.i2c: i2c-5: S3C I2C adapter
[    0.219335] s3c-i2c 12cd0000.i2c: slave address 0x00
[    0.219344] s3c-i2c 12cd0000.i2c: bus frequency set to 65 KHz
[    0.219860] s3c-i2c 12cd0000.i2c: i2c-7: S3C I2C adapter
[    0.219925] s3c-i2c 12ce0000.i2c: slave address 0x00
[    0.219935] s3c-i2c 12ce0000.i2c: bus frequency set to 378 KHz
[    0.220153] s3c-i2c 12ce0000.i2c: i2c-8: S3C I2C adapter
[    0.220473] of_get_named_gpio_flags exited with status 177
[    0.220490] of_get_named_gpio_flags exited with status 168
[    0.220501] of_get_named_gpio_flags: can't parse gpios property
[    0.220574] i2c i2c-4: Added multiplexed i2c bus 104
[    0.220960] cros-ec-i2c 104-001e: Chrome EC device registered
[    0.221316] of_get_named_gpio_flags: can't parse gpios property
[    0.221323] of_get_named_gpio_flags: can't parse gpios property
[    0.221328] of_get_named_gpio_flags: can't parse gpios property
[    0.221382] TPS65090_RAILSDCDC1: no parameters
[    0.221414] TPS65090_RAILSDCDC1: supplied by vbat-supply
[    0.222186] TPS65090_RAILSDCDC2: no parameters
[    0.222210] TPS65090_RAILSDCDC2: supplied by vbat-supply
[    0.222969] TPS65090_RAILSDCDC3: no parameters
[    0.222993] TPS65090_RAILSDCDC3: supplied by vbat-supply
[    0.223747] vcd_led: no parameters
[    0.223770] vcd_led: supplied by vbat-supply
[    0.226500] video_mid: no parameters
[    0.226524] video_mid: supplied by vbat-supply
[    0.229267] wwan_r: no parameters
[    0.229293] wwan_r: supplied by vbat-supply
[    0.230044] sdcard: no parameters
[    0.230066] sdcard: supplied by vbat-supply
[    0.232812] camout: no parameters
[    0.232839] camout: supplied by vbat-supply
[    0.233592] lcd_vdd: no parameters
[    0.233615] lcd_vdd: supplied by vbat-supply
[    0.236341] video_mid_1a: no parameters
[    0.236366] video_mid_1a: supplied by vbat-supply
[    0.237132] TPS65090_RAILSLDO1: no parameters
[    0.237155] TPS65090_RAILSLDO1: supplied by vbat-supply
[    0.237238] TPS65090_RAILSLDO2: no parameters
[    0.237258] TPS65090_RAILSLDO2: supplied by vbat-supply
[    0.237589] media: Linux media interface: v0.10
[    0.237616] Linux video capture interface: v2.00
[    0.237981] of_get_named_gpio_flags exited with status 75
[    0.238063] chromeos_arm chromeos_arm: chromeos system detected
[    0.239948] Advanced Linux Sound Architecture Driver Initialized.
[    0.240279] EXYNOS5250: Adaptive Support Voltage init
[    0.240294] EXYNOS5250: ASV lock int: 0 g3d: 0 arm: 0
[    0.240300] EXYNOS5250: ORIG: 5 MOD: 0 RESULT: 5
[    0.240306] EXYNOS5250 MIF: RESULT: 0
[    0.254792] NET: Registered protocol family 2
[    0.255082] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.255173] TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
[    0.255283] TCP: Hash tables configured (established 8192 bind 8192)
[    0.255318] TCP: reno registered
[    0.255330] UDP hash table entries: 512 (order: 2, 24576 bytes)
[    0.255355] UDP-Lite hash table entries: 512 (order: 2, 24576 bytes)
[    0.255512] NET: Registered protocol family 1
[    0.255880] hw perfevents: enabled with ARMv7 Cortex-A15 PMU driver, 7 counters available
[    0.257467] bounce pool size: 64 pages
[    0.260685] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.261011] msgmni has been set to 1428
[    0.261746] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.261755] io scheduler noop registered
[    0.261762] io scheduler deadline registered
[    0.261840] io scheduler cfq registered (default)
[    0.274227] of_get_named_gpio_flags exited with status 156
[    0.274561] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.275299] tpm_i2c_infineon 3-0020: registering reboot notifier [gentle shutdown]
[    0.278445] tpm_i2c_infineon 3-0020: 1.2 TPM (device-id 0xD115)
[    0.353907] [drm] Initialized drm 1.1.0 20060810
[    0.354020] of_get_named_gpio_flags: can't parse gpios property
[    0.354027] of_get_named_gpio_flags: can't parse gpios property
[    0.354032] of_get_named_gpio_flags: can't parse gpios property
[    0.354593] [drm] FIMD: using MIE dithering
[    0.354805] of_get_named_gpio_flags exited with status 163
[    0.356229] exynos-mixer 14450000.mixer: probe start
[    0.357046] of_get_named_gpio_flags exited with status 99
[    0.357063] of_get_named_gpio_flags exited with status 145
[    0.357502] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    0.357510] [drm] No driver support for vblank timestamp query.
[    0.454137] exynos-dp 145b0000.display-port-controller: EDID data does not include any extensions.
[    0.459414] exynos-dp 145b0000.display-port-controller: EDID Read success!
[    0.462655] exynos-dp 145b0000.display-port-controller: Link Training Clock Recovery success
[    0.464526] exynos-dp 145b0000.display-port-controller: Link Training success!
[    0.523937] Console: switching to colour frame buffer device 170x48
[    0.528559] exynos-drm exynos-drm: fb0:  frame buffer device
[    0.528566] exynos-drm exynos-drm: registered panic notifier
[    0.528605] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[    0.528658] usbcore: registered new interface driver udl
[    0.528836] mali 11800000.mali: Continuing without Mali clock control
[    0.528883] v4 support
[    0.529201] mali 11800000.mali: GPU identified as 0x6956 r0p0 status 1
[    0.529413] mali 11800000.mali: Probed as mali0
[    0.531546] loop: module loaded
[    0.531567] lkdtm: No crash points registered, enable through debugfs
[    0.561799] cros-ec-i2c 104-001e: bad packet checksum
[    0.562518] of_get_named_gpio_flags exited with status 155
[    0.562826] dwc3 12000000.dwc3: no usb3 phy configured
[    0.562847] platform 12000000.dwc3: Driver dwc3 requests probe deferral
[    0.563036] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.563136] of_get_named_gpio_flags exited with status 141
[    0.563149] unable to find transceiver of type USB2 PHY
[    0.563158] s5p-ehci 12110000.usb: no platform data or transceiver defined
[    0.563174] platform 12110000.usb: Driver s5p-ehci requests probe deferral
[    0.563239] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.563298] unable to find transceiver of type USB2 PHY
[    0.563307] exynos-ohci 12120000.usb: no platform data or transceiver defined
[    0.563317] platform 12120000.usb: Driver exynos-ohci requests probe deferral
[    0.563450] usbcore: registered new interface driver cdc_acm
[    0.563457] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    0.563462] Initializing USB Mass Storage driver...
[    0.563493] usbcore: registered new interface driver usb-storage
[    0.563499] USB Mass Storage support registered.
[    0.563552] usbcore: registered new interface driver usbserial
[    0.563572] usbcore: registered new interface driver usbserial_generic
[    0.563592] usbserial: USB Serial support registered for generic
[    0.563755] samsung-usb2phy 12130000.usbphy: Not a multi controller PHY
[    0.563782] of_get_named_gpio_flags exited with status 172
[    0.563794] samsung-usb2phy 12130000.usbphy: No HS Tx Pre-Emp current control
[    0.563801] of_get_named_gpio_flags: can't parse gpios property
[    0.563806] samsung-usb2phy 12130000.usbphy: Can't get usb-phy clock gpio
[    0.564065] samsung-usb3phy 12100000.usbphy: Not a multi controller PHY
[    0.564082] samsung-usb3phy 12100000.usbphy: Can't get usb-phy sysreg cfg register
[    0.564088] of_get_named_gpio_flags: can't parse gpios property
[    0.564094] samsung-usb3phy 12100000.usbphy: No HS Tx Pre-Emp current control
[    0.564104] of_get_named_gpio_flags exited with status 91
[    0.564425] input: cros-ec-i2c as /devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0
[    0.565944] max77xxx-rtc max77686-rtc: max77xxx_rtc_probe
[    0.648957] input: Cypress APA Trackpad (cyapa) as /devices/12c70000.i2c/i2c-1/1-0067/input/input1
[    0.729909] max77xxx-rtc max77686-rtc: rtc core: registered max77xxx-rtc as rtc0
[    0.731360] s5p-mfc 11000000.codec: decoder registered as /dev/video10
[    0.731446] s5p-mfc 11000000.codec: encoder registered as /dev/video11
[    0.737541] Exynos: Kernel Thermal management registered
[    0.737984] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled
[    0.738498] device-mapper: ioctl: 4.23.1-ioctl (2012-12-18) initialised<EMAIL_ADDRESS>[    0.738666] device-mapper: verity-chromeos: dm-verity-chromeos registered
[    0.738674] device-mapper: bootcache: version 0.1.0 loaded
[    0.738742] cpuidle: using governor ladder
[    0.738823] cpuidle: using governor menu
[    0.738847] sdhci: Secure Digital Host Controller Interface driver
[    0.738853] sdhci: Copyright(c) Pierre Ossman
[    0.738859] Synopsys Designware Multimedia Card Interface Driver
[    0.739265] dwmmc_exynos 12200000.dwmmc0: no vmmc regulator found: -19
[    0.739286] dwmmc_exynos 12200000.dwmmc0: Using internal DMA controller.
[    0.739298] dwmmc_exynos 12200000.dwmmc0: Version ID is 241a
[    0.739373] dwmmc_exynos 12200000.dwmmc0: DW MMC controller at irq 107, 32 bit host data width, 128 deep fifo
[    0.739398] of_get_named_gpio_flags: can't parse gpios property
[    0.767883] dwmmc_exynos 12200000.dwmmc0: 1 slots initialized
[    0.768163] dwmmc_exynos 12220000.dwmmc2: no vmmc regulator found: -19
[    0.768183] dwmmc_exynos 12220000.dwmmc2: Using internal DMA controller.
[    0.768193] dwmmc_exynos 12220000.dwmmc2: Version ID is 241a
[    0.768315] dwmmc_exynos 12220000.dwmmc2: DW MMC controller at irq 109, 32 bit host data width, 128 deep fifo
[    0.768336] of_get_named_gpio_flags exited with status 52
[    0.797876] dwmmc_exynos 12220000.dwmmc2: 1 slots initialized
[    0.798177] dwmmc_exynos 12230000.dwmmc3: Using internal DMA controller.
[    0.798190] dwmmc_exynos 12230000.dwmmc3: Version ID is 241a
[    0.798329] dwmmc_exynos 12230000.dwmmc3: DW MMC controller at irq 110, 32 bit host data width, 128 deep fifo
[    0.798346] of_get_named_gpio_flags: can't parse gpios property
[    0.826682] mmc0: BKOPS_EN bit is not set
[    0.827869] dwmmc_exynos 12230000.dwmmc3: 1 slots initialized
[    0.828272] usbcore: registered new interface driver usbhid
[    0.828289] usbhid: USB HID core driver
[    0.829495] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0)
[    0.830857] mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 52000000Hz, actual 50000000HZ div = 1)
[    0.831160] mmc0: new high speed DDR MMC card at address 0001
[    0.831398] mmcblk0: mmc0:0001 SEM16G 14.6 GiB
[    0.831513] mmcblk0boot0: mmc0:0001 SEM16G partition 1 2.00 MiB
[    0.831625] mmcblk0boot1: mmc0:0001 SEM16G partition 2 2.00 MiB
[    0.831725] mmcblk0rpmb: mmc0:0001 SEM16G partition 3 128 KiB
[    0.835353]  mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12
[    0.838334]  mmcblk0boot1: unknown partition table
[    0.839811]  mmcblk0boot0: unknown partition table
[    0.868183] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    0.872754] mmc2: new high speed SDIO card at address 0001
[    0.900184] max98095 7-0011: Hardware revision: C
[    0.907440] of_get_named_gpio_flags exited with status 148
[    0.907450] of_get_named_gpio_flags exited with status 150
[    0.907972] daisy-snd-max98095 sound.8:  HiFi <-> 3830000.i2s mapping ok
[    0.908759] daisy-snd-max98095 sound.8:  HiFi <-> 3830000.i2s mapping ok
[    0.909325] input: DAISY-I2S HDMI Jack as /devices/sound.8/sound/card0/input2
[    0.909480] input: DAISY-I2S Headphone Jack as /devices/sound.8/sound/card0/input3
[    0.909625] input: DAISY-I2S Mic Jack as /devices/sound.8/sound/card0/input4
[    0.910795] Netfilter messages via NETLINK v0.30.
[    0.910832] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[    0.911020] ctnetlink v0.93: registering with nfnetlink.
[    0.911225] ip_tables: (C) 2000-2006 Netfilter Core Team
[    0.911294] TCP: cubic registered
[    0.911540] NET: Registered protocol family 10
[    0.911907] NET: Registered protocol family 17
[    0.912060] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    0.912099] ThumbEE CPU extension supported.
[    0.912193] Registering SWP/SWPB emulation handler
[    0.913662] LDO5: disabling
[    1.134234] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    1.134347] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 1
[    1.134481] xhci-hcd xhci-hcd.2.auto: irq 104, io mem 0x12000000
[    1.134535] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.134544] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.134551] usb usb1: Product: xHCI Host Controller
[    1.134558] usb usb1: Manufacturer: Linux 3.8.11 xhci-hcd
[    1.134564] usb usb1: SerialNumber: xhci-hcd.2.auto
[    1.134770] xHCI xhci_add_endpoint called for root hub
[    1.134777] xHCI xhci_check_bandwidth called for root hub
[    1.134846] hub 1-0:1.0: USB hub found
[    1.134861] hub 1-0:1.0: 1 port detected
[    1.134995] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    1.135096] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 2
[    1.135161] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    1.135170] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.135177] usb usb2: Product: xHCI Host Controller
[    1.135184] usb usb2: Manufacturer: Linux 3.8.11 xhci-hcd
[    1.135190] usb usb2: SerialNumber: xhci-hcd.2.auto
[    1.135375] xHCI xhci_add_endpoint called for root hub
[    1.135381] xHCI xhci_check_bandwidth called for root hub
[    1.135452] hub 2-0:1.0: USB hub found
[    1.135466] hub 2-0:1.0: 1 port detected
[    1.135724] of_get_named_gpio_flags exited with status 141
[    1.135731] gpio_request: gpio-141 (ehci_vbus_gpio) status -16
[    1.135737] s5p-ehci 12110000.usb: can't request ehci vbus gpio 141
[    1.142917] s5p-ehci 12110000.usb: S5P EHCI Host Controller
[    1.143021] s5p-ehci 12110000.usb: new USB bus registered, assigned bus number 3
[    1.143078] s5p-ehci 12110000.usb: irq 103, io mem 0x12110000
[    1.152832] s5p-ehci 12110000.usb: USB 2.0 started, EHCI 1.00
[    1.152880] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    1.152888] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.152895] usb usb3: Product: S5P EHCI Host Controller
[    1.152901] usb usb3: Manufacturer: Linux 3.8.11 ehci_hcd
[    1.152907] usb usb3: SerialNumber: 12110000.usb
[    1.153147] hub 3-0:1.0: USB hub found
[    1.153163] hub 3-0:1.0: 3 ports detected
[    1.153420] samsung-usb2phy 12130000.usbphy: USB PHY already initialized
[    1.153430] exynos-ohci 12120000.usb: EXYNOS OHCI Host Controller
[    1.153529] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 4
[    1.153554] exynos-ohci 12120000.usb: irq 103, io mem 0x12120000
[    1.211872] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[    1.211882] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.211889] usb usb4: Product: EXYNOS OHCI Host Controller
[    1.211895] usb usb4: Manufacturer: Linux 3.8.11 ohci_hcd
[    1.211901] usb usb4: SerialNumber: 12120000.usb
[    1.212124] hub 4-0:1.0: USB hub found
[    1.212142] hub 4-0:1.0: 3 ports detected
[    1.212479] of_get_named_gpio_flags exited with status 143
[    1.212492] of_get_named_gpio_flags exited with status 161
[    1.212507] gpio_set_debounce: gpio-143 status -22
[    1.212570] gpio_set_debounce: gpio-161 status -22
[    1.212697] input: gpio-keys.7 as /devices/gpio-keys.7/input/input5
[    1.229864] max77xxx-rtc max77686-rtc: setting system clock to 2015-04-06 20:46:22 UTC<PHONE_NUMBER>)
[    1.229875] VDD_ARM : L0, 1225000 uV
[    1.229880] VDD_ARM : L1, 1187500 uV
[    1.229886] VDD_ARM : L2, 1137500 uV
[    1.229891] VDD_ARM : L3, 1100000 uV
[    1.229896] VDD_ARM : L4, 1075000 uV
[    1.229901] VDD_ARM : L5, 1037500 uV
[    1.229906] VDD_ARM : L6, 1012500 uV
[    1.229911] VDD_ARM : L7, 987500 uV
[    1.229916] VDD_ARM : L8, 962500 uV
[    1.229921] VDD_ARM : L9, 950000 uV
[    1.229926] VDD_ARM : L10, 925000 uV
[    1.229931] VDD_ARM : L11, 912500 uV
[    1.229936] VDD_ARM : L12, 900000 uV
[    1.229941] VDD_ARM : L13, 900000 uV
[    1.229946] VDD_ARM : L14, 900000 uV
[    1.229950] VDD_ARM : L15, 900000 uV
[    1.230051] NOT Capping CPU0 frequency
[    1.237560] VDD_INT Voltage table set with 5 Group
[    1.237670] cpufreq_interactive: monitoring input on cros-ec-i2c
[    1.237688] cpufreq_interactive: monitoring input on Cypress APA Trackpad (cyapa)
[    1.237947] ALSA device list:
[    1.237955]   #0: DAISY-I2S
[    1.237994] Warning: unable to open an initial console.
[    1.238018] device-mapper: init: attempting early device configuration.
[    1.238458] device-mapper: init: adding target '0 2506752 verity payload=PARTUUID=6463ec5b-6277-c14a-acbc-5c9a7154c035/PARTNROFF=1 hashtree=PARTUUID=6463ec5b-6277-c14a-acbc-5c9a7154c035/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=10cdbc993010cc914d17a9645813c5a6931988e6 salt=c8d02530f097c1e313449a5090ed8c56646be9dc4932a9a45badf09ab4722a16'
[    1.238472] device-mapper: verity: Argument 0: 'payload=PARTUUID=6463ec5b-6277-c14a-acbc-5c9a7154c035/PARTNROFF=1'
[    1.238480] device-mapper: verity: Argument 1: 'hashtree=PARTUUID=6463ec5b-6277-c14a-acbc-5c9a7154c035/PARTNROFF=1'
[    1.238486] device-mapper: verity: Argument 2: 'hashstart=2506752'
[    1.238493] device-mapper: verity: Argument 3: 'alg=sha1'
[    1.238499] device-mapper: verity: Argument 4: 'root_hexdigest=10cdbc993010cc914d17a9645813c5a6931988e6'
[    1.238506] device-mapper: verity: Argument 5: 'salt=c8d02530f097c1e313449a5090ed8c56646be9dc4932a9a45badf09ab4722a16'
[    1.242201] bio: create slab  at 1
[    1.242266] device-mapper: init: dm-0 is ready
[    1.247915] EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
[    1.248296] EXT4-fs (dm-0): mounting ext2 file system using the ext4 subsystem
[    1.250564] EXT4-fs (dm-0): mounted filesystem without journal. Opts: (null)
[    1.250594] VFS: Mounted root (ext2 filesystem) readonly on device 254:0.
[    1.259429] devtmpfs: mounted
[    1.259662] Freeing init memory: 316K
[    1.462868] usb 3-2: new high-speed USB device number 2 using s5p-ehci
[    1.593240] usb 3-2: New USB device found, idVendor=0424, idProduct=3503
[    1.593254] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.593687] hub 3-2:1.0: USB hub found
[    1.593862] hub 3-2:1.0: 3 ports detected
[    1.704021] Chromium OS LSM: init_module locked module="/lib/modules/3.8.11/kernel/drivers/net/tun.ko" pid=117 cmdline="modprobe tun"
[    1.704047] Chromium OS LSM: dev(254,0): read-only
[    1.704054] Chromium OS LSM: module locking engaged.
[    1.705369] tun: Universal TUN/TAP device driver, 1.6
[    1.705380] tun: (C) 1999-2004 Max Krasnyansky<EMAIL_ADDRESS>[    1.713018] PPP generic driver version 2.4.2
[    1.733897] systemd-udevd[125]: starting version 208
[    1.762478] udevd[125]: invalid key/value pair in file /lib/udev/rules.d/50-rtc.rules on line 2,starting at character 53 ('r')
[    1.778035] Unsafe core_pattern used with suid_dumpable=2. Pipe handler or fully qualified core dump path required.
[    1.819861] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: commit=600
[    1.825030] EXT4-fs (mmcblk0p8): VFS: Can't find ext4 filesystem
[    1.878001] usb 3-2.2: new high-speed USB device number 3 using s5p-ehci
[    2.049246] usb 3-2.2: New USB device found, idVendor=2232, idProduct=1037
[    2.049261] usb 3-2.2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[    2.049269] usb 3-2.2: Product: WebCam SC-03FFM12339N
[    2.049277] usb 3-2.2: Manufacturer: Generic
[    2.049284] usb 3-2.2: SerialNumber:<PHONE_NUMBER>01
[    2.067759] uvcvideo: Found UVC 1.00 device WebCam SC-03FFM12339N (2232:1037)
[    2.074531] usbcore: registered new interface driver uvcvideo
[    2.074545] USB Video Class driver (1.1.1)
[    2.162042] bio: create slab  at 2
[    2.518218] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: discard,commit=600
[    2.598472] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,data=ordered
[    3.471486] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    3.623942] cfg80211: Calling CRDA to update world regulatory domain
[    3.646912] cfg80211: World regulatory domain updated:
[    3.646926] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    3.646935] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[    3.646944] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[    3.646951] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
[    3.646959] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[    3.646967] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[    3.646978] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
[    4.529757] EXT4-fs (dm-1): resizing filesystem from 4096 to 115467 blocks
[    4.533357] EXT4-fs (dm-1): resized filesystem to 115467
[    4.623815] [drm:drm_mode_legacy_fb_format] ERROR bad bpp, assuming x8r8g8b8 pixel format
[    4.879045] init: disable_echo main process (105) killed by TERM signal
[    6.583390] [drm:drm_mode_legacy_fb_format] ERROR bad bpp, assuming x8r8g8b8 pixel format
[    6.657193] [drm:drm_mode_legacy_fb_format] ERROR bad bpp, assuming x8r8g8b8 pixel format
[   11.877920] Unhandled prefetch abort: breakpoint debug exception (0x002) at 0x00000000
[   11.877945] Unhandled prefetch abort: breakpoint debug exception (0x002) at 0x00000000
[   11.902703] Unhandled prefetch abort: breakpoint debug exception (0x002) at 0x00000000
[   11.902725] Unhandled prefetch abort: breakpoint debug exception (0x002) at 0x00000000
[   15.120555] low_mem: setting minfree to 108544 kB
[   15.182019] fuse init (API version 7.20)
[   15.210156] zsmalloc: module is from the staging directory, the quality is unknown, you have been warned.
[   15.216771] zram: module is from the staging directory, the quality is unknown, you have been warned.
[   15.218763] zram: num_devices not specified. Using default: 1
[   15.218778] zram: Creating 1 devices ...
[   15.326619] s3c-rtc 101e0000.rtc: rtc disabled, re-enabling
[   15.326833] s3c-rtc 101e0000.rtc: rtc core: registered s3c as rtc1
[   15.326856] s3c-rtc 101e0000.rtc: warning: invalid RTC value so initializing it
[   15.361189] Adding 2001084k swap on /dev/zram0.  Priority:-1 extents:1 across:2001084k SS
[   15.407388] Bluetooth: Core ver 2.19
[   15.407487] NET: Registered protocol family 31
[   15.407494] Bluetooth: HCI device and connection manager initialized
[   15.407516] Bluetooth: HCI socket layer initialized
[   15.407529] Bluetooth: L2CAP socket layer initialized
[   15.407561] Bluetooth: SCO socket layer initialized
[   15.503901] Bluetooth: vendor=0x2df, device=0x912a, class=255, fn=2
[   15.710376] isl29018: module is from the staging directory, the quality is unknown, you have been warned.
[   15.762452] sbs-battery 104-000b: sbs-battery: battery gas gauge device registered
[   15.762543] i2c-core: driver [sbs-battery] using legacy suspend method
[   16.563652] mwifiex_sdio mmc2:0001:1: Other intf already running! Skip FW download
[   16.768690] mwifiex_sdio mmc2:0001:1: WLAN FW is active
[   17.040516] mwifiex_sdio mmc2:0001:1: ignoring F/W country code US
[   17.041056] mwifiex_sdio mmc2:0001:1: driver_version = mwifiex 1.0 (14.66.27.p16)
[   17.241723] i2c /dev entries driver
[   17.341718] cros-ec-i2c 104-001e: bad packet checksum
[  150.454237] [drm:drm_mode_legacy_fb_format] ERROR bad bpp, assuming x8r8g8b8 pixel format
[  150.469201] [drm:drm_mode_legacy_fb_format] ERROR bad bpp, assuming x8r8g8b8 pixel format
[  160.251813] Unhandled prefetch abort: breakpoint debug exception (0x002) at 0x00000000
[  160.251835] Unhandled prefetch abort: breakpoint debug exception (0x002) at 0x00000000"

@tempsave - I would suggest -

Backing up your chroot(s) and your Downloads files and folders
Make a restoral image from your Chromebook using the Chromebook Recovery Utility
Restore your Chromebook to 'like new' condition.
Restore your chroot(s) and Downloads files and folders.


document pros/cons of seq/sequence/gen

maybe draw from existing blog posts/readme (including the gagallium post from gasche)

http://gallium.inria.fr/blog/generators-iterators-control-and-continuations/
my talk at some OUPS: http://cedeela.fr/~simon/talks/sequence.pdf
for a short explanation of the differences:

seq is pure, functional, and can be iterated on as many times as needed (if providers of the iterators did their job correctly).  You can write cartesian_product, zip, map2, for_all2`, etc. on it because you (the caller) control iteration.

gen is imperative, mutable, and consumable (you can't iterate twice on the same 'a gen). It looks a lot like iterators in rust/java/… and can be pretty efficient in some cases. Since you control iteration you can also write map2, for_all2, etc but only with linear use of input generators (since you can traverse them only once). That requires some trickery for cartesian_product (like storing already produced elements internally).

sequence is not under the control of the consumer: you give it a callback and it'll call it on every element. Therefore it's not as flexible as gen, and even less so than seq. The upside is that it can be super super fast, especially for things like filter or flat_map. In some cases it can be turned back to nested for loops or just a call to Foo.iter with a complicated callback. Memory consumption should be good too. You cannot write zip, map2, etc since these require step-wise iteration on several iterators, whereas sequence only offers the equivalent of nested loops.

Where would you like such a document to be placed ultimately? And what should it be written in?

Good question, since it concerns all three libraries (gen, sequence, oseq/seq/stdlib). I think it should be a markdown file, I can host it somewhere (or we could make it into a gist?)

How about ocamlverse?

We could have a copy of it on ocamlverse, sure. I'd still like the source to also be in one of the iterators' repositories.


PhotoMatte13K dataset source

Could you please tell some more words about PhotoMatte13K dataset source?
Did you order them in some photo studio or buy at photo stock?

We acquired the data from a partner company that does commercial photo shooting. Unfortunately, we aren't able to disclose more.

We acquired the data from a partner company that does commercial photo shooting. Unfortunately, we aren't able to disclose more.


Define protocol indices in airnode-protocol

Relates to https://github.com/api3dao/airnode/issues/1195

RRP protocol ID = Request-response protocol protocol ID but RRP ID doesn't work so meh.

Yeah, I was thinking the same.

Maybe call it PROTOCOL_ID_RRP for better autocomplete (especially since Airkeeper/Airseeker won't be obvious) but it's up to you.

Alternatively, we can do enum style:
const PROTOCOL_IDS = {
    RRP: '1'
    ...
}

wdyt?


fix nodemanager tests

:nut_and_bolt: Description: What code changed, and why?
noticed some tests in CI weren't failing where they should...

i added a failure commit so we expect to see that same nodemanager-service test suite fail 🤞

The bash function that runs these tests runs two go_tests in a row, could the first one fail and the second pass making the whole thing a success?
https://github.com/chef/automate/blob/master/.studio/nodemanager-service#L8-L11
I wonder if we need to && those together or just run all the tests in one command...

We probably don't want failfast everywhere since that is more useful in a local fast iteration scenario.

I opened a PR to try to fix this in #2435 but it's failing some tests.


Switch to GitHub Actions for CI

Travis CI suddenly stopped running builds for Leaflet and many of my other open source repos for unknown reasons. Rather than try to figure out what's wrong, we should just switch to GitHub Actions — it's part of GitHub, it's more flexible and runs faster.
Example config on one of my projects: https://github.com/mourner/flatbush/blob/master/.github/workflows/node.yml

I worked a little bit with GH-Actions if you are interessted I could set something up...

@jonkoops thanks again for landing this!
Before I can close this, to finish fully migrating to GH Actions, we also need to port over the artifacts bit in the Travis config which was responsible for uploading a distribution of Leaflet (for download) for every commit on the master branch.

@mourner Sure, I can take a look at that as well. Where exactly were those files being uploaded before?
FYI I also opened #7660 which allows the tests to run on all the different browsers properly.

The S3 upload is working now, all good!


Add GetSpanPath and SpanExists

TL;DR
This is part of Flytekit Metrics Exploration.
This PR helps propeller to get span uri(highlighted in green).

Flytekit Metrics Exploration includes:

flytekit: https://github.com/flyteorg/flytekit/pull/1683

flyteplugins: https://github.com/flyteorg/flyteplugins/pull/361

flyteidl: https://github.com/flyteorg/flyteidl/pull/415

flytepropeller: https://github.com/flyteorg/flytepropeller/pull/577

flyteadmin: https://github.com/flyteorg/flyteadmin/pull/575

Hi, we are moving all Flyte development to a monorepo. In order to help the transition period, we're moving open PRs to monorepo automatically and your PR was moved to https://github.com/flyteorg/flyte/pull/4128. Notice that if there are any conflicts in the resulting PR they most likely happen due to the change in the import path of the flyte components.


remove/disable leader election info log

As operator of Kubermatic, I get every 2 seconds the following log line in the machine-controller:
cluster-9k6tgrg7hj | I1203 17:15:33.863797       1 leaderelection.go:199] successfully renewed lease kube-system/machine-controller

This info don't give any benefit for anyone. Only a error message when something breaks helps. So I would suggest to remove this log message or move it to a debug level.
The issue is may a follow up from https://github.com/kubermatic/kubermatic/pull/2471:

This implies that all the logging we do has to be on a lower level than four

Related: kubermatic/kubermatic#2471


TD-3234 Update RoadPreview Component

Closes TD-3234
Contributes TD-3196
Changes

A brief description of what this pull request solves / introduces.

Move the RoadPreview component to its own
Implement the FormatLabel, FormatVersionLabel, FileLabel, DateLabel, UserLabel components.
Bound the above mentioned components in boxes, so that they truncate and size to their content properly
Adjusted types to fit the new definitions
Adjusted the stories to pass the props in the correct way due to the type change
Adjusted tests to test with the new data-testids

Maybe a short description of what is not included and will come in future work where appropriate.
Dependencies

UI/UX

Testing notes

Open storybook
Check the RoadPreview component
Make sure the RoadPreview component belongs to the Preview group in storybook
Make sure the component matches FIGMA
Make sure that you can adjust the createdAt, file, format, formatVersion, user values. Make sure that when these values are long truncation happens and nothing exceeds the parent component (the card).

Author checklist
Before I request a review:

[x] I have reviewed my own code-diff.
[x] I have tested the changes in Docker / a deploy-preview.
[x] I have assigned the PR to myself or an appropriate delegate.
[x] I have added the relevant labels to the PR.
[x] I have included appropriate tests.
[x] I have checked that the Lint and Test workflows pass on Github.
~- [ ] I have populated the deploy-preview with relevant test data.~
[x] I have tagged a UI/UX designer for review if this PR includes UI/UX changes.

@Sowbhagya-ipg Can you please confirm that this component matches your expectation. Thanks!

Checked it looks fine for me. @AronPetrauskas

@Sowbhagya-ipg The gap has been decreased and the tool tips removed. Can you please confirm everything is working well?

One thing has changed, the anchor tag was longer(wider) than the text of the road name, this was fixed.


Try fixing display delay after billing info completed

PR-Codex overview
This PR refactors API hooks to accept a refetchInterval parameter, optimizes query invalidation, and removes unnecessary code in billing components.
Detailed summary

useAccount now accepts a refetchInterval parameter
Improved query invalidation in billing components
Removed unnecessary code in billing components

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

📝 Changed routes:

…board/settings/billing

(view full size)

Commit 120440db553223a09303cc9a2cc837874864ade5 (https://thirdweb-d7395cc85.thirdweb-preview.com).


i

Gonna probably report user, would close this as well, already has opened 4 other spam ones as referenced in comments by myself and @IEvangelist in #23113


Visual Studio Code does not recognize ElevatedButton

Minimal Example
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(
          title: Text('Hello World'),
        ),
        body: Center(
          child: RaisedButton(// change it to ElevatedButton to reproduce the issue!
            child: Text('Click Me'),
            onPressed: () {},
          ),
        ),
      ),
    );
  }
}

Steps to Reproduce

Create a project, copy the given minimal example above.  It should run without any issue.
Change RaisedButton to ElevatedButton and I get the following errors.

Logs

My Settings

Have you tested this on dartpad yet? You can check it here.
https://dartpad.dev/ba816904e0aefbde80e6840aae24fd2c

What is your Flutter version?
flutter --version

on the Terminal
It is possible that your flutter version is not up to date.

See my updated question.

Updating the flutter sdk solved the problem.


variants: arduino_nano_33_iot: Fix 'i2c0' fail to resolve

Use arduino_nano_i2c instead of i2c0.
Signed-off-by: TOKITA Hiroshi<EMAIL_ADDRESS>

@soburi does this PR solve https://github.com/zephyrproject-rtos/gsoc-2022-arduino-core/issues/50 ?
If so then kindly mention "close https://github.com/zephyrproject-rtos/gsoc-2022-arduino-core/issues/50" in the commit or PR description

@soburi does this PR solve #50 ? If so then kindly mention "close #50" in the commit or PR description

Oh! I missed #50 issue.
Add mention to #50.
Thank you notify to me.


adds unit tests to pkg/slices

Please provide a description of this PR:

adds tests to pkg/slices as part of #37354
modifies slices.Flatten to explicitly handle a nil slice as an argument
modifies slices.MapFilter to add quick return in the case of a nil filter function, preventing a panic

Hi @colinjlacy. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@colinjlacy: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8215d3a9069001ce56d2a96b53bd0322ba161f53
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@colinjlacy: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8215d3a9069001ce56d2a96b53bd0322ba161f53
link
true
/test lint

gencheck_istio
8215d3a9069001ce56d2a96b53bd0322ba161f53
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@colinjlacy: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8215d3a9069001ce56d2a96b53bd0322ba161f53
link
true
/test lint

gencheck_istio
8215d3a9069001ce56d2a96b53bd0322ba161f53
link
true
/test gencheck

integ-ambient_istio
8215d3a9069001ce56d2a96b53bd0322ba161f53
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test lint

/test integ-ambient

/test gencheck

/ok-to-test


add a real Terminal aka Remote Connection / Shell --> a putty alternative

the app looks promissing, if connections like terminal, ssh etc. will be added it will become more usefull.
like a putty alternative. with saved account-data (verify by account-verification like fingerprint, pin, passw)

Thanks for the request. Terminal is going to be a very good local terminal. We are not planning on adding specific ssh and telnet client support because ssh and telnet are already part of Windows. You can use them inside terminal.
If we add support for password and identity storage and management, we will become a security product and it will be harder and more complicated to develop. 😄


Adding Machine learning example.

Hello, how are you doing?
I've done a machine learning basic example using KNN.
Hope it is useful.
Thanks in advance. Cheers!

The example introduced by this PR has been merged and is available as the k-NN DApp.


[Admin] Lower pull request approval requirement to 1

Hi @node-fetch/core,

Per @jimmywarting's request, I will consider lowering our merge approval count from 2 to 1 in the coming week.

Given the number of pending changes and our team member schedule, I believe this will speed up 3.0 development considerably.

There are definitely some risk involved; as an alternative, I am open to recruiting more active reviewers.

If you have any other suggestions or concerns, please feel free to voice it here.

If you support the move to lower approval requirement, please leave your vote here so we know :)

Thx and have a nice day.

There are definitely some risk involved; as an alternative, I am open to recruiting more active reviewers.

on the other end of it, we also get security bugs and hotfixes out faster.
it would still be okey to keep it at 2, but that would require that we recruit more active reviewers. Some ppl have lost touch and interest in maintaining this. it is especially slow to get approvals when a team member like myself makes a pr and needs 2 approvals from somebody other then myself. it feels like there is 3 ppl that sometimes approves PRs and when you are one of them who can't approve your own PR then it's VERY long and tedious process of getting something approved cuz you are waiting for that one last person who isn't involved so much
Merging some random persons PR is sometimes quicker.

as i discussed with @bitinn over email also... I think a automated deployment would be nice to have also. @gr2m already made a PR about it: https://github.com/node-fetch/node-fetch/pull/1270
cuz the way it's right now is: you make a PR, wait for two approvals and when it's done, someone needs to make a new PR with a major, minor or patch version and needs to wait for that to be approved by two ppl as well. it takes very long to get something out in production

Ping @node-fetch/reviewers for comments too, if you got any suggestions to help maintain node-fetch better, let us know here :)

I agree with what @jimmywarting stated in his comment about the PR process. The restrictions are good, but if there could be more people that can code review and approve, it will make the process more fluid & fast even if we do 1 PR/Merge approval.
Automating the deploy of a new version should be a great addition save time. As long as the PR was approved a merged, publishing a new version is a step that is both complicated & easy, complicated because if you automate you have to decide how to upgrade the version from a patch to a major or a minor & also if it is manual we need someone to do it and that someone may not be free.

Ideally, the amount of reviewers should not be constrained by a number we set and forget, but instead by common sense and pure logic. Following the same threshold for all pull requests doesn't make sense since some can have a bigger impact than others.
However, having 1 as a minimum requires at least 1 other person to take a took which is fine in most circumstances though we should still internalise the fact that we should be waiting for approvals as needed rather than to just satisfy the quota.

I'm okay with this, but personally I don't feel too confident merging most of the PRs that are open now with only one reviewer. Some minor ones could benefit from it though ☺

I agree with LinusU.

OK, I understand the hesitation here, then maybe we can establish an active PR review assignment table, here is how I think it might work:

We open a pinned issue with all candidate PRs as a single task list.

Members who have time and feel confident to review an PR, can take it formally.

We will mark a PR as active when 2 members have taken it.

And it will be accepted when these 2 members have reviewed and author has cleared all concerns.

This way we have a clear picture of (1) which PR needs reviewing and (2) who are reviewing a PR.
It's a bit old-fashioned but I like to have a central place for (1) project transparency, (2) not GitHub project or tag filter so any new members can understand.
It may look something like:

[x] #1314 (taken by @LinusU and @Richienb)
[ ] #1270 (taken by @jimmywarting, missing one reviewer)
[ ] #1326 (missing 2 reviewers)

How do you think about this?
(Personally, I no longer code in nodejs, but I am happy to help maintain such a dashboard)

I don't know, i would rather prefer GitHub project or tags

I'd rather use a project, too. I think it's something that should be automated, not add additional maintenance overhead.
I added my 👍🏼 to reduce the approval requirement to 1. From my experiences, open source projects that lowered the barrier of contribution and maintenance are the ones that thrive in the long term. Even with only a single review required, every maintainer can still block a PR, either by rejecting a PR in its current state or requiring a review of themselves if they want to review the PR but need more time. And we can add required reviews manually to any PRs where we think certain maintainers should at least acknowledge it.
And lastly, when things slip through, it's easy enough to revert a change.

regarding:

ci: semantic-release #1270 (taken by @jimmywarting, missing one reviewer)

...That missing reviewer needs to be you @bitinn, only you can add NPM_TOKEN, and do the other recommendations

...That missing reviewer needs to be you @bitinn, only you can add NPM_TOKEN, and do the other recommendations

Please let me know when you have that token, and I will do the steps: I don't even have npm installed on my work machine at this point, that's how far removed I am from nodejs.
I am not the only admin for this right? I was given admin right after node-fetch org migration.

I don't think i have github-admin privileges (?)
I can't see the settings-tab

both @Richienb @xxczaki should have organization admin permission.

I don't think i have github-admin privileges (?) I can't see the settings-tab

I think i can generate a NPM token, cuz i can publish to npm (Don't think you need to install npm to generate a token, you can do it all from the web in npm & github)
I have wanted to enable discussion in this repo, but i can't

both @Richienb @xxczaki should have organization admin permissions. the exact work to be done can be discussed in the issue thread.

Hi @jimmywarting,
If you are looking for admin access to this repo to setup some automation stuffs, please ping @Richienb and @xxczaki directly to setup a role for it. I wasn't involved in the node-fetch org's role settings, it would be better if they are involved.
Given current input I have changed required reviewer count to 1, to get the balls rolling on PRs.
Thx.


Publish rmarkdown remotely #2051

Added helper to publish r markdown remotely and open the output locally using blobs.

I think we can add a file transfer service/helper when we have a better picture of how the sync works. For now I added extension methods on IRSession to do this.

👍

:+1:


Resubmit failed jobs

As described in #20 60 jobs failed, which need to be resubmitted.

14 of the jobs failed due to memory issues, they have now been resplit and submitted at the time of writing.

These 14 jobs have now been run successfully.


go-start to 0.0.1

Promote go-start to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@truncj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

promotion-build
f7b9742550324c701d358d62483b5da526fef9d7
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[admin] (Links) Fixing broken link anchors

Docs Build status updates of commit ad6b21a:
:clock10: Pending: waiting for processors (87 builds ahead of you)
:warning: Docs Build is busy, currently there are 87 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit ad6b21a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/asynchronous-programming-in-office-add-ins.md
:white_check_mark:Succeeded

docs/develop/loading-the-dom-and-runtime-environment.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/excel-api-1-2-requirement-set.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes.

Bicep or Terraform?
Bicep
Module Classification?
Resource Module
Module Name
avm/res/azure-stack-hci/network-interface
Module Details
Azure Stack HCI Network Interfaces
Deriving from https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.azurestackhci/vm-windows-disks-and-adjoin/main.bicep
Do you want to be the owner of this module?
Yes
Module Owner's GitHub Username (handle)
mbrat2005
(Optional) Secondary Module Owner's GitHub Username (handle)
steveswalwell

Hi @mbrat2005,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:

Team Definitions & RACI
Shared Specification (Bicep & Terraform)
Module Support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR

I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER

Hi @mbrat2005,
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
Before starting development, please ensure ALL the following requirements are met.
Please use the following values explicitly as provided in the module index page:

For your module:

ModuleName - for naming your module
TelemetryIdPrefix - for your module's telemetry

For your module's repository:

Repo name and folder path are defined in RepoURL
Create GitHub teams for module owners and contributors and grant them permissions as outlined here.
Grant permissions for the AVM core team and PG teams on your GitHub repo as described here.

Check if this module exists in the other IaC language. If so, collaborate with the other owner for consistency. 👍
You can now start the development of this module! ✅ Happy coding! 🎉
Please respond to this comment and request a review from the AVM core team once your module is ready to be published! Please include a link pointing to your PR, once available. 🙏
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team

Working on a bicep template to deploy the prereqs for an Azure Stack HCI cluster running in Azure to enable a testing pipeline. Once completed, I will prioritize the #929 module before moving to Arc VM related modules

Depends on #929, which is in progress

Completed initial work, but blocked by same secrets issue as cluster resource https://github.com/mbrat2005/bicep-registry-modules/tree/mtb-azure-stack-hci-network-interface

Blocked by: https://github.com/Azure/Azure-Verified-Modules/issues/1194

Unblocked now that customer CI secret solution is merged


rename the namespace to quadiron

quad is a bit too "common" to be used as a good namespace.
Using quadiron seems better to avoid eventual name clashes, and if
it's too long users can still shorten it by themselves.

@lamphamsy in the end, I think you were right: quadiron is better as namespace.


Upgrade to latest Motoko compiler + Motoko base

Hi @kritzcreek ,
This lib is widely used for testing on the IC, but to my surprise it hasn't been updated for 2 years.
I have forked this project and will be updating on it to the latest compiler + motoko base.
I can easily create a PR that updates this repo too, would you be interested / accept it?
Thank you,
Tiago

Fixed in #13
I've also added some commits to master to update versions in CI and apply VSCode's formatting to all files.
After merging https://github.com/kritzcreek/motoko-matchers/pull/15 I'll make a new release.

Released as v1.3.0


Replace toBe with to.equal for typeof tests

Having this undefined is not a function (evaluating 'expect(_MyComponent.default.data).toBe('function')')
when using toBe. No more error when using to.equal

Note this comment:

// Here are some Jasmine 2.0 tests, though you can
// use any test runner / assertion library combo you prefer

Since you're not using Jasmine, but another assertion library with a different syntax, you have to adjust the examples to use the assertion syntax supported by that library.


Documentation related to the constant is inconsistent with the codebase

Hello
Current aerospike.md claims that there is a OP_LIST_MERGE constant;
Nevertheless:
$ php -a
Interactive mode enabled

php > var_dump(Aerospike::OP_LIST_MERGE);
PHP Fatal error:  Undefined class constant 'OP_LIST_MERGE' in php shell code on line 1
PHP Stack trace:
PHP   1. {main}() php shell code:0

Fatal error: Undefined class constant 'OP_LIST_MERGE' in php shell code on line 1

Call Stack:
   23.9651     219240   1. {main}() php shell code:0

The next question I'm interested in:
The values of these constants have changed in a minor version

Constant
v3.4.6
v3.4.7

OPT_POLICY_KEY
11
12

OPT_POLICY_GEN
12
13

OPT_POLICY_REPLICA
13
14

OPT_POLICY_CONSISTENCY
14
15

OPT_POLICY_COMMIT_LEVEL
15
16

OPT_TTL
16
17

USE_BATCH_DIRECT
17
18

it seems to me that for changes which BC breaks should use the next major version, for example v3.5.0. Could you please explain a bit more your release process?
And finally:
The 3.4.7 version introduces COMPRESSION_THRESHOLD and OP_GEOWITHINREGION constants. Also, if I'm not mistaken the 3.4.6 version introduces JOB_QUERY and JOB_SCAN constants.
Can you please document them?

@rbotzer, @jboone100 ping :)

The 3.4.8 version which is incorrectly called 3.4.7 introduces:

ERR_GEO_INVALID_GEOJSON
INDEX_GEO2DSPHERE
OP_GEOCONTAINSPOINT

constants. Can you please document them?

@rbotzer ping

Thanks for pointing these out. OP_LIST_MERGE has been removed from the documentation since it is invalid. All others have been added to the documentation for the 3.4.9 release.


Log the Engine SSO endpoint used

After a successfull login, log the sso endpoint used during authentication. This is available on the _request var present on the
LogLogin command.
https://www.pivotaltracker.com/story/show/175904919

Sir, quartermaster @quartje, does this meet your requirements, sir?

What's being logged is:
Mar 29 15:41:12 apps.vm.openconext.org EBAUTH[1307]: {"channel":"authentication","level":"INFO","message":"login granted","context":{"login_stamp":"2021-03-29T15:41:12.442692+02:00","user_id":"urn:collab:person:example.com:asdfasdf","sp_entity_id":"https://profile.vm.openconext.org/authentication/metadata","idp_entity_id":"http://mock-idp","key_id":null,"proxied_sp_entity_ids":[],"workflow_state":"prodaccepted","original_name_id":"urn:collab:person:example.com:asdfasdf","authncontextclassref":"urn:oasis:names:tc:SAML:2.0:ac:classes:Password","engine_sso_endpoint_used":"https://engine.vm.openconext.org/authentication/idp/single-sign-on"},"extra":{"session_id":"7ruj1vn6cg8hrdeij5bl6teves","request_id":"6061d8f7de05a"}}

When using the md5 hash of the IdP in the path like this:
https://engine.vm.openconext.org/authentication/idp/single-sign-on/key:xxxx/md5hashoftheidp
would that be explicitly logged by this change?

Do you hint at the unsolicited SSO option? If that's the case, no the original destination of the SSO AuthNRequest is lost. But the request is flagged as being unsolicited. So I would be able to reconstruct the idp hash and the url-encoded sp EntityId.

No, I think Bart refers to the different ways you can start a regular Authentication Request on EB.
An SP can call e.g.:
https://engine.vm.openconext.org/authentication/idp/single-sign-on
https://engine.vm.openconext.org/authentication/idp/single-sign-on/key:20210330
https://engine.vm.openconext.org/authentication/idp/single-sign-on/234353ee1e96b99f9bb5f488a235982b
https://engine.vm.openconext.org/authentication/idp/single-sign-on/key:20210330/234353ee1e96b99f9bb5f488a235982b
If one SP uses the first and another SP uses the last, will this be visible in different logged strings?

Ah, yes forgot this is is possible too, I will check if that gets logged correctly. I do think this is already the case. The unsolicited sso was the strange :duck: when it comes to storing the incoming authn request from the 'SP'.

Confirmed, the IdP hash in the sso uri is also logged. As proved by this: (same would apply when specifying a key)
Mar 30 11:59:01 apps.vm.openconext.org EBAUTH[1307]: {"channel":"authentication","level":"INFO","message":"login granted","context":{"login_stamp":"2021-03-30T11:59:01.681569+02:00","user_id":"urn:collab:person:example.com:rftgyj","sp_entity_id":"https://profile.vm.openconext.org/authentication/metadata","idp_entity_id":"http://mock-idp","key_id":null,"proxied_sp_entity_ids":[],"workflow_state":"prodaccepted","original_name_id":"urn:collab:person:example.com:rftgyj","authncontextclassref":"urn:oasis:names:tc:SAML:2.0:ac:classes:Password","engine_sso_endpoint_used":"https://engine.vm.openconext.org/authentication/idp/single-sign-on/234353ee1e96b99f9fa5f488a235982b"},"extra":{"session_id":"9d9bghurbqfpe5kj3gce3sgkfh","request_id":"6062f64daec8b"}}


test: add a compitable version function

Is there any component you are going to support with this style of the version?

I'm trying to use sky-go in api-testing. During the process, I found out it will add the prefix v no matter if the version has or not.

I got an error when execute the make test command locally. Considering this is not related to my PR. Just ignored it.

I got an error when execute the make test command locally. Considering this is not related to my PR. Just ignored it.

@mrproliu PTAL. Is it worth checking whether anything is missing when tracing gRPC?

I got an error when execute the make test command locally. Considering this is not related to my PR. Just ignored it.

I think you need to more debug into it, it already running many times on the CI and works well. Please focus on the server_test.go:87, It should not throw an error, you need to check out what's happened.

Is it worth checking whether anything is missing when tracing gRPC?

For the UT, It is not related to the gRPC plugin.

It is usually decided by the version environment when we release the skywalking-go.

Totally understand it. I'm wondering if it's possible and reasonable to allow user passing the version.

There are plugin tests failing, is this change breaking something?

There are plugin tests failing, is this change breaking something?

Shouldn't be. This is a compitable change. Or it does not allow this change.

I'm wondering if it's possible and reasonable to allow user passing the version.

Users don't need to know about the "version" parameter. They just need to download the specified version when using it.


Extension Development - Modifying Code Coverage

I am in a team developing an additional SNAC extension to OpenRefine and am currently tinkering with the code coverage through coveralls as it was previously set up on the base OpenRefine project. I am running into trouble excluding certain files from being counted and I was wondering if you would have any insight on that as I've been trying for a while now with little success. I'm messing with the pom.xml, jacoco, and <excludes> tag of the base project as well as the one for the extension but no luck. Here is a link to the project if it helps

Actually for some reason our code coverage isn't currently being submitted to Coveralls - I should investigate why!
Also, the link to the project is invalid.

Oh apologies, let's try that again.

Got it! I needed to move the <excludes> tag out a level.