secmohammed

#image: atlassian/default-image:2
image: python:3.7.3

pipelines:
  tags:
    'v*': # the tag is "vSomthing" like "v-0.4.2"
      - step:
         name: Build docker image and push to AWS ECR
         services:
           - docker

secmohammed

{"lastUpload":"2021-12-13T15:18:30.566Z","extensionVersion":"v3.4.3"}

secmohammed

// run with go test -test.bench Bench

package main

import (
	// "fmt"
	"runtime"
	"sync"
	"sync/atomic"
	"testing"

secmohammed

RESP3 specification

Versions history:

• 1.0, 2 May 2018, Initial draft to get community feedbacks.

Background

The Redis protocol has served us well in the past years, showing that, if carefully designed, a simple human readable protocol is not the bottleneck in the client server communication, and that the simplicity of the design is a major advantage in creating a healthy client libraries ecosystem.

Yet the Redis experience has shown that after about six years from its introduction (when it replaced the initial Redis protocol), the current RESP protocol could be improved, especially in order to make client implementations simpler and to support new features.

secmohammed

// Also available at: https://play.golang.org/p/yTTpB5gB6C

package main

import (
	"fmt"
)

// *****************************************************************************
// Example 1 - Struct vs Struct with Embedded Type

secmohammed

```
const validationSchema = yup.object().shape({
    email: yup
        .string()
        .min(3, emailNotLongEnough)
        .max(255)
        .email(invalidEmail)
        .required(),
    password: yup
        .string()

secmohammed

# If you come from bash you might have to change your $PATH.
# export PATH=$HOME/bin:/usr/local/bin:$PATH

# Path to your oh-my-zsh installation.
export ZSH="/Users/mohammed/.oh-my-zsh"

# Set name of the theme to load --- if set to "random", it will
# load a random theme each time oh-my-zsh is loaded, in which case,
# to know which specific one was loaded, run: echo $RANDOM_THEME
# See https://github.com/robbyrussell/oh-my-zsh/wiki/Themes

secmohammed

First do a commit of your changes

 git add *
 git commit -a -m "local file server commit message"
Then fetch the changes and overwrite if there is a conflict

 git fetch origin master
 git merge -s recursive -X theirs origin/master

secmohammed

• when using the Rule class to check on existence of specific record while validation , a query builder is being returned that can be used for nested checks

Rule::exists('addresses', 'id')->where(function($builder) {
  $builder->where('user_id', auth()->id());
})
                

That's an alternative to creating a couple of "exists" rule like the following: