text:
Wicket error when accessing attendance tool in master experimental

Just added the attendance tool to the trunk nightly experimental instance (21.x) and am getting the following stack when accessing the tool:
`26-Nov-2019 12:15:43.486 WARN [http-nio-20213-exec-2] RequestCycleExtra.handleException Handling the following exception
org.apache.wicket.WicketRuntimeException: The component(s) below failed to render. Possible reasons could be that: 1) you have added a component in code but forgot to reference it in the markup (thus the component will never be rendered), 2) if your components were added in a parent container then make sure the markup for the child container includes them in wicket:extend.

[Component id = header-event-edit]

[Component id = header-print-links]
at org.apache.wicket.Page.checkRendering(Page.java:673)
at org.apache.wicket.Page.onAfterRender(Page.java:829)
at org.apache.wicket.markup.html.WebPage.onAfterRender(WebPage.java:224)
at org.apache.wicket.Component.afterRender(Component.java:918)
at org.apache.wicket.Component.render(Component.java:2306)
at org.apache.wicket.Page.renderPage(Page.java:1024)
at org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:139)
at org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:284)
at org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:175)
at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:890)
at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:426)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:712)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:459)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:352)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
at org.sakaiproject.tool.impl.ActiveToolComponent$MyActiveTool.forward(ActiveToolComponent.java:508)
at org.sakaiproject.portal.charon.SkinnableCharonPortal.forwardTool(SkinnableCharonPortal.java:1490)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doToolBuffer(SiteHandler.java:1241)
at org.sakaiproject.portal.charon.handlers.SiteHandler.bufferContent(SiteHandler.java:1075)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doSite(SiteHandler.java:498)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doGet(SiteHandler.java:274)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doGet(SiteHandler.java:162)
at org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:856)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:475)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:679)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:836)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1747)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
26-Nov-2019 12:15:43.488 WARN [http-nio-20213-exec-2] RequestCycleExtra.handleException ********************************
org.apache.wicket.WicketRuntimeException: The component(s) below failed to render. Possible reasons could be that: 1) you have added a component in code but forgot to reference it in the markup (thus the component will never be rendered), 2) if your components were added in a parent container then make sure the markup for the child container includes them in wicket:extend.

[Component id = header-event-edit]

[Component id = header-print-links]
at org.apache.wicket.Page.checkRendering(Page.java:673)
at org.apache.wicket.Page.onAfterRender(Page.java:829)
at org.apache.wicket.markup.html.WebPage.onAfterRender(WebPage.java:224)
at org.apache.wicket.Component.afterRender(Component.java:918)
at org.apache.wicket.Component.render(Component.java:2306)
at org.apache.wicket.Page.renderPage(Page.java:1024)
at org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:139)
at org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:284)
at org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:175)
at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:890)
at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:426)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:712)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:459)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:352)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
at org.sakaiproject.tool.impl.ActiveToolComponent$MyActiveTool.forward(ActiveToolComponent.java:508)
at org.sakaiproject.portal.charon.SkinnableCharonPortal.forwardTool(SkinnableCharonPortal.java:1490)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doToolBuffer(SiteHandler.java:1241)
at org.sakaiproject.portal.charon.handlers.SiteHandler.bufferContent(SiteHandler.java:1075)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doSite(SiteHandler.java:498)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doGet(SiteHandler.java:274)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doGet(SiteHandler.java:162)
at org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:856)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:475)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:679)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:836)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1747)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
26-Nov-2019 12:15:43.491 ERROR [http-nio-20213-exec-2] org.apache.wicket.DefaultExceptionMapper.mapUnexpectedExceptions Unexpected error occurred
org.apache.wicket.WicketRuntimeException: The component(s) below failed to render. Possible reasons could be that: 1) you have added a component in code but forgot to reference it in the markup (thus the component will never be rendered), 2) if your components were added in a parent container then make sure the markup for the child container includes them in wicket:extend.

[Component id = header-event-edit]

[Component id = header-print-links]
at org.apache.wicket.Page.checkRendering(Page.java:673)
at org.apache.wicket.Page.onAfterRender(Page.java:829)
at org.apache.wicket.markup.html.WebPage.onAfterRender(WebPage.java:224)
at org.apache.wicket.Component.afterRender(Component.java:918)
at org.apache.wicket.Component.render(Component.java:2306)
at org.apache.wicket.Page.renderPage(Page.java:1024)
at org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:139)
at org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:284)
at org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:175)
at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:890)
at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:426)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:712)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:459)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:352)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
at org.sakaiproject.tool.impl.ActiveToolComponent$MyActiveTool.forward(ActiveToolComponent.java:508)
at org.sakaiproject.portal.charon.SkinnableCharonPortal.forwardTool(SkinnableCharonPortal.java:1490)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doToolBuffer(SiteHandler.java:1241)
at org.sakaiproject.portal.charon.handlers.SiteHandler.bufferContent(SiteHandler.java:1075)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doSite(SiteHandler.java:498)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doGet(SiteHandler.java:274)
at org.sakaiproject.portal.charon.handlers.SiteHandler.doGet(SiteHandler.java:162)
at org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:856)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:475)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:679)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:836)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1747)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)`

I tested on my local trunk and can't replicate. LMK if you can still replicate

authors: kenaragon ottenhoff

repo: sakaicontrib/attendance


text:
SAM-2831 Create Student Audio Response question screen. Add Bootstrap

Changed display for large resolutions

how do you do so many PRs? :dancer: LGTM

source: gharchive/pull-request

authors: SedueRey alejandrogj

repo: sakaiproject/sakai

license_type: permissive

license_source: github-api


text:
SAK-29549 Now able to hide connections in roster

A new sakai.property has been added, roster_view_connections,
which when false will hide the Connections button in the roster
view. The property's default is true, though it will be false
if profile2.connections.enabled is also false (also see
SAK-29267 & SAK-29408).
Jira ticket: https://jira.sakaiproject.org/browse/SAK-29549

A coupling between Profile2 and Roster2 all ready exists. Roster2 uses org.sakaiproject.profile2.logic.ProfileConnectionsLogic.
I added a null check before using the Profile2 SakaiProxy, which is how the ProfileConnectionsLogic is used.
If this is not acceptable, let me know and I will read in the Profile2 properties directly.

I'd prefer it if you just pulled the prop in Roster2's sakaiProxy.
Profile2's sakaiProxy doesn't do anything with the property so it just
seems a bit heavy to wire it in just for that purpose. I don't think you're
wrong or anything, I just know that I'll probably do it myself later just
to take some cruft out of the Spring wiring.
Thanks for adding the switch - it is a useful feature. Do you like the
handlebars clientside stuff?
Cheers,
Adrian.
On 22 June 2015 at 14:58, Leonardo Canessa notifications@github.com wrote:

A coupling between Profile2 and Roster2 all ready exists. Roster2 uses
org.sakaiproject.profile2.logic.ProfileConnectionsLogic.
I added a null check before using the Profile2 SakaiProxy, which is how
the ProfileConnectionsLogic is used.
If this is not acceptable, let me know and I will read in the Profile2
properties directly.
—
Reply to this email directly or view it on GitHub
https://github.com/sakaiproject/sakai/pull/701#issuecomment-114112569.

The changes you requested are in place.
The template changes are nice; it definitely makes for a much cleaner product.

Good one on the ProfileConstants. Go ahead and merge it in.
Cheers,
Adrian.
On 22 June 2015 at 19:55, Leonardo Canessa notifications@github.com wrote:

The changes you requested are in place.
The template changes are nice; it definitely makes for a much cleaner
product.
—
Reply to this email directly or view it on GitHub
https://github.com/sakaiproject/sakai/pull/701#issuecomment-114220896.

What's the hold up on merging this?

authors: adrianfish master-bob


text:
Pass null instead of an empty list if "Default Queues" toggle is enabled in Example App settings

MOB-3657
What was solved?
Fixed the issue: enabled "Default Queues" toggle in Example App ends up with an empty Entry Widget state
Release notes:

[x] Feature
[x] Ignore
[ ] Release notes (Is it clear from the description here?)
[ ] Migration guide (If changes are needed for integrator already using the SDK - what needs to be communicated? Add underneath please)

Additional info:

[ ] Is the feature sufficiently tested? All tests fixed? Necessary unit, acceptance, snapshots added? Check that at least new public classes & methods are covered with unit tests
[ ] Did you add logging beneficial for troubleshooting of customer issues?
[ ] Did you add new logging? We would like the logging between platforms to be similar. Refer to Logging from Android SDKs → Things to consider for newly added logs in Confluence for more information.

Under the hood, it anyway uses an emptyList https://github.com/salemove/android-sdk/blob/master/androidSdk/src/main/java/com/glia/androidsdk/Glia.java#L1122 .
But it means the behavior should be the same, isn't it?

Under the hood, it anyway uses an emptyList https://github.com/salemove/android-sdk/blob/master/androidSdk/src/main/java/com/glia/androidsdk/Glia.java#L1122 . But it means the behavior should be the same, isn't it?

@AndriiHorishniiMOC I have made a change 63146b297549dc5ee9ad4f1171f92ab71e192067 according to the agreement on the stand-up. I suppose it's an answer to your question, right? I'll request your review once again. Thanks.

authors: AndriiHorishniiMOC andrews-moc

repo: salemove/android-sdk-widgets

license: MIT


text:
Need to enable "Build for distribution"

Hi. We're using GliaWidgets which has a dependency on SalemoveSDK. However, with Swift 5.7, the SalemoveSDK project needs to have Build for distribution enabled on the framework target to allow it to be used by Swift 5.7. See the following Stack Overflow thread, BUILD_LIBRARY_FOR_DISTRIBUTION. This setting turns on both library evolution and module stability.
This is the error...

(1, 8) Failed to build module 'SalemoveSDK'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 5.6.1 (swiftlang-5.6.0.323.66 clang-1316.0.20.12)', while this compiler is 'Apple Swift version 5.7 (swiftlang-5.7.0.127.4 clang-1400.0.29.50)'). Please select a toolchain which matches the SDK.

I was going to submit a PR, but wasn't able to, so here's a patch...
From f8cdd0c82e85be2f8a3ffc06f9c965444363a95a Mon Sep 17 00:00:00 2001
From: David Nedrow <david.nedrow@libertymutual.com>
Date: Wed, 5 Oct 2022 16:55:00 -0400
Subject: [PATCH] Enabled  flag

---
 GliaWidgets.xcodeproj/project.pbxproj | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/GliaWidgets.xcodeproj/project.pbxproj b/GliaWidgets.xcodeproj/project.pbxproj
index 7e56297..23d9ced 100644
--- a/GliaWidgets.xcodeproj/project.pbxproj
+++ b/GliaWidgets.xcodeproj/project.pbxproj
@@ -3396,6 +3396,7 @@
 			isa = XCBuildConfiguration;
 			baseConfigurationReference = 2BF626EDE27A8B893F1AAEF5 /* Pods-GliaWidgets.debug.xcconfig */;
 			buildSettings = {
+				BUILD_LIBRARY_FOR_DISTRIBUTION = YES;
 				CLANG_ENABLE_MODULES = YES;
 				CODE_SIGN_IDENTITY = "";
 				CODE_SIGN_STYLE = Automatic;
@@ -3425,6 +3426,7 @@
 			isa = XCBuildConfiguration;
 			baseConfigurationReference = 26CBB076AA7AE3578DCD9D1F /* Pods-GliaWidgets.release.xcconfig */;
 			buildSettings = {
+				BUILD_LIBRARY_FOR_DISTRIBUTION = YES;
 				CLANG_ENABLE_MODULES = YES;
 				CODE_SIGN_IDENTITY = "";
 				CODE_SIGN_STYLE = Automatic;
--
2.37.3

0001-Enabled-flag.patch.zip

Thank you for letting us know about this issue. The fix is in PR and will be delivered in next release.

source: gharchive/issue

authors: dnedrow dukhovnyi

repo: salemove/ios-sdk-widgets


text:
Please provide example for single node, multi gpu implementation

We want to utilize two GPUs in a single node.
In reviewing the code for the load_model_and_preprocess function, it doesn't support torch's DataParallel. Please provide an example of how to achieve this, or an alternative method to utilize both GPUs?

+1 on this need

+1 on this need

I also wondering how to do multi-gpu implementation, and found this #321 , I have tried it, but still have errors.

@RulinShao Hey, Have you solved the problem? When I use multi-node to train BLIP2 stage1, it hangs

repo: salesforce/LAVIS


text:
Exclude stories from storyshots or change Jest environment

Storybook Stories that use the DOM (Modal for instance, need JSDOM mode.

either DOM or visuals
update test readme with directions

We also could switch node/JSDOM with Jest. https://jestjs.io/docs/en/configuration.html#testenvironment-string
The question how to do that with Storyshots.

All DOM snapshots run in jsDOM environment now.

repo: salesforce/design-system-react

license_source: bigquery


text:
Combobox - Incorrect PropTypes type for 'disabled' prop in options array.

I'm getting an error for the 'disabled' prop that is part of option object for the options prop on the Combobox component. Here is the error:

and the current shape of the object for options in combobox.jsx:

I believe the fix is to just make the 'disabled' prop PropTypes.bool instead of PropTypes.boolean and all should be good to go. Just like this:

I tested this by changing it from the node_modules directory and the error went away. Please let me know if I can be of any more assistance in this.

Bumping thread to see if any movement has been made towards this issue.

I would like to work on this Issue
Please assign to me and guide me once

Would like to work on this issue.
Please assign this to me.


text:
Please Clarify Which NPM Package To Be Using for SCV Connector Base

Hey Salesforce Team,
Currently in Node Package Manager (NPM) website, there are two SCV Connector Base NPM packages
We are currently using the following NPM Package @salesforce/scv-connector-base

https://www.npmjs.com/package/@salesforce/scv-connector-base

Currently the latest version is 3.3.19, which was released 5 months ago
Has a couple hundred weekly downloads
Has over 50+ collaborators

We notice that there is another NPM Package scv-connector-base

https://www.npmjs.com/package/scv-connector-base

Currently the latest and only version is 3.5.1, which was released a month ago
Only has a couple weekly download
Published by v.goyal - https://www.npmjs.com/~v.goyal

Could you confirm that we should still be using @salesforce/scv-connector-base and NOT  scv-connector-base
Perhaps scv-connector-base NPM Package was made visible to the public incorrectly?
Please could you let me know.
@krishnan-force @sfyz @dlouvton  @vivektikoo-force
Thanks

Seems that scv-connector-base NPM Package has disappeared

https://www.npmjs.com/package/scv-connector-base

So the correct NPM Package to use would be @salesforce/scv-connector-base

https://www.npmjs.com/package/@salesforce/scv-connector-base

Seems that scv-connector-base NPM Package has disappeared

https://www.npmjs.com/package/scv-connector-base

So the correct NPM Package to use would be @salesforce/scv-connector-base

https://www.npmjs.com/package/@salesforce/scv-connector-base

repo: salesforce/scv-connector-base


text:
README needs overhaul.

The README currently describes the DynamicSpout framework and the Sideline implementation almost hand in hand.  We should review the README and pull these concepts apart and describe each independently.

Going to tackle this after we've split up the pieces into modules.  Then each module can get its own clear readme.

Resolved this in #131

authors: Crim stanlemon

repo: salesforce/storm-dynamic-spout


text:
Selfreporting Symptoms .- Add structured fields that can be set up per patient

Is your feature request related to a problem? Please describe.
To get better structure what is added in the selfreporting part of the app we need to have structured fields with options not just

date field
free text

Describe the solution you'd like
The doctor can per patient set up some questions to answer with more options to select from
Describe alternatives you've considered
Just upload a video were the patient report issues
Additional context

Example Eclipse yourself selfreporting

Self reporting feedback to the enduser


text:
Menu cmd issues

The button menu not working all of them, but from menu v7 works perfect I hope you will look at it

A loyal member of xlicon

Bro Buttons Patched By Whatsapp also i removed menu v8 to v12


text:
db.close() should be awaited

Hi,
I just came across a lock issue because db.close() is not awaited :
https://github.com/salsita/node-pg-migrate/blob/56608a511ba192f249ff5b31a588f050694d4acc/src/runner.ts#L352
I can make a PR if needed.
Many thanks

I can make a PR

@remidewitte yes pls 🫡

repo: salsita/node-pg-migrate

license: mit


text:
🛑 Blog is down

In 86966cc, Blog (https://saltbo.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Blog is back up in 579daa0 after 8 minutes.

repo: saltbo/status


text:
codegen: change static func names to avoid conflicts

Static functions were generated as public functions using the method name found in the windows metadata. Since all static functions of a namespace are added to the same Go package, this could cause collisions when two classes had the same static method (FromBluetoothAddress for example can be found in both Bluetoothdevice and BluetoothLEDevice).
This commit changes the naming strategy to include the class name as a prefix of the static function names. And the existing methods will be kept for a while marked as deprecated to maintain backwards compatibility.
fixes #85

Considering that the change only involves renaming a few functions and the simpler code, I agree

repo: saltosystems/winrt-go


text:
IPv6 & IPv4 use same port crash.

Describe the bug
use IPv6 [::] and IPv4 0.0.0.0 and use same port(eg.21000) crash in my raspberry pi4.
To Reproduce
use salvo::prelude::*;

#[tokio::main]
async fn main() {
    let router = Router::with_path("<**path>").get(cached_proxy);
    tokio::spawn(async {
        let router = Router::with_path("<**path>").get(cached_proxy);
        let acceptor = TcpListener::new(String::from("[::]:21000")).bind().await; Server::new(acceptor).serve(router).await;
    });
    let acceptor = TcpListener::new(String::from("0.0.0.0:21000")).bind().await; Server::new(acceptor).serve(router).await;
}
#[handler]
async fn cached_proxy(_req: &mut Request, _res: &mut Response) { }

Expected behavior
support tcpv4 and tcpv6 at same time.
Screenshots
output
pi@raspbian:~/workspace/rust/cached_api$ cargo r -r
   Compiling cached_api v0.1.0 (/home/pi/workspace/rust/cached_api)
    Finished release [optimized] target(s) in 34.11s
     Running `target/release/cached_api`
thread 'tokio-runtime-worker' panicked at /home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/salvo_core-0.63.1/src/conn/mod.rs:201:31:
called `Result::unwrap()` on an `Err` value: Io(Os { code: 98, kind: AddrInUse, message: "Address already in use" })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
^C

Desktop (please complete the following information):

OS: Win10
Browser ...
Version salvo 0.61 & 0.63.1 rustc 1.73.

additional
It's OK in Windows 10.
It's OK use [::1] and 0.0.0.0 when using same port in raspberry pi4.
It's OK use [::] alone.
Backtrace
pi@raspbian:~/workspace/rust/cached_api$ RUST_BACKTRACE=full cargo r -r
    Finished release [optimized] target(s) in 0.73s
     Running `target/release/cached_api`
thread 'tokio-runtime-worker' panicked at /home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/salvo_core-0.63.1/src/conn/mod.rs:201:31:
called `Result::unwrap()` on an `Err` value: Io(Os { code: 98, kind: AddrInUse, message: "Address already in use" })
stack backtrace:
   0:     0xaaaae111a6ec - std::backtrace_rs::backtrace::libunwind::trace::heaab0e590535aeb3
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:     0xaaaae111a6ec - std::backtrace_rs::backtrace::trace_unsynchronized::h89cc7ae9ebb707d7
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0xaaaae111a6ec - std::sys_common::backtrace::_print_fmt::h08c31be18fedf422
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:67:5
   3:     0xaaaae111a6ec - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hc38bcf44d9e857e3
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:44:22
   4:     0xaaaae113b27c - core::fmt::rt::Argument::fmt::ha5b752f9cd7ef4a3
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/fmt/rt.rs:138:9
   5:     0xaaaae113b27c - core::fmt::write::h9fac187ae7486f3c
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/fmt/mod.rs:1094:21
   6:     0xaaaae11178dc - std::io::Write::write_fmt::h239e9fb6296b3a7f
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/io/mod.rs:1714:15
   7:     0xaaaae111a520 - std::sys_common::backtrace::_print::h52f67cfa8753b0ab
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:47:5
   8:     0xaaaae111a520 - std::sys_common::backtrace::print::hdea7481e2c957a93
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:34:9
   9:     0xaaaae111bba4 - std::panicking::default_hook::{{closure}}::h7c36fa733369c49e
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:270:22
  10:     0xaaaae111b8cc - std::panicking::default_hook::h303eee75f9a8f6a8
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:290:9
  11:     0xaaaae111c168 - std::panicking::rust_panic_with_hook::h270c94381ec34744
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:707:13
  12:     0xaaaae111c030 - std::panicking::begin_panic_handler::{{closure}}::h3653e3502bcc1625
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:599:13
  13:     0xaaaae111abd0 - std::sys_common::backtrace::__rust_end_short_backtrace::h6b8510f2f024eeeb
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:170:18
  14:     0xaaaae111bd80 - rust_begin_unwind
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:595:5
  15:     0xaaaae0f2c680 - core::panicking::panic_fmt::ha96945d7a1b20293
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/panicking.rs:67:14
  16:     0xaaaae0f2c968 - core::result::unwrap_failed::h52241e4ea1d20f58
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/result.rs:1652:5
  17:     0xaaaae0f52bf8 - salvo_core::conn::Listener::bind::{{closure}}::h89a49ff811a8e5e2
  18:     0xaaaae0f36388 - cached_api::main::{{closure}}::{{closure}}::h98b1ee5eea1fab85
  19:     0xaaaae0f34f14 - tokio::runtime::task::core::Core<T,S>::poll::hba8c5b3c48cf2b94
  20:     0xaaaae0f2f4f0 - tokio::runtime::task::harness::Harness<T,S>::poll::h46d47dc1c4f2fd1b
  21:     0xaaaae10d2668 - tokio::runtime::scheduler::multi_thread::worker::Context::run_task::ha220636d44fac3be
  22:     0xaaaae10d0030 - tokio::runtime::context::scoped::Scoped<T>::set::h1ce4a5bf264f0863
  23:     0xaaaae10d2320 - tokio::runtime::scheduler::multi_thread::worker::run::h5a57c31435d58fe0
  24:     0xaaaae10e3adc - tokio::runtime::task::core::Core<T,S>::poll::h871775fbbe59196e
  25:     0xaaaae10cb0cc - tokio::runtime::task::harness::Harness<T,S>::poll::hb3a873bee79e751c
  26:     0xaaaae10edaac - tokio::runtime::blocking::pool::Inner::run::h8403d5d4d76e7800
  27:     0xaaaae10e4760 - std::sys_common::backtrace::__rust_begin_short_backtrace::h94edcef3c32dab02
  28:     0xaaaae10e8448 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hc940c9bdbc895459
  29:     0xaaaae111e970 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h01303c6de09f5469
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/alloc/src/boxed.rs:2007:9
  30:     0xaaaae111e970 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h4f39e7995f973f4c
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/alloc/src/boxed.rs:2007:9
  31:     0xaaaae111e970 - std::sys::unix::thread::Thread::new::thread_start::h9f792bc0c268271e
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys/unix/thread.rs:108:17
  32:     0xffff950307e4 - start_thread
  33:     0xffff94eb559c - <unknown>
  34:                0x0 - <unknown>
^C

Only reproduced on raspberry pi4? I don't have device to test.

I run it in another raspberry pi3b+ with lastest raspbian os & ubuntu server instead of 3rd os in pi4.
The result is same. I don't know if it's a common problem in arm64 platforms, but I have no more arm64 devices for testing it.

I check it with tokio & std, same result. Maybe it's a spec problem of raspberry pi.

authors: chrislearn dryBranch

repo: salvo-rs/salvo


text:
Ascii art usage

Do we have to make our own ascii art for each OS or can we just copy it from https://github.com/dylanaraps/neofetch/blob/master/neofetch
Is it a legal thing?

Both paleofetch and neofetch are open source and licensed under MIT, so I don't think copying them would be a legal issue. If I interpret the wording of the license correctly, if we used enough of them we'd have to include their copy of the MIT license in the source code. At the very least if you copy from neofetch you should mention it in a comment.

Oh ok, I just wanted to make sure! :)

authors: Titaniumtown sam-barr

repo: sam-barr/paleofetch


text:
Installing 5.0.6 on Synology with Portainer - No connection to external MySQL DB

Hi all,
I try to install the newest version of Redmine on a Synology DS1621+ NAS and don't get the connction to my MySQL running.
I run the MariaDB on the Syn NAS:
Server: MariaDB 10 (Localhost via UNIX socket)
Server-Typ: MariaDB
Server-Verbindung: SSL wird nicht verwendet
Server-Version: 10.11.2-MariaDB - Source distribution
Protokoll-Version: 10
Server-Zeichensatz: UTF-8 Unicode (utf8mb3)

My NAS is the follow:
OS Information	linux x86_64 Synology NAS (containerized)
Kernel Version	4.4.302+
Total CPU	4
Total memory	33.6 GB

My Docker is:
Version	20.10.23 (API: 1.41)
Root directory	/volume1/@docker
Storage Driver	btrfs
Logging Driver	db
Volume Plugins	local
Network Plugins	bridge, host, ipvlan, macvlan, null, overlay

I try this yml:
version: '3.9'
services:
  redmine:
    image: sameersbn/redmine:latest
    container_name: CC_Redmine_Prod
    hostname: cc_redmine_prod
    environment:
      DB_ADAPTER: mysql2
      DB_HOST: Synology_NAS_IP
      DB_PORT: 3306
      DB_NAME: redmine
      DB_USERNAME: REDMINEDBUSER
      DB_PASSWORD: REDMINEDBPW

    volumes:
      - /volume1/docker/redmine/files:/usr/src/redmine/files:rw
      - /volume1/docker/redmine/data:/home/redmine/data:rw
      - /volume1/docker/redmine/log:/var/log/redmine:rw
    ports:
      - 3434:3000
    restart: always

The container starts and is running but get the message:
Initializing logdir...
Initializing datadir...
Symlinking dotfiles...
Installing configuration templates...
Configuring redmine...
Configuring redmine::database...........................................................
Could not connect to database server. Aborting...

And thats it!
If I test the db connection with the SSH console I can login to my Redmine Container and can do a MariaDB connection without any Problems:
root@cc_redmine_prod:/home/redmine/redmine# mysql --host=Synology_NAS_IP -u REDMINEDBUSER -p redmine
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 7150
Server version: 5.5.5-10.11.2-MariaDB Source distribution

Copyright (c) 2000, 2023, Oracle and/or its affiliates.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> select * from redmine
    ->
    -> exit
    -> ^C
mysql> exit
Bye
root@cc_redmine_prod:/home/redmine/redmine# exit
exit

I'm stuck at this point. If I try to connect to an MySQL like the one who is written in the repository yml:
services:
  mysql:
    image: sameersbn/mysql:5.7.22-1
    container_name: CC_Redmine_Prod_DB
    hostname: redmine-db
    environment:
      - DB_USER=REDMINEDBUSER
      - DB_PASS=REDMINEDBPW
      - DB_NAME=redmine_production
    volumes:
      - /volume1/docker/redmine/db:/var/lib/mysql:rw

  redmine:
    build: ./
    image: sameersbn/redmine:latest
    container_name: CC_Redmine_Prod
    hostname: redmine
    depends_on:
      - mysql
    environment:
      - TZ=Europe/Berlin

      - DB_ADAPTER=mysql2
      - DB_HOST=redmine-db
      - DB_PORT=3306
      - DB_USER=REDMINEDBUSER
      - DB_PASS=REDMINEDBPW
      - DB_NAME=redmine_production
      - DB_SSL_MODE=preferred

I get the same error on the container console.
HINT: The way of Marius hosting is also not functional for me.
Thanks a lot in advance.
Best regards,
Firehead

The following command is used to check if mysql is reachable, can you try that as well.
mysqladmin -h ${DB_HOST} -P ${DB_PORT} -u ${DB_USER} ${DB_PASS:+-p$DB_PASS} status

Note it might help to read through this issue as well
https://github.com/sameersbn/docker-redmine/issues/399
As far as I can tell all of this works okay when the host is ubuntu so not sure what Synology is doing things differently.

Hi jcormier,
I tryed you command in the SSH shell and get the following:
root@CCNAS01:~# docker exec -it CC_Redmine_Prod bash
root@cc_redmine_prod:/home/redmine/redmine# mysqladmin -h Synology_NAS_IP -P 3306 -u REDMINEDBUSER -pREDMINEDBPW status
mysqladmin: [Warning] Using a password on the command line interface can be insecure.
Uptime: 100519  Threads: 14  Questions: 30904  Slow queries: 0  Opens: 14477  Open tables: 10  Queries per second avg: 0.307
root@cc_redmine_prod:/home/redmine/redmine#

Solved:
WRONG
      DB_USERNAME: REDMINEDBUSER
      DB_PASSWORD: REDMINEDBPW

CORRECT
      DB_USER: REDMINEDBUSER
      DB_PASS: REDMINEDBPW

And for completeness, here are the yml for Redmine, deploying it via portainer.io on a Synology NAS in docker with an external MariaDB/MySQL Server:
version: '3.9'
services:
  redmine:
    image: sameersbn/redmine:latest
    container_name: Redmine_Prod
    hostname: redmine_prod
    environment:
      DB_ADAPTER: mysql2
      DB_HOST: <YOUR_SQLSRV_IP>
      DB_PORT: 3306
      DB_NAME: redmine
      DB_USER: redmine
      DB_PASS: redmine
    volumes:
      - /volume1/docker/redmine/files:/usr/src/redmine/files:rw
      - /volume1/docker/redmine/data:/home/redmine/data:rw
      - /volume1/docker/redmine/log:/var/log/redmine:rw
    ports:
      - 8059:80
      - 8060:443
    restart: always

Please keep in mind, if you are using an external SQL server, you first have to create the user and the database, otherwise it will not be working and don't forget to create the folders for the volumes ;)
Hope this save others hours of finding errors... I spend over 9h to get it functional, but it depends on my low experrience with docker.
Cheers,
Firehead

authors: FireheadJuran jcormier

repo: sameersbn/docker-redmine


text:
How To Implement it Without Getting Logged in

Can We edit it by passing Clientid and client_secret in code instead getting logged for user every time . Please confirm me about this

The client ID and client secret are related to the app, not the user. As I understand it, for the app to access the service, it requires a user authentication with an Amazon account.

Yep the security credentials are for the Amazon oAuth process which then needs an individual user to auth their amazon account, if you don't click the X to logout then it should set a cookie on your browser which would stay logged in.

authors: YiddishNinja bhallaheemanshu sammachin

repo: sammachin/alexaweb


text:
Can't withdraw using the API

print(kucoin.create_withdrawal('BTC', amount, 'address'))

I just used this code will correct API keys and it raises the kucoin.exceptions.KucoinAPIException: KucoinAPIException : b''

I thought it was just me, but it sounds like this is on Kucoin's end. :)
https://news.kucoin.com/en/page/2/
"KuCoin API System and Security Question Login Maintenance
PUBLISHED 2018-04-19
Dear KuCoin Users,
We are performing an API system upgrade. For the time being, users won’t be able to withdraw through the API."

repo: sammchardy/python-kucoin


text:
Expose GIRepositoryNamespace underscore properties in TS namespace

Hello,
In GJS's source code, all GIRepositoryNamespace (Object representing imported GIR libraries) expose two underscored properties containing the lib name and version:
https://gitlab.gnome.org/GNOME/gjs/-/blob/master/gi/ns.cpp#L186-190
This PR exposes those properties in the Typescript namespace definition for each processed lib.

Will check why the tests are failing

Fixed the tests.
This was originally a very quick and dirty change to add the support needed for a project I am working, so I only tested on the environment that I was developing in, sorry. It should now be a cleaner implementation with support for all the environment this tool is targeting.

repo: sammydre/ts-for-gir


text:
🛑 Jobster-API is down

In 1dffa42, Jobster-API (https://jobster-api-vnuk.onrender.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jobster-API is back up in 89645b7 after 8 minutes.

repo: sampathsailanka/monitoring-tool


text:
Could more gracefully handle error

I just found out that the way I was using Rangetouch broke my site for about a week.
I guess I accidentally moved require("rangetouch/dist/rangetouch"); to before $(document).ready(function () {.
And I didn't have it within a try/catch.
What would have been nice is if Rangetouch wouldn't cause an exception (causing all my other javascript to fail) just because at the time of it being called there was no input range rendered on the page.
Thanks so much for your cool tool!
I'm now successfully using it like this:
$(document).ready(function () {
        try {
            require("rangetouch/dist/rangetouch");//This must be called *after* $(document).ready() https://rangetouch.com/ https://github.com/sampotts/rangetouch
        } catch (e) {
            console.log(e);
        }
...

Sorry about that. I'll get this fixed up today given it will be a tiny fix...

Hey,
This should be resolved in v1.0.3

@sampotts Awesome! Thanks for your hard work!

authors: ryancwalsh sampotts

repo: sampotts/rangetouch


text:
Handle renaming a slot

Right now if you have already defined agent response and you change the slot name then the agent responses remain using the wrong slot name.

Closed by https://github.com/samtecspg/articulate/commit/634da469db9d7e9936153fc0b091b92ca3da306e

authors: dcalvom wrathagom

repo: samtecspg/articulate


text:
add frozenset to schema.py/field_class_to_schema

Feature Request
         pydantic version: 1.5.1
        pydantic compiled: False
             install path: /home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/pydantic
           python version: 3.6.5 (default, May 11 2018, 13:30:17)  [GCC 7.3.0]
                 platform: Linux-4.15.0-29deepin-generic-x86_64-with-Deepin-15.11-stable
 optional deps. installed: []

Use pydantic to validate frozenset in FastApi, when I open SwaggerUI in Chrome, error occurs.
Add frozenset type in schema.py/field_class_to_schema to resolve the error.

```exception
Traceback (most recent call last):
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/uvicorn/protocols/http/httptools_impl.py", line 385, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/uvicorn/middleware/proxy_headers.py", line 45, in __call__
    return await self.app(scope, receive, send)
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/fastapi/applications.py", line 148, in __call__
    await super().__call__(scope, receive, send)  # pragma: no cover
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/starlette/applications.py", line 102, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/starlette/middleware/errors.py", line 181, in __call__
    raise exc from None
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/starlette/middleware/errors.py", line 159, in __call__
    await self.app(scope, receive, _send)
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/starlette/exceptions.py", line 82, in __call__
    raise exc from None
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/starlette/exceptions.py", line 71, in __call__
    await self.app(scope, receive, sender)
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/starlette/routing.py", line 550, in __call__
    await route.handle(scope, receive, send)
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/starlette/routing.py", line 227, in handle
    await self.app(scope, receive, send)
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/starlette/routing.py", line 41, in app
    response = await func(request)
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/fastapi/applications.py", line 103, in openapi
    return JSONResponse(self.openapi())
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/fastapi/applications.py", line 95, in openapi
    openapi_prefix=self.openapi_prefix,
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/fastapi/openapi/utils.py", line 291, in get_openapi
    flat_models=flat_models, model_name_map=model_name_map
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/fastapi/utils.py", line 84, in get_model_definitions
    model, model_name_map=model_name_map, ref_prefix=REF_PREFIX
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/pydantic/schema.py", line 456, in model_process_schema
    model, by_alias=by_alias, model_name_map=model_name_map, ref_prefix=ref_prefix, known_models=known_models
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/pydantic/schema.py", line 492, in model_type_schema
    f, by_alias=by_alias, model_name_map=model_name_map, ref_prefix=ref_prefix, known_models=known_models
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/pydantic/schema.py", line 191, in field_schema
    known_models=known_models or set(),
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/pydantic/schema.py", line 418, in field_type_schema
    known_models=known_models,
  File "/home/wang/PycharmProjects/FastApiLearn/venv/lib/python3.6/site-packages/pydantic/schema.py", line 686, in field_singleton_schema
    raise ValueError(f'Value not declarable with JSON Schema, field: {field}')
ValueError: Value not declarable with JSON Schema, field: name='a' type=frozenset required=True

```schema.py

field_class_to_schema: Tuple[Tuple[Any, Dict[str, Any]], ...] = (
    (Path, {'type': 'string', 'format': 'path'}),
    (datetime, {'type': 'string', 'format': 'date-time'}),
    (date, {'type': 'string', 'format': 'date'}),
    (time, {'type': 'string', 'format': 'time'}),
    (timedelta, {'type': 'number', 'format': 'time-delta'}),
    (IPv4Network, {'type': 'string', 'format': 'ipv4network'}),
    (IPv6Network, {'type': 'string', 'format': 'ipv6network'}),
    (IPv4Interface, {'type': 'string', 'format': 'ipv4interface'}),
    (IPv6Interface, {'type': 'string', 'format': 'ipv6interface'}),
    (IPv4Address, {'type': 'string', 'format': 'ipv4'}),
    (IPv6Address, {'type': 'string', 'format': 'ipv6'}),
    (str, {'type': 'string'}),
    (bytes, {'type': 'string', 'format': 'binary'}),
    (bool, {'type': 'boolean'}),
    (int, {'type': 'integer'}),
    (float, {'type': 'number'}),
    (Decimal, {'type': 'number'}),
    (UUID, {'type': 'string', 'format': 'uuid'}),
    (dict, {'type': 'object'}),
    (list, {'type': 'array', 'items': {}}),
    (tuple, {'type': 'array', 'items': {}}),
    (set, {'type': 'array', 'items': {}, 'uniqueItems': True}),
    (frozenset, {'type': 'array', 'items': {}, 'uniqueItems': True}),  # my addition
)

Could you fix your formatting in the issue?
It would be useful to see a demonstration of the problem: e.g. code that raises an exception.

Could you fix your formatting in the issue?
It would be useful to see a demonstration of the problem: e.g. code that raises an exception.

I have added my exception.

I meant a self contained example that demonstrates the problem.
E.g.:
from pydantic import BaseModel

...

from pydantic import BaseModel
class Item(BaseModel):
    item1: frozenset

This piece of code is ok. But when I read "SwaggerUI" in web framework "FastApi", the above exception occured.

That's not a demonstration of the problem. The error can be caused with:
from pydantic import BaseModel

class Item(BaseModel):
    item1: frozenset

item = Item(item1={1, 2, 3})
print(item.schema())

exception:
Traceback (most recent call last):
  File "test.py", line 9, in <module>
    print(item.schema())
  File "/Users/samuel/code/pydantic/pydantic/main.py", line 558, in schema
    s = model_schema(cls, by_alias=by_alias)
  File "/Users/samuel/code/pydantic/pydantic/schema.py", line 137, in model_schema
    m_schema, m_definitions, nested_models = model_process_schema(
  File "/Users/samuel/code/pydantic/pydantic/schema.py", line 465, in model_process_schema
    m_schema, m_definitions, nested_models = model_type_schema(
  File "/Users/samuel/code/pydantic/pydantic/schema.py", line 501, in model_type_schema
    f_schema, f_definitions, f_nested_models = field_schema(
  File "/Users/samuel/code/pydantic/pydantic/schema.py", line 190, in field_schema
    f_schema, f_definitions, f_nested_models = field_type_schema(
  File "/Users/samuel/code/pydantic/pydantic/schema.py", line 417, in field_type_schema
    f_schema, f_definitions, f_nested_models = field_singleton_schema(
  File "/Users/samuel/code/pydantic/pydantic/schema.py", line 733, in field_singleton_schema
    raise ValueError(f'Value not declarable with JSON Schema, field: {field}')
ValueError: Value not declarable with JSON Schema, field: name='item1' type=frozenset required=True

This is what I was looking for.
PR welcome to to fix this.

authors: samuelcolvin wangpeibao

repo: samuelcolvin/pydantic


text:
BaseModel.construct does not set aliased fields consistently with standard instantiation

Checks

[x] I added a descriptive title to this issue
[x] I have searched (google, github) for similar issues and couldn't find anything
[x] I have read and followed the docs and still think this is a bug

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.8.2
            pydantic compiled: False
                 install path: /Users/kyleamos/Library/Caches/pypoetry/virtualenvs/api-KwVDv1SR-py3.9/lib/python3.9/site-packages/pydantic
               python version: 3.9.1 (default, Jan 18 2022, 12:54:24)  [Clang 13.0.0 (clang-1300.0.29.30)]
                     platform: macOS-12.1-arm64-arm-64bit
     optional deps. installed: ['email-validator', 'typing-extensions']

from pydantic import BaseConfig, BaseModel, Field

class Foo(BaseModel):
    class Config(BaseConfig):
        allow_population_by_field_name = True

    bar_: int = Field(..., alias="bar")

expected_value = 2
assert Foo(bar=expected_value).bar_ == expected_value
assert Foo.construct(bar=expected_value).bar_ == expected_value  # AttributeError: 'Foo' object has no attribute 'bar_'
...

https://github.com/samuelcolvin/pydantic/pull/4191
I'll try to get everything installed for checks to pass on the PR tomorrow, the current fail one at a time in CI stuff has exhausted my time for this for today.
I'm sure there's an automagic way to get the PR to link to this issue as well and I'm sure I messed that up.


text:
Fix jQuery detection when @ember/jquery is only an indirect dependency

We took the advice to upgrade to v2.0.0-beta. Overall it seems pretty stable already :+1:. We're currently running into one issue, which is addressed in this PR.

This solves the following use case:

App A has a dependency on addon B.
App A does not have a direct dependency on @ember/jquery.
Addon B does have a direct dependency on @ember/jquery.

Previously, it was in this case incorrectly assumed that window.jQuery would be available when running app A.

The change looks reasonable to me. Thanks!

https://github.com/san650/ember-cli-page-object/releases/tag/v2.0.0-beta.5


text:
Allow pure web component mounting

For most web component test cases (in my experience anyway) - you simply want to mount the web component the same way you would mount it in an app, i.e. as a string:
<my-web-component some-attribute="foo">bar</my-web-component>
This (very hacky) fix allows the above option whilst keeping the existing behaviour if necessary.

For most web component test cases (in my experience anyway) - you simply want to mount the web component the same way you would mount it in an app, i.e. as a string:
<my-web-component some-attribute="foo">bar</my-web-component>
This (very hacky) fix allows the above option whilst keeping the existing behaviour if necessary.

Thank you for another PR! It is nice that the component used in testing is used in the same way as in production. However the cons i see are:

It will destroy type safety
It is not consistent with Playwright's API
Would have to register the component manually as we cannot resolve the component based on a string

If we do this, i think this should be added to Playwright first. Someone else asked the same thing for Svelte BTW.: https://github.com/microsoft/playwright/issues/18758#issuecomment-1319599376
Maybe we should create a separate issue for now to collect upvotes?

For most web component test cases (in my experience anyway) - you simply want to mount the web component the same way you would mount it in an app, i.e. as a string:
<my-web-component some-attribute="foo">bar</my-web-component>
This (very hacky) fix allows the above option whilst keeping the existing behaviour if necessary.

Thank you for another PR! It is nice that the component used in testing is used in the same way as in production. However the cons i see are:

It will destroy type safety
It is not consistent with Playwright's API
Would have to register the component manually as we cannot resolve the component based on a string

If we do this, i think this should be added to Playwright first. Someone else asked the same thing for Svelte BTW.: microsoft/playwright#18758 (comment)
Maybe we should create a separate issue for now to collect upvotes?

I've discovered a problem with this 'hack' anyway :) It's not un-mounting the component(s) between tests and I also have to have at least one test that creates the component via the standard mechanism otherwise it doesn't recognise any tests. So yes, probably safe to ignore this for now - however it is (IMO) a much nicer way to component test web components than creating them using JS.


text:
Redirect results in 404 on mobile devices

Detailed description
Payments are being registered, yet when made on a mobile device the redirect url results in a 404. On desktops it works just fine.

Not much to go on here. What url are you redirecting to?

Closing this issue due to inactivity.

authors: icuMedia sandervanhooft


text:
Hotifx sockets

Web Sockets were not working because of a bad merge inside
client/src/modules/list/index.jsx   file.
I have found "React can't call setState after a component is unmounted..." and fix is inside ListItem.jsx file.

@marekrozmus
I removed socket emitting and receiving logic from ListItem to ItemsList component.
And now, no error related with React can't call set state appears in the console.
Everything works as expected.
Anyway, I can't totally remove socket connection from ListItem component, cause this item need to pass socket as an argument to all actions related to archiving, deleting, restoring, etc.
Because inside the action I'm emitting action about "ARCHIVE_ITEM" "RESTORE_ITEM" etc

repo: sandstreamdev/eoc


text:
chore(main): release audit 1.42.0

:robot: I have created a release beep boop
1.42.0 (2023-05-12)
Features

root project vulnerability scan now optional (ffc121d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sandworm-hq/sandworm-audit/releases/tag/audit-v1.42.0 :sunflower:

repo: sandworm-hq/sandworm-audit


text:
[Supernova] Silence Scheduler for Supernova

Add a form to schedule silences for e.g. maintenance.
fixes #398

When opening the Template form without selecting any template you can still press save and an error will be displayed. I will propose to disable the save button until the template is selected. What do you think?

If the template have same title the select displays the two templates selected. This is probably because the key is the title. I would recomend to create unique ids (index) to avoid it.

Check how the key status is used in the old Supernova. Ex:
"status": "active",

Validate template input. Changing for example editable_labels  as string crashes the component.

authors: ArtieReus TilmanHaupt

repo: sapcc/juno


text:
Add GitHub sponsors support!

I really want to chip in since I don't have much coding skills, but I can spare some monetary support!
Good job with the work so far, and I hope this grows even faster than it already is.

The sponsor button is up.

authors: hanaral sapoturge

repo: sapoturge/froggum


text:
Work with finance/procurement to create agile RFP

If one does not already exist ... if it does, close with issue

Work with finance to create an RFP that follows guidance from here
https://github.com/sara-sabr/technology-budgeting/blob/master/handbook.md

Ex:

A Statement of Objectives rather than a Statement of Work
Quality Assessment Surveillance Plan (QASP)
Establish clear requirements about the regular delivery of working code, documentation, testing
Ownership of all work products remaining with the state

See https://www.gcpedia.gc.ca/wiki/Agile_Procurement

Oh that's fantastic. Thanks @gabrielcossette !

authors: gabrielcossette jaysonmc

repo: sara-sabr/ITStrategy


text:
[fix] Allow funcdefs to be passed into ?

Prior to this, you could not pass funcdef into a function that has '?/any'
Minimal example:
Angelscript:
funcdef void foo();

void test()
{
    func(@foo);
}

as.predefined
void func(?&in);

Before this PR, it would error out. If there is a better way to patch/add this in, just let me know :)

LGTM!


text:
fix(sasjs-compile): insert precode as part of compile step

Issue
https://github.com/sasjs/cli/issues/163
Intent
Insert precode as part of the compile step rather than later in the process.
Implementation

Moved insertion of precode to compile step.
Removed precode insertion at the time of creating the final .sas files.

Checks

[x] Code is formatted correctly (npm run lint:fix).
[ ] Any new functionality has been unit tested.
[x] All unit tests are passing (npm test).
[x] All CI checks are green.
[ ] JSDoc comments have been added or updated.

:tada: This PR is included in version 1.17.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: sasjs/cli


text:
Fix issue with base64 encoding & decoding

Issue
No Github issue to link.
Intent
Fix special characters encoding on SAS9 for sasjs.js ( sasjs/adapter/index ) for minimal seed apps.
Implementation
Replaced btoa with js-base64 package.
Removed nonBinaryFileTypes as for creating services, all files' content should be encoded to base64.
Changes in sasjsout

added utf-8 in header
improved base64 decoding code

Checks

[x] Code is formatted correctly (npm run lint:fix).
[ ] Any new functionality has been unit tested.
[x] All unit tests are passing (npm test).
[ ] All CI checks are green.
[ ] JSDoc comments have been added or updated.
[ ] Reviewer is assigned.
[ ] Successful deployment of minimal seed app for SAS9.
[ ] Successful deployment of react seed app for SAS9.

@saadjutt01 pls pull from master into encode-to-base64


text:
node-sass 4.7.2 installation error - npm - Mac OS X High Sierra

It seems that I cannot install node-sass in my environment. I'm on Mac OS X 10.13.3.
To replicate, I simply execute:
mypath root# npm install node-sass

as root.
Detailed log follows:
> node-sass@4.7.2 install /mypath/node_modules/node-sass
> node scripts/install.js

Unable to save binary /mypath/node_modules/node-sass/vendor/darwin-x64-57 : { Error: EACCES: permission denied, mkdir '/mypath/node_modules/node-sass/vendor'
    at Object.fs.mkdirSync (fs.js:885:18)
    at sync (/mypath/node_modules/mkdirp/index.js:71:13)
    at Function.sync (/mypath/node_modules/mkdirp/index.js:77:24)
    at checkAndDownloadBinary (/mypath/node_modules/node-sass/scripts/install.js:111:11)
    at Object.<anonymous> (/mypath/node_modules/node-sass/scripts/install.js:154:1)
    at Module._compile (module.js:643:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/mypath/node_modules/node-sass/vendor' }

> node-sass@4.7.2 postinstall /mypath/node_modules/node-sass
> node scripts/build.js

Building: /usr/local/bin/node /mypath/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ '/usr/local/bin/node',
gyp verb cli   '/mypath/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using node-gyp@3.6.2
gyp info using node@8.9.4 | darwin | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` succeeded python2 /usr/local/bin/python2
gyp verb check python version `/usr/local/bin/python2 -c "import platform; print(platform.python_version());"` returned: "2.7.10\n"
gyp verb get node dir no --target version specified, falling back to host node version: 8.9.4
gyp verb command install [ '8.9.4' ]
gyp verb install input version string "8.9.4"
gyp verb install installing version: 8.9.4
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 8.9.4
gyp verb build dir attempting to create "build" dir: /mypath/node_modules/node-sass/build
gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir '/mypath/node_modules/node-sass/build'
gyp ERR! System Darwin 17.4.0
gyp ERR! command "/usr/local/bin/node" "/mypath/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /mypath/node_modules/node-sass
gyp ERR! node -v v8.9.4
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
Build failed with error code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@4.7.2 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@4.7.2 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

NPM version: 5.6.0
Node version: v8.9.4
Node Process: { http_parser: '2.7.0',  node: '8.9.4',  v8: '6.1.534.50',  uv: '1.15.0',  zlib: '1.2.11',  ares: '1.10.1-DEV',  modules: '57',  nghttp2: '1.25.0',  openssl: '1.0.2n',  icu: '59.1',  unicode: '9.0',  cldr: '31.0.1',  tz: '2017b' }
Node Platform: darwin
Node architecture: x64
node-sass version: n.a.
npm node-sass versions: n.a.

The error message clearly indicates this is a permission issue trying to
create '/mypath/node_modules/node-sass/vendor'.
Npm runs scripts as a restricted user, no root.
You can try using the --unsafe-perms flag to npm install. Otherwise you
need to fix your permissions.
On 2 Mar. 2018 12:38 am, "rik72" notifications@github.com wrote:
It seems that I cannot install node-sass in my environment. I'm on Mac OS X
10.13.3.
To replicate, I simply execute:
mypath root# npm install node-sass
as root.
Detailed log follows:

node-sass@4.7.2 install /mypath/node_modules/node-sass
node scripts/install.js

Unable to save binary
/mypath/node_modules/node-sass/vendor/darwin-x64-57 : { Error: EACCES:
permission denied, mkdir '/mypath/node_modules/node-sass/vendor'
at Object.fs.mkdirSync (fs.js:885:18)
at sync (/mypath/node_modules/mkdirp/index.js:71:13)
at Function.sync (/mypath/node_modules/mkdirp/index.js:77:24)
at checkAndDownloadBinary
(/mypath/node_modules/node-sass/scripts/install.js:111:11)
at Object.
(/mypath/node_modules/node-sass/scripts/install.js:154:1)
at Module._compile (module.js:643:30)
at Object.Module._extensions..js (module.js:654:10)
at Module.load (module.js:556:32)
at tryModuleLoad (module.js:499:12)
at Function.Module._load (module.js:491:3)
errno: -13,
code: 'EACCES',
syscall: 'mkdir',
path: '/mypath/node_modules/node-sass/vendor' }

node-sass@4.7.2 postinstall /mypath/node_modules/node-sass
node scripts/build.js

Building: /usr/local/bin/node
/mypath/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose
--libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ '/usr/local/bin/node',
gyp verb cli   '/mypath/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using node-gyp@3.6.2
gyp info using node@8.9.4 | darwin | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb which succeeded python2 /usr/local/bin/python2
gyp verb check python version /usr/local/bin/python2 -c "import platform; print(platform.python_version());" returned: "2.7.10\n"
gyp verb get node dir no --target version specified, falling back to
host node version: 8.9.4
gyp verb command install [ '8.9.4' ]
gyp verb install input version string "8.9.4"
gyp verb install installing version: 8.9.4
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 8.9.4
gyp verb build dir attempting to create "build" dir:
/mypath/node_modules/node-sass/build
gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir
'/mypath/node_modules/node-sass/build'
gyp ERR! System Darwin 17.4.0
gyp ERR! command "/usr/local/bin/node"
"/mypath/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose"
"--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags="
"--libsass_library="
gyp ERR! cwd /mypath/node_modules/node-sass
gyp ERR! node -v v8.9.4
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
Build failed with error code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@4.7.2 postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@4.7.2 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely
additional logging output above.

NPM version: 5.6.0
Node version: v8.9.4
Node Process: { http_parser: '2.7.0', node: '8.9.4', v8: '6.1.534.50',
uv: '1.15.0', zlib: '1.2.11', ares: '1.10.1-DEV', modules: '57', nghttp2:
'1.25.0', openssl: '1.0.2n', icu: '59.1', unicode: '9.0', cldr: '31.0.1',
tz: '2017b' }
Node Platform: darwin
Node architecture: x64
node-sass version: n.a.
npm node-sass versions: n.a.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2263, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWKmjcEjiIhVuvDcO-Cu5F8x-vjvqks5tZ_nygaJpZM4SYUZx
.

https://github.com/sass/node-sass/blob/master/TROUBLESHOOTING.md#cannot-find-module-rootinstalljs

Thank you.

Hello,
I'm having the same issue and I tried the previous link but still nothing changed.
Any other recommandations ?
Thank you.

Please open a new issue
On 3 Mar. 2018 3:36 am, "Charly Bernard" notifications@github.com wrote:

Hello,
I'm having the same issue and I tried the previous link but still nothing
changed.
Any other recommandations ?
Thank you.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2263#issuecomment-369975727,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWGIM8hsNKAmLMjsT2F1o9gZFnaVgks5taXUogaJpZM4SYUZx
.

Same issue three weeks later, no solution

The issue resolution was very clear. The OP didn't have the right permissions to install a global package.
Use the suggested resolution or open a new issue.

try:
sudo rm -rf node_modules && npm rebuild node-sass && npm i
ref: http://froshgeek.com/fix-npm-error-permission-denied-mkdir-related-to-node-sass-macos/

authors: cbernard lek-tin nschonni rik72 stevematdavies xzyfer

repo: sass/node-sass


text:
[SECURITY] Please FIX vulnerabilities!

=== npm audit security report ===

								 Manual Review
			 Some vulnerabilities require your attention to resolve

		  Visit https://go.npm.me/audit-guide for additional guidance

  Moderate        Prototype pollution

  Package         hoek

  Patched in      > 4.2.0 < 5.0.0 || >= 5.0.3

  Dependency of   node-sass [dev]

  Path            node-sass > node-gyp > request > hawk > boom > hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Patched in      > 4.2.0 < 5.0.0 || >= 5.0.3

  Dependency of   node-sass [dev]

  Path            node-sass > node-gyp > request > hawk > cryptiles > boom >
				  hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Patched in      > 4.2.0 < 5.0.0 || >= 5.0.3

  Dependency of   node-sass [dev]

  Path            node-sass > node-gyp > request > hawk > hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Patched in      > 4.2.0 < 5.0.0 || >= 5.0.3

  Dependency of   node-sass [dev]

  Path            node-sass > node-gyp > request > hawk > sntp > hoek

  More info       https://nodesecurity.io/advisories/566

found 4 moderate severity vulnerabilities in 6455 scanned packages
  4 vulnerabilities require manual review. See the full report for details.

See https://github.com/nodejs/node-gyp/pull/1492

I don't know what I'm doing wrong but I keep getting the error
PC-006% npm i -D node-sass
npm WARN notice [SECURITY] hoek has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=hoek&version=2.16.3 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.

I deleted node_modules folder, package-lock.json and the cache folder.
At every install the "broken" hoek version is retrieved.
I tried on Windows  and on WSL Ubuntu - no difference.

What version are you running? This seems like a duplicate of #2355 which is resolved by updating to 4.9.1

@bardware the answer is literally in the comment above yours. Please read issues before posting.

As explained in #2355 and this issue (again). We have updated request which had a dependency on heok. However one of our dependencies (node-gyp) is also locked to an older version of request because they too cannot break backward compatibility.
There is an open PR (linked above) to bump that dependency as we did to a version of request that removes hoek whilst maintaining BC.
All of this information was present in the issues you read. Please direct your enthusiasm at the node-gyp PR linked above.

Neither both v4.7.x (suggest in the other issue although v4.7.0 doesn't exist) and v4.9.1 fixes this issue. I still get the 4 moderate severity vulnerabilities.
None of the solutions in #2355 work.

@nschonni Why did you closed this issue which is still a problem?

The problem is, i've broken their "Issue templating"; But why i must add some informations like What is the expected behaviour? and other unwanted informations, when the problem is on their side and not on my own?
I've used the latest version, there can be installed by npm; And you no more need informations. Use non-vulnerability packages, upgrade old vulnerabilities or be a bad developer.

It's closed because there is nothing we can do. We have summarized the issue multiple times. People insist on not bothering to read the issue and post their opinion.
There is no further discussion to had on this topic. It's out of our control. Read the prior couple comments.

authors: Berkmann18 Bizarrus bardware nschonni xzyfer


text:
includePaths not working on 2.0.1

Travis as well as an ubuntu 12.04.5 LTS vm with node 0.10.0 fails when using grunt-sass with the includePaths option set.
Running "sass:all" (sass) task
OptionParser::InvalidOption: invalid option: --include-paths=bower_components
  Use --trace for backtrace.

See: https://github.com/bezoerb/generator-grunt-symfony/issues/10 for some more details.
My local copy using node 0.12.0 however is working fine as well as the cli version.

When reporting issue on node-sass, please include the reproducible steps with node-sass API code.
More at bug reporting guidelines: https://github.com/sass/node-sass/blob/master/CONTRIBUTING.md#bug-reports.

Thanks for the hint ;)
Looks like this is no node-sass issue. At least i can't reproduce the the error when using the node-sass API or the CLI directly. Sorry for the interrupt. I'll try to dig some deeper.


text:
Recursive output

There doesnt seem to be a way to recursively output files. All my attempts simply extract one file. my setup in package.json : cat ./app/styles/**/*.scss | node-sass | autoprefixer -b 'last 2 versions' | cleancss -o public/css/main.css
is this even possible?
Thanks

Do you mean UNIX cat does not support ** syntax? Use find app/styles -type f -name '*.scss' -print to get a list of files to concatenate. You could even try
 find app/styles --type f -name '*.scss' -exec cat {} \; | node-sass

to feed them all to node-sass. It's a UNIX shell question, not a node-sass issue, is it?

Sorry, I think I explained it wrong and that this might be discussion on another thread.
I am trying to find a way to output the compiled files individually, rather than into one compiled css file. So that when I run the command my sass input structure will be mirrored in my output folder.
Not sure if this is possible using node-sass.
Thanks

That's unrelated to node-sass
a script similar to the one below would do the job:
find nt -name '*.scss' -exec $HOME/node_modules/node-sass/bin/node-sass {} `dirname {}`/`basename {} .scss`.css \;

@talwoolf do you mean you want to compile multiple files in a sass directory and output them to a css directory? If so that was added to the cli recently and should be part of the next beta version.

Amazing, thats exactly what I wanted. great work. Thanks.

authors: paulcpederson saper talwoolf


text:
fix(telegram): polling when stops bot

在 polling 时停用适配器，http 请求未中断，响应后向下继续执行

Codecov Report

Merging #150 (e60f010) into master (a3ea0c8) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##           master     #150   +/-   ##
=======================================
  Coverage   81.83%   81.83%
=======================================
  Files           1        1
  Lines         424      424
  Branches       86       86
=======================================
  Hits          347      347
  Misses         77       77

authors: XxLittleCxX codecov-commenter

repo: satorijs/satori


text:
Setup CI system

I just learned how to use Github Workflows 👍 It's super easy and awesome. I can setup CI for us if you're cool with it @titusfortner ?

I just switched to GitHub Workflows in the WebdriverIO project and it's amazing. I also recommend to automate releases through it if possible.

authors: christian-bromann nadvolod


text:
feat: Bump saucectl runners

Description

Cypress framework version 12.17.4, runner version 10.5.0.
Playwright framework version 1.37.1, runner version 2.21.0 .
TestCafe framework version 3.2.0, runner version 3.1.0.
Motivation and Context

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation fix (typos, incorrect content, missing content, etc.)

Hi @lauramthomas , can I get a review for this PR? Thanks!

repo: saucelabs/sauce-docs


text:
Missing visual specs for parallelization + multi-screeenshot

I'm adding 2 important use cases in visual. One for doing multi screenshots in a single test. One for running a test cross-platform. As we will see, our current implementation of cross-platform doesn't work. I am pretty sure that it's because we by default set a build name which in Screener should not be set.

Superceded by #256

authors: nadvolod titusfortner


text:
Protobuf 3

How can I help make sure this project can support proto3?

It would be perfect if proto3 is supported.

https://issues.apache.org/jira/browse/PARQUET-665
Proto3 support has landed in Parquet.

Thats great news! Would this just be a matter of updating the dependency once mr-parquet releases the changes?

happy to take PR/contribution. I wonder how one would handle protobuf 2.5 that is already shipped with Hadoop and Spark?

@saurfang That's a good question. There may not be a good way to support both protobuf 2.5 and protobuf 3.0. To use proto3 with Spark that already ships with proto 2.5, we can use shaded jars.

@saurfang Btw, does this work directly with Spark 2.0 or needs some re-work?

@IceMan81 this is exactly what we do for a number of our jobs.
<relocation>
  <pattern>com.google.protobuf.util</pattern
  <shadedPattern>shaded.com.google.protobuf.util</shadedPattern>
</relocation>
<relocation>
  <pattern>com.google.protobuf</pattern
  <shadedPattern>shaded.com.google.protobuf</shadedPattern>
</relocation>

authors: IceMan81 ebenoist saurfang

repo: saurfang/sparksql-protobuf


text:
Add flag for turning on notifications

In this pull request, one flag and one behavior change is done:

By default waybar-updates does not notifies when updates are needed. This would be a more sensible behavior as normally people would like to just see the updates on the bar and it is better to opt-in to notifications instead.
The flag -n or --notify is added to turn on notifications.

This would solve issue #26.

I will release it soon.

Released as update v0.4.0.

authors: juanscr savely-krasovsky

repo: savely-krasovsky/waybar-updates


text:
Purge directory suddently appearing

Hi,
I am currently investigating on this issue: After performing a yum update on my RHEL 7 servers, effectively going from 7.6 to 7.7, this puppet module started purging the /etc/rsyslog.d/ directory. The consequence is that it deletes the listen.conf file, that is provided by the systemd package. I have no idea of how this purge began and I doubt this module.
Sep 19 21:34:11 server1 puppet-agent[3154]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/listen.conf]/ensure) removed
If someone has ideas or hints, feel free to comment. I'll let you know if I find something.

Nevermind, it was my config, I just didn't know.

repo: saz/puppet-rsyslog


text:
Switch to eclipse-temurin by default?

These come with ubuntu/alpine/windowsservercore
This is mentioned on the openjdk docker page

https://hub.docker.com/_/openjdk?tab=description
WARNING
If you are a user/consumer of Java, this image is probably not what you expect!
These images contain "vanilla" builds of the OpenJDK project provided by Oracle or the relevant "updates project lead" (depending on the version).
For a more "supported" experience, we recommend one of the following other Official Images (listed in alphabetical order with no intentional or implied preference):
[amazoncorretto](https://hub.docker.com/_/amazoncorretto)
[eclipse-temurin](https://hub.docker.com/_/eclipse-temurin)
[ibm-semeru-runtimes](https://hub.docker.com/_/ibm-semeru-runtimes)
[ibmjava](https://hub.docker.com/_/ibmjava)
[sapmachine](https://hub.docker.com/_/sapmachine)

+1 on Eclipse Temurin. I explicitly endorse that on https://www.scala-sbt.org/1.x/docs/Installing-sbt-on-Linux.html page as well over distro JDKs.

The question is a bit what is "by default"
We probably can't just switch as the images without qualifier are based on debian and temurin is based on ubuntu?
Maybe it's enough to:

repeat above concern in the readme
update all examples to use temurin
stop updating openjdk images, remove them from the build

Now that this image is under new management/sbtscala, I think there's some degree of design freedom we earned under the new name. I personally see Ubuntu and Debian both as distribution of deb-based distro.

Readme was update in 4d959120f79c14fecc87407032cf9bb26c2e148a
Will for now namespace the openjdk images as openjdk-* so that users don't think these are the default images.

repo: sbt/docker-sbt


text:
Incremental compiler is not multiprocess-safe

It's common that users run multiple instances of incremental compiler that all try to write to the same target directory. It might because they have two sbt processes running alongside. Another common scenario is that people have both sbt and Scala IDE running with the same project loaded.
At the moment incremental compiler has no built-in support for detecting access races to target directory. This result in hard to debug crashes as seen in #1184.
At the very least we should detect and issue an error when another process tries to run incremental compiler while one is running already.

you don't even need to be multi-process to cause this: https://github.com/scala/scala/pull/6256/commits/8b63ea205e2ead8a984f52dee1ff690ea298d94e :) (/cc @retronym)

authors: dwijnand gkossakowski

repo: sbt/sbt


text:
1.4.0-RC1: Confusing cache resolution messages

When compiling a multi-project build, the remote cache messages leave something to be desired:
[info] remote cache not found for 0.0.0-4de3154dfe2290e65174c1cc740636ffbfea757c
[info] remote cache artifact extracted for Some(cached-compile)
[info] remote cache artifact extracted for Some(cached-test)
[info] remote cache artifact extracted for Some(cached-compile)
[info] remote cache artifact extracted for Some(cached-test)
[info] remote cache artifact extracted for Some(cached-compile)
[info] remote cache artifact extracted for Some(cached-test)
[info] remote cache artifact extracted for Some(cached-compile)
[info] remote cache artifact extracted for Some(cached-test)
[info] remote cache not found for 0.0.0-1d149c7cb425617484ffa7a7cb5c5de3845fac11

It would be very helpful to have the module / subproject name next to the "not found / extracted" messages to get an idea what SBT is talking about.

This was address in https://github.com/sbt/sbt/pull/5996 by @xuwei-k


text:
scala-library-2.13 on managedClasspath of Scala 3 project

steps
$ docker run -it --rm hseeberger/scala-sbt:11.0.12_1.5.5_3.0.1 sbt ++3.0.1! 'show managedClasspath'
...
[info] * Attributed(/root/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala3-library_3/3.0.1/scala3-library_3-3.0.1.jar)
[info] * Attributed(/root/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala-library/2.13.6/scala-library-2.13.6.jar)

problem
scala-library-2.13.6.jar is being added to the managedClasspath of Scala 3 project.
expectation
Only scala3-library_3-3.0.1.jar should be present in managedClasspath.
notes
Disabling Coursier doesn't seem to affect the behaviour (must be something in sbt itself then?):
$ docker run -it --rm hseeberger/scala-sbt:11.0.12_1.5.5_3.0.1 sbt ++3.0.1! 'set useCoursier := false; show managedClasspath'
...
[info] * Attributed(/root/.ivy2/cache/org.scala-lang/scala3-library_3/jars/scala3-library_3-3.0.1.jar)
[info] * Attributed(/root/.ivy2/cache/org.scala-lang/scala-library/jars/scala-library-2.13.6.jar)

Only scala3-library_3-3.0.1.jar should be present in managedClasspath.

Is this true? Scala 3 as far as I know is built on top of Scala 2.13's standard library (5.5MB). scala3-library contains the runtime for Scala 3 features, but I don't think it contains collection library etc.

@eed3si9n Indeed, thanks for pointing this out! Closing as invalid.


text:
sbtn should reevaluate env variables

steps
Given a hello world application that reads out an environment variable and prints it out:
@main def Main(args: String*): Unit =
  println(System.getenv("FOO"))

Then run:
FOO=BAR sbtn run

problems
I see null.
expectations
I see BAR
notes
When I run:
FOO=BAR bloop run my-project

I correctly see BAR
In fact the sbtn behavior is flaky. It depends on how the server was started. If the server was not running to begin with, then yes
FOO=BAR sbtn run

will indeed print out BAR and the subsequent requests as well. However as soon as we change it to
FOO=NOT_BAR sbtn run

we will keep seeing the incorrect BAR.
original report
I'm not sure whether it's an issue or a feature request. I already created a feature request here: https://discuss.lightbend.com/t/feature-request-sbtn-should-reevaluate-env-variables/9908 but haven't heard anything in over 2 weeks so I'm opening an issue here as well.

I think this issue is related:

#6468

I don't monitor Lightbend forums since I no longer work there. We have https://github.com/sbt/sbt/discussions for discussions, but I'm happy to discuss this issue/feature here.

Yeah no worries @eed3si9n it's just that submitting a feature request here points to the Lightbend forums which is why I submitted it there.
So is this a bug or a limitation of the current implementation?

it's just that submitting a feature request here points to the Lightbend forums which is why I submitted it there.

ahhhh, https://github.com/sbt/sbt/blob/1.8.x/.github/ISSUE_TEMPLATE/--feature-request.md needs updating, thanks for bringing that up. @eed3si9n I guess you know best what URL and wording you want

Thanks both. I've fixed the issue template https://github.com/sbt/sbt/commit/5bd44058ef6a96171cfa7cb2779b725fa40633a7.

So is this a bug or a limitation of the current implementation?

It's hard to say. Strictly speaking, as sbt, this is working as intended because sbt emulates run (JVM process) using a function call reusing the JVM already started by sbt server.
However, the spirit of sbtn is to make it work seamlessly with the shell environment (bash, zsh etc) so your expectation also makes sense as the future direction of sbtn. Somewhat related:

https://www.scala-sbt.org/1.x/docs/Running-Project-Code.html
https://www.scala-sbt.org/1.x/docs/In-Process-Classloaders.html
https://www.scala-sbt.org/1.x/docs/Forking.html

A feature that I've always wanted is letting individual client like sbtn execute the program when run is requested (#6178), which should largely solve this problem of env variable inheritance.

authors: SethTisue agilesteel eed3si9n laughedelic


text:
Fixes #2415. Hide global setting fix behind sbt.globalsettingfix

We are hiding a bug fix on global setting that was not importing auto
imports because fixing this via sbt/sbt#2399 breaks the source
compatibility: sbt/sbt#2415
I've split out the relevant portion of the scripted test into
global-settings, and marked it pending.
/cc @timcharper, @dwijnand

Thinking about this more I'm now in agreement with a feature flag. :+1:
Even if it's just for the remainder of 0.13, can we find a less opaque name than sbt.globalsettingfix? Not sure but perhaps something like sbt.enable.autoimports.in.global?
Also we should tweaks notes so people know can learn how to benefit from this fix.

Not sure but perhaps something like sbt.enable.autoimports.in.global?

Using dot (.) delimited English phrase I don't think is consistent with other flags we do have, which are partially documented to be fair in http://www.scala-sbt.org/0.13/docs/Command-Line-Reference.html and peppered around the code via sys.props and Boolean.getBoolean.
As per tweaking notes, could we do it after the merge? I'm about to get on a flight, and if possible I'd like to get RC2 sooner without involving Travis waiting.

I'm happy to tweak both the words and the formatting, just looking for something a little more informative. sbt.global.autoimports to match sbt.global.base?
Sure we can do notes later, let's just remember :) Have a safe flight and enjoy the conference.

@dwijnand Added a commit from :airplane:.

Ugh, I'd merge if I could. Punching Travis into going green.


text:
Update vite config for excluded dependencies

ipfs-http-client should not be in the list of dependencies that is excluded from eager bundling by vote. See the vite.config.ts file:

Update the excludeDeps array and remove ipfs-http-client
The app will compile and run as-is, but if you try to use ipfs-http-client, it'll cause a runtime error.

done in https://github.com/scaffold-eth/scaffold-eth-typescript/compare/feat/%2364-cleanup?expand=1

authors: ShravanSunder grothem

repo: scaffold-eth/scaffold-eth-typescript


text:
Native indexOf() for js.Array

indexOf() is implemented in js.Array using an implicit although JavaScript already provides an implementation out of the box. If I understand correctly, implicits incur a run-time overhead when used on native JavaScript collection types.

The implicits are inlined away by the Scala.js optimizer. So no, there is no runtime overhead.

Yes, implicits are inlined, but it still rolls out its own version of indexOf(). I just verified with the following code:
  def testA(): Int = {
    val arr = js.Array(1)
    arr.indexOf(1)
  }

  def testB(): Int = {
    val arr = js.Array(1)
    arr
      .asInstanceOf[js.Dynamic]
      .indexOf(1.asInstanceOf[js.Dynamic])
      .asInstanceOf[Int]
  }

This results in:
ScalaJS.c.Lorg_widok_todomvc_Main$.prototype.testA__I = (function() {
  var arr = [1];
  var len = ScalaJS.uI(arr["length"]);
  var i = 0;
  while (true) {
    if ((i < len)) {
      var index = i;
      var arg1 = arr[index];
      var jsx$1 = (!ScalaJS.m.sr_BoxesRunTime$().equals__O__O__Z(1, arg1))
    } else {
      var jsx$1 = false
    };
    if (jsx$1) {
      i = ((1 + i) | 0)
    } else {
      break
    }
  };
  var n = i;
  return ((n >= ScalaJS.uI(arr["length"])) ? (-1) : n)
});

ScalaJS.c.Lorg_widok_todomvc_Main$.prototype.testB__I = (function() {
  var arr = [1];
  return ScalaJS.uI(arr["indexOf"](1))
});

Ideally, it should use the native indexOf() for testA, too.

Ideally, it should use the native indexOf() for testA, too.

No, ideally it would do exactly what it does. Its own rolled out version of indexOf is faster than the "native" one. And it follows the Scala semantics of ==, which the "native" version doesn't do.

Thanks for pointing this out. Intuitively, I would have assumed the native version to be faster though, but apparently indexOf() also does a has-property check which makes it slower (see also http://jsperf.com/js-for-loop-vs-array-indexof).

authors: sjrd tindzk

repo: scala-js/scala-js


text:
PhantomJSEnv does not properly escape JS code in webpage

The following code will fail:
console.log("<script></script>");

Discovered while debugging #2322.

This is a hard problem:
PhantomJS seems to correctly interpret everything between <script> tags as CDATA, so simply escaping the tag doesn't work. Of course a closing </script> tag can only appear in a literal string, so usually the solution is to do:
console.log("<script></sc" + "ript>");

However, this is hard to back-fit on code (without parsing it) because JS has two types of quotes.
An easy fix would be to just write stuff to temp files and include it, completely mitigating the escaping issue. However, this wont work trivially for runner code, since we need to wrap it in an onload handler (see writeCodeLauncher).
An option would be to wrap it in a magic function, write it to a file, include the file via script tag and register the onload handler on the magic function. But that seems very ugly.