Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Answered
Getting error in q2 extension

I created a new extension with the 'Hello world' guide.
The server is running (q2 run)
I can see my extension in the nav bar.
When I click on the extension I get error 500:
{"auditId":399318,"endUserMessage":null,"errorReturnCode":-2,"exceptionMessage":null,"expectedWaitTime":0,"data":{"formId":0,"forms":null,"json":null,"navString":null,"newWindow":false}}
The errors in the console:
2022-09-12T13:39:36.715 tornado.access WARNING 404 POST //AccountDashboard (52.86.164.26) 31.28ms
2022-09-12T13:39:53.802 tornado.access WARNING 404 GET //inspect/AccountDashboard (52.86.164.26) 1.10ms

Posted 4 years ago
Votes Newest

Answers


Hello, there could be a number of things that are wrong, but based on the 404 in the SDK logs, my guess is it is trying to access an entrypoint that isn't there for some reason. I would recommend making a case on https://q2developer.com/support/create?ticketType=Bug with as many details you can give and we will get you working from there. It is quite likely that a quick call with a developer will solve this.

The information I am missing is whether you are working local or on the shared dev, what your repo looks like and what commands leading up to q2 run have you run that this is the result.

Posted 4 years ago
Trey Teter
124 × 2 Administrator