text:
Juno test Permission denied

I copy the revent and apk files to /usr/local/lib/python2.7/dist-packages/wlauto/workloads/templerun/
then execute the wa , then I found the following error:
2016-08-02 17:43:02,980 INFO     Runner: Connecting to device
2016-08-02 17:43:02,984 DEBUG    android: Discovering ANDROID_HOME from adb path.
2016-08-02 17:43:02,987 DEBUG    android: ANDROID_HOME: /usr
2016-08-02 17:43:02,987 DEBUG    android: Using aapt for version android-4.2.2
2016-08-02 17:43:02,987 DEBUG    android: adb  devices
2016-08-02 17:43:02,991 DEBUG    android: adb disconnect 192.168.1.2:5555
2016-08-02 17:43:02,995 DEBUG    android: adb connect 192.168.1.2:5555
2016-08-02 17:43:02,999 DEBUG    android: connected to 192.168.1.2:5555
2016-08-02 17:43:02,999 DEBUG    android:
2016-08-02 17:43:02,999 DEBUG    android: adb -s 192.168.1.2:5555 shell " if [ -f /proc/cpuinfo ] ; then true ; else false ; fi"
2016-08-02 17:43:03,057 DEBUG    Juno: Polling for device 192.168.1.2:5555...
2016-08-02 17:43:03,058 DEBUG    android: adb  devices
2016-08-02 17:43:03,064 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop sys.boot_completed"
2016-08-02 17:43:03,143 INFO     Runner: Initializing device
2016-08-02 17:43:03,146 DEBUG    ExtensionLoader: Checking module wlauto.result_processors
2016-08-02 17:43:03,147 DEBUG    ExtensionLoader: Checking module wlauto.result_processors.cpustate
2016-08-02 17:43:03,147 DEBUG    ExtensionLoader: 	Adding result_processor cpustates
2016-08-02 17:43:03,147 DEBUG    ExtensionLoader: Checking module wlauto.result_processors.dvfs
2016-08-02 17:43:03,148 DEBUG    ExtensionLoader: 	Adding result_processor dvfs
2016-08-02 17:43:03,148 DEBUG    ExtensionLoader: Checking module wlauto.result_processors.ipynb_exporter
2016-08-02 17:43:03,148 DEBUG    ExtensionLoader: 	Adding result_processor ipynb_exporter
2016-08-02 17:43:03,148 DEBUG    ExtensionLoader: Checking module wlauto.result_processors.mongodb
2016-08-02 17:43:03,148 DEBUG    ExtensionLoader: 	Adding result_processor mongodb
2016-08-02 17:43:03,149 DEBUG    ExtensionLoader: Checking module wlauto.result_processors.notify
2016-08-02 17:43:03,149 DEBUG    ExtensionLoader: 	Adding result_processor notify
2016-08-02 17:43:03,149 DEBUG    ExtensionLoader: Checking module wlauto.result_processors.sqlite
2016-08-02 17:43:03,149 DEBUG    ExtensionLoader: 	Adding result_processor sqlite
2016-08-02 17:43:03,149 DEBUG    ExtensionLoader: Checking module wlauto.result_processors.standard
2016-08-02 17:43:03,150 DEBUG    ExtensionLoader: 	Adding result_processor csv
2016-08-02 17:43:03,150 DEBUG    ExtensionLoader: 	Adding result_processor standard
2016-08-02 17:43:03,150 DEBUG    ExtensionLoader: 	Adding result_processor summary_csv
2016-08-02 17:43:03,150 DEBUG    ExtensionLoader: 	Adding result_processor json
2016-08-02 17:43:03,150 DEBUG    ExtensionLoader: Checking module wlauto.result_processors.status
2016-08-02 17:43:03,151 DEBUG    ExtensionLoader: 	Adding result_processor status
2016-08-02 17:43:03,151 DEBUG    ExtensionLoader: Checking module wlauto.result_processors.syeg
2016-08-02 17:43:03,151 DEBUG    ExtensionLoader: 	Adding result_processor syeg_csv
2016-08-02 17:43:03,151 DEBUG    ExtensionLoader: Checking module wlauto.result_processors.uxperf
2016-08-02 17:43:03,151 DEBUG    ExtensionLoader: 	Adding result_processor uxperf
2016-08-02 17:43:03,160 DEBUG    ExtensionLoader: Checking module wlauto.workloads
2016-08-02 17:43:03,160 DEBUG    ExtensionLoader: Checking module wlauto.workloads.andebench
2016-08-02 17:43:03,160 DEBUG    ExtensionLoader: 	Adding workload andebench
2016-08-02 17:43:03,160 DEBUG    ExtensionLoader: Checking module wlauto.workloads.androbench
2016-08-02 17:43:03,160 DEBUG    ExtensionLoader: 	Adding workload androbench
2016-08-02 17:43:03,160 DEBUG    ExtensionLoader: Checking module wlauto.workloads.angrybirds
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload angrybirds
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: Checking module wlauto.workloads.angrybirds_rio
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload angrybirds_rio
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: Checking module wlauto.workloads.anomaly2
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload anomaly2
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: Checking module wlauto.workloads.antutu
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload antutu
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: Checking module wlauto.workloads.apklaunch
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload apklaunch
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: Checking module wlauto.workloads.applaunch
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload applaunch
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: Checking module wlauto.workloads.audio
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload audio
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: Checking module wlauto.workloads.autotest
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload autotest
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: Checking module wlauto.workloads.bbench
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload bbench
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: Checking module wlauto.workloads.benchmarkpi
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload benchmarkpi
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: Checking module wlauto.workloads.blogbench
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload blogbench
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: Checking module wlauto.workloads.caffeinemark
2016-08-02 17:43:03,161 DEBUG    ExtensionLoader: 	Adding workload caffeinemark
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.cameracapture
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload cameracapture
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.camerarecord
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload camerarecord
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.castlebuilder
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload castlebuilder
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.castlemaster
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload castlemaster
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.cfbench
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload cfbench
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.citadel
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload citadel
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.cyclictest
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload cyclictest
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.dex2oat
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload dex2oat
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.dhrystone
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload dhrystone
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.dungeondefenders
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload dungeondefenders
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.ebizzy
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload ebizzy
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.facebook
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload facebook
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: Checking module wlauto.workloads.geekbench
2016-08-02 17:43:03,162 DEBUG    ExtensionLoader: 	Adding workload geekbench
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.glbcorp
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: 	Adding workload glb_corporate
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.glbenchmark
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: 	Adding workload glbenchmark
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.googlemap
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: 	Adding workload googlemap
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.gunbros2
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: 	Adding workload gunbros2
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.hackbench
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: 	Adding workload hackbench
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.homescreen
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: 	Adding workload homescreen
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.hwuitest
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: 	Adding workload hwuitest
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.idle
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: 	Adding workload idle
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.iozone
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: 	Adding workload iozone
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.ironman
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: 	Adding workload ironman3
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.krazykart
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: 	Adding workload krazykart
2016-08-02 17:43:03,163 DEBUG    ExtensionLoader: Checking module wlauto.workloads.linpack
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload linpack
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.linpack_cli
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload linpack-cli
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.lmbench
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload lmbench
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.manual
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload manual
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.memcpy
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload memcpy
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.nenamark
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload nenamark
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.peacekeeper
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload peacekeeper
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.power_loadtest
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload power_loadtest
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.quadrant
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload quadrant
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.real_linpack
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload real-linpack
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.realracing3
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload realracing3
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.recentfling
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload recentfling
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: Checking module wlauto.workloads.rt_app
2016-08-02 17:43:03,164 DEBUG    ExtensionLoader: 	Adding workload rt-app
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.shellscript
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload shellscript
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.skypevideo
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload skypevideo
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.smartbench
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload smartbench
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.spec2000
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload spec2000
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.sqlite
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload sqlitebm
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.stream
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload stream
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.stress_ng
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload stress_ng
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.sysbench
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload sysbench
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.telemetry
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload telemetry
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.templerun
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload templerun
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.thechase
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload thechase
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: Checking module wlauto.workloads.truckerparking3d
2016-08-02 17:43:03,165 DEBUG    ExtensionLoader: 	Adding workload truckerparking3d
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: Checking module wlauto.workloads.vellamo
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: 	Adding workload vellamo
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: Checking module wlauto.workloads.video
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: 	Adding workload video
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: Checking module wlauto.workloads.videostreaming
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: 	Adding workload videostreaming
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: Checking module wlauto.modules
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: Checking module wlauto.modules.active_cooling
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: 	Adding module mbed-fan
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: 	Adding module odroidxu3-fan
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: Checking module wlauto.modules.cgroups
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: 	Adding module cgroups
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: Checking module wlauto.modules.cpufreq
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: 	Adding module devcpufreq
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: Checking module wlauto.modules.cpuidle
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: 	Adding module cpuidle
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: Checking module wlauto.modules.flashing
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: 	Adding module fastboot
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: 	Adding module vexpress
2016-08-02 17:43:03,166 DEBUG    ExtensionLoader: Checking module wlauto.modules.reset
2016-08-02 17:43:03,167 DEBUG    ExtensionLoader: 	Adding module netio_switch
2016-08-02 17:43:03,168 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation
2016-08-02 17:43:03,168 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.coreutil
2016-08-02 17:43:03,168 DEBUG    ExtensionLoader: 	Adding instrument coreutil
2016-08-02 17:43:03,168 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.daq
2016-08-02 17:43:03,168 DEBUG    ExtensionLoader: 	Adding instrument daq
2016-08-02 17:43:03,168 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.delay
2016-08-02 17:43:03,168 DEBUG    ExtensionLoader: 	Adding instrument delay
2016-08-02 17:43:03,168 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.dmesg
2016-08-02 17:43:03,168 DEBUG    ExtensionLoader: 	Adding instrument dmesg
2016-08-02 17:43:03,168 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.energy_model
2016-08-02 17:43:03,168 DEBUG    ExtensionLoader: 	Adding instrument energy_model
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.energy_probe
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument energy_probe
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.fps
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument fps
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.freqsweep
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument freq_sweep
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.hwmon
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument hwmon
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.juno_energy
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument juno_energy
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.misc
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument interrupts
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument sysfs_extractor
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument execution_time
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument cpufreq
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.netstats
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument netstats
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.perf
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument perf
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.pmu_logger
2016-08-02 17:43:03,169 DEBUG    ExtensionLoader: 	Adding instrument cci_pmu_logger
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.poller
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: 	Adding instrument file_poller
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.screenon
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: 	Adding instrument screenon
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.servo_power_monitors
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: 	Adding instrument servo_power
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.streamline
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: 	Adding instrument streamline
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: 	Adding resource_getter streamline_resource
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.systrace
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: 	Adding instrument systrace
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: Checking module wlauto.instrumentation.trace_cmd
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: 	Adding instrument trace-cmd
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: Checking module wlauto.commands
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: Checking module wlauto.commands.create
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: 	Adding command create
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: Checking module wlauto.commands.list
2016-08-02 17:43:03,170 DEBUG    ExtensionLoader: 	Adding command list
2016-08-02 17:43:03,171 DEBUG    ExtensionLoader: Checking module wlauto.commands.record
2016-08-02 17:43:03,171 DEBUG    ExtensionLoader: 	Adding command record
2016-08-02 17:43:03,171 DEBUG    ExtensionLoader: 	Adding command replay
2016-08-02 17:43:03,171 DEBUG    ExtensionLoader: Checking module wlauto.commands.run
2016-08-02 17:43:03,171 DEBUG    ExtensionLoader: 	Adding command run
2016-08-02 17:43:03,171 DEBUG    ExtensionLoader: Checking module wlauto.commands.show
2016-08-02 17:43:03,171 DEBUG    ExtensionLoader: 	Adding command show
2016-08-02 17:43:03,172 DEBUG    ExtensionLoader: Checking module wlauto.devices
2016-08-02 17:43:03,172 DEBUG    ExtensionLoader: Checking module wlauto.devices.android
2016-08-02 17:43:03,172 DEBUG    ExtensionLoader: Checking module wlauto.devices.android.gem5
2016-08-02 17:43:03,172 DEBUG    ExtensionLoader: 	Adding device gem5_android
2016-08-02 17:43:03,172 DEBUG    ExtensionLoader: Checking module wlauto.devices.android.generic
2016-08-02 17:43:03,172 DEBUG    ExtensionLoader: 	Adding device generic_android
2016-08-02 17:43:03,172 DEBUG    ExtensionLoader: Checking module wlauto.devices.android.juno
2016-08-02 17:43:03,172 DEBUG    ExtensionLoader: 	Adding device juno
2016-08-02 17:43:03,172 DEBUG    ExtensionLoader: Checking module wlauto.devices.android.nexus10
2016-08-02 17:43:03,172 DEBUG    ExtensionLoader: 	Adding device Nexus10
2016-08-02 17:43:03,172 DEBUG    ExtensionLoader: Checking module wlauto.devices.android.nexus5
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: 	Adding device Nexus5
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: Checking module wlauto.devices.android.note3
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: 	Adding device Note3
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: Checking module wlauto.devices.android.odroidxu3
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: 	Adding device odroidxu3
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: Checking module wlauto.devices.android.tc2
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: 	Adding device TC2
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: Checking module wlauto.devices.linux
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: Checking module wlauto.devices.linux.XE503C12
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: 	Adding device XE503C12
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: Checking module wlauto.devices.linux.chromeos_test_image
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: 	Adding device chromeos_test_image
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: Checking module wlauto.devices.linux.gem5
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: 	Adding device gem5_linux
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: Checking module wlauto.devices.linux.generic
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: 	Adding device generic_linux
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: Checking module wlauto.devices.linux.odroidxu3_linux
2016-08-02 17:43:03,173 DEBUG    ExtensionLoader: 	Adding device odroidxu3_linux
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: Checking module wlauto.resource_getters
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: Checking module wlauto.resource_getters.standard
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter environment_jar
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter environment_dependency
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter extension_asset
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter http_assets
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter env_exe_getter
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter environment_common_dependency
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter filer
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter package_exe_getter
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter filer_assets
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter enviroment_revent
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter package_file
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter package_apk
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter packaged_dependency
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter packaged_common_dependency
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter environment_file
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter exe_getter
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter package_revent
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter environment_apk
2016-08-02 17:43:03,174 DEBUG    ExtensionLoader: 	Adding resource_getter package_jar
2016-08-02 17:43:03,175 DEBUG    ExtensionLoader: Loading from paths.
2016-08-02 17:43:03,175 DEBUG    android: adb -s 192.168.1.2:5555 shell "su"
2016-08-02 17:43:04,179 DEBUG    check_output: 29480 timed out; sending SIGKILL
2016-08-02 17:43:04,180 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/online'\''' | su"
2016-08-02 17:43:04,270 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -e '/sys/devices/system/cpu/cpu0/cpufreq' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:04,336 DEBUG    Juno: Installing module "devcpufreq"
2016-08-02 17:43:04,339 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -e '/sys/devices/system/cpu/cpuidle' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:04,404 DEBUG    Juno: Installing module "cpuidle"
2016-08-02 17:43:04,405 DEBUG    android: adb -s 192.168.1.2:5555 shell "mkdir -p /sdcard/wa-working"
2016-08-02 17:43:04,483 DEBUG    android: adb -s 192.168.1.2:5555 shell "mkdir -p /data/local/tmp/wa-bin"
2016-08-02 17:43:04,559 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -e '/data/local/tmp/wa-bin/busybox' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:04,622 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:04,709 DEBUG    ResourceResolver: Resolving <no-one's arm64 sqlite3>
2016-08-02 17:43:04,710 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:04,710 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:04,710 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:04,711 DEBUG    ResourceResolver: Resource <no-one's arm64 sqlite3> found using :
2016-08-02 17:43:04,711 DEBUG    ResourceResolver: 	/usr/local/lib/python2.7/dist-packages/wlauto/common/bin/arm64/sqlite3
2016-08-02 17:43:04,711 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -e '/data/local/tmp/wa-bin/sqlite3' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:04,773 DEBUG    android: adb -s 192.168.1.2:5555 shell "/data/local/tmp/wa-bin/busybox which sqlite3"
2016-08-02 17:43:04,844 DEBUG    android: adb -s 192.168.1.2:5555 shell "mount"
2016-08-02 17:43:04,931 DEBUG    android: adb -s 192.168.1.2:5555 push '/tmp/tmpcA3VQj' '/sdcard/wa-working/disable_screen_lock'
2016-08-02 17:43:05,058 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cp /sdcard/wa-working/disable_screen_lock /data/local/tmp/wa-bin/disable_screen_lock' | su"
2016-08-02 17:43:05,169 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'chmod 0777 /data/local/tmp/wa-bin/disable_screen_lock' | su"
2016-08-02 17:43:05,265 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo '/data/local/tmp/wa-bin/disable_screen_lock' | su"
2016-08-02 17:43:05,388 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop ro.build.version.sdk"
2016-08-02 17:43:05,453 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'getenforce' | su"
2016-08-02 17:43:05,560 INFO     Runner: Initializing workloads
2016-08-02 17:43:05,561 DEBUG    ResourceResolver: Resolving <'s revent>
2016-08-02 17:43:05,561 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:05,562 DEBUG    RemoteFilerGetter: resource=<'s revent>, version=None, remote_path=templerun, local_path=/root/.workload_automation/dependencies/templerun
2016-08-02 17:43:05,562 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:05,647 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:05,722 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:05,723 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:05,723 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:05,802 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:05,802 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:05,878 DEBUG    ResourceResolver: Resource <'s revent> found using :
2016-08-02 17:43:05,878 DEBUG    ResourceResolver: 	/usr/local/lib/python2.7/dist-packages/wlauto/workloads/templerun/revent_files/juno.setup.revent
2016-08-02 17:43:05,879 DEBUG    ResourceResolver: Resolving <'s revent>
2016-08-02 17:43:05,879 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:05,879 DEBUG    RemoteFilerGetter: resource=<'s revent>, version=None, remote_path=templerun, local_path=/root/.workload_automation/dependencies/templerun
2016-08-02 17:43:05,879 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:05,959 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:06,048 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:06,048 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:06,048 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:06,135 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:06,135 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:06,215 DEBUG    ResourceResolver: Resource <'s revent> found using :
2016-08-02 17:43:06,215 DEBUG    ResourceResolver: 	/usr/local/lib/python2.7/dist-packages/wlauto/workloads/templerun/revent_files/juno.run.revent
2016-08-02 17:43:06,216 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:06,294 DEBUG    ResourceResolver: Resolving <no-one's arm64 revent>
2016-08-02 17:43:06,295 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:06,295 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:06,296 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:06,296 DEBUG    ResourceResolver: Resource <no-one's arm64 revent> found using :
2016-08-02 17:43:06,296 DEBUG    ResourceResolver: 	/usr/local/lib/python2.7/dist-packages/wlauto/common/bin/arm64/revent
2016-08-02 17:43:06,296 DEBUG    android: adb -s 192.168.1.2:5555 shell "mount"
2016-08-02 17:43:06,369 DEBUG    android: adb -s 192.168.1.2:5555 push '/usr/local/lib/python2.7/dist-packages/wlauto/common/bin/arm64/revent' '/sdcard/wa-working/revent'
2016-08-02 17:43:07,555 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cp /sdcard/wa-working/revent /data/local/tmp/wa-bin/revent' | su"
2016-08-02 17:43:07,705 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'chmod 0777 /data/local/tmp/wa-bin/revent' | su"
2016-08-02 17:43:07,800 DEBUG    android: adb -s 192.168.1.2:5555 push '/usr/local/lib/python2.7/dist-packages/wlauto/workloads/templerun/revent_files/juno.run.revent' '/sdcard/wa-working/juno.run.revent'
2016-08-02 17:43:07,996 DEBUG    android: adb -s 192.168.1.2:5555 push '/usr/local/lib/python2.7/dist-packages/wlauto/workloads/templerun/revent_files/juno.setup.revent' '/sdcard/wa-working/juno.setup.revent'
2016-08-02 17:43:08,177 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:08,256 DEBUG    ResourceResolver: Resolving <'s arm64 APK>
2016-08-02 17:43:08,256 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:08,257 DEBUG    RemoteFilerGetter: resource=<'s arm64 APK>, version=None, remote_path=templerun, local_path=/root/.workload_automation/dependencies/templerun
2016-08-02 17:43:08,257 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:08,257 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:08,257 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:08,257 DEBUG    ResourceResolver: Resource <'s arm64 APK> found using :
2016-08-02 17:43:08,257 DEBUG    ResourceResolver: 	/usr/local/lib/python2.7/dist-packages/wlauto/workloads/templerun/Temple_Run_2-Hack.apk
2016-08-02 17:43:08,257 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -f '/etc/arch-release' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:08,315 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -d '/etc/arch-release' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:08,382 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -f '/etc/debian_version' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:08,450 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -d '/etc/debian_version' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:08,518 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -f '/etc/lsb-release' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:08,588 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -d '/etc/lsb-release' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:08,654 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -f '/proc/config.gz' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:08,718 DEBUG    android: adb -s 192.168.1.2:5555 shell "/data/local/tmp/wa-bin/busybox zcat /proc/config.gz"
2016-08-02 17:43:08,832 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -f '/proc/cmdline' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:08,894 DEBUG    android: adb -s 192.168.1.2:5555 shell "cat /proc/cmdline"
2016-08-02 17:43:08,955 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -f '/proc/cpuinfo' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:09,023 DEBUG    android: adb -s 192.168.1.2:5555 shell "cat /proc/cpuinfo"
2016-08-02 17:43:09,091 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -f '/proc/version' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:09,159 DEBUG    android: adb -s 192.168.1.2:5555 shell "cat /proc/version"
2016-08-02 17:43:09,227 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -f '/proc/zconfig' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:09,295 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -d '/proc/zconfig' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:09,363 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -f '/sys/kernel/debug/sched_features' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:09,431 DEBUG    android: adb -s 192.168.1.2:5555 shell "cat /sys/kernel/debug/sched_features"
2016-08-02 17:43:09,499 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -f '/sys/kernel/hmp' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:09,568 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -d '/sys/kernel/hmp' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:09,635 DEBUG    android: adb -s 192.168.1.2:5555 pull '/sys/kernel/hmp' 'wa_output/__meta/sys.kernel.hmp'
2016-08-02 17:43:10,208 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:10,293 DEBUG    android: adb -s 192.168.1.2:5555 shell "dumpsys window > /sdcard/wa-working/window.dumpsys"
2016-08-02 17:43:12,240 DEBUG    android: adb -s 192.168.1.2:5555 pull '/sdcard/wa-working/window.dumpsys' 'wa_output/__meta/window.dumpsys'
2016-08-02 17:43:12,412 DEBUG    android: adb -s 192.168.1.2:5555 shell "ls /sys/devices/system/cpu/cpu0/cpuidle"
2016-08-02 17:43:12,495 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state0/desc'\''' | su"
2016-08-02 17:43:12,576 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state0/name'\''' | su"
2016-08-02 17:43:12,657 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state0/latency'\''' | su"
2016-08-02 17:43:12,750 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state0/power'\''' | su"
2016-08-02 17:43:12,841 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state1/desc'\''' | su"
2016-08-02 17:43:12,932 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state1/name'\''' | su"
2016-08-02 17:43:13,025 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state1/latency'\''' | su"
2016-08-02 17:43:13,117 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state1/power'\''' | su"
2016-08-02 17:43:13,208 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state2/desc'\''' | su"
2016-08-02 17:43:13,288 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state2/name'\''' | su"
2016-08-02 17:43:13,362 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state2/latency'\''' | su"
2016-08-02 17:43:13,452 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cat '\''/sys/devices/system/cpu/cpu0/cpuidle/state2/power'\''' | su"
2016-08-02 17:43:13,545 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -e '/sys/devices/system/cpu/cpuidle' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:13,613 DEBUG    ResourceResolver: Resolving <juno_energy's file readenergy>
2016-08-02 17:43:13,613 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:13,635 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:13,635 DEBUG    RemoteFilerGetter: resource=<juno_energy's file readenergy>, version=None, remote_path=juno_energy, local_path=/root/.workload_automation/dependencies/juno_energy
2016-08-02 17:43:13,636 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:13,636 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:13,636 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:13,636 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:13,637 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:13,637 DEBUG    ResourceResolver: Resource <juno_energy's file readenergy> found using :
2016-08-02 17:43:13,637 DEBUG    ResourceResolver: 	/usr/local/lib/python2.7/dist-packages/wlauto/instrumentation/juno_energy/readenergy
2016-08-02 17:43:13,637 DEBUG    android: adb -s 192.168.1.2:5555 shell "ps | /data/local/tmp/wa-bin/busybox grep readenergy"
2016-08-02 17:43:13,734 DEBUG    android: adb -s 192.168.1.2:5555 shell "mount"
2016-08-02 17:43:13,800 DEBUG    android: adb -s 192.168.1.2:5555 push '/usr/local/lib/python2.7/dist-packages/wlauto/instrumentation/juno_energy/readenergy' '/sdcard/wa-working/readenergy'
2016-08-02 17:43:14,131 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cp /sdcard/wa-working/readenergy /data/local/tmp/wa-bin/readenergy' | su"
2016-08-02 17:43:14,247 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'chmod 0777 /data/local/tmp/wa-bin/readenergy' | su"
2016-08-02 17:43:14,342 DEBUG    android: adb -s 192.168.1.2:5555 shell "getprop"
2016-08-02 17:43:14,422 DEBUG    ResourceResolver: Resolving <trace-cmd's arm64 trace-cmd>
2016-08-02 17:43:14,422 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:14,423 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:14,423 DEBUG    ResourceResolver: Trying
2016-08-02 17:43:14,438 DEBUG    ResourceResolver: Resource <trace-cmd's arm64 trace-cmd> found using :
2016-08-02 17:43:14,438 DEBUG    ResourceResolver: 	/usr/local/lib/python2.7/dist-packages/wlauto/instrumentation/trace_cmd/bin/arm64/trace-cmd
2016-08-02 17:43:14,439 DEBUG    android: adb -s 192.168.1.2:5555 shell "mount"
2016-08-02 17:43:14,524 DEBUG    android: adb -s 192.168.1.2:5555 push '/usr/local/lib/python2.7/dist-packages/wlauto/instrumentation/trace_cmd/bin/arm64/trace-cmd' '/sdcard/wa-working/trace-cmd'
2016-08-02 17:43:15,116 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'cp /sdcard/wa-working/trace-cmd /data/local/tmp/wa-bin/trace-cmd' | su"
2016-08-02 17:43:15,232 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'chmod 0777 /data/local/tmp/wa-bin/trace-cmd' | su"
2016-08-02 17:43:15,328 DEBUG    android: adb -s 192.168.1.2:5555 shell "if [ -e '/sdcard/wa-working/temp-fs-cpufreq' ]; then echo 1; else echo 0; fi"
2016-08-02 17:43:15,393 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'mkdir -p /sdcard/wa-working/temp-fs-cpufreq' | su"
2016-08-02 17:43:15,503 DEBUG    android: adb -s 192.168.1.2:5555 shell "echo 'mount -t tmpfs -o size=32m tmpfs /sdcard/wa-working/temp-fs-cpufreq' | su"
2016-08-02 17:43:15,617 INFO     Runner: Running workload 1 templerun (iteration 1)
2016-08-02 17:43:15,617 DEBUG    instrumentation: Disabling instrument juno_energy
2016-08-02 17:43:15,618 DEBUG    instrumentation: Disabling instrument execution_time
2016-08-02 17:43:15,618 DEBUG    instrumentation: Disabling instrument interrupts
2016-08-02 17:43:15,618 DEBUG    instrumentation: Disabling instrument trace-cmd
2016-08-02 17:43:15,618 DEBUG    instrumentation: Disabling instrument cpufreq
2016-08-02 17:43:15,618 DEBUG    instrumentation: Disabling instrument fps
2016-08-02 17:43:15,619 DEBUG    instrumentation: Enabling instrument execution_time
2016-08-02 17:43:15,619 DEBUG    instrumentation: Enabling instrument interrupts
2016-08-02 17:43:15,619 DEBUG    instrumentation: Enabling instrument cpufreq
2016-08-02 17:43:15,619 DEBUG    instrumentation: Enabling instrument fps
2016-08-02 17:43:15,620 DEBUG    instrumentation: Enabling instrument trace-cmd
2016-08-02 17:43:15,620 DEBUG    instrumentation: Enabling instrument juno_energy
2016-08-02 17:43:15,620 DEBUG    Runner: Setting up device parameters
2016-08-02 17:43:15,622 DEBUG    Runner: running templerun
2016-08-02 17:43:15,622 INFO     Runner: 	Setting up
2016-08-02 17:43:15,622 DEBUG    android: adb -s 192.168.1.2:5555 shell "dumpsys package com.imangi.templerun"
2016-08-02 17:43:15,700 DEBUG    android: /usr/build-tools/android-4.2.2/aapt dump badging /usr/local/lib/python2.7/dist-packages/wlauto/workloads/templerun/Temple_Run_2-Hack.apk
2016-08-02 17:43:15,723 INFO     Runner: 	Skipping the rest of the iterations for this spec.
2016-08-02 17:43:15,723 ERROR    Runner: Error while running templerun
2016-08-02 17:43:15,723 ERROR    Runner: OSError("[Errno 13] Permission denied")
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 739, in _handle_errors
2016-08-02 17:43:15,737 ERROR    Runner:     yield
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 618, in _run_job
2016-08-02 17:43:15,737 ERROR    Runner:     self._run_workload_iteration(spec.workload)
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 673, in _run_workload_iteration
2016-08-02 17:43:15,737 ERROR    Runner:     workload.setup(self.context)
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/local/lib/python2.7/dist-packages/wlauto/common/android/workload.py", line 474, in setup
2016-08-02 17:43:15,737 ERROR    Runner:     ApkWorkload.setup(self, context)
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/local/lib/python2.7/dist-packages/wlauto/common/android/workload.py", line 196, in setup
2016-08-02 17:43:15,737 ERROR    Runner:     self.initialize_package(context)
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/local/lib/python2.7/dist-packages/wlauto/common/android/workload.py", line 204, in initialize_package
2016-08-02 17:43:15,737 ERROR    Runner:     self.initialize_with_host_apk(context, installed_version)
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/local/lib/python2.7/dist-packages/wlauto/common/android/workload.py", line 217, in initialize_with_host_apk
2016-08-02 17:43:15,737 ERROR    Runner:     host_version = ApkInfo(self.apk_file).version_name
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/local/lib/python2.7/dist-packages/wlauto/utils/android.py", line 157, in init
2016-08-02 17:43:15,737 ERROR    Runner:     self.parse(path)
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/local/lib/python2.7/dist-packages/wlauto/utils/android.py", line 163, in parse
2016-08-02 17:43:15,737 ERROR    Runner:     output = subprocess.check_output(command)
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/lib/python2.7/subprocess.py", line 537, in check_output
2016-08-02 17:43:15,737 ERROR    Runner:     process = Popen(stdout=PIPE, *popenargs, **kwargs)
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/lib/python2.7/subprocess.py", line 679, in init
2016-08-02 17:43:15,737 ERROR    Runner:     errread, errwrite)
2016-08-02 17:43:15,737 ERROR    Runner:   File "/usr/lib/python2.7/subprocess.py", line 1249, in _execute_child
2016-08-02 17:43:15,737 ERROR    Runner:     raise child_exception
2016-08-02 17:43:15,737 ERROR    Runner:
2016-08-02 17:43:15,737 INFO     Runner: Job status was FAILED. Retrying...
2016-08-02 17:43:15,737 INFO     Runner: Skipping workload 1 templerun (iteration 2)
2016-08-02 17:43:15,737 INFO     Runner: Skipping workload 1 templerun (iteration 3)
2016-08-02 17:43:15,737 INFO     Runner: Skipping workload 1 templerun (iteration 4)
2016-08-02 17:43:15,738 INFO     Runner: Skipping workload 1 templerun (iteration 5)
2016-08-02 17:43:15,738 INFO     Runner: Skipping workload 1 templerun (iteration 6)
2016-08-02 17:43:15,738 DEBUG    instrumentation: Enabling instrument juno_energy
2016-08-02 17:43:15,738 DEBUG    instrumentation: Enabling instrument execution_time
2016-08-02 17:43:15,738 DEBUG    instrumentation: Enabling instrument interrupts
2016-08-02 17:43:15,738 DEBUG    instrumentation: Enabling instrument trace-cmd
2016-08-02 17:43:15,738 DEBUG    instrumentation: Enabling instrument cpufreq
2016-08-02 17:43:15,738 DEBUG    instrumentation: Enabling instrument fps
2016-08-02 17:43:15,738 INFO     Runner: Finalizing workloads
2016-08-02 17:43:15,738 INFO     Runner: Finalizing.
Is permission denied Juno problem or WA problem?

Instead of using /usr/local/lib/python2.7/dist-packages/wlauto/workloads/templerun/ try using  ~/.workload_automation/dependencies/templerun/

Assumed resolved

repo: ARM-software/workload-automation


text:
Fix #34: Do not try to use a va_list twice

If the prefix function was set, mbed_vtracef would pass ap to vsnprintf to
determine the output length, then use ap again for the actual output,
running off the real arguments.
Create a copy of ap for the initial scan. (Thank you to C99, who added
va_copy. Would have been stuck without it.)

missing test :)

Verified with mbed-client-testapp on Linux , works fine
+1

thanks :)

Expanded the existing prefix function test to take 2 arguments.

source: gharchive/pull-request

authors: jupe kjbracey-arm yogpan01

repo: ARMmbed/mbed-trace

license_type: permissive

license_source: github-api


text:
Migrate release announcements

Background
Release announcements are currently sent to a list of emails originating from the website, but which faces several issues (we don't have a mechanism to extend it anymore and sending out the announcements has an unacceptable delay).
Task Breakdown

[x] create a child page for the release process in confluence for announcement emails and document the remaining subtasks there
[x] ask @danh-arm about the process and create a new release mailing list (eg mbed-tls-announce@lists.trustedfirmware.org)
[x] create an official email address for the purpose of sending the announcements from that (eg mbed-tls@trustedfirmware.org)
[x] compose a last message to the old list with an announcement about the move and
point them to the new announcement list and invite them to the developer lists as well. Have the text reviewed by @danh-arm or @yanesca
[x] send out the last message (on how to do that, see "release announcement" on the Release Process confluence page)
[ ] draft an email template for a release email that is sent out 1 or 2 weeks prior the actual release
[x] revise and improve the template for the second release email. (for a sample release email see "release announcement" on the Release Process confluence page)
[x] have both of the templates reviewed by @danh-arm and @yanesca

This is linked to #3231 in that we want to announce that change at the same time.

The release announcements have been going out on the new announcement list for more than 6 months now. Sending an advance announcement wasn't part of the process and not necessary for the new release process.
Closing this issue as completed.

source: gharchive/issue

authors: danh-arm yanesca

repo: ARMmbed/mbedtls

license_source: bigquery


text:
Cannot build config tsc debug: MLIR not found

I'm currently trying to build the project to work on my side, but I can't get past config_tsc_debug.bat
I'm building using Visual Studio 16 2019
C:\Users\Administrator\Desktop\BetterElytraBot\TypeScriptCompiler\__build\tsc>cmake ../../tsc -G "Visual Studio 16 2019" -A x64 -DCMAKE_BUILD_TYPE=Debug -Wno-dev
-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19045.
-- MLIR_DIR is C:/Users/Administrator/Desktop/BetterElytraBot/TypeScriptCompiler/3rdParty/llvm/debug/lib/cmake/mlir
-- CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE was x64 and set to x64
CMake Error at CMakeLists.txt:62 (find_package):
  Could not find a package configuration file provided by "MLIR" with any of
  the following names:

    MLIRConfig.cmake
    mlir-config.cmake

  Add the installation prefix of "MLIR" to CMAKE_PREFIX_PATH or set
  "MLIR_DIR" to a directory containing one of the above files.  If "MLIR"
  provides a separate development package or SDK, be sure it has been
  installed.

-- Configuring incomplete, errors occurred!
See also "C:/Users/Administrator/Desktop/BetterElytraBot/TypeScriptCompiler/__build/tsc/CMakeFiles/CMakeOutput.log".
See also "C:/Users/Administrator/Desktop/BetterElytraBot/TypeScriptCompiler/__build/tsc/CMakeFiles/CMakeError.log".

The folder /llvm/debug/lib/mlir does not exist

you need to run prepare_3rdParty.bat and ensure that it finished

then u need to open "tsc" folder and run 2 bats:  config_tsc_debug.bat   and then build_tsc_debug.bat

then u need to open "tsc" folder and run 2 bats: config_tsc_debug.bat and then build_tsc_debug.bat

I found out that I needed more than 120 GB of storage to build it so I made some space and restarted
This is how it looks like, now
But it looks like there's still some missing folders

I did find an error and a warning from prepare_3rdParty.bat
CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.24/Modules/GNUInstallDirs.cmake:243 (message):
  Unable to determine default CMAKE_INSTALL_LIBDIR directory because no
  target architecture is known.  Please enable at least one language before
  including GNUInstallDirs.
Call Stack (most recent call first):
  C:/Users/Administrator/Desktop/BetterElytraBot/TypeScriptCompiler/3rdParty/llvm-project/llvm/cmake/modules/LLVMInstallSymlink.cmake:5 (include)
  tools/llvm-ar/cmake_install.cmake:48 (include)
  tools/cmake_install.cmake:39 (include)
  cmake_install.cmake:69 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Error at tools/mlir/lib/Dialect/MemRef/Transforms/cmake_install.cmake:37 (file):
  file INSTALL cannot find
  "C:/Users/Administrator/Desktop/BetterElytraBot/TypeScriptCompiler/__build/llvm/debug/lib/MLIRMemRefTransforms.lib":
  No such file or directory.
Call Stack (most recent call first):
  tools/mlir/lib/Dialect/MemRef/cmake_install.cmake:38 (include)
  tools/mlir/lib/Dialect/cmake_install.cmake:66 (include)
  tools/mlir/lib/cmake_install.cmake:40 (include)
  tools/mlir/cmake_install.cmake:55 (include)
  tools/cmake_install.cmake:45 (include)
  cmake_install.cmake:69 (include)

I built the project again
Here are the errors
CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.24/Modules/GNUInstallDirs.cmake:243 (message):
  Unable to determine default CMAKE_INSTALL_LIBDIR directory because no
  target architecture is known.  Please enable at least one language before
  including GNUInstallDirs.
Call Stack (most recent call first):
  C:/Users/Administrator/Desktop/BetterElytraBot/TypeScriptCompiler/3rdParty/llvm-project/llvm/cmake/modules/LLVMInstallSymlink.cmake:5 (include)
  tools/llvm-ar/cmake_install.cmake:48 (include)
  tools/cmake_install.cmake:39 (include)
  cmake_install.cmake:69 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Error at tools/mlir/lib/Dialect/MemRef/Transforms/cmake_install.cmake:37 (file):
  file INSTALL cannot find
  "C:/Users/Administrator/Desktop/BetterElytraBot/TypeScriptCompiler/__build/llvm/debug/lib/MLIRMemRefTransforms.lib":
  No such file or directory.
Call Stack (most recent call first):
  tools/mlir/lib/Dialect/MemRef/cmake_install.cmake:38 (include)
  tools/mlir/lib/Dialect/cmake_install.cmake:66 (include)
  tools/mlir/lib/cmake_install.cmake:40 (include)
  tools/mlir/cmake_install.cmake:55 (include)
  tools/cmake_install.cmake:45 (include)
  cmake_install.cmake:69 (include)

try do delete __build folder and try again

try do delete __build folder and try again

I tried that multiple times
The 4 first builds were all different
And the 2 latests builds ended up with the same content
I'm not exactly sure what exactly could cause this, maybe I have to use Visual Studio 17 2022 instead of 16 2019 but I can't get the compiler to be recognized with this version

try to use "ninja" build tools

Are you building on linux ?
I will try to build the project in linux to see if it works with ninja

license: MIT


text:
Add autoRIFT golden test pairs for L4,5,7,9

The landsat-4 pair here failed with an OutOfMemoryError: Container killed due to memory usage for all 3 attempts (the log just abruptly ends which is indicative of a memory failure; confirmed by looking at the batch job)
https://hyp3-test-api.asf.alaska.edu/jobs/5efd7f58-0cdf-4663-bed7-68d7b00b16ee
I'll dig up a L4 pair we know runs.

@forrestfwilliams any thoughts as to why the L4 pair failed? Looks to be during the FFT step.

Submitted all the proposed pairs here to production:
https://hyp3-api.asf.alaska.edu/jobs?name=Golden test update for l457
{
  "jobs": [
    {
      "execution_started": true,
      "job_id": "75e52782-505b-4127-9107-66218c6691af",
      "job_parameters": {
        "granules": [
          "LC09_L1GT_215109_20220125_20220125_02_T2",
          "LC09_L1GT_215109_20220210_20220210_02_T2"
        ]
      },
      "job_type": "AUTORIFT",
      "name": "Golden test update for l457",
      "priority": 9996,
      "request_time": "2022-11-03T00:36:26+00:00",
      "status_code": "PENDING",
      "user_id": "jhkennedy"
    },
    {
      "execution_started": true,
      "job_id": "87278854-a560-4bab-8004-4f79c1f5e73f",
      "job_parameters": {
        "granules": [
          "LT05_L1GS_001013_19920425_20200915_02_T2",
          "LT05_L1GS_001013_19920628_20200914_02_T2"
        ]
      },
      "job_type": "AUTORIFT",
      "name": "Golden test update for l457",
      "priority": 9998,
      "request_time": "2022-11-03T00:36:26+00:00",
      "status_code": "PENDING",
      "user_id": "jhkennedy"
    },
    {
      "execution_started": true,
      "job_id": "d0e55049-c7cd-444b-87b9-6fef0d31b276",
      "job_parameters": {
        "granules": [
          "LE07_L1TP_063018_20040911_20200915_02_T1",
          "LE07_L1TP_063018_20040810_20200915_02_T1"
        ]
      },
      "job_type": "AUTORIFT",
      "name": "Golden test update for l457",
      "priority": 9997,
      "request_time": "2022-11-03T00:36:26+00:00",
      "status_code": "PENDING",
      "user_id": "jhkennedy"
    },
    {
      "execution_started": true,
      "job_id": "879efe81-adf2-48cb-89db-f4bd88c577e4",
      "job_parameters": {
        "granules": [
          "LT04_L1TP_063018_19880627_20200917_02_T1",
          "LT04_L1TP_063018_19880627_20200917_02_T1"
        ]
      },
      "job_type": "AUTORIFT",
      "name": "Golden test update for l457",
      "priority": 9999,
      "request_time": "2022-11-03T00:36:26+00:00",
      "status_code": "PENDING",
      "user_id": "jhkennedy"
    }
  ],
  "next": "https://hyp3-api.asf.alaska.edu/jobs?name=Golden+test+update+for+l457&start_token=eyJqb2JfaWQiOiAiZWEyNzkyMzgtM2M0Yi00YWI0LThkOWUtZWQ0OWZhZGZiYzkzIiwgInVzZXJfaWQiOiAiamhrZW5uZWR5IiwgInJlcXVlc3RfdGltZSI6ICIyMDIyLTAyLTE4VDIyOjI5OjQyKzAwOjAwIn0%3D"
}

Woops, accidentally summited the L4 pair with the same reference and secondary scenes. Here's the correct pair, as in the suggestion:
https://hyp3-api.asf.alaska.edu/jobs/4a74c527-f8d4-4ddf-b2ad-a3385f814153


text:
🛑 eatery.ch is down

In 7a36efe, eatery.ch (https://www.eatery.ch/) was down:

HTTP code: 502
Response time: 953 ms

Resolved: eatery.ch is back up in d942ae4.


text:
我之前安装过，然后图片无法全屏就卸载了，但是图片却没法去掉。

然后我现在看可以全屏了，就安装了一下，新图片确实全屏了，但是和以前的图片重叠在一起

你之前的图片应该是使用这个扩展添加上去的--backgound。
解决方法：你尝试再安装之前的这个扩展把图片禁用\关闭，之后再去卸载

authors: AShujiao tomuGo

repo: AShujiao/vscode-background-cover


text:
Highly active tP noted -- Kudos!

Guys, it looks like your tP is maintaining a high-level of coding activities so far and all members are actively contributing (as per the tP Dashboard) :+1:
Note: hope you can work together to help less-active team members, if they need help.
Keep up the good work!

noted 👍

authors: ang-zeyu damithc


text:
Update documentation

Changes include:

Fix issues in user guide
Update user stories in developer guide
Add additional NFRs in developer guide
Add Effort appendix in developer guide
Enlarge the storage class diagram
Readjusted the model component in the UI class diagram
Add PPP
Update Documentation.md to remove traces of AB-3
Update index.md to remove traces of address book

Codecov Report

Merging #286 (ca45524) into master (abc7c90) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #286   +/-   ##
=========================================
  Coverage     76.94%   76.94%
  Complexity      998      998
=========================================
  Files           140      140
  Lines          2646     2646
  Branches        356      356
=========================================
  Hits           2036     2036
  Misses          530      530
  Partials         80       80

Continue to review full report at Codecov.

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

LGTM

authors: codecov-commenter g4ryy nniiggeell


text:
Fix bold

Fixes #312

Codecov Report

Merging #314 (3d7a044) into master (122cdc2) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #314   +/-   ##
=========================================
  Coverage     75.97%   75.97%
  Complexity      683      683
=========================================
  Files            94       94
  Lines          1998     1998
  Branches        223      223
=========================================
  Hits           1518     1518
  Misses          414      414
  Partials         66       66

Continue to review full report at Codecov.

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

authors: codecov-commenter yeo-yiheng


text:
Update functionality of finding people

IMPORTANT (Can skip reviewing files changed first)
The functionality of find has been drastically changed to include flags for finding based on any detail (e.g. find -n for names). It will not work without flags but I am open to changing back to the original way of finding by name without a flag. Also, the keywords for find must be spaced apart, otherwise, it is taken as one keyword
It will no longer be possible to find multiple people at once just by matching any of the keywords for this implementation so "find -n Alex Bernice" will not give any results for the basic list because "Alex Bernice" does not match any name as an abbreviation. However, if the keywords match the names of multiple people, it would still return more than one person. There would probably need to be a certain character or flag to specify finding people with other abbreviations (which I think is unnecessary since there are tags and tasks for grouping but I would be open to making this option possible).
Also, the "subsequence" is relative to each part of a person's detail (e.g. name). So, an example would be "Harry James Potter" and "Harry J Potter" or "h P" would work because there is some part of the name that starts with one of the keywords and the order of the keywords relative to the name is the same, regardless of case. For this reasons, "a J P" would not be valid. It also preserves the functionality of finding by full name.
Let me know if the sequence is supposed to be one keyword and just match the names by each character in the subsequence and have the same order as the different parts of the name (e.g. ay -> alex yeoh) because I think a pure subsequence to match any part of a person's name could end up in matching many people's names that should not have matched unless it is case-sensitive (e.g. ex -> alex yeoh). Its also consistent with the way I implemented the find function for other details like tags and tasks because I think one word as a subsequence for many tags or tasks is not ideal. So, this is why I implemented finding by names this way but I could see a special case for names
Also, I'm not sure if everything needs to be abbreviated, like phone number, so do let me know as well.
Less important
However, this order that I've been using does not matter for tags or tasks since it is not as important as for the other details, though the keywords will still have to all match someone's tags or tasks, following the idea for finding by name (or its abbreviation).

LGTM. Might want to consider adding for description too.

Some descriptions might be long and random so I think it might be doable but I I think I would have to go back to full word matches to reduce the number of matches. If everyone thinks its ok, then I'll implement it.

LGTM. I think how the keywords are matched are similar to IntelliJ's search which I think is fine.


text:
Update PPP - Hao Wei

Changes
This PR amends the PPP by adding recent contributions to the program as well as standardizing the program description.
Related Issues
None.

Codecov Report

Merging #322 (f74f3c0) into master (ed8ca54) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #322   +/-   ##
=========================================
  Coverage     72.28%   72.28%
  Complexity     1247     1247
=========================================
  Files           160      160
  Lines          3842     3842
  Branches        452      452
=========================================
  Hits           2777     2777
  Misses          985      985
  Partials         80       80

Continue to review full report at Codecov.

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

authors: KwanHW codecov-commenter


text:
Enhance new meeting parser

NOTE:
This is a major change that affects how CreateMeetingCommand and CreateMeetingCommandParser function, although the expected outcomes are the same. Need to re-write the corresponding tests.
What?
Modified CreateMeetingCommandParser such that it handles more of the validation of the user input instead of letting CreateMeetingCommand and Meeting handle the validation.
Why?
Previously most of the validation takes place in the CreateMeetingCommand and Meeting classes -- in CreateMeetingCommandParser, the parse(arguments) method only checks whether the arguments are empty, while passing the trimmed input arguments wholesale to the CreateMeetingCommand class for processing, which defeats the purpose of a parser. Thus it is preferable to restructure the code such that CreateMeetingCommandParser adheres to the necessary functionalities of a parser. Refer to #68
How?
I have moved the splitting of the trimmed user input (names of Person(s) to meet, meeting description, meeting date and time, meeting location) and the validation of date and time [essentially processes that do not require the model] forward to CreateMeetingCommandParser, leaving CreateMeetingCommand to use the model to handle the validation of the person/ contact, as well as the creation and validation of the new Meeting. Meeting will take in the information of the new meeting passed in as the arguments of its constructor without further validation.

Codecov Report
Base: 67.82% // Head: 62.18% // Decreases project coverage by -5.64% :warning:

Coverage data is based on head (ba0370d) compared to base (057cbb3).
Patch coverage: 38.98% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #69      +/-   ##
============================================
- Coverage     67.82%   62.18%   -5.65%
+ Complexity      556      518      -38
============================================
  Files           102      105       +3
  Lines          1930     1962      +32
  Branches        209      215       +6
============================================
- Hits           1309     1220      -89
- Misses          564      677     +113
- Partials         57       65       +8

Impacted Files
Coverage Δ

...u/address/logic/commands/DeleteMeetingCommand.java
0.00% <0.00%> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
62.96% <0.00%> (-2.43%)
:arrow_down:

...dress/logic/parser/DeleteMeetingCommandParser.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
74.07% <0.00%> (-9.88%)
:arrow_down:

...el/meeting/exceptions/ImpreciseMatchException.java
0.00% <0.00%> (ø)

...main/java/seedu/address/model/meeting/Meeting.java
71.05% <42.85%> (-8.70%)
:arrow_down:

...u/address/logic/commands/CreateMeetingCommand.java
17.64% <45.45%> (-76.95%)
:arrow_down:

...dress/logic/parser/CreateMeetingCommandParser.java
82.60% <77.77%> (-17.40%)
:arrow_down:

...edu/address/logic/commands/EditMeetingCommand.java
57.14% <100.00%> (-38.10%)
:arrow_down:

... and 11 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: HakkaNgin codecov-commenter


text:
Added Edit Record Functionality

Added EditRecordCommand, EditRecordCommandParser for editing of a patient's records
Added test classes for EditRecordCommand, EditRecordCommandParser
Updated test class for DeleteRecordCommandParser
Added Exception classes for duplicate or missing Record
Enabled assertions in build.gradle
Renamed Record commands

Resolves #73 , #75

Codecov Report

Merging #79 (2510761) into master (f0fa370) will increase coverage by 0.94%.
The diff coverage is 73.83%.

@@             Coverage Diff              @@
##             master      #79      +/-   ##
============================================
+ Coverage     69.85%   70.80%   +0.94%
- Complexity      535      567      +32
============================================
  Files            94       98       +4
  Lines          1712     1819     +107
  Branches        172      196      +24
============================================
+ Hits           1196     1288      +92
+ Misses          465      463       -2
- Partials         51       68      +17

Impacted Files
Coverage Δ

.../java/seedu/address/logic/commands/AddCommand.java
85.71% <ø> (ø)

...seedu/address/logic/commands/AddRecordCommand.java
86.66% <ø> (ø)

...edu/address/logic/commands/ClearRecordCommand.java
100.00% <ø> (ø)

...du/address/logic/commands/DeleteRecordCommand.java
85.71% <ø> (ø)

...eedu/address/logic/commands/FindRecordCommand.java
81.81% <ø> (ø)

...eedu/address/logic/commands/ListRecordCommand.java
100.00% <ø> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
68.00% <0.00%> (-2.84%)
:arrow_down:

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)

...el/person/exceptions/DuplicateRecordException.java
0.00% <0.00%> (ø)

...del/person/exceptions/RecordNotFoundException.java
0.00% <0.00%> (ø)

... and 9 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: anthonyhoth codecov-commenter


text:
[PE-D][Tester B] Add command allows non numeric characters for phone number

The add command allows non numeric characthers entered for the phone number.
Command Used: add n/Test2 p/123/// e/test@gmail.com

Labels: severity.Medium type.FunctionalityBug
original: nicholascher/ped#8

Duplicate of #166.


text:
Combine sample data, examples into ProductionData

There are some classes that handle sample data that end users will see, such as SampleContactsUtil. There are also a fair few locations with help text that include many arbitrary strings of valid data. We could combine these into some form of ProductionData file, similar to how we now have a TestData. Note that such a file should likely be in main/ and not test/.
The class may contain mostly valid data, but in case invalid data is needed, it could contain that too. Then, we could import these values into TestData for use in our actual tests, replacing any existing values that serve the same purpose (it may turn out to be good to ensure the values we show to users are actually valid/invalid).
This may be considered a subissue of #76.

Nice to have, but won't negatively impact grading if not done. Culling this issue.


text:
A revamped GUI for the existing UI

Note: The whole UI will be done by v1.3b.

And Also revamping success messages etc


text:
add PersonCreator class

Fixes #63 and #64

Should we just name it as PersonBuilder? I think that's the convention for this builder pattern.

What do you guys think about following the pattern described here.
The Person constructor will be private, and PersonBuilder will be a static nested class inside Person (so that it has access to the Person constructor). Any Person object will be created only through PersonBuilder. Optional attributes can be added by calling the corresponding with... method. The final collection of fields will then be used to create a Person using the build method.

Good idea! I will reference this in another issue.

authors: dickongwd lilozz2 zhyuhan


text:
[PE-D][Tester B] Improvement on the warning message returned

Command that I input: add /nMary p/11111 c/1111 t/1233
Response: Invalid command format!
add: Adds a person to the address book. Parameters: n/NAME p/PHONE [e/EMAIL] [a/ADDRESS] [th/TELEHANDLE] [t/TAG]... [c/COURSE]...
Example: add n/John Doe p/98765432 e/johnd@example.com a/311, Clementi Ave 2, #02-25 th/@Johnnnnyyy t/Friend c/CS2100 c/CS2103T c/IS1108
Perhaps try to specify which type of input the user input in an invalid format would be more useful. Currently, I am not sure about whether the input type of phone, course or tag is wrong in the case provided above.

Labels: severity.Low type.DocumentationBug
original: NgChunMan/ped#1

Note taken on feature suggestion.

authors: Carlintyj nus-pe-script


text:
Create Project Portfolio Page

Create skeletal Project Portfolio Page (PPP)

Completed [#40]


text:
AddClaim unable to take in parameters in any order

Should we implement AddClaim such that parameters can be in any order (as stated in the original user guide)? There is a contradiction between the user guide and AddClaim parser.
When order of parameters is changed, the wrong error message is shown as well.

Possible solution 1: Remove the point on "Parameters can be in any order" from the user guide

Possible solution 2: Implement ability to take in parameters in any order for AddClaim

I personally think solution 1 would be better

i think solution 1 is also best, but if u wanna explore solution 2, maybe we can see how it is done in the "Add" command

i fixed it as such in my most recent PR


text:
[Alek] ummatch [non-natural num] [non-natural num] feedback not specific

I think this is not really a format issue?
This error message is not specific that the issue is with the index

authors: KengHian Quasant


text:
Standardize FindCommand logic

Currently, if we find by multiple keywords with the same field with find, CC will OR the predicates. However, when finding by different fields (name and tag for example), CC will AND both predicates.

Suspect this is due to the argMultiMap grouping keywords for the same field together, causing this difference (confirmed)

Proposed changes:

Enforce 1 keyword per field except for tag (keep the AND)
Get all contacts that fulfill any predicate (keep the OR)

Closed, we have decided to keep this functionality


text:
Mapping pixels to voxels

Hi Aaron,
Thanks for sharing the code. I would like to know, how can I map pixels in the scaled image to voxels in the raw file. Like if I localize a face feature lets say nose in jpg, how can I know  which part of raw file correspond to that region. I am planning to interpolate 2 raw files for specific features like nose etc. to simulate aesthetic surgery results. Do you have any tips. Thanks.

A pre-processing step crops the image. The volume is in direct correspondence with this image. If you load the raw file using readvol and take sum(vol,3) you will see that it is in correspondence.

Hi Aaron,
Can you tell me what does values at a particular voxel in raw file signify? Earlier I thought there are only two values 0 and 255, indicating whether the voxel is filled or not. Am I correct? I see multiple values different values

Never mind. I figured

Some isosurface functions use it for smoothing. Matlab does a very nice job of this.

authors: AaronJackson aggarwal-himanshu

repo: AaronJackson/vrn

license: mit


text:
🛑 NNAF main website is down

In c26e0f6, NNAF main website (https://abortionfunds.org) was down:

HTTP code: 403
Response time: 581 ms

Resolved: NNAF main website is back up in 80ee808.

repo: AbortionFunds/nnaf-status


text:
install packages to a different root directory

We need to install packages to a directory other than /usr/local, because we need to be able to access multiple VFX reference platforms without having to switch between different Docker images.
The shell scripts that build each package allow you to specify any location you want, which is a good start. But adapting the Dockerfiles to build and install all the packages to a different location is a huge headache. (For me, anyway.)
Has anybody else out there been confronted with this problem? And perhaps found a solution?

You can use the Conan packages to install the available packages anywhere. Building multiple parallel VFX platforms in the same image would be very hard without Conan. Unfortunately not all VFX packages are available yet in Conan.

Thanks for that, Aloys. When you say "the Conan packages", do you mean one can use the Conan recipes provided by ASWF to do this? Or do you mean to use packages from Conan Center?

The direction in which the containers are evolving is that packages will all be built as Conan packages, and then assembled into runnable containers: we're not quite there yet, but getting there.
Starting with VFX 2023, there's a script in scripts/common/install_conanpackages.sh which installs all the Conan packages called for by a container, and if you look in python/aswfdocker/data/ci-image-dockerfile.jinja2 you will find the template for the code installing those packages in /usr/local:
{% if name != "common" %}
RUN --mount=type=cache,target=/opt/conan_home/d \
    --mount=type=bind,rw,target=/opt/conan_home/.conan,source=packages/conan/settings \
    /tmp/install_conanpackages.sh /usr/local vfx${ASWF_VFXPLATFORM_VERSION}
{% else %}
RUN --mount=type=cache,target=/opt/conan_home/d \
    --mount=type=bind,rw,target=/opt/conan_home/.conan,source=packages/conan/settings \
    /tmp/install_conanpackages.sh /usr/local ci_common${CI_COMMON_VERSION}
{% endif %}

So you could change the destination based on the ASWF_VFXPLATFORM_VERSION variable, then:
aswfdocker dockergen

which regenerates the ci-*/Dockerfile files, and rebuild your own containers with a versioned installation destination.
Of course that only handles the Conan packages... It would definitely be better if the aswfdocker command had an option to specify the installation prefix for custom builds.

authors: aloysbaillet glevner jfpanisset

repo: AcademySoftwareFoundation/aswf-docker


text:
Clean up cmake/config

Remove unused cmake/JoinPaths.cmake
Remove unused cmake/OpenEXRLibraryDefine.cmake
Clean up and reformat comments

Signed-off-by: Cary Phillips cary@ilm.com

I think I may have botched the merge when resolving the conflicts here. Can someone confirm that the squash and merge here will still leave a linear history?

I noticed that the have large stack support was set after the config file was generated while I was making the changes for symbol visibility configure options, so that should be addressed. There are a number of other cleanups I would like to see eventually (not needed prior to 3.0 release), such as I don't believe we need IexConfig.h or IlmThreadConfig.h any more...

This PR removes two unused files and cleans up some comments, no need to go
into the 3.0.0 release. It has conflicts that need to be resolved anyway,
it may be better to start from scratch, I'll close it and open another
later.
On Mon, Mar 15, 2021 at 3:50 AM Kimball Thurston @.***>
wrote:

I noticed that the have large stack support was set after the config file
was generated while I was making the changes for symbol visibility
configure options, so that should be addressed. There are a number of other
cleanups I would like to see eventually (not needed prior to 3.0 release),
such as I don't believe we need IexConfig.h or IlmThreadConfig.h any more...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AcademySoftwareFoundation/openexr/pull/957#issuecomment-799319344,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFC3DGLWBEDAPDSSYIHKKV3TDXQ7TANCNFSM4Y454MTQ
.

--
Cary Phillips | R&D Supervisor | ILM | San Francisco

repo: AcademySoftwareFoundation/openexr


text:
Create overview of communication tools and calendar processes and opt…

…ions for ASWF projects
Signed-off-by: John Mertic jmertic@linuxfoundation.org

Agreed @jfpanisset  - feel free to make the edits in there.

repo: AcademySoftwareFoundation/tac


text:
Update to instructions

This is to update the instructions to inform users of the requirement to open port 80 to complete the stack installation, and instruction of how to achieve this.

Thanks @stephankfolkes for the contribution. However, this has been added to the readme already (https://github.com/Accenture/adop-docker-compose).

authors: RobertNorthard stephankfolkes

repo: Accenture/adop-docker-compose


text:
Improve Pause and Play controls

The aria labels for slide controls could be clearer by using "Pause Carousel" instead of "Pause" and "Play Carousel" instead of "Play".

Because this looked like it qualified as one of the simpler updates, I went ahead and created a Pull Request.


text:
feat(ws): Add a WebSocket server option

Requires #12

me omw to lgtm my own code >:)

repo: AceLikesGhosts/ytm-rpc


text:
Add Day3 stuff

Contains everything from the last day, before I almost lost it all

Looks like this won't work, gonna need a force push because PICO being pico


text:
feat: add login with phone  return code

根据框架加了验证手机号，然后返回固定验证码，以及写了中间件处理验证码那一块

A了哥

authors: Goblin-master dbinggo

repo: AchoBeta/achobeta-pluto-backend


text:
Fix some typos and simplify age calculation a bit.

I think using DayOfYear makes the code a little easier to read compared to checking both month and day.

Thank you, much nicer!

authors: PeterOrneholm viktorvan


text:
fix(versions): update Activiti/activiti-cloud-connectors versions into develop

UpdateBot pushed maven dependency: org.activiti.cloud.common:activiti-cloud-service-common-dependencies to: 7.1.43

UpdateBot commands:
updatebot push-version --kind maven org.activiti.cloud.common:activiti-cloud-service-common-dependencies 7.1.43

repo: Activiti/activiti-cloud-connectors


text:
update org.activiti.cloud.query:activiti-cloud-query-dependencies to 7.0.20

UpdateBot pushed maven dependency: org.activiti.cloud.query:activiti-cloud-query-dependencies to: 7.0.19

UpdateBot commands:
updatebot push-version --kind maven org.activiti.cloud.query:activiti-cloud-query-dependencies 7.0.19

UpdateBot commands:
updatebot push-version --kind maven org.activiti.cloud.query:activiti-cloud-query-dependencies 7.0.20

UpdateBot commands:
updatebot push-version --kind maven org.activiti.cloud.query:activiti-cloud-query-dependencies 7.0.21

UpdateBot commands:
updatebot push-version --kind maven org.activiti.cloud.query:activiti-cloud-query-dependencies 7.0.22

UpdateBot commands:
updatebot push-version --kind maven org.activiti.cloud.query:activiti-cloud-query-dependencies 7.0.22

repo: Activiti/activiti-cloud-dependencies


text:
update [\s+tag: (.*)] to 0.0.136

UpdateBot pushed regex: [\s+tag: (.*)] to: 0.0.136

UpdateBot commands:
updatebot push-regex --regex \s+tag: (.*) --value 0.0.136 --exclude --previous-line \s+ repository: activiti/activiti-modeling-app charts/activiti-cloud-modeling/values.yaml

repo: Activiti/activiti-cloud-modeling


text:
Create a Docs Repository

Summary
As discussed in issue #355, we should consider moving away from the GitHub Wiki for documentation in the long term. One alternative would be to create a new AdamsLair/duality-docs repo that hosts all documentation.
Analysis

The GitHub Wiki lacks some features and also has some disadvantages from the management side:

Pages need to have unique names and folder structures are ignored.
Users can't upload images and other media.
Lack of multi-version support (crucial for v3.0).
Lack of multi-language support.
No branches for bigger edits, no PRs or reviews.
Either everyone can edit, or only people with direct push access.
History not available on a global level.

All of these problems are solved by moving docs to a new AdamsLair/duality-docs repository.
The repository's main readme file acts as the home page for documentation.
A proper directory structure needs to be defined.

Anticipate support for multiple versions co-existing.
Anticipate support for multiple languages co-existing.
Maybe something like Pages/en/vX/...?

Investigate the possibility of turning on the github pages feature for the master branch and generating a nice docs website from the markdown files.

This issue is up for grabs. Let me know if you're interested in getting some work done on this. Ideally, do the first prototypes in a public repo in your own account, which we can later either transfer or re-create in the AdamsLair organization.

I think creating new repository is  a best for management.

As things stand the duality project is actually pretty heavy, due to binaries being in the repo or otherwise, so we ought to put the documentation in a separate repo for that reason if nothing else.

Yep. And even if it was only for keeping it tidy, I'd still agree 100%.

Assuming that route is taken, I can start transferring our documentation into a repo and put together a gh-pages structure that seems intuitive and then we can transfer the repo over to the AdamsLair space. It seems like this would be pretty easy to do, I've transferred repos previously and it's seamless.

Sounds good! GitHub also allows you to configure the repo so all the docs can be on the regular master branch, so we don't have to use this awkward gh-pages naming convention.

gh-pages will generate the documentation pages as we commit/merge to master on the documentation repo, which means we can focus on creating content using markdown and create a custom theme over time to ensure that it ultimately conforms to the Duality branded color and stylistic choices.

👍

Overall, however, we ought to be strict about making our contributions in markdown, as anything else only makes maintenance more complicated.

Yep, agree completely. We should limit the docs to markdown for maintenance reasons, and also to strictly separate content from design / layout.

Please let me know if there are other elements you would like to have me look into.

I think it would be a good thing to have a first "prototype", and then we can take it from there and talk about how to proceed.

Sounds good. I'll get it going this evening. Expect a link when you pop on tomorrow.

I have cloned the wiki repo and shoved it into my repo for testing.

The site is currently published at https://bobgneu.github.io/duality-documentation

Got the index page into place. Gonna take a break for the evening to do some thinking about organization.

I have cloned the wiki repo and shoved it into my repo for testing.

Okay, let's iterate on this. 👍
First thing that we need to improve vs. the raw wiki export is directory structure. The root folder shouldn't have any content, and we should anticipate docs for multiple Duality versions and, potentially, in multiple languages. Multi-language is not a priority for now, but it only costs us another directory step, so we might as well include it.
I'd currently go with a directory structure like this:
Pages/en/v2/...

Except for the welcome page, which could remain in root. Not yet sure about how to organize folders inside /v2/....
Second point, is there any way to get the footer and sidebar back?

The template can be modified. I can look into that if you would like.

I reorganized the pages as requested and took the liberty of wrapping my mind around the template system, and its quite straight forward.
{% include footer.html %}

the include statement references a file within the _layouts directory, and explicitly drops its content into the template. By default the default.html template is used, where the {{content}} block is replaced by the rendered markdown.
It is rudimentary, but works.
There is the ability for each md file to include configuration in its header, as well as some customization fields as we see fit.
I tried to include markdown, but the contents are not rendered, and instead just copied in explicitly, even with an md extension.
WRT Organizing the documentation, a good first step would be to classify them based on the perspective of a new developer. Each document could be bucketed based on a Low/Medium/High experience score that we can now derive from a value in the header of the md file, tied to a badge or something in the top right of each page. Some level of flagging of Tutorials would also be beneficial, as when I was starting up the first steps were pretty daunting and I was looking for tutorials to help bridge the gaps when kicking off my first project.

For Inspiration: https://github.com/pages-themes

Re-organized folder structure looks good. Also, thanks for your insight into the templating - seems like we could provide a completely custom template file, complete with footer and potentially even an auto-generated sidebar. Sounds very promising!

WRT Organizing the documentation, a good first step would be to classify them based on the perspective of a new developer. Each document could be bucketed based on a Low/Medium/High experience score that we can now derive from a value in the header of the md file, tied to a badge or something in the top right of each page. Some level of flagging of Tutorials would also be beneficial, as when I was starting up the first steps were pretty daunting and I was looking for tutorials to help bridge the gaps when kicking off my first project.

Good idea, but would defer this to some later point, when we already have all the docs moved and published. The docs repo will then also have its own GitHub project and issue list, so we'll have a good place to keep track of ideas like this too.
For now, here's a list of the things that I think need to be tackled so we can do a full docs switch, not necessarily in order:

Move img and en from root into a Pages subfolder, so we don't clutter the root directory with content specific folders as we add more later on.
Figure out how images and links work, and how they can be linked with a relative URL.
Fix the images and links in all pages.
Decide on a good base theme / template to use and customize.
Integrate the base theme.
Figure out which special templates are required, for example for the home page
Adjust the default template with footer support.
Adjust the default template with sidebar support.
Transfer the repository to the AdamsLair organization account.
Consider renaming the repo to duality-docs.
Just before release, pull all the latest Wiki pages into the new repo again to not miss recent changes. Make sure to fix images and links as done before.

@BobGneu Feel free to add any points that you have on your radar, or address any of them. This issue is somewhat big, so I think it makes sense to at some point just make the cut and turn it into a team effort. In that case, just let me know that you're ready for the switch and we'll do the repo transfer.

Let's do the transfer. The repo can be renamed upon transfer and from that point things will be more manageable.
Images are referenced as with standard html, relative or absolute paths are interchangeable. I already did the work to validate this on the home page. It should be pretty straight forward to correct the other images. Once we get the repo transferred we can use the issues system to track the notes above.

I'll be off for a week, but will get back to you as soon as I'm back 👍

One side note, in order to transfer ownership I will need the permission relating to creating repositories within the AdamsLair space.
https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/

Repo renamed.

Moved img and en into pages sub directory.

In the future, when making bulleted lists you can make them into checkboxes to simplify and track updates. All checkboxes are tracked in the first post of a PR and Issue. They show up on the issue listing.

Images can be referenced using markdown similar to the following
Inline Relative / Exact
![Debug Game Break](../../img/GettingStarted/RunGameButton.png)
![Debug Game Break]({{site.baseurl}}/pages/img/GettingStarted/RunGameButton.png)

Deferred Relative
![Debug Game Break][DebugGameBreak]
![Debug Game Break][DebugGameBreakDirect]

[DebugGameBreak]: ../../img/GettingStarted/RunGameButton.png
[DebugGameBreakDirect]: {{site.baseurl}}/pages/img/GettingStarted/RunGameButton.png

Alternatively, we can make image references.
<img src="{{site.baseurl}}/pages/img/GettingStarted/RunGameButton.png" />

In terms of the layout, Having a thin layout is not going to work with many of the code samples, as anything deeper than about 30 characters is going to require scrolling or wordwrap is going to be a mess, stretching things out.

In looking at a few of the other similar sites ~ 740 - 800px of width seems to provide enough space for code examples.
We can create a template with a header, side menu and footer. Given that we have full HTML access we can even position the footer and headers at the top and bottom of any given window. No need for JQuery or anything. Mock up the layout you would like to see and I'll give it a go.

Repo renamed.
Moved img and en into pages sub directory.

👍

Images can be referenced using markdown similar to the following

I think we should stick to the markdown way. I don't have a clear favorite among the variants, but would vaguely prefer relative inline paths.

In terms of the layout, Having a thin layout is not going to work with many of the code samples, as anything deeper than about 30 characters is going to require scrolling or wordwrap is going to be a mess, stretching things out.

In looking at a few of the other similar sites ~ 740 - 800px of width seems to provide enough space for code examples, though its still pretty tight.

We can create a template with a header, side menu and footer. Given that we have full HTML access we can even position the footer and headers at the top and bottom of any given window. No need for JQuery or anything. Mock up the layout you would like to see and I'll give it a go.

Do we have a proper css file to work with? Might as well go for a responsive design and use the full width up to a max value for big screens, and adjust the sidebar for small screens below a min width. Could turn it into a "site header" instead in those cases.

Let's do the transfer.

Great, let's do it. I think the easiest way would be to transfer it to me, and I'll forward it to the AdamsLair org.

Initiated the transfer to you.

Transferred 👍 Here's the new repo link.
ToDo

Set up labels on the new docs repo, probably similar to the ones in the main Duality repo.
Transfer all remaining ToDo items into issues in the new docs repo, but keep this one open until first release.
Fix the images and links in all pages.
Decide on a good base theme / template to use and customize.
Integrate the base theme.
Figure out which special templates are required, for example for the home page
Adjust the default template with footer support.
Adjust the default template with sidebar support.
Transfer the repository to the AdamsLair organization account.
Consider renaming the repo to duality-docs.
Just before release, pull all the latest Wiki pages into the new repo again to not miss recent changes. Make sure to fix images and links as done before.

Labels Created.

images ticket created.
https://github.com/AdamsLair/duality-docs/issues/2

Theme ticket created
https://github.com/AdamsLair/duality-docs/issues/3

I summed up the template based notes together in
AdamsLair/duality-docs#3 and opened up a ticket for pulling in the latest from the wiki. https://github.com/AdamsLair/duality-docs/issues/4

I elaborated as best I could, Please feel free to edit them further.

Nice work on the issues! The template one is actually not what I meant, but still a good idea the way you read it. Updated ToDo overview:
ToDo

Adjust labels to match naming (where appropriate) and colors from the main repo and follow a consistent color scheme overall.
Transfer remaining ToDo items into issues in the new docs repo, but keep this one open until first release.
Fix the remaining images and links on pages that were not yet cleaned up.
Decide on a good base theme / template to use, then integrate it to start iterating on.

As part of this, figure out which special jekyll page templates are required, for example for the home page.

Adjust the default template with footer support.
Adjust the default template with sidebar support.
Just before release, pull all the latest Wiki pages into the new repo again to not miss recent changes. Make sure to fix images and links as done before.

Note that we both had been added as collaborators accidentally during the transfer. I removed us again, so access rights are now again managed via teams, but this also means that you won't be able to adjust the labels, since you're no longer a project admin. I'll pick up that one.

Progress

Adjusted labels to use similar color-based categorization as in the main repo, but removed and renamed labels where applicable.

Immediate ToDo

Transfer remaining ToDo items into issues in the new docs repo, but keep this one open until first release.
Fix the remaining images and links on pages that were not yet cleaned up.
Decide on a good base theme / template to use, then integrate it to start iterating on.

As part of this, figure out which special jekyll page templates are required, for example for the home page.

Adjust the default template with footer support.
Adjust the default template with sidebar support.
Just before release, pull all the latest Wiki pages into the new repo again to not miss recent changes. Make sure to fix images and links as done before.

Created a First Release milestone on the docs repo, which contains all issues that need to be addressed in order to release.
cc @AdamsLair/duality-contributors for everyone who would be interested in joining the docs transfer with a PR or two.

Moved all remaining docs issues from the main repo to the docs repo.

Closing this, as all open work have been moved to the new docs repo and first release milestone.

authors: BobGneu htw5295 ilexp

repo: AdamsLair/duality


text:
Filtering Log Still Not Fixed After 5 Years

The design of Adguard's Filtering Log doesn't recognise when parts of a webwpage are blocked by Cosmetic/Element hiding rules, they can be in a subscribed to Filter Lister or a Custom User Created Rule.
This badly designed Filtering Log makes it extremely difficult to determine what is blocking parts of a webpage.
This should NOT be the case, ALL BLOCKED ITEMS should be reported.
This is in a fact a Technical Issue which is created by the badly designed Filtering Logs.
Adguard have stubbornly refused to acknowledge there is a problem created by the Filtering Logs.
This was raised 5 years ago on the Github Forums
Here's the link: https://github.com/AdguardTeam/CoreLibs/issues/180
The Adguard Filtering Log is still NOT fixed after 5 years.
It is absolutely disgusting and very shameful conduct that this was raised on Github 5 very, very long years ago and Adguard have done absolutely NOTHING TO FIX THEIR FILTERING LOGS.
With various other ad blockers such as ublock Origin, the filtering logs do clearly show when a Cosmetic or User/Custom rule is in effect.
When Blocked Items are NOT REPORTED AT ALL, do you understand that this makes discovering the source of a webpage problem an extremely time consuming, difficult and painstaking process.
To discover the source of the problem I literally had to spend several hours of my valuable time disabling each and every single Adguard function one at a time and then reloading the webpage until I discovered the source of the problem.
It is absolutely disgusting and quite shameful that after 5 very, very long years Adguard has still done absolutely NOTHING about this.

Addressed it here: https://github.com/AdguardTeam/CoreLibs/issues/1784#issuecomment-1649284401

authors: ameshkov jputting

repo: AdguardTeam/CoreLibs


text:
PhoneNumberInput - fix clearing logic

При нажатии иконки очистки должен стираться только номер телефона, код страны должен оставаться

Иконка очистки убрана из компонента, добавлена дефолтная иконка при отсутствии совпадений с кодами стран. Согласовано с @Eldar-Gyzyev

authors: Parasjona syros

repo: AdmiralDS/react-ui