high-performance

Describe the solution you'd like
It'd be nice to actually apply the security framework when building.

Describe alternatives you've considered
Ignoring security problems won't help.

ActorAdapter will ignore null message with "Adapter function returned null which is not valid as an .."

However, this seems not be documented. For instance, scaladoc/javadoc of pipeToSelf could mention it as well as any other place where adapters are used.

What language are you using?

C++

What operating system (Linux, Ubuntu, …) and version?

Linux

What runtime / compiler are you using (e.g. jdk version or version of gcc)

4.8.5

Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
tars的发布流程：tarsweb上传安装包 -> tarsAdminRegistry开始发布 -> tarspatch 从/usr/local/app/p

In NIOFoundationCompat we already have a bunch of useful convenience for ByteBuffer + JSONEncoder/JSONDecoder. We should have the same for JSONSerialization. For example:

try JSONSerialization.jsonObject(with: Data(buffer: byteBuffer), ...)

is tedious, we could directly have

try JSONSerialization.jsonObject(buffer: byteBuffer, ...)

Links to all modules are broken because of renaming

Version:

• v2.x.x
• v1.x.x

Issue type:

• Bug
• Proposal/Enhancement
• Question
• Discussion

This is admittedly a problem that bothers us in internal portal usage more than real customers (who tend not to have so many db versions)

When there's many db versions available to YW, the default db software version in Create Universe flow (first version in the list below) seems to be based on sort order. Instead we should default the DB version to the same as the current Platform version (in

Heston model has accurate density approximations for European option prices, which are of interest.

The module implementing this method should live under tf_quant_finance/volatility/heston_approximation.py. It should support both European option puts and calls approximations. Tests should be in heston_approximation_test.py in the same folder.

Currently we have a mix of:

• Out of memory error.
• Out of memory error
• out of memory error
• out of memory
• out of memory.
• out of memory [some context]

All these should be adjusted to use the same wording for consistency and it should also make the executable a little bit smaller 😄