log.txt
Error Reproduction:

OS: WSL2
Build: amd64
Environment: Local
Movement CLI: movement 1.0.13

In path examples/movement/* run:

movement move test

Process gets stuck and never ends itself. move test does not lead to the same issue.

strace movement move test available as attachment

Using the graph example, build a BST: https://github.com/movemntdev/movement-hack/blob/main/examples/movement/data_structures/sources/graph.move . Provide helpers for preorder, inorder, postorder, and level order.

Transfer and complete the proof of concepts generated while developing the original content outline. This should be sub-issued.

https://movement-hack.netlify.app/week_1/movement_standard_library#aptos_framworkresource_account

Summary

The cargo generate template which we currently encourage developers to use to set up a well configured project is sourced from this repo. Change it to https://github.com/movemntdev/M1.

Recommended Approach

1. Consult the https://github.com/movemntdev/movement-hack/blob/main/cargo-generate.toml. Understand which files from this repo are included and which are excluded.
2. Draft a PR for M1. Include necessary files. Test PR locally by using the cargo generate --path flag.

https://movement-hack.netlify.app/week_1/developer_setup?highlight=our%20very%20own%20cli#clis
to give direct access to an important resource of interest, link to movement cli page

maybe (?) https://movement.gitbook.io/english/developers/developer-tools/movement-cli

Description

A link in the documentation points to a file that does not exist. Accessing the link results in a 404 error, suggesting the file is missing or the link is incorrect.

Steps to Reproduce

1. Go to link.
2. Click on the link described as Generics to Constrain Abilities and Generics with Multiple Type Parameters.
3. Observe the resulting error page.

Possible Solutions

• Verify if the targeted file has been moved or renamed and update the link accordingly.
• If the file is indeed missing, it may need to be re-added to the appropriate location.

https://movement-hack.netlify.app/week_1/basic_move_syntax?highlight=gudies#basic-move-syntax

Here is the original hackathon content: https://www.notion.so/Hackathon-Content-2f9a0784b6304eaaa64712becbbdde0e

Modify this to better align with network base: https://docs.google.com/spreadsheets/d/1xvEm9aVdeBWM1vwJUojgpwfC80Dalhm39022Uyjw5g8/edit#gid=2084859754

Add additional tests to https://github.com/movemntdev/movement-hack/blob/main/examples/movement/data_structures/sources/graph.move

Try to cover traversal edge cases in particular.

Add a dfs inline to the graph example: https://github.com/movemntdev/movement-hack/blob/main/examples/movement/data_structures/sources/graph.move. Use the bfs as a point of reference.

Transfer the Week 1 content from Notion to mdBook: https://www.notion.so/Week-1-Welcome-Introduction-to-Move-097b32558baa4e1e9ce5e87fc2346d17?pvs=4

Fill in the bullet points from #2 . The lowest level bullet points should be roughly a paragraph (2-5 sentences). If you find or generate interesting visuals, feel free to include them.

Transfer Week 2 from Notion to mdBook: https://www.notion.so/Week-2-Advanced-Move-Building-Basic-DeFi-Smart-Contracts-92b9e83d9e374a4c985a57d5d3e74d4f

It would be best if Share block would link users to sharing content and achievements. It seems like there was the intent to include it.

https://movement-hack.netlify.app/week_2/testing

Error is

Run ./bin/maintainer/citest.sh
  ./bin/maintainer/citest.sh
  shell: sh -e {0}
/__w/_temp/c9b0da90-5374-43ec-af1d-8607[2](https://github.com/movementlabsxyz/movement-hack-old/actions/runs/9546387234/job/26309145402#step:3:2)3d77944.sh: 1: ./bin/maintainer/citest.sh: not found
Error: Process completed with exit code 127.

Any idea why that's happening or how to fix it?

I do see the file /bin/maintainer/citest.sh in the repo.

Here's the workflow in citest.yaml:

name: Run Citests

on:
  push:
    branches:
      - main
jobs:       
  test:
      runs-on: ubuntu-latest
      container:
        image: mvlbs/m1:latest
      steps:
        - run: ./bin/maintainer/citest.sh

and here's the Dockerfile:

FROM public.ecr.aws/c4i6k4r8/movement-dev:latest

COPY . .

ENTRYPOINT ["/bin/bash", "./abin/citest.sh"]

Could it be that https://public.ecr.aws/c4i6k4r8/movement-dev:latest or the image mvlbs/m1:latest needs to be updated?

https://movement-hack.netlify.app/week_2/testing

There are two sections where issue is present, Manual testing and For movement
https://movement-hack.netlify.app/week_2/testing#manual-testing
https://movement-hack.netlify.app/week_2/testing#for-movement

to be consistent with the rest of the descriptions, change:

from: “store: The store ability allows the type to be stored inside a struct in global storage.”
to : “store: The store ability allows the type's value to be stored inside a struct in global storage.”

Summary

Provide a comprehensive guide for resource accounts in the Week 2 curriculum. This should be coupled with a Move project in examples/movement/resource_account.

Recommended Approach

1. Begin by drafting the examples.
   1. Begin with simplest possible usage of resource account you can imagine.
   2. Build up to resource account usage in examples/movement/mini_dex with a series of examples.
2. Write up content to cover examples.
3. Adjust content to include more generalized explanation of resource_accounts.

Finalize the devcontainers should both for checking out and templating.

To get started serving and editing the book.

1. Clone this repo.
2. Review the mdbook documentation.
3. Reopen the repo int the maintainer devcontainer.
4. cd book
5. mdbook serve

You may sometimes need to handling delete the docker containers yourself.

If they are kept, .aptos configs should be replaced with our .movement configs when the CLI is ready.

Fill in the bullet points from #3 . The lowest level bullet points should be roughly a paragraph (2-5 sentences). If you find or generate interesting visuals, feel free to include them.

In most cases, we wouldn't want to keep these configs in the repo, but maybe it serves a useful purpose for the tutorial. And, given we're working off of testnet there's not really much of vulnerability.

I don't seem to have permission to change it.

I created a "movement-hack-new" repo and Primata asked me to make that one "movement-hack".

If someone could change this one to "movement-hack-old" then I can go ahead with the name change on the new repo.