no S3 sleep mode on HP x360 spectre

I have a dual boot setup at HP Spectre x360 Tablet 13″ ap0xxx (BIOS F.27/16Gb RAM/512Gb SSD/model 2018) Win10/Linux (Fedora 30 and Kubuntu 19.04)

Problem: There is no S3 mode available in either of Linux distro. Have tried stock kernels as well as latest for ubuntu 5.1.4-050104-generic

dmesg | grep ACPI | grep supports [    0.371691] ACPI: (supports S0 S4 S5)  cat /sys/power/mem_sleep  [s2idle] 

Questions: Is it Linux kernel issue or BIOS/UEFI? Is there a way to solve it, if HP keeps silence?

Guided Access Mode preventing iOS updates from MDM console?

Our organization uses an enterprise MDM product that features remote updating. All conditions specified by the MDM vendor are being met for this to work, but it doesn’t. I discovered that as soon as a kiosk is “Ended” from guided access mode, the pending download of iOS begins. Since all fleets of kiosks are locked down in some way, updating should work in this mode, or there would be no purpose to the existence of remote updating. Does anyone have any ideas about this?

Can’t see HD in disk utility in recovery mode, but can in OS

I’m pretty new to Macs. I got an iMac Pro in 2017 (grey one) and about 6 months ago it started giving me occasional folder flashing icon on startup.

It also started occasionally forgetting my password and so I’d have to reset it.

I figured maybe the HD got corrupted, so I ran first aid on it in disk utility while logged in. Whenever (after a restart) I run this, it says it’s ok. If I immediately re-run it, it says there’s corruption and I must run it from recovery mode.

Problem is, whenever I boot into recovery mode, it can’t find the disk at all.

Clearly it can find the disk for me to log in and run disk util in the OS.

I don’t have any external drives attached.

It’s running Mojave 10.14.13 (I tried updating to 10.14.15 and it has a broken download and won’t download the remainder of the update – that’s yet another issue).

This iMac has hardly been used at all since I bought it.

Thanks for any pointers.

Render content type display mode in custom module [duplicate]

This question already has an answer here:

  • How do I render nodes, now that node_view() has been deprecated? 3 answers

I’m facing the issue with rendering content type in specified display mode (teaser) in my custom module. I have a module which stores NIDs in session, and when user enters specific page, I want to load those NIDs from session, then get specified node’s fields from Drupal DB according to these NIDs and print content types on page in my module in template.

Is this possible, or am I aiming the wrong way?

Bitcoin core’s estimatesmartfee gives same estimate on ECONOMICAL and CONSERVATIVE mode

I have observed this behavior several times before now, the commands bitcoin-cli estimatesmartfee 2 ECONOMICAL and bitcoin-cli estimatesmartfee 2 CONSERVATIVE give the same estimates.

For example, now I get:

>bitcoin-cli estimatesmartfee 2 ECONOMICAL {   "feerate": 0.00173558,   "blocks": 2 }  >bitcoin-cli estimatesmartfee 2 CONSERVATIVE {   "feerate": 0.00173558,   "blocks": 2 }  >bitcoin-cli estimatesmartfee 144 ECONOMICAL {   "feerate": 0.00036069,   "blocks": 2 }  >bitcoin-cli estimatesmartfee 144 CONSERVATIVE {   "feerate": 0.00036069,   "blocks": 2 } 

I can increase the number of blocks even higher than 144 and I get the same result both. My node has been running uninterrupted for a long time so I found no reason for these values to be wrong. However, what’s the point of having two modes of estimating fees if they give the same

Is throwing exceptions in Debug mode a bad idea? [on hold]

I am working in an iOS project which have two schemes enabled from configurations,

  • Release
  • Debug

As you know Debug scheme is used for developers while developing features and testing etc. However, Release scheme is used for generating official final artefact to upload in App Store. Currently my application quality is not good and many exceptions are not properly handled by developers (most of them are ignored). In current codebase most of the methods are developed in such a way that when exceptions happens they are catched and printed in log. Let’s say here is a pseudocode,

func doSomething() {     do {         //code that might generate exception     } catch let error {         print("Error: \(error)")     } }  

However, I feel many exceptions should be thrown in development phase and developers should invest more time to analyse and fix them. For that reason I want to log exceptions only in Release mode but not in Debug mode. Let’s say my intention is to refactor the above similar code as below,

func doSomething() throws  {      do {         //code that might generate exception e     } catch let error {          #if Release             print("Error: \(error)")         #else Debug             throw error         #endif     } }  

Is there is any other issues might arise for this approach? Is it a bad idea anyway?