OK, good to know. would any one be willing to give a quick review?
https://gitlab.kitware.com/paraview/paraview/merge_requests/1476
On 03/20/2017 12:16 PM, Ben Boeckel wrote:
On Mon, Mar 20, 2017 at 11:31:28 -0700, Burlen Loring wrote:
I had to apply to clang-format manually. it's up there
On Mon, Mar 20, 2017 at 11:31:28 -0700, Burlen Loring wrote:
> I had to apply to clang-format manually. it's up there now. changes were
> minimal so I squashed them into the patch.
The fixes would have had to had been squashed in anyways; the robot
checks each commit individually.
> System has
Hi Cory,
I had to apply to clang-format manually. it's up there now. changes were
minimal so I squashed them into the patch. System has yet to acknowledge
and re check. I assume it will eventually.
Try as I may the clang-format script you guys are using doesn't work for
me. here are the
On Fri, Mar 17, 2017 at 12:36:10 -0700, Burlen Loring wrote:
> fyi, https://gitlab.kitware.com/paraview/paraview/merge_requests/1476
>
> it complains about clang-format, but it seems that the source file was
> not formatted in that way to begin with.
When I enabled clang-format checking, I did
Burlen,
Thanks for the patch.
With regards to clang-format, we recently enabled automatic style
enforcement checks. This way to fix is to install clang-format, run
`git clang-format` in your ParaView source directory, amend your
commit, then force push it with `git gitlab-push -f`.
- Cory
On
fyi, https://gitlab.kitware.com/paraview/paraview/merge_requests/1476
it complains about clang-format, but it seems that the source file was
not formatted in that way to begin with.
On 03/17/2017 12:11 PM, Burlen Loring wrote:
Thank you guys. I poked around this morning and found the
Thank you guys. I poked around this morning and found the following:
The "BlueObeliskElements" is the only cmap in the default presets that
triggers the issue. It has more values than can be displayed on a single
line, and this is what triggers the FPE in the logic.
Enforcing a minimum
Burlen,
I've created an issue for your report. It sure looks like a bug.
https://gitlab.kitware.com/paraview/paraview/issues/17305
Ufuk,
That fix turns out to already be in v5.3.0:
commit 90e710d5792116e640d25caa8ff455ae4e65d718
Author: Sergey Sindeev
Date: Sun Dec 18
Hi Burlen,
Your issue could be related with following,
https://software.intel.com/en-us/forums/intel-c-compiler/topic/702934
I opened a bug report in Intel form and they found a bug in that
particular source file (pqPresetToPixmap.cxx). So, if you apply the fix
you might solve the problem but i
not sure if it matters, but I had been trying to load a color map that
was saved from ParaView 5.1.0. attached.
On 03/16/2017 04:50 PM, Burlen Loring wrote:
I tried out ParaView 5.3.0 today, and I encountered the above crash.
steps to reproduce: load data (sphere source will work), set color
I tried out ParaView 5.3.0 today, and I encountered the above crash.
steps to reproduce: load data (sphere source will work), set color by
var, open color map dialog, change to categorical, open choose presets
dialog, scroll down, when you get near the bottom you will get the crash.
Program
11 matches
Mail list logo