cephfs: replace getCloneInfo() with a go-ceph implementation

Once #1545 is merged, implement getCloneInfo() with go-ceph language bindings too.

This is fixed now closing


Wrap inline code

Hi,
Amazing theme! For some reason, long inline code blocks do not wrap properly.
Is there any way to resolve this?
Thank you!

Makes sense, thanks! I'll put long code in blocks instead.


Incorrect default option string for wasm-runtime

The default value for wasm-runtime option shows incorrectly.
# wasm-runtime = e (=eos-vm-jit

https://github.com/EOSIO/appbase/pull/86


message.gFOF = status[1] IndexError: list index out of rang

Traceback (most recent call last):
File "/home/toor/catkin_ws/devel/lib/onrobot_rg_control/OnRobotRGTcpNode.py", line 15, in
exec(compile(fh.read(), python_script, 'exec'), context)
File "/home/toor/catkin_ws/src/onrobot/onrobot_rg_control/nodes/OnRobotRGTcpNode.py", line 90, in
OnRobotRGTcp()
File "/home/toor/catkin_ws/src/onrobot/onrobot_rg_control/nodes/OnRobotRGTcpNode.py", line 50, in init
self.mainLoop()
File "/home/toor/catkin_ws/src/onrobot/onrobot_rg_control/nodes/OnRobotRGTcpNode.py", line 68, in mainLoop
status = self.gripper.getStatus()
File "/home/toor/catkin_ws/src/onrobot/onrobot_rg_control/src/onrobot_rg_control/baseOnRobotRG.py", line 107, in getStatus
message.gFOF = status[1]
IndexError: list index out of rang

@Raviteja-T
Please carefully explain the condition when you faced this error and change the title so that we can understand what kind of issue this is.
The title is not the place to copy and paste the error.


Add support for Scala 2.12.12

Still something doesn't compile Oo
home/runner/work/scalameta/scalameta/target/scala-library/scala-2.12.12/src/library/scala/collection/immutable/TreeMap.scala:333: error: type arguments [_] do not conform to class SortedMapFactory's type parameter bounds [CC[A, B] <: scala.collection.SortedMap[A,B] with scala.collection.SortedMapLike[A,B,CC[A,B]]]
      case cbf: SortedMapFactory[_]#SortedMapCanBuildFrom[_,_] => {
                ^
/home/runner/work/scalameta/scalameta/target/scala-library/scala-2.12.12/src/library/scala/collection/immutable/TreeSet.scala:210: error: type arguments [_] do not conform to class SortedSetFactory's type parameter bounds [CC[A] <: scala.collection.SortedSet[A] with scala.collection.SortedSetLike[A,CC[A]]]
      case cbf: SortedSetFactory[_]#SortedSetCanBuildFrom[_] => {
                ^
two errors found

I changed to compile the 2.13.3 sources instead of 2.12.12, which works around the issue. I unable to reproduce the issue by disabling the SemanticDB compiler plugin when compiling the sources of 2.12.12 so I suspect the root cause is on our side instead of a regression in 2.12.12. I don't have time to investigate further so I'm gonna go ahead and merge anyways.
We should keep an eye out for related issues where enabling SemanticDB causes compile errors in 2.12.12. I haven't seen this happen before, the plugin doesn't mess with the type-checker anymore (it used to replace the type-checker with runtime reflection).


Update for IntelliJ IDEA 2021.1.1

The plugin manager is reporting Incompatible: Requires IDE build 203.* or older when running IntelliJ IDEA 2021.1.1

This should be fixed now.  Thanks for letting me know, sorry for the delay in fixing it.


Support the other lazy projects (ie LazyNPM and LazyDocker)

Is your feature request related to a problem? Please describe.
Lazygit only supports the display of LazyGit
Describe the solution you'd like
I'd like to be able to use the other Lazy UIs developed by jesseduffield
Additional context

I don't use lazydocker or lazynpm enough that I don't think it would be best if I maintained it. You can though write your own plugin and I'm sure it'll be quite useful for folks.
Alternatively, you can use toggleterm to make a lazygit / lazydocker / lazynpm wrapper for yourself.

I've been thinking of making a fork of this for lazynpm, I'll close this if that ever happens ;)


Change bucket policy on cgl-recompute bucket

To requester-pays and open

This issue was moved to BD2KGenomics/core-dev#2


Should class yii\rest\Serializer support  a public property $params like Pagination and Sort?

This will be useful when we want to use an array parameters (name => value) to specify fields and expand parameters instead of using values come from Yii::$app->getRequest().
The implementing logic is just like the params property of yii\data\Pagination or  yii\data\Sort

I am unsure it such enhancement violates the HATEOS REST, but still: #8404

isn't this already possible using the $request property? @fproject please describe your use case in more detail.

In my case, I have fields and expand values come from HTTP request body, not from parameters.
And then, I want to set them to yii\rest\Serializer. Curently the only way is mocking a Request object  that return these values via get method.
I think if we support using an array parameters (name => value) just like the params property of yii\data\Pagination or  yii\data\Sort, its will be easier and more understandable.
And I also think this will not violate HATEOAS constraints.


Fix OpenAPI CLI messages and Formatting issues with EOF and field access

Purpose
This will fix the OpenAPI CLI tool experimental feature message to match .help file message.
Also, this will fix issues related to formatting field-based access expressions and printing EOF when the tree is broken.
Fixes #18990
Fixes #19113
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[x] Checked Tooling Support
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #19097 into ballerina-1.0.x will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           ballerina-1.0.x   #19097   +/-   ##
================================================
  Coverage            15.73%   15.73%
================================================
  Files                   47       47
  Lines                 1265     1265
  Branches               197      197
================================================
  Hits                   199      199
  Misses                1053     1053
  Partials                13       13

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 4dc7e8c...688086f. Read the comment docs.


Signed out of Git Desktop

So my Git desktop app has somehow signed me out and when I try to type what I am completely sure are the correct username and password to log in, it keeps telling me they're wrong. I've logged out of like the actual git website and logged back in WITH THE SAME CREDENTIALS just to make sure I have the info right. The weird part is it's still supposedly connected to my git account in the area where it says like "link account." And it's letting me like upload the changes but not push them to actually be published. HALP.

@zkoostra
Yikes! I take it you haven't reset your password since making your account, right? What's your operating system? Were you using Git desktop when it did this, or did it do this upon opening the program?

Perhaps it is case-sensitive? Was your caps lock on or you didn't/did capitalize something in your log in credentials? :( sorry I'm not more help!

Any luck?
Sounds like you may need to reset your password on GitHub.com http://github.com/, then come back to the GitHub Desktop and try again.

I think that it's an error of some kind where my desktop app (mac, for the person who asked that) can't connect correctly to my git account. I've reset the password, I've quit the app and reopened it, and it still is just saying my username or password is incorrect. I KNOW it's not incorrect, I know I'm not typing it wrong. I don't know what I should do from here.

Bummer. Are you in Missoula? Could you either swing by my office hours today (12-1:30)? Or to lab hours in 127 https://montana-media-arts.github.io/creative-coding-1/help/#lab-hours https://montana-media-arts.github.io/creative-coding-1/help/#lab-hours ?

I can come to office hours. Thanks, I kind of forgot that was an option lol. I'll be there.

@zkoostra I had the same issue. I uninstalled the whole app and reinstalled it. Everything is working fine for me now.

Whenever i have weird issues with programs on my computer i always start by uninstalling and reinstalling. I would say 80 percent of the time this fixes any issues.


Update images and Track as Option

During use of this library ive found a little mishap which was panicking during deserialization.
Spotify api documentation is not so generout about nullable properties.
Ive got this response from api with images being null
    {
      "collaborative": false,
      "description": "",
      "external_urls": {
        "spotify": "https://open.spotify.com/playlist/4TKd95mrFFDcaQ4zvBb3vl"
      },
      "href": "https://api.spotify.com/v1/playlists/4TKd95mrFFDcaQ4zvBb3vl",
      "id": "4TKd95mrFFDcaQ4zvBb3vl",
      "images": null,
      "name": "My Playlist #21",
      "owner": {
        "display_name": "<username>",
        "external_urls": {
          "spotify": "https://open.spotify.com/user/<username>"
        },
        "href": "https://api.spotify.com/v1/users/<username>",
        "id": "<username>",
        "type": "user",
        "uri": "spotify:user:<username>"
      },
      "primary_color": null,
      "public": true,
      "snapshot_id": "AAAAAY3hiR+5j7UoSn8R3Ny8L2yt3nBg",
      "tracks": {
        "href": "https://api.spotify.com/v1/playlists/4TKd95mrFFDcaQ4zvBb3vl/tracks",
        "total": 0
      },
      "type": "playlist",
      "uri": "spotify:playlist:4TKd95mrFFDcaQ4zvBb3vl"
    }

Same happened with empty track record ? (Probably deleted song ?????)
{
  "added_at": "2023-04-22T10:06:59Z",
  "added_by": {
    "external_urls": {
      "spotify": "https://open.spotify.com/user/k79f8pfzzsj35ytb8kf0tuzs9"
    },
    "href": "https://api.spotify.com/v1/users/k79f8pfzzsj35ytb8kf0tuzs9",
    "id": "k79f8pfzzsj35ytb8kf0tuzs9",
    "type": "user",
    "uri": "spotify:user:k79f8pfzzsj35ytb8kf0tuzs9"
  },
  "is_local": false,
  "primary_color": null,
  "track": null,
  "video_thumbnail": { "url": null }
}

Hey, thanks for the info!
Yeah, the Spotify API docs aren't reliable.
I think instead of Option<Vec<Image>> an empty Vec<Image> makes more sense, which is what the next branch uses.
As for the track record, thanks, I'll add that to the next branch since it's a breaking change and I want to release them all in the new version.
Also, may I ask what request you sent that returned the empty track record response? So I can test it a bit

Oh im not sure if i can still find the request in logs, but will give it a look within next week. Also i will give a look at @next branch

Hi,
I have closed this request since i needed to reclone the repository with the next branch.
During further examination of invalid api responses i have found the link for the empty (null) track response:
"https://api.spotify.com/v1/playlists/6s8WFDII6hpHqwsLbkIH2y/tracks?offset=260&limit=20"


Add Blaze Information Security

Fixed a double spacing on a heading
Fixed a missing line break after a heading
Improved consistency of  with and without spacing
Added Blaze Information Security on Security

Thanks @vpereira01!


[Enhancement]: Add method to return CosmosDb connection string for internal network

Problem
Right now, CosmosDbContainer has a string GetConnectionString() method which returns a connection string for use on the host. It would be useful if CosmosDbContainer also had a method returning a connection string usable within a network the container is attached to. Ideally, this method would work before the container is started so that it can be used to build other containers which rely on this connection string.
Solution
I propose adding a method to class CosmosDbContainer which is functionally equivalent to:
private string GetInternalConnectionString(string networkAlias)
{
    var properties = new Dictionary<string, string>
    {
        ["AccountEndpoint"] = new UriBuilder(Uri.UriSchemeHttps, networkAlias, CosmosDbBuilder.CosmosDbPort).ToString(),
        ["AccountKey"] = CosmosDbBuilder.DefaultAccountKey
    };
    return string.Join(";", properties.Select(kvp => string.Join("=", kvp.Key, kvp.Value)));
}

Benefit
This method will make it easier to create connection strings used to build other containers which communicate with the cosmos container.
Alternatives
This connection string can be created using the code snippet proposed above, but results in duplicated code.
Would you like to help contributing this enhancement?
Yes

I do not think this refers to the Cosmos DB Emulators module only. No module shares a method or property that resolves the internal connection string, base address, endpoint, or whatever it may be called. This heavily depends on the actual test configuration and how you put various containers together. Currently, we recommend using the network alias and manually configuring the connection, as we do, for instance, with the WebDrive module or in our Flyway example. Nevertheless, I comprehend that supporting something like this might slightly reduce the amount of necessary code and configuration.

Ideally, this method would work before the container is started so that it can be used to build other containers which rely on this connection string.

I do not understand. How would you interact with the container service before it starts?

Would you have builders for each DB impl?  Something like:
var someContainer = ...;

var connectionString = new CosmosDbConnectionStringBuilder()
    .WithInternalHost(someContainer)
    .Build();

var cosmos = new CosmosDbBuilder()
    .WithConnectionString(someContainer)
    .Build();

This would be wornderful 😊


Regenerated docs

What is this PR About?
New version of konstraint so docs code their side has been tweaked.
Check list

[x] Have you re-generated POLICIES.md

cc: @redhat-cop/rego-policies

is there really just some white space changes here?

/lgtm

@springdo yep; since its an auto-generated file, when they change how their code works it makes slight changes on our doc.


Placeholders are not consistent in all browsers

IE, Edge and Firefox have different placeholders colors than other browsers
Should add:
:-ms-input-placeholder {
color: #a9a9a9;
}
::-ms-input-placeholder {
color: #a9a9a9;
}
:-moz-placeholder,
::-moz-placeholder {
color: #606060;	/* -> #a9a9a9 on display */
}

@Yapaslfeu, great work. Why is that the placeholder in Firefox requires a different color than what is displayed. Are they also using opacity or something?

You're right, there's an opacity set!
For Firefox, should be:
:-moz-placeholder,
::-moz-placeholder {
color: #a9a9a9;
opacity: 1;
}

Fantastic. Why are you including both the invalid : and :: valid pseudo-element selectors?

I kept it for backward compatibility only but we can remove it

I think the single colon notation : was only relevant to IE8.

I this this would be a nice addition.
Regarding compatibility, @thierryk is right, IE8 only supports the single-colon syntax, and only Firefox 18- supports :-moz-placeholder.

In the past, I tried to normalise placeholder according to the styles applied by Firefox:
/* Blink, WebKit, Edge HTML */
::-webkit-input-placeholder {
  color: inherit;
  opacity: .54;
}
/* Gecko */
::-moz-placeholder {
  color: inherit;
  opacity: .54;
}
/* Trident */
:-ms-input-placeholder {
  color: inherit;
  opacity: .54;
}

but IE 11 applies also opacity on the form element itself and does not inherit the color from the form element :sob:
Here is my test: http://codepen.io/7studio/pen/MKVvev
I hope it can help you in your reflexion.

There was some discussion a long time ago on the issue with placeholders in https://github.com/necolas/normalize.css/issues/157 but it was eventually closed.

Thanks @grantgeard for contributing to this issue over the years. Did you ever come across a clever way to share the currentColor with a placeholder without running into the bug you described? Is the opacity linked hard-wired to the input -ms-input-placeholder?

@jonathantneal I don't think it's possible. IE has implemented :-ms-input-placeholder as :placeholder-shown which the spec describes as a pseudo-class that targets an input element that is currently showing placeholder text. That's why changing the opacity affects the entire element and why the styles aren't applied after the input is focused or a value is entered.

^ @grantgeard, that is very sad, but your explanation provides exactly the information we need to make a decision, so thank you so very much. :)

input::-moz-placeholder {   opacity: initial; } input::-webkit-input-placeholder {   color: inherit; }
It's enough for ie10-11, safari8-9, firefox44 and chrome49. (tested by https://www.browserstack.com)
But, if you need opacity, code will be:
input:-ms-input-placeholder {   opacity: 0.54; } input::-moz-placeholder {   opacity: 0.54; } input::-webkit-input-placeholder {   opacity: 0.54;   color: inherit; }
with bug in IE10 and 11 (border will inherit opacity from placeholder, i dont know why..)

Since Edge understands the ::-webkit-input-placeholder, we can normalize Edge, Chrome, and Safari with just one rule.
::-webkit-input-placeholder {
  color: inherit;
  opacity: 0.54;
}

This leaves IE 10-11 untouched, appearing somewhat similar to other browsers, only without additional opacity. It could be manually added using something like:
:-ms-input-placeholder {
  color: rgba(0,0,0,.54);
}

But the rgb values would need to be adjusted based on the color being specified; something we can leave to authors.

I think the IE problem is a big issue for the moment, as it's still used a lot!
Despite all the discussions, i still believe that we have to force the placeholder color to a light grey for the moment, and fix Firefox - the only browser which do it differently - to opacity:1!
Firefox is not necessary right: light silver is like a system color for placeholders, and placeholders with a lighter color than the input text is not so logic in my point of view.
Above all, it's far more easy for one to change all the placeholders colors if needed (i.e. bad readability, which is not so common and immediately visible, even at design phase), than obliging everybody to set the placeholder color with a rgba when changing the fields text color (very common modification), and only for IE 11!

[https://github.com/necolas/normalize.css/pull/571#issuecomment-208283753]


Returning the whole media information when uploading

Hello, I know this library is not in active development anymore, but I'd like to know if it was possible to update the .uploadMedia wrapper in order to return the full media information instead of the media_id.
https://github.com/PLhery/node-twitter-api-v2/blob/38f87ecc8d58cf8da92798be408fecd632e54219/src/v1/client.v1.write.ts#L382
Of course, a workaround is to use the .mediaInfo wrapper, but if we can save a request for an information we have when uploading a media, that would be nice. Another solution is to fork this repo, make the change and use my forked version, but it would be easier to have it here. It would be a breaking change so probably a major version change.
I'm looking for the media_key and expires_after_secs values.
Any reason to return the media_id instead of whole object?
Thank you!

Fair point ; to avoid a breaking change, we could add an argument "returnFullMediaData = false" to decide whether to return the id or the full object

What's the excepted behaviour when media processing fails?
Throw an error or return the .mediaInfo data with the error payload?

@PLhery Adding a parameter with default behavior to current would be perfect to prevent major version change.
@alkihis I don't know, something that will be consistent with other POST endpoints will be fine!

Feature available in v1.16.0


Changing values with form.setValues() in an onChange() handler removes reactive props

Environment

OS: macOS 10.12.6
Node: 8.9.4
NPM: 5.6.0
react-advanaced-form: 1.6.7

What
Current behavior
When 2 fields that have a reactive prop (required) on the same field, and that field has an onChange handler that calls this.form.setValues(), the reactive props are removed.
Expected behavior
Calling setValues() from an onChange handler for a field upon which other fields react should not remove reactive props.
Use Case
The reason I was doing this was because I wanted to clear the values of 2 text boxes when I unchecked a checkbox on my form and both of those text boxes were required if the checkbox was checked.
How
I altered the SingleTarget reactive props example from your codebase to exhibit the problem.  See below. Note that if you remove fieldThree from setValues() and only alter firstName the issue doesn't occur.  Seems like it only happens if you modify more than one form field.  Also, the fields that you modify with setValues() don't have to be the ones with the reactive props - they can be any other 2 fields.
import React from 'react'
import { Form } from 'react-advanced-form'
import { Input } from '@examples/fields'
import Button from '@examples/shared/Button'

export default class RxPropsSingleTarget extends React.Component {
  handleChange = () => {
    this.form.setValues({
      firstName: "",
      fieldThree: ""
    })
  }

  render() {
    return (
      <React.Fragment>

Single target

        <Form onSubmitStart={this.props.onSubmitStart} ref={(form) => this.form = form}>
          <Input
            name="firstName"
            label="First name"
            hint="Required when `lastName` has value"
            required={({ get }) => {
              return !!get(['lastName', 'value'])
            }}
          />
          <Input name="lastName" label="Last name" onChange={this.handleChange} />
          <Input
            name="fieldThree"
            label="Some field three"
            hint="Required when `lastName` has value"
            required={({ get }) => {
              return !!get(['lastName', 'value'])
            }}
          />
          <Button>Submit</Button>
        </Form>
      </React.Fragment>
    )
  }
}

Thank you for reporting, @johnpreed!
Please give me some time, I will get into this issue's scenario on my local and will update shortly after with more technical details.
Meanwhile I am re-writing the state update algorithm to use patched state updates. This may resolve this issue in case it's a concurrency problem (updateA contains next value of reactive prop, update B contains next value without react prop). No release deadline, there's quite a lot of work to verify after such change.

Quick update: Testing your use case on the latest branch I can conclude that the reactive prop (required) is updated properly when typing into lastName. However, as you can see on the screenshot below, subscribed fields must not be set as "valid" once they are cleared using setValues().
I will add this scenario into existing scenario to make sure its test passes.


On fresh Windows install, launch fails due to missing msvcp140.dll

Version
0.3.3
What steps are needed to reproduce the behavior?

Have fresh Windows install.
Install Stevedore.
Restart to complete installation.
Stevedore startup launch fails. If you try and launch manually, you'll be prompted by the missing dll.

What you expected?
Stevedore launches on startup.
What happened?
Missing msvcp140.dll.
Additional context
Although I doubt anyone will be installing this on a fresh windows install, it doesn't hurt to cover all launch prerequisites in order foro the executable to function.

This issue was fixed in just-released Stevedore 0.3.4


Define a standard for how to size elements

I've been trying to create some standard for how I write code, and this is an area I've been flip flopping with for months. I've read a couple of great articles on why you should use rem for global sizing and em for local sizing. This seems to make sense to me, and I should try to implement it.
The idea is to make modules use em so that they dynamically size to their layout containers.
More information:

https://css-tricks.com/rem-global-em-local/
https://css-tricks.com/rems-ems/

I definitely like px at the root, rem for blocks, and ems for fonts.


Release beta to main

Release beta build to main

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Invited user receives "You need permissions" error when tries to access SP Online site after federation

Thanks for the article. I have created Google federation and indeed the gmail user is not required to create MS account. We want to invite gmail users to an Office 365 group and collaborate within the corresponding SharePoint online site
However there is a very annoying issue: When the user click in the email he received (after being added to an Office 365 group) on the link Go To SharePoint he gets an error "You need permission to access this site". However, if the user clicks again on the Go To SharePoint link in the email, he is given access!. This situation spoils the entire user experience.
I have attached step-by-step screenshots

Please help with this. I have tested already with 2 different organizations and the same problem.
Marius

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

ID: 6ed01893-a5cd-28bd-b865-e7ebe5870567
Version Independent ID: b3d96be0-1470-eb2c-ea5b-cea0a5cc44a1
Content: Add Google as an identity provider for B2B - Azure AD
Content Source: articles/active-directory/b2b/google-federation.md
Service: active-directory
Sub-service: b2b
GitHub Login: @msmimart
Microsoft Alias: mimart

Hello @tmarius1970, Can you share the Azure document link / URL that you are referring to ?
This azure-docs repository deals about feedback related to particular Azure document page (like correcting doc bugs, doc enhancements, product issues related to wrong doc instructions if any, etc.) so thats the reason for asking related Azure document link / URL to get more context of this issue if it's intended to update / correct / enhance anything in the referred Azure document.

Hi, yes, sorry about that.
The link is:
https://docs.microsoft.com/en-us/azure/active-directory/b2b/google-federation
Marius
On Mon, Feb 17, 2020 at 10:50 AM KrishnaG-MSFT<EMAIL_ADDRESS>wrote:

Hello @tmarius1970 https://github.com/tmarius1970, Can you share the
Azure document link / URL that you are referring to ?
This https://github.com/MicrosoftDocs/azure-docs/issues azure-docs
repository deals about feedback related to particular Azure document page
(like correcting doc bugs, doc enhancements, product issues related to
wrong doc instructions if any, etc.) so thats the reason for asking related
Azure document link / URL to get more context of this issue if it's
intended to update / correct / enhance anything in the referred Azure
document.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/48228?email_source=notifications&email_token=AOSOL4B2AWMBUGFZ7QPVYFLRDJFWRA5CNFSM4KWMUUX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL5RQOY#issuecomment-586881083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOSOL4BJACSZETGEMKUJF2LRDJFWRANCNFSM4KWMUUXQ
.

@tmarius1970 Thanks for your referred Azure document link / URL. We will review and provide an update as appropriate.

@tmarius1970 I tested this in my lab and you are absolutely correct. The first access attempt blocked by SharePoint and the subsequent access attempt without even requesting access is allowed. I setup an exactly similar scenario and collected a fiddler trace where I see the Access denied sent by sharepoint at the first access attempt after invitation is redeemed using "Go to sharepoint".
I also noticed that I had to invite the guest gmail user by using Outlook People Application . When I clicked Add members then the invitation is sent .

I collected a fiddler trace and the first request when we click the "Go to sharepoint" link there is a HTTP 302 redirect to https://outlook.office365.com/owa/gtest@xxxxxx.onmicrosoft.com/groupsubscription.ashx?source=WelcomeEmail&sourceversion=V2&action=files&GuestId=505715e5-2b2f-4cfa-9f5d-e810d8dd64c1
And this redirects to SharePoint . Sharepoint finds that the user is still new and does not have a valid token because the invited user has yet not redeemed the invitation so Invitation redemption starts and SharePoint redirects the user to login.microsoftonline.com for redemption of B2B invitation.

Once the invitation is redeemed , The request is redirected to<EMAIL_ADDRESS> and this is where the first AccessDenied is returned. I believe this is because The sharepoint team site may not be allowing guests at the first attempt or its yet not able to verify the state of user about B2B invitation redemption.

Once this is done, we try to click the go to SharePoint link again in 2nd request as shown in above fiddler trace and SharePoint access is given without an issue. At this point I believe sharepoint is able to verify that the user is part of the o365 group for which they are trying to access the team sharepoint and hence it allows access. this is my understanding as per the details in the trace.
I believe this would be normal behavior by SharePoint however I do agree that this surely does not provide best user experience. In order to get a definitive answer I would suggest to open a case with the sharepoint support team using Office365 admin portal and they will help you on the same. If you have any trouble opening a case , please do email us at azcommunity[at]microsoft[dot]com and we will help you with the same. If you have opened a case , please let me know the case number and I can internally help drive the same.
Please let us know in case you have any further queries.

Hi Shashi Shailaj
Thank you for your detailed analysis, I am not familiar with fiddler and couldn’t do it without you.
I am interested to know if there is a solution or maybe a workaround for this issue.
I have not opened any case yet, can you do it for me?
Thank you,
Marius
Toma Marius
Administrator
SC CLOUDLOGIC SRL
office<EMAIL_ADDRESS>+40723-425-750
From: ShashiShailaj-MSFT<EMAIL_ADDRESS>Sent: Wednesday, February 19, 2020 9:18 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: tmarius1970<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Invited user receives "You need permissions" error when tries to access SP Online site after federation (#48228)
@tmarius1970https://github.com/tmarius1970 I tested this in my lab and you are absolutely correct. The first access attempt blocked by SharePoint and the subsequent access attempt without even requesting access is allowed. I setup an exactly similar scenario and collected a fiddler trace where I see the Access denied sent by sharepoint at the first access attempt after invitation is redeemed using "Go to sharepoint".
I also noticed that I had to invite the guest gmail user by using Outlook People Application . When I clicked Add members then the invitation is sent .
[image]https://user-images.githubusercontent.com/532022/74861990-4f981c00-5371-11ea-82de-99f549c38f1d.png
I collected a fiddler trace and the first request when we click the "Go to sharepoint" link there is a HTTP 302 redirect to https://outlook.office365.com/owa/gtest@xxxxxx.onmicrosoft.com/groupsubscription.ashx?source=WelcomeEmail&sourceversion=V2&action=files&GuestId=505715e5-2b2f-4cfa-9f5d-e810d8dd64c1
And this redirects to SharePoint . Sharepoint finds that the user is still new and does not have a valid token because the invited user has yet not redeemed the invitation so Invitation redemption starts and SharePoint redirects the user to login.microsoftonline.com for redemption of B2B invitation.
[image]https://user-images.githubusercontent.com/532022/74865757-aa347680-5377-11ea-8ad9-2d28e1be0770.png
Once the invitation is redeemed , The request is redirected to<EMAIL_ADDRESS>and this is where the first AccessDenied is returned. I believe this is because The sharepoint team site may not be allowing guests at the first attempt or its yet not able to verify the state of user about B2B invitation redemption.
[image]https://user-images.githubusercontent.com/532022/74867130-2465fa80-537a-11ea-8f93-71c88198189d.png
Once this is done, we try to click the go to SharePoint link again in 2nd request as shown in above fiddler trace and SharePoint access is given without an issue. At this point I believe sharepoint is able to verify that the user is part of the o365 group for which they are trying to access the team sharepoint and hence it allows access. this is my understanding as per the details in the trace.
I believe this would be normal behavior by SharePoint however I do agree that this surely does not provide best user experience. In order to get a definitive answer I would suggest to open a case with the sharepoint support team using Office365 admin portal and they will help you on the same. If you have any trouble opening a case , please do email us at azcommunity[at]microsoft[dot]com and we will help you with the same. If you have opened a case , please let me know the case number and I can internally help drive the same.
Please let us know in case you have any further queries.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/48228?email_source=notifications&email_token=AOSOL4AKOSMH7WMFJA7BHQTRDWAXTA5CNFSM4KWMUUX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMJD6VY#issuecomment-588398423, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOSOL4HWIA7JUCETT2VZQPTRDWAXTANCNFSM4KWMUUXQ.

@tmarius1970 Thank you for your reply . I tried to check a workaround and found that if you add the guest  user being invited using the Azure AD portal (portal.azure.com) and add the user to the O365 group you had created beforehand while inviting the user itself , the user just gets an email that they have been invited to the tenant .  And user tries to access the team SharePoint using the URL https://.sharepoint.com/sites//  they don't get access denied. But in this case they also do not get a similar mail as below.

They will need to be provided the Exact URL for the team site eg.  https://.sharepoint.com/sites//  . However if you use the Outlook People application from the O365 launcher panel then you will still get the access denied in first attempt. I would require an email from your side as its essentially a problem from Office365 . We use github for documentation improvement and this issue seems to require deeper troubleshooting hence I would suggest you to send us an email azcommunity[at]microsoft[dot]com and we will take this offline internally to find a solution for the same . We are closing this issue now however I will be waiting for your email to take this further internally.
Thank you.


LightevalTask.process_results() is not aligned with LightevalTask.get_request_type()

Hi there!
LightevalTask.process_results() does not expect the same ordering of requests by type as what is implied by LightevalTask.get_request_type():
create_requests_from_tasks returns a dict of requests whose keys' order follows the return value of get_request_type(). This request dict is iterated in evaluate() and the responses of different request types belonging to a specific task_example are put into a list with the same order as that of the get_request_type() as a consequence. By process_results() expects another order which could break things.
A reproducing example:
from lighteval.tasks.lighteval_task import LightevalTask, LightevalTaskConfig
from lighteval.tasks.requests import Doc, TaskExampleId
from lighteval.logging.evaluation_tracker import EvaluationTracker
from lighteval.evaluator import evaluate
from lighteval.models.base_model import BaseModel, BaseModelConfig, EnvConfig
import collections

def test_get_request_type_and_process_results_alignment():
    config = LightevalTaskConfig("test", "arc", "test","test", ["loglikelihood_acc", "exact_match"], evaluation_splits='test',generation_size=4, stop_sequence=["\n"])
    task = LightevalTask("test", config)
    doc = Doc("Which one?", ["A"], 0)
    reqs = task.construct_requests(doc, doc.query, "", "test|0")
    all_reqs = collections.defaultdict(list)
    req_types = task.get_request_type()
    for req_type in req_types:
        all_reqs[req_type].extend(reqs[req_type])
    model_config = BaseModelConfig("hf-internal-testing/tiny-random-gpt2")
    model = BaseModel(model_config, EnvConfig())
    evaluation_tracker = EvaluationTracker()
    evaluate(model, all_reqs, {TaskExampleId("test|0",""): doc}, {'test': task}, 1, evaluation_tracker)

Output:
self = <lighteval.metrics.metrics_sample.ExactMatches object at 0x7f744b3f8ca0>, gold = 'A'
pred = -6.878859996795654

    def compute_one_item(
        self,
        gold: str,
        pred: str,
    ) -> float:
        """Compares two strings only.

        Args:
            gold (str): One of the possible references
            pred (str): One of the possible predictions

        Returns:
            float: The exact match score. Will be 1 for a match, 0 otherwise.
        """
        if not pred:
            return 0

        if self.strip_strings:
            gold = gold.strip()
>           pred = pred.strip()
E           AttributeError: 'float' object has no attribute 'strip'

The solution might be to make get_request_type() return always the same ordering (currently it runs set() on its intermediate request type list and Set doesn't guarantee the order) and change process_results to expect the same ordering for responses.
By the way, thank you for this great library. My issues & PRs are due to my job task on evaluating LLMs in a specific domain. I would be happy to tackle this issue if it helps.

We're a bit swamped but thanks a lot for your interest in the lib! We'll come back to it full speed in hopefully a week, and will do our best to address your PRs

@clefourrier , shall I send new PRs or wait until then if it makes inconvenience?

It's not inconvenient at all, we just won't have time to work on them and give you feedback for at least a week :)

A cleaner example with the same error:
from unittest.mock import Mock
from lighteval.tasks.registry import Registry, taskinfo_selector
from lighteval.tasks.lighteval_task import create_requests_from_tasks, LightevalTask
from lighteval.models.base_model import BaseModel, BaseModelConfig
from lighteval.models.model_config import EnvConfig
from lighteval.evaluator import evaluate

model_config = BaseModelConfig("hf-internal-testing/tiny-random-LlamaForCausalLM")
base_model= BaseModel(model_config, EnvConfig())
task_names_list, few_shots_dict = taskinfo_selector("original|arc:c:letters|0|0")
task_dict = Registry(cache_dir="").get_task_dict(task_names_list)
LightevalTask.load_datasets(task_dict.values())
requests, docs = create_requests_from_tasks(
        task_dict=task_dict,
        fewshot_dict=few_shots_dict,
        num_fewshot_seeds=0,
        lm=base_model,
        max_samples=1,
        evaluation_tracker=Mock(),
        use_chat_template=False,
        system_prompt="",
)
evaluate(base_model, requests, docs, task_dict, 1, Mock())


support updating doc mapper through api

Description
allow updating the doc-mapper of an index
part of #5084
How was this PR tested?
updated tests, tested manually on a simple doc-mapper change (changing tokenizer)

The docs need to be updated:

https://github.com/quickwit-oss/quickwit/blob/3df3eed6ca1b9e24fc2ede522b23f3d9f955e00a/docs/reference/rest-api.md#L311-L333
https://github.com/quickwit-oss/quickwit/blob/3df3eed6ca1b9e24fc2ede522b23f3d9f955e00a/docs/configuration/index-config.md#L17


Charging stations and Gates are considered as obstacles.

if you put a configuration where a rack or a gate is only reachable through passing on a station or gate, the order gets issued but the robot doesn't move. I don't think that the stations and gates should be considered as areas that the robot can't go through, but if that is done because of something else please tell me. Also if there is a gate that is surrounded by impassable objects why does the order say that it is still issued despite it being impossible to be fulfilled ?

Something related to this issue, in agent sliding racks, stations, gates aren't considered as obstacles. I know why they aren't considered as obstacles in this case which makes me think that they shouldn't be as obstacles in normal order issuing as well. Not sure about racks but why not ?

Hmm, that is strange! 😅
If you are able to reproduce the bug, please save the map and send it to me.


[vm] Inline == operation in AOT

Currently == is not inlined in AOT when the LHS is nullable.
When the LHS is a nullable instance of a type which doesn't override ==, we should emit a simple compare.

/cc @mraleph @mkustermann


elastic release

https://github.com/Azure/sdk-release-request/issues/4156

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-arm-elastic


Notebooks: Fast update WYSIWYG support for source update (#12289)

This PR fixes #12287.

Pull Request Test Coverage Report for Build 259897688

20 of 23 (86.96%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.04%) to 38.998%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/contrib/notebook/browser/models/notebookTextFileModel.ts
20
23
86.96%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/jupyter/pypiClient.ts
1
81.82%

Totals

Change from base Build 259786930:
0.04%

Covered Lines:
19172

Relevant Lines:
44874

💛  - Coveralls


Generate changelog without tags with qualifier.

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

Comparison is base (c335c56) 69.31% compared to head (a8e418b) 69.36%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #49      +/-   ##
==========================================
+ Coverage   69.31%   69.36%   +0.04%
==========================================
  Files           7        7
  Lines         642      643       +1
==========================================
+ Hits          445      446       +1
  Misses        197      197

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


Add virtual miniscreen (display and buttons) web interface

I am imagining this as a backend of the miniscreen class - it could be configured to output to display/web/imgcat/pygame, etc.
An alternative would be to provide it as a swap-out replacement for pitop.miniscreen.Miniscreen

perhaps pitop.miniscreen.WebEmulator?

This is obviously a different paradigm to other web interfaces in the SDK, but the advantage of doing this separately for the miniscreen is that this would be great for rapid debugging, local development (no pi-top), etc.

Ins't this the same as #485 ?


List of plots that could be pleasant to have

Phase-space

[x] Phase-space of two dimensionless variables for one system, with color as the time value
[ ] Phase-space of two dimensionless variables for all the system, with color as the system index
[ ] All phase-space of each couple of dimensionless variables for :

One system color time
All systems

Filters, common dimensions

[x] When displaying all variables at the same time, doing it in 3 graphs :

Extensive possibility in log
Intensive
Dimensionless

[x] This system with all the variables that share the same dimensions on the same graph

One variable and more analysis

[x] One variable is shown with its envelope evolution, and statistical indications such as :

Mean value during a cycle (and the evolution of this mean value)
std during a cycle
Max and min during a cycle (and their evolution)
Cycle duration
Harmonic components

Done everything for one system (multiple system will come later)


[7.x] Str::slug(null) will fail

Laravel Version: 7.0.1
PHP Version: 7.4.3

Description:
Str::slug(null) will not works anymore. Not was documented as a breaking change. But I think that is better force (string).
In real world case, some fields from a table, for instance, could be a VARCHAR(...) NULLABLE, and you can't use anymore something like Str::slug($user->name) without a (string) cast in all cases.

Sent in a PR: https://github.com/laravel/framework/pull/31717


DeprecationWarning: The punycode module is deprecated

With Node 22, the following error message is output anytime aio is run:
(node:353) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

Fix recommended by Node here: https://nodejs.org/api/punycode.html#punycode. We'll likely need to figure out where punycode is being used and replace it with the userland version.

Full deprecation trace (using node's --trace-deprecation flag):
(node:46829) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
    at node:punycode:3:9
    at BuiltinModule.compileForInternalLoader (node:internal/bootstrap/realm:398:7)
    at BuiltinModule.compileForPublicLoader (node:internal/bootstrap/realm:337:10)
    at loadBuiltinModule (node:internal/modules/helpers:96:7)
    at Module._load (node:internal/modules/cjs/loader:1063:17)
    at wrapModuleLoad (node:internal/modules/cjs/loader:212:19)
    at Module.require (node:internal/modules/cjs/loader:1297:12)
    at require (node:internal/modules/helpers:123:16)
    at Object.<anonymous> (/opt/homebrew/lib/node_modules/@adobe/aio-cli/node_modules/whatwg-url/lib/url-state-machine.js:2:18)
    at Module._compile (node:internal/modules/cjs/loader:1460:14)

This is due to node-fetch requiring an out-of-date version (5.0.0, current is 14.0.0) of whatwg-url (https://www.npmjs.com/package/whatwg-url/v/5.0.0?activeTab=code) which includes an out-of-date version of tr-46 which incorrectly imported the puny-code package for versions 3.0.0 and older.
This project either needs to upgrade to a 3.x.x version of node-fetch, or node-fetch needs to upgrade their 2.x.x's whatwg-url version to one that supports a newer version of tr-46.

Closing this in favor of: https://github.com/adobe/aio-cli/issues/679


Fail transaction if requested cu-limit exceeds max limit

Problem
Currently user can set_compute_unit_limit to any valid u32, it would be silently trimmed at MAX_COMPUTE_UNIT_LIMIT if exceeds the limit. Transactions that set cu-limit above MAX_COMPUTE_UNIT_LIMIT should just fail.
(This is part of #682. Another part of cu-limit validation needs additional plumbing of native program's cost, will do that separately.)
Summary of Changes

add TransactionErr::InvalidComputeUnitLimitRequested
If cu-limit's requested, check if it exceeds max limit; fail tx if so.

Partially fixes #682

This is going to require a feature switch right?

This is going to require a feature switch right?

oh yes, good call!

This is going to require a feature switch right?

oh yes, good call!

Adding an additional feature switch to process_compute_budget_instructions would have to touch a dozen files, piping feature_set everywhere. Putting this PR as draft for now, while looking at what it takes to bring runtime-transaction online first.


Empty bills & project members after password change on cospend

Hi there,
I noticed another bug. If I changed the project password on the server side the project still shows the project as active in the project list, but bills & project members are empty.
I would expect an error with a prompt to re-enter the password again.

Hi, good point, this would be a much better UX.
Could take a while, as I am fixing the more critical bugs first.
I think this could be a good issue for someone new wanting to contribute and try out a bit of SwiftUI though!


Please provide a sample/snippet for publishing NPM module (tgz) using REST api

Such scenario is critical for migration of private NPM with tens thousands packages. Official npm publish way is no go as it does not allow to define registry in case module defines publishConfig in package.json.

@OlegZee -- Oleg, thank you for your feedback.  Are you following a particular learn.microsoft.com article?  Meanwhile, please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

I did look over all available resources everywhere with no success. The widely popular opinion is that it's not possible at all.

@OlegZee -- Oleg, thank you for your follow-up.  Is there a specific learn.microsoft.com article that you'd like to add this information into?

@WilliamAntonRohm I do not see a solution and I don't see any resource explaining any of migration scenarios for any 3rd party repositories. Tio begin with https://learn.microsoft.com/en-us/azure/devops/migrate/migration-overview?view=azure-devops

@OlegZee -- Oleg, your request may be out of scope for this documentation.
cc @chcomley for awareness


⚠ Bofrost.at has degraded performance

In 233a1a6, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1115 ms

Resolved: Bofrost.at performance has improved in 9ed24aa after 16 minutes.


Using {{since build.started}} throws Evaluation error type float64 but it should be int64

Hello,
I added {{since build.started}} to my .drone.yml as per the doc (http://plugins.drone.io/appleboy/drone-telegram/). But notification fails.
Here is the error message:
Evaluation error: Helper since called with argument 0 with type float64 but it should be int64

Any idea? Thanks a lot!

Try appleboy/drone-telegram:linux-amd64 image


Migrate build tool to glide

Migrate away from gvt to glide. Standardising build tools with the user service.

Should this be "migrate build tool to dep" now that the Glide project page itself says "Please consider trying to migrate from Glide to dep."?
:P


Support primitive types for entity attributes

Need to support primitive types for entity attributes.
Motivation:

Mentioned by Vlad problem with GraphQL and User/UserDetails entity (https://github.com/Haulmont/jmix-templates/issues/28)
Outside developers are often confused why we don't support primitives
"boolean" is much more convenient to use than Boolean, because Boolean null is the same as Boolean false.
Help users to avoid NPEs in code (e.g. with mathematic calculations)

Points to discuss:

Should we offer primitives in Studio entity designer?
...

old CUBA ticket: https://github.com/cuba-platform/cuba/issues/1288


Design a backend solution for tx monitoring

Design a way to generate notifications for movements of funds on certain addresses. Currently we only plan to create the backend infrastructure. Rollout should only be done if we can ensure that the txs are visible in the graphsense dashboard upon notification. With the current syncing granularity of one day this would lead to a bad user experience (user gets notification, clicks link, record not found).

The Release r23.06 includes a preliminary version of tx monitoring. A user can define a watch config (eth_watch_config.json.cfg) file in the form of:
{     "0x05a56e2d52c817161883f50c441c3228cfe54d9f": {         "email"<EMAIL_ADDRESS>        "on_outgoing": true,         "on_incoming": true     },     "0xd9666150a9da92d9108198a4072970805a8b3428": {         "email"<EMAIL_ADDRESS>        "on_outgoing": true,         "on_incoming": false     },     "0xdac17f958d2ee523a2206206994597c13d831ec7": {         "email"<EMAIL_ADDRESS>        "on_outgoing": true,         "on_incoming": true     } }
to get notified on incoming or outgoing cryptocurrency events. A watcher process can then be started with (for a dev environment)
graphsense-cli -v watch money-flows -e dev -c eth --state-file watcher_state.json.cfg --watchpoints-file eth_watch_config.json.cfg
the watcher_state.json.cfg file is uses to persist the last watched block by the watcher process and continue there on the next startup. The process by default sleeps if no new blocks are available.

created a followup improvement issue (https://github.com/graphsense/graphsense-lib/issues/7). Closing


Accessibility: Heading structure in API-delegation

Description
We have issues with heading structures in all of our pages.
Headings should follow a hierarchical descent, and the first should always be a h1.
On most current pages this can be achieved by simply making the header in the Page-component use the h1-tag or (possibly) the Heading-component from the design system.
Additional Information
You can check for breaks in heading rules by using the WAVE extension to check the page in your browser.
Tasks
No response
Acceptance Criterias
No response

Sjekket, så bra ut.


make sure test files are cleaned up if tests fail

This change uses addCleanup to make sure that test whisper files are properly deleted if tests fail.

Coverage remained the same at 92.068% when pulling 6bfca43062a1cd1081f8b2acdc5df1ddd48f8412 on test-cleanup into 0360c0d7e0ce964ae690356ccdf00bd4ff261fd3 on master.

:+1:
Flaky tests are annoying.


Some math fonts show misaligned \Bigg\vert when math tagging is active

\DocumentMetadata
{
	testphase={phase-III,math},
	pdfstandard = a-4f,
	pdfversion  = 2.0,
	lang		= en-US,
}
\documentclass[11pt]{article}

\usepackage{unicode-math}

\setmathfont{STIXTwoMath-Regular}[
	Extension = .otf,
	Scale=MatchUppercase,
]
%\setmathfont{texgyretermes-math}[
%    	Extension = .otf,
%    	Scale=MatchUppercase,
%]
%\setmathfont{texgyrepagella-math}[
%    	Extension = .otf,
%    	Scale=MatchUppercase,
%]
%\setmathfont{LucidaBrightMathOT}[%
%	  Extension=.otf,
%	  Scale=MatchUppercase,
%	  BoldFont=LucidaBrightMathOT-Demi.otf,
%]
%\setmathfont{Asana-Math}[
%    	Extension = .otf,
%    	Scale=MatchUppercase,
%]
%\setmathfont{FiraMath-regular}[
%    	Extension = .otf,
%    	Scale=MatchUppercase,
%]
%\setmathfont{GFSNeohellenicMath}[
%    	Extension = .otf,
%    	Scale=MatchUppercase,
%]
%\setmathfont{libertinusmath-regular}[
% 	Extension = .otf,
%	Scale=MatchUppercase,
%	]

\begin{document}
The \verb+\Bigg\vert+ is vertically misaligned when math tagging is active if certain math fonts are loaded.
\begin{equation}
\int_{\Gamma^h_s}\frac{\partial}{\partial n_x}\int_{\Gamma^a_\xi} \mkern-3mu b(\xi) \frac{\partial E(x|\xi)}{\partial n_\xi} \,dl_\xi \Bigg\vert_{x\to s}\,dl_s = 0
\end{equation}
This behavior occurs for Stix2, TeX Gyre fonts,  and Lucida; but NOT for FiraMath, GFSNeohellenicMath, Libertinus, or default LMR.
\end{document}

@u-fischer  the luatex manual isn't exactlyclear but if you force height and depth to be half the requested size rather than relying on axis to shift then it's closer to the intended layout
      \Uvextensible height~#1~ \dimexpr0.5\big@size\relax ~ depth ~#1~  \dimexpr0.5\big@size\relax~ axis~~#2

actually having got clarification in chat axis does not re-centre the entire delimiter on the axis, just interprets height and depth relative to that, so the code you originally showed should have a depth component as well (not clear why it  appears to work in some cases without)

So you can try with definition which should go after \begin{document}
\makeatletter
\ExplSyntaxOn
\cs_set:Npn \bBigg@ #1 #2 {
  {
    \ensuremath {
      \Uvextensible height~#1~ \dimexpr0.5\big@size\relax ~ depth ~#1~  \dimexpr0.5\big@size\relax~ axis~exact~#2
    }
  }
}
\makeatother
\ExplSyntaxOff


Stockholm, Sweden

Adding Stockholm municipality, which is about 10% of Sweden's population.
It has an API that one could query to get all streets in the city, and then all addresses for the street. I am also attaching the script file.
Getting the API key is easily done here: http://openstreetgs.stockholm.se/Home/Key. Put an email in the box on the left and preferably select the WGS 84 coordinate system.
I have not found the reference to a specific license, but I am reasonably sure from the text on the site that it is not share-alike and at most requires attribution.

Fixed the bad header (it had leading spaces in column names). Ready to commit.

Thanks!


Set up LP Dashboard in new validator test network 'sandbox'

Task
Configure and set up apps for the new validator test network 'sandbox'
URL from Fryd https://n01.sandbox.vega.xyz/
Here is the PR they have created for the sandbox genesis https://github.com/vegaprotocol/networks-internal/pull/149
Tasks

[ ] Create .env files
[ ] Create netlify app building from release branch
[ ] Configured required Netlify env vars
[ ] Configure domain for console.sandbox.vega.xyz

Note: LP dashboard doesn't have a custom domain yet

Is this done @pennyandrews

No, I do not believe it is as it doesn't have a domain and we haven't release it to anyone external and therefore it's not needed on the validator sandbox. It should be kept in the backlog but right at the bottom as a reminder we will need to do this at a point we release it, IF it ends up being released as a standalone app. If it gets swept up into the website or other app then this becomes invalid and could be deleted

I dont see why we need this.
Sandbox will probably not have markets on it for the most part.  Can be descoped.

We definitely arent doing this. Closing completely.


Testing

This should make unit-testing significantly faster.

R CMD check results local
From: 3m 55.1s
To: 1m 27.3s


Odf multicluster console plugin deployment

@GowthamShanmugam Looks like this PR depends on K8s version upgrades and other dependencies. I don't see the updates to get new openshift/api , is it a separate PR?

@GowthamShanmugam Looks like this PR depends on K8s version upgrades and other dependencies. I don't see the updates to get new openshift/api , is it a separate PR?

it is done on: https://github.com/red-hat-storage/odf-multicluster-orchestrator/pull/99/files#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6R165

hub could be one of the managedcluster as was discussed in one the DR meetings, then we should add tolerations for ocs nodes (node.ocs.openshift.io/storage)

hub could be one of the managedcluster as was discussed in one the DR meetings, then we should add tolerations for ocs nodes (node.ocs.openshift.io/storage)

This will be added by odf-operator / ocs-operator right?

hub could be one of the managedcluster as was discussed in one the DR meetings, then we should add tolerations for ocs nodes (node.ocs.openshift.io/storage)

This will be added by odf-operator / ocs-operator right?

For multicluster-console deployment, we have to add the tolerations so they can be scheduled on those particular nodes. They won't be added for us by odf-op

hub could be one of the managedcluster as was discussed in one the DR meetings, then we should add tolerations for ocs nodes (node.ocs.openshift.io/storage)

This will be added by odf-operator / ocs-operator right?

For multicluster-console deployment, we have to add the tolerations so they can be scheduled on those particular nodes. They won't be added for us by odf-op

Ok then let me check that, but it is different from this PR

/lgtm

/lgtm

/approve


Identified motifs missing in nanomotif assignment table

Hi,
I have a question regarding the nanomotif output. We used a bacterial isolate as input.
Some of the motifs in the motifs.tsv file don't show up in the nanomotif_assignment_table. I was wondering whether there is a specific reason why they are not in there (e.g. a filtering step?)
I am attaching the nanomotif output files of an example genome.
For example, the motif "CTCGAG" is in the motif.tsv file, but not in the assignment table.
Thank you for your help!
motifs.txt
mtase_assignment_table.txt
nanomotif_assignment_table.txt

The reason for this is that you probably have used the bin_motifs.tsv file (as you should) when executing the nanomotif 'MTase-linker run' command creating the nanomotif_assignment_table. You should see an agreement between the bin_motifs.tsv and the nanomotif_assignment_table.
The key difference between motifs.tsv and bin_motifs.tsv lies in the series of post-processing steps applied to improve the final motifs. For more details on these post-processing steps, refer to supplementary note 1 of our preprint: https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>1623v1
Also, only motifs with a degree of methylation above 50% in bin_motifs.tsv will be included the assignment process. Thus, CTCGAG will not be included since the degree of methylation for this motif is below 50%.

That makes total sense. Thanks for the quick response!

Hi again,
We looked at the data in more depth, and we were wondering if there is a specific reason why the threshold of the "degree of methylation" is set to 50%. We are working with isolates, and we wonder if a methylation of ~30-40 % might also be interesting in this case. Is there a known technical reason why this should not be done?
Otherwise, do you think it might be possible to add an -isolate or -methylation_perc option?
Thank you!

Hi again
I want to clarify that the degree of methylation, that I referred to, was the proportion of motif occurrences in the bin, which are methylated. From literature (Beaulaurier 2019 provided a good review), we know that if a methylation motif is targeted by an MTase, typically >95% of motif occurrences are methylated. This is the reason why we choose this threshold of 50%.
In your case with isolates, looking at methylation degree for a fixed position and motif at the read level is definitely interesting, especially for similar strains. To clarify, for a specific motif on a fixed position in the genome, the degree of methylation of the reads at this position might indicate epigenetic regulation leading to different phenotypes. For instance, in S.enterica, we will observe different serotypes depending on the methylation status of the GATC motifs in the gtr promotor. Nanomotif does not give you the methylation degree of a specific motif on a specific position explicitly yet, however we are working on providing this as an output. Meanwhile you should be able to combine the information from methylation pileup file and bin-motifs file to get the proportion of methylated reads (fraction modified column) for a given motif at a given position (See attached figure)
I hope this answer was helpful.
Sorry for the long answer time


Set Properties ReplyToQ and ReplyToQmgr

Hi,
We have to send a message to the IBM MQ 8 in zOS, for that we create an instance of the IBM MQ <IP_ADDRESS> with the topics that send over the remote queue to the mainframe.
But in the mainframe side, we can't send, or capture, the properties ReplyToQ and ReplyToQmgr.
Have you an idea of how to set this information in the headers ou in the options/properties?
Regards.

Hi @MPBatista and thanks for your question.
This seems like a broker-specific question, so I'd suggest that you post this over on dW answers here with the MQ and zOS tags and an IBM MQ specialist should get back to you with an answer.


Spontaneous Error: npm ls -json -prod -long -all failed with code 1 when running serverless deploy or package

Error: npm ls -json -prod -long -all failed with code 1
    at ChildProcess.<anonymous> (/Users/mishabruml/****/node_modules/serverless-esbuild/dist/utils.js:53:24)
    at ChildProcess.emit (node:events:390:28)
    at ChildProcess.emit (node:domain:475:12)
    at maybeClose (node:internal/child_process:1064:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)

This error started spontaneously with no code or environment changes that i can work out. I have pulled down my master branch, which is working in circleci just fine, but locally I recieve the above error. I am not sure what actually causes this error as the stack trace is unclear. Is it to do with resolving dependencies across monorepo structure? For information, my project looks like:
├── package-lock.json
├── package.json
├── packages
│   ├── common
│   │   ├── src
│   │   ├── package.json
│   │   ├── tsconfig.json
│   │   └── tsconfig.lint.json
│   ├── service-a
│   │   ├── esbuild-plugins.js
│   │   ├── package.json
│   │   ├── serverless.yml
│   │   ├── src
│   │   ├── tsconfig.json
│   │   └── tsconfig.lint.json
│   └── service-b
│       ├── package.json
│       ├── src
│       └── tsconfig.json
├── tsconfig.json
└── tsconfig.lint.json

Where the packages are managed by npm workspaces. It is service-a that is the serverless project.
service-a package.json
{
  "engines": {
    "node": "^16.12.0",
    "npm": "^8.1.0"
  },
  "version": "1.0.0",
  "description": "service-a",
  "license": "ISC",
  "scripts": {
    "tsc:check": "tsc -b --listFiles",
    "eslint": "DEBUG=eslint:cli-engine eslint .",
    "prettier": "prettier . --check",
    "test": "jest",
    "sls:deploy": "SLS_DEBUG=* rm -rf .build && sls deploy",
    "sls:package": "rm -rf .build && sls package"
  },
  "devDependencies": {
    "@aws-sdk/types": "^3.38.0",
    "@emarketeer/esbuild-plugin-tsc": "^0.4.1",
    "@tsconfig/node16": "^1.0.2",
    "@types/aws-lambda": "^8.10.84",
    "@types/http-errors": "^1.8.2",
    "@types/jest": "^27.0.2",
    "@types/node": "^14.17.20",
    "esbuild": "^0.14.18",
    "esbuild-plugin-tsc": "^0.3.0",
    "jest": "^27.2.4",
    "serverless": "^3.1.1",
    "serverless-esbuild": "^1.23.4",
    "serverless-offline": "^8.5.0",
    "serverless-step-functions": "^3.5.1",
    "ts-jest": "^27.0.5",
    "ts-node": "^10.4.0",
    "typescript": "^4.5.5"
  },
  "dependencies": {
    "@faker-js/faker": "^6.0.0-alpha.7",
    "@kafkajs/confluent-schema-registry": "^3.2.0",
    "@middy/core": "^2.5.2",
    "@middy/http-json-body-parser": "^2.5.7",
    "@middy/http-response-serializer": "^2.5.7",
    "@middy/ssm": "^2.5.2",
    "@middy/validator": "^2.5.7",
    "@typedorm/common": "^1.14.9",
    "@typedorm/core": "^1.14.9",
    "@types/convict": "^6.1.1",
    "avsc": "^5.7.3",
    "convict": "^6.2.1",
    "http-errors": "^2.0.0",
    "kafkajs": "^1.15.0",
    "middy-zod-validator": "^1.0.5",
    "reflect-metadata": "^0.1.13",
    "uuid": "^8.3.2",
    "zod": "^3.11.6"
  }
}

service-a/esbuild-plugins.js
module.exports = [
  require("@emarketeer/esbuild-plugin-tsc")({
    force: true,
  }),
];

service-a/serverless.yml
plugins:
  - serverless-esbuild
  - serverless-step-functions
  - serverless-offline

custom:
  esbuild:
    plugins: esbuild-plugins.js
    external:
      - "@typedorm/core"
      - "@typedorm/common"
    sourcemap: true

package:
  individually: true

npm ls -json -prod -all --depth 0 in service-a dir yields:
{
  "version": "1.0.0",
  "name": "service-a",
  "dependencies": {
    "@faker-js/faker": {
      "version": "6.0.0-alpha.7",
      "resolved"<EMAIL_ADDRESS>    },
    "@kafkajs/confluent-schema-registry": {
      "version": "3.2.1",
      "resolved"<EMAIL_ADDRESS>    },
    "@middy/core": {
      "version": "2.5.7",
      "resolved"<EMAIL_ADDRESS>    },
    "@middy/http-json-body-parser": {
      "version": "2.5.7",
      "resolved"<EMAIL_ADDRESS>    },
    "@middy/http-response-serializer": {
      "version": "2.5.7",
      "resolved"<EMAIL_ADDRESS>    },
    "@middy/ssm": {
      "version": "2.5.7",
      "resolved"<EMAIL_ADDRESS>    },
    "@*******/avro-kafkajs": {
      "version": "0.8.1",
      "resolved"<EMAIL_ADDRESS>    },
    "@*******/castle": {
      "version": "0.8.1",
      "resolved"<EMAIL_ADDRESS>    },
    "@sinclair/typebox": {
      "version": "0.23.4",
      "resolved"<EMAIL_ADDRESS>    },
    "@typedorm/common": {
      "version": "1.14.9",
      "resolved"<EMAIL_ADDRESS>    },
    "@typedorm/core": {
      "version": "1.14.9",
      "resolved"<EMAIL_ADDRESS>    },
    "@types/convict": {
      "version": "6.1.1",
      "resolved"<EMAIL_ADDRESS>    },
    "avsc": {
      "version": "5.7.3",
      "resolved": "https://registry.npmjs.org/avsc/-/avsc-5.7.3.tgz"
    },
    "convict": {
      "version": "6.2.1",
      "resolved": "https://registry.npmjs.org/convict/-/convict-6.2.1.tgz"
    },
    "http-errors": {
      "version": "2.0.0",
      "resolved": "https://registry.npmjs.org/http-errors/-/http-errors-2.0.0.tgz"
    },
    "kafkajs": {
      "version": "1.16.0",
      "resolved": "https://registry.npmjs.org/kafkajs/-/kafkajs-1.16.0.tgz"
    },
    "reflect-metadata": {
      "version": "0.1.13",
      "resolved": "https://registry.npmjs.org/reflect-metadata/-/reflect-metadata-0.1.13.tgz"
    },
    "uuid": {
      "version": "8.3.2",
      "resolved": "https://registry.npmjs.org/uuid/-/uuid-8.3.2.tgz"
    },
    "zod": {
      "version": "3.13.2",
      "resolved": "https://registry.npmjs.org/zod/-/zod-3.13.2.tgz"
    }
  }
}

Commenting out the lines

The change I made in the dependency fix PR was adding -long to the npm command. Without it, it was impossible for me to tell if something was deduped in the tree.
I suppose you've possibly tried running npm ls -json -prod -long -all locally?

Yes I have. I have managed to resolve this issue by moving the typedorm dependencies from /common to /service-a, but that isn't ideal

{
  "version": "1.0.0",
  "name": "service-a",
  "engines": {
    "node": "^16.12.0",
    "npm": "^8.1.0"
  },
  "description": "service-a",
  "author": "ovo",
  "license": "ISC",
  "scripts": {
    "tsc:check": "tsc -b --listFiles",
    "eslint": "DEBUG=eslint:cli-engine eslint .",
    "prettier": "prettier . --check",
    "test": "jest",
    "sls:deploy": "SLS_DEBUG=* rm -rf .build && sls deploy",
    "sls:package": "rm -rf .build && sls package"
  },
  "devDependencies": {
    "@aws-sdk/types": "^3.38.0",
    "@emarketeer/esbuild-plugin-tsc": "^0.4.1",
    "@tsconfig/node16": "^1.0.2",
    "@types/aws-lambda": "^8.10.84",
    "@types/http-errors": "^1.8.2",
    "@types/jest": "^27.0.2",
    "@types/node": "^14.17.20",
    "esbuild": "^0.14.18",
    "esbuild-plugin-tsc": "^0.3.0",
    "jest": "^27.2.4",
    "serverless": "^3.1.1",
    "serverless-esbuild": "^1.23.4",
    "serverless-offline": "^8.5.0",
    "serverless-step-functions": "^3.5.1",
    "ts-jest": "^27.0.5",
    "ts-node": "^10.4.0"
  },
  "extraneous": false,
  "path": "/Users/mishabruml/hm/homemoves-monorepo-poc/packages/service-a",
  "_dependencies": {
    "@faker-js/faker": "^6.0.0-alpha.7",
    "@kafkajs/confluent-schema-registry": "^3.2.0",
    "@middy/core": "^2.5.2",
    "@middy/http-json-body-parser": "^2.5.7",
    "@middy/http-response-serializer": "^2.5.7",
    "@middy/ssm": "^2.5.2",
    "@*******/avro-kafkajs": "^0.8.1",
    "@*******/castle": "^0.8.1",
    "@sinclair/typebox": "^0.23.3",
    "@typedorm/common": "^1.14.9",
    "@typedorm/core": "^1.14.9",
    "@types/convict": "^6.1.1",
    "avsc": "^5.7.3",
    "convict": "^6.2.1",
    "http-errors": "^2.0.0",
    "kafkajs": "^1.15.0",
    "reflect-metadata": "^0.1.13",
    "uuid": "^8.3.2",
    "zod": "^3.11.6"
  },
  "peerDependencies": {},
  "problems": [
    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>  ],
  "dependencies": {
    "@faker-js/faker": {
      "required": "^6.0.0-alpha.7",
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@kafkajs/confluent-schema-registry": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@middy/core": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@middy/http-json-body-parser": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@middy/http-response-serializer": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@middy/ssm": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@*******/avro-kafkajs": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@*******/castle": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@sinclair/typebox": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@typedorm/common": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@typedorm/core": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@types/convict": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "avsc": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "convict": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "http-errors": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "kafkajs": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "reflect-metadata": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "uuid": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "zod": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    }
  }
}

node -v v16.12.0
npm -v 8.1.0
I need npm 8 for npm workspaces 😁

Do the external deps you've listed have peerDependencies?

 "node_modules/@typedorm/common": {
      "version": "1.14.9",
      "resolved"<EMAIL_ADDRESS>      "integrity": "sha512-rmLydYjpiYnq2PmotkkfiQCdSTeYRHNRa2bV8nB1PAcY6bKBnsa6ap5xD13T1OzsEl0qUBZBGJmRlIw9ImyvGg==",
      "dependencies": {
        "chalk": "^4.1.0",
        "class-transformer": "0.4.0",
        "debug": "^4.3.1",
        "uuid": "^8.3.1"
      },
      "peerDependencies": {
        "reflect-metadata": "^0.1.13"
      }
    },
    "node_modules/@typedorm/core": {
      "version": "1.14.9",
      "resolved"<EMAIL_ADDRESS>      "integrity": "sha512-xrvPacYZNY0YOja9nO5xxvsUM2AC+toINmL3GBzZAKPj3z76RNrwBLnOmVjWrH2kqYEQ7n3ejQiqscdEIXLz6w==",
      "dependencies": {
        "class-transformer": "0.4.0",
        "fast-glob": "^3.2.4",
        "ksuid": "^2.0.0",
        "p-limit": "^3.1.0",
        "uuid": "^8.3.1"
      },
      "peerDependencies": {
        "@typedorm/common": "1.14.9",
        "aws-sdk": "^2.799.0",
        "reflect-metadata": "^0.1.13"
      }
    },

Hmm since this is locally we might be able to log the error.
In node_modules/serverless-esbuild/dist/util.js can you add: console.log(stdout, stderr) between line 51 and 52 and see what it's yelling about? I have a hunch it's related to peer deps.

Thanks for looking into this. Here is the output. Some redaction due to private repos 😄

> sls:deploy
> SLS_DEBUG=* rm -rf .build && sls deploy

8.1.0

{
  "version": "1.0.0",
  "name": "service-a",
  "engines": {
    "node": "^16.12.0",
    "npm": "^8.1.0"
  },
  "description": "service-a",
  "author": "*****",
  "license": "ISC",
  "scripts": {
    "tsc:check": "tsc -b --listFiles",
    "eslint": "DEBUG=eslint:cli-engine eslint .",
    "prettier": "prettier . --check",
    "test": "jest",
    "sls:deploy": "SLS_DEBUG=* rm -rf .build && sls deploy",
    "sls:package": "rm -rf .build && sls package"
  },
  "devDependencies": {
    "@aws-sdk/types": "^3.38.0",
    "@emarketeer/esbuild-plugin-tsc": "^0.4.1",
    "@tsconfig/node16": "^1.0.2",
    "@types/aws-lambda": "^8.10.84",
    "@types/http-errors": "^1.8.2",
    "@types/jest": "^27.0.2",
    "@types/node": "^14.17.20",
    "esbuild": "^0.14.18",
    "esbuild-plugin-tsc": "^0.3.0",
    "jest": "^27.2.4",
    "serverless": "^3.1.1",
    "serverless-esbuild": "^1.23.4",
    "serverless-iam-roles-per-function": "^3.2.0",
    "serverless-offline": "^8.5.0",
    "serverless-step-functions": "^3.5.1",
    "ts-jest": "^27.0.5",
    "ts-node": "^10.4.0"
  },
  "extraneous": false,
  "path": "/Users/mishabruml/*****/**********/packages/service-a",
  "_dependencies": {
    "@faker-js/faker": "^6.0.0-alpha.7",
    "@kafkajs/confluent-schema-registry": "^3.2.0",
    "@middy/core": "^2.5.2",
    "@middy/http-json-body-parser": "^2.5.7",
    "@middy/http-response-serializer": "^2.5.7",
    "@middy/ssm": "^2.5.2",
    "@*****/avro-kafkajs": "^0.8.1",
    "@*****/castle": "^0.8.1",
    "@sinclair/typebox": "^0.23.3",
    "@types/convict": "^6.1.1",
    "avsc": "^5.7.3",
    "convict": "^6.2.1",
    "http-errors": "^2.0.0",
    "kafkajs": "^1.15.0",
    "reflect-metadata": "^0.1.13",
    "uuid": "^8.3.2",
    "zod": "^3.11.6"
  },
  "peerDependencies": {},
  "problems": [
    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>  ],
  "dependencies": {
    "@faker-js/faker": {
      "required": "^6.0.0-alpha.7",
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@kafkajs/confluent-schema-registry": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@middy/core": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@middy/http-json-body-parser": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@middy/http-response-serializer": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@middy/ssm": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@*****/avro-kafkajs": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@*****/castle": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@sinclair/typebox": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "@types/convict": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "avsc": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "convict": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "http-errors": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "kafkajs": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "reflect-metadata": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "uuid": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    },
    "zod": {
      "missing": true,
      "problems": [
        "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>      ]
    }
  }
}
 npm ERR! code ELSPROBLEMS
npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>{
  "error": {
    "code": "ELSPROBLEMS",
    "summary": "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "detail": ""
  }
}

npm ERR!      /Users/mishabruml/.npm/_logs/2022-03-03T14_33_14_772Z-debug.log

Error:
Error: npm ls -json -prod -long -all failed with code 1
    at ChildProcess.<anonymous> (/Users/mishabruml/*****/**********/node_modules/serverless-esbuild/dist/utils.js:54:24)
    at ChildProcess.emit (node:events:390:28)
    at ChildProcess.emit (node:domain:475:12)
    at maybeClose (node:internal/child_process:1064:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)

This is likely related to https://github.com/serverless-heaven/serverless-webpack/pull/782

thanks a lot for this
hmm. I tried adding
{ npmError: 'code ELSPROBLEMS', log: false } to the ignoredNpmErrors here https://github.com/floydspace/serverless-esbuild/blob/master/src/packagers/npm.ts#L124-L128
but received the same error regardless. this seems to be due to the stringmatching in the error handling function throwing a false negative for the block of JSON that is output to stderr. I am continuing some local testing and may submit a PR 👍
JSON emitted to stderr that needs ignoring:
{
  "error": {
    "code": "ELSPROBLEMS",
    "summary": "missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>required by<EMAIL_ADDRESS>    "detail": ""
  }
}


Number TextField breaks when inputting letters

[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 😯
Inputting a letter makes the text on the top drop down onto the current text:
https://user-images.githubusercontent.com/24500411/103972319-a04b6b80-5121-11eb-82bf-c153e9cc401f.mp4
Expected Behavior 🤔
Either:

The text wont drop down and the letters will be caught by form validation
Letters can't be entered

Steps to Reproduce 🕹

https://codesandbox.io/s/material-ui-issue-forked-3o9f6
Steps:

Create a textfield like this:  <TextField   id="outlined-number"   type="number"   variant="outlined"   margin="normal"   required   fullWidth   label="Testing"   name="Testing"   value={value}   onChange={(e) => setValue(e.target.value)}   autoFocus />

Context 🔦
I'm trying to make a form element that only accepts numbers. (html built-in form validation is fine)
Your Environment 🌎
C:\Users\Evan>npx @material-ui/envinfo
npx: installed 2 in 1.648s

  System:
    OS: Windows 10 10.0.19042
  Binaries:
    Node: 12.18.3 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.423.0), Chromium (87.0.664.66)

I use firefox!

@gubareve This is expected, Firefox fires a change event with an empty string when the content of the field is wrong. See https://next.material-ui.com/components/text-fields/#shrink for the documented solution.

@gubareve This is expected, Firefox fires a change event with an empty string when the content of the field is wrong. See https://next.material-ui.com/components/text-fields/#shrink for the documented solution.

@oliviertassinari This scenario seems quite common, so I would expect it to work better. Do you think it's possible to use HTMLInputElement.validity.badInput object to decide to shrink a field when it contains an invalid number? Maybe that would help.

@oliviertassinari This scenario seems quite common, so I would expect it to work better. Do you think it's possible to use HTMLInputElement.validity.badInput object to decide to shrink a field when it contains an invalid number? Maybe that would help.


[SUGGESTION] Collaboration with other open projects

Hi there,
this project is extremely interesting for all Vegas Pro users - like us - who are accustomed to its excellent GUI and don't have any valid (open source/multiplatform) alternative.
We launched the HyMPS project to support A/V open projects by trying to promote collaboration between developers for mutual evolution.
That's why we've "doxed" TitanVideoEditor too under the VIDEO - Editors - Non-Linear Editors section.
Let us know if we listed it correctly (or if you prefer a different page/section for it) and how we can improve our "collection" for the purposes described above.
Hope that inspires !
Thanks in advance.

Looks great, thanks for noticing my project! My projects don't usually get recognized often lol, right now I'm having a road block with the editor in trying to figure out rendering, with real time decoding for the preview.

We strongly advise you to avoid the "reinventing the wheel" approach: it's just a waste of time and energy and often drives projects to a state of stalemate and sometimes even abandonment.
Check out Video libraries to choose a "consistent" backend that can help you to focus your efforts on the interface rather than technical features of the editor.
Last but not least, as already suggested above, we encourage you to carefully (and deeply) check out other projects in order to get inspiration and/or understand what you can "reuse" from their codebases...
...here's a (visual-only) example:

Hope that helps/inspires !

Right now, I am using ffmpeg to manipulate video, but I think the video libraries you provided will be better for my use case. Thank you for providing me with these libraries, I'll try them out!

Bump (links updated)...
...any news ?

No not really, just kinda moved on onto different projects


pulseaudio: adapt icon names to form factors

Now that the icon is determined based on the form factor (see 8fb3211594ced057025d2b8a9acc1b63a27cb388), it makes sense to adapt the icon names to the string representation of the form factors.
The form factor strings are copied from pulseaudio:
static const char *form_factor_to_string(pa_bluetooth_form_factor_t ff) {
    switch (ff) {
        case PA_BLUETOOTH_FORM_FACTOR_UNKNOWN:
            return "unknown";
        case PA_BLUETOOTH_FORM_FACTOR_HEADSET:
            return "headset";
        case PA_BLUETOOTH_FORM_FACTOR_HANDSFREE:
            return "hands-free";
        case PA_BLUETOOTH_FORM_FACTOR_MICROPHONE:
            return "microphone";
        case PA_BLUETOOTH_FORM_FACTOR_SPEAKER:
            return "speaker";
        case PA_BLUETOOTH_FORM_FACTOR_HEADPHONE:
            return "headphone";
        case PA_BLUETOOTH_FORM_FACTOR_PORTABLE:
            return "portable";
        case PA_BLUETOOTH_FORM_FACTOR_CAR:
            return "car";
        case PA_BLUETOOTH_FORM_FACTOR_HIFI:
            return "hifi";
        case PA_BLUETOOTH_FORM_FACTOR_PHONE:
            return "phone";
    }

Thanks!

I updated the wiki. The default config file in resources/config should also be updated.