What are the next 10 bugs we'll fix on Manifold?

Ṁ4.6k

Ṁ1.5k

resolved Oct 26

ALL

10%9%

Multiple (consecutive) links in a comment don't open properly

10%8%

Opening a market page shows outdated info for a few seconds before up-to-date info loads

10%8%

Comments are reverse-chronological but hitting reply adds at the bottom.

10%8%

Still getting notifs while unwatched

10%7%

Sell free answer tooltip showing up in wrong place

10%7%

Mentioning a user with '@' popup shows Austin's avatar first for any user

10%7%

Tooltip for payout is open by default on desktop when opening Market info dialog ('...' menu)

10%5%

The betting streak notification says I have a 3.5-day betting streak when it should in fact say I have a 7-day streak.

10%5%

Manifold is counting loan values towards profit: https://manifold.markets/AndrewG?tab=bets

10%3%

When you create a market with a too high MAX number, the page shows: Application error: a client-side exception has occurred (see the browser console for more information).

0.1%Other

18%

ANTE

0.1%

On Android Firefox, if you click on 'embed a market' in a comment, the cancel button does nothing. You cannot close the pop-up.

0.1%

Writing a free response comment reply gets erased if someone adds a new answer before you submit

0.2%

Hovering over the down arrow on a market currently at 99.0% changes it to 96%, which has a smaller display width, which causes the arrows to move, and this can then rapidly flicker back and forth.

0.1%

Limits

0.2%

Wrong liquidity amount shown after inject & withdraw liquidity

0.1%

On Android Firefox, if the url bar is not shown on the bottom of the page, none of the bottom buttons work

0.1%

Limits not available in sell menu

0.0%

Notifications show up as "unread"(and trigger the notice in the sidebar) that the user has already read.

Aug 24, 10:20pm: ~~What are the next 5 bugs we'll fix on Manifold?~~ → What are the next 10 bugs we'll fix on Manifold?

Rules:

- Eligible answers must be submitted before the bug is fixed

- The market resolves once 10 eligible bugs are fixed, each of which gets 10% of the pool.

I hope this is a good way of surfacing bugs that we should be fixing!

Previous bug market:

https://manifold.markets/JamesGrugett/what-are-the-next-5-bugs-well-fix-o-4e848dc44637

Aug 24, 10:20pm: Update: I think I'll just make this the next 10 bugs that are fixed to reduce costs of switching to a new market. I'll add more ante money so no one loses out.

Get Ṁ600 play money

🏅 Top traders

#	Name	Total profit
1		Ṁ2,270
2		Ṁ868
3		Ṁ398
4		Ṁ210
5		Ṁ58

25 Comments

17 Holders

108 Trades

Sort by:

There were more than 10 bugs fixed, so I had to pick which ones were solved first.

I tried to deduplicate submitted bugs and pass over some that were not that specific. Probably still made some mistakes since these bugs were not fresh in memory — sorry!

Thanks for participating!

@JamesGrugett can this be resolved?

@hamnox Ah, yes. Sorry for the delay!

@JamesGrugett pls resolve

@JamesGrugett I think 10 bugs in this market have been fixed by now - though I'm not sure about the betting streaks

@Sinclair betting streaks are def fixed

bought Ṁ200

@wavedash fixed

bought Ṁ100

I believe this got fixed recently, though can't find the PR. Does it still happen?

bought Ṁ150

this is fixed

@jack it would probably be good if there's some kind of notice on the page that this is possibly outdated, and updates are still being fetched, eh?

Specifically, the probability, graph, comments, bets, etc all show a (prerendered, cached?) version that might be outdated, and takes a few seconds to update to the latest data. It's problematic because I feel like I can't trust the page, and I don't always know when it's loaded the realtime data. On the other hand, not loading at all for several seconds would also be pretty lousy.

Very high latencies across the board.

While the client side model was unworkable on raw tables, it would probably be better using condensed/capped tables; the UI used to be fast/beautiful and now is stale/“A Trader”/300-x000ms response times etc.

💰💰💰

Very often markets lag (out of date numbers, “trader” instead of names); comments as well

Better than insta-crash but very noticeable.

@Gigacasting 🎉

“🏠” has latency; bets/markets back to 💯%

@ian Oh actually I wonder if I deployed this to prod

@ian Great thanks! My thoughts: If I have shares in the market than I should still get a notif for resolutions. I could go either way on new answers on your own question.

@Gigacasting I think this may be fixed! Could you try again?

@jack fixed this for comments, undecided on whether this unwatch filtering should apply to email:
- resolutions
- new answers on your own questions
as well.