swipe
BBuildShip
•Created by swipe on 12/4/2024 in #❓・buildship-help
This doc seems out of date or there is something wrong with the file upload trigger
https://docs.buildship.com/connecting-triggers/firebase-file-upload
There is no "buffer" available in Rest API File Upload (Auth). Maybe it's a bug or the documentation needs to be updated to explain how to get the buffer.
4 replies
BBuildShip
•Created by swipe on 11/29/2024 in #❓・buildship-help
Timeout issue (BuildShip slow response) + Twilio workaround?
I have the "slow start" upgrade, but it seems like at least one of our workflows is still timing out at 15 seconds sometimes while Twilio is sending SMS messages to us. This is super critical because it means we essentially lose customer messages.
We need a more robust solution to this problem. Is there any way to ensure more robust delivery of messages, perhaps when BuildShip is having trouble, even if our customers have to wait that's ok.
I'm doubtful setting up a second endpoint that queues the response would fix this, but maybe it would? Maybe a proxy with retry logic (that seems like a feature request).
I've also considered setting up a Twilio function that retries the endpoint a few times, which might buy us more time.
Ideas welcomed!
4 replies
BBuildShip
•Created by swipe on 11/18/2024 in #❓・buildship-help
Wondering about Best Practices around error status codes.
I'm noticing that a lot of my "expected" return status codes like 404 are being reported as "Failed" red dots in the logs, when they aren't in fact errors, but just states that are handled by the app. (example: promo code note found results in a 404). In terms of REST, I believe this to be best practice (?), to use the status codes to represent the api status. Ideally, I'd like "Failed" to appear only for return error 500 statuses. And this would make the most sense to me anyway - why would a 404 be a typical error condition, versus just a normal state of the api?
Am I missing something? Is there a better way to do this?
5 replies
BBuildShip
•Created by swipe on 11/14/2024 in #❓・buildship-help
Cannot migrate to 2.0!
When I click the Migrate button, it just spins and then stops spinning. I cannot access my workflows and it's not even clear if they are running...
4 replies
BBuildShip
•Created by swipe on 6/3/2024 in #❓・buildship-help
Undefined node support
I have a bunch of semi-complex workflows that require that nodes after the branch reference a node within one side of the branch. This works fine if that branch is the one that runs, otherwise I get an undefined node error.
Ideally I could simply write something like: ((x)node && (x)node.us_blue) but instead I get an undefined node error. What am I doing wrong?
3 replies
BBuildShip
•Created by swipe on 3/10/2024 in #❓・buildship-help
Workflow Versioning
When handling client-based requests (from an app), it could be helpful for me to "version" my workflows, so that when I ship a major update to the client, the endpoint url could be versioned (buildshipurl.com/v2/nodename). That way, if I make breaking changes to the workflow at a later date, I won't break my client requests for those still using the older version.
4 replies
BBuildShip
•Created by swipe on 3/10/2024 in #❓・buildship-help
Re-run a query
When diagnosing a client issue, it would be nice to be able to edit and re-run a query from the log, including all headers. I imagine this feature working such that I could tap an icon in the Log, which would populate the test node window, allowing me to edit and then re-run as a test from within BuildShip
2 replies
BBuildShip
•Created by swipe on 2/26/2024 in #❓・buildship-help
Strange UI typing bug
When I type in any field, such as the feather notes box or in any node string, there appears to be a weird race condition going on where various characters are being dropped, moved, and deleted after having been typed; seemingly at random.
To test this, I typed the alphabet and got: abcdefhijlmnoqrtuvxwz
This is a new bug, have not seen this behavior before.
3 replies
BBuildShip
•Created by swipe on 2/20/2024 in #❓・buildship-help
Firebase complex queries (OR, AND)
The current firestore collection query allows for filters, but doesn't seem to support OR queries. Is that true? I'd love to be able to do something like:
val db = Firebase.firestore
val usersRef = db.collection("users")
val queryByAdminOrAge= usersRef.where(Filter.or(
Filter.equalTo("admin", true),
Filter.greaterThanOrEqualTo("age", 18)
))
or
val db = Firebase.firestore
val usersRef = db.collection("users")
val queryByAdminOrAge= usersRef.where(Filter.and(
Filter.equalTo("technology", "Firebase"),
Filter.or(
Filter.equalTo("admin", true),
Filter.greaterThanOrEqualTo("age", 18)
)
))
5 replies
BBuildShip
•Created by swipe on 1/22/2024 in #❓・buildship-help
Bug in Google Sheets Add Row
When you add the node "Google Sheets Add Row" it seems to add a different node called "Get Sheets" with the description "Fetch a Google Spreadsheet using the Google Sheets API". It doesn't accept any parameters for data to add and certainly doesn't seem to know how to add a row.
Seems to be a misconfigured node.
3 replies
BBuildShip
•Created by swipe on 1/22/2024 in #❓・buildship-help
Get Authorization Header Node has incorrect output type
The node is set up to output "string" but the code clearly outputs an object:
export default function getAuthorizationHeader({ req }) {
return { headerValue: req.headers["authorization"] };
}
Not totally sure why it doesn't just output the string...4 replies