uber | Uber API client in Go | REST library

You can use an if else statement to check how long broken_name is. Try:

Better answer: as suggested by @Oliver Dain, use zap.AtomicLevel. See their answer for details.

Another option is to create a core with a custom LevelEnabler function. You can use zap.LevelEnablerFunc to convert a closure to a zapcore.LevelEnabler.

The relevant docs:

LevelEnabler decides whether a given logging level is enabled when logging a message.

LevelEnablerFunc is a convenient way to implement zapcore.LevelEnabler with an anonymous function.

That function may then return true or false based on some other variable that changes at runtime:

A few issues:

1. while (fscanf(dict, "%s", word) != EOF) is wrong. You want: while (fscanf(dict, "%s", word) == 1)
2. Faster to store the given word into the table as uppercase. (i.e.) We do toupper only once for each word.
3. The check function will be faster because it can [then] use strcmp instead of strcasecmp [which is slower]
4. If we can add fields to the node struct, we can have it hold a hash value. This can speed up the check function (see NODEHASH in code below).
5. Doing a malloc for each node is slow/wasteful. A pooled/arena/slab allocator can be faster (see FASTALLOC in code below). Again, if we can add a field to the node struct.

There are some other bugs that are documented in the code below (see the "NOTE" comments). I've used cpp conditionals to denote old vs. new code:

I suggest you to use a method by analyzing each part of your string by iterating over each lines (i assume that your string is compose like in your exemple). It is easier to understand and coding it than using a regex.

The exemple below represent your request callback function. I split the code in 3 logics :

• search the filename
• search the line we are interesting with ("Scenario" word)
• extract the ID by filter function

You can after that, easily change you ID filter (txt.substr(0, txt.indexOf(' ')) to use a more proper expression to extract your sentence.

The result is sent to a callback function with as first argument the filename, and as second all ids. Like you did in your exemple.

Try this one:

If original ordering is not important, use DataFrame.stack:

You have to also implement Clone() from the zapcore.Encoder interface. If you wish to keep the parent logger unaltered, you have to construct an actual clone — possibly with the same config, so you might want to store it as a field:

You can use a custom encoder that embeds a zapcore.Encoder.

Embedding the encoder gives you the implementation of all methods "for free" with the same configuration you have now. Then you can implement only EncodeEntry with the additional logic you require.

NOTE: You still have to implement Clone() if you plan to use structured logging, e.g. logger.With(). More info: Why custom encoding is lost after calling logger.With in Uber Zap?

Back to your main question, this is a working example; see the comments in code for additional explanation:

When a task fails, it contains an exception with more information about what went wrong. You should always log that exception to learn the cause of the problem: