-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dont seem to be able to configure heart rate zones down to my max HR of 168 #552
Comments
I have configured my max and min HR rate on the athlete section but this does not alter anything within the zones section. In zone 9 I can only reduce this to 205. I wish I had a max HR of 205 |
Is your problem fixed in v6.0.3 ? |
Ok let me know if your problem is fixed. Because i fixed a bug on 6.0.3 which may fix yours. You don't need to pay me ;) By the way you can change the value of the donation in the field. Tom |
Hi Tom,
Thanks I will pay you as I love it and am happy that you are out there doing your thing to make everyone else better cyclists. I use it a lot as I do many other apps.
Will I need to reload the new versions after deleting the old.
With my best regards,
Ali Marsh
…________________________________
From: Thomas Champagne <[email protected]>
Sent: Sunday, March 25, 2018 4:29:57 PM
To: thomaschampagne/stravistix
Cc: Upinthehills; Author
Subject: Re: [thomaschampagne/stravistix] Dont seem to be able to configure heart rate zones down to my max HR of 168 (#552)
Ok let me know if your problem is fixed. Because i fixed a bug on 6.0.3 which may fix yours.
You don't need to pay me ;) By the way you can change the value of the donation in the field.
Tom
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fthomaschampagne%2Fstravistix%2Fissues%2F552%23issuecomment-375974705&data=02%7C01%7C%7Ceb3516d8348c4175974408d5925ce403%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636575850007423630&sdata=LE90W5FJfOW8PNO3zl9ALUGIRH6NKzz%2Fru5Ay1SuDAU%3D&reserved=0>, or mute the thread<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAeRyxWYvEJkee78K_zY3_yGwF-BKTOUnks5th6nlgaJpZM4Sy0d4&data=02%7C01%7C%7Ceb3516d8348c4175974408d5925ce403%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636575850007423630&sdata=wgJ%2BR5B7CXHnk40L%2BkKoi5YyGQEI7zh3pKAa7Y3DiEI%3D&reserved=0>.
|
@Upinthehills You have nothing to do. Just ensure that you have at least version 6.0.3. Open strava and check that: Let me know if your problem is fixed or not. I could fix it in new version i will deploy tomorrow. Tom |
This seems to happen in LTHR at least. |
@ferrix you are experiencing same issue described in the ticket? This error means you want to sync too much data in chrome synced storage. Having to many zones could be the cause. If error still there. Then think about reset settings from avanced menu |
The zones are the defaults. |
Ok thanks. Potential link with https://github.com/thomaschampagne/stravistix/issues/568 Could you in the developer console (F12 key) enter these 3 commands and provide me results for each one: 1 chrome.storage.sync.getBytesInUse((bytesInUse) => {
let storage = {
bytesInUse,
quotaBytes: chrome.storage.sync.QUOTA_BYTES,
percentUsage: bytesInUse / chrome.storage.sync.QUOTA_BYTES * 100,
};
console.log(storage);
}); 2 chrome.storage.sync.get(null, (data) => {
function byteCount(s) {
return encodeURI(s).split(/%..|./).length - 1;
}
console.log("User zones item size saved: " + byteCount(JSON.stringify(data)) + " bytes" );
}); 3 chrome.storage.sync.get(null, (data) => { // All synsec settings !
console.log(JSON.stringify(data));
}); Thanks for your help ! |
Since the storage is limited in bytes, "f" and "t" or even [95, 100] instead of named key-vals. |
The QUOTA_BYTES_PER_ITEM for chrome synced data is 8,192 bytes And you have 9691 bytes total on your zones. As quick work around, try to reduce your the number of your zones to stay under 8,192 bytes. As a violent solution you can "reset" your settings from the advanced menu and be less greedy on zones count :) Anyway this is a problem, i have to re-think how chrome sync is managed too. I may switch this to the local storage and next provide a dedicated online sync solution (without quota per item limit). Thanks ! |
The fact that you don't need a backend to sync is quite practical. What we lose in the process is copying sessions between browsers and the rather opinionated large number of zones in all dimensions or whatever the defaults are nowadays but I don't remember setting that to 15ish myself. That in turn leads (in my case) to going with the defaults for most settings since there is not a very practical way to sync between instances of stravistix. More accurately that is not anywhere front and center for me to do. I would argue that storing the settings in a denser "digest" format would help in transfering the configuration between my instances. Let's say there was a 32-byte arbitrary-looking string that I could pass into a new browser and get the rest of the data from Strava. Alternatively, this could be piggybacked into a Strava field (yes, fragile). By now, this is not the same issue but a brand new design to fix a completely different feature. Thanks and sorry :D |
So you no longer have QUOTA exceeded error and can add your LTHR? |
Yes.
…On Sat, 7 Apr 2018 at 17:03 Thomas Champagne ***@***.***> wrote:
So you no longer have QUOTA exceeded error and can add your LTHR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/thomaschampagne/stravistix/issues/552#issuecomment-379484210>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACIrJs_9GG5GBpDA1cbds0wy6QQ0KHqks5tmPFygaJpZM4Sy0d4>
.
|
Step 1: Are you in the right place?
Step 2: Describe your environment
Step 3: Describe the problem:
Steps to reproduce:
Actual Behavior:
Expected Behavior:
Media attachement:
Providing your stravistix synced athlete history can be usefull to solve the problem
The text was updated successfully, but these errors were encountered: