the Bitshares network is so bad in the past several days, always cost several mins to open a page!check how many accounts exist in your wallet.
what cause this? API servers are degraded? GUI bugs?
the Bitshares network is so bad in the past several days, always cost several mins to open a page!check how many accounts exist in your wallet.
what cause this? API servers are degraded? GUI bugs?
if there are many strange account, it's a bug of GUI which I have met several days ago, it consider any accounts with the same address as your account, and subscribe too many data from api server.
Which version client are you guys using?I have tried almost 10 different "stable" versions recently published,
Bug reports can go here:Which version client are you guys using?I have tried almost 10 different "stable" versions recently published,
but almost no one can be used in fact
I wonder who are the manage of the GUI development worker, too bad.
no thanks.Bug reports can go here:Which version client are you guys using?I have tried almost 10 different "stable" versions recently published,
but almost no one can be used in fact
I wonder who are the manage of the GUI development worker, too bad.
https://github.com/bitshares/bitshares-ui/issues/
no thanks.Bug reports can go here:Which version client are you guys using?I have tried almost 10 different "stable" versions recently published,
but almost no one can be used in fact
I wonder who are the manage of the GUI development worker, too bad.
https://github.com/bitshares/bitshares-ui/issues/
I thought we should pay for a professional worker.
I wonder who can tell me which version is really usable.
can you tell me which stable version do you use?no thanks.Bug reports can go here:Which version client are you guys using?I have tried almost 10 different "stable" versions recently published,
but almost no one can be used in fact
I wonder who are the manage of the GUI development worker, too bad.
https://github.com/bitshares/bitshares-ui/issues/
I thought we should pay for a professional worker.
I wonder who can tell me which version is really usable.
you can either keep dissing the worker or help make it better, your call
If you don't provide details/bug report it can't be fixed
(fwiw, mine runs with 15 different accounts loaded and appears to work fine)
There are 2 possible reasons for your problem:
a) There was a change recently on the subscription behaviour of bitshares-core. Copying from teh release notes:
"Operators of API nodes that service client software that expect to receive updates about all data on the blockchain by default (such as BitShares Reference Wallet before 180401), as opposed to narrowly subscribed data, should ensure that their API nodes are configured with the enable-subscribe-to-all set to true due to Pull Request 1049."
So maybe you're connecting to an API node with the subscribe-to-all setting set to true
or
b) This issue recently brought up by abit: https://github.com/bitshares/bitshares-core/issues/1472
Interestingly, neither of those is a UI issue but core API issues identified and fixed (for (a)...application depends on node operator) or in the process of being fixed (for (b))
So please don't spread false accusations.
can you tell me which stable version do you use?no thanks.Bug reports can go here:Which version client are you guys using?I have tried almost 10 different "stable" versions recently published,
but almost no one can be used in fact
I wonder who are the manage of the GUI development worker, too bad.
https://github.com/bitshares/bitshares-ui/issues/
I thought we should pay for a professional worker.
I wonder who can tell me which version is really usable.
you can either keep dissing the worker or help make it better, your call
If you don't provide details/bug report it can't be fixed
(fwiw, mine runs with 15 different accounts loaded and appears to work fine)
There are 2 possible reasons for your problem:
a) There was a change recently on the subscription behaviour of bitshares-core. Copying from teh release notes:
"Operators of API nodes that service client software that expect to receive updates about all data on the blockchain by default (such as BitShares Reference Wallet before 180401), as opposed to narrowly subscribed data, should ensure that their API nodes are configured with the enable-subscribe-to-all set to true due to Pull Request 1049."
So maybe you're connecting to an API node with the subscribe-to-all setting set to true
or
b) This issue recently brought up by abit: https://github.com/bitshares/bitshares-core/issues/1472
Interestingly, neither of those is a UI issue but core API issues identified and fixed (for (a)...application depends on node operator) or in the process of being fixed (for (b))
So please don't spread false accusations.
when I met a problem, I try to change another version, almost every stable version has different problems after I try less than several minutes.
I think there are no need to report bug for such unstable software, they need to test themself, it's a job with payment, not a hobit job.
for the issue brought by abit, it's also the GUI's job of course, they used a wrong design, used a wrong api.
when I tell the wallet that my account is alt, it just need to subscribe infomation about alt, I never told it to subscribe other account with the same key.
eventually, it even bring those junk account to my default list of transfer function. such stupid.
can you tell me which stable version do you use?no thanks.Bug reports can go here:Which version client are you guys using?I have tried almost 10 different "stable" versions recently published,
but almost no one can be used in fact
I wonder who are the manage of the GUI development worker, too bad.
https://github.com/bitshares/bitshares-ui/issues/
I thought we should pay for a professional worker.
I wonder who can tell me which version is really usable.
you can either keep dissing the worker or help make it better, your call
If you don't provide details/bug report it can't be fixed
(fwiw, mine runs with 15 different accounts loaded and appears to work fine)
There are 2 possible reasons for your problem:
a) There was a change recently on the subscription behaviour of bitshares-core. Copying from teh release notes:
"Operators of API nodes that service client software that expect to receive updates about all data on the blockchain by default (such as BitShares Reference Wallet before 180401), as opposed to narrowly subscribed data, should ensure that their API nodes are configured with the enable-subscribe-to-all set to true due to Pull Request 1049."
So maybe you're connecting to an API node with the subscribe-to-all setting set to true
or
b) This issue recently brought up by abit: https://github.com/bitshares/bitshares-core/issues/1472
Interestingly, neither of those is a UI issue but core API issues identified and fixed (for (a)...application depends on node operator) or in the process of being fixed (for (b))
So please don't spread false accusations.
when I met a problem, I try to change another version, almost every stable version has different problems after I try less than several minutes.
I think there are no need to report bug for such unstable software, they need to test themself, it's a job with payment, not a hobit job.
for the issue brought by abit, it's also the GUI's job of course, they used a wrong design, used a wrong api.
when I tell the wallet that my account is alt, it just need to subscribe infomation about alt, I never told it to subscribe other account with the same key.
eventually, it even bring those junk account to my default list of transfer function. such stupid.
Which version client are you guys using?
Which version client are you guys using?
2.0.181010
Which version client are you guys using?
2.0.181010
Please, can you try latest 2.0.181212-rc1 ?
can you tell me which stable version do you use?
when I met a problem, I try to change another version, almost every stable version has different problems after I try less than several minutes.
I think there are no need to report bug for such unstable software, they need to test themself, it's a job with payment, not a hobit job.
for the issue brought by abit, it's also the GUI's job of course, they used a wrong design, used a wrong api.
when I tell the wallet that my account is alt, it just need to subscribe infomation about alt, I never told it to subscribe other account with the same key.
eventually, it even bring those junk account to my default list of transfer function. such stupid.
the team need to be responsable for the whole development process include management / design / implement / test.Rewarding testing/bug-reports is out of scope of the ui workers, avoid 'release candidate' or 'staging' releases if you're only wanting to run 'stable/usable' versions. You should most certainly be updating your UI to the latest stable whenever possible otherwise you're a target.
now all I can see is several unusable "stable" release, and seems nobody can tell me which one is the really stable/usable version.
the team need to be responsable for the whole development process include management / design / implement / test.Rewarding testing/bug-reports is out of scope of the ui workers, avoid 'release candidate' or 'staging' releases if you're only wanting to run 'stable/usable' versions. You should most certainly be updating your UI to the latest stable whenever possible otherwise you're a target.
now all I can see is several unusable "stable" release, and seems nobody can tell me which one is the really stable/usable version.
I will support the GUI worker when I saw a professional team.
I mean we can get a really usable product from the worker's job.
the team need to be responsable for the whole development process include management / design / implement / test.
now all I can see is several unusable "stable" release, and seems nobody can tell me which one is the really stable/usable version.
Don't be surprised, he will only say NO NO NO to proposals that are good for the BTSI will support the GUI worker when I saw a professional team.
I mean we can get a really usable product from the worker's job.
the team need to be responsable for the whole development process include management / design / implement / test.
now all I can see is several unusable "stable" release, and seems nobody can tell me which one is the really stable/usable version.
Just curious have you worked on the GUI? What constitutes as a professional team? What if we stopped working on it, and shut everything down? Would you like to take over and do ALL the development work? Do you think you can do better??? Would you rather help than point fingers and make a fuss, which barely does anything other than delay progress? I bet I can't convince you, but really it's as professional as it can be for a decentralized, hard working, dedicated, and knowledgeable team.
I hope you come around for Bitshares sake. Right now the worker's out, which could be very bad for the future of this platform.
I will support the GUI worker when I saw a professional team.
I mean we can get a really usable product from the worker's job.
the team need to be responsable for the whole development process include management / design / implement / test.
now all I can see is several unusable "stable" release, and seems nobody can tell me which one is the really stable/usable version.
I will support the GUI worker when I saw a professional team.
I mean we can get a really usable product from the worker's job.
the team need to be responsible for the whole development process include management/design/implement/test.
now all I can see is several unusable "stable" release and seems nobody can tell me which one is the really stable/usable version.
I will support the GUI worker when I saw a professional team.
I mean we can get a really usable product from the worker's job.
the team need to be responsible for the whole development process include management/design/implement/test.
now all I can see is several unusable "stable" release and seems nobody can tell me which one is the really stable/usable version.
We are in the middle of the design and development process. You can see the current stage on the roadmap - http://bitshares.rossul.com/
I can walk you through what's been designed so far, and answer any question if you like.
I will support the GUI worker when I saw a professional team.
I mean we can get a really usable product from the worker's job.
the team need to be responsable for the whole development process include management / design / implement / test.