UpdateServicesComputerTargetGroup: New resource - managing computer target groups

Pull Request (PR) description
A rebased pull for #60
It looks OK to me, waiting to see if it passes the Pester tests as these may need updating to support 5
This Pull Request (PR) fixes the following issues

Fixes #44

Task list

[x] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[x] Resource documentation added/updated in README.md.
[x] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[x] Comment-based help added/updated.
[x] Localization strings added/updated in all localization files as appropriate.
[x] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Hey, @johlju. Trying to rebase per our discussion in #60. However the tests are failing for resources that I'm not touching, in a way that I haven't seen before - all saying ' Cannot find the Windows PowerShell data file 'MSFT_UpdateServicesApprovalRule.strings.psd1' in directory xxx' but the files they reference seem to appear in the module - feels like this is unrelated to my pull request. Can you advise?

Will have a look as soon as I have time.

@johlju Quick reminder when you have a few minutes to check out the issue with the tests here :)

@Borgquite if you wouldn't mind reviewing PR #79 so I can merge it, then this PR should be able to run the tests again after it has been rebased. 🙁

I merged PR #79 so this one can be rebased.

I merged PR #79 so this one can be rebased.

Thanks - I'll see if I can get the tests to resolve myself now, will keep you posted!

Ping me when the tests passes on this one, I will try to get the time to review. 🙂

Ping me when the tests passes on this one, I will try to get the time to review. 🙂

Thanks - doing some fairly major reworking of the rest of UpdateServicesDsc (it's missing tonnes of useful parameters, breaks a lot of DSC 'rules' from my PoV, e.g. as others have noted, certain parameters take effect even when they are 'unspecified') and it generally just needs some love. I'll keep you posted.


Unexpected duplicate small transactions

The netcode should deduplicate small transactions before feeding them off to chain::controller. However it seems pretty clear that it isn't doing this 100% correctly as a lot of duplicate transactions show up on as error prints.
This issue only covers small transactions. I suspect large transactions are suffering other problems related to this as well but they are tricker to fix I think.

Fixed and tested via internet test net


hasRole() behaviour

I'm not sure if this is expected behavior, but hasRole(null) returns true.  Maybe it should throw InvalidArgumentException for anything other than int, so if someone (like me:) accidentally pass null there it wont let unauthorized user in?

I think returning false will be sufficient.  I don't see anything else right now. I let you know if I find something.


Add support for privileged intents

This PR adds support for intents, enables "Server Members" Privileged Intent, and drops requirement of "Presence" Privileged Intent. This is needed to keep role-based actions (which is a lot for a moderation bot) running.

You will need to update to discord.py 1.5.0 or higher (pip3 install -U discord.py)
You will need to enable the "Server Members" privileged intent: https://discordpy.readthedocs.io/en/latest/intents.html?highlight=intents#privileged-intents

This is a little urgent as discord will be changing default intents on October 7, 2020. ID verification is not needed as the bot will only be in one server, not 100+. Sorry for being so late about this, but discord.py only added support this Tuesday with 1.5.0.

Waiting for @NicholeMattera to pull


az afd endpoint create Fail "Default value is TenantReuse ,, Acceptable values are: UNSECURE, TENANTREUSE, SUBSCRIPTIONREUSE, RESOURCEGROUPREUSE, NOREUSE"

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

az afd endpoint create  --resource-group myRGFD  --endpoint-name mvp-casi-aa  --profile-name activeactiveafd  --enabled-state Enabled  --name-reuse-scope TenantReuse
Describe the bug

Fails with below error
Default value is TenantReuse ,, Acceptable values are: UNSECURE, TENANTREUSE, SUBSCRIPTIONREUSE, RESOURCEGROUPREUSE, NOREUSE
This error occurs in all cases if you supply the --name-reuse-scope  value, or if you don't. The default is not taken. Powershell works, but the CLI does not.
To Reproduce

az group create --name myRGFD --location eastus
az afd profile create  --profile-name activeactiveafd  --resource-group myRGFD  --sku Standard_AzureFrontDoor
az afd endpoint create  --resource-group myRGFD  --endpoint-name mvp-casi-aa  --profile-name activeactiveafd  --enabled-state Enabled  --name-reuse-scope TenantReuse
Fails with below error
Default value is TenantReuse ,, Acceptable values are: UNSECURE, TENANTREUSE, SUBSCRIPTIONREUSE, RESOURCEGROUPREUSE, NOREUSE
Expected behavior

Expect endpoint to be created.
Environment summary

Cloudshell Bash
az version
{
"azure-cli": "2.45.0",
"azure-cli-core": "2.45.0",
"azure-cli-telemetry": "1.0.8",
"extensions": {
"ai-examples": "0.2.5",
"aks-preview": "0.5.122",
"connectedk8s": "1.3.5",
"front-door": "1.0.17",
"k8s-configuration": "1.6.0",
"k8s-extension": "1.2.6",
"ml": "2.13.0",
"ssh": "1.1.3"
}
}
Additional context

route to CXP team

Duplicate with https://github.com/Azure/azure-cli/issues/25553, service team is rolling out a hotfix for that.

Fix rolled out, closed the issue


Support of latest PostgreSQL versions

Dear PgWeb Developers,
thank you for an amazing product. It really helps a lot.
Do you have any plans to support the latest PostgreSQL version?
I'm referring the content of the next file -> https://github.com/sosedoff/pgweb/blob/master/pkg/statements/sql.go
Thank you!

Pgweb supports the latest version 16 of Postgresql

Thank you!


[BuildSystem] Don't overcommit CPUs in execution queue.

I would like to do a rigorous study of this eventually, but for now the
following logic suggests we should default to numLanes == numCPUs:

We should always be willing to max out the CPU count if we have enough
work. As currently implemented, this means we must have numLanes >= numCPUs
(since we always block a lane once a subprocess is executing).

There will always be cache contention from having an overly loaded CPU ready
set. If we overcommit the CPUs, we are forcing the OS to deal with this load
in an unblocked build. The benefit we get from that is that the overcommitted
CPU can mean we recapture latency when one lane has no work.

However, we also have to worry about the Core engine which is executing
outside of the lanes. It is critical that it isn't starved, in order to
ensure the execution queue is as deep as possible. By overcommitting, we are
starving the ready queue potentially increasing task latency (the only thing
we were potentially gaining).

rdar://problem/32114117 Don't overcommit CPUs in llbuild execution lanes

@swift-ci please smoke test

@swift-ci please test macOS

@swift-ci pleased test

@swift-ci pleased test

@swift-ci please test


Update billing info for ampproject GitHub org to point to OpenJSF

Although ampproject is on the GitHub Free plan, there are billing settings that still point to Google.

https://github.com/organizations/ampproject/settings/billing lists Google Admin as the Billing Manager
https://github.com/organizations/ampproject/settings/profile lists a google.com Billing email address

We should update these, though I'm not sure what to set these to for OpenJSF. @brianwarner, @tobie or @jorydotcom do you know what this should be?

Hi @mrjoro, yep, this is pretty straightforward. Can you please make me an owner and temporarily set those to me? I'll get them set properly.

Done!
A related question--we are shifting to using GitHub Actions for testing, and there will be a cost of about $40k/year for this.  Before the move to OpenJSF we'd talked about how we would handle things like this in the abstract, but now that it's actually happened I'm not sure what the process is to get approval for this expense and to make sure it's properly funded.  Can you provide guidance on this?
/cc @rsimha and @ampproject/wg-infra as FYI

Nice

@brianwarner friendly ping on whether we've resolved how to handle expenses like this (the ~$40k for GitHub Actions).  With the billing updated to point to OpenJSF charges like GitHub Actions would presumably be handled by OpenJSF, with Google able to direct funding for this if needed.

@mrjoro thanks for the reminder. This past week and the coming week are a trainwreck, can we maybe connect over Slack and find a time to talk it through?

Sorry, this one has slipped through the cracks... :)
I did see that I was able to set a "Billing Manager" for ampproject, and I've sent an invite to @brianwarner for this role.  I think that should give you enough rights to update whatever billing info should be updated?  If not, let me know!


C++ syntax highlighting grammar injection doesn't work

Does this issue occur when all extensions are disabled?: Yes

I'm trying to add custom keywords to the cpp syntax. The same keywords work for .c files but they are not highlighted in .cpp files.
The same question was asked also here but there is no answer there.
// package.json
    "grammars": [
      {
        "scopeName": "qt.injection",
        "path": "./res/lang/cpp/qt_cpp.injection.json",
        "injectTo": [
          "source.c",
          "source.cpp"
        ]
      }
    ],

// qt_cpp.injection.json
{
  "scopeName": "qt.injection",
  "injectionSelector": [
    "L:source.c -string -comment",
    "L:source.cpp -string -comment"
  ],
  "patterns": [{ "include": "#signal-keyword" }],
  "repository": {
    "signal-keyword": {
      "name": "keyword.control.signal",
      "match": "\\bSIGNAL\\b"
    }
  }
}

I'm not sure whether this is a bug or not. Is there anything I should do to make it work?
Version: 1.88.1
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:34:12.840Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Linux x64 6.5.0-28-generic

wrong scopeName
source.cpp.embedded.macro
the cpp extension seems to assign two different grammars to the cpp language
I assume VSCode uses the first grammar
https://github.com/microsoft/vscode/blob/535703cb11b9248dfcdf9066e0cd96522a42d1b8/extensions/cpp/package.json#L76-L85

wrong scopeName? source.cpp.embedded.macro
the cpp extension seems to assign two different grammars to the cpp language I assume VSCode uses the first grammar
https://github.com/microsoft/vscode/blob/535703cb11b9248dfcdf9066e0cd96522a42d1b8/extensions/cpp/package.json#L76-L85
otherwise you're fighting the cpp grammar it might be consuming whitespace before your keyword so you'll have to do the same

I didn't understand what you proposed. Do you propose changing scopeName from qt.injection to something else or adding source.cpp.embedded.macro to injectTo?

I had proposed adding source.cpp.embedded.macro to injectTo
but that won't work as it's not actually applied
"function_call" in the cpp.embedded.macro grammar does consume the whitespace before function names (and the following ( )

https://github.com/microsoft/vscode/blob/2d6df400a7ee2c3bc458ff23b18b9df4d6500ad6/extensions/cpp/syntaxes/cpp.embedded.macro.tmLanguage.json#L2984
so you will need to do the same \\s*\\bpar_for\\b

@RedCMD It worked. Thank you.

@RedCMD It worked. Thank you.


Implement support for external interrupts

Please consider following stmhal's API for this (ExtInt class).  Even better would be to somehow make stmhal/extint.c reusable for this port by abstracting the external interrupt hardware implementation.  This also goes for the other classes (UART, SPI, I2C, etc).  Some may be difficult to do, so let's see how it goes.

Ok, I will follow the path you suggest, lets see where it takes me...
On Tue, Jan 27, 2015 at 4:43 PM, Damien George<EMAIL_ADDRESS>wrote:

Please consider following stmhal's API for this (ExtInt class). Even
better would be to somehow make stmhal/extint.c reusable for this port by
abstracting the external interrupt hardware implementation. This also goes
for the other classes (UART, SPI, I2C, etc). Some may be difficult to do,
so let's see how it goes.
—
Reply to this email directly or view it on GitHub
https://github.com/danicampora/micropython/issues/12#issuecomment-71669114
.

@dpgeorge I know that you are super busy, but I just one to know if the stack usage that I have seen is normal...

You need about 216 bytes stack for a Python function call.  You can check using micropython.mem_info() function (it tells current stack usage).  But for an IRQ call it depends how much extra overhead you have setting up the callback.  Try printing the result of mp_stack_usage() in different places in the IRQ to see how much stack you are using (actually this won't work because mp_stack_usage measures for the main thread and you'll be on the IRQ stack... so you'll need to write your own version of mp_stack_usage for the IRQ; should be easy).

Thanks!. I already have something in place to check the high water mark of the main stack. But that info about the 216 bytes is what I was looking for.


Not publishing on main thread Relay

2023-06-10 13:51:51.783271-0700 NostrSDKDemo[29109:47174192] [SwiftUI] Publishing changes from background threads is not allowed; make sure to publish values from the main thread (via operators like receive(on:)) on model updates.

We can discuss this, but maybe we could make it flexible so that the client application can choose what thread/queue to receive updates on.

We can discuss this, but maybe we could make it flexible so that the client application can choose what thread/queue to receive updates on.

Yeah, I wasn't aware of receive(on: but that seems to work well 👍


This doesn't happen on apache, only on nginx.

Log has:
2016/07/06 12:42:32 [error] 42764#0: [ngx_pagespeed <IP_ADDRESS>-7962] http://shardi\
ng-css-images.example.com/mod_pagespeed_test/sharding-css-images/example.css:0:E\
rror status=670002 (Name or service not known) serf_connection_create2
2016/07/06 12:42:32 [warn] 42764#0: [ngx_pagespeed <IP_ADDRESS>-7962] Fetch failed t\
o start: http://sharding-css-images.example.com/mod_pagespeed_test/sharding-css-\
images/example.css

So it does look like we're trying to call out to the domain we're sharding to, which doesn't make any sense.  Weirdly, it will probably work, but it's not how it should work.

My guess is that this is a ProxyFetch bug.

Actually, I'm misreading the logs and set this up wrong.  There's nothing wrong with this behavior.  What's happening is that nginx is calling out to http://sharding-css-images.example.com because it doesn't know about my proxy.  Totally reasonable.


Address Kaxil's comments on PR #290

The commit addresses Kaxil's comments on PR #290
The changes are:

Unpin openlineage-airflow version
Upgrade apache-airflow to >= 2.3.0

However, upon local testing, I am observing an issue with OpenLineage
https://github.com/OpenLineage/OpenLineage/issues/736 which makes version 0.8.1 unstable
for us and hence will keep the PR in draft mode.
Edit: The above issue is resolved by delaying referencing of the hook's client.

Closing this PR as I have cherry picked the commits from here into https://github.com/astronomer/astronomer-providers/pull/335.


Updates?

the last update was over a year ago.
There are breaking issues that make this theme not usable on github.io.
Are there plans to update this repository to fix them?
If not, can you declare that this project is no longer being updated at the top of the readme?

... and link to alternatives.

I ended up just starting from the minimal-mistakes base (https://mmistakes.github.io/minimal-mistakes/) and slowly integrating pieces that I had completed in this repository into the new one.
You can see the results in my repository https://github.com/ian-bertolacci/ian-bertolacci.github.io .
You might be able to follow my changes starting at
f00c55 and going through to d25a8d
After that it started working.
Best of luck!

Thanks. That's precisely what I started doing now, too. for f in $( git diff 25c30de2b4ce3e3f23559384699bb4b9865d6473 --name-only ); do cp $f ../minimal-mistakes/$f ; done ;)

I ended up just starting from the minimal-mistakes base (https://mmistakes.github.io/minimal-mistakes/) and slowly integrating pieces that I had completed in this repository into the new one.
You can see the results in my repository https://github.com/ian-bertolacci/ian-bertolacci.github.io .
You might be able to follow my changes starting at
f00c55 and going through to d25a8d
After that it started working.
Best of luck!

Hey Ian --- your repo is private. Would be great to see your fixes :)

Done.

@ian-bertolacci
What breaking issues are there for github.io? I have just started my site (mdkar.github.io) and haven't encountered any so far. I don't want to get too far into populating it with content before realizing something doesn't work.

Fo rme, it was fine locally but when uploaded to github, the build would fail: #356

Strange, It worked out of the box for me (never tried it locally). But I'm having a problem with ordering pages in "portfolio". If I include a number in the file name but no date, then the posts sort numerically as intended, but when I add a date, the posts sort in chronological order. I want them reversed so the most recent is at the top.


Added REST proxy over existing RPCs

What?
Added REST proxy for the gRPC services.
Why?
These changes will allow UI developers to access results API over REST
Context https://github.com/tektoncd/results/issues/198
How?
gRPC gateway is used to generate the REST handlers and routing is done through google.api.http annotations in the service definition.

/ok-to-test

Rebased branch and resolved conflicts with PR #214

/retest

/assign @dibyom

hi @sayan-biswas - thanks for assigning. Might take me a few days to get to this :)

Unsure why Prow is not adding the approved label, since I am in the OWNERS file...

Hmm...this is odd

@adambkaplan https://github.com/tektoncd/community/pull/828 should fix this

/assign @adambkaplan

/approve

/kind feature


Remove version: taers232c.GAMADV-XTD3 version 6.71.09

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/taers232c/GAMADV-XTD3/releases/download/v6.71.09/gamadv-xtd3-6.71.09-windows-x86_64.msi
OK
(Automated message - build 910)


Performance Issues

With the implementation of assignment operators, the interrupt time has gone up 0.004 seconds for the test script. Even without any assignment operators present.

Attached the xdebug output for running the script.
xdebug.zip

Going to start testing on PHP7.3, I just realized my laptop is running PHP7.0. Updating it now..

Running PHP 7.3.0 TS the compile time is Compile time is: 0.0066261291503906 seconds, only 5% faster.

I think assignment operators are going to need to be removed, they can be replaced with math functions e.g add, multiply, etc.

OR I can rewrite this to parse 1mbcode into PHP code and then execute it?..


Fix regression with 'dynamic' or 'NSManaged' properties witnessing protocol requirements

The 'modify' coroutine should always call getter and setter methods, and not directly access storage. It should also be marked serialized so that it can be referenced from serialized protocol witness thunks.
Fixes https://bugs.swift.org/browse/SR-8657 / rdar://problem/43951732.

@swift-ci Please smoke test

@swift-ci Please test source compatibility

Oops, CoreStoreDemo still fails in the same way. Looks like there’s another bug here. Also I need to update a couple of SILGen tests. Updated version coming up, but I don’t expect it to change much.

It passes locally. I wonder if PR testing built the wrong revision?

.... ah, no, it's -enable-testing.

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please test source compatibility

@swift-ci Please smoke test

Ok, CoreStore is now passing!
17:06:56 Failures:
17:06:56   FAIL: Chatto, 4.0.3, 3e4b1a, ChattoApp, generic/platform=iOS
17:06:56   FAIL: Chatto, 4.0.3, 3e4b1a, ChattoAdditions, generic/platform=iOS

@DougGregor remaining failure is on you :)