Skip to content
#

Serverless

Serverless architecture refers to apps that depend on third-party services (backend as a service, or BaaS) or custom code (functions as a service, or FaaS). Their goal is to free the developer and operator from managing the server their code runs on.

Here are 7,103 public repositories matching this topic...

cube.js
florian-fischer-swarm
florian-fischer-swarm commented Mar 1, 2021

Describe the bug
Incremental refreshkey with updateWindow for pre-aggregation generates broken SQL for MSSQL

To Reproduce

Setting up an incremental update for a pre-aggregation like this (ignore bogus values):

 somePreaggregation: {
            type: `rollup`,
            measureReferences: [somecount],
            timeDimensionReference: timestamp,
            granularity
fission
swaroopnuli
swaroopnuli commented Sep 19, 2020

Is your feature request related to a problem? Please describe.

Missing functionality to update min/max cpu/mem of an exiting ENV. Currently, to update, we are forced to delete and re-create the env. This also has a risk of dependent functions being erratic. It also de-couple resource utilization independent of function creation and be useful to update the resource in a quick to respond situ

rabbah
rabbah commented Apr 2, 2020

The typescript runtime was recently added to openwhisk but we do not yet have docs for the runtime and it is missing from runtimes.json.

We need a doc like https://github.com/apache/incubator-openwhisk/blob/master/docs/actions-nodejs.md for typescript functions.

Adding the runtime to the runtime manifest can be done per https://github.com/apache/openwhisk/blob/master/docs/actions-new.md#the-

rdallman
rdallman commented Jun 13, 2018

this will very quickly get out of hand if we allow it, i realize we don't have principles written down anywhere but to date one of them has been that binaries 'just work' without having to do any configuration. currently a user must set FN_MAX_REQUEST_SIZE, FN_MAX_RESPONSE_SIZE -- neither of these should be required to run.

test case:

cd tests/fn-system-tests/
go test -v

this

appwrite
eldadfux
eldadfux commented Oct 27, 2020

We want to use caching to speed up Appwrite's Travis CI build process, and we can use the community help here.

Currently our build process time is around ~10 minutes which is OK, but as faster it can be less time maintainers needs to wait for confirmation that there changes are running as expected.

This change should be focused on our Travis CI YAML file. Any suggestions for improving the co

Wikipedia
Wikipedia