[Scilab-users] Atoms login
Samuel Gougeon
sgougeon at free.fr
Thu Jan 4 01:54:20 CET 2018
Hello,
After this fix https://codereview.scilab.org/#/c/19273/ and up to the
break of ATOMS at the end of July 2017, the whole ATOMS system on both
server and client GUI sides behaved exactly as expected (for the first
time since ATOMS exists): any online modification of a module on the
server was immediately visible in the ATOMS GUI (after updating it).
But indeed, this normal behavior was of short duration: During the short
access periods to ATOMS without LDAP or other logging issues, it is no
longer working.
The issue is clearly on the server side: The file listing all modules
available for the querying Scilab client and exported by the server is
no longer updated. For instance, for Win64,
http://atoms.scilab.org/6.0/TOOLBOXES/64/windows.gz unzipped and text
edited does not include IPCV 1.2, nor plotplots 1.0 created yesterday
with binaries also available for Scilab 6.0.
Regards
Samuel
Le 29/12/2017 à 13:47, Tan Chin Luh a écrit :
> Hi,
>
> I am facing the similar issue with Scilab IPCV 1.2
> (https://atoms.scilab.org/toolboxes/IPCV/1.2), after uploading the
> module with binaries for quite some times, the atomsGUI still showing
> the older version, which is 1.1, and atomsInstall will then install
> the old version as well. atomsSystemUpdate() does not help as well.
>
> Any advice on what extra steps to make the updates available ?
>
> Thanks.
>
> Regards,
> Chin Luh
>
> On 18/11/2017 12:35 AM, Grzegorz Skiba wrote:
>> Dear Simon,
>>
>> it seems that there is still some problem with ATOMS, after uploading
>> new version of MicroDAQ toolbox isn't isn't visible in Module manage
>> in Scilab - the uploaded 1.2 version and previous versions are not
>> available.
>>
>> The 1.2v can be accessed via web:
>>
>> https://atoms.scilab.org/toolboxes/microdaq/1.2.0
>>
>> but it is not possible to install it from Scilab with
>> atomsInstall("microdaq");
>>
>> The toolbox should be available immediately or server needs to do
>> some indexing etc and will be available later?
>>
>> Regards Grzegorz
>>
>> 2017-11-17 11:22 GMT+01:00 <simon.marchetto at scilab-enterprises.com
>> <mailto:simon.marchetto at scilab-enterprises.com>>:
>>
>> Hello,
>>
>> The login issue has been fixed. There were two problems with LDAP
>> configuration (due to migration), and session management.
>>
>> There is still a problem about email sending, probably due to a
>> bad configuration on the new server, we are working on it.
>> But it does not prevent toolbox or file (fileexchange) updates.
>>
>> Sorry for the delay.
>>
>> Simon Marchetto
>>
>> Le 2017-11-14 20:53, Samuel Gougeon a écrit :
>>
>> Hello,
>>
>> Le 26/09/2017 à 22:49, Samuel Gougeon a écrit :
>>
>> Le 25/09/2017 à 23:07, Shamika Mohanan a écrit :
>>
>> Hello,
>>
>> Is anyone having trouble logging into their ATOMS
>> account? I'm
>> unable to log in or create a new account.
>>
>>
>> Neither are we. Please have a look at
>>
>> http://mailinglists.scilab.org/Scilab-users-Cannot-access-module-at-atom-scilab-tt4036831.html
>> <http://mailinglists.scilab.org/Scilab-users-Cannot-access-module-at-atom-scilab-tt4036831.html>
>>
>> [1]
>>
>>
>> There are some slight changes on this side, despite it is still
>> impossible to update existing modules and filesets and to
>> create new
>> ones:
>> When login, we no longer get neither a blank page without
>> actually
>> being logged, nor -- more recently -- getting any red
>> messages about
>> internal errors (likely addressed to debuggers).
>>
>> But there is now a kind of status inversion:
>> Let's logging. Then, we are directed back to the ATOMS
>> portal with
>>
>> displayed on the top right corner, and still without any admin
>> rights. The strange thing is that
>> when we then click on "create an account" while we have
>> already one
>> and we just tried to logging,
>> we get on the top right corner
>>
>> So, we have been actually acknowledged by the loggin process!
>> Unfortunately, clicking on Preferences does not lead to the
>> dedicated personal page.
>> No actual page uses the user profile and the SESSION_ID.
>>
>> This stands also after having removed all old cookies, that
>> could
>> prevent a sane ATOMS session after the migration of the ATOMS
>> server.
>>
>> Regards
>> Samuel Gougeon
>>
>>
>>
>> Links:
>> ------
>> [1]
>> http://mailinglists.scilab.org/Scilab-users-Cannot-access-module-at-atom-scilab-tt4036831.html
>> <http://mailinglists.scilab.org/Scilab-users-Cannot-access-module-at-atom-scilab-tt4036831.html>
>>
>> _______________________________________________
>> users mailing list
>> users at lists.scilab.org <mailto:users at lists.scilab.org>
>> http://lists.scilab.org/mailman/listinfo/users
>> <http://lists.scilab.org/mailman/listinfo/users>
>>
>> _______________________________________________
>> users mailing list
>> users at lists.scilab.org <mailto:users at lists.scilab.org>
>> http://lists.scilab.org/mailman/listinfo/users
>> <http://lists.scilab.org/mailman/listinfo/users>
>>
>>
>>
>>
>> _______________________________________________
>> users mailing list
>> users at lists.scilab.org
>> http://lists.scilab.org/mailman/listinfo/users
>
>
>
>
> _______________________________________________
> users mailing list
> users at lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20180104/ab520b16/attachment.htm>
More information about the users
mailing list