Error: Trade history incomplete
    getAverageOpenPrice PerpAccount.js:81
    collectPerpPosition usePerpPositions.tsx:49
    perpAccounts usePerpPositions.tsx:97
    usePerpPositions usePerpPositions.tsx:96
    UserInfoTabs UserInfo.tsx:26
    React 9
    unstable_runWithPriority scheduler.development.js:468
    React 5
    listener index.js:79
    setState index.js:11
    setState index.js:11
    set useMangoStore.tsx:243
    _callee$/< useMangoStore.tsx:306
    promise callback*_callee$ useMangoStore.tsx:298
    Babel 8
    _callee$ useWallet.tsx:122
    Babel 8
    _handleConnect phantom.ts:43
    emit inpage.js:116
    _handleMessage inpage.js:288
    a inpage.js:288
    a inpage.js:288
    _handleMessage inpage.js:288
 
UserInfoTabs@webpack-internal:///./components/UserInfo.tsx:44:21
div
UserInfo@webpack-internal:///./components/UserInfo.tsx:163:89
div
FloatingElement@webpack-internal:///./components/FloatingElement.tsx:23:21
div
Resizable@webpack-internal:///./node_modules/react-resizable/build/Resizable.js:46:35
DraggableCore@webpack-internal:///./node_modules/react-draggable/build/cjs/DraggableCore.js:130:20
GridItem@webpack-internal:///./node_modules/react-grid-layout/build/GridItem.js:65:20
div
ReactGridLayout@webpack-internal:///./node_modules/react-grid-layout/build/ReactGridLayout.js:98:20
ResponsiveReactGridLayout@webpack-internal:///./node_modules/react-grid-layout/build/ResponsiveReactGridLayout.js:144:20
WidthProvider@webpack-internal:///./node_modules/react-grid-layout/build/components/WidthProvider.js:77:22
TradePageGrid@webpack-internal:///./components/TradePageGrid.tsx:396:86
div
PageBodyWrapper@webpack-internal:///./components/styles.tsx:71:20
div
PerpMarket@webpack-internal:///./pages/market.tsx:76:101
div
ViewportProvider@webpack-internal:///./hooks/useViewport.tsx:18:20
f@webpack-internal:///./node_modules/next-themes/dist/index.modern.js:10:242
App@webpack-internal:///./pages/_app.tsx:129:21
I18nextProvider@webpack-internal:///./node_modules/react-i18next/dist/es/I18nextProvider.js:11:14
AppWithTranslation@webpack-internal:///./node_modules/next-i18next/dist/esm/appWithTranslation.js:37:24
StyleRegistry@webpack-internal:///./node_modules/styled-jsx/dist/stylesheet-registry.js:231:28
ErrorBoundary@webpack-internal:///./node_modules/@next/react-dev-overlay/lib/internal/ErrorBoundary.js:26:47
ReactDevOverlay@webpack-internal:///./node_modules/@next/react-dev-overlay/lib/internal/ReactDevOverlay.js:90:20
Container@webpack-internal:///./node_modules/next/dist/client/index.js:330:24
AppContainer@webpack-internal:///./node_modules/next/dist/client/index.js:770:20
Root@webpack-internal:///./node_modules/next/dist/client/index.js:888:21

This events has length 0 then it goes directly to the error.

The events is this tradeHistory that's 0 length. Don't know how it would get values. Don't know why/if trade history is necessary.

When trying to place an order it gets stuck in this infinite loop trying to call this

Is there any documentation on the backend this uses? Specifically the heroku app for stats? I'm curious to understand how latest funding rates are calculated and where oracle prices come from.

Redacted

To reproduce, open mango ui with a position open, select reduce only, and click 25%. it will not populate the order details box with 25% of the position you intend to reduce, it will instead populate with 25% of your margin.

I have 240 units of MNGO and I was trying to trade on the platform.

When I click sell MNGO button, this pops up

Finally I failed to send limit order and I have no idea why this will happen.
error message link: https://explorer.solana.com/tx/37TACBNvFbBoPN1ALDoFbrsxidDaDJciw1h3kWwd1JQQY7qHYtdBoLUT6LV9v1gm3f6zpuGcE2Qda6oX1PcJTAAy?cluster=mainnet

Trying to wrap my head around the project.

This line from components/TradingView/index.tsx says "// Make sure to follow step 1 of the README". Which README is it talking about?

The org page shows mango-ui as the popular repo. Would also be nice to add a deprecation notice to that one, and have a look at the issues :) (or at least transfer them here)

Console Errors:

Unhandled Runtime Error
Error: failed to get recent blockhash: Error: 403 : {"jsonrpc":"2.0","error":{"code": 403, "message":"Access forbidden, contact your app developer or [email protected]."}, "id": "e37da218-91e7-4020-a2b4-b8e05d1be464" }

Call Stack
Connection.getRecentBlockhash
node_modules/@solana/web3.js/lib/index.browser.esm.js (6519:0)

Hi. Can you tell me how to create files to upload to the server. For example, in the repository https://github.com/project-serum/serum-dex-ui just write yarn build. It will automatically create a "build" folder with all the necessary files to upload to the server.

While fork the code and run locally , the chart is showing that error .

The price fetching into the tab title doesn't seem to work anymore.. It's a super convenient feature!
I gather the issue is here but i'm not super familiar with how the state is represented... could someone take a look ? :)
@

Guys, I have a problem, when try to start your interface locally.
When I try to run dev process on 'account' route, or on base route and then go to account route - dev process is crashing with error heap out of memory.
OS ubuntu 20.04. 8GB DDR4 + 10 GB swap

It's pretty cool that we have the ability to swap any token on the Mango UI now, but I think the page is a bit sparse and unintuitive for new users. For example, as a new user, I don't immediately know why I should use this on Mango instead of just going to Orca/Raydium/Serum. My first thought is: oh look Mango has a swap thing that's probably just a worse version of some other project that focuses on that exclusively.

@saml33 Can you work on making this a bit more intuitive to use? Maybe, some kind of info to signal that the Swap feature is strictly better than going elsewhere. If you think it's already perfect please say so!

How do I make the default design theme "Dark" instead of "Mango"? In which file should I change the code?And is it also possible to remove the Mango theme from the app?

This is an attractive nuisance. New users might think that's their account address and would transfer SOL there, and lose their money.

That address also shows at https://trade.mango.markets/account. If there's a good reason to show it, a warning not to send money there might be useful.

1. I think the switch icon with the double arrows is not very intuitive and fast. For one, the spot markets are first but they're not necessarily the most popular markets (with the exception of one person market making the SOLUSDC). I think it would be cleaner if it was sorted by 24 hour perp volume and the spot markets placed below the perp markets with the same ordering (I understand we don't have an easy way to query spot volumes). I think the switch icon itself is not an inuitive symbol. I didn't know that I could use it to switch between markets. Maybe a dropdown symbol would be more intuitive? Maybe if the market name (e..g SOL-PERP) itself can be clicked to bring about the drop down? I don't know.

2. The yellow connect wallet in the top right is way too bright when using the Mango theme. It's more acceptalbe in dark theme. Can we tone it down a bit?

Screencast for trying to sort by market, but clicking any of the other column headers doesn't do anything.

I really like the new Account page deployed in https://alpha.mango.markets/account

I'm going to use this Issue to list all minor bugs

1. When you hit Claim Rewards in the top right, it doesn't update the value after tx is successful
2. It's a bit confusing that this says pnl (24 hours) but is actually showing total lifetime pnl. Also pnl on the left is showing total pnl including spot. Maybe naming will help here?
   

Hey team!

Would you be interested in my help to put together the GenesysGo auth (I just noticed that you removed it)?

Trying to run dev locally. Crashes

There seems to be a 404 when accessing files at the public folder root. I noticed it when I checked for apple-touch-icon.png via https://mango.markets/apple-touch-icon.png. Manifest.json also throws a 404 (search engines do not like that - see attached screenshot when I analyzed the page using Google tools).