Turns out it is a known issue
https://bugs.chromium.org/p/chromium/issues/detail?id=811403
On Wednesday, June 27, 2018 at 5:55:21 PM UTC-7, zcw wrote:
>
> Hello,
>
> We found a strange behavior with timezone. I tested the following with the
> v8_shell.
> running:
Hello,
We found a strange behavior with timezone. I tested the following with the
v8_shell.
running:
var d =new Date()
d.getTimezoneOffset()
It will give me 420 which is correct for PDT. but if I set the TZ variable
by doing:
export TZ=:/etc/localtime
and running the above script again, it giv
etup doesn't allow you to modify V8's source.
>
> Maybe it's easiest to just keep the default console.log implementation,
> letting it print to stdout and redirecting the output of the process to a
> file?
>
> On Wed, Jun 27, 2018 at 11:37 AM zcw >
> wrote:
-7, zcw wrote:
>
> Hello Jakob,
>
> May I get some more directions for using the consoleDelegate?
> From d8 files. I saw that we could make a console class and use set
> consoleDelegate to set console functions.
> But in our old way, we create a global template fo
erow wrote:
>
> On Mon, Jun 25, 2018 at 8:30 PM zcw >
> wrote:
>
>> Thank you so much!
>> I wanted to save the log to a specific file. I tried using the provided
>> console but couldn't find where it stored the log message.
>>
>
>
Thank you so much!
I wanted to save the log to a specific file. I tried using the provided
console but couldn't find where it stored the log message.
And could the ConsoleDelegate work for the release build?
On Monday, June 25, 2018 at 6:14:42 PM UTC-7, Jakob Kummerow wrote:
>
> V8 now provides
