optc | This is a calculator for the mobile game One Piece Treasure | Apps library

What about using Stream::of and concat in using reduce:

I am answering my own question

I just found a temporary solution but failed to find what is happening inside retrofit and android and why

Thinking a bit longer about this, this behaviour is perfectly reasonable in the "serverless" model; resources(both CPU and memory) are throttled down to 0 when the service is not processing requests [1], which is exactly what ekg picks up.

Why logs are printed out even outside of requests is still a bit of a mystery, though ..

[1] https://cloud.google.com/run/docs/reference/container-contract#lifecycle

when i try to converting an activity than i get following two errors. 1. getActivity () 2. getContext()

When you change Fragment to Activity, all method need getActivity() and getContext() can be change to this. Example new Intent(getActivity(),finalresult.class); to new Intent(this,finalresult.class);

You are using ImmutableMap, and ImmutableMap does not like null key or value: https://guava.dev/releases/23.0/api/docs/com/google/common/collect/ImmutableMap.html#of-K-V-

public static ImmutableMap of(K k1, V v1)

Returns an immutable map containing a single entry. This map behaves and performs comparably to Collections.singletonMap(K, V) but will not accept a null key or value. It is preferable mainly for consistency and maintainability of your code.

The message is produced by this method: https://github.com/google/guava/blob/82b3e9806dc3422e51ecb9400d8f50404b083dde/guava/src/com/google/common/collect/CollectPreconditions.java#L28

If you copied you database class, but forget to change table name - it can lead to duplication of data.

First, I see no error in your JSON other than you have a spelling error ("b": "glyceraldehde"). So there must be some other issue. The following almost does the job:

There is no need to return a const std::string. You can just return a std::string and the caller can decide if it wants it to be const or not. If you are okay with that, then your function would become

The resolution between your two overloads of asOptional() is done at compile time using the type information available at that time.

The print output is showing you the runtime type.

For #4 the type of optc is known to be Optional at compile time, which conforms to OptionalType, and so the compiler selects the second overload of asOptional().

For #7 the type of t is only known to be some type T at compile time, so the compiler must select the first overload of asOptional(), which results in the double optional result at runtime if t has an optional type.

HTH