Skip to content

Instantly share code, notes, and snippets.

View palash25's full-sized avatar

Palash Nigam palash25

View GitHub Profile
const (
USER_INDEX_VERSION = "1"
RESPONSE_INDEX_VERSION = "2"
ORGANIZATION_INDEX_VERSION = "1"
)
func index_and_type(typ string, version string, org_id string) (string, string) {
switch type {
case "user":
if version != "" {
{
'size': '0',
'query': {
'bool': {
'filter': [{
'match': {
'formId': '324fds'
}
}, {
'match': {
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
OpenJDK 64-Bit Server VM warning: UseAVX=2 is not supported on this CPU, setting it to UseAVX=1
[2019-05-15T13:26:36,144][WARN ][o.e.b.JNANatives ] Unable to lock JVM Memory: error=12, reason=Cannot allocate memory
[2019-05-15T13:26:36,146][WARN ][o.e.b.JNANatives ] This can result in part of the JVM being swapped out.
[2019-05-15T13:26:36,147][WARN ][o.e.b.JNANatives ] Increase RLIMIT_MEMLOCK, soft limit: 16777216, hard limit: 16777216
[2019-05-15T13:26:36,147][WARN ][o.e.b.JNANatives ] These can be adjusted by modifying /etc/security/limits.conf, for example:
# allow user 'elasticsearch' mlockall
elasticsearch soft memlock unlimited
elasticsearch hard memlock unlimited
[2019-05-15T13:26:36,147][WARN ][o.e.b.JNANatives ] If you are logged in interactively, you will have to re-login for the new limits to take
@palash25
palash25 / The Technical Interview Cheat Sheet.md
Created March 15, 2019 17:49 — forked from tsiege/The Technical Interview Cheat Sheet.md
This is my technical interview cheat sheet. Feel free to fork it or do whatever you want with it. PLEASE let me know if there are any errors or if anything crucial is missing. I will add more links soon.

Studying for a Tech Interview Sucks, so Here's a Cheat Sheet to Help

This list is meant to be a both a quick guide and reference for further research into these topics. It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth. It also will be available as a gist on Github for everyone to edit and add to.

Data Structure Basics

###Array ####Definition:

  • Stores data elements based on an sequential, most commonly 0 based, index.
  • Based on tuples from set theory.
@palash25
palash25 / rabbitmq_client.go
Last active March 3, 2019 17:03 — forked from urey-hiker/rabbitmq_client.go
rabbitmq client in golang.
package client
import (
"context"
"crypto/md5"
"crypto/tls"
"encoding/json"
"errors"
"fmt"
"net"
git clone --depth=1 https://github.com/sclorg/thermostat-container.git
Cloning into 'thermostat-container'...
remote: Enumerating objects: 112, done.
remote: Counting objects: 100% (112/112), done.
remote: Compressing objects: 100% (71/71), done.
remote: Total 112 (delta 7), reused 99 (delta 2), pack-reused 0
Receiving objects: 100% (112/112), 1.14 MiB | 576.00 KiB/s, done.
Resolving deltas: 100% (7/7), done.
Checking connectivity... done.
cd thermostat-container ; \
all: thermostat-container
thermostat-container:
git clone --depth=1 https://github.com/sclorg/thermostat-container.git
cd thermostat-container ; \
git submodule update --init ; \
patch -p 1 -i ../thermostat-container-s390x.patch ; \
make
push:
## make log for memcached image
git clone --depth=1 https://github.com/sclorg/memcached.git
Cloning into 'memcached'...
remote: Enumerating objects: 31, done.
remote: Counting objects: 100% (31/31), done.
remote: Compressing objects: 100% (27/27), done.
remote: Total 31 (delta 1), reused 16 (delta 0), pack-reused 0
Unpacking objects: 100% (31/31), done.

this is my goto copy paste answer that I post everywhere and I'm going to explain you how to solve an issue using an example so I cannot assure you that this would work in case of every issue but my aim is to try to make you understand what and how to think like when solving an issue.

Note this guide assumes that you have some exposure to software devleopment and have built at least one or two of your own applications as a side project. If not then try building a few projects before starting out with OSS dev it would certainly help. Use this guide for ideas.

Get familiar with git and github if you are not already. Best way to do this is to make a little side project and push it to github. You have a lot of time for GSoC so you can make lots of side projects and experiment around with those until you are familiar with the git workflow

Pick up a software that you find interesting

palash25@Lenovo-G50  ~/Dev  perl6 hell.p6
<== 220 smtp.gmail.com ESMTP e131-v6sm38790685pfc.52 - gsmtp
==> EHLO Lenovo-G5
<== 250-smtp.gmail.com at your service, [157.41.45.32]
<== 250-SIZE 35882577
<== 250-8BITMIME
<== 250-STARTTLS
<== 250-ENHANCEDSTATUSCODES<== 250-PIPELINING
<== 250-CHUNKING
<== 250 SMTPUTF8