Vladimir Kotal

I tried to reproduce the issue on local disk with a directory created under ~/Desktop from which I stripped write permissions (chmod -w ~/Desktop/tagtest). Observing Tagger with dtruss (https://github.com/joyent/dtruss-osx/blob/master/dtruss) I...

> The original design was that because it was the high-level client, the result (image object or exception in case of failure) was more important to the user than the...

The other thing is that with using the low level build API, one is basically forced to reimplement the gory-details of `docker/models/images.py#build()`, i.e. matching the regex so that image ID...

> Do you think that the issue related to empty/useless documents not being cleaned could explain too that searches sometimes report several times the exact same line in a file...

What does the repository history of the `UcCreatePeriodView.cpp` file look like ? Lots of updates, I guess ?

I've been investigating this for bunch of days. There are 3 issues: - index traversal using the document uid (`QueryBuilder.U`) visits deleted documents in multi-segment index. This is causing the...

I'd say it is all or nothing. Either multi segment indexes work in all aspects of the indexer and webapp, or single segment will have to be forced.

It seems I managed to reproduce the case number 3. Previously, the approach I took was a carefully staged small sequence of changes (eventually destined to be a test case)...

Looking into the search results, all the returned documents are actually live, i.e. not deleted. In the index there was just one deleted document with the `IndexDatabase.java` path and it...

I wondered how the multiple live documents matching single path come into existence. By using `NoMerge` index writer settings and carefully stepping through certain changesets in OpenGrok Git repository history...