Day changed to 2025-04-01
[23:18] nekoluce: good afternoon :D
[23:19] nekoluce: first of 1 april :D
[23:19] nekoluce: happy aprils fools day :D
[23:35] jfw: in honor of the occasion, we'll be migrating the channel to WhatsApp.
Day changed to 2025-04-02
[02:00] caai_: hahaha
[14:46] caai: jfw: i have received a response from the developer, which solved the problem. i missed a rather simple 3rd step; not running "gulp plugins". this step is clearly outlined in the documentation.
[14:50] caai: i overlooked it because "gulp plugins" was included in the gulpfile.js file in version 3.1, but was omitted in version 4.0. indeed, as i am sure you recall, it is the only line of code that was removed in version 4.0.
[14:51] jfw: ah, the pesky plugins. and that did come up in studying the changes
[14:51] jfw: I thought we did check the docs too, though
[14:54] caai: it wasn't necessary to run gulp plugins in the previous built, at least not after the initial built. i think that is why we overlooked it
[14:56] caai: i remember that you also concluded that it is best not to run gulp plugins on each built (only the initial built) and thus removed it from the 3.1 gulpfile.js file.
Day changed to 2025-04-12
[21:13] caai: hey jfw, running across a small hang up. i committed the last change, but then decided on better wording. i attempted to amend the commit, mistyped and created 2 more commits. therefore, i did a hard reset back to the last "real" commit.
[21:14] caai: you can see the history here: http://jfxpt.com/paste/k3xu2cmund
[21:15] caai: now, when i open the "data_management_page" all of the changes from out last work session are gone. i am not sure how that could have happened.
[21:19] caai: obviously, i need to look before i leap next time. that being said, i am fairly sure this work is salvageable .....
[21:21] caai: could please advise on how to best proceed?
[21:49] jfw: looking
[21:53] jfw: caai: if you 'git show d29966e' do you see the changes we made?
[21:56] caai: when i run 'git show d29966e', this is the output: http://jfxpt.com/paste/2mw3h6muw8
[21:56] jfw: I just loaded the page from your server and it appears to have the latest code in place. so in the worst case you could fish it back from the server as long as you don't redeploy first
[21:58] jfw: it appears that you did not "git add" the modified file so only the prior file rename operation was included in the commit
[21:58] jfw: then probably the hard reset caused that uncommitted modification to be discarded.
[21:59] jfw: if so, indeed the version on the server is your best bet.
[21:59] caai: ahhh yes, i jumped the gun and did not "git add" the modified. Tis true
[22:00] caai: great. i just connected to the server i see that it will be easy to salvage the work that was done
[22:01] caai: thank you very much
[22:01] jfw: you're welcome
Day changed to 2025-04-15
[19:56] lru: are there sources for price data that are up to 1 minute or 5 minute granularity, for say, the entire history of bitcoin?
[19:58] jfw: lru: I'd look at APIs for historical data from the individual exchanges. I'd guess there are services that have it all aggregated but not for free at that level of detail.
[20:06] lru: thanks
[20:06] lru: I did find this: https://www.kaggle.com/datasets/mczielinski/bitcoin-historical-data but they want me to sign up to download it
[23:18] nekoluce: good afternoon :D
[23:19] nekoluce: first of 1 april :D
[23:19] nekoluce: happy aprils fools day :D
[23:35] jfw: in honor of the occasion, we'll be migrating the channel to WhatsApp.
Day changed to 2025-04-02
[02:00] caai_: hahaha
[14:46] caai: jfw: i have received a response from the developer, which solved the problem. i missed a rather simple 3rd step; not running "gulp plugins". this step is clearly outlined in the documentation.
[14:50] caai: i overlooked it because "gulp plugins" was included in the gulpfile.js file in version 3.1, but was omitted in version 4.0. indeed, as i am sure you recall, it is the only line of code that was removed in version 4.0.
[14:51] jfw: ah, the pesky plugins. and that did come up in studying the changes
[14:51] jfw: I thought we did check the docs too, though
[14:54] caai: it wasn't necessary to run gulp plugins in the previous built, at least not after the initial built. i think that is why we overlooked it
[14:56] caai: i remember that you also concluded that it is best not to run gulp plugins on each built (only the initial built) and thus removed it from the 3.1 gulpfile.js file.
Day changed to 2025-04-12
[21:13] caai: hey jfw, running across a small hang up. i committed the last change, but then decided on better wording. i attempted to amend the commit, mistyped and created 2 more commits. therefore, i did a hard reset back to the last "real" commit.
[21:14] caai: you can see the history here: http://jfxpt.com/paste/k3xu2cmund
[21:15] caai: now, when i open the "data_management_page" all of the changes from out last work session are gone. i am not sure how that could have happened.
[21:19] caai: obviously, i need to look before i leap next time. that being said, i am fairly sure this work is salvageable .....
[21:21] caai: could please advise on how to best proceed?
[21:49] jfw: looking
[21:53] jfw: caai: if you 'git show d29966e' do you see the changes we made?
[21:56] caai: when i run 'git show d29966e', this is the output: http://jfxpt.com/paste/2mw3h6muw8
[21:56] jfw: I just loaded the page from your server and it appears to have the latest code in place. so in the worst case you could fish it back from the server as long as you don't redeploy first
[21:58] jfw: it appears that you did not "git add" the modified file so only the prior file rename operation was included in the commit
[21:58] jfw: then probably the hard reset caused that uncommitted modification to be discarded.
[21:59] jfw: if so, indeed the version on the server is your best bet.
[21:59] caai: ahhh yes, i jumped the gun and did not "git add" the modified. Tis true
[22:00] caai: great. i just connected to the server i see that it will be easy to salvage the work that was done
[22:01] caai: thank you very much
[22:01] jfw: you're welcome
Day changed to 2025-04-15
[19:56] lru: are there sources for price data that are up to 1 minute or 5 minute granularity, for say, the entire history of bitcoin?
[19:58] jfw: lru: I'd look at APIs for historical data from the individual exchanges. I'd guess there are services that have it all aggregated but not for free at that level of detail.
[20:06] lru: thanks
[20:06] lru: I did find this: https://www.kaggle.com/datasets/mczielinski/bitcoin-historical-data but they want me to sign up to download it