Update screwed up Reach! Help!

[JamesLampert]

Two weeks ago today, discovering that the new "RSVP" tutorial requires features not in my then-current version of Reach, I did a
./reach update

At the time the version I had was working just fine. After I updated, it stopped working completely. If I do a
./reach version
(or a ./reach anything else, for that matter), something flickers in my Docker window, too fast to read, and then I get:

Jamess-iMac:tut jameslampert$ ./reach version
Missing:

reach 0.1.11 (98ccf409) - Reach command-line tool

Usage: reach COMMAND

Available options:
  -h,--help                Show this help text

Available commands:
  clean                    Delete 'build/$MODULE.$IDENT.mjs'
  compile                  Compile an app
  config                   Configure default Reach settings
  devnet                   Run only the devnet
  docker-reset             Kill and remove all Docker containers
  down                     Halt all Dockerized Reach services and devnets
  hashes                   Display git hashes used to build each Docker image
  help                     Show usage
  info                     List available updates
  init                     Set up source files for a simple app in the current
                           directory
  react                    Run a simple React app
  rpc-run                  Run an RPC server + frontend with development
                           configuration
  rpc-server               Run a simple Reach RPC server
  run                      Run a simple app
  scaffold                 Set up Docker scaffolding for a simple app in the
                           current directory
  support                  Create a GitHub gist of index.rsh and index.mjs
                           (default), or specify your own files to upload!
  tsa                      Run the TEAL Static Analyzer (only available with
                           Reach Everest)
  update                   Perform available updates
  version                  Display version

I'm on a Mac, running Catalina, VSCode is my Reach development environment, and Bash is my default command line shell. I think I did the ./reach update from a terminal session within VSCode, but I get the subsequent utterly uninformative error message, and the helptext, regardless of whether I'm in a VSCode terminal session or a terminal window opened from Finder.

I've had this question up on Discord since the day it happened.

[jeapostrophe]

I am pretty sure the problem is needing a new cli image. If you delete the old one, it will download a new one, or you could specifically get a new one

@DanBurton can you copy in the Docker command to get a new cli image?

[JamesLampert]

forgot how long it takes. Now, I get:

Jamess-iMac:tut jameslampert$ ./reach version
reach 0.1.12
Jamess-iMac:tut jameslampert$ ./reach hashes
reach-cli: 816420cc
reach: 816420cc
react-runner: 816420cc
rpc-server: 816420cc
runner: 816420cc
devnet-algo: 816420cc
devnet-cfx: 816420cc
devnet-eth: 816420cc

I'm guessing that at this point, I just need to propagate (or maybe alias?) the new "reach" shell script to all other occurrences, and I can get right back into the RSVP tutorial.

[jeapostrophe]

Yup

[JamesLampert]

Interesting: I now have VSCode up, with the first (very incomplete) version of the "rsvp" project up. When it came up, my Docker window showed a single container/app with a red icon. When I did a ./reach compile from VSCode's terminal pane, I got

Jamess-iMac:rsvp-1 jameslampert$ ./reach compile
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
       sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
Verifying knowledge assertions
Verifying for generic connector
  Verifying when ALL participants are honest
  Verifying when NO participants are honest
Checked 9 theorems; No failures!

and the Docker window, the next time I looked at Containers/Apps, showed a whole bunch more than I can recall seeing before:

Is something still wrong? What's the "sed:illegal option" about? I don't get it in a regular terminal window; it goes straight to "Verifying knowledge assertions."

[jeapostrophe]

I looked through all of the uses of sed in the code you're calling and I don't see any with -r in them, so I am confused. It apparently didn't cause a problem.

We expect to use one more container than before, but I don't expect to see so many. I'll have to investigate. Can you say what version of Docker you're running?

[JamesLampert]

Re: "sed" (for some reason I'm thinking of the "sed-a-give" gag from Young Frankenstein), the error message only happens in the VSCode terminal pane, so that might have something to do with it.

Docker Desktop 4.4.2 (73305)
Engine: 20.10.12
Compose: v2.2.3
Credential Helper: 0.6.4
Kubernetes: v1.22.5
Snyk: v1.809.0

VSCode is
Version: 1.71.2 (Universal)
Commit: 74b1f979648cc44d385a2286793c226e611f59e7
Date: 2022-09-14T21:05:37.721Z (2 wks ago)

Not sure where to look, to find out what version of Reach support I have in VSCode, assuming that's relevant.