Could be a breaking change in NuGet, seems like search doesn't work at all.

$ paket find-packages "FA"
Paket version 5.79.3
Ignoring error when requesting 'https://www.nuget.org/api/v2': Request to 'https://api.nuget.org/v3-flatcontainer/?q=FA&take=10000' failed with: 'BadRequest'
Performance:
 - Average Request Time: 778 milliseconds
 - Number of Requests: 3
 - Runtime: 3 seconds

5.5.3 is the last version that works.

paket find-packages "" doesn't work yet

For me it is working:

{ simplenugetserverpaketrepro } master » .paket/paket.exe find-packages ""                                                                                                                            /c/proj/simplenugetserverpaketrepro
Paket version 5.80.0
Ignoring error when requesting 'http://localhost:5000': Could not retrieve data from 'http://localhost:5000/Packages()?$filter=IsLatestVersion and IsAbsoluteLatestVersion and substringof('',tolower(Id))'
Newtonsoft.Json
NUnit
EntityFramework
jQuery
bootstrap
AutoMapper
NUnit.Runners
Microsoft.AspNet.Mvc
log4net
NuGet.Core
Npgsql
HtmlAgilityPack
SlowCheetah.Xdt
Microsoft.Owin.Host.SystemWeb
NLog
Microsoft.AspNet.SignalR
Microsoft.AspNet.WebApi
jQuery.UI.Combined
AjaxControlToolkit
angularjs
Performance:
 - Average Request Time: 429 milliseconds
 - Number of Requests: 3
 - Runtime: 2 seconds

Hm, for me it's not:

cmd.exe:

$ .paket/paket.exe find-packages ""
Paket version 5.80.0
 - Please enter search text (:q for exit):

zsh/bash:

$ .paket/paket.exe find-packages ""
Paket version 5.80.0
 - Please enter search text (:q for exit):
:q

$ .paket/paket.exe find-packages ''
Paket version 5.80.0
 - Please enter search text (:q for exit):

Do you use magic mode? It seems that the arg is lost in translation:

no I did not in my tests, so yes that could be the reason...

Thanks for posting so quickly, was trying every shell I could find, and all were working ;)

Tested again with the latest bootstrapper. No dice.

So technically it's a different issue which was there ever since magic mode was introduced I guess?

Probably, yes. During completion development I only tested against locally compiled paket.exes since I required args that were not released yet.

Can we open a new one? I'd like to keep that one as a reminder to add a regression test for the initial issue.

Or we can fix the issue :)