search for: _anyway_

...I'd probably be happy not to have them indexed. It won't be > perfect, since those file types could exist inside zip files, but maybe > would cut out a bit of the load. Solr itself apparently has 'tika integration' out of the box. Since the solr server instance bundles jetty _anyway_, and it _is_ already up/running ... wondering if the indexing load can be better managed there. iiuc, limits and types can be specified in solr/tika config directly. perhaps Dovecot can be configured to send all messages+attachments, and let solr/tika config 'choose' to index just the m...

...still undergoing polishing, but is already testable. Looked art the qemu side for now, commenting here due to qemu patches not being posted to the list yet (guess that is at least partly already on your todo list): * Both legacy and modern should be switchable. Modern needs to be switchable _anyway_ for backward compatibility with old qemu versions. But legacy should be too, for testing purposes and for new device types which don't need legacy in the first place. * I'd like to see some more flexibility in the pci bar layout. Stuff I have in mind: - New devices which do...

...still undergoing polishing, but is already testable. Looked art the qemu side for now, commenting here due to qemu patches not being posted to the list yet (guess that is at least partly already on your todo list): * Both legacy and modern should be switchable. Modern needs to be switchable _anyway_ for backward compatibility with old qemu versions. But legacy should be too, for testing purposes and for new device types which don't need legacy in the first place. * I'd like to see some more flexibility in the pci bar layout. Stuff I have in mind: - New devices which do...

...appy not to have them indexed. It won't be >> perfect, since those file types could exist inside zip files, but maybe >> would cut out a bit of the load. > > Solr itself apparently has 'tika integration' out of the box. > Since the solr server instance bundles jetty _anyway_, and it _is_ > already up/running ... > ?wondering if the indexing load can be better managed there. Dovecot currently implements separate integrations, first the attachments are sent to tika, then the results are sent to solr. The two could even be running on separate servers. > > iiuc...

...behavior, that is presently failing (and is fixed by changing this option to not filter in this way). I admin I'm personally a little unclear on if this is supposed to actually be illegal or not (and if it is, we might want to special-case the no-argument ambiguity demonstrated in your example _anyway_, since that's fairly common in C...). Regardless of what our defaults are, setting that option should get things going for you, and I apologize for the trouble. Thanks for your detailed reports, and happy callgraph building :) ~Will

I wrote: > I'll keep poking at this some more and let you folks know if I hit any other surprises. Well, that didn't take long. :-) I have found two new surprises in DSCallGraph as built by TDDataStructures. Consider the following program, which is complete and self-contained and which has one simple indirect call site: volatile int unknown; static void red() { } static void

Will Dietz wrote: > This is actually the expected behavior for EQTD :). Expected by you, maybe. :-D > If you switch to TD you'll get better alias-analysis information, and > in this example the correct result. OK, I have switched to TDDataStructures as well, and I am also seeing much better (for my purposes) results in simple tests. I'll keep poking at this some more and

On 15/11/2020 15:49, PGNet Dev wrote: > On 11/15/20 6:33 AM, John Fawcett wrote: >> I've configured a tika server behind an apache proxy which enforces >> basic auth, but sending basic auth credentials for a tika server is not >> currently supported by Dovecot. > > i was _just_ setting up a tika instance behind a nginx proxy with > basicauth in place. > >

Hello all, I''m kinda going through a rocky upgrade to rails 1.1 and I can''t find much on google about this. When I run my tests I get this: $ rake (in /home/www/art2) /usr/bin/ruby -Ilib:test "/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake/rake_test_loader.rb" "test/functional/panoramas_controller_test.rb"

...testable. > > Looked art the qemu side for now, commenting here due to qemu patches > not being posted to the list yet (guess that is at least partly already > on your todo list): Absolutely. > * Both legacy and modern should be switchable. Modern needs to be > switchable _anyway_ for backward compatibility with old qemu > versions. But legacy should be too, for testing purposes and for > new device types which don't need legacy in the first place. I agree. > * I'd like to see some more flexibility in the pci bar layout. Stuff > I have in mi...

...testable. > > Looked art the qemu side for now, commenting here due to qemu patches > not being posted to the list yet (guess that is at least partly already > on your todo list): Absolutely. > * Both legacy and modern should be switchable. Modern needs to be > switchable _anyway_ for backward compatibility with old qemu > versions. But legacy should be too, for testing purposes and for > new device types which don't need legacy in the first place. I agree. > * I'd like to see some more flexibility in the pci bar layout. Stuff > I have in mi...

Thanks for the http://vorbis.com link. That worked. But I looked in the download area and there is no SDK for Mac OS 9. So I am compiling the vorbis code directly into my app. The problem I am having now is that the CodeWarrior 5.0 compiler has a bug with alloca(). It allocates the area on the stack but, under some circumstances, it does not restore the stack pointer at the end of the routine.

Changes since v2: handling for devices without config space (e.g. rng) reduce # of mappings for VQs These patches seem to work fine on my virtio-1.0 qemu branch. There haven't been any bugs since v2: just minor cleanups and enhancements. QEMU side is still undergoing polishing, but is already testable. Rusty, what do you think? Let's merge these for 3.20? Also - will you be doing that

Changes since v2: handling for devices without config space (e.g. rng) reduce # of mappings for VQs These patches seem to work fine on my virtio-1.0 qemu branch. There haven't been any bugs since v2: just minor cleanups and enhancements. QEMU side is still undergoing polishing, but is already testable. Rusty, what do you think? Let's merge these for 3.20? Also - will you be doing that