Pages: 1 [2] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 18 post(s) |
|
CCP FoxFour
C C P C C P Alliance
2908
|
Posted - 2014.02.11 21:28:00 -
[31] - Quote
Luigi Thirty wrote:If the problem is numbers that are too big for 32-bit, why not just send them only as strings instead of an integer format that may break applications when it gets too big and let the application worry about manipulating them?
This way an application gets to choose and the consumer should be aware of the limitations of their language. Either way it doesn't really matter, it's not something that is up for discussion at this time and I wouldn't be the person to discuss it with. CCP FoxFour // Game Designer @regnerba |
|
Draleth
Brave Newbies Inc. Brave Collective
14
|
Posted - 2014.02.12 03:13:00 -
[32] - Quote
Here's a comparison between the sample CREST killmail endpoint data and the result of my recursive transformation code on the V2 XML data; they're actually surprisingly similar, excluding the foreign references: https://gist.github.com/amcgregor/194ccbe33e199b2d785e
I'm disappointed that the new API, after having been given a clean slate, continues to invent "unique" (in terms of I've never seen that done by anyone before) edge cases especially ones that correct primarily non-issues.
Every JS implementation I tested supported at least 15 digits (all nines) accurate representation for integers. In actuality the largest "integer" an IEEE 754 double-precision floating point number can represent, as used by the ECMAScript standard is: 9,007,199,254,740,992, or 2^53, the number of bits assigned to the mantissa of a 64-bit float. JavaScript is defined as using this representation, see: http://ecma262-5.com/ELS5_HTML.htm#Section_8.5
So far the largest ID I've seen for character, corporation, or alliance is 2,081,394,931, so there's some room for growth.
But, too late to fix it, I guess. Just more preprocessing for me to do later.
(Side note: if the number is being used for bitwise operations or shifts the limitation is somewhat stricter at a 32-bits.) |
|
CCP FoxFour
C C P C C P Alliance
2912
|
Posted - 2014.02.12 09:21:00 -
[33] - Quote
Just to be clear, I don't fully know or understand the decision for both string and none string representation of numbers in CREST. If you would like to talk about the design of CREST come to Fanfest and those that worked on it I am sure would love to talk your ears off.
For now though, lets keep this thread focused specifically on this endpoint.
There are currently 3 known issues with the endpoint: 1) If a killmail has types on it that were deleted in the past, for example the old probes, the endpoint would choke and die. /sad panda. 2) If there was a sleeper or other NPC on the killmail that belonged to a faction and not a corporation the endpoint would choke. 3) The image links for corporations, alliances, and factions did not work.
All three issues have been fixed and should hopefully be deployed during Thursdays downtime.
Issue 1 was a tricky fix because there are a few ways to fix it none of which are really that good. The chosen solution is to carry on as normal but replace the name of the item with "Invalid item".
Issue 2 was due to some NPCs not being in a corporation. When the killmail is generated in those cases their corporationID is populated with a factionID and the endpoint would choke when trying to match a factionID to a corporation. I now have some special casing in there to deal with this and if a corpID is actually a factionID put it into the faction slot as it should.
Issue 3 was really just me not testing well enough. Characters use .jpg and tested fine but corps, alliances, and factions all use .png but I clearly didn't test that and thought they would all be jpg. I was clearly wrong. This has been fixed.
Sorry for the brokens but hopefully that should clear up most of the problems. If you have any further issues after Thursday please let me know and I will see about fixing them ASAP. CCP FoxFour // Game Designer @regnerba |
|
|
CCP FoxFour
C C P C C P Alliance
2913
|
Posted - 2014.02.13 10:39:00 -
[34] - Quote
Due to me being terrible, occupied with far to many things, and just what not these fixes will not be going out today (Thursday the 13th). I will get them out at the earliest opportunity and will let you know when they go out. So sorry! :( CCP FoxFour // Game Designer @regnerba |
|
Harvey James
The Sengoku Legacy
649
|
Posted - 2014.02.14 12:31:00 -
[35] - Quote
is this too replace the normal API killboards as they don't seem too work atm? Tech 3's need to be multi role ships not cruiser hulls with battleship tank and insane resists ABC's are clearly T2 in all but name.. remove drone assist mechanic. Nerf web strength ..... module tiercide FTW role based instead of tiers please. |
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
2641
|
Posted - 2014.02.14 13:05:00 -
[36] - Quote
Harvey James wrote:is this too replace the normal API killboards as they don't seem too work atm?
This is to replace manual posting of kill mails, with a way that can be immediately verified. Steve Ronuken for CSM 9! http://www.fuzzwork.co.uk/ Twitter: @fuzzysteve on Twitter |
Peter Powers
Terrorists of Dimensions Free 2 Play
201
|
Posted - 2014.02.14 14:34:00 -
[37] - Quote
Harvey James wrote:is this too replace the normal API killboards as they don't seem too work atm? can you explain what you mean by that? 3rdPartyEve.net - your catalogue for 3rd party applications |
Crasniya
Strange Energy Gentlemen's Agreement
378
|
Posted - 2014.02.14 16:37:00 -
[38] - Quote
This is fantastic, FoxFour, glad to see CREST finally moving forwards. :)
Though I suppose this explains why Planetary Conquest hasn't been fixed. :/ |
Luigi Thirty
GoonWaffe Goonswarm Federation
40
|
Posted - 2014.02.16 21:38:00 -
[39] - Quote
Harvey James wrote:is this too replace the normal API killboards as they don't seem too work atm?
No they fixed that with a new endpoint already. This is for authenticating killmails so they can be entered immediately by a user. |
|
CCP FoxFour
C C P C C P Alliance
2919
|
Posted - 2014.02.18 14:47:00 -
[40] - Quote
CCP FoxFour wrote:Just to be clear, I don't fully know or understand the decision for both string and none string representation of numbers in CREST. If you would like to talk about the design of CREST come to Fanfest and those that worked on it I am sure would love to talk your ears off.
For now though, lets keep this thread focused specifically on this endpoint.
There are currently 3 known issues with the endpoint: 1) If a killmail has types on it that were deleted in the past, for example the old probes, the endpoint would choke and die. /sad panda. 2) If there was a sleeper or other NPC on the killmail that belonged to a faction and not a corporation the endpoint would choke. 3) The image links for corporations, alliances, and factions did not work.
All three issues have been fixed and should hopefully be deployed during Thursdays downtime.
Issue 1 was a tricky fix because there are a few ways to fix it none of which are really that good. The chosen solution is to carry on as normal but replace the name of the item with "Invalid item".
Issue 2 was due to some NPCs not being in a corporation. When the killmail is generated in those cases their corporationID is populated with a factionID and the endpoint would choke when trying to match a factionID to a corporation. I now have some special casing in there to deal with this and if a corpID is actually a factionID put it into the faction slot as it should.
Issue 3 was really just me not testing well enough. Characters use .jpg and tested fine but corps, alliances, and factions all use .png but I clearly didn't test that and thought they would all be jpg. I was clearly wrong. This has been fixed.
Sorry for the brokens but hopefully that should clear up most of the problems. If you have any further issues after Thursday please let me know and I will see about fixing them ASAP.
This fixes have been submitted and should be going out with tomorrows (February 19th) downtime. If you run into any issues after that be sure to let me know. :)
Again, sorry for the delay on getting these fixes out.
CCP FoxFour // Game Designer @regnerba |
|
|
Squizz Caphinator
Woopatang
155
|
Posted - 2014.02.19 16:54:00 -
[41] - Quote
The fixes were successful. zKillboard currently has over 10k crest endpoints in our database, of which just over 700 of them had errors prior to this release.
After the release, only 4 have errors, and 2 of those are invalid hashes.
Thanks FoxFour! Various projects I enjoy putting my time into: http://zkillboard.com | http://evewho.com | http://eve-kill.net | http://evechatter.com | http://skillq.net |
|
CCP FoxFour
C C P C C P Alliance
2921
|
Posted - 2014.02.19 17:17:00 -
[42] - Quote
Squizz Caphinator wrote:The fixes were successful. zKillboard currently has over 10k crest endpoints in our database, of which just over 700 of them had errors prior to this release.
After the release, only 4 have errors, and 2 of those are invalid hashes.
Thanks FoxFour!
I will be looking more into these as soon as possible to see if they are just broken killmails or if my endpoint is broken. CCP FoxFour // Game Designer @regnerba |
|
Fade Toblack
Per.ly The 20 Minuters
69
|
Posted - 2014.02.19 18:06:00 -
[43] - Quote
The Int64/String dual-property thing was mentioned back during the AT CREST trial.
https://forums.eveonline.com/default.aspx?g=posts&t=257854
|
|
CCP FoxFour
C C P C C P Alliance
2921
|
Posted - 2014.02.20 14:55:00 -
[44] - Quote
Hey guys,
So with yesterdays release when I attempted to fix the issue with Sleepers and other factions while I did test with factions and making sure that worked I failed to test what happens when there are multiple attackers. The problem basically comes down to me comparing a string to int when checking if someone is in a corporation or not. You can guess how well that went, a whole lot of false negatives.
I have a patch ready to go, however it is going to have to wait until Monday. While I know how much this affects you third party guys it's still not really an emergency and deploying anything but emergency patches on a Friday is... well not desired.
So Monday will get this fix out and hopefully return things to good. I am also in the process of getting a better test script setup that will use a random selection of killmails from TQ to hopefully find these problems sooner... but even then since the corp field is optional I would have had to see it.
TL;DR: I r did dumb dumb and will have a fix out Monday. CCP FoxFour // Game Designer @regnerba |
|
Powers Sa
941
|
Posted - 2014.02.20 15:09:00 -
[45] - Quote
Thanks for responding so quick to a little twitter joshing around. lol |
Salvoxia
Evoke. Ev0ke
6
|
Posted - 2014.02.20 16:48:00 -
[46] - Quote
Thank you! |
|
CCP FoxFour
C C P C C P Alliance
2925
|
Posted - 2014.02.25 20:17:00 -
[47] - Quote
Just as an update, the most recent hotfix was deployed today and we seem to be good for the most part.
I was presented with a potential issue though: https://zkillboard.com/detail/36931325/
The NPC in there, which appears to just be a torpedo, has no corporation listed. I don't know why this would be happening after a quick look over the code but I will continue to dig and see if I can find out why.
If you have any other examples of issues or broken things with the CREST killmails endpoint please let me know. It has been a bit of a rough launch and I apologize for that but I am hoping we are through the worst of it now. Thank you for all your patience. CCP FoxFour // Game Designer @regnerba |
|
Karbowiak
4M-CORP
178
|
Posted - 2014.02.25 20:19:00 -
[48] - Quote
CCP FoxFour wrote:Just as an update, the most recent hotfix was deployed today and we seem to be good for the most part. I was presented with a potential issue though: https://zkillboard.com/detail/36931325/The NPC in there, which appears to just be a torpedo, has no corporation listed. I don't know why this would be happening after a quick look over the code but I will continue to dig and see if I can find out why. If you have any other examples of issues or broken things with the CREST killmails endpoint please let me know. It has been a bit of a rough launch and I apologize for that but I am hoping we are through the worst of it now. Thank you for all your patience.
Filthy NPC scum, they always cause troubles!
gj tho, <3 |
Squizz Caphinator
Woopatang
155
|
Posted - 2014.02.25 20:21:00 -
[49] - Quote
Please don't hate me! Various projects I enjoy putting my time into: http://zkillboard.com | http://evewho.com | http://eve-kill.net | http://evechatter.com | http://skillq.net |
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
2728
|
Posted - 2014.02.25 20:23:00 -
[50] - Quote
CCP FoxFour wrote:Just as an update, the most recent hotfix was deployed today and we seem to be good for the most part. I was presented with a potential issue though: https://zkillboard.com/detail/36931325/The NPC in there, which appears to just be a torpedo, has no corporation listed. I don't know why this would be happening after a quick look over the code but I will continue to dig and see if I can find out why. If you have any other examples of issues or broken things with the CREST killmails endpoint please let me know. It has been a bit of a rough launch and I apologize for that but I am hoping we are through the worst of it now. Thank you for all your patience.
Some kills are just bad in game. Like one of the people on my Dread loss has no ship Steve Ronuken for CSM 9! https://forums.eveonline.com/default.aspx?g=posts&m=4236322 http://www.fuzzwork.co.uk/ Twitter: @fuzzysteve on Twitter |
|
|
CCP FoxFour
C C P C C P Alliance
2925
|
Posted - 2014.02.25 20:38:00 -
[51] - Quote
Steve Ronuken wrote:CCP FoxFour wrote:Just as an update, the most recent hotfix was deployed today and we seem to be good for the most part. I was presented with a potential issue though: https://zkillboard.com/detail/36931325/The NPC in there, which appears to just be a torpedo, has no corporation listed. I don't know why this would be happening after a quick look over the code but I will continue to dig and see if I can find out why. If you have any other examples of issues or broken things with the CREST killmails endpoint please let me know. It has been a bit of a rough launch and I apologize for that but I am hoping we are through the worst of it now. Thank you for all your patience. Some kills are just bad in game. Like one of the people on my Dread loss has no ship
Which makes this all the harder. Killmails are so unreliable right now that I basically have to make everything about them optional and add way more if statements than I ever wanted to. CCP FoxFour // Game Designer @regnerba |
|
TheSmokingHertog
TALIBAN EXPRESS
194
|
Posted - 2014.02.25 22:06:00 -
[52] - Quote
*wonders about ban hammers and killboard links* |
|
CCP FoxFour
C C P C C P Alliance
2926
|
Posted - 2014.02.26 09:02:00 -
[53] - Quote
TheSmokingHertog wrote:*wonders about ban hammers and killboard links*
Not sure what you mean... CCP FoxFour // Game Designer @regnerba |
|
Peter Powers
Terrorists of Dimensions Free 2 Play
203
|
Posted - 2014.02.26 10:24:00 -
[54] - Quote
probably he is confusing this with C&P 3rdPartyEve.net - your catalogue for 3rd party applications |
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
2733
|
Posted - 2014.02.26 14:07:00 -
[55] - Quote
CCP FoxFour wrote:TheSmokingHertog wrote:*wonders about ban hammers and killboard links* Not sure what you mean...
There are rules on the forum saying 'no killboard links, unless you're in crime and punishment'
But we're living to the spirit of the rule (don't troll and gloat), if not the word Steve Ronuken for CSM 9! https://forums.eveonline.com/default.aspx?g=posts&m=4236322 http://www.fuzzwork.co.uk/ Twitter: @fuzzysteve on Twitter |
darkchild's corpse
Rens Nursing Home
3
|
Posted - 2014.03.03 11:08:00 -
[56] - Quote
is there an easy way to get the crest api endpoint link from the old api killlog? would be cool to have ONE endpoint to get killmails for posting manually (via crest endpoint) and via old crappy api thingy
im not asking you to implement it because its bullshit to work on that old api anymore imo... ( or maybe its just a rly tiny change that takes only 5 mins :3 )
but afaik this is how the endpoint link is build: http://public-crest.eveonline.com/killmails/kill-id/some-magic-hash/
we get the kill ID from the old api.... so thats no problem. but what about the hash? how is that generated? is there an easy way to generate the hash out of the information from the old API?
i like the fact that there are item names in the crest api... so i dont have to maintain a stupid item table in my DB \o/ |
|
CCP FoxFour
C C P C C P Alliance
2932
|
Posted - 2014.03.03 14:19:00 -
[57] - Quote
darkchild's corpse wrote:is there an easy way to get the crest api endpoint link from the old api killlog? would be cool to have ONE endpoint to get killmails for posting manually (via crest endpoint) and via old crappy api thingy im not asking you to implement it because its bullshit to work on that old api anymore imo... ( or maybe its just a rly tiny change that takes only 5 mins :3 ) but afaik this is how the endpoint link is build: http://public-crest.eveonline.com/killmails/kill-id/ some-magic-hash/ we get the kill ID from the old api.... so thats no problem. but what about the hash? how is that generated? is there an easy way to generate the hash out of the information from the old API? i like the fact that there are item names in the crest api... so i dont have to maintain a stupid item table in my DB \o/
At this point in time we are not ready to say what the hash is, and getting it in the old API is a bit tricky. So no, not at this time. Sorry. :( CCP FoxFour // Game Designer @regnerba |
|
|
|
|
Pages: 1 [2] :: one page |
First page | Previous page | Next page | Last page |