python310Packages.azure-mgmt-keyvault: 10.0.0 -> 10.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.azure-mgmt-keyvault is: "This is the Microsoft Azure Key Vault Management Client Library"
meta.homepage for python310Packages.azure-mgmt-keyvault is: "https://github.com/Azure/azure-sdk-for-python"
meta.changelog for python310Packages.azure-mgmt-keyvault is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 10.1.0 with grep in /nix/store/zf7rmhhzl4c71ybas9r0h0mk9i0k4si6-python3.10-azure-mgmt-keyvault-10.1.0
found 10.1.0 in filename of file in /nix/store/zf7rmhhzl4c71ybas9r0h0mk9i0k4si6-python3.10-azure-mgmt-keyvault-10.1.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
azure-cli
python310Packages.azure-mgmt-keyvault
python39Packages.azure-mgmt-keyvault

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zf7rmhhzl4c71ybas9r0h0mk9i0k4si6-python3.10-azure-mgmt-keyvault-10.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.azure-mgmt-keyvault https://github.com/r-ryantm/nixpkgs/archive/d81e29a67e17cdfb7f13bc306fd4095edc0954e1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zf7rmhhzl4c71ybas9r0h0mk9i0k4si6-python3.10-azure-mgmt-keyvault-10.1.0
ls -la /nix/store/zf7rmhhzl4c71ybas9r0h0mk9i0k4si6-python3.10-azure-mgmt-keyvault-10.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

azure-cli
python310Packages.azure-mgmt-keyvault
python39Packages.azure-mgmt-keyvault

Maintainer pings
cc @jonringer @mwilsoncoding for testing.

Result of nixpkgs-review pr 185986 run on x86_64-darwin 1

3 packages built:

azure-cli
python310Packages.azure-mgmt-keyvault
python39Packages.azure-mgmt-keyvault


chore: replace ioutil functions

I also ran go mod tidy, and there's a lot of deletion in go.sum.

Thanks!


Mobs without brains?

Is it possible to setup a method or something to create a passive mob that does NOT respond to anything around them?  Right now we can create mobs (awesome!), but they are based on the game engines for whatever mob you pick,  Be it a spider, creeper, or the default villager.
I appreciate that we have methods to try to freeze the mobs in place, but they still spin around even if you can get them to stand still.
I would like to create a mob that only does what I tell them.  One that requires my code to do anything.
Thanks for such an awesome enhancement to Minecraft!

Or something like on pc the command summon nbt tag NoAi

Awesome!  Added as an enhancement!  Thanks @zhuowei !
I know this is going to help one of my mods, but big time it is going to help the Mechanics mod (cars/bikes/etc.).

added Entity.setImmobile, which completely freezes the entity; will look into disabling the AI portion only.

Thanks!  This is awesome!


fix: namespace for extension-apiserver-authentication rolebinding

Pull Request
What? (description)
Helm chart includes rolebinding which installed in release namespace for role persists in kube-system namespace.
This will not work if chart deployed in separate namesapce
Why? (reasoning)
role extension-apiserver-authentication-reader originally persists inkube-system namespace, the rolebinding must be created in same namespace
related log:
I1010 11:00:48.283722       1 serving.go:348] Generated self-signed cert in-memory
I1010 11:00:48.368155       1 serving.go:348] Generated self-signed cert in-memory
W1010 11:00:48.368198       1 client_config.go:618] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
W1010 11:00:48.680596       1 requestheader_controller.go:193] Unable to get configmap/extension-apiserver-authentication in kube-system.  Usually fixed by 'kubectl create rolebinding -n kube-system ROLEBINDING_NAME --role=extension-apiserver-authentication-reader --serviceaccount=YOUR_NS:YOUR_SA'
unable to load configmap based request-header-client-ca-file: configmaps "extension-apiserver-authentication" is forbidden: User "system:serviceaccount:infra-proxmox:proxmox-proxmox-cloud-controller-manager" cannot get resource "configmaps" in API group "" in the namespace "kube-system"
E1010 11:00:48.680643       1 run.go:74] "command failed" err="unable to load configmap based request-header-client-ca-file: configmaps \"extension-apiserver-authentication\" is forbidden: User \"system:serviceaccount:infra-proxmox:proxmox-proxmox-cloud-controller-manager\" cannot get resource \"configmaps\" in API group \"\" in the namespace \"kube-system\""

Acceptance
Please use the following checklist:

[ ] you linked an issue (if applicable)
[ ] you included tests (if applicable)
[x] you linted your code (make lint)
[x] you linted your code (make unit)

can you change the chart version to  0.1.7


Event cancellation doesn't work right

When cancelling an event, I get in Outlook 365 a "not supported calendar message.ics" attachment, which cannot be opened in order to remove the event from the calendar.

I verified that the ICS contents are valid using a couple of online validators, and it passed validation.
I tried all the methods mentioned here:
https://stackoverflow.com/questions/27662899/outlook-365-receives-a-message-that-has-an-attachment-that-is-named-not-support
But nothing helped.
Currently, my suspicion is that this happened because I used a SendGrid account to send the event cancellation, which may have been detected as a sender other than the organizer.
I should test this on a new event created directly from a non-SendGrid account.

The same problem still occurs even when sending from a Gmail account, and when sending from a personal Microsoft account.
I'm currently at a loss. I have no idea why this is happening.

Not sure if you are still supporting this, but I found that changing the name of the ics file from Meeting.ics to invite.ics caused the cancel mail to work.

Wait, seriously? That easy? I'm gonna try this myself ASAP

Not sure if you are still supporting this, but I found that changing the name of the ics file from Meeting.ics to invite.ics caused the cancel mail to work.

I tried making the change but I'm still getting the same issue with the "not supported calendar message.ics" attachment.
I pushed the changes to the v2.4 branch. Are you sure about this solution?

You are correct.  I was getting it to work when I was sending the invite attachment from gmail.  If I send it from the SQL server to my outlook account, it is giving the same error.

For reference, I generated a calendar invite using the native Outlook web-based interface and then cancelled it.
I captured the attached invite.ics file that arrived with the cancellation, and I'm adding it here:
invite.zip
I don't have the time to do it right now, but I should compare this file's contents to the contents generated by my CLR method, and take note of the differences. Maybe I'll find something.


add localizations?

how can i add Breadcrumb translations?

It is not possible at the moment, PRs are welcome though, it shouldn't be that hard to implement. If I get the time for it I'll do it.
Duplicate of #28

One thought I have to accomplish this, although kludgey, would be to have the route for each endpoint have language specific routing (ie "/en/account" vs "/es/cuenta", etc.) and have the breadcrumb use them in conjunction with the correct language translations).
However it seems to me that really, the most direct (.net) way would be to add an additional optional argument to the breadcrumb attribute to pass in the name of the resource resolver.  That way your doing translations using the same key, but getting the correct translated value back.


Reduce plot size

Where
"Productivity index" plot
What
Reduce vertical size from 8/10 of the screen to about 6/10.

Fixed by cc96337


bump metrics to 0.23, and attendant metrics-exporter-prometheus

i tested locally and things are passing

Thanks, but it's already in #52, which I'm planning to work on and merge soon.


RFE: Network Rules Interface

Rancher version:
2.2.2
Description:
We have to open firewall holes to external resources for specific applications, but because those rules are for all nodes, technically all pods have access to that resource. We need a way to secure network rules per project, namespace, deployment, etc. Right now we are looking at buying Twistlock for this, but having it built into Rancher would be a huge value add.
I think this would go along with the security theme for Rancher 2.3

Implementing an interface is a start but we will also have to provide a way to either feed these rules to a runtime security tool (like Aqua/Twistlock) or to provide such capability from within Rancher.
I think we can address this if (or when) we enable runtime security within Rancher.


Code Samples

It would be beneficial for exhibition to be able to generate sample code from the exhibition definition.
At first, we can just use the exhibit content directly. Potential improvements include replacing context.parameter(...) with the default value for each parameter.
These snippets should be able to be selected + copied for use in a project.

Explorations in mjarvis/docs including an extremely naive proof of concept that pulls the sample via sourcery from defaultValue in type.staticVariables where name == "exhibit"


How to use bulkCreate

How to use bulkCreate

Like you normally would, without calling .cache() first.


fix: omit setting style title for sld 1.1.0

This omits setting the style title for sld 1.1.0 since this element does not exist in that version. This also does not derive the name from the title but rather from the name element.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add fuzzing to CI

This is currently broken because of #3536

It looks like https://github.com/mozillasecurity/fuzzdata.git/trunk/samples/h264 can't be accessed. @tysmith do you know what might be going on here?

@jschwartzentruber is taking a look

This should be fixed by https://github.com/google/oss-fuzz/pull/11207

This should be fixed by google/oss-fuzz#11207

Right, so someone should update the fuzz job here in this repo as well, to do something similar?

Nope, things should just work now.

Nope, things should just work now.

Hmm, I just retried a job, and it failed again: https://github.com/mstorsjo/openh264/actions/runs/6796632625/job/18542284463
+ svn export https://github.com/mozillasecurity/fuzzdata.git/trunk/samples/h264 corpus/
svn: E170013: Unable to connect to a repository at URL 'https://github.com/mozillasecurity/fuzzdata.git/trunk/samples/h264'
svn: E215004: No more credentials or we tried too many times.
Authentication failed

The above PR has not been merged yet.

The above PR has not been merged yet.

Ah, I see - sorry for the too hasty conclusion.

Ok, now this seems to work again. Thanks!


Excelexport

Current coverage is 47.04%

Merging #178 into master will decrease coverage by -0.86% as of b4e621c

@@            master    #178   diff @@
======================================
  Files           20      20
  Stmts          311     321    +10
  Branches         0       0
  Methods          0       0
======================================
+ Hit            149     151     +2
  Partial          0       0
- Missed         162     170     +8

Review entire Coverage Diff as of b4e621c

Powered by Codecov. Updated on successful CI builds.


CL-468 Split language list

Objective
Split language list, clean-up.
Description
Non-breaking changes!

The Language list was split into two new lists, the origin one is unchanged.

This action was needed to use ISO languages without the non-ISO languages like AUTO etc.

Introduce LanguageConfig to avoid type assertions.
Fix some typos.

Acceptance
No test needed, non-breaking changes.
Checklist

[ ] I have added relevant info to the CHANGELOG.md

Splitting the list of languages into two sublists (ISO + non-ISO) can be useful in some aspects, but here nothing is done with these two separated lists, apart from later concatenating them into one. They could be exported if that's needed.
Apart from that, this PR is breaking because TS no longer recognizes the elements inside of the language object (see comments in code)

The ISOLanguage is exported, I have just add export also for non-iso language.
The type change is non-breaking, the language objects is recognizable by TS, explicit assertion as it was used is equal to the changes I have done.

The ISOLanguage is exported, I have just add export also for non-iso language.
--> My bad, i missed that.

For the typing, completion with my version:

Vs completion in your version:

Trying to access an inexisting language in my version:

Vs trying to access an inexisting language in your version:

So no, the two typings are definitely not equivalent.

BTW, I do get that you thought your typing would work, no worries with that. What worries me a bit more is that you took the time to make quite a lot of changes, but those changes:

don't make the cleaner or easier to maintain
don't make it run faster
don't add any feature

If it's not broken, don't fix it, because here you are just breaking it.

The ISOLanguage is exported, I have just add export also for non-iso language.
--> My bad, i missed that.

For the typing, completion with my version:
Vs completion in your version:
Trying to access an inexisting language in my version:
Vs trying to access an inexisting language in your version:
So no, the two typings are definitely not equivalent.

My mistake, autocomplete is indeed broken and there is no clean way how to fix it, so I have reverted it.

To be fair, I am not 100% happy with repeating as LanguageInfo for every entry either. I think it sux that TS does not see it automatically. The version you tried is the first thing I tried too, because it made sense, but after pulling my hair on why is completion not working, I decided to go for the current way...

To be fair, I am not 100% happy with repeating as LanguageInfo for every entry either. I think it sux that TS does not see it automatically. The version you tried is the first thing I tried too, because it made sense, but after pulling my hair on why is completion not working, I decided to go for the current way...

Easiest way is to type Language with { [key in keyof typeof ISOLanguage | keyof typeof NonISOLanguage]: LanguageInfo }.

Hum.. maybe, I'd have to try. I guess since both ISOLanguage and NonISOLanguage are declared as const, then that could work. But then you would not have a nice working completion on ISOLanguage and NonISOLanguage.

Hum.. maybe, I'd have to try. I guess since both ISOLanguage and NonISOLanguage are declared as const, then that could work. But then you would not have a nice working completion on ISOLanguage and NonISOLanguage, which we are also exporting.

Unfortunately yes, so keep types as they are.


[SPARK-25262][K8S][2.4] Allow SPARK_LOCAL_DIRS to be tmpfs backed on K8S

What changes were proposed in this pull request?
This is a backport of changes from SPARK-25262, PR #22323
I plan to also backport SPARK-28042, PR #24879 after this is landed. That diff will also include a test confirming that related issue SPARK-31666 is fixed.
I had originally submitted both as a single PR, but have decided to close that PR and open 2 smaller ones per the recommendation of @dongjoon-hyun . See #28982 for more details.
Why are the changes needed?
Running Spark on Kubernetes and not being able to use mounted volumes as local storage causes issues that prevent Spark jobs from starting. I've seen this on AWS EKS, but I've been able to reproduce it with a basic spark-submit command on a standard K8S cluster. Upgrading to 3.0 just to fix this bug is more hassle than it's worth for some organizations.
Does this PR introduce any user-facing change?
Technically, yes. This adds the spark.kubernetes.local.dirs.tmpfs back to Spark 2.4 from Spark 3. However, there's no "breaking changes" per se.
How was this patch tested?
The tests were backported. Also, we've been running our own custom Spark 2.4.5 build with this patch applied at my org for the past few months.

As best as I can tell, both patches are required for fixing SPARK-31666. My plan was to add the additional unit test in the PR for backporting SPARK-28042. If I add the additional unit test to this PR, it will fail.

I closed SPARK-31666 as Not A Problem because Apache Spark 2.4's SPARK-23529 is not designed for the duplicate volume name. It works as designed and your configuration is not supported by Kubernetes.

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Added Mavlink command reception support

I have added Mavlink command reception for my personal use as it does not seem to be implemented yet.
I share it here in case someone is interested.

Yes, as you could guess, I am receiving commands on multiple plugins, I filter the target system and component ID, handle the command and send back a CMD_ACK. For instance, non-mavlink cameras directly connected to a companion computer with a running MAVSDK application, each camera having a different component ID and a separate instance of my custom plugin. When the plugin receives the command, it filters the system and component ID, trigger the user callback and send a CMD_ACK.
One thing I should have done here, is to filter the target system ID before calling the plugin callback, i.e. at the MavlinkCommands level.
Moreover, the CMD_ACK could also be sent from the MavlinkCommands class, according to the plugin callback result, ensuring we send an ack for each command received.
As you said, my changes have nothing to do with the existing MavlinkCommands, and it could be split in 2 classes. I cannot tell you which choice is the best, both suit me well.

As you said, my changes have nothing to do with the existing MavlinkCommands, and it could be split in 2 classes. I cannot tell you which choice is the best, both suit me well.

I like @julianoes' idea of having MavlinkCommandReceiver and MavlinkCommandSender, if that's easily feasible :+1: :blush:.

@yhabib29 do you have time to continue and finish this in the mean time? Any time window you can provide? Thanks!

Continued in https://github.com/mavlink/MAVSDK/pull/1236.

Thanks @yhabib29, it will come in with #1236.

Thanks @TSC21 for your work, I just saw your message today ...


Problems at Scientifica font.

Right one is Liga scientifica and left one is normal scientifica.

Hi! Could you git checkout at branch issue-1 and build it again? I tested the font in some emulators and got the spacing glitch too.

It works now, thanks! :-)


Requirements for making tss-react compatible for Material-UI makeStyles replacement

Following up on our discussion started in https://github.com/mui-org/material-ui/issues/26571 about how we can make tss-react compatible as a replacement for the makeStyles API for v5. I've done some initial testing. Here are some thoughts:
SSR
Have you tried to configure nextjs to work with tss-react? It uses @emotion/css so I believe some extra steps would be required. This would be the first requirement so that we could use it together with material-ui. Our docs (the Material-UI's) can be a good candidate for testing this out.
API suggestions
Here are some suggestions regarding the API itself:
I wouldn't return named options, if there is only one option returned. For example:
-const { createUseClassNames } = createUseClassNamesFactory({ useTheme }); // createUseClassNames is the only option
+const makeStyles = createUseClassNamesFactory({ useTheme });

-const { useClassNames } = createUseClassNames()(
+const useStyles = makeStyles()(
  (theme)=> ({
    root: {
      color: theme.palette.primary.main,
    },
  })
);

With this, we can actually make the API closer to the v4 makeStyles API. We could overcome this by adding adapters, but I will leave it to you.

Question: Is it really necessary to invoke function createUseClassNames() and then propagate the input to the next function call? What are the arguments required there? Can it be omitted?

I am open to help and move this forward :)

Thanks for reaching out.
I am working now but I will check this out tonight!

This is a tiny but helpful package. It would be great if we can integrate it as one of the default style options in MUI, applying exactly the same interface as what JSS supports in V4 and keep maintenance the code within MUI repo.

Hi @mnajdova,

SSR
Have you tried to configure nextjs to work with tss-react? It uses @emotion/css so I believe some extra steps would be required. This would be the first requirement so that we could use it together with material-ui. Our docs (the Material-UI's) can be a good candidate for testing this out.

I haven't tested it yet. I can make time for that on the week-end.
Is this still true?

Question: Is it really necessary to invoke function createUseClassNames() and then propagate the input to the next function call? What are the arguments required there? Can it be omitted?

Yes, it unfortunately is nessesary to get the type inferrence working.
The root of the problem is that TypeScript doesn't support partial argument inference.
In other word we can't have a generic function with two type argument, specify one and let the other be inferred.
Consider this example:
 createStyles<"root" | "label", { color: string; }>({
    "root": {
        "backgroundColor": "blue"
    },
    "label": ({ color })=>({
        color
    })
})

We shouldn't have to explicitly provide "root" | "label" it should be inferable from the object passed in argument.
But because we have to specify { color: string; } we have to put "root" | "label" as well.
The only way to circumvent this limitation is to use the higher order function pattern as implemented in tss-react.

API suggestions
Here are some suggestions regarding the API itself:
I wouldn't return named options, if there is only one option returned. For example:
-const { createUseClassNames } = createUseClassNamesFactory({ useTheme }); // createUseClassNames is the only option
+const makeStyles = createUseClassNamesFactory({ useTheme });

-const { useClassNames } = createUseClassNames()(
+const useStyles = makeStyles()(
  (theme)=> ({
    root: {
      color: theme.palette.primary.main,
    },
  })
);

With this, we can actually make the API closer to the v4 makeStyles API. We could overcome this by adding adapters, but I will leave it to you.

Well, I am very passionate about this topic. Let me make my case and if you aren't convinced I'll make the API changes, even if I think it's a mistake, because I'd like this colab to go through.
First, I believe it's almost always better to return results of functions wrapped into an object, even if there is only one result. The reasoning behind that is that a large part of a developer's job is to give meaningful and consistent names to things.
By providing the results with a default name, we switch the responsibility of finding a suitable name from the API users to the API designer.
This is huge for consistency and quality of life for developers.
What happen in practice if you don't do that is that users either refer to documentation examples every time or come up with uninspired names.
On the other hand, this kind of flow is only possible with named returns:

Maybe it is more critical for me than for others because I am dyslexic but I know I am knot the only one for whom this pattern is life changing.
Beside I am convinced that we should ditch the old naming scheme: makeStyles -> useStyles -> classes it is arbitrary and inconsistent, createUseClassNames -> useClassNames -> classNames make much more sense although being a bit longer.
I understand the willingness to keep the naming familiar but users will have some refactoring to do if they want to switch from the V4 hook API to TSS . It's now or never the time to ditch the legacy naming scheme.
How do we avoid emotion to be included twice
As mentioned here I think it would be important to provide a way to reuse the part of emotion that material-ui v5 includes by default instead of including another copy of emotion.
It is already possible not to include emotion twice assuming the project already depends on @emotion/css but Material-UI v5 depends on @emotion/react and @emotion/styled we should find a way to reuse that, don't you think?
Best regards

SSR
Have you tried to configure nextjs to work with tss-react? It uses @emotion/css so I believe some extra steps would be required. This would be the first requirement so that we could use it together with material-ui. Our docs (the Material-UI's) can be a good candidate for testing this out.

I haven't tested it yet. I can make time for that on the week-end.

I will set up a simple repository to test this out, and we can see if there are some problems. From the initial try on the Material-UI docs it did not work, but it would be simpler to reproduce on a clean slate.

Is this still true?

Yes

Yes, it unfortunately is necessary in order to get the type inference working.
The root of the problem is that TypeScript doesn't support partial argument inference.
In other word we can't have a generic function with two type argument, specify one and let the other be inferred.
Consider this example:
 createStyles<"root" | "label", { color: string; }>({
    "root": {
        "backgroundColor": "blue"
    },
    "label": ({ color })=>({
        color
    })
})

We shouldn't have to explicitly provide "root" | "label" it should be inferable from the object passed in argument.
But because we have to specify { color: string; } we have to put "root" | "label" as well.
The only way to circumvent this limitation is to use the higher order function pattern as implemented in tss-react.

It's unfortunate that the API needs to suffer because of TypeScript limitation :( In Material-UI we have a similar createStyles function https://github.com/mui-org/material-ui/blob/next/packages/material-ui-styles/src/createStyles/createStyles.d.ts but it can be used optionally: https://next.material-ui.com/guides/typescript/#using-createstyles-to-defeat-type-widening Would be great if we can do something similar here. I believe it is used for the same exact reason.
Regarding the API changes :)

Beside I am convinced that we should ditch the old naming scheme: makeStyles -> useStyles -> classes it is arbitrary and inconsistent, createUseClassNames -> useClassNames -> classNames make much more sense although being a bit longer.
I understand the willingness to keep the naming familiar but users will have some refactoring to do if they want to switch from the V4 hook API to TSS. It's now or never the time to ditch the legacy naming scheme.

I understand your point, looking from Material-UI perspective, if the API stays as it is at the current moment, we will need to create an adapter so that we can keep the same API as in v4. We are considering adding back the makeStyles partially so that we can ease up the migration (together with the other benefits it has), so adding more changes to it, won't help with it.
If there are other reasons for adding adapter, then it may be fine, but int he end it would be great if we can keep the same API :)

Will link here later today/tomorrow the repository where we can test the integration.

@mnajdova Thank you for setting up the next.js repo and for the rapid feedback.
I will get back to it ASAP.

In Material-UI we have a similar createStyles function https://github.com/mui-org/material-ui/blob/next/packages/material-ui-styles/src/createStyles/createStyles.d.ts but it can be used optionally: https://next.material-ui.com/guides/typescript/#using-createstyles-to-defeat-type-widening Would be great if we can do something similar here. I believe it is used for the same exact reason.

Ok there is something that I want to point out.
The API of TSS and the one of makeStyle are different beyond the naming conventions.
const { useClassNames } = createUseClassNames<{ color: string; }>()(
  (theme, { color })=> ({
    "root": {
        "backgroundColor": theme.palette.primary.main
    },
    "label": { color }
  })
);

const useStyles = makeStyles(
  theme => createStyles<"root" | "label">, { color: string; }>({
    "root": {
        "backgroundColor": theme.palette.primary.main
    },
    "label": ({ color })=>({
        color
    })
  })
);

Notice how with TSS we get color alongside the theme rather that with makeStyles we get it as argument of the label property. I made this change so we don't need the createStyle anymore.

I believe it is used for the same exact reason

createStyles was introduced to cope with the fact that the API, as designed in JSS is hard to type right. Notice however that createStyles doesn't solve the problem we have of having to enumerate "root" | "label" that should be inferable.

It's unfortunate that the API needs to suffer because of TypeScript limitation :(

Regardless, I think we should optimise the user experience for TypeScript, not for vanilla JS.

In Material-UI we have a createStyles would be great if we can do something similar here.

...we can't, it's technically impossible as of TypeScript v3.4.5

If there are other reasons for adding adapter, then it may be fine, but int he end it would be great if we can keep the same API :)

Actually there is one. Currently the API TSS has no support for composition as JSS see this issue. This is the solution I plan to implement latter this week.

As mentioned here I think it would be important to provide a way to reuse the part of emotion that material-ui v5 includes by default instead of including another copy of emotion.
It is already possible not to include emotion twice assuming the project already depends on @emotion/css but Material-UI v5 depends on @emotion/react and @emotion/styled we should find a way to reuse that, don't you think?

Some though? It seemed to be important for @oliviertassinari, but if you don't mind bundling an other copy of @emotion/css, I don't 😄
Best regards.

We now have a polyfill the css function of @emotion/css using @emotion/react.

Meaning that TSS will be able to reuse the version of emotion bundled in @material-ui/core v5.
Focusing on getting things to work on SSR. @mnajdova you have been of great help so far.
Best regard

@garronej I feel like we can close the issue, I don't see some blockers at this moment. As mention in https://github.com/mui-org/material-ui/issues/26571#issuecomment-878641387 we are going to promote tss-react as the emotion's equivalent to the makeStyles API. If other developers find issues, it would be better to open new ones that will be more focused on a specific problem.

Well, I am very passionate about this topic. Let me make my case and if you aren't convinced I'll make the API changes, even if I think it's a mistake, because I'd like this colab to go through.
First, I believe it's almost always better to return results of functions wrapped into an object, even if there is only one result. The reasoning behind that is that a large part of a developer's job is to give meaningful and consistent names to things.
By providing the results with a default name, we switch the responsibility of finding a suitable name from the API users to the API designer.
This is huge for consistency and quality of life for developers.
What happen in practice if we don't do that is that users either refer to documentation examples every time or come up with uninspired names.

No it's not right to return always an object when we want to return a single value; IMO this is a bad practise. End users must have a direct freedom to name things as they want, we should not create things just having in mind beginners that will make up weird names, teams and experienced developers will always be consistent regarding the names they're using. A library shouldn't care what internal names a project will use. Most users and especially beginners, will always read the documentation when they'll start to learn how to develop (using MUI for example) so they'll see what naming convention the framework is using.
An other awkward thing about this is when we want to create multiple useClassNames or multiple useStyles, then we're forced to do ugly destructuring renaming like:
const { useClassNames: useComp1ClassNames } = createUseClassNames(...)

const { useClassNames: useComp2ClassNames } = createUseClassNames(...)

const { useClassNames: useComp3ClassNames } = createUseClassNames(...)

instead of:
const useComp1ClassNames = createUseClassNames(...)

const useComp2ClassNames = createUseClassNames(...)

const useComp3ClassNames = createUseClassNames(...)

Libraries should not be opinionated regarding naming conventions and should not enforce any king of end naming.

Well... we have conflicting views.
I think the DX is better if we can deconstruct the returned value. I prefer not having to wonder, "what is this supposed to be called again?" it distracts me from the important things.
Beside it doesn't enforce the end naming, it's just a suggestion, you find the syntax for renaming awkward, I'll admit it's a bit verbose but a vast majority of people will always want the standard name, especially for a hook that have to start with use.
That's said, I am willing to make the following API changes if there is a clear consensus in this direction.
-const { useStyles } = makeStyles()(...);
+const useStyles = makeStyles()(...);

@clytras, on a personal note, your peremptory tone did rub me the wrong way. Feel free to express your opinion, it is taken into consideration but please, be polite.

@garronej what exactly wasn't polite and with a "peremptory tone" regarding my comment? That I told you that "it's not right to return always an object when we want to return a single value" or "IMO this is a bad practise"?
I'm trying to make you rethink of something that it's obsiously wrong; Yeah, maybe I should have written "please reconsider the usage of this BAD practise" but I believe you're getting the point and I have no intention to insult you nor offend you in any way.
It's not a hook, it is a function that it creates a hook and that makes a huge difference because it's very likely that there might be multiple hooks in the same file, it's not a standard hook like useState or useEffect; people will use a function to create it and they should have the freedom to name it without the need of extra destructuring syntax.
There are cases that we need to return an object even if we have a single value to return, like for example the useRef hook that it always return an object because we need that ref of that object to be immutable while to hold something in the current property that it shall be mutated. In the makeStyles hook generator we don't have such a need.

I prefer not having to wonder, "what is this supposed to be called again?" it distracts me from the important things.

Developers won't have to wonder when they see how it's done in the examples and tutorials which they will dive, read and follow when they are about to learn something. IMO creating such an opinionated behaviour only adds syntactic noise and it doesn't add much regarding DX.

you find the syntax for renaming awkward, I'll admit it's a bit verbose but a vast majority of people will always want the standard name

It is awkward when I want to create 3, 4 and many hooks to destructure a repetitive name like this; remeber here we don't have a standard hook, but we're creating new hooks and there might be many of them.
Please reconsider the usage of this and please don't take my words personal; I don't know you, the there no intention for any offence.

I shouldn't have took your words personally, as I said I am very passionate about this issue. 😅
It's not my place to assert how the lib should be used maybe you have a valid use case where it make sense to declare multiple useStyle side by side, it's just that I don't see it, maybe if you link me the code it would convince me.
Also, I stress that named return is an accessibility features. We are not all equals regarding what we can remember, a lib that only requires to remember concepts and not naming conventions is way more friendly to people with ADHD and beginners.
That said your point was upvoted twice, @mnajdova also suggested this change and it was like that in @material-ui v4 so
I will probably do it.

This PR https://github.com/DimensionDev/Maskbook/pull/3745/files gives an interesting overview of the feasibility to move from @material-ui/styles to tss-react.


Typo in the Official Documentation

Proposed feature
There is a typo on the Atala Prism documentation page link under Operating an agent with secrets.
Feature description
The typo is HachiCorp Vault, but I believe it was meant to refer to HashiCorp Vault.
Anything else?
No response

Thanks for reporting, we're on it!

No problem.

Fixed by https://github.com/hyperledger-labs/open-enterprise-agent/pull/886


Update pattern

This looks to address most of the issues I noted here: https://github.com/insin/react-maskedinput/issues/8#issuecomment-125251570
Perhaps if this could get rebased against master (squashing the commits) this could be a contender for being really close for a fix to #8 \o/
See https://github.com/insin/react-maskedinput/issues/8#issuecomment-125538427 for the one remaining nit. Going from a short pattern to a longer pattern via paste, the selection is not at the the end of the string. We can probably look at fixing that separately in any case.

@muffinresearch You got it.

@insin would you have some time to take a look at this patch in relation to #8 ?

Hmm not sure what's happening but the dist file looks to be out of date e.g. it's missing the componentWillReceiveProps that's in the .jsx flle. Also testing the changes I'm no longer seeing pattern updates rendering. Can you see if still works for you?

Hey, just grabbed this one to see if it fixed my issue - PR has issues with pattern vs match so the following code snippet is the fixed version of the code (No time to make PR sorry). AFAIK this works for all issues in #8 as well (didn't extensively test though).
componentWillUpdate(nextProps, nextState) {
    if (nextProps.mask !== this.props.mask) {
      this._updatePattern(nextProps)
    }
  },

  componentDidUpdate(prevProps) {
    if (prevProps.mask !== this.props.mask && this.mask.selection.start) {
      this._updateInputSelection()
    }
  },

  _updatePattern: function(props) {
    this.mask.setPattern(props.mask, {
      value: this.mask.getRawValue(),
      selection: getSelection(this.input)
    });
  },

Closed by #53


Remove lodash dependency from build script

As discussed in #1555, this PR refactors the scripts/build.js script to not be dependent on lodash, since it fails on projects running on node@4 that have both lodash and the latest bookshelf version as dependencies.
Closes #1555

LGTM!
How about you @Playrom ?

Sorry it has a bug, let me fix and I'll let you know when's ready to review.

correct the bug, update the PR and I think we can merge
I think it's preferable to have a correct installation procedure then the presence of some checks

My bad guys, done!

👍

Thanks! Any idea of how far are you from making a new release?

I think we are going to publish a new release really soon, to fix all the bug fixes merged in the last month
And we'll start an open call for feature and help in the development really soon! stay tuned :)


Fix csv for utf8mb4

On MySQL, in order to store Emoji in the database, one must use utf8mb4 encoding. Yet, this encoding was not present in the list of UTF8_ENCODINGS, so the export fails with
ArgumentError: unknown encoding name - utf8mb4

The build has failed but as far as I can tell, this is unrelated to my changes.

Closing in favor of #2270.


hide the thumbv* target files

due to how Cargo works, the rustc-cfg in build.rs was picking our target
specifications rather than the one the user meant to use. Placing our
target files in any place other than the root of the Cargo project
avoids the issue.

@homunkulus r+

:pushpin: Commit 0827f8c has been approved by japaric

:hourglass: Testing commit 0827f8c with merge 0827f8c...

:sunny: Test successful - status-appveyor, status-travis
Approved by: japaric
Pushing 0827f8c7f131c95ae9747c0639c1b89070f6c94a to master...


Fix failing travis test

https://travis-ci.org/emerald-rubies/tenacious#L606
Webpacker requires Yarn version >= 0.20.1. Please download and install the latest version from https://yarnpkg.com/lang/en/docs/install/

I came across this problem on a project I started last week. Below is my install block in .travis.hml.
install:
  - bundle install
  - nvm install node
  - node -v
  - npm i -g yarn
  - yarn

Adding that fixed the failing travis test for me.

I'm guessing that changed the container base and that's what's causing the
issue. bin/setup takes care of a lot of that, but before that step, simply
line 5 might fix it. On automated things, please use the explicit "install"
though.
On Mon, Aug 7, 2017, 11:26 AM Troy Starwalt<EMAIL_ADDRESS>wrote:

I came across this problem on a project I started last week. Below is my
install block in .travis.hml.
install:

bundle install
nvm install node
node -v
npm i -g yarn
yarn

Adding that fixed the failing travis test for me.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/emerald-rubies/tenacious/issues/102#issuecomment-320711818,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGaPS5XGjOUT9Jj22Hfn-h0hhHK2MUyiks5sVzqsgaJpZM4Ou9BJ
.

@troystarwalt Were you offering to fix this or just pointing to a possible fix?


Validate enthalpy-porosity model with water freezing benchmark

@article{michalek2003simulations,
title={Simulations of the water freezing process--numerical benchmarks},
author={MICHA{\L}EK, TOMASZ and KOWALEWSKI, TOMASZ A},
journal={Task Quarterly},
volume={7},
number={3},
pages={389--408},
year={2003}
}

Validated as of cc94d0cdb05d140d4840b0bd0f4f8966e1ce5dba


Add ability to publish to telegram

The idea is to use telegram as an optional destination for any given feed.

note: https://core.telegram.org/bots/api#sendaudio
An audio file is limited to 50M. There are a few ways to deal with this:

detect file size and if above 50m post a link
always publish links (to mp3) only
figure a way to publish large files directly to telegram and link them

I see this as a telegram bot subscribes for RSS feed and post it to the channel, there are tons of such bots tho.. Am I wrong? What do you have in mind?

Am I wrong? What do you have in mind?

I have in mind not just publishing RSS item but retrieving an enclosed file and publishing mp3 to telegram as well, if possible. I think my comment above describes it clear enough.

[Telegram боты. Загружаем файлы больше 50мб] (https://habr.com/ru/post/348234/)


Allow a permissions boundary to be attached

...as these things are useful, but must be attached to the role at
creation.

/codefresh run test

@rsrchboy Looks good, but please rebuild README by executing these commands:
make init
make readme/deps
make readme

It will add the new variables and outputs to README.md automatically.
In general, any changes to README should be made in README.yaml (not in this case), and after that executing the commands above will rebuild README.yaml into README.md and add all new variables and outputs to README.md
Also, please, run terraform fmt to properly format variables.tf
thanks

/codefresh run test


#Peer-To-Peer-Code-Review

Hello Ackon 😊
I can see that you have done a good job 👏
Cheers and Happy Coding 👍

Hi Ackon, Great job :clap:

Your website looks awesome :+1:
I really like the way you implement your navbar :1st_place_medal:

But I do have some subjection for you

It will be nice to notify the user when the book has been added successfully
I think it will be good to prevent the user to add a book when one of the fields is empty. what do you think?


Add Commands::Graph.build and extend Env#command to support it

TODO

[x] make it possible to use as just like with a normal command
[x] move stuff to Graph::ClassInterface for consistency
[x] add docs

Changes Unknown when pulling bd4757e26e69f20a7cb6dbc2832778e08c446990 on command-graph-builder into ** on master**.

O_o
On Fri, 10 Feb 2017 at 13:41, Coveralls<EMAIL_ADDRESS>wrote:

[image: Coverage Status] https://coveralls.io/builds/10090602
Changes Unknown when pulling bd4757e
https://github.com/rom-rb/rom/commit/bd4757e26e69f20a7cb6dbc2832778e08c446990
on command-graph-builder into ** on master**.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rom-rb/rom/pull/247#issuecomment-278912466, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAw-tqKqMZ1empB2n6jZBZuUF10GhRzPks5rbD7xgaJpZM4EvCOU
.

lol wat :D


Fix wrong file size return if there's no Content-Length returned

Some webdav server, e.g., apache, does not return content-length header when the file size is zero.

mvn test:
Results :
Tests run: 170, Failures: 0, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15.425 s
[INFO] Finished at: 2015-07-22T15:29:29+08:00
[INFO] Final Memory: 14M/158M
[INFO] ------------------------------------------------------------------------

OK, I'm fine with this going in as long as there is an accompanying FileLengthCommandTest for this case, can you please add that to the PR?

@massdosage the PR is updated. :octocat:

@hrchu - ok, looks good, feel free to merge this one!


services/obs: Service test failed for content mismatch

Related PR: https://github.com/beyondstorage/go-storage/pull/957
Test Case: https://github.com/beyondstorage/go-storage/runs/3982686814?check_suite_focus=true

     When Read a file with offset or size
      When Read with offset
        The error should be nil ✔✔
        The content should be match ✔✘✔
      When Read with size
        The error should be nil ✔✔
        The content should be match ✔✘✔
      When Read with offset and size
        The error should be nil ✔✔
        The content should be match ✔✘✔

 Failures:

  * /data/actions/beta/go-storage/go-storage/services/obs/tests/storage_test.go
  Line 14:
  Expected: '138112'
  Actual:   '451281'
  (Should be equal)

  * /data/actions/beta/go-storage/go-storage/services/obs/tests/storage_test.go
  Line 14:
  Expected: '1288953'
  Actual:   '2688928'
  (Should be equal)

  * /data/actions/beta/go-storage/go-storage/services/obs/tests/storage_test.go
  Line 14:
  Expected: '49793'
  Actual:   '291284'
  (Should be equal)

Obs implementation must be buggy, let's fix it before release.

Wait for https://github.com/huaweicloud/huaweicloud-sdk-go-obs/issues/10


Add pie design

The Facebook messenger video upload indicator is a simple transparent grey pie that fills. Would be good if that was added as an option to this library

Can you please share a gif or a demo of the mentioned indicator?

I think they mean something like this

It seems like you can use some of the props and make it looks like pie with current codes (CircularProgress) :) Thanks Author 🥇


Rename "teamEnv" to "accountEnv"

Background at https://github.com/netlify/build/pull/2040#discussion_r553900932
We use both "account" and "team" terms in the Netlify Build repository.
It seems like an account is either a team or user.
https://github.com/netlify/open-api/blob/309feb2f40dc7b1003e94cfbda87b63e7bee4116/swagger.yml#L1233
We should rename those terms accordingly in the repository, including in open PRs (e.g. https://github.com/netlify/build/pull/2040)

Done, thanks @eduardoboucas !

Done, thanks @eduardoboucas !


WIP: Refactor to get list of reports

Still need to enforce report permissions and
add list to dashboard.
Signed-off-by: Christopher Mundus<EMAIL_ADDRESS>Description
This will get a list of the reports that have been generated.
Discussion list or pending tasks
Need to add permissions to only list what the user has ownership of.

This is super cool stuff! Really nice work.
I added a commit with a new PostgREST API that is implemented as an RPC that adds the Content-Disposition header to the response. This RPC is also filtering by owner_id to enforce that the caller is the owner of the file being downloaded. I think we can use this same WHERE clause in the other view definitions to enforce people seeing only their own files.
I would like to update the apitest cases to demonstrate intended use of the files APIs, the current stuff is showing a weird way that we shouldn't use. It probably makes sense to completely remove the PUT support from the PostgREST files view so we don't accidentally use that API.
In order to get this working in Elm I think we will have to add a call to File.Download.bytes in order to save the bytes we get back from the XmlHttpRequest that is fired by Http.request.
One other thing I think will have to be handled before merging this is making the iss setting configurable, since the tokens issued from staging.havengrc.com will have a different issuer than dev.

This doesn't have working file downloads just yet, but it has grown large enough that I want to merge it so that these improvements are available to base other work on.


API Doc Specification

Signed-off-by: rabollin<EMAIL_ADDRESS>

This is the template we should be following for SDK documentation, so that the same template we will be using it for producing the documents for all SDKs we support today and also write new documentation.  My understanding of the Spec template you had described is primarily to detail the technical implementation of the SDK should follow.

Closing PR, due to archive


Disable checkFeature[FeatureNetworkInjection] for NetBSD

There is a problem with the image. Until the problem will be resolved,
disable the feature as it causes premature death of the syzbot setup.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1451   +/-   ##
=======================================
  Coverage   56.49%   56.49%
=======================================
  Files         135      135
  Lines       25777    25777
=======================================
  Hits        14562    14562
  Misses      10544    10544
  Partials      671      671

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 312c6a5...a5d2fb1. Read the comment docs.


How do I insert a scene in Tabs, without placing it in the TabsBar?

I've found myself needing an answer for this too. That or being able to render tabs from a scene that is not nested within Tabs.

From a UX perspective, you're looking a modal rather than replacing a tab screen, only scenes inside a tab bar will be rendered with a tab bar because they're the core sceeens of the app.
Any additional views like edit profile screens etc should be presented as modals.

@AlexCatch is right, closing this ticket.
You may try to use clone attribute, but I didn't test it for Tabs (only for Stack)


ESP 8266 WIFI Shield Access Point cannot be enabled

Describe the bug
i am trying to use the ESP 8266 WIFi Shield with the Board Nucleo F429Zi. I tested the connection to my WiFI network and it worked.
my idea for my project is to run the ESP 8266 WIFI Shield as an Access Point with a WebServer to set up the WIFI Network Connection. After the Set Up the ESP WIFI should turn off.
In my Code ( see below) , i set up the SSID as "ESPAP" without password for the Access point. The access point failed and is not enabled. I changed the parameters but it is still not working. Could someone of you help me to solve this Problem? Thank You!
To Reproduce
Steps to reproduce the behavior:

west build -b nucleo_f429zi myproject/esp_ap -- -DSHIELD=esp_8266
See CODE
CODE
/* Main */

void
main (void)
{
struct net_if *default_net_iface = net_if_get_default();
static struct wifi_connect_req_params wifi_conn_params;
printf("Wifi Test\n");

net_mgmt_init_event_callback(
    &wifi_management_callback,
    wifi_management_event_handler,
    WIFI_MANAGEMENT_EVENTS);

net_mgmt_init_event_callback(
    &dhcp_management_callback,
    dhcp_management_event_handler,
	NET_EVENT_IPV4_ADDR_ADD);

net_mgmt_add_event_callback(&wifi_management_callback);
net_mgmt_add_event_callback(&dhcp_management_callback);

printf("Network management setup complete, now wasting some time...\n");

k_sleep(K_SECONDS(5));
wifi_conn_params.ssid = "ESPAP";
wifi_conn_params.ssid_length = strlen("ESPAP");
wifi_conn_params.channel = WIFI_CHANNEL_ANY;
wifi_conn_params.security = WIFI_SECURITY_TYPE_NONE;

if (net_mgmt(NET_REQUEST_WIFI_AP_ENABLE, default_net_iface,
	     &wifi_conn_params, sizeof(struct wifi_connect_req_params))) {
	printf("AP mode failed\n");
	return;
} else {
	printf("AP mode enabled\n");
}
k_sleep(K_SECONDS(60));

Expected behavior
I excepted that the ESP WiFi Shield acts as an Access Point. The WiFi SSID "ESPAP" should be displayed in the WiFi network without password.
Logs and console output

Environment (please complete the following information):

OS: Linux
Toolchain  Zephyr SDK

Hi @cfriedt ,
I create the shield config that uses esp-at driver. However, I never tried to use it as a server.
I know that @mniestroj  is a major contributor for esp-at driver, maybe he can help us to understand current status.
@mniestroj do you know if is it possible use esp-at as server ? Is there any sample configuration ?
CC: @sylvioalves

@moncef-bibani I tried using ESP8266 with ESP-AT v2.1 in Access Point mode. This worked with following shell command:
uart:~$ wifi ap enable ESPAP 5
AP mode enabled

after that I was seeing "ESPAP" WiFi network from my smartphone.
Keep in mind that various ESP-AT firmware versions might behave slightly different. I recommend ESP-AT v2.1, as it is probably tested the most. I am not using Access Point, but at least it is visible by smartphone correctly.
@nandojve Using esp-at as a server is another case. This is not supported (listen is not implemented) and there is an enhancement already reported in #37113.

Hi @moncef-bibani ,
This is the right command to use Arduino Serial ( usart6 ).
west build -b nucleo_f429zi myproject/esp_ap -- -DSHIELD=esp_8266_arduino
Did you tried ?
west build -b nucleo_f429zi samples/net/wifi -- -DSHIELD=esp_8266_arduino
Just to make sure everything is OK.

Hi @nandojve @mniestroj ,
i tried the command with Arduino Serial. It´s still not working to enable the ap mode.
the wifi sample project from zephyr is worked fine and i could start the Access Point mode.
Everything works fine in my code except the NET_REQUEST_WIFI_AP_ENABLE. I could connect to a wifi network with the net_mgmt procedure with "NET_REQUEST_WIFI_CONNECT" .
I installed the firmware the AT V1.7 on the ESP-01S.
i don´t what the problem is, please help me to resolve it.
Thank you very much!

I had the same problem. Changing the parameter
wifi_conn_params.channel = WIFI_CHANNEL_ANY;
to
wifi_conn_params.channel = 5;
solved it for me with ESP AT Firmware 2.1


Getting UnsupportedValue for RegularExpression type in HTTPRouteHeaderMatch

What happened:
I'm trying to apply the following HTTPRoute, that according to the documentation and the CRD's should work:

And when describing the httproute i'm seeing:
      Message:               All rules are invalid: spec.rules[0].matches[0].headers[0].type: Unsupported value: "RegularExpression": supported values: "Exact"      Observed Generation:   1       Reason:                UnsupportedValue
What you expected to happen:
Everything to work fine, and my HTTPRoute to be applied and resolved.
How to reproduce it (as minimally and precisely as possible):
Try to apply a HTTPRoute that catches a header withthe type RegularExpression.
Anything else we need to know?:
I'm using the NGINX Fabric Gateway controller, and tried both the standard install and both the experimental, both are not working.
Thanks!

Hi @Danielkiss9
NGINX Fabric Gateway (NGF) doesn't support Regex matching for headers . List of supported fields of HTTPRoute -- https://docs.nginx.com/nginx-gateway-fabric/overview/gateway-api-compatibility/#httproute Related discussion https://github.com/nginxinc/nginx-gateway-fabric/discussions/1676
Please note that https://github.com/kubernetes-sigs/gateway-api repo is about Gateway API, not individual implementations like NGF.  For NGF specific questions, I recommend reaching out to the NGF maintainers https://github.com/nginxinc/nginx-gateway-fabric?tab=readme-ov-file#contacts

Thank you very much @pleshakov.
This was my mistake as i thought the HTTPRoute is individually maintained by the gateway API and not NGINX.
I'll be closing this issue :)


[VS Code] Starting collaboration session: RPC connection closed.

LiveShareLogs.zip

Error:
Starting collaboration session: RPC connection closed.
Steps to Reproduce:

I'm logged into Live share via GitHub
Click the 'live share button'.  This error immediately shows up.
I'm on a mac.  It does have a firewall installed (corp policy), is there something that needs to be opened to allow this feature?

Version Data

extensionName
VSLS

extensionVersion
0.4.0-dev

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.31.1

platformName
MacOS

platformVersion
17.7.0

Thanks for reporting this! We're tracking this via #1353, so I'm going to close it as a duplicate.


Reevaluate Font Size Responsiveness, especially in an Embed context.

This is part of OSMS's requests for making the map more embed friendly for makers.

https://github.com/findthemasks/findthemasks/pull/1064

@eikhunter is this completed by #1064? Can I close?

Yes it is, I'll close it for you


Version number on PyPI is different from version number on Github

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
The current yt-dlp version number in Github is 2024.04.09: https://github.com/yt-dlp/yt-dlp/releases
But the current yt-dlp version number in PyPI is 2024.4.9: https://pypi.org/project/yt-dlp/
To my mind, this difference might qualify as a bug in the build/release process.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
-

The correct version number is 2024.04.09 in conformance with datever, however PyPI normalizes those leading zeros away in conformance with the version specifier spec. Since we want to keep XXXX.XX.XX as the format there is not much we can do, and this shouldnt be considered a bug.
FYI, python -m pip install "yt-dlp==2024.04.09" for example works bc those versions are the same, but pypi normalizes it for display

Thanks for explaining, @Grub4K.


Make the /edit permalink retrievable if the leader is logged in

Relates to gh-568.

TODO

[ ] itest: Have the leader log in, drawing on login code from v1 itest.
[ ] itest: New, parallel itest. Copied from links itest. Have the leader retrieve their link from the post-login Your Seders page.


Add video quick install

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

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

this is fix with 2 videos
https://cloudnativetoolkit.dev/toolkit-resources/videos
https://cloudnativetoolkit.dev/workshop/setup


Add access codes to admin interface

Description
Add access codes to admin interface.
Reviewer Notes
There are a couple filters available. Experiment with these. You should be able to search for a particular access code, or add a filter to filter to a specific move type. Also, a careful code review is appreciated, since this first time working with the admin interface and haven't looked at access codes in long while.
@chrisrcoles a couple questions / things for you to look at, since these intersected w/ previous work you'd done on this branch.

Some of your work on this branch involved moving the access codes to internal the internal api. This was conflicting with similar work that was done in b6c33db67281ec84c63ac200652787a7b04dde82. It looked like it was a just a matter of whether to pluralize the endpoint name or not. I just deferred to what was already in master to limit the diff size (since this story was about adding an admin endpoint), but please double check that section.

I saw the model for access codes added a ServiceMember. I wasn't sure if this should be a pointer or not. No tests were breaking, but just wanted to double check that made sense, since I haven't worked with the access codes much.

Setup
Add any steps or code to run in this section to help others prepare to run your code:
make server_test
make server_run
make admin_client_run

Code Review Verification Steps

[ ] Code follows the guidelines for [Logging]
[ ] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

We created a story for all of the followup around move type: https://www.pivotaltracker.com/story/show/168762441


added css to project

This PR adds a CSS style sheet and an updated HTML file for the prework study guide application

I am unable to merge feature/add-css and feature/add-html to base branch


ref ignored if syntactically looks like a value in some cases

I think this is a parser bug with babel-preset-solid and possibly the underlying lib it uses, but see https://codesandbox.io/s/ignored-ref-xsikh?file=/src/index.tsx

Yeah I was too specific in the non-assignable case to only look for functions. It should take every non-assignable statement and try to call it as a function instead. I know the fix will push it when able.

@ryansolid Let's me fix this issue.


Bhindupur/speech as input

Purpose
This PR removes the previously hardcoded list of spoken languages recognized by the chat web interface and reads the list from the deployment configuration instead.
The parameter is accepted by the deployment bicep script, and is outputted to the azure env file. It is then injected at build time  to the frontend UI react app via an environment variable.
At runtime, this environment variable is read by the frontend UI app to configure the Azure Speech recognizer to recognize the given languages via speech.
Does this introduce a breaking change?

[ ] Yes
[x ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[x ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test
Deploy the code, then test via the web chat app that the configured languages are being recognized by the speech input.
I tested English and Italian at my end.

nit: Can you change the title of this PR and link it to an issue/bug/etc?

From my understanding, this change is all about passing in a string "en-US,fr-FR,de-DE,it-IT" to TypeScript.

I agree with the bicep changes to get this into an .env file for local debugging, but then as Adam states, it should be added to the AppSettings for the host "web" and "web.docker"
vite will read whatever is on process.env, so I don't see why it needs the path of the env file, rather as it should be able to read VITE_SPEECH_RECOGNIZER_LANGUAGES if it's loaded onto the process.
I would also question why the variable needs to be prefixed with VITE_ as that does not relate to it
I think you have gone down this path because it is not working in the makefile - and that is because we did not implement a previous change that I requested. I think you need something like

AZURE_ENV_FILE := $(shell azd env list --output json | jq -r '.[] | select(.IsDefault == true) | .DotEnvPath')
ifeq ($(filter $(MAKECMDGOALS),config clean),)
	ifneq ($(strip $(wildcard $(AZURE_ENV_FILE))),)
		ifneq ($(MAKECMDGOALS),config)
			include $(AZURE_ENV_FILE)
			export
		endif
	endif
endif

This would actually "export" the file and the process would have the all of the environment variables loaded and vite would get your string. In the case of running in the cloud, then it would use the AppSettings

Many thanks for this, one tiny addition for me and we can get this home!


How could I get the answer of the exercises in PH525x series?

Sorry to trouble you, I'm a beginner of bioinformatics and recently I'm reading your book "PH525x series - Biomedical Data Science". I followed the chapter and did the exercises, but I can't find the answer so I came here for help. Could you give me a link to the answer? Thank you.

The solutions are not available as an online document. But if you are taking the course the solutions are shown once you try the assessments. If this is not working for you contact HarvardX<EMAIL_ADDRESS>

I searched the web and found the course. Thank you so much!
------------------ 原始邮件 ------------------
发件人:                                                                                "genomicsclass/labs"<EMAIL_ADDRESS>发送时间: 2021年2月26日(星期五) 上午6:57
收件人<EMAIL_ADDRESS>抄送: "Zeki"<1156466645<EMAIL_ADDRESS>主题: Re: [genomicsclass/labs] How could I get the answer of the exercises in PH525x series? (#101)
The solutions are not available as an online document. But if you are taking the course the solutions are shown once you try the assessments. If this is not working for you contact HarvardX<EMAIL_ADDRESS>—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Additional documentation linked

Documentation with current Intune network endpoints added

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

acknowledged review

@hathin - please merge the commit on the copy/edit review done by JohanFreelancer9 or make the necessary changes on the PR following the suggestions made. Thank you.

@jaimeo - PR has been copy edited and is ready for final review.
Thank you.
cc: @kenwith


Select/combobox built-in labels

Pull Request
🤨 Rationale
Implementation for #2183 . (Work item includes figuring out usage guidance, so won't close it with this PR yet)
👩💻 Implementation
See updated HLD in this PR.
🧪 Testing

Local testing in Storybook
Added autotests to cover the select's new (internal) labelContent property and that it sets aria-label (similar to those in list-option-group.spec.ts)
Storybook: Added the 'height test' stories present in other controls that have labels
Inspected Chromatic diffs. Haven't accepted these yet, but the changes are all expected:

Disabled controls now have disabled labels
If a width style is set on the control (as it is in the theme matrix tests), labels will wrap to multiple lines if needed. This matches existing control behavior (see text area / number field stories)

Verified pre-existing accessibility violations for select / combobox are resolved

✅ Checklist

[x] I have updated the project documentation to reflect my changes or determined no changes are needed.

Updated Storybook docs to document label support for select/combobox

@atmgrifter00 can you buddy this PR?


Graduated-related sites and materials | Wenhan’s Notes

https://whwu17.github.io/notes/postgraduate/2023/04/12/essay-template.html

12212212

231

32323

oiuou

efe


The Class prop overrides DevExtreme classes

Issue Type
bug report
Description

The issue is related to all components
Steps to Reproduce
Change any component class after it was initialized
Current Behavior
dx-* classes removed
Expected Behavior
dx-* classes remain
Environment Details

devextreme-vue version: 18.1.5-alpha.8

Vue does not get access to a class property. We will investigate how to fix this issue.
As a workaround, you can wrap the DevExtreme widget in a div and set your class it.

Vue has some restrictions for the case. From the https://github.com/vuejs/vue/issues/3975:

This is expected behaviour in 2.0, since these changes can't be reflected in the virtualDOM and get therefore overriden during updates.

We are unable to fix this issue because of Vue 2.0 limitations. We will consider this modification once Vue 3.0 is released.


Notifications via email or sms

Hi,
I was using pokemongomap previously before it was shut down and i was able to edit the script (as a noob) and was able to get it to send me a sms  (bulksms) when a predefined pokemon  pokemon appeared and the sms contained the name of the pokemon, its dissappear time and a clickable google maps link directing you to it.  Im struggling to impliment it in your script, any ideas?

BTW, you guys are legends!

I would love the ability to get a phone notification somehow!

It worked so well, im very inexperienced in python but i managed to get it working flawlessly.
This is how the sms comes, i just copied it...
Squirtle -  http://maps.google.com/?q=-33.860078,18.535788   Disappears at: 2016-07-26 22:33:01.358000

An email would work for me too tbh

Ya i knw, i worked with bulksms before so it was easier to implement. Email is free where im paying for sms credits now, but its cheap.

I used to code for telegram bots, I could do something with that! but I can't fully understand this library, baby steps

made a telegram bot in #279

@eugenio, u are a legend... only 1 small problem, how does one scan for many pokemon and not just 1?

Still working on it, I need an array for rare, ultra rare Pokemon etc etc

Done, now it supports the notification based on rarity, but I moved to https://GitHub.com/eugenio412/pogoBOT

hii
Get best Bulk SMS service provider in India to relate with your customer.


Falco container crashes on Amazon Linux 2 using 4.14 Kernel

Describe the bug
When using Amazon Linux 2 and running falco in a container, the container crashes with the error Runtime error: failed to open event raw_syscalls/sys_enter. Exiting. This can be resolved by upgrading the kernel to 5.10 however this is presently not an option open to me. If I understand the Falco documentation correctly kernel v4.14 is supported.
How to reproduce it

Create a fresh EC2 instance running AL2 and kernel 4.14. For the avoidance of doubt the AMI ID here is ami-053bef78866800cfa.
 Cannot start container to pass --version
System info:
Cannot start container to pass args
Cloud provider or hardware configuration:
OS:

NAME="Amazon Linux"
VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
HOME_URL="https://amazonlinux.com/"

Kernel:
Linux ip-10-123-212-173.eu-west-2.compute.internal 4.14.314-237.533.amzn2.x86_64 #1 SMP Thu May 4 09:55:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Installation method:
Containerised. Pull from dockerhub

Additional context
During the course of debug iptables was flushed and selinux disabled using grubby to no effect.
Logs from docker logs for the sake of completeness
2023-06-01T12:02:22+0000: Falco initialized with configuration file /etc/falco/falco.yaml
2023-06-01T12:02:22+0000: Loading rules from file /etc/falco/falco_rules.yaml:
2023-06-01T12:02:22+0000: Loading rules from file /etc/falco/falco_rules.local.yaml:
Rules match ignored syscall: warning (ignored-evttype):
         loaded rules match the following events: access,brk,close,cpu_hotplug,drop,epoll_wait,eventfd,fcntl,fstat,fstat64,futex,getcwd,getdents,getdents64,getegid,geteuid,getgid,getpeername,getresgid,getresuid,getrlimit,getsockname,getsockopt,getuid,infra,k8s,llseek,lseek,lstat,lstat64,mesos,mmap,mmap2,mprotect,munmap,nanosleep,notification,page_fault,poll,ppoll,pread,preadv,procinfo,pwrite,pwritev,read,readv,recv,recvmmsg,select,semctl,semget,semop,send,sendfile,sendmmsg,setrlimit,shutdown,signaldeliver,splice,stat,stat64,switch,sysdigevent,timerfd_create,write,writev;
         but these events are not returned unless running falco with -A
2023-06-01T12:02:23+0000: Unable to load the driver.

The falco_rules files in question can be located at https://gitlab.com/gitlab-org/security-products/package-hunter/-/tree/main/falco. I do not believe these to be causing an issue but are included for the sake of completeness.

ei @andy-welsh-dwp our documentation is not completely correct, if you are running a kernel version < 4.17 you need to add a volume to the docker command
-v /sys/kernel/debug:/sys/kernel/debug:ro \

The documentation says this is the commad:
docker run --rm -i -t \
    --cap-drop all \
    --cap-add sys_admin \
    --cap-add sys_resource \
    --cap-add sys_ptrace \
    -v /var/run/docker.sock:/host/var/run/docker.sock \
    -e FALCO_BPF_PROBE="" \
    -v /root/.falco:/root/.falco \
    -v /etc:/host/etc \
    -v /proc:/host/proc:ro \
    falcosecurity/falco-no-driver:latest

But for kernel versions < 4.17 you need to type
docker run --rm -i -t \
    --cap-drop all \
    --cap-add sys_admin \
    --cap-add sys_resource \
    --cap-add sys_ptrace \
    -v /var/run/docker.sock:/host/var/run/docker.sock \
    -e FALCO_BPF_PROBE="" \
    -v /root/.falco:/root/.falco \
    -v /etc:/host/etc \
    -v /proc:/host/proc:ro \
    -v /sys/kernel/debug:/sys/kernel/debug:ro \
    falcosecurity/falco-no-driver:latest

Thank you for reporting this I will update the docs!

That works great. I could have sworn I had tested this but I must have been tripping over my own debugging.
Can you explain the cause of the issue? I am guessing that debugfs is not being properly exposed to the container? This is handled somehow differently in kernels > 4.17?

Can you explain the cause of the issue? I am guessing that debugfs is not being properly exposed to the container? This is handled somehow differently in kernels > 4.17?

Yes, sure! As you said debugfs was not being properly exposed to the container, but we need it to load simple BPF tracepoints. More precisely we need to read under "/sys/kernel/debug/tracing/events/<tracepoint_name>/id" to find the id of the tracepoint. Starting from kernel versions >= 4.17 we use raw_tracepoints and we don't need anymore to read under this path we can directly use the bpf syscall. Not sure you want this level of detail but just to be super explicit these are the 2 involved functions:
static int __attach_raw_tp(struct bpf_attached_prog* prog, char* last_err)
{
	union bpf_attr attr;
	memset(&attr, 0, sizeof(attr));
	attr.raw_tracepoint.name = (unsigned long)prog->name;
	attr.raw_tracepoint.prog_fd = prog->fd;

	prog->efd = syscall(__NR_bpf, BPF_RAW_TRACEPOINT_OPEN, &attr, sizeof(attr));
	if(prog->efd < 0)
	{
		return scap_errprintf(last_err, -prog->efd, "BPF_RAW_TRACEPOINT_OPEN: event %s", prog->name);
	}
	return SCAP_SUCCESS;
}

static int __attach_tp(struct bpf_attached_prog* prog, char* last_err)
{
	int efd = 0;
	int err = 0;
	char buf[SCAP_MAX_PATH_SIZE];
	snprintf(buf, sizeof(buf), "/sys/kernel/debug/tracing/events/%s/id", prog->name);
	efd = open(buf, O_RDONLY, 0);
	if(efd < 0)
	{
		if(strcmp(prog->name, "exceptions/page_fault_user") == 0 ||
		   strcmp(prog->name, "exceptions/page_fault_kernel") == 0)
		{
			return SCAP_SUCCESS;
		}

		return scap_errprintf(last_err, errno, "failed to open event %s", prog->name);
	}

	err = read(efd, buf, sizeof(buf));
	if(err < 0 || err >= sizeof(buf))
	{
		int err = errno;
		close(efd);
		return scap_errprintf(last_err, err, "read from '%s' failed", prog->name);
	}
	close(efd);

	buf[err] = 0;
	int id = atoi(buf);

	struct perf_event_attr attr = {};
	attr.type = PERF_TYPE_TRACEPOINT;
	attr.sample_type = PERF_SAMPLE_RAW;
	attr.sample_period = 1;
	attr.wakeup_events = 1;
	attr.config = id;

	efd = syscall(__NR_perf_event_open, &attr, -1, 0, -1, 0);
	if(efd < 0)
	{
		return scap_errprintf(last_err, -efd, "event %d", id);
	}

	if(ioctl(efd, PERF_EVENT_IOC_SET_BPF, prog->fd))
	{
		int err = errno;
		close(efd);
		return scap_errprintf(last_err, err, "PERF_EVENT_IOC_SET_BPF");
	}
	prog->efd = efd;
	return SCAP_SUCCESS;
}

As you can notice in __attach_raw_tp we directly use the bpf syscall to load tracepoints.
Hope this will be useful

That is super useful yes, thank you! Always good to be as detailed as possible!
As we're working I'll mark as closed. Thanks for the help!


Fix english lang translation

Click here if you want to create code_sniffer's auto-correct Pull Request

See the documentation if you want to get more information about auto-correct.
Document

Thank you


Beagle install fails

The installation of beagle currently fails. I think maybe there's be a version update and the beagle version used in ColabBEAST isn't pinned?
sed: can't read configure.ac: No such file or directory
/bin/bash: ./autogen.sh: No such file or directory
/bin/bash: ./configure: No such file or directory
make: *** No rule to make target 'install'.  Stop.
make: *** No rule to make target 'check'.  Stop.

Hello @Wytamma! you're right! beagle currently fails.
I thought it was easy to solve but I guess I was wrong. Actually, I set the installation to beagle version 3.1.2 but now I have an error when I run beast with the test datasets.
CUDA error: "Unknown error" from file <GPUInterfaceCUDA.cpp>, line 276.
The weird thing is that beast -beagle_info works without any problem
If you don't have any idea... I will have to check the beagle installation more closely to solve the problem.
Thanks for the error report!

Yeah I ran into that same issue... tried messing with the complier and changing to the new cmake install instructions but no luck :/

It is Fixed!  @Wytamma!!
Could you confirm that it was fixed on your side?

Awesome! yes it works :D nice work!


Add function to "instantiate" annotations-derived 'attr.ib's.

TLDR
It would be very useful to extract the __annotations__ handling logic currently in _transform_attrs into a standalone function that can be used to convert annotations into _CountingAttrs and _CountAttr.types. This would support attrs-based plugins that set or modify attribute validators/converters/metadata before attr.s-based class generation.
Current State
One major strength of attrs is the ability to layer metadata, validation and conversion logic onto attr classes to implement project-specific class declaration patterns.
As a toy example, consider the case of adding simple init-time type validation to a class:
@attr.s
class Foo:
    bar = attr.ib(type=str, validator=attr.validators.instance_of(str))
    bat = attr.ib(type=int, validator=attr.validators.instance_of(int))
    baz = attr.ib(type=float, validator=attr.validators.instance_of(float))

Very punchy, but we're spoiled. This can be dry-ed out with a trivial decorator:

def validate_attr_types(cls):
    counting_attrs = [
	v for v in cls.__dict__.values()
	if isinstance(v, attr._make._CountingAttr)
    ]

    for ca in counting_attrs:
	if ca.type:
	    ca.validator(attr.validator.instance_of(ca.type))

    return cls

@attr.s
@validate_attr_types
class Foo:
    bar = attr.ib(type=str)
    bat = attr.ib(type=int)
    baz = attr.ib(type=float)

As our decorator is in the business of modifying the declared attributes to add validation (or conversion,  metadata, ...) it needs to run before attr.s, which freezes _CountingAttrs down into Attributes. This isn't an obstacle, as we're declaring all the attr.ibs and most of the time we'll define a nice wrapper around attr.ib if we need any non-trivial logic.
The Problem
It's 2018 and type annotations are in! We would really prefer to write something like:
@attr.s(auto_attribs=True)
@validate_attr_types
class Foo:
    bar : str
    bat : int
    baz : float

Unfortunately this gets us into a real sticky wicket. At the time our decorator fires Foo doesn't have any _CountingAttr instances available for us to update, just entries in the __annotations__ dict. The naive idea of swapping the decorator ordering is no good, as the generated attributes would be frozen by attr.s. We might be able to let attr.s run, hackily create an updated variant of the class, call attr.s again, and then return the second generated class but this just feels wrong.
Slightly subtly, this problem bites us even if we mandate that all attr.ibs are declared:
@attr.s(auto_attribs=True)
@validate_attr_types
class Foo:
    bar : str = attr.ib()
    bat : int = attr.ib()
    baz : float = attr.ib()

Our decorator will now fail because the type information stored in the __annotations__ hasn't yet been extracted into _CountingAttr.type.
A Solution
It would be ideal if attrs offered an idempotent function to convert all __annotations__ based attribute information into concrete, mutable _CountingAttr instances on a pre-attr.s class. This would convert:
class FooPre:
    bar : str
    bat : int = attr.ib()
    baz = attr.ib(type=float)

into _CountingAttr equivalents of:
class Foo:
    bar = attr.ib(type=str)
    bat = attr.ib(type=int)
    baz = attr.ib(type=float)

Given the straw-man name attr.transform_annotations, this would let us write our simple decorator as:
def validate_attr_types(cls):

    # in-place update of cls from __annotations__
    attr.transform_annotations(cls, auto_attribs=True)

    counting_attrs = [
	v for v in cls.__dict__.values()
	if isinstance(v, attr._make._CountingAttr)
    ]

    for ca in counting_attrs:
	if ca.type:
	    ca.validator(attr.validator.instance_of(ca.type))

    return cls

and write:
@attr.s
@validate_attr_types
class Foo:
    bar : str
    bat : int
    baz : float

Note that with type annotations, instance_of is a partial solution, since we'll also see people trying interface types:
@attr.s
@validate_attr_types
class Foo:
    bar : AnyStr
    bat : Optional[float]
    baz : Mapping[str, int]

While instance_of validation is useful, I suspect, we'll see lots of bug reports right away.
Maybe if validate_attr_types gets a more limited-sounding name we might see fewer.

(Excellent write-up, by the way.)

Just to clarify, the example decorator is just a minimal immediately-grok-able sample. I'm not proposing that such a decorator be included in attrs, and have (hopefully) clarified this in the example.
The actually-motivating use case is a little more complex; I'm attempting to cleanup and spinout an attrs-based tensor data adapter we're using in a private project. This component currently relies on a hack-y combination of a mixed-in base class and method-time analysis of the attribute list, but I would like to convert it to a simpler & more performant model based on an an attr.s style class decorator. This will require definition-time processing of the target class's attributes to set library-specific metadata values.

Perhaps a solution that's more inline with decorator-esque customization is to provide decorators that would split attrs into transforming and freezing:
@attr.freeze
@validate_attr_types
@attr.transform
class Foo:
    bar : str
    bat : int
    baz : float

Just to TL;DR it, you would like to change our flow to make
class Foo:
    bar = attr.ib(type=str)

the canonical form that is used by attrs itself and make type annotations a separate, idempotent step?
I guess that might even simplify our internal code to a certain degree? 🤔

I would slightly expand that to state that there should be a canonical "internal" form, which both attrs and attrs-based external libraries can rely on during class configuration. As this canonical form won't match the preferred user-facing form, which is likely a "dataclass" style declaration using type annotations, attrs should provide an idempotent coercion function to convert from all allowable using-facing formats to the canonical programmatic representation.
To lift out specifics, this function would be an subset of the current attr._make._transform_attrs function however it would involve an in-place modification of the target class to add _CountingAttr class properties rather than extracting an attribute list.
This may slightly simplify the internal code, but I don't believe it will have much of an effect. The _transform_attrs call is the first step of _ClassBuilder process, so attrs is effectively relying on a standard representation throughout class construction already.

@Kentzo I don't think this a bad idea, but it seems like it'd unnecessarily expose an implementation detail about attrs' preferred internal representation to the consuming user? If we write an idempotent transformation function then attrs, and attrs-dependent wrapping libraries, can call that function before any class modification to ensure that the canonical internal representation is present.

As a gut-check, does this idea seem generally acceptable? If so I can open a straw-man PR to help focus the conversation around implementation specifics.

This looks related to #649 and #653

Don't forget that annotations could be strings too.  And in Python 3.10 will always be strings.  And so not only do you have to evaluate them, you might also have forward references to objects that don't exist when the class is being created.  Here's what we do at our company.  (Someday we will open source this):
We have a decorator that replaces attr.s and before it calls attrs.s shoves an
def __attrs_post_init__(self: object) -> None:
            _verify_attribute_types(self)

into the class.
_verify_attribute_types first calls something like:  https://paper.dropbox.com/doc/datetime-methods-you-should-use--A2FODCFy8MVelBUoOkmr2akfAg-aCPNKYCZEqmOU2J4xlyqN
(And caches it on the class for performance)
And now that it has the real types it loops through the arguments and checks them using whatever method you want.

FYI the linked doc doesn't seem to be public.

Oops. Not what I meant to post.

Like this?
import attr
from attr import NOTHING, attrib
from typing import TypeVar

from attr._make import _get_annotations, _CountingAttr, _is_class_var

_C = TypeVar("_C", bound=type)

def make_auto_attribs(cls: _C) -> _C:
    for attr_name, type in _get_annotations(cls).items():
        if _is_class_var(type):
            continue
        a = getattr(cls, attr_name, NOTHING)
        if not isinstance(a, _CountingAttr):
            setattr(cls, attr_name, attrib(default=a))
    return cls

@make_auto_attribs
class Foo:
    x: int
    y: str = "15"
    z: bool = attr.ib(True)

print(Foo.x)
print(Foo.y)
print(Foo.z)

I guessed I asked this before, but is there a way we could add this to attrs behind an option? It seems very handy especially when looking towards 3.10.

Which part is "this" exactly?  There are lots of proposals in this issue.  :)

Heh sorry. 😅 I meant automatically running something like make_auto_attribs such that the typing information is always concrete.

If I understand this correctly, do you mean something like make_auto_attribs accompanied by something like resolve_types from #302 so that the type property is resolved into a concrete value?
My interpretation of make_auto_attributes as implemented above is that it tackles the top-level request, but that it does not handle resolving typing information from strings to concrete types.

resolving types often cannot be performed at class creation time.  (e.g. if you have forward refs)
Also not everything needs these to be concrete types so it would be wasted resources to do it automatically.

I'm super sorry, I'm sure you told me that (at least) once before. Could I compel you to submit a PR to explain this problematic in https://www.attrs.org/en/stable/types.html because we're 100% gonna get bugs about it and also I'll be able to refer to your explanation the next time I forget. 🙈😅


Plugin is not loading.

[x] This issue isn't duplicated - you can check if it is by using the search bar located at the top left hand corner and select "Issues" on the left.
[x] This issue includes appropriate markdown for sections - e.g. code blocks for crash dumps.
[x] This issue is understandable - feel free to use your native language to write issues if you are not comfortable with English.

Issue description
Plugin is not loading.

Reproducing the issue

DevTools is loading the Folder-Plugin
Then comes the Error and the Plugin is at /pl red marked.

Client information
PocketMine-MP Version: [17:06:39] [Server thread/INFO]: This server is running PocketMine-MP 1.7dev-82 「[REDACTED]」 implementing API version 3.0.0-ALPHA8 for Minecraft: PE v<IP_ADDRESS> (protocol version 137)
Plugin Version: [17:03:28] [Server thread/INFO]: Enabling MyPlot v1.1.7
PHP version: 7.0.13 (default)

Optional information
[17:03:28] [Server thread/CRITICAL]: Error: "Class 'spoondetector\SpoonDetector' not found" (EXCEPTION) in "MyPlot/src/                                              MyPlot/MyPlot" at line 441

Have fixed the Problem. ;)

How did you fix it?

Wie hast du es behoben?


core: bump version to v0.2.0

Codecov Report

Merging #9 (79359c4) into main (e793b2a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main        #9   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          776       776
  Branches        55        55
=========================================
  Hits           776       776

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Clipping subsampler refactor

I need to add ffmpeg pipes to speed up processing, and to do that I first needed to refactor some of the code to make it easier to reason about.
For context, I'm processing webvid-10M and the codebase is currently too slow. I'm hoping to speed it up by an order of magnitude by combining subsamplers into a single ffmpeg pipe operation, and adding other optimizations.

I'm processing webvid-10M and the codebase is currently too slow. I'm hoping to speed it up by an order of magnitude by combining subsamplers into a single ffmpeg pipe operation.

nice, yes this is a great idea

is this ready to go? If so could you give a high level overview of the changes?

This is basically just a refactor. I broke the code into smaller functions, added types, only process metadata once per clip (instead of once per stream), renamed some stuff for clarity, and cleaned up the segment_times collection code.
I avoided making any functional changes, but I think I see a couple of places for improvement that I'll hit in later pull requests.

looks much better
I think the smaller functions could be an opportunity to add some more tests. What do you think?

just merged https://github.com/iejMac/video2dataset/pull/262 and having a bit of trouble to rebase here hmm

probably best if you handle this rebase @MattUnderscoreZhang  ; I think it's mostly about replacing the code that's doing the extract subtitle by that new function

Yeah no prob, I just merged changes.

@MattUnderscoreZhang did you test this to produce the same results as before? this is a lot of complex code that is changed

Yes, I get the exact same results for my use case, which involves a frame rate resampling, resizing, cropping, and clipping.
Plus, all the unit tests pass as expected.


POC shared package in monorepo

See parent issue.

The current NX setp of the js sdk easily allow adding the shared package for flagd in-process core logic.
I attempted this using NX tutorial [1] and local dependencies get resolved. I will include more logic into this POC and open a draft PR soon.
[1] - https://nx.dev/getting-started/tutorials/integrated-repo-tutorial#create-a-package

If it's the easiest route, you could even add the package, and version it 0.0.1-alpha. Publishing this library empty wont hurt, and it won't be empty for long.

@toddbaert good suggestion. I created the initial PR with 0.0.1-alpha version - https://github.com/open-feature/js-sdk-contrib/pull/620

And consider the package usage in this draft PR - https://github.com/open-feature/js-sdk-contrib/pull/621


adding 2.3.3

🙏

Hi Adam, I am doing this for QCloud. The EY stack upgrade will lead us to 2.3.3, and I would like to have the same version in Jenkins.


DO NOT MERGE Towards 0.6.4. CI only.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1684/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2182/
Test PASSed.


chore: replace ContainerInspect and Info with GetContainer and GetInfo

replace ContainerInspect and Info with GetContainer and GetInfo

LGTM

Thanks for your contribution! :tada: :+1:


Unable to load DLL Microsoft.Data.SqlClient.x86.dll (Exception From HRESULT: 0x800707E)

Describe the bug
I am trying to edit connection string on my report using DevExpress winform report wizard

when I click on next button I get this error

When I try to install latest stable version of Microsoft.Data.SqlClient 1.1.3 I get two different error
01-With Windows authentication

02-With Server authentication

Note:
-When running the app, all report works fine without any problems.
Further technical details
Microsoft.Data.SqlClient version: 2.0.0-preview4.20142.4
Microsoft.Data.SqlClient.SNI version: 2.0.0-preview1.20141.10
System.Configuration.ConfigurationManager version: 5.0.0-preview.4.20251.6
.NET target: Framework 4.7.2
SQL Server version: SQL Server 2019
Operating system: Windows 10 Version 2004
DevExpress 20.1.3
Microsoft Visual Studio Enterprise 2019 Preview Version 16.7.0 Preview 2.0
Update:
It is seems to be related to DevExpress version ,I downgrade to version 19.2.8 and all problems are gone.

Hi @qwertybba,
I installed the DevExpress(trial) v20.1.4 and Visual Studio community 2019 v16.6.1, but the DevExpress components are not added to the Toolbox and it was not in the component window to add. Can you prepare your repo app here for more investigations?

Hi @qwertybba,
I installed the DevExpress(trial) v20.1.4 and Visual Studio community 2019 v16.6.1, but the DevExpress components are not added to the Toolbox and it was not in the component window to add. Can you prepare your repo app here for more investigations?
Sorry for the delay.
https://github.com/qwertybba/DXApplication1

@qwertybba, I am not able to run the sample application. I have an issue with licenses.licx. I need a repro app to investigate more.
According to the library you are using is not open source, can I ask you do you follow your issue with the DevExpress support team?

After contacting the DevExpress support team, advise me to do the following
"I have managed to reproduce this error and found the following workaround:
Open the bin\Debug folder in your project, and copy all files starting with "Microsoft.Data.SqlClient" the "C:\Program Files (x86)\Microsoft Visual Studio\2019[YOUR EDITION NAME]\Common7\IDE\PrivateAssemblies" folder.
Restart Visual Studio."
So I copied these files and the problem was solved
Microsoft.Data.SqlClient.dll
Microsoft.Data.SqlClient.pdb
Microsoft.Data.SqlClient.SNI.x64.dll
Microsoft.Data.SqlClient.SNI.x64.pdb
Microsoft.Data.SqlClient.SNI.x86.dll
Microsoft.Data.SqlClient.SNI.x86.pdb
Microsoft.Data.SqlClient.xml
Big Thanks to DevExpress support team

Thank you for the update. So, I am closing this issue.


remove  unsupported test cases from service  feature

…oviders
Description of the changes
remove  serviceSequenceAddDeleteProvider test  since it's not valid with current design.
Type of fix:
Bug Fix

Fixes #
Fixes 908

As per current design, service instances object should be created before adding service provider object. removing those test cases in which provider object is  created before service objects.

run L3-CI which is passed after those changes earlier it was failing all the time.

run make l3-test which is passed after this changes

TODO
-documentation update under process

LGTM


Try to use the target branch

@bthaile hoping this stops all PRs to v2 from running ALL tests and building pop dockers

@mergeifyio backport dev