보고 • Board Game Arena

모든 보고

#12779: "Player game history "from date" field glitch on /gamestats renders application unusable."

fixed: 버그가 수정되었습니다

무엇에 대한 보고입니까?

BGA 사이트

무슨 일이 발생했나요? 아래에서 선택하세요

사이트 이용 중 올바르게 동작하지 않았던 것 (게임 중 제외)

무슨 일이 발생했나요? 아래에서 선택하세요

사이트 이용 중 올바르게 동작하지 않았던 것 (게임 중 제외)

같은 내용에 대하여 이미 등록된 보고가 있는지 확인해주세요

그렇다면, 이 보고를 추천해주세요. 추천을 가장 많이 받은 보고부터 우선적으로 처리됩니다!

#	Status	Votes	Game	Type	Title	Last update

상세한 설명

보고 이력

2019년 Jun 14일 06:46 • BulgarianHorde • 개발자가 아직 버그를 재현하지 않았습니다:

Things I've tried:
- Different devices
- different start dates
- inputting and end date first
- typing in the date(s)
everything resulted in the same effect. I have not been able to confirm that other parties have experienced this problem.

2019년 Jun 19일 15:10 • BulgarianHorde • 개발자가 아직 버그를 재현하지 않았습니다:

bug reproduced by DaMaster and Delferth
(thanks!)

2019년 Jun 19일 15:11 • Delferth • 개발자가 아직 버그를 재현하지 않았습니다:

Other parties do experience this.

2020년 Mar 8일 22:19 • Smugs • 개발자가 아직 버그를 재현하지 않았습니다:

This is still an issue

2020년 Apr 14일 20:53 • Sugs • 개발자가 아직 버그를 재현하지 않았습니다:

+1 Experienced on both desktop (Firefox) and mobile (Android), which actually crashes the app.

The bug status is still "Bug has not been reproduced by developers yet" — Have they attempted a repro? It seems to be just broken, I don't think it will be hard to reproduce.

Impact: Right now there's no other way to view non-recent history more than several entries at a time, other than clicking "More" and scrolling, click and scroll, click and scroll, endlessly.

2020년 Apr 14일 20:55 • Sugs • 개발자가 아직 버그를 재현하지 않았습니다:

+2 more users (cookiea and chaos05) who've confirmed the same

This would be great to get fixed, especially since we are interested in tracking our game scores for a particular game. Thanks!

2020년 Apr 14일 22:13 • Sugs • 개발자가 아직 버그를 재현하지 않았습니다:

I think you can consolidate these 2 later bug reports with this one:
boardgamearena.com/bug?id=13057
boardgamearena.com/bug?id=13608

More details.... This is probably at least 2 different bugs:
– Case 1: Entering a valid start date causes endless "Error while processing Database request" red error box overlays.
– Case 2: Entering a valid end date cause endless redirects (flickering). This is worse than endless reloads because it also floods the browser history, forcing the user to close the tab (navigating back doesn't work).

Additionally:
– Entering an invalid date does not cause a problem: the page resets the field and reloads (via a fresh URL).
– Only valid dates cause these issues, and it's the same whether typed or using the date picker.

– The 2 different outcomes suggest Case 1 is creating and executing a SQL/db query but that the query is bad (date format error maybe?) but that some other exception is derailing Case 2 either before or after the query.
– My off-the-wall guess would be before and while actually constructing the query (perhaps assuming start date exists and is valid?).

2020년 Apr 14일 22:49 • Sugs • 개발자가 아직 버그를 재현하지 않았습니다:

Debugging within Firefox, I see 2 GETs on every update to the search inputs. This pair of requests get repeated forever. For example on a start date change:
– boardgamearena.com/gamestats?player=85562224&opponent_id=0&start_date=1586329200&finished=0&refreshtemplate=1&dojo.preventCache=1586895615311
– boardgamearena.com/gamestats/gamestats/getGames.html?player=85562224&opponent_id=0&start_date=1586329200&finished=0&updateStats=1&dojo.preventCache=1586895617663

(The only change between requests is every URL gets a new dogo.preventCache value, presumably to force a fresh DB read.)

Same with end date (but with end_date URL param).

I was curious if the bug was related to not having both start and end date (which a user never is able to achieve because the page becomes unusable after setting either one), so I manually cold loaded a URL with both in it:
– boardgamearena.com/gamestats?player=85562224&opponent_id=0&start_date=1586329200&end_date=1586674800&finished=0

Same result as the Case 1 (start date) – endless DB errors.

Hope that helps!

P.S. BTW, I'd highly recommend some kind of quadratic backoff and/or even a hard abort after some number of consecutive errors... at least for some class of endpoint calls. I realize this is trickier in cases like this where the looping is actually a chain of reloads, but this does seem to be common pattern across your whole site (e.g. voice chat, move transmit retries, etc). This has to dramatically affect site stability however — even 1 unbroken loop slams your site with requests, but any blip in infrastructure multiplies then compounds it! Anyway sorry for the digression...

2020년 May 17일 20:52 • megamau • 개발자가 아직 버그를 재현하지 않았습니다:

Confirmed also by user megamau. Unusable in any way

2020년 Jul 24일 02:46 • KongKing123 • 개발자가 아직 버그를 재현하지 않았습니다:

I can confirm that this is still an issue on Firefox 78.0.2, this is what it looks like: i.postimg.cc/fbrzbK7X/Game-history-date-crash.png

2020년 Nov 22일 10:06 • v1p3r • 개발자가 아직 버그를 재현하지 않았습니다:

Using on firefox 82.0.3 (64-bit)
Mac OS 10.15.7 (19H15)

The issue is still persistent, tried different date ranges from 10 year to 1 year all of them have same issue

2020년 Nov 23일 10:28 • Een • 버그가 수정되었습니다:

Thanks, this will be fixed with the next release.

2020년 Nov 23일 13:09 • KongKing123 • 버그가 수정되었습니다:

Great! These duplicates can then also be closed:

* boardgamearena.com/bug?id=13057
* boardgamearena.com/bug?id=13608
* boardgamearena.com/bug?id=28457

2020년 Nov 23일 13:11 • KongKing123 • 버그가 수정되었습니다:

Another duplicate: boardgamearena.com/bug?id=18618

리포트에 내용 추가하기

여기에 버그를 재현하거나 당신의 제안을 이해하는 데 관련 있는 내용을 아무것이나 남겨주십시오:

다른 테이블 번호 / 수 번호
새로고침을 해서 문제가 해결 되었습니까?
문제가 얼마나 자주 일어났습니까?
만약에 버그에 대한 스크린샷을 가지고 계신다면 Imgur.com 사이트에 업로드 하시고, 여기에 링크를 복사/붙여넣기 하시기 바랍니다.

취소 업데이트 보고

#12779: "Player game history "from date" field glitch on /gamestats renders application unusable."

무엇에 대한 보고입니까?

무슨 일이 발생했나요? 아래에서 선택하세요

무슨 일이 발생했나요? 아래에서 선택하세요

같은 내용에 대하여 이미 등록된 보고가 있는지 확인해주세요

상세한 설명

보고 이력

리포트에 내용 추가하기

보고의 상태를 다음으로 변경:

도움말

기여하기

탐색하기

저희를 팔로우해주세요