marked | Sinatra application for sharing markdown

Overview

I am trying to tabulate time over days under Google Sheets and see each person's availability based on their start and end times which changes almost every week.

File Information I have this Sample Availability Timesheet with two Sheet-Tabs.

Master Sheet-Tab: This Sheet-Tab contains the list of employees with their respective start-time & end-time.

Availability Sheet-Tab: This Sheet-Tab contains the list of employees and a timescale with one hour hop. The resource availability is marked with Y, and by N if the resource is not available using the following formula:

I am working on a data frame df which is as below:

I Would like to use REGEX to match all the tab characters that appear after the first letter or number. As it's possible to see in the image below, I have a hierarchical text file that each level of category is marked with a TAB (\t) character.

After some research I've found out the REGEX that almost fit my desire:

the Regular Expression: \b[\t]{1,}\b

The problem:

As it's possible to see in the image below, this REGEX does not select the TABs that appear after a string that finishes with a dot (1., 2., 3., 4. ...).

Does anyone know how to include in the REGEX this pattern as well?

Here is a partial text of my example:

I am using the SQL connector to capture CDC on a table that we only expose a subset of all columns on the table. The table has two unique indexes A & B on it. Neither index is marked as the PRIMARY INDEX but index A is logically the primary key in our product and what I want to use with the connector. Index B references a column we don't expose to CDC. Index B isn't truly used in our product as a unique key for the table and it is only marked UNIQUE as it is known to be unique and marking it gives us a performance benefit.

This seems to be resulting in the error below. I've tried using the message.key.columns option on the connector to specify index A as the key for this table and hopefully ignore index B. However, the connector seems to still want to do something with index B

1. How can I work around this situation?
2. For my own understanding, why does the connector care about indexes that reference columns not exposed by CDC?
3. For my own understanding, why does the connector care about any index besides what is configured on the CDC table i.e. see CDC.change_tables.index_name documentation

I have a table that's ordered by timestamp, and I only want to keep steps of a consecutive order (marked with * below).
In imperative programming, it would be:

I have a table with customers that I join with a fact table with sales, based on invoices.

What I need from my report is to get in first part the biggest value of sales based on the incoming order type (1,2,3,C,D) for a customer for last year. And in the second part to get the same but for current year. What I get as result from my current query is all incoming order types with the customer revenue made for each of them. I tried with outer apply as subquery to get only the top 1 value ordered by revenue descending, but in the result I get the same - For all order types the customer revenue. Please help! I hope my explanation isn't understood only by me (happens a lot..)

I want to deploy hexo to github page:https://chenjuexu.github.io/

But it did not work like below:

$ hexo generate FATAL YAMLException: can not read a block mapping entry; a multiline key may not be an implicit key (107:18)

I wrote an AppleScript to synch my Reminders (via export to JSON). It runs great... from the Script Editor. As soon as I tried to run it on the command line via osascript, I discovered it hits a wall when it tries to access reminders. After maybe a minute and a half, I get this error:

According to the libevent book:

Deferred callbacks

By default, a bufferevent callbacks are executed immediately when the corresponding condition happens. (This is true of evbuffer callbacks too; we’ll get to those later.) This immediate invocation can make trouble when dependencies get complex. For example, suppose that there is a callback that moves data into evbuffer A when it grows empty, and another callback that processes data out of evbuffer A when it grows full. Since these calls are all happening on the stack, you might risk a stack overflow if the dependency grows nasty enough.

To solve this, you can tell a bufferevent (or an evbuffer) that its callbacks should be deferred. When the conditions are met for a deferred callback, rather than invoking it immediately, it is queued as part of the event_loop() call, and invoked after the regular events' callbacks.

As described above:

1. The event loop fetches a batch of events, and processes them one by one immediately.
2. Before the fetched events are processed, any new event won't be fetched and processed.
3. If an event was marked as BEV_OPT_DEFER_CALLBACKS, then it will be processed after all other events in the same batch are processed.

Provided two callbacks ca and cb. First, ca is called, ca finds evbuffer_A is empty, then writes a message into it.

Then, cb is called, and cb finds evbuffer_A contains a message, then fetch and send it out.

When cb is called, ca's stack has been released. I think there won't be a stack overflow in such a scenario.

So, my question is:

What's the purpose of deferred callbacks in libevent?