eggdrop | least SKIM this document before asking questions | Chat library

You could hold an array containing the user and their join time. Something like (untested):

Your error is in this command:

Well, since there is only one element of row, you don't need to loop on it:

The problem is that you're sending $arg as one string rather than multiple arguments. The fix is probably to do this:

In your json response, there are newline characters in the json. One of the values for _source is null. Python won't be able to treat them as dictionaries. While forming the bulk request, clean up the complete data and hit the bulk API.

Json at 192nd index is having null as _source.

Json at 47th index is having newline characters.

Please cleanup those data while exporting to elasticsearch.

Hope this helps.

It doesn't matter what those floors are. What matters is the number of floors we need to consider. If we have 9 floors and an egg survives the 6th floor, we need to consider the 3 floors above 6: the 7th, 8th, and 9th floor. Another way to think about it is that having to test the floors 7-9 is exactly the same as testing the floors 1-3 (in terms of the number of drops in the worst case).

The problem is in the if condition: there is an extra } after {database_name}. It leads to the body of the procedure being closed too early, and the body of the if command becomes an unintended extra argument to proc (and the very last closing brace becomes an invalid command).

This could be called a parse-time error. If an error makes it all the way to execution (a run-time error) Tcl usually knows enough about the situation to produce a better error message.

At this point though, all the Tcl interpreter knows is that it is trying to execute a command with three arguments, and it has been given four. Hence, the error message is very vague.

However, when a "wrong # args" error is signaled, one has usually either inserted white-space in a place where it shouldn't be, or the braces don't match up. A brace-matching editor is very useful in the latter case.

The problem is formally in code you've not shown, urltitle::parse, since your patterns correctly match both URLs. A good way to determine if that is actually true is to just try running little bits of code in an interactive shell.

I'm guessing that the actual problem is that the youtu.be URL generates an HTTP redirect to the other URL (or one very much like it); Tcl's http library doesn't process redirects for you — it'd be a higher-level layer on top (and if this is the source to the urltitle code then I can see that it isn't doing it) — and the result causes something to choke in a nasty way.

If you're just wanting to support these youtu.be urls, you can the rewrite yourself with regsub immediately before passing the URL into urltitle::parse: