ERROR invoke trace_block api on block 21030627

Describe the bug
invoke trace_block api on block 21030627 report error :
error code -32003: insufficient funds for gas * price + value: have<PHONE_NUMBER>692614043 want<PHONE_NUMBER>692614043
Steps to reproduce
cast rpc trace_block 0x140e6e3
Node logs
No response
Platform(s)
Linux (x86)
What version/commit are you on?
`
reth Version: 1.1.0
Commit SHA: 1ba631ba9581973e7c6cadeea92cfe1802aceb4a
Build Timestamp: 2024-10-10T18:21:07.285015202Z
Build Features: asm_keccak,jemalloc
Build Profile: maxperf
`
What database version are you on?
Current database version: 2 Local database version: 2
Which chain / network are you on?
eth mainnet
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

it fixed after full synced .


Content measure issue

Why content is not remeasured after loading indicator is replaced with the content?
I think you need to update the height after changing child props in component.
If response comes after 1 second it works, if it is around 300ms it doesn't work, so I think the problem no in my component. Can you check the code example:
https://snack.expo.io/SJ84WiNtr

@AleksandrLeontev save my day!

What did you do? @AleksandrLeontev


HDDS-8131. Add Configuration for OM Ratis Log Purge Tuning Parameters.

What changes were proposed in this pull request?
Currently Ozone Manager enables raft.server.log.purge.upto.snapshot.index by default.
However, for OM cluster with large metadata store, there might be a case where OM leader purge its Ratis logs before a slow follower replicated it to its log. This means that the follower needs to download the whole metadata store from the OM leader. This can be problematic if the metadata store in leader is too large.
We should add two configurations in OM to enable/disable Ratis purge parameters:

raft.server.log.purge.upto.snapshot.index

Disabling this would guarantee that the OM leader will not purge its Ratis log unless all the logs have been replicated to all the followers (through commitIndex).
This would effectively means that there shouldn't be a case where the slow follower needs to download the full metadata from the leader. So no snapshot down from follower. For small OM metadata, it can be faster for follower to download the leader's metadata snapshot than normally replicating and applying the outstanding logs.
For a very slow follower / downed follower, the OM leader cannot purge the log until the follower catch up to it. This might increase the disk space usage for OM leader.
Default would be true to preserve the current OM snapshot behavior

raft.server.log.purge.preservation.log.num

RATIS-1626 introduces logic to preserve the latest n won't-be-purged logs
Setting n > 0 while still enabling raft.server.log.purge.upto.snapshot.index should balance a between the cost of preserving & transferring logs and the cost of transferring snapshot.
Default would be 0 to preserve the current OM snapshot behavior

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8131
How was this patch tested?
Should have already be covered in Ratis test.

Hi @Xushaohong @szetszwo could you take a look?

Hi @prashantpogde @hemantk-12 @GeorgeJahad I see that there is already an effort to introduce incremental checkpoint in the OM snapshot process. Our cluster is currently encountering issue in which a slow OM follower has to download a large OM metadata due to the leaders' log being purged. This merge request seeks to circumvent this issue by disabling raft.server.log.purge.upto.snapshot.index so that leader will only purge the log once the followers have replicated the log.  Could you take a look?
However this has a risk in which the OM leader disk space could be filled quickly if the follower is down / very slow. Therefore I think the long-term solution would be to integrate incremental checkpoint. May I know what is the progress on the feature? We are interested in integrating it in our cluster.

@szetszwo Thank you for the review and merge.


*: Fix retention parameter

Previously we were passing nanoseconds instead of the expected
milliseconds.
Fixes #160

Oops!
Nice :rocket:


Google gms service causes app not to run

Bug Description
App runs as long as I don't add
apply plugin: 'com.google.gms.google-services'
in my android/app/build.grade
Platform: Flutter
Things I have tried:

tried versions of gms - 3.2.1 and 3.2.2.
tried downgrading Flutter to its previous stable version.

My pubspec.yaml file
cupertino_icons: ^0.1.3
 intl_phone_number_input: ^0.3.0
 **firebase_core: ^0.4.4
 firebase_auth: ^0.15.4
 firebase_crashlytics: ^0.1.3
 firebase_performance: ^0.3.1+5
 firebase_messaging: ^6.0.9
 firebase_analytics: ^5.0.11**
 sqflite: ^1.2.1
 google_fonts: ^0.3.9
 **firebase_database: ^3.1.1**
 intl: ^0.16.1
 rxdart: ^0.23.1
 font_awesome_flutter: ^8.7.0
 streamqflite: ^1.0.0
 **cloud_firestore: ^0.13.3**
 fancy_on_boarding: ^1.4.0
 **cloud_functions: ^0.4.2**
 get_it: ^4.0.0
 grouped_buttons: ^1.0.4
 pin_code_fields: ^2.3.0+3
 hive_flutter: ^0.3.0+2
 hive: ^1.4.1+1
 cached_network_image: ^2.0.0

Expected Behaviour
The app needs to run on Android.
Additional details:

The present version of gms is 3.2.1.
App runs on IOS but gives this problem when run on android.

Flutter doctor:
[✓] Flutter (Channel master, v1.15.4-pre.241, on Mac OS X 10.15.3 19D76, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
[✓] Android Studio (version 3.5)
[✓] VS Code (version 1.42.1)

Hi @ram-koushik-reddy
can you please provide your flutter run --verbose
Thank you


How to understand the broker node to get the segments from the MiddleManager node？

Guys，
I am a software engineer at a Chinese bank. I am sorry for my poor English.😄
Our team going to build a druid production cluster recently.
Broker could get data from MiddleManager.
MiddleManager could generate segments and writes to deep storage.
What is the state of segment ,that is queried through the MiddleManager node?
How to choose the SSD size of the servers which run the MiddleManager process?

For the latter question, see the clustering docs.


cgroup path inconsistent between containerd 1.3 and 1.2.7

Description of problem
This may not be an issue with Kata
When validating SandboxCgroup Only with Kata, containerd 1.2.7 was utilized, and the cgroup was created in the path:
parent-cgroup-path=/kubepods.slice/kubepods-pod8949946d_3d17_415c_89d4_a8150388e128.slice/d22c91ffc5d7fa128db2a284baa50623935be294edda4d31a83b02838ef52cd3

In 1.3, this is:
parent-cgroup-path="/vc/kubepods-podc9c28094_37b3_49e8_a9a7_939773aea4d2.slice:cri-containerd:56ff8b750887f33a7fd0dfe8110267bf957eb6f2d38ee43fd5802d34bd83a497"

This is observed when looking @ https://github.com/kata-containers/runtime/blob/master/virtcontainers/sandbox.go#L2180-L2208
With the following applied:
--- a/virtcontainers/sandbox.go
+++ b/virtcontainers/sandbox.go
@@ -2192,6 +2192,11 @@ func (s *Sandbox) setupSandboxCgroup() error {
        }
        validContainerCgroup := utils.ValidCgroupPath(spec.Linux.CgroupsPath)

+       s.Logger().WithFields(logrus.Fields{
+               "parent-cgroup-path": validContainerCgroup,
+               "from-spec":          spec.Linux.CgroupsPath,
+       }).Warning("EGERNST: setupSandboxCgroup")
+

The spec.LinuxCgroupsPath looks correct, while the "ValudCgroupPath" provides an unexpected result (@ /vc/)
It looks like in 1.2.7 an absolute path was provided, whereas in 1.3.0 its a relative path (among other changes):
1.2.7:
/kubepods.slice/kubepods-podfoo.slice/bar

1.3.0:
kubepods-podfoo.slice:cri-containerd:bar

We need to either determine the path another way or work to get this fixed on containerd side.
Expected result
we land appropriately into kubepod path...
Actual result
we don't

/cc @randomliu

/cc @random-liu

/cc @devimc

Turns out that in 1.2.7, while Kubernetes was operating with systemd based cgroups, we had configured containerd to utilize cgroupfs.  As a result, a full path was provided.
After chatting with @random-liu, I now understand that its common practice to pass only the last component of the cgroup path to systemd.  See https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/dockershim/docker_service.go#L472
pkg/kubelet/dockershim/docker_service.go:472

runc/libcontainer handling:
https://github.com/opencontainers/runc/tree/master/libcontainer/cgroups/systemd

@devimc as part of your v2 work, can you PTAL?
/assign @devimc


Application with install4j fails to install in AIX

Question
I'm getting following error when I install the application using install4j, I'm not certain the root cause, could you please help?
Error log
$ ./app-8_0_0-aix-ppc64.sh
Unpacking JRE ...
Starting Installer ...
An error occurred:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
Error log: /tmp/install4jError9845213310594816837.log
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at com.install4j.runtime.installer.frontend.GUIHelper.invokeOnEDT(GUIHelper.java:716)
at com.install4j.runtime.installer.frontend.headless.AbstractHeadlessScreenExecutor.init(AbstractHeadlessScreenExecutor.java:74)
at com.install4j.runtime.installer.frontend.headless.ConsoleScreenExecutor.(ConsoleScreenExecutor.java:24)
at com.install4j.runtime.installer.frontend.headless.InstallerConsoleScreenExecutor.(InstallerConsoleScreenExecutor.java:6)
at com.install4j.runtime.installer.Installer.getScreenExecutor(Installer.java:91)
at com.install4j.runtime.installer.Installer.runInProcess(Installer.java:60)
at com.install4j.runtime.installer.Installer.main(Installer.java:46)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84)
at com.install4j.runtime.launcher.UnixLauncher.start(UnixLauncher.java:66)
at install4j.Installer371033952.main(Unknown Source)
Caused by: java.lang.reflect.InvocationTargetException
at java.desktop/java.awt.EventQueue.invokeAndWait(Unknown Source)
at java.desktop/java.awt.EventQueue.invokeAndWait(Unknown Source)
at com.install4j.runtime.installer.frontend.GUIHelper.invokeOnEDT(GUIHelper.java:712)
... 13 more
Caused by: java.lang.UnsatisfiedLinkError: /home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/jre/lib/libfontmanager.so: /home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/jre/lib/libfontmanager.so, LIBPATH=/home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/jre/lib/server:/home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/jre/lib:/home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/jre/lib/jli:/home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/jre/../lib:/home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/user:, LD_LIBRARY_PATH=/home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/user: :   0509-022 Cannot load module /home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/jre/lib/libfontmanager.so.
0509-150   Dependent module libfreetype.a(libfreetype.so.6) could not be loaded.
0509-022 Cannot load module libfreetype.a(libfreetype.so.6).
0509-026 System error: A file or directory in the path name does not exist.
0509-022 Cannot load module /home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/jre/lib/libfontmanager.so.
0509-150   Dependent module /h
at java.base/java.lang.ClassLoader$NativeLibrary.load0(Native Method)
at java.base/java.lang.ClassLoader$NativeLibrary.load(Unknown Source)
at java.base/java.lang.ClassLoader$NativeLibrary.loadLibrary(Unknown Source)
at java.base/java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.base/java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.base/java.lang.Runtime.loadLibrary0(Unknown Source)
at java.base/java.lang.System.loadLibrary(Unknown Source)
at java.desktop/sun.font.FontManagerNativeLibrary$1.run(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.desktop/sun.font.FontManagerNativeLibrary.(Unknown Source)
at java.desktop/sun.font.SunFontManager$1.run(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.desktop/sun.font.SunFontManager.(Unknown Source)
at java.desktop/sun.font.FontDesignMetrics.getMetrics(Unknown Source)
at java.desktop/sun.swing.SwingUtilities2.getFontMetrics(Unknown Source)
at java.desktop/javax.swing.JComponent.getFontMetrics(Unknown Source)
at java.desktop/javax.swing.text.WrappedPlainView.updateMetrics(Unknown Source)
at java.desktop/javax.swing.text.WrappedPlainView.updateChildren(Unknown Source)
at java.desktop/javax.swing.text.WrappedPlainView.insertUpdate(Unknown Source)
at java.desktop/javax.swing.plaf.basic.BasicTextUI$RootView.insertUpdate(Unknown Source)
at java.desktop/javax.swing.plaf.basic.BasicTextUI$UpdateHandler.insertUpdate(Unknown Source)
at java.desktop/javax.swing.text.AbstractDocument.fireInsertUpdate(Unknown Source)
at java.desktop/javax.swing.text.AbstractDocument.handleInsertString(Unknown Source)
at java.desktop/javax.swing.text.AbstractDocument.insertString(Unknown Source)
at java.desktop/javax.swing.text.PlainDocument.insertString(Unknown Source)
at java.desktop/javax.swing.text.DefaultEditorKit.read(Unknown Source)
at java.desktop/javax.swing.JEditorPane.setText(Unknown Source)
at java.desktop/javax.swing.JEditorPane.(Unknown Source)
at com.install4j.runtime.installer.frontend.headless.AbstractHeadlessScreenExecutor.createEditorPane(AbstractHeadlessScreenExecutor.java:354)
at com.install4j.runtime.installer.frontend.headless.AbstractHeadlessScreenExecutor.initFontManager(AbstractHeadlessScreenExecutor.java:314)
at com.install4j.runtime.installer.frontend.headless.AbstractHeadlessScreenExecutor.access$400(AbstractHeadlessScreenExecutor.java:32)
at com.install4j.runtime.installer.frontend.headless.AbstractHeadlessScreenExecutor$2.run(AbstractHeadlessScreenExecutor.java:78)
at java.desktop/java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)
Context
Java version: jdk11_0_9

Your operating system and platform: AIX 7.2 TL4

The error says Freetype is missing. That's something that needs to be supplied by the user because it's only bundled on few platfroms. I'm not familiar with Install4J, so I don't know how to fix it.

Thanks. I have used IBM's JDK 8 and did not get this error. I upgraded to Java 11 recently end up with this issue. When I see the difference AdoptOpenJDK 11.0.9 AIX version's /jre/lib/ loaded with many library files like /jre/lib/libfontmanager.so and particularly this libfontmanager.so has few other system level dependencies as we can see in the error log:
Cannot load module /home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/jre/lib/libfontmanager.so.
0509-150 Dependent module libfreetype.a(libfreetype.so.6) could not be loaded.
0509-022 Cannot load module libfreetype.a(libfreetype.so.6).
0509-026 System error: A file or directory in the path name does not exist.
0509-022 Cannot load module /home/aowuw/app-8_0_0-aix-ppc64.sh.6750682.dir/jre/lib/libfontmanager.so.
0509-150 Dependent module /h
I don't think is related with install4j, do you think we have to install these dependencies to AIX? and any idea why IBM's java 8 does not have these libraries like libfontmanager.so inside /jre/lib? Thanks

You can read more about the font situation on https://blog.adoptopenjdk.net/2021/01/prerequisites-for-font-support-in-adoptopenjdk/. If your AIX does not have those libraries, please let me know what packages have to be installed with the system's package manager and I'll update the article.

and any idea why IBM's java 8 does not have these libraries like libfontmanager.so inside /jre/lib?

Oracle JDK 8 in the early days looked significantly different in comparison to what we have now. And IBM JDK is a completely different beast with another VM.

As suggested in https://blog.adoptopenjdk.net/2021/01/prerequisites-for-font-support-in-adoptopenjdk/, installing Freetype and Fontconfig solved the problem. Thanks for the help :)

@kthaya What steps did you perform to install both? Would be a nice addition to the article.

I'm sorry, I made a mistake. I actually did not install Fontconfig. I have installed only Freetype.
Freetype have some dependencies, I have installed following in order in AIX.

rpm -Uvh bzip2-1.0.6-1.aix5.1.ppc.rpm
rpm -Uvh zlib-1.2.11-1.aix5.1.ppc.rpm
rpm -Uvh libpng-1.6.34-1.aix5.1.ppc.rpm
rpm -Uvh freetype2-2.8.1-1.aix5.1.ppc.rpm


Unexplained asterisks on products

Under the section "View a list of self-service purchase products and their status" where the products are listed, the Project and Visio products have asterisks beside them. These aren't explained either in that section or at the bottom of the page. They should either be removed to avoid confusion, or a footnote should be added to explain what the asterisks are intended to denote.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5082f7ed-ad40-04c1-5c6c-59e67b253257
Version Independent ID: 3d8b109d-285c-952f-2fa4-9fa244c2a3f9
Content: Use AllowSelfServicePurchase for the MSCommerce PowerShell module
Content Source: microsoft-365/commerce/subscriptions/allowselfservicepurchase-powershell.md
Service: o365-administration
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

Today I will try to add explanation

@yogkumgit, Please look in this PR #7273.

@RAJU2529 Thank you very much for the contribution and updating the documentation with PR. @alesteravo Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


PyROOT and Notebook Fail to Load

Issue:
After installation by the instructions, I am unable to  import ROOT  in python or run  root --notebook  on Ubuntu 18.04 LTS. The following is the terminal output when I try. Just running  root  on its own works perfectly.

(std) nk42@MXP:~/workspace$ conda activate root_env
(root_env) nk42@MXP:~/workspace$ root
   ------------------------------------------------------------
  | Welcome to ROOT 6.18/00                  https://root.cern |
  |                               (c) 1995-2019, The ROOT Team |
  | Built for linuxx8664gcc on Jun 29 2019, 20:36:00           |
  | From tag , 25 June 2019                                    |
  | Try '.help', '.demo', '.license', '.credits', '.quit'/'.q' |
   ------------------------------------------------------------

root [0] .demo
root [1] .q

Taking a break from ROOT? Hope to see you back!

(root_env) nk42@MXP:~/workspace$ python
Python 3.7.3 | packaged by conda-forge | (default, Jul  1 2019, 21:52:21)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ROOT
Error in <TCling::RegisterModule>: cannot find dictionary module libPyROOT_rdict.pcm
>>> quit()
(root_env) nk42@MXP:~/workspace$ root --notebook
Traceback (most recent call last):
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/traitlets/traitlets.py", line 528, in get
    value = obj._trait_values[self.name]
KeyError: 'allow_remote_access'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 864, in _default_allow_remote
    addr = ipaddress.ip_address(self.ip)
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/ipaddress.py", line 54, in ip_address
    address)
ValueError: '' does not appear to be an IPv4 or IPv6 address

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/nk42/miniconda3/envs/root_env/bin/jupyter-notebook", line 11, in <module>
    sys.exit(main())
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/jupyter_core/application.py", line 266, in launch_instance
    return super(JupyterApp, cls).launch_instance(argv=argv, **kwargs)
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/traitlets/config/application.py", line 657, in launch_instance
    app.initialize(argv)
  File "</home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/decorator.py:decorator-gen-7>", line 2, in initialize
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/traitlets/config/application.py", line 87, in catch_config_error
    return method(app, *args, **kwargs)
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 1630, in initialize
    self.init_webapp()
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 1378, in init_webapp
    self.jinja_environment_options,
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 159, in __init__
    default_url, settings_overrides, jinja_env_options)
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 252, in init_settings
    allow_remote_access=jupyter_app.allow_remote_access,
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/traitlets/traitlets.py", line 556, in __get__
    return self.get(obj, cls)
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/traitlets/traitlets.py", line 535, in get
    value = self._validate(obj, dynamic_default())
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 867, in _default_allow_remote
    for info in socket.getaddrinfo(self.ip, self.port, 0, socket.SOCK_STREAM):
  File "/home/nk42/miniconda3/envs/root_env/lib/python3.7/socket.py", line 748, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
(root_env) nk42@MXP:~/workspace$

One thing I could note is that I am running it on the windows linux subsystem, but I also tried the python import test on a pure Ubuntu machine with the same issue.
I also tried with python 2.7 with no influence on the error.
This is an amazing way to install root and I hope to get to use it.

 From quickly testing it looks like it might be a harmless error so it shouldn't stop you from using ROOT.
For Jupyter, can you try running jupyter notebook instead of root --notebook? The ROOT kernel should be available there so there is no need to use the --notebook option. (Or you could also install jupyterlab and run jupyter lab which is the newer version of Jupyter.)

The  jupyter notebook  and  jupyter lab  options both work. I did still get the same  module libPyROOT_rdict.pcm  error but it didn't appear to affect the functionality as I was able to plot test histograms without issue.

(std) nk42@MXP:~/workspace$ jupyter lab --no-browser
[I 06:07:18.758 LabApp] JupyterLab extension loaded from /home/nk42/miniconda3/envs/std/lib/python3.7/site-packages/jupyterlab
[I 06:07:18.760 LabApp] JupyterLab application directory is /home/nk42/miniconda3/envs/std/share/jupyter/lab
[W 06:07:18.762 LabApp] JupyterLab server extension not enabled, manually loading...
[I 06:07:18.767 LabApp] JupyterLab extension loaded from /home/nk42/miniconda3/envs/std/lib/python3.7/site-packages/jupyterlab
[I 06:07:18.767 LabApp] JupyterLab application directory is /home/nk42/miniconda3/envs/std/share/jupyter/lab
[I 06:07:18.768 LabApp] Serving notebooks from local directory: /home/nk42/workspace
[I 06:07:18.770 LabApp] The Jupyter Notebook is running at:
[I 06:07:18.770 LabApp] http://localhost:8888/
[I 06:07:18.771 LabApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[I 06:07:24.018 LabApp] 302 GET / (<IP_ADDRESS>) 1.85ms
[W 06:07:24.680 LabApp] Could not determine jupyterlab build status without nodejs
[I 06:07:25.621 LabApp] Kernel started: 20e9cb41-8b2b-42ae-a497-3f46cbe881e2
Error in <TCling::RegisterModule>: cannot find dictionary module libPyROOT_rdict.pcm
[IPKernelApp] ERROR | Can't load '/home/nk42/miniconda3/envs/std/lib/python3.7/site-packages/metakernel/magics/parallel_magic.py': error: No module named 'ipyparallel'
[I 06:07:32.246 LabApp] Adapting to protocol v5.1 for kernel 20e9cb41-8b2b-42ae-a497-3f46cbe881e2
[I 06:07:32.263 LabApp] Adapting to protocol v5.1 for kernel 20e9cb41-8b2b-42ae-a497-3f46cbe881e2
[I 06:09:25.520 LabApp] Saving file at /Untitled.ipynb

That's reassuring, is root --notebook only broken on the Windows Subsystem for Linux? If so it's probably a ROOT bug rather than a conda packaging issue.
Do you have a folder called .rootnb in your home directory? Renaming or deleting it might help.

I was able to reproduce the  root --notebook  error on a pure Ubuntu 18.04 machine over ssh.

"""
(std) nk42@MXP:~$ ssh ntcuser@lab109
Password:
ntcuser@lab109's password:
Welcome to Ubuntu 18.04.2 LTS (GNU/Linux 4.18.0-22-generic x86_64)

Documentation:  https://help.ubuntu.com

Management:     https://landscape.canonical.com

Support:        https://ubuntu.com/advantage

Canonical Livepatch is available for installation.

Reduce system reboots and improve kernel security. Activate at:
https://ubuntu.com/livepatch

123 packages can be updated.
0 updates are security updates.
Your Hardware Enablement Stack (HWE) is supported until April 2023.
*** System restart required ***
Last login: Mon Jul  8 04:05:18 2019 from <IP_ADDRESS>
(base) ntcuser@ntc-inspiron:~$ conda activate root_env
(root_env) ntcuser@ntc-inspiron:~$ root --notebook
Traceback (most recent call last):
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/traitlets/traitlets.py", line 528, in get
value = obj._trait_values[self.name]
KeyError: 'allow_remote_access'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 864, in _default_allow_remote
addr = ipaddress.ip_address(self.ip)
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/ipaddress.py", line 54, in ip_address
address)
ValueError: '' does not appear to be an IPv4 or IPv6 address
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ntcuser/miniconda3/envs/root_env/bin/jupyter-notebook", line 11, in
sys.exit(main())
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/jupyter_core/application.py", line 266, in launch_instance
return super(JupyterApp, cls).launch_instance(argv=argv, **kwargs)
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/traitlets/config/application.py", line 657, in launch_instance
app.initialize(argv)
File "</home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/decorator.py:decorator-gen-7>", line 2, in initialize
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/traitlets/config/application.py", line 87, in catch_config_error
return method(app, *args, **kwargs)
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 1630, in initialize
self.init_webapp()
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 1378, in init_webapp
self.jinja_environment_options,
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 159, in init
default_url, settings_overrides, jinja_env_options)
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 252, in init_settings
allow_remote_access=jupyter_app.allow_remote_access,
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/traitlets/traitlets.py", line 556, in get
return self.get(obj, cls)
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/traitlets/traitlets.py", line 535, in get
value = self._validate(obj, dynamic_default())
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/site-packages/notebook/notebookapp.py", line 867, in _default_allow_remote
for info in socket.getaddrinfo(self.ip, self.port, 0, socket.SOCK_STREAM):
File "/home/ntcuser/miniconda3/envs/root_env/lib/python3.7/socket.py", line 748, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
(root_env) ntcuser@ntc-inspiron:~$
"""

The error could be caused by the notebook trying to open a browser over ssh or through the subsystem (so I also think it could be a ROOT bug). I typically use the  --no-browser  flag when starting a jupyter notebook, but things would work without that flag just with an additional inconsequential error. But the   --no-browser  flag doesn't seem to do anything for the  root --notebook  command.
I renamed the  .rootnb  folder with no change to the error. It seems to rewrite the  .rootnb  folder.

Fixed binaries for the PyROOT error message are now deployed so you can update to them.

I renamed the .rootnb folder with no change to the error. It seems to rewrite the .rootnb folder.

That's expected, ROOT recreates it if it doesn't already exist. As you can get errors if it was made by a different installation. I'd recommend just using Jupyter directly as it will be the same (or better if you use Jupyter lab).

Sounds good. Thanks a bunch!

I asked the ROOT team and the root --notebook problem is a known issue will be fixed in the next release of Jupyter notebook. See https://sft.its.cern.ch/jira/browse/ROOT-9920 for details.


PowerShell - v-smandalika - 9375980 - Updated the information of a parameter-specific section

Hi @AshaIyengar21 ,
SME Nelson Riera has approved the updates we made in this PR. Hence, we are assigning this PR to for your help in reviewing it and in attaching the Sign off label.
Thanks,
@v-smandalika


Add reduce method to array

This PR adds a reduce methods to the array structure.
This method is very useful if you want to apply a function to all elements of an array.  Using fold for this purpose is cumbersome since there is no information about the starting element and retrieving it is not trivial.
User-facing API
#assert.eq(
  (2, 3).reduce((a, b) => (a + b) * 2),
  10,
)

This PR adds a reduce methods to the array structure.
This method is very useful if you want to apply a function to all elements of an array. Using fold for this purpose is cumbersome since there is no information about the starting element and retrieving it is not trivial.
User-facing API
#assert.eq(
  (2, 3).reduce((a, b) => (a + b) * 2),
  10,
)

Accidentally closed PR :)

Thanks!


Google SSO updates

Removed step1 as unneccessary
Changed order to enable API near start to prevent UI errors
Added authorised domains step
Updated screenshots

Updated the changes. Is there any issue with the new screenshots not being same size as rest on page?

Thanks! ../google_authorised_domains.png is a bit smaller compared to the other images, but otherwise it seems fine, at least here https://github.com/mattermost/docs/blob/2b54151e988ebc2eadc9c4857da7f0f0cc95018b/source/deployment/sso-google.md
Or did you feel the images were much different in size?

Ok, as long as you are happy. Didn't know how particular we were.


Lint a second path or use go workspaces for price feeder

The oracle module introduces a second go.mod file in the price-feeder folder.
We should either explicitly add the price-feeder folder to the linter, or begin using go workspaces.
Since go workspaces (go.work) has significant tradeoffs, we should.... flip a coin?

Just adding the folter to the linter is the better option here imo

Thank you I'll take care of that shortly


[Spring Security]简介

https://vincentmi.gitbooks.io/spring-security-reference-zh/content/1_introduction.html

Awesome!


Metrics not found warnings should be silenced (without verbose flag)

[ ]  we need add --verbose flag and silence warnings while checking pods.

Feature added.


feat: add trace id to response header

Hi!
I added trace id to response header.
#22

@riandyrn Hi! Can u review my PR?

Hey, @badygin-yakov
Thanks a lot for the PR! I think this is good enough. 👍
Would you like to also accommodate @batazor request?

Hello, @batazor
Doesn't this PR already support customizing the header name?
You can check here & here.
Or maybe this feature does not meet your needs?

Hello, @jcarter3
Would you like to confirm if this PR resolves your issue in #22?


Readd a daily run of the cleanvm matrix

+1

@dirkmueller shouldn't that be triggered after the trackupstream job is done?

+1

shouldn't that be triggered after the trackupstream job is done? And I guess some time is needed so the package builds are done triggered by trackupstream

Hm, true. It seem in the past (before the jbb switch) we ran it a 4am daily (https://github.com/SUSE-Cloud/automation/commit/552a88954e74fc957725a4d6a458dce1eb2c6249#diff-54668dddec90538b7be71f34abba3096L90). Not sure if that is enough time to rebuild everything, trackupstream runs a 1am IIRC.

@rhafer @toabctl I don't think that makes any difference, since it is very unlikely that OBS would have finished building the repositories + publishing within 3 hours. But I've restored the 4am time slot now to make it more predictable when it happens.

+1

+1

:+1:


fixed windows support

using where which is the windows equivalent to linux which
closes https://github.com/mnapoli/pretty/issues/14

Thank you!


HA Cluster provider support

Hi Team,
Any plan to roll out the support of HA Cluster provider migration in the provided migration script from AMS Classic to new one.

Hi,
Currently, we do not have plans for adding migration for HA Cluster providers, please create them manually from the azure portal, let us know in case you are facing any problems.
Below link has the list of steps to follow while setting up the provider
https://learn.microsoft.com/en-us/azure/virtual-machines/workloads/sap/configure-ha-cluster-azure-monitor-sap-solutions
Also, ensure that you create a provider for both the nodes of your HA cluster.
Thanks.

Please re-open this issue of raise a ticket on azure portal in case more assistance is needed.


Inject pytest.parameters using different solvers

Please note that a public GitHub server would have no access to a Mosek License. Of course, we don't want to expose the license code for a Mosek License in a repo.

There must be a way to trigger some tests only if they run on our local machines

Use
@pytest.mark.parametrize("solver", [cp.ECOS, cp.MOSEK, cp.CLARABEL])
def test_min_var(solver):
    if os.getenv("CI", False) and solver == cp.MOSEK:
        pytest.skip("Skipping MOSEK test on CI")

Test objective values


Is there support for two player ?

the controls only controll one player,how to set two kinds keys

It works with joysticks.
If you want both players using the keyboard, you can try tweaking the code here:
https://github.com/fogleman/nes/blob/master/ui/util.go#L53-L64
https://github.com/fogleman/nes/blob/master/ui/gameview.go#L133-L140


Error: Unable to download xmlrpc source files

I keep running into this error when trying to execute the script.

Error: Unable to download xmlrpc source files from https://svn.code.sf.net/p/xmlrpc-c/code/stable
This is most likely a network error, if your network is working, then it is likely a temporary issue with the relevant file server
Below is the error log from rtinst.log
Fetching rtinst scripts
Configuring SSH
Generating a 2048 bit RSA private key
..+++
.............................+++
writing new private key to '/etc/ssl/private/vsftpd.pem'
Downloading rtorrent source files
rtinst.sh: line 502: svn: command not found

ok svn was not installed as it should have been earlier in the script. Not quite sure why but try the following
run the command - sudo apt-get -y install svn
then rerun the script

Sorry, the issue was on my end as the sources list had some issue. Fixed that, ran the above command on install svn. All working good now.
Thanks a lot!


Add commands and hook useful in cci

This PR adds two commands and a hook that have been useful in the migration process to Conan 2.
list_v2_ready is the least important of them, and export_all_sources has been pretty useful. The hook is a modified version from the one used in CCI, but this one is guarded under a conf to avoid it from running on users that install this repo. We might want to remove it, or it and its associated list_v2_ready command, which is not too useful in the long run.
I'll add some tests once we decide which ones stay and which ones go (if any)

Merge Conflicts :(


v.2.2.1 On FireTV tiles cannot be selected

When you go into season 2021, or any other season, you cannot select which video to play.
The tiles move to the left as you press to the right, but no tile can be selected and played.
Previously used version 2.1.1 where it was fine.
Cleared data, uninstalled it, installed 2.2.1
If you need any more feedback, please ask.
Thank you for your time and the great work, well done!

Can you record a video of your issue?

Here you are.
Best regards!
https://user-images.githubusercontent.com/68645590/126539869-f0b7efaf-5b20-4967-a41a-eb4d10831093.mp4

Hey, just finished updating and now I have this same problem.

Hi guys, could you join the Alpha program test to help me with this issue? I just released a build there that should be available in some minutes aiming to solve this issue
Click this link on web to join the Alpha program: https://play.google.com/apps/testing/com.github.leonardoxh.f1 (If you installed the app via Google PlayStore)

Hello,
I just installed the new version 2.2.2, but i still have the same problem.
I can't join the Alpha program for some reason..
The app is not available for this account.
Your account is currently not eligible for this app's testing program.

Hmmmmmmmmm If you were not available to join the alpha program how did you install it? You compiled from the branch itself?

I sideloaded through the Downloader app on the Fire TV Stick.

You sure it is v2.2.2 ? Because I did not publish it yet...
By the way, can you try to side load this apk:
https://github.com/leonardoxh/race-control-tv/releases/tag/v2.2.3
I did some other changes, I might just found something.

Now i cant enter any of the menus, when i choose a season, it briefly loads and return to choose a season again.

Tried 2.2.3. Tries the load the current season, fails and returns to season selection screen

Oh god apologies.
Wrong apk, can you please try with this one?
https://github.com/leonardoxh/race-control-tv/releases/tag/v2.2.4

Ok, now i can play the videos, but i can't see what i am choosing, the indicator of what is selected is gone.

Cool that is good at least, I will see this tomorrow

Hi I think I got it, had to revert more stuff from another PR.
I uploaded the apk to my google drive this time to avoid create another release, if it is working I will then release it
https://drive.google.com/file/d/1Qr6nE-E8QWGRFeNUWDZD9YUdXZ_1xFpF/view?usp=sharing

Hey there, the 2.2.5 has the same issue, i can play the videos, but can't see what is selected.

What about this one?
It will still show as v2.2.5

This one is good! Working fine now.

Fantastic I will publish it right away.

Thank you very much for the testing and patience. I released v2.2.5
Closing this issue for now


BUG: Lending Bots TVL is also wrong

@rootedbox Please match the tracking_price of the Curve Lending bot with USD price same as other bots.


Add "FOR UPDATE SKIP LOCKED" DeleteExpiredQuery

Postgresql 9.5 onwards supports this feature.
It prevents deadlocks in such scenarios were a delete is done with an inner select, see
https://stackoverflow.com/questions/68626800/deadlock-when-using-delete-on-postgresql
Assume that rely on the version 9.5 and higher is ok, since EOL
https://endoflife.software/applications/databases/postgresql
shows that you should have a newer DB

@peterhaochen47 @bruce-ricard question is, if you know tests and/or situation where postgresl < 9.5 is in use ?
We have seen lock situations in DB monitoring and found this statement enhancement which prevents locks.
Each login with authz will have entries in oauth_code and revocable_tokens and in similar time we have delete operations, thus this can lead to locks

found release notes
https://github.com/cloudfoundry/uaa/releases/tag/v74.13.0
-> for postgresql we have condition 9.5. and higher already, so this change can be done


Update mrlearning-base-ch5.md

loc header

Docs Build status updates of commit a71d143:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/mrlearning-base-ch5.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix for 2228

This is a simple typo fix which changes error in the various responses to the proper variable to avoid the undefined error in the dev console.

Fixing #2228 error


Edits to FAQs and footer

This PR includes text editions and collapsible box sections for the FAQs page, text update of the About section of the footer (following the recommended wording), a new link to the Terms of use page, and the User guide.
Help to modify a few details in the footer are needed, which are described here https://github.com/ScilifelabDataCentre/genome-portal/pull/67#issuecomment-2458386608.

Help to modify a few details in the footer are needed, which are described here https://github.com/ScilifelabDataCentre/genome-portal/pull/67#issuecomment-2458386608.

Thanks, I will work on the issues described about the hugo/layouts/partials/footer.html file here and commit a change to this branch then.

I'm finished with changes to the footer, I will work on the navbar on this branch now, I will therefore be editing the files: hugo/layouts/partials/navbar.html and hugo/assets/css/styles.css.

First part of the User guide in 334e3c9

Perfect! Thanks @brinkdp for the edits.

@apfuentes I've now looked at the current version of the user guide (everything until 2. Useful genome browser features). It looks excellent! This is quite some work, thank you so much for this! I have nothing to add for now.
@RMCrean After the latest Navbar update, User guide renders on two lines in Firefox on my computer. Zoom level and responsiveness does not seem to affect it. When I open it in Safari, the link conforms to the bottom line as I think is intended.
Firefox:

Safari:

Hi all, I will fix the conflict now.
Thanks for the report @brinkdp, I will work on this now and then I can merge it.
Thanks @apfuentes, it's hard to get them to line up exactly so I'll see what I can do now (but I will be working on the presentation instead most of today), otherwise I'll save this for after the launch.

@brinkdp, I've dropped the font sizes and image sizes for the different screen sizes where the navbar is expanded, as I couldn't reproduce your issue on my firefox or chrome, could you pull the latest changes and if it looks okay, merge this branch?

I just spotted a few typos in FAQ page, I will change them now.

@RMCrean any idea why Trivy - Security scan is failing?

The navbar looks good now, thanks @RMCrean!
The Trivy thing has been going on for a few weeks now and it is nothing major to worry about. It seems that they get so many requests that the checks sometimes time-out and give a fail message.


Fix gitignore to include Jekyll generated files

.

Can one of the admins verify this patch?

@AppInventorWorkerBee ok to test


Expose Raw Frame Buffers

MediaCapture abstracts over the need to manage any of the internals of how bevy_media_capture works. This also means it isn't easy / obvious to figure out how to get the raw frame data being stored.
Consider adding some methods to make this a first-class function (and to provide more utility with all encoding formats disabled).
Possible ideas:
get_last_frame and take_last_frame - for getting a clone of the most recently captured frame, or popping it from the stack and taking it, respectively
get_stored_frames and take_stored_frames - for getting a clone of the stored frames, or taking sole ownership of the stored frames, respectively

What about adding a Recorder trait, with some sample recorders (e.g. gif) provided by the library, but customizable easily by end users.
Here's an example of how the API could look:

adding the recorders in a builder pattern (.add_recorder::<CustomRecorder>())
inserting MediaCapture as a component for each camera where its needed - this way no need to link the id's. Internally, maybe a few instances could be used but end-user API more bevy-style this way (.insert(MediaCapture::<CustomTracker>::new().set_duration(Duration::from_secs(5)));)

use std::time::Duration;
use bevy::prelude::*;
use bevy_capture_media::{MediaCapture, BevyCapturePlugin};

pub fn spawn_cameras(
    mut commands: Commands,
) {
    let camera_entity = commands
        .spawn_bundle(Camera2dBundle::default())
        .insert(MainCamera)
        .insert(MediaCapture::<CustomTracker>::new().set_duration(Duration::from_secs(5)));
}

pub fn take_screenshot(
    input: Res<Input<KeyCode>>,
    mut capture: Query<&mut MediaCapture<CustomTracker>, With<MainCamera>>,
) {
    if input.just_released(KeyCode::RShift) {
        capture.start();
    }
}

#[derive(Component)]
pub struct MainCamera;

fn main() {
    App::new()
        .add_plugin(DefaultPlugins)
        .add_plugin(bevy_capture_media::BevyCapturePlugin::new().add_recorder::<CustomRecorder>())
        .add_startup_system(spawn_cameras)
        .add_system(take_screenshot)
        .run();
}

pub struct MediaCapture<T: Recorder> {
  recorder: T
}

pub trait Record {
  // some common methods, like receive_frame
}

pub struct CustomRecorder;

impl Recorder for CustomRecorder {
   // ...
}

note: didn't try if possible in practice... (especially the storage of trait, if multiple implementations used)


No output exmaple

There no example with output and an explaining what it means .

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6444fdcc-eab2-9bb3-1b94-34914af628c9
Version Independent ID: 31345b9a-df7a-8403-7fda-86784646d2c6
Content: tracert
Content Source: WindowsServerDocs/administration/windows-commands/tracert.md
Product: windows-server
Technology: windows-commands
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

Hey Diramu,
Thanks again for contacting Microsoft. We value your feedback.
A documentation change has been made adding a tracert output example with included description of what each column represents. Changes will be live after the next business day. We will now be closing this thread.
Thank you and have a most pleasant day.
#please-close


Files table and management system

This system should be based around a files or objects table and should allow:

Linking to files stored in S3 buckets (either under our control or managed externally)
Tracking of basic bucket/file metadata (e.g., hashes, access dates, content types) so we don't have to grab it from AWS each time
Support eventual development of a basic suite of tools for file hygiene: checking/removing/verifying access etc.

This will be critical for all manner of ingestion and file management tasks.
Prior art:

This storage system schema I implemented based on Supabase's design.
Supabase storage system.

While Supabase's API isn't exactly what we want, I think (it assumes storage in a single S3 bucket and is generally quite tailored to their use case) maintaining alignment and potentially compatibility would be useful.

Starting to work on this in #13 !

@brianaydemir @CannonLock , it sounds like this is being worked on — is there a stable pull request that can be separated from the rest of the additions for your user interface? Or is the schema somewhere else?


Support Mechanical Turk sandbox mode

Currently the endpoint prefix is hardcoded for mturk:
host = get_host("mturk-requester", client)
...
defp get_host(endpoint_prefix, client) do
    if client.region == "local" do
      "localhost"
    else
      "#{endpoint_prefix}.#{client.region}.#{client.endpoint}"
    end
end

Since there is a sandbox development endpoint, it would be nice to support the "mturk-requester-sandbox" prefix as well.
The following lines allow passing the prefix through the options:
defp request(client, action, input, options) do
    prefix = Keyword.get(options, :endpoint_prefix, "mturk-requester")
    options = Keyword.delete(options, :endpoint_prefix)
    client = %{client | service: "mturk-requester"}
    host = get_host(prefix, client)
   ...
end

Then, one can pass the prefix like:
AWS.MechanicalTurk.list_h_i_ts(client, %{}, endpoint_prefix: "mturk-requester-sandbox")

Not sure if this is the best approach or if it would make more sense to pass this through the client though.
The code for the prefix fix: https://github.com/4knahs/aws-elixir/blob/mturk-sandbox/lib/aws/mechanical_turk.ex#L577

Solved #2


jrnl: 4.0.1 -> 4.1

Description of changes
See https://github.com/jrnl-org/jrnl/releases/tag/v4.1 for changelog. This update removes the ansiwrap dependency.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 265636 run on aarch64-darwin 1

2 packages built:

jrnl
jrnl.dist


[QUESTION] Can you update the response data in a UseAfter middleware?

Pretty much all the details in the title. I'm trying to filter data and update the response using a UseAfter middleware. Ty :)

You have two solutions: middleware or interceptor (https://tsed.io/docs/interceptors.html#decorators).
With the middleware:
class MyAfterMiddleware {
   use(@Context() ctx: Context) {
      console.log(ctx.data)
      ctx.data = mapData()
  }
}

See you
Romain

I was under the impression that I could use context although I wasn’t entirely sure how updating the context within the middleware was going to update the context globally. Although since you’ve mentioned it I’m assuming you’re using a get and set in the context class in order to set it globally right?

Context is a ref which contain the current data returned by the endpoint. Context is attached to the express request, and will be consumed by Ts.ED to create the response.


Format problem in TechIndicators get.bbands

Code:
get.bands gives different data format for different tickers.
bollinger_time_series = TechIndicators(key=api_key, output_format='pandas', indexing_type='data')
bollinger, meta_bollinger = bollinger_time_series.get_bbands(symbol=symbol, interval='daily', time_period=20, series_type='close', nbdevup=3, nbdevdn=3, matype=0)
...
sym = ['DECK']
data = alpha_vantage_daily_adjusted_simple(sym)
// Order: Real Middle Band; Real Upper Band; Real Lower Band
sym = ['KAR']
data = alpha_vantage_daily_adjusted_simple(sym)
// Order: Real Middle Band; Real Lower Band; Real Upper Band
This is very inconvenient for data handling.

Temporarily closing this issue due to a prolonged period since the last response was posted. Will re-open if needed.


Drop support for __global__ params in --param-file YAML files

See #167, #168, and this point of feedback from @nickjalbert in #173:

The semantics of __global__ params were a bit confusing.  If I understand correctly, they only get passed to the call to the entry point.  This is maybe a bit of a misnomer because we'll, for example, call __init__ functions and not pass them, even though I often want the global params when I'm setting up my components.

This is done.


Received an error when choosing 'no' to automatically create an EAS project

Issue tracker is ONLY used for reporting bugs. New features should be discussed on our discord, in the #create-expo-stack channel.

Expected Behavior

An error should not have occured on selecting 'no' to automatically creating an EAS project.
Current Behavior

I received an unexpected error

Possible Solution

Look into the reason why I received an error. Possibly remove the error if there's nothing wrong.
Steps to Reproduce

Create a project using create-expo-stack
Select 'no' for the question Would you like to automatically create an EAS project for @username?

CES Config File

{
  "cesVersion": "2.11.25",
  "projectName": "n",
  "packages": [
    {
      "name": "expo-router",
      "type": "navigation",
      "options": {
        "type": "stack"
      }
    },
    {
      "name": "nativewind",
      "type": "styling"
    },
    {
      "name": "supabase",
      "type": "authentication"
    }
  ],
  "flags": {
    "noGit": false,
    "noInstall": false,
    "overwrite": false,
    "importAlias": true,
    "packageManager": "npm",
    "eas": true
  },
  "packageManager": {
    "type": "npm",
    "version": "10.9.0"
  },
  "os": {
    "type": "Windows_NT",
    "platform": "win32",
    "arch": "x64",
    "kernelVersion": "10.0.22631"
  }
}

if you choose to setup eas but then say no when it asks to setup eas for you then that seems like its a fail state. Is that not what you would expect? Could you explain what you would expect to happen?

Closing since there's no response, let me know if we should reopen


Remove redundant parameter in test scripts

With PR #10854, Sql-database-projects UTs were moved out to run just in canary until all the failures were fixed, with the use of new parameter (RUN_DBPROJECT_TESTS). But with PR #11179, the newly added parameter isn't respected anymore and the tests have been running in all pipelines regardless.
This PR cleans up the test scripts to remove the redundant parameter.

are you going to remove it from the pipelines as well?

Yes. I will do that before checking in the change.
These are the only two pipelines where the variable is been used.
Azure Data Studio - Canary: Variable set to True.
Azure Data Studio - PR Validation: Set to False.

Pull Request Test Coverage Report for Build 413739488

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.5%) to 43.04%

Totals

Change from base Build 413614681:
1.5%

Covered Lines:
24001

Relevant Lines:
51094

💛  - Coveralls

Removed variables, closing the PR.


Airport select block the page when have houndreds of airports

In our environment we have more than 15000 airports inside the database, this cause that we can't load any page where the select with airports are present.
Dev version
To Reproduce
Steps to reproduce the behavior:

Install phpvms
Import database with thousands of airports
See error

Expected behavior
The system use select2 that provide a function to sarch dinamycally without need load all airports in the select box when load the page

I think #1574 closes this one


Standardise format of Accumulo Store unit tests

Currently there are several different formats for the tests used by the Accumulo Store.  These should be standardised before refactoring of the store begins.  Has to be done before gh-190

Merged into develop.


Question regarding Joint-FT

Hello Authors,
Thank you for releasing the code. Could I ask how you implemented the Joint-FT experiment? More specifically:

Which codebase/configs was used?
What training settings were used for this experment? (Learning rate, epochs, learning rate schedule, etc).

Best,
Jinhyung Park

Hi Jinhyung,
Thank you for your interest in our work! As mentioned in Sec. 5.2, we trained Joint-FT and Seq-FT using the recommended fine-tuning strategy of ViT [5], with the same number of training epochs as ours.
[5] Alexey Dosovitskiy, Lucas Beyer, Alexander Kolesnikov, Dirk Weissenborn, Xiaohua Zhai, Thomas Unterthiner, Mostafa Dehghani, Matthias Minderer, Georg Heigold, Syl- vain Gelly, Jakob Uszkoreit, and Neil Houlsby. An image is worth 16x16 words: Transformers for image recognition at scale. In Proceedings of the International Conference on Learning Representations (ICLR), 2021.

Which codebase/configs were used?
We used this codebase with data.num_init_classes=0 and data.num_increment_classes=N, where N is 100 or 200 for CIFAR100/ImageNet-R.

What training settings were used for this experiment? (Learning rate, epochs, learning rate schedule, etc.)
Learning Rate/Batch Size: 0.005/64 (It should be 0.01/128, but it requires more GPU memory)
Epochs: 5/50 for CIFAR100/ImageNet-R
Optimizer/LR Schedule: SGD/Cosine

I hope this addresses your questions. If you have any further inquiries or need additional information, please feel free to let me know.
Best regards,
Qiankun Gao

I see - thank you so much for your response! Apologies; I wasn't too familiar with the codebase yet.

@Divadi You are welcome. If you encounter any further issues or have additional questions, please don't hesitate to reach out. We're here to assist you in any way we can.


Common Login issues and Troubleshooting questions

Can you please include basic authentication and certificate issues related to users/context and in general standard pod issues. Like what if a service pod is down on Master node/worker node? How to troubleshoot it etc etc

@Tejas-udeshi working on adding the troubleshooting scenarios. Added for applications.


Add evaluation data for amazon_reviews_multi

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

As discussed with @lewtun, we are closing this PR, because it requires first the task names to be aligned between AutoTrain and datasets.


How to limit the query size?

Does this have the syntax of offset and limit just like mysql database.

here is the answer: https://github.com/realm/realm-cocoa/issues/2608


factory.LazyFunction not registered at the root module

Tried to call the LazyFunction helper as specified in the documentation, but it doesn't seems to be exposed by the factory module:
>>> import factory
>>> factory.__version__
'2.6.1'
>>> factory.LazyAttribute
<class 'factory.declarations.LazyAttribute'>
>>> factory.LazyFunction
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'LazyFunction'

Is the documentation introduced by #267 wrong or should LazyFunction be exposed directly from the factory module?

Ok, forget it. Everything's fine. Just that the documentation reference the development branch and #267 hasn't been released yet... :expressionless:


Buddy memory allocation Algorithm Implementation in Java, C++, C and Python

Is your feature request related to a problem? Please describe.
The repo does not contain Buddy System Memory Allocation Algorithm, i want to work on this issue, kindly assign me this issue
Describe the solution you'd like
I would add an implementation of the algorithm in C, C++, Java & Python.

Assigned!
@ranjanmangla1 : C, C++, Python and Java


manually add typed and with_type methods

Closes #1384
I've also found DropTarget::new which could receive the same treatment, but that's a more complex case, because it can also accept the type G_TYPE_INVALID when the user wants to specify multiple GTypes, so I've just skipped that.

Maybe it can be split into DropTarget::new, DropTarget::with_type and DropTarget::with_types?

There are other ones as you can tell from the link i shared in the issue

Please add a note to the changelog as well

Maybe it can be split into DropTarget::new, DropTarget::with_type and DropTarget::with_types?

That is what I ended up doing. It is a much better API :-)
Replaced by https://github.com/gtk-rs/gtk4-rs/pull/1415


Add a 5 minute cooldown to the topic command

Relevant Issues

Closes #868
Description

Using the command while it's on cooldown will hit the error handler, which sends an error message showing how long is left on the cooldown, which is deleted after 7.5 seconds.

Did you:

[x] Join the Python Discord Community?
[x] Read all the comments in this template?
[x] Ensure there is an issue open, or link relevant discord discussions?
[x] Read and agree to the contributing guidelines?

I'm not a fan of this solution. I think there are relevant reasons to use two topic commands in a five minutes span. I'd propose one of the following:

Reduce to one minute
Add a re-roll reaction that can be only used by the command runner


Create dataset loader for Filipino Product Reviews (Lazada)

Dataloader name: lazada_review_filipino/lazada_review_filipino.py
DataCatalogue: http://seacrowd.github.io/seacrowd-catalogue/card.html?lazada_review_filipino

Dataset
lazada_review_filipino

Description
The dataset contains over 900+ weakly annotated Filipino reviews scraped from the Lazada Philippines platform. Each review is associated with a five star point rating where one is the lowest and five is the highest.

Subsets
-

Languages
fil, tgl

License
Creative Commons Attribution Non Commercial 4.0 (cc-by-nc-4.0)

Homepage
https://github.com/EricEchemane/Filipino-Tagalog-Product-Reviews-Sentiment-Analysis/tree/main/data

HF URL
-

Paper URL
https://github.com/EricEchemane/Filipino-Tagalog-Product-Reviews-Sentiment-Analysis/tree/main

#self-assign

Yep working on this issues got busy with some things but will try to wrap this issues by next week.

I'll un-stale this for now. Please do add a tag pr-ready whenever you have finished on your dataloader so that the bot won't tag this issue as stale or let us know if you need more time for this issue.

Sorry couldn't work on this last weekend due to christmas holidays and celebration will try to conclude this, this weekend.

Thanks for the update, @bp-high! no rush on this; please take your time to enjoy ur holiday!

Hi @bp-high, may we know the update on this dataloader issue? It's been 3 weeks since the last poke from the SEACrowd stale-checker, and we might consider unassigning if there's no progress update in the next 24 hours.


Header bar (on homepage at least) is very messy on mobile

fixes are pretty obvious....

Fixed on static version, will be pushed this afternoon


chore: Daniel Bourke Youtube Channel

Fixes Issue
#775

Changes proposed
I have incorporated an additional learning resource for TensorFlow and established a dedicated JSON file to facilitate the inclusion of future resources pertaining to TensorFlow.

Screenshots

Note to reviewers

@rupali-codes, we need your force push

Hello @CBID2, I am wondering why the PR has not been merged yet. Could you please clarify if there are any issues with my contributions?

Hello @CBID2, I am wondering why the PR has not been merged yet. Could you please clarify if there are any issues with my contributions?

I think a deployment issue happened @Shiva-Sai-ssb. @rupali-codes, we need a force push

Hello @CBID2, I am wondering why the PR has not been merged yet. Could you please clarify if there are any issues with my contributions?

I think a deployment issue happened @Shiva-Sai-ssb. @rupali-codes, we need a force push

Thank you for your response. Therefore, it is necessary for @rupali-codes to perform a force push in order to merge this pull request, correct?

Hello @CBID2, I am wondering why the PR has not been merged yet. Could you please clarify if there are any issues with my contributions?

I think a deployment issue happened @Shiva-Sai-ssb. @rupali-codes, we need a force push

Thank you for your response. Therefore, it is necessary for @rupali-codes to perform a force push in order to merge this pull request, correct?

Yes, she is the owner of this repo so it only works for her

Hello @CBID2, I am wondering why the PR has not been merged yet. Could you please clarify if there are any issues with my contributions?

Please keep patience


After a sucessful updating, I found cookie information gone.

Problem
As the title says, cookie information is missing after a successful updating. I store user information in cookie, but now it's gone. I read the plugin wiki and got no workaround. Do you guys came across that?
I changed the storage using "cordova-sqlite-storage" instead of cookie, it worked, but I still want cookie can do a better job there. Got any idea?

Hello,
Is the cookie referencing an external domain, like  http://www.example.com or internal like file://?
My sign on cookies seem to stay intact on android, haven't test on ios yet.

@ivanixgames nope, I use ionic to build my apps, I'll show the code below:
var expireDate = new Date();
expireDate.setDate(expireDate.getDate() + 90);
$cookies.put('token', data.token, {'expires': expireDate});
$cookies.put('user', JSON.stringify(data), {'expires': expireDate});

Never mind , I'll close this issue!


Enable rrweb recording only in cli

The CLI code also sets some settings:
        await frame.evaluate(`
        window["METICULOUS_RECORDING_TOKEN"] = "${recordingToken}";
        window["METICULOUS_APP_COMMIT_HASH"] = "${appCommitHash}";
        window["METICULOUS_FORCE_RECORDING"] = true;
        window["METICULOUS_UPLOAD_INTERVAL_MS"] = ${uploadIntervalMs};
        window["METICULOUS_ENABLE_RRWEB_PLUGIN_NODE_DATA"] = true;
      `);

However we can't easily make changes to these, since it'll depend on the customer updating their version of the CLI. This can cause issues when the CLI and passive snippet make assumptions about their configuration options or defaults and get out of sync. Therefore maybe we should move to:
        await frame.evaluate(`
        window["METICULOUS_MANUAL_RECORDING"] = true;
        window["METICULOUS_RECORDING_TOKEN"] = "${recordingToken}";
        window["METICULOUS_APP_COMMIT_HASH"] = "${appCommitHash}";
        window["METICULOUS_UPLOAD_INTERVAL_MS"] = ${uploadIntervalMs};
      `);

And then we set the CLI defaults within the snippet. Eventually we could publish separate snippets for passive vs manual, and so reduce the size of the passive snippet.
This PR moves in this direction (CLI settings for snippet set in snippet not in CLI), and also disables rrweb recording in the passive snippet. This is because rrweb often produces > 2mb of data, which causes the session to be abandoned.

Oops pushed wrong repo / changes


How to get the 4bit model after training is completed

Hi,
When training is finished, i use merge_lora_weights_and_save_hf_model.py script get hf model  ,that is work! thank you !
but how to get the 4bit model?
Regards!
Zheng

Hi, we do not provide script to transform a model to 4 bit. We only support that you load in a model with 4-bit quantization.


异常的时候看下控制面板日志

异常的时候看下控制面板日志

2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43693 failure: protocol not supported
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43694 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43695 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43697 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43698 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43699 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43700 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43701 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43702 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43703 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43704 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43705 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43706 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43707 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43708 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43709 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43710 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43711 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43712 failure: protocol not supported
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:08:06[info] [TCP] <IP_ADDRESS>:43693 --> <IP_ADDRESS> match RuleSet(Netflix) using Proxy[jp02]
2020-11-03 20:07:36[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43715 failure: protocol not supported
2020-11-03 20:07:36[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:36[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43716 failure: protocol not supported
2020-11-03 20:07:36[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:36[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43717 failure: protocol not supported
2020-11-03 20:07:36[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:36[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43718 failure: protocol not supported
2020-11-03 20:07:36[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43719 failure: protocol not supported
2020-11-03 20:07:36[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:36[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43720 failure: protocol not supported
2020-11-03 20:07:36[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43721 failure: protocol not supported
2020-11-03 20:07:36[info] [TCP] <IP_ADDRESS>:43719 --> <IP_ADDRESS> match RuleSet(Netflix) using Proxy[jp02]
2020-11-03 20:07:37[info] [TCP] <IP_ADDRESS>:43721 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:37[info] [TCP] <IP_ADDRESS>:43720 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:37[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43723 failure: protocol not supported
2020-11-03 20:07:37[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43724 failure: protocol not supported
2020-11-03 20:07:37[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:37[info] [TCP] <IP_ADDRESS>:43723 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:37[info] [TCP] <IP_ADDRESS>:43724 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:38[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43726 failure: protocol not supported
2020-11-03 20:07:38[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43727 failure: protocol not supported
2020-11-03 20:07:38[info] [TCP] <IP_ADDRESS>:43727 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:07:38[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:38[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43728 failure: protocol not supported
2020-11-03 20:07:41[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43736 failure: protocol not supported
2020-11-03 20:07:41[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:41[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43738 failure: protocol not supported
2020-11-03 20:07:41[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:43[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:43[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43741 failure: protocol not supported
2020-11-03 20:07:43[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43742 failure: protocol not supported
2020-11-03 20:07:43[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43743 failure: protocol not supported
2020-11-03 20:07:43[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:43[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43744 failure: protocol not supported
2020-11-03 20:07:43[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43745 failure: protocol not supported
2020-11-03 20:07:43[info] [TCP] <IP_ADDRESS>:43742 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:07:43[info] [TCP] <IP_ADDRESS>:43743 --> <IP_ADDRESS> match RuleSet(Netflix) using Proxy[jp02]
2020-11-03 20:07:43[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43746 failure: protocol not supported
2020-11-03 20:07:43[info] [TCP] <IP_ADDRESS>:43744 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:43[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43747 failure: protocol not supported
2020-11-03 20:07:43[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43748 failure: protocol not supported
2020-11-03 20:07:44[info] [TCP] <IP_ADDRESS>:43747 --> <IP_ADDRESS> match RuleSet(Netflix) using Proxy[jp02]
2020-11-03 20:07:44[info] [TCP] <IP_ADDRESS>:43748 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43753 failure: protocol not supported
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43754 failure: protocol not supported
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43755 failure: protocol not supported
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43756 failure: protocol not supported
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43757 failure: protocol not supported
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43758 failure: protocol not supported
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43759 failure: protocol not supported
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43760 failure: protocol not supported
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43761 failure: protocol not supported
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43762 failure: protocol not supported
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43763 failure: protocol not supported
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43764 failure: protocol not supported
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43765 failure: protocol not supported
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43766 failure: protocol not supported
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43767 failure: protocol not supported
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43768 failure: protocol not supported
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43769 failure: protocol not supported
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:46[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43770 failure: protocol not supported
2020-11-03 20:07:46[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:47[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43772 failure: protocol not supported
2020-11-03 20:07:47[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43773 failure: protocol not supported
2020-11-03 20:07:47[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:47[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:47[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43774 failure: protocol not supported
2020-11-03 20:07:47[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43775 failure: protocol not supported
2020-11-03 20:07:47[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:47[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: connect: connection refused
2020-11-03 20:07:48[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:48[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43777 failure: protocol not supported
2020-11-03 20:07:48[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:48[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43778 failure: protocol not supported
2020-11-03 20:07:48[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:48[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43779 failure: protocol not supported
2020-11-03 20:07:51[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43786 failure: protocol not supported
2020-11-03 20:07:52[info] [TCP] <IP_ADDRESS>:43786 --> avatars1.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:52[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43790 failure: protocol not supported
2020-11-03 20:07:52[info] [TCP] <IP_ADDRESS>:43790 --> avatars1.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:53[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:53[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43794 failure: protocol not supported
2020-11-03 20:07:53[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:53[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:54[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43796 failure: protocol not supported
2020-11-03 20:07:54[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43797 failure: protocol not supported
2020-11-03 20:07:54[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43798 failure: protocol not supported
2020-11-03 20:07:54[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43799 failure: protocol not supported
2020-11-03 20:07:54[info] [TCP] <IP_ADDRESS>:43796 --> <IP_ADDRESS> match RuleSet(Netflix) using Proxy[jp02]
2020-11-03 20:07:54[info] [TCP] <IP_ADDRESS>:43797 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:54[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43800 failure: protocol not supported
2020-11-03 20:07:54[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43801 failure: protocol not supported
2020-11-03 20:07:55[info] [TCP] <IP_ADDRESS>:43800 --> <IP_ADDRESS> match RuleSet(Netflix) using Proxy[jp02]
2020-11-03 20:07:55[info] [TCP] <IP_ADDRESS>:43801 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:56[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43806 failure: protocol not supported
2020-11-03 20:07:56[info] [TCP] <IP_ADDRESS>:43806 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:07:56[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43808 failure: protocol not supported
2020-11-03 20:07:56[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43809 failure: protocol not supported
2020-11-03 20:07:56[info] [TCP] <IP_ADDRESS>:43809 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:07:56[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43810 failure: protocol not supported
2020-11-03 20:07:56[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43811 failure: protocol not supported
2020-11-03 20:07:56[info] [TCP] <IP_ADDRESS>:43811 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:07:57[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43812 failure: protocol not supported
2020-11-03 20:07:57[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43814 failure: protocol not supported
2020-11-03 20:07:57[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43815 failure: protocol not supported
2020-11-03 20:07:57[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43816 failure: protocol not supported
2020-11-03 20:07:57[info] [TCP] <IP_ADDRESS>:43814 --> avatars1.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:57[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43817 failure: protocol not supported
2020-11-03 20:07:57[info] [TCP] <IP_ADDRESS>:43810 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:07:57[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43818 failure: protocol not supported
2020-11-03 20:07:57[info] [TCP] <IP_ADDRESS>:43818 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:07:57[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43819 failure: protocol not supported
2020-11-03 20:07:58[info] [TCP] <IP_ADDRESS>:43816 --> avatars3.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:58[info] [TCP] <IP_ADDRESS>:43812 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:07:58[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43821 failure: protocol not supported
2020-11-03 20:07:58[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43822 failure: protocol not supported
2020-11-03 20:07:58[info] [TCP] <IP_ADDRESS>:43817 --> avatars3.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:58[info] [TCP] <IP_ADDRESS>:43822 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:07:58[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:58[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43823 failure: protocol not supported
2020-11-03 20:07:58[info] [TCP] <IP_ADDRESS>:43823 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:07:58[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43824 failure: protocol not supported
2020-11-03 20:07:58[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43825 failure: protocol not supported
2020-11-03 20:07:58[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43826 failure: protocol not supported
2020-11-03 20:07:58[info] [TCP] <IP_ADDRESS>:43821 --> avatars3.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:58[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43827 failure: protocol not supported
2020-11-03 20:07:58[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43828 failure: protocol not supported
2020-11-03 20:07:58[info] [TCP] <IP_ADDRESS>:43825 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:58[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43829 failure: protocol not supported
2020-11-03 20:07:59[info] [TCP] <IP_ADDRESS>:43819 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:07:59[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43830 failure: protocol not supported
2020-11-03 20:07:59[info] [TCP] <IP_ADDRESS>:43827 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:59[info] [TCP] <IP_ADDRESS>:43828 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:59[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:59[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43832 failure: protocol not supported
2020-11-03 20:07:59[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43833 failure: protocol not supported
2020-11-03 20:07:59[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43834 failure: protocol not supported
2020-11-03 20:07:59[info] [TCP] <IP_ADDRESS>:43829 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:59[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:07:59[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43835 failure: protocol not supported
2020-11-03 20:07:59[info] [TCP] <IP_ADDRESS>:43834 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:59[info] [TCP] <IP_ADDRESS>:43833 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:07:59[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43836 failure: protocol not supported
2020-11-03 20:07:59[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43837 failure: protocol not supported
2020-11-03 20:08:00[info] [TCP] <IP_ADDRESS>:43830 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:08:00[info] [TCP] <IP_ADDRESS>:43837 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:00[info] [TCP] <IP_ADDRESS>:43836 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:00[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43841 failure: protocol not supported
2020-11-03 20:08:00[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43842 failure: protocol not supported
2020-11-03 20:08:00[info] [TCP] <IP_ADDRESS>:43841 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:00[info] [TCP] <IP_ADDRESS>:43842 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:01[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43843 failure: protocol not supported
2020-11-03 20:08:01[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43844 failure: protocol not supported
2020-11-03 20:08:01[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43846 failure: protocol not supported
2020-11-03 20:08:01[info] [TCP] <IP_ADDRESS>:43846 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:08:01[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43847 failure: protocol not supported
2020-11-03 20:08:01[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:08:01[info] [TCP] <IP_ADDRESS>:43843 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:01[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43848 failure: protocol not supported
2020-11-03 20:08:01[info] [TCP] <IP_ADDRESS>:43844 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:01[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43849 failure: protocol not supported
2020-11-03 20:08:01[info] [TCP] <IP_ADDRESS>:43826 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:08:01[info] [TCP] <IP_ADDRESS>:43847 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:01[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43850 failure: protocol not supported
2020-11-03 20:08:01[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43851 failure: protocol not supported
2020-11-03 20:08:01[info] [TCP] <IP_ADDRESS>:43851 --> <IP_ADDRESS> match Match() using DIRECT
2020-11-03 20:08:01[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43852 failure: protocol not supported
2020-11-03 20:08:01[info] [TCP] <IP_ADDRESS>:43849 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:02[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43853 failure: protocol not supported
2020-11-03 20:08:02[info] [TCP] <IP_ADDRESS>:43850 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:02[info] [TCP] <IP_ADDRESS>:43852 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:02[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43855 failure: protocol not supported
2020-11-03 20:08:02[info] [TCP] <IP_ADDRESS>:43853 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:02[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:08:02[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43856 failure: protocol not supported
2020-11-03 20:08:02[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43857 failure: protocol not supported
2020-11-03 20:08:02[info] [TCP] <IP_ADDRESS>:43855 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:02[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43858 failure: protocol not supported
2020-11-03 20:08:03[info] [TCP] <IP_ADDRESS>:43857 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:03[info] [TCP] <IP_ADDRESS>:43858 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:03[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:08:03[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43862 failure: protocol not supported
2020-11-03 20:08:03[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43863 failure: protocol not supported
2020-11-03 20:08:03[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43864 failure: protocol not supported
2020-11-03 20:08:03[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43865 failure: protocol not supported
2020-11-03 20:08:03[info] [TCP] <IP_ADDRESS>:43863 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:03[info] [TCP] <IP_ADDRESS>:43865 --> avatars0.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:03[info] [TCP] <IP_ADDRESS>:43864 --> avatars2.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:03[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43866 failure: protocol not supported
2020-11-03 20:08:04[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43867 failure: protocol not supported
2020-11-03 20:08:04[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43868 failure: protocol not supported
2020-11-03 20:08:04[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43870 failure: protocol not supported
2020-11-03 20:08:04[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43871 failure: protocol not supported
2020-11-03 20:08:04[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:08:04[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43872 failure: protocol not supported
2020-11-03 20:08:04[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout
2020-11-03 20:08:04[info] [TCP] <IP_ADDRESS>:43868 --> avatars0.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:04[info] [TCP] <IP_ADDRESS>:43867 --> avatars0.githubusercontent.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:04[info] [TCP] <IP_ADDRESS>:43866 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:04[info] [TCP] <IP_ADDRESS>:43871 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:04[info] [TCP] <IP_ADDRESS>:43870 --> <IP_ADDRESS> match RuleSet(Netflix) using Proxy[jp02]
2020-11-03 20:08:04[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43873 failure: protocol not supported
2020-11-03 20:08:04[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43874 failure: protocol not supported
2020-11-03 20:08:04[debug] [Process] Resolve process of tcp:<IP_ADDRESS>:43875 failure: protocol not supported
2020-11-03 20:08:05[info] [TCP] <IP_ADDRESS>:43874 --> github.com match RuleSet(PROXY) using Proxy[jp02]
2020-11-03 20:08:05[info] [TCP] <IP_ADDRESS>:43875 --> <IP_ADDRESS> match RuleSet(Netflix) using Proxy[jp02]
2020-11-03 20:08:06[warning] dial DIRECT error: dial tcp4 <IP_ADDRESS>:443: i/o timeout

服务到期了。。。麻烦您了。。


has_aux optional parameter for jvp, jacfwd and jacrev

I am relying on the parameter has_aux to avoid recalculating the same function twice however it is not available for the function jvp, jacfwd, jacrev. Is there a technical reason for this that I would not be aware of ? If not I could look into making a pull request.

Hi, did you manage to solve your problem? I'm curious cause I have the same issue. Thanks :)


Removed duplicate copies of extensions.

I noticed that there are duplicate copies of two extensions (decisiontree.zip and variable slider.zip). From a maintenance perspective, it makes more sense to just have one copy of each in the repository.

Hi, and thanks for contributing!
Note: If you are part of Qlik R&D, you can ignore this process (but let us know in a comment below!)
Before we can handle your pull request we need you to sign our contributor license agreement.
This is a one-time thing and enables you to contribute without hassle to any of the qlik-oss repositories in the future.
And it only takes a few minutes! Here are some useful links to get you started:

Sign the CLA
Rationale behind the CLA
Qlik R&D Open Source repository
Official Slack team

Having troubles? Feel free to reach out to us either here or on Slack!