Full Blog TOC

Full Blog Table Of Content with Keywords Available HERE

Monday, August 21, 2023

Publish Android Library AAR to Maven Central


 

In this post we will review the steps required to publish an Android library as an artifact in maven central. This is required when we create an Android library that we want our customers to use, without the need to manually download files, and also allows the customers to enjoy the maven dependency management.


The procedure below includes 3 steps:

1. Create a local maven artifact

2. Create a new project in maven central

3. Manually upload the artifact to maven central


Create A Local Maven Artifact

Open the project in Android Studio, make sure the gradle version is at least 7.1.

This is visible through the File menu, Project Structure, Project (on the right bar).



Now, open the build.gradle under the library folder, and add maven-publish plugin right below the existing android library plugin:



Next, in the same file, right after the android root element, add the publishing:



The full text of the publishing element is below. Notice that I've used my-company and my-library, but feel free to replace with the text that describes the relevant company/library. Notice that this company name must be under your ownership at github.




After updating the gradle, we need to rebuild the library.



And finally, run the publish: under the Android Studio gradle tab, select the library project, then under tasks, publishing, select publishReleasePublicationToMavenLocal.



The built maven artifact is now available in ~/.m2/repository/io/github/my-company/my-library


Create a New Project in Maven Central

1. Create new github user by the company name. For example:

https://github.com/my-company/my-library


2. Create new user in Sonatype: https://issues.sonatype.org/secure/Signup!default.jspa


3. Create ticket to create new project: https://issues.sonatype.org/browse/OSSRH-94213

You must prove ownership on the project ID, so either own the DNS or use GitHub and prove ownership on the GitHub user. I have chosen github. Once the ticket is open, follow the instructions in the ticket to prove ownership.


4. Create gpg keys:

gpg --full-gen-key

# select 1

# select 4096

# select 0

# enter name and email

# comment can be empty

gpg --list-keys

gpg --keyserver keyserver.ubuntu.com --send-keys THE_KEY_ID_SHOWN_IN_THE_LIST_KEYS

gpg --export-secret-keys THE_KEY_ID_SHOWN_IN_THE_LIST_KEYS| base64



Manually Upload The Artifact To Maven Central

Basically this steps can be automated, see steps here:

However, I would not recommend doing this automatically, as it is very complicated process, and not expected to be run many times in most scenarios.

The manual steps are listed here:
But we provide details below, so keep on reading below.


1. Run gpg for each file:

cd ~/.m2/repository/io/github/my-compant/my-library/1.0.0/
rm -f my-library-1.0.0.aar.asc
rm -f my-library-1.0.0.pom.asc
rm -f my-library-1.0.0.module.asc
gpg -ab my-library-1.0.0.aar
gpg -ab my-library-1.0.0.pom
gpg -ab my-library-1.0.0.module
rm -f bundle.jar
jar -cvf bundle.jar *


3. Select “Staging Upload” on the left bar




4. Select Artifact bundle

5. Select the file ~/.m2/repository/io/github/my-company/my-library/1.0.0/bundle.jar and upload


6. Select “Staging Repositories” on the left bar



7. Select the uploaded repository, and click Close button on the top



8. In case of failures, the reasons appears on the bottom under the activity tab:



9. Finally, release the library using the release button


Monday, August 14, 2023

Compacting JSON Representation in GoLang



In this post we will review a method to shrink JSON representation of Go structures. This is critical in case we need to save the state by marshaling the state objects and save them in Redis, which works really bad with large bulk of strings.

Let dive in quickly with an example. Let assume our state is represented by a struct, and see the JSON representation of it:


package main

import (
"encoding/json"
"fmt"
"time"
)

type DetectorConfig struct {
AnomalyThreshold float32
AnomalyPattern string
EnableDetection bool
}

type State struct {
Counter int
Stations []string
Detector DetectorConfig
LastUpdateEpoch int64
}

func ProduceDefaultState() *State {
return &State{
Counter: 0,
Stations: []string{"load", "build", "deploy", "test", "deliver"},
Detector: DetectorConfig{
AnomalyThreshold: 5.55,
AnomalyPattern: ".*",
EnableDetection: true,
},
LastUpdateEpoch: time.Now().Unix(),
}
}

func main() {

state := ProduceDefaultState()
bytes, err := json.Marshal(state)
if err != nil {
panic(err)
}

jsonText := string(bytes)
fmt.Printf("JSON length is: %v, JSON text is: %v", len(jsonText), jsonText)
}


And the output is:


JSON length is: 178, JSON text is: {"Counter":0,"Stations":["load","build","deploy","test","deliver"],"Detector":{"AnomalyThreshold":5.55,"AnomalyPattern":".*","EnableDetection":true},"LastUpdateEpoch":1691996599}


How can we compact it?

We could use the `json` annotation to use shorter names for the elements, but then we will not be able to display a clear and user friendly JSON to the system admin. A better method would be to decide upon need whether to use clear and user friendly JSON representation when displaying the state to a human, and whether to use a compact JSON representation when saving the state to a DBMS such as redis.

Here is an example of using the compact form:


package main

import (
"fmt"
jsoniter "github.com/json-iterator/go"
"time"
)

type DetectorConfig struct {
AnomalyThreshold float32 `compact:"a"`
AnomalyPattern string `compact:"b"`
EnableDetection bool `compact:"c"`
}

type State struct {
Counter int `compact:"a"`
Stations []string `compact:"b"`
Detector DetectorConfig `compact:"c"`
LastUpdateEpoch int64 `compact:"d"`
}

func ProduceDefaultState() *State {
return &State{
Counter: 0,
Stations: []string{"load", "build", "deploy", "test", "deliver"},
Detector: DetectorConfig{
AnomalyThreshold: 5.55,
AnomalyPattern: ".*",
EnableDetection: true,
},
LastUpdateEpoch: time.Now().Unix(),
}
}

func main() {
state := ProduceDefaultState()
jsonCompact := jsoniter.Config{TagKey: "compact"}.Froze()
bytes, err := jsonCompact.Marshal(state)
if err != nil {
panic(err)
}

jsonText := string(bytes)
fmt.Printf("Compact JSON length is: %v, compact JSON text is: %v", len(jsonText), jsonText)
}


and the output is:


Compact JSON length is: 102, compact JSON text is: {"a":0,"b":["load","build","deploy","test","deliver"],"c":{"a":5.55,"b":".*","c":true},"d":1691996466}


But can we do better?

What if out state is mostly static, and only a few fields are changing? Then we can list only the fields that change, and merge them in to the default config.


package main

import (
"encoding/json"
"fmt"
"radware.com/proximity/commons/global/reflectionapi"
"time"
)

type DetectorConfig struct {
AnomalyThreshold float32 `compact:"a"`
AnomalyPattern string `compact:"b"`
EnableDetection bool `compact:"c"`
}

type State struct {
Counter int `compact:"a"`
Stations []string `compact:"b"`
Detector DetectorConfig `compact:"c"`
LastUpdateEpoch int64 `compact:"d"`
}

func ProduceDefaultState() *State {
return &State{
Counter: 0,
Stations: []string{"load", "build", "deploy", "test", "deliver"},
Detector: DetectorConfig{
AnomalyThreshold: 5.55,
AnomalyPattern: ".*",
EnableDetection: true,
},
LastUpdateEpoch: time.Now().Unix(),
}
}

func main() {
state := ProduceDefaultState()
state.LastUpdateEpoch = time.Now().Add(time.Second).Unix()
state.Detector.EnableDetection = false

defaultState := ProduceDefaultState()
diffMap := reflectionapi.CreateDiffMap("compact", defaultState, state)
bytes, err := json.Marshal(diffMap)
if err != nil {
panic(err)
}

jsonText := string(bytes)
fmt.Printf("Diff JSON length is: %v, diff JSON text is: %v", len(jsonText), jsonText)
}


And the output is:

Diff JSON length is: 32, diff JSON text is: {"c":{"c":false},"d":1691996360}


Of course the length had significantly reduced, and will be reduced much further the bigger is our state, and the less updated fields it includes.


The reflection library is below:


package reflectionapi

import (
"fmt"
"reflect"
"strings"
)

type DiffHandler func(
elementPath string,
value1 interface{},
value2 interface{},
)

func FindDiff(
tagForName string,
item1 interface{},
item2 interface{},
handler DiffHandler,
) {
findDiffRecursive(
tagForName,
"",
item1,
item2,
handler,
)
}

func findDiffRecursive(
tagForName string,
prefix string,
item1 interface{},
item2 interface{},
handler DiffHandler,
) {
reflectType := reflect.TypeOf(item2).Elem()
reflectValue1 := reflect.ValueOf(item1).Elem()
reflectValue2 := reflect.ValueOf(item2).Elem()

for i := 0; i < reflectType.NumField(); i++ {
fieldType := reflectType.Field(i)
useName := fieldType.Name
if tagForName != "" {
useName = fieldType.Tag.Get(tagForName)
}

value1 := reflectValue1.Field(i).Interface()
value2 := reflectValue2.Field(i).Interface()

path := prefix + "/" + useName
switch reflectValue2.Field(i).Kind() {
case reflect.Struct:
interface1 := reflectValue1.Field(i).Addr().Interface()
interface2 := reflectValue2.Field(i).Addr().Interface()
findDiffRecursive(tagForName, path, interface1, interface2, handler)
break
case reflect.Slice:
value1String := fmt.Sprintf("%v", value1)
value2String := fmt.Sprintf("%v", value2)
if value1String != value2String {
handler(path, value1, value2)
}
break
default:
if value2 != value1 {
handler(path, value1, value2)
}
break
}
}
}

func CreateDiffMap(
tagForName string,
itemBaseline interface{},
itemChanged interface{},
) map[string]interface{} {
diffMap := make(map[string]interface{})

handler := func(elementPath string, valueBaseline interface{}, valueChanged interface{}) {
diffMapEntry := diffMap

sections := strings.Split(elementPath, "/")
sections = sections[1:]

for {
sectionName := sections[0]
if len(sections) == 1 {
diffMapEntry[sectionName] = valueChanged
break
} else {
sections = sections[1:]
nextEntry := diffMapEntry[sectionName]
if nextEntry == nil {
nextEntry = make(map[string]interface{})
diffMapEntry[sectionName] = nextEntry
}
diffMapEntry = nextEntry.(map[string]interface{})
}
}
}

FindDiff(tagForName, itemBaseline, itemChanged, handler)

return diffMap
}













Monday, August 7, 2023

Simplifying creation of Go applications on Google Cloud - Post Review


TL;DR

Google seems to stop having new ideas, so it just publishes nonsense as if it was news


Once in a while I read the blogs for some frameworks such as GCP, AWS, and K8s.

Some of the updates are marketing posts, but among them we can find some interesting news. Lat week, checkin gthe GCP blog, I've found the post Simplifying creation of Go applications on Google Cloud. This post seems promising, as a framework for Go applications is something that takes time to build, and I thought I might find interesting ideas there.

The post includes 4 templates:


"

  • httpfn: A basic HTTP handler (Cloud Function)

  • pubsubfn: A function that is subscribed to a PubSub topic handling a Cloud Event (Cloud Function)

  • microservice: An HTTP server that can can be deployed to a serverless runtime (Cloud Run)

  • taskhandler: An basic app that handles tasks from requests (App Engine)

"


So I've checked the templates, and was very disappointed. Most of the templates include less than 10 lines of banal code. It seems that someone in google thought that adding sample code that does almost nothing is good enough to be published in the GCP blog.


The question asked here is: what are the expectations from such a post?


The answer is framework and standards!


Instead of a naive example for HTTP server handler function, add a framework to wrap the HTTP handler, add error handling and logging as part of the HTTP wrapper, add some built-in handlers to the HTTP server, such as pprof profiling capabilities, and setup standards for code design and style.

Most of the projects I've been part of have a major part of the code in the "common" libraries. These common libraries provide a real template for new applications, making them more robust, simple to create, and set code and design standards to the application using the libraries.

A partial list of such libraries is:

  • Logging, log level, logger handler
  • Error handling (panic, recover)
  • HTTP web server wrapper
  • Scheduler wrapper
  • Extend core functionality for: io, slices, strings, parallelism, time
  • Testing wrapper

While adding usage such set of libraries to existing application is almost impossible, this can set a standard to new applications, and this is what I expect from Google - to setup standards. I hope next post would be more in this direction...