come-maiz

diff --git a/WORKSPACE b/WORKSPACE
index ca9d3d999..cb4daf4a5 100644
--- a/WORKSPACE
+++ b/WORKSPACE
@@ -13,11 +13,10 @@ http_archive(
     ],
 )
 
-http_archive(
+git_repository(

come-maiz

elopio@kiln:~/lighthouse$ make
cargo install --path lighthouse --force --locked --features ""
  Installing lighthouse v2.1.5 (/home/elopio/lighthouse/lighthouse)
    Updating crates.io index
warning: package `blake2 v0.10.2` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `crossbeam-channel v0.5.2` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `zeroize_derive v1.3.1` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
   Compiling libsecp256k1 v0.6.0
error: failed to compile `lighthouse v2.1.5 (/home/elopio/lighthouse/lighthouse)`, intermediate artifacts can be found at `/home/elopio/lighthouse/target`

come-maiz

pragma solidity ^0.5.10;

contract AssemblyArrays {
  
  bytes testArray;
  
  function getLength() public view returns (uint256) {
      return testArray.length;
  }
  

come-maiz

Notation

• When the same error can show multiple values, some examples of the possible values are noted like: {value1|value2|value3}. Only one of those values is displayed to the user.
• When the error takes a value specified by the user in the snapcraft.yaml or through the command line, it is noted like: {sample-value}.

Errors

errors.MissingStateCleanError:

come-maiz

Maintained by upstream

⚙️ base58: snapcraft.yaml | CI releasing to edge | Install instructions waiting for review | Not yet released to stable.

⚙️ bcoin: snapcraft.yaml | Not yet released to the store.

⚙️ bigchaindb: snapcraft.yaml | Not yet released to the store.

⚙️ borg: snapcraft.yaml | Not yet released to the store.

come-maiz

Verifying that "elopio.id" is my Blockstack ID. https://explorer.blockstack.org/name/elopio.id

come-maiz

20171012:
 * unit: http://paste.ubuntu.com/25724713/

20171011:

 * plugins: http://paste.ubuntu.com/25724482/

come-maiz

The snapcraft store tests run against the staging store. However, these steps have to be run also in the production store, because the staging store is synched with production. If you run only the steps in staging, then they will be lost in the next sync.

1. Register the user snapcraft-test+user@canonical.com in https://login.ubuntu.com and https://login.staging.ubuntu.com/.

   (elopio has the password of the registered user)

2. Validate the email address.

(The previous step sends an email with the validation link. elopio has the password for the email account)

come-maiz

github.com/snapcore/snapcraft

./.travis.yml:20: comming ==> coming

./TESTING.md:28: excercise ==> exercise

./TESTING.md:28: excecution ==> execution

./TESTING.md:34: excercise ==> exercise

come-maiz

Before trying to make a snap, check if it's status is already being tracked in https://gist.github.com/elopio/242d4dee6b0dc90086efe3e37a919e30

• websites

  https://github.com/dawnlabs/carbon

  http://veniversum.me/git-visualizer/

• dump: