connector-sdk | SDK for connecting events to functions | Function As A Service library

by openfaas Go Version: v0.6.4 License: MIT

X-Ray Key Features Code Snippets(1)Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | connector-sdk Summary

connector-sdk is a Go library typically used in Serverless, Function As A Service applications. connector-sdk has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

SDK for connecting events to functions

Support

Quality

Security

License

Reuse

Support

connector-sdk has a low active ecosystem.

It has 46 star(s) with 25 fork(s). There are 4 watchers for this library.

It had no major release in the last 12 months.

There are 13 open issues and 18 have been closed. On average issues are closed in 95 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of connector-sdk is v0.6.4

Quality

connector-sdk has 0 bugs and 0 code smells.

Security

connector-sdk has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

connector-sdk code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

connector-sdk is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

connector-sdk releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

It has 952 lines of code, 38 functions and 10 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed connector-sdk and discovered the below as its top functions. This is intended to give you an instant insight into connector-sdk implemented functionality, and help decide if they suit your requirements.

invokefunction calls the given reader
NewController creates a new controller
buildServiceMap converts a list of functions to a service map
MakeClient returns a new http . Client .
GetCredentials returns basic auth credentials
appendServiceMap appends a service map to a map
NewInvoker creates a new Invoker
NewTopicMap returns a new TopicMap
gatewayRoute returns the route for the gateway
Subscribe registers a response subscriber

Get all kandi verified functions for this library.

connector-sdk Key Features

No Key Features are available at this moment for connector-sdk.

connector-sdk Examples and Code Snippets

Creating your own connector

Lines of Code : 33

License : Permissive (MIT)

Copy


	additionalHeaders := http.Header{}
	additionalHeaders.Add("X-Served-By", "cmd/tester")

	// Simulate events emitting from queue/pub-sub
	for {
		log.Printf("Invoking on topic payment - %s\n", gateway)
		time.Sleep(2 * time.Second)
		data := []byte(

Community Discussions

Trending Discussions on connector-sdk

Running into LinearAlloc overflows midway through integration tests

QUESTION

Running into LinearAlloc overflows midway through integration tests

Asked 2020-Mar-02 at 11:36

This is for a largish 3-4 year running Android project, running on Gradle 5.4.1. Integration testing is with Mockito, espresso and dagger.

I have run into an issue where we are adding a Pendo library to the project, the dependency was added to Gradle as standard. Everything runs fine, until we try to run integration tests (~2000), these are run in shards with Spoon.

Around half way through the integration tests, on random tests each time, we run into a native crash killing the test run, due to LinearAlloc exceeding capacity. Running these tests in isolation, or in their classes locally they pass with no issues and have been stable for a long time.

I brought the whole app back to the known good build, added the Pendo dependency only and this results in the same problem, however I don't believe this is due to Pendo, as I tested by coming back to a known good build (tested on again at this point for sanity) and adding a random new dependency, this resulted in the same problem.

From what I can find this may be something to do with the method limits around Android. I should mention we are using multidex to break the app down. Proguard and minify are also being used.

Part of the issue here is that I'm really not sure what to look at to figure out what's going on to cause this overflow. Following the logs for the test runs, nothing appears to be amiss, bar a fair bit of garbage collection (which I'm guessing means a leak somewhere). I'm unsure if this issue is down to some underlying leak, and the new libraries are pushing something just over the edge, or if there's some dependency limit in android that I'm unaware of, or some other way to break the files down so we aren't causing LinearAlloc to fill up.

From reading, I know the limits of LinearAlloc were upped around Android 5, we are having problems on devices both above (Android 10) and below this (Android 4) and I don't really see much chat around this since 2017, so I feel like I'm missing something obvious, or something is misconfigured in the project given it was setup before then.

Any help would be really appreciated. I've dumped a cut down version of the gradle file below

...

ANSWER

Answered 2020-Mar-02 at 11:36

Okay so this was a fun one, leaving this up incase anyone ever runs into a similar issue.

It seems in this case, the error message we were getting out was fairly misleading. A good way to help diagnose these sort of errors is to look at the tombstone left by the crash, see https://source.android.com/devices/tech/debug/native-crash for more info around that

In this case proguard was our enemy, it seemed to be performing some sort of optimisation on the test code leading to variables being assigned incorrectly and was resolved by adding -optimizations *other optimizations*,!code/allocation/variable this might not work for your particular case, but maybe try configuring proguard to do no optimisation and see if that helps :D

Source https://stackoverflow.com/questions/60420269

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install connector-sdk

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: