BFG run is complete! When ready, run: git reflog expire --expire=now --all && git gc --prune=now --aggressive
--
You can rewrite history in Git - don't let Trump do it for real!
Trump's administration has lied consistently, to make people give up on ever
being told the truth. Don't give up: https://www.aclu.org/
--
~/g/aliostad cd deep-learning-lang-detection.git
~/g/a/deep-learning-lang-detection.git git reflog expire --expire=now --all && git gc --prune=now --aggressive
Enumerating objects: 89539, done.
Counting objects: 100% (89539/89539), done.
Delta compression using up to 8 threads
Compressing objects: 100% (89537/89537), done.
Writing objects: 100% (89539/89539), done.
Total 89539 (delta 28336), reused 61123 (delta 0)
~/g/a/deep-learning-lang-detection.git git push
Enter passphrase for key '/Users/alikheyrollahi/.ssh/id_rsa':
Enumerating objects: 89539, done.
Counting objects: 100% (89539/89539), done.
Delta compression using up to 8 threads
Compressing objects: 100% (61201/61201), done.
Writing objects: 100% (89539/89539), 40.83 MiB | 1.01 MiB/s, done.
Total 89539 (delta 28336), reused 89539 (delta 28336)
remote: Resolving deltas: 100% (28336/28336), done.
To github.com:aliostad/deep-learning-lang-detection.git
+ ac12aa680...c51406cc8 master -> master (forced update)
~/g/a/deep-learning-lang-detection.git cd ..
Well they said, I had 24 hours to remove the offending item according to the "remove sensitive data" link which I abided in a matter of a few minutes. They still took down the repo - that is the problem, not sending the notice.
"We're giving you 24 hours to make the changes identified in the following notice:
If you need to remove specific content from your repository, simply making the repository private or deleting it via a commit won't resolve the alleged infringement. Instead, you must follow these instructions to remove the content from your repository's history, even if you don't think it's sensitive:
We just did a benchmarking for a PoC on DocumentDB side-by-side Cassandra. It does the job, I have not yet seen anything revolutionary. Cassandra benchmarks seemed better.
For those who had the opportunity and pleasure of meeting you personally, the day the news broke out was a black day. You are a person who makes a deep impression, your thoughtfulness and very balanced view and how you articulate them. I now read your writings and find them even more compelling: sharp observation and bravery to spell the truth out.
Death is coming to all of us. We all die. Death of some, however, will be a big loss. You, sir, are among them.
I was exactly where you were. I felt I was solving problems that look almost trivial to me. Of course there are lots of hard distributed computing problems at the scale that Facebook and Google operate but not anyone is to work on them.
I found scientific programming: i.e. using Machine Learning and related disciplines to solve hard AI problems. I can guarantee you might get frustrated by lack of success and hardship of challenges but never ever bored.
dude, have you ever used Google Trends? It is a cut and paste from the source. The y axis is the popularity as the title says. It is so obvious even Google has omitted it.
Imperative style means that A has to know about B. In needs to know what is the next step. With reactive it does not. This creates the decoupling. And also not everyone else's protocol. An event is an important business milestones for an order which has nothing to do with the implementation, and if you look, almost all of them are as such.
Yes, but they do them differently. BeeHive is much more opinionated about the message (must be event and has an enveloper) and the Basic Data Structures.
Also BeeHive avoids stateful actors. State is always persistent in HA queues or Basic Data Structure stores.
Have a look at this list https://github.com/github/dmca/blob/master/2020/01/2020-01-2...