Skip to content
This repository has been archived by the owner on Feb 13, 2024. It is now read-only.

No perp account for basket token USDC #11

Closed
viralhysteria opened this issue Nov 12, 2021 · 3 comments
Closed

No perp account for basket token USDC #11

viralhysteria opened this issue Nov 12, 2021 · 3 comments

Comments

@viralhysteria
Copy link

viralhysteria commented Nov 12, 2021

Using the MarketMakingQuickstart readme step-by-step (using WSL2 properly configured), returns following error after calling account balance in second step of part 9

Traceback (most recent call last):
File "/app/bin/show-account-balances", line 78, in
report: mango.AccountInstrumentValues = mango.AccountInstrumentValues.from_account_basket_base_token(
File "/app/mango/accountinstrumentvalues.py", line 114, in from_account_basket_base_token
raise Exception(f"No perp account for basket token {account_slot.base_instrument.symbol}")
Exception: No perp account for basket token USDC

usdc deposit was however subtracted from account without error

also, there seems to be an issue with displaying some characters on WSL but i'm not sure if that's on WSL side, i've tried cycling a couple different mono fonts

ubuntu2004_bJgxBoMgJQ

@OpinionatedGeek
Copy link
Contributor

Hi,

Apologies - this should be fixed now in v3.2.3 if you pull the latest code.

As for WSL, it looks like either that subsystem or that terminal just isn't displaying Unicode properly - you should see object types like 𝙸𝚗𝚜𝚝𝚛𝚞𝚖𝚎𝚗𝚝𝚅𝚊𝚕𝚞𝚎 and 𝙿𝚛𝚒𝚌𝚎𝚍𝙰𝚌𝚌𝚘𝚞𝚗𝚝𝙸𝚗𝚜𝚝𝚛𝚞𝚖𝚎𝚗𝚝𝚅𝚊𝚕𝚞𝚎𝚜.

@viralhysteria
Copy link
Author

viralhysteria commented Nov 13, 2021

Thanks, the new pull did in fact fix the issue. No problems finishing the rest of the quick start.

Unicode display seems to be a long standing issue on WSL/Terminal based on their github due to poor (or no handling) for fallback fonts.
microsoft/terminal#306
microsoft/terminal#190

Running WSL through windows terminal after the update in the following issue fixed my output
microsoft/terminal#10478 (comment)

WindowsTerminal_32SHYbJCN1

@OpinionatedGeek
Copy link
Contributor

Excellent - glad it's working for you now, and apologies for the problems.

Thanks also for the info on the WSL problems - interesting stuff!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants