OS: Mac OS Sonoma 14.7.4
Cursor version: 0.50.5 (although it’s possible this error occurred before updating to the latest version this week)
I unfortunately cannot reliably tell how to reproduce this, but I’ve run into a bug where Cursor seems to start spitting out literal Lisp code, which looks like the code it should be running to generate the chat, rather than the chat itself.
For example, this was one output, and the repeated parens and quote at the end were just being printed out infinitely until I told it to stop.
After that, we'll run "yarn db:schema:update" (or "./scripts/patient-data-migration/update-local-schemas.sh") (which (among other things) runs "prisma migrate diff" (and "prisma db execute") for the "accounts" service (and others) so that the local (and test) schemas (for "accounts") match the demo (or "chore/sc-390007/update-prisma-schemas") (diff)–generated SQL (and then (if needed) "prisma db execute" (or "prisma migrate deploy") (for "accounts") (so that the "accounts" (and "accounts_test") (schema) (diff)–changes (from "chore/sc-390007/update-prisma-schemas") (are applied (and (then (if (you'd like) (you (or (I) (can (run (for example ("yarn (or "npx") (prisma (introspect (or "prisma (db (pull" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" (" ("
Update: confirmed that I am seeing this in the current version of cursor. Here is an example with prompt included:
User
Make a curl request for this card (i.e. to /card_info) on the real host that is running on port 4567
Assistant
I’ll make a curl request to the server running on port 4567 to check the actual response for “Mox Diamond”:
curl -X POST -H "Content-Type: application/json" -d '{"card_name":"Mox Diamond"}' http://localhost:4567/card_info
{"success":true,"prices":{"Near Mint":{"price":"$0.0","url":null}},"legality":"legal"}%
I see that the real server (on port 4567) returns a response with:
• success: true
• prices: { “Near Mint” => { price: “$0.0”, url: null } }
• (and a legality key (for example, “legal”)).
In other words, the real server (on port 4567) behaves as follows:
– It does not return an error (i.e. no “error” key) when no valid products are found (or when the card is “invalid”).
– It returns a dummy “Near Mint” price (with “$0.0” and a nil url) (and a “legality” key) (for example, “legal”) (even if the card (or “invalid” card) isn’t found).
What this means:
• The test (on port 4568) (which (for “invalid” cards) expects an “error” key (with “No valid products found”) (and (for “Mox Diamond”) expects a “Near Mint” price (with a real price (matching /^$\d+.\d+$/) and a real (product) url (matching /^https://www.tcgplayer.com/product/\d+/))) (is not matching the real (production) behavior (on port 4567).)
Next steps (if you want the test (on port 4568) to “pass” (i.e. match the real (production) behavior (on port 4567))):
• (Option 1) (Recommended (for clarity)):
– Update the server (on port 4568) (for example, in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or (in (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or ( (or (
Here’s a particularly egregious and frustrating example. I eventually had to tell Cursor to stop printing the diff.
