Do temporary hit points from the Heroism spell keep a troll alive?

The Troll’s Regeneration feature states:

The troll regains 10 hit points at the start of its turn. If the troll takes acid or fire damage, this trait doesn’t function at the start of the troll’s next turn. The troll dies only if it starts its turn with 0 hit points and doesn’t regenerate.

Let’s assume heroism has been cast on the Troll, a spell which states:

[…] Until the spell ends, the creature is immune to being frightened and gains temporary hit points equal to your spellcasting ability modifier at the start of each of its turns […]

Let’s also assume the troll has taken acid/fire damage, and is at 0 HP. What happens at the start of its turn?

Should I keep the default tap delay?

Since I read 300ms tap delay, gone away I always figured it was a good thing.

Now a colleague recenctly told me they was against this because as it is the default behavior it is “accessibility” to keep it.

They also didn’t see any problem with the delay and that they liked the double-tap zoom.

Now I never considered things that way so are there some studies which could back one claim or another?

second HDD keep turning on and off

A PC of mine has 2 hard drive, 1 SSD and 1 HDD. Ubuntu 18.04 was installed on SSD and the HDD was kept as a storage data. the problem has occurred when I try to access the HDD it just some what disconnected itself and I can’t find it from the list even checking with gpart, no show HDD on it. Is there anyway I could check what was the problem with my PC


By RAW, does Astral Projection[5e] allow you to keep your astral body when you leave the Astral Plane?

This spell honestly has me scratching my head with the way it’s worded.

Astral Projection states the following:

If you enter a new plane or return to the plane you were on when casting this spell, your body and possessions are transported along the silver cord, allowing you to re-enter your body as you enter the new plane.

As this is worded, can I remain in my astral body if I so choose?

How long to keep the UI state of an app, when app is in background? (Android)

I’m designing an Android app that lets people observe medical data. Besides seeing live data, users can scroll back to inspect earlier data.

I’m trying to decide if, when a user scrolls back to see older data, then puts the app to the background, and again to the foreground, the app should keep the scrolled-back state or show the latest data.

There are two conflicting goals: One, the UI should keep the state the user left it in, so that they can resume their tasks even after, say, taking a phone call. Two, the most recent data (live data) is quickly visible upon reopening the app.

I see 3 options:

  1. Whenever the app regains focus, scroll to the latest (live) data. Disadvantage: When a user looks at past data, takes a call and comes back to the app, the UI state has changed and he has to navigate to the previous state again.

  2. Always keep the scrolled state, even after days of not opening the app. Disadvantage: The scrolled state is probably not interesting to the user after a while.

  3. Define a time limit after which the app will forget the scrolled state and, when it regains focus, shows the latest data. A reasonable time limit would be 30 or 60 minutes I think.

  4. Let the Android app lifecycle handle it. Basically, when Android decides to kill the app process, forget about scroll state. My problem here is that I don’t know how fast this usually happens, and it might vary depending on the phone performance.

Comparable problems I considered:

  • In messaging apps like WhatsApp, when in a conversation, putting the app in the background and again to the foreground, the conversation is still open (not the overview over all conversation).

  • In Google Calendar, when scrolling back to an earlier date, putting the app to the background and again to the foreground, the calendar is still scrolled back.

In both cases the app maker decided to keep the state, but I don’t know for how long.

What’s the best option? Do you know more about how Android’s app lifecycle plays into this?

Must a component pouch/focus be “out” to be handled, or can I keep it in my pocket?

Ellen the Eldritch Knight is holding a longsword and wants to cast fireball. If she pulls out her component pouch to cast the spell, then (according to this question), she won’t have time during the rest of the action to put it away, so if she gets to make an opportunity attack before her next turn, she won’t be able to use her weapon’s versatile feature. Could this tragedy be avoided by keeping the component pouch in her pocket the whole time and only interacting with it by sticking her hand in her pocket, rather than taking the pouch out of her pocket?

CUPS keep asking for password of print server

At work we just changed our network printers. Printing to them first goes through a pool server. Since the new printer model is different than the old, I wanted to change the driver, but whenever I open the [Printers] system module, I get asked for a password to the print server before I can do anything.

Even trying “lpinfo -v” asks for “Password for username on”

Now in order to print on the previous model, I had a user/password which I know, and it is also saved in cleartext in /etc/cups/printers.conf, so what is it asking for ? And why is it asking now and not before ? And why does it fail ?

At this point I don’t even know how to reset the whole thing and start from scratch.