According to a popular crypto analyst Avalanche has still more room to grow. He says he’s still bullish on the smart contract platform and said it has more room to grow up to more than 280 USD. He’s comparing the movement of Avalanche to Solana’s parabolic move.
Also quoted from the crypto analyst “If the $SOL (Solana) run is anything to go by, then $AVAX (Avalanche) should have plenty of gas left in the tank.”.
Zooming in the crypto analyst chart, seems he plotted that it will go up to 280 USD with a potential of 110% from its current price 128-133 USD.
At the time of the writing the price of Avalanche still swinging from 120-140 USD with an ATR (Average True Range) of 4.2.
Rebasing is one of the features you probably want to have, if you plan to work on a neat git based project.
🍣 Where To Rebase?
If you know how many commits you make, to rebase you use git rebase with -i flag to enable interactive rebasing. The HEAD~<n> corresponds to the number of commits you have done (e.g. HEAD~4 if you have 4 commits to rollback to get to common ancestor commit).
git rebase -i HEAD~<n>
Sometimes, you commit a lot and forgot how many commits you’d make. To know the least common anscestor you have with master, you do git merge-base with your branch name as parameter.
git merge-base <your-branch> master
The above command will return a git hash which you can use on the git rebase command.
If you already know the git hash, then you can rollback to that specific commit and moving all current changes to unstaged. Once, the editor pop-ups you will choose which commit to retain, squash, and reword.
git rebase -i <git-ref-hash>
🍣 Merge Latest From Master
If you’ve already rebased your changes and needed to get lastest changes from master. All you have to do is rebase to the latest changes from master. This command will do that.
git rebase origin/master
In any case, you’ve encountered some conflict first resolve it then continue in rebasing instead of creating new merge commit.
git rebase --continue
🍣 Overwriting Remote Repo Changes
Once all is done, overwrite your remote repo latest changes if you’ve pushed it. This will do a force push ignoring current ref on remote repo.
git push -f
🍣 Did Something Wrong? In Need Of Rollback
Did something wrong on merging conflicts? Don’t worry you can still see your previous changes using the command git reflog short for reference log. You can checkout the reference hash then re-merge your changes.
Window Subsystem Linux v2 (WSL2) is an iteration of the VM created by Microsoft, from Hyper-V to WSL and this the second generation of WSL. If it’s your first time accessing WSL2, it automatically provide you with the default setup which doesn’t provide any limits accessing your full workstation resources (CPU, RAM and other HDD). It means that if you have 8 cores cpu and 16Gb memory, it will use all that up. The problem with it is sometimes it affects your host computer and it gets slow. So to solve that problem we try to limit the resource consumption of WSL2.
Limit WSL Resource Consumption
On your profile directory %USERPROFILE% create a new file named .wslconfig. Set it’s content to the following:
Change the settings base on your workstation capability, and this is what works for me.
Next, open up a powershell terminal in administrator mode and restart the LxssManager as this manages WSL2.
Get-Service LxssManager | Restart-Service
You could also use the wsl --shutdown method to restart WSL. Check if the vmmem process still consumes beyond its limit.
If the changes still not reflecting, try to restart your machine and also restart Docker Desktop.