Guard boost::filesystem usage

Description
CMake was unopinionated about what filesystem is used and required excessive flag setting. Now it clarifies that boost::filesystem is default and std::filesystem is used in case
BOOST_GIL_USE_BOOST_FILESYSTEM is off and CMAKE_CXX_STANDARD>=17.
Apparently we did not explicitly linked to boost libraries anyway. Either that, or I overlooked it.
References
https://github.com/boostorg/gil/issues/742
Tasklist

[ ] Add test case(s)
[ ] Ensure all CI builds pass
[ ] Review and approve

I think this is what we need, thank you!

Boost::gil still unconditionally links to Boost::filesystem
https://github.com/boostorg/gil/blob/201f31c76eed54b304f8d89e44da08a5e8825094/CMakeLists.txt#L30

Thanks @Osyotr for reporting that.
I have not tested, but I think that line should read - if I still can remember CMake expressions
$<$<BOOL:${BOOST_GIL_USE_BOOST_FILESYSTEM}>:Boost::filesystem>

Additionally, this piece
https://github.com/boostorg/gil/blob/e5f5bce2b953c49f964ddf677a3dc2a97bde3eb6/CMakeLists.txt#L114-L126
could be simplified to
target_compile_definitions(gil_compile_options
  INTERFACE
    $<$<CXX_COMPILER_ID:MSVC>:_CRT_NONSTDC_NO_DEPRECATE>
    $<$<CXX_COMPILER_ID:MSVC>:_SCL_SECURE_NO_DEPRECATE>
    $<$<CXX_COMPILER_ID:MSVC>:_CRT_SECURE_NO_WARNINGS>
    $<$<CXX_COMPILER_ID:MSVC>:NOMINMAX>
    $<$<CXX_COMPILER_ID:MSVC>:BOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE>
   $<$<BOOL:${BOOST_GIL_USE_BOOST_FILESYSTEM}>:BOOST_GIL_IO_USE_STD_FILESYSTEM>)

Am I correct?

Honestly I'd prefer not to force a specific filesystem library implementation at build time because once cmake config is installed, it's impossible to switch to another implementation.
Effectively I propose reverting this PR and removing explicit linkage on Boost::filesystem from the public interface and keep it for tests.

@Osyotr I now see better what you mean. Although I don't mind reverting it, especially if it smoothens the vcpg integration, but I do need to point out at a couple of things related to our CMake configuration

The (historic) status of our CMake:
https://github.com/boostorg/gil/blob/e5f5bce2b953c49f964ddf677a3dc2a97bde3eb6/CONTRIBUTING.md?plain=1#L387-L389

The fact that those deps where generated by Boost-wide tooling, so might be that not just GIL is affected by the deps annoyance:

#614
https://github.com/boostorg/gil/blob/e5f5bce2b953c49f964ddf677a3dc2a97bde3eb6/CMakeLists.txt#L12

So, chances are the boost::filesystem will reappear.

I'm not seeing how this PR here is causing the trouble. I think, it is more the change in PR #614 that causes it, isn't it?

Actually I think there's no problem. These options are meaningless in vcpkg because we take the "if" path:
https://github.com/boostorg/gil/blob/8994c2ff8ed8b88e0ffef9658a4c603c4a001fad/CMakeLists.txt#L10-L41
I was confused by the lack of indentation inside if-else block and thought that these target_link_libraries calls are sequential.

@Osyotr No problem, thanks for your feedback. I'm happy to make package maintainers life easier. So, please feel free to report issues/suggest improvements.


Simulating the Gripper in ROS

Using the gripper in simulation appears to not be possible in a ROS environment, at the moment. Using MoveIt's pick command in simulation with the demo launch file from the panda_moveit_config package results in the 'No sampler was constructed' issue #17.
As a replacement, I tried to use the grasp action from the franka_gripper_node and interfaced it from Python without problems. However, an action server must be available, obviously, but demo.launch does not provide such one. Only, the gripper node provides it but also requires a connection to the FCI and thus a real robot, to which a have only very limited access in my usecase.  Then the gripper node is able to start but this it fails to get the (real) gripper state which is not published via UDP as it is required for the gripper node.
As a result, I am stuck. The only thing I can do is to move the gripper via the fake joint state publisher node from demo.launch. Anyways, there should be some way to use gripper in simulation. Just moving the robot around, which works fine with MoveIt by the way, becomes boring at some point ;-)

The "simulation" is provided by MoveIt's MoveItFakeControllerManager. The hand also has a fake controller manager, so it works the same was as the robot.
Simply running roslaunch panda_moveit_config demo.launch and then using the RViz MotionPlanning tab to control the hand (or panda_arm_hand) planning group with a random goal state seems to work fine, so in principle it should work.

Yes, you cannot use the franka_gripper_node (or, I think, any of the other franka_ros nodes) without a real robot. Even for the robot arm itself, it is only MoveIt which provides fake execution, but e.g. the franka_control_node topics and services are also not simulated.

Ok. It's nice to have a confirmation for my assumption.
Are there any plans to provide kind of a simulation mode for the Franka nodes where not FCI/robot is required? In my particular use-case, I have only limited access to the robot, thus a primarily rely on simulation during development. Maybe this is true for other developers as well.

Sorry, I just realized I never answered you again. There are currently no plans to provide a simulation mode for the gripper or the robot. You should, however, be able to use MoveIt's fake execution with the gripper as well. Of course, then you can only use MoveIt's control_msgs::GripperCommandAction and not franka_ross custom gripper actions.


Dotted lines

Hi there,
.. how do I get rid of those red or blue dotted lines around textElements, at margins etc in the generated file?
thx

..sry. silly question. it is the debug mode:
url = try PDFGenerator.generateURL(document: document, filename: "Example.pdf", progress: {
(progressValue: CGFloat) in
print("progress: ", progressValue)
}, debug: false)
thx anyway.

Duplicate of #83


Arm64 problem while configure

I have the latest Xcode version, and when executing the build script, all architectures work fine, except for arm64. When I get to arm64, the shell prints:
Problem while make - Please check […]/OpenSSL-for-iPhone-master/bin/iPhoneOS7.1-arm64.sdk/build-openssl-1.0.1g.log
When looking at the log, these are the last lines:
/opt/local/bin/ranlib: /opt/local/bin/ranlib: cannot execute binary file
ar: internal ranlib command failed
make[1]: *** [../libcrypto.a] Error 1
make: *** [build_crypto] Error 1
I googled the issue, and found this page: http://lists.cs.uiuc.edu/pipermail/llvmbugs/2014-March/033328.html, which suggested I change the ranlib path. So I changed my /opt/local/bin/ranlib alias to the recommended path suggested on the page, '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib', add then all architectures stopped working. I filtered the generation to arm64, but it still didn't work for that one, and the error remained the same. So I reversed to the original ranlib alias, and the other architectures except for arm64 resumed working.
Still, I really need it to compile for arm64. Could you suggest any resolutions to the issue?

Hello from 2015! :)
Thank you @isa56k for your tips. I tried lots of suggestions, but yours worked.
I have the same issue on Yosemite 10.10.5 with Xcode 7.1 and installed Command Line Tools. Cocoapods 0.39.0. No MacPorts.
I found that ranlib was linked to libtool.
~ ls -lamo /opt/local/bin/ranlib
lrwxr-xr-x  1 root  7 Jan 30  2014 /opt/local/bin/ranlib -> libtool

I removed link and copied ranlib from /usr/bin/ranlib
~ sudo rm /opt/local/bin/ranlib
~ sudo cp /usr/bin/ranlib /opt/local/bin/ranlib
~ ls -lamo /opt/local/bin/ranlib
-rwxr-xr-x+ 1 root  14160 Oct 27 16:21 /opt/local/bin/ranlib
~ which ranlib
/opt/local/bin/ranlib

Just in case, I read that there could be similar issues with ar. My ar was okay.
~ which ar
/opt/local/bin/ar
~ ls -lamo /opt/local/bin/ar
-r-xr-xr-x+ 1 root  32176 Jul  5  2013 /opt/local/bin/ar

I found it was sufficient just to remove /opt/local/bin from my path.


Adding changes to extend secret stores scope to global

Description

Adding changes to support global scope
Remove appliction as a requred property
Create namespace provided by user if not exists
Adding unit tests

Design doc: https://github.com/radius-project/design-notes/pull/38
Type of change

This pull request adds or changes features of Radius and has an approved issue (issue link required).
This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and doesn't change the functionality of Radius (issue link optional).

Fixes: https://github.com/radius-project/radius/issues/7030

Do we have a plan to add a functional test for this? Or update an existing test?

Planning to add it as part of the private repo functional work! as we need to create a global scoped secret store resource.


Tag version with precompilie()

Could you please add a tag for this recent change?

I was hoping to do this after #57 clears up. That is fixed on master but not the current rc. This package doesn't need to change, but then the tests will pass.

@jverzani I didn't understand your comment very well. I know that __precompile__() is already in master, you meant the tag will be added soon after #57 is solved?

Yes, but #57 is a Julia issue, not an issue with the package. I expect the
next rc to fix it.
On Sunday, August 7, 2016, Júlio Hoffimann Mendes<EMAIL_ADDRESS>wrote:

@jverzani https://github.com/jverzani I didn't understand your comment
very well. I know that precompile() is already in master, you meant
the tag will be added soon after #57
https://github.com/Keno/Polynomials.jl/issues/57 is solved?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Keno/Polynomials.jl/issues/62#issuecomment-238113911,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZvTGOsRsnu3DkiyjCfz5Xbs7Fw4q9bks5qdmKHgaJpZM4JejeO
.

--
John Verzani
Chair, Department of Mathematics
College of Staten Island, CUNY
<EMAIL_ADDRESS>

Could you tag a new release now please?

Just tagged and published. Should hit metadata soon. Thanks!


[WIP] Bug: Typing quickly in textinput gives incorrect output

Issue: The cursor position is not reliable when typing quickly - it can lag behind and cause text to be inserted in the incorrect position.
Example:

Defect: Our cursor-positioning logic is based on a render hook, which is dependent on re-renders and framerate.
Fix: We should adjust the cursor position at the same time we adjust the text.

@glennsl fixed this in a much better way in #644


Excuse me, can I add the euleros CVE ?

Excuse me, can I add the euleros CVE ?
https://developer.huaweicloud.com/euleros/cve.html

Have you got the list of this CVE's in any format (xml, json)?


处理格式错误的LRC会panic

Check for existing issues
检查是否已存在相同issue

[X] Completed/已检查

Describe the bug and provide steps to reproduce it
描述遇到的bug并提供相应的复现方法
播放日推歌曲Shadow Of The Sun（Adventure Club Remix）时panic
Environment / 运行环境
操作系统：ArchLinux
CPU架构：AMD64
musicfox版本：V4.3.1
If applicable, list the error messages you see
如果有错误输出请一并填入

If applicable, attach your ${MUSICFOX_ROOT}/musicfox.log file to this issue.
如果${MUSICFOX_ROOT}/musicfox.log里有错误日志，请一并上传
日志文件内无内容

歌曲id为28723886

歌曲id为28723886

判断为网易云api返回的歌词格式错误
{
    "sgc": false,
    "sfy": false,
    "qfy": false,
    "transUser": {
        "id": 1643796,
        "status": 99,
        "demand": 1,
        "userid": 0,
        "nickname": "Ri_NanMo",
        "uptime":<PHONE_NUMBER>360
    },
    "lyricUser": {
        "id": 1643781,
        "status": 99,
        "demand": 0,
        "userid": 0,
        "nickname": "CHENRUI_LIN",
        "uptime":<PHONE_NUMBER>360
    },
    "lrc": {
        "version": 11,
        "lyric": "[00:00.00] 作词 : Max Elto\n[00:01.00] 作曲 : Max Elto\n[00:28.37]Oh and I need you.\n[00:31.74]Oh and I need you.\n[00:34.95]Oh and I need you.\n[00:38.22]Oh and I need you.\n[00:41.67]Oh and I need you.\n[00:44.99]Oh and I need you.\n[00:48.52]Oh and I need you.\n[00:51.63]Oh and I need you.\n[00:54.88]I'm in the shadow of the shadow of the sun,\n][00:57.87]where I belong there's something coming on.\n[01:01.66]I'm in the shadow of the shadow of the sun,\n[01:05.65]Oh and I need you.\n[01:08.77]I'm in the shadow of the shadow of the sun,\n[01:11.45]where I belong, there's something coming on.\n[01:15.33]I'm in the shadow of the shadow of the sun,\n[01:19.29]Oh and I need you.\n[01:23.18]Oh and I need you.\n[01:33.62]Oh and I need you.\n[01:46.89]Oh and I need you.\n[02:00.52]Oh and I need you.\n[02:07.55]Oh and I need you.\n[02:41.39]Oh and I need you.\n[02:55.82]Oh and I need you.\n[03:11.69]I'm in the shadow of the shadow of the sun,\n[03:14.55]where I belong there's something coming on.\n[03:18.29]I'm in the shadow of the shadow of the sun,\n[03:22.23]Oh and I need you.\n[03:25.80]I'm in the shadow of the shadow of the sun,\n[03:27.94]where I belong, there's something coming on.\n[03:31.93]I'm in the shadow of the shadow of the sun,\n[03:36.34]Oh and I need you.\n[03:38.57]I need you.\n[03:40.11]I need you.\n[03:41.71]I need you.\n[03:43.31]I need you.\n[03:44.91]I need you.\n[03:46.61]I need you.\n[03:48.31]I need you.\n[03:49.96]I need you.\n[03:51.83]I need you.\n[03:53.50]I need you.\n[03:54.98]I need you.\n[03:56.86]I need you.\n[03:58.45]I need you.\n[04:00.22]I need you.\n[04:03.78]Oh and I need you.\n[04:17.86]Oh and I need you.\n[04:24.52]Oh and I need you.\n[04:58.99]Oh and I need you.\n"
    },
    "klyric": {
        "version": 0,
        "lyric": ""
    },
    "tlyric": {
        "version": 6,
        "lyric": "[by:Ri_NanMo]\n[00:28.37]噢我需要你\n[00:31.74]噢我需要你\n[00:34.95]噢我需要你\n[00:38.22]噢我需要你\n[00:41.67]噢我需要你\n[00:44.99]噢我需要你\n[00:48.52]噢我需要你\n[00:51.63]噢我需要你\n[00:54.88]我活在无限的阴影中\n[00:57.87]而在这属于我的地方好像有什么事要发生\n[01:01.66]我活在无限的阴影中\n[01:05.65]哦我需要你\n[01:08.77]我活在无限的阴影中\n[01:11.45]而在这属于我的地方好像有什么事要发生\n[01:15.33]我活在无限的阴影中\n[01:19.29]噢我需要你\n[01:23.18]噢我需要你\n[01:33.62]噢我需要你\n[01:46.89]噢我需要你\n[02:00.52]噢我需要你\n[02:07.55]噢我需要你\n[02:41.39]噢我需要你\n[02:55.82]噢我需要你\n[03:11.69]我活在无限的阴影中\n[03:14.55]而在这属于我的地方好像有什么事要发生\n[03:18.29]我活在无限的阴影中\n[03:22.23]噢我需要你啊\n[03:25.80]我活在无限的阴影中\n[03:27.94]而在这属于我的地方好像有什么事要发生\n[03:31.93]我活在无限的阴影中\n[03:36.34]噢我需要你啊\n[03:38.57]我需要你\n[03:40.11]我需要你\n[03:41.71]我需要你\n[03:43.31]我需要你\n[03:44.91]我需要你\n[03:46.61]我需要你\n[03:48.31]我需要你\n[03:49.96]我需要你\n[03:51.83]我需要你\n[03:53.50]我需要你\n[03:54.98]我需要你\n[03:56.86]我需要你\n[03:58.45]我需要你\n[04:00.22]我需要你\n[04:03.78]噢我需要你啊\n[04:17.86]噢我需要你啊\n[04:24.52]噢我需要你啊\n[04:58.99]噢我需要你啊\n"
    },
    "code": 200
}

在[00:57.87]处的歌词前面多了个]
][00:57.87]where I belong there's something coming on.\n

建议改名，处理格式错误的LRC会panic

v4.3.2已修复


[AutoPR eventhub/resource-manager] Update eventhub management Node.js package version to 2.0.0

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3536

Closing PRs that have been open for more than 1 month.


[FIXES #106] Tooltips Icons

On hover of icons of the sidebar, you can see the tooltips what each icon signifies.
https://github.com/SUGAM-ARORA/UniCollab/assets/132436131/f5f747f4-178f-4edd-8889-51aaecab9627

@yashmandi One thing more kindly follow the template -
Fixes #IssueNumber  in description and not in the title


META6.json specifies a version for dependency as-cli-arguments

The META6.json file for this module specifies a version number for the dependency as-cli-arguments (v0.0.2), which is not the current version of that module (v0.0.4).

Argh.  Had done all the necessary changes, just forgot to upload to zef.  Now done.  Thanks for the nudge!


heasoft update

Heasoft 6.29 was released in July. I'm currently using 6.28 locally and in the github actions, but it may be worth upgrading since there appears to be a few improvements for Swift:
https://heasarc.gsfc.nasa.gov/docs/software/heasoft/release_notes.html
@mdecleir would be helpful to have you look over the specific changes for Swift if you can spot anything specific that we might want to look into switching as a part of our pipeline (e.g. improvements to uvotimage).

None of the updates seem to be crucial for our pipeline in the sense that there seem to be no bug fixes. They mainly added functionality. It looks like e.g. uvotimage is now capable of creating bad pixel maps as well, which possibly means one does not have to run the uvotbadpix function anymore. So this could maybe save one step in our pipeline. However, since our pipeline works, I would not waste too much time in figuring out the new functionalities. In the end, I think it would be good to update to the newest version before making big changes to the code, just to make sure everything is still compatible and running as expected. When you do, make sure to check the "before" and "after" output files to see if nothing changed.


Check if all array elements are pairwise co-prime or not

💥 Proposal
(A clear and concise description of what the proposal is.)
Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Check if all array elements are pairwise co-prime or not[Imp CP question in number theory]

I want to work on this issue . Please assign me with tag DWOC

I want to work on this issue . Please assign me with tag DWOC


Add url field to BaseMessageQueue

Description:
BaseMessageQueue is a Pydantic BaseModel that has no fields. Though, all of its subclasses so far have an url attribute. It's probably fair to assume at this point that all subclasses of this base class will contain url and so we should just include it in the base.

@logan-markewich @nerdai Can I work on this?

That would be great @srikary12!


Add Razvy to Contributors list

Hi  @razvan05, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

This was a very good tutorial. Thank you!

I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://goo.gl/PM1Jdh


Cannot add a Windows node

Rancher Server Setup

Rancher version: 2.6.3
Installation option (Docker install/Helm Chart): Docker
Proxy/Cert Details:

Information about the Cluster

Kubernetes version: v1.21.9+rke2r1
Cluster Type (Local/Downstream): Local

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) Admin

Describe the bug
Provision windows node get stucked on:" provisioning worker node(s) custom-acd5fa465cdb: waiting on probes: calico"
To Reproduce
Rancher server deployed in a Ubuntu Server;
Add a RKE2 cluster with all default values;
Add a Linux node;
Add a Windows 2019 (1809) with containers feature enabled
Result
At Windows EV these messages are observed for racnher-wins:
error loading system cert pool for probe (calico): crypto/x509: system root pool is not available on Windows
error loading system cert pool for probe (kubelet): crypto/x509: system root pool is not available on Windows

Add windows node worked in latest version

Can you share what you did to resolve this?

Hi, the regular steps with no additional configuration. Just used the last version of Rancher.


[Build] Set NuGet Audit Mode to Direct to revert changes made with VS 17.12

Summary of the Pull Request
Setting NuGet Audit Mode to Direct since VS 17.12 sets default mode to transitive packages. Many packages have transitive references to older System.* packages that aren't used in the build, but instead pulled in from the current .NET Runtime libraries.

PR Checklist

[ ] Closes: #xxx
[X] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed
Setting the NuGet Audit Mode back to direct, resolves build issues.
https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes-preview#nugetaudit

/azp run


Updated specgen tool to use a go module and added get service logs api call

Updated the specgen tool so it uses the newer go modules instead of godep.
I also updated the docker version imported to the latest 19.03.13.
This was tested on a fresh install of go on a new machine. All you have to do to update the models is install go, update the docker repo which is imported using go get -u github.com/docker/docker@ and then run the update-generate-code.cmd script. It downloads all of the correct dependencies, builds the program and generates the models. This has been updated in the readme for specgen.
I have also added a call to the get service logs endpoint. To do this I had to add a model which was the reason for updating the go specgen program.

This pull request can be closed when @589 is in.
The important backend changes were done in https://github.com/dotnet/Docker.DotNet/pull/480


TFLM: Adding TANH op optimized for CEVA-BX1

See github issue:  https://github.com/tensorflow/tensorflow/issues/45607

@yair-ehrenwald Can you please resolve conflicts? Thanks!

@yair-ehrenwald Any update on this PR? Please. Thanks!

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

I will open a new PR for this later on.


Provide better typings, an example and or test for decodeInstruction()

I am trying to decode serum order info directly from the blockchain history.
I think I should be able to pass a solana Instruction from the rpc directly to the exported serum function decodeInstruction()
I tried with raw TransactionInstruction from getConfirmedTransaction...
and with:
PartiallyDecodedInstruction from  getParsedConfirmedTransactions
both give an error with this stack:
 Layout.js:570 Uncaught (in promise) TypeError: b.readUIntLE is not a function
    at UInt.decode (Layout.js:570)
    at OffsetLayout.decode (Layout.js:529)
    at UnionLayoutDiscriminator.decode (Layout.js:1414)
    at Union.decode (Layout.js:1682)
    at VersionedLayout.decode (layout.js:97)
    at decodeInstruction (instructions.js:108)

it seems that instructions.decode is passing along the whole (untyped) message and later decode is expecting it to have a
readUIntLE function.

further details of the issue:

@armaniferrante said
That decodeInstruction takes in raw bytes, i.e. the "instruction data"

So rather than passing the whole instruction one needs to pass the instruction.data in as a Uint8Array of raw bytes.
In this codesandbox  i'm using basex-encoder.decodeToBuffer() to convert the  PartiallyDecodedInstruction.data (which is base58 encoded) and then passing that to the serum decodeInstruction() fx, which returns this:
newOrderV3: Object
  side: "buy"
  limitPrice: BN
  maxBaseQuantity: BN
  maxQuoteQuantity: BN
  selfTradeBehavior: "decrementTake"
  orderType: "limit"
  clientId: BN
  limit: 65535


Apply requests_params and remove from data before generating signature

Setting per-use requests_params failed and resulted in an invalid signature. This was because the signature was generated with these parameters still in data and removed them after. This fix removes the requests_params from data before generating the signature.

Coverage remained the same at 38.705% when pulling 9ff962f0421e661412c0a3cf3ec20c59e77f46c5 on ron7684:bugfix/requests_params_signature into 78a64a67cad02ca6397b0b95486b2bc830ae5ef0 on sammchardy:master.


New version: PlotlyJS v0.16.1

Registering package: PlotlyJS
Repository: https://github.com/JuliaPlots/PlotlyJS.jl
Created by: @sglyon
Version: v0.16.1
Commit: 6a2154261f2809877a4d61ccd478b70b4f9b01dd
Reviewed by: @sglyon
Reference: https://github.com/JuliaPlots/PlotlyJS.jl/commit/6a2154261f2809877a4d61ccd478b70b4f9b01dd#commitcomment-52667762

looks like the CI error here was a network error trying to download electron for Blink.jl
Perhaps we could restart the CI job?

Note that you could have retriggered the job yourself by registering again the same version


[WFLY-4850] Enabling extended cluster passivation test failed by assertion

https://issues.jboss.org/browse/WFLY-4850
There was an issue with assertion errors being thrown when server was not available at time. But it could be expected situation and check for isActive could then fail with assertion exception instead of returning a boolean.
After some fixes in wfcore this seems not happening anymore and the test could be enabled.
./integration-tests.sh clean install -Dts.noSmoke -Dts.clustering -Djboss.dist=$JBOSS_HOME -Dtest=ClusterPassivationTestCase -DextendedTests

@ochaloup Please always link the Jiras in the description, saves a lot of copy pasting. Also, the Jira is already resolved, no fix version specified... lets please keep Jira clean :-(
Moreover, this needs a special run with -DextendedTests, the current status check is misleading since the test was not run.

Started custom linux run http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=79012&tab=buildResultsDiv&buildTypeId=WFPR

Linux Build 8777 outcome was FAILURE using a merge of 3fda9e2dafa59759d5b17ad77251c0319f3cb7bb
Summary: Tests failed: 18 (18 new), passed: 3391, ignored: 373 Build time: 01:36:40
Failed tests
org.jboss.as.test.clustering.cluster.web.expiration.FineSessionExpirationTestCase(ASYNC-tcp).test: java.lang.AssertionError: null
	at org.jboss.as.test.clustering.cluster.web.expiration.SessionExpirationTestCase.test(SessionExpirationTestCase.java:186)
------- Stdout: -------
10:35:59,981 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
10:35:59,981 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
10:35:59,981 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
 [0m10:35:59,993 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-ASYNC-tcp-0/standalone/data/content/ab/8cbdd8442f4c6f37f3e303c636efafd65acbb7/content
 [0m [0m10:35:59,995 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
 [0m [0m10:36:00,029 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,030 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,031 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 83) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,032 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 83) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,033 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,033 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,076 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0002: Started expiration.war cache from web container
 [0m [0m10:36:00,094 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 8) WFLYCLINF0002: Started routing cache from web container
 [0m [0m10:36:00,132 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 8) WFLYUT0021: Registered web context: /expiration
 [0m [0m10:36:00,139 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
 [0m10:36:00,146 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
 [0m10:36:00,156 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-ASYNC-tcp-1/standalone/data/content/b1/e7b90479957b56592b20fca623eed2a8283baa/content
 [0m [0m10:36:00,163 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
 [0m [0m10:36:00,213 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 74) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,214 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 74) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,218 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 74) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,218 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 74) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,220 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,220 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m10:36:00,226 INFO  [org.infinispan.CLUSTER] (ServerService Thread Pool -- 80) ISPN000310: Starting cluster-wide rebalance for cache routing, topology CacheTopology{id=1, rebalanceId=1, currentCH=DefaultConsistentHash{ns=80, owners = (1)[node-0: 80+0]}, pendingCH=DefaultConsistentHash{ns=80, owners = (2)[node-0: 40+40, node-1: 40+40]}, unionCH=null, actualMembers=[node-0, node-1]}
 [0m [0m10:36:00,268 INFO  [org.infinispan.CLUSTER] (ServerService Thread Pool -- 74) ISPN000310: Starting cluster-wide rebalance for cache expiration.war, topology CacheTopology{id=1, rebalanceId=1, currentCH=DefaultConsistentHash{ns=80, owners = (1)[node-0: 80+0]}, pendingCH=DefaultConsistentHash{ns=80, owners = (2)[node-0: 40+40, node-1: 40+40]}, unionCH=null, actualMembers=[node-0, node-1]}
 [0m [0m10:36:00,301 INFO  [org.infinispan.CLUSTER] (transport-thread--p15-t2) ISPN000336: Finished cluster-wide rebalance for cache routing, topology id = 1
 [0m [0m10:36:00,303 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 80) WFLYCLINF0002: Started routing cache from web container
 [0m [0m10:36:00,321 INFO  [org.infinispan.CLUSTER] (transport-thread--p15-t7) ISPN000336: Finished cluster-wide rebalance for cache expiration.war, topology id = 1
 [0m [0m10:36:00,324 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0002: Started expiration.war cache from web container
 [0m [0m10:36:00,349 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0021: Registered web context: /expiration
 [0m [0m10:36:00,358 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
 [0m [0m10:36:00,396 INFO  [stdout] (default task-26) http://[::1]:8080/expiration/listener?operation=set&name=a;jsessionid=63yCOpoOw53qTxf5yt9epTsK2ORdBlBFoS3s31Tv
 [0m [0m10:36:00,411 INFO  [stdout] (default task-27) http://[::1]:8080/expiration/listener?operation=set&name=a&value=1;jsessionid=63yCOpoOw53qTxf5yt9epTsK2ORdBlBFoS3s31Tv
 [0m [0m10:36:00,452 INFO  [stdout] (default task-23) http://[::1]:8180/expiration/listener?operation=get&name=a;jsessionid=63yCOpoOw53qTxf5yt9epTsK2ORdBlBFoS3s31Tv
 [0m [0m10:36:00,491 INFO  [stdout] (default task-24) http://[::1]:8180/expiration/listener?operation=remove&name=b;jsessionid=63yCOpoOw53qTxf5yt9epTsK2ORdBlBFoS3s31Tv
 [0m [0m10:36:00,507 INFO  [stdout] (default task-28) http://[::1]:8080/expiration/listener?operation=set&name=a&value=2;jsessionid=63yCOpoOw53qTxf5yt9epTsK2ORdBlBFoS3s31Tv
 [0m [0m10:36:00,525 INFO  [stdout] (default task-25) http://[::1]:8180/expiration/listener?operation=get&name=a;jsessionid=63yCOpoOw53qTxf5yt9epTsK2ORdBlBFoS3s31Tv
 [0m [0m10:36:00,543 INFO  [stdout] (default task-29) http://[::1]:8080/expiration/listener?operation=set&name=a;jsessionid=63yCOpoOw53qTxf5yt9epTsK2ORdBlBFoS3s31Tv
 [0m [0m10:36:00,552 INFO  [stdout] (default task-26) http://[::1]:8180/expiration/listener?operation=get&name=a;jsessionid=63yCOpoOw53qTxf5yt9epTsK2ORdBlBFoS3s31Tv
 [0m10:36:00,561 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
10:36:00,561 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
10:36:00,561 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
 [0m10:36:00,565 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 82) WFLYUT0022: Unregistered web context: /expiration
 [0m [0m10:36:00,579 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000029: Passivating all entries to disk
 [0m [0m10:36:00,581 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000030: Passivated 3 entries in 1 milliseconds
 [0m [0m10:36:00,589 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0003: Stopped expiration.war cache from web container
 [0m [0m10:36:00,596 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 31ms

org.jboss.as.test.clustering.extended.ejb2.stateful.passivation.dd.ClusterPassivationDDTestCase(SYNC-tcp-extended).defineMaps:

org.jboss.as.test.clustering.tunnel.singleton.SingletonTunnelTestCase(ASYNC-tunnel).testSingletonService: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
	at org.jboss.as.test.clustering.NodeUtil.undeploy(NodeUtil.java:48)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.afterTestMethod(ClusterAbstractTestCase.java:101)
	at org.jboss.as.test.clustering.tunnel.singleton.SingletonTunnelTestCase.afterTestMethod(SingletonTunnelTestCase.java:113)
------- Stdout: -------
11:21:00,665 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
	at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.afterTestMethod(ClusterAbstractTestCase.java:100)
	at org.jboss.as.test.clustering.tunnel.singleton.SingletonTunnelTestCase.afterTestMethod(SingletonTunnelTestCase.java:113)

11:21:00,728 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
	at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.afterTestMethod(ClusterAbstractTestCase.java:100)
	at org.jboss.as.test.clustering.tunnel.singleton.SingletonTunnelTestCase.afterTestMethod(SingletonTunnelTestCase.java:113)

11:21:00,732 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.deploy(ClusterAbstractTestCase.java:115)
	at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:37)
------- Stdout: -------
11:21:03,617 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
	at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.start(ClusterAbstractTestCase.java:107)
	at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:36)

11:21:03,686 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
	at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.start(ClusterAbstractTestCase.java:107)
	at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:36)

11:21:03,691 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-2
11:21:03,703 WARNING [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Bundles path is deprecated and no longer used.
11:21:03,704 INFO  [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/usr/java/latest/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -Djboss.dist=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../../../dist/target/wildfly-10.0.0.CR5-SNAPSHOT, -Djboss.dist=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../../../dist/target/wildfly-10.0.0.CR5-SNAPSHOT, -Djava.net.preferIPv6Addresses=true, -server, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=::1, -Dmcast=ff13::1, -Dmcast.ttl=0, -Djbossas.ts.submodule.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering, -Djbossas.ts.integ.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/.., -Djbossas.ts.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../.., -Djbossas.project.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../../.., -Djboss.inst=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0, -Djboss.node.name=NYC-0, -Djboss.port.offset=200, -ea, -Djboss.home.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0, -Dorg.jboss.boot.log.file=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/standalone/log/server.log, -Dlogging.configuration=file:/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/standalone/configuration/logging.properties, -jar, /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/jboss-modules.jar, -mp, /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/modules:/opt/buildAgent/work/a31d203e70e89f90/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules:/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/modules, org.jboss.as.standalone, -Djboss.home.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0, -Djboss.server.base.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/standalone, -Djboss.server.log.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/standalone/log, -Djboss.server.config.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/standalone/configuration, -Dts.wildfly.version=10.0.0.CR5-SNAPSHOT, -c=standalone-ha.xml]
11:21:03,798 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
11:21:03,866 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
11:21:03,907 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.14.Final
 [0m11:21:04,362 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
 [0m [0m11:21:04,623 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
 [0m [0m11:21:04,731 INFO  [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Full 10.0.0.CR5-SNAPSHOT (WildFly Core 2.0.1.Final) starting
 [0m [0m11:21:06,322 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 22) WFLYCTL0028: Attribute 'stack' in the resource at address '/subsystem=jgroups/stack=tcp/relay=relay.RELAY2/remote-site=LON' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m11:21:06,323 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 22) WFLYCTL0028: Attribute 'stack' in the resource at address '/subsystem=jgroups/stack=tcp/relay=relay.RELAY2/remote-site=SFO' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m11:21:06,483 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m11:21:06,509 INFO  [org.xnio] (MSC service thread 1-3) XNIO version 3.3.2.Final
 [0m [0m11:21:06,517 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.3.2.Final
 [0m [0m11:21:06,565 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.14.Final
 [0m [0m11:21:06,623 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
 [0m [0m11:21:06,682 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
 [0m [0m11:21:06,686 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m11:21:06,729 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 45) WFLYCLJG0001: Activating JGroups subsystem.
 [0m [0m11:21:06,765 INFO  [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.1.Final)
 [0m [0m11:21:06,768 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [0m11:21:06,823 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m11:21:06,835 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem
 [0m [0m11:21:06,850 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m11:21:06,868 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension
 [0m [33m11:21:06,901 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
 [0m [0m11:21:06,900 INFO  [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
 [0m [0m11:21:06,899 INFO  [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=4.9.3.Final

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeExecutionDisabledTestCase: To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.remotecall.RemoteLocalCallTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.remotecall.RemoteLocalCallProfileTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase.testRemoteServerRestarts: 	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
	at org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase.testRemoteServerRestarts(RemoteOutboundConnectionReconnectTestCase.java:201)
------- Stdout: -------
11:21:28,230 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
11:21:28,284 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
11:21:28,315 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.14.Final
11:21:28,941 WARN  [org.jboss.remotingjmx.Util] (main) The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'.

##### there are 8 more failed tests, see build details

@rhusar: long time that I haven't been adding any pull request...
I see, I've added link to description but now it's probably late :)
My intention here was to enable test which could be run (if somebody would like to run extended ones).
This PR only enable test not fixing anything. I have no control over WFLY-4850. This should be done by asignee. I can only confirm that trouble that I have was fixed sometime during WFLY 10 development and in CR4 it's ok and test is passing.

Testing with -DextendedTests at https://ci.wildfly.org/viewLog.html?buildId=16039&tab=buildResultsDiv&buildTypeId=WF_MasterIgnoreLinux and https://ci.wildfly.org/viewLog.html?buildId=16039&tab=buildResultsDiv&buildTypeId=WF_MasterIgnoreLinux

^ @bstansberry those are the same link twice :-)

Not any more!

retest this please

Just one more retest this please to verify all is good.

@jamezp The retest won't test this. These tests are in "extended" package which is only run if -DextendedTests parameter is provided to the testsuite run (see Brian's build configuration).

Ah yes. It helps to fully read comments eh? Thanks @rhusar. It looks like the runs Brian linked did not go so well.

Although I don't see ClusterPassivationTestCase failing, but I don't see it neither when I click "Tests" and filter by ClusterPassivationTestCase...

@bstansberry @jamezp Ah, I just realized this is not going to work since running the testsuite with extended flag will always take longer than maximum configured timeout in our regular jobs... we need test this branch using this job we have setup https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxExtendedClustering which has increased timeout to deal with this.
[ERROR] There was a timeout or other error in the fork

@ochaloup As this pull request has  been held up for a long time, I am closing it to get the pull request queue under control again. Since this is very old now, it will be a very long time until this one will be addressed. Also, I don't have much time to spend on this to evaluate on a case by case basis.
If this is something important to you or the project please feel free to recreate the pull request. That way it will come on top of the pile again, and be looked at again sooner.
If it is a new feature, please follow the new process for features. Ping @kabir or @jamez if you are unsure what this means, and we can help. Please do that before opening the pull request though.
Sorry for any inconvenience!


Question: Error trying to connect to MongoDB on Amazon EC2

Anyone knows what could be causing this? "Failed to connect to: http:0: php_network_getaddresses: getaddrinfo failed: Name or service not known"
Thanks

We can' help you with so few informations. I currently use MongoDB on EC2 with no problem.
Where your MongoDB instance is located (same instance, other instance, other service like MongoLab...) ? Have you properly installed and configured the php-mongo and the mongodb packages (check php-info) ?


Feature: Alert components with icon support

Problem:
There are no components for warning, error, info, etc. We might be using these components on multiple pages. So, having these components in the DCX library will be quite useful.
Additional details:
For example, On importing the warning component should render the warning icon with the warning message.
Ex:

hi @dilipkumarindla can you please provide a visual example on how the component should render please? it's a modal or a toaster or something different?

hi @daniele-zurico - Below is the screenshot for the info example. The component should render text that is in bold and has an icon on the left side.

but this one is a pure css component, it doesn't have any logic/behaviour.
I suppose you can achieve that one saying:

text

Am I missing something?

Hi @daniele-zurico  -  I am referring  to this page https://design-system.service.gov.uk/components/warning-text/
So, we are using the warningtext component at multiple places, so thought of suggesting this component be added in the dcx-react library as well to achieve a similar look and for code re-usability.
Yes, I agree with your approach. However, considering reusability suggested including this feature. If you think that it is not required, we can close this ticket.


ghactions: Automatically create gh releases

This commit uses the 'gh' command line tool to create a new draft github
release and upload the gvproxy* binaries to it.
It's triggered on v* tag pushes.

/lgtm
/approve


Allow google sign in oauth

This allows authentication via google sign in oauth which prevents an end user from having to input his google account credentials. Instead, the user is redirected to GoogleSignInAuth.LOGIN_URL where they are given a code to copy and paste into the application.
Unfortunately the existing PGoAuth protocol doesn't completely make sense for this implementation. The login method takes a username, password but in this case only one string argument is needed for the login code. In order to conform to the existing protocol, I've simply used the password argument to pass the code, and the username argument is ignored. This isn't ideal, obviously, but it works.

Thank you for this. I am going to merge this and change the name to something like GPSOAuth2 and edit a few things. I'll edit the protocol as well.

yes that's okay with me. This is also what I was trying to accomplish with https://github.com/lsapan/pgoapi-swift/issues/45 so it probably makes sense to make loginOAuth private again.

Thanks! This should be resolved now.


Don't let FormData stop iterating when there is an empty value.

Resolves https://github.com/YOCKOW/SwiftCGIResponder/issues/71

Crashes on Ubuntu...
Why..?

I'll refactor TemporaryFile.


Update reveal.js from v4.2.1 to 4.3.0

Please see changelog of reveal.js
Auto-generated by GitHub Actions

NOTE: Use #95


Balloon - really long messages are garbled

gol's Balloon regular size message box is not big enough to fit messages length past some longish threshold. Balloon should be capable of expanding horizontally to fit almost an arbitrary size message. i would rather keep vertical size constant for messages of all lengths for visual aesthetics.

e-mailed a screenshot to you

ok, I saw it.
I'll look into it later.


Command Line Usage?

Is there a way to use this with the command line instead of the Notebook software?

Not yet. It should not be very difficult to write a CLI, though.

What about taking the CLI from this: https://github.com/kesara/deepdreamer and using it on your modified code? I have done it with deep dream itself, but not with a modified tile system.

I ran $ ipython nbconvert --to python deep_dream.ipynb to convert it to a python script. But now I get the following error:
ubuntu@ip-Address:~/deep_dream$ python deep_dream.py
Traceback (most recent call last):
  File "deep_dream.py", line 12, in <module>
    import deep_dream
  File "/home/ubuntu/deep_dream/deep_dream/__init__.py", line 1, in <module>
    from .deep_dream import CNN, EPS, ShapeError, call_normalized, normf, save_as_hdr, to_image
  File "/home/ubuntu/deep_dream/deep_dream/deep_dream.py", line 8, in <module>
    from pathlib import Path
ImportError: No module named pathlib
ubuntu@ip-Address:~/deep_dream$


Refactor Keywords to query Contentful

What's this PR do?
Upon passing a keyword, the chatbot router now queries the Contentful keyword type to find the campaignId associated with it, instead of inspecting the app.locals.keywords cache, which is populated from the campaigns documents for ids set in CAMPAIGNBOT_CAMPAIGNS
This is a big step toward easier configuration: to enable a Campaign for Gambit, add the Keyword and its Campaign ID into Contentful (and add the Keyword on the Mobile Commons mData) -- and the Campaign is live on Gambit. To override Campaignbot messages and/or populate the Campaign's Messaging Group ID's , we still do need to add the ID to CAMPAIGNBOT_CAMPAIGNS to populate the Mongo document -- so we're not out of the woods with the config variable and app restart just yet.
TODO:

[x]  Support the {{keyword}} token in CampaignBot.renderMessage -- so we need to add a getKeywordsForCampaign function to lib/contentful
[x] Call the getKeywordsForCampaign function in the campaigns endpoint
[x] Remove the keywords property from the Campaign model, and all use of app.locals.keywords

How should this be reviewed?
Opening this for now to help keep reviewing easier.
Any background context you want to provide?
Not ready for merge yet -- more changes on the way.
Relevant tickets
#775
Checklist

[ ] Documentation added for new features/changed endpoints.
[ ] Add all staging keywords+campaigns into Contentful
[ ] Tested on staging.
[ ] Add all production keywords+campaigns into Contentful

@sergii-tkachenko This is ready for a part 2 when you have a chance.  All items in the TODO have been completed, and about to start testing on Thor.
I decided to add a environment property to the Contentful keyword content type to keep implementation simple, instead of spinning up a whole new Contentful space that would be trickier to keep synced with content type structure:

I'll be testing this branch on Thor, and start updating the Gambit wiki instructions for chatbot maintenance upon merge.

I've added the production keywords/campaigns as well, in anticipation of releasing this next week.


Add support for user_id in authorizes and report

Fixes #56

Travis CI failing because the build in master is broken, it's unrelated to this PR. #58 fixes the build.

Rebased on top of master after merging #58


Fixing maps and cellmaps

Codecov Report

Merging #11 into master will increase coverage by 0.38%.
The diff coverage is 72.64%.

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
+ Coverage   72.18%   72.57%   +0.38%
==========================================
  Files          35       35
  Lines        1323     1360      +37
==========================================
+ Hits          955      987      +32
- Misses        368      373       +5

Impacted Files
Coverage Δ

src/CellValues/CellValues.jl
100% <ø> (ø)
:arrow_up:

src/Numa.jl
100% <ø> (ø)
:arrow_up:

src/Maps/Maps.jl
100% <ø> (ø)
:arrow_up:

src/Maps/AbstractMaps.jl
57.14% <0%> (ø)
:arrow_up:

src/Maps/AnalyticalField.jl
62.5% <0%> (ø)
:arrow_up:

src/CachedArrays.jl
100% <100%> (ø)

src/CellValues/Operations.jl
86.89% <100%> (+3.77%)
:arrow_up:

src/Maps/Operations.jl
67.81% <68.67%> (+3.53%)
:arrow_up:

src/Maps/Composition.jl
82.6% <91.66%> (-2.4%)
:arrow_down:

src/Polynomials.jl
94.36% <0%> (+1.31%)
:arrow_up:

... and 1 more

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 6d09fe2...eeb203a. Read the comment docs.


Data classification: Symbol ":" is missing in the training result on the Train page.

System Information (please complete the following information):
Windows OS: Windows-11-Enterprise-21H2
ML.Net Model Builder 2022: <IP_ADDRESS>1301 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.3.6)
.Net: 6.0
Describe the bug

On which step of the process did you run into an issue:
Symbol ":" is missing in the training result on the Train page for Data classification scenario.

Data Source
https://testpass.blob.core.windows.net/test-pass-data/wikipedia-detox-250-line-data.tsv
https://testpass.blob.core.windows.net/test-pass-data/issues.tsv.txt
https://github.com/dotnet/machinelearning-samples/raw/main/samples/modelbuilder/MulticlassClassification_RestaurantViolations/RestaurantScores.zip
To Reproduce
Steps to reproduce the behavior:

Select Create a new project from the Visual Studio 2022 start window.
Choose the C# Console App (.NET Core6.0) project template.
Add model builder by right click on the project.
Select Data classification scenario.
On Data page, select the data source and choose Sentiment column as label.
On the Train page, click "Start training" button to complete the training. (The default Metric is "Macro-Accuracy")
You will see that symbol ":" is missing in the training result.

Expected behavior
Symbol ":" should be displayed normally.
Screenshot

The bug has been fixed on the latest main build: <IP_ADDRESS>2402

@v-Hailishi Can you start doing something new? When you validate a bug you've filed as fixed please close the bug too. Thanks!


CPU hits illegal instruction signal on older hardware

I installed Japronto on OSX via setup.py, and attempted to run the hello world example. The example threw an error when I tried to connect to it via my browser or wrk. The error message was
Worker exited with code -4!
Note:
I am using a 2010 Macbook pro with Sierra, and received this error straight from the fresh git clone. The installation ran fine but I received a few warnings about uvloop.

a similar error,
ubuntu 16.04
all required libraries are updated
Worker exited with code -4!

OK, signal 4 means illegal instruction (CPU encountered an instruction that it doesnt know). Is it possible that your computer doesnt have SSE 4.2 extensions. What is your CPU model?
@Superman132 I think the first Macbook to support SSE 4.2 is from 2011
@wku can you provide cat /proc/cpuinfo
This should be fixed, the plan:

first Japronto should warn if the host CPU doesnt have SSE 4.2
second Japronto should provide slow path for old hardware without using SSE 4.2

@Superman132, @wku I tried to address the problem. Can you try the version from this pull request? https://github.com/squeaky-pl/japronto/pull/40
Be sure that you removed previous version and checked out right branch in git (sse-fallback2)

After trying your branch, I experienced an error at installation
python3 setup.py install
yields the following error
src/japronto/parser/cparser.c:747:5: error: use of unknown builtin '__builtin_cpu_init' [-Wimplicit-function-declaration]     __builtin_cpu_init();     ^ 1 error generated. error: command 'clang' failed with exit status 1'

@Superman132 yes, I need to find a clang counterpart of that functionality. A clang expert on the team would help.

@Superman132 I updated the code to include a clang version, can you retry?

cpuinfo.txt

@wku Yes, that CPU is missing SSE 4.2 extensions. @wku can you try uninstalling the version you have and try with:
pip3 install git+git://github.com/squeaky-pl/japronto.git@sse-fallback2

Yes,
this version works,
and issues a warning

Warning: Host CPU doesnt support SSE 4.2, selecting slower implementationAccepting connections

wrk -c 100 -t 6 -d 60 http://localhost:8080
Running 1m test @ http://localhost:8080
6 threads and 100 connections
Thread Stats   Avg      Stdev     Max   +/- Stdev
Latency   765.45us    1.38ms  40.23ms   91.54%
Req/Sec    36.21k     8.52k   70.99k    58.00%
12982360 requests in 1.00m, 1.11GB read
Requests/sec: 216022.62
Transfer/sec:     18.95MB

@wku that's not bad at all for a non-pipelined benchmark. Close to what you can do on a modern Intel i7 processor with SSE 4.2.

yes I agree, OK

Sorry about keeping this thread alive, but I just tried the sse-fallback2 branch and tried to install via clang.
It gave the following error
src/japronto/cpu_features.c:11:16: error: use of undeclared identifier       'bit_SSE4_2'   return ecx & bit_SSE4_2;                ^ 1 error generated.
This same error occurred on master branch also.

@Superman123 thanks for trying this out. This is another difference between clang and gcc. I think I finally got it right and upcoming 0.1.1 should work.

@Superman123 0.1.1 is out, please pip install japronto. It should get you a warning about missing SSE 4.2 but continue working.

Thanks everyone, The latest japronto release seemed to work as expected on my MacBook. I am closing this issue.


Figure out why builds of next branch are failing

For example, this build failed from https://github.com/palantir/tslint/pull/1162, whereas this build from https://github.com/palantir/tslint/pull/1163 worked fine as expected.
There's something weird going on with NPM dependency requirements that's causing the problems of these failing builds, but not sure what it is yet.

Problem was caused by CircleCI caching installed node modules from old builds. Running the build with a cleared cache fixed the issue.


ntr phrynoderma issue #773

Addition of term phrynoderma, more information in issue #773

@cmungall I resolved the conflicts, this should be ready to merge


Issue 62620 - fix unit test with Ubuntu 2020 LTS bzr 3.0.2

testdata/vcstest/bzr: fix unit test with Ubuntu 2020 LTS bzr 3.0.2
As pointed by @bcmills, upstream fixed this in 3.1.0 in https://github.com/breezy-team/breezy/commit/30143860ced0ad9f42cbf18a119f2800117decff
Fixes #62620.

Wrong base commit. My apologies.


Addition Radar sensor LP 2410

Hello, will you be able to add the LD 2410 sensor for the realization of radar for static people.
Thank you for your work.
https://www.hlktech.net/index.php?id=988

It would even be useful in the premium version.

As I see, this sensor has an output with HIGH (occupied) and LOW (unoccupied). So, you can connect it to PTVO as a regular presence sensor:
https://ptvo.info/zigbee-configurable-firmware-features/diy-examples/diy-zigbee-motion-detection-sensor-pir/

I agree, but it is not possible to change LD2410 parameters such as sensitivity, range, etc :-(

Indeed, the great interest is to be able to read the movement distance, static as well as the detection distance.

@Wielebny666 This sensors requires a proprietary program to change sensor settings via UART.

I know, but when the sensor is mounted in a case, e.g. under the ceiling, this is an inconvenient solution.
The ESPHome project includes full support for this sensor via UART.


Add support for Nuxt folder

References #650
Changes proposed:

[x] Add
[ ] Delete
[ ] Fix
[ ] Prepare

Could the folder color get a little lighter?

A color change of the closed folder icon pending.

Need to re-install my editing software, not sure If I would make it before new year eve 🙈

After testing with several green tones I think it's better to take the blue-gray color as a base:

The problem is not completely solved, as the line of the icon is really thin and not enough thick to get noticed in a clear way.
Making the green lighter is not enough to make the great triangle visible. Darker works better for that triangle.
Let me know what do you think.

@robertohuertasm Maybe we could slightly increase the thickness of each triangle in order to improve readability. I do feel like any folder color couldn't satisfy at all both dark and light versions with smaller lines as this icon does.

I tested it and it wasn't really good either... I'll keep this PR and the one for PERL (#2305) for the next release when we all come back from Christmas holidays so we can discuss it.
In the meantime I'll prepare the changelog and prepare for the last 2019 release.

@vscode-icons/development I'll have a look at this today.

Doing various tests the only solution is to add an outline on the nuxt icon to make it more distinguishable. @KingDarBoja can you take of it?

@JimiC Okie dokie, a white outline should do the job. I will get some free time to submit the new version today.

I would have done it myself but had to leave work early today


Fix build path output, and Demo Apps Ref path import and Output

Remove hard-coded directory offsets for Component outputs
Use offset location for components in Demo Apps
Remove Release GAC'ing
Fix explorer for the copied target names

Peter,
You will probably need to rework the installer, if you have included the demo apps, as their locations are now different.

Ok, I'll build all of the solutions. Might be released tomorrow.


"Tumblr account" section does not support long usernames

I wanted to add my tumblr in the appropriate section, but then I found out that my username (NOT url) was 21 characters, exactly 1 longer than the maximum you allow. Considering also that the maximum for a username on tumblr is 32 characters, it might be wise to reconsider the maximum of characters you allow, because the whole "tumblr" section is kinda pointless otherwise...
Thanks.

I updated the limits for the social links: https://github.com/SchoolIdolTomodachi/SchoolIdolAPI/commit/5ccc145f734e7557c65d08cf0c3140ee0438f46f
Thanks for reporting!


Problem with Windows-EFLOW folder sharing

Describe the Problem
Can't share Windows folder with EFLOW VM
To Reproduce
Below is the script I use to create folders, sharedFolder.json file, and eventually share the folder with EFLOW VM
# Enabling Windows folder share
Write-Host "Enabling Windows-EFLOW folder sharing"
$jsonData = @"
[
    {
        "sharedFolderRoot": "C:\\OpenVPN\\EFLOW-Shared",
        "sharedFolders": [
            {
                "hostFolderPath": "Certificates",
                "readOnly": false,
                "targetFolderOnGuest": "/etc/aziot/EFLOW-Shared/Certificates"
            }
        ]
    }
]
"@

$RootFolderPath = "C:\OpenVPN\EFLOW-Shared"
$CertificatesFolderPath = "C:\OpenVPN\EFLOW-Shared\Certificates"
$sharedFoldersJson = "sharedFolders.json"
$sharedFoldersJsonFilePath = Join-Path -Path $RootFolderPath -ChildPath $sharedFoldersJson

if (-not (Test-Path -Path $CertificatesFolderPath -PathType Container)) {
    New-Item -Path $CertificatesFolderPath -ItemType Directory | Out-Null
}

$jsonData | Set-Content -Path $sharedFoldersJsonFilePath -Force

Add-EflowVmSharedFolder -sharedFoldersJsonPath $sharedFoldersJsonFilePath

However, I face the following error:
Enabling Windows-EFLOW folder sharing
 - Creating container - (EflowStorageContainerbfe3938d-6a8d-46e3-9161-9b0a733fe678)
 - Creating storage sharedfolders under root (C:\OpenVPN\EFLOW-Shared)
 - Did not find any matching sharedfolders!

[09/08/2023 09:10:04] Exception caught!!!

 - C:\Program Files\Azure IoT Edge\nodectl.exe  storage sharedfolder create --config "C:\Program Files\Azure IoT Edge\\yaml\cloudsf-EflowStorageSharedFolder803abb60-
607d-46f7-94ae-5d45a937350a.yaml" failed to execute [E0908 09:10:03.218823    8872 wssd.go:55] [SharedFolder] Create failed with error rpc error: code = Unknown desc
 = Not Supported Error: rpc error: code = Unknown desc = Not Supported] at line 4349
C:\Program Files\Azure IoT Edge\nodectl.exe  storage sharedfolder create --config "C:\Program Files\Azure IoT Edge\\yaml\cloudsf-EflowStorageSharedFolder803abb60-607
d-46f7-94ae-5d45a937350a.yaml" failed to execute [E0908 09:10:03.218823    8872 wssd.go:55] [SharedFolder] Create failed with error rpc error: code = Unknown desc =
Not Supported Error: rpc error: code = Unknown desc = Not Supported]

Below is the screenshot of folders:

Expected behavior
Folders get shared
Windows Host OS (please complete the following information):

Windows Server 2019 with latest updates

Additional context
Latest version of IoT Edge Eflow has been installed.

@fcabrera23
Any plans to add support on Windows Server?
Given that this is currently not possible , what is the recommended way to recursively copy a directory from the host to EFLOW?


Start menu configurations not saving on restart

Excellent script by the way and thanks for sharing. I did run into an issue with my configurations in the start menu not saving on a restart right after running the script. However the following steps I found on stack exchange fixed the problem. Maybe we can integrate these steps into the script?

Open Regedit
Open Running Processes and end Explorer.exe (don't restart it yet),
Delete the key with Regedit
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore
Start Explorer.exe again
Restart machine

I can certainly add this in. I will do it this weekend.

This has been completed.


Post quantity without LinkedIn restrictions

Hi there,
Have you found the specific limitations of scraped post quantity before accounts get restricted?
I get restrictions after around 4-5x50 scraped posts and want to avoid getting hit again.
Cheers,
Paul

Hi Paul,
To avoid restrictions, you should add time between requests, using random intervals. or rotating IPs


Sidebar: allow list of feeds to be sorted

Initially by name, but also by date of most recent update.

NNW 3 (and 2 IIRC) had the ability to sort subscriptions/feeds by by unread count. This was my preferred mode.

This ticket includes manual sort order as an option, not just sorting by other criteria.


manual scan button in tray menu

Just in case.
Would be a good workaround for issues like #2

https://github.com/Julusian/companion-remote/releases/tag/v0.2.0


remove warning from yamllint

https://github.com/istio/istio/issues/15334

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: irisdingbj
To complete the pull request process, please assign douglas-reid
You can assign the PR to them by writing /assign @douglas-reid in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

bin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn, irisdingbj
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

bin/OWNERS [howardjohn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@irisdingbj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-new-install-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-new-install-k8s-presubmit-tests-master

prow/racetest.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-racetest-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-new-install-k8s-presubmit-tests-master

prow/racetest.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-racetest-master

prow/integ-mixer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-racetest-master

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-mixer-k8s-presubmit-tests-master

prow/racetest.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-racetest-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-mixer-k8s-presubmit-tests-master

prow/racetest.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-racetest-master

prow/codecov.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-codecov-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-mixer-k8s-presubmit-tests-master

prow/racetest.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-racetest-master

prow/codecov.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-codecov-master

prow/integ-new-installer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-new-install-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/racetest.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-racetest-master

prow/codecov.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-codecov-master

prow/integ-new-installer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/codecov.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-codecov-master

prow/integ-new-installer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-mixer-k8s-presubmit-tests-master

prow/racetest.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-racetest-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-mixer-k8s-presubmit-tests-master

prow/racetest.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-racetest-master

prow/codecov.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-codecov-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-racetest-master

/test istio-codecov-master

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test integ-mixer-k8s-presubmit-tests-master

prow/racetest.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-racetest-master

prow/codecov.sh
46af290f39f642707a440786bd6904d641daeb6b
link
/test istio-codecov-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-codecov-master


Increase Fuzz Coverage for mvc_dec_fuzzer.cpp

Enhanced mvc_dec_fuzzer.cpp to improve fuzz coverage by adding varied input cases, improving error handling, implementing structure-aware fuzzing, and utilizing mutation-based fuzzing.

Hii @harishdm Could You please Review This PR
Thanks

Hii @harishdm Could You please Review This PR again i had comited changes
Thanks

kMaxNumDecodeCalls is chosen based on the runtime requirements for the fuzzer etc and there are no plans of increasing this.
At this point, I do not see why this change is needed.


[Security] Overview of Rootkits

Topic Suggestion
Proposed title of article
Overview of Rootkits
Proposed article introduction
Security and privacy have nearly become myths in this digital age of computers and technology. As much as data has become crucial, its protection has become even more valuable. Today, securing our data and information is our top priority. There are numerous ways for someone to get unauthorized access to our systems and steal the data. Rootkits are one such method.
Rootkits are malicious software that targets the operating system, firmware, or various system applications in order to gain root privileges. They have the ability to go undetected by the system and deploy various malware that allows them to steal data.
Key takeaways

Understand what are rootkits
What makes them vulnerable
How they affect our system
How they can be used to improve existing systems
Different types of rootkits

Article quality
This article provides a quick overview of rootkits and gets the reader started. It is intended for beginners and anyone interested in learning more about one of the many topics in cybersecurity. The types of rootkits, how they function, how to detect and avoid them, and so on should be able to help them comprehend the type of threat that exists that one might face in the future.
References
https://en.wikipedia.org/wiki/Rootkit
https://www.kaspersky.com/resource-center/definitions/what-is-rootkit

Approved but be sure to include plenty of detail to make your article more substantial over existing ones.

Closed #5432 via #5920


Kate/gis classes

Description & motivation
Receive Topography from QGIS as a correct Revit Topography category
Changes:

Adding GisTopography class
Adding a conversion from GisTopography to RevitTopography
Adding a function to clean Speckle Mesh from duplicate points as required for RevitTopography (only detects (x,y,z) duplicates, not (x,y) )

To test: https://speckle.xyz/streams/17b0b76d13/commits/d0dc6b87a3

Can we just use or extend the https://github.com/specklesystems/speckle-sharp/blob/main/Objects/Objects/BuiltElements/Topography.cs class instead?

Class extension is ok, should the Partial class ConvertGisTopography also merge with ConvertTopography?


Add context option for child views like in NestedView

Why you don't added context option binding for child views like in your NestedView plugin for Backbone ?
Example:
{{#each models}}
{{view "myChildView" context=this}}
{{/each}}

+1 on this.


[derive] Improve IntoBytes error messages

On Rust toolchains 1.78.0 or later, use
#[diagnostic::on_unimplemented] to improve the error message emitted when IntoBytes is derived on a type with inter-field padding.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 88.79%. Comparing base (fcb0b32) to head (a0f7422).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1712      +/-   ##
==========================================
- Coverage   88.98%   88.79%   -0.20%
==========================================
  Files          16       16
  Lines        5830     5843      +13
==========================================
  Hits         5188     5188
- Misses        642      655      +13

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


Made _GetInputByPath in closurebuilder.py use os.path.realpath.

A problem occured if 'closurebuilder.py' was run with relative path inputs
and the sources were absolute paths with symlinks within. 'os.path.abspath'
always resolves symlinks in the stem it adds to a relative path even though
it doesn't ever resolve symlinks for absolute paths.
The solution was to use 'os.path.realpath' instead which resolves all
embedded symlinks, providing an apples-to-apples comparison.

Hi -- we need a CLA to be able to take this patch. We have no record for "camio"
See https://cla.developers.google.com

Hi -- There should be a CLA on file for all of Stellar Science. Is there any other information you need?

sorry, I do not see a CLA for Stellar Science.

Sorry, my bad. I have it.


Copy edit guide notebooks 00-01

Note this is a work in progress to show I'm currently working through the notebooks I was assigned to copy edit.
Finished

notebook 01.05 calibration overview still contains a note to self and seems to be missing a summary line at the end, perhaps it's not finished? I also noticed there are no notebooks 01.01 and 01.02.

I've finished copy editing notebooks 00-01: see previous comments regarding specific notebook questions.


ARROW-1096: [C++] CreateFileMapping maximum size calculation issue

@wesm , have updated changes, thanks!

This test takes about 5 seconds to run on my machine with a very fast flash drive, so I don't think we should run it by default. Can you add DISABLED_ to the test name per https://github.com/google/googletest/blob/master/googletest/docs/V1_7_AdvancedGuide.md#temporarily-disabling-tests? We can always run the test with io-file-test --gtest_also_run_disabled_tests

@wesm , okay, sure, have updated the test to be disabled by default, thanks

Appveyor build here https://ci.appveyor.com/project/MaxRisuhin/arrow/build/1.0.80. +1, thanks @MaxRis!


Terraform 0.14 upgrade

what

Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

Support Terraform 0.14

/test all

/test all

/test all

/test all

/test all

/test all


Update Localizable.legal.strings to correct button text [EXPOSUREAPP-5139]

Description
Adapted button in legal text to fit to actual button on UI (activate exposure logging)

Fixes https://github.com/corona-warn-app/cwa-app-ios/pull/2080


 welcomes user with 'undefined' text value (only for object subproperties)

Description
An undefined value, when binding to <textarea>,  is treated as 'undefined' text, but only if it appears in an object subproperty.
Interestingly null gets treated just fine. undefined in a flat property is also just fine.
<input type="text"> doesn't have the issue.
See the live demo.
Live Demo
http://jsbin.com/xukejamegi/edit?html,output
Expected Results
It should work like <input type="text">
Actual Results
The user value is an 'undefined' text.
Browsers Affected

[x] Chrome
[x] Firefox
[x] Edge
[x] Safari 9
[x] Safari 8
[x] IE 11

Versions

Polymer: v1.9.1, v2.0.0 (we are using 1.9.1 - please do try to fix 1.X)
webcomponents: 0.7.24

For native HTML elements, you should use value$ for bindings instead of value: https://www.polymer-project.org/2.0/docs/devguide/data-binding#anatomy-of-a-data-binding

@TimvdLippe Using $value can't work with <textarea> because there isn't such an attribute.
If this was static HTML, you'd pass the value <textarea>here</textarea> but this doesn't work with binding.
Rather exists a value property though and binding to it is the Polymer prescribed pattern

@slawomir-brzezinski-at-interxion Oh sorry I missed that. Yeah seems like a bug.

Thanks for the issue. Interesting that it's the first bug report we've had of this, even though Polymer 1.0 would have suffered from the same issue.
At any rate, we avoid this for <input>.value only because there's an explicit special-case check for that exact case in the binding code: https://github.com/Polymer/polymer/blob/master/lib/mixins/property-effects.html#L601
Since we've already got precedent for special-casing input, I think we'd just add an || node.localName ==  textarea' to the condition and fix the bug.

Thanks for fixing this guys.
@azakus does this fix 1.X at all?


Log Android Buttons (Globally) for Crashlytics User Metrics

Need to monitor all back presses globally, for all activities, requiring me to extend AppCompatActivity
Solution http://stackoverflow.com/questions/24781130/use-a-service-for-a-global-onbackpressed-override

Additional info: https://docs.fabric.io/android/answers/answers-events.html


Update link to tenant example json

Minor typo corrections found when reviewing process - fixes #3

@timroster Thanks for your feedback and fix!


NetBox 400 status reason: {"type":["0 is not a valid choice."]}

Getting this error when trying to import:
2020-02-04 10:39:27,978 [DEBUG] Received HTTP Status 200.
2020-02-04 10:39:27,979 [DEBUG] NetBox GET request OK; returned 200 status.
2020-02-04 10:39:27,980 [INFO] Netbox virtual_interfaces 'vNIC0' object not found. Requesting creation.
2020-02-04 10:39:27,980 [DEBUG] Sending POST to 'https://netbox.xxx.dev/api/virtualization/interfaces/' with data '{'virtual_machine': {'name': 'T-114-270-026'}, 'type': 0, 'name': 'vNIC0', 'mac_address': 'XXXXXXXXXX', 'enabled': True, 'tags': ['Synced', 'vCenter', 'p-114-288-001']}'.
2020-02-04 10:39:28,028 [DEBUG] Received HTTP Status 400.
2020-02-04 10:39:28,029 [WARNING] NetBox failed to create virtual_interfaces object. A duplicate record may exist or the data sent is not acceptable.
2020-02-04 10:39:28,030 [DEBUG] NetBox 400 status reason: {"type":["0 is not a valid choice."]}
2020-02-04 10:39:28,030 [DEBUG] Unaccepted request data: {'virtual_machine': {'name': 'T-114-270-026'}, 'type': 0, 'name': 'vNIC0', 'mac_address': 'XXXXXXXXXX', 'enabled': True, 'tags': ['Synced', 'vCenter', 'p-114-288-001']}
2020-02-04 10:39:28,031 [DEBUG] Sending GET to 'https://netbox.xxx.dev/api/virtualization/interfaces/?virtual_machine=T-114-270-061&name=vNIC0' with data 'None'.

Hello @Razmuzh! What version of NetBox are you using? I suspect there has been a recent change to the interface type definitions which I'll need to account for. Would you please confirm? Thanks!
NetBox v2.6.12

NetBox v2.7.3

I have NetBox v.2.7.1.
# Interfaces
#

class InterfaceTypeChoices(ChoiceSet):

    # Virtual
    TYPE_VIRTUAL = 'virtual'
    TYPE_LAG = 'lag'

    # Ethernet
    TYPE_100ME_FIXED = '100base-tx'
    TYPE_1GE_FIXED = '1000base-t'
    TYPE_1GE_GBIC = '1000base-x-gbic'
    TYPE_1GE_SFP = '1000base-x-sfp'

Is it a day to get around it?
Thanks!
R.

Thanks for confirming. It's not a huge deal. I'll work on updating for NetBox v2.7 API and report back when it's ready for testing.

@Razmuzh - I think think I've got a backwards compatible solution that will support Netbox API v2.7. Would you mind testing the latest commit in the  50-interface-type-updates branch? Thanks!

Passed all functional tests in NetBox v2.6.12 and NetBox v2.7.2 on my side.

Passed regression testing. This will be included in the latest release shortly.


[release-v1.10] Add eventshub service port name

Same as https://github.com/openshift-knative/eventing/pull/289

/cc @ReToCode