Skip to content
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

[Tilt] Enable rest service by default in Tilt #793

Merged
merged 1 commit into from
Sep 4, 2024

Conversation

red-0ne
Copy link
Contributor

@red-0ne red-0ne commented Sep 4, 2024

Summary

Enable the rest service by default in Tilt

Issue

Since the rest service is used in E2E tests, it should be enabled by default to avoid non-edited localnet_config.yaml files to succeed E2E tests.

image

Type of change

Select one or more from the following:

Testing

  • Documentation: make docusaurus_start; only needed if you make doc changes
  • Unit Tests: make go_develop_and_test
  • LocalNet E2E Tests: make test_e2e
  • DevNet E2E Tests: Add the devnet-test-e2e label to the PR.

Sanity Checklist

  • I have tested my changes using the available tooling
  • I have commented my code
  • I have performed a self-review of my own code; both comments & source code
  • I create and reference any new tickets, if applicable
  • I have left TODOs throughout the codebase, if applicable

@red-0ne red-0ne added testing Test (or test utils) additions, fixes, improvements or other tooling Tooling - CLI, scripts, helpers, off-chain, etc... labels Sep 4, 2024
@red-0ne red-0ne self-assigned this Sep 4, 2024
@red-0ne red-0ne merged commit ff05ce6 into main Sep 4, 2024
12 checks passed
Olshansk pushed a commit that referenced this pull request Sep 4, 2024
## Summary

Enable the `rest` service by default in Tilt

## Issue

Since the `rest` service is used in E2E tests, it should be enabled by
default to avoid non-edited `localnet_config.yaml` files to succeed E2E
tests.


![image](https://github.com/user-attachments/assets/88ac37ca-bf9f-4146-83f1-2eafc2f3c829)

## Type of change

Select one or more from the following:

- [ ] New feature, functionality or library
- [ ] Consensus breaking; add the `consensus-breaking` label if so. See
#791 for details
- [ ] Bug fix
- [x] Code health or cleanup
- [ ] Documentation
- [ ] Other (specify)

## Testing

- [ ] **Documentation**: `make docusaurus_start`; only needed if you
make doc changes
- [ ] **Unit Tests**: `make go_develop_and_test`
- [ ] **LocalNet E2E Tests**: `make test_e2e`
- [ ] **DevNet E2E Tests**: Add the `devnet-test-e2e` label to the PR.

## Sanity Checklist

- [ ] I have tested my changes using the available tooling
- [ ] I have commented my code
- [ ] I have performed a self-review of my own code; both comments &
source code
- [ ] I create and reference any new tickets, if applicable
- [ ] I have left TODOs throughout the codebase, if applicable
bryanchriswhite added a commit that referenced this pull request Sep 5, 2024
…ke-transfer

* pokt/main:
  [Relay Mining] Use per-service difficulty in the relayer (#745)
  [Tilt] Enable rest service by default in Tilt (#793)
  [Docs] Minor doc updates across the board (#792)
  build(deps): bump webpack from 5.89.0 to 5.94.0 in /docusaurus (#775)
  [Docs] Tokenomics Documentation (#750)
  fix: ensure stable_marshaler_all option on all proto files (#772)
  build(deps): bump micromatch from 4.0.5 to 4.0.8 in /docusaurus (#774)
  [Tooling] Add `protocheck` CLI tool (#770)
  Update `adding_params.md` to use `ignite` (#764)
  [Docs] Cleanup & Deprecation (#766)
bryanchriswhite added a commit that referenced this pull request Sep 5, 2024
…actor/transfer-msg_period-param

* issues/657/feat/app-stake-transfer:
  chore: regenerate protobufs
  [Relay Mining] Use per-service difficulty in the relayer (#745)
  [Tilt] Enable rest service by default in Tilt (#793)
  [Docs] Minor doc updates across the board (#792)
  build(deps): bump webpack from 5.89.0 to 5.94.0 in /docusaurus (#775)
  [Docs] Tokenomics Documentation (#750)
  fix: ensure stable_marshaler_all option on all proto files (#772)
  build(deps): bump micromatch from 4.0.5 to 4.0.8 in /docusaurus (#774)
  [Tooling] Add `protocheck` CLI tool (#770)
  Update `adding_params.md` to use `ignite` (#764)
  [Docs] Cleanup & Deprecation (#766)
bryanchriswhite added a commit that referenced this pull request Sep 5, 2024
…ues/657/chore/app-transfer-period

* issues/657/refactor/transfer-msg_period-param:
  chore: regenerate protobufs
  chore: regenerate protobufs
  fix: failing test
  chore: regenerate protobufs
  Revert "refactor: rename param to application_transfer_and_unboding_period_sessions"
  [Relay Mining] Use per-service difficulty in the relayer (#745)
  [Tilt] Enable rest service by default in Tilt (#793)
  [Docs] Minor doc updates across the board (#792)
  build(deps): bump webpack from 5.89.0 to 5.94.0 in /docusaurus (#775)
  [Docs] Tokenomics Documentation (#750)
  fix: ensure stable_marshaler_all option on all proto files (#772)
  build(deps): bump micromatch from 4.0.5 to 4.0.8 in /docusaurus (#774)
  [Tooling] Add `protocheck` CLI tool (#770)
  Update `adding_params.md` to use `ignite` (#764)
  [Docs] Cleanup & Deprecation (#766)
okdas pushed a commit that referenced this pull request Nov 14, 2024
## Summary

Enable the `rest` service by default in Tilt

## Issue

Since the `rest` service is used in E2E tests, it should be enabled by
default to avoid non-edited `localnet_config.yaml` files to succeed E2E
tests.


![image](https://github.com/user-attachments/assets/88ac37ca-bf9f-4146-83f1-2eafc2f3c829)

## Type of change

Select one or more from the following:

- [ ] New feature, functionality or library
- [ ] Consensus breaking; add the `consensus-breaking` label if so. See
#791 for details
- [ ] Bug fix
- [x] Code health or cleanup
- [ ] Documentation
- [ ] Other (specify)

## Testing

- [ ] **Documentation**: `make docusaurus_start`; only needed if you
make doc changes
- [ ] **Unit Tests**: `make go_develop_and_test`
- [ ] **LocalNet E2E Tests**: `make test_e2e`
- [ ] **DevNet E2E Tests**: Add the `devnet-test-e2e` label to the PR.

## Sanity Checklist

- [ ] I have tested my changes using the available tooling
- [ ] I have commented my code
- [ ] I have performed a self-review of my own code; both comments &
source code
- [ ] I create and reference any new tickets, if applicable
- [ ] I have left TODOs throughout the codebase, if applicable
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Test (or test utils) additions, fixes, improvements or other tooling Tooling - CLI, scripts, helpers, off-chain, etc...
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

2 participants