just now added ssh key,still same error coming..
On Fri, Jan 17, 2020 at 10:38 PM Aaron Meurer <[email protected]> wrote: > I think you will need to add your ssh key to GitHub. We should be > using the https URL here > https://github.com/sympy/sympy-live/blob/master/.gitmodules. > > Aaron Meurer > > On Fri, Jan 17, 2020 at 6:41 AM James . <[email protected]> wrote: > > > > https://github.com/sympy/sympy-live/blob/master/README.rst > > from this i have followed every step,but im not able to see the gui of > sympy live shell in my local server,i think its because of this command "$ > git submodule update"-->its not working,its showing some error. > > """" > > git submodule update > > Cloning into 'C:/Users/James/AppData/Local/Google/Cloud > SDK/sympy-live/static'... > > Host key verification failed. > > fatal: Could not read from remote repository. > > > > Please make sure you have the correct access rights > > and the repository exists. > > fatal: clone of '[email protected]:sympy/sympy-web-static.git' into > submodule path 'C:/Users/James/AppData/Local/Google/Cloud > SDK/sympy-live/static' failed > > Failed to clone 'static'. Retry scheduled > > Cloning into 'C:/Users/James/AppData/Local/Google/Cloud > SDK/sympy-live/static'... > > Host key verification failed. > > fatal: Could not read from remote repository. > > > > Please make sure you have the correct access rights > > and the repository exists. > > fatal: clone of '[email protected]:sympy/sympy-web-static.git' into > submodule path 'C:/Users/James/AppData/Local/Google/Cloud > SDK/sympy-live/static' failed > > Failed to clone 'static' a second time, aborting > > > > """ > > > > if anyone testing sympy live shell on their local server please tell me > how you did it.. > > > > Regards, > > James > > > > > > On Fri, Jan 17, 2020 at 1:14 AM Aaron Meurer <[email protected]> wrote: > >> > >> I'm not really sure how to create a graph of the number of concurrent > >> users on the App Engine Dashboard. If anyone knows how to do it, let > >> me know. > >> > >> Aaron Meurer > >> > >> On Thu, Jan 16, 2020 at 12:23 PM Mridul Seth <[email protected]> > wrote: > >> > > >> > As Aaron suggested, wouldn't it be much better to use something like > mybinder in the background or https://ines.github.io/juniper/ ? > >> > Why reinvent the wheel? > >> > > >> > The autoscaling thing of App engine translates easily to mybinder too > as every user will have their own instance(docker container) of mybinder > running in the background, > >> > unless sympy expects more than 100 concurrent users it should be okay. > >> > > >> > On Wednesday, 15 January 2020 22:54:38 UTC+5:30, James . wrote: > >> >> > >> >> Django is the best option for sympy live, i have already planned on > telling this because Django is more faster than the current framework and > most of the big companies are also using Django only. > >> >> > >> >> On Wed, Jan 15, 2020, 22:34 Gagandeep Singh (B17CS021) < > [email protected]> wrote: > >> >>> > >> >>> IMHO, it would be great to have the sessions of a particular user > saved. I observed that there is a `Log In` link that let's someone create a > session but it isn't worked upon further. Probably, using django for > redesigning sympy-live would be great as it will be easy to maintain. We > can start from unoptimized version of the website. Though I am not aware > whether Google App Engine supports django. > >> >>> Let me know what you think. > >> >>> > >> >>> On Wed, Jan 15, 2020 at 12:12 AM Aaron Meurer <[email protected]> > wrote: > >> >>>> > >> >>>> Well none of us are backend developers, or else we probably would > have > >> >>>> done something like this already. So you would need to have some > >> >>>> decent backend experience, and would need to come up with a plan on > >> >>>> what to actually do. > >> >>>> > >> >>>> I would prefer to build as little as possible for ourselves, so > that > >> >>>> we don't have to maintain much. So I would look into other projects > >> >>>> such as Binder, and look at what other projects are building in > this > >> >>>> area. If we can build something that is usable by others, or > better, > >> >>>> reuse something that is already built, that would be ideal. > >> >>>> > >> >>>> The biggest technical issue with the App Engine is that it isn't > >> >>>> really designed to do what are do with it. Each App Engine > execution > >> >>>> can run for at most 60 seconds. We "fake" a continual session with > >> >>>> this by doing some tricks like pickling the session. This leads to > all > >> >>>> kinds of bugs, such as the one listed here. I don't actually know > what > >> >>>> causes the bug listed here, but I can make a pretty strong guess > that > >> >>>> it has to do with this. Actually most of these issues have to do > with > >> >>>> pickling itself being broken in a lot of SymPy, but even so, it > would > >> >>>> be better if we had a real persistent session, similar to how > >> >>>> something like Binder works > >> >>>> > >> >>>> At a higher level, I don't like that we have a lot of cloud > specific > >> >>>> code that we have to maintain ourselves, because really nobody does > >> >>>> maintain it, as you can see from the commit history of the SymPy > Live > >> >>>> repo. > >> >>>> > >> >>>> The advantage of the App Engine is that it does autoscaling and > >> >>>> automatic sandboxing. > >> >>>> > >> >>>> Aaron Meurer > >> >>>> > >> >>>> On Tue, Jan 14, 2020 at 11:32 AM James . <[email protected]> > wrote: > >> >>>> > > >> >>>> > Hi,My name is James, i am a 3rd year undergraduate student from > India. I am using python from 3 years, from a couple of months ago I > started using sympy and I am very much interested in refactoring sympy > live.can someone help me what are the prerequisites I need to do this? > >> >>>> > > >> >>>> > On Tue, Jan 14, 2020, 22:46 Aaron Meurer <[email protected]> > wrote: > >> >>>> >> > >> >>>> >> Open an issue in the Live repo about this. > >> >>>> >> > >> >>>> >> SymPy Live will need some serious refactoring in the near future > >> >>>> >> anyway in order to keep it up-to-date, since the current setup > doesn't > >> >>>> >> support Python 3. I'm still hopefully that we can replace the > backend > >> >>>> >> completely (this would be a good GSoC project for anyone > interested). > >> >>>> >> > >> >>>> >> Aaron Meurer > >> >>>> >> > >> >>>> >> On Tue, Jan 14, 2020 at 8:45 AM Chris Smith <[email protected]> > wrote: > >> >>>> >> > > >> >>>> >> > I have found that if you use "_" to refer to the last output > it causes this problem. Fix: reload and remember not to do that. > >> >>>> >> > > >> >>>> >> > On Monday, January 13, 2020 at 7:26:27 AM UTC-6, Gagandeep > Singh (B17CS021) wrote: > >> >>>> >> >> > >> >>>> >> >> Hi, > >> >>>> >> >> > >> >>>> >> >> I am facing some problems on SymPy Live. I tried executing > the example session on live.sympy.org and the following error was thrown, > >> >>>> >> >> > >> >>>> >> >> ``` > >> >>>> >> >> >>> expr = (x + y)**5 > >> >>>> >> >> Traceback (most recent call last): File "<string>", line 1, > in <module> File > "/base/data/home/apps/s~sympy-live-hrd/20200105t193609.423659059328302322/sympy/sympy/core/decorators.py", > line 91, in __sympifyit_wrapper return func(a, b) File > "/base/data/home/apps/s~sympy-live-hrd/20200105t193609.423659059328302322/sympy/sympy/core/decorators.py", > line 129, in binary_op_wrapper return func(self, other) File > "/base/data/home/apps/s~sympy-live-hrd/20200105t193609.423659059328302322/sympy/sympy/core/expr.py", > line 176, in __add__ return Add(self, other) File > "/base/data/home/apps/s~sympy-live-hrd/20200105t193609.423659059328302322/sympy/sympy/core/cache.py", > line 94, in wrapper retval = cfunc(*args, **kwargs) File > "/base/data/home/apps/s~sympy-live-hrd/20200105t193609.423659059328302322/sympy/sympy/core/compatibility.py", > line 916, in wrapper del cache[oldkey] KeyError: [<class > 'sympy.core.add.Add'>, x, y, <class > 'sympy.core.assumptions.ManagedProperties'>, <class > 'sympy.core.symbol.Symbol'>, <class 'sympy.core.symbol.Symbol'>] > >> >>>> >> >> ``` > >> >>>> >> >> Can someone help me with this? > >> >>>> >> >> Thank you. > >> >>>> >> > > >> >>>> >> > -- > >> >>>> >> > You received this message because you are subscribed to the > Google Groups "sympy" group. > >> >>>> >> > To unsubscribe from this group and stop receiving emails from > it, send an email to [email protected]. > >> >>>> >> > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/6c3e4698-8945-4054-8c12-f452b489ee23%40googlegroups.com > . > >> >>>> >> > >> >>>> >> -- > >> >>>> >> You received this message because you are subscribed to the > Google Groups "sympy" group. > >> >>>> >> To unsubscribe from this group and stop receiving emails from > it, send an email to [email protected]. > >> >>>> >> To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2BirBEH3Ki-ka9MoG91y%3DcmGRbYqrgYYaxweAkLUsmWJg%40mail.gmail.com > . > >> >>>> > > >> >>>> > -- > >> >>>> > You received this message because you are subscribed to the > Google Groups "sympy" group. > >> >>>> > To unsubscribe from this group and stop receiving emails from > it, send an email to [email protected]. > >> >>>> > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAHvhkMQdDDX%3Doi-%3D_dfp4%3DT1pKdxjy1%2BHdN3ikfhBxGY4U-Akw%40mail.gmail.com > . > >> >>>> > >> >>>> -- > >> >>>> You received this message because you are subscribed to the Google > Groups "sympy" group. > >> >>>> To unsubscribe from this group and stop receiving emails from it, > send an email to [email protected]. > >> >>>> To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAKgW%3D6LJR8LMqDMJGMv23RuxVHFV4SUg9Q5N7FE53tzFBh%3DuOg%40mail.gmail.com > . > >> >>> > >> >>> > >> >>> > >> >>> -- > >> >>> With regards, > >> >>> Gagandeep Singh > >> >>> Github - https://github.com/czgdp1807/ > >> >>> Linkedin - https://www.linkedin.com/in/czgdp1807/ > >> >>> > >> >>> -- > >> >>> You received this message because you are subscribed to the Google > Groups "sympy" group. > >> >>> To unsubscribe from this group and stop receiving emails from it, > send an email to [email protected]. > >> >>> To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAAvS0gWKUCafHmDsabR%2BZQsSzLS1_KzeqzDbENBhGgQTUvJAeg%40mail.gmail.com > . > >> > > >> > -- > >> > You received this message because you are subscribed to the Google > Groups "sympy" group. > >> > To unsubscribe from this group and stop receiving emails from it, > send an email to [email protected]. > >> > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/09365dca-af50-4c68-b0b1-e8cc4c02b6aa%40googlegroups.com > . > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups "sympy" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > >> To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAKgW%3D6J7wAFORNj62bvOgCjhL0QvEjPxDz33Cy_y%3Dnyf_8%3DweQ%40mail.gmail.com > . > > > > -- > > You received this message because you are subscribed to the Google > Groups "sympy" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAHvhkMQAXapmptOJvpuvXzJCwcCj2_s0caNcRosZSBEk-fOrpQ%40mail.gmail.com > . > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAKgW%3D6LRLcsTfrXwAmt4gGZ%3Dd4WUenmeyZEaeiQhkXUa4vYB_A%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAHvhkMQbX83vdGh7Ab-TSZwnE4LDZiBVxCmT%3DqOfvvJrbydvYw%40mail.gmail.com.
