1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Phoebus lock down BOB |
From: | Stainer Tom via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Mon, 29 Mar 2021 07:31:45 +0000 |
>>> From now on you can start phoebus with
the >> > -layout /path/to/Example.memento > I can confirm that it will print that warning because unfortunately that part of the code isn't currently aware of some other part actually handling the
option. > So when I try that now, it "works" but there is that warning which should be removed. > And there's no warning when /path/to/example.memento is simply not valid, i.e. no such file. > So bottom line the error handling is terrible, but fundamentally it works when you have a current version of phoebus. > -Kay Thanks Kay for the advice, however I am still having issues. After pulling master (including the merged pull request) I no longer get the two warning messages from before, so that’s good!
But it still opens CSS in the same way as opening the BOB file – I can edit the OPI and from the user point of view it is still Phoebus not a single page application
that is locked down. Again, I ran it via the same command. Is it just my system?
My system is: ·
Fedora 33 (5.10.19-200.fc33.x86_64 #1 SMP Fri Feb 26 16:21:30 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux) ·
openjdk 15.0.2 2021-01-19 ·
OpenJDK Runtime Environment 20.9 (build 15.0.2+7) ·
OpenJDK 64-Bit Server VM 20.9 (build 15.0.2+7, mixed mode, sharing) ·
Phoebus master (commit 70b9a4c3a7feefc7cf86c97f328c443af8468fc5) Kind regards, Tom |