text:
SQLThread: Fixed infinite loop

Steps to reproduce the issue

Enable xdebug or recursionguard and start the server
Execute the stop command to stop the server
A recursive calling loop has been detected

backtrace
stop
[09:19:57.187] [Server thread/INFO]: [CONSOLE: Stopping the server]
[09:19:57.188] [Server thread/INFO]: Disabling DevTools v1.15.0
[09:19:57.189] [Server thread/INFO]: Disabling DEVirion v1.2.8
[09:19:57.189] [Server thread/INFO]: Disabling TNTTag v0.0.4
[09:19:57.191] [Server thread/INFO]: Unloading world "world"
[09:19:57.918] [Server thread/INFO]: Stopping other threads

Fatal error: Uncaught Error: Reached maximum call depth of 256, aborting! in P:\game\test1\new\virions\libSQL_fork\src\cooldogedev\libSQL\thread\SQLThread.php:87
Stack trace:
#0 [internal function]: cooldogedev\libSQL\thread\SQLThread->cooldogedev\libSQL\thread\{closure}()
#1 P:\game\test1\new\virions\libSQL_fork\src\cooldogedev\libSQL\thread\SQLThread.php(90): Threaded->synchronized(Object(Closure))
#2 P:\game\test1\new\virions\libSQL_fork\src\cooldogedev\libSQL\thread\SQLThread.php(88): cooldogedev\libSQL\thread\SQLThread->quit()
...
#378 [internal function]: cooldogedev\libSQL\thread\SQLThread->cooldogedev\libSQL\thread\{closure}()
#379 P:\game\test1\new\virions\libSQL_fork\src\cooldogedev\libSQL\thread\SQLThread.php(90): Threaded->synchronized(Object(Closure))
#380 phar://P:/game/test1/new/PocketMine-MP.phar/src/thread/ThreadManager.php(84): cooldogedev\libSQL\thread\SQLThread->quit()
#381 phar://P:/game/test1/new/PocketMine-MP.phar/src/PocketMine.php(313): pocketmine\thread\ThreadManager->stopAll()
#382 phar://P:/game/test1/new/PocketMine-MP.phar/src/PocketMine.php(328): pocketmine\server()
#383 P:\game\test1\new\PocketMine-MP.phar(11): require('phar://P:/game/...')
#384 {main}
  thrown in P:\game\test1\new\virions\libSQL_fork\src\cooldogedev\libSQL\thread\SQLThread.php on line 87

Took too long to stop, server was killed forcefully!

Thanks for the contribution!

source: gharchive/pull-request

authors: DaisukeDaisuke cooldogedev

repo: cooldogedev/libSQL

license: MIT

license_type: permissive

license_source: github-api


text:
[Bug]: MR Previews not showing in the Previews Section

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I commit changes to an active merge request, a build is executed for the merge request, but nothing appears under the previews pane. See below screenshots.

Steps To Reproduce

Create an application with GitLab as a source (self-hosted instance in my case)
Choose the appropriate options for the application (NodeJS in my case)
Deploy the application, and verify that visiting it works (it does for me)
Create another branch, start a merge request and push a commit to the merge request

Coolify will build the merge request, but it won't place it in the previews pane.
Version
3.10.0

I think I know what’s going on. The PR builds failed to start and that is why is not shown.
I will fix / improve it.

source: gharchive/issue

authors: FrinkMan andrasbacsai

repo: coollabsio/coolify


text:
ActionsSecret from a Secret

Feature request:
Add the option to use (reference) a Kubernetes Secret as a value in ActionSecret.

Hi @vfarcic
I think this feature is already there https://github.com/coopnorge/provider-github/blob/main/package/crds/actions.github.upbound.io_actionssecrets.yaml#L76-L113.
Does this cover your feature request?

My bad. I somehow missed it. Sorry for that.

authors: AtzeDeVries vfarcic

repo: coopnorge/provider-github


text:
Alternative install with Conda

This PR adds an alternative install with Conda to the README.

Codecov Report

Merging #739 (ae7e2b7) into master (fa3515e) will decrease coverage by 16.59%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #739       +/-   ##
===========================================
- Coverage   96.62%   80.02%   -16.60%
===========================================
  Files          41       41
  Lines        2930     2929        -1
===========================================
- Hits         2831     2344      -487
- Misses         99      585      +486

Flag
Coverage Δ

unittests
80.02% <ø> (-16.60%)
:arrow_down:

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

Impacted Files
Coverage Δ

tests/test_prompt.py
13.09% <0.00%> (-76.20%)
:arrow_down:

tests/test_complex_questions.py
30.72% <0.00%> (-69.28%)
:arrow_down:

tests/test_updatediff.py
57.02% <0.00%> (-42.98%)
:arrow_down:

tests/test_tools.py
52.00% <0.00%> (-40.00%)
:arrow_down:

tests/test_templated_prompt.py
72.13% <0.00%> (-27.87%)
:arrow_down:

copier/user_data.py
70.13% <0.00%> (-23.11%)
:arrow_down:

tests/conftest.py
72.72% <0.00%> (-22.73%)
:arrow_down:

copier/cli.py
81.17% <0.00%> (-16.48%)
:arrow_down:

tests/helpers.py
91.22% <0.00%> (-8.78%)
:arrow_down:

tests/test_migrations.py
91.47% <0.00%> (-8.53%)
:arrow_down:

... and 7 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

repo: copier-org/copier


text:
The timeline editor should allow to scroll a bit past the last event so that it is easier to drop new events at the bottom of the timeline

I added a spacer node (just a control node with rect_min_size(Vector2(0,100)) but I ran into a funny issue with doing that:

I should probably recalculate the size of the children node and just add X pixels of size instead of the fixed control node, but I'll keep trying for a while this way.

managed to get it almost right. I hope to merge today

repo: coppolaemilio/dialogic


text:
fix http.Flusher and io.ReaderFrom implementation

Thank you for contributing to Coraza WAF, your effort is greatly appreciated
Before submitting check if what you want to add to coraza list meets quality standards before sending pull request. Thanks!

Make sure that you've checked the boxes below before you submit PR:

[x] My code includes positive and negative tests.
[x] I have an appropriate description with correct grammar.
[x] I have read Contribution guidelines, maintainers note and Quality standard.
[x] My code is properly linted and passes pre-commit tests.

Before this change http.Flusher and io.ReaderFrom essentially acted like a bypass for the coraza middleware because they directly called the underlying writer.
http.Flusher is unimplementable because it doesn't make sense to flush early to the client. It does have one observable effect. A call to Flush before a call to Write (or WriteHeader) also implies a call to WriteHeader.
io.ReaderFrom can be implemented by linking it with Write through io.Copy

It looks good to me, just fix the coverage. Any thoughts @anuraaga ?

I am done with edits now.
I think this is ready for a second look.
Thank you @jcchavezs for the review 🙇

This should trigger a release I think.
On Tue, 21 Nov 2023, 06:28 Anuraag Agrawal, @.***>
wrote:

Merged #923 https://github.com/corazawaf/coraza/pull/923 into main.
—
Reply to this email directly, view it on GitHub
https://github.com/corazawaf/coraza/pull/923#event-11019568468, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAW2CFRQ43AOMGJEO6DYFQ3WBAVCNFSM6AAAAAA7TERI2CVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGAYTSNJWHA2DMOA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you for the reviews everyone 🙇

@mholt do you think this is something we should port to the caddy connector?

That might be a good idea if it fixes a bug.

authors: jcchavezs mholt romainmenke

repo: corazawaf/coraza


text:
🛑 Guangdianyun is down

In 0414ee7, Guangdianyun (https://www.guangdianyun.tv) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guangdianyun is back up in 3d1403a.

repo: corcd/charlotte


text:
🛑 Guangdianyun is down

In 1b81ae3, Guangdianyun (https://www.guangdianyun.tv) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guangdianyun is back up in 38e3d35.


text:
🛑 Guangdianyun Consoles is down

In 026c96b, Guangdianyun Consoles (https://consoles.guangdianyun.tv) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guangdianyun Consoles is back up in 4c6d4e7.


text:
move to http://svgjs.com/ or better

instead of making raw svg tags as inner html

@jacksenechal this looks awesome

repo: core-network/client

license: mit

license_source: bigquery


text:
Add missing parse case to featurefmt

Many of the parsers have code like the following pseudo-code:
packages_file = """
package_name: one
package_version: 1.0

package_name: two
package_version
"""

for line in packages_file:
  if line == package_name:
    pkg.name = parse_package_name_from_line(line)
  elif line == package_version:
    pkg.version = parse_package_version_from_line(line)

  if pkg.name != "" and pkg.version != "":
    packages_map[uniquename(pkg)] = pkg
    pkg = new_blank_pkg_object()
  # The following is the missing case we need to add:
  if line == blank_line:
    pkg = new_blank_pkg_object()

We need to add missing case that determines if the parser has hit the new line delimiter between two separate packages and then resets our current package object.
I haven't had this bug cause any problems parsing so far, but a malformed file could definitely cause issues.

I agree. Assumption was made that the package managers would not produce an invalid file, so little validation has been written. Changing this would be straight-forward and provide some peace of mind.
The kind/enhancement label is kinda pointless tho. Or I start writting PRs that just make the project worse, then I can label them kind/regression.

authors: Quentin-M jzelinskie

repo: coreos/clair


text:
Slow private network

Currently I'm trying latest version of coreos-vagrant with almost default settings. The only non default values:
config.rb file:
$num_instances=3

Vagrant file:
ip = "10.0.69.#{i+30}"

And after vagrant up here is what I'm getting when trying to ping the private network
ping from core-01 to core-02
core@core-01 ~ $ ping 10.0.69.32
PING 172.17.8.102 (172.17.8.102) 56(84) bytes of data.
64 bytes from 10.0.69.32: icmp_seq=1 ttl=64 time=8.47 ms
64 bytes from 10.0.69.32: icmp_seq=2 ttl=64 time=6.73 ms
64 bytes from 10.0.69.32 icmp_seq=3 ttl=64 time=2.27 ms
64 bytes from 10.0.69.32: icmp_seq=4 ttl=64 time=10.6 ms
64 bytes from 10.0.69.32: icmp_seq=5 ttl=64 time=11.5 ms
64 bytes from 10.0.69.32: icmp_seq=6 ttl=64 time=11.4 ms
64 bytes from 10.0.69.32: icmp_seq=7 ttl=64 time=8.15 ms
64 bytes from 10.0.69.32: icmp_seq=8 ttl=64 time=6.52 ms

I'm experiencing slow private network only under coreos instances. For example the same default private network between two vagrant centos 7 instances:
[root@lb-1 vagrant]# ping 10.0.69.3
PING 10.0.69.3 (10.0.69.3) 56(84) bytes of data.
64 bytes from 10.0.69.3: icmp_seq=1 ttl=64 time=0.389 ms
64 bytes from 10.0.69.3: icmp_seq=2 ttl=64 time=0.587 ms
64 bytes from 10.0.69.3: icmp_seq=3 ttl=64 time=0.678 ms
64 bytes from 10.0.69.3: icmp_seq=4 ttl=64 time=0.505 ms
64 bytes from 10.0.69.3: icmp_seq=5 ttl=64 time=0.563 ms

End here is the output from ping between one of the centos vagrant instances to core-01:
[root@lb-1 vagrant]# ping 10.0.69.31
PING 10.0.69.31 (10.0.69.31) 56(84) bytes of data.
64 bytes from 10.0.69.31: icmp_seq=1 ttl=64 time=5.99 ms
64 bytes from 10.0.69.31: icmp_seq=2 ttl=64 time=4.82 ms
64 bytes from 10.0.69.31: icmp_seq=3 ttl=64 time=162 ms
64 bytes from 10.0.69.31: icmp_seq=4 ttl=64 time=2.08 ms
64 bytes from 10.0.69.31: icmp_seq=5 ttl=64 time=9.50 ms
64 bytes from 10.0.69.31: icmp_seq=6 ttl=64 time=7.16 ms
64 bytes from 10.0.69.31: icmp_seq=7 ttl=64 time=156 ms
64 bytes from 10.0.69.31: icmp_seq=8 ttl=64 time=5.90 ms
64 bytes from 10.0.69.31: icmp_seq=9 ttl=64 time=3.39 ms
64 bytes from 10.0.69.31: icmp_seq=10 ttl=64 time=2.63 ms
64 bytes from 10.0.69.31: icmp_seq=11 ttl=64 time=96.9 ms
64 bytes from 10.0.69.31: icmp_seq=12 ttl=64 time=150 ms
64 bytes from 10.0.69.31: icmp_seq=13 ttl=64 time=8.86 ms
64 bytes from 10.0.69.31: icmp_seq=14 ttl=64 time=148 ms
64 bytes from 10.0.69.31: icmp_seq=15 ttl=64 time=7.07 ms

All the servers are empty (i.e. no docker instances under coreos or running process under centos).
The above experience i'm getting on the separate servers both with:
CentOS release 6.6 (Final)
Vagrant version: 1.7.2
CoreOS 633.1.0 (but also same issue with previews alfa version)
How I can speed up the private network?

Can you give me dmesg output from the host? It is almost certainly a local problem. Also, what OS, virtualbox version and vagrant version are you on? I am using OSX and VMWare Fusion and seeing sub millisecond pings.

CentOS release 6.6 (Final)
Vagrant version: 1.7.2
CoreOS 633.1.0 (but also same issue with previews alfa version)
The output from the centos host
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.32-504.8.1.el6.x86_64 (mockbuild@c6b9.bsys.dev.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) ) #1 SMP Wed Jan 28 21:11:36 UTC 2015
Command line: ro root=UUID=01341f68-0e59-4711-9015-68c95a784b47 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto  KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  Centaur CentaurHauls
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009d800 (usable)
 BIOS-e820: 000000000009d800 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000020000000 (usable)
 BIOS-e820: 0000000020000000 - 0000000020200000 (reserved)
 BIOS-e820: 0000000020200000 - 0000000040004000 (usable)
 BIOS-e820: 0000000040004000 - 0000000040005000 (reserved)
 BIOS-e820: 0000000040005000 - 00000000cd7c4000 (usable)
 BIOS-e820: 00000000cd7c4000 - 00000000ce026000 (reserved)
 BIOS-e820: 00000000ce026000 - 00000000ce0b0000 (usable)
 BIOS-e820: 00000000ce0b0000 - 00000000ce14c000 (ACPI NVS)
 BIOS-e820: 00000000ce14c000 - 00000000ce6d5000 (reserved)
 BIOS-e820: 00000000ce6d5000 - 00000000ce6d6000 (usable)
 BIOS-e820: 00000000ce6d6000 - 00000000ce719000 (ACPI NVS)
 BIOS-e820: 00000000ce719000 - 00000000cedc6000 (usable)
 BIOS-e820: 00000000cedc6000 - 00000000ceff2000 (reserved)
 BIOS-e820: 00000000ceff2000 - 00000000cf000000 (usable)
 BIOS-e820: 00000000cf800000 - 00000000dfa00000 (reserved)
 BIOS-e820: 00000000f8000000 - 00000000fc000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fed00000 - 00000000fed04000 (reserved)
 BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 000000041f600000 (usable)
DMI 2.7 present.
SMBIOS version 2.7 @ 0xF04C0
DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-VG3, BIOS P1.90 07/11/2013
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)
e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
last_pfn = 0x41f600 max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-BFFFF uncachable
  C0000-CFFFF write-protect
  D0000-E7FFF uncachable
  E8000-FFFFF write-protect
MTRR variable ranges enabled:
  0 base 000000000 mask C00000000 write-back
  1 base 400000000 mask FE0000000 write-back
  2 base 0E0000000 mask FE0000000 uncachable
  3 base 0D0000000 mask FF0000000 uncachable
  4 base 0CF800000 mask FFF800000 uncachable
  5 base 41F800000 mask FFF800000 uncachable
  6 base 41F600000 mask FFFE00000 uncachable
  7 disabled
  8 disabled
  9 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
original variable MTRRs
reg 0, base: 0GB, range: 16GB, type WB
reg 1, base: 16GB, range: 512MB, type WB
reg 2, base: 3584MB, range: 512MB, type UC
reg 3, base: 3328MB, range: 256MB, type UC
reg 4, base: 3320MB, range: 8MB, type UC
reg 5, base: 16888MB, range: 8MB, type UC
reg 6, base: 16886MB, range: 2MB, type UC
total RAM covered: 16110M
Found optimal setting for mtrr clean up
 gran_size: 64K 	chunk_size: 16M 	num_reg: 9  	lose cover RAM: 0G
New variable MTRRs
reg 0, base: 0GB, range: 2GB, type WB
reg 1, base: 2GB, range: 1GB, type WB
reg 2, base: 3GB, range: 256MB, type WB
reg 3, base: 3320MB, range: 8MB, type UC
reg 4, base: 4GB, range: 4GB, type WB
reg 5, base: 8GB, range: 8GB, type WB
reg 6, base: 16GB, range: 512MB, type WB
reg 7, base: 16886MB, range: 2MB, type UC
reg 8, base: 16888MB, range: 8MB, type UC
e820 update range: 00000000cf800000 - 0000000100000000 (usable) ==> (reserved)
last_pfn = 0xcf000 max_arch_pfn = 0x400000000
initial memory mapped : 0 - 20000000
init_memory_mapping: 0000000000000000-00000000cf000000
 0000000000 - 00cf000000 page 2M
kernel direct mapping tables up to cf000000 @ 10000-15000
Use unified mapping for non-reserved e820 regions.
init_memory_mapping: 0000000100000000-000000041f600000
 0100000000 - 041f600000 page 2M
kernel direct mapping tables up to 41f600000 @ 13000-21000
RAMDISK: 1effe000 - 1ffeff8a
ACPI: RSDP 00000000000f0490 00024 (v02 ALASKA)
ACPI: XSDT 00000000ce13e078 00074 (v01 ALASKA    A M I 01072009 AMI  00010013)
ACPI: FACP 00000000ce147388 0010C (v05 ALASKA    A M I 01072009 AMI  00010013)
ACPI Warning: FADT (revision 5) is longer than ACPI 2.0 version, truncating length 268 to 244 (20090903/tbfadt-288)
ACPI: DSDT 00000000ce13e188 091FC (v02 ALASKA    A M I 00000022 INTL 20051117)
ACPI: FACS 00000000ce14a080 00040
ACPI: APIC 00000000ce147498 00072 (v03 ALASKA    A M I 01072009 AMI  00010013)
ACPI: FPDT 00000000ce147510 00044 (v01 ALASKA    A M I 01072009 AMI  00010013)
ACPI: MCFG 00000000ce147558 0003C (v01 ALASKA    A M I 01072009 MSFT 00000097)
ACPI: SSDT 00000000ce147598 007E1 (v01 Intel_ AoacTabl 00001000 INTL 20091112)
ACPI: AAFT 00000000ce147d80 000EA (v01 ALASKA OEMAAFT  01072009 MSFT 00000097)
ACPI: HPET 00000000ce147e70 00038 (v01 ALASKA    A M I 01072009 AMI. 00000005)
ACPI: SSDT 00000000ce147ea8 0036D (v01 SataRe SataTabl 00001000 INTL 20091112)
ACPI: SSDT 00000000ce148218 00A92 (v01  PmRef    CpuPm 00003000 INTL 20051117)
ACPI: BGRT 00000000ce148cb0 00038 (v00 ALASKA    A M I 01072009 AMI  00010013)
ACPI: Local APIC address 0xfee00000
Setting APIC routing to flat.
No NUMA configuration found
Faking a node at 0000000000000000-000000041f600000
Bootmem setup node 0 0000000000000000-000000041f600000
  NODE_DATA [0000000000020000 - 0000000000053fff]
  bootmap [0000000000100000 -  0000000000183ebf] pages 84
(8 early reservations) ==> bootmem [0000000000 - 041f600000]
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
  #1 [0000006000 - 0000008000]       TRAMPOLINE ==> [0000006000 - 0000008000]
  #2 [0001000000 - 0002029be4]    TEXT DATA BSS ==> [0001000000 - 0002029be4]
  #3 [001effe000 - 001ffeff8a]          RAMDISK ==> [001effe000 - 001ffeff8a]
  #4 [000009d800 - 0000100000]    BIOS reserved ==> [000009d800 - 0000100000]
  #5 [000202a000 - 000202a1e7]              BRK ==> [000202a000 - 000202a1e7]
  #6 [0000010000 - 0000013000]          PGTABLE ==> [0000010000 - 0000013000]
  #7 [0000013000 - 0000020000]          PGTABLE ==> [0000013000 - 0000020000]
found SMP MP-table at [ffff8800000fd750] fd750
Reserving 130MB of memory at 48MB for crashkernel (System RAM: 16886MB)
 [ffffea0000000000-ffffea000e7fffff] PMD -> [ffff88002c600000-ffff88003a3fffff] on node 0
Zone PFN ranges:
  DMA      0x00000010 -> 0x00001000
  DMA32    0x00001000 -> 0x00100000
  Normal   0x00100000 -> 0x0041f600
Movable zone start PFN for each node
early_node_map[9] active PFN ranges
    0: 0x00000010 -> 0x0000009d
    0: 0x00000100 -> 0x00020000
    0: 0x00020200 -> 0x00040004
    0: 0x00040005 -> 0x000cd7c4
    0: 0x000ce026 -> 0x000ce0b0
    0: 0x000ce6d5 -> 0x000ce6d6
    0: 0x000ce719 -> 0x000cedc6
    0: 0x000ceff2 -> 0x000cf000
    0: 0x00100000 -> 0x0041f600
On node 0 totalpages: 4117142
  DMA zone: 56 pages used for memmap
  DMA zone: 117 pages reserved
  DMA zone: 3808 pages, LIFO batch:0
  DMA32 zone: 14280 pages used for memmap
  DMA32 zone: 824641 pages, LIFO batch:31
  Normal zone: 44765 pages used for memmap
  Normal zone: 3229475 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
Setting APIC routing to flat.
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a701 base: 0xfed00000
SMP: Allowing 4 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 24
PM: Registered nosave memory: 000000000009d000 - 000000000009e000
PM: Registered nosave memory: 000000000009e000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
PM: Registered nosave memory: 0000000020000000 - 0000000020200000
PM: Registered nosave memory: 0000000040004000 - 0000000040005000
PM: Registered nosave memory: 00000000cd7c4000 - 00000000ce026000
PM: Registered nosave memory: 00000000ce0b0000 - 00000000ce14c000
PM: Registered nosave memory: 00000000ce14c000 - 00000000ce6d5000
PM: Registered nosave memory: 00000000ce6d6000 - 00000000ce719000
PM: Registered nosave memory: 00000000cedc6000 - 00000000ceff2000
PM: Registered nosave memory: 00000000cf000000 - 00000000cf800000
PM: Registered nosave memory: 00000000cf800000 - 00000000dfa00000
PM: Registered nosave memory: 00000000dfa00000 - 00000000f8000000
PM: Registered nosave memory: 00000000f8000000 - 00000000fc000000
PM: Registered nosave memory: 00000000fc000000 - 00000000fec00000
PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000
PM: Registered nosave memory: 00000000fec01000 - 00000000fed00000
PM: Registered nosave memory: 00000000fed00000 - 00000000fed04000
PM: Registered nosave memory: 00000000fed04000 - 00000000fed1c000
PM: Registered nosave memory: 00000000fed1c000 - 00000000fed20000
PM: Registered nosave memory: 00000000fed20000 - 00000000fee00000
PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000
PM: Registered nosave memory: 00000000fee01000 - 00000000ff000000
PM: Registered nosave memory: 00000000ff000000 - 0000000100000000
Allocating PCI resources starting at dfa00000 (gap: dfa00000:18600000)
Booting paravirtualized kernel on bare hardware
NR_CPUS:4096 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1
PERCPU: Embedded 30 pages/cpu @ffff88002c200000 s90968 r8192 d23720 u524288
pcpu-alloc: s90968 r8192 d23720 u524288 alloc=1*2097152
pcpu-alloc: [0] 0 1 2 3
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 4057924
Policy zone: Normal
Kernel command line: ro root=UUID=01341f68-0e59-4711-9015-68c95a784b47 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=130M@0M  KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
PID hash table entries: 4096 (order: 3, 32768 bytes)
xsave/xrstor: enabled xstate_bv 0x7, cntxt size 0x340
Checking aperture...
No AGP bridge found
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Placing 64MB software IO TLB between ffff880024000000 - ffff880028000000
software IO TLB at phys 0x24000000 - 0x28000000
Memory: 16008144k/17291264k available (5336k kernel code, 822696k absent, 460424k reserved, 7016k data, 1288k init)
Hierarchical RCU implementation.
NR_IRQS:33024 nr_irqs:440
Extended CMOS year: 2000
Console: colour VGA+ 80x25
console [tty0] enabled
allocated 66060288 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
hpet clockevent registered
Fast TSC calibration using PIT
Detected 3292.691 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 6585.38 BogoMIPS (lpj=3292691)
pid_max: default: 32768 minimum: 301
Security Framework initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Mount-cache hash table entries: 256
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
Initializing cgroup subsys blkio
Initializing cgroup subsys perf_event
Initializing cgroup subsys net_prio
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 7 MCE banks
CPU0: Thermal monitoring enabled (TM1)
using mwait in idle threads.
ACPI: Core revision 20090903
ftrace: converting mcount calls to 0f 1f 44 00 00
ftrace: allocating 21918 entries in 86 pages
APIC routing finalized to flat.
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz stepping 09
Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
... version:                3
... bit width:              48
... generic registers:      4
... value mask:             0000ffffffffffff
... max period:             0000ffffffffffff
... fixed-purpose events:   3
... event mask:             000000070000000f
NMI watchdog enabled, takes one hw-pmu counter.
Booting Node   0, Processors  #1 #2 #3 Ok.
Brought up 4 CPUs
Total of 4 processors activated (26341.52 BogoMIPS).
sizeof(vma)=200 bytes
sizeof(page)=56 bytes
sizeof(inode)=592 bytes
sizeof(dentry)=192 bytes
sizeof(ext3inode)=800 bytes
sizeof(buffer_head)=104 bytes
sizeof(skbuff)=232 bytes
sizeof(task_struct)=2656 bytes
devtmpfs: initialized
PM: Registering ACPI NVS region at ce0b0000 (638976 bytes)
PM: Registering ACPI NVS region at ce6d6000 (274432 bytes)
regulator: core version 0.5
NET: Registered protocol family 16
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
ACPI: bus type pci registered
PCI: MCFG configuration 0: base f8000000 segment 0 buses 0 - 63
PCI: MCFG area at f8000000 reserved in E820
PCI: Using MMCONFIG at f8000000 - fbffffff
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: No dock devices found.
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
pci_root PNP0A08:00: host bridge window [io  0x0000-0x0cf7]
pci_root PNP0A08:00: host bridge window [io  0x0d00-0xffff]
pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000d3fff]
pci_root PNP0A08:00: host bridge window [mem 0x000d4000-0x000d7fff]
pci_root PNP0A08:00: host bridge window [mem 0x000d8000-0x000dbfff]
pci_root PNP0A08:00: host bridge window [mem 0x000dc000-0x000dffff]
pci_root PNP0A08:00: host bridge window [mem 0x000e0000-0x000e3fff]
pci_root PNP0A08:00: host bridge window [mem 0x000e4000-0x000e7fff]
pci_root PNP0A08:00: host bridge window [mem 0xdfa00000-0xfeafffff]
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7]
pci_bus 0000:00: root bus resource [io  0x0d00-0xffff]
pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
pci_bus 0000:00: root bus resource [mem 0xdfa00000-0xfeafffff]
pci 0000:00:02.0: reg 10: [mem 0xf7800000-0xf7bfffff 64bit]
pci 0000:00:02.0: reg 18: [mem 0xe0000000-0xefffffff 64bit pref]
pci 0000:00:02.0: reg 20: [io  0xf000-0xf03f]
pci 0000:00:16.0: reg 10: [mem 0xf7c0a000-0xf7c0a00f 64bit]
pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
pci 0000:00:16.0: PME# disabled
pci 0000:00:1a.0: reg 10: [mem 0xf7c08000-0xf7c083ff]
pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.0: PME# disabled
pci 0000:00:1b.0: reg 10: [mem 0xf7c00000-0xf7c03fff 64bit]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.3: PME# disabled
pci 0000:00:1d.0: reg 10: [mem 0xf7c07000-0xf7c073ff]
pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.0: PME# disabled
pci 0000:00:1f.2: reg 10: [io  0xf0b0-0xf0b7]
pci 0000:00:1f.2: reg 14: [io  0xf0a0-0xf0a3]
pci 0000:00:1f.2: reg 18: [io  0xf090-0xf097]
pci 0000:00:1f.2: reg 1c: [io  0xf080-0xf083]
pci 0000:00:1f.2: reg 20: [io  0xf060-0xf07f]
pci 0000:00:1f.2: reg 24: [mem 0xf7c06000-0xf7c067ff]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:00:1f.3: reg 10: [mem 0xf7c05000-0xf7c050ff 64bit]
pci 0000:00:1f.3: reg 20: [io  0xf040-0xf05f]
pci 0000:00:1c.0: PCI bridge to [bus 01-01]
pci 0000:02:00.0: reg 10: [io  0xe000-0xe0ff]
pci 0000:02:00.0: reg 18: [mem 0xf0004000-0xf0004fff 64bit pref]
pci 0000:02:00.0: reg 20: [mem 0xf0000000-0xf0003fff 64bit pref]
pci 0000:02:00.0: supports D1 D2
pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:02:00.0: PME# disabled
pci 0000:00:1c.3: PCI bridge to [bus 02-02]
pci 0000:00:1c.3:   bridge window [io  0xe000-0xefff]
pci 0000:00:1c.3:   bridge window [mem 0xf0000000-0xf00fffff 64bit pref]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT]
 pci0000:00: Requesting ACPI _OSC control (0x1d)
 pci0000:00: ACPI _OSC control (0x18) granted
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 *4 5 6 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 10 11 12 14 15)
vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
vgaarb: bridge control possible 0000:00:02.0
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: old code would have set cacheline size to 32 bytes, but clflush_size = 64
PCI: pci_cache_line_size set to 64 bytes
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
  alloc irq_desc for 24 on node -1
  alloc kstat_irqs on node -1
  alloc irq_desc for 25 on node -1
  alloc kstat_irqs on node -1
  alloc irq_desc for 26 on node -1
  alloc kstat_irqs on node -1
  alloc irq_desc for 27 on node -1
  alloc kstat_irqs on node -1
HPET: 8 timers in total, 4 timers will be used for per-cpu timer
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 24, 25, 26, 27, 0, 0
hpet0: 8 comparators, 64-bit 14.318180 MHz counter
hpet: hpet2 irq 24 for MSI
hpet: hpet3 irq 25 for MSI
hpet: hpet4 irq 26 for MSI
hpet: hpet5 irq 27 for MSI
Switching to clocksource hpet
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:00: [io  0x0cf8-0x0cff]
pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
pnp 00:01: [mem 0xfed40000-0xfed44fff]
pnp 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
pnp 00:02: [io  0x0000-0x001f]
pnp 00:02: [io  0x0081-0x0091]
pnp 00:02: [io  0x0093-0x009f]
pnp 00:02: [io  0x00c0-0x00df]
pnp 00:02: [dma 4]
pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
pnp 00:03: [mem 0xff000000-0xffffffff]
pnp 00:03: Plug and Play ACPI device, IDs INT0800 (active)
pnp 00:04: [mem 0xfed00000-0xfed003ff]
pnp 00:04: Plug and Play ACPI device, IDs PNP0103 (active)
pnp 00:05: [io  0x002e-0x002f]
pnp 00:05: [io  0x004e-0x004f]
pnp 00:05: [io  0x0061]
pnp 00:05: [io  0x0063]
pnp 00:05: [io  0x0065]
pnp 00:05: [io  0x0067]
pnp 00:05: [io  0x0070]
pnp 00:05: [io  0x0080]
pnp 00:05: [io  0x0092]
pnp 00:05: [io  0x00b2-0x00b3]
pnp 00:05: [io  0x0680-0x069f]
pnp 00:05: [io  0x1000-0x100f]
pnp 00:05: [io  0xffff]
pnp 00:05: [io  0xffff]
pnp 00:05: [io  0x0400-0x0453]
pnp 00:05: [io  0x0458-0x047f]
pnp 00:05: [io  0x0500-0x057f]
pnp 00:05: [io  0x164e-0x164f]
pnp 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:06: [io  0x0070-0x0077]
pnp 00:06: [irq 8]
pnp 00:06: Plug and Play ACPI device, IDs PNP0b00 (active)
pnp 00:07: [io  0x0454-0x0457]
pnp 00:07: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
pnp 00:08: [io  0x0000-0xffffffffffffffff disabled]
pnp 00:08: [io  0x0290-0x029f]
pnp 00:08: [io  0x0000-0xffffffffffffffff disabled]
pnp 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:09: [io  0x0010-0x001f]
pnp 00:09: [io  0x0022-0x003f]
pnp 00:09: [io  0x0044-0x005f]
pnp 00:09: [io  0x0062-0x0063]
pnp 00:09: [io  0x0065-0x006f]
pnp 00:09: [io  0x0072-0x007f]
pnp 00:09: [io  0x0080]
pnp 00:09: [io  0x0084-0x0086]
pnp 00:09: [io  0x0088]
pnp 00:09: [io  0x008c-0x008e]
pnp 00:09: [io  0x0090-0x009f]
pnp 00:09: [io  0x00a2-0x00bf]
pnp 00:09: [io  0x00e0-0x00ef]
pnp 00:09: [io  0x04d0-0x04d1]
pnp 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:0a: [io  0x00f0-0x00ff]
pnp 00:0a: [irq 13]
pnp 00:0a: Plug and Play ACPI device, IDs PNP0c04 (active)
pnp 00:0b: [mem 0xfed1c000-0xfed1ffff]
pnp 00:0b: [mem 0xfed10000-0xfed17fff]
pnp 00:0b: [mem 0xfed18000-0xfed18fff]
pnp 00:0b: [mem 0xfed19000-0xfed19fff]
pnp 00:0b: [mem 0xf8000000-0xfbffffff]
pnp 00:0b: [mem 0xfed20000-0xfed3ffff]
pnp 00:0b: [mem 0xfed90000-0xfed93fff]
pnp 00:0b: [mem 0xfed45000-0xfed8ffff]
pnp 00:0b: [mem 0xff000000-0xffffffff]
pnp 00:0b: [mem 0xfee00000-0xfeefffff]
pnp 00:0b: [mem 0xdfa00000-0xdfa00fff]
pnp 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:0c: [mem 0x20000000-0x201fffff]
pnp 00:0c: [mem 0x40004000-0x40004fff]
pnp 00:0c: Plug and Play ACPI device, IDs PNP0c01 (active)
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: [mem 0xfed40000-0xfed44fff] has been reserved
system 00:05: [io  0x0680-0x069f] has been reserved
system 00:05: [io  0x1000-0x100f] has been reserved
system 00:05: [io  0xffff] has been reserved
system 00:05: [io  0xffff] has been reserved
system 00:05: [io  0x0400-0x0453] has been reserved
system 00:05: [io  0x0458-0x047f] has been reserved
system 00:05: [io  0x0500-0x057f] has been reserved
system 00:05: [io  0x164e-0x164f] has been reserved
system 00:07: [io  0x0454-0x0457] has been reserved
system 00:08: [io  0x0290-0x029f] has been reserved
system 00:09: [io  0x04d0-0x04d1] has been reserved
system 00:0b: [mem 0xfed1c000-0xfed1ffff] has been reserved
system 00:0b: [mem 0xfed10000-0xfed17fff] has been reserved
system 00:0b: [mem 0xfed18000-0xfed18fff] has been reserved
system 00:0b: [mem 0xfed19000-0xfed19fff] has been reserved
system 00:0b: [mem 0xf8000000-0xfbffffff] has been reserved
system 00:0b: [mem 0xfed20000-0xfed3ffff] has been reserved
system 00:0b: [mem 0xfed90000-0xfed93fff] has been reserved
system 00:0b: [mem 0xfed45000-0xfed8ffff] has been reserved
system 00:0b: [mem 0xff000000-0xffffffff] has been reserved
system 00:0b: [mem 0xfee00000-0xfeefffff] could not be reserved
system 00:0b: [mem 0xdfa00000-0xdfa00fff] has been reserved
system 00:0c: [mem 0x20000000-0x201fffff] has been reserved
system 00:0c: [mem 0x40004000-0x40004fff] has been reserved
pci 0000:00:1c.0: PCI bridge to [bus 01-01]
pci 0000:00:1c.3: PCI bridge to [bus 02-02]
pci 0000:00:1c.3:   bridge window [io  0xe000-0xefff]
pci 0000:00:1c.3:   bridge window [mem 0xf0000000-0xf00fffff 64bit pref]
  alloc irq_desc for 16 on node -1
  alloc kstat_irqs on node -1
pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.0: setting latency timer to 64
  alloc irq_desc for 19 on node -1
  alloc kstat_irqs on node -1
pci 0000:00:1c.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19
pci 0000:00:1c.3: setting latency timer to 64
pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7]
pci_bus 0000:00: resource 5 [io  0x0d00-0xffff]
pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff]
pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff]
pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff]
pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff]
pci_bus 0000:00: resource 11 [mem 0x000e0000-0x000e3fff]
pci_bus 0000:00: resource 12 [mem 0x000e4000-0x000e7fff]
pci_bus 0000:00: resource 13 [mem 0xdfa00000-0xfeafffff]
pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
pci_bus 0000:02: resource 2 [mem 0xf0000000-0xf00fffff 64bit pref]
NET: Registered protocol family 2
IP route cache hash table entries: 524288 (order: 10, 4194304 bytes)
TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 524288 bind 65536)
TCP reno registered
NET: Registered protocol family 1
pci 0000:00:02.0: Boot video device
pci 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1a.0: PCI INT A disabled
  alloc irq_desc for 23 on node -1
  alloc kstat_irqs on node -1
pci 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
pci 0000:00:1d.0: PCI INT A disabled
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 16327k freed
futex hash table entries: 1024 (order: 4, 65536 bytes)
audit: initializing netlink socket (disabled)
type=2000 audit(1427413318.318:1): initialized
HugeTLB registered 2 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 31297
SELinux:  Registering netfilter hooks
alg: No test for stdrng (krng)
ksign: Installing public key data
Loading keyring
- Added public key 99BA280A469ED0C1
- User ID: CentOS (Kernel Module GPG key)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
intel_idle: MWAIT substates: 0x1120
intel_idle: v0.4 model 0x3A
intel_idle: lapic_timer_reliable_states 0xffffffff
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
ACPI: Power Button [PWRF]
ACPI: acpi_idle yielding to intel_idleACPI Error (psargs-0359): [\_PR_.CPU0._PPC] Namespace lookup failure, AE_NOT_FOUND
ACPI Error (psparse-0537): Method parse/execution failed [\_PR_.CPU0._PDC] (Node ffff880419090538), AE_NOT_FOUND
ACPI: SSDT 00000000cdfd5c18 00119 (v01  PmRef    ApCst 00003000 INTL 20051117)
[Firmware Bug]: No valid trip found
GHES: HEST is not enabled!
Non-volatile memory driver v1.3
Linux agpgart interface v0.103
crash memory driver: version 1.1
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
brd: module loaded
loop: module loaded
input: Macintosh mouse button emulation as /devices/virtual/input/input2
Fixed MDIO Bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ehci_hcd 0000:00:1a.0: setting latency timer to 64
ehci_hcd 0000:00:1a.0: EHCI Host Controller
ehci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.0: debug port 2
ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported
ehci_hcd 0000:00:1a.0: irq 16, io mem 0xf7c08000
ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.32-504.8.1.el6.x86_64 ehci_hcd
usb usb1: SerialNumber: 0000:00:1a.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.0: setting latency timer to 64
ehci_hcd 0000:00:1d.0: EHCI Host Controller
ehci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.0: debug port 2
ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported
ehci_hcd 0000:00:1d.0: irq 23, io mem 0xf7c07000
ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: EHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.32-504.8.1.el6.x86_64 ehci_hcd
usb usb2: SerialNumber: 0000:00:1d.0
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
rtc_cmos 00:06: RTC can wake from S4
rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
cpuidle: using governor ladder
cpuidle: using governor menu
EFI Variables Facility v0.08 2004-May-17
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
GRE over IPv4 demultiplexor driver
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
registered taskstats version 1
rtc_cmos 00:06: setting system clock to 2015-03-26 23:41:59 UTC (1427413319)
Initalizing network drop monitor service
Freeing unused kernel memory: 1288k freed
Write protecting the kernel read-only data: 10240k
Freeing unused kernel memory: 788k freed
Freeing unused kernel memory: 1568k freed
dracut: dracut-004-356.el6
dracut: rd_NO_LUKS: removing cryptoluks activation
dracut: rd_NO_LVM: removing LVM activation
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
udev: starting version 147
[drm] Initialized drm 1.1.0 20060810
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[drm] Memory usable by graphics device = 2048M
i915 0000:00:02.0: setting latency timer to 64
  alloc irq_desc for 28 on node -1
  alloc kstat_irqs on node -1
i915 0000:00:02.0: irq 28 for MSI/MSI-X
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
i915 0000:00:02.0: No connectors reported connected with modes
[drm] Cannot find any crtc or sizes - going 1024x768
fbcon: inteldrmfb (fb0) is primary device
Console: switching to colour frame buffer device 128x48
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
i915 0000:00:02.0: registered panic notifier
acpi device:41: registered as cooling_device4
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3
ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
dracut: Starting plymouth daemon
usb 1-1: new high speed USB device number 2 using ehci_hcd
dracut: rd_NO_MD: removing MD RAID activation
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
  alloc irq_desc for 29 on node -1
  alloc kstat_irqs on node -1
ahci 0000:00:1f.2: irq 29 for MSI/MSI-X
ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 3 Gbps 0x33 impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst
ahci 0000:00:1f.2: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 abar m2048@0xf7c06000 port 0xf7c06100 irq 29
ata2: SATA max UDMA/133 abar m2048@0xf7c06000 port 0xf7c06180 irq 29
ata3: DUMMY
ata4: DUMMY
ata5: SATA max UDMA/133 abar m2048@0xf7c06000 port 0xf7c06300 irq 29
ata6: SATA max UDMA/133 abar m2048@0xf7c06000 port 0xf7c06380 irq 29
usb 1-1: New USB device found, idVendor=8087, idProduct=0024
usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 2-1: new high speed USB device number 2 using ehci_hcd
usb 2-1: New USB device found, idVendor=8087, idProduct=0024
usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 2-1: configuration #1 chosen from 1 choice
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 6 ports detected
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5: SATA link down (SStatus 0 SControl 300)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6: SATA link down (SStatus 0 SControl 300)
ata2.00: ACPI _SDD failed (AE 0x5)
Refined TSC clocksource calibration: 3292.520 MHz.
Switching to clocksource tsc
[drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
ata1.00: ACPI _SDD failed (AE 0x5)
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ACPI _SDD failed (AE 0x5)
ata2.00: ACPI: failed the second time, disabled
ata2.00: ATA-9: WDC WD20EZRX-00D8PB0, 80.00A80, max UDMA/133
ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
ata2.00: configured for UDMA/133
ata1.00: ACPI _SDD failed (AE 0x5)
ata1.00: ACPI: failed the second time, disabled
ata1.00: ATA-8: KINGSTON SV300S37A120G, 506ABBF0, max UDMA/133
ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      KINGSTON SV300S3 506A PQ: 0 ANSI: 5
scsi 1:0:0:0: Direct-Access     ATA      WDC WD20EZRX-00D 80.0 PQ: 0 ANSI: 5
STARTING CRC_T10DIF
sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 1:0:0:0: [sdb] 4096-byte physical blocks
sd 0:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb:
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
 unknown partition table
sd 1:0:0:0: [sdb] Attached SCSI disk
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts:
dracut: Mounted root filesystem /dev/sda2
SELinux:  Disabled at runtime.
SELinux:  Unregistering netfilter hooks
type=1404 audit(1427413325.813:2): selinux=0 auid=4294967295 ses=4294967295
dracut:
dracut: Switching root
udev: starting version 147
  alloc irq_desc for 22 on node -1
  alloc kstat_irqs on node -1
snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
  alloc irq_desc for 30 on node -1
  alloc kstat_irqs on node -1
snd_hda_intel 0000:00:1b.0: irq 30 for MSI/MSI-X
snd_hda_intel 0000:00:1b.0: setting latency timer to 64
input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input4
input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5
input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20090903/utaddress-254)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000057f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20090903/utaddress-254)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
lpc_ich: Resource conflict(s) found affecting gpio_ich
  alloc irq_desc for 18 on node -1
  alloc kstat_irqs on node -1
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI) (20090903/utaddress-254)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
r8169 0000:02:00.0: setting latency timer to 64
  alloc irq_desc for 31 on node -1
  alloc kstat_irqs on node -1
r8169 0000:02:00.0: irq 31 for MSI/MSI-X
r8169 0000:02:00.0: eth0: RTL8168evl/8111evl at 0xffffc900065fc000, bc:5f:f4:d4:0b:bd, XID 0c900800 IRQ 31
r8169 0000:02:00.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07rh
iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts:
EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts:
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ip6_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
r8169 0000:02:00.0: firmware: requesting rtl_nic/rtl8168e-3.fw
r8169 0000:02:00.0: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
r8169 0000:02:00.0: eth0: link up
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
type=1305 audit(1427413329.973:3): audit_pid=1513 old=0 auid=4294967295 ses=4294967295 res=1
p4-clockmod: Warning: EST-capable CPU detected. The acpi-cpufreq module offers voltage scaling in addition to frequency scaling. You should use that instead of p4-clockmod, if possible.
vboxdrv: Found 4 processor cores.
vboxdrv: fAsync=0 offMin=0x1d4 offMax=0x1fb8
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.3.22 (interface 0x001a0009).
vboxpci: IOMMU not found (not compiled)
coretemp coretemp.0: TjMax is 105 C.
coretemp coretemp.0: TjMax is 105 C.
eth0: no IPv6 routers present
device vboxnet4 entered promiscuous mode
vboxnet4: no IPv6 routers present
device vboxnet8 entered promiscuous mode
vboxnet8: no IPv6 routers present
device eth0 entered promiscuous mode
INTNET-RECV[9545]: segfault at 7fe9a5dc53d9 ip 00007fe9ce93b6ad sp 00007fe99136ea90 error 4 in libpthread-2.12.so[7fe9ce92f000+17000]
Bridge firewalling registered
device vboxnet10 entered promiscuous mode
vboxnet10: no IPv6 routers present
device vboxnet10 left promiscuous mode
vboxnetflt: 0 out of 101 packets were not sent (directed to host)
device vboxnet10 entered promiscuous mode

@philips same issue using:
Mac Book Pro
Virtualbox v4.3.22r98236
Vagrant v1.7.2
CoreOS v640.0.0 (latest)
Here is the core-01 dmesg ouput:
https://gist.github.com/mlazarov/10ad38b7aedeb82b17e7

Now i'm sure it is coreos related bug.
Running only one coreos instance (not a coreos cluster) and the issue is missing - the network delay between the host and the coreos instance is constantly 0.35ms

Finaly for other trapped in this case: the issue only appears when using more than one cpu core per coreos instance. Using only one core and the problem disappears!

I have this issue and I'm using just one core ... the networking throughput between Guest and Host is ~ 45Mb/s ...

l15k4, how you are measuring this speed? Can you give some information about the ping times between the host and the CoreOS instance?

@mlazarov
ping times :
core@localhost ~ $ ping 10.0.2.2
PING 10.0.2.2 (10.0.2.2) 56(84) bytes of data.
64 bytes from 10.0.2.2: icmp_seq=1 ttl=63 time=0.695 ms
64 bytes from 10.0.2.2: icmp_seq=2 ttl=63 time=0.925 ms
64 bytes from 10.0.2.2: icmp_seq=3 ttl=63 time=0.822 ms
64 bytes from 10.0.2.2: icmp_seq=4 ttl=63 time=0.891 ms
64 bytes from 10.0.2.2: icmp_seq=5 ttl=63 time=0.632 ms
64 bytes from 10.0.2.2: icmp_seq=6 ttl=63 time=0.692 ms
64 bytes from 10.0.2.2: icmp_seq=7 ttl=63 time=0.919 ms
64 bytes from 10.0.2.2: icmp_seq=8 ttl=63 time=0.971 ms
64 bytes from 10.0.2.2: icmp_seq=9 ttl=63 time=0.926 ms
64 bytes from 10.0.2.2: icmp_seq=10 ttl=63 time=0.881 ms
64 bytes from 10.0.2.2: icmp_seq=11 ttl=63 time=0.860 ms

I'm running local docker repository to cache images and then pulling all my images I'm using in vagrant to spare  resources, like this  docker pull 10.0.2.2:5000/foo/bar
The problem is that the throughput of "lo" interface  doesn't cross 40Mb/s so it is pulling the images extremely slowly if I do the same on my host machine it is pulling them by ~ 400MB/s so instead of gaining like 80x bump I speeded it up like 5 times max

Moved to https://github.com/coreos/bugs/issues/1343

authors: crawford l15k4 mlazarov philips

repo: coreos/coreos-vagrant


text:
Fixed libvirt script name

minor fix
/cc @robszumski

LGTM

authors: kayrus robszumski

repo: coreos/docs


text:
Some requests becomes very slow(several seconds)

We made a test on kubernetes and etcd: 4500 nodes, each has one pod. Then from the log of API server, some requests becomes very slow(seconds), and others are normal:
I0331 18:20:57.395788       6 handlers.go:144] , PUT /api/v1/nodes/10.181.25.72/status: (114.958349ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:21434]
I0331 18:20:57.397911       6 handlers.go:144] , PUT /api/v1/nodes/10.181.17.88/status: (111.765933ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:17112]
I0331 18:20:57.398033       6 handlers.go:144] , PUT /api/v1/nodes/10.181.30.171/status: (122.495104ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:49117]
I0331 18:20:57.398760       6 handlers.go:144] , PUT /api/v1/nodes/10.181.29.91/status: (122.507883ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:21683]
I0331 18:20:57.398988       6 handlers.go:144] , PUT /api/v1/nodes/10.181.17.240/status: (114.352425ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:22163]
I0331 18:20:57.399574       6 handlers.go:144] , PUT /api/v1/nodes/10.181.29.161/status: (114.201966ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:21821]
I0331 18:20:57.399955       6 handlers.go:144] , PUT /api/v1/nodes/10.181.30.55/status: (114.618983ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:21148]
I0331 18:20:57.401170       6 handlers.go:144] , PUT /api/v1/nodes/10.181.21.70/status: (128.034216ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:22215]
I0331 18:20:57.402067       6 handlers.go:144] , GET /api/v1/services: (2.107599062s) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:44284]
I0331 18:20:57.403535       6 handlers.go:144] , PUT /api/v1/nodes/10.181.23.202/status: (112.886076ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:20543]
I0331 18:20:57.405869       6 handlers.go:144] , PUT /api/v1/nodes/10.181.29.67/status: (145.922009ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:17561]
I0331 18:20:57.405895       6 handlers.go:144] , PUT /api/v1/nodes/10.181.24.244/status: (2.472018267s) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:12967]
I0331 18:20:57.406131       6 handlers.go:144] , PUT /api/v1/nodes/10.181.26.231/status: (113.295554ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:21904]
I0331 18:20:57.406217       6 handlers.go:144] , PUT /api/v1/nodes/10.181.30.214/status: (125.41683ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:15228]
I0331 18:20:57.406274       6 handlers.go:144] , PUT /api/v1/nodes/10.181.23.196/status: (118.959124ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:32937]
I0331 18:20:57.406311       6 handlers.go:144] , PUT /api/v1/nodes/10.181.25.170/status: (114.947446ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:35304]
I0331 18:20:57.406341       6 handlers.go:144] , PUT /api/v1/nodes/10.181.19.87/status: (116.553634ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:39378]
I0331 18:20:57.406461       6 handlers.go:144] , PUT /api/v1/nodes/10.181.33.15/status: (120.794757ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:16322]
I0331 18:20:57.406886       6 handlers.go:144] , PUT /api/v1/nodes/10.181.30.219/status: (121.67343ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:18948]
I0331 18:20:57.406990       6 handlers.go:144] , PUT /api/v1/nodes/10.181.28.3/status: (146.058874ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:15068]
I0331 18:20:57.407187       6 handlers.go:144] , PUT /api/v1/nodes/10.181.32.232/status: (2.474173989s) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:2995]
I0331 18:20:57.407295       6 handlers.go:144] , PUT /api/v1/nodes/10.181.31.192/status: (115.19927ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:17204]
I0331 18:20:57.407333       6 handlers.go:144] , PUT /api/v1/nodes/10.181.20.177/status: (115.41544ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:54553]
I0331 18:20:57.407474       6 handlers.go:144] , PUT /api/v1/nodes/10.181.19.198/status: (121.624376ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:64090]
I0331 18:20:57.407657       6 handlers.go:144] , PUT /api/v1/nodes/10.181.22.2/status: (146.841849ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:19616]
I0331 18:20:57.407689       6 handlers.go:144] , PUT /api/v1/nodes/10.181.16.54/status: (117.484453ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:36729]
I0331 18:20:57.407806       6 handlers.go:144] , PUT /api/v1/nodes/10.181.23.199/status: (122.410125ms) 200 [[kubelet/v1.0.0.12 (linux/amd64) kubernetes/unknown] 115.236.124.141:51271]

As the log demonstrate, one GET and one PUT requests is very slow, but others are normal. It's really strange.
BTW, there are some "broken pipe" log in etcd's log, what's the meaning of this log?
81814 2016-03-31 12:17:30.714777 W | etcdhttp: error writing event (write tcp 10.180.10.215:2379->10.180.8.215:60910: write: broken pipe)
81815 2016-03-31 12:17:32.378037 W | etcdhttp: error writing event (write tcp 10.180.10.215:2379->10.180.8.215:54154: write: broken pipe)
81816 2016-03-31 12:17:34.574282 W | etcdhttp: error writing event (write tcp 10.180.10.215:2379->10.180.8.215:33120: write: broken pipe)
81817 2016-03-31 12:17:47.079529 W | etcdhttp: error writing event (write tcp 10.180.10.215:2379->10.180.8.215:57699: write: broken pipe)
81818 2016-03-31 12:17:47.648702 W | etcdhttp: error writing event (write tcp 10.180.10.215:2379->10.180.8.215:33729: write: broken pipe)

Do you know how many items will that get return? And what size is the returned response?
Broken pipe means the client has already closed the connection. Most of the time it is a client side issue.
Moreover, please check https://github.com/coreos/etcd/blob/master/Documentation/reporting_bugs.md#reporting-bugs before reporting bugs.
We can look into this if you can reproduce the issue in an isolated environment. Or you can open an issue in kubernetes.

@mqliang I chatted with some people working on k8s. It is probably just because k8s trying to return large response to user. Please verify the response type and size.

@xiang90 Thanks. We are now adding more logs to API server, hoping we could reproduce it and find out what on earth caused the strange fluctuation.
Close this. Will open a new one if we confirm that the fluctuation is from etcd.

repo: coreos/etcd


text:
etcdctl: use os.Stdout, os.Stderr directly for cmd

Related to https://github.com/coreos/etcd/issues/4287.

lgtm

Thanks.
@xiang90  If you don't have any objection, I will merge.
I don't see any reason to use another goroutine to copy stdout, stderr.
I saw this pattern in old etcdctl code (since day 1).

LGTM

Thanks

authors: gyuho heyitsanthony xiang90


text:
Add arm64 travis builds

See: https://github.com/coreos/etcd/issues/5054

overall this seems OK and the CI hit doesn't look too bad. Are there any solid plans for getting arm64 unit/integration tests working with CI yet?

Reworked and pushed out an update that just uses GOARCH.
We are working on a local Jenkins installation to run the tests here at Huawei.  It does not seem practical to do them with github travis, as we would need an arm64 execution environment (QEMU for example).  See: #5054

lgtm after squashing. defer to @xiang90

OK, by 'squash', did you want me put these into a single patch?

@glevand yes

lgtm

authors: glevand heyitsanthony xiang90


text:
All hosts get same subnet and do not recognize the other hosts

I trying out flannel using cores-vagrant. I start up 3 hosts and install the flannel binary in each of them. I add the network configuration using etcdctl and then start flannel on each host using
sudo /opt/bin/flanneld &
and on all hosts I get the same output
Installing signal handlers
I0926 06:56:56.933827 00733 main.go:89] Determining IP address of default interface
I0926 06:56:56.934355 00733 main.go:164] Using 10.0.2.15 as external interface
I0926 06:56:56.997207 00733 subnet.go:80] Subnet lease acquired: 10.0.78.0/24
I0926 06:56:57.001976 00733 main.go:175] UDP mode initialized
I0926 06:56:57.002595 00733 udp.go:238] Watching for new subnet leases
coreos-vagrant creates two network adapters on each host : one nat and one host only
Could my problem be that flannel selects the NAT adapter (10.0.2.15)?

Life-saver right here!

Life-saver :+1:

authors: helander kiddkai pires

repo: coreos/flannel


text:
EtcdLease should not use ListenableFuture directly

Currently, EtcdLease exposes com.google.common.util.concurrent.ListenableFuture as a part of API. If ListenableFuture is used directly, it will conflict with user-side guava library. Instead, ListenableSetFuture in #45 or some wrapper class in com.coreos.jetcd should be used to avoid the problem.

This is related to #16.
IMHO best would be to shade guava and use CompletableFutures as suggested by @jurmous

@lburgazzoli thanks for the notification. I will also check #16.
I have a patch to shade Guava into jetcd locally, so I can send a PR soon. However, it can increase the size of binary. Can we accept it?

I do not know, but having had quite a few issues with guava dependencies I would really like not to do it again ;)

Thanks for your comment. I agree with you. Created #47. I appreciate if you take look.

closing via https://github.com/coreos/jetcd/pull/109

authors: fanminshi lburgazzoli oza

repo: coreos/jetcd


text:
Can't set objstore option for thanos.

What did you do?
Thanos latest version supports objstore.config options instead of s3.xxx (these are removed)
So when I use set thanos v0.2.0, storage configuration is not applied properly.
--objstore.config-file=/etc/thanos/thanos-s3.yaml
https://github.com/improbable-eng/thanos/blob/master/cmd/thanos/flags.go
func regCommonObjStoreFlags(cmd *kingpin.CmdClause, suffix string) *pathOrContent {
	fileFlagName := fmt.Sprintf("objstore%s.config-file", suffix)
	bucketConfFile := cmd.Flag(fileFlagName, fmt.Sprintf("Path to YAML file that contains object store%s configuration.", suffix)).
		PlaceHolder("<bucket.config-yaml-path>").String()

	bucketConf := cmd.Flag(fmt.Sprintf("objstore%s.config", suffix), fmt.Sprintf("Alternative to '%s' flag. Object store%s configuration in YAML.", fileFlagName, suffix)).
		PlaceHolder("<bucket.config-yaml>").String()

	return &pathOrContent{
		name: fmt.Sprintf("objstore%s.config", suffix),

		path:    bucketConfFile,
		content: bucketConf,
	}
}

I can't find any related code in prometheus-operator.
What did you expect to see?
I want to add objstore.config and objstore.config.file options.
What did you see instead? Under which circumstances?
Environment

Prometheus Operator version:
insert image tag or Git SHA here

Kubernetes version information:
insert output of kubectl version here

Kubernetes cluster kind:
insert how you created your cluster: kops, bootkube, tectonic-installer, etc.

Manifests:

insert manifests relevant to the issue

Prometheus Operator Logs:

insert Prometheus Operator logs relevant to the issue here

Related code
https://github.com/coreos/prometheus-operator/blob/0ea64587a152727e072986dbe6cd60a06b57a545/pkg/prometheus/statefulset.go#L702-L732
Errror(s) seen within sidecar when trying to use v0.2.0 of  Thanos...
Error parsing commandline arguments: unknown long flag '--s3.bucket'
thanos: error: unknown long flag '--s3.bucket'

Looking at the thanos sidecar we can see the operator is attempting to pass in s3 bucket details via args
thanos-sidecar:
    Container ID:  docker://6e19519c626edbfcc6354c31935828f88e78ab5dff4cb7552d88b556edf44570
    Image:         improbable/thanos:v0.2.0
    Image ID:      docker-pullable://improbable/thanos@sha256:7555f2255dbfa7791cb9630a4633d8e22c1fba34071eec13954a2f44ec203ad1
    Ports:         10902/TCP, 10901/TCP, 10900/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP
    Args:
      sidecar
      --prometheus.url=http://127.0.0.1:9090
      --tsdb.path=/prometheus
      --cluster.address=[$(POD_IP)]:10900
      --grpc-address=[$(POD_IP)]:10901
      --cluster.peers=thanos-peers:10900
      --s3.bucket=test
      --s3.endpoint=minio-service:9000
      --s3.insecure
      --s3.signature-version2
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Tue, 18 Dec 2018 15:21:25 -0500
      Finished:     Tue, 18 Dec 2018 15:21:25 -0500
    Ready:          False
    Restart Count:  17
    Environment:
      POD_IP:   (v1:status.podIP)
    Mounts:
      /prometheus from prometheus-prometheus-operator-prometheus-db (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from prometheus-operator-prometheus-token-bp7jx (ro)

However, with v0.2.0 and newer for Thanos, a ConfigSet with the s3 parameters should be setup in K8's and then used with a volumeMount via the --objstore.config-file=/your/file.yaml used via the volumeMount provided by a creates ConfigSet.

I made PR for this.
https://github.com/coreos/prometheus-operator/pull/2226#issuecomment-447338905

repo: coreos/prometheus-operator


text:
Hit maximum Secret size for prometheus.yaml in Kubernetes

What did you do?
Rolled out Prometheus-operator 0.26.0
What did you see instead? Under which circumstances?
operator.go:866] Sync "monitoring/platform-001" failed: creating config failed: Secret "prometheus-platform-001" is invalid: data: Too long: must have at most 1048576 characters

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.7", GitCommit:"0c38c362511b20a098d7cd855f1314dad92c2780", GitTreeState:"clean", BuildDate:"2018-08-20T10:09:03Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.11-gke.1", GitCommit:"5c4fddf874319c9825581cc9ab1d0f0cf51e1dc9", GitTreeState:"clean", BuildDate:"2018-11-30T16:18:58Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:

Google cloud
We allow our users to create their own ServiceMonitors, meaning we have limited control over their efficiency in doing so. Is this something other people have run into? I wasn't able to find an existing issue.
Needless to say compression would help greatly. 1mb prometheus config compressed with default gzip params to 22kb

I don't think there's an automatic way to fix this right now.
The thing that comes to my mind:

Have multiple Prometheuses running. ServiceMonitors get labels and you specify for which labels each Prometheus is responsible.
Have multiple Prometheuses running and tell those which namespaces to watch for ServiceMonitors and do sharing that way.

Thanks for the suggestions.
This won't work for me however, as it means scaling my prometheus instances based on configuration size. Not to mention unnecessary complexity with regard to alerting and grafana dashboarding.

authors: metalmatze wleese


text:
Makefile: Add clean target

Adding make clean target to main Makefile. This helps a lot debugging
jsonnet vendoring issues.
Up for discussion. Let me know if you feel unsafe adding this.
Relevant git clean manual entry:
-d
Remove untracked directories in addition to untracked files.
If an untracked directory is managed by a different Git repository, it
is not removed by default. Use -f option twice if you really want to
remove such a directory.

-f, --force
If the Git configuration variable clean.requireForce is not set to
false, git clean will refuse to delete files or directories unless given
-f, -n or -i. Git will refuse to delete directories with .git sub
directory or file unless a second -f is given.

-X
Remove only files ignored by Git. This may be useful to rebuild
everything from scratch, but keep manually created files.

Let's move forward with this and improve if we see fit.

authors: brancz mxinden


text:
build system: systemd inclusion in time of building stage1-*.aci

edit: Original issue content under below line.
There is an issue with tracking existence of systemd binaries in build-*/aci-for*flavor/ sometimes in time of rebuilding process, done without previous make clean or rm -rf build-*/. Minor issue, because of mentioned commands.

On actual master we have:
sudo ./build-rkt-1.4.0+git/bin/rkt run --mds-register=false --insecure-options=all --interactive sha512-cdb74a334f97f442a4da5230610ccf46
image: using image from file /home/jell/Data/src/go/gopath_src/github.com/coreos/rkt/build-rkt-1.4.0+git/bin/stage1-kvm.aci
image: using image from the store with hash sha512-cdb74a334f97f442a4da5230610ccf46757688b964ccd3eddc604ab5afb48e85
run: group "rkt" not found, will use default gid when rendering images
networking: loading networks from /etc/rkt/net.d
stage1: warning: error setting journal ACLs, you'll need root to read the pod journal: group "rkt" not found
kvm: network unit created: "interface-eth0.service" in "stage1/rootfs/usr/lib/systemd/system" (iface="eth0", addr="172.16.28.7/24")
[    0.226850] Kernel panic - not syncing: Requested init /usr/lib/systemd/systemd failed (error -2).
[    0.227102] Kernel Offset: disabled
[    0.227132] Rebooting in 1 seconds..
  # KVM session ended normally.

I'm now bisecting which particular commit added this.

Blocking 1.5.0 release.

Latest master works for me:
$  sudo rkt run coreos.com/etcd:v2.0.10
image: using image from local store for image name coreos.com/rkt/stage1-kvm:1.4.0+gitdfee465
image: using image from local store for image name coreos.com/etcd:v2.0.10
networking: loading networks from /etc/rkt/net.d
kvm: network unit created: "interface-eth0.service" in "stage1/rootfs/usr/lib/systemd/system" (iface="eth0", addr="172.16.28.195/24")
[    0.461038] etcd[141]: 2016/04/28 13:27:13 etcd: no data-dir provided, using default data-dir ./default.etcd
[    0.462845] etcd[141]: 2016/04/28 13:27:13 etcd: listening for peers on http://localhost:2380
[    0.463120] etcd[141]: 2016/04/28 13:27:13 etcd: listening for peers on http://localhost:7001
[    0.463328] etcd[141]: 2016/04/28 13:27:13 etcd: listening for client requests on http://localhost:2379
[    0.463522] etcd[141]: 2016/04/28 13:27:13 etcd: listening for client requests on http://localhost:4001
[    0.463719] etcd[141]: 2016/04/28 13:27:13 etcdserver: datadir is valid for the 2.0.1 format
[    0.463970] etcd[141]: 2016/04/28 13:27:13 etcdserver: name = default
[    0.464177] etcd[141]: 2016/04/28 13:27:13 etcdserver: data dir = default.etcd
[    0.464376] etcd[141]: 2016/04/28 13:27:13 etcdserver: member dir = default.etcd/member
[    0.464565] etcd[141]: 2016/04/28 13:27:13 etcdserver: heartbeat = 100ms
[    0.464773] etcd[141]: 2016/04/28 13:27:13 etcdserver: election = 1000ms
[    0.464957] etcd[141]: 2016/04/28 13:27:13 etcdserver: snapshot count = 10000
[    0.465158] etcd[141]: 2016/04/28 13:27:13 etcdserver: advertise client URLs = http://localhost:2379,http://localhost:4001
[    0.465352] etcd[141]: 2016/04/28 13:27:13 etcdserver: initial advertise peer URLs = http://localhost:2380,http://localhost:7001
[    0.465553] etcd[141]: 2016/04/28 13:27:13 etcdserver: initial cluster = default=http://localhost:2380,default=http://localhost:7001
[    0.475686] etcd[141]: 2016/04/28 13:27:13 etcdserver: start member ce2a822cea30bfca in cluster 7e27652122e8b2ae
[    0.476605] etcd[141]: 2016/04/28 13:27:13 raft: ce2a822cea30bfca became follower at term 0
[    0.476883] etcd[141]: 2016/04/28 13:27:13 raft: newRaft ce2a822cea30bfca [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
[    0.477169] etcd[141]: 2016/04/28 13:27:13 raft: ce2a822cea30bfca became follower at term 1
[    0.492526] etcd[141]: 2016/04/28 13:27:13 etcdserver: added local member ce2a822cea30bfca [http://localhost:2380 http://localhost:7001] to cluster 7e27652122e8b2ae
[    1.777971] etcd[141]: 2016/04/28 13:27:15 raft: ce2a822cea30bfca is starting a new election at term 1
[    1.779652] etcd[141]: 2016/04/28 13:27:15 raft: ce2a822cea30bfca became candidate at term 2
[    1.780484] etcd[141]: 2016/04/28 13:27:15 raft: ce2a822cea30bfca received vote from ce2a822cea30bfca at term 2
[    1.781164] etcd[141]: 2016/04/28 13:27:15 raft: ce2a822cea30bfca became leader at term 2
[    1.781717] etcd[141]: 2016/04/28 13:27:15 raft.node: ce2a822cea30bfca elected leader ce2a822cea30bfca at term 2
[    1.797137] etcd[141]: 2016/04/28 13:27:15 etcdserver: published {Name:default ClientURLs:[http://localhost:2379 http://localhost:4001]} to cluster 7e27652122e8b2ae

Are you sure you don't have a corrupt/wrongly generated stage1?

I could repro locally, and turns out blowing away the build environment is necessary between builds.
So not a regression in the KVM stage1, but a serious problem in the build system.

False alarm. Problem lies in buildsystem. Will be described in more details by @mstachowski ;)
hint: rm -rf ./build-*  resolved this problem.

Are we keeping this open to track the build system problems?

It looks like one of stamps(which is responsible for tracking changes inside flavor aci) has been deleted and another(which is responsible for tracking changes in systemd binaries) is not. I didn't diagnose it, because there is simple workarond for this(mentioned by @jellonek rm -rf ./build-*)
@iaguis we should keep this open(because it's build system bug), but IMO it's not P1

Moving to P2 then :)

Ok, so whole issue screams for rename ;)

What is the issue exactly? No /usr/lib/systemd/systemd in the stage1 image? How can I reproduce it?

@krnowak not sure, it turns up intermittently when re-building without blowing away the build directly. Maybe just try a few consecutive builds of the kvm stage1? or one failed build followed by one build that should succeed

I can't remember exact procedure to reproduce this bug, but i'm pretty sure that it was connected with rerunning ./configure and make without make clean.

authors: iaguis jellonek jonboulle krnowak mstachowski

repo: coreos/rkt


text:
stage1: persist runtime parameters

This stores runtime parameters such as insecure options and the MDS
token to disk in the stage1. These are provided during init, but are
necessary during app add. This also simplifies the signature of some of
the stage1 methods.

This is a step towards runc, fixing a few issues I found while preparing the config file.

github.com/coreos/rkt/stage1_fly/run/main.go:243: not enough arguments in call to "github.com/coreos/rkt/stage1/common/types".LoadPod

Semaphore failure is some kind of weird flake.

I'm generally in favor of this but I have two general doubts:

should we have some kind of versioning even for this internal data-structures?
how should we handle runtime data that have been persisted with a different rkt version/schema?

No versioning is needed because this is file is entirely internal to the stage1. Since stage1 versions never change during the lifetime of a pod, we don't need to worry about that.

Probably worth addinng a comment to the struct to that effect (and maybe
adding Internal to the struct's name to be completely explicit?)
On 2 December 2016 at 14:39, Casey Callendrello notifications@github.com
wrote:

No versioning is needed because this is file is entirely internal to the
stage1. Since stage1 versions never change during the lifetime of a pod, we
don't need to worry about that.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/coreos/rkt/pull/3432#issuecomment-264455803, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACewN16n3AzYpf8iRFVYoLC38-FBXdocks5rEB-qgaJpZM4LBQux
.

There is a pretty clear comment, though the struct could have a better name. Currently it's RuntimePod. InternalParams or PodParams? PodInternalRuntimeParams feels a bit awkward, eh.

It has to be capitalised because of go's stupid json encoding rules?
Casey Callendrello notifications@github.com schrieb am Fr., 2. Dez. 2016,
15:03:

There is a pretty clear comment, though the struct could have a better
name. Currently it's RuntimePod. InternalParams or PodParams?
PodInternalRuntimeParams feels a bit awkward, eh.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/coreos/rkt/pull/3432#issuecomment-264460446, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACewN6Mc1lCopS4yAOtIcNHFaQjrMDMZks5rECUfgaJpZM4LBQux
.

It can't be private - the type is referenced externally.

Any further comments?

@lucab renamed the InsecureOptions members like we discussed.

authors: jonboulle lucab squeed


text:
Ingress Events

Feature Request
Environment
What hardware/cloud provider/hypervisor is being used with Tectonic?
AWS and bare metal
Desired Feature
An Ingress resource could have an Events tab (just like a Pod) to show the related Events.
They are visible under Troubleshooting -> Events, but there's no way to drill-down on a specific Ingress (something like kubectl describe ing <ingress name>)
Other Information
Another way to address that feature would be to have a dropdown in the Troubleshooting view that let you drill-down on a specific Ingress

@ledor473 Thanks for reporting this. I think this would be helpful for debugging ingress resources as well.

repo: coreos/tectonic-forum


text:
Object Store Volumes

This needs a design. There was support for this in very early versions of Torus, but there were a number of mistakes in that design. Fortunately, we know the current architecture allows for it. We can probably make a better one, and this issue is to track ideas and plan out what the right design looks like.
After implementation, we can talk about FUSE mounts and WebDAV and S3 and other great interfaces to it, but let's build the right thing and then spawn all the cool features.

Also consider relaxing the consistency rules for pure object storage.  Synchronous replication will snuff out any possibility of running a global object store.

Is there any previous design on this ? Does this mean, we need to use objectset instead of blockset ? Inode would have objectRefs instead of blockrefs ?

authors: barakmich dronadroid mikefedyk

repo: coreos/torus


text:
SQLi: add overlay(...placing...)

Description
SQLi bypass submitted by Shivam Bathla.
Example payload:
id=overlay(password%20placing%20%27%27%20from%201%20for%200)::int
Todo: add function overlay(...placing...).

-> PL1 rule 942480

repo: coreruleset/coreruleset


text:
Add coverage results using additional rules directory

As a security rules tester, I would like to have tests results coverage based on the tests and on the rules I am testing.
Requirements

add an optional --coverage parameter, with a required additional --rules directory parameter that will contain rules.
rules will be read from *.conf files in that directory
a map will contain the rule identifiers as key
for every test that starts with the ID of the rule, we add a counter or similar to the map
after running all tests, we can display a summary of the map based on keys empty/with content.

Output

summary of the tests run plus the coverage percentage based on the map

Rules should have a classification also. For example, if the rule has a skip, then it might be difficult to test by the tool.

repo: coreruleset/go-ftw


text:
Improve external memory interface

While trying to use the API I added in #152, I ran into usability issues.
Originally I had MappedBuffer hold a PhantomData<&mut ExternalMemory> which does make sense in principle, since it is essentially like a view, but it made it difficult to return MappedBuffer from functions.
By taking ownership of ExternalMemory, the drop order is still preserved, while making the API a bit easier to use in practice.
It does mean that you cannot map an ExternalMemory multiple times (before this you could drop the MappedBuffer to unmap), but I do not need that for my use-case, and in the future something like MappedBuffer::unmap() -> ExternalMemory could be added if it is needed.
This is a breaking change because it removes lifetime parameters and changes the function signatures of the mapping functions. Hopefully this is not a problem since a new version of cudarc has not been published since my previous PR.

Looks good to me 👍

authors: ViliamVadocz coreylowman

repo: coreylowman/cudarc


text:
Popover crashes on iPad

Popover crashes on iPad

*** Terminating app due to uncaught exception 'NSGenericException', reason: 'Your application has presented a UIAlertController of style UIAlertControllerStyleActionSheet. The modalPresentationStyle of a UIAlertController with this style is UIModalPresentationPopover. You must provide location information for this popover through the alert controller's popoverPresentationController. You must provide either a sourceView and sourceRect or a barButtonItem.  If this information is not known when you present the alert controller, you may provide it in the UIPopoverPresentationControllerDelegate method -prepareForPopoverPresentation.'

I think your crash is caused by UIAlertController.  this article is useful for you.
https://stackoverflow.com/questions/31577140/uialertcontroller-is-crashed-ipad


text:
Keycloak Test Realm Config for CWA

Hello Guys,
first of all thanks a lot for the great work you are providing to the world!
As i am willing to test the different components with a goal to contribute back to this initiative, i was faced with the challenge to configure the cwa realm with all required clients and roles to make all pieces running. Can you please share an example JSON file configuration of the cwa realm for Keycloak?
Thanks a lot in advance

Hello Team,
any updates please on my question?
Thanks

@elenakalimera I will raise this once more in our project daily tomorrow and ask our dev team to get back to you. Thank you!

@daniel-eder Thanks a lot!

As soon as we have resources to implement a basic configuration of the cwa realm for the Keycloak in JSON format, we will adress this point in devolopment.

I am sorry to say, but at this time the resource allocation does not allow to handle this issue. If a higher priority or critical issue arises out of this issue, please reopen this issue.

repo: corona-warn-app/cwa-verification-iam


text:
Analysis page shows outdated data

Where to find the issue

https://www.coronawarn.app/de/analysis/

Describe the issue
The following figures on https://www.coronawarn.app/de/analysis/ are out of date:

Downloads (last data from 04.11.2021)
Registriere Tests (last data from 02.11.2021)
Teilungsverhalten (last data from 02.11.2021)

Suggested change
Update the data.

@dsarkar
The data feed for:

Registrierte Tests and
Teilungsverhalten

is still blocked.

@Ein-Tim @MikeMcC399 Yes, TSI is looking at it right now.
One can see the issue in https://obs.eu-de.otc.t-systems.com/obs-public-dashboard/json/v1/nested_cwa_public_dashboard_data.json.
Date in this file is shown on the dashboard.
Screenshots from left to right show 2.11., 3.11., 7.11. (marked are the  "Downloadzahlen", which are updated)
From  3.11. on, there are missing numbers (null) in the json file.
Up to date:

Downloads
Empfangene Warnungen
Not up to date:
Registrierte Tests
Teilungsverhalten

@dsarkar
Thanks for the link to https://obs.eu-de.otc.t-systems.com/obs-public-dashboard/json/v1/nested_cwa_public_dashboard_data.json!
You can also see the pattern of missing data in https://obs.eu-de.otc.t-systems.com/obs-public-dashboard/csv/cwa_all_data.zip (use the "Alle Daten exportieren Button on https://www.coronawarn.app/de/analysis/).
The .json file is a bit easier to read but maybe that's just a personal preference.

@Ein-Tim
The data is now appearing up to date again.

I can confirm that this issue has been fixed.
As of now, 09.11.2021, 20:45h, all data on the analysis page is available, up to yesterday (this is intended).
Here is a screenshot from the page:

Thanks to @MikeMcC399 for informing me that this issue has been fixed!

Closing as fixed.

authors: Ein-Tim MikeMcC399 dsarkar

repo: corona-warn-app/cwa-website