Exact match not being obvious

[Keats]

When doing a search, a crate matching exactly the search will appear first, even if sorted by downloads. I initially thought it was a bug: #396 (comment)

Would it be possible to extract the exact match out of the list and display it differently?

[carols10cents]

Changing this bug's level to medium, because it involves a bunch of little pieces scattered all over. I think each of the pieces individually should be easy, but putting them all together might take a little while.

The pieces:

• SQL: Adding to the SELECT a column that has the value name = $1, which is what indicates that this sort put the crate to the top. Example of how this works:

select id, name, name = 'sassers' as exact_match from crates;
 id |      name       | exact_match
----+-----------------+-------------
  2 | sassers         | t
  6 | piston          | f

• Rust: Adding an exact_match: bool field to the EncodableCrate struct to hold the value from that select query and send it back in the API results. Note that all the other places that EncodableCrate is used should just get false for this field... not sure if adding exact_match: false or implementing the Default trait on EncodableCrate will be more annoying :)

• Ember: Adding the exact_match property to the Ember crate model

• Handlebars: Adding a class to this element if crate.exact_match is true

• CSS: Styling that class to visually differentiate the exact match crate somehow :)

If anyone wants to pick off a piece of this, I'd accept PRs for each little bit separately-- I don't think any of these individually should break other things (famous last words ;) )

[venkatagiri]

@carols10cents I wanted to work on this and ran cargo test before making any changes and few tests are failing trying to upload to S3 bucket. Logs are here http://pastebin.com/Hrei2g7H
README says "No actual requests to s3 will be made". Not sure what's wrong with my setup.

[carols10cents]

Hi @venkatagiri, there is something weird with the .env file and the way crates.io uses env vars that I was hoping to fix before I needed to document it but I haven't yet :( Could you try changing your .env file to have export S3_REGION= instead of whatever you have for that variable?

If you already have that, could you pastebin your .env file, without any usernames, passwords, or keys of course?

Sorry about this! It's totally not your fault.

[venkatagiri]

The S3_REGION variable is empty. Here's the .env file I am using. http://pastebin.com/gLDh31Dn
Just FYI, I have PostgreSQL running in a docker container.

If you can point me to the piece of code where the S3 calls get mocked, I will take a go at debugging this and fix it.

[carols10cents]

Hmm, strange. So in tests, the Config that gets used is defined here, getting S3_REGION from the environment:

crates.io/src/tests/all.rs

Line 86 in 4f9aeb3

s3_region: env::var("S3_REGION").ok(),

The s3_proxy set in the config in the tests comes from record::proxy() The src/tests/record.rs file implements the mocking-- if the tests are run in recording mode, it stores a file of request/response data per test in src/tests/http-data. Then in replay mode (most of the time), when the config gets a request to s3, it tries to play back the data from the file for that test. The error you're seeing comes from this spot in record.rs that validates the request headers, but for some reason your app is creating requests to http://alexcrichton-test.s3-.amazonaws.com and the http-data files have requests to http://alexcrichton-test.s3.amazonaws.com recorded, so the headers don't match up.

This is where the S3 host gets constructed, so the http-data expect S3_REGION to be None but for some reason when you run the tests S3_REGION is Some(""), is what I think the problem is.

Something to try might be removing S3_REGION from your .env file completely, but I'd love to see a more robust solution to this problem. This is kind of related to #470... for some reason that I haven't completely figured out how to change yet, I have to set S3_REGION="" for running the server locally and S3_REGION= when running the tests :(