-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove depricated: literal constraints #1441
Conversation
Signed-off-by: Nikhil B N <[email protected]>
1f8ef8b
to
27473ec
Compare
…depricated Signed-off-by: Nikhil B N <[email protected]>
27473ec
to
07eb693
Compare
@fanatid could you please approve workflow run ? I have fixed all warnings and build errors, now I have to make sure to get rid of literal constraints which are being used in certain tests in these files: 1, 2. Literal constraint is also used over here -> as Thanks |
@fanatid please approve workflow run! |
@NBNARADHYA please research how to run actions on your fork. You can start from editing these lines: https://github.com/project-serum/anchor/blob/master/.github/workflows/tests.yaml#L3-L9 |
Oh. My bad! I thought github would atleast display actions in forked repo and I could run it manually but I wasn't able to. So, I assumed it was disabled on forked repo! Thanks @fanatid |
Signed-off-by: Nikhil B N <[email protected]>
6d8bec7
to
db2f498
Compare
Yes, please open a pr on the submodule. |
@armaniferrante @fanatid I have made a pr to the stake repo: project-serum/stake#21 |
The submodules which were linked to this repository were: All of these except stake are "literal constraint" free. So, I have made the changes to only stake repo @fanatid @armaniferrante |
Closing as stale. |
Changes: