| Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 [17] 18 19 20 30 .. 30 :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |

Ambo
I've Got Nothing
|
Posted - 2010.07.28 11:47:00 -
[481]
1.5.1.1 is now available.
This hopefully fixes Anna's issue though I can't be 100% sure as I couldn't reproduce it. Assuming no further problems reported, I'm planning to put this on general release on Friday.
Complete list of changes for 1.5.1.1:
- EMMA will now inform the user at startup if there is new documentation available through the EMMA project page. (This can be disabled if you wish)
- Corrected a bug with the way corporate orders were processed. This could cause all sorts of odd behaviour and even crashes in certain situations.
- Corrected a bug that caused order notifications to fail in a particular situation: If the market order is created and is then cancelled, filled or expired before EMMA is aware of it then the order will never appear in the unacknowledged orders window. Historic orders that have been affected by this bug can be seen by going into Orders and changing the state dropdown to 'expired/filled' (Normally, with this filter on the view should be empty)
- Corrected a bug that could cause one character's or corp's update checkbox to appear under the scrollbar in the API update status window.
--------------------------------------
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.07.28 12:38:00 -
[482]
Nice work.
I've just updated, I'll report back later today.
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.07.28 22:37:00 -
[483]
Originally by: Ambo 1.5.1.1 is now available.
This hopefully fixes Anna's issue though I can't be 100% sure as I couldn't reproduce it.
Sorry, nop 
I'm seeing exactly the same errors, and now of course the shiny new asset tracking thingy is deciding that a whole bunch of newly bought items are "found" and that all the sold ones are "destroyed".
|

Kapila Parthalan
|
Posted - 2010.07.28 23:50:00 -
[484]
Originally by: Anna Weston I'm seeing exactly the same errors, and now of course the shiny new asset tracking thingy is deciding that a whole bunch of newly bought items are "found" and that all the sold ones are "destroyed".
I've also been seeing problems with false unacknowledged asset changes (specifically, a few missing items) since 1.5.1.0, which I have already reported to Ambo, but I don't think we have made progress on it. While the items that have been showing up as missing are indeed items I have been recently selling, the items and quantities of missing stuff don't match my sales too well. Can you tell us how well your bought/sold items match the gained/missing items?
I have verified that I get false missing assets even when my assets data is accurate both before and after an assets API update. I have also seen inaccurate assets data immediately after an update. Has your data been correct or are you getting these found/missing items because it is broken?
|

Ambo
I've Got Nothing
|
Posted - 2010.07.29 05:33:00 -
[485]
Originally by: Anna Weston
Originally by: Ambo 1.5.1.1 is now available.
This hopefully fixes Anna's issue though I can't be 100% sure as I couldn't reproduce it.
Sorry, nop 
I'm seeing exactly the same errors, and now of course the shiny new asset tracking thingy is deciding that a whole bunch of newly bought items are "found" and that all the sold ones are "destroyed".
Could you send me a copy of the orders XML files that are failing? ([email protected]) I can't see any other way to identify this problem.
Originally by: Kapila Parthalan
I've also been seeing problems with false unacknowledged asset changes (specifically, a few missing items) since 1.5.1.0, which I have already reported to Ambo, but I don't think we have made progress on it. While the items that have been showing up as missing are indeed items I have been recently selling, the items and quantities of missing stuff don't match my sales too well. Can you tell us how well your bought/sold items match the gained/missing items?
I have verified that I get false missing assets even when my assets data is accurate both before and after an assets API update. I have also seen inaccurate assets data immediately after an update. Has your data been correct or are you getting these found/missing items because it is broken?
You're problem is slightly different Kapila. In Anna's case, the orders data is not updated and so EMMA won't know about items for sale in those missing sell orders.
For you, I understand that the API updates are not giving any errors but that you just have some missing assets.
Do you use that particular item types for anything else? (i.e. production, contract sales, etc) --------------------------------------
|

Kapila Parthalan
|
Posted - 2010.07.29 10:59:00 -
[486]
Originally by: Ambo You're problem is slightly different Kapila. In Anna's case, the orders data is not updated and so EMMA won't know about items for sale in those missing sell orders.
For you, I understand that the API updates are not giving any errors but that you just have some missing assets.
Do you use that particular item types for anything else? (i.e. production, contract sales, etc)
Oh, I see. I haven't done anything with those assets other than sell on the market or move via courier contract. The courier contracts were a while before this issue, though, and should not have had any effect, plus the item I have been seeing missing the most has not been moved at all. The items definitely were not missing.
|

Ambo
I've Got Nothing
|
Posted - 2010.07.30 08:52:00 -
[487]
EMMA 1.5.1.2 beta is now available.
I've not been able to reproduce Anna's issue but in the course of investigating it, I've found several problems. In particular, it seems that the corporate orders API does actually return all corporate orders and not just the orders created by that character as I had thought.
Due to this, I've made changes to go back to the old system of only retrieving corporate orders for the selected character.
--------------------------------------
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.01 07:52:00 -
[488]
Originally by: Ambo EMMA 1.5.1.2 beta is now available.
I've not been able to reproduce Anna's issue but in the course of investigating it, I've found several problems. In particular, it seems that the corporate orders API does actually return all corporate orders and not just the orders created by that character as I had thought.
Due to this, I've made changes to go back to the old system of only retrieving corporate orders for the selected character.
That does seem to have fixed the problem of corporate orders not updating. However it has led to a return of the infinite-number-of-unacknowledged-orders-to-click-through problem. Overall I'd say it's the lesser of two evils.
|

Ambo
Mortis Angelus
|
Posted - 2010.08.01 15:18:00 -
[489]
Originally by: Anna Weston
Originally by: Ambo EMMA 1.5.1.2 beta is now available.
I've not been able to reproduce Anna's issue but in the course of investigating it, I've found several problems. In particular, it seems that the corporate orders API does actually return all corporate orders and not just the orders created by that character as I had thought.
Due to this, I've made changes to go back to the old system of only retrieving corporate orders for the selected character.
That does seem to have fixed the problem of corporate orders not updating. However it has led to a return of the infinite-number-of-unacknowledged-orders-to-click-through problem. Overall I'd say it's the lesser of two evils.
Glad to hear it. I *think* that the big stack of orders to click through might be because of a previous problem that was also fixed in the last update. Unfortunately, existing data will still have the problem so you might still see this for a while. --------------------------------------
|

Ambo
Mortis Angelus
|
Posted - 2010.08.03 08:09:00 -
[490]
Edited by: Ambo on 03/08/2010 08:09:07 Version 1.5.1.3 is now available as a beta, just a few small changes:
- Corrected a bug that caused the 'new documentation available' message to always display after an update.
- Added a new lost asset reason of 'Not lost'. This will cause the asset to be retained in EMMA's database, on the next asset update, it will be treated as normal. This is intended to overcome situations where EMMA thinks that an item has gone missing but it's actually just somewhere else. For example, if an orders update occurs and then between the order update finishing and the asset update starting, you create a sell order. All the items in the sell order will be listed as missing (this has actually happened to me). There are also a couple of other situations where this 'not lost' reason would be useful.
If anyone is still getting any issues with the beta, please let me know so that I can fix them before general release. In particular, the problem with lots of orders needing to be acknowleged. If any of those orders should not be there and have a creation date after 30th July, please give me a shout. --------------------------------------
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.03 13:59:00 -
[491]
Originally by: Ambo
If anyone is still getting any issues with the beta, please let me know so that I can fix them before general release. In particular, the problem with lots of orders needing to be acknowleged. If any of those orders should not be there and have a creation date after 30th July, please give me a shout.
Sorry, but yes. I'm seeing it with orders dated right up to yesterday.
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.03 14:09:00 -
[492]
Also, although I haven't been seeing any error messages within the user interface, the exception log shows this for - at first glance - every API update.
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 01:42:03 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== uh-oh, character limit...
|

Kapila Parthalan
|
Posted - 2010.08.03 14:36:00 -
[493]
Originally by: Ambo Edited by: Ambo on 03/08/2010 08:09:07 Version 1.5.1.3 is now available as a beta, just a few small changes:
- Corrected a bug that caused the 'new documentation available' message to always display after an update.
- Added a new lost asset reason of 'Not lost'. This will cause the asset to be retained in EMMA's database, on the next asset update, it will be treated as normal. This is intended to overcome situations where EMMA thinks that an item has gone missing but it's actually just somewhere else. For example, if an orders update occurs and then between the order update finishing and the asset update starting, you create a sell order. All the items in the sell order will be listed as missing (this has actually happened to me). There are also a couple of other situations where this 'not lost' reason would be useful.
If anyone is still getting any issues with the beta, please let me know so that I can fix them before general release. In particular, the problem with lots of orders needing to be acknowleged. If any of those orders should not be there and have a creation date after 30th July, please give me a shout.
EMMA can't find the new update, even when I try to manually update it through the settings menu.
I still get the missing items issue in 1.5.1.2 and am still working on it.
|

Ambo
Mortis Angelus
|
Posted - 2010.08.03 15:05:00 -
[494]
Originally by: Kapila Parthalan
EMMA can't find the new update, even when I try to manually update it through the settings menu.
I still get the missing items issue in 1.5.1.2 and am still working on it.
It's probably just a case of mirrors not updating yet. One time I had to wait almost 24 hours before my home PC would recognise that there was a new version.
Originally by: Anna Weston Also, although I haven't been seeing any error messages within the user interface, the exception log shows this for - at first glance - every API update.
Thanks for that, I never finished the diagnostics section because I couldn't think of anything useful to output but it's interesting (and worrying) that the error is still occurring.
Originally by: Anna Weston
Originally by: Ambo
If anyone is still getting any issues with the beta, please let me know so that I can fix them before general release. In particular, the problem with lots of orders needing to be acknowleged. If any of those orders should not be there and have a creation date after 30th July, please give me a shout.
Sorry, but yes. I'm seeing it with orders dated right up to yesterday.
This is almost certainly connected with the above problem. It's pretty major imo so certainly want to get it fixed before general release. I've got a few new ideas to try. --------------------------------------
|

Lost Hamster
Hamster Holding Corp
|
Posted - 2010.08.03 15:16:00 -
[495]
Ambo,
You have uploaded a wrong version as a beta to eve-files. Beta_EveMarketMonitorApp.zip is version: 1.4.2.1 same with the versionhistory.txt and summary.xml
|

Ambo
Mortis Angelus
|
Posted - 2010.08.03 17:53:00 -
[496]
Originally by: Lost Hamster Ambo,
You have uploaded a wrong version as a beta to eve-files. Beta_EveMarketMonitorApp.zip is version: 1.4.2.1 same with the versionhistory.txt and summary.xml
Ah, that would explain it. 
I'll re upload tomorrow. In the mean time, you can all point your updaters towards starfreeze instead if you're impatient  --------------------------------------
|

Hexxx
Minmatar
|
Posted - 2010.08.03 19:31:00 -
[497]
Ambo,
I'll be using your convention going forward. As you know already I'm using a similar technique, but I think it's important to be consistent. To that end, anyone else using a similar technique with asset tracking should attempt to do the same.
Love the asset guide. =) Projects Blog |

Ambo
Mortis Angelus
|
Posted - 2010.08.04 07:23:00 -
[498]
Originally by: Hexxx Ambo,
I'll be using your convention going forward. As you know already I'm using a similar technique, but I think it's important to be consistent. To that end, anyone else using a similar technique with asset tracking should attempt to do the same.
Love the asset guide. =)
Thanks, if you have any suggestions for improvements, etc, then just give me a shout.
I'm currently working on grabbing the industry jobs data and then using that to improve this system for those who manufacture, do blueprint research, etc. --------------------------------------
|

Ambo
Mortis Angelus
|
Posted - 2010.08.04 12:48:00 -
[499]
1.5.1.4 is now up (add I actually uploaded the right exe this time..)
Anna, I've added some diagnostics to help track down your problem so please check your exception log after an orders update and let me know the results (either post here, in-game email or [email protected]) --------------------------------------
|

Hexxx
Minmatar
|
Posted - 2010.08.04 21:22:00 -
[500]
Originally by: Ambo 1.5.1.4 is now up (add I actually uploaded the right exe this time..)
Anna, I've added some diagnostics to help track down your problem so please check your exception log after an orders update and let me know the results (either post here, in-game email or [email protected])
I should point out that Ambo's asset tracking method provides true accounting and is the most accurate measure of profit today. Projects Blog |

Dalden V
Blue Lounge Industries
|
Posted - 2010.08.04 23:39:00 -
[501]
What would be the reccomended way to add a bond with a fixed interest rate and an optional maturiry date to the investment section? It doesn't quite fit the parameters of a corp or a bank.
|

Ambo
Mortis Angelus
|
Posted - 2010.08.05 07:17:00 -
[502]
Originally by: Dalden V What would be the reccomended way to add a bond with a fixed interest rate and an optional maturiry date to the investment section? It doesn't quite fit the parameters of a corp or a bank.
I would set it up as a corp. None of the information you enter there actually matters. (i.e. the ROI, NAV, etc) These are purely for your own information.
Once you've set the corp up buy shares using the bond value and quantity.
When you receive interest on the bond then if it is paid by the dividend system or corporate account transfer then the 'auto update dividends' button will pick it up (assuming the corp name in game exactly matches the name of the bond corp in EMMA).
If you receive interest through player donations or the corp name does not match then you'll have to add the dividends manually.
Finally, when the bond is paid off, sell the shares for the appropriate amount.
Tbh, the only real difference in eve between IPOs and bonds is terminology so just imagine the buttons and fields saying different things and it'll be fine.  --------------------------------------
|

Ambo
Mortis Angelus
|
Posted - 2010.08.05 08:10:00 -
[503]
1.5.1.5 Beta is now up.
This contains a fix for the issue that causes corporate orders to keep asking for acknowledgement
Big thanks to Lost Hamster for tracking this bug down for me.
- Version 1.5.1.0 included a change to store corporate orders and assets by the corporation ID rather than the character ID of the character that had been used to retreive the data from the API. Unfortunatley, a bug slipped in that caused an order's owner to be set to the character ID when it was acknowledged. This has now been fixed.
--------------------------------------
|

Kapila Parthalan
|
Posted - 2010.08.05 11:16:00 -
[504]
EMMA still hasn't been able to find any updates, even though I've tried a few times since you put up 1.5.1.4, and I also tried deleting eve-files from the update servers list. My current version is 1.5.1.2.
|

Lost Hamster
Hamster Holding Corp
|
Posted - 2010.08.05 11:35:00 -
[505]
Edited by: Lost Hamster on 05/08/2010 11:35:33
Originally by: Kapila Parthalan EMMA still hasn't been able to find any updates, even though I've tried a few times since you put up 1.5.1.4, and I also tried deleting eve-files from the update servers list. My current version is 1.5.1.2.
Worst case, you can try to update EMMA manually. Download the following files: http://dl.eve-files.com/media/corp/Ambo/Beta_VersionHistory.zip http://dl.eve-files.com/media/corp/Ambo/Beta_summary.zip http://dl.eve-files.com/media/corp/Ambo/Beta_EveMarketMonitorApp.zip
Extract them, and then rename them in the following way: Beta_VersionHistory --> VersionHistory.txt Beta_summary --> summary.xml Beta_EveMarketMonitorApp --> EveMarketMonitorApp.exe
After it, overwrite your original files. That should do the update.
|

Dalden V
Blue Lounge Industries
|
Posted - 2010.08.05 11:50:00 -
[506]
Originally by: Lost Hamster
Worst case, you can try to update EMMA manually. Download the following files: http://dl.eve-files.com/media/corp/Ambo/Beta_VersionHistory.zip http://dl.eve-files.com/media/corp/Ambo/Beta_summary.zip http://dl.eve-files.com/media/corp/Ambo/Beta_EveMarketMonitorApp.zip
Extract them, and then rename them in the following way: Beta_VersionHistory --> VersionHistory.txt Beta_summary --> summary.xml Beta_EveMarketMonitorApp --> EveMarketMonitorApp.exe
After it, overwrite your original files. That should do the update.
I just tried this on my version of EMMA (1.5.1.0 which also finds no updates using AutoUpdater), but after launching EMMA I get an error popup:
Problem loading EMMA: An error occurred while getting new row from user defined Table Valued Function: System.formatException: Input string was not in a correct format. System.FormatException: at System.Number.StringToNumber ... EveMarketMonitorApp.DatabaseClasses.ListSplit.IntlistFillRow(Object row, Int32& n)
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.05 12:16:00 -
[507]
Hmm.
I tried auto-updating EMMA and it didn't find any new beta updates.
I tried downloading the August 5th update files from EVE Files but Windows doesn't think they're valid zip files. Had this upload gotten corrupted maybe?
|

Ambo
Mortis Angelus
|
Posted - 2010.08.05 15:15:00 -
[508]
Originally by: Dalden V
Originally by: Lost Hamster
Worst case, you can try to update EMMA manually. Download the following files: http://dl.eve-files.com/media/corp/Ambo/Beta_VersionHistory.zip http://dl.eve-files.com/media/corp/Ambo/Beta_summary.zip http://dl.eve-files.com/media/corp/Ambo/Beta_EveMarketMonitorApp.zip
Extract them, and then rename them in the following way: Beta_VersionHistory --> VersionHistory.txt Beta_summary --> summary.xml Beta_EveMarketMonitorApp --> EveMarketMonitorApp.exe
After it, overwrite your original files. That should do the update.
I just tried this on my version of EMMA (1.5.1.0 which also finds no updates using AutoUpdater), but after launching EMMA I get an error popup:
Problem loading EMMA: An error occurred while getting new row from user defined Table Valued Function: System.formatException: Input string was not in a correct format. System.FormatException: at System.Number.StringToNumber ... EveMarketMonitorApp.DatabaseClasses.ListSplit.IntlistFillRow(Object row, Int32& n)
I'd be very surprised if that worked as the zip files are not 'real' zip files and cannot be decompressed without EMMA's decompression logic.
Originally by: Anna Weston Hmm.
I tried auto-updating EMMA and it didn't find any new beta updates.
I tried downloading the August 5th update files from EVE Files but Windows doesn't think they're valid zip files. Had this upload gotten corrupted maybe?
As above, windows will not actually see them as valid zip files so this is correct behaviour.
My version of EMMA is picking these updates up without any issue so not sure what's going on here... will have to investigate further. --------------------------------------
|

Dalden V
Blue Lounge Industries
|
Posted - 2010.08.05 15:45:00 -
[509]
Originally by: Ambo
I'd be very surprised if that worked as the zip files are not 'real' zip files and cannot be decompressed without EMMA's decompression logic.
I used WinRar and it had no problem unpacking the files, I had to rename though because they had no extensions.
|

Lost Hamster
Hamster Holding Corp
|
Posted - 2010.08.05 16:04:00 -
[510]
Originally by: Ambo
I'd be very surprised if that worked as the zip files are not 'real' zip files and cannot be decompressed without EMMA's decompression logic.
However that's how it works. It's a standard zip format. I usually use total commander to uncompress it.
And I use the above way to update my EMMA, as I managed to kill the autoupdate feature in my config file. 
|
| |
|
| Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 [17] 18 19 20 30 .. 30 :: one page |
| First page | Previous page | Next page | Last page |