I see a lot of fd users that seem to think that they need to add "{}" to all commands. Some users also seem to think that the closing semicolon (which needs to be escaped) \; is required:

fd … -x command "{}" \;

In reality, 90% of the --exec use cases can be written without the "{}" part (which fd adds, if it is ommitted) because the file entry often comes last. The semic

Added object oriented approach for BST. Please review and let me know if any changes are required.

• Adding hints and doctest to old codes
• Reviewing Pending PRs
• Helping new Contributors
• Add more algorithms #14 #195

thank you

When working on a fix for #2755 I noticed that tags are being handled that cannot be used anyway, e.g. tags of disconnected changesets. Similarly, per-branch tags should be constrained to the checked out branch.

When trying to add a field of type constant_keyword to a Mapping, an exception is returned:

DSL class `constant_keyword` does not exist in field.

What happened

Accidentally omitting document content returns 500 Internal Server Error with a body of {"message":"Internal error","uri":"/new_index"}

What was expected

Emitting any kind of helpful message would be helpful. Also, in my experience, when the client receives a 500 response, there is usually something informative on the server-side. But in this case, the server e