Update ApplicationDataBackupRestore cli plugin version to 0.3.0

Authored-by: Shaan Sapra<EMAIL_ADDRESS>Thank you for contributing to the CF CLI Plugin Repository!
This repo contains both the plugin repo server and the metadata for CLI
community plugins.
Some of the requirements for PRs will apply to only one of these parts.
We're not allowed to accept any PRs without a signed CLA, no matter how small.
If your contribution falls under a company CLA but your membership is not public, expect delays while we confirm.
Submitting Plugins
If you haven't yet, please review our contributing guidelines:
https://github.com/cloudfoundry/cli-plugin-repo#submitting-plugins
In particular ensure the following requirements are being met:

[x] The plugin's name field in repo-index.yml matches the Name field in the plugin's plugin.PluginMetadata section
[x] The plugin's url field in repo-index.yml contains the same version from the version field

Submitting PRs to CLIPR (the CLI Plugin Repo server)
All new code requires tests to protect against regressions.
Description of the Change
There is a new flag argument to control how many backups are listed.
cf adbr --help now prints all the commands and their respective flags.
Why Is This PR Valuable?
Customers were limited to see only the 5 most recent backups. This change allows them to see more.
Applicable Issues
List any applicable Github Issues here
How Urgent Is The Change?
Is the change urgent? If so, explain why it is time-sensitive.
Other Relevant Parties
Who else is affected by the change?

LGTM


Missing or invalid type information in bicep

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce
cd deploy
az bicep build --file main.bicep

Any log messages given by the failure

container-http.bicep(32,23) : Warning BCP081: Resource type "Microsoft.Web/containerApps@2021-03-01" does not have types available.
environment.bicep(26,16) : Warning BCP036: The property "Flow_Type" expected a value of type "'Bluefield' | null" but the provided value is of type "'Redfield'".
environment.bicep(27,21) : Warning BCP036: The property "Request_Source" expected a value of type "'rest' | null" but the provided value is of type "'CustomDeployment'".
environment.bicep(35,5) : Warning BCP037: The property "type" is not allowed on objects of type "KubeEnvironmentProperties". Permissible properties include "aksResourceID", "arcConfiguration", "staticIp". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]
environment.bicep(44,5) : Warning BCP037: The property "containerAppsConfiguration" is not allowed on objects of type "KubeEnvironmentProperties". Permissible properties include "aksResourceID", "arcConfiguration", "staticIp". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]

Expected/desired behavior
-There is no documentation for "Microsoft.Web/containerApps".
-"Microsoft.Web/kubeEnvironments" does not mention "type" and "containerAppsConfiguration".
https://docs.microsoft.com/en-us/azure/templates/microsoft.web/kubeenvironments?tabs=bicep
Versions
Bicep CLI version 0.4.1008
Mention any other details that might be useful
https://github.com/Azure/bicep/issues/784#issuecomment-959799594
https://github.com/Azure/bicep/issues/784#issuecomment-959805535

I was wondering this earlier - I usually check the REST API specs, but that's not been updated yet https://github.com/Azure/azure-rest-api-specs/tree/main/specification/web/resource-manager/Microsoft.Web/stable

Correct - we're working on publishing the api specs and once those are available these warnings should go away

I got response from bicep team. We seem to have to wait a bit. But it works, so I have no problem.
https://github.com/Azure/bicep/issues/784#issuecomment-963529983

FIXED
https://github.com/Azure/bicep/releases/tag/v0.4.1272


OPCT-257: CI pipeline fix when uploading artifacts to release

Fix Github action pipeline when uploading artifacts to Github release.

/assign @rvanderp3

Ci tests are passing. Moving this PR forward to add the changes in v0.5 queue[1] for alpha.5 including[2].
[1] https://issues.redhat.com/browse/OPCT-257
[2] https://github.com/redhat-openshift-ecosystem/provider-certification-tool/pull/76


ParseError no longer use the error.cause property

Expected Behavior
Earlier the error thrown within the handler would be attached to the ParseError to the .cause property. This no longer is the case. This broke one of our prod services that were relying on this property.
I think it was unintentionally removed as part of dropping Node 16 support.
Here's the link to the change.
https://github.com/aws-powertools/powertools-lambda-typescript/commit/e4eee73770ffccead9212a566335ec256a31af7d#diff-27fac689aa83bd57991ab46c30f4cd72584c529baa433ce899e8b7bd6db7a7deL21
Current Behavior
ParseError.cause is undefined
Code snippet
Just throw any validation error in the handler and look for error.cause property.
Steps to Reproduce
You can run any tests in this file "packages/parser/tests/unit/envelope.test.ts" and check for error.cause property. It will be undefined.
Possible Solution
I've submitted a PR which reverts the ParseError change that removed this behaviour.
Powertools for AWS Lambda (TypeScript) version
latest
AWS Lambda function runtime
20.x
Packaging format used
npm
Execution logs
No response

Hi @tusharf5, thank you for opening this issue.
You are right in that the cause property was removed unintentionally; the change was made because since dropping Node.js 16 we can now safely assume that all errors have the cause property by default.
The idea was to use the "native" property instead of one defined by us, however it seems that I introduced a bug by not propagating the second argument we pass when we throw a ParseError to its parent class here. The error should've been like this:
class ParseError extends Error {
  public constructor(message: string, options?: { cause?: Error }) {
    const errorMessage = options?.cause
      ? `${message}. This error was caused by: ${options?.cause.message}.`
      : message;
-   super(errorMessage);
+   super(errorMessage, options);
    this.name = 'ParseError';
  }
}

Even though the API for this specific utility is still to be considered unstable during its beta period, we should have included this property in our tests.
--
Thank you for submitting the PR to fix it, I've left a couple comments. Once addressed it's good to be merged.

Hi @tusharf5, the release notes are not yet out but we made a release that includes the fix to this issue.
This should unblock your production workload.
Thanks again for the quick PR.


IllegalAccessError: tried to access method org.bson.internal.OverridableUuidRepresentationCodecRegistry

Whenever I run my application I get this error:
java.lang.IllegalAccessError: tried to access method org.bson.internal.OverridableUuidRepresentationCodecRegistry.(Lorg/bson/codecs/configuration/CodecProvider;Lorg/bson/UuidRepresentation;)V from class org.litote.kmongo.KMongo
at org.litote.kmongo.KMongo.createRegistry(KMongo.kt:87) ~[?:?]
at org.litote.kmongo.KMongo.createClient(KMongo.kt:78) ~[?:?]
at org.hyrical.influx.storage.Storage.load(Storage.kt:30) ~[?:?]
dependencies {
    implementation 'org.litote.kmongo:kmongo-serialization:4.6.1'
    implementation "org.jetbrains.kotlinx:kotlinx-serialization-json:1.3.3"
    implementation 'org.mongodb:bson:4.7.1'
}

and I run shadowJar
Here is my implementation (It errors when I call this)
    lateinit var client: MongoClientSettings

    lateinit var mongoClient: MongoClient
    lateinit var database: MongoDatabase

    fun load() {
        client = MongoClientSettings.builder()
            .applyConnectionString(ConnectionString("my mongoDb URL"))
            .uuidRepresentation(UuidRepresentation.STANDARD)
            .build()

        mongoClient = KMongo.createClient(client)

        database = mongoClient.getDatabase("Influx")
    }

Specifically on the line where I initialize mongoClient.

This is caused by the protocol in the ihcf event causing an abstract class to throw an java exception handler

First idea: try to use org.litote.kmongo:kmongo-serialization:4.7.0.
Because org.litote.kmongo:kmongo-serialization:4.6.1 is compiled with org.mongodb:bson:4.6.0 (and not 4.7.0)
HTH

implementation 'org.mongodb:bson:4.7.1'

Sorry for the late response.
Still seems to throw the exact same error.

Check if you have other version of mongo jar in your dependencies (from third party dependencies). Usually this is the origin of this stacktrace
HTH


增加PP-ShiTu的C++代码在windows环境下的编译步骤

增加PP-ShiTu的C++代码在windows环境下的编译步骤

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add System V message queue bindings for Linux (glibc/musl)

Yeah :cheer:, finally all green!
Code is ready for review.

@bors: r+
Thanks!

:pushpin: Commit 7590565 has been approved by alexcrichton

Thanks!

:hourglass: Testing commit 7590565 with merge 4548dc6...

:sunny: Test successful - status-appveyor, travis
Approved by: alexcrichton
Pushing 4548dc66daa9cafc87d7b069347e236a60fd13fa to master...


initial orientation of the map frame

Hi all!
I've been using Cartographer for several months and have successfully accomplished 2D SLAM and 2D pure localization function.
Now I'm trying to build a map and later set the initial_pose for pure_localization. But when I started, the orientation of the /map frame is not correct.
The correct orientation of the /map frame should be the same with the orientation of the /base_link frame (as shown below, the orientation deviation/error between /map frame and /base_link frame is around 60 degrees):

And the /tf between /map frame and /base_link frame is keep changing like this:
williamwoo@williamwoo:~$ rosrun tf tf_echo /map /base_link
At time<PHONE_NUMBER>.615
- Translation: [0.327, -0.494, -0.254]
- Rotation: in Quaternion [0.002, 0.007, -0.518, 0.856]
            in RPY (radian) [-0.004, 0.015, -1.088]
            in RPY (degree) [-0.222, 0.856, -62.336]
At time<PHONE_NUMBER>.615
- Translation: [0.327, -0.494, -0.254]
- Rotation: in Quaternion [0.002, 0.007, -0.518, 0.856]
            in RPY (radian) [-0.004, 0.015, -1.088]
            in RPY (degree) [-0.222, 0.856, -62.336]
At time<PHONE_NUMBER>.625
- Translation: [0.518, -0.821, -0.254]
- Rotation: in Quaternion [-0.000, 0.004, -0.518, 0.856]
            in RPY (radian) [-0.004, 0.007, -1.088]
            in RPY (degree) [-0.245, 0.399, -62.340]
At time<PHONE_NUMBER>.625
- Translation: [0.681, -1.168, -0.254]
- Rotation: in Quaternion [-0.001, 0.005, -0.516, 0.857]
            in RPY (radian) [-0.006, 0.008, -1.083]
            in RPY (degree) [-0.372, 0.467, -62.079]
At time<PHONE_NUMBER>.614
- Translation: [0.858, -1.494, -0.254]
- Rotation: in Quaternion [0.000, 0.003, -0.508, 0.861]
            in RPY (radian) [-0.003, 0.006, -1.067]
            in RPY (degree) [-0.152, 0.343, -61.110]
At time<PHONE_NUMBER>.624
- Translation: [1.048, -1.834, -0.254]
- Rotation: in Quaternion [-0.002, 0.001, -0.524, 0.852]
            in RPY (radian) [-0.004, -0.001, -1.102]
            in RPY (degree) [-0.249, -0.058, -63.150]
At time<PHONE_NUMBER>.619
- Translation: [1.215, -2.160, -0.254]
- Rotation: in Quaternion [0.000, 0.001, -0.514, 0.858]
            in RPY (radian) [-0.001, 0.002, -1.080]
            in RPY (degree) [-0.032, 0.142, -61.884]

The orientation of the /map frame is very critical for me because it's closely related to the initial_pose that I'm gonna set for the pure_localization part.
So I want to know what determines the initial orientation of the /map frame?
Any idea for solving this issue?
Thanks a lot !!
-----------------------------------Update----------------------------------
I've tried to record a few rosbags at different places and found that the orientation deviation/error between /map frame and /base_link frame is random......So I'm more confused about this issue :(

Maybe this helps: https://github.com/googlecartographer/cartographer/issues/1507#issuecomment-456813582

@MichaelGrupp
Thanks for replying !
I carefully checked googlecartographer/cartographer/issues/1507.
It's a bit relative because I also find that all the global submap poses that lie on the SLAM trajectory in my map do have the same orientation with the first submap pose, which aligns with the Grid. The Reference Frame of the Grid is the Fixed Frame (same direction with the /map frame), as shown below:

Each submap has its own coordinate frame origin that corresponds to the position of the first (accumulated) range scan data that was inserted into it.

By this, do you mean that the orientation of the /map frame is determined by the first accumulated range scan data (IMO, equals to the first submap?) ?
If so, is it correct to say that the orientation of the /map frame in the pure_localization part is different for every different trial (start position)?
Because my main issue is how to set the rotation parameter of the initial_pose that I'm gonna set for the pure_localization part, so I'm still not clear about this.
Any hint or advice is much appreciated.
Cheers!

-------------------------------------------------------Update-----------------------------------------------------------
I've dug into the /map frame and /base_link frame a bit more. I found that when I just started the normal SLAM process (or build the .pbstream process, the same), the /map(odom) is overlaid(same) with the /imu_link, and the same x direction with the /laser (as shown below).

But after around 0.8 second, the /base_link flipped 180 degrees and then correspondingly the /laser and /imu_link also flipped 180 degrees. And the /base_link changed direction from the /map(odom) (as shown below).

The whole flipping process is shown in the flipped.mp4 video
I originally thought it maybe related to the direction of my IMU, so I flipped and changed the direction of the IMU and re-collect the rosbag. But after this the Cartographer even fails to build the map. So I don't think it's the issue with my IMU. Then I'm more confused and got two questions:

The possible reason why the /base_link frame flip 180 degrees and changed the direction from the /map(odom) frame?
Which part of the Cartographer code specify the relation between /base_link and /odom? Is it possible that the Cartographer code asks the /base_link to flip 180 degrees with respect to the /odom(map) after receiving the IMU messages? I've browsed through the source code of Cartographer but didn't find the related code.

Any hint or advice for this?
Thanks!!
@MichaelGrupp @gaschler @neomanic

I think I've figured out this issue.
Finally I found the error is in the backpack_2d.urdf file. I modified the joint relation between base_link and imu_link, which means I wrongly added the rpy (roll, pitch, yaw) relation between them.
After the correction, base_link frame doesn't flip anymore and is the same with the imu_link frame. Both of them have the same direction with the map frame.
Thanks for all your help!


Add NSG to AzureBastionSubnet - Fixing #240

Overview/Summary
This PR adds an NSG to the AzureBastionSubnet
This PR fixes/adds/changes/removes

Fixes #240 by adding NSG to AzureBastionSubnet

Breaking Changes
None
Testing Evidence
Tested in my own environment and deployed successfully.
PR Tests will confirm also
As part of this Pull Request I have

[x] Read the Contribution Guide and ensured this PR is compliant with the guide
[x] Checked for duplicate Pull Requests
[x] Associated it with relevant GitHub Issues
[ ] (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Performed testing and provided evidence.
[ ] Updated one or more of the following tests (if required)

Unit
Linting
E2E (End-To-End)
ValidateAzCloud (Base validation in Azure Cloud)

[x] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
[ ] If relevant, created or updated Code Tours here

/azp run validateazcloud

/azp run e2e

Markdown link check failure is a false positive.


Multiple initiative rolls at the same time result in lost rolls

How to reproduce:
Make two initiative rolls in quick succession:

For logging purposes, "Today" is 6/17/2020
Recommendation is to build a patch for the initiative order, and then merge it with whatever the current order is at the end.

cant do much about it with how emojis work and the character limits on
messages.  results are tagged for each person too....
On Wed, Jun 17, 2020 at 9:27 PM Timothy Regan<EMAIL_ADDRESS>wrote:

How to reproduce:
Make two initiative rolls in quick succession:
[image: proof]
https://user-images.githubusercontent.com/5122881/84970731-46ce1180-b0e9-11ea-80dd-677791efedbe.PNG
For logging purposes, "Today" is 6/17/2020
Recommendation is to build a patch for the initiative order, and then
merge it with whatever the current order is at the end.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SkyJedi/FFGNDS-Discord-Dice-Roller/issues/27, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWUO6EXNV74QE2HMTWJAZ3RXF3QNANCNFSM4OBERX5A
.

I don't think that would matter, would it? The issue seems to be the time it takes to complete the roll. It gets the init order at the start, performs all the steps needed, and then replaces the init already stored with the one it builds. With two running at the same time there's a high chance that one will overwrite the other.

oh, no. that won't happen results are written before the messages are sent
On Wed, Jun 17, 2020 at 9:34 PM Timothy Regan<EMAIL_ADDRESS>wrote:

I don't think that would matter, would it? The issue seems to be the time
it takes to complete the roll. It gets the init order at the start,
performs all the steps needed, and then replaces the init already stored
with the one it builds. With two running at the same time there's a high
chance that one will overwrite the other.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SkyJedi/FFGNDS-Discord-Dice-Roller/issues/27#issuecomment-645732881,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWUO6EFCGVNDHYYG4ALB2TRXF4JTANCNFSM4OBERX5A
.

Doesn't the roll function send messages while it does its thing?

no
On Wed, Jun 17, 2020 at 9:37 PM Timothy Regan<EMAIL_ADDRESS>wrote:

Doesn't the roll function send messages while it does its thing?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SkyJedi/FFGNDS-Discord-Dice-Roller/issues/27#issuecomment-645733865,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWUO6HFJCMKFLGOCDTNOFDRXF4W5ANCNFSM4OBERX5A
.

It's distressingly easy. Maybe something has changed about the data api?

oh yeah, this quick again.  lemme sleep on it.  till then roll slower

Looks like the other process is waited on. That would mean that it has to finish doing the roll messages before it updates the init: https://github.com/SkyJedi/FFGNDS-Discord-Dice-Roller/blob/926c0a290c2874a484ad45d3a715ef95e84cada6/modules/SW.GENESYS/initiative.js#L25

Ahhhh, if is one of those "Do I need this code? No I do not need this code.
I have deleted the code.  Moments.
I think I know the fix, will test in the morning.
On Wed, Jun 17, 2020, 9:43 PM Timothy Regan<EMAIL_ADDRESS>wrote:

Looks like the other process is waited on. That would mean that it has to
finish doing the roll messages before it updates the init:
https://github.com/SkyJedi/FFGNDS-Discord-Dice-Roller/blob/926c0a290c2874a484ad45d3a715ef95e84cada6/modules/SW.GENESYS/initiative.js#L25
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SkyJedi/FFGNDS-Discord-Dice-Roller/issues/27#issuecomment-645735640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWUO6AK6X5NETZ23N3G6TLRXF5M3ANCNFSM4OBERX5A
.

its _better_but not bullet proof.  I need to completely overhaul initiative to really fix the problem.  so now just have players space out imitative rolls

Cool, iterative fixes get us there eventually.


Adding screenshots

issue: #6
adding listing commands

Hey @KunalKhandelwal1
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

@KunalKhandelwal1 please do only ONE task in a PR. Here, in this PR, you'll receive points for issue: #6, i.e. 10 points instead of 20 points. Kindly make another PR referencing issue: #5. For merging this, I'll be deleting Task-4.txt from this commit

Hey @KunalKhandelwal1
Your PR has been merged 🥳🥳 and you have earned 10 points.
Thanks for contributing in OpenCode'24 ✨✨


validate engine hash

Fixes #27574
Validates that flutter_tester --help gives us a Flutter Engine Version that matches the contents of bin/internal/engine.version.  This is meant to guard against regressions in the recipe scripts where we accidentally upload a revision to the wrong bucket folder.

The bot is confused because this PR doesn't modify a _test.dart file, but this does in fact add a test.

This is a good addition, but this only handles the upload side of #27574. The tool would also like to validate the cache contents after downloading

@jonahwilliams isn't this running after we download the artifacts again?

If there's more work you want to do for the linked bug we can reopen it

This change broke Flutter-engine-Dart head-head-head bot:
Running smoketests...
▌10:18:29▐ RUNNING: cd .; bin/cache/artifacts/engine/linux-x64/flutter_tester --help
▌10:18:29▐ ELAPSED TIME: 0.058s for bin/cache/artifacts/engine/linux-x64/flutter_tester --help in .
Expected "Flutter Engine Version: 2b75c6d111f768b349311884212fc50b454b921d", but found "Flutter Engine Version: 189ec1e7c43030f67a6323cd743bd449d2719eab".

This might be because HHH bot replaces certain parts of Flutter (e.g. flutter/bin/cache/dart-sdk) with a version built from sources (at HEAD).

Maybe we could add a flag for the bot to bypass this check... Why doesn't the bot just use the local-engine flag though?  Modifying the cache seems dangerous


Replace scandal file matcher with glob

now uses glob to search .ensime files
see #112 for more details

 You should sign our Contributor License Agreement in order to get your pull request merged.

:+1: Scandal's main functionality is searching the contents of files. For finding files by name, glob is a more appropriate tool.

@makovich Awesome! LGTM! I'll release.
Can you just sign the MIT licens

@makovich v0.32.1 published. Thanks a lot!

I'd clicked that "sign CLA button" dozen of times and nothing happened. It asks my to agree with terms, I do what it wants, and all the things still stand. Have no idea what it can be. Maybe closed PR prevent from signing.

@fommil, do you know why Paul can't sign CLA?
On Tue, Jan 26, 2016 at 2:52 PM Paul Makovich<EMAIL_ADDRESS>wrote:

I'd clicked that "sign CLA button" dozen of times and nothing happened. It
asks my to agree with terms, I do what it wants, and all the things still
stand. Have no idea what it can be. Maybe closed PR prevent from signing.
—
Reply to this email directly or view it on GitHub
https://github.com/ensime/ensime-atom/pull/115#issuecomment-175025123.

@makovich Can you trying going to settings -> Authorised Applications -> CLA Assistant, and Click 'Revoke' or similar.  I saw this something similar when I had accidentally rejected authenticating an github application and nothing worked after that.

@rorygraves @hedefalk I made that, wait a little bit and then repeat revoking + signing... Not works for me. Weird. What if?

maybe because it's closed. Probably it'll ask for the next PR?


feat: Support fast webhook update

Also cleaning away unnecessary fetch of environment

Make docs to update docs?

Make docs to update docs?

Good point


Running VMs on unsigned UTM

When I try to run UTM from Xcode, I cannot start a VM. When I use the instructions to build it unsigned, I still cannot start a VM. How can I start a VM while developing UTM?

Is there any error shown?
FYI only Emulated VLAN networking will work with an unsigned build.

Something about permissions error

Can you send a screenshot?

On Fri Jun 17, 2022 at 9:33 PM +08, Sandra Mattar wrote:

Yes, that means the VM is using either Shared or Bridged networking.
Change it to Emulated VLAN in the VM settings.

--
Reply to this email directly or view it on GitHub:
https://github.com/utmapp/UTM/issues/4139#issuecomment-1158876884
You are receiving this because you commented.
Message ID: @.***>

OK. Now I get

Do you have a VM running with UTM already? If not, go to Activity
Monitor and kill all the "QEMU Helper" and "QEMU Launcher" processes.

No. It works fine in the versions of UTM I download from the Releases page, but not when I build it myself.

I am using Emulated VLAN now. It still doesn't work.

If you're still having the error in your second screenshot, then try
rebooting your Mac (so the QEMU processes using that port won't be
running)

I rebooted my Mac and now I ge

t

Is there a way to completely turn off SPICE?

Worth noting that on maOS, UTM needs the hypervisor entitlement to run VMs in virtualization mode. See development docs.

Weird, not sure what would cause that error.


Configure docs ready for Travis

Saw you were having trouble getting docs to build. This is how I'd set them up—assuming you have the travis/codecov side of things sorted, I expect this to pass tests at least.
The docs pages 'build' for me locally, but since you don't have any written for the moment, there's not much to populate of course :smile:

Well, looks like your master branch may have some issues with packages: MakieRecipes is not found.

I had a broken package in the Project

You've got some restrictions in Project.toml that can't be satisfied in Julia v1.0. I'll allow failures there for the moment.

Is that because they rely on packages that use stuff from other packages that may use features from 1.5 that aren't in 1.0? So they have their own compat restrictions that are too high?

Something like that, yeah.

ERROR: Unsatisfiable requirements detected for package CairoMakie [13f3f980]:
CairoMakie [13f3f980] log:
├─possible versions are: [0.0.1-0.0.2, 0.1.0-0.1.3, 0.2.0-0.2.9, 0.3.0-0.3.3] or uninstalled
├─restricted to versions 0.3.0-0.3 by an explicit requirement, leaving only versions 0.3.0-0.3.3
└─restricted by julia compatibility requirements to versions: [0.0.1-0.0.2, 0.1.0-0.1.2] or uninstalled — no versions left

So if CairoMakie needs > 1 in v0.3+, then you can't tag that version...

I've droped GLMakie and WGLMakie and CairoMakie as dependencies here, since you're developing a library and want to give users the freedom to set up and use it how they wish. Looks like, for the most part you want to rely on AbstractPlotting. Take a look at how InteractiveChaos works for example.
For interactions, when you need a GL backend then you can suggest
using BioMakie, GLMakie

in the docs.
I'd say this is really how you want to develop this package, but primarily I did this since I'm not even sure it's possible to build GLMakie on Travis at all...
If that's something you're not happy with, or can't work with, then getting the package to function on Travis is a bit outside my wheelhouse. GLMakie itself seems to build fine using gitlab-ci, so perhaps that's something to investigate?
Otherwise, looks like things are building just fine now. When you merge, you may want to squash this PR - I made a bit of a mess of it sorry. One thing you'll need to do before the automatic push works is add the DOCUMENTER_KEY.


Add macOS arm64 or universal2 wheels

xref https://github.com/scikit-build/cmake-python-distributions/issues/132

@mayeut will you have time to to do this? Or should I plan to work on it in the future? We could also move to cibuildwheel, I think.

As of now, I've just been looking how to upgrade the ninja version and there's one question which comes to my mind @jcfr probably has answer to:
I see that the upstream ninja repo now provides a universal2 binary however, this repo uses the Kitware fork to provide the make-style jobserver support.
I see multiple options and would like to know which one is appropriate:

update with upstream 1.10.2
Ask Kitware to release a 1.10.2 with make-style jobserver support and a universal binary.
rebuild from current sources

If the answer is to build from sources, I'll have no way to test universal2 (no way to test in other cases as well but I'd rely on upstream or Kitware testing their released artifacts).

Thanks for the derailed summary.
I ask the CMake team to publish arm64 binaries. Will update this issue when I hear back.

I've got an M1 and am happy to test if you need me to.

Will update this issue when I hear back.

It turns out we (aka colleagues working on CMake and VTK) are working this.
See https://gitlab.kitware.com/utils/ci-utilities/-/merge_requests/11

I've got an M1 and am happy to test if you need me to.

That is great.
@mathstuf and bradking: If needed, @henryiii offered to help test.

It turns out my colleagues are working on this.

great news.

I've got an M1 and am happy to test if you need me to.

Thanks @henryiii, have you been able to test cmake ? (I wouldn't expect any issues)

will you have time to to do this? Or should I plan to work on it in the future? We could also move to cibuildwheel, I think.

I can prepare the same work as is being done on cmake to move to cibuildwheel.

have you been able to test cmake

Yes, just a very basic install and --help so far, but that worked fine.

Looks like the linked MR was merged two weeks ago. What's the status for a release we can package (not sure where to find that in the repo)?

What's the status for a release we can package (not sure where to find that in the repo)?

I can see the tag in the Kitware repo but there's no release and no binary assets associated with that tag: https://github.com/Kitware/ninja/releases/tag/v1.10.2.g51db2.kitware.jobserver-1
@jcfr, can you check with your colleagues about that please ?

Binaries are available here: https://gitlab.kitware.com/utils/ci-utilities/-/releases/ninja%252Fv1.10.2.g51db2.kitware.jobserver-1
We already have gitlab-ci set up with access to macOS and Windows machines which seems to still be difficult on GitHub actions, so we just reused that infrastructure.

Thanks for the links @mathstuf
FYI, the Windows archive returns a 404 not found error on my end.
Given we're already building from source for almost all architectures and that the build seems much simpler than the one for CMake (and also much shorter), I wonder if we would be better off building everything from sources (using cmake rather than python bootstrap as is done in Kitware CI and also upstream CI) ? I will draft something for this. The only gotcha is that it might require to wait for a new release of scikit-build or some clever tricks for universal2 if going this way ?

FYI, the Windows archive returns a 404 not found error on my end.

Hmm. Somehow the Windows binary got missed in the upload glob? I'll look at that next week.

fixed by #63


getting error

Error while creating release definition: Tasks with versions 'Replace variables in Ansible script to deploy Azure resources:4., Run playbook to deploy Azure resources:0.' are not valid for deploy job 'Agent job' in stage Azure Dev.

@beginner-academy kindly provide more info on the template that you are using.


Walles/packaging

Added basic setup.py

Looks like reasonable changes to me. Perhaps we should use the entry_points parameter to setuptools.setup instead of writing really short scripts in bin? Less boilerplate for FTW. (There is an example using this in gerrit2ghe setup.py)

@nresare: Good point, fixed!

@walles the scripts arg to setup needs to go, as it references something that no longer exists. Also the main methods referenced are expected to take zero args.

looks good to me :) :+1:


[SPARK-50283][INFRA] Add a separate docker file for linter

What changes were proposed in this pull request?
Add a separate docker file for linter
Why are the changes needed?
1, to centralize the installation of linter;
2, to spin it off the single docker;
Does this PR introduce any user-facing change?
no, infra-only
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no

also cc @panbingkun

Merged to master.


Create ConvertDaysToHours.ts

Closes #4280
What's being changed:
Added TS file to convert days to hours

@Greeshma-frontier
The issue you linked is for R program. Please link the TS one.
Thank you!

Merged in #4355


New extension: Fake 3D

Description
This extension uses ZOrder as an Z axis
How to use the extension

Install 3D extension
Open object behaviours
Add new behaviour
Now the object will be generated as 3D object. There are also some conditions and actions

Checklist

[X] I've followed all of the best practices.
[X] I confirm that this extension can be integrated to this GitHub repository, distributed and MIT licensed.

Example
https://gamejolt.com/games/3d-gdevelop/723513
Extension file
https://gamejolt.com/games/3d-gdevelop/723513

Hello :3
Cool extension, it seems fun to play around with it.
here is a few things that's required for the extension:
1- An example(Gdevelop project) is required to see how this extension work in action.
2- Rename action (Create an 3D object) to (Create 3D object) or (Create a 3D object).
3- Rename action (Add force in 3D) to (Add 3D force to object).
4- If you set the speed on Z axis to -5 or -1 (just any minus number) ,and then previewed the game, the object will disappear until you release the key (set as condition to add the force) then it will appear again.
5- the action (Create 3D object) doesn't seem to work, i set at the beginning of the scene to create and object at the center of the scene window, but nothing happened.
6- I don't think changing the object size to its Z order is a good idea.
7- (Z position) we already have a condition (Z order) to check the Z order of the object, its better to use it on creating another one.
8- (3D collision) ^ Same thing apply on the collision condition.
9- Rather on adding an event to check if the Object z order is less > than 2 then change it to 2
You can prevent the action (change object size set to its Z order) from happening if the Z order is less than 2
by setting a condition (Z order of Object is Greater than 2
Over all the extension have potentials but its still in a very basic position and require a lot of updates and improvements :3
Thanks for submitting it and we hope to have more extensions from you in the future 😉


Imginn?

Every time I use farside.link/bibliogram/*, I get redirected to imginn.com. This redirection is probably done by the only Bibliogram instance left in your curated list, https://bibliogram.privacydev.net

What is this service?
Has it been vetted? There's no privacy policy, no source code, and very little information
There's also imginn.org, same code, different UI?

Hi everyone, I'm discontinuing Bibliogram.
I'm doing this because I just don't want to work on it anymore. It's very depressing because I'm working against a hostile system and a hostile company, and not very rewarding since I do not personally care about anyone/anything on Instagram. It's a chore that Instagram is continuously and actively trying to stop me from doing. I have been thinking about this for a couple of weeks.
There will maybe be one more commit for personal use and one more commit that public instances can use to display a >discontinued message and remove user lookup functionality. Bibliogram can still be used to view individual posts, which is >pretty cool, so having it as just a post viewer will be its future - until that breaks too.
Bibliogram is still really good code to work on if anybody wants to try to fix collecting the data from Instagram. You can write a >new function (or edit an existing one) in collectors.js to make an upstream request, and then you can parse the response using >whatever you want, and return a User structure. You're welcome to maintain a fork if you fix this, but if you plan to upload your >fork to GitHub, please also edit the readme. (While you're at it, I'd suggest a name change to reduce the risks of legal action - >Bibliograph is a name that's been floating in my head for a while that you can use if you'd like.)
I have not received any legal demands and there are no legal restrictions on Bibliogram or its code besides the AGPL license.
It's been two and a half years. This is now a mourning chatroom. Thanks for the fun, and pour one out for Bibliogram.

Source: https://matrix.to/#/!seqaBRImHwZJpNbjYb:cadence.moe:8111/$SVA58yktA7bSubQ6L760sJwl0gpH3FkxB1BtIX4Hwi0?via=cadence.moe&via=matrix.org&via=tchncs.de

@neurodiverseEsoteric I forgot to state the obvious, i.e. that I'm aware of the discontinuation of Bibliogram, but that still leaves the questions posed.

Hi! I am the owner of https://privacydev.net and since I discontinued to host my Bibliogram instance because of its broken state, I wanted to redirect people that still find links and have bookmarks that point to https://bibliogram.privacydev.net to another working Instagram front-end to make it as painless of a shutdown for the users as possible.
Since all Bibliogram instances are equally broken as mine was and Imginn offers a superior experience for users without an account compared to using Instagram directly, I decided to automatically redirect users to valid Imginn URLs instead.
I did ask the Bibliogram maintainer to remove my instance from the official instance list because of that a while ago as well, which they did.
I understand that this may not be the behavior that everybody expects and I apologize for any confusion. But it was an easy transitional solution that I hoped would cause as little friction as possible.
But since it is not actually a Bibliogram instance it would be best to remove my instance from the list as well.

@PrivacyDevel Thanks for explaining the situation. I assumed this was the case, but I'm also trying to find out if Imginn can be trusted privacy-wise.

I've removed the instance, since I don't personally know anything about Imginn.

That said, in light of the news of Bibliogram no longer being actively developed, I'm a bit torn on whether or not Farside should continue supporting Bibliogram redirects. I guess there's always the possibility that someone else steps up and figures out a solution to the recent changes to Instagram's user profile page. But in the meantime, anyone relying on Farside for Bibliogram redirects will probably get annoyed that all of the instances are down. Anyone have any strong thoughts one way or another?

Well, considering that Bibliogram isn't working anymore for user profiles at least, I see the following possible solutions:

redirect them to Imginn like I do for the reasons I just mentioned
redirect them back to the original Instagram URL
remove Bibliogram redirects completely (leads to dead links)
only redirect non-user pages, as those actually still work sometimes
create an informational page with a links to the original Instagram and / or Imginn URLs

Solution 5 would probably be the cleanest solution.

According to the message by the dev, it still partly works (posts, not user pages), which makes it a bit more complicated.


[BEAM-3293] Add check for error on NewIterable call

Restore a check of an error message from the NewIterable call. A nil, error return from NewIterable would still error for makeSideInput; however this makes the error more clear.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @lostluck


merge from konsum-frontend-svelte,template-svelte-app

package.json

chore(deps): add ^6.12.52 remove ^6.12.51 (devDependencies.npm-pkgbuild)

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

v1.29.25
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Suggestion: Grids seperating the nodes.

Hi,
We have tried your interface in a test environment, i hope you do not mind a suggestion in the interface design.
Currently in our Cloud environment we have various nodes with different cpu counts. Some nodes have 64 cores, some have 32 and others 8. In your current design it is difficult to see a difference where node X starts and stops. Example:

To give a suggestion: Perhaps insert a set grid between each node with some whitespace and perhaps a single line to separate each node , this would help in visibility. I would suggest to set the grid space for every node based on the largest node in the cluster.
Thanks for your current work so far! :+1:

Hi @a-nldisr,
Thanks for your feedback.
Your remark is very relevant, we'll work to improve the visualization in this way.
Cheers

Looking forward to the improvements! :+1:

Please check down the latest commits and let me know what you think...

Wow, great work! :+1:
It works excellent:
https://ui.hpccloud.surfsara.nl/oneinsight/frontend/

Thanks for the feedback.

Last point: From the link you shared with us (thanks again), I found a minor problem with tooltips (the turquoise color is not for 100% load). I fix that in my latest commit.

Great work! :+1:

hi @a-nldisr ,
I made some improvement in oneInsight that significantly improved your node grid here: https://ui.hpccloud.surfsara.nl/oneinsight/frontend/
Try it out and let me know.
Regards,
R.

Hi @rchakode
I no longer work at SURFsara, but i'll forward it to the guys there. Thanks!


updating README to contain link to netlify deployment

@vinomaster found issues in the README that hadn't been fixed, yet.

We are now committing to dev, not main.  Closing PR.


Adding swagger for redis cache 2016-04-01 api version

Hi @TimLovellSmith, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (tilovell). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

No modification for NodeJS

No modification for Python


Added projects and users api

Looks good to me, could you fix the go lint issue?

Fixed linting

Could you add the new endpoints examples and test cases for test coverage?

Working on it.

Hi @ramakantar, in order to add test case you need to work on three point:

add a new test function in the ${filename}_test.go file
add mocked data for the API response (https://github.com/Colstuwjx/awx-go/tree/master/internal/mockserver/mockdata)
add an handler for the API in the https://github.com/Colstuwjx/awx-go/blob/master/internal/mockserver/mockserver.go file


Java

Add to docs:
$ java --request
and click “More Info…” to visit the Java Developer Kit download website.
Otherwise:
Unable to find any JVMs matching version "(null)".
No Java runtime present, try --request to install.
Unable to find any JVMs matching version "(null)".
No Java runtime present, try --request to install.

Added to wiki:
https://github.com/mhulse/dotfizzles/wiki/Optional-dependencies


Redis Cache example

I think, first of all we must mention that it's StackExchange.Redis implementation. From this article- it's not clear. As well as mention, that it's one of possible implementation for .net, because our friends from Pluralsight creating question for "architecture" roleIQ based on this documentation and asking about this client as about only single possible implementation.
Second moment, I would suggest to rephrase this "The GetMyEntityAsync method in the following code example shows an implementation of the Cache-Aside pattern based on Azure Redis Cache", because code is Redis specific, not Azure Redis Cache specific. For a not expert in a question, this sentence could tell that Redis in Azure significantly different from regular Redis implementation

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

ID: 67f58625-4e97-1fc6-197b-8b25341f5a4f
Version Independent ID: bdabf990-9a18-ec7f-a948-3fc79dc255e0
Content: Cache-Aside
Content Source: docs/patterns/cache-aside.md
Service: guidance
GitHub Login: @dragon119
Microsoft Alias: pnp

Good point - I'll clarify this in the doc.


Managed Identity: Configurable timeout based on time

Feature Request
Currently, the retry logic in the Azure SDKs for Managed Identity token generation supports a configurable time out based on counts. For response time sensitive services this has not been enough. Per customer feedback, they would like to have timeout configuration based on time (i.e. milliseconds)
This will allow for quicker fail after certain.
Can we make the retry max configurable based on time?
@binderjoe FYI

Yes. But also the ability to just set the time, without having to set the number of tries. Apologies for the delay in responding.
Thanks,
-Arturo
Managed Service Identityhttp://aka.ms/msidocs
From: Joel Hendrix<EMAIL_ADDRESS>Reply-To: Azure/azure-sdk-for-go<EMAIL_ADDRESS>Date: Thursday, January 31, 2019 at 1:56 PM
To: Azure/azure-sdk-for-go<EMAIL_ADDRESS>Cc: Arturo Lucatero<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-sdk-for-go] Managed Identity: Configurable timeout based on time (#3975)
@arlucahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farluca&data=02|01|arluca%40microsoft.com|efc6ea6440fc420865f308d687c6ed11|72f988bf86f141af91ab2d7cd011db47|1|0|636845685785475839&sdata=OdWII4Ge%2B72CCu8mC9DiJBkYRnNX1RdRfMCUn%2F3Cscc%3D&reserved=0 to make sure I understand, the ask is to add a cap to the max time spanning retries? E.g. it might retry N number of times within X amount of time? So whichever value is exceeded first fails token generation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-for-go%2Fissues%2F3975%23issuecomment-459521454&data=02|01|arluca%40microsoft.com|efc6ea6440fc420865f308d687c6ed11|72f988bf86f141af91ab2d7cd011db47|1|0|636845685785485834&sdata=oXhKFnZ%2FYK2wV6ENEvp9eMcYVPja%2BbEl1KW5kdjsqaI%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANREMl86zAVTq9sqMuQ9zGqCfCqZ3M40ks5vI2Z_gaJpZM4abUZL&data=02|01|arluca%40microsoft.com|efc6ea6440fc420865f308d687c6ed11|72f988bf86f141af91ab2d7cd011db47|1|0|636845685785495824&sdata=a6%2BYoRlPfXRR9OJ5rric7fuggHztgQQwI1rtRkKeV0Y%3D&reserved=0.

Actually I think you can achieve this today by setting MaxMSIRefreshAttempts to 1 and using a context with the required deadline (sample code below).  Are you able to try this out and verify it works as required?
package main

import (
	"context"
	"os"
	"time"

	"github.com/Azure/azure-sdk-for-go/services/redis/mgmt/2018-03-01/redis"
	"github.com/Azure/go-autorest/autorest"
	"github.com/Azure/go-autorest/autorest/adal"
	"github.com/Azure/go-autorest/autorest/azure"
)

func createSPT() (autorest.Authorizer, error) {
	tenantID := os.Getenv("AZURE_TENANT_ID")
	oauthConfig, err := adal.NewOAuthConfig(azure.PublicCloud.ActiveDirectoryEndpoint, tenantID)
	if err != nil {
		return nil, err
	}
	clientID := os.Getenv("AZURE_CLIENT_ID")
	clientSecret := os.Getenv("AZURE_CLIENT_SECRET")
	spToken, err := adal.NewServicePrincipalToken(*oauthConfig, clientID, clientSecret, azure.PublicCloud.ResourceManagerEndpoint)
	if err != nil {
		return nil, err
	}
	// limit MSI token acquisition retry attemps to one
	spToken.MaxMSIRefreshAttempts = 1
	return autorest.NewBearerAuthorizer(spToken), nil
}

func main() {
	auth, _ := createSPT()
	client := redis.NewClient(os.Getenv("AZURE_SUBSCRIPTION_ID"))
	client.Authorizer = auth
	// specify a context with a 500 millisecond timeout
	ctx, cancel := context.WithTimeout(context.Background(), 500*time.Millisecond)
	defer cancel()
	client.Create(ctx, "rgName", "redis1", redis.CreateParameters{})
}

Let me chat with the customer.
Arturo Lucatero [LinkedInhttps://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Farturo-lucatero&data=04|01||1f19e83c655c43523fb208d61833ec23|72f988bf86f141af91ab2d7cd011db47|1|0|636723008644823124|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=RKgUrONgQDBbP4wIa0fUm3K1n%2B5GCYvqn%2FBiZ0eGk0Y%3D&reserved=0 | Twitterhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FArLucaID&data=04|01||1f19e83c655c43523fb208d61833ec23|72f988bf86f141af91ab2d7cd011db47|1|0|636723008644833136|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=o2%2FWgOKikQzXxhgnEM%2BBhUhScrWpPYkZsj2BvqelJkg%3D&reserved=0]
Managed Identities for Azure resources docshttp://aka.ms/msidocs | Onboarding to Azure IAMhttps://microsoft.sharepoint.com/teams/AzureMSI/SitePages/Home.aspx | Azure IAM office hourshttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FAzureRBACMSI-OfficeHours&data=04|01||1f19e83c655c43523fb208d61833ec23|72f988bf86f141af91ab2d7cd011db47|1|0|636723008644843145|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=i5udbijTDcf0PE2JGJM6LBiG4D%2Bwcn0V9EqNJB4ZNb0%3D&reserved=0
From: Joel Hendrix<EMAIL_ADDRESS>Sent: Monday, February 11, 2019 12:43 PM
To: Azure/azure-sdk-for-go<EMAIL_ADDRESS>Cc: Arturo Lucatero<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-sdk-for-go] Managed Identity: Configurable timeout based on time (#3975)
Actually I think you can achieve this today by setting MaxMSIRefreshAttempts to 1 and using a context with the required deadline (sample code below). Are you able to try this out and verify it works as required?
package main
import (
    "context"

    "os"

    "time"

    "github.com/Azure/azure-sdk-for-go/services/redis/mgmt/2018-03-01/redis"

    "github.com/Azure/go-autorest/autorest"

    "github.com/Azure/go-autorest/autorest/adal"

    "github.com/Azure/go-autorest/autorest/azure"

)
func createSPT() (autorest.Authorizer, error) {
    tenantID := os.Getenv("AZURE_TENANT_ID")

    oauthConfig, err := adal.NewOAuthConfig(azure.PublicCloud.ActiveDirectoryEndpoint, tenantID)

    if err != nil {

           return nil, err

    }

    clientID := os.Getenv("AZURE_CLIENT_ID")

    clientSecret := os.Getenv("AZURE_CLIENT_SECRET")

    spToken, err := adal.NewServicePrincipalToken(*oauthConfig, clientID, clientSecret, azure.PublicCloud.ResourceManagerEndpoint)

    if err != nil {

           return nil, err

    }

    // limit MSI token acquisition retry attemps to one

    spToken.MaxMSIRefreshAttempts = 1

    return autorest.NewBearerAuthorizer(spToken), nil

}
func main() {
    auth, _ := createSPT()

    client := redis.NewClient(os.Getenv("AZURE_SUBSCRIPTION_ID"))

    client.Authorizer = auth

    // specify a context with a 500 millisecond timeout

    ctx, cancel := context.WithTimeout(context.Background(), 500*time.Millisecond)

    defer cancel()

    client.Create(ctx, "rgName", "redis1", redis.CreateParameters{})

}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-for-go%2Fissues%2F3975%23issuecomment-462486582&data=02|01|arluca%40microsoft.com|2d74fc798766479b241b08d690618189|72f988bf86f141af91ab2d7cd011db47|1|0|636855145790577526&sdata=FalNP6RpqjZmRtstanXT98289E70FcqcNW9sqyP59a0%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANREMtfreALr9Nx18N20hCog1LfmomPaks5vMdXRgaJpZM4abUZL&data=02|01|arluca%40microsoft.com|2d74fc798766479b241b08d690618189|72f988bf86f141af91ab2d7cd011db47|1|0|636855145790589042&sdata=%2FvfRKrt9uWFulyUNQzrK15dFBqggehRKml26pFlJJ4Y%3D&reserved=0.

@jhendrixMSFT : This helps with limiting the number of tries; however, what about limiting the period of time before it times out (even within a single try?)

In this sample the context should time out after 500ms and cancel the in-flight request.  Are you saying that isn't happening?

Per offline discussion this works for the customer so closing.


Add deploy script

Deploy script should be triggered by pushes to main. It will deploy the project to GitHub pages, including a custom domain and HTTPS.
See Astro docs for implementation guide.
Domain (21ctownball.com) registered with iwantmyname.

Deploy script has been created and DNS configured for dev.21ctownball.com.
When ready to release 1.0, GitHub settings and DNS will have to be reconfigured for apex domain (see #19).


Panic if an unsupported trait definition passed

This is an error on the side of the proc-macro that uses derive_utils and users of the proc-macro see a useless error message. This should be clearly separated from input errors that returned by EnumData::parse.

bors r+


Issue #18: Illegal document name on create_annotation

What's in the PR

Use a dummy name without a slash

How to test manually

No specific test procedure

Automatic testing

[x] PR includes unit tests

Documentation

[ ] PR updates documentation

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


chore: Update deprecated patchesJson6902 to patches in yaml

Update deprecated patchesJson6902 to patches in yaml

Checklist

[ ] When introducing a new scaler, I agree with the scaling governance policy
[X] I have verified that my change is according to the deprecations & breaking changes policy
[ ] Tests have been added
[ ] Changelog has been updated and is aligned with our changelog requirements
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[X] Commits are signed with Developer Certificate of Origin (DCO - learn more)

I don't know why this update will affect scaling_modifiers_test. Do you have any idea? @JorTurFer


[WIP] Airplane Improvements

Working on a fairly substantial improvement to the coverage of the library
Note: These changes are breaking and will be a new major release

Modify how the auto-cli works by removing the requirement of having a main function and instead moving to a subcommand based approach. This allow more flexible use as both a library and a CLI tool and feels very much how the AWS SDK works.
All functions now handle both CLI calls and lib calls from the same function
Standardize Auh Librarary to single calls
BBOX api now writes to STDOUT in CLI mode
Bounds API now has list & stats modes
Add support for clone API
Add support for feature ID api
Add support for feature key API
Add support for feature history API
retire the register library - replaced by generic user library
introduce user library with user info lookup & registration
Add Server Meta API
Add Stats API
Add auth tests

cc/ @mapbox/search

👋 @ingalls this merged with codecov failures due to an -11.23% drop in test coverage:

Is that intentional? /cc @mapbox/search @ianshward

Responded in slack.


Add document for encoding literal values for all wit types

Adds docs written by @lann for how to encode literal values for all the various wit types. Once this is merged we can update the parser to handle this.
One interesting thing will be that in this proposal some the type of literals are not ambiguous. For example: 1 can be any of the various integer types. "hello" can be a string, option<string> result<string> and more. We'll have to see if this causes problems and perhaps make the encoding more strict if it does.

Was able to get support in for records, enums and variants, and it seems to work fairly well. Going to merge this.

Cool. I've been slowly working on a standalone parser & writer for the syntax too with the hope of eventually upstreaming it into wasm-tools.


Azure Frontdoor configuration subdomain patterns with wildcard

In continuation of https://github.com/MicrosoftDocs/azure-docs/issues/63099
ruleA forwards all requests for a*.myDomain.com/* to backendPool-A (e.g. a1.myDomain.com, a2.myDomain.com)
ruleB forwards all requests for b*.myDomain.com/* to backendPool-B (e.g. b1.myDomain.com, b2.myDomain.com)

Front Door states supporting wildcards only at the end
Pattern must start with a / and the only allowed asterisk is at the end, and asterisk must be preceded by a slash (/*).
If I want to specialize my filtering using a rule with the rule engine, it doesn't seem to properly work.
In my example, I am trying to match *-app.mycustomdomain.com. I added the following rule >

And I bind the rule to the source/target with

But every request made to mycustomdomain ends up in the same downstream service. E.g. contoso.mycustomdomain.com shouldn't be routed, but it is.
Is there any other way to achieve this level of matching?

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

ID: 81a99fee-aaee-89d5-958b-ab645d8f6a00
Version Independent ID: edeb5885-5b26-299d-8ffe-6d0be1533769
Content: Azure Front Door - Support for wildcard domains
Content Source: articles/frontdoor/front-door-wildcard-domain.md
Service: frontdoor
GitHub Login: @duongau
Microsoft Alias: duau

@bobleujr , thank you for your query. We'll review this and get back to you shortly!

The issue was with the time it took for the change to be effective, but it works. I am closing this


Entities type hint

This PR adds type hints for the entities module. Just starting on slowly making the code nicer :)

Thanks for the review and suggestions @efredriksson-modelon , I have now made the suggested fixes. Could you please take another look? :)


force test to front of queue / start right now

From @arlake228 on March 14, 2015 12:21
Original issue 924 created by arlake228 on 2014-06-11T13:33:25.000Z:
A reasonably common issue that comes up is the inability for administrators to perform a test “right now”. Either end might be unable to schedule a test for some period of time despite an administrator wanting to be able to verify something in the near term.
A possible solution to this would have the ability to have certain tests be authenticated and allow those tests to go to the front of the queue. Because this impacts both sides and potentially a side where the local admin is not the admin on the far end being able to do this arbitrarily seems undesireable.
It would additionally be useful if an authenticated test were able to cancel an existing test, such as if a currently running test were say 15 minutes long and even getting to the front of the queue would not help enough.
Copied from original issue: perfsonar/project#922

Comment #1 originally posted by arlake228 on 2015-01-27T14:49:10.000Z:
<empty>


distributed xgboost mpi examples

Is there an example of running distributed xgboost on mpi

The official documentation currently doesn't provide an example. Try posting at the user forum https://discuss.xgboost.ai/ to see anyone else has tried it. Again, contribution is welcome.

Consolidating to #3439. This issue should be re-opened when someone decides to write a tutorial with MPI.


fix: Strip and ignore trailing hashes

I have found that some symbols have a $<32 hex digits> suffix, that when stripped will demangle the symbol perfectly fine.

Do you have any idea where these come from? I've never seen this before.

Not entirely sure, this is one of the long list of demangling failures we get at sentry. It could be possible that they come from a different step of our pipeline and would need to be stripped out differently. CC @jan-auer ?

I'm not opposed to merging this but I would still like an answer to the question.

Hm, this slipped my radar. We were briefly looking into where these things might come from internally but didn’t find anything obvious looking through the code. I think we can deal with these suffixes in symbolic rather.


Some emmet css abbreviations with ":n" value don't work as expected

Issue Type: Bug
Abbreviations like list:n, bdt:n, bgi:n, q:n are expanded into properties with value of "n" instead of "none", bg:n expands into "no-clip" instead of "none". I haven't tested all abbreviations, so it's likely that there are more cases like these.
 Also you might want to label this as upstream.

@sergeche should the default values all be none in these cases?

For n abbreviation value the output should be none

Some of the abbreviations have been fixed, though I just did a test and realized bg:n still expands to background: no-clip; so I will have to configure the upstream snippets file some more.

Some of the abbreviations have been fixed, though I just did a test and realized bg:n still expands to background: no-clip; so I will have to configure the upstream snippets file some more.

This is more of a note-to-self, but some of the properties are compound properties, which means none can possibly show up in those properties too.
For example bg:n implies bgi:n (https://stackoverflow.com/a/20784582).
Therefore, I'd have to adjust my CSS none property scraper https://github.com/rzhao271/css-none-scraper to check those cases.
Switching task to backlog as it's low-pri.

The upstream issue has been fixed, so now what's left is to figure out why vscode-emmet-helper isn't handling the cases properly. There is most likely a configuration issue somewhere, e.g. see https://github.com/emmetio/emmet/commit/5f8782bc84cd28169b11eb05ea05291d735d8ae9#diff-c3095d5010e65c52737a98a5d618ea24049ebe90c8470752426081d70ed6e012R329 for reference.

@TylerLeonhardt successfully reproduced and looking into this (AnitaB OSD)

@kelleyneubauer it looks like this issue is marked as "upstream" which means that the problem is in https://github.com/emmetio/emmet/issues/628#issuecomment-810522830 as @rzhao271 mentioned. You could try to investigate that, but we don't know too much about that source code so it could be harder than expected.
@rzhao271 correct me if I'm wrong

@TylerLeonhardt looking at the prior fix before the issue was reopened, it seems that the solution might be just one line of code in test/stylesheet.ts: equal(expand('bn:n'), 'background: none;'); ...this is my first time working with open source, not sure how or if I should proceed

I haven't looked at this issue in a while, and would have to reconfirm the tests upstream fail.
If they do, then the issue is still in the upstream repo.

@rzhao271 got the bg:n css abbreviation closed vide PR

The original issue is fixed now.

Paste the following in a CSS file

.test {

}

Place the cursor between the braces and type bg:n
Emmet should suggest background: none instead of background: no-clip;
Accept the completion just to confirm it works, but delete it after
Repeat steps 2 to 4 with the abbreviation bdt:n, which should expand to border-top: none;


Bug in phpDocumentor2 @method parser

7.11 @method: https://github.com/php-fig/fig-standards/blob/master/proposed/phpdoc.md#711-method says that methods should be documented with @method [return type] [name]([type] [parameter], [...]) [description]
Appendix A. Types: https://github.com/php-fig/fig-standards/blob/master/proposed/phpdoc.md#appendix-a-types says that @return int[] (type followed by []) is proper array notation.

Well, try documenting this class in phpDocumentor2:

This is the result. It totally dies:

As you can see, phpDocumentor2 dies whenever the @method type is Class[] as opposed to Class. It then fails to parse the line and outputs a blank method name instead...
It also fails for lines with @method $this setSomething() and outputs those as blank too. Even though PSR-5 (at the bottom of its type-appendix) says that $this is a valid type.
As far as I can see from PSR-5, my @method syntax is correct in all of our files...
We use relative class-paths for the types (as opposed to FQDN), and trailing [] syntax for arrays of objects. You can see our files here: https://github.com/mgp25/Instagram-API/tree/master/src/Response

I just checked our regular @return VideoUploadUrl[] classes.
Those are properly documented:

That means the Class[] syntax is a valid return type, and that the phpDocumentor2 bugs are only in the @method parser. I guess it doesn't get much love and attention since not many people use it. ;-)

Thanks for this complete report. Only thing I'm missing is which version of phpdocumentor you are using.
We are currently working very hard to get phpdocumentor v3 out. We would be very pleased if you are able to test our current development version to check if this issue still exists. If so we will have a look.

@jaapio Hi. Sorry, I forgot the version:
phpdoc --version
phpDocumentor version v2.9.0

And it's great to hear that v3 is on the way. I know what it's like to work on a big project (similar level of stars and activity as this one) and know what it feels like to be close to a new major release. I hope it goes well and relieves pressure. :-)
Unfortunately I can't test the dev version. I installed phpdocumentor with Homebrew which has no "from-source" version for that formula: https://github.com/Homebrew/homebrew-php/blob/master/Formula/phpdocumentor.rb

However, if any of you clone this repo, you can check if it's fixed in v3:
https://github.com/mgp25/Instagram-API.git

#1926 shows that this works with v3.0.0-alpha1.


Add Instructor Model to Embeddins

Add new Instructor model to embeddings

Actually need to fix this, ignore for now

Was broken, should be fixed now.

Hi @enoreyes. Seems that we cross paths a bit and have duplicate PRs (https://github.com/hwchase17/langchain/pull/756) for the Instructor embeddings (they are very cool). I am not expert but your structure looked better (and you had tests!!) - but I noticed that there were a few differences in function. Have commented directly in the PR. If I can help in any way let me know.

@enoreyes @seanaedmiston what do you think about making this a separate class entirely? the reason i think this might be nice is the logic seems to diverge kinda substantially (theres 3 separate places with the if... else... loop). i can also take a stab at this and see what i might look like

@enoreyes @seanaedmiston took a stab at it here: https://github.com/hwchase17/langchain/pull/811
i think i kinda like it! the different in the embedding logic is different for every method, so i dont actually know what we gain by having them in the same class
Thoughts?
that pr still needs to be cleaned up (and to work with the test here, etc) so if you like/agree maybe you could take over from there?

@hwchase17 I agree with your separation of Classes. I'll pick this up and try to add in the separation of instruction for query vs. embed.

closing as other pr landed!


PAK message tracker

Not looking to merge before 1.0.
Adds additional message logging options, which can be read by an external program to generate an IPS trace. This is toggled with an additional config option MessageTracking (defaults to False, i.e. off), and the location of the log set with an additional config option MessageTrackingLogFilePath (defaults to /var/log/calico/calico-message-tracker.log)
Also updates some actor names for increased specificity.
@joe-marshall @fasaxc

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Can one of the admins verify this patch?

We'd like to get this merged at some point, but Patrick has finished his internship.
I'm going to own this patch and get it reviewed/merged, but I don't have a firm timetable for doing so.

Can one of the admins verify this patch?

The only non-trivial merge conflict is in calico/felix/fiptables.py:
<<<<<<< HEAD
    def __init__(self, table, ip_version=4):
        super(IptablesUpdater, self).__init__(qualifier="%s v%d" % (table, ip_version))
=======
    def __init__(self, table, config, ip_version=4):
        super(IptablesUpdater, self).__init__(qualifier="v%d-%s" %
                                                        (ip_version, table))
>>>>>>> master

I can't see any difference between the two, so I'm going to resolve in favour of master and assume everything will be okay.

@fasaxc Assigning this to you for review, but this is a lower priority than Miroslav's changes (since he's still around in the office).

ok to test

General thoughts:

Unfortunately, the logging as structured will be too expensive because it does lots of work to stringify the log messages as JSON before handing it off to Logger.info().
There's a lot of duplication between the log calls.  We should have a utility method for logging that something happened to a message.  That method should return immediately if the function is disabled and it should handle formatting a generic JSON object.  This could even be a method on the Message object itself.
We're using a logger but we're duplicating its functions (such as logging time in our own format).

i.e.
msg.log_event("Sent")
msg.log_event("Received")
msg.log_event("Attempted")
msg.log_event("Succeeded")
msg.log_event("Failed", exc=e)
msg.log_event("Batch failed", exc=e)

I think this has enough problems that we should close this PR and revisit if we decide to add this function later.
My number one concern is that this is all on the critical path of message passing so it needs to be very defensive and low overhead, especially when turned off.


Add CI

Adding tests (#1) is good, but actually running them is even better!

Will add deploying via Github releases tomorrow.

Resolved by #7


Compatibility issue with cudnn 7.0.5 and cuda 9.0

My source code required tensorflow 1.7.0 with cuda 9.0 and cudnn 7.0.5 version. However when i install cudnn 7.0.5 then my cuda 9.0 version downgraded to 8.0 that arise error during training. While when i install cuda 9.0 and cudnn 7.1.2 then i got following error:
E tensorflow/stream_executor/cuda/cuda_dnn.cc:396] Loaded runtime CuDNN library: 7102 (compatibility version 7100) but source was compiled with 7005 (compatibility version 7000).  If using a binary install, upgrade your CuDNN library to match.  If building from sources, make sure the library loaded at runtime matches a compatible version specified during compile configuration.

@Vishal2188
Any update on this issue please. Thanks!

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


[WIP] Support for Wink oauth application authorization

Description:
Wink added a developer portal recently and client_id and client_secrets obtained from there do not support the grant_type of password like the old client_id and client_secrets do. So... this adds support for authorizing your application (HomeAssistant) like the fitbit component does. I copied most of that code.
Users will only be able to use this new method for oauth meaning they will need to update their configs and follow the new flow. People without client_id and client_secrets can still use the username and password method which uses the Home-Assistant.io form to get an access token. Both methods of oauth will continue to work to support older client_id and client_secrets.
Manually assigning access_token in the config is been removed. All users should be moved over to at least the username/password authentication which uses the form on the .io site.
Also still need to update the image for what the redirect URL should be, set to the fitbit one currently.
Fixes https://github.com/home-assistant/home-assistant/issues/7546
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
wink:

Things that still need fixed:

[x] Add support back for old grant_type=password auth
[x] Add clarification that the .wink.conf is a hidden file
[x] Possible fix required for 401 issue after authentication

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[X] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies are only imported inside functions that use them (example).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

@balloob For some reason this stopped working for me if I have a password set I get a 401 after the authentication at Wink redirects back to Hass. If I remove my password it works fine. Any idea what would cause that?

Using Chrome and serving Hass over https ? Try opening the dev tools -> application -> clear storage -> select all and click clear site data.

Nope still the same thing. I tried rebooting everything an clearing all the data I know of, still get a 401. Wink's API sends a redirect URI of http://IP_ADDRESS:8123/auth/wink/callback?code=SOME_RANDOM_CODE?state= if I append that url with my password like so.
http://IP_ADDRESS:8123/auth/wink/callback?code=SOME_RANDOM_CODE&state=&api_password=MY_PASSWORD it works like it should/like it did a few days ago. I am not sure what the deal is.
I am serving Hass over http to my nginx reverse proxy, but I am not going through the proxy I am connecting directly to HA via the same computer that HA is running on using an IP address.

Just as an FYI, the only way I got this to work (suggested by @w1ll1am23 in testing) was to run it in a GUI session in the browser on my Pi which is hosting the HA server.

Hey guys, I have been very busy lately and not keeping up on the changes @w1ll1am23 is doing. Would like to have my wink devices working for more then a few hours with HASS. Can someone direct me on how to use the latest wink.py. I do have a Wink application with Oauth Settings and Oauth URLs.

@Dayve67 No one has reported that issue in production in several releases. Can you confirm that you are still having this problem with the newest production release 0.47?

@balloob  I, too, get a 401 after the authentication when Wink redirects back to Hass.  After I removed my Hass password I was able to finish the configuration process.  Once finished, I added back the Hass password and everything still appears to be working.

@w1ll1am23 make sure to remove WIP from the title once you're ready for code review.

@balloob will do, pretty sure the code is good. I was hoping to get one other person to test from the forums. I'll remove the WIP in the next day or so with or without another testers sign off.

@balloob This is ready for another look. I believe I have address all of your concerns.

Confirm that this has worked for me....

I just updated to HASS 0.50.1 and trying to get the WINK api working again. What do I need to put in the wink.conf file for information? And do I need to use the quotes around the client_id and client_secret info?
Do I also need to put my email and password in there too?

@Dayve67
You don't need to edit the wink.conf all you need is wink: in your main config. If that exists you will get a wink configurator in the frontend which will guide you through the setup.


In-app subscription iOS not working with SandBox testers

As I'm working on In-app subscription for iOS, it takes approx. 30 minutes to open Payment options for sandbox testers.
Second issue is whenever I call CompletePurchase method for force purchase it shows "storekit_duplicate_product_object" exception.
I'm using flutter version - 2.0.3
in_app_purchase: ^0.5.2
Please guide me to implement in-app subscription for iOS.

Hi @Pratiksha0796

I'm using flutter version - 2.0.3
in_app_purchase: ^0.5.2

You are using a quite old Flutter SDK and in_app_purchase plugin version. The latest Flutter SDK stable is 3.3.2 and in_app_purchase plugin is 3.0.7. So, try upgrading them and retrying to see if the issue is reproducible.

Please guide me to implement in-app subscription for iOS.

The goal of this Github repo is not to give assistance on personal code or the whole package/plugin project,
but to improve flutter reporting bugs or feature requests. Please see flutter's community for resources and ask questions like this. You may also get some help if you post it on Stack Overflow and flutterhelp.
If you encounter behavior that you believe could be a bug, please provide a completed and minimal reproducible code sample that represents the problem. Also, please provide the output of flutter doctor -v as well.
Thank you!

Hi @huycozy ,
Thanks for your reply.
Is there any way to solve this issue with my existing flutter version and plugin version.
Because we have more than 5 apps are live on this version and we don't need big change right now.

Hi @Pratiksha0796
There are many changes through versions of the Flutter SDK as well as the IAP plugin. For the best support, you should update them to the new version and check again. Thanks!


optimize: use iterator to remove timeout future.

Ⅰ. Describe what this PR did
1.use iterator to remove timeout future.
2.print log when load extConfiguration.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1920 into develop will increase coverage by 0.04%.
The diff coverage is 5.88%.

@@              Coverage Diff              @@
##             develop    #1920      +/-   ##
=============================================
+ Coverage      55.31%   55.35%   +0.04%
- Complexity      2404     2406       +2
=============================================
  Files            428      428
  Lines          14361    14359       -2
  Branches        1695     1694       -1
=============================================
+ Hits            7944     7949       +5
+ Misses          5699     5696       -3
+ Partials         718      714       -4

Impacted Files
Coverage Δ
Complexity Δ

...a/io/seata/core/rpc/netty/AbstractRpcRemoting.java
10.05% <5.88%> (+0.09%)
3 <0> (ø)
:arrow_down:

...o/seata/server/coordinator/DefaultCoordinator.java
48.41% <0%> (+0.39%)
28% <0%> (+1%)
:arrow_up:

...in/java/io/seata/server/session/GlobalSession.java
85.02% <0%> (+0.48%)
68% <0%> (+1%)
:arrow_up:

...server/store/file/FileTransactionStoreManager.java
57.91% <0%> (+0.94%)
29% <0%> (ø)
:arrow_down:

LGTM, because it is ConcurrentMap, why not just use for, but use iterator to loop?

ok,it has been modified.


Replicate QC flag

Is your feature request related to a problem? Please describe.
Users of TADA have noted that it would be useful to incorporate replicate field samples into water quality data analysis by flagging routine field sample measurements whose associated replicate field sample measurements are outside of a user-defined window of precision (relative percent difference or absolute difference).  A two-stage data-quality-indicator, where low values should be within the absolute difference limit and high values within the Relative Percent Difference (RPD) limit, may be appropriate. RPD is the calculated difference (RPD) between the routine sample result and its associated replicate sample result. For example, if the RPD/CV exceeds 20% some water quality, analysts consider that to be a potentially concerning lack of precision, especially for non-particulate analytes. However, depending on the characteristic being analyzed and the sampling method, acceptable RPDs can vary widely. Therefore, it is best for the user to define their own level of RPD acceptability. In addition, a tiered approach may be more appropriate, where the widely used 20% RPD for measurements can be used for results above XX-times the detection limit, but also an absolute difference approach can be used for those result-values near the detection limit, or lower than the detection limit (e.g., phosphorus). An absolute difference approach is more appropriate when implementing RPD for samples close to the detection limit, as even small absolute differences might show up as large relative percent differences that "fail" the 20% RPD test.
For example, when nutrient concentrations are close to detection limit, it becomes impossible to have a low RPD. In this scenario, high RPD's are acceptable because if you stand back and look at ALL the data, and not just the replicates, these data may be agreeing perfectly well that nutrients are very low. DO NOT throw out data if RPD is >20%, unless you have good reason, or you will potentially bias your data toward high concentrations. QA procedures should not bias statistical analyses of the data. Note that a modest error in a measurement will have a much smaller effect than implementing a QA process that builds in bias.
Describe the solution you'd like
Write new function to flag paired replicates using a tiered approach, where the widely used 20% RPD for measurements can be used for results above XX-times the detection limit, but also an absolute difference approach can be used for those result-values near the detection limit, or lower than the detection limit (e.g., phosphorus). An absolute difference approach is more appropriate when implementing RPD for samples close to the detection limit, as even small absolute differences might show up as large relative percent differences that "fail" the 20% RPD test.
Additional context
What are replicate samples and how are they used in water analyses?
Replicate field samples are samples taken to assess the reproducibility of the sampling technique or analytical method. They are independently carried through all the steps of the sampling and measurement process in an identical manner to their associated routine field sample and used to measure the precision of the total sampling method.
Theoretically, the analysis of a replicate field sample should yield a very similar result as its associated routine field sample. If the results are not the same or acceptably similar, it could signal possible contamination or other issues in the sampling chain. However, water quality can vary at very small scales. So, the field replicate can mix up analytical precision with small scale variability. Field replicates tell you the potential for your method to yield the same results at a single time and place, to the extent that you are actually in exactly the same place, and the few seconds (or any defined time window) from one sample to the next does not matter, and the water isn’t moving. Be careful about labeling data as imprecise or bad based on this alone.
See Issue Paper: https://usepa.sharepoint.com/:w:/r/sites/AutomatedDataAnalysisWorkingGroup/_layouts/15/Doc.aspx?sourcedoc={12716121-CFA6-4845-88B0-F1C88070B29C}&file=IssuePaper_ReplicateSamples_July2023.docx&action=default&mobileredirect=true
And notes: https://usepa.sharepoint.com/:w:/r/sites/AutomatedDataAnalysisWorkingGroup/_layouts/15/Doc.aspx?sourcedoc={4151F130-8C47-4A57-9D56-9A90D92FF74A}&file=TADAWorkingGroup_Jul2023.docx&action=default&mobileredirect=true
Reminders for TADA contributors addressing this issue
New features should include all of the following work:

[ ] Create the function/code.

[ ] Document all code using comments to describe what is does.

[ ] Create tests in tests folder.

[ ] Create help file using roxygen2 above code.

[ ] Create working examples in help file (via roxygen2).

[ ] Add to appropriate vignette (or create new one).

@wokenny13 - is this one you might be interested in working on?

This could be an item I am interested in. I will review the current function and the requested enhancement idea in this request!

This is a comment from @cefergus's review of https://github.com/USEPA/EPATADA/pull/501 (continuous data flagging updates)

I think the revised function looks good from what I could see. I ran the revised function on Fond du Lac data and a random TADA test data set. I looked for observations with same location, depth, comparable data identifier, and organization and it looked like the function is correctly flagging continuous vs discrete observations. Some observations labeled "Field Msr/Obs" and flagged as "Continuous" look like duplicated result values. But maybe a different function can flag those incidences.

After flagging replicates is developed, maybe that function can be run as part of TADA_FlagContinuousData so that replicate samples are not identified as continuous.


[Bug] Text gets cut on the bottom

S20 Ultra, 5x2 Widget gets cut on the bottom but supposedly has space to show.

I'll publish a new beta version of the app with a few fixes. Let me know if that fixes your problem.

I can see the same bug with the Samsung Galaxy Note 10+ as well

I've just published the beta version v2.0.5.
Let me know if you have the chance to try it and check if the bug persists.

Hi @tommasoberlose I can still see the cut off, 8 forgot to mention that it happens when I extend the widget to 5x1. In 4x1 looks good

@edimistra is the cutoff present in the application too?

No, it looks good in the app @tommasoberlose

The update really fixed everything for me.

2.0.5 fixed it for me. S20 Ultra

Great! Thank you guys!


Added PrimaryTextCard-RecentFiles

By submitting this pull request, you agree to the contribution guidelines

If you aren't familiar with how to contribute to open-source repositories using GitHub, or if you find the instructions on this page confusing, sign up for one of our Sharing is Caring events. It's completely free, and we'll guide you through the process.

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Related issues?
no

What's in this Pull Request?
Added PrimaryText-RecentFiles, it shows a counter of the recent files from Microsoft Graph to the card view and enables the user to navigate through the files and open the selected file in the quick view.

Hi @dcashpeterson and thanks for the feedback, I'll take a look as soon as I can and let you know.

Hi @dcashpeterson, I committed a fix for the console errors, it seems that the base64 images in the quick view card template generated those errors.
I tried to verify the open button issue but I cannot reproduce the problem, can you please explain better what's the issue?


Running "npm install" on working project blocks development

Describe the bug
Using "npm" as package manager not working properly and blocks development.
To Reproduce
Steps to reproduce the behavior:

Run "create-universal-react"
Choose "npm" as package manager
Choose any arch type [ssg,ssr,microApp]
Run "npm run dev"

Expected behavior
After initial setup and running "npm run dev" should run all apps without any errors
Error
"Error: Cannot find module 'react'"
Node Version
v14.17.6
npm Version
v6.14.15

Issue fixed with npm version 8.5.5. Use "npm install -g npm@latest" to update npm version. Closing.


Show CCPA feature in docs

Is there a PBJS PR that goes along with this docs update? I took a quick look at recent releases and open PRs but didn't see one.

Is there a PBJS PR that goes along with this docs update? I took a quick look at recent releases and open PRs but didn't see one.

nope , this feature already was inside adapter, but was not documented


Fix GridObjectCollection

Overview
GridObjectCollection was not properly working:

Horizontal and Vertical layouts were not even implemented
Rows and Columns were not swapped when switching between which comes first, offsetting the whole layout from the center.

@cre8ivepark, I think this is in your area of expertise

Something broke prior to porting the collections from HTK -> MRTK. I found this bug but haven't had time to fix it. Thank you @Alexees !
I'd argue the different layout results are in fact the desired ones.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 2290 ms

Resolved: Bofrost.at performance has improved in 30d2930 after 34 minutes.


[ROCKETMQ-14]invoke callback shoule be invoked in an executor rather than in current thread.

For success callback,  processResponseCommand will execute invoke callback in a saparate executor rather than the time thread.
But for timeout problem , the timeout callback will be invoked directly in timer thread/netty selector thread.
If the user put some time-cost task when timeout, the other timeout callback will be blocked to schedule.
JIRA issue: https://issues.apache.org/jira/browse/ROCKETMQ-14

@Jaskey Thanks for your PR, Could you paste some unit test for these question :-) . please see our contributing checklist, https://github.com/apache/incubator-rocketmq/blob/master/CONTRIBUTING.md

@vongosling
please check the commited unit test .

@Jaskey Thanks your PR
Could you abide our PR process(modify your PR subject and mention your jira address in the description), please follow this PR. #5

Source code seems ok, please @zhouxinyu @lollipopjin review it

Hi,
This PR has been merged, but next time please use JIRA issue name(ROCKETMQ-14) as branch name instead of master. Please refer to here for more details.
Thanks.


uniform equivilent to System.Random.randoms and randomRs

I'm porting some code from using System.Random to this library. The code is using randoms and randomRs functions which produces an infinite list of random values. Is there an advised way to do the same thing here?
If not, then an alternative would be a vector, but I'd need a vector of ranged values (i.e. uniformR), but we don't seem to have that available.

Unfortunately there's no way to generate infinite list since generator work in ST/IO it uses mutable state underneath.
Generating finite list/vector on other hand is easy: replicateM n (uniformR range gen)

Thanks, closing issue


No header, minor

If one has no header (initial block) but refers to a minor (at least in a save) then it does not see it.

Done, miraculously enough.


Upgrade SDK version to v0.1.0

@jtimeus-slalom - I hope you don't mind I started the work to migrate from the pre-release SDK version over to the latest.
Here are my steps:

poetry add singer-sdk=="^0.1.0"
import the new standard tests file from the cookiecutter template
remove references to helpers module which is now deprecated

utcnow() is deprecated. It was being imported but wasn't being referenced so I simply deleted the import.
singer_sdk.helpers.typing is now simply singer_sdk.typing. I removed .helpers from the applicable reference lines.

Ready for retest!
poetry run pytest should do the trick.

poetry run pytest is throwing a strange error for me.  I got the tap working after one method name change, and confirmed that data was being emitted in a format suitable for target consumption, but I don't understand the error coming from pytest
PS C:\Repos_Other\tap-powerbi-metadata> poetry run tap-powerbi-metadata --config=.secrets\config.json > Activity.jsonl

time=2021-04-12 15:57:09 name=tap-powerbi-metadata level=INFO message=tap-powerbi-metadata v0.0.1, Singer SDK v0.1.2)
time=2021-04-12 15:57:09 name=tap-powerbi-metadata level=INFO message=Skipping parse of env var settings...
time=2021-04-12 15:57:09 name=tap-powerbi-metadata level=INFO message=Config validation passed with 0 errors and 0 warnings.
time=2021-04-12 15:57:09 name=tap-powerbi-metadata level=INFO message=Beginning INCREMENTAL sync of stream 'ActivityEvents'...
time=2021-04-12 15:57:09 name=tap-powerbi-metadata level=INFO message=OAuth authorization attempt was successful.
time=2021-04-12 15:57:11 name=tap-powerbi-metadata level=INFO message=OAuth authorization attempt was successful.
time=2021-04-12 15:57:13 name=tap-powerbi-metadata level=INFO message=OAuth authorization attempt was successful.

Aborted!

PS C:\Repos_Other\tap-powerbi-metadata> cat Activity.jsonl | target-csv

INFO Sending version information to singer.io. To disable sending anonymous usage data, set the config parameter "disable_collection" to true

PS C:\Repos_Other\tap-powerbi-metadata> poetry run pytest

  FileNotFoundError

  [WinError 2] The system cannot find the file specified

  at c:\python38\lib\subprocess.py:1307 in _execute_child
      1303│             sys.audit("subprocess.Popen", executable, args, cwd, env)
      1304│
      1305│             # Start the process
      1306│             try:
    → 1307│                 hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
      1308│                                          # no special security
      1309│                                          None, None,
      1310│                                          int(not close_fds),
      1311│                                          creationflags,
PS C:\Repos_Other\tap-powerbi-metadata>

Maybe it ahs something to do with poetry expecting an exe as noted here?

well, it helps of pytest is installed...did a pipx install pytest and got further
Now poetry run pytest is giving an error about not being able to import singer_sdk, even though there are several import singer_sdk statements in the code.
PS C:\Repos_Other\tap-powerbi-metadata> poetry run pytest
========================================================== test session starts ==========================================================
platform win32 -- Python 3.8.6, pytest-6.2.3, py-1.10.0, pluggy-0.13.1
rootdir: C:\Repos_Other\tap-powerbi-metadata
collected 0 items / 1 error

================================================================ ERRORS =================================================================
__________________________________ ERROR collecting tap_powerbi_metadata/tests/test_standard_tests.py ___________________________________
ImportError while importing test module 'C:\Repos_Other\tap-powerbi-metadata\tap_powerbi_metadata\tests\test_standard_tests.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
c:\python38\lib\importlib\__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tap_powerbi_metadata\tests\test_standard_tests.py:5: in <module>
    from singer_sdk.testing import get_standard_tap_tests
E   ModuleNotFoundError: No module named 'singer_sdk'
======================================================== short test summary info ========================================================
ERROR tap_powerbi_metadata/tests/test_standard_tests.py
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
=========================================================== 1 error in 0.12s ============================================================
PS C:\Repos_Other\tap-powerbi-metadata>

@jtimeus-slalom - hello!

Now poetry run pytest is giving an error about not being able to import singer_sdk, even though there are several import singer_sdk statements in the code.

This makes me think that pytest is not aware of the poetry environment. I checked and pytest is included in pyproject.toml. Can you try to run poetry install just in case that pytest library hasn't been installed yet in the poetry virtual environment? Also, it might be worthwhile to uninstall (at least temporarily for debugging) the global version of pytest (pipx uninstall pytest).
Can you try poetry add -D pytest? It might be that the version of pytest being installed is not getting access to the virtual environment?
In the meanwhile, I'll see if I can replicate the issue locally.

Regarding this error:

  FileNotFoundError

  [WinError 2] The system cannot find the file specified

I can confirm this looks like a poetry error, most likely poetry failing to find pytest. (As discussed above in this thread.)

@jtimeus-slalom - I saw the latest commit of adding pytest to CI. I don't know if I mentioned this as a breaking change earlier, but the SDK now looks for env variables in the form (all uppercase): <PLUGIN>_<SETTING>. (Previously, the expected input was a lowercase setting.)
Also:

When run in CLI, the env vars are only parsed if you add --config=ENV
When run in CI and Pytest tests, env vars are parsed automatically.

I think I might have triggered an infosec tool that blocks suspicious access, but after doing the poetry remove -D pytest then reverting the files and doing poetry install a few times, it started running the tests...?
I am now getting errors like the ones seen in the cicd pipeline output

Was able to get pytest to succeed locally by updating test_standard_tests.py to read from my local config file
This won't allow us to run pytest in the cicd pipeline until we have a test org or some other safe location  to auth to and test against


Investigate for a possible OutputMessage class mapping after serialization

Evaluate if there are any reasons to add a method that help to map a post-serialized OutputMessage class instance.

see  #134


iOS notifications are not displayed when running the app

When we are not running our app; e.g., in the main screen or in some other app, the notification will appear in the notification bar.  However, if we are running our app, the notification will not show up.   We are testing on iOS 7.0.4.
Please advise.
Dave

Hope you are doing well. I am using Pushwoosh cordova plugin for Android and iOS apps. I am just wondering if hwid is always unique for iOS device, so I can use to detect special ios device with it? It will be changed for any circumstances? In that case, I will not be able to use hwid as unique device id for iOS device. Thanks for your great help.
Sincerely

@Wang0620 please open a new issue for this.

I've just opened new issue. Please take a look at and let me know.
https://github.com/Pushwoosh/phonegap-cordova-push-notifications/issues/60
Thanks