text:
下载安装后百度云界面不显示PD下载按钮

问题描述(必要)
如题，下载安装后百度云界面不显示PD下载按钮
版本号(必要)
3.4  MacOS x64
操作系统(必要)
MacOS Mojave 10.14
相关截图
相关日志
2018-12-15 22:11:56.866 [nioEventLoopGroup-3-1] ERROR org.pdown.gui.http.EmbedHttpServer - native request error
java.lang.RuntimeException: http get error:http://127.0.0.1:55714/proxy/disabled?ns=null
at org.pdown.gui.util.ExecUtil.httpGet(ExecUtil.java:81)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.disabledProxy(ExtensionProxyUtil.java:105)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.enabledPACProxy(ExtensionProxyUtil.java:51)
at org.pdown.gui.util.AppUtil.refreshPAC(AppUtil.java:52)
at org.pdown.gui.http.controller.NativeController.changeProxyMode(NativeController.java:355)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.pdown.gui.http.EmbedHttpServer.invoke(EmbedHttpServer.java:60)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:103)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:97)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:647)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:582)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:499)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:461)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
2018-12-15 22:14:53.084 [nioEventLoopGroup-3-1] ERROR org.pdown.gui.http.EmbedHttpServer - native request error
java.lang.RuntimeException: http get error:http://127.0.0.1:55714/proxy/disabled?ns=null
at org.pdown.gui.util.ExecUtil.httpGet(ExecUtil.java:81)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.disabledProxy(ExtensionProxyUtil.java:105)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.enabledPACProxy(ExtensionProxyUtil.java:51)
at org.pdown.gui.util.AppUtil.refreshPAC(AppUtil.java:52)
at org.pdown.gui.http.controller.NativeController.extensionCommon(NativeController.java:316)
at org.pdown.gui.http.controller.NativeController.installExtension(NativeController.java:257)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.pdown.gui.http.EmbedHttpServer.invoke(EmbedHttpServer.java:60)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:103)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:97)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:647)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:582)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:499)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:461)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
2018-12-15 22:14:58.191 [nioEventLoopGroup-3-1] ERROR org.pdown.gui.http.EmbedHttpServer - native request error
java.lang.RuntimeException: http get error:http://127.0.0.1:55714/proxy/disabled?ns=null
at org.pdown.gui.util.ExecUtil.httpGet(ExecUtil.java:81)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.disabledProxy(ExtensionProxyUtil.java:105)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.enabledPACProxy(ExtensionProxyUtil.java:51)
at org.pdown.gui.util.AppUtil.refreshPAC(AppUtil.java:52)
at org.pdown.gui.http.controller.NativeController.extensionCommon(NativeController.java:316)
at org.pdown.gui.http.controller.NativeController.installExtension(NativeController.java:257)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.pdown.gui.http.EmbedHttpServer.invoke(EmbedHttpServer.java:60)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:103)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:97)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:647)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:582)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:499)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:461)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
2018-12-15 22:15:01.397 [nioEventLoopGroup-3-1] ERROR org.pdown.gui.http.EmbedHttpServer - native request error
java.lang.RuntimeException: http get error:http://127.0.0.1:55714/proxy/disabled?ns=null
at org.pdown.gui.util.ExecUtil.httpGet(ExecUtil.java:81)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.disabledProxy(ExtensionProxyUtil.java:105)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.enabledPACProxy(ExtensionProxyUtil.java:51)
at org.pdown.gui.util.AppUtil.refreshPAC(AppUtil.java:52)
at org.pdown.gui.http.controller.NativeController.changeProxyMode(NativeController.java:355)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.pdown.gui.http.EmbedHttpServer.invoke(EmbedHttpServer.java:60)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:103)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:97)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:647)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:582)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:499)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:461)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
2018-12-15 22:15:02.795 [nioEventLoopGroup-3-1] ERROR org.pdown.gui.http.EmbedHttpServer - native request error
java.lang.RuntimeException: http get error:http://127.0.0.1:55714/proxy/disabled?ns=null
at org.pdown.gui.util.ExecUtil.httpGet(ExecUtil.java:81)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.disabledProxy(ExtensionProxyUtil.java:105)
at org.pdown.gui.http.controller.NativeController.changeProxyMode(NativeController.java:357)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.pdown.gui.http.EmbedHttpServer.invoke(EmbedHttpServer.java:60)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:103)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:97)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:647)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:582)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:499)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:461)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
2018-12-15 22:16:51.771 [nioEventLoopGroup-3-2] ERROR org.pdown.gui.http.EmbedHttpServer - native request error
java.lang.RuntimeException: http get error:http://127.0.0.1:55714/proxy/disabled?ns=null
at org.pdown.gui.util.ExecUtil.httpGet(ExecUtil.java:81)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.disabledProxy(ExtensionProxyUtil.java:105)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.enabledPACProxy(ExtensionProxyUtil.java:51)
at org.pdown.gui.util.AppUtil.refreshPAC(AppUtil.java:52)
at org.pdown.gui.http.controller.NativeController.changeProxyMode(NativeController.java:355)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.pdown.gui.http.EmbedHttpServer.invoke(EmbedHttpServer.java:60)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:103)
at org.pdown.gui.http.EmbedHttpServer$1$1.channelRead0(EmbedHttpServer.java:97)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:647)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:582)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:499)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:461)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
2018-12-15 22:25:05.251 [JavaFX Application Thread] ERROR org.pdown.gui.DownApplication - Extension content load error
java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
at sun.net.www.http.HttpClient.(HttpClient.java:242)
at sun.net.www.http.HttpClient.New(HttpClient.java:339)
at sun.net.www.http.HttpClient.New(HttpClient.java:357)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
at org.pdown.gui.util.ExecUtil.httpGet(ExecUtil.java:80)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.disabledProxy(ExtensionProxyUtil.java:105)
at org.pdown.gui.extension.mitm.util.ExtensionProxyUtil.enabledPACProxy(ExtensionProxyUtil.java:51)
at org.pdown.gui.util.AppUtil.refreshPAC(AppUtil.java:52)
at org.pdown.gui.DownApplication.initExtension(DownApplication.java:159)
at org.pdown.gui.DownApplication.start(DownApplication.java:92)
at com.sun.javafx.application.LauncherImpl.lambda$launchApplication1$161(LauncherImpl.java:863)
at com.sun.javafx.application.PlatformImpl.lambda$runAndWait$174(PlatformImpl.java:326)
at com.sun.javafx.application.PlatformImpl.lambda$null$172(PlatformImpl.java:295)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.javafx.application.PlatformImpl.lambda$runLater$173(PlatformImpl.java:294)
at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:95)

同样的问题

同样的问题

没安装专用证书

没安装专用证书

证书安装了的 在钥匙串里看到是受信任的

关了重新打开全网嗅测插件，PD按钮又显示了。

同樣問題，期待更新！！

authors: Fable21 Jayxiang daiyoyo dhqdqk yyearth

repo: proxyee-down-org/proxyee-down


text:
Ensure specs_size is an int

Setting VSPHERE_SPECS_SIZE environment variable results in a specs_size that is actually a string.  This is the exception:
vmware_exporter    | 2020-01-14 20:07:00,759 INFO:Fetched vim.VirtualMachine inventory (0:00:00.472943)
vmware_exporter    | 2020-01-14 20:07:00,783 ERROR:Traceback (most recent call last):
vmware_exporter    |   File "/usr/local/lib/python3.6/site-packages/vmware_exporter/vmware_exporter.py", line 997, in _async_render_GET
vmware_exporter    |     yield self.generate_latest_metrics(request)
vmware_exporter    | twisted.internet.defer.FirstError: FirstError[#1, [Failure instance: Traceback: <class 'TypeError'>: 'str' object cannot be interpreted as an integer
vmware_exporter    | /usr/local/lib/python3.6/site-packages/twisted/internet/defer.py:460:callback
vmware_exporter    | /usr/local/lib/python3.6/site-packages/twisted/internet/defer.py:568:_startRunCallbacks
vmware_exporter    | /usr/local/lib/python3.6/site-packages/twisted/internet/defer.py:654:_runCallbacks
vmware_exporter    | /usr/local/lib/python3.6/site-packages/twisted/internet/defer.py:1475:gotResult
vmware_exporter    | --- <exception caught here> ---
vmware_exporter    | /usr/local/lib/python3.6/site-packages/twisted/internet/defer.py:1418:_inlineCallbacks
vmware_exporter    | /usr/local/lib/python3.6/site-packages/vmware_exporter/vmware_exporter.py:640:_vmware_get_vm_perf_manager_metrics
vmware_exporter    | ]]
vmware_exporter    |

I built a docker image with this change and no longer get an exception.

@treydock Thank you for your contribution. It is appreciated and this will go out as a fix shortly.

@treydock Thank you for your contribution. It is appreciated and this will go out as a fix shortly.

I have to take this back is there any way you could update the failing test.
=================================== FAILURES ===================================

____________________________ test_vmware_disconnect ____________________________

    @pytest_twisted.inlineCallbacks

    def test_vmware_disconnect():

        collect_only = {

            'vms': True,

            'vmguests': True,

            'datastores': True,

            'hosts': True,

            'snapshots': True,

        }

        collector = VmwareCollector(

            '127.0.0.1',

            'root',

            'password',

            5000,

>           collect_only,

        )

tests/unit/test_vmware_exporter.py:1076:

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <vmware_exporter.vmware_exporter.VmwareCollector object at 0x7fc0a15e5cc0>

host = '127.0.0.1', username = 'root', password = 'password'

collect_only = 5000

specs_size = {'datastores': True, 'hosts': True, 'snapshots': True, 'vmguests': True, ...}

ignore_ssl = False

    def __init__(self, host, username, password, collect_only, specs_size, ignore_ssl=False):

        self.host = host

        self.username = username

        self.password = password

        self.ignore_ssl = ignore_ssl

        self.collect_only = collect_only

>       self.specs_size = int(specs_size)

E       TypeError: int() argument must be a string, a bytes-like object or a number, not 'dict'

vmware_exporter/vmware_exporter.py:47: TypeError

Fix test failures, the order of arguments was incorrect and new int() caught that issue.

Codecov Report

Merging #174 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #174   +/-   ##
=======================================
  Coverage   93.77%   93.77%
=======================================
  Files           4        4
  Lines         546      546
=======================================
  Hits          512      512
  Misses         34       34

Impacted Files
Coverage Δ

vmware_exporter/vmware_exporter.py
93% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Ill merge in just a bit.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.77%. Comparing base (9fcde29) to head (100fd81).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #174   +/-   ##
=======================================
  Coverage   93.77%   93.77%
=======================================
  Files           4        4
  Lines         546      546
=======================================
  Hits          512      512
  Misses         34       34

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

source: gharchive/pull-request

authors: codecov-commenter codecov-io pryorda treydock

license_type: permissive

license_source: github-api


text:
Error importing pester module from psake

Hello!
I'm struggling with importing Pester and creating a psake task that can run tests. I'm not exactly sure how psake imports modules, but it seems to conflict with how pester is creating objects. Here is my setup:
psake-config.ps1:
$config.modules=(
    "..\PSModules\Pester"
)
$config.verboseError=$true

stage.ps1:
Task Default -Depends Test
Task Test {
    $testResults = Invoke-Pester -Path $PSScriptRoot -PassThru
    if ($testResults.FailedCount -gt 0) {
        $testResults | Format-List
        Write-Error -Message 'One or more Pester tests failed!'
    }
}

And I get the following exception from Pester:
5/10/2016 12:29:50 PM: An Error Occurred. See Error Details Below:
----------------------------------------------------------------------
 +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [<<==>>] Exception: The property 'CommandCovera
ge' cannot be found on this object. Verify that the property exists and can be set.
----------------------------------------------------------------------

ErrorRecord:

PSMessageDetails      :
Exception             : System.Management.Automation.RuntimeException: The property 'CommandCoverage' cannot be found
                        on this object. Verify that the property exists and can be set.
                           at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext
                        funcContext, Exception exception)
                           at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame
                        frame)
                           at
                        System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
                        frame)
                           at
                        System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
                        frame)
                           at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
                           at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
                           at System.Management.Automation.PSScriptCmdlet.RunClause(Action`1 clause, Object
                        dollarUnderbar, Object inputToProcess)
                           at System.Management.Automation.PSScriptCmdlet.DoEndProcessing()
                           at System.Management.Automation.CommandProcessorBase.Complete()
TargetObject          :
CategoryInfo          : InvalidOperation: (:) [Enter-CoverageAnalysis], RuntimeException
FullyQualifiedErrorId : PropertyNotFound,Enter-CoverageAnalysis
ErrorDetails          :
InvocationInfo        : System.Management.Automation.InvocationInfo
ScriptStackTrace      : at Enter-CoverageAnalysis, C:\git\ops\release-scripts\PSModules\Pester\Functions\Coverage.ps1:
                        line 29
                        at Invoke-Pester, C:\git\ops\release-scripts\PSModules\Pester\Pester.psm1: line 266
                        at <ScriptBlock>, C:\git\ops\release-scripts\staging\stage.ps1: line 33
                        at Invoke-Task, C:\git\ops\release-scripts\PSModules\psake\psake.psm1: line 99
                        at Invoke-Task, C:\git\ops\release-scripts\PSModules\psake\psake.psm1: line 125
                        at <ScriptBlock>, C:\git\ops\release-scripts\PSModules\psake\psake.psm1: line 400
                        at ExecuteInBuildFileScope, C:\git\ops\release-scripts\PSModules\psake\psake.psm1: line 697
                        at Invoke-psake, C:\git\ops\release-scripts\PSModules\psake\psake.psm1: line 361
                        at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}

I'm using psake 4.6.0 and Pester 3.4.0. This problem seems to only exist when I try to import the module using psake. Importing Pester beforehand doesn't seem to cause the issue at all.
Any guidance would be gladly appreciated, and perhaps if this issue is not relevant to psake's inner workings, I can post on the Pester issue board.

I wasn't able to reproduce the problem, using the same version of psake / Pester.  Not sure what's going on here.

@dlwyatt
Thanks for taking a look.
Just to be complete, I made this repository to make sure we're on the same page. I was able to reproduce the problem on a couple different machines using both Powershell 4 and Powershell 5.

Still wasn't able to repro.  :(
C:\Users\dlwya_000\Documents\GitHub
λ git clone https://github.com/csharris/psake-pester-test.git
Cloning into 'psake-pester-test'...
remote: Counting objects: 240, done.
remote: Compressing objects: 100% (201/201), done.
remote: Total 240 (delta 32), reused 239 (delta 31), pack-reused 0R
Receiving objects: 100% (240/240), 1.12 MiB | 0 bytes/s, done.
Resolving deltas: 100% (32/32), done.
Checking connectivity... done.
C:\Users\dlwya_000\Documents\GitHub
λ cd .\psake-pester-test\
C:\Users\dlwya_000\Documents\GitHub\psake-pester-test [master]
λ ls

    Directory: C:\Users\dlwya_000\Documents\GitHub\psake-pester-test

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        5/10/2016   4:24 PM                Pester
d-----        5/10/2016   4:24 PM                psake
-a----        5/10/2016   4:24 PM            302 default.ps1
-a----        5/10/2016   4:24 PM             82 default.tests.ps1
-a----        5/10/2016   4:24 PM             64 psake-config.ps1

C:\Users\dlwya_000\Documents\GitHub\psake-pester-test [master]
λ invoke-psake
psake version 4.6.0
Copyright (c) 2010-2014 James Kovacs & Contributors

Loading module: C:\Users\dlwya_000\Documents\GitHub\psake-pester-test\Pester

Executing Test

Describing Test
 [+] Tests 89ms
Tests completed in 89ms
Passed: 1 Failed: 0 Skipped: 0 Pending: 0 Inconclusive: 0

Build Succeeded!

----------------------------------------------------------------------
Build Time Report
----------------------------------------------------------------------
Name   Duration
----   --------
Test   00:00:00.1511335
Total: 00:00:00.1533883
C:\Users\dlwya_000\Documents\GitHub\psake-pester-test [master]

I'm just running a plain Windows 10 system, by the way (currently PS version 5.0.10586.122 ).  No insider builds or anything like that.

In the case of Windows 10, I think Pester comes installed by default (version 3.3.5). Would you mind running Get-Module?
Also, I found that if I run Install-Module Pester -Force on Windows 10, pester is then added to C:\ProgramFiles\WindowsPowershell\Modules\Pester\3.4.0. If I restart powershell and then run psake, everything works fine. Unfortunately, this isn't a viable option for me.

@csharris the restart isn't a viable option or performing an upgrade? You could install the newer version via something like Chocolatey and then just call powershell.exe ./psake.ps1 so it will be in the path when psake gets called.

source: gharchive/issue

authors: csharris dlwyatt dragon788

repo: psake/psake

license: mit

license_source: bigquery


text:
Simple block allocator

See #3

As for the map vs set discussion, set is definitely fine for now, but since blocks have fixed size, later we should even consider a bitset - with a 1TB disk and 32MB-sized chunks, bitset's size would be around 4KB and it will definitely be faster than a set. But, it's premature optimization for now, set is OK.
Also, general request - please squash all the fixup commits with git rebase -i and force-repush so that git history remains clear. Series for Seastar are only merged if they are clear, i.e. they don't include fixes to themselves. In this particular case, all these commits can be squashed into a single Add block allocator commit. Finally, please add some unittests for the feature.

plz rebase on top of current head of zpp_fs and I'll merge it

authors: psarna wmitros

repo: psarna/seastar


text:
BUG: KeyboardInterrupt and EOFError can leave repository in a non-clean state

Some commands, but especially onyo set and onyo unset leave the repository in a dirty state, when the user uses CTRL+C while a user-response is requested to save the changes.
One can add in python except (KeyboardInterrupt, EOFError) as e: and I think we should figure out what the correct way is to make sure that a user-interrupt or an EOFError gets handled correctly.

We might simply add the KeyboardInterrupt to the function request_user_response() (and maybe at other places?) and interprete this as a valid response, because currently when the user does Interrupt onyo, it will leave the repository in a "dirty" state, instead of restoring before leaving.
About the EOFError I am not as sure as I am about the KeyboardInterrupt, it would provide the same value of not leaving the repository in a dirty state, but at the same time, when writing an onyo script, we might not want to run the next commands, but leave with the Error?
Alternatively, we might throw our own type of error instead, restore the repository, and then do a sys.exit(1).

The biggest problem I see, and this is not specific for this issue, but possibly most urgently in this context, is that when we would in request_user_response() add
except (KeyboardInterrupt, EOFError) as e:
    repo.restore()
    sys.exit(1)

That this would lead to problems when the user has unstaged/uncommitted changes in the repository. Our fscks currently should prevent that from being a problem, but since we want to modify that behavior, and even allow --skip-tests later, this might lead to information loss. Maybe we need to upgrade the restore-function to make sure it just restores assets or something, not everything.
In general I think there should happen something, to leave the repository not in a weird state, but we should probably discuss in a more complete way, what exactly is the behavior we want, and with which downsides we can live.

FTR:
I think the biggest issue here is the internal flow that actually does changes before it knows that it should do them. If user confirmation is required: Get the confirmation first, not write and rollback. Same for dryruns: Something called a dryrun is not supposed to actually change anything. Ever. Doing it for real and rolling back is not what a dryrun is for.
Same flavor again for collecting a multitude of changes: Often things are changed and staged long before we know we can actually perform the operation. So, it's spending time on doing this onyl to then spend more time rolling it back to then eventually fail, because an input argument couldn't be acted upon.
Instead: Assemble a "TODO-list" and only when it's complete - act on it.
Otherwise, I agree: things like KeyboardInterrupt need to be accounted for, but currently the problem is bigger than it ought to be - independently on how such an exception is handled.

In onyo/lib/command_utils.py we now use:
from difflib import unified_diff
This replaces the "editing" of files before the user verified that changes should be written. This should solve the underlying issue; thereby I close this issue.

authors: TobiasKadelka bpoldrack

repo: psyinfra/onyo

license: ISC


text:
BF: allow onyo new with just --clone or --template

close #645

It's the little things :)
LGTM!

authors: TobiasKadelka aqw


text:
大佬，右测点下载到，总是会卡1-2秒，是因为设置目录过多的原因吗

大佬，右测点下载到，总是会卡1-2秒，是因为设置目录过多的原因吗  可以解决吗

这个点出来会卡1-2秒才会出现

mt 需要先解析下载链接

repo: pt-plugins/PT-Plugin-Plus

license: MIT


text:
big OTA won't start

Hi, PTVO.
I have another problem.
I added the MX25R8035FZUIL0 flash memory to one of my Zigbbe devices. I uploaded new firmware with OTA. After rebooting the device, the LED blinks rapidly for a few seconds indicating the firmware is being copied to flash. Service command 131 returns the correct signature "C2 28 14" in attribute 16385. The device is working properly.
I have prepared a full firmware update via OTA according to the instructions on the website. After trying to upload for several dozen seconds on the Zigbbee@MQTT I can see an empty progress bar and "estimated time: N/A". Then there is an error in the logs:
2023-04-25 22:25:24Received MQTT message on 'z2m/bridge/request/device/ota_update/update' with data '{"id":"0x00124b00257934ab","transaction":"a0678-23"}'
info 2023-04-25 22:25:24Updating '0x00124b00257934ab' to latest firmware

2023-04-25 22:25:25Update of '0x00124b00257934ab' at 0.00%
info  2023-04-25 22:27:53: MQTT publish: topic 'z2m/0x00124b00257934ab', payload'{"bind_command_l7":null,"bind_command_l8":null,"contact_l7":false,"contact_l8":true,"device":"applicationVersion":1,"dateCode":"2023-04-25","friendlyName":"0x00124b00257934ab","hardwareVersion":1,"ieeeAddr":"0x00124b00257934ab","manufacturerID":0,"manufacturerName":"ARTi","model":"ptvo.GWC-E72","networkAddress":27045,"powerSource":"Mains (single phase)","softwareBuildID":"2023-04-25","stackVersion":3,"type":"Router","zclVersion":1},"l1":20,"last_seen":"2023-04-25T22:27:49+02:00","link_to_output_l7":null,"link_to_output_l8":null,"linkquality":211,"state_l2":"OFF","state_l3":"OFF","state_l4":"OFF","state_l5":"OFF","switch_actions_l7":null,"switch_actions_l8":null,"switch_type_l7":null,"switch_type_l8":null,"update":{"state":"available"},"update_available":null}'
info  2023-04-25 22:27:53: MQTT publish: topic 'z2m/bridge/response/device/ota_update/update', payload '{"data":{"id":"0x00124b00257934ab"},"error":"Update of '0x00124b00257934ab' failed (Timeout: device did not request any image blocks)","status":"error","transaction":"a0678-23"}'
error 2023-04-25 22:27:53: Update of '0x00124b00257934ab' failed (Timeout: device did not request any image blocks)
debug 2023-04-25 22:27:53: Error: Timeout: device did not request any image blocks
    at /app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:360:28
    at runMicrotasks (<anonymous>)
    at runNextTicks (node:internal/process/task_queues:61:5)
    at listOnTimeout (node:internal/timers:528:9)
    at processTimers (node:internal/timers:502:7)

But if I prepare a small OTA update (settings only), the device updates itself after a dozen or so seconds, reporting the correct update in the logs.

No, it's regular router. I'll try some more tests.

I think I found the reason why the device is not downloading the update even though the update is reported in the logs.
The cause is the watchdog enabled in the firmware installed on the device. After disabling the watchdog and installing such firmware, the traditional "via cable", the next large and small OTAs pass without problems. Previously, only small (configuration) OTAs were passed with the watchdog turned on, and not always.
PTVO - can you test it yourself and possibly confirm if it's just my problem with this one DIY device, or if a firmware fix is needed.

@axelhorn I cannot repeat this problem with my test board.

Hmmm.... It's amazing. I try it with another of my devices (PSM too) and write here results of tests. This one above still updates fine every time, but only when watchdog is disabled.

authors: axelhorn ptvoinfo

repo: ptvoinfo/zigbee-configurable-firmware


text:
WIP: this is broken AF, just trying to figure out how to set up as a monorepo

This will not get merged - i'm following some tutorials for preconstruct and will submit a PR with a fresh setup that can be promoted to main once all the kinks are worked out... or could just be a new repo...

For a little more context using yarn workspaces for monorepo setup:
https://classic.yarnpkg.com/lang/en/docs/workspaces/

repo: public-assembly/npm-package-boilerplate


text:
Ability to use PMP's PubSubHubbub notifications rig instead of cron

NOTE: this is a work in progress and needs testing.
This pull request:

Adds an "Allow PMP API to send content updates?" option to the settings panel:

When saving settings, if the "Enable" option is checked, the PMP plugin runs the subscription and verification workflow.
When savings settings, if the "Enable" option is unchecked, the PMP plugin runs the unsubscribe process.
When this option is enabled, the PMP plugin does not poll for updates to content via cron.
Also blesses "/?pmp-notifications" as a valid query parameter and uses said query parameter in the callback url used for communicating with the PMP hub.

Still needs:

Documentation
Probably would be a good idea to link to the PMP docs for the notification system
Unit tests
???

When trying to save that form with the content-updates checkbox checked, I get:
Fatal error: Call to undefined function pmp_send_subscription_request() in /home/pmpbot/wordsand.pmpdev.org/public_html/wp-content/plugins/pmp-github/inc/settings.php on line 103

Ah, nevermind.  User fail.
It now successfully saves.  However, I'm not seeing that subscription show up in the PMP database.  And there's no trace of the HTTP request in the logs.
Did you verify that the subscription part actually works?  Looks like it should fail if it doesn't get a 204.

Here's the actual HTTP response when the box is checked:
  'body' => 'Verification error: Subscriber callback provided wrong challenge code',
  'response' =>
  array (
    'code' => 412,
    'message' => 'Precondition Failed',
  ),

Okay, I've made a couple changes to get this working for me.  You may want to review them, and make sure it sounds sane.  (Particularly the logic I inverted for subscribe/unsubscribe).

Making a list of things I'm QA-ing on #89

Also note: I'm getting this message in my PHP error log, every time there's a notification callback:
[10-Aug-2015 18:26:14 UTC] PHP Deprecated:  Automatically populating $HTTP_RAW_POST_DATA is deprecated and will be removed in a future version. To avoid this warning set 'always_populate_raw_post_data' to '-1' in php.ini and use the php://input stream instead. in Unknown on line 0
[10-Aug-2015 18:26:14 UTC] PHP Warning:  Cannot modify header information - headers already sent in Unknown on line 0

Doesn't really give correct line numbers - but seems to be coming from pmp_do_notification_callback.  Maybe getallheaders() and file_get_contents('php://input') ?

Okay, after fixing a PMP side bug, here's what I think is left to address:

[ ] Also subscribe to "delete" topic (per #89)
[ ] Respect individual "subscribe to updates" Post flags (per #89)
[ ] Address (or at least explain) the above deprecation/warning I'm getting in the logs
[ ] Default to "on" for this option.  Unless that's a bad idea.  Is there any way to check if a site has a real/public domain name when the plugin is initialized?

@cavis I pushed several changes which address (most of) the issues identified.
Regarding the deprecation message:
It looks like, if you're using $HTTP_RAW_POST_DATA on newer versions of php, you'll receive this warning unless you set always_populate_raw_post_data in your php.ini. I have no sane explanation for this since we're not actually using $HTTP_RAW_POST_DATA anywhere in the plugin. It could be that something in WordPress core is triggering the deprecation warning because of the way we're interacting with php://input, but I can't confirm.
Regarding defaulting to "on":
IMO I don't think we should make the notifications rig the default method of receiving updates, at least not right away. I'd like to see how this model works in the wild to work out any issues we may encounter before forcing the option on new users.

Confirmed that this all works.  Had to shorten the transient key down to 40, to make it work in my system, though.
Setting always_populate_raw_post_data fixed my warnings.
And agreed - I'm good with defaulting to "no push notifications", for now.

authors: cavis rnagle

repo: publicmediaplatform/pmp-wordpress


text:
Latest DB Schema Details

Hi @manimaarans
We need it separately for each service. ChatGPT can tell you how to get the schema out so DBdiagram.io or other tools can generate the diagram. Shouldn't be more than 1 hour of work.

yes @manimaarans

@manimaarans you can put this in - docs/DB_Design

repo: pucardotorg/dristi


text:
Getting error - UNMET PEER DEPENDENCY

Getting this error.

As it says, you probably need to install pug

authors: battlesnake mittalyashu

repo: pugjs/pug-loader


text:
JXPaginView 升级到最新版，segmentedControl.listContainer = pagingView.listContainerView 赋值报错

extension JXPagingListContainerView: JXSegmentedViewListContainer {}

可以了，谢谢呀


text:
Clean up dump files on sftp server

We'll need a job that cleans up the full and incremental publishing job dump files on the ftp server to keep it from growing out of control.
these files are in /alma/publishing
We can delete anything older than 1 month. (note the files are stored longer in bibdata; see https://github.com/pulibrary/bibdata/blob/50b293cd5fcdb02ff8716984c6f953c6a24ecc14/lib/tasks/marc_liberation.rake)

Normally the way this would get handled is a cron job on lib-sftp that just does find /alma/* -mtime +30 -exec rm {} \;, but it doesn't look like lib-sftp is handled by ansible. @kayiwa should we add an ansible role that only does that somehow? Or maybe we should just add this to that box?

We should enter the cron manually and document it in pul-the-hard-way. Put the cron job on the user who owns the files.

authors: hackartisan tpendragon

repo: pulibrary/bibdata


text:
increased contrast for navbar

closes #1217

@hackartisan I'll add a screenshot soon! It's still in draft since I plan to talk to Shaun about making this change. In order for the accessibility test to pass, the navbar loses nearly all its transparency. There might be some acceptable balance since the color behind the navbar is not usually white (which the accessibility test assumes it is).

@XanderGardner makes sense -- thanks!

Looking at the original issue, the contrast problem is in the breadcrumb (which is below the exhibit navbar), not the exhibit navbar. This PR seems to adjust the contrast of that navbar, which doesn't have an accessibility problem as far as I'm currently aware.

Thank you @thanyabegum! I've just fixed the breadcrumb contrast issue.
Unfortunately it seems the test still fails on the navbar. This screenshot is from rspec showing the breadcrumb fix and how the navbar appears to have a much darker background in testing due to its transparency.

authors: XanderGardner hackartisan thanyabegum

repo: pulibrary/dpul


text:
Updating exception_file parameter to be required

fixes #953

Coverage increased (+0.03%) to 82.569% when pulling c6fec82b3c2e20d50583a6f16b587415253df7f5 on i#953-file-required into 47cf4e0e7de98f1de8155025cf5a73289ba5f8e5 on main.

authors: carolyncole coveralls


text:
Testbench for running simulations

Hi,
I was going through the source directory but couldn't find an existing Testbench which could be used to run sims. Is there a chance that the TB would also made open-source?

Hi, we don’t have exactly an open source standalone testbench for Zero-Riscy, but you can

use PULPissimo as a simulation platform
use PULPino as a simulation platform (but beware, the SW environment is legacy)
slightly modify other testbenches. Here (https://github.com/pulp-platform/hwpe-tb) you find a testbench for accelerators which also includes a Zero-Riscy core and dummy memories

Thank you for the comment. I'll take a look at them.
Closing!

authors: FrancescoConti raulbehl

repo: pulp-platform/zero-riscy


text:
Update the KEDA blog post

Updates some content in a post form last year to bring it more current. See https://github.com/pulumi/docs/pull/2972#issuecomment-614963222 for context.

lgtm

authors: cnunciato ericrudder

repo: pulumi/docs


text:
Errors when destroying Service Principal Passwords - azuread

Seeing weird errors when destroying Service Principal Password:
Diagnostics:
  azuread:index:ServicePrincipalPassword (k8s-dev-SpPassword-ExtDNS):
    error: deleting urn:pulumi:k8s::tms-pulumi::azuread:index/servicePrincipalPassword:ServicePrincipalPassword::k8s-dev-SpPassword-ExtDNS: Error parsing Application Password ID: Credential ID should be in
the format {objectId}/{keyType}/{keyId} - but got "f0aad1c4-****-4629-929e-b4f2da41****/33ee0852-****-****-17d0-33b52a02****"

This happened with:

pulumi: 2.4.0
pulumi/azure: 3.8.0
pulumi/azuread: 2.3.0

I tried downgrading a couple of versions but got same error.
In the end I had to export the stack, remove in the json and then import.
I have earlier successfully destroyed stacks with SpPasswords, so guessing something must have changed.

It sounds like a consequence of https://github.com/terraform-providers/terraform-provider-azuread/pull/264
Does it work if you create this resource again with the newest version, and then delete it?

As mentioned above, I assume the problem was caused by a breaking change between two old versions. Since no comments were posted since 2020, I'll go ahead and close the issue as resolved.

authors: mikhailshilkov pjoe

repo: pulumi/pulumi-azure


text:
Packet 18 (opcode) is missing.

worker: [warning] unknown packet ID(18): 12

In original code (http://agar.io/main_out.js) it resets all cells. It's defined here too: http://agar.gcommer.com/index.php?title=Protocol#Reset_all_cells_.28opcode_18.29
Can you fix it please?

@SzAmmi already fixed, update your agaio-client:
'18': function() {
            for(var k in this.balls) if(this.balls.hasOwnProperty(k)) this.balls[k].destroy({'reason':'server-forced'});
        },

Thanks.

authors: SzAmmi agarioBotDev

repo: pulviscriptor/agario-client


text:
Bring back area save on unload/refresh

Currently this is not happening in 0.6.

I believe areas area saving on unload now.

authors: boutell jth-

repo: punkave/apostrophe


text:
Add auto-refresh on index page

Add an auto refresh to the index page.

Hmm, I don't think we should do this for refreshing personally.  Instead, we really need to investigate an AJAX-based solution like Angular.js or similar.  I'll test this out tomorrow but I'm pretty set on using a strategy that involved Javascript to dynamically update elements on the page instead of refreshing the entire page via a meta tag.

I am personally happy with this solution until an AJAX solution emerges. @tjayl can you rebase this and we can merge it?

@tjayl rebase?

Sorry dude,
I have put all my changes in 245e625

@tjayl could you take a look again? it seems like a rebase is needed here.

I am unsure what you are expecting of me here. I have put all of the changes for this into one commit.
If i do a git rebase i only get 'Current branch master is up to date.'

You've to do a rebase against the master:
git checkout master
git pull # to update your master to the latest one
git checkout auto-refresh
git rebase -i master

this is untested and based on my memory, use the commands with caution. If you experience any issues you can ask here or also in #puppet-community on freenode

Thanks bastelfreak.
I have done that and pushed it back to my repo.

did you push it in the wrong branch? I can't see anything changed here :(
git is pure magic

I pushed it into the master branch on my repo:
git remote -v
origin	https://github.com/tjayl/puppetboard.git (fetch)
origin	https://github.com/tjayl/puppetboard.git (push)

git branch -v
  auto-refresh 245e625 Add auto refresh to the index page
* master       245e625 Add auto refresh to the index page

You need to add the original repo as an upstream.
https://help.github.com/articles/configuring-a-remote-for-a-fork/

Or follow these steps.
https://help.github.com/articles/merging-an-upstream-repository-into-your-fork/

Thanks for those guides.
I think i have managed to do it.

After the rebase you've to push (probably push -f) into your auto-refresh branch, than the changes will appear here. I can't see anything changed here. If you want, we can fiddle that out if you join #puppet-community.

Got it.
If there are still issues, i will jump on IRC to resolve them

great, you based it \o/
but you missed two pieces off git diff code. could you rebase again and squash it down to one commit?

rebase done

the code looks fine, could you squash the two commits into one? Than we should finally be ready to merge \o/

https://ariejan.net/2011/07/05/git-squash-your-latests-commits-into-one/

It doesn't seem to want to squash 245e625 and d44152f
I am guessing because 245e625 was committed over a year ago

Would it be possible for you to create a new branch with just a single commit and a new PR? That could be easier than squashing this one.

Done it (at last)

thanks, looks perfect!
can somebody merge this or do the docs need to be extended?

authors: bastelfreak fgimian janorn nibalizer tjayl

repo: puppet-community/puppetboard


text:
page.hover(selector) throws undefined

page.hover(selector) does not work
Tell us about your environment:

Puppeteer version: 1.8.0
Platform / OS version: Mac OS
Node.js version: v8.9.1

Puppeteer config:
  browser = await puppeteer.launch({ headless: true });
    page = await browser.newPage();
    const override = Object.assign(page.viewport(), { width: 1920 });
    await page.setViewport(override);
    await page.goto(`http://127.0.0.1:3000`, { waitUntil: 'networkidle0' });

What steps will reproduce the problem?

Here is a snippet of my code that tries to do hover on element and take screenshot.

const hoverScreenshot = async (page, dataHook, directory) => {
  const element = await page.hover(`[data-hook="${dataHook}`);
  await page.waitFor(50);
  await element.screenshot({
    omitBackground: true,
    path: `e2e/screenshots/${directory}/${dataHook}-hover.png`
  });
})

See error.

What is the expected result?
Taken screenshot of hovered element.
What happens instead?
Throws an error:
TypeError: Cannot read property 'screenshot' of undefined

      35 |   const element = await page.hover(`[data-hook="${dataHook}`);
      36 |   await page.waitFor(500);
    > 37 |   await element.screenshot({
         |                 ^
      38 |     omitBackground: true,
      39 |     path: `e2e/screenshots/${directory}/${dataHook}-hover.png`
      40 |   });

I am pretty sure that element is in the DOM as my other function that searches with the same data-hook finds it:
const standardScreenshot = async (page, dataHook, directory) => {
  const element = await page.$(`[data-hook="${dataHook}`);
  await page.waitFor(50);
  await element.screenshot({
    omitBackground: true,
    path: `e2e/screenshots/${directory}/${dataHook}.png`
  });
};

Update. await page.$([data-hook="${dataHook}).hover() throws that it is not a function.

Thanks this is a life saver!

const element = await page.$(`[data-hook="${dataHook}`);
await element.hover()

also works for me. You don't need to select it twice.

authors: DanEdens LucasArruda mykas

repo: puppeteer/puppeteer


text:
fullPage changes viewport size or changes element positions

Puppeteer is apparently resizing the viewport size or changing element positions when taking a fullPage screenshot. Visually testing pages using the fullPage screenshot feature is currently problematic because they do not match pixel wise to the coordinates in the expected viewport size set prior to screenshot.
Steps to reproduce
Tell us about your environment:

Puppeteer version: 2.0.0
Platform / OS version: Windows 10
Node.js version: 13.3.0
NPM version: 6.13.4
Browser: Packaged Chromium

What steps will reproduce the problem?

Visit web page and set viewport.
Take coordinates of an element.
Take screenshot using fullPage mode. (In headless or GUI)
Stroke rectangle around element in the fullPage Screenshot image.
Repeat with non fullPage mode and compare if neccessary.

EXAMPLE 1:
Webpage Repository: https://github.com/redecheck/example-webpages/tree/master/3-Minute-Journal
Full-xpath-1: /HTML/BODY/DIV[3]/DIV/DIV[2]/DIV/DIV/DIV[2]/DIV[8]
Full-xpath-2: /HTML/BODY/DIV[3]/DIV/DIV[2]/DIV/DIV/DIV[2]
Here is a screenshot using fullPage at viewport 992...

Here is a normal screenshot  at viewport 992...

EXAMPLE 2:
Webpage Repository: https://github.com/redecheck/example-webpages/tree/master/Pepfeed
Full-xpath-1: /HTML/BODY/DIV[2]/DIV[2]/DIV/DIV[2]/DIV/DIV[2]/DIV/DIV[2]
Full-xpath-2: /HTML/BODY/DIV[2]/DIV[2]/DIV/DIV[2]/DIV/DIV[2]/DIV/DIV/DIV[2]/DIV[3]
Here is a screenshot using fullPage at viewport 950...

Here is a normal screenshot  at viewport 950...

What is the expected result?
I expect that coordinates and viewport size remains the same during screenshots using fullPage.
What happens instead?
I assume viewport size changes.

I also have this issue, and it's very annoying as it messes up some screenshots.
For example, I need to take a screenshot of the drop-down menu that shows up upon hover. But when the puppeteer resizes viewport menu colapses.
@ibrahimalthomali  do you have any suggestions to avoid viewport resizing?

I experienced similar issues. A workaround that was sufficient for me was to change my code to take screenshots of the body element instead, which doesn't appear to fire the resize event (at least in my case).
const bodyElement = await page.$("body");   await bodyElement.screenshot({path:out/example.png"});

authors: Padge91 ibrahimalthomali vasyl-design


text:
[Bug]: Puppeteer gives error that Error: Failed to launch the browser process! when the user profile path is given

Bug description
Steps to reproduce the problem:

Copy paste the code but replace the user profile path.

I am getting the browser launch failure because I am loading my user profile from a file path. Can someone tell me how to fix this and why am i getting this error?
Here's the code:
This code gives me the error:
const puppeteer = require('puppeteer');

async function start() {
    const browser = await puppeteer.launch({
        headless: false,
        executablePath: "C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe",
        args: ['--start-maximized', '--user-data-dir=C:\\Users\\anirudha tiwari\\AppData\\Local\\Google\\Chrome\\User Data\\'
        ]
        //ignoreDefaultArgs: ['--disable-extensions']
    });

    const page = await browser.newPage();
    await page.setViewport({
        width: 0,
        height: 0
    });

    await page.goto('https://www.webnovel.com/', { "waitUntil": "networkidle0" });

};
}

start();

But if u comment the user profile path the code runs fine.
By the way, when I tried the second code snippet the browser opened with the specified profile but it didn't go to the page specified which would be 'www.webnovel.com'. Is there a problem with files in the specified path?. If so how do I fix my google profile files? Thanks in advance.
Puppeteer version
13.0.1
Node.js version
16.13.0
npm version
8.1
What operating system are you seeing the problem on?
Windows
Relevant log output
here is the error:

node_modules\puppeteer\lib\cjs\puppeteer\node\BrowserRunner.js:229
            reject(new Error([
                   ^

Error: Failed to launch the browser process!

I was having the same issue today. Didn't really got to know why, but I copied all of User Data directory to another folder and then pointed the --user-data-dir to that new folder and it's working now

Same issue here
needed help

Error: Failed to launch the browser process!
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
at onClose (C:\Users\it\Desktop\nodejs PROJECTs\src\fake usr in yt v2\production_v3\node_modules\puppeteer\lib\cjs\puppeteer\node\BrowserRunner.js:290:20)
at ChildProcess.<anonymous> (C:\Users\it\Desktop\nodejs PROJECTs\src\fake usr in yt v2\production_v3\node_modules\puppeteer\lib\cjs\puppeteer\node\BrowserRunner.js:281:24)
at ChildProcess.emit (node:events:525:35)
at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)

I have the same problem, if i remove userDataDir it works but in Person 1 profile and not with specific profile.
Failed to launch the browser process!
      {        executablePath: '/Program Files/Google/Chrome/Application/chrome.exe',       userDataDir: '/Users/XXXXX/AppData/Local/Google/Chrome/User Data',       args: [ '--profile-directory=Profile 6', '--ignore-certificate-errors' ]       }

Please report the issue upstream to crbug.com if the browser does not start with custom arguments. Not much we can do in Puppeteer.

I have the same issue I can't run the puppeteer within my existing chrome profile ..
(async () => {
  const browser = await puppeteer.launch({
    executablePath: "C:/Program Files/Google/Chrome/Application/chrome.exe",
    headless: false,
    args: [ '--user-data-dir=C:/Users/acer/AppData/Local/Google/Chrome/User Data/','--profile-directory=Default', '--ignore-certificate-errors',"--disabled-setupid-sandbox"],
  });
  const page = (await browser.pages())[0];;

  await page.goto("https://developer.chrome.com/");

  await browser.close();
})();```

I was having the same issue today. Haven't really come to understand why, but I copied all of User Data directory to another folder in a different drive and then pointed the --user-data-dir to that new folder and it's working now

If someone still have the same issue, just do what @zeeskhan1990 said.
At least for me it worked, thanks 👍

Same here. However, the following workaround did not help too.

I was having the same issue today. Haven't really come to understand why, but I copied all of User Data directory to another folder in a different drive and then pointed the --user-data-dir to that new folder and it's working now

If someone still have the same issue, just do what @zeeskhan1990 said.
At least for me it worked, thanks 👍

Also tried downgrading puppeter, also did not help.

System processes through gitlab run into the issue that they have no access to other paths like the install paths of browsers. this affects all browsers.


text:
Issue where beaker gets stuck when an invalid Vagrantfile had been generated

I'm not sure what the correct solution is here. In one case if beaker generates an invalid Vagrantfile then beaker will remain stuck without a way to get unstuck unless you manually go find the Vagrantfile and delete it.
In another case if the destroy fails to destroy an existing VM and the original Vagrantfile is deleted the user might be in a very bad state where there's a VM but Vagrant will not work with that existing VM unless the Vagrantfile is restored. I'm not sure what the chances of this actually happening.
Another solution might be to try to destroy then raise a custom exception to let the user know about these 2 states and extend beaker's cleanup rake task to clear the Vagrantfile. This moves the decision from here to the user's judgment.
Let me know what the best choice is and I can make whatever changes need to happen. I found myself in this situation where beaker kept failing even though I knew it should of been fine. I had to inspect the source code to realize I needed to clear out the old Vagrantfile.
Thanks!!

Can one of the admins verify this patch?

Hi @dillongilmore, thanks for submitting this question/situation.
Is the Vagrantfile cleared during the destroy command you're highlighting in your changes, or is the file being cleared out just by our make_vfile method that writes a new one?
I would say that if we can control when the clearing happens, then we should log the failure to destroy, keep the Vagrantfile around around, and quit the run, letting the user know the circumstances around the failure, so they can manually take care of whatever issue is causing the failure.
I'm open to entertaining other failure modes, but with the information I have now, that seems like the best option, if it's do-able. Let me know if you have any questions or comments for me about this.

@dillongilmore 👍 sounds good to me.

Hi @dillongilmore,
Thank you for contributing and submitting this PR!
Would you mind editing this PR to match our contributing guideline? It requires you to create a JIRA ticket about the same and editing your git commit to match the required commit message format with the JIRA ticket number on it (more information can be found on the same contributing page). You can edit your current commit message by git commit --amend and force push it.
Also as this is a functionality change, we would need some spec tests for this.
Thank you!

Thanks for the info!!
I went ahead and made those changes and tested it. I'm not sure exactly how to add a unit test. If someone can point me in the right direction I can add that. In this case we need to somehow force Beaker to output an invalid Vagrantfile so that the vagrant destroy will fail and the error message will output.
To test this manually you can use the vagrant-libvirt hypervisor then edit the generated Vagrantfile's mac address to something invalid and that should do the trick.
LMK what else I need to do!! Thanks!

@dillongilmore thanks for creating a ticket and making these changes.
We use Rspec for unit/spec testing. For this to merge we need updated spec tests to pass through our CI (we will kick it on once you submit updated tests).
An example of Spec test can be found here. You might want to make a similar block for this case and can use expect-receive and return statements to create a Runtime error and test if and expected error message is raised. Spec tests are usually used to make sure that the method API is working as expected, its calling the functions like it should and its raising errors appropriately.
More information about writing and running testing can be found in this section of our contributing docs.

@dillongilmore last comment is still current

@dillongilmore last comment is still current. If no more activity happens in a week, we'll close this PR due to inactivity.

Hey there. Sorry for that. I've been busy with work/vacations. I still plan to make the requested spec tests as requested this weekend. Thanks!!

Hi there, new to rspec. I have this, which is passing
    it "notifies user of failed provision" do
      allow( vagrant ).to receive( :vagrant_cmd ).with( "destroy --force" ).and_raise( RuntimeError )
      vagrant.provision
    end

Is this the right way to do this? I tried to put an expect on the logger, but I didn't see any examples for that so I avoided doing it.

@dillongilmore, yes you are on the right path.
Here you are stubbing (fake calling) the rescue block of you code but are not actually testing if the message is passed to @logger object.
Before your allow statement you need to expect @logger object to to receive debug method call with the argument of the error message. But instead of testing the whole error message you can use a regex to test a part of it. An example of the same can be found here. Your call to @logger object will be different than the example and you'll be expecting :debug instead of :error and instead of the last .never part you will have with (more rspec docs about with). Somewhere along the lines of:
expect(@logger).to receive(:debug).with(/myregex/)

Got it!! Thank you for your patience and guidance on this. Small chance, but hopefully this helps other people.
Note I had to call vagrant.provision twice in my spec tests. The first time to generate the Vagrantfile and the 2nd time to get vagrant destroy to be called and raise the exception. I didn't see any other tests for that so I'm not sure if that function call was covered before or not.

Absolutely! This looks good to me, kicking off CI

@puppetlabs-jenkins test this please

@puppetlabs-jenkins retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/3985/

@dillongilmore nit for next time: there are parens around the ticket ref or MAINT keyword. If that's right, then we won't squash when we merge.
Thanks for your contribution! It should be out in the next cut of Beaker this Wednesday! Refer to our wiki for the status & release date of our next release at any time!

authors: dillongilmore kevpl puppetlabs-jenkins rishijavia

repo: puppetlabs/beaker


text:
release bolt version with latest facter

Please consider release a bolt package with updated facter.
The fix for Apple silicon is included in facter 4.5.2, that comes with puppet agent, but 4.5.0 that comes with bolt detects architecture wrong:
$ uname -m
arm64
$ /opt/puppetlabs/bolt/bin/facter --version
4.5.0
$ /opt/puppetlabs/bolt/bin/facter os.architecture
x86_64

$ /opt/puppetlabs/bin/facter --version
4.5.2
$ /opt/puppetlabs/bin/facter os.architecture
arm64

Thanks for reporting this. Generally I would like to update the runtime we ship in bolt packages as it could use a refresh. Not to mention figuring out what a puppet 8 based bolt package will be.

authors: donoghuc vchepkov

repo: puppetlabs/bolt


text:
(PUP-9649) Backport certname mismatch error handling to 6.0.x

Backport PUP-8213 to 6.0.x
This is the same PR as https://github.com/puppetlabs/puppet/pull/7490, but applied to 6.0.x and includes an additional commit to delete the unused rest client.

CLA signed by all contributors.

jenkins please test this on windows2016-64a with servertests

authors: joshcooper puppetcla

repo: puppetlabs/puppet


text:
(PUP-9936) Change deviceconfdir section to agent

Setting $deviceconfdir in the main section makes puppetserver want to create it, which it shouldn't.
Starting puppetserver with an affected puppet version fails because of this. Changing the section of $deviceconfdir to agent fixes the issue.

@gimmyxd the only change needed in .travis.yml was to add openjdk8 since Xenial defaulted to 11 and tests failed on it. We don't need trusty since 6.0.x does not test against ruby 1.9.

CLA signed by all contributors.

authors: GabrielNagy puppetcla


text:
(maint) Cleanup integration tests

Remove have_printed matcher. Use builtin rspecexit_with and output(..).to_stdout matchers
Use compound matchers expect(..).to exit_with(0).and output(..).to_stdout instead of nested expects.
When testing an application, call its Application#run method, instead of skipping the earlier phases of the application lifecycle.
Delete useless file metadata and content tests that used the "a file_serving model" shared behavior.
Convert man, config, and help unit tests to integration. Removing stubbing.

CLA signed by all contributors.

Fix https://tickets.puppetlabs.com/browse/PUP-4548

jenkins please test this with redhat7-64a,ubuntu1804-64a,windows2019-64a


text:
(PDB-3029) admin-clean-test: block until unlock

Use a cyclic barrier to block the next test iteration until we know that
the current iteration has released the clean lock.
A (Thread/sleep 1000) at the end of the clear-clean-status! wrapper
function will demonstrate the problem, and the original failure looked
like this:
FAIL in (admin-clean-status) (admin_clean_test.clj:43)
expected: (= http/status-ok (:status result))
actual: (not (= 200 409))
{:status 409,
:headers
{"Date" "Wed, 07 Sep 2016 19:48:43 GMT",
"Content-Type" "application/json; charset=utf-8",
"Connection" "close",
"Server" "Jetty(9.2.10.v20150310)"},
:body
"{\n  "kind" : "conflict",\n  "msg" : "Another cleanup is already in progress",\n  "details" : null\n}",
:request-time 5,
:trace-redirects ["http://localhost:41655/pdb/admin/v1/cmd"],
:orig-content-encoding nil}
(cherry picked from commit 12fbc1aa75759cf0c247403183e864bf84e90c11)

Test PASSed

authors: puppetlabs-jenkins rbrw

repo: puppetlabs/puppetdb


text:
Fixed "unless" test condition for ppa repository

After the repository is added, the ${::apt::sources_list_d}/${sources_list_d_filename} file is created as an empty file.The unless condition of Exec["add-apt-repository-${name}"] calls test -s, which returns 1 if the file is empty. Because the file is empty, the unless condition is never true and the repository is added on every execution. This commit replaces the -s test condition with -f, which is true if the file exists or false otherwise.

Thanks for the fix!
This breaks a number of tests as we check that we get the full command, including what used to be the -s switch. Please check the spec/ directory and update the tests accordingly. We can't merge it otherwise.

As requested, the last commit fixes the broken tests.

@bmjen @tphoney Could someone take a look at why the Beaker tests fail? Looking at them it's not related to this PR.
@nicobn Could you squash your commits into one so we get one single commit that fixes the bug and adjusts the tests?

@nicobn @daenney one of the errors was a transient issue. I will look further into the other issue.

authors: daenney nicobn tphoney

repo: puppetlabs/puppetlabs-apt


text:
Add a proper creation time (crtime) attribute

We misunderstood the ctime attribute to mean creation time when it means changed time. We should still keep ctime around because it's a filesystem attribute. The work in this issue is to add a separate crtime attribute for the creation time, which mirrors some FSes like Ext 3/4 and NTFS, and to clean-up the core plugins to ensure things that once set ctime to creation time now set crtime to creation time.
The work here would also include adding a crtime primary to Wash find so users can filter on it.

bazil/fuse has the Crtime attribute, so we should also set it there.

authors: MikaelSmith ekinanp

repo: puppetlabs/wash


text:
Missing Biome Tint impacts leaves color with mod - SnowyLeavesPlus

When utilizing the SnowyLeavesPlus mod, it's supposed to change the leaves color from green to white however it is done utilizing biome tint. Since this pack has the biome tint removed in order to maintain the color, it results in this mod not being able to work. May result in other visual issues with other similar mods.

Reinstated biome tint in the leaves.json file and now works with the SnowyLeavesMod. Jungle and Cherry leaves will not work with this mod when having those trees in a snowy biome.

repo: puppyraeluna/blu-rae


text:
Fix type inference by exposing classless API

Description of the change
Previously, compiler would fail to infer the type of Buffer.create 1 as Effect Buffer
because the Buffer API was exposed only via the multiparameter typeclass MonadBuffer.
Due to the functional dependency between the two parameters, the monadic type cannot be inferred
until the buffer type is known (either Buffer or STBuffer).:
import Node.Buffer as Buffer

-- Example 1
main :: Effect Unit
main = do
  x <- Buffer.create 1 -- compiler: is this `Int -> Effect Buffer` or `Int -> ST h (STBuffer h)?
  pure unit

The workaround was to add a type annotation, indicating the x is a Buffer:
import Node.Buffer as Buffer

-- Example 2
main :: Effect Unit
main = do
  x :: Buffer <- Buffer.create 1 -- compiler: Oh! It's `Int -> Effect Buffer`
  pure unit

This change does not break anyone's code if one was using a create (or another such typeclass member)
to get Int -> Effect Buffer. Rather, such users can now drop the :: Buffer annotation
(i.e. Example 1 above now compiles).
If one was using create to get forall m buf. MonadBuffer buf m => Int -> m buf,
then one will need to update their imports:
-import Node.Buffer (class MonadBuffer)
+import Node.Buffer.Class (class MonadBuffer)

Checklist:

[x] Added the change to the changelog's "Unreleased" section with a reference to this PR (e.g. "- Made a change (#0000)")
[ ] Linked any existing issues or proposals that this pull request should close
[ ] Updated or added relevant documentation
[ ] Added a test for the contribution (if applicable)

@thomashoneyman :ping_pong:

repo: purescript-node/purescript-node-buffer


text:
Update to v0.14.0-rc3

Backlinking to purescript/purescript#3492

CI fails with this error:
> eslint src && spago build '--censor-lib --strict'

/home/runner/work/purescript-web-file/purescript-web-file/src/Web/File/FileReader.js
Error:   1:11  error  'FileReader' is already defined as a built-in global variable  no-redeclare

✖ 1 problem (1 error, 0 warnings)

We also need to update the Bower file to point to master.

authors: JordanMartinez thomashoneyman

repo: purescript-web/purescript-web-file


text:
Remove createObservableStream()

I think, RxJava support should be 100% reactive, that means that such code
storIOSQLite
  .get()
  .listOfObjects(Tweet.class)
  .withQuery(new Query.Builder()
    .table("tweets")
    .build())
  .prepare()
  .createObservable()
  .subscribeOn(Schedulers.io())
  .observeOn(AndroidSchedulers.mainThred())
  .subscribe(tweets -> {
    // this should be reactive stream
    // each change should reload it
  });

createObservableStream() is not a good name, because Observable is stream by its nature.
If user needs to get result one time, he should use observable.take(1)
@nikitin-da PTAL and write your opinion please

I guess, #77 also was created for this problem. I think yes, it should be obivios, that if you use createObservable for operation, you just subscribe only to it. Not to all changes in table.

Wait wait wait :)
Please reread issue carefully, I want to remove createObservableStream() and leave only createObservable() which will be subscribed to changes in tables from query.
It will make API more convenient and really reactive

authors: artem-zinnatullin nikitin-da

repo: pushtorefresh/storio


text:
Does  StorIO support Unique Key or Compound key?

This will be really handy. Thanks.

Yes!
StorIO can work with any kind of primary keys via resolvers: you can use any combination of columns as keys :)

Closing, feel free to comment!

authors: Kistamushken artem-zinnatullin


text:
🛑 Elibs is down

In a99d757, Elibs (https://elibs.unmer.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Elibs is back up in 15cc3fc after 5 minutes.

repo: pusimgit/upptime


text:
🛑 SISTER is down

In 3ad5888, SISTER (https://sister.unmer.ac.id/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SISTER is back up in b841bd9 after 25 minutes.


text:
Direct and diffuse shading factors - spatial approach (for Photosynthetically Active Radiation)

Is your feature request related to a problem? Please describe.
This is the broadest proposal I'm ever going to do here, I think.
The model (or workflow, I don't know how to call it) is described in [1]. It compares the output of a Matlab script against PVsyst and SketchUp and calculates shading factors for direct and diffuse components, in the context of PAR incidence onto ground. Nevertheless part of the workflow seems equally applicable to shadows of other objects onto arrays.
A first step is a geometrical description of the PV arrays and projection of their shadows onto arbitrary planes, described in [3] of [1].
For the direct shading factor:
I already have arbitrary shadow castings onto a random plane: I'm currently at equation 20 of [1], finished section 4.3 of [3]. You can check out some dirty progress at this gist. Next steps include probably using the shapely package, doing intersections and unions of shadows.
For the diffuse shading factor:
A semi-spherical discrete integral is done. I haven't made any progress on it nor I have read enough to be sure about the approach.
Describe the solution you'd like
A functional set of functions in a new submodule, something along spatial.py (shamelessly stealing this idea from @adriesse 😉 ) to handle the array rectangle and rotation creation, projection of the corners, and translation from 3D coordinates to 2D plane system (required for easy area calculations). I usually find functional code more hackable and well-documented.
Then I would like to add at least the fixed tilt agrivoltaic system modelling in an example. I can add the other examples in different PRs.
I'm still unsure regarding how to approach the diffuse integral.
Describe alternatives you've considered

Create a parallel OOP modelling for 3D operations
The base object would be:

Surface -> rectangle to describe arrays, the field or flat obstacles. Internally a shapely polygon. Initialized from azimuth, tilt, length, width and a point (a corner or the centroid). Would have methods to make the boundary checks of the shadows onto the surface (intersection), shadow area calculation (or output as a Polygon)
The pro of this approach is no user mess of mis-reused variables, and ease of use I think. With solar azimuth and zenith and shadowing objects, I think a method can handle the projection:
shadow_polygon (or shadow_area) = shaded_surface.shadow_by(solar_azimuth, solar_zenith, array1, obstacle1, array2, obstacle2, ...)
I have doubts regarding trackers, since they change their corners coordinates.
This would possibly allow expanding the obstacles with more complex geometries, or defining them just as Polygons

Add the above to the current Array class (or by inheritance)

Additional context
This is part of my GSoC PAR analysis proposals.

[1] S. Zainali et al., ‘Direct and diffuse shading factors modelling for the most representative agrivoltaic system layouts’, Applied Energy, vol. 339, p. 120981, Jun. 2023, doi: 10.1016/j.apenergy.2023.120981.
[3] Y. Cascone, V. Corrado, and V. Serra, ‘Calculation procedure of the shading factor under complex boundary conditions’, Solar Energy, vol. 85, no. 10, pp. 2524–2539, Oct. 2011, doi: 10.1016/j.solener.2011.07.011.

I request input in:

where to put new code
whether or not to add more examples in a single PR
approach: functional or OOP

Closing as not planned, see discussion on #2106

repo: pvlib/pvlib-python


text:
PVWatts_loss was applied on AC calculation

Hi,
In the description of pvwatts_losses function, the losses are applied on DC side:
'Calculates DC power losses according the PVwatts model using pvwatts_losses() and self.losses_parameters.`'
However I found that in pvlib.modelchain.ModelChain.pvwatts_losses, PVwatts loss was applied to AC.
'def pvwatts_losses(self):
self.losses = (100 - self.system.pvwatts_losses()) / 100.
self.ac *= self.losses
return self'
When system have high DC/AC ratio, AC power output clips at a lower level as a result of these losses applied on the AC side.

thanks @yxh289. pull request welcome.

Concur with the bug report.  May have been due to coding following the older PVWatts description, rather than the v5 document.  Or a simple typo.

The post-inverter losses such as the AC wiring losses and AC Availability should in theory only apply to the AC power and not be subjected to inverter clipping.

@pasquierjb conceptually that might be true, but in this case we're just sticking with the original spec: per Section 11 of the PVWatts Version 5 Manual, "Losses in the system that are not explicitly modeled are provided by the user as a percentage of DC energy."
See also #1350

authors: cwhanse kanderso-nrel pasquierjb wholmgren yxh289


text:
add timezone for package overview

fixes #156 update "package overview" to use UTC or localized time only (v0.3.0)

I'm done for now.

adds timezone to coordinates dictionary
coordinates = [(30, -110, 'Tucson', 700, 'US/Mountain'),
(35, -105, 'Albuquerque', 1500, 'US/Mountain'),
(40, -120, 'San Francisco', 10, 'US/Pacific'),
(50, 10, 'Berlin', 34, 'Europe/Berlin')]

also moves times creation inside the loop, because tz_localize(pytz.timezone('US/Mountain')) always raises NonExistentTimeError which is pandas issue  8917

NOTE: I tried to use tz_localize with 'Etc/GMT+7' which is equivalent to UTC-0700 (ie: US/Mountain), etc, but that raises TypeError: Already tz-aware, use tz_convert to convert. after first loop so times actually has to go inside the loop anyway, and it's just cleaner to make a new datetime index series each loop and localize it to the actual timezones which are clearer than the GMT timezones.

add new test module called test_docs.py - this can probably be removed if doctest sphinx extension is used? but I've never used it so not sure?

add test_package_overview to test_docs for this issue, checks if energies are all close to previously calculated, except, that now Tuscon and SF don't agree :frowning:

also for expedience I just copied the doc source over to the test, but I put a todo to use docutils to grab this code, unfortunately, tho, docutils doesn't like the ipython directive so I couldn't figure this out right away, also if using doctest extension, maybe this goes away?

Thanks!
This seems like a good place to demonstrate the use of the Etc/GMT time zones. People will see US/Mountain or similar in many other places, so I think we might as well expose them to another option here. Thoughts? I'm ok with either approach.
I'd definitely like to get some kind documentation testing working, but it's pretty low on my priority list. I think that doctests is probably the way to go, but I also haven't used it. In the spirit of small changes and getting something done sooner than later, I suggest removing the test_docs.py from this PR. In any case, it's not obvious to me why it's failing on the py27-min build.

I'm okay with the Etc/GMT timezones, that was definitely new to me, so I think you're right about it being a good chance to expose users to them. I'll make the switch and push it up to the PR.
Not sure why test_docs fails py-min, it passed on my machine. The traceback says AssertionError: None.
======================================================================
FAIL: test package overview update to timezone
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/miniconda/envs/test_env/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/travis/build/pvlib/pvlib-python/pvlib/test/test_docs.py", line 78, in test_package_overview
    ok_(np.allclose(energies.values, pd.Series(ENERGIES).values))
AssertionError: None

I'll remove the test anyway tho since it doesn't really add much, and it's a bit fragile (so not DRY) since it copies the example from the docs source. IE: if the doc source changes, then this test is worthless. I'll make the change and push it up to the PR.
I might not have time to make the changes today, but definitely by Friday.
I've never used doctest and not sure how to. The ipython directive you're using was totally new to me too. I agree postpone doctest, but I'll add an issue that addresses it so we don't forget.

@mikofski do you think you can switch to Etc/GMT remove the test_docs.py file in the next week? I want to finish 0.3.3 before PVSC.

When building docs, I get this warning, I think it's unrelated:
>>>-------------------------------------------------------------------------
Warning in pvlib-python\docs\sphinx\source\package_overview.rst at block ending on line 120
Specify :okwarning: as an option in the ipython:: block to suppress this message
----------------------------------------------------------------------------
pvlib-python\pvlib\clearsky.py:247: VisibleDeprecationWarning: using a non-integer number instead of an integer will result in an error in the future
  g = linke_turbidity_table[latitude_index][longitude_index]
<<<-------------------------------------------------------------------------

Otherwise I the documents look good to me and I think this is ready to merge. :smile:

I agree that it's good to go, except for changing San Francisco from +7 to +8. Oh, and please add a note and your name or username to the whats new.

Thanks @mikofski!

authors: mikofski wholmgren


text:
Removed the party feature?

any specific reason why the showing party feature got removed?
The one which shows which ppl are in the same squad. Thats like mainly why I used that tracker above others....

It didn't get removed, still working on my side.

I have yet to fix this issue because it's something related to decoding the presences so it's gonna be tough. Don't expect this to work for the time being.

Do you know if it's even possible to fix by now?

Do you know if it's even possible to fix by now?

I am not sure yet, but I will close this issue if it can't be fixed.

Right now this issue will be stale for a while. Because RiotGames changed how their API works, we used to grab the PartyID from the local endpoint /chat/v4/presences but now that API only shows friends, which in part means that we can't fetch the PartyID for the players in our match. So we can't know who is premade.
TLDR; Can't look at parties because we can't get info from players

Update in the issue, I have seen some possibilities to show some kind of parties (not 100% accurate) but it will be better than not having any party indicators. It will take a while to implement.
Also for the technical details, the tracker.gg app uses last 20 matches to check if players have queued together and uses that to predict parties. Another way is thru an obscure endpoint feature that may or may not work.

I have a small update, the PartyID so the functionalty can be as good as before the API change can be retrieved via the messaging protocol of Riot (based off XMPP) so I am working in a side project to be able to bring that to NOWT. I don't have a estimated timeline so don't get too hyped but it'll be soon™.

update?

update?

There is no update. For personal and general reasons, I haven't been involved a lot on finishing this. But as I stated previously don't get your hopes up it will be "soon™" refering that it could be from now till the end on time.
References: Soon™

it is not working anymore, not loading any info, even not showing that valorant is running
Appreciate your efforts' dev,


text:
Fix: Remove the notification after the user clicks the download button when using database notifications

Fixed issue #174

Thanks

authors: muzhawir pxlrbt

repo: pxlrbt/filament-excel


text:
Add docstrings and seperate things. Closes #210

Bit of a big change to be honest. This is something I've been working on for a while really. Adds doc strings to pretty much everything, adds slots to all the classes, separates Connection into BaseConnection, BaseReadSync, and BaseWriteSync (don't worry Connection is still there, just subclasses all of these.) so that there can be separate BaseReadAsync and BaseWriteAsync, so that TCPAsyncSocketConnection and UDPAsyncSocketConnection can exist and not have tons of duplicated code.
Also adds unused read_varlong and write_varlong functions, this could be removed but why not.
This might make python 3.7 not work right because I got rid of some odd stuff with the BytesConvertable type, but I haven't tested.

Thanks! However we've made the decision to slowly move away from our custom Connection implementation in favor of using PyMine-Net as a library which will handle these low-level things for us, since this repo isn't really a place to maintain these. For this reason, any big non-critical changes to how it works are probably not worth making considering the whole file will be removed completely at some point.

What do you mean in the "made the decision" link? It doesn't go anywhere.

What do you mean in the "made the decision" link? It doesn't go anywhere.

It's a link to our discord server, though you have to join it to be able to access the link. You can join it by clicking on the discord badge in our README, or by finding it in a pinned issue (Community Chat)

I'm not opposed to having improvements to these connections in the meanwhile. A shift to using pymine-net is a change that'll probably take a while and it hasn't even started yet.

Rebased in #273

repo: py-mine/mcstatus


text:
numpy has no attribute 'long'

I'm installing via pip and I'm getting this error despite having numpy version 1.24.

This is a numpy issue. long has been removed in 1.24. You can use 1.23 version of numpy (or any other version >=1.20) to avoid this error.

authors: amit-sharma zzzrbx

repo: py-why/dowhy