Adding support for aws-vault sessions in aws section

What has been done

aws-vault creates temporary credentials and correctly unsets AWS_PROFILE to prevent tools from ignoring the environment variables containing the temporary keys. However, aws-vault helpfully provides an AWS_VAULT that contains the name of the profile it used to create the session.
New variable SPACESHIP_AWS_PROFILE used in section gets value of AWS_PROFILE if available, falling back to the value of AWS_VAULT if available.

How to test

Verify the aws section behaves as before with AWS_PROFILE set and unset.
Install aws-vault if necessary and add a profile.
Verify that Spaceship shows the correct profile name after creating a timed session subshell with aws-vault exec -t 1h <PROFILE_NAME>

Close #663

@denysdovhan check my comments, I think it requires some minor changes.
Diff with fixes:
❯ git diff
diff --git i/sections/aws.zsh w/sections/aws.zsh
index cc02c58..43a59c9 100644
--- i/sections/aws.zsh
+++ w/sections/aws.zsh
@@ -25,13 +25,16 @@ spaceship_aws() {
   # Check if the AWS-cli is installed
   spaceship::exists aws || return

+  # Interpolate Native or aws-vualt profile
+  SPACESHIP_AWS_PROFILE="${AWS_PROFILE:-"$AWS_VAULT"}"
+
   # Is the current profile not the default profile
-  [[ -z $AWS_PROFILE ]] || [[ "$AWS_PROFILE" == "default" ]] && return
+  [[ -z $SPACESHIP_AWS_PROFILE ]] || [[ "$SPACESHIP_AWS_PROFILE" == "default" ]] && return

   # Show prompt section
   spaceship::section \
     "$SPACESHIP_AWS_COLOR" \
     "$SPACESHIP_AWS_PREFIX" \
-    "${SPACESHIP_AWS_SYMBOL}$AWS_PROFILE" \
+    "${SPACESHIP_AWS_SYMBOL}$SPACESHIP_AWS_PROFILE" \
     "$SPACESHIP_AWS_SUFFIX"
 }

Close #663

It would great if you guys can review this, @RolfKoenders @segevfiner @cdimitroulas @Mentioum
#671 also addresse same improvement with some suggestions applied.

Good catch on the parameter expansion issue @pecigonzalo @salmanulfarzy. The PR looks good to me as long as those changes are made by @hatless.

Yeah that was the intention, but he seems MIA
On Mon, Jun 3, 2019, 17:50 Christos Dimitroulas<EMAIL_ADDRESS>wrote:

Good catch on the parameter expansion issue @pecigonzalo
https://github.com/pecigonzalo @salmanulfarzy
https://github.com/salmanulfarzy. The PR looks good to me as long as
those changes are made by @hatless https://github.com/hatless.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/denysdovhan/spaceship-prompt/pull/652?email_source=notifications&email_token=ACLS7CPNER5WJ4TIHZQFXYLPYU4VJA5CNFSM4HFR37C2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWZ26OI#issuecomment-498315065,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLS7CPEPJKK2UADO4DH3ADPYU4VJANCNFSM4HFR37CQ
.

Otherwise, I can rebase my code on his code to at least credit him the commits.

Given a couple of years have now gone, maybe @pecigonzalo could rebase and finish this PR, if he has time/willingness?

Im willing

hi folks, anyone knows how this PR stand with https://github.com/spaceship-prompt/spaceship-prompt/pull/671 ?
@denysdovhan  are you still the maintainer  and if so any chance you can chime in pls and clarify if this PR will be the one to work on or the mentioned closed one ?

hi folks, anyone knows how this PR stand with #671 ?
@denysdovhan are you still the maintainer and if so any chance you can chime in pls and clarify if this PR will be the one to work on or the mentioned closed one ?

Released https://github.com/spaceship-prompt/spaceship-prompt/pull/1089
Please use the latest version.


[Bug] Hexagon CI tests fail on tlc-pack/relax HEAD

I ran the Hexagon CI tests on Relax HEAD. I expected all tests to pass since they are not using Relax at all. However, 5 tests failed according to CI summary below:
=========================== short test summary info ============================
FAILED tests/python/contrib/test_hexagon/test_launcher.py::test_aot_executor[c]
FAILED tests/python/contrib/test_hexagon/test_launcher.py::test_aot_executor_multiple_conv2d[c]
FAILED tests/python/contrib/test_hexagon/test_models.py::test_mobilenet - Ass...
FAILED tests/python/contrib/test_hexagon/test_usmp.py::test_conv2d[c-False]
FAILED tests/python/contrib/test_hexagon/test_usmp.py::test_conv2d[c-True] - ...
= 5 failed, 786 passed, 1365 skipped, 15 xfailed, 752 warnings in 15744.57s (4:22:24)

These failures need to be investigated.
Possible reasons for failure could be:

These tests are already failing on TVM main
Some important changes in TVM main might be lost in merge conflicts during last rebase of Relax.
Some changes required for Relax actually break a feature required by Hexagon.

Here is the log file.
CI ran when Relax Head is at 4329af78eb1dc4c4ff8a61d3bf39aa4034e9cb2a

Thanks @psrivas2 for summarizing the Hexagon CI results!
Interestingly, all of these 5 tests are currently skipped in TVM main CI. I believe we can successfully run the test_launcher.py::test_aot_executor test 2 weeks ago with some branches in the relax repo. To locate the issue, we can check if the tests can pass locally with the relax branch and tvm main.


OctopOS Prime Logo Designs-1

Design of 3 animated logos for OctopOS Prime in different styles. When creating the logos, it is important that the tones are in harmony with each other.

3 logos and animations are being worked on for OctopOS Prime.


Add missing Madoko markup for P4 code block in static_assert section

Fixes https://github.com/p4lang/p4-spec/issues/1279


[Corehttp] Update credential classes

Aligning with the credential classes added to azure-core: https://github.com/Azure/azure-sdk-for-python/pull/36565

/check-enforcer override


Add examples to readme

Add examples to readme
Add for the top 5 most used functions an example
Add load, loadS and loadW examples

closed by #72


Rate limit

Hi, I hadn't used this before, but I wonder if these APIs have a small rate limit?

yep, 500/15 mins for most, some are as low as 50/15 mins. Also see: https://developer.twitter.com/en/docs/twitter-api/rate-limits

Would the per app or per user apply in this case?

@mangaroo Good question. The docs I pointed to above were meant to be more of a supplementary resource, just to illustrate the general shape of their newest API. Scraping data mostly relies on the "undocumented" GraphQL API endpoints. Account operations generally use v1 endpoints, and a few account operations + search use the new v2 endpoints.
Overall most scraping/search operations hover around 500 reqs/15 mins, and Account operations range between 10-500 reqs/15 mins.

Thank you again, and for this, best wishes.


Moved AEConicalGradient to /Graphics

Project URL

https://github.com/tadija/AEConicalGradient
Category

/Graphics
Description

Conical (angular) gradient for iOS written in Swift

          1 Warning

:warning:
Found 1 link issue, a project collaborator will take care of these, thanks :)

Link issue by awesome_bot

Line
Status
Link

2877
302
http://www.ios-blog.co.uk/ redirects tohttp://www.ios-blog.co.uk/cgi-sys/suspendedpage.cgi

  Generated by :no_entry_sign: Danger


REACTION_EMOJI not sending recognitions from threads

Attempted to recognize another team member from a thread in Slack using the REACTION_EMOJI and the recognition was not sent to the receiver.
Source of the first mention of this issue can be found pinned in the #gratibot-development channel

@Pactionly mentioned it could be an error in looking up the original message tied to the reaction

This issue appears to be caused by using the Slack API's conversations.history function, which only returns top level messages in a channel. conversations.replies should be used instead, which will also allow messages in threads to be returned.


Web - Line Breaks - Copying & Pasting Line breaks does not work

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Pre- Condition: User has copied a line break previously

Access staging.new.expensify.com
Sign into any valid account
Click on any chat
Attempt to paste the line break in the chat box

Expected Result:
The user expects the line break to show correctly
Actual Result:
The line break does not work and text displays as:
"I'm a text withlinebreaks"
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): any
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
https://user-images.githubusercontent.com/93399543/176269449-b13e5d4b-e963-48dd-bf6c-c17bd8fa0185.mp4
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Unable to reproduce the issue. I tried copying over from Slack and even from a regular text area and the new lines are preserved when pasting into NewDot
Slack:

Regular text area:

NewDot:

Not sure if it's something specific to the comment box on TestRail


Alexey test task, prototype implementation of fortune-client

Based on https://docs.google.com/document/d/1NuuUMBjbzSsOaIBTYXleysrJxJFmMACn9QsrmeE6k4M/edit#


[TextField] Required variant prop

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
The following code failing with error Type 'undefined' is not assignable to type '"outlined"'
const textFieldProps: Partial<TextFieldProps> = { }

<TextField value="" onChange={console.log} {...textFieldProps} />

Expected Behavior 🤔
No errors
Steps to Reproduce 🕹
https://codesandbox.io/s/gallant-hermann-k06ld?file=/src/index.tsx
Context 🔦
This loc should have ?
Your Environment 🌎

Tech
Version

Material-UI
v4.9.11

TypeScript
v3.8.3

etc.

Duplicate of #15697?

Probably, sorry. But what the reason to close it?

No it is not a duplicate. It is about handing it is optional ?

It's a duplicate of #15697. The error message is just misleading. See https://github.com/mui-org/material-ui/issues/15697#issuecomment-493419773 for a more detailed explanation.

It's not about determination union, but about missing ? for according props.
type Props = {
  variant?: "outlined"
} | {
  variant?: "filled"
}

Instead of what you have for now
type Props = {
  variant?: "outlined"
} | {
  variant: "filled"
}


vss2tool tries to create earliest tag from VSS; error: tag already exists

I downloaded, built, and ran vss2git successfully last week. Today I needed to run it again. I cleaned out the Git directory, ran it again, and it complained when it first tried to create the very first tag that the tag already exists.
I just hacked around: got rid of the target git directory completely, got rid of a clone, and rebuilt vss2git in Visual Studio. Now it worked fine. There must have been, somehow, some scraps of data left over someplace, but apparently I got rid of them. Anyway, this is a possible issue.

Thanks for reporting it, but it sounds more like an issue with deleting the git repository than with vss2git. Also, it would need detailed reproduction steps to be actionable. I'm closing this for now, but feel free to reopen if you can demonstrate how to reproduce the issue and vss2git appears to be the cause.

That's fine. This may well be Git's fault. If I have time I might
experiment a bit, but you can close the issue certainly.
On Thu, Jul 19, 2018 at 12:24 PM, Trevor Robinson<EMAIL_ADDRESS>wrote:

Thanks for reporting it, but it sounds more like an issue with deleting
the git repository than with vss2git. Also, it would need detailed
reproduction steps to be actionable. I'm closing this for now, but feel
free to reopen if you can demonstrate how to reproduce the issue and
vss2git appears to be the cause.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/trevorr/vss2git/issues/49#issuecomment-406387159, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AnY2ubLSv9GH_Y8afsj1-bxTM3PvIIgcks5uINz0gaJpZM4VRmkE
.


feat(packages): Use AnyUrl type

I noticed while making search filters for packages that there are several fields that are described as URLs but don't use the pydantic.AnyUrl type. Though, maybe this was intentional.

Pull Request Test Coverage Report for Build 699992699

7 of 7 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 48.99%

Totals

Change from base Build 699928748:
0.0%

Covered Lines:
1406

Relevant Lines:
2870

💛  - Coveralls

Hi @tymokvo, thank you for the PR. Good observation.
For metadata I wanted to keep the fields flexible for users. We can change that if you think that's better.
For recipes and dependencies it was intentional. Unfortunately AnyUrl doesn't support a uri for local files. That means we couldn't use local registries with a filepath. Here is a simple example for you to test.
class Package(BaseModel):
    source: AnyUrl

Package(source='file:///C:/Users/username/.queenbee')

pydantic.error_wrappers.ValidationError: 1 validation error for Package
source
  URL host invalid (type=value_error.url.host)

Got it! That is a slightly tricky caveat. The *nix equivalent of your example does work:
class A(BaseModel):
    u: AnyUrl

print(A(u='file://localhost/home/tyler/.bashrc'))

>>> A(u=AnyUrl('file://localhost/home/tyler/.bashrc', scheme='file', host='localhost', host_type='int_domain', path='/home/tyler/.bashrc'))


Requesting dot format

The program used to generate dot format output previously. Is it still supported?
I tried with ... -format=dot -file=/tmp/callvis, and I saw two files under /tmp:
-rwxr-x--x 1     518  /tmp/callvis.gv*
-rw-rw---- 1     558  /tmp/callvis.dot

But neither can be consumed by dot:
 cat /tmp/callvis.gv | dot -Tpng -o /tmp/out.png
 cat /tmp/callvis.dot | dot -Tpng -o /tmp/out.png

What's the proper way of doing it? Thx!
PS. Related to https://github.com/ofabry/go-callvis/issues/97. As if there is no official way to break up large graphs, I have to hack into .dot file and break it up myself.

The  ... -format=dot -file= doesn't work for me. What is the command that you used?
My goal is to obtain all the nodes and edges in a textual representation as in the dot format.

I cannot recall. If you want help on this, better open a new issue instead.

The ... -format=dot -file= doesn't work for me. What is the command that you used? My goal is to obtain all the nodes and edges in a textual representation as in the dot format.

Hi! Did you manage to get it done yet? I also need that.


raspberry pi docker failing to start TypeError: Cannot read property 'length' of undefined

Ty-connector in the raspberry pi docker image is failing to start and looping with the following in the log file. I have tried blowing away and re-installing with no luck,

<EMAIL_ADDRESS>start /usr/src/app
node ./bin/www

2019-04-28 08:40:02 [info]: WebSocket init
/usr/src/app/service/tuya.js:22
for(var i=0; i<list.length; i++){
^
TypeError: Cannot read property 'length' of undefined
at TuyaService._init (/usr/src/app/service/tuya.js:22:25)
at Timeout.TuyaService.setTimeout [as _onTimeout] (/usr/src/app/service/tuya.js:16:12)
at ontimeout (timers.js:466:11)
at tryOnTimeout (timers.js:304:5)
at Timer.listOnTimeout (timers.js:267:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node ./bin/www
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
pi@magicmirror:~ $ docker version
Client:
Version:      17.09.0-ce
API version:  1.32
Go version:   go1.8.3
Git commit:   afdb6d4
Built:        Tue Sep 26 22:58:36 2017
OS/Arch:      linux/arm
Server:
Version:      17.09.0-ce
API version:  1.32 (minimum version 1.12)
Go version:   go1.8.3
Git commit:   afdb6d4
Built:        Tue Sep 26 22:52:15 2017
OS/Arch:      linux/arm
Experimental: false
pi@magicmirror:~ $ docker  images
REPOSITORY                  TAG                 IMAGE ID            CREATED             SIZE
fison67/ty-connector-rasp   0.0.1               60faa000f1ae        2 months ago        520MB
pi@magicmirror:~ $ docker container ls
CONTAINER ID        IMAGE                             COMMAND                  CREATED             STATUS              PORTS               NAMES
68ac2d39c6ce        fison67/ty-connector-rasp:0.0.1   "/usr/bin/entry.sh..."   19 minutes ago      Up 15 seconds                           ty-connector-rasp

Delete a ty-config.json & Restart a docker container

Its got further after removing the ty-config.json. The container is not looping now but the node startup is. From the container log...

<EMAIL_ADDRESS>start /usr/src/app
node ./bin/www

2019-04-29 02:34:10 [info]: WebSocket init

<EMAIL_ADDRESS>start /usr/src/app
node ./bin/www

2019-04-29 02:34:30 [info]: WebSocket init

<EMAIL_ADDRESS>start /usr/src/app
node ./bin/www

2019-04-29 02:34:51 [info]: WebSocket init

The service starts before config loads, causing a problem..
If you can go in to the docker container
apt-get install nano
nano /usr/src/app/service/tuya.js
find this part
setTimeout(()=>{
this._init();
}, 1000);
Modify to 5000.
This problem is occured

Thanks - that has resolved it for me.


feat: add LabShare Logger as a global module - FCS-161

:tada: This PR is included in version 4.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Separate each class in the docs into its own page

From https://jazz.tools/docs/api-reference/jazz-tools#ID to https://jazz.tools/docs/api-reference/jazz-tools/ID

This doesn't make much sense now considering the lack of documentation. We'd end up with lots of almost-empty pages.


chore: use a custom presubmit_tests.sh script

The Knative test infrastructure runs presubmit tests which are defined in vendor/knative.dev/hack/presubmit-tests.sh. This has been running in test and release infrastructure. It is possible to customize the behavior of this script by defining a handful of functions. The function definitions provided here ensure that we are running tasks that are already being run with the default (e.g. verify-codgen.sh) but make use of our existing build and test targets.
(There also seems to be a stray version of this that I committed a couple of years ago. That has been removed as it is in the wrong location for test-infra and was never used anyway.)
Relates to: https://github.com/knative/func/issues/1333
EDIT: This PR focuses entirely on unit tests. A follow-up PR addressing integration tests will come next.
See: https://github.com/knative/infra/pull/115 (configures prow for func unit tests)
See: https://github.com/knative/infra/pull/104 (reverted, but this includes changes required for integration tests)
/kind chore

Where is presubmit-tests.sh described? I don't see it in client/serving/eventing.

/hold

/retest

/test unit-tests

/unhold

/override "style / suggester / shell"

Not sure why codecov has failed - I have not reduced the total tests. I will look into it, but I think maybe we shouldn't let that hold this up.

Not sure why codecov has failed - I have not reduced the total tests. I will look into it, but I think maybe we shouldn't let that hold this up.

Rebased and force pushed to trigger actions/jobs. We'll see if that changes codecov reporting.

/approve
/lgtm

The code coverage test doesn't seem to behave deterministically, and we appear to add an exception to omit style-checking the vendor directory
/lgtm

/override "style / suggester / shell"


Update README.md

see line 666-671 I have updated the code snippet - is this what you want ?

Attempting to close #198

Requested from Kent as a good issue for a first time contributor to attempt.

Editing the readme.md file.

Checklist:

[X] Documentation
[ ] Tests "N/A"
[ ] Code complete "N/A"
[ ] Added myself to contributors table
[ ] Followed the commit message format

Codecov Report

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

@@          Coverage Diff          @@
##           master   #207   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          10     10
  Lines         142    142
  Branches       36     36
=====================================
  Hits          142    142

Continue to review full report at Codecov.

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


.refine does not work in request params and request query

If we use refine to add complex validation of a zod schema, the output is a ZodEffect, and it does not work with request.query and request.params. It works with body tho.
I've got this schema:
  const user = z
    .object({ name: z.string(), age: z.string() })
    .refine((val) => val.name || val.age, {
      message: "name or age required",
      path: ["name", "age"],
    });

and this path:
      registry.registerPath({
        method: "get",
        path: "/users/{id}",
        summary: "Get a single user",
        request: {
          params: user, // <-- error
          query: user, // <-- error
          body: {
            content: {
              'application/json': {
                schema: user
              }
            }
          }
        },
        responses: {},
      });

The error is:
Type 'ZodEffects<ZodObject<{ age: ZodString; name3: ZodString; }, "strip", ZodTypeAny, { name3: string; age: string; }, { name3: string; age: string; }>, { ...; }, { ...; }>' is not assignable to type 'ZodObject<any, any, any, { [x: string]: any; }, { [x: string]: any; }>'

In the source code, the schema body type is ZodType<unknown> | SchemaObject | ReferenceObject
While params and query are: AnyZodObject which is ZodObject<any, any, any>

Hello again @ootkin!
You are correct. Overall the idea that we've followed is that query, params and headers are not just any type - they are always an object (or even a key-value entries) because of how HTTP specifications are being followed. And in the OpenAPI realm they are described in a different manner than the body. We chose to use the AnyZodObject instead of a regular Record type from typescript mainly for easier usage. The rest of the types (like just a number) are not compatible with the OpenAPI specification.
Now I do imagine your question would be - sure but can you not make it so that ZodEffects with a ZodObject base can be used - to which the answer might be "Yes" and I'll have to check.
In general our main logic here was that on an API docs level the documentation is generated based on "an object of properties" => the documentation part can be rendered as such. And any additional validation can easily be done on another layer of an API as it contains a somewhat business specific logic.
i.e you could always do:
  const user = z.object({ name: z.string(), age: z.string() })

  const organizationUser = user
    .refine((val) => val.name || val.age, {
      message: "name or age required",
      path: ["name", "age"],
    });

and use them accordingly. However I do agree that this might not be optimal so I'd try and look into the possibility of using refine/preprocess on a ZodObject

The generator should just unwrap when detecting a zodeffect

@thelinuxlich  you might be correct - if you've checked the code - please go ahead and open a PR

@ootkin @thelinuxlich this should now be available as part of the v7.0.0 Release :rocket: .Sorry that this took so long


How to use the malib to rollout based on a trained model?

excuse me, when the training is done, where is the model saved, and how to use the model to rollout? Besides, how to replay the training process, can we render the envs like mpe, magent

The repo has been refactored. Thus I closed this issue.


Weird question groups formatting

Current behavior

https://beta.metaculus.com/questions/18274/will-the-gop-win-these-battleground-states/

this looks fixed on dev


Release a src dist

Hi,
it would be cool if you could also upload a source dist with the next release.  This would make re-packaging (e.g., for Conda or Linux distros) a lot easier. :-)

If it helps, happy to do so :)
JFYI, building from source requires Rust on the target machine.
Could you please explain what you mean by repackaging? I'm not familiar the case when wheels aren't enough.

I mean "repackaging" in the sense of "build a binary package in a different format (conda) from source and building it with a defined version of rust in a defined environment".
I was able to build dtparse from source (the source package from the github release page) using setuptools-rust (and rust), so building an sdist should be relatively easy. :)


a2lix_translations in sonata, rich text option?

I've set up TranslationFormBundle with Prezent which works perfect with the locale tabs.
Now there is an issue providing the user with translatable rich text input field.
Is there a way to inject sonata_formatter_type into the fields options of the translation?
Or another way to create rich text translations?
This is the call now:
			->add('translations', 'a2lix_translations',
					array(
						'locales' => array('en', 'nl'),
						'required_locales' => array('en'),
						'label' => false,
						'fields' => array(
							'title' => array(),
							'content' => array(
								'field_type' => 'textarea',
								'label' => 'Description'
							))))

Otherwise I'll have to go for another solution...

For https://github.com/egeloen/IvoryCKEditorBundle/blob/master/Resources/doc/configuration.md by example, something like :
            ->add('translations', 'a2lix_translations',
                    array(
                        'locales' => array('en', 'nl'),
                        'required_locales' => array('en'),
                        'label' => false,
                        'fields' => array(
                            'title' => array(),
                            'content' => array(
                                'field_type' => 'ckeditor'
                                'config_name' => 'my_config',
                                'label' => 'Description'
                            ))))

should be ok.
For sonata_formatter_type, it'll need a custom overwrite of this form type to work I think.

Easy enough!
That's a quick and good solution for now.
Still a lot to learn about Sonata but it is a great framework


Add azure devops var group module

All Submissions:

[YES] Have you followed the guidelines in our Contributing document?
[YES] Have you added an explanation of what your changes do and why you'd like us to include them?
[YES] I have updated the documentation accordingly.
[NO] I have added tests to cover my changes.
[YES] All new and existing tests passed.
[YES] My code follows the code style of this project.
[YES] I ran lint checks locally prior to submission.
[YES] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Add Azure devops variable group module
testing will be added in a separate PR

Does this introduce a breaking change?

[NO]

Any relevant logs, error output, etc?

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Other information

Cc: @nmiodice


[loc][Query][azure-pipelines-tasks /VSOAgent_BuildTask] Localizability of strings

Hi,
please help localization team to answer question from translator.
In case translator is not sure about context/meaning/localizability of string we raise a question to Core team.
Thanks in advance for the reply

Id
File Name Live Page Extended
String Resource ID
Full Source String
Extended Description
Answer Needed By

50,223
GitHubReleaseV0\Strings\resources.resjson\en-US\resources.resjson
0;   "loc.input.help.changeLogType"
Changelog can be commit based or   issue based . Commit based changelog lists all commits included in a release   where as Issue based changelog lists all the issues/pr included in the   release.
pr = problems/pull requests?

50,224
ACRTaskV0\Strings\resources.resjson\en-US\resources.resjson
0;   "loc.messages.TaskRunStatus"
Run   Id: %s is %s
Please,   define placeholders for a better translation.

50,227
DownloadGitHubNugetPackageV1\Strings\resources.resjson\en-US\resources.resjson
0;   "loc.instanceNameFormat"
dotnet restore
According to Resource ID,   'dotnet restore' is an instance name, so we left it in Eng. Please check if   it's OK.

50,228
PublishCodeCoverageResultsV2\Strings\resources.resjson\en-US\resources.resjson
0;   "loc.input.help.summaryFileLocation"
Paths   to summary files containing code coverage statistics, such as line, method,   and class coverage. Multiple summary files will be merged into a single   report. Supports multiple lines of minimatch patterns. More   information
It   seems '[More information]' can be translated, so we translated it.     Please check if it's OK.

50,229
Common\artifacts-common\Strings\resources.resjson\en-US\resources.resjson
0;   "loc.messages.CredProvider_SettingUpForOrgFeeds"
Setting up the credential   provider to use the identity '%s' for feeds in your organization/collection   starting with:
Are the feed starting with   something specific? Or is process starting with specific feeds?

50,253
ACRTaskV0\Strings\resources.resjson\en-US\resources.resjson
0;   "loc.input.label.valuesFilePath"
ValuesFilePath
is   this localizable as Values File Path?

50,254
ACRTaskV0\Strings\resources.resjson\en-US\resources.resjson
0;   "loc.instanceNameFormat"
acrTask
Is this localizable?

50,255
AzureFunctionOnKubernetesV0\Strings\resources.resjson\en-US\resources.resjson
0;   "loc.instanceNameFormat"
Func   on K8s - deploy
Is   this string localizable? For the time being, I have considered it as   localizable and localized as:     Function in Kubernetes - Deploy     Please confirm

50,256
FuncToolsInstallerV0\Strings\resources.resjson\en-US\resources.resjson
0;   "loc.input.help.version"
Specify the version of Azure   func tools to install.   Ex:2.7.1575v2.7.1575latest
Is func tools referred to   Functions Core Tools? See also other occurrences

Hi @PDostalek ,
Adding response for Id 50,223:
pr -> pull requests

[x] Id: 50, 228 - Looks good, https://aka.ms/minimatchexamples

@ds-ms @azooinmyluggage: Can you please help here?

[ ] 50,255 - AzureFunctionOnKubernetesV0 - Yes, it's localisable
[ ] 50,256 - FuncToolsInstallerV0 - Yes, it refers to Functions Core Tools

ACRTaskV0 is not to be released yet, localisation can be held off on this task.

[ ] 50, 224 - ACRTaskV0 - No
[ ] 50, 253 - ACRTaskV0 - No
[ ] 50, 254 - ACRTaskV0 - No

50,229 | Common\artifacts-common\Strings\resources.resjson\en-US\resources.resjson | 0; "loc.messages.CredProvider_SettingUpForOrgFeeds" | Setting up the credential provider to use the identity '%s' for feeds in your organization/collection starting with: | Are the feed starting with something specific? Or is process starting with specific feeds?
There will be a list of prefixes for feed URLs after this line. For example:
"Setting up the credential provider to use the identity 'Project Build Service' for feeds in your organization/collection starting with:
https://organization.pkgs.visualstudio.com/
https://pkgs.dev.azure.com/organization/"
For context, this message will help understand which feed sources are being set up with nuget auth. Let me know if you have any other questions.

Hi @PDostalek
Yes, it is fine to translate '[More information]' in the following context:

50,228
PublishCodeCoverageResultsV2\Strings\resources.resjson\en-US\resources.resjson
0; "loc.input.help.summaryFileLocation"
Paths to summary files containing code coverage statistics, such as line, method, and class coverage. Multiple summary files will be merged into a single report. Supports multiple lines of minimatch patterns. More information
It seems '[More information]' can be translated, so we translated it. Please check if it's OK.

FYI: @ajinkya599

ACRTaskV0 is not to be released yet, localisation can be held off on this task.
* [ ]  50, 224 - ACRTaskV0 - No

* [ ]  50, 253 - ACRTaskV0 - No

* [ ]  50, 254 - ACRTaskV0 - No

Ok, please let me know when new changes will be performed @ajinkya599
still missing reply for 50,227

Ok, please let me know when new changes will be performed @ajinkya599
still missing reply for 50,227

@romil07 to take a look.

@romil07 please check


The process was not automated.

The "get" and "put" statements were not automatically inserted into the PolyCtl.h and PolyCtl.cpp files. I had to do it manually. The IDL file created a Get function but Put was inserted as Set.

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

ID: 29408b51-59df-3afb-b521-7fcdb259803f
Version Independent ID: e32689f9-74c1-3055-79fd-c32728dbf665
Content: Adding a Property to the Control (ATL Tutorial, Part 3)
Content Source: docs/atl/adding-a-property-to-the-control-atl-tutorial-part-3.md
Product: visual-cpp
GitHub Login: @mikeblome
Microsoft Alias: mblome

Investigating

@makelyblakley thanks for the feedback! This has now been fixed.


Add spec-file parfmeter to unit-test gulp task

This allows to run specific tests in file not the whole suite.
It accepts globe patterns as well.

Current coverage is 82.49% (diff: 100%)

Merging #468 into master will increase coverage by 0.66%

@@             master       #468   diff @@
==========================================
  Files            18         18
  Lines          2069       2165    +96
  Methods         371        371
  Messages          0          0
  Branches        181        181
==========================================
+ Hits           1693       1786    +93
- Misses          376        379     +3
  Partials          0          0

Powered by Codecov. Last update 0611aee...4938bc8


Refs #32379 -- Added USE_TZ settings to AdminScriptTestCase.write_settings().

Follow up to 8cd55021bcb6c9727c1adccd9623fa4acfc0312b.
Without USE_TZ in settings.py many test_runner and admin_scripts tests crash on Python built with Py_DEBUG, e.g.
======================================================================
FAIL: test_option_name_and_value_separated (test_runner.tests.CustomTestRunnerOptionsSettingsTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "django/tests/test_runner/tests.py", line 312, in test_option_name_and_value_separated
    self.assertNoOutput(err)
  File "django/tests/admin_scripts/tests.py", line 151, in assertNoOutput
    self.assertEqual(len(stream), 0, "Stream should be empty: actually contains '%s'" % stream)
AssertionError: 266 != 0 : Stream should be empty: actually contains 'django/django/conf/__init__.py:163: RemovedInDjango50Warning: The default value of USE_TZ will change from False to True in Django 5.0. Set USE_TZ to False in your project settings if you want to keep the current default behavior.
  warnings.warn(

Yes busted, I'm checking our test suite with the Python main branch :smile:

@claudep Thanks for checking :+1:


Fixes for passing Request to fetch

Don't create a new request when one is passed to fetch but do apply any default headers

@bryanrsmith Can you review this?

@bryanrsmith ping...

Sorry for the delay.
@timbell I like the change, but it breaks functionality if we don't apply the base URL. We can't do that without copying the Request, which was why that was added. I don't think we can accept the breaking change at this point. Maybe when we reach 2.0?
Was the Request copying causing a problem for you? If so, is there another way to solve it?

Yes, there are the problems with the Request copying - see my comment on issue #1 which led to this pull request.

Right, makes sense. So this case has never worked right, which means we can
make the change without further breaking anyone.
Would you mind just rebasing to clean up those extra commits? Thanks, and
sorry again for neglecting the PR.
On Wed, Mar 9, 2016 at 11:22 PM timbell<EMAIL_ADDRESS>wrote:

Yes, there are the problems with the Request copying - see my comment on
issue #1
https://github.com/aurelia/fetch-client/issues/1#issuecomment-186124700
which led to this pull request.
—
Reply to this email directly or view it on GitHub
https://github.com/aurelia/fetch-client/pull/40#issuecomment-194713064.

Sorry, I've got in a total pickle with git - it's not something I use day to day. What's the easiest way to start again?

@timbelk
Remove the commits, while preserving your work:
git reset --soft master

Commit and push:
git commit

git push

@Gheoan - thanks. Is the pull request usable now? (I notice that the Travis build has failed but it did before too.)

Could I ask the status of this? Do I need to fix stuff in git? If so, I will need instructions I'm afraid.

Right now the status says that the branch has conflicts. You would need to rebase on master. If you can do that, we'll get @bryanrsmith to make one final review. Assuming all tests pass and we have a CLA signature, I can get it in immediately and make a release.

I've done:
git fetch origin
git rebase origin/master
Is that right? What do I do next?

@timbell please follow the instruction in my youtube video here: https://www.youtube.com/watch?v=M7ZYkjOWr6g

Ok, looks like there are no conflicts. I see that the travis-ci is failing. @timbell Can you run the unit tests and also run the linting to make sure everything is passing on your local machine. If not, we need to see if there's something funny going on with travis. Please ping me and let me know.

Unit tests pass:
07 04 2016 15:48:10.601:WARN [karma]: No captured browser, open http://localhost:9876/
07 04 2016 15:48:10.616:INFO [karma]: Karma v0.13.19 server started at http://localhost:9876/
07 04 2016 15:48:10.637:INFO [launcher]: Starting browser Chrome
07 04 2016 15:48:12.050:INFO [Chrome 49.0.2623 (Windows 8.1 0.0.0)]: Connected on socket /#tE9trb1JavToo3h1AAAA with id 64963748
Chrome 49.0.2623 (Windows 8.1 0.0.0): Executed 32 of 32 SUCCESS (0.047 secs / 0.023 secs)
How do I run the linting?

gulp lint

[17:06:00] Using gulpfile ...\fetch-client\gulpfile.js
[17:06:00] Starting 'lint'...
[17:06:02] Finished 'lint' after 1.76 s
So I guess ok?

Yes. So, something else is going on here. I wonder if the tests aren't configured quite right for the CI environment. I'll look into it. Thanks! We'll get this merged shortly.

I think the failures are left over from the core-js removal. We probably just need to add the polyfill library to the karma config. I might have time to take a look in a few hours.

Changes Unknown when pulling 91ea045ea9df5824c0cf18d07dac99c21354d6e3 on timbell:Request-as-input-in-buildRequest into ** on aurelia:master**.


Update doorbird to 1.0.5

Please update my adapter ioBroker.doorbird to version 1.0.5.
This pull request was created by https://www.iobroker.dev c0726ff.

1.0.5 released 5.7.
App 10% user
OK


Default campaign start/end dates on Create page are 1/1/0001

I'll sort this out; shall I go with current date for start plus one month for end?

Sounds good


Create app_it-arb

@albanobattistella Hi!
Thank you very much for the awesome contribution!
Will include this translation in nearest build


consider providing < and >

The \< and \> escape sequences correspond to "left word boundary" and "right word boundary," respectively. They are more specific variants of \b.
There was a request to add them to ripgrep, but in reality, this is more a request for the regex engine itself.
It's not clear whether these are worthwhile things to add, but they are present in other regex engines. There's a secondary question of whether their negation should be support too, although I don't think that's a common thing.
Since unrecognized escape sequences produce a syntax error today, these can be added in a backwards compatible way at any time.

Note that in PCRE2 (as discussed in #1151) \> is generally recognized as an escape (although as @BurntSushi notes, it is an error in the current dialect), which may lead to unexpected results.
PCRE2 does not support \> and \< as word boundaries, which as I understand it are GNU extensions to the original dialect. I'm not able to secure information about which regex engines do support it, but I think the biggest one people are familiar with is through vim (which doesn't support \b, if I'm remembering correctly).
Just some food for thought.

Grep supports them, as well as other gnu tools like sed, and emacs. Vim obviously supports them.
The primary reason why I'd like them implemented isn't that \b doesn't work for most use cases but mostly because I habitually type < instead of \b due to use in vim which doesn't support \b.. I also find it easier to think about wrapping a word in < > mentally verses using the same boundary key for left and right side..
It's not a huge deal as much as it required retraining to use different sequences in different programs. It can be worked around well enough...
I understand that specific word boundaries aren't all that useful because you generally follow up with either a word or non word character on at least one side. So yea they don't necessarily hold their weight in terms of adding useful features... It's more about compatibility with other tools.

I think I'm just going to say no to this feature now. I'm happy to revisit it in the future, but I think I'd want something compelling. It is also worth nothing that even GNU grep supports \b:
$ echo 'foo bar' | egrep '\w\b' -o
o
r

So it kind of seems like vim is the oddball here that doesn't support \b.

I would like to argue for this, because there is a common workflow (for me at least) that this gets in the way:

In vim, you use * to search for a word, it puts \<word\> into your / register (search register)
If you want to then search for it in other files, you just type :grep then press <Ctrl-R> then / and it inserts the contents of the / register.

Given there is a patch (the URL from HN points to https://github.com/hvdijk/regex/commit/511c6485e49c22c79b47a3663a97624348343e6d to make it easier to find, I find HN to be a difficult to read wall of text), is there any reason why we couldn't merge that patch? Could I help?
But also, if you really don't want to add \< and \>, then even just ignoring it as per https://github.com/rust-lang/regex/issues/93 would be nice -- even if you make ignoring escapes an optional behaviour in ripgrep that you pass a flag to, you can tell vim to pass custom flags to the grep program.

@KoviRobi I'm not sure what you mean by ignoring them. Ignoring them would mean that, e.g., \< would match <, which is probably not what you want given the workflow you described?

@KoviRobi I'm not sure what you mean by ignoring them. Ignoring them would mean that, e.g., \< would match <, which is probably not what you want given the workflow you described?

Ah I misunderstood the issue I linked, I thought it ignored the escape characters at all, so \< would be the same as the empty string, not ignored the escape so \< is the same as <.

I'll re-open this for now. We can consider adding this once https://github.com/rust-lang/regex/issues/656 is done.

Excellent, thank you -- let me know if I can be of any help

In addition to \< and \>, I've been noodling on also adding these:

\b{start} as an alias for \<.
\b{end} as an alias for \>.
\b{prev-non-word} for (?<!\w), or equivalently, (?<=\W|^).
\b{next-non-word} for (?!\w), or equivalently, (?=\W|$).

I like \b{start} and \b{end} because I find them less opaque and also leave the door open for \B{start} and \B{end}, although I'd like to avoid adding those for the time being.
The \b{prev-non-word} and \b{next-non-word} are somewhat more specialized. For example, \b{start} only matches at a position where the left side is \W and the right side is \w, but \b{prev-non-word} only matches whenever the left side is \W, even if the right side is also \W. It turns out that this is quite useful for implementing the -w/--word-regexp flag in grep programs, where standard behavior is not to do \b(?:pat)\b, but (?<!\w)(?:pat)(?!\w). Indeed, that's how -w/--word-regexp is implemented in ripgrep when using PCRE2. But in a regex engine without general look-around, implementing it is a tortured affair. Indeed, I've found some latent bugs in the implementation.
I've thought for some time about how to implement something like \b{prev-non-word}/\b{next-non-word} outside of the regex engine and I haven't been able to come up with something that is obviously correct. However, it seems to be that they (along with \b{start} and \b{end}) could slot right in as new look-around assertions in the regex engine. And then there would no longer need to be any work-arounds in ripgrep or any other routine that wants similar semantics.
One downside of this is that adding new look-around assertions will require breaking change releases of both regex-syntax and regex-automata. I was hoping to avoid doing a breaking change release so quickly after the last one, but I'd like to get the -w/--word-regexp stuff cleaned up in ripgrep. And I can bundle in a few other planned breaking changes while I'm at it: #1090, #1088, #1031 and maybe a couple others that slip my mind at the moment.
My plan at this point is to think a bit more about working around this in ripgrep without adding the new word boundary assertions to the regex engine. If I can come up with something that makes me happy, then I might forgo this for now.

I've been thinking about names because I really don't like \b{prev-non-word} and \b{next-non-word}. I'm thinking that I like \b{start-half} and \b{end-half} better. (Although I still don't like them.)

I have this implemented in #1098 and I'm currently planning to include it in the regex 1.10 release. Specifically, this is the new syntax as it will appear in the docs:
\b{start}, \<   a Unicode start-of-word boundary (\W|\A on the left, \w on the right)
\b{end}, \>     a Unicode end-of-word boundary (\w on the left, \W|\z on the right))
\b{start-half}  half of a Unicode start-of-word boundary (\W|\A on the left)
\b{end-half}    half of a Unicode end-of-word boundary (\W|\z on the right)

I have this implemented in #1098 and I'm currently planning to include it in the regex 1.10 release. Specifically, this is the new syntax as it will appear in the docs:
\b{start}, \<   a Unicode start-of-word boundary (\W|\A on the left, \w on the right)
\b{end}, \>     a Unicode end-of-word boundary (\w on the left, \W|\z on the right))
\b{start-half}  half of a Unicode start-of-word boundary (\W|\A on the left)
\b{end-half}    half of a Unicode end-of-word boundary (\W|\z on the right)

I haven't looked through the patch series yet, but this caught my eye.
Does this add the < character to regex-syntax is_meta_character, there is a decently sized comment
here where I will need to test/update some downstream code when this gets included.
https://github.com/softdevteam/grmtools/blob/cf6af64db67fed12c7259902794b98c627daadf1/lrlex/src/lib/parser.rs#L511

Thanks for checking!
No, it doesn't. This change doesn't make < a meta character. That would break things so bad as to be untenable. It's only \< that is interpreted as a word boundary. If you try using \< in regex 1.9, you get an error:
$ regex-cli debug hir '\<'
failed to parse pattern 0 to AST: '\<': failed to parse pattern: regex parse error:
    \<
    ^^
error: unrecognized escape sequence

I guess the problem then is that the code linked above is going to strip the \, off of \< unless it is a meta character i.e. currently we already need to escape < into \< to get it passed to regex as <, so I think to use this word boundary as-is without modifying the linked code above one would have to double escape \, via \\\<.
I would definitely recommend people rather use the \b{...} instead from lex, so thanks for adding those alternatives.
Anyhow I think it's not pretty but at least we can send both < via single-escape, and \< via double escape through the format.
So I think it should all work out.
But yeah, I concur that adding it as a meta-character would seem to be a mistake as it would become impossible to encode <. directly in our format.
So I don't believe there are any major issues or objections on my side of this.

currently we already need to escape < into \< to get it passed to regex as <

Eh? No. The regex < matches < literally.
Is there some existing valid regex pattern whose behavior or interpretation changes as a result of this PR?
Also, where and how are you using this crate? (Out of curiosity.)

Sorry, for not making things explicitly clear, I'm dealing with 2 layers of escaping:
quoting from ^1

Both Lex and grmtools support escaping arbitrary characters, for all other characters
besides those listed above, when given an escaped character \c it will be passed to
the regex engine as the character c.  This is useful when a character is used within
the lex format.
An example of this is when the character < is used at the beginning of a regex. Both Lex
and grmtools interpret this as the beginning of a start condition prefix. Which can be
escaped with \< to ensure it is treated as the start of a regular expression.

There is a simple testcase usage here^2, and an example where we use < before a regex, but not as part of the regex itself.
I use the crates in my lex/yacc lsp implementation, instead of codegen it builds parse tables at runtime and so you can modify grammars and modify/parse input sources at runtime from a traditional lex/yacc specification.

Yes, you shouldn't have to change anything. Nothing in this PR should change the behavior or semantics of any existing valid regex. And since < was never and will never be a meta character on its own, there is no need to escape it for this crate. Whatever escaping you're already doing just necessarily be sufficient after this PR, for if it weren't, it would imply your escaping routine would lead to an invalid regex pattern in the status quo.

Thank you for this, I was going to give it a try by patching Cargo.toml in ripgrep https://github.com/KoviRobi/ripgrep/tree/use-word-boundary-regex but seems like I did something wrong, when I try to test it out I get the following:
ripgrep/$ cargo r -- \<foo\>
    Finished dev [unoptimized + debuginfo] target(s) in 0.03s
     Running `target/debug/rg '\<foo\>'`
regex parse error:
    (?:\<foo\>)
       ^^
error: unrecognized escape sequence

possibly I have just misunderstood something (my understanding is ripgrep uses this engine, but maybe it also has some syntax checking that needs to be patched?)

Note also that ripgrep's -w/--word-regexp flag will be using \b{start-half} and \b{end-half}, not \< and \>. (Although of course \< and \> will still be available for use explicitly.)

@BurntSushi thank you, I have updated https://github.com/KoviRobi/ripgrep/tree/use-word-boundary-regex by updating the regex-automata and regex-syntax, then fixing the remaining errors to my best intuition, it seems to work!

Aye yeah, both regex-syntax and regex-automata have breaking changes (which means they get 0.8.0 and 0.4.0 releases, respectively). Once the releases are out, I'll update ripgrep master pretty quickly and you can drop your patch.

@KoviRobi You should be good to build ripgrep from master now!

@BurntSushi thanks! Also just saw your last commit message about fixing up past commits being an effort, have you come across https://github.com/tummychow/git-absorb ? It makes the fixup workflow extremely simple

Yes, I use it all the time. The issue there wasn't finding the right commit, but the conflicts that I guessed would result from inserting the change in the Cargo.lock file. (I didn't actually try it though, it was just my sense of things at the time.)


Added vibration for notification channels

https://github.com/phonegap/phonegap-plugin-push/pull/2353


Drag & Drop disable

How do I disable passive drag and drop?
And how can I select the time interval I want and run a function?

And last question.
How can i use ajax load data ?

Hi @emrahnalci
To disable the drag&drop you need to set both editable and eventStartEditable to false (the editable is set to false by default).
To load the events data from a URL via AJAX you should use eventSources option. The Event Calendar will send requests to the specified URL whenever it needs new event data. The request will include the start and end parameters (ISO8601 date strings) which specify the date-range that the calendar needs events for. The expected response format is JSON with the events data.


hchiorean - Initial version

Impl class: dev.morling.onebrc.CalculateAverage_hchiorean
JDK version:  openjdk 21.0.1 2023-10-17
Tested on: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz   2.80 GHz, 16GB RAM
Est. run time: 59s

Hey @hchiorean, howdy? Long time, no see :)
Can you please

make the launche script executable
run ./test.sh hchiorean and fix the failure(s); in particular, there may be no superfluous content on stdout, like that "using decoder..." part
make sure the output of the progam is the same as that one of the base line script

Thx!

@gunnarmorling howdy
This was fun, you should consider making it a regular thing like AOC

00:59.377. Thx for participating!

this was fun, you should consider making it a regular thing like AOC

Hehe, not sure whether I'll have the energy to do this again that quickly ;) But yeah, perhaps :)


Update tenant domain for analytics

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

Project coverage is 37.29%. Comparing base (2ed9c16) to head (08fa8f9).

Additional details and impacted files
@@            Coverage Diff            @@
##           main    #2280       +/-   ##
=========================================
+ Coverage      0   37.29%   +37.29%
=========================================
  Files         0       15       +15
  Lines         0     1263     +1263
  Branches      0      246      +246
=========================================
+ Hits          0      471      +471
- Misses        0      792      +792

Flag
Coverage Δ

common-controller
4.07% <ø> (?)

idp-domain-service
80.21% <ø> (?)

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

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


Default nbsite proposal

nbsite can handle a variety of different site configurations, but I'd like to propose a default for most PyViz sites to use .  I'll use datashader as an example, which currently looks like:

...

The layout currently looks jumbled and haphazard to me, and I'd like to address that. In particular:

The little logo in the top left looks a bit odd when there is a big logo, but I think the big logo is important for branding.
The little logo isn't using the wordmark, which again looks odd next to the big one.
The sidebar is mostly empty
The Twitter feed looks crammed in
There's a lot of space taken at the bottom by the page footer
There are at least three ways to navigate, all of which look like they are different things (top bar, side bar, page footer).  Two or three places to do the same thing is convenient; three different-seeming ways to do the same thing is confusing.

Here's one possible mockup addressing most of the points above, but I'm still thinking about it:

Note that the above approach is for a site where the sidebar is always visible; it would need a different approach if it weren't.
Also note that the top bar should presumably stay visible on scrolling, as in http://numba.pydata.org/numba-doc/0.38.0/index.html ...

I agree datashader.org is a bit of a mess, especially with that huge logo.
My reference here is holoviews.org...

and bokeh.org...

which I think look fine.

Philipp pointed out that the holoplot site looks fine with the logo (and I agree):


Add challenges

Added new view. Added live tab to maintain simetry. Added map in mobile menu

Bloomberg descrittions is wrong. Should be: "to best hack"


Create config file

this gonna impact the whole project

I think most system configuration should go to .env, but there will be some config variables that we need?? such as allowable password field length which we need to apply on html input's maxlength attribute and server side API's validation function.


Checking EOF of stdio PIPE is broken running Windows executable with WSL2

First, I placed all files to explain this issue at https://github.com/LumaKernel/issue-WSL2-pipe .
a.c is small program enough to reproduce this issue. ( Simple program to read lines and print unless it finds EOF. )
a.exe is compiled with gcc.exe a.c.
a.linux.out is compiled with gcc a.c.
I found the same issue with Go and Rust programs (including clip.exe ( one shipped from Microsoft ;) ), win32yank, my small Go program and powershell.exe (see below) ).
This issue doesn't happen with Linux Programs.
Environment
$ # All below commands are run with bash.
$ # using WSL2
$ echo $SHELL
/bin/bash
$ uname -a
Linux MyComputer 4.19.104-microsoft-standard #1 SMP Wed Feb 19 06:37:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/version
Linux version 4.19.104-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Wed Feb 19 06:37:35 UTC 2020
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
$ which gcc.exe  # This is shipped from `scoop install gcc` ( actually mingw-w64's one )
/mnt/c/Users/luma/scoop/apps/gcc/current/bin/gcc.exe
$ which gcc
/home/linuxbrew/.linuxbrew/bin/gcc

winver.exe is saying...

ver and wsl -l -v in cmd is saying...
C:\Users\luma>ver

Microsoft Windows [Version 10.0.20180.1000]

C:\Users\luma>wsl -l -v
  NAME                   STATE           VERSION
* Ubuntu                 Running         2
  docker-desktop         Running         2
  Ubuntu-18.04           Stopped         1
  docker-desktop-data    Running         2
  Alpine                 Running         2

And I tested with Windows Terminal.
Steps to reproduce
The piping is broken if checking EOF in program.
Windows executable program will wait user input.
$ ./a.exe < sample.txt  # works well with file input
61 0a    |a.|
62 0a    |b.|
FOUND EOF!!
$ echo a | ./a.exe  # not working well
61 0a    |a.|
^C$
$ # After at least 3 seconds, but not reaching EOF
$ # and I hit CTRL-C to stop a program.
$ # same
$ cat sample.txt | ./a.exe
61 0a    |a.|
62 0a    |b.|
^C$

Below is using linux native executable ( and this is the expected behavior. )
$ ./a.linux.out < sample.txt
61 0a    |a.|
62 0a    |b.|
FOUND EOF!!
$ cat sample.txt | ./a.linux.out
61 0a    |a.|
62 0a    |b.|
FOUND EOF!!

This may have happened after installing update of WSL2 Linux Kernel from here. It was working well before installing this.
Q. Works with single line read ?
A. Yes.
$ echo -ne "a\x0a" | powershell.exe -c "Read-Host"
a
a

$

Q. Works good with CRLF ?
A. No.
$ echo -en "a\x0d\x0ab\x0d\x0a\x0d\x0a" | ./a.exe
61 0a    |a.|
62 0a    |b.|
0a     |.|
^C$

Expected behavior
Windows executable exits having found EOF.
Actual behavior
Windows executable program will stop working without exiting.

/dupe #5648  did not make 20180.


Speeding up display of diff for large flows

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Proposed changes
Speed up the display of the diff panel in the editor UI for large flows.
Currently the diff of a flow of 2500 nodes takes 3mins, 3300 nodes 5 mins...etc
This is because the DOM for the whole diff (all nodes, all properties of all nodes) is generated when the diff panel is opened.
By generating the DOM for node properties only if the user clicks on the node, the size of the flow has much less impact on the loading time of the panel.
This brings the appearance of the diff table down to a few seconds even for large flows.
Checklist

[x] I have read the contribution guidelines
[x] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage decreased (-0.04%) to 76.493% when pulling 6b3b68a4e5d7ad587b242231dd02281a02d9fc49 on TothiViseo:diffNodePropertiesOnClick into 8167608f047308a15ac7e42079d47fb968dfa2e1 on node-red:dev.


Medication Extractor added

Support for the CancerRelatedMedication resource has been added. As a reminder, this should be tested against the corresponding PR on the mcode-extraction-framework repo. Happy testing!

Likely needs a rebase after DM's changes; will provide a thorough Monday AM

Do we want an update to an example config indicating the extractor details needed? @Dtphelan1 any thoughts on this? I don't know if we have an mCODE example config yet so maybe we don't need this.


Minikube Cluster Setup

Fixes #496
Minikube Cluster Setup Documentation

Please do have a look @daemon1024

Will make a new pr for #492

Required change has been done please do have a look @daemon1024

Any updates @daemon1024

Required changes have been done @daemon1024

It doesn't seem to be formatted right sweat_smile Can you look into it please? Thanks a lot for the efforts.

My bad, let me check

@Akshit42-hue @daemon1024
wondering why we have the drop-down text for minikube?
the text is the same as contribution/minikube/README.md.
Is there any reason to have the text instead of a link like the others?

It's part of the Documentation revamp to elimate external linking and collect and organize the documentation to less number of files leveraging the drop down texts #477
@nam-jaehyun Other points are in process of being changed too, like #698 and others being linked in the parent issues.

It's good to have all the information on a single page rather than going for the external link and I think dropdown is the best way


Pl/constant specs as ps

Trying Catalyst#constant-specs-as-ps.
cc @isaacsas

Sounds good. I’ll try to fix up the API stuff and then make a new breaking release. Should be tomorrow evening at the latest if that works.

@anandijain , this PR treats constant species as parameters. It assigns them the new isconstantspecies=true metadata in Catalyst v12 (IIUC this allows them to participate as reactants/products and enable correct interpretation of mass action kinetics). Could you please review?

lgtm


WebGL2 bad performance only in Firefox

Expected Behavior
If I understand correctly, a webgl2 canvas is hardware accelerated, as opposed to 2d canvas. I expect two browsers that both run in webgl2 mode to perform about the same.
Current Behavior
Pixijs is very performant in Chrome. It is however very slow in Firefox.
Steps to Reproduce
Open https://pixijs.io/pixi-filters/tools/demo/ in Chrome, full screen, High-res (retina). Very performant. Now do the same in Firefox. Less than 10 FPS (unless your computer is very fast I guess).
Environment

pixi.js version: PixiJS 5.0.3 - ✰ WebGL 2
Browser & Version: Firefox Quantum 67 x64, Chrome 76.0.3806.1 64-bit
OS & Version: Linux Mint 19.1 AKA Ubuntu 18.04.1
Running Example: _https://pixijs.io/pixi-filters/tools/demo/_

OK, I'll try to reproduce!

Linux Mint 19.1 AKA Ubuntu 18.04.1

Oh noes, i will have to install OS!
Its also depends on linux drivers, beware! Which ones do i have to install?

Oh noes, i will have to install OS!

Perhaps you can observe the same difference using the bootable Live image. I believe it's running the open source Nouveau driver.
Either way, I'm running Nvidia proprietary driver 396.54 from the "Driver Manager". You can't install drivers on the Live image, because you have to reboot.

OK got it. Though you will have to wait before I confirm it. My queue for that kind of tasks is loooong.

Update
I see the same problem using non-pixijs graphics, e.g. https://webglsamples.org/aquarium/aquarium.html
Hence, this is not directly pixijs related.
However, contrary to what my mother says, I am not unique. So this will probably affect a (small) fraction of pixijs users. It might be in everyones interest to find out if a specific method or call causes this and can be circumvented.
Not sure if I should close this issue or leave open until upstream cause and pixijs workaround is found.

We can report it to bugzilla and then close this issue.

I have amended an existing issue in Bugzilla here: Mozilla Bugzilla #1246410 comment 39. I am not sure this has the same cause.
Either way, note that when searching through the bug tracker, you can find similar reports dating back 7 years. Every next release had a wontfix label. They probably have their reasons (or not, could be lack of interest in webgl), but it looks a bit like webgl in Firefox is like Duke Nukem Forever: It's done when it's done.
People are slowly moving from Chrome to Firefox, so more people will be affected by this. So we can either wait for upstream fixes (Duke Nukem Forever took 15 years), or see if a local workaround is possible in PixiJS.
Possible workaround in PixiJS
If I understand correctly, texImage2D is to blame. A function used by PixiJS for everything texture related. I read in https://www.khronos.org/registry/webgl/specs/latest/2.0/ that texStorage2D is more performant:

texStorage2D should be considered a preferred alternative to texImage2D. It may have lower memory costs than texImage2D in some implementations.

If OpenGL ES is related to WebGL, this might also be interesting:
http://www.voidcn.com/article/p-qijrpsze-bcq.html
I don't know enough about this to say something more meaningful.

interesting. We have workaround through texSubImage2D : https://github.com/pixijs/pixi.js/blob/dev/packages/core/src/textures/resources/BaseImageResource.js#L69
We didnt use texStorage2D yet.
As for bugzilla, I'm afraid that its very slow compared to chromium. Im waiting for more than a year on 2 issues.

Can you tell me what would effectively cause the if right above that to be false?

Also gameofbombs (wow pretty addictive) is laggy in Firefox/Linux. Smooth on Chrome.

We can report it to bugzilla and then close this issue.

I will close this issue. Firefox is lacking in Linux. I better detect Firefox + Linux and tell visitors that this browser is not supported.


feat: update thank you for your submission screen

This PR resolves ONYX-959
Description
This PR updates the Thank you for your submission screen to match the new designs

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

update thank you screen in new submission flow - mounir

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (update thank you screen in new submission flow - mounir)

  Generated by :no_entry_sign: dangerJS against 1b490ae571018d4dbddbd912f359683f8f25e728


PodSecurityPolicy was deprecated in Kubernetes v1.21, and removed fro…

Signed-off-by: yanggang<EMAIL_ADDRESS>/kind cleanup
PodSecurityPolicy was deprecated in Kubernetes v1.21, and removed from Kubernetes in v1.25.

Sorry for the delay on this - docs have moved to github.com/tigera/docs, so we'll need to re-open this there.
CC @ctauchen


V3.0.0 KeyError: 'currency'

Error: GET (400) https://api.binance.com/api/v3/account - Timestamp for this request is outside of the recvWindow.
KeyError('currency')
Traceback (most recent call last):
File "pandas/_libs/hashtable_class_helper.pxi", line 1683, in pandas._libs.hashtable.PyObjectHashTable.get_item
KeyError: 'currency'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/pi/.local/lib/python3.7/site-packages/pandas/core/indexes/base.py", line 2897, in get_loc
raise KeyError(key) from err
KeyError: 'currency'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "pandas/_libs/hashtable_class_helper.pxi", line 1683, in pandas._libs.hashtable.PyObjectHashTable.get_item
KeyError: 'currency'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/pi/.local/lib/python3.7/site-packages/pandas/core/indexes/base.py", line 2897, in get_loc
raise KeyError(key) from err
KeyError: 'currency'

Updated to latest Pandas available to RPi and installed requirements.

Same error occurs on version 3.1.1 as well.

also in latest 3.2.2
Auto restarting bot for BTCBUSD after exception: KeyError('currency')

Still the same issue here on latest and now with this traceback:
ConnectionError: https://api.binance.com
Exception('Data range too small.')
Traceback (most recent call last):
File "pandas/_libs/hashtable_class_helper.pxi", line 1683, in pandas._libs.hashtable.PyObjectHashTable.get_item
KeyError: 'currency'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/pi/.local/lib/python3.7/site-packages/pandas/core/indexes/base.py", line 2897, in get_loc
raise KeyError(key) from err
KeyError: 'currency'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/pi/DOGE/pycryptobot/models/Trading.py", line 1052, in addSMA
raise Exception("Data range too small.")
Exception: Data range too small.

could try to catch those exceptions, so the bot is not interrupted, right?

Hey @Olney1, @jegb and @sansal54. Is this still happening?

not any more, there are binance api issues in my opinion.

Ok, Thanks. I'll close this issue then.


Not ending loop possible with RetryingGetBlockFromPeersTask

Description
In the GetBlockFromPeerTask in executeTask the result is completed exceptionally with an IncompleteResultsException if the response from the peer was empty.
This is caught in AbstractRetryingPeerTask in the executeTask() method, which calls the handleError() method on RetryingGetBlockFromPeersTask, which calls the handleError() method on AbstractRetryingSwitchingPeerTask, which in turn calls the handleError() task on AbstractRetryingPeerTask.
In the handleError() task we are calling the isRetryableError() method on RetryingGetBlockFromPeersTask, which returns true   @Override   protected boolean isRetryableError(final Throwable error) {     return super.isRetryableError(error) || error instanceof IncompleteResultsException;   }
and then we call the executeTask on GetBlockFromPeerTask, which will use the same peer (if one was assigned) to try the same request again.
If a peer does not have the block we are asking for it will response with an empty response.
Eventually all peers will be disconnected because we are reporting a useless response every time.

@fab-10 Could you have a look at this issue please. I think you made the empty response retryable to fix an issue.

Looking at the code the not ending loop should not happen, because there is an upper bound to the number of retries that are allowed, that is usually the number of peers, after which MaxRetriesReachedException is returned, and the assigned peer is only used on the first try, following tries will use another peer.
Will create a unit test to confirm what I see from the code.

test added to verify this does not happen in practice


YETUS-1170. some plugins are missing delete_parameters calls

So... using these plugins breaks the precomit parsing for subsequent plugins?

precommit will error saying the flags are invalid because they are still on the stack "unparsed."

Maybe we need a test that uses everything?

I've been thinking more and more about building another repo that is nothing but test code to check failures.  Our current setup really allows for positives.
Thanks for the review!


Supporting same kind of events across providers:

this updates providers to process same kind of events

pull request (open, updated, reopened)
push,
comment (only when created) : /retest, /ok-to-test

Signed-off-by: Shivam Mukhade<EMAIL_ADDRESS>
Changes

Submitter Checklist

[x] ♽  Run make test lint before submitting a PR (ie: via pre-push github hook no need to waste CPU cycle on CI
[x] 📖 If you are adding a user facing feature or make a change of the behavior, please make sure to document it
[x] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[x] 🎁 If that's something that is possible to do please make sure to check if we can add a e2e test.
[x] 🔎 If there is a flakiness in the CI tests then make sure to get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it.

See the developer guide for a bit more details.

@chmouel what do you think about this?

can you explain me a bit more what it does, I am not sure I understand from your description 😅

can you explain me a bit more what it does, I am not sure I understand from your description sweat_smile

previously for bitbucket server we were processing pr:comment:edited which means if any comment is edited and changes to /retest it would run the CI but not for other providers
so this updates all providers to process same kind of events.
so now pac will process /restest comment it the comment is created first time but won't if any comment is edited to /retest
similarly other events.

/retest
ah gotcha, yeah that better, I think it should be only new comment and not edited one to parse.

/retest

unittest error is legit :
=== RUN   TestProvider_Detect/push_event
=== RUN   TestProvider_Detect/pull_request_event
    github_test.go:718: assertion failed: true (tt.processReq bool) != false (processReq bool)
--- FAIL: TestProvider_Detect (0.05s)
    --- PASS: TestProvider_Detect/not_a_github_Event (0.00s)
    --- PASS: TestProvider_Detect/invalid_github_Event (0.00s)
    --- PASS: TestProvider_Detect/valid_check_run_Event (0.00s)
    --- PASS: TestProvider_Detect/unsupported_Event (0.00s)
    --- PASS: TestProvider_Detect/invalid_check_run_Event (0.00s)
    --- PASS: TestProvider_Detect/invalid_issue_comment_Event (0.00s)
    --- PASS: TestProvider_Detect/issue_comment_Event_with_no_valid_comment (0.00s)
    --- PASS: TestProvider_Detect/issue_comment_Event_with_ok-to-test_comment (0.00s)
    --- PASS: TestProvider_Detect/issue_comment_Event_with_ok-to-test_and_some_string (0.00s)
    --- PASS: TestProvider_Detect/issue_comment_Event_with_retest (0.00s)
    --- PASS: TestProvider_Detect/issue_comment_Event_with_retest_with_some_string (0.01s)
    --- PASS: TestProvider_Detect/push_event (0.00s)
    --- FAIL: TestProvider_Detect/pull_request_event (0.04s)

unittest error is legit :
=== RUN   TestProvider_Detect/push_event
=== RUN   TestProvider_Detect/pull_request_event
    github_test.go:718: assertion failed: true (tt.processReq bool) != false (processReq bool)
--- FAIL: TestProvider_Detect (0.05s)
    --- PASS: TestProvider_Detect/not_a_github_Event (0.00s)
    --- PASS: TestProvider_Detect/invalid_github_Event (0.00s)
    --- PASS: TestProvider_Detect/valid_check_run_Event (0.00s)
    --- PASS: TestProvider_Detect/unsupported_Event (0.00s)
    --- PASS: TestProvider_Detect/invalid_check_run_Event (0.00s)
    --- PASS: TestProvider_Detect/invalid_issue_comment_Event (0.00s)
    --- PASS: TestProvider_Detect/issue_comment_Event_with_no_valid_comment (0.00s)
    --- PASS: TestProvider_Detect/issue_comment_Event_with_ok-to-test_comment (0.00s)
    --- PASS: TestProvider_Detect/issue_comment_Event_with_ok-to-test_and_some_string (0.00s)
    --- PASS: TestProvider_Detect/issue_comment_Event_with_retest (0.00s)
    --- PASS: TestProvider_Detect/issue_comment_Event_with_retest_with_some_string (0.01s)
    --- PASS: TestProvider_Detect/push_event (0.00s)
    --- FAIL: TestProvider_Detect/pull_request_event (0.04s)

strange 🤔  why didn't the git hook catched it!

Codecov Report

Merging #509 (769ba57) into main (7a98584) will increase coverage by 0.01%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##             main     #509      +/-   ##
==========================================
+ Coverage   73.04%   73.06%   +0.01%
==========================================
  Files          55       55
  Lines        3161     3174      +13
==========================================
+ Hits         2309     2319      +10
- Misses        642      644       +2
- Partials      210      211       +1

Impacted Files
Coverage Δ

pkg/provider/gitlab/gitlab.go
91.17% <66.66%> (-0.41%)
:arrow_down:

pkg/provider/bitbucketserver/bitbucketserver.go
84.93% <100.00%> (ø)

pkg/provider/github/github.go
87.59% <100.00%> (ø)

pkg/matcher/annotation_tasks_install.go
84.12% <0.00%> (-1.84%)
:arrow_down:

pkg/acl/acl.go
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


[Improvement][dashboard] Modify startup scripts that support JDK9 or later.

What changes were proposed in this pull request?
The script startup parameters are outdated when the dashboard is booted with an advanced JDK version.
The issues are as follows：
[0.001s][warning][gc] -XX:+PrintGC is deprecated. Will use -Xlog:gc instead.
[0.001s][warning][gc] -XX:+PrintGCDetails is deprecated. Will use -Xlog:gc* instead.
-XX:ConcGCThreads=5 -XX:G1ConcRefinementThreads=20 -XX:GCDrainStackTargetSize=64 -XX:+IgnoreUnrecognizedVMOptions -XX:InitialHeapSize=42949672960 -XX:InitiatingHeapOccupancyPercent=45 -XX:MaxGCPauseMillis=200 -XX:MaxHeapSize=42949672960 -XX:ParallelGCThreads=20 -XX:+PrintCommandLineFlags -XX:+PrintGC -XX:+PrintGCDetails -XX:ReservedCodeCacheSize=251658240 -XX:+SegmentedCodeCache -XX:+UseG1GC
Why are the changes needed?
Fix: #1401
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing UT.

@rickyma PATL.

Wait one day for others to take a look.

Merged to master. Thanks @yl09099 @jerqi


Backend

Set Url and Open Chat link in models
Implement views and urls.py
Implement simple search
Use unions to process querysets

Cool!


Subscribe to others works for PPU and guest users

Hey everyone,
as per the section: https://learn.microsoft.com/en-us/power-bi/collaborate-share/end-user-subscribe?tabs=creator#subscribe-external-users
as per my knowledge (and testing) a report on a PPU capacity can be subscribed to others, even guest users, as long as the other users have at least a Power BI Pro license assigned. It does not work for users with a PBI Free license only. Could this be adjusted?

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

ID: 2caf5705-b9c8-3818-4524-3c4bf9b112a2
Version Independent ID: 98ede3b9-f4f6-88a6-83fc-6afab863bf4a
Content: Email subscriptions for reports and dashboards in the Power BI service - Power BI
Content Source: powerbi-docs/collaborate-share/end-user-subscribe.md
Service: powerbi
Sub-service: pbi-explore
GitHub Login: @mihart
Microsoft Alias: mihart

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

Thanks for your comment, @gmuenster . This looks like a support request or product question rather than documentation feedback. You might find a solution in the Power BI Community, at https://community.powerbi.com. You may also be able to contact Support (refer to this article: https://docs.microsoft.com/en-us/power-bi/admin/service-support-options to review available Support options.)


Post idea : The smell of change management

The smell of change management

Code smell: In software development, any symptom of a greater sin within the product.

Ladies and gentlemen, members of the board and shareholders, I am glad to welcome you to this year's leaders meeting.
For those of you who do not know me, the name is Thomas Doe, co-creator of Pentathlon and head of the IT department.
I hope that everyone made a fine trip and that you all enjoyed the petits fours. It is now time to kick-start this meeting with the less enjoyable news. Yes, I am talking about the migration to our new set of applications.

 That all of our collaborators will finally be able to stop using our legacy catch-all solution.
Not only did we miss the milestone, but we also have seen our expenses exploded and our satisfaction reports are lower than ever. I am here today to explain the hows and whys and introduce our next steps to bounce of this failure.

But first, let me do a quick recap of the whole situation. Since the beginning of Pentathlon, our collaborators working in stores can take of their businesses via the All4Sales application.
This application includes the stocks management, actions surrounding the prices, customer relationship, etc...
Feature after feature, the monolith became unmanageable. We never took the time to look at the big picture and realize that all we did was add to the already enormous technical debt.
It was already too late when we came to the conclusion : If we want to be competitive, we cannot continue down this way.

We gather every member of the IT department to find a solid and sustainable solution. At the time, every tech radar and every blog posts praised microservices and the whole ecosystem behind them. It also seems to correspond to our needs at the time, to split the monolith !
A year and a half ago, we rushed heads down in that idyllic direction, the one that I introduced to you in the last leaders meeting.
I am not going to explain the technical difficulties we encountered. Just know that we really struggled to deliver in due time. The new solution was finally there, ready to be used by our collaborators. A shinny new set of applications available in our custom store, Apps4Stores. However, the hype was not quite there... just the opposite.

Based on anonymous reports, 89% of our users found the new set of applications to be counter intuitive. 80% of them are not ready to stop using the legacy application. The stores where the usage of Apps4Stores was made mandatory have seen their "happiness at work" surveys' results dropped by up to 50 points in two months. One could call that a catastrophic launch.
But what went wrong? How could the users not see that everything they need is right there, under their nose?
We could not - or wanted not to - answer these questions at the time. All that mattered was to migrate every user and to decommission the legacy application.
What we did, however, is to start a massive change management plan. We brought every region managers for a three days training. Everything they needed to know about how to use the applications and how to train people themselves was explained to them. After that, we published a series of video tutorials and let two months to the managers to train the collaborators in their region.
Let us just say that it may not have been our smartest nor our most appreciated move.

With no precise directive and no shared values, nearly all of the managers failed to make everyone walk in the same direction.
Some stores finally dropped the legacy app, under the pressure of the deadline. Most of them, however, did not was the value of changing and just postponed.
When the date was finally there, only 8% of the stores completely dropped All4Sales. We just could not shut it down without losing billions dollars a day. One could call that a catastrophic migration.
Where could we go from there? We could choose to keep going with the same approach or to rethink the whole problem from the ground up, from an empty page. We started both of these solution and decided to see which one offers the greatest results after a few months.

We kept going with our change management and tried to create Habit Forming Products. We put a tremendous effort on adding socialization and gamification elements in our products. One could earn experience by using the set of applications on a daily basis, share his thoughts with other collaborators and fulfill diverse achievements.
It connected at first with our youngest users, but most of them disliked being addressed to as children in their workplace, according to anonymous surveys. One could call that a failed last stand from a stillborn project.

In the meantime, another team was put together to try out a completely opposite approach : learn from the previous mistakes and put the collaborator in the center of the debate.
The team was made of a consulting evangAgilist, a product owner and three software engineers. They had carte-blanche to do whatever they needed to provide a well-received and promising solution. We expected them to deliver a small Proof of Concept, a little side project with a workflow we could follow for out next products. They blew this expectation away and may have changed the while mindset of Pentathlon's IT department.

The first action they took may seem quite simple : they put their offices next to an actual store.
They are the first IT team to localize themselves out of the department, and to go closer to their clients. This way, they were able to find allies in the store's collaborators. A lot of informal discussions were made for the team to really understand their users.
When the time was there to start brainstorming , they invited a representative of the domain and two sellers. They all tried to pinpoint the actual domains behind the users' work.
These workshops took a certain amount of time to get right, and they needed to iterate a lot on their discoveries, but it really makes the team understands their domains.
While continuing to iterate on the discovery work, they started implementing the more matured domain, the stock management.
Knowing every events occurring in this domain and every associated actors, they could relatively quickly provide an answer tailored to the users' needs.
The first store to try this solution out was the one next to the team. They loved the product and the approach so much that the word swiftly spread out. Tutorials and formations was not needed since the user experience was so well mapped on their behaviors.
A few other stores already uses the new solution and it will be available to everyone in the very near future. One could call that a complete success!

We have already planned to follow the same schema for the other domains. There is still a lot of work to do, but we believe that this mindset is the right one to build the best solutions for our users. Solutions that are helping our collaborators, not constrain them.

I would like to thank you all for coming, do not hesitate if you have any questions or if you want to meet the team!
This article is a satire, it does not represent any actual individuals or companies. It was initially made to be presented in Agile and IT conferences.
The main goal is to initiate debates and you can do so in the comments section.

The smell of change management

Code smell : In software development, any symptom of a greater sin within the product.

Ladies and gentlemen, members of the board and share-holders, I am glad to welcome you to this year's leaders meeting.
For those of you who do not know me, the name is Thomas Doe, co-creator of Pentathlon and head of the IT department.
I hope that everyone made a fine trip and that you all enjoyed the petits fours. It is now time to kickstart this meeting with the less enjoyable news. Yes, I am talking about the migration to our new set of applications.

 That all of our collaborators will finally be able to stop using our legacy catch-all solution.
Not only did we miss the milestone, but we also have seen our expenses exploded and our satisfaction reports are lower than ever. I am here today to explain the hows and whys and introduce our next steps to bounce of this failure.

But first, let me do a quick recap of the whole situation. Since the beginning of Pentathlon, our collaborators working in stores can take of their businesses via the All4Sales application.
This application includes the stocks management, actions surrounding the prices, customer relationship, etc...
Feature after feature, the monolith became unmaintainable. We never took the time to look at the big picture and realize that all we did was add to the already enormous technical debt.
It was already too late when we came to the conclusion : If we want to be competitve, we cannot continue down this way.

We gather every member of the IT department to find a solid and sustainable solution. At the time, every tech radar and every blog posts praiser microservices and the whole ecosystem behind them. It also seems to correspond to our needs at the time, to split the monolith !
A year and a half ago, we rushed heads down in that idyllic direction, the one that I introduced to you in the last leaders meeting.
I am not going to explain the technical difficulties we encountered. Just know that we really struggled to deliver in due time. The new solution was finally there, ready to be used by our collaborators. A shinny new set of applications available in our custom store, Apps4Stores. However, the hype was not quite there... just the opposite.

TODO :

[ ] Lighten the tone
[ ] Add a stock picture for every part
[ ] Check if it fits in a 15 minutes talk (quicky)