No communication between ConBee2 in Docker Container

Hi,
I an running the deconz community container on a RasPi 4 on Raspbian 10 Buster.
After upgrading the Docker Container from 2.13 I guess to the current 2.16.01 (docker-compose pull command) release I had no communication between docker image and ConBee2.
From within the container I can do GCFlasher and find the device (and for what strange reason a RaspBee that is not connected...)
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh

Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyACM0     | 0x1CF1 | 0x0030  |            | ConBee II
/dev/ttyAMA0     | 0x0000 | 0x0000  |            | RaspBee

The serial number of the ConBee is not showing up. Any other attempt to communicate with the Conbee2 fails.
I have flashed the current 26780700 firmware on Windows what worked fine. There, I could also see the serial number.
A brand new image from https://phoscon.de/en/conbee2/sdcard works. So the issue must be within the container / container configuration.
I have followed the installation instructions from https://hub.docker.com/r/deconzcommunity/deconz
My docker-compose.yml is the following:
version: '3'
services:
  homeassistant:
    container_name: homeassistant
    image: "ghcr.io/home-assistant/home-assistant:stable"
    volumes:
    - /home/pi/home-assistant:/config
    - /etc/localtime:/etc/localtime:ro
    - /media/nextcloud_hdd/homeassistant
    - /home/pi/.ssh:/root/.ssh
    restart: unless-stopped
    privileged: true
    network_mode: host
    healthcheck:
      test: ["CMD", "curl", "-f", "http://<IP_ADDRESS>:8123"]
      interval: :30s
      timeout: 10s
      retries: 6

  deconz:
    container_name: deconz
    image: "deconzcommunity/deconz:latest"
    volumes:
    - /etc/localtime:/etc/localtime:ro
    - /home/pi/.local/share/dresden-elektronik/deCONZ:/opt/deCONZ
    devices:
    - /dev/ttyACM0
    environment:
    - DECONZ_DEVICE=/dev/ttyACM0
    - DEBUG_INFO=1
    ports:
    - 8124:80
    restart: unless-stopped

  gitea:
    container_name: gitea
    image: strobi/rpi-gitea:latest
    environment:
     - USER_UID=1000
     - USER_GID=1000
    restart: unless-stopped
    volumes:
    - /media/nextcloud_hdd/gitea:/data
    - /etc/timezone:/etc/timezone:ro
    - /etc/localtime:/etc/localtime:ro
    #privileged: true
    ports:
    - "3000:3000"
    - "222:22"

I am also in contact with dresden-elektronik, they are trying their best but I guess we are at some point where they will say hardware is fine - not our business what would be fair
What else could I do to get the ConBee running?
Where / how can I see the logfiles? As journalctl seems to be disabled I am a bit confused where to look for the logs...
And, a bit off-topic, how can I edit text files? I have never ever seen a linux without vi...
Best regards, Stefan

You don't have any volume mounted for your device. See the read.me.

You don't have any volume mounted for your device. See the read.me.

I am having the same issue and I do not understand what you mean with no volume mounted for your device. I have looked into the README.md but still don't understand what you mean. Can you elaborate?

This one looks similar: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/4374

Seems like it got it fixed by adding "privileged: true" to my docker compose file.
Strange that this is now needed while I never needed that before.

Oh man thanks for hooking in into this conversation. This fixed it for me, too!!!

Maybe leave it open as it seems to be new behaviour that it needs to run privileged. And probably more people will have this issue. See also the issue where I just mentioned this issue.

Maybe leave it open as it seems to be new behaviour that it needs to run privileged. And probably more people will have this issue. See also the issue where I just mentioned this issue.

Unfortunately it did not work. Nothing really changed. The Raspbee did work on the phoscon image yesterday.


Is oneops safe to deploy in a cloud with existing infrastructure?

I deployed it on a test account and followed the deploy with the test assembly and I noticed in the logs that it was running queries on currently running instances.
Why is it doing that, and will it modify existing infrastructure that isn't configured somewhere in oneops?

@empath Any resources created in the cloud(s) by OneOps will usually have the unique OneOps ID (ciId) as part of the name, so there should be no conflicts with any non-OneOps managed resources under the same cloud account.  It's possible that some component recipes will perform a 'list' call in order to check if the expected resources are there or not in which case you will see the non-managed stuff in the logs. If you can track down the place in the code in https://github.com/oneops/circuit-oneops-1 based on your logs (or join our slack team and I can help track it down) we can take a look at either modifying the query to avoid this or maybe just suppress the extra logging
Bottom line, it should be safe to use in parallel with existing infrastructure, but it's worth noting couple of things:

OneOps has been open-source for few weeks only, so not much time for community to discover any issues related to this area
OneOps has been used in production at Walmart for some time now, but there is very little cloud use NOT managed by oneops, meaning not much opportunity to discover issues related to conflicts with existing infrastructure

Obviously, creating separate identity/credentials/tenants, if possible, during an evaluation period would be preferred.


Implement ZEEBE_INSECURE_CONNECTION config via environment

See: https://zeebe.io/blog/2019/10/0.21-release/#tls
The Node client establishes an insecure connection by default (to allow an easy out-of-the-box UX), but should switch useTLS: true if ZEEBE_INSECURE_CONNECTION=false is in the environment and converse (the converse case will make reversing the default behaviour easy in the future, if we go that way).

I wrote the docs for this, and it ruins the UX completely to go with INSECURE. Making this ZEEBE_SECURE_CONNECTION instead.


Improve formatting

Source code formatting seems to be optimized towards a small number of code lines. This results in poor readability (at least for me).
Therefore the source code should be reformatted, preferable using a code style which is similar to the one used in Glencoe.
We should make sure the comments stay in correct lines.

Created feature branch format.

Finished, but not merged yet.


No longer works with open3d 0.9

In 0.9 open3d function calls are grouped into categories.
Simply changing all similar occurrences of open3d.read_point_cloud(...) to open3d.io.read_point_cloud(...) fixed the syntax issue. When running the tests, an empty cloud is being published, so the conversions do not work.
I am using Ubuntu 18 on ROS Melodic with open3d 0.9.
Edit: Relevant Error message:
Traceback (most recent call last):
  File "/home/aaron/bedestrian_ws/src/open3d_ros_pointcloud_conversion/lib_cloud_conversion_between_Open3D_and_ROS.py", line 120, in <module>
    open3d_cloud = open3d.read_point_cloud(filename)
AttributeError: 'module' object has no attribute 'read_point_cloud'

you can easily port that. But there are still problems regarding colors within point clouds...
maybe i figure it out and do a pullrequest

I'm no longer working with open3d

what library are using now?


Train/Test split for Figure 4 results

Dear @slee5777 and @bearpelican,
thank you for making the work publicly available, including the dataset and the code.
I have a question about Figure 4 in the paper, where you computed AP across different classes. It is not clear from the paper what was the training and what testing dataset to generate the results for Figure 4. The holdout dataset is only mentioned that was used to generate results for Figure 5, where only cell counts are reported.
Can you elaborate on that, so that Figure 4 results for the DCNet can be reproduced?
Thanks!

I have found in the code that there is a random splitting performed using the fastai RandomSplitter, which is not mentioned in the paper. The default for the splitter is an 80/20 split. The code is also not working:
thresh = []
for iou_thresh in [0.1, 0.25, 0.5]:
    aps = []
    for score_thresh in [0.05, 0.1, 0.2, 0.4]:
        for min_area in [2,3,4]:
            ccap = calc_class_ap(lbls,preds, score_thresh=score_thresh, min_area=min_area, iou_thresh=iou_thresh)
            aps.append((ccap[-1]['ap'], score_thresh, min_area))
    print(iou_thresh, max(aps))
    thresh.append((iou_thresh,) + max(aps)[1:])

The code requires lbls and preds variables, which are not calculated before and are thus undefined.

The code is a bit scattered by order. I have loaded the pre-trained model and after running the above code, I mostly get much better results then reported in the paper, for al the classes and the combined ('all') class. I have thus no idea how to replicate the results from the paper, as the code seems not to be the same one that was used to generate the paper results.

The code requires lbls and preds variables, which are not calculated before and are thus undefined.

gt_lbls for training; holdout_lbls for test.  They are variables given when loaded.  preds are the results from predictions from DCNet.

The code is a bit scattered by order.

Sorry about that.  This repo is a simplified version of the whole development and experiment process.

I have loaded the pre-trained model and after running the above code, I mostly get much better results then reported in the paper, for al the classes and the combined ('all') class.

Good to hear.  Is it really a problem to understate the performance in the paper?!  We used a small pilot dataset for proof of concept.  So, we did not want to overfit the model.

I have thus no idea how to replicate the results from the paper, as the code seems not to be the same one that was used to generate the paper results.

After you load the model weight file .pth from Google Drive, then predict on the holdout_lbls.  You should get the same cell count results.  I tested it before I made this repo.

I have found in the code that there is a random splitting performed using the fastai RandomSplitter, which is not mentioned in the paper.

That is a common MLOps practice used in the industry for solving real-world problems.  Maybe we should mention it in the paper.  Both of us are from industries, not academics.  Actually, it is my very first academic paper.  So, any suggestions for improvements are welcomed.


[BUG] - Accordion has issue "Error: Unknown element <[object Object]> in collection."

NextUI Version
2.1.12
Describe the bug
When creating an accordion like this
import React from "react";
import {Accordion, AccordionItem} from "@nextui-org/accordion";

export default function App() {
const defaultContent =
    "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.";
  return (
    <Accordion>
      <AccordionItem key="1" aria-label="Accordion 1" title="Accordion 1">
        {defaultContent}
      </AccordionItem>
      <AccordionItem key="2" aria-label="Accordion 2" title="Accordion 2">
        {defaultContent}
      </AccordionItem>
      <AccordionItem key="3" aria-label="Accordion 3" title="Accordion 3">
        {defaultContent}
      </AccordionItem>
    </Accordion>
  );
}

I get the error Error: Unknown element <[object Object]> in collection.
Your Example Website or App
https://codesandbox.io/p/sandbox/fervent-firefly-vwvqc9
Steps to Reproduce the Bug or Issue
Create a page using the Accordion Component.
Expected behavior
https://nextui.org/docs/components/accordion
Screenshots or Videos
No response
Operating System Version
MacOS
Browser
Chrome

I also have experienced this error. Copy and pasted the code exactly from the documentation.

Same too.

workaround
@nextui-org/accordion is a client-side component, so simply add "use client" at the top of the page or import it in a client-side component.

Guys, please check this comment: https://github.com/nextui-org/nextui/issues/1403#issuecomment-1678863519

Remove the  from the layout.tsx, it's a server component, you can set as client component or create a new layout in other directory and then import the providers there

这是一个服务器组件，在引用的组件上方 增加
"use client";

表达这是一个客户端渲染组件。

在早前的版本中 会提示仅可在client 中使用，不知道为何 这个友好的提醒消失了

@CracKerMe  thanks. your solution fixed the error

@CracKerMe ありがとう

"use client"
Work

'use client' isn't a fix. Should be able to use the components with 'use server'

Two reasons why this error came.

No use client pragma usage
Wrong imports

The wrong imports depend on how you installed Nextui in the project. Module/component wise of globally. For example in the module case
Correct
import { Avatar } from "@nextui-org/avatar";
import {
  Dropdown,
  DropdownItem,
  DropdownMenu,
  DropdownTrigger,
} from "@nextui-org/dropdown";

wrong
import {
  Avatar,
  Dropdown,
  DropdownItem,
  DropdownMenu,
  DropdownTrigger,
} from "@nextui-org/react";


Updating data points & Load more data on the pan

Hi, there!
Updating data points in real time and load more data do not work fine together.
Here are my code snippets:
https://codesandbox.io/s/k5q55018no
I recorded the problem I have:

I will be really appreciated if you can help. Thanks in advance!

Hi, I figured out where was my mistake. Sorry for the inconvenience

@alexandrkondrachuk what was the issue/solution? I'm seeing the same behavior.


python3Packages.chia-rs: fix dependency patch and add missing check inputs

The build for chia-rs is broken because the fix-build.patch
file doesn't apply to the currently packaged source version.
Since the patch changes the dependencies pulled into the module's
rust build, I also had to change the corresponding Cargo.lock
file override.
With the fixed build, the module's tests also fail because of two
missing dependencies (clvm, clvm_tools).
Things done

Adapted fix-build.patch for the currently packaged version
Added clvm and clvm-tools dependencies as check inputs

Hydra job: https://hydra.nixos.org/build/241321128#tabs-details
Hydra build: https://hydra.nixos.org/build/241321128/nixlog/3
Relevant log excerpt:
patching sources
applying patch /nix/store/61vqx009qlkk0hh150n623mjcfg14dd7-fix-build.patch
patching file Cargo.toml
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file Cargo.toml.rej

#ZurichZHF
ZHF: https://github.com/NixOS/nixpkgs/issues/265948

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

@ofborg build python3Packages.chia-rs

This PR seems generally fine. Had to dig up through some history to figure out why this Cargo.lock vendoring is required - looks like upstream disabled building the wheel subdir by default, which means their lockfile doesn't include the deps for it.
Given that this package seems to be unmaintained, I question whether it should be kept in the package set. It keeps being broken, the maintainer team seems mostly inactive and other members of the community are having to step up to keep it up to date and building.
@lourkeur can you commit to keeping this up to date and unbroken in the future, or should we remove this derivation from nixpkgs?

This PR seems generally fine. Had to dig up through some history to figure out why this Cargo.lock vendoring is required - looks like upstream disabled building the wheel subdir by default, which means their lockfile doesn't include the deps for it.
Given that this package seems to be unmaintained, I question whether it should be kept in the package set. It keeps being broken, the maintainer team seems mostly inactive and other members of the community are having to step up to keep it up to date and building.
@lourkeur can you commit to keeping this up to date and unbroken in the future, or should we remove this derivation from nixpkgs?

I cannot commit, please see #270254

Thank you for the quick reply! Let's close this in favor of #270254 then.


Memory not returned back from swapfile

Windows Version
Microsoft Windows [Version 10.0.22631.3085]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
-Define swapspace in wsl.config
-Run application that uses swapspace
Expected Behavior
-Memory should be returned back when finished or at the next start of the system
Actual Behavior
-Memory is not returned
Diagnostic Logs
No response

/logs

Hello,
It says that I should reproduce the problem and then save the logs. However in my case there is no single step to reproduce the problem since there is the existing swap file and it doesn't return memory back. I think it is the same problem as with the vhdx from wsl itself, which has been a problem for a long time until it has been solved with the SparseVhd parameter. However for the swapfiles, there is no such parameter and one has to delete the swapfile manually when it gets too large

@JannikSchneider12 - can you clarify what you mean by "does not reclaim the memory back"? Are you referring to the swap vhd  disk that is created?


Variable width font for Pandas tables in Hydrogen output area

Description:
Prior to September 2018, the Hydrogen output area used a variable width font (Arial or similar), which worked well for general text output or Pandas' formatted data tables. However, in September 2018, a change was applied to styles/hydrogen.less, to use a monospaced font for the output area. See here. This causes my editor to use Courier New (or similar) for output, which is lighter, looser-spaced and less legible than Arial. This makes most output less attractive, less information-dense and harder to read.
I restored the older, more attractive behavior by going to Atom > Preferences > Packages > Hydrogen > View Code > styles > hydrogen.less > Output Area > .multiline-container, then commenting out "font-family: monospace;". But most users would not want to do that.
Would it be possible to add a "Font for output area" option to Hydrogen, for users who prefer a variable-width font for the output area?
Steps to Reproduce:

Create a file with a .py extension
Execute "Hydrogen: Toggle Output Area" command to activate output area
Type this command: import pandas; pandas.DataFrame({'a': [1, 2], 'b': [3, 4]}) and press cmd-return or ctrl-Enter
Observe that the resulting table is shown in a light monospaced font

Versions:
Atom    : 1.32.2
Electron: 2.0.9
Chrome  : 61.0.3163.100
Node    : 8.9.3
Plugins:
Do you have any Hydrogen plugins installed and active?

[x] hydrogen-python
[x] Hydrogen Launcher
[ ] Data Explorer

Logs:
(N/A)

The change was 100% purposeful as a lot of space formatted outputs rely on monospace. See https://github.com/nteract/hydrogen/pull/1424#issue-217547592

Mentioning @BenRussert to approve, and if so I'll take it on. Thanks for the recommendation @mfripp.

Totally agree, it is especially harder to read with pandas dataframes.

@wadethestealth I could take this issue to work or has someone working on this issue?


💡[Feature]:  Alzheimer Disease Prediction

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I would like to develop a model which predicts accurately alzheimers disease.
Use Case
Alzheimers is a problem which became common these days . My model is trained on patients data and gives results.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@TAHIR0110
Kindly assign this issue to me.

@AmrutaJayanti assigned!


VS2017 Getting Started doc updates

Fixes #1480
Notes

Still rough! Ruf! Ruf! :dog2: Even after review and merge, I'd like to come back in a week or two and work these a bit more.
New images! ... but more needed in a few spots. Let's not hold it up tho just for a couple that I can add later.
Propose we keep the old images in the media folder. They might be linked into other docs. After all docs in this area have dedicated static asset folders for their images, we can delete all of the images in the media folder safely.
If there are more docs that need updating under #1480, I can do those, but I suppose not holding up the whole 🌏 planet 🌍 for these would be good.
@mairaw I don't think you added the red stroke outlines to the images you did for #1663. I got it covered ... I opened #1675 for it.

I'll remove the WIP label after the build runs and I fix any broken links.
I'll ping when it's ready for a :eyes: look :eyes:.

@GuardRex,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


switch $(uname) to $OSTYPE in case example

Massive caveat: I'm on MacOS and have only been able to Google how other operating systems report $OSTYPE -- so this may not be 100% correct.
Can confirm darwin is correct for Mojave dev preview though :)

LGTM :+1:
Thanks!

The code should be correct, I was working on this for Neofetch but decided to continue to use uname since we execute it once for a bunch of flags and cache the output (so there's no speed difference between the two).
There's a table here with values for OSTYPE.
https://github.com/dylanaraps/neofetch/issues/433


Crash when passing an empty blocks array to editorStateFromRaw

I have an error when I try to initiate an editor state as shown here :
http://megadraft.io/#/docs/saving-loading
const editorState = editorStateFromRaw({"entityMap": {}, "blocks": []});

Uncaught TypeError: Cannot read property 'getKey' of undefined
at Function.createWithContent (EditorState.js:56)
at editorStateFromRaw (utils.js:39)
at new App (App.js:22)
at ReactCompositeComponent.js:295
at measureLifeCyclePerf (ReactCompositeComponent.js:75)
at ReactCompositeComponentWrapper._constructComponentWithoutOwner (ReactCompositeComponent.js:294)
at ReactCompositeComponentWrapper._constructComponent (ReactCompositeComponent.js:280)
at ReactCompositeComponentWrapper.mountComponent (ReactCompositeComponent.js:188)
at Object.mountComponent (ReactReconciler.js:46)
at ReactCompositeComponentWrapper.performInitialMount (ReactCompositeComponent.js:371)

A simple workaround is to pass a null value :
const editorState = editorStateFromRaw(null);

I have fixed the "saving & loading" doc

Hey @jimojon! Looks like this is a DraftJS problem, I'm closing the issue ok?


Distance attenuation is working in reverse

The distance attenuation is actually getting louder the further i go away from the source. Seems its working in reverse.
My settings: https://gyazo.com/58b434146eed4069e5c0d9e10364b0a7

Make sure you use the latest version here from the releases page: https://github.com/thorwe/CrossTalk/releases
The version on the official teamspeak addon page is heavily outdated.

Ok i used 1.6.1 on both sides, will try with latest and report back.

Is your Rolloff value positive? It should be negative in order to decrease when you move further apart.

@thorwe why?

Why what? Note my comment in this issue is from a year ago if you mean that.

Ohh okay i thought they wouldn't accept updates once again ;D

Closing as solved.


Remove sleep from BlobOutputStream

BlobOutputStream currently does of series of polling/short sleeps to wait for data upload to finish before completing. We should switch to using a condition variable similar to what we did with FluxInputStream so that we don't waste time/cpu sleeping the thread.

This has been updated


Changes to telemetry with regards to discovery of python environments

sendTelemetryWhenDone(EventName.PYTHON_INTERPRETER_DISCOVERY, promise, undefined, { locator: this.name });
Change above code to capture number of items discovered.
Currently it just indicates the discovery ran to completion without errors, that's it, pretty much useless
Easy change.

Prescribed solution:

Modify getInterpreters method of src/client/interpreter/locators/services/cacheableLocatorService.ts
Send the counter (number of interpreters)
Update InterpreterDiscovery type in src/client/telemetry/types.ts
to account for this new property sent as part of the telemetry


Flawed initialization concept for BodyWriter

Version of Beast
1.78.0 (latest)
The Problem
So I wrote a custom BodyWriter that allows to compress data on the fly using the HTTP Content-Encoding mechanism. This means the BodyWriter has to conditionally set the response headers to gzip or deflate in this case, based on what the HTTP client actually supports. This is what the current layout currently looks like:
class custom_body::writer {
  value_type& _value;

 public:
  using const_buffers_type = boost::asio::const_buffer;

  template <bool isRequest, class Fields>
  writer(boost::beast::http::header<isRequest, Fields>& header, value_type& value):  _value{value} {
    if (value.isGzip()) {
      header.insert(field::content_encoding, "gzip");
    } else if (value.isDeflate()) {
      header.insert(field::content_encoding, "deflate");
    }
  }

  void init(boost::system::error_code& ec) noexcept {
    ec = {};
  }

  boost::optional<std::pair<const_buffers_type, bool>> get(boost::system::error_code& ec) {
    // compressing code
  }
};

However when I recently stumbled over the official documentation of BodyWriter it clearly stated that:

The writer shall not access the contents of h or v before the first call to init, permitting lazy construction of the message.

For the constructor of the writer class. The only way to be compliant with this requirement is to use type-erasure of some sort (std::any, std::function, etc.)due to the template <bool isRequest, class Fields> being used for the header; as it can't be stored as a regular member. This is really inconvenient because the type information is lost. In case the documentation has a legitimate reason for this requirement, a potential solution to this would be to pass the headers to init and/or get as an argument directly instead of passing it to the constructor.
What are your thoughts on this?

Yes I agree the Body concept (plus the reader and writer) have design flaws.

Yes I agree the Body concept (plus the reader and writer) have design flaws. You are probably better just writing the header using beast, but serializing the body yourself using a buffer-based approach instead of trying to make it work with the Body concept.

Yeah, writing the headers 'by-hand' is what I ended up doing. I'm not exactly sure how you imagine a buffer-base approach. Somehow writing to the stream directly I suppose? I ended up using the Body concept just to implement chunked transfer encoding (because the size is unknown) so I don't have to change the code that previously sent a plain string too much.

We can't change this for now but I am working on some new concepts in a new library.

@vinniefalco By "new library" do you mean something completely independent of beast or more like beast 2.0?

Completely independent of beast

@vinniefalco Thanks for your time and I'm looking forward to it 👍🏼


SDL not configured with EGL support

Running NeoDemo on a mac.
When I switch the backend to OpenGL ES demo crashes with:
"Unable to create OpenGL Context: \"SDL not configured with EGL support\". This may indicate that the system does not support the requested OpenGL profile, version, or Swapchain format.”

So I'm guessing something's wrong with the backend detection here (i.e OpenGL ES should not be enabled in this case)?

As far as I know, macOS does not support OpenGL ES at all.

(i.e OpenGL ES should not be enabled in this case)?

Yeah, that's correct. The other options are greyed out because Veldrid does real support checks for those.
Unfortunately, Veldrid doesn't currently detect whether OpenGL or OpenGL ES are "supported" by the system, because it is rather complicated. I can probably do better OS-based checks, though, and at least detect this case.

Calling GraphicsDevice.IsBackendSupported(GraphicsBackend.OpenGLES) on macOS will now return false. NeoDemo uses that information to determine whether an option is available in the drop-down.
https://github.com/mellinoe/veldrid/commit/46ce154a0ebdded4fccee7ff93dec4c31352b5d8

This one should have been improved by the commit above -- please re-open if that's not the case.


No value has been specified for property 'packageJsonFile'.

I am using Gradle 6 with the following configuration in the build file:
node {   version = '12.14.1'   npmVersion = '6.13.6'   distBaseUrl = 'https://nodejs.org/dist'   download = true   workDir = file("${project.buildDir}/app") }
When I run gradle npmInstall, it builds for a while but then exits due to:
No value has been specified for property 'packageJsonFile'.
Where do I set this property and what should it be set to?

I got my setup to work, replacing plugin's npmInstall task with hand-made one:
	task "npmMyInstall"( type:NpmTask ) {
		group = 'node'
		description = 'Runs npm install'
		workingDir = file '...'
		args = [ 'install' ]
	}


Pull Request participants is not mapped correctly

The actual response from the API includes more information including if the reviewer approved or not but this library doesn't have that

Taking a look.

Should be fixed @dcu.


Improvements to OLM bundle building of test index

Release Note
NONE

Much of this PR seems to have been superceded and already added so changes here are fixes in response to review comments.

The test is failing:
❌ TestKameletFromCustomRepository (10m10.77s)


Add SP_IDP_ATTR table to Identity DB

Describe the issue:
Following change has been introduced for issue https://github.com/wso2/product-is/issues/15843
with https://github.com/wso2/carbon-identity-framework/pull/4473
This will need migration for the existing versions.

This won't be required for migration.
This will be removed with

https://github.com/wso2/product-is/issues/15998


fix: remember shards that fail Open(), avoid repeated attempts

If a shard cannot be opened store its ID and last error.
Prevent future attempts to open during this invocation of
influxDB. This information is not persisted, however.
partial close of https://github.com/influxdata/influxdb/issues/23428
closes https://github.com/influxdata/influxdb/issues/23426

[X] Well-formatted commit messages
[X] Rebased/mergeable
[X] Tests pass

I would like to implement the change of reporting MaxSeriesDataBaseExceeded as a separate issue, because the changes are wide-ranging (it gets passed around as a string field in a PartialWriteError and that has to be converted in a error to allow distinguishing it from other partial writes.

I would like to implement the change of reporting MaxSeriesDataBaseExceeded as a separate issue, because the changes are wide-ranging (it gets passed around as a string field in a PartialWriteError and that has to be converted in a error to allow distinguishing it from other partial writes.

Added to https://github.com/influxdata/plutonium/issues/3870 (general logging audit)


allow custom date formats when retrieving historical data

As the current date format for the retrieved information is: dd/mm/yyyy, which stands for day-month-year.
But as that format is the one used in Spain, more date formats should be supported such as mm/dd/yy, m/d/yy, etc. also the separator can either be -, / or no separator can be used.
This argument will be optional, since default date format will remain as established currently (until 0.8.7 release) as dd/mm/yyyy.

19ab35e6963af39c64e5b4490301ac4878a149b6


Split test code, fix assertions and follow idiomatic test naming

After adding the SWAP PR #363, I believe that we need to change the file structure and naming of files to continue growing the number of tests in an idiomatic way.
EX: We had the swap script tests in one separate file and p2id and p2idr swap scripts tests in one global "note_test" file
I propose in this PR:

Splitting different tests in their own files
Fixed the naming of the test files
Fixed the used assertions
Removed the miden particle

Nice initiative


Fix blank screen on safari desktop with small window size

On desktop (macOs) safari shows blank screen around 991 - 977 pixels.

This was the simplest fix I could come up with. Better approach maybe in CSS - but problem is difference between browsers on whether the scrollbar is counted.
@superzordon let me know if you want me to PR this to diamondapp as well.

such a waste of energy and time...


Error monitoring Host after importing new Host to new Cluster

Description
Getting a error "Fri Jul 7 09:16:19 2023 : Error monitoring Host server-node01.foo.bar (27):" after importing a new host to a new created cluster in OpenNebula.
To Reproduce

Login to Open Nebula Management
Create a new cluster
Import a new host with type KVM

Expected behavior
One will import the host correctly.
Details

Affected Component: Scheduler (it seems to be)
Hypervisor: KVM
Version: 6.4.0

Additional context
We're determine, that the following scripts are hanging (We're think it's affected to STDIN) on the remote node machine after the one-mgmt pushed the scripts to the new nodes and try to executed it remotely.

/var/tmp/one/im/kvm.d/monitord-client_control.sh
/var/tmp/one/im/kvm.d/monitord-client.rb

The ssh-connection between one-mgmt and server-node01 works well and as expected. We're don't have any more error informations about this case.
If you have any informations for me to get more error-logs or something else please let me know and I will share it here.
server-node01 operating system: Debian 11.7
one-mgmt operating system: Debian 11.7
Progress Status

[ ] Code committed
[ ] Testing - QA
[ ] Documentation (Release notes - resolved issues, compatibility, known issues)

Can be closed. It was the missing datastore path configuration.


docs: add installation steps for Azure RedHat Openshift

Reason for Change:

Requirements

[x] squashed commits
[x] included documentation
[x] added unit tests and e2e tests (if applicable).

Issue Fixed:

fixes #365
Does this change contain code from or inspired by another project?

[ ] Yes
[x] No

If "Yes," did you notify that project's maintainers and provide attribution?
Special Notes for Reviewers:

@ezYakaEagle442 Could you help review this PR?

Codecov Report

Merging #446 (2a0d804) into master (52b147c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #446   +/-   ##
=======================================
  Coverage   62.86%   62.86%
=======================================
  Files           6        6
  Lines         474      474
=======================================
  Hits          298      298
  Misses        144      144
  Partials       32       32

@aramase it looks goods but one key step is missing : "How to get/create the Cloud Provider secret" as I have described at Azure/OpenShift#216

@ezYakaEagle442 The Secrets Store CSI Driver doesn't use the cloud provider config. All the required parameters are configured using the SecretProviderClass


Updates appear in Live Preview but CSS file isn't updated

First off, great plugin! When I had it working a couple months ago I was thrilled!
When I tried using it today, though, something strange happened. I can edit my scss file and see the changes happening to my html file in Live Preview, but the css file is never actually updated. Any ideas what might be up here?

Never mind! I figured out what the problem is.
I had another project open and had opened my index.html and .scss file by right clicking my files and using Open in Brackets. To fix, in Brackets I selected File > Open Folder... and selected my folder instead. Then I clicked on the files to open them and the problem went away.
What gave it away was the URL. At first it started with file:///, then when I did it right it changed to my http://<IP_ADDRESS>/ localhost.


Discord invite link are expired/broken

Hi ... I want to join the smelte discord server, but it looks like the link has expired.

Found it. Here is the link to the discord server: https://discord.gg/Fdyqpt9
Warning, it seems to be fairly inactive at the moment.

Thanks @SureDroid !

New link: https://discord.gg/M9tQnNps


Signe In with Oidc broken

Running a self hosted version 2.75.0 of WeKan. When I clock on Sign in with Oidc I get an error saying a.join is not a function. Sign in with Oidc worked until sometime around 5/24/2019

Please try newest Wekan.
sudo snap refresh


Indention Rule: Parameters should be aligned vertically

Enforce that parameters should be aligned. This is how default IntelliJ
formatter works. This approach is listed on:
https://ktlint.github.io/#rule-indentation
https://kotlinlang.org/docs/reference/coding-conventions.html#class-header-formatting
https://android.github.io/kotlin-guides/style.html#functions
This allows to prevent stuff like that
class ClassA(paramA: String
    paramB: String,
        paramC: String)

@shyiko Sorry, initially I was fully confident that "align parameters"  is how rule is designed (https://ktlint.github.io/#rule-indentation). But just before creating PR, I've noticed that error message actually allow not aligned parameters.

Unexpected indentation (${line.length}) (parameters should be either vertically aligned or indented by the multiple of $indent)

Feel free to close this PR, if you actually want to preserve that option.

@shyiko This change also allows to implement auto correction. Because expected indent is completely defined. See https://github.com/shyiko/ktlint/pull/126
I'm looking forward to know your thoughts about this change.

Unless I'm reading it wrong,
class ClassA(paramA: String, paramB: String,
             paramC: String)
class ClassB(paramA: String, paramB: String, paramC: String)

should be formatted as
class ClassA(
    paramA: String,
    paramB: String,
    paramC: String
)
class ClassB(paramA: String, paramB: String, paramC: String)

(per "Classes with longer headers should be formatted so that each primary constructor argument is in a separate line with indentation" and "When a function signature does not fit on a single line, break each parameter declaration onto its own line").
Would you be willing to update PR to reflect this? (having this + #126 would be awesome)

Should this really be applied for methods too? Seems like it's a bit of overkill.

@shyiko it's even more strict than what I wanted to do. But I'm fine with that :)
I'd like to completely clarify what is done. There are two rules. IndentationRule and ParametersOnSeparateLinesRule. They have different responsibilities.
IndentaionRule only cares about indentation.
In case of parameters, it verifies that, if parameter already has indentation (eg. placed on new line), then parameter should be aligned with the first parameter (regardless where it's placed).
Valid examples
class ClassA(paramA: String, paramB: String,
             paramC: String)

class ClassA(
    paramA: String, paramB: String,
    paramC: String)

//it also works for lambda
val fieldExample =
        LongNameClass { paramA,
                        paramB,
                        paramC ->
            ClassB(paramA, paramB, paramC)
        }

Non valid examples
class ClassA(paramA: String, paramB: String,
    paramC: String)

class ClassA(
    paramA: String, paramB: String,
  paramC: String)

val fieldExample =
        LongNameClass { paramA,
            paramB,
            paramC ->
            ClassB(paramA, paramB, paramC)
        }

ParametersOnSeparateLinesRule takes care about each parameter
Parameters should:

either occupy only one line
either each parameter should be placed on new line

Exception: this rule doesn't take case of lambda (see example below)
Valid
class ClassA(paramA: String, paramB: String, paramC: String)

class ClassA(
    paramA: String,
    paramB: String,
    paramC: String)

class ClassA(
    paramA: String,
    paramB: String,
    paramC: String
)

As you see it doesn't care about enclosing brace.
Non Valid
class ClassA(paramA: String, paramB: String,
             paramC: String)

class ClassA(paramA: String,
             paramB: String,
             paramC: String)

class ClassA(
    paramA: String, paramB: String,
    paramC: String
)

Exception for lambda
val fieldExample =
        LongNameClass { paramA,
                        paramB,
                        paramC ->
            ClassB(paramA, paramB, paramC)
        }

this example is not enforced.
Final notes
Final brace ) is not enforced and lambda is not supported. I did it by purpose, in order to reduce scope of changes. I would prefer to do it in separate PRs.
@shyiko let me know what you think.

@vanniktech good question.
I would say yes.  The initial rationale for me is: Having each parameter on separate line improves readability. In case of multiple parameters per line, I have to "parse" that line when I read it, in order to find all parameters.
And for me same rationale applies for classes, functions etc.
@shyiko what do you think?

I would say yes. The initial rationale for me is: Having each parameter on separate line improves readability. In case of multiple parameters per line, I have to "parse" that line when I read it, in order to find all parameters.
And for me same rationale applies for classes, functions etc.

This becomes really verbose really quickly especially when you have a large function call. I'd like to have a flag for this so that you can either enable or disable this for parameters.

Sorry, for my previous "too quick" response. Actually, this is aligned with
https://android.github.io/kotlin-guides/style.html#functions

When a function signature does not fit on a single line, break each parameter declaration onto its own line.

I like the way it'll be done in kotlinpoet - https://github.com/square/kotlinpoet/pull/281/

@vanniktech I'm not sure what you mean exactly. Decide wrap or not according to line length? If yes, we should definitely do that. But I would prefer to do it in separate PR. Just to keep current one smaller and merge it earlier.
@shyiko I'm looking forward for your feedback :)

Then let's do it in a different PR.

@MyDogTom (just so we are all on the same page) I plan to merge this + #126 (with a few adjustments related to braces) right after the New Year's Eve.

@shyiko 👍


Add a minTileHeight to ListTile widget so its height can be customized to less than the default height.

fixes: https://github.com/flutter/flutter/issues/145369
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] I followed the breaking change policy and added Data Driven Fixes where supported.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Added a issue.
I tried isDense and the tile height is 48, i want to implement a tile with height to 32 for my use case.
Also if we need to add this property, should we also add visual density adjustment to minTileHeight? >> I think if you set the minHeight explicitly, it makesense to override the visual density.


External Event Drag Drop in Calendar

Left divs (1-2-3-4-5) i want to drag on my calendar than i want to edit on function
for example div data attributes: data-id, data-title, data-explanation(for popover), data-color
Hi Vladimir,
How are you ?
I want to drag and drop external event from left or right div content than remove div :)
How can i do ?
I cant find about external event drag&drop :(

Hi @emrahnalci
Unfortunately, external drag and drop is not supported yet. There was some discussion about this here.

Hmm im understand Vladimir
Thank you 👍🏼


Better Android custom data location support.

PR for #22
Allow targeting SDK to Android 12
A preview build can download here.
https://github.com/samnyan/techmania/releases/tag/1.0.2-android

Looks like TECHMANIA/Assets/Plugins/AndroidNativeIO/lib-release.aar is a compiled Android library.

Is this the library that cn.samnya.nativeandroid.io refers to?
Is the source code of this library available?

Yes, and the source code was released here
https://github.com/samnyan/UnityNativeAndroidIO

Content URI
content:// paths is Android Content Provider URI and basically, it provides an application layer file access.
For example, the Google Drive app can provide a URI like content://google.drive/someFilePath.jpg. Any application access to this file will be handled by the Google Drive app itself without downloading to some public folder and reading from there.
By using the file picker provided by Android when setting the custom data location, it returns a URI looks like
content://com.android.externalstorage.documents/tree/primary%3ATechmania%2FTracks.
This means the file access is provided by com.android.externalstorage.documents, a system application.
UniversalIO.GetRealPathFromUri
The URI provided by com.android.externalstorage.documents can be translated back to a real file path most of the time, UniversalIO.GetRealPathFromUri does exactly that.
From the URI content://com.android.externalstorage.documents/tree/primary%3ATechmania%2FTracks

primary:Techmania/Tracks was the URL decoded result of that URI result.
primary means the primary storage device, mounted at  /storage/emulated/0/
Techmania/Tracks is the relative path

So the resulting output will look like /storage/emulated/0/Techmania/Tracks
The old Fantom plugin will return this real path as the file picker result.
But using C# file access on the real path has huge limitations after Android 11.
It only provided access to media files with with ".mp4 .jpg .mp3" extension for example.
And listing files with C# enumeratefiles won't see any other file at all.
This is why most of the file access will be handled by the plugins.
And because media files can be accessed directly, assets like eye catch and key sound were converted back to the real path and then handle by Unity.
About the UniversalIO
I will create a subclass inside UniversalIO for a better method name.
The reason some method doesn't handle content URI is that it doesn't provide an equivalent method in Android, and I may remove those methods in UniversalIO. (Most of them were for unzipping the track)
For the streaming assets, I don't think it will handle by this native io. I'm still working on that.


Propagate shape information from tensorlist to mhlo ops.

Seeing things like
    %1393 = "tensorlist.Concat.Tensor"(%1392) : (!tensorlist.list) -> tensor<?xf32>
    %1394 = "mhlo.reshape"(%1393) : (tensor<?xf32>) -> tensor<1x528xf32>

This is the issue for tracking shape dynamism in ASR.

Obsolete


Action Plugin Missing

Hi @selwynpolit Thank you for putting this together.
It would help many to learn Drupal.
Here is the reference example for action_plugin_examples
custom action plugin with ConfigurationForm

@bhanu951 Is this some examples of custom actions that you've written for use with the Drupal Core Actions module?

@selwynpolit yes, they are custom actions based on core actions module.

Great.  Are you interested in writing a paragraph or two explaining what they do?  It's ok if you don't want to, I can write them and you can edit what I write.

I don't have much experience in documentation and explanation. I can try
but can't guarantee it.
If I have not made any progress in a day or two please carry on with your
writing.
On Wed, 10 May, 2023, 8:48 am Selwyn Polit, @.***>
wrote:

Great. Are you interested in writing a paragraph or two explaining what
they do? It's ok if you don't want to, I can write them and you can edit
what I write.
—
Reply to this email directly, view it on GitHub
https://github.com/selwynpolit/d9book/issues/50#issuecomment-1541285440,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBBJ4FMVKDZFWKRVUSQ5CTXFMCJRANCNFSM6AAAAAAX3NRDVY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Action Plugins
Overview
A Drupal action is a fuctionality which performs specific action when executed.
For example, Archive Node, Make Content Sticky.
Actions use the annotation class of Drupal\Core\Annotation\Action, and extend Drupal\Core\Action\ActionBase or Drupal\Core\Action\ConfigurableActionBase (if the action is configurable).
Action Plugin definition is defined in Plugin Annotation. It has 3 required keys

/**
 * Provides an Archive Node Action.
 *
 * @Action(
 *   id = "action_plugin_examples_archive_node",
 *   label = @Translation("Archive Node"),
 *   type = "node",
 *   category = @Translation("Custom")
 * )
 */

id --> ID of the Action Plugin
label --> Name of the Action Plugin
type --> Entity type to which the Action Plugin belongs to
category --> (optional) Category of the Action Plugin
Create Simple Action

<?php

namespace Drupal\action_plugin_examples\Plugin\Action;

use Drupal\Core\Action\ActionBase;
use Drupal\Core\Session\AccountInterface;
use Drupal\Core\Plugin\ContainerFactoryPluginInterface;
use Symfony\Component\DependencyInjection\ContainerInterface;
use Drupal\pathauto\PathautoState;

/**
 * Provides an Archive Node Action.
 *
 * @Action(
 *   id = "action_plugin_examples_archive_node",
 *   label = @Translation("Archive Node"),
 *   type = "node",
 *   category = @Translation("Custom")
 * )
 */
class ArchiveNode extends ActionBase implements ContainerFactoryPluginInterface {

  /**
   * The Messenger service.
   *
   * @var \Drupal\Core\Messenger\MessengerInterface
   */
  protected $messenger;

  /**
   * Logger service.
   *
   * @var \Drupal\Core\Logger\LoggerChannelFactoryInterface
   */
  protected $logger;

  /**
   * The path alias manager.
   *
   * @var \Drupal\path_alias\AliasManagerInterface
   */
  protected $aliasManager;

  /**
   * Language manager for retrieving the default Langcode.
   *
   * @var \Drupal\Core\Language\LanguageManagerInterface
   */
  protected $languageManager;

  /**
   * {@inheritdoc}
   */
  public static function create(ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition) {
    $instance = new static($configuration, $plugin_id, $plugin_definition);
    $instance->logger = $container->get('logger.factory')->get('action_plugin_examples');
    $instance->messenger = $container->get('messenger');
    $instance->aliasManager = $container->get('path_alias.manager');
    $instance->languageManager = $container->get('language_manager');
    return $instance;
  }

  /**
   * {@inheritdoc}
   */
  public function access($node, AccountInterface $account = NULL, $return_as_object = FALSE) {
    /** @var \Drupal\node\NodeInterface $node */
    $access = $node->access('update', $account, TRUE)
      ->andIf($node->title->access('edit', $account, TRUE));
    return $return_as_object ? $access : $access->isAllowed();
  }

  /**
   * {@inheritdoc}
   */
  public function execute($node = NULL) {

    /** @var \Drupal\node\NodeInterface $node */

    $language = $this->languageManager->getCurrentLanguage()->getId();

    $old_alias = $this->aliasManager->getAliasByPath('/node/' . $node->id(), $language);

    $title = $node->getTitle();
    $date = $node->created->value;
    $year = date('Y', $date);
    // $old_alias = $node->path->alias;
    $new_title = $this->t('[Archive] | @title', ['@title' => $title]);
    $node->setTitle($new_title);
    $node->setSticky(FALSE);
    $node->setPromoted(FALSE);

    $new_alias = '/archive/' . $year . $old_alias;
    $node->set("path", [
      'alias' => $new_alias,
      'langcode' => $language,
      'pathauto' => PathautoState::SKIP,
    ]);

    $node->save();

    $message = $this->t('Node with NID : @id Archived.', ['@id' => $node->id()]);

    $this->logger->notice($message);
    $this->messenger->addMessage($message);

  }

}

Inorder to get Action Plugin Discoverable you need to add system.action.<plugin_id>.yml which is placed in config/install
The structure of the .yml file should be as below.

langcode: en
status: true
id: action_plugin_examples_archive_node
label: 'Archive Node'
type: node
plugin: action_plugin_examples_archive_node

Create Custom Action Plugin with ConfigurationForm
<?php

namespace Drupal\action_plugin_examples\Plugin\Action;

use Drupal\Core\Action\ConfigurableActionBase;
use Drupal\Core\Form\FormStateInterface;
use Drupal\Core\Session\AccountInterface;
use Drupal\Core\Plugin\ContainerFactoryPluginInterface;
use Symfony\Component\DependencyInjection\ContainerInterface;

/**
 * Provides a an Update Node Title Action.
 *
 * @Action(
 *   id = "action_plugin_examples_update_node_title",
 *   label = @Translation("Update Node title"),
 *   type = "node",
 *   category = @Translation("Custom")
 * )
 */
class UpdateNodeTitle extends ConfigurableActionBase implements ContainerFactoryPluginInterface {

  /**
   * The Messenger service.
   *
   * @var \Drupal\Core\Messenger\MessengerInterface
   */
  protected $messenger;

  /**
   * Logger service.
   *
   * @var \Drupal\Core\Logger\LoggerChannelFactoryInterface
   */
  protected $logger;

  /**
   * The path alias manager.
   *
   * @var \Drupal\path_alias\AliasManagerInterface
   */
  protected $aliasManager;

  /**
   * Language manager for retrieving the default Langcode.
   *
   * @var \Drupal\Core\Language\LanguageManagerInterface
   */
  protected $languageManager;

  /**
   * {@inheritdoc}
   */
  public static function create(ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition) {
    $instance = new static($configuration, $plugin_id, $plugin_definition);
    $instance->logger = $container->get('logger.factory')->get('action_plugin_examples');
    $instance->messenger = $container->get('messenger');
    $instance->aliasManager = $container->get('path_alias.manager');
    $instance->languageManager = $container->get('language_manager');
    return $instance;
  }

  /**
   * {@inheritdoc}
   */
  public function defaultConfiguration() {
    return ['title' => 'Updated New Title'];
  }

  /**
   * {@inheritdoc}
   */
  public function buildConfigurationForm(array $form, FormStateInterface $form_state) {
    $form['title'] = [
      '#title' => $this->t('New Title'),
      '#type' => 'textfield',
      '#required' => TRUE,
      '#default_value' => $this->configuration['title'],
    ];
    return $form;
  }

  /**
   * {@inheritdoc}
   */
  public function submitConfigurationForm(array &$form, FormStateInterface $form_state) {
    $this->configuration['title'] = $form_state->getValue('title');
  }

  /**
   * {@inheritdoc}
   */
  public function access($node, AccountInterface $account = NULL, $return_as_object = FALSE) {
    /** @var \Drupal\node\NodeInterface $node */
    $access = $node->access('update', $account, TRUE)
      ->andIf($node->title->access('edit', $account, TRUE));
    return $return_as_object ? $access : $access->isAllowed();
  }

  /**
   * {@inheritdoc}
   */
  public function execute($node = NULL) {
    /** @var \Drupal\node\NodeInterface $node */
    $old_title = $node->getTitle();
    $updated_title = $this->t('@new_title @old_title', ['@old_title' => $old_title, '@new_title' => $this->configuration['title']]);

    $node->setTitle($updated_title)->save();

    $message = $this->t('Node Title for Node with NID : @id Updated.', ['@id' => $node->id()]);

    $this->logger->notice($message);
    $this->messenger->addMessage($message);
  }

}

Schema for Action Plugin action_plugin_examples.schema.yml which is placed in config/schema

action_plugin_examples.configuration.action_plugin_examples_update_node_title:
  type: mapping
  label: 'Configuration for "Update node title" action'
  mapping:
    title:
      type: string
      label: Title

Action Plugin Definition system.action.<plugin_id>.yml which is placed in config/install

langcode: en
status: true
dependencies:
  module:
    - node
    - pathauto
id: action_plugin_examples_update_node_title
label: 'Update Node Title'
type: node
plugin: action_plugin_examples_update_node_title
configuration:
  title: 'Updated New Title'

You need to install the core module Actions first to be able to configure action plugins in UI.
Configuration Page /admin/config/system/actions
On the top of the page your new plugin should be present in the select list for creating advanced actions. When you select the plugin you should see the configuration form of your plugin:
Change Record : https://www.drupal.org/node/2020549

Text Gist https://gist.github.com/bhanu951/23019cc11cf590a4610bb69c493ccf35
@selwynpolit  I wrote my explanation in the above gist, do review it and make necessary changes.

That looks pretty good to me.  I'll get this added to a new actions section ASAP.

@bhanu951 Thanks again for your contribution.  I finished putting up that page. What do you think?  https://selwynpolit.github.io/d9book/actions#overview

Hi @selwynpolit  , Thanks for creating new chapter, except minor spelling nits, its good. I believe we are good to close this issue.

@bhanu951 please give the edit a try - it is at the bottom of the page and fix those spelling nits.

Done @selwynpolit  https://github.com/selwynpolit/d9book/pull/60/


#22778 Fix outline update issue on script scrolling

Fast scrolling up and down in a comparable big script with opened Outline should not lead to crash or inconsistency in highlighting or outline anymore.

Verified


Testing workflow authentication

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Improve overall performance and utilization.

There are a number of potential improvements to this design, including changing the weight representation, leveraging sparsity, changing the number of weights-per-spin, etc.
For example, we could also replace the buffers with asynchronous up-down counters, but that may cause weird glitching, so it remains to be seen if that'll happen.
This is a long-term issue that will remain open even as PRs go in that help with utilization.

One major challenge here is that smaller versions of the architecture have relatively more synthesized LUTs in the oscillator path compared to manually placed LUTs. This appears to degrade performance.


[Add] DenseNets

What does this PR introduce?
Fixes #issue

Hello @DavianYang! Thanks for opening this PR.

In the file models/densenets/model.py:

Line 19:1: E302 expected 2 blank lines, found 1
Line 78:1: E302 expected 2 blank lines, found 1
Line 160:38: W292 no newline at end of file

In the file scripts/densenets/run.py:

Line 17:1: E302 expected 2 blank lines, found 1
Line 21:89: E501 line too long (112 > 88 characters)

Do see the Hitchhiker's guide to code style

Please replace accuracy with topk

Okie


Question: How to reuse and modify only few elements of json

Question: I have a big request json and for every test case I should only modify few elements in json.
I am trying to have one request json as common file for all tests and just modify the required elements for each test using def variable. Is it possible? IF yes, please let me know how.
I tried a few approaches and that didn't work.

look at the set examples at the end. this is for beta version <IP_ADDRESS>
https://github.com/intuit/karate/blob/develop/karate-junit4/src/test/java/com/intuit/karate/junit4/demos/js-arrays.feature

Excellent. It's very useful. When is this release planned?  I will put all my tests (depending on this enhancement) on hold and resume once you release the changes.Thanks!

you can actually start using <IP_ADDRESS> so you don't need to put anything on hold. but expect a final release within 2 weeks.


Crash when completing chapters/bounds in FTB quests

For example: Deploy..Deploy..Deploy..

This stat doesn't exist anymore, it was changed in 1.17. You'll want to change it to play_time, which is "Time played".

👀

Pog.

This is actually still an issue, because there's two places where play_one_minute still show up; once in overview.snbt (in chapter 5) and one in stage_4.snbt (I don't remember what this file is for)


Ensure we always point to streams.lab in README's

There are some READMEs where we still point to all, non-working endpoints. We need to fix that to point to streams.lab
Example
https://github.com/FIWARE/dataModels/tree/master/specs/Environment/AirQualityObserved
we are pointing to
curl -S -H 'fiware-service:airquality' -H 'fiware-servicepath:/Spain_Madrid' -H 'x-auth-token:<my_token>' "http://<IP_ADDRESS>:1027/v2/entities?options=keyValues&q=dateObserved:2016-11-28T12:00;stationCode:'28079004'"
which does not exist ...

The same situation as in https://github.com/FIWARE/dataModels/issues/477
It's better to split into several steps:

change already refactored harvesters and change available links
refactor other harvesters
change other links.

closing


Automated cherry pick of #2230: 对 actionlog 的 tenent_id 字段加索引，提升 actionlog 查询速率

Cherry pick of #2230 on release/2.11.
#2230: 对 actionlog 的 tenent_id 字段加索引，提升 actionlog 查询速率

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@966ac58). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.11   #2232   +/-   ##
==============================================
  Coverage                ?   7.08%
==============================================
  Files                   ?     452
  Lines                   ?   71212
  Branches                ?       0
==============================================
  Hits                    ?    5046
  Misses                  ?   65748
  Partials                ?     418

Flag
Coverage Δ

#aFlag
7.08% <ø> (?)

Impacted Files
Coverage Δ

pkg/cloudcommon/db/opslog.go
2.66% <ø> (ø)

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 966ac58...8fe37c3. Read the comment docs.

/lgtm
/approve


mention notifications separately from other notifications

Currently, if a user tags you in a comment, you are notified in the same way as if a new comment was posted on a question you're following. This means that such notifications might get lost and also makes conversations slower as the new comment notifications are sent every hour.
I'm proposing to bring the old system of notifications back, where you got separate emails for them that weren't bundled with the new comment emails and they were instant.

Will be done in #1006.


Lambda direct resolver event type

Adding lambda direct resolver request event to be used in cased where we are not using direct vtl integrations and require to be able to handle the event in a lambda. I have used this same event for months in production and it has worked out great.

Codecov Report

Merging #465 (e542405) into main (0f46684) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #465   +/-   ##
=======================================
  Coverage   69.69%   69.69%
=======================================
  Files          20       20
  Lines        1201     1201
=======================================
  Hits          837      837
  Misses        297      297
  Partials       67       67

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I added another test but the code coverage is not passing. Could anyone let me know why so I can amend the tests.

The coverage is fine - its the linter check that's failing

events/appsync.go:69: File is not gofmt-ed with -s (gofmt)

Also, got a link to the AWS docs for this integration that I can use as a reference for reviewing this PR?

The coverage is fine - its the linter check that's failing

events/appsync.go:69: File is not gofmt-ed with -s (gofmt)

Thank you @bmoffatt, sorry I was readying the actions wrong.
I am not getting an error when I run gofmt -s -w . on the directory. Can you see anything that I am doing wrong?

@bmoffatt here is a link to the direct lambda resolver docs
https://docs.aws.amazon.com/appsync/latest/devguide/resolver-context-reference.html
Note that some types need to be map[string]interface{} because there are many different options, such as identity

@joshpauline do you plan to continue this one? #467 has been opened to add the same struct


Restore some object safety and remove R in traits

This is entirely cleanup-related; we currently have many avoidable losses of object safety, as well as random (no pun intended) Rs popping up in traits as generics.
The latter is a big issue, because it prevents type-safe code generation that creates code like this:
enum ReactorEvent {
   MyComponent(<MyComponent as Component<Self>>::Event)
}

The example above is impossible in the current codebase, as it would require a Component<Self, R>, without any R being available.
Status: Currently aiming to get some early feedback from the CI while I continue to refactor.

bors r+

bors r+


Provide test macro like #[tokio::test] or #[runtime::test]

As as the title says, async_std should provide macro like  #[async_std::test] similar to #[tokio::test] or #[runtime::test] for writing tests.

While the test macro is some sweet sugar, I find task::block_on() not much worse when it comes to ergonomics. Compare:
#[async_std::test]
async fn foo() {
    // ...
}

#[test]
fn foo() {
    task::block_on(async {
        // ...
    })
}

That said, I wouldn't be against adding a #[async_std::test] attribute similar to #[std::test].

Yes, the block_on is close, but macro feel more natural IMO. Also, block_on version has more boilerplate.

@95th compile times would likely spike significantly if we included such a macro. Perhaps it would make sense to create as a separate package (perhaps under the org) that's not necessarily part of the same top-level crate.
In my opinion the main benefit of such macros is when abstracting over different systems; in particular between different execution styles. This isn't quite in scope for the async-std crate yet, but it might be in the future, and getting ahead of that isn't necessarily a bad thing imo. As long as we can stick to the driving vision of: "we provide an async version of std".

@skade The pattern you described above is still looks better better with macro IMHO:
#[runtime::test]
fn test() {
   // future construction
   let x = task::spawn(fut1);
   let y = task::spawn(fut2);
   x.await;
   y.await;
}

it avoids running into annoying situations like this being a block_on in a block_on if we had such a test annotation

Agreed.

In my opinion the main benefit of such macros is when abstracting over different systems; in particular between different execution styles.

For us, the only benefit of the #[test] macro is sugar.
But I think #[bench] would have another additional benefit. The following is not the best way of benchmarking things:
#[bench]
fn benchmark(b: &mut Bencher) {
    b.iter(|| {
        task::block_on(async {
            // ...
        })
    })
}

The reason is that block_on currently spawns a task and then awaits it (which is costly!), rather than polling the future on the current thread. But I think we'll change the behavior of block_on so that it does poll the future on the current thread without spawning. That would also remove the F: Send bound from block_on.
We can then try:
#[bench]
fn benchmark(b: &mut Bencher) {
    task::block_on(async {
        b.iter(|| {
            // ...
        })
    })
}

Still, that is not yet there because a future polled outside the runtime interacting with the reactor and the executor will be slower than one that is spawned onto the executor.
So then the proper way of benchmarking tasks becomes:
#[bench]
fn benchmark(b: &mut Bencher) {
    task::block_on(task::spawn(async {
        b.iter(|| {
            // ...
        })
    }))
}

Except one has to really think about this whenever benchmarking stuff in order to not get misleading numbers.
So the summary is that an attribute is not only syntax sugar; it also provides the optimal benchmarking setup.

async-attributes now exists, which adds support for all the features discussed in this issue (including @stjepang's correct bench code).
You can get it from crates.io. Thanks all!


Fix notifications in Firefox by calling the constructor with 'new'

Calling the browser notification constructor without the new keyword throws an error that prevents the notification from being displayed.
cc @bgilbert who found this bug and helped fix/test

Automated message from Dropbox CLA bot
@alliejones, it looks like you've already signed the Dropbox CLA. Thanks!

Great, thanks for fixing this!  I squashed the two commit together and am merging.


Add trailing backslash to fix "not a directory" error

Running this Dockerfile on Fedora 22 throws a "not a directory" error when it reaches "ADD cert/cert.pem /cert". Adding a backslash to the path resolves the issue.

Good point! Thank you for the fix.
I guess this is the reason of the error:

If <dest> does not end with a trailing slash, it will be considered a regular file and the contents of <src> will be written at <dest>.
-- https://docs.docker.com/engine/reference/builder/

Thank you for the script! Very helpful.
On Tue, Jan 5, 2016 at 5:07 PM Yi EungJun<EMAIL_ADDRESS>wrote:

Merged #1 https://github.com/npcode/mattermost-docker/pull/1.
—
Reply to this email directly or view it on GitHub
https://github.com/npcode/mattermost-docker/pull/1#event-506590673.


The new registry sync format.

This issue pertains to discussion about the new registry sync format.
There have been a few issues with the registry sync fabric uses that causes it to reach the maximum packet size quickly.
A few of these issues include:

The overhead of the NBT format in serialization for the packet
The inclusion of the namespace inside all Minecraft namespaced identifiers.
The map structure of the packet using key -> value for every namespace and string takes up extra room.
Where a sequence of all identifiers inside the packet are of the same namespace, the namespace is included in the identifier.
Some registries get many more registrations than others, meaning just a few registries in the same packet fill up the entire payload of the packet.
Overloaded registries cannot be split if they hit the max payload size.

Given the above issues, I feel we can greatly reduce the size of the packet with some optimizations.

Suggestion for a "common registry" packet structure:
struct rsync_packet_common {
    mc_id registry;
    int namespace_count;
    rsync_packet_common_namespace[] namespaces;
}

struct rsync_packet_common_namespace {
    int size;
    string namespace;
    string[] paths;
    int[] ids;
}

This is efficient for things like the block/item registries which get many registrations in many namespaces (the segmented nature allows multiple namespaces to be sent in one packet, should the namespaces be small enough).

Registry synchronization PR has been merged, which comes already with a new format for Quilt.


Moves methods comment into docstring and remove trailing whitespaces

Only cosmetic stuff, but at least pylint usually complains whenever it finds method without docstring or trailing whitespace on code lines. So this pull request doesn't bring any additional functionality, but eliminates some of the comments that pylint would throw about this code.

Hey @jylitalo thanks a lot. Can you open a PR against this repo instead? MPG CloudFrunt
I'm going to reconfigure this @disloops CloudFrunt repo so that the MPG one is upstream. I've merged a couple PRs there already.


fix: e2e test and relational generator dependencies, fixes #3344

Description of changes:

fix: update to proper dependency for subscription testing in e2e
fix #3344 which is a regression dependency from previous change

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #3352 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3352   +/-   ##
=======================================
  Coverage   60.09%   60.09%
=======================================
  Files         254      254
  Lines       12451    12451
  Branches     2578     2578
=======================================
  Hits         7483     7483
  Misses       4631     4631
  Partials      337      337

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 0d8cadc...32ef7b3. Read the comment docs.


Create an internal plugin infrastructure

This PR is a WIP to create an internal plugin infrastructure. Once it is stable "enough" it could be exposed as an API to a project using Sagui.
The first internal (build) plugins are:

Babel
CSS Modules
ESLint
JSON
Media: images and fonts
Pages: support multiple page outputs
SCSS

The internal plugin infrastructure is used to setup the entire Sagui environment, loading user preferences, setting up paths, the test runner (Karma) and the builder (Webpack).
It still requires some remaining cleaning work and documentation before it can be merged.

Looks neat. I guess the main question would be how to add a plugin to sagui, and where the plugin would reside.

So the idea is that a user can setup Sagui in two different ways:
Configuration
By creating a file sagui.config.js you can leverage the existing plugins by providing some static configuration:
module.exports = {
  pages: ['index', 'demo']
}

The configuration is loaded before any plugin is processed.
Extension
Extension is a much powerful feature, by creating a file sagui.extension.js, the user has access to the entire runtime environment of Sagui, allowing extension of pretty much anything (such as webpack configuration). It works exactly like an internal plugin.
Here is an example of setting up an YAML loader:
module.exports = function (env, merge) {
  const webpackConfig = merge(env.webpackConfig, {
    module: {
      loaders: [
        {
          test: /\.(yaml)$/,
          loader: 'yaml-loader'
        }
      ]
    }
  })

  return Object.assign({}, env, { webpackConfig: webpackConfig })
}

In contrast with configuration, the extension is executed as the last step in the plugin chain, allowing the user to overwrite or add any extra configuration.

:+1:

On the subject of plugins I think it is important that we don't try to come up with a complete new ecosystem. We already have Babel, ESLint and Webpack which are very modular libraries that can be extended as any project see fit. To open-up a project like Sagui as another plugin ecosystem would be just a terrible mistake that would make the community ever more confused.
So, the problem with these tools is that it can become overwhelmingly complicated to setup everything to get started. The good thing is that the community is already comming up with solutions that address this problem via Babel's presets and ESLint's config extension for example.
This is the point where I think Webpack is still lacking a good solution, a "presets" support to use and compose, and extend on a project by project base.
With that in mind, I'll try in a next iteration of this PR not to hide away these tools, but rather provide their native configuration methods while extending Sagui's defaults.
As the next steps of this PR, I'll toy around the idea of:

A sagui.webpack.config.js that would work the same way as a regular webpack configuration file, but inheriting the default stuff from Sagui;
Extract away Sagui's ESLint and Babel configuration as external packages.

We still have Karma, but I'll leave that for another moment.


Thunk withExtraArgument

Hey Guys,
Thanks for this useful tool. I was wondering if there is any way to pass extra arguments to thunk? Similar to:
const store = createStore(   reducer,   applyMiddleware(thunk.withExtraArgument(api)) )
Thanks

It is supported, but not released on npmjs.  #9 added it way back.
I chose a recent fork for my devDep.
Use it like this:
    const extraArgument = { sdk: SDK };
    const dispatches = await Thunk(
      clientDuck.fetchAll,
      extraArgument
    ).execute();
    each(dispatches, spatch => {
      console.log(spatch.getAction());
    });


Chinese character display in context menu

Description
System language is Chinese (simplified). Using Huorong Security software (https://www.huorong.cn/) some entries will be put in the context menu. And sometimes (by this I mean not always) some of them can't be displayed properly. Other programs and Chinese context menu entries are likely to have the same problem randomly. I doubt it is a char encoding issue. Hope to see a fix in future version.
Steps To Reproduce
Right click on any file or directory, scroll down, and will see the wrong char in the list.
Expected behavior
A correct display of these Chinese characters
Files Version
<IP_ADDRESS>
Windows Version
10.0.22000.376
Relevant Assets/Logs
debug_fulltrust.log
debug.log

@KingfuChan can you upload a screenshot?

Well I have to wait until next time I see this bug. It's really random and I have no idea if it is Files to blame.

Merging with #7389


// @ts-check doesn't know Web Bluetooth and Generic Sensors

I get errors for navigator.bluetooth Accelerometer, Magnetometer etc.
If you can tell me where this can be added and how to, we can supply PRs

This issue was moved to Microsoft/TSJS-lib-generator#294

As a workaround, try installing these the typings for web bluetooth manually: npm install --save-dev @types/web-bluetooth


handle server-only tests

Add server-side tests.
To do so, just name your test file [name].server.test.[ext] and Jest will automatically run it using node instead of jsdom.
Closes #85

Nice! Same question than for Next, can you check that there is no server only test? I guess in the "VN" unit tests, there might be some like testing the mongo connection.


outlier detection destination rule didn't work

Bug description
Hi, guy, I met a probelem about istio's  outlier detection, when I use the office example httpbin and fortio to test the outlier_detection,  it wasn't work, I have seen some report in this github, but not the right answer, could you help me?
the httpbin.yaml

[root@ecs-5274-0318501 httpbin]# cat httpbin.yaml
# Copyright 2017 Istio Authors
#
#   Licensed under the Apache License, Version 2.0 (the "License");
#   you may not use this file except in compliance with the License.
#   You may obtain a copy of the License at
#
#       http://www.apache.org/licenses/LICENSE-2.0
#
#   Unless required by applicable law or agreed to in writing, software
#   distributed under the License is distributed on an "AS IS" BASIS,
#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#   See the License for the specific language governing permissions and
#   limitations under the License.

##################################################################################################
# httpbin service
##################################################################################################
apiVersion: v1
kind: Service
metadata:
  name: httpbin
  labels:
    app: httpbin
spec:
  ports:
  - name: http
    port: 8000
    targetPort: 80
  selector:
    app: httpbin
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: httpbin
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: httpbin
        version: v1
    spec:
      containers:
      - image: <IP_ADDRESS>:10004/library/kennethreitz/httpbin
        imagePullPolicy: IfNotPresent
        name: httpbin
        ports:
        - containerPort: 80

the destinetion rule:

[root@ecs-5274-0318501 httpbin]# cat httpbin-destinationrule.yaml
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: httpbin
spec:
  host: httpbin
  trafficPolicy:
    #connectionPool:
    #  tcp:
    #    maxConnections: 1
    #  http:
    #    http1MaxPendingRequests: 1
    #    maxRequestsPerConnection: 1
    outlierDetection:
      baseEjectionTime: 1m
      consecutiveErrors: 1
      maxEjectionPercent: 100
      minHealthPercent: 0
      #consecutiveErrors: 1
      #interval: 1s
      #baseEjectionTime: 3m
      #maxEjectionPercent: 100

when I tested the outlierDetection though fortio, it wasn't work, the results were below:

[root@ecs-5274-0318501 httpbin]# kubectl exec -it fortio-deploy-b5958f8cc-655jd -n istio-test  -c fortio /usr/bin/fortio -- load -c 3 -qps 0 -n 30 -loglevel Warning  http://httpbin:8000/status/502
13:02:41 I logger.go:97> Log level is now 3 Warning (was 2 Info)
Fortio 1.3.1 running at 0 queries per second, 16->16 procs, for 30 calls: http://httpbin:8000/status/502
Starting at max qps with 3 thread(s) [gomax 16] for exactly 30 calls (10 per thread + 0)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
13:02:41 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
Ended after 18.242209ms : 30 calls. qps=1644.5
Aggregated Function Time : count 30 avg 0.001717947 +/- 0.001055 min 0.000901202 max 0.005225748 sum 0.051538409
# range, mid point, percentile, count
>= 0.000901202 <= 0.001 , 0.000950601 , 16.67, 5
> 0.001 <= 0.002 , 0.0015 , 86.67, 21
> 0.002 <= 0.003 , 0.0025 , 90.00, 1
> 0.004 <= 0.005 , 0.0045 , 96.67, 2
> 0.005 <= 0.00522575 , 0.00511287 , 100.00, 1
# target 50% 0.00147619
# target 75% 0.00183333
# target 90% 0.003
# target 99% 0.00515802
# target 99.9% 0.00521898
Sockets used: 30 (for perfect keepalive, would be 3)
Code 502 : 30 (100.0 %)
Response Header Sizes : count 30 avg 0 +/- 0 min 0 max 0 sum 0
Response Body/Total Sizes : count 30 avg 245 +/- 0 min 245 max 245 sum 7350
All done 30 calls (plus 0 warmup) 1.718 ms avg, 1644.5 qps
You have mail in /var/spool/mail/root

the fortio s outlierDetection  configuration:

     "cluster": {
      "name": "outbound|8000||httpbin.istio-test.svc.cluster.local",
      "type": "EDS",
      "eds_cluster_config": {
       "eds_config": {
        "ads": {},
        "initial_fetch_timeout": "0s"
       },
       "service_name": "outbound|8000||httpbin.istio-test.svc.cluster.local"
      },
      "connect_timeout": "10s",
      "circuit_breakers": {
       "thresholds": [
        {
         "max_retries": 1024
        }
       ]
      },
      "outlier_detection": {
       "base_ejection_time": "60s",
       "max_ejection_percent": 100,
       "enforcing_consecutive_5xx": 0,
       "consecutive_gateway_failure": 1,
       "enforcing_consecutive_gateway_failure": 100
      },

Is there something I missed?  could you give me some ideas? thank you.
Expected behavior
hope outlier detection destination rule can set success
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
How was Istio installed?
accroding to office document
Environment where bug was observed (cloud vendor, OS, etc)

[root@ecs-5274-0318501 httpbin]# istioctl version
client version: 1.2.2
citadel version: 1.2.2
egressgateway version: 1.2.2
galley version: 1.2.2
ingressgateway version: 1.2.2
pilot version: 1.2.2
policy version: 1.2.2
sidecar-injector version: 1.2.2
telemetry version: 1.2.2

if I set  connectionPool, it was okay, but also outlierDetection didn't work, it was so strange.

[root@ecs-5274-0318501 httpbin]# kubectl exec -it fortio-deploy-b5958f8cc-655jd -n istio-test    -c fortio /usr/bin/fortio -- load -c 3 -qps 0 -n 30 -loglevel Warning  http://httpbin.istio-test:8000/status/502
14:40:33 I logger.go:97> Log level is now 3 Warning (was 2 Info)
Fortio 1.3.1 running at 0 queries per second, 16->16 procs, for 30 calls: http://httpbin.istio-test:8000/status/502
Starting at max qps with 3 thread(s) [gomax 16] for exactly 30 calls (10 per thread + 0)
14:40:33 W http_client.go:679> Parsed non ok code 503 (HTTP/1.1 503)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 503 (HTTP/1.1 503)
14:40:33 W http_client.go:679> Parsed non ok code 503 (HTTP/1.1 503)
14:40:33 W http_client.go:679> Parsed non ok code 503 (HTTP/1.1 503)
14:40:33 W http_client.go:679> Parsed non ok code 503 (HTTP/1.1 503)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 503 (HTTP/1.1 503)
14:40:33 W http_client.go:679> Parsed non ok code 503 (HTTP/1.1 503)
14:40:33 W http_client.go:679> Parsed non ok code 503 (HTTP/1.1 503)
14:40:33 W http_client.go:679> Parsed non ok code 503 (HTTP/1.1 503)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
14:40:33 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
Ended after 22.945576ms : 30 calls. qps=1307.4
Aggregated Function Time : count 30 avg 0.0017834201 +/- 0.00133 min 0.000170206 max 0.005175701 sum 0.053502603
# range, mid point, percentile, count
>= 0.000170206 <= 0.001 , 0.000585103 , 30.00, 9
> 0.001 <= 0.002 , 0.0015 , 66.67, 11
> 0.002 <= 0.003 , 0.0025 , 86.67, 6
> 0.003 <= 0.004 , 0.0035 , 90.00, 1
> 0.004 <= 0.005 , 0.0045 , 96.67, 2
> 0.005 <= 0.0051757 , 0.00508785 , 100.00, 1
# target 50% 0.00154545
# target 75% 0.00241667
# target 90% 0.004
# target 99% 0.00512299
# target 99.9% 0.00517043
Sockets used: 30 (for perfect keepalive, would be 3)
Code 502 : 21 (70.0 %)
Code 503 : 9 (30.0 %)
Response Header Sizes : count 30 avg 0 +/- 0 min 0 max 0 sum 0
Response Body/Total Sizes : count 30 avg 243.8 +/- 1.833 min 241 max 245 sum 7314
All done 30 calls (plus 0 warmup) 1.783 ms avg, 1307.4 qps
You have mail in /var/spool/mail/root

[root@ecs-5274-0318501 httpbin]# cat httpbin-destinationrule.yaml
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: httpbin
spec:
  host: httpbin
  trafficPolicy:
    connectionPool:
      tcp:
        maxConnections: 1
      http:
        http1MaxPendingRequests: 1
        maxRequestsPerConnection: 1
    outlierDetection:
      baseEjectionTime: 1m
      consecutiveErrors: 1
      maxEjectionPercent: 100
      minHealthPercent: 0
      #consecutiveErrors: 1
      #interval: 1s
      #baseEjectionTime: 3m
      #maxEjectionPercent: 100
  subsets:
    - labels:
        version: v1
      name: v1

@hzxuzhonghu hi, dear, could you give me some ideas?  thank you.

I recommend you to read carefully about the envoy doc
The number of hosts in a cluster that must have enough request volume to detect success rate outliers. If the number of hosts is less than this setting, outlier detection via success rate statistics is not performed for any host in the cluster. Defaults to 5.

https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/cluster/outlier_detection.proto#envoy-api-field-cluster-outlierdetection-success-rate-minimum-hosts

@hzxuzhonghu okay, thank you for your advice, I will read it carefully in a period of time.

does it means I should set the httpbin deployment replica gt 5 so that outlier detection can success ? I'm not sure I understand it right.
so I config the replica to 6, but it also didn't work, for details, see below:

[root@ecs-5274-0318501 ~]# kubectl get deploy -n istio-test
NAME            READY   UP-TO-DATE   AVAILABLE   AGE
fortio-deploy   1/1     1            1           10d
httpbin         6/6     6            6           10d
v1-service      1/1     1            1           16h
[root@ecs-5274-0318501 ~]# kubectl get pod -n istio-test
NAME                            READY   STATUS    RESTARTS   AGE
fortio-deploy-b5958f8cc-655jd   2/2     Running   0          10d
httpbin-867cbdf97b-4j62f        2/2     Running   0          34m
httpbin-867cbdf97b-8chjf        2/2     Running   0          34m
httpbin-867cbdf97b-cbpk6        2/2     Running   0          34m
httpbin-867cbdf97b-cfj4q        2/2     Running   0          34m
httpbin-867cbdf97b-gm9wt        2/2     Running   0          34m
httpbin-867cbdf97b-hjnpz        2/2     Running   0          10d
v1-service-ccc54bcbb-pm5kg      2/2     Running   0          16h

the dr  yaml is:

[root@ecs-5274-0318501 ~]# kubectl get dr httpbin -o yaml -n istio-test
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"networking.istio.io/v1alpha3","kind":"DestinationRule","metadata":{"annotations":{},"name":"httpbin","namespace":"istio-test"},"spec":{"host":"httpbin","subsets":[{"labels":{"version":"v1"},"name":"v1"}],"trafficPolicy":{"connectionPool":{"http":{"http1MaxPendingRequests":1024,"maxRequestsPerConnection":1024},"tcp":{"maxConnections":1024}},"outlierDetection":{"baseEjectionTime":"1m","consecutiveErrors":1,"maxEjectionPercent":100,"minHealthPercent":0}}}}
  creationTimestamp: "2020-02-24T12:27:29Z"
  generation: 9
  name: httpbin
  namespace: istio-test
  resourceVersion: "60168558"
  selfLink: /apis/networking.istio.io/v1alpha3/namespaces/istio-test/destinationrules/httpbin
  uid: 05c0205d-5701-11ea-b333-4eb0d5f6e7df
spec:
  host: httpbin
  subsets:
  - labels:
      version: v1
    name: v1
  trafficPolicy:
    outlierDetection:
      baseEjectionTime: 1m
      consecutiveErrors: 1
      interval: 1s
      maxEjectionPercent: 100
      minHealthPercent: 0

I  found a parameters success_rate_request_volume UInt32Value) The minimum number of total requests that must be collected in one interval (as defined by the interval duration above) to include this host in success rate based outlier detection. If the volume is lower than this setting, outlier detection via success rate statistics is not performed for that host. Defaults to 100   in https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/cluster/outlier_detection.proto#envoy-api-field-cluster-outlierdetection-success-rate-minimum-hosts, so I've increased my requests number, see below:

[root@ecs-5274-0318501 ~]# kubectl exec -it fortio-deploy-b5958f8cc-655jd -n istio-test  -c fortio /usr/bin/fortio -- load -c 3 -qps 0 -n 500  -loglevel Warning  http://httpbin:8000/get
02:58:23 I logger.go:97> Log level is now 3 Warning (was 2 Info)
Fortio 1.3.1 running at 0 queries per second, 16->16 procs, for 500 calls: http://httpbin:8000/get
Starting at max qps with 3 thread(s) [gomax 16] for exactly 500 calls (166 per thread + 2)
Ended after 236.428746ms : 500 calls. qps=2114.8
Aggregated Function Time : count 500 avg 0.0013972727 +/- 0.0005947 min 0.001077253 max 0.006477875 sum 0.698636344
# range, mid point, percentile, count
>= 0.00107725 <= 0.002 , 0.00153863 , 94.80, 474
> 0.002 <= 0.003 , 0.0025 , 97.00, 11
> 0.003 <= 0.004 , 0.0035 , 98.40, 7
> 0.004 <= 0.005 , 0.0045 , 99.60, 6
> 0.006 <= 0.00647788 , 0.00623894 , 100.00, 2
# target 50% 0.00156301
# target 75% 0.00180687
# target 90% 0.00195318
# target 99% 0.0045
# target 99.9% 0.00635841
Sockets used: 3 (for perfect keepalive, would be 3)
Code 200 : 500 (100.0 %)
Response Header Sizes : count 500 avg 230 +/- 0 min 230 max 230 sum 115000
Response Body/Total Sizes : count 500 avg 601 +/- 0 min 601 max 601 sum 300500
All done 500 calls (plus 0 warmup) 1.397 ms avg, 2114.8 qps
You have mail in /var/spool/mail/root

after that, I set a secries fault `status 502` request

[root@ecs-5274-0318501 ~]# kubectl exec -it fortio-deploy-b5958f8cc-655jd -n istio-test  -c fortio /usr/bin/fortio -- load -c 3 -qps 0 -n 5  -loglevel Warning  http://httpbin:8000/status/502
03:01:18 I logger.go:97> Log level is now 3 Warning (was 2 Info)
Fortio 1.3.1 running at 0 queries per second, 16->16 procs, for 5 calls: http://httpbin:8000/status/502
Starting at max qps with 3 thread(s) [gomax 16] for exactly 5 calls (1 per thread + 2)
03:01:18 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
03:01:18 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
03:01:18 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
03:01:18 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
03:01:18 W http_client.go:679> Parsed non ok code 502 (HTTP/1.1 502)
Ended after 10.111522ms : 5 calls. qps=494.49
Aggregated Function Time : count 5 avg 0.003791451 +/- 0.0007009 min 0.002936993 max 0.004481769 sum 0.018957255
# range, mid point, percentile, count
>= 0.00293699 <= 0.003 , 0.0029685 , 40.00, 2
> 0.004 <= 0.00448177 , 0.00424088 , 100.00, 3
# target 50% 0.00408029
# target 75% 0.00428103
# target 90% 0.00440147
# target 99% 0.00447374
# target 99.9% 0.00448097
Sockets used: 5 (for perfect keepalive, would be 3)
Code 502 : 5 (100.0 %)
Response Header Sizes : count 5 avg 0 +/- 0 min 0 max 0 sum 0
Response Body/Total Sizes : count 5 avg 245 +/- 0 min 245 max 245 sum 1225
All done 5 calls (plus 0 warmup) 3.791 ms avg, 494.5 qp

finally, I tested the outlier detection, but it also didn't work , was there something I missed?

[root@ecs-5274-0318501 ~]# kubectl exec -it fortio-deploy-b5958f8cc-655jd -n istio-test  -c fortio /usr/bin/fortio -- load -c 3 -qps 0 -n 5  -loglevel Warning  http://httpbin:8000/get
03:04:21 I logger.go:97> Log level is now 3 Warning (was 2 Info)
Fortio 1.3.1 running at 0 queries per second, 16->16 procs, for 5 calls: http://httpbin:8000/get
Starting at max qps with 3 thread(s) [gomax 16] for exactly 5 calls (1 per thread + 2)
Ended after 8.981688ms : 5 calls. qps=556.69
Aggregated Function Time : count 5 avg 0.0035860942 +/- 0.001204 min 0.00174051 max 0.004639149 sum 0.017930471
# range, mid point, percentile, count
>= 0.00174051 <= 0.002 , 0.00187025 , 20.00, 1
> 0.002 <= 0.003 , 0.0025 , 40.00, 1
> 0.004 <= 0.00463915 , 0.00431957 , 100.00, 3
# target 50% 0.00410652
# target 75% 0.00437284
# target 90% 0.00453262
# target 99% 0.0046285
# target 99.9% 0.00463808
Sockets used: 3 (for perfect keepalive, would be 3)
Code 200 : 5 (100.0 %)
Response Header Sizes : count 5 avg 230 +/- 0 min 230 max 230 sum 1150
Response Body/Total Sizes : count 5 avg 601 +/- 0 min 601 max 601 sum 3005
All done 5 calls (plus 0 warmup) 3.586 ms avg, 556.7 qps