fix/docs: remove imageCredentials.email from root README snippets

Description

imageCredentials.email isn't specified or used in any of the Charts,
so this is extraneous and confusing
also, imageCredentials.email isn't specified in the Charts' README's
themselves, only in the root README

this might be a good reason to not have subtly different duplicative
docs in two places, similar to how 38f48d607ca6fbda0cb29a154df9f47d3ce8bd15
removed the duplicate configuration that was in the root README

Tags
Seems to have been like this since origination.
Related to #110 which removes an unused imageCredentials.email in KubeEnforcer's values

There are conflicts now because 70ae917 was pushed directly to master after this PR was made and it added a $  to the start of the snippets. That change also doesn't pass markdownlint MD014

not relevant anymore. @agilgur5 thanks for reporting.


[AP-195] Back navigation from passported/not passported

What
AP-195

Modify the address pages to update the address if there is one rather than always creating a new one
Implement correct backlink URL on check_benefits page

Checklist
Before you ask people to review this PR:

[x] Tests and rubocop should be passing: bundle exec rake
[x] Github should not be reporting conflicts; you should have recently run git rebase master.
[x] There should be no unneccessary whitespace changes. These make diffs harder to read and conflicts more likely.
[x] The PR description should say what you changed and why, with a link to the JIRA story.
[x] You should have looked at the diff against master and ensured that nothing unexpected is included in your changes.
[x] You should have checked that the commit messages say why the change was made.

@reggieb, @lostie, I addressed your feedbacks. Could you have another look when you have a moment?

:+1:


Fixes #16247: clone behaviors when cloning components

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
yes

Tests pass?
yes

Fixed issues
#16247

Merged. Thanks!

Why events are not cloned in the same way?

Should be, I guess. Want to make a pull request?

Events don’t seem as obvious as behaviors. Cloning an object is basically a shortcut to defining a new object with the same class and setting the same properties on it - and if behaviors are ment to act as extensions of the class, that definitely seems like it should be cloned too. But events are intentionally registered either at the class level (already will work on a clone) or for a specific instance. Maybe it's not intended that the events should be set on the clone as well though.

Hmm... right. That's controversial.

Events don’t seem as obvious as behaviors.

I don't see any difference. It looks inconsistent to me, especially that events attached from behaviors are cloned, but events attached manually are not.
But AFAIK there will be some changes in events handling in 3.0 so it may be irrelevant after all.

especially that events attached from behaviors are cloned

Events added from behaviors are essentially the class dynamically defining its own business logic. The non-behavior equivelant would have been for the owner class to just call some internal method alongside firing the event.
I’m not saying it definitely doesn’t make sense for events to be cloned as well; just that it’s not always going to be expected behavior. For example, if I did this:
$obj = new MyObject();
$obj->on('afterDoSomething', function() {
    // ...
});

$obj2 = clone $obj;
$obj2->doSomething();

I don’t think expected behavior would be that the afterDoSomething handler would get called for $obj2. If you disagree, maybe it’s worth opening this up as a new issue for debate there. This PR is  probably the wrong place to discuss it :)

@brandonkelly Let's just agree to disagree. For me current behavior is inconsistent and I don't see any reason why dynamically attached behaviors and its events should be handled differently than dynamically attached events. But this is not important for me, I almost never use this feature anyway. I just wanted to point it now, because fixing this inconsistency may require BC break (you cannot just clone all events because cloned behaviors already attaches its events, so you will get duplicated events).

Let's not clone events for now.


Add community reference to aiolinkding

I started building a linkding workflow for Alfred and realized that instead of burying the linkding API logic in the workflow, it would be helpful (for both that project and others) to create a Python3, async wrapper library. Thus, this PR adds aiolinkding to the community section of the docs.

Nice job!


Add explanation about configuration

Add configuration instructions to readme

@iriark01 Does this cover all your change requests?

Yep; this is good to go from my end


cargo,clippy,rustc,rustfmt: 1.78.0 -> 1.79.0

Description of changes
For the first time, it seems that no new kernel patch is required!
Built:

[x] firefox on aarch64-linux
[x] firefox on x86_64-linux
[x] thunderbird on aarch64-linux
[x] thunderbird on x86_64-linux
[x] watchman on aarch64-linux
[x] watchman on x86_64-linux
[x] fd on aarch64-darwin
[x] fd on aarch64-linux
[x] fd on x86_64-darwin
[x] fd on x86_64-linux

Help needed testing fd on Darwin!
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Built fd on aarch64-darwin and x86_64-darwin.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/failed-to-package-zola-0-19-0-dependencies-require-newer-rustc-version/47528/2

Is this likely to be backported to NixOS 24.05? Seems the COSMIC desktop (which there's a test Flake for) now requires Rust 1.79.

Is this likely to be backported to NixOS 24.05?

No, unless a package that needs to be updated in 24.05 for security reasons (most likely Firefox) starts requiring it.


fix(portal): update prefix URL in EditPage component

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR updates the prefix variable in EditPage.tsx to point to a new GitHub URL.
Detailed summary

Updated the prefix variable URL in EditPage.tsx from docs-v2 to js for GitHub link.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#3962  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gregfromstl and the rest of your teammates on  Graphite


[Permissions] Not seeing permission request dialog

Description
I'm not seeing the permission request dialog when invoking "launchMultiplePermissionRequest()". I'm not sure if I'm doing something wrong or if this is a bug (I'm guessing the former). launchPermissionRequest()  also doesn't work for me.
Steps to reproduce
Create new android project.
add accompanist permissions,
copy paste RequestMultiplePermissionsSample code.
repro project: https://github.com/fluxxion82/permission_test
Expected behavior
User should see the permission request dialog.
Additional context
I've tested on a Pixel 4XL running Android 13, Pixel 8 running Android 14 and an emulated Pixel 7 running 14.

The READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE permissions do not have any effect on Android 13+ devices. As explained in the Android 13 behavior changes, you need to use the granular media permissions if you need any permissions at all for your use case (see the Storage Permissions page for more details).
Therefore you'd never see any permission request dialog for these permissions, whether you are using Accompanist or not.


Unable to compile?

Tried gcc test.c -L. -1:NimScanToC.a -w -o NimScan.exe
came up with heap of errors
is this the right command?

Updated the repo.
Can you try again?
Also, you used -1 and not -l

Yeah I actually use -l and it showed a long error. -1 does not work at all. not sure why i had that inaccurate description.
My error is here: https://paste.rs/S5D

Have you tried to recompile after the update?
What are your GCC and Nim versions?


Django 5 Error because of timezone.utc deprecation

On installed version Django 4.1 and django-auditlog 2.1.1 we are witnessing:

/usr/local/lib/python3.9/site-packages/auditlog/diff.py:67: RemovedInDjango50Warning: The django.utils.timezone.utc alias is deprecated. Please update your code to use datetime.timezone.utc instead.
value = timezone.make_naive(value, timezone=timezone.utc)

Seems like we are using this deprecated feature in 2 places

here
here
and here in the tests

Its simple to fix. Ive already done it in a couple projects I have.
Seems like a great beginners friendly issue!

Thanks @andrewgy8 for this issue.
Yes, it would be great!


Defaults for Union types are not encoded/decoded correctly

@TikhonJelvis I have bumped into an issue where default values for union types are not encoded/decoded in Schema in a way that they can be respected by decoding functionality.
For this schema:
{
        "type": "record",
        "name": "Inner",
        "fields": [
          { "name": "id", "type": "int" },
          { "name": "smell", "type": ["null", "string"], "default": null }
        ]
}

the expected Haskell representation would be:
Record
  { name = "Inner"
  , namespace = Nothing
  , aliases = []
  , doc = Nothing
  , order = Just Ascending
  , fields =
      [ Field
          { fldName = "id"
          , fldAliases = []
          , fldDoc = Nothing
          , fldOrder = Just Ascending
          , fldType = Int
          , fldDefault = Nothing
          }
      , Field
          { fldName = "smell"
          , fldAliases = []
          , fldDoc = Nothing
          , fldOrder = Just Ascending
          , fldType = Union {options = Null :| [String], unionLookup = <function>}, fldDefault = Just (Union (Null :| [String]) Null Null)}
      ]
  }

Note that the fldDefault is annotated with its type of Union Null String.
However the current implementation gives me this:
Record
  { name = "Inner"
  , namespace = Nothing
  , aliases = []
  , doc = Nothing
  , order = Just Ascending
  , fields =
      [ Field
          { fldName = "id"
          , fldAliases = []
          , fldDoc = Nothing
          , fldOrder = Just Ascending
          , fldType = Int
          , fldDefault = Nothing
          }
      , Field
          { fldName = "smell"
          , fldAliases = []
          , fldDoc = Nothing
          , fldOrder = Just Ascending
          , fldType = Union {options = Null :| [String], unionLookup = <function>}, fldDefault = Just Null}
      ]
  }

Which doesn't annotate the union type for the default value.
Looking at the code I see that it has been done deliberately.
Is there anything that I am missing or should we fix the type annotation back?

The error that I am currently getting is this:
Error "Unexpected value when decoding for 'Maybe a': Null"

Which is correct in a way, because Null is not of type Union.

I changed the union code to reflect the fact that the default value for a union has to be from the first branch of the union. It looks like this is an unintended consequence of that change.
I can't think of a way to fix this without special-casing unions one way or another. The simplest thing is probably wrapping the fldDefault value in the appropriate Union when building the Schema record.

I think we can fix type annotation back and it'll work again.
From what I see now the change is somewhere between 304ada7 (which works) and 15400f3 (which doesn't work).
I'll branch off 304ada7 to create <IP_ADDRESS> release (because I need to fix another unrelated bug for de-conflicting schemas) and then will try tracking it down and figuring out how to preserve the annotation.
Any help/advice is appreciated! :)

I can take a quick stab at fixing it for the 0.3.* version of the package.
I would like to preserve the new behavior because the old version did not match the Avro specification and the way it handled the logic caused me some problems. (I'd have to root around a bit for the exact details, but I was having trouble when it failed to match a NamedType against the complex type with the corresponding name.)
On a related note, I think it would be really helpful to continue making tags like v<IP_ADDRESS> for every release. It makes navigating through old version much easier, like finding which commit <IP_ADDRESS> was released at.

Tags are now done automatically every time CI detects a version change in the cabal file :) I think it'll continue to work.


Update ecr, kms, s3, ses, sfn, sns, sqs to 2.26.5 in scala-steward-dependencies

About this PR
📦 Updates

software.amazon.awssdk:ecr
software.amazon.awssdk:kms
software.amazon.awssdk:s3
software.amazon.awssdk:ses
software.amazon.awssdk:sfn
software.amazon.awssdk:sns
software.amazon.awssdk:sqs

from 2.26.3 to 2.26.5
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #438.


rnn_cell little bug fixed

When input is list of "NC" layout(i.e. split by time). The batch_axis should be 0.
Add HybidSequentialRNNCell, which can be nested in HybridBlock but SequentialRNNCell cannot.

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

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

Changes

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

Comments

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

@chinakook pinging again. It would be great if we could get this in. Would you address the review comments? Thanks.

@szha Is that all?

Rebasing like this? I've not very familiar with rebasing.

suppose you have a git remote called "upstream" (which you can get by doing git remote add upstream https://github.com/apache/incubator-mxnet), you can do git pull upstream master --rebase and then do a force push. You don't need to reopen the PR

@chinakook thanks for the contribution. @eric-haibin-lin I will add the test.


feat: expected end time / back time

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Adds support for timing to the end of a show by specifying the expected end of a playlist, and for timing to the next break by specifying the expected end time of the rundown and setting the endIsBreak property on the rundown.

What is the current behavior? (You can also link to an open issue here)

New feature.

What is the new behavior (if this is a feature change)?

If expectedEnd is specified for a rundown, it will be displayed as the "Planned End" time in the rundown divider. The same applies for the playlist level. (data used for screenshots is made up using a mock iNews script, so some values may not add up).

The timer to the left of "Planned End" in the rundown header will show by how much you are expected to be over/under your target end time. The "Expected start" will be worked out from the playlist expected end - playlist expected duration, to indicate when you should start the show to finish on time.
This PR also adds the property endIsBreak to rundowns. In the case of a rundown being marked with this property, when the rundown is active a timer counting down to the next break will be shown (if enabled in settings, see below). The timer will show (right to left) when the break is planned for, by how much over/under you're expected to be for the break, and the diff according to your planned duration (expected duration) of the rundowns between the current rundown and the end of the rundown marked as the next break. The timer will look ahead from the current rundown to find the next rundown marked as a break.

A number of settings are exposed by this PR to allow customizing which timers show and when, and what text to show on the timers.

In the above image you can see the following settings:

Expected End text: The text to show above the "Planned End" timer
Hide Expected End timing when a break is next: This allows the timer to "change" from showing the next break, to showing the end of the playlist based on whether there is a break coming up next or not when used in combination with "Last rundown is not break"
Show next break timing: Must be enabled for the "Next Break" timer to be shown
Last rundown is not break: If there's only one break in the future and it's on the last rundown, don't show the "Next Break" timer
Next break text: The text to show above the "Next Break" timer

Other information:

These changes build upon the work in https://github.com/nrkno/tv-automation-server-core/pull/537
Status

[ ] Code documentation for the relevant parts in the code have been added/updated by the PR author
[X] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

Codecov Report

Merging #540 (b26d2d6) into release36 (3c1050d) will increase coverage by 31.93%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           release36      #540       +/-   ##
===============================================
+ Coverage      68.06%   100.00%   +31.93%
===============================================
  Files            255         2      -253
  Lines          17099        46    -17053
  Branches        3851        16     -3835
===============================================
- Hits           11638        46    -11592
+ Misses          5424         0     -5424
+ Partials          37         0       -37

Impacted Files
Coverage Δ

meteor/lib/api/userActions.ts

meteor/server/api/buckets.ts

meteor/server/api/playout/lookahead/util.ts

meteor/lib/collections/PeripheralDevices.ts

meteor/server/cache/ActivationCache.ts

...eteor/server/api/playout/lookahead/findForLayer.ts

meteor/server/migration/0_18_0.ts

...eor/lib/collections/ExpectedPackageWorkStatuses.ts

meteor/client/lib/data/mos/plugin-support.ts

meteor/server/migration/databaseMigration.ts

... and 235 more

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 3c1050d...b26d2d6. Read the comment docs.


feat: table of contents on documentation

Closes #3867
Adds a new table of contents on the right side of the docs page based on prior work done in #4475 and does a few other things:

Moves the doc actions (edit, translate) from the footer to the header.
Disables https://github.com/electron/electronjs.org/pull/1053 (The duplicated DOM used by this selector doesn't play well with grabbing all of the headings in a page)

Nice addition! Works well, code looks good.
We could consider having a fixed "Table of contents" button on mobile viewports (where there is no place for the right sidebar) that opens and collapses the table of contents overlaid on the page (I do this on https://polypane.app/docs) but that can be a different ticket.


Split up the Nix interop

Separate the bit about calling Nickel (importNickel), and the one really about Organist (importOrganist).
Doesn't change anything semantically, but

Makes the flow (hopefully) clearer
Allow exporting a lower-level importNickel function that just calls Nickel and imports back the result without the Organist magic

Depends on #203

I think there's an importNcl left somewhere in lib/lib.nix within a comment; a search and replace might get rid of those.

Indeed, a quick grep found a few extras in the documentation, thanks.

Otherwise, I know it's provided as it is, but maybe a bit more documentation on what importNickel is doing so that non-organist users can make something out of it could be nice. But doesn't have to be in this PR, even if it can.

That's fair. I've added a quick blurb to the function. I don't think it deserves much right now (it's still a bit coupled with Organist, so not producion-ready as an independent thing).


Adding in paymentMethod prop to embedded ui

paymentMethod wasn't being used in crossmintPaymentService. Adding the prop according to the docs and updating the type to match the docs.

Hey @jhubbardsf ,
First of all, thanks a lot for chiming in and contribute! ❤
I agree there is a misalignment between the docs and the code, but in this case is the docs that are not correct! Google pay and Apple pay are enabled by default. No need to set this field for anything.
We will remove that field from the docs shortly, cause it has a different intention.
Thanks again and sorry for the confusion!

@pgarciaegido Thanks for the clarification!


[DialogTitle] Documentation default variant different from default rendered

In the documentation the default component rendered for DialogTilte is an h2 but an h6 is the default rendered element.

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔

Based on documentation the default element rendered for DialogTitle is an h2 element.

Current Behavior 😯

The default element rendered is an h6
Steps to Reproduce 🕹

Link:

https://codesandbox.io/s/create-react-app-ns87j
examples on https://material-ui.com/components/dialogs/

Context 🔦

To make our application more accessible, while also making it easier for people to contribute without a large knowledge base of accessibility.
Your Environment 🌎

Tech
Version

Material-UI
v4.1.1

React
v 16.8.6

Browser
Chrome v75.0

etc.

@dayander Do you mean that we should change the description from default h2 to h6?

@oliviertassinari I think the default should be an h2 and match the documentation. Rendering as an h2 is best practice for accessibility.

Do you have resources on why h2?

https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/dialog.html uses h2
https://getbootstrap.com/docs/4.3/components/modal/ uses h5
https://allyjs.io/tutorials/accessible-dialog.html#interactive-demo uses h1

https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/dialog.html
WAI-ARIA is one of the working groups that decide accessibility standards. I think it's best practice to follow what they do.

Google owns Youtube and has people contributing to the working group for WAI-ARIA.
Bootstrap is not a source for accessibility.
Each page should contain one h1 denoting the whole meaning of the page. The next consecutive order after an h1 is h2. When the dialog becomes an overlay over the current page and should still fall under the content scope of the h1 and the next heading level should be an h2.

Is this written down somewhere? What's the impact?

On a different note, Bootstrap has https://github.com/cvrebert as a contributor, he has done more than 200 commits one topics that seem related to accessibility, he is a member of the WCAG. It's not all that bad.

Hey, I was just chatting with @dayander a little bit about this and thought I could chime in with a few more resources to look at.
The higher the ranking of the header, the less important it is on the page. A heading element should never exceed h6. Although theoretically you can go higher, and some screen readers may support it, the results can be unpredictable with other browser/screen reader combinations. 1
If the dialog header begins at h6, this can cause issues for screen readers if any other headers need to be added to the same dialog, as they would have to be an h7 or higher. 2
Another resource for this information can be found here: https://www.w3.org/WAI/tutorials/page-structure/headings/

@Auchindoun Thanks, that sounds good to me, the change could be:
diff --git a/packages/material-ui/src/DialogTitle/DialogTitle.js b/packages/material-ui/src/DialogTitle/DialogTitle.js
index f3cc523ce..e877b67b4 100644
--- a/packages/material-ui/src/DialogTitle/DialogTitle.js
+++ b/packages/material-ui/src/DialogTitle/DialogTitle.js
@@ -18,7 +18,7 @@ const DialogTitle = React.forwardRef(function DialogTitle(props, ref) {

   return (

-      {disableTypography ? children : <Typography variant="h6">{children}</Typography>}
+      {disableTypography ? children : <Typography component="h2" variant="h6">{children}</Typography>}

   );
 });

That sounds great. Thank you. I will make the changes and open a PR.

Why is the h2 component given a class that renders it with h6 typography?
Dialog Title text

@shiraze I don't understand. What do you mean?

@oliviertassinari , sorry I just re-read what I said and it's not clear!
I have jsx with <DialogTitle>Dialog Title text</DialogTitle> which renders in the browser as

Dialog Title text

The inner component is an h2 but the css class applied to it (MuiTypography-h6) renders it as an h6

@shiraze Yes, it's the expected behavior. Does https://material-ui.com/components/typography/#changing-the-semantic-element make it clearer?

what's the cleanest way to override this h6 variant and use h2 instead, from the global overrides object? thanks

@ghan Upgrade to v4 or target DialogTitle with https://material-ui.com/customization/globals/#default-props.

Hi Oliver, thanks for responding. My question was a little vague, I apologize. I'm on v4.5 and wanted to have
, not
 globally. I've added my current workaround... I'm hoping there's a cleaner solution out there:
const theme = createMuiTheme({     ...     props: {         MuiDialogTitle: {             disableTypography: true         }     },     overrides: {         MuiDialogTitle: {             root: {                 fontFamily: headerFont,                 fontSize: headerSize,                 fontWeight: headerWeight,                 lineHeight: headerLineheight             }         }     } ... }
Thanks, let me know if you guys do something smarter.

@ghan I'm sorry, It still unclear what's your objective, I would suggest you to try StackOverlow.

Hi @oliviertassinari, regarding @ghan 's use case. I actually came across the very exact issue.
Let me try explaining the issue in a different way.
Although the DialogTitle allows us to customize the Typography component used within DialogType through disableTypography (like change the rendered variant h6 to h3), the current API does not allow us to change all DialogTitle's Typography component globally due to hardcoding in this line:
https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/DialogTitle/DialogTitle.js#L24...
If we wanted to keep all DialogTitle's rendering H3's, we would have to disableTypography in every Dialog...
A possible solution might be to add a prop to DialogTitle called 'variant' which maps to
<Typography component="h2" variant={variant}>
And just default with h6... Then make sure the global theme api can use
theme = {
    props: {
        DialogTitle: {
            variant: 'h3' <--- Or anything required
        },
}

.... I came across this issue myself. I thought it was possible through some sort of api like
theme = {
    props: {
        DialogTitle: {
            children: props => <Typography component="h2" variant="h3">{props.children}</Typography>
        },
}

But that's not the case! :D
I can try to clarify it again if needed!

Yes, I am also running into this issue. @KyruCabading proposed solution is exactly what I would have expected this component to support from the get-go. This would be a very useful update!


Updated documentation for addr_uri argument in AddListeningPort.

Removed extraneous bracket and random (stray ?) slash.

@nicolasnoble

Thank you for the PR!


Support RegExp for hasQuery name

URI.hasQuery does not allow RegExp for parameter names like for values. The following would be a nice complement to the RegExp support in URI.removeQuery:
var uri = URI("http://example.org/?foo[bar]=1&foo[qux]=2");

uri.hasQuery(/^foo/); // true
uri.hasQuery(/^baz/); // false

feel free to send a PR for changing URI.hasQuery and its test accordingly

@rodneyrehm Should be straightforward, I'll give it a try.

thank you! :)


CODEOWNERS file syntax documentation does not make it explicitly clear that a pattern can only be used once

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
What changes are you suggesting?
The existing documentation for file syntax does not make it explicitly clear that a pattern can only be specified once, and that if >1 instance of a pattern is present, the last instance will take precedence.
For example the following example would only request review from @doctocat, @octocat would not be included in the reviewers.
apps/ @octocat
apps/ @doctocat

I would propose that a line be added to the CODEOWNERS syntax section indicating that a repeated pattern is not supported.
Additional information
Additionally, I believe an issue should be raised internally against the validation of codeowners files - the above example will be marked as valid by the CODEOWNERS validation, and will not provide any indication to the end user that only the last instance of the pattern will be used.

Thanks @ReidWeb! We can definitely mention that if you want to list two code owners for the same pattern, they should be on the same line, because listing them twice will fall prey to the "last matching pattern takes the most precedence" rule. 👍🏻 You or anyone else is welcome to open a PR for that!

I would like to work on this issue!

@nawed2611 You or anyone else is welcome to work on this issue! 💖


Proposal for an IO interpreter

After composing the API, we need to convert the resulting data structure into executable IOs. Propose a simple interpreter (a function from Behaviour[A] to IO[A]) to test our examples and see them running

What about Sink, as defined in Chapter 8 of the paper? Something about Events is implemented, extend it for Behaviour.

Proposal: implement Sink, as defined in chapter 8 in the book - see https://github.com/scalaz/scalaz-reactive/blob/d1cc9027658527e4436c665e14d489cbf9c21f79/core/src/main/scala/scalaz/reactive/Sink.scala
Given that at the moment our Future is an IO, Sink naturally produces another IO[Void,()].


Robot configuration  not clear

I'm beginner with FANUC.
I put all sources to my robot project. Compile is okay.
I didn't find anything where I put in the configuration data, which are described:

Global DPM configuration
Schedule1, channel 1,2 and 3 configuration

Would be helpful to tell me where I can input the configuration data

Ok. First thing to check: do you have the R739 option?
Information on the installed software options can be found by consulting the documentation that came with your robot. Alternatively, the Version ID submenu of the STATUS screen can be used. On the TP: Menu→NEXT→STATUS→Version ID, then CONFIG (or F3). The same information is available on the Summary Configuration/Status webpage, which should be accessible if your controller has the web server option installed.

I'm going to close this due to no activity.
If you still run into the same issue(s), comment and we can re-open.

hi, @gavanderhoorn @MeisterTom  ,I met the same problem. firstly, I am sure the robot have the R739 option.

But I did not find the exactly config as you mentioned.

And this is my DPM config items as show below, looks very different from yours.

So, I have two problem:

Where is the config interface as you mentioned in readme? It shoud be looks like as image show below, but I did not find it.

You mentioned the manual <Refer to the Fanuc Dynamic Path Modification User's Guide (MARUBDPMO02141E)>. Can you send it to me please, my email is<EMAIL_ADDRESS>

@eyes366: please post in the Discussion forum. Additional comments under an already closed issue are not a good idea.


will elementary compatible with dbt-spark package

Describe the gap
will elementary compatible with dbt-spark package

@Maayan-s can somebody please answer on same

Hi @gargvipul1349 !
While Elementary does work for some users with dbt-spark, unfortunately at this point it's not an officially supported contribution and is not actively maintained by the Elementary team, and I cannot guarantee a timeline for it.
That being said, you can try to see if it works for you and also feel free to consult with members in the community slack
Thanks,
Itamar


OCH Mind Dump

Discuss:

Requirements
Users / Data Consumers
Query API
Startup configuration and supported scopes
Storage backend

Business case & context
Buzz words
Sub-tasks
Context and prerequisite definition
Out of scope
Acceptance criteria
Quality


[1.12.2] Linux crash running FTBI, fails to register FileSystemWatcher

Crashlog: https://mclo.gs/tezeo4D
Fails with a generic NullPointerException, helpful. Running a slim pack with CC in a debugger grants the following info.
It fails in FileSystemWatcher where it tries to register a new file system watcher here:
tmp = FileSystems.getDefault().newWatchService();
With this debug pointer I can see the message java.io.IOException: User limit of inotify instances reached or too many open files
The specific crash reason is something I can fix up my side. However, it would be good if CC could fail more gracefully and surface this error message more easily.

O.o how the fluff did we reach the Filesystem watching limit? O.o
That is interesting.
Yeah I am not at home so can't fix it today.
But it's a thing I will fix on Monday the moment I am awake!
Ty for the report

I don't know why/how we reached it, but I think running apps like Intellij Idea in the background take up a large number. It's easy enough to raise the limit, but I had to dig into source code to see what the error message was


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_bfltqruxjk/clone/recipe/meta.yaml:25: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_bfltqruxjk/clone/recipe/meta.yaml:31: missing_pip_check: For pypi packages, pip check should be present in the test commands
WARNING: /tmp/abs_bfltqruxjk/clone/recipe/meta.yaml:40: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
WARNING: /tmp/abs_bfltqruxjk/clone/recipe/meta.yaml:40: missing_description: The recipe is missing a description
Errors were found


Can it run in iPadOS?

How it run on iPadOS?

/question
AFAIK this is only possible when you use the Online / Browser / Web variant. Maybe start here.
https://docs.microsoft.com/en-gb/visualstudio/online/quickstarts/browser


Added ability to disable DelegateFactory for TypedFaciliy.

This modification allows the disabilitation of DelegateFactory, this imply
that, if an object has a dependency from Func it gets registered with
TypedFactory only if someone explicitly register Func with code
Container.Register(Component.For<Func>().AsFactory());

@alkampfergit - Is there an issue we can link this back to?

@alkampfergit without an issue describing the problem this is attempting to fix I'm now going to close this pull request. Looking at the included unit test I wonder if making it facility wide is the right choice, per factory registration is probably where it belongs.


Legrand Dimmer switch w/o neutral for sw_build_id=0x0039 with and without Ballast cluster

Fixes #1127

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 80.03%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
4328

Relevant Lines:
5408

💛  - Coveralls

Codecov Report

Merging #1128 (3318033) into dev (02aeb29) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev    #1128      +/-   ##
==========================================
+ Coverage   80.00%   80.02%   +0.02%
==========================================
  Files         197      197
  Lines        5401     5408       +7
==========================================
+ Hits         4321     4328       +7
  Misses       1080     1080

Impacted Files
Coverage Δ

zhaquirks/legrand/dimmer.py
100.00% <100.00%> (ø)

zhaquirks/ikea/shortcutbtn.py
100.00% <0.00%> (ø)

zhaquirks/tuya/__init__.py
72.80% <0.00%> (+0.11%)
:arrow_up:

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 02aeb29...3318033. Read the comment docs.


Unable to install AngularJs on Windows 7

Hi,
I'm trying to setup development environment for AngularJS. After repeated attempts it fails with the below message:
C:\angular.js>npm install
npm ERR! git rev-list -n1 ced17cbe52c1412b2ada53160432a5b681f37cd7: fatal: bad o
bject ced17cbe52c1412b2ada53160432a5b681f37cd7
npm ERR! git rev-list -n1 ced17cbe52c1412b2ada53160432a5b681f37cd7:
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\nodejs\\\\node.exe" "C:\\nodejs\\node_modules\\npm\\bin\\npm-
cli.js" "install"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code 128

npm ERR! Command failed: git -c core.longpaths=true rev-list -n1 ced17cbe52c1412
b2ada53160432a5b681f37cd7
npm ERR! fatal: bad object ced17cbe52c1412b2ada53160432a5b681f37cd7
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     C:\angular.js\npm-debug.log

npm debug.log file contains the below(Last few lines)
3357 verbose etag https://registry.npmjs.org/dgeni-packages from cache
3358 verbose get saving dgeni-packages to C:\Users\002812\AppData\Roaming\npm-cache\registry.npmjs.org\dgeni-packages\.cache.json
3359 silly cache afterAdd<EMAIL_ADDRESS>3360 verbose afterAdd C:\Users\002812\AppData\Roaming\npm-cache\dgeni-packages\0.10.17\package\package.json not in flight; writing
3361 verbose afterAdd C:\Users\002812\AppData\Roaming\npm-cache\dgeni-packages\0.10.17\package\package.json written
3362 verbose stack Error: Command failed: git -c core.longpaths=true rev-list -n1 ced17cbe52c1412b2ada53160432a5b681f37cd7
3362 verbose stack fatal: bad object ced17cbe52c1412b2ada53160432a5b681f37cd7
3362 verbose stack
3362 verbose stack     at ChildProcess.exithandler (child_process.js:751:12)
3362 verbose stack     at ChildProcess.emit (events.js:110:17)
3362 verbose stack     at maybeClose (child_process.js:1015:16)
3362 verbose stack     at Socket.<anonymous> (child_process.js:1183:11)
3362 verbose stack     at Socket.emit (events.js:107:17)
3362 verbose stack     at Pipe.close (net.js:485:12)
3363 verbose cwd C:\angular.js
3364 error Windows_NT 6.1.7601
3365 error argv "C:\\nodejs\\\\node.exe" "C:\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
3366 error node v0.12.7
3367 error npm  v2.11.3
3368 error code 128
3369 error Command failed: git -c core.longpaths=true rev-list -n1 ced17cbe52c1412b2ada53160432a5b681f37cd7
3369 error fatal: bad object ced17cbe52c1412b2ada53160432a5b681f37cd7
3370 error If you need help, you may report this error at:
3370 error     <https://github.com/npm/npm/issues>
3371 verbose exit [ 1, true ]

I don't see any angular related error there. Maybe something is wrong with your environment? A git command seems to have failed.

Resolved!
Issue was with devDependencies "grunt-jasmine-node" mentioned in angularjs package.json file.
Changed it from "grunt-jasmine-node": "git://github.com/vojtajina/grunt-jasmine-node.git#fix-grunt-exit-code" to "grunt-jasmine-node": "~2.0.1"
grunt-jasmine-node was the referring to the fatal object

Good to hear! I just tested it too, no problems here.


feat: add use case of LLM on food review running on colab

How do I add a colab link in the notebook? Is it just HTML?


null Showing up in Nextjs console

Bug report
Describe the bug
Right after running npm run dev without visiting any app pages in my browser, null will start to show up on my server console.
To Reproduce

npm run dev
Don't view any app pages
Just wait and watch server console

Expected behavior
No null logs
Screenshots

System information

OS: Windows 10
Version of Next.js: 8.0.3

We cannot reproduce this on canary. Are you sure this isn't caused by a customization in next.config.js?
The only way we'll be able to inspect this further is if you provide a repository with a reproduction.
Thanks!


Build fails for want of xxd

Need to include the xxd command as a dependency shown in BUILD.md. In Gentoo Linux it's provided by app-editors/vim; other distros may vary but I suspect it's the case across the board.

Thanks @MincingWords, this is a known issue. I'll add it in BUILD.md.


blood form

The Blood Investigations Form was already updated.
Please check: https://github.com/ServiceToMankind/STM-medical-camp-management/commit/dbeb65186bb4f569236783359920bfec4e4f1cff


Is A-OKVQA support discontinued?

A while back A-OKVQA was supported, and I did try that out. Now, I am not seeing that in the ImageMCQDataset class.
https://github.com/open-compass/VLMEvalKit/blob/058f6733a82954fd4c8c72dfc22c6b3881c93638/vlmeval/dataset/image_mcq.py#L43

Hi @MOSHIIUR. Sorry for accidentally deleting the link to the file due to our mistake, we've added it here (https://github.com/open-compass/VLMEvalKit/blob/main/vlmeval/dataset/image_mcq.py#L94), thank you very much for reminding us!


feat: skip branch unprotect/protect if values are unchanged

Skip branch unprotect/protect if the same values are already set.
This will fix egnyte#178

Thanks for your contribution, @YuraBeznos ! :) Please check and fix, if necessary, the failing tests.

Hey @YuraBeznos ! Version 2 of GitLabForm will be released with days so it would be great if you could rebase your branch against v2 and target your PR to that branch. Can you do that please?

Hey @YuraBeznos ! Version 2 of GitLabForm will be released with days so it would be great if you could rebase your branch against v2 and target your PR to that branch. Can you do that please?

I tried, but looks like made it wrong :)

I think that it will be easier to create a new branch from v2, cherry-pick your commit 3134dfe there and then force-push to the source branch of this PR.

Right now should be better.

LGTM, thanks for your contribution @YuraBeznos !


CORS error No 'Access-Control-Allow-Origin' header is present on the requested resource

Hi Everybody,
I am newbie in spring cloud, today when I setup my project and deploy to server, I have error when call API from localhost to server bellow:

Access to XMLHttpRequest at 'xxxx/api/authentication/send-sign-in-code' from origin 'http://localhost:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

This is my config in application.properties
spring.application.name=gateway
server.port=3012
spring.main.allow-bean-definition-overriding=true

eureka.registerWithEureka=true
eureka.fetchRegistry=true
eureka.client.serviceUrl.defaultZone=http://localhost:1313/eureka

AUTHENTICATION_URL=http://localhost:3011

spring.cloud.gateway.defaultFilters=DedupeResponseHeader=Access-Control-Allow-Origin Access-Control-Allow-Credentials, RETAIN_UNIQUE
spring.cloud.gateway.globalCors.corsConfigurations.[/**].allowedOrigins=*
spring.cloud.gateway.globalCors.corsConfigurations.[/**].allowedMethods=*
spring.cloud.gateway.globalCors.corsConfigurations.[/**].allowedHeaders=*
spring.cloud.gateway.globalCors.corsConfigurations.[/**].allowCredentials=true

And I saw log in server:
java.lang.IllegalArgumentException: When allowCredentials is true, allowedOrigins cannot contain the special value "*" since that cannot be set on the "Access-Control-Allow-Origin" response header. To allow credentials to a set of origins, list them explicitly or consider using "allowedOriginPatterns" instead.
        at org.springframework.web.cors.CorsConfiguration.validateAllowCredentials(CorsConfiguration.java:538) ~[spring-web-6.0.13.jar:6.0.13]
        Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Error has been observed at the following site(s):
        *__checkpoint ⇢ org.springframework.cloud.gateway.filter.WeightCalculatorWebFilter [DefaultWebFilterChain]
        *__checkpoint ⇢ HTTP OPTIONS "/api/authentication/send-sign-in-code" [ExceptionHandlingWebHandler]

I then changed my configuration back and allowed localhost in allowedOrigins :
spring.cloud.gateway.globalCors.corsConfigurations.[/**].allowedOrigins=http://localhost:3000
and I got another error
Access to XMLHttpRequest at 'xxxxxx/api/authentication/send-sign-in-code' from origin 'http://localhost:3000' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values 'http://localhost:3000, *', but only one is allowed.
i spent all day looking for the solution but couldn't find it, please help me, thanks

@KhanamDEV - As the error message clearly indicates you are sending multiple values in the header Access-Control-Allow-Origin. Try sending just  http://localhost:3000 instead of http://localhost:3000, *

First, the message indicates that the error is because of the multiple values in the header Access-Control-Allow-Origin, and it should only contain one value.
Then, we need to find out why it contains two values. If you can ensure that you only set one value in spring cloud gateway, as spring.cloud.gateway.globalCors.corsConfigurations.[/**].allowedOrigins=http://localhost:3000 , then the problem is in your backend application. Your backend application set the header Access-Control-Allow-Origin to *, that's the core.
So the solution is not to set the header in your backend application.

This error should be resolved in the backend.  The cors error doesn't appear when both the frontend and the backend are at the same url.  The most important thing to pay attention to is setting the frontend port
config.addAllowedOrigin (*)
@Configuration
@EnableWebMvc
public class CorsConfig {
@Bean
public FilterRegistrationBean corsFilter() {
    UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();
    CorsConfiguration config = new CorsConfiguration();
    config.setAllowCredentials(true);
    config.addAllowedOrigin("http://localhost:3000");
    config.setAllowedHeaders(Arrays.asList(
            HttpHeaders.AUTHORIZATION,
            HttpHeaders.CONTENT_TYPE,
            HttpHeaders.ACCEPT));
    config.setAllowedMethods(Arrays.asList(
            HttpMethod.GET.name(),
            HttpMethod.POST.name(),
            HttpMethod.PUT.name(),
            HttpMethod.DELETE.name()));
    config.setMaxAge(3600L);
    source.registerCorsConfiguration("/**", config);
    FilterRegistrationBean bean = new FilterRegistrationBean(new CorsFilter(source));
    bean.setOrder(-100);
    return bean;
}


What condition the condition is in...

Basically code is working in one direction (single site) or the other (multisite, subdomain/directory), but NOT both.
So far changes to the conditionals let one line work, but the cause things to error out on the unused set. Looking into a group_by structure to solve the issue.
That aside, the individual parts are functional.

Going in a different direction.


[FEA] Support FromUTCTimestamp

I wish we can Support FromUTCTimestamp
Reproduce:
import org.apache.spark.sql.functions._
import spark.implicits._
import org.apache.spark.sql.types._

var df = spark.sparkContext.parallelize(Seq(1)).toDF()
df=df.withColumn("value82", (lit("123456.78").cast(DecimalType(8,2)))).
           withColumn("value63", (lit("123.456").cast(DecimalType(6,3)))).
           withColumn("value1510", (lit("12345.0123456789").cast(DecimalType(15,10)))).
           withColumn("value2510", (lit("123456789012345.0123456789").cast(DecimalType(25,10)))).
           withColumn("value2901", (lit("1234567890123456789012345678.1").cast(DecimalType(29,1)))).
           withColumn("value3802", (lit("123456789012345678901234567890123456.01").cast(DecimalType(38,2)))).
           withColumn("timestring", (lit("1997-02-28 10:30:00.012")))

df.write.format("parquet").mode("overwrite").save("/tmp/df.parquet")
df=spark.read.parquet("/tmp/df.parquet")
df.createOrReplaceTempView("df")

spark.sql("SELECT from_utc_timestamp(timestring,'UTC') FROM df").collect

Not-supported-messages:
! <FromUTCTimestamp> from_utc_timestamp(cast(timestring#420 as timestamp), UTC) cannot run on GPU because GPU does not currently support the operator class org.apache.spark.sql.catalyst.expressions.FromUTCTimestamp
      !Expression <Cast> cast(timestring#420 as timestamp) cannot run on GPU because the GPU only supports a subset of formats when casting strings to timestamps. Refer to the CAST documentation for more details. To enable this operation on the GPU, set spark.rapids.sql.castStringToTimestamp.enabled to true.; Parsing the full rage of supported years is not supported. If your years are limited to 4 positive digits set spark.rapids.sql.hasExtendedYearValues to false.

@viadea In the example above it looks like there is a conversion from a UTC timestamp to a UTC timestamp.  Is that what is required, or do we expect the second parameter to be another timezone like Asia/Seoul?  And if the second parameter is expected to be something other than UTC, will it always be a literal or will it be a column?

The real use case is like below:
from_utc_timestamp(cast(date_format(xxx, Some(Etc/UTC)) as timestamp), UTC)

So above is just my minimum reproduce.
I can ask about the second parameter which is the timezone


Add instructions to consume other file formats that are not directly supported by devfile

/area documentation
Which area this documentation change is related to?
/area api
Issue details
What mistake did you find / what is missing in the documentation?
Add instructions to exec other tools or consume other file formats that are not directly supported by devfile. There are many other configuration files or systems that an existing customer may be using, e.g. helm, tilt, dev container, etc. The devfile specification may not have a native way to include those configuration files as part of the devfile (similar to kubernetes yaml in the kubernetes component or dockerfile in the image component).
However, the user will still be able to execute those when running the devfile by:

creating their own container to contain the tools requires to run those configuration files
create an exec command to run those configuration files within the container

This instruction will walk-through an example to help user to understand how to consume other configuration files in a devfile.

This is a nice item. I've added it as a devtools week item.


Add joint_offsets to ar_gazebo file

I noticed that ar_gazebo won't launch after the recent inclusion of the joint_offsets.yaml file.
Looks like my editor auto-formatted the file as well. Hope that's OK.

had same problem !


Host the readme images on imgur

Is your feature request related to a problem? Please describe.
10 images(670 kb) were added to the repository in https://github.com/creativecommons/ccsearch-browser-extension/pull/156. Their size is more than that of src/ directory (which also has the license and provider images).
Describe the solution you'd like
Upload the image to Imgur and edit the readme to update the images src. Make sure to link the right image in the right place.

Hi @makkoncept , Can I work on this issue ?

@lakshaybits go ahead.

@lakshaybits Hey, are you still working on this?

@preetmishra  Yes, actually i have exams going on, so i was not able to give much time. I will complete it in a day or two.

@lakshaybits Alright.


Generics don't work with this in classes

TypeScript Version:  3.4.0-dev.201xxxxx

Search Terms:
generics, class, this
Code
class Cmp {
  $events: {
    click: (arg: string) => boolean
  }

  constructor (fn: (arg: string) => boolean) {
    this.$events = {
      click: fn
    }
  }

  created() {
    const a: ReturnType<this['$events']['click']> = true
    console.log(a)
  }
}

const a = new Cmp(arg => arg === 'hello')
a.created()

Expected behavior:
Should compile successfully
Actual behavior:
error TS2322: Type 'true' is not assignable to type 'ReturnType<this["$events"]["click"]>'.

Playground Link

If I don't use Generics - it works fine.
class Cmp {
  $events: {
    click: (arg: string) => boolean
  }

  constructor (fn: (arg: string) => boolean) {
    this.$events = {
      click: fn
    }
  }

  created() {
    const a: this['$events']['click'] = arg => arg === 'hello'
    console.log(a)
  }
}

const a = new Cmp(arg => arg === 'hello')
a.created()

You can workaround it simply by specifying class name instead of 'this':
const a: ReturnType<Cmp['$events']['click']> = true

Your sample can be simplified:
type R<T> = T extends (...args: any[]) => infer R ? R : any;

class Cmp {
  click: (arg: string) => boolean;

  a: R<this['click']> = true;
  b: R<Cmp['click']> = true;
}

Maybe the problem here is with polymorphic this.

@NN---, that won't help if you use this in a parent class that refers to a property from the child class.

@NN---, that won't help if you use this in a parent class that refers to a property from the child class.

When you have a this type involved (not a this value, as in the later comment), the compiler correctly accounts for the fact that you might be violated a derived class contract to return a more specific value -- a class derived from Cmp might legally define $events: { click: (arg: string) => false; };, which a would be breaking.
The "fix" if you don't care about that (which would be totally reasonable!) would be to just write
const a: ReturnType<Cmp['$events']['click']> = true

instead of
const a: ReturnType<this['$events']['click']> = true


Attempt to fix version dropdown by re-adding Bootstrap v4.5.3

This is an attempt to fix #281.

@amotl I think readding those won't make it work again, this is the one we need: https://github.com/crate/crate-docs-theme/blob/69b41069f4c5ee8981b1d1f098b7f1e7bbc6b968/src/crate/theme/rtd/crate/static/js/webflow.js

Thank you. Closing this in favor of #283.


Support andreas-berg fork of entso-e integration

Hi,
Thank you for your work on this integration!
I'm using a fork of the entso-e integration (https://github.com/andreas-berg/hass-entsoe-dayahead) which is better maintained than the original one. However the electricity price structure does not match the format of the original integration. When I attempt to add the data to the ev_smart_charging device it I get the following error:

Would it be possible to add support for this integration?
Kind regards

Hi guys, @acejoh got me interested in the ev_smart_charging and the possibility to integrate the hass-entsoe-dayahead (a fork of JaccoRs original but seemingly unmaintained) component.
This component currently only provides two sensors: todays prices (in the configured timezone) and tomorrows prices (same TZ, empty array when tomorrow not available).
In both cases, the sensor value is in the simplest way possible, arrays of floats.
The European electricity markets will change (of course not all at the same time, where would be the fun in that ;)) to a 15-min slot and this will not break this array but it will break any client logic that expects the data in 1h slots.
@jonasbkarlsson If you have a clear preference on new stable interface, pls let me know and I'd be happy to implement this in the hass-entsoe-dayahead.

Support of template sensors in v1.11.0.
If you make a template sensor that will work with fork https://github.com/andreas-berg/hass-entsoe-dayahead, please post it here.
Or if @andreas-berg would like to implement this price information format in that fork.


Cannot start the bot...

Hey, I got the bot today and I tried to start it after installing the dependencies, but I got this error when starting server.js.
module.js:544
throw err;
^Error: Cannot find module 'pako'

Could someone tell me how to correct it?
Thanks,
FHGDev

Install the module pako with npm install pako and doesn't seem to be an actual issue with this bot as it doesn't use pako.


[Home Assistant Sensors] inline config, add icons, quotes unification

Instead of uploading a separate config file, adjust the code directly during customization.
Add icons depending on level+state: Home Assistant already uses a level-dependent icon, but doesn't know the sensors belong together, so doesn't add a charging indicator.
Cleanup: use double quotes everywhere, instead of randomly mixed ' and "

Nice - thanks!


chore: update chainsafe dependencies

Motivation
Keep chainsafe dependencies up to date
Description

update dependencies
clean up yarn lock

:tada: This PR is included in v1.16.0 :tada:


Added New Relational Database Language 'Microsoft SQL Server'

This pull request is for issue #56 [FEATURE] Add more Database Languages.
Added Resource Card 'Microsoft SQL Server' and 5 resource links along with it to Database.js.
Added SideBarSubtitle 'Microsoft SQL Server' with link to https://www.techroadmap.xyz/backend#microsoftsqlserver to BackendNav.js.

Thank you for your pull request @Joeyg61703. everything looks good. and I will merge it now. Please star our repo if you haven't yet. 😄.

@all-contributors please add @Joeyg61703  for  data, code and content


Remove unnecessary logic based on orientation to really fix #2

I don't really know what last update should fix, but it did not help on my device. So I am sharing my fix.
As I already explained in issue #2 flutter layout listener should be aware of orientation and width & height should be set. You dont need any extra logic there

Thanks for the PR but this won't make the sizes (.h, .w, .sp) stay the same when changing from portrait to landscape orientation. You could reproduce this by setting a Container's width and height using .w and .h and then rotate your phone to go landscape mode.

.h and .w should not stay the same...thats the whole point of this PR...they should come from actual orientation.
With .sp I agree, its bad implementation to get .sp from width only...it should be ration of width AND height. Will do some fix about it.
And just tested your example, which works correctly with this PR:
12.5% Height and 50 % width
With current code it would use 50% height and 12.5% width in landscape!

Thanks for helping me improve this package. I also agree that the .sp implementation could be improved. I'm sorry I couldn't merge your PR because there are many instances where .h and .w shouldn't come from the actual orientation. An example would be with images, we don't want the image's height and width to change drastically when changing orientation like what happened to the container above. If you want to use your version of responsive_sizer, feel free to fork my package and create a new one. This video helped me publish my first package: https://www.youtube.com/watch?v=6OqXMPbDCik

Sure np I can release it separately. But that make no sense...
If you want to have image (logo) for example present on top of your screen with width = 80% and height = 20%
And you move it to landscape...with your code you will have 20% width and 80 % height.... ie when in first situation user could see 80% of content (form for example) not he will see 20%...
Actual viewport and available space, thats all what matters. Anyway will continue my journey elsewhere///
Wish you all the best then

I get what you're trying to do with the widget having the actual width and height  during landscape mode but I wanted to be able to make the container have the same dimensions regardless of the orientation. I wish you the best with your separate package.


[Improve][Connector-V2][Influxdb] Unified exception for influxdb source & sink connector

Purpose of this pull request
sub-task of #2930
close #3535

Check list

[x] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

@TyrantLucifer @Hisoka-X PTAL, thanks


Pagination not working - Pass options.removeUndefinedValues=true to remove undefined values

Unable to use pagination using next tokens
I am trying to implement pagination using GSI. First find query works fine without providing next. When I add next param, i am getting error Pass options.removeUndefinedValues=true to remove undefined values from map/array/set.
I have following schema
export const InstallationSavesSchema = {
  format: "onetable:1.1.0",
  version: "0.0.1",
  indexes: {
    primary: { hash: "PK" },
    GSI1: { hash: "G1PK", sort: "G1SK" },
    GSI2: { hash: "G2PK", sort: "G2SK" },
  },
  params: {
    typeField: "_type",
    timestamps: true,
    isoDates: true,
    createdField: "createdAt",
    updatedField: "updatedAt",
  },
  models: {
    InstallationSave: {
      PK: { type: String, hidden: true, value: "installationUuid#${installationUuid}#itemUuid#${itemUuid}" },
      installationUuid: { type: String, required: true },
      itemUuid: { type: String, required: true },
      typename: {
        type: String,
        enum: Object.values(InstallationSaveTypes),
        required: true,
      },
      placeUuid: { type: String, required: true },
      createdAt: { type: Date },
      updatedAt: { type: Date },
      G1PK: {
        type: String,
        hidden: true,
        value: "installationUuid#${installationUuid}#placeUuid#${placeUuid}",
      },
      G1SK: {
        type: String,
        hidden: true,
        value: "typename#${typename}",
      },
      G2PK: {
        type: String,
        hidden: true,
        value: "installationUuid#${installationUuid}",
      },
      G2SK: {
        type: String,
        hidden: true,
        value: "createdAt#${createdAt}",
      },
    },
  } as const,
};

When I use find method on this schema without next, it works fine
const saves0 = await this.modelInstallationSave.find(
      {
        G1PK: `installationUuid#${installationUuid}#placeUuid#${placeUuid}`,
      },
      {
        limit: pageSize,
        index: "GSI1",
      }
    );

// output of saves0.next
   // next =  "next": {
   //     "G1SK": "typename#LANDMARK",
    //    "PK": "installationUuid#123#itemUuid#SAO_PAULO_CASA_DAS_ROSAS",
    //    "G1PK": "installationUuid#123#placeUuid#9ed982b6-5ef0-43fe-b178-27e44acae5fd"
    //}

just right after this query, i exec it again, with the next provided from this result as
  const saves = await this.modelInstallationSave.find(
      {
        G1PK: `installationUuid#${installationUuid}#placeUuid#${placeUuid}`,
      },
      {
        limit: pageSize,
        next: saves0.next,
        index: "GSI1",
      }
    );

And for the second request i am getting error Pass options.removeUndefinedValues=true to remove undefined values from map/array/set.
Onetable version: 2.6.2
Node: v20.11.1

I don't think value templates in the PK work like you think they work.
In your find request, you should be providing the ingredients (installationUUid, placeUUid) and not the PK itself.

Can you provide a debug.ts so we can replicate?

Closing for now. Please feel free to reopen if you can supply a reproduction.

@mobsense I had the same issue. After digging a lot I have found that the sort property is mandatory with the last change from https://github.com/aws/aws-sdk-js-v3/issues/2158
The proposed solution by AWS is not working in this repo:
const dynamoClient = DynamoDBDocumentClient.from(new DynamoDBClient({
    apiVersion: "2012-08-10",
    region: process.env.AWS_REGION
}), {
    marshallOptions: {
        removeUndefinedValues: true
    }
});

because the  https://github.com/sensedeep/dynamodb-onetable/blob/main/src/Table.js#L1070 and https://github.com/sensedeep/dynamodb-onetable/blob/main/src/Table.js#L1070 are getting the value from an incorrect place.

Is this the solution you propose:
                    let {hash, sort} = this.index
                    let start = {[hash]: cursor[hash]}
                    if (sort && cursor[sort]) {
                        start[sort] = cursor[sort]
                    }

That could be a solution to not add undefined: undefined but anyway lines 1070 and 1096 are wrong and not doing anything.


Out of date documentation?

Can you guys update this documentation? There are a lot of features across 365 being changed without appropriate up to date documentation.  These roles seems to have been changed on Oct. 14th, but the doc is from Sept. 22nd.
https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/permissions-in-the-security-and-compliance-center?view=o365-worldwide

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

ID: 5b34b5c8-b67e-72f2-0eba-d98b760f1d16
Version Independent ID: adcd41fb-ffd1-f6d0-96ad-0036c0a677a7
Content: Permissions - Security & Compliance Center - Office 365
Content Source: microsoft-365/security/office-365-security/permissions-in-the-security-and-compliance-center.md
Service: o365-seccomp
GitHub Login: @chrisda
Microsoft Alias: chrisda

@liamdou, are there specific changes you'd like to see?

@liamdou We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if you see an improvement is required in the specific area of this documentation. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


New features/settings, bit of bug fixes

Better and detailed descriptions in the commit messages. But I've fixed several bugs reported from users, as well as improved the overall functionality of the bot, and drastically stopped it from retweeting other bots that are retweeting fake contests or tweets in tweets of tweets (yea...).
Before this bot could tweet several thousand useless tweets that were often caused by many of these bots being confused by each other and tweeting around quoted tweets of other users. Almost every single one of these were completely invalid contests and not even real, just bad bot behavior. This has configurable checks now to make this bot more sophisticated with what it is tweeting, and lower down on it's chances of hitting the rate limits. It is now more likely to hit search rate API limit because it's having to search for new content because 99% of search results is invalid bot tweets and wants to search again quickly, so there is now 30 second sleep period between search queries.
With any luck, people using this bot will use these updates and trim down the amount of bad tweets out there so we can get better results as more bots stop retweeting garbage en-masse.

hi, i've done tests with your version, seems pretty good but i have an issue, when searching the word "retweet" no problem but it seems to be totally ignoring the "rt" keyword, any idea ?

Hey there. Perhaps it's too short? That was the most annoying part to work with was the Twitter search queries. They can't be very long, and it's really difficult to run tests on them accurately. I was trying to do really large ones with multiple OR statements but it seems you can't really do that... That's why I have an array of search queries now that it just searches through.
Perhaps do not just do "rt" but like "rt to win", "rt 2 win", etc.

Hi @henhouse , thanks for the dedicated work! I'm ashamed I haven't had time to improve on this Twitter bot, but it was a fun quick-do thing for me and I didn't think back then it would reach so many people. Glad someone finally had the time to also write some code. Hopefully I'll have a little more time in the near future to also put down some more code here.
Just a small thought: maybe keep the braces starting after the function definition instead of under it (Allman c++ style). And again, many thanks!

@raulrene,
No worries, I had a bit of fun making improvements and making it more efficient. Some of the code isn't the best... but I don't often program in JavaScript and Node so it was a bit of practice for me to play around in. It seems like many people are probably using this bot, so I really wanted to make the improvements to not retweet other bots, block them, etc. because there's a incredibly high amount of useless bots retweeting each other... hah.
Isn't Allman style the way I did it? I always prefer brackets under function declarations out of habit... so I changed them all for my own personal readability. :grimacing:


archive slack history to new apache list

Our slack history is currently not archived on Apache servers. This issue is to figure out the best way to do that.
Exporting the history from Slack yields folders for each channel and files for each day of communication for that channel. At the very least we can serialize the export and send an email per day per channel to a specific Apache mailing list.
subject: [channel name] [day]
where the content is:
[timestamp] [user id|name] message

Thanks for this initiative!
I think the main goal is for those messages to be found at https://lists.apache.org/ but maybe some channels deserve to be directly exposed to the OpenWhisk dev and users lists? And probably create a dedicated slack-archive for the other channels.
If that's possible it would be nice to include a link that points to the position of the first message in the Slack channel. That might cause a forking of some discussions between Slack and lists but that's inevitable.

If that's possible it would be nice to include a link that points to the position of the first message in the Slack channel.

Setting aside the question of whether I can construct the link from the information available - since the openwhisk slack is not a paid slack, the messages that are older than the most recent 10K will not be available publicly and so the link will not work as expected.
I could include the link anyway for posterity if it's feasible.

I could include the link anyway for posterity if it's feasible.

If that's easy I would include it and you can add a note about the 10k limit.

Thanks for the feedback @bdelacretaz.
Some further refinement based on input from @csantanapr and @dgrove-oss from Slack:

send email to dev list
a daily email digest for all the active channels that day

Some mining of previous discussion on the dev list
A daily Slack digests from Apache Pulsar:
<EMAIL_ADDRESS>Using python Slacker package here is the API
https://github.com/merlimat/slack-email-digest/blob/master/slack_email_digest.py#L55

The primary api is documented at https://api.slack.com/methods/channels.history

There is an official npm documented at https://slackapi.github.io/node-slack-sdk/web_api

I adapted the slack to email digest noted above and ran the first digest moments ago. Here's the first post to the dev list<EMAIL_ADDRESS>I'm currently running the job out of my github repo but will move it to an apache repo once we figure out where it should sit.

@bdelacretaz no dice on the link - not enough info to construct it. I could put a general link to the slack channel but not individual messages. I'll read more of the API for something better.

Heh the email subject looks like it's from the future (ran in a different time zone)... 😅
Will tweak the app.

I tweaked the digest to ignore channel join/leave events - this cuts down noise from channels that may only have such events on a given day.
If the volume of messages becomes high, we can look to consolidate the digests across channels. For now I'm leaving it separate since we primarily use a 1-3 channels.

I could put a general link to the slack channel but not individual messages

I think that's good enough, people can search for the messages if needed
Apart from that I think saying [slack-digest] in square brackets in the subject lines would make filtering easier. But the digests look good already, thank you!

I will adjust the subject line as suggested.
More reading of the Slack API - there is a way to retrieve a permanent link for each message documented here https://api.slack.com/methods/chat.getPermalink

The code lives here and is running nightly using travis ci
https://github.com/rabbah/slack-email-digest
Considering this task completed for now.

Thanks @rabbah !! Later we can probably add this code to devtools repo and execute only if its triggered by cron

👍 i wanted to get the upstream repo to add a (apache :) license first before committing to our code base.


fix(react-table): Table.Pagination component doesn't update with Table.Body

Closes #543
📝 Description
Updating <Table /> component can be a usual action, as mentioned in #543. However, <Table.Pagination> does not update synchronically with <Table.Body />, which results in two bugs:

<Table.Pagination /> length doesn't change. So when rows number is larger after the update, some pages can not be selected via <Table.Pagination />.
When rows number is smaller comparing to the previous table, the original page of <Table.Pagination /> is automatically selected and a blank table is showed.3.

This is because:

The table context collection never updates when rows data change.
<Pagination /> is not properly controlled as it does not receive the page prop.

⛳ Current behavior (updates)
#543 described it thoroughly. I've added a new story here so it would be clearer to test.

🚀 New behavior

💣 Is this a breaking change (Yes/No): No

📝 Additional Information

As agreed with @imchell, I will add some test cases to his PR.

Codecov Report

Merging #549 (3421c4f) into main (d3c7f53) will increase coverage by 1.25%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #549      +/-   ##
==========================================
+ Coverage   74.75%   76.00%   +1.25%
==========================================
  Files         200      200
  Lines        3090     3101      +11
  Branches      952      956       +4
==========================================
+ Hits         2310     2357      +47
+ Misses        765      729      -36
  Partials       15       15

Impacted Files
Coverage Δ

packages/react/src/table/table-pagination.tsx
85.71% <ø> (+71.42%)
:arrow_up:

packages/react/src/table/table-context.tsx
84.00% <100.00%> (+2.18%)
:arrow_up:

packages/react/src/card/card.tsx
100.00% <0.00%> (ø)

packages/react/src/button/button.tsx
94.00% <0.00%> (ø)

packages/react/src/popover/popover-trigger.tsx
100.00% <0.00%> (ø)

packages/react/src/dropdown/dropdown-trigger.tsx
100.00% <0.00%> (ø)

packages/react/src/utils/collections.ts
83.07% <0.00%> (+1.53%)
:arrow_up:

packages/react/src/use-pagination/index.ts
100.00% <0.00%> (+2.43%)
:arrow_up:

packages/react/src/pagination/pagination.tsx
68.42% <0.00%> (+2.63%)
:arrow_up:

packages/react/src/table/table.tsx
93.54% <0.00%> (+3.22%)
:arrow_up:

... and 7 more

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 d3c7f53...3421c4f. Read the comment docs.

Fixed here https://github.com/nextui-org/nextui/pull/626


Secondary image Tokenizer

Is the image tokenizer for the secondary image already created, or should we create it in the  finetune file:
config["model"]["observation_tokenizers"]["top"] = ModuleSpec.create(
        ImageTokenizer,
        obs_stack_keys=["secondary"],
        task_stack_keys=["secondary"],
        encoder=ModuleSpec.create(SmallStem16),
    )

Not sure the specific model that you download, I think you need to create it by default. You can search for "secondary" in the config.json in the model folder. They are there if the model have them created.


Self-contained configuration and resources package

Summary of the new feature / enhancement
It may be useful to have a zip package format that defines how to have a self-contained configuration and resources making it easier to deploy configuration without installing resources onto each node.
Proposed technical implementation details (optional)
The zip would contain its own manifest defining the root configuration file (as it may include other configs).  Resources would be, by default, constrained to those found in the zip and also ones included with DSC (within the DSC home folder).  Optionally, DSC_RESOURCE_PATH can be defined within the manifest.  Also have a way to catalog sign the package that is cross-platform compatible which would include hashes of the configs and resources.

+1

Isn't this want  Machine Configuration Packages are already doing - would be great if it was aligned with that.

The existing machine configuration implementation is built around processing the MOF files representing PSDSC configurations - if DSCv3 supports resolving a configuration and its resources into an archive, machine configuration would be able to leverage that artifact instead of redesigning their implementation to operate on v3 configuration documents.
This functionality is also very useful for test scenarios.

My initial thoughts:

We name the package with the extension .dscpkg (pronounced "DSC package") and use the zip format.
The .dscpkg is passed to dsc.exe the same as a configuration file: dsc config get foo.dscpkg
The root of the dscpkg contains a single file with the extension of .dscpkg.yaml, .dscpkg.yml, or .dscpkg.json

If more than one file with any of these extensions is found in the root, an error is returned

The contents of the dscpkg manifest has:

$schema pointing to the schema and version of the package manifest
Optional metadata property which the author can put whatever they want and isn't used by DSC like: description, author, copyright, license, etc... (it probably makes sense to recommend some standard metadata properties if we expect these packages to be shared)
Required resourcePath which takes an array of strings to relative paths within the zip to search for resources

Any path that resolves outside of the zip is an error

Optional allowCoreResources (not sure if Core, Builtin, or something else describes this better) that is a boolean when true will include the dsc.exe home to search for resources (this is where the group, etc... resources reside).  Default is false if not specified.
Required configurationFile which is a resolved as a relative path within the zip to a YAML or JSON file that is used as the configuraiton

DSC_CONFIG_ROOT is wherever this file resides within the zip
Any path that resolves outside of the zip is an error

Optional removePackage enum accepts:

onSuccess when the operation is successful, the dscpkg is deleted
always the package is always deleted even if it failed
never the package is never deleted (this is default)

The zip is unpacked into user temp folder


Edit court state description, Click to open the file browser

I noticed a couple of imprecise descriptions on the court UI.
Additionally, I added a click handler to open the file browser for revealing the vote.

I am currently scanning for more description to change.


termsrv.dll 10.0.18362.267

Please update For Windows 10 Pro v1909 Terminal Service
termsrv.dll 10.0.18362.267
termsrv.zip

https://github.com/stascorp/rdpwrap/issues/1022#issuecomment-596437997

Worked !
Thanks  Bro.
You Saved My Life ;)

A Problem Found In This Version of termsrv.dll (10.0.18362.267).
"Disable Shadowing" Not Work Correctly.
I Just Want Single User Per Session Without Shadowing.

If there is a fix for the ini section, please let me know; I only maintain the ini from provided ini sections by others skilled in creating the sections....

Duplicate of https://github.com/stascorp/rdpwrap/issues/871


compile [exe|aot-snapshot] with --no-sound-null-safety does not work when the Dart VM is switched to sound null safety by default

The compile [exe|aot-snapshot] commands appear to rely on the automatic detection of null safety from the kernel file as a result when the Dart VM is switched to sound null safety by default these commands do not work when used with --no-sound-null-safety
dart compile exe --no-sound-null-safety hello.dart
would fail

This now works when we retain the ability to detect the null safety mode from the AOT snapshot or the kernel file.


Add a validate function prop

This will allow a user to pass a function that will be called to validate the text before it is added as a tag. Common use case can be a list of emails, that you want to validate an item is a valid email, but can be useful for many things.

Thanks, good idea! I've made a new release with your contribution.


Couchbase using ACI

Ben,
Please take a look at my submission and let me know what you think!
Thanks

Nice!  Merged!


CAMEL-8206 Updated chunk-templates version from 2.6 to 2.6.3 release

Hi all,
This PR is related to: https://issues.apache.org/jira/browse/CAMEL-8206
Thanks,
Bye.
Andrea

I close the PR since Claus has already merged it.


Extra nodes not appearing under cluster.

I have followed the guide step 3 and added the additional scaleset with new size Standard_D2_v3. Used the same  "nodeTypeRef"  as the primary cluster.
However i cant see the additional new nodes under the cluster?
When i add the new scale set to the primary node should i see 10 nodes under the cluster?

@inkey Thank you for your feedback.  Could you provide the URL of the documentation that you are following?
Thanks.
James

@inkey Since this issue is a duplicate of https://github.com/MicrosoftDocs/azure-docs/issues/18694
We will close this issue and will work with you on https://github.com/MicrosoftDocs/azure-docs/issues/18694
Thanks.


docs: fix mock return value example

Summary
The mock return value example result was wrong, so just to fix. It was showing undefined on console instead the wished value.
Test plan

Codecov Report

Merging #11047 (c29ff18) into master (baf9f99) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11047   +/-   ##
=======================================
  Coverage   64.22%   64.22%
=======================================
  Files         305      305
  Lines       13254    13254
  Branches     3234     3234
=======================================
  Hits         8512     8512
  Misses       4050     4050
  Partials      692      692

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 baf9f99...c29ff18. Read the comment docs.


Composer constraints do not reflect conflict with Symfony < 5

Monolog version 2
I just composer uped a project that's running on Symfony 3.4 LTS and requires "symfony/monolog-bundle: "^3.0" which today resulted in an upgrade of Monolog from 1.25.1 to 2.0.1. Composer went through fine, but in the post-update-cmd Monolog complained:
In MonologExtension.php line 55:

  Symfony 5 is required for Monolog 2 support. Please downgrade Monolog to version 1.

Why isn't Monolog 2 declaring a conflict with any Symfony version lower than 5 in the composer.json?

see symfony/monolog-bundle#330

Yes, but I still don't understand why Monolog fails at runtime and doesn't declare this important conflict from the get-go. Is some sort of performance the reason for not declaring the conflict in Monolog itself?

it is not monolog which is failing. It is MonologBundle.

Fair enough, I misinterpreted the error message.


Respond to size constraints

width: 100% height: 100% is nearly impossible to get working, especially with flexbox in the mix. Can we find a way to be more responsive with sizing?

@contra @veggiemonk so this lib indeed passes through the user defined class and doesn't ship with any hardcoded styles to it (.react-codemirror2 is applied to the component but is empty).
I played with this a bit and the following seemed to work for me. Can you try out and let me know if this works? I would absolutely love an isolated use case that clearly demonstrates this shortcoming. Please share one if you can? I'm trying to figure out what can be done on my end that applying styles in implementation can't achieve.
.react-codemirror2 {
  flex: 1 1 auto;
  margin-top: 0;
  height: 100%;
  position: relative;
}

.CodeMirror {
  position:absolute;
  top: 0;
  bottom: 0;
  left: 0;
  right: 0;
  height: 100%;
}

Hi  @scniro,
Thanks for getting in touch.
I just quickly tried it out and it looks good.
So far, it seems to be good enough for my simple use case but I'll try to customize it further and give feedback here. To give it a specific doesn't seem trivial. I'll let you know.
Thank you. 👍

Going to close this out for now as I have't had any further breakthroughs on this and the above styling seems to work. Please reopen if you have any other difficulty with this!

@scniro Thanks, sorry for no response I haven't had time to confirm that fixes as we had switched editors already.

meet same questions here,
reason is that
<.codemirror2> can not set 'style' flag. code like this is useless:
import {UnControlled as CodeMirror} from 'react-codemirror2';
<CodeMirror>
style=...
...
</CodeMirror>

So, when try to set real codemirror height & width to 100%, it will useless because of it's parent node 'react-codemirror2' have not a certain height & width.

Hope this could support style flags. thanks.

Just in case anyone runs across this. I had to add !important to the height attribute.
.CodeMirror {
  position:absolute;
  top: 0;
  bottom: 0;
  left: 0;
  right: 0;
  height: 100% !important;
}


Add emoji for some features in README.md

Can I contribute?

Can I contribute?

@ypoleto
Yes, of course) You can choose suitable emojis (at your discretion) and make a PR.


What about the ingestion endpoint?

When the SDK is being connected using a connection string (not only the key), do we need to open the firewall for that also?

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

ID: 3942b937-b212-3ceb-d356-450b7f598f68
Version Independent ID: 8b015b42-cf02-3942-3cc3-6e0f977d191a
Content: IP addresses used by Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/app/ip-addresses.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @AaronMaxwell
Microsoft Alias: aaronmax

Thanks for the question. We are actively investigating and will get back to you soon.

@Leonardo-Ferreira - Yes, we need to open the firewall.
At this moment, Since there is no doc update required, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Resume experiments

Why?
Sometimes the training process dies, and you want to resume from a checkpoint, keeping your partially trained model weights and metric history.
How?
Editing an existing experiment might be problematic (see #177). Perhaps we could create a new experiment with all the data from the previous experiment but with a new ID somehow.

Commenting to say that I love the library so far. Being able to resume experiments would be really really helpful to me, so if there's anything I can do to improve the release time of this feature, I'd be interested in helping.


Use it only for backend?

I got a question for people using this project: would it make sense to only use this for SSR? I got a nice setup already working on the client, so I was wondering if it would make sense to only use the server rendering capabilities of this library. Is it just not worth it and it's better to adapt my client code to also use isomorphic-relay, or it's doable and won't introduce performance pains and/or errors?
Thanks!

This library should be used on the both the server and the client to make it work.


fix: DEV-3919: Fix overflow to show audioform settings and volume popups

This fix is not the best way to fix this, closing this PR to fix directly in label-studio


Isolate OpenShift maintainer commits from main branch

Include OpenShift maintainer commits in their own OCP branch.
Ideally, this will be rebased on top of the main branch periodically when we do releases.

/verify-owners

@rhmdnd Could you also add @BhargaviGudi into the approvers list? Thanks.

Done - thanks!


Add support for VCPKG on Windows

[X] I agree to follow the project's code of conduct.
[X] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

Set GDAL_VCPKG environment variable to 1 to enable VCPKG support.
Set GDAL_VCPKG_TRIPLET to the desired triplet (e.g. x64-windows-static).
VCPKG_ROOT must point to the VCPKG root directory.
Install GDAL with vcpkg install gdal:x64-windows-static (or the desired triplet).
Install pkgconf with vcpkg install pkgconf:x64-windows-static.
Set PKG_CONFIG to the pkgconf executable (e.g. %VCPKG_ROOT%\installed\x64-windows-static\tools\pkgconf\pkgconf.exe).
Set PKG_CONFIG_PATH to %VCPKG_ROOT%\installed\x64-windows-static\lib\pkgconfig.
When building non-static version, copy missing dlls from %VCPKG_ROOT%\installed\x64-windows\bin to the executable directory.

@aljen Thanks for the PR! I'm not a windows (nor vcpkg) guy, so not sure how to review this. I'll reach out to the community in discord and see if anyone volunteers.

Ping @aljen can you take another look at this?

Yeah, I planned to do this over the weekend, I had my plate full lately :)


[BUG] Change Affinity for VM form missing

Change affinity for a VM missing, old UI form looks like this: (notice multi-select)

With @davidjumani

We've a PR


FATAL error caused by SDK 1.38.0 with jvm crash

Previous issue links: https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/2572
We recently switched to Speech SDK 1.38.0, it still encountered Fatal errors.
Version of the Cognitive Services Speech SDK
SpeechSDK-Linux-1.38.0
Platform, Operating System, and Programming Language

OS: CentOS Linux release 7.8.2003
Hardware: x64, x86, ARM
Programming language: java
0penSSL: 1.1.1u

The error message is as follows:
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fa83e3b5eb8, pid=2850, tid=140359522543360
#
# JRE version: Java(TM) SE Runtime Environment (8.0_40-b26) (build 1.8.0_40-b26)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.40-b25 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libcrypto.so.10+0x144eb8]  ASN1_item_verify+0x38
#
# Core dump written. Default location: /data/service/offlinetask/cti-outbound/core or core.2850
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

Current thread is native thread

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x0000000000000004

Registers:
RAX=0x0000000000000000, RBX=0x00007fa7ff7b5750, RCX=0x00007fa84c096820, RDX=0x0000000000000000
RSP=0x00007fa7ff7b5420, RBP=0x00007fa84805d030, RSI=0x0000000000000000, RDI=0x00007fa83e6b61e0
R8 =0x00007fa84805d030, R9 =0x0000000000000000, R10=0x0000000000000014, R11=0x00007fa95cc01590
R12=0x00007fa84805d030, R13=0x00007fa848063ed0, R14=0x00007fa7ff7b5750, R15=0x00007fa8480d0940
RIP=0x00007fa83e3b5eb8, EFLAGS=0x0000000000010206, CSGSFS=0x0000000000000033, ERR=0x0000000000000004
  TRAPNO=0x000000000000000e

CentOS Linux release 7

As stated previously, CentOS 7 is unsupported since its EOL on June 30, 2024 and the Speech SDK 1.40.0 release:
https://www.redhat.com/topics/linux/centos-linux-eol
https://learn.microsoft.com/azure/ai-services/speech-service/releasenotes?tabs=speech-sdk#speech-sdk-140-2024-august-release
Sorry, but we cannot support old SDK releases on CentOS 7 either.
Current supported Linux environments:
https://learn.microsoft.com/azure/ai-services/speech-service/quickstarts/setup-platform?tabs=linux&pivots=programming-language-java#platform-requirements


REFACTOR-#3176: Use ray from conda instead of pip

Signed-off-by: Vasilij Litvinov<EMAIL_ADDRESS>
What do these changes do?

[x] commit message follows format outlined here
[x] passes flake8 modin
[x] passes black --check modin
[x] signed commit with git commit -s
[x] Resolves #3176
[x] tests added and passing
[x] module layout described at docs/developer/architecture.rst is up-to-date

We're installing modin by conda anyway. conda itself recommends to not mix it and pip :)
That said, I don't think users would install modin from conda and ray from pip - most likely they would install both from the same source.


Add terms and conditions

Is your proposal related to a problem?

(Write your answer here.)
Describe the solution you'd like

(Describe your proposed solution here.)
Describe alternatives you've considered

(Write your answer here.)
Additional context

(Write your answer here.)
Requirement/Document

(Share it here.)

please assign this task to me , i have done with making 3 websites for client ,so i am best for it


[bug] command variable interpolation issues

Describe the bug
I can break this out into separate issues if needed. Related to #729 if we could have the final command logged, after interpolation is applied, I could provide more context.
We have a project that is being deployed via a moon run infra-core:deploy command. There appear to be a few issues:

The $project variable is being written "incorrectly"
The $timestamp variable isn't being replaced

We're using @moonrepo/cli v0.26.4
Steps to reproduce
The package.json file for the project is:
{
  "name": "infra-core",
  "version": "0.1.0",
  "description": "Core Infrastructure Dependencies",
  "license": "UNLICENSED",
  "author": "Rally"
}

And the task definition is:
  deploy:
    command: 'cdk'
    args: 'deploy --all --require-approval=never --app "FORCE_COLOR=1 pnpm exec deploy --target=$projectRoot" --output $workspaceRoot/.cdk/$project/$timestamp'

Expected behavior

$project should be infra-core, as that matches package.json and the project name required to run the command
$timestamp should be replaced

I had thought that $timestamp landed in v0.26.4, but could be mistaken.
Screenshots
We can see from the following screenshot that the $project variable was replaced with "core" and the $timestamp variable wasn't replaced. I recall you all mentioning that the project name defaulted to the directory name, but given the inconsistency between the project name when calling the command, and the default name, that probably warrants some resolution.

Environment
MacOS Ventura M2
Additional context

@shellscape $project is the moon project name, not package.json name. This won't change.
Also $timestamp won't be released until the next v1 version.

Fair enough. But as a followup, projects are defined as:
projects:
  - 'apps/*'
  - 'infra/*'
  - 'packages/*'
  - 'services/*'
  - '.'

There's a big inconsistency between how we have to call a project by name to run a command, and what the subsystem thinks the project name is. e.g. infra-core required to call a command for a project, versus core which is what $project is being interpreted as. I think there's more to chat about here.

@shellscape Are you using this setting? https://moonrepo.dev/docs/config/toolchain#aliaspackagenames
That would make moon run infra-core:... available, but the project name is still core. infra-core is simply the alias.
With that said, I'll add a $projectAlias token. I honestly thought that already existed :P

🙌  that's awesome, thank you.
yes, we have aliasPackageNames: 'name-and-scope' set from the default setup. this makes total sense now.