Willing to help

I really appreciate the hard work you (and of course the sqlite-jdbc guys) have put into this project. I would like to help you getting up to date with SQLite and sqlite-jdbc in case you don't have the time for it, but I'm not used to the build infrastructure yet and to the open issues which must be resolved to put out a new release.
Could you elaborate where to start?
Chris

Hello @INPUTsys-Chris,
Indeed, I'm quite busy at the time, and I'm late by a good number of version.
Build instructions are located in the README_BUILD.md file. But I'm not sure if they are perfectly up-to-date.
To sum up, tools listed at the top are required. Most of the build will happen in docker container (for cross-compilation), the process will download images that can take a lot of space on your system. Building takes also time (~30 minutes) !
Building is quite easy though:

export your JAVA_HOME variable
check / update version in the VERSION and pom.xml files (version of SqliteMC and SQLite must be coherent with the one listed at  https://github.com/utelle/SQLite3MultipleCiphers/releases)
run make all

The difficult part is when some of the native build are failing;
Each native build can be manually triggered by running the make target that correspond. The list is available here: https://github.com/Willena/sqlite-jdbc-crypt/blob/82c7fb024254b6fc1393721ae33df2299d81abf0/Makefile#L151
Synchronization with the upstream is "as simple as a git merge". We just need to be careful with modification that can affect some of our own changes. Usually the synchronization with the upstream is the last thing I do (unless there is a major commit). From what I've seen (at the time of writing this comment) the 70+ commit late from upstream are not that important.
I wish I can automate things a little bit more, but for now most of the actions are manually done. The last time I worked was on the bugfix/ci-improve branch trying to fix the CI jobs (https://github.com/Willena/sqlite-jdbc-crypt/actions/runs/6373825471/job/17297874282)
Thanks a lot for your help.

Hi @Willena
Thanks for the detailed answer. I'll have a look and get back to you.
I guess I can close this since I'll either submit PRs or open new tickets


Sped up the submission page autofill when numerous compounds are missing

Summary Change Description
Made dramatic running time improvements to the autofill-only mode of the build-a-submission page (when numerous compounds don't exist in the database).
It turns out that there were a number of aspects of the code that, when these combined changes are implemented, there is a dramatic improvement to data-specific lag (e.g. when there are numerous repeated lookups of missing compounds).
One thing I learned during this effort is that pandas' iterrows method is very slow.  So when the peak annotations file is large (many samples and many compounds), the unicorr format has the drawback that it hits pandas' iterrows pretty hard.  The time that pandas spends instantiating pd.Series objects becomes rather large.  I had initially just mimicked existing code when I utilized iterrows, so I imagine that a future refactor could address the iterrows usage later more holistically.
Combine that with the fact that Compound.compound_matching_name_or_synonym has a worst-case running time when the compound is not found, so when the peak annotations file has numerous not-before-loaded compounds, that method also hits the overall running time pretty hard.
Lastly, you get a not insignificant running time hit when the PeakAnnotationsLoader buffers all those excessive exceptions.  For the purposes of the autofill-only mode, we don't need those exceptions.  We only need them in validation mode, so I did 2 things to address this aspect:

Skip compounds we've seen before (so not failed lookup or exception occurs.
Added an argument to the methods involved to turn off error buffering.

It's probably not necessary to skip the exception buffering given the skipping of already seen compound strings, but it did improve running time a noticeable amount.
It's also notable that, after the autofill step, the user will likely fill in the missing information in the Compounds sheet, so even if we buffer errors in the validation step, there shouldn't be (as many) missing compounds, so the problem should mostly go away at validation anyway.  Besides, in the validation step, we're only going to validate the study doc, so we won't be hitting these repeated exceptions anyway in the PeakAnnotationsLoader, so even if they don't fill the compounds sheet in, we won't hit this lag in the validation step.
I also added a debug print that prints the compounds added to the compounds sheet.
The files which demonstrate the slowness are:

col013a_negative_cor.xlsx
col013a_pos-highmz_cor.xlsx

Combined, they now get processed in about 30 seconds, and the vast majority of that is simply reading the files (now).
Affected Issues/Pull Requests

Resolves no documented issue.  See the Summary Change Description above)
Merges into PR #1083
Next PR: #1085

Review Notes

See comments in-line.
Checklist

This pull request will be merged once the following requirements are met.  The
author and/or reviewers should uncheck any unmet requirements:

Review requirements

Minimum approvals: 1
No changes requested
All blocking issues resolved by reviewers
Specific reviewers: @add_username_here

Review period: 2 days

Associated issue/pull request requirements:

[x] All requirements in affected issues marked "resolved" are satisfied
[x] All required pull requests are merged (or none)

Basic requirements

[x] All linters pass
[x] All tests pass
[x] All conflicts resolved

Overhead requirements

[x] New/changed method tests implemented/updated (or no change)
[ ] Updated Unreleased section of changelog.md (or no change)
[x] Migrations created & committed (or no change)

Looks like a nice speedup. It does strike me as something that the Django cache mechanism could handle: https://docs.djangoproject.com/en/5.0/topics/cache/#basic-usage, but this is a simple one-off solution and seems to work well.

I had considered using the Django cache. I started looking at applying it to the compound method, but eventually dismissed it. The lookups that were taking all the time were the ones resulting in None. While caching can store and return None, those lookups are only ever needed during the life of the current process. The website doesn't ever look up non-existent values and in the next load, when the missing compound is included, you wouldn't want it to return None. I guess I could have cleared the cache at the end of the script, but regardless, the a lot of the speed up came from other things, such as using vectorized operations instead of iterrows, and caching wouldn't have sped that up.
I could create an issue for temporary caching instead of using a dict for the non-existent compound lookup if you want. We'd just have to be careful that that cache is emptied by the end of the life of the script, at least for the None values, though to be honest, I'm not a big fan of caching when there's not a strategy in place to prevent stale cached values from being returned. HierCachedModel does that, but it doesn't support None.


Added Squonk-facts

Truly a fantastic creature.

skelpdar:mystory is now one commit ahead of floridop:master with the desired changes, in a merge-able way. It seems that github closed this PR when I did a git reset at some point, but I'm reopening it now.

Hi @Skelpdar
I do not understand why you did not want to perform a merge, can you clarify? Maybe the slides are not clear?
git reset should only be used to undo changes on your local branch, before you push it.
You can read about this in slide 110 of Tutorial 5.


Add display of buffer.id in print solutions in LaTeX form

I have been using this project recently and found that adding buffer.id to the diagram is very convenient for me to visually view the memory life cycle.

Looks good, thank you!


How to set start angle for progress circle?

How can I set start angle for progress circle? I don't see a prop for that.

You could try setting a rotation style.
style={{     transform: [       { rotateZ: '180deg' },     ],   }}


Recipe App

Is your feature request related to a problem? Please describe.
Finding new recipes everyday is a tedious task
Describe the solution you'd like
Therefore I have made a website using ReactJs which will have some preloaded recipes and the user can also search for new recipes of his/her choice
Steps Followed✅

[x] Is your feature request related to a problem? Please describe.
[x] Describe the solution you'd like
[x] Describe alternatives you've considered
[x] Additional context

Code of Conduct✅

[x] I agree to follow this project's Code of Conduct.
[x] I checked the current issues for duplicate problems.
[x] I have gone through project README.

this type of project already exists, also we don't accept react projects as of now.


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
13 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
10 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
19 seconds
clair-scan

✅ Succeeded
13 seconds
sbom-json-check

✅ Succeeded
18 seconds
sanity-optional-label-check

✅ Succeeded
17 seconds
sanity-label-check

✅ Succeeded
6 seconds
show-summary


Use correct error type for timeout error silencing

Fix silenced error type for OpLogDistributedReceptionist.sendAckOps
Motivation:
The error type the was silenced by #996 was actually wrong, this fixes it.

Sorry, I should have double checked.

Thanks :)


Fix GaugeConfig StartAngle & EndAngle to double.

These parameters should be double and not of the type int.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: illumen sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[    1.819734] scare-pigeon 13e10000.host1x:vi-thi@15f00000: initialized
[    1.820432] scare-pigeon 14b00000.isp-thi: initialized
[    1.832171] pva 16000000.pva0: initialized
[    1.864368] pva 16800000.pva1: initialized
[    1.895922] nvdla 15880000.nvdla0: initialized
[    1.926963] nvdla 158c0000.nvdla1: initialized
[    1.931138] tegra-slvs-ec 15ac0000.slvs-ec: initialized
[    1.931408] tegra-slvs-ec 15ac0000.slvs-ec: no streams defined
[    1.931456] tegra-slvs-ec 15ac0000.slvs-ec: failed to init SLVS media controller (-19)
[    1.931550] tegra-slvs-ec 15ac0000.slvs-ec: probed
[    1.932757] tegradccommon 15200000.dc_common: host1x channel mapped
[    1.932825] tegradccommon 15200000.dc_common: dc_common syncpt # 1 allocated
[    1.932941] tegradccommon 15200000.dc_common: dma mapping done
[    1.934494] tegradc 15200000.nvdisplay: disp0 connected to head0->/host1x/sor2
[    1.934606] generic_infoframe_type: 0x87
[    1.934775] tegradc 15200000.nvdisplay: DT parsed successfully
[    1.934868] tegradc 15200000.nvdisplay: Display dc.ffffff800be50000 registered with id=0
[    1.942151] tegra_nvdisp_bandwidth_register_max_config: max config iso bw = 15681600 KB/s
[    1.942215] tegra_nvdisp_bandwidth_register_max_config: max config EMC floor =<PHONE_NUMBER> Hz
[    1.942288] tegra_nvdisp_bandwidth_register_max_config: max config hubclk = 358400000 Hz
[    1.942691] tegradc 15200000.nvdisplay: vblank syncpt # 8 for dc 0
[    1.942748] tegradc 15200000.nvdisplay: vpulse3 syncpt # 9 for dc 0
[    1.944516] tegradc 15200000.nvdisplay: Bootloader disp_param detected. Detected mode: 640x480 (on 0x0mm) pclk=50347983
[    1.946860] tegra-adma 2930000.adma: Tegra210 ADMA driver registered 16 channels
[    1.947145] tegradc 15200000.nvdisplay: hdmi: invalid prod list prod_list_hdmi_board
[    1.947232] tegradc 15200000.nvdisplay: hdmi: tegra_hdmi_tmds_range_read(bd) failed
[    1.948383] tegra-fuse-burn 3820000.efuse:efuse-burn: Fuse burn driver initialized
[    1.949473] kfuse 3830000.kfuse: initialized
[    1.952021] tegradc 15200000.nvdisplay: probed
[    1.960825] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.964630] 3100000.serial: ttyTHS0 at MMIO 0x3100000 (irq = 50, base_baud = 0) is a TEGRA_UART
[    1.966170] 3110000.serial: ttyTHS1 at MMIO 0x3110000 (irq = 51, base_baud = 0) is a TEGRA_UART
[    1.967289] 3140000.serial: ttyTHS4 at MMIO 0x3140000 (irq = 52, base_baud = 0) is a TEGRA_UART
[    4.459163] console [ttyTCU0] enabled
[    4.459746] [drm] Initialized
[    4.459821] Console: switching to colour frame buffer device 80x30
[    4.472286] tegradc 15200000.nvdisplay: fb registered
[    4.477696] gpio tegra-gpio wake71 for gpio=98(M:2)
[    4.482933] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
[    4.488292] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
[    4.490422] brd: module loaded
[    4.498681] loop: module loaded
[    4.500216] tegra_profiler: version: 1.134, samples/io: 47/26
[    4.506420] tegra_profiler: auth: init
[    4.510229] nct1008_nct72 4-004c: starting parse dt
[    4.510638] THERMAL EST: found 3 subdevs
[    4.510645] THERMAL EST num_resources: 0
[    4.510652] [THERMAL EST subdev 0]
[    4.510689] [THERMAL EST subdev 1]
[    4.510695] [THERMAL EST subdev 2]
[    4.510707] THERMAL EST: Found 2 profiles, default profile is quiet
[    4.511220] thermal thermal_zone7: Registering thermal zone thermal_zone7 for type thermal-fan-est
[    4.511225] THERMAL EST: thz register success.
[    4.511468] THERMAL EST: end of probe, return err: 0
[    4.512156] Parent Clock set for DC plld3
[    4.517141] ufs_tegra 2450000.ufshci: freq-table-hz property not specified
[    4.517156] ufs_tegra 2450000.ufshci: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
[    4.518126] ufs_tegra 2450000.ufshci: wakeup init done, cdirq 459
[    4.518140] gpio tegra-gpio-aon wake25 for gpio=32(EE:0)
[    4.532508] scsi host0: ufshcd
[    4.544253] hisi_sas: driver version v1.6
[    4.550480] libphy: Fixed MDIO Bus: probed
[    4.551204] tun: Universal TUN/TAP device driver, 1.6
[    4.551210] tun: (C) 1999-2004 Max Krasnyansky<EMAIL_ADDRESS>[    4.552770] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    4.552774] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    4.552854] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[    4.552858] igb: Copyright (c) 2007-2014 Intel Corporation.
[    4.552931] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
[    4.552936] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    4.553004] Intel(R) 10GbE PCI Express Linux Network Driver - version 4.6.4
[    4.553009] Copyright(c) 1999 - 2017 Intel Corporation.
[    4.559010] eqos 2490000.ether_qos: Setting local MAC: 0 4 4b e5 78 73
[    4.559163] libphy: dwc_phy: probed
[    4.562686] PPP generic driver version 2.4.2
[    4.562929] PPP BSD Compression module registered
[    4.562936] PPP Deflate Compression module registered
[    4.562955] PPP MPPE Compression module registered
[    4.562961] NET: Registered protocol family 24
[    4.563030] usbcore: registered new interface driver r8152
[    4.563089] usbcore: registered new interface driver asix
[    4.563143] usbcore: registered new interface driver ax88179_178a
[    4.563204] usbcore: registered new interface driver cdc_ether
[    4.563254] usbcore: registered new interface driver net1080
[    4.563298] usbcore: registered new interface driver cdc_subset
[    4.563350] usbcore: registered new interface driver zaurus
[    4.563422] usbcore: registered new interface driver cdc_ncm
[    4.563794] VFIO - User Level meta-driver version: 0.3
[    4.570063] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.570083] ehci-pci: EHCI PCI platform driver
[    4.570137] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    4.570148] ohci-pci: OHCI PCI platform driver
[    4.570196] ohci-platform: OHCI generic platform driver
[    4.573723] tegradc 15200000.nvdisplay: hdmi: tmds rate:50349K prod-setting:prod_c_hdmi_0m_54m
[    4.574482] tegradc 15200000.nvdisplay: hdmi: get RGB quant from REG programmed by BL.
[    4.574496] tegradc 15200000.nvdisplay: hdmi: BL set VIC 0
[    4.574502] tegradc 15200000.nvdisplay: hdmi: get YCC quant from REG programmed by BL.
[    4.578987] tegra-xusb 3610000.xhci: USB2 port 0 has OTG_CAP
[    4.578995] tegra-xusb 3610000.xhci: USB3 port 2 has OTG_CAP
[    4.582255] Could not get extcon-dev /xhci@3610000:id(0)
[    4.586237] usbcore: registered new interface driver uas
[    4.586310] usbcore: registered new interface driver usb-storage
[    4.586417] usbcore: registered new interface driver usbserial
[    4.587603] extcon-disp-state external-connection:disp-state: cable 48 state 1
[    4.587610] Extcon AUX2(HDMI) enable
[    4.588810] Could not get extcon-dev /host1x/nvdisplay@15210000:typec0(0)
[    4.589621] Could not get extcon-dev /host1x/nvdisplay@15220000:typec1(1)
[    4.591486] tegra-xudc-new 3550000.xudc: PMQOS CPU boost enabled
[    4.591580] Could not get extcon-dev /xudc@3550000:vbus(0)
[    4.594790] ucsi_ccg 1-0008: FW1 Version: gn v12.05, [Base <IP_ADDRESS>7]
[    4.594801] ucsi_ccg 1-0008: FW2 Version: gn v12.05, [Base <IP_ADDRESS>7]
[    4.595945] ucsi_ccg 1-0008: fw_mode: 2
[    4.595953] ucsi_ccg 1-0008: fw1_invalid: 0
[    4.595959] ucsi_ccg 1-0008: fw2_invalid: 0
[    4.595965] ucsi_ccg 1-0008: silicon_id: 0x1f00
[    4.596217] ucsi_ccg 1-0008: typec-port0 extcon dev created
[    4.596483] ucsi_ccg 1-0008: typec-port1 extcon dev created
[    4.596646] ucsi_ccg 1-0008: typec-pd extcon dev created
[    4.596818] gpio tegra-gpio-aon wake48 for gpio=10(BB:2)
[    4.598693] ucsi_ccg 1-0008: [typec-port0] Cable state:1, cable id:1
[    4.602565] ucsi_ccg 1-0008: HPI Command Success.
[    4.605233] ucsi_ccg 1-0008: HPI Command Success.
[    4.605258] ucsi_ccg 1-0008: ucsi_ccg_init: complete
[    4.606214] mousedev: PS/2 mouse device common for all mice
[    4.606361] usbcore: registered new interface driver xpad
[    4.725431] max77686-rtc max77620-rtc: rtc core: registered max77620-rtc as rtc0
[    4.727065] Wake73 for irq=42
[    4.728517] rtc rtc1: alarm rtc device
[    4.728538] tegra_rtc c2a0000.rtc: rtc core: registered c2a0000.rtc as rtc1
[    4.728566] tegra_rtc c2a0000.rtc: Tegra internal Real Time Clock
[    4.728827] i2c /dev entries driver
[    4.733781] max77620-power max20024-power: Event recorder REG_NVERC : 0x44
[    4.743666] tegra-thermal-throttle bthrot_cdev: clk:cpu max:2265600000, min:115200000 steps:28
[    4.798474] tegra-thermal-throttle bthrot_cdev: clk:gpu max:1377000000, min:114750000 steps:13
[    4.798532] tegra-thermal-throttle bthrot_cdev: cdev:skin-balanced clk:0:cpu off:0 slope-adj:200
[    4.798539] tegra-thermal-throttle bthrot_cdev: cdev:skin-balanced clk:1:gpu off:0 slope-adj:400
[    4.798755] tegra-thermal-throttle bthrot_cdev: cdev:skin-balanced max_state:56 cutoff:0
[    4.798865] tegra-thermal-throttle bthrot_cdev: cdev:gpu-balanced clk:0:cpu off:0 slope-adj:400
[    4.798874] tegra-thermal-throttle bthrot_cdev: cdev:gpu-balanced clk:1:gpu off:0 slope-adj:400
[    4.799220] tegra-thermal-throttle bthrot_cdev: cdev:gpu-balanced max_state:52 cutoff:1
[    4.799292] tegra-thermal-throttle bthrot_cdev: cdev:cpu-balanced clk:0:cpu off:0 slope-adj:200
[    4.799301] tegra-thermal-throttle bthrot_cdev: cdev:cpu-balanced clk:1:gpu off:365500000 slope-adj:300
[    4.799655] tegra-thermal-throttle bthrot_cdev: cdev:cpu-balanced max_state:56 cutoff:0
[    4.799731] tegra-thermal-throttle bthrot_cdev: cdev:emergency-balanced clk:0:cpu off:38400000 slope-adj:10
[    4.799738] tegra-thermal-throttle bthrot_cdev: cdev:emergency-balanced clk:1:gpu off:25500000 slope-adj:10
[    4.800192] tegra-thermal-throttle bthrot_cdev: cdev:emergency-balanced max_state:2 cutoff:0
[    4.800276] tegra-thermal-throttle bthrot_cdev: cdev:aux-balanced clk:0:cpu off:0 slope-adj:400
[    4.800282] tegra-thermal-throttle bthrot_cdev: cdev:aux-balanced clk:1:gpu off:0 slope-adj:400
[    4.800573] tegra-thermal-throttle bthrot_cdev: cdev:aux-balanced max_state:52 cutoff:1
[    4.801399] FAN dev name: pwm-fan
[    4.801506] FAN:gpio request success.
[    4.801519] FAN: can't find tach_gpio
[    4.801532] pwm_fan_driver pwm-fan: Found 2 profiles, default profile is quiet
[    4.801599] pwm_fan_driver pwm-fan: cap state:4, cap pwm:255
[    4.801949] pwm_fan_driver pwm-fan: got pwm for fan. polarity is normal
[    4.801956] pwm_fan_driver pwm-fan: tach period: 1000
[    4.802326] pwm_fan_driver pwm-fan: index 0: pwm=0, rpm=0, rru=40, rrd=40, state:2
[    4.802334] pwm_fan_driver pwm-fan: index 1: pwm=77, rpm=1000, rru=2, rrd=2, state:2
[    4.802341] pwm_fan_driver pwm-fan: index 2: pwm=120, rpm=2000, rru=1, rrd=1, state:2
[    4.802346] pwm_fan_driver pwm-fan: index 3: pwm=160, rpm=3000, rru=1, rrd=1, state:2
[    4.802352] pwm_fan_driver pwm-fan: index 4: pwm=255, rpm=4000, rru=1, rrd=1, state:3
[    4.802358] pwm_fan_driver pwm-fan: index 5: pwm=255, rpm=5000, rru=1, rrd=1, state:3
[    4.802364] pwm_fan_driver pwm-fan: index 6: pwm=255, rpm=6000, rru=1, rrd=1, state:3
[    4.802370] pwm_fan_driver pwm-fan: index 7: pwm=255, rpm=7000, rru=1, rrd=1, state:4
[    4.802377] pwm_fan_driver pwm-fan: index 8: pwm=255, rpm=10000, rru=1, rrd=1, state:4
[    4.802384] pwm_fan_driver pwm-fan: index 9: pwm=255, rpm=11000, rru=1, rrd=1, state:4
[    4.803544] device-mapper: uevent: version 1.0.3
[    4.804119] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised<EMAIL_ADDRESS>[    4.821867] tegra194_cpufreq_probe: platform driver Initialization: pass
[    4.827045] cpuidle: Initializing cpuidle driver
[    4.839512] sdhci: Secure Digital Host Controller Interface driver
[    4.839514] sdhci: Copyright(c) Pierre Ossman
[    4.839516] sdhci-pltfm: SDHCI platform and OF driver helper
[    4.840846] sdhci-tegra 3460000.sdhci: Client registration for eMC Successful
[    4.842947] CMDQ: cmdq_platfm_init successful
[    4.843611] sdhci-tegra 3400000.sdhci: Got CD GPIO
[    4.846769] sdhci-tegra 3400000.sdhci: Client registration for eMC Successful
[    4.848437] sdhci-tegra 3400000.sdhci: wakeup init done, cdirq 254
[    4.852921] tegra-se-elp 3ad0000.se_elp: tegra_se_elp_probe: complete
[    4.853839] tegra-se-nvhost 15810000.se: initialized
[    4.854971] tegra-se-nvhost 15810000.se: tegra_se_probe: complete
[    4.855730] tegra-se-nvhost 15820000.se: initialized
[    4.856686] tegra-se-nvhost 15820000.se: tegra_se_probe: complete
[    4.857259] tegra-se-nvhost 15830000.se: initialized
[    4.857731] tegra-se-nvhost 15830000.se: tegra_se_probe: complete
[    4.858231] tegra-se-nvhost 15840000.se: initialized
[    4.859042] tegra-se-nvhost 15840000.se: tegra_se_probe: complete
[    4.859234] hidraw: raw HID events driver (C) Jiri Kosina
[    4.860566] usbcore: registered new interface driver usbhid
[    4.860569] usbhid: USB HID core driver
[    4.865932] tegra186-cam-rtcpu bc00000.rtcpu: deferring, 14800000.isp is not probed
[    4.866903] tegra_aon c1a0000.aon: tegra aon driver probe OK
[    4.867299] tegra186-aondbg aondbg: aondbg driver probe() OK
[    4.867932] denver_knobs_init:MTS_VERSION:45309758
[    4.868115] tegra19x_actmon d230000.actmon: in actmon_register()...
[    4.868852] tegra19x_actmon d230000.actmon: initialization Completed for the device mc_all
[    4.869155] t19x_cache tegra-cache: probed
[    4.875278] misc nvmap: cvsram :dma coherent mem declare 0x0000000050000000,4194304
[    4.875288] misc nvmap: created heap cvsram base 0x0000000050000000 size (4096KiB)
[    4.877305] nvpmodel: initialized successfully
[    4.881821] trusty-virtio trusty:virtio: initializing
[    4.882049] trusty_ipc virtio0: vring0: va(pa)  ffffffc3d9da0000(0) qsz 32 notifyid 1
[    4.882056] trusty_ipc virtio0: vring1: va(pa)  ffffffc3d9da2000(0) qsz 32 notifyid 2
[    4.882190] trusty-virtio trusty:virtio: initializing done
[    4.882406] trusty_ipc virtio0: is online
[    4.882874] tegra-hda 3510000.hda: Override SDO lines to 4
[    4.883171] usbcore: registered new interface driver snd-usb-audio
[    4.891558] mmc0: SDHCI controller on 3460000.sdhci [3460000.sdhci] using ADMA 64-bit with 64 bit addr
[    4.894481] snd_hda_codec_hdmi hdaudioC0D5: HDMI: Unknown ELD version 0
[    4.895732] gpio tegra-gpio wake8 for gpio=55(G:7)
[    4.895787] mmc1: SDHCI controller on 3400000.sdhci [3400000.sdhci] using ADMA 64-bit with 64 bit addr
[    4.897280] input: tegra-hda-galen-t194 HDMI/DP,pcm=3 as /devices/3510000.hda/sound/card0/input0
[    4.897515] input: tegra-hda-galen-t194 HDMI/DP,pcm=7 as /devices/3510000.hda/sound/card0/input1
[    4.897728] input: tegra-hda-galen-t194 HDMI/DP,pcm=8 as /devices/3510000.hda/sound/card0/input2
[    4.897997] input: tegra-hda-galen-t194 HDMI/DP,pcm=9 as /devices/3510000.hda/sound/card0/input3
[    4.977292] mmc0: mmc_decode_ext_csd: CMDQ supported: depth: 31, cmdq_support: 1
[    4.989067] mmc0: periodic cache flush enabled
[    4.989101] mmc0: new HS400 Enhanced strobe MMC card at address 0001
[    4.989617] mmcblk0: mmc0:0001 HBG4a2 29.1 GiB
[    4.989933] mmcblk0boot0: mmc0:0001 HBG4a2 partition 1 8.00 MiB
[    4.990154] mmcblk0boot1: mmc0:0001 HBG4a2 partition 2 8.00 MiB
[    4.990362] mmcblk0rpmb: mmc0:0001 HBG4a2 partition 3 4.00 MiB
[    4.993094]  mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30 p31 p32 p33 p34 p35 p36 p37
��WARNING: pll_d3 has no dyn ramp
��[    5.620068] tegradc 15200000.nvdisplay: blank - powerdown
[    5.620209] nct1008_nct72 4-004c: !!!Found deprecated property!!!
[    5.620213] nct1008_nct72 4-004c: success parsing dt
[    5.620359] nct1008_nct72 4-004c: success in enabling tmp451 VDD rail
[    5.652952] nct1008_nct72 4-004c: LOC shutdown limit 107
[    5.654399] nct1008_nct72 4-004c: EXT shutdown limit 109
[    5.658552] extcon-disp-state external-connection:disp-state: cable 48 state 0
[    5.658555] Extcon AUX2(HDMI) disable
[    5.682623] tegra_nvdisp_handle_pd_disable: Powergated Head1 pd
[    5.683501] tegra_nvdisp_handle_pd_disable: Powergated Head0 pd
[    5.688402] nct1008_nct72 4-004c: initial LOC temp: 39000
[    5.688863] nct1008_nct72 4-004c: initial EXT temp: 51250
[    5.689921] nct1008_nct72 4-004c: hi_b:-10, lo_b:128
[    5.690704] nct1008_nct72 4-004c: nct1008_probe: initialized
[    5.706394] tegradc 15200000.nvdisplay: unblank
[    5.707145] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
[    5.707248] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
[    5.709327] Parent Clock set for DC plld3
[    5.713971] tegradc 15200000.nvdisplay: hdmi: tmds rate:154000K prod-setting:prod_c_hdmi_111m_223m
[    6.740913] gpio tegra-gpio wake12 for gpio=149(S:5)
[    6.834738] OPE platform probe
[    6.834877] OPE platform probe successful
[    6.964238] tegra-asoc: sound: ADMAIF1 <-> ADMAIF1 mapping ok
[    6.964354] tegra-asoc: sound: ADMAIF2 <-> ADMAIF2 mapping ok
[    6.964450] tegra-asoc: sound: ADMAIF3 <-> ADMAIF3 mapping ok
[    6.964546] tegra-asoc: sound: ADMAIF4 <-> ADMAIF4 mapping ok
[    6.964653] tegra-asoc: sound: ADMAIF5 <-> ADMAIF5 mapping ok
[    6.964752] tegra-asoc: sound: ADMAIF6 <-> ADMAIF6 mapping ok
[    6.964863] tegra-asoc: sound: ADMAIF7 <-> ADMAIF7 mapping ok
[    6.964983] tegra-asoc: sound: ADMAIF8 <-> ADMAIF8 mapping ok
[    6.965077] tegra-asoc: sound: ADMAIF9 <-> ADMAIF9 mapping ok
[    6.965178] tegra-asoc: sound: ADMAIF10 <-> ADMAIF10 mapping ok
[    6.965295] tegra-asoc: sound: ADMAIF11 <-> ADMAIF11 mapping ok
[    6.965404] tegra-asoc: sound: ADMAIF12 <-> ADMAIF12 mapping ok
[    6.965509] tegra-asoc: sound: ADMAIF13 <-> ADMAIF13 mapping ok
[    6.965633] tegra-asoc: sound: ADMAIF14 <-> ADMAIF14 mapping ok
[    6.965738] tegra-asoc: sound: ADMAIF15 <-> ADMAIF15 mapping ok
[    6.965814] tegra-asoc: sound: ADMAIF16 <-> ADMAIF16 mapping ok
[    6.965909] tegra-asoc: sound: ADMAIF17 <-> ADMAIF17 mapping ok
[    6.966011] tegra-asoc: sound: ADMAIF18 <-> ADMAIF18 mapping ok
[    6.966089] tegra-asoc: sound: ADMAIF19 <-> ADMAIF19 mapping ok
[    6.966161] tegra-asoc: sound: ADMAIF20 <-> ADMAIF20 mapping ok
[    7.000781] input: tegra-snd-t19x-mobile-rt565x Headset Jack as /devices/sound/sound/card1/input4
[    7.001920] u32 classifier
[    7.001922]     Actions configured
[    7.001979] Initializing XFRM netlink socket
[    7.002436] NET: Registered protocol family 10
[    7.003026] NET: Registered protocol family 17
[    7.003044] NET: Registered protocol family 15
[    7.003080] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    7.003159] Bluetooth: RFCOMM socket layer initialized
[    7.003180] Bluetooth: RFCOMM ver 1.11
[    7.003185] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    7.003190] Bluetooth: HIDP socket layer initialized
[    7.003204] 9pnet: Installing 9P2000 support
[    7.003251] Key type dns_resolver registered
[    7.003440] Registered cp15_barrier emulation handler
[    7.003456] Registered setend emulation handler
[    7.004951] registered taskstats version 1
[    7.005428] tegra-pcie-dw 14180000.pcie: Setting init speed to max speed
[    7.006302] OF: PCI: host bridge /pcie@14180000 ranges:
[    7.006319] OF: PCI:    IO 0x38100000..0x381fffff -> 0x38100000
[    7.006343] OF: PCI:   MEM 0x1b40000000..0x1bffffffff -> 0x40000000
[    7.006348] OF: PCI:   MEM 0x1800000000..0x1b3fffffff -> 0x1800000000
[    7.518874] tegra-pcie-dw 14180000.pcie: link is down
[    7.519090] tegra-pcie-dw 14180000.pcie: PCI host bridge to bus 0000:00
[    7.519113] pci_bus 0000:00: root bus resource [bus 00-ff]
[    7.519119] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0x38100000-0x381fffff])
[    7.519124] pci_bus 0000:00: root bus resource [mem 0x1b40000000-0x1bffffffff] (bus address [0x40000000-0xffffffff])
[    7.519127] pci_bus 0000:00: root bus resource [mem 0x1800000000-0x1b3fffffff pref]
[    7.519624] iommu: Adding device 0000:00:00.0 to group 61
[    7.519987] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    7.520008] pci 0000:00:00.0: Max Payload Size set to  256/ 256 (was  256), Max Read Rq  512
[    7.520243] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
[    7.520748] iommu: Removing device 0000:00:00.0 from group 61
[    7.522050] tegra-pcie-dw 14180000.pcie: PCIe link is not up...!
[    7.522642] tegra-pcie-dw 14100000.pcie: Setting init speed to max speed
[    7.523468] OF: PCI: host bridge /pcie@14100000 ranges:
[    7.523482] OF: PCI:    IO 0x30100000..0x301fffff -> 0x30100000
[    7.523488] OF: PCI:   MEM 0x1230000000..0x123fffffff -> 0x40000000
[    7.523515] OF: PCI:   MEM 0x1200000000..0x122fffffff -> 0x1200000000
[    7.631553] tegra-pcie-dw 14100000.pcie: link is up
[    7.631880] tegra-pcie-dw 14100000.pcie: PCI host bridge to bus 0001:00
[    7.631886] pci_bus 0001:00: root bus resource [bus 00-ff]
[    7.631893] pci_bus 0001:00: root bus resource [io  0x100000-0x1fffff] (bus address [0x30100000-0x301fffff])
[    7.631897] pci_bus 0001:00: root bus resource [mem 0x1230000000-0x123fffffff] (bus address [0x40000000-0x4fffffff])
[    7.631900] pci_bus 0001:00: root bus resource [mem 0x1200000000-0x122fffffff pref]
[    7.632240] iommu: Adding device 0001:00:00.0 to group 61
[    7.633706] iommu: Adding device 0001:01:00.0 to group 62
[    7.644538] pci 0001:00:00.0: BAR 14: assigned [mem 0x1230000000-0x12300fffff]
[    7.644543] pci 0001:00:00.0: BAR 13: assigned [io  0x100000-0x100fff]
[    7.644561] pci 0001:01:00.0: BAR 6: assigned [mem 0x1230000000-0x123000ffff pref]
[    7.644565] pci 0001:01:00.0: BAR 5: assigned [mem 0x1230010000-0x12300101ff]
[    7.644631] pci 0001:01:00.0: BAR 4: assigned [io  0x100000-0x10000f]
[    7.644695] pci 0001:01:00.0: BAR 0: assigned [io  0x100010-0x100017]
[    7.644721] pci 0001:01:00.0: BAR 2: assigned [io  0x100018-0x10001f]
[    7.644746] pci 0001:01:00.0: BAR 1: assigned [io  0x100020-0x100023]
[    7.644806] pci 0001:01:00.0: BAR 3: assigned [io  0x100024-0x100027]
[    7.644834] pci 0001:00:00.0: PCI bridge to [bus 01-ff]
[    7.644838] pci 0001:00:00.0:   bridge window [io  0x100000-0x100fff]
[    7.644856] pci 0001:00:00.0:   bridge window [mem 0x1230000000-0x12300fffff]
[    7.644872] pci 0001:00:00.0: Max Payload Size set to  256/ 256 (was  256), Max Read Rq  512
[    7.644963] pci 0001:01:00.0: Max Payload Size set to  256/ 512 (was  128), Max Read Rq  512
[    7.645316] pcieport 0001:00:00.0: Signaling PME through PCIe PME interrupt
[    7.645319] pci 0001:01:00.0: Signaling PME through PCIe PME interrupt
[    7.646450] ahci 0001:01:00.0: AHCI 0001.0000 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
[    7.646519] ahci 0001:01:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
[    7.647271] scsi host1: ahci
[    7.647461] ata1: SATA max UDMA/133 abar m512@0x1230010000 port 0x1230010100 irq 563
[    7.647624] tegra-pcie-dw 14140000.pcie: Setting init speed to max speed
[    7.648425] OF: PCI: host bridge /pcie@14140000 ranges:
[    7.648438] OF: PCI:    IO 0x34100000..0x341fffff -> 0x34100000
[    7.648445] OF: PCI:   MEM 0x12b0000000..0x12bfffffff -> 0x40000000
[    7.648449] OF: PCI:   MEM 0x1280000000..0x12afffffff -> 0x1280000000
[    7.962691] ata1: SATA link down (SStatus 0 SControl 300)
[    8.164597] tegra-pcie-dw 14140000.pcie: link is down
[    8.164756] tegra-pcie-dw 14140000.pcie: PCI host bridge to bus 0003:00
[    8.164762] pci_bus 0003:00: root bus resource [bus 00-ff]
[    8.164783] pci_bus 0003:00: root bus resource [io  0x200000-0x2fffff] (bus address [0x34100000-0x341fffff])
[    8.164788] pci_bus 0003:00: root bus resource [mem 0x12b0000000-0x12bfffffff] (bus address [0x40000000-0x4fffffff])
[    8.164791] pci_bus 0003:00: root bus resource [mem 0x1280000000-0x12afffffff pref]
[    8.165225] iommu: Adding device 0003:00:00.0 to group 63
[    8.165424] pci 0003:00:00.0: PCI bridge to [bus 01-ff]
[    8.165461] pci 0003:00:00.0: Max Payload Size set to  256/ 256 (was  256), Max Read Rq  512
[    8.165652] pcieport 0003:00:00.0: Signaling PME through PCIe PME interrupt
[    8.166093] iommu: Removing device 0003:00:00.0 from group 63
[    8.167372] tegra-pcie-dw 14140000.pcie: PCIe link is not up...!
[    8.194264] tegra-pcie-dw 141a0000.pcie: Setting init speed to max speed
[    8.228132] OF: PCI: host bridge /pcie@141a0000 ranges:
[    8.228151] OF: PCI:    IO 0x3a100000..0x3a1fffff -> 0x3a100000
[    8.228160] OF: PCI:   MEM 0x1f40000000..0x1fffffffff -> 0x40000000
[    8.228164] OF: PCI:   MEM 0x1c00000000..0x1f3fffffff -> 0x1c00000000
[    8.351573] tegra-pcie-dw 141a0000.pcie: link is up
[    8.351867] tegra-pcie-dw 141a0000.pcie: PCI host bridge to bus 0005:00
[    8.351872] pci_bus 0005:00: root bus resource [bus 00-ff]
[    8.351878] pci_bus 0005:00: root bus resource [io  0x300000-0x3fffff] (bus address [0x3a100000-0x3a1fffff])
[    8.351883] pci_bus 0005:00: root bus resource [mem 0x1f40000000-0x1fffffffff] (bus address [0x40000000-0xffffffff])
[    8.351899] pci_bus 0005:00: root bus resource [mem 0x1c00000000-0x1f3fffffff pref]
[    8.352245] iommu: Adding device 0005:00:00.0 to group 63
[    8.353647] iommu: Adding device 0005:01:00.0 to group 64
[    8.404938] pci 0005:00:00.0: BAR 15: assigned [mem 0x1c00000000-0x1c000fffff 64bit pref]
[    8.404945] pci 0005:01:00.0: BAR 0: assigned [mem 0x1c00000000-0x1c00000fff 64bit pref]
[    8.405019] pci 0005:01:00.0: BAR 2: assigned [mem 0x1c00001000-0x1c00001fff 64bit pref]
[    8.405093] pci 0005:00:00.0: PCI bridge to [bus 01-ff]
[    8.405122] pci 0005:00:00.0:   bridge window [mem 0x1c00000000-0x1c000fffff 64bit pref]
[    8.405135] pci 0005:00:00.0: Max Payload Size set to  256/ 256 (was  256), Max Read Rq  512
[    8.405188] pci 0005:01:00.0: Max Payload Size set to  256/ 256 (was  128), Max Read Rq  512
[    8.405520] pcieport 0005:00:00.0: Signaling PME through PCIe PME interrupt
[    8.405523] pci 0005:01:00.0: Signaling PME through PCIe PME interrupt
[    8.456391] tegra-cbb 14040000.cv-noc: noc_secure_irq = 98, noc_nonsecure_irq = 97>
[    8.599946] extcon-disp-state external-connection:disp-state: cable 40 state 1
[    8.606992] Extcon HDMI: HPD enabled
[    8.610948] tegradc 15200000.nvdisplay: hdmi: plugged
[    8.617508] tegra194-isp5 14800000.isp: initialized
[    8.630934] tegra194-vi5 15c10000.vi: initialized
[    8.638794] tegra194-vi5 15c10000.vi: ep of_device is not enabled /host1x/vi@15c10000/ports/port@0/endpoint.
[    8.640510] tegra194-vi5 15c10000.vi: ep of_device is not enabled /host1x/vi@15c10000/ports/port@1/endpoint.
[    8.647727] tegra-xusb 3610000.xhci: USB2 port 0 has OTG_CAP
[    8.651238] tegra-xusb 3610000.xhci: USB3 port 2 has OTG_CAP
[    8.660086] tegra-xusb 3610000.xhci: extcon 0: ffffffc3da627400 id
[    8.664444] tegradc 15210000.nvdisplay: disp1 connected to head1->/host1x/sor
[    8.664701] tegra-xudc-new 3550000.xudc: PMQOS CPU boost enabled
[    8.664729] tegra-xudc-new 3550000.xudc: device count: 1
[    8.665685] tegra-xudc-new 3550000.xudc: vbus state: 1
[    8.665699] tegra-xudc-new 3550000.xudc: device mode on: 0
[    8.665858] tegra-xudc-new 3550000.xudc: active: 0 => 1
[    8.665867] tegra-xudc-new 3550000.xudc: Initialize boost_cpufreq work
[    8.666610] tegra186-cam-rtcpu bc00000.rtcpu: Trace buffer configured at IOVA=0xbff00000
[    8.667064] tegra-xusb 3610000.xhci: Firmware timestamp: 2018-03-29 14:24:42 UTC, Version: 60.05 release
[    8.667094] tegra-xusb 3610000.xhci: xHCI Host Controller
[    8.667106] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 1
[    8.668337] tegra-xusb 3610000.xhci: hcc params 0x0184ff25 hci version 0x110 quirks 0x00050810
[    8.668381] tegra-xusb 3610000.xhci: irq 472, io mem 0x03610000
[    8.668557] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    8.668560] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    8.668563] usb usb1: Product: xHCI Host Controller
[    8.668566] usb usb1: Manufacturer: Linux 4.9.140-l4t-r32.2+g3dcbed5d27df xhci-hcd
[    8.668568] usb usb1: SerialNumber: 3610000.xhci
[    8.668959] hub 1-0:1.0: USB hub found
[    8.668983] hub 1-0:1.0: 4 ports detected
[    8.669319] tegra-xusb 3610000.xhci: xHCI Host Controller
[    8.669326] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 2
[    8.669331] tegra-xusb 3610000.xhci: Host supports USB 3.1 Enhanced SuperSpeed
[    8.669448] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    8.669451] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    8.669454] usb usb2: Product: xHCI Host Controller
[    8.669456] usb usb2: Manufacturer: Linux 4.9.140-l4t-r32.2+g3dcbed5d27df xhci-hcd
[    8.669459] usb usb2: SerialNumber: 3610000.xhci
[    8.669762] hub 2-0:1.0: USB hub found
[    8.669802] hub 2-0:1.0: 4 ports detected
[    8.742165] tegra-ivc ivc-bc00000.rtcpu: region 0: iova=0xbfee0000-0xbfefffff size=131072
[    8.742513] tegra-ivc ivc-bc00000.rtcpu:echo@0: echo: ver=0 grp=1 RX[16x64]=0x1000-0x1480 TX[16x64]=0x1480-0x1900
[    8.742724] tegra-ivc ivc-bc00000.rtcpu:dbg@1: dbg: ver=0 grp=1 RX[1x384]=0x1900-0x1b00 TX[1x384]=0x1b00-0x1d00
[    8.742867] tegra-ivc ivc-bc00000.rtcpu:dbg@2: dbg: ver=0 grp=1 RX[1x8192]=0x1d00-0x3d80 TX[1x8192]=0x3d80-0x5e00
[    8.743185] tegra-ivc ivc-bc00000.rtcpu:ivccontrol@3: ivccontrol: ver=0 grp=1 RX[64x320]=0x5e00-0xae80 TX[64x320]=0xae80-0xff00
[    8.743272] tegra-ivc ivc-bc00000.rtcpu:ivccapture@4: ivccapture: ver=0 grp=1 RX[512x64]=0xff00-0x17f80 TX[512x64]=0x17f80-0x20000
[    8.743470] tegra186-cam-rtcpu bc00000.rtcpu: using cam RTCPU IRQ (69)
[    8.743472] tegra186-cam-rtcpu bc00000.rtcpu: tegra_camrtc_mon_create is successful
[    8.744364] tegra186-cam-rtcpu bc00000.rtcpu: firmware version cpu=rce cmd=5 sha1=cf2bef3ad10e437272857b76308abef8ffb80bda
[    8.744809] gpio tegra-gpio wake67 for gpio=48(G:0)
[    8.744866] gpio tegra-gpio-aon wake29 for gpio=36(EE:4)
[    8.744998] input: gpio-keys as /devices/gpio-keys/input/input5
[    8.779792] usb usb1: usb_suspend_both: status 0
[    8.780400] tegra_rtc c2a0000.rtc: setting system clock to 2019-11-29 14:49:21 UTC<PHONE_NUMBER>)
[    8.780901] mmcblk mmc0:0001: Card claimed for testing.
[    8.825980] bpmp: mounted debugfs mirror
[    8.831307] vdd-1v8-cvb: disabling
[    8.831311] vdd-1v8-sd: disabling
[    8.831313] vdd-epb-1v0: disabling
[    8.831315] avdd-cam-2v8: disabling
[    8.831317] vdd-sata-1v5: disabling
[    8.831319] vdd-3v3-slt: disabling
[    8.831321] vdd-fan: disabling
[    8.831323] vdd_sys_en: disabling
[    8.831330] ALSA device list:
[    8.831333]   #0: tegra-hda-galen-t194 at 0x3518000 irq 68
[    8.831335]   #1: tegra-snd-t19x-mobile-rt565x
[    9.014270] tegradc 15210000.nvdisplay: parse_dp_settings: No dp-lt-settings node
[    9.022128] tegradc 15210000.nvdisplay: DT parsed successfully
[    9.027989] tegradc 15210000.nvdisplay: Display dc.ffffff800ffd0000 registered with id=1
[    9.035888] tegradc 15210000.nvdisplay: vblank syncpt # 15 for dc 1
[    9.042215] tegradc 15210000.nvdisplay: vpulse3 syncpt # 16 for dc 1
[    9.056270] tegradc 15210000.nvdisplay: probed
[    9.077582] tegradc 15210000.nvdisplay: fb registered
[    9.082583] hpd: state 7 (Takeover from bootloader), hpd 0, pending_hpd_evt 1
[    9.083803] tegradc 15220000.nvdisplay: disp2 connected to head2->/host1x/sor1
[    9.083842] tegradc 15220000.nvdisplay: parse_dp_settings: No dp-lt-settings node
[    9.083903] tegradc 15220000.nvdisplay: DT parsed successfully
[    9.083942] tegradc 15220000.nvdisplay: Display dc.ffffff80114d0000 registered with id=2
[    9.084157] tegradc 15220000.nvdisplay: vblank syncpt # 17 for dc 2
[    9.084161] tegradc 15220000.nvdisplay: vpulse3 syncpt # 18 for dc 2
[    9.106834] hpd: switching from state 7 (Takeover from bootloader) to state 0 (Reset)
[    9.114675] hpd: state 0 (Reset), hpd 0, pending_hpd_evt 0
[    9.120007] tegradc 15210000.nvdisplay: blank - powerdown
[    9.125342] extcon-disp-state external-connection:disp-state: cable 44 state 0 already set.
[    9.133572] Extcon DP: HPD disabled
[    9.137248] hpd: hpd_switch 0
[    9.140296] hpd: switching from state 0 (Reset) to state 1 (Check Plug)
[    9.147042] hpd: state 1 (Check Plug), hpd 0, pending_hpd_evt 0
[    9.152911] hpd: switching from state 1 (Check Plug) to state 3 (Disabled)
[    9.161128] tegradc 15220000.nvdisplay: probed
[    9.184109] tegradc 15220000.nvdisplay: fb registered
[    9.189254] hpd: state 7 (Takeover from bootloader), hpd 0, pending_hpd_evt 1
[    9.190987] hpd: switching from state 7 (Takeover from bootloader) to state 0 (Reset)
[    9.192629] hpd: state 0 (Reset), hpd 0, pending_hpd_evt 0
[    9.194243] tegradc 15220000.nvdisplay: blank - powerdown
[    9.195860] extcon-disp-state external-connection:disp-state: cable 44 state 0 already set.
[    9.197336] Freeing unused kernel memory: 8576K
[    9.208453] Extcon DP: HPD disabled
[    9.208472] hpd: hpd_switch 0
[    9.208476] hpd: switching from state 0 (Reset) to state 1 (Check Plug)
[    9.208486] hpd: state 1 (Check Plug), hpd 0, pending_hpd_evt 0
[    9.208490] hpd: switching from state 1 (Check Plug) to state 3 (Disabled)
[   12.827977] Wake76 for irq=199
[   12.829637] Wake77 for irq=199
[   12.831228] Wake78 for irq=199
[   12.832799] Wake79 for irq=199
[   12.834336] Wake80 for irq=199
[   12.835874] Wake81 for irq=199
[   12.837379] Wake82 for irq=199
[   12.838942] tegra-xusb 3610000.xhci: Upgrade port 0 to USB3.0
[   12.840516] tegra-xusb 3610000.xhci: Upgrade port 1 to USB3.0
[   12.931931] usb usb2: usb_suspend_both: status 0
[   15.323527] tegra-xusb 3610000.xhci: entering ELPG
[   15.331273] tegra-xusb 3610000.xhci: entering ELPG done

After
[    9.197336] Freeing unused kernel memory: 8576K

On the screen I get this message:
Mounting ...

And after
[    9.208490] hpd: switching from state 1 (Check Plug) to state 3 (Disabled)

I get
mount: mounting   on /mnt failed: Invalid argument

I use the stock flash configuration. It looks OK to me:
<?xml version="1.0"?>

<!--
I'll put that to run and check again on Monday.
Thanks

I guess rdinit=/bin/sh involves a full rebuild.

You should just be able to set KERNEL_ARGS_append = " rdinit=/bin/sh" in your local.conf... shouldn't require a full rebuild, but you will need to re-flash.
BTW, which branch are you working off of?

Alright, thanks for the tip.
I'm on warrior at the moment.
On Fri, Nov 29, 2019, 17:23 Matt Madison<EMAIL_ADDRESS>wrote:

I guess rdinit=/bin/sh involves a full rebuild.
You should just be able to set KERNEL_ARGS_append = " rdinit=/bin/sh" in
your local.conf... shouldn't require a full rebuild, but you will need to
re-flash.
BTW, which branch are you working off of?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/madisongh/meta-tegra/issues/216?email_source=notifications&email_token=AEDDM24D2MOZUAR3XUH5KLTQWEXXPA5CNFSM4JTACG62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPDN3Q#issuecomment-559822574,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEDDM23CTVSVGSURBE4XOMTQWEXXPANCNFSM4JTACG6Q
.

What rdinit=/bin/sh  should do?
I've added it but I don't get any shell and the system boots as without.
My kernel arguments are
Linux Cmdline: console=ttyTCU0,115200 console=ttyTCU0,115200 console=tty0 OS=l4t fbcon=map:0 rdinit=/bin/sh video=tegrafb no_console_suspend=1 earlycon=tegra_comb_uart,mmio32,0x0c168000 gpt tegra_fbmem=0x140000@0xa0697000 lut_mem=0x20
And after checking, my kernel version is
Linux version 4.9.140-l4t-r32.2+g3dcbed5d27df (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 SMP PREEMPT Fri Nov 29 15:38:06 UTC 2019

It should bring up a shell when the kernel first starts - in the initial ramdisk.  Do you have a keyboard and monitor attached?  Since there's a console=tty0 in the kernel command line, the shell prompt will come up on the graphical console.  If you only have the serial console attached, try adding KERNEL_ARGS_remove = "console=tty0" in your local.conf to get rid of the reference to the graphical console.
Hmm.  I could swear I saw '4.4' when I looked at that log before.

Yes you did see 4.4 =) minicom just kept writing to an old TX2 file... and wasn't careful enough. I updated the lengthy post.
I basically only have Xavier dev kit with USB C port connected to my PC and minicom on ttyUSB3. I have a monitor connected too.
I'll try what you suggested, I'd like to learn to make that bit work.
In the meanwhile I think I've just discovered the culpitt.
boot2qt ditro layer is overwriting init-boot.sh to add nfs boot option. See
opt="rw"
wait=""
nfsroot=""
nfsopts=""
for bootarg in `cat /proc/cmdline`; do
    case "$bootarg" in
    root=*) rootdev="${bootarg##root=}" ;;
    nfsroot=*)
            nfsroot=$(echo ${bootarg##nfsroot=} | cut -d ',' -f 1)
            nfsopts=$(echo ${bootarg##nfsroot=} | cut -d ',' -f 2-)
            nfsopts=${nfsopts##${nfsroot}}
            ;;
    ro) opt="ro" ;;
    rootwait) wait="yes" ;;
    esac
done
if [ -n "$wait" -a ! -b "${rootdev}" ]; then
    echo "Waiting for ${rootdev}..."
    count=0
    while [ $count -lt 25 ]; do
    test -b "${rootdev}" && break
    sleep 0.1
    count=`expr $count + 1`
    done
fi
echo "Mounting ${rootdev}..."
if [ "$rootdev" = "/dev/nfs" ]; then
    echo "Using NFS to boot..."
    mount -t nfs -o "${opt},${nfsopts}" "${nfsroot}" /mnt || exec sh
else
    mount -t ext4 -o "$opt" "${rootdev}" /mnt || exec sh
fi
echo "Switching to rootfs on ${rootdev}..."
mount --move /sys  /mnt/sys
mount --move /proc /mnt/proc
mount --move /dev  /mnt/dev
exec switch_root /mnt /sbin/init

and that script doesn't use the platform-preboot script added for xavier (not officially a supported board).
I'll try to merge these 2.
The core-image-initial image with only meta-tegra and poky builds and boots fine.

Fixed by adding platform-preboot script execution


[Event Request] table 96 "G/L Budget Entry" - OnAfterUpdateDimSet

Hello, we need the followong new Event OnAfterUpdateDimSet in table 96 "G/L Budget Entry".
thanks a lot!
procedure UpdateDimSet(var TempDimSetEntry: Record "Dimension Set Entry" temporary; DimCode: Code[20]; DimValueCode: Code[20])
    begin
        if DimCode = '' then
            exit;
        if TempDimSetEntry.Get("Dimension Set ID", DimCode) then
            TempDimSetEntry.Delete();
        if DimValueCode = '' then
            DimVal.Init()
        else
            DimVal.Get(DimCode, DimValueCode);
        TempDimSetEntry.Init();
        TempDimSetEntry."Dimension Set ID" := "Dimension Set ID";
        TempDimSetEntry."Dimension Code" := DimCode;
        TempDimSetEntry."Dimension Value Code" := DimValueCode;
        TempDimSetEntry."Dimension Value ID" := DimVal."Dimension Value ID";
        TempDimSetEntry.Insert();

        OnAfterUpdateDimSet(DimCode, DimValueCode, Rec.Date);
    end;

    [IntegrationEvent(false, false)]
    local procedure OnAfterUpdateDimSet(DimCode: Code[20]; DimValueCode: Code[20]; GLBudgetEntryDate: Date)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 53049.


Set channel state to NOTINFLUSH when Closing

Description

closes: #3987
Since we close the channel in several places, I created a helper function for this behaviour. There are a few other ways that we could do it that might be nicer.
// no modification
func CloseChannel(channel Channel) Channel {
	channel.State = CLOSED
	channel.FlushStatus = NOTINFLUSH
	return channel
}

// method instead of function
func (c Channel) Close() Channel {
        c.State = CLOSED
	c.FlushStatus = NOTINFLUSH
	return c
}

If people think this is overkill, we can just keep the re-assignments directly in-line. My concern is that it is now no longer sufficient to just modify the channel state to "close" the channel so it seems beneficial to create a function for this.
Commit Message / Changelog Entry
N/A Feature branch
see the guidelines for commit messages. (view raw markdown for examples)

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

If we go for the pointer receiver solution, it would be nice to update the description of the PR, @chatton :)


BlenderRender : "view material diffuse texture as TexturedSolid", or "Texface update"

material viewport mode in Blender render is not useful, I think we have a better visibility by using TexturedSolid viewport shading, but this use texface, so we need a bridge between texface assignation and material assignation. Can be also useful for unwrapping and updating texfaces.

available in beta, need little enhancement


WIP: haskellPackages.ghcWithPackages: Wrap haddock with GHC lib dir

Motivation for this change
#36976
haddock isn't wrapped up in ghcWithPackages and friends. I think it's safe to do so, but I'm unsure whether this is the right approach, so I'm looking for feedback.
Things done
Wrapped up haddock with only -B$NIX_${ghcCommandCaps}_LIBDIR. I think this is sufficient, but maybe it doesn't hurt to simply use the wrapper used for eg. the ghc executable, which adds more env vars?

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Here's what I tested, inspired by @mrkkrp
~/nixpkgs nixos-unstable
❯ nix-shell -p "pkgs.haskellPackages.ghcWithPackages (pkgs: with pkgs; [ lens ])" --run 'haddock --optghc -package --optghc lens; echo $?'
<command line>: cannot satisfy -package lens
    (use -v for more information)
1

❯ git checkout haddock-wrapped

~/nixpkgs haddock-wrapped
❯ nix-shell -p "pkgs.haskellPackages.ghcWithPackages (pkgs: with pkgs; [ lens ])" --run 'haddock --optghc -package --optghc lens; echo $?'
0


Update msh_checkbox.dart fix initial value True.

fix initial value True.

Thanks for the contribution! Would you mind explaining a bit the rationale for this change?
This would run the animation when the widget is initially built, even if the initial value is already true. That is most likely not the desired behavior for everyone, but you could consider adding it as a conditionally enabled behavior. Perhaps something like this:
MSHCheckBox(
  // ...
  runAnimationOnFirstBuild: true, // default to false
),

Please also format your code using the dart_style formatter for consistency.
Thank you!

Hi @dr4mohamed,
Another user recently submitted a pull request, which I think addresses the issue which you were trying to fix here. I apologize that I did not understand the bug you were trying to fix, but you should find that version 1.1.2 is working!


Run runActivity on main thread (#895)

Fixes #895 .

Hi @sk409, I believe the only way runActivity could be called on a background thread is if your test is running on a background thread. Instead of this change can you mark your test with @MainActor?
We have plans to more deeply integrate snapshot testing with Swift's concurrency tools, but until then you will need to be responsible for calling its APIs on the main thread.

@mbrandonw
My app uses SDWebImageSwiftUI to display images, but SDWebImageSwiftUI loads images and updates views on the main thread, so when I run the test on the main thread, XCTWaiter.wait blocks image loading and updating views. Therefore, the image will no longer be displayed in the snapshot.
For the reasons mentioned above I need to run my tests on a background thread instead of the main thread.


typescript version of foliate js

is there any plans for typescript porting of foliate js?
This renderer could very well replace epub.js, but for us to really integrate it into our workflow a typescript port is needed
thanks for the great project

Not for now. A good part of the code is written in a quite dynamic style and doesn't seem to translate easily to well typed TypeScript. Besides that, I quite like not having a build step. Perhaps one should start with creating declaration files first.

Hey both of you; I'm porting parts of foliate-js to a Typescript project (I'm only interested in extracting metadata from various ebook formats for now) and would be willing to contribute those migrated parts back upstream, if this helps.

You can also use jsdoc to add types, I just saw an article from the svelte creator about why they prefer that route.
https://devclass.com/2023/05/11/typescript-is-not-worth-it-for-developing-libraries-says-svelte-author-as-team-switches-to-javascript-and-jsdoc/


[JSON] fix bug that incorrectly allowed trailing commas after an empty container

I believe the intent here is that container_just_begun_ indicates when the previous character is a { or [.  We're using that to determine if it's okay to accept a } character when we're expecting an object key or a ] character when we're expecting an array element.  However, the only place that we were setting it back to false was here, and that code-path was not used when we saw a } or ] character, so we were never resetting it to false in the case that the container was empty.


can this library support customized Token parsing?

Hi, this library is nice! Good work! Though it has many advanced C++ template code which is a bit hard for me.
Back to my question, I mean in my application, I have my own lexer(mainly the C-preprocessor) implemented myself, so my question is: can the library support parsing rules for custom lexer.
For example, the lexer has some kinds of std::vector<Token> supplied, the Token class may have definition like:
class Token
{
    TokenKind kind;
    std::string lexeme;
}

So, I would like this library to parse the Token stream not the char stream.
Any suggestions?
Thanks.

Hello!
It is certainly possible, the library is completely input type agnostic. To be able to parse non-character elements, you'd pass in the sequence of tokens to the reader. The passed in source is expected to be read with an indexer operator, so a std::vector<Token> is perfectly fine to pass in. Note, that the reader won't own the source it reads from, you need to keep the vector alive.
Once you got your reader, you'd define your basic helper combinator to match on a certain token type. The combinator pc::one will work out of the box, and consume a token from the input unconditionally. Then you could define your match combinator using the builtin transformations, something like so:
template <TokenKind Kind>
bool has_token_kind(Token const& t) { return t.kind == Kind; }

template <TokenKind Kind>
inline constexpr auto match = pc::one[pc::filter(has_token_kind<Kind>)];

This will give you a parser that can match a certain kind of token (for ex. match<TokenKind::identifier>).

Thanks for the reply.
The final goal I want to do is try to parse the C++ source file in the Code::Blocks editor. Because the C++ grammar becomes too complex for me to write many hand-written ParseXXX functions. If you have any idea/suggestion, dose the CppCmb library is suitable for this kind of things? I mean I would like to use the CppCmb library to generate the Parser. While, the Lexer and the Preprocessor are still remain the same.
For some reasons, I need to do some type check of  parsing the x*y, if x is a type, then it is a pointer definition, such as this document/cpp file did: PEGParser/type_checker.cpp at master · TheLartians/PEGParser
I think it is still a bit complex for me to tweak the CppCmb compiler. If you have time, can you help to add such sample code for a Token class?
My actual Token class could be:
class Token
{
    wxString lexeme;
    TokenKind kind;
}

Which does not use the std::string.
Another question is: is it possible to add some operator precedence climbing feature(maybe it is called pratt parser, see:Operator-precedence parser - Wikipedia )? I mean it is better for handling the expressions like a+b/c+d*e. See also:
https://github.com/yhirose/cpp-peglib#parsing-infix-expression-by-precedence-climbing
I have a discussion/request here in another peg based parser here:
Any method to integrate a customized lexer in your library?

To be honest, I don't think I'd use any generator or library for parsing C++, simply because it's context sensitive (well in the case of C++ it's even more complex than context sensitive). Most parsing tools primarily target context-free languages, ones that can be well-structured without any semantic analysis, CppCmb is no exception. The parser has no direct ability to feed back or forward information for other elements of a front-end (well, technically one could do it with some transformation combinators, but never played around with the idea in practice).
If you just need a "good-enough" parser, or a parser that can produce ambiguous trees that you can disambiguate with post-processing steps, you might want to take a look at TreeSitter, which was made especially for editors for incremental parsing, and parsing ambiguous constructs that can be disambiguated on the fly.

I think it is still a bit complex for me to tweak the CppCmb compiler. If you have time, can you help to add such sample code for a Token class?

I'll try to find some time during the weekend.

Another question is: is it possible to add some operator precedence climbing feature(...)?

When I wrote this library, I simply didn't feel the need, as one can encode precedence directly in the grammar, as shown in the last example of the wiki. It should be totally possible, just needs more template-metaprogramming that unrolls the precedence list into the appropriately nested grammars.

Hi, thanks for the detailed reply.
I think parsing every component of the C++ code is too complex. But my idea is that a simple C++ parser can extract the tags of a source file, not the full code. For example, the function body content may be skipped when collecting the tags, this is similar like the tool: universal-ctags/ctags: A maintained ctags implementation.
I have read your sample code in your example A full expression parser, it is complex, I'm not sure, but I can't find some document that let a client user to add the semantic action function(or functor) to the matched items. If you have time, can you show me a direction on how to add such functions? This maybe useful to build a AST.
int to_num(std::vector<char> const& chs) {
    int n = 0;
    for (auto c : chs) n = n * 10 + (c - '0');
    return n;
}
...
...
cppcmb_def(num) =
      (+digit) [to_num]
    ;

It looks like the to_num is the callback function when the +digit get matched, but I'm not sure the parameter of the function it will set if we use a custom Token lexer.
Thanks.


Add flag to control raising exception via expectation order

To be honest, I'm not sure what the point is. Why would the mock not raise an exception when it has been told that the expectation order matters?


Treat UnwillingToPerformError like an InvalidCredentialsError

When attempting to pass a zero-length password to a server that doesn't allow unauthenticated binds, the client returns an UnwillingToPerformError, which results in ldapauth trying to authenticate again. When this happens, the client is still connected to the server, so the backoff attempt ends up leaking clients, and getting stuck in a loop that will never end.

Note to self: See SYSOPS-164 for internal details.
Thanks Cody!


Running on multiple conditions

Hello, i have a short question. I am currently running it for multiple conditions. I run it by pooling all the cells together with different identifiers per condition.
In case i want to use the plot funtions, would it be statistically correct to just plot the based on the senders, receivers of focus param? Using plots like the eventum bar, seem to miss some of the cell groups.
Thank you in advance!!:)

Thanks for using mebocost. I am not sure if I got you correctly, and why it missed some of the cell groups. If you set the focused senders and receivers, the eventnum bar plot will only show you the number of communications identified associated with the focused senders and receivers, so will not show other cell groups that did not specified. Keep empty list if you do not specify cell groups of focus.

Thanks a lot !! it was a small bug in my code that was thresholding some of the connections.
Is it possible in the current version to run the pathway analysis like in v1.0.3 ( in the other github repo) or it's  an on-going process?

Thank you for the question. Since we are still developing the pathway analysis module, I removed that function from this version. We will release it once the module has matured.

Makes sense, looking forward to it!


Stumped at the command line (Mac OS)

Apologies for a bit of a novice troubleshooting, but I could use some help. I attempting to run fmriprep-docker out of my -zsh terminal.
Command line fmriprep-docker /Volumes/PhD2TB/hudgins/project /Volumes/PhD2TB/hudgins/project/sub-R0097/derivatives participant --participant-label sub-R0097 --fs-license-file /Volumes/PhD2TB/hudgins/license.txt --use-syn-sdc --output-spaces anat --stop-on-first-crash --fs-no-reconall --ignore slicetiming
I ran the above command line with .\derivatives to have the preprocessing run correctly, but the output files went to some inaccessible "tmp" folder location.
For example,
211006-18:31:34,49 nipype.workflow INFO:
[Node] Running "skullstrip_first_dilate" ("nipype.interfaces.fsl.maths.DilateImage"), a CommandLine Interface with command:
fslmaths -dt char /tmp/work/fmriprep_wf/single_subject_R0097_wf/func_preproc_ses_2_task_rest_wf/bold_t1_trans_wf/bold_reference_wf/enhance_and_skullstrip_bold_wf/skullstrip_first_pass/ref_bold_corrected_brain_mask.nii.gz -kernel sphere 6.0000 -dilF /tmp/work/fmriprep_wf/single_subject_R0097_wf/func_preproc_ses_2_task_rest_wf/bold_t1_trans_wf/bold_reference_wf/enhance_and_skullstrip_bold_wf/skullstrip_first_dilate/ref_bold_corrected_brain_mask_dil.nii.gz
211006-18:31:35,246 nipype.workflow INFO:
[Node] Finished "fmriprep_wf.single_subject_R0097_wf.func_preproc_ses_2_task_rest_wf.bold_t1_trans_wf.bold_reference_wf.enhance_and_skullstrip_bold_wf.skullstrip_first_dilate".
211006-18:31:36,29 nipype.workflow INFO:
[Node] Setting-up "fmriprep_wf.single_subject_R0097_wf.func_preproc_ses_2_task_rest_wf.bold_t1_trans_wf.bold_reference_wf.enhance_and_skullstrip_bold_wf.skullstrip_first_mask" in "/tmp/work/fmriprep_wf/single_subject_R0097_wf/func_preproc_ses_2_task_rest_wf/bold_t1_trans_wf/bold_reference_wf/enhance_and_skullstrip_bold_wf/skullstrip_first_mask".
However, when corrected:
%  fmriprep-docker /Volumes/PhD2TB/hudgins/project /Volumes/PhD2TB/hudgins/project/sub-R0097/derivatives participant --participant-label sub-R0097 --fs-license-file /Volumes/PhD2TB/hudgins/license.txt --use-syn-sdc --output-spaces anat --stop-on-first-crash --fs-no-reconall --ignore slicetiming
RUNNING: docker run --rm -e DOCKER_VERSION_8395080871=20.10.8 -it -v /Volumes/PhD2TB/hudgins/license.txt:/opt/freesurfer/license.txt:ro -v /Volumes/PhD2TB/hudgins/project:/data:ro -v /Volumes/PhD2TB/hudgins/project/sub-R0097/derivatives:/out nipreps/fmriprep:20.2.3 /data /out participant --participant-label sub-R0097 --use-syn-sdc --stop-on-first-crash --fs-no-reconall --ignore slicetiming --output-spaces anat
You are using fMRIPrep-20.2.3, and a newer version of fMRIPrep is available: 20.2.4.
Please check out our documentation about how and when to upgrade:
https://fmriprep.readthedocs.io/en/latest/faq.html#upgrading
<EMAIL_ADDRESS>1: [WARN] You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. (code: 13 - SLICE_TIMING_NOT_DEFINED)
	./sub-R0097/ses-1/func/sub-R0097_ses-1_task-rest_bold.nii
	./sub-R0097/ses-2/func/sub-R0097_ses-2_task-rest_bold.nii

Please visit https://neurostars.org/search?q=SLICE_TIMING_NOT_DEFINED for existing conversations about this issue.

2: [WARN] The Authors field of dataset_description.json should contain an array of fields - with one author per field. This was triggered because there are no authors, which will make DOI registration from dataset metadata impossible. (code: 113 - NO_AUTHORS)

Please visit https://neurostars.org/search?q=NO_AUTHORS for existing conversations about this issue.

    Summary:                   Available Tasks:        Available Modalities:
    1101 Files, 69.23GB        rest                    T1w
    180 - Subjects                                     bold
    3 - Sessions

If you have any questions, please post on https://neurostars.org/tags/bids.

211006-23:45:08,18 nipype.workflow IMPORTANT:
Running fMRIPREP version 20.2.3:
  * BIDS dataset path: /data.
  * Participant list: ['R0097'].
  * Run identifier: XXXXX.
  * Output spaces: anat.
  * Pre-run FreeSurfer's SUBJECTS_DIR: /out/freesurfer.

Process Process-2:
Traceback (most recent call last):
File "/usr/local/miniconda/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
self.run()
File "/usr/local/miniconda/lib/python3.7/multiprocessing/process.py", line 99, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/miniconda/lib/python3.7/site-packages/fmriprep/cli/workflow.py", line 82, in build_workflow
retval["workflow"] = init_fmriprep_wf()
File "/usr/local/miniconda/lib/python3.7/site-packages/fmriprep/workflows/base.py", line 64, in init_fmriprep_wf
single_subject_wf = init_single_subject_wf(subject_id)
File "/usr/local/miniconda/lib/python3.7/site-packages/fmriprep/workflows/base.py", line 304, in init_single_subject_wf
func_preproc_wf = init_func_preproc_wf(bold_file)
File "/usr/local/miniconda/lib/python3.7/site-packages/fmriprep/workflows/bold/base.py", line 206, in init_func_preproc_wf
sbref_files = layout.get(return_type='file', **entities)
File "/usr/local/miniconda/lib/python3.7/site-packages/bids/layout/layout.py", line 631, in get
raise ValueError(msg + "If you're sure you want to impose "
ValueError: 'desc' is not a recognized entity. If you're sure you want to impose this constraint, set invalid_filters='allow'.
fMRIPrep: Please report errors to https://github.com/nipreps/fmriprep/issues
Any guidance to what I am overlooking would be greatly appreciated.

You're including the output directory inside a subject directory. That seems very likely to cause problems as derivatives will pollute your inputs. I would strongly suggest keeping your outputs separate from your inputs.

Does the dataset still validate? It reads as if you have files with desc- in them in your inputs.

|.derivatives
|.DS_Store
|____.project
|license.txt
|list_missing.csv
|project
| |. .


Trilium Next Arm

Hello,
Would it be possible to add compatibility with ARM processors in the configuration because it was added with version 0.90.4
https://github.com/TriliumNext/Notes/releases/tag/v0.90.4
Thank

Refresh the addon store. Hopefully should work.

Hello,
It's work


Correct spelling error

"Pre-requisite" is not a word. However, prerequisite is. This PR does not introduce any new functionality and only documentation changes.

@binaryflesh can you give a PR with base to develop? develop get to master every release

@binaryflesh any update on this?

@binaryflesh closing this due to inactivity. Please do re-open or re-submit the PR


Added binary search tree algorithm

What does this PR do?
Contribute to #1 by adding a binary search tree.

Note: this is the simplest implementation of the binary search tree.

Signed-off-by: Richard Burk Orofeo<EMAIL_ADDRESS>

Thank you for contributing to @AllAlgorithms, your pr got merged! ✨ Make sure that you ⭐ the project 🤓, and continue helping us!

We are very happy with your contribution, but for the pull request to got merged in, we should fix the following:

[ ] Implement the algorithm in one file. What about a simple fmt.Println() 😃

Will update my PR @abranhe

Hi @abranhe, I've updated my PR now :) hope I got the idea.


Consistent setting of code and location

Currently, we set the code and location after the Handler has "handled" the node. While this is quite convenient, it posses a problem. If we include the location into the hash code to speed up performance (A LOT), we need to make sure that location is set as early as possible. Therefore I suggest to set the code and location as soon as possible, e.g. through our NodeBuilder paradigm.

This actually has another advantage, that we have better control in the handle functions which original AST node should denote the code and region of the CPG node. This is especially useful if the original AST node has sub-nodes which need to be assigned to respective CPG nodes (for example in variable assignments). Currently, the code/region of the sub nodes is either not set at all or is set incorrectly to the complete outer node.


Re-do writeup for enable-ui repo that includes screenshot of www.ines.fund, and writeup explaining that it's a frontend for enable-contracts

Currently, there is no explanation for the enable-ui repository.

[ ] Include screenshot of www.ines.fund
[ ] Short write up with links to the enable repository, and enable-contracts repository

@onggunhao Assign me on this

Wait, you can't edit the issues in this repository?


Missing majority of ZMWs after running lima to search for adapters

Hi, I'm not sure if you can help me on this but just want to raise this issue I've encountered after filtering adapters with lima. Not entirely sure why lima filtered out majority of the 'deepconsensus hifi reads'. Below is the script for the deepconsensus and lima:
DC
cmd4="module purge && module load deepconsensus/0.3.1 && deepconsensus run --checkpoint=/cluster/home/dc_model_0.3/checkpoint --ccs_bam=${outDir}/${outFilePrefix}.${SLURM_ARRAY_TASK_ID}.bam --subreads_to_ccs=${outDir}/${outFilePrefix%.ccs}.subreads_to_ccs.${SLURM_ARRAY_TASK_ID}.bam --output=${outDir}/${outFilePrefix%.ccs}.deepconsensus.${SLURM_ARRAY_TASK_ID}.fastq --cpus ${THREAD}"
Lima
lima --num-threads 84 --split-bam-named --same --ccs ${ID}.deepconsensus.fastq /cluster/home/lima_pbmarkdup/pb_pcr_adapter.fa ${ID}.deepconsensus.lima.fastq
Here is the output summary from lima:
ZMWs input (A) : 1925775
ZMWs above all thresholds (B) : 13042 (0.68%)
ZMWs below any threshold (C) : 1912733 (99.32%)
ZMW marginals for (C):
Below min length : 199 (0.01%)
Below min score : 648496 (33.90%)
Below min end score : 648496 (33.90%)
Below min passes : 0 (0.00%)
Below min score lead : 648496 (33.90%)
Below min ref span : 1912733 (100.00%)
Without SMRTbell adapter : 0 (0.00%)
ZMWs for (B):
With same pair : 13042 (100.00%)
Coefficient of correlation : 0.00%
ZMWs for (A):
Allow diff pair : 1925775 (100.00%)
Allow same pair : 1925775 (100.00%)
Reads for (B):
Above length : 13042 (100.00%)
Below length : 0 (0.00%)
Thank you, I appreciate your help!

Hi @rosspdu ,
Do you have any updates for us? If not, I'll plan to close this issue in the next few days. Thank you!

Dear Pi-Chuan,
Apologies for the late reply and for not providing updates on this. Yes,
please close this issue. We figured it's 'running lima' that caused the
missing ZMWs.
Thanks again for your help.
Cheers,
Ross
On Wed, Jan 4, 2023 at 8:28 PM Pi-Chuan Chang @.***>
wrote:

Hi @rosspdu https://github.com/rosspdu ,
Do you have any updates for us? If not, I'll plan to close this issue in
the next few days. Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/google/deepconsensus/issues/49#issuecomment-1371331606,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3U7MXLFN7G75KPPX3BP4GLWQXFOLANCNFSM6AAAAAASDGFXBA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Cannot download win32-x64-46_binding.node

My environment
node version : v4.2.2
npm version : v2.14.7
node-sass version :3.4.1
THE ERROR
Cannot download "https://github.com/sass/node-sass/releases/download/v3.4.1/win32-x64-46_binding.node":

socket hang up

Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g.

      export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

      npm config set proxy http://example.com:8080

I troubleshoot the cause, it may be a network failure. I can not access
https://github-cloud.s3.amazonaws.com/releases/4128353/10dc4cb6-88a5-11e5-8375-a865ca7ff7b8.node

Advice:
Move the *.node files from github-cloud.s3.amazonaws.com to github.com

This is a networking problem, you can try to download those file offline.

Sorry ,I just can download the Source code (zip),
Can you tell me how to bulid the win32-x64-46_binding.node file?
Thanks !

We will not move the binaries. As the error message suggests you should use
a proxy.
On 12 Nov 2015 9:25 am, "Leon kao"<EMAIL_ADDRESS>wrote:

My environment
node version : v4.2.2
npm version : v2.14.7
THE ERROR
Cannot download "https://github.com/sass/node-sass/releases/download/v3.4.1/win32-x64-46_binding.node":
socket hang up
Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.
  export HTTP_PROXY=http://example.com:1234

or configure npm proxy via
  npm config set proxy http://example.com:8080

I troubleshoot the cause, it may be a network failure. I can not access
https://github-cloud.s3.amazonaws.com/releases/4128353/10dc4cb6-88a5-11e5-8375-a865ca7ff7b8.node
Advice:
Move the *.node files from github-cloud.s3.amazonaws.com to github.com
—
Reply to this email directly or view it on GitHub
https://github.com/sass/node-sass/issues/1263.

I got it.
Thank you very much!

On Thu, 12 Nov 2015, Leon kao wrote:

Sorry ,I just can download the Source code (zip),
Can you tell me how to bulid the win32-x64-46_binding.node file?

You can try building from source using MinGW or Microsoft Visual Studio 2013 or 2015
and a Windows SDK.
You can also get a ready file by cloning https://github.com/sass/node-sass-binaries
repository.

@saper
I'm sorry to reply to your message too late.
Thank you very much!


Add support for OpenJDK 17

Mirror PR for jvm-common.
References W-8655975

Removing the Skip changelog label, since tthis needs a changelog entry (it was just the date and version number that didn't want to be included - add the changelog entry under "unreleased" :-) ).

@edmorley yeah, sorry I was temporarily confused when I read your comment at 7am 😓  I'll re-add the changelog.md comment! :)


Update openra to 20170527

After making all changes to the cask:

[x] `brew cask audit --download {{cask_file}}` is error-free.
[x] `brew cask style --fix {{cask_file}}` left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as 2813b2c3781845dff0d0ab1fc350a45672d0b73f. Your contribution is still credited to you.


Argo UI - Archived Workflows - Error when clicking on hidden nodes ellipsis

Summary
What happened/what you expected to happen?
When trying to view the hidden nodes in an archived workflow by clicking on the ellipsis, the following error occurs.

Diagnostics
What Kubernetes provider are you using?

Azure Kubernetes Service

What version of Argo Workflows are you running?

Argo v2.11.1

Occurs for all workflows that have multiple parallel steps generated with withParam
Logs from Argo UI:
 Cannot read property 'inputs' of undefined
 Reload this page to try again.

Stack Trace
TypeError: Cannot read property 'inputs' of undefined
    at t.WorkflowNodeInfo (https://argo-platform.maersk-digital.net/main.2abc14257d733f566d49.js:478:515762)
    at Zo (https://argo-platform.maersk-digital.net/main.2abc14257d733f566d49.js:396:52993)
    at Di (https://argo-platform.maersk-digital.net/main.2abc14257d733f566d49.js:396:59761)
    at Pi (https://argo-platform.maersk-digital.net/main.2abc14257d733f566d49.js:396:66453)
    at Ua (https://argo-platform.maersk-digital.net/main.2abc14257d733f566d49.js:396:90552)
    at Xa (https://argo-platform.maersk-digital.net/main.2abc14257d733f566d49.js:396:90936)
    at Es (https://argo-platform.maersk-digital.net/main.2abc14257d733f566d49.js:396:97823)
    at Ds (https://argo-platform.maersk-digital.net/main.2abc14257d733f566d49.js:396:97203)
    at js (https://argo-platform.maersk-digital.net/main.2abc14257d733f566d49.js:396:98578)
    at Cn (https://argo-platform.maersk-digital.net/main.2abc14257d733f566d49.js:396:30569)

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Can I please request the full workflow YAML so I can verify my fix works?

Reproduces using loops-param-result- example.


bug: the one end-to-end test is in test/integration

Describe the bug
Look at https://github.com/kubestellar/kubestellar/tree/ks-0.20/test . You will see just one subdirectory, integration, but the test it contains is an end-to-end test rather than an integration test.
Steps To Reproduce
See above
Expected Behavior
Things categorized in an ordinary way.
Additional Context
No response

/cc @effi-ofer

Created PR #1574

Fixed in #1572


Link content is missing in search results

On the search page the parts of the summary that are links in the fully-rendered documentation are completely missing. While those links should probably be rendered as normal text in the search results they should not be absent completely.
To Reproduce
Steps to reproduce the behavior:

Go to, e.g. https://docs.microsoft.com/en-us/dotnet/api/?view=netframework-4.7&term=DispatcherObject

Expected behavior
The Description column which shows the summary of the documentation should show the same text as the fully rendered documentation on its own page. Instead, those parts are missing.
Screenshots
Search results with missing words:

Documentation page with link where the word was missing:

Desktop:

OS: Windows 10 1809
Browser Chrome
Version 70

Additional context
Considering there are still various ways of documentation in the backend (I think there's still a mixture of auto-converted Markdown and the original documentation XML), this might not happen in all cases, but only for some content formats. I havent'checked, though.

@dend Can you take a look at this issue?

This is a duplicate of #637

Closing as duplicate of #637 - good call, @mairaw!


Delay when loading backgroundImage between tabs

Environment
Windows build number: 10.0.18362.295
Windows Terminal version (if applicable): 0.4.2382.0

Steps to reproduce

In your profiles.json, create two profiles (we will call them A and B)
Give A the space background image and B the tree background image (attached at the bottom)
Open windows terminal with A as the default profile
Open B in a new tab

Expected behavior

There should ideally be no delay in loading the background images.
Actual behavior

When we start with profile A, there will be no delay. However, when opening profile B we see the background is gray for small moment of time. Afterwards, the image loads normally. If we switch between tabs every 1.5 seconds(ish) when going from A to B the image has a delay loading. But if switch quickly there will be no delay. I will add a gif showing the result happening. I'll also add both of the background images I'm using.

This is image for profile A.

This is image for profile B.

 We do not cache the scaled images in order to avoid caching/live-update issues in the Terminal.
If you scale those images down to a size more like the typical size of your Terminal, they should require much less scaling and take much less time to render.
If you still see major perf issues, you may want to open an issue on the Win-UI XAML project who re responsible for the image rendering control we're using.
Closing this issue for now.

@bitcrazed So you're saying I can't have 8k images as the background and have amazing performance at the same time??????
I'm kidding, thanks for taking the time to respond.

Pffft! 8K is soooo last year! 16K is the way of the future ;)


How do we build data-generator-x.x.x.jar?

Tried building sample-data-generator using ./gradlew build. Build went successfully but i can't find the data-generator jar file.

It's called backend.jar, since the intent was for there to be a frontend some point. The JAR is available in ./backend/build/libs/backend-1.0.0.jar.
I'll close this when I update the README.

@emersonf thank you. That worked.


Can't unlisten browserHistory

I've tried asking on StackOverflow without results...
http://stackoverflow.com/questions/36851800/react-router-browserhistory-removelisten
How can I unlisten browserHistory?

The return from listen is a function that will remove the listener when called.

Is it documented somewhere?

Not here, but on the related history project: https://github.com/mjackson/history/blob/master/docs/GettingStarted.md

thanks


Fix compiling with vs2019 and sdk extras

Fixes the
'obj\Release\monoandroid81\Resource.Designer.cs' could not be found
error.

Seems to be fixed, please confirm.

Is fixed with the newest preview of visual studio 2019.
Please note that cake does not find the newest location of msbuild yet because they changed the location of msbuild.

Is fixed with the newest preview of visual studio 2019.
Please note that cake does not find the newest location of msbuild yet because they changed the location of msbuild.


Add debug framework

Add debug framework #241 and currently support javascript and python3.

@wangtao0101 Thank you for the contribution. So far, I noticed some problems in this PR:

This is a too big PR which is almost impossible to review
There are some file changes which I cannot know why, like some files with number, e.g.  src/debug/entry/javascript/problems/116.js

Just as I have said, so far I don't want to embed the debug features into this extension, for the following reasons:

Impossible to provide a general debug framework for all languages
Too much uncertainties, any of the dependent language extension changes its API, we breaks.

So, my suggestion is that, you can build and publish your own extension for a specific language's debug scenario, if you need any help, I'm willing to help you.

@jdneo Thank you for your suggestion. I  will publish my own extension.


[Downloads Manager] Copy File Action in Manage Downloads

Description
Added the action Copy File for the Manage Downloads command
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hey @yug2005, thanks for the contribution. This is really cool. I simplified the code a bit and use our built-in <Action.CopyToClipboard /> component.


Request support for Czajnik Setti+ KT950W

Log Message
2023-02-13 14:35:16.681 WARNING (MainThread) [custom_components.tuya_local.config_flow] Device matches bwt_heatpump with quality of 29%. DPS: {'updated_at':<PHONE_NUMBER>.7473915, '1': False, '2': 27, '3': 80, '4': '40', '5': '104', '6': '40', '7': '104', '8': 40, '9': 104, '10': 40, '11': 104, '12': 'c', '13': False, '14': 30, '15': 'standby', '16': 'temp_setting', '19': 0}
Information about DPS mappings
{
  "result": {
    "category": "bh",
    "functions": [
      {
        "code": "start",
        "type": "Boolean",
        "values": "{}"
      },
      {
        "code": "temp_setting_quick_c",
        "type": "Enum",
        "values": "{\"range\":[\"85\"]}"
      },
      {
        "code": "temp_setting_quick_f",
        "type": "Enum",
        "values": "{\"range\":[\"185\"]}"
      },
      {
        "code": "temp_boiling_quick_c",
        "type": "Enum",
        "values": "{\"range\":[\"85\",\"100\"]}"
      },
      {
        "code": "temp_boiling_quick_f",
        "type": "Enum",
        "values": "{\"range\":[\"185\",\"212\"]}"
      },
      {
        "code": "temp_set",
        "type": "Integer",
        "values": "{\"unit\":\"℃\",\"min\":0,\"max\":100,\"scale\":0,\"step\":1}"
      },
      {
        "code": "temp_set_f",
        "type": "Integer",
        "values": "{\"unit\":\"℉\",\"min\":32,\"max\":212,\"scale\":0,\"step\":1}"
      },
      {
        "code": "temp_boiling_c",
        "type": "Integer",
        "values": "{\"unit\":\"℃\",\"min\":0,\"max\":100,\"scale\":0,\"step\":1}"
      },
      {
        "code": "temp_boiling_f",
        "type": "Integer",
        "values": "{\"unit\":\"℉\",\"min\":32,\"max\":212,\"scale\":0,\"step\":1}"
      },
      {
        "code": "temp_unit_convert",
        "type": "Enum",
        "values": "{\"range\":[\"c\",\"f\"]}"
      },
      {
        "code": "warm",
        "type": "Boolean",
        "values": "{}"
      },
      {
        "code": "warm_time",
        "type": "Integer",
        "values": "{\"unit\":\"min\",\"min\":0,\"max\":360,\"scale\":0,\"step\":1}"
      },
      {
        "code": "work_type",
        "type": "Enum",
        "values": "{\"range\":[\"setting_quick\",\"boiling_quick\",\"temp_setting\",\"temp_boiling\"]}"
      }
    ],
    "status": [
      {
        "code": "start",
        "type": "Boolean",
        "values": "{}"
      },
      {
        "code": "temp_current",
        "type": "Integer",
        "values": "{\"unit\":\"℃\",\"min\":0,\"max\":100,\"scale\":0,\"step\":1}"
      },
      {
        "code": "temp_current_f",
        "type": "Integer",
        "values": "{\"unit\":\"℉\",\"min\":32,\"max\":212,\"scale\":0,\"step\":1}"
      },
      {
        "code": "temp_setting_quick_c",
        "type": "Enum",
        "values": "{\"range\":[\"85\"]}"
      },
      {
        "code": "temp_setting_quick_f",
        "type": "Enum",
        "values": "{\"range\":[\"185\"]}"
      },
      {
        "code": "temp_boiling_quick_c",
        "type": "Enum",
        "values": "{\"range\":[\"85\",\"100\"]}"
      },
      {
        "code": "temp_boiling_quick_f",
        "type": "Enum",
        "values": "{\"range\":[\"185\",\"212\"]}"
      },
      {
        "code": "temp_set",
        "type": "Integer",
        "values": "{\"unit\":\"℃\",\"min\":0,\"max\":100,\"scale\":0,\"step\":1}"
      },
      {
        "code": "temp_set_f",
        "type": "Integer",
        "values": "{\"unit\":\"℉\",\"min\":32,\"max\":212,\"scale\":0,\"step\":1}"
      },
      {
        "code": "temp_boiling_c",
        "type": "Integer",
        "values": "{\"unit\":\"℃\",\"min\":0,\"max\":100,\"scale\":0,\"step\":1}"
      },
      {
        "code": "temp_boiling_f",
        "type": "Integer",
        "values": "{\"unit\":\"℉\",\"min\":32,\"max\":212,\"scale\":0,\"step\":1}"
      },
      {
        "code": "temp_unit_convert",
        "type": "Enum",
        "values": "{\"range\":[\"c\",\"f\"]}"
      },
      {
        "code": "warm",
        "type": "Boolean",
        "values": "{}"
      },
      {
        "code": "warm_time",
        "type": "Integer",
        "values": "{\"unit\":\"min\",\"min\":0,\"max\":360,\"scale\":0,\"step\":1}"
      },
      {
        "code": "status",
        "type": "Enum",
        "values": "{\"range\":[\"standby\",\"heating\",\"cooling\",\"warm\",\"heating_temp\",\"boiling_temp\",\"reserve_1\",\"reserve_2\",\"reserve_3\"]}"
      },
      {
        "code": "work_type",
        "type": "Enum",
        "values": "{\"range\":[\"setting_quick\",\"boiling_quick\",\"temp_setting\",\"temp_boiling\"]}"
      }
    ]
  },
  "success": true,
  "t":<PHONE_NUMBER>422,
  "tid": "d8cc1a4baba311ed9de742b33a3cd862"
}

Product ID
{
  "result": {
    "active_time":<PHONE_NUMBER>,
    "category": "bh",
    "category_name": "Smart Kettle",
    "create_time":<PHONE_NUMBER>,
    "gateway_id": "",
    "icon": "smart/icon/ay1578885126041ps8K2/eecc96a059fba5b5df4c68387371c91b.png",
    "id": "bf33b66314f3c0e062vtnt",
    "ip": "redacted",
    "lat": "redacted",
    "local_key": "redacted",
    "lon": "redacted",
    "model": "D2818EWB",
    "name": "Czajnik Setti+ KT950W",
    "online": true,
    "owner_id": "71836261",
    "product_id": "rsygyyeiyarl4urt",
    "product_name": "Smart kettle Setti+ KT950W",
    "sub": false,
    "time_zone": "+01:00",
    "update_time":<PHONE_NUMBER>,
    "uuid": "d1139a23a90a643e"
  },
  "success": true,
  "t":<PHONE_NUMBER>080,
  "tid": "6eccb786aba411edbe05a63cfb33a057"
}

Information about how the device functions
https://setti.pl/produkty/kuchnia/czajniki/czajnik-kt950w-smart-sterowanie-smartfonem-regulacja-temperatury-zimna-obudowa
A 1,7l kettle which besides just boiling water allows to set a specific temperature to warm up to and lets the user hold temperature for a specified amount of time. has DPs displaying temperature in both Celsius and Fahrenheit, since it is a product distributed in Poland it should default to Celsius.

For whatever reason after updating integration to the latest version double checked that /config/custom_components/tuya_local/devices/setti_czajnik_kettle.yaml is in there) and restarting HA the set up of the kettle doesn't proceed properly. It doesn't suggest the preset you've created (instead it proposes to use BWT_heatpump as before), and it's not even on the list of possible templates to assign to this device.

Please check the log message again.
We had similar problems with the Kogan kettle, it appears to send different dps depending on what state it is in.

2023-02-16 09:45:26.276 WARNING (MainThread) [homeassistant.util.async_] Detected blocking call to sleep inside the event loop. This is causing stability issues. Please report issue to the custom integration author for tuya_local doing blocking calls at custom_components/tuya_local/device.py, line 69: self._api = tinytuya.Device(dev_id, address, local_key)
2023-02-16 09:45:28.095 WARNING (MainThread) [custom_components.tuya_local.config_flow] Device matches bwt_heatpump with quality of 29%. DPS: {'updated_at':<PHONE_NUMBER>.4945655, '1': False, '2': 26, '3': 78, '4': '40', '5': '104', '6': '40', '7': '104', '8': 40, '9': 104, '10': 40, '11': 104, '12': 'c', '13': False, '14': 30, '15': 'standby', '16': 'temp_setting', '19': 0}
2023-02-16 09:45:28.098 WARNING (MainThread) [custom_components.tuya_local.config_flow] Report this to https://github.com/make-all/tuya-local/issues/

With the file from the last commit the kettle is properly recognized now, thanks!
Is there a way to add a separate toggle to start boiling water (you know, the most common feature of a kettle;)) ?

I would suggest adding buttons in the UI.  There isn't really a "turn on", because the device has so many "on" modes (Boil, Quick Boil, Warm, Quick Warm), so the "off" was mapped to mode along with them.

"Czajnik" is Polish for "Kettle".  It seems to me that there is an unnecessary tautology in the name of the configuration file :).

Unfortunately it was released in the last release, so is more difficult to change now.

The turn_on and turn_off services for the water_heater platform should now be implemented in 2023.2.4 (it was accidentally checked in along with another change so missed in the release notes), so it should now be possible to add actions to buttons or an input_boolean to get the simple UI you want (the turn_on will just use whatever mode the kettle is in).

Hi. I have  Setti+ KT950W and have problem. After integration with HA  the kettle "by itself" from time to time makes sounds, such as it normally emits when it receives a command from the application. It looks like HA sends some command to it from time to time

The integration does not send commands without being told to do so by Home Assistant.  However, there have been devices that reboot, perhaps due to internal memory leaks in the local protocol handling code, and I suspect that may be what is happening here.  On a smart switch that I have here, the problem went away when this integration switched from polling to persistent connections, but your device may be the other way around, and may work better with polling.

The self-reboot theory makes sense. The household members say that since the integration, the kettle does not boil the water - it runs for a while, then stops (probably a restart) and they had to press the switch again, heated it up a bit again, stop (restart) etc.

The integration does not send commands without being told to do so by Home Assistant. However, there have been devices that reboot, perhaps due to internal memory leaks in the local protocol handling code, and I suspect that may be what is happening here. On a smart switch that I have here, the problem went away when this integration switched from polling to persistent connections, but your device may be the other way around, and may work better with polling.

How can I switch from persistent to pooling ?

If you go into Settings / Devices and select your device in the Tuya Local panel on the integrations page, you should get an "Options" button.  In there is a checkbox to select polling.


podman login: tlsdir and certdir are mutually exclusive

Since e9d56496261807a5174c1347123b49e629c2490b, attempting to login to a container registry with the podman driver results in:
failed: [localhost] (item="workspace-src-ubuntu_focal registry username: ") => {"ansible_loop_var": "item", "changed": false, "item": {"image": "ghcr.io/image:tag", "name": "workspace-src-ubuntu_focal", "pre_build_image": true, "registry": {"credentials": {"password": ****, "username": *****}, "url": "ghcr.io"}}, "msg": "parameters are mutually exclusive: certdir|tlsverify"}

e9d56496261807a5174c1347123b49e629c2490b uses the containers.podman.podman_login module instead of using ansible.command to login to the registry. It appears that containers.podman.podman_login explicitly disallows setting the tlsverify and certdir arguments together -- no matter whether they are false/true. e9d56496261807a5174c1347123b49e629c2490b appears to set the parameters to an empty string even when they default to false.
Since this renders the podman plugin practically unusable, I propose:

to rollback the relevant part of e9d56496261807a5174c1347123b49e629c2490b
open a bug report with https://github.com/containers/ansible-podman-collections.git if it is felt that it should be possible to set these two options together (I do not personally see the rational for making them mutually exclusive -- I think podman allows both?)
if this is fixed upstream, reinstate the use of the podman.podman_login

Any news ?


Ci compute update

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

https://cloud.seqera.io/orgs/sanger-tol/workspaces/github-ci/watch/5VUhThWsZpmaJm
The job completed successfully now.

Oki, thanks. In that case, to avoid the risk of other pipelines failing for the same reason. Should we apply the plan you discussed last time ? i.e. change the TOWER_COMPUTE_ENV value to point at the 4 GB environment.
That way, all pipelines are changed at once.
From the perspective of compute efficiency, I'd be OK with that because it is justified and limited (there aren't that many Tower jobs coming through)

Oki, thanks. In that case, to avoid the risk of other pipelines failing for the same reason. Should we apply the plan you discussed last time ? i.e. change the TOWER_COMPUTE_ENV value to point at the 4 GB environment. That way, all pipelines are changed at once.

Yes, can you update? And then we can close this PR and delete the new repo level secret I added this morning.

Changed.
At the same time I've renamed the environments in Tower to be explicit about the RAM (rather than "small", "large")

Repo level secret deleted and no action for this PR itself.