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.

Sign up for GitHub

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

Jump to bottom

[EPIC] Design and implement metadata storage interface #4

Closed
4 tasks done
jerryshao opened this issue May 6, 2023 · 0 comments
Closed
4 tasks done

[EPIC] Design and implement metadata storage interface #4

jerryshao opened this issue May 6, 2023 · 0 comments
Assignees
@jerryshao
Labels
epic Key feature
Milestone
Graviton v0.1.0 (...

Comments

@jerryshao
Copy link
Contributor

jerryshao commented May 6, 2023 •
edited
Loading

This epic tracks the work of designing metadata entity storage interface and achieve one implementation.

The works are:
@jerryshao jerryshao added the epic Key feature label May 6, 2023
@jerryshao jerryshao changed the title [EPIC] Design and implement metadata storage layout [EPIC] Design and implement metadata storage interface May 6, 2023
@jerryshao jerryshao mentioned this issue Jun 13, 2023
Closed
@jerryshao jerryshao self-assigned this Jun 13, 2023
This was referenced Jun 14, 2023
Closed
Closed
This was referenced Jul 14, 2023
Closed
Closed
@LanceHsun LanceHsun mentioned this issue Jun 21, 2024
Closed
danhuawang added a commit that referenced this issue Jul 1, 2024
@danhuawang
[Minor] Frontend integration test failed in headless environment (#4006)
445792f 
### What changes were proposed in this pull request?

Frontend integration test failed in certain headless environment, like
the ec2 in aws.

### Why are the changes needed?

 Frontend integration test failed due to the following error:
```
 MetalakePageTest > initializationError FAILED
    org.openqa.selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally.
      (chrome not reachable)
      (The process started from chrome location /actions-runner/_work/gravitino-test/gravitino-test/gravitino/integration-test/build/chrome/chrome-linux/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
    Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
    System info: host: 'ip-172-31-5-251', ip: '172.31.5.251', os.name: 'Linux', os.arch: 'amd64', os.version: '6.5.0-1020-aws', java.version: '1.8.0_412'
    Driver info: driver.version: ChromeDriver
    remote stacktrace: #0 0x561b8bc79869 <unknown>
    #1 0x561b8bc14383 <unknown>
    #2 0x561b8b9f6ca3 <unknown>
    #3 0x561b8ba1a286 <unknown>
    #4 0x561b8ba157cd <unknown>
    #5 0x561b8ba4f11d <unknown>
    #6 0x561b8ba49963 <unknown>
    #7 0x561b8ba1fe36 <unknown>
    #8 0x561b8ba20fd5 <unknown>
    #9 0x561b8bc41f90 <unknown>
    #10 0x561b8bc53d80 <unknown>
```

### Does this PR introduce _any_ user-facing change?

N/A

### How was this patch tested?

<img width="1492" alt="image"
src="https://github.com/datastrato/gravitino/assets/154112360/3e16870e-ad51-4677-aec5-8e8be0c68f9b">
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jerryshao jerryshao

Labels
epic Key feature
Projects
None yet
Milestone
Graviton v0.1.0 (updated)
Development

No branches or pull requests
1 participant
@jerryshao