Srijan Choudhary

Hi, I'm Srijan Choudhary.

I'm a founding member and software engineering leader at GreyOrange, working on disrupting and redefining fulfillment.

I'm interested in software team leadership, functional programming, distributed systems, artificial intelligence, and software infrastructure.

In my free time, I enjoy traveling, running, playing with technology, listening to music, creating music, and reading.

I write here when I have something to share - a personal project, some difficult problem I solved recently, or just an idea.

Take a look at the about page for more details, or follow me on mastodon.

Recent Articles

Recent Notes

Srijan Choudhary Srijan Choudhary
> Reply to Issues ยท Hanno Perrey / khalel ยท GitLab

Ability to pass options (before command) to vdirsyncer

Hi. I've been using khalel + khal + vdirsyncer for the last few days, and it has been an absolute joy. I tried various ways of working with my work calendar in my org system, and this has been the best in terms of stability and simplicity.

However, in my setup, vdirsyncer shows a lots of warnings for "Skipping identical href" or "Server did not supply properties" - possibly because I'm syncing with a pretty old google calendar that might have some bad entries. I want to run sync with vdirsyncer -verror sync to silence these warnings in the output of khalel-run-vdirsyncer, but continue to show errors.

I could not find a way to make this configurable, because the -v flag comes before the sync command, and setting khalel-vdirsyncer-command to vdirsyncer -v does not work.

Similarly, someone could have the use case of passing a different config file using vdirsyncer -c .custom/location sync (I don't).

So, I think a way to configuring custom flags for vdirsyncer makes sense.

Syndicated to:
Srijan Choudhary Srijan Choudhary
> Reply to Issues ยท jeanparpaillon/erlang-dbus ยท GitHub

Error when introspection results have a root node element without name attribute

The name attribute is optional for the root node element in introspection results.

From https://dbus.freedesktop.org/doc/dbus-specification.html#introspection-format :

Only the root <node> element can omit the node name, as it's known to be the object that was introspected. If the root <node> does have a name attribute, it must be an absolute object path. If child <node> have object paths, they must be relative.

When writing a test case for another issue, I found that dbus services written using C++ QT Dbus library can cause this issue.

I will raise a pull request to fix both of these issues including test cases.