blank page when running #4
Comments
|
Hiya, thanks very much, you're quite right, the codebase hadn't been updated in quite a while. I've now bumped everything to point to the right package name and also fixed a minor issue (which means that this now requires volatility3 version 2.5.2, which is currently still only in the development branch). I've tested this and doesn't just provide a white page. If you're still running into the issue, please feel free to reopen it and we can start debugging from there... 5:) |
|
@ikelos still a blank page sadly, I do not see errors in the console |
|
Did you make sure to follow the installation guide and install the web components using npm? If they're installed then you should be served something? Otherwise you will be returned a blank page because the tool hasn't been installed correctly... |
|
@ikelos yeah... |
|
Ok, could you please attach the output of the server after you start it and make a request, and then we can compare it to a working version and see where they deviate. You might also want to see if your browser console lists an issue... |
|
Devconsole seems okay. here is the output https://pastebin.com/Ss3wNSb6 |
|
Ok, so then if you can go to the web tools and look at the Elements, volumetric-shell should have a #shadow-root object underneath it, and when you mouse over it, it should show you the size/height of the element on the page. You web log shows that the web components are getting pulled down, and if your web console is empty it suggests no errors, so I'm at a bit of a loss. You could check the network tab and make sure all the requests are succeeding? |
|
I got 1536x8 from hovering the |
|
Ok, so you do get a |
|
oh u meant the |
|
|
|
Ok, then something's up with web components (although it did seem to try grabbing most of them?). Do you have javascript disabled or any other unusual settings? Could you try it in another browser and/or a private browsing window to see if there's something interfering with it? |
|
I tried different browsers, incognito, etc already. |
|
I'm afraid this is sounding more and more like a problem specific to the setup? Do you have any other machines, or a virtual machine, you could configure to try it out? The pages seem to be transferred correctly, but aren't being interpreted by your browser as web components, but web components have been standardized for years... |
Hello, tried to make it work and after I have done all of the steps I result in a blank page, the node_modules directory did appear under volumetric-master and also under resources, the get requests seems okay but nothing happens.
also volumetric calls for package named volatility while its named volatility3 which causes a lot of issues...
The text was updated successfully, but these errors were encountered: