Re: [sage-devel] Re: SageNB and ldap packages

[Jori Mäntysalo]

On Sat, 9 Dec 2017, kcrisman wrote:


  >       After some trying I ended up with line
  >
  >       from ldap.functions import strf_secs

Hmm, what was your previous Sage instance?


Version 8.0.


Did you conceivably compile Sage using Py3?


Just did normal make.

Dima wrote:

It's probably coming from one of (non-standard ?) python packages you 
have installed.


True, I installed some optional packages (gap_database, dot2tex etc.). But 
I don't get that -- how those affect login on SageNB?


--
Jori Mäntysalo

[sage-devel] Re: Another build error

[Travis Scrimshaw]

> > IMO, a better practice is to merge in old branches to a branch based off 
> > develop. If you want to rebase, then run rebase. That way you never have 
> > old cruft and have to watch Sage do a massive rebuild of things with 
> only 
> > changed timestamps. For example 
> > 
> > $ git checkout -b branch_name develop 
> > $ git merge branch_name 
> > $ git rebase develop 
>
> I am not sure if I understand that procedure correctly. Where does the 
> old branch comes into play? Should the second line perhaps be 
>   $ git merge old_branch 
> ? 
>
> Why would you rebase if old_branch merges cleanly into develop? 
>
> And even if you abstain from rebasing: Assume you have local_old_branch 
> that is identical with remote_old_branch in the branch field of Trac 
> ticket 
> 12345. The purpose is to somehow merge it with the latest develop, and 
> according to your suggestion one does 
>  $ git checkout -b new_branch_name develop 
>  $ git merge local_old_branch 
> and then push new_branch_name to #12345. Would that mean to force-push? Or 
> would a normal push suffice? 
>
>
Personally, I never rebase on published branches because that overwrites 
history (although I will do this on my personal branches before I push 
them). However, if you do

$ git fetch trac old_branch:local_branch_name
$ git checkout local_branch_name
$ git merge develop

you reset everything to the version that old_branch was at, so all of the 
timestamps get updates, and then the merge resets them again to the state 
of develop. So as far as make knows, you have just changed everything.

Now if you follow the procedure with no rebasing, then you can do a normal 
push and the branch just picks up a merge commit.

I also never have branches that are not based on develop. I make it a point 
to update all of my local branches in order to avoid accidentally switching 
versions.

Best,
Travis

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error Installing Sage 8.0 (gcc-7.2.0 won't install)

[Dima Pasechnik]

What is the Xcode version you are using?
You do have its command line tools installed, too, right?
It worked for me (and other people) on 8.1.rc*...

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Update on Boolean-Cayley-graphs

[Paul Leopardi]

Hi all,
I have just finished attending the 5th International Conference on 
Combinatorics, where I spoke about my Sage computations with Cayley graphs 
of bent functions, and the new inclusion of SQL database support for this 
project. For background info, see "Classifying bent functions" below. The 
accompanying paper on arXiv is out of date, and still needs to be 
completed, and the Sage and Python code still needs work, especially 
doctests. Any advice or help on how to proceed at this point is welcome. I 
am especially looking for advice on long-term publicly accessible hosting 
of large (TB size) relational databases, as well as advice on how to 
incorporate parts of my work into Sage proper.
All the best, Paul

   - Classifying bent functions 
   , 
   University of Melbourne, 2017.
   - Yet another database of strongly regular graphs 
   , 
   5ICC , Monash University, 2017. 
   (Highlights, other than the prototype databases, include a proof that 
   two of the 10 published Extended Affine classes of bent functions of degree 
   3 in 8 dimensions are actually the same class, and evidence that 8 of the 
   256 bent functions that define the 8 S-boxes of CAST-128 have more symmetry 
   than the other 248 functions do.)
   - Paul Leopardi, "Classifying  
   bent 
   functions by their Cayley graphs".
   
   Preprint: 
   
arXiv:1705.04507
 
   [math.CO] , updated July 2017.
   
   Explores the connections between bent functions and their Cayley graphs, 
   as well as projective two-weight linear codes, and symmetric designs with 
   the symmetric difference property, through various equivalence classes. 
   Includes exhaustive classifications of bent functions up to 8 dimensions 
   and degree 3, with selected examples of degree 4.
   
SageMath code: Boolean-Cayley-graphs: Investigations of Boolean functions, 
their Cayley graphs, and associated structures.

   - CoCalc: public folder of worksheets, source code and data files 
   

   .
   - GitHub: Git repository of source code, data and papers. 
   
   - SourceForge: Documentation of Python modules in HTML format. 
   

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error Installing Sage 8.0 (gcc-7.2.0 won't install)

[Michael Frey]

On Sunday, November 19, 2017 at 11:27:43 AM UTC-5, M Mills wrote:
>
> Thanks.
>
> On Sunday, November 19, 2017 at 4:34:30 AM UTC-6, Dima Pasechnik wrote:
>>
>> 8.0 will not work with the current Xcode.
>> You would need 8.1.rc2 (or wait for 8.1 to be done, probably very soon).
>>
>
This is still a problem with the 8.1 release of 12/07/2017.  Does anyone 
have a workaround? 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Why doesn't #23931 get merged?

[William Stein]

On Sat, Dec 9, 2017 at 5:41 AM Volker Braun  wrote:

> First of all, what sets us apart from most open source projects is that
> the time required for a CI (buildbot) run is about a day. And we produce
> more more tickets than one per day. So unless we massively throw hardware
> at this, we have to collect a couple of tickets for each buildbot run and
> then backtrack if there is a failure.
>

I can help with that...

Email me off list.  I just got a brand new grant-funded machine at UW...


> The biggest flaw of the current process is IMHO that not enough things are
> automatized; Most build failures are actually trivial (like documentation
> doesn't build) and should be caught without human interaction before doing
> a full buildbot run. The problem is that our tests are too flaky to be 100%
> reliable. For example #23391 often causes at least one buildbot to crap
> out. And patchbots often produce spurious errors, which leads to people
> ignoring their output. In part this is because we don't have a lot of
> incentive to hunt down rare failures, most people just want their ticket
> merged and don't run tests 100x. Another sign of things not being automated
> is that tarball updates require human (i.e. my) intervention to upload
> them. And as long as they aren't uploaded they can't be tested.
>
> To address these issues, I/we should:
>
> 1) address the tarball issue, either add a download url to, say,
> checksums.ini and code to auto-download from that url if it can't be found
> on the mirrors. Or set up a web service where tarball updates must be
> submitted to be accessible by build/patchbots (any volunteers for hardware
> / hosting?)
>
> 2) work towards a release script that automatically merges or sets back to
> "needs review" based on tests on a fast machine; This will also increase
> the visibility and pain of random testsuite failures...
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
-- William Stein

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Another build error

[Emmanuel Charpentier]

I have the same problem :

charpent@p-202-021:/usr/local/sage-8$ git status
Sur la branche 8_1_R_343
Fichiers non suivis:
  (utilisez "git add ..." pour inclure dans ce qui sera validé)

src/sage/libs/cypari2/

aucune modification ajoutée à la validation mais des fichiers non suivis 
sont présents (utilisez "git add" pour les suivre)
charpent@p-202-021:/usr/local/sage-8$ git status src/sage/libs/cypari2/
Sur la branche 8_1_R_343
Fichiers non suivis:
  (utilisez "git add ..." pour inclure dans ce qui sera validé)

src/sage/libs/cypari2/auto_gen.pxi
src/sage/libs/cypari2/auto_instance.pxi

aucune modification ajoutée à la validation mais des fichiers non suivis 
sont présents (utilisez "git add" pour les suivre)
charpent@p-202-021:/usr/local/sage-8$ ls -lR src/sage/libs/cypari2
src/sage/libs/cypari2:
total 908
-rw-r--r-- 1 charpent charpent 860368 avril 25  2017 auto_gen.pxi
-rw-r--r-- 1 charpent charpent  57753 avril 25  2017 auto_instance.pxi
drwxr-xr-x 2 charpent charpent   4096 avril  1  2017 __pycache__

src/sage/libs/cypari2/__pycache__:
total 4
-rw-r--r-- 1 charpent charpent 247 avril  1  2017 __init__.cpython-35.pyc

This is my workhorse branch, updated often. Since I have had a lot of 
upfddates since april, it seems to be dead wood. I tend to think  that I 
can "rm -Rf /usr/sage/libs/cypary2" without ill effects.

What do you think ?

--
Emmanuel Charpentier

Le jeudi 7 décembre 2017 23:19:51 UTC+1, François Bissey a écrit :
>
>
>
> > On 8/12/2017, at 11:12, Simon King  
> wrote: 
> > 
> > On 2017-12-07, Simon King  wrote: 
> >> Hi! 
> >> 
> >> Building Sage again, I get the error 
> >>  InternalError: Internal compiler error: 'cysignals/signals.pxi' not 
> >>  found 
> >> 
> >> Unfortunately, the error did not go away after "make distclean". 
> >> 
> >> What can I do? The error occurs on some local branch (different from 
> >> develop), however I didn't touch cysignals. 
> > 
> > Strangely, git status mentions 
> >src/sage/libs/cypari2/ 
> > which my local branch is *not* touching. So, what's happening? 
> > 
>
> Anything in that folder? That folder has been removed when cypari2 has 
> been 
> made a separate package. git sometimes don’t remove folders that have been 
> removed. What is the exact git status for that folder? 
>
> François 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: SageNB and ldap packages

[Dima Pasechnik]

On Saturday, December 9, 2017 at 6:10:53 AM UTC, Jori Mäntysalo wrote:
>
> On Fri, 8 Dec 2017, Dima Pasechnik wrote: 
>
> >   How to set up SageNB with LDAP to SageMath 8.1? 
> > 
> >   After some trying I ended up with line 
> > 
> >   from ldap.functions import strf_secs 
> > 
> > 
> > I've no idea where this comes from, it's not in the current sagenb code, 
> > as far as I can tell. 
> > (I didn't try looking too hard, but ldap.functions seems to be something 
> Python 3-only...) 
>
> As always, I started by downloading the stable version and compiled from 
> scratch. So it should be there, or otherwise there are ghosts in the 
> server. 
>

It's probably coming from one of (non-standard ?) python packages you have 
installed.
Note that I don't have strf_secs anywhere in my Sage 8.1 local/ directory
while I do have sagenb installed.


> -- 
> Jori Mäntysalo

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Why doesn't #23931 get merged?

[Volker Braun]

First of all, what sets us apart from most open source projects is that the 
time required for a CI (buildbot) run is about a day. And we produce more 
more tickets than one per day. So unless we massively throw hardware at 
this, we have to collect a couple of tickets for each buildbot run and then 
backtrack if there is a failure.

The biggest flaw of the current process is IMHO that not enough things are 
automatized; Most build failures are actually trivial (like documentation 
doesn't build) and should be caught without human interaction before doing 
a full buildbot run. The problem is that our tests are too flaky to be 100% 
reliable. For example #23391 often causes at least one buildbot to crap 
out. And patchbots often produce spurious errors, which leads to people 
ignoring their output. In part this is because we don't have a lot of 
incentive to hunt down rare failures, most people just want their ticket 
merged and don't run tests 100x. Another sign of things not being automated 
is that tarball updates require human (i.e. my) intervention to upload 
them. And as long as they aren't uploaded they can't be tested.

To address these issues, I/we should:

1) address the tarball issue, either add a download url to, say, 
checksums.ini and code to auto-download from that url if it can't be found 
on the mirrors. Or set up a web service where tarball updates must be 
submitted to be accessible by build/patchbots (any volunteers for hardware 
/ hosting?)

2) work towards a release script that automatically merges or sets back to 
"needs review" based on tests on a fast machine; This will also increase 
the visibility and pain of random testsuite failures...


-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: SageNB and ldap packages

[kcrisman]

On Saturday, December 9, 2017 at 1:10:53 AM UTC-5, Jori Mäntysalo wrote:
>
> On Fri, 8 Dec 2017, Dima Pasechnik wrote: 
>
> >   How to set up SageNB with LDAP to SageMath 8.1? 
> > 
> >   After some trying I ended up with line 
> > 
> >   from ldap.functions import strf_secs 
> > 
> > 
> > I've no idea where this comes from, it's not in the current sagenb code, 
> > as far as I can tell. 
> > (I didn't try looking too hard, but ldap.functions seems to be something 
> Python 3-only...) 
>
> As always, I started by downloading the stable version and compiled from 
> scratch. So it should be there, or otherwise there are ghosts in the 
> server. 
>

Hmm, what was your previous Sage instance?  There haven't necessarily been 
big changes - see https://github.com/sagemath/sagenb/commits/master - we 
had some things to ensure Py3 compatibility, or at least start it, but the 
last version bump to 1.0.1 really shouldn't have changed anything related 
to ldap.  Did you conceivably compile Sage using Py3? (I didn't think that 
was possible yet to run.)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Why doesn't #23931 get merged?

[Volker Braun]

I understand that everybody wants to see their tickets merged first, thats 
ok. But please realise that you aren't the only one here. The way I see it, 
the choice was between

* Having another potential breakage leading to another rc-version, 
essentially delaying the release by a week.

* You being incovenienced by having to add an extra line to your cygwin 
build script



On Friday, December 8, 2017 at 10:15:42 AM UTC+1, Erik Bray wrote:
>
> On Thu, Dec 7, 2017 at 3:39 PM, Friedrich Wiemer 
>  wrote: 
> > The ticket #23931 has a positive review for quite some time and I'm not 
> > aware of any changes left for it, so my humble question is: Is there a 
> > reason this ticket isn't merged yet? 
>
> In the time between now and when I raised the issue there's no reason 
> the multiple tickets needed for Windows could have been merged no 
> problem.  I don't know why that wasn't done despite my pleas. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Merge fails of positive ticket HOWTO

[Volker Braun]

The easy solution: Just wait for the next beta

If you absolutely positively can't wait you can get the current branch from 
my github page; If you merge with that you'll find the conflict. But don't 
ever publish that merge as it is bound to be rewritten before the next beta 
is released.

On Saturday, December 9, 2017 at 7:54:48 AM UTC+1, Ralf Stephan wrote:
>
> Hi,
> A positive-review ticket was sent back because of merge conflict. 
> Somewhere there has to be the info which other ticket caused it so I can 
> provide a conflict fix. I also remember Volker giving me a web address once 
> in such a case but it's buried in a ticket.
>
> So, I want to put a howto in a Wiki page that explains where to look and 
> what to do.
>
> Can you help please?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Should the "Element = ..." trick require categories?

[Jeroen Demeyer]

The "modern" way to define a Parent class is as follows:

class MyParent(Parent):
Element = MyElement
def __init__(self):
Parent.__init__(self, category=MyCategory())

One thing which surprises me is that the code to have the "Element = 
MyElement" trick work is implemented in the category of Sets. It seems 
to me that this should really be part of the general Parent 
infrastructure, independent of categories.


So, is there any particular reason why this is implemented in Sets? Are 
there any objections to changing that?



Jeroen.

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: SageNB and ldap packages

[Jori Mäntysalo]

On Fri, 8 Dec 2017, William Stein wrote:


CoCalc also support sharing notebooks (and latex documents and pretty
much any type of files) within a group, with realtime multiuser
editing.  That's what the "Add people to project" section of project
settings enables.


Ah, good. So let's test. I didn't found INSTALL.md, so I just read the end 
of https://github.com/sagemathinc/cocalc and npm run install-all ends to


npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: 
fsevents@1.1.3
npm ERR! Linux 4.4.0-98-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! node-sass@4.7.2 install: `node scripts/install.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the node-sass@4.7.2 install script 'node scripts/install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.

But propably this was wrong path anyways?

--
Jori Mäntysalo