Compilation issue

I cannot currently get the code to "make" successfully.
I have tried : MEX configured to use 'Microsoft Visual C++ 2012' for C++ language compilation and
VisualStudio 2010.
With Visual C++ 2012 I get  for the compilation of the Function baslerGetData.cpp
Error using mex
Creating library baslerGetData.lib and object baslerGetData.exp
baslerGetData.obj : error LNK2019: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::system_category(void)"
(?system_category@system@boost@@YAAEBVerror_category@12@XZ) referenced in function "void __cdecl boost::system::dynamic initializer for 'native_ecat''(void)" (??__Enative_ecat@system@boost@@YAXXZ) baslerGetData.obj : error LNK2019: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::generic_category(void)" (?generic_category@system@boost@@YAAEBVerror_category@12@XZ) referenced in function "void __cdecl boost::system::dynamic initializer for 'errno_ecat''(void)"
(??__Eerrno_ecat@system@boost@@YAXXZ)
baslerGetData.obj : error LNK2019: unresolved external symbol "void __cdecl boost::filesystem::path_traits::convert(wchar_t const *,wchar_t const *,class
std::basic_string<char,struct std::char_traits,class std::allocator > &,class std::codecvt<wchar_t,char,int> const &)"
(?convert@path_traits@filesystem@boost@@YAXPEB_W0AEAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEBV?$codecvt@_WDH@5@@Z) referenced in function
"void __cdecl boost::filesystem::path_traits::convert(wchar_t const *,wchar_t const *,class std::basic_string<char,struct std::char_traits,class
std::allocator > &)" (?convert@path_traits@filesystem@boost@@YAXPEB_W0AEAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)
baslerGetData.obj : error LNK2019: unresolved external symbol "public: static class std::codecvt<wchar_t,char,int> const & __cdecl
boost::filesystem::path::codecvt(void)" (?codecvt@path@filesystem@boost@@SAAEBV?$codecvt@_WDH@std@@XZ) referenced in function "void __cdecl
boost::filesystem::path_traits::convert(wchar_t const *,wchar_t const *,class std::basic_string<char,struct std::char_traits,class std::allocator > &)"
(?convert@path_traits@filesystem@boost@@YAXPEB_W0AEAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)
baslerGetData.mexw64 : fatal error LNK1120: 4 unresolved externals
AND With VisualStudio2010 I get:
Error using mex
baslerGetParameter.cpp
C:\projects\Basler\baslerGetParameter.cpp(13) : error C2332: 'enum' : missing tag name
C:\projects\Basler\baslerGetParameter.cpp(13) : error C2236: unexpected 'class' 'ParamType'. Did you forget a ';'?
C:\projects\Basler\baslerGetParameter.cpp(13) : error C3381: 'ParamType' : assembly access specifiers are only available in code compiled with a /clr option
I guess this one is due to C++11 ?
But I dont know how to solve either.
I also have VisualStudio 2015 Community (not professional), but I am  not sure if Matlab mex can run with this.

I have now got VisualStudio2013 installed and have rebuilt the boost libraries to -vc120- .
Unfortunately I get the same error as above.
Any suggestions ?

Hello, @njw500
I don't know whether you have solved the issue.I just met the same promblem last night,almost the same as yours.After several efforts, I finally conquered it.
Well,I want to share my solution with you!
The errors are caused by the boost library which lacks some libraries needed.Personally speaking,it may blame to the compiling process which omits some parameters when building the Boost.(I don't know well about the Boost Library so that I just give the reason with the most probability I guess)
As a result,I choose the pre-compiled Boost Library.Since you are using VS 2013 PRO,you can go to sourceforge to download the msvs-12 version.
Then,follow Lansbergen's tutorial BaslerCamDriver_Installation_Tutorial_Windows_7.
Pay great attention to Step 5 to change the library folder.
Wish you can deal with it !
P.S.
Environment:
OS: Windows 8.1 x64
IDE:VS2013 PRO
MATLAB:2015b
BOOST:1.60-msvc-12.0


fixes createTypes deprecated warning

fixes Gatsby v4 warning: warn Calling createTypes in the sourceNodes API is deprecated. Please use: createSchemaCustomization.

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


Is it possible to use pip-installed libraries in codon?

Is it possible to install popular libraries such as requests and use them with Codon?

Yes, see https://docs.exaloop.io/codon/interoperability/python for more info. Example:
from python import numpy as np
arr = np.array([1, 2, 3])
print(arr * 2)

Gotcha. That worked!
Thanks!


bug fixes in OKex and KuCoin websockets

Corrected the websocket port of okex according to latest document.
And merge kucoin ticker fix again. Don't know why it was reverted.

@szmcdull, please rebase to resolve conflicts

KuCoin is unchanged. Now I understand it is because the file tree was changed


Make it clear that event hub scalability is limited by MIN(Partitions, ThroughputUnits)

It is not immediately clear how important the partition count is when considering scalability of event hubs, because the documentation does not clearly note that a partition can use at most one throughput unit.

@Plasma : Thanks for your contribution! The author, @ShubhaVijayasarathy, has been notified to review your proposed change.

@Plasma: thank you for your suggestion. Since this has a merge conflict, we request for closure and work on updating the suggested changes in a separate PR.
#please-close


Enable to define a function for error message.

Based on this PR by @apalm in Revalidation.
It makes a lot of sense to enable to pass in a function instead of a string, in case the input value is needed to display a useful error message.
The specific change would require to check if errorMsg is a function and if so apply the function with the value.
https://github.com/25th-floor/spected/blob/master/src/index.js#L36

This is solved now via #2


[bug, priority high] Updating workflow files should use stricter rules

See https://github.com/ethereum/EIPs/pull/4859
Multiple editors should be required to add/remove editors or manage other parts of the EIP Bot.
Currently, any EIP editor can remove all other EIP editors and/or add any user as an editor - this appears to be a pretty serious security flaw.

Question: how does the bot could avoid editors re-writing any part of the bot's code ?

I actually don't think the bot will automerge changes to /.github/*.  If it does, we should fix that.  I believe I manually merged that commit, not the bot.  I am able to do that because I'm an admin of this repository, and there is essentially nothing the bot can do about a rogue admin.

Ok, thanks. Could we close this issue ?

It really looks like the bot was about to auto-merge it (but then you enabled auto-merge first): https://github.com/ethereum/EIPs/pull/4859#issuecomment-1054459875

Who merged it ? bot or editor ?

Enabling auto-merge I believe happens automatically, but it still needs other checks to pass before it will auto-merge?  I think one of the other checks would have failed?

Nope. The auto merge action is usually skipped. This is what it looked like before the approval:

After the approval:

Clearly, the EIP bot passed all checks, and so the auto merge action wasn't skipped.
ethereum/EIPs#5073 will give us all the information we need, once an editor approves it.

Here's another screenshot from the before/after logs:

let me know if this is the consensus so I can propose the coded rule.

I'd say that for now, it should be manually merged and always fail.


Issue auto generate id int (websql)

Hi
I am having a problem after entering 10 records, the next record is not entered and 10 is updated with data.
I think problem is in using the sort () function in the connect method, it is sorting pks alphabetically, the system needs to be numerically.

In the ECMAscript specification (the normative reference for the generic Javascript), ECMA-262, 3rd ed., section <IP_ADDRESS>, the default sort order is lexicographical, although they don't come out and say it, instead giving the steps for a conceptual sort function that calls the given compare function if necessary, otherwise comparing the arguments when converted to strings:

_WebSQLStore.prototype.connect = function (complete) {
        var _this = this;
        this._db = window.openDatabase(this._id, "1.0", this._id, this._size || utilities_1.isAndroid ? 5000000 : 1);
        utilities_1.fastALL(Object.keys(this._pkKey), function (table, i, nextKey) {
            _this._sql(true, "CREATE TABLE IF NOT EXISTS " + table + " (id BLOB PRIMARY KEY UNIQUE, data TEXT)", [], function () {
                _this._sql(false, "SELECT id FROM " + table, [], function (result) {
                    var idx = [];
                    for (var i_1 = 0; i_1 < result.rows.length; i_1++) {
                        idx.push(result.rows.item(i_1).id);
                    }
                    // SQLite doesn't sort primary keys, but the system depends on sorted primary keys
                    idx = idx.sort();
                    _this._dbIndex[table].set(idx);
                    nextKey();
                });
            });
        }).then(complete);
    };

The solution is to pass a custom function in sort ()
idx = idx.sort(function(a,b){return a - b});

I saw that it has already been resolved in the last update.
You can close this issue.
Thank you


feat(debugger): highlight current src code loc

Description
Problem
Part of #3015. Highlights the current source code location during a debugging session, by dimming the rest of it.
Summary
I decided to use the owo-colors crate because it's already in use in the dependency tree.
PR Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I'll limit the amount of lines displayed so we can keep this PR self-contained


ORA-01034: ORACLE not available with 19.3.0-ee

Hello I encountered the above error when I tried to run any query commands on sqlplus.
Also noticed that when I try login to Enterprise Manager with the password I created it won't let me while the same password works on sqlplus.
Any suggestions would be appreciated.
Thank you and looking forward to hearing soon.
Cheers
Environment:
Oracle Database 19c EE
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.3 LTS
Release:	18.04
Codename:	bionic
Steps to reproduce:
docker run -d -it --rm --name 19c -p 1521:1521 -p 5500:5500 -e ORACLE_PWD=someboguspassworcd -v /home/oracle/oradata19:/opt/oracle/oradata oracle/database:19.3.0-ee

docker exec -ti 19c /bin/bash

export ORACLE_SID=ORCLCDB1

/opt/oracle/product/19c/dbhome_1/bin/sqlplus sys as sysdba

SQL> select * from v$database;

ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

Log output:
docker logs -f 19c
ORACLE PASSWORD FOR SYS, SYSTEM AND PDBADMIN: someboguspassworcd

LSNRCTL for Linux: Version <IP_ADDRESS>.0 - Production on 12-OCT-2019 14:39:41

Copyright (c) 1991, 2019, Oracle.  All rights reserved.

Starting /opt/oracle/product/19c/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
System parameter file is /opt/oracle/product/19c/dbhome_1/network/admin/listener.ora
Log messages written to /opt/oracle/diag/tnslsnr/ca71db62fe1c/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
Start Date                12-OCT-2019 14:39:41
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /opt/oracle/product/19c/dbhome_1/network/admin/listener.ora
Listener Log File         /opt/oracle/diag/tnslsnr/ca71db62fe1c/listener/alert/log.xml
Listening Endpoints Summary...
   For details check the logfiles at:
 /opt/oracle/cfgtoollogs/dbca/ORCLCDB.
Database Information:
Global Database Name:ORCLCDB
System Identifier(SID):ORCLCDB
Look at the log file "/opt/oracle/cfgtoollogs/dbca/ORCLCDB/ORCLCDB.log" for further details.

SQL*Plus: Release <IP_ADDRESS>.0 - Production on Sat Oct 12 14:53:06 2019
Version <IP_ADDRESS>.0

Copyright (c) 1982, 2019, Oracle.  All rights reserved.

Connected to:
Oracle Database 19c Enterprise Edition Release <IP_ADDRESS>.0 - Production
Version <IP_ADDRESS>.0

SQL>
System altered.

SQL>
System altered.

SQL>
Pluggable database altered.

SQL>
PL/SQL procedure successfully completed.

SQL> Disconnected from Oracle Database 19c Enterprise Edition Release <IP_ADDRESS>.0 - Production
Version <IP_ADDRESS>.0
The Oracle base remains unchanged with value /opt/oracle
#########################
DATABASE IS READY TO USE!
#########################
The following output is now a tail of the alert.log:
ORCLPDB1(3):ALTER DATABASE DEFAULT TABLESPACE "USERS"
ORCLPDB1(3):Completed: ALTER DATABASE DEFAULT TABLESPACE "USERS"
2019-10-12T14:53:06.934146+00:00
ALTER SYSTEM SET control_files='/opt/oracle/oradata/ORCLCDB/control01.ctl' SCOPE=SPFILE;
2019-10-12T14:53:06.953288+00:00
ALTER SYSTEM SET local_listener='' SCOPE=BOTH;
   ALTER PLUGGABLE DATABASE ORCLPDB1 SAVE STATE
Completed:    ALTER PLUGGABLE DATABASE ORCLPDB1 SAVE STATE

XDB initialized.
2019-10-12T15:02:53.084511+00:00
ORCLPDB1(3):Resize operation completed for file# 10, old size 327680K, new size 337920K
2019-10-12T16:03:06.210022+00:00
Resize operation completed for file# 3, old size 522240K, new size 532480K
2019-10-12T17:23:11.324421+00:00

XDB initialized.

XDB initialized.
2019-10-12T17:26:48.301734+00:00

XDB initialized.

XDB initialized.
2019-10-12T17:26:49.360789+00:00

XDB initialized.
2019-10-12T17:29:00.597675+00:00

XDB initialized.
2019-10-12T17:29:01.745478+00:00

XDB initialized.
2019-10-12T17:41:08.010072+00:00

XDB initialized.
2019-10-12T18:03:31.806511+00:00
Resize operation completed for file# 3, old size 532480K, new size 542720K
2019-10-12T19:15:25.355706+00:00

XDB initialized.

XDB initialized.
2019-10-12T19:16:48.493018+00:00

XDB initialized.
2019-10-12T19:16:51.389092+00:00

XDB initialized.
2019-10-12T19:24:57.375210+00:00
ORCLPDB1(3):ALTER PLUGGABLE DATABASE  OPEN
ORCLPDB1(3):ORA-1031 signalled during: ALTER PLUGGABLE DATABASE  OPEN ...
2019-10-12T20:53:15.808541+00:00
Resize operation completed for file# 201, old size 32768K, new size 33792K
Resize operation completed for file# 201, old size 33792K, new size 34816K
Resize operation completed for file# 201, old size 34816K, new size 35840K
Resize operation completed for file# 201, old size 35840K, new size 36864K
Resize operation completed for file# 201, old size 36864K, new size 37888K
Resize operation completed for file# 201, old size 37888K, new size 38912K
Resize operation completed for file# 201, old size 38912K, new size 39936K
Resize operation completed for file# 201, old size 39936K, new size 40960K
Resize operation completed for file# 201, old size 40960K, new size 41984K
Resize operation completed for file# 201, old size 41984K, new size 43008K
Resize operation completed for file# 201, old size 43008K, new size 44032K
Resize operation completed for file# 201, old size 44032K, new size 45056K
Resize operation completed for file# 201, old size 45056K, new size 46080K
Resize operation completed for file# 201, old size 46080K, new size 47104K
Resize operation completed for file# 201, old size 47104K, new size 48128K
Resize operation completed for file# 201, old size 48128K, new size 49152K
Resize operation completed for file# 201, old size 49152K, new size 50176K
Resize operation completed for file# 201, old size 50176K, new size 51200K
Resize operation completed for file# 201, old size 51200K, new size 52224K
Resize operation completed for file# 201, old size 52224K, new size 53248K
Resize operation completed for file# 201, old size 53248K, new size 54272K
Resize operation completed for file# 201, old size 54272K, new size 55296K
Resize operation completed for file# 201, old size 55296K, new size 56320K
Resize operation completed for file# 201, old size 56320K, new size 57344K
Resize operation completed for file# 201, old size 57344K, new size 58368K
Resize operation completed for file# 201, old size 58368K, new size 59392K
Resize operation completed for file# 201, old size 59392K, new size 60416K
Resize operation completed for file# 201, old size 60416K, new size 61440K
Resize operation completed for file# 201, old size 61440K, new size 62464K
Resize operation completed for file# 201, old size 62464K, new size 63488K
Resize operation completed for file# 201, old size 63488K, new size 64512K
Resize operation completed for file# 201, old size 64512K, new size 65536K
Resize operation completed for file# 201, old size 65536K, new size 66560K
Resize operation completed for file# 201, old size 66560K, new size 67584K
Resize operation completed for file# 201, old size 67584K, new size 68608K
Resize operation completed for file# 201, old size 68608K, new size 69632K
2019-10-12T20:53:16.811767+00:00
Resize operation completed for file# 201, old size 69632K, new size 70656K
Resize operation completed for file# 201, old size 70656K, new size 71680K
Resize operation completed for file# 201, old size 71680K, new size 72704K
Resize operation completed for file# 201, old size 72704K, new size 73728K
Resize operation completed for file# 201, old size 73728K, new size 74752K
Resize operation completed for file# 201, old size 74752K, new size 75776K
Resize operation completed for file# 201, old size 75776K, new size 76800K
Resize operation completed for file# 201, old size 76800K, new size 77824K
Resize operation completed for file# 201, old size 77824K, new size 78848K
Resize operation completed for file# 201, old size 78848K, new size 79872K
Resize operation completed for file# 201, old size 79872K, new size 80896K
Resize operation completed for file# 201, old size 80896K, new size 81920K
Resize operation completed for file# 201, old size 81920K, new size 82944K
Resize operation completed for file# 201, old size 82944K, new size 83968K
Resize operation completed for file# 201, old size 83968K, new size 84992K
Resize operation completed for file# 201, old size 84992K, new size 86016K
Resize operation completed for file# 201, old size 86016K, new size 87040K
Resize operation completed for file# 201, old size 87040K, new size 88064K
Resize operation completed for file# 201, old size 88064K, new size 89088K
Resize operation completed for file# 201, old size 89088K, new size 90112K
Resize operation completed for file# 201, old size 90112K, new size 91136K
Resize operation completed for file# 201, old size 91136K, new size 92160K
Resize operation completed for file# 201, old size 92160K, new size 93184K
Resize operation completed for file# 201, old size 93184K, new size 94208K
Resize operation completed for file# 201, old size 94208K, new size 95232K
Resize operation completed for file# 201, old size 95232K, new size 96256K
Resize operation completed for file# 201, old size 96256K, new size 97280K
Resize operation completed for file# 201, old size 97280K, new size 98304K
Resize operation completed for file# 201, old size 98304K, new size 99328K
Resize operation completed for file# 201, old size 99328K, new size 100352K
Resize operation completed for file# 201, old size 100352K, new size 101376K
Resize operation completed for file# 201, old size 101376K, new size 102400K
Resize operation completed for file# 201, old size 102400K, new size 103424K
Resize operation completed for file# 201, old size 103424K, new size 104448K
Resize operation completed for file# 201, old size 104448K, new size 105472K
Resize operation completed for file# 201, old size 105472K, new size 106496K
Resize operation completed for file# 201, old size 106496K, new size 107520K
Resize operation completed for file# 201, old size 107520K, new size 108544K
Resize operation completed for file# 201, old size 108544K, new size 109568K
Resize operation completed for file# 201, old size 109568K, new size 110592K
2019-10-12T20:53:17.815283+00:00
Resize operation completed for file# 201, old size 110592K, new size 111616K
Resize operation completed for file# 201, old size 111616K, new size 112640K
Resize operation completed for file# 201, old size 112640K, new size 113664K
Resize operation completed for file# 201, old size 113664K, new size 114688K
Resize operation completed for file# 201, old size 114688K, new size 115712K
Resize operation completed for file# 201, old size 115712K, new size 116736K
Resize operation completed for file# 201, old size 116736K, new size 117760K
Resize operation completed for file# 201, old size 117760K, new size 118784K
Resize operation completed for file# 201, old size 118784K, new size 119808K
Resize operation completed for file# 201, old size 119808K, new size 120832K
Resize operation completed for file# 201, old size 120832K, new size 121856K
Resize operation completed for file# 201, old size 121856K, new size 122880K
Resize operation completed for file# 201, old size 122880K, new size 123904K
Resize operation completed for file# 201, old size 123904K, new size 124928K
Resize operation completed for file# 201, old size 124928K, new size 125952K
Resize operation completed for file# 201, old size 125952K, new size 126976K
Resize operation completed for file# 201, old size 126976K, new size 128000K
Resize operation completed for file# 201, old size 128000K, new size 129024K
Resize operation completed for file# 201, old size 129024K, new size 130048K
Resize operation completed for file# 201, old size 130048K, new size 131072K
Resize operation completed for file# 201, old size 131072K, new size 132096K
2019-10-12T20:53:44.173561+00:00
ORCLPDB1(3):Resize operation completed for file# 203, old size 36864K, new size 37888K
ORCLPDB1(3):Resize operation completed for file# 203, old size 37888K, new size 38912K
ORCLPDB1(3):Resize operation completed for file# 203, old size 38912K, new size 39936K
ORCLPDB1(3):Resize operation completed for file# 203, old size 39936K, new size 40960K
ORCLPDB1(3):Resize operation completed for file# 203, old size 40960K, new size 41984K
ORCLPDB1(3):Resize operation completed for file# 203, old size 41984K, new size 43008K
ORCLPDB1(3):Resize operation completed for file# 203, old size 43008K, new size 44032K
ORCLPDB1(3):Resize operation completed for file# 203, old size 44032K, new size 45056K
ORCLPDB1(3):Resize operation completed for file# 203, old size 45056K, new size 46080K
ORCLPDB1(3):Resize operation completed for file# 203, old size 46080K, new size 47104K
ORCLPDB1(3):Resize operation completed for file# 203, old size 47104K, new size 48128K
ORCLPDB1(3):Resize operation completed for file# 203, old size 48128K, new size 49152K
ORCLPDB1(3):Resize operation completed for file# 203, old size 49152K, new size 50176K
ORCLPDB1(3):Resize operation completed for file# 203, old size 50176K, new size 51200K
ORCLPDB1(3):Resize operation completed for file# 203, old size 51200K, new size 52224K
ORCLPDB1(3):Resize operation completed for file# 203, old size 52224K, new size 53248K
ORCLPDB1(3):Resize operation completed for file# 203, old size 53248K, new size 54272K
ORCLPDB1(3):Resize operation completed for file# 203, old size 54272K, new size 55296K
ORCLPDB1(3):Resize operation completed for file# 203, old size 55296K, new size 56320K
ORCLPDB1(3):Resize operation completed for file# 203, old size 56320K, new size 57344K
ORCLPDB1(3):Resize operation completed for file# 203, old size 57344K, new size 58368K
ORCLPDB1(3):Resize operation completed for file# 203, old size 58368K, new size 59392K
ORCLPDB1(3):Resize operation completed for file# 203, old size 59392K, new size 60416K
ORCLPDB1(3):Resize operation completed for file# 203, old size 60416K, new size 61440K
ORCLPDB1(3):Resize operation completed for file# 203, old size 61440K, new size 62464K
ORCLPDB1(3):Resize operation completed for file# 203, old size 62464K, new size 63488K
ORCLPDB1(3):Resize operation completed for file# 203, old size 63488K, new size 64512K
ORCLPDB1(3):Resize operation completed for file# 203, old size 64512K, new size 65536K
ORCLPDB1(3):Resize operation completed for file# 203, old size 65536K, new size 66560K
ORCLPDB1(3):Resize operation completed for file# 203, old size 66560K, new size 67584K
ORCLPDB1(3):Resize operation completed for file# 203, old size 67584K, new size 68608K
ORCLPDB1(3):Resize operation completed for file# 203, old size 68608K, new size 69632K
ORCLPDB1(3):Resize operation completed for file# 203, old size 69632K, new size 70656K
ORCLPDB1(3):Resize operation completed for file# 203, old size 70656K, new size 71680K
ORCLPDB1(3):Resize operation completed for file# 203, old size 71680K, new size 72704K
ORCLPDB1(3):Resize operation completed for file# 203, old size 72704K, new size 73728K
ORCLPDB1(3):Resize operation completed for file# 203, old size 73728K, new size 74752K
2019-10-12T20:53:45.176536+00:00
ORCLPDB1(3):Resize operation completed for file# 203, old size 74752K, new size 75776K
ORCLPDB1(3):Resize operation completed for file# 203, old size 75776K, new size 76800K
ORCLPDB1(3):Resize operation completed for file# 203, old size 76800K, new size 77824K
ORCLPDB1(3):Resize operation completed for file# 203, old size 77824K, new size 78848K
ORCLPDB1(3):Resize operation completed for file# 203, old size 78848K, new size 79872K
ORCLPDB1(3):Resize operation completed for file# 203, old size 79872K, new size 80896K
ORCLPDB1(3):Resize operation completed for file# 203, old size 80896K, new size 81920K
ORCLPDB1(3):Resize operation completed for file# 203, old size 81920K, new size 82944K
ORCLPDB1(3):Resize operation completed for file# 203, old size 82944K, new size 83968K
ORCLPDB1(3):Resize operation completed for file# 203, old size 83968K, new size 84992K
ORCLPDB1(3):Resize operation completed for file# 203, old size 84992K, new size 86016K
ORCLPDB1(3):Resize operation completed for file# 203, old size 86016K, new size 87040K
ORCLPDB1(3):Resize operation completed for file# 203, old size 87040K, new size 88064K
ORCLPDB1(3):Resize operation completed for file# 203, old size 88064K, new size 89088K
ORCLPDB1(3):Resize operation completed for file# 203, old size 89088K, new size 90112K
ORCLPDB1(3):Resize operation completed for file# 203, old size 90112K, new size 91136K
ORCLPDB1(3):Resize operation completed for file# 203, old size 91136K, new size 92160K
ORCLPDB1(3):Resize operation completed for file# 203, old size 92160K, new size 93184K
ORCLPDB1(3):Resize operation completed for file# 203, old size 93184K, new size 94208K
ORCLPDB1(3):Resize operation completed for file# 203, old size 94208K, new size 95232K
ORCLPDB1(3):Resize operation completed for file# 203, old size 95232K, new size 96256K
ORCLPDB1(3):Resize operation completed for file# 203, old size 96256K, new size 97280K
ORCLPDB1(3):Resize operation completed for file# 203, old size 97280K, new size 98304K
ORCLPDB1(3):Resize operation completed for file# 203, old size 98304K, new size 99328K
ORCLPDB1(3):Resize operation completed for file# 203, old size 99328K, new size 100352K
ORCLPDB1(3):Resize operation completed for file# 203, old size 100352K, new size 101376K
ORCLPDB1(3):Resize operation completed for file# 203, old size 101376K, new size 102400K
ORCLPDB1(3):Resize operation completed for file# 203, old size 102400K, new size 103424K
ORCLPDB1(3):Resize operation completed for file# 203, old size 103424K, new size 104448K
ORCLPDB1(3):Resize operation completed for file# 203, old size 104448K, new size 105472K
ORCLPDB1(3):Resize operation completed for file# 203, old size 105472K, new size 106496K
ORCLPDB1(3):Resize operation completed for file# 203, old size 106496K, new size 107520K
ORCLPDB1(3):Resize operation completed for file# 203, old size 107520K, new size 108544K
ORCLPDB1(3):Resize operation completed for file# 203, old size 108544K, new size 109568K
ORCLPDB1(3):Resize operation completed for file# 203, old size 109568K, new size 110592K
ORCLPDB1(3):Resize operation completed for file# 203, old size 110592K, new size 111616K
ORCLPDB1(3):Resize operation completed for file# 203, old size 111616K, new size 112640K
ORCLPDB1(3):Resize operation completed for file# 203, old size 112640K, new size 113664K
ORCLPDB1(3):Resize operation completed for file# 203, old size 113664K, new size 114688K
2019-10-12T20:53:46.171156+00:00
ORCLPDB1(3):Resize operation completed for file# 203, old size 114688K, new size 115712K
ORCLPDB1(3):Resize operation completed for file# 203, old size 115712K, new size 116736K
ORCLPDB1(3):Resize operation completed for file# 203, old size 116736K, new size 117760K
ORCLPDB1(3):Resize operation completed for file# 203, old size 117760K, new size 118784K
ORCLPDB1(3):Resize operation completed for file# 203, old size 118784K, new size 119808K
ORCLPDB1(3):Resize operation completed for file# 203, old size 119808K, new size 120832K
ORCLPDB1(3):Resize operation completed for file# 203, old size 120832K, new size 121856K
ORCLPDB1(3):Resize operation completed for file# 203, old size 121856K, new size 122880K
ORCLPDB1(3):Resize operation completed for file# 203, old size 122880K, new size 123904K
ORCLPDB1(3):Resize operation completed for file# 203, old size 123904K, new size 124928K
ORCLPDB1(3):Resize operation completed for file# 203, old size 124928K, new size 125952K
ORCLPDB1(3):Resize operation completed for file# 203, old size 125952K, new size 126976K
ORCLPDB1(3):Resize operation completed for file# 203, old size 126976K, new size 128000K
ORCLPDB1(3):Resize operation completed for file# 203, old size 128000K, new size 129024K
ORCLPDB1(3):Resize operation completed for file# 203, old size 129024K, new size 130048K
ORCLPDB1(3):Resize operation completed for file# 203, old size 130048K, new size 131072K
2019-10-12T21:04:09.819628+00:00
Resize operation completed for file# 3, old size 542720K, new size 552960K
2019-10-13T01:00:11.992942+00:00
TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P221 (43750) VALUES LESS THAN (TO_DATE(' 2019-10-14 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P224 (43750) VALUES LESS THAN (TO_DATE(' 2019-10-14 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-13T01:04:59.740937+00:00
Resize operation completed for file# 3, old size 552960K, new size 563200K
2019-10-13T02:01:38.051853+00:00
TABLE SYS.WRP$_REPORTS: ADDED INTERVAL PARTITION SYS_P241 (3573) VALUES LESS THAN (TO_DATE(' 2019-10-14 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_DETAILS: ADDED INTERVAL PARTITION SYS_P242 (3573) VALUES LESS THAN (TO_DATE(' 2019-10-14 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_TIME_BANDS: ADDED INTERVAL PARTITION SYS_P245 (3572) VALUES LESS THAN (TO_DATE(' 2019-10-13 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-13T06:00:00.057545+00:00
Setting Resource Manager plan SCHEDULER[0x4D58]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager CDB plan DEFAULT_MAINTENANCE_PLAN via parameter
2019-10-13T06:00:02.531162+00:00
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
2019-10-13T06:00:27.516142+00:00
Resize operation completed for file# 1, old size 911360K, new size 921600K
2019-10-13T06:01:20.943138+00:00
Resize operation completed for file# 1, old size 921600K, new size 931840K
2019-10-13T06:01:37.916189+00:00
Thread 1 advanced to log sequence 8 (LGWR switch)
  Current log# 2 seq# 8 mem# 0: /opt/oracle/oradata/ORCLCDB/redo02.log
2019-10-13T06:06:03.881440+00:00
Resize operation completed for file# 3, old size 563200K, new size 573440K
2019-10-13T09:06:43.163022+00:00
Resize operation completed for file# 3, old size 573440K, new size 583680K
2019-10-13T13:00:00.100262+00:00
ORCLPDB1(3):Setting Resource Manager plan SCHEDULER[0x4D55]:DEFAULT_MAINTENANCE_PLAN via scheduler window
ORCLPDB1(3):Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
2019-10-13T13:00:14.014808+00:00
ORCLPDB1(3):TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P241 (43750) VALUES LESS THAN (TO_DATE(' 2019-10-14 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
ORCLPDB1(3):TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P244 (43750) VALUES LESS THAN (TO_DATE(' 2019-10-14 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-13T13:01:04.719161+00:00
Thread 1 cannot allocate new log, sequence 9
Private strand flush not complete
  Current log# 2 seq# 8 mem# 0: /opt/oracle/oradata/ORCLCDB/redo02.log
2019-10-13T13:01:07.742018+00:00
Thread 1 advanced to log sequence 9 (LGWR switch)
  Current log# 3 seq# 9 mem# 0: /opt/oracle/oradata/ORCLCDB/redo03.log
2019-10-13T13:01:24.751649+00:00
ORCLPDB1(3):Resize operation completed for file# 9, old size 276480K, new size 286720K
2019-10-13T13:07:35.468413+00:00
Resize operation completed for file# 3, old size 583680K, new size 604160K
2019-10-13T13:07:35.468411+00:00
ORCLPDB1(3):Resize operation completed for file# 10, old size 337920K, new size 348160K
2019-10-13T16:08:13.914923+00:00
Resize operation completed for file# 3, old size 604160K, new size 614400K
2019-10-13T21:19:20.938384+00:00
Resize operation completed for file# 3, old size 614400K, new size 624640K
2019-10-14T00:01:41.679820+00:00
TABLE SYS.WRP$_REPORTS_TIME_BANDS: ADDED INTERVAL PARTITION SYS_P261 (3573) VALUES LESS THAN (TO_DATE(' 2019-10-14 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-14T01:10:19.555903+00:00
TABLE SYS.WRP$_REPORTS: ADDED INTERVAL PARTITION SYS_P281 (3574) VALUES LESS THAN (TO_DATE(' 2019-10-15 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_DETAILS: ADDED INTERVAL PARTITION SYS_P282 (3574) VALUES LESS THAN (TO_DATE(' 2019-10-15 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-14T01:10:19.732117+00:00
TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P285 (43751) VALUES LESS THAN (TO_DATE(' 2019-10-15 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P288 (43751) VALUES LESS THAN (TO_DATE(' 2019-10-15 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-14T01:10:24.269607+00:00
ORCLPDB1(3):TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P261 (43751) VALUES LESS THAN (TO_DATE(' 2019-10-15 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
ORCLPDB1(3):TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P264 (43751) VALUES LESS THAN (TO_DATE(' 2019-10-15 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-14T01:10:26.269565+00:00
Thread 1 cannot allocate new log, sequence 10
Private strand flush not complete
  Current log# 3 seq# 9 mem# 0: /opt/oracle/oradata/ORCLCDB/redo03.log
2019-10-14T01:10:29.289789+00:00
Thread 1 advanced to log sequence 10 (LGWR switch)
  Current log# 1 seq# 10 mem# 0: /opt/oracle/oradata/ORCLCDB/redo01.log
2019-10-14T01:20:13.420594+00:00
Resize operation completed for file# 3, old size 624640K, new size 634880K
2019-10-14T02:00:00.160493+00:00
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager CDB plan via parameter
2019-10-14T06:21:18.295289+00:00
Resize operation completed for file# 3, old size 634880K, new size 645120K
2019-10-14T09:00:00.141553+00:00
ORCLPDB1(3):Closing scheduler window
ORCLPDB1(3):Closing Resource Manager plan via scheduler window
ORCLPDB1(3):Clearing Resource Manager plan via parameter
2019-10-14T15:03:09.657825+00:00
Resize operation completed for file# 3, old size 645120K, new size 655360K
2019-10-14T22:00:00.171122+00:00
Setting Resource Manager plan SCHEDULER[0x4D52]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager CDB plan DEFAULT_MAINTENANCE_PLAN via parameter
2019-10-14T22:00:00.969041+00:00
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
2019-10-14T22:00:02.068347+00:00
End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
2019-10-14T22:04:40.423874+00:00
Resize operation completed for file# 3, old size 655360K, new size 665600K
2019-10-14T22:41:47.353230+00:00
Warning: VKTM detected a forward time drift.
Please see the VKTM trace file for more details:
/opt/oracle/diag/rdbms/orclcdb/ORCLCDB/trace/ORCLCDB_vktm_2710.trc
2019-10-15T00:05:07.036806+00:00
Resize operation completed for file# 3, old size 665600K, new size 675840K
2019-10-15T02:00:00.058972+00:00
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager CDB plan via parameter
2019-10-15T05:00:00.179067+00:00
ORCLPDB1(3):Setting Resource Manager plan SCHEDULER[0x4D4F]:DEFAULT_MAINTENANCE_PLAN via scheduler window
ORCLPDB1(3):Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
2019-10-15T05:00:07.737013+00:00
ORCLPDB1(3):TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P281 (43752) VALUES LESS THAN (TO_DATE(' 2019-10-16 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
ORCLPDB1(3):TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P284 (43752) VALUES LESS THAN (TO_DATE(' 2019-10-16 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-15T05:00:15.293910+00:00
Thread 1 advanced to log sequence 11 (LGWR switch)
  Current log# 2 seq# 11 mem# 0: /opt/oracle/oradata/ORCLCDB/redo02.log
2019-10-15T05:00:38.500623+00:00
TABLE SYS.WRP$_REPORTS: ADDED INTERVAL PARTITION SYS_P301 (3575) VALUES LESS THAN (TO_DATE(' 2019-10-16 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_DETAILS: ADDED INTERVAL PARTITION SYS_P302 (3575) VALUES LESS THAN (TO_DATE(' 2019-10-16 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_TIME_BANDS: ADDED INTERVAL PARTITION SYS_P305 (3574) VALUES LESS THAN (TO_DATE(' 2019-10-15 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-15T06:06:25.374312+00:00
Resize operation completed for file# 3, old size 675840K, new size 686080K
2019-10-15T09:00:00.051388+00:00
ORCLPDB1(3):Closing scheduler window
ORCLPDB1(3):Closing Resource Manager plan via scheduler window
ORCLPDB1(3):Clearing Resource Manager plan via parameter
2019-10-15T11:07:30.755439+00:00
Resize operation completed for file# 3, old size 686080K, new size 696320K
2019-10-15T19:09:17.789483+00:00
Resize operation completed for file# 3, old size 696320K, new size 706560K
2019-10-15T22:00:00.046030+00:00
Setting Resource Manager plan SCHEDULER[0x4D53]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager CDB plan DEFAULT_MAINTENANCE_PLAN via parameter
2019-10-15T22:00:01.902882+00:00
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
2019-10-15T22:00:03.291310+00:00
End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
2019-10-15T22:00:07.743904+00:00
TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P321 (43752) VALUES LESS THAN (TO_DATE(' 2019-10-16 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P324 (43752) VALUES LESS THAN (TO_DATE(' 2019-10-16 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-15T22:30:01.314395+00:00
Resize operation completed for file# 3, old size 706560K, new size 716800K
2019-10-16T00:19:35.586808+00:00

***********************************************************************

Fatal NI connect error 12170.

  VERSION INFORMATION:
	TNS for Linux: Version <IP_ADDRESS>.0 - Production
	Oracle Bequeath NT Protocol Adapter for Linux: Version <IP_ADDRESS>.0 - Production
	TCP/IP NT Protocol Adapter for Linux: Version <IP_ADDRESS>.0 - Production
  Version <IP_ADDRESS>.0
  Time: 16-OCT-2019 00:19:35
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12535

TNS-12535: TNS:operation timed out
    ns secondary err code: 12606
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
  Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=46306))
2019-10-16T00:19:35.589661+00:00
WARNING: inbound connection timed out (ORA-3136)
2019-10-16T02:00:00.058450+00:00
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager CDB plan via parameter
2019-10-16T02:01:21.739381+00:00
TABLE SYS.WRP$_REPORTS: ADDED INTERVAL PARTITION SYS_P341 (3576) VALUES LESS THAN (TO_DATE(' 2019-10-17 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_DETAILS: ADDED INTERVAL PARTITION SYS_P342 (3576) VALUES LESS THAN (TO_DATE(' 2019-10-17 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_TIME_BANDS: ADDED INTERVAL PARTITION SYS_P345 (3575) VALUES LESS THAN (TO_DATE(' 2019-10-16 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-16T04:01:13.307568+00:00
Resize operation completed for file# 3, old size 716800K, new size 727040K
2019-10-16T05:00:00.038818+00:00
ORCLPDB1(3):Setting Resource Manager plan SCHEDULER[0x4D50]:DEFAULT_MAINTENANCE_PLAN via scheduler window
ORCLPDB1(3):Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
2019-10-16T05:00:06.951848+00:00
ORCLPDB1(3):TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P301 (43753) VALUES LESS THAN (TO_DATE(' 2019-10-17 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
ORCLPDB1(3):TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P304 (43753) VALUES LESS THAN (TO_DATE(' 2019-10-17 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-16T07:00:24.445576+00:00
Thread 1 advanced to log sequence 12 (LGWR switch)
  Current log# 3 seq# 12 mem# 0: /opt/oracle/oradata/ORCLCDB/redo03.log
2019-10-16T09:00:00.042338+00:00
ORCLPDB1(3):Closing scheduler window
ORCLPDB1(3):Closing Resource Manager plan via scheduler window
ORCLPDB1(3):Clearing Resource Manager plan via parameter
2019-10-16T10:02:32.676070+00:00
Resize operation completed for file# 3, old size 727040K, new size 737280K
2019-10-16T17:04:05.212663+00:00
Resize operation completed for file# 3, old size 737280K, new size 747520K
2019-10-16T22:00:00.179018+00:00
Setting Resource Manager plan SCHEDULER[0x4D54]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager CDB plan DEFAULT_MAINTENANCE_PLAN via parameter
2019-10-16T22:00:01.095609+00:00
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
2019-10-16T22:00:02.771769+00:00
End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
2019-10-16T22:00:06.175989+00:00
TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P361 (43753) VALUES LESS THAN (TO_DATE(' 2019-10-17 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P364 (43753) VALUES LESS THAN (TO_DATE(' 2019-10-17 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-16T22:25:16.902481+00:00
Resize operation completed for file# 3, old size 747520K, new size 757760K
2019-10-17T00:01:35.604096+00:00
TABLE SYS.WRP$_REPORTS_TIME_BANDS: ADDED INTERVAL PARTITION SYS_P381 (3576) VALUES LESS THAN (TO_DATE(' 2019-10-17 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-17T02:00:00.026434+00:00
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager CDB plan via parameter
2019-10-17T03:01:49.822253+00:00
TABLE SYS.WRP$_REPORTS: ADDED INTERVAL PARTITION SYS_P401 (3577) VALUES LESS THAN (TO_DATE(' 2019-10-18 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_DETAILS: ADDED INTERVAL PARTITION SYS_P402 (3577) VALUES LESS THAN (TO_DATE(' 2019-10-18 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-17T03:06:19.355493+00:00
Resize operation completed for file# 3, old size 757760K, new size 768000K
2019-10-17T04:54:28.030481+00:00
Resize operation completed for file# 1, old size 931840K, new size 942080K
2019-10-17T05:00:00.018856+00:00
ORCLPDB1(3):Setting Resource Manager plan SCHEDULER[0x4D51]:DEFAULT_MAINTENANCE_PLAN via scheduler window
ORCLPDB1(3):Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
2019-10-17T05:00:07.916061+00:00
ORCLPDB1(3):TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P321 (43754) VALUES LESS THAN (TO_DATE(' 2019-10-18 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
ORCLPDB1(3):TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P324 (43754) VALUES LESS THAN (TO_DATE(' 2019-10-18 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-17T05:06:45.249572+00:00
ORCLPDB1(3):Resize operation completed for file# 10, old size 348160K, new size 358400K
2019-10-17T09:00:00.147983+00:00
ORCLPDB1(3):Closing scheduler window
ORCLPDB1(3):Closing Resource Manager plan via scheduler window
ORCLPDB1(3):Clearing Resource Manager plan via parameter
2019-10-17T10:00:43.294132+00:00
Thread 1 advanced to log sequence 13 (LGWR switch)
  Current log# 1 seq# 13 mem# 0: /opt/oracle/oradata/ORCLCDB/redo01.log
2019-10-17T10:07:51.915406+00:00
Resize operation completed for file# 3, old size 768000K, new size 778240K
2019-10-17T14:08:46.690071+00:00
Resize operation completed for file# 3, old size 778240K, new size 788480K
2019-10-17T22:00:00.117181+00:00
Setting Resource Manager plan SCHEDULER[0x4D55]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager CDB plan DEFAULT_MAINTENANCE_PLAN via parameter
2019-10-17T22:00:01.080357+00:00
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
2019-10-17T22:00:02.826599+00:00
End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
2019-10-17T22:00:06.219468+00:00
TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P421 (43754) VALUES LESS THAN (TO_DATE(' 2019-10-18 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P424 (43754) VALUES LESS THAN (TO_DATE(' 2019-10-18 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
2019-10-17T22:00:25.234665+00:00
Resize operation completed for file# 3, old size 788480K, new size 798720K
2019-10-17T22:30:32.819548+00:00
Resize operation completed for file# 3, old size 798720K, new size 808960K

The ORACLE_SID is ORCLCDB and not ORCLCDB1.
If you change export ORACLE_SID=ORCLCDB you should get in just fine.


Add --install option to init

The init command has a new option in v1.21.1.
-i, --install <value>               install a specific Yarn release

I've bumped the version of the package. Let me know if I should revert that.

Thanks!


Independent yafti configs between bluefin-dx and bluefin

We wanna add more developer oriented options for the -dx yafti setup on first boot. Right now bluefin and bluefin-dx share the same yafti.yml file.
We need to split them for each image, and then what we can do is when you're on a -dx image we run yafti twice, once with the stock config, and then when they go through that run it with the -dx config, and in there we can add some kickass developer personas: "AI Tools" which pull in ollama and a bunch of goodies, etc. and so on.

We have different yafti's for bluefin and aurora right now.
I think we can consolidate these two and use sed or something for branding changes at build time. The same method could be used for our -dx config.


AGM map display

Hi ..
I am using AGM Map. While zoom out fully I m getting map as follows,

But I want to show like below,

Please help me. Thank you

Hi,
You should use maxZoom to limit zooming out by the user. In my code I have maxZoom of 18, I think it should do for you too:
this.mapOptions = {
...
maxZoom: 18
}

@kror000 , its not working. I want to control zoom out only. No need to control zoom in

There's nothing I can do. It's how the Google Maps API behaves. Feel free to reopen


Support for referenda without preimage(Inlined call)

Our referendum 77 doesn't show up in the website, likely because it uses the Inline bounded call?
{
  Ongoing: {
    track: 34
    origin: {
      Origins: BigSpender
    }
    proposal: {
      Inline: 0x12030f0044b643bd4c21004896aa6b146417590bd0191a7fe9677e64347e5d6f3d70bca9ded984c2c5c84e
    }
    enactment: {
      After: 100
    }
    submitted: 16,336,895
    submissionDeposit: {
      who: EDVirtoiVjAv8HFZwSGbiBcY6P4kDFba9VKsBS911Aw8evX
      amount: 33,333,333,333
    }
    decisionDeposit: {
      who: EDVirtoiVjAv8HFZwSGbiBcY6P4kDFba9VKsBS911Aw8evX
      amount: 13,333,333,333,200
    }
    deciding: null
    ...
  }
}

Thank you for bringing this issue to our attention. Our team has identified and resolved the problem with the referendum 77 not showing up on the website, which has now been corrected. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to fix the issue. If you have any further questions or concerns, please don't hesitate to reach out.


Progress bar merge_and_unload

Feature request
Merging adapters takes time, although I must admit that I am not sure whether most time is taken by loading the base model or by the merging itself. If a lot of time is taken by the merging itself, it can be useful for users to see a progressbar. Specifically, a tqdm can be added here:
https://github.com/huggingface/peft/blob/9f7492577ff91c51077308f98dade45bf32c268a/src/peft/tuners/lora.py#L433
which should be disable-able with a function argument progressbar: bool = True or similar.
Motivation
Users benefit when a time-consuming process gets a progressbar
Your contribution
If you think this is a good idea, I can add it.

Hi @BramVanroy
indeed that would be great! Feel free to open a PR


Wrong article authors

I found out the autor extraction sometimes extract  Bad authors,for ex.: because at the page attribute authors doesn't mean always that it's the author of the article
It's better has less number of extracted authors Than bad  extracted authors
also dc.creator always mean journalist_??_
VALS = ['author', 'byline', 'dc.creator', 'byl']

139 line

 newspaper/newspaper/extractors.py

This is potentially the case with any html tags - it all depends on what the tags are populated with. Any of the tags could potentially have bad authors.
I would recommend adding some kind of automated validation step after newspaper returns results, possibly using services like dbpedia or wikidata to remove bad results?


creating a notification rule from any to crit should generate the correct flux

looks like it is generating monitor.stateChanges(fromLevel: "unknown", toLevel: "crit")
but it should be monitor.stateChanges(fromLevel: "any", toLevel: "crit")

this may also solve this issue: https://github.com/influxdata/influxdb/issues/14967


Command restriction isn't working

*Reproduction steps:

use a command with adminOnly bool.

Expected behaviour

it should block it but instead allows the command to be run regardless if their snowflake is in data.json

Fixed in #21


Missing cxxabi.h include when compiling on Windows with libc++

The cxxabi.h header is not used on Windows when using the Microsoft C++ runtime. Most people build with the Microsoft STL when building on Windows, but I am using libc++, and I have found that the protection against including cxxabi.h doesn't work in this case:
https://github.com/jeremy-rifkin/cpptrace/blob/d2b940ab07521df8baeff0fbf7aea68d94dffc65/src/utils/exception_type.hpp#L7
and
https://github.com/jeremy-rifkin/cpptrace/blob/d2b940ab07521df8baeff0fbf7aea68d94dffc65/src/utils/exception_type.hpp#L16
My guess is that they are meant to be evaluated as: defined(CPPTRACE_HAS_CXX_EXCEPTION_TYPE) && defined(__GLIBCXX__) || defined(__GLIBCPP__) || defined(_LIBCPP_VERSION
but the preprocessor operator precedence makes it evaluated as: defined(CPPTRACE_HAS_CXX_EXCEPTION_TYPE) && defined(__GLIBCXX__) || defined(__GLIBCPP__) || defined(_LIBCPP_VERSION)
Since I am using libc++, _LIBCPP_VERSION is defined, which means I get a compile error because it can't find cxxabi.h, even though CPPTRACE_HAS_CXX_EXCEPTION_TYPE is not defined.
Is this the correct interpretation of what the #if is meant to check, and if so, would making the precedence of operations explicit in these expressions be the best way to solve the issue?

Thanks for the report

I've released v0.6.0 which includes the fix for this


Are Atomic instructions supported?

Are Atomics (A-Ext) supported? and how to configure riscof to run them?

There are no tests for the A extension currently. Riscof follows the same method of configuration for all the extensions i.e using the isa yaml.

Unknown. I've created an SOW for Dev partners, tiemframe is TBD. Note that it will not be possible to test that they are multi-hart atomic, only they function correctly within a signel hart (even if interrupts occur immediately before or after.

First of all we need tests that check basic functionality of these instructions - like amoadd adds a register value to a memory location - these types of tests shouldn't be hard to generate. (A CPU implementer can mess up even this due the spec misunderstanding). Multiprocessor aspects of these instructions is much more difficult to verify and I'm not sure can be done in this "compliance" tests framework. (Similar as "invisible" aspects of fence/fence.i instruction or interrupts /exceptions handling compliance. )

yes - exactly.
The SOW I wrote up does exactly that (and includes some interesting values
as well)
There are lots of tests that need writing, and it's all volunteers that do
it it (some volunteered by the companies emplying them, or by university
grants) so it takes a while.
On Mon, Feb 20, 2023 at 2:17 PM algrobman @.***> wrote:

First of all we need tests that check basic functionality of these
instructions - like amoadd adds a register value to a memory location -
these types of tests shouldn't be hard to generate. (A CPU implementer can
mess up even this due the spec misunderstanding). Multiprocessor aspects of
these instructions is much more difficult to verify and I'm not sure can be
done in this "compliance" tests framework. (Similar as "invisible" aspects
of fence/fence.i instruction or interrupts /exceptions handling compliance.
)
—
Reply to this email directly, view it on GitHub
https://github.com/riscv-non-isa/riscv-arch-test/issues/315#issuecomment-1437611146,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPXVJR2NDA6TUKABHX5KDTWYPUQNANCNFSM6AAAAAAU2LTXMU
.
You are receiving this because you commented.Message ID:
@.***>

why can't your test generator  do this? (one, which generated all other RISCV tests)I'm running A-Ext tests from https://github.com/riscv-software-src/riscv-tests, which look very similar to the tests from your repo. ..
On Monday, February 20, 2023 at 04:22:35 PM CST, Allen Baum<EMAIL_ADDRESS>wrote:

yes - exactly.
The SOW I wrote up does exactly that (and includes some interesting values
as well)
There are lots of tests that need writing, and it's all volunteers that do
it it (some volunteered by the companies emplying them, or by university
grants) so it takes a while.
On Mon, Feb 20, 2023 at 2:17 PM algrobman @.***> wrote:

First of all we need tests that check basic functionality of these
instructions - like amoadd adds a register value to a memory location -
these types of tests shouldn't be hard to generate. (A CPU implementer can
mess up even this due the spec misunderstanding). Multiprocessor aspects of
these instructions is much more difficult to verify and I'm not sure can be
done in this "compliance" tests framework. (Similar as "invisible" aspects
of fence/fence.i instruction or interrupts /exceptions handling compliance.
)
—
Reply to this email directly, view it on GitHub
https://github.com/riscv-non-isa/riscv-arch-test/issues/315#issuecomment-1437611146,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPXVJR2NDA6TUKABHX5KDTWYPUQNANCNFSM6AAAAAAU2LTXMU
.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

why can't your test generator  do this? (one, which generated all other RISCV tests)I'm running A-Ext tests from https://github.com/riscv-software-src/riscv-tests, which look very similar to the tests from your repo.

The test generator needs augmentation to handle the A extension tests. It does not support it in its current state.

I think the test have been merged into the repo, so I'm closing this. Reopen if you see something missing

Are there LR/SC tests? I've found AMO*  instructions tests only in A- directory ..

This is an issue that has been opened. Supposedly coming shortly.
On Sun, Oct 29, 2023 at 7:58 AM algrobman @.***> wrote:

Are there LR/SC tests? I've found AMO* instructions tests only in A-
directory ..
—
Reply to this email directly, view it on GitHub
https://github.com/riscv-non-isa/riscv-arch-test/issues/315#issuecomment-1784136573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPXVJUFQNFKGSH22ON5INLYBZVHXAVCNFSM6AAAAAAU2LTXMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBUGEZTMNJXGM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Extension causes high cpu load

ms-vsliveshare.vsliveshare-unresponsive.cpuprofile.txt

Issue Type: Performance
Extension Name: vsliveshare
Extension Version: 0.3.1071
OS Version: Darwin x64 18.2.0
VSCode version: 1.30.1

Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Duplicate of #1449


[Documentation] Removing inconsistencies in botskills documentation

Fix 3489

Purpose
What is the context of this pull request? Why is it being done?
There were some inconsistences between documentation and the argument's explanation of botskills.
Changes
Are there any changes that need to be called out as significant or particularly difficult to grasp? (Include illustrative screenshots for context if applicable.)
We fixed the inconsistencies in the documentation and updated some outdated docs.
Tests
Is this covered by existing tests or new ones? If no, why not?
Feature Plan
Are there any remaining steps or dependencies before this issue can be fully resolved? If so, describe and link to any relevant pull requests or issues.
Checklist
General

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated the appropriate tests
[X] I have updated related documentation

LGTM! @LCarbonellRod will review it and as soon as you have their confirmation you can push them to the PR.
Just minor question, have you double checked all the location that the .NET Core runtime is used in the docs? Just to update the semver in every doc

Yes @Batta32, I checked and updated the semver version in every doc. I detected five documents that contains this note.

Can we close this PR? @DiegoCardozo94


Add GitHub workflow to verify Mbed OS image build process.

Problem
Some way to verify proposed Mbed OS docker image is needed.
Related issue: #4653
Summary of Changes
Add new GitHub workflow which builds mbed-os image and verify that all tools which we need are in the place.
Added workflow has to be triggered manually (workflow_dispatch) and should be used on PR #4620 branch

I updated workflow to work with PR #4657 - I guess @woody-apple change will land on master first.

@lukgni CI failures?

In our team we decided to close this PR and return with mbed integration when we will have more complete solution.


updated defaults, deprecating old/unused code

Codecov Report

Merging #12 (e86be0d) into main (1d6cc85) will increase coverage by 7.20%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   83.61%   90.81%   +7.20%
==========================================
  Files           6        6
  Lines        1373     1339      -34
==========================================
+ Hits         1148     1216      +68
+ Misses        225      123     -102

Impacted Files
Coverage Δ

micro21cm/inference.py
89.25% <ø> (+10.39%)
:arrow_up:

micro21cm/models.py
92.23% <100.00%> (+6.74%)
:arrow_up:

micro21cm/util.py
96.59% <100.00%> (+7.22%)
:arrow_up:

Continue to review full report at Codecov.

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


Just Made Things For interaction reply 🌱

Not sure if all people would like to use interaction instead of message. I'll review in some time and let you know


Add an abstract base-class, which all the various Stream implementations inherit from

By having an abstract base-class, it becomes a lot clearer exactly which methods/getters are expected to exist on all Stream instances.
Furthermore, since a number of the methods are identical for all Stream implementations, this reduces unnecessary code duplication in the Stream, DecodeStream, and ChunkedStream classes.
For e.g. gulp mozcentral, the built pdf.worker.js files decreases from 1 619 329 to 1 616 115 bytes with this patch-series.
The only way to review this is probably one commit at a time, with the ?w=1 flag appended to the URL.

/botio test

/botio test

Thank you for all this work; looks much better!

@timvandermeij Thanks a lot for reviewing this patch series; I realize that it cannot have been all that easy, or even fun for that matter!


importlib.metadata.PackageNotFoundError: exchange_calendars in AWS lambda

Reproduced after upgrade from 4.0.2 to 4.1.
Reproducible when packaging exchange-calendar inside AWS lambda function using serverless.
Traceback:
Traceback (most recent call last):
  File "/var/task/src/handler/httpbase.py", line 40, in __call__
    return self.response(event, context)
  File "/var/task/src/handler/httpbase.py", line 108, in response
    from src.dateutils import NonTradingDayException
  File "/var/task/src/dateutils.py", line 9, in <module>
    import pandas_market_calendars as mcal
  File "/var/task/pandas_market_calendars/__init__.py", line 19, in <module>
    from .calendar_registry import get_calendar, get_calendar_names
  File "/var/task/pandas_market_calendars/calendar_registry.py", line 28, in <module>
    from .exchange_calendars_mirror import *
  File "/var/task/pandas_market_calendars/exchange_calendars_mirror.py", line 8, in <module>
    import exchange_calendars
  File "/var/task/exchange_calendars/__init__.py", line 46, in <module>
    __version__ = version("exchange_calendars")
  File "/var/lang/lib/python3.9/importlib/metadata.py", line 569, in version
    return distribution(distribution_name).version
  File "/var/lang/lib/python3.9/importlib/metadata.py", line 542, in distribution
    return Distribution.from_name(distribution_name)
  File "/var/lang/lib/python3.9/importlib/metadata.py", line 196, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: exchange_calendars

Packaging is pretty standard for serverless-python-requirements plugin:
  pythonRequirements:
    slim: true
    dockerizePip: true
    dockerRunCmdExtraArgs: [ '--platform', 'linux/arm64/v8' ]
    dockerImage: public.ecr.aws/sam/build-python3.9:latest-arm64

Hmm @maread99  - any idea here?
Maybe we should also make this try/catch so just in case this never fails

I'm not familiar with the context here, but seems that for whatever reason importlib.metadata was unable to resolve the version. The importlib.metadata doc explains how the module gets the version from the metadata of the installed package, where...

By “installed package” we generally mean a third-party package installed into Python’s site-packages directory via tools such as pip. Specifically, it means a package with either a discoverable dist-info or egg-info directory

I'm guessing this isn't the case in this context.
#214 proposes a fix by falling back on the version as set in _version.py when the package is built.

Thank you for the quick resolution! 4.1.1 works well.

Thanks for letting us know that all's working.


PublicPairedSingleSampleWf: create reference cache from fasta.

Avoids fetching from EBI servers during "samtools index "
by creating the local reference cache from the input fasta.
The fetch from EBI can hang "samtools index" as described here:
https://github.com/samtools/htslib/issues/412
The approach added here is that recommended by:
http://www.htslib.org/workflow/#the-refpath-and-refcache
except without the fallback to EBI.

@vdauwera, @sooheelee, is comms in charge of maintaining this repo? Or is it red team?

Yep, this is on us.

I actually made the same change in #60, generated it from a new private wdl. If you can review that, we can close this PR.

implemented in #60


i can't change fontSize

{
title: {
text: null,
},
series: [{
type: 'liquidFill',
radius: '70%',
data: data,
backgroundStyle: {
borderWidth: 5,
borderColor: '#76b9ed',
color: 'rgba(255,0,255,0)'
},
label: {
fontSize: 30,
normal: {
formatter: value * 100 + '%',
}
}
}]
}

I also encountered this problem. you are supposed to switch to 3.x.x version.

It works with echarts 4.2.1 and echarts-liquidFill 2.0.4.
If it still not works for you, please use the latest version and provide the version code here.


Would Superset Project open a user forum?

The google group seems to be deprecated - does it mean that the only way ta ask a question about using this software is the mailing list?

What's the problem with the mailing list?

It would be nice to have a better way to ask questions. The mailing list is ok, but hard to search.

superset is the first open source project, where i feel it can be a viable solution used by non IT business user, it will be nice really to have a forum, as a non programmer, we are not really used for mailing list, and github

If search is the problem we can probably leverage http://www.nabble.com/

Apache wants us to keep the conversations in Apache infrastructure-approved places like the mailing list and Github. I've used Gitter before, happy to open it up (or even Slack) though I personally don't have much time for it.

I would like to implement the pagination on server_side through the apache superset. Is it possible to override the sql query on explore_json_api on backend side.


pyiceberg always return false for catalog.table_exists when used with Polaris catalog

Apache Iceberg version
0.7.0 (latest release)
Please describe the bug 🐞
cross posting here, as I am not sure, if it is a pyiceberg bug or polaris
https://github.com/polaris-catalog/polaris/issues/96

Hello @djouallah, I did a test with the Tabular catalog and table_exists works as expected. So I believe this is a bug in the Polaris catalog.


Issue with referencing types in files in sub-directories when cwd is at the project root.

I was having difficulty getting ts-data-checker working in a unit test I wanted to write to verify some JSON data files.
My code is in a factionUtils.test.ts file that sits next to the file factionUtils.ts containing the type I wanted to validate the JSON with, so I created the checker like this, as in your example:
const {checkJson} = checker('FactionDetails', './factionUtils');
After multiple attempts and experiments to get it to work, I ended up debugging the failing test into your library code to see what was wrong with my JSON.  It turned out that the validation was failing because Typescript was unable to import the factionUtils.ts file I had referenced.
After trying a few things, I noted that your servicesHost config defined getCurrentDirectory to return process.cwd(), and since my test was being run by a test runner with the cwd at the top level of the project, I changed my test code to create the checker using a path to the file relative to the project root:
const {checkJson} = checker('FactionDetails', './src/server/util/factionUtils');
This got it working, and it was able to validate my JSON data.
It would be nice if ts-data-checker could somehow tell TS to use a cwd that was in the folder containing the call to checker, rather than process.cwd().  The only way I can think you could do that would be to take an optional cwd parameter in the checker function, to which a user can pass in __dirname.  It would be better if there was some way to do it automatically though.
Thanks for the library!

Thank you for your feedback, glad you found the lib useful.
Yes, perhaps an optional parameter with working directory would make sense. I'm also considering if there are other typescript options that needs to be passed to the checker (as in tsconfig stuff). Perhaps that would solve this case too, if you could define e.g. the tsconfig paths array.

As a workaround, you could call process.chdir('./src/server/util') in your tests, but probably need to change it back at the end of the test…

Just published<EMAIL_ADDRESS>where you can do this:
const { checkValue } = checker("BasicType", "./basic", { workingDir: __dirname });

I might consider automatically figuring out working directory relative to the current module using callsite or parent-module for a future version, but that would be a breaking change.

Awesome, thanks for the quick turnaround!
Do you think you might add something to the README about this issue?  The Caveats section could note that the path to the file passed to the checker function is relative to the cwd of the process, and that you can override that with the workingDir optional parameter.

Yeah, added an Options section as well.

Nice :)


Relax setuptools build dependency

With the same context and for the same reason as https://github.com/reity/fountains/pull/1 and https://github.com/nthparty/fe25519/pull/1.

Version 1.5.1 of ge25519 is on PyPI.


Does it compatbile with all browsers?

AngularJS-Toaster supports what all browsers?

Hi, I haven't tested all browsers. I suppose that it works on modern browsers. IE 8 might have some troubles with CSS3 but I haven't tested it.


Support object_ids that start with 0

Resolve #278
This lets us parse and roundtrip ids that start with 0 correctly, both on Rust and JS.
To do this, we pad the packed value into a 12-byte (24-character) string, which is the expected length on mongodb.  This works for me in both sim and production.
I'm kind of unclear on whether there are other backends that may not like this format or if there is any reason to keep the shorter format around.

Unfortunately I think loki-backed private servers still use 15 byte ids - see #244. We'll probably need to store the length of the string to solve reliably, as discussed there.  Or we could declare loki private servers unsupported, but I suspect we should probably avoid going down that road given the number of complaints we already get for being incompatible with sim ;)

Would it work to gate 15-byte mode behind a feature?  I don't think we would need to support both in a single build, and it would avoid figuring out how to pack this in the type itself and the associated marshal/demarshal check

Yeah, a feature flag for loki compatibility would probably do the job just fine without having to stress about performance penalties, and doing one for sim has been one of the ideas proposed for the issues there - I think that'd probably work.

Hrmm.. one last big tricky bit on this is that the default map on private servers retains the 'random' 15 byte ids on room objects, so those objects break things.

I believe 15 byte mode should be supported with the short-id feature.

From @shanemadden

Oh right - it's that if you have a mixed set of ids (like if you use the default private server map, which has short ids, but then use a mongo backend which uses long ids) then a feature flag doesn't cut it. I was thinking we'd maybe need to go with a more onerous fix of having a value in the id which indicated how many characters to pad to

Closing for now.


Search SDK: Merge AutoRest to search-v2-preview-dev

@brjohnstmsft Can you squash these commits, please?

Given the issues in the CI builds right now, I'm just going to abandon this and try again later when the dust settles from the .NET Core RTM migration.


feat: Add ability to configure client TLS

Hello there! :)
There is no issue for this PR yet (I think I will create it)
This PR adds support for TLS client certificates at transport level. It's intended for those S3 endpoints that are behind mTLS protection. This has been already tested in our endpoints and it's working well

I have added those params as flags under format command as this is more expectable by the user.
I saw you stored some of them as query params, for example tls-insecure-skip-verify but equally they are stored in metadata settings
WDYT?
CC: @davies @SandyXSD @zhijian-pro I mention you all as you are the top contributors, so I dunno who to invoke

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

This definitely would be useful for me. 👍

@davies Fixed

lgtm, please update the docs for these parameters, thanks!


Style guide/rules

We have a scalastyle config and reference it in Contributing.md, but do not actually use it. We should/could actually use a formatter. Or we decide to not use a formatter and remove it from the contributing guide.

Maybe we should consider switching to scalafmt first.
Scalastyle is pretty much abandonware and scalafmt is quite powerful, although it lacks documentation.
That being said, I like scalastyle. I have always found it easier to make it do what I want, but there have been some improvements to scalafmt recently that fixed that.
Also the language aware features of scalafmt are really nice.
Thoughts?

Scalafmt sounds good, let's add it after merging #441


Feature request: Send Traces to Observability Frameworks

Use case
For production use-cases, we need some way to send traces of the orchestrator and agents to an Observability Framework like Langfuse, so they can be visualized there nicely and combined with user feedback.
Right now, it is unclear to me how this is possible. Only getting text from logs is not sufficient for debugging when a lot of users utilize the system.
Solution/User Experience
Need some kind of mechanism to write traces to external SDKs like the one from Langfuse (https://langfuse.com/docs/integrations/amazon-bedrock).
Alternative solutions
No response

@brnaba-aws  Thanks for your help. I will try to implement this to send the input, output and reasoning steps to LangFuse like in this example from AWS (https://aws.amazon.com/de/blogs/machine-learning/accelerate-analysis-and-discovery-of-cancer-biomarkers-with-amazon-bedrock-agents/):

Hi @maxritter
Please let us know how it goes, we might provide this as an example in our repo for others.

We have started some experimentation with langfuse and minimal modification in our framework.
So far so good. We need to finalize a bit the design

@brnaba-aws Thanks for your efforts! I do not have time in the next couple of days to tackle this, but the way I thought about implementing it would be using https://langfuse.com/docs/sdk/python/low-level-sdk to include:

Traces (Tracks agent execution from input query to final output including token usage and all spans / generations)
Spans (Log sub-events like Knowledge Base call including input / output, execution time)
Generations (Metadata about model calls including input / output messages, cost, execution time)

Here is a good example of how the different type of events can be captured after calling the invoke_agent function from Boto3: https://github.com/aws-samples/amazon-bedrock-agents-cancer-biomarker-discovery/blob/c86dd6c07a445d8c3134d2eb11db5667ebf49945/streamlitapp/app.py#L230
It's not a complete list of all things that can be captured, there is even more in https://docs.aws.amazon.com/bedrock/latest/userguide/trace-events.html.

Thanks for sharing this. I think, as a best option for us, we would have a callback for each steps (before/after calling LLM, tools, Retriever, Agents...)


feat(network): add container as network on creation

allows selection of container as network (select 'container' in network dropdown menu)
fix error when a container is not connected to any networks (#302) - I have implemented the same solution as Glowbal to hopefully alleviate merge conflicts)

I personally never used container as a network (wasn't even aware that this was possible) but I feel like the UX could be enhanced on this one, maybe by bringing a dropdown with the name of all the containers instead of having to input the container name (less error prone, more easy to use).
Waiting for @ncresswell review.

Yeah, agreed. It does show an error message if the container you entered doesn't exist, but having a drop down box would definitely be better.
I'll have a go this evening

It's now updated so that you can select running containers. I can't seem to get swarm working to test it out there (/dockerapi/info just seems to hang and then return 500), however I copied some of the logic from the templates route, so hopefully it will work in swarm as well as on a single host

Awesome, we will give it another review soon. Also, we'll ensure that it's working on each all our environments before merging (final workflow step).
I'll define the contribution workflow somewhere.

@Glowbal No technical review has been made on this now for now. The workflow will be posted soon but FYI the first step is a functional review, if it's approved then I'll do the technical review :)
Also, yes, as there is no CI yet, be sure to run grunt lint (it's in the contribution guidelines).

whoops, missed those - fixed now.

@deviantony all done :)

Not working with Docker Swarm, when trying to run a container using another container network the following issue is raised:
Unable to find a node that satisfies the following conditions
[available container slots]
[--net=container:/swarm-node1/containername]

The part /swarm-node1/ should be removed from the container name, see my comment.

I'll try to get it running locally in swarm mode to fix the swarm issues later

managed to get it working in swarm, strangely though the container was shown as /containername, not /swarm-node1/containername though. I've catered for both though.

@RobBrazier thanks I'll review it again.
Note that we support Docker Swarm and Docker swarm-mode which are two different things. The /swarm-node1/containername behaviour is only present with Docker Swarm.

@RobBrazier Reviewed again, please update one thing (see my comment). I've tested it with the change against Swarm / Docker swarm mode and Standalone. Works fine.


RFW0034: Monlam dictionary editor mock

Abstract
This RFC proposes the design  Monlam Grand Dictionary Editor . The UI will provide an intuitive and user-friendly platform for managing dictionary entries, enabling users to interact with the backend API for tasks such as editing database values, searching entries, and managing user roles and permissions.
User Interface Design
Key Pages

Login Page

Dashboard

Overview of dictionary metrics and shortcuts to key features.

Dictionary Entries

List view with search, sort, and filter options.
Editable form modal for creating or editing entries.

User Management

Accessible to Admins only.
Display list of users and their roles.

Steps

[x] Requirements gathering and wireframe design.
[x] Auth

[x] Side Graphic Image

[x] editor

[x] Inputs fields Component
[x] Layout Design

changes after review

[x] Sidebar

[x] Closing
[x] Layout Design

[x] pop up sense (flow and design)
[x] Mobile Responsive
[x] flow for reviewer
[x] Prototype

Card Reviewer

[ ] @kaldan007  @Tendolls

figma link: https://www.figma.com/design/XIUwbSgQSpT2viGFcXSkm8/Editor?node-id=5-104&t=OQ0bp2hdFvlJaAfz-1

ready for review
cc @kaldan007

all changes are reflected
cc @kaldan007


Replicate ocaml-bench-server setup

In Sandmark, we dynamically generate a configuration JSON file and invoke make ocaml-versions/target.bench from a Makefile to produce the benchmark results.
TAG='"run_in_ci"' make multicore_parallel_run_config_filtered.json
TAG='"macro_bench"' make multicore_parallel_run_config_filtered_filtered.json
RUN_BENCH_TARGET=run_orunchrt BUILD_BENCH_TARGET=multibench_parallel RUN_CONFIG_JSON=multicore_parallel_run_config_filtered_filtered.json make ocaml-versions/4.12.0+domains.bench

When integrating with current-bench, is there a way to parameterize these steps for a single or multiple benchmark pipeline invocation?
Reference:

https://github.com/ocaml-bench/sandmark/blob/master/run_all_effects.sh
https://github.com/ocaml-bench/sandmark/blob/master/run_all_parallel.sh
https://github.com/ocaml-bench/sandmark/blob/master/run_all_serial.sh
https://github.com/ocaml-bench/sandmark/blob/master/Makefile#L111

With the use of a custom bench.Dockerfile in current-bench, we can now pass these build steps as an environment variable in the Dockerfile.


suggestion: hide the bars

Would it be possible to have an option that hides the button and search bars at the top of the window? The window itself is good and useful but I don't need the bars.
The button bar has some functionality of the options page. But I did set the options weeks ago and it runs since then exactly like that. I never use these buttons in daily work, not one of them. The same with the search bar. I can remember what I have open, I must never search one of my seven or ten open files. (I know, other people have 50 or more files open, but this is not me.)
The options are always available in the Tools|Options menu, so the user can always switch the bars on  again when this should be needed.
Note: These two bars consume a constant hight of about 15mm which I call wasted. This comes on top of the Solution Explorer which also wastes 15mm. I would like to use this vertical space for something more useful.

Please upgrade to version 1.6.0 for this feature

Great! Thanks a lot for that.


perf(transformer): reuse same UID for _this in arrow function transform

Re-use same _this UID for every scope, instead of creating a new one each time - _this, _this2 etc. It's not necessary for each var to have a different name, as only one this can be in scope anywhere.
Conformance fails because some of Babel's test cases rely on every _this var to be named differently, so we can't merge this, but submitting PR just to see the effect on benchmarks.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5840  👈
#5839
#5837
#5836
#5833
#5830
#5828
#5827
#5826
#5825
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

Interesting. generate_uid is now cheap enough that this doesn't make any noticeable difference on benchmarks. Or maybe our benchmarks don't include enough arrow functions containing this for the code to be exercised.


Fixed the aggregate report broken link.

Aggregate-report failed at one of the broken link in Readme:
https://docs.microsoft.com/samples/azure-samples/azure-samples-python-management/{{package_doc_id}}
We have to either put a concrete link or put the link in file:

I believe it's fixed today


[DO NOT MERGE] debug no ci logs in e2e tests

@rajatjindal Is this PR still an active avenue of investigation, or have we established that it's space that's the issue and no more info is required?

yes, @vdice confirmed it is due to resource issues.


[RFR][TA]Go analysis test

Resolves https://issues.redhat.com/browse/MTA-3374 and https://issues.redhat.com/browse/MTA-3179.
Marked the Test case with the bug https://issues.redhat.com/browse/MTA-3661

@kpunwatk looks like you're not signing the commits, we need the commits to be signed to merge the PR

I always do signing, but let me check and sign-in again, Thanks!

Done @abrugaro, Ready for merge, Thank You!


Compatibility with BlockArrays?

It would be awesome to get some compatibility between BlockArrays and ComponentArrays.
Either BlockArrays of ComponentArrays, such that I'm able to access some vector at
x[Block(i)].componentName
or/and ComponentArrays of BlockArrays, in order to access some vector at
x.componentName[Block(i)]

It’s kinda tough to have components be different array types like this. In theory, you should be able to store the component’s type for reconstruction, but in practice it just doesn’t work at all because other array types don’t all follow the same interface for reconstruction via type.

But I guess I’d also have to see an example of something that would be accomplished with ComponentArrays + BlockArrays that can’t just be accomplished with ComponentArrays.

How would you handle components c1,c2,...,cN for varying N right now??
Am 24. November 2022 19:20:12 schrieb Jonnie Diegelman
@.***>:

But I guess I’d also have to see an example of something that would be
accomplished with ComponentArrays + BlockArrays that can’t just be
accomplished with ComponentArrays.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID:
@.***>

You could do something like this:
julia> N = 5
5

julia> ca = ComponentArray(NamedTuple(Symbol(:c, i) => rand(3) for i in 1:N))
ComponentVector{Float64}(c1 = [0.5482904644627941, 0.13909008040255955, 0.013857229990063002], c2 = [0.3497491172730053, 0.323080764846305, 0.5759352391226321], c3 = [0.30645828956848165, 0.49153219318714503, 0.5192535821238988], c4 = [0.557607879404576, 0.4721650175935741, 0.2839147469190002], c5 = [0.44203806768864384, 0.20414854972570728, 0.8787506621852561])

julia> ca.c3
3-element view(::Vector{Float64}, 7:9) with eltype Float64:
 0.30645828956848165
 0.49153219318714503
 0.5192535821238988


modified:   src/main/java/org/jsoup/select/StructuralEvaluator.java as per issue #2108

[API] [Question] Why is StructuralEvaluator not public? #2108

Pull request submitted for issue #2108, waiting for build checks to complete as per this comment.

Small code updates based on best conventions. Using SonarLint.

Treebuilder stack.size() == 0 => stack.isEmpty()

Suthat

My code failed to build. So why are you spamming this?

Builds failed


[Bug]: Error while migrating to null-safety

Dart SDK Version (2.13.1)
Whether you are using Windows, MacOSX, or Linux -- Windows
Whether you are using Chrome, Safari, Firefox, Edge -- Chrome

I tried migrating my codebase
E:\okDone\flutter-main\okdone>dart migrate
Migrating E:\okDone\flutter-main\okdone

See https://dart.dev/go/null-safety-migration for a migration guide.

Analyzing project...
[---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|]
No analysis issues found.

Generating migration suggestions...
[----------------------------------------------------------------------------                                                                                ]
Aborting migration due to an exception.  This most likely is due to a
bug in the migration tool.  Please consider filing a bug report at:

https://github.com/dart-lang/sdk/issues/new
Please include the SDK version (2.13.1) in your bug report.

To attempt to perform migration anyway, you may re-run with
--ignore-exceptions.

Exception details:

NoSuchMethodError: The getter 'node' was called on null.
 The node variable which it's mentioning in the output is not there in my codebase.

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


usm: Enable event stream by default

What does this PR do?
Enable the use of the events stream by default instead of netlink for monitoring processes since the former has shown to be more dependable.
Motivation
https://datadoghq.atlassian.net/browse/USMON-1344
Describe how to test/QA your changes
Automated tests have been updated.
The event stream enabled config is already running in staging (on some clusters for months).
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Worm isn't a synonym for C elegans?

I searched NIF for worm, and it doesn’t appear to be a synonym for C elegans. I thought we took care of that a long time ago?
Maryann Martone, Ph. D.
Professor-in-Residence
Department of Neuroscience
University of California, San Diego
San Diego, CA 92093-0608
858-822-0745

NIFORG:birnlex_420 is indeed missing worm as a synonym

NCBITaxon:6239


New version: DataToolkitCommon v0.3.0

Registering package: DataToolkitCommon
Repository: https://github.com/tecosaur/DataToolkitCommon.jl
Created by: @tecosaur
Version: v0.3.0
Commit: 6af8a64f472496c3a59b8eb8f02994d39bfb64c9
Reviewed by: @tecosaur
Reference: https://github.com/tecosaur/DataToolkitCommon.jl/commit/6af8a64f472496c3a59b8eb8f02994d39bfb64c9#commitcomment-107351916
Description: A collection of data tranformers and plugins

please close this PR, an issue slipped in


[REQUEST] Support for advanced generators for energy module

I would like to request support for advanced generators with the energy module.
https://bdew.net/generators/
https://github.com/bdew/generators/
Enjoying the mod :)

If those generators properly support the CoFH RF API it should work automatically. Are you really sure it isn't working? You must use the energy module on the actual block where you can also extract the RF from.

I had tested it several location of the multi-block but possibly not the output as that was hidden behind. I will test that now.

I have tested it and it is indeed "user error" :)
Thanks.


Bring back Add method overloads to DataLogger

Due to the reimplementation of the DataLogger two of the Add overloads were dropped.
But as @jpgarza93 has mentioned in #4114, they can be useful. Bringing them back.

Thanks for this PR @drolevar, and thanks @jpgarza93 for pointing out the change! This will be in the next release 🚀


Fix a little RFC5321 syntax unconformance

Description

I removed the additional spaces in two email commands
Motivation and Context
The description of the Mail transaction as provided in the RFC5321 does not specify a space after the MAIL FROM: and RCPT TO: commands.
How Has This Been Tested?

This changes were tested with an instance of the dovecot submission server, that previously refused the client commands.

Checklist:

[x] I have submitted a CLA form
[x] If applicable, I have updated the documentation accordingly.
[x] If applicable, I have added tests to cover my changes.

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

Hello, I signed the CLA, you can now merge the PR

@vitkabele Thanks for the PR.  Unfortunately I haven't gotten around to fixing these unit tests yet since they require test email accounts.  But I'll go ahead and merge since @mbarnach gave the thumbs up and visual inspection seems good and straight forward enough. :-)


fix: cross-site errors; can't access window.top

Description

Within the iframe, when its hosted on a different site than the parent frame, it can't access the window.top properties and thus it throws cross-site scripting errors.  This changes the render function as well.
Additional context (optional)

Checklist
Have you considered all of the following?
Please confirm by checking off each item to ensure you've considered it:

[ ] Did you create or update tests?
[x] Did you create or update any documentation?

Fixes:

Codecov Report

Merging #82 (98de4e1) into main (05cb07b) will increase coverage by 3.76%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #82      +/-   ##
==========================================
+ Coverage   46.50%   50.26%   +3.76%
==========================================
  Files           9        8       -1
  Lines         243      189      -54
  Branches       41       34       -7
==========================================
- Hits          113       95      -18
+ Misses        108       75      -33
+ Partials       22       19       -3

Flag
Coverage Δ

unittests
50.26% <0.00%> (+3.76%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/api/utils.js
55.69% <ø> (ø)

src/frame/auction.js
23.80% <ø> (ø)

src/frame/utils.js
14.28% <0.00%> (-0.61%)
:arrow_down:

Continue to review full report at Codecov.

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


Pairs has suffix??

How to trade the brokers that used suffix after the name of a pair?? Like - Exness(GBPUSDm)

This project is open source. You can fork the repository, and in the SYMBOLS list, you can append the 'm' or whatever suffix you need to all the pairs available. You can even add support any pairs that are not already included in the list.

Closing this issue

@HackyN00b As mentioned previously, you'll have to fork this repository and remove EURUSD from the list of SYMBOLS and replace it with EURUSDx instead, then you'll be able to deploy that version of your telegram bot. However, I've created a new version of this bot that handles this for you. Please check out this video here: https://youtu.be/niWDWnlc3xU

@HackyN00b, Hmm this is interesting. I'm assuming that you've added "EURUSDX" to the pair of symbols but kept "NOW" in there as well too? I'll investigate more into this.

@HackyN00b It might help if you post a link to your repository as well

@HackyN00b I believe the issue is being thrown by MetaAPI (aka your broker). If you look in the run.py file, the "Specified symbol price not found" error message is not something thrown by the script, but rather the MetaAPI when a trade is attempted to be placed.
If I had to guess, I'm assuming that you may have misspelled the name of the symbol ? Rather than using a capital 'X' in EURUSD, I'm assuming maybe it's either EURUSDx or EURUSD.x, but I'm not completely sure without knowing who your broker is.

I'm not entirely sure what the issue is, I just ran the code here with parsing the signal and it works as expected. https://onecompiler.com/python/3ze6gk5wb

I tried to also add suffix, but it's giving me the same error Invalid Trade
here is a link to my repository, to my run.py file where I changed all the pairs to XXXXXX.i, because my broker has ".i" after all the pairs...
https://github.com/edycbu/MT4-MT5-Forex-Signal-Copier-Telegram-Bot/blob/16007c1e00e7f721eec0f9f47f4d1afcc076e3c6/run.py

Can you help me ?

having the same issue, but works on normal symbols without the suffix..


viber: <IP_ADDRESS> -> <IP_ADDRESS>

Also change url back to upstream. Web-archive is very slow, at least for me.

Motivation for this change
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[ ] 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/)
21.11 Release Notes (or backporting 21.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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 146492 run on x86_64-linux 1

1 package built:

viber


FIX-#2498: Fix possible number of partitions for Dask engine

Signed-off-by: yaroslav.igoshev<EMAIL_ADDRESS>
What do these changes do?

 Tests are passing locally. I will rerun CI.

As I expected, cluster member is not always equal to not None. I am changing the fix.