interrupt: Support no-std pre-v6 ARM targets

Closes #26
This currently disables only IRQs. This is explained in the document on safety requirements:

On pre-v6 ARM, this currently disables only IRQs.
Enabling this cfg in an environment where FIQs must also be disabled is also considered unsound.

I have a few questions:

Should we also disable FIQs? The emulation of atomic operation on Linux seemed to disable only IRQs, but they may have disabled FIQs globally. EDIT: see https://github.com/taiki-e/portable-atomic/pull/28#issuecomment-1214146912
Is there a way to test this target on CI?

I think it is okay that we only disable the I bit because in some environments the F bit seems not to be able to be changed. Also, it seems that only IRQ is used in GBA.

bors r+
Test passed locally.

Your readme should likely note that this does not work in User mode.

https://github.com/taiki-e/portable-atomic#optional-cfg

This uses privileged instructions to disable interrupts, so it usually doesn't work on unprivileged mode. Enabling this cfg in an environment where privileged instructions are not available is also usually considered unsound, although the details are system-dependent.

Oh, i only looked at the lines that the PR diff highlighted in green XD

I just wanted to say that this is really cool and much appreciated!
As for running mGBA in "headless" mode, you can take a look at how agb compiles and uses its mgba-test-runner.

Thanks @Jinxit! I will look into mgba-test-runner.


[WIP] Multithreading inference.

Description
(Brief description on what this PR is about)
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Shouldn't we hide this abstraction from our users? The engine should be smart enough to determine when to multithread - the APIs just have to support concurrent calls.

This PR is mainly for demo.
For your comments, I think it's necessary to expose the number of threads for parallel inference. The computation in an executor is parallelized itself. This gives another option for parallelization along with parallelism in an executor. It's hard for a system to figure. Users should try and decide.


Rewriting graphics functions to support other rendering engines

Hello!
I'm using weathermap for few maps that are over 5k x 5k pixels in size and in my opinion it's time to rewrite code to use another rendering engine to make it look more fresh. I wonna replace all function calls with something like RE[::|->]filledarc(...) (RE for Render Engine).
Is now good time to fork project and replace that code or it's better for me to write those render engine class and write script to rewrite [by regex] all calls to graphics functions (to make it possible replacing calls in future versions of map)?

I'm halfway through a pretty major refactoring job, to pull a lot of code out of the WeatherMap class that shouldn't really be there. This includes new dedicated classes for link and scale drawing, too.
Agreed about the issues with gd. What did you have in mind as a replacement?

I'm going to write script, which will replace all gd function with static calls to some class and there I wonna call ImageMagick functions. IM library is a lot better at rendering everything - it generates smooth images with great antialiasing (and it's a little bit faster, but that's not my point).

OK - up to not that long ago, Weathermap actually had a wrapper around all the GD functions already, from when I experimented with Cairo and SVG... it wouldn't be that hard to put that back in. So then there would be a WMGraphics class and subclasses for GD, IM, Cairo etc. Font handling is probably going to be the tricky part - everything does that differently, and a few parts of weathermap expect to be able to get a bounding box for a string of text. It should be done so that nothing outside the rendering class needs to know about the specifics though - so probably not static calls, but some singleton object with the state of the graphics system.

It's exactly what I'm thinking about, the class can be singleton and
contain data for image to know what and with what to do.
My first version makes an static array with images and allow same calls as
with GD, where first argument it's just unique integer in that static array
simulating separate image resource. Bringing back wrapper is needed in my
opinion. Each subclass or implementation will get same data for fonts and
will have to use it's internal functions to get similiar result as with GD.
9 kwi 2015 11:27 "Howard Jones"<EMAIL_ADDRESS>napisał(a):

OK - up to not that long ago, Weathermap actually had a wrapper around all
the GD functions already, from when I experimented with Cairo and SVG... it
wouldn't be that hard to put that back in. So then there would be a
WMGraphics class and subclasses for GD, IM, Cairo etc. Font handling is
probably going to be the tricky part - everything does that differently,
and a few parts of weathermap expect to be able to get a bounding box for a
string of text. It should be done so that nothing outside the rendering
class needs to know about the specifics though - so probably not static
calls, but some singleton object with the state of the graphics system.
—
Reply to this email directly or view it on GitHub
https://github.com/howardjones/network-weathermap/issues/23#issuecomment-91172807
.

Firstly I'm going to create such thing:
class GraphicsEngine {
	public function __call($name, $args)
	{
		return call_user_func_array($name, $args);
	}
}

$ge = new GraphicsEngine;
$im = $ge->imagecreate(150, 250);

Then I will be able to set anything in $ge and handle it my way. Are you ok with that or should I write full class and do something like:
<?php

interface Renderer {
	public function createimage($w, $h);
}

class ImagickRenderer implements Renderer {
	private $images = array();

	public function createimage($w, $h)
	{
		$rid = uniqid();
		$this->images[$rid] = new Imagick($w, $h, ImagePixel('white'));
		return $rid;
	}
}

?

Actually, I think it should be a full class. Here's why:

I'm in the process of moving all the geometry stuff to use WMPoint,
WMRectangle and WMVector classes instead of lots of loose x,y pairs. The
GraphicsEngine class should take those, and translate as necessary for
the actual backend.
Same thing with WMColour
Same thing with WMFont

Basically, I'm already working on hiding the detail of GD where I can,
and reducing the amount of repeated stuff in the main classes. So for
example imagerectangle should become something like
$ge->drawRectangle($rectangleObject, $colourObject), and it can deal
with those internally in a way that's appropriate for GD, SVG,
ImageMagick or whatever.
On 20/04/2015 18:57, Misiek wrote:

Firstly I'm going to create such thing:
class  GraphicsEngine  {
public  function  __call($name,$args)
{
return  call_user_func_array($name,$args);
}
}
$ge  =  new  GraphicsEngine;
$im  =  $ge->imagecreate(150,250);
Then I will be able to set anything in $ge and handle it my way. Are
you ok with that or should I write full class and do something like:
images[$rid]=  new  Imagick($w,$h, ImagePixel('white'));
         return  $rid;
     }
}

?

—
Reply to this email directly or view it on GitHub
.

If it's possible - let me know in this issue when code will be in good condition for extending to other rendering engines, so I can work on ImageMagick version.
Now I'm looking for someone with big map, who can give me access to data provided for map, so I can test my code. Maybe someone here is watching this repo and can help me?

OK - I'm still working through the very large methods in Node and Link.
I have a small collection of user maps - I've been meaning to do some search/replace to make them anonymous so they can be added to the repo as test inputs - I'll get those done (and of course if there are others that could be donated). I have been working on performance with a couple of users and have some test maps from them.
There's already a fairly complete set of tests for Weathermap output though - they work by pixel comparison, so they will fail with another rendering engine, but they do test most features. Check out the configs in test-suite/tests (and the expected outputs in test-suite/refererence). Your engine should be able to render all 160+ of those and get similar results.
I guess we'll have to update the testing code to test multiple graphics engines too. reference-gd, reference-imagemagick etc.

What do you think about using Imagine (repo)?


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/30564

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/31166

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/32880

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/43406

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/44663

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/44715

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/48138

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/75201


DPL-599 Prepare for upgrade Postgresql 14

Describe the Housekeeping
Systems are asking for upgrade postgresql database. This will require testing baracoda and check that code is compatible and performance doesnt decrease.
We are aiming to have this tests done by the end of january so they can perform the upgrade.
Blocking issues
Describe any other issues or tickets that may be blocking this change.
Additional context
Add any other context about the problem here.

Tasks

[ ] Check that all endpoints work as expected
[ ] Compare performance with previous version
[ ] Run the integration suite and check that all is ok
[ ] Plan how we are going to do the downtime for the upgrade


fix(module:select): fix option's selected hight-light

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

The rule of Select option is different from antd design's . The question is that highlight doesn't disappear when mouse leave the option selected.
Issue Number: N/A
What is the new behavior?
Hightlight will disappear as expected.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Hi, This Pull Request is going to be closed since no update for a long time, feel free to open a new PR if any new update.


Update fs functions for node 12.11.1

Testing https://github.com/nystudio107/generator-craftplugin/pull/94 locally was tricky. Stepping node back to 6.17.1 led to a bunch of breakages, and yo craftplugin nearly worked until fs interactions, which would throw errors to the tune of
+ Creating Craft plugin folder generic
events.js:187
      throw er; // Unhandled 'error' event
      ^

TypeError [ERR_INVALID_CALLBACK]: Callback must be a function. Received undefined
    at maybeCallback (fs.js:146:9)
    at Object.writeFile (fs.js:1245:14)
    at child.configuring (/path/to/generator-craftplugin/app/index.js:294:12)
    at /path/to/generator-craftplugin/node_modules/yeoman-generator/lib/base.js:429:16
    at processImmediate (internal/timers.js:439:21)
    at process.topLevelDomainCallback (domain.js:131:23)
Emitted 'error' event on child instance at:
    at /path/to/generator-craftplugin/node_modules/yeoman-generator/lib/base.js:437:14
    at processImmediate (internal/timers.js:439:21)
    at process.topLevelDomainCallback (domain.js:131:23)

Apparently fs methods differ slightly in node 12, so the changes in this PR allow yo craftplugin to work fully—and generate a plugin as expected—running node 12.11.1. (I alternatively tried updating the npm dependencies, but Yeoman 1.0 introduced breaking changes I wasn’t immediately sure how to resolve.)
Submitting as a PR since I’m not sure what kind of terrors this could introduce for pluginfactory.io.

...and this is a duplicate of https://github.com/nystudio107/generator-craftplugin/pull/92.


PCC Error on Resnet50 on Blackhole

Need to identify the ops causing PCC error:
conv2d has good PCC with BFLOAT16
conv2d has bad PCC with BFLOAT8_B
maxpool2d has good PCC with both BFLOAT16 and BFLOAT8_B

Latest: Debugging conv2d with BFLOAT8_B, simplest case on 1 core:
Branch: asarje/bh-rn50-test
pytest "tests/ttnn/unit_tests/operations/test_new_conv2d.py::test_resnet50_conv_wh[no_auto_shard-no_bias-no_pack_l1-math_fidelity=MathFidelity.LoFi-activations_dtype=DataType.BFLOAT8_B-weights_dtype=DataType.BFLOAT8_B-batch_size=1-output_channels=32-input_channels=32-input_height=4-input_width=4-filter_height=3-filter_width=3-stride_h=1-stride_w=1-pad_h=0-pad_w=0-use_1d_systolic_array=False-config_override={'num_cores_nhw': 1}-device_params={'l1_small_size': 16384}]"

All data looks good as it comes out of the conv op (checked the dst register output -- looks good, also checked conv op output tensor -- looks good). Likely issue with TMs. Need to confirm.

Tracking Conv2D PCC issue separately here: #15396.


feat: Implemented semantic release

The Issue
Current release flow is manual. Since the semantic commits are already in place - it can be vastly improved by using an automated release process depending on the commit type.
Having manual semantic versioning can cause unneeded major / minor version incrementation, and can cause wild release number jumps depending on the current commiter, working team, and personal style / coding preference.
The previous release flow has various steps which are manual and which are used to check the next version, analyze commits, and do all of the stuff a single npm package does automatically, in a simple, reliable and consistent manner.
How This PR Solves The Issue
Implements a semantic release flow with automatic changelog generation, and major / major.minor versioning for the marketplace action.
Using the semantic-release package automates the whole package release workflow including:

determining the next version number
generating the release notes
publishing the package

By using semantic versioning, there is no relation between human emotion and version numbers. Changelog generation is automatic, standardized, and links everything properly in various ways.
It also does comments on PRs, Issues, and discussions.
This PR simplifies the action development, and reduces maintenance time.
Manual Testing Instructions
None needed
Automated Testing Overview
Merging this pr will automatically bump the minor version.
Related Issue Link(s)
Release/Deployment Notes
Will improve deployment further on.

I think you'd have more success with things like this if you opened an issue first asking whether this would be welcome. When you just dive in with a PR you're assuming that people will automatically agree with your view of the world.
Then, when you make a PR, consider it your job to carefully explain why you're doing it, what the effects are, and why you think it's important. None of those things are done here.
Just because you know what you think should happen doesn't mean that others with either understand what you think or agree with it.

I think you'd have more success with things like this if you opened an issue first asking whether this would be welcome. When you just dive in with a PR you're assuming that people will automatically agree with your view of the world.
Then, when you make a PR, consider it your job to carefully explain why you're doing it, what the effects are, and why you think it's important. None of those things are done here.
Just because you know what you think should happen doesn't mean that others with either understand what you think or agree with it.

Edited the description

Far better, thanks.
I have in fact made a mistake with a release version on DDEV. It was unfortunate. Intended v1.20.1 and did v1.21.1 IIRC

Thank you for this PR and for introducing me to this semantic-release package.
I have several reasons for thinking that the current release process would have a hard time being replaced by a fully automatic one.
But it's an interesting subject, so I think I'll test this approach on a few of my personal projects.
And now, a few points that I think need to be discussed if we are to move in this direction:

the semantic commits are already in place

Well, there is a .githooks folder that aims to be used as a template for a commit-msg hook but we did not implemented any check to see if all commits respect the convention format. Could be something interesting to work on... Should be possible to check commit message for a pull request with some GitHub action but I don't know how to prevent badly formatted message for a direct push, for example.

there is no relation between human emotion and version numbers

To determine the next version number , I base myself on https://semver.org/spec/v2.0.0.html
a) One of the most important points is to define, as explicitly as possible, what the public API is. In the case of this project, I've defined the public API as being determined solely by the action.yaml file. This means that we need to be able to consider only modifications to this file for release changes: we need to be able to exclude commits to files not covered by the public API (docs, .githooks and tests folder, etc.).
b) It's true that with every release, I have to ask myself whether it's just a fix without breaking change (patch), a modification/addition without breaking change (minor), or a breaking change (major): it's a human decision, with all the risks that entails.
BUT, as far as I can read here: https://www.npmjs.com/package/semantic-release#how-does-it-work , semantic-release is using commit messages to determine the next release number. and these commit messages will have been written by humans ... For example, the responsibility for writing BREAKING CHANGE in the footer of the commit message will have been taken by a human; and I don't see much difference between that decision and the one I have to take now, every time I prepare to create a release.

To conclude, but this is more of a personal opinion, unfortunately too suggestive, I'm basing the changelog on this: https://keepachangelog.com/en/1.1.0/ and I like the guiding principle: "Changelogs are for humans, not machines.".
So I'm not too keen on seeing a list of commit messages in a changelog (a link with a version comparison seems sufficient for those interested in the details of each commit).

Thanks

I have in fact made a mistake with a release version on DDEV. It was unfortunate. Intended v1.20.1 and did v1.21.1 IIRC

I remember this one :)
And this is one of the reasons why, in most of the projects I maintain, I make sure to add the version number to certain files (README, CHANGELOG, others) so that I can perform a consistency check, during the release action, before creating the tag.
This reduces the chances (not to 0%, unfortunately) of publishing a wrong version number, because that would mean I'd made a mistake in several files...

Ok, let's take it from the top.

Well, there is a .githooks folder that aims to be used as a template for a commit-msg hook but we did not implemented any check to see if all commits respect the convention format.

This is easily done via husky and commitlint.
$ npm install husky --save-dev
$ npm pkg set scripts.prepare="husky install"
$ npm run prepare

.husky/commit-msg
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

npx commitlint --edit $1

.commitlintrc.json
{
  "extends": ["@commitlint/config-angular"],
  "rules": {
    "subject-case": [
      2,
      "always",
      ["sentence-case", "start-case", "pascal-case", "upper-case", "lower-case"]
    ],
    "type-enum": [
      2,
      "always",
      [
        "build",
        "chore",
        "ci",
        "docs",
        "feat",
        "fix",
        "perf",
        "refactor",
        "revert",
        "style",
        "test",
        "sample"
      ]
    ]
  }
}

Angular commit style enforced across all commits. Any contributor needs to follow the commit message standard. Enforced across forks, pull requests, and other workflows.

Could be something interesting to work on... Should be possible to check commit message for a pull request with some GitHub action but I don't know how to prevent badly formatted message for a direct push, for example.

No need to check anything via actions. Everything is done by husky and the commit-msg hook. Fully enforceable.
This is easily implementable and works OOB for everyone, everywhere

To determine the next version number , I base myself on https://semver.org/spec/v2.0.0.html

That is the semver spec, and is fully inline with semantic-release

a) One of the most important points is to define, as explicitly as possible, what the public API is. In the case of this project, I've defined the public API as being determined solely by the action.yaml file.

The public API is the action file. Feature changes add the minor version, fixes add patch, and breaking changes are incrementing the major version.

This means that we need to be able to consider only modifications to this file for release changes: we need to be able to exclude commits to files not covered by the public API (docs, .githooks and tests folder, etc.).

That's where the angular commit convention comes into play. Prefixes chore, docs, style, refactor will not make a new release. Commit type can be tweaked. So we can configure it any way we want. For example, maybe we want refactor to add the patch version. semantic-release can be configured that way

b) It's true that with every release, I have to ask myself whether it's just a fix without breaking change (patch), a modification/addition without breaking change (minor), or a breaking change (major): it's a human decision, with all the risks that entails.

There is always a human factor. Yes, developer should know beforehand what he intends to do and to mark it as such.

BUT, as far as I can read here: https://www.npmjs.com/package/semantic-release#how-does-it-work , semantic-release is using commit messages to determine the next release number. and these commit messages will have been written by humans ... For example, the responsibility for writing BREAKING CHANGE in the footer of the commit message will have been taken by a human; and I don't see much difference between that decision and the one I have to take now, every time I prepare to create a release.

The difference is - we switch over to git hooks and automated process, and we don't have to maintain separate actions for parsing the MD file, setting up changelog, etc. Everything is done automatically.
The decision what type of commit it is, and what's being coded is still on the developer.
There is just less maintanance all around. The release yml file has 150+ lines. Why should that be maintained, if it can be superceeded by 3 config files, and ready-made package which does the same (in a more consistent and reliable style)?

To conclude, but this is more of a personal opinion, unfortunately too suggestive, I'm basing the changelog on this: https://keepachangelog.com/en/1.1.0/ and I like the guiding principle: "Changelogs are for humans, not machines.".
So I'm not too keen on seeing a list of commit messages in a changelog (a link with a version comparison seems sufficient for those interested in the details of each commit).

IMHO, changelogs are unecessary - that's what release notes are for. One for every separate release, but I think that's subjective, and I'm open for a middle ground, or to defer to your call.
All in all to summarize.
Implementing semantic-release flow will:

Standardize deployments
Standardize commit messages
Reduce maintenance load on everyone
Introduce easy updates, since it will automatically update vX and vX.Y tags so people can just use major tags.

Here is an example of an action I wrote which uses the semantic-release process
https://github.com/better-php-actions/publish-composer-package

Thanks for these explanations.
Now that I have all the facts, I've decided not to merge this PR.
The main reason is that I don't want version numbers to depend on commit messages.
Thanks again.

No worries. I'll rollout my own 💪

https://github.com/oblakstudio/action-test-ddev-addon
I've also implemented some reusable workflows which I will document further.
https://github.com/oblakstudio/public-workflows/


Support for HTTP/2

Is your feature request related to a problem? Please describe.
OpenSearch currently only supports HTTP/1 which is a single request/response protocol. HTTP/2 allows multiple requests to be in progress at the same time on a single connection with the mechanism of streams. There are workarounds with HTTP/1 such as to maintain multiple open connections or to send fewer large requests (e.g. bulk API). Both has their own problems.
Describe the solution you'd like
HTTP/2 has been around for sometime and is supported in Netty. However, we need to do some work to make sure HTTP/2 works without any issue.
Describe alternatives you've considered
Keep using HTTP/1

@adnapibar @dblock would you mind if I pick it up? Did some work on Netty + HTTP/2 integration before


Library to support Telemetry.Metrics as OpenTelemetry metrics

Not ready because still using local changes in the deps but wanted to open it up for review while those changes are being merged and released.

Forgot I needed to make meter a per-metric option. Though that isn't actually going to work since the main purpose of this is supporting stuff like Phoenix which isn't going to add meter to the reporter opts of telemetry events...
So may just add a warning in the docs that Scope is going to be wrong for all your Telemetry.Metrics

@AndrewDryga yes, definitely! Are you on slack? I hit a bug in metrics that has kept me from having time to spend on docs but could help you on slack to get going.

WHOOPS. I started a job shortly after this and forgot about this PR, wow. Trying to resurrect it.

Marked as ready for review tho I don't remember if it really is. But based on the tests it has I guess it works, hehe.

I'm very interested in getting this merged. How can I help?

@ethangunderson  tried it by chance? That'd make it easier to feel confident merging.

@tsloughter I haven't yet, but I have the perfect app for it. I'll make time for it this week and report back.

Alright, a bit late, but I tried this out yesterday.
I have an existing application that uses the OTLP collectors from a Datadog agent. Traces work correctly, but I can't get metrics working. If I swap out the reader for otel_metric_exporter_pid, I do see the expected metrics in my console, so this is probably a DD config issue on my part. That being said, I'm not sure how to troubleshoot that any further. Do you have a metrics application that you use locally for verification of this stuff?
If the application does not have opentelemetry_experimental configured the Telemetry handler is detached with the following error.
15:25:07.397 [error] Handler {OtelTelemetryMetrics, [:telemetry, :event], #PID<0.935.0>} has failed and has been detached. Class=:error
Reason=:undef
Stacktrace=[
  {:otel_meter_noop, :record,
   [
     %{
       {:otel_tracer, :span_ctx} => {:span_ctx,
<PHONE_NUMBER>11476008642819364899241647806,<PHONE_NUMBER>8643449198, 1,
        {:tracestate, []}, true, false, true,
        {:otel_span_ets,
         #Function<2.20827891/1 in :otel_tracer_server.on_end/1>}}
     },

@ethangunderson are you sending the metrics to the collector which then sends to DataDog? Can you verify if they are getting to the cluster by adding the debug exporter to the collector metrics pipeline.

@tsloughter I work with @ethangunderson and just got a little test using this working. We're actually sending metrics directly to a Datadog Agent over grpc on port 4317 and I got it to work fine, just a few things that tripped me up along the way. I'll provide the three main things I ran into (I hacked a couple of them into working just to prove this out as a PoC).
First, here's the config we're using for reference
config :opentelemetry_experimental,
  readers: [
    %{
      module: :otel_metric_reader,
      config: %{
        exporter:
          {:otel_exporter_metrics_otlp,
           %{
             endpoint: System.get_env("OTLP_ENDPOINT"),
             protocol: :grpc,
             compression: :gzip
           }}
      }
    }
  ]

We set up a little test with a single Telemetry.Metrics.counter/2  metric:
defmodule Vantage.Otel.Metrics do
  @moduledoc """
  Experimental usage of OtelTelemetryMetrics for a PoC
  """
  use Supervisor

  import Telemetry.Metrics

  def start_link(opts) do
    Supervisor.start_link(__MODULE__, opts, name: __MODULE__)
  end

  @impl Supervisor
  def init(opts) do
    children = [
      {OtelTelemetryMetrics, metrics: Keyword.get(opts, :metrics, metrics())}
    ]

    Supervisor.init(children, strategy: :one_for_one)
  end

  defp metrics do
    [
      counter("vantage.test.metric.count",
        # unit: :count, ====> Needed to set this explicitly to avoid an error in `otel_otlp_metrics.erl`
        event_name: [:vantage, :test, :metric],
        description: "just a test",
        measurement: 1
      )
    ]
  end
end

1) ArgumentError on :unicode.characters_to_binary/1 without explicitly passing a value to :unit on Telemetry.Metrics opts
Without explicitly setting a value for :unit in the Telemetry.Metrics options, we hit this exception:
10:17:01.357 [error] GenServer #PID<0.428.0> terminating
** (ArgumentError) errors were found at the given arguments:

  * 1st argument: not valid character data (an iodata term)

    (stdlib 6.1.2) unicode.erl:1219: :unicode.characters_to_binary(1)
    (opentelemetry_experimental 0.5.1) /Users/zkayser/dev/carburetor/deps/opentelemetry_experimental/apps/opentelemetry_experimental/src/otel_otlp_metrics.erl:72: :otel_otlp_metrics.to_proto/1

We were able to get around this by passing a value under the :unit option on the Telemetry.Metrics definition.
2) Undefined instrumentation scope on default meter
This may be user error on my part or we should have been using our own #meter{}, but with the default meter we ran into this exception:
10:29:09.651 [error] GenServer #PID<0.493.0> terminating
** (stop) {:badrecord, :undefined}
    (opentelemetry_experimental 0.5.1) /Users/zkayser/dev/carburetor/deps/opentelemetry_experimental/apps/opentelemetry_experimental/src/otel_otlp_metrics.erl:51: anonymous fn/3 in :otel_otlp_metrics.to_proto_by_scope/1

I hacked this one a bit to get around this issue. This may not be an issue if there is something similar to create_application_tracers/1 but for meters instead. I hacked this by adding instrumentation_scope = opentelemetry:instrumentation_scope(<<>>, <<>>, <<>>) to the default meter in otel_meter_server.erl.

Undefined description on metric caused error on generated metric service protobuf module

The last error I ran into was that without a #metric record having its description field set, it failed in opentelemetry_exporter_metrics_service_pb.erl due to a function clause missing error:
10:35:37.249 [error] GenServer #PID<0.468.0> terminating
** (FunctionClauseError) no function clause matching in :opentelemetry_exporter_metrics_service_pb.is_empty_string/1
    (opentelemetry_exporter 1.8.0) /Users/zkayser/dev/carburetor/deps/opentelemetry_exporter/src/opentelemetry_exporter_metrics_service_pb.erl:2171: :opentelemetry_exporter_metrics_service_pb.is_empty_string(:undefined)

There is not much in this feedback that pertains specifically to this PR other than maybe getting tripped up on the :unit value. I admit that we are just now getting started with Otel Metrics (we've been reporting metrics over Statsd for years now) and that there may indeed be some user error on our part.
If there is anything at all I can do to help make this feedback more actionable, or if there are any issues I can work on, I would be happy to help out in whatever way we can!


Feature Request: Make server settings per-user

Hi,
I have Heisenbridge set up for my personal Matrix user (running on my personal Matrix server) and it works wonderfully (thanks!).  The way I use it is by connecting to my ZNC bouncer, which means I have my ZNC nickname/password set up on each Heisenbridge network setting.
Now I'd like to allow some friends to use my Heisenbridge server, but obviously I don't want them to have access to my personal ZNC configuration.  Unfortunately it seems that this is not possible; I did some initial tests before granting them access, and I was able to open my personal server configurations just fine using another Matrix user.
It would be awesome if server settings could be made per-user and not global (just like ZNC).
Thanks!

If you already have heisenbridge why do you need ZNC too? I setup a Matrix homeserver and heisenbridge specifically to replace ZNC, which they do wonderfully.

If you already have heisenbridge why do you need ZNC too?

Because I use other IRC clients as well.

If you already have heisenbridge why do you need ZNC too?

Because I use other IRC clients as well.

I use irssiproxy for this. It allows me even to use simultaneously 5 different clients if I want, all in sync.


[Marker.io] "As used by" section is missing on api page

Steps to reproduce:

notice the section above "key features"
compare with figma

Actual result: "As used by" sectionis missing
Expected result: please check and add it(if it should be there)

Reported by: vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://wf-b.stg.prezzee.com/en-us/corporate-gifting-solutions/api?marker=true
Issue details: Open in Marker.io
Device typedesktopBrowserChrome <IP_ADDRESS>Screen Size1366 x 768OSWindows 10 (10.0.0)Viewport Size1366 x 641Pixel Ratio@1x

Waiting on Client to add correct Brand/Company images

🤖 Marker.io bot - This issue was marked as ✅ Resolved in Marker.io


Sum of Middle Elements of two sorted arrays.cpp

Hey @Chinmayee7697! Kindly add your file inside CPP folder.

Ok @DiyaVj
Done
I request you to please check it and merge it into the main.


b2 application key permissions

Output of restic version
0.9.1
How did you run restic exactly?
Generated application key on b2 with bucket only read/write permissions. restic calls into b2 with a list_buckets which is not permitted with bucket level only permissions.
restic init
What backend/server/service did you use to store the repository?
b2, bucket level only permissions
Expected behavior
I would expect a b2 application key to be generated for a specific bucket. Giving the key access to 'all' buckets works as expected.
Actual behavior
restic errors out with a 401 error with the the list_buckets call.
Steps to reproduce the behavior
Do you have any idea what may have caused this?
API level permissions
Do you have an idea how to solve the issue?
Perhaps the list_buckets call can be avoided on an init?
Did restic help you or made you happy in any way?
Restic is awesome!

It appears that the call to listBuckets is required to verify that the bucket exists: https://github.com/kurin/blazer/blob/c83da4d7069325fe34d9ed0f09883c02aedac140/b2/b2.go#L285
This is how the B2 client library works, and isn't really specific to restic. I'm not sure what the implications are of skipping the existence check, or if it's even possible to bypass it: many operations are called on the Bucket once it is obtained.

This is definitely a user story for restic... I looked into the blazer library and b2_list_buckets errors with the given bucket the key has permissions to. Another alternative is to call b2_list_buckets with bucketName to list only the specified bucket. I know it doesn't fit into this project, but the blazer library could be improved to pass the specific bucket with bucketName to b2_list_buckets so the operation is not O(N).

Ah, this is an issue with how application keys work: they cannot just be used instead of the master keys, but need to be handled differently, so all libraries/programs will need explicit support for them. I had a discussion with @kurin and people from Backblaze about that, and there's a fix in the blazer library (in the master branch that I haven't tested yet). If you'd like to try it, then you need to build restic with the latest version of the library.
I had exactly the same effect when I tested the application keys feature last week.
If you do, please report back!

For what it's worth, when we're not dealing with bucket-specific application keys, a b2_list_buckets request requesting the specific bucket name won't really be faster than getting all the buckets and then filtering.  There are a maximum of 100 buckets per account, and so the b2_list_buckets call doesn't support pagination.  You're going to incur exactly one round-trip no matter what you do.

I've just merged #1914, so the code in the master branch now supports application keys! You can build restic yourself to try it out, or download a compiled beta version here: https://beta.restic.net/?sort=time&order=desc

Thank you!


add missing blank for test TestParseSlowLog002

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.粟含 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


LicenseCompareHelper: CC-BY-4.0 license text published by Creative Commons not recognised

The license text for CC-BY-4.0 published by Creative Commons is not being recognised by org.spdx.utility.compare.LicenseCompareHelper.isTextStandardLicense().  Specifically, the "difference message" in the returned  DifferenceDescription object says:
Normal text of license does not match starting at line #5 column #9 "commons" when comparing to template text "

By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms a...".  Last optional text was not found due to the optional difference:
	Normal text of license does not match starting at line #5 column #29 "(" when comparing to template text " Creative Commons Attribution 4.0 International Public License

".  Last optional text was not found due to the optional difference:
	Normal text of license does not match starting at line #34 column #5 "licensed" when comparing to template text " Creative Commons Corporation ("Creative Commons") is not a law firm and does not provide legal serv...".  Last optional text was not found due to the optional difference:
	Normal text of license does not match starting at line #34 column #5 "licensed" when comparing to template text " Creative Commons Corporation ("Creative Commons") is not a law firm and does not provide legal serv...".  Last optional text was not found due to the optional difference:
	Normal text of license does not match starting at line #1 column #12 "4" when comparing to template text "Creative Commons"

Note: tested with Spdx-Java-Library v1.1.5.

Thanks @pmonks for reporting this.
Do you know if this worked in previous releases of the library?  I recently made a lot of changes to handle line separators properly and I may have broken something.

@goneall I'm not entirely sure. The first documented instance of this issue that I can find is in this comment, where I was testing against a pre-release of 1.1.5.  I know I tested this text against v1.1.4 (along with the other texts in that table - they're basically my test suite), but my memory is a bit hazy about what the results were.

I found 4 problems causing this to not match.  It doesn't look like any of these were regressions due to changes in the tooling, it looks like they have all been introduced by subtle changes in the official license text.
2 of the problems are with the alt text in the CC-BY-4.0.xml file which needs to be addressed in the source.  One of the problems is the current CC-BY-4.0 license text replaced a bunch (maybe all) of the dashes with 2 dashes.  This can be fixed by adding alt text for the dashes allowing either single or double dashes.  One of the issues could be considered a tooling issue where there is a linebreak which changed:
CC-licensed

to:
CC-
licensed

Although one could argue the tool should be able to handle a linebreak with a dash, it is probably easier (and safer) to fix this as another alt text to allow the linebreak.
Here's the details:

The cc-lincensed token is broken into two lines.  This is in the XML file on line 29.  Suggested fix - add an alt which allows both variants (e.g. `match="cc-[ \t\r\n\f]+lincensed"
Many of the dashes are now 2 dashes.  Suggested fix - search and replace the dashed with an `-
The <alt match=": wiki.creativecommons.org/Considerations_for_licensors|\." name="considerationsLicensors"> doesn't match if there is a linebreak between the : and wiki....  Suggest changing the match to match=":[ \t\r\n\f]+wiki.creativecommons.org/Considerations_for_licensors|\."  This is on line 29 in the XML.

This most or all of the fixes are to the license XML, I'm moving this issue to the LicenseList-XML repo.


Functor

In #29 and #19 we discussed whether the Dimensional constructor should be exposed, and whether to have a Functor instance.
We came down on the side of no, which I strongly agree with, because it breaks the abstraction. We exposed dmap from DK but not DK.Prelude so that people could get at this if they wanted to, but wouldn't get it by default.
I now propose that we add a Functor instance, but put it in a separate module.
{-# LANGUAGE OverlappingInstances #-}
{-# OPTIONS_GHC -fno-warn-orphan-instances #-}
module Numeric.Units.Dimensional.DK.DubiousFunctorInstance where

import Numeric.Units.Dimensional.DK

instance Functor (Dimensional v d) where
  fmap = dmap

The purpose of this is to empower users to make the choice for themselves. One specific reason for making such a choice would be to be able to get along with Edward's linear package.

OK with me. If you prefer you can call the module .Functor and document the dubiousness.
On Tue, May 12, 2015 at 9:20 PM, Douglas McClean<EMAIL_ADDRESS>wrote:

In #29 and #19 we discussed whether the Dimensional constructor should be exposed, and whether to have a Functor instance.
We came down on the side of no, which I strongly agree with, because it breaks the abstraction. We exposed dmap from DK but not DK.Prelude so that people could get at this if they wanted to, but wouldn't get it by default.
I now propose that we add a Functor instance, but put it in a separate module.
{-# LANGUAGE OverlappingInstances #-}
{-# OPTIONS_GHC -fno-warn-orphan-instances #-}
module Numeric.Units.Dimensional.DK.DubiousFunctorInstance where
import Numeric.Units.Dimensional.DK
instance Functor (Dimensional v d) where
  fmap = dmap

The purpose of this is to empower users to make the choice for themselves. One specific reason for making such a choice would be to be able to get along with Edward's linear package.
Reply to this email directly or view it on GitHub:
https://github.com/bjornbm/dimensional-dk/issues/68

Will do.
Also discovered in preparing this patch that 7.10 deprecated 7.8.4's way of specifying overlappingness.


admin: add streaming variant of the admin API

Commit Message: In https://github.com/envoyproxy/envoy/pull/19693 a streaming stats implementation was introduced, dramatically reducing the amount of time and memory it takes to generate an admin http response.  /config_dump (#32054) and /clusters_ (#32054) can also be improved in this way.
However, in some environments we do not want to expose an HTTP port for admin requests, and we must use the C++ API. However that API is not streaming: it buffers the entire content. This PR adds a new streaming API.
Mechanically this new functionality was easy to add as an externally callble C++ API as the Admin class already supported this model on behalf of /stats.
However there's a fair amount of complexity managing potential races between active streaming requests, server exit, and explicit cancellation of an in-progress request. So much of the effort and complexity in this PR is due to making that thread-safe and testing it.
Additional Description:
Note to reviewers: if this PR is too big it can be broken into 2. The significant additions to main_common.cc, main_common.h, and main_common_test.cc need to stay together in one PR, the rest of the changes are non-functional refactors which are needed for the larger changes to work; they could be reviewed and merged first.
Risk Level: medium -- this is a new API but it does refactor some existing functionality. Using the new functionality will add some risk also as there is some careful thought required to believe we have protected against all possibilities of shutdown/cancel/admin-request races.
Testing: //test/..., and lots of tsan repeated tests for the new streaming tests. Lots of iteration to ensure every new line of main_common.cc is hit by coverage tests.
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a
Fixes: #31755

@RyanTheOptimist the coverage change is actually to increase the coverage expectation. I assume that should be an easy one.

Just started looking into this PR. Just a high level question:
To my understanding, the Admin interface(stats/config_dump,...) is served by the Envoy main-thread.  Do you mean if the stats is sent out by streaming , it is actually served by a separate Envoy thread, and such streaming can be terminated by a command from main_thread?

@yanjunxiang-google you are correct: /stats is served by the main thread. But it is served in chunks via a Request API internal to Envoy now, with a nextChunk method. Actually all admin endpoints go through that API but (for now) all the others deliver the entire content in one chunk. Thus, at least for stats, this mechanism enables streaming through the C++ endpoints and I have a demo I can show you internally about how much less memory that consumes, compared to buffering the entire response in one string.
See the PRs and Issues referenced in the description above for more detail.

FSM diagram: let me konw of this helps: https://docs.google.com/drawings/d/1njUl1twApEMoxmjaG4b7optTh5fcb_YNcfSnkHbdfq0/edit

thanks for the reviews; will do a pass over them later today.

I got the thread-synchronizer strategy to work but decided it was more verbose and harder to read than the interlock call, so I dropped it.

Filed https://github.com/envoyproxy/envoy/issues/32769 for test flake in ext_proc
/retest

/retest

/retest

@tyxia @ravenblackx are there more comments? Thanks!

Thansk for the great comments, @ravenblackx and @tyxia .
Greg can you do a senior maintainer pass? Thanks!


docs: Fix typo on README

cherry-picked the fix to master since there was a weird extra merge commit on this branch

thanks for the fix :tada:


Setup test configuration and add tests

Goal
Setup Jest and write tests
Tasks

[x] Install and configure jest and ts-jest
[ ] Setup Toggl test account and seed
[ ] Setup Clockify test account and seed

Installed and configured Jest on #4.


[Nominations Open] Most Valuable Jenkins Contributor 2022 🏆

This issue is to receive nominations for the Most Valuable Jenkins Contributor 2022. This award is presented to an individual who has contributed to the Jenkins project the most through new features, bug fixes or plugin development efforts.
To nominate someone, reply to this issue with the following:

Full name of the person you’re nominating
Short description of their contributions to the Continuous Delivery Foundation and why they should win.

Nomination Deadline: Tuesday, March 29, 2022 [EXTENDED to April 11, 2022]
More details are available here: https://cd.foundation/cdf-community-awards/

Nomination: Jan Faracik
He did a tremendous job in improving the user experience and design of the Jenkins user interface. His work includes new icons, improved UI form elements, view redesign, UI developer API, helpful developer documentation, etc. His changes let Jenkins look modern again!

@jmMeessen and I are pleased to nominate Kris Stern (@krisstern on GitHub) for the Most Valuable Advocate award. Kris is a new contributor to the Jenkins project, and has shown exemplary dedication to the meaning of giving back. Kris volunteered to be a mentor and an org admin for Jenkins Google Summer of Code 2022. Since signing up he has displayed genuine commitment to the success of this program. He is present at every office hours even when it is 1am his local time. He is always available and responsive to all GSoC potential contributors, providing feedback, guidance and technical advice. At times Kris could be seen gracefully challenging potential contributors to think outside of the box, as a good mentor does. There are times throughout the program where the ratio of potential contributors outnumbered the mentors prompting a flurry of inquiries, Kris rose to the occasion and took the lead to address those inquiries, even when he is the very few doing so.
Kris’ contributions, commitment, and thoughtfulness amplify what the Jenkins community stands for which is fostering an open and welcoming community.
Many Thanks Kris!

Nomination: Basil Crow (@basil)
Basil modernized major components in Jenkins core.  He converted the Linux installers from System V init to systemd.  He updated, adopted, and released additional core Jenkins components.  He adopted, updated, and released multiple Jenkins plugins.
Some examples of his contributions:

Member of the Jenkins core team, reviewing and improving Jenkins core

Over 300 pull requests to Jenkins core in the last 15 months

Multiple challenging upgrades of core components like Guava, Guice, ASM, and JNR
Quality improvement with spotbugs, checkstyle, and spotless

Installation improvements

Over 50 pull requests to Jenkins Linux installer in the last 6 months

Java support improvements

Identified and resolved Java 11 support issues
Identified and resolved Java 17 support issues

Maintainer of 23 plugins

API plugins like Jakarta activation API, Jakarta mail API, JavaX activation API, JavaX mail API, Jersey2 API, and JNR POSIX API
Infrastructure plugins like file leak detector, email ext, and SQLite database
Pipeline plugins like workspace cleanup, timestamper, lockable resources, resource disposer, and http_request
Authentiation plugins like GitHub OAuth and GitLab OAuth

Thank you, everyone! Award ceremony happened at cdCon 2022.
Congratulation to the winner @basil!
All winners here: https://github.com/cdfoundation/awards/blob/main/README.md

Are the voting results public as well? I.e., who got how many votes?

Thanks for reaching out @uhafner.

Are the voting results public as well? I.e., who got how many votes?

The results are not public.
In order to increase the transparency of CDF Awards process, we are working on documenting it.
Please feel free to share your feedback about it directly on the corresponding issue.
We can include you as a reviewer to PR once it becomes available so you can provide your feedback directly on it.
Please let us know.

@uhafner we have made a few changes to the CDF Awards Program for 2023.

The awards program guidelines are published.
As noted on the guidelines, each CDF project conducts their own selection process for their Most Valuable Contributor Award.
For CDF Awards, we introduced a new role, Awards Officer, overseeing the nomination and voting process for CDF Awards.

Please let us know if you want to become the Awards Officer for the CDF Awards.

Hi @fdegir, yes, I am happy to help! What are the steps to do? Review the documents?

That's great @uhafner. It would be good if you could review the awards program guidelines as well as the community roles and let us know of your feedback by opening up an issue in the foundation repo or directly proposing changes via PRs.
We added awards officer topic to the agenda of the TOC Meeting that will happen on Tuesday, February 14th at 16:00 UTC and call for volunteers. If possible, it would be good if you could join and state your interest.

@uhafner could you please pass your email address to me via a private message on CDF Slack so we can communicate nomination and voting related information with you?


redis: can't parse "ype":"PerfdataValue","unit":"","value":0.0,"warn":null}],"status":{"checkercomponent":{"checker":{"i"

We at @Icinga are developing two applications, one writes to Redis (and publishes events) and the other reads (and subscribes for the events).
The writer PUBLISHes periodically data like...
{"ApiListener":{"perfdata":[{"counter":false,"crit":null,"label":"api_num_conn_endpoints","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null},{"counter":false,"crit":null,"label":"api_num_endpoints","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null},{"counter":false,"crit":null,"label":"api_num_http_clients","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null},{"counter":false,"crit":null,"label":"api_num_json_rpc_clients","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null},{"counter":false,"crit":null,"label":"api_num_json_rpc_relay_queue_item_rate","max":null,"min":null,"type":"PerfdataValue","unit":"","value":46.399999999999998579,"warn":null},{"counter":false,"crit":null,"label":"api_num_json_rpc_relay_queue_items","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null},{"counter":false,"crit":null,"label":"api_num_json_rpc_sync_queue_item_rate","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null},{"counter":false,"crit":null,"label":"api_num_json_rpc_sync_queue_items","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null},{"counter":false,"crit":null,"label":"api_num_json_rpc_work_queue_count","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null},{"counter":false,"crit":null,"label":"api_num_json_rpc_work_queue_item_rate","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null},{"counter":false,"crit":null,"label":"api_num_json_rpc_work_queue_items","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null},{"counter":false,"crit":null,"label":"api_num_not_conn_endpoints","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null}],"status":{"api":{"conn_endpoints":[],"http":{"clients":0.0},"identity":"CENSOREDCENSOREDCENSOREDCENSO","json_rpc":{"clients":0.0,"relay_queue_item_rate":46.399999999999998579,"relay_queue_items":0.0,"sync_queue_item_rate":0.0,"sync_queue_items":0.0,"work_queue_count":0.0,"work_queue_item_rate":0.0,"work_queue_items":0.0},"not_conn_endpoints":[],"num_conn_endpoints":0.0,"num_endpoints":0.0,"num_not_conn_endpoints":0.0,"zones":{"alexanders-mbp.int.netways.de":{"client_log_lag":0.0,"connected":true,"endpoints":["alexanders-mbp.int.netways.de"],"parent_zone":""}}}}},"CIB":{"perfdata":[],"status":{"active_host_checks":1.8500000000000000888,"active_host_checks_15min":1649.0,"active_host_checks_1min":111.0,"active_host_checks_5min":562.0,"active_service_checks":21.350000000000001421,"active_service_checks_15min":19280.0,"active_service_checks_1min":1281.0,"active_service_checks_5min":6399.0,"avg_execution_time":0.021172960599263507958,"avg_latency":0.011358479658762613354,"max_execution_time":0.077728986740112304688,"max_latency":0.045314073562622070312,"min_execution_time":0.001573085784912109375,"min_latency":0.0,"num_hosts_acknowledged":0.0,"num_hosts_down":1.0,"num_hosts_flapping":0.0,"num_hosts_in_downtime":0.0,"num_hosts_pending":0.0,"num_hosts_unreachable":0.0,"num_hosts_up":0.0,"num_services_acknowledged":0.0,"num_services_critical":3.0,"num_services_flapping":0.0,"num_services_in_downtime":0.0,"num_services_ok":4.0,"num_services_pending":0.0,"num_services_unknown":3.0,"num_services_unreachable":12.0,"num_services_warning":2.0,"passive_host_checks":0.0,"passive_host_checks_15min":0.0,"passive_host_checks_1min":0.0,"passive_host_checks_5min":0.0,"passive_service_checks":0.0,"passive_service_checks_15min":0.0,"passive_service_checks_1min":0.0,"passive_service_checks_5min":0.0,"remote_check_queue":0.0,"uptime":18855.292195796966553}},"CheckResultReader":{"perfdata":[],"status":{"checkresultreader":{}}},"CheckerComponent":{"perfdata":[{"counter":false,"crit":null,"label":"checkercomponent_checker_idle","max":null,"min":null,"type":"PerfdataValue","unit":"","value":13.0,"warn":null},{"counter":false,"crit":null,"label":"checkercomponent_checker_pending","max":null,"min":null,"type":"PerfdataValue","unit":"","value":0.0,"warn":null}],"status":{"checkercomponent":{"checker":{"idle":13.0,"pending":0.0}}}},"CompatLogger":{"perfdata":[],"status":{"compatlogger":{}}},"ElasticsearchWriter":{"perfdata":[],"status":{"elasticsearchwriter":{}}},"ExternalCommandListener":{"perfdata":[],"status":{"externalcommandlistener":{}}},"FileLogger":{"perfdata":[],"status":{"filelogger":{"main-log":1.0}}},"GelfWriter":{"perfdata":[],"status":{"gelfwriter":{}}},"GraphiteWriter":{"perfdata":[],"status":{"graphitewriter":{}}},"IcingaApplication":{"perfdata":[],"status":{"icingaapplication":{"app":{"enable_event_handlers":true,"enable_flapping":true,"enable_host_checks":true,"enable_notifications":true,"enable_perfdata":true,"enable_service_checks":true,"environment":"production","node_name":"alexanders-mbp.int.netways.de","pid":7700.0,"program_start":1531475256.183437109,"version":"v2.8.4-779-g45b3429fa"}}}},"InfluxdbWriter":{"perfdata":[],"status":{"influxdbwriter":{}}},"LivestatusListener":{"perfdata":[],"status":{"livestatuslistener":{}}},"NotificationComponent":{"perfdata":[],"status":{"notificationcomponent":{"notification":1.0}}},"OpenTsdbWriter":{"perfdata":[],"status":{"opentsdbwriter":{}}},"PerfdataWriter":{"perfdata":[],"status":{"perfdatawriter":{}}},"StatusDataWriter":{"perfdata":[],"status":{"statusdatawriter":{}}},"SyslogLogger":{"perfdata":[],"status":{"sysloglogger":{}}}}

... and the reader consumes that using this library.
Wireshark shows nothing special, just these messages and some PINGs, but after a while the reader hits internal/proto/reader.go:106 with line being ...
ype":"PerfdataValue","unit":"","value":0.0,"warn":null}],"status":{"checkercomponent":{"checker":{"idle":13.0,"pending":0.0}}}},"CompatLogger":{"perfdata":[],"status":{"compatlogger":{}}},"ElasticsearchWriter":{"perfdata":[],"status":{"elasticsearchwriter":{}}},"ExternalCommandListener":{"perfdata":[],"status":{"externalcommandlistener":{}}},"FileLogger":{"perfdata":[],"status":{"filelogger":{"main-log":1.0}}},"GelfWriter":{"perfdata":[],"status":{"gelfwriter":{}}},"GraphiteWriter":{"perfdata":[],"status":{"graphitewriter":{}}},"IcingaApplication":{"perfdata":[],"status":{"icingaapplication":{"app":{"enable_event_handlers":true,"enable_flapping":true,"enable_host_checks":true,"enable_notifications":true,"enable_perfdata":true,"enable_service_checks":true,"environment":"production","node_name":"CENSOREDCENSOREDCENSOREDCENSO","pid":7700.0,"program_start":1531475256.183437109,"version":"v2.8.4-779-g45b3429fa"}}}},"InfluxdbWriter":{"perfdata":[],"status":{"influxdbwriter":{}}},"LivestatusListener":{"perfdata":[],"status":{"livestatuslistener":{}}},"NotificationComponent":{"perfdata":[],"status":{"notificationcomponent":{"notification":1.0}}},"OpenTsdbWriter":{"perfdata":[],"status":{"opentsdbwriter":{}}},"PerfdataWriter":{"perfdata":[],"status":{"perfdatawriter":{}}},"StatusDataWriter":{"perfdata":[],"status":{"statusdatawriter":{}}},"SyslogLogger":{"perfdata":[],"status":{"sysloglogger":{}}}}

Please try to isolate the problem and create a program that reproduces it. Without such program I don't think we can make any progress on this issue.

OK, I'll provide you a Docker image.

With this one I've reproduced this two times both after 15 minutes.

Thanks for the reproducer. It should be fixed in master. The problem was that go-redis set network read timeout equal to the PubSub message timeout which caused read timeouts at the time when publisher published some messages.

Looking at this today I don't think I fixed anything. Timeouts will still occur which means that data still can be half-read...

Well, at the moment I'm running that container again for 2.33h and it works for me.

Just increase time.Sleep between messages to 15 seconds and it should start failing again. I have a proper fix coming.

I don't really get it (nor could reproduce it), but we (@Icinga) are happy as long as this error doesn't occur again.
Thank you for fixing this.

I'm afraid you was right with the 15 secs part – just reproduced this (before #822).

That should be fixed in the latest version. As for the today the recommended way to use PubSub is via PubSub.Channel API (and don't touch any Receive* methods). See https://godoc.org/github.com/go-redis/redis#example-PubSub
ReceiveMessage should work in 99% cases too, but it does not send periodic Ping to check if connection/PubSub is healthy.

They don't PING? Strange, I believe to remember PINGs in the captured TCP stream while reproducing the problem.

... and IMAO this doesn't matter as there's traffic every 10/15s anyway.

I used ReceiveTimeout in my code and encountered this problem too, is that also fixed for receive with timeout in v6.13? Because I saw in the new code the timeout of ReceiveMessage is set to 0, I suppose that solution only affects ReceiveMessage but not ReceiveTimeout, is that true?

Yes. ReceiveTimeout is unreliable since read with timeout can read half of the message.


Running logstash 6.x in Docker Swarm creates nonconfigurable container

I have the following simple docker-compose.yml file:
version: "3"

services:
  logstash:
      image: docker.elastic.co/logstash/logstash:6.2.4
      volumes:
        - ./logstash/config/:/usr/share/logstash/config/
        - ./logstash/pipeline/:/usr/share/logstash/pipeline/
      deploy:
        mode: replicated
        replicas: 1

where the pipeline is configured with a TCP input and elasticsearch output. Logstash 6.x in Docker fails to read the configuration when run in a Docker Swarm, i.e. with the command docker swarm init; docker stack deploy --compose-file docker-compose.yml asdf. The symptom: logstash starts up and immediately quits, presumably because it uses the default stdin config.
Running the same file with docker-compose up works. Running Logstash 5.x works.
The culprit MAY be that for some reason the container startup command (obtained by docker ps --no-trunc) for the working setups is "/usr/local/bin/docker-entrypoint" but for some reason the command for the broken 6.x container in the Docker Swarm is "/docker-entrypoint -e ". In logstash 6.x the empty -e flag overrides the configuration file (as far as I know), even if the file mounts correctly into the container.
I have no idea why this weird command is generated in the Swarm but not in compose. Setting the entrypoint property in the compose file to the "right" value makes logstash not start at all.

Hi. Thanks for this really detailed report, and sorry for the slow response.
I'm sorry to say that this doesn't reproduce for me...
I created this docker-compose.yml
version: "3"

services:
  logstash:
      image: docker.elastic.co/logstash/logstash:6.2.4
      volumes:
        - ./logstash/pipeline/:/usr/share/logstash/pipeline/
      deploy:
        mode: replicated
        replicas: 1

...and this file in ./logstash/pipeline/pipeline.conf:
input {
  heartbeat {
    message  => "I am alive."
    interval => 1
  }
}

output {
  stdout {}
}

I then ran docker swarm init and:
docker stack deploy --compose-file docker-compose.yml repro

After some time, I was able to see the exepected output in the logs:
$ docker service logs repro_logstash | grep alive | tail
repro_logstash.1.ygeqt11bnd7u@rasa    |        "message" => "I am alive.",
repro_logstash.1.ygeqt11bnd7u@rasa    |        "message" => "I am alive.",
repro_logstash.1.ygeqt11bnd7u@rasa    |        "message" => "I am alive.",
repro_logstash.1.ygeqt11bnd7u@rasa    |        "message" => "I am alive.",
repro_logstash.1.ygeqt11bnd7u@rasa    |        "message" => "I am alive.",
repro_logstash.1.ygeqt11bnd7u@rasa    |        "message" => "I am alive.",
repro_logstash.1.ygeqt11bnd7u@rasa    |        "message" => "I am alive.",
repro_logstash.1.ygeqt11bnd7u@rasa    |        "message" => "I am alive.",
repro_logstash.1.ygeqt11bnd7u@rasa    |        "message" => "I am alive.",
repro_logstash.1.ygeqt11bnd7u@rasa    |        "message" => "I am alive.",

Also, the command was set correctly:
$ docker ps --no-trunc --format '{{.Names}} {{.Command}}'
repro_logstash.1.ygeqt11bnd7urrawk5fe2xuev "/usr/local/bin/docker-entrypoint"

I suspect that Swarm is running the wrong image, especially since the entrypoint/command for the old image from Docker Inc. is /docker-entrypoint -e. How and why it's doing that are interesting questions!

I see! Thanks for the extra info. I'll try to debug some more. If I understand correctly, the /docker-entrypoint -e command worked in Docker <5.x because the -e flag was combined with any potential config files, while in 6.x it replaces the config file. Since this command now breaks my 6.2.4 image, I am assuming that the underlying software IS in fact 6.2.4, but the Dockerfile somehow behaves weirdly. Or perhaps Swarm, somehow.

Your analysis sounds good to me. I can't find the documentation for the change to -e just now, but it does sound very familiar.
The most suspicious thing for me is still where the invalid command is coming from. It's also super suspicious that it matches the command for a different Logstash image.
Good luck, and please let me know if you crack it! I'm very curious now.

Oh, since you are mounting all of /usr/share/logstash/config/, make sure it's up to date with what's needed for 6.2. There are quite a few files that ship in that directory as the default configuration, including the new pipelines.yml.
$ docker run docker.elastic.co/logstash/logstash:6.2.4 ls /usr/share/logstash/config
jvm.options
log4j2.properties
logstash.yml
pipelines.yml
startup.options

Finally solved it! It was indeed Swarm running the wrong image. Turns out the example I gave above, which was slightly cleaned up from the production config I was using, was in itself working :) In actuality, I re-tagged the logstash image to shorten the image name, and that's where the problems arose. I have filed a new bug with Docker proper, at https://github.com/docker/cli/issues/1286, and this can be considered closed.

Excellent! Thanks for reporting in, and happy 'stashing!


[Fix] fix_t_flink_app Missing "hadoop_user" field

What changes were proposed in this pull request
Issue Number: close #3480

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): (yes / no)

@wolfboys If you have time, please help me review the code. Due to the lack of the "hadoop_user" field, the dev branch is currently unable to start properly

I'm not sure if this is a bug


Jenkins Swagger specifications update 20.14.0

This is an auto swagger specifications update from Jenkins

Pouah, forget it the 20.14 branch of the Agent is not up to date.... will run it later


How to forward Littleproxy through an HTTP proxy?

Hi,
I was wondering if I can use littleproxy to forward requests through another proxy before reaching the destination server. I would like an example of how this is done, if possible.
I need :
Client > Littleproxy > HTTP Proxy > Website

@adamfisk

Any help would be appreciated :)

ChainedProxy will do the job, just add the http proxy to the chain. Take a look at BaseChaindedProxyTest


Sending a quick reply causes an error

The problem was simply that the incorrect key was being sent in the request.  It should be quick_replies

Thanks @keeth


Add tutorial on setup_codingclub_session()

Just adding a note regarding how this would render. A sample of the (locally) rendered website for this tutorial:

Two things here:

the R chunks don't have the right syntax colouring + background. This will be rectified when following Hans' advice. In the md file, code blocks will then start with ```r and output blocks with ``` (so implementing that is an alternative).

best put backticks around inline function/argument/variable names and values, e.g.:
`root_dir` wich is set to `"."`

Bingo:

Thanks @florisvdh. The tutorial got better and better and I learned again something new.
I have unfortunately and suddenly a problem while knitting to md. I don't know the reason, but a strange html is generated now instead of a md. And I get always this message:
> blogdown:::preview_site()
Launching the server via the command:
  C:\Users\damiano_oldoni\AppData\Roaming\Hugo\hugo.exe server --bind <IP_ADDRESS> -p 4321 --themesDir themes -t minimo -D -F --navigateToChanged

Nothing happens and after 30s I get this error of course:
Fout: het proces 13128 is niet gevonden.
Error: It took more than 30 seconds to launch the server. There may be something wrong. The process has been killed. If the site needs more time to be built and launched, set options(blogdown.server.timeout) to a larger value.

No preview is generated as it was before.

I followed the hugo setup more or less according to the Travis CI (I have no blogdown experience):
curl -Lo hugo.deb https://github.com/gohugoio/hugo/releases/download/v0.62.0/hugo_0.62.0_Linux-64bit.deb
sudo dpkg -i hugo.deb
git clone https://github.com/MunifTanjim/minimo.git --depth 1 --branch v2.7.0 themes/minimo

And implementing (from a local tutorials repo) like:
hugo -d ~/ContinuLegen/tutorials -b ~/ContinuLegen/tutorials --cleanDestinationDir

I removed the package blogdown from library and everything works fine: I push on Knit button and a .md file is produced without any problem as before.
@florisvdh, @EmmaCartuyvels1: I pushed the final md. Time to merge, is it ok for you?

@damianooldoni  are these files needed?
index_files/anchor-sections/anchor-sections.css
index_files/anchor-sections/anchor-sections.js

No idea. They have been generated by knitting to md.

I've been looking at current RStudio preview version and it seems blogdown is triggered automatically. However it prevents the normal rendering of md-file by rmarkdown, and it also seems to be the cause of the index_files folder. After blogdown is removed and Rmd is knitted, that folder is not created anymore and md file is again created normally. Also, the folder is not needed for rendering the website (have tested this).
Adding two commits for this + shorten a sentence.

Thanks @florisvdh. I learned again a lot.
I have just updated the date and knitted to md. The branch is already up to date with master. Green light from Travis CI as well. I will merge then. :partying_face:

Superb @EmmaCartuyvels1 @damianooldoni ! Nice result: https://inbo.github.io/tutorials/tutorials/r_setup_codingclub_session/
Ideal for including in the upcoming Open Science newletter BTW :wink:


SingleDatePicker should show the selected month when initialVisibleMonth changes

I'm creating a form with the city of departure, the one of arrival and the SingleDatePicker with all the available dates.
Most of the times the available dates will be in a different month of the one currently visible.
I can fix the problem with initialVisibleMonth for the first selection, but there's no way to move manually to the right month when the cities are changed and the initialVisibleMonth is changed.

So I think this is a duplicate of https://github.com/airbnb/react-dates/issues/48 so I'm going to close this in favor of that discussion.
Right now, month is not a controlled property. To make this change, we'd need to do a lot of thinking about how the animation works, especially as it involves jumping more than one month at a time. Currently this is not on my roadmap and the initialVisibleMonth solves our present needs, but I am open to discussion on this and your thoughts.


Convert to a functional style

All setters should be explicit methods that return a new (shallow) copy, so as to make it safer to perform modifications. The choice of "shallow" depends on the method involved, e.g., a set_column() method might need to make a copy of the dict while a  set_metadata() method would not need to do so.
You may choose to provide an in_place option that defaults to False but can be set to True to directly mutate the object.

TBH even getters should be actual methods for consistency and flexibility, e.g., mcols(use_names=True).


javascript auto format on save disable not working

VSCode Version: Code 1.7.2 (7ba55c5860b152d999dda59393ca3ebeb1b5c85f, 2016-11-21T22:01:10.756Z)
OS Version: Darwin x64 15.5.0
Extensions:

Extension
Author
Version

beautify
HookyQR
0.5.5

sample-ext
RolandGreim
0.0.2

ActiveFileInStatusBar
RoscoP
1.0.2

code-settings-sync
Shan
2.3.8

project-manager
alefragnani
0.12.2

django-snippets
bibhasdn
1.1.0

vscode-eslint
dbaeumer
1.1.0

githistory
donjayamanne
0.1.0

python
donjayamanne
0.5.5

ansible
haaaad
0.2.3

rest-client
humao
0.10.5

docthis
joelday
0.3.5

vscode-JS-CSS-HTML-formatter
lonefy
0.2.2

MagicPython
magicstack
0.6.0

vs-remote-debugger
mkloubert
1.9.9

prettify-json
mohsen1
0.0.3

view-in-browser
qinjia
0.0.3

vscode-icons
robertohuertasm
4.0.2

sass-indented
robinbentley
1.2.1

annotator
ryu1kn
0.10.1

python
tht13
0.2.3

python-extended-snippets
tushortz
0.0.1

Material-theme
zhuangtongfa
1.0.3

vscode-open-in-github
ziyasal
1.2.2

Steps to Reproduce:

Edit a javascript file and save. file will be auto formatted which i don't want. Event though i have the below settings but auto format is not disabled

    "editor.formatOnSave": false,
    "javascript.format.enable": false

It looks like that either the VS Code recent update is causing this issue or some extension is interfering. Due to this issue i am unable to work. Please suggest a solution.

In addition to the default javascript formatter that ships with VS Code you have installed another (vscode-JS-CSS-HTML-formatter	lonefy	0.2.2) which is likely now format. You must either uninstall that or configure it separately.

Thanks @jrieken, uninstalling vscode-JS-CSS-HTML-formatter solved the issue.


Issue With Shoulder's Surfing Mod and Spartan Weaponry Not Working Together.

I'm having an issue with forge 1.18.2 with  with shoulder's surfing mod and spartan weaponry working together that when I have a throwable weapon in my hand and I'm on the shoulder's surfing perspective view, my health bar, hunger bar, and XP bar are gone, and when I ever try to go to game menu or press E (opening my inventory screen), it crashes the game completely and gives a
"java.util.NoSuchElementException: null".

Screenshot without the spartan weaponry's throwable weapons:

Screenshot with one of the spartan weaponry's throwable weapons:

When your game crashes, it should generate a crash report in the "crash-reports" folder. Can you reproduce the crash and send me the latest crash report? This will help me figure out what is causing this.

crash-2024-02-14_15.23.36-client.txt

forgot to mention that the crash happens only when I press game menu key while having a javelin or a throwing knife on hand while on shoulder's surfing perspective.

I can't seem to reproduce the issue so far. What mods do you have that modifies the HUD. I suspect that one of those mods might be causing this issue in tandem with mine

The mods I'm currently using that change the HUD are called "Inventory HUD+" , "Thirst Was Taken", "Crosshair Bobbing", "AppleSkin", "Armor Toughness Bar", . I'm also using resource pack called "Excalibur" that changes the HUD as well.

I found the issue, so apparently the issue was that in the config of shoulder surfing itself that changing the crosshair type to "dynamic" is what causes the issue.

Oh that's nice to know. I'll see if there is a way to prevent this issue from happening on my end.

still happens on 1.19.2


feat: support any Inspector for block + tx tracing

unblocks #6977
Previously all tx+block tracing helper trait functions were limited to TracingInspector.
This adds these implementations as additional functions that are generic over Inspector trait and reuses them.

ah rip, the suggestion linked to a private item


Memory Usage issues

Is there any method using which we can control the memory consumption of the tika server? Apparently the more files I parse the memory consumption of the tika server keeps increasing.

This is one to file upstream in Apache Tina’s JIRA


Problem in building serialbox2 with gridtools unittests

[  8%] Built target gtest
[ 30%] Built target SerialboxCoreLibraryObjects
[ 31%] Built target SerialboxCoreLibraryShared
[ 32%] Built target SerialboxCoreLibraryStatic
[ 41%] Built target SerialboxCLibraryObjects
[ 42%] Built target SerialboxCLibraryStatic
[ 42%] Built target sdbPython
[ 42%] Built target SerialboxPython
[ 43%] Built target SerialboxCLibraryShared
[ 47%] Built target SerialboxUnittestUtility
[ 48%] Building CXX object test/serialbox/core/CMakeFiles/SerialboxCppUnittest.dir/frontend/gridtools/UnittestStorageView.cpp.o
In file included from /home/adam/tmp/gridtools/include/storage/meta_storage.hpp:39:0,
                 from /home/adam/tmp/gridtools/include/storage/meta_storage_extender.hpp:37,
                 from /home/adam/tmp/gridtools/include/storage/storage.hpp:51,
                 from /home/adam/tmp/gridtools/include/storage/storage_metafunctions.hpp:44,
                 from /home/adam/tmp/gridtools/include/storage/storage-facility.hpp:38,
                 from /home/adam/tmp/serialbox2/test/utility/GridTools.h:27,
                 from /home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:15:
/home/adam/tmp/serialbox2/src/serialbox/core/frontend/gridtools/StorageViewHelper.h: In instantiation of ‘std::vector<int, std::allocator<int> > serialbox::gridtools::internal::get_strides(const StorageType&, const MetaDataType&) [with MetaDataType = gridtools::meta_storage<gridtools::meta_storage_aligned<gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 1u>, gridtools::layout_map<0, 1>, false>, gridtools::aligned<0u>, gridtools::halo<1u, 2u> > >; StorageType = gridtools::storage<gridtools::base_storage<gridtools::wrap_pointer<int, true>, gridtools::meta_storage<gridtools::meta_storage_aligned<gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 1u>, gridtools::layout_map<0, 1>, false>, gridtools::aligned<0u>, gridtools::halo<1u, 2u> > >, 1u> >]’:
/home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:181:3:   required from ‘void GridToolsStorageViewTest_Construction_Test<gtest_TypeParam_>::TestBody() [with gtest_TypeParam_ = int]’
/home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:485:1:   required from here
/home/adam/tmp/gridtools/include/storage/meta_storage_base.hpp:134:42: error: ‘gridtools::array<int, 2ul> gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 1u>, gridtools::layout_map<0, 1>, false>::m_strides’ is protected
         array< int_t, space_dimensions > m_strides;
                                          ^
In file included from /home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:23:0:
/home/adam/tmp/serialbox2/src/serialbox/core/frontend/gridtools/StorageViewHelper.h:43:41: error: within this context
   const auto& strides_array = meta_data.m_strides;
                                         ^
In file included from /home/adam/tmp/gridtools/include/storage/meta_storage.hpp:39:0,
                 from /home/adam/tmp/gridtools/include/storage/meta_storage_extender.hpp:37,
                 from /home/adam/tmp/gridtools/include/storage/storage.hpp:51,
                 from /home/adam/tmp/gridtools/include/storage/storage_metafunctions.hpp:44,
                 from /home/adam/tmp/gridtools/include/storage/storage-facility.hpp:38,
                 from /home/adam/tmp/serialbox2/test/utility/GridTools.h:27,
                 from /home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:15:
/home/adam/tmp/serialbox2/src/serialbox/core/frontend/gridtools/StorageViewHelper.h: In instantiation of ‘void* serialbox::gridtools::internal::get_origin_ptr(const StorageType&, const MetaDataType&, unsigned int) [with StorageType = gridtools::storage<gridtools::base_storage<gridtools::wrap_pointer<int, true>, gridtools::meta_storage<gridtools::meta_storage_aligned<gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 1u>, gridtools::layout_map<0, 1>, false>, gridtools::aligned<0u>, gridtools::halo<1u, 2u> > >, 1u> >; MetaDataType = gridtools::meta_storage<gridtools::meta_storage_aligned<gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 1u>, gridtools::layout_map<0, 1>, false>, gridtools::aligned<0u>, gridtools::halo<1u, 2u> > >]’:
/home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:181:3:   required from ‘void GridToolsStorageViewTest_Construction_Test<gtest_TypeParam_>::TestBody() [with gtest_TypeParam_ = int]’
/home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:485:1:   required from here
/home/adam/tmp/gridtools/include/storage/meta_storage_base.hpp:134:42: error: ‘gridtools::array<int, 2ul> gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 1u>, gridtools::layout_map<0, 1>, false>::m_strides’ is protected
         array< int_t, space_dimensions > m_strides;
                                          ^
In file included from /home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:23:0:
/home/adam/tmp/serialbox2/src/serialbox/core/frontend/gridtools/StorageViewHelper.h:91:41: error: within this context
   const auto& strides_array = meta_data.m_strides;
                                         ^
In file included from /home/adam/tmp/gridtools/include/storage/meta_storage.hpp:39:0,
                 from /home/adam/tmp/gridtools/include/storage/meta_storage_extender.hpp:37,
                 from /home/adam/tmp/gridtools/include/storage/storage.hpp:51,
                 from /home/adam/tmp/gridtools/include/storage/storage_metafunctions.hpp:44,
                 from /home/adam/tmp/gridtools/include/storage/storage-facility.hpp:38,
                 from /home/adam/tmp/serialbox2/test/utility/GridTools.h:27,
                 from /home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:15:
/home/adam/tmp/serialbox2/src/serialbox/core/frontend/gridtools/StorageViewHelper.h: In instantiation of ‘std::vector<int, std::allocator<int> > serialbox::gridtools::internal::get_strides(const StorageType&, const MetaDataType&) [with MetaDataType = gridtools::meta_storage<gridtools::meta_storage_aligned<gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 3u>, gridtools::layout_map<0, 1, -1>, false>, gridtools::aligned<0u>, gridtools::halo<1u, 2u, 3u> > >; StorageType = gridtools::storage<gridtools::base_storage<gridtools::wrap_pointer<int, true>, gridtools::meta_storage<gridtools::meta_storage_aligned<gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 3u>, gridtools::layout_map<0, 1, -1>, false>, gridtools::aligned<0u>, gridtools::halo<1u, 2u, 3u> > >, 1u> >]’:
/home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:201:3:   required from ‘void GridToolsStorageViewTest_Construction_Test<gtest_TypeParam_>::TestBody() [with gtest_TypeParam_ = int]’
/home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:485:1:   required from here
/home/adam/tmp/gridtools/include/storage/meta_storage_base.hpp:134:42: error: ‘gridtools::array<int, 3ul> gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 3u>, gridtools::layout_map<0, 1, -1>, false>::m_strides’ is protected
         array< int_t, space_dimensions > m_strides;
                                          ^
In file included from /home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:23:0:
/home/adam/tmp/serialbox2/src/serialbox/core/frontend/gridtools/StorageViewHelper.h:43:41: error: within this context
   const auto& strides_array = meta_data.m_strides;
                                         ^
In file included from /home/adam/tmp/gridtools/include/storage/meta_storage.hpp:39:0,
                 from /home/adam/tmp/gridtools/include/storage/meta_storage_extender.hpp:37,
                 from /home/adam/tmp/gridtools/include/storage/storage.hpp:51,
                 from /home/adam/tmp/gridtools/include/storage/storage_metafunctions.hpp:44,
                 from /home/adam/tmp/gridtools/include/storage/storage-facility.hpp:38,
                 from /home/adam/tmp/serialbox2/test/utility/GridTools.h:27,
                 from /home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:15:
/home/adam/tmp/serialbox2/src/serialbox/core/frontend/gridtools/StorageViewHelper.h: In instantiation of ‘void* serialbox::gridtools::internal::get_origin_ptr(const StorageType&, const MetaDataType&, unsigned int) [with StorageType = gridtools::storage<gridtools::base_storage<gridtools::wrap_pointer<int, true>, gridtools::meta_storage<gridtools::meta_storage_aligned<gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 3u>, gridtools::layout_map<0, 1, -1>, false>, gridtools::aligned<0u>, gridtools::halo<1u, 2u, 3u> > >, 1u> >; MetaDataType = gridtools::meta_storage<gridtools::meta_storage_aligned<gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 3u>, gridtools::layout_map<0, 1, -1>, false>, gridtools::aligned<0u>, gridtools::halo<1u, 2u, 3u> > >]’:
/home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:201:3:   required from ‘void GridToolsStorageViewTest_Construction_Test<gtest_TypeParam_>::TestBody() [with gtest_TypeParam_ = int]’
/home/adam/tmp/serialbox2/test/serialbox/core/frontend/gridtools/UnittestStorageView.cpp:485:1:   required from here
/home/adam/tmp/gridtools/include/storage/meta_storage_base.hpp:134:42: error: ‘gridtools::array<int, 3ul> gridtools::meta_storage_base<mpl_::integral_c<unsigned int, 3u>, gridtools::layout_map<0, 1, -1>, false>::m_strides’ is protected
         array< int_t, space_dimensions > m_strides;
                                          ^

Steps to reproduce:
Install vanilla Ubuntu 16.04 server and then
sudo apt install cmake build-essential gfortran git libboost-filesystem-dev libboost-system-dev libboost-chrono-dev libboost-log-dev
git clone --depth 1 https://github.com/eth-cscs/serialbox2.git
git clone --depth 1 git@github.com:GridTools/gridtools.git
mkdir serialbox2/build
cd serialbox2/build
cmake -DSERIALBOX_TESTING=ON -DSERIALBOX_TESTING_GRIDTOOLS=ON -DSERIALBOX_GRIDTOOLS_ROOT=../../gridtools -DGRIDTOOLS_ROOT=../../gridtools ..
make

I use up-to-date gridtools with last commit
commit 87d9ca198cd015b4c3f61d2c000c52fe67e8ff2e
Author: Hannes Vogt<EMAIL_ADDRESS>Date:   Fri Mar 10 11:19:01 2017 +0100

    Fix daint environment (#594)

    Bug description: The slurm partition was not set correctly in the slurm script and the timelimit was to strict.

    Changes: Increase timelimit to 15 min (instead of 10 min).

Hey Adam,
It is unlikely that the latest gridtools commit works as I activly developed the library in late 2016 and gridtools is a rapidly progressing library. I'll fix it as soon as I can get my hands on a computer. You will have it by noon.

Thanks! It is not that urgent. For me it can wait at least 2 work days. I started work on incorporation the Fortran part to our project.

The problem was that my original PR to allow serialbox2 to compile was never merged upstream. I created a new PR (https://github.com/eth-cscs/gridtools/pull/629). In the mean time you can pull from my fork (https://github.com/thfabian/gridtools/tree/serialbox2_fix) branch serialbox2_fix.
Let me know if there are any further problems.

@thfabian Do you know why your patch has not been merged into gridtools? Is it safe to use your fork of gridtools?

What happened to the https://github.com/eth-cscs/gridtools anyway? It doesn't seem to be on Github anymore...

gridtools underwent a major update of the storage infrastructure and thus the gridtools frontend of serialbox needs to some adjustments to function properly again. @havogt will take over development of serialbox but in the mean time you can use my fork (the changes are very minimal anyway).

The fork you mentioned still doesn't exist, (or maybe it is not available to me).

Yes, eth-cscs/gridtools is the internal repository. We will update GridTools/gridtools and make the fix available to you.

This issue is resolved with gridtools 1.05.01.


Owner could not be found on any guild

Please tick all applicable boxes.

[ O ] I am using Python 3.5.3 or higher (run python --version on the command line)
[ O ] I have followed the official guides to install the bot for my system
[ O ] I have updated my dependencies to the latest version using the appropriate update script

Which version are you using?

[ O ] The latest master version (release-260419)
[ ] The latest review version

What type of issue are you creating?

[ O ] Bug
[ ] Feature request
[ ] Question

Description of issue
I have all enabled Privileged Gateway Intents option in Discord Developer Portal, but every time I start the bot I get an error stating that the owner could not be found on any guild, the number of members in the server voice channel cannot be counted so if the AutoPause option is enabled, only one person can access the voice channel Even if you leave, the currently playing music will be paused.
Steps to reproduce
[INFO] launcher: Starting sanity checks
[INFO] launcher: Checking for Python 3.5+
[INFO] launcher: Checking console encoding
[INFO] launcher: Setting console encoding to UTF-8
[INFO] launcher: Ensuring we're in the right environment
[INFO] launcher: Adding local bins/ folder to path
[INFO] launcher: Required checks passed.
[INFO] launcher: Optional checks passed.
[INFO] launcher: Moving old musicbot log
Starting MusicBot release-260819-5-gc87dc05
Loaded autoplaylist with 2531 entries
Authenticated with Spotify successfully using client ID and secret.
Connected:<PHONE_NUMBER>75958794/Jade vine#0722
WARNING: Owner could not be found on any guild (id:<PHONE_NUMBER>16443393)

Log file
Please attach your MusicBot log file (located at logs/musicbot.log) to this issue. You can do so by dragging and dropping the file here. If you do not include your log file, you WILL be asked to provide one.
musicbot.log

intents aren't in the master branch yet, switch to review using git checkout review enjoy the new features on there as well!


Cann't use Ctrl+C, Ctrl+V

when I mouse select some text in doc,I just want copy line what I selected,but when I parse,it's not run.

Couldn't fully understand your description, but I guess I'm experiencing the same problem: copying text via Ctrl+V doesn't work, though it works via right mouse button. I guess it's because hotkeys are focused to work inside NP++, not the panel. It allows you to show/hide panel on hotkey, but copying text must be done from NP++ itself too, not from the panel

The copy event (CTRL+C) is captured by npp and is not passed to the underlying IE (which is embedded).
Best workaround is to use right click "Copy".


retain formatting option when creating 1st post of discussion

When creating a discussion, the formatting option (rich/plain) is not used

Thank you, @answeb!

You're welcome !
How can I get this fix in my project ? I'm using ^1.4 in my composer.json.

I'll take a release now, and once a release is ready, you can run composer update andreaselia/laravel-firefly

Release has been tagged @answeb 👍


Clicking on recipe shrinks on Android Device

Expected Behaviour: Open based.cooking, Find the recipe to open, click on it, recipe page appears, cook it.
Bug: Upon clicking the link/name of the recipe, the recipe hyperlink shrinks instead of opening the webpage. Then a reclick on the same link/name is required to open the webpage.
Tested on:
Device- Poco F1
Browser- Brave
Android Version- Android 11

I tested on both Brave and Bromite, i get the same error too

My pull request might have fixed this issue, please try again now.

Yes it is fixed now. Thank You