Don't evaluate primary key defaults multiple times

Summary of the changes / Why this improves CrateDB
We compute the primary key value early because it is needed for sharding.
This led to a problem with nondeterministic DEFAULT functions
because those got computed a second time when the source gets generated.
We ended up using the _id of the first computation and the primary key column
values from the second generation. Leading to a mismatch.
Closes https://github.com/crate/crate/issues/12427
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

retest this please
Unrelated errors:
java.lang.AssertionError: node2 has at least 3 shards
Expected: a value equal to or greater than <3>
     but: <0> was less than <3>
	at __randomizedtesting.SeedInfo.seed([42907E6DF70CED29:26A510A4299AB9C0]:0)
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
	at org.junit.Assert.assertThat(Assert.java:964)
	at io.crate.integrationtests.DiskUsagesITest.lambda$testRerouteOccursOnDiskPassingHighWatermark$6(DiskUsagesITest.java:135)

org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple Failures (2 failures)
	com.carrotsearch.randomizedtesting.ThreadLeakError: 2 threads leaked from SUITE scope at io.crate.integrationtests.LogicalReplicationITest:
   1) Thread[id=2669, name=cratedb[subscriber1][netty-worker][T#1], state=RUNNABLE, group=TGRP-LogicalReplicationITest]


v4: Some bugs on ion-list

Describe the Bug
We try to use your ion-list using alpha.7 with latest beta documentation.
We also created a demo repo https://github.com/mburger81/ionic4-tests where you can navigate to Lists menu to see bugs and simulate them.
This is what we have figured out, or we think we have figured out :)

Breaking change, in v3 ion-list for default used lines, in v4 it seems the default is none.

Having a look on the demo site https://beta.ionicframework.com/docs/api/list, it seems on IOS the default is with lines, in MD the default is none, in v3 there was no difference between v3 and v4 between the two modes

The full attribute wasn't in v3, but having a look at the screenshots the inset property has a different look and behavior

v3

v4

Thanks for the issue! I'm not sure I understand what the bug is here. From the screenshots of v4 and the code here https://github.com/mburger81/ionic4-tests/blob/master/src/app/pages/list/list.page.html, it appears to be working as intended. Could you explain more on what you're expecting?
In v3 it wasn't possible to change the borders/lines on items unless you modified the Sass/CSS directly. Without seeing the code for that example, I think you are using the inset property of a list, which is a boolean property that adds some margin around the list (see the old documentation https://ionicframework.com/docs/components/#inset-list), but this is different from the newly added lines property.
Please let me know if I am misunderstanding you. Thanks! 🙂

I'm going to close this because it seems to be working as it should, but please let me know if I am wrong. Thanks!


Invoke the callback, when browser cannot validate our cert

Issue related to the https://github.com/AdguardTeam/AdguardForWindows/issues/2390.
We need to get at least the domain and the processName as a parameters for this callback

Okay, we may turn EvCertificateEvent into just CertificateEvent of two types:

UNKNOWN_CA
EV_CERT

core/pull-requests/1218

core/pull-requests/1226


Add meta types for CSF

According this https://github.com/storybookjs/storybook/issues/7677
Internal usage in storybook apps, like @storybook/react
import { ReactElement } from 'react';
import { DecoratorFunction, StoryContext, StoryFn } from '@storybook/addons';
import {
  KindMeta as KindMetaBase,
  StoryMeta as StoryMetaBase,
  DecoratorFunction as DecoratorFunctionBase,
  DefaultParameters
} from '@storybook/csf';

type ReactDecoratorFunction = DecoratorFunctionBase<StoryContext, StoryFn<ReactElement>>;

export type KindMeta<Component = unknown> = KindMetaBase<
  ReactDecoratorFunction ,
  DefaultParameters,
  Component
>;
export type StoryMeta<Parameters = DefaultParameters> = StoryMetaBase<
  StoryContext,
  StoryFn<ReactElement>,
  ReactDecoratorFunction ,
  Parameters
>;

// NOTE Optionally we could export more flexible type to allow pass generic for parameters
export type KindMetaWithParams<Parameters, Component = unknown> = KindMetaBase<
  ReactDecoratorFunction ,
  Parameters,
  Component
>;

How to use types in projects
import React from 'react';
import { KindMeta, StoryMeta } from '@storybook/react';
import Button from './button';

const kind: KindMeta<Button> = {
  title: 'Button',
  component: Button
};

export default kind;

export const Simple: StoryMeta = () => <Button />;
Simple.story = {
 /* ... */
};

How to user can get complete story parameters typings. User must define types.ts file somewhere in project, where he could import all his addons typings and override StoryMeta's parameters. And then he could use his StoryMeta for CSF stories.
// somewhere in `.storybook/types.ts` file
import { Parameters as KnobsParameters } from '@storybook/addon-knob'
import { Parameters as A11yParameters } from '@storybook/addon-a11y'
/* other addon imports */
import { KindMetaWithParams as KindMetaBase, StoryMeta as StoryMetaBase} from '@storybook/react'

export type StoryParameters = KnobsParameters & A11yParameters
export type KindMeta<Component = unknown> = KindMetaBase<StoryParameters, Component>;
export type StoryMeta = StoryMetaBase<StoryParameters>

I don't really understand the TS but it seems like a good idea.

@gaetanmaisse, thank you for review. Type naming is discussable, I don't have any against StoryMetadata, so I could rename it. Type tests sounds reasonable, I'll add it.

@gaetanmaisse thanks for the review! i don't think i ever released the previous version, so let's just do whatever's best.

@shilman, will there be more comments?
@gaetanmaisse, could you please look one more time?

@wKich thanks for your patience on this. before i merge, can you make one small change which is to actually add a few stories to the bottom of storyt.test.ts?

@shilman done

@wKich AWESOME 💯

:rocket: PR was released in v0.0.2-next.0 :rocket:


OpenXR support?

Khronos just released the OpenXR 0.90 spec:
https://www.khronos.org/news/press/khronos-releases-openxr-0.90-provisional-specification-for-high-performance-access-ar-vr-platforms-and-devices
Are there any plans to support this?

OpenHMD is actually part of Monado, a full open source OpenXR runtime and can already be used with OpenXR applications!
https://monado.freedesktop.org/

Awesome!


Support ; for repeating movements

I am relatively new to vim, and I don't know whether this should just work but I have broke something in my config or it is just impossible to do that. If it is the latter I would like to understand the reason behind it.
Is your feature request related to a problem? Please describe.
I would like to be able to repeat motion ]m/]M etc with ;, the same way that I repeat motion from f/F/t/T
Additional context
I am aware of the existence of vim-repeat that allows repeating custom actions, I am surprised that there is nothing like that for repeating motions.

https://github.com/vim-scripts/repeatable-motions.vim

https://github.com/vim-scripts/repeatable-motions.vim
This exists, however I have not checked it.

Thanks for the pointer.
As far as I know, using the same ; key is not possible and you need to make a separate binding for this TS textobjects, if it gets implemented.
In order to use ; key, you need to override all f, F, t, T keys to work as usual and remember the last movement with TS textobjects. This is a dirty solution which can potentially cause problems with other plugins.. This is also how repeatable-motions.vim implements this.
https://github.com/vim-scripts/repeatable-motions.vim/blob/d51360269b312a34922d3de412505af069565e77/plugin/repeatable-motions.vim#L390-L393

I tried several stuff.

Adding { repeatable = true } here:
https://github.com/nvim-treesitter/nvim-treesitter-textobjects/blob/37a810aaa3066f2794753547ad81c7a1fe256a66/lua/nvim-treesitter/textobjects/move.lua#L87

It works in normal mode but not in visual mode.

Using tpope/vim-repeat

map <Plug>nextfunc <cmd>TSTextobjectGotoNextStart @function.outer<CR>
silent! call repeat#set("\<Plug>nextfunc", v:count)
map <C-A-l> <Plug>nextfunc

It works in normal mode but not in visual mode.

Adding { repeatable = true } here:

because I only allowed in normal mode. I think it is very unusual for . to be used for non-edit operations, this would not be expected. I would just add a Lua function that executes the last motion this plugin performed. This function could be enabled for "n", "x", "o". People can then map it to something they like

I agree that using . for non-edit operations would be counter-intuitive, that is why I asked originally for ; as it is used by default to repeat motions.

Adding { repeatable = true } here:
It works in normal mode but not in visual mode.

That would be already an improvement for me. Is there an option I can configure that externally?

@ghostbuster91 I am implementing this feature and it will come very soon.

@ghostbuster91 Do you mind if you try #359 and let me know how you like it? Any feedback would be appreciated!

@kiyoon During work on the separate version of that feature I came across some weird behavior. I think that your version might be also affected but I didn't have time yet to confirm that. I will try to do it in upcoming days.

@kiyoon During the work on the separate version of that feature I came across some weird behavior. I think that your version might be also affected but I didn't have time yet to confirm that. I will try to do it in upcoming days.

Thanks for reporting. Let me know what kind of behaviour you observed

@kiyoon Sorry false alarm, it was just me being tired, all good.

Sorry to comment on a closed issue: does this refer to ts_repeat_move (with ;/,)  as per README? I cannot get the repetition to work: is it supposed to work in all cases (namely for all text objects)?

Sorry to comment on a closed issue: does this refer to ts_repeat_move (with ;/,) as per README? I cannot get the repetition to work: is it supposed to work in all cases (namely for all text objects)?

Same here.


Obey mouse setting

Is there any way to disable mouse support in neovide? I explicitly do set mouse= because I do not like things to happen when I click on vim but neovide seems to ignore this setting.
Is this a bug or an intended feature? I would like a way to disable it if possible.

Should be fixed


bug: ion-checkbox checked attribute

Type: bug
Ionic Version: 2.x
Platform: all
ion-checkbox checked attribute values "false" and "true" shows ion-checkbox checked on 2.0.0-alpha.48. checked="true" and checked="" works fine, but I don't know if it's a code or documentation bug.

Not seeing this with alpha.53: https://github.com/driftyco/ionic/blob/2.0/CHANGELOG.md#200-alpha53-2016-01-28
Please let me know if this is still an issue, thanks!


Entrypoint option does not support multiple commands separated by && or ;

Rancher Version:
Rancher v1.1.3
Cattle  v<IP_ADDRESS>
User Interface  v1.1.12
Rancher Compose v0.8.6
Docker Version:
OS and where are the hosts located? (cloud, bare metal, etc):
Amazon linux on EC2
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
type a long set of commands in the entrypoint field when creating a service eg:
make migrate && gunicorn -b <IP_ADDRESS>:8000 app.wsgi --access-logfile -
Results:
error out while trying to pass everything as parameters to make
Expected:
run make and then gunicorn, normal Dockerfile/shell behaviour

Can you share what the equivalent docker run command would be so I can try to reproduce?

docker run -ti --entrypoint sh alpine:latest -c "true && echo hi"
apparently --entrypoint on the command line only lets you override using the non shell version of entrypoint. if this is the case for the ui it should say so and only accepts a binary name... but usually if you are overriding is because you need something more complex

This was a bug in the UI parsing the command into an array to pass to the API..

it still should be documented that it will parse it into an array and not be the shell version of entrypoint.

Version 1.2 - not fixed?
UI changes && to && and it doesn't seem to work

I have solved this (in v1.3.1) with an Entry Point of /bin/sh -c and a Command of something like this: 'echo "asdf" > /tmp/test1 && cp /tmp/test1 /tmp/test2 && cat /tmp/test2 && /bin/sh'

Yes it was mostly fixed in 1.3 but cloning brought back all the control character escaped (e.g. echo hello \&\& echo world)

Version - v1.4.0-rc6
Verified fixed.

Is having an Entrypoint necessary in the UI?
If i just want to run touch /success
Do I need the full path? /usr/bin/touch /success
Do I need to wrap the command in quotations? "/usr/bin/touch /success"

I'm having this issue with exit code 127. My Entrypoint in dockerfile is
ENTRYPOINT ["/bootstrap.sh", "cd /app/myproject/output && dotnet myproject.dll"]
and my bootstrap.sh does end with exec "$@"


Is it possible to use FindBy with data from external resource (JSON, Resources.resx, etc.)

Hello,
I am testing an application where I would ideally like to contain all my Id's, CSS selectors, etc. and then load them into the page objects FindBy. The reason for this being that I run these tests across multiple builds and databases that may have minor discrepancies in say, an Id field, but in the end is the same application.
current example:
// DB-1 id="id_in_div_3"
// DB-2 id="id_in_div_4"
[FindById("id_in_div_3")]
public Button<_> MyButton { get; private set; }

desired example:
[FindById(SomeIdNameFromFileOrResource)]
public Button<_> MyButton { get; private set; }

I may be trying to go about this the wrong way, but is this possible?

I am closing this issue as it is quite old. Hope you solved that problem.


isNew & isUpdated classes on frontend are fishy

Looks like isNew animation when adding new data is not working as expected. Investigate and fix

Also useTimeoutPolling hook has a bug in result mapping logic. Those those empty rows appear very often.

In some cases it also shows invalid number of accounts (some items are duplicated), there is a total of 3 accounts in the db, but UI shows this:

Solved polling problem
Fixed messed up layout


Flexible tlogs

Catchup from an old arakoon to a newer one using flexible rollover will give issues ...
So it should either be blocked or fixed (by only streaming entries to older nodes).
This means you can put a new last_entries variant next to it and use that opportunity to also send along information regarding start/end i of a tlog?

There's still a travis test failure https://s3.amazonaws.com/archive.travis-ci.org/jobs/108264111/log.txt
Failure: universe:11:system:2:startup:2:ahead_master_loses_role

value for 'invalidkey' should not be in store

ok


Proposal: IncrementalHashAlgorithm

Bytes used as an input to the HashAlgorithm are often not in a single span. For that purpose the .NET standard library has the IncrementalHash class. I propose implementing something similar in NSec. Base class would in that case probably look something like this:
public sealed class IncrementalHashAlgorithm : Algorithm, IDisposable
{
	public void AppendData(ReadOnlySpan<byte> data);
 	public bool TryGetHashAndReset(Span<byte> destination, out int bytesWritten);
}

(This is the way IncrementalHash is implemented in .NET Core 2.1, see dotnet/corefx#22614.)
In case that you approve this addition to the API, I would be happy to submit the pull request.

That sounds like a useful addition (and is actually on my to-do list). I'd like to iterate a bit on the API before implementation starts.
First, zero-allocation. Incremental hashing might be used in performance-critical code and shouldn't require the allocation of a class instance. A struct would be the obvious alternative, but mutable structs are evil™.
Second, there are some interesting additions to the System.Buffers namespace in the System.Memory package. It seems one option could be letting the hash algorithm pull from a sequence of spans rather than pushing several spans to it.

I don't think you can avoid the allocation in this case. You have to keep the state of the hash function across the update calls, but you can't stackalloc it like you did in the HashAlgorithm.
Sequence of spans could work, but that would be slightly weird API for the users (every library I've seen so far has some version of Update/Finish functions).

Added two more items.
I was thinking if something like this could work:
Span<IncrementalHashState> state = stackalloc IncrementalHashState[1];
algorithm.Init(state);
algorithm.Update(state, span1);
algorithm.Update(state, span2);
algorithm.Update(state, span3);
algorithm.Final(state, hash);

Or maybe a mutable struct wouldn't be that evil at all:
algorithm.Init(out IncrementalHashState state);
algorithm.Update(ref state, span1);
algorithm.Update(ref state, span2);
algorithm.Update(ref state, span3);
algorithm.Final(ref state, hash);

(where IncrementalHashState in both cases is a struct without public members).
I agree that a sequence accepting API would be somewhat weird for this use case (though maybe a nice addition to the single-span and update/finish APIs).

That would work, but it breaks encapsulation, and it's very ugly approach, especially compared to the rest of the library, which is super simple and elegant.
What about just embedding the state (which would be a struct) in the algorithm object? You have to allocate the algorithm object anyway, and it doesn't really matter if its size is 8 bytes or 208 bytes. Something like this:
[StructLayout(LayoutKind.Sequential, Size = 104)]
public struct Sha256State
{
}

public class Sha256Algorithm
{
	private readonly Sha256State state;
}

You've discovered why incremental hashing isn't already part of the library :-)
Embedding the state is somewhat ugly, since all algorithm classes are stateless right now - and therefore thread-safe. (You're not expected to allocate a new algorithm instance for each operation.) And it doesn't satisfy the alignment requirement of Blake2b (which my proposal above doesn't as well, sadly).
The alignment requirements basically means that the state must be pinned the whole time or copied on each update.

Proposal:
var hash = new byte[sha256.DefaultHashSize];
IncrementalHash.Initialize(sha256, hash.Length, out var state);
IncrementalHash.Update(ref state, span1);
IncrementalHash.Update(ref state, span2);
IncrementalHash.Update(ref state, span3);
IncrementalHash.Finalize(ref state, hash);

namespace NSec.Cryptography
{
    public struct IncrementalHash
    {
        public static void Initialize(HashAlgorithm algorithm, int hashSize, out IncrementalHash state);
        public static void Update(ref IncrementalHash state, ReadOnlySpan<byte> data);
        public static byte[] Finalize(ref IncrementalHash data);
        public static void Finalize(ref IncrementalHash state, Span<byte> hash);
        public static void FinalizeAndVerify(ref Incremental state, ReadOnlySpan<byte> hash);
        public static bool FinalizeAndTryVerify(ref Incremental state, ReadOnlySpan<byte> hash);
    }

    public struct IncrementalMac
    {
        public static void Initialize(MacAlgorithm algorithm, Key key, int macSize, out IncrementalMac state);
        public static void Update(ref IncrementalMac state, ReadOnlySpan<byte> data);
        public static byte[] Finalize(ref IncrementalMac data);
        public static void Finalize(ref IncrementalMac data, Span<byte> mac);
        public static void FinalizeAndVerify(ref Incremental state, ReadOnlySpan<byte> mac);
        public static bool FinalizeAndTryVerify(ref Incremental state, ReadOnlySpan<byte> mac);
    }
}

@Metalnem Do you have an opinion about the above API shape? It's not an evil mutable struct, doesn't break encapsulation, and looks relatively simple to me.

Most of what I've said in the previous comment still holds (the state remains exposed instead of being hidden inside the object instance).
Besides that, this API looks more low-level than the rest of the library (it's basically the direct translation of the C API).
In my opinion, it all boils down to this: in this case you can either have a zero-allocation API, or a standard library quality API. You are in favor of the former, I'm in favor of the latter :)

Not sure if the belongs to this issue, but I don’t think that you need all the Verify functions to be instance methods. I believe they are all doing the same thing - caling some constant-time memory compare function? If that’s the case, maybe they could be just static methods in the HashAlgorithm/MacAlgorithm class?

@Metalnem Thanks for taking a look.
I'm trying to argue that the difference isn't actually that big :smile:. In fact, the only difference is that you write StaticMethod(ref state) instead of state.InstanceMethod(). The state is hidden in the instance either way; you don't get more access to the internal state than with the other.
You get a bit more control of how the state is passed around (by-reference or by-value) and zero-allocation with structs, which I think is desirable.

The Verify methods indeed just provide a hash/MAC calculation with a constant-time memory compare in one step. They essentially exist only to make constant-time compare easier to use than the built-in SequenceEqual method. Of course, I could simplify the API a bit by letting users do the verification in two steps, but I think the convenience methods are a small win here.
The one step verification methods need know which algorithm you want to use. If they were static, you'd need to pass the algorithm to them as a parameter. Here, I think algorithm.InstanceMethod() is more discoverable than StaticMethod(algorithm), because the primary Hash/Mac methods are (and must be) instance methods.
Feedback like this is very welcome, btw, while there's still time for breaking changes until System.Memory gets stable. I see you're working on a Noise implementation; NSec is exactly intended for use cases like that.  Do you see any other issues that would prevent NSec from being used to (theoretically speaking) replace the crypto algorithm classes in your code?

The difference may look small, but if you are aiming for the wide adoption of the library, you should probably provide the API that feels natural. I will use this library in any case, but other users may end up confused.
Do you really need to know the algorithm for the verification? You only have to compare the two byte spans, irrespective of the algorithm that produced them. Anyway, this is more of a nitpick than a real issue (it's just that I always prefer the smallest API surface possible).
I was waiting for the NSec to be released to start working on my Noise implementation, but finally gave up because I didn't want to depend on the release of .NET Core 2.1 (you released the first preview version after I started my implementation). I'm currently directly using libsodium, but I'll experiment with replacing my interop code with NSec some time this week. I'll give you more feedback when that happens.


Continued regardless of answer to Proceed?

The issue
Answered 'n' and it appeared to proceed.
Ctrl-C and Ctrl-Z did not halt it. Possibly still trying to process the massive db? There is something else wrong with my databases, users, or command - I don't get the list of changes before Proceed? is offered. It appeared to be busy or hang, cursor blinking.
Stack versions:
Windows7
Python 3.4.2
pip (1.5.6)
pymssql (2.1.1)
rdbms-subsetter (0.2.1)
setuptools (2.1)
SQLAlchemy (0.9.8)

Thanks for the project, will be watching closely!
We are trying to use it for our 250GB Microsoft SQL Server DB, no luck so far. Took me a while to figure out the dependencies to use and the connection string, so that would really promote adoption for casual users. I made it to the point of getting KeyErrors.

tried reverting to check.. no longer stops at the Proceed point.. closing until I figure it out

just to keep the notes:
did a few more tries with Python3.4+pymssql, Python 3.3+pyodbc, different size fraction, schema.
Getting alot of:
No approximation known for driver pyodbc
DEBUG:root:failed to get approximate rowcount for table_name
I see that it's 3.4 in travis. That and pymssql seemed to at least show the rows before Proceed?
In the sqlalchemy page they mention adodbapi driver but it's still on an old version of sqlalchemy
If on linux it would make more sense to check out tds route.


ChangeCipherSpec is not decrypted/authenticated

Hello, I noticed that there's a special case that exempts ChangeCipherSpec from decryption. This is true for every cipher.
https://github.com/pion/dtls/blob/77fae27e533bb08a75644fd6e92a71de9df4d619/crypto_cbc.go#L99
The act of decryption also performs authentication. Without this, attackers can forge and send ChangeCipherSpec packets even when a connection is otherwise encrypted and authenticated.
Today, these packets would be able to kill a connection by bumping the epoch. This can be done blindly by sending a packet to each UDP port, although ICE and connection mapping would make it harder (requires spoofed addresses).
There may be future ramifications and there's no reason to not decrypt/authenticate these packets.

Thanks for the report @kixelated !
How does bumping the epoch effect the connection? The remote epoch is only taken into account if we need to replay the initial handshake.

I am all for authenticating these though, but since they occur in epoch 0 they all can’t be authenticated. Need to confirm

Yeah, it's probably fine with the current pion implementation. You should really reject ChangeCipherRecord packets unless you're in the right flight of the handshake.
   Note that because DTLS records may be reordered, a record from epoch
   1 may be received after epoch 2 has begun.  In general,
   implementations SHOULD discard packets from earlier epochs, but if
   packet loss causes noticeable problems they MAY choose to retain
   keying material from previous epochs for up to the default MSL
   specified for TCP [TCP] to allow for packet reordering.  (Note that
   the intention here is that implementors use the current guidance from
   the IETF for MSL, not that they attempt to interrogate the MSL that
   the system TCP stack is using.)  Until the handshake has completed,
   implementations MUST accept packets from the old epoch.

Closing since ChangeCipherSpec isn't meant to be encrypted (last packet sent before encryption)
The lack of a state machine (and us handling packets out of order) is a concern though, I am going to create some other tickets for this!


Rkt should support setting supplemental groups on containers

Currently it is possible to set the UID/GID on a container process, but not possible to control the supplemental groups.  It would be very convenient to have supplemental group control to enable sharing volumes across containers running as different UID/GIDs.

https://github.com/appc/spec/issues/339

@jonboulle Thanks, I think I must have even read that issue before -- should we close this one, if there's already an issue to add it to the spec?

@pmorie Nope we can leave this open, it might encourage me to fix that in the spec sooner (or feel free to put up a PR yourself if you'd like to see this sooner than later :-)

This has been fixed in the spec but now needs to be implemented in rkt


Drop support for configure AssignPiblicIp for headnode

Drop support for configure AssignPiblicIp for headnode because we will need to create an ENI for headnode. ENI and AssignPiblicIp can not be configured together.

Unit tests are failing.


feature/services-section: Section Services

SECTION SERVICES
• Mobile and desktop version were implemented.
NOTES
• I moved Section Services from style.css to home.css
• I moved some general styles from home.css to style.css, this way we can keep the general reset in one place.
• I replaced PNG icons for SVG instead.
• I deleted the media query code that I wrote because I hadn’t seen the media query setup that already exists, sorry my bad.
• I did refactor of the code based in Juanse’s feedback.
This is the way how it looks
Desktop Version

Mobile Version

@ArleyAV Hi, we do have a defined unique breakpoint at 960px, how ever this i have found is not easy to know as it is not very clear in our documentation, i will find a way to make this information visible.
Taking that into account the breakpoint structure you have, even being well implemented might not suit the project correctly, lets discuss this offline as doing it in comments would be redundant and complicated.

Please add a SS of your work both on mobile and desktop viewports tho the PR description.

Please use images in SVG instead of PNG, this way we can avoid having multi-size assets.

Great work with the PR naming, Description, commit message and css structure, its super clean.

In the sketch cloud  in your section  i see a botton "cotiza tu estadia" and in your photo i dont  see it.

please remove all the .DS_STORE files, these are just trash data.

why the footer icons are inline block? ; in developt is fine.

@jhonatanrojasbastidas
I defined a class for images and videos of full width, this mean every image must be fitted regarding the size of the container instead its own size

Hi! I followed your recomendations and comments. You can check again. I fixed the vertical icons in the footer.

Looks pretty good, just remove that last .DS_store


Per-Guild Command/Command Category Enable/Disable

Describe your proposal
Allow guild owners/admins to disable/enable commands and command categories in their guild
Use-Cases for your proposal
There are millions of bots out there, and a lot of overlap between them. Giving guild owners an opportunity to disable features in your bot (when using the Klasa framework) is a great way to make sure that your bot sticks around on their server rather than getting phased out in favor of something else
Expected and actual behavior
disable commandName => when run by guild owner, disables the command or command category in their server only
same with enable
Further details

This is very easy to do on your own. Create a disabledCategories setting as string with array: true on the DefaultGuildSchema, and an inhibitor that simply does return msg.guild && msg.guild.settings.get('disabledCategories ').includes(command.category). That's all you need and that even updates the help for those guilds. This is something that will not be included in the core library, so I am closing this issue.

That's, absolutely amazing. Thanks for the tip!


[benchmark] Benchmark cannot use custom AK/SK.

Please describe the issue you observed:

Cannot use custom ak/sk, when using benchmark test,

Please tell us about your environment:

rocketmq 4.9.2

Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

Support custom ak/sk parameters.

merged


better catalogIcon display

minor css changes. I added max-width so logos like Kibana looks better. Moreover certan svg ratio went out of the box, e.g. the logo for Plone I am adding in https://github.com/eea/rancher-catalog/tree/master/templates/plone

Hi @demarant, this is getting redesigned in the reskin branch (which will be master probably on Friday) and they are fixed width round-rects now:

@vincent99: thanks! Indeed it looked weird with inline CSS their. I am glad see these improvements.


SSO(Single Sign-on)

I want to integrate the Superset with my web project, but I am a new hand of python, How can I implement SSO with Superset ?  Please HELP ME !!!

this is probably not the best place to ask such a question.
superset uses flask-appbuilder which supports oauth2 out of the box, you should check out their documentation


Hashes of domains should be consistent with equality

The logic of the hash function should be the same as that of isequal, since the intention is that a == b should imply hash(a) == hash(b). I doubt this is the case right now.
An example when using intervals is given in https://github.com/JuliaMath/IntervalSets.jl/issues/167:
julia> unique([2..1, 3..1])
2-element Vector{ClosedInterval{Int64}}:
 2 .. 1
 3 .. 1

julia> 2..1 == 3..1
true

The fact that 2..1 and 3..1 hash to different values results in unique returning two elements rather than one. DomainSets has an elaborate way of checking for equality of domains, but the hash function doesn't, so I bet there are many more examples of this type of error.

Bump, and in addition: defining hash for intervals should not be done in DomainSets.

I've concluded that this is hard to do. It is harder than deciding on the equality of domains, because you only have a single argument and not a combination of arguments. Since Point(0.5) == 0.5..0.5 their hashes should be the same. But a closed ball with radius zero is also a point, so should have the same hash. A unit ball in 1D is a unit interval. Etcetera.

I think the interval constructor should force the left to be smaller than the right. It's expensive but it's similar to what ranges in Base do.


Access to the Veeam\backup path denied after v11 Veeam update

Hi,
We upgraded to v11 recently and since then we've been getting the following log output for the sensor:
Disconnect-VBRServer : Access to the path 'Veeam\Backup' is denied.
I updated the script to the latest in the repo here but same issue.

Hi,
Another user (Till) reported this on my blog:
https://mycloudrevolution.com/en/2020/01/27/prtg-veeam-sensor-retrospective/
I was need able to reproduce that and need a few more Details about your environment:

have you installed the vbr console on the probe or are you using PS remote?
which OS are you using?
have you upgraded the console after vbr upgrade?
have you tried to execute the script manually in the PowerShell?

Best wishes
Markus

Hi Markus thanks for the reply,

have you installed the vbr console on the probe or are you using PS remote? | VBR Console is on the probe.
which OS are you using? | 2012 R2 Standard
have you upgraded the console after vbr upgrade? | Yes both are on V<IP_ADDRESS>7
have you tried to execute the script manually in the PowerShell? | Manually running the script shows no error.

Hello,
I assume the issue #77 has the same root cause.

What are the local permissions of the user the probe uses to call the script?

Hi guys, same problem here, I've read all #77 #78 and this.
have you installed the vbr console on the probe or are you using PS remote? | VBR Console is on the probe.
which OS are you using? | 2019 Datacenter
have you upgraded the console after vbr upgrade? | Yes both are on V<IP_ADDRESS>7
have you tried to execute the script manually in the PowerShell? | Manually running the script shows no error.

Duplicate of #77

This is a really strange issue. I am not able to reproduce that.
@cipo80 which permisses has the user on the local system which the PRTG Probe uses to run the sensor?

Hi All,
in my case the user has local administrative rights, and with the veeam console (installed on the probe server) I can login with my user an see the backups...
seems, that everything is OK.
In the past sometimes I have to correct the permission in the regedit (HKLM\SOFTWARE\Veeam\Veeam Backup and Replication)
But that is also fine in my environment

This is a really strange issue. I am not able to reproduce that.
@cipo80 which permisses has the user on the local system which the PRTG Probe uses to run the sensor?

Hi @vMarkusK , thank you for the reply,
the user has local administrative rights, like @carsten0407 I can correctly login by console installed on the probe server.
I've also try to remove/reinstall the console.
If I run the script by PS with .\PSx64.exe work correctly

I have already talked to prtgtools (vendor of PSx64) to make sure they do not use any special parameters - they do not.
Have you guys enabled UAC?

Hi @cipo80https://github.com/cipo80
Are you sure?
If I run the scritp without PSx64.exe it seems to work, with PSx64.exe, at the beginning there is an “0”
The community is not sure that this is the problem
Mit freundlichen Grüßen / best regards
i. A. Carsten Trautmann
Senior System Engineer
IT-Service
[http://support.it.konicaminolta.de/signatures/KM_LOGO.jpg]
Konica Minolta Business Solutions Deutschland GmbH
Mittlerer Pfad 1, 70499 Stuttgart, Germany
Phone:
+49 (711) 1385 - 131tel:+497111385131
Fax:
+49 (711) 1385 - 222
Mail:
<EMAIL_ADDRESS>Web:
www.konicaminolta.dehttp://www.konicaminolta.de
District Court / Amtsgericht: Hannover, HRB 61209
Management / Geschäftsführer:
Joerg Hartmann & Kenichiro Fukasawa
Aufsichtsratsvorsitzender: Jens Venrath
Informationen über die Verarbeitung Ihrer personenbezogenen Daten durch uns können Sie unter https://www.konicaminolta.de/de/business-solutions/meta/dseg.html einsehen.
[http://support.it.konicaminolta.de/signatures/emailPrinzip.jpg]
Von: cipo80 @.>
Gesendet: Montag, 22. März 2021 12:34
An: vMarkusK/Advanced-PRTG-Sensors @.>
Cc: Trautmann, Carsten @.>; Mention @.>
Betreff: Re: [vMarkusK/Advanced-PRTG-Sensors] Access to the Veeam\backup path denied after v11 Veeam update (#80)
This is a really strange issue. I am not able to reproduce that.
@cipo80https://github.com/cipo80 which permisses has the user on the local system which the PRTG Probe uses to run the sensor?
Hi @vMarkusKhttps://github.com/vMarkusK , thank you for the reply,
the user has local administrative rights, like @carsten0407https://github.com/carsten0407 I can correctly login by console installed on the probe server.
I've also try to remove/reinstall the console.
If I run the script by PS with .\PSx64.exe work correctly
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/vMarkusK/Advanced-PRTG-Sensors/issues/80#issuecomment-803993785, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APIS7JAUWCU66IQLET27ZHDTE4TLZANCNFSM4ZJ4CGDA.

I have already talked to prtgtools (vendor of PSx64) to make sure they do not use any special parameters - they do not.
Have you guys enabled UAC?

Just check, UAC is off

Hi @carsten0407 , in my case both working (psx64 and without it) by PS and both aren't working by PRTG.
Without psx64 is it a XML Custom EXE/Script Sensor standard without parameter, right?

Strange, in my case the script is working in my ISE, with PSx64 and CMD, I get the leading =”0”
in PRTG also the XML-Error.
My Protocol in PRTG looks like @cipo80 yours?
Disconnect-VBRServer : Access to the path  "Veeam\Backup" was
denied.
In C:\Program Files (x86)\PRTG Network Monitor\custom
sensors\EXEXML\PRTG-VeeamBRStatsLocalBackupV2.0.ps1:66 Zeichen:5

Disconnect-VBRServer -ErrorAction SilentlyContinue

~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [], UnauthorizedAccessExceptio
n
FullyQualifiedErrorId : System.UnauthorizedAccessException

@.***D71F20.9DA43D40]
Mit freundlichen Grüßen / best regards
i. A. Carsten Trautmann
Senior System Engineer
IT-Service
[http://support.it.konicaminolta.de/signatures/KM_LOGO.jpg]
Konica Minolta Business Solutions Deutschland GmbH
Mittlerer Pfad 1, 70499 Stuttgart, Germany
Phone:
+49 (711) 1385 - 131tel:+497111385131
Fax:
+49 (711) 1385 - 222
Mail:
<EMAIL_ADDRESS>Web:
www.konicaminolta.dehttp://www.konicaminolta.de
District Court / Amtsgericht: Hannover, HRB 61209
Management / Geschäftsführer:
Joerg Hartmann & Kenichiro Fukasawa
Aufsichtsratsvorsitzender: Jens Venrath
Informationen über die Verarbeitung Ihrer personenbezogenen Daten durch uns können Sie unter https://www.konicaminolta.de/de/business-solutions/meta/dseg.html einsehen.
[http://support.it.konicaminolta.de/signatures/emailPrinzip.jpg]
Von: cipo80 @.>
Gesendet: Montag, 22. März 2021 13:11
An: vMarkusK/Advanced-PRTG-Sensors @.>
Cc: Trautmann, Carsten @.>; Mention @.>
Betreff: Re: [vMarkusK/Advanced-PRTG-Sensors] Access to the Veeam\backup path denied after v11 Veeam update (#80)
Hi @carsten0407https://github.com/carsten0407 , in my case both working (psx64 and without it) by PS and both aren't working by PRTG.
Without psx64 is it a XML Custom EXE/Script Sensor standard without parameter, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/vMarkusK/Advanced-PRTG-Sensors/issues/80#issuecomment-804014802, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APIS7JAEMLGDBCL6GAPKJODTE4XWTANCNFSM4ZJ4CGDA.

..thanx to everybody who works on it….
Mit freundlichen Grüßen / best regards
i. A. Carsten Trautmann
Senior System Engineer
IT-Service
[http://support.it.konicaminolta.de/signatures/KM_LOGO.jpg]
Konica Minolta Business Solutions Deutschland GmbH
Mittlerer Pfad 1, 70499 Stuttgart, Germany
Phone:
+49 (711) 1385 - 131tel:+497111385131
Fax:
+49 (711) 1385 - 222
Mail:
<EMAIL_ADDRESS>Web:
www.konicaminolta.dehttp://www.konicaminolta.de
District Court / Amtsgericht: Hannover, HRB 61209
Management / Geschäftsführer:
Joerg Hartmann & Kenichiro Fukasawa
Aufsichtsratsvorsitzender: Jens Venrath
Informationen über die Verarbeitung Ihrer personenbezogenen Daten durch uns können Sie unter https://www.konicaminolta.de/de/business-solutions/meta/dseg.html einsehen.
[http://support.it.konicaminolta.de/signatures/emailPrinzip.jpg]
Von: Trautmann, Carsten
Gesendet: Montag, 22. März 2021 13:43
An: vMarkusK/Advanced-PRTG-Sensors @.>; vMarkusK/Advanced-PRTG-Sensors @.>
Cc: Mention @.***>
Betreff: AW: [vMarkusK/Advanced-PRTG-Sensors] Access to the Veeam\backup path denied after v11 Veeam update (#80)
Strange, in my case the script is working in my ISE, with PSx64 and CMD, I get the leading =”0”
in PRTG also the XML-Error.
My Protocol in PRTG looks like @cipo80 yours?
Disconnect-VBRServer : Access to the path  "Veeam\Backup" was
denied.
In C:\Program Files (x86)\PRTG Network Monitor\custom
sensors\EXEXML\PRTG-VeeamBRStatsLocalBackupV2.0.ps1:66 Zeichen:5

Disconnect-VBRServer -ErrorAction SilentlyContinue

~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [], UnauthorizedAccessExceptio
n
FullyQualifiedErrorId : System.UnauthorizedAccessException

@.***D71F20.9DA43D40]
Mit freundlichen Grüßen / best regards
i. A. Carsten Trautmann
Senior System Engineer
IT-Service
[http://support.it.konicaminolta.de/signatures/KM_LOGO.jpg]
Konica Minolta Business Solutions Deutschland GmbH
Mittlerer Pfad 1, 70499 Stuttgart, Germany
Phone:
+49 (711) 1385 - 131tel:+497111385131
Fax:
+49 (711) 1385 - 222
Mail:
<EMAIL_ADDRESS>Web:
www.konicaminolta.dehttp://www.konicaminolta.de
District Court / Amtsgericht: Hannover, HRB 61209
Management / Geschäftsführer:
Joerg Hartmann & Kenichiro Fukasawa
Aufsichtsratsvorsitzender: Jens Venrath
Informationen über die Verarbeitung Ihrer personenbezogenen Daten durch uns können Sie unter https://www.konicaminolta.de/de/business-solutions/meta/dseg.html einsehen.
[http://support.it.konicaminolta.de/signatures/emailPrinzip.jpg]
Von: cipo80 @.>
Gesendet: Montag, 22. März 2021 13:11
An: vMarkusK/Advanced-PRTG-Sensors @.>
Cc: Trautmann, Carsten @.>; Mention @.>
Betreff: Re: [vMarkusK/Advanced-PRTG-Sensors] Access to the Veeam\backup path denied after v11 Veeam update (#80)
Hi @carsten0407https://github.com/carsten0407 , in my case both working (psx64 and without it) by PS and both aren't working by PRTG.
Without psx64 is it a XML Custom EXE/Script Sensor standard without parameter, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/vMarkusK/Advanced-PRTG-Sensors/issues/80#issuecomment-804014802, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APIS7JAEMLGDBCL6GAPKJODTE4XWTANCNFSM4ZJ4CGDA.

Carsten Trautmann

Same output by PRTG:
Disconnect-VBRServer : Access to the path 'Veeam\Backup' is denied.
At C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1:77 char:5

Disconnect-VBRServer -ErrorAction SilentlyContinue

~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [], UnauthorizedAccessException
FullyQualifiedErrorId : System.UnauthorizedAccessException

`Disconnect-VBRServer : Access to the path 'Veeam\Backup' is denied.
At C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1:77 char:5

Disconnect-VBRServer -ErrorAction SilentlyContinue

~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [], UnauthorizedAccessException
FullyQualifiedErrorId : System.UnauthorizedAccessException`

Ups, I installed the sensor at a different customer (the old script with a veeam 9.5)
And I see, that the leading “0” is also visible..
I threw that in the case, thought the leading “0” is responsible for the XML error.
That doesn't seem to be the case
The script working perfect, also in PRTG
="srv.dom.local"
0: <-Not the Problem

Successful-Backups
1
1
1

Mit freundlichen Grüßen / best regards
i. A. Carsten Trautmann
Senior System Engineer
IT-Service
[http://support.it.konicaminolta.de/signatures/KM_LOGO.jpg]
Konica Minolta Business Solutions Deutschland GmbH
Mittlerer Pfad 1, 70499 Stuttgart, Germany
Phone:
+49 (711) 1385 - 131tel:+497111385131
Fax:
+49 (711) 1385 - 222
Mail:
<EMAIL_ADDRESS>Web:
www.konicaminolta.dehttp://www.konicaminolta.de
District Court / Amtsgericht: Hannover, HRB 61209
Management / Geschäftsführer:
Joerg Hartmann & Kenichiro Fukasawa
Aufsichtsratsvorsitzender: Jens Venrath
Informationen über die Verarbeitung Ihrer personenbezogenen Daten durch uns können Sie unter https://www.konicaminolta.de/de/business-solutions/meta/dseg.html einsehen.
[http://support.it.konicaminolta.de/signatures/emailPrinzip.jpg]
Von: Trautmann, Carsten
Gesendet: Montag, 22. März 2021 13:43
An: vMarkusK/Advanced-PRTG-Sensors @.>; vMarkusK/Advanced-PRTG-Sensors @.>
Cc: Mention @.***>
Betreff: AW: [vMarkusK/Advanced-PRTG-Sensors] Access to the Veeam\backup path denied after v11 Veeam update (#80)
Strange, in my case the script is working in my ISE, with PSx64 and CMD, I get the leading =”0”
in PRTG also the XML-Error.
My Protocol in PRTG looks like @cipo80 yours?
Disconnect-VBRServer : Access to the path  "Veeam\Backup" was
denied.
In C:\Program Files (x86)\PRTG Network Monitor\custom
sensors\EXEXML\PRTG-VeeamBRStatsLocalBackupV2.0.ps1:66 Zeichen:5

Disconnect-VBRServer -ErrorAction SilentlyContinue

~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [], UnauthorizedAccessExceptio
n
FullyQualifiedErrorId : System.UnauthorizedAccessException

@.***D71F20.9DA43D40]
Mit freundlichen Grüßen / best regards
i. A. Carsten Trautmann
Senior System Engineer
IT-Service
[http://support.it.konicaminolta.de/signatures/KM_LOGO.jpg]
Konica Minolta Business Solutions Deutschland GmbH
Mittlerer Pfad 1, 70499 Stuttgart, Germany
Phone:
+49 (711) 1385 - 131tel:+497111385131
Fax:
+49 (711) 1385 - 222
Mail:
<EMAIL_ADDRESS>Web:
www.konicaminolta.dehttp://www.konicaminolta.de
District Court / Amtsgericht: Hannover, HRB 61209
Management / Geschäftsführer:
Joerg Hartmann & Kenichiro Fukasawa
Aufsichtsratsvorsitzender: Jens Venrath
Informationen über die Verarbeitung Ihrer personenbezogenen Daten durch uns können Sie unter https://www.konicaminolta.de/de/business-solutions/meta/dseg.html einsehen.
[http://support.it.konicaminolta.de/signatures/emailPrinzip.jpg]
Von: cipo80<EMAIL_ADDRESS>Gesendet: Montag, 22. März 2021 13:11
An: vMarkusK/Advanced-PRTG-Sensors<EMAIL_ADDRESS>Cc: Trautmann, Carsten<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [vMarkusK/Advanced-PRTG-Sensors] Access to the Veeam\backup path denied after v11 Veeam update (#80)
Hi @carsten0407https://github.com/carsten0407 , in my case both working (psx64 and without it) by PS and both aren't working by PRTG.
Without psx64 is it a XML Custom EXE/Script Sensor standard without parameter, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/vMarkusK/Advanced-PRTG-Sensors/issues/80#issuecomment-804014802, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APIS7JAEMLGDBCL6GAPKJODTE4XWTANCNFSM4ZJ4CGDA.
Mit freundlichen Grüßen / best regards
i. A. Carsten Trautmann
Senior System Engineer
IT-Service
[http://support.it.konicaminolta.de/signatures/KM_LOGO.jpg]
Konica Minolta Business Solutions Deutschland GmbH
Mittlerer Pfad 1, 70499 Stuttgart, Germany
Phone:
+49 (711) 1385 - 131tel:+497111385131
Fax:
+49 (711) 1385 - 222
Mail:
<EMAIL_ADDRESS>Web:
www.konicaminolta.dehttp://www.konicaminolta.de
District Court / Amtsgericht: Hannover, HRB 61209
Management / Geschäftsführer:
Joerg Hartmann & Kenichiro Fukasawa
Aufsichtsratsvorsitzender: Jens Venrath
Informationen über die Verarbeitung Ihrer personenbezogenen Daten durch uns können Sie unter https://www.konicaminolta.de/de/business-solutions/meta/dseg.html einsehen.
[http://support.it.konicaminolta.de/signatures/emailPrinzip.jpg]
Von: Trautmann, Carsten
Gesendet: Montag, 22. März 2021 13:43
An: vMarkusK/Advanced-PRTG-Sensors @.>; vMarkusK/Advanced-PRTG-Sensors @.>
Cc: Mention @.***>
Betreff: AW: [vMarkusK/Advanced-PRTG-Sensors] Access to the Veeam\backup path denied after v11 Veeam update (#80)
Strange, in my case the script is working in my ISE, with PSx64 and CMD, I get the leading =”0”
in PRTG also the XML-Error.
My Protocol in PRTG looks like @cipo80 yours?
Disconnect-VBRServer : Access to the path  "Veeam\Backup" was
denied.
In C:\Program Files (x86)\PRTG Network Monitor\custom
sensors\EXEXML\PRTG-VeeamBRStatsLocalBackupV2.0.ps1:66 Zeichen:5

Disconnect-VBRServer -ErrorAction SilentlyContinue

~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [], UnauthorizedAccessExceptio
n
FullyQualifiedErrorId : System.UnauthorizedAccessException

@.***D71F20.9DA43D40]
Mit freundlichen Grüßen / best regards
i. A. Carsten Trautmann
Senior System Engineer
IT-Service
[http://support.it.konicaminolta.de/signatures/KM_LOGO.jpg]
Konica Minolta Business Solutions Deutschland GmbH
Mittlerer Pfad 1, 70499 Stuttgart, Germany
Phone:
+49 (711) 1385 - 131tel:+497111385131
Fax:
+49 (711) 1385 - 222
Mail:
<EMAIL_ADDRESS>Web:
www.konicaminolta.dehttp://www.konicaminolta.de
District Court / Amtsgericht: Hannover, HRB 61209
Management / Geschäftsführer:
Joerg Hartmann & Kenichiro Fukasawa
Aufsichtsratsvorsitzender: Jens Venrath
Informationen über die Verarbeitung Ihrer personenbezogenen Daten durch uns können Sie unter https://www.konicaminolta.de/de/business-solutions/meta/dseg.html einsehen.
[http://support.it.konicaminolta.de/signatures/emailPrinzip.jpg]
Von: cipo80 @.>
Gesendet: Montag, 22. März 2021 13:11
An: vMarkusK/Advanced-PRTG-Sensors @.>
Cc: Trautmann, Carsten @.>; Mention @.>
Betreff: Re: [vMarkusK/Advanced-PRTG-Sensors] Access to the Veeam\backup path denied after v11 Veeam update (#80)
Hi @carsten0407https://github.com/carsten0407 , in my case both working (psx64 and without it) by PS and both aren't working by PRTG.
Without psx64 is it a XML Custom EXE/Script Sensor standard without parameter, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/vMarkusK/Advanced-PRTG-Sensors/issues/80#issuecomment-804014802, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APIS7JAEMLGDBCL6GAPKJODTE4XWTANCNFSM4ZJ4CGDA.

Hey,
I've got the same error after the update to v11:
PS C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML> .\PSx64.exe -f="veeam_new.ps1" -p="server.local" -raw
0

XML: Das zurückgelieferte XML entspricht nicht dem erwarteten Schema. (Code: PE233) -- JSON: Das zurückgelieferte JSON entspricht nicht der erwarteten Struktur (Invalid JSON.). (Code: PE231)
I also tried the latest version 2.0.1 of the script and updated PRTG to the latest stable build.

Might you please add a new Sensor to PRTG, similar to the Original one (enable log) but use this Diagnostic Script instead:
https://github.com/vMarkusK/Advanced-PRTG-Sensors/blob/master/Veeam/PRTG-VeeamBRStats-Diag.ps1
Please share the Log (Default Path: C:\ProgramData\Paessler\PRTG Network Monitor\Logs\sensors) returned after the Sensor is executed. Example:
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.-Diag.ps1 : Execution environment
cannot be initialized to Remote
At line:1 char:1
+ &'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\P ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,PRTG-VeeamBRStats.-Diag.ps1

C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.-Diag.ps1 : at <ScriptBlock>,
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.-Diag.ps1: line 48
at <ScriptBlock>, <No file>: line 1
At line:1 char:1
+ &'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\P ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,PRTG-VeeamBRStats.-Diag.ps1

Failed to Connect
<prtg>
 <error>1</error>
 <text>User 'WIN-RT26QHK0M11$' /  Error::  Execution environment cannot be initialized to Remote</text>
</prtg>

Might you please add a new Sensor to PRTG, similar to the Original one (enable log) but use this Diagnostic Script instead:
https://github.com/vMarkusK/Advanced-PRTG-Sensors/blob/master/Veeam/PRTG-VeeamBRStats-Diag.ps1
Please share the Log (Default Path: C:\ProgramData\Paessler\PRTG Network Monitor\Logs\sensors) returned after the Sensor is executed. Example:
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.-Diag.ps1 : Execution environment
cannot be initialized to Remote
At line:1 char:1
+ &'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\P ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,PRTG-VeeamBRStats.-Diag.ps1

C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.-Diag.ps1 : at <ScriptBlock>,
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.-Diag.ps1: line 48
at <ScriptBlock>, <No file>: line 1
At line:1 char:1
+ &'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\P ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,PRTG-VeeamBRStats.-Diag.ps1

Failed to Connect
<prtg>
 <error>1</error>
 <text>User 'WIN-RT26QHK0M11$' /  Error::  Execution environment cannot be initialized to Remote</text>
</prtg>

Here is my log for it
C:\Program Files (x86)\PRTG Network Monitor\custom
sensors\EXEXML\MIFSA-BKP.ps1 : Access to the path 'Veeam\Backup' is denied.
At line:1 char:1

&'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\M ...

  + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorExcep
 tion
  + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
 n,MIFSA-BKP.ps1

C:\Program Files (x86)\PRTG Network Monitor\custom
sensors\EXEXML\MIFSA-BKP.ps1 : at , C:\Program Files (x86)\PRTG
Network Monitor\custom sensors\EXEXML\MIFSA-BKP.ps1: line 48
at , : line 1
At line:1 char:1

&'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\M ...

  + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorExcep
 tion
  + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
 n,MIFSA-BKP.ps1

Failed to Connect

1
User 'SKY-PRTG$' /  Error::  Access to the path 'Veeam\Backup' is denied.

Hey Markus,
thanks for your fast response. Here is the result:
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\veeam_diag.ps1 : Execution environment cannot be
initialized to Remote
In Zeile:1 Zeichen:1
+ &'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\v ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,veeam_diag.ps1

C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\veeam_diag.ps1 : bei <ScriptBlock>, C:\Program Files
(x86)\PRTG Network Monitor\custom sensors\EXEXML\veeam_diag.ps1: Zeile 48
bei <ScriptBlock>, <Keine Datei>: Zeile 1
In Zeile:1 Zeichen:1
+ &'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\v ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,veeam_diag.ps1

0:

And here the Data:
Data['linuxloginpassword'].asString := '***';
Data['notonpod'].asString := '0';
Data['fastcount'].asString := '0';
Data['lastmsg'].asString := '#Y2 Structural error in xml file, 3 open items. @#O231[Invalid JSON.]';
Data['resultfile'].asString := 'Result of Sensor 6351.txt';
Data['windowsloginusername'].asString := 'username';
Data['hostv6'].asString := '';
Data['exefile'].asString := 'PSx64.exe';
Data['lastuptime'].asString := '0';
Data['writeresult'].asString := '1';
Data['blockedsens'].asString := '';
Data['reqmsginterval'].asString := '60';
Data['windowslogindomain'].asString := 'domain.local';
Data['tlsexplicit_imap'].asString := '';
Data['channelnames'].asString := '';
Data['tlsexplicit_default'].asString := '';
Data['canlinux'].asString := '0';
Data['isexesensor'].asString := '1';
Data['windowsloginpassword'].asString := '***';
Data['environment'].asString := '';
Data['mutexname'].asString := '';
Data['channelinfos'].asString := '{}';
Data['uptimecount'].asString := '0';
Data['vmwareparams'].asString := '1';
Data['reboot'].asString := '44279.3297263079';
Data['usednstime'].asString := '0';
Data['newpowershell'].asString := '0';
Data['linuxlogindomain'].asString := '';
Data['tlsexplicit_port'].asString := '';
Data['monitorchange'].asString := '';
Data['inerror'].asString := '1';
Data['sensorid'].asString := '6351';
Data['ipversion'].asString := '0';
Data['tlsexplicit_smtp'].asString := '';
Data['host'].asString := 'hostname.domain.local';
Data['exeparamslist'].asString := '';
Data['usewindowsauthentication'].asString := '0';
Data['simulate'].asString := '0';
Data['tlsexplicit_ftp'].asString := '';
Data['timeout'].asString := '60';
Data['exeparams'].asString := '-f="veeam_diag.ps1" -p="hostname.domain.local"';
Data['momopersistent'].asString := '';
Data['tlsexplicit_pop3'].asString := '';

The root cause of this issue (and also #77 ) seems to be a connection issue to the Veeam Server.

PRTG Uses the Security Context of the Probe Device for the Advanced Sensor
Security Context is by default "Local System" (In @JasperSnail Case "SKY-PRTG$")
This Security Context does not have permissions to the Veeam Server (I am wondering that this was the case in v10)

My Recommendation:

Use a Dedicated Probe for this Sensor
Start the PRTG Probe Service as an account with access to the Veeam Console

Other Options;

Place the Computer Account from the remote probe in the local administrators group of the VBR Server (not recommended / Validated)
Use PS Remote for this sensor

The root cause of this issue (and also #77 ) seems to be a connection issue to the Veeam Server.

PRTG Uses the Security Context of the Probe Device for the Advanced Sensor
Security Context is by default "Local System" (In @JasperSnail Case "SKY-PRTG$")
This Security Context does not have permissions to the Veeam Server (I am wondering that this was the case in v10)

My Recommendation:

Use a Dedicated Probe for this Sensor
Start the PRTG Probe Service as an account with access to the Veeam Console

Other Options;

Place the Computer Account from the remote probe in the local administrators group of the VBR Server (not recommended / Validated)
Use PS Remote for this sensor

Thanks Markus, I will give these a shot

Hey Markus,
thanks for analyzing this and this makes sense. We're discussing the options and try your recommendations.
Thank you!

@efflicto @JasperSnail great, I am looking forward to your feedback.
And just to complete the analysis. The xml error is based on the strange error message of the Veeam PowerShell Cmdlet, which includes a XML syntax.

Hey Markus,
so we sided with the PRTG Remote Probe option. I've installed the probe on the Veeam server and added the sensor to it and it worked fine. The other options, except the PS Remote, weren't an option because of security.
Thank you for your time and help!

My Recommendation:

Start the PRTG Probe Service as an account with access to the Veeam Console
Hello,
i tried that, but without success.

We've a sysaccount, especially for PRTG (sys022). I changed the Probe-Service to run under this account.
Veeam Backup and Replication:

But i get an error:
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1 : Failed to connect to Veeam
BR Host '-BRHost de001ba0003.engrotec.lokal' with user 'sys022'
In Zeile:1 Zeichen:1
+ &'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\P ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,PRTG-VeeamBRStats.ps1

C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1 : bei <ScriptBlock>,
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1: Zeile 317
bei <ScriptBlock>, <Keine Datei>: Zeile 1
In Zeile:1 Zeichen:1
+ &'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\P ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,PRTG-VeeamBRStats.ps1

0:<prtg>  <error>1</error>  <text>Failed to connect to Veeam BR Host '-BRHost de001ba0003.engrotec.lokal' with user 'sys022'</text> </prtg>

Tried the same…..same result
Mit freundlichen Grüßen / best regards
i. A. Carsten Trautmann
Senior System Engineer
IT-Service
[http://support.it.konicaminolta.de/signatures/KM_LOGO.jpg]
Konica Minolta Business Solutions Deutschland GmbH
Mittlerer Pfad 1, 70499 Stuttgart, Germany
Phone:
+49 (711) 1385 - 131tel:+497111385131
Fax:
+49 (711) 1385 - 222
Mail:
<EMAIL_ADDRESS>Web:
www.konicaminolta.dehttp://www.konicaminolta.de
District Court / Amtsgericht: Hannover, HRB 61209
Management / Geschäftsführer:
Joerg Hartmann & Kenichiro Fukasawa
Aufsichtsratsvorsitzender: Jens Venrath
Informationen über die Verarbeitung Ihrer personenbezogenen Daten durch uns können Sie unter https://www.konicaminolta.de/de/business-solutions/meta/dseg.html einsehen.
[http://support.it.konicaminolta.de/signatures/emailPrinzip.jpg]
Von: DerKiLLa @.>
Gesendet: Dienstag, 30. März 2021 12:56
An: vMarkusK/Advanced-PRTG-Sensors @.>
Cc: Trautmann, Carsten @.>; Mention @.>
Betreff: Re: [vMarkusK/Advanced-PRTG-Sensors] Access to the Veeam\backup path denied after v11 Veeam update (#80)
My Recommendation:

Start the PRTG Probe Service as an account with access to the Veeam Console
Hello,
i tried that, but without success.

We've a sysaccount, especially for PRTG (sys022). I changed the Probe-Service to run under this account.
Veeam Backup and Replication:
[image]https://user-images.githubusercontent.com/4670462/112978022-14147780-9157-11eb-9c60-72c8638a86ec.png
But i get an error:
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1 : Failed to connect to Veeam
BR Host '-BRHost de001ba0003.engrotec.lokal' with user 'sys022'
In Zeile:1 Zeichen:1

&'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\P ...

  + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException

  + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,PRTG-VeeamBRStats.ps1

C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1 : bei ,
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1: Zeile 317
bei , : Zeile 1
In Zeile:1 Zeichen:1

&'C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\P ...

  + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException

  + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,PRTG-VeeamBRStats.ps1

0: 1 Failed to connect to Veeam BR Host '-BRHost de001ba0003.engrotec.lokal' with user 'sys022'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/vMarkusK/Advanced-PRTG-Sensors/issues/80#issuecomment-810125587, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APIS7JD3VGMY4CIB6H22X4TTGGU4NANCNFSM4ZJ4CGDA.

Hello,
I just want to update you about the current state of the analysis.
I have tested a few Concepts to reproduce this issue:

Probe on VBR Server (Service as "local System" and "Named User")
Probe on dedicated Server (Service as "Named User")

As I was not able to reproduce this issue I need more details details to dig deeper:

OS of VBR Server
OS of PRTG Probe
Domain Members?
Is the Probe installed on VBR or dedicated Server?
Is probe Server Started as Named user?
Local permission of the Probe Service  user on the Probe?
Local permission of the Probe Service  user on the VBR Server?
VBR Permissions of the Probe Service User?

@efflicto @JasperSnail great, I am looking forward to your feedback.
And just to complete the analysis. The xml error is based on the strange error message of the Veeam PowerShell Cmdlet, which includes a XML syntax.

Hi Markus,
I have set the PRTG Probe service to run as a domain admin service acc, it has access as a Standard user in Veeam BR - now upon trying to run the script I get the following error:
A required privilege is not held by the client. (0x522)
Do you know where I might be missing a permission?

..same testing, same result….
Mit freundlichen Grüßen / best regards
i. A. Carsten Trautmann
Senior System Engineer
IT-Service
[http://support.it.konicaminolta.de/signatures/KM_LOGO.jpg]
Konica Minolta Business Solutions Deutschland GmbH
Mittlerer Pfad 1, 70499 Stuttgart, Germany
Phone:
+49 (711) 1385 - 131tel:+497111385131
Fax:
+49 (711) 1385 - 222
Mail:
<EMAIL_ADDRESS>Web:
www.konicaminolta.dehttp://www.konicaminolta.de
District Court / Amtsgericht: Hannover, HRB 61209
Management / Geschäftsführer:
Joerg Hartmann & Kenichiro Fukasawa
Aufsichtsratsvorsitzender: Jens Venrath
Informationen über die Verarbeitung Ihrer personenbezogenen Daten durch uns können Sie unter https://www.konicaminolta.de/de/business-solutions/meta/dseg.html einsehen.
[http://support.it.konicaminolta.de/signatures/emailPrinzip.jpg]
Von: JasperSnail @.>
Gesendet: Mittwoch, 31. März 2021 03:55
An: vMarkusK/Advanced-PRTG-Sensors @.>
Cc: Trautmann, Carsten @.>; Mention @.>
Betreff: Re: [vMarkusK/Advanced-PRTG-Sensors] Access to the Veeam\backup path denied after v11 Veeam update (#80)
@efflictohttps://github.com/efflicto @JasperSnailhttps://github.com/JasperSnail great, I am looking forward to your feedback.
And just to complete the analysis. The xml error is based on the strange error message of the Veeam PowerShell Cmdlet, which includes a XML syntax.
Hi Markus,
I have set the PRTG Probe service to run as a domain admin service acc, it has access as a Standard user in Veeam BR - now upon trying to run the script I get the following error:
A required privilege is not held by the client. (0x522)
Do you know where I might be missing a permission?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/vMarkusK/Advanced-PRTG-Sensors/issues/80#issuecomment-810697151, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APIS7JHOZHKWLWLTAE7NCLTTGJ6I5ANCNFSM4ZJ4CGDA.

@DerKiLLa Is your User "sys022" member of the local administrators on the VBR Server?

Yes. But this shouldn't make a difference.
OS of VBR Server Windows Server 2012 Datacenter
OS of PRTG Probe Windows Server 2019
Domain Members? Yes, Windows Domain
Is the Probe installed on VBR or dedicated Server? Dedicated Server
Is probe Server Started as Named user? Yes, sys022
Local permission of the Probe Service user on the Probe? Yes, local admin
Local permission of the Probe Service user on the VBR Server? Yes, local admin
VBR Permissions of the Probe Service User? Veeam Backup Administrator

So an update from me.
When testing on the probe with powershell and running the script directly, all results were fine from any way we tested.
But as soon as the Probe sensor was trying to run it, we'd get the above failures.
To workaround this that we found worked was having the Sensor configured to run a separate PS1 file that invokes the PRTG sensor script.
Sensor settings: Psx64.exe
Params: -f="C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\RunVeeamScript.ps1"
Create .PS1 file called RunVeeamScript.ps1 with the following code:
Invoke-Command -ComputerName <VeeamServer> -FilePath "C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\VeeamAdvancedPRTG.ps1"

So an update from me.
When testing on the probe with powershell and running the script directly, all results were fine from any way we tested.
But as soon as the Probe sensor was trying to run it, we'd get the above failures.
To workaround this that we found worked was having the Sensor configured to run a separate PS1 file that invokes the PRTG sensor script.
Sensor settings: Psx64.exe
Params: -f="C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\RunVeeamScript.ps1"
Create .PS1 file called RunVeeamScript.ps1 with the following code:
Invoke-Command -ComputerName <VeeamServer> -FilePath "C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\VeeamAdvancedPRTG.ps1"

Thanks for this workaround! Works like a charm! 👍

So an update from me.
When testing on the probe with powershell and running the script directly, all results were fine from any way we tested.
But as soon as the Probe sensor was trying to run it, we'd get the above failures.
To workaround this that we found worked was having the Sensor configured to run a separate PS1 file that invokes the PRTG sensor script.
Sensor settings: Psx64.exe
Params: -f="C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\RunVeeamScript.ps1"
Create .PS1 file called RunVeeamScript.ps1 with the following code:
Invoke-Command -ComputerName <VeeamServer> -FilePath "C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\VeeamAdvancedPRTG.ps1"

This work around working also in my enviroment.
Thank you 1k Jasper!!

So an update from me.
When testing on the probe with powershell and running the script directly, all results were fine from any way we tested.
But as soon as the Probe sensor was trying to run it, we'd get the above failures.
To workaround this that we found worked was having the Sensor configured to run a separate PS1 file that invokes the PRTG sensor script.
Sensor settings: Psx64.exe
Params: -f="C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\RunVeeamScript.ps1"
Create .PS1 file called RunVeeamScript.ps1 with the following code:
Invoke-Command -ComputerName <VeeamServer> -FilePath "C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\VeeamAdvancedPRTG.ps1"

Works well here too!
Thanks Jasper!!


PhantomJS generate PDF make issue Window 10 Vs Ubuntu 16.04 / CentOS 6.9

I been trying to solve this issue but not sure what's the cause for this.
phantom.create().then(function(ph) {
    ph.createPage().then(function(page) {
        page.property('paperSize', {
            orientation: 'portrait',
            format: 'A3',
        });
        page.property('zoomFactor', 0.5);  // not working for 2.1.1
        page.open('xyz').then(function(status) {
            setTimeout(function(){
                page.render('pdfName.pdf').then(function(response, err) {
                    ph.exit();
                });
            }, 3000)

        });
    });
});

I ran same code in window system and check PDF that looks fine and same run in Ubuntu / CentOS it's not working properly.
I'm using node 8.9.1 & phantomjs 2.1.1 & package.json contain phantom: ^4.0.12.
Please help me out of these

If it works in one OS env but not another then I bet it’s because you are missing dependencies. You need to make sure you have all dependencies installed for phantomjs. Checkout the docker file in example directory.
Sent from my iPad

On Jun 19, 2018, at 7:17 AM, gunjan-bvi<EMAIL_ADDRESS>wrote:
I been trying to solve this issue but not sure what's the cause for this.
phantom.create().then(function(ph) {
ph.createPage().then(function(page) {
page.property('paperSize', {
orientation: 'portrait',
format: 'A3',
});
page.property('zoomFactor', 0.5);  // not working for 2.1.1
page.open('xyz').then(function(status) {
setTimeout(function(){
page.render('pdfName.pdf').then(function(response, err) {
ph.exit();
});
}, 3000)
    });
});

});
I ran same code in window system and check PDF that looks fine and same run in Ubuntu / CentOS it's not working properly.
I'm using node 8.9.1 & phantomjs 2.1.1 & package.json contain phantom: ^4.0.12.
Please help me out of these
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

did this resolve ? I see the same question on Mac


Register

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/20679
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 3ae7356a5d4fd0fc180cbcf5bf8cccaaf19d56ac
git push origin v0.1.0


refactor(operators): move to singular form names

closes #847.
This PR renames paths to singular form,
operators -> operator
subjects -> subject
schedulers -> scheduler
and update import references accordingly.

Lot of work!

Lot of work!

: power of editor :smiley:

Merged with f123887. Thanks @kwonoj!


Add ability to change queue elements

There's currently no way to change a queue elements data value. This would be nice for more complex processes.

It's currently not possible to change the 'data' column of a queue element, but it's possible to update the 'message' column. Since both are just free text values it might be sensible to limit 'data' to read only and then have the 'message' as dynamic data

I like the idea of having both a readonly and a read/write column for passing data.
To me, 'message' sounds more like a logging column, though. I think it's better suited for writing exception messages to or a status message about the queue element.


[Bug] Major - Admin panel/  Menu "Тегления" does not work properly

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to dev.podkrepi.bg
Login as an admin
Select the side Menu "Тегления"
Click on it

Expected behavior
To open a new page with info.
Actual result; 500 Internal server error
Desktop (please complete the following information):

OS: Windows
Browser - Chrome
Version 99.0.4844.74 (Official Build) (64-bit)

Can you please check again, should be ok by now

Hello, ilko.
I think it is OK as per functionality.
As far as it concerns accessibility, UI it is not good enough. Look at the attached pic.
I opened through my phone A22 5G, Android

cleaning up - this is working now


Outdated Power BI Formatting UI

The Format Page icon has changed/moved in a recent Power BI update

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

ID: 4bc4f82a-1cec-444c-8561-c02aa38caa96
Version Independent ID: c05253d9-f12e-b2ee-763f-96e4a76fec54
Content: Adding formatting options to a Power BI custom visual - Power BI
Content Source: powerbi-docs/developer/visuals/custom-visual-develop-tutorial-format-options.md
Service: powerbi
Sub-service: powerbi-custom-visuals
GitHub Login: @mberdugo
Microsoft Alias: monaberdugo

Thanks for your comment, @arkansang. This issue has been assigned to the doc author for review.

Thanks for pointing this out to me, @arkansang. I'll try to update the tutorial when I can.

The screenshots for the tutorial have been updated. Thanks again.

No worries, thanks for updating :)


Updated & Fixed WebAPI

Upgraded to .NET8.0
Fixed logging (removed Console replaced with Ilogger)
Fixed warnings (Null Strings, etc).
The application now returns data from the back-end chat services when called from the Swagger API test framework.

Thanks for this!
@xbotter I think you were working on some WebAPI stuff recently, would you mind reviewing this?

Thanks for the feedback. I've added the default values you suggested.


add SPM support

I'm trying to use this project in a backend swift project, and is missing SPM support. I believe this may be useful for iOS as well.

Hi @vsouza, SPM will be supported on the Swift 3 branch soon, which has quite some change, including the removal of 3rd party testing frameworks. In the mean time please consider using the Just.swift file in your project directly as a temporary workaround. Thanks for your suggesting and PR!


Fixes the CanFocus equal to false from setting HasFocus to true again.

By checking this issue #1611 I found this bug, but not yet the disposing issue.

I know you folks were already way on top of this, but I just realized you'd all responded and I'd forgotten about the thread and never expected such a quick and hearty response!
You're awesome. I'll do a quick test too and +1 that other ticket in the next moments here.

Replicated on e3b62cff38a8ed0a460a26d73951710aea348bbd:

Passes afterwards:
Is there an Assert.DoesNotThrow type thing in your test framework?

https://github.com/migueldeicaza/gui.cs/pull/1623


"The storage is now inconsistent. Restart Prometheus ASAP to initiate recovery." When restarting

What did you do?
Shut down prometheus
What did you expect to see?
Clean shutdown and restart
What did you see instead? Under which circumstances?
Saw the following message: time="2017-03-17T18:29:58Z" level=error msg="The storage is now inconsistent. Restart Prometheus ASAP to initiate recovery." error="error in method hasArchivedMetric(a64b08e58585b0fd): leveldb: closed" source="persistence.go:399"
Environment

System information:
Linux 4.3.3-coreos x86_64
AWS m4.10xlarge

Prometheus version:

prometheus, version 1.5.2 (branch: master, revision: bd1182d29f462c39544f94cc822830e1c64cf55b)
  build user:       root@1a01c5f68840
  build date:       20170210-16:23:28
  go version:       go1.7.5

Logs:

time="2017-03-17T18:27:30Z" level=warning msg="Received SIGTERM, exiting gracefully..." source="main.go:230"
time="2017-03-17T18:27:30Z" level=info msg="See you next time!" source="main.go:237"
time="2017-03-17T18:27:30Z" level=info msg="Stopping target manager..." source="targetmanager.go:75"
time="2017-03-17T18:27:35Z" level=info msg="Stopping rule manager..." source="manager.go:374"
time="2017-03-17T18:27:35Z" level=info msg="Rule manager stopped." source="manager.go:380"
time="2017-03-17T18:27:35Z" level=info msg="Stopping notification handler..." source="notifier.go:369"
time="2017-03-17T18:27:35Z" level=info msg="Stopping local storage..." source="storage.go:396"
time="2017-03-17T18:27:35Z" level=info msg="Stopping maintenance loop..." source="storage.go:398"
time="2017-03-17T18:28:21Z" level=info msg="Done checkpointing in-memory metrics and chunks in 1m48.97614954s." source="persistence.go:639"
time="2017-03-17T18:28:21Z" level=info msg="Maintenance loop stopped." source="storage.go:1259"
time="2017-03-17T18:28:21Z" level=info msg="Stopping series quarantining..." source="storage.go:402"
time="2017-03-17T18:28:21Z" level=info msg="Series quarantining stopped." source="storage.go:1701"
time="2017-03-17T18:28:21Z" level=info msg="Stopping chunk eviction..." source="storage.go:406"
time="2017-03-17T18:28:21Z" level=info msg="Chunk eviction stopped." source="storage.go:1079"
time="2017-03-17T18:28:21Z" level=info msg="Checkpointing in-memory metrics and chunks..." source="persistence.go:612"
time="2017-03-17T18:29:45Z" level=info msg="Done checkpointing in-memory metrics and chunks in 1m24.051053986s." source="persistence.go:639"
time="2017-03-17T18:29:45Z" level=info msg="Checkpointing fingerprint mappings..." source="persistence.go:1480"
time="2017-03-17T18:29:45Z" level=info msg="Done checkpointing fingerprint mappings in 85.264922ms." source="persistence.go:1503"
time="2017-03-17T18:29:58Z" level=error msg="The storage is now inconsistent. Restart Prometheus ASAP to initiate recovery." error="error in method hasArchivedMetric(a64b08e58585b0fd): leveldb: closed" source="persistence.go:399"
time="2017-03-17T18:29:58Z" level=info msg="Local storage stopped." source="storage.go:421"

This looks like a problem in one of the LevelDB indices.
If you restart the server again and go to crash recovery again, those problems might get fixed.
But there are definitely corruptions in leveldb possible that cannot be fixed in that way.
Once https://github.com/prometheus/prometheus/issues/2210 is fixed, you might have even better chances.
There are also tools out there in the internet to repair a leveldb (in cold state).
It might also be more feasible in this case to purge you whole data directory and start from a blank storage.

We just experienced the same scenario.  Running V1.5.0 on Kubernetes/AWS with the database on a EBS volume.  We had received some high CPU alerts caused by Prometheus a little earlier in the day so not sure if Prometheus was already having issues with the database.  During shutdown received the same set of messages and then when restarted it logged the following messages during crash recovery:
time="2017-04-25T22:27:45Z" level=warning msg="Fingerprint ddb8f7da9dc068d0 assumed archived but couldn't be found in archived index." source="crashrecovery.go:388"

I was under a time constraint so couldn't wait for recovery to finish to see if it was going to be repaired. Restarted Prometheus with a fresh database.

Please upgrade to 1.5.2 or 1.6.1 ASAP. That's a known bug in 1.5.0.


Client emails should not be required for TI Flow

Is your feature request related to a problem? Please describe.
Navigators mentioned clients do not typically use email and that this requirement hinders the experience. Navigators mentioned they monitor statuses through their own email and do not always need to include clients’ addresses.
Describe the solution you'd like
Change the requirements of emails and make it optional.
Additional context
Add any other context or screenshots about the feature request here.
Done when
What conditions need to be met before this issue can be closed?

Needs technical review of level of effort for removing email as the identifier in database. @swatkat1 -- let's chat about taking the initial review. And partnering with @nb1701 as needed.

@nb1701 --I don't want to change it directly in the file, but here is my suggestion. @ldinhcos --What do you think?
"Add an email address for your client to receive status updates about their application"
+ " automatically. Without an email, you or your community-based organization will be"
+ " responsible for communicating updates to your client.")
Rationale: TIs don't actually call themselves TIs, rather they are community-based orgs. Include more direct language.

Thanks Nick & Elise.
I saw the original copy and I like Elise's updates in it as it calls out the acronym of CBOs clearly instead of the verbiage of TI's as it may confuse people and also appreciate that it appoints them as responsible for sharing status updates.

From: Elise Kalstad @.>
Sent: Thursday, July 13, 2023 12:43 PM
To: civiform/civiform @.>
Cc: Dinh, Long @.>; Mention @.>
Subject: Re: [civiform/civiform] Client emails should not be required for TI Flow (Issue #4908)
CAUTION: External Email
@nb1701https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31321b84-4544474f5631-e0eae16f8381256a&q=1&e=378757f0-f7b9-4c03-8d10-9d6058ba4206&u=https%3A%2F%2Fgithub.com%2Fnb1701 --I don't want to change it directly in the file, but here is my suggestion. @ldinhcoshttps://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31321b84-4544474f5631-d92c9ad61009452d&q=1&e=378757f0-f7b9-4c03-8d10-9d6058ba4206&u=https%3A%2F%2Fgithub.com%2Fldinhcos --What do you think?
"Add an email address for your client to receive status updates about their application"

" automatically. Without an email, you or your community-based organization will be"
" responsible for communicating updates to your client.")

Rationale: TIs don't actually call themselves TIs, rather they are community-based orgs. Include more direct language.
—
Reply to this email directly, view it on GitHubhttps://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31321b84-4544474f5631-850fb7f2a4732f46&q=1&e=378757f0-f7b9-4c03-8d10-9d6058ba4206&u=https%3A%2F%2Fgithub.com%2Fciviform%2Fciviform%2Fissues%2F4908%23issuecomment-1634810253, or unsubscribehttps://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31321b84-4544474f5631-e6c4914135e6c080&q=1&e=378757f0-f7b9-4c03-8d10-9d6058ba4206&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA6Z5OS6S24E2466HUZEXAP3XQBFVDANCNFSM6AAAAAAYIDQIFI.
You are receiving this because you were mentioned.Message ID: @.***>


Flexible GPU specification in generate.sh

Problem
Current data generation requires GPU ids starting from 0 and consecutive (i.e. cuda device=0..7). Specifying non-consecutive devices is necessary when using public clusters.
Changes

AVAILABLE_GPUS is added in scripts/generate.sh for such usage. For example AVAILABLE_GPUS=(1 3 5 6) means running on device 1, 3, 5 and 6. Note that the array in shell requires space separators.
Change of package versions in setup.py that work for me.

it may be simpler to just specify CUDA_VISIBLE_DEVICES=... outside?

it may be simpler to just specify CUDA_VISIBLE_DEVICES=... outside?

They do have set environment variable for cuda at top: https://github.com/uclaml/SPPO/blob/main/scripts/generate.sh#L4
But during generation they reset it with fixed GPU ids here:
https://github.com/uclaml/SPPO/blob/main/scripts/generate.sh#L51
It's not trivial since there are many generated files named with GPU ids.


Bot Build success but not deployed

The bot code was built successfully but not deployed in server.
Stack logs
2020-10-16T00:54:12.000000+00:00 app[api]: Build started by user<EMAIL_ADDRESS>2020-10-16T00:54:27.598654+00:00 app[api]: Deploy 8723a1a6 by user<EMAIL_ADDRESS>2020-10-16T00:54:27.598654+00:00 app[api]: Release v7 created by user<EMAIL_ADDRESS>2020-10-16T00:54:28.000000+00:00 app[api]: Build succeeded
2020-10-16T00:54:33.995866+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=flutterdocsbot.herokuapp.com request_id=264f1708-2d81-4bf6-a664-c074d6e569cd fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https

Adding Procfile resolved this issue.

Note: Procfile name is case sensitive


Broken link to change log.

On the https://gedcom.io/specs/ page the “change log” link is broken.

Thanks for reporting this. Fixed


docker start container-name command is not allowed to login CLI

Hello,
After we enable our nodes with containerlab deploy command, I wanted to test docker commands.
I made down all containers and then I did " docket start CONTAINERNAME".
Container is becoming up. however,  we are not able to login via CLI. But bash is successfull.
Have you experienced such thing in your environment?
root@ubuntu:~/Arista# docker ps
CONTAINER ID   IMAGE               COMMAND                  CREATED        STATUS              PORTS     NAMES
6aa6409effdd   ceosimage:4.30.5M   "bash -c '/mnt/flash…"   11 hours ago   Up About a minute             CUSTOMER-AristaDCEVPNVXLAN-leaf1
root@ubuntu:~/Arista# docker exec  -it CUSTOMER-AristaDCEVPNVXLAN-leaf1 Cli
Cannot connect to ConfigAgent
                             Entering standalone shell.

This is expected. The cEOS container does not start the Cli process automatically, you have to pass Cli command to it.

Well, as soon as you stop a container, the namespace with all its configuration is being terminated / destroyed.
Part of the namespace configuration is the assigned interfaces. So if you simply start the namespaces again, the wireing is gone and other things might not be properly initialized anymore. Hence you should again use containerlab deploy .... probably with the --reconfigure flag. Then all the interfaces will get recreated and the env should come up as expected.


[Hotfix][Docs] Fix README.md adapt to new module name

Why are the changes needed?

Fix README.md adapt to new module name
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Hi @zhongqishang, there are still some errors in CONTRIBUTING.md document.
https://github.com/apache/amoro/blob/970127ef9050c506b1b147347dee943622afea0c/CONTRIBUTING.md?plain=1#L82


Add Windows Support

Currently we do not support Windows.
Most reasons why Windows does not currently work is related to path differences between UNIX and Windows (/ vs \).

Original issue #144


Saucelabs doesn't pickup job status correctly

Thanks to @DavertMik our tests now post links to their jobs on saucelabs in the travis log. However on saucelabs they are all listed as a status of "?" (complete) instead of pass/fail. Reading the SauceLabs documentation it wasn't clear to me if reporting the test results to saucelabs is something I need to do manually or something codeceptjs is supposed to be doing automatically.

Sorry, I don't know much on this topic. However you are pointing to unit testing documentation on SauceLas which is nothing to do with CodeceptJS and Selenium.

if reporting the test results to saucelabs is something I need to do manually or something codeceptjs is supposed to be doing automatically.

CodeceptJS doesn't do it automatically

@DavertMik Oops. I don't think that was the link I meant to put in. I think this was the link I meant: https://wiki.saucelabs.com/display/DOCS/Setting+Test+Status+to+Pass+or+Fail
Looks like it wont be too difficult for us to implement, so you can close this if you want. Since the last framework we used did it automatically I thought maybe it was intended for CodeceptJS to do it as well, hence the issue.

If anyone else finds this via google or something, this is how I am doing this right now:
  _after() {
    if (process.env.SAUCE_USERNAME) {
      var sessionId = this.helpers['WebDriverIO'].browser.requestHandler.sessionID;
      var sauce_url = "Test finished. Link to job: https://saucelabs.com/jobs/";
      sauce_url = sauce_url.concat(sessionId);
      console.log(sauce_url);

      var dataString = '{"passed": true}';
      var status_url = 'https://saucelabs.com/rest/v1/';
      status_url = status_url.concat(process.env.SAUCE_USERNAME);
      status_url = status_url.concat('/jobs/');
      status_url = status_url.concat(sessionId);

      var options = {
        url: status_url,
        method: 'PUT',
        body: dataString,
        auth: {
          'user': process.env.SAUCE_USERNAME,
          'pass': process.env.SAUCE_ACCESS_KEY
        }
      };

      function callback(error, response, body) {
        if (!error && response.statusCode == 200) {
          console.log(body);
        }
      }

      request(options, callback);
    }
  }

@waryhermit The above code says "passed" even the test case is failed on sauce labs. The job status is updated to "passed" in sauce labs even test is failed. Is there anything I should add apart from above code ?

well if you are still wondering for a workaround on this, I have managed to publish this https://www.npmjs.com/package/codeceptjs-saucehelper
Feel free to use it, updates with the correct status and test names.
@shrikanthkm07 @waryhermit