IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Thanks Herb for finding this:-)
This was my bug, I typed it in on gd's laptop and he just run 'svn ci'
metze
(This used to be commit 3c08e29f4fdde586084bdcf1b36eaf92ae944750)
(up to 8, currently) randomly generated _and_ verify if the
change has actually been made.
surprising results when running the test (I hope it's just
a bug somewhere in it or in the libnet code).
rafal
(This used to be commit 652a291145ac18de2734266ebba843abe659b7db)
changes.
Also, some common definitions for user mod tests have been put into
a separate file.
rafal
(This used to be commit 0040c087481be68d44a0b59744be5c5e569fd8a4)
and add one requested field in to the function creating testing
set of changes for user modify routine.
rafal
(This used to be commit f6d4f356b3de03baa3d1672730195668bbfdc9c7)
which have a ulimit -n of 100. Drop the number of searches to 20.
That should limit the maximum total fd count to about 76, most of
which is all the listening sockets on the various interfaces
(This used to be commit fb5b8c4f8c1ed69e3a813befeeb2a9627e84c454)
Jerry, there is a big difference on the wire between these two:
[out] uint32 x;
and
[out] uint32 *x;
if you change from
[out] uint32 x;
then you need to change to:
[out,ref] uint32 *x;
otherwise it changes the format on the wire, which means we are no
longer compatible with MS servers.
but be aware that even if you change to a ref ptr, you also need to
change all the client code to set all the return variables in the out
part of the structure. That's why I don't like the MIDL restriction of
forcing the use of ref pointers for output variables - it makes life
much harder when writing client code, and makes the code much more
error prone (just look at all the extra code needed to make this work
again).
I know we could auto-allocate these variables in the generated client
side NDR code, but if we did that then we would have no way of doing a
_real_ ref out pointer, which we really wanted to set to some already
allocated variable.
So please hold off on changing our idl to use the MIDL convention for
output variables until Jelmer and I have had a good "chat" about this :-)
(This used to be commit 555aed43ba3c08360ca7fa921622b80732a7f657)
assigned into a static initialiser must be constant.
Wishing sweet dreams on the jet-lagged tridge :-)
Andrew Bartlett
(This used to be commit 174014d956cb1d246bd07218ea289418195a73fb)
is passed a stack pointer from values[], which is not valid when the
torture suite is run.
Jelmer, need to be careful when converting test code not to use stack
values from the torture_XXX() call in the test suite
(This used to be commit 2744a0b385f58aaf0b45f33bec0d0a16c09709d7)
jelmer: I think there're a few ref pointer related bugs in pidl
we need to discuss them the next days
metze
(This used to be commit 8c4241ecbbd9686d990073cec53dc1fde0fdde9b)
