Vitalik Gordon
Vitalik Gordon
@aksperiod Yeah, that makes sense, as I thought you were using it with Node. Currently I don't think it's possible to have objects expandable in browser's console, as internally in...
@drmikecrowe Thanks for looking into ololog. To be honest, I don't have any far-reaching plans with this particular project. But I am certainly open to any suggestions/contributions!
@ourarash Have you looked into this: https://github.com/xpl/ololog#adding-custom-helper-methods ? Try that code: ```javascript log = require ('ololog') .configure (/* YOUR CONFIG HERE */) .methods ({ severity (n) { return this.configure ({...
Thanks for the report, I'll check that.
There was indeed a trouble when linking Ololog as a `script` tag from another website — stack entries going to that script were not handled correctly. I fixed that. But...
I'm not sure yet what exactly is happening, but as a quick workaround you can try disabling location tags, so it won't try to fetch the page source: ```js log...
Could you provide a reproducible example as a github repo (I'm too lazy to configure rollup)?
Could you please check if the issue is gone with the latest published version of Ololog?
Thank you for the repro, I'll look into it in the coming days.
What's interesting is that after finetuning it seems to be still working with FIM, so finetuning made not the model "forget" the FIM at least completely :)