该用户的聊天记录定位。
<@707597210845446214> <@1361217824776786031> can u please look at this. is it a correct trading engine behaviour or its a bug ?
<@707597210845446214> <@1361217824776786031> can u please look at this. is it a correct trading engine behaviour or its a bug ?
are u rly trying to scam anybody in dev chat ?
are u rly trying to scam anybody in dev chat ?
i placed GTC order, it partially matched than canceled as if it was FAK order. what didnt u understand ?
i placed GTC order, it partially matched than canceled as if it was FAK order. what didnt u understand ?
???
???
Looks like a bug. 1) Placing GTC order with size = 5 2) Placing GTC order matches some orders in orderbook. matched size = 0.91 3) Order canceles. So i expected to see my GTC order in orderbook. with matched size = 0.91 and unmatched size = 4.09 but there is no order in orderbook. I know that min order size for maker order is 5. I suppose that trading engine passed my initial order bcs its size was 5. than match occured. than tried to place rest of limit order but remaining order size < 5 so it was canceled. But it looks like an error, bcs initial order size was 5 and its ok, trading engine accepted order and even partially matched. But than canceled the remaining part of GTC order. orderID = 0x4546b5857294a3920370acc6563d2bad41bad46fe94af0290226d3101eac9bda
Looks like a bug. 1) Placing GTC order with size = 5 2) Placing GTC order matches some orders in orderbook. matched size = 0.91 3) Order canceles. So i expected to see my GTC order in orderbook. with matched size = 0.91 and unmatched size = 4.09 but there is no order in orderbook. I know that min order size for maker order is 5. I suppose that trading engine passed my initial order bcs its size was 5. than match occured. than tried to place rest of limit order but remaining order size < 5 so it was canceled. But it looks like an error, bcs initial order size was 5 and its ok, trading engine accepted order and even partially matched. But than canceled the remaining part of GTC order. orderID = 0x4546b5857294a3920370acc6563d2bad41bad46fe94af0290226d3101eac9bda
Looks like a bug. 1) Placing GTC order with size = 5 2) Placing GTC order matches some orders in orderbook. matched size = 0.91 3) Order canceles. So i expected to see my GTC order in orderbook. with matched size = 0.91 and unmatched size = 4.09 but there is no order in orderbook. I know that min order size for maker order is 5. I suppose that trading engine passed my initial order bcs its size was 5. than match occured. than tried to place rest of limit order but remaining order size < 5 so it was canceled. But it looks like an error, bcs initial order size was 5 and its ok, trading engine accepted order and even partially matched. But than canceled the remaining part of GTC order as if the order type was FAK. orderID = 0x4546b5857294a3920370acc6563d2bad41bad46fe94af0290226d3101eac9bda
Looks like a bug. 1) Placing GTC order with size = 5 2) Placing GTC order matches some orders in orderbook. matched size = 0.91 3) Order canceles. So i expected to see my GTC order in orderbook. with matched size = 0.91 and unmatched size = 4.09 but there is no order in orderbook. I know that min order size for maker order is 5. I suppose that trading engine passed my initial order bcs its size was 5. than match occured. than tried to place rest of limit order but remaining order size < 5 so it was canceled. But it looks like an error, bcs initial order size was 5 and its ok, trading engine accepted order and even partially matched. But than canceled the remaining part of GTC order as if the order type was FAK. orderID = 0x4546b5857294a3920370acc6563d2bad41bad46fe94af0290226d3101eac9bda
i reported this in bug-report channel. and attached txt file with full logs. but a clown said that this is a scem file. so i shortly describe an issue here
i reported this in bug-report channel. and attached txt file with full logs. but a clown said that this is a scem file. so i shortly describe an issue here
time=2026-06-25T22:08:12.203+03:00 level=ERROR msg="order was not canceled" eventSlug=highest-temperature-in-ankara-on-june-27-2026 assetID=16617666799727151967108757299055364325117701119235127812703017701478903281023 orderID=0xae2f361cfacb16cdc74dc1a07a6b44302ee4b8727f8b68c0db2517b8f7f12850 reason="matched orders can't be canceled" but as a result the order was canceled. i received a trade message via web socket. with status = MATCHED then received this http response message and DIDNT receive a second trade message with status = CONFIRMED. and looks like my order was canceled bcs i dont see assets bought via my maker order
time=2026-06-25T22:08:12.203+03:00 level=ERROR msg="order was not canceled" eventSlug=highest-temperature-in-ankara-on-june-27-2026 assetID=16617666799727151967108757299055364325117701119235127812703017701478903281023 orderID=0xae2f361cfacb16cdc74dc1a07a6b44302ee4b8727f8b68c0db2517b8f7f12850 reason="matched orders can't be canceled" but as a result the order was canceled. i received a trade message via web socket. with status = MATCHED then received this http response message and DIDNT receive a second trade message with status = CONFIRMED. and looks like my order was canceled bcs i dont see assets bought via my maker order
status=500 body={"error":"rpc error: code = DeadlineExceeded desc = context deadline exceeded"} problem solved ?
status=500 body={"error":"rpc error: code = DeadlineExceeded desc = context deadline exceeded"} problem solved ?
post orders failed: status=500 body={"error":"rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
post orders failed: status=500 body={"error":"rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
true. played => attempted to play => willing to attempt to play => what's next ?
true. played => attempted to play => willing to attempt to play => what's next ?
depends on how u look at FF i can say that they had tech difficulties and FF map 2 and map 3. So they didnt FF clincing map they FF the match => so 50-50 u can say that they FF map 2 => score = 1-1 and then FF map 3 => map 3 was clincing map so Over.
depends on how u look at FF i can say that they had tech difficulties and FF map 2 and map 3. So they didnt FF clincing map they FF the match => so 50-50 u can say that they FF map 2 => score = 1-1 and then FF map 3 => map 3 was clincing map so Over.
"If the match begins but is not completed, and one team wins due to the opponent's match forfeiture, disqualification, or walkover, this market will resolve to 50-50" this is written in the rules too
"If the match begins but is not completed, and one team wins due to the opponent's match forfeiture, disqualification, or walkover, this market will resolve to 50-50" this is written in the rules too
u show picks and bans from the second map. as commentator said "Це реально був техлуз, на перший, друзі" translate into english "That was really a technical loss, the first one, guys"
u show picks and bans from the second map. as commentator said "Це реально був техлуз, на перший, друзі" translate into english "That was really a technical loss, the first one, guys"
as i said score was already 1-0 when map 2 started. and commentator said that it was tech lose on map 1 if it wasn't tech lose on map1 why the score was already 1-0 when 2nd map started and they really played it
as i said score was already 1-0 when map 2 started. and commentator said that it was tech lose on map 1 if it wasn't tech lose on map1 why the score was already 1-0 when 2nd map started and they really played it
Polymarket