text:
"Cannot retry request with a non-repeatable request entity" exception when uploading triples

I have made a fresh install of rdf4j 2.1.1 on Tomcat 8.5.
Now I'm trying to add some triples using the workbench->add upload which doesn't work. I get the following exception:
org.apache.http.client.ClientProtocolException
org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
org.eclipse.rdf4j.http.client.SparqlSession.execute(SparqlSession.java:1102)
org.eclipse.rdf4j.http.client.SparqlSession.executeNoContent(SparqlSession.java:1083)
org.eclipse.rdf4j.http.client.SesameSession.upload(SesameSession.java:845)
org.eclipse.rdf4j.http.client.SesameSession.upload(SesameSession.java:672)
org.eclipse.rdf4j.http.client.SesameSession.upload(SesameSession.java:661)
org.eclipse.rdf4j.repository.http.HTTPRepositoryConnection.add(HTTPRepositoryConnection.java:466)
org.eclipse.rdf4j.workbench.commands.AddServlet.add(AddServlet.java:101)
org.eclipse.rdf4j.workbench.commands.AddServlet.doPost(AddServlet.java:52)
org.eclipse.rdf4j.workbench.base.TransformationServlet.service(TransformationServlet.java:96)
org.eclipse.rdf4j.workbench.base.AbstractServlet.service(AbstractServlet.java:125)
org.eclipse.rdf4j.workbench.proxy.ProxyRepositoryServlet.service(ProxyRepositoryServlet.java:109)
org.eclipse.rdf4j.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:213)
org.eclipse.rdf4j.workbench.proxy.WorkbenchServlet.handleRequest(WorkbenchServlet.java:141)
org.eclipse.rdf4j.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:109)
org.eclipse.rdf4j.workbench.proxy.WorkbenchGateway.service(WorkbenchGateway.java:120)
org.eclipse.rdf4j.workbench.base.AbstractServlet.service(AbstractServlet.java:125)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
org.eclipse.rdf4j.workbench.proxy.CacheFilter.doFilter(CacheFilter.java:62)
org.eclipse.rdf4j.workbench.proxy.CookieCacheControlFilter.doFilter(CookieCacheControlFilter.java:53)
root cause
org.apache.http.client.NonRepeatableRequestException: Cannot retry request with a non-repeatable request entity
org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:107)
org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
org.eclipse.rdf4j.http.client.SparqlSession.execute(SparqlSession.java:1102)
org.eclipse.rdf4j.http.client.SparqlSession.executeNoContent(SparqlSession.java:1083)
org.eclipse.rdf4j.http.client.SesameSession.upload(SesameSession.java:845)
org.eclipse.rdf4j.http.client.SesameSession.upload(SesameSession.java:672)
org.eclipse.rdf4j.http.client.SesameSession.upload(SesameSession.java:661)
org.eclipse.rdf4j.repository.http.HTTPRepositoryConnection.add(HTTPRepositoryConnection.java:466)
org.eclipse.rdf4j.workbench.commands.AddServlet.add(AddServlet.java:101)
org.eclipse.rdf4j.workbench.commands.AddServlet.doPost(AddServlet.java:52)
org.eclipse.rdf4j.workbench.base.TransformationServlet.service(TransformationServlet.java:96)
org.eclipse.rdf4j.workbench.base.AbstractServlet.service(AbstractServlet.java:125)
org.eclipse.rdf4j.workbench.proxy.ProxyRepositoryServlet.service(ProxyRepositoryServlet.java:109)
org.eclipse.rdf4j.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:213)
org.eclipse.rdf4j.workbench.proxy.WorkbenchServlet.handleRequest(WorkbenchServlet.java:141)
org.eclipse.rdf4j.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:109)
org.eclipse.rdf4j.workbench.proxy.WorkbenchGateway.service(WorkbenchGateway.java:120)
org.eclipse.rdf4j.workbench.base.AbstractServlet.service(AbstractServlet.java:125)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
org.eclipse.rdf4j.workbench.proxy.CacheFilter.doFilter(CacheFilter.java:62)
org.eclipse.rdf4j.workbench.proxy.CookieCacheControlFilter.doFilter(CookieCacheControlFilter.java:53)
I can't be the only one with this problem?
/Rune

I can't immediately reproduce this.
How are you adding the triples: by URL, by local file upload, or are you using the text area to copy-paste data?
Also: what kind of store are you uploading to? Native, Memory? Any reasoners or other "extras" (lucene, etc) enabled?
Are there any errors or warning in the RDF4J Server logs (http://localhost:8080/rdf4j-server/system/logging/overview.view)?

Possible cause is use of InputStreamEntity (which is non-repeatable) to read an InputStream. We should look into using a FileEntity instead, if possible.

Btw this should not normally happen: for some reason the initial request failed, the http client tries to redo the request (and fails because it uses an inputstream for its content). It will be interesting to figure out why the request failed (which is why I'd like to see if your server logs show anything).

Hi Jeen
So it’s happening when I try upload an .nt-file via the add menu in the workbench:
Uploading the same data as rdf works.
The same problem if I use curl.
Other questions:

Simple Native Java Store
No reasoners
RDF4J Workbench 2.1.1
Java 1.8.0_112

Server log:
[Rio fatal] Auf Elementtyp "http:" müssen entweder Attributspezifikationen, ">" oder "/>" folgen. (1, 8)
Client sent bad request ( 400)org.eclipse.rdf4j.http.server.ClientHTTPException: MALFORMED DATA: Auf Elementtyp "http:" müssen entweder Attributspezifikationen, ">" oder "/>" folgen. [line 1, column 8]
Rolling back transaction due to connection closejava.lang.Throwable: null
at org.eclipse.rdf4j.sail.helpers.AbstractSailConnection.close(AbstractSailConnection.java:224)
at org.eclipse.rdf4j.repository.sail.SailRepositoryConnection.close(SailRepositoryConnection.java:199)
at org.eclipse.rdf4j.http.server.repository.RepositoryInterceptor.cleanUpResources(RepositoryInterceptor.java:164)
at org.eclipse.rdf4j.http.server.ServerInterceptor.afterCompletion(ServerInterceptor.java:45)
at org.eclipse.rdf4j.http.server.ServerInterceptor$$FastClassBySpringCGLIB$$3d820688.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:717)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:653)
at org.eclipse.rdf4j.http.server.repository.RepositoryInterceptor$$EnhancerBySpringCGLIB$$8ebd78c0.afterCompletion()
at org.springframework.web.servlet.HandlerExecutionChain.triggerAfterCompletion(HandlerExecutionChain.java:170)
at org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1045)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:971)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at com.github.ziplet.filter.compression.CompressingFilter.doFilter(CompressingFilter.java:300)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:108)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:620)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:784)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:802)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1410)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source)
Client sent bad request ( 400)org.eclipse.rdf4j.http.server.ClientHTTPException: MALFORMED DATA: Auf Elementtyp "http:" müssen entweder Attributspezifikationen, ">" oder "/>" folgen. [line 1, column 8]
at org.eclipse.rdf4j.http.server.repository.statements.StatementsController.getAddDataResult(StatementsController.java:463)
at org.eclipse.rdf4j.http.server.repository.statements.StatementsController.handleRequestInternal(StatementsController.java:125)
at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:147)
at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:50)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at com.github.ziplet.filter.compression.CompressingFilter.doFilter(CompressingFilter.java:300)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:108)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:620)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:784)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:802)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1410)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source)
Regards,
Rune

Den 12. nov. 2016 kl. 00.41 skrev Jeen Broekstra notifications@github.com:
I can't immediately reproduce this.
How are you adding the triples: by URL, by local file upload, or are you using the text area to copy-paste data?
Also: what kind of store are you uploading to? Native, Memory? Any reasoners or other "extras" (lucene, etc) enabled?
Are there any errors or warning in the RDF4J Server logs (http://localhost:8080/rdf4j-server/system/logging/overview.view)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/eclipse/rdf4j/issues/647#issuecomment-260081158, or mute the thread https://github.com/notifications/unsubscribe-auth/AEeP1hFiOVuLRIc51_TdLeHtEkI3rWz3ks5q9P0tgaJpZM4KvnFT.

It's definitely strange that you get this unhelpful error in the Workbench, but the Server log shows that your N-Triples file is syntactically incorrect. Apparently already at line 1. This is what causes the request to fail.

Strange because since it’s an unmodified export from the workbench of an earlier version om Sesame.

Den 14. nov. 2016 kl. 16.29 skrev Jeen Broekstra notifications@github.com:
It's definitely strange that you get this unhelpful error in the Workbench, but the Server log shows that your N-Triples file is syntactically incorrect. Apparently already at line 1. This is what causes the request to fail.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/eclipse/rdf4j/issues/647#issuecomment-260366456, or mute the thread https://github.com/notifications/unsubscribe-auth/AEeP1i1U5IqfnXQjO7E_hdv-XIi2t6yBks5q-H5vgaJpZM4KvnFT.

There have been some changes in the N-Triples parser. We updated to a newer version of the spec a few versions of Sesame ago. However I thought those changes were backward-compatible.
Can you copy in a fragment of your N-Triples file? Just the first few lines should do since apparently the problem is right at the start...

Ok - Thank you:
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.kl.dk/ontologies/kle_emneindeks.owl#Hovedgruppe .
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.kl.dk/ontologies/kle_emneindeks.owl#Hovedgruppe .
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.w3.org/2000/01/rdf-schema#label "Kommunens styrelse" .
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.kl.dk/ontologies/kle_emneindeks.owl#HgServicesidetekst "Hovedgruppe 00 'Kommunens styrelse' d\u00E6kker sager der vedr\u00F8rer styrelsen af kommunen som kommune jf. kommunestyrelsesloven. Det g\u00E6lder bl.a. kommunalbestyrelsens konstituering, neds\u00E6ttelse af politiske udvalg, forretningsorden, styrelsesvedt\u00E6gt, kommunens organisation og \u00F8konomiske forvaltning.\n\nHovedgruppe 00 indeholder ogs\u00E5 grupper, som ikke naturligt kan indplaceres under de \u00F8vrige hovedgrupper. Fx 00.03 'International virksomhed og EU', 00.05 'Bes\u00F8g, repr\u00E6sentation', 00.10 'Integration og udl\u00E6ndinge.'\n\nSager der g\u00E5r p\u00E5 tv\u00E6rs af flere hovedgrupper, indplaceres under 00.01.10 'Opgaver der d\u00E6kker flere hovedgrupper', oprettet konkret til dette form\u00E5l.\n\nHovedgruppe 00 omfatter bl.a. sager, der administreres/behandles i henhold til f\u00F8lgende lovgivning:\n\n\nLBK om folkeskolen (Folkeskoleloven)\nLBK om fonde og visse foreninger (Fondsloven)\nLBK om forpligtende kommunale samarbejder\nLBK om fremgangsm\u00E5den ved ekspropriation vedr\u00F8rende fast ejendom\nLBK om kommunal udligning og generelle tilskud til kommuner (Udligningsloven)\nLBK om kommunernes styrelse (Kommunestyrelsesloven)\nLBK om regionernes finansiering\nLBK om statsgaranti til l\u00E5n til fors\u00F8gsbyggeri (St\u00F8ttet boligbyggeri)\nLBK om ungdomsskoler (Ungdomsskoleloven)\nLov om en satsreguleringsprocent\nLov om etablering af den selvejende institution Udbetaling Danmark\nLov om Folketingets Ombudsmand (Ombudsmandsloven)\nLov om kommunale borgerservicecentre (Borgerservicecenterloven)\nLov om midlertidig binding af kommunernes og amtskommunernes overskudslikviditet\nLov om neds\u00E6ttelse af statstilskuddet til kommuner ved forh\u00F8jelser af kommunale parkeringsindt\u00E6gter\nLov om offentlighed i forvaltningen (Offentlighedsloven)\nLov om regionale kulturfors\u00F8g\nLov om revision af den kommunale inddeling\nLov om Udbetaling Danmark (Udbetaling Danmark-loven)\nLov om videreanvendelse af den offentlige sektors informationer (PSI-loven)\nLov om \u00E6ndringer af landets inddeling i kommuner og regioner og om opl\u00F8sning og udpegelse af forpligtende kommunale samarbejder\nLov om socialtilsyn (Socialtilsynsloven)\nLov om \u00E6ndring af lov om Det Centrale Personregister (S\u00E6rlig adressebeskyttelse til personer, som uds\u00E6ttes for trusler mod deres person i forbindelse med \u00E6resrelaterede eller samlivsrelaterede konflikter m.v.) (CPR-loven)\nLBK om biblioteksvirksomhed (Biblioteksloven)\nBEK om beregning af satsreguleringsprocenten m.v.\nBEK om deling af kommuner\nBEK om forretningsorden for b\u00F8rn og unge-udvalgene\nBEK om kommuners l\u00E5ntagning og meddelelse af garantier mv.\nBEK om kommunernes mellemv\u00E6render med de kommunale forsyningsvirksomheder\nBEK af lov om frikommuner m.v. (Frikommuneloven)\nBEK om aktindsigt i visse interne kommunale og regionale dokumenter\nBEK af lov om rettens pleje\nBEK om Udbetaling Danmarks kontoplan m.v.\nBEK om kommunernes budget- og regnskabsv\u00E6sen, revision m.v.\nBEK om \u00E6ndring af bekendtg\u00F8relse om regionernes budget- og regnskabsv\u00E6sen, revision m.v.\nBEK om regnskaber m.v. for Udbetaling Danmark\nBEK af lov om merv\u00E6rdiafgift (momsloven)\nBEK af forvaltningsloven (Forvaltningsloven)\nBEK om organisering og underst\u00F8ttelse af besk\u00E6ftigelsesindsatsen m.v.\n\n" .
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.kl.dk/ontologies/kle_emneindeks.owl#Hovedgruppenummer "00" .
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.kl.dk/ontologies/kle_emneindeks.owl#Oprettetdato "1988-01-01"^^http://www.w3.org/2001/XMLSchema#date .
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.kl.dk/ontologies/kle_emneindeks.owl#har_rettelse http://www.kl.dk/ontologies/kle_emneindeks.owl#ret_hg_00 .
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.kl.dk/ontologies/kle_emneindeks.owl#indg\u00E5r_i_delplan http://www.kl.dk/ontologies/kle_emneindeks.owl#dp_FolkeskolenDelplan .
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.kl.dk/ontologies/kle_emneindeks.owl#indg\u00E5r_i_delplan http://www.kl.dk/ontologies/kle_emneindeks.owl#dp_DagtilbudDelplan .
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.kl.dk/ontologies/kle_emneindeks.owl#indg\u00E5r_i_delplan http://www.kl.dk/ontologies/kle_emneindeks.owl#dp_KommunalVandDelplan .
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.kl.dk/ontologies/kle_emneindeks.owl#indg\u00E5r_i_delplan http://www.kl.dk/ontologies/kle_emneindeks.owl#dp_SaerligStoetteDelplan .
http://www.kl.dk/ontologies/kle_emneindeks.owl#_00 http://www.kl.dk/ontologies/kle_emneindeks.owl#indg\u00E5r_i_delplan http://www.kl.dk/ontologies/kle_emneindeks.owl#dp_JobcenterDelplan .

Den 14. nov. 2016 kl. 16.44 skrev Jeen Broekstra notifications@github.com:
There have been some changes in the N-Triples parser. We updated to a newer version of the spec a few versions of Sesame ago. However I thought those changes were backward-compatible.
Can you copy in a fragment of your N-Triples file? Just the first few lines should do since apparently the problem is right at the start...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/eclipse/rdf4j/issues/647#issuecomment-260370995, or mute the thread https://github.com/notifications/unsubscribe-auth/AEeP1q-86Ir6-P2fGcURnM__vuOdGsVhks5q-IHagaJpZM4KvnFT.

Odd - I can upload the fragment you provided just fine, without any errors. Can you verify if the problem still occurs if you only try to upload this fragment?
If it no longer occurs with this fragment, there might be a problem deeper in the file. Not sure how private your data is, but if possible can you attach a copy of the full file to this issue?

Update I think I have found the root cause: you are trying to upload a file of type "N-Triples", but you have the wrong file type selected, or you have "(autodetect)" selected. Unfortunately autodetect does not work properly, this is a known issue ( #67 ). Try uploading by explicitly selecting "N-Triples" in the file format dropdown.
A secondary issue is that  the error should be reported like this:

But instead you get this strange ClientProtocolException

Hi Jeen
I found out importing in RDF and via looking at the system log, that I problems with non valid RDF:id-names, and also duplicates. Like you said these things weren’t checked in the older Sesame versions.
Only thing is, that the browser and API still throws the not very telling connection exception, when there’s and error in the RDF/XML. I have to go to the system log to see what’s actually wrong.

Den 16. nov. 2016 kl. 04.42 skrev Jeen Broekstra notifications@github.com:
Update I think I have found the root cause: you are trying to upload a file of type "N-Triples", but you have the wrong file type selected, or you have "(autodetect)" selected. Unfortunately autodetect does not work properly, this is a known issue ( #67 https://github.com/eclipse/rdf4j/issues/67 ). Try uploading by explicitly selecting "N-Triples" in the file format dropdown.
A secondary issue is that the error should be reported like this:
https://cloud.githubusercontent.com/assets/728776/20333995/c2f86aae-ac0a-11e6-9ed0-639758b711a2.png
But instead you get this strange ClientProtocolException
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/eclipse/rdf4j/issues/647#issuecomment-260845572, or mute the thread https://github.com/notifications/unsubscribe-auth/AEeP1oUDiflluqKPg2_Z6eJ5Nlhvqx9xks5q-nuagaJpZM4KvnFT.

One of the implementations of SesameSession.upload (heavily overloaded and there are multiple final paths possible) buffers the content into a ByteArrayInputStream in memory and stores it in a custom implementation of AbstractHttpEntity. It then uses Apache Commons IOUtil.transfer, which seems like it depletes the InputStream, and hence isRepeatable has been set to return false for it. It could be implemented alternatively to be repeatable, given it is already buffering. That could improve debugging for issues like this.
I found this while reviewing my changes for #684, but I won't change it in that pull request.

authors: ansell jeenbroekstra rune66


text:
JMH runner ignores lock to avoid parallel builds failing

This PR addresses GitHub issue: #1529  .
Briefly describe the changes proposed in this PR:

configured surefire plugin set jmh.ignoreLock to true to avoid benchmark execution failing
ran local parallel test, seems to solve the issue (but proof is in Jenkins obviously)

Merging this in immediately in a "let's see if it actually works" kinda way.

source: gharchive/pull-request

license_type: permissive

license_source: bigquery


text:
Merge develop into main

GitHub issue resolved: #
Briefly describe the changes proposed in this PR:

PR Author Checklist (see the contributor guidelines for more details):

[ ] my pull request is self-contained
[ ] I've added tests for the changes I made
[ ] I've applied code formatting (you can use mvn process-resources to format from the command line)
[ ] I've squashed my commits where necessary
[ ] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

Main requires PR verify for java 8 :(


text:
Update third-party-libraries with latest output

third-party-libraries.xlsx as generated from eb34c80cd1c511ed7184f4ba4993a95208753e42

Can one of the admins verify this patch?

repo: eclipse/winery

license_source: github-api


text:
CadsObs adaptor to use the retrieve_list_of_results method

For consistency with other adaptors, the CadsObs adaptor should use the retrieve_list_of_results method.
This returns a list of paths, and is called by the default self.retrieve method. The self.make_download_object is then responsible turning the list of paths into a downloadable object for the retreive-api.
If the default self.make_download_object is incompatible with the adaptor, then please define your own retrieve method which handles the creation of a download object, which must be an open binary file.
This will give more flexibility with anticipated functionality, and allows use with the MultiAdaptor.
(Markel, this is lower priority than the task that Paul has given you, we can discuss in the next  sprint meeting)

It should be easy to do, we only need to be careful with the error handling.

source: gharchive/issue

authors: EddyCMWF garciampred

repo: ecmwf-projects/cads-adaptors


text:
Support for ecflow-generated variables

Is your feature request related to a problem? Please describe.
We can't use ecflow-generated variables in scripts as they are not supported by pyflow, which means they are not detected and exported at the beginning of the script. For instance, if I create a RepeatDate("YMD",...), ecflow will generate the following variables:

YMD
YMD_DD
YMD_DOW
YMD_JULIAN
YMD_MM
YMD_YYYY
But we can't use those because they are not added to the exportables list in pyflow (see https://github.com/ecmwf/pyflow/blob/master/pyflow/attributes.py#L259 and https://github.com/ecmwf/pyflow/blob/master/pyflow/nodes.py#L401). The RepeatDate class is only linked to one exported variable, following the name provided in the RepeatDate class.
The FAMILY variable, attached to a Family node is another example, but there are many others. We should list them.

Describe the solution you'd like
We could maybe add a list of exportables attached to an Exportable class?
Describe alternatives you've considered
No response
Additional context
No response
Organisation
No response

List of ECFLOW generated variables (missing repeat and maybe other attributes): https://ecflow.readthedocs.io/en/latest/ug/user_manual/ecflow_variables/generated_variables.html

repo: ecmwf/pyflow


text:
怎么给图表添加点击事件，以便反馈到page里进行重新赋值

提问前应该做的事
请确保提问前做了以下事，将完成的项目的 [] 改为 [x]：

[x] 我已通读过 README
[x] 我已阅读过 FAQ

需提供的信息
将符合项的 [] 改为 [x]，并补充需要的信息：
简单描述问题：
想点击图表后，给界面上独立于图表外的值重新赋值
预期效果：
？？？
（如有需要请提供预期的图）
实际效果：
？？？
（如有需要请提供截图）
复现环境：

[] 在微信开发工具中存在该问题
[] 在真机上存在该问题

试试在tooltip的formatter的回调函数里面触发图表外方法

在初始化图表（init）里增加：
Chart.on('click', function (params) {
//你的具体逻辑流程
that.setData({
     });
  })

在初始化图表（init）里增加：
Chart.on('click', function (params) {
//你的具体逻辑流程
that.setData({
     });
  })

没效果...

authors: Lamenda SingleShadow curiousbabyMz ehcsa

repo: ecomfe/echarts-for-weixin


text:
看图，折线图有两组数据的时候好像不准确

One-line summary [问题简述]
option = {
title: {
text: '折线图堆叠'
},
tooltip: {
trigger: 'axis'
},
legend: {
data:['邮件营销','联盟广告','视频广告','直接访问','搜索引擎']
},
grid: {
left: '3%',
right: '4%',
bottom: '3%',
containLabel: true
},
toolbox: {
feature: {
saveAsImage: {}
}
},
xAxis: {
type: 'category',
boundaryGap: false,
data: ['周一','周二','周三','周四','周五','周六','周日']
},
yAxis: {
type: 'value'
},
series: [
{
name:'邮件营销',
type:'line',
stack: '总量',
data:[120, 132, 101, 134, 90, 230, 210]
},
{
name:'联盟广告',
type:'line',
stack: '总量',
data:[220, 182, 191, 234, 290, 330, 310]
},
{
name:'视频广告',
type:'line',
stack: '总量',
data:[150, 232, 201, 154, 190, 330, 410]
},
{
name:'直接访问',
type:'line',
stack: '总量',
data:[320, 332, 301, 334, 390, 330, 320]
},
{
name:'搜索引擎',
type:'line',
stack: '总量',
data:[820, 932, 901, 934, 1290, 1330, 1320]
}
]
};
以上的数据显示，“搜索引擎”对应的线条高度是不对的！这个就是官网的示例
Version & Environment [版本及环境]

ECharts version [ECharts 版本]:
Browser version [浏览器类型和版本]:
OS Version [操作系统类型和版本]:

Expected behaviour [期望结果]
ECharts option [ECharts配置项]

option = {

}

Other comments [其他信息]

可能我对stack: '总量',不大理解，去掉又是正常的

repo: ecomfe/echarts


text:
fix(Discount): remove discount in Subscription GalaxPay

Relacionado a issue #28

https://apx-mods.e-com.plus/api/v1/create_transaction/schema.json?store_id=100
O params.items aqui realmente não tem a propriedade flags e também a amout.balance também não. Acredito que essas sejam as únicas pendências.

repo: ecomplus/app-galaxpay

license: MIT


text:
Update helpers.html

typo at makeEndpoint
update signle to single

Thank you, but sorry, gh-page is not where you fix issues. it's on /website on .md files.

Sorry, I tried to find it and didn't know how I ended up on gh-page

authors: ecyrbe pkrinesh

repo: ecyrbe/zodios


text:
Require sb3 version 2 or newer

Our environment will not work with older sb3 versions, due to using gymnasium (where older sb3 versions used gym).
Edit: This may cause an issue with rllib, I will check the test results and see if it can be addressed if it does.

It seems that older Ray is installed on the tests that pass, so by specifying the gymnasium version we could be enforcing older Ray (which works with our config) to be installed. On the newer version of Ray, I also locally had some issues unless I try a different path format. Even outside of the path issue, I also had some issues with one of my environments with both Ray versions, something about the format of observations, but I didn't test it in-depth, so I don't know the issue was related to my Godot environment (which worked with SB3 which I mostly use for now), or something else.
I'll add the gymnasium version as a quick temporary fix, if it works, we can merge the PR for now since it's focused on ensuring the correct SB3 version, and in the future we can test our Ray configuration and see if something needs to be updated.

With this approach, newer Ray 2.7 seems to work, although I didn't perform much testing to see if everything works with this as before. As a quick fix I've changed the folder path to an absolute path as that seems to fix the error. An alternative could be to use older Ray or find a different fix for the issue.
It should be noted that one of my environments didn't work with rllib (some observation type error), but I think that holds for both Ray versions, and may need more troubleshooting at some future point as I'm not sure about the cause yet (maybe something with the env itself even though it works with SB3). Jumperhard worked on my PC as well, but there might be some difference in observations from my env (which has some floats and a raycast obs array).
For future reference and in case similar errors appear in the future, the error was:
ValueError: The two structures don't have the same nested structure.

First structure: type=dict str={'obs': [0.0028, 0.000441726500866935, 0.00281361560337245, 0.00664886436425149, 0.260605245828629, 0.39156648516655, -0.00112051225733, -1.99999463558197, 0.781054401397705, 0.746744704246521, 0.712950587272644, 0.76171236038208, 0.769729685783386, 0.743742609024048, 0.659272933006287, 0.363503074645996, 0, 0.292076635360718, 0.415652275085449, 0.244122076034546, 0, 0.216817808151245, 0.643476295471191, 0.747096061706543, 0.781146144866943]}

Second structure: type=OrderedDict str=OrderedDict([('obs', array([-0.19811498,  0.8486953 ,  0.7596289 ,  0.2623617 , -0.08332985,
        0.21301392,  0.7458078 , -0.4820755 , -0.88564146, -0.6634987 ,
        0.82966214,  0.6683578 , -0.18554112, -0.7013975 ,  0.8797588 ,
       -0.24309783,  0.77364075,  0.4879668 , -0.982385  , -0.4481921 ,
        0.8362797 , -0.21034704,  0.9531232 , -0.33154443,  0.886062  ],
      dtype=float32))])

More specifically: Substructure "type=list str=[0.0028, 0.000441726500866935, 0.00281361560337245, 0.00664886436425149, 0.260605245828629, 0.39156648516655, -0.00112051225733, -1.99999463558197, 0.781054401397705, 0.746744704246521, 0.712950587272644, 0.76171236038208, 0.769729685783386, 0.743742609024048, 0.659272933006287, 0.363503074645996, 0, 0.292076635360718, 0.415652275085449, 0.244122076034546, 0, 0.216817808151245, 0.643476295471191, 0.747096061706543, 0.781146144866943]" is a sequence, while substructure "type=ndarray str=[-0.19811498  0.8486953   0.7596289   0.2623617  -0.08332985  0.21301392
  0.7458078  -0.4820755  -0.88564146 -0.6634987   0.82966214  0.6683578
 -0.18554112 -0.7013975   0.8797588  -0.24309783  0.77364075  0.4879668
 -0.982385   -0.4481921   0.8362797  -0.21034704  0.9531232  -0.33154443
  0.886062  ]" is not
Entire first structure:
{'obs': [., ., ., ., ., ., ., ., ., ., ., ., ., ., ., ., ., ., ., ., ., ., ., ., .]}
Entire second structure:
OrderedDict([('obs', .)])


text:
[RFR] Fixed an issue with non-button toggles

Fix #23.

Yes.

Looks great

authors: HugoGiraudel smartmike


text:
cicd: specify unittest directory

Description
cicd: specify unittest directory
Type of change

[ ] Bug fix
[ ] New feature
[ ] Document
[x] Test
[x] CI/CD
[x] Refactor

How has this been tested

[x] Unittest
[ ] Others:

Checklist:

[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Let's make the world better✨😋🐍🌎

Codecov Report

Merging #37 (9336a49) into main (c60b059) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #37   +/-   ##
=======================================
  Coverage   95.56%   95.57%
=======================================
  Files          21       21
  Lines         609      610    +1
  Branches       36       36
=======================================
+ Hits          582      583    +1
  Misses         18       18
  Partials        9        9

Impacted Files
Coverage Δ

pypj/task/githubactions.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c60b059...9336a49. Read the comment docs.

authors: codecov-commenter edge-minato

repo: edge-minato/pypj


text:
Restore Tenant Provisioning

Move it to the Tenants API, removing the Provisioning context.
Use AshJsonApi to expose a new JsonApi compatible API.

Edgehog.Tenants.Reconciler.Behaviour expects Edgehog.Tenants.Tenant to have a typespec @type t().
Ash.Resource has @type record :: struct().
I think we can start with @type record :: Ash.Resource.record() for Tenant and Tenant.record() in Reconciler.Behaviour

authors: rbino szakhlypa

repo: edgehog-device-manager/edgehog


text:
Update edgex modules to v0.1.0 pre-edinburgh

Fix #1380
In preparation for cutting the edinburgh branch, we need to consume
v0.1.0 in the go.mod for all edgex modules

go-mod-core-contracts
go-mod-messaging
go-mod-registry

Signed-off-by: Trevor Conn trevor_conn@dell.com

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@823421a). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1383   +/-   ##
=========================================
  Coverage          ?   17.02%
=========================================
  Files             ?       78
  Lines             ?     8789
  Branches          ?        0
=========================================
  Hits              ?     1496
  Misses            ?     7142
  Partials          ?      151

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 823421a...904ce62. Read the comment docs.

repo: edgexfoundry/edgex-go


text:
feat(notifications): Implement GET /transmission/id/{id} V2 API

Close: #3452
Signed-off-by: weichou weichou1229@gmail.com
PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?

Issue Number: #3452
What is the new behavior?
Implement GET /transmission/id/{id} V2 API according to the doc https://app.swaggerhub.com/apis-docs/EdgeXFoundry1/support-notifications/2.x#/default/get_transmission_id__id_
Does this PR introduce a breaking change?

[ ] Yes
[x] No

New Imports

[ ] Yes
[x] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

Rebased.


text:
Replace the use of the deprecated Dict module

The Dict module is deprecated.

Coverage remained the same at 90.135% when pulling 6f9925fd925e38535c7078934b2c3e43f3528b29 on nscyclone:fix/replace-dict into 925200ded23aa0009919a3e48a0dae1952398d63 on edgurgel:master.

thank you @nscyclone

authors: coveralls duksis nscyclone

repo: edgurgel/tentacat

license: mit


text:
Remove the Jenkins setup wizard

On first provisioning of the vagrant box when running the Jenkins server the user has to go through a security setup wizard. This should be removed to further speed up the process of having the Jenkins ready.

I've done this before so might be able to help, it's a case of adding a lot of jenkins config files and is quite verbose

Any contributions are welcome really.

This was resolved with #10.
Thank you for all your contributions @munkiepus. I will add you as a contributor to the repository so that you can directly create branches and review and merge future PR-s.

authors: edinc munkiepus

repo: edinc/vagrant-jenkins


text:
Adapt generated tmux config to new tmux 2.9 syntax

Closes #102
Closes #100
Inspired by @secuvim in #102
I do not know if this is all that is needed, but it worked for me.

This would break the backwards compatibility for users with tmux versions < 1.9.
To keep the backwards compatibility you could wrap your changes in something like:
let tmux_version = system("tmux -V")
    if (tmux_version < 'tmux 1.9')
        let misc_options = ...
        let win_options = ...
    else
        let misc_options = ...
        let win_options = ...
    elseif

This is just a suggestion as I am not the maintainer of this package.
@He-Ro Thanks for implementing a fix.
@edkolev What is your opinion on this?

Some of the presets appear to write into win_options['window-status-activity-attr'] which causes problems if you're using one of those presets:

https://github.com/edkolev/tmuxline.vim/blob/c8a0295eb34bf11447779a5a203fd472147788a7/autoload/tmuxline/presets/powerline.vim#L26
https://github.com/edkolev/tmuxline.vim/blob/c8a0295eb34bf11447779a5a203fd472147788a7/autoload/tmuxline/presets/nightly_fox.vim#L15
https://github.com/edkolev/tmuxline.vim/blob/c8a0295eb34bf11447779a5a203fd472147788a7/autoload/tmuxline/presets/crosshair.vim#L23

@He-Ro amazing work on this, thanks! Could you also:

git grep and change everywhere window-status-activity-attr => window-status-activity-style
add yourself to the CONTRIBUTORS.md in the root of the project

@khalsah good catch!

This would break the backwards compatibility for users with tmux versions < 1.9.
@edkolev What is your opinion on this?

I'm fine with breaking compatibility for tmux <1.9 - it's been more than 5 years since 1.9 was released. Adding a conditional in the vim script would not work when you share the generated tmux conf file between machines with different versions of tmux.

Added the requested changes.
Also found a mention of attr in the README.

Thanks for working on this. Just noting https://github.com/tmux/tmux/wiki/FAQ#how-do-i-translate--fg--bg-and--attr-options-into--style-options and curious if this was a known issue here.

and curious if this was a known issue here

Could you clarify the question? The link is pointing to a wiki entry about migration; the wiki entry isn't a know issue

Gotcha, maybe this issue isn't related. I had to manually fix up some tmuxline generated settings to comply with the Tmux 2.9 Syntax ralated to -style and -attr. If thosed fixes have been merged in, I can try to run a new snapshot and see if that works.

This PR addresses exactly this - the *-fg/bg to *-style migration. And yes, you should be able to create a snapshot which works with the lates tmux.

authors: He-Ro edkolev khalsah secuvim shrop


text:
🛑 Siakad Polinema is down

In d38fb84, Siakad Polinema (http://siakad.polinema.ac.id/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Siakad Polinema is back up in 29a90bf.

repo: edoaurahman/check-web-uptime


text:
Workaround to repair IsLastestVersion for Android.

Quick implementation from Nick Kovalsky workaround :
https://stackoverflow.com/questions/72407251/how-to-get-version-number-of-application-from-play-store-using-xamarin-forms/72643625#72643625
Fixes #43 #42  .
Changes proposed in this pull request:

Repair plugin for Android Platform.

Thank you for the PR.
Please remove the second commit - a test project should not be included in this PR, just the fix. That commit is also breaking the build.
Thank you.

Beta nuget is available here: https://www.nuget.org/packages/Xam.Plugin.LatestVersion/2.1.1-beta.107

authors: Jerome-Liger edsnider

repo: edsnider/latestversionplugin


text:
🛑 Webmail-DGE is down

In 780e7e4, Webmail-DGE (http://www.webmail.mendoza.edu.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Webmail-DGE is back up in fb9aa22.

repo: edu-red/DGE-GOV


text:
🛑 Portal-DGE is down

In 93f61cc, Portal-DGE (https://www.mendoza.edu.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portal-DGE is back up in a66ab92.


text:
WIP [BD-6] OEP-18 Compliance and tests Python 3.8

Add setup.py install_requirements definition.
Update travis file using new requirements.
Create requirements folder.
create pip_tools, base, test and travis requirements files.
Add Makefile.
Add makefile upgrade command.
Include requirements files generated using upgrade command.
Add openedx.yaml and include OEPs list.
Add python 3.8 to tests.

Thanks for the pull request, @ericfab179! I've created OSPR-4550 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.
Feel free to add as much of the following information to the ticket:

supporting documentation
edx-code email threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here.

@ericfab179 🎉 Your pull request was merged!
Please take a moment to answer a two question survey so we can improve your experience in the future.

repo: edx/TinCanPython


text:
API client now passes the user's full name to ecommerce

This merge also requires a merge on ecommerce and edx-platform with tyler-jwt-fullname, so keep that in mind.
@clintonb @rlucioni FYI: @wedaly @jimabramson

Tests are required.

@clintonb Will do that now

Minor: Cleanup the commit message. We generally use a simple statement of the overall change as the title (e.g. Added support for passing full name via JWT). Additional information can be provided as a paragraph or list after the title.
Added support for passing full name via JWT

- User's full name can be passed to the API when using JWT authentication. This field is optional.
- Email is no longer required for JWT authentication.

Aside from the message change, :+1: . Please await a second approval from @rlucioni or @jimabramson before merging.

Oh, I actually not aware that Git messages could be multiline like that. I'll change it then force a push. Thanks @clintonb.

Once you get a clean build, :+1: .

@Nickersoft I'm surprised to see a major version bump on this change; was expecting 0.5.0.  Is there something backwards-incompatible?

@jimabramson My mistake. The constructor was changed in a backwards-incompatible manner. We can make it backwards-compatible if you'd like.

ah.   somehow i missed that.  As it's backward-incompatible, then 1.0.0 is fine and I'll shut up.

authors: Nickersoft clintonb jimabramson rlucioni

repo: edx/ecommerce-api-client


text:
Navigate within App from dates to course component

Description
LEARNER-8214

Navigate within app when a link is clicked on Full Page dates screen

@omerhabib26 The app still navigates to screen for the un-available course unit.
https://user-images.githubusercontent.com/43750646/108349158-78f9bb00-7204-11eb-9459-e5fbb3221edc.mp4

repo: edx/edx-app-android


text:
Update AUTHORS and bump version

Update to AUTHORS and bump version to 1.3.0

@clintonb @rlucioni

:+1:

:+1:

authors: clintonb mjfrey rlucioni

repo: edx/edx-rest-api-client


text:
Add manual control of Repeat and Shuffle

Related to #8 is adding the ability to toggle shuffle and repeat. The play queue should have the following states:

Shuffle on: randomize the order of the queue every time shuffle is turned on.
Shuffle off:

Version 1: It would be fine to just not change the order of the current play queue for V1 of this feature .
Version 2: If playing from a defined playlist (either a playlist, album list, or a future "All Songs" view), turning shuffle off should reorder the queue according to the list display order, with playback continuing from whatever queue position holds the currently playing song. If playing from a queue modified with "Add to Queue", just leave the queue in its current order.
Version 3: If the queue was created with "Play Next" or "Add to Queue", reorder the queue according to the order of whatever view it was started with and play back from whatever queue position the current song is at.

Repeat off: play to the end of the current queue and stop.
Repeat One: continuously play the current song, only changing if the song is manually changed by the user (by choosing a new song or pressing the Next button).
Repeat All: play to the end of the current queue; if Shuffle is on randomize the queue order and start from the beginning, or if shuffle is off just go back to the beginning of the queue and continue playback.

When starting playback by choosing a song or pressing Play, the Shuffle state should be whatever it was previously. When starting playback by pressing Shuffle, the Shuffle state should be turned on.

Defs want to add this. At the moment playback issues are my priority. I would like to have a solid foundation before bolting on features.

authors: eeston jgoguen

repo: eeston/Jello


text:
🛑 Nodo UTT Ramos Mejia is down

In c4ef14b, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in d53b9f4.

repo: efecear/upptime


text:
🛑 Tierra Firme is down

In 69bb2d7, Tierra Firme (https://www.tierrafirmenodoutt.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tierra Firme is back up in 473d37b.


text:
🛑 Nodo UTT Ramos Mejia is down

In a8d9866, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in 3673f33.


text:
🛑 Almacén BioPandora is down

In a5cc926, Almacén BioPandora (https://www.biopandora.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén BioPandora is back up in c1d82f9.


text:
🛑 Almacén BioPandora is down

In a275909, Almacén BioPandora (https://www.biopandora.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén BioPandora is back up in ee65c2f.


text:
🛑 Tierra Firme is down

In 34cfe86, Tierra Firme (https://www.tierrafirmenodoutt.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tierra Firme is back up in 9cc655c.


text:
Ошибка в решении задачи №1 варианта от 9 июня 2013 года

Ошибка в одном  знаке. Правильный ответ -

в чем можно убедиться непосредственно.

Почему? a_1 должен быть равен 1, а не 1/2.

Да, меня что-то переклинило, сорри)

authors: dqdp efiminem

repo: efiminem/supershad


text:
🛑 CDN-Mikrotik-2 is down

In f4c67ec, CDN-Mikrotik-2 (http://118.179.50.70) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CDN-Mikrotik-2 is back up in 3f74049 after 49 minutes.


text:
🛑 CDN-Mikrotik-2 is down

In 0eb6f66, CDN-Mikrotik-2 (http://118.179.50.70) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CDN-Mikrotik-2 is back up in ad4217b after 30 minutes.


text:
Variant type 2 (vt: 2) has to be implemented

GlorpInt2Test

This is solved in this PR https://github.com/tesonep/pharo-com/pull/10

PR merged, this issue can ble closed.

authors: eMaringolo eftomi

repo: eftomi/pharo-ado


text:
I created firebase but I don't know how to create music.

I created firebase but I don't know how to create music.

Daily Songs with Firestore

How to create firestore database for daily songs?

repo: eggsy/website


text:
This site hackcss.egoist.moe can’t be reached

Hi,
This site hackcss.egoist.moe can’t be reached :(
Best,
Kokiro

Hi @Kokiro,
today I tried to restore the website with the style guidelines: https://hackcssbckp.herokuapp.com/
hope it helps! 😀

According to CNAME at github-pages the working address is hackcss.egoist.sh

authors: Kokiro mugiwarafx onjin

repo: egoist/hack


text:
Applying egg to SSA-based IRs

Hi! What are the prospects of utilizing egg to perform rewrite-driven transformations on SSA-based IRs (?)
I read this paper (whose authors appear to be collaborators with y'all): https://www.cs.cornell.edu/~ross/publications/eqsat/ where they describe E-PEG-based program representation.
On the other hand, I'm working on IRs which are closer to strict SSA (where all control flow is de-sugared to basic blocks and branching) and everything is linear (e.g. blocks are vectors of instructions) vs. strictly tree-like.
I'd love to find or understand how equality saturation could be applied to this representation structure -- it's likely that maybe this information can be gleaned from the above paper (but I expect that maintainers here might be able to unpack this more than I can).

Hi! I use egg for a language which is mostly-SSA. In my case, things "just work" so far because I mostly care about straight line blocks. The only additional information I track which may be necessary for other SSA-based usages as well is to make sure you don't use variables before they are defined. This, in my case, was possible with a simple e-class analysis.

Hi, I think @chandrakananandi is right. I don't think there is any major technical blocker stopping you from doing this today!
The original eqsat paper you linked to contains a lot of good ideas on how to encode your problem into an e-graph. If I'm understanding your setting, you'll still want E-PEGs if you want to encode loops in a transparent way that you can optimize through. If you only care about optimizing one basic block (one DFG) at a time, then you don't need them.
The egg paper (and tool) are mostly innovating in how equality saturation is done. How you encode your problem is still up to you!
Despite there not being any huge blockers, I still think it's a large and challenging task, and one that I'd like to try to tackle at some point (if I can find the time), or see someone else take a stab at!
One thing that I will add: you'll have a much easier time with a tree- or dag-like IR that a linear, mutating IR. All the rewrites that you do are over trees or dags, and just overall the e-graph doesn't do a lot for you if your language is heavily sequential. If that's your case, consider building def-use chains or some other method to make things more graph-like for the e-graph.

Also, this doesn't seem to be an issue, so I'm converting it to a discussion.

authors: chandrakananandi femtomc mwillsey

repo: egraphs-good/egg


text:
An extra bottom-up recursive extractor

Hi,
Before I saw #8 I made a a recursive extractor, too.
This code is much ugglier than #8, but is faster on some problems (for example acyclic graphs). On acyclic graphs it's able to extract in one pass through, without building the dependencies.
Taking the cumulative times for all three extractors on my machine:
Loaded 454 jsons.
...
Cumulative time for bottom-up: 3386ms
Cumulative time for bottom-up-analysis: 2483ms
Cumulative time for bottom-up-recursive: 977ms

bottom-up is the one currently in,
bottom-up-analysis is #8,
bottom-up-recursive is this PR.
Is there benefit in having all three, or should the two new ones be combined?

Good question! @Bastacyclop what do you think? Offhand, I'm leaning toward fewer, more distinct algorithms, so unless we can characterize that these have different advantages, I'd prefer to have just one.

Running the benchmarks with my plot.py version gives:
Loaded 675 jsons.
---- output/babble -- bottom-up results:
tree        mean: 383.4740
dag         mean: 202.1272
micros      mean: 4099.8324
tree   quantiles:    38.00, 201.00, 368.00, 531.00, 1138.00
dag    quantiles:    31.00, 124.50, 199.00, 266.50, 476.00
micros quantiles: 145.00, 1710.50, 3735.00, 5617.50, 16994.00
---- output/babble -- bottom-up-analysis results:
tree        mean: 383.4740
dag         mean: 202.1618
micros      mean: 9924.3410
tree   quantiles:    38.00, 201.00, 368.00, 531.00, 1138.00
dag    quantiles:    31.00, 124.50, 199.00, 266.50, 476.00
micros quantiles: 293.00, 3834.50, 9014.00, 13213.50, 34602.00
---- output/babble -- bottom-up-recursive results:
tree        mean: 383.4740
dag         mean: 202.1272
micros      mean: 6283.2775
tree   quantiles:    38.00, 201.00, 368.00, 531.00, 1138.00
dag    quantiles:    31.00, 124.50, 199.00, 266.50, 476.00
micros quantiles: 173.00, 2303.50, 5119.00, 8275.50, 25213.00

---- output/egg -- bottom-up results:
tree        mean: 3.7143
dag         mean: 3.2857
micros      mean: 7137.1071
tree   quantiles:    1.00, 1.00, 3.00, 6.00, 13.00
dag    quantiles:    1.00, 1.00, 3.00, 5.00, 13.00
micros quantiles: 12.00, 20.50, 57.00, 463.25, 148309.00
---- output/egg -- bottom-up-analysis results:
tree        mean: 3.7143
dag         mean: 3.2857
micros      mean: 16172.1786
tree   quantiles:    1.00, 1.00, 3.00, 6.00, 13.00
dag    quantiles:    1.00, 1.00, 3.00, 5.00, 13.00
micros quantiles: 19.00, 50.25, 88.00, 861.75, 317778.00
---- output/egg -- bottom-up-recursive results:
tree        mean: 3.7143
dag         mean: 3.2857
micros      mean: 9666.6786
tree   quantiles:    1.00, 1.00, 3.00, 6.00, 13.00
dag    quantiles:    1.00, 1.00, 3.00, 5.00, 13.00
micros quantiles: 13.00, 29.00, 78.50, 693.75, 183555.00

---- output/flexc -- bottom-up results:
tree        mean: 322.0000
dag         mean: 85.0000
micros      mean: 50959.7857
tree   quantiles:    89.00, 92.00, 404.50, 546.00, 546.00
dag    quantiles:    35.00, 37.00, 91.50, 137.00, 137.00
micros quantiles: 30125.00, 33549.75, 54544.50, 58975.50, 102810.00
---- output/flexc -- bottom-up-analysis results:
tree        mean: 322.0000
dag         mean: 84.4286
micros      mean: 43439.8571
tree   quantiles:    89.00, 92.00, 404.50, 546.00, 546.00
dag    quantiles:    35.00, 36.00, 91.50, 136.00, 137.00
micros quantiles: 28394.00, 31866.75, 44750.00, 49550.25, 79446.00
---- output/flexc -- bottom-up-recursive results:
tree        mean: 322.0000
dag         mean: 85.0000
micros      mean: 36553.7857
tree   quantiles:    89.00, 92.00, 404.50, 546.00, 546.00
dag    quantiles:    35.00, 37.00, 91.50, 137.00, 137.00
micros quantiles: 26775.00, 30454.50, 35102.00, 38385.25, 73826.00

---- output/tensat -- bottom-up results:
tree        mean: 1858437671761.2795
dag         mean: 5.9862
micros      mean: 737891.6000
tree   quantiles:    2.69, 4.32, 966.23, 2320915813054.39, 9300713475693.02
dag    quantiles:    0.82, 0.94, 4.41, 8.35, 18.81
micros quantiles: 869.00, 22696.25, 230507.50, 1727811.50, 2385394.00
---- output/tensat -- bottom-up-analysis results:
tree        mean: 1858437671761.2795
dag         mean: 5.9793
micros      mean: 584151.0000
tree   quantiles:    2.69, 4.32, 966.23, 2320915813054.39, 9300713475693.02
dag    quantiles:    0.82, 0.94, 4.41, 8.34, 18.80
micros quantiles: 495.00, 18215.00, 143353.50, 1247708.75, 2311130.00
---- output/tensat -- bottom-up-recursive results:
tree        mean: 1858437671761.2795
dag         mean: 5.9916
micros      mean: 69755.5000
tree   quantiles:    2.69, 4.32, 966.23, 2320915813054.39, 9300713475693.02
dag    quantiles:    0.82, 0.94, 4.41, 8.36, 18.84
micros quantiles: 168.00, 10949.75, 54289.00, 69088.25, 349218.00

tree costs are basically the same, as expected.
bottom up recursive is faster than bottom up analysis for all datasets, in particular for tensat: is this only from skipping building dependencies or is there more going on?

I feel like we should be able to combine the three bottom up versions, with some more experiments and code cleanup. Maybe by (1) doing a first pass without building dependencies; and (2) if dependencies are used, doing a bottom up analysis based on unique queues. The question would be whether using unique queues for the second stage brings performance benefits or not (I think it should: https://github.com/egraphs-good/egg/issues/239). To properly evaluate that I would like to see datasests with more costly to compute, child-dependent cost functions.

PS: one thing to consider is that in egg the dependencies don't need to be computed as they are already stored in the e-graph.

I would like to consider computation of dependencies (parents) as somewhat negligible, as its only linear and as @Bastacyclop says it's already there in many contexts.
I'd like to preserve the "dumb" bottom up extractor as a base case. Ideally, we could consolidate the "smarter" bottom-up extractors into one (i.e., those that do not aim to do cost sharing, as a possible definition). Thoughts on that?

Before I read this closely I also worked on a bottom-up extractor (#20)
Sorry for duplicated work! I would also be happy with consolidating this, #20, and #8 if possible.

With the recent changes to the bottom-up extractor(#20), there's now only a small time advantage for the extractor that I proposed introducing (Note these times differ from before because extra problems have been added). Currently:
Cumulative time for faster-bottom-up: 2060ms [The one in #20]
Cumulative time for bottom-up-recursive: 1533ms [The one in this PR].
Cumulative time for bottom-up: 4471ms
Meaning that the extractor in this PR is only about 25% faster than the others, but is much uglier.
However, there are some tweaks to the "faster-bottom-up" extractor which brings down its runtime to almost the same as the extractor in this PR:
###################################################
faster-bottom-up vs faster-bottom-up-old

extractors: ['faster-bottom-up', 'faster-bottom-up-old']
cumulative time for faster-bottom-up: 1649ms
cumulative time for faster-bottom-up-old: 2060ms
cumulative tree cost for faster-bottom-up: 18584377265237
cumulative tree cost for faster-bottom-up-old: 18584377265237
cumulative dag cost for faster-bottom-up: 78037
cumulative dag cost for faster-bottom-up-old: 78037
Cumulative time for faster-bottom-up: 1649ms
Cumulative time for faster-bottom-up-old: 2060ms
faster-bottom-up / faster-bottom-up-old
geo mean
tree: 1.0000
dag: 1.0000
micros: 0.8184
quantiles
tree:   1.0000, 1.0000, 1.0000, 1.0000, 1.0000
dag:    1.0000, 1.0000, 1.0000, 1.0000, 1.0000
micros: 0.3611, 0.7825, 0.8227, 0.8611, 1.8333

So I've changed this PR to now just introduce some small speedups to the faster-bottom-up extractor, as well as fixing up attribution to @Bastacyclop.

:+1:

authors: Bastacyclop TrevorHansen mwillsey oflatt

repo: egraphs-good/extraction-gym


text:
OffHeapChainMap thieving argument is ignored

OffHeapChainMap is backed by EvictionListeningReadWriteLockedOffHeapClockCache but the latter lacks a constructor that accepts shareByThieving argument.
The offheap store lib should be modified to add such constructor so that OffHeapChainMap can make use of it.

Given how busted ARC is at the moment this turns out to be a non-issue. That said @AbfrmBlr is going to fixing the broken ARC implementation in clustered (that he wrote) and extending it to cover unclustered offheap and disk. He's going to run headlong in to this as a result.

This will be fixed under #2215

authors: chrisdennis lorban


text:
ehrbase/project_management#98 added ACTION examples and updated AQL test suite data

@testautomation this includes the action compositions and the queries were updated too.

:heavy_check_mark:

authors: ppazos testautomation

repo: ehrbase/ehrbase


text:
glaceful close ssl socket

Hi: @eidheim
    void close() noexcept {
        error_code ec;
        std::unique_lock<std::mutex> lock(socket_close_mutex); // The following operations seems to be needed to run sequentially
        socket->lowest_layer().shutdown(asio::ip::tcp::socket::shutdown_both, ec);
        socket->lowest_layer().close(ec);
      }

In this way, we directly close tcp socket, why we not close SSL socket first in HTTPS server?
Thank you.

Last time I studied this I came to the conclusion that calling ssl::stream::shutdown was not needed. Though I might be wrong! By the way, ssl::stream does not have a close-member function.

Although, thank you for bringing this up. I'll add a couple of labels to this issue.

@eidheim  In a rare case, If I don't add mutex before shutdown/close,  Segment error happen. Why you choose use mutex before shutdown/close?

authors: eidheim lxlenovostar

repo: eidheim/Simple-Web-Server


text:
Use latest pickle protocol

See also #51

Closed in favour of #51

repo: eigenein/iftttie


text:
Reorder parameters within functions

Fixes #141

Really great contribution @alpeshjamgade . Thanks
I would be reviewing in a day or two. Meanwhile could you make one change.
define a private function _scr(M, c=default value, G=default value for calculating Rs. Putting units for calculating Rs seems unnecessary and slow, and may cause problems while implementing jit for the functions.
Also, I guess you have made some merge commits while rebasing your branch. Try to fix that. Maybe refer https://github.com/k88hudson/git-flight-rules/ .
One word of advice, try to create separate branches for fixing and developing things. The master should not ever diverge from the upstream. Believe me, I have learnt that the hard way.

Really great contribution @alpeshjamgade . Thanks
I would be reviewing in a day or two. Meanwhile could you make one change.
define a private function _scr(M, c=default value, G=default value for calculating Rs. Putting units for calculating Rs seems unnecessary and slow, and may cause problems while implementing jit for the functions.
Also, I guess you have made some merge commits while rebasing your branch. Try to fix that. Maybe refer https://github.com/k88hudson/git-flight-rules/ .
One word of advice, try to create separate branches for fixing and developing things. The master should not ever diverge from the upstream. Believe me, I have learnt that the hard way.

thank you
you asked me to define a private function _scr.
Before the schwarzschild_radius function in schwarzschid_utils.py  was getting any M value as input weather it has astropy unit or not  and return Rs in astropy units and also 'Rs' was the input to the most functions which was in astropy units only, but  when i changed Rs with "M", i needed to make sure that "M" should be in astropy units , that means everytime i call such function i need to provide M value in astropy units otherwise it would throw an error, and we dont expect users to provide M in astropy units, it would be great if they can just give M value as input and if the given function need to calculate Rs, it would need M in astropy units then schwarzschild_radius function will convert M to astropy units, thast just  what i did. please tell me if i can do any better.

i think we dont need private  _scr function, if we want Rs in floats we can just asked for it with command Rs.value , otherwise it will always be in astropy units. please tell me if i dont understand something.

i think we dont need private _scr function, if we want Rs in floats we can just asked for it with command Rs.value , otherwise it will always be in astropy units. please tell me if i dont understand something.

User always specifies things with units, but during heavy calculation internally, we don't use units. As functions like christoffels() are called thousands of time in a loop to get the trajectory it may be good to save some computation by not using astropy.units. But still wait some time, I am not sure what to do. @shreyasbapat Suggestions??

i have just created another pull request #196 for this issue , this time i didnt messed up my master. sorry for this. i did not consider on which branch i was making changes before.

authors: alpeshjamgade ritzvik

repo: einsteinpy/einsteinpy


text:
Revert workaround for micrometer bug in tests

#3187 added a workaround for a micrometer bug. We should revert this workaround as soon as a micrometer version with a fix is available.

fixed in https://github.com/elastic/apm-agent-java/pull/3264

authors: JonasKunz jackshirazi

repo: elastic/apm-agent-java


text:
Update to Elasticsearch 0.90.3

Issue reported in https://groups.google.com/d/msg/elasticsearch/bpdetIvIg5M/cMAUGwhRVf0J
No problem with elasticsearch 0.90.2 and the cloud-aws 1.12.0 plugin (other than the usual node discovery flakiness), but I'm unable to get elasticsearch 0.90.3 to start:
Initialization Failed ...
1) IllegalStateException[This is a proxy used to support circular references involving constructors. The object we're proxying is not constructed yet. Please wait until after injection has completed to use this object.]2) NoSuchMethodError[org.elasticsearch.discovery.zen.ZenDiscovery.<init>(Lorg/elasticsearch/common/settings/Settings;Lorg/elasticsearch/cluster/ClusterName;Lorg/elasticsearch/threadpool/ThreadPool;Lorg/elasticsearch/transport/TransportService;Lorg/elasticsearch/cluster/ClusterService;Lorg/elasticsearch/node/settings/NodeSettingsService;Lorg/elasticsearch/cluster/node/DiscoveryNodeService;Lorg/elasticsearch/discovery/zen/ping/ZenPingService;)V]

Do I need to wait for a new version of cloud-aws, or is there some other problem here?
My /etc/elasticsearch/elasticsearch.yml:
cluster.name: foo

plugin.mandatory: cloud-aws,lang-javascript

cloud:
    aws:
        access_key: ********
        secret_key: ********
        region: us-east-1

discovery:
    type: ec2
    ec2:
        ping_timeout: 15s

gateway:
    type: s3
    s3:
        bucket: bar

For anyone (like me) who is seeing this error, my fix was to update to the correct version (as indicated by the README) - I accidentally updated Elasticsearch to 1.5.0 without updating elasticsearch-cloud-aws.

@jacobwgillespie ha, thanks for pointing this out, I did the same thing!

I just ran into this issue today, and it had nothing to do with mis-matched ES/Plugin versions. This error is also thrown if your config values for the cloud-aws plugin are not correct.
What I had:
cloud:
  aws:
    access_key: XXX
    secret: XXX
    region: us-east-1

What I needed:
cloud:
  aws:
    access_key: XXX
    secret_key: XXX
    region: us-east-1

The major difference between the two of them being cloud.aws.secret in the first, non-working example; which is changed to cloud.aws.secret_key in the second, working example.
So, apparently, this exact same error is what you'll get if you've completely borked your cloud-aws config. So, keep that in mind!
Maybe in a future release, if you could detect a bad config state like this (access key is present, but secret key is missing) and throw an error, that would be pretty great. Alternatively, implementing it so that an error is thrown if any unknown string appears in the cloud.aws namespace would work just as well (so, an error would have been thrown because cloud.aws.secret is not a recognized and valid key), but I don't know how feasible that is to do. Just some food for thought!
Hopefully someone finds this useful!

@hjc1710 I think it's useful and I agree that we should better catch that kind of error.
May be you would like to open an issue in elasticsearch repo now that we moved aws plugin there?
Thanks!

Awesome, thanks @dadoonet! I did not know that this plugin had moved and the official repo is elastic/elasticsearch now. Anyway, I opened up an issue there for this very feature, after doing a bit of rewording and thinking. If you guys need my help for that feature (for whatever reason), I'm happy to help!

authors: dadoonet hjc1710 jacobwgillespie rabidscorpio

repo: elastic/elasticsearch-cloud-aws


text:
Adding search_analyzer to mapping

I can't figure out how to add the search_analyzer option to the mapping block. The Mappings class only provides indexes as a way to add fields.
https://www.elastic.co/guide/en/elasticsearch/reference/current/search-analyzer.html

My bad, documentation parsing error from my side.

repo: elastic/elasticsearch-rails


text:
elasticsearch.keystore: Device or resource busy

Chart version: 8.5.1
Kubernetes version: 1.23.12-gke.1600
Kubernetes provider:  GKE (Google Kubernetes Engine)
Helm Version: version.BuildInfo{Version:"v3.9.3", GitCommit:"414ff28d4029ae8c8b05d62aa06c7fe3dee2bc58", GitTreeState:"clean", GoVersion:"go1.19"}

Describe the bug:
Exception in thread "main" java.nio.file.FileSystemException: /usr/share/elasticsearch/config/elasticsearch.keystore.tmp -> /usr/share/elasticsearch/config/elasticsearch.keystore: Device or resource busy
Steps to reproduce:

Create the secret

kubectl create secret generic elk-backup --from-file=gcs.client.elk-backup.credentials_file=./elk-backup.json

To add these secrets to the keystore:

keystore:
  - secretName: elk-backup

Expected behavior:
mount the secret in keystore should work
Provide logs and/or server output (if relevant):
Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting
Exception in thread "main" java.nio.file.FileSystemException: /usr/share/elasticsearch/config/elasticsearch.keystore.tmp -> /usr/share/elasticsearch/config/elasticsearch.keystore: Device or resource busy
at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:100)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
at java.base/sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:420)
at java.base/sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:266)
at java.base/java.nio.file.Files.move(Files.java:1430)
at org.elasticsearch.common.settings.KeyStoreWrapper.save(KeyStoreWrapper.java:498)
at org.elasticsearch.common.settings.KeyStoreWrapper.save(KeyStoreWrapper.java:412)
at org.elasticsearch.cli.keystore.AddStringKeyStoreCommand.executeCommand(AddStringKeyStoreCommand.java:102)
at org.elasticsearch.cli.keystore.BaseKeyStoreCommand.execute(BaseKeyStoreCommand.java:64)
at org.elasticsearch.common.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:54)
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:85)
at org.elasticsearch.cli.MultiCommand.execute(MultiCommand.java:94)
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:85)
at org.elasticsearch.cli.Command.main(Command.java:50)
at org.elasticsearch.launcher.CliToolLauncher.main(CliToolLauncher.java:64)

Any additional context:
I can seeing this error in pod with role master

I'm not sure but maybe it's because the keystore file is mounted as a subpath in the chart
- name: keystore
  mountPath: /usr/share/elasticsearch/config/elasticsearch.keystore
  subPath: elasticsearch.keystore

I don't know how elasticsearch-keystore tool works but it looks like it's trying to replace elasticsearch.keystore file by elasticsearch.keystore.tmp file instead of replacing the content of it.
I reproduce the issue by trying to do the following command:
mv elasticsearch.keystore.tmp elasticsearch.keystore
mv: cannot move 'elasticsearch.keystore.tmp' to 'elasticsearch.keystore': Device or resource busy

cp command works just fine
cp elasticsearch.keystore.tmp elasticsearch.keystore

I see 2 possibilities to fix that:

change the way elasticsearch-keystore write content in keystore file
add the possibility to specify a custom path for the keystore file and mount it in is own directory to prevent the use of subpath

Hi @TanguyPatte

seems like there is something wrong with the current statefulset.yaml that causes this issue.
FWIW deploying with this template works well for elasticsearch 8.6.2 : https://github.com/elastic/helm-charts/blob/d4e9f6bc47cf7f7ad4dfaaec102e1327d8a345e3/elasticsearch/templates/statefulset.yaml
but there may be more recent iterations that may work.

Chart version: 8.5.1
Kubernetes version: 1.23.12-gke.1600
Kubernetes provider: GKE (Google Kubernetes Engine)
Helm Version: version.BuildInfo{Version:"v3.9.3", GitCommit:"414ff28d4029ae8c8b05d62aa06c7fe3dee2bc58", GitTreeState:"clean", GoVersion:"go1.19"}
Describe the bug: Exception in thread "main" java.nio.file.FileSystemException: /usr/share/elasticsearch/config/elasticsearch.keystore.tmp -> /usr/share/elasticsearch/config/elasticsearch.keystore: Device or resource busy
Steps to reproduce:

Create the secret

kubectl create secret generic elk-backup --from-file=gcs.client.elk-backup.credentials_file=./elk-backup.json

To add these secrets to the keystore:

keystore:
  - secretName: elk-backup

Expected behavior: mount the secret in keystore should work
Provide logs and/or server output (if relevant):
Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting
Exception in thread "main" java.nio.file.FileSystemException: /usr/share/elasticsearch/config/elasticsearch.keystore.tmp -> /usr/share/elasticsearch/config/elasticsearch.keystore: Device or resource busy
at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:100)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
at java.base/sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:420)
at java.base/sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:266)
at java.base/java.nio.file.Files.move(Files.java:1430)
at org.elasticsearch.common.settings.KeyStoreWrapper.save(KeyStoreWrapper.java:498)
at org.elasticsearch.common.settings.KeyStoreWrapper.save(KeyStoreWrapper.java:412)
at org.elasticsearch.cli.keystore.AddStringKeyStoreCommand.executeCommand(AddStringKeyStoreCommand.java:102)
at org.elasticsearch.cli.keystore.BaseKeyStoreCommand.execute(BaseKeyStoreCommand.java:64)
at org.elasticsearch.common.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:54)
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:85)
at org.elasticsearch.cli.MultiCommand.execute(MultiCommand.java:94)
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:85)
at org.elasticsearch.cli.Command.main(Command.java:50)
at org.elasticsearch.launcher.CliToolLauncher.main(CliToolLauncher.java:64)

Any additional context: I can seeing this error in pod with role master

@SashaShcherbyna
I have got the same error, Did you have a solution to resolve this issue?

I can resolve this issue because I have not set ELASTIC_PASSWORD with my own credential.
Just add
extraEnvs:
  - name: ELASTIC_PASSWORD
    valueFrom:
      secretKeyRef:
        name: elastic-config-credentials
        key: password

secret:
  enabled: false

and then add the keystore just normal.

authors: Drookoo SashaShcherbyna TanguyPatte adrifermo ppatcha

repo: elastic/helm-charts


text:
fix: close fd after debug logs are written

fix #110
runner end should be called after reset since we are logging the output inside reset
Moved from nextTick to setTimeout as its called after all the micro tasks and ensure all log statements are printed before we end stream.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: [Pull request #112 opened]

Start Time: 2020-10-29T16:43:01.167+0000

Duration: 14 min 22 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
42

Skipped
0

Total
42

authors: apmmachine vigneshshanmugam

repo: elastic/synthetics


text:
Fix 2 errors

fix an import typo
add a missing exception definition

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@gongweibao please review this pr, thanks~

@gongweibao please review this pr, thanks~

authors: CLAassistant Ruminateer tizhou86

repo: elasticdeeplearning/edl


text:
How to cite this work in my assignment?

Thank you for your work and may I know how should I cite your works in my project?

这里已经写好了构建的


text:
Set the docker image tag to run

This pull request makes possible to run a specific Home Assistant docker image tag sending a variable to the script. If the variable is not sent, the version included in .hass/config/.HA_VERSION file will be used as the tag. Also, to generate the docker cache key, the aforementioned file will be used instead of the package.json.

coverage: 100.0%. remained the same
when pulling b723a4b7d1ede517f74d010d5fef0427c01cad17 on run_docker_image_tag_dynamic
into ebd6f452dca960044803e08becec7c7e2efbfd39 on master.

authors: coveralls elchininet

repo: elchininet/keep-texts-in-tabs


text:
🛑 Instagram is down

In 5d4c8f1, Instagram (https://www.instagram.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Instagram is back up in dc19a67.

repo: eldikra/monitoreo


text:
🛑 Instagram is down

In 3cdf44f, Instagram (https://www.instagram.com) was down:

HTTP code: 429
Response time: 371 ms

Resolved: Instagram is back up in fa90aaf.


text:
[Feature Request] Add Deploy to Heroku button to README.md

Feature Request
Hi there! Great application! I really love how simple and privacy focused it is.
It would be great to have a Deploy to Heroku button, would help drive up adoption!
Documentation

A "Deploy to Heroku" button would be cool, but I guess that #73 should be finished first. Help is welcome!

Will be part of v1.4.3.

repo: electerious/Ackee


text:
Feature request: make the auto-fullscreen behaviour configurable

In PR #583, a new behaviour was introduced that would cause the picture to switch to fullscreen if the viewer didn't move his mouse for >=1 second.
In my case, I need people (elderly relatives) to always see the top bar with the title. I have for now achieved that for myself by commenting out the relevant part from that PR in view.js, but it would be nicer if there was a config switch in the DB to turn the auto-fullscreen off. Notably I wouldn't have to redo this after every update and rebuild lychee.

+1 for that, also being able to adjust that 1 second delay would be nice.

A setting isn't planned, but we could increase the delay. I agree that 1 second might be too fast for some users.

The next version will use a 2.5s delay. 1 second was too aggressive.

authors: electerious jullit31 mhellwig

repo: electerious/Lychee


text:
Listener warning

I have a view with a lot of small components that all have a small query listening for updates to their specific object — which should be a supported use case I'd assume? Or if there is an actual limit you want to warn against, set it to that. But I'm assuming the eventemitter is just set to the default (11 I think).

Looking at the notifier code under src/notifiers/event.ts, we have the following:
// Global singleton that all event notifiers use by default. Emitting an event
// on this object will notify all subscribers in the same thread. Cross thread
// notifications use the `./bridge` notifiers.
const globalEmitter = new EventEmitter()

// Increase the maximum number of listeners because multiple components
// use this same emitter instance.
globalEmitter.setMaxListeners(250)

This limit was increased to 250 by @thruflo int https://github.com/electric-sql/electric/pull/377 - since this is a global emitter I find it hard to think of any reasonable way to adjust this limit for a large application while still retaining the ability to detect if listeners are being accumulated or not appropriately removed. Maybe removing this warning and checking if many listeners are being added in the same "place", or having them be identified somehow could help construct a better warning.
For your particular case, would a "parent" component with view-only children work as well or would it complicate the code too much?

Yeah I'm sure I could refactor — I think ideally though the subscriptions are efficient enough it's not necessary.

I haven't noticed any slowdowns with the app & memory is fine — though all these listeners are to objects that are rarely changed. So what exactly is the upper limit is pretty arbitrary depending on what's updating in your app.

@samwillis what's your take on this? I think it makes sense to remove the warning altogether as we explicitly use a global emitter - if we want to catch leaks we can implement our own tests or mechanisms from within our EventNotifier to catch them.

authors: KyleAMathews msfstef

repo: electric-sql/electric


text:
PGliteWorker not working with drizzle

OS: windows 11
Browser: chrome 127.0.6533.119
framework: solid-start
The minimal reproduction repository: GitHub Repo Link
description:
I am using PGliteWorker with drizzle. I followed the instructions on https://pglite.dev/docs/multi-tab-worker to create a worker wrapper:
PGliteWorker.ts
worker({   async init() {     const pg = await PGlite.create({...});     await pg.exec(...);     const db = drizzle(pg, { schema });     const ret = await db.query.verification_token.findMany();     console.log(ret);     return pg;   }, });
I can see the results in the browser console.
However, if I
entry-client.tsx
const pg = await PGliteWorker.create(   new Worker(PGliteWorkerUrl, {     type: "module",   }) ); const db = drizzle(pg, { schema }); const ret = await db.query.verification_token.findMany(); console.log(ret);
The browser console gives the following error:
Uncaught DOMException: Failed to execute 'postMessage' on 'BroadcastChannel': value => value could not be cloned.
at j.g (http://localhost:3001/_build/node_modules/.pnpm/@electric-sql+pglite@0.2.0/node_modules/@electric-sql/pglite/dist/worker/index.js?v=c34c2280:201:21)
at j.query (http://localhost:3001/_build/node_modules/.pnpm/@electric-sql+pglite@0.2.0/node_modules/@electric-sql/pglite/dist/worker/index.js?v=c34c2280:98:56)
at async PglitePreparedQuery.execute (http://localhost:3001/_build/node_modules/.vinxi/client/deps/drizzle-orm_pglite.js?v=d787a4e7:58:20)
at async http://localhost:3001/_build/@fs/D:/ToramCalculator/src/entry-client.tsx:16:13

I've experienced this issue as well when trying to write to the DB with drizzle. My read queries were working. I wonder if this issue is an issue with drizzle

The Failed to execute 'postMessage' on 'BroadcastChannel' error makes me think it could be our side as we use a BroadcastChannel to communicate with the worker. It's either:

drizzle is trying to pass an un-cloneable object as a parameter to the query api.
or we have something in our api that doesn't work with the worker and is not currently covered by the tests.
or both, which is my suspicion:

I'm 99% sure we will find it's the parser query option (https://pglite.dev/docs/api#query-options) and will need a bit of a refactor.

The issue seems to be that we are trying to transfer ParserOptions which contains anonymous functions to the worker without proper serialization.
Either the parsing is done at the calling thread (and the ParserOptions are stored and handled there) or we assume some limitations on the functions being passed and serialize them and deserialize them to run in the worker (e.g. with a toString()/eval() combination).
Since these parsers might depend on various imports and what not it might be better to handle deserialization in the caller.

authors: KiaClouth TheAndrewJackson msfstef samwillis

repo: electric-sql/pglite


text:
[BUG] Cost data is wrongly mapped into Budget graphs

Current Situation
Having this cost data in November

The data is shown in the Budget Graphs in Januaray

Desired
Data of November should be shown in November also on Budget-Chart

I just debugged this screen myself.
The cost data is passed into the BudgetChart component as an array of monthly costs here: https://github.com/electrolux-oss/infrawallet/blob/main/plugins/infrawallet/src/components/Budgets/Budgets.tsx#L250
    "id": "AWS",
    "reports": {
        "2023-12": 19.6492511966,
        "2024-01": 1939.0336325847002,
        "2024-02": 1610.1251975480995,
        "2024-03": 2149.6599309432,
        "2024-04": 2629.0959797089004,
        "2024-05": 2603.6509832689,
        "2024-06": 2438.023622028399,
        "2024-07": 2767.510390127999,
        "2024-08": 9312.452064800302,
        "2024-09": 8760.504147668702,
        "2024-10": 10055.072295576203,
        "2024-11": 5529.263631147701
    }
}

It's then converted to a running sum here: https://github.com/electrolux-oss/infrawallet/blob/main/plugins/infrawallet/src/components/Budgets/Budgets.tsx#L91-L98
{
    0: 19.6492511966,
    1: 1958.6828837813002,
    2: 3568.8080813294,
    3: 5718.4680122726,
    4: 8347.5639919815,
    5: 10951.214975250401,
    6: 13389.2385972788,
    7: 16156.748987406798,
    8: 25469.2010522071,
    9: 34229.7051998758,
    10: 44284.77749545201,
    11: 49814.04112659971
}

This is then plotted on the chart, with a constant set of x-axis titles: https://github.com/electrolux-oss/infrawallet/blob/main/plugins/infrawallet/src/components/Budgets/Budgets.tsx#L122
xAxis={[
          {
            data: ['Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'],
            scaleType: 'band',
          },
        ]}

I think that the x-axis labels just need to be dynamically generated by mapping the keys from the original report variable to the month names.

@tollercode @darylgraham Can you check if version 0.2.0-20241118212048-4e21a4a works for you?

authors: darylgraham emillg tollercode

repo: electrolux-oss/infrawallet


text:
npm start did not open the app

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
I followed the instruction on https://github.com/electron-userland/electron-forge and start a demo project my-app, but when I run npm start, it didn't open the electron. It did stop on "electron-squirrel-startup processing squirrel command .".

Console output when you run electron-forge with the environment variable DEBUG=electron-forge:*. (Instructions on how to do so here). Please include the stack trace if one exists.
Put the console output here

D:\code\electron\my-app>npm start

> my-app@1.0.0 start D:\code\electron\my-app
> electron-forge start

√ Checking your system
√ Locating Application
√ Preparing native dependencies
√ Launching Application

D:\code\electron\my-app>npm start -v
6.4.1

D:\code\electron\my-app>set DEBUG=*

D:\code\electron\my-app>npm start

> my-app@1.0.0 start D:\code\electron\my-app
> electron-forge start

- Checking your system  electron-forge:check-system checking system, create ~/.skip-forge-system-check to stop doing this +0ms
√ Checking your system
- Locating Application  electron-forge:project-resolver searching for project in: D:\code\electron\my-app +0ms
  electron-forge:project-resolver electron-forge compatible package.json found in D:\code\electron\my-app\package.json +15ms
√ Locating Application
- Preparing native dependencies  electron-rebuild rebuilding with args: [Arguments] {
  '0':
   { buildPath: 'D:\\code\\electron\\my-app',
     electronVersion: '3.0.6',
     arch: 'x64' } } +0ms
  electron-rebuild rebuilding with args: D:\code\electron\my-app 3.0.6 x64 [] false https://atom.io/download/electron [ 'prod', 'optional' ] false +15ms
  electron-rebuild exploring D:\code\electron\my-app\node_modules\electron-squirrel-startup +4ms
  electron-rebuild exploring D:\code\electron\my-app\node_modules\debug +5ms
  electron-rebuild exploring D:\code\electron\my-app\node_modules\debug\node_modules\ms +5ms
  electron-rebuild exploring D:\code\electron\my-app\node_modules\ms +5ms
  electron-rebuild identified prod deps: Set { 'electron-squirrel-startup': true, debug: true, ms: true } +7ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules +11ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\@electron-forge +6ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\@electron-forge\async-ora\node_modules +5ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\@electron-forge\cli\node_modules +10ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\@electron-forge\core\node_modules +20ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\@electron-forge\installer-dmg\node_modules +12ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\@electron-forge\shared-types\node_modules +22ms
\ Preparing native dependencies  electron-rebuild scanning: D:\code\electron\my-app\node_modules\@types +11ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\@types\electron-packager\node_modules +5ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\@types\electron-packager\node_modules\@types +7ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\are-we-there-yet\node_modules +15ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\asar\node_modules +11ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\camelcase-keys\node_modules +27ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\concat-stream\node_modules +28ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\cross-spawn\node_modules +10ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\cross-zip\node_modules +4ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\debug\node_modules +8ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\decompress-zip\node_modules +6ms
| Preparing native dependencies  electron-rebuild scanning: D:\code\electron\my-app\node_modules\electron\node_modules +13ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\electron-download\node_modules +3ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\electron-osx-sign\node_modules +8ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\electron-packager\node_modules +7ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\electron-rebuild\node_modules +9ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\electron-winstaller\node_modules +11ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\electron-winstaller\node_modules\asar\node_modules +4ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\execa\node_modules +15ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\execa\node_modules\cross-spawn\node_modules +4ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\external-editor\node_modules +8ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\extract-zip\node_modules +3ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\find-up\node_modules +10ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\flora-colossus\node_modules +4ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\fstream\node_modules +14ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\galactus\node_modules +3ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\get-package-info\node_modules +13ms
/ Preparing native dependencies  electron-rebuild scanning: D:\code\electron\my-app\node_modules\global-prefix\node_modules +26ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\http-signature\node_modules +9ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\inquirer\node_modules +7ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\load-json-file\node_modules +32ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\mkdirp\node_modules +36ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\mksnapshot\node_modules +6ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\mksnapshot\node_modules\fs-extra\node_modules +9ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\node-abi\node_modules +8ms
- Preparing native dependencies  electron-rebuild scanning: D:\code\electron\my-app\node_modules\node-gyp\node_modules +11ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\normalize-package-data\node_modules +7ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\nugget\node_modules +4ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\ora\node_modules +13ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\path-type\node_modules +21ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\redent\node_modules +29ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\request\node_modules +3ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\run-async\node_modules +13ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\spawn-rx\node_modules +16ms
\ Preparing native dependencies  electron-rebuild scanning: D:\code\electron\my-app\node_modules\temp\node_modules +22ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\touch\node_modules +13ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\verror\node_modules +17ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\wide-align\node_modules +9ms
  electron-rebuild scanning: D:\code\electron\my-app\node_modules\yargs-parser\node_modules +16ms
√ Preparing native dependencies
√ Launching Application

Thu, 25 Oct 2018 03:28:11 GMT electron-squirrel-startup processing squirrel command `.`

What command line arguments are you passing?
Put the arguments here

What does your config.forge data in package.json look like?
Paste the config.forge JSON object here

Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
reproduce your problem. Using electron-forge init is a good starting point, if that is not the
source of your problem.

Hi, I have the same problem on Win 10 64bit.
I just started using electron, and electron-forge.  To reproduce, just start from scratch on a new machine and follow the electron-forge page.

After running those commands, there are a bunch of error messages and the app window never appears.
Separately, I was able to get the regular electron demo to work from their man page:

What version of Electron Forge is this?

If you are using node 11, then you should use electron 3.0.8 or newer.
see more details on https://github.com/electron/electron/pull/15470

If that's the issue, I'm inclined to close this as not a bug in Electron Forge.

@malept, @vic2r I tested it and confirmed what I guess.

Ok, thank you guys for resolving this issue for me.  I am still learning.
I am on node version 11.x.  I thought I was on electron 3.0.8.   When I install electron-forge and look the json package.json (there are many nested version under folders called "node_modules" it always says 2.0.8.  I've tried googling, and several commands to update electron inside my test projects.  I'm sure it's something simple, can either of you point me in the right direction?   How do I "use electron version 3.0.8 or newer"?
Thanks again to both of you.

repo: electron-userland/electron-forge