zap | Blazing fast, structured, leveled logging in Go

I am experiencing performance problems with a large (wide and long) table that uses a UDF that has variables passed as structured references.

It seems that when a structured reference for a specific cell, eg "[@A]" is passed to the UDF, it flags the whole column, ie "[A]" as dirty and every cell in the column the UDF references is recalculated (this is the source of the performance problem).

I have found that if I change the UDF within the table to use cell address, eg "A2", then the UDF only executes when that cell changes.

To test, create a simple function with debug.print to highlight when it is run:

How can I access the full information about the logging event in uber-zap's hooks?

For example, I am trying to add a zapcore.Field to the logging event, but it does not show up in the zapcore.Entry.

If it is not possible, can I at least have the fully-formatted string somehow? The goal is to send an email/automated message/Sentry/etc in case of errors.

(based on this question: Uber Zap Logger: how to prepend every log entry with a string)

I replaced the Encoder of my uber-zap logger with a custom one to prepend every log entry with a SystemD-friendly error level (), but now after I use the logger with additional fields (With(fields ...Field)), the custom prepending is gone:

I am using my app as a SystemD service and need to prepend every message with an entry level for JournalD like:

Based off the configurations for zap.NewDevelopmentConfig() and zap.NewProductionConfig(), I've assumed that zap writes logs to stderr. However, I can't seem to capture the output in unit tests.

I have the following captureOutput func:

I'm using OpenApi 3. A tool I use, Owasp Zap looks at the OpenAPI doc and creates fake requests. When it gets a 404, it complains that it doesn't have the media type that the OpenAPI promises.

But I didn't write anything in the OpenAPI doc about how 404s are handled. Obviously I can't write an infinite number of bad end points & document that they return 404s.

What is the right way to record this in the OpenAPI yaml or json?

Here is a minimal yaml file... I know for sure that this file does say anything about 404, ie. 404s aren't in the contract so tools are complaining that 404s are valid responses, but 404 is what a site should return when a resource is missing

I am using AWS SES for mail service. Following the package "github.com/aws/aws-sdk-go/service/ses"

using this I found that HTML data is passing as a string

in one of my scenario i want to show year dynamically.. means now i want to show 2021 next year 2022 in mail footer section

I have a command for zap-api-scan.py, but unlike zap-full-scan.py, there seems to be no way to limit these.

via OWASP's official docker image:

I have spent the whole day trying to get my anroid app to sign in using firebase. But no turtorial solved my problem.

I have a firebase Project, and the SHA1 was updated.

I used this code here

The exception only says login faild. I thougt the problem might be the pre installed google app on the emulator, so I tried it on another device, didn't help. I wiped the data on all emulators, didn't help.

What else could I try? Did you have the same problem, how did you solve it?

Edit: