Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

mu not finding related message via message id #380

Closed
adamrt opened this Issue · 20 comments

8 participants

@adamrt

version: mu 9.9.5 stable installed via homebrew --with-emacs
osx mavericks

I'm unable to use the include related feature successfully. Anytime I use the feature I get no messages returned. Am I missing something. I didnt find anything special I needed to do during indexing. Here's the steps I'm taking.

And thank you.

Rebuild index just to start fresh

%: mu index --rebuild
indexing messages under /Users/adam/Maildir [/Users/adam/.mu/xapian]
/ processing mail; processed: 4650; updated/new: 4650, cleaned-up: 0
cleaning up messages [/Users/adam/.mu/xapian]
| processing mail; processed: 4666; updated/new: 0, cleaned-up: 0
elapsed: 0 second(s)
/ processing mail; processed: 4666; updated/new: 0, cleaned-up: 0
elapsed: 14 second(s), ~ 333 msg/s

Search for both messages by messageid and find them

%: mu find -u i:m2sir7t8bm.fsf@mydomain.com
Tue Feb 25 09:23:41 2014 My Name <adam@mydomain.com> tests
%: mu find -u i:CACj_FnCdd2sxoWrMnQaFF9_jFTCqX4TeNP11A2WDOW_427oC2Q@mail.gmail.com
Tue Feb 25 09:23:55 2014 My Friend <myfriend@gmail.com> Re: tests

Search for both messages by message id and include-related and Dont find them

%: mu find -u -r i:m2sir7t8bm.fsf@mydomain.com
mu: no matches for search expression
%: mu find -u -r i:CACj_FnCdd2sxoWrMnQaFF9_jFTCqX4TeNP11A2WDOW_427oC2Q@mail.gmail.com
mu: no matches for search expression

Search for both messages by message id and include-related dont remove duplicates

%: mu find -r i:m2sir7t8bm.fsf@mydomain.com
mu: no matches for search expression
%: mu find -r i:CACj_FnCdd2sxoWrMnQaFF9_jFTCqX4TeNP11A2WDOW_427oC2Q@mail.gmail.com
mu: no matches for search expression
@djcb
Owner

I would recommend trying a bit newer version of mu... and indeed it's time to make a new release!

@adamrt

Ok I just upgraded to 0.9.9.6pre2 and rebuilt my index and getting the same results.

It seems that anytime I use -r I get no results. My name is adam and if I do mu find adam I get nearly 5000 results. If i do mu find -r adam I get no results. Any thoughts?

@adamrt

Ok so with a bit more testing I've exhausted the options that I know. To get back to neutral, I've uninstalled and reinstalled mu and xapian, removed ~/.mu completely. Searched by different fields, etc. Tried running with -d and/or -v to no avail.

Still get nothing anytime I use -r on any type of search. Is there a better way to try and debug this?
Thanks

@zickzackv

Since my update to OS X 10.9 is experience the same behavior. The result set is empty when using W in mu4e or mu find -r. I deleted .mu and rebuild the index with the same result.

➜ ~  mu find date:today | wc -l
   22
➜  ~  mu find date:today -r | wc -l
mu: no matches for search expression (4)
   0

My mu version:

➜ ~ mu --version
mu (mail indexer/searcher) version 0.9.9.6pre2
Copyright (C) 2008-2013 Dirk-Jan C. Binnema
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Built from:

➜  mu4e git:(master) git rev-parse HEAD
85f94e1743014393168db1d2a02c680435b8b4ce
@adamrt

I had been running 10.7 until recently and while I wasn't using mu4e full time then I do remember the related feature working. So it may be some 10.9 issue.

@purcell

I'm also seeing this issue, on OSX 10.9.

@adamrt

@djcb Any idea weather this would be xapian or mu issue? I've been search all over but can't seem to find anything.

@adamrt

Just an update. This weekend I downgraded and did a fresh install of Mountain Lion (10.8) and now the related message functionality works.

Unfortunately the multi monitor support is better in 10.9 so I'll be switching back right away.

@djcb
Owner

@adamrt: so it seems something specific to 10.9; are the versions of other libs the same (xapian, mu)?

@adamrt

Yeah it's 10.9. I did a fresh install of 10.8, then installed mu (--HEAD) and xapian (1.2.17) from homebrew. And everything worked perfectly. I then just upgraded to 10.9 with everything intact. Once the upgrade was complete related messages no longer worked. Other than the OS I don't think anything else changed.

@grimradical

On a whim, I tried recompiling and specifying the exact C++11 stdlib to use on 10.9:

env CXXFLAGS='-std=c++11' ./configure && make

Once rebuilt, mu can find related messages just fine.

@adamrt

@grimradical Worked fro me as well! Thanks. What made you try that?

@grimradical

It was a long and winding road. :) First, I had the thought that perhaps it was clang that was causing the issue, so I spent a while installing gcc-48 from homebrew. I tried using that to recompile mu, but I would invariable get errors when trying to link the C++ code, with the error messages being around C++ stdlib functions. After some googling, it turns out that on mavericks they switched from using libstdc++ to libc++. I therefore guessed that using gcc might be a red herring, and instead just tried recompiling using clang but forcing use of a different stdlib (see http://stackoverflow.com/a/19774902/1094818) and it seemed to work afterwards.

@adamrt

Ok so well this is a homebrew/OS X problem then. I'll see if I can get it worked out on that end. Thanks for mu, @djcb!

@adamrt adamrt closed this
@djcb
Owner

Excellent catch @grimradical!

@seanfarley

So, I just ran into this in MacPorts and indeed got this to compile by setting CXXFLAGS='-std=c++11' but that seems to be a red herring. Indeed, compiling with g++ will be difficult due to the system only providing libc++ but it seems that the real culprit was an optimization flag (-Os in this case). So, this is either a compiler bug or something else weird going on with the code path for -r.

@mankoff

Agreed that CXXFLAGS='-std=c++11 isn't the only solution. That worked for me on earlier versions. The latest mu version (on OS X 10.8) doesn't find related even with that flag set.

@mankoff

One more hint - this is a mu4e issue, not mu. Find-related works in mu:

$ mu find date:today |wc -l
      13
$ mu find date:today -r|wc -l
      19

But when pressing w in mu4e, the statusline says [mu4e] Include-related turned on, but no messages are shown in the header view.

@mankoff

Since my current issue appears different (mu finds related, mu4e does not) I've opened a new issue rather than hijack this issue. See #505.

@danieroux

For me, compiling with -O0 and the fix in 17dbee9 sorted it out (finally).

CXXFLAGS='-std=c++11' also works, but intermittently it seems.

@danieroux danieroux referenced this issue from a commit in danieroux/homebrew
@danieroux danieroux Fix the --related option for 10.9
CXXFLAGS='-std=c++11' need to be set for xapian to be happy, it seems.

Fix from: djcb/mu#380
c3f2149
@danieroux danieroux referenced this issue in Homebrew/homebrew
Closed

Fix the --include-related option for 10.9 #37020

@BrewTestBot BrewTestBot referenced this issue from a commit in BrewTestBot/homebrew
@danieroux danieroux Fix the --related option for 10.9
CXXFLAGS='-std=c++11' need to be set for xapian to be happy, it seems.

Fix from: djcb/mu#380
d4ae5d8
@BrewTestBot BrewTestBot referenced this issue from a commit in BrewTestBot/homebrew
@danieroux danieroux Fix the --related option for 10.9
CXXFLAGS='-std=c++11' need to be set for xapian to be happy, it seems.

Fix from: djcb/mu#380
eb389c7
@danieroux danieroux referenced this issue from a commit in danieroux/mu
@danieroux danieroux Add a test case for djcb#380 a36db98
@danieroux danieroux referenced this issue from a commit in danieroux/homebrew
@danieroux danieroux Add a test for mu
The expectation is that mavericks and yosemite will fail this test.

djcb/mu#380 is a tricky one too fix, it seems.
4181c4d
@danieroux danieroux referenced this issue from a commit in danieroux/homebrew
@danieroux danieroux Add a test for mu
The expectation is that mavericks and yosemite will fail this test.

djcb/mu#380 is a tricky one too fix, it seems.
3be3774
@danieroux danieroux referenced this issue from a commit in danieroux/homebrew
@danieroux danieroux Add a test for mu
The expectation is that mavericks and yosemite will fail this test.

djcb/mu#380 is a tricky one too fix, it seems.
8f9d4bc
@danieroux danieroux referenced this issue in Homebrew/homebrew
Closed

Add a test for mu #37077

@BrewTestBot BrewTestBot referenced this issue from a commit in BrewTestBot/homebrew
@danieroux danieroux Add a test for mu
The expectation is that mavericks and yosemite will fail this test.

djcb/mu#380 is a tricky one too fix, it seems.
93724ad
@danieroux danieroux referenced this issue from a commit in danieroux/mu
@danieroux danieroux Add a test case for djcb#380
--include-related fails on some platforms (OSX 10.9 and 10.10) due to a
compilation error.

This test case catches it.
f996d92
@BrewTestBot BrewTestBot referenced this issue from a commit in BrewTestBot/homebrew
@danieroux danieroux Add a test for mu
The expectation is that mavericks and yosemite will fail this test.

djcb/mu#380 is a tricky one too fix, it seems.
8a335af
@danieroux danieroux referenced this issue from a commit in danieroux/homebrew
@danieroux danieroux Fix the mu --related option for 10.9
- Compile with -O0 on >= mavericks
- Add a test for mu
- djcb/mu#380
de55538
@BrewTestBot BrewTestBot referenced this issue from a commit in BrewTestBot/homebrew
@danieroux danieroux Fix the mu --related option for 10.9
- Compile with -O0 on >= mavericks
- Add a test for mu
- djcb/mu#380
3597b7a
@danieroux danieroux referenced this issue from a commit in danieroux/homebrew
@danieroux danieroux Fix the mu --related option for 10.9
- Compile with -O0 on >= mavericks
- Add a test for mu
- djcb/mu#380
1a6c7ca
@BrewTestBot BrewTestBot referenced this issue from a commit in BrewTestBot/homebrew
@danieroux danieroux Fix the mu --related option for 10.9
- Compile with -O0 on >= mavericks
- Add a test for mu
- djcb/mu#380
dd0844c
@danieroux danieroux referenced this issue from a commit in danieroux/homebrew
@danieroux danieroux Fix the mu --include-related option for 10.9
- Compile with -O0 on >= mavericks
- Add a test for mu
- djcb/mu#380
a08835c
@BrewTestBot BrewTestBot referenced this issue from a commit in BrewTestBot/homebrew
@danieroux danieroux Fix the mu --include-related option for 10.9
- Compile with -O0 on >= mavericks
- Add a test for mu
- djcb/mu#380
f756b75
@danieroux danieroux referenced this issue from a commit in danieroux/homebrew
@danieroux danieroux Fix the mu --include-related option for 10.9
- Compile with -O0 on >= mavericks
- Add a test for mu
- djcb/mu#380
d599f8b
@danieroux danieroux referenced this issue from a commit in danieroux/homebrew
@danieroux danieroux Remove MACOSX_DEPLOYMENT_TARGET hack
djcb/mu#332 is the same root cause as
djcb/mu#380 which is fixed by
Homebrew#37020
71fd95f
@danieroux danieroux referenced this issue from a commit in danieroux/homebrew
@danieroux danieroux Remove MACOSX_DEPLOYMENT_TARGET hack
djcb/mu#332 is the same root cause as
djcb/mu#380 which is fixed by
Homebrew#37020
5e85510
@danieroux danieroux referenced this issue from a commit in danieroux/homebrew
@danieroux danieroux Remove MACOSX_DEPLOYMENT_TARGET hack
djcb/mu#332 is the same root cause as
djcb/mu#380 which is fixed by
Homebrew#37020
89bb57e
@BrewTestBot BrewTestBot referenced this issue from a commit in BrewTestBot/homebrew
@danieroux danieroux Fix the mu --include-related option for 10.9
- Compile with -O0 on >= mavericks
- Add a test for mu
- djcb/mu#380
77b4191
@BrewTestBot BrewTestBot referenced this issue from a commit in BrewTestBot/homebrew
@danieroux danieroux Remove MACOSX_DEPLOYMENT_TARGET hack
djcb/mu#332 is the same root cause as
djcb/mu#380 which is fixed by
Homebrew#37020
f9f14d9
@mikemcquaid mikemcquaid referenced this issue from a commit in Homebrew/homebrew
@danieroux danieroux mu: fix --include-related option for 10.9
- Compile with -O0 on >= mavericks
- Add a test for mu
- djcb/mu#380
- Remove MACOSX_DEPLOYMENT_TARGET hack

djcb/mu#332 is the same root cause as
djcb/mu#380 which is fixed by
#37020

Closes #37020.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
3f91fb1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.