vite issueshttps://gitlab.inria.fr/solverstack/vite/-/issues2024-02-28T11:46:52+01:00https://gitlab.inria.fr/solverstack/vite/-/issues/27GUI is broken on Wayland2024-02-28T11:46:52+01:00Philippe SWARTVAGHERGUI is broken on WaylandGUI is broken on Wayland systems. Tested with a fresh install of Debian 12 Gnome in a virtual machine:
![VirtualBox_Debian_Gnome_28_02_2024_11_43_12](/uploads/b71a12cffa8c1bfccf867744a97498d5/VirtualBox_Debian_Gnome_28_02_2024_11_43_12.p...GUI is broken on Wayland systems. Tested with a fresh install of Debian 12 Gnome in a virtual machine:
![VirtualBox_Debian_Gnome_28_02_2024_11_43_12](/uploads/b71a12cffa8c1bfccf867744a97498d5/VirtualBox_Debian_Gnome_28_02_2024_11_43_12.png)
It works fine if I launch Gnome on X11.
Tested with Vite installed from Debian repositories, Vite built from source (commit 9dcc61ffe333510fd98c1295104bb108cf13c7d3), with OpenGL and VBO, with OpenGL without VBO. Not tested with Vulkan.
Maybe it is worth testing !45 before trying to understand this bug.
Reported by @jcollin.https://gitlab.inria.fr/solverstack/vite/-/issues/26files without copyright headers2023-06-29T19:52:32+02:00Johnny Jazeixfiles without copyright headersMaybe some false positives, I did: `grep -rL "CeCILL" src/ plugins/`:
```
src/interface/viteqtreewidget.cpp
src/interface/viteqtreewidget.hpp
src/interface/qxtspanslider.cpp
src/render/vbo/Shader.hpp
src/render/vbo/Shader.cpp
src/render/...Maybe some false positives, I did: `grep -rL "CeCILL" src/ plugins/`:
```
src/interface/viteqtreewidget.cpp
src/interface/viteqtreewidget.hpp
src/interface/qxtspanslider.cpp
src/render/vbo/Shader.hpp
src/render/vbo/Shader.cpp
src/render/texture.cpp
src/render/text2D.hpp
src/render/texture.hpp
src/render/text2D.cpp
src/statistics/Statistics_window.cpp
src/statistics/Diagram.hpp
src/statistics/Diagram.cpp
src/statistics/ChartView.cpp
src/statistics/ChartView.hpp
src/trace/portable_archive_exception.hpp
src/trace/Serializer_container.hpp
src/trace/Serializer_values.hpp
src/trace/Serializer_structs.hpp
src/trace/SerializerDispatcher.cpp
src/trace/Serializer_types.hpp
src/trace/TraceBuilderThread.hpp
src/trace/Serializer.hpp
src/trace/TraceBuilderThread.cpp
src/trace/Serializer.cpp
src/trace/SerializerWriter.cpp
src/common/Palette.hpp
src/common/Palette.cpp
src/common/TraceMemory.hpp
src/parser/ParserSplitted.cpp
src/parser/ParserFactory.hpp
plugins/TraceInfos/TraceInfos.hpp
plugins/TraceInfos/TraceInfos.cpp
plugins/MatrixVisualizer/Helper.cpp
plugins/MatrixVisualizer/Windows/MatrixGLWidget.hpp
plugins/MatrixVisualizer/Windows/MatrixWindow.cpp
plugins/MatrixVisualizer/Windows/MatrixGLWidget.cpp
plugins/MatrixVisualizer/Windows/MatrixWindow.hpp
plugins/MatrixVisualizer/Common/Zoom.cpp
plugins/MatrixVisualizer/Common/Quadtree.cpp
plugins/MatrixVisualizer/Common/Zooming.hpp
plugins/MatrixVisualizer/Common/Quadtree.hpp
plugins/MatrixVisualizer/Common/Zoom.hpp
plugins/MatrixVisualizer/Common/Zooming.cpp
plugins/MatrixVisualizer/Helper.hpp
plugins/MatrixVisualizer/Formats/SymbolMatrix.cpp
plugins/MatrixVisualizer/Formats/SymbolMatrix.hpp
plugins/MatrixVisualizer/MatrixVisualizer.cpp
plugins/MatrixVisualizer/Parsers/SymbolParser.cpp
plugins/MatrixVisualizer/Parsers/SymbolParser.hpp
plugins/MatrixVisualizer/Parsers/ValuesParser.hpp
plugins/MatrixVisualizer/Parsers/ValuesParser.cpp
plugins/MatrixVisualizer/Parsers/OrderParser.cpp
plugins/MatrixVisualizer/Parsers/OrderParser.hpp
plugins/MatrixVisualizer/Parsers/Readers/Pastix.hpp
plugins/MatrixVisualizer/Parsers/Readers/Pastix.cpp
plugins/MatrixVisualizer/Parsers/Parser.hpp
plugins/MatrixVisualizer/MatrixVisualizer.hpp
plugins/Distribution/Distribution.cpp
plugins/CriticalPath/ParserStats.hpp
plugins/CriticalPath/CriticalPath.hpp
plugins/CriticalPath/ParserStats.cpp
plugins/CriticalPath/DrawStats.cpp
plugins/CriticalPath/ParseTasks.hpp
plugins/CriticalPath/ParseDAG.cpp
plugins/CriticalPath/DrawStats.hpp
plugins/CriticalPath/ParseDAG.hpp
plugins/CriticalPath/ParseTasks.cpp
```https://gitlab.inria.fr/solverstack/vite/-/issues/24OpenGL migration2023-07-08T19:43:19+02:00Johnny JazeixOpenGL migrationJust to track the migration. QGLWidget is deprecated and removed in Qt6 so it needs to be updatedJust to track the migration. QGLWidget is deprecated and removed in Qt6 so it needs to be updatedhttps://gitlab.inria.fr/solverstack/vite/-/issues/23Qt6 migration2023-07-08T19:43:19+02:00Johnny JazeixQt6 migrationJust to track the migrationJust to track the migrationhttps://gitlab.inria.fr/solverstack/vite/-/issues/21Preferences -> Settings takes a very long time to open2023-04-03T14:57:11+02:00THIBAULT Samuelsamuel.thibault@inria.frPreferences -> Settings takes a very long time to openHello,
It seems like the time that the Preferences->Settings menu takes to open depends on the size of the trace currently open. For instance, with this trace: [paje.trace](/uploads/b4b7ecd824f608c777c79c7d51e57410/paje.trace) it takes ...Hello,
It seems like the time that the Preferences->Settings menu takes to open depends on the size of the trace currently open. For instance, with this trace: [paje.trace](/uploads/b4b7ecd824f608c777c79c7d51e57410/paje.trace) it takes a few seconds, while for this trace: https://dept-info.labri.fr/~thibault/tmp/gpu.trace it takes minutes.
I have tried with git 38510db9a5a06a4fe7a154ac04fd9c738c5e8c2c (Mon Aug 8 10:11:39 2022)
Samuelhttps://gitlab.inria.fr/solverstack/vite/-/issues/19Wrong values in ruler when max displayed above 100002020-08-18T20:18:09+02:00Johnny JazeixWrong values in ruler when max displayed above 10000See attached files.
![export](/uploads/585072ffd7c7784a4dd183ae5e54915d/export.png)[per-color-state.trace](/uploads/84731c36bd4bad39234f6390e1717239/per-color-state.trace)
The ruler displays 4000 but the value is 5000.
If you zoom betwe...See attached files.
![export](/uploads/585072ffd7c7784a4dd183ae5e54915d/export.png)[per-color-state.trace](/uploads/84731c36bd4bad39234f6390e1717239/per-color-state.trace)
The ruler displays 4000 but the value is 5000.
If you zoom between 6000 and 10000+, all will be rounded to thousands (so we can have 6000, 6000, 7000, 7000 in the graduations instead of the good values).https://gitlab.inria.fr/solverstack/vite/-/issues/16Vite displays type of link in the field Value2020-10-19T23:41:20+02:00Philippe SWARTVAGHERVite displays type of link in the field ValueHello,
If I display informations about a link representing a communcation, the field **Value** contains `MPI communication` (so the same as the field **Type**). According to the definition of the Paje file, the field **Value** should co...Hello,
If I display informations about a link representing a communcation, the field **Value** contains `MPI communication` (so the same as the field **Type**). According to the definition of the Paje file, the field **Value** should contains the size of transfered data.
The same occurs if the link represents a work stealing: StarPU puts 0 as value of the link, but Vite displays `Work stealing`.
I can try to fix it, but before, confirm it's a bug, please.https://gitlab.inria.fr/solverstack/vite/-/issues/10Please support per-state Color2020-10-20T00:14:55+02:00THIBAULT Samuelsamuel.thibault@inria.frPlease support per-state ColorHello,
In some cases, I'd like to be able to set different colors for different states, but without having to define a state type for each color (because there can e.g. be a *lot* of different colors). The attached [trace.zip](/uploads/...Hello,
In some cases, I'd like to be able to set different colors for different states, but without having to define a state type for each color (because there can e.g. be a *lot* of different colors). The attached [trace.zip](/uploads/d3b0f560d0e72c5ec0335c00c84c6c92/trace.zip) would be an example: PajeSetState 22 has an additional Color field, which is used by 22 at line 537 & 538 (time 1407.695097000), which should thus make the first task show up as almost black instead of green.. Note that just like in https://gitlab.inria.fr/solverstack/vite/issues/9 , vite currently crashes like every other opening of the file, so https://gitlab.inria.fr/solverstack/vite/issues/9 probably needs to be fixed first :)
Samuelhttps://gitlab.inria.fr/solverstack/vite/-/issues/7Increase the windows size2018-01-11T16:32:45+01:00Mathieu FavergeIncrease the windows sizeWe should be able to define the matrix size to display the symbol matrix in order to increase/decrease its size.We should be able to define the matrix size to display the symbol matrix in order to increase/decrease its size.CHEVALIER ArthurCHEVALIER Arthurhttps://gitlab.inria.fr/solverstack/vite/-/issues/1"holes" in the state of a thread when zooming2017-08-31T09:12:49+02:00François Trahay"holes" in the state of a thread when zoomingWhen zooming in a trace, the transition between states is shown as a "hole".
For instance, with the attached trace, running:
$ vite -t 0.095:0.096 eztrace_output.trace
shows a hole between ~0.0955871 and ~0.0956144
[eztrace_output.trac...When zooming in a trace, the transition between states is shown as a "hole".
For instance, with the attached trace, running:
$ vite -t 0.095:0.096 eztrace_output.trace
shows a hole between ~0.0955871 and ~0.0956144
[eztrace_output.trace](/uploads/7fe17da4c0a0f5e8711bbfc3fc69103a/eztrace_output.trace)