akash-network / cloudmos Goto Github PK
View Code? Open in Web Editor NEWDeploy docker containers on the Akash Network
Home Page: https://cloudmos.io
License: Apache License 2.0
Deploy docker containers on the Akash Network
Home Page: https://cloudmos.io
License: Apache License 2.0
The current "Templates" section could benefit from improvements.
I've prepared a draft of a possible improvement here:
At the top of the page we could recommend templates. This would allow us to feature certain templates that we would like to highlight at a specific point of time. For example if a new LLM comes around, or not long ago we had Zephyr mining on Akash - which could be highlighted at that time.
Next to that we could provide another option where users could view "most popular templates". For all the users who like to explore templates based on popularity.
The filtering option could be added to the section of "All templates" as well.
Refactor the Cloudmos API to enhance usability and maintainability. More and more projects in the akash ecosystem would benefit from using the cloudmos API in their project and this is the ground work for making it more accessible and developer-friendly.
/v1/deployments
)Other Notes:
Logo branding - similar to console.akash.network
Light/ Dark mode: Cloudmos already has this so it'll be great to keep supporting it.
Templates - leave as-is for the scope of this ticket - we will work on a new design as part of #42
Problem Statement: We have a lot of deployments happening on cloudmos but few that use USDC. One thing to note is that it isn't obvious in the main deployment workflow that we support USDC based deploys. This issue recommends two changes to improve that UX
For people using the SDL builder, switching from uAKT to uUSDC does not update the SDL (not sure if this is a bug?). There also isn't an explicit "save" on that "placement" modal (should there be?).
The UI to switch from uAKT to USDC is buried one level deep. Let's surface that up to the main page so that changing it automatically sets the ibc channel to ibc/170C677610AC31DF0904FFE09CD3B5C657492170E7E52372E48756B71E56F2F1
This would be similar to the UI implemented in the "Rent GPU" page as shown below.
Cosmos kit wallet disconnects after a certain period of time andif we reconnect and go on a deployment detail page, the local certificates are not loaded properly.
Would love to have a Button in Readme:
Deploy on Akash
But would need a URL handler like:
https://deploy.cloudmos.io/new-deployment?template_url=https://raw.gitlab.com/...
I checked the code and so far doesn't seem to exist 🧐
TODO
when trying to import and save this sdl to my templates on my cloudmos profile.
i get this error.
---
version: "2.0"
services:
geekbench:
image: davidsarkany/geekbench:6.0.2
expose:
- port: 80
to:
- global: true
env:
- GEEKBENCH_VERSION=6.0.2 #Supports any version of 5.0
- UPLOAD #Replace with NO_UPLOAD to disable uploading results to the Geekbench Browser
#- EMAIL= #Unlock Geekbench using EMAIL and KEY
#- KEY= #Required if email is present
profiles:
compute:
geekbench:
resources:
cpu:
units: 250
memory:
size: 100Gi #2Gi required
storage:
size: 100Gi
placement:
akash:
pricing:
geekbench:
denom: uakt
amount: 10000
deployment:
geekbench:
akash:
profile: geekbench
count: 1
One bug and 2 improvement suggestions:
Bug: When downloading from the shell (and likely the log tab too but did not test that specifically) - the formatting is messed up:
Improvement suggestion:
It wasn't immediately clear to me that the "Download File" button (on the SHELL tab) downloads CLI output from the provider and allows saving it locally - I tended to think that the button let's me download files on to the provider (since I am SSH'ed into the provider at the time) - in other words I thought this was an "upload function" - could be just me though :) -- this brought up two things in my mind:
Cloudmos currently stores some data locally (in the browser local storage) - this causes inconsistencies when using different browsers/ machines or deploying to a new instance. We should discuss an alternate approach to this. Things stored locally include:
Potential Options:
Will need to probe and see if users will use option 1 at all and if they will then consider implementing it
When trying to view the deployments for a given wallet address, the https://stats.akash.network page fails to properly render the list items.
Below i've linked to a quick screen grab by showing what's going on. it's worth pointing out that the fetch is actually succeeding, and it's within the the rendering process that this issue comes to life.
And here is the actual error being printed to the console:
ZodError: [
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
0,
"hash"
],
"message": "Required"
},
{
"code": "invalid_type",
"expected": "array",
"received": "undefined",
"path": [
0,
"messages"
],
"message": "Required"
},
{
"code": "invalid_type",
"expected": "number",
"received": "undefined",
"path": [
0,
"height"
],
"message": "Required"
},
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
0,
"datetime"
],
"message": "Required"
},
{
"code": "invalid_type",
"expected": "boolean",
"received": "undefined",
"path": [
0,
"isSuccess"
],
"message": "Required"
},
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
0,
"error"
],
"message": "Required"
},
{
"code": …
NextJS 11
a
get error
parse
m
_
fetchFn
c
l
promise callback*93476/l/<
promise callback*c
l
69-1727f102e3946f37.js:1:3791
error NextJS
overrideMethod https://stats.akash.network/addresses/akash16sxmnrphfp0393mw6dw2tdugmyeftchxl0tyyl/deployments:13024
NextJS 8
The idea is to build upon the existing Templates + the SDL builder to create a Template Marketplace or SDL Registry if sorts. Inspired from Terraform Registry https://registry.terraform.io/browse/providers or equivalent template marketplaces.
This will allow for the following objectives:
Stretch: Allowing saved templates to generate PRs into github under akash-network/awesome-akash
The SDL builder UX can use a couple of improvements:
The providers' audited icon is clickable and it leads to an error page. This happens on several providers that I checked and it most likely happens on every provider.
Guessing this should lead to info about the provider's auditing or maybe the icon should not be clickable until it leads correctly to provider's audited info.
I uploaded an SDL with GPUs and the builder threw an error.
SDL for ref:
---
version: "2.0"
services:
app:
image: zjuuu/comfyui:0.5
expose:
- port: 8080
as: 8080
to:
- global: true
env:
- "VAEURLS="
- "MODELURLS="
- "UPSCALEURLS="
- "COMMANDLINE_ARGS=--listen --port 8080 --gpu-only"
profiles:
compute:
app:
resources:
cpu:
units: 6.0
memory:
size: 35Gi
gpu:
units: 1
attributes:
vendor:
nvidia:
storage:
size: 50Gi
placement:
akash:
pricing:
app:
denom: uakt
amount: 10000
deployment:
app:
akash:
profile: app
count: 1
selecting a provider and then canceling the transaction (to choose another provider) requires a refresh of the page for the "accept bid" button to become active again. It may be better to cancel the keplr transaction if the bid selection popup is closed, so that the bid selection UI is active again (and the user can select a different provider)
Context:
The current visualization of network capacity on the global map displays single dots for each city with active providers. This representation does not differentiate between cities with multiple providers, potentially obscuring the actual distribution and density of providers.
Problem:
Cities with multiple providers, such as Singapore, which has sg.lnlm.akash.pub
and sg.lneq.akash.pub
, are currently represented with a single dot. This makes it challenging to recognize areas with a higher concentration of providers at a glance.
Proposed Solution:
Implement a dynamic visual representation for cities with multiple providers. Suggestions for this are:
Benefit:
This enhancement would improve the user interface by providing a more accurate visual representation of the network's distribution, allowing users to easily identify hubs of activity and make more informed decisions based on provider density.
Additional Notes:
I believe this feature would significantly improve the user experience and provide valuable insights at a glance. Looking forward to the team's thoughts on this.
The endpoints:
Implement authentication system to recognize clients and better track usage. Separated from issue #54 for better tracking.
GPU RAM quantity should be included in the attribute key when it is set in SDL.
SDL used for testing: https://gist.github.com/chainzero/b21f34f4be2cbb0a882177b00c52e90b
Recent PR enabling this feature in CLI: akash-network/node#1926
--- version: "2.0" services: foo: image: "" expose: - port: 80 as: 80 to: - global: true params: storage: data: mount: /test readOnly: false profiles: compute: foo: resources: cpu: units: 0.1 memory: size: 512Mi storage: - size: 1Gi - name: data size: 10Gi attributes: persistent: true class: beta1 placement: dcloud: pricing: foo: denom: uakt amount: 1000 deployment: foo: dcloud: profile: foo count: 1
Broken:
--- version: "2.0" services: foo: image: "" expose: - port: 80 as: 80 to: - global: true params: storage: dato: mount: /test readOnly: false profiles: compute: foo: resources: cpu: units: 0.1 memory: size: 512Mi storage: - size: 1Gi - name: dato size: 10Gi attributes: persistent: true class: beta1 placement: dcloud: pricing: foo: denom: uakt amount: 1000 deployment: foo: dcloud: profile: foo count: 1
How to reproduce:
Problem 1: Twitter webview
Problem 2:
So as we spoke in our Client meeting today, I tried running my own database last year, as I was trying to fetch some data from Cloudmos API,but was also having some trouble with CORS (which I got it working now)
My issue when trying to run the database, was downloading the database backup that is in Mega https://github.com/akash-network/cloudmos#how-to-run - cloudmos-akash-20230611.sql
I am not very familiar with Mega CLI and although I created a Mega account, for some reason I was not able to download the database backup and thus was not able to continue to the next steps.
I recall trying with this https://github.com/MaxFork/MegaTools and having issues with either my account access or the database requesting some sort of permission or password. (Although now I see that we have this available https://mega.io/cmd which I have not tried)
Either way, if it would be possible to have the database backup uploaded somewhere else and that it can just be downloaded with "wget" or something similar it might be easier for some of us.
Maybe something like what Polkachu has here https://polkachu.com/tendermint_snapshots/akash
Or maybe just some instructions for people not that familiar with Mega.
Thank you
Noticed two things:
This is deployment #1 in the list:
We need an API that takes the owner address and dseq and returns the JSON below.
{
"owner": "akash18ttl3praclcd87dhsy6mczcwvnxrqltdakjn07",
"dseq": "14228985",
"denom": "uakt",
"createdHeight": 14228987,
"createdDate": "2023-12-22T16:15:09.865Z",
"closedHeight": 14229553,
"closedDate": "2023-12-22T17:11:31.053Z",
"status": "closed",
"balance": 4999783.2351,
"transferred": 216.7649,
"settledAt": 14229553,
"resources": {
"cpu": 100,
"memory": 268435456,
"gpu": 0,
"ephemeralStorage": 268435456,
"persistentStorage": 0
},
"leases": [
{
"provider": "akash1e02tys4hawc2wjexadjxztvrkxnkl9r7ym0k7v",
"gseq": 1,
"oseq": 1,
"price": 0.394118,
"createdHeight": 14229003,
"createdDate": "2023-12-22T16:16:46.983Z",
"closedHeight": 14229553,
"closedDate": "2023-12-22T17:11:31.053Z",
"status": "closed",
"resources": {
"cpu": 100,
"memory": 268435456,
"gpu": 0,
"ephemeralStorage": 268435456,
"persistentStorage": 0
}
}
]
}
Add metamask support to cosmoskit using using this code
--platform=linux/amd64
to be able to run on AkashThe old note in the desktop app repo
Only x86_64 processors are officially supported for Akash implementations. But if the docker image is built setting the target platform to linux/amd64 it is possible that it will work from others processors.
Add the note in the FAQ page
Getting error when running cloudmos/api (https://github.com/akash-network/cloudmos/tree/main/api) from Dockerfile as well as from npm directly.
The error is something like Module not found: Error: Can't resolve '@shared/xxx'
is it related to https://github.com/akash-network/cloudmos/tree/main/shared repo?
The full error log from docker is below.
[+] Building 18.7s (12/12) FINISHED docker:default
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 273B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/node:18-alpine 1.7s
=> [1/8] FROM docker.io/library/node:18-alpine@sha256:b1a0356f7d6b86c958a06949d3db3f7fb27f95f627aa6157cb98bc65c801efa2 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 3.07kB 0.0s
=> CACHED [2/8] WORKDIR /app 0.0s
=> CACHED [3/8] COPY . . 0.0s
=> CACHED [4/8] WORKDIR /app/shared 0.0s
=> CACHED [5/8] RUN npm ci 0.0s
=> CACHED [6/8] WORKDIR /app/api 0.0s
=> CACHED [7/8] RUN npm ci 0.0s
=> ERROR [8/8] RUN npm run build 16.8s
------
> [8/8] RUN npm run build:
0.783
0.783 > [email protected] build
0.783 > webpack --config webpack.prod.js
0.783
16.68 assets by status 113 KiB [cached] 1 asset
16.68 cacheable modules 208 KiB 42 modules
16.68 modules by path external "@akashnetwork/akashjs/build/protobuf/akash/ 1010 bytes
16.68 modules by path external "@akashnetwork/akashjs/build/protobuf/akash/market/ 336 bytes 8 modules
16.68 modules by path external "@akashnetwork/akashjs/build/protobuf/akash/deployment/ 252 bytes 6 modules
16.68 modules by path external "@akashnetwork/akashjs/build/protobuf/akash/audit/ 126 bytes 3 modules
16.68 modules by path external "@akashnetwork/akashjs/build/protobuf/akash/cert/ 126 bytes 3 modules
16.68 modules by path external "@akashnetwork/akashjs/build/protobuf/akash/provider/ 126 bytes 3 modules
16.68 external "@akashnetwork/akashjs/build/protobuf/akash/base/v1beta3/storage" 42 bytes [built] [code generated]
16.68 modules by path external "@cosmjs/ 168 bytes
16.68 external "@cosmjs/crypto" 42 bytes [built] [code generated]
16.68 external "@cosmjs/encoding" 42 bytes [built] [code generated]
16.68 external "@cosmjs/proto-signing" 42 bytes [built] [code generated]
16.68 external "@cosmjs/stargate" 42 bytes [built] [code generated]
16.68 + 24 modules
16.68
16.68 ERROR in ./src/db/blocksProvider.ts 13:16-50
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/akash' in '/app/src/db'
16.68 @ ./src/routers/apiRouter.ts 17:25-58
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/db/blocksProvider.ts 14:15-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/base' in '/app/src/db'
16.68 @ ./src/routers/apiRouter.ts 17:25-58
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/db/dbConnection.ts 17:20-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas' in '/app/src/db'
16.68 @ ./src/index.ts 46:23-51
16.68
16.68 ERROR in ./src/db/dbConnection.ts 18:15-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/user' in '/app/src/db'
16.68 @ ./src/index.ts 46:23-51
16.68
16.68 ERROR in ./src/db/dbConnection.ts 19:27-62
16.68 Module not found: Error: Can't resolve '@shared/chainDefinitions' in '/app/src/db'
16.68 @ ./src/index.ts 46:23-51
16.68
16.68 ERROR in ./src/db/deploymentProvider.ts 14:15-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/base' in '/app/src/db'
16.68 @ ./src/routers/apiRouter.ts 32:29-66
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/db/deploymentProvider.ts 15:16-50
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/akash' in '/app/src/db'
16.68 @ ./src/routers/apiRouter.ts 32:29-66
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/db/deploymentProvider.ts 17:20-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas' in '/app/src/db'
16.68 @ ./src/routers/apiRouter.ts 32:29-66
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/db/networkRevenueProvider.ts 25:15-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/base' in '/app/src/db'
16.68 @ ./src/routers/web3indexRouter.ts 17:33-74
16.68 @ ./src/index.ts 43:26-62
16.68
16.68 ERROR in ./src/db/networkRevenueProvider.ts 26:16-50
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/akash' in '/app/src/db'
16.68 @ ./src/routers/web3indexRouter.ts 17:33-74
16.68 @ ./src/index.ts 43:26-62
16.68
16.68 ERROR in ./src/db/providerDataProvider.ts 13:16-50
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/akash' in '/app/src/db'
16.68 @ ./src/routers/apiRouter.ts 31:31-70
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/db/statsProvider.ts 13:15-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/base' in '/app/src/db'
16.68 @ ./src/routers/apiRouter.ts 22:24-56
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/db/statsProvider.ts 14:16-50
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/akash' in '/app/src/db'
16.68 @ ./src/routers/apiRouter.ts 22:24-56
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/db/templateProvider.ts 32:15-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/user' in '/app/src/db'
16.68 @ ./src/routers/userRouter.ts 40:27-62
16.68 @ ./src/index.ts 42:21-52
16.68
16.68 ERROR in ./src/db/transactionsProvider.ts 13:15-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/base' in '/app/src/db'
16.68 @ ./src/routers/apiRouter.ts 19:31-70
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/db/transactionsProvider.ts 14:16-50
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/akash' in '/app/src/db'
16.68 @ ./src/routers/apiRouter.ts 19:31-70
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/providers/apiNodeProvider.ts 23:15-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/base' in '/app/src/providers'
16.68 @ ./src/routers/apiRouter.ts 20:26-67
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/providers/apiNodeProvider.ts 25:16-50
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/akash' in '/app/src/providers'
16.68 @ ./src/routers/apiRouter.ts 20:26-67
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/providers/providerStatusProvider.ts 13:16-50
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/akash' in '/app/src/providers'
16.68 @ ./src/routers/apiRouter.ts 21:33-81
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/providers/providerStatusProvider.ts 14:27-78
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/akash/providerSnapshot' in '/app/src/providers'
16.68 @ ./src/routers/apiRouter.ts 21:33-81
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in ./src/providers/stripeProvider.ts 16:15-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/user' in '/app/src/providers'
16.68 @ ./src/routers/userRouter.ts 41:25-65
16.68 @ ./src/index.ts 42:21-52
16.68
16.68 ERROR in ./src/providers/userDataProvider.ts 13:15-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/user' in '/app/src/providers'
16.68 @ ./src/routers/userRouter.ts 37:27-69
16.68 @ ./src/index.ts 42:21-52
16.68
16.68 ERROR in ./src/routers/dashboardRouter.ts 16:15-48
16.68 Module not found: Error: Can't resolve '@shared/dbSchemas/user' in '/app/src/routers'
16.68 @ ./src/index.ts 47:26-62
16.68
16.68 ERROR in /app/src/db/blocksProvider.ts
16.68 ./src/db/blocksProvider.ts 1:61-86
16.68 [tsl] ERROR in /app/src/db/blocksProvider.ts(1,62)
16.68 TS2307: Cannot find module '@shared/dbSchemas/akash' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 17:25-58
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/db/blocksProvider.ts
16.68 ./src/db/blocksProvider.ts 2:39-63
16.68 [tsl] ERROR in /app/src/db/blocksProvider.ts(2,40)
16.68 TS2307: Cannot find module '@shared/dbSchemas/base' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 17:25-58
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/db/dbConnection.ts
16.68 ./src/db/dbConnection.ts 5:56-75
16.68 [tsl] ERROR in /app/src/db/dbConnection.ts(5,57)
16.68 TS2307: Cannot find module '@shared/dbSchemas' or its corresponding type declarations.
16.68 @ ./src/index.ts 46:23-51
16.68
16.68 ERROR in /app/src/db/dbConnection.ts
16.68 ./src/db/dbConnection.ts 6:73-97
16.68 [tsl] ERROR in /app/src/db/dbConnection.ts(6,74)
16.68 TS2307: Cannot find module '@shared/dbSchemas/user' or its corresponding type declarations.
16.68 @ ./src/index.ts 46:23-51
16.68
16.68 ERROR in /app/src/db/dbConnection.ts
16.68 ./src/db/dbConnection.ts 7:33-59
16.68 [tsl] ERROR in /app/src/db/dbConnection.ts(7,34)
16.68 TS2307: Cannot find module '@shared/chainDefinitions' or its corresponding type declarations.
16.68 @ ./src/index.ts 46:23-51
16.68
16.68 ERROR in /app/src/db/deploymentProvider.ts
16.68 ./src/db/deploymentProvider.ts 4:28-52
16.68 [tsl] ERROR in /app/src/db/deploymentProvider.ts(4,29)
16.68 TS2307: Cannot find module '@shared/dbSchemas/base' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 32:29-66
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/db/deploymentProvider.ts
16.68 ./src/db/deploymentProvider.ts 5:34-59
16.68 [tsl] ERROR in /app/src/db/deploymentProvider.ts(5,35)
16.68 TS2307: Cannot find module '@shared/dbSchemas/akash' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 32:29-66
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/db/deploymentProvider.ts
16.68 ./src/db/deploymentProvider.ts 7:31-50
16.68 [tsl] ERROR in /app/src/db/deploymentProvider.ts(7,32)
16.68 TS2307: Cannot find module '@shared/dbSchemas' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 32:29-66
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/db/networkRevenueProvider.ts
16.68 ./src/db/networkRevenueProvider.ts 2:20-44
16.68 [tsl] ERROR in /app/src/db/networkRevenueProvider.ts(2,21)
16.68 TS2307: Cannot find module '@shared/dbSchemas/base' or its corresponding type declarations.
16.68 @ ./src/routers/web3indexRouter.ts 17:33-74
16.68 @ ./src/index.ts 43:26-62
16.68
16.68 ERROR in /app/src/db/networkRevenueProvider.ts
16.68 ./src/db/networkRevenueProvider.ts 3:36-61
16.68 [tsl] ERROR in /app/src/db/networkRevenueProvider.ts(3,37)
16.68 TS2307: Cannot find module '@shared/dbSchemas/akash' or its corresponding type declarations.
16.68 @ ./src/routers/web3indexRouter.ts 17:33-74
16.68 @ ./src/index.ts 43:26-62
16.68
16.68 ERROR in /app/src/db/providerDataProvider.ts
16.68 ./src/db/providerDataProvider.ts 1:44-69
16.68 [tsl] ERROR in /app/src/db/providerDataProvider.ts(1,45)
16.68 TS2307: Cannot find module '@shared/dbSchemas/akash' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 31:31-70
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/db/statsProvider.ts
16.68 ./src/db/statsProvider.ts 1:20-44
16.68 [tsl] ERROR in /app/src/db/statsProvider.ts(1,21)
16.68 TS2307: Cannot find module '@shared/dbSchemas/base' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 22:24-56
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/db/statsProvider.ts
16.68 ./src/db/statsProvider.ts 2:36-61
16.68 [tsl] ERROR in /app/src/db/statsProvider.ts(2,37)
16.68 TS2307: Cannot find module '@shared/dbSchemas/akash' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 22:24-56
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/db/templateProvider.ts
16.68 ./src/db/templateProvider.ts 1:56-80
16.68 [tsl] ERROR in /app/src/db/templateProvider.ts(1,57)
16.68 TS2307: Cannot find module '@shared/dbSchemas/user' or its corresponding type declarations.
16.68 @ ./src/routers/userRouter.ts 40:27-62
16.68 @ ./src/index.ts 42:21-52
16.68
16.68 ERROR in /app/src/db/transactionsProvider.ts
16.68 ./src/db/transactionsProvider.ts 1:46-70
16.68 [tsl] ERROR in /app/src/db/transactionsProvider.ts(1,47)
16.68 TS2307: Cannot find module '@shared/dbSchemas/base' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 19:31-70
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/db/transactionsProvider.ts
16.68 ./src/db/transactionsProvider.ts 2:61-86
16.68 [tsl] ERROR in /app/src/db/transactionsProvider.ts(2,62)
16.68 TS2307: Cannot find module '@shared/dbSchemas/akash' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 19:31-70
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/providers/apiNodeProvider.ts
16.68 ./src/providers/apiNodeProvider.ts 7:26-50
16.68 [tsl] ERROR in /app/src/providers/apiNodeProvider.ts(7,27)
16.68 TS2307: Cannot find module '@shared/dbSchemas/base' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 20:26-67
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/providers/apiNodeProvider.ts
16.68 ./src/providers/apiNodeProvider.ts 9:44-69
16.68 [tsl] ERROR in /app/src/providers/apiNodeProvider.ts(9,45)
16.68 TS2307: Cannot find module '@shared/dbSchemas/akash' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 20:26-67
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/providers/providerStatusProvider.ts
16.68 ./src/providers/providerStatusProvider.ts 1:72-97
16.68 [tsl] ERROR in /app/src/providers/providerStatusProvider.ts(1,73)
16.68 TS2307: Cannot find module '@shared/dbSchemas/akash' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 21:33-81
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/providers/providerStatusProvider.ts
16.68 ./src/providers/providerStatusProvider.ts 2:33-75
16.68 [tsl] ERROR in /app/src/providers/providerStatusProvider.ts(2,34)
16.68 TS2307: Cannot find module '@shared/dbSchemas/akash/providerSnapshot' or its corresponding type declarations.
16.68 @ ./src/routers/apiRouter.ts 21:33-81
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 ERROR in /app/src/providers/stripeProvider.ts
16.68 ./src/providers/stripeProvider.ts 1:28-52
16.68 [tsl] ERROR in /app/src/providers/stripeProvider.ts(1,29)
16.68 TS2307: Cannot find module '@shared/dbSchemas/user' or its corresponding type declarations.
16.68 @ ./src/routers/userRouter.ts 41:25-65
16.68 @ ./src/index.ts 42:21-52
16.68
16.68 ERROR in /app/src/providers/stripeProvider.ts
16.68 ./src/providers/stripeProvider.ts 2:25-40
16.68 [tsl] ERROR in /app/src/providers/stripeProvider.ts(2,26)
16.68 TS2307: Cannot find module '@shared/plans' or its corresponding type declarations.
16.68 @ ./src/routers/userRouter.ts 41:25-65
16.68 @ ./src/index.ts 42:21-52
16.68
16.68 ERROR in /app/src/providers/userDataProvider.ts
16.68 ./src/providers/userDataProvider.ts 1:45-69
16.68 [tsl] ERROR in /app/src/providers/userDataProvider.ts(1,46)
16.68 TS2307: Cannot find module '@shared/dbSchemas/user' or its corresponding type declarations.
16.68 @ ./src/routers/userRouter.ts 37:27-69
16.68 @ ./src/index.ts 42:21-52
16.68
16.68 ERROR in /app/src/routers/dashboardRouter.ts
16.68 ./src/routers/dashboardRouter.ts 1:38-62
16.68 [tsl] ERROR in /app/src/routers/dashboardRouter.ts(1,39)
16.68 TS2307: Cannot find module '@shared/dbSchemas/user' or its corresponding type declarations.
16.68 @ ./src/index.ts 47:26-62
16.68
16.68 ERROR in /app/src/utils/map/provider.ts
16.68 ./src/utils/map/provider.ts 1:25-50
16.68 [tsl] ERROR in /app/src/utils/map/provider.ts(1,26)
16.68 TS2307: Cannot find module '@shared/dbSchemas/akash' or its corresponding type declarations.
16.68 @ ./src/providers/providerStatusProvider.ts 18:19-53
16.68 @ ./src/routers/apiRouter.ts 21:33-81
16.68 @ ./src/index.ts 41:20-50
16.68
16.68 48 errors have detailed information that is not shown.
16.68 Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.
16.68
16.68 webpack 5.78.0 compiled with 48 errors in 14783 ms
------
Dockerfile:16
--------------------
14 | WORKDIR /app/api
15 | RUN npm ci
16 | >>> RUN npm run build
17 |
18 | EXPOSE 80
--------------------
ERROR: failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 1
In Nav.tsx there is a check to decide which logo should be used (light/dark). When using the "system" theme, it always use the darkmode logo even if system theme is light.
Switch custom wallet logic to use CosmosKit instead. This will allow us to add support for new wallet very quickly.
The below yaml was generated with the generator returns no bids, even though the network has a100 80GB
I suspect there is an issue with using proper tag for - model: a100
---
version: "2.0"
services:
obtaingpu:
image: ubuntu:22.04
command:
- "sh"
- "-c"
args:
- 'uptime;
nvidia-smi;
sleep infinity'
expose:
- port: 8080
as: 80
to:
- global: true
profiles:
compute:
obtaingpu:
resources:
cpu:
units: 1.0
memory:
size: 1Gi
gpu:
units: 1
attributes:
vendor:
nvidia:
- model: a100
storage:
size: 1Gi
placement:
akash:
pricing:
obtaingpu:
denom: uakt
amount: 100000
deployment:
obtaingpu:
akash:
profile: obtaingpu
count: 1
Add API to return leases when passing provider address - active and inactive.
input - providerAddress, pagination.limit, pagination.offset, state
example return -
{
"deployment": {
"deployment_id": {
"owner": "akash18ttl3praclcd87dhsy6mczcwvnxrqltdakjn07",
"dseq": "13713996"
},
"state": "closed",
"version": "sRo1rTeBjw7MYgpP0JmiRWyiF6ZnKNZug6RrNuiOo2Q=",
"created_at": "13714019"
},
"groups": [
{
"group_id": {
"owner": "akash18ttl3praclcd87dhsy6mczcwvnxrqltdakjn07",
"dseq": "13713996",
"gseq": 1
},
"state": "closed",
"group_spec": {
"name": "akash",
"requirements": {
"signed_by": {
"all_of": [
],
"any_of": [
]
},
"attributes": [
]
},
"resources": [
{
"resource": {
"id": 1,
"cpu": {
"units": {
"val": "500"
},
"attributes": [
]
},
"memory": {
"quantity": {
"val": "536870912"
},
"attributes": [
]
},
"storage": [
{
"name": "default",
"quantity": {
"val": "536870912"
},
"attributes": [
]
}
],
"gpu": {
"units": {
"val": "0"
},
"attributes": [
]
},
"endpoints": [
{
"kind": "SHARED_HTTP",
"sequence_number": 0
}
]
},
"count": 1,
"price": {
"denom": "uakt",
"amount": "10000.000000000000000000"
}
}
]
},
"created_at": "13714019"
}
],
"escrow_account": {
"id": {
"scope": "deployment",
"xid": "akash18ttl3praclcd87dhsy6mczcwvnxrqltdakjn07/13713996"
},
"owner": "akash18ttl3praclcd87dhsy6mczcwvnxrqltdakjn07",
"state": "closed",
"balance": {
"denom": "uakt",
"amount": "0.437134000000000000"
},
"transferred": {
"denom": "uakt",
"amount": "255.562866000000000000"
},
"settled_at": "13714260",
"depositor": "akash18ttl3praclcd87dhsy6mczcwvnxrqltdakjn07",
"funds": {
"denom": "uakt",
"amount": "0.000000000000000000"
}
}
}
input - providerAddress, pagination.limit, pagination.offset, state
example return
{
"leases": [
{
"lease": {
"lease_id": {
"owner": "akash18ttl3praclcd87dhsy6mczcwvnxrqltdakjn07",
"dseq": "13713996",
"gseq": 1,
"oseq": 1,
"provider": "akash1jrt5gj4njygdyfjksdpjerdgwpk8pzj8cg3el9"
},
"state": "closed",
"price": {
"denom": "uakt",
"amount": "1.092149000000000000"
},
"created_at": "13714026",
"closed_on": "13714260"
},
"escrow_payment": {
"account_id": {
"scope": "deployment",
"xid": "akash18ttl3praclcd87dhsy6mczcwvnxrqltdakjn07/13713996"
},
"payment_id": "1/1/akash1jrt5gj4njygdyfjksdpjerdgwpk8pzj8cg3el9",
"owner": "akash1jrt5gj4njygdyfjksdpjerdgwpk8pzj8cg3el9",
"state": "closed",
"rate": {
"denom": "uakt",
"amount": "1.092149000000000000"
},
"balance": {
"denom": "uakt",
"amount": "0.562866000000000000"
},
"withdrawn": {
"denom": "uakt",
"amount": "255"
}
}
}
],
"pagination": {
"next_key": null,
"total": "1"
}
}
After almost 2 months since the GPU mainnet launch, we've gathered many feedbacks from the community, both from the crypto and non-crypto native users. What comes out the most is the ease of use to deploy, a "point and click solution".
Hence, I created this topic to track the advancement on a new type of form similar to the SDL builder, but verticaly aligned for GPUs.
The form will support:
Hi,
I'm Mr. Tetroid, a very friendly guy.
Cloudmos SDL builder is completely and utterly broken in Brave browser running on Debian 11.
This is nuts. It takes a little while to put an SDL file together and then it just gets wiped most of the time. No way to preview before wiping either. Come on make SDL building a nice experience. As of now it is extremely buggy and also the saving capability does not seem to be persistent anyway. Worst kind of SDL builder.
TODO:
With bid attributes supported akash-network/support#124 we should display GPU model type and any other available attributes in the bid requests in cloudmos
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.