Skip to content

Instantly share code, notes, and snippets.

View carlosrbta's full-sized avatar

Carlos Roberto Augusto Junior carlosrbta

View GitHub Profile
{
"files.exclude": {
"xxx/.config": true,
},
"explorer.excludeGitIgnore": true,
"editor.formatOnSave": true,
"[typescript]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[javascript]": {
from operator import le
from selenium import webdriver
from selenium.webdriver.chrome.options import Options
from selenium.webdriver.chrome.service import Service
from selenium.webdriver.common.by import By
from json import dump
import time
import csv
@carlosrbta
carlosrbta / private_fork.md
Last active July 18, 2021 14:14 — forked from 0xjac/private_fork.md
Create a private fork of a public repository

The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.

The correct way of creating a private frok by duplicating the repo is documented here.

For this assignment the commands are:

  1. Create a bare clone of the repository. (This is temporary and will be removed so just do it wherever.)

git clone --bare [email protected]:usi-systems/easytrace.git

@carlosrbta
carlosrbta / GitHub-Forking.md
Created November 4, 2019 14:40 — forked from Chaser324/GitHub-Forking.md
GitHub Standard Fork & Pull Request Workflow

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

import React from 'react'
import { withTranslations } from 'lets-i18n'
import { withRouter } from 'next/router'
import { Redirect, Head } from 'src/components'
import NewTicketDialog from './NewTicketDialog'
class TicketsPage extends React.Component {
render() {
return (
<Redirect.IfNotLogged>
import React from 'react'
import { Drawer } from 'src/components'
const MyDrawer = ({ open, setClose }) => (
<Drawer
pullRight
width={700}
open={open}
setClose={setClose}
className="teste"
1. install openjdk
`sudo apt-get install openjdk-7-jdk`
2. install `android sdk`
# download android sdk
wget http://dl.google.com/android/android-sdk_r24.2-linux.tgz
tar -xvf android-sdk_r24.2-linux.tgz
cd android-sdk-linux/tools
@carlosrbta
carlosrbta / mongo_dump_restore.md
Created July 16, 2018 12:20 — forked from saggiyogesh/mongo_dump_restore.md
Mongodb dump and restore from mlab
  • install mongodb on local machine (mongodump & mongorestore) commands are required.
  • command dumping

mongodump -h xxx11.mlab.com:11 -u user -p password --authenticationDatabase release-db -d release-db -o /home/dumps

**Options** `-h`: mlab host:port, `-u`: db user, `-p`: db user password, `--authenticationDatabase` `-d`: mlab dbname, `-o`: path to store backupfiles
  • restore command, to restore locally

    mongorestore --db dname /home/dumps

Otherwise to restore in mlab, create a new db and replace the options