Build times                  <= 1ms      <= 2ms      <= 5ms     <= 10ms     <= 20ms     <= 50ms    <= 100ms     > 100ms
0:00         now           0           0           0           0           0           0           0           0
1:00        0:00           1           0           0           0           0           0           0           0
2:00        1:00           2           0           0           0           0           0           0           0
3:00        2:00           0           0           0           0           0           0           0           0
4:00        3:00           0           0           0           0           0           0           0           0
5:00        4:00           0           0           0           0           0           0           0           0
6:00        5:00           0           0           0           0           0           0           0           0
7:00        6:00           0           0           0           0           0           0           0           0
8:00        7:00           0           0           0           0           0           0           0           0
9:00        8:00           0           0           0           0           0           0           0           0
22:05:16         now         437           6           2           2           2           0           0           0
Use counters                   <= 1        <= 2        <= 5       <= 10       <= 20       <= 50      <= 100       > 100
0:00         now           0           0           0           0           0           0           0           0
1:00        0:00           0           0           0           0           0           0           0           1
2:00        1:00           0           0           0           0           0           0           1           1
3:00        2:00           0           0           0           0           0           0           0           0
4:00        3:00           0           0           0           0           0           0           0           0
5:00        4:00           0           0           0           0           0           0           0           0
6:00        5:00           0           0           0           0           0           0           0           0
7:00        6:00           0           0           0           0           0           0           0           0
8:00        7:00           0           0           0           0           0           0           0           0
9:00        8:00           0           0           0           0           0           0           0           0
22:05:16         now          33           6           9          14          20          50          31         285
"
[2023-11-19 09:01:30 VRB] Exit code: 0
[2023-11-19 09:01:30 INF] App Version: 1.1.37
[2023-11-19 09:01:30 INF] Attempting to check modding status from package dump
[2023-11-19 09:01:30 INF] Modded permission not found, downloading APK from the Quest instead . . .
[2023-11-19 09:01:30 DBG] Executing ADB command: adb shell pm path com.projectflashback2121.ProjectFlashback
[2023-11-19 09:01:30 VRB] Standard output: "package:/data/app/~~9KdIw17YW1HCNaPPd5TxDg==/com.projectflashback2121.ProjectFlashback-SelWoX26FTc9zu0EJG7d5A==/base.apk
"
[2023-11-19 09:01:30 VRB] Exit code: 0
[2023-11-19 09:01:30 DBG] Executing ADB command: adb pull "/data/app/~~9KdIw17YW1HCNaPPd5TxDg==/com.projectflashback2121.ProjectFlashback-SelWoX26FTc9zu0EJG7d5A==/base.apk" "C:\Users\Evan\AppData\Local\Temp\QuestPatcher\patching\currentlyInstalled.apk"
[2023-11-19 09:01:38 VRB] Standard output: "/data/app/~~9KdIw17YW1HCNaPPd5TxDg==/com.projectflashback2121.ProjectFlashback-SelWoX26FTc9zu0EJG7d5A==/base.apk: 1 file pulled, 0 skipped. 37.8 MB/s (310610308 bytes in 7.843s)
"
[2023-11-19 09:01:38 VRB] Exit code: 0
[2023-11-19 09:01:38 INF] Checking APK modding status . . .
[2023-11-19 09:01:41 DBG] Executing ADB command: adb shell pm list packages
[2023-11-19 09:01:41 VRB] Standard output: "package:com.oculus.assetdelivery
package:com.oculus.avatareditor
package:com.projectflashback2121.ProjectFlashback
package:com.projecteternalCHRISTMAS21.projecteternalCHRISTMAS21
package:com.oculus.updater
package:com.android.providers.calendar
package:com.oculus.statscollector
package:com.oculus.environment.prod.bubbles
package:com.android.providers.media
package:com.oculus.systemdriver
package:com.oculus.magicislandcastingservice
package:games.b4t.epicrollercoasters.oculus
package:com.oculus.websafety
package:com.oculus.captionservice
package:com.oculus.preshutdowntaskservice
package:com.roblox.client
package:com.android.documentsui
package:com.facebook.horizon
package:com.android.externalstorage
package:com.oculus.browser
package:com.android.htmlviewer
package:com.whatsapp
package:com.android.companiondevicemanager
package:com.oculus.os.vrlockscreen
package:com.oculus.cvp
package:com.meta.curio.toybox
package:com.android.providers.downloads
package:com.android.providers.tv
package:com.meta.curio.ruler
package:com.android.networkstack.inprocess
package:com.melonloader.installer
package:com.oculus.accountscenter
package:in.with.flow.Swords
package:com.oculus.identitymanagement.service
package:com.facebook.wearable.system.location.proxy
package:unity.SUPERHOT_Team.SUPERHOT_VR_Demo
package:com.facebook.wearable.system.location.service
package:com.bilbyinc.bilbyrunners
package:com.meta.AccountsCenter.pwa
package:com.oculus.vrshell.desktop
package:com.beatgames.beatsaber
package:com.android.pacprocessor
package:com.oculus.integrity
package:com.android.connectivity.resources
package:com.oculus.vrshell
package:com.oculus.os.vrusb
package:com.android.modulemetadata
package:com.android.certinstaller
package:com.oculus.environment.prod.adobe
package:com.oculus.henry5k
package:com.ProjectDust.DustProject
package:android
package:com.meta.automation.pauldron.vr
package:com.oculus.metacam
package:com.android.mtp
package:com.android.backupconfirm
package:com.oculus.extrapermissions
package:com.oculus.panelapp.kiosk
package:com.oculus.horizon
package:com.android.provision
package:com.android.statementservice
package:com.oculus.systemutilities
package:com.meta.curio.homepad
package:com.oculus.deviceauthserver
package:com.oculus.firsttimenux
package:com.bigscreenvr.bigscreen
package:com.oculus.os.cm
package:com.oculus.store
package:com.oculus.linefrequencyservice
package:com.oculus.bugreportuploader
package:com.oculus.xrstreamingclient
package:com.android.providers.settings
package:com.oculus.socialplatform
package:com.android.sharedstoragebackup
package:com.oculus.qplservice
package:com.android.webview
package:com.android.inputdevices
package:com.oculus.assistant
package:com.oculus.notification_proxy
package:com.oculus.systemresource
package:com.oculus.companion.server
package:com.oculus.backuptransportservice
package:com.oculus.MiramarSetupRetail
package:com.google.android.apps.youtube.vr.oculus
package:com.android.onetimeinitializer
package:com.oculus.os.rro
package:com.android.server.telecom
package:com.android.keychain
package:com.oculus.systempermissions
package:com.android.wifi.resources
package:com.oculus.vrcast
package:com.android.localtransport
package:com.Axelmatic.Bigscary
package:com.android.packageinstaller
package:com.oculus.systemux
package:com.ProjectBlaze.BlazeTag
package:com.facebook.spatial_persistence_service
package:com.Lemmon.GorillaTagHorror
package:com.android.proxyhandler
package:com.oculus.nux.ota
package:com.oculus.fitnesstracker
package:com.android.managedprovisioning
package:com.meta.federatedcomputing.oculus
package:com.android.soundpicker
package:com.oculus.q4bservice
package:com.oculus.bugreportservice
package:com.oculus.guidebook
package:com.oculus.gatekeeperservice
package:com.Magnopus.MissionISS
package:com.oculus.environment.prod.cyberhome
package:com.oculus.os.chargecontrol
package:com.Alucinar.Chamvr
package:com.oculus.os.clearactivity
package:com.BigBoxVR.PopulationONE
package:com.oculus.ocms
package:com.oculus.yadi
package:com.mgatelabs.mobilevrstationthree
package:com.meta.mr.awe
package:com.oculus.appsafety
package:com.facebook.orca
package:com.oculus.bodyapiservice
package:com.survios.CreedDemo
package:com.facebook.workrooms
package:com.oculus.systemactivities
package:com.cxinventor.file.explorer
package:com.oculus.tv
package:com.oculus.userserver2
package:com.ToastVR.RichiesPlankExperience
package:com.android.storagemanager
package:com.android.bookmarkprovider
package:com.android.settings
package:com.oculus.guardianresources
package:com.oculus.guardian
package:com.oculus.gamingactivity
package:com.android.networkstack.tethering.inprocess
package:com.android.networkstack.permissionconfig
package:com.oculus.explore
package:com.oculus.q4b.mdm
package:com.beatgames.beatsaber.demo
package:com.oculus.presence
package:com.android.vpndialogs
package:com.android.shell
package:com.oculus.helpcenter
package:com.android.providers.blockednumber
package:com.android.providers.userdictionary
package:com.oculus.externalstorage
package:com.android.providers.media.module
package:com.CozProductionsInc.BadTag
package:com.android.hotspot2.osulogin
package:com.oculus.preloader
package:com.android.location.fused
package:com.oculus.maintenanceboot
package:com.android.permissioncontroller
package:com.resolutiongames.baitsantacruz
package:com.facebook.arvr.quillplayer
package:oculus.platform
package:com.LiminalVR.Liminal
package:com.TriangleFactory.HyperDash
package:com.oculus.micservice
package:com.oculus.mobile_mrc_setup
package:com.camouflaj.republiquevr
package:com.oculus.vralertservice
package:com.android.bluetooth
package:com.qualcomm.timeservice
package:com.android.providers.contacts
package:com.IRLStudios.GymClass
package:com.android.captiveportallogin
package:com.oculus.shellenv
package:com.AgainstGravity.RecRoom
package:com.oculus.mrservice
"
[2023-11-19 09:01:41 VRB] Exit code: 0
[2023-11-19 09:02:13 INF] Starting QuestPatcher . . .
[2023-11-19 09:02:13 DBG] Executing ADB command: adb shell pm list packages com.bilbyinc.bilbyrunners
[2023-11-19 09:02:13 VRB] Standard output: "package:com.bilbyinc.bilbyrunners
"
[2023-11-19 09:02:13 VRB] Exit code: 0
[2023-11-19 09:02:13 INF] App is installed
[2023-11-19 09:02:13 INF] Deleting old files. . .
[2023-11-19 09:02:13 DBG] Executing ADB command: adb shell "mkdir -p '/sdcard/QuestPatcher/com.bilbyinc.bilbyrunners/installedMods/' && mkdir -p '/sdcard/Android/data/com.bilbyinc.bilbyrunners/files/mods/' && mkdir -p '/sdcard/Android/data/com.bilbyinc.bilbyrunners/files/libs/'"
[2023-11-19 09:02:13 VRB] Standard output: ""
[2023-11-19 09:02:13 VRB] Exit code: 0
[2023-11-19 09:02:13 DBG] Executing ADB command: adb shell "ls -p "/sdcard/QuestPatcher/com.bilbyinc.bilbyrunners/installedMods/" | grep -v /"
[2023-11-19 09:02:13 VRB] Standard output: ""
[2023-11-19 09:02:13 VRB] Exit code: 1
[2023-11-19 09:02:13 DBG] Executing ADB command: adb shell dumpsys "package com.bilbyinc.bilbyrunners"
[2023-11-19 09:02:13 VRB] Standard output: "Activity Resolver Table:
Non-Data Actions:
android.intent.action.MAIN:
dd329d6 com.bilbyinc.bilbyrunners/com.unity3d.player.UnityPlayerActivity filter b2c3457
Action: "android.intent.action.MAIN"
Category: "android.intent.category.LAUNCHER"
Category: "com.oculus.intent.category.VR"
Domain verification status:
Key Set Manager:
[com.bilbyinc.bilbyrunners]
Signing KeySets: 94
Packages:
Package [com.bilbyinc.bilbyrunners] (a826c3):
userId=10045
pkg=Package{13a1b40 com.bilbyinc.bilbyrunners}
codePath=/data/app/~~w1nPQ6q-p-Og9jVjabkx2A==/com.bilbyinc.bilbyrunners-KwH0shiZfFbAEDTe3vLF8w==
resourcePath=/data/app/~~w1nPQ6q-p-Og9jVjabkx2A==/com.bilbyinc.bilbyrunners-KwH0shiZfFbAEDTe3vLF8w==
legacyNativeLibraryDir=/data/app/~~w1nPQ6q-p-Og9jVjabkx2A==/com.bilbyinc.bilbyrunners-KwH0shiZfFbAEDTe3vLF8w==/lib
extractNativeLibs=true
primaryCpuAbi=arm64-v8a
secondaryCpuAbi=null
cpuAbiOverride=null
versionCode=80 minSdk=24 targetSdk=32
minExtensionVersions=[]
versionName=1.1.15
usesNonSdkApi=false
splits=[base]
apkSigningVersion=2
applicationInfo=PackageImpl{13a1b40 com.bilbyinc.bilbyrunners}
flags=[ HAS_CODE ALLOW_CLEAR_USER_DATA ALLOW_BACKUP ]
privateFlags=[ PRIVATE_FLAG_ACTIVITIES_RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION ALLOW_AUDIO_PLAYBACK_CAPTURE PRIVATE_FLAG_ALLOW_NATIVE_HEAP_POINTER_TAGGING ]
privateFlagsExt=[ PROFILEABLE ]
forceQueryable=false
queriesPackages=[]
dataDir=/data/user/0/com.bilbyinc.bilbyrunners
supportsScreens=[small, medium, large, xlarge, resizeable, anyDensity]
timeStamp=2023-11-11 01:10:47
firstInstallTime=2023-11-11 01:10:58
lastUpdateTime=2023-11-11 01:10:58
signatures=PackageSignatures{d8b4a79 version:2, signatures:[1dad2545], past signatures:[]}
installPermissionsFixed=true
pkgFlags=[ HAS_CODE ALLOW_CLEAR_USER_DATA ALLOW_BACKUP ]
requested permissions:
android.permission.INTERNET
android.permission.RECORD_AUDIO
android.permission.MODIFY_AUDIO_SETTINGS
install permissions:
android.permission.MODIFY_AUDIO_SETTINGS: granted=true
android.permission.INTERNET: granted=true
User 0: ceDataInode=128043 installed=true hidden=false suspended=false distractionFlags=0 stopped=false notLaunched=false enabled=0 instant=false virtual=false
gids=[3003]
runtime permissions:
android.permission.RECORD_AUDIO: granted=true, flags=[ USER_SET|USER_SENSITIVE_WHEN_GRANTED|USER_SENSITIVE_WHEN_DENIED]
Queries:
system apps queryable: false
queries via package name:
queries via intent:
com.facebook.orca:
com.bilbyinc.bilbyrunners
queryable via interaction:
User 0:
queryable via uses-library:
Package Changes:
Sequence number=138
User 0:
seq=0, package=com.android.bluetooth
seq=96, package=com.AnotherAxiom.GorillaTag
seq=97, package=com.ProjectRevial.NoxTagAlpha
seq=118, package=com.enter.tag
seq=125, package=com.oculus.fitnesstracker
seq=135, package=com.oculus.identitymanagement.service
seq=137, package=com.oculus.socialplatform
Dexopt state:
[com.bilbyinc.bilbyrunners]
path: /data/app/~~w1nPQ6q-p-Og9jVjabkx2A==/com.bilbyinc.bilbyrunners-KwH0shiZfFbAEDTe3vLF8w==/base.apk
arm64: [status=speed-profile] [reason=bg-dexopt]
Compiler stats:
[com.bilbyinc.bilbyrunners]
base.apk - 113
Snapshot statistics
Unrecorded-hits: 3629  Cork-level: 0
Summary stats               TotBlds     TotUsed     TotCork     BigBlds    ShortLvd     TotTime     MaxTime
0:43         now           0           0           0           0           0           0           0
1:43        0:43           1         616           0           0           0           0           0
2:43        1:43           2        6555           0           0           0           0           0
3:43        2:43           0           0           0           0           0           0           0
4:43        3:43           0           0           0           0           0           0           0
5:43        4:43           0           0           0           0           0           0           0
6:43        5:43           0           0           0           0           0           0           0
7:43        6:43           0           0           0           0           0           0           0
8:43        7:43           0           0           0           0           0           0           0
9:43        8:43           0           0           0           0           0           0           0
22:05:59         now         449      504872           0           2          49         184          13
Build times                  <= 1ms      <= 2ms      <= 5ms     <= 10ms     <= 20ms     <= 50ms    <= 100ms     > 100ms
0:43         now           0           0           0           0           0           0           0           0
1:43        0:43           1           0           0           0           0           0           0           0
2:43        1:43           2           0           0           0           0           0           0           0
3:43        2:43           0           0           0           0           0           0           0           0
4:43        3:43           0           0           0           0           0           0           0           0
5:43        4:43           0           0           0           0           0           0           0           0
6:43        5:43           0           0           0           0           0           0           0           0
7:43        6:43           0           0           0           0           0           0           0           0
8:43        7:43           0           0           0           0           0           0           0           0
9:43        8:43           0           0           0           0           0           0           0           0
22:05:59         now         437           6           2           2           2           0           0           0
Use counters                   <= 1        <= 2        <= 5       <= 10       <= 20       <= 50      <= 100       > 100
0:43         now           0           0           0           0           0           0           0           0
1:43        0:43           0           0           0           0           0           0           0           1
2:43        1:43           0           0           0           0           0           0           1           1
3:43        2:43           0           0           0           0           0           0           0           0
4:43        3:43           0           0           0           0           0           0           0           0
5:43        4:43           0           0           0           0           0           0           0           0
6:43        5:43           0           0           0           0           0           0           0           0
7:43        6:43           0           0           0           0           0           0           0           0
8:43        7:43           0           0           0           0           0           0           0           0
9:43        8:43           0           0           0           0           0           0           0           0
22:05:59         now          33           6           9          14          20          50          31         285
"
[2023-11-19 09:02:13 VRB] Exit code: 0
[2023-11-19 09:02:13 INF] App Version: 1.1.15
[2023-11-19 09:02:13 INF] Attempting to check modding status from package dump
[2023-11-19 09:02:13 INF] Modded permission not found, downloading APK from the Quest instead . . .
[2023-11-19 09:02:13 DBG] Executing ADB command: adb shell pm path com.bilbyinc.bilbyrunners
[2023-11-19 09:02:14 VRB] Standard output: "package:/data/app/~~w1nPQ6q-p-Og9jVjabkx2A==/com.bilbyinc.bilbyrunners-KwH0shiZfFbAEDTe3vLF8w==/base.apk
"
[2023-11-19 09:02:14 VRB] Exit code: 0
[2023-11-19 09:02:14 DBG] Executing ADB command: adb pull "/data/app/~~w1nPQ6q-p-Og9jVjabkx2A==/com.bilbyinc.bilbyrunners-KwH0shiZfFbAEDTe3vLF8w==/base.apk" "C:\Users\Evan\AppData\Local\Temp\QuestPatcher\patching\currentlyInstalled.apk"
[2023-11-19 09:02:18 VRB] Standard output: "/data/app/~~w1nPQ6q-p-Og9jVjabkx2A==/com.bilbyinc.bilbyrunners-KwH0shiZfFbAEDTe3vLF8w==/base.apk: 1 file pulled, 0 skipped. 36.2 MB/s (163736847 bytes in 4.316s)
"
[2023-11-19 09:02:18 VRB] Exit code: 0
[2023-11-19 09:02:18 INF] Checking APK modding status . . .
[2023-11-19 09:02:18 INF] APK is not modded and is 64 bit
[2023-11-19 09:02:18 INF] Loading mods . . .
[2023-11-19 09:02:18 DBG] Executing ADB command: adb shell "mkdir -p '/sdcard/QuestPatcher/com.bilbyinc.bilbyrunners/installedMods/' && mkdir -p '/sdcard/Android/data/com.bilbyinc.bilbyrunners/files/mods/' && mkdir -p '/sdcard/Android/data/com.bilbyinc.bilbyrunners/files/libs/'"
[2023-11-19 09:02:18 VRB] Standard output: ""
[2023-11-19 09:02:18 VRB] Exit code: 0
[2023-11-19 09:02:18 DBG] Listing files in mods, libs and installedMods . . .
[2023-11-19 09:02:18 DBG] Executing ADB command: adb shell "ls -p "/sdcard/QuestPatcher/com.bilbyinc.bilbyrunners/installedMods/" | grep /"
[2023-11-19 09:02:18 DBG] Executing ADB command: adb shell "ls -p "/sdcard/Android/data/com.bilbyinc.bilbyrunners/files/mods/" | grep -v /"
[2023-11-19 09:02:18 DBG] Executing ADB command: adb shell "ls -p "/sdcard/Android/data/com.bilbyinc.bilbyrunners/files/libs/" | grep -v /"
[2023-11-19 09:02:18 VRB] Standard output: ""
[2023-11-19 09:02:18 VRB] Exit code: 1
[2023-11-19 09:02:18 VRB] Standard output: ""
[2023-11-19 09:02:18 VRB] Exit code: 1
[2023-11-19 09:02:18 VRB] Standard output: ""
[2023-11-19 09:02:18 VRB] Exit code: 1
[2023-11-19 09:02:18 DBG] Starting mod load tasks . . .
[2023-11-19 09:02:18 INF] 0 mods loaded in 330.7052ms!
[2023-11-19 09:02:33 INF] Copying APK to patched location . . .
[2023-11-19 09:02:33 INF] Copying files to patch APK . . .
[2023-11-19 09:02:33 DBG] Downloading libunity index for the first time . . .
[2023-11-19 09:02:37 INF] Checking index for unstripped libunity.so . . .
[2023-11-19 09:02:37 WRN] Unstripped libunity not found for this app
[2023-11-19 09:02:39 INF] Copying libmain.so and libmodloader.so . . .
[2023-11-19 09:02:39 INF] Patching manifest . . .
[2023-11-19 09:02:39 INF] Loading manifest as AXML . . .
[2023-11-19 09:02:39 INF] Adding permission android.permission.READ_EXTERNAL_STORAGE
[2023-11-19 09:02:39 INF] Adding permission android.permission.WRITE_EXTERNAL_STORAGE
[2023-11-19 09:02:39 INF] Adding permission android.permission.MANAGE_EXTERNAL_STORAGE
[2023-11-19 09:02:39 INF] Adding permission questpatcher.modded
[2023-11-19 09:02:39 INF] Adding permission oculus.permission.handtracking
[2023-11-19 09:02:39 INF] Adding permission com.oculus.permission.HAND_TRACKING
[2023-11-19 09:02:39 INF] Adding feature oculus.software.handtracking
[2023-11-19 09:02:39 INF] Adding debuggable flag . . .
[2023-11-19 09:02:39 INF] Adding legacy external storage flag . . .
[2023-11-19 09:02:39 INF] Saving manifest as AXML . . .
[2023-11-19 09:02:39 INF] Adding tag . . .
[2023-11-19 09:02:39 INF] Signing APK (this might take a while) . . .
[2023-11-19 09:02:42 INF] Closing APK archive . . .
[2023-11-19 09:02:46 INF] Uninstalling the default APK . . .
[2023-11-19 09:02:46 DBG] Executing ADB command: adb uninstall com.bilbyinc.bilbyrunners
[2023-11-19 09:02:47 VRB] Standard output: "Success
"
[2023-11-19 09:02:47 VRB] Exit code: 0
[2023-11-19 09:02:47 INF] Installing the modded APK . . .
[2023-11-19 09:02:47 DBG] Executing ADB command: adb install "C:\Users\Evan\AppData\Local\Temp\QuestPatcher\patching\patched.apk"
[2023-11-19 09:03:03 VRB] Standard output: "Performing Streamed Install
"
[2023-11-19 09:03:03 VRB] Error output: "adb: failed to install C:\Users\Evan\AppData\Local\Temp\QuestPatcher\patching\patched.apk: Failure [-124: Failed parse during installPackageLI: Targeting R+ (version 30 and above) requires the resources.arsc of installed APKs to be stored uncompressed and aligned on a 4-byte boundary]
"
[2023-11-19 09:03:03 VRB] Exit code: 1
[2023-11-19 09:03:03 ERR] Patching failed!:  QuestPatcher.Core.AdbException: Failure [DELETE_FAILED_INTERNAL_ERROR]
at QuestPatcher.Core.AndroidDebugBridge.RunCommand(String command, Int32[] allowedExitCodes) in D:\a\QuestPatcher\QuestPatcher\QuestPatcher.Core\AndroidDebugBridge.cs:line 148
at QuestPatcher.Core.AndroidDebugBridge.UninstallApp(String packageId) in D:\a\QuestPatcher\QuestPatcher\QuestPatcher.Core\AndroidDebugBridge.cs:line 186
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in D:\a\QuestPatcher\QuestPatcher\QuestPatcher.Core\Patching\PatchingManager.cs:line 463
at QuestPatcher.ViewModels.PatchingViewModel.StartPatching() in D:\a\QuestPatcher\QuestPatcher\QuestPatcher\ViewModels\PatchingViewModel.cs:line 59
[2023-11-19 09:05:22 DBG] Closing QuestPatcher . . .
[2023-11-19 09:05:22 INF] Saving config file . . .
[2023-11-19 09:05:22 DBG] Goodbye!

You are on a very outdated version of QuestPatcher. Please update to the latest release and get back to me.

i am download it

ill try this ver

tysm it worked :)


LIBUSB::ERROR_ACCESS in libusb_open

Hi Perryn,
I have done everything to make this work, but everytime I initialize Blinky, I always got this error message. Can you help me with this?
arvin@arvin-VirtualBox:~$ irb
r2.2.0 :001 > require 'blinky'
=> true
2.2.0 :002 > l = Blinky.new
LIBUSB::ERROR_ACCESS: LIBUSB::ERROR_ACCESS in libusb_open
from /home/arvin/.rvm/gems/ruby-2.2.0/gems/libusb-0.2.2/lib/libusb/constants.rb:46:in raise_error' 	from /home/arvin/.rvm/gems/ruby-2.2.0/gems/libusb-0.2.2/lib/libusb/device.rb:58:in open'
from /home/arvin/.rvm/gems/ruby-2.2.0/gems/libusb-0.2.2/lib/libusb/compat.rb:175:in open' 	from /home/arvin/.rvm/gems/ruby-2.2.0/gems/blinky-0.0.12/lib/blinky/light_factory.rb:11:in block in detect_lights'
from /home/arvin/.rvm/gems/ruby-2.2.0/gems/blinky-0.0.12/lib/blinky/light_factory.rb:7:in each' 	from /home/arvin/.rvm/gems/ruby-2.2.0/gems/blinky-0.0.12/lib/blinky/light_factory.rb:7:in detect_lights'
from /home/arvin/.rvm/gems/ruby-2.2.0/gems/blinky-0.0.12/lib/blinky.rb:26:in `initialize'

hi
what OS are you using?

It is Ubuntu 14.04 with Virtual Box Windows host


Rewrite to remove FilesPipeline

Deals with:
Can we stop Scrapy hitting each end point twice?
https://github.com/open-contracting/kingfisher-scrape/issues/114
Don't store local files named with a MD5
https://github.com/open-contracting/kingfisher-scrape/issues/45
Send better errors to Error API
https://github.com/open-contracting/kingfisher-scrape/issues/89
Also, this makes not relevant any more:
Do we only ever return one URL in file_urls?
https://github.com/open-contracting/kingfisher-scrape/issues/51

Also, this provides full logging in the database of non-200 HTTP responses.
Under the old way, it's possible a non-200 response would be dropped by scrapy, and not logged in our system.

Can we have some kind of base parse method?

"Can we have some kind of base parse method?" I was thinking that, but I wasn't yet sure which bits might change per scraper and which bits might be the same and thus should be in a library. checked in chat - merging now and will bear in mind for future.


Add system test for 'Table.create' using nested schema

Derived from schema from @tswast.
Toward #3029.

@dhermes Any remaining issues?


Session details not displaying

Session
Awaiting data ...

Live-Timing/-Session is currently broken and will be the next feature implemented.


Server error 500 after deploying site to Google App Engine

Context (Environment)

Google App Engine Deployment
Node v9.0.0
Expected Behavior
After running gcloud app deploy --project=**my_project_id**
and then
gcloud app browse --project=**my_project_id**
I should be able to browse my library site.
Actual Behavior

After running gcloud app deploy --project=**my_project_id**
and then
gcloud app browse --project=**my_project_id**
I'm asked to sign into my library site. After signing in with my account, I'm presented with the following error:

To Reproduce

Follow steps as written on the following guides in the following order:

https://nyt-library-demo.herokuapp.com/get-started/create-a-google-cloud-platform-project
https://nyt-library-demo.herokuapp.com/get-started/create-a-service-account
https://nyt-library-demo.herokuapp.com/get-started/enable-and-configure-api-services
https://nyt-library-demo.herokuapp.com/get-started/create-an-oauth-client
https://nyt-library-demo.herokuapp.com/get-started/deploying-library-google-app-engine

Additional Information
Seems to be the same problem as explained here: https://github.com/nytimes/library/issues/17. Full disclosure, I'm not experienced in doing this sort of thing, and am unsure of even where to start troubleshooting this problem! I have noticed some small discrepancies between the steps I followed (from the sample NYT Library here) and the steps as they are listed here on GitHub: https://github.com/nytimes/library#deploying-the-app (e.g. the NODE_ENV=development # node environment line in step 4 of Development Workflow.
Possible Solution

I've been through all the steps a few times, maybe I just need to start again and stick to the instructions as they appear on GitHub?

Hey @magicustwo, are you able to view the server logs for your app engine deployment? Without a stack trace from the 500 it's hard to say what specific problem you might be running into as that screen is a catch-all for any unexpected error.

Hey @isaacwhite, thanks for the speedy reply! So I've just run gcloud app logs read (thanks Google) and this is what the log says:

2019-06-11 14:46:14 default[20190611t135450]  info: Trying to parse client credentials via GOOGLE_APPLICATION_JSON.
2019-06-11 14:46:14 default[20190611t135450]  warn: failed updating tree
2019-06-11 14:46:14 default[20190611t135450]  { message: 'Unexpected end of JSON input',
2019-06-11 14:46:14 default[20190611t135450]    stack:
2019-06-11 14:46:14 default[20190611t135450]     'SyntaxError: Unexpected end of JSON input\n    at JSON.parse ()\n    at inflight (/srv/server/auth.js:33:25)\n    at /srv/node_modules/promise-inflight/inflight.js:29:24\n    at Promise._execute (/srv/node_modules/bluebird/js/release/debuggability.js:303:9)\n    at Promise._resolveFromExecutor (/srv/node_modules/bluebird/js/release/promise.js:483:18)\n    at new Promise (/srv/node_modules/bluebird/js/release/promise.js:79:10)\n    at _inflight (/srv/node_modules/promise-inflight/inflight.js:28:25)\n    at /srv/node_modules/promise-inflight/inflight.js:22:14\n    at tryCatcher (/srv/node_modules/bluebird/js/release/util.js:16:23)\n    at Promise._settlePromiseFromHandler (/srv/node_modules/bluebird/js/release/promise.js:512:31)\n    at Promise._settlePromise (/srv/node_modules/bluebird/js/release/promise.js:569:18)\n    at Promise._settlePromiseCtx (/srv/node_modules/bluebird/js/release/promise.js:606:10)\n    at Async._drainQueue (/srv/node_modules/bluebird/js/release/async.js:138:12)\n    at Async._drainQueues (/srv/node_modules/bluebird/js/release/async.js:143:10)\n    at Immediate.Async.drainQueues (/srv/node_modules/bluebird/js/release/async.js:17:14)\n    at runCallback (timers.js:705:18)' }

I guess I've messed up adding the JSON to my .env file? I'll go back and check I don't have an apostrophe or bracket where there shouldn't be one.
I'll keep you posted!

Hey @isaacwhite, the source of all my problems was line breaks in the GOOGLE_APPLICATION_JSON part of the .env.
Went through it all to make sure it was just on one line and presto! I have a functional library deployment now!
Such a rookie mistake 😅 , but thanks for the nudge in the right direction!


progressReportNumber - new annotation

Describe the bug
a new column named "projectReportNumber" is present in file annotations
Expected behavior
There should be a column named "progressReportNumber"
Additional context
Recommend changing the column name to reflect "progressReportNumber" in the schema to reduce renaming of columns in the backend of projectLive.

Fixed!


Release candidate

Changes:

Incremented SEECD version number to 4.7.0

Updated Global Variables to store property name and GUID for the new feature

Added new Page GUID to the SEECD XML to enable custom channel names for REM I/O and 3rd party IOVs

Added new page for REM I/O and 3rd party IOVs

Extended action VI “OnLoad” to make IOV channels compatible with new CD version. It sets page GUID to IOV channels (to enable user-defined names) and store channel name (=bus IO name) as IOV Name Channel Property

updated init of the RT driver for REM I/O and 3rd party modules to work with custom IO module names

[x] This contribution adheres to CONTRIBUTING.md.

Pull goal: Add possibility to set custom names for Remote I/O and 3rd party slave IOVs
Why should this Pull Request be merged?
Feature fully implemented and tested by O. Kuba (NI) and tested/reviewed by J. Keprt
What testing has been done?

manual testing:

version bump (update of an existing SDF v <4.7) - successfully added new item properties
successful auto-detection (local chassis, EC master + RemIO slaves, NI slaves, 3rd party slave)
successful deployment of the setup from pt. 2) on cRIO-9033, PXI/Pharlap
performing same tests with changed IOV names

Hi @czokubik. thank you for the pull request! We will start reviewing it shortly.
Can you update the pull request title and description to make it clearer what functionality this pull request enables? I believe this adds support for renaming Remote I/O and 3rd party channel names, however that is not entirely clear from the existing title and description.

Hi @rtzoeller,
I tried to revert project files. I also rolled back CD version 4.7->4.6 and updated OnLoad accordingly. For the "Scan Engine Generic IOV Channel Page.vi" I originally used a page from some other existing CD (don't remember which one ... maybe Pickering) but I for my last release I used the regular page template.
Honestly, I'm not mastering Git much as I'm not a software developer, so please try be patient if I haven't fixed all the file signatures. Please let me know what else needs to be resolved and I'll try to do my best to do so...

@czokubik The changes look good so far. There are still conflicts. Since you started this work we have added some new modules (9224, 9228, 9350) to the custom device. You must resolve these conflicts before we can merge your changes into ni:master.

Merging this pull request into #61. Closing this duplicate pull request.


Add a standards positions URL field to the schema

I think the best way to capture that would be a standards_positions field that can link to issues in https://github.com/mozilla/standards-positions or https://github.com/WebKit/standards-positions.

Originally posted by @foolip in https://github.com/web-platform-dx/feature-set/pull/183#discussion_r1195237433

I think there are discussions to do this in BCD too. Also worth noting that Chrome and Edge don't have a standards positions repo.

Alternatively we ask the maintainers of those repos to use some tagging mechanism so they can maintain the mapping. For chromestatus that's what I'd like to do at least.

I do think we need something here. For both BCD and web-features. It's different to say "this feature is not yet implemented in browser X", than to say "this feature is not implemented in browser X because they oppose this feature of the web platform, learn more at ...".
Currently, neither BCD and web-features tell this story, and I think it would be useful for web developers to know. They might be contemplating using an API, without knowing that it will simply never be implemented in some browser (that is, unless the feature's design changes substantially).

Example: Idle Detection
Baseline badge and BCD table
They both simply say that the feature is not supported:

Standards positions
They tell a different story

Mozilla: https://mozilla.github.io/standards-positions/#idle-detection-api

We are concerned about the user-surveillance, user-manipulation, and abuse of user resources potential of this API ...

WebKit: https://lists.webkit.org/pipermail/webkit-dev/2020-October/031565.html

Unless a significant new development is being made in either one of the issues we've raised, our position will remain to object to the addition of this API unless otherwise stated regardless of whether we continue to say so in public or not.

Deciding if the data should be maintained in those positions repos (by using tags that match our web-features' IDs), or in the present repo or in BCD (by using boolean statuses and links) seems like an implementation choice we can always change later.
@Elchi3 I seem to remember BCD wanting to collect this information. Did this happen?
I'd also value @jgraham's and @annevk's points of view on this issue. Would you be open to adding a field in your positions JSON data that maps back to the web-features maintained here?
For Idle Detection, for Mozilla for example, this could like this:
  {
    "ciuName": null,
    "description": "This document defines a web platform API for observing system-wide user presence signals.",
    "id": "idle-detection-api",
    "mozBugUrl": "",
    "mozPosition": "negative",
    "mozPositionDetail": "We are concerned about the user-surveillance, user-manipulation, and abuse of user resources potential of this API, despite the required 60 second mitigation. Additionally it seems to be an unnecessarily powerful approach for the motivating use-cases, which themselves are not even clear they are worth solving, as pointed out in https://lists.webkit.org/pipermail/webkit-dev/2020-October/031562.html",
    "mozPositionIssue": 453,
    "org": "Proposal",
    "title": "Idle Detection API",
    "url": "https://wicg.github.io/idle-detection/",
    "web-features-tag": "idle-detection"
  },

@captainbrosset wrote:

For both BCD and web-features. It's different to say "this feature is not yet implemented in browser X", than to say "this feature is not implemented in browser X because they oppose this feature of the web platform, learn more at ...".

"because they oppose this feature of the web platform" is poor framing that presumes a disputed outcome—if a feature is only implemented in one engine, it's by definition not part of the web platform.

I think this continues to be a nice-to-have (it'd be helpful for confirming the results of computed statuses, for instance), but I don't think we should put any effort into a schema until there's a consumer that's actually going to attempt to tell a story to web developers with such data.
Last I heard, there was not enthusiasm on MDN or caniuse's part to make this information prominent. Until we hear from someone saying that they're going to do something with this data, I'd prefer to see what Philip suggested in https://github.com/web-platform-dx/web-features/issues/186#issuecomment-1933255705.

@hober wrote:

"because they oppose this feature of the web platform" is poor framing that presumes a disputed outcome—if a feature is only implemented in one engine, it's by definition not part of the web platform.

Thanks for the feedback, I agree about removing the "web platform" part of it and I've updated my comment to say "this feature is not implemented in browser X, see browser X's position about it at ..." instead.

@ddbeck I agree with not doing anything until consumers of the data share a need for this with us. And I also prefer Philip's suggestion, which is why I'd like to hear what folks who maintain browser position repos think about adding web-features IDs to their data.

FWIW, I think we'd probably accept patches, but I'm not sure about actively investing in the accuracy of that data.

I think there are use cases for this which don't depend on user-facing consumers.
For example for Interop if a proposal corresponds to a web-feature (which hopefully is the most common case, particularly if we support features being defined before implementations ship) we could automatically pull in the s-p data from different vendors so it wouldn't require additional manual effort to find vendor's existing positions on the feature.

@annevk you mean you'd accept patches for the https://github.com/WebKit/standards-positions repo? If we follow Philips proposal, once we tag those positions with the Web Feature identifiers, you'd only need to keep the repo itself up to date.

I just proposed this PR for Mozilla: https://github.com/mozilla/standards-positions/pull/1034
I plan on opening a similar one for WebKit.

And here is the PR for WebKit: https://github.com/WebKit/standards-positions/pull/357.
@foolip what about chromestatus.com? Is there ongoing work to also map features there?

@foolip what about chromestatus.com? Is there ongoing work to also map features there?

It's being worked on right now, but there is indeed a plan! Each chromestatus entry would get a web-features ID, replacing the categories we currently have.
cc @past

For information, and to revive this thread, the WebKit and Mozilla PRs didn't go very far. Both repos want to use labels on issues to track the info about a position. Only repo maintainers would be able to add new labels (e.g. web-features:grid) on position issues.
I didn't get the impression that either wanted to commit to doing this, and the discussions died down.
Should we add a standard-position field to our features? @ddbeck ? @atopal ?
I know we're trying to only add the fields that are strictly necessary to generate the data for a feature, and leave it to other data sources to points to us via our unique IDs. But there are also cases, like these ones, where it's either not practical to do so, or perceived as too much work.
Another example of it seeming like too much work is https://github.com/web-platform-tests/interop/issues/693.

Thanks for reviving Patrick! For standards positions, I'd try again to see if there is a way, but ultimately it might still be a good idea to handle that in Web Features, since we may take that into account for future availability statuses, they are very limited in number and will very rarely change, so  the maintenance burden should be low.
For developer signals from Interop items, I'm not so sure about that, there are so many possible sources of signals for developer needs, it seems like this would set a bad precedent. Also, because those won't impact the availability status. I think your suggestion of tagging or in some other way marking them with web-feature-ids in the Interop repo makes much more sense.

There is undoubtedly value in mapping standard positions to Web Features, and I think this group is well positioned to do so as we review features and their implementations. I'm not sure it needs to be part of the main Web Features dataset or package - iow, it could be maintained by us out of band, either as a separate file (there aren't so many to track in the first place), or a in a separate repo altogether.

I'm neutral on adding standards positions URLs to web-features. An out-of-band experiment would be a good step, to figure out what proportion of (non-Baseline) features would even have a standards position associated with it—if mapping proves especially challenging, it'd be nice to know that before we merge new data and code into web-features.
That said, if they were added to web-features, then I'd like their introduction to include:

Linting for validity. I didn't really like the usage stats URLs because the only checking we did was against a regex. It was still rather easy to introduce incorrect URLs. Ideally, we'd get an inventory (or inventories) of vendors' standards positions URLs (or make one ourselves, like I've done for MDN content).

Dropping URLs as soon as they become historic. Again, ideally, I'd like something like this to happen: if a vendor ships a feature, we drop that vendor's standards position URL as soon as that information propagates to us from BCD.

A use case. Even if it's initially only the web-features explorer, I'd like there to be some consumer for the data. I think my earlier comment didn't actually bear fruit. I can recall one time I was curious enough to go looking for a standards position while authoring or reviewing a feature. Standards positions are not obviously useful for authoring, so I'd like there to be some realistic expectation that the data's going to be used somewhere.

A use case. Even if it's initially only the web-features explorer, I'd like there to be some consumer for the data. I think my earlier comment didn't actually bear fruit. I can recall one time I was curious enough to go looking for a standards position while authoring or reviewing a feature. Standards positions are not obviously useful for authoring, so I'd like there to be some realistic expectation that the data's going to be used somewhere.

I can commit to adding this to the explorer. In fact, there's already a link to search for standard positions on feature pages. For example: https://web-platform-dx.github.io/web-features-explorer/features/file-system-access/ shows that Firefox and Safari do not support the API. Clicking on the Search for standards position links takes you to Mozilla and WebKit's standards position repositories, and you then have to go and find the position issue yourself.
Ideally, if they exist, those links would take you to https://mozilla.github.io/standards-positions/#native-file-system and https://webkit.org/standards-positions/#position-28 instead.

Maintaining this out of band would, I think, be the right thing to do here. In fact, I can see how a JSON mapping of web-features ID to standards-position URLs could be useful to others too. I know BCD has wanted something like this too.
Are folks here ok if I create a new repo under our GitHub organization to get this started? Does this seem like the right first step?

Are folks here ok if I create a new repo under our GitHub organization to get this started?

That seems a good idea. It's also a good way to eat our own dog food ;)

Dropping URLs as soon as they become historic.

If we do it out of band, I would actually prefer that we preserve the information: these URLs should be relatively stable, and the information can help with historical analyses (be it only to measure average durations between events in the lifecycle of a feature).

FWIW I think the missing piece on getting vendors interested here is more likely about not seeing how the workflow will work, or understanding the value proposition vs technical concerns about where the data is stored. Or at the least I think the technical concerns can be resolved if the use cases are strong enough.
Trying to store these mappings outside of standards positions is a workaround that doesn't seem sustainable in the longer term, and only seems worthwhile for prototyping the system to understand the challenges.
So, what do I think the long term should look like? Well:

When someone starts working on a spec and it's reached the level of stability that they want to get formal input from others, or start prototyping an implementation, they define a web feature.
Initially this feature should be considered mutable. That's pretty different from the kinds of features we've defined so far which are mostly well-established and might be expected to grow, but not change.
The feature name is used in all the following situations:

Submitting a standards position request
Publishing an Intent (e.g. to implement or to ship)

It is the responsibility of the person requesting the s-p or writing the Intent to ensure that the feature is defined, and matches their plans.
In the case where the plans don't match the feature that is clearly documented and we have some clear escalation process. For example if browser A proposes a large feature X and browser B decides that they are only interested in some subset X', we need to resolve that e.g. by splitting the feature into separate X' + X'', which can get different statuses.
Other vendor published data (e.g. use counters, release notes) uses the feature name wherever it makes sense.

The goal here is that it's easy to understand the status of in-progress or partially implemented platform features without needing to manually read a lot of different data sources, and piece together which of them are relating to the same functionality. That's definitely a pain point, and whilst sometimes one can use spec names to solve it, often that doesn't work.
I think in terms of process, getting a commitment that people will do the work to define a feature and provide the feature name when communicating about the feature is more important than getting people to agree up-front to a standardised way of storing that information if it happens to be provided. Even if people provide the feature name as plain text (e.g. in an intent email or s-p request) it should be possible to parse that out much of the time, assuming there's a template that they're using. Once that's working and people see the value there's a lot more motivation to solve the "how do I store this in a more structured way" question (which for GH labels could be something like an action that can parse out the feature from the issue, check it's a real feature, and then automatically create a label if it is).

When someone starts working on a spec and it's reached the level of stability that they want to get formal input from others, or start prototyping an implementation, they define a web feature.

I like the idea of reserving feature IDs early in time. I remember this group talking about this a few times already, and I recall general agreement.
I'm less excited about the they define a web feature part. Much as I'd love for people to do it, I don't really see it happening because I fear it'll be perceived as one more manual step in an already long and complex process.
How can we make this easy/transparent/fast enough for it to happen every time? I don't know ... Happy to hear proposals.
After that, I agree that it's easy enough to change the template used in intent emails, or in new s-p issues.

As for a short term fix, while waiting for web-features to become a fully integrated part of the platform evolution process, how's this:

Create a new repo in this GH org
Add a big JSON file to it which maps web-features IDs to WebKit and Mozilla standards positions issues
Optionally add a CI script that periodically gets the actual position (positive/support, neutral, negative/oppose, defer, ...) for each known standards position and updates the JSON with it.
Update the explorer to use and present this data somewhere in the UI.

More context on the way WebKit and (soon) Mozilla manage their standards positions:

They both have a GitHub repo where issues constitute the source of truth for positions.
Mozilla is in a bit of a mixed situation right now, with some positions as issues, others on a website, others in a JSON file. But they're moving to using issues only, like WebKit.
New issues are filed to request them to state a position about a feature.
Issue may have a position: ... label or not. Issues that do have this label have received a position. Others haven't (yet).
Positions may be positive, neutral, negative, or sometimes defer.

Here is how I envision our JSON mapping file to be:
[
  // Positive position
  {
    webFeatureID: "nesting",
    positions: {
      mozilla: {
        link: "https://github.com/mozilla/standards-positions/issues/695",
        position: "positive"
      }
      webkit: {
        link: "https://github.com/WebKit/standards-positions/issues/69",
        position: "support"
      }
    }
  },
  // No position
  {
    webFeatureID: "eyedropper",
    positions: {
      mozilla: {
        link: "https://github.com/mozilla/standards-positions/issues/557"
      }
      webkit: {
        link: "https://github.com/WebKit/standards-positions/issues/29"
      }
    }
  },
  // Negative position
  {
    webFeatureID: "file-system-access",
    positions: {
      mozilla: {
        link: "https://github.com/mozilla/standards-positions/issues/154"
      }
      webkit: {
        link: "https://github.com/WebKit/standards-positions/issues/28",
        position: "oppose"
      }
    }
  }
]


Options "sort" don't work using rewrite

Example:
//Direct reference sort works OK
PostSchema.plugin(deepPopulate, {
    populate: {
        'approved.user': {
            select: 'name',
            options: {
                limit: 5,
                sort: {name: -1}
            }
        }
    }
});

//Rewrite reference sort don't work
PostSchema.plugin(deepPopulate, {
    populate: {
        'approver': {
            select: 'name',
            options: {
                limit: 5,
                sort: {name: -1}
            }
        }
    }
});

BTW your plugin is awesome, it works better than the normal populate.

Already addressed in v1.0.0


Improved stability on Android.

Only detaching from JVM thread if not already attached. Fixes a crash when sharing in a callback from another Java extension. Also removing local references to Java strings from C++.

Thanks!


updating tf version in docs_require

Current coverage is 99.41% (diff: 100%)

No coverage report found for master at fbde5b3.

Powered by Codecov. Last update fbde5b3...3fd0fcf


Error in file(con, "r") : cannot open the connection

Hello,
I am getting the following error when I attempt to run MBASR
file.name.tree="treefile.tree"
file.name.trait.data="traitfile.txt"
file.name.plot.settings="plot.settings.1.txt"
character.type="unordered"
n.samples=500
n.burnin=50
source("MBASR.load.functions.R")
> MBASR(file.name.tree, file.name.trait.data, file.name.plot.settings, character.type, n.samples, n.burnin)

MrBayes is working on the ASR...
Summarizing the results...
Error in file(con, "r") : cannot open the connection
In addition: Warning messages:
1: In file.remove("matrix.nex.t") :
cannot remove file 'matrix.nex.t', reason 'No such file or directory'
2: In file.remove("matrix.nex.mcmc") :
cannot remove file 'matrix.nex.mcmc', reason 'No such file or directory'
3: In file(con, "r") :
Error in file(con, "r") : cannot open the connection

Any help is appreciated.
Thank you,
Vishnu

Hi Vishnu,
Are you using Windows or MacOs?
Best, Steven
Sent from ProtonMail Mobile
On Mon, Mar 8, 2021 at 2:13 PM, VishnuRaghuram94<EMAIL_ADDRESS>wrote:

Hello,
I am getting the following error when I attempt to run MBASR
file.name.tree="treefile.tree"
file.name.trait.data="traitfile.txt"
file.name.plot.settings="plot.settings.1.txt"
character.type="unordered"
n.samples=500
n.burnin=50
source("MBASR.load.functions.R")

MBASR(file.name.tree, file.name.trait.data, file.name.plot.settings, character.type, n.samples, n.burnin)

MrBayes is working on the ASR...
Summarizing the results...
Error in file(con, "r") : cannot open the connection
In addition: Warning messages:
1: In file.remove("matrix.nex.t") :
cannot remove file 'matrix.nex.t', reason 'No such file or directory'
2: In file.remove("matrix.nex.mcmc") :
cannot remove file 'matrix.nex.mcmc', reason 'No such file or directory'
3: In file(con, "r") :
Error in file(con, "r") : cannot open the connection

Any help is appreciated.
Thank you,
Vishnu
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I am on Windows

Hi Vishnu,
I tried to recreate your error, but no success. If you want to email me your tree file and trait data file, perhaps I can find the issue. Your data is confidential with me.
In the meantime, there is a brief tutorial video here:
https://youtu.be/IVta6QVo6yM
Also, there is a very recent version update of MBASR at GitHub. Maybe you will want to grab the zip with the newest code.
All my best,
Steven
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, March 8, 2021 3:13 PM, VishnuRaghuram94<EMAIL_ADDRESS>wrote:

I am on Windows
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi again,
I also noticed one other thing. You have added an n.burnin=50 argument to the R function -- but there is no user assigned burnin for MBASR. The algorithm will automatically discard/filter your burnin generations based on their LnL scores, keeping only generations that attain the LnL plateau. So I suggest that you leave that out as you proceed.
Best, Steven
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, March 8, 2021 6:09 PM, Steven Heritage<EMAIL_ADDRESS>wrote:

Hi Vishnu,
I tried to recreate your error, but no success. If you want to email me your tree file and trait data file, perhaps I can find the issue. Your data is confidential with me.
In the meantime, there is a brief tutorial video here:
https://youtu.be/IVta6QVo6yM
Also, there is a very recent version update of MBASR at GitHub. Maybe you will want to grab the zip with the newest code.
All my best,
Steven
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, March 8, 2021 3:13 PM, VishnuRaghuram94<EMAIL_ADDRESS>wrote:

I am on Windows
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.


How to show the ctc loss?

I want to view the loss of the warp-ctc each epoch to prevent overfit. Is there a way to show the ctc loss just like 'accuracy' or 'F1'?

I want to view the loss of the warp-ctc each epoch to prevent overfit. Is there a way to show the ctc loss just like 'accuracy' or 'F1'?

@maybepossible , Could you please post your question on discuss.mxnet.io ? We handle questions through that forum.
@sandeep-krishnamurthy Could you please tag the issue as question and close the issue.
@maybepossible Please feel free to reopen in case it is closed in error.

Please ask usage related questions at https://discuss.mxnet.io/ for more people being able to answer, search and refer in future. We want to keep GitHub for issues/bugs.


Lambda packaging suddenly failing.

Description
I can't honestly explain what is going on because it worked Friday and today it doesn't. I see no significant changes to anything related to this code. Already tried backing out to aws provider 4.56.0. Same exact messages.
│ Error: External Program Execution Failed
│
│   with module.edge_lambda.data.external.archive_prepare[0],
│   on .terraform/modules/edge_lambda/package.tf line 10, in data "external" "archive_prepare":
│   10:   program = [local.python, "${path.module}/package.py", "prepare"]
│
│ The data source received an unexpected error while attempting to execute the program.
│
│ Program: /usr/local/bin/python3
│ Error Message: Traceback (most recent call last):
│   File "/Users/spliskamatyshak/Documents/GitHub/discover-api/infrastructure/pipelines/acct-infra/.terraform/modules/edge_lambda/package.py", line 1627, in <module>
│     main()
│   File "/Users/spliskamatyshak/Documents/GitHub/discover-api/infrastructure/pipelines/acct-infra/.terraform/modules/edge_lambda/package.py", line 1623, in main
│     exit(args.command(args))
│          ^^^^^^^^^^^^^^^^^^
│   File "/Users/spliskamatyshak/Documents/GitHub/discover-api/infrastructure/pipelines/acct-infra/.terraform/modules/edge_lambda/package.py", line 1433, in prepare_command
│     content_hash.update(hash_extra.encode())
│                         ^^^^^^^^^^^^^^^^^
│ AttributeError: 'NoneType' object has no attribute 'encode'
│
│ State: exit status 1

If your request is for a new feature, please use the Feature request template.

[*] ✋ I have searched the open/closed issues and my issue is not listed.

⚠ Note
Before you submit an issue, please perform the following first:

Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists

Versions

Module version [Required]:
4.10.1
Terraform version:

1.3.9

Provider version(s):

provider registry.terraform.io/hashicorp/aws v4.57.0
provider registry.terraform.io/hashicorp/external v2.3.0
provider registry.terraform.io/hashicorp/local v2.3.0
provider registry.terraform.io/hashicorp/null v3.2.1

Reproduction Code [Required]

Steps to reproduce the behavior:

module "edge_lambda" {
  source  = "terraform-aws-modules/lambda/aws"
  version = "~> 4.10"

  function_name  = "within3-discover-headers"
  description    = "Edge lambda for auth0"
  handler        = "index.header"
  runtime        = "nodejs16.x"
  lambda_at_edge = true
  source_path    = "${path.root}/../../fixtures/edge"
}

Expected behavior

Should package the lambda as it has until today.
Actual behavior

See error above.
Terminal Output Screenshot(s)

Additional context

I am also facing this issue for our prod deployment on version 1.38.0.
Did anyone found the root cause or fix for this issue?

It appears this could be related to the external provider used for the data source.
Link to relevant issue and discussion: https://github.com/hashicorp/terraform-provider-external/issues/193

Setting the hash_extra input to an arbitrary value got around this issue.

Updating to v2.3.1 of the external provider fixed the issue for my team.
If you are obtaining the latest provider/not setting constraints, the next deployment should detect this from registry.

I ended up blowing away my repo locally and recloning before things started working again. I'm guessing ultimately, it was the external provider update that actually fixed this.


[Backport release-23.05] {ungoogled-,}chromium,chromedriver: 119.0.6045.199/105 -> 120.0.6099.71

Description of changes
Manual backport of #272487 (and 17ca7f65295805d8ebfeef2b81b68122fb30886e from #271677)
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 273132 run on x86_64-linux 1

20 packages built:

chromedriver
chromium
chromium.sandbox
fast-cli
google-chrome
netflix
playwright-test
puppeteer-cli
python310Packages.pytest-playwright
python310Packages.pytest-playwright.dist
python311Packages.pytest-playwright
python311Packages.pytest-playwright.dist
reveal-md
selendroid
selenium-server-standalone
sharedown
ungoogled-chromium
ungoogled-chromium.sandbox
vhs
wayback

nix-build -A stable -A ungoogled nixos/tests/chromium.nix
/nix/store/4jz2kykr3gfrf4407lnh9slzbhbw2pl6-vm-test-run-chromium-stable
/nix/store/ca237v7gvs7jrkhnw5nccp8nwvxl5k49-vm-test-run-chromium-ungoogled


Ability to pass parameters to the script being executed

Hello!
This pull request provides a way to pass parameters to a bau script file - I based this off of the issue #212. I wanted this for what I am currently trying to achieve with bau!
Here is how you could possibly use it:
C:\bau>scriptcs script_with_params.csx -- process_parameters -p FirstName=John -p LastName=Doe

Corresponding bau script file with details on how the context is retrieved and used.
var bau = Require<Bau>();
var parameters = bau.GetParameterContext();

bau
    .Task("process_parameters")
    .Do(() =>
    {
        Console.WriteLine("Parameters count: " + parameters.Count);
        Console.WriteLine("Parameter 'FirstName': " + parameters["FirstName"]);
        Console.WriteLine("Parameter 'LastName': " + parameters["LastName"]);
    })
.Run();

What follows is the output when running this script
C:\bau>scriptcs script_with_params.csx -- process_parameters -p FirstName=John -p LastName=Doe
[Bau] Bau 0.1.0 Copyright (c) Bau contributors<EMAIL_ADDRESS>[Bau] Running 'process_parameters' and dependencies...
[Bau] Starting 'process_parameters'...
Parameters count: 2
Parameter 'FirstName': John
Parameter 'LastName': Doe
[Bau] Finished 'process_parameters' after 8.58 ms.
[Bau] Completed 'process_parameters' and dependencies in 23.8 ms.

Please check it out!

By the way, this is new fork of bau and I am not using the previous fork I used for my previous contribution!

Just wanted to one more thing - The changes I made also supports accessing the parameters using dynamic, like
var bau = Require<Bau>();
dynamic parameters = bau.GetParameterContext();

bau
    .Task("process_parameters")
    .Do(() =>
    {
        Console.WriteLine("Parameters count: " + parameters.Count);
        Console.WriteLine("Parameter 'FirstName': " + parameters.FirstName);
        Console.WriteLine("Parameter 'LastName': " + parameters.LastName);
    })
.Run();

But this would fail as of since it looks like dynamic is not yet implemented in Roslyn. For example I got the following error:
C:\bau>scriptcs script_with_parameters.csx -- process_parameters -p FirstName=John -p LastNa
me=Doe
ERROR: Script compilation failed. [CompilationErrorException] D:\bau\parameters.
csx(2,1): error CS8000: This language feature ('dynamic') is not yet implemented
 in Roslyn.

Hi @karthik25 thanks for raising this, I'll take a look ASAP.

@adamralph You are welcome and thank you for the opportunity!!

@karthik25 after careful consideration I've decided to mothball this project. If you're interested in taking it over, please let me know.


Failed to get "write" lock\nIs another process using the image [/var/run/kubevirt-private/vmi-disks/manual37/disk.img]

What happened:
virtual machine cannot start after adding a disk
What you expected to happen:
normal start
How to reproduce it (as minimally and precisely as possible):
this is my vm yaml

Additional context:

Environment:

KubeVirt version (use virtctl version): v1.1.0-alpha.0
Kubernetes version (use kubectl version): 23
VM or VMI specifications: N/A
Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): N/A
Kernel (e.g. uname -a): N/A
Install tools: N/A
Others: N/A

could you give us  more info? such as virt-launcher-pod's log?

Are you sharing the PVC with another Pod or VM?

Sorry for the late reply due to illness in the past two days. I will sort it out in a moment.

The root cause of the problem was found. As mentioned above, the sc I bound was created by ourselves and indeed shared pvc with other pods.


self referencing of belongs-to

What version of Go are you using (go version)?
go version go1.8.3 linux/amd64
Which database and its version are you using?
mysql  Ver 15.1 Distrib 5.5.52-MariaDB, for Linux (x86_64) using readline 5.1
What did you do?
My Model:
type User struct {
    ID string `gorm:"primary_key"`
    BelongsToUser string
    BelongsTo *User `gorm:"ForeignKey:BelongsToUser"`
}

expecting for a belongs-to referencing but behaving as has-one referencing

Change to?
type User struct {
    ID string `gorm:"primary_key"`
    BelongsToID string
    BelongsTo *User
}

What if you have struct property names you can not change?
type User struct {
    UUID string `gorm:"primary_key"`
    BelongsToUUID string
    BelongsTo *User
}

I can not easily change the struct property name of BelongsToUUID to BelongsToID. Can I specify in some kind of tag?

Same issue here.

same here ...


HOP glove resprite

About the PR

Resprited the HOP gloves to look a little more fancy
Why / Balance

The HOP is second in command (at least for non security matters), it'd make sense for the HOP's gloves to look fancy like the captain's.
Technical details

n/a
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Re-sprited HOP gloves to match the prestige of being second in command

i don't like the fact it's matching more to uniform, because that gloves supposed to be only for paperwork and not weared all-time

in this world it's drip or drown and the HOP is too important to drown lol

You can also make him a hardsuit, like a captain’s🤡

He's sooo important...

Literally the next after i make the PR after putting a lot of effort into the sprite, it’s getting replaced? It least give it a chance.

i think the brown is a nice contrast with the rest of the uniform and it pairs nicely with the shoes. adding even more blue to the outfit just makes it look more generic and indistinct. The current gloves look plenty fancy as-is with their gold trimmings. I don't see why making them look like bulky gauntlets is a better fit for the role.

alright then, i guess.


Add support for injecting a custom argument into epics

Hi, after using the project for a bit I'm really missing the dependency injection from thunk and redux-observable for my testing.
Implementing this was raised in issue #19 but dismissed at the time in favour of a more elegant HOF approach and imminent API changes, but after four months with no project activity I've gone for the simplest, most pragmatic implementation that I believe is backwards-compatible.
If you're willing to accept this (until the lovely proposed HOF-support rewrite arrives) let me know and I'll update the documentation too.

(there's some travis config issue - the tests should pass!)

Hi, @alex2 . I will check this out very soon. Unfortunately, I've been pretty busy lately. I've been meaning to get back to this and update the project to use most/core, include Flow types, explore the HOFs & this dependency injection feature. I just haven't had time recently. Thanks for submitting the PR. I'd love help, in general!
I'm currently interviewing for new jobs and very busy... I have some take home work to complete this weekend, but I may have a bit of time free if I finish it soon enough. Otherwise, it will be soon after. Sorry for the wait.

No worries, really good of you to let me know. Good luck with your interviewing!

@alex2 After reviewing, yes, I am willing to accept this.
Here are the remaining tasks that need to be accomplished:

As you said, we need to update the documentation to reflect the API change.

The only other thing than documentation that you missed is updating the two Epic interfaces & the createEpicMiddleware function in the index.d.ts type definitions file. This should be relatively straight forward, given what is already there, but let me know if you'd like me to do it instead. Unfortunately, I believe we will have to use the any type for the dependencies argument, as it's really up to the user what they want to pass in there.... it could be a function, an object, etc...

I'd like to merge this and all future PR requests into the dev branch. I manually test things out there to make sure all is safe before merging into master.

Let me know if you're okay with tackling these things. I'm okay with doing any or all of them if you'd prefer, but I figured I'd leave it to you if you'd like to contribute.
Thanks again for taking the initiative to make a PR for this! I had been neglecting the project for a bit too long.

@alex2 You still interested in helping finish this up (docs + type definitions) or would you like me to merge as is and help finish it?

Hey, I've also been interviewing for a new job(!) but managed to be much less communicative than you while doing it, so my apologies for the lack of updates. I'll have some free time this weekend to make your suggested changes.

@alex2 You should do a pull. The type definitions file recently changed somewhat due to someone's pull request to make it compatible with Redux 4.0. The changes are minor, but there are some conflicts right now.
FWIW, I'll wait until later with this, but I've been thinking about changing the API soon to just use object destructuring to pass all params at the same time as one object arg.
Like ({ dispatch, getState, dependencies, stateStream }) => ..., etc.... We should wait on this until later, but what do you think?
It makes a point-free style harder/less readable in some cases, but removes the positional aspect of the arguments and lets you just treat it as a grab-bag, letting you grab the things you need and ignoring the test.


Paginate applications on the prison dashboard page

Context
Jira ticket: https://dsdmoj.atlassian.net/jira/software/c/projects/CAS2/boards/1347?selectedIssue=CAS2-409
Changes in this PR
Adds pagination to the prison dashboard view.
Screenshots of UI changes
Before

After

Release checklist
As part of our continuous deployment strategy we must ensure that this work is
ready to be released at any point. Before merging to main we must first
confirm:
Pre merge checklist

[ ] Are any changes required to the e2e tests?
[ ] If you've added a new route, have you added a new
auditEvent? (see server/routes/apply.ts for examples)
[ ] Are there environment variables or other infrastructure configuration which needs to be included in this release?
[ ] Are there any data migrations required. Automatic or manual?
[ ] Does this rely on changes being deployed to the CAS API?

Post merge checklist
Once we've merged it will be auto-deployed to the dev environment.
Find the build-and-deploy job in CircleCI.
Should a release fail at any step, you as the author should now lead the work to
fix it as soon as possible.

I think with introducing pagination there is a chance the e2e test for 'adding a note to a submitted application created by another user' will fail, if  there are more than 10 applications and so the application it is looking for is on the second page.
Not entirely sure what would be best solution - maybe splitting up the tests, one checks the prison dashboard displays, one that navigates directly to the seeded application and adds a note?

I have a fix for the e2e's here https://github.com/ministryofjustice/hmpps-community-accommodation-tier-2-ui/compare/fix/add-note-on-prison-dashboard?expand=1


Adds first UI tests for SessionDetailActivity using Espresso.

The tests verify initial views are correctly rendered and external Intents are
correctly thrown when clicking the Twitter/GitHub icons by launching the SessionDetailActivity
on connected emulators or devices.
Note that this is the first time for me to setup an emulator on CircleCI.
I referred to this document on how to run an emulator on the CircleCI.
If the pre-submit fails, let me play around the setup until the pre-submit becomes green.

:eyes:

Have you ever set up Circle CI + Espresso? Could you help to set up circle.yml if you can? :sob: :bow:
@hotchemi @KeithYokoma @hkurokawa

@konifar OK. I will take a look.

FYI
I've found CircleCI people created a sample project using Espresso.
https://github.com/circleci/EspressoSample
Trying that way..

Yeah! Thanks!

LGTM! :shipit:

Thanks! Let me add another minor commit to explain those settings introduced by this PR was inspired by the sample project.
Or if you prefer, I can squash the commits in one commit. Which do you prefer?

Thanks! I prefer commented one. It is great helpful for me.

LGTM!


Disable default caching for discovery

fixed

Why was this change done?
At least the doc comments still say that it defaults to one hour:
https://github.com/IdentityServer/IdentityServer4/blob/e130df9abd0b915cf70603442c6b32f9528d350a/src/IdentityServer4/Configuration/DependencyInjection/Options/DiscoveryOptions.cs#L70

The change was done because once you go to production you are expected to choose these values (not us). Also, if you don't know about the value and it's set by default then you might have unexpected behavior in prod.


New issue with two custom ILoggerProvider singletons created on application startup introduced in 2.1

I have had an similar issue earlier but this is not exactly the same and I can't figure out how to do some workaround this time.
My first issue in 2.0
https://github.com/aspnet/Logging/issues/701
That was similar/same as this issue
https://github.com/aspnet/Hosting/issues/1150
Here I have a repo of the issue with the latest commit showing the change between 2.1 and 2.0 removing the part that introduced the issue in 2.0.
https://github.com/Rinsen/MultipleSingletonsCreated
The instance is created for this logger type
"Microsoft.AspNetCore.Hosting.Internal.WebHost"
The easiest way to understand the repo is to put a breakpoint in the ctor in DoNothingLogProvider and end up there two times

Yea this is by design. Are you running into something specific?

I Always get two singletons when I expect to only get one. It was possible previously to only get one by not injecting it to the Startup class.

@davidfowl
Should I maybe just close this issue? No reason to have an open issue hanging around for a thing that is by design and will not change. I don't need more answers as the cost for having a worker doing more or less nothing is so small that it doesen't matter at all.

Right so I believe what you are seeing is related to the fact that in 2.1, we allow 3rd party containers to customer Startup activation and that basically requires us to resolve things earlier in another bootstrapping container.

@davidfowl even when no 3rd party container is used this behavior is valid?
Like @Rinsen, this affected me where I expected a singleton to initialize some behavior and ended up having two.

@bruno-garcia
I use only the built in container so it's not only with 3rd party containers.

I'm reproducing a problem where two instances are created but only the second one is disposed.
This really affects me since the first instance ends up doing the initialization of some state which needs to be disposed and that never gets disposed.
Is the reason of the two instance some intermediate CreateServiceProvider called by the GenericHostBuilder? If so, shouldn't that call dispose on that intermediate container?

Another problem is that - when two LoggingProviders are instantiated, the second one has a different external scope provider. The application uses the second instance for logging, but the WebHost still uses the external scope provider of the first, orphaned logging provider.
I just reported this as https://github.com/aspnet/Home/issues/3395

It seems that both containers are disposed on app shutdown. Is that the case?
Does the first container just stays in memory and is not used?
Is this behavior documented? It would be great to understand it a bit better as it's side effect really affects me.

We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.


Default props for function types are not understood when using spreads

If you specify a defaultProp value for a function type, Flow thinks that it is undefined.
Here is an example (try) of the failure:
import * as React from 'react';

type BaseProps = {
  foo: () => number,
};

type Props = {
  ...BaseProps
};

class MyComponent extends React.Component<Props> {
  static defaultProps = {
    foo: () => 42,
  };

  render() {
    return
{this.props.foo() + 1}
;
  }
}

<MyComponent />

17:     return
{this.props.foo() + 1}
;
                              ^ Cannot call `this.props.foo` because undefined [1] is not a function.
References:
4:   foo: () => number,
          ^ [1]

If I remove the object spread in Props (try), there is no Flow failure.
import * as React from 'react';

type Props = {
  foo: () => number,
};

class MyComponent extends React.Component<Props> {
  static defaultProps = {
    foo: () => 42,
  };

  render() {
    return
{this.props.foo() + 1}
;
  }
}

<MyComponent />

Oddly, this only seems to apply to function types.

Works as expected.
Fixed example.

Hi @apsavin, thanks for your quick reply.
Could you maybe be more descriptive? I am not sure to understand why it works as expected since I don't see any documentation about spread.

Spread makes all fields optional if spreaded type is not exact.
There're PRs with docs.

@apsavin that's much more informative, thanks.

Thanks so much. This helped me spot the problem in my real code.

Spread makes all fields optional if spreaded type is not exact.

This is surprising -- it sounds like a Flow bug. In this case, foo was marked required and even though it's spread into the new object, Flow should be able to figure it out, right? 🤷♀

This is surprising -- it sounds like a Flow bug.

Well, flow team created type spread operator with some semantics. It works by design. You can use it with $Exact so you can change it's behaviour if needed.

The issue seems to be fixed a long time ago


Issue with Latest Flutter Version - 3.24

I get this error after adding the package and trying to run it. please look into this.


Update subsampling.py

The StackNFramesSubsampling module was missing the pos_enc attribute, which caused an AttributeError when pos_enc.position_encoding was called in the forward_chunk.

great


Add email notification text options to "admin" profile pages.

for only certain user email addresses, specified in the environment variables, can access and edit the same notification email/sms text. should be very short and to the point.

Likely going to stay in env variables for now....

We should have way less messages now.. Store in YAML for internationalization.


Update all.json

Site
Urlscan
Screenshot

app-tool.org
NA
https://user-images.githubusercontent.com/97024090/184309953-ab454819-31f1-455d-98ea-11423c96ceeb.png

deficonnects.net
https://urlscan.io/result/7c019227-8516-437d-8801-ab5c7d799df3/dom/
https://user-images.githubusercontent.com/97024090/184307058-26652d4c-7715-4ddd-96f5-6f1203142546.png

defi-connector.info
fearless: https://urlscan.io/result/5b088a87-2f98-497a-96ab-f17e42011d2f/dom/
https://user-images.githubusercontent.com/97024090/184305867-3325f679-7888-4aa8-a1c8-5b396864f2be.png

walletvalidators.net
https://urlscan.io/result/fb07e3ab-3035-48c0-bd3b-a5db1f830900/dom/
https://user-images.githubusercontent.com/97024090/184295684-9e14ca3b-9fe6-4150-934b-993f9c42b8e4.png

Extra proof for app-tool.org:

dapp.allinone-connects.com
This one is already on #2051

Strange because it did resolve for me, wasnt blocked by polkadot.js

Member

Because #2051 is still not merged.


Judges Award will Only Upload Winner

We had multiple teams listed for the Judges Award (2nd and 3rd Place) at Kingsford but only winner is displayed.

It seems you only picked one team.

Fixed.


Unable to play a video from youtube

open('.cache/youtube-viewer/d03b50cf18f60e477b0e9152a7dd10bb', 'w'): Permission denied at /usr/local/lib64/perl5/5.22.2/WWW/YoutubeViewer.pm line 309.

I have this error each time I try to play a video.
The system i am using is gentoo.
I tried to install it from the official repos, but it was not working (i had  no video, and no error).
So I tried to install it from the source (git clone from github), now I am getting this error.
Any help will be appreciated.
H.

The cache directory seems to not be writable. Try to change it to another directory (such as /tmp/) on which you have writable permissions.
The configuration files are:

~/.config/youtube-viewer/youtube-viewer.conf
~/.config/youtube-viewer/gtk-youtube-viewer.conf

Change the cache_dir config value to:
cache_dir => "/tmp/youtube-viewer",

thanks you,
I am not getting the error above anymore, but i am still not getting any video.
I tried the to launch the application with the command below
youtube-viewer --player=mpv --debug
I am getting this

-> Resolution: 720
-> Video itag: 22
-> Video type: video/mp4;+codecs="avc1.64001F,+mp4a.40.2"
-> Command: /usr/bin/mpv --really-quiet --title Donald\ Trump\ Asks\ The\ Terminally\ Ill\ For\ A\ Huge\ Favor https://r2---sn-oxq5u55-cage.googlevideo.com/videoplayback?initcwndbps=628750&lmt=1476015354926355&pcm2cms=yes&expire=1476038143&requiressl=yes&mime=video%2Fmp4&ipbits=0&ratebypass=yes&sparams=dur%2Cei%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Clmt%2Cmime%2Cmm%2Cmn%2Cms%2Cmv%2Cpcm2cms%2Cpl%2Cratebypass%2Crequiressl%2Csource%2Cupn%2Cexpire&upn=cpzpRSNQvw8&itag=22&id=o-AAX8AP6S4gQYvF-dxj3xcyXXz3W8PESQNlhBxuLlbTcJ&ei=njn6V_2VOs78oQOinKbIDg&ms=au&mt=1476015997&mv=m&dur=534.685&source=youtube&pl=24&ip=<IP_ADDRESS>&key=yt6&signature=2451682B98181AB0557C1BD864444211C3EDEE55.3448ECB07523A05F173079384FD85A6B577F9BBF&mm=31&mn=sn-oxq5u55-cage

,and no video.
...

Is mpv installed?

yes, it is

mpv 0.20.0 (C) 2000-2016 mpv/MPlayer/mplayer2 projects
built on UNKNOWN
ffmpeg library versions:
libavutil       54.31.100
libavcodec      56.60.100
libavformat     56.40.101
libswscale      3.1.101
libavfilter     5.40.101
libswresample   1.2.101
ffmpeg version: 2.8.6

Hmm. That's strange. Probably https support was not enabled on ffmpeg/mpv when it was built? (I'm just guessing).
I tried the command from your debug output and it works correctly here. Try to execute the same command locally, but first removing the "--really-quiet" option, to see what is really going on.

Thank you,
It`s working great after recompiling ffmpeg with openssl, gnutls enable.


[Proposal] Unhide Konsole but also keep Ptyxis

Keep Ptyxis as a default though.
Windows has had Powershell and Command Prompt for ages, so why can't we ship two terminals?  Satisfies enjoyers of both terminals.

I'm happy to ship them both as flatpak so people can uninstall the one they don't like, as long as it doesn't interfere with their functionality.

Also the flatpak of Ptyxis is updated faster, just like we had like a month without a fixed Ptyxis version from Fedora when the container profiles "broke"

The only issue I found while using Konsole flatpak (and I assume the same would be with any other terminals running in flatpak), is that when you execute a command, in the titlebar it does not display that command, but it's always flatpak-spawn.
(Not sure if they could be patched in flathub to skip one level and display the next command only, but it would be nice...)

(and I assume the same would be with any other terminals running in flatpak)

huhh, just checked, this is actually NOT the case: Ptyxis flatpak handles the flatpak environment correctly, displays the actual command in the titlebar and even changes title color to red when executing sudo... nice!
(I hope Konsole flatpak will also be corrected in the near future.)
But I think shipping both as flatpak is a good idea, that way ppl can remove the one they don't need.

I'll dogfood konsole for a week and let y'all know if I run into any issues with it.

Is there a way for us to have the Ctrl+Alt+T shortcut use the default terminal instead of being hardcoded to ptyxis?

The only issue I found while using Konsole flatpak (and I assume the same would be with any other terminals running in flatpak), is that when you execute a command, in the titlebar it does not display that command, but it's always flatpak-spawn.
(Not sure if they could be patched in flathub to skip one level and display the next command only, but it would be nice...)

I haven’t found a way around this with the konsole flatpak either, but it’s the only issue I’ve noticed with the flatpak as well.
Personally I’d be in favor of leaving konsole in the image unless a workaround is found, it’s not exactly like it’s eating a ton of space.

IMO, worst case if they uninstall both, they can just reinstall them on discover. I understand the sentiment though, I'm a bit biased tho since I'd prefer to not have ptyxis at all tbh.

Maybe the best would be to include Konsole on the image and Ptyxis as flatpak (as the flatpak comes straight from upstream and not from Fedora).
Not sure where in the configs the ctrl+alt+t shortcut is set, tried to look for it but couldn't yet find where it is set for KDE.

https://github.com/ublue-os/aurora/pull/39
Konsole is back on the image, and i'm happy to remove ptyxis from the image and add it back as a flatpak.

#39
Konsole is back on the image, and i'm happy to remove ptyxis from the image and add it back as a flatpak.

I'm a little more hesitant to do this because Flatpaks are part of the ISO and those who use Ptyxis might also configuration files (however I'm not sure), however I'm open to a PR for :latest before it hits :stable.  Also, I'm asking this a little prematurely and plan to write this up formally for the Aurora maintainers and Universal Blue members, but are you interested in getting right access to approve PRs for this repo soon?  We're looking for some additional contributors/maintainers for this project now that it's separated from Bluefin, so I thought I'd ask this now before I write it up officially to see how this goes since I'm used to writing Bazzite documentation not deputizing contributors. 😅

I'm a little more hesitant to do this because Flatpaks are part of the ISO and those who use Ptyxis might also configuration files (however I'm not sure), but I'm open to a PR for :latest before it hits :stable.

sounds good, i'll make a pr for it.

Also, I'm asking this a little prematurely and plan to write this up formally for the Aurora maintainers and Universal Blue members, but are you interested in getting right access to approve PRs for this repo soon? We're looking for some additional contributors/maintainers for this project now that it's separated from Bluefin, so I thought I'd ask this now before I write it up officially to see how this goes since I'm used to writing Bazzite documentation not deputizing contributors. 😅
EDIT: realized closing this means you can't respond to my question...

Yeah I'm down to help out more, I've been using aurora on both my devices so I'm happy to work on whatever's needed.


Update example spawn-and-move

Update the syntax of example spawn-and-move based on the dojo-starter repository.
Update outdated readme

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (18182a0) 67.51% compared to head (845d714) 67.51%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1413   +/-   ##
=======================================
  Coverage   67.51%   67.51%
=======================================
  Files         231      231
  Lines       21023    21023
=======================================
+ Hits        14193    14194    +1
+ Misses       6830     6829    -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Release notes POC

This is a POC for some changes to the release notes structure.
Summary of changes
Landing page
New landing page with tiles.
Removed What's New page
These items are on the individual pages. The heading on the individual pages (New features and enhancements) doesn't match the title of the What's new page.
There is too much info on the aggregate page. Maybe useful when we had fewer modules, but now we have many more modules and frequent, unsynchronized releases.
Source of much ire WRT merge conflicts. Not helpful with a large number of editors because sometimes changes are inadvertently overwritten.
Avoids potential problem of users going to "Whats new" and never going to the individual module pages (where they can see fixed issues, early access, and hotfixes in addition to what's new).
Need redirect for the removed page. Not sure what to do with the RSS feed.
New layout for early access page
Early access
Presented a new layout and three template options to format information about early access features. I am open to suggestions.
Feature are either early access or GA, so this page is more feature-focused than date-focused - although dates are still present (for date-centric approach, refer to individual release note pages).
My preferred options are pictured below.

The third option (pictured below) is least user-friendly due to being version/date-centric; this doesn't provide valuable information at a high level and forces the reader to "read into" each section rather than scanning the headings for key words that pique their interest. I presented it just to compare with the other two, but I feel it isn't the right choice for this page, which is more of a "beta feature catalog" and less of "cutting edge release notes". Date is not as important here as getting customers interested in testing these beta features.

At the end, there is an option to archive by year (not recommended) or have a "Feature promoted to GA" section where the feature descriptions are moved when they are promoted to GA. We need to have a remove/archive process to prevent this section from getting bloated.
New layout for individual pages
Individual pages- CI page used as a demo.
Organized by MONTH, YYYY and then version.
Hotfixes listed as separate versions rather than subheadings.
Previous release accordion is for the prior year. Current year's release notes should remain visible with clickable/linkable headings (Date/Version).
Only MONTH,YEAR for the current year are "visible". Prior year release notes are inside accordions. During Q1, authors may choose, at their discretion, to progressively "cut over" release notes from the prior year (so that Oct/Nov/Dec release notes aren't immediately "wiped out" in January). By end of Q1, all prior year release notes should be within the prior year accordion.
Exclude the subsection headings if there aren't any of that category in that release (i.e no fixed issues, then no fixed issues heading). This eliminated bloat from excessive headings that only contained the text "This release doesn't include this". It makes the page overall shorter (fewer lines).

New intro blurb
Updated the intro blurb at the top of the release notes pages- it contained some pieces of advisory information that could be handled in a different way.

Reorg left nav
Early access, platform, and delegate first, then modules in alpha order, and SMP and FirstGen last.
I think we should also adopt this approach for the docs, tutorials, and KB 1) for consistency and 2) it makes more sense from a user story perspective (platform/delegate are the base with the modules on top).

Advantages
Here are some benefits of these changes:

Beta features are presented in a more feature-centric view so users can skim and jump to features of interest, rather than being forced to browse by date.
Fewer merge conflicts in the early access file due to module-first heading structure. What's new file no longer exists to cause merge conflicts.
Reflects a more realistic use case for release notes - People most likely to read release notes are existing customers. Do you read release notes for apps that aren't on your phone or games that you don't play? People are going to focus on the apps they already use and are unlikely to read about other apps.
Update no more than 2 files per release. Only need to update 2 if there is a new beta feature or an update to a beta feature.
Individual pages (not the early access page) are sorted by clear MONTH, YEAR headings with versions underneath. This allows us to include a general date for customer visibility, avoid potential misunderstanding when the update is not pushed to a particular cluster on release day, and address the need for a date when preparing the monthly update newsletter for customers. It is easy to see the latest release in the current month without a need for a specific date. Authors can include a specific date in comment format if needed.
The month, year heading structure allows us to keep more headings visible on the page without overcluttering the TOC - This makes it easier to ctrl+F or jump to information from a google/site search. Accordions are prohibitive of crtl+F and arriving from search because the information isn't automatically visible (Ctrl+F will find no results if accordion is closed and a link-to-highlight cant overcome the closed accordion). Setting the accordion to default "open" defeats the purpose of the accordion.

Future considerations

How will we handle long-term archiving? After 4-5 years, there will be a lot of release notes. At some point we should cut off the release notes from the site and archive them somewhere (maybe in PDF format on GitHub?).
Can we get release notes into the software (exclusively or in addition to online)?
Automation?
Early access upkeep: If we are not otherwise informed, authors need to periodically audit their early access features to see which ones have gone to GA and update the early access topic accordingly.
The early access page doesn't list all the feature flags. We need to audit them across the docs (make sure inactive ones aren't listed or marked as GA, and that active ones are properly flagged and documented).

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

We have some MCs, not sure since they are lengthy @aimurphy can you help resolve?

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

We have some MCs, not sure since they are lengthy @aimurphy can you help resolve?

I have to manually fix the release-notes/... ones before I merge. The docusausus.config.js one is probably from auto-changes when Wei was trying to fix the sidebar. It changed all single quotes to double quotes.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app