VOIP call initiation fails

Hello thank you for the great little firewall. I have been using qubes mirage firewall 0.7.1 for several days and everything seems to be working great. Today I found something. I use voip software over a udp vpn. The vpn has been working fine with no problems. The client is able to log into the voip server without problem as indicated with a green circle (online). However, when I try to initiate a call, it tries for about 10 seconds then fails. On sys-firewall it works normally. I have gone back and forth several times to verify that it works on sys-firewall, but does not work on qmf071. I also tried a different voip client and it is the same. It is strange because since it is over a vpn the firewall should not treat the packets differently. But the problem is real. It is the only problem I have found.

Does anything appear in the logs when this happens?
(you can view the logs using Qubes Manager : select the firewall, then Qube -> Logs -> guest-mirage-firewall.log)

Thank you for your response @talex5
I verified again that in both cases, the vpn connects, and the voip client logs in successfully to the VOIP server. It is still true that with sys-firewall a test call connects successfully, but with mirage-firewall it times out.
Sys-net is <IP_ADDRESS>, and the vpn attached to mirage-firewall is <IP_ADDRESS>.
The related mtu size is 1500 on each. The sys-firewall log is posted after the mirage-firewall log in case it is helpful.
Here are the contents of guest-mirage-firewall.log:
.[32;1mMirageOS booting....[0m
Initialising timer interface
Initialising console ... done.
gnttab_stubs.c: initialised mini-os gntmap
2020-06-29 14:19:48 -00:00: INF [qubes.rexec] waiting for client...
2020-06-29 14:19:48 -00:00: INF [qubes.gui] waiting for client...
2020-06-29 14:19:48 -00:00: INF [qubes.db] connecting to server...
2020-06-29 14:19:48 -00:00: INF [qubes.db] connected
2020-06-29 14:19:49 -00:00: INF [qubes.rexec] client connected, using protocol version 2
2020-06-29 14:19:49 -00:00: INF [unikernel] QubesDB and qrexec agents connected in 0.044 s
2020-06-29 14:19:49 -00:00: INF [dao] Got network configuration from QubesDB:
NetVM IP on uplink network: <IP_ADDRESS>
Our IP on uplink network:   <IP_ADDRESS>
Our IP on client networks:  <IP_ADDRESS>
2020-06-29 14:19:49 -00:00: INF [net-xen frontend] connect 0
2020-06-29 14:19:49 -00:00: INF [net-xen frontend] create: id=0 domid=1
2020-06-29 14:19:49 -00:00: INF [net-xen frontend]  sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false
2020-06-29 14:19:49 -00:00: INF [net-xen frontend] MAC: 00:16:3e:5e:6c:00
2020-06-29 14:19:49 -00:00: INF [ethernet] Connected Ethernet interface 00:16:3e:5e:6c:00
2020-06-29 14:19:49 -00:00: INF [ARP] Sending gratuitous ARP for <IP_ADDRESS> (00:16:3e:5e:6c:00)
2020-06-29 14:19:49 -00:00: INF [ARP] Sending gratuitous ARP for <IP_ADDRESS> (00:16:3e:5e:6c:00)
2020-06-29 14:19:49 -00:00: INF [udp] UDP interface connected on <IP_ADDRESS>
Attempt to open(/dev/urandom)!
Unsupported function getpid called in Mini-OS kernel
Unsupported function getppid called in Mini-OS kernel
2020-06-29 14:19:49 -00:00: INF [dao] Watching backend/vif
2020-06-29 14:19:49 -00:00: INF [memory_pressure] Writing meminfo: free 49756 / 61236 kB (81.25 %)
2020-06-29 14:19:49 -00:00: INF [qubes.gui] client connected (screen size: 1600x900 depth: 24 mem: 5626x)
2020-06-29 14:19:49 -00:00: INF [unikernel] GUI agent connected
2020-06-29 14:19:49 -00:00: INF [qubes.db] got update: "/qubes-keyboard" = "xkb_keymap {\n\txkb_keycodes  { include "evdev+aliases(qwerty)"\t};\n\txkb_types     { include "complete"\t};\n\txkb_compat    { include "complete"\t};\n\txkb_symbols   { include "pc+us+inet(evdev)"\t};\n\txkb_geometry  { include "pc(pc105)"\t};\n};"
2020-06-29 14:19:49 -00:00: WRN [command] << Unknown command "QUBESRPC qubes.SetMonitorLayout dom0"
2020-06-29 14:20:19 -00:00: INF [client_net] add client vif {domid=15;device_id=0} with IP <IP_ADDRESS>
2020-06-29 14:20:19 -00:00: INF [qubes.db] got update: "/mapped-ip/<IP_ADDRESS>/visible-ip" = "<IP_ADDRESS>"
2020-06-29 14:20:19 -00:00: INF [qubes.db] got update: "/mapped-ip/<IP_ADDRESS>/visible-gateway" = "<IP_ADDRESS>"
2020-06-29 14:20:19 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>/0001" = "action=accept specialtarget=dns"
2020-06-29 14:20:19 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>/0003" = "action=drop"
2020-06-29 14:20:19 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>/0002" = "action=accept proto=icmp"
2020-06-29 14:20:19 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>/0000" = "action=accept proto=udp dstports=1194-1194"
2020-06-29 14:20:19 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>/policy" = "drop"
2020-06-29 14:20:19 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>" = ""
2020-06-29 14:20:23 -00:00: INF [client_net] Client 15 (IP: <IP_ADDRESS>) ready
2020-06-29 14:20:23 -00:00: INF [ethernet] Connected Ethernet interface fe:ff:ff:ff:ff:ff
2020-06-29 14:20:23 -00:00: INF [qubes.db] got rm "/qubes-firewall/<IP_ADDRESS>/"
2020-06-29 14:20:23 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>/0001" = "action=accept specialtarget=dns"
2020-06-29 14:20:23 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>/0003" = "action=drop"
2020-06-29 14:20:23 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>/0002" = "action=accept proto=icmp"
2020-06-29 14:20:23 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>/0000" = "action=accept proto=udp dstports=1194-1194"
2020-06-29 14:20:23 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>/policy" = "drop"
2020-06-29 14:20:23 -00:00: INF [qubes.db] got update: "/qubes-firewall/<IP_ADDRESS>" = ""
2020-06-29 14:20:23 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
2020-06-29 14:20:55 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
2020-06-29 14:21:26 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
2020-06-29 14:21:57 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
2020-06-29 14:22:33 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
2020-06-29 14:23:09 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
2020-06-29 14:23:36 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:23:36 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:23:37 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:23:39 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:23:40 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
2020-06-29 14:23:43 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:23:51 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:24:07 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:24:12 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
2020-06-29 14:24:46 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
2020-06-29 14:25:18 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
2020-06-29 14:25:30 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:25:30 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:25:31 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:25:33 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:25:37 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:25:45 -00:00: WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size")
2020-06-29 14:25:50 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
2020-06-29 14:26:23 -00:00: INF [client_eth:dom15:<IP_ADDRESS>] who-has <IP_ADDRESS>? responding with fe:ff:ff:ff:ff:ff
Sys-firewall guest log:
[    0.000000] Linux version 4.19.125-1.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC)) #1 SMP Sat May 30 16:11:30 UTC 2020
[    0.000000] Command line: root=/dev/mapper/dmroot ro nomodeset console=hvc0 rd_NO_PLYMOUTH rd.plymouth.enable=0 plymouth.enable=0 xen_scrub_pages=0 nopat
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fefff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000ff000-0x00000000000fffff] ACPI data
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003e8003ff] usable
[    0.000000] BIOS-e820: [mem 0x00000000fc000000-0x00000000fc007fff] ACPI data
[    0.000000] x86/PAT: PAT support disabled.
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI not present or invalid.
[    0.000000] Hypervisor detected: Xen HVM
[    0.000000] Xen version 4.8.
[    0.258280] tsc: Fast TSC calibration failed
[    0.258285] tsc: Detected 2693.774 MHz processor
[    0.261567] last_pfn = 0x3e800 max_arch_pfn = 0x400000000
[    0.261640] Disabled
[    0.261663] CPU MTRRs all blank - virtualized system.
[    0.261667] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC- UC
[    0.280378] Using GB pages for direct mapping
[    0.280547] RAMDISK: [mem 0x02e2d000-0x03dc2fff]
[    0.280618] ACPI: Early table checksum verification disabled
[    0.280626] ACPI: RSDP 0x00000000000FFFC0 000024 (v02 Xen   )
[    0.280631] ACPI: XSDT 0x00000000FC007F60 000034 (v01 Xen    HVM      00000000 HVML 00000000)
[    0.280637] ACPI: FACP 0x00000000FC007D70 00010C (v05 Xen    HVM      00000000 HVML 00000000)
[    0.280643] ACPI: DSDT 0x00000000FC001050 006C9B (v05 Xen    HVM      00000000 INTL 20160831)
[    0.280647] ACPI: FACS 0x00000000FC001010 000040
[    0.280651] ACPI: FACS 0x00000000FC001010 000040
[    0.280654] ACPI: APIC 0x00000000FC007E80 000034 (v02 Xen    HVM      00000000 HVML 00000000)
[    0.280921] No NUMA configuration found
[    0.280923] Faking a node at [mem 0x0000000000000000-0x000000003e7fffff]
[    0.280933] NODE_DATA(0) allocated [mem 0x3e7d5000-0x3e7fffff]
[    0.281861] Zone ranges:
[    0.281863]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.281864]   DMA32    [mem 0x0000000001000000-0x000000003e7fffff]
[    0.281866]   Normal   empty
[    0.281867]   Device   empty
[    0.281868] Movable zone start for each node
[    0.281872] Early memory node ranges
[    0.281873]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
[    0.281875]   node   0: [mem 0x0000000000100000-0x000000003e7fffff]
[    0.281957] Zeroed struct page in unavailable ranges: 6241 pages
[    0.281958] Initmem setup node 0 [mem 0x0000000000001000-0x000000003e7fffff]
[    0.287511] ACPI: No IOAPIC entries present
[    0.287513] Using ACPI for processor (LAPIC) configuration information
[    0.287532] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[    0.287550] [mem 0x3e800400-0xfbffffff] available for PCI devices
[    0.287556] Booting paravirtualized kernel on Xen PVH
[    0.287559] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>391419 ns
[    0.387095] random: get_random_bytes called from start_kernel+0xc3/0x76a with crng_init=0
[    0.387108] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:1 nr_node_ids:1
[    0.387259] percpu: Embedded 44 pages/cpu s143360 r8192 d28672 u2097152
[    0.387290] Built 1 zonelists, mobility grouping on.  Total pages: 251881
[    0.387291] Policy zone: DMA32
[    0.387297] Kernel command line: root=/dev/mapper/dmroot ro nomodeset console=hvc0 rd_NO_PLYMOUTH rd.plymouth.enable=0 plymouth.enable=0 xen_scrub_pages=0 nopat
[    0.387327] You have booted with nomodeset. This means your GPU drivers are DISABLED
[    0.387329] Any video related functionality will be severely degraded, and you may not even be able to suspend the system properly
[    0.387330] Unless you actually understand what nomodeset does, you should reboot without enabling it
[    0.390140] Memory: 959820K/1023612K available (12300K kernel code, 1486K rwdata, 3892K rodata, 2656K init, 4404K bss, 63792K reserved, 0K cma-reserved)
[    0.390232] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.390242] Kernel/User page tables isolation: enabled
[    0.390289] ftrace: allocating 38262 entries in 150 pages
[    0.402117] rcu: Hierarchical RCU implementation.
[    0.402119] rcu: 	RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=1.
[    0.402120] 	Tasks RCU enabled.
[    0.402121] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[    0.403984] Using NULL legacy PIC
[    0.403986] NR_IRQS: 4352, nr_irqs: 32, preallocated irqs: 0
[    0.404000] xen:events: Using FIFO-based ABI
[    0.404008] xen:events: Xen HVM callback vector for event delivery is enabled
[    0.404018] rcu: 	Offload RCU callbacks from CPUs: (none).
[    0.404058] Console: colour dummy device 80x25
[    0.405108] console [hvc0] enabled
[    0.405140] ACPI: Core revision 20180810
[    0.405191] ACPI: setting ELCR to 0200 (from ffff)
[    0.405224] Failed to register legacy timer interrupt
[    0.405242] APIC: Switch to symmetric I/O mode setup
[    0.405255] x2apic: IRQ remapping doesn't support X2APIC mode
[    0.405411] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x26d44549f58, max_idle_ns:<PHONE_NUMBER>45 ns
[    0.405445] Calibrating delay loop (skipped), value calculated using timer frequency.. 5387.54 BogoMIPS (lpj=2693774)
[    0.405466] pid_max: default: 32768 minimum: 301
[    0.406432] Security Framework initialized
[    0.406432] Yama: becoming mindful.
[    0.406432] AppArmor: AppArmor disabled by boot time parameter
[    0.406432] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.406432] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[    0.406432] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[    0.406432] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
[    0.406432] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
[    0.406432] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
[    0.406432] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.406432] Spectre V2 : Mitigation: Full generic retpoline
[    0.406432] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.406432] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.406432] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.406432] Spectre V2 : User space: Mitigation: STIBP via seccomp and prctl
[    0.406432] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.406432] MDS: Mitigation: Clear CPU buffers
[    0.406432] Freeing SMP alternatives memory: 32K
[    0.406432] clocksource: xen: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns:<PHONE_NUMBER>83 ns
[    0.406432] installing Xen timer for CPU 0
[    0.406432] smpboot: CPU0: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz (family: 0x6, model: 0x45, stepping: 0x1)
[    0.406432] Performance Events: unsupported p6 CPU model 69 no PMU driver, software events only.
[    0.406432] rcu: Hierarchical SRCU implementation.
[    0.406969] random: crng done (trusting CPU's manufacturer)
[    0.407006] NMI watchdog: Perf NMI watchdog permanently disabled
[    0.407063] smp: Bringing up secondary CPUs ...
[    0.407077] smp: Brought up 1 node, 1 CPU
[    0.407087] smpboot: Max logical packages: 1
[    0.407103] smpboot: Total of 1 processors activated (5387.54 BogoMIPS)
[    0.407211] devtmpfs: initialized
[    0.407262] x86/mm: Memory block size: 128MB
[    0.407916] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>275000 ns
[    0.407938] futex hash table entries: 256 (order: 2, 16384 bytes)
[    0.408003] pinctrl core: initialized pinctrl subsystem
[    0.428428] RTC time: 165:165:165, date: 165/165/65
[    0.428620] NET: Registered protocol family 16
[    0.428667] xen:grant_table: Grant tables using version 1 layout
[    0.428707] Grant table initialized
[    0.428773] audit: initializing netlink subsys (disabled)
[    0.428914] audit: type=2000 audit(1593440214.302:1): state=initialized audit_enabled=0 res=1
[    0.428983] cpuidle: using governor menu
[    0.429450] ACPI: bus type PCI registered
[    0.429507] PCI: Fatal: No config space access function found
[    0.431716] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.431734] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.431912] cryptd: max_cpu_qlen set to 1000
[    0.432099] ACPI: Added _OSI(Module Device)
[    0.432110] ACPI: Added _OSI(Processor Device)
[    0.432123] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.432135] ACPI: Added _OSI(Processor Aggregator Device)
[    0.432147] ACPI: Added _OSI(Linux-Dell-Video)
[    0.432160] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.435087] ACPI: 1 ACPI AML tables successfully acquired and loaded
[    0.435323] ACPI: SCI (ACPI GSI 9) not registered
[    0.439030] ACPI: Interpreter enabled
[    0.439043] ACPI: (supports S0)
[    0.439054] ACPI: Using platform specific model for interrupt routing
[    0.439086] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.439222] ACPI: Enabled 1 GPEs in block 00 to 0F
[    0.439244] ACPI Error: No handler or method for GPE 00, disabling event (20180810/evgpe-841)
[    0.439274] ACPI Error: No handler or method for GPE 01, disabling event (20180810/evgpe-841)
[    0.439468] ACPI Error: No handler or method for GPE 03, disabling event (20180810/evgpe-841)
[    0.439501] ACPI Error: No handler or method for GPE 04, disabling event (20180810/evgpe-841)
[    0.439531] ACPI Error: No handler or method for GPE 05, disabling event (20180810/evgpe-841)
[    0.439561] ACPI Error: No handler or method for GPE 06, disabling event (20180810/evgpe-841)
[    0.439590] ACPI Error: No handler or method for GPE 07, disabling event (20180810/evgpe-841)
[    0.444682] xen:balloon: Initialising balloon driver
[    0.465004] vgaarb: loaded
[    0.465122] SCSI subsystem initialized
[    0.468587] ACPI: bus type USB registered
[    0.468617] usbcore: registered new interface driver usbfs
[    0.468637] usbcore: registered new interface driver hub
[    0.468653] usbcore: registered new device driver usb
[    0.468686] pps_core: LinuxPPS API ver. 1 registered
[    0.468699] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>[    0.468721] PTP clock support registered
[    0.468776] EDAC MC: Ver: 3.0.0
[    0.472941] PCI: Using ACPI for IRQ routing
[    0.472961] PCI: System does not support PCI
[    0.473086] NetLabel: Initializing
[    0.473105] NetLabel:  domain hash size = 128
[    0.473118] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.473143] NetLabel:  unlabeled traffic allowed by default
[    0.476732] clocksource: Switched to clocksource xen
[    0.490515] VFS: Disk quotas dquot_6.6.0
[    0.490551] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.490644] pnp: PnP ACPI init
[    0.490691] pnp: PnP ACPI: found 0 devices
[    0.494914] NET: Registered protocol family 2
[    0.495042] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes)
[    0.495068] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.495135] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
[    0.495190] TCP: Hash tables configured (established 8192 bind 8192)
[    0.495219] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.495235] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.495270] NET: Registered protocol family 1
[    0.495285] NET: Registered protocol family 44
[    0.495321] Unpacking initramfs...
[    0.508679] Freeing initrd memory: 15960K
[    0.517201] Initialise system trusted keyrings
[    0.517221] Key type blacklist registered
[    0.517263] workingset: timestamp_bits=36 max_order=18 bucket_order=0
[    0.518190] zbud: loaded
[    0.993970] alg: No test for 842 (842-generic)
[    0.994012] alg: No test for 842 (842-scomp)
[    0.997933] NET: Registered protocol family 38
[    0.997954] Key type asymmetric registered
[    0.997964] Asymmetric key parser 'x509' registered
[    0.997989] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    0.998028] io scheduler noop registered
[    0.998038] io scheduler deadline registered
[    0.998086] io scheduler cfq registered (default)
[    0.998099] io scheduler mq-deadline registered
[    0.998147] atomic64_test: passed for x86-64 platform with CX8 and with SSE
[    0.998650] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    0.999516] Non-volatile memory driver v1.3
[    0.999550] Linux agpgart interface v0.103
[    0.999744] libphy: Fixed MDIO Bus: probed
[    0.999821] usbcore: registered new interface driver usbserial_generic
[    0.999841] usbserial: USB Serial support registered for generic
[    0.999866] i8042: PNP: No PS/2 controller found.
[    0.999895] mousedev: PS/2 mouse device common for all mice
[    0.999959] device-mapper: uevent: version 1.0.3
[    1.000008] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised<EMAIL_ADDRESS>[    1.000069] hidraw: raw HID events driver (C) Jiri Kosina
[    1.000110] usbcore: registered new interface driver usbhid
[    1.000123] usbhid: USB HID core driver
[    1.000175] drop_monitor: Initializing network drop monitor service
[    1.000284] Initializing XFRM netlink socket
[    1.000376] NET: Registered protocol family 10
[    1.001967] Segment Routing with IPv6
[    1.001997] mip6: Mobile IPv6
[    1.002008] NET: Registered protocol family 17
[    1.002137] mce: Using 2 MCE banks
[    1.002165] RAS: Correctable Errors collector initialized.
[    1.002184] AVX2 version of gcm_enc/dec engaged.
[    1.002197] AES CTR mode by8 optimization enabled
[    1.009740] sched_clock: Marking stable<PHONE_NUMBER>, 1408225)->(1374533636, -365094537)
[    1.009855] registered taskstats version 1
[    1.009870] Loading compiled-in X.509 certificates
[    1.009890] zswap: loaded using pool lzo/zbud
[    1.012354] Key type big_key registered
[    1.013596] Key type encrypted registered
[    1.013615] ima: No TPM chip found, activating TPM-bypass!
[    1.013630] ima: Allocated hash algorithm: sha1
[    1.013754] xenbus_probe_frontend: Device with no driver: device/vbd/51712
[    1.013768] xenbus_probe_frontend: Device with no driver: device/vbd/51728
[    1.013782] xenbus_probe_frontend: Device with no driver: device/vbd/51744
[    1.013795] xenbus_probe_frontend: Device with no driver: device/vbd/51760
[    1.013808] xenbus_probe_frontend: Device with no driver: device/vif/0
[    1.013831]   Magic number: 1:252:3141
[    1.013882] hctosys: unable to open rtc device (rtc0)
[    1.015031] Freeing unused decrypted memory: 2040K
[    1.016448] Freeing unused kernel image memory: 2656K
[    1.018490] Write protecting the kernel read-only data: 18432k
[    1.020020] Freeing unused kernel image memory: 2024K
[    1.020213] Freeing unused kernel image memory: 204K
[    1.020242] rodata_test: all tests were successful
[    1.020256] Run /init as init process
Qubes initramfs script here:
[    1.026084] Invalid max_queues (4), will use default max: 1.
[    1.133853] blkfront: xvda: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
[    1.151149]  xvda: xvda1 xvda2 xvda3
[    1.180467] blkfront: xvdb: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
[    1.227304] blkfront: xvdc: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
[    1.252120] blkfront: xvdd: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
Waiting for /dev/xvda* devices...
Qubes: Doing R/W setup for TemplateVM...
[    1.371027]  xvdc: xvdc1 xvdc3
Setting up swapspace version 1, size = 1024 MiB<PHONE_NUMBER> bytes)
no label, UUID=cfdc1921-80c5-4f85-afd8-a12d9e4fc0e4
Qubes: done.
[    1.400109] EXT4-fs (xvda3): mounted filesystem with ordered data mode. Opts: (null)
Waiting for /dev/xvdd device...
mount: /dev/xvdd is write-protected, mounting read-only
[    1.406120] EXT4-fs (xvdd): mounting ext3 file system using the ext4 subsystem
[    1.410229] EXT4-fs (xvdd): mounted filesystem with ordered data mode. Opts: (null)
[    1.437987] EXT4-fs (xvda3): re-mounted. Opts: (null)
switch_root: failed to mount moving /dev to /sysroot/dev: Invalid argument
switch_root: forcing unmount of /dev
switch_root: failed to mount moving /proc to /sysroot/proc: Invalid argument
switch_root: forcing unmount of /proc
switch_root: failed to mount moving /sys to /sysroot/sys: Invalid argument
switch_root: forcing unmount of /sys
switch_root: failed to mount moving /run to /sysroot/run: Invalid argument
switch_root: forcing unmount of /run
[    1.569010] systemd[1]: systemd v241-14.git18dd3fb.fc30 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[    1.569099] systemd[1]: Detected virtualization xen.
[    1.569116] systemd[1]: Detected architecture x86-64.
Welcome to .[0;34mFedora 30 (Thirty).[0m!
[    1.570973] systemd[1]: No hostname configured.
[    1.570992] systemd[1]: Set hostname to .
[    1.655635] systemd[1]: /usr/lib/systemd/system/qubes-meminfo-writer.service:7: PIDFile= references path below legacy directory /var/run/, updating /var/run/meminfo-writer.pid → /run/meminfo-writer.pid; please update the unit file accordingly.
[    1.689335] systemd[1]: /usr/lib/systemd/system/qubes-vpn.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/qubes-vpn/pid → /run/qubes-vpn/pid; please update the unit file accordingly.
[    1.721013] systemd[1]: Listening on udev Control Socket.
[.[0;32m  OK  .[0m] Listening on .[0;1;39mudev Control Socket.[0m.
[    1.721233] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[.[0;32m  OK  .[0m] Started .[0;1;39mForward Password R…uests to Wall Directory Watch.[0m.
[    1.721376] systemd[1]: Reached target Remote File Systems.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mRemote File Systems.[0m.
[.[0;32m  OK  .[0m] Created slice .[0;1;39msystem-getty.slice.[0m.
[.[0;32m  OK  .[0m] Listening on .[0;1;39mJournal Socket.[0m.
Starting .[0;1;39mCreate list of re…odes for the current kernel.[0m...
Starting .[0;1;39mFile System Check on Root Device.[0m...
[.[0;32m  OK  .[0m] Listening on .[0;1;39mJournal Audit Socket.[0m.
[.[0;32m  OK  .[0m] Listening on .[0;1;39mudev Kernel Socket.[0m.
[.[0;32m  OK  .[0m] Listening on .[0;1;39minitctl Compatibility Named Pipe.[0m.
Mounting .[0;1;39mPOSIX Message Queue File System.[0m...
[.[0;32m  OK  .[0m] Listening on .[0;1;39mProcess Core Dump Socket.[0m.
[.[0;32m  OK  .[0m] Created slice .[0;1;39mUser and Session Slice.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mSlices.[0m.
Mounting .[0;1;39mKernel Debug File System.[0m...
Mounting .[0;1;39m/proc/xen.[0m...
[.[0;32m  OK  .[0m] Created slice .[0;1;39msystem-serial\x2dgetty.slice.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mDispatch Password …ts to Console Directory Watch.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mLocal Encrypted Volumes.[0m.
Starting .[0;1;39mudev Coldplug all Devices.[0m...
[.[0;32m  OK  .[0m] Set up automount .[0;1;39mArbitrary…s File System Automount Point.[0m.
Starting .[0;1;39mLoad Kernel Modules.[0m...
[.[0;32m  OK  .[0m] Listening on .[0;1;39mJournal Socket (/dev/log).[0m.
Starting .[0;1;39mJournal Service.[0m...
[.[0;32m  OK  .[0m] Created slice .[0;1;39msystem-systemd\x2dfsck.slice.[0m.
Mounting .[0;1;39mHuge Pages File System.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mCreate list of req… nodes for the current kernel.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mFile System Check on Root Device.[0m.
[.[0;32m  OK  .[0m] Mounted .[0;1;39mPOSIX Message Queue File System.[0m.
[    1.792830] xen:xen_evtchn: Event-channel device installed
[.[0;32m  OK  .[0m] Mounted .[0;1;39mKernel Debug File System.[0m.
[    1.795990] u2mfn: loading out-of-tree module taints kernel.
[.[0;32m  OK  .[0m] Mounted .[0;1;39m/proc/xen.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mLoad Kernel Modules.[0m.
[.[0;32m  OK  .[0m] Mounted .[0;1;39mHuge Pages File System.[0m.
Starting .[0;1;39mQubes DB agent.[0m...
Mounting .[0;1;39mKernel Configuration File System.[0m...
Starting .[0;1;39mApply Kernel Variables.[0m...
[    1.845458] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x26d44549f58, max_idle_ns:<PHONE_NUMBER>45 ns
Starting .[0;1;39mRemount Root and Kernel File Systems.[0m...
[.[0;32m  OK  .[0m] Mounted .[0;1;39mKernel Configuration File System.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mApply Kernel Variables.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mQubes DB agent.[0m.
Starting .[0;1;39mInit Qubes Services settings.[0m...
[    1.911457] EXT4-fs (xvda3): re-mounted. Opts: discard
[.[0;32m  OK  .[0m] Started .[0;1;39mRemount Root and Kernel File Systems.[0m.
Starting .[0;1;39mLoad/Save Random Seed.[0m...
Starting .[0;1;39mCreate Static Device Nodes in /dev.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mLoad/Save Random Seed.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mCreate Static Device Nodes in /dev.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mLocal File Systems (Pre).[0m.
Starting .[0;1;39mudev Kernel Device Manager.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mudev Coldplug all Devices.[0m.
[    2.013924] systemd: 52 output lines suppressed due to ratelimiting
[    2.024990] systemd[1]: systemd v241-14.git18dd3fb.fc30 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[    2.025098] systemd[1]: Detected virtualization xen.
[    2.025115] systemd[1]: Detected architecture x86-64.
[    2.197266] systemd[1]: /usr/lib/systemd/system/qubes-meminfo-writer.service:7: PIDFile= references path below legacy directory /var/run/, updating /var/run/meminfo-writer.pid → /run/meminfo-writer.pid; please update the unit file accordingly.
[    2.223790] systemd[1]: /usr/lib/systemd/system/qubes-vpn.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/qubes-vpn/pid → /run/qubes-vpn/pid; please update the unit file accordingly.
[    2.340200] systemd[1]: Started Init Qubes Services settings.
[.[0;32m  OK  .[0m] Started .[0;1;39mInit Qubes Services settings.[0m.
[    2.340488] systemd[1]: Condition check resulted in Protect Qubes VM execution environment at startup being skipped.
[    2.341112] systemd[1]: Starting Adjust root filesystem size...
Starting .[0;1;39mAdjust root filesystem size.[0m...
[    2.428515] systemd[1]: Started Adjust root filesystem size.
[.[0;32m  OK  .[0m] Started .[0;1;39mAdjust root filesystem size.[0m.
[    2.477572] systemd[1]: Started Journal Service.
[.[0;32m  OK  .[0m] Started .[0;1;39mJournal Service.[0m.
[    2.478485] audit: type=1130 audit(1593440216.351:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Starting .[0;1;39mFlush Journal to Persistent Storage.[0m...
[    2.490169] systemd-journald[203]: Received request to flush runtime journal from PID 1
[.[0;32m  OK  .[0m] Started .[0;1;39mFlush Journal to Persistent Storage.[0m.
[    2.606117] audit: type=1130 audit(1593440216.479:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[.[0;32m  OK  .[0m] Started .[0;1;39mudev Kernel Device Manager.[0m.
[    2.618422] audit: type=1130 audit(1593440216.491:4): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    2.741357] input: PC Speaker as /devices/platform/pcspkr/input/input0
[    2.782089] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer
[    2.782121] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[    2.782136] RAPL PMU: hw unit of domain package 2^-14 Joules
[    2.782151] RAPL PMU: hw unit of domain dram 2^-14 Joules
[    2.782163] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[    2.804788] xen_netfront: Initialising Xen virtual ethernet driver
[    2.842330] intel_rapl: Found RAPL domain package
[    2.842349] intel_rapl: Found RAPL domain core
[    2.842363] intel_rapl: Found RAPL domain uncore
[    2.842378] intel_rapl: Found RAPL domain dram
[    2.842393] intel_rapl: RAPL package 0 domain package locked by BIOS
[    2.842425] intel_rapl: RAPL package 0 domain dram locked by BIOS
[.[0;32m  OK  .[0m] Found device .[0;1;39m/dev/hvc0.[0m.
[.[0;32m  OK  .[0m] Found device .[0;1;39m/dev/xvdb.[0m.
Starting .[0;1;39mInitialize and mount /rw and /home.[0m...
Starting .[0;1;39mFile System Check on /dev/xvdb.[0m...
[.[0;32m  OK  .[0m] Found device .[0;1;39m/dev/xvdc1.[0m.
Activating swap .[0;1;39m/dev/xvdc1.[0m...
[    3.023186] Adding 1048572k swap on /dev/xvdc1.  Priority:-2 extents:1 across:1048572k SSFS
[.[0;32m  OK  .[0m] Activated swap .[0;1;39m/dev/xvdc1.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mSwap.[0m.
Mounting .[0;1;39mTemporary Directory (/tmp).[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mFile System Check on /dev/xvdb.[0m.
[    3.044514] audit: type=1130 audit(1593440216.918:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-xvdb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[.[0;32m  OK  .[0m] Mounted .[0;1;39mTemporary Directory (/tmp).[0m.
[    3.050683] EXT4-fs (xvdb): mounted filesystem with ordered data mode. Opts: discard
[.[0;32m  OK  .[0m] Started .[0;1;39mInitialize and mount /rw and /home.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mLocal File Systems.[0m.
[    3.128465] audit: type=1130 audit(1593440217.001:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-mount-dirs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Starting .[0;1;39mCreate Volatile Files and Directories.[0m...
Starting .[0;1;39mEarly Qubes VM settings.[0m...
Starting .[0;1;39mRestore /run/initramfs on shutdown.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mRestore /run/initramfs on shutdown.[0m.
[    3.145892] audit: type=1130 audit(1593440217.019:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dracut-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    3.159651] audit: type=1325 audit(1593440217.032:8): table=nat family=2 entries=0
[    3.159875] audit: type=1300 audit(1593440217.032:8): arch=c000003e syscall=313 success=yes exit=0 a0=6 a1=5ad189f3e358 a2=0 a3=6 items=0 ppid=206 pid=408 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="modprobe" exe="/usr/bin/kmod" key=(null)
[    3.160066] audit: type=1327 audit(1593440217.032:8): proctitle=2F7362696E2F6D6F6470726F6265002D71002D2D0069707461626C655F6E6174
[.[0;32m  OK  .[0m] Started .[0;1;39mCreate Volatile Files and Directories.[0m.
Starting .[0;1;39mUpdate UTMP about System Boot/Shutdown.[0m...
[.[0;32m  OK  .[0m] Reached target .[0;1;39mSystem Time Synchronized.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mEarly Qubes VM settings.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mUpdate UTMP about System Boot/Shutdown.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mSystem Initialization.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mPeriodically check for updates.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mUpdate system time each 6h.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mPaths.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mdaily update of the root trust anchor for DNSSEC.[0m.
[.[0;32m  OK  .[0m] Listening on .[0;1;39mD-Bus System Message Bus Socket.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mSockets.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mBasic System.[0m.
Starting .[0;1;39mXen driver domain device daemon.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mEntropy Daemon based on the HAVEGE algorithm.[0m.
Starting .[0;1;39mQubes memory information reporter.[0m...
Starting .[0;1;39mLogin Service.[0m...
Starting .[0;1;39mQubes base firewall settings.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mDaily Cleanup of Temporary Directories.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mTimers.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mXen driver domain device daemon.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mQubes memory information reporter.[0m.
Starting .[0;1;39mupdate of the roo…NSSEC validation in unbound.[0m...
Starting .[0;1;39mQubes GUI Agent.[0m...
Starting .[0;1;39mQubes remote exec agent.[0m...
Starting .[0;1;39mD-Bus System Message Bus.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mQubes GUI Agent.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mQubes remote exec agent.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mQubes base firewall settings.[0m.
Starting .[0;1;39mQubes firewall updater.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mD-Bus System Message Bus.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mupdate of the root… DNSSEC validation in unbound.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mLogin Service.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mQubes firewall updater.[0m.
Starting .[0;1;39mQubes network forwarding setup.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mQubes network forwarding setup.[0m.
Starting .[0;1;39mQubes misc post-boot actions.[0m...
[.[0;32m  OK  .[0m] Reached target .[0;1;39mNetwork.[0m.
Starting .[0;1;39mPermit User Sessions.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mPermit User Sessions.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mGetty on tty1.[0m.
[.[0;32m  OK  .[0m] Created slice .[0;1;39mUser Slice of UID 1000.[0m.
Starting .[0;1;39mUser Runtime Directory /run/user/1000.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mSerial Getty on hvc0.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mLogin Prompts.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mUser Runtime Directory /run/user/1000.[0m.
Starting .[0;1;39mUser Manager for UID 1000.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mUser Manager for UID 1000.[0m.
[    5.474588] kauditd_printk_skb: 51 callbacks suppressed
[    5.474589] audit: type=1130 audit(1593440219.347:44): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[.[0;32m  OK  .[0m] Started .[0;1;39mSession c2 of user user.[0m.
[.[0;32m  OK  .[0m] Started .[0;1;39mSession c1 of user user.[0m.
[    5.482988] audit: type=1105 audit(1593440219.355:45): pid=516 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask,pam_lastlog acct="user" exe="/usr/bin/qubes-gui-runuser" hostname=sys-firewall addr=? terminal=/dev/tty7 res=success'
[    5.492212] audit: type=1105 audit(1593440219.365:46): pid=523 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask,pam_lastlog acct="user" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success'
[    5.520847] audit: type=1325 audit(1593440219.394:47): table=nat family=2 entries=18
[    5.522487] audit: type=1300 audit(1593440219.394:47): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=0 a2=40 a3=6292e6549dc0 items=0 ppid=662 pid=665 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-legacy-multi" key=(null)
[    5.522675] audit: type=1327 audit(1593440219.394:47): proctitle=69707461626C6573002D74006E6174002D460050522D514253
[    5.537256] audit: type=1325 audit(1593440219.410:48): table=nat family=2 entries=14
[    5.537648] audit: type=1300 audit(1593440219.410:48): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=0 a2=40 a3=59431fdb48a0 items=0 ppid=673 pid=680 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables-restor" exe="/usr/sbin/xtables-legacy-multi" key=(null)
[    5.538423] audit: type=1327 audit(1593440219.410:48): proctitle=69707461626C65732D726573746F7265002D6E
[.[0;32m  OK  .[0m] Started .[0;1;39mQubes misc post-boot actions.[0m.
[.[0;32m  OK  .[0m] Reached target .[0;1;39mMulti-User System.[0m.
[    5.547612] audit: type=1130 audit(1593440219.420:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-misc-post comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Starting .[0;1;39mUpdate UTMP about System Runlevel Changes.[0m...
[.[0;32m  OK  .[0m] Started .[0;1;39mUpdate UTMP about System Runlevel Changes.[0m.
[    5.567878] fbcon: Taking over console
Fedora 30 (Thirty)
Kernel 4.19.125-1.pvops.qubes.x86_64 on an x86_64 (hvc0)
sys-firewall login: [   28.652088] kauditd_printk_skb: 5 callbacks suppressed
[   28.652089] audit: type=1130 audit(1593440242.525:55): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-sync-time comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   28.903037] audit: type=1131 audit(1593440240.012:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-sync-time comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  189.924302] audit: type=1325 audit(1593440401.033:57): table=raw family=2 entries=0
[  189.924553] audit: type=1300 audit(1593440401.033:57): arch=c000003e syscall=313 success=yes exit=0 a0=0 a1=5f0b5d659358 a2=0 a3=0 items=0 ppid=430 pid=858 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="modprobe" exe="/usr/bin/kmod" key=(null)
[  189.924801] audit: type=1327 audit(1593440401.033:57): proctitle=2F7362696E2F6D6F6470726F6265002D71002D2D0069707461626C655F726177
[  189.926457] audit: type=1325 audit(1593440401.034:58): table=raw family=2 entries=3
[  189.926479] audit: type=1300 audit(1593440401.034:58): arch=c000003e syscall=54 success=yes exit=0 a0=6 a1=0 a2=40 a3=60d02e9c81a0 items=0 ppid=821 pid=857 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables-restor" exe="/usr/sbin/xtables-legacy-multi" key=(null)
[  189.926554] audit: type=1327 audit(1593440401.034:58): proctitle=69707461626C65732D726573746F7265002D2D6E6F666C757368002D2D77616974
[  189.930196] audit: type=1325 audit(1593440401.039:59): table=raw family=10 entries=0
[  189.930372] audit: type=1300 audit(1593440401.039:59): arch=c000003e syscall=313 success=yes exit=0 a0=0 a1=61dcc962e358 a2=0 a3=0 items=0 ppid=430 pid=861 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="modprobe" exe="/usr/bin/kmod" key=(null)
[  189.930624] audit: type=1327 audit(1593440401.039:59): proctitle=2F7362696E2F6D6F6470726F6265002D71002D2D006970367461626C655F726177
[  189.932011] IPv6: ADDRCONF(NETDEV_UP): vif14.0: link is not ready
[  189.932098] audit: type=1325 audit(1593440401.040:60): table=raw family=10 entries=3
[  192.708967] vif vif-14-0 vif14.0: Guest Rx ready
[  192.708998] IPv6: ADDRCONF(NETDEV_CHANGE): vif14.0: link becomes ready
[  329.713841] kauditd_printk_skb: 2 callbacks suppressed
[  329.713843] audit: type=1130 audit(1593440540.823:61): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-update-check comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  329.713902] audit: type=1131 audit(1593440540.823:62): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-update-check comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

I guess WRN [firewall] Failed to write packet to <IP_ADDRESS>: (Failure "length exceeds size") is the problem. Failed to write packet is (probably) logged at https://github.com/mirage/qubes-mirage-firewall/blob/094637b2de8ccaf9743cf956e3c654afbb9bc03e/firewall.ml#L29-L31
length exceeds size comes from https://github.com/mirage/mirage-net-xen/blob/581196b7be3ae14587dccb4605547087e88ca9a0/lib/frontend.ml#L313, which is a sanity check that fails if the user of the network device sends more data than they said they would.
The Ethernet layer writes to the network device here: https://github.com/mirage/ethernet/blob/master/src/ethernet.ml#L79
We don't seem to be specifying a size, in which case it defaults to the MTU, which is the largest permitted size.
mirage-net-xen should probably use Cstruct.sub to restrict the callback to just the area it asked for, rather than letting it write the whole block and then complaining. That might produce a better error. You could try looking at one of the failed packets in wireshark in the sending VM. Maybe the sending VM has a different idea of the MTU, or maybe it's sending valid packets but the firewall is making them larger when doing NAT? Who is familiar with this new size-and-callback system?

Who is familiar with this new size-and-callback system?

I am. Notes in https://mirage.io/blog/announcing-mirage-35-release#TCP-IP.
The short overview is that the target (network device) knows best about alignment restrictions and MTU. This is why the send this buffer API changed. Briefly, a higher layer calls "send" with an argument "size" (how much data to be sent by the upper layer, if known), and a callback function "fill" (buffer -> int) which receives the buffer, fills it, and returns the length which was used.
This way, the ethernet layer gets the size argument from the IP layer, adds 14, and calls the network send. In the callback, it writes source and destination addresses (and protocol type) into the buffer, and calls the IP layer fill function with the buffer shifted to where the IP header should start.
Now, considering this issue report, I suspect there's something wrong. What would help is a pcap of one of the packets sent by the client, and not forwarded to sys-net.

the firewall is making them larger when doing NAT?

No, NAT does not increase packet sizes. But our NAT library now reassembles and fragments packets, so we should ensure that the right MTU is passed (to remind myself, the MTU in our stack is different for each layer since the (static) header is subtracted).

Cstruct.sub to restrict the callback to just the area it asked for, rather than letting it write the whole block and then complaining.

Yes, this is a good idea. To fix this issue, it'd be also worth to have the numbers in the log messages (sorry for them being slightly useless since they do not contain any data).

Dear @jorgejones7711, I was able to locally reproduce the issue with some icmp packets. I developed a fix (in mirage-net-xen, see the reference above if of interest). Could you check that this works for you? I compiled and uploaded a new firewall virtual machine image to http://data.robur.coop/qubes-firewall-0.7.1-mtu-fixed.xen -- if you download this and put it in your dom0 as /var/lib/qubes/vm-kernel/mirage-firewall/vmlinuz and then start (or restart) your mirage-firewall and test your VPN + VoIP setup, and report back here, that'd be great.

It works! Thank you @hannesm and @talex5! Please close this when the next release is out.

Want to say it's still working great, never a problem. Thanks guys. I hope this get mainlined into qubes.


Ensure Datasette Lite is promoted in docs and README

As of 0.62 https://lite.datasette.io is a supported piece of the overall Datasette ecosystem.

I'm going to promote it here too: https://docs.datasette.io/en/latest/getting_started.html


Distribute entity actions over time instead of front-loading them

This gets rid of the regular spikes in CPU usage. When the load tests began, every entity would act immediately. Then 4 minutes later, every entity would act again. Then 4 minutes later, again, and so on. They didn't act at exactly the same time because they don't all start at exactly the same time (and there's a slight variance applied), but the activity was always very front-loaded.
This should have a pretty positive impact on our load test performance, but probably more importantly, this allows us to get much more consistent and accurate profiles.

Shouldn't https://github.com/mattermost/mattermost-load-test/blob/master/loadtest/run.go#L144 be distributing them?

Hm. I hadn't noticed that sleep. Yeah that seems like it should do it... but I know it's not. I need to dig deeper apparently to figure out exactly why...

@crspeller Yeah, so that sleep isn't distributing them because it doesn't account for multiple entity types. For example, if you run a test with 20,000 entities, 2,000 of those entities will be "webhook user" entities. And all of those entities will be created consecutively, in a tight grouping.
Those entities only create posts. So when its their turn to act, we see this (from a short profile during the CPU spike):

(GetAllProfilesInChannel is only called when posts are made.)

@ccbrown Ah right. That makes sense, can we as part of this PR remove the old method of distribution so it's not confusing?

Do you think we can just remove the sleep entirely? I wouldn't want to overload the server before the tests even begin. (I haven't tested it, but it seems like it might be a good idea to leave some sort of pacing in.)

Ya probably better to leave it in.


[ALLUXIO-3278]  Enforce no unshaded protobuf and thrift classes in the outpu

https://alluxio.atlassian.net/browse/ALLUXIO-3278
Cherry-pick to 1.7 branch

Update title to just protobuf?

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20803/
Test PASSed.

Merged build finished. Test PASSed.

@aaudiber title updated

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder-copy/2/
Test FAILed.


Fiberpostprocess

What is fiberpostprocess doing to the vtk files that changes them before running dtitractstat? I cannot find information regarding what a fiberpostprocess command line will do to a vtk with no flags toggled. I'm running into issues when fibers are created and saved with a particular version of slicer - the internal point data is formatted differently than other versions and that could be the source for dtitractstat failure.

It removes wrong (NaN) fibers, filters them with a threshold value and crops them using a maks if provided.


3d tiles unary ops

PR for #4603

@Dylan-Brown this is really close, just these few more comments.

In case you missed this comment, this should fix the failure: https://github.com/AnalyticalGraphicsInc/cesium/pull/4628#discussion_r88118717

The error with the check is:
"Expected 20626.480624709635 to equal epsilon 6.283185307179586, 1e-10."
the test that fails is:
it('evaluates degrees function', function() {         var expression = new Expression('degrees(360)');         expect(expression.evaluate(undefined)).toEqualEpsilon(2*Math.PI, CesiumMath.EPSILON10);     });
I think this means there's something wrong with CesiumMath.toDegrees. Investigating now

Awesome I'm glad to merge this!

Next up just add these functions to https://github.com/AnalyticalGraphicsInc/3d-tiles.

Nice work here, thanks again @Dylan-Brown!


Error 500

error 500 on urls:
/api/v0/server/mods/dlc
/api/v0/server/mods/list
{
"error": "AgentInternalError("Failed to get mods: FactorioDatFileSerde(OutOfRange)")"
}

i'm not sure if game modify mod list file but i think this appeared after i manually set mod list and started server

OutOfRange indicates that there's been a change to the way the Factorio data files are written, tracking issue here https://github.com/circlesabound/factorio-file-parser/issues/1

Ok, so i continued play and tried to move this save to network today. mods import fine, server starts and is working but mod list dies after that
[
alatar02.zip
](url)


renovatebot(deps): update dependency xml-apis:xml-apis to v2

This PR contains the following updates:

Package
Update
Change

xml-apis:xml-apis
major
1.4.01 -> 2.0.2

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

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

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.null seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Bug] Unable to download grafana.com dashboards - x509: certificate signed by unknown authority

Describe the bug
Unable to use GrafanaDashboard with remote HTTPS URLs. This is the error from the logs:
2021-11-02T22:33:37.061Z    ERROR    dashboard-node-exporter-full    failed to request dashboard from grafana.com, falling back to config map; if specified    {"error": "failed to request dashboard url 'https://grafana.com/api/dashboards/
1860/revisions/23/download': Get \"https://grafana.com/api/dashboards/1860/revisions/23/download\": x509: certificate signed by unknown authority"}

The base docker image for the operator is registry.access.redhat.com/ubi8/ubi-micro:8.4, this image doesn't include the trusted CA bundle so all HTTPS requests which should be trusted aren't.
Discussed on slack, but creating this issue to make it more easily discoverable.
Version
v4.0.1
To Reproduce
Create a GrafanaDashboard like so:
apiVersion: integreatly.org/v1alpha1
kind: GrafanaDashboard
metadata:
  name: node-exporter-full
spec:
  datasources:
    - inputName: "DS_PROMETHEUS"
      datasourceName: "Prometheus"
  grafanaCom:
    id: 1860
    revision: 23
  json: ""

Expected behavior
The dashboard from grafana.com should be downloaded and no errors appear in the operator logs.
Suspect component/Location where the bug might be occuring
Docker image doesn't contain trusted CA bundles.
Runtime (please complete the following information):

OS: Ubuntu and CoreOS
Grafana Operator Version: 4.0.1
Environment: Kubernetes v1.21.3-gke.2001
Deployment type: GKE public cluster

Hello,
We're having the same issue

So I've managed to get it to work by running the ubi-minimal image locally and copying the ca-bundle.crt as so:
docker run -itd --rm --name minimal registry.access.redhat.com/ubi8/ubi-minimal:8.4
docker cp minimal:/etc/pki/tls/certs/ca-bundle.crt .

Create a ConfigMap with ca-bundle.crt as a file entry.
Add a volume mount to the operator deployment something like so:
          volumeMounts:
            - mountPath: /etc/pki/tls/certs/ca-bundle.crt
              subPath: ca-bundle.crt
              name: ca-bundle
              readOnly: true
      volumes:
        - name: ca-bundle
          configMap:
            name: ca-bundle

What would the maintainers prefer a PR do? Use ubi-minimal as the base image in the Dockerfile? Or use another stage in the Dockerfile to copy from ubi-minimal?

First of all thanks for reporting the issue and taking such a deep look at it.
I would personally love to be able to keep on using ubi-micro, mainly to minimise the potential attack service  as much as possible and lower startup times. Not that the operator starts up often but any way :)
So copying the certs from ubi-minimal sounds like a good idea to me. Sure it will increase the build time a bit but build only happens once.

Any EAT regarding this?

About now :D
The next question is when/how we will cut a new tag for it. I will work to get this done quickly.


feat: add documentation settings

🗃 Github Issue Or Explanation for this PR. (What is it supposed to do and Why is needed)
#1821
🙈 Screenshots

@pugakn can you resolve the conflict?


getvardual should work to return infeasible rays

This seems to work to get mosek to return infeasible rays. @ulfworsoe, is there anything unsafe here?

It should be straight forward. An infeasible ray is just a solution vector.

One thing, though: We should consider if we want to return values for all solution statuses. If solution is a cert. of primal infeasibility, the primal values are arbitrary garbage (but MOSEK will still return them).
We should consider if we want to return this without warning.

I don't think that's a big issue. It's up to users to check the solution
status, though a warning wouldn't hurt.
On Jun 6, 2016 12:54 PM, "Ulf Worsøe"<EMAIL_ADDRESS>wrote:

One thing, though: We should consider if we want to return values for all
solution statuses. If solution is a cert. of primal infeasibility, the
primal values are arbitrary garbage (but MOSEK will still return them).
We should consider if we want to return this without warning.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JuliaOpt/Mosek.jl/pull/84#issuecomment-223927215, or mute
the thread
https://github.com/notifications/unsubscribe/ABp0M-8xutSsSYov5Xldf0d269HUuRW2ks5qI_xkgaJpZM4It5qi
.

In that case this should be good.


Python ROSE_main.py throws error "ERROR: OPERATION TIME OUT. MAPPING OUTPUT NOT DETECTED"

Hello,
I'm trying to use ROSE_main.py to identify super-enhancers, but I'm encountering the following error.
I have provided the required GFF format file and indexed BAM file as requested.However, when I run this command, the script throws an error.
My command line parameters are:
python ROSE_main.py -g HG38 -i xx.gff -r xx.bam -o xx -s 12500 -t 2500
The error message reads:
ERROR: OPERATION TIME OUT. MAPPING OUTPUT NOT DETECTED
I've tried rerunning the command, but the issue persists. What could be causing this error, and how can I resolve it?
Thanks!

I also face to the problem. Are you deal with it? I think the main problem come from bamToGff.py ,but i can't fix it.

Hi folks, I recommend trying and commenting on the reconstructed version here, which is more actively maintained: https://github.com/stjude/ROSE
What is most likely happening is that ROSE_bamToGFF is failing for some reason, and ROSE_main is waiting for the output from failed jobs, which never arrives.  Reasons this can occur is if your BAM is not sorted or indexed, but we would need more information to troubleshoot.

I also face to the problem. Are you deal with it? I think the main problem comes from bamToGff.py , but I can't fix it.

Hi~.  I haven't resolved this issue yet. The error message indicates that it automatically terminated due to exceeding the time limit. I've attempted to modify the time limit in the source code. You can give it a try; perhaps it might help you. Try increasing the value in the source code where it says if ticker == 1152.

@LLi-jie . Thanks for your reply. I had resolved the problem which has wasted my much time . If you want to deal with the problem , you will check your gff file when you face to the error. The codes is ok.

Hello @LLi-jie, @amateur-boy @abrahamb2
     I have been encountering the same error (Operation time out). As per your suggestion, I did change the ticker value to == 1152 and it still ends with the same error after having run for several days.

I would appreciate any suggestions on how to tackle this issue.
Thank you!!

Duplicating my reply from above:
What is most likely happening is that ROSE_bamToGFF is failing for some reason, and ROSE_main is waiting for the output from failed jobs, which never arrives. Reasons this can occur is if your BAM is not sorted or indexed, but we would need more information to troubleshoot.
You can test this by determining whether the bamToGFF output is generated or by studying the output logs for errors.

Hi@abraham2,
Thank you for your reply.
I don't see a log file yet. The output folder looks like this

I was trying to re-run python ROSE_main.py script again.

Does anything in the screen shots look off?
Thank you!

Hi @abrahamb2, @LLi-jie , @amateur-boy,
I believe I encountered this problem because I did not set the PATH environment variable correctly as outlined here https://github.com/stjude/ROSE#changes-from-source
PATHTO=/path/to/ROSE
PYTHONPATH=$PATHTO/lib
export PYTHONPATH
export PATH=$PATH:$PATHTO/bin
Having addressed that it appears to be working now.
Thanks!


Add pyproject.toml for Custom Node Registry

We are working with dr.lt.data and comfyanon to build a global registry for custom nodes (similar to PyPI). Eventually, the registry will be used as a backend for the UI-manager. All nodes go through a verification process before being published to users.
The main benefits are that authors can

publish nodes by version and users can safely update nodes knowing ahead of time if their workflows will break or not
automate testing against new commits in the comfy repo and existing workflows through our CI/CD dashboard

Action Required:

[ ] Go to the registry. Login and create a publisher id. Add the publisher id into the pyproject.toml file.
[ ] Write a short description.
[ ] Merge the separate Github Actions PR and run the workflow.

If you want to publish the node manually, install the cli and run comfy node publish
Check out our docs if you want to know more about the registry. Otherwise, feel free to message me on discord at haohao_81202 or join our server if you have any questions!

hey @wolfden, wanted to send a small nudge and ask if you had any questions!

@wolfden, wondering if there's any way we can support you on this PR!


Programatically show/hide utility buttons

There should be a way to bounce the cell or slide it programatically. I'd like to do this the first time the table is shown in my app as a hint to the users that they can slide the cells to reveal extra functions.

Why was this issue closed? Is there a method to do it?

It can be done by calling showLeftUtilityButtonsAnimated /  showRightUtilityButtonsAnimated and then hideUtilityButtonsAnimated after a delay.

Thanks 👍


Support encryption at rest

It would be useful if the roles supports encryption at rest: https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/

This looks interesting to me. I had some study on https://learn.hashicorp.com/vault/identity-access-management/vault-agent-k8s but seems vault couldn't act as such KMS provider for Kubernetes.
Beside above initial research I don't have any idea for implementing data encryption for Kubernetes yet. Could you share for more idea or information?

I have used the Hashicorp Vault Agent, but it's not straightforward and adds complexity to the applications. I think it's too much application space for your roles.
I guess that leaves two alternatives:

A simple EncryptionConfiguration on the api-server
KMS provider plugin
There are Vault KMS provider plugins, https://github.com/oracle/kubernetes-vault-kms-plugin, but I have never tried it and have no idea how well it works.

I think it would make more sense to use option 1. It's not the most secure solution, but it's simple and at least secures copies of etcd.

PR is welcome


Refresh source / load external source

Is there a way to load/ import a new source while the designer is already created?
So it starts empty and then an import will render the new source with a new undo step? If so, how?

Hello @MrMoronIV,
you can use the replaceDefinition method. It adds a new definition to the history stack.
designer.replaceDefinition(newDefinition);

That didn't work for some reason, but this did:
designer.api.editor.definitionModifier.replaceDefinition

The Designer.replaceDefinition(definition) method returns the Promise instance. Have you used await?
Internally it uses the replaceDefinition method from the DefinitionModifier class. It should work completelly the same.

designer doesn't have a method replaceDefinition, maybe this not latest version doesn't have that method exposed yet.
(I made some small changes for the Ids on the tasks that you now implemented but didn't update yet.)
But it worked out for now. The definition is replaced successfully :)

replaceDefinition is available from 0.18.4.
Ok, great!


Add sleep commands

Maybe also put HDDs to sleep automatically

hdparm -y or -Y (which one are we using right now?)


Scale ingress controller down to 0 before setting liveness probe

Signed-off-by: Raul Sevilla<EMAIL_ADDRESS>Description
In single node deployments we need to scale the number of ingress controllers to zero before setting liveness probe due to the anti-affinity rules of this deployment  and the deployment rollout policy (maxUnavailable is 50%)
Fixes

Fixes #220

@kedark3 @rsevilla87 I've verified the fix with Raul's personal branch.

@qiliRedHat @rsevilla87 let's :ship: it!


Giving love (updates)

Use OSI standardized license text so it is machine detectable by GitHub/Licensee
Update CI by including Windows (x64/x86) through Travis
Update Codecov example (is codecov enabled for the repo?)
Using current Pkg.jl format for test/docs stages
Added example of using/import statements
Added Weave for docs

Use OSI standardized license text so it is machine detectable by GitHub/Licensee

This now doesn't match what is generated by PkgTemplates and Pkg.generate, however.

We should make the changes to PkgTemplates and Pkg.generate to use the OSI standard texts rather a custom text which is not machine detectable.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f968c69). Click here to learn what that means.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master    #44   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      1
  Lines             ?      5
  Branches          ?      0
=======================================
  Hits              ?      5
  Misses            ?      0
  Partials          ?      0

Impacted Files
Coverage Δ

src/Example.jl
100% <100%> (ø)

Continue to review full report at Codecov.

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

Can you split the PR into smaller pieces? That will help merging the less controversial changes soon. I'd like the question of the standard format to use for LICENSE.md to be settled here before switching other packages (as you propose in your PRs).

I have split the changes into #45, #46, #47, and #48. I can open another one for the using/import example since it is an issue that comes up often in the Slack.


feat: add logging for conditions.ResourcesDeleted

Adds logging to conditions.ResourcesDeleted like with conditions.ResourceDeleted

/lgtm
/approve


Import Bitcoin Private Keys Format

Hi,
I want to import a Bitcoin Private key and de XPRV format is not accepted. Can you tell me which would be the right format?. thank you

Upload a new key created in the same way as your existing one that does not work and I will try it and tell you why it does not work.  Offhand, I cannot tell you.

The private key is from a Copay/bitpay BTC wallet. I've got the seed, the xPrivKey, requestPrivkey, and the Walletprivkey but none of them works on elctroncash

An XprivKey should definitely always work.
Make sure you picked "Standard Wallet" in the first menu, then pick "Use public or private keys" (I know, it's confusing as hell).
Attached you will see what I mean.
It should definitely work.  I think you just got (understandably) confused by the menu options.

@Behzad781 If you try us and this works, please let us know, so we can close this issue.

Thanks a lot. It's working perfect!! you can close this issue


ModuleNotFoundError when using DevOps Pipeline Task AzureFunctionApp@1

Investigative information
When deploying my function from a DevOps pipeline, using the AzureFunctionApp@1 task, the python worker is unable to find the correct modules.
As a default, the above tasks will upload your .zip function code to the Function's storage account, and the following App Setting added: WEBSITE_RUN_FROM_PACKAGE, where the value is the path to the blob item.
I have tried troubleshooting this error as described by this page. The documentation indicates that when having troubles with python modules, the following should be added to the application's settings: SCM_DO_BUILD_DURING_DEPLOYMENT and ENABLE_ORYX_BUILD.
However, when using WEBSITE_RUN_FROM_PACKAGE, which is the default behavior of AzureFunctionApp@1, SCM_DO_BUILD_DURING_DEPLOYMENT is actually ignored. This is documented here.
Repro steps
Using the DevOps Pipeline builder, build your pipeline following the UI. At the end of the process, you should have a pipeline that should look similar to the below. Alternatively, you can use this template  from Microsoft as a guideline.
trigger:
- master

variables:
  # Azure Resource Manager connection created during pipeline creation
  azureSubscription: '{{some_subscription}}'

  # Function app name
  functionAppName: '{{some_function}}'

  # Agent VM image name
  vmImageName: 'ubuntu-latest'

  # Working Directory
  workingDirectory: '$(System.DefaultWorkingDirectory)/functions'

stages:
- stage: Build
  displayName: Build stage

  jobs:
  - job: Build
    displayName: Build
    pool:
      vmImage: $(vmImageName)

    steps:
    - bash: |
        if [ -f extensions.csproj ]
        then
            dotnet build extensions.csproj --runtime ubuntu.16.04-x64 --output ./bin
        fi
      workingDirectory: $(workingDirectory)
      displayName: 'Build extensions'

    - task: UsePythonVersion@0
      displayName: 'Use Python 3.7'
      inputs:
        versionSpec: 3.7 # Functions V2 supports Python 3.6 as of today

    - bash: |
        python -m venv worker_venv
        source worker_venv/bin/activate
        pip install -r requirements.txt
      workingDirectory: $(workingDirectory)
      displayName: 'Install application dependencies'

    - task: ArchiveFiles@2
      displayName: 'Archive files'
      inputs:
        rootFolderOrFile: '$(workingDirectory)'
        includeRootFolder: false
        archiveType: zip
        archiveFile: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
        replaceExistingArchive: true

    - publish: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
      artifact: drop

- stage: Deploy
  displayName: Deploy stage
  dependsOn: Build
  condition: succeeded()

  jobs:
  - deployment: Deploy
    displayName: Deploy
    environment: 'development'
    pool:
      vmImage: $(vmImageName)

    strategy:
      runOnce:
        deploy:

          steps:
          - task: AzureFunctionApp@1
            displayName: 'Azure functions app deploy'
            inputs:
              azureSubscription: '$(azureSubscription)'
              appType: functionAppLinux
              appName: $(functionAppName)
              package: '$(Pipeline.Workspace)/drop/$(Build.BuildId).zip'

Expected behavior
I expect that my function will find and install all the python libraries stored in the requirements.txt file in the project directory during or after deployment.
Actual behavior
Python worker is unable to find any modules that my function needs.
Known workarounds
Deploy your function using the VSCode Function extension.
Contents of the requirements.txt file:
azure-functions==1.2.1
azure-storage-blob==12.3.1
flake8==3.8.1
beautifulsoup4==4.9.1
pytest==5.4.2
sendgrid==6.3.1

Can you try this?:
Instead of pip install -r requirements.txt try recommendation from here pip install --target="./.python_packages/lib/site-packages" -r ./requirements.txt
https://docs.microsoft.com/en-us/azure/azure-functions/functions-how-to-azure-devops?tabs=python

Sorry for the delay in my response. The pip install --target seemed to have worked, thanks.

Can you try this?:
Instead of pip install -r requirements.txt try recommendation from here pip install --target="./.python_packages/lib/site-packages" -r ./requirements.txt
https://docs.microsoft.com/en-us/azure/azure-functions/functions-how-to-azure-devops?tabs=python

Another option - should the above script therefore not be python -m venv .python_packages instead of python -m venv worker_venv then?
Apart from installing the packages, which works absolutely fine, and I can see them installing, I can't seem to see what controls what folder name the Azure Function looks for the virtual environment folder. So is .python_packages hardcoded as the folder that the Azure Function is lookings for?

Can you try this?:
Instead of pip install -r requirements.txt try recommendation from here pip install --target="./.python_packages/lib/site-packages" -r ./requirements.txt
https://docs.microsoft.com/en-us/azure/azure-functions/functions-how-to-azure-devops?tabs=python

Another option - should the above script therefore not be python -m venv .python_packages instead of python -m venv worker_venv then?
Apart from installing the packages, which works absolutely fine, and I can see them installing, I can't seem to see what controls what folder name the Azure Function looks for the virtual environment folder. So is .python_packages hardcoded as the folder that the Azure Function is lookings for?

Issue seems to be resolved. Closing the issue

Issue seems to be resolved. Closing the issue

Another important note is that despite all these changes, I still had this problem. The issue in my case was the App Service Plan was a Y1/Dynamic plan, which doesn't support kudu extensions. I had to upgrade the App Service Plan to a S1/Standard app service. After that, with all the above changes, it worked.

@Fl4v @dirkesquire @priyaananthasankar @stefanushinardi can anyone of you help here:
https://stackoverflow.com/questions/76726316/azure-pipeline-cannot-find-installed-python-libraries
I am stuck at this step and need some help.

@Fl4v @dirkesquire @priyaananthasankar @stefanushinardi can anyone of you help here: https://stackoverflow.com/questions/76726316/azure-pipeline-cannot-find-installed-python-libraries
I am stuck at this step and need some help.

Sure thing! I've got this working successfully and importing pandas.
I had to put quite a lot of extra parameters to pip install to get this to work.
Here is a snippet from my azure_pipelines.yml:
    - task: UsePythonVersion@0
      displayName: 'Use Python 3.9'
      inputs:
        versionSpec: 3.9

    - bash: |
        python -m venv .venv
        source .venv/bin/activate
        pip install --upgrade pip
        pip install --target="./.python_packages/lib/site-packages" -r ./requirements.txt --use-pep517
      workingDirectory: $(workingDirectory)
      displayName: 'Install application dependencies'

requirements.txt:
wheel
azure-functions
openpyxl
pandas

@dirkesquire
I am downloading the artifact in my local machine and then activating the venv. I am unable to import any library which was installed during build stage. Also, I would like to know whether we can really work this way, I mean archive and build the artifact. then Download it and use like a normal project?

You might be able to work this way - but bear in mind that you will need to activate and treat '.python_packages' as your virtual directory NOT '.venv'. Azure Functions seems hardcoded to expect that folder name, and will ignore any custom virtual env we create. So therefore any package we install into '.venv' won't work.

@dirkesquire Thanks for your help. The problem is solved. Issue was the mismatch in vmimage and its version.


多图推理OOM

当进行多图推理时，会爆显存（单卡，32G显存）
提升使用的推理卡数量（2卡，4卡均有尝试），依然爆显存，请问为什么会出现该问题

Hi, we need more information to understand your situation:

which framework were you using? transformers or vllm? was flash_attention used?
how did you run the inference? what resolutions were the images? did you try lowering max_pixels ($$x$$ pixels = $$x/784$$ tokens) as in the README?

model: Qwen2-VL-7B-Instruct
framework: transformers
no flash_attention
how did you run the inference? : use demo code in readme
resolutions: [1436, 717] or higher
did you try lowering max_pixels (x pixels = x/784 tokens) as in the README? no, I'm worried that I'll lose image details this way

@jklj077 where did you see that (x pixels = x/784 tokens)? can we control it during finetuning will llama factory?

@whatever-wlb 请问你有解决这个问题吗


Typescript types are not highlighted

VSCode Version: 1.25.0
OS Version: macOS 10.13.5

Steps to Reproduce:

declare more than 2 variables with a single let/const/var each on a new line
type each variable
observe that starting from 3rd var it's type is not highlighted

putting all vars in one line highlights type of every var

Does this issue occur when all extensions are disabled?: Yes

Does this issue occur in latest insiders build?: Yes

Opened https://github.com/Microsoft/TypeScript-TmLanguage/issues/635 to track this upstream


link: don't allow more openssl/libressl linkage.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you successfully run brew tests with your changes locally?

This extends the approach in #597 to further prevent linkage of formulae that conflict with the system OpenSSL and can cause the issues described in that issue. CC @DomT4 for thoughts.

Addressed feedback.

:+1:


GH-17 Add okaeri serializer and test for it.

Fixes: GH-17
If you consider this to be a needed, we can add unit test for the MultificationNoticeSerializer. As long as awesome helps me with this.
test coverage:

I am wondering if GH actions runs all testes, because I couldn't find any mention in logs, except
> Task :multification-okaeri:test


Add IsLegacy column to OnboardedApp

@kjetilhau How do I access Onboardig App?

@AreWiv
Currently, there's no GUI for managing Onboarded Apps.
You can use the endpoints in Swagger: /api/onboarded-apps. See https://backend-fusion-project-portal-test.radix.equinor.com/swagger/index.html
When calling the GET endpoints, you should be able to see the property IsLegacy.

Verified - IsLegacy property is included when calling GET endpoints in Swagger.
Re-opened to set to Done.

Remember to close the Issue too ;)


Better client-side mod detection

Currently, the only way to have mod menu show a mod as client-side is to add the modmenu:clientsideOnly tag to fabric.mod.json. However, client-side-only mods should already be using "environment": "client" so as to not load on dedicated servers. It seems like a no-brainer to have mod menu simply detect that rather than requiring mods to add a custom tag (you can keep the tag of course, this request is simply additive).

Unfortunately, there's nothing I can do from my end without accessing Fabric Loader internals. For some reason, the environment type is not exposed in Loader's API. I've been meaning to make a Loader PR at some point but never did get around to it.

Thanks so much for this! Love the work you're doing <3

np


[ENH] Consolidate quantile parameterized distributions in few classes

@felixwick, @setoguchi-naoki, @Ram0nB I think we should consolidate the three curent quantile parameterized distribution (QPD) classes into a single one, and move the distribution logic in the quantile regressor in another QPD related class.
This idea is based on two observations:

the quantile-to-distribution logic in current MultipleQuantileRegressor is one way to construct a QPD with arbitrary number of input quantile predictions/values.
the Johnson QPD taking lower, middle, upper quantile predictions/values, output by CyclicBoosting, are spread across three classes which seem a bit redundant. They are also being reworked in #232, related to the cyclic_boosting 1.4.0 release.

I would suggest the following end state:

the logic in MultipleQuantileRegressor moves into a QPD, to which we can later add different interpolation modes and basis functions.

I would suggest replacing the three QPD_X distributions by a single class for Johnson QPD, QPD_Johnson, or similar. This can have a parameter bounding which can be "bounded", "unbounded", "semi", mapping onto the logic in the three current classes.

Do you have any thoughts about this suggestion? It might simplify the interface(s) of the connected regressors as well.

I think that makes sense.
Also, instead of importing the J-QPD implementation from Cyclic Boosting, we might consider to create an independent class directly here in the new QPD module. (I know I suggested differently before, but your description changed my mind.)

Also, instead of importing the J-QPD implementation from Cyclic Boosting, we might consider to create an independent class directly here in the new QPD module. (I know I suggested differently before, but your description changed my mind.)

I think the "optimal state" is either that, or a lightweight interface, as for instance to scipy with Poisson.

Done in https://github.com/sktime/skpro/pull/232


Improve SBOM storage/format

Describe what should be investigated or refactored
Currently the sboms.tar layer contains both JSON documents and generated HTML for an "SBOM viewer" page for each of the images in the Zarf package. The current approach has several downsides:

adds non-trivial overhead to the size of every Zarf package stored in OCI
downloading individual SBOMs (ex. for a particular image) is impossible
the JSON documents are in a Syft-specific JSON format (not SPDX or CycloneDX) and thus not consumable by other tooling, like Trivy
there is no way to tell what specific tooling/version was used to generate the SBOMs

$ oras blob fetch ghcr.io/defenseunicorns/packages/uds/gitlab@sha256:3269b4c33b0d452e6935fc7782dbf64da197b2e6225eb0ba7699831a6cabe877 --output sboms.tar
$ ls -lah sboms.tar
-rw-rw-r-- 1 marshall007 marshall007  77M Oct  3 15:07 sboms.tar

For comparison, compressed tarballs that contain only the JSON documents are <10x the size:
$ ls -lah sboms.tar
-rw-rw-r-- 1 marshall007 marshall007  77M Oct  3 15:07 sboms.tar
-rw-rw-r-- 1 marshall007 marshall007 5.4M Oct  3 15:09 sboms.tar.gz
-rw-rw-r-- 1 marshall007 marshall007 1.7M Oct  3 15:09 sboms.tar.xz

Proposed solution

adopt standard SPDX JSON format
store SBOM documents as OCI artifacts using in-toto attestations
if we wish to keep the HTML "SBOM viewer", consider baking it into the CLI tool (i.e. start a web server that looks at local or remote SPDX JSON documents)

Currently Zarf has prioritized an agnostic format for SBOMs to capture the maximum amount of data that Syft (the tool Zarf uses under the hood) can give Zarf. The Syft JSON files can be downconverted to other formats and conversion is covered in the latter half of this docs section: https://docs.zarf.dev/ref/sboms/#extracting-a-packages-sbom

For the tooling/version used are you looking to see Zarf or Syft?
As of v0.41.0, Syft has .descriptor.name and .descriptor.version in the json, which evaluate to Zarf and Zarf version respectively. Additionally, under the .schema field there's the schema version of the Syft json.

Thanks guys, the Syft JSON makes sense. I'm sold.

For the tooling/version used are you looking to see Zarf or Syft?

I think I'd expect to see Syft, but maybe this is not so important afterall. I'm still looking into it but maybe all that matters is the schema version. I need to see if different syft versions produce different results (outside of schema version changes).

As of v0.41.0, the Syft json has .descriptor.name and .descriptor.version, which evaluate to Zarf and Zarf version respectively.

I see these fields, but Zarf is failing to populate .descriptor.version in the SBOMs I've looked at so far.

Another thing I discovered today is that Zarf is not preserving the original manifest digests in the generated SBOM. Here is the diff between the .source section of an SBOM in the Zarf package vs what I get from scanning with syft directly:

This is good to know thanks for doing this analysis. The media types changing makes sense. I'm not sure why syft writes the mediatypes of layers in that format, even when the manifest in the registry is already using the newer vnd.oci.image.layer.v1.
Losing the architecture, manifest and manifest digests is a bit concerning though. The differences likely have to do with the fact that we're using the equivalent of syft scan oci-dir under the hood. It looks like it's missing a lot of information that should be in the image manifest in Zarf, however it does have the layers, which it must get from the manifest.

@AustinAbro321 something we're wrestling with on the sec-hub implementation is what to do when multiple Zarf packages include the same container images, but with slightly different SBOMs. We're noticing that syft does not really guarantee deterministic output even for the same syft-json schema version.
A good example is comparing these two SBOMs between 10.6.0-uds.0-upstream and 10.6.0-uds.1-upstream (which, by definition, include identical images):
# download artifacts
crane blob ghcr.io/defenseunicorns/packages/uds/sonarqube:10.6.0-uds.0-upstream@sha256:3c3c927030c26b05efa1c0504ed79722f747d46d4b671bd99c870ad5f7d72e42 | tar -Ox docker.io_library_sonarqube_10.6.0-community.json > sonarqube-uds.0.json
crane blob ghcr.io/defenseunicorns/packages/uds/sonarqube:10.6.0-uds.1-upstream@sha256:d0e3ff0e4e26779571a30e0633cede9e6692179e817c573da320fc09d6a0fcea | tar -Ox docker.io_library_sonarqube_10.6.0-community.json > sonarqube-uds.1.json

# structural diff
jd -color -mset -setkeys "artifacts.purl" sonarqube-uds.{0..1}.json

I thought that this was the result of bumping the syft dependency, but it turns out both packages were built using the same Zarf version (v0.36.1).

tl;dr: I think this is all good evidence suggesting we should store SBOMs as attestations and not bundle them with the Zarf package. We should be periodically rescanning packages so we can provide richer SBOMs (more metadata, up-to-date syft-json schema version, new/improved catalogers, etc).


Rails/RedundantAllowNil crashes with interpolations

This seems to be related to #6882. RuboCop stumbles on dynamic validations, in this case with string interpolations
Expected behavior
RuboCop finishes without errors
Actual behavior
1 error occurred:
An error occurred while Rails/RedundantAllowNil cop was inspecting /path/to/my/class.rb:4:2.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
https://github.com/rubocop-hq/rubocop/issues

Mention the following information in the issue report:
0.67.2 (using Parser <IP_ADDRESS>, running on ruby 2.5.1 x86_64-linux-gnu)

Steps to reproduce the problem
This minimal class should reproduce the problem.
class Foo < ActiveRecord::Base
  validates :details, "path_to_dynamic_validation/#{with_interpolation}": true
end

RuboCop version
0.67.2 (using Parser <IP_ADDRESS>, running on ruby 2.5.1 x86_64-linux-gnu)

I reproduced the problem with following code.
class Foo < ActiveRecord::Base
  BAR = "sample"
  validates :name, "#{self::BAR}": true
end

class SampleValidator < ActiveModel::EachValidator
  def validate_each(record, attribute, value)
    if value.size > 3
      record.errors.add(attribute, 'too long')
    end
  end
end

This is stacktrace.
An error occurred while Rails/RedundantAllowNil cop was inspecting /myapp/app/models/foo.rb:3:2.
undefined method `value' for "s(:dsym,\n  s(:begin,\n    s(:const,\n      s(:self), :BAR)))":RuboCop::AST::Node


add utilities for operator startup

Adds some basic utilities to get the "simple" operators off the ground.
@sttts

Usage is here: https://github.com/openshift/service-serving-cert-signer/pull/4/files#r190340485


8ch Images don't load

I think that 8ch has changed the location where images are stored, so all images are now broken, except for cached images and thumbnails.

nevermind, it just got fixed somehow


Travel Time Index

In PeMS the Travel Time Index (TTI) is the ratio of the average travel time for all users across a region to the free-flow travel time. The free-flow travel time is taken to be the time to traverse the link when traveling at 60MPH. For loop-based performance measures, the TTI is simply the free-flow speed divided by the performance measure Q.
We compute this performance measure at the 5-minute level for each loop detector location and the aggregate value across all lanes.
The measures Q and TTI are just ratios of the base performance measures of VMT and VHT.

Closing, fixed by https://github.com/cagov/caldata-mdsa-caltrans-pems/pull/164


Deployment target 11+ and tvOS availability

Xcode 14 minimal deployment target is iOS 11 so I've bumped it in Package.swift file as well.
I see no reason why this component is not available on tvOS. Deployment target has been changed to tvOS 11 and tvOS 14 has been added to @available attributes
Tuned preview a bit to look good in both color schemes and all supported platforms

Thank you for the contribution!


Full recalc using 'Recalculate Rollup is incorrectly calculating as blank/null

When performing a full recalculate using the Recalculate Rollup tab, the rollup calculation is incorrect.  It is actually setting it to blank/null.  Pls see video below:
Video - https://www.loom.com/share/dc7414b9d1f548738f427fb508dda7f0
Report from video - https://wallsforms--wffull.sandbox.lightning.force.com/lightning/r/Report/00OVD0000004GuD2AU/view
CMDT rollup - https://wallsforms--wffull.sandbox.lightning.force.com/lightning/setup/CustomMetadata/page?address=%2Fm0IVD000000426T
Sample Parent record 1 - https://wallsforms--wffull.sandbox.lightning.force.com/lightning/r/GFERP__Item__c/a3o3w000002OIIlAAO/view
Sample Parent record 2 - https://wallsforms--wffull.sandbox.lightning.force.com/lightning/r/GFERP__Item__c/a3o3w000002OHbwAAG/view
Sample Parent record 3 - https://wallsforms--wffull.sandbox.lightning.force.com/lightning/r/GFERP__Item__c/a3o3w000002OAo0AAG/view

@jamessimone You previously had access to this org but I have since refreshed the sandbox. Pls let me know if you'd like me to setup you as a user again and using which email.

@baobao917 was this based off of 1.6.13? I'm happy to take a look if you can create a user again for my Salesforce email.

@jamessimone Actually it was based off of 1.6.12.  I upgraded to 1.6.13 and that release seems to have fixed it.  Thanks!


Reduce node auto gpu expansion

This PR includes two things:

function get_reduction_schedule
auto expansion of the reduce node

This PR adds the auto expansion to the set of available reduce node expansions. The auto expansion is aimed at GPUs. Its goal is to compute an optimal mapping of the reduction input to GPU threads and expands the reduce node according to the computed schedule.
The schedule gets computed via the newly added function get_reduction_schedule, which takes as an input the dimension of the input tensor and a list of the axes to reduce and returns a Python dictionary schedule, which specifies the number of blocks and threads per block to use, etc. At the highest level, the schedule depends on whether contiguous data or non-contiguous data has to be reduced.
The actual expansion called ExpandReduceAuto then calls get_reduction_schedule and creates the actual SDFG expanding the reduce node according to the schedule returned by get_reduction_schedule.
If the auto expansion cannot handle a specific input, it simply falls back to the pure expansion ExpandReducePure.

Exciting! Can't wait to try this


Change approve button on approved

When a user clicks the "Approve feed" button, the database is updated and the button turns into the darker "Approved" non-clickable button.
Pivotal story: 106138734

LGTM - the only thing I think I'd like to see is a less ugly hover color, but everything else is fine.


Change Licensing to UPL

To align with the licensing of Coherence CE we need to change the license from CDDL to the more liberal The Universal Permissive License (UPL).

Done.


Containers can't communicate with each other

RancherOS Version: 1.5.1
Where are you running RancherOS? DigitalOcean
My cloud config specifies two containers. One is based on Node.js and the other is Redis. They should be able to communicate with each other using their container names, but webapp cannot connect to redis using redis as the host name.
#cloud-config

rancher:
  registry_auths:
    "registry.gitlab.com":
      auth: REDACTED
  services:
    webapp:
      image: registry.gitlab.com/REDACTED/webapp/webapp:latest
      restart: always
      ports:
      - "80:3000"
      links:
      - "redis:redis"
    redis:
      image: redis:5.0.3-alpine
      container_name: redis
      ports:
      - "6379:6379"

From docker logs redis:
Error: Redis connection to redis:6379 failed - getaddrinfo ENOTFOUND redis redis:6379

I tried making it more explicit, but it still doesn't work.
#cloud-config

rancher:
  registry_auths:
    "registry.gitlab.com":
      auth: REDACTED
  services:
    webapp:
      image: registry.gitlab.com/REDACTED/webapp/webapp:latest
      restart: always
      ports:
      - "80:3000"
      networks:
      - foobar
    redis:
      image: redis:5.0.3-alpine
      container_name: redis
      ports:
      - "6379:6379"
      networks:
      - foobar
  networks:
    ssltimer:
      driver: bridge
      name: foobar

Also, it seems that networks are completely ignored.
$ docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
258d3ac6c703        bridge              bridge              local
86b246106e49        host                host                local
ca31c796b4ca        none                null                local

It must be an issue with the default Docker engine (18.x.x).
This fixed the config (the one with links, not networks, which I haven't tried with this fix):
  docker:
    engine: docker-17.12.1-ce

I wonder if Rancher OS has some Docker 18 compatibility issues that need to be addressed. It doesn't seem right that, by default, containers cannot communicate with each other by their name. For that reason, although I have a workaround, I'm not going to close this issue.

@steve-taylor Seems cannot reproduce your issue.
[root@rancheros conf]# docker version
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:20:43 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:28:38 2018
  OS/Arch:          linux/amd64
  Experimental:     false

[root@rancheros conf]# ros c export
hostname: rancheros
rancher:
  environment:
    EXTRA_CMDLINE: /init
  network:
    interfaces:
      eth0:
        dhcp: true
      eth1:
        dhcp: true
      lo:
        address: <IP_ADDRESS>/8
  services:
    test1:
      image: nginx
    test2:
      depends_on:
      - test1
      image: nginx
      links:
      - test1

[root@rancheros conf]# docker exec -it test2 bash
root@7317f2a63c88:/# curl test1
<!DOCTYPE html>

<title>Welcome to nginx!</title>

Welcome to nginx!

If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.

For online documentation and support please refer to
nginx.org.

Commercial support is available at
nginx.com.

Thank you for using nginx.

@Jason-ZW thanks for your detailed example. It looks like additional configuration is required when using Docker engine 18 vs 17. I’m not sure if this is called out anywhere. The documentation is quite thin. I’ll give this a try and see if it works in my case.

  network:
    interfaces:
      eth0:
        dhcp: true
      eth1:
        dhcp: true
      lo:
        address: <IP_ADDRESS>/8

This seems to have broken the network. I'm getting network unreachable.

I had the same issue.
The containers started to communicate again after creating a new bridge network and connecting all the containers to it.