Git Product home page Git Product logo

clmystery's Introduction

The Command Line Murder

.OOOOOOOOOOOOOOO @@                                   @@ OOOOOOOOOOOOOOOO.
OOOOOOOOOOOOOOOO @@                                    @@ OOOOOOOOOOOOOOOO
OOOOOOOOOO'''''' @@                                    @@ ```````OOOOOOOOO
OOOOO'' aaa@@@@@@@@@@@@@@@@@@@@"""                   """""""""@@aaaa `OOOO
OOOOO,""""@@@@@@@@@@@@@@""""                                     a@"" OOOA
OOOOOOOOOoooooo,                                            |OOoooooOOOOOS
OOOOOOOOOOOOOOOOo,                                          |OOOOOOOOOOOOC
OOOOOOOOOOOOOOOOOO                                         ,|OOOOOOOOOOOOI
OOOOOOOOOOOOOOOOOO @          THE                          |OOOOOOOOOOOOOI
OOOOOOOOOOOOOOOOO'@           COMMAND                      OOOOOOOOOOOOOOb
OOOOOOOOOOOOOOO'a'            LINE                         |OOOOOOOOOOOOOy
OOOOOOOOOOOOOO''              MURDERS                      aa`OOOOOOOOOOOP
OOOOOOOOOOOOOOb,..                                          `@aa``OOOOOOOh
OOOOOOOOOOOOOOOOOOo                                           `@@@aa OOOOo
OOOOOOOOOOOOOOOOOOO|                                             @@@ OOOOe
OOOOOOOOOOOOOOOOOOO@                               aaaaaaa       @@',OOOOn
OOOOOOOOOOOOOOOOOOO@                        aaa@@@@@@@@""        @@ OOOOOi
OOOOOOOOOO~~ aaaaaa"a                 aaa@@@@@@@@@@""            @@ OOOOOx
OOOOOO aaaa@"""""""" ""            @@@@@@@@@@@@""               @@@|`OOOO'
OOOOOOOo`@@a                  aa@@  @@@@@@@""         a@        @@@@ OOOO9
OOOOOOO'  `@@a               @@a@@   @@""           a@@   a     |@@@ OOOO3
`OOOO'       `@    aa@@       aaa"""          @a        a@     a@@@',OOOO'

There's been a murder in Terminal City, and TCPD needs your help.

Before you start, skim through the required materials in the Command Line and Version Control sections of the PreCourse on Teachable. Use it as a reference while working through the case.

Now with your Terminal at hand you're ready to start. A couple of ground rules first:

  • Don't use a text editor. You will find that the command line is an incredibly powerful tool on its own.
  • You can use Google, PreCourse materials, cheatsheets or any other materials available.

To the investigation!

Step 1: Get the repo

First you need to fork this repository. To do that click on the "Fork" button in the upper right corner of this page. Forking a 'repo' creates a copy of the repository on your Github account. This gives you your own version of the project to experiment with.

Fork

Next you need to download those files to your machine so that you can edit them. To do that you must clone your forked repository. See this Github guide on how to do this.

Step 2: Investigate

Each step of your investigation will contain a reference to the Detective Handbook at the top. Each page of the Detective Handbook contains the description of the commands you will need to complete that particular step.

Open a Terminal, go to the location of the files (using the cd command), and start by reading the file 'step0'.

One way you can do this is with following command:

cat step0

(cat is a command that will print the contents of the file called step0 for you to read.)

Credits

By Noah Veltman Projects: noahveltman.com GitHub: veltman Twitter: @veltman

Adapted by the Makers Academy Team

clmystery's People

Contributors

anitacanita avatar dbugsy avatar edwardandress avatar mathnerd314 avatar oceansize avatar roidriscoll avatar ruthmoog avatar smylers avatar soph-g avatar tommyoswinwilliams avatar veltman avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

clmystery's Issues

Grepping on Step6 clmystery

I know there's previously been an issue on this that has been closed but when I try the solution from there it doesn't work. This is what I'm using to get back multiple lines of text using grep (while in the mystery directory);

grep -A 5 L337 vehicles | grep -A 4 -B 1 Honda vehicles | grep -A 3 -B 2 Blue vehicles | grep -A 1 -B 4 'Height: 6' vehicles

It basically just "cats" the file, ignoring all the parameters I've given it. I've also tried it with quotes around the first parameter and it does the same thing. I'd appreciate any help. Thanks

Initial Push returns

I'm attempting to make my initial push and seem to be getting an error 403, anyone know why this might be?

Username for 'https://github.com': [email protected] Password for 'https://[email protected]@github.com': remote: Permission to makersacademy/clmystery.git denied to crsanghani. fatal: unable to access 'https://github.com/makersacademy/clmystery.git/': The requested URL returned error: 403

step6 having trouble grepping

I am really struggling to figure out what the right code is to grep multiple pieces of text in the vehicles file. I have tried piping so
grep -A 5 'L377' mystery/vehicles | grep -B 1 -A 4 'Honda' | grep -B 2 -A 3 'Blue' | grep -B 4 -A 1 'Height: 6' >> suspects.txt
but nothing appears in suspects.txt
I'm definitely missing something! Can anyone help?

Not passing the CI tests after completing the challenge

Hi Guys,
Hope you're well.

This is a continuation of the issues I posted on Slack. I thought I should add it as a git issue because I'm a bit stuck...

Here is my position.

I found the killer.
I tested this with the solutions file and I have the correct name.
I checked the permissions of the file. I can read, write and execute, groups and others can read only.
I have added the jail.txt file to git
I have committed the changes
I have pushed this to the makers git.

The CI test comes up with an error.
The error is with this bit of code which is the test:

$ find ./ -name "jail.txt" | xargs less | $(command -v md5 || command -v md5sum) | grep -qif /dev/stdin encoded

This is basically very similar to the code in the solutions file that checks the name of the killer.

So somewhere between pointing terminal to the correct name and pointing terminal on makers git to a file containing the correct name, I've messed something up.

I reckon this will be something silly with my file that I haven't done or have missed.
I've tried deleting it and making it again, making it with a text editorvinstead of command line, changing the permissions.

Not quite sure what to do now.
(No doubt I'll feel stupid when I find out what I did wrong.)

Any suggestions are welcome.

Clmystery step 8

Hi all,

I found the correct suspect, but when I put in the below code, it comes up as SORRY, TRY AGAIN:

echo “John Doe“ | $(command -v md5 || command -v md5sum) | grep -qif /dev/stdin encoded && echo CORRECT\!GREAT WORK, GUMSHOE. || echo SORRY, TRY AGAIN.

(where John Doe is the correct name - I just haven't put it here in case I ruin the challenge for someone else. I know I have the correct person, because I then checked the solution.)

Has anyone else had this issue confirming their suspect is correct?

Not sure if there is a problem with the solution script?

Best wishes, Michael

Problem when doing the pull request

When doing the pull request, there is an error with the file jail.txt. But it is present in my repository on github and it contains the right name of the murderer.
I am not sure why i got the failed message

Error in pull request in step 6

I'm getting this readout:

continuous-integration/travis-ci/pr — The Travis CI build failed

I've attached screenshots for the log and config.

I've tried googling the Travis CI build to work out the issue but so far no joy.
screen shot 2017-05-25 at 17 36 40
screen shot 2017-05-25 at 17 26 32

Step 5

I've created the file interview_info.txt, added and committed it, but when I merge the step-5 branch back into master, using 'git merge origin/step-5', whilst on the master branch, this file is removed.

I'm now getting the message below and not really sure what's going on?

My understanding is that the file should remain as I've merged a historic version into the master, therefore bringing any commits with it?

Thanks!


Malins-MacBook-Air:interviews Malin$ git checkout remotes/origin/step-5
Note: checking out 'remotes/origin/step-5'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b

HEAD is now at 4f7b424... Note on Vim

clmystery - Not sure if I'm finished

Hey Everyone, Other than seeing that my pull request is green and I've added, committed and pushed the 'jail.txt' to clmystery, is there a rocksolid way of knowing I've completed the challenge?

Red crosses

I've only just noticed that I have red crosses next to my pull request..I know this means I've made a mistake somewhere, but how do I go about trying to find out what it is? Is there anything that tells you why it's wrong? It looks like I've started to go wrong at step6 with the list of suspects, but I've created my list of 4 suspects so I'm not sure where I've gone wrong!

Also how do I go back and change it now, do I need to delete my last few commits?

not passing the test after completing(?) the challenge

My suspects.txt contains 4 suspects, and all the information about them, and it doesn't pass the test. I also tried to make the pull request using a file suspects.txt with all the information but weight, and it still does not pass the test.

Step-5

Hi!

I do git branch and I get *Master and the the remote/origin/master.
The big question is: am I supposed to have a step-5 branch? or do I have to create one?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.