Am I going crazy, or do those methods only handle the "blob fetching" part of this equation? I was looking for examples of the "create a File, do a chunked upload, attach said File to an existing object" flow.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 1 2021
Jul 20 2020
Aug 13 2019
Jul 18 2019
Jul 15 2019
For uploading binary blobs, we'd do the reverse: have the client stream the blob into Files, then call an API method with a reference to the object.
Jul 10 2019
Jul 9 2019
Jul 5 2019
Jul 4 2019
Thanks for the report. Fixed in D20642, which may or may not land today because of the holiday.
Jun 26 2019
cd provides "at least once" delivery guarantees.
Jun 20 2019
Jun 19 2019
Apr 19 2019
Apr 18 2019
Apr 11 2019
Apr 10 2019
In T13269#245817, @pasik wrote:well, I'd say for example the "Close as <status> (only acts if task is not already closed)" is useful, and definitely needed.
Move the task to "done" column on the workboard, and the task automatically gets closed. That's handy.
Broadly, it's not clear to me that any of these rules are actually good/useful/worth building.
- Close as <status> (only acts if task is not already closed).
- Reopen as <status>.
Apr 5 2019
Mar 28 2019
Mar 27 2019
Mar 26 2019
Feb 22 2019
Feb 20 2019
Feb 11 2019
This load chart for admin001, where steady state CPU load has dropped from ~20% to ~10%, suggests that the new scheme is legitimately more efficient and the deploy actually changed something:
Feb 10 2019
Feb 5 2019
That upstream bug report is really something else.
Feb 1 2019
Jan 29 2019
Jan 16 2019
When I was messing around with SMS sending last week, I put a rough cut of this together that is capable of sending an SMS using SNS, which has almost the same API as SES: D19982. I can tackle this unless you're already in the middle of it.
Jan 11 2019
Jan 4 2019
This doesn't help if you're committed to that Apache life, but FWIW I'm using nginx 1.15.8 via Homebrew on Mojave without any issues.
Jan 2 2019
Does anyone have experience with an existing Push Notifications As A Service provider? I would naively suggest AWS SNS, because we already depend on other AWS services and it's free for the first 1m pushes, and then $0.50/1m pushes after that. It also wouldn't raise any new data privacy issues for Phacility customers since we wouldn't have to deliver pushes outside of our existing VPC infrastructure. List of supported push targets:
Dec 20 2018
Dec 19 2018
I was also able to get OpenSSH 7.9p1 to build cleanly on OS X Mojave 10.14.2. For posterity:
